diff --git a/marked/Rel-18/25_series/25106/raw.md b/marked/Rel-18/25_series/25106/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..87ca019da57bf10d5a06390623d5400b4594530e --- /dev/null +++ b/marked/Rel-18/25_series/25106/raw.md @@ -0,0 +1,1326 @@ + + +# 3GPP TS 25.106 V18.0.0 (2024-03) --- + +*Technical Specification* + +![5G Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRA repeater radio transmission and reception (Release 18)** + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +--- + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G'. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 Relationship between Minimum Requirements and Test Requirements ..... | 7 | +| 4.2 Regional requirements..... | 8 | +| 5 Frequency bands and channel arrangement ..... | 9 | +| 5.1 Frequency bands..... | 9 | +| 5.2 TX - RX frequency separation ..... | 9 | +| 5.3 Channel arrangement..... | 10 | +| 5.3.1 Channel spacing..... | 10 | +| 5.3.2 Channel raster..... | 10 | +| 5.3.3 Channel number..... | 10 | +| 6 Output power..... | 12 | +| 6.1 Maximum output power..... | 13 | +| 6.1.1 Minimum Requirements..... | 13 | +| 7 Frequency stability..... | 13 | +| 7.1 Minimum requirement..... | 13 | +| 8 Out of band gain..... | 13 | +| 8.1 Minimum requirement..... | 13 | +| 9 Unwanted emission..... | 14 | +| 9.1 Out of band emission..... | 14 | +| 9.1.1 Void..... | 14 | +| 9.1.2 Operating band unwanted emissions ..... | 14 | +| 9.1.3 Protection of the BS receiver in the operating band..... | 19 | +| 9.1.3.1 Minimum Requirement..... | 19 | +| 9.1.4 Co-existence with services in adjacent frequency bands..... | 19 | +| 9.1.4.1 Minimum requirement..... | 19 | +| 9.2 Spurious emissions..... | 19 | +| 9.2.1 General Requirements ..... | 20 | +| 9.2.1.1 Minimum Requirement (Category A)..... | 20 | +| 9.2.1.2 Minimum Requirement (Category B)..... | 20 | +| 9.2.2 Void..... | 21 | +| 9.2.3 Co-existence with other systems in the same geographical area..... | 21 | +| 9.2.3.1 Minimum Requirements ..... | 22 | +| 9.2.4 Co-existence with co-located and co-sited Base Stations ..... | 25 | +| 9.2.4.1 Minimum Requirements ..... | 26 | +| 9.2.5 Co-existence with PHS..... | 28 | +| 9.2.5.1 Minimum Requirement..... | 28 | +| 9.2.6 Co-existence with UTRA-TDD and/or E-UTRA TDD..... | 29 | +| 9.2.6.1 Operation in the same geographic area..... | 29 | +| 9.2.6.1.1 Minimum Requirement..... | 29 | +| 9.2.6.2 Co-located Repeaters and UTRA-TDD and/or E-UTRA TDD base stations..... | 31 | +| 9.2.6.2.1 Minimum Requirement ..... | 31 | +| 9.2.7 Void..... | 33 | +| 9.2.8 Protection of public safety operations ..... | 33 | +| 9.2.8.1 Minimum Requirement..... | 33 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------|-----------| +| 10 | Modulation accuracy..... | 33 | +| 10.1 | Error Vector Magnitude ..... | 33 | +| 10.1.1 | Minimum requirement..... | 34 | +| 10.2 | Peak code domain error..... | 34 | +| 10.2.1 | Minimum requirement..... | 34 | +| 10.3 | Relative Code Domain Error (RCDE) for 64QAM modulation ..... | 34 | +| 10.3.1 | Minimum requirement..... | 34 | +| 11 | Input Intermodulation ..... | 34 | +| 11.1 | General Requirement..... | 34 | +| 11.1.1 | Minimum requirement..... | 34 | +| 11.2 | Co-location with BS in other systems ..... | 35 | +| 11.2.1 | Minimum requirements - Co-location with GSM, DCS, PCS, UTRA FDD and/or E-UTRA FDD..... | 35 | +| 11.2.2 | Minimum Requirement - Co-location with UTRA-TDD and/or E-UTRA TDD..... | 38 | +| 11.3 | Co-existence with other systems..... | 39 | +| 11.3.1 | Minimum requirements ..... | 39 | +| 12 | Output intermodulation ..... | 42 | +| 12.1 | Minimum requirement..... | 42 | +| 13 | Adjacent Channel Rejection Ratio (ACRR) ..... | 43 | +| 13.1 | Definitions and applicability ..... | 43 | +| 13.2 | Minimum Requirements..... | 43 | +| Annex A (informative): | Change History..... | 44 | + +# --- 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 radio frequency performance of UTRA FDD repeaters. + +# --- 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-R Recommendation SM.329: "Unwanted emissions in the spurious domain". +- [2] 3GPP TS 25.143: "UTRA Repeater Conformance Testing". +- [3] 3GPP TS 25.113: "Base Station and Repeater Electromagnetic Compatibility". +- [4] ETSI ETR 273-1-2: "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". +- [5] 3GPP TR 25.942: "RF System Scenarios". +- [6] 3GPP TS 25.104: "UTRA(BS) FDD; Radio transmission and Reception". +- [7] CEPT ECC Decision (13)03, "The harmonised use of the frequency band 1452-1492 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL) ". +- [8] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) 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: + +**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. + +**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 5.1, Table 5.1. + +NOTE 2: Unless specified, operating band refers to the uplink operating band and downlink operating band. + +**Pass band:** 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). In operating bands specified with only down-link or up-link, only the up-link or down-link as specified for the operating band is repeated. + +**Up-link:** Signal path where mobile transmits and base station receives. + +## 3.2 Symbols + +(void) + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------------------| +| BS | Base Transceiver Station | +| DL | Down Link (forward link) | +| DTT | Digital Terrestrial Television | +| EVM | Error Vector Magnitude | +| EIRP | Effective Isotropic Radiated Power | +| FDD | Frequency Division Duplex | +| FFS | For Further Study | +| IMT2000 | International Mobile Telecommunication-2000 | +| ITU | International Telecommunication Union | +| RCDE | Relative Code Domain Error. | +| RF | Radio Frequency | +| 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 General + +This specification applies only to UTRA-FDD repeaters. + +Unless otherwise stated, all requirements in this specification apply to both the up-link and down-link directions, where applicable. + +## 4.1 Relationship between Minimum Requirements and Test Requirements + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The repeater test specification 25.143 section 5 [2] 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 Part 1 sub-part 2 section 6.5 [4]. + +## 4.2 Regional requirements + +Some requirements in TS 25.106 may only apply in certain regions. Table 4.1 lists all requirements that may be applied differently in different regions. + +**Table 4.1: List of regional requirements.** + +| Clause number | Requirement | Comments | +|---------------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5.1 | Frequency bands | Some bands may be applied regionally. | +| 5.2 | TX – RX frequency separation | The requirement is applied according to which frequency bands in Clause 5.1 that are supported by the Repeater. | +| 5.3 | Channel arrangement | The requirement is applied according to what frequency bands in clause 5.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. Additional spectrum protection may apply regionally. | +| 9.2.1.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 [1], are applied. | +| 9.2.1.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 [1], are applied. | +| 9.2.3 | 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.4 | 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 FDD BS operating in another frequency band are co-located with a UTRA FDD Repeater. | +| 9.2.5 | 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.6.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.6.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.8 | Spurious emissions: Protection of public safety operations | This requirement may be applied for the protection of public safety systems in geographic areas in which both UTRA FDD Repeater and public safety systems are deployed. | +| 11.2 | Input Intermodulation: Co-location with BS in other systems | The requirement may be applied when GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD BS operating in another frequency band and UTRA-FDD Repeaters are co-located. | +| 11.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 Frequency bands and channel arrangement + +## 5.1 Frequency bands + +- a) A UTRA/FDD Repeater is designed to operate in one or several pass bands within either of the following operating bands; + +**Table 5.1: Frequency bands** + +| Operating Band | UL Frequencies
UE transmit, Node B receive | DL frequencies
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 - 1447.9 MHz | 1475.9 - 1495.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 | +| XXVI | 814 - 849 MHz | 859 - 894 MHz | +| XXXII | N/A | 1452 - 1496 MHz | + +- b) Deployment in other frequency bands is not precluded. + +## 5.2 TX - RX frequency separation + +- a) A UTRA/FDD repeaters is designed to operate with the following TX to RX frequency separation + +**Table 5.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 | +| XXVI | 45 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. + +## 5.3 Channel arrangement + +### 5.3.1 Channel spacing + +The nominal channel spacing is 5 MHz, but this can be adjusted to optimise performance in a particular deployment scenario. + +### 5.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 5.3, which means that and the centre frequencies for these channels are shifted 100 kHz relative to the general raster. + +### 5.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 5.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 5.4. + +Table 5.3: UARFCN definition (general) + +| Band | UPLINK (UL)
UE transmit, Node B receive | | | DOWNLINK (DL)
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 | +| XXVI | -291 | 816.4 | 846.6 | -291 | 861.4 | 891.6 | +| XXXII | - | N/A | N/A | 131 | 1454.4 | 1493.6 | + +Table 5.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 | +| XXVI | -325.9 | 816.5, 821.5, 826.5,
827.5, 831.5, 832.5,
836.5, 837.5, 841.5,
842.5, 846.5 | -325.9 | 861.5, 866.5, 871.5, 872.5,
876.5, 877.5, 881.5, 882.5,
886.5, 887.5, 891.5 | +| XXXII | - | - | 87.1 | 1454.5, 1459.5, 1464.5,
1469.5, 1474.5, 1479.5,
1484.5, 1489.5 | + +# 6 Output power + +Output power, $P_{out}$ , of the repeater is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter. + +Rated output power, $P_{RAT}$ , of the repeater is the mean power level per carrier at maximum repeater gain that the manufacturer has declared to be available at the antenna connector. + +## 6.1 Maximum output power + +Maximum output power, $P_{max}$ , of the repeater is the mean power level per carrier measured at the antenna connector in specified reference condition. + +### 6.1.1 Minimum Requirements + +The requirements shall apply at maximum gain, with WCDMA signals in the pass band of the repeater, at levels that produce the maximum rated output power per channel. + +When the power of all signals is increased by 10 dB, compared to the power level that produce the maximum rated output power, the requirements shall still be met. + +In normal conditions, the Repeater maximum output power shall remain within limits specified in Table 6.1 relative to the manufacturer's rated output power. + +**Table 6.1: Repeater output power; normal conditions** + +| Rated output power | Limit | +|----------------------|-----------------| +| $P \geq 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, the Repeater maximum output power shall remain within the limits specified in Table 6.2 relative to the manufacturer's rated output power. + +**Table 6.2: Repeater output power; extreme conditions** + +| Rated output power | Limit | +|----------------------|---------------------| +| $P \geq 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 of conditions defined as normal. + +# --- 7 Frequency stability + +Frequency stability is the ability to maintain the same frequency on the output signal with respect to the input signal. + +## 7.1 Minimum requirement + +The frequency deviation of the output signal with respect to the input signal shall be no more than $\pm 0,01$ ppm. + +# --- 8 Out of band gain + +Out of band gain refers to the gain of the repeater outside the pass band. + +## 8.1 Minimum requirement + +The intended use of a repeater in a system is to amplify the in band signals and not to amplify the out of band emission of the donor base station. + +In the intended application of the repeater, the out of band gain is less than the donor coupling loss. + +The repeater minimum donor coupling loss shall be declared by the manufacturer. This is the minimum required attenuation between the donor BS and the repeater for proper repeater operation. + +The gain outside the pass band shall not exceed the maximum level specified in table 8.1, where: + +- $f\_offset$ is the distance from the centre frequency of the first or last 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$ MHz | 60 dB | +| $3,5 \leq f\_offset < 7,5$ MHz | 45 dB | +| $7,5 \leq f\_offset < 12,5$ MHz | 45 dB | +| $12,5$ MHz $\leq f\_offset$ | 35 dB | + +For $12,5$ MHz $\leq f\_offset$ the out of band gain shall not exceed the maximum gain of table 8.2 or the maximum gain stated in table 8.1 whichever is lower. + +**Table 8.2: Out of band gain limits 2** + +| Repeater maximum output power as in 9.1.1.1 | Maximum gain | +|-----------------------------------------------------------------------------|---------------------------------------------------------------------| +| $P < 31$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $31$ dBm $\leq P < 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $P \geq 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss - ( $P-43$ dBm) | +| NOTE 1: The out of band gain is considered with $12,5$ MHz $\leq f\_offset$ | | + +# 9 Unwanted emission + +Unwanted emissions consist of out-of-band emissions and spurious emissions [1]. 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 + +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 [1], s4.1. + +NOTE 2: Limit based on ITU-R Recommendation SM.329 [1], s4.3 and Annex 7. + +NOTE 3: Bandwidth as in ITU-R Recommendation SM.329 [1], s4.1. Upper frequency as in ITU-R SM.329 [1], s2.5 table 1. + +The mask defined in tables 9.1 to 9.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 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. The requirements shall also apply at maximum gain without WCDMA signals in the pass band. + +Emissions shall not exceed the maximum level specified in tables 9.1 to 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{offsetmax}}$ is 12,5 MHz. +- $\Delta f_{\max}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measurement filter. + +![Figure 9.1: Illustrative diagram of 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 2.5, 2.7, 3.5, and 7.5. The mask is defined by several horizontal and sloped lines. Key power levels are indicated: P = 31 dBm (at 3.5 MHz), P = 39 dBm (at 7.5 MHz), and P = 43 dBm (at 7.5 MHz). The mask is shaded in green.](a2f89834a149b852721f8887349fd6fa_img.jpg) + +Figure 9.1: Illustrative diagram of 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 2.5, 2.7, 3.5, and 7.5. The mask is defined by several horizontal and sloped lines. Key power levels are indicated: P = 31 dBm (at 3.5 MHz), P = 39 dBm (at 7.5 MHz), and P = 43 dBm (at 7.5 MHz). The mask is shaded in green. + +**Figure 9.1: Illustrative diagram of emission mask** + +**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 | 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 dBm | 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}$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -26 dBm | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $4,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm | 1 MHz | + +**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 | 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 dBm | 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}$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -26 dBm | 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 dBm | 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 | + +**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 | 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}$ | 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}$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $P - 65 \text{ dB}$ | 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}$ | 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 | + +**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 dBm | 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}$ | 30 kHz | +| ( Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -34 dBm | 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 dBm | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f\_max$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -25 dBm | 1 MHz | + +For operation in band II, IV, V, X, XII, XIII, XIV, XXV and XXVI, 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 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 dBm | 1 MHz | + +**Table 9.4B: Additional emission mask values for Band V and XXVI** + +| 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 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 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 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 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.4.D, 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, $F_{\text{filter}}$ | 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 [6] 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. + +In certain regions, the following requirements may apply to UTRA repeaters operating in Band XXXII within 1452-1492 MHz. The level of unwanted emissions, measured on centre frequencies $f_{\text{offset}}$ with filter bandwidth, according to Table 9.4E shall neither exceed the maximum emission level $P_{\text{EM,B32,a}}$ , $P_{\text{EM,B32,b}}$ nor $P_{\text{EM,B32,c}}$ declared by the manufacturer. + +**Table 9.4E: Declared operating band XXXII unwanted emission within 1452-1492 MHz** + +| Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Declared emission level [dBm] | Measurement bandwidth | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|-----------------------| +| 5 MHz | $P_{\text{EM,B32,a}}$ | 5 MHz | +| 10 MHz | $P_{\text{EM,B32,b}}$ | 5 MHz | +| $15 \text{ MHz} \leq f_{\text{offset}} \leq f_{\text{offsetmax,B32}}$ | $P_{\text{EM,B32,c}}$ | 5 MHz | +| NOTE: $f_{\text{offsetmax,B32}}$ denotes the frequency difference between the lower channel carrier frequency and 1454.5 MHz, and the frequency difference between the upper channel carrier frequency and 1489.5 MHz for the set channel position. | | | + +NOTE: The regional requirement, included in [7], is defined in terms of EIRP per antenna, 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 base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS36.104 [8]. + +In certain regions, the following requirement may apply to UTRA repeaters operating in Band XXXII within 1452-1492 MHz for the protection of services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to Table 9.4F shall neither exceed the maximum emission level $P_{\text{EM,B32,d}}$ nor $P_{\text{EM,B32,e}}$ declared by the manufacturer. This requirement applies in the frequency range 1429-1518 MHz even though part of the range falls in the spurious domain. + +**Table 9.4F: Operating band XXXII declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission level [dBm] | Measurement bandwidth | +|---------------------------------------------------------------------|-------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{\text{filter}} \leq 1448.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | +| $F_{\text{filter}} = 1450.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $F_{\text{filter}} = 1493.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{\text{filter}} \leq 1517.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | + +NOTE: The regional requirement, included in [7], is defined in terms of EIRP, 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 base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS36.104 [8]. + +### 9.1.3. Protection of the BS receiver in the operating band + +This requirement shall be applied for the protection of UTRA FDD BS receiver in geographic areas in which UTRA-FDD Repeater and UTRA-FDD BS are deployed. + +The requirement applies outside the emission mask. + +#### 9.1.3.1 Minimum Requirement + +This requirement applies to the uplink of the repeater, at maximum gain. + +The power of any operating band unwanted emission shall not exceed the limits in Table 9.7A. + +**Table 9.7A: Uplink operating band unwanted emissions limits for protection of the BS receiver** + +| Maximum Level | Measurement Bandwidth | Note | +|---------------|-----------------------|------| +| -53 dBm | 100 kHz | | + +NOTE 1: These requirements in Table 9.7A: for the uplink 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 5.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.16: 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 + +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 repeaters RF output port. + +The spurious emission limits apply from 9 kHz to 12.75 GHz (or above, as indicated in Table 9.5 and 9.5A), 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.13 and 9.16 that apply also closer than 10 MHz from repeaters operating band. + +Unless otherwise stated, all requirements are measured as mean power. + +### 9.2.1 General Requirements + +The requirements of either subclause 9.2.1.1 or subclause 9.2.1.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. + +#### 9.2.1.1 Minimum Requirement (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 [1], 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.5. The requirements shall also apply at maximum gain without WCDMA signals in the pass band. + +When the power in all channels is increased by 10 dB, compared to the input level producing the maximum rated output power, the requirement shall still be met. + +**Table 9.5: Up-link and down-link: General spurious emissions limits, Category A** + +| Band | Maximum level | Measurement Bandwidth | Note | | +|----------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|----------------|--| +| 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,75GHz – 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 [1], s4.1 | | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [1], s2.5 table 1 | | | | | +| NOTE 3: Applies only for Band XXII | | | | | + +#### 9.2.1.2 Minimum Requirement (Category B) + +The following requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [1], are applied. + +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 table 9.5A for the down- and up-link. + +The requirements shall also apply at maximum gain without WCDMA signals in the pass band. + +When the power in all channels is increased by 10 dB, compared to the input level producing the maximum rated output power, the requirement shall still be met. + +**Table 9.5A: 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 [1], s4.1 | | | | +| NOTE 2: Bandwidth as in ITU-R Recommendation SM.329 [1], s4.1. Upper frequency as in ITU-R SM.329 [1], s2.5 table 1 | | | | +| NOTE 3: Applies only for Band XXII | | | | + +**Table 9.6: (Void)****Table 9.6A: (Void)****Table 9.6B: (Void)****Table 9.6C: (Void)****Table 9.6D: (Void)****Table 9.6E: (Void)****Table 9.6F: (Void)** + +### 9.2.2 Void + +### 9.2.3 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.3.1 Minimum Requirements + +The power of any spurious emission shall not exceed the limits of Table 9.9 for a UTRA FDD Repeater where requirements for co-existence with the system listed in the first column apply. + +**Table 9.9: 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 geographic 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 or XXVI. | +| | 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 or XXVI, 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 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 | 869 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or XXVI. | + +| | | | | | +|----------------------------------------------------|---------------------|---------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 5 | 824 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band V or XXVI, 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, XX or XXVI. | +| | 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, XX or XXVI. | +| | 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 the UTRA FDD Repeater operating in band V, XX or XXVI. | +| UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | +| | 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 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, band XXI or XXXII. | +| | 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. For UTRA repeaters operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. | +| | 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. For UTRA repeaters operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. | +| 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 XIII, since it is already covered by the band XX 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 uplink 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 | 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. | +| | 2010 - 2020 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 24 | 1525 - 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. | +| UTRA FDD Band XXVI or E-UTRA Band 26 | 859 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI. | +| | 814 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XXVI since it is already covered by the requirement in sub-clause 9.1.3. For UTRA FDD Repeater operating in band V, it applies for 814 MHz to 824 MHz, while the rest is covered in sub-clause 9.1.3. | +| E-UTRA Band 27 | 852 - 869 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI. | +| | 807 - 824 MHz | -49 dBm | 1 MHz | For UTRA FDD Repeater operating in band XXVI, it applies for 807 MHz to 814 MHz, while the rest is covered in sub-clause 9.1.3. | +| E-UTRA Band 28 | 758 - 803 MHz | -52 dBm | 1 MHz | | +| | 703 - 748 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 29 | 717 - 728 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 30 | 2350 - 2360 MHz | -52 dBm | 1 MHz | | +| | 2305 - 2315 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 31 | 462.5 - 467.5 MHz | -52 dBm | 1 MHz | | +| | 452.5 - 457.5 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA Repeater operating in Band XI, XXI, or XXXII | + +- | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 5.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.4 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.4.1 Minimum Requirements + +The power of any spurious emission shall not exceed the limits of Table 9.10 for a UTRA FDD Repeater where requirements for co-location with the Base Station listed in the first column apply. + +**Table 9.10: 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 or band XXVI. 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 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 or band XXVI. 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 | 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, XX or XXVI. | + +| | | | | | +|-------------------------------------------------|---------------------|---------|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Band 6, 18 or 19 | 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, XX or XXVI. | +| 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 E-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 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. This requirement applies only for operation between 1475.9 MHz and 1495.9 MHz for UTRA FDD repeater operating in band XXXII. | +| | 1447.9 - 1462.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL 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. This requirement applies only for operation between 1475.9 MHz and 1495.9 MHz for UTRA FDD repeater operating in band XXXII. | +| 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 the UL of 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 2, 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. | +| UTRA FDD Band XXVI or E-UTRA Band 26 | 814 – 849 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XXVI. 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 V, it applies from 814 MHz to 824MHz, 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. | +| E-UTRA Band 27 | 807 – 824 MHz | -96 dBm | 100 kHz | For UTRA FDD Repeater operating in band XXVI, this requirement applies from 807 MHz to 814MHz, 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. | +| E-UTRA Band 28 | 703 – 748 MHz | -96 dBm | 100 kHz | | +| E-UTRA Band 30 | 2305 – 2315 MHz | -96 dBm | 100 kHz | | +| E-UTRA Band 31 | 452.5 – 457.5 MHz | -96 dBm | 100 kHz | | +| NOTE 1: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeater operating band (see Table 5.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 FDD 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. | | | | | + +### 9.2.5 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.5.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.13: UTRA Repeater up-link and down-link spurious 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.6 Co-existence with UTRA-TDD and/or E-UTRA TDD + +#### 9.2.6.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.6.1.1 Minimum Requirement + +In the down-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.14: 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 | | +| E-UTRA Band 44 | 703 – 803 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.14A: 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 | | +| E-UTRA Band 44 | 703 – 803 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.14 and Table 9.14A, 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.6.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 BS and UTRA-FDD Repeater are co-located. + +##### 9.2.6.2.1 Minimum Requirement + +In the down-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.15: 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 | This requirement does not apply to E-UTRA FDD Repeater operating in band VII. | +| 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 | | +| E-UTRA Band 44 | 703 – 803 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.15A: 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, 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 | This requirement does not apply to E-UTRA FDD Repeater operating in band VII. | +| 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 | | +| E-UTRA Band 44 | 703 – 803 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.15 and Table 9.15A , 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.15A 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.7 Void + +### 9.2.8 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.8.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.16: Spurious emissions limits for the up-link and down-link of UTRA Repeater for protection of 700 MHz 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 | | + +This requirement shall be applied to repeaters operating in Band XXVI to ensure that appropriate interference protection is provided to 800 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. + +The power of any spurious emission shall not exceed: + +**Table 6.16A: Spurious emissions limits for the up-link and down-link of UTRA Repeater for protection of 800 MHz public safety operations** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|----------------|---------------|---------------|-----------------------|--------------------------------------------------------| +| XXVI | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5kHz from the channel edge | + +# 10 Modulation accuracy + +## 10.1 Error Vector Magnitude + +The modulation accuracy is defined by the Error Vector Magnitude (EVM), which is a measure of the difference between the theoretical waveform and a modified version of the measured waveform. This difference is called the error vector. The measured waveform is modified by first passing it through a matched root raised cosine filter with bandwidth 3.84 MHz and roll-off $\alpha=0.22$ . The waveform is then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing so as to minimise the error vector. The EVM result is defined as root of the ratio of the mean error vector power to the mean reference signal power expressed as a %. + +The measurement interval is one power control group (timeslot). The repeater shall operate with an ideal WCDMA signal in the pass band of the repeater at a level, which produce the maximum rated output power per channel, as specified by the manufacturer. + +### 10.1.1 Minimum requirement + +The Error Vector Magnitude shall not be worse than 12,5 %. + +## 10.2 Peak code domain error + +The peak code domain error is computed by projecting the power of the error vector (as defined in subclause 10.1) onto the code domain at a specified 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.1 Minimum requirement + +The peak code domain error shall not exceed -35 dB at spreading factor 256. + +## 10.3 Relative Code Domain Error (RCDE) for 64QAM modulation + +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. + +### 10.3.1 Minimum requirement + +The average Relative Code Domain Error for 64QAM modulated codes shall not exceed -21 dB at spreading factor 16. + +# --- 11 Input Intermodulation + +The input intermodulation is a measure of the capability of the repeater to inhibit the generation of interference in the pass band, in the presence of interfering signals on frequencies other than the pass band. + +## 11.1 General Requirement + +The following requirement applies for interfering signals in the frequency bands defined in sub-clause 5.1, depending on the repeaters pass band. The requirement shall be met with the repeater operating at maximum gain. + +### 11.1.1 Minimum requirement + +For the parameters specified in table 11.1, the power in the pass band, shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the 3rd order intermodulation product is positioned in the centre of the pass band. + +Table 11.1 specifies the parameters for two interfering signals, where: + +- $f\_offset$ is the separation between the centre frequency of first or last 5 MHz channel in the pass band and one the interfering signals. + +**Table 11.1: Input intermodulation requirement** + +| $f\_offset$ | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|-------------|---------------------------|-----------------|-----------------------| +| 3,5 MHz | -40 dBm | 2 CW carriers | 1 MHz | + +## 11.2 Co-location with BS in other systems + +The requirement shall be met with the repeater operating at maximum gain. + +### 11.2.1 Minimum requirements - Co-location with GSM, DCS, PCS, UTRA FDD and/or E-UTRA FDD + +This additional input intermodulation requirement 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. + +For the parameters specified in table 11.2, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the lowest order intermodulation product is positioned in the centre of the pass band. + +NOTE 1: The lowest intermodulation product corresponds to the 4th and 3rd order for the GSM 900 and DCS 1800 bands, respectively. + +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.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.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.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 or XXVI, since it is already covered by the requirement in sub-clause 11.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.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.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.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.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 or band XXVI, since it is already covered by the requirement in sub-clause 11.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, XIX or XXVI, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band VII or E-UTRA | 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 | + +| | | | | | | +|-------------------------------------------------|---------------------|---------|---------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Band 7 | | | | | sub-clause 11.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.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.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.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.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. This requirement does not apply to UTRA FDD Repeater operating in band XXXII, between 1475.9 MHz and 1496 MHz, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station 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.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.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.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.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.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.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.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 receive port. | +| UTRA-FDD Band XXVI or E-UTRA Band 26 | 859 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXVI, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. For UTRA FDD Repeater operating in band V, it applies from 859 MHz to 869 MHz, while the rest is covered in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 27 | 852 - 869 MHz | +16 dBm | 2 CW carriers | 1 MHz | For UTRA FDD Repeater operating in band XXVI, it applies from 852 MHz to 859 MHz, while the rest is covered in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 28 | 758 - 803 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 29 | 717 - 728 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 30 | 2350 - 2360 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 31 | 462.5 – 467.5 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, XXI or XXXII, since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between BS and the repeater DL receive 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 [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. | | | | | | + +### 11.2.2 Minimum Requirement - Co-location with UTRA-TDD and/or E-UTRA TDD + +An additional input intermodulation requirement may be applied for the protection of FDD BS receivers when UTRA TDD and/or E-UTRA TDD is co-located with a UTRA FDD Repeater. + +The requirements in this chapter assume a 30 dB coupling loss between transmitter and receiver. + +The current state-of-the-art technology does not allow a single generic solution for co-location with UTRA-TDD on adjacent frequencies for 30dB BS-Repeater minimum coupling loss. + +However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5]. + +**Table 11.2A: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD systems** + +| Co-located other system | 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 TDD 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 | +| E-UTRA Band 44 | 703 - 803 MHz | +16 dBm | 2 CW carriers | 1 MHz | + +NOTE 1: The co-location requirements in Table 11.2A 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.2A. 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. + +## 11.3 Co-existence with other systems + +The following requirement may be applied when GSM 900, DCS 1800, PCS1900, GSM850, E-UTRA FDD, E-UTRA TDD BS and/or UTRA FDD, UTRA TDD BS operating in another frequency band and UTRA-FDD Repeaters co-exist. The requirement shall be met with the repeater operating at maximum gain. + +### 11.3.1 Minimum requirements + +For the parameters specified in table 11.3 and table 11.3A, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the lowest order intermodulation product is positioned in the centre of the pass band. + +NOTE 1: The lowest intermodulation product corresponds to the 4th and 3rd order for the GSM 900 and DCS 1800 bands, respectively. + +Table 11.3: 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.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.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.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 or band XXVI, since it is already covered by the requirement in sub-clause 11.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.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.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.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.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 or band XXVI, since it is already covered by the requirement in sub-clause 11.1. | +| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 815 - 8845 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.1. This requirement does not apply to the UL of the 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.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.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.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.1. | +| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 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.1. | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|---------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 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.1. For UTRA FDD Repeater operating in band XXXII, it applies from 1447.9 MHz to 1452 MHz, while the rest is covered in sub-clause 11.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.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.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.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.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.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.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.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. | +| UTRA-FDD Band XXVI or E-UTRA Band 26 | 814 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXVI, since it is already covered by the requirement in sub-clause 11.1. For UTRA FDD Repeater operating in band V, it applies from 814MHz to 824 MHz, while the rest is covered in sub-clause 11.1. | +| E-UTRA Band 27 | 807 - 824 MHz | -15 dBm | 2 CW carriers | 1 MHz | For UTRA FDD Repeater operating in band XXVI, this requirement applies from 807MHz to 814 MHz, while the rest is covered in sub-clause 11.1. | +| E-UTRA Band 28 | 703 - 748 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 30 | 2305 - 2315 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 31 | 452.5 - 457.5 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| NOTE 1: The co-existence requirements in Table 11.3 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.3. 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.3A: 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 | | +| E-UTRA Band 44 | 703 - 803 MHz | -15 dBm | 2 CW carriers | 1 MHz | | + +NOTE 1: The co-existence requirements in Table 11.3A 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.3A. 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. + +# 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. + +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. + +## 12.1 Minimum requirement + +The output intermodulation level shall not exceed the out of band emission or the spurious emission requirements of section 9.1 and 9.2. + +# 13 Adjacent Channel Rejection Ratio (ACRR) + +## 13.1 Definitions and applicability + +Adjacent Channel Rejection Ratio (ACRR) is the ratio of the RRC weighted gain per carrier of the repeater in the pass band to the RRC weighted gain of the repeater on an adjacent channel. + +The 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 | + +# Annex A (informative): Change History + +| TSG | Doc | CR | R | Title | Cat | Curr | New | Work Item | +|-------|-----------|------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|--------|--------------------| +| RP-31 | | | | Rel-7 version created; based on v6.4.0 | | | 7.0.0 | | +| RP-31 | RP-060100 | 0042 | 2 | Introduction of operating band III to IX requirements in 25.106 | B | 6.3.0 | 7.0.0 | TEI7 | +| RP-31 | RP-060110 | 0043 | | Correction of spurious emissions for coexistence with GSM900 in same geographic area | F | 6.3.0 | 7.0.0 | RlnImp-UMTS900 | +| RP-33 | RP-060520 | 0046 | 1 | Clean up of Spurious emissions | A | 7.0.0 | 7.1.0 | TEI5 | +| RP-33 | RP-060521 | 0049 | 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 | 0052 | 1 | Corrections to input intermodulation | A | 7.1.0 | 7.2.0 | TEI5 | +| RP-36 | RP-070370 | 0056 | | Category B spurious emission limits for UTRA Repeater | A | 7.2.0 | 7.3.0 | TEI4 | +| RP-36 | RP-070373 | 0057 | | Introduction of operating band X into the repeater specification | B | 7.2.0 | 7.3.0 | TEI7 | +| RP-39 | RP-080126 | 0058 | | Introduction of UMTS1500 requirements | B | 7.3.0 | 8.0.0 | RlnImp8-UMTS1500 | +| | | | | Minor correction to CR implementation | | 8.0.0 | 8.0.1 | | +| | | | | Update of history table | | 8.0.1 | 8.0.2 | | +| RP-42 | RP-080943 | 60 | 1 | Introduction of operating band unwanted emission | F | 8.0.2 | 8.1.0 | TEI8 | +| RP-45 | RP-080819 | 61 | | Introduction of band XII, XIII, XIV | F | 8.1.0 | 8.2.0 | TEI8 | +| RP-45 | RP-080819 | 62 | | CR to limit the scope to FDD only to 25.106 | F | 8.1.0 | 8.2.0 | TEI8 | +| RP-46 | RP-091277 | 063 | | Corrections on additional spectrum emission limits for Bands XII, XIII, XIV | F | 8.2.0 | | TEI8 | +| | | | | Automatic upgrade from previous Release | | 8.3.0 | 9.0.0 | TEI9 | +| RP-49 | RP-100925 | 064 | | Introduction of operating band XIX, XX and XXI and correction of band XI | F | 9.0.0 | 9.1.0 | TEI9 | +| RP-49 | RP-100913 | 067 | 1 | RCDE for 64QAM modulated codes for FDD Repeater | A | 9.0.0 | 9.1.0 | TEI7 | +| RP-50 | RP-101336 | 072 | | Protection of cdma and E-UTRA bands | A | 9.1.0 | 9.2.0 | TEI8 | +| RP-50 | RP-101337 | 074 | | Removal of brackets | A | 9.1.0 | 9.2.0 | TEI8 | +| RP-50 | RP-101347 | 068 | | Remove test settings for unwanted emissions from core spec | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-50 | RP-101347 | 069 | | Corrections to the symbols and abbreviations clause related to DTT requirement | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-50 | RP-101347 | 070 | | Co-existence with services in adjacent frequency bands | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-51 | RP-110352 | 0075 | - | Inclusion of E-UTRA TDD text to co-location on 25.106 | F | 9.2.0 | 10.0.0 | TEI10 | +| RP-55 | RP-120303 | 078 | 1 | Correction on the table of Regional requirements | F | 10.0.0 | 10.1.0 | TEI10 | +| RP-55 | RP-120303 | 079 | 1 | Introduction of operating frequency band XXII | B | 10.0.0 | 10.1.0 | TEI10 | +| RP-55 | RP-120303 | 080 | 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 | 082 | 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 | 085 | | Additional spurious emissions requirements for PHS | A | 10.1.0 | 10.2.0 | TEI8 | +| RP-57 | RP-121313 | 088 | 2 | Introduction of missing Spurious Emission limits and Input Intermodulation requirements towards E-UTRA FDD Band 24 | F | 10.2.0 | 10.3.0 | TEI10 | +| SP-57 | - | - | - | Update to Rel-11 version (MCC) | - | 10.3.0 | 11.0.0 | - | +| RP-58 | RP-121867 | 095 | | 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 | 096 | | 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 | 097 | | 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 | RlnImp9-UMTSLTE800 | +| RP-58 | RP-121867 | 100 | | 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 | +| SP-65 | - | - | - | Update to Rel-12 version (MCC) | - | 11.1.0 | 12.0.0 | | + +| | | | | | | | | | +|-------|-----------|-----|---|---------------------------------------------------|---|--------|--------|---------------------------------------------------------------------------------------------------------------------------------------| +| RP-66 | RP-142154 | 103 | | Update with regard to operating bands of TS25.106 | F | 12.0.0 | 12.1.0 | LTE_UTRA_SDL_BandL-Core, LTE450_Brazil-Core, LTE_WCS_b and-Core, LTE_DL_FD700-Core, LTE_APAC700-Core, LTE_e850_L B-Core, E850_UB-Core | +| SP-70 | - | - | - | Update to Rel-13 version (MCC) | - | 12.1.0 | 13.0.0 | | +| RP-75 | - | - | - | Update to Rel-14 version (MCC) | - | 13.0.0 | 14.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|--|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | | 16.0.0 | +| 2022-03 | SA#95 | | | | | Update to Rel-17 version (MCC) | | 17.0.0 | +| 2024-03 | RAN#103 | | | | | Update to Rel-18 version (MCC) | | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/25_series/25153/raw.md b/marked/Rel-18/25_series/25153/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..225def43bbaa5b5200d11c7e1ba7c3c0eb068153 --- /dev/null +++ b/marked/Rel-18/25_series/25153/raw.md @@ -0,0 +1,1839 @@ + + +# 3GPP TS 25.153 V18.0.0 (2024-03) + +*Technical Specification* + +![5G Advanced logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRA repeater conformance testing (LCR TDD) (Release 18)** + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font. The 'G' has a red signal wave icon below it, and there is a small 'TM' symbol to the right of the 'P'. + +3GPP logo + +A GLOBAL INITIATIVE + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 Frequency bands and channel arrangement ..... | 8 | +| 4.1 Frequency bands..... | 8 | +| 4.2 TX-RX frequency separation ..... | 9 | +| 4.3 Channel arrangement..... | 9 | +| 4.3.1 Channel spacing..... | 9 | +| 4.3.2 Channel raster..... | 9 | +| 4.3.3 Channel number..... | 9 | +| 5 General test conditions and declarations..... | 9 | +| 5.1 Acceptable uncertainty of Test System..... | 10 | +| 5.1.1 Measurements of test environments ..... | 10 | +| 5.1.2 Measurements of Repeater ..... | 11 | +| 5.2 Repeater test tolerances (informative)..... | 11 | +| 5.3 Interpretation of measurement results ..... | 12 | +| 5.4 Test Environment..... | 12 | +| 5.4.1 Normal test environment ..... | 12 | +| 5.4.2 Extreme test environment..... | 13 | +| 5.4.2.1 Extreme temperature..... | 13 | +| 5.4.3 Vibration..... | 13 | +| 5.4.4 Power supply ..... | 14 | +| 5.5 Selection of configurations for testing ..... | 14 | +| 5.6 Regional requirements..... | 15 | +| 5.7 Format and interpretation of tests..... | 15 | +| 5.8 Repeater configurations..... | 16 | +| 5.8.1 Power supply options ..... | 16 | +| 5.8.2 Combining of Repeaters..... | 16 | +| 6 Output power..... | 17 | +| 6.1 Definition and applicability..... | 17 | +| 6.2 Minimum Requirements..... | 17 | +| 6.3 Test purpose ..... | 17 | +| 6.4 Method of test..... | 17 | +| 6.4.1 Initial conditions ..... | 17 | +| 6.4.2 Procedure ..... | 18 | +| 6.5 Test Requirements..... | 18 | +| 7 Frequency stability..... | 18 | +| 7.1 Definition and applicability..... | 19 | +| 7.2 Minimum Requirement ..... | 19 | +| 7.3 Test purpose ..... | 19 | +| 7.4 Method of test..... | 19 | +| 7.4.1 Initial conditions ..... | 19 | +| 7.4.2 Procedure ..... | 19 | +| 7.5 Test requirements..... | 19 | +| 8 Out of band gain..... | 19 | +| 8.1 Definitions and applicability ..... | 19 | +| 8.2 Minimum requirement..... | 20 | +| 8.3 Test purpose ..... | 20 | + +| | | | +|-----------|---------------------------------------------|----| +| 8.4 | Method of test..... | 20 | +| 8.4.1 | Initial conditions ..... | 20 | +| 8.4.2 | Procedure ..... | 20 | +| 8.5 | Test requirements ..... | 21 | +| 9 | Unwanted emission ..... | 21 | +| 9.1 | Spectrum emission mask..... | 21 | +| 9.1.1 | Definition and applicability ..... | 21 | +| 9.1.2 | Minimum Requirements ..... | 21 | +| 9.1.3 | Test purpose..... | 22 | +| 9.1.4 | Method of test..... | 22 | +| 9.1.4.1 | Initial conditions ..... | 22 | +| 9.1.4.2 | Procedure..... | 22 | +| 9.1.5 | Test Requirements ..... | 23 | +| 9.2 | Spurious emissions..... | 24 | +| 9.2.1 | Definition and applicability ..... | 24 | +| 9.2.2 | Minimum Requirements ..... | 24 | +| 9.2.2.1 | Mandatory Requirements..... | 24 | +| 9.2.2.1.1 | Spurious emissions (Category A)..... | 24 | +| 9.2.2.1.2 | Spurious emissions (Category B)..... | 24 | +| 9.2.2.2 | Co-existence with GSM 900..... | 25 | +| 9.2.2.2.1 | Operation in the same geographic area ..... | 25 | +| 9.2.2.2.2 | Co-located base stations ..... | 25 | +| 9.2.2.3 | Co-existence with DCS 1800..... | 26 | +| 9.2.2.3.1 | Operation in the same geographic area ..... | 26 | +| 9.2.2.3.2 | Co-located base stations ..... | 26 | +| 9.2.2.4 | Co-existence with UTRA-FDD ..... | 26 | +| 9.2.2.4.1 | Operation in the same geographic area ..... | 26 | +| 9.2.2.4.2 | Co-located base stations ..... | 27 | +| 9.2.2.5 | Co-existence with unsynchronised TDD ..... | 27 | +| 9.2.2.5.1 | Operation in the same geographic area ..... | 27 | +| 9.2.2.5.2 | Co-located base stations..... | 28 | +| 9.2.3 | Test purpose..... | 28 | +| 9.2.4 | Method of test..... | 29 | +| 9.2.4.1 | Initial conditions ..... | 29 | +| 9.2.4.2 | Procedure..... | 29 | +| 9.2.5 | Test Requirements ..... | 29 | +| 10 | Modulation accuracy..... | 29 | +| 10.1 | Error Vector Magnitude ..... | 29 | +| 10.1.1 | Definition and applicability ..... | 29 | +| 10.1.2 | Minimum requirements ..... | 29 | +| 10.1.3 | Test purpose..... | 29 | +| 10.1.4 | Method of test..... | 30 | +| 10.1.4.1 | Initial conditions ..... | 30 | +| 10.1.4.2 | Procedure ..... | 30 | +| 10.1.5 | Test requirements ..... | 30 | +| 10.2 | Peak code domain error..... | 30 | +| 10.2.1 | Definition and applicability ..... | 30 | +| 10.2.2 | Minimum requirement..... | 30 | +| 10.2.3 | Test purpose..... | 30 | +| 10.2.4 | Method of test..... | 30 | +| 10.2.4.1 | Initial conditions ..... | 30 | +| 10.2.4.2 | Procedure ..... | 31 | +| 10.2.5 | Test requirements ..... | 31 | +| 11 | Input Intermodulation ..... | 31 | +| 11.1 | Definition and applicability..... | 31 | +| 11.2 | Minimum requirement..... | 31 | +| 11.2.1 | General requirement ..... | 31 | +| 11.2.2 | Co-location with BS in other systems ..... | 33 | +| 11.2.3 | Co-existence with other systems ..... | 36 | +| 11.3 | Test purpose ..... | 37 | + +| | | | +|-------------------------------|-------------------------------------------------------|-----------| +| 11.4 | Method of test..... | 38 | +| 11.4.1 | Initial conditions ..... | 38 | +| 11.4.2 | Procedure ..... | 38 | +| 11.5 | Test requirements ..... | 38 | +| 12 | Output Intermodulation..... | 38 | +| 12.1 | Definition and applicability..... | 38 | +| 12.2 | Minimum requirements..... | 38 | +| 12.3 | Test purpose ..... | 38 | +| 12.4 | Method of test..... | 39 | +| 12.4.1 | Initial conditions ..... | 39 | +| 12.4.2 | Procedures ..... | 39 | +| 12.5 | Test requirements ..... | 39 | +| 13 | Adjacent Channel Rejection Ratio (ACRR) ..... | 40 | +| 13.1 | Definitions and applicability ..... | 40 | +| 13.2 | Minimum Requirements..... | 40 | +| 13.3 | Test purpose ..... | 40 | +| 13.4 | Method of test..... | 40 | +| 13.4.1 | Initial conditions ..... | 40 | +| 13.4.2 | Procedure ..... | 41 | +| 13.5 | Test Requirements..... | 41 | +| 14 | Timing Accuracy..... | 41 | +| 14.1 | Definition and applicability..... | 41 | +| 14.2 | Minimum requirements..... | 41 | +| 14.3 | Test purpose ..... | 42 | +| 14.4 | Method of test..... | 42 | +| 14.4.1 | Initial conditions ..... | 42 | +| 14.4.2 | Procedure ..... | 43 | +| 14.5 | Test Requirements..... | 43 | +| Annex A (normative): | Repeater measurement system set-up ..... | 45 | +| A.1 | Maximum output power..... | 45 | +| A.2 | Frequency stability..... | 45 | +| A.3 | Out of band gain..... | 45 | +| A.4 | Unwanted emission: Spectrum emission mask..... | 45 | +| A.5 | Unwanted emission: Spurious emission ..... | 46 | +| A.6 | Modulation Accuracy: Error Vector Magnitude..... | 46 | +| A.7 | Modulation Accuracy: Peak Code Domain Error ..... | 46 | +| A.8 | Input inter modulation..... | 46 | +| A.9 | Output Intermodulation..... | 47 | +| A.10 | Timing Accuracy..... | 47 | +| Annex B (informative): | Derivation of Test Requirements ..... | 48 | +| Annex C (informative): | Acceptable uncertainty of Test Equipment ..... | 49 | +| Annex D (informative): | Change history..... | 50 | + +# --- 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 LCR TDD Repeaters. These have been derived from, and are consistent with the LCR TDD Repeater specifications defined in TS 25.116. + +This document establishes the minimum RF characteristics of the LCR TDD Repeater. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.105: “Base Station (BS) radio transmission and reception (TDD)”. +- [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.142: “Base station conformance testing (TDD)”. +- [12] 3GPP TS 25.106: “UTRA Repeater; Radio transmission and reception”. +- [13] 3GPP TS 25.116: “LCR TDD Repeater; 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: + +**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. + +**Pass band:** the Repeater can have one or several pass bands. The pass band is the frequency range that the Repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal 5 MHz channels. If they are not consecutive each subset of channels shall be considered as an individual pass band. + +**Repeater:** a device that receives, amplifies and transmits the radiated or conducted RF carrier both in the down-link direction (from the base station to the mobile area) and in the up-link direction (from the mobile to the base station). + +**Up-link:** signal path where mobile transmits and base station receives. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-------------------------|----------------------------------------------------------------------------------------| +| BW Channel | Channel bandwidth | +| BW Config | Transmission bandwidth configuration, expressed in MHz. | +| BW Meas | Measurement bandwidth | +| BW Signal | Bandwidth of the repeater input signal filling the repeater pass band | +| F DL_low | The lowest frequency of the downlink operating band | +| F DL_high | The highest frequency of the downlink operating band | +| F UL_low | The lowest frequency of the uplink operating band | +| F UL_high | The highest frequency of the uplink operating band | +| f _offset_PB | Distance from the channel edge frequency of the first or last channel in the pass band | +| N DL | Downlink LARFCN | +| N offs-DL | Offset used for calculating downlink LARFCN | +| N offs-UL | Offset used for calculating uplink LARFCN | +| N RB | Transmission bandwidth configuration, expressed in units of resource blocks | +| N UL | Uplink LARFCN | +| P max | Maximum output power | +| P out | Output power | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|-------------------------------------------------| +| BTS | Base Transceiver Station | +| CW | Continuous Wave (unmodulated signal) | +| EVM | Error Vector Magnitude | +| FDD | Frequency Division Duplex | +| FFS | For Further Study | +| IMT2000 | International Mobile Telecommunication-2000 | +| ITU | International Telecommunication Union | +| MS | Mobile Station | +| RF | Radio Frequency | +| TDD | Time Division Duplex | +| LARFCN | LCR TDD Absolute Radio Frequency Channel Number | +| UMTS | Universal Mobile Telecommunication System | +| UTRA | Universal Terrestrial Radio Access | + +# --- 4 Frequency bands and channel arrangement + +## 4.1 Frequency bands + +UTRA/TDD is designed to operate in the following bands; + +- a) 1900 - 1920 MHz: Uplink and downlink transmission +2010 - 2025 MHz Uplink and downlink transmission +- b) 1850 - 1910 MHz Uplink and downlink transmission +1930 - 1990 MHz Uplink and downlink transmission +- c) 1910 - 1930 MHz Uplink and downlink transmission +- d) 2570 - 2620 MHz Uplink and downlink transmission +- e) 2300 - 2400 MHz Uplink and downlink transmission +- f) 1880 - 1920 MHz: Uplink and downlink transmission + +Note: Deployment in existing and other frequency bands is not precluded. + +## 4.2 TX-RX frequency separation + +No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each subframe consists of 7 main timeslots where all main timeslots (at least the first one) before the single switching point are allocated DL and all main timeslots (at least the last one) after the single switching point are allocated UL. + +## 4.3 Channel arrangement + +### 4.3.1 Channel spacing + +The channel spacing is 1.6MHz, 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 carrier frequency must be a multiple of 200 kHz. + +### 4.3.3 Channel number + +The carrier frequency is designated by the UTRA absolute radio frequency channel number (UARFCN). The value of the UARFCN in the IMT2000 band is defined in the general case as follows: + +$$N_t = 5 * F \qquad 0.0 \leq F \leq 3276.6 \text{ MHz}$$ + +where F is the carrier frequency in MHz. + +# --- 5 General test conditions and declarations + +This specification applies only to LCR TDD 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 LCR TDD 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 A. + +## 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: | $\pm 5$ kPa. | +| Temperature: | $\pm 2$ degrees. | +| Relative Humidity: | $\pm 5$ %. | +| DC Voltage: | $\pm 1,0$ %. | +| AC Voltage: | $\pm 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 Maximum output power | $\pm 0,7$ dB | | +| 7 Frequency error | $\pm 12$ Hz | Measurement results of $\pm 500$ Hz | +| 8 Out of band gain | $\pm 0,5$ dB
Calibration of test set-up shall be made without D.U.T. in order to achieve the accuracy | | +| 9.1 Spectrum emission mask | $\pm 1,5$ dB | | +| 9.2 Spurious emissions | $\pm 2,0$ dB for BS and coexistence bands for results $> -60$ dBm
$\pm 3,0$ dB for results $< -60$ dBm

Outside above range:
$f \leq 2,2$ GHz: $\pm 1,5$ dB
$2,2$ GHz $< f \leq 4$ GHz: $\pm 2,0$ dB
$f > 4$ GHz: $\pm 4,0$ dB | | +| 10.1 Error vector magnitude | $\pm 2,5$ % (single code applied)

( $\pm 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 | $\pm 1,1$ dB

Formula: RSS measurement error and impedance mismatch error

(using $\pm 1,0$ dB measurement error and $\pm 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 | +| 11 Input intermodulation Characteristics | $\pm 1,2$ dB

Formula: RSS CW1 level error, 2 x CW2 level error, and measurement error (using all errors = $\pm 0,5$ dB) | | +| 12 Output Intermodulation | The value below applies to the setting of the interference signal level only and is unrelated to the measurement uncertainty of the tests (9.1 and 9.2) which have to be carried out in the presence of the interference signal.

$\pm 1$ dB | The uncertainty of the interferer has double the effect on the result due to the frequency offset. | +| 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 Maximum output power | 0,7 dB | | +| 9.1 Spectrum emission mask | 1,5 dB | 0 dB test tolerance for the additional Band II, IV and V 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 | | +| 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 shared risk principle. + +The Shared 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 equipment 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. + +This procedure will ensure that a Test System not compliant with subClause 4.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 4.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 under any combination of conditions between the minimum and maximum limits 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: + +- The equipment class for the equipment under test, as defined in IEC 60721-3-3 [2]. +- The equipment class for the equipment under test, as defined in IEC 60721-3-4 [3]. +- For equipment that does not comply to the mentioned classes, the relevant classes from IEC 60 721 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 this TS. 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 environmental test equipment and methods of inducing the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-1 [4], Environmental Testing, Part 2: Tests - Tests A: Cold. The equipment shall be maintained at the stabilized condition for the duration of the test sequence. + +##### Maximum temperature: + +- The test shall be performed with 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-2 [5] (Environmental Testing, Part 2: Tests - Tests Bd Dry heat). The equipment shall be maintained at the stabilized condition for the duration of the test sequence. + +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 manufacturers 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 [8], Environmental Testing, Part 2: Tests - Test Fc and guidance: Vibration (Sinusoidal). Other environmental conditions shall be within the ranges specified in subClause 4.4.1, Normal test environment. + +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 the 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 a steady state minimum and maximum limit declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [4] Test Ab/Ad: Cold and IEC 60 068-2-2 [5] 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 a steady state minimum and maximum limit declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [4] Test Ab/Ad: Cold and IEC 60 068-2-2 [5] Test Bb/Bd: Dry Heat. + +## 5.5 Selection of configurations for testing + +Measurements shall be performed within the time slots under test as specified individually for each test within the subclause " Procedure ". + +Most tests in this TS 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.153 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 | Up-link to down-link frequency separation | The requirement is applied according to what frequency bands in clause 5.1 that are supported by the Repeater. | +| 4.3 | Channel arrangement | The requirement is applied according to what frequency bands in clause 5.1 that are supported by the Repeater. | +| 6 | 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 | Spectrum emission mask | The mask specified may be mandatory in certain regions. In other regions this mask may not be applied. | +| 9.2.2.1.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.1.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.2.1 | Co-existence with GSM900 - Operation in the same geographic area | This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS in geographic areas in which both GSM 900 and UTRA are deployed. | +| 9.2.2.2.2 | Co-existence with GSM900 - Co-located base stations | This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and UTRA BS are co-located. | +| 9.2.2.3.1 | Co-existence with DCS1800 - Operation in the same geographic area | This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS in geographic areas in which both DCS 1800 and UTRA are deployed. | +| 9.2.2.3.2 | Co-existence with DCS1800 - Co-located base stations | This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and UTRA BS are co-located. | +| 9.2.2.4.1 | Co-existence with UTRA FDD - Operation in the same geographic area | This requirement may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD are deployed. | +| 9.2.2.4.2 | Co-existence with UTRA FDD - Co-located base stations | This requirement may be applied for the protection of UTRA-FDD BS receivers when UTRA-TDD BS and UTRA FDD BS are co-located. | +| 9.2.2.5.1 | Co-existence with unsynchronised TDD - Operation in the same geographic area | This requirement may be applied for the protection of TDD BS receivers in geographic areas in which unsynchronised TDD is deployed. | +| 9.2.2.5.2 | Co-existence with unsynchronised TDD - Co-located base stations | This requirement may be applied for the protection of TDD BS receivers when unsynchronised TDD BS are co-located. | +| 11.2.2 | Input intermodulation: Co-location with 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 LCR TDD Repeaters are co-located. | +| 11.2.3 | Input Intermodulation: Co-existence with other systems | These requirements may apply in geographic areas in which both LCR TDD Repeater and GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD operating in another frequency band are deployed. | + +## 5.7 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 4.3 Interpretation of measurement results. + +## 5.8 Repeater configurations + +### 5.8.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.8.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 + +![Diagram of a repeater configuration showing two repeaters connected in parallel between two combiner/splitter units. The input and output are labeled as 'Test port'. The connections between the combiner/splitter and the repeaters are labeled as 'Antenna connector'.](bd4c85f71b8f5e06d935a6240b6dab56_img.jpg) + +The diagram illustrates a repeater configuration. On the left, a 'Test port' is connected to a 'Combiner / Splitter' block. From this block, two parallel lines lead to two 'Repeater' blocks. These lines are labeled 'Antenna connector' at their connection points to the repeaters. After passing through the repeaters, the two parallel lines are connected to another 'Combiner / Splitter' block. From this second block, a single line leads to another 'Test port' on the right. Vertical dashed lines are drawn through the 'Antenna connector' labels and the repeater blocks. + +Diagram of a repeater configuration showing two repeaters connected in parallel between two combiner/splitter units. The input and output are labeled as 'Test port'. The connections between the combiner/splitter and the repeaters are labeled as 'Antenna connector'. + +Figure 5.1: Example of repeater configuration + +# 6 Output power + +Output power, $P_{out}$ , of the repeater is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter. + +Rated output power, $PRAT$ , of the repeater is the mean power level per carrier at maximum repeater gain that the manufacturer has declared to be available at the antenna connector. + +## 6.1 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.2 Minimum Requirements + +The requirements shall apply at maximum gain, with LCR TDD signals in the pass band of the repeater, at levels that produce the maximum rated output power per channel. + +When the power of all signals is increased by 10 dB, compared to the power level that produce the maximum rated output power, the requirements shall still be met. + +In normal conditions, the Repeater maximum output power shall remain within limits specified in Table 6.1 relative to the manufacturer's rated output power. + +**Table 6.1: Repeater output power; normal conditions** + +| Rated output power | Limit | +|--------------------|-----------------| +| $P \geq 31$ dBm | +2 dB and -2 dB | +| $P < 31$ dBm | +3 dB and -3 dB | + +In extreme conditions, the Repeater maximum output power shall remain within the limits specified in Table 6.2 relative to the manufacturer's rated output power. + +**Table 6.2: Repeater output power; extreme conditions** + +| Rated output power | Limit | +|--------------------|---------------------| +| $P \geq 31$ dBm | +2,5 dB and -2,5 dB | +| $P < 31$ dBm | +4 dB and -4 dB | + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges of conditions defined as normal. + +## 6.3 Test purpose + +To verify that the Repeater maximum output power is within the limit specified in 6.1.2. + +## 6.4 Method of test + +### 6.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.4.2 Procedure + +- 1) Set the signal generator to transmit a signal according to table 6.3. + +**Table 6.3: Parameters of the transmitted signal for output power test** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| 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) | + +- 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.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.4: Repeater output power; normal conditions** + +| Rated output power | Limit | +|--------------------|---------------------| +| $P \geq 31$ dBm | +2,7 dB and -2,7 dB | +| $P < 31$ dBm | +3,7 dB and -3,7 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.5: Repeater output power; extreme conditions** + +| Rated output power | Limit | +|--------------------|---------------------| +| $P \geq 31$ dBm | +3,2 dB and -3,2 dB | +| $P < 31$ dBm | +4,7 dB and -4,7 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$ 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 signal generator equipment to the Repeater input port. +- 3) Connect the signal analyser to the Repeater output port.. + +### 7.4.2 Procedure + +- 1) Set the signal generator to transmit one signal according to table 7.1. + +**Table 7.1: Parameters of the transmitted signal for Frequency stability test** + +| 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 | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| BS output power setting | PRAT | +| Data content of DPCH | real life (sufficient irregular) | + +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain. +- 3) 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 requirement + +The intended use of a repeater in a system is to amplify the in band signals and not to amplify the out of band emission of the donor base station. + +In the intended application of the repeater, the out of band gain is less than the donor coupling loss. + +The repeater minimum donor coupling loss shall be declared by the manufacturer. This is the minimum required attenuation between the donor BS and the repeater for proper repeater operation. + +The gain outside the pass band shall not exceed the maximum level specified in table 8.1, where: + +- $f\_offset$ is the distance from the centre frequency of the first or last channel within the pass band. + +**Table 8.1: Out of band gain limits 1** + +| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain | +|----------------------------------------------------------|--------------| +| $1,0 \leq f\_offset < 1,8$ MHz | 60 dB | +| $1,8 \leq f\_offset < 5,8$ MHz | 45 dB | +| $5,8 \leq f\_offset < 10,8$ MHz | 45 dB | +| $10,8$ MHz $\leq f\_offset$ | 35 dB | + +For $10,8$ MHz $\leq f\_offset$ the out of band gain shall not exceed the maximum gain of table 8.2 or the maximum gain stated in table 8.1 whichever is lower. + +**Table 8.2: Out of band gain limits 2** + +| Repeater maximum output power as in 9.1.1.1 | Maximum gain | +|-----------------------------------------------------------------------------|---------------------------------------------------------------------| +| $P < 31$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $31$ dBm $\leq P < 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $P \geq 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss - ( $P-43$ dBm) | +| NOTE 1: The out of band gain is considered with $10,8$ 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 by the minimum requirements. + +## 8.4 Method of test + +### 8.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) $f\_offset\_CW$ is the offset between the outer channel edge frequency of the outer channel in the pass band and a CW-signal. +- 3) The test shall be performed with an $f\_offset\_CW$ of 1 MHz, 1.8 MHz, 5.8 MHz, 10.8 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. + +### 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 | +|----------------------------------------------------------|--------------| +| $1,0 \leq f\_offset < 1,8$ MHz | 60,5 dB | +| $1,8 \leq f\_offset < 5,8$ MHz | 45,5 dB | +| $5,8 \leq f\_offset < 10,8$ MHz | 45,5 dB | +| $10,8$ 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 | Maximum gain | +|------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| $P < 31$ dBm | Out of band gain $\leq$ minimum donor coupling loss + 0,5 dB | +| $31$ dBm $\leq P < 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss + 0,5 dB | +| $P \geq 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss – (P-43dBm) + 0,5 dB | +| NOTE: The donor coupling loss is considered with $10,8$ MHz $\leq f\_offset$ | | + +# 9 Unwanted emission + +## 9.1 Spectrum emission mask + +### 9.1.1 Definition and applicability + +The spectrum emission mask specifies the limit of the transmitter out of band emissions at frequency offsets from the assigned channel frequency of the wanted signal between 0,8 MHz and 4 MHz. + +The mask defined in Table 9.1 to 9.3 may be mandatory in certain regions. In other regions this mask may not be applied. + +### 9.1.2 Minimum Requirements + +For regions where this subclause applies, the requirement shall be met by LCR TDD repeater transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in tables 9.1 to 9.3 in the frequency range of $f\_offset$ from 0.815 MHz to $f\_offset_{max}$ from the carrier frequency, where: + +- $f\_offset$ is the separation between the carrier frequency and the centre of the measurement filter +- $f\_offset_{max}$ is either 4 MHz or the offset to the UMTS Tx band edge as defined in subclause 4.2, whichever is the greater. + +**Table 9.1: Spectrum emission mask values, maximum output power $P \geq 34$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | -20 dBm | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $-20\text{dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | -28 dBm | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm | 1 MHz | + +**Table 9.2: Spectrum emission mask values, maximum output power $26 \leq P < 34$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | P-54 dB | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $P - 54\text{dB} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | P-62 dB | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{\max}$ | P - 47 dB | 1 MHz | + +**Table 9.3: Spectrum emission mask values, maximum output power $P < 26$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | -28 dBm | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $-28\text{dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | -36 dBm | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -21 dBm | 1 MHz | + +NOTE: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +### 9.1.3 Test purpose + +The purpose of this test is to verify that the Repeater meet the spectrum emission requirements as specified in TS 25.116. + +### 9.1.4 Method of test + +#### 9.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. + +#### 9.1.4.2 Procedure + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator(s) to generate signal(s) in accordance to table 9.4, at level(s) which produce the manufacturer specified maximum output power at maximum gain. + +**Table 9.4: Parameters of the transmitted signal for spectrum emission mask testing** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| 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) | + +- 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. + +### 9.1.5 Test Requirements + +The spectrum emissions measured according to subclause 9.1.4.2 shall be within the mask defined in the table 9.5 to 9.7. + +**Table 9.5: Spectrum emission mask values, maximum output power $P \geq 34$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | -18.5 dBm | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $-18.5\text{dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | -26.5 dBm | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -11.5 dBm | 1 MHz | + +**Table 9.6: Spectrum emission mask values, maximum output power $26 \leq P < 34$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | $P - 52.5 \text{ dB}$ | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $P - 52.5\text{dB} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | $P - 60.5 \text{ dB}$ | 30 kHz | +| $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 45.5 \text{ dB}$ | 1 MHz | + +**Table 9.7: Spectrum emission mask values, maximum output power $P < 26$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | -26.5 dBm | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | $-26.5\text{dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{dB}$ | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | -34.5 dBm | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -19.5 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 base station RF output port. + +The requirements shall apply whatever the type of transmitter considered (single carrier or multi carrier). It applies for all transmission modes foreseen by the manufacturer's. + +For 1.28 Mcps TDD option, either requirement applies at frequencies within the specified frequency ranges which are more than 4 MHz under the first carrier frequency used or more than 4 MHz above the last carrier frequency used. + +Unless otherwise stated, all requirements are measured as mean power. + +### 9.2.2 Minimum Requirements + +#### 9.2.2.1 Mandatory Requirements + +The requirements of either subclause 9.2.2.1.1 or subclause 9.2.2.1.2 shall apply. + +##### 9.2.2.1.1 Spurious emissions (Category A) + +The following requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [6], are applied. + +The power of any spurious emission shall not exceed the maximum level given in Table 9.8. + +**Table 9.8: LCR TDD repeater Mandatory spurious emissions limits, Category A** + +| Band | Minimum requirement | 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 | | +| NOTE 1: Bandwidth as in ITU SM.329 [6], s4.1 | | | | | +| NOTE 2: Upper frequency as in ITU SM.329 [6], s2.5 table 1 | | | | | + +NOTE: only the measurement bands are different according to the occupied bandwidth. + +##### 9.2.2.1.2 Spurious emissions (Category B) + +The following requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329-9 [6], are applied. + +The power of any spurious emission shall not exceed the maximum levels given in Table 9.9. + +**Table 9.9: LCR TDD repeater Mandatory spurious emissions limits, Category B** + +| Band | Maximum Level | Measurement Bandwidth | Notes | +|------------------------------|---------------|-----------------------|--------| +| 9kHz - 150kHz | -36 dBm | 1 kHz | Note 1 | +| 150kHz - 30MHz | - 36 dBm | 10 kHz | Note 1 | +| 30MHz - 1GHz | -36 dBm | 100 kHz | Note 1 | +| 1GHz
↔
Fl -10 MHz | -30 dBm | 1 MHz | Note 1 | +| Fl -10MHz
↔
Fu +10 MHz | -15 dBm | 1 MHz | Note 2 | +| Fu +10 MHz
↔
12.5 GHz | -30 dBm | 1 MHz | Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1 +NOTE 2: Specification in accordance with ITU-R SM.329 [6], s4.1 +NOTE 3: Bandwidth as in ITU-R SM.329-9, s4.1. Upper frequency as in ITU-R SM.329-9, s2.5 table 1 + +Fl: Lower frequency of the band in which TDD operates + +Fu: Upper frequency of the band in which TDD operates + +#### 9.2.2.2 Co-existence with GSM 900 + +##### 9.2.2.2.1 Operation in the same geographic area + +This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS receivers in geographic areas in which both GSM 900 and UTRA are deployed. + +The power of any spurious emission shall not exceed the maximum level given in Table 9.10. + +**Table 9.10: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of GSM 900 MS and GSM 900 BTS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------|---------------|-----------------------|------| +| 876 - 915 MHz | -61 dBm | 100 kHz | | +| 921 - 960MHz | -57 dBm | 100 kHz | | + +##### 9.2.2.2.2 Co-located base stations + +This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and UTRA BS are co-located. + +The power of any spurious emission shall not exceed the maximum level given in table 9.11. + +**Table 9.11: LCR TDD repeater Spurious emissions limits for protection of the GSM 900 BTS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------|---------------|-----------------------|------| +| 876 - 915 MHz | -98 dBm | 100 kHz | | + +#### 9.2.2.3 Co-existence with DCS 1800 + +##### 9.2.2.3.1 Operation in the same geographic area + +This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS receivers in geographic areas in which both DCS 1800 and UTRA are deployed. + +The power of any spurious emission shall not exceed the maximum level given in table 9.12. + +**Table 9.12: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1785 MHz | -61 dBm | 100 kHz | | +| 1805 - 1880MHz | -47 dBm | 100 kHz | | + +**Table 9.12a: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver operating in 1710-1755 MHz/1805-1850 MHz** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1755 MHz | -61 dBm | 100 kHz | | +| 1805 - 1850MHz | -47 dBm | 100 kHz | | + +##### 9.2.2.3.2 Co-located base stations + +This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and UTRA BS are co-located. + +The power of any spurious emission shall not exceed the maximum level given in table 9.13. + +**Table 9.13: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when co-located with DCS 1800 BTS** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1785 MHz | -98 dBm | 100 kHz | | + +**Table 9.13a: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when co-located with DCS1800 BTS** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1755 MHz | -98 dBm | 100 kHz | | + +#### 9.2.2.4 Co-existence with UTRA-FDD + +##### 9.2.2.4.1 Operation in the same geographic area + +This requirement may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD operating in bands specified in Table 9.11 are deployed. + +For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.11. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz. + +The power of any spurious emission shall not exceed the maximum level given in table 9.14. + +**Table 9.14: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of UTRA-FDD** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|------| +| 1920 - 1980 MHz | -43 dBm (*) | 3,84 MHz | | +| 2110 - 2170 MHz | -52 dBm | 1 MHz | | +| 2500 - 2570 MHz | -43 dBm(**) | 3,84 MHz | | +| 2620 - 2690 MHz | -52 dBm | 1 MHz | | +| NOTE* For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. | | | | +| NOTE ** For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6 MHz below the lowest TDD carrier used, whichever is lower. | | | | + +NOTE: The requirements in Table 9.14 are based on a coupling loss of 70 dB between LCR TDD repeater and FDD Wide Area base stations. + +##### 9.2.2.4.2 Co-located base stations + +This requirement may be applied for the protection of UTRA-FDD BS receivers when UTRA-TDD BS and UTRA FDD BS are co-located. + +For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.12. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz. + +The power of any spurious emission shall not exceed the maximum level given in table 9.15. + +**Table 9.15: LCR TDD repeater Spurious emissions limits for BS co-located with UTRA-FDD** + +| Band | Maximum Level | Measurement Bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| 1920 - 1980 MHz | -80 dBm (*) | 3,84 MHz | +| 2110 - 2170 MHz | -52 dBm | 1 MHz | +| 2500 - 2570 MHz | - 80 dBm(**) | 3,84 MHz | +| 2620 - 2690 MHz | -52 dBm | 1 MHz | +| NOTE * For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. | | | +| NOTE ** For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6MHz below the lowest TDD carrier used, whichever is lower. | | | + +NOTE: The requirements in Table 9.15 are based on a minimum coupling loss of 30 dB between LCR TDD repeater and UTRA-FDD base stations. + +#### 9.2.2.5 Co-existence with unsynchronised TDD + +##### 9.2.2.5.1 Operation in the same geographic area + +This requirement may be applied for the protection of TDD BS receivers in geographic areas in which unsynchronised TDD is deployed. + +In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission shall not exceed the limits specified in table 9.16, otherwise the limits in table 9.17 shall apply. + +**Table 9.16: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised 1,28 Mcps TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-----------------|---------------|-----------------------| +| 1900 - 1920 MHz | -39 dBm | 1,28 MHz | +| 2010 - 2025 MHz | -39 dBm | 1,28 MHz | +| 2300 - 2400 MHz | -39 dBm | 1,28 MHz | +| 2570 - 2620 MHz | -39 dBm | 1,28 MHz | +| 1880 – 1920 MHz | -39 dBm | 1,28 MHz | + +**Table 9.17: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-----------------|---------------|-----------------------| +| 1900 - 1920 MHz | -39 dBm | 3,84 MHz | +| 2010 - 2025 MHz | -39 dBm | 3,84 MHz | +| 2570 - 2620 MHz | -39 dBm | 3,84 MHz | + +NOTE: The requirements in Table 9.16 and 9.17 for the LCR TDD repeater are based on a minimum coupling loss of 67 dB between LCR TDD repeater and unsynchronised TDD base stations. + +##### 9.2.2.5.2 Co-located base stations + +This requirement may be applied for the protection of TDD BS receivers when unsynchronised TDD BS are co-located. + +In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission in case of co-location shall not exceed the limits specified in table 9.18, otherwise the limits in table 9.19 shall apply. + +**Table 9.18: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised 1,28 Mcps TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| 1900 - 1920 MHz | -76 dBm | 1,28 MHz | +| 2010 - 2025 MHz | -76 dBm | 1,28 MHz | +| 2300 - 2400 MHz | -76 dBm | 1,28 MHz | +| 2570 - 2620 MHz | -76 dBm | 1,28 MHz | +| 1880 - 1920 MHz | -76 dBm | 1,28 MHz | +| NOTE: The requirement applies for frequencies more than 10 MHz below or above the supported frequency range declared by the vendor. | | | + +**Table 9.19: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-----------------|---------------|-----------------------| +| 1900 - 1920 MHz | -76 dBm | 3,84 MHz | +| 2010 - 2025 MHz | -76 dBm | 3,84 MHz | +| 2570 - 2620 MHz | -76 dBm | 3,84 MHz | + +NOTE: The requirements in Table 9.18 and 9.19 for the LCR TDD repeater are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations. + +### 9.2.3 Test purpose + +The test purpose is to verify the ability of the LCR TDD repeater to limit the interference caused by unwanted transmitter effects to other systems operating at frequencies which are more than 4 MHz away from of the UTRA band used. + +### 9.2.4 Method of test + +#### 9.2.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. + +#### 9.2.4.2 Procedure + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator(s) to generate signal(s) in accordance to table 9.4, 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. + +### 9.2.5 Test Requirements + +The spurious emissions measured according to subclause 9.2.4.2 shall not exceed the limits specified in the relevant tables of 9.2.2. + +# --- 10 Modulation accuracy + +## 10.1 Error Vector Magnitude + +### 10.1.1 Definition and applicability + +The modulation accuracy is defined by the Error Vector Magnitude (EVM), which is a measure of the difference between the theoretical waveform and a modified version of the measured waveform. This difference is called the error vector. The measured waveform is modified by first passing it through a matched root raised cosine filter with bandwidth 1.28MHz and roll-off $\alpha=0.22$ . The waveform is then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing so as to minimise the error vector. The EVM result is defined as root of the ratio of the mean error vector power to the mean reference signal power expressed as a %. + +The measurement interval is one power control group (timeslot). The repeater shall operate with an ideal LCR TDD signal in the pass band of the repeater at a level, which produce the maximum rated output power per channel, as specified by the manufacturer. + +### 10.1.2 Minimum requirements + +The Error Vector Magnitude shall not be worse than 8 %. + +### 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 + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the signal analyser to the Repeater output port.. + +#### 10.1.4.2 Procedure + +- 1) Set the signal generator to transmit one signal according to table 10.1. + +**Table 10.1: Parameters of the transmitted signal for Error Vector Magnitude testing** + +| 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 | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 10 | +| Power of each DPCH | 1/10 of Base Station output power | +| Base station power | PRAT | + +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain. +- 3) Measure the Error Vector Magnitude for both paths uplink and downlink of the Repeater. + +### 10.1.5 Test requirements + +The error vector magnitude (EVM) measured according to subclause 10.1.4.2 shall not exceed 8 %. + +## 10.2 Peak code domain error + +### 10.2.1 Definition and applicability + +The code domain error is computed by projecting the error vector power onto the code domain at a specific spreading factor. The error power for each code is defined as the ratio to the mean power of the reference waveform expressed in dB. And the Peak Code Domain Error is defined as the maximum value for Code Domain Error. The measurement interval is one timeslot. + +### 10.2.2 Minimum requirement + +The peak code domain error shall not exceed -30 dB at spreading factor 16. + +### 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 + +- 1) Set-up the equipment as shown in annex A. + +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the signal analyser to the Repeater output port.. + +#### 10.2.4.2 Procedure + +- 1) Set the signal generator to transmit one signal according to table 10.2. + +**Table 10.2: Parameters of the transmitted signal for Peak Code Domain Error testing** + +| 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 | TS4, TS5 and TS6 | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 10 | +| Power of each DPCH | 1/10 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain. +- 3) Measure the Peak Code Domain Error for both paths uplink and downlink of the Repeater. + +### 10.2.5 Test requirements + +The peak code domain error measured according to subclause 10.2.4.2 shall not exceed -30 dB at spreading factor 16. + +# 11 Input Intermodulation + +The input intermodulation is a measure of the capability of the repeater to inhibit the generation of interference in the pass band, in the presence of interfering signals on frequencies other than the pass band. + +## 11.1 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. + +This test applies to uplink and downlink path of the Repeater. + +## 11.2 Minimum requirement + +### 11.2.1 General requirement + +For the parameters specified in table 11.1, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the 3rd order intermodulation product is positioned in the centre of the pass band. + +Table 11.1 specifies the parameters for two interfering signals, where: + +- $f_1$ offset is the offset from the channel edge frequency of the first or last channel in the pass band of the closer carrier. + +**Table 11.1: Input intermodulation requirement** + +| f1 offset | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|-----------------------------|----------------------------------|------------------------|------------------------------| +| 1,0 MHz | -40 dBm | 2 CW carriers | 1 MHz | + +### 11.2.2 Co-location with BS in other systems + +This additional input intermodulation requirement may be applied for the protection of TDD Repeater input when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS are co-located with an LCR TDD Repeater. + +Unless otherwise stated this requirement applies to the uplink and downlink of the repeater, at maximum gain. + +For the parameters specified in table 11.2, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the lowest order intermodulation product is positioned in the centre of the pass band. + +NOTE 1: The lowest intermodulation products correspond to the 4th and 3rd order for the GSM 900 and DCS 1800 bands, respectively. + +**Table 11.2: Input intermodulation requirements for interfering signals in co-located 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 | | +| DCS1800 | 1805 - 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| PCS1900 | 1930 - 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| GSM850 | 869 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band I or E-UTRA Band 1 | 2110 - 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band II or E-UTRA Band 2 | 1930 - 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band III or E-UTRA Band 3 | 1805 - 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band V or E-UTRA Band 5 | 869 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band VI or E-UTRA Band 6 | 875 - 885 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band VIII or E-UTRA Band 8 | 925 - 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | | + +| | | | | | | +|---------------------------------------|---------------------|---------|---------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA-FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XI or E-UTRA Band 11 | 1475.9 - 1500.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XII or E-UTRA Band 12 | 728 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 | 746 - 756 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA TDD in Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band a), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band a), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band b), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band b), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band c), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band d), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band e), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA TDD in Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band f), since it is already covered by the requirement in sub-clause 11.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | + +- NOTE 1: The co-location requirements in Table 11.2 do not apply when the repeaters pass band frequency range is adjacent to the band for 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 30dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [13]. +- NOTE 2: The Table 11.2 assumes that two operating bands, where the corresponding transmit and receive 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. + +### 11.2.3 Co-existence with other systems + +This additional input intermodulation requirement may be applied when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS operating in another frequency band co-exist with an E-UTRA FDD Repeater. + +Unless otherwise stated this requirement applies to the uplink and downlink of the repeater, at maximum gain. + +For the parameters specified in table 11.3, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the lowest order intermodulation product is positioned in the centre of the pass band. + +NOTE 1: The lowest intermodulation products correspond to the 4th and 3rd order for the GSM 900 and DCS 1800 bands, respectively. + +**Table 11.3: Input intermodulation requirements for interfering signals in co-existing 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 | | +| DCS1800 | 1710 - 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| PCS1900 | 1850 - 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| GSM850 | 824 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band I or E-UTRA Band 1 | 1920 - 1980 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band II or E-UTRA Band 2 | 1850 - 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band III or E-UTRA Band 3 | 1710 - 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band V or E-UTRA Band 5 | 824 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band VI or E-UTRA Band 6 | 815 - 850 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band VII or E-UTRA Band 7 | 2500 - 2570 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 | 880 - 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1452.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | | + +| | | | | | | +|---------------------------------------|-----------------|---------|---------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA TDD in Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band a), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band a), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band b), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band b), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band c), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band d), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band e), since it is already covered by the requirement in sub-clause 11.1. | +| UTRA TDD in Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to LCR TDD Repeater operating in band f), since it is already covered by the requirement in sub-clause 11.1. | + +NOTE 1: The co-existence requirements in Table 11.3 do not apply when the repeaters pass band frequency range is adjacent to the band for the co-existence requirement in the Table 11.3. The current state-of-the-art technology does not allow a single generic solution for co-existence. + +NOTE 2: The Table 11.3 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. + +## 11.3 Test purpose + +The purpose of this test is to verify that the Repeater meets the intermodulation characteristics requirements as specified by the minimum requirements. + +## 11.4 Method of test + +### 11.4.1 Initial conditions + +- 1) A measurement system set-up is 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 one carrier, $f_1$ , is 1 MHz outside the channel edge frequency of the first or last channel in the pass band, and the lowest order intermodulation product from the two carriers 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 + +The Input intermodulation measured according to subclause 11.4.2 shall not exceed the limits specified in the relevant tables of 11.2. + +# --- 12 Output Intermodulation + +The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. + +## 12.1 Definition and applicability + +The transmit intermodulation level is the power of the intermodulation products when a LCR TDD modulated interference signal is injected into the antenna connector at a mean power level of 30 dB lower than that of the mean power of the subject signal. + +The requirement is applicable for downlink signals. + +## 12.2 Minimum requirements + +The frequency of the interference signal shall be $\pm 1.6$ MHz, $\pm 3.2$ MHz and $\pm 4.8$ MHz offset from the subject signal. The Transmit intermodulation level shall not exceed the out of band or the spurious emission requirements of section 9.1 and 9.2. + +## 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) A measurement system set-up is shown in annex A. +- 2) Connect a signal generator to the input port of the Repeater (wanted signal). Connect a signal generator to the circulator on the output port (interfering signal) and make sure the signal generator power is directed to the repeater output port. +- 3) 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 table 12.1, at the level which produce the manufacturer specified maximum output power at maximum gain. + +**Table 12.1: Parameters of the transmitted signal for transmit intermodulation testing** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| 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) | + +- 3) Set the signal generator at the repeater output port (interference signal) to generate a signal in accordance to table 12.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 1,6\text{MHz}$ , $\pm 3,2\text{MHz}$ and $\pm 4,8\text{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 + +The mean power level of the interference signal shall be 30 dB below the mean power level of the wanted signal. + +At the frequencies of all third and fifth order intermodulation products, the Test Requirements for out of band and spurious emissions as specified in subclauses 9.1.5 (Spectrum emission mask), and 9.2.5 (Spurious emissions) shall be met. + +# 13 Adjacent Channel Rejection Ratio (ACRR) + +## 13.1 Definitions and applicability + +Adjacent Channel Rejection Ratio (ACRR) is the ratio of the RRC weighted gain per carrier of the repeater in the pass band to the RRC weighted gain of the repeater on an adjacent channel. The carrier in the pass band and in the adjacent channel shall be of the same type (reference carrier). + +The requirement shall apply to the uplink and downlink of Repeater, at maximum gain, where the donor link is maintained via antennas (over the air Repeater). + +## 13.2 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 Pmax | Channel offset from the channel edge from the first or last channel within the pass band. | ACRR limit | +|------------------------------|-------------------------------------------------------------------------------------------|------------| +| $P \geq 31$ dBm | 1,6 MHz | 33dB | +| $P \geq 31$ dBm | 3,2 MHz | 33dB | +| $P < 31$ dBm | 1,6 MHz | 20dB | +| $P < 31$ dBm | 3,2 MHz | 20dB | + +Note: For co-existence with TDD, a narrow band requirement is for further study. + +## 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 according to table 13.2. + +**Table 13.2: Parameters of the transmitted signal for ACRR test** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| 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) | + +- 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.5 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.3. + +**Table 13.3: Repeater ACRR** + +| Repeater maximum output power as in 9.1.1.1 | Channel offset from the centre frequency of the first or last channel within the pass band. | ACRR limit | +|---------------------------------------------|---------------------------------------------------------------------------------------------|------------| +| $P \geq 31$ dBm | 1,6 MHz | 32,3dB | +| $P \geq 31$ dBm | 3,2 MHz | 32,3dB | +| $P < 31$ dBm | 1,6 MHz | 19,3dB | +| $P < 31$ dBm | 3,2 MHz | 19,3dB | + +# 14 Timing Accuracy + +## 14.1 Definition and applicability + +Timing Accuracy is the repeater synchronization accuracy with NodeB, it includes the downlink ramp on/off time and uplink ramp on/off time. + +## 14.2 Minimum requirements + +The downlink gain versus time should meet the mask specified in figure 14.1. The beginning and end point of downlink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator. + +![Figure 14.1: Downlink gain ON/OFF template. The diagram shows a rectangular pulse representing gain over time. The vertical axis has two levels: 'Zero Gain' (solid line) and 'Rated Gain' (dashed line). The pulse starts at 'Zero Gain', rises to 'Rated Gain', and then falls back to 'Zero Gain'. The duration of the high-gain period is labeled 'Downlink burst without GP'. There are two '8 chips' intervals marked with double-headed arrows at the start and end of the high-gain period, indicating the transition time.](0892c0cb3b8502a44c4fe4e786be912a_img.jpg) + +Figure 14.1: Downlink gain ON/OFF template. The diagram shows a rectangular pulse representing gain over time. The vertical axis has two levels: 'Zero Gain' (solid line) and 'Rated Gain' (dashed line). The pulse starts at 'Zero Gain', rises to 'Rated Gain', and then falls back to 'Zero Gain'. The duration of the high-gain period is labeled 'Downlink burst without GP'. There are two '8 chips' intervals marked with double-headed arrows at the start and end of the high-gain period, indicating the transition time. + +Figure 14.1: Downlink gain ON/OFF template + +The uplink gain versus time should meet the mask specified in figure 14.2. The beginning and end point of uplink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator. + +![Figure 14.2: Uplink gain ON/OFF template. This diagram is identical to Figure 14.1, showing a rectangular pulse for uplink gain. The vertical axis has 'Zero Gain' (solid line) and 'Rated Gain' (dashed line). The high-gain period is labeled 'Uplink burst without GP'. Two '8 chips' intervals are marked at the start and end of the high-gain period with double-headed arrows.](031e354d9de9563c9f650e3e4fcba16d_img.jpg) + +Figure 14.2: Uplink gain ON/OFF template. This diagram is identical to Figure 14.1, showing a rectangular pulse for uplink gain. The vertical axis has 'Zero Gain' (solid line) and 'Rated Gain' (dashed line). The high-gain period is labeled 'Uplink burst without GP'. Two '8 chips' intervals are marked at the start and end of the high-gain period with double-headed arrows. + +Figure 14.2: Uplink gain ON/OFF template + +## 14.3 Test purpose + +This test verifies the ability of the LCR TDD repeater to reduce its transmit power outside of the active part of the Tx time slot (burst without guard period) to values below specified limits. This ability is needed to minimize the interference for other users receiving on the same frequency. + +## 14.4 Method of test + +### 14.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 signal analyser to the Repeater output port.. + +### 14.4.2 Procedure + +- 1) Set the signal generator to transmit one signal according to table 14.1. + +**Table 14.1: Parameters of the transmitted signal for Timing Accuracy testing** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is UpPCH,1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| 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 | + +- 2) Measure the RRC filtered mean power of the LCR TDD repeater output signal chipwise (i.e. averaged over time intervals of one chip duration) over the transmit off power period starting 8 chips before the beginning point of uplink/downlink burst, and ending 8 chips after the end point of uplink/downlink burst. + +## 14.5 Test Requirements + +The Timing Accuracy measured according to subclause 14.4.2 shall not exceed the limits specified in the relevant figures of 14.1 and 14.2. + + + +# Annex A (normative): Repeater measurement system set-up + +Example of measurement system set-ups are attached below as an informative annex. + +## A.1 Maximum output power + +![Block diagram for maximum output power measurement](1e8c50ad4fca7f315a407347dd5091cc_img.jpg) + +``` +graph LR; A[Power meter or equivalent] <--> B[Repeater under test] <--> C[LCR TDD Signal Generator] +``` + +The diagram shows a linear arrangement of three components. From left to right: a box labeled 'Power meter or equivalent', a box labeled 'Repeater under test', and a box labeled 'LCR TDD Signal Generator'. Double-headed arrows connect the 'Power meter or equivalent' to the 'Repeater under test', and the 'Repeater under test' to the 'LCR TDD Signal Generator'. + +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 + +![Block diagram for RF frequency stability measurement](080a7af02bc47cf21ebfae4e0be39745_img.jpg) + +``` +graph LR; A[Spectrum analyzer] <--> B[Repeater under test] <--> C[LCR TDD Signal Generator] +``` + +The diagram shows a linear arrangement of three components. From left to right: a box labeled 'Spectrum analyzer', a box labeled 'Repeater under test', and a box labeled 'LCR TDD Signal Generator'. Double-headed arrows connect the 'Spectrum analyzer' to the 'Repeater under test', and the 'Repeater under test' to the 'LCR TDD Signal Generator'. + +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 + +![Block diagram for out of band gain measurement](08e8bbb2a063a3935a0c649b39ade125_img.jpg) + +``` +graph LR; A[Spectrum analyser] <--> B[-30 dB precision attenuator] <--> C[Repeater under test] <--> D[-30 dB precision attenuator] <--> E[CW Signal Generator] +``` + +The diagram shows a linear arrangement of five components. From left to right: a box labeled 'Spectrum analyser', a box labeled '-30 dB precision attenuator', a box labeled 'Repeater under test', another box labeled '-30 dB precision attenuator', and a box labeled 'CW Signal Generator'. Double-headed arrows connect each adjacent pair of components. + +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 + +![Block diagram for spectrum emission mask measurement](1bc74e8f6d9201dc09d80d17653a55db_img.jpg) + +``` +graph LR; A[Spectrum analyzer] <--> B[Repeater under test] <--> C[Channel filter] <--> D[LCR TDD Signal Generator] +``` + +The diagram shows a linear arrangement of four components. From left to right: a box labeled 'Spectrum analyzer', a box labeled 'Repeater under test', a box labeled 'Channel filter', and a box labeled 'LCR TDD Signal Generator'. Double-headed arrows connect each adjacent pair of components. + +Block diagram for spectrum emission mask measurement + +**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 + +![Block diagram for Figure A.5: Measuring system set-up for unwanted emission: spurious emission. The diagram shows four blocks connected in a line from right to left: LCR TDD Signal Generator, Channel filter, Repeater under test, and Spectrum analyzer. Arrows indicate the signal flow from the generator to the analyzer.](c1278da91cbcabe32628e589ebc47418_img.jpg) + +``` +graph LR; A[LCR TDD Signal Generator] --> B[Channel filter]; B --> C[Repeater under test]; C --> D[Spectrum analyzer]; +``` + +Block diagram for Figure A.5: Measuring system set-up for unwanted emission: spurious emission. The diagram shows four blocks connected in a line from right to left: LCR TDD Signal Generator, Channel filter, Repeater under test, and Spectrum analyzer. Arrows indicate the signal flow from the generator to the analyzer. + +**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 + +![Block diagram for Figure A.6: Measuring system set-up for modulation accuracy: error vector magnitude. The diagram shows three blocks connected in a line from right to left: LCR TDD Signal Generator, Repeater under test, and Spectrum analyzer. Arrows indicate the signal flow from the generator to the analyzer.](30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg) + +``` +graph LR; A[LCR TDD Signal Generator] --> B[Repeater under test]; B --> C[Spectrum analyzer]; +``` + +Block diagram for Figure A.6: Measuring system set-up for modulation accuracy: error vector magnitude. The diagram shows three blocks connected in a line from right to left: LCR TDD Signal Generator, Repeater under test, and Spectrum analyzer. Arrows indicate the signal flow from the generator to the analyzer. + +**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 + +![Block diagram for Figure A.7: Measuring system set-up for modulation accuracy: peak code domain error. The diagram shows three blocks connected in a line from right to left: LCR TDD Signal Generator, Repeater under test, and Spectrum analyzer. Arrows indicate the signal flow from the generator to the analyzer.](cdd9c57c9c578160002ead5cdaef414d_img.jpg) + +``` +graph LR; A[LCR TDD Signal Generator] --> B[Repeater under test]; B --> C[Spectrum analyzer]; +``` + +Block diagram for Figure A.7: Measuring system set-up for modulation accuracy: peak code domain error. The diagram shows three blocks connected in a line from right to left: LCR TDD Signal Generator, Repeater under test, and Spectrum analyzer. Arrows indicate the signal flow from the generator to the analyzer. + +**Figure A.7: Measuring system set-up for modulation accuracy: peak code domain error.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.8 Input inter modulation + +![Block diagram for Figure A.8: Measuring system set-up for input inter modulation. The diagram shows three blocks connected in a line from right to left: CW Signal Generator, Repeater under test, and Spectrum analyser. Arrows indicate the signal flow from the generator to the analyser.](d99a54a2d327cbeae6f5a3abd0c978ad_img.jpg) + +``` +graph LR; A[CW Signal Generator] --> B[Repeater under test]; B --> C[Spectrum analyser]; +``` + +Block diagram for Figure A.8: Measuring system set-up for input inter modulation. The diagram shows three blocks connected in a line from right to left: CW Signal Generator, Repeater under test, and Spectrum analyser. Arrows indicate the signal flow from the generator to the analyser. + +**Figure A.8: Measuring system set-up for input inter modulation.** + +## A.9 Output Intermodulation + +![Figure A.9: Measuring system set-up for Output Intermodulation.](036ceaf207a7b289ca76e160892eb724_img.jpg) + +The diagram illustrates the measuring system set-up for Output Intermodulation. It features a 'Spectrum analyser' on the left connected to a 'circulator' (represented by a circle with a clockwise arrow). The 'circulator' is also connected to an 'attenuator' and a 'Repeater under test'. The 'attenuator' is connected to a 'Channel filter', which is in turn connected to an 'LCR TDD Signal Generator'. The 'Repeater under test' is connected to another 'Channel filter', which is connected to a second 'LCR TDD Signal Generator'. + +Figure A.9: Measuring system set-up for Output Intermodulation. + +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. + +## A.10 Timing Accuracy + +![Figure A.10: Measuring system set-up for Timing Accuracy.](a3083eec2a883ee8327b3c24174df6a9_img.jpg) + +The diagram illustrates the measuring system set-up for Timing Accuracy. It shows a 'Spectrum analyzer' on the left connected to a 'Repeater under test', which is connected to an 'LCR TDD Signal Generator' on the right. Above the 'Spectrum analyzer' and 'Repeater under test', there are two lines labeled 'Frequency reference' and 'Frame Trigger', both originating from the 'LCR TDD Signal Generator'. + +Figure A.10: Measuring system set-up for Timing Accuracy. + +Figure A.10: Measuring system set-up for Timing Accuracy. + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +# 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 4.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.116 | Test Tolerance (TT) | Test Requirement in TS 25.153 | +|---------------|------------------------|-----------------------------------------------------------------|----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| 6 | Maximum output power | In normal conditions
Table 6.1 | 0,7 dB | Formula:
Upper limit + TT
Lower limit – TT
In normal conditions refer to
Table 6.4 | +| | | In extreme conditions
Table 6.2 | 0,7dB | In extreme conditions refer to
Table 6.5 | +| 9.1 | Spectrum emission mask | Tables 9.1, 9.2 and 9.3:
"Maximum level" = X dB | 1,5 dB | Formula:
Maximum level + TT
Refer to tables 9.5, 9.6 and
9.7 | +| 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 | Formula:
Maximum level + TT
Refer to table 8.2 | +| 9.2 | Spurious emissions | Tables 9.8, to 9.19 | 0 dB | | +| 10.1 | Error Vector Magnitude | 10.1.2 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.2 Minimum requirement | 1,1 dB | Formula:
Maximum error + TT
Refer to 10.2.5 Test
requirements | +| 11 | Input intermodulation | 11.2 Minimum requirements,
and Tables 11.1 ,11.2 and
11.3 | 1,2 dB | Maximum in-band power
increase + TT
Refer to 11.5 Test
requirements. | +| 12 | Output intermodulation | 12.2 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 Output power | Not critical | Not critical | +| 9.1 Spectrum emission mask | Not critical | Not critical | +| 9.2 Spurious emissions | Not critical | Not critical | +| 11 Input intermodulation (interferer requirement) | Not critical | 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 | $\pm 1 \text{ dB}$ | Measurements in the range $-25 \text{ dB}$ to $-30 \text{ dB}$ at signal power = $P_{max}$ | +| 8 Out of band gain | | | +| 11 Input intermodulation | Not critical | Not critical | +| 12 Output intermodulation | Not critical | Not critical | +| 13 ACRR | | | +| 14 Timing Accuracy | Not critical | Not critical | + +# Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|-----------|----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2009-10 | RAN4#52 bis | R4-093748 | | | TS skeleton created from 3GPP TS template. | | 0.0.1 | +| 2010-02 | RAN4#54 | R4-100999 | | | TS with the TP approved at RAN4#52bis and RAN4#53
R4-093756 Text proposal for TS25.153: Output Power
R4-094018 Text proposal for TS25.153: Frequency Error
R4-093752 Text proposal for TS25.153: EVM
R4-093757 Text proposal for TS25.153: PCDE
R4-093755 Text proposal for TS25.153: Output Intermodulation
R4-094017 Text proposal for TS25.153: Frequency bands and channel arrangements
R4-093753 Text proposal for TS25.153: Input Intermodulation
R4-093754 Text proposal for TS25.153: Out of Band Gain
R4-093751 Text proposal for TS25.153: ACRR
R4-094019 Text proposal for TS25.153: Timing Accuracy
R4-093759 Text proposal for TS25.153: Unwanted Emissions
R4-093760 Text proposal for 25.153: Clause 1 to Clause 3
R4-094638 Text proposal for 25.153: Clause 4
R4-094768 Text proposal for 25.153: Annex A to Annex D
R4-100998 Correction of the Figure A.10 of TS 25.153 | 0.0.1 | 1.0.0 | +| 2010-03 | RAN#47 | RP-100111 | | | Presentation to TSG for approval | 1.0.0 | 1.0.0 | +| 2010-03 | RAN#47 | RP-100111 | | | Approved by TSG RAN | 1.0.0 | 10.0.0 | +| 2012-09 | SP-57 | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | SP-70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | RAN#75 | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-09 | RAN#81 | | | | | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-03 | SA#95 | | | | | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | RAN#103 | | | | | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/25_series/25215/raw.md b/marked/Rel-18/25_series/25215/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a213e7dac2e05c3d603720ad7204bbc8a553287d --- /dev/null +++ b/marked/Rel-18/25_series/25215/raw.md @@ -0,0 +1,719 @@ + + +# 3GPP TS 25.215 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical layer; Measurements (FDD) (Release 18)** + +![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 3GPP logo consists of the stylized text "3GPP" in black. Below the "G" and the first "P", there are three curved red lines representing a signal or broadcast icon. A small "TM" trademark symbol is located at the top right of the second "P". + +3GPP logo + +## --- **Keywords** + +--- + +UMTS, radio, layer 1 + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + +--- + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|-----------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and Abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Control of UE/UTRAN measurements ..... | 7 | +| 5 Measurement abilities for UTRA FDD..... | 8 | +| 5.1 UE measurement abilities..... | 8 | +| 5.1.1 CPICH RSCP..... | 9 | +| 5.1.2 PCCPCH RSCP ..... | 9 | +| 5.1.3 UTRA carrier RSSI ..... | 9 | +| 5.1.4 GSM carrier RSSI..... | 9 | +| 5.1.5 CPICH Ec/No ..... | 10 | +| 5.1.6 Transport channel BLER..... | 10 | +| 5.1.7 UE transmitted power ..... | 10 | +| 5.1.8 SFN-CFN observed time difference ..... | 11 | +| 5.1.9 SFN-SFN observed time difference ..... | 11 | +| 5.1.10 UE Rx-Tx time difference ..... | 12 | +| 5.1.11 Void ..... | 12 | +| 5.1.12 UE GPS Timing of Cell Frames for UE positioning ..... | 12 | +| 5.1.13 UE GPS code phase..... | 12 | +| 5.1.14 UE transmission power headroom..... | 12 | +| 5.1.15 UE GANSS Timing of Cell Frames for UE positioning ..... | 13 | +| 5.1.16 UE GANSS code measurements ..... | 13 | +| 5.1.17 E-UTRA RSRP..... | 13 | +| 5.1.18 Void ..... | 13 | +| 5.1.19 E-UTRA RSRQ ..... | 14 | +| 5.1.20 IEEE 802.11 Beacon RSSI ..... | 14 | +| 5.2 UTRAN measurement abilities ..... | 14 | +| 5.2.1 Received total wide band power..... | 15 | +| 5.2.2 SIR..... | 15 | +| 5.2.3 SIR error ..... | 15 | +| 5.2.4 Transmitted carrier power ..... | 16 | +| 5.2.5 Transmitted code power ..... | 16 | +| 5.2.6 Transport channel BER ..... | 16 | +| 5.2.7 Physical channel BER ..... | 16 | +| 5.2.8 Round trip time..... | 17 | +| 5.2.9 UTRAN GPS Timing of Cell Frames for UE positioning ..... | 17 | +| 5.2.10 PRACH Propagation delay..... | 17 | +| 5.2.11 Acknowledged PRACH preambles ..... | 17 | +| 5.2.12 Void ..... | 18 | +| 5.2.13 Void ..... | 18 | +| 5.2.14 SFN-SFN observed time difference ..... | 18 | +| 5.2.15 Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH
or E-HICH transmission..... | 18 | +| 5.2.16 DL Transmission Branch Load ..... | 18 | +| 5.2.17 Received scheduled E-DCH power share (RSEPS) ..... | 19 | +| 5.2.18 UTRAN GANSS Timing of Cell Frames for UE positioning..... | 19 | +| 6 Measurements for UTRA FDD..... | 19 | +| 6.1 UE measurements..... | 19 | +| 6.1.1 Compressed mode ..... | 19 | +| 6.1.1.1 Use of compressed mode for monitoring..... | 19 | + +6.1.1.2 Parameterisation of the compressed mode................................................................................................ 20 + +**Annex A (informative): Change history......................................................................................................... 23** + +# --- 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 contains the description and definition of the measurements for FDD done at the UE and network in order to support operation in idle mode and connected 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.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [2] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [3] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [4] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [5] 3GPP TS 25.215: "Physical layer - Measurements (FDD)". +- [6] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [7] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [8] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [9] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [10] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [11] 3GPP TS 25.302: "Services provided by the Physical layer". +- [12] 3GPP TS 25.303: "UE functions and interlayer procedures in connected mode". +- [13] 3GPP TS 25.304: "UE procedures in idle mode". +- [14] 3GPP TS 25.331: "RRC Protocol Specification". +- [15] 3GPP TR 25.922: "Radio Resource Management Strategies". +- [16] 3GPP TR 25.923: "Report on Location Services (LCS)". +- [17] 3GPP TR 25.401: "UTRAN Overall Description". +- [18] 3GPP TS 25.101: "UE Radio transmission and Reception (FDD)". +- [19] 3GPP TS 25.104: "UTRA (BS) FDD; Radio transmission and Reception". +- [20] 3GPP TS 25.133: " Requirements for Support of Radio Resource Management (FDD)" +- [21] 3GPP TS 25.225: " Physical layer – Measurements (TDD)". + +- [22] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification" +- [23] 3GPP TS 36.211: "E-UTRA; Physical Channels and Modulation" +- [24] 3GPP TS 36.214: "E-UTRA; Physical layer – Measurements" +- [25] IEEE 802.11, Part 11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std." + +# --- 3 Definitions and Abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**cell portion:** A geographical part of a cell for which a Node B measurement can be reported to the RNC. A cell portion is semi-static, and identical for both the UL and the DL. Within a cell, a cell portion is uniquely identified by a cell portion ID. + +Note 1: a cell portion is not necessarily analogous to actual beams used for transmission and/or reception of e.g. a DPCH at the Node B. + +Note 2: RNC may associate physical channels with cell portions. + +**DL\_DCH\_FET\_Config:** Higher layers signal this configuration parameter to indicate enhanced DCH physical layer configuration. The possible values are 0 and 1. The value 0 indicates Mode 0 configuration where DL transport channels concatenation and UL ACK/NACK signalling are not configured. The value 1 indicates Mode 1 where DL transport channel concatenation and UL ACK/NACK signalling for DL FET are configured. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|-------------------------------------------------------------------| +| BER | Bit Error Rate | +| BLER | Block Error Rate | +| Ec/No | Received energy per chip divided by the power density in the band | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| F-DPCH | Fractional Dedicated Physical Channel | +| GANSS | Galileo and Additional Navigation Satellite Systems | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| ISCP | Interference Signal Code Power | +| RL | Radio Link | +| RSCP | Received Signal Code Power | +| RSRP | Reference Signal Received Power | +| RSRQ | Reference Signal Received Quality | +| RSSI | Received Signal Strength Indicator | +| SIR | Signal to Interference Ratio | + +# --- 4 Control of UE/UTRAN measurements + +In this chapter the general measurement control concept of the higher layers is briefly described to provide an understanding on how L1 measurements are initiated and controlled by higher layers. + +L1 provides with the measurement specifications a toolbox of measurement abilities for the UE and the UTRAN. These measurements can be differentiated in different reported measurement types: intra-frequency, inter-frequency, inter-system, traffic volume, quality and UE internal measurements (see [14]). + +In the L1 measurement specifications the measurements, see chapter 5, are distinguished between measurements in the UE (the messages will be described in the RRC Protocol or MAC Protocol [22]) and measurements in the UTRAN (the messages will be described in the NBAP and the Frame Protocol). + +To initiate a specific measurement the UTRAN transmits a 'measurement control message' to the UE including a measurement ID and type, a command (setup, modify, release), the measurement objects and quantity, the reporting quantities, criteria (periodical/event-triggered) and mode (acknowledged/unacknowledged), see [14]. + +When the reporting criteria is fulfilled the UE shall answer with a 'measurement report message' to the UTRAN including the measurement ID and the results. + +In idle mode the measurement control message is broadcast in a System Information. + +Intra-frequency reporting events, traffic volume reporting events and UE internal measurement reporting events described in [14] define events which trigger the UE to send a report to the UTRAN. This defines a toolbox from which the UTRAN can choose the needed reporting events. + +# 5 Measurement abilities for UTRA FDD + +In this chapter the physical layer measurements reported to higher layers are defined. The GSM measurements are required only from the GSM capable terminals. The TDD measurements are required only from the terminals that are capable to operate in TDD mode. + +## 5.1 UE measurement abilities + +The structure of the table defining a UE measurement quantity is shown below. + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Column field | Comment | +| Definition | Contains the definition of the measurement. | +| Applicable for |

States in which RRC state according to [14] a measurement shall be possible to perform. For RRC connected mode states information is also given on the possibility to perform the measurement on intra-frequency and/or inter-frequency.

The following terms are used in the tables:
Idle = Shall be possible to perform in idle mode;
URA_PCH = Shall be possible to perform in URA_PCH;
CELL_PCH = Shall be possible to perform in CELL_PCH;
CELL_FACH = Shall be possible to perform in CELL_FACH;
CELL_DCH = Shall be possible to perform in CELL_DCH;

For all RRC connected mode states i.e. URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH
Intra appended to the RRC state = Shall be possible to perform in the corresponding RRC state on an intra-frequency cell;
Inter appended to the RRC state = Shall be possible to perform in the corresponding RRC state on an inter-frequency cell.
Inter-RAT appended to the RRC state = Shall be possible to perform in the corresponding RRC state on an inter-RAT cell.

| + +The term "antenna connector of the UE" used in this sub-clause to define the reference point for the UE measurements is defined in [18]. Performance and reporting requirements for the UE measurements are defined in [20]. + +### 5.1.1 CPICH RSCP + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Code Power, the received power on one code measured on the Primary CPICH. The reference point for the RSCP shall be the antenna connector of the UE. If Tx diversity is applied on the Primary CPICH the received code power from each antenna shall be separately measured and summed together in [W] to a total received code power on the Primary CPICH. If receiver diversity is in use by the UE, the measured CPICH RSCP value shall not be lower than the corresponding CPICH RSCP of any of the individual receive antenna branches. | +| Applicable for | Idle,
URA_PCH intra, URA_PCH inter,
CELL_PCH intra, CELL_PCH inter,
CELL_FACH intra, CELL_FACH inter,
CELL_DCH intra, CELL_DCH inter | + +### 5.1.2 PCCPCH RSCP + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Code Power, the received power on one code measured on the PCCPCH from a TDD cell. The reference point for the RSCP shall be the antenna connector of the UE.

See [21] for further details on this measurement. | +| Applicable for | Idle,
URA_PCH inter,
CELL_PCH inter,
CELL_FACH inter,
CELL_DCH inter | + +### 5.1.3 UTRA carrier RSSI + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The received wide band power, including thermal noise and noise generated in the receiver, within the bandwidth defined by the receiver pulse shaping filter. The reference point for the measurement shall be the antenna connector of the UE. If receiver diversity is in use by the UE, the measured UTRA carrier RSSI value shall not be lower than the corresponding UTRA carrier RSSI of any of the individual receive antenna branches. | +| Applicable for | CELL_DCH intra, CELL_DCH inter | + +### 5.1.4 GSM carrier RSSI + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Strength Indicator, the wide-band received power within the relevant channel bandwidth. Measurement shall be performed on a GSM BCCH carrier. The reference point for the RSSI shall be the antenna connector of the UE. | +| Applicable for | Idle,
URA_PCH inter-RAT
CELL_PCH inter-RAT
CELL_FACH inter-RAT
CELL_DCH inter-RAT | + +### 5.1.5 CPICH Ec/No + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The received energy per chip divided by the power density in the band. If receiver diversity is not in use by the UE, the CPICH Ec/No is identical to CPICH RSCP/UTRA Carrier RSSI.

Measurement shall be performed on the Primary CPICH. The reference point for the CPICH Ec/No shall be the antenna connector of the UE. If Tx diversity is applied on the Primary CPICH the received energy per chip (Ec) from each antenna shall be separately measured and summed together in [Ws] to a total received chip energy per chip on the Primary CPICH, before calculating the Ec/No. If receiver diversity is in use by the UE the measured CPICH Ec/No value shall not be lower than the corresponding CPICH RSCP/UTRA Carrier RSSI of receive antenna branch i.

| +| Applicable for |

Idle,
URA_PCH intra, URA_PCH inter,
CELL_PCH intra, CELL_PCH inter,
CELL_FACH intra, CELL_FACH inter,
CELL_DCH intra, CELL_DCH inter

| + +### 5.1.6 Transport channel BLER + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Estimation of the transport channel block error rate (BLER). The BLER estimation shall be based on evaluating the CRC of each transport block associated with the measured transport channel after RL combination. The BLER shall be computed over the measurement period as the ratio between the number of received transport blocks resulting in a CRC error and the number of received transport blocks.

When either TFCI or guided detection is used, the measurement "Transport channel BLER" may only be requested for a transport channel when the associated CRC size is non zero and at least one transport format in the associated transport format set includes at least one transport block.

When neither TFCI nor guided detection is used, the measurement "Transport channel BLER" may only be requested for a transport channel when the associated CRC size is non zero and all transport formats in the associated transport format set include at least one transport block.

The measurement "Transport channel BLER" does not apply to transport channels mapped on a P-CCPCH and a S-CCPCH. The UE shall be able to perform the measurement "Transport channel BLER" on any transport channel configured such that the measurement "Transport channel BLER" can be requested as defined in this section.

| +| Applicable for | CELL_DCH intra | + +### 5.1.7 UE transmitted power + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The sum of the total UE transmitted power on all configured uplink carriers. The reference point for the UE transmitted power shall be the antenna connector of the UE. In the case where transmissions from multiple branches take place the transmitted power for each branch shall be measured and summed together in [W].

| +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.8 SFN-CFN observed time difference + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The SFN-CFN observed time difference to cell is defined as: OFF \times 38400 + T_m, where:
T_m = (T_{UETx} - T_0) - T_{RxSFN}, given in chip units with the range [0, 1, ..., 38399] chips
T_{UETx} is the time when the UE transmits an uplink DPCCH frame.
T_0 is defined in [1].
T_{RxSFN} is the time at the beginning of the neighbouring P-CCPCH frame received most recent in time before the time instant T_{UETx} - T_0 in the UE. If the beginning of the neighbouring P-CCPCH frame is received exactly at T_{UETx} - T_0 then T_{RxSFN} = T_{UETx} - T_0 (which leads to T_m = 0).
and
OFF = (SFN - CFN_{Tx}) \bmod 256, given in number of frames with the range [0, 1, ..., 255] frames
CFN_{Tx} is the connection frame number for the UE transmission of an uplink DPCCH frame at the time T_{UETx}.
SFN is the system frame number for the neighbouring P-CCPCH frame received in the UE at the time T_{RxSFN}.
The reference point for the SFN-CFN observed time difference shall be the antenna connector of the UE.

In case the inter-frequency measurement is done with compressed mode, the UE is not required to read the cell SFN of the target inter-frequency neighbour cell and the value for the parameter OFF is always reported to be 0.
In case that the SFN measurement indicator indicates that the UE does not need to read cell SFN of the target neighbour cell, the value of the parameter OFF is always be set to 0.

| +| Applicable for | CELL_DCH intra, CELL_DCH inter | + +### 5.1.9 SFN-SFN observed time difference + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Type 1:
The SFN-SFN observed time difference to cell is defined as: OFF \times 38400 + T_m, where:
T_m = T_{RxSFNj} - T_{RxSFNi}, given in chip units with the range [0, 1, ..., 38399] chips
T_{RxSFNj} is the time at the beginning of a received neighbouring P-CCPCH frame from cell j.
T_{RxSFNi} is the time at the beginning of the P-CCPCH frame from serving cell i of most recent in time before the time instant T_{RxSFNj} in the UE. If the next neighbouring P-CCPCH frame is exactly at T_{RxSFNj} then T_{RxSFNj} = T_{RxSFNi} (which leads to T_m = 0).
and
OFF = (SFN_j - SFN_i) \bmod 256, given in number of frames with the range [0, 1, ..., 255] frames
SFN_j is the system frame number for downlink P-CCPCH frame from cell j in the UE at the time T_{RxSFNj}.
SFN_i is the system frame number for the P-CCPCH frame from serving cell i in the UE at the time T_{RxSFNi}.
The reference point for the SFN-SFN observed time difference type 1 shall be the antenna connector of the UE.

Type 2:
The relative timing difference between cell j and cell i, defined as T_{CPICHRxj} - T_{CPICHRxi}, where:
T_{CPICHRxj} is the time when the UE receives one Primary CPICH slot from cell j
T_{CPICHRxi} is the time when the UE receives the Primary CPICH slot from cell i that is closest in time to the Primary CPICH slot received from cell j.
The reference point for the SFN-SFN observed time difference type 2 shall be the antenna connector of the UE.

| +| Applicable for |

Type 1: Idle, URA_PCH intra, CELL_PCH intra, CELL_FACH intra

Type 2:
URA_PCH intra, URA_PCH inter,
CELL_PCH intra, CELL_PCH inter,
CELL_FACH intra, CELL_FACH inter
CELL_DCH intra, CELL_DCH inter

| + +### 5.1.10 UE Rx-Tx time difference + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The difference in time between the UE uplink DPCCH frame transmission and the first detected path (in time), of the downlink DPCH or F-DPCH frame from the measured radio link. Type 1 and Type 2 are defined. For Type 1, the reference Rx path shall be the first detected path (in time) amongst the paths (from the measured radio link) used in the demodulation process. For Type 2, the reference Rx path shall be the first detected path (in time) amongst all paths (from the measured radio link) detected by the UE. The reference path used for the measurement may therefore be different for Type 1 and Type 2. The reference point for the UE Rx-Tx time difference shall be the antenna connector of the UE. Measurement shall be made for each cell included in the active set. | +| Applicable for | CELL_DCH intra | + +### 5.1.11 Void + +### 5.1.12 UE GPS Timing of Cell Frames for UE positioning + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The timing between cell j and GPS Time Of Week. $T_{UE-GPSj}$ is defined as the time of occurrence of a specified UTRAN event according to GPS 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-GPSj}$ shall be the antenna connector of the UE. | +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.13 UE GPS code phase + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The whole and fractional phase of the spreading code of the $i^{th}$ GPS satellite signal. The reference point for the GPS code phase shall be the antenna connector of the UE. | +| Applicable for | Void (this measurement is not related to UTRAN/GSM signals; its applicability is therefore independent of the UE RRC state) | + +### 5.1.14 UE transmission power headroom + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | For each uplink DPCCH, UE transmission power headroom (UPH) is the ratio of the maximum UE transmission power and the DPCCH code power, and shall be calculated as following:
$UPH = P_{max, tx} / P_{DPCCH}$ where:
$P_{max, tx} = \min \{Maximum\ allowed\ UL\ TX\ Power, P_{max}\}$ is the UE maximum transmission power;
Maximum allowed UL TX Power is set by UTRAN and defined in [14];
$P_{max}$ is the UE nominal maximum output power according to the UE power class and specified in [18] table 6.1;
$P_{DPCCH}$ is the transmitted code power on the DPCCH.

The reference point for the UE transmission power headroom shall be the antenna connector of the UE. | +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.15 UE GANSS Timing of Cell Frames for UE positioning + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The timing between cell j and GANSS Time Of Day for a given GANSS system. $T_{UE-GANSS}$ is defined as the time of occurrence of a specified UTRAN event according to GANSS time for a given GANSS Id. 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-GANSS}$ shall be the antenna connector of the UE. | +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.16 UE GANSS code measurements + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The GANSS code phase and GANSS Integer code phase of the spreading code of the $i^{th}$ GANSS satellite signal. The reference point for the GANSS code phase shall be the antenna connector of the UE. | +| Applicable for | Void (this measurement is not related to UTRAN/GSM signals; its applicability is therefore independent of the UE RRC state) | + +### 5.1.17 E-UTRA RSRP + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Reference signal received power (RSRP), is defined as the linear average over the power contributions (in [W]) of the resource elements that carry cell-specific reference signals within the considered measurement frequency bandwidth.
For RSRP determination the cell-specific reference signals $R_0$ according to TS 36.211 [23] shall be used. If the UE can reliably detect that $R_1$ is available it may use $R_1$ in addition to $R_0$ to determine RSRP.

The reference point for the RSRP shall be the antenna connector of the UE.

If receiver diversity is in use by the UE, the reported value shall not be lower than the corresponding RSRP of any of the individual diversity branches. | +| Applicable for | Idle,
URA_PCH inter-RAT
CELL_PCH inter-RAT
CELL_DCH inter-RAT | + +NOTE 1: The number of resource elements within the considered measurement frequency bandwidth and within the measurement period that are used by the UE to determine RSRP is left up to the UE implementation with the limitation that corresponding measurement accuracy requirements have to be fulfilled. + +NOTE 2: The power per resource element is determined from the energy received during the useful part of the symbol, excluding the CP. + +### 5.1.18 Void + +### 5.1.19 E-UTRA RSRQ + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Reference Signal Received Quality (RSRQ) is defined as the ratio $N \times \text{RSRP} / (\text{E-UTRA carrier RSSI})$ , where $N$ is the number of resource blocks of the E-UTRA carrier RSSI measurement bandwidth. The measurements in the numerator and denominator shall be made over the same set of resource blocks.

E-UTRA Carrier Received Signal Strength Indicator (RSSI), comprises the linear average of the total received power (in [W]) observed only in certain OFDM symbols of measurement subframes, in the measurement bandwidth, over $N$ number of resource blocks by the UE from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise etc.

Unless indicated otherwise by higher layers, RSSI is measured only from OFDM symbols containing reference symbols for antenna port 0 of measurement subframes. If higher layers indicate all OFDM symbols for performing RSRQ measurements, then RSSI is measured from all OFDM symbols of the DL part of measurement subframes.

The reference point for the RSRQ shall be the antenna connector of the UE.

If receiver diversity is in use by the UE, the reported value shall not be lower than the corresponding RSRQ of any of the individual diversity branches. | +| Applicable for | Idle,
URA_PCH inter-RAT
CELL_PCH inter-RAT
CELL_DCH inter-RAT | + +### 5.1.20 IEEE 802.11 Beacon RSSI + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------| +| Definition | The IEEE 802.11 Beacon RSSI is defined in [25]. | +| Applicable for | Idle,
URA_PCH inter-RAT
CELL_PCH inter-RAT
CELL_FACH inter-RAT
CELL_DCH inter-RAT | + +## 5.2 UTRAN measurement abilities + +The structure of the table defining a UTRAN measurement quantity is shown below. + +| | | +|---------------------|---------------------------------------------| +| Column field | Comment | +| Definition | Contains the definition of the measurement. | + +The term "antenna connector" used in this sub-clause to define the reference point for the UTRAN measurements refers to the "BS antenna connector" test port A and test port B as described in [19]. The term "antenna connector" refers to Rx or Tx antenna connector as described in the respective measurement definitions. + +### 5.2.1 Received total wide band power + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The received wide band power, including noise generated in the receiver, within the bandwidth defined by the receiver pulse shaping filter. The reference point for the measurement shall be the Rx antenna connector. In case of receiver diversity the reported value shall be linear average of the power in the diversity branches. When cell portions are defined in the cell, the total received wideband power shall be measured for each cell portion. | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.2 SIR + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Type 1:
Signal to Interference Ratio, is defined as: (RSCP/ISCP) \times SF. The measurement shall be performed on the DPCCH of a Radio Link Set. In compressed mode the SIR shall not be measured in the transmission gap. The reference point for the SIR measurements shall be the Rx antenna connector. If the radio link set contains more than one radio link, the reported value shall be the linear summation of the SIR from each radio link of the radio link set. If Rx diversity is used in the Node B for a cell, the SIR for a radio link shall be the linear summation of the SIR from each Rx antenna for that radio link. When cell portions are defined in the cell, the SIR measurement shall be possible in each cell portion.

where:

RSCP = Received Signal Code Power, unbiased measurement of the received power on one code.
ISCP = Interference Signal Code Power, the interference on the received signal.
SF=The spreading factor used on the DPCCH.

Type 2:
Signal to Interference Ratio, is defined as: (RSCP/ISCP) \times SF. The measurement shall be performed on the PRACH control part. The reference point for the SIR measurements shall be the Rx antenna connector. When cell portions are defined in the cell, the SIR measurement shall be possible in each cell portion.

where:

RSCP = Received Signal Code Power, unbiased measurement of the received power on the code.
ISCP = Interference Signal Code Power, the interference on the received signal.
SF=The spreading factor used on the control part of the PRACH.

| +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.3 SIRerror + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

SIR_{error} = SIR - SIR_{target\_ave}, where:

SIR = the SIR measured by UTRAN, defined in section 5.2, given in dB.

SIR_{target\_ave} = the SIR_{target} averaged over the same time period as the SIR used in the SIR_{error} calculation. In compressed mode SIR_{target}=SIR_{cm\_target} shall be used when calculating SIR_{target\_ave}. In compressed mode the SIR_{target\_ave} shall not be calculated over the transmission gap. The averaging of SIR_{target} shall be made in a linear scale and SIR_{target\_ave} shall be given in dB.

| +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.4 Transmitted carrier power + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Transmitted carrier power, is the ratio between the total transmitted power on one DL carrier from one UTRAN access point, and the maximum transmission power possible to use on that DL carrier at this moment of time. Total transmission power is the mean power [W] on one carrier from one UTRAN access point. Maximum transmission power is the mean power [W] on one carrier from one UTRAN access point when transmitting at the configured maximum power for the cell. Measurement shall be possible on any carrier transmitted from the UTRAN access point. The reference point for the transmitted carrier power measurement shall be the Tx antenna connector. In case of Tx diversity the transmitted carrier power is the ratio between the sum of the total transmitted powers of all branches and the maximum transmission power. When cell portions are defined in the cell, the transmitted carrier power for each cell portion shall be measured and reported to higher layers. | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.5 Transmitted code power + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Transmitted code power, is the transmitted power on one channelisation code on one given scrambling code on one given carrier. For DPCH, measurement shall be possible on the DPCCH-field of any dedicated radio link transmitted from the UTRAN access point and shall reflect the power on the pilot bits of the DPCCH-field, except for the downlink DPCH slot formats 17 and 18, in which case the measurement shall be possible on the TPC-field and shall reflect the power on the TPC bits. For F-DPCH, measurement shall be possible on the TPC-field and shall reflect the power on the TPC bits. When measuring the transmitted code power in compressed mode all slots shall be included in the measurement, e.g. also the slots in the transmission gap shall be included in the measurement. The reference point for the transmitted code power measurement shall be the Tx antenna connector. In case of Tx diversity the transmitted code power for each branch shall be measured and summed together in [W]. | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.6 Transport channel BER + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The transport channel BER is an estimation of the average bit error rate (BER) of the DPDCH data of a Radio Link Set. The transport channel (TrCH) BER is measured from the data considering only non-punctured bits at the input of the channel decoder in Node B. It shall be possible to report an estimate of the transport channel BER for a TrCH after the end of each TTI of the TrCH. The reported TrCH BER shall be an estimate of the BER during the latest TTI for that TrCH. | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.7 Physical channel BER + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The Physical channel BER is an estimation of the average bit error rate (BER) on the DPCCH of a Radio Link Set. An estimate of the Physical channel BER shall be possible to be reported after the end of each TTI of any of the transferred TrCHs. The reported physical channel BER shall be an estimate of the BER averaged over the latest TTI of the respective TrCH. | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.8 Round trip time + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Round trip time (RTT), is defined as

$RTT = T_{RX} - T_{TX}$

where

T_{TX} = The time of transmission of the beginning of a downlink DPCH or F-DPCH frame to a UE. The reference point for T_{TX} shall be the Tx antenna connector.

T_{RX} = The time of reception of the beginning (the first detected path, in time) of the corresponding uplink DPCCH frame from the UE. The reference point for T_{RX} shall be the Rx antenna connector.

Measurement shall be possible on DPCH or F-DPCH for each RL transmitted from an UTRAN access point and DPDCH for each RL received in the same UTRAN access point.

| +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.9 UTRAN GPS Timing of Cell Frames for UE positioning + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

TUTRAN-GPS is defined as the time of the occurrence of a specified UTRAN event according to GPS Time Of Week. The specified UTRAN event is the beginning of the transmission of a particular frame in the cell. The reference point for TUTRAN-GPS shall be the Tx antenna connector.

| +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.10 PRACH Propagation delay + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Propagation delay is defined as one-way propagation delay as measured during PRACH access:

PRACH :

Propagation delay = (T_{RX} - T_{TX} - 2560)/2, where:

T_{TX} = The transmission time of AICH access slot (n-2-AICH transmission timing), where 0 \leq (n-2-AICH\ Transmission\ Timing) \leq 14 and AICH_Transmission_Timing can have values 0 or 1. The reference point for T_{TX} shall be the Tx antenna connector.

T_{RX} = The time of reception of the beginning (the first detected path, in time) of the PRACH message from the UE at PRACH access slot n. The reference point for T_{RX} shall be the Rx antenna connector.

| +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.11 Acknowledged PRACH preambles + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The Acknowledged PRACH preambles measurement is defined as the total number of acknowledged PRACH preambles per access frame per PRACH. This is equivalent to the number of positive acquisition indicators transmitted per access frame per AICH.

| +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +5.2.12 Void + +5.2.13 Void + +5.2.14 SFN-SFN observed time difference + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The relative timing difference between cell j and cell i, defined as T_{\text{CPICHRxj}} - T_{\text{CPICHRxi}}, where:

T_{\text{CPICHRxj}} is the time when the LMU receives the beginning of one Primary CPICH frame from cell j and

T_{\text{CPICHRxi}} is the time when the LMU receives the beginning of the Primary CPICH frame from cell i that is closest in time to the beginning of Primary CPICH frame received from cell j.

The reference point for the measurements shall be the Rx antenna connector.

| +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +5.2.15 Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission is the ratio between the total transmitted power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission on one DL carrier from one UTRAN access point, and the maximum transmission power possible to use on that DL carrier at this moment of time. Total transmission power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission is the mean power [W] of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission on one carrier from one UTRAN access point. Maximum transmission power is the mean power [W] on one carrier from one UTRAN access point when transmitting at the configured maximum power for the cell. The measurement shall be possible on any carrier transmitted from the UTRAN access point. The reference point for the measurement shall be the Tx antenna connector. In case of Tx diversity the measurement is the ratio between the sum of the total transmitted powers of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission of all branches and the maximum transmission power. When cell portions are defined in the cell, the measurement shall be performed and reported to higher layers for each cell portion.

| +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +5.2.16 DL Transmission Branch Load + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The 'DL transmission branch load' is the maximum of the transmission branch loads calculated for each branch.

A 'transmission branch load' is the ratio between the total transmitted power [W] on the considered branch and the 'maximum DL branch capability' on this branch.

The 'maximum DL branch capability' defines the maximum transmission power possible to use on that branch.

The reference point for the transmission branch load measurement shall be the TX antenna connector.

| +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.17 Received scheduled E-DCH power share (RSEPS) + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The 'Received scheduled E-DCH power share' is defined as a report of 2 values for a considered cell:

  1. 1. RSEPS: defined as a quotient:
    sum of all scheduled E-DPCCH and E-DPDCH power contributions determined in the RSEPS measurement period T=t2-t1>0 for all UEs for which this cell is the serving E-DCH cell
    divided by
    the corresponding received total wideband power value determined for this cell during T.
  2. 2. RTWP*: This is the received total wideband power (RTWP) measured for this cell as defined in section 5.2.1 but determined for the same time period T starting at t1 and ending at t2 during which RSEPS is determined.

The reference point for the RSEPS and RTWP* measurements shall be the Rx antenna connector.

When cell portions are defined in the cell, RSEPS (and RTWP*) shall be measured for each cell portion.

The sum in the numerator of RSEPS is determined under the following conditions:

  • - The contributions are summed up TTI wise and only TTIs which are ending between the time instants t1 and t2 are considered.
  • - In case a UE has not only a radio link to the considered cell but also other radio links to the same Node B ('softer handover'): It is allowed to take into account the power value combined for these radio links of the same Node B and divided by the number of combined radio links.

Note: For improved measurement performance it is possible to consider only the power contribution determined for the considered cell.

| +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.18 UTRAN GANSS Timing of Cell Frames for UE positioning + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

TUTRAN-GANSS is defined as the time of the occurrence of a specified UTRAN event according to GANSS Time Of Day. The specified UTRAN event is the beginning of the transmission of a particular frame in the cell. The reference point for TUTRAN-GANSS shall be the Tx antenna connector.

| +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# 6 Measurements for UTRA FDD + +## 6.1 UE measurements + +### 6.1.1 Compressed mode + +#### 6.1.1.1 Use of compressed mode for monitoring + +On command from the UTRAN, a UE shall monitor cells on other FDD frequencies and on other modes and radio access technologies that are supported by the UE (i.e. TDD, GSM, E-UTRA). To allow the UE to perform measurements, UTRAN shall command that the UE enters in compressed mode, depending on the UE capabilities. + +The UE capabilities define whether a UE requires compressed mode in order to monitor cells on other FDD frequencies and on other modes and radio access technologies. UE capabilities indicate the need for compressed mode separately for the uplink and downlink and for each mode, radio access technology and frequency band. + +A UE shall support compressed mode for all cases for which the UE indicates that compressed mode is required. + +A UE does not need to support compressed mode for cases for which the UE indicates that compressed mode is not required. For these cases, the UE shall support an alternative means of making the measurements. + +The UE shall support one single measurement purpose for one transmission gap pattern sequence. The measurement purpose of the transmission gap pattern sequence is signalled by higher layers. + +The following subclause provides rules to parameterise the compressed mode. + +#### 6.1.1.2 Parameterisation of the compressed mode + +In response to a request from higher layers, the UTRAN shall signal to the UE the compressed mode parameters. + +A transmission gap pattern sequence consists of consecutive occurrences of transmission gap pattern 1, where transmission gap pattern 1 consists of one or two transmission gaps. See figure 1. + +The following parameters characterise a transmission gap pattern: + +- TGSN (Transmission Gap Starting Slot Number): A transmission gap pattern begins in a radio frame, henceforward called first radio frame of the transmission gap pattern, containing at least one transmission gap slot. TGSN is the slot number of the first transmission gap slot within the first radio frame of the transmission gap pattern; +- TGL1 (Transmission Gap Length 1): This is the duration of the first transmission gap within the transmission gap pattern, expressed in number of slots; +- TGL2 (Transmission Gap Length 2): This is the duration of the second transmission gap within the transmission gap pattern, expressed in number of slots. If this parameter is not explicitly set by higher layers, then $TGL2 = TGL1$ ; +- TGD (Transmission Gap start Distance): This is the duration between the starting slots of two consecutive transmission gaps within a transmission gap pattern, expressed in number of slots. The resulting position of the second transmission gap within its radio frame(s) shall comply with the limitations of [2]. If this parameter is not set by higher layers, then there is only one transmission gap in the transmission gap pattern; +- TGPL1 (Transmission Gap Pattern Length): This is the duration of transmission gap pattern 1, expressed in number of frames; + +The following parameters control the transmission gap pattern sequence start and repetition: + +- TGPRC (Transmission Gap Pattern Repetition Count): This is the number of transmission gap patterns within the transmission gap pattern sequence; +- TGCFN (Transmission Gap Connection Frame Number): This is the CFN of the first radio frame of the first pattern 1 within the transmission gap pattern sequence. + +In addition to the parameters defining the positions of transmission gaps, each transmission gap pattern sequence is characterised by: + +- UL/DL compressed mode selection: This parameter specifies whether compressed mode is used in UL only, DL only or both UL and DL; +- UL compressed mode method: The methods for generating the uplink compressed mode gap are spreading factor division by two or higher layer scheduling and are described in [2]. This parameter does not impact the compressed mode method used when DL\_DCH\_FET\_Config is configured by higher layers; +- DL compressed mode method: The methods for generating the downlink compressed mode gap are spreading factor division by two or higher layer scheduling and are described in [2]. This parameter does not impact the compressed mode method used when DL\_DCH\_FET\_Config is configured by higher layers; +- downlink frame type: This parameter defines if frame structure type 'A' or 'B' shall be used in downlink compressed mode. The frame structures are defined in [2]; +- scrambling code change: This parameter indicates whether the alternative scrambling code is used for compressed mode method 'SF/2'. Alternative scrambling codes are described in [3]; + +- RPP: Recovery Period Power control mode specifies the uplink power control algorithm applied during recovery period after each transmission gap in compressed mode. RPP can take 2 values (0 or 1). The different power control modes are described in [4]; +- ITP: Initial Transmit Power mode selects the uplink power control method to calculate the initial transmit power after the gap. ITP can take two values (0 or 1) and is described in [4]. + +The UE shall support simultaneous compressed mode pattern sequences which can be used for different measurements. The following measurement purposes can be signalled from higher layers: + +- FDD +- TDD +- GSM carrier RSSI measurement +- Initial BSIC identification +- BSIC re-confirmation +- E-UTRA. + +The UE shall support one compressed mode pattern sequence for each measurement purpose while operating in FDD mode, assuming the UE needs compressed mode to perform the respective measurement. In case the UE supports several of the measurement purposes, it shall support in parallel one compressed mode pattern sequence for each supported measurement purpose where the UE needs compressed mode to perform the measurement. The capability of the UE to operate in compressed mode in uplink and downlink is given from the UE capabilities. + +The GSM measurements Initial BSIC identification and BSIC re-confirmation are defined in [20]. + +Higher layers will ensure that the compressed mode gaps do not overlap and are not scheduled to overlap the same frame. The behaviour when an overlap occurs is described in [11]. UE is not required to support two compressed mode gaps in a frame. + +In all cases, higher layers have control of individual UE parameters. Any pattern sequence can be stopped on higher layers' command. + +The parameters TGSN, TGL1, TGL2, TGD, TGPL1, TGPRC and TGCFN shall all be integers. + +![Diagram illustrating compressed mode pattern parameters. It shows a sequence of TG patterns (#1 to #5 and #TGPRC) and a detailed view of 'TG pattern 1' showing transmission periods, gaps (gap 1, gap 2), TGSN, TGL1, TGL2, TGD, and TGPL1.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates the structure of a compressed mode pattern. At the top, a sequence of patterns is shown: #1, #2, #3, #4, #5, and #TGPRC, each labeled 'TG pattern 1'. A callout from the first pattern provides a detailed view. This view shows a repeating sequence of 'Transmission' and 'gap' periods. 'gap 1' and 'gap 2' are explicitly labeled. The 'TGSN' (Transmission Gap Start Number) is indicated by an arrow pointing to the start of the first transmission. 'TGL1' and 'TGL2' represent the transmission gap lengths for the first and second gaps, respectively, shown as double-headed arrows. 'TGD' represents the transmission gap duration, shown as a single-headed arrow from the start of the first transmission to the start of the second. 'TGPL1' represents the transmission gap period, shown as a long double-headed arrow spanning the duration of one full cycle (transmission plus gap). + +Diagram illustrating compressed mode pattern parameters. It shows a sequence of TG patterns (#1 to #5 and #TGPRC) and a detailed view of 'TG pattern 1' showing transmission periods, gaps (gap 1, gap 2), TGSN, TGL1, TGL2, TGD, and TGPL1. + +Figure 1: Illustration of compressed mode pattern parameters + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/01/00 | RAN_05 | RP-99590 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RAN_06 | RP-99688 | 001 | 3 | Clarifications for compressed mode parameters | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 002 | - | Definition of PCCPCH RSCP | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 003 | - | Definition of observed time difference to GSM cell | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 004 | - | Measurements are done on Primary CPICH | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 005 | 1 | Physical channel BER on DPCCH | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 006 | - | Definition of SIR measurement | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 007 | 2 | Ranges and resolution of timing measurements | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 009 | 2 | Range and resolution for RF related measurements | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99689 | 010 | 2 | New subclauses: 5.1.15 - UE GPS Timing of Cell Frames for LCS; 5.2.8 UTRAN GPS Timing of Cell Frames for LCS | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 011 | - | Removal of Annex A from TS 25.215 | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 013 | - | Definition of Transmitted code power | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 014 | 2 | Range and resolution of BLER measurements | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 015 | 2 | Range and resolution of BER measurements | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 020 | - | Correction of SFN-SFN observed time difference | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99688 | 021 | 1 | CFN-SFN measurement with compressed mode | 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-000066 | 024 | 1 | Definition of Transmitted carrier power | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 025 | - | Clarification of Observed time difference to GSM cell | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 027 | - | Naming of BER/BLER mapping | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 028 | - | Minor corrections in TS 25.215 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 029 | - | Re-definition of timing measurements | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 030 | 2 | Mapping of timing measurements | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 031 | - | Removal of note in Round trip time measurement | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 033 | - | Removal of fixed gap position in 25.215 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 036 | 4 | Corrections to 25.215 compressed mode parameter list | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 037 | 3 | Definition and range of physical channel BER | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 040 | - | Clarification of CPICH measurements in Tx diversity | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 042 | 1 | UTRAN RSSI measurement | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 043 | 1 | UTRAN Propagation delay | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 044 | 2 | Correction to subclauses: 5.1.15 UE GPS Timing of Cell Frames for LCS; 5.2.8 UTRAN GPS Timing of Cell Frames for LCS, including timing mapping | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 047 | - | Removal of RSCP measurement | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000066 | 048 | - | UE BER measurement removal and clarification for use of uplink compressed mode | 3.1.1 | 3.2.0 | +| 26/06/00 | RAN_08 | RP-000270 | 049 | 1 | Propagation delay for PCPCH | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 050 | 1 | Maximum number of simultaneous compressed mode pattern sequences | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 051 | 1 | Clarification of Physical channel BER | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 052 | - | Clarification of transmitted code power | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 053 | - | Editorial correction in TS 25.215 | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 055 | - | Proposed CR for Measurements of RACH in FDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 056 | - | Proposed CR for Measurements of CPCH in FDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 057 | - | Transfer of information from TS 25.212 table 9 to TS 25.215 | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 058 | - | Correction to CM parameter list | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 062 | - | Clarification of radio link measurements in compressed mode | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 063 | - | Clarification of the Transmitted code power measurement in Tx diversity | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 064 | 1 | Removal of Range/mapping | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000270 | 066 | - | Removal of UTRAN TrCH BLER measurement | 3.2.0 | 3.3.0 | +| 23/09/00 | RAN_09 | RP-000343 | 067 | - | Insertion of UTRAN SIRerro measurement in 25.215 | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000343 | 068 | - | Reporting of UTRAN Transmitted carrier power | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000343 | 070 | - | Clarification of UTRAN SIR measurement | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000343 | 071 | - | Clarification of first significant path | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000343 | 072 | - | Clarification of radio link set as the measured object | 3.3.0 | 3.4.0 | +| 15/12/00 | RAN_10 | RP-000541 | 069 | 3 | Support of parallel compressed mode patterns | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000541 | 074 | 1 | Clarification of SIError measurement during compressed mode | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000541 | 075 | 2 | Definition of UTRAN RSSI | 3.4.0 | 3.5.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|---------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 15/12/00 | RAN 10 | RP-000541 | 076 | 1 | Clarification of GPS timing measurements | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN 10 | RP-000541 | 077 | 2 | Clarification of reference point for UE/UTRAN measurements | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN 10 | RP-000541 | 078 | 1 | Correction to measurement "Rx-Tx time difference" | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN 10 | RP-000541 | 080 | 1 | Clarifications to compressed mode usage | 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-010061 | 079 | 2 | Correction of the observed time difference to GSM measurement | 3.5.0 | 3.6.0 | +| 16/03/01 | RAN 11 | RP-010061 | 081 | - | Removal of UE SIR measurement | 3.5.0 | 3.6.0 | +| 16/03/01 | RAN 11 | RP-010061 | 082 | 1 | Correction of GSM reference | 3.5.0 | 3.6.0 | +| 16/03/01 | RAN 11 | RP-010061 | 083 | - | Correction of GPS Timing measurement | 3.5.0 | 3.6.0 | +| 16/03/01 | RAN 11 | RP-010061 | 086 | - | Correction on transport channel BLER | 3.5.0 | 3.6.0 | +| 16/03/01 | RAN 11 | RP-010072 | 085 | - | RTD measurement in UTRAN for FDD | 3.5.0 | 4.0.0 | +| 15/06/01 | RAN 12 | RP-010335 | 088 | - | Renaming of LCS measurements | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN 12 | RP-010456 | 090 | 2 | Correction the TrCH BLER measurement | 4.0.0 | 4.1.0 | +| 21/09/01 | RAN 13 | RP-010521 | 096 | - | Removal of the BLER measurement of the BCH | 4.1.0 | 4.2.0 | +| 14/12/01 | RAN 14 | RP-010740 | 098 | - | Clarification of internal measurements | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN 14 | RP-010740 | 103 | - | Clarification of P-CCPCH RSCP in 25.215 | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN 14 | RP-010740 | 105 | - | Revised definitions of CPICH Ec/No and UTRA carrier RSSI | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN 14 | RP-010745 | 099 | 2 | UE GPS code phase measurement | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN 14 | RP-010745 | 106 | 1 | UTRAN SFN-SFN observed time difference measurement | 4.2.0 | 4.3.0 | +| 08/03/02 | RAN 15 | RP-020245 | 114 | 3 | Clarification of UE measurements Applicability | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020048 | 116 | - | Correction to the definition of UTRAN GPS timing of cell frames for UE positioning | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020048 | 117 | - | Correction to the definition of UE GPS timing of cell frames for UE positioning | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN 15 | RP-020231 | 111 | 1 | Removal of channel coding option "no coding" for FDD | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN 15 | - | - | - | Raised up to v5.0.0 together with other specs. | 4.4.0 | 5.0.0 | +| 18/09/02 | RAN 17 | RP-020530 | 119 | 4 | Transmitted carrier power measurement correction | 5.0.0 | 5.1.0 | +| 18/09/02 | RAN 17 | RP-020575 | 121 | - | Measurements for observed time difference to GSM cell | 5.0.0 | 5.1.0 | +| 18/09/02 | RAN 17 | RP-020575 | 130 | - | Compressed mode limitation | 5.0.0 | 5.1.0 | +| 18/09/02 | RAN 17 | RP-020558 | 128 | - | Correction of UE SFN-SFN type 1 measurement | 5.0.0 | 5.1.0 | +| 21/12/02 | RAN 18 | RP-020842 | 131 | 1 | Received Total Wide Band Power Measurement Definition | 5.1.0 | 5.2.0 | +| 26/03/03 | RAN 19 | RP-030017 | 133 | 3 | Correction of UTRAN SIR measurement definition | 5.2.0 | 5.3.0 | +| 26/03/03 | RAN 19 | RP-030081 | 134 | 1 | Non-HSDPA power measurement | 5.2.0 | 5.3.0 | +| 23/06/03 | RAN_20 | RP-030270 | 142 | - | Correction of transmitted carrier power definition in case of Tx diversity | 5.3.0 | 5.4.0 | +| 23/06/03 | RAN_20 | RP-030274 | 143 | - | Correction of transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission definition in case of Tx diversity | 5.3.0 | 5.4.0 | +| 22/09/03 | RAN 21 | RP-030452 | 144 | 1 | Beamforming Enhancement related measurements | 5.4.0 | 5.5.0 | +| 07/01/04 | RAN_22 | - | - | - | Approved to promote to a Release 6 TS and created for M.1457 update | 5.5.0 | 6.0.0 | +| 07/01/04 | RAN 22 | RP-030726 | 145 | 2 | Beamforming Enhancement related measurements | 5.5.0 | 6.0.0 | +| 13/12/04 | RAN 26 | RP-040449 | 149 | 1 | Introduction of E-DCH | 6.0.0 | 6.1.0 | +| 14/03/05 | RAN 27 | RP-050050 | 147 | 4 | Introduction of 'DL Transmission Branch Load' measurement | 6.1.0 | 6.2.0 | +| 14/03/05 | RAN 27 | RP-050038 | 153 | 1 | Removal of TGPL2 | 6.1.0 | 6.2.0 | +| 14/03/05 | RAN 27 | RP-050092 | 154 | - | Clarification of the cell on SFN-SFN observed time difference | 6.1.0 | 6.2.0 | +| 14/03/05 | RAN 27 | RP-050088 | 155 | - | Introduction of F-DPCH without pilot field | 6.1.0 | 6.2.0 | +| 16/06/05 | RAN 28 | RP-050250 | 161 | - | Feature Clean Up: Removal of "CPCH" | 6.2.0 | 6.3.0 | +| 16/06/05 | RAN_28 | RP-050245 | 163 | - | Feature Clean Up: Removal of observed time difference to GSM cell measurement | 6.2.0 | 6.3.0 | +| 16/06/05 | RAN_28 | RP-050249 | 165 | - | Feature clean up: Removal of the 'compressed mode by puncturing' | 6.2.0 | 6.3.0 | +| 26/09/05 | RAN 29 | RP-050453 | 0166 | 1 | UE power headroom measurement | 6.3.0 | 6.4.0 | +| 26/09/05 | RAN 29 | RP-050440 | 0167 | - | Non-HS power measurement | 6.3.0 | 6.4.0 | +| 20/03/06 | RAN 31 | - | - | - | Creation of Release 7 specification (v.7.0.0) at RAN#31 | 6.4.0 | 7.0.0 | +| 29/09/06 | RAN 33 | RP-060495 | 0170 | 3 | Introduction of a Node B measurement for E-DCH RRM | 7.0.0 | 7.1.0 | +| 30/05/07 | RAN 36 | RP-070391 | 0172 | 5 | Clarification of UE measurement definitions for RX diversity | 7.1.0 | 7.2.0 | +| 11/09/07 | RAN_37 | RP-070648 | 0176 | 1 | Adding GANSS related measurements in the FDD physical layer measurements | 7.2.0 | 7.3.0 | +| 27/11/07 | RAN 38 | RP-070946 | 0177 | - | Clarification of UE measurement definitions for RX diversity | 7.3.0 | 7.4.0 | +| 04/03/08 | RAN 39 | - | - | - | Release 8 version further to RAN 39 decision | 7.4.0 | 8.0.0 | +| 28/05/08 | RAN 40 | RP-080436 | 188 | - | E-UTRA measurements for UTRA – E-UTRA interworking | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080672 | 189 | - | UPH measurement support for Enhanced Uplink for CELL_FACH state | 8.1.0 | 8.2.0 | +| 09/09/08 | RAN 41 | RP-080666 | 190 | - | Modification of RSRQ and removal of RSSI | 8.1.0 | 8.2.0 | +| 09/09/08 | RAN 41 | RP-080666 | 192 | - | Modification of RSRP definition | 8.1.0 | 8.2.0 | +| 03/03/09 | RAN 43 | RP-090232 | 194 | 1 | RSRP and RSRQ Measurement Definitions | 8.2.0 | 8.3.0 | +| 15/09/09 | RAN 45 | RP-090888 | 195 | 1 | Clarification on reference point of RSRP and RSRQ for EUTRA | 8.3.0 | 8.4.0 | +| 18/09/09 | RAN 45 | - | - | - | Release 9 created further to RAN 45 decision | 8.4.0 | 9.0.0 | +| 01/12/09 | RAN 46 | RP-091170 | 196 | 2 | Introduction of DC-HSUPA | 9.0.0 | 9.1.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|--------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 16/03/10 | RAN_47 | RP-100205 | 197 | 2 | Modification of RSRQ definition | 9.1.0 | 9.2.0 | +| 21/03/11 | SP_51 | - | - | - | Release 10 created further to SP_51 decision | 9.2.0 | 10.0.0 | +| 05/12/11 | RAN_54 | RP-111672 | 199 | - | Introduction of Uplink Closed Loop Transmit Diversity for HSPA | 10.0.0 | 11.0.0 | +| 10/09/14 | RAN_65 | RP-141480 | 201 | 1 | Introduction of DCH Enhancements | 11.0.0 | 12.0.0 | +| 10/09/14 | RAN_65 | RP-141484 | 202 | 2 | Inclusion of definition of WLAN Beacon RSSI in UMTS specifications | 11.0.0 | 12.0.0 | +| 09/03/15 | RAN_67 | RP-150361 | 200 | 2 | New E-UTRA RSRQ measurement definition | 12.0.0 | 12.1.0 | +| 07/12/15 | SP_70 | | | | Release 13 created further to SP_70 decision | 12.1.0 | 13.0.0 | + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2016-06 | RP-72 | RP-161144 | 0206 | | F | Clarification on measuring the transmitted code power for the downlink DPCH slot formats #17 and #18 | 13.1.0 | | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | | +| 2022-03 | RP-95e | - | - | - | - | Upgrade to Rel-17 version without technical change | 17.0.0 | | +| 2024-03 | RP-103 | - | - | - | - | Upgrade to Rel-18 version without technical change | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/25_series/25225/raw.md b/marked/Rel-18/25_series/25225/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..880a63e22e3643892d9b7f8bb48e63e920c904cd --- /dev/null +++ b/marked/Rel-18/25_series/25225/raw.md @@ -0,0 +1,816 @@ + + +# 3GPP TS 25.225 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical layer; Measurements (TDD) (Release 18)** + +![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. The '3' is black, 'G' is black, 'P' is black, and 'P' is black. There is a small red signal icon below the 'G' and 'P'. A small 'TM' symbol is located to the top right of the 'P'. + +3GPP logo + +## --- **Keywords** + +UMTS, radio, layer 1 + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Abbreviations ..... | 7 | +| 4 Control of UE/UTRAN measurements ..... | 7 | +| 4.1 General measurement concept ..... | 8 | +| 4.2 Measurements for cell selection/reselection ..... | 8 | +| 4.3 Measurements for Handover ..... | 8 | +| 4.4 Measurements for DCA ..... | 8 | +| 4.5 Measurements for timing advance ..... | 8 | +| 5 Measurement abilities for UTRA TDD ..... | 9 | +| 5.1 UE measurement abilities..... | 9 | +| 5.1.1 P-CCPCH RSCP..... | 10 | +| 5.1.2 CPICH RSCP..... | 10 | +| 5.1.3 Timeslot ISCP ..... | 10 | +| 5.1.4 UTRA carrier RSSI ..... | 10 | +| 5.1.5 GSM carrier RSSI..... | 11 | +| 5.1.6 SIR..... | 11 | +| 5.1.7 CPICH Ec/No ..... | 11 | +| 5.1.8 Transport channel BLER..... | 11 | +| 5.1.9 UE transmitted power..... | 12 | +| 5.1.10 SFN-SFN observed time difference ..... | 13 | +| 5.1.11 SFN-CFN observed time difference ..... | 14 | +| 5.1.12 Observed time difference to GSM cell..... | 14 | +| 5.1.13 UE GPS Timing of Cell Frames for UE positioning ..... | 15 | +| 5.1.14 Timing Advance ( $T_{ADV}$ ) for 1.28Mcps TDD..... | 15 | +| 5.1.15 UE GPS code phase..... | 15 | +| 5.1.16 UE transmission power headroom (1.28Mcps option only)..... | 16 | +| 5.1.17 UE transmission power headroom (3.84Mcps and 7.68Mcps options)..... | 16 | +| 5.1.18 E-UTRA RSRP..... | 17 | +| 5.1.19 E-UTRA RSRQ ..... | 17 | +| 5.1.20 IEEE 802.11 Beacon RSSI ..... | 18 | +| 5.2 UTRAN measurement abilities ..... | 18 | +| 5.2.1 RSCP ..... | 18 | +| 5.2.2 Timeslot ISCP ..... | 18 | +| 5.2.3 Received total wide band power..... | 18 | +| 5.2.4 SIR..... | 19 | +| 5.2.5 Transport channel BER ..... | 19 | +| 5.2.6 Transmitted carrier power ..... | 19 | +| 5.2.7 Transmitted code power ..... | 19 | +| 5.2.8 RX Timing Deviation..... | 20 | +| 5.2.9 UTRAN GPS Timing of Cell Frames for UE positioning ..... | 20 | +| 5.2.10 SFN-SFN observed time difference ..... | 20 | +| 5.2.11 Cell Sync Burst Timing..... | 21 | +| 5.2.12 Cell Sync Burst SIR..... | 21 | +| 5.2.13 Received SYNC-UL Timing Deviation for 1.28Mcps TDD..... | 22 | +| 5.2.14 Angle of Arrival (AOA) for 1.28Mcps TDD ..... | 22 | +| 5.2.15 HS-SICH reception quality..... | 22 | +| 5.2.16 Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission..... | 23 | +| 5.2.17 UpPTS interference (1.28Mcps TDD) ..... | 23 | +| Annex A (informative): Monitoring GSM from TDD: Calculation Results..... | 24 | +| A.1 Low data rate traffic using 1 uplink and 1 downlink slot (for the 3.84 Mcps option) ..... | 24 | + +A.1.1 Higher data rate traffic using more than 1 uplink and/or 1 downlink TDD timeslot ..... 25 + +A.2 Low data rate traffic using 1 uplink and 1 downlink slot (for the 1.28 Mcps option) ..... 26 + +A.2.1 Higher data rate traffic using more than 1 uplink and/or 1 downlink TDD timeslot (for 1.28Mcps TDD)..... 27 + +**Annex B (informative): Change history..... 29** + +# --- 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 contains the description and definition of the measurements done at the UE and network in TDD mode in order to support operation in idle mode and connected 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.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [2] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [3] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [4] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [5] 3GPP TS 25.215: "Physical layer measurements (FDD)". +- [6] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [7] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [8] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [9] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [10] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [11] 3GPP TS 25.302: "Services provided by the Physical layer". +- [12] 3GPP TS 25.303: "UE functions and interlayer procedures in connected mode". +- [13] 3GPP TS 25.304: "UE procedures in idle mode". +- [14] 3GPP TS 25.331: "RRC Protocol Specification". +- [15] 3GPP TR 25.922: "Radio Resource Management Strategies". +- [16] 3GPP TR 25.923: "Report on Location Services (LCS)". +- [17] 3GPP TS 25.102: "UTRA (UE) TDD; Radio transmission and Reception" +- [18] 3GPP TS 25.105: "UTRA (BS) TDD; Radio transmission and Reception" +- [19] 3GPP TS 25.123: "Requirements for Support of Radio Resources Management (TDD)" +- [20] 3GPP TS 36.211: "E-UTRA; Physical Channels and Modulation" +- [21] 3GPP TS 36.214: "E-UTRA; Physical layer – Measurements" + +[22] IEEE 802.11, Part 11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std." + +# --- 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|-------------------------------------------------------------------| +| BCH | Broadcast Channel | +| BCCH | Broadcast Control Channel (GSM) | +| BER | Bit Error Rate | +| BLER | Block Error Rate | +| CFN | Connection Frame Number | +| CPICH | Common Pilot Channel (FDD) | +| CRC | Cyclic Redundancy Check | +| DCA | Dynamic Channel Allocation | +| DCH | Dedicated Channel | +| DPCH | Dedicated Physical Channel | +| Ec/No | Received energy per chip divided by the power density in the band | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-HICH | E-DCH Hybrid ARQ Indicator Channel | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| FACH | Forward Access Channel | +| FCCH | Frequency Correction Channel (GSM) | +| FDD | Frequency Division Duplex | +| GSM | Global System for Mobile Communication | +| GPS | Global Positioning System | +| ISCP | Interference Signal Code Power | +| P-CCPCH | Primary Common Control Physical Channel | +| PCH | Paging Channel | +| PLMN | Public Land Mobile Network | +| PRACH | Physical Random Access Channel | +| PDSCH | Physical Downlink Shared Channel | +| PUSCH | Physical Uplink Shared Channel | +| RACH | Random Access Channel | +| RSCP | Received Signal Code Power | +| RSRP | Reference Signal Received Power | +| RSRQ | Reference Signal Received Quality | +| RSSI | Received Signal Strength Indicator | +| S-CCPCH | Secondary Common Control Physical Channel | +| SCH | Synchronisation Channel | +| SCTD | Space Code Transmit Diversity | +| SF | Spreading Factor | +| SFN | System Frame Number | +| SIR | Signal-to-Interference Ratio | +| TDD | Time Division Duplex | +| TDMA | Time Division Multiple Access | +| TrCH | Transport Channel | +| TTI | Transmission Time Interval | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| USCH | Uplink Shared Channel | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# --- 4 Control of UE/UTRAN measurements + +In this clause the general measurement control concept of the higher layers is briefly described to provide an understanding on how L1 measurements are initiated and controlled by higher layers. + +## 4.1 General measurement concept + +L1 provides with the measurement specifications a toolbox of measurement abilities for the UE and the UTRAN. These measurements can be differentiated in different measurement types: intra-frequency, inter-frequency, inter-system, traffic volume, quality and internal measurements (see [14]). + +In the L1 measurement specifications the measurements are distinguished between measurements in the UE (the messages will be described in the RRC Protocol) and measurements in the UTRAN (the messages will be described in the NBAP and the Frame Protocol). + +To initiate a specific measurement the UTRAN transmits a 'measurement control message' to the UE including a measurement ID and type, a command (setup, modify, release), the measurement objects and quantity, the reporting quantities, criteria (periodical/event-triggered) and mode (acknowledged/unacknowledged), see [14]. + +When the reporting criteria is fulfilled the UE shall answer with a 'measurement report message' to the UTRAN including the measurement ID and the results. + +In idle mode the measurement control message is broadcast in a System Information. + +Intra-frequency reporting events, traffic volume reporting events and UE internal measurement reporting events described in [14] define events which trigger the UE to send a report to the UTRAN. This defines a toolbox from which the UTRAN can choose the needed reporting events. + +## 4.2 Measurements for cell selection/reselection + +Whenever a PLMN has been selected the UE shall start to find a suitable cell to camp on, this is 'cell selection'. + +When camped on cell the UE regularly searches for a better cell depending on the cell reselection criteria, this is called 'cell reselection'. The procedures for cell selection and reselection are described in [13] and the measurements carried out by the UE are explained in this specification. + +## 4.3 Measurements for Handover + +For the handover preparation the UE receives from the UTRAN a list of cells (e.g. TDD, FDD or GSM), which the UE shall monitor (see 'monitored set' in [14]) in its idle timeslots. + +At the beginning of the measurement process the UE shall find synchronization to the cell to measure using the synchronization channel. This is described under 'cell search' in [9] if the monitored cell is a TDD cell and in [4] if it is an FDD cell. + +For a TDD cell to monitor after this procedure the exact timing of the midamble of the P-CCPCH is known and the measurements can be performed. Depending on the UE implementation and if timing information about the cell to monitor is available, the UE may perform the measurements on the P-CCPCH directly without prior SCH synchronisation. + +## 4.4 Measurements for DCA + +DCA is used to optimise the resource allocation by means of a channel quality criteria or traffic parameters. The DCA measurements are configured by the UTRAN. The UE reports the measurements to the UTRAN. + +For DCA no measurements are performed in idle mode in the serving TDD cell. + +When connecting with the initial access the UE immediately starts measuring the ISCP of time slots which are communicated on the BCH. The measurements and the preprocessing are done while the UTRAN assigns an UL channel for the UE for signalling and measurement reporting. + +In connected mode the UE performs measurements according to a measurement control message from the UTRAN. + +## 4.5 Measurements for timing advance + +To update timing advance of a moving UE the UTRAN measures 'Received Timing Deviation', i.e. the time difference of the received UL transmission (PRACH, DPCH, PUSCH) in relation to its timeslot structure that means in relation to the ideal case where an UL transmission would have zero propagation delay. The measurements are reported to higher layers, where timing advance values are calculated and signalled to the UE. + +# 5 Measurement abilities for UTRA TDD + +In this clause the physical layer measurements reported to higher layers. (this may also include UE internal measurements not reported over the air-interface) are defined. + +## 5.1 UE measurement abilities + +The structure of the table defining a UE measurement quantity is shown below. + +| Column field | Comment | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Contains the definition of the measurement. | +| Applicable for |

States in which RRC state according to [14] a measurement shall be possible to be performed. For RRC connected mode states information is also given on the possibility to perform the measurement on intra-frequency and/or inter-frequency.

The following terms are used in the tables:
Idle = Shall be possible to perform in idle mode;
URA_PCH = Shall be possible to perform in URA_PCH;
CELL_PCH = Shall be possible to perform in CELL_PCH;
CELL_FACH = Shall be possible to perform in CELL_FACH;
CELL_DCH = Shall be possible to perform in CELL_DCH;

For all RRC connected mode states i.e. URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH
Intra appended to the RRC state = Shall be possible to perform in the corresponding RRC state on an intra-frequency cell;
Inter appended to the RRC state = Shall be possible to perform in the corresponding RRC state on an inter-frequency cell.
Inter-RAT appended to the RRC state = Shall be possible to perform in the corresponding RRC state on an inter-RAT cell.

| + +NOTE 1: Measurements for TDD which are specified on the Primary CCPCH (P-CCPCH) are carried out on the P-CCPCH or on any other beacon channel, see [6]. + +NOTE 2: For the beacon channels [6], the received power measurements shall be based on the received power for midamble $m^{(1)}$ if no Space Code Transmit Diversity (SCTD) is applied to the P-CCPCH and on the sum of the received powers for midambles $m^{(1)}$ and $m^{(2)}$ if SCTD is applied to the P-CCPCH. + +NOTE 3: The UTRAN has to take into account the UE capabilities when specifying the timeslots to be measured in the measurement control message. + +NOTE 4: The line 'applicable for' indicates whether the measurement is applicable for inter-frequency and/or intra-frequency and furthermore for idle and/or connected mode. + +NOTE 5: The Interference part of the SIR measurement will be dependent on the receiver implementation, and will normally be different from the Timeslot ISCP measurement. + +NOTE 6: The measurement 'Timeslot ISCP' is only a measure of the intercell interference. + +NOTE 7: The term "antenna connector of the UE" used in this sub-clause to define the reference point for the UE measurements is defined in [17]. + +NOTE 8: Performance and reporting requirements for the UE measurements are defined in [19]. + +### 5.1.1 P-CCPCH RSCP + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Code Power, the received power on P-CCPCH of own or neighbour cell. The reference point for the RSCP shall be the antenna connector of the UE. If receiver diversity is in use by the UE, the reported value shall not be lower than the corresponding P-CCPCH RSCP of any of the individual diversity branches. | +| Applicable for | Idle,
URA_PCH intra, URA_PCH inter,
CELL_PCH intra, CELL_PCH inter,
CELL_FACH intra, CELL_FACH inter,
CELL_DCH intra, CELL_DCH inter | + +### 5.1.2 CPICH RSCP + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Code Power, the received power on one code measured on the Primary CPICH. The reference point for the RSCP shall be the antenna connector of the UE. (This measurement is used in TDD for monitoring FDD cells while camping on a TDD cell).
If Tx diversity is applied on the Primary CPICH the received code power from each antenna shall be separately measured and summed together in [W] to a total received code power on the Primary CPICH. | +| Applicable for | Idle,
URA_PCH inter,
CELL_PCH inter,
CELL_FACH inter,
CELL_DCH inter | + +### 5.1.3 Timeslot ISCP + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Interference Signal Code Power, the interference on the received signal in a specified timeslot measured on the midamble. The reference point for the ISCP shall be the antenna connector of the UE. | +| Applicable for | CELL_FACH intra,
CELL_DCH intra | + +### 5.1.4 UTRA carrier RSSI + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The received wide band power, including thermal noise and noise generated in the receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD within a specified timeslot. The reference point for the measurement shall be the antenna connector of the UE. If receiver diversity is in use by the UE, the reported value shall not be lower than the corresponding UTRA carrier RSSI of any of the individual diversity branches. | +| Applicable for | CELL_DCH intra, CELL_DCH inter | + +### 5.1.5 GSM carrier RSSI + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Strength Indicator, the wide-band received power within the relevant channel bandwidth Measurement shall be performed on a GSM BCCH carrier. The reference point for the RSSI shall be the antenna connector of the UE. | +| Applicable for | Idle,
URA_PCH inter-RAT,
CELL_PCH inter-RAT,
CELL_FACH inter-RAT,
CELL_DCH inter-RAT | + +### 5.1.6 SIR + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Signal to Interference Ratio, defined as: $(RSCP/Interference) \times SF$ .
Where:
RSCP = Received Signal Code Power, the received power on the code of a specified DPCH or PDSCH.
Interference = The interference on the received signal in the same timeslot which can't be eliminated by the receiver.
SF = The used spreading factor.

The reference point for the SIR shall be the antenna connector of the UE.
If receiver diversity is in use by the UE, the reported SIR value shall not be lower than the corresponding SIR of any of the individual diversity branches. | +| Applicable for | CELL_FACH intra,
CELL_DCH intra | + +### 5.1.7 CPICH Ec/No + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The received energy per chip divided by the power density in the band. The CPICH Ec/No is identical to CPICH RSCP/UTRA Carrier RSSI. The measurement shall be performed on the Primary CPICH. The reference point for the CPICH Ec/No shall be the antenna connector of the UE. (This measurement is used in TDD for monitoring FDD cells while camping on a TDD cell)
If Tx diversity is applied on the Primary CPICH the received energy per chip (Ec) from each antenna shall be separately measured and summed together in [Ws] to a total received chip energy per chip on the Primary CPICH, before calculating the Ec/No. | +| Applicable for | Idle,
URA_PCH inter,
CELL_PCH inter,
CELL_FACH inter,
CELL_DCH inter | + +### 5.1.8 Transport channel BLER + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Estimation of the transport channel block error rate (BLER). The BLER estimation shall be based on evaluating the CRC on each transport block. | +| Applicable for | CELL_DCH intra | + +### 5.1.9 UE transmitted power + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The total UE transmitted power on all carriers in a specified timeslot. The reference point for the UE transmitted power shall be the antenna connector of the UE. | +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.10 SFN-SFN observed time difference + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

SFN-SFN observed time difference is the time difference of the reception times of frames from two cells (serving and target) measured in the UE and expressed in chips. It is distinguished by two types. Type 2 applies if the serving and the target cell have the same frame timing.

The reference point for the SFN-SFN observed time difference type 1 and 2 shall be the antenna connector of the UE.

Type 1:
SFN-SFN observed time difference =

$\begin{cases} \text{OFF} \times 12800 + T_m \text{ in chips} & \text{for 1.28 Mcps TDD} \\ \text{OFF} \times 38400 + T_m \text{ in chips} & \text{for 3.84 Mcps TDD} \\ \text{OFF} \times 76800 + T_m \text{ in chips} & \text{for 7.68 Mcps TDD} \end{cases}$

where:

T_m = T_{\text{RxSFNi}} - T_{\text{RxSFNk}}, given in chip units

with the range \begin{cases} [0, 1, \dots, 12799] \text{ chips} & \text{for 1.28 Mcps TDD} \\ [0, 1, \dots, 38399] \text{ chips} & \text{for 3.84 Mcps TDD} \\ [0, 1, \dots, 76799] \text{ chips} & \text{for 7.68 Mcps TDD} \end{cases}

T_{\text{RxSFNi}} = time of start (defined by the first detected path in time) of the received frame SFNi of the serving TDD cell i.

T_{\text{RxSFNk}} = time of start (defined by the first detected path in time) of the received frame SFNk of the target UTRA cell k received most recently in time before the time instant T_{\text{RxSFNi}} in the UE. If this frame SFNk of the target UTRA cell is received exactly at T_{\text{RxSFNi}} then T_{\text{RxSFNk}} = T_{\text{RxSFNi}} (which leads to T_m=0).

OFF = (\text{SFNi} - \text{SFNk}) \bmod 256, given in number of frames with the range [0, 1, ..., 255] frames

SFNI = system frame number for downlink frame from serving TDD cell i in the UE at the time T_{\text{RxSFNi}}.

SFNk = system frame number for downlink frame from target UTRA cell k received in the UE at the time T_{\text{RxSFNk}}. (for FDD: the P-CCPCH frame)

The reference point for the SFN-SFN observed time difference type 1 shall be the antenna connector of the UE.

Type 2:
SFN-SFN observed time difference = T_{\text{Rx\_Frame\_cell k}} - T_{\text{Rx\_Frame\_cell i}}, in chips, where

T_{\text{Rx\_Frame\_cell i}}: time of start (defined by the first detected path in time) of the frame boundary from the serving TDD cell i.

T_{\text{Rx\_Frame\_cell k}}: time of start (defined by the first detected path in time) of the frame boundary from the target UTRA cell k that is closest in time to the frame boundary of the serving TDD cell i.

The reference point for the SFN-SFN observed time difference type 2 shall be the antenna connector of the UE.

| +| Applicable for |

Type 1: CELL_FACH intra

Type 2:
Idle,
URA_PCH intra, URA_PCH inter,
CELL_PCH intra, CELL_PCH inter,
CELL_FACH intra, CELL_FACH inter,
CELL_DCH intra, CELL_DCH inter

| + +### 5.1.11 SFN-CFN observed time difference + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The SFN-CFN observed time difference is defined as:
T_m for an FDD neighbour cell (i.e. the value is reported in chips),
OFF for a TDD neighbour cell (i.e. the value is reported in frames),
where:
T_m = T_{UETx} - T_{RxFN}, given in chip units with the range [0, 1, ..., 38399] chips.
T_{UETx} = the time at the beginning of the frame with the connection frame number CFN_{Tx} considering the transmission from the UE in the serving TDD cell.
T_{RxFN} = the time (defined by the first detected path in time) at the beginning of the frame with the system frame number SFN (for FDD neighbour cells: P-CCPCH frame is considered) received at the UE from a neighbour cell. T_{RxFN} is the time instant most recent in time before the time instant T_{UETx}
OFF = (SFN - CFN_{Tx}) \bmod 256, given in number of frames with the range [0, 1, ..., 255] frames.
CFN_{Tx} = the connection frame number for the UE transmission.
SFN = is the system frame number for the neighbouring cell frame (for FDD neighbour cells: P-CCPCH frame) received in the UE at the time instant T_{RxFN}.

The reference point for the SFN-CFN observed time difference shall be the antenna connector of the UE.

| +| Applicable for | CELL_DCH intra, CELL_DCH inter | + +### 5.1.12 Observed time difference to GSM cell + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Observed time difference to GSM cell is reported as the time difference T_m in ms, where
T_m = T_{RxGSMk} - T_{RxFN0i}
T_{RxFN0i} = time of start (defined by the first detected path in time) of the received frame SFN=0 of the serving TDD cell i
T_{RxGSMk} = time of start of the GSM BCCH 51-multiframe of the considered target GSM frequency k received closest in time after the time T_{RxFN0i}. If the next GSM BCCH 51-multiframe is received exactly at T_{RxFN0i} then T_{RxGSMk} = T_{RxFN0i} (which leads to T_m=0). The beginning of the GSM BCCH 51-multiframe is defined as the beginning of the first tail bit of the frequency correction burst in the first TDMA-frame of the GSM BCCH 51-multiframe, i.e. the TDMA-frame following the IDLE-frame.

The reference point for the Observed time difference to GSM cell shall be the antenna connector of the UE.

The reported time difference is calculated from the actual measurement in the UE. The actual measurement shall be based on:
T_{MeasGSM,j}: The start of the first tail bit of the most recently received GSM SCH on frequency j
T_{MeasSFN,i}: The start of the last frame received in TDD cell i before receiving the GSM SCH on frequency j

For calculating the reported time difference, the frame lengths are always assumed to be 10 ms for UTRA and (60/13) ms for GSM.

| +| Applicable for | Idle, URA PCH inter-RAT, CELL PCH inter-RAT, CELL_DCH Inter-RAT | + +### 5.1.13 UE GPS Timing of Cell Frames for UE positioning + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | $T_{UE-GPSj}$ is defined as the time of occurrence of a specified UTRAN event according to GPS Time Of Week. 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 P-CCPCH. The reference point for $T_{UE-GPSj}$ shall be the antenna connector of the UE. | +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.14 Timing Advance ( $T_{ADV}$ ) for 1.28Mcps TDD + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The 'timing advance (T_{ADV})' is the time difference

$T_{ADV} = T_{RX} - T_{TX}$

Where

T_{RX}: calculated beginning time of the first uplink time slot in the first subframe used by the UE with the UE timing according to the reception of start (defined by the first detected path in time) of a certain downlink time slot (for the timing it is assumed that the time slots within a sub-frame are scheduled like given in the frame structure described in 25.221 chapter5A.1)

T_{TX}: time of the beginning of the same uplink time slot by the UE (for the timing it is assumed that the time slots within a sub-frame are scheduled like given in the frame structure described in 25.221 chapter5A.1)

The reference point for the Timing Advance (T_{ADV}) shall be the antenna connector of the UE.

| +| Applicable for | CELL_FACH intra, CELL_DCH intra | + +### 5.1.15 UE GPS code phase + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The whole and fractional phase of the spreading code of the $i^{th}$ GPS satellite signal. The reference point for the GPS code phase shall be the antenna connector of the UE. | +| Applicable for | Void (this measurement is not related to UTRAN/GSM signals; its applicability is therefore independent of the UE RRC state.) | + +### 5.1.16 UE transmission power headroom (1.28Mcps option only) + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

UE transmission power headroom (UPH) in reference to a carrier is the ratio of the maximum UE transmission power and the product of P_{e-base} power of this carrier and serving cell path loss, and shall be calculated as following:

$UPH = \frac{P_{max, tx}}{P_{e-base} \cdot L_{Path\_loss}}$

where:
P_{max, tx} = \min \{Maximum\ allowed\ UL\ TX\ Power, P_{max}\} is the UE maximum transmission power;
Maximum allowed UL TX Power is set by UTRAN and defined in [14];
P_{max} is the UE nominal maximum output power according to the UE power class and specified in [17] table 6.2;
P_{e-base} is a closed-loop quantity of this carrier defined in [9] and L_{Path\_loss} is the serving cell path loss.

The reference point for the UE transmission power headroom shall be the antenna connector of the UE.

| +| Applicable for | CELL_DCH intra | + +### 5.1.17 UE transmission power headroom (3.84Mcps and 7.68Mcps options) + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

UE transmission power headroom (UPH) is the ratio of the maximum UE transmission power and a value P_{e,norm}, and shall be calculated as per the following:

$UPH = \frac{P_{max, tx}}{P_{e,norm}}$

where:
P_{max, tx} = \min \{Maximum\ allowed\ UL\ TX\ Power, P_{max}\} is the UE maximum transmission power;
Maximum allowed UL TX Power is set by UTRAN and defined in [14];
P_{max} is the UE nominal maximum output power according to the UE power class and specified in [17] table 6.1;
P_{e,norm} is equal to the calculated E-PUCH transmission power as defined in [9] for the case in which \beta_e = 0.

The reference point for the UE transmission power headroom shall be the antenna connector of the UE.

| +| Applicable for | CELL_DCH intra | + +### 5.1.18 E-UTRA RSRP + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Reference signal received power (RSRP), is defined as the linear average over the power contributions (in [W]) of the resource elements that carry cell-specific reference signals within the considered measurement frequency bandwidth.

For RSRP determination the cell-specific reference signals R_0 according to TS 36.211 [20] shall be used. If the UE can reliably detect that R_1 is available it may use R_1 in addition to R_0 to determine RSRP.

The reference point for the RSRP shall be the antenna connector of the UE.

If receiver diversity is in use by the UE, the reported value shall not be lower than the corresponding RSRP of any of the individual diversity branches.

| +| Applicable for |

Idle,
URA_PCH inter-RAT
CELL_PCH inter-RAT
CELL_DCH inter-RAT

| + +NOTE 1: The number of resource elements within the considered measurement frequency bandwidth and within the measurement period that are used by the UE to determine RSRP is left up to the UE implementation with the limitation that corresponding measurement accuracy requirements have to be fulfilled. + +NOTE 2: The power per resource element is determined from the energy received during the useful part of the symbol, excluding the CP. + +### 5.1.19 E-UTRA RSRQ + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Reference Signal Received Quality (RSRQ) is defined as the ratio N \times \text{RSRP} / (\text{E-UTRA carrier RSSI}), where N is the number of resource blocks of the E-UTRA carrier RSSI measurement bandwidth. The measurements in the numerator and denominator shall be made over the same set of resource blocks.

E-UTRA Carrier Received Signal Strength Indicator (RSSI), comprises the linear average of the total received power (in [W]) observed only in certain OFDM symbols of measurement subframes, in the measurement bandwidth, over N number of resource blocks by the UE from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise etc.

Unless indicated otherwise by higher layers, RSSI is measured only from OFDM symbols containing reference symbols for antenna port 0 of measurement subframes. If higher layers indicate all OFDM symbols for performing RSRQ measurements, then RSSI is measured from all OFDM symbols of the DL part of measurement subframes.

The reference point for the RSRQ shall be the antenna connector of the UE.

If receiver diversity is in use by the UE, the reported value shall not be lower than the corresponding RSRQ of any of the individual diversity branches.

| +| Applicable for |

Idle,
URA_PCH inter-RAT
CELL_PCH inter-RAT
CELL_DCH inter-RAT

| + +### 5.1.20 IEEE 802.11 Beacon RSSI + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------| +| Definition | The IEEE 802.11 Beacon RSSI is defined in [22]. | +| Applicable for | Idle,
URA_PCH inter-RAT
CELL_PCH inter-RAT
CELL_FACH inter-RAT
CELL_DCH inter-RAT | + +## 5.2 UTRAN measurement abilities + +NOTE 1: If the UTRAN supports multiple frequency bands then the measurements apply for each frequency band individually. + +NOTE 2: The Interference part of the SIR measurement will be dependent on the receiver implementation, and will normally be different from the Timeslot ISCP measurement + +NOTE 3: The term "antenna connector" used in this sub-clause to define the reference point for the UTRAN measurements refers to the "BS antenna connector" test port A and test port B as described in [18]. The term "antenna connector" refers to Rx or Tx antenna connector as described in the respective measurement definitions. + +### 5.2.1 RSCP + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Signal Code Power, the received power on one DPCH, PRACH, PUSCH, HS-SICH or E-PUCH code. The reference point for the RSCP shall be the Rx antenna connector. When Cell Portions are defined in the cell, the RSCP for each Cell Portion can be measured and reported to higher layers. | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.2 Timeslot ISCP + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Interference Signal Code Power, the interference on the received signal in a specified timeslot measured on the midamble. The reference point for the ISCP shall be the Rx antenna connector. In the case of RX antenna diversity, the average of the linear values [W] of the ISCP values measured for each antenna branch shall be reported. When Cell Portions are defined in the cell, the Timeslot ISCP for each Cell Portion can be measured and reported to higher layers. | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.3 Received total wide band power + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The received wide band power in a specified timeslot including the noise generated in the receiver, within the bandwidth defined by the receiver pulse shaping filter. The reference point for the measurement shall be the Rx antenna connector. In case of receiver diversity the reported value shall be the linear average of the power in [W] in the diversity branches. When Cell Portions are defined in the cell, the received total wide band power for each Cell Portion can be measured and reported to higher layers. | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.4 SIR + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Signal to Interference Ratio, defined as: (RSCP/Interference) \times SF.

Where:

RSCP = Received Signal Code Power, the received power on the code of a specified DPCH, PRACH, PUSCH, HS-SICH or E-PUCH.

Interference = The interference on the received signal in the same timeslot which can't be eliminated by the receiver.

SF = The used spreading factor.

The reference point for the SIR shall be the Rx antenna connector.

| +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.5 Transport channel BER + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The transport channel BER is an estimation of the average bit error rate (BER) of DCH or USCH data. The transport channel (TrCH) BER is measured from the data considering only non-punctured bits at the input of the channel decoder in Node B.

It shall be possible to report an estimate of the transport channel BER for a TrCH after the end of each TTI of the TrCH. The reported TrCH BER shall be an estimate of the BER during the latest TTI for that TrCH. Transport channel BER is only required to be reported for TrCHs that are channel coded.

| +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.6 Transmitted carrier power + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Transmitted carrier power, is the ratio between the total transmitted power and the maximum transmission power.

Total transmission power is the power [W] transmitted on one DL carrier in a specific timeslot from one UTRAN access point.

Maximum transmission power is the power [W] on the same carrier when transmitting at the configured maximum transmission power for the cell.

The measurement shall be possible on any carrier transmitted from the UTRAN access point.

The reference point for the transmitted carrier power measurement shall be the Tx antenna connector.

In case of Tx diversity the transmitted carrier power is the ratio between the sum of the total transmitted powers of all branches and the maximum transmission power. When Cell Portions are defined in the cell, the transmitted carrier power for each Cell Portion can be measured and reported to higher layers.

| +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.7 Transmitted code power + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Transmitted Code Power, is the transmitted power on one carrier and one channelisation code in one timeslot. The reference point for the transmitted code power measurement shall be the Tx antenna connector.

In the case of Tx diversity the transmitted code power for each branch shall be measured and the linear sum of the values shall be reported to higher layers, i.e. only one value will be reported to higher layers.

| +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.8 RX Timing Deviation + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

'RX Timing Deviation' is the time difference TRXdev = TTS - TRXpath in chips, with

TRXpath: time of the reception in the Node B of the first detected uplink path (in time) to be used in the detection process. The reference point for TRXpath shall be the Rx antenna connector. For 1.28 Mcps TDD only the first UL timeslot in the first subframe used by the UE is used for the calculation of TRXpath.

TTS: time of the beginning of the respective slot according to the Node B internal timing

| +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: This measurement can be used for timing advance calculation or location services. + +### 5.2.9 UTRAN GPS Timing of Cell Frames for UE positioning + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

T_{UTRAN-GPSj} is defined as the time of occurrence of a specified UTRAN event according to GPS Time Of Week. The specified UTRAN event is the beginning of the transmission of a particular frame (identified through its SFN) transmitted in the cell. The reference point for T_{UTRAN-GPSj} shall be the Tx antenna connector.

| +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.10 SFN-SFN observed time difference + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

SFN-SFN observed time difference = T_{Rx\_Frame\_cell\ k} - T_{Rx\_Frame\_cell\ i}, in chips, where

T_{Rx\_Frame\_cell\ i}: time of start (defined by the first detected path in time) of the frame boundary from the TDD cell i.

T_{Rx\_Frame\_cell\ k}: time of start (defined by the first detected path in time) of the frame boundary from the cell k that is closest in time to the frame boundary of the TDD cell i.

| +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.11 Cell Sync Burst Timing + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Cell sync burst timing is the time of start (defined by the first detected path in time) of the cell sync burst of a neighbouring cell. This measurement is applicable for 3.84Mcps TDD and 1.28Mcps TDD. For 1.28 Mcps TDD the DwPCH represents the cell sync burst. Type 1 is used for the initial phase of Node B synchronization. Type 2 is used for the steady-state phase of Node B synchronization. Both have different range.

The reference point for the cell sync burst timing measurement shall be the Rx antenna connector.

Type 1:
\text{Cell sync burst timing} = T_{\text{Rx}} - T_{\text{slot}} in chips, where

T_{\text{slot}} : time of start of the cell sync timeslot in the frame, where the cell sync burst was received.

T_{\text{Rx}} : time of start (defined by the first detected path in time) of a cell sync burst received from the target UTRA cell.

Type 2:
\text{Cell sync burst timing} = T_{\text{Rx}} - T_{\text{slot}}, in chips, where

T_{\text{slot}} : time of start of the cell sync timeslot in the frame, where the cell sync burst was received.

T_{\text{Rx}} : time of start (defined by the first detected path in time) of a cell sync burst received from the target UTRA cell.

| +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.12 Cell Sync Burst SIR + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Signal to Interference Ratio for the cell sync burst, defined as: \text{RSCP/Interference}, where:

\text{RSCP} = Received Signal Code Power, the received power on the code and code offset of a cell sync burst.

\text{Interference} = The interference on the received signal in the same timeslot which can't be eliminated by the receiver

This measurement is applicable for 3.84Mcps TDD and 1.28Mcps TDD.

The reference point for the cell sync burst SIR shall be the Rx antenna connector. For 1.28 Mcps TDD the DwPCH represents the cell sync burst.

| +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.13 Received SYNC-UL Timing Deviation for 1.28Mcps TDD + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

'Received SYNC-UL Timing Deviation' is the time difference

$UpPCH_{POS} = UpPCH_{Rxpath} - UpPCH_{TS}$

Where

UpPCHRxpath: time of the reception in the Node B of the SYNC-UL to be used in the uplink synchronization process

UpPCHTS: time instance 128 chips prior to the start of the UpPCH according to the Node B internal timing

UE can calculate Round Trip Time (RTT) towards the UTRAN after the reception of the FPACH containing UpPCHPOS transmitted from the UTRAN.

Round Trip Time RTT is defined by

$RTT = UpPCH_{ADV} + UpPCH_{POS} - 8 * 16 T_C$

Where

UpPCHADV: the amount of time by which the transmission of UpPCH is advanced in time relative to the end of the guard period according to the UE Rx timing.

| +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.14 Angle of Arrival (AOA) for 1.28Mcps TDD + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

AOA defines the estimated angle of a user with respect to a reference direction. The reference direction for this measurement shall be the North, positive in a counter-clockwise direction. The AOA is determined at the BS antenna for an UL channel corresponding to this UE. When Cell Portions are defined in the cell, the AOA for cell portion can be measured if possible.

| +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.15 HS-SICH reception quality + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The HS-SICH reception quality is defined via the following quantities. Each quantity is measured over the defined reporting period per UE:

  • - the number of expected HS-SICH transmissions from a given UE, and
  • - the number of unsuccessful HS-SICH receptions for this same UE in the Node B.

The number of expected HS-SICH transmissions from any given UE shall correspond to the number of scheduled HS-SCCH transmissions to the same UE.

Unsuccessful HS-SICH receptions shall be further divided into two categories;

  • - the number of failed HS-SICH receptions, and
  • - the number of missed HS-SICH receptions

for a given UE counted during the reporting period.

A failed HS-SICH reception is defined as an HS-SICH estimated to have been transmitted by the UE, but deemed not to have been received successfully by the Node B. A missed HS-SICH reception is defined as an HS-SICH estimated not to have been transmitted by the UE, if an HS-SICH transmission occasion was scheduled for the UE.

For the HS-SICH reception quality measurement, only HS-SICH transmission occasions for the respective UE during the reporting period shall be taken into account.

| +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.16 Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, or E-HICH transmission + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission is the ratio between the total transmitted power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission in a specified timeslot on one DL carrier from one UTRAN access point, and the maximum transmission power possible to use on that DL carrier in the timeslot. Total transmission power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission is the sum of the mean power levels [W] of each of the codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission in the specified timeslot on one carrier from one UTRAN access point. Maximum transmission power is the mean power [W] in the specified timeslot on one carrier from one UTRAN access point when transmitting at the configured maximum power for the cell. The measurement shall be possible on any timeslot and carrier transmitted from the UTRAN access point. The reference point for the transmitted carrier power measurement of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission shall be the Tx antenna connector. In case of Tx diversity the transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission is the ratio between the sum of the total transmitted powers of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission of all branches and the maximum transmission power. When Cell Portions are defined in the cell, the transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH or E-HICH transmission for each Cell Portion can be measured and reported to higher layers. | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.17 UpPTS interference (1.28Mcps TDD) + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The level of interference in the UpPTS, defined as the difference between the mean received power in the UpPTS and the sum of the estimated mean power levels of all detected UpPCH transmissions. In the case of antenna diversity, the linear average of the UpPTS interference levels calculated for each antenna branch shall be calculated. The reference point for the UpPTS interference measurement shall be the Rx antenna connector. When Cell Portions are defined in the cell, the UpPTS interference for each Cell Portion can be measured and reported to higher layers. | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# Annex A (informative): Monitoring GSM from TDD: Calculation Results + +## A.1 Low data rate traffic using 1 uplink and 1 downlink slot (for the 3.84 Mcps option) + +NOTE: The section evaluates the time to acquire the FCCH if all idle slots are devoted to the tracking of a FCCH burst, meaning that no power measurements is done concurrently. The derived figures are better than those for GSM. The section does not derive though any conclusion. A conclusion may be that the use of the idle slots is a valid option. An alternative conclusion may be that this is the only mode to be used, removing hence the use of the slotted frames for low data traffic or the need for a dual receiver, if we were to considering the monitoring of GSM cells only, rather than GSM, TDD and FDD. + +If a single synthesiser UE uses only one uplink and one downlink slot, e.g. for speech communication, the UE is not in transmit or receive state during 13 slots in each frame. According to the timeslot numbers allocated to the traffic, this period can be split into two continuous idle intervals A and B as shown in the figure below. + +![Figure A.1: Possible idle periods in a frame with two occupied timeslots. The diagram shows a horizontal timeline representing a 10 ms frame, divided into 15 timeslots. The first timeslot is labeled 'Tx' (transmit) and is shaded grey. The fifth timeslot is labeled 'Rx' (receive) and is also shaded grey. The remaining 13 timeslots are white and represent idle periods. These 13 idle slots are divided into two continuous intervals: 'A' (between the Tx and Rx slots) and 'B' (between the Rx and Tx slots). A vertical line separates the first 10 timeslots from the remaining 5. The total duration of the frame is indicated as 10 ms.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +Figure A.1: Possible idle periods in a frame with two occupied timeslots. The diagram shows a horizontal timeline representing a 10 ms frame, divided into 15 timeslots. The first timeslot is labeled 'Tx' (transmit) and is shaded grey. The fifth timeslot is labeled 'Rx' (receive) and is also shaded grey. The remaining 13 timeslots are white and represent idle periods. These 13 idle slots are divided into two continuous intervals: 'A' (between the Tx and Rx slots) and 'B' (between the Rx and Tx slots). A vertical line separates the first 10 timeslots from the remaining 5. The total duration of the frame is indicated as 10 ms. + +**Figure A.1: Possible idle periods in a frame with two occupied timeslots** + +A is defined as the number of idle slots between the Tx and Rx slots and B the number of idle slots between the Rx and Tx slots. It is clear that $A+B=13$ time slots. + +In the scope of low cost terminals, a [0.8] ms period is supposed to be required to perform a frequency jump from UMTS to GSM. This lets possibly two free periods of $A \cdot T_s - 1.6$ ms and $B \cdot T_s - 1.6$ ms during which the mobile station can monitor GSM, $T_s$ being the slot period. + +Following table evaluates the average synchronisation time and maximum synchronisation time, where the announced synchronisation time corresponds to the time needed to find the FCCH. The FCCH is supposed to be perfectly detected meaning that the FCCH is found if it is entirely present in the monitoring window. The FCCH being found the SCH location is unambiguously known from that point. All the 13 idle slots are assumed to be devoted to FCCH tracking and the UL traffic is supposed to occupy the time slot 0. + +**Table A.1: example- of average and maximum synchronisation time with two busy timeslots per frame and with 0.8 ms switching time (\*)** + +| Downlink time slot number | Number of free TS in A | Number of free TS in B | Average synchronisation time (ms) | Maximum synchronisation time (ms) | +|---------------------------|------------------------|------------------------|-----------------------------------|-----------------------------------| +| 1 | 0 | 13 | 44 | 140 | +| 2 | 1 | 12 | 50 | 187 | +| 3 | 2 | 11 | 58 | 188 | +| 4 | 3 | 10 | 66 | 189 | +| 5 | 4 | 9 | 70 | 233 | +| 6 | 5 | 8 | 77 | 234 | +| 7 | 6 | 7 | 75 | 189 | +| 8 | 7 | 6 | 75 | 189 | +| 9 | 8 | 5 | 75 | 235 | +| 10 | 9 | 4 | 67 | 235 | +| 11 | 10 | 3 | 63 | 186 | +| 12 | 11 | 2 | 56 | 186 | +| 13 | 12 | 1 | 49 | 186 | +| 14 | 13 | 0 | 43 | 132 | + +(\*) All simulations have been performed with a random initial delay between GSM frames and UMTS frames. + +Each configuration of TS allocation described above allows a monitoring period sufficient to acquire synchronisation. + +### A.1.1 Higher data rate traffic using more than 1 uplink and/or 1 downlink TDD timeslot + +The minimum idle time to detect a complete FCCH burst for all possible alignments between the GSM and the TDD frame structure (called 'guaranteed FCCH detection'), assuming that monitoring happens every TDD frame, can be calculated as follows ( $t_{FCCH}$ = one GSM slot): + +$$t_{min, guaranteed} = 2 \times t_{synth} + t_{FCCH} + \frac{10ms}{13} = 2 \times t_{synth} + \frac{35ms}{26}$$ + +- (e.g for $t_{synth} = 0ms$ : 3 TDD **consecutive** idle timeslots needed, for $t_{synth} = 0,3ms$ : 3 slots, for $t_{synth} = 0,5ms$ : 4 slots, for $t_{synth} = 0,8ms$ : 5 slots). Under this conditions the FCCH detection time can never exceed the time of 660ms. +- (For a more general consideration $t_{synth}$ may be considered as a sum of all delays before starting monitoring is possible). +- For detecting SCH instead of FCCH (for a parallel search) the same equation applies. +- In the equation before the dual synthesiser UE is included if the synthesiser switching time is 0ms. + +**Table A.2: FCCH detection time for a dual synthesizer UE monitoring GSM from TDD every TDD frame** + +| occupied slots=
15-idle slots | cases | FCCH detection time in ms | | +|----------------------------------|-------|---------------------------|---------| +| | | Average | maximum | +| 2 | 105 | 37 | 189 | +| 3 | 455 | 46 | 327 | +| 4 | 1365 | 58 | 419 | +| 5 | 3003 | 72 | 501 | +| 6 | 5005 | 90 | 646 | +| 7 | 6435 | 114 | 660 | +| 8 | 6435 | 144 | 660 | +| 9 | 5005 | 175 | 660 | +| 10 | 3003 | 203 | 660 | +| 11 | 1365 | 228 | 660 | +| 12 | 455 | 254 | 660 | +| 13 | 105 | - | - | +| 14 | 15 | - | - | +| | | | | + +In the table above for a given number of occupied slots in the TDD mode all possible cases of distributions of these occupied TDD slots are considered (see 'cases'). For every case arbitrary alignments of the TDD and the GSM frame structure are taken into account for calculating the average FCCH detection time (only these cases are used which guarantee FCCH detection for all alignments; only the non-parallel FCCH search is reflected by the detection times in the table 2). + +The term 'occupied slots' means that the UE is not able to monitor in these TDD slots. + +For a synthesiser switching time of one or one half TDD timeslot the number of needed consecutive idle TDD timeslots is summarized in the table below: + +**Table A.3: Link between the synthesiser performance and the number of free consecutive TSs for guaranteed FCCH detection, needed for GSM monitoring** + +| One-way switching time for the synthesiser | Number of free consecutive TDD timeslots needed in the frame for a guaranteed FCCH detection | +|--------------------------------------------|----------------------------------------------------------------------------------------------| +| 1 TS (=2560 chips) | 5 | +| 0.5 TS (=1280 chips) | 4 | +| 0 (dual synthesiser) | 3 | + +## A.2 Low data rate traffic using 1 uplink and 1 downlink slot (for the 1.28 Mcps option) + +**NOTE:** The section evaluates the time to acquire the FCCH if all idle slots are devoted to the tracking of a FCCH burst, meaning that no power measurements is done concurrently. The derived figures are better than those for GSM. The section does not derive though any conclusion. A conclusion may be that the use of the idle slots is a valid option. An alternative conclusion may be that this is the only mode to be used, removing hence the use of the slotted frames for low data traffic or the need for a dual receiver, if we were to considering the monitoring of GSM cells only, rather than GSM, TDD and FDD. + +If a single synthesiser UE uses only one uplink and one downlink slot, e.g. for speech communication, the UE is not in transmit or receive state during 5 slots in each frame. According to the timeslot numbers allocated to the traffic, this period can be split into two continuous idle intervals A and B as shown in the figure below. + +![Figure A.2: Possible idle periods in a subframe with two occupied timeslots. The diagram shows a subframe 'i' and 'i+1' with timeslots. Subframe 'i' contains a TX timeslot and an RX timeslot. The number of idle slots between TX and RX is labeled 'A'. The number of idle slots between RX and TX is labeled 'B'. The number of idle slots between TX and RX in subframe 'i+1' is labeled 'C'.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure A.2: Possible idle periods in a subframe with two occupied timeslots. The diagram shows a subframe 'i' and 'i+1' with timeslots. Subframe 'i' contains a TX timeslot and an RX timeslot. The number of idle slots between TX and RX is labeled 'A'. The number of idle slots between RX and TX is labeled 'B'. The number of idle slots between TX and RX in subframe 'i+1' is labeled 'C'. + +**Figure A.2: Possible idle periods in a subframe with two occupied timeslots** + +A is defined as the number of idle slots between the Tx and Rx slots and B the number of idle slots between the Rx and Tx slots. It is clear that $A+B=5$ time slots and C is equal to the DwPTS+GP+UpPTS. + +In the scope of low cost terminals, a [0.5] ms period is supposed to be required to perform a frequency jump from 1.28Mcps TDD to GSM and vice versa. This lets possibly two free periods of $A \times \text{Timeslots} - 1$ ms and $B \times \text{Timeslots} + C - 1$ ms during which the mobile station can monitor GSM, Timeslots being the slot period. + +Following table evaluates the average synchronisation time and maximum synchronisation time, where the announced synchronisation time corresponds to the time needed to find the FCCH. The FCCH is supposed to be perfectly detected which means that it is entirely present in the monitoring window. The FCCH being found the SCH location is unambiguously known from that point. All the 5 idle slots and the DwPTS+GP+UpPTS are assumed to be devoted to FCCH tracking and the UL traffic is supposed to occupy the time slot 1. + +**Table A.4: example- of average and maximum synchronisation time with two busy timeslots per sub-frame and with 0.5 ms switching time** + +| Downlink time slot number | Number of free Timeslots in A | Number of free Timeslots in B | Average synchronisation time (ms) | Maximum synchronisation time (ms) | +|---------------------------|-------------------------------|-------------------------------|-----------------------------------|-----------------------------------| +| 0 | 5 | 0 | 83 | 231 | +| 2 | 0 | 5 | 75 | 186 | +| 3 | 1 | 4 | 98 | 232 | +| 4 | 2 | 3 | 185 | 558 | +| 5 | 3 | 2 | 288 | 656 | +| 6 | 4 | 1 | 110 | 371 | + +(\*) All simulations have been performed with a random initial delay between GSM frames and 1.28Mcps TDD sub-frames. + +Each configuration of Timeslots allocation described above allows a monitoring period sufficient to acquire synchronisation. + +NOTE: Considering about the frame structure of 1.28Mcps TDD, there are total 7 timeslots in each sub-frame that can be used as data traffic. If more than 1 uplink and/or 1 downlink TDD timeslot are used for data traffic, that means it will occupy at least 3 time slots, equal to $0.675 \times 3 = 2.025$ ms. And more time slots for traffic data means more switching point are needed to switch between the GSM and the 1.28Mcps TDD. As it was mentioned above, each switching will take 0.5ms. As a result, the idle time left for monitoring the GSM will be very little. So monitoring GSM from 1.28Mcps TDD under this situation will be considered in the future. It will need more carefully calculation and simulation. + +### A.2.1 Higher data rate traffic using more than 1 uplink and/or 1 downlink TDD timeslot (for 1.28Mcps TDD) + +The minimum idle time to detect a complete FCCH burst for all possible alignments between the GSM and the 1.28Mcps TDD frame structure (called 'guaranteed FCCH detection'), assuming that monitoring happens every sub-frame, can be calculated as follows ( $t_{\text{FCCH}}$ = one GSM slot): + +$$t_{min, guaranteed} = 2 \times t_{synth} + t_{FCCH} + \frac{5ms}{13} = 2 \times t_{synth} + \frac{25ms}{26}$$ + +- (e.g for $t_{synth} = 0ms$ : 2 1.28Mcps TDD **consecutive** idle timeslots needed, for $t_{synth} = 0.3ms$ : 3 slots (or 2 slots and the DwPTS+GP+UpPTS), for $t_{synth} = 0.5ms$ : 3 slots, for $t_{synth} = 0.8ms$ : 4 slots). Under this conditions the FCCH detection time can never exceed the time of 660ms. +- (For a more general consideration $t_{synth}$ may be considered as a sum of all delays before starting monitoring is possible). +- For detecting SCH instead of FCCH (for a parallel search) the same equation applies. +- In the equation before the dual synthesiser UE is included if the synthesiser switching time is 0ms. + +**Table A.5 : FCCH detection time for a single synthesizer UE monitoring GSM from 1.28Mcps TDD every sub-frame** + +| Occupied Slots | Cases | AVERAGE FCCH detection time in ms | MAXIMUM FCCH detection time in ms | +|----------------|-------|-----------------------------------|-----------------------------------| +| 2 | 21 | 136.625 | 660.785 | +| 3 | 35 | 188.451 | 660.785 | +| 4 | 35 | 231.115 | 660.785 | +| 5 | 21 | - | - | +| 6 | 7 | - | - | +| 7 | 1 | - | - | + +The result in the above table is based on the following assumption: + +- A single synthesizer is used. +- A [0.5] ms period is supposed to be required to perform a frequency jump from 1.28Mcps TDD to GSM and vice versa. +- For a given number of occupied slots in the TDD mode all possible cases of distributions of these occupied TDD slots are considered (see 'cases'). For every case arbitrary alignments of the TDD and the GSM frame structure are taken into account for calculating the average FCCH detection time (only these cases are used which guarantee FCCH detection for all alignments; only the non-parallel FCCH search is reflected by the detection times in the above table). + +The term 'occupied slots' means that the UE is not able to monitor in these TDD slots. + +For a synthesiser switching time of one or one half TDD timeslot the number of needed consecutive idle TDD timeslots is summarized in the table below: + +**Table A.6 : Link between the synthesiser performance and the number of free consecutive Timeslots for guaranteed FCCH detection, needed for GSM monitoring** + +| One-way switching time for the synthesiser | Number of free consecutive 1.28Mcps TDD timeslots needed in the sub-frame for a guaranteed FCCH detection | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| 1 Timeslot (=864 chips) | 4 | +| 0.5 Timeslot (=432 chips) | 3 | +| 0 (dual synthesiser) | 2 | + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|-----------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/01/00 | RAN_05 | RP-99595 | - | | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RAN_06 | RP-99700 | 001 | 1 | Primary and Secondary CCPCH in TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99701 | 002 | 1 | Block STTD capability for P-CCPCH, TDD component | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99700 | 003 | 1 | Update concerning measurement definitions, ranges and mappings | 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-000071 | 004 | 1 | Correction of CPICH measurements and 'RX Timing Deviation' range | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000071 | 005 | 2 | Editorial modifications to 25.225 | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000071 | 006 | 1 | Corrections to 25.225 Measurements for TDD | 3.1.1 | 3.2.0 | +| 26/06/00 | RAN_08 | RP-000275 | 009 | - | Clarifications on TxDiversity for UTRA TDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000275 | 010 | - | Removal of Range/mapping | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000275 | 011 | - | Removal of transport channel BLER | 3.2.0 | 3.3.0 | +| 23/09/00 | RAN_09 | RP-000348 | 012 | 1 | Alignment of TDD measurements with FDD : GPS related measurements | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 013 | 1 | Alignment of TDD measurements with FDD :SFN-CFN observed time difference | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 014 | - | Clarification of the Timeslot ISCP measurements | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 015 | - | Terminology regarding the beacon function | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 016 | - | Removal of Physical Channel BER | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000348 | 017 | - | Update of TS25.225 due to recent change for FDD: Reporting of UTRAN TX carrier power | 3.3.0 | 3.4.0 | +| 15/12/00 | RAN_10 | RP-000545 | 018 | 2 | Corrections and Clarifications to 25.225 | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000545 | 019 | 1 | Corrections and Clarifications to 25.225 | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000545 | 020 | 1 | Clarification of measurement reference points | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000545 | 021 | - | Removal of incorrect note relating to RSCP measurements | 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-010066 | 023 | - | Correction of the observed time difference to GSM measurement | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010073 | 022 | - | Measurements for Node B synchronisation | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010071 | 024 | 1 | Inclusion of 1.28Mcps TDD in TS 25.225 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010072 | 025 | - | RTD measurement in UTRAN for UP-TDD | 3.5.0 | 4.0.0 | +| 15/06/01 | RAN_12 | RP-010339 | 029 | - | Renaming of LCS measurements | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010339 | 030 | - | Addition to the abbreviation list | 4.0.0 | 4.1.0 | +| 21/09/01 | RAN_13 | RP-010526 | 034 | - | Clarification of the Beacon Measurement in TS25.225 | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010707 | 031 | 1 | RxTiming Deviation for 1.28 Mcps TDD | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010532 | 032 | - | SFN-SFN type 1 for 1.28 Mcps TDD | 4.1.0 | 4.2.0 | +| 14/12/01 | RAN_14 | RP-010743 | 036 | 1 | Removal of references to Block STTD | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010743 | 040 | - | Correction of measurement definition for UTRA Carrier RSSI and CPICH Ec/No | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010750 | 038 | 1 | Introduction of new "UE GPS code phase" measurement | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010750 | 042 | - | Corrections in annex A.2 in TS 25.225 | 4.2.0 | 4.3.0 | +| 08/03/02 | RAN_15 | RP-020055 | 041 | 1 | Introduction of "Node B synchronization for 1.28 Mcps TDD" | 4.3.0 | 5.0.0 | +| 08/03/02 | RAN_15 | RP-020057 | 043 | - | Introduction of "UE Positioning Enhancements for 1.28 Mcps TDD" | 4.3.0 | 5.0.0 | +| 07/06/02 | RAN_16 | RP-020312 | 050 | 2 | Clarification of UE measurements Applicability | 5.0.0 | 5.1.0 | +| 20/09/02 | RAN_17 | RP-020578 | 053 | - | Correction to SFN-SFN Type 2 measurement | 5.1.0 | 5.2.0 | +| 20/09/02 | RAN_17 | RP-020558 | 061 | - | Correction of UE SFN-SFN type 1 measurement for TDD | 5.1.0 | 5.2.0 | +| 22/12/02 | RAN_18 | RP-020844 | 064 | - | Received Total Wide Band Power Measurement Definition | 5.2.0 | 5.3.0 | +| 24/03/03 | RAN_19 | RP-030080 | 065 | 2 | Addition of HS-SICH quality measurement for UTRA TDD | 5.3.0 | 5.4.0 | +| 24/06/03 | RAN_20 | RP-030366 | 070 | 1 | Power Measurement in non HSDPA codes for TDD | 5.4.0 | 5.5.0 | +| 24/06/03 | RAN_20 | RP-030365 | 074 | - | Correction of transmitted carrier power definition in case of Tx diversity | 5.4.0 | 5.5.0 | +| 06/01/04 | RAN_22 | RP-030651 | 071 | 4 | Definition of Transmitted Code Power and ISCP measurements in the case of antenna diversity for TDD | 5.5.0 | 5.6.0 | +| 13/01/04 | RAN_22 | - | - | - | created for M.1457 update | 5.6.0 | 6.0.0 | +| 23/03/04 | RAN_23 | RP-040088 | 069 | 1 | Interference measurement in UpPTS for 1.28Mcps TDD | 6.0.0 | 6.1.0 | +| 23/03/04 | RAN_23 | RP-040084 | 078 | 1 | Clarification of TA definition for 1.28Mcps TDD | 6.0.0 | 6.1.0 | +| 20/03/06 | RAN_31 | RP-060079 | 079 | - | Introduction of 7.68Mcps TDD option | 6.1.0 | 7.0.0 | +| 12/06/06 | RAN_32 | RP-060294 | 081 | - | Clarify the reference point for LCR TDD TA | 7.0.0 | 7.1.0 | +| 29/09/06 | RAN_33 | RP-060492 | 083 | - | Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD | 7.1.0 | 7.2.0 | +| 07/03/07 | RAN_35 | RP-070120 | 087 | - | Physical layerspecification of UE Power Headroom measurement | 7.2.0 | 7.3.0 | +| 07/03/07 | RAN_35 | RP-070118 | 086 | - | Introduction of E-DCH for 1.28Mcps TDD | 7.2.0 | 7.3.0 | +| 13/03/07 | RAN_35 | RP-070113 | 085 | 1 | Modification on the HS-SICH reception quality of HS-SICH for LCR | 7.2.0 | 7.3.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|--------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | | | | | TDD | | | +| 11/09/07 | RAN_37 | RP-070650 | 088 | - | Introduction of multi-frequency operation for 1.28Mcps TDD | 7.3.0 | 7.4.0 | +| 04/03/08 | RAN_39 | - | - | - | Creation of Release 8 further to RAN_39 decision | 7.4.0 | 8.0.0 | +| 09/09/08 | RAN_41 | RP-080667 | 0089 | - | E-UTRA measurements for UTRA TDD – E-UTRA interworking | 8.0.0 | 8.1.0 | +| 03/03/09 | RAN_43 | RP-090232 | 0091 | 2 | RSRP and RSRQ Measurement Definitions | 8.1.0 | 8.2.0 | +| 15/09/09 | RAN_45 | RP-090888 | 0092 | - | Clarification on reference point of RSRP and RSRQ for EUTRA | 8.2.0 | 8.3.0 | +| 15/09/09 | RAN_45 | RP-090891 | 0093 | - | Clarification of UE measurement definitions for RX diversity of LCR TDD | 8.2.0 | 8.3.0 | +| 01/12/09 | RAN_46 | RP-091175 | 0094 | 3 | Introduction of Cell Portion for 1.28 Mcps TDD | 8.3.0 | 9.0.0 | +| 16/03/10 | RAN_47 | RP-100205 | 0095 | 1 | Modification of RSRQ definition | 9.0.0 | 9.1.0 | +| 01/06/10 | RAN_48 | RP-100584 | 0098 | - | Correction to the reference table number for nominal maximum output power for 1.28Mcps TDD | 9.1.0 | 9.2.0 | +| 07/12/10 | RAN_50 | RP-101317 | 0099 | 2 | Introduction of MC-HSUPA for 1.28Mcps TDD | 9.2.0 | 10.0.0 | +| 01/06/11 | RAN_52 | RP-110817 | 0101 | 2 | Introduction of Cell Portion in AOA measurement for LCR TDD | 10.0.0 | 10.1.0 | +| 2012-09 | SP_57 | - | - | - | Update to Rel-11 version (MCC) | 10.1.0 | 11.0.0 | +| 10/09/14 | RAN_65 | RP-141484 | 0104 | - | Inclusion of definition of WLAN Beacon RSSI in UMTS specifications | 11.0.0 | 12.0.0 | +| 09/03/15 | RAN_67 | RP-150361 | 0103 | 3 | New E-UTRA RSRQ measurement definition | 12.0.0 | 12.1.0 | +| 07/12/15 | SP_70 | - | - | - | Creation of Release 13 further to SP_70 decision | 12.1.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | +| 2022-03 | RP-95e | - | - | - | - | Upgrade to Rel-17 version without technical change | 17.0.0 | +| 2024-03 | RP-103 | - | - | - | - | Upgrade to Rel-18 version without technical change | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/25_series/25367/raw.md b/marked/Rel-18/25_series/25367/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..71669542d2aedd1dda388d09ad476252db27a8db --- /dev/null +++ b/marked/Rel-18/25_series/25367/raw.md @@ -0,0 +1,476 @@ + + +# 3GPP TS 25.367 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Mobility procedures for Home Node B (HNB); Overall description; Stage 2 (Release 18)** --- + +![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. The '3' is black, 'G' is black, 'P' is black, and 'P' is black. There is a small red signal icon below the 'G' and 'P'. A small 'TM' symbol is located to the top right of the 'P'. + +3GPP logo + +## --- **Keywords** + +UMTS, stage 2, radio, architecture, HNB, CSG + +## **3GPP** + +## --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|-----------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 Overview..... | 7 | +| 5 CSG Identification ..... | 8 | +| 6 CSG Selection..... | 8 | +| 6.1 Manual CSG ID Selection..... | 8 | +| 7 CSG Cell Reselection..... | 9 | +| 7.1 Measurement Rules for CSG Cells ..... | 9 | +| 7.2 Reselection to CSG Cell..... | 9 | +| 7.2.1 Criteria for Intra-frequency Cell Reselection..... | 9 | +| 7.2.2 Criteria for Inter-frequency Cell Reselection..... | 9 | +| 7.2.3 Criteria for Inter-RAT Cell Reselection..... | 9 | +| 7.3 Reselection from CSG Cell ..... | 9 | +| 7.3.1 Criteria for Intra-frequency Cell Reselection..... | 9 | +| 7.3.2 Criteria for Inter-frequency Cell Reselection..... | 9 | +| 7.3.3 Criteria for Inter-RAT Cell Reselection..... | 9 | +| 7.4 Reselection from CSG Cell to CSG Cell ..... | 10 | +| 7.5 Parameters for CSG Cell Reselection ..... | 10 | +| 8 CSG and Hybrid Cell Handover ..... | 10 | +| 8.1 Handover to CSG/Hybrid Cell ..... | 10 | +| 8.1.1 CSG/Hybrid Cell Intra-frequency Measurement Procedure ..... | 11 | +| 8.1.2 CSG/Hybrid Cell Inter-frequency/Inter-RAT Measurement Procedure ..... | 12 | +| 8.2 Handover from CSG Cell..... | 13 | +| 8.3 Handover from CSG Cell to CSG Cell ..... | 13 | +| 9 Support of Hybrid Cells ..... | 13 | +| 9.1 Measurement Rules..... | 13 | +| 9.2 Reselection ..... | 13 | +| Annex B (informative): Void..... | 14 | +| Annex C (informative): Change history..... | 14 | + +# --- 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 + +This document provides a high level description of the mobility procedures applicable to Home NodeB support in the current Release. Where appropriate, the reasons behind the agreements are provided. Throughout this document, unless otherwise stated, the UE is assumed to be a current Release UE that supports the Closed Subscriber Group (CSG) feature, whether it is actually a member of a CSG or not. A UE that does not support the CSG feature is not required to support any of the procedures stated in this document. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 25.304: "UE procedures in idle mode and procedures for cell reselection in connected mode". +- [3] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [4] 3GPP TS 23.011: "Service accessibility". +- [5] 3GPP TS 22.220: "Service Requirements for Home NodeBs and Home eNodeBs". +- [6] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B (HNB)". +- [7] 3GPP TS 25.214: "Physical layer procedures (FDD)". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Acceptable Cell:** A cell that satisfies certain conditions as specified [2]. A UE can always attempt emergency calls on an acceptable cell. + +**CSG whitelist:** A list provided by NAS containing all the CSG Identities of the CSGs to which the subscriber belongs. + +NOTE: This list is known as Allowed CSG List in Rel-8 Access Stratum specifications. + +**Available PLMN:** A PLMN for which the UE has found at least one cell and read its PLMN identity. + +**Barred Cell:** A cell a UE is not allowed to camp on. + +**Camped on a cell:** UE has completed the cell selection/reselection process and has chosen a cell. The UE monitors system information and (in most cases) paging information. + +**Camped on any cell:** UE is in idle mode and has completed the cell selection/reselection process and has chosen a cell irrespective of PLMN identity. + +**Closed Subscriber Group (CSG):** A Closed Subscriber Group identifies subscribers of an operator who are permitted to access one or more cells of the PLMN but which have restricted access (CSG cells). + +**CSG Cell:** A cell, part of the PLMN, broadcasting a CSG Indicator that is set to TRUE and a specific CSG identity. A CSG cell is accessible by the members of the closed subscriber group for that CSG identity. + +**CSG Identity (CSG ID):** An identifier broadcast by a CSG/Hybrid cell or cells and used by the UE to facilitate access for authorised members of the associated Closed Subscriber Group. + +**CSG member cell:** A cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN and for which the CSG whitelist of the UE includes an entry comprising cell's CSG ID and the respective PLMN identity. + +**DRX cycle:** Individual time interval between monitoring Paging Occasion for a specific UE. + +**Equivalent PLMN list:** List of PLMNs considered as equivalent by the UE for cell selection, cell reselection, MBSFN Cluster selection MBSFN Cluster reselection and handover according to the information provided by the NAS. + +**Home NodeB (HNB):** A HNB is a customer-premises equipment that connects a 3GPP UE over UTRAN wireless air interface to a mobile operator's network using broadband IP backhaul. + +**HNB Name:** The Home NodeB Name is a broadcast string in free text format that provides a human readable name for the Home NodeB CSG identity. + +**Home PLMN:** A PLMN where the Mobile Country Code (MCC) and Mobile Network Code (MNC) of the PLMN identity are the same as the MCC and MNC of the IMSI. + +**Hybrid cell:** A cell broadcasting a CSG identity which is accessible as a CSG cell by UEs which are members of the CSG and as a normal cell by all other UEs. + +**Non-CSG Cell:** A cell that is not a CSG cell, e.g. a macro cell. + +**Process:** A local action in the UE invoked by a RRC procedure or an Idle Mode procedure. + +**Radio Access Mode:** Radio access mode of the cell, FDD or TDD. + +**Radio Access Technology:** Type of technology used for radio access, for instance UTRA or GSM. + +**Registered PLMN:** This is the PLMN on which certain Location Registration outcomes have occurred. + +**Registration Area:** (NAS) registration area is an area in which the UE may roam without a need to perform location registration, which is a NAS procedure. + +**Reserved Cell:** A cell on which camping is not allowed, except for particular UEs, if so indicated in the system information. + +**Restricted Cell:** A cell on which camping is allowed, but access attempts are disallowed for UEs whose access classes are indicated as barred. + +**Selected PLMN:** This is the PLMN that has been selected by the NAS, either manually or automatically. + +**Serving cell:** The cell on which the UE is camped. + +**Strongest cell:** The cell on a particular carrier that is considered strongest according to the layer 1 cell search procedure [7]. As the details of the layer 1 cell search are implementation dependent, the precise definition of 'strongest cell' is also implementation dependent. + +**Suitable Cell:** This is a cell on which an UE may camp. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|----|----------------| +| AS | Access Stratum | +|----|----------------| + +| | | +|--------|--------------------------------------------| +| BCCH | Broadcast Control Channel | +| CM | Connection Management | +| CN | Core Network | +| CSG | Closed Subscriber Group | +| DRX | Discontinuous Reception | +| E-UTRA | Evolved UMTS Terrestrial Radio Access | +| FDD | Frequency Division Duplex | +| GPRS | General Packet Radio Service | +| GSM | Global System for Mobile Communications | +| HCS | Hierarchical Cell Structure | +| HNB | Home NodeB | +| IMSI | International Mobile Subscriber Identity | +| MCC | Mobile Country Code | +| MM | Mobility Management | +| MNC | Mobile Network Code | +| NAS | Non-Access Stratum | +| PCH | Paging Channel | +| PI | Page Indicator | +| PICH | Page Indication Channel | +| PLMN | Public Land Mobile Network | +| RAT | Radio Access Technology | +| RRC | Radio Resource Control | +| SAP | Service Access Point | +| TDD | Time Division Duplex | +| TMGI | Temporary Mobile Group Identity | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# 4 Overview + +A Home NodeB may provide restricted access to only UEs belonging to a Closed Subscriber Group (CSG). One or more of such cells providing restricted access, known as CSG cells, are identified by a unique numeric identifier called CSG Identity. To facilitate access control, a UE with CSG subscription would have an CSG whitelist, which contains one or more CSG Identities associated with the CSG cells on which the UE is allowed access. The UE uses the CSG whitelist along with the CSG Identity and associated PLMN ID broadcast by the CSG Cells in CSG cell selection and reselection. + +A HNB can also be operated as a hybrid cell. A hybrid cell is accessed as a CSG cell by a UE whose CSG whitelist contains the cell's CSG ID and associated PLMN ID and as a normal cell by all other UEs. Members of the CSG are expected to receive preferential access according to [5]. + +NOTE: Although pre-Rel-9 UEs are able to camp on hybrid cells (which would be regarded as normal cells for access) there is no possibility for these UEs to identify a hybrid cell as a CSG cell even though the cell's CSG identity and associated PLMN ID are in the UE's CSG whitelist. + +In addition, manual selection of CSG Identity is introduced, which enables the human user to manually select a CSG Identity for UE to camp on. + +This document provides high level descriptions and procedures of the mobility features to support CSG deployment in the current Release. The following areas will be covered in the subsequent chapters: + +- Identifiers associated with the CSG framework +- Manual selection of CSG Identity +- Measurement rules for CSG Cells +- Cell reselection to a CSG cell, from a CSG cell, and between CSG cells +- Handover to a CSG cell, from a CSG cell, and between CSG cells, where applicable + +- Measurement rules, (re)selection and handover procedures for hybrid cells. + +# --- 5 CSG Identification + +One or more Closed Subscriber Group (CSG) cells are identified by a unique numeric identifier called CSG Identity or CSG ID. A UE belonging to a CSG has the corresponding CSG ID and associated PLMN ID in its CSG whitelist. The CSG whitelist is maintained and provided by NAS. The CSG ID is broadcast in system information by the CSG cell or hybrid cell, and used by the UE for cell (re)selection and handover purposes. + +A cell may optionally broadcast the CSG Indicator, whose presence and value of TRUE indicates the cell is a CSG cell. The absence of the CSG indicator in a cell which broadcasts a CSG identity indicates that it is a hybrid cell. + +A CSG cell or hybrid cell may broadcast the HNB Name, a textual identifier, in system information. The HNB Name can be used to aid the human user in manual selection of a CSG ID. + +At the physical layer, a CSG cell is identified by its carrier frequency (UARFCN) and Primary Scrambling Code (PSC). A set of PSCs could be reserved for CSG deployment and this reserved PSC range may be signalled in system information. The PSC of a CSG cell belongs to the reserved PSC range if broadcast. + +On the mixed carrier frequency shared by both non-CSG cells (UMTS macro cells) and CSG cells, CSG cells broadcast in system information the PSC range reserved by the network for CSG cells. The non-CSG cells may also broadcast the reserved PSC range. The reserved PSC range is only applicable to the UARFCN within the PLMN where the UE received this information. The UE considers the last received reserved PSC range to be valid within the entire PLMN for the duration of 24 hours. The UE may use the reserved PSC information for CSG cell search and (re)selection purposes, according to UE's implementation. + +**NOTE:** In shared network scenario, aligned PSC ranges are beneficial in the shared carrier frequency across the involved PLMNs. Furthermore, in deployments where cells broadcast different primary PLMN (with or without multiple PLMN IDs), it is beneficial that CSG and non-CSG cells will broadcast same PSC ranges. Moreover, it is beneficial if a CSG cell, if listed in system information and associated with a PLMN, is associated with the primary PLMN of the serving cell. + +Non-CSG cells and CSG cells may broadcast indications of one or more carrier frequencies used for dedicated CSG deployment. This information may be used by a UE to avoid unnecessary measurements on that frequency even when cell measurement rules would require measurements of this carrier frequency. Indications of which carrier frequencies are dedicated to CSG-only deployment may be signalled in system information and are applicable only in the cell where this information is broadcast. + +# --- 6 CSG Selection + +## 6.1 Manual CSG ID Selection + +Manual CSG ID selection enables a human user to select a CSG ID. In manual CSG ID selection the UE may scan all frequencies in the supported frequency bands and display a list of found CSG IDs or the corresponding HNB Names if broadcast by the CSG cells or hybrid cells, and indications as to whether the found CSG IDs and associated PLMN IDs are contained in the UE's CSG whitelist. When the user selects an entry in the list, the UE selects any CSG cell or hybrid cell among the ones with same CSG ID and PLMN ID. The UE may normally camp on the chosen cell if it is a CSG member cell or a hybrid cell. + +During manual CSG ID selection a UE is allowed to perform Location Registration procedure on a CSG cell that is not a CSG member cell. + +Based on the outcome of a Location Registration procedure initiated on a CSG cell, the UE's CSG whitelist is updated. + +The UE is allowed to *not* support manual CSG ID selection in connected mode. + +# 7 CSG Cell Reselection + +## 7.1 Measurement Rules for CSG Cells + +To measure CSG member cell(s), a UE applies an autonomous search function, per UE implementation, regardless of which RAT the UE is camping on. The autonomous search function determines when and where to search for the CSG member cells. + +Autonomous search procedure is disabled by the search function if UE's CSG whitelist does not exist or is empty. + +On a mixed carrier, a UE may avoid measurements of any CSG cells that are known by the UE not to be CSG member cells. + +A UE may avoid measurements of any CSG cells that are known by the UE not to be CSG member cells on the carrier frequency dedicated to CSG deployment. + +## 7.2 Reselection to CSG Cell + +The cell reselection criteria described in this section is applicable when the UE is in the following call states: Idle Mode, Cell\_PCH, URA\_PCH and Cell\_FACH states, unless otherwise stated. + +Inter-RAT and inter-frequency reselection in CELL\_FACH state only needs to be performed when second DRX is used. + +### 7.2.1 Criteria for Intra-frequency Cell Reselection + +For intra-frequency reselection from a non-CSG cell to a CSG member cell, the UE follows the same cell ranking rules as those defined for the UTRA case in [2]. The UE may ignore not allowed CSG cells in the ranking. The UE applies reselection parameters broadcast by the serving cell. A UE may normally camp on a CSG member cell. + +### 7.2.2 Criteria for Inter-frequency Cell Reselection + +For inter-frequency cell reselection, the UE considers the frequency where its CSG member cell is on to have the highest priority value, irrespective of network configured frequency priorities, as long as the CSG member cell remains best ranked on that frequency. + +### 7.2.3 Criteria for Inter-RAT Cell Reselection + +Inter-RAT reselection to a CSG member cell is supported when the UE is camped on another RAT. The UE requirements are defined in the specifications of the concerned RAT. + +## 7.3 Reselection from CSG Cell + +### 7.3.1 Criteria for Intra-frequency Cell Reselection + +For intra-frequency reselection from a CSG member cell to a non-CSG cell, the UE follows the same cell ranking rules as those defined for the UTRA case defined in [2]. + +### 7.3.2 Criteria for Inter-frequency Cell Reselection + +For inter-frequency reselection from a CSG member cell to a non-CSG cell, the UE follows the same cell ranking rules as those defined for the UTRA case defined in [2]. + +### 7.3.3 Criteria for Inter-RAT Cell Reselection + +For reselection from a CSG cell to a GSM or E-UTRA cell, the UE follows the respective procedures defined in [2]. + +## 7.4 Reselection from CSG Cell to CSG Cell + +For reselection between CSG member cells, the UE follows the same cell ranking rules as those defined for the UTRA case in [2]. + +## 7.5 Parameters for CSG Cell Reselection + +No new parameters are defined for CSG cell ranking. The same cell reselection parameters defined for the UTRA case in [2] are used for CSG cell ranking purposes, if configured. The operator may configure the cell reselection parameters, such as Qoffset and Qhyst, to bias the reselection of CSG cells. + +# --- 8 CSG and Hybrid Cell Handover + +## 8.1 Handover to CSG/Hybrid Cell + +Handover to a HNB/HeNB follows the framework as specified in [3], [6]. Handover to a HNB/HeNB is different from the normal handover procedure in four aspects: + +1. **Proximity Estimation:** in case the UE is able to determine, based on UE implementation, that it is near a CSG member cell, the UE may provide to the SRNC an indication of proximity. The CSG proximity indication may be used as follows: + - a. If a measurement configuration is not present for the concerned frequency/RAT, the SRNC may configure the UE to perform measurements and reporting for the concerned frequency/RAT. + - b. The SRNC may determine whether to perform other actions related to handover to HNB/HeNBs based on having received a proximity indication (for example, the SRNC may not configure compressed mode gaps for the UE to detect the HNB/HeNB on a different frequency/RAT unless it has received a proximity indication). +2. **PSC/PCI Confusion:** due to the typical cell size of HNB/HeNBs being much smaller than macro cells, there can be multiple HNBs/HeNBs within the coverage of the SRNC that have the same PSC/PCI. This leads to a condition referred to as PSC/PCI confusion, wherein the SRNC is unable to determine the correct target cell for handover from the PSC/PCI included in the measurement reports from the UE. PSC/PCI confusion is solved by the UE reporting the cell identity of the target HNB/HeNB. +3. **Access Control:** If the target cell is a hybrid cell, prioritization of allocated resources may be performed based on the UE's membership status. Access control is done by a two step process, where first the UE reports whether the target cell is a CSG member cell based on the UE's CSG whitelist, and then the network verifies the reported status. +4. **PLMN Report:** If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition. + +Mobility from SRNC to a CSG/hybrid cell from network perspective is described in [6]. The following two sections describe the radio aspects. The SRNC in the call flows of these sections can be an RNC or a HNB. + +### 8.1.1 CSG/Hybrid Cell Intra-frequency Measurement Procedure + +![Sequence diagram illustrating the Intra-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SRNC + Note right of SRNC: 5. Handover processing [6] + SRNC->>UE: 1. MEASUREMENT CONTROL [(Measurement Type = CSG Proximity detection)] + UE-->>SRNC: 2. MEASUREMENT REPORT [CSG Proximity Indication] + SRNC->>UE: 3. MEASUREMENT CONTROL [(CSG Intrafrequency cell info), (Intra-frequency SI Acquisition)] + UE-->>SRNC: 4. MEASUREMENT REPORT [PSC, Cell Identity, CSG Member Indication] + +``` + +The diagram shows a sequence of interactions between a User Equipment (UE) and a Serving Radio Network Controller (SRNC). The process begins with the SRNC sending a 'MEASUREMENT CONTROL' message to the UE, specifying 'CSG Proximity detection' as the measurement type. The UE responds with a 'MEASUREMENT REPORT' containing a 'CSG Proximity Indication'. The SRNC then sends another 'MEASUREMENT CONTROL' message, this time providing 'CSG Intrafrequency cell info' and requesting 'Intra-frequency SI Acquisition'. The UE replies with a 'MEASUREMENT REPORT' that includes the 'PSC', 'Cell Identity', and 'CSG Member Indication'. Finally, the SRNC initiates 'Handover processing' as described in reference [6]. + +Sequence diagram illustrating the Intra-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC. + +**Figure 8.1.1-1: Intra-frequency Measurement Procedure of CSG and Hybrid cells** + +- 1) The SRNC configures the UE with a measurement having "CSG Proximity detection" as measurement type. +- 2) The UE sends an "entering" CSG proximity indication when it determines it may be near a CSG member cell (based on UE implementation). +- 3) If a measurement configuration for CSG/hybrid cells is not present, the SRNC configures the UE with relevant measurement configuration which includes the PSCs that the UE must measure and the PSCs for which SI acquisition should be performed. The network may use the CSG proximity indication for intra-frequency case to minimize the time during which measurements for CSG/hybrid cells are configured. +- 4) The UE sends a measurement report including the measured PSC, Cell Identity, CSG ID and CSG membership indication of the target HNB to the SRNC (e.g., due to a triggered intra-frequency event 1d). The UE can acquire MIB and SIB3/SIB4 of intra-frequency target HNB cells in parallel with reception of the serving cell transmissions in CELL\_DCH. No measurement gaps are required for reading MIB and SIB3/SIB4. If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition. +- 5) SRNC can then proceed with the handover processing as described in [6]. + +After sending an "entering" CSG proximity indication (step 2), if the UE determines that it is no longer near any CSG member cell (on the reported proximate RAT and frequency), the UE sends a "leaving" CSG proximity indication to the SRNC. Upon reception of this indication, the SRNC may reconfigure the UE to stop measurements configured. + +The PSC confusion is resolved by steps 3 and 4. The SRNC can request SI acquisition and reporting for any PSC, not limited to PSCs of CSG or hybrid cells. + +### 8.1.2 CSG/Hybrid Cell Inter-frequency/Inter-RAT Measurement Procedure + +![Sequence diagram illustrating the Inter-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SRNC + Note left of UE: 6. UE reads System Information of the target HNB + Note right of SRNC: 8. Handover processing [6] + + SRNC->>UE: 1. MEASUREMENT CONTROL [(Measurement Type = CSG Proximity detection)] + UE-->>SRNC: 2. MEASUREMENT REPORT [CSG Proximity Indication] + SRNC->>UE: 3. MEASUREMENT CONTROL [ CSG Inter-frequency cell info] + UE-->>SRNC: 4. MEASUREMENT REPORT [measured PSCs] + SRNC->>UE: 5. MEASUREMENT CONTROL [(report criteria = Periodical reporting criteria), (Amount of reporting = 1), (Inter-frequency SI Acquisition)], + UE-->>SRNC: 7. MEASUREMENT REPORT [Cell Identity, CSG Member Indication] + +``` + +The diagram shows a sequence of interactions between a User Equipment (UE) and a Serving Radio Network Controller (SRNC) for inter-frequency measurement of CSG and hybrid cells. The sequence starts with the SRNC sending a measurement control to the UE with the type set to 'CSG Proximity detection'. The UE responds with a measurement report indicating it may be near a CSG member cell. The SRNC then configures a measurement on the concerned frequency/RAT to measure CSG/hybrid cells, including compressed mode gaps. The UE sends a measurement report with measured PSCs. The SRNC configures the UE for system information (SI) acquisition and reporting of a particular PSC/PCI. The UE reads the system information of the target HNB and sends a measurement report with cell identity and CSG member indication. Finally, the SRNC proceeds with handover processing. + +Sequence diagram illustrating the Inter-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC. + +**Figure 8.1.2-1: Inter-frequency Measurement Procedure of CSG and Hybrid cells.** + +- 1) The SRNC configures the UE with a measurement having "CSG Proximity detection" as measurement type. +- 2) The UE sends an "entering" CSG proximity indication when it determines it may be near a CSG member cell (based on UE implementation). The CSG proximity indication includes the RAT and frequency of the cell. +- 3) The SRNC configures a measurement on the concerned frequency/RAT to measure CSG/hybrid cells. Compressed mode gaps, if required by the UE, are also activated to allow UE to perform measurements on the reported RAT and frequency. The network may also use the proximity indication to minimize the requesting of handover preparation information of CSG/hybrid cells by avoiding requesting such information when the UE is not in the geographical area where its CSG member cells are located. +- 4) The UE sends a measurement report including the measured PSCs/PCIs. +- 5) The SRNC configures the UE to perform SI acquisition and reporting of a particular PSC/PCI. +- 6) The UE performs SI acquisition using autonomous gaps, i.e., the UE may suspend reception and transmission with the SRNC to acquire the relevant system information from the target HNB/HeNB. +- 7) The UE sends a measurement report including Cell Identity, CSG ID and CSG membership indication. If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition. +- 8) SRNC can then proceed with the handover processing. The handover processing for inter-frequency handover to a CSG/Hybrid cell is described in [6]. + +NOTE: The above steps also apply to inter-RAT mobility from UMTS cell to HeNB. + +After sending an "entering" CSG proximity indication (step 2), if the UE determines that it is no longer near any CSG member cell (on the reported proximate RAT and frequency), the UE sends a "leaving" CSG proximity indication to the SRNC. Upon reception of this indication, the SRNC may reconfigure the UE to stop measurements on the reported RAT and frequency. + +In the above procedure, step 2 may not be performed in case the UE has not previously visited the HNB, e.g., when the UE first visits a CSG/hybrid cell. + +The PSC/PCI confusion is resolved by steps 5, 6 and 7. The SRNC can request SI acquisition and reporting for any PSC/PCI, not limited to PSCs/PCIs of CSG or hybrid cells. + +## 8.2 Handover from CSG Cell + +In Cell\_DCH state, the handover procedure from a CSG member cell to a non-CSG cell is expected to be the same as the procedure specified in [3]. + +## 8.3 Handover from CSG Cell to CSG Cell + +In Cell\_DCH state, handover between CSG member cells with the same CSG ID is expected to be the same as the procedure specified in Section 8.1. + +In Cell\_DCH state, handover between CSG member cells with different CSG IDs is expected to be the same as the procedure specified in Section 8.1. + +# --- 9 Support of Hybrid Cells + +## 9.1 Measurement Rules + +To measure for hybrid cells with a CSG Identity and its associated PLMN ID belonging to an entry in the UE's CSG whitelist, measurement rules of Chapter 7.1 apply. Otherwise, normal measurement rules apply. + +NOTE: The autonomous search for hybrid cells does not imply that UE need to constantly check the CSG ID of all cells it sees. + +## 9.2 Reselection + +In case the UE has CSG ID and its associated PLMN ID of the hybrid cell in its CSG whitelist, cell reselection procedures will be the same as for a CSG cell as described in Chapter 7.2. + +For all other UEs, cell reselection procedures will utilise normal cell reselection rules. + +# Annex B (informative): Void + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 2008-11-17 | RAN2#64 | | | | | Proposal for 25.367 TS structure and Text Proposals | 0.0.0 | +| 2008-11-20 | RAN2#64 | | | | | Revision based on discussion for email agreement. | 0.0.1 | +| 2008-11-21 | RAN2#64 | | | | | Final text proposals for email agreement. | 0.0.2 | +| 2008-11-25 | RAN2#64 | | | | | Revision based on email agreement. | 1.0.0 | +| 2008-12 | RP-42 | RP-080873 | - | - | | v1.0.0 was approved at RAN #42 as v8.0.0 and put under CR control | 8.0.0 | +| 2009-03 | RP-43 | RP-090135 | 0001 | 1 | | Corrections to manual CSG search | 8.1.0 | +| | RP-43 | RP-090135 | 0002 | 1 | | Allignment to latest stage 3 agreements | 8.1.0 | +| 2009-06 | RP-44 | RP-090524 | 0003 | - | | Idle mode requirements to support hybrid cells for HNB | 9.0.0 | +| 2009-09 | RP-45 | RP-090930 | 0005 | 4 | | CR capturing HNB inbound mobility agreements | 9.1.0 | +| | RP-45 | RP-090911 | 0008 | - | | Correction to manual CSG ID selection 25.367CR(R9) | 9.1.0 | +| 2009-12 | RP-46 | RP-091343 | 0010 | 1 | | CR on Add Hybrid cell into the manual CSG ID selection in 25.367 | 9.2.0 | +| | RP-46 | RP-091343 | 0011 | 2 | | Draft CR capturing HNB inbound mobility agreements | 9.2.0 | +| | RP-46 | RP-091343 | 0012 | - | | Removal of description related to small repetition of SIB3/4 | 9.2.0 | +| | RP-46 | RP-091343 | 0014 | 1 | | Renaming Allowed CSG List (25.367 Rel-9) | 9.2.0 | +| | RP-46 | RP-091330 | 0015 | - | | Correction to definition of CSG cell. | 9.2.0 | +| 2010-03 | RP-47 | RP-100306 | 0017 | - | | CR capturing HNB inbound mobility agreements | 9.3.0 | +| 2010-06 | RP-48 | RP-100551 | 0018 | - | | Some corrections to 25.367 | 9.4.0 | +| 2010-12 | RP-50 | RP-101206 | 0019 | - | | Correction to the limitation of SI acquisition | 9.5.0 | +| 2011-03 | RP-51 | - | - | - | | Upgrade to the Release 10 - no technical change | 10.0.0 | +| 2012-06 | RP-56 | RP-120880 | 0026 | - | | PSC range note on RAN sharing | 11.0.0 | +| 2013-03 | RP-59 | RP-130247 | 0028 | 1 | | Corrections on mobility to CSG and hybrid cells for UMTS | 11.1.0 | +| 2013-12 | RP-62 | RP-131998 | 0030 | 1 | | Introduction of inbound mobility to shared CSG/hybrid cell | 12.0.0 | +| | RP-62 | RP-131998 | 0031 | - | | Introduction of CSG CELL_FACH mobility | 12.0.0 | +| 2015-12 | RP-70 | | | | | Upgrade to the Release 13 - no technical change | 13.0.0 | +| 2017-03 | RP-75 | | | | | Upgrade to Release 14 - no technical change | 14.0.0 | +| 2018-06 | SA-80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | +| 2022-03 | RP-95e | - | - | - | - | Upgrade to Rel-17 version without technical change | 17.0.0 | +| 2024-03 | RP-103 | - | - | - | - | Upgrade to Rel-18 version without technical change | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/25_series/25410/raw.md b/marked/Rel-18/25_series/25410/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6db757bb8be45e03218bf1d10b830c34d5a76c72 --- /dev/null +++ b/marked/Rel-18/25_series/25410/raw.md @@ -0,0 +1,1102 @@ + + +# 3GPP TS 25.410 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu Interface: general aspects and principles (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 3.3 Specification Notations ..... | 8 | +| 4 General Aspects ..... | 9 | +| 4.1 UTRAN Architecture ..... | 9 | +| 4.1.1 Iu Interface Architecture..... | 9 | +| 4.1.2 I u connection principles ..... | 10 | +| 4.1.3 Implementation of the NAS Node Selection Function..... | 10 | +| 4.1.4 Implementation of MOCN configuration support..... | 10 | +| 4.2 I u Interface General Principles ..... | 10 | +| 4.3 I u Interface Specification Objectives..... | 10 | +| 4.4 I u Interface Capabilities..... | 11 | +| 4.5 I u Interface Characteristics ..... | 12 | +| 4.5.1 Use of Transport Network User Plane as Signalling Bearer ..... | 12 | +| 4.5.1.1 Use of SCCP..... | 12 | +| 4.5.1.1.1 General ..... | 12 | +| 4.5.1.1.2 SCCP Connection Establishment procedure..... | 12 | +| 4.5.1.1.3 SCCP Connection Release procedure ..... | 14 | +| 4.5.1.1.4 General SCCP Abnormal Conditions..... | 15 | +| 4.5.1.2 Use of MTP3b..... | 15 | +| 4.5.2 Use of Transport Network User Plane as User Data Bearer..... | 15 | +| 4.5.2.1 Use of AAL2..... | 15 | +| 4.5.2.2 Use of GTP-U ..... | 15 | +| 4.5.2.3 Use of RTP..... | 15 | +| 4.5.3 Use of Transport Network User Plane on Iu-BC..... | 15 | +| 5 Functions of the I u Interface Protocols & Functional Split..... | 16 | +| 5.1 General ..... | 16 | +| 5.2 RAB management Functions ..... | 18 | +| 5.2.1 RAB establishment, modification and release function ..... | 18 | +| 5.2.2 RAB characteristics mapping to Uu bearers function ..... | 18 | +| 5.2.3 RAB characteristics mapping to I u transport bearers..... | 18 | +| 5.2.4 RAB queuing, pre-emption and priority function ..... | 18 | +| 5.3 Radio Resource Management over I u ..... | 19 | +| 5.3.1 Radio resource admission control ..... | 19 | +| 5.3.2 Broadcast information management..... | 19 | +| 5.4 I u link Management functions ..... | 19 | +| 5.4.1 I u Signalling Link Management function ..... | 19 | +| 5.4.2 ATM Virtual Connection Management function ..... | 19 | +| 5.4.3 AAL2 connection establish and release function ..... | 19 | +| 5.4.4 AAL5 management function ..... | 19 | +| 5.4.5 GTP-U tunnels management function ..... | 19 | +| 5.4.6 TCP Management Function..... | 20 | +| 5.4.7 Buffer Management..... | 20 | +| 5.4.8 RTP Session Management Function ..... | 20 | +| 5.5 I u U-plane (RNL) Management Functions ..... | 20 | +| 5.5.1 I u U-plane frame protocol mode selection function..... | 20 | +| 5.5.2 I u U-plane frame protocol initialisation ..... | 20 | +| 5.6 Mobility Management Functions ..... | 20 | +| 5.6.1 Location information update function ..... | 20 | +| 5.6.2 Handover and Relocation functions ..... | 21 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------|-----------| +| 5.6.2.1 | Inter RNC hard HO function, Iur not used or not available ..... | 21 | +| 5.6.2.2 | Serving RNS Relocation function..... | 21 | +| 5.6.2.3 | Inter system Handover (e.g. UMTS-GSM) function ..... | 21 | +| 5.6.2A | Inter System Change (e.g. UMTS-GSM) function..... | 21 | +| 5.6.3 | Paging Triggering ..... | 21 | +| 5.6.4 | Shared Networks Access Control..... | 21 | +| 5.6.5 | GERAN System Information Retrieval..... | 21 | +| 5.7 | Security Functions..... | 21 | +| 5.7.1 | Data Confidentiality ..... | 21 | +| 5.7.1.1 | Radio interface ciphering function ..... | 21 | +| 5.7.1.2 | Ciphering key management function..... | 22 | +| 5.7.2 | Data integrity ..... | 22 | +| 5.7.2.1 | Integrity checking ..... | 22 | +| 5.7.2.2 | Integrity key management ..... | 22 | +| 5.8 | Service and Network Access Functions..... | 22 | +| 5.8.1 | Core Network signalling data transfer function ..... | 22 | +| 5.8.2 | Data Volume Reporting..... | 22 | +| 5.8.3 | UE Tracing ..... | 22 | +| 5.8.4 | Location reporting function ..... | 22 | +| 5.8.5 | MDT ..... | 22 | +| 5.9 | Co-ordination Functions..... | 22 | +| 5.9.1 | Paging Co-ordination function ..... | 22 | +| 5.9.2 | NAS Node Selection Function ..... | 23 | +| 5.9.3 | Information Transfer Function ..... | 23 | +| 5.9.4 | MOCN Rerouting Function..... | 23 | +| 5.9.5 | SIPTO at Iu-PS Function..... | 23 | +| 5.9.6 | SIPTO at the Local Network with Standalone GW..... | 23 | +| 5.10 | MBMS Functions..... | 23 | +| 5.10.1 | MBMS RAB Management functions ..... | 23 | +| 5.10.2 | MBMS UE Linking Function..... | 23 | +| 5.10.3 | MBMS Registration Control Function ..... | 23 | +| 5.10.4 | MBMS Enquiry Function ..... | 24 | +| 6 | I u Interface Protocol Structure..... | 24 | +| 6.1 | General ..... | 24 | +| 6.2 | Iu-CS ..... | 25 | +| 6.3 | Iu-BC..... | 25 | +| 6.4 | Iu-PS ..... | 27 | +| 7 | Other I u Interface Specifications ..... | 27 | +| 7.1 | UTRAN I u Interface: Layer 1 (3GPP TS 25.411) ..... | 27 | +| 7.2 | UTRAN I u Interface: Signalling Transport (3GPP TS 25.412) ..... | 27 | +| 7.3 | UTRAN I u Interface: RANAP Specification (3GPP TS 25.413)..... | 27 | +| 7.4 | UTRAN I u Interface: Data Transport and Transport Signalling (3GPP TS 25.414)..... | 28 | +| 7.5 | UTRAN I u Interface: CN-UTRAN User Plane Protocol (3GPP TS 25.415)..... | 28 | +| 7.6 | UTRAN I u Interface: Service Area Broadcast Protocol SABP (3GPP TS 25.419) ..... | 28 | +| 7.7 | Summary ..... | 28 | +| Annex A (informative): | Change History..... | 29 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is an introduction to the 3GPP TS 25.41x series of Technical Specifications that define the Iu interface for the interconnection of Radio Network Controller (RNC) component of the UMTS Terrestrial Radio Access Network (UTRAN) to the Core Network of the UMTS system. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.401: "UTRAN Overall Description". +- [2] 3GPP TR 23.930: "Iu Principles". +- [3] 3GPP TS 23.110: "UMTS Access Stratum Services and Functions". +- [4] 3GPP TS 25.411: "UTRAN Iu Interface Layer 1". +- [5] 3GPP TS 25.412: "UTRAN Iu Interface Signalling Transport". +- [6] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". +- [7] 3GPP TS 25.414: "UTRAN Iu Interface Data Transport and Transport Signalling". +- [8] 3GPP TS 25.415: "UTRAN Iu Interface User Plane Protocols". +- [9] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part". +- [10] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages". +- [11] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes". +- [12] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures". +- [13] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [14] 3GPP TS 25.419: "UTRAN Iu Interface: Service Area Broadcast Protocol SABP". +- [15] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". +- [16] ITU-T Recommendation Q.2630.1: "AAL type 2 signalling protocol - (Capability Set 1)". +- [17] ITU-T Recommendation Q.2630.2: "AAL type 2 signalling protocol - Capability Set 2". +- [18] IETF RFC 3332 (2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)". +- [19] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real Time Applications". +- [20] IETF RFC 768 (1980-08): "User Datagram Protocol". + +- [21] IETF RFC 793 (1981-09): "TCP, Transmission Control Protocol". +- [22] IETF RFC 791 (1981-09): "Internet Protocol". +- [23] Void +- [24] Void +- [25] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [26] 3GPP TS 23.251: "Network sharing; Architecture and functional description". +- [27] 3GPP TS23.246: Multimedia Broadcast/Multicast Service (MBMS) Architecture and functional description +- [28] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2". +- [29] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [30] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TS 25.401 [1] apply. + +### **MBMS related terms and definitions:** + +**MBMS bearer service:** as defined in TS 23.246 [27]. + +**MBMS RAB:** as defined in TS 25.346 [28]. + +**MBMS Iu signalling connection:** as defined in TS 25.346 [28]. + +**MBMS session start:** as defined in TS 25.346 [28]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|------------------------------------------------------| +| 3G-MSC | 3 rd Generation Mobile Switching Centre | +| 3G-SGSN | 3 rd Generation Serving GPRS Support Node | +| AAL | ATM Adaptation Layer | +| ATM | Asynchronous Transfer Mode | +| BC | Broadcast | +| BSSMAP | Base Station Subsystem Management Application Part | +| CBS | Cell Broadcast Service | +| CC | Connection Confirm | +| CN | Core Network | +| CR | Connection Release | +| CREF | Connection Refusal | +| CS | Circuit Switched | +| GT | Global Title | +| GTP-U | GPRS Tunnelling Protocol | +| GWCN | Gateway Core Network | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | + +| | | +|----------|--------------------------------------------------| +| ISDN | Integrated Services Digital Network | +| L-GW | Local GateWay | +| LA | Location Area | +| M3UA | MTP3 User Adaptation Layer | +| MBMS | Multimedia Broadcast Multicast Service | +| MDT | Minimization of Drive-Tests | +| MOCN | Multi Operator Core Network | +| NAS | Non Access Stratum | +| NACC | Network Assisted Cell Change | +| NNSF | NAS Node Selection Function | +| O&M | Operation and Maintenance | +| PLMN | Public Land Mobile Network | +| PS | Packet Switched | +| PSTN | Public Switched Telephone Network | +| PVC | Permanent Virtual Circuit | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| RA | Routing Area | +| RAB | Radio Access Bearer | +| RANAP | Radio Access Network Application Part | +| RIM | RAN Information Management | +| RLP | Radio Link Protocol | +| RNC | Radio Network Controller | +| RNL | Radio Network Layer | +| RRC | Radio Resource Control | +| RTCP | Real Time Control Protocol | +| RTP | Real Time Protocol | +| SA | Service Area | +| SABP | Service Area Broadcast Protocol | +| SAP | Service Access Point | +| SCCP | Signalling Connection Control Part | +| SIPTO | Selected IP Traffic Offload | +| SIPTO@LN | Selected IP Traffic Offload at the Local Network | +| SCTP | Stream Control Transmission Protocol | +| SNA | Shared Network Area | +| SPC | Signalling Point Code | +| SRNS | Serving Radio Network Subsystem | +| SSN | Sub-System Number | +| SVC | Switched Virtual Circuit | +| S-GW | Serving GateWay | +| TCP | Transmission Control Protocol | +| UE | User Equipment | +| UDP | User Datagram Protocol | +| UP | User Plane | +| URA | UTRAN Registration Area | +| UTRAN | UMTS Terrestrial Radio Access Network | +| VC | Virtual Circuit | + +## 3.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +| | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure | When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Radio Network Layer procedures. | +| Message | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message. | + +| | | +|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Frame | When referring to a control or data frame in the specification the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DCH transport frame. | +|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# 4 General Aspects + +## 4.1 UTRAN Architecture + +### 4.1.1 Iu Interface Architecture + +The overall UMTS architecture and UTRAN architectures are described in TS 25.401 [1]. This subclause specifies only the architecture of the Iu interface, and shall not constrain the network architecture of either Core or Radio Access Networks. + +The Iu interface is specified at the boundary between the Core Network and UTRAN. Figure 4.1 depicts the logical division of the Iu interface. From the Iu perspective, the UTRAN access point is an RNC. + +![Figure 4.1: Iu Interface Architecture diagram showing UTRAN (Node B, RNC) connected to Core Network (CN) domains (CS, PS, BC) via the Iu interface.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +The diagram illustrates the Iu Interface Architecture. On the left, the UTRAN (Radio Access Network) contains four Node B units connected to two RNC (Radio Network Controller) units. The RNC units are connected to the Core Network (CN) on the right via the Iu interface, which is represented by a vertical dashed line. The CN is divided into three domains: CS (Circuit Switched) Domain, PS (Packet Switched) Domain, and BC (Broadcast) Domain. The Iu interface is logically divided into three segments: Iu-CS (towards the CS Domain), Iu-PS (towards the PS Domain), and Iu-BC (towards the BC Domain). The RNC units are connected to these segments as follows: the top RNC connects to Iu-CS and Iu-PS, while the bottom RNC connects to Iu-PS and Iu-BC. + +Figure 4.1: Iu Interface Architecture diagram showing UTRAN (Node B, RNC) connected to Core Network (CN) domains (CS, PS, BC) via the Iu interface. + +Figure 4.1: Iu Interface Architecture + +The Iu interface towards the PS-domain of the core network is called Iu-PS, and the Iu interface towards the CS-domain is called Iu-CS. The differences between Iu-CS and Iu-PS are treated elsewhere in the present document. The Iu interface to the Broadcast domain is called Iu-BC. + +There shall not be more than one Iu interface (Iu-PS) towards the PS-domain from any one RNC – except where the NNSF is used, see subclause 4.1.3, or in MOCN configuration – see TS 23.251 [26]. Each RNC shall not have more than one Iu interface (Iu-CS) towards its default CN node within the CS domain, but may also have further Iu interfaces (Iu-CS) towards other CN nodes within the CS domain. (See [6] for definition of Default CN node.) These further Iu interfaces (Iu-CS) shall only be used as a result of intra-MSC inter-system handover or SRNS relocation, in the case the anchor CN node directly connects to the target RNC. There may also be more than one Iu interface towards the CS-Domain if the NNSF is used – see subclause 4.1.3, or in MOCN configuration – see TS 23.251 [26]. There shall not be more than one Iu interface (Iu-BC) from an RNC towards the Broadcast domain. + +In the separated core network architecture, this means that there shall be separate signalling and user data connections towards the PS and CS domains – this applies in both transport and radio network layers. + +In the combined architecture, there shall be separate connections in the user plane towards the PS and CS domains (in both transport and radio network layers). In the control plane, there shall be separate SCCP connections to the two logical domains. + +In either architecture, there can be several RNCs within UTRAN and so UTRAN may have several Iu access points towards the Core Network. As a minimum, each Iu access point (in UTRAN or CN) shall independently fulfil the requirements of the relevant Iu specifications (25.41x series – see clause 7). + +### 4.1.2 Iu connection principles + +The Iu interface has a hierarchical architecture where one higher layer entity controls several lower layer entities. The hierarchy for the CN - UTRAN signalling connection end points is described below: + +- Each CN Access Point may be connected to one or more UTRAN Access Points. +- For the PS domain, each UTRAN Access Point shall not be connected to more than one CN Access Point – except where the NNSF is used, see subclause 4.1.3, or when RNC is shared in MOCN configuration.. +- For the CS domain, each UTRAN Access Point may be connected to one or more CN Access Points. +- For the BC domain, each UTRAN Access Point may be connected to one CN Access Point only. + +### 4.1.3 Implementation of the NAS Node Selection Function + +The optional NAS Node Selection Function (NNSF) is described in TS 23.236 [25]. + +If the NAS Node Selection Function is used by an RNC: + +- There may be more than one Iu interface (Iu-CS) towards the CS domain and/or more than one Iu interface (Iu-PS) towards the PS-domain from this RNC. + +### 4.1.4 Implementation of MOCN configuration support + +The MOCN configuration is described in TS 23.251 [26]. When the RNC is shared in MOCN configuration: + +- There may be more than one Iu interface (Iu-CS) towards the CS domain of different CN operators and/or more than one Iu interface (Iu-PS) towards the PS-domain of different CN operators from this RNC. +- The MOCN Rerouting Function shall be supported. + +## 4.2 Iu Interface General Principles + +From a UTRAN perspective, maximising the commonality of the various protocols that flow on the Iu interface is desirable. This means at the minimum that: + +- A common set of radio access bearer services will be offered by UTRAN to the Core Network nodes, regardless of their type (e.g. 3G-MSC or 3G-SGSN). + +There will be a common functional split between UTRAN and the Core Network nodes, regardless of their type (e.g. 3G-MSC or 3G-SGSN). + +Signalling in the radio network control plane shall not depend on the specific choice of transport layers. + +## 4.3 Iu Interface Specification Objectives + +The following objectives are partly derived from TR 23.930 [2]. + +The Iu interface shall be specified such that it can support: + +- the interconnection of RNCs with Core Network Access Points within a single PLMN, and within several PLMNs in case of network sharing, as described in TS 23.251 [26]. + +- the interconnection of RNCs with Core Network Access Points irrespective of the manufacturer of any of the elements. +- all UMTS services. + +The Iu interface shall facilitate the use of the same RNC, MSC or SGSN in all PLMNs. + +The Iu interface shall facilitate the sharing of transport technology between Iu-PS and Iu-BC. + +The Iu interface shall allow interworking to the GSM Core Network. + +Independence between the protocol layers and between control and user planes shall be maintained on the Iu interface. + +The Iu interface shall allow independent evolution of technologies within the Core, Radio Access and Transport Networks. + +The Iu interface shall allow separate evolution of O&M facilities. + +The Iu interface shall be standardised as an open and multi-vendor interface. + +The Iu interface specifications shall facilitate the migration of some services from the CS-domain to the PS-domain. In particular, the RANAP protocol shall be common to both PS and CS domains, and the Iu user plane protocol(s) shall be independent of the core network domain (PS or CS), except where a specific feature is only required for one domain. + +## 4.4 Iu Interface Capabilities + +The following capabilities are derived from the requirements described in TR 23.930 [2]. + +The Iu interface supports: + +- procedures to establish, maintain and release Radio Access Bearers; +- procedures to perform SRNS relocation, intra-system handover, inter-system handover and inter-system change; +- procedures to support the Cell Broadcast service; +- a set of general procedures, not related to a specific UE; +- the separation of each UE on the protocol level for user specific signalling management; +- the transfer of NAS signalling messages between UE and CN; +- location services by transferring requests from the CN to UTRAN, and location information from UTRAN to CN. The location information may comprise a geographical area identifier or global co-ordinates with uncertainty parameters; +- simultaneous access to multiple CN domains for a single UE; +- mechanisms for resource reservation for packet data streams; +- procedures to support MBMS bearer services; +- mechanisms to support SIPTO at Iu-PS for a specific UE (optional); +- mechanisms to support SIPTO at the Local Network with standalone GW for a specific UE (optional). + +## 4.5 Iu Interface Characteristics + +### 4.5.1 Use of Transport Network User Plane as Signalling Bearer + +#### 4.5.1.1 Use of SCCP + +##### 4.5.1.1.1 General + +The SCCP (ITU-T Rec. Q.711 [9] /ITU-T Rec. Q.712 [10]/ITU-T Rec. Q.713 [11]/ITU-T Rec. Q.714 [12]) is used to support signalling messages between the CNs and the RNC. One user function of the SCCP, called Radio Access Network Application Part (RANAP), is defined. The RANAP uses one SCCP signalling connection per active UE and CN for the transfer of layer 3 messages. RANAP also uses one SCCP signalling connection per MBMS bearer service. + +Both connectionless and connection-oriented procedures are used to support the RANAP. TS 25.413 [6] explains whether connection oriented or connectionless services should be used for each layer 3 procedure. + +RANAP may use SSN, SPC and/or GT and any combination of them as addressing schemes for the SCCP. Which of the available addressing scheme to use for the SCCP is an operator matter. + +When GT addressing is utilised, the following settings shall be used: + +- SSN Indicator = 1 (RANAP SSN as defined in TS 23.003 [13] shall always be included). +- Global Title Indicator = 0100 (GT includes translation type, numbering plan, encoding scheme and nature of address indicator). +- Translation Type = 0000 0000 (not used). +- Numbering Plan = 0001 (E.163/4). +- Nature of Address Indicator = 000 0100 (International Significant Number). +- Encoding Scheme = 0001 or 0010 (BCD, odd or even). +- Routing indicator = 0 or 1 (route on GT or PC/SSN). + +When used, the GT shall be the E.164 address of the relevant node. + +The following subclauses describe the use of SCCP connections for RANAP transactions. Subclause 4.5.1.2 describes the connection establishment procedures. Subclause 4.5.1.3 describes the connection release procedures. Subclause 4.5.1.4 describes abnormal conditions. + +##### 4.5.1.1.2 SCCP Connection Establishment procedure + +A new SCCP connection is established when information related to the communication between a UE and the network has to be exchanged between RNC and CN, and no SCCP connection exists between the CN and the RNC involved, for the concerned UE. A new SCCP connection is also established for MBMS service purpose between the RNC and CN. + +Various SCCP connection establishment cases have to be distinguished: + +- i) RNC Initiated SCCP Signalling Connection for a UE; +- ii) CN Initiated SCCP Signalling Connection for a UE; +- iii) CN Initiated SCCP Signalling Connection for an MBMS Service. + +The above cases are the only cases currently identified for SCCP connection establishment. Others may emerge in the future. + +###### 4.5.1.1.2.1 Establishment procedure in case i + +The SCCP signalling connection establishment is initiated, by the RNC, at the reception of the first layer 3 non access stratum message from the UE or at the execution of the enhanced relocation or at the initiation of the UE Registration Query procedure. + +###### Initiation + +The RNC sends SCCP CONNECTION REQUEST message to the Core Network. A RANAP message shall be included in the user data field of the SCCP CONNECTION REQUEST message when the RANAP message size is less than or equal to the maximum size of the user data field in the SCCP CONNECTION REQUEST message. When the RANAP message is longer than the maximum size, the user data field shall not be included in the SCCP CONNECTION REQUEST message. + +If the Core Network receives an SCCP CONNECTION REQUEST message for a UE for which an SCCP connection already exists, or if the Core Network receives an SCCP CONNECTION REQUEST message that does not include a user data field, and later finds out that the SCCP CONNECTION REQUEST message was for a UE for which an SCCP connection already exists, the Core Network shall ensure that the new SCCP connection and the already existing SCCP connection are for the same UE, e.g. by security functions, and if so, release the already existing SCCP connection via the normal Iu Release procedure and all UTRAN resources allocated to it. + +###### Termination + +- **successful outcome** + - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP message in the user data field, is returned to the RNC. +- **unsuccessful outcome** + - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the RNC. This message may contain a RANAP message in the user data field. + +For more information on how the RANAP procedures Initial UE Message, Enhanced Relocation Complete and UE Registration Query are handled, please see the elementary procedures Initial UE Message, Enhanced Relocation Complete and UE Registration Query in TS 25.413 [6]. + +![](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg) + +| RNC | CN | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| CR {SSN=RANAP, a1=x, RANAP message or no user data}
-----> | | +| CC {a1=y, a2=x, RANAP message or no user data}
<----- | | +| or | | +| CREF{a2=x, RANAP message or no user data}
<----- | | +| a1 = source local reference,
a2 = destination local reference,
x = SCCP connection reference at the RNC,
y = SCCP connection reference at the CN. | | + +**Figure 4.2: Setting-up of RNC Initiated SCCP Signalling Connection** + +###### 4.5.1.1.2.2 Establishment procedure in case ii + +The SCCP signalling connection establishment is initiated, by the Core Network, in connection with performing a Relocation. + +###### Initiation + +The Core Network initiates the connection establishment by sending an SCCP CONNECTION REQUEST message to the RNC. Optionally, a RANAP message may be included in the user data field of the SCCP CONNECTION REQUEST message. + +###### Termination + +- **successful outcome** + - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP message in the user data field, is returned to the Core Network. +- **unsuccessful outcome** + - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the Core Network. This message may contain a RANAP message in the user data field. + +![Sequence diagram showing the setting-up of a CN Initiated SCCP Signalling Connection between RNC and CN. The RNC sends a CR message to the CN. The CN responds with either a CC message or a CREF message. A legend defines the variables: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the RNC, and y is SCCP connection reference at the CN.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + Note right of RNC: a1 = source local reference, +a2 = destination local reference, +x = SCCP connection reference at the RNC, +y = SCCP connection reference at the CN. + RNC->>CN: CR {SSN=RANAP, a1=y, RANAP message or no user data} + Note left of CN: <----- + CN-->>RNC: CC {a1=x, a2=y, RANAP message or no user data} + Note right of CN: -----> + Note left of CN: or + CN-->>RNC: CREF{a2=y, RANAP message or no user data} + Note right of CN: -----> + +``` + +Sequence diagram showing the setting-up of a CN Initiated SCCP Signalling Connection between RNC and CN. The RNC sends a CR message to the CN. The CN responds with either a CC message or a CREF message. A legend defines the variables: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the RNC, and y is SCCP connection reference at the CN. + +**Figure 4.3: Setting-up of CN Initiated SCCP Signalling Connection** + +###### 4.5.1.1.2.3 Establishment procedure in case iii + +The SCCP signalling connection establishment is initiated, by the Core Network, to establish a new SCCP connection between the RNC and the CN for an MBMS service at the start of an MBMS session and when no SCCP connection already exists between the CN and the RNC involved, for the concerned MBMS service. + +###### Initiation + +The Core Network initiates the connection establishment by sending an SCCP CONNECTION REQUEST message to the RNC. Optionally, a RANAP message may be included in the user data field of the SCCP CONNECTION REQUEST message. + +###### Termination + +- **successful outcome** + - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP message in the user data field, is returned to the Core Network. +- **unsuccessful outcome** + - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the Core Network. This message may contain a RANAP message in the user data field. + +##### 4.5.1.1.3 SCCP Connection Release procedure + +This procedure is always initiated at the Core Network side in normal release case. + +An SCCP connection is released when the CN realises that a given signalling connection is no longer required. + +The CN sends a SCCP RELEASED message. + +The procedure may be initiated at the Core Network side and the RNC side in any abnormal release case. + +##### 4.5.1.1.4 General SCCP Abnormal Conditions + +If a user-out-of-service information or signalling-point-inaccessible information is received by the RANAP, no new attempt to establish SCCP connections towards the affected point code will be started until the corresponding user-in-service information or signalling-point-accessible information is received. + +When a user-out-of-service information or signalling-point-inaccessible is received by the RNC, an optional timer may be started. When the timer expires, all the SCCP connections towards the affected point code will be released. When the user-in-service or signalling-point-accessible is received, the timer is stopped. + +If for any reason an SCCP connection is released, the optional timer expires or a connection refusal is received while any of the RANAP procedures are being performed or while a dedicated resource is still allocated, the following actions are taken: + +###### At RNC: + +- Any RNC procedure relating to that connection is abandoned. +- The UTRAN resources allocated to the connection are released. + +###### At Core Network: + +- The resources associated with the SCCP connection are cleared as soon as possible. + +#### 4.5.1.2 Use of MTP3b + +- For a given MSC, the RNC shall be able to access RANAP and ALCAP either under the same MTP3b (IETF RFC 3332 [18]) destination point code, or under different point codes; +- For a given RNC, the MSC shall be able to access RANAP and ALCAP either under the same MTP3b destination point code, or under different point codes. + +### 4.5.2 Use of Transport Network User Plane as User Data Bearer + +#### 4.5.2.1 Use of AAL2 + +In the ATM transport option AAL2 is used as the user data bearer towards the CS domain. + +Q.2630.2 is used as the protocol for dynamically setup AAL-2 connections over Iu towards the CS domain. Q.2630.2 adds new optional capabilities to Q.2630.1. + +#### 4.5.2.2 Use of GTP-U + +GTP-U is used as the user data bearer towards the PS domain. + +RANAP Signalling is used to establish, modify and release the GTP-U tunnels towards the PS domain. + +#### 4.5.2.3 Use of RTP + +RTP/UDP/IP (IETF RFC 1889 [19]/ IETF RFC 768 [20]/ IETF RFC 791[22]) is used as the user data bearer towards the CS domain in the IP transport option. The use of RTCP (IETF RFC 1889 [19]) is optional. + +RANAP Signalling is used to establish, modify and release RTP sessions towards the CS domain. + +### 4.5.3 Use of Transport Network User Plane on Iu-BC + +TCP/IP (IETF RFC 793[21]/ IETF RFC 791[22]) is used as the bearer for the radio network layer protocol over Iu-BC. + +The TCP connection is normally established by the CN using standard TCP procedures. + +A new TCP connection is established by the RNC only when there is information (e.g. failure or restart indications) that needs to be sent from RNC to the CN, and there is no existing TCP connection. The RNC shall establish the connection using standard TCP procedures. + +The node that established the connection shall release the TCP connection. + +# --- 5 Functions of the Iu Interface Protocols & Functional Split + +## 5.1 General + +This subclause defines the functional split between the core network and the UMTS radio access network. In addition, the possible interaction between the functions is defined. The functional split is shown in table 5.1. + +Table 5.1: Iu interface functional split + +| Function | UTRAN | CN | +|-----------------------------------------------------|-------|----| +| RAB management functions: | | | +| RAB establishment, modification and release | X | X | +| RAB characteristics mapping Iu transmission bearers | X | | +| RAB characteristics mapping Uu bearers | X | | +| RAB queuing, pre-emption and priority | X | X | +| Radio Resource Management functions: | | | +| Radio Resource admission control | X | | +| Broadcast Information | X | X | +| Iu link Management functions: | | | +| Iu signalling link management | X | X | +| ATM VC management | X | X | +| AAL2 establish and release | X | X | +| AAL5 management | X | X | +| GTP-U Tunnels management | X | X | +| TCP Management | X | X | +| Buffer Management | X | | +| Iu U-plane (RNL) Management: | | | +| Iu U-plane frame protocol management | | X | +| Iu U-plane frame protocol initialization | X | | +| Mobility management functions: | | | +| Location information reporting | X | X | +| Handover and Relocation | | | +| Inter RNC hard HO, Iur not used or not available | X | X | +| Serving RNS Relocation (intra/inter MSC) | X | X | +| Inter system hard HO (UMTS-GSM) | X | X | +| Inter system Change (UMTS-GSM) | X | X | +| Paging Triggering | | X | +| GERAN System Information Retrieval | X | X | +| Security Functions: | | | +| Data confidentiality | | | +| Radio interface ciphering | X | | +| Ciphering key management | | X | +| User identity confidentiality | X | X | +| Data integrity | | | +| Integrity checking | X | | +| Integrity key management | | X | +| Service and Network Access functions: | | | +| CN Signalling data | X | X | +| Data Volume Reporting | X | | +| UE Tracing | X | X | +| MDT | X | X | +| Location reporting | X | X | +| QoE | X | X | +| Iu Co-ordination functions: | | | +| Paging co-ordination | X | X | +| NAS Node Selection Function | X | | +| MOCN Rerouting Function | X | X | +| SIPTO at Iu-PS | X | X | +| SIPTO at the Local Network with Standalone GW | X | X | +| MBMS functions | X | X | +| MBMS RAB Management | X | X | +| MBMS UE Linking Function | X | X | +| MBMS Registration Control Function | X | X | + +| Function | UTRAN | CN | +|-----------------------|-------|----| +| MBMS Enquiry Function | X | X | + +## 5.2 RAB management Functions + +### 5.2.1 RAB establishment, modification and release function + +The RAB, Radio Access Bearer, is defined to be set-up between UE and CN. Depending on subscription, service, requested QoS etc. different types of RABs will be used. It is the CN that controls towards the UTRAN the establishment, modification or release of a RAB. Furthermore, the CN selects the type of the transport bearer, i.e. ATM or IP. + +The RAB identity is allocated by CN by mapping the value for the NAS Binding information (from the actual protocol IE for the respective CN domain) to the RAB ID as specified in TS 23.110 [3]. The RAB identity is globally significant on both the radio bearer and on the Iu bearer for a given UE in a particular CN domain. + +RAB establishment, modification and release is a CN initiated function. + +RAB establishment, modification and release is a UTRAN executed function. + +RAB release request is a UTRAN initiated function, triggered when UTRAN e.g. fails to keep the RAB established with the UE. + +### 5.2.2 RAB characteristics mapping to Uu bearers function + +The RAB characteristics mapping function is used to map the radio access bearers to the Uu bearers. The mapping is performed during the establishment of the RAB. UTRAN shall perform the mapping between the bearers. + +RAB mapping to Uu transmission bearers is a UTRAN function. + +### 5.2.3 RAB characteristics mapping to Iu transport bearers + +The RAB characteristics mapping function is used to map the radio access bearers to the Iu interface transport bearers. The mapping is performed during the establishment of the RAB. + +UTRAN shall perform this mapping between the bearers if AAL2 is used, since it is the UTRAN that establishes the AAL2 connections. + +In case of RAB towards the PS domain, UTRAN shall perform the mapping between the radio access bearers and the IP layer. + +RAB characteristics mapping to Iu transport bearers is a UTRAN function. + +### 5.2.4 RAB queuing, pre-emption and priority function + +The allocation/retention priority level of a RAB is determined by the CN based on e.g. subscription information, QoS information etc. Accordingly, the CN shall request RAB establishment or modification with an indication of the priority level and the pre-emption capability of that RAB and the queuing vulnerability. Queuing and resource pre-emption shall be performed by UTRAN accordingly. + +RAB queuing, pre-emption and allocation/retention priority handling is a UTRAN controlled function. + +RAB queuing, pre-emption and allocation/retention priority setting is a CN function. + +## 5.3 Radio Resource Management over Iu + +### 5.3.1 Radio resource admission control + +When UTRAN receives a request to establish or modify a radio access bearer from the CN, the current radio resource situation is analysed and the admission control either accepts or rejects the request. This is called "Radio resource admission control" and is handled by the UTRAN. If the request is queued, it is handled by the RAB queuing, pre-emption and priority function. + +### 5.3.2 Broadcast information management + +This function consists in the broadcast from network toward UE of some information in the coverage area of the whole network or different parts of the network. + +There are two kinds of Broadcast information management. UTRAN broadcast information, and Cell Broadcast information management. All UTRAN broadcast information management shall be handled locally within UTRAN. All Cell Broadcast information is controlled by CN and executed by UTRAN. + +## 5.4 Iu link Management functions + +### 5.4.1 Iu Signalling Link Management function + +The Iu signalling link management function provides a reliable transfer of the radio network signalling between UTRAN and CN. Both CN and UTRAN manage the function. + +This function is in particular responsible for Iu signalling connection establishment, which can be established either by the CN or the RNC and for Iu signalling connection release, which is controlled by CN possibly upon UTRAN request. + +### 5.4.2 ATM Virtual Connection Management function + +This function refers to handling of ATM Virtual Connections (VCs) between CN and UTRAN. + +This function shall be used to establish, maintain and release the ATM VCs. For permanent VCs, it is regarded to be an O&M function. + +This function also includes the selection of a Virtual Circuit to be used for a particular RAB. The selection of ATM VC upon an Iu radio access bearer service request, shall be done by UTRAN. The selected VC shall fulfil the requirements of the request. The VC may consist of several sublinks: such as SCCP connections, AAL2 connections or IP flows. + +### 5.4.3 AAL2 connection establish and release function + +This function is used to establish and release the AAL type 2 connections between CN and UTRAN upon an Iu radio access bearer service request. Both UTRAN and CN are taking part in the establishment of AAL2 connection. UTRAN shall initiate both establishment and release of AAL2 connections. In abnormal cases, the CN may also initiate release of AAL2 connections. The use of AAL2 for Iu transmission bearers depends on type of CN. + +### 5.4.4 AAL5 management function + +AAL5 connections between CN and UTRAN shall be pre-configured at system initialisation. Basic configuration is PVCs. For user data, SVC is possible. + +The AAL5 management is a function handled by both the CN and the UTRAN. + +### 5.4.5 GTP-U tunnels management function + +This function is used to establish and release GTP-U tunnels between CN and UTRAN upon a radio access bearer service request. This involves assigning a tunnel identifier for each direction and the creation of a context containing the tunnel information. The tunnel identifier for the downlink is allocated by the UTRAN, and the tunnel identifier for the + +uplink is allocated by the CN. Both CN and UTRAN should maintain the context. The use of GTP-U for Iu transport bearers depends on type of CN. + +### 5.4.6 TCP Management Function + +This function is used to establish and release the TCP connections between CN and UTRAN over Iu-BC. + +The TCP management function exists in both UTRAN and CN. + +### 5.4.7 Buffer Management + +Congestion control shall be performed over the Iu user plane using buffer management and no flow control. + +This function includes buffers to store received packet data units that at reception can not be processed due to e.g. congestion. In UTRAN, there must be a buffer management function handling received packets from the peer CN node. + +The used mechanism is not in the scope of the present document and not relevant to be standardised. + +Buffer management is a UTRAN function. + +### 5.4.8 RTP Session Management Function + +This function is used to establish and release RTP sessions between CN and UTRAN upon a radio access bearer service request. This involves assigning a RTP session identifier for each direction and the creation of a context containing the RTP session information. The RTP session identifier for the downlink is allocated by the UTRAN, and the RTP session identifier for the uplink is allocated by the CN. Both CN and UTRAN should maintain the RTP session context. The use of RTP for Iu transport bearers depends on type of CN. + +## 5.5 Iu U-plane (RNL) Management Functions + +### 5.5.1 Iu U-plane frame protocol mode selection function + +The Iu UP in the Radio Network Layer provides modes of operation that can be activated on RAB basis. For a given RAB, the Iu UP operates either in a Transparent or in Support mode. Iu U-plane frame protocol mode is selected by the CN. A set of appropriate U-plane version(s) is indicated within RANAP. The final U-plane version is selected during the Iu UP initiation procedure among the indicated version(s). + +This function is a CN function. + +### 5.5.2 Iu U-plane frame protocol initialisation + +Iu U-plane frame protocol is initialised by the UTRAN. In certain cases, as described in TS 23.153 [15], the Iu U-plane frame protocol may be initialised by the CN. + +## 5.6 Mobility Management Functions + +### 5.6.1 Location information update function + +Some functionality within the CN, needs information about the present location of an active UE, i.e. a UE with established signalling connection. The Location information update function is used to transfer this information from the UTRAN to the CN. It is the UTRAN responsibility to send this information initially at the signalling connection establishment for a UE and at any change of the UE location as long as the signalling connection exists. For this function, the location information shall be at Location and Routing Area level. + +### 5.6.2 Handover and Relocation functions + +#### 5.6.2.1 Inter RNC hard HO function, Iur not used or not available + +This functionality includes procedures for handover from one RNC to another RNC when Iur interface is not used or is not available, i.e. soft handover is not possible. The connection is switched in the CN, so both UTRAN and CN are involved. Both intra and inter CN entity cases are applicable. This functionality includes also the moving of the Serving RNS functionality from one RNC to another RNC. + +#### 5.6.2.2 Serving RNS Relocation function + +This functionality allows moving the Serving RNS functionality from one RNC to another RNC, e.g. closer to where the UE has moved during the communication. The Serving RNS Relocation procedure may be applied when active cell management functionality has created a suitable situation for it. Both UTRAN and CN are involved. + +#### 5.6.2.3 Inter system Handover (e.g. UMTS-GSM) function + +Inter system handover is performed when a mobile hands over between cells belonging to different systems such as GSM and UMTS. For intersystem handover between UMTS and GSM, the GSM procedures are used within the GSM network. Both UTRAN and CN are involved. + +NOTE: The GSM BSSMAP procedures are outside the scope of the present document. + +### 5.6.2A Inter System Change (e.g. UMTS-GSM) function + +Inter system change is performed when a GPRS attached mobile moves from cells belonging to different systems such as GSM and UMTS. For intersystem change between UMTS and GSM, the GPRS procedures are used within the GPRS network. Both UTRAN and CN are involved. + +### 5.6.3 Paging Triggering + +The Core Network shall, when considered necessary, trigger the Location/Routing/RNC Area paging in the UTRAN system. + +### 5.6.4 Shared Networks Access Control + +The Shared Networks Access Control function allows the CN to request the UTRAN to apply UE specific access control to the UTRAN and the neighbouring networks on a PLMN or an SNA basis. The Shared Networks Access Control function is further described in TS 25.401 [1]. + +### 5.6.5 GERAN System Information Retrieval + +In order to provide the UE with system information related to NACC towards a GERAN system - to be used as an optimisation - the GERAN System Information Retrieval function allows the source system to request GERAN (via CN) to provide this system information. The request and subsequent transfer of the GERAN System Information is performed transparently with the RIM function. The RIM function is further described in TS 25.401 [1] + +## 5.7 Security Functions + +### 5.7.1 Data Confidentiality + +#### 5.7.1.1 Radio interface ciphering function + +The radio interface shall be ciphered upon request of the Core Network. Both Signalling and user data may be subject to ciphering. The ciphering shall be done within UTRAN. + +#### 5.7.1.2 Ciphering key management function + +The ciphering key and the permitted algorithm shall be supplied by the CN. UTRAN selects the used algorithm. + +### 5.7.2 Data integrity + +#### 5.7.2.1 Integrity checking + +The purpose of the integrity check is to make sure that the signalling continues between the same elements as by authentication. The integrity check shall be done within the UTRAN. + +#### 5.7.2.2 Integrity key management + +The integrity key and the permitted algorithm shall be supplied by the CN. UTRAN selects the used algorithm. + +## 5.8 Service and Network Access Functions + +### 5.8.1 Core Network signalling data transfer function + +The NAS CN signalling data such as Call Control (CC), Session Management (SM), Mobility Management (MM), Short Message Services Point to Point and Supplementary Services (SS) shall be transparently conveyed between the CN and the UE. Over the Iu interface, the same Iu interface channel that is used for the UTRAN-CN signalling shall be used. + +### 5.8.2 Data Volume Reporting + +The data volume reporting function is used to report the volume of unacknowledged data to the CN. The function shall be in the UTRAN and is triggered from the CN. + +### 5.8.3 UE Tracing + +This feature allows tracing of various events related to the UE and its activities. This is an O&M functionality. + +### 5.8.4 Location reporting function + +The positioning function performs the determination of the geographical position and optionally the velocity for an UE. The location reporting function transfers the positioning information between the UTRAN and the CN according to CN commands. This function involves UTRAN and CN. + +### 5.8.5 MDT + +This feature enables the transfer of MDT measurements collected by the UE, as defined in TS 37.320 [30]. This is an O&M functionality. + +## 5.9 Co-ordination Functions + +### 5.9.1 Paging Co-ordination function + +The two CN domain architecture implies need for a page co-ordination, i.e. handling of page triggered by one CN node when UE has a signalling connection to the other CN node. The paging co-ordination is performed by UTRAN and/or optionally by CN. The Common ID is used for UTRAN paging co-ordination. The CN provides the UTRAN with the Common ID. + +The paging co-ordination is a UTRAN function. Optionally the paging co-ordination may be performed in the CN. + +### 5.9.2 NAS Node Selection Function + +The optional NAS Node Selection Function enables the RNC to initially assign CN resources to serve a UE and subsequently setup a signalling connection to the assigned CN resource. + +The method by which the RNC initially assigns CN resources is implementation dependent. + +The NNSF is described in detail in TS 23.236 [25]. + +### 5.9.3 Information Transfer Function + +The Information Transfer function allows configuration data to be passed from the CN to the RNC upon CN trigger. This function is operated in acknowledged mode. It should be used by the CN to maintain alignment between the data as configured in the CN and the configuration data provided to the UTRAN. This may be used e.g. to coordinate the SNA geographical definition (LA to SNA mapping) between CN and UTRAN in order to apply access control on an SNA basis. + +### 5.9.4 MOCN Rerouting Function + +Rerouting is a mechanism used as part of the assignment of CN operator in shared networks with MOCN configuration for network sharing non-supporting UEs when they perform initial attach/registration. In this case RNC may not know towards which CN to route the initial UE request message and the latter may be rerouted to another CN via RNC. + +The MOCN Rerouting Function is described in detail in TS 23.251 [26]. + +### 5.9.5 SIPTO at Iu-PS Function + +If supported, SIPTO at Iu-PS Function provides the capability to offload certain PS RABs from the CN at RAB setup. The SIPTO at Iu-PS is implementation dependent and may be implemented in a separate entity outside of RNS, for further information see TS 23.060 [29]. + +### 5.9.6 SIPTO at the Local Network with Standalone GW + +SIPTO@LN provides access to a defined IP network (e.g. the Internet) without the user plane traversing the mobile operator's core network by using standalone GW (with S-GW and L-GW collocated) in the local network, as specified in TS 23.060 [29]. + +## 5.10 MBMS Functions + +### 5.10.1 MBMS RAB Management functions + +The MBMS RAB, Radio Access Bearer, is defined to be set-up between the CN and one or several UEs for MBMS. Depending on the MBMS service characteristics, different types of MBMS RABs will be used. It is the CN that controls towards the UTRAN the establishment, update or release of an MBMS RAB. The MBMS RAB is defined for the PS domain only. + +### 5.10.2 MBMS UE Linking Function + +This function provides the RNC with the list of MBMS services that a given UE, with existing dedicated Iu-PS signalling connection, has "joined" or has "left" TS 23.246 [27]. + +### 5.10.3 MBMS Registration Control Function + +This function allows the RNC to either register or deregister to the PS core network domain for a specific MBMS bearer service so that it is notified whenever a session of this service starts. + +It also allows the CN to inform the RNC that a given MBMS bearer service is no longer available. + +### 5.10.4 MBMS Enquiry Function + +This function allows the RNC to request to the SGSN the list of MBMS bearer services that a given UE has “joined” TS 23.246 [27] or the IP Multicast Address and APN defined in TS 23.246 [27] which correspond to a given MBMS bearer service. + +# --- 6 Iu Interface Protocol Structure + +## 6.1 General + +The Radio Network signalling over Iu consists of the Radio Access Network Application Part (RANAP). The RANAP protocol consists of mechanisms to handle all procedures between the CN and UTRAN. It is also capable of conveying messages transparently between the CN and the UE without interpretation or processing by the UTRAN. + +Over the Iu interface the RANAP protocol is, e.g. used for: + +- Facilitate a set of general UTRAN procedures from the Core Network such as paging -notification as defined by the notification SAP in TS 23.110 [3]. +- Separate each User Equipment (UE) on the protocol level for mobile specific signalling management as defined by the dedicated SAP in TS 23.110 [3]. +- Transfer of transparent non-access signalling as defined in the dedicated SAP in TS 23.110 [3]. +- Request of various types of UTRAN Radio Access Bearers through the dedicated SAP in TS 23.110 [3]. +- Perform the SRNS Relocation function. +- Perform the various MBMS procedures. +- Perform SIPTO at Iu-PS (optional). + +The Radio Access Bearers are provided by the Access Stratum. + +Over Iu-BC, a datagram mechanism is used, so there is no clear separation of control and user planes, and the SABP protocol is used for data transfer and signalling. + +## 6.2 Iu-CS + +Figure 6.1 shows the protocol structure for Iu-CS, following the structure described in TS 25.401 [1]. + +![Protocol stack diagram for Iu-CS interface showing Control Plane, User Plane, and Transport Network Control Plane layers.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +The diagram illustrates the protocol stack for the Iu-CS interface, organized into three main vertical sections: Control Plane, User Plane, and Transport Network Control Plane. All three sections share a common 'Radio Network Layer' at the top and a common 'Physical Layer' at the bottom. + +- Control Plane:** The 'Radio Network Layer' contains the 'RANAP' protocol. Below it, the 'Transport Network Control Plane' contains 'Q.2630.2', 'Q.2150.1', 'MTP3b', 'SSCF-NNI', 'SSCOP', and 'AAL5'. The 'Transport User Plane' (part of the Transport Network Layer) contains 'SCCP', which is further divided into 'M3UA', 'MTP3b', 'SSCF-NNI', 'SCTP', 'SSCOP', 'IP', and 'AAL5'. This section ends with 'Data Link' and 'ATM' layers. +- User Plane:** The 'Radio Network Layer' contains the 'Iu UP Protocol Layer'. Below it, the 'Transport User Plane' contains 'AAL2', 'RTP/RTCP\*)', and 'UDP/IP'. This section ends with 'ATM' and 'Data Link' layers. +- Transport Network Control Plane:** This central section contains the protocols 'Q.2630.2', 'Q.2150.1', 'MTP3b', 'SSCF-NNI', 'SSCOP', and 'AAL5', which connect to the 'ATM' layer. + +Vertical arrows indicate the flow of data and signaling between the layers within each plane. Horizontal dashed lines separate the Control Plane, User Plane, and Transport Network Control Plane sections. + +Protocol stack diagram for Iu-CS interface showing Control Plane, User Plane, and Transport Network Control Plane layers. + +\*) RTCP is optional. + +Figure 6.1: Iu –Interface Protocol Structure towards CS Domain + +## 6.3 Iu-BC + +Figure 6.2 shows the protocol structure for the Iu-BC. + +![Protocol stack diagram for Iu interface towards Broadcast Domain. It shows layers from Radio Network Layer down to Physical Layer, with a specific SA Broadcast Plane highlighted in a dashed box.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +The diagram illustrates the protocol stack for the Iu interface towards the Broadcast Domain. It is divided into two main sections: the Radio Network Layer and the Transport Network Layer. + +- Radio Network Layer:** Contains the SA Broadcast Plane, which includes the SABP Protocol Layer. +- Transport Network Layer:** Contains the Transport User Plane and the Network Plane. The Network Plane is highlighted with a dashed box and includes the following layers from top to bottom: + - TCP + - IP + - AAL5 + - ATM + - Physical Layer +- Connections:** + - A vertical arrow points from the Network Plane (IP layer) up to the SABP Protocol Layer in the SA Broadcast Plane. + - Vertical arrows point from the Transport User Plane down to the TCP layer. + - Double-headed vertical arrows connect the AAL5 layer to the ATM layer and the IP layer to the Data Link layer. + +Protocol stack diagram for Iu interface towards Broadcast Domain. It shows layers from Radio Network Layer down to Physical Layer, with a specific SA Broadcast Plane highlighted in a dashed box. + +Figure 6.2: Iu Interface Protocol Structure towards Broadcast Domain + +## 6.4 Iu-PS + +Figure 6.3 shows the protocol structure for Iu-PS, following the structure described in TS 25.401 [1]. + +![Figure 6.3: Iu Interface Protocol Structure towards PS Domain. The diagram illustrates the protocol stack for the Iu-PS interface, divided into Control Plane and User Plane, running over the Transport Network Layer.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +The diagram shows the protocol structure for the Iu-PS interface towards the PS Domain. It is organized into two main vertical sections: Control Plane and User Plane, both situated above the Transport Network Layer. + +- Control Plane:** + - Radio Network Layer:** Contains the RANAP protocol. + - Transport Network Layer:** RANAP connects to the SCCP layer. The SCCP layer is supported by a stack of protocols: MTP3-B, M3UA, SCTP, SSCF-NNI, SSCOP, IP, and AAL5. Below this, the stack splits into ATM and Data Link, which both connect to the Physical Layer. +- User Plane:** + - Radio Network Layer:** Contains the Iu UP Protocol Layer. + - Transport Network Layer:** The Iu UP Protocol Layer connects to a stack of protocols: GTP-U, UDP, IP, and AAL5. Below this, the stack splits into ATM and Data Link, which both connect to the Physical Layer. +- Transport Network Control Plane:** A central section of the Transport Network Layer, currently empty in this diagram. + +Figure 6.3: Iu Interface Protocol Structure towards PS Domain. The diagram illustrates the protocol stack for the Iu-PS interface, divided into Control Plane and User Plane, running over the Transport Network Layer. + +Figure 6.3: Iu Interface Protocol Structure towards PS Domain + +# 7 Other Iu Interface Specifications + +## 7.1 UTRAN Iu Interface: Layer 1 (3GPP TS 25.411) + +TS 25.411 [4] specifies the range of physical layer technologies that may be used to support the Iu interface. + +## 7.2 UTRAN Iu Interface: Signalling Transport (3GPP TS 25.412) + +TS 25.412 [5] specifies the signalling bearers for the RANAP and transport network control plane protocols for both Iu-PS and Iu-CS. + +## 7.3 UTRAN Iu Interface: RANAP Specification (3GPP TS 25.413) + +TS 25.413 [6] specifies the RANAP protocol for radio network control plane signalling over the Iu interface. + +## 7.4 UTRAN Iu Interface: Data Transport and Transport Signalling (3GPP TS 25.414) + +TS 25.414 [7] specifies the transport bearers for the user plane of the Iu interface. It also specifies the protocol used to control these transport bearers. + +## 7.5 UTRAN Iu Interface: CN-UTRAN User Plane Protocol (3GPP TS 25.415) + +TS 25.415 [8] specifies the user plane frame handling protocol for the Iu interface. + +## 7.6 UTRAN Iu Interface: Service Area Broadcast Protocol SABP (3GPP TS 25.419) + +TS 25.419 [14] specifies the communication requirements over the Iu interface towards the BC domain. + +## 7.7 Summary + +The present document, 3GPP TS 25.410, specifies the general aspects and principles of the Iu interface as a whole. + +The relationship between the other technical specifications that define the UTRAN Iu interface is shown in figure 7.1. + +![Figure 7.1: Summary of Iu Interface Specification Structure. This diagram illustrates the relationship between various 3GPP specifications across different layers of the Iu interface. The top layer is the Radio Network Layer, which contains three planes: Control Plane (spec 25.413), User Plane (spec 25.415), and SA Broadcast Plane (spec 25.419). The middle layer is the Transport Network Layer, which is divided into Transport User Plane (spec 25.412 for Control Plane, 25.415 for User Plane, and 25.419 for SA Broadcast Plane) and Transport Network Control Plane (spec 25.414). The bottom layer is a common Transport Network Control Plane (spec 25.411). Arrows indicate the flow of data and control between these layers and specifications.](49a49278cad196bdfe0db6b4dd1be7fd_img.jpg) + +The diagram shows the specification structure for the Iu interface across three layers: + +- Radio Network Layer:** Contains three planes: Control Plane (25.413), User Plane (25.415), and SA Broadcast Plane (25.419). +- Transport Network Layer:** Divided into Transport User Plane and Transport Network Control Plane. The Transport User Plane for the Control Plane is 25.412. The Transport Network Control Plane for the User Plane and SA Broadcast Plane is 25.414. The Transport User Plane for the User Plane is 25.415. +- Common Transport Network Control Plane:** Specification 25.411. + +Arrows indicate the relationship between the layers: Control Plane (25.413) ↔ Transport User Plane (25.412) ↔ Common Transport Network Control Plane (25.411); User Plane (25.415) ↔ Transport Network Control Plane (25.414) ↔ Common Transport Network Control Plane (25.411); SA Broadcast Plane (25.419) ↔ Transport User Plane (25.419) ↔ Common Transport Network Control Plane (25.411). + +Figure 7.1: Summary of Iu Interface Specification Structure. This diagram illustrates the relationship between various 3GPP specifications across different layers of the Iu interface. The top layer is the Radio Network Layer, which contains three planes: Control Plane (spec 25.413), User Plane (spec 25.415), and SA Broadcast Plane (spec 25.419). The middle layer is the Transport Network Layer, which is divided into Transport User Plane (spec 25.412 for Control Plane, 25.415 for User Plane, and 25.419 for SA Broadcast Plane) and Transport Network Control Plane (spec 25.414). The bottom layer is a common Transport Network Control Plane (spec 25.411). Arrows indicate the flow of data and control between these layers and specifications. + +Figure 7.1: Summary of Iu Interface Specification Structure + +# Annex A (informative): Change History + +| Date / TSG | TSG Doc | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|----------------------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.0.0 | 8.0.0 | +| RP-43 | RP-090078 | 0068 | 1 | RANAP: Enhanced Relocation Complete Request in SCCP: Connection Request | 8.1.0 | +| 12/2009 | - | - | - | Created version 9.0.0 based on v. 8.1.0 | 9.0.0 | +| 12/2010 | - | - | - | Created version 10.0.0 based on v. 9.0.0 | 10.0.0 | +| RP-50 | RP-101389 | 0070 | - | Introduction of the SIPTO at Iu-PS Function | 10.0.0 | +| SP-49 | SP-100629 | - | - | Clarification on the use of References (TS 21.801 CR#0030) | 10.1.0 | +| RP-51 | RP-110230 | 0074 | 1 | Support for MDT | 10.1.0 | +| RP-52 | RP-110684 | 0075 | - | Correction of references | 10.2.0 | +| 09/2012 | - | - | - | Update to Rel-11 version (MCC) | 11.0.0 | +| RP-62 | RP-131909 | 0076 | 6 | Introduction of Standalone GW for SIPTO@LN | 12.0.0 | +| RP-70 | RP-152088 | 0077 | 1 | Introduction of improvements to CS/PS coordination in UTRAN Shared Network | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RAN#75 | RP-170545 | 0079 | 1 | B | Introduction of QMC for streaming services | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-03 | SA#95-e | - | - | - | - | Promotion to Release 17 without technical change | 17.0.0 | +| 2024-03 | SA#103- | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/25_series/25411/raw.md b/marked/Rel-18/25_series/25411/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dcbd887b7ef78064e03a8652a2b551644960f203 --- /dev/null +++ b/marked/Rel-18/25_series/25411/raw.md @@ -0,0 +1,270 @@ + + +# 3GPP TS 25.411 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface layer 1 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in small black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | | +|-------------------------------|-------------------------------------|-----------| +| 1 | Scope..... | 5 | +| 2 | References..... | 5 | +| 3 | Abbreviations..... | 6 | +| 4 | Iu Layer 1 ..... | 6 | +| 4.1 | Introduction ..... | 6 | +| 4.2 | Layer 1 Description..... | 6 | +| 4.2.1 | Layer 1 Synchronised ..... | 6 | +| 4.2.2 | [IP – Layer 1 Unsynchronised]..... | 8 | +| 4.3 | Requirements from higher layer..... | 8 | +| 4.4 | Services Provided by Layer 1..... | 8 | +| 4.4.1 | ATM Transport..... | 8 | +| 4.5 | Interface to Management Plane..... | 8 | +| 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 allowed to implement Layer 1 on the Iu interface. + +The specification of transmission delay requirements and O&M requirements are not in the scope of the present document. + +In the following 'Layer 1' and 'Physical Layer' are assumed to be synonymous. + +# --- 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.432.2 (1996-08): "ISDN User-Network interfaces, Layer 1 Recommendations, 155 520 kbit/s and 622 080 kbit/s operation". +- [2] Void. +- [3] ITU-T Recommendation G.703 (1998-10): "Physical/electrical characteristics of hierarchical digital interfaces". +- [4] ITU-T Recommendation G.704 (1998-10): "Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels". +- [5] ITU-T Recommendation G.957 (1995-07): "Optical interfaces for equipments and systems relating to the synchronous digital hierarchy". +- [6] ITU-T Recommendation I.432.1 (1996-08): "ISDN User-Network interfaces, Layer 1 Recommendations, General characteristics". +- [7] ITU-T Recommendation G.823 (2000-03): "The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy". +- [8] ITU-T Recommendation G.824 (2000-03): "The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy". +- [9] ITU-T Recommendation G.825 (2001-08): "The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH)". +- [10] ITU-T Recommendation G.826 (1996-08): "Error performance parameters and objectives for international, constant bit rate digital paths at or above the primary rate". +- [11] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification". +- [12] ATM Forum AF-PHY-0016.000 (1994-09): "DS1 Physical Layer Specification". +- [13] ATM Forum AF-PHY-0064.000 (1996-09): "E1 Physical Layer Interface Specification". +- [14] ATM Forum AF-PHY-0086.001 (1999-02): "Inverse Multiplexing for ATM (IMA) Specification Version 1.1". + +- [15] ITU-T Recommendation G.751 (1988-11): "Digital multiplex equipments operating at the third order bit rate of 34 368 kbit/s and the fourth order bit rate of 139 264 kbit/s and using positive justification". +- [16] ITU-T Recommendation G.811 (1997-02): "Timing Characteristics of Primary Reference Clocks". +- [17] ITU-T Recommendation G.804 (1998-02): "ATM cell mapping into plesiochronous digital hierarchy (PDH)". +- [18] Standard ECMA-226: "Private Integrated Services Network (PISN) - Mapping Functions for the Employment of Dedicated Circuit Mode Connections as Inter-PTNX Connections (MAPPING-CM-STATIC)". +- [19] ITU-T Recommendation I.431 (1988-11): "Primary rate user-network interface - Layer 1 specification". + +# --- 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------| +| ATM | Asynchronous Transfer Mode | +| HEC | Header Error Control | +| IMA | Inverse Multiplexing on ATM | +| IP | Internet Protocol | +| PDH | Plesiochronous Digital Hierarchy | +| PMD | Physical Media Dependent | +| PHY-SAP | Physical Service Access Point | +| SDH | Synchronous Digital Hierarchy | +| SDU | Service Data Unit | +| SONET | Synchronous Optical Networking | + +# --- 4 Iu Layer 1 + +## 4.1 Introduction + +The main functions of Layer 1 are summarised in the following: + +- Interface to physical medium; +- [ATM-Cell delineation]; +- Line clock extraction capability; +- Layer 1 alarms extraction and generation; +- In-sequence delivery; +- Transmission quality control. + +## 4.2 Layer 1 Description + +### 4.2.1 Layer 1 Synchronised + +When the Layer 1 Synchronised option is used (i.e. PDH/SDH/SONET links), the following requirements shall be met: + +Layer 1 reference configuration shall be according to ITU-T Rec. I.432.1 [6]. + +The physical layer is divided into: + +- Physical Media Dependent (PMD) sublayer; +- Transmission Convergence (TC) sublayer defined according to ITU-T Rec. I.432.1 [6]. + +The PMD shall comply with at least one of the following standards: + +- ETSI STM-4 (622 Mb/s) interface according to ITU-T Rec. I.432.2 [1] with optical S-4.1 interface according to ITU-T Rec. G.957 [5]. +- SONET STS-12c (622 Mb/s) interface according to ANSI, T1.105-1995 with optical multimode. +- SONET STS-3c (155 Mb/s) interface according to ANSI, T1.105-1995 with optical multimode. +- ETSI STM-1 (155 Mb/s) interface according to ITU-T Rec. I.432.2 [1] with electrical interface (CMI) to ITU-T Rec. G.703 [3]. +- ETSI STM-1 (155 Mb/s) interface according to ITU-T Rec. I.432.2 [1] with optical S-1.1 interface according to ITU-T Rec. G.957 [5]. +- ITU STS-1 (51 Mb/s) interface according to ANSI, T1.105-1995 with electrical interface. +- ITU STM-0 (51 Mb/s) interface according to ETSI/TTC with electrical interface. +- ITU STM-0 (51 Mb/s) interface according to ETSI/TTC with optical S-1.1 interface according to ITU-T Rec. G.957 [5]. +- J2, 6.3 Mb/s interface according to Japanese standard JT-G.703 (ITU-T Rec. G.703 [3]) and JT-G.704 (ITU-T Rec. G.704 [4]) (75 Ohm). + +NOTE: J2 requires that the ATM cells be mapped into the physical layer according to HEC based mapping in ITU-R Rec. G.804 [17]. + +- E2, 8Mb/s according to ETSI/ITU G.703 (ITU-T Rec. G.703 [3]) and G.704 (ITU-T Rec. G.704 [4]) (75 Ohm). +- E3, 34 Mb/s interface according to ETSI/ITU G.751 (ITU-T Rec. G.751 [15]) (75 Ohm). +- T3, 45 Mb/s interface according to ANSI/ITU G.703 (ITU-T Rec. G.703 [3]) and G.704 (ITU-T Rec. G.704 [4]) (75 Ohm). +- E1, 2Mb/s interface balanced 120 Ohm symmetrical according to ETS 300 420 (Standard ECMA-226 [18]), ITU-T Rec. G.704 [4] and TBR 013 (ITU-T Rec. G.703 [3]), and AF-PHY-0064.000 [13]. +- E1, 2Mb/s according to ITU-T Rec. G.703 [3] and ITU-T Rec. G.704 [4] (75 Ohm), and AF-PHY-0064.000 [13]. +- J1, 1.5 Mb/s interface according to JT-I.431-a (ITU-T Rec. I.431 [19]) (100 Ohm). +- J1, 1.5 Mb/s interface according to JT-G.703 (ITU-T Rec. G.703 [3]) and JT-G.704 (ITU-T Rec. G.704 [4]) (110 Ohm). +- T1, 1.5 Mb/s interface according to AF-PHY-0016.000 [12] and ITU-T Rec. G.703 [3] and ITU-T Rec. G.704 [4] (100 Ohm). + +Services provided to the upper layer shall be independent from the used underlying technology. + +The support of intervening transport networks - like PDH or SDH terrestrial links, Point-to-point or Point-to-Multipoint radio links - shall not be prevented. + +When using E1, T1, or J1, it shall be possible to use inverse multiplexing of ATM (IMA) (ATM Forum AF-PHY-0086.001 [14]) within suitable subsets of the physical ports on the respective Exchange Termination (ET). + +The jitter and wander performance requirements on the interface shall be in accordance with network limits for output wander at traffic interfaces of either Reference ITU-T Rec. G.823 [7], ITU-T Rec. G.824 [8] or network limits for the maximum output jitter and wander at any hierarchical interface of Reference ITU-T Rec. G.825 [9], whichever is applicable. + +The synchronisation reference extracted from the Iu may be used as UTRAN synchronisation reference. A general recommendation is to supply a traceable synchronisation reference according to reference ITU-T Rec. G.811 [16]. + +Transmission quality control shall be provided according to ITU-T Rec. G.826 [10]. + +### 4.2.2 [IP – Layer 1 Unsynchronised] + +When Layer 1 unsynchronised option is used, the following requirements shall be met: + +The support of any suitable physical layer - like Ethernet L1 or other suitable point-to-point or point-to-multipoint techniques - shall not be prevented. + +## 4.3 Requirements from higher layer + +No specific requirements beyond the ones listed in the introduction have been identified. + +## 4.4 Services Provided by Layer 1 + +### 4.4.1 ATM Transport + +The physical layer provides services to the upper layer via the Physical Service Access Point (PHY-SAP) according to ITU-T I.361 [11], as described in the following figure: + +![Diagram showing the SAP between Physical Layer and ATM Layer. The ATM Layer is at the top, connected to the Physical Layer at the bottom via a PHY-SAP (represented by an oval).](740442c999390734911677f01af0316d_img.jpg) + +The diagram illustrates the interface between the ATM Layer and the Physical Layer. At the top is a rectangular box labeled "ATM Layer". At the bottom is a rectangular box labeled "Physical Layer". A vertical line connects the two boxes. In the middle of this line is an oval shape, and to the right of the oval is the text "PHY-SAP", indicating the Physical Service Access Point. + +Diagram showing the SAP between Physical Layer and ATM Layer. The ATM Layer is at the top, connected to the Physical Layer at the bottom via a PHY-SAP (represented by an oval). + +**Figure 1: SAP between Physical Layer and ATM Layer** + +According to ITU-T Rec. I.361 [11], subclause 3.2, the following primitives are provided over PHY-SAP: + +- PHY-DATA request (PHY-SDU); +- PHY-DATA indication (PHY-SDU). + +The parameter PHY-SDU contains one ATM cell as defined in ITU-T I.361 [11] received or to be transferred over the physical medium. + +## 4.5 Interface to Management Plane + +The description of the interface towards Management Plane is out of scope of this document, anyhow at least the following O&M functions should be foreseen: + +- Performance Monitoring Functions; + +- Alarm Status Reporting Functions; +- Synchronisation Source Management. + +# 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-110684 | 0019 | | Correction of references | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-03 | SA#95-e | | | | | Promotion to Release 17 without technical change | 17.0.0 | +| 2024-03 | SA#103- | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/25_series/25419/raw.md b/marked/Rel-18/25_series/25419/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5c744c20bcb74151f612baabbe1525eef58499fd --- /dev/null +++ b/marked/Rel-18/25_series/25419/raw.md @@ -0,0 +1,3339 @@ + + +# 3GPP TS 25.419 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu-BC Interface: Service Area Broadcast Protocol (SABP) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|---------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 General..... | 8 | +| 4.1 Procedure Specification Principles..... | 8 | +| 4.2 Forwards and Backwards Compatibility..... | 9 | +| 4.3 Specification Notations ..... | 9 | +| 5 Services provided by SABP..... | 9 | +| 6 Services expected from the Transport layer..... | 9 | +| 7 Functions of SABP..... | 10 | +| 8 SABP Procedures..... | 10 | +| 8.1 Elementary Procedures..... | 10 | +| 8.2 Write-Replace..... | 10 | +| 8.2.1 General ..... | 10 | +| 8.2.2 Successful Operation..... | 11 | +| 8.2.3 Unsuccessful Operation..... | 12 | +| 8.2.4 Abnormal Conditions ..... | 13 | +| 8.3 Kill..... | 13 | +| 8.3.1 General ..... | 13 | +| 8.3.2 Successful Operation..... | 13 | +| 8.3.3 Unsuccessful Operation..... | 14 | +| 8.3.4 Abnormal Conditions ..... | 14 | +| 8.4 Load Status Enquiry ..... | 14 | +| 8.4.1 General ..... | 14 | +| 8.4.2 Successful Operation..... | 14 | +| 8.4.3 Unsuccessful Operation..... | 15 | +| 8.4.4 Abnormal Conditions ..... | 15 | +| 8.5 Message Status Query ..... | 15 | +| 8.5.1 General ..... | 15 | +| 8.5.2 Successful Operation..... | 16 | +| 8.5.3 Unsuccessful Operation..... | 16 | +| 8.5.4 Abnormal Conditions ..... | 17 | +| 8.6 Reset..... | 17 | +| 8.6.1 General ..... | 17 | +| 8.6.2 Successful Operation..... | 17 | +| 8.6.3 Unsuccessful Operation..... | 17 | +| 8.6.4 Abnormal Conditions ..... | 18 | +| 8.7 Restart Indication ..... | 18 | +| 8.7.1 General ..... | 18 | +| 8.7.2 Successful Operation..... | 18 | +| 8.7.3 Abnormal Conditions ..... | 18 | +| 8.8 Failure Indication ..... | 18 | +| 8.8.1 General ..... | 18 | +| 8.8.2 Successful Operation..... | 19 | +| 8.8.3 Abnormal Conditions ..... | 19 | +| 8.9 Error Indication ..... | 19 | +| 8.9.1 General ..... | 19 | +| 8.9.2 Successful Operation..... | 19 | +| 8.9.3 Abnormal Conditions ..... | 20 | + +| | | | +|---------|--------------------------------------------------------------------|----| +| 9 | Elements for SABP Communication ..... | 20 | +| 9.1 | Message Functional Definiton and Content..... | 20 | +| 9.1.1 | General ..... | 20 | +| 9.1.2 | Message Contents..... | 20 | +| 9.1.2.1 | Presence ..... | 20 | +| 9.1.2.2 | Criticality ..... | 20 | +| 9.1.2.3 | Range ..... | 20 | +| 9.1.2.4 | Assigned Criticality ..... | 21 | +| 9.1.3 | WRITE-REPLACE ..... | 21 | +| 9.1.4 | WRITE-REPLACE COMPLETE ..... | 21 | +| 9.1.5 | WRITE-REPLACE FAILURE ..... | 21 | +| 9.1.6 | KILL ..... | 22 | +| 9.1.7 | KILL COMPLETE ..... | 22 | +| 9.1.8 | KILL FAILURE ..... | 22 | +| 9.1.9 | LOAD QUERY ..... | 22 | +| 9.1.10 | LOAD QUERY COMPLETE ..... | 23 | +| 9.1.11 | LOAD QUERY FAILURE ..... | 23 | +| 9.1.12 | MESSAGE STATUS QUERY..... | 23 | +| 9.1.13 | MESSAGE STATUS QUERY COMPLETE ..... | 23 | +| 9.1.14 | MESSAGE STATUS QUERY FAILURE..... | 24 | +| 9.1.15 | RESET ..... | 24 | +| 9.1.16 | RESET COMPLETE..... | 24 | +| 9.1.17 | RESET FAILURE ..... | 24 | +| 9.1.18 | RESTART ..... | 25 | +| 9.1.19 | FAILURE ..... | 25 | +| 9.1.20 | ERROR INDICATION ..... | 25 | +| 9.2 | Information Element Definitions ..... | 25 | +| 9.2.0 | General ..... | 25 | +| 9.2.1 | MessageType..... | 26 | +| 9.2.2 | Broadcast Message Content ..... | 26 | +| 9.2.3 | Serial Number..... | 26 | +| 9.2.4 | Old Serial Number..... | 26 | +| 9.2.5 | New Serial Number ..... | 27 | +| 9.2.6 | Service Areas List..... | 27 | +| 9.2.7 | Category ..... | 27 | +| 9.2.8 | Repetition Period..... | 27 | +| 9.2.9 | Number of Broadcasts Requested ..... | 27 | +| 9.2.10 | Number of Broadcasts Completed List ..... | 28 | +| 9.2.11 | Service Area Identifier..... | 29 | +| 9.2.12 | Failure List..... | 29 | +| 9.2.13 | Radio Resource Loading List ..... | 29 | +| 9.2.14 | Cause ..... | 30 | +| 9.2.15 | Data Coding Scheme ..... | 32 | +| 9.2.16 | Recovery Indication..... | 32 | +| 9.2.17 | Criticality Diagnostics ..... | 32 | +| 9.2.18 | Available Bandwidth..... | 34 | +| 9.2.19 | Message Identifier ..... | 34 | +| 9.2.20 | Message Structure ..... | 34 | +| 9.2.21 | Paging ETWS Indicator..... | 35 | +| 9.2.22 | Warning Type..... | 35 | +| 9.2.23 | Warning Security Information..... | 36 | +| 9.2.24 | Broadcast Message Content Validity Indicator ..... | 36 | +| 9.3 | Message and Information Element Abstract Syntax (with ASN.1) ..... | 36 | +| 9.3.0 | General ..... | 36 | +| 9.3.1 | Usage of protocol extension mechanism for non-standard use ..... | 36 | +| 9.3.2 | Elementary Procedure Definitions..... | 38 | +| 9.3.3 | PDU Definitions ..... | 41 | +| 9.3.4 | Information Element Definitions ..... | 51 | +| 9.3.5 | Common Definitions ..... | 56 | +| 9.3.6 | Constant Definitions ..... | 57 | +| 9.3.7 | Container Definitions ..... | 58 | +| 9.4 | Message Transfer Syntax ..... | 61 | + +| | | | +|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------| +| 10 | Handling of Unknown, Unforeseen or Erroneous Protocol Data ..... | 61 | +| 10.1 | General ..... | 61 | +| 10.2 | Transfer Syntax Error ..... | 61 | +| 10.3 | Abstract Syntax Error ..... | 61 | +| 10.3.1 | General ..... | 61 | +| 10.3.2 | Criticality Information ..... | 62 | +| 10.3.3 | Presence Information ..... | 62 | +| 10.3.4 | Not comprehended IE/IE group ..... | 63 | +| 10.3.4.1 | Procedure Code ..... | 63 | +| 10.3.4.1A | Type of Message ..... | 63 | +| 10.3.4.2 | IEs other than the Procedure Code and Type of Message ..... | 63 | +| 10.3.5 | Missing IE or IE group ..... | 64 | +| 10.3.6 | IEs or IE groups received in wrong order or with too many occurrences or erroneously present ..... | 65 | +| 10.4 | Logical Error ..... | 66 | +| 10.5 | Exceptions ..... | 66 | +| Annex A (informative): Guidelines for Usage of the Criticality Diagnostics IE ..... | | 67 | +| A.1 | EXAMPLE MESSAGE Layout ..... | 67 | +| A.2 | Example on a Received EXAMPLE MESSAGE ..... | 68 | +| A.3 | Content of Criticality Diagnostics ..... | 69 | +| A.3.1 | Example 1 ..... | 69 | +| A.3.2 | Example 2 ..... | 70 | +| A.3.3 | Example 3 ..... | 71 | +| A.3.4 | Example 4 ..... | 72 | +| A.3.5 | Example 5 ..... | 73 | +| A.4 | ASN.1 of EXAMPLE MESSAGE ..... | 74 | +| Annex B (informative): Change history ..... | | 77 | + +# --- 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 *Service Area Broadcast Protocol (SABP)* between the Cell Broadcast Centre (CBC) and the Radio Network Controller (RNC). It fulfils the CBC - RNC communication requirements specified in TS 23.041 [5] and is defined over the Iu-BC – reference point. + +# --- 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] Void +- [3] Void +- [4] 3GPP TR 25.931: "UTRAN Functions: Examples on Signalling Procedures". +- [5] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [6] 3GPP TS 25.414: "UTRAN Iu Interface Data Transport and Transport Signalling". +- [7] ITU-T Recommendation X.680 (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [8] ITU-T Recommendation X.681 (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification". +- [9] ITU-T Recommendation X.691 (2002-07): "Information Technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)". +- [10] 3GPP TR 25.921 (Version 7.0.0): "Guidelines and Principles for Protocol Description and Error Handling". +- [11] 3GPP TS 25.324: "Broadcast/Multicast Control BMC". +- [12] 3GPP TS 23.003: "Numbering, addressing and identification". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Elementary Procedure:** SABP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the CN (CBC) and the RNC. These EPs 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 SABP 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. 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 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). + +Class 2 EPs are considered always successful. + +**Message Reference:** This is defined as consisting of the following parameters: Message Identifier, Serial Number, and SAI (Service Area Identifier). + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|---------------------------------| +| CBC | Cell Broadcast Centre | +| CBS | Cell Broadcast Service | +| CN | Core Network | +| EP | Elementary Procedure | +| FP | Frame Protocol | +| PDU | Protocol Data Unit | +| RNC | Radio Network Controller | +| SA | Service Area | +| SABP | Service Area Broadcast Protocol | + +# --- 4 General + +The protocol described in the present document is the protocol between CN (CBC) and RNC needed for the CBC Application. The CBC Application is described in TS 23.041 [5]. + +## 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 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 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. + +## 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. Write-Replace 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. WRITE-REPLACE 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. Old Serial 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 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Background ". | + +# --- 5 Services provided by SABP + +- During normal operation the CN (CBC) initiates all message transfer and query operations. The RNC responds to the message transfer and query operations initiated by the CBC. +- The RNC will open the connection only in case an error (Failure Indication Procedure) or recovery (Restart Indication Procedure) is to be reported. +- The initiator of a connection is responsible for the termination of the connection. + +# --- 6 Services expected from the Transport layer + +Following service is expected from the transport layer: + +- in sequence delivery of Signalling data TS 25.414 [6]. + +# 7 Functions of SABP + +The SABP has the following functions: + +- Message Handling. This function is responsible for the broadcast of new messages, amend existing broadcasted messages and to stop the broadcasting of specific messages. +- Load Handling. This function is responsible for determining the loading of the broadcast channels at any particular point in time. +- Reset. This function permits the CBC to end broadcasting in one or more Service Areas. +- Error Handling. This function allows the reporting of general error situations, for which function specific error messages have not been defined. + +These functions are implemented by one or several SABP elementary procedures described in the following clauses. + +# 8 SABP Procedures + +## 8.1 Elementary Procedures + +In the following tables, all EPs are divided into Class 1 and Class 2 Procedures. + +**Table 1: Class 1** + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|----------------------|--------------------|------------------------|-----------------------| +| | | Response message | Response message | +| Write-Replace | WRITE-REPLACE | WRITE-REPLACE COMPLETE | WRITE-REPLACE FAILURE | +| Kill | KILL | KILL COMPLETE | KILL FAILURE | +| Load Status Enquiry | LOAD QUERY | LOAD QUERY COMPLETE | LOAD QUERY FAILURE | +| Message Status Query | MESSAGE QUERY | MESSAGE QUERY COMPLETE | MESSAGE QUERY FAILURE | +| Reset | RESET | RESET COMPLETE | RESET FAILURE | + +**Table 2: Class 2** + +| Elementary Procedure | Message | +|----------------------|------------------| +| Restart Indication | RESTART | +| Failure Indication | FAILURE | +| Error Indication | ERROR INDICATION | + +## 8.2 Write-Replace + +### 8.2.1 General + +The purpose of this Write-Replace procedure is to broadcast new information or replace a message already broadcast to a chosen Service Area(s). + +### 8.2.2 Successful Operation + +![Sequence diagram showing the Write-Replace Procedure: Successful Operation between an RNC and a CN. The CN sends a WRITE-REPLACE message to the RNC, and the RNC responds with a WRITE-REPLACE COMPLETE message.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` + +sequenceDiagram + participant CN + participant RNC + Note left of CN: CN initiates procedure + CN->>RNC: WRITE-REPLACE + Note right of RNC: RNC broadcasts message + RNC->>CN: WRITE-REPLACE COMPLETE + +``` + +Sequence diagram showing the Write-Replace Procedure: Successful Operation between an RNC and a CN. The CN sends a WRITE-REPLACE message to the RNC, and the RNC responds with a WRITE-REPLACE COMPLETE message. + +**Figure 1: Write-Replace Procedure: Successful Operation** + +The CN shall initiate the procedure by sending a WRITE-REPLACE message to the RNC. + +The presence of a *New Serial Number* IE will indicate that this is a new broadcast. The presence of both the *Old Serial Number* IE and a *New Serial Number* IE will indicate that this message is a replacement of an existing broadcast. + +The RNC will initiate broadcasting of a new message or replace a message already broadcast as requested to the service areas as indicated in the *Service Areas List* IE. + +The RNC shall uniquely identify the CBS message by the *Message Identifier* IE together with the twelve leftmost bits of the serial number in the *New Serial Number* IE and the *Service Area Identifier* IE. + +The RNC shall perform the broadcast according to the value of the *Category* IE as follows: + +- The *Category* IE, if given in the WRITE-REPLACE message, shall be treated as follows: + 1. If the value of *Category* IE is indicated as "High Priority", the RNC shall perform the broadcast immediately; + 2. If the value of *Category* IE is indicated as "Background", the RNC shall perform the broadcast when no other broadcast message indicated as "High Priority" or "Normal"; + 3. If the value of *Category* IE is indicated as "Normal", the RNC shall perform the broadcast according to the *Repetition Period* IE. +- If the *Category* IE is not given in the WRITE-REPLACE message, the RNC shall perform the broadcast as the same category indicated as "Normal". + +The RNC shall pass the *Data Coding Scheme* IE transparently to the radio interface protocol. + +The RNC shall pass the *Broadcast Message Content* IE Transparently to the radio interface protocol. + +The RNC shall broadcast the message frequently according to the value of the *Number of Broadcasts Requested* IE. If the value is set to "0", the RNC shall broadcast the message until the CN requests otherwise. If the value is different than "0", the RNC shall broadcast the message as many times as indicated in the *Number of Broadcasts Requested* IE, and after the completion of the broadcast, the RNC shall release the involved messages and their status stored for each service area. + +Upon receipt of the WRITE-REPLACE message the RNC shall respond using the WRITE-REPLACE COMPLETE message containing a *New Serial Number* IE indicating that resources are available as requested for the Service Area(s) specified and a *Number of Broadcasts Completed List* IE to indicate the number of times the version of the old CBS message identified by the *Message Identifier* IE and the *Old Serial Number* IE, has been successfully broadcast to the particular Service Area(s). If the version corresponding to the *Old Serial Number* IE value is not recognized for a particular service area, the number of broadcast completed shall be reported as '0' and the *Number of Broadcasts Compl Info* IE set to 'unknown'. + +If the WRITE-REPLACE message sent from the CN: + +- contained a *New Serial Number* IE but not an *Old Serial Number* IE, the *Number of Broadcasts* IE within the *Number of Broadcasts Completed List* IE is set to "0" for each included Service Area in the corresponding WRITE-REPLACE COMPLETE message. +- contained both the *New Serial Number* IE and the *Old Serial Number* IE, an entry is made in the *Number of Broadcasts* IE in the *Number of Broadcasts Completed List* IE for each included Service Area in the corresponding WRITE-REPLACE COMPLETE message. The RNC shall also release the involved old messages and their status stored for each service area. + +If *Paging ETWS Indicator* IE is included in the WRITE-REPLACE message, the RNC shall construct and send paging message towards the UE. The paging message contains warning information based on *Warning Type* IE. If the *Broadcast Message Content Validity Indicator* IE is included in the WRITE-REPLACE message then the RNC shall ignore the contents of the *Broadcast Message Content* IE, *Repetition Period* IE and *Number of Broadcasts Requested* IE. + +If the *Warning Security Information* IE is included in the WRITE-REPLACE message sent from the CN, the RNC shall send the *Warning Security Information* IE together with the paging message. + +### 8.2.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Write-Replace procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow labeled 'WRITE-REPLACE' points from the CN to the RNC. A horizontal arrow labeled 'WRITE-REPLACE FAILURE' points from the RNC to the CN. Both lifelines end with a thick horizontal bar at the bottom.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of RNC: + CN->>RNC: WRITE-REPLACE + Note right of RNC: + RNC->>CN: WRITE-REPLACE FAILURE + Note left of RNC: + Note right of CN: +``` + +Sequence diagram showing the Unsuccessful Operation of the Write-Replace procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow labeled 'WRITE-REPLACE' points from the CN to the RNC. A horizontal arrow labeled 'WRITE-REPLACE FAILURE' points from the RNC to the CN. Both lifelines end with a thick horizontal bar at the bottom. + +Figure 2: Write-Replace Procedure: Un-Successful Operation + +If there is at least one Service Area specified in the WRITE-REPLACE message for which the RNC cannot allocate all the resources requested or for which the RNC cannot complete as requested, then the RNC shall return a WRITE-REPLACE FAILURE message to the CN as an outcome of the procedure. A list of Service Area(s) where the requested resources are unavailable or for which the RNC cannot complete as requested and appropriate cause value shall be provided in this WRITE-REPLACE FAILURE message in the *Failure List* IE. + +This WRITE-REPLACE FAILURE message may also include those Service Area(s) where the requested resources were available and shall indicate in the *Number of Broadcasts Completed List* IE those Service Area(s) which completed the request successfully. + +If the WRITE-REPLACE message sent from the CN: + +- contained a *New Serial Number* IE but not an *Old Serial Number* IE, the *Number of Broadcasts* IE within the *Number of Broadcasts Completed List* IE is set to '0' for each included Service Area in the corresponding WRITE-REPLACE FAILURE message. +- contained a *New Serial Number* IE but not an *Old Serial Number* IE, and the CBS message is already used by the RNC, it shall consider the Write Replace procedure as failed for this Service Area and return a WRITE-REPLACE FAILURE message with the Service Area Identifier of this particular Service Area included in the *Failure List* IE together with the cause value "Message-reference already-used". + +- contained both the *New Serial Number* IE and the *Old Serial Number* IE, an entry is made in *Number of Broadcasts* IE in the *Number of Broadcasts Completed List* IE for each included Service Area in the corresponding WRITE-REPLACE FAILURE message. +- contained both the *New Serial Number* IE and the *Old Serial Number* IE, but if the old CBS message is unknown to the RNC (i.e. it can not execute the kill request) for a particular Service Area, it shall consider the Write Replace procedure as failed for this Service Area. When the procedure is completed, the RNC shall return a WRITE-REPLACE-FAILURE message which includes the Service Area Identifier of this particular Service Area in the *Failure List* IE together with the cause value "Valid-CN-message-not-identified". + +### 8.2.4 Abnormal Conditions + +## 8.3 Kill + +### 8.3.1 General + +The purpose of the Kill procedure is to stop the broadcast of the indicated message. + +### 8.3.2 Successful Operation + +![Sequence diagram illustrating the Kill Procedure: Successful Operation. The diagram shows two vertical lifelines: RNC (left) and CN (right). The CN sends a 'KILL' message to the RNC. The RNC then sends a 'KILL COMPLETE' message back to the CN. Both lifelines end with a thick horizontal bar at the bottom.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) + +``` + +sequenceDiagram + participant CN + participant RNC + Note left of RNC: + CN->>RNC: KILL + Note right of RNC: + RNC->>CN: KILL COMPLETE + Note right of CN: + +``` + +Sequence diagram illustrating the Kill Procedure: Successful Operation. The diagram shows two vertical lifelines: RNC (left) and CN (right). The CN sends a 'KILL' message to the RNC. The RNC then sends a 'KILL COMPLETE' message back to the CN. Both lifelines end with a thick horizontal bar at the bottom. + +Figure 3: Kill Procedure: Successful Operation + +The CN shall initiate the procedure by sending a KILL message to the RNC. + +Upon receipt of the KILL message the RNC shall stop broadcasting the CBS message, which is indicated in the *Message Identifier* IE and the twelve leftmost bits of the *Old Serial Number* IE, in the indicated Service Area(s) as indicated in the *Service Areas List* IE. + +The RNC shall respond using the KILL COMPLETE message, containing the *Old Serial Number* IE copied from the request and the *Number of Broadcast Completed List* IE when all Service Areas successfully stopped the broadcast. It shall indicate in the *Number of Broadcast Completed List* IE for each of these Service Area(s), the number of times the version of the CBS message identified by the *Message Identifier* IE and the *Old Serial Number* IE received has been sent to this particular Service Area(s) for broadcast. The RNC shall also release the involved messages and their status stored for each service area. If the version corresponding to the *Old Serial Number* IE value is not recognized for a particular service area, the number of broadcast completed shall be reported as '0' and the *Number of Broadcasts Compl Info* IE set to 'unknown'. + +### 8.3.3 Unsuccessful Operation + +![Sequence diagram for Kill Procedure: Un-Successful Operation](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of RNC: + CN->>RNC: KILL + Note right of CN: + RNC-->>CN: KILL FAILURE + Note right of RNC: +``` + +The diagram shows a sequence of messages between a CN (Core Network) and an RNC (Radio Network Controller). The CN sends a 'KILL' message to the RNC. The RNC responds with a 'KILL FAILURE' message. Both entities are represented by vertical lifelines with a horizontal bar at the bottom. + +Sequence diagram for Kill Procedure: Un-Successful Operation + +Figure 4: Kill Procedure: Un-Successful Operation + +If the RNC fails to stop broadcasting the CBS message as indicated in the KILL message in at least one service area, the RNC shall return the KILL FAILURE message to the CN. A *Failure List* IE indicating the list of Service Area(s) where the CBS message was not recognized or the broadcast could not be stopped together with the appropriate cause value shall be provided in the KILL FAILURE message. This response message may also – if applicable - indicate in the *Number of Broadcasts Completed List* IE those Service Area(s) where the KILL message successfully stopped the broadcast. + +### 8.3.4 Abnormal Conditions + +## 8.4 Load Status Enquiry + +### 8.4.1 General + +The purpose of this Load Status Enquiry procedure is to obtain the current permissible bandwidth available for broadcast within particular Service Area(s). + +### 8.4.2 Successful Operation + +![Sequence diagram for Load Status Enquiry Procedure: Successful Operation](66c2bf11a8f117cddf67eff92d4c736c_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of RNC: + CN->>RNC: LOAD QUERY + Note right of CN: + RNC-->>CN: LOAD QUERY COMPLETE + Note right of RNC: +``` + +The diagram shows a sequence of messages between a CN (Core Network) and an RNC (Radio Network Controller). The CN sends a 'LOAD QUERY' message to the RNC. The RNC responds with a 'LOAD QUERY COMPLETE' message. Both entities are represented by vertical lifelines with a horizontal bar at the bottom. + +Sequence diagram for Load Status Enquiry Procedure: Successful Operation + +Figure 5: Load Status Enquiry Procedure: Successful Operation + +The CN shall initiate the procedure by sending a LOAD QUERY message to the RNC. The message shall include a *Service Areas List* IE. Upon reception of the LOAD QUERY message the RNC shall respond with a LOAD QUERY COMPLETE message containing the *Radio Resource Loading List* IE indicating the available bandwidth of the Service Area(s). + +### 8.4.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful Load Status Enquiry procedure. The CN sends a LOAD QUERY message to the RNC, and the RNC responds with a LOAD QUERY FAILURE message.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of CN: CN initiates procedure + CN->>RNC: LOAD QUERY + Note right of RNC: RNC cannot respond + RNC->>CN: LOAD QUERY FAILURE +``` + +Sequence diagram showing an unsuccessful Load Status Enquiry procedure. The CN sends a LOAD QUERY message to the RNC, and the RNC responds with a LOAD QUERY FAILURE message. + +**Figure 6: Load Status Enquiry Procedure: Un-Successful Operation** + +If the RNC contains Service Area(s) for which the RNC was not able to respond to, it shall respond with a LOAD QUERY FAILURE message which includes the *Failure List* IE. + +The LOAD QUERY FAILURE response message may – if applicable - also contain a *Radio Resource Loading List* IE for which the LOAD STATUS QUERY reporting was successful. + +### 8.4.4 Abnormal Conditions + +## 8.5 Message Status Query + +### 8.5.1 General + +The Message Status Query procedure is used by the CN to obtain the message status of a broadcast message. + +### 8.5.2 Successful Operation + +![Sequence diagram for Figure 7: Message Status Query Procedure: Successful Operation. The diagram shows two lifelines, RNC and CN. The CN sends a MESSAGE STATUS QUERY message to the RNC. The RNC responds with a MESSAGE STATUS QUERY COMPLETE message to the CN.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of CN: + CN->>RNC: MESSAGE STATUS QUERY + Note right of RNC: + RNC->>CN: MESSAGE STATUS QUERY COMPLETE + Note right of CN: +``` + +Sequence diagram for Figure 7: Message Status Query Procedure: Successful Operation. The diagram shows two lifelines, RNC and CN. The CN sends a MESSAGE STATUS QUERY message to the RNC. The RNC responds with a MESSAGE STATUS QUERY COMPLETE message to the CN. + +**Figure 7: Message Status Query Procedure: Successful Operation** + +The CN shall initiate the procedure by sending a MESSAGE STATUS QUERY message to the RNC. The message shall contain the *Old Serial Number* IE along with the *Service Areas List* IE containing the Service Area Identifiers the status query is intended for. The status is requested for the version of the CBS message identified by the *Message Identifier* IE and the full value of the *Old Version Number* IE. + +Upon receipt of the MESSAGE STATUS QUERY message the RNC shall respond using the MESSAGE STATUS QUERY COMPLETE message. + +Within this message the *Number of Broadcasts Completed List* IE contains each Service Area which successfully performed the requested operation and for each of these Service Area(s), the number of times the version of this CBS message has been sent to this particular Service Area(s) for broadcast. If the version corresponding to the *Old Serial Number* IE value is not recognized for a particular service area, the number of broadcast completed shall be reported as '0' and the *Number of Broadcasts Compl Info* IE set to 'unknown'. + +### 8.5.3 Unsuccessful Operation + +![Sequence diagram for Figure 8: Message Status Query Procedure: Unsuccessful Operation. The diagram shows two lifelines, RNC and CN. The CN sends a MESSAGE STATUS QUERY message to the RNC. The RNC responds with a MESSAGE STATUS QUERY FAILURE message to the CN.](f57a881fcbcaf494a7dedc4f61224991_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of CN: + CN->>RNC: MESSAGE STATUS QUERY + Note right of RNC: + RNC->>CN: MESSAGE STATUS QUERY FAILURE + Note right of CN: +``` + +Sequence diagram for Figure 8: Message Status Query Procedure: Unsuccessful Operation. The diagram shows two lifelines, RNC and CN. The CN sends a MESSAGE STATUS QUERY message to the RNC. The RNC responds with a MESSAGE STATUS QUERY FAILURE message to the CN. + +**Figure 8: Message Status Query Procedure: Unsuccessful Operation** + +If the requested operation fails (e.g. because the CBS message is unknown, or when the RNC cannot send the status for a known CBS message) the RNC shall send a MESSAGE STATUS QUERY FAILURE message to the CN containing a *Failure List* IE for Service Area(s) for which the requested operation failed. + +The MESSAGE STATUS QUERY FAILURE message may – if applicable - also include the *Number of Broadcasts Completed List* IE indicating those Service Area(s) for which the MESSAGE STATUS QUERY message was successful. + +### 8.5.4 Abnormal Conditions + +## 8.6 Reset + +### 8.6.1 General + +The purpose of the Reset procedure is to end broadcasting in one or more Service Areas in the RNC. + +### 8.6.2 Successful Operation + +![Sequence diagram for Figure 9: Reset Procedure: Successful Operation. It shows two vertical lifelines labeled RNC and CN. A horizontal arrow labeled 'RESET' points from the CN lifeline to the RNC lifeline. A horizontal arrow labeled 'RESET COMPLETE' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom.](29f586959675cafdf81cf934954908eb_img.jpg) + +Sequence diagram for Figure 9: Reset Procedure: Successful Operation. It shows two vertical lifelines labeled RNC and CN. A horizontal arrow labeled 'RESET' points from the CN lifeline to the RNC lifeline. A horizontal arrow labeled 'RESET COMPLETE' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom. + +Figure 9: Reset Procedure: Successful Operation + +The CN shall initiate the procedure by sending a RESET message to the RNC, in order to end broadcasting in one or more Service Areas of the RNC. + +Upon receipt of this message the RNC shall end broadcasting in the indicated Service Area(s) and shall respond using a RESET COMPLETE message. + +### 8.6.3 Unsuccessful Operation + +![Sequence diagram for Figure 10: Reset Procedure: Un-Successful Operation. It shows two vertical lifelines labeled RNC and CN. A horizontal arrow labeled 'RESET' points from the CN lifeline to the RNC lifeline. A horizontal arrow labeled 'RESET FAILURE' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom.](4aa740e8119817a3f9b9f72d06eaa53d_img.jpg) + +Sequence diagram for Figure 10: Reset Procedure: Un-Successful Operation. It shows two vertical lifelines labeled RNC and CN. A horizontal arrow labeled 'RESET' points from the CN lifeline to the RNC lifeline. A horizontal arrow labeled 'RESET FAILURE' points from the RNC lifeline to the CN lifeline. Both lifelines end with a thick horizontal bar at the bottom. + +Figure 10: Reset Procedure: Un-Successful Operation + +If upon receipt of this message the RNC can not end broadcasting in the indicated Service Area(s), it shall respond using a RESET FAILURE message. The RESET FAILURE message may contain the *Service Areas List* IE and shall contain the *Failure List* IE indicating the relevant Service Area(s) in which the RESET message was successful and unsuccessful respectively, along with the appropriate cause value. + +The sum of the Service Area(s) included in the *Service Areas List* and *Failure List* IEs shall be the same as indicated in the *Service Areas List* IE of the initiating RESET message. + +### 8.6.4 Abnormal Conditions + +## 8.7 Restart Indication + +### 8.7.1 General + +The purpose of the Restart Indication procedure is for the RNC to indicate to the CN that a Service Area broadcasting related restart situation has occurred in one or more of its Service Areas e.g. when a Service Area becomes operational or when the RNC is initialised. + +### 8.7.2 Successful Operation + +![Sequence diagram showing the Restart Indication Procedure: Successful Operation. The RNC sends a RESTART message to the CN.](124c6108c63173818afb8ed49521e22d_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + RNC->>CN: RESTART + +``` + +The diagram illustrates a sequence of two vertical lifelines. The left lifeline is labeled 'RNC' and the right is labeled 'CN'. A horizontal arrow points from the RNC lifeline to the CN lifeline, with the word 'RESTART' centered above it. Both lifelines end in a thick horizontal bar at the bottom. + +Sequence diagram showing the Restart Indication Procedure: Successful Operation. The RNC sends a RESTART message to the CN. + +**Figure 11: Restart Indication Procedure: Successful Operation** + +The RNC shall initiate the procedure by sending a RESTART message to the CN. This message shall contain a *Service Areas List* IE for reference and may also include the *Recovery Indication* IE to indicate whether the previous broadcast information needs to be loaded. In the absence of the *Recovery Indication* IE, the CN shall interpret it as "lost". + +### 8.7.3 Abnormal Conditions + +## 8.8 Failure Indication + +### 8.8.1 General + +The purpose of the Failure Indication procedure is to indicate to the CN from the RNC that a Service Area broadcasting related problem is occurring in one or more of its Service Areas. + +### 8.8.2 Successful Operation + +![Sequence diagram for Figure 12: Failure Indication Procedure: Successful Operation. It shows a horizontal arrow labeled 'FAILURE' pointing from the RNC to the CN. Both RNC and CN are represented by boxes with vertical lifelines extending downwards to a horizontal bar.](10781f43062bf3e9601a1e086710556c_img.jpg) + +``` +sequenceDiagram + participant RNC + participant CN + Note right of RNC: FAILURE + RNC->>CN: FAILURE + Note left of CN: +``` + +Sequence diagram for Figure 12: Failure Indication Procedure: Successful Operation. It shows a horizontal arrow labeled 'FAILURE' pointing from the RNC to the CN. Both RNC and CN are represented by boxes with vertical lifelines extending downwards to a horizontal bar. + +**Figure 12: Failure Indication Procedure: Successful Operation** + +The RNC shall initiate the procedure by sending a FAILURE message to the CN. The FAILURE message shall contain the *Service Areas List* IE to indicate which Service Area(s) has a Service Area broadcasting related problem. + +Upon receipt of this FAILURE message, the CN will not generate further WRITE or REPLACE messages for these Service Area(s) until the CN is informed by a RESTART message that the Service Area can resume normal Service Area broadcasting operation. + +### 8.8.3 Abnormal Conditions + +## 8.9 Error Indication + +### 8.9.1 General + +The Error Indication procedure is initiated by the RNC to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. + +### 8.9.2 Successful Operation + +![Sequence diagram for Figure 13: Error Indication Procedure: Successful Operation. It shows a horizontal arrow labeled 'ERROR INDICATION' pointing from the RNC to the CN. Both RNC and CN are represented by boxes with vertical lifelines extending downwards to a horizontal bar.](cf4ac1058c52bc3ca37737740afb7f2c_img.jpg) + +``` +sequenceDiagram + participant RNC + participant CN + Note right of RNC: ERROR INDICATION + RNC->>CN: ERROR INDICATION + Note left of CN: +``` + +Sequence diagram for Figure 13: Error Indication Procedure: Successful Operation. It shows a horizontal arrow labeled 'ERROR INDICATION' pointing from the RNC to the CN. Both RNC and CN are represented by boxes with vertical lifelines extending downwards to a horizontal bar. + +**Figure 13: Error Indication Procedure: Successful Operation** + +When the conditions defined in chapter 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". +- "Abstract Syntax Error (reject)". + +### 8.9.3 Abnormal Conditions + +# 9 Elements for SABP Communication + +## 9.1 Message Functional Definition and Content + +### 9.1.1 General + +Section 9.1 presents the contents of SABP messages in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 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 [10]. + +For each message there is, a table listing the signalling elements in their order of appearance in the transmitted message. + +### 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 3 + +**Table 3: Meaning of abbreviations used in SABP messages** + +| Abbreviation | Meaning | +|--------------|------------------------------------------------------------------------------------------------------------------------------------| +| M | IE's marked as Mandatory (M) will always be included in the message. | +| O | IE's marked as Optional (O) may or may not be included in the message. | +| C | IE's marked as Conditional (C) will be included in a message only if the condition is satisfied. Otherwise the IE is not included. | + +#### 9.1.2.2 Criticality + +Each Information Element or Group of Information Elements may have a criticality information applied to it. Following cases are possible. + +**Table 4: 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 WRITE-REPLACE + +This message is sent by the CN to the RNC. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| New Serial Number | M | | 9.2.5 | | yes | reject | +| Old Serial Number | O | | 9.2.4 | | yes | ignore | +| Service Areas List | M | | 9.2.6 | | yes | reject | +| Category | O | | 9.2.7 | | yes | ignore | +| Repetition Period | M | | 9.2.8 | | yes | reject | +| Number of Broadcasts Requested | M | | 9.2.9 | | yes | reject | +| Data Coding Scheme | M | | 9.2.15 | | yes | reject | +| Broadcast Message Content | M | | 9.2.2 | | yes | reject | +| Warning Security Information | O | | 9.2.23 | See TS 23.041 [5]. | yes | ignore | +| Paging ETWS Indicator | O | | 9.2.21 | | yes | ignore | +| Warning Type | O | | 9.2.22 | | yes | ignore | +| Broadcast Message Content Validity Indicator | O | | 9.2.24 | | yes | ignore | + +### 9.1.4 WRITE-REPLACE COMPLETE + +This message will be sent by the RNC to the CN in a successful response to a WRITE-REPLACE message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| New Serial Number | M | | 9.2.5 | | yes | reject | +| Number of Broadcasts Completed List | M | | 9.2.10 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.5 WRITE-REPLACE FAILURE + +This message will be sent by the RNC to the CN as an unsuccessful response to a WRITE-REPLACE message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| New Serial Number | M | | 9.2.5 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Number of Broadcasts Completed List | O | | 9.2.10 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.6 KILL + +This message is sent by the CN to the RNC to stop broadcasting of a specific message. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | + +### 9.1.7 KILL COMPLETE + +This message is sent by the RNC to the CN as a successful response to a KILL message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Number of Broadcasts Completed List | M | | 9.2.10 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.8 KILL FAILURE + +This message is sent by the RNC to the CN as unsuccessful response to a KILL message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Number of Broadcasts Completed List | O | | 9.2.10 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.9 LOAD QUERY + +This message is sent by the CN to the RNC to gain an indication of broadcast resources available. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | + +### 9.1.10 LOAD QUERY COMPLETE + +This message will be sent by the RNC as a successful response to the LOAD QUERY message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Radio Resource Loading List | M | | 9.2.13 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.11 LOAD QUERY FAILURE + +This message is sent by the RNC to the CN as an unsuccessful response to a LOAD QUERY message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Radio Resource Loading List | O | | 9.2.13 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.12 MESSAGE STATUS QUERY + +This message is sent by the CN to the RNC to obtain the current status of a Service Area broadcasting message. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | + +### 9.1.13 MESSAGE STATUS QUERY COMPLETE + +This message is sent by the RNC to the CN as a successful response to a MESSAGE QUERY message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Number of Broadcasts Completed List | M | | 9.2.10 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.14 MESSAGE STATUS QUERY FAILURE + +This message is sent by the RNC to the CN in an unsuccessful response to a MESSAGE QUERY message. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Message Identifier | M | | 9.2.19 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Old Serial Number | M | | 9.2.4 | | yes | reject | +| Number of Broadcasts Completed List | O | | 9.2.10 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.15 RESET + +The message is sent by the CN to the RNC to request that the RNC end broadcasting in one or more Service Areas. + +Direction: CN → RNC + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | + +### 9.1.16 RESET COMPLETE + +This message is sent from the RNC to the CN as a successful response to a RESET message where indicated Service-Area(s) are now not broadcasting any messages. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Service Areas List | M | | 9.2.6 | | yes | reject | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.17 RESET FAILURE + +This message is sent from the RNC to the CN as an unsuccessful response to a RESET message to indicate that a Service Area broadcasting related problem exists in one or more of its Service Areas. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | reject | +| Failure List | M | | 9.2.12 | | yes | reject | +| Service Areas List | O | | 9.2.6 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +### 9.1.18 RESTART + +This message is sent from the RNC to the CN to indicate a Service Area broadcasting related restart situation in one or more of its Service-Areas. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | ignore | +| Service Areas List | M | | 9.2.6 | | yes | ignore | +| Recovery Indication | O | | 9.2.16 | | yes | ignore | + +### 9.1.19 FAILURE + +This message is sent from the RNC to the CN to indicate that a Service Area broadcasting related problem exists in one or more of its Service-Areas. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | ignore | +| Service Areas List | M | | 9.2.6 | | yes | ignore | + +### 9.1.20 ERROR INDICATION + +This message is sent by the RNC to CN and is used to indicate that some errors have been detected in the node. + +Direction: RNC → CN + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | yes | ignore | +| Message Identifier | O | | 9.2.19 | | yes | ignore | +| Serial Number | O | | 9.2.3 | | yes | ignore | +| Cause | O | | 9.2.14 | | yes | ignore | +| Criticality Diagnostics | O | | 9.2.17 | | yes | ignore | + +## 9.2 Information Element Definitions + +### 9.2.0 General + +Section 9.2 presents the SABP IE definitions in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 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 MessageType + +*Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Message Type | | | | | +| >Procedure Code | M | | ENUMERATED (Write-Replace, Kill, Load Status Enquiry, Message Status Query, Reset, Restart Indication, Failure Indication, Error Indication ,...) | | +| >Type of Message | M | | ENUMERATED (Initiating Message, Successful Outcome, Unsuccessful Outcome, Outcome) | | + +### 9.2.2 Broadcast Message Content + +*Broadcast Message Content* IE is sent from the CN to the RNC containing user information i.e. the message, and will be broadcast over the radio interface. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------------|----------|-------|----------------------|------------------------------------------------------------| +| Broadcast Message Content | M | | BIT STRING (1..9968) | The size of the received bitstring shall be multiple of 8. | + +### 9.2.3 Serial Number + +*Serial Number* IE is a 16-bit integer which identifies a particular message from the source and type indicated by the Message Identifier and is altered every time the message with a given Message Identifier is changed. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------|----------|-------|----------------|-----------------------| +| Serial Number | O | | BIT STRING(16) | | + +### 9.2.4 Old Serial Number + +*Old Serial Number* IE enables identification of an existing message to be identified. The format of this IE is defined in subclause 9.2.3. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|-------------------|----------|-------|-------------|-----------------------| +| Old Serial Number | M | | 9.2.3 | | + +### 9.2.5 New Serial Number + +*New Serial Number* IE enables identification of a new message for broadcast to be identified, and is altered every time the message is changed. The format of this IE is defined in subclause 9.2.3. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|-------------------|----------|-------|-------------|-----------------------| +| New Serial Number | O | | 9.2.3 | | + +### 9.2.6 Service Areas List + +The *Service Areas List* IE identifies a sequence of one or more Service Areas to which the message(s) apply. The *Service Areas List* IE must include at least one Service Area. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------------|----------|---------------------------|-------------|-----------------------| +| Service Areas List | | 1 to
of SAI> | | | +| >Service Area Identifier | M | | 9.2.11 | | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------| +| MaxnoofSAI | Maximum no. of SAI in Service Areas List. Value is 65535 | + +### 9.2.7 Category + +*Category* IE is sent from the CN to the RNC, and is used to indicate the priority of the message. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------|----------|-------|---------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| Category | O | | Enumerated (High Priority, Background, Normal, Default) | This IE contains the broadcast priority of the message. The value "Default" shall not be used | + +### 9.2.8 Repetition Period + +*Repetition Period* IE is sent from the CN to the RNC and indicates the periodicity of message broadcasts. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|-------------------|----------|-------|-------------------|---------------------------------------------------------------------------------------------------------------| +| Repetition Period | M | | INTEGER (1..4096) | Range is 1 to 4096 where each unit will represent a repetition of one second to a maximum of once per ~1 hour | + +### 9.2.9 Number of Broadcasts Requested + +*Number of Broadcasts Requested* IE is sent from the CN to the RNC and indicates the number of times a message is to be broadcast. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|--------------------------------|----------|------------|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of Broadcasts Requested | M | 0 to 65535 | INTEGER (0..65535) | This specifies the number of times the message is to be broadcast.
"0" indicates the message shall be broadcasted until CN request otherwise. | + +### 9.2.10 Number of Broadcasts Completed List + +*Number of Broadcasts Completed List* IE is sent from the RNC to the CN, and indicates the number of times that a CN message (all pages) has been sent to each Service Area specified in the *Service Areas List* IE of the request message for broadcast over the radio interface. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|--------------------------------------------|----------|-------------------|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of Broadcasts Completed List | | 1 to | | | +| >Service Area Identifier | M | | OCTET STRING (7) | | +| >Number of Broadcasts | M | | INTEGER (0.. 65535 ) | | +| >Number of Broadcasts Compl Info | O | | ENUMERATED (overflow, unknown) | Overflow indicates that the number of times that CN message sent to the radio interface has been overflow.
Unknown indicates that no information regarding the number of times that CN message sent to the radio interface. | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------| +| MaxnoofSAI | Maximum no. of SAI in Service Areas List Value is 65535 | + +### 9.2.11 Service Area Identifier + +*Service Area Identifier* IE in BC domain is used to identify an area consisting of one cell TS 23.003 [12]. Such an area is called a Service Area. For this protocol, only a Service Area that is defined to be applicable to the BC domain shall be used. + +| IE/Group Name | Presence | Range | IE type and Reference | Semantics description | +|----------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SAI | | | | | +| >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).
| +| >LAC | M | | OCTET STRING (2) | 0000 and FFFE not allowed. | +| >SAC | M | | OCTET STRING (2) | | + +### 9.2.12 Failure List + +*Failure List* IE identifies the list of Service-Area(s) for which the RNC could not complete as requested. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|--------------------------|----------|--------------------|-------------|-----------------------| +| Failure List | | 1 to | | | +| >Service Area Identifier | M | | 9.2.11 | | +| >Cause | M | | 9.2.14 | | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------| +| MaxnoofSAI | Maximum no. of SAI in Service-Area-List. Value is 65535 | + +### 9.2.13 Radio Resource Loading List + +*Radio Resource Loading List* IE presents the available bandwidth available for Broadcast purposes of a specific Service Area. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|------------------------------------|----------|--------------------|-------------|-----------------------| +| Radio Resource Loading List | | 1 to | | | +| >Service Area Identifier | M | | 9.2.11 | | +| >Available Bandwidth | M | | 9.2.18 | | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------| +| MaxnoofSAI | Maximum no. of SAI in Service Area List. Value is 65535 | + +### 9.2.14 Cause + +*Cause* IE indicates the reason for a particular error event for the SABP protocol. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|---------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >Cause | M | | INTEGER (

Parameter-not-recognised(0),







Parameter-value invalid(1),







Valid-CN-message-not-identified(2),







Service-Area-identity-not-valid(3),







Unrecognised-message(4),







Missing-mandatory-element(5),







RNC-capacity-exceeded(6), | Range is 0-255

Sent when the recipient (CN or RNC) was unable to act upon the message received due to an unrecognised parameter. A message should not be rejected only because a parameter is not recognised as this would prevent extensions to the service

Sent when a failure occurred due to the value of a parameter being invalid, e.g. out of range, or in Write-Replace, the parameter "no of pages" does not equal the number of pages received

Sent when the RNC does not recognise the CN message reference

Sent when the RNC does not recognise a Service-Area Identity

Sent when the RNC did not recognise the message at all

Sent when a mandatory element is missing from the message

Sent when a write-replace fails | + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|---------------|----------|-------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | because the RNC cannot meet the requested repetition period because of the cell loading | +| | | | RNC-memory-exceeded(7), | Sent when the RNC is unable to store a CBS message as the RNC memory has been exceeded. | +| | | | Service-Area-broadcast-not-supported(8), | Sent when the SABCH/CN related Radio Resource is not configured for a Service-Area | +| | | | Service-Area-broadcast-not-operational(9), | Sent when the SABCH/CN related radio resource is not available because of error conditions or due to maintenance activities | +| | | | Message-reference already-used(10), | Sent when the recipient was unable to act upon the Write-Replace message received due to a previous Write-Replace received with the same message reference. | +| | | | Unspecified-error(11), | Sent when none of the above cause values apply. | +| | | | (Transfer Syntax Error(12), | Sent to indicate transfer syntax error in any message | +| | | | Semantic Error (12), | Sent to indicate semantic error any message | +| | | | Message not | Sent to indicate | + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | compatible with receiver state (14),

Abstract Syntax Error (Reject) (15),

Abstract Syntax Error (Ignore and Notify) (16),

Abstract Syntax Error (Falsely Constructed Message) (17)) | that received message is not compatible with the receiver state

Sent to indicate rejection due to Abstract Syntax Error

Sent to indicate Abstract Syntax Error in some IE that has been ignored

Sent to indicate Abstract Syntax Error due to false message construction | + +### 9.2.15 Data Coding Scheme + +*Data Coding Scheme* IE is sent from the RNC to the CN and identifies the alphabet or coding employed for the message characters and message handling at the UE (it is passed transparently from the CN to the UE). + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|--------------------|----------|-------|---------------|-----------------------| +| Data Coding Scheme | M | | BIT STRING(8) | | + +### 9.2.16 Recovery Indication + +*Recovery Indication* IE is used to indicate whether the CN related data was lost or is still available. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------|----------|-------|------------------------------|-----------------------| +| Recovery Indication | O | | ENUMERATED (Lost, Available) | | + +### 9.2.17 Criticality Diagnostics + +For further details on how to use the *Criticality Diagnostics* IE, see annex A. + +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 that were not comprehended or were missing. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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 | | ENUMERATED(initiati | The Triggering | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|-----------------------|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Criticality Diagnostics | | | | | +| | | | ng message, successful outcome, unsuccessful outcome, outcome) | Message is used only if the Criticality Diagnostics is part of Error Indication procedure. | +| >Procedure Criticality | O | | ENUMERATED(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 | | ENUMERATED(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.20 |

The Message Structure IE describes 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 | | ENUMERATED(not understood, missing, ...) | | + +| 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.18 Available Bandwidth + +*Available Bandwidth* IE is used to indicate the Bandwidth available for the broadcast of messages. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------------|----------|-------|--------------------|-------------------------| +| Available Bandwidth | O | | INTEGER (0..20480) | The unit is: bit/second | + +### 9.2.19 Message Identifier + +*Message Identifier* IE is set by the CN, transfer to the UE by the RNC. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and
Reference | Semantics Description | +|--------------------|----------|-------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Identifier | M | | BIT STRING(16) | This IE is set by the CN, transfer to the UE by the RNC, the RNC needs not to understand what is the meaning of the value but shall treat it as a identifier of a message.
The Message Identifier is defined in TS 25.324 [11]. | + +### 9.2.20 Message Structure + +The *Message Structure* IE gives information for each level with assigned criticality in an 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.21 Paging ETWS Indicator + +*Paging ETWS Indicator* IE is used to indicate to the RNC that the received SABP message contains ETWS contents that need to be sent via paging message towards the UE. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|-----------------------|----------|-------|--------------------------|-----------------------| +| Paging ETWS Indicator | M | | ENUMERATED (Paging, ...) | | + +### 9.2.22 Warning Type + +Warning Type IE indicates the types of the disaster. This IE can be used by the UE to differentiate type of alert according to the type of disaster. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------|----------|-------|------------------|-----------------------| +| Warning Type | M | | OCTET STRING (2) | | + +### 9.2.23 Warning Security Information + +*Warning Security Information* IE is set by the CN, transferred to the UE by the RNC. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and
Reference | Semantics Description | +|------------------------------|----------|-------|--------------------------|-----------------------| +| Warning Security Information | M | | OCTET STRING(50) | | + +### 9.2.24 Broadcast Message Content Validity Indicator + +The *Broadcast Message Content Validity Indicator* IE indicates that the *Broadcast Message Content* IE does not contain any valid information. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and
Reference | Semantics Description | +|----------------------------------------------|----------|-------|-----------------------------------------------------|-----------------------| +| Broadcast Message Content Validity Indicator | M | | ENUMERATED
(Broadcast Message Content not valid) | | + +## 9.3 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.3.0 General + +SABP ASN.1 definition conforms with ITU-T Rec. X.680 [7] and ITU-T Rec. X.681 [8]. + +The ASN.1 definition specifies the structure and content of SABP messages. SABP 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 SABP message according to the PDU definitions module and with the following additional rules (Note that in the following 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): + +- 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. + +If a SABP 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. + +### 9.3.1 Usage of protocol extension mechanism for non-standard use + +The protocol extension 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 extension mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 9.3.2 Elementary Procedure Definitions + +``` + +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +SABP-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) sabp (3) version1 (1) sabp-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + ProcedureCode +FROM SABP-CommonDataTypes + + Error-Indication, + Failure, + Kill, + Kill-Complete, + Kill-Failure, + Load-Query, + Load-Query-Complete, + Load-Query-Failure, + Reset, + Reset-Complete, + Reset-Failure, + Restart, + Message-Status-Query, + Message-Status-Query-Complete, + Message-Status-Query-Failure, + Write-Replace, + Write-Replace-Complete, + Write-Replace-Failure +FROM SABP-PDU-Contents + + id-Error-Indication, + id-Failure-Indication, + id-Kill, + id-Reset, + id-Restart-Indication, + +``` + +``` + + id-Load-Status-Enquiry, + id-Message-Status-Query, + id-Write-Replace +FROM SABP-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +SABP-ELEMENTARY-PROCEDURE ::= CLASS { + &InitiatingMessage , + &SuccessfulOutcome OPTIONAL, + &UnsuccessfulOutcome OPTIONAL, + &procedureCode ProcedureCode UNIQUE, + &criticality Criticality DEFAULT ignore +} +WITH SYNTAX { + INITIATING MESSAGE &InitiatingMessage + [SUCCESSFUL OUTCOME + + &SuccessfulOutcome] + [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] + PROCEDURE CODE &procedureCode + [CRITICALITY &criticality] +} + +-- ***** +-- +-- Interface PDU Definition +-- +-- ***** + +SABP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode SABP-ELEMENTARY-PROCEDURE.&procedureCode ({SABP-ELEMENTARY-PROCEDURES}), + criticality SABP-ELEMENTARY-PROCEDURE.&criticality ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SABP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode SABP-ELEMENTARY-PROCEDURE.&procedureCode ({SABP-ELEMENTARY-PROCEDURES}), + criticality SABP-ELEMENTARY-PROCEDURE.&criticality ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SABP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode SABP-ELEMENTARY-PROCEDURE.&procedureCode ({SABP-ELEMENTARY-PROCEDURES}), + +``` + +``` + + criticality SABP-ELEMENTARY-PROCEDURE.&criticality ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SABP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({SABP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +SABP-ELEMENTARY-PROCEDURES SABP-ELEMENTARY-PROCEDURE ::= { + SABP-ELEMENTARY-PROCEDURES-CLASS-1 | + SABP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +SABP-ELEMENTARY-PROCEDURES-CLASS-1 SABP-ELEMENTARY-PROCEDURE ::= { + write-Replace | + kill | + load-Status-Enquiry | + message-Status-Query | + reset , + ... +} + +SABP-ELEMENTARY-PROCEDURES-CLASS-2 SABP-ELEMENTARY-PROCEDURE ::= { + restart-Indication | + failure-Indication | + error-Indication , + ... +} + +write-Replace SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Write-Replace + SUCCESSFUL OUTCOME Write-Replace-Complete + UNSUCCESSFUL OUTCOME Write-Replace-Failure + PROCEDURE CODE id-Write-Replace + CRITICALITY reject +} + +kill SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Kill + SUCCESSFUL OUTCOME Kill-Complete + UNSUCCESSFUL OUTCOME Kill-Failure + PROCEDURE CODE id-Kill + CRITICALITY reject +} + +load-Status-Enquiry SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Load-Query + SUCCESSFUL OUTCOME Load-Query-Complete + UNSUCCESSFUL OUTCOME Load-Query-Failure + PROCEDURE CODE id-Load-Status-Enquiry + CRITICALITY reject +} + +``` + +``` + +message-Status-Query SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Message-Status-Query + SUCCESSFUL OUTCOME Message-Status-Query-Complete + UNSUCCESSFUL OUTCOME Message-Status-Query-Failure + PROCEDURE CODE id-Message-Status-Query + CRITICALITY reject +} + +reset SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Reset + SUCCESSFUL OUTCOME Reset-Complete + UNSUCCESSFUL OUTCOME Reset-Failure + PROCEDURE CODE id-Reset + CRITICALITY reject +} + +restart-Indication SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Restart + PROCEDURE CODE id-Restart-Indication + CRITICALITY ignore +} + +failure-Indication SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Failure + PROCEDURE CODE id-Failure-Indication + CRITICALITY ignore +} + +error-Indication SABP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Error-Indication + PROCEDURE CODE id-Error-Indication + CRITICALITY ignore +} + +END + +``` + +### 9.3.3 PDU Definitions + +``` + +-- ***** +-- +-- PDU definitions for SABP. +-- +-- ***** + +SABP-PDU-Contents { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) sabp (3) version1 (1) sabp-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** + +``` + +``` +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Broadcast-Message-Content, + Category, + Cause, + Criticality-Diagnostics, + Data-Coding-Scheme, + Failure-List, + Message-Identifier, + New-Serial-Number, + Number-of-Broadcasts-Completed-List, + Number-of-Broadcasts-Requested, + Old-Serial-Number, + Paging-ETWS-Indicator, + Radio-Resource-Loading-List, + Recovery-Indication, + Repetition-Period, + Serial-Number, + Service-Areas-List, + WarningSecurityInfo, + Warning-Type, + Broadcast-Message-Content-Validity-Indicator +FROM SABP-IEs + + ProtocolExtensionContainer{}, + ProtocolIE-Container{}, + SABP-PROTOCOL-EXTENSION, + SABP-PROTOCOL-IEs +FROM SABP-Containers + + id-Broadcast-Message-Content, + id-Category, + id-Criticality-Diagnostics, + id-Cause, + id-Data-Coding-Scheme, + id-Failure-List, + id-Message-Identifier, + id-New-Serial-Number, + id-Number-of-Broadcasts-Completed-List, + id-Number-of-Broadcasts-Requested, + id-Old-Serial-Number, + id-Paging-ETWS-Indicator, + id-Radio-Resource-Loading-List, + id-Recovery-Indication, + id-Repetition-Period, + id-Serial-Number, + id-Service-Areas-List, + id-WarningSecurityInfo, + id-Warning-Type, + id-Broadcast-Message-Content-Validity-Indicator +FROM SABP-Constants; +``` + +``` + +-- ***** +-- +-- Write-Replace +-- +-- ***** + +Write-Replace ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Extensions} } OPTIONAL, + ... +} + +Write-Replace-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-New-Serial-Number CRITICALITY reject TYPE New-Serial-Number PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY ignore TYPE Old-Serial-Number PRESENCE optional } | + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } | + { ID id-Category CRITICALITY ignore TYPE Category PRESENCE optional } | + { ID id-Repetition-Period CRITICALITY reject TYPE Repetition-Period PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Requested + CRITICALITY reject TYPE Number-of-Broadcasts-Requested PRESENCE mandatory } | + { ID id-Data-Coding-Scheme CRITICALITY reject TYPE Data-Coding-Scheme PRESENCE mandatory } | + { ID id-Broadcast-Message-Content + CRITICALITY reject TYPE Broadcast-Message-Content PRESENCE mandatory }, + ... +} + +Write-Replace-Extensions SABP-PROTOCOL-EXTENSION ::= { + { ID id-WarningSecurityInfo CRITICALITY ignore EXTENSION WarningSecurityInfo PRESENCE optional } | + { ID id-Paging-ETWS-Indicator CRITICALITY ignore EXTENSION Paging-ETWS-Indicator PRESENCE optional } | + { ID id-Warning-Type CRITICALITY ignore EXTENSION Warning-Type PRESENCE optional } | + { ID id-Broadcast-Message-Content-Validity-Indicator CRITICALITY ignore EXTENSION Broadcast-Message-Content-Validity-Indicator PRESENCE optional }, + ... +} + +-- ***** +-- +-- Write-Replace-Complete +-- +-- ***** + +Write-Replace-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-Complete-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Complete-Extensions} } OPTIONAL, + ... +} + +Write-Replace-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-New-Serial-Number CRITICALITY reject TYPE New-Serial-Number PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY reject TYPE Number-of-Broadcasts-Completed-List + PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + +``` + +``` + +CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Write-Replace-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Write-Replace-Failure +-- +-- ***** + +Write-Replace-Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-Failure-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Failure-Extensions} } OPTIONAL, + ... +} + +Write-Replace-Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-New-Serial-Number CRITICALITY reject TYPE New-Serial-Number PRESENCE mandatory } | + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY ignore TYPE Number-of-Broadcasts-Completed-List + PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Write-Replace-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Kill +-- +-- ***** + +Kill ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Kill-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Kill-Extensions} } OPTIONAL, + ... +} + +Kill-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } , + ... +} + +Kill-Extensions SABP-PROTOCOL-EXTENSION ::= { + +``` + +``` + + ... + } + + -- ***** + -- + -- Kill-Complete + -- + -- ***** + + Kill-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Kill-Complete-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Kill-Complete-Extensions}} OPTIONAL, + ... + } + + Kill-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY reject TYPE Number-of-Broadcasts-Completed-List + PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... + } + + Kill-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- Kill-Failure + -- + -- ***** + + Kill-Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Kill-Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Kill-Failure-Extensions}} OPTIONAL, + ... + } + + Kill-Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY ignore TYPE Number-of-Broadcasts-Completed-List + PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... + } + + Kill-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + +``` + +``` + + ... + } + + -- ***** + -- + -- Load-Query + -- + -- ***** + + Load-Query ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Load-Query-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Load-Query-Extensions}} OPTIONAL, + ... + } + + Load-Query-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } , + ... + } + + Load-Query-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- Load-Query-Complete + -- + -- ***** + + Load-Query-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Load-Query-Complete-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Load-Query-Complete-Extensions}} OPTIONAL, + ... + } + + Load-Query-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Radio-Resource-Loading-List + CRITICALITY reject TYPE Radio-Resource-Loading-List + PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... + } + + Load-Query-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- Load-Query-Failure + -- + -- ***** + +``` + +``` + +Load-Query-Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Load-Query-Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Load-Query-Failure-Extensions}} OPTIONAL, + ... +} + +Load-Query-Failure-IEs SABP-PROTOCOL-IES ::= { + + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Radio-Resource-Loading-List + CRITICALITY ignore TYPE Radio-Resource-Loading-List + PRESENCE optional } | + + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Load-Query-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Message-Status-Query +-- +-- ***** + +Message-Status-Query ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Message-Status-Query-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Message-Status-Query-Extensions}} OPTIONAL, + ... +} + +Message-Status-Query-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } , + ... +} + +Message-Status-Query-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Message-Status-Query-Complete +-- +-- ***** + +Message-Status-Query-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Message-Status-Query-Complete-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Message-Status-Query-Complete-Extensions}} OPTIONAL, + ... +} + +``` + +``` + +Message-Status-Query-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY reject TYPE Number-of-Broadcasts-Completed-List + PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Message-Status-Query-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Message-Status-Query-Failure +-- +-- ***** + +Message-Status-Query-Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Message-Status-Query-Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Message-Status-Query-Failure-Extensions}} OPTIONAL, + ... +} + +Message-Status-Query-Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Old-Serial-Number CRITICALITY reject TYPE Old-Serial-Number PRESENCE mandatory } | + { ID id-Number-of-Broadcasts-Completed-List + CRITICALITY ignore TYPE Number-of-Broadcasts-Completed-List + PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Message-Status-Query-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset +-- +-- ***** + +Reset ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Reset-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Reset-Extensions}} OPTIONAL, + ... +} + +``` + +``` + +Reset-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } , + ... +} + +Reset-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset-Complete +-- +-- ***** + +Reset-Complete ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Reset-Complete-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Reset-Complete-Extensions}} OPTIONAL, + ... +} + +Reset-Complete-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE mandatory } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional } , + ... +} + +Reset-Complete-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset-Failure +-- +-- ***** + +Reset-Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Reset-Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Reset-Failure-Extensions}} OPTIONAL, + ... +} + +Reset-Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Failure-List CRITICALITY reject TYPE Failure-List PRESENCE mandatory } | + { ID id-Service-Areas-List CRITICALITY reject TYPE Service-Areas-List PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional } , + ... +} + +Reset-Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + } + + -- ***** + -- + -- Restart + -- + -- ***** + + Restart ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Restart-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Restart-Extensions}} OPTIONAL, + ... + } + + Restart-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY ignore TYPE Service-Areas-List PRESENCE mandatory } | + { ID id-Recovery-Indication CRITICALITY ignore TYPE Recovery-Indication PRESENCE optional } , + ... + } + + Restart-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- Failure + -- + -- ***** + + Failure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Failure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Failure-Extensions}} OPTIONAL, + ... + } + + Failure-IEs SABP-PROTOCOL-IES ::= { + { ID id-Service-Areas-List CRITICALITY ignore TYPE Service-Areas-List PRESENCE mandatory } , + ... + } + + Failure-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- Error-Indication + -- + -- ***** + + Error-Indication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{Error-Indication-IEs}}, + protocolExtensions ProtocolExtensionContainer {{Error-Indication-Extensions}} OPTIONAL, + ... + } +``` + +``` + +} + +Error-Indication-IEs SABP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY ignore TYPE Message-Identifier PRESENCE optional } | + { ID id-Serial-Number CRITICALITY ignore TYPE Serial-Number PRESENCE optional } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } | + { ID id-Criticality-Diagnostics + CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +Error-Indication-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} + +END + +``` + +### 9.3.4 Information Element Definitions + +``` + +-- ***** +-- +-- Information Element Definitions +-- +-- ***** + +SABP-IEs { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) sabp (3) version1 (1) sabp-IEs (2) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + maxNrOfErrors, + maxnoofSAI, + maxNrOfLevels, + + id-MessageStructure, + id-TypeOfError + +FROM SABP-Constants + + Criticality, + ProcedureCode, + TriggeringMessage, + ProtocolIE-ID +FROM SABP-CommonDataTypes + + ProtocolExtensionContainer{}, + +``` + +``` +SABP-PROTOCOL-EXTENSION +FROM SABP-Containers; +``` + +``` +-- A +``` + +``` +Available-Bandwidth ::= INTEGER (0..20480) +-- bits/sec +``` + +``` +-- B +``` + +``` +Broadcast-Message-Content ::= BIT STRING (SIZE (1..9968))-- This IE is sent from the CN to the RNC containing user information i.e. +-- the message. +``` + +``` +Broadcast-Message-Content-Validity-Indicator ::= ENUMERATED { + broadcast-Message-Content-not-valid, + ... +} +``` + +``` +-- C +``` + +``` +Category ::= ENUMERATED { + high-priority, + background-priority, + normal-priority, + default-priority, + ... +} +``` + +``` +Cause ::= INTEGER { + parameter-not-recognised (0), + parameter-value-invalid (1), + valid-CN-message-not-identified (2), + service-area-identity-not-valid (3), + unrecognised-message (4), + missing-mandatory-element (5), + rNC-capacity-exceeded (6), + rNC-memory-exceeded (7), + service-area-broadcast-not-supported (8), + service-area-broadcast-not-operational (9), + message-reference-already-used (10), + unspecified-error (11), + transfer-syntax-error (12), + semantic-error (13), + message-not-compatible-with-receiver-state (14), + abstract-syntax-error-reject (15), + abstract-syntax-error-ignore-and-notify (16), + abstract-syntax-error-falsely-constructed-message (17) +} (0..255) +``` + +``` +Criticality-Diagnostics ::= SEQUENCE { + procedureCode ProcedureCode OPTIONAL, + triggeringMessage TriggeringMessage OPTIONAL, + procedureCriticality Criticality OPTIONAL, + iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, +``` + +``` + +iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, +... +} + +CriticalityDiagnostics-ExtIEs SABP-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 SABP-PROTOCOL-EXTENSION ::= { + { ID id-MessageStructure CRITICALITY ignore EXTENSION MessageStructure PRESENCE optional } | + { 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 SABP-PROTOCOL-EXTENSION ::= { +... +} + +-- D + +Data-Coding-Scheme ::= BIT STRING (SIZE (8)) + +-- E + +-- F + +Failure-List ::= SEQUENCE (SIZE (1..maxnoofSAI)) OF Failure-List-Item + +Failure-List-Item ::= SEQUENCE { + service-area-identifier Service-Area-Identifier, + cause Cause, + iE-Extensions ProtocolExtensionContainer { {FailureListItemIE-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` +FailureListItemIE-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +-- G + +-- H + +-- I + +-- J + +-- K + +-- L + +-- M + +Message-Identifier ::= BIT STRING (SIZE (16)) + +-- N + +New-Serial-Number ::= Serial-Number + +Number-of-Broadcasts-Completed-List ::= SEQUENCE (SIZE (1..maxnoofSAI)) OF + Number-of-Broadcasts-Completed-List-Item + +Number-of-Broadcasts-Completed-List-Item ::= SEQUENCE { + service-area-identifier Service-Area-Identifier, + number-of-broadcasts-completed INTEGER (0..65535), + number-of-broadcasts-completed-info Number-Of-Broadcasts-Completed-Info OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {NoOfBroadcastsCompletedListItemIE-ExtIEs} } OPTIONAL, + ... +} + +NoOfBroadcastsCompletedListItemIE-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +Number-Of-Broadcasts-Completed-Info ::= ENUMERATED { + overflow, + unknown, + ... +} + +Number-of-Broadcasts-Requested ::= INTEGER { + broadcast-indefinitely (0) +} (0..65535) + +-- O + +Old-Serial-Number ::= Serial-Number + +-- P +``` + +``` + +Paging-ETWS-Indicator ::= ENUMERATED { + paging, + ... +} + +-- Q + +-- R + +Radio-Resource-Loading-List ::= SEQUENCE (SIZE (1..maxnoofSAI)) OF + Radio-Resource-Loading-List-Item + +Radio-Resource-Loading-List-Item ::= SEQUENCE { + service-area-identifier Service-Area-Identifier, + available-bandwidth Available-Bandwidth, + iE-Extensions ProtocolExtensionContainer { {RadioResourceLoadingListItemIE-ExtIEs} } OPTIONAL, + ... +} + +RadioResourceLoadingListItemIE-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +Recovery-Indication ::= ENUMERATED { + data-lost, + data-available +} + +RepetitionNumber0 ::= INTEGER(0..255) + +RepetitionNumber1 ::= INTEGER(1..256) + +Repetition-Period ::= INTEGER (1..4096) +-- Each unit represents a repetition of one second to a maximum of +-- once per 4096 seconds (~1 hour). + +-- S + +Serial-Number ::= BIT STRING (SIZE (16)) + +Service-Area-Identifier ::= SEQUENCE { + pLMNIdentity OCTET STRING (SIZE (3)) + -- Digits 0 to 9, two digits per octet. -- + -- Each octet 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 3 digit MNC). -- , + lac OCTET STRING (SIZE (2)) + -- 0000 and FFFE not allowed -- , +} + +``` + +``` + + sac OCTET STRING (SIZE (2)) + } + + -- **TODO** The IE type for these parameters is not known as yet + Service-Areas-List ::= SEQUENCE (SIZE (1..maxnoofSAI)) OF Service-Area-Identifier + + -- T + + TypeOfError ::= ENUMERATED { + not-understood, + missing, + ... + } + + -- U + + -- V + + -- W + + WarningSecurityInfo ::= OCTET STRING (SIZE (50)) + + Warning-Type ::= OCTET STRING (SIZE (2)) + + -- X + + -- Y + +END + +``` + +### 9.3.5 Common Definitions + +``` + +-- ************************************************************** +-- +-- Common definitions +-- +-- ************************************************************** + +SABP-CommonDataTypes { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +umts-Access (20) modules (3) sabp (3) version1 (1) sabp-CommonDataTypes (3) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +Criticality ::= ENUMERATED { reject, ignore, notify } + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +ProcedureCode ::= INTEGER (0..255) + +ProtocolExtensionID ::= INTEGER (0..65535) + +``` + +``` + +ProtocolIE-ID ::= INTEGER (0..65535) + +TriggeringMessage ::= ENUMERATED {initiating-message, successful-outcome, unsuccessful-outcome, outcome} + +END + +``` + +### 9.3.6 Constant Definitions + +``` + +-- ***** +-- +-- Constant definitions +-- +-- ***** + +SABP-Constants { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) sabp (3) version1 (1) sabp-Constants (4) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- Elementary Procedures +-- +-- ***** + +id-Write-Replace INTEGER ::= 0 +id-Kill INTEGER ::= 1 +id-Load-Status-Enquiry INTEGER ::= 2 +id-Message-Status-Query INTEGER ::= 3 +id-Restart-Indication INTEGER ::= 4 +id-Reset INTEGER ::= 5 +id-Failure-Indication INTEGER ::= 6 +id-Error-Indication INTEGER ::= 7 + +-- ***** +-- +-- IEs +-- +-- ***** + +id-Broadcast-Message-Content INTEGER ::= 0 +id-Category INTEGER ::= 1 +id-Cause INTEGER ::= 2 +id-Criticality-Diagnostics INTEGER ::= 3 +id-Data-Coding-Scheme INTEGER ::= 4 +id-Failure-List INTEGER ::= 5 +id-Message-Identifier INTEGER ::= 6 +id-New-Serial-Number INTEGER ::= 7 +id-Number-of-Broadcasts-Completed-List INTEGER ::= 8 +id-Number-of-Broadcasts-Requested INTEGER ::= 9 + +``` + +``` + +id-Old-Serial-Number INTEGER ::= 10 +id-Radio-Resource-Loading-List INTEGER ::= 11 +id-Recovery-Indication INTEGER ::= 12 +id-Repetition-Period INTEGER ::= 13 +id-Serial-Number INTEGER ::= 14 +id-Service-Areas-List INTEGER ::= 15 +id-MessageStructure INTEGER ::= 16 +id-TypeOfError INTEGER ::= 17 +id-Paging-ETWS-Indicator INTEGER ::= 18 +id-Warning-Type INTEGER ::= 19 +id-WarningSecurityInfo INTEGER ::= 20 +id-Broadcast-Message-Content-Validity-Indicator INTEGER ::= 21 + +-- ***** +-- +-- Extension constants +-- +-- ***** + +-- ***** +-- +-- Lists +-- +-- ***** + +maxNrOfErrors INTEGER ::= 256 +maxnoofSAI INTEGER ::= 65535 + +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 +maxNrOfLevels INTEGER ::= 256 + +END + +``` + +### 9.3.7 Container Definitions + +``` + +-- ***** +-- +-- Container definitions +-- +-- ***** + +SABP-Containers { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) sabp (3) version1 (1) sabp-Containers (5) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- + +``` + +``` + +-- ***** + +IMPORTS + Criticality, + Presence, + ProtocolExtensionID, + ProtocolIE-ID +FROM SABP-CommonDataTypes + + maxProtocolExtensions, + maxProtocolIEs +FROM SABP-Constants; + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +SABP-PROTOCOL-IES ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality DEFAULT ignore, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Protocol Extensions +-- +-- ***** + +SABP-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolExtensionID UNIQUE, + &criticality Criticality DEFAULT ignore, + &Extension, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ***** +-- +-- Container for Protocol IEs +-- +-- ***** + +``` + +``` +-- ***** + +ProtocolIE-Container {SABP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field {SABP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id SABP-PROTOCOL-IES.&id ({IEsSetParam}), + criticality SABP-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}), + value SABP-PROTOCOL-IES.&Value ({IEsSetParam}{@id}) +} + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, SABP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +ProtocolExtensionContainer {SABP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + +ProtocolExtensionField {SABP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id SABP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), + criticality SABP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), + extensionValue SABP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) +} + +END +``` + +## 9.4 Message Transfer Syntax + +SABP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. ITU-T Rec. X.691 [9]. + +# 10 Handling of Unknown, Unforeseen or 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: + +![Diagram illustrating Protocol Errors in SABP. It shows two boxes: 'SABP functional entity' at the top and 'ASN.1 Decoding' at the bottom. A dashed double-headed arrow points between them. To the right of the top box, a curly brace groups 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the bottom box, a curly brace groups 'Transfer Syntax Errors'. A large vertical arrow on the far right points upwards, indicating the flow of error reporting from Transfer Syntax Errors to the others.](6b9ee906d502aece4a2becf5895db07a_img.jpg) + +``` + +graph TD + subgraph SABP_errors [ ] + LE[Logical Errors] + ASE[Abstract Syntax Errors] + end + subgraph Transfer_errors [ ] + TSE[Transfer Syntax Errors] + end + SABP[SABP functional entity] --- LE + SABP --- ASE + ASN1[ASN.1 Decoding] --- TSE + ASN1 -.-> SABP + TSE --> LE + TSE --> ASE + style SABP fill:none,stroke:none + style ASN1 fill:none,stroke:none + style LE fill:none,stroke:none + style ASE fill:none,stroke:none + style TSE fill:none,stroke:none + style SABP_errors fill:none,stroke:none + style Transfer_errors fill:none,stroke:none + +``` + +Diagram illustrating Protocol Errors in SABP. It shows two boxes: 'SABP functional entity' at the top and 'ASN.1 Decoding' at the bottom. A dashed double-headed arrow points between them. To the right of the top box, a curly brace groups 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the bottom box, a curly brace groups 'Transfer Syntax Errors'. A large vertical arrow on the far right points upwards, indicating the flow of error reporting from Transfer Syntax Errors to the others. + +**Figure 14: Protocol Errors in SABP** + +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. + +## 10.3 Abstract Syntax Error + +### 10.3.1 General + +An Abstract Syntax Error occurs when the receiving functional SABP 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 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 SABP 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 the 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, SABP 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 SABP-PROTOCOL-IES, SABP-PROTOCOL-IES-PAIR, SABP-PROTOCOL-EXTENSION or SABP-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. + +### 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* according to the following: + +Reject IE: + +- If a message is received with a *Procedure Code* 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* 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* 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 groups 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 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 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*" which 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 IE/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 only 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 A) 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 A) 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 the present document 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/IE groups 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 A) 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 A) 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 IE's/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. + +## 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. + +# Annex A (informative): Guidelines for Usage of the Criticality Diagnostics IE + +## A.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.4. + +## A.2 Example on a Received EXAMPLE MESSAGE + +Assume further more that a received message based on the above tabular format is according to figure A.1. + +![A hierarchical tree diagram showing the structure of a received message across four levels. Level 1 (top level) contains nodes A, B, C, and D. Level 2 contains node E (connected to B) and node K (connected to C). Level 3 contains nodes F (dashed box, connected to E), H (connected to E), G (connected to E), J (dashed box, connected to K), and L (dashed box, connected to K). Level 4 contains seven nodes, each labeled G, connected to the nodes in Level 3. Below the diagram is a legend indicating that overlapping boxes represent repetitions (1st, 2nd, ..., Nth). A solid box represents an IE based on a protocol container, and a dashed box represents an IE being an 'ordinary' ASN.1 type.](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +Legend: + +- 1st repetition +- 2nd repetition +- ... +- Nth repetition + +□ IE based on a protocol container + +⬮ IE being an "ordinary" ASN.1 type + +A hierarchical tree diagram showing the structure of a received message across four levels. Level 1 (top level) contains nodes A, B, C, and D. Level 2 contains node E (connected to B) and node K (connected to C). Level 3 contains nodes F (dashed box, connected to E), H (connected to E), G (connected to E), J (dashed box, connected to K), and L (dashed box, connected to K). Level 4 contains seven nodes, each labeled G, connected to the nodes in Level 3. Below the diagram is a legend indicating that overlapping boxes represent repetitions (1st, 2nd, ..., Nth). A solid box represents an IE based on a protocol container, and a dashed box represents an IE being an 'ordinary' ASN.1 type. + +Figure A.1: Example of content of a received SABP message based on the EXAMPLE MESSAGE + +## A.3 Content of Criticality Diagnostics + +### A.3.1 Example 1 + +![Diagram of a received SABP message structure showing four levels of Information Elements (IEs). 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 (instance 5), J, and L. Level 4 contains multiple instances of IE G (instances 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14). IE E (level 2) is included in the Message Structure IE. IE J (level 3) is not included in the Message Structure IE. IE G (level 4) instance 11 is highlighted in grey and marked as a not comprehended IE. This IE is included in the Information Element Criticality Diagnostics IE, which contains a) IE ID IE and b) Repetition Number IE.](76d19e4271bf243b20d55a98efd51483_img.jpg) + +Diagram of a received SABP message structure showing four levels of Information Elements (IEs). 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 (instance 5), J, and L. Level 4 contains multiple instances of IE G (instances 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14). IE E (level 2) is included in the Message Structure IE. IE J (level 3) is not included in the Message Structure IE. IE G (level 4) instance 11 is highlighted in grey and marked as a not comprehended IE. This IE is included in the Information Element Criticality Diagnostics IE, which contains a) IE ID IE and b) Repetition Number IE. + +**Figure A.2: Example of a received SABP 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, 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.3.2 Example 2 + +![Diagram of a received SABP message structure showing 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 E), and L (under K). Level 4 contains multiple G boxes under F, H, J, and L. Annotations indicate that C is included in the Message Structure IE, and the Information Element Criticality Diagnostics IE includes IE ID IE and Repetition Number IE.](a9159a006d67a834a7b1a771c18191cc_img.jpg) + +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 of a received SABP message structure showing 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 E), and L (under K). Level 4 contains multiple G boxes under F, H, J, and L. Annotations indicate that C is included in the Message Structure IE, and the Information Element Criticality Diagnostics IE includes IE ID IE and Repetition Number IE. + +**Figure A.3: Example of a received SABP 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, 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 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.3.3 Example 3 + +![Diagram illustrating a received SABP message structure with four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (with instances 1, 2, 3, 4) and K. Level 3 contains F (dashed), H (with instances 1, 2), G, J (dashed), and L (dashed). Level 4 contains multiple G instances. Arrows indicate that B, C, and E are included in the Message Structure IE, and H is included in the Information Element Criticality Diagnostics IE. A grey box highlights an error instance in H's G instance.](9cb54072e43a6b6717eb16036a7640a2_img.jpg) + +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 received SABP message structure with four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (with instances 1, 2, 3, 4) and K. Level 3 contains F (dashed), H (with instances 1, 2), G, J (dashed), and L (dashed). Level 4 contains multiple G instances. Arrows indicate that B, C, and E are included in the Message Structure IE, and H is included in the Information Element Criticality Diagnostics IE. A grey box highlights an error instance in H's G instance. + +**Figure A.4: Example of a received SABP 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, 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.3.4 Example 4 + +![Diagram of a received SABP message structure showing levels 1 to 4. 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 (grey, instance 5), J, and L. Level 4 contains multiple instances of IE G (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14). Arrows indicate that IE E is included in the Message Structure IE, and IE G (grey) is included in the Information Element Criticality Diagnostics IE.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +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 of a received SABP message structure showing levels 1 to 4. 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 (grey, instance 5), J, and L. Level 4 contains multiple instances of IE G (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14). Arrows indicate that IE E is included in the Message Structure IE, and IE G (grey) is included in the Information Element Criticality Diagnostics IE. + +**Figure A.5: Example of a received SABP 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, 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.3.5 Example 5 + +![Diagram of a received SABP message structure 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, 13). Arrows indicate that IE E is included in the Message Structure IE and that IE G (instance 4) is included in the Information Element Criticality Diagnostics IE.](b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg) + +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* + +Diagram of a received SABP message structure 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, 13). Arrows indicate that IE E is included in the Message Structure IE and that IE G (instance 4) is included in the Information Element Criticality Diagnostics IE. + +**Figure A.6: Example of a received SABP 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, 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.4 ASN.1 of EXAMPLE MESSAGE + +``` + +ExampleMessage ::= SEQUENCE { + ProtocolIEs ProtocolIE-Container {{ExampleMessage-IEs}}, + ProtocolExtensions ProtocolExtensionContainer {{ExampleMessage-Extensions}} OPTIONAL, + ... +} + +ExampleMessage-IEs SABP-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 SABP-PROTOCOL-EXTENSION ::= { + ... +} + +E-List ::= SEQUENCE (SIZE (1..maxE)) OF ProtocolIE-Container { {E-IEs} } + +E-IEs SABP-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 SABP-PROTOCOL-EXTENSION ::= { + ... +} + +F-List ::= SEQUENCE (SIZE (1..maxF)) OF F + +F ::= SEQUENCE { + g G-List2 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {F-ExtIEs} } OPTIONAL, + ... +} + +F-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +G-List2 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G2-IEs} } + +G2-IEs SABP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY ignore TYPE G PRESENCE mandatory } + ... +} + +H-List ::= SEQUENCE (SIZE (1..maxH)) OF ProtocolIE-Container { {H-IEs} } + +H-IEs SABP-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 SABP-PROTOCOL-EXTENSION ::= { + ... +} + +G-List3 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G3-IEs} } + +G3-IEs SABP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY notify TYPE G PRESENCE mandatory }, + ... +} + +G-List1 ::= ProtocolIE-Container { {G1-IEs} } + +G1-IEs SABP-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 SABP-PROTOCOL-EXTENSION ::= { + ... +} + +G-List4 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G4-IEs} } + +G4-IEs SABP-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 SABP-PROTOCOL-IES ::= { + { ID id-K CRITICALITY notify TYPE K PRESENCE mandatory }, + ... +} + +K ::= SEQUENCE { + l L-List, + iE-Extensions ProtocolExtensionContainer { {K-ExtIEs} } OPTIONAL, + ... +} + +K-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} + +L-List ::= SEQUENCE (SIZE (1..maxL)) OF L + +L ::= SEQUENCE { + m M OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {L-ExtIEs} } OPTIONAL, + ... +} + +L-ExtIEs SABP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ExampleMessage-Extensions SABP-PROTOCOL-EXTENSION ::= { + ... +} +``` \ No newline at end of file diff --git a/marked/Rel-18/25_series/25420/raw.md b/marked/Rel-18/25_series/25420/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fa6e0194d5819879a2e722b9ab33d10449062738 --- /dev/null +++ b/marked/Rel-18/25_series/25420/raw.md @@ -0,0 +1,935 @@ + + +# 3GPP TS 25.420 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iur interface general aspects and principles (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 3.2 Specification Notations ..... | 8 | +| 4 General Aspects ..... | 9 | +| 4.1 Introduction ..... | 9 | +| 4.2 Iur Interface General Principles ..... | 9 | +| 4.3 Iur Interface Specification Objectives..... | 9 | +| 4.3.1 General ..... | 9 | +| 4.3.2 Addressing of RNSs over the Iur Interface ..... | 9 | +| 4.4 Iur Interface Capabilities..... | 10 | +| 4.4.1 Radio application related signalling ..... | 10 | +| 4.4.2 Iub/Iur DCH data streams..... | 10 | +| 4.4.3 Iur RACH data streams ..... | 10 | +| 4.4.4 Iur DSCH data streams [TDD]..... | 10 | +| 4.4.5 Iur USCH data streams [TDD]..... | 10 | +| 4.4.6 Iur FACH data streams..... | 10 | +| 4.4.7 Iur HS-DSCH data streams ..... | 10 | +| 4.4.8 Iub/Iur E-DCH data streams..... | 10 | +| 4.4.9 Iur IuUP data streams for CS data forwarding ..... | 11 | +| 4.5 Iur Interface Characteristics ..... | 11 | +| 4.5.1 Uses of SCCP ..... | 11 | +| 4.5.1.1 General..... | 11 | +| 4.5.1.2 SCCP connection establishment ..... | 11 | +| 4.5.1.3 Establishment procedure initiated from the SRNC..... | 11 | +| 4.5.1.3A Establishment procedure initiated from an RNC requesting common measurements or information..... | 12 | +| 4.5.1.4 SCCP connection release..... | 13 | +| 4.5.1.5 General SCCP Abnormal Conditions ..... | 13 | +| 4.5.1.5.1 SCCP bearer failure..... | 13 | +| 4.5.1.5.2 SCCP connection failure ..... | 13 | +| 4.5.2 SCCP Addressing Scheme ..... | 14 | +| 4.5.2.1 General..... | 14 | +| 5 Functions of the I ur Interface Protocols..... | 14 | +| 5.1 Functional List..... | 14 | +| 5.2 Functional Split over Iur ..... | 15 | +| 5.2.1 Combining/Splitting ..... | 15 | +| 5.2.2 Control of Combining/Splitting Topology ..... | 15 | +| 5.2.3 Handling of DRNS Hardware Resources ..... | 15 | +| 5.2.4 Allocation of Physical Channels ..... | 15 | +| 5.2.5 UpLink Power Control ..... | 15 | +| 5.2.6 Down-Link Power Control ..... | 15 | +| 5.2.7 Admission Control..... | 16 | +| 5.2.8 Radio Protocol Functional Split ..... | 16 | +| 5.2.9 MBMS Bearer Type Control..... | 16 | +| 5.2.10 MBSFN MCCH Information Control ..... | 16 | +| 6 I ur Interface Protocols..... | 16 | +| 6.1 General ..... | 16 | +| 6.2 Radio Signalling Protocols..... | 17 | +| 6.2.1 RNSAP Protocol..... | 17 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------| +| 6.3 | User Plane Frame Protocols ..... | 17 | +| 6.3.1 | Iub/Iur DCH Frame Protocol ..... | 17 | +| 6.3.2 | Iur DSCH Frame Protocol [TDD] ..... | 18 | +| 6.3.3 | Iur USCH Frame Protocol [TDD] ..... | 18 | +| 6.3.4 | Iur RACH Frame Protocol ..... | 18 | +| 6.3.5 | Iur FACH Frame Protocol ..... | 18 | +| 6.3.6 | Iur HS-DSCH Frame Protocol ..... | 18 | +| 6.3.7 | Iur E-DCH Frame Protocol ..... | 19 | +| 6.4 | Mapping of Frame Protocols onto transport bearers ..... | 19 | +| 7 | DRNS logical Model over I ur ..... | 19 | +| 7.1 | Overview ..... | 19 | +| 7.2 | Logical Model Elements ..... | 20 | +| 7.2.1 | Radio Link ..... | 20 | +| 7.2.2 | Cell ..... | 20 | +| 7.2.3 | Iur DCH Data Port ..... | 20 | +| 7.2.4 | Iur DSCH Data Port [TDD] ..... | 21 | +| 7.2.5 | Iur USCH Data Port [TDD] ..... | 21 | +| 7.2.6 | Iur RACH/FACH Data Port ..... | 21 | +| 7.2.7 | Iur Control Port ..... | 21 | +| 7.2.8 | Iur HS-DSCH Data Port ..... | 21 | +| 7.2.9 | Iur E-DCH Data Port ..... | 21 | +| 8 | I ur Interface Protocol Structure ..... | 21 | +| 9 | Other I ur Interface Specifications ..... | 22 | +| 9.1 | UTRAN Iur Interface: Layer 1 (TS 25.421) ..... | 22 | +| 9.2 | UTRAN Iur Interface: Signalling Transport (TS 25.422) ..... | 22 | +| 9.3 | UTRAN Iur Interface: RNSAP Specification (TS 25.423) ..... | 22 | +| 9.4 | UTRAN Iur Interface: Data Transport and Transport Signalling for Common Transport Channel Data Streams (TS 25.424) ..... | 22 | +| 9.5 | UTRAN Iur Interface: User Plane Protocols for Common Transport Channel Data Streams (TS 25.425) ..... | 22 | +| 9.6 | UTRAN Iur & Iub Interface: Data Transport and Transport Signalling for DCH Data Streams (TS 25.426) ..... | 23 | +| 9.7 | UTRAN Iur & Iub Interface: User Plane Protocols for DCH Data Streams (TS 25.427) ..... | 23 | +| 9.8 | Summary of UTRAN Iur Interface Technical Specifications ..... | 23 | +| Annex A (informative): | Change History ..... | 24 | + +# --- 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 is an introduction to the TSG RAN TS 25.42x series of UMTS Technical Specifications that define the Iur Interface. It is a logical interface for the interconnection of two Radio Network Controller (RNC) components of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.427: "UTRAN Iub/Iur Interface User Plane Protocol for DCH Data Streams". +- [2] 3GPP TS 25.425: "UTRAN Iur Interface: User Plane Protocols for Common Transport Channel Data Streams". +- [3] 3GPP TS 25.421: "UTRAN Iur Interface: Layer 1". +- [4] 3GPP TS 25.422: "UTRAN Iur Interface: Signalling Transport". +- [5] 3GPP TS 25.423: "UTRAN Iur Interface: Radio Network Subsystem Application Part (RNSAP) signalling". +- [6] 3GPP TS 25.424: "UTRAN Iur Interface: Data Transport & Transport Signalling ". +- [7] Void +- [8] 3GPP TS 25.426: "UTRAN Iur & Iub Interface: Data Transport & Transport Signalling for DCH Data Streams". +- [9] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part". +- [10] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages". +- [11] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes". +- [12] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures". +- [13] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [14] Void +- [15] Void +- [16] Void +- [17] 3GPP TR 43.930: "Iur-g interface; Stage 2". +- [18] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast/Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2". +- [19] 3GPP TS 25.319: "Enhanced Uplink; Overall description; Stage 2". + +[20] + +3GPP TS 25.415: "UTRAN Iu interface user plane protocols" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +None. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|------------------------------------------------------------------| +| AAL2 | ATM Adaptation Layer type 2 | +| AAL5 | ATM Adaptation Layer type 5 | +| ALCAP | Access Link Control Application Part | +| ATM | Asynchronous Transfer Mode | +| BSS | Base Station Subsystem | +| CRNC | Controlling RNC | +| CTP | Common Transport Protocol | +| DCH | Dedicated Transport Channel | +| DL | Downlink | +| DPCH | Dedicated Physical Channel | +| DRNC | Drift Radio Network Controller | +| DRNS | Drift Radio Network Subsystem | +| DSCH | Downlink Shared Channel | +| E-DCH | Enhanced Dedicated Channel | +| EDGE | Enhanced Data rates for GSM Evolution | +| FACH | Forward Access Channel | +| F-DPCH | Fractional DPCH | +| FFS | For Further Study | +| GERAN | GSM/EDGE Radio Access Network | +| GSM | Global System for Mobile communications | +| GT | Global Title | +| HARQ | Hybrid Automatic Repeat Request | +| HS-DSCH | High Speed Downlink Shared Channel | +| IP | Internet Protocol | +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast Multicast Service | +| MRNC | MBMS Master RNC | +| MTP3-B | Message Transfer Part level 3 (for Q.2140) | +| PLMN | Public Land Mobile Network | +| PTM | Point To Multipoint | +| PTP | Point To Point | +| QoS | Quality of Service | +| RACH | Random Access Channel | +| RF | Radio Frequency | +| RNC | Radio Network Controller | +| RNS | Radio Network Subsystem | +| RNSAP | Radio Network Subsystem Application Part | +| RRC | Radio Resource Control | +| SCCP | Signalling Connection Control Part | +| SPC | Signalling Point Code | +| SRNC | Serving Radio Network Controller | +| SRNS | Serving Radio Network Subsystem | +| SS7 | Signalling System N° 7 | +| SSCF-NNI | Service Specific Co-ordination Function – Network Node Interface | +| SSCOP | Service Specific Connection Oriented Protocol | +| SSN | Sub-System Number | + +| | | +|-------|-------------------------------------------| +| STC | Signalling Transport Converter | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UL | Up-link | +| UMTS | Universal Mobile Telecommunication System | +| URA | UTRAN Registration Area | +| USCH | Uplink Shared Channel | +| UTRAN | UMTS Terrestrial Radio Access Network | + +## 3.2 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 7.68 Mcps TDD, 3.84Mcps 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 7.68 Mcps TDD, 3.84Mcps 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 7.68 Mcps TDD, 3.84Mcps 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 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. RNSAP Basic Mobility Procedures. | +| Message | When referring to a message in the specification, the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message. | +| Frame | When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DCH data frame. | + +# --- 4 General Aspects + +## 4.1 Introduction + +The logical connection that exists between any two RNCs within the UTRAN is referred to as the Iur interface. + +## 4.2 Iur Interface General Principles + +The general principles for the specification of the Iur interface are as follows: + +- The Iur interface should be open; +- The Iur interface shall support the exchange of signalling information between two RNCs, in addition the interface may need to support one or more Iur data streams; +- From a logical standpoint, the Iur is a point-to-point interface between two RNCs within the UTRAN. A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the two RNCs. + +## 4.3 Iur Interface Specification Objectives + +### 4.3.1 General + +The Iur interface specifications shall facilitate the following: + +- inter-connection of RNCs supplied by different manufacturers; +- support of continuation between RNSs of the UTRAN services offered via the Iu interface; +- separation of Iur interface Radio Network functionality and Transport Network functionality to facilitate introduction of future technology. + +### 4.3.2 Addressing of RNSs over the Iur Interface + +- For an RRC connection using a dedicated channel or for a UE using F-DPCH in the downlink, the Iur standard shall allow the addition / deletion of radio links supported by cells belonging to any RNS within the PLMN. +- The specification of the Iur interface shall allow an RNC to address any other RNC within the PLMN for establishing a signalling bearer over Iur. +- The specification of the Iur interface shall allow an RNC to address any other RNC within the PLMN for establishing user data bearers for Iur data streams. + +RNSAP shall allow different kinds of addressing schemes to be used for the signalling bearer. + +## 4.4 Iur Interface Capabilities + +### 4.4.1 Radio application related signalling + +The Iur interface provides capability to support radio interface mobility between RNSs, of UEs having a connection with UTRAN. This capability includes the support of handover, radio resource handling, MBMS handling and synchronisation between RNSs. + +### 4.4.2 Iub/Iur DCH data streams + +The Iur interface provides the means for transport of uplink and downlink Iub/Iur DCH frames carrying user data and control information between SRNC and Node B (DRNS), via the DRNC. + +In the UTRAN, one DCH data stream always corresponds to a bi-directional transport channel. Although the TFS is configured separately for each DCH direction and a DCH could be configured with e.g. only a zero-bit transport format in one direction, the DCH is always treated as a bi-directional transport channel in the UTRAN. As a result, two uni-directional Uu DCH transport channels with opposite directions can be mapped to either one or two DCH transport channels in the UTRAN. + +### 4.4.3 Iur RACH data streams + +The Iur interface provides the means for transport of uplink RACH transport frames between DRNC and SRNC. + +### 4.4.4 Iur DSCH data streams [TDD] + +An Iur DSCH data stream corresponds to the data carried on one DSCH transport channel for one UE. A UE may have multiple Iur DSCH data streams. + +The Iur interface provides a means of transporting down link MAC-c/sh SDUs. In addition, the interface provides a means to the SRNC for queue reporting and a means for the DRNC to allocate capacity to the SRNC. + +### 4.4.5 Iur USCH data streams [TDD] + +An Iur USCH data stream corresponds to the data carried on one USCH transport channel for one UE. A UE may have multiple Iur USCH data streams. + +### 4.4.6 Iur FACH data streams + +The Iur interface provides the means for transport of downlink FACH transport frames between SRNC and DRNC. + +### 4.4.7 Iur HS-DSCH data streams + +An Iur HS-DSCH data stream corresponds to the data carried on one MAC-d flow for one UE. A UE may have multiple Iur HS-DSCH data streams. + +The Iur interface provides a means of transporting down link MAC-d PDUs. In addition, the interface provides a means to the SRNC for queue reporting and a means for the DRNC to allocate capacity to the SRNC. + +### 4.4.8 Iub/Iur E-DCH data streams + +The Iur interface provides the means for transport of Iub/Iur E-DCH frames carrying user data between NodeB (DRNS) and SRNC, via the DRNC. + +An Iur E-DCH data stream corresponds to the data carried on one MAC-d flow for one UE. A UE may have multiple E-DCH data streams. In addition, the interface provides the following: + +- A means for the Node B to indicate the number of HARQ retransmissions to the SRNC ITU-T Rec. Q.713 [11]; + +- A means to indicate to the SRNC, for the purposes of re-ordering, the CFN and Subframe Number that have been added by the Node B in the DRNSTS 25.427 [1]. + +### 4.4.9 Iur IuUP data streams for CS data forwarding + +In order to support data forwarding for CS services like during enhanced relocation, Iu UP protocol is used according to the procedures described in TS 25.415 [20] on the Iur link for forwarding the CS data from source RNC to target RNC. It is assumed that the Target RNC supports the same Iu UP mode version as the one used between the source SRNC and the CN. + +## 4.5 Iur Interface Characteristics + +### 4.5.1 Uses of SCCP + +#### 4.5.1.1 General + +The SCCP (ITU-T Rec. Q.711 [9] / ITU-T Rec. Q.712 [10]/ ITU-T Rec. Q.713 [11]/ ITU-T Rec. Q.714 [12]) is used to support signalling messages between two RNCs. One user function of the SCCP, called Radio Network Subsystem Application Part (RNSAP), is defined. The RNSAP uses one signalling connection per DRNC and UE where a UE is having one or more active radio links for the transfer of layer 3 messages. RNSAP also uses one signalling connection per RNC providing common measurements and information to a particular RNC (i.e. if measurements and information are transferred in both directions between a pair of RNCs, then two SCCP connections are used). + +Both connectionless and connection-oriented procedures are used to support the RNSAP. TS 25.423 [6] explains whether connection oriented or connectionless services should be used for a layer 3 procedure. + +The following subclauses describe the use of SCCP connections for RNSAP transactions. Subclause 4.5.1.2 describes the connection establishment procedures. Subclause 4.5.1.3 describes the connection establishment procedures initiated from SRNC. Subclause 4.5.1.4 describes the connection release procedures. Subclause 4.5.1.5 describes abnormal conditions. + +#### 4.5.1.2 SCCP connection establishment + +A new SCCP connection is established when information related to the communication between a UE and the network has to be exchanged between two RNCs, and no SCCP connection exists between the two RNCs involved, for the concerned UE. + +In this case, the SCCP connection is established by the SRNC. + +A new SCCP connection is established when a request for common measurements or information is made towards a particular RNC and no SCCP connection for common measurements and information transfer has been established from the RNC requesting the measurements or information towards the one providing the measurements or the information. + +In this case, the SCCP connection is established by the RNC requesting the measurements or the information. + +#### 4.5.1.3 Establishment procedure initiated from the SRNC + +The SCCP signalling connection establishment is initiated, by the SRNC, when the SRNC needs to request dedicated resources, i.e. a DCH, from a DRNC. + +##### Initiation + +- The SRNC sends the SCCP: CR message to the DRNC. The RADIO LINK SETUP REQUEST message or the ENHANCED RELOCATION REQUEST may be included in the user data field of an SCCP Connection Request message. + +##### Termination + +1. Successful outcome: + +- The SCCP Connection Confirm message, which may optionally contain a connection oriented RNSAP message in the user data field, is returned to the SRNC. +2. Unsuccessful outcome: +- If the SCCP signalling connection establishment fails, an SCCP Connection Refusal message will be sent back to the SRNC. This message may optionally contain a connection oriented RNSAP message. + +For more information on how the RNSAP procedures Radio Link Setup and Enhanced Relocation are handled, please see the procedures Radio Link Setup and Enhanced Relocation in TS 25.423 [5]. + +![Sequence diagram showing the setting-up of an SCCP Signalling Connection between an SRNC and a DRNC. The SRNC sends a CR message to the DRNC. The DRNC responds with either a CC message or a CREF message. A legend defines the parameters: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the SRNC, and y is SCCP connection reference at the DRNC.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant DRNC + Note right of SRNC: a1 = source local reference, +a2 = destination local reference +x = SCCP connection reference at the SRNC, +y = SCCP connection reference at the DRNC. + SRNC->>DRNC: CR {SSN=RNSAP, a1=x, +RNSAP message or no user data } + DRNC-->>SRNC: CC {a1=y, a2=x, RNSAP message or no user data} + Note right of DRNC: OR + DRNC-->>SRNC: CREF {a2=x, RNSAP message or no user data} + +``` + +Sequence diagram showing the setting-up of an SCCP Signalling Connection between an SRNC and a DRNC. The SRNC sends a CR message to the DRNC. The DRNC responds with either a CC message or a CREF message. A legend defines the parameters: a1 is source local reference, a2 is destination local reference, x is SCCP connection reference at the SRNC, and y is SCCP connection reference at the DRNC. + +**Figure 1: Setting-up of SCCP Signalling Connection** + +#### 4.5.1.3A Establishment procedure initiated from an RNC requesting common measurements or information + +The SCCP signalling connection establishment is initiated, by an RNC, when the RNC needs to request common measurements or provision of information from another RNC and there is no signalling bearer existing for this purpose. For the description below, the RNC requesting the measurements or the information is called RNC1 and the RNC being requested to provide the measurements or the information is called RNC2. + +##### Initiation + +- The RNC1 sends the SCCP: CR message to the RNC2. The COMMON MEASUREMENT INITIATION REQUEST or the INFORMATION EXCHANGE INITIATION REQUEST message shall be included in the user data field of the SCCP Connection Request message. + +##### Termination + +1. Successful outcome: + - The SCCP Connection Confirm message, which may optionally contain a connection oriented RNSAP message in the user data field, is returned to the RNC1. +2. Unsuccessful outcome: + - If the SCCP signalling connection establishment fails, an SCCP Connection Refusal message will be sent back to the RNC1. This message may optionally contain a connection oriented RNSAP message. + +RNSAP Common Measurement Initiation and Information Exchange Initiation procedures are described in TS 25.423 [5]. + +![Sequence diagram showing the setting-up of an SCCP Signalling Connection between RNC1 and RNC2. RNC1 sends a CR message to RNC2. RNC2 responds with either a CC message or a CREF message. A legend defines the variables: a1 (source local reference), a2 (destination local reference), x (SCCP connection reference at the SRNC), and y (SCCP connection reference at the DRNC).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant RNC1 + participant RNC2 + Note right of RNC1: a1 = source local reference, +a2 = destination local reference +x = SCCP connection reference at the SRNC, +y = SCCP connection reference at the DRNC. + RNC1->>RNC2: CR {SSN=RNSAP, a1=x, RNSAP message } + RNC2-->>RNC1: CC {a1=y, a2=x, RNSAP message or no user data} + Note over RNC1, RNC2: OR + RNC2-->>RNC1: CREF {a2=x, RNSAP message or no user data} + +``` + +Sequence diagram showing the setting-up of an SCCP Signalling Connection between RNC1 and RNC2. RNC1 sends a CR message to RNC2. RNC2 responds with either a CC message or a CREF message. A legend defines the variables: a1 (source local reference), a2 (destination local reference), x (SCCP connection reference at the SRNC), and y (SCCP connection reference at the DRNC). + +**Figure 1a: Setting-up of SCCP Signalling Connection** + +#### 4.5.1.4 SCCP connection release + +An SCCP connection related to a specific UE is released in all normal release cases when the RNC which established the SCCP connection realises that a given signalling connection is no longer required. + +The RNC which established SCCP connection sends an SCCP Released message. + +The procedure may be initiated at the SRNC side and the DRNC side in any abnormal release case. + +An SCCP connection used for common measurements and information exchanges is released in all normal release cases when the RNC1 (see 4.5.1.3A) determines that a given signalling connection is no longer required. The RNC1 sends an SCCP Released message. + +In case an SCCP Release message is received after the successful completion of an SRNC Relocation procedure while dedicated resources are still allocated the new SRNC shall only release the SCCP connection and the Iur related dedicated resource. + +The procedure may be initiated at the RNC 1 side and the RNC 2 side in any abnormal release case. + +#### 4.5.1.5 General SCCP Abnormal Conditions + +##### 4.5.1.5.1 SCCP bearer failure + +If a user-out-of-service information or signalling-point-inaccessible information is received by the RNSAP, no new attempt to establish SCCP connections or to send SCCP Connectionless messages towards the affected signalling point (indicated by the affected signalling point code) will be started until the corresponding user-in-service information or signalling-point-accessible information is received. + +When a user-out-of-service information or signalling-point-inaccessible is received by an RNC, an optional timer may be started. When the timer expires, the RNC shall take actions as described in TS 25.423 [5] Annex D.1.1. When the user-in-service or signalling-point-accessible is received, the timer is stopped. + +##### 4.5.1.5.2 SCCP connection failure + +If for any reason an SCCP connection is released, the optional timer expires or a connection refusal is received while any of the RNSAP procedures are being performed or while a dedicated resource is still allocated, this shall be handled by the RNC as described in TS 25.423 [5] Annex D.1.2. + +### 4.5.2 SCCP Addressing Scheme + +#### 4.5.2.1 General + +RNSAP may use SSN, SPC and/or GT and any combination of them as addressing schemes for the SCCP. Which of the available addressing schemes to use for the SCCP is an operator matter. + +When GT addressing is utilised, the following settings shall be used: + +- SSN Indicator = 1 (RNSAP SSN as defined in TS 23.003 [13] shall always be included); +- Global Title Indicator = 0100 (GT includes translation type, numbering plan, encoding scheme and nature of address indicator); +- Translation Type = 0000 0000 (not used); +- Numbering Plan = 0001 (E.163/4); +- Nature of Address Indicator = 000 0100 (International Significant Number); +- Encoding Scheme = 0001 or 0010 (BCD, odd or even); +- Routing indicator = 0 or 1 (route on GT or PC/SSN). + +When used, the GT shall be the E.164 address of the relevant node. + +# --- 5 Functions of the Iur Interface Protocols + +## 5.1 Functional List + +The list of functions on the Iur interface is the following: + +1. Transport Network Management. +2. Traffic management of Common Transport Channels: + - Preparation of Common Transport Channel resources; + - Paging. +3. Traffic Management of Dedicated Transport Channels: + - Radio Link Setup/ Addition/ Deletion; + - Measurement Reporting. +4. [TDD - Traffic Management of Downlink Shared Transport Channels and Uplink Shared Transport Channels]: + - Radio Link Setup/ Addition/ Deletion; + - Capacity Allocation. +5. Measurement reporting for common and dedicated measurement objects. +6. Information exchange of UTRAN, GERAN and MBMS bearer service information. +7. Tracing of various events related to a UE. +8. MBMS related functions + - MBMS UE Linking/De-linking + - MBMS URA linking/De-linking + +- MBMS Channel type Indication +- MBSFN MCCH Information Control + +## 5.2 Functional Split over Iur + +### 5.2.1 Combining/Splitting + +DRNS may perform combining/splitting of data streams communicated via its cells. SRNS performs combining/splitting of Iur data streams received from/sent to DRNS(s), and data streams communicated via its own cells. + +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)]. + +The internal DRNS handling of combining (respectively splitting) of Iub (respectively Iur) DCH frames is controlled by the DRNS. + +### 5.2.2 Control of Combining/Splitting Topology + +When requesting the addition of a new cell for a UE-UTRAN connection for DCH, the RNC of the SRNS (i.e. the SRNC) can explicitly request to the RNC of the DRNS (i.e. the DRNC) a new Iur data stream, in which case the combining and splitting function within the DRNS is not used for that cell. The SRNC can also explicitly request from the DRNC the use of the combining and splitting function inside the DRNS for that cell. Otherwise, the DRNS takes the decision whether combining and splitting function is used inside the DRNS for that cell i.e. whether a new Iur data stream shall be added or not. + +For E-DCH combining at the DRNC is not allowed. However, combining in NodeB of the DRNS is mandatory where applicable as described in TS 25.319 [19]. + +### 5.2.3 Handling of DRNS Hardware Resources + +Allocation and control of DRNS hardware resources, used for Iur data streams and radio interface transmission/reception in DRNS is performed by DRNS. + +### 5.2.4 Allocation of Physical Channels + +Allocation of physical channels in cells belonging to DRNS is performed in DRNS. + +### 5.2.5 UpLink Power Control + +This group of functions controls the level of the uplink transmitted power in order to minimise uplink interference and keep the quality of the connections. If the connection involves both a SRNS and a DRNS the function UL Outer Loop Power Control (located in the SRNC) sets the target quality for the UL Inner Loop Power Control function (located in Node B for DCH [FDD]). For E-DCH, the DRNS (NodeB) reports the number of HARQ retransmissions to SRNC as an input to the Outer Loop Power Control function. + +### 5.2.6 Down-Link Power Control + +This group of functions controls the level of the downlink transmitted power. In FDD it is also used to correct the downlink power drifting between several radio links. SRNC regularly (or under some algorithms) sends the target down link power reference based on the measurement report from UE. + +### 5.2.7 Admission Control + +Admission control in a DRNC is implicitly invoked during radio link setup/modify. + +Information on UL interference and DL power on cells controlled by the DRNC should be available across Iur. + +Additional information exchanges between admission control functions located in different RNCs are for further study. + +### 5.2.8 Radio Protocol Functional Split + +Iur supports the radio protocol functional split between SRNC and DRNC. + +### 5.2.9 MBMS Bearer Type Control + +MBMS Bearer type control is split between SRNC and DRNC. The CRNC is in control of an MBMS Bearer of PTM type. The MBMS bearer services activated by the UE are transferred over Iur from SRNC to DRNC. In case the CRNC is a DRNC for one or several UEs, it indicates the selected bearer type to SRNC but it is SRNC decision to set up or release MBMS bearers of PTP type for a given UE as described in TS 25.346 [18]. + +### 5.2.10 MBSFN MCCH Information Control + +In case MRNC is used, 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 and schedule information to be used. The CRNC performs the MCCH configuration and sends the MCCH information accordingly. + +# --- 6 Iur Interface Protocols + +## 6.1 General + +There shall exist a clear separation between the Radio Network Layer and the Transport Layer. Therefore, the radio network signalling and Iur data streams are separated from the data transport resource and traffic handling as shown in Figure 2. Data transport resource and traffic handling is controlled by Transport Signalling. The Transport Signalling is carried by a Signalling Bearer over the Iur interface. + +![Diagram illustrating the separation of Radio Network Protocols and transport over Iur. The diagram shows two layers: Radio Network layer and Transport layer. The Radio Network layer contains two protocols: Radio Signalling Protocols and User Plane Framing Protocols. The Transport layer contains a Signalling Bearer, Transport Signalling, and Data Transport. Arrows show the flow: Radio Signalling Protocols to Signalling Bearer, User Plane Framing Protocols to Data Transport, and Transport Signalling controlling both the Signalling Bearer and Data Transport.](64fd8bd804acee34ea91bdde28997fe3_img.jpg) + +``` +graph TD + subgraph RNL [Radio Network layer] + RSP((Radio Signalling Protocols)) + UPFP((User Plane Framing Protocols)) + end + subgraph TL [Transport layer] + SB[Signalling Bearer] + TS[Transport Signalling] + DT[Data Transport] + end + RSP --> SB + UPFP --> DT + TS --> SB + TS --> DT +``` + +Diagram illustrating the separation of Radio Network Protocols and transport over Iur. The diagram shows two layers: Radio Network layer and Transport layer. The Radio Network layer contains two protocols: Radio Signalling Protocols and User Plane Framing Protocols. The Transport layer contains a Signalling Bearer, Transport Signalling, and Data Transport. Arrows show the flow: Radio Signalling Protocols to Signalling Bearer, User Plane Framing Protocols to Data Transport, and Transport Signalling controlling both the Signalling Bearer and Data Transport. + +**Figure 2: Separation of Radio Network Protocols and transport over Iur** + +## 6.2 Radio Signalling Protocols + +### 6.2.1 RNSAP Protocol + +The protocol responsible for providing signalling information across the Iur interface is called the Radio Network Subsystem Application Part (RNSAP). A subset of RNSAP is used over the Iur-g interface. + +The RNSAP is terminated by the two RNCs inter-connected via the Iur interface RNSAP Procedure Modules. In addition, the RNSAP is terminated by a RNC and a BSS supporting Iu mode inter-connected via the Iur-g interface (TR 43.930 [17]). For 1.28Mcps TDD, the RNSAP may be terminated by a RNC and a BSS supporting A/Gb mode inter-connected via the Iur-g interface. + +RNSAP procedures are divided into four 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 as well as to handle mobility in case of UTRAN/GERAN interworking. + +The Dedicated Procedures module contains procedures that are used to handle DCHs, [FDD – F-DPCH,] E-DCH, [TDD – DSCH, USCHs] and HS-DSCH between two RNSs. If procedures from this module are not used in a specific Iur, then the usage of DCH, [FDD – F-DPCH,] E-DCH, [TDD – DSCH, USCH] and HS-DSCH 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, E-DCH 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. The procedures in this module are also used in cases involving one RNC and one BSS. + +The MBMS Procedures module contains procedures that are specific to MBMS and used for cases that cannot be handled by other modules. + +## 6.3 User Plane Frame Protocols + +### 6.3.1 Iub/Iur DCH Frame Protocol + +There are two types of Iub/Iur DCH FP frames: + +- DCH data frame; +- DCH control frame. + +The contents of the Iub/Iur DCH data frame include: + +- Transport Block Sets; +- Quality estimate. + +The contents of the Iur DCH control frame include: + +- Measurement reports; +- Power control information; + +- Synchronisation information. + +For a more detailed description of the Iur/Iub DCH frame protocol refer to 'UTRAN Iur & Iub Interface User Plane Protocol for DCH Data Streams' TS 25.427 [1]. + +### 6.3.2 Iur DSCH Frame Protocol [TDD] + +There are two types of Iur DSCH FP frames: + +- DSCH data frame; +- DSCH control frames. + +The contents of the Iur DSCH data frame include: + +- MAC-c/sh SDUs; +- User Buffer Status. + +The contents of the Iur DSCH control frame include: + +- Flow control Information (UL); +- Capacity Request Information (DL). + +For a more detailed description of the Iur DSCH frame protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.3 Iur USCH Frame Protocol [TDD] + +There is one type of Iur USCH FP frames: + +- USCH data frame. + +The contents of the Iur USCH data frame include: + +- MAC-c/sh SDUs. + +For a more detailed description of the Iur USCH frame protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.4 Iur RACH Frame Protocol + +For a more detailed description of the Iur RACH framing protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.5 Iur FACH Frame Protocol + +For a more detailed description of the Iur FACH framing protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.6 Iur HS-DSCH Frame Protocol + +There are two types of Iur HS-DSCH FP frames: + +- HS-DSCH data frame; +- HS-DSCH control frames. + +The contents of the Iur HS-DSCH data frame include: + +- MAC-d PDUs; + +- User Buffer Status. + +The contents of the Iur HS-DSCH control frame include: + +- Flow control Information (UL); +- Capacity Request Information (DL). + +For a more detailed description of the Iur HS-DSCH frame protocol refer to 'UTRAN Iur Interface User Plane protocols for Common Transport Channel Data Streams' TS 25.425 [2]. + +### 6.3.7 Iur E-DCH Frame Protocol + +There is one type of Iur E-DCH FP frames: + +- E-DCH data frame; + +The contents of the Iur E-DCH data frame include: + +- Mac-es PDUs (multiplexed); +- Number of HARQ retransmissions; +- CFN and Sub frame number. + +For a more detailed description of the Iur E-DCH frame protocol refer to 'UTRAN Iur Interface User Plane Protocols for DCH Data Streams' TS 25.427 [1]. + +## 6.4 Mapping of Frame Protocols onto transport bearers + +| | | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DCH | One Iur DCH data stream is carried on one transport bearer except in the case of co-ordinated DCHs in which case a set of co-ordinated DCHs are multiplexed onto the same transport bearer. | +| [TDD - DSCH | One Iur DSCH data stream is carried on one transport bearer.] | +| HS-DSCH | One Iur HS-DSCH data stream is carried on one transport bearer. | +| E-DCH | One Iur E-DCH data stream is carried on one transport bearer. For each E-DCH data stream, a transport bearer must be established over the Iur interface. | +| [TDD - USCH | One Iur USCH data stream is carried on one transport bearer.] | +| RACH | Multiple RACH data streams may be carried on one transport bearer. | +| FACH | Multiple FACH data streams may be carried on one transport bearer. | + +RACH and FACH data streams for one UE are carried on same transport bearer. + +# --- 7 DRNS logical Model over Iur + +## 7.1 Overview + +The model in Figure 3 shows the Drift Radio Network System as seen from the SRNC. It is modelled as a «black box» with a set of Radio Links on the Uu side of the box and another set of User Plane access ports on the Iur side of the box. The Radio Links are connected to the Iur user ports via the internal transport mechanisms of the DRNS. Operations for controlling the connections between ports are sent from the SRNC to the DRNC via an Iur Control Plane port. + +![Figure 3: Drift RNS Logical Model diagram showing the architecture of a Drift Radio Network System (DRNS) connected to a Serving Radio Network System (SRNS).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates the logical model of a Drift Radio Network System (DRNS). At the top, a large rectangle represents the **Serving Radio Network System** (SRNS). Below it, the **Drift Radio Network System** (DRNS) is shown. The DRNS contains two **Cell** boxes, each enclosing three **Radio Link** circles. These Radio Links are connected to various **Iur Data Ports** located between the SRNS and the DRNS. The Iur Data Ports are of several types: **Iur Control Port**, **Iur DCH Data Port**, **Iur E-DCH Data Port**, **Iur TDD DSCH Data Port**, **Iur HS-DSCH Data Port**, and **Iur RACH/FACH Data Port**. A box labeled **RACH/FACH Traffic Contexts With attributes** is connected to the Iur RACH/FACH Data Ports. The bottom of the diagram is labeled **Radio User Plane**, indicating the flow of user data through the Radio Links. + +Figure 3: Drift RNS Logical Model diagram showing the architecture of a Drift Radio Network System (DRNS) connected to a Serving Radio Network System (SRNS). + +Figure 3: Drift RNS Logical Model + +## 7.2 Logical Model Elements + +### 7.2.1 Radio Link + +A Radio Link represents a User Plane access point on the UTRAN side of the Uu interface between the User Equipment and the UTRAN. + +The semantics of a Radio Link include the following: + +- It is created, destroyed, and added by SRNC. +- It can be attached to one or more Iur Data Ports at any given time. +- Its resources are allocated and controlled by the DRNS. + +### 7.2.2 Cell + +It is defined by: + +- A Cell identifier. + +The semantics of a Cell include the following: + +- It is created and destroyed by administrative procedures. + +### 7.2.3 Iur DCH Data Port + +One Iur DCH Data port represents one user plane transport bearer. One user plane transport bearer will carry only one DCH data stream except in the case of co-ordinated DCHs, in which case the data streams of all co-ordinated DCHs shall be multiplexed on one and the same user plane transport bearer. + +The semantics of an Iur DCH Data Port include the following: + +- It is created and destroyed by administrative procedures when transport facilities are added to, or deleted from, the Iur interface between the SRNS and DRNS. It can also be created and destroyed dynamically using dynamically setup transport bearers to add or remove transport facilities. + +- It is assigned and released by the SRNC in reaction to requests for bearer services from the UE. +- It may be attached to one or more Radio Links. When attached to Radio Links in the downlink direction, it acts as a point-to-multipoint connection for diversity transmission. When attached to multiple Radio Links in the uplink direction, it acts as a multipoint-to-point connection for diversity reception [FDD]. +- The transmit and receive combining/splitting resources required to implement the point-to-multipoint and multipoint-to-point connections are controlled by the DRNS [FDD]. +- The Iur DCH Data Stream emanating from the Iur DCH Data Port terminates in the SRNS connected to DRNS. + +### 7.2.4 Iur DSCH Data Port [TDD] + +One Iur DSCH Data port represents one bi-directional Iur user plane transport bearer. One Iur user plane transport bearer will carry only one DSCH data stream. + +### 7.2.5 Iur USCH Data Port [TDD] + +One Iur USCH Data port represents one Iur user plane transport bearer. One Iur user plane transport bearer will carry only one USCH data stream. + +### 7.2.6 Iur RACH/FACH Data Port + +The Iur RACH/FACH data port represents a transport bearer and is identified with a transport bearer identity. + +### 7.2.7 Iur Control Port + +An Iur Control Port represents the Control Plane access point on the Iur interface between the SRNS and the DRNS. It is defined by: + +- A transport bearer channel identifier. + +The semantics of an Iur Control Port include the following: + +- It is created via administrative procedures when the Iur interface is created. + +### 7.2.8 Iur HS-DSCH Data Port + +One Iur HS-DSCH Data port represents one bi-directional Iur user plane transport bearer. One Iur user plane transport bearer will carry only one HS-DSCH data stream. + +### 7.2.9 Iur E-DCH Data Port + +One Iur E-DCH Data port represents one bi-directional Iur user plane transport bearer. One Iur user plane transport bearer will carry only one E-DCH data stream. It is assigned and released by the SRNC in reaction to requests for bearer services from the UE. [FDD - It may be attached to one or more Radio Links. When attached to multiple Radio Links in the uplink direction, the receive combining resources required to implement the multipoint-to-point connections is in the NodeB of the DRNS.] + +# --- 8 Iur Interface Protocol Structure + +The Iur interface protocol architecture consists of two functional layers: + +- Radio Network Layer, defines the procedures related to the interaction of two RNCs within a PLMN. The radio network layer consists of a Radio Network Control Plane and a Radio Network User Plane. +- Transport layer, defines procedures for establishing physical connections between two RNCs within a PLMN. + +![Figure 4: Iur Interface Protocol Structure. This diagram illustrates the protocol stack for the Iur interface between two Radio Network Controllers (RNCs). The stack is divided into three vertical sections: Control Plane, User Plane, and Transport Network Control Plane. The Control Plane on the left shows RNSAP at the top, connected to the Transport Network User Plane, which in turn connects to SCCP. SCCP is supported by MTP3-B, M3UA, and M3UA. Below MTP3-B are SSCF-NNI, SCTP, and SCTP. Below SSCF-NNI are SSCOP, IP, and IP. Below IP is AAL5, which is supported by ATM. The ATM layer is connected to the Physical Layer. The User Plane on the right shows Iur Data Stream(s) at the top, connected to the Transport Network User Plane, which connects to AAL2 and UDP/IP. Below AAL2 and UDP/IP is ATM, which is connected to the Physical Layer. The Transport Network Control Plane in the center shows Q.2630.2 at the top, connected to STC (Q.2150.1). STC (Q.2150.1) is supported by MTP3-B, M3UA, and M3UA. Below MTP3-B are SSCF-NNI, SCTP, and SCTP. Below SSCF-NNI are SSCOP, IP, and IP. Below IP is AAL5, which is supported by ATM. The ATM layer is connected to the Physical Layer. All three planes share a common Physical Layer at the bottom.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 4: Iur Interface Protocol Structure. This diagram illustrates the protocol stack for the Iur interface between two Radio Network Controllers (RNCs). The stack is divided into three vertical sections: Control Plane, User Plane, and Transport Network Control Plane. The Control Plane on the left shows RNSAP at the top, connected to the Transport Network User Plane, which in turn connects to SCCP. SCCP is supported by MTP3-B, M3UA, and M3UA. Below MTP3-B are SSCF-NNI, SCTP, and SCTP. Below SSCF-NNI are SSCOP, IP, and IP. Below IP is AAL5, which is supported by ATM. The ATM layer is connected to the Physical Layer. The User Plane on the right shows Iur Data Stream(s) at the top, connected to the Transport Network User Plane, which connects to AAL2 and UDP/IP. Below AAL2 and UDP/IP is ATM, which is connected to the Physical Layer. The Transport Network Control Plane in the center shows Q.2630.2 at the top, connected to STC (Q.2150.1). STC (Q.2150.1) is supported by MTP3-B, M3UA, and M3UA. Below MTP3-B are SSCF-NNI, SCTP, and SCTP. Below SSCF-NNI are SSCOP, IP, and IP. Below IP is AAL5, which is supported by ATM. The ATM layer is connected to the Physical Layer. All three planes share a common Physical Layer at the bottom. + +Figure 4: Iur Interface Protocol Structure + +# 9 Other Iur Interface Specifications + +## 9.1 UTRAN Iur Interface: Layer 1 (TS 25.421) + +TS 25.421 [3] specifies the range of physical layer technologies that may be used to support the Iur interface and the Iur-g interface. + +## 9.2 UTRAN Iur Interface: Signalling Transport (TS 25.422) + +TS 25.422 [4] specifies the signalling bearers for the RNSAP for Iur Interface and for Iur-g interface. + +## 9.3 UTRAN Iur Interface: RNSAP Specification (TS 25.423) + +TS 25.423 [5] specifies the RNSAP protocol for radio network control plane signalling over the Iur interface and over the Iur-g interface. + +## 9.4 UTRAN Iur Interface: Data Transport and Transport Signalling for Common Transport Channel Data Streams (TS 25.424) + +TS 25.424 [6] specifies the transport bearers for the user plane of the Iur interface. It also specifies the ALCAP protocol used to control these transport bearers. + +## 9.5 UTRAN Iur Interface: User Plane Protocols for Common Transport Channel Data Streams (TS 25.425) + +TS 25.425 [2] specifies the user plane frame handling protocol for the common channels on Iur interface. + +## 9.6 UTRAN Iur & Iub Interface: Data Transport and Transport Signalling for DCH Data Streams (TS 25.426) + +TS 25.426 [8] specifies the transport bearers for the user plane of the Iub/Iur interface. It also specifies the ALCAP protocol used to control these transport bearers. + +## 9.7 UTRAN Iur & Iub Interface: User Plane Protocols for DCH Data Streams (TS 25.427) + +TS 25.427 [1] specifies the user plane frame handling protocol for the dedicated channels on Iub/Iur interface. + +## 9.8 Summary of UTRAN Iur Interface Technical Specifications + +The relationship between the technical specifications that define the UTRAN Iur interface is shown in Figure 5. + +![Figure 5: Iur Interface Technical Specifications diagram showing the relationship between Radio Network Control Plane, Transport Network Control Plane, and User Plane across Radio Network Layer and Transport Layer.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +| | Radio Network Control Plane | Transport Network Control Plane | User Plane | | +|---------------------|-----------------------------------|----------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-------------------------------------------| +| Radio Network Layer | RNSAP
TS 25.423 | | Dedicated Channels
TS 25.427 | Common Channels
TS 25.425 | +| Transport Layer | Signalling Transport
TS 25.422 | Transport Signaling

TS 25.426
(Dedicated Channel Transport)

TS 25.424
(Common Channel Transport) | Dedicated Channel Transport

TS 25.426 | Common Channel Transport

TS 25.424 | +| | | Physical Layer TS 25.421 | | | + +Figure 5: Iur Interface Technical Specifications diagram showing the relationship between Radio Network Control Plane, Transport Network Control Plane, and User Plane across Radio Network Layer and Transport Layer. + +Figure 5: Iur Interface Technical Specifications + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|----------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Rel-8 version created based on v7.3.0 | 8.0.0 | +| 42 | RP-080849 | 0059 | - | Enable to dynamically control the MBMS services in MBSFN | 8.0.0 | +| 43 | RP-090078 | 0060 | 1 | RNSAP: Enhanced Relocation Request in SCCP: Connection Request | 8.1.0 | +| 12/2009 | - | - | - | Created Rel-9 version based on v8.1.0 | 9.0.0 | +| 49 | RP-100909 | 0061 | - | CS Data forwarding support for Iur interface | 9.1.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.1.1 | +| 03/2011 | | | | Created Rel-10 version based on v9.1.1 | 10.0.0 | +| 06/2011 | RP-110684 | 0063 | - | Correction of references | 10.1.0 | +| 06/2011 | RP-110694 | 0064 | 2 | Introduction of Enhancements of Iur-g Interface | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-03 | SA#95-e | | | | | Promotion to Release 17 without technical change | 17.0.0 | +| 2024-03 | SA#103- | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/25_series/25421/raw.md b/marked/Rel-18/25_series/25421/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8faba6eb9356e7d436d51665a554e5598bf25561 --- /dev/null +++ b/marked/Rel-18/25_series/25421/raw.md @@ -0,0 +1,118 @@ + + +# 3GPP TS 25.421 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iur interface layer 1 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|---------------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.3 Abbreviations ..... | 5 | +| 4 Iur Layer 1..... | 5 | +| Annex A (informative): Change history..... | 6 | + +# --- 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 standards allowed to implement Layer 1 on the Iur interface. The specification of transmission delay requirements and O&M requirements are not in the scope of this document. + +In the following 'Layer 1' and 'Physical Layer' are assumed to be synonymous. + +# --- 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.411: "UTRAN Iu interface Layer 1". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 25.411 [1] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TS 25.411 [1] apply. + +# --- 4 Iur Layer 1 + +The Iur Layer 1 shall comply with the requirements of chapter 4 in TS 25.411 [1]. \ No newline at end of file diff --git a/marked/Rel-18/25_series/25426/raw.md b/marked/Rel-18/25_series/25426/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..51633858d364848a96b6b69879f7019243eddcc1 --- /dev/null +++ b/marked/Rel-18/25_series/25426/raw.md @@ -0,0 +1,380 @@ + + +# 3GPP TS 25.426 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iur and Iub interface data transport & transport signalling for DCH data streams (Release 18)** + +![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G ADVANCED logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Data Link Layer ..... | 7 | +| 4.1 ATM Transport Option ..... | 7 | +| 4.1.1 Protection Switching at ATM Layer ..... | 7 | +| 4.2 IP Transport Option..... | 7 | +| 5 Iur and Iub Data Transport for DCH and E-DCH Data Streams ..... | 8 | +| 5.1 Introduction ..... | 8 | +| 5.2 ATM Transport Option ..... | 8 | +| 5.3 IP Transport Option..... | 8 | +| 6 Transport Signalling Application for DCH and E-DCH Data Streams ..... | 9 | +| 6.1 Introduction ..... | 9 | +| 6.2 ALCAP in ATM Transport Option ..... | 9 | +| 6.3 ALCAP in IP Transport Option ..... | 9 | +| 7 Signalling Bearer for ALCAP on Iub Interface ..... | 9 | +| 7.1 Introduction ..... | 9 | +| 7.2 Signalling Bearer in ATM Transport Option ..... | 10 | +| 7.3 Signalling Bearer in IP Transport Option ..... | 10 | +| 8 Signalling Bearer for ALCAP on Iur Interface..... | 10 | +| 8.1 Introduction ..... | 10 | +| 8.2 Signalling Bearer in ATM Transport Option ..... | 11 | +| 8.3 Signalling Bearer in IP Transport Option ..... | 11 | +| 9 Interworking between ATM and IP Transport Options..... | 11 | +| 9.1 Introduction ..... | 11 | +| 9.2 Interworking Alternatives ..... | 11 | +| Annex A (informative): Change history..... | 13 | + +# --- 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 transport bearers for the DCH/E-DCH data streams on UTRAN Iur and Iub interfaces. The corresponding Transport Network Control plane is also specified. The physical layer for the transport bearers is outside the scope of the present document. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.427: "UTRAN Iub/Iur interface user plane protocol for DCH data streams". +- [2] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification". +- [3] ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation Layer specification; Type 2 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 Q.2630.1 (1999-12): "AAL type 2 signalling protocol (Capability Set 1)". +- [6] ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing". +- [7] ITU-T Recommendation X.213 (1995-11): "Information Technology - Open Systems Interconnection - Systems Interconnection - Network Service Definition". +- [8] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)". +- [9] ITU-T Recommendation Q.2130 (1994-07): "B-ISDN signalling ATM adaptation layer - Service Specific Coordination Function for Support of Signalling at the User-Network Interface (SSCF at UNI)". +- [10] ITU-T Recommendation Q.2150.2 (1999-12): "AAL type 2 signalling transport converter on SSCOP". +- [11] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of the ITU-T Recommendation Q.2140". +- [12] 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 at NNI)". +- [13] ITU-T Recommendation Q.2150.1 (1999-12): "AAL type 2 signalling transport converter on broadband MTP". +- [14] IETF RFC 791 (1981-09): "Internet Protocol". +- [15] IETF RFC 1483 (1993-07): "Multiprotocol Encapsulation over ATM Adaptation Layer 5". +- [16] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM". + +- [17] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [18] IETF RFC 2960 (2000-10): "Stream Control Transmission Protocol". +- [19] IETF RFC 3332(2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)". +- [20] ITU-T Recommendation I.630 (1999-02): "ATM protection switching". +- [21] ITU-T Recommendation Q.Imp2210 (1996-07): "Implementor's guide (03/99) for Recommendation Q.2210 (07/96)". +- [22] ITU-T Recommendation Q.2630.2 (2000-12): "AAL type 2 signalling protocol (Capability Set 2)". +- [23] IETF RFC 1661 (1994-07): "The Point-To-Point Protocol (PPP)". +- [24] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing". +- [25] IETF RFC 2507 (1999-02): "IP header compression". +- [26] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)". +- [27] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP". +- [28] IETF RFC 2509 (1999-02): "IP Header Compression over PPP". +- [29] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification". +- [30] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [31] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [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] Void +- [36] ITU-T Recommendation E.164 (1997-05): "The international public telecommunication numbering plan ". +- [37] IETF RFC 3309 (2002-09): "SCTP Checksum Change". +- [38] 3GPP TS 25.414: "UTRAN Iu Interface data transport & transport signalling". +- [39] 3GPP TS 25.401: "UTRAN overall description". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following term and definition applies: + +**ALCAP:** transport signalling protocol used to setup and tear down transport bearers + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +AAL2                    ATM Adaptation Layer type 2 + +| | | +|---------|-------------------------------------------------------| +| AESA | ATM End System Address | +| ATM | Asynchronous Transfer Mode | +| CPCS | Common Part Convergence Sublayer | +| CPS | Common Part Sublayer | +| DCH | Dedicated Channel | +| E-DCH | Enhanced DCH | +| HDLC | High level Data Link Control | +| HS-DSCH | High Speed Downlink Shared Channel | +| IP | Internet Protocol | +| LC | Link Characteristics | +| M3UA | SS7 MTP3 User Adaptation layer | +| ML/MC | Multi-link / Multi-class | +| MPLS | Multiprotocol Label Switching | +| MTP | Message Transfer Part | +| NNI | Network-Node Interface | +| NSAP | Network Service Access Point | +| PPP | Point to Point Protocol | +| PT | Path Type | +| SAAL | Signalling ATM Adaptation Layer | +| SAR | Segmentation and Reassembly | +| SCTP | Stream Control Transmission Protocol | +| SSCF | Service Specific Co-ordination Function | +| SSCP | Service Specific Connection Oriented Protocol | +| SSCS | Service Specific Convergence Sublayer | +| SSSAR | Service Specific Segmentation and Reassembly sublayer | +| STC | Signalling Transport Converter | +| UDP | User Datagram Protocol | +| UNI | User-Network Interface | + +# --- 4 Data Link Layer + +## 4.1 ATM Transport Option + +ATM shall be used in the transport network user plane and transport network control plane according to ITU-T Rec. I.361 [2]. + +### 4.1.1 Protection Switching at ATM Layer + +If redundancy of pathways at ATM Layer between RNC and Node B is supported, it shall be implemented using ATM Protection Switching according to ITU-T Rec. I.630 [20]. + +## 4.2 IP Transport Option + +A UTRAN node supporting IP transport option shall support PPP protocol IETF RFC 1661 [23] with HDLC framing (IETF RFC 1662 [24]). + +NOTE: This does not preclude the single implementation and use of any other L2/L1 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 towards the upper layers. + +A UTRAN node supporting IP transport option and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [25]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [26], IETF RFC 2686 [27]). In this case the negotiation of header compression (ITU-T Rec. I.630 [20]) over PPP shall be performed via IETF RFC 2509 [28]. + +# 5 Iur and Iub Data Transport for DCH and E-DCH Data Streams + +## 5.1 Introduction + +The Frame Protocol for DCH and E-DCH data streams (TS 25.427 [1]) is the user of the transport layer specified in the present document. + +There are two options for the transport layer of the DCH and E-DCH data streams in Iur and Iub: + +- 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. + +![Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces. The diagram shows two protocol stacks. The left stack is for the ATM transport option, showing layers from top to bottom: Radio Network Layer, AAL2 SSSAR (I.366.1), AAL2 CPS (I.363.2), ATM, and Physical layer. The right stack is for the IP transport option, showing layers from top to bottom: Radio Network Layer, UDP (RFC768), IPv6 (RFC2460) with IPv4 optional (RFC791), Data link layer, and Physical layer. Both stacks are labeled with 'Transport Network Layer' on the left side.](731f533b0599c8e42a063f06e4332045_img.jpg) + +Protocol stack for ATM transport option +Protocol stack for IP transport option + +Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces. The diagram shows two protocol stacks. The left stack is for the ATM transport option, showing layers from top to bottom: Radio Network Layer, AAL2 SSSAR (I.366.1), AAL2 CPS (I.363.2), ATM, and Physical layer. The right stack is for the IP transport option, showing layers from top to bottom: Radio Network Layer, UDP (RFC768), IPv6 (RFC2460) with IPv4 optional (RFC791), Data link layer, and Physical layer. Both stacks are labeled with 'Transport Network Layer' on the left side. + +**Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces** + +## 5.2 ATM Transport Option + +Asynchronous Transfer Mode (ATM) (ITU-T Rec. I.361 [2]) and ATM Adaptation Layer type 2 (AAL2) (ITU-T Rec. I.363.2 [3], ITU-T Rec. I.366.1 [4]) are used as a transport layer for DCH and E-DCH data streams on Iur and Iub interfaces. Service Specific Segmentation and Reassembly (SSSAR) sublayer for AAL2 is used for the segmentation and reassembly of AAL2 SDUs. + +## 5.3 IP Transport Option + +UDP (IETF RFC 768 [17]) over IP shall be supported as the transport for DCH and E-DCH data streams on Iub and Iur interfaces. The data link layer is as specified in chapter 4.2. + +An IP UTRAN Node shall support IPv6 (IETF RFC 2460[29]). The support of IPv4 (IETF RFC 791[14]) 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. + +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 Radio Network Layer on the Iur/Iub interface shall use the NSAP structure. See sub clause 6.1.8.2 of TS 25.401 [39]. + +IP Differentiated Services code point marking (IETF RFC 2474 [30]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M. Traffic categories are implementation-specific and may be determined from the application parameters. + +# 6 Transport Signalling Application for DCH and E-DCH Data Streams + +## 6.1 Introduction + +This chapter specifies the ALCAP protocol(s) to be used in Iur and Iub interfaces for DCH data streams. + +## 6.2 ALCAP in ATM Transport Option + +AAL2 signalling protocol Capability Set 2 (ITU-T Rec. Q.2630.2 [22]) is the signalling protocol to control AAL2 connections on Iub and Iur interfaces. ITU-T Rec. Q.2630.2 [22] adds new optional capabilities to ITU-T Rec. Q.2630.1 [5]. + +Binding ID provided by the radio network layer shall be copied in SUGR parameter of ESTABLISH.request primitive of ITU-T Rec. Q.2630.2 [22]. + +User Plane Transport bearers for Iur interface are established, in all normal cases released and optionally modified by the ALCAP in the Serving RNC. The binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iur interface in the Drift RNC. + +User Plane Transport bearers for Iub interface are established, in all normal cases released and optionally modified by the ALCAP in the Controlling RNC. Binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iub interface in the Node B. In case of a Reset initiated by the CRNC, the ALCAP in the Node B shall release the transport bearers involved in the impacted Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers for the removed dedicated channels that were remaining within the cell when the cell is deleted. + +AAL2 transport layer addressing is based on embedded E.164 or other AESA variants of the NSAP addressing format (ITU-T Rec. E.191 [6], ITU-T Rec. X.213 [7]). Native E.164 addressing (ITU-T Rec. E.164 [36]) shall not be used. + +The Link Characteristics parameter (LC) shall be included in the Establish Request message and in the Modification Request message of AAL2 signalling protocol. + +If there is an AAL2 switching function in the transport network layer of the interface, the Path Type parameter (PT) may be included in the Establish Request message of AAL2 signalling protocol for prioritisation at ATM level. + +If the value in either the Maximum CPS-SDU Bit Rate or the Average CPS-SDU Bit Rate of the Link Characteristics(LC) in AAL2 signalling messages as specified in reference ITU-T Rec. Q.2630.2 [22] is 2048 Kbit/s, it shall be interpreted as bit rate 2048 Kbit/s or higher. + +NOTE: Separation of traffic (e.g. HS-DSCH, E-DCH) that is using this modified interpretation of Link Characteristics in ref. ITU-T Rec. Q.2630.2 [22] from other traffic is highly recommended. Otherwise the potential bursty nature of this specific traffic in combination with its unknown bit rate may decrease the QoS of all traffic within the same AAL type 2 path. + +## 6.3 ALCAP in IP Transport Option + +An ALCAP protocol is not required in case both UTRAN nodes are using the IP transport option. + +Application of ALCAP in IP to ATM interworking case is defined in chapter 9 of this Technical Specification. + +# 7 Signalling Bearer for ALCAP on Iub Interface + +## 7.1 Introduction + +This clause specifies the signalling bearer for the ALCAP on Iub interface. + +## 7.2 Signalling Bearer in ATM Transport Option + +SAAL-UNI (ITU-T Rec. Q.2110 [8], ITU-T Rec. Q.2130 [9]) is used as the signalling bearer for the AAL Type 2 Signalling protocol on Iub interface. Signalling Transport Converter for SSCOP is applied ITU-T Rec. Q.2150.2 [10]. The following figure shows the signalling bearer protocol stack for the ALCAP on Iub interface. + +![Figure 2: Signalling bearer for ALCAP on Iub interface. The diagram shows a protocol stack with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.2). Below STC is AAL5 SSCS, which contains SSCF-UNI and SSCOP. Below AAL5 SSCS is AAL5 Common Part, which contains CPCS and SAR. Below AAL5 Common Part is ATM, and at the bottom is PHY. The entire stack from STC to PHY is enclosed in a dashed box, and a horizontal line passes through the middle of the stack.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +| | | +|---------------------|----------| +| ALCAP
(Q.2630.2) | | +| STC
(Q.2150.2) | | +| AAL5 SSCS | SSCF-UNI | +| | SSCOP | +| AAL5 Common Part | CPCS | +| | SAR | +| ATM | | +| PHY | | + +Figure 2: Signalling bearer for ALCAP on Iub interface. The diagram shows a protocol stack with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.2). Below STC is AAL5 SSCS, which contains SSCF-UNI and SSCOP. Below AAL5 SSCS is AAL5 Common Part, which contains CPCS and SAR. Below AAL5 Common Part is ATM, and at the bottom is PHY. The entire stack from STC to PHY is enclosed in a dashed box, and a horizontal line passes through the middle of the stack. + +Figure 2: Signalling bearer for ALCAP on Iub interface + +## 7.3 Signalling Bearer in IP Transport Option + +An ALCAP protocol is not required in case both UTRAN nodes are using the IP transport option. + +# --- 8 Signalling Bearer for ALCAP on Iur Interface + +## 8.1 Introduction + +This clause specifies the signalling bearer for the ALCAP on the Iur interface. + +## 8.2 Signalling Bearer in ATM Transport Option + +There are two protocol stacks specified for Iur ALCAP Signalling Bearer in ATM option - one based on MTP-3B (ITU-T Rec. Q.2210 [11], ITU-T Rec. Q.Imp2210 [21]) and SAAL-NNI (ITU-T Rec. Q.2140 [12], ITU-T Rec. Q.2110 [8]) and the other based on SCTP (IETF RFC 2960 [18]). Signalling Transport Converter for MTP-3B is applied (ITU-T Rec. Q.2150.1 [13]). MTP-3 User Adaptation Layer (M3UA) for SCTP is applied in IETF RFC 3332 [19]. Classical IP over ATM is specified in IETF RFC 2225 [16]. Multiprotocol Encapsulation over AAL5 is specified in IETF RFC 1483 [15]. The checksum method specified in IETF RFC 3309 [37] shall be used instead of the method specified in IETF RFC 2960 [18]. The following figure shows the signalling bearer protocol stacks for the ALCAP on Iur interface. + +![Figure 3: Signalling bearers for ALCAP on Iur interface. The diagram shows two protocol stacks. The left stack is for an MTP-3B based Iur ALCAP Signalling Bearer, and the right stack is for an IP based Iur ALCAP Signalling Bearer. Both stacks start with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.1). The left stack then has MTP-3B, followed by AAL5 SSCS (SSCF-NNI, SSCOP) and AAL5 Common Part (CPCS, SAR), then ATM, and finally PHY. The right stack has M3UA, SCTP, IP, AAL5, ATM, and finally PHY.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +| MTP-3B based Iur ALCAP Signalling Bearer | IP based Iur ALCAP Signalling Bearer | +|------------------------------------------|--------------------------------------| +| ALCAP (Q.2630.2) | ALCAP (Q.2630.2) | +| STC (Q.2150.1) | STC (Q.2150.1) | +| MTP-3B | M3UA | +| AAL5 SSCS (SSCF-NNI, SSCOP) | SCTP | +| AAL5 Common Part (CPCS, SAR) | IP | +| ATM | AAL5 | +| PHY | ATM | +| | PHY | + +Figure 3: Signalling bearers for ALCAP on Iur interface. The diagram shows two protocol stacks. The left stack is for an MTP-3B based Iur ALCAP Signalling Bearer, and the right stack is for an IP based Iur ALCAP Signalling Bearer. Both stacks start with ALCAP (Q.2630.2) at the top, followed by STC (Q.2150.1). The left stack then has MTP-3B, followed by AAL5 SSCS (SSCF-NNI, SSCOP) and AAL5 Common Part (CPCS, SAR), then ATM, and finally PHY. The right stack has M3UA, SCTP, IP, AAL5, ATM, and finally PHY. + +Figure 3: Signalling bearers for ALCAP on Iur interface + +## 8.3 Signalling Bearer in IP Transport Option + +An ALCAP protocol is not required in case both UTRAN nodes are using the IP transport option. + +# 9 Interworking between ATM and IP Transport Options + +## 9.1 Introduction + +This clause specifies the interworking between IP and ATM transport options. A UTRAN node supporting IP transport option shall provide interworking to a UTRAN node supporting only ATM transport option. + +## 9.2 Interworking Alternatives + +For interworking with a UTRAN node supporting only ATM option, the UTRAN node supporting IP option shall additionally support at least one of the following interworking mechanisms: + +- 1) ATM&IP dual stack. An ALCAP protocol is not required in this interworking solution. + +Annex A of TS 25.414 [38] 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 UTRAN node. AAL2 signalling protocol Capability Set 2 (ITU-T Rec. Q.2630.2 [22]) shall be supported as ALCAP protocol between the Interworking Function and the UTRAN node supporting ATM transport option. + +Annex A of TS 25.414 [38] shows an example of a protocol stack for the bearer control protocol between the RNC/CN IP Node and its IWF for the case when the IWF is an external unit to the RNC/CN node. Other protocol stacks for this case are not precluded. \ No newline at end of file diff --git a/marked/Rel-18/25_series/25427/raw.md b/marked/Rel-18/25_series/25427/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9fac3bbda433deacd4d07c31a8a49420bd3dbb5a --- /dev/null +++ b/marked/Rel-18/25_series/25427/raw.md @@ -0,0 +1,1891 @@ + + +# 3GPP TS 25.427 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub/Iur interface user plane protocol for DCH data streams (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in small black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + + + +# --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 3.3 Specification Notations ..... | 8 | +| 4 General aspects ..... | 9 | +| 4.1 DCH and E-DCH FP services ..... | 10 | +| 4.2 Services expected from the Data Transport Network layer ..... | 10 | +| 4.3 Protocol Version..... | 10 | +| 5 DCH Frame Protocol procedures ..... | 11 | +| 5.1 Data Transfer..... | 11 | +| 5.1.0 General ..... | 11 | +| 5.1.1 Uplink for DCH ..... | 11 | +| 5.1.1a Uplink for E-DCH ..... | 11 | +| 5.1.2 Downlink ..... | 12 | +| 5.2 Timing Adjustment ..... | 13 | +| 5.3 DCH Synchronisation ..... | 14 | +| 5.4 Outer Loop PC Information Transfer [FDD, 1.28 Mcps TDD] ..... | 14 | +| 5.5 Node Synchronisation ..... | 14 | +| 5.6 Rx Timing Deviation Measurement [3.84 Mcps and 7.68 Mcps TDD] ..... | 15 | +| 5.7 DSCH TFCI Signalling [FDD] ..... | 15 | +| 5.8 Radio Interface Parameter Update [FDD]..... | 15 | +| 5.9 Timing Advance [3.84 Mcps and 7.68 Mcps TDD] ..... | 16 | +| 5.10 General ..... | 16 | +| 5.10.1 Transport bearer replacement..... | 16 | +| 5.10.2 Transport channel addition..... | 17 | +| 5.11 Generation of subframe number..... | 17 | +| 5.12 Generation of number of HARQ retransmissions ..... | 17 | +| 5.13 Indication of HARQ failure..... | 18 | +| 5.14 TNL Congestion Indication..... | 19 | +| 6 Frame structure and coding..... | 19 | +| 6.1 General ..... | 19 | +| 6.1.1 General principles for the coding ..... | 20 | +| 6.2 Data frames ..... | 20 | +| 6.2.1 Introduction ..... | 20 | +| 6.2.2 UL DATA FRAME..... | 20 | +| 6.2.2.1 UL DATA FRAME FOR DCH..... | 20 | +| 6.2.2.2 UL DATA FRAME FOR E-DCH TYPE 1 ..... | 21 | +| 6.2.2.3 UL DATA FRAME FOR E-DCH TYPE 2 ..... | 23 | +| 6.2.3 DL DATA FRAME..... | 24 | +| 6.2.4 Coding of information elements in data frames ..... | 24 | +| 6.2.4.1 Header CRC..... | 24 | +| 6.2.4.2 Frame Type (FT)..... | 25 | +| 6.2.4.3 Connection Frame Number (CFN) ..... | 25 | +| 6.2.4.4 Transport Format Indicator (TFI) ..... | 25 | +| 6.2.4.5 Quality Estimate (QE) ..... | 25 | +| 6.2.4.6 Transport Block (TB)..... | 26 | +| 6.2.4.7 CRC indicator (CRCI) ..... | 26 | +| 6.2.4.8 Payload CRC..... | 26 | +| 6.2.4.9 Spare Extension ..... | 26 | +| 6.2.4.10 Subframe Number..... | 26 | + +| | | | +|------------|--------------------------------------------------------|----| +| 6.2.4.11 | Number of HARQ Retransmissions, NHR ..... | 26 | +| 6.2.4.12 | Number of Subframes ..... | 27 | +| 6.2.4.13 | Number of MAC-es PDUs..... | 27 | +| 6.2.4.14 | Data Description Indicator, DDI..... | 27 | +| 6.2.4.15 | Number of MAC-d PDUs, N ..... | 27 | +| 6.2.4.16 | FSN – Frame Sequence Number ..... | 27 | +| 6.2.4.17 | Number of MAC-is PDUs ..... | 27 | +| 6.2.4.18 | User Buffer size ..... | 27 | +| 6.2.4.19 | Number of MAC-is SDU in frame ..... | 28 | +| 6.2.4.20 | MAC-is PDU descriptor ..... | 28 | +| 6.2.4.21 | UL Multiplexing Information (UL Mux Info)[FDD] ..... | 28 | +| 6.2.4.22 | UL CLTD Removal (CLTD-R)[FDD] ..... | 28 | +| 6.3 | Control frames..... | 28 | +| 6.3.1 | Introduction ..... | 28 | +| 6.3.2 | Header structure of the control frames ..... | 29 | +| 6.3.2.1 | Frame CRC ..... | 29 | +| 6.3.2.2 | Frame Type (FT)..... | 29 | +| 6.3.2.3 | Control Frame Type..... | 29 | +| 6.3.3 | Payload structure and information elements ..... | 30 | +| 6.3.3.1 | TIMING ADJUSTMENT ..... | 30 | +| 6.3.3.1.1 | Payload structure ..... | 30 | +| 6.3.3.1.2 | CFN ..... | 30 | +| 6.3.3.1.3 | Time of Arrival (ToA)..... | 30 | +| 6.3.3.1.4 | Spare Extension..... | 30 | +| 6.3.3.2 | DL SYNCHRONISATION ..... | 30 | +| 6.3.3.2.1 | Payload structure ..... | 30 | +| 6.3.3.2.2 | CFN ..... | 30 | +| 6.3.3.2.3 | Spare Extension..... | 31 | +| 6.3.3.3 | UL SYNCHRONISATION ..... | 31 | +| 6.3.3.3.1 | Payload structure ..... | 31 | +| 6.3.3.3.2 | CFN ..... | 31 | +| 6.3.3.3.3 | Time of Arrival (ToA)..... | 31 | +| 6.3.3.3.4 | Spare Extension..... | 31 | +| 6.3.3.4 | OUTER LOOP POWER CONTROL [FDD, 1.28Mcps TDD] ..... | 31 | +| 6.3.3.4.1 | Payload structure ..... | 31 | +| 6.3.3.4.2 | SIR Target ..... | 32 | +| 6.3.3.4.3 | Spare Extension..... | 32 | +| 6.3.3.4.4 | UL Mux Info ..... | 32 | +| 6.3.3.5 | DL NODE SYNCHRONISATION ..... | 32 | +| 6.3.3.5.1 | Payload structure ..... | 32 | +| 6.3.3.5.2 | T1 ..... | 32 | +| 6.3.3.5.3 | Spare Extension..... | 32 | +| 6.3.3.6 | UL NODE SYNCHRONISATION ..... | 32 | +| 6.3.3.6.1 | Payload structure ..... | 32 | +| 6.3.3.6.2 | T1 ..... | 33 | +| 6.3.3.6.3 | T2 ..... | 33 | +| 6.3.3.6.4 | T3 ..... | 33 | +| 6.3.3.6.5 | Spare Extension..... | 33 | +| 6.3.3.7 | RX TIMING DEVIATION [3.84 Mcps and 7.68Mcps TDD] ..... | 33 | +| 6.3.3.7.1 | Payload structure ..... | 33 | +| 6.3.3.7.2 | Rx Timing Deviation [3.84 Mcps TDD]..... | 34 | +| 6.3.3.7.2A | Rx Timing Deviation [7.68 Mcps TDD]..... | 34 | +| 6.3.3.7.2B | E-RUCCH Flag ..... | 35 | +| 6.3.3.7.3 | Spare Extension..... | 35 | +| 6.3.3.7.4 | CFN ..... | 35 | +| 6.3.3.7.5 | New IE Flags ..... | 35 | +| 6.3.3.8 | DSCH TFCI SIGNALLING [FDD] ..... | 35 | +| 6.3.3.8.1 | Payload structure ..... | 35 | +| 6.3.3.8.2 | TFCI (field 2) ..... | 35 | +| 6.3.3.8.3 | Spare Extension..... | 35 | +| 6.3.3.8.4 | CFN ..... | 36 | +| 6.3.3.9 | RADIO INTERFACE PARAMETER UPDATE [FDD] ..... | 36 | + +| | | | +|-------------------------------|------------------------------------------------------------------------|-----------| +| 6.3.3.9.1 | Payload structure ..... | 36 | +| 6.3.3.9.2 | Radio Interface Parameter Update flags..... | 36 | +| 6.3.3.9.3 | TPC Power Offset (TPC PO) ..... | 37 | +| 6.3.3.9.4 | Spare Extension..... | 37 | +| 6.3.3.9.4A | CFN ..... | 37 | +| 6.3.3.9.5 | DPC Mode..... | 37 | +| 6.3.3.9.6 | TFCI Power Offset (TFCI PO)..... | 37 | +| 6.3.3.9.7 | TFCI Power Offset for primary cell (TFCI PO_primary)..... | 37 | +| 6.3.3.9.8 | Multiple RL Sets Indicator ..... | 37 | +| 6.3.3.9.9 | Maximum UE TX Power ..... | 37 | +| 6.3.3.9.10 | Multiple RL Sets Indicator on the secondary uplink frequency..... | 38 | +| 6.3.3.10 | TIMING ADVANCE [3.84Mcps and 7.68 Mcps TDD] ..... | 38 | +| 6.3.3.10.1 | Payload structure ..... | 38 | +| 6.3.3.10.2 | CFN ..... | 38 | +| 6.3.3.10.3 | TA [3.84 Mcps]..... | 39 | +| 6.3.3.10.3A | TA [7.68 Mcps]..... | 39 | +| 6.3.3.10.4 | Spare Extension..... | 39 | +| 6.3.3.10.5 | New IE Flags [7.68Mcps TDD] ..... | 39 | +| 6.3.3.11 | TNL CONGESTION INDICATION..... | 39 | +| 6.3.3.11.1 | Payload structure ..... | 39 | +| 6.3.3.11.2 | Congestion Status ..... | 39 | +| 6.3.3.11.3 | Spare Extension..... | 39 | +| 7 | Handling of Unknown, Unforeseen and Erroneous Protocol Data ..... | 40 | +| 7.1 | General ..... | 40 | +| 7.2 | Error detection ..... | 40 | +| 7.2.1 | CRC Calculation..... | 40 | +| 7.2.1.1 | Relation between input and output of the Cyclic Redundancy Check ..... | 40 | +| Annex A (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 shall provide a description of the UTRAN Iur and Iub interfaces user plane protocols for Dedicated Transport Channel data streams as agreed within the TSG-RAN working group 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 TS 25.301: "Radio interface protocol architecture". +- [2] 3GPP TS 25.401: "UTRAN overall description". +- [3] 3GPP TS 25.302: "Services provided by the physical layer". +- [4] 3GPP TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling". +- [5] 3GPP TS 25.402: "Synchronisation in UTRAN, Stage 2". +- [6] 3GPP TS 25.423: "UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling". +- [7] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)". +- [8] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)". +- [9] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [10] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [11] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [12] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [13] 3GPP TS 25.319: "Enhanced uplink; Overall description; Stage 2" +- [14] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)" +- [15] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification" +- [16] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Transport Bearer:** service provided by the transport layer and used by frame protocol for the delivery of FP PDU + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|----------------------------------------| +| BER | Bit Error Rate | +| CCTrCH | Coded Composite Transport Channel | +| CFN | Connection Frame Number | +| CRC | Cyclic Redundancy Checksum | +| CRCI | CRC Indicator | +| DCH | Dedicated Transport Channel | +| DL | Downlink | +| DPC | Downlink Power Control | +| DRNC | Drift RNC | +| DSCH | Downlink Shared Channel | +| DTX | Discontinuous Transmission | +| E-DCH | Enhanced DCH | +| FP | Frame Protocol | +| FT | Frame Type | +| HARQ | Hybrid ARQ | +| LTOA | Latest Time of Arrival | +| PC | Power Control | +| PDU | Protocol Data Unit | +| PO | Power Offset | +| QE | Quality Estimate | +| RL | Radio Link | +| SIR | Signal-to-Interference Ratio | +| SRNC | Serving RNC | +| TB | Transport Block | +| TBS | Transport Block Set | +| TFI | Transport Format Indicator | +| TFCI | Transport Format Combination Indicator | +| ToA | Time of Arrival | +| ToAWE | Time of Arrival Window Endpoint | +| ToAWS | Time of Arrival Window Startpoint | +| TPC | Transmit Power Control | +| TTI | Transmission Time Interval | +| UE | User Equipment | +| UL | Uplink | + +## 3.3 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 7.68 Mcps TDD, 3.84Mcps 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 7.68Mcps TDD, 3.84Mcps TDD and 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. +- [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. +- [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 7.68 Mcps TDD, 3.84Mcps 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. +- [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. +- [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. +- 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. Timing Adjustment 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. DL SYNCHRONISATION 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. *Connection 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.2.4 or 6.3.3 enclosed by quotation marks, e.g. "0" or "255". + +# 4 General aspects + +The specification of Iub DCH and E-DCH data streams is also valid for Iur DCH and E-DCH data streams. + +The complete configuration of the transport channel is selected by the SRNC and signalled to the Node B via the Iub and Iur control plane protocols. + +The parameters of a transport channel are described in TS 25.301 [1]. Transport channels are multiplexed on the downlink by the Node B on radio physical channels, and de-multiplexed on the uplink from radio physical channels to transport channels. + +In Iur interface, every set of coordinated transport channels related to one UE context that is communicated over a set of cells that are macro-diversity combined within Node B or DRNC, is carried on one transport bearer. This means that there are as many transport bearers as set of coordinated transport channels and Iur DCH data ports for that communication. + +In Iub interface, every set of coordinated transport channels related to one UE context that is communicated over a set of cells that are macro-diversity combined within Node B is carried on one transport bearer. This means that there are as many transport bearers as set of coordinated transport channels and Iub DCH data ports for that communication. + +Bi-directional transport bearers are used. + +## 4.1 DCH and E-DCH FP services + +DCH frame protocol provides the following services: + +- Transport of TBS across Iub and Iur interface. +- Transport of outer loop power control information between the SRNC and the Node B. +- Support of transport channel synchronisation mechanism. +- Support of node synchronization mechanism. +- [3.84 Mcps TDD and 7.68 Mcps - Transfer of Rx timing deviation from the Node B to the SRNC.] +- Transfer of radio interface parameters from the SRNC to the Node B. + +[FDD – E-DCH frame protocol provides the following services: + +- Transport of MAC-es or MAC-is PDUs across Iub and Iur interface from Node B to SRNC. +- Transport of outer loop power control information between the SRNC and the Node B. +- Transfer of radio interface parameters from the SRNC to the Node B. +- Transport of network congestion indication from SRNC across Iub and Iur interface. +- Transport of hybrid ARQ information between SRNC and Node B.] + +[TDD – E-DCH frame protocol provides the following services: + +- Transport of MAC-es or MAC-is PDUs across Iub and Iur interface from Node B to SRNC. +- Transport of outer loop power control information between the SRNC and the Node B. +- Transport of network congestion indication from SRNC across Iub and Iur interface. +- Transport of hybrid ARQ information between SRNC and Node B.] + +## 4.2 Services expected from the Data Transport Network layer + +Following service is required from the transport layer: + +- Delivery of FP PDU. + +In sequence delivery is not required. However, frequent out-of-sequence delivery may impact the performance and should be avoided. + +## 4.3 Protocol Version + +This revision of the specification specifies version 1 of the protocol. + +# 5 DCH Frame Protocol procedures + +## 5.1 Data Transfer + +### 5.1.0 General + +When there is some data to be transmitted, DCH data frames are transferred every transmission time interval from the SRNC to the Node B for downlink transfer, and DCH/E-DCH data frames are transferred every transmission time interval from Node B to the SRNC for uplink transfer. [FDD – For 2 ms Uu TTI and depending on configuration from higher layers, the uplink E-DCH MAC-es or MAC-is PDU's from one or more 2ms Uu TTI's may be bundled into one E-DCH Data Frame before being transferred at an interval of e.g. 10ms from the Node B to the SRNC.] + +An optional error detection mechanism may be used to protect the data transfer if needed. At the transport channel setup it shall be specified if the error detection on the user data is used. + +### 5.1.1 Uplink for DCH + +![Diagram of Uplink Data Transfer procedure for DCH](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +The diagram shows two entities, 'Node B' and 'SRNC', each in a rectangular box. Below each box is a horizontal line representing a layer. A horizontal arrow labeled 'UL DATA FRAME' points from the layer under 'Node B' to the layer under 'SRNC'. + +Diagram of Uplink Data Transfer procedure for DCH + +Figure 1: Uplink Data Transfer procedure + +Two modes can be used for the UL transmission: *normal mode* and *silent mode*. The mode is selected by the SRNC when the transport bearer is setup and signalled to the Node B with the relevant control plane procedure. + +- In normal mode, the Node B shall always send an UL DATA FRAME to the RNC for all the DCHs in a set of coordinated DCHs regardless of the number of Transport Blocks of the DCHs. +- In silent mode and in case only one transport channel is transported on a transport bearer, the Node B shall not send an UL DATA FRAME to the RNC when it has received a TFI indicating "number of TB equal to 0" for the transport channel during a TTI. +- In silent mode and in case of coordinated DCHs, when the Node B receives a TFI indicating "number of TB equal to 0" for all the DCHs in a set of coordinated DCHs, the Node B shall not send an UL DATA FRAME to the RNC for this set of coordinated DCHs. + +For any TTI in which the Node B Layer 1 generated at least one CPHY-Out-of-Sync-IND primitive, the Node B is not required to send an UL DATA FRAME to the SRNC. + +When Node B receives an invalid TFCI, no UL DATA FRAME shall be sent to the SRNC. + +#### 5.1.1a Uplink for E-DCH + +![Diagram of Uplink Data Transfer procedure for E-DCH](e58a867750e4ae01604318506b79df7a_img.jpg) + +The diagram shows two entities, 'Node B' and 'SRNC', each in a rectangular box. Below each box is a horizontal line representing a layer. A horizontal arrow labeled 'E-DCH UL DATA FRAME' points from the layer under 'Node B' to the layer under 'SRNC'. + +Diagram of Uplink Data Transfer procedure for E-DCH + +Figure 1a: Uplink Data Transfer procedure + +When a MAC-e or MAC-i PDU is received, it is demultiplexed into MAC-d flows which are then each sent on separate transport bearers to the RNC using the E-DCH UL DATA FRAME TYPE 1 (MAC-e) or TYPE 2 (MAC-i). + +Only silent mode is used, i.e. E-DCH user-plane payload is transmitted using the E-DCH UL DATA FRAME only when some payload has been successfully received. + +[FDD – In case of Multi Cell E-DCH operation two transport bearer modes can be used for the E-DCH payload transmission: *separate Iub transport bearer mode* and *E-DCH UL flow multiplexing mode*. The mode is selected by the SRNC when the RL on secondary UL frequency is setup and signalled to the Node B with the relevant control plane procedure. + +- In separate Iub transport bearer mode, the Node B shall send each MAC-d flow received in cells of the different UL frequencies (primary and secondary) on separate transport bearers, one per frequency, to the RNC using the E-DCH UL DATA FRAME TYPE 2 (MAC-i). +- In E-DCH UL flow multiplexing mode, the Node B shall send the MAC-d flows received on all UL frequencies (primary as well as secondary) on one transport bearer to the RNC using the E-DCH UL DATA FRAME TYPE 2 (MAC-i).] + +[1.28Mcps TDD – In case of multiple carriers E-DCH operation two transport bearer modes can be used for the E-DCH payload transmission: *separate Iub transport bearer mode* and *E-DCH UL flow multiplexing mode*. The mode is selected by the SRNC when the RL is setup and signalled to the Node B with the relevant control plane procedure. + +- In separate Iub transport bearer mode, the Node B shall send each MAC-d flow received in the different frequencies on separate transport bearers, one per frequency, to the RNC using the E-DCH UL DATA FRAME TYPE 2 (MAC-i). +- In E-DCH UL flow multiplexing mode, the Node B shall send one MAC-d flow received on all frequencies on one transport bearer to the RNC using the E-DCH UL DATA FRAME TYPE 2 (MAC-i).] + +### 5.1.2 Downlink + +![Diagram illustrating the Downlink Data Transfer procedure. A Node B (left) and an SRNC (right) are shown. An arrow labeled 'DL DATA FRAME' points from the SRNC to the Node B, indicating the direction of data transfer.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +``` + +graph LR + SRNC[SRNC] -- "DL DATA FRAME" --> NodeB[Node B] + +``` + +Diagram illustrating the Downlink Data Transfer procedure. A Node B (left) and an SRNC (right) are shown. An arrow labeled 'DL DATA FRAME' points from the SRNC to the Node B, indicating the direction of data transfer. + +Figure 2: Downlink Data Transfer procedure + +The Node B shall only consider a transport bearer synchronised after it has received at least one DL DATA FRAME on this transport bearer before LTOA (TS 25.402 [5]). + +The Node B shall consider the DL user plane of a certain RL synchronised once all transport bearers established to carry DCH DL DATA FRAMES included in the CCTrCH for this RL are considered as synchronised. Once synchronised, the Node B shall assume the DL user plane for this Radio Link stays synchronised as long as the Radio Link exists, even if transport bearers are added (see 5.10.2), replaced (see subclause 5.10.1), or removed. When a RL established through the Radio Link Addition procedure (TS 25.433 [4] TS 25.423 [6]) is combined with a RL whose DL user plane is considered as synchronised, the Node B shall consider the DL user plane of this newly established RL as synchronised. + +[FDD - The Node B shall transmit on the DL DPDCH(s) of a certain RL only when the DL user plane of this RL is considered synchronised.] + +[TDD – The Node B shall transmit special bursts on the DL DPCH as per TS 25.224 [11], until the DL user plane is considered synchronised]. + +When the DL user plane is considered synchronised and the Node B does not receive a valid DL DATA FRAME in a TTI, it assumes that there is no data to be transmitted in that TTI for this transport channel, and shall act as one of the following cases: + +- [TDD – If the Node B receives no valid DL DATA FRAMES for any transport channel assigned to a UE it shall assume DTX and transmit special bursts as per TS 25.224 [11]]. +- If the Node B is aware of a TFI value corresponding to zero bits for this transport channel, this TFI is assumed. If the TFS contains both a TFI corresponding to "TB length equal to 0 bits" and a TFI corresponding to "number of TB equal to 0", the Node B shall assume the TFI corresponding to "number of TB equal to 0". When combining the TFI's of the different transport channels, a valid TFCI might result and in this case data shall be transmitted on Uu. +- If the Node B is not aware of a TFI value corresponding to zero bits for this transport channel or if combining the TFI corresponding to zero bits with other TFI's, results in an unknown TFI combination, the handling as described in the following paragraph shall be applied. + +At each radio frame, the Node B shall build the TFCI value of each CCTrCH, according to the TFI of the DCH data frames multiplexed on this CCTrCH and scheduled for that frame. [FDD - In case the Node B receives an unknown combination of TFIs from the DL DATA FRAMES, it shall transmit only the DPCCH without TFCI bits.] [TDD - In case the Node B receives an unknown combination of DCH DL DATA FRAMES, it shall apply DTX, i.e. suspend transmission on the corresponding DPCHs.] + +## 5.2 Timing Adjustment + +The Timing Adjustment procedure is used to keep the synchronization of the DCH data stream in DL direction, i.e to ensure that the Node B receives the DL frames in an appropriate time for the transmission of the data in the air interface. + +SRNC always includes the Connection Frame Number (CFN) to all DCH DL DATA FRAMES. + +If a DL DATA FRAME arrives outside the arrival window defined in the Node B, the Node B shall send a TIMING ADJUSTMENT control frame, containing the measured ToA and the CFN value of the received DL DATA FRAME. + +![Diagram illustrating the Timing Adjustment procedure. A Node B (left) sends a TIMING ADJUSTMENT message to an SRNC (right).](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) + +``` + +graph LR + NodeB[Node B] -- TIMING ADJUSTMENT --> SRNC[SRNC] + +``` + +The diagram shows two entities, 'Node B' and 'SRNC', each represented by a rectangle with a horizontal line underneath. A horizontal arrow labeled 'TIMING ADJUSTMENT' points from the 'Node B' rectangle to the 'SRNC' rectangle. + +Diagram illustrating the Timing Adjustment procedure. A Node B (left) sends a TIMING ADJUSTMENT message to an SRNC (right). + +**Figure 3: Timing Adjustment procedure** + +The arrival window and the time of arrival are defined as follows: + +**Time of Arrival Window Endpoint (ToAWE):** ToAWE represents the time point by which the DL data shall arrive to the Node B from Iub. The ToAWE is defined as the amount of milliseconds before the last time point from which a timely DL transmission for the identified CFN would still be possible taking into account the Node B internal delays. ToAWE is set via control plane. If data does not arrive before ToAWE a TIMING ADJUSTMENT control frame shall be sent by Node B. + +**Time of Arrival Window Startpoint (ToAWS):** ToAWS represents the time after which the DL data shall arrive to the Node B from Iub. The ToAWS is defined as the amount of milliseconds from the ToAWE. ToAWS is set via control plane. If data arrives before ToAWS a TIMING ADJUSTMENT control frame shall be sent by Node B. + +**Time of Arrival (ToA):** ToA is the time difference between the end point of the DL arrival window (ToAWE) and the actual arrival time of DL frame for a specific CFN. A positive ToA means that the frame is received before the ToAWE, a negative ToA means that the frame is received after the ToAWE. + +The general overview on the Timing Adjustment procedure is reported in TS 25.401 [2]. + +## 5.3 DCH Synchronisation + +DCH Synchronisation procedure is used to achieve or restore the synchronisation of the DCH data stream in DL direction, and as a keep alive procedure in order to maintain activity on the Iur/Iub transport bearer. + +The procedure is initiated by the SRNC by sending a DL SYNCHRONISATION control frame towards Node B. This control frame indicates the target CFN. + +Upon reception of the DL SYNCHRONISATION control frame, Node B shall immediately respond with UL SYNCHRONISATION control frame indicating the ToA for the DL SYNCHRONISATION control frame and the CFN indicated in the received DL SYNCHRONISATION control frame. + +UL SYNCHRONISATION control frame shall always be sent, even if the DL SYNCHRONISATION control frame is received by the Node B within the arrival window. + +![Sequence diagram of DCH Synchronisation procedure between Node B and SRNC.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +A sequence diagram showing the interaction between Node B and SRNC. The SRNC sends a 'DL SYNCHRONISATION' message to the Node B. The Node B responds with a 'UL SYNCHRONISATION' message back to the SRNC. Both entities are represented by rectangular boxes with a horizontal line at the bottom. + +Sequence diagram of DCH Synchronisation procedure between Node B and SRNC. + +Figure 4: DCH Synchronisation procedure + +## 5.4 Outer Loop PC Information Transfer [FDD, 1.28 Mcps TDD] + +Based, for example, on the CRCI values and on the quality estimate in the UL DATA FRAME, SRNC modifies the SIR target used by the UL inner loop power control by including the absolute value of the new SIR target in the OUTER LOOP PC control frame sent to the Node B's. + +At the reception of the OUTER LOOP PC control frame, the Node B shall immediately update the SIR target used for the inner loop power control [1.28 Mcps TDD - of the respective CCTrCH for UL DCHs] with the specified value. + +The OUTER LOOP PC control frame can be sent via any of the transport bearers dedicated to one UE. [1.28 Mcps TDD - In case of multiple CCTrCHs carrying DCHs, the OUTER LOOP PC control frame can be sent via any of the transport bearers carrying DCHs which belong to the CCTrCH for which the UL SIR target shall be adjusted.] + +![Sequence diagram of Outer Loop Power Control Information Transfer procedure between Node B and SRNC.](2bc39576969969ffe6d3f3d5264bba75_img.jpg) + +A sequence diagram showing the interaction between Node B and SRNC. The SRNC sends an 'OUTER LOOP PC' message to the Node B. Both entities are represented by rectangular boxes with a horizontal line at the bottom. + +Sequence diagram of Outer Loop Power Control Information Transfer procedure between Node B and SRNC. + +Figure 5: Outer Loop Power Control Information Transfer procedure + +## 5.5 Node Synchronisation + +The Node Synchronisation procedure is used by the SRNC to acquire information on the Node B timing. + +The procedure is initiated by the SRNC by sending a DL NODE SYNCHRONISATION control frame to Node B containing the parameter T1. + +Upon reception of a DL NODE SYNCHRONISATION control frame, the Node B shall respond with UL NODE SYNCHRONISATION control frame, including the parameters T2 and T3, as well as the T1 which was indicated in the initiating DL NODE SYNCHRONISATION control frame. + +The T1, T2, T3 parameters are defined as: + +T1: RNC specific frame number (RFN) that indicates the time when RNC sends the DL NODE SYNCHRONISATION control frame through the SAP to the transport layer. + +T2: Node B specific frame number (BFN) that indicates the time when Node B receives the correspondent DL NODE SYNCHRONIZATION control frame through the SAP from the transport layer. + +T3: Node B specific frame number (BFN) that indicates the time when Node B sends the UL NODE SYNCHRONISATION control frame through the SAP to the transport layer. + +The general overview on the Node Synchronisation procedure is reported in TS 25.401 [2]. + +![Figure 6: Node Synchronisation procedure diagram. It shows two entities, Node B and SRNC, represented by boxes. A horizontal arrow labeled 'DL NODE SYNCHRONISATION' points from the SRNC box to the Node B box. Below it, another horizontal arrow labeled 'UL NODE SYNCHRONISATION' points from the Node B box to the SRNC box. Both boxes have a vertical line extending downwards to a thick horizontal bar at the bottom, representing the radio interface.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +Figure 6: Node Synchronisation procedure diagram. It shows two entities, Node B and SRNC, represented by boxes. A horizontal arrow labeled 'DL NODE SYNCHRONISATION' points from the SRNC box to the Node B box. Below it, another horizontal arrow labeled 'UL NODE SYNCHRONISATION' points from the Node B box to the SRNC box. Both boxes have a vertical line extending downwards to a thick horizontal bar at the bottom, representing the radio interface. + +Figure 6: Node Synchronisation procedure + +## 5.6 Rx Timing Deviation Measurement [3.84 Mcps and 7.68 Mcps TDD] + +In case the *Timing Advance Applied* IE indicates "Yes" (see TS 25.433 [4]) in a cell, the Node B shall, for all UEs using DCHs/E-DCHs, monitor the receiving time of the uplink DPCH/E-PUCH bursts arriving over the radio interface, and shall calculate the Rx timing deviation. Additionally, the Rx timing deviation shall be calculated when an E-RUCCH or a TA Request (TS 25.319 [13]) transmission is received. If the calculated value, after rounding, is not zero, it shall be reported to the SRNC in a RX TIMING DEVIATION control frame belonging to that UE. For limitation of the frequency of this reporting, the Node B shall not send more than one RX TIMING DEVIATION control frame per UE within one radio frame. The RX TIMING DEVIATION control frame indicates whether the deviation is derived from a conventional E-RUCCH or a TA Request reception. + +If the *Timing Advance Applied* IE indicates "No" (see TS 25.433 [4]) in a cell, monitoring of the receiving time of the uplink DPCH bursts is not necessary and no RX TIMING DEVIATION control frame shall be sent. + +![Figure 7: Rx Timing Deviation Measurement procedure diagram. It shows two entities, Node B and SRNC, represented by boxes. A horizontal arrow labeled 'RX TIMING DEVIATION' points from the Node B box to the SRNC box. Both boxes have a vertical line extending downwards to a thick horizontal bar at the bottom, representing the radio interface.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg) + +Figure 7: Rx Timing Deviation Measurement procedure diagram. It shows two entities, Node B and SRNC, represented by boxes. A horizontal arrow labeled 'RX TIMING DEVIATION' points from the Node B box to the SRNC box. Both boxes have a vertical line extending downwards to a thick horizontal bar at the bottom, representing the radio interface. + +Figure 7: Rx Timing Deviation Measurement procedure + +## 5.7 DSCH TFCI Signalling [FDD] + +Void. + +## 5.8 Radio Interface Parameter Update [FDD] + +This procedure is used to update radio interface parameters which are applicable to all RL's, or E-DCH Serving Radio Link Set, for the concerning UE. Both synchronised and unsynchronised parameter updates are supported. + +The procedure consists of a RADIO INTERFACE PARAMETER UPDATE control frame sent by the SRNC to the Node B. + +![Sequence diagram for Figure 9: Radio Interface Parameter Update procedure. It shows two vertical lifelines: Node B on the left and SRNC on the right. A horizontal arrow points from the SRNC lifeline to the Node B lifeline, labeled 'RADIO INTERFACE PARAMETER UPDATE'. Both lifelines end in a thick horizontal bar at the bottom.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +Sequence diagram for Figure 9: Radio Interface Parameter Update procedure. It shows two vertical lifelines: Node B on the left and SRNC on the right. A horizontal arrow points from the SRNC lifeline to the Node B lifeline, labeled 'RADIO INTERFACE PARAMETER UPDATE'. Both lifelines end in a thick horizontal bar at the bottom. + +**Figure 9: Radio Interface Parameter Update procedure** + +If the RADIO INTERFACE PARAMETER UPDATE control frame contains a valid TPC power offset value, the Node B shall apply the newly provided TPC PO in DL. + +If the RADIO INTERFACE PARAMETER UPDATE control frame contains a valid Maximum UE TX Power value, the E-DCH serving Node B may use the provided value to improve E-DCH scheduling. + +If the frame contains a valid DPC mode value, the Node B shall apply the newly provided value in DL power control. + +The new values shall be applied as soon as possible in case no valid CFN is included or from the indicated CFN. If the frame contains a valid Multiple RL Sets Indicator value, the Node B may use the newly provided value in Multiple RL Sets Indicator whenever the Node B loses UL synchronization on a RL Set after initial UL synchronization as described in TS 25.214 [12]. + +If the frame contains a valid Multiple RL Sets Indicator on the secondary uplink frequency value, the Node B may use the newly provided value in Multiple RL Sets Indicator on the secondary uplink frequency whenever the Node B loses UL synchronization on a RL Set after initial UL synchronization on the secondary uplink frequency as described in TS 25.214 [12]. + +## 5.9 Timing Advance [3.84 Mcps and 7.68 Mcps TDD] + +This procedure is used in order to signal to the Node B the adjustment to be performed by the UE in the uplink timing. + +The Node B shall use the CFN and timing adjustment values to adjust its layer 1 to allow for accurate impulse averaging. + +![Sequence diagram for Figure 9A: Timing Advance procedure. It shows two vertical lifelines: Node B on the left and SRNC on the right. A horizontal arrow points from the SRNC lifeline to the Node B lifeline, labeled 'TIMING ADVANCE'. Both lifelines end in a thick horizontal bar at the bottom.](69f52512bb7387a5dc9f952279513019_img.jpg) + +Sequence diagram for Figure 9A: Timing Advance procedure. It shows two vertical lifelines: Node B on the left and SRNC on the right. A horizontal arrow points from the SRNC lifeline to the Node B lifeline, labeled 'TIMING ADVANCE'. Both lifelines end in a thick horizontal bar at the bottom. + +**Figure 9A: Timing Advance procedure** + +## 5.10 General + +### 5.10.1 Transport bearer replacement + +As described in NBAP (TS 25.433 [4]) and RNSAP (TS 25.423 [6]), transport bearer replacement can be achieved by using the Synchronised Radio Link Reconfiguration Preparation procedure in combination with the Synchronised Radio Link Reconfiguration Commit procedure, or by using the Unsynchronised Radio Link Reconfiguration procedure. In both cases the following steps can be discerned: + +- 1) The new transport bearer is established after which 2 transport bearers exist in parallel. + +- 2) The transport channel(s) is/are switched to the new transport bearer. +- 3) The old transport bearer is released. + +In step 1), communication on the old transport bearer continues as normal. In addition, the Node B shall support DL DATA FRAMES, the DCH Synchronisation procedure (see section 5.3) and the Timing Adjustment procedure (see section 5.2) on the new bearer. This enables the SRNC to determine the timing on the new transport bearer. DL DATA FRAMES transported on the new transport bearer shall not be transmitted on the DL DPDCH before the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message. + +Regarding step 2), the moment of switching is determined differently in the synchronised and unsynchronised case: + +- When using the combination of the Synchronised Radio Link Reconfiguration Preparation procedure and the Synchronised Radio Link Reconfiguration Commit procedure, the UL/DL DATA FRAMES shall be transported on the new transport bearer from the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message [FDD - or in the case the the *Fast Reconfiguration* IE is included in the RADIO LINK RECONFIGURATION COMMIT message the Node B shall start using the new transport bearer for the transport of UL DATA FRAMES from the CFN at which the NodeB detects that the UE uses the new configuration in the uplink]. +- When using the Unsynchronised Radio Link Reconfiguration procedure, the Node B shall start using the new transport bearer for the transport of UL DATA FRAMES from the CFN at which the new transport bearer is considered synchronised (i.e. has received a DL DATA FRAME before LTOA (TS 25.433 [4])). Not applicable for E-DCH. Change is done directly in case of an E-DCH. + +In both cases, starting from this CFN the Node-B shall support all applicable DCH/E-DCH Frame Protocol procedures on the new transport bearer and no requirements exist regarding support of DCH/E-DCH Frame Protocol procedures on the old transport bearer. + +Finally in step 3), the old transport bearer is released. + +### 5.10.2 Transport channel addition + +As described in NBAP (TS 25.433 [4]) and RNSAP (TS 25.423 [6]), transport channel addition can be achieved by using the Synchronised Radio Link Reconfiguration Preparation procedure in combination with the Synchronised Radio Link Reconfiguration Commit procedure, or by using the Unsynchronised Radio Link Reconfiguration procedure. + +When using the Synchronised Radio Link Reconfiguration Preparation procedure the Node B shall support DL DATA FRAMES, the Synchronisation procedure (see section 5.3) and the Timing Adjustment procedure (see section 5.2) on the new transport bearer also before the CFN indicated in the RADIO LINK RECONFIGURATION COMMIT message, in order to enable the SRNC to determine the timing on the new transport bearer. DL DATA FRAMES transported on the new transport bearer before this CFN shall not be transmitted on the DL DPDCH. Starting from this CFN the Node B shall support all applicable DCH and E-DCH frame protocol procedures on the new transport bearer. + +When using the Unsynchronised Radio Link Reconfiguration procedure the Node B shall support data frames and control frames when the new transport bearer is established. + +## 5.11 Generation of subframe number + +The *CFN* and *Subframe Number* IE's values in the E-DCH Data Frame shall reflect the CFN and subframe number when the payload in the E-DCH Data Frame was correctly received on the Uu. This corresponds to when the HARQ process correctly decoded the data. [FDD - The subframe number is for 2 ms TTI set to values {0-4} and for 10 ms TTI set to {0}]. [3.84Mcps TDD, 7.68 Mcps TDD - the subframe number is set to {0}]. [1.28 Mcps TDD - the subframe number is set to {0-1}]. + +## 5.12 Generation of number of HARQ retransmissions + +After successful decoding of E-DCH payload received over Uu, the Node B shall insert the following values in the *Number of HARQ Retransmissions* IE: + +- If the RSN value in the last HARQ retransmission that resulted in successful decoding has the value 0, 1 [FDD - or 2], then the Node B shall insert the same value in the *Number Of HARQ Retransmissions* IE in the E-DCH Data Frame. +- If the RSN value in the last HARQ retransmission that resulted in successful decoding has the value [TDD -2 or] 3, then the Node B shall insert the calculated value of the actual number of retransmissions used for the successful decoding into the *Number of HARQ Retransmissions* IE in the E-DCH Data Frame. If the actual number of retransmission cannot be calculated, then the Node B shall insert the value 15 in the *Number of HARQ Retransmissions* IE, indicating that the number of HARQ retransmissions is unknown. +- If the UE was power limited at the time the subframe was received, or another condition applies in which the number of retransmissions should not influence the SIR target level, then the Node B shall insert value 13 into the *Number of HARQ Retransmissions* IE, indicating that the *Number of HARQ Retransmissions* IE is inappropriate as input to the outer loop power control. + +After unsuccessful decoding of the E-DCH payload, the serving Node B shall act according to section 5.13, Indication of HARQ failure. + +## 5.13 Indication of HARQ failure + +After unsuccessful decoding of the E-DCH payload and under conditions listed below, the serving Node B shall send a HARQ Failure Indication to the SRNC. [FDD - The non-serving Node B(s) shall not send a HARQ Failure Indication.] + +The serving Node B shall send a HARQ Failure Indication to the SRNC under any of the following conditions: + +- A MAC-e or MAC-i PDU for a HARQ process has not yet been successfully decoded and the RSN [TDD -and HARQ process ID] indicates the transmission of a new MAC-e or MAC-i PDU for the same HARQ process and the number of HARQ retransmissions that had already occurred was equal or higher than the lowest of the maximum HARQ retransmissions values for the UE's configured MAC-d flows. +- A MAC-e or MAC-i PDU for a HARQ process has not yet been successfully decoded and the maximum retransmissions for the MAC-d flow with the highest maximum HARQ retransmissions value valid for the UE connection have occurred, or should have occurred in case the HARQ related outband signalling (RSN) on the [FDD - E-DPCCH] [TDD - E-UCCH] could not be decoded. +- A MAC-e or MAC-i PDU for a HARQ process has not yet been successfully decoded when the MAC-e or MAC-i Reset is performed in UE. The Node B knows the timing of the MAC-e or MAC-i Reset in the UE via higher layer. + +The HARQ Failure Indication shall be sent on only one transport bearer. The Node B may select any of the transport bearers associated with the UE for which the HARQ failure relates to. + +[FDD – In case of Multi Cell E-DCH operation: + +- In E-DCH UL flow multiplexing mode, the NodeB may select any of the transport bearers associated with the UE for which the HARQ failure relates to, and including UL Mux Info (UL Multiplexing Information) into data frame to indicate on which frequency the HARQ failure happens - primary UL frequency or secondary UL frequency. +- In separate Iub transport bearer mode, the NodeB may select any of the transport bearers associated with the frequency of the UE for which the HARQ failure relates to]. + +The HARQ failure is indicated in a user data frame with values set as follows: + +- The *CFN* and *Subframe Number* IE values shall reflect the time when the failure was detected +- TYPE 1: The *Number of MAC-es PDUs* IE shall be set to zero. As a consequence there are no *DDI* and *N* IEs in the header and 4 bits padding is used after *Number of MAC-es PDUs* IE in order to have the octet aligned structure, and there are no *MAC-es PDUs* IEs in the payload part of the data frame related to the HARQ failure. +- TYPE 2: The *Number of MAC-is PDUs* IE shall be set to zero. As a consequence there are no *MAC-is PDU descriptor* IE and there are no *MAC-is PDUs* IEs in the payload part of the data frame related to the HARQ failure. + +- The *Number of HARQ Retransmissions* IE shall be set to the number of HARQ retransmissions that occurred when the failure was detected. The coding shall be the same as for a correctly decoded payload as described in section 5.12. +- [FDD - In case of Multi Cell E-DCH operation, the *UL Mux Info* IE shall indicate the frequency in which the failure was detected - primary UL frequency or secondary UL frequency as described in subclause 6.2.4.21 in E-DCH UL flow multiplexing mode of Multi Cell E-DCH operation.] + +## 5.14 TNL Congestion Indication + +This procedure is used by the SRNC to signal, on a transport bearer carrying an E-DCH MAC-d flow, that a transport network congestion situation on Iub/Iur has been detected. + +![Diagram of TNL Congestion Indication procedure showing Node B and SRNC.](a734898ce18e972938949637c32a34f4_img.jpg) + +The diagram illustrates the TNL Congestion Indication procedure. It shows two main entities: 'Node B' on the left and 'SRNC' on the right. Each entity is represented by a rectangular box with a horizontal line extending downwards to a thick black horizontal bar. A horizontal arrow labeled 'TNL CONGESTION INDICATION' points from the SRNC box to the Node B box. + +Diagram of TNL Congestion Indication procedure showing Node B and SRNC. + +Figure 9AB: TNL Congestion Indication procedure + +At the reception of the TNL CONGESTION INDICATION control frame, the Node B should reduce the bit rate on the Iub interface. + +If the TNL CONGESTION INDICATION control frame is indicating “TNL Congestion – detected by frame loss”, or the TNL CONGESTION INDICATION control frame is indicating “TNL Congestion – detected by delay build-up”, the Node B should reduce the bit rate for at least the MAC-d flow on which the congestion indication control frame was received. + +If the TNL CONGESTION INDICATION control frame is indicating “No TNL Congestion”, the Node B can gradually go back to normal operation. + +# --- 6 Frame structure and coding + +## 6.1 General + +The general structure of a DCH FP frame consists of a header and a payload. The structure is depicted in figure 9B. + +![Diagram of general structure of a frame protocol PDU showing Header and Payload.](61a1c017e34df13360be6319539570df_img.jpg) + +The diagram shows the general structure of a frame protocol PDU. It consists of two adjacent rectangular boxes. The left box is labeled 'Header' and the right box is labeled 'Payload'. + +Diagram of general structure of a frame protocol PDU showing Header and Payload. + +Figure 9B: General structure of a frame protocol PDU + +The header contains a CRC checksum, the frame type field and information related to the frame type. + +There are two types of DCH FP frames (indicated by the *FT* IE): + +- DCH data frame. +- DCH control frame. + +For the UL direction there is also an E-DCH data frame (indicated by signalling). The E-DCH data frame is defined with two structures, TYPE 1 and TYPE 2 depending of if it contains MAC-es PDUs (TYPE 1) or MAC-is PDUs (TYPE 2). + +- E-DCH data frame. + +The payload of the data frames contains radio interface user data, quality information for the transport blocks and for the radio interface physical channel during the transmission time interval (for UL only), and an optional CRC field. + +The payload of the control frames contains commands and measurement reports related to transport bearer and the radio interface physical channel but not directly related to specific radio interface user data. + +### 6.1.1 General principles for the coding + +In the present document the structure of frames will be specified by using pictures similar to figure 10. + +![](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +| | | | | | | | | | +|-----------------|---|---|---------|---|---|---------|---|----------------------------------------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Condition

Byte 1
Byte 2
Byte 3 | +| Field 1 | | | | | | Field 2 | | | +| Field 3 | | | | | | | | | +| Field 3 (cont.) | | | Field 4 | | | | | | +| Spare Extension | | | | | | | | | + +**Figure 10: Example of notation used for the definition of the frame structure** + +Unless otherwise indicated, fields which consist of multiple bits within a byte will have the more significant bit located at the higher bit position (indicated above frame in figure 10). In addition, if a field spans several bytes, more significant bits will be located in lower numbered bytes (right of frame in figure 10). + +On the Iub/Iur interface, the frame will be transmitted starting from the lowest numbered byte. Within each byte, the bits are sent according decreasing bit position (bit position 7 first). + +The parameters are specified giving the value range and the step (if not 1). The coding is done as follows (unless otherwise specified): + +- Unsigned values are binary coded. +- Signed values are coded with the 2's complement notation. + +Bits labelled "Spare" shall be set to zero by the transmitter and shall be ignored by the receiver. The *Spare Extension* IE indicates the location where new IEs can in the future be added in a backward compatible way. The *Spare Extension* IE shall not be used by the transmitter and shall be ignored by the receiver. + +## 6.2 Data frames + +### 6.2.1 Introduction + +The purpose of the user data frames is to transparently transport the transport blocks between Node B and SRNC. + +The protocol allows for multiplexing of coordinated dedicated transport channels, with the same transmission time interval, onto one transport bearer. + +The transport blocks of all the coordinated DCHs for one transmission time interval are included in one frame. + +SRNC indicates the multiplexing of coordinated dedicated transport channels in the appropriate RNSAP/NBAP message. + +### 6.2.2 UL DATA FRAME + +#### 6.2.2.1 UL DATA FRAME FOR DCH + +The structure of the UL DATA FRAME is shown in figure 11. + +![Figure 11: UL DATA FRAME structure. A diagram showing the bit fields of an uplink data frame. The frame is divided into a Header and a Payload. The Header contains fields like Header CRC, FT, CFN, TFI of first DCH, TFI of last DCH, and First TB of first DCH. The Payload contains fields like First TB of first DCH (cont), Last TB of first DCH, Last TB of first DCH (cont), First TB of last DCH, First TB of last DCH (cont), Last TB of last DCH, Last TB of last DCH (cont), QE, CRCI of first TB of first DCH, CRCI of last TB of last DCH, Pad, Spare Extension, Payload CRC, and Payload CRC (cont).](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +| | | | | | | | | | +|-------------------------------|---|------------------|---|-----------------------------|-----|---|-----|---------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Header | +| Header CRC | | | | | | | FT | | +| CFN | | | | | | | | Payload | +| Spare bits 7-5 | | TFI of first DCH | | | | | | | +| Spare bits 7-5 | | TFI of last DCH | | | | | | | +| First TB of first DCH | | | | | | | | | +| First TB of first DCH (cont) | | | | | | | Pad | | +| Last TB of first DCH | | | | | | | | | +| Last TB of first DCH (cont) | | | | | | | Pad | | +| First TB of last DCH | | | | | | | | | +| First TB of last DCH (cont) | | | | | | | Pad | | +| Last TB of last DCH | | | | | | | | | +| Last TB of last DCH (cont) | | | | | | | Pad | | +| QE | | | | | | | | | +| CRCI of first TB of first DCH | | | | | | | | | +| | | | | CRCI of last TB of last DCH | Pad | | | | +| Spare Extension | | | | | | | | | +| Payload CRC | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | + +Figure 11: UL DATA FRAME structure. A diagram showing the bit fields of an uplink data frame. The frame is divided into a Header and a Payload. The Header contains fields like Header CRC, FT, CFN, TFI of first DCH, TFI of last DCH, and First TB of first DCH. The Payload contains fields like First TB of first DCH (cont), Last TB of first DCH, Last TB of first DCH (cont), First TB of last DCH, First TB of last DCH (cont), Last TB of last DCH, Last TB of last DCH (cont), QE, CRCI of first TB of first DCH, CRCI of last TB of last DCH, Pad, Spare Extension, Payload CRC, and Payload CRC (cont). + +Figure 11: UL DATA FRAME structure + +For the description of the fields see subclause 6.2.4. + +There are as many TFI fields as number of DCH multiplexed in the same transport bearer. + +The DCHs in the frame structure are ordered from the lower DCH id ('first DCH') to the higher DCH id ('last DCH'). + +The size and the number of TBs for each DCH are defined by the correspondent TFI. + +If the TB does not fill an integer number of bytes, then bit padding is used as shown in the figure in order to have the octet aligned structure (ex: a TB of 21 bits requires 3 bits of padding). + +There is a CRCI for each TB included in the frame irrespective of the size of the TB, i.e. the CRCI is included also when the TB length is zero. If the CRCIs of one data frame do not fill an integer number of bytes, then bit padding is used as shown in the figure in order to have the octet aligned structure (ex: 3 CRCI bits require 5 bits of padding, but there are no CRCI bits and no padding, when the number of TBs is zero). + +The *Payload CRC* IE is optional, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). + +#### 6.2.2.2 UL DATA FRAME FOR E-DCH TYPE 1 + +The structure of the E-DCH UL DATA FRAME TYPE 1 is shown in Figure 11a. TYPE 1 frame structure is used when the E-DCH UL DATA FRAME is carrying MAC-es PDUs (TS 25.321 [16]). + +![](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +| | | | | | | | | | | +|-------------------------------------|--------------------|---|---------------------|---------------------------------|---|--------|---|--------|----| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Header | | +| Header CRC | | | | | | | | | FT | +| Header CRC (cont) | | | | FSN | | | | | | +| Spare bits 7-4 | | | Number of subframes | | | | | | | +| CFN | | | | | | | | | | +| Spare | N of HARQ Retransm | | | 1 st subframe number | | | | | | +| N of MAC-es PDUs | | | First DDI | | | | | | | +| First DDI cont | First N | | | | | | | | | +| | | | | | | | | | | +| Last DDI | | | | | | Last N | | | | +| Last N cont | | | Pad | | | | | | | +| Spare | N of HARQ Retransm | | | Last Subframe number | | | | | | +| N of MAC-es PDUs | | | First DDI | | | | | | | +| First DDI cont | First N | | | | | | | | | +| | | | | | | | | | | +| Last DDI | | | | | | Last N | | | | +| Last N cont | | | Pad | | | | | | | +| Spare bits 7-6 | | | | | | | | | | +| First MAC-es PDU of first Subframe | | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | | +| Second MAC-es PDU of first Subframe | | | | | | | | | | +| | | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | | +| Last MAC-es PDU of first Subframe | | | | | | | | | | +| | | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | | +| First MAC-es PDU of last Subframe | | | | | | | | | | +| | | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | | +| Second MAC-es PDU of last Subframe | | | | | | | | | | +| | | | | | | | | | | +| Spare bits 7-6 | | | | | | | | | | +| Last MAC-es PDU of last Subframe | | | | | | | | | | +| | | | | | | | | | | +| Spare Extension | | | | | | | | | | +| Payload CRC | | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | | + +Header + +Payload + +Optional Payload + +Figure 11a: E-DCH UL DATA FRAME TYPE 1 structure + +For the description of the fields see subclause 6.2.4. + +When there is an even, including zero, number of DDI + N field pairs for a subframe, then 4 bits padding is used as shown in the figure in order to have the octet aligned structure. + +The *Payload CRC* IE is optional in frames that contain a Payload, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). The *Payload CRC* IE may only be present if the E-DCH UL data frame contains payload. + +#### 6.2.2.3 UL DATA FRAME FOR E-DCH TYPE 2 + +The structure of the E-DCH UL DATA FRAME TYPE 2 is shown in Figure 11b. TYPE 2 frame structure is used when the E-DCH UL DATA FRAME is carrying MAC-is PDUs (TS 25.321 [16]). + +![](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|-----------------------------------------------------------|--------------------|---|---------------------------------|---|---|---|----|---------------| +| Header CRC | | | | | | | FT | Frame header | +| Header CRC (cont) | | | FSN | | | | | | +| Spare bits 7-6 | UL Mux info | | Number of subframes | | | | | | +| CFN | | | | | | | | | +| User Buffer Size (UB Size) | | | | | | | | | +| User Buffer Size (UB Size) cont | | | | | | | | | +| UB Size cont | Spare bits 5-6 | | Nr of MAC-is SDU in frame | | | | | | +| Nr of MAC-is SDU in frame(cont) | | | | | | | | | +| Spare | N of HARQ Retransm | | 1 st Subframe number | | | | | | +| N of MAC-is PDUs | | | Spare bits 3-0 | | | | | | +| Spare | N of HARQ Retransm | | 2nd Subframe number | | | | | | +| N of MAC-is PDUs | | | Spare bits 3-0 | | | | | | +| | | | | | | | | | +| Spare | N of HARQ Retransm | | Last Subframe number | | | | | | +| N of MAC-is PDUs | | | Spare bits 3-0 | | | | | | +| MAC-is PDU descriptor of 1st MAC-is PDU of 1st subframe | | | | | | | | | +| MAC-is PDU descriptor of 2nd MAC-is PDU of 1st subframe | | | | | | | | | +| | | | | | | | | | +| MAC-is PDU descriptor of last MAC-is PDU of 1st subframe | | | | | | | | | +| | | | | | | | | | +| MAC-is PDU descriptor of 1st MAC-is PDU of last subframe | | | | | | | | | +| | | | | | | | | | +| MAC-is PDU descriptor of last MAC-is PDU of last subframe | | | | | | | | | +| First MAC-is PDU of first subframe | | | | | | | | Frame Payload | +| Second MAC-is PDU of first subframe | | | | | | | | | +| | | | | | | | | | +| Last MAC-is PDU of first subframe | | | | | | | | | +| | | | | | | | | | +| First MAC-is PDU of last subframe | | | | | | | | | +| | | | | | | | | | +| Last MAC-is PDU of last subframe | | | | | | | | | +| Spare Extension | | | | | | | | | +| Payload CRC | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | + +Optional Frame Payload + +Figure 11b: E-DCH UL DATA FRAME TYPE 2 structure + +For the description of the fields see subclause 6.2.4. + +The *Payload CRC* IE is optional in frames that contain a Payload, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). The *Payload CRC* IE may only be present if the E-DCH UL data frame contains payload. + +### 6.2.3 DL DATA FRAME + +The structure of the DL DATA FRAME is shown in figure 12. + +![](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +|------------------------------|-------------|------------------|-------------|-------------|-------------|-------------|-------------|-------------------------|--| +| Header CRC | | | | | | | FT | Header | | +| CFN | | | | | | | | | | +| Spare bits 7-6 | | TFI of first DCH | | | | | | | | +| Spare bits 7-6 | | TFI of last DCH | | | | | | | | +| First TB of first DCH | | | | | | | | Payload | | +| First TB of first DCH (cont) | | | | | | Pad | | | | +| Last TB of first DCH | | | | | | | | | | +| Last TB of first DCH (cont) | | | | | | | Pad | | | +| First TB of last DCH | | | | | | | | | | +| First TB of last DCH (cont) | | | | | | Pad | | | | +| Last TB of last DCH | | | | | | | | | | +| Last TB of last DCH (cont) | | | | | | Pad | | | | +| New IE fl 7(E) | New IE fl 6 | New IE fl 5 | New IE fl 4 | New IE fl 3 | New IE fl 2 | New IE fl 1 | New IE fl 0 | | | +| Spare bits 7-1 | | | | | | | CLTD-R | | | +| Spare Extension | | | | | | | | Optional Payload | | +| Payload CRC | | | | | | | | | | +| Payload CRC (cont) | | | | | | | | | | + +Figure 12: DL DATA FRAME structure + +Bit 0 of New IE Flags in DL DATA FRAME structure indicates if CLTD-R is present (1) or not (0) in the octet following the *New IE Flags* IE. Bits 1 through 6 of New IE Flags in DL DATA FRAME shall be set to 0. + +Field length of *Spare Extension* IE in DL DATA FRAME is 0-30 octets. + +For the description of the fields see subclause 6.2.4. + +There are as many TFI fields as number of DCH multiplexed in the same transport bearer. + +The DCHs in the frame structure are ordered from the lower DCH id ('first DCH') to the higher DCH id ('last DCH'). + +The size and the number of TBs for each DCH are defined by the correspondent TFI. + +If the TB does not fill an integer number of bytes, then bit padding is used as shown in the figure in order to have the octet aligned structure (ex: a TB of 21 bits requires 3 bits of padding). + +The *Payload CRC* IE is optional, i.e. the whole 2 bytes field may or may not be present in the frame structure (this is defined at the setup of the transport bearer). + +### 6.2.4 Coding of information elements in data frames + +#### 6.2.4.1 Header CRC + +**Description:** Result of the CRC applied to the remaining part of the header, i.e. from bit 0 of the first byte (the *FT IE*) to the bit 0 (included) of the last byte of the header (not including the *Header CRC Cont* four bits), with one of the + +corresponding generator polynomials: + +$G(D) = D^7 + D^6 + D^2 + 1$ for the 7 bit header CRC, + +$G(D) = D^{11} + D^9 + D^8 + D^2 + D + 1$ for the 11 bit header CRC. + +See subclause 7.2. + +**Field Length:** 7 bits. 11 bits for UL Data Frame for E-DCH. + +#### 6.2.4.2 Frame Type (FT) + +**Description:** Describes if it is a control frame or a data frame. + +**Value range:** {0=data, 1=control}. + +**Field Length:** 1 bit. + +#### 6.2.4.3 Connection Frame Number (CFN) + +**Description:** Indicator as to which radio frame the first data was received on uplink or shall be transmitted on downlink. See TS 25.401 [2]. For E-DCH the Connection Frame Number shall indicate the radio frame when the HARQ process correctly decoded the data. + +For E-DCH apart from reordering purposes, CFN (and Subframe number) can be used for dynamic delay measurements. + +**Value range:** {0-255}. + +**Field length:** 8 bits. + +#### 6.2.4.4 Transport Format Indicator (TFI) + +**Description:** TFI is the local number of the transport format used for the transmission time interval. For information about what the transport format includes see TS 25.302 [3]. + +**Value range:** {0-31}. + +**Field length:** 5 bits. + +#### 6.2.4.5 Quality Estimate (QE) + +**Description:** The quality estimate is derived from the transport channel BER [FDD - or physical channel BER.] + +[FDD - If the DCH FP frame includes TB's for the DCH which was indicated as "selected" with the *QE-selector* IE in the control plane (TS 25.433 [4] TS 25.423 [6]), then the QE is the transport channel BER for the selected DCH. If no transport channel BER is available the QE is the physical channel BER.] + +[FDD - If the value of the *QE-Selector* IE equals "non-selected" for all DCHs in the DCH FP frame, then the QE is the physical channel BER.] + +[TDD - If no transport channel BER is available, then the QE shall be set to 0. This is in particular the case when no transport blocks have been received. The value of QE will be ignored by the RNC in this case.] + +The quality estimate shall be set to the transport channel BER [FDD - or physical channel BER] and be measured in the units TrCh\_BER\_LOG [FDD - and PhCh\_BER\_LOG respectively] (see TS 25.133 [7] and TS 25.123 [8]). The quality estimate is needed in order to select a transport block when all CRC indications are showing bad (or good) frame. The UL outer loop power control may also use the quality estimate. + +**Value range:** {0-255}. + +**Granularity:** 1. + +**Field length:** 8 bits. + +#### 6.2.4.6 Transport Block (TB) + +**Description:** A block of data to be transmitted or received over the air interface. The transport format indicated by the TFI describes the transport block length and transport block set size. See TS 25.302 [3]. + +**Field length:** The length of the TB is specified by the TFI. + +#### 6.2.4.7 CRC indicator (CRCI) + +**Description:** Indicates the correctness/incorrectness of the TB CRC received on the Uu interface. For every transport block included in the data frame a CRCI bit will be present, irrespective of the presence of a TB CRC on the Uu interface. If no CRC was present on the Uu for a certain TB, the corresponding CRCI bit shall be set to "0". + +**Value range:** {0=Correct, 1=Not Correct}. + +**Field length:** 1 bit. + +#### 6.2.4.8 Payload CRC + +**Description:** CRC for the payload. This field is optional. It is the result of the CRC applied to the remaining part of the payload, i.e. from the bit 7 of the first byte of the payload to the bit 0 of the byte of the payload before the *Payload CRC* IE, with the corresponding generator polynomial: + $G(D) = D^{16} + D^{15} + D^2 + 1$ . See clause 7.2. + +**Field length:** 16 bits. + +#### 6.2.4.9 Spare Extension + +**Description:** Indicates the location where new IEs can in the future be added in a backward compatible way. + +**Field length:** 0-32 octets. + +#### 6.2.4.10 Subframe Number + +**Description:** Indicates the subframe number in which the payload was received. Apart from reordering purposes, Subframe number (and CFN) can be used for dynamic delay measurements. [3.84 Mcps TDD, 7.68 Mcps TDD – This will always be set to "0".][1.28 Mcps TDD – This will be set to {0-1}.] + +**Value range:** {0-4} + +**Field length:** 3 bits. + +#### 6.2.4.11 Number of HARQ Retransmissions, NHR + +**Description:** Indicates the number of HARQ retransmissions used for successful decoding of the payload, or in case of HARQ decoding failure the number of HARQ retransmissions that were used at the time when the HARQ decoding failure was detected. The value 13 indicates that the actual number of retransmissions is inappropriate as input to the outer loop power control. The value 15 indicates that the Node B could not calculate the number of HARQ retransmissions. + +**Value range:** {0-15} + +Value {12}: Used for indicating that the number of HARQ retransmissions was 12 or higher. + +Value {13}: Used for indicating that the number of HARQ retransmissions shall not be used by the outer loop power control + +Values {14}: Reserved in this user plane revision. Shall be ignored by the receiver. + +Value {15}: Used for indicating that the number of HARQ retransmissions is unknown. + +**Field length:** 4 bits. + +#### 6.2.4.12 Number of Subframes + +**Description:** The *Number of Subframes* field indicates how many subframes that follows in the frame. [TDD – This will always be set to "1".] + +Note: A subframe has both a header portion and a payload portion in the frame. + +**Value range:** {1-16} + +The binary coding is derived from the value minus 1. E.g. value 1 is coded as binary “0000” and value 16 is coded as binary “1111”. + +Values {11, 12, 13, 14, 15, 16}: Reserved in this user plane revision. Shall be ignored by the receiver. + +**Field length:** 4 bits. + +#### 6.2.4.13 Number of MAC-es PDUs + +**Description:** Indicates the number of MAC-es PDUs in the user data frame in the payload part for the corresponding subframe number. + +**Value range:** {0-15} + +**Field length:** 4 bits. + +#### 6.2.4.14 Data Description Indicator, DDI + +**Description:** The *Data Description Indicator* is mapped directly from the DDI field received over the Uu. + +**Field length:** 6 bits. + +#### 6.2.4.15 Number of MAC-d PDUs, N + +**Description:** The *Number of MAC-d PDUs* is mapped directly from the N field received over the Uu. + +**Field length:** 6 bits. + +#### 6.2.4.16 FSN – Frame Sequence Number + +**Description:** The 4-bit *Frame Sequence Number* is incremented (modulo 16) for each transmitted data frame. Each flow generates its own Frame Sequence. [FDD – In case E-DCH UL flow multiplexing mode is used for secondary E-DCH, Node B shall set the value per carrier.] + +**Value range:** {0..15}. + +**Granularity:** 1. + +**Field length:** 4 bits. + +#### 6.2.4.17 Number of MAC-is PDUs + +**Description:** Indicates the number of MAC-is PDUs in the user data frame in the payload part for the corresponding subframe number. + +**Value range:** {0-15} + +**Field length:** 4 bits. + +#### 6.2.4.18 User Buffer size + +**Description:** Indicates the total size of the UL DATA FRAME TYPE 2 in octets + +**Value range:** {0-262 140}. + +**Field length:** 18 bits. + +#### 6.2.4.19 Number of MAC-is SDU in frame + +**Description:** Total number of MAC-is SDUs in all MAC-is PDUs in the UL DATA FRAME TYPE 2. + +**Value range:** {0-4095}. + +**Field length:** 12 bits. + +#### 6.2.4.20 MAC-is PDU descriptor + +**Description:** The *MAC-is PDU descriptor* contains the Length (L), Logical channel identifier (LCH-ID) and Flag (F) fields mapped directly from the "MAC-i Header n" field ( $n > 0$ ) received over the Uu (TS 25.321 [16]). + +**Field length:** variable; length of *MAC-is PDU descriptor* in octets = $2 \times$ number of MAC-is SDU contained in the corresponding MAC-is PDU as described in TS 25.321 [16]. + +#### 6.2.4.21 UL Multiplexing Information (UL Mux Info)[FDD] + +**Description:** Applicable to Multi Cell E-DCH operation in E-DCH UL flow multiplexing mode. Indicates the frequency of the cell in which the MAC-i frame was received - primary UL frequency or secondary UL frequency. + +Primary UL frequency Value = "0" + +Secondary UL frequency Value = "1" + +In separate Iub transport bearer mode or non Multi Cell E-DCH operation Value = "0" shall be used, ignored by the receiver + +**Value range:** {0-3}. + +Values {2, 3}: Reserved in this user plane revision. Shall be ignored by the receiver. + +**Field length:** 2 bits. + +#### 6.2.4.22 UL CLTD Removal (CLTD-R)[FDD] + +**Description:** Indicator of the removal of UL CLTD + +**Value range:** {0= UL CLTD not relevant, 1= UL CLTD Removal}. + +**Field length:** 1 bit. + +## 6.3 Control frames + +### 6.3.1 Introduction + +Control frames are used to transport control information between SRNC and Node B. + +On the uplink, these frames are not combined – all frames are passed transparently from Node B to SRNC. On the downlink, the same control frame is copied and sent transparently to all the Node Bs from the SRNC. + +The structure of the control frames is shown in the figure 13. + +![Diagram showing the general structure of control frames. It includes a bit layout from 0 to 7, a detailed header structure, and a simplified header and payload view.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +| | | | | | | | | +|----------------------------|---|---|---|---|---|---|----| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| Frame CRC | | | | | | | FT | +| Control Frame Type | | | | | | | | +| Control Information | | | | | | | | +| Control Information (cont) | | | | | | | | +| Spare Extension | | | | | | | | + +| | +|---------------------------------| +| Header | +| Payload
(variable
length) | + +Diagram showing the general structure of control frames. It includes a bit layout from 0 to 7, a detailed header structure, and a simplified header and payload view. + +**Figure 13: General structure of the control frames** + +*Control Frame Type* IE defines the type of the control frame. + +The structure of the header and the payload of the control frames is defined in the following subclauses. + +### 6.3.2 Header structure of the control frames + +#### 6.3.2.1 Frame CRC + +**Description:** It is the result of the CRC applied to the remaining part of the frame, i.e. from bit 0 of the first byte of the header (the *FT* IE) to bit 0 of the last byte of the payload, with the corresponding generator polynomial: $G(D) = D^7+D^6+D^2+1$ . See subclause 7.2. + +**Field Length:** 7 bits. + +#### 6.3.2.2 Frame Type (FT) + +**Description:** Describes if it is a control frame or a data frame. + +**Value range:** {0=data, 1=control}. + +**Field Length:** 1 bit. + +#### 6.3.2.3 Control Frame Type + +**Description:** Indicates the type of the control information (information elements and length) contained in the payload. + +**Value:** The values are defined in table 1. + +**Table 1** + +| Control frame type | Coding | +|----------------------------------|-----------| +| OUTER LOOP POWER CONTROL | 0000 0001 | +| TIMING ADJUSTMENT | 0000 0010 | +| DL SYNCHRONISATION | 0000 0011 | +| UL SYNCHRONISATION | 0000 0100 | +| Reserved Value | 0000 0101 | +| DL NODE SYNCHRONISATION | 0000 0110 | +| UL NODE SYNCHRONISATION | 0000 0111 | +| RX TIMING DEVIATION | 0000 1000 | +| RADIO INTERFACE PARAMETER UPDATE | 0000 1001 | +| TIMING ADVANCE | 0000 1010 | +| TNL CONGESTION INDICATION | 0000 1011 | + +**Field length:** 8 bits. + +The "Reserved Value" for the *Control Frame Type* IE shall not be used by the SRNC. A control frame whose *Control Frame Type* IE is set to the "Reserved Value" shall be ignored by the Node B. + +### 6.3.3 Payload structure and information elements + +#### 6.3.3.1 TIMING ADJUSTMENT + +##### 6.3.3.1.1 Payload structure + +Figure 14 shows the structure of the payload when control frame is used for the timing adjustment. + +![](24c9e038a791677ed33100667b64f7e6_img.jpg) + +| | | | | | | | | | +|-----------------|---|---|---|---|---|---|---|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| CFN | | | | | | | | | +| ToA | | | | | | | | | +| ToA (cont) | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +Figure 14: Structure of the payload for the TIMING ADJUSTMENT control frame + +##### 6.3.3.1.2 CFN + +**Description:** The CFN value is extracted from the corresponding DL DATA FRAME. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.1.3 Time of Arrival (ToA) + +**Description:** Time difference between the arrival of the DL frame with respect to ToAWE (based on the CFN value in the frame). + +**Value range:** {-1280, +1279.875 msec}. + +**Granularity:** 125 $\mu$ s. + +**Field length:** 16 bits. + +##### 6.3.3.1.4 Spare Extension + +**Description:** Indicates the location where new IEs can in the future be added in a backward compatible way. + +**Field length:** 0-32 octets. + +#### 6.3.3.2 DL SYNCHRONISATION + +##### 6.3.3.2.1 Payload structure + +Figure 15 shows the structure of the payload when control frame is used for the user plane synchronisation. + +![](b0b5357ee0f4d1a974e29c3733a52d60_img.jpg) + +| | | | | | | | | | +|-----------------|---|---|---|---|---|---|---|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| CFN | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +Figure 15: Structure of the payload for the DL SYNCHRONISATION control frame + +##### 6.3.3.2.2 CFN + +**Description:** The CFN value is the target CFN and used to calculate ToA. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.2.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +#### 6.3.3.3 UL SYNCHRONISATION + +##### 6.3.3.3.1 Payload structure + +Figure 16 shows the structure of the payload when the control frame is used for the user plane synchronisation. + +![](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +| | | | | | | | | | +|-----------------|---|---|---|---|---|---|---|-----------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| CFN | | | | | | | | | +| ToA | | | | | | | | | +| ToA (cont) | | | | | | | | | +| Spare Extension | | | | | | | | 0-32bytes | + +**Figure 16: Structure of the UL SYNCHRONISATION control frame** + +##### 6.3.3.3.2 CFN + +**Description:** The CFN value is extracted from the corresponding DL SYNCHRONISATION control frame. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.3.3 Time of Arrival (ToA) + +The *ToA* IE is described in subclause 6.3.3.1.3. + +##### 6.3.3.3.4 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +#### 6.3.3.4 OUTER LOOP POWER CONTROL [FDD, 1.28Mcps TDD] + +##### 6.3.3.4.1 Payload structure + +Figure 17 shows the structure of the payload when control frame is used for the UL outer loop power control. + +![](278c76ad60393fb4ccbc06a485230a4c_img.jpg) + +| | | | | | | | | | +|----------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| UL SIR TARGET | | | | | | | | | +| New
IE fl
7(E) | New
IE fl 6 | New
IE fl 5 | New
IE fl 4 | New
IE fl 3 | New
IE fl 2 | New
IE fl 1 | New
IE fl 0 | | +| Spare bits 7-2 | | | | | | UL Mux Infor | | | +| Spare Extension | | | | | | | | 0-30 bytes | + +**Figure 17: Structure of the payload for OUTER LOOP PC control frame** + +Bit 0 of New IE Flags in OUTER LOOP POWER CONTROL indicates if the UL Mux Info is present (1) or not present (0) in the byte following the *New IE Flags* IE. + +Bits 1 through 6 of New IE Flags in OUTER LOOP POWER CONTROL shall be set to 0. + +##### 6.3.3.4.2 SIR Target + +**Description:** Value (in dB) of the SIR target to be used by the UL inner loop power control. + +SIR Target is given in the unit UL\_SIR\_TARGET where: + +| | | +|---------------------|----------------------| +| UL_SIR_TARGET = 000 | SIR Target = -8.2 dB | +| UL_SIR_TARGET = 001 | SIR Target = -8.1 dB | +| UL_SIR_TARGET = 002 | SIR Target = -8.0 dB | +| ... | | +| UL_SIR_TARGET = 254 | SIR Target = 17.2 dB | +| UL_SIR_TARGET = 255 | SIR Target = 17.3 dB | + +**Value range:** {-8.2...17.3 dB}. + +**Granularity:** 0.1 dB. + +**Field length:** 8 bits. + +##### 6.3.3.4.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +##### 6.3.3.4.4 UL Mux Info + +The *UL Mux Info* IE is described in subclause 6.2.4.21. + +#### 6.3.3.5 DL NODE SYNCHRONISATION + +##### 6.3.3.5.1 Payload structure + +Figure 18 shows the structure of the payload for the DL NODE SYNCHRONISATION control frame. + +![](eb2ecad845f6639684b50f51a346cec9_img.jpg) + +| | | | | | | | | | +|-----------------|----------|----------|----------|----------|----------|----------|----------|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| T1 | | | | | | | | | +| T1 (cont) | | | | | | | | | +| T1 (cont) | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +**Figure 18: Structure of the payload for the DL NODE SYNCHRONISATION control frame** + +##### 6.3.3.5.2 T1 + +**Description:** RNC specific frame number (RFN) that indicates the time when RNC sends the frame through the SAP to the transport layer. + +**Value range:** As defined in subclause 6.3.3.6.2. + +**Field length:** 24 bits. + +##### 6.3.3.5.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +#### 6.3.3.6 UL NODE SYNCHRONISATION + +##### 6.3.3.6.1 Payload structure + +The payload of the UL NODE SYNCHRONISATION control frames is shown in figure 19. + +![](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|-----------------|---|---|---|---|---|---|---|------------| +| T1 | | | | | | | | | +| T1 (cont) | | | | | | | | | +| T1 (cont) | | | | | | | | | +| T2 | | | | | | | | | +| T2 (cont) | | | | | | | | | +| T2 (cont) | | | | | | | | | +| T3 | | | | | | | | | +| T3 (cont) | | | | | | | | | +| T3 (cont) | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +Figure 19: Structure of the payload for UL NODE SYNCHRONISATION control frame + +##### 6.3.3.6.2 T1 + +**Description:** T1 timer is extracted from the correspondent DL NODE SYNCHRONISATION control frame. + +**Value range:** {0-40959.875 ms}. + +**Granularity:** 0.125 ms. + +**Field length:** 24 bits. + +##### 6.3.3.6.3 T2 + +**Description:** Node B specific frame number (BFN) that indicates the time when Node B received the correspondent DL NODE SYNCHRONISATION control frame through the SAP from the transport layer. + +**Value range:** {0-40959.875 ms}. + +**Granularity:** 0.125 ms. + +**Field length:** 24 bits. + +##### 6.3.3.6.4 T3 + +**Description:** Node B specific frame number (BFN) that indicates the time when Node B sends the frame through the SAP to the transport layer. + +**Value range:** {0-40959.875 ms}. + +**Granularity:** 0.125 ms. + +**Field length:** 24 bits. + +##### 6.3.3.6.5 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +#### 6.3.3.7 RX TIMING DEVIATION [3.84 Mcps and 7.68Mcps TDD] + +##### 6.3.3.7.1 Payload structure + +Figure 20 shows the structure of the payload when the control frame is used for the Rx timing deviation. + +![](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +| | | | | | | | | +|------------------------------------------------------------|-------------|-------------|-------------|-------------|---------------|----------------------------|-------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| CFN | | | | | | | | +| Rx Timing Deviation | | | | | | | | +| New IE fl 7(E) | New IE fl 6 | New IE fl 5 | New IE fl 4 | New IE fl 3 | New IE fl 2 | New IE fl 1 | New IE fl 0 | +| Spare bits 7-2 for 3.84Mcps
Spare bits 7-3 for 7.68Mcps | | | | | E-RUC CH flag | Rx Timing Deviation (cont) | | +| Spare Extension | | | | | | | | + +0-30 bytes + +**Figure 20: Structure of the payload for RX TIMING DEVIATION control frame** + +Bit 0 of New IE Flags in RX TIMING DEVIATION CONTROL FRAME indicates if the extended bits of the Rx Timing Deviation are present (1) or not present (0) in the byte (bit 0 for 3.84 Mcps TDD, bits 0 and 1 for 7.68 Mcps TDD) following the *New IE Flags* IE. + +Bit 1 of New IE Flags in RX TIMING DEVIATION CONTROL FRAME indicates if the E-RUCCH Flag is present (1) or not present (0) in the byte (bit 1 for 3.84 Mcps TDD, bit 2 for 7.68 Mcps TDD) following the *New IE Flags* IE. + +Bits 2 through 6 of New IE Flags in RX TIMING DEVIATION CONTROL FRAME shall be set to 0. + +##### 6.3.3.7.2 Rx Timing Deviation [3.84 Mcps TDD] + +**Description:** Measured Rx Timing deviation as a basis for timing advance. + +**Value range:** {-1024, ..., +1023 chips}. + +$$\{N * 4 - 256\} \text{ chips} \leq \text{RxTiming Deviation} < \{(N+1) * 4 - 256\} \text{ chips}$$ + +With N = 0, 1, ..., 127 + +$$\{(N-128)*4 - 1024\} \text{ chips} \leq \text{Rx Timing Deviation} < \{(N-127)*4 - 1024\} \text{ chips}$$ + +With N = 128, 129, ..., 319 + +$$\{N*4 - 1024\} \text{ chips} \leq \text{Rx Timing Deviation} < \{(N+1)*4 - 1024\} \text{ chips}$$ + +With N = 320, 321, ..., 511 + +**Granularity:** 4 chips. + +**Field length:** 9 bits. The least significant 8 bits are contained in the RX timing deviation field and the most significant bit is contained in the RX timing deviation (continuation) field. + +##### 6.3.3.7.2A Rx Timing Deviation [7.68 Mcps TDD] + +**Description:** Measured Rx Timing deviation as a basis for timing advance. + +**Value range:** {-2056, ..., +2055} chips + +$$\{N*4 - 2056\} \text{ chips} \leq \text{RxTiming Deviation} < \{(N+1)*4 - 2056\} \text{ chips}$$ + +With N = 0, 1, ..., 1027 + +**Granularity:** 4 chips. + +**Field length:** 10 bits. The least significant 8 bits are contained in the RX timing deviation field and the most significant 2 bits are contained in the RX timing deviation (continuation) field. + +##### 6.3.3.7.2B E-RUCCH Flag + +**Description:** Indicates whether the timing deviation is derived from a conventional E-RUCCH (carrying Scheduling Information) reception or a TA Request reception. + +**Value range:** {0 conventional E-RUCCH reception, 1 TA Request reception} + +**Field length:** 1 bit. + +##### 6.3.3.7.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +Field length of *Spare Extension* IE in RX TIMING DEVIATION CONTROL FRAME is 0-30 octets. + +##### 6.3.3.7.4 CFN + +**Description:** The CFN value in this control frame is the CFN when the RX timing deviation was measured. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.7.5 New IE Flags + +**Description:** The *New IE Flags* IE is only present if at least one new IE is present. The *New IE Flags* IE contains flags indicating which new IEs that are present following the *New IE Flags* IE. The last bit position of the *New IE Flags* IE is used as the Extension Flag to allow the extension of the *New IE Flags* IE in the future. Extension octets of the *New IE Flags* IE shall follow directly after the first octet of the *New IE Flags* IE. When an extension octet of the *New IE Flags* IE is present, then all previous extension octets of the *New IE Flags* IE and the *New IE Flags* IE shall also be present, even if they have all their flag bits indicating no presence of their respective new IEs. + +###### Value range: + +Bit 0-6 of each octet: Indicates if a new IE is present (1) or not present (0) in the bytes following the *New IE Flags* IE. The meaning of each bit is explained in the corresponding DATA FRAME subclause; + +Bit 7 of each octet: Indicates if an extension octet of the *New IE Flags* IE follows (1) or not (0). + +**Field length:** 1 – 31 octets. + +#### 6.3.3.8 DSCH TFCI SIGNALLING [FDD] + +##### 6.3.3.8.1 Payload structure + +Void. + +##### 6.3.3.8.2 TFCI (field 2) + +Void. + +##### 6.3.3.8.3 Spare Extension + +Void. + +##### 6.3.3.8.4 CFN + +Void. + +#### 6.3.3.9 RADIO INTERFACE PARAMETER UPDATE [FDD] + +##### 6.3.3.9.1 Payload structure + +The figure 22 shows the structure of the payload when the control frame is used for signalling radio interface parameter updates. + +![](409498e57b1f988b2b604d12cd997002_img.jpg) + +| | | | | | | | | +|----------------------------------------|--------------------------------------------------------------|---------------|----------|----------|----------|----------|----------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| Radio Interface Parameter Update Flags | | | | | | | | +| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| CRN | | | | | | | | +| Spare bits 7-6 | | DPC Mode | TPC PO | | | | | +| Multiple RL sets Indicator | Multiple RL Sets Indicator on the secondary uplink frequency | Reserved Bits | | | | | | +| Spare | Reserved Bits | | | | | | | +| Spare | MAX UE TX POW | | | | | | | +| Spare Extension | | | | | | | | + +0-29 bytes + +**Figure 22: Structure of the payload for the RADIO INTERFACE PARAMETER UPDATE control frame** + +##### 6.3.3.9.2 Radio Interface Parameter Update flags + +**Description:** Contains flags indicating which information is valid in this control frame. + +###### **Value range:** + +Bit 0: Indicates if the 3rd byte of the control frame payload contains a valid CFN (1) or not (0); + +Bit 1: Indicates if the 4th byte (bits 0-4) of the control frame payload contains a valid TPC PO (1) or not (0); + +Bit 2: Indicates if the 4th byte (bit 5) of the control frame payload contains a valid DPC mode (1) or not (0); + +Bit 3: Reserved bit; + +Bit 4: Reserved bit; + +Bit 5: Indicates if the 5th byte (bit 7) of the control frame payload contains a valid Multiple RL Sets Indicator (1) or not (0); + +Bit 6: Indicates if the 7th byte (bits 0-6) of the control frame payload contains a valid Maximum UE TX Power (1) or not (0); + +Bit 7: Indicates if the 5th byte (bit 6) of the control frame payload contains a valid Multiple RL Sets Indicator on the secondary uplink frequency (1) or not (0); + +Bit 8-15: Set to (0): reserved in this user plane revision. Any indicated flags shall be ignored by the receiver. + +Reserved bits shall be set to 0 by the SRNC and ignored by the Node B. + +**Field length:** 16 bits. + +##### 6.3.3.9.3 TPC Power Offset (TPC PO) + +**Description:** Power offset to be applied in the DL between the DPDCH information and the TPC bits on the DPCCH as specified in the clause 5.2 of TS 25.214 [12]. + +**Value range:** {0-7.75 dB}. + +**Granularity:** 0.25 dB. + +**Field length:** 5 bits. + +##### 6.3.3.9.4 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +##### 6.3.3.9.4A CFN + +**Description:** The CFN value indicates when the presented parameters shall be applied. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.9.5 DPC Mode + +**Description:** DPC mode to be applied in the UL. + +**Value range:** {0,1}. + +The DPC mode shall be applied as specified in TS 25.214 [12]. + +**Field length:** 1 bit. + +##### 6.3.3.9.6 TFCI Power Offset (TFCI PO) + +Void. + +##### 6.3.3.9.7 TFCI Power Offset for primary cell (TFCI PO\_primary) + +Void. + +##### 6.3.3.9.8 Multiple RL Sets Indicator + +**Description:** Multiple RL Sets Indicator indicates whether the UE has several RL Sets or not. + +**Value range:** {0=UE has only one RL Set, 1=UE has several RL Sets}. + +**Field length:** 1 bit. + +##### 6.3.3.9.9 Maximum UE TX Power + +**Description:** The Maximum UE TX Power is the lower of the maximum output power of the UE power class, defined in ref TS 25.101 [14], and the Maximum Allowed UL TX Power that is also sent to the UE, see ref TS 25.331 [15]. + +Maximum UE TX Power is given in the unit MAX\_UE\_TX\_POW where: + +MAX\_UE\_TX\_POW = 00      Maximum UE TX Power = -55 dBm +MAX\_UE\_TX\_POW = 01      Maximum UE TX Power = -54 dBm +MAX\_UE\_TX\_POW = 02      Maximum UE TX Power = -53 dBm +... +MAX\_UE\_TX\_POW = 87      Maximum UE TX Power = 32 dBm +MAX\_UE\_TX\_POW = 88      Maximum UE TX Power = 33 dBm + +**Value range:** {-55..33 dBm}. + +**Granularity:** 1 dBm + +**Field length:** 7 bit + +##### 6.3.3.9.10 Multiple RL Sets Indicator on the secondary uplink frequency + +**Description:** Multiple RL Sets Indicator indicates whether the UE has several RL Sets or not on the secondary uplink frequency. + +**Value range:** {0=UE has only one RL Set, 1=UE has several RL Sets}. + +**Field length:** 1 bit. + +#### 6.3.3.10 TIMING ADVANCE [3.84Mcps and 7.68 Mcps TDD] + +##### 6.3.3.10.1 Payload structure + +Figure 23 shows the structure of the payload when the control frame is used for timing advance. + +![](6c6d2bce2630f62fb3a5345c9ec84f68_img.jpg) + +| | | | | | | | | | +|-----------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| CFN | | | | | | | | | +| TA | | | | | | | | | +| New IE fl 7(E) | New IE fl 6 | New IE fl 5 | New IE fl 4 | New IE fl 3 | New IE fl 2 | New IE fl 1 | New IE fl 0 | | +| Spare bits 7-1 | | | | | | | | TA (cont) | +| Spare Extension | | | | | | | | 0-30 bytes | + +**Figure 23a: Structure of the TIMING ADVANCE control frame for 7.68Mcps TDD** + +![](f1dad78a1f90d19db60771f807c68885_img.jpg) + +| | | | | | | | | | +|-----------------|---|---|---|---|---|---|---|------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| CFN | | | | | | | | | +| TA | | | | | | | | | +| Spare Extension | | | | | | | | 0-32 bytes | + +**Figure 23b: Structure of the TIMING ADVANCE control frame for 3.84Mcps TDD** + +[7.68Mcps TDD - Bit 0 of New IE Flags in TIMING ADVANCE CONTROL FRAME indicates if the extended bits of the TA are present (1) or not present (0) in the byte following the *New IE Flags* IE. Bits 1 through 6 of New IE Flags in TIMING ADVANCE CONTROL FRAME shall be set to 0.] + +##### 6.3.3.10.2 CFN + +**Description:** The CFN value in this control frame is the frame that the timing advance will occur. + +**Value range:** As defined in subclause 6.2.4.3. + +**Field length:** 8 bits. + +##### 6.3.3.10.3 TA [3.84 Mcps] + +**Description:** UE applied UL timing advance adjustment. + +**Value range:** {0-1020 chips}. + +**Granularity:** 4 chips. + +**Field length:** 8 bits. + +##### 6.3.3.10.3A TA [7.68 Mcps] + +**Description:** UE applied UL timing advance adjustment. + +**Value range:** {0-2044 chips}. + +**Granularity:** 4 chips. + +**Field length:** 9 bits. + +##### 6.3.3.10.4 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +[7.68Mcps TDD - Field length of *Spare Extension* IE in TIMING ADVANCE CONTROL FRAME is 0-30 octets]. + +##### 6.3.3.10.5 New IE Flags [7.68Mcps TDD] + +The *New IE Flags* IE is described in subclause 6.3.3.7.5. + +#### 6.3.3.11 TNL CONGESTION INDICATION + +##### 6.3.3.11.1 Payload structure + +Figure 24 shows the structure of the payload when the control frame is used for TNL CONGESTION INDICATION. + +![](09084c793f44a50d7a1558dbb45d317d_img.jpg) + +| | | | | | | | | +|-----------------|----------|----------|----------|----------|----------|-------------------|----------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| Spare bits 7-2 | | | | | | Congestion Status | | +| Spare Extension | | | | | | | | + +0-32 bytes + +**Figure 24: Structure of the TNL CONGESTION INDICATION control frame** + +##### 6.3.3.11.2 Congestion Status + +**Description:** The Congestion Status indicates whether there is transport network congestion or not. + +**Value range:** + +- 0 No TNL congestion +- 1 Reserved for future use. +- 2 TNL Congestion – detected by delay build-up +- 3 TNL Congestion – detected by frame loss + +**Field length:** 2 bits. + +##### 6.3.3.11.3 Spare Extension + +The *Spare Extension* IE is described in subclause 6.3.3.1.4. + +# 7 Handling of Unknown, Unforeseen and Erroneous Protocol Data + +## 7.1 General + +A frame protocol frame with illegal or not comprehended parameter value shall be ignored. Frame protocol frames sent with a CFN in which the radio resources assigned to the associated Iub data port are not available, shall be ignored. + +Frame protocol data frames with CFN value that does not fulfil the requirement set in clause [FDD - 4.2.14 of TS 25.212 [9]] [TDD - 4.2.12 of TS 25.222 [10]], shall be ignored. + +## 7.2 Error detection + +Error detection is provided on frames through a Cyclic Redundancy Check. The length of the CRC for the payload is 16 bits, for the data frame header 7 or 11 bits and for control frames it is 7 bits. + +### 7.2.1 CRC Calculation + +The parity bits are generated by one of the following cyclic generator polynomials: + +$$g_{CRC16}(D) = D^{16} + D^{15} + D^2 + 1$$ + +$$g_{CRC11}(D) = D^{11} + D^9 + D^8 + D^2 + D + 1$$ + +$$g_{CRC7}(D) = D^7 + D^6 + D^2 + 1$$ + +Denote the bits in a frame by $a_1, a_2, a_3, \dots, a_{A_i}$ , and the parity bits by $p_1, p_2, p_3, \dots, p_{L_i}$ . $A_i$ is the length of a protected data and $L_i$ is 16, 11 or 7 depending on the CRC length. + +The encoding is performed in a systematic form, which means that in GF(2), the polynomial for the payload + +$$a_1 D^{A_i+15} + a_2 D^{A_i+14} + \dots + a_{A_i} D^{16} + p_1 D^{15} + p_2 D^{14} + \dots + p_{16} D^1 + p_{16}$$ + +yields a remainder equal to 0 when divided by $g_{CRC16}(D)$ , the polynomial for the data frame header with 11 bit CRC + +$$a_1 D^{A_i+10} + a_2 D^{A_i+9} + \dots + a_{A_i} D^{11} + p_1 D^{10} + p_2 D^9 + \dots + p_{10} D^1 + p_{11}$$ + +yields a remainder equal to 0 when divided by $g_{CRC11}(D)$ and the polynomial for the data frame header with 7 bit CRC and control frame + +$$a_1 D^{A_i+6} + a_2 D^{A_i+5} + \dots + a_{A_i} D^7 + p_1 D^6 + p_2 D^5 + \dots + p_6 D^1 + p_7$$ + +yields a remainder equal to 0 when divided by $g_{CRC7}(D)$ . If $A_i = 0$ , $p_1 = p_2 = p_3 = \dots = p_{L_i} = 0$ . + +#### 7.2.1.1 Relation between input and output of the Cyclic Redundancy Check + +The bits after CRC attachment are denoted by $b_1, b_2, b_3, \dots, b_{B_i}$ , where $B_i = A_i + L_i$ . + +The parity bits for the payload are attached at the end of the frame: + +$$b_k = a_k \quad k = 1, 2, 3, \dots, A_i$$ + +$$b_k = p_{(k-A_i)} \quad k = A_i + 1, A_i + 2, A_i + 3, \dots, A_i + L_i$$ + +The parity bits for the frame header and the control frames are attached at the beginning of the frame: + +$$b_k = p_k \quad k = 1, 2, 3, \dots, L_i$$ + +$$b_k = a_{(k-L_i)} \quad k = L_i + 1, L_i + 2, L_i + 3, \dots, L_i + A_i$$ \ No newline at end of file diff --git a/marked/Rel-18/25_series/25434/raw.md b/marked/Rel-18/25_series/25434/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9c7f079057900a53258e74b21be3bde0365c63b1 --- /dev/null +++ b/marked/Rel-18/25_series/25434/raw.md @@ -0,0 +1,353 @@ + + +# 3GPP TS 25.434 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub interface data transport and transport signalling for Common Transport Channel data streams (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the letters is a red signal wave icon, and below that, the text 'A GLOBAL INITIATIVE' in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|----------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 3.4 Specification Notations ..... | 7 | +| 4 Data Link Layer ..... | 8 | +| 4.1 ATM Transport Option ..... | 8 | +| 4.1.1 Protection Switching at ATM Layer ..... | 8 | +| 4.2 Data Link Layer for IP Transport Option..... | 8 | +| 5 I ub Data Transport for Common Transport Channel Data Streams..... | 8 | +| 5.1 Introduction ..... | 8 | +| 5.2 ATM Transport Option ..... | 9 | +| 5.3 IP Transport Option..... | 9 | +| 6 I ub Transport Signalling Application for Common Transport Channel Data Streams ..... | 10 | +| 6.1 Introduction ..... | 10 | +| 6.2 Transport Signalling in case of ATM Transport Option ..... | 10 | +| 6.3 Transport Signalling in case of IP Transport Option ..... | 10 | +| 7 Signalling Bearer for ALCAP on I ub Interface..... | 10 | +| 7.1 Introduction ..... | 10 | +| 7.2 Signalling Bearer in ATM Transport Option ..... | 11 | +| 7.3 Signalling Bearer in IP Transport Option ..... | 11 | +| 8 Interworking between ATM and IP Transport Options..... | 11 | +| Annex A (informative): Change history..... | 12 | + +# --- 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 shall provide a specification of the UTRAN RNC-Node B (Iub) interface Data Transport and Transport Signalling for Common Transport Channel data streams. + +# 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.363.2 (2000-11): "B-ISDN ATM Adaptation layer specification: Type 2 AAL". +- [2] ITU-T Recommendation I.366.1 (1998-06): "Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2". +- [3] ITU-T Recommendation Q.2630.1 (1999-12): "AAL type 2 signalling protocol (Capability Set 1)". +- [4] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)". +- [5] ITU-T Recommendation Q.2130 (1994-07): "B-ISDN signalling ATM adaptation Layer - Service Specific Coordination Function for Support of Signalling at the User Network Interface (SSCF at UNI)". +- [6] ITU-T Recommendation Q.2150.2 (1999-12): "Signalling transport converter on SSCOP and SSCOPMCE". +- [7] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification". +- [8] ITU-T Recommendation I.630 (1999-02): "ATM protection switching". +- [9] ITU-T Recommendation Q.2630.2 (2000-12): "AAL Type 2 signalling protocol (Capability Set 2)". +- [10] ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing". +- [11] ITU-T Recommendation X.213 (1995-11): "Information Technology - Open Systems Interconnection - Network Service Definition". +- [12] IETF RFC 768, (1980-08): "User Datagram Protocol". +- [13] IETF RFC 2460, (1998-12): "Internet Protocol, Version 6 (IPv6) Specification". +- [14] IETF RFC 791, (1981-09): "Internet Protocol". +- [15] IETF RFC 2474, (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [16] IETF RFC 1661, (1994-07): "The Point-to-Point Protocol (PPP)". +- [17] IETF RFC 1662, (1994-07): "PPP in HDLC-like Framing". + +- [18] IETF RFC 2507, (1999-02): "IP header compression". +- [19] IETF RFC 1990, (1996-08): "The PPP Multilink Protocol (MP)". +- [20] IETF RFC 2686, (1999-09): "The Multi-Class Extension to Multi-Link PPP". +- [21] Void +- [22] 3GPP TS 25.401, "UTRAN Overall Description" +- [23] 3GPP TS 25.426, "UTRAN Iur and Iub Interface Data Transport & Transport Signalling for DCH Data Streams" +- [24] IETF RFC 3153, (2001-08): "PPP Multiplexing". +- [25] IETF RFC 2364, (1998-07): "PPP over AAL5". +- [26] IETF RFC 3031, (2001-01): "Multiprotocol Label Switching Architecture". +- [27] ITU-T Recommendation E.164 (1997-05): "The international public telecommunication numbering plan". +- [28] IETF RFC 3376 (2002-10), "Internet Group Management Protocol, Version 3". +- [29] IETF RFC 3810 (2004-06), "Multicast Listener Discovery Version 2 (MLDv2) for IPv6". +- [30] IETF RFC 3544, (2003-07): "IP Header Compression over PPP". + +# --- 3 Definitions, symbols and abbreviations + +For the purposes of the present document, the following abbreviations apply: + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**ALCAP:** "ALCAP" is a generic name for the transport signalling protocol used to setup and tear down transport bearers. + +**IP UTRAN node:** An UTRAN Node supporting the IP Transport Option + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +| | | +|---------|------------------------------------| +| AAL | ATM Adaption Layer | +| AAL2 | AAL Type 2 | +| ATM | Asynchronous Transfer Mode | +| CPCS | Common Part Convergence Sublayer | +| CPS | Common Part Sublayer | +| DSCH | Downlink Shared Channel | +| FACH | Forward Access Channel | +| FP | Frame Protocol | +| HDLC | High-level Data Link Control | +| HS-DSCH | High Speed Downlink Shared Channel | +| IP | Internet Protocol | +| LC | Link Characteristics | +| PPP | Point-to-Point Protocol | + +| | | +|-------|-----------------------------------------------| +| PT | Path Type | +| RACH | Random Access Channel | +| RNC | Radio Network Controller | +| SAAL | Signalling ATM Adaption Layer | +| SAR | Segmentation And Reassembly | +| SSCF | Service Specific Co-ordination Function | +| SSCOP | Service Specific Connection Oriented Protocol | +| SSCS | Service Specific Convergence Sublayer | +| SSSAR | Service Specific Segmentation And Reassembly | +| STC | Signalling Transport Converter | +| UDP | User Datagram Protocol | +| UMTS | Universal Mobile Telecommunication Network | +| UNI | User-Network Interface | +| USCH | Uplink Shared Channel | +| UTRAN | UMTS Terrestrial Radio Access Network | + +## 3.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. + +# --- 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 [7]. + +### 4.1.1 Protection Switching at ATM Layer + +If redundancy of pathways at ATM layer between RNC and Node B is supported, it shall be implemented using ATM Protection Switching according to ITU-T Recommendation I.630 [8]. + +## 4.2 Data Link Layer for IP Transport Option + +An RNC or Node B supporting IP Transport Option shall support the PPP protocol with HDLC framing (IETF RFC 1661 [16], IETF RFC 1662 [17]). + +NOTE: This does not preclude the single implementation and use of any other L2/L1 protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 [24], IETF RFC 2364 [25]), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 [26]), etc.) fulfilling the UTRAN requirements towards the upper layers. + +An RNC or Node B supporting IP transport option and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [18]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [19], IETF RFC 2686 [20]). In this case, negotiation of header compression (IETF RFC 2507 [18]) over PPP shall be performed via (IETF RFC 3544 [30]). + +# --- 5 Iub Data Transport for Common Transport Channel Data Streams + +## 5.1 Introduction + +This subclause specifies the transport layers that support Common Transport Channel (FACH, RACH, PCH, DSCH, HS-DSCH, USCH [TDD]) data streams. + +There are two options for protocol suites for transport of RACH, FACH, USCH [TDD], DSCH and HS-DSCH Iub data streams: + +- 1) ATM Transport Option +- 2) IP Transport Option + +The following figure 1 shows the protocol stacks of these two options: + +![Figure 1: Protocol stack for the transport of RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH Iub data streams. The diagram shows two protocol stacks connected to a common Radio Network Layer. The left stack is for the ATM Transport Option, and the right stack is for the IP Transport Option.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates two protocol stacks for transporting data streams from the Radio Network Layer. Both stacks share a common Radio Network Layer at the top, which handles FP for RACH, FACH, PCH, DSCH [TDD], HS-DSCH, and USCH [TDD]. + +**Protocol Stack for ATM Transport Option (Left):** + +- Radio Network Layer:** FP for RACH, FACH, PCH, DSCH [TDD], HS-DSCH, USCH [TDD] +- Transport Network Layer:** + - AAL2 SSSAR (I.366.1) + - AAL2 CPS (I.363.2) + - ATM +- PHY** + +**Protocol Stack for IP Transport Option (Right):** + +- Radio Network Layer:** FP for RACH, FACH, PCH, DSCH [TDD], HS-DSCH, USCH [TDD] +- Transport Network Layer:** + - UDP + - IP +- Data Link Layer** +- Physical Layer** + +Figure 1: Protocol stack for the transport of RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH Iub data streams. The diagram shows two protocol stacks connected to a common Radio Network Layer. The left stack is for the ATM Transport Option, and the right stack is for the IP Transport Option. + +**Figure 1: Protocol stack for the transport of RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH Iub data streams** + +## 5.2 ATM Transport Option + +ATM and AAL2 (ITU-T Rec. I.363.2 [1] and ITU-T Rec. I.366.1 [2]) are used at the standard transport layer for Iub RACH, FACH, PCH, DSCH [TDD], USCH [TDD], HS-DSCH data streams. + +The Service Specific Segmentation and Reassembly (SSSAR) sublayer is used for the segmentation and reassembly of AAL2 SDUs (i.e. SSSAR is only considered from ITU-T Recommendation I.366.1 [2]). + +## 5.3 IP Transport Option + +UDP (IETF RFC 768 [12]) over IP shall be supported as the transport for RACH, FACH, PCH, DSCH [TDD], USCH [TDD] and HS-DSCH data streams on Iub Interface. The data link layer is as specified in chapter 4.2 + +An IP UTRAN node shall support IPv6 (IETF RFC 2460 [13]). The support of IPv4 (IETF RFC 791 [14]) is optional. + +NOTE: This does not preclude single implementation and use of IPv4. + +IP dual stack is recommended for the potential transition period from IPv4 to IPv6 in the transport network. + +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 Radio Network Layer on the Iur/Iub interface shall use the NSAP structure. See sub clause 6.1.8.2 of TS 25.401 [22]. + +IP Differentiated Services code point marking (IETF RFC 2474 [15]) 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. + +IP multicast (IETF RFC 3376 [28], IETF RFC 3810 [29]) may be supported for FACH data streams on Iub Interface if the security of RAN will not be compromised. This can be guaranteed in a closed IP based RAN. + +# 6 Iub Transport Signalling Application for Common Transport Channel Data Streams + +## 6.1 Introduction + +This subclause specifies the transport signalling protocol(s) used to establish the user plane transport bearers. The protocol stack is shown in clause 7 (figure 2). + +## 6.2 Transport Signalling in case of ATM Transport Option + +Q.2630.2 as developed by ITU-T [9] is selected as the standard AAL2 signalling protocol for Iub. ITU-T Recommendation Q.2630.2 [9] adds new optional capabilities to ITU-T Recommendation Q.2630.1 [3]. + +Binding ID provided by the radio network layer shall be copied in SUGR parameter of ESTABLISH.request primitive of ITU-T Rec. Q.2630.2 [9]. The binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iub interface in the Node B. + +User Plane Transport bearers are established and in all normal cases released by the ALCAP in the Controlling RNC. The Node B shall initiate release of the user plane transport bearers for the removed common channels that were remaining within the cell when the cell is deleted. + +AAL2 transport layer addressing is based on embedded E.164 (ITU-T Rec. E.164 [27]) or other AESA variants of the NSAP addressing format (ITU-T Rec. E.191 [10], ITU-T Rec. X.213 [11]). Native E.164 addressing (ITU-T Rec. E.164 [27]) shall not be used. + +If there is an AAL2 switching function in the transport network layer of the interface, the Link Characteristics parameter (LC) shall be included in the Establish Request message and in the Modification Request message of AAL2 signalling protocol. + +If there is an AAL2 switching function in the transport network layer of the interface, the Path Type parameter (PT) may be included in the Establish Request message of AAL2 signalling protocol for prioritisation at ATM level. + +If the value in either the Maximum CPS-SDU Bit Rate or the Average CPS-SDU Bit Rate of the Link Characteristics (LC) in AAL2 signalling messages as specified in reference ITU-T Rec. Q.2630.2 [9] is 2048 Kbit/s, it shall be interpreted as bit rate 2048 Kbit/s or higher. + +NOTE: Separation of traffic (e.g. HSDPA) using this modified ITU-T Rec. Q.2630.2 [9] from other traffic is highly recommended. Otherwise the bursty nature of the HSDPA traffic in combination with the unknown traffic volume per connection for bit rates exceeding 2048 Kbit/s may decrease the QoS of all traffic within the same AAL type 2 path. + +## 6.3 Transport Signalling in case of IP Transport Option + +An ALCAP protocol is not required in case both UTRAN Nodes (RNC and Node B) are using the IP Transport Option. + +# 7 Signalling Bearer for ALCAP on Iub Interface + +## 7.1 Introduction + +This subclause specifies the signalling bearer protocol stack which supports the ALCAP. + +## 7.2 Signalling Bearer in ATM Transport Option + +SAAL-UNI is the standard signalling bearer for the AAL Type Signalling protocol (ITU-T Rec. Q.2630.2 [9]) on Iub (ITU-T Rec. Q.2110 [4], ITU-T Rec. Q.2130 [5]). The protocol stack is shown in figure 2. + +![Figure 2: Transport Network Control plane protocol structure on Iub in case of ATM Transport Option. The diagram shows a protocol stack with five layers. From top to bottom: Q.2630.2 (dashed box), STC (Q.2150.2) (solid box), AAL5 SSCS (SSCF-UNI, SSCOP) (solid box), AAL5 Common Part (CPCS / SAR) (dashed box), and PHY (dashed box). The layers are connected by a vertical line with an oval at the top, indicating the interface.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Figure 2: Transport Network Control plane protocol structure on Iub in case of ATM Transport Option. The diagram shows a protocol stack with five layers. From top to bottom: Q.2630.2 (dashed box), STC (Q.2150.2) (solid box), AAL5 SSCS (SSCF-UNI, SSCOP) (solid box), AAL5 Common Part (CPCS / SAR) (dashed box), and PHY (dashed box). The layers are connected by a vertical line with an oval at the top, indicating the interface. + +**Figure 2: Transport Network Control plane protocol structure on Iub in case of ATM Transport Option** + +The signalling transport converter (STC) relevant for Iub is ITU-T Recommendation Q.2150.2 [6]. The AAL5 Common Part contains CPCS and SAR. + +## 7.3 Signalling Bearer in IP Transport Option + +An ALCAP protocol is not required in case of both UTRAN Nodes (RNC and Node B) are using the IP Transport Option. + +# --- 8 Interworking between ATM and IP Transport Options + +An RNC or Node B supporting IP transport option shall provide interworking to an RNC or Node B supporting only ATM transport option. The interworking alternatives are defined in TS 25.426 [23]. \ No newline at end of file diff --git a/marked/Rel-18/25_series/25442/raw.md b/marked/Rel-18/25_series/25442/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ca2d7e8d79d03c98f1ebaf5ae696f00eae933a5f --- /dev/null +++ b/marked/Rel-18/25_series/25442/raw.md @@ -0,0 +1,219 @@ + + +# 3GPP TS 25.442 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN implementation-specific O&M transport (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|---------------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 Implementation Specific O&M Transport..... | 6 | +| 4.1 Requirements..... | 6 | +| 4.2 Routing..... | 6 | +| 4.3 Transport Bearer..... | 7 | +| 4.3.1 ATM Transport Option..... | 7 | +| 4.3.2 IP Transport Option..... | 7 | +| Annex A (informative): Change history..... | 9 | + +# --- 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 transport of implementation specific O&M signalling between Node B and the Management Platform in case that the transport is routed via the RNC. + +# --- 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] Void +- [3] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer Type 5 Specification". +- [4] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM". +- [5] IETF RFC 2684 (1999-09): "Multiprotocol Encapsulation over ATM Adaptation Layer 5". +- [6] IETF RFC 791 (1981-09): "Internet Protocol". +- [7] Void +- [8] 3GPP TS 25.426: "UTRAN Iur and Iub Interface Data Transport&Transport Signalling for DCH". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Logical O&M:** Logical O&M is the signalling associated with the control of logical resources owned by the RNC but physically implemented in Node B. + +**Implementation Specific O&M:** Implementation Specific O&M functions depend on the implementation of the Node B, both for its hardware and software components. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|-----------------------------| +| AAL5 | ATM Adaptation Layer type 5 | +| ATM | Asynchronous Transfer Mode | +| ARP | Address Resolution Protocol | +| RFC | Request For Comment | +| IP | Internet Protocol | + +| | | +|-----|---------------------------| +| O&M | Operation and Maintenance | +| RNC | Radio Network Controller | +| TNL | Transport Network Layer | + +# 4 Implementation Specific O&M Transport + +## 4.1 Requirements + +While this specification only addresses the transport of Node B Implementation Specific O&M signalling, many of the following requirements are derived from generic requirements for O&M of UMTS network elements: + +- Common O&M infrastructure for all network elements. +- Independence from various data link protocols. +- Support of various higher layer protocols and applications. +- Secure transmission. +- No Impact of O&M transport on traffic transport and signalling. +- Re-use of existing transport facilities, i.e. co-existence of Iub and Implementation Specific O&M on the same bearer. + +## 4.2 Routing + +It is the responsibility of the RNC to route Implementation Specific O&M signalling traffic. The traffic exchanged over this signalling link is completely transparent to the RNC. Both RNC and Node B have to support the routing of Implementation specific O&M via the RNC. + +![Diagram illustrating Implementation Specific O&M Transport via RNC. The diagram shows a central RNC connected to two Node Bs (one blue, one yellow) and a Management Platform(s). The RNC contains an RNC O&M block and a Node B Logical O&M block. The Node Bs contain Implementation Specific O&M and Logical O&M blocks. The Management Platform(s) contain Node B Management Model, RNC Management Model, and Node B Management Model blocks. Arrows indicate the flow of Implementation Specific O&M Transport from the Management Platform(s) through the RNC to the Node Bs. The RNC O&M block is connected to the RNC Management Model. The Node B Logical O&M block is connected to the Node B Management Models. The Implementation Specific O&M Transport flows from the Management Platform(s) through the RNC O&M block to the Node Bs. The Logical O&M flows from the Node Bs through the RNC to the Management Platform(s). The Physical bearer is shown at the bottom of the RNC and Node Bs.](47e8c2042061e08a14e012472e9fdbaa_img.jpg) + +The diagram illustrates the architecture for Implementation Specific O&M transport. At the top, a 'Management Platform(s)' box contains three models: 'Node B Management Model' (blue), 'RNC Management Model' (blue), and 'Node B Management Model' (yellow). Below this, a central 'RNC' box (blue) contains an 'RNC O&M' block and a 'Node B Logical O&M' block. The 'RNC O&M' block is connected to the 'RNC Management Model'. The 'Node B Logical O&M' block is connected to both 'Node B Management Model' blocks. On the left, a 'Node B' box (blue) contains 'Implementation Specific O&M' and 'Logical O&M' blocks. On the right, another 'Node B' box (yellow) contains the same two blocks. Arrows show 'Implementation Specific O&M Transport' (blue lines) flowing from the 'Management Platform(s)' through the 'RNC O&M' block to the 'Node Bs'. Green lines represent 'Logical O&M' traffic passing through the 'Node B Logical O&M' block in the RNC. Dashed ovals labeled 'Physical bearer' are shown at the bottom of each Node B and the RNC, indicating the transport medium. The label 'Iub' is placed near the connections between the Node Bs and the RNC. + +Diagram illustrating Implementation Specific O&M Transport via RNC. The diagram shows a central RNC connected to two Node Bs (one blue, one yellow) and a Management Platform(s). The RNC contains an RNC O&M block and a Node B Logical O&M block. The Node Bs contain Implementation Specific O&M and Logical O&M blocks. The Management Platform(s) contain Node B Management Model, RNC Management Model, and Node B Management Model blocks. Arrows indicate the flow of Implementation Specific O&M Transport from the Management Platform(s) through the RNC to the Node Bs. The RNC O&M block is connected to the RNC Management Model. The Node B Logical O&M block is connected to the Node B Management Models. The Implementation Specific O&M Transport flows from the Management Platform(s) through the RNC O&M block to the Node Bs. The Logical O&M flows from the Node Bs through the RNC to the Management Platform(s). The Physical bearer is shown at the bottom of the RNC and Node Bs. + +Figure 1: Implementation Specific O&M Transport via RNC + +## 4.3 Transport Bearer + +An appropriate transport bearer for Implementation Specific O&M should consider the requirements listed in subclause 4.1. IP (IETF RFC 791 [6]) should be the transport mechanism in order to allow a data link independent support of a variety of O&M applications and protocols for the Implementation Specific O&M of the Node B. + +IP datagrams containing O&M signalling have to be carried over the same bearer as Iub. There are two options for the implementation specific O&M signalling bearer in Iub: + +- 1) ATM Transport option +- 2) IP Transport option + +### 4.3.1 ATM Transport Option + +The following figure shows the protocol stack for Implementation Specific O&M transport between Node B and RNC in case of ATM transport option in Iub: + +![Figure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option). The diagram shows two protocol stacks. The left stack is for the RNC and consists of three layers: IP at the top, Data Link Layer in the middle (containing AAL5 and ATM sub-layers), and PHY at the bottom. The right stack is for the Node B and consists of four layers: Implementation Specific O&M at the top, followed by IP, AAL5, ATM, and PHY at the bottom. A horizontal line connects the PHY layers of both stacks, representing the Iub interface.](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg) + +Figure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option). The diagram shows two protocol stacks. The left stack is for the RNC and consists of three layers: IP at the top, Data Link Layer in the middle (containing AAL5 and ATM sub-layers), and PHY at the bottom. The right stack is for the Node B and consists of four layers: Implementation Specific O&M at the top, followed by IP, AAL5, ATM, and PHY at the bottom. A horizontal line connects the PHY layers of both stacks, representing the Iub interface. + +**Figure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option)** + +AAL5 shall be used according to ITU-T Recommendation I.363.5 [3]. + +AAL5 virtual circuits are used to transport the IP packets containing Implementation Specific O&M signalling data between Node B and RNC. Multiple VCs can 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 can be made using O&M or using ATM Inverse ARP according to Classical IP over ATM. + +Classical IP over ATM protocols are used to carry the IP packets over the ATM transport network. Classical IP over ATM is specified in IETF RFC 2225 [4]. Multiprotocol Encapsulation over AAL5 is specified in IETF RFC 2684 [5]. + +### 4.3.2 IP Transport Option + +The following figure shows the protocol stack for Implementation Specific O&M transport between Node B and RNC in case of IP transport option in Iub: + +![Protocol stack diagram for Implementation Specific O&M Transport (IP TNL) between RNC and Node B.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the protocol stack for Implementation Specific O&M Transport (IP TNL) between an RNC and Node B. The RNC stack consists of three layers: IP at the top, Datalink layer in the middle (with an internal IP layer), and PHY at the bottom. The Node B stack consists of four layers: Implementation Specific O&M at the top, IP below it, IP (if tunnelled) below that, Datalink layer below that, and PHY at the bottom. A horizontal line connects the PHY layers of both stacks, indicating a direct physical connection. + +| | | | +|----------------|----------------|-----------------------------| +| IP | | Implementation Specific O&M | +| Datalink layer | IP | IP | +| | Datalink layer | IP (if tunnelled) | +| PHY | PHY | Datalink layer | +| | | PHY | + +RNC                      Node B + +Protocol stack diagram for Implementation Specific O&M Transport (IP TNL) between RNC and Node B. + +**Figure 3: Protocol Stack for Implementation Specific O&M Transport (IP TNL)** + +Implementation specific O&M signalling is conveyed by IP between the Node B and the RNC. IP-in-IP tunneling may be applied when the Iub Transport Network Layer is used. + +IP based Transport Network Layer of Iub is further defined in TS 25.426 [8]. + diff --git a/marked/Rel-18/25_series/25444/raw.md b/marked/Rel-18/25_series/25444/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5e0f8a4eb959c1af06ab640089a210ee43f217a7 --- /dev/null +++ b/marked/Rel-18/25_series/25444/raw.md @@ -0,0 +1,236 @@ + + +# 3GPP TS 25.444 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Iuh data transport (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +- Foreword ..... 4 +- 1 Scope..... 5 +- 2 References..... 5 +- 3 Definitions and abbreviations ..... 5 + - 3.1 Definitions..... 5 + - 3.2 Abbreviations ..... 5 +- 4 Data Link Layer ..... 6 +- 5 Circuit switched domain ..... 6 + - 5.1 Transport Network User Plane without bandwidth efficiency mechanisms..... 6 + - 5.3 Transport Network User Plane with bandwidth efficiency mechanisms ..... 6 + - 5.3.1 General ..... 6 + - 5.3.2 Transport format..... 6 + - 5.3.2.1 UDP ..... 6 + - 5.3.2.2 RTP..... 6 + - 5.3.2.2.1 Transport Format for multiplexing RTP packets ..... 6 +- 6 Packet switched domain..... 8 + - 6.1 Transport network user plane..... 8 +- Annex A (informative): Change history..... 9** + +# --- 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 between the HNB and HNB-GW/CN. + +# --- 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] Void +- [3] Void +- [4] 3GPP TS 25.414: "UTRAN Iu interface data transport and transport signalling". +- [5] Void +- [6] Void +- [7] Void +- [8] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [9] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real-Time Applications". +- [10] Void +- [11] Void +- [12] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [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]. + +## 3.2 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]. + +| | | +|--------|------------------------------| +| CN | Core Network | +| CS | Circuit Switched | +| HNB | Home Node B | +| HNB-GW | Home Node B Gateway | +| IP | Internet Protocol | +| PS | Packet Switched | +| RFC | Request For Comment | +| RTP | Real-Time Transport Protocol | +| UDP | User Datagram Protocol | + +# --- 4 Data Link Layer + +Any data link protocol that fulfils the requirements toward the upper layer may be used. + +# --- 5 Circuit switched domain + +## 5.1 Transport Network User Plane without bandwidth efficiency mechanisms + +Defined in Reference TS 25.414 [4], subclause 5.1.3. + +NOTE: The Transport Network Layer as described in ref TS 25.414 [4] subclause 5.1.3, may be directly between HNB and the CN. + +## 5.3 Transport Network User Plane with bandwidth efficiency mechanisms + +### 5.3.1 General + +Bandwidth efficient transport of Uplink CS data payload PDUs may be supported over bearer transport mechanisms for the Iuh interface, using a bearer transport multiplexing scheme that allows transporting several RTP PDUs of different user plane connections within one packet. + +### 5.3.2 Transport format + +UDP/IP shall be applied on Iuh between HNB and HNB GW as described in TS 25.414 [4] for Iu between RNC and CN, subclause 5.1.3, except as stated below. + +#### 5.3.2.1 UDP + +The path protocol used shall be UDP (IETF RFC 768 [8]). If multiplexing is applied the source UDP port number shall indicate the local termination used to combine the multiplexed packet and the destination UDP port number shall indicate the remote port number where PDUs are demultiplexed. + +#### 5.3.2.2 RTP + +RTP (IETF RFC 1889[9]) shall be applied as described in TS 25.414 [4], subclause 5.1.3.3 and requirements below. + +##### 5.3.2.2.1 Transport Format for multiplexing RTP packets + +Use of multiplexing shall be negotiated between the HNB and HNB-GW. + +Before each multiplexed RTP/codec payload PDU inserted into the UDP/IP packet a Multiplex Header, which identifies the multiplexed packet, shall be inserted. + +| Bits | | | | | | | | Number of Octets | | | | | | | | | +|----------------------------------------------------|--------------------------------------------------------|---|---|---|---|---|---|------------------|------------------|--|--|--|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | +| Source IP, Dest IP, ... | | | | | | | | 20/40 | IP | | | | | | | | +| Source Port, Dest Port=, Length, ... | | | | | | | | 8 | UDP | | | | | | | | +| T=0 | Mux ID = (Destination UDP Port of multiplexed PDU) / 2 | | | | | | | 2 | Multiplex Header | | | | | | | | +| Length Indicator (LI) = n | | | | | | | | 1 | | | | | | | | | +| R | Source ID = (Source UDP Port of multiplexed PDU) / 2 | | | | | | | 2 | | | | | | | | | +| Full RTP packet | | | | | | | | n | RTP header | | | | | | | | +| | | | | | | | | | RTP Payload | | | | | | | | +| Multiplex Header | | | | | | | | 5 | Multiplex Header | | | | | | | | +| Full RTP packet | | | | | | | | m | RTP header | | | | | | | | +| | | | | | | | | | RTP Payload | | | | | | | | +| ... | | | | | | | | | | | | | | | | | + +**Figure 1: UDP/IP Packet with multiplexed RTP payload PDUs** + +The Multiplex Header includes : + +- T bit. + +The field has two possible values. Value 0 shall be used for an uncompressed RTP header, as described in the present sub-clause. Value 1 is FFS. + +- Mux ID, 15 bits. + +For identification of different user plane connections. The value shall be the UDP destination port of the corresponding non-multiplexed RTP PDU packet divided by two (only even numbered ports are used for RTP sessions). + +- Length Indicator (LI), 8 bits, unsigned integer. + +Gives the length of the multiplexed RTP PDU packet (RTP header + RTP) in bytes (the last byte of the RTP PDU is padded to the next byte boundary if necessary). Maximum length is 255 bytes. This LI allows to calculate where the next Multiplex Header for the next multiplexed RTP PDU packet starts. + +- R bit. + +Reserved for future use. Shall be set to 0 by the sending entity and be ignored by the receiving entity. + +- Source ID, 15 bits. + +For identification of the different connections. The value shall be the source UDP port of the corresponding non-multiplexed RTP/codec PDU packet divided by two (only even numbered ports are used for RTP sessions). + +The multiplexed RTP PDU shall be inserted in the IP/UDP packet directly after the corresponding Multiplex Header. The multiplexed RTP packet PDU shall follow the rules defined in IETF RFC 1889 [9] and consists of the full RTP header and the RTP payload. If the multiplexed RTP packet PDU does not end at a byte boundary, then the remaining bits of its last byte shall be padded with zeros. + +The multiplexing method does not limit the number of packets being multiplexed and it is thus the data link layer protocol that defines the maximum frame size. In order to avoid additional delay in the network the packets should not be delayed more than 1 ms to 2 ms, which also effectively limits the number of multiplexed packets and makes the multiplexing-jitter low. + +![Figure 2: Example of multiplexed packet with two RTP frames. The diagram illustrates the structure of a multiplexed packet containing two RTP frames. At the top, two separate packets are shown. The first packet has a header section (IP (20/40 bytes), UDP (8), RTP (12)) and a payload (IuUP frame (9 ...)). A callout box points to the UDP port, labeled 'Dest. & Source UDP Port: xxxx'. The second packet has a similar header section and payload. A callout box points to its UDP port, labeled 'Dest. & Source UDP Port: yyyy'. Below these, the packets are shown being multiplexed. The first packet's header is replaced by a 'Common header' (IP (20/40 bytes), UDP (8)). The UDP port is now a 'Negotiated UDP MUX port.'. The RTP (12) and IuUP frame (9 ...) are preserved. This is followed by a 'MUX (5)' header. The second packet's RTP (12) and IuUP frame (9 ...) are also preserved, followed by another 'MUX (5)' header. The resulting multiplexed packets are labeled '1. MUX packet' and '2. MUX packet'. A double-headed arrow indicates the maximum length of the multiplexed packet is 'max 255 bytes'. Callout boxes point to the UDP ports for the multiplexed packets, labeled 'Dest. & Source UDP Port: xxxx' and 'Dest. & Source UDP Port: yyyy'.](7affafe7362a2d2d072e9d4bf515f0bb_img.jpg) + +Figure 2: Example of multiplexed packet with two RTP frames. The diagram illustrates the structure of a multiplexed packet containing two RTP frames. At the top, two separate packets are shown. The first packet has a header section (IP (20/40 bytes), UDP (8), RTP (12)) and a payload (IuUP frame (9 ...)). A callout box points to the UDP port, labeled 'Dest. & Source UDP Port: xxxx'. The second packet has a similar header section and payload. A callout box points to its UDP port, labeled 'Dest. & Source UDP Port: yyyy'. Below these, the packets are shown being multiplexed. The first packet's header is replaced by a 'Common header' (IP (20/40 bytes), UDP (8)). The UDP port is now a 'Negotiated UDP MUX port.'. The RTP (12) and IuUP frame (9 ...) are preserved. This is followed by a 'MUX (5)' header. The second packet's RTP (12) and IuUP frame (9 ...) are also preserved, followed by another 'MUX (5)' header. The resulting multiplexed packets are labeled '1. MUX packet' and '2. MUX packet'. A double-headed arrow indicates the maximum length of the multiplexed packet is 'max 255 bytes'. Callout boxes point to the UDP ports for the multiplexed packets, labeled 'Dest. & Source UDP Port: xxxx' and 'Dest. & Source UDP Port: yyyy'. + +Figure 2: Example of multiplexed packet with two RTP frames + +# 6 Packet switched domain + +## 6.1 Transport network user plane + +Defined in Ref TS 25.414 [4] subclause 6.1.3. + +NOTE: The Transport Network Layer as described in ref TS 25.414 [4] subclause 6.1.3, may be directly between HNB and the CN. \ No newline at end of file diff --git a/marked/Rel-18/29_series/29122/raw.md b/marked/Rel-18/29_series/29122/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ad601e14cd8a94036f0aff703056f5cb6f8f5045 --- /dev/null +++ b/marked/Rel-18/29_series/29122/raw.md @@ -0,0 +1,26084 @@ + + +# 3GPP TS 29.122 V18.4.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; T8 reference point for Northbound APIs; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above it and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. There is a small red signal wave icon under the 'G'. + +3GPP logo + +Keywords +SCEF, SCS/AS, HTTP + +**3GPP** + +Postal address + +3GPP support office address +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + +**3GPP** + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------|----| +| Foreword..... | 20 | +| 1 Scope..... | 21 | +| 2 References..... | 21 | +| 3 Definitions and abbreviations..... | 23 | +| 3.1 Definitions..... | 23 | +| 3.2 Abbreviations..... | 23 | +| 4 T8 reference point..... | 24 | +| 4.1 Overview..... | 24 | +| 4.2 Reference model..... | 25 | +| 4.3 Functional elements..... | 25 | +| 4.3.1 SCEF..... | 25 | +| 4.3.2 SCS/AS..... | 26 | +| 4.4 Procedures over T8 reference point..... | 26 | +| 4.4.1 Introduction..... | 26 | +| 4.4.2 Monitoring Procedures..... | 26 | +| 4.4.2.1 General..... | 26 | +| 4.4.2.2 Monitoring Events Configuration..... | 26 | +| 4.4.2.2.1 General..... | 26 | +| 4.4.2.2.2 Monitoring Events Configuration via HSS..... | 28 | +| 4.4.2.2.2.1 General..... | 28 | +| 4.4.2.2.2.2 Configuration Request for an individual UE..... | 28 | +| 4.4.2.2.2.3 Configuration Request for a group of UEs..... | 29 | +| 4.4.2.2.3 Monitoring Events Configuration directly via MME/SGSN..... | 30 | +| 4.4.2.2.4 Monitoring Events Configuration via PCRF..... | 30 | +| 4.4.2.2.4.1 General..... | 30 | +| 4.4.2.2.4.2 Configuration Request for an individual UE..... | 31 | +| 4.4.2.2.4.3 Configuration Request for a group of UEs..... | 31 | +| 4.4.2.3 Reporting of Monitoring Event Procedure..... | 31 | +| 4.4.2.4 Network-initiated Explicit Monitoring Event Deletion Procedure..... | 32 | +| 4.4.2.5 Network initiated notification of applied parameter configuration..... | 32 | +| 4.4.3 Procedures for resource management of Background Data Transfer..... | 32 | +| 4.4.4 Procedures for changing the chargeable party at session set up or during the session..... | 33 | +| 4.4.5 Procedures for Non-IP Data Delivery..... | 34 | +| 4.4.5.1 General..... | 34 | +| 4.4.5.2 NIDD Configuration..... | 35 | +| 4.4.5.2.1 NIDD Configuration for a single UE..... | 35 | +| 4.4.5.2.2 NIDD Configuration for a group of UEs..... | 36 | +| 4.4.5.3 Mobile Terminated NIDD procedure..... | 36 | +| 4.4.5.3.1 Mobile Terminated NIDD for a single UE..... | 36 | +| 4.4.5.3.2 Mobile Terminated NIDD for a group of UEs..... | 38 | +| 4.4.5.4 Mobile Originated NIDD procedure..... | 38 | +| 4.4.5.5 NIDD Authorisation Update procedure..... | 39 | +| 4.4.5.6 Port Management Configuration..... | 39 | + +###### Copyright Notification + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +| | | | +|-------------|-------------------------------------------------------------------|----| +| 4.4.5.6.1 | Port Reservation and Release..... | 39 | +| 4.4.5.6.2 | Port Notification..... | 40 | +| 4.4.6 | Procedures for Device Triggering..... | 41 | +| 4.4.7 | Procedures for Group Message Delivery..... | 42 | +| 4.4.7.1 | General..... | 42 | +| 4.4.7.2 | Group Message Delivery via MBMS..... | 42 | +| 4.4.7.2.1 | General..... | 42 | +| 4.4.7.2.2 | Group Message Delivery via MBMS by MB2..... | 42 | +| 4.4.7.2.2.1 | TMGI Allocation..... | 42 | +| 4.4.7.2.2.2 | TMGI Deallocation..... | 43 | +| 4.4.7.2.2.3 | Creation of group message delivery..... | 43 | +| 4.4.7.2.2.4 | Modification of previous submitted group message delivery..... | 43 | +| 4.4.7.2.2.5 | Cancellation of previous submitted group message delivery..... | 44 | +| 4.4.7.2.3 | Group message Delivery via MBMS by xMB..... | 44 | +| 4.4.7.2.3.1 | Service Creation..... | 44 | +| 4.4.7.2.3.2 | Service Deletion..... | 44 | +| 4.4.7.2.3.3 | Creation of group message delivery..... | 45 | +| 4.4.7.2.3.4 | Modification of previous submitted group message delivery..... | 45 | +| 4.4.7.2.3.5 | Cancellation of previous submitted group message delivery..... | 46 | +| 4.4.8 | Procedures for Reporting of Network Status..... | 46 | +| 4.4.8.1 | General..... | 46 | +| 4.4.8.2 | Network Status Reporting Subscription..... | 46 | +| 4.4.8.3 | Network Status Reporting Notification..... | 47 | +| 4.4.9 | Procedures for Communication Pattern Parameters Provisioning..... | 47 | +| 4.4.10 | Procedures for PFD Management..... | 48 | +| 4.4.11 | Procedures for Enhanced Coverage Restriction Control..... | 50 | +| 4.4.12 | Procedures for Network Parameter Configuration..... | 50 | +| 4.4.12.1 | General..... | 50 | +| 4.4.12.2 | Configuration Request for an individual UE..... | 51 | +| 4.4.12.3 | Configuration Request for a group of UEs..... | 51 | +| 4.4.12.4 | Notification of applied parameter configuration..... | 52 | +| 4.4.13 | Procedures for setting up an AS session with required QoS..... | 52 | +| 4.4.14 | Procedures for MSISDN-less Mobile Originated SMS..... | 53 | +| 4.4.14.1 | General..... | 53 | +| 4.4.14.2 | Delivery of MSISDN-less MO SMS..... | 53 | +| 4.4.15 | Procedures for RACS Parameter Provisioning..... | 54 | +| 5 | T8 APIs..... | 54 | +| 5.1 | Introduction..... | 54 | +| 5.2 | Information applicable to several APIs..... | 55 | +| 5.2.1 | Data Types..... | 55 | +| 5.2.1.1 | Introduction..... | 55 | +| 5.2.1.2 | Referenced structured data types..... | 58 | +| 5.2.1.2.1 | Type: SponsorInformation..... | 58 | +| 5.2.1.2.2 | Type: UsageThreshold..... | 58 | +| 5.2.1.2.3 | Type: TimeWindow..... | 58 | +| 5.2.1.2.4 | Type: Acknowledgement..... | 59 | +| 5.2.1.2.5 | Type: NotificationData..... | 59 | +| 5.2.1.2.6 | Type: EventReport..... | 59 | +| 5.2.1.2.7 | Type: AccumulatedUsage..... | 59 | +| 5.2.1.2.8 | Type: FlowInfo..... | 59 | +| 5.2.1.2.9 | Type: TestNotification..... | 60 | +| 5.2.1.2.10 | Type: WebsockNotifConfig..... | 60 | +| 5.2.1.2.11 | Type: LocationArea..... | 60 | +| 5.2.1.2.12 | Type: ProblemDetails..... | 61 | +| 5.2.1.2.13 | Type: InvalidParam..... | 61 | +| 5.2.1.2.14 | Type: PlmnId..... | 62 | +| 5.2.1.2.15 | Type: ConfigResult..... | 62 | +| 5.2.1.2.16 | Type: UsageThresholdRm..... | 62 | +| 5.2.1.2.17 | Type: LocationArea5G..... | 62 | +| 5.2.1.2.18 | Type: EthFlowInfo..... | 63 | +| 5.2.1.3 | Referenced Simple data types and enumerations..... | 63 | + +| | | | +|-----------|--------------------------------------------------------------------|-----| +| 5.2.1.3.1 | Introduction..... | 63 | +| 5.2.1.3.2 | Simple data types..... | 63 | +| 5.2.1.3.3 | Enumeration: Event..... | 64 | +| 5.2.1.3.4 | Enumeration: ResultReason..... | 65 | +| 5.2.1.4 | Conventions for documenting structured data types..... | 65 | +| 5.2.2 | Usage of HTTP..... | 66 | +| 5.2.2.1 | General..... | 66 | +| 5.2.2.2 | Usage of the HTTP PATCH method..... | 66 | +| 5.2.3 | Content type..... | 66 | +| 5.2.4 | URI structure..... | 67 | +| 5.2.4.1 | Resource URI structure..... | 67 | +| 5.2.4.2 | Custom operations URI structure..... | 67 | +| 5.2.4.3 | Callback URI structure..... | 67 | +| 5.2.5 | Notifications..... | 68 | +| 5.2.5.1 | General..... | 68 | +| 5.2.5.2 | Notification Delivery using a separate HTTP connection..... | 68 | +| 5.2.5.3 | Notification Test Event..... | 68 | +| 5.2.5.4 | Notification Delivery using Websocket..... | 68 | +| 5.2.6 | Error handling..... | 70 | +| 5.2.7 | Feature negotiation..... | 72 | +| 5.2.8 | HTTP custom headers..... | 72 | +| 5.2.8.1 | General..... | 72 | +| 5.2.8.2 | Reused HTTP custom headers..... | 72 | +| 5.2.8.3.1 | General..... | 72 | +| 5.2.9 | Conventions for Open API specification files..... | 74 | +| 5.2.9.1 | General..... | 74 | +| 5.2.9.2 | Formatting of OpenAPI files..... | 74 | +| 5.2.9.3 | Structured data types..... | 74 | +| 5.2.9.4 | Info..... | 76 | +| 5.2.9.5 | Servers..... | 76 | +| 5.2.9.6 | References to other 3GPP-defined Open API specification files..... | 76 | +| 5.2.9.7 | Server-initiated communication..... | 77 | +| 5.2.9.8 | Describing the body of HTTP PATCH requests..... | 77 | +| 5.2.9.8.1 | General..... | 77 | +| 5.2.9.8.2 | JSON Merge Patch..... | 77 | +| 5.2.9.8.3 | JSON PATCH..... | 78 | +| 5.2.9.9 | Error Responses..... | 78 | +| 5.2.9.10 | Enumerations..... | 79 | +| 5.2.9.11 | Read only attribute..... | 80 | +| 5.2.9.12 | externalDocs..... | 80 | +| 5.2.9.13 | Operation identifiers..... | 80 | +| 5.2.9.14 | Usage of the "tags" field..... | 80 | +| 5.2.10 | Redirection handling..... | 81 | +| 5.2.11 | Support of Load and Overload Control..... | 81 | +| 5.2.12 | Query parameters..... | 82 | +| 5.2.13 | Vendor-specific extensions..... | 82 | +| 5.2.13.1 | General 82 | | +| 5.2.13.2 | Vendor-specific extensions to the data model..... | 82 | +| 5.2.13.3 | Vendor-specific query parameters..... | 83 | +| 5.3 | MonitoringEvent API..... | 84 | +| 5.3.1 | Overview..... | 84 | +| 5.3.2 | Data model..... | 84 | +| 5.3.2.1 | Resource data types..... | 84 | +| 5.3.2.1.1 | Introduction..... | 84 | +| 5.3.2.1.2 | Type: MonitoringEventSubscription..... | 87 | +| 5.3.2.1.3 | Void..... | 99 | +| 5.3.2.2 | Notification data types..... | 99 | +| 5.3.2.2.1 | Introduction..... | 99 | +| 5.3.2.2.2 | Type: MonitoringNotification..... | 99 | +| 5.3.2.3 | Referenced structured data types..... | 100 | +| 5.3.2.3.1 | Introduction..... | 100 | + +| | | | +|---------------|---------------------------------------------------------|-----| +| 5.3.2.3.2 | Type: MonitoringEventReport..... | 100 | +| 5.3.2.3.3 | Type: IdleStatusInfo..... | 104 | +| 5.3.2.3.4 | Type: UePerLocationReport..... | 104 | +| 5.3.2.3.5 | Type: LocationInfo..... | 104 | +| 5.3.2.3.6 | Type: FailureCause..... | 106 | +| 5.3.2.3.7 | Type: PdnConnectionInformation..... | 107 | +| 5.3.2.3.8 | Type: AppliedParameterConfiguration..... | 107 | +| 5.3.2.3.9 | Type: ApiCapabilityInfo..... | 107 | +| 5.3.2.3.10 | Type: MonitoringEventReports..... | 108 | +| 5.3.2.3.11 | Type: UavPolicy..... | 108 | +| 5.3.2.3.11 | Type: ConsentRevocNotif..... | 108 | +| 5.3.2.3.12 | Type: ConsentRevoked..... | 109 | +| 5.3.2.3.13 | Type: GroupMembListChanges..... | 109 | +| 5.3.2.3.14 | Type: RangeDirection..... | 109 | +| 5.3.2.3.15 | Type: TwodrelativeLocation..... | 109 | +| 5.3.2.3.16 | Type: ThreedrelativeLocation..... | 109 | +| 5.3.2.3.17 | Type: UpLocRepAddrAfRm..... | 110 | +| 5.3.2.3.18 | Type: UpCumEvtRep..... | 110 | +| 5.3.2.4 | Referenced simple data types and enumerations..... | 110 | +| 5.3.2.4.1 | Introduction..... | 110 | +| 5.3.2.4.2 | Simple data types..... | 110 | +| 5.3.2.4.3 | Enumeration: MonitoringType..... | 110 | +| 5.3.2.4.4 | Enumeration: ReachabilityType..... | 111 | +| 5.3.2.4.5 | Enumeration: LocationType..... | 112 | +| 5.3.2.4.6 | Enumeration: AssociationType..... | 112 | +| 5.3.2.4.7 | Enumeration: Accuracy..... | 112 | +| 5.3.2.4.8 | Enumeration: PdnConnectionStatus..... | 113 | +| 5.3.2.4.9 | Enumeration: PdnType..... | 113 | +| 5.3.2.4.10 | Enumeration: InterfaceIndication..... | 113 | +| 5.3.2.4.11 | Enumeration: LocationFailureCause..... | 114 | +| 5.3.2.4.12 | Enumeration: SubType..... | 114 | +| 5.3.2.4.13 | Enumeration: SACRepFormat..... | 114 | +| 5.3.3 | Resource structure..... | 114 | +| 5.3.3.1 | General..... | 114 | +| 5.3.3.2 | Resource: Monitoring Event Subscriptions..... | 115 | +| 5.3.3.2.1 | Introduction..... | 115 | +| 5.3.3.2.2 | Resource definition..... | 115 | +| 5.3.3.2.3 | Resource methods..... | 115 | +| 5.3.3.2.3.1 | GET..... | 115 | +| 5.3.3.2.3.2 | PUT..... | 116 | +| 5.3.3.2.3.3 | PATCH..... | 116 | +| 5.3.3.2.3.4 | POST..... | 117 | +| 5.3.3.2.3.5 | DELETE..... | 118 | +| 5.3.3.3 | Resource: Individual Monitoring Event Subscription..... | 118 | +| 5.3.3.3.1 | Introduction..... | 118 | +| 5.3.3.3.2 | Resource definition..... | 118 | +| 5.3.3.3.3 | Resource methods..... | 118 | +| 5.3.3.3.3.1 | GET..... | 118 | +| 5.3.3.3.3.2 | PUT..... | 119 | +| 5.3.3.3.3.3 | PATCH..... | 120 | +| 5.3.3.3.3.4 | POST..... | 121 | +| 5.3.3.3.3.5 | DELETE..... | 121 | +| 5.3.3.4 | Void..... | 122 | +| 5.3.3.A | Notifications..... | 122 | +| 5.3.3.A.1 | General..... | 122 | +| 5.3.3.A.2 | Monitoring Notification..... | 123 | +| 5.3.3.A.2.1 | Description..... | 123 | +| 5.3.3.A.2.2 | Target URI..... | 123 | +| 5.3.3.A.2.3 | Standard Methods..... | 123 | +| 5.3.3.A.2.3.1 | Notification via POST..... | 123 | +| 5.3.3.A.2.3.2 | Notification via Websocket..... | 124 | + +| | | | +|--------------|----------------------------------------------------|-----| +| 5.3.3A.3 | User Consent Revocation Notification..... | 124 | +| 5.3.3A.3.1 | Description..... | 124 | +| 5.3.3A.3.2 | Target URI..... | 124 | +| 5.3.3A.3.3 | Operation Definition..... | 125 | +| 5.3.3A.3.3.1 | Notification via HTTP POST..... | 125 | +| 5.3.3A.3.3.2 | Notification via Websocket..... | 125 | +| 5.3.4 | Used Features..... | 125 | +| 5.3.5 | Error handling..... | 128 | +| 5.3.5.1 | General..... | 128 | +| 5.3.5.2 | Protocol Errors..... | 128 | +| 5.3.5.3 | Application Errors..... | 128 | +| 5.4 | ResourceManagementOfBdt API..... | 130 | +| 5.4.1 | Overview..... | 130 | +| 5.4.2 | Data model..... | 130 | +| 5.4.2.1 | Resource data types..... | 130 | +| 5.4.2.1.1 | Introduction..... | 130 | +| 5.4.2.1.2 | Type: Bdt..... | 130 | +| 5.4.2.1.3 | Type: BdtPatch..... | 131 | +| 5.4.2.1.4 | Type: ExNotification..... | 132 | +| 5.4.2.2 | Referenced structured data types..... | 132 | +| 5.4.2.2.1 | Introduction..... | 132 | +| 5.4.2.2.2 | Type: TransferPolicy..... | 132 | +| 5.4.2.3 | Referenced simple data types and enumerations..... | 133 | +| 5.4.2.3.1 | Introduction..... | 133 | +| 5.4.2.3.2 | Simple data types..... | 133 | +| 5.4.3 | Resource structure..... | 133 | +| 5.4.3.1 | General..... | 133 | +| 5.4.3.2 | Resource: BDT Subscriptions..... | 134 | +| 5.4.3.2.1 | Introduction..... | 134 | +| 5.4.3.2.2 | Resource definition..... | 134 | +| 5.4.3.2.3 | Resource methods..... | 134 | +| 5.4.3.2.3.1 | GET..... | 134 | +| 5.4.3.2.3.2 | PUT..... | 135 | +| 5.4.3.2.3.3 | PATCH..... | 135 | +| 5.4.3.2.3.4 | POST..... | 135 | +| 5.4.3.2.3.5 | DELETE..... | 136 | +| 5.4.3.3 | Resource: Individual BDT Subscription..... | 136 | +| 5.4.3.3.1 | Introduction..... | 136 | +| 5.4.3.3.2 | Resource definition..... | 136 | +| 5.4.3.3.3 | Resource methods..... | 136 | +| 5.4.3.3.3.1 | GET..... | 136 | +| 5.4.3.3.3.2 | PUT..... | 137 | +| 5.4.3.3.3.3 | PATCH..... | 138 | +| 5.4.3.3.3.4 | POST..... | 139 | +| 5.4.3.3.3.5 | DELETE..... | 139 | +| 5.4.3.4 | Void..... | 140 | +| 5.4.3A | Notifications..... | 140 | +| 5.4.3A.1 | General..... | 140 | +| 5.4.3A.2 | BDT Warning Notification..... | 141 | +| 5.4.3A.2.1 | Description..... | 141 | +| 5.4.3A.2.2 | Target URI..... | 141 | +| 5.4.3A.2.3 | Standard Methods..... | 141 | +| 5.4.3A.2.3.1 | Notification via POST..... | 141 | +| 5.4.3A.2.3.2 | Notification via Websocket..... | 142 | +| 5.4.4 | Used Features..... | 142 | +| 5.4.5 | Error handling..... | 142 | +| 5.4.5.1 | General..... | 142 | +| 5.4.5.2 | Protocol Errors..... | 142 | +| 5.4.5.3 | Application Errors..... | 142 | +| 5.5 | ChargeableParty API..... | 143 | +| 5.5.1 | Overview..... | 143 | + +| | | | +|--------------|--------------------------------------------------------|-----| +| 5.5.2 | Data model..... | 143 | +| 5.5.2.1 | Resource data types..... | 143 | +| 5.5.2.1.1 | Introduction..... | 143 | +| 5.5.2.1.2 | Type: ChargeableParty..... | 143 | +| 5.5.2.1.3 | Type: ChargeablePartyPatch..... | 145 | +| 5.5.3 | Resource structure..... | 145 | +| 5.5.3.1 | General..... | 145 | +| 5.5.3.2 | Resource: Chargeable Party Transactions..... | 146 | +| 5.5.3.2.1 | Introduction..... | 146 | +| 5.5.3.2.2 | Resource definition..... | 146 | +| 5.5.3.2.3 | Resource methods..... | 146 | +| 5.5.3.2.3.1 | GET..... | 146 | +| 5.5.3.2.3.2 | PUT..... | 147 | +| 5.5.3.2.3.3 | PATCH..... | 147 | +| 5.5.3.2.3.4 | POST..... | 147 | +| 5.5.3.2.3.5 | DELETE..... | 148 | +| 5.5.3.3 | Resource: Individual Chargeable Party Transaction..... | 148 | +| 5.5.3.3.1 | Introduction..... | 148 | +| 5.5.3.3.2 | Resource definition..... | 148 | +| 5.5.3.3.3 | Resource methods..... | 148 | +| 5.5.3.3.3.1 | GET..... | 148 | +| 5.5.3.3.3.2 | PUT..... | 149 | +| 5.5.3.3.3.3 | PATCH..... | 149 | +| 5.5.3.3.3.4 | POST..... | 150 | +| 5.5.3.3.3.5 | DELETE..... | 150 | +| 5.5.3.4 | Void..... | 151 | +| 5.5.3A | Notifications..... | 151 | +| 5.5.3A.1 | General..... | 151 | +| 5.5.3A.2 | Event Notification..... | 152 | +| 5.5.3A.2.1 | Description..... | 152 | +| 5.5.3A.2.2 | Target URI..... | 152 | +| 5.5.3A.2.3 | Standard Methods..... | 152 | +| 5.5.3A.2.3.1 | Notification via POST..... | 152 | +| 5.5.3A.2.3.2 | Notification via Websocket..... | 153 | +| 5.5.4 | Used Features..... | 153 | +| 5.5.5 | Error handling..... | 153 | +| 5.5.5.1 | General..... | 153 | +| 5.5.5.2 | Protocol Errors..... | 153 | +| 5.5.5.3 | Application Errors..... | 153 | +| 5.6 | NIDD API..... | 154 | +| 5.6.1 | Overview..... | 154 | +| 5.6.2 | Data model..... | 154 | +| 5.6.2.1 | Resource data types..... | 154 | +| 5.6.2.1.1 | Introduction..... | 154 | +| 5.6.2.1.2 | Type: NiddConfiguration..... | 155 | +| 5.6.2.1.3 | Type: NiddDownlinkDataTransfer..... | 157 | +| 5.6.2.1.4 | Type: NiddUplinkDataNotification..... | 159 | +| 5.6.2.1.5 | Type: NiddDownlinkDataDeliveryStatusNotification..... | 159 | +| 5.6.2.1.6 | Type: NiddConfigurationStatusNotification..... | 160 | +| 5.6.2.1.7 | Type: NiddConfigurationPatch..... | 160 | +| 5.6.2.1.8 | Type: GmdNiddDownlinkDataDeliveryNotification..... | 161 | +| 5.6.2.1.9 | Type: ManagePort..... | 161 | +| 5.6.2.1.10 | Type: ManagePortNotification..... | 162 | +| 5.6.2.1.11 | Type: NiddDownlinkDataTransferPatch..... | 162 | +| 5.6.2.2 | Referenced structured data types..... | 163 | +| 5.6.2.2.1 | Introduction..... | 163 | +| 5.6.2.2.2 | Type: RdsPort..... | 163 | +| 5.6.2.2.3 | Type: GmdResult..... | 164 | +| 5.6.2.2.4 | Type: NiddDownlinkDataDeliveryFailure..... | 164 | +| 5.6.2.2.5 | Type: RdsDownlinkDataDeliveryFailure..... | 164 | +| 5.6.2.3 | Referenced simple data types and enumerations..... | 165 | + +| | | | +|-------------|-------------------------------------------------------|-----| +| 5.6.2.3.1 | Introduction..... | 165 | +| 5.6.2.3.2 | Simple data types..... | 165 | +| 5.6.2.3.3 | Enumeration: PdnEstablishmentOptions..... | 165 | +| 5.6.2.3.4 | Enumeration: DeliveryStatus..... | 165 | +| 5.6.2.3.5 | Enumeration: NiddStatus..... | 166 | +| 5.6.2.3.6 | Enumeration: PdnEstablishmentOptionsRm..... | 166 | +| 5.6.2.3.7 | Enumeration: ManageEntity..... | 167 | +| 5.6.2.3.8 | Enumeration: SerializationFormat..... | 167 | +| 5.6.3 | Resource structure..... | 167 | +| 5.6.3.1 | General..... | 167 | +| 5.6.3.2 | Resource: NIDD Configurations..... | 168 | +| 5.6.3.2.1 | Introduction..... | 168 | +| 5.6.3.2.2 | Resource definition..... | 169 | +| 5.6.3.2.3 | Resource methods..... | 169 | +| 5.6.3.2.3.1 | GET..... | 169 | +| 5.6.3.2.3.2 | PUT..... | 170 | +| 5.6.3.2.3.3 | PATCH..... | 170 | +| 5.6.3.2.3.4 | POST..... | 170 | +| 5.6.3.2.3.5 | DELETE..... | 170 | +| 5.6.3.3 | Resource: Individual NIDD Configuration..... | 170 | +| 5.6.3.3.1 | Introduction..... | 170 | +| 5.6.3.3.2 | Resource definition..... | 171 | +| 5.6.3.3.3 | Resource methods..... | 171 | +| 5.6.3.3.3.1 | GET..... | 171 | +| 5.6.3.3.3.2 | PUT..... | 172 | +| 5.6.3.3.3.3 | PATCH..... | 172 | +| 5.6.3.3.3.4 | POST..... | 173 | +| 5.6.3.3.3.5 | DELETE..... | 173 | +| 5.6.3.4 | Resource: NIDD downlink data deliveries..... | 173 | +| 5.6.3.4.1 | Introduction..... | 173 | +| 5.6.3.4.2 | Resource definition..... | 174 | +| 5.6.3.4.3 | Resource methods..... | 174 | +| 5.6.3.4.3.1 | GET..... | 174 | +| 5.6.3.4.3.2 | PUT..... | 175 | +| 5.6.3.4.3.3 | PATCH..... | 175 | +| 5.6.3.4.3.4 | POST..... | 175 | +| 5.6.3.4.3.5 | DELETE..... | 177 | +| 5.6.3.5 | Resource: Individual NIDD downlink data delivery..... | 177 | +| 5.6.3.5.1 | Introduction..... | 177 | +| 5.6.3.5.2 | Resource definition..... | 177 | +| 5.6.3.5.3 | Resource methods..... | 177 | +| 5.6.3.5.3.1 | GET..... | 177 | +| 5.6.3.5.3.2 | PUT..... | 178 | +| 5.6.3.5.3.3 | PATCH..... | 179 | +| 5.6.3.5.3.4 | POST..... | 180 | +| 5.6.3.5.3.5 | DELETE..... | 181 | +| 5.6.3.6 | Void..... | 182 | +| 5.6.3.7 | Void..... | 182 | +| 5.6.3.8 | Void..... | 182 | +| 5.6.3.9 | Resource: Individual ManagePort Configuration..... | 182 | +| 5.6.3.9.1 | Introduction..... | 182 | +| 5.6.3.9.2 | Resource definition..... | 182 | +| 5.6.3.9.3 | Resource methods..... | 182 | +| 5.6.3.9.3.1 | GET..... | 182 | +| 5.6.3.9.3.2 | PUT..... | 183 | +| 5.6.3.9.3.3 | PATCH..... | 184 | +| 5.6.3.9.3.4 | POST..... | 184 | +| 5.6.3.9.3.5 | DELETE..... | 184 | +| 5.6.3.10 | Void..... | 185 | +| 5.6.3.11 | Resource: ManagePort Configurations..... | 185 | +| 5.6.3.11.1 | Introduction..... | 185 | + +| | | | +|--------------|-------------------------------------------------------|-----| +| 5.6.3.11.2 | Resource definition..... | 186 | +| 5.6.3.11.3 | Resource methods..... | 186 | +| 5.6.3.11.3.1 | GET..... | 186 | +| 5.6.3.11.3.2 | PUT..... | 187 | +| 5.6.3.11.3.3 | PATCH..... | 187 | +| 5.6.3.11.3.4 | POST..... | 187 | +| 5.6.3.11.3.5 | DELETE..... | 187 | +| 5.6.3A | Notifications..... | 187 | +| 5.6.3A.1 | General..... | 187 | +| 5.6.3A.2 | NIDD Configuration Update Notification..... | 187 | +| 5.6.3A.2.1 | Description..... | 187 | +| 5.6.3A.2.2 | Target URI..... | 188 | +| 5.6.3A.2.3 | Standard Methods..... | 188 | +| 5.6.3A.2.3.1 | Notification via POST..... | 188 | +| 5.6.3A.2.3.2 | Notification via Websocket..... | 189 | +| 5.6.3A.3 | NIDD Downlink Data Delivery Status Notification..... | 189 | +| 5.6.3A.3.1 | Description..... | 189 | +| 5.6.3A.3.2 | Target URI..... | 189 | +| 5.6.3A.3.3 | Standard Methods..... | 189 | +| 5.6.3A.3.3.1 | Notification via POST..... | 189 | +| 5.6.3A.3.3.2 | Notification via Websocket..... | 191 | +| 5.6.3A.4 | NIDD Uplink Data Notification..... | 191 | +| 5.6.3A.4.1 | Description..... | 191 | +| 5.6.3A.4.2 | Target URI..... | 191 | +| 5.6.3A.4.3 | Standard Methods..... | 191 | +| 5.6.3A.4.3.1 | Notification via POST..... | 191 | +| 5.6.3A.4.3.2 | Notification via Websocket..... | 192 | +| 5.6.3A.5 | ManagePort Notification..... | 192 | +| 5.6.3A.5.1 | Description..... | 192 | +| 5.6.3A.5.2 | Target URI..... | 192 | +| 5.6.3A.5.3 | Standard Methods..... | 193 | +| 5.6.3A.5.3.1 | Notification via POST..... | 193 | +| 5.6.3A.5.3.2 | Notification via Websocket..... | 193 | +| 5.6.4 | Used Features..... | 194 | +| 5.6.5 | Error handling..... | 194 | +| 5.6.5.1 | General..... | 194 | +| 5.6.5.2 | Protocol Errors..... | 194 | +| 5.6.5.3 | Application Errors..... | 194 | +| 5.7 | DeviceTriggering API..... | 195 | +| 5.7.1 | Overview..... | 195 | +| 5.7.2 | Data model..... | 195 | +| 5.7.2.1 | Resource data types..... | 195 | +| 5.7.2.1.1 | Introduction..... | 195 | +| 5.7.2.1.2 | Type: DeviceTriggering..... | 196 | +| 5.7.2.1.3 | Type: DeviceTriggeringDeliveryReportNotification..... | 197 | +| 5.7.2.1.4 | Type: DeviceTriggeringPatch..... | 198 | +| 5.7.2.2 | Referenced simple data types and enumerations..... | 198 | +| 5.7.2.2.1 | Introduction..... | 198 | +| 5.7.2.2.2 | Simple data types..... | 198 | +| 5.7.2.2.3 | Enumeration: DeliveryResult..... | 198 | +| 5.7.2.2.4 | Enumeration: Priority..... | 199 | +| 5.7.3 | Resource structure..... | 199 | +| 5.7.3.1 | General..... | 199 | +| 5.7.3.2 | Resource: Device Triggering Transactions..... | 200 | +| 5.7.3.2.1 | Introduction..... | 200 | +| 5.7.3.2.2 | Resource definition..... | 200 | +| 5.7.3.2.3 | Resource methods..... | 200 | +| 5.7.3.2.3.1 | GET..... | 200 | +| 5.7.3.2.3.2 | PUT..... | 201 | +| 5.7.3.2.3.3 | PATCH..... | 201 | +| 5.7.3.2.3.4 | POST..... | 201 | + +| | | | +|---------------|---------------------------------------------------------|-----| +| 5.7.3.2.3.5 | DELETE..... | 202 | +| 5.7.3.3 | Resource: Individual Device Triggering Transaction..... | 202 | +| 5.7.3.3.1 | Introduction..... | 202 | +| 5.7.3.3.2 | Resource definition..... | 202 | +| 5.7.3.3.3 | Resource methods..... | 202 | +| 5.7.3.3.3.1 | GET..... | 202 | +| 5.7.3.3.3.2 | PUT..... | 203 | +| 5.7.3.3.3.3 | PATCH..... | 204 | +| 5.7.3.3.3.4 | POST..... | 205 | +| 5.7.3.3.3.5 | DELETE..... | 205 | +| 5.7.3.4 | Void..... | 206 | +| 5.7.3A | Notifications..... | 206 | +| 5.7.3A.1 | General..... | 206 | +| 5.7.3A.2 | Device Triggering Delivery Report Notification..... | 207 | +| 5.7.3A.2.1 | Description..... | 207 | +| 5.7.3A.2.2 | Target URI..... | 207 | +| 5.7.3A.2.3 | Standard Methods..... | 207 | +| 5.7.3A.2.3.1 | Notification via POST..... | 207 | +| 5.7.3a.2.3.2 | Notification via Websocket..... | 208 | +| 5.7.4 | Used Features..... | 208 | +| 5.7.5 | Error handling..... | 208 | +| 5.7.5.1 | General..... | 208 | +| 5.7.5.2 | Protocol Errors..... | 208 | +| 5.7.5.3 | Application Errors..... | 208 | +| 5.8 | GMD via MBMS related APIs..... | 209 | +| 5.8.1 | Overview..... | 209 | +| 5.8.2 | GMDviaMBMSByMB2 API..... | 209 | +| 5.8.2.1 | Data model..... | 209 | +| 5.8.2.1.1 | Resource data types..... | 209 | +| 5.8.2.1.1.1 | Introduction..... | 209 | +| 5.8.2.1.1.2 | Type: TMGIAllocation..... | 209 | +| 5.8.2.1.1.3 | Type: GMDViaMBMSByMb2..... | 210 | +| 5.8.2.1.1.4 | Type: GMDByMb2Notification..... | 211 | +| 5.8.2.1.1.5 | Type: TMGIAllocationPatch..... | 211 | +| 5.8.2.1.1.6 | Type: GMDViaMBMSByMb2Patch..... | 211 | +| 5.8.2.1.1.7 | Type: MbmsLocArea..... | 212 | +| 5.8.2.2 | Resource structure..... | 212 | +| 5.8.2.2.1 | General..... | 212 | +| 5.8.2.2.2 | Resource: TMGI Allocation..... | 213 | +| 5.8.2.2.2.1 | Introduction..... | 213 | +| 5.8.2.2.2.2 | Resource definition..... | 213 | +| 5.8.2.2.2.3 | Resource methods..... | 213 | +| 5.8.2.2.2.3.1 | GET..... | 213 | +| 5.8.2.2.2.3.2 | PUT..... | 214 | +| 5.8.2.2.2.3.3 | PATCH..... | 214 | +| 5.8.2.2.2.3.4 | POST..... | 214 | +| 5.8.2.2.2.3.5 | DELETE..... | 215 | +| 5.8.2.2.3 | Resource: Individual TMGI Allocation..... | 215 | +| 5.8.2.2.3.1 | Introduction..... | 215 | +| 5.8.2.2.3.2 | Resource definition..... | 215 | +| 5.8.2.2.3.3 | Resource methods..... | 215 | +| 5.8.2.2.3.3.1 | GET..... | 215 | +| 5.8.2.2.3.3.2 | PUT..... | 216 | +| 5.8.2.2.3.3.3 | PATCH..... | 217 | +| 5.8.2.2.3.3.4 | POST..... | 218 | +| 5.8.2.2.3.3.5 | DELETE..... | 218 | +| 5.8.2.2.4 | Resource: GMD via MBMS by MB2..... | 219 | +| 5.8.2.2.4.1 | Introduction..... | 219 | +| 5.8.2.2.4.2 | Resource definition..... | 219 | +| 5.8.2.2.4.3 | Resource methods..... | 220 | +| 5.8.2.2.4.3.1 | GET..... | 220 | + +| | | | +|----------------|----------------------------------------------------|-----| +| 5.8.2.2.4.3.2 | PUT..... | 220 | +| 5.8.2.2.4.3.3 | PATCH..... | 220 | +| 5.8.2.2.4.3.4 | POST..... | 220 | +| 5.8.2.2.4.3.5 | DELETE..... | 221 | +| 5.8.2.2.5 | Resource: Individual GMD via MBMS by MB2..... | 221 | +| 5.8.2.2.5.1 | Introduction..... | 221 | +| 5.8.2.2.5.2 | Resource definition..... | 221 | +| 5.8.2.2.5.3 | Resource methods..... | 221 | +| 5.8.2.2.5.3.1 | GET..... | 221 | +| 5.8.2.2.5.3.2 | PUT..... | 222 | +| 5.8.2.2.5.3.3 | PATCH..... | 223 | +| 5.8.2.2.5.3.4 | POST..... | 224 | +| 5.8.2.2.5.3.5 | DELETE..... | 224 | +| 5.8.2.2.6 | Void..... | 225 | +| 5.8.2.2A | Notifications..... | 225 | +| 5.8.2.2A.1 | General..... | 225 | +| 5.8.2.2A.2 | GMD via MBMS by MB2 Notification..... | 226 | +| 5.8.2.2A.2.1 | Description..... | 226 | +| 5.8.2.2A.2.2 | Target URI..... | 226 | +| 5.8.2.2A.2.3 | Standard Methods..... | 226 | +| 5.8.2.2A.2.3.1 | Notification via POST..... | 226 | +| 5.8.2.2A.2.3.2 | Notification via Websocket..... | 227 | +| 5.8.2.3 | Used Features..... | 227 | +| 5.8.2.4 | Error handling..... | 227 | +| 5.8.2.4.1 | General..... | 227 | +| 5.8.2.4.2 | Protocol Errors..... | 227 | +| 5.8.2.4.3 | Application Errors..... | 227 | +| 5.8.3 | GMDviaMBMSByxMB API..... | 228 | +| 5.8.3.1 | Data model..... | 228 | +| 5.8.3.1.1 | Resource data types..... | 228 | +| 5.8.3.1.1.1 | Introduction..... | 228 | +| 5.8.3.1.1.2 | Type: ServiceCreation..... | 228 | +| 5.8.3.1.1.3 | Type: GMDViaMBMSByxMB..... | 229 | +| 5.8.3.1.1.4 | Type: GMDBByxMBNotification..... | 230 | +| 5.8.3.1.1.5 | Type: GMDViaMBMSByxMBPatch..... | 230 | +| 5.8.3.1.1.6 | Type: MbmsLocArea..... | 231 | +| 5.8.3.1.2 | Referenced simple data types and enumerations..... | 231 | +| 5.8.3.1.2.1 | Introduction..... | 231 | +| 5.8.3.1.2.2 | Simple data types..... | 231 | +| 5.8.3.1.2.3 | Enumeration: ServiceAnnouncementMode..... | 232 | +| 5.8.3.2 | Resource structure..... | 232 | +| 5.8.3.2.1 | General..... | 232 | +| 5.8.3.2.2 | Resource: xMB Services..... | 233 | +| 5.8.3.2.2.1 | Introduction..... | 233 | +| 5.8.3.2.2.2 | Resource definition..... | 233 | +| 5.8.3.2.2.3 | Resource methods..... | 233 | +| 5.8.3.2.2.3.1 | GET..... | 233 | +| 5.8.3.2.2.3.2 | PUT..... | 234 | +| 5.8.3.2.2.3.3 | PATCH..... | 234 | +| 5.8.3.2.2.3.4 | POST..... | 234 | +| 5.8.3.2.2.3.5 | DELETE..... | 235 | +| 5.8.3.2.3 | Resource: Individual xMB Service..... | 235 | +| 5.8.3.2.3.1 | Introduction..... | 235 | +| 5.8.3.2.3.2 | Resource definition..... | 235 | +| 5.8.3.2.3.3 | Resource methods..... | 235 | +| 5.8.3.2.3.3.1 | GET..... | 235 | +| 5.8.3.2.3.3.2 | PUT..... | 236 | +| 5.8.3.2.3.3.3 | PATCH..... | 236 | +| 5.8.3.2.3.3.4 | POST..... | 236 | +| 5.8.3.2.3.3.5 | DELETE..... | 236 | +| 5.8.3.2.4 | Resource: GMD via MBMS by xMB..... | 237 | + +| | | | +|----------------|-----------------------------------------------------------------|-----| +| 5.8.3.2.4.1 | Introduction..... | 237 | +| 5.8.3.2.4.2 | Resource definition..... | 237 | +| 5.8.3.2.4.3 | Resource methods..... | 238 | +| 5.8.3.2.4.3.1 | GET..... | 238 | +| 5.8.3.2.4.3.2 | PUT..... | 238 | +| 5.8.3.2.4.3.3 | PATCH..... | 238 | +| 5.8.3.2.4.3.4 | POST..... | 238 | +| 5.8.3.2.4.3.5 | DELETE..... | 239 | +| 5.8.3.2.5 | Resource: Individual GMD via MBMS by xMB..... | 239 | +| 5.8.3.2.5.1 | Introduction..... | 239 | +| 5.8.3.2.5.2 | Resource definition..... | 239 | +| 5.8.3.2.5.3 | Resource methods..... | 239 | +| 5.8.3.2.5.3.1 | GET..... | 239 | +| 5.8.3.2.5.3.2 | PUT..... | 240 | +| 5.8.3.2.5.3.3 | PATCH..... | 241 | +| 5.8.3.2.5.3.4 | POST..... | 242 | +| 5.8.3.2.5.3.5 | DELETE..... | 242 | +| 5.8.3.2.6 | Void..... | 243 | +| 5.8.3.2A | Notifications..... | 243 | +| 5.8.3.2A.1 | General..... | 243 | +| 5.8.3.2A.2 | GMD via MBMS by xMB Notification..... | 244 | +| 5.8.3.2A.2.1 | Description..... | 244 | +| 5.8.3.2A.2.2 | Target URI..... | 244 | +| 5.8.3.2A.2.3 | Standard Methods..... | 244 | +| 5.8.3.2A.2.3.1 | Notification via POST..... | 244 | +| 5.8.3.2A.2.3.2 | Notification via Websocket..... | 245 | +| 5.8.3.3 | Used Features..... | 245 | +| 5.8.3.4 | Error handling..... | 245 | +| 5.8.3.4.1 | General..... | 245 | +| 5.8.3.4.2 | Protocol Errors..... | 245 | +| 5.8.3.4.3 | Application Errors..... | 245 | +| 5.9 | ReportingNetworkStatus API..... | 246 | +| 5.9.1 | Overview..... | 246 | +| 5.9.2 | Data model..... | 246 | +| 5.9.2.1 | Resource data types..... | 246 | +| 5.9.2.1.1 | Introduction..... | 246 | +| 5.9.2.1.2 | Type: NetworkStatusReportingSubscription..... | 246 | +| 5.9.2.1.3 | Type: NetStatusRepSubsPatch..... | 247 | +| 5.9.2.2 | Notification data types..... | 248 | +| 5.9.2.2.1 | Introduction..... | 248 | +| 5.9.2.2.2 | Type: NetworkStatusReportingNotification..... | 248 | +| 5.9.2.3 | Referenced simple data types and enumerations..... | 249 | +| 5.9.2.3.1 | Introduction..... | 249 | +| 5.9.2.3.2 | Simple data types..... | 249 | +| 5.9.2.3.3 | Enumeration: CongestionType..... | 249 | +| 5.9.3 | Resource structure..... | 249 | +| 5.9.3.1 | General..... | 249 | +| 5.9.3.2 | Resource: Network Status Reporting Subscriptions..... | 250 | +| 5.9.3.2.1 | Introduction..... | 250 | +| 5.9.3.2.2 | Resource definition..... | 250 | +| 5.9.3.2.3 | Resource methods..... | 250 | +| 5.9.3.2.3.1 | GET..... | 250 | +| 5.9.3.2.3.2 | PUT..... | 251 | +| 5.9.3.2.3.3 | PATCH..... | 251 | +| 5.9.3.2.3.4 | POST..... | 251 | +| 5.9.3.2.3.5 | DELETE..... | 252 | +| 5.9.3.3 | Resource: Individual Network Status Reporting Subscription..... | 252 | +| 5.9.3.3.1 | Introduction..... | 252 | +| 5.9.3.3.2 | Resource definition..... | 252 | +| 5.9.3.3.3 | Resource methods..... | 252 | +| 5.9.3.3.3.1 | GET..... | 252 | + +| | | | +|--------------|--------------------------------------------------------|-----| +| 5.9.3.3.3.2 | PUT..... | 253 | +| 5.9.3.3.3.3 | PATCH..... | 254 | +| 5.9.3.3.3.4 | POST..... | 255 | +| 5.9.3.3.3.5 | DELETE..... | 255 | +| 5.9.3.4 | Void..... | 256 | +| 5.9.3A | Notifications..... | 256 | +| 5.9.3A.1 | General..... | 256 | +| 5.9.3A.2 | Network Status Reporting Notification..... | 257 | +| 5.9.3A.2.1 | Description..... | 257 | +| 5.9.3A.2.2 | Target URI..... | 257 | +| 5.9.3A.2.3 | Standard Methods..... | 257 | +| 5.9.3A.2.3.1 | Notification via POST..... | 257 | +| 5.9.3A.2.3.2 | Notification via Websocket..... | 258 | +| 5.9.4 | Used Features..... | 258 | +| 5.9.5 | Error handling..... | 258 | +| 5.9.5.1 | General..... | 258 | +| 5.9.5.2 | Protocol Errors..... | 258 | +| 5.9.5.3 | Application Errors..... | 258 | +| 5.10 | CpProvisioning API..... | 259 | +| 5.10.1 | Overview..... | 259 | +| 5.10.2 | Data model..... | 259 | +| 5.10.2.1 | Resource data types..... | 259 | +| 5.10.2.1.1 | Introduction..... | 259 | +| 5.10.2.1.2 | Type: CpInfo..... | 260 | +| 5.10.2.2 | Referenced structured data types..... | 262 | +| 5.10.2.2.1 | Introduction..... | 262 | +| 5.10.2.2.2 | Type: CpParameterSet..... | 262 | +| 5.10.2.2.3 | Type: ScheduledCommunicationTime..... | 264 | +| 5.10.2.2.4 | Type: CpReport..... | 264 | +| 5.10.2.2.5 | Type: UmtLocationArea5G..... | 264 | +| 5.10.2.2.6 | Type: AppExpUeBehaviour..... | 266 | +| 5.10.2.3 | Referenced simple data types and enumerations..... | 267 | +| 5.10.2.3.1 | Introduction..... | 267 | +| 5.10.2.3.2 | Simple data types..... | 267 | +| 5.10.2.3.3 | Enumeration: CommunicationIndicator..... | 267 | +| 5.10.2.3.4 | Enumeration: StationaryIndication..... | 267 | +| 5.10.2.3.5 | Enumeration: CpFailureCode..... | 267 | +| 5.10.2.3.6 | Enumeration: BatteryIndication..... | 268 | +| 5.10.2.3.7 | Enumeration: TrafficProfile..... | 268 | +| 5.10.2.3.8A | Enumeration: ScheduledCommunicationType..... | 268 | +| 5.10.3 | Resource structure..... | 269 | +| 5.10.3.1 | General..... | 269 | +| 5.10.3.2 | Resource: CP Provisioning Subscriptions..... | 269 | +| 5.10.3.2.1 | Introduction..... | 269 | +| 5.10.3.2.2 | Resource definition..... | 270 | +| 5.10.3.2.3 | Resource methods..... | 270 | +| 5.10.3.2.3.1 | GET..... | 270 | +| 5.10.3.2.3.2 | PUT..... | 271 | +| 5.10.3.2.3.3 | PATCH..... | 271 | +| 5.10.3.2.3.4 | POST..... | 271 | +| 5.10.3.2.3.5 | DELETE..... | 271 | +| 5.10.3.3 | Resource: Individual CP Provisioning Subscription..... | 272 | +| 5.10.3.3.1 | Introduction..... | 272 | +| 5.10.3.3.2 | Resource definition..... | 272 | +| 5.10.3.3.3 | Resource methods..... | 272 | +| 5.10.3.3.3.1 | GET..... | 272 | +| 5.10.3.3.3.2 | PUT..... | 273 | +| 5.10.3.3.3.3 | PATCH..... | 274 | +| 5.10.3.3.3.4 | POST..... | 274 | +| 5.10.3.3.3.5 | DELETE..... | 274 | +| 5.10.3.4 | Resource: Individual CP Set Provisioning..... | 275 | + +| | | | +|--------------|------------------------------------------------------|-----| +| 5.10.3.4.1 | Introduction..... | 275 | +| 5.10.3.4.2 | Resource definition..... | 275 | +| 5.10.3.4.3 | Resource methods..... | 275 | +| 5.10.3.4.3.1 | GET..... | 275 | +| 5.10.3.4.3.2 | PUT..... | 276 | +| 5.10.3.4.3.3 | PATCH..... | 277 | +| 5.10.3.4.3.4 | POST..... | 277 | +| 5.10.3.4.3.5 | DELETE..... | 277 | +| 5.10.4 | Used Features..... | 278 | +| 5.10.5 | Error handling..... | 278 | +| 5.10.5.1 | General..... | 278 | +| 5.10.5.2 | Protocol Errors..... | 278 | +| 5.10.5.3 | Application Errors..... | 278 | +| 5.11 | PfdManagement API..... | 279 | +| 5.11.1 | Overview..... | 279 | +| 5.11.2 | Data model..... | 279 | +| 5.11.2.1 | Resource data types..... | 279 | +| 5.11.2.1.1 | Introduction..... | 279 | +| 5.11.2.1.2 | Type: PfdManagement..... | 280 | +| 5.11.2.1.3 | Type: PfdData..... | 281 | +| 5.11.2.1.4 | Type: Pfd..... | 281 | +| 5.11.2.1.5 | Type: PfdReport..... | 282 | +| 5.11.2.1.6 | Type: UserPlaneLocationArea..... | 282 | +| 5.11.2.1.7 | Type: PfdManagementPatch..... | 283 | +| 5.11.2.2 | Referenced simple data types and enumerations..... | 283 | +| 5.11.2.2.1 | Introduction..... | 283 | +| 5.11.2.2.2 | Simple data types..... | 283 | +| 5.11.2.2.3 | Enumeration: FailureCode..... | 284 | +| 5.11.2.2.4 | Enumeration: DomainNameProtocol..... | 284 | +| 5.11.3 | Resource structure..... | 284 | +| 5.11.3.1 | General..... | 284 | +| 5.11.3.2 | Resource: PFD Management Transactions..... | 285 | +| 5.11.3.2.1 | Introduction..... | 285 | +| 5.11.3.2.2 | Resource definition..... | 285 | +| 5.11.3.2.3 | Resource methods..... | 286 | +| 5.11.3.2.3.1 | GET..... | 286 | +| 5.11.3.2.3.2 | PUT..... | 286 | +| 5.11.3.2.3.3 | POST..... | 287 | +| 5.11.3.2.3.4 | PATCH..... | 287 | +| 5.11.3.2.3.5 | DELETE..... | 287 | +| 5.11.3.3 | Resource: Individual PFD Management Transaction..... | 288 | +| 5.11.3.3.1 | Introduction..... | 288 | +| 5.11.3.3.2 | Resource definition..... | 288 | +| 5.11.3.3.3 | Resource methods..... | 288 | +| 5.11.3.3.3.1 | GET..... | 288 | +| 5.11.3.3.3.2 | PUT..... | 289 | +| 5.11.3.3.3.3 | PATCH..... | 290 | +| 5.11.3.3.3.4 | POST..... | 291 | +| 5.11.3.3.3.5 | DELETE..... | 291 | +| 5.11.3.4 | Resource: Individual Application PFD Management..... | 292 | +| 5.11.3.4.1 | Introduction..... | 292 | +| 5.11.3.4.2 | Resource definition..... | 292 | +| 5.11.3.4.3 | Resource methods..... | 293 | +| 5.11.3.4.3.1 | GET..... | 293 | +| 5.11.3.4.3.2 | PUT..... | 293 | +| 5.11.3.4.3.3 | PATCH..... | 294 | +| 5.11.3.4.3.4 | POST..... | 295 | +| 5.11.3.4.3.5 | DELETE..... | 295 | +| 5.11.3.5 | Void..... | 296 | +| 5.11.3.A | Notifications..... | 296 | +| 5.11.3.A.1 | General..... | 296 | + +| | | | +|---------------|-----------------------------------------------------|-----| +| 5.11.3A.2 | PFD Management Notification..... | 297 | +| 5.11.3A.2.1 | Description..... | 297 | +| 5.11.3A.2.2 | Target URI..... | 297 | +| 5.11.3A.2.3 | Standard Methods..... | 297 | +| 5.11.3A.2.3.1 | Notification via POST..... | 297 | +| 5.11.3A.2.3.2 | Notification via Websocket..... | 298 | +| 5.11.4 | Used Features..... | 298 | +| 5.11.5 | Error handling..... | 298 | +| 5.11.5.1 | General..... | 298 | +| 5.11.5.2 | Protocol Errors..... | 298 | +| 5.11.5.3 | Application Errors..... | 298 | +| 5.12 | ECRControl API..... | 299 | +| 5.12.1 | Overview..... | 299 | +| 5.12.2 | Data model..... | 299 | +| 5.12.2.1 | Data types..... | 299 | +| 5.12.2.1.1 | Introduction..... | 299 | +| 5.12.2.1.2 | Type: ECRControl..... | 299 | +| 5.12.2.1.3 | Type: ECRData..... | 300 | +| 5.12.2.1.4 | Type: PlmnEcRestrictionDataWb..... | 301 | +| 5.12.3 | Custom Operations without associated resources..... | 301 | +| 5.12.3.1 | Overview..... | 301 | +| 5.12.3.2 | Operation: query..... | 301 | +| 5.12.3.2.1 | Description..... | 301 | +| 5.12.3.2.2 | Operation Definition..... | 301 | +| 5.12.3.3 | Operation: configure..... | 302 | +| 5.12.3.3.1 | Description..... | 302 | +| 5.12.3.3.2 | Operation Definition..... | 303 | +| 5.12.4 | Used Features..... | 303 | +| 5.12.5 | Error handling..... | 304 | +| 5.12.5.1 | General..... | 304 | +| 5.12.5.2 | Protocol Errors..... | 304 | +| 5.12.5.3 | Application Errors..... | 304 | +| 5.13 | NpConfiguration API..... | 304 | +| 5.13.1 | Overview..... | 304 | +| 5.13.2 | Data model..... | 304 | +| 5.13.2.1 | Resource data types..... | 304 | +| 5.13.2.1.1 | Introduction..... | 304 | +| 5.13.2.1.2 | Type: NpConfiguration..... | 305 | +| 5.13.2.1.3 | Type: NpConfigurationPatch..... | 307 | +| 5.13.2.1.4 | Type: ConfigurationNotification..... | 307 | +| 5.13.3 | Resource structure..... | 308 | +| 5.13.3.1 | General..... | 308 | +| 5.13.3.2 | Resource: NP Configurations..... | 308 | +| 5.13.3.2.1 | Introduction..... | 308 | +| 5.13.3.2.2 | Resource definition..... | 308 | +| 5.13.3.2.3 | Resource methods..... | 308 | +| 5.13.3.2.3.1 | GET..... | 308 | +| 5.13.3.2.3.2 | PUT..... | 309 | +| 5.13.3.2.3.3 | PATCH..... | 309 | +| 5.13.3.2.3.4 | POST..... | 309 | +| 5.13.3.2.3.5 | DELETE..... | 310 | +| 5.13.3.3 | Resource: Individual NP Configuration..... | 310 | +| 5.13.3.3.1 | Introduction..... | 310 | +| 5.13.3.3.2 | Resource definition..... | 310 | +| 5.13.3.3.3 | Resource methods..... | 311 | +| 5.13.3.3.3.1 | GET..... | 311 | +| 5.13.3.3.3.2 | PUT..... | 311 | +| 5.13.3.3.3.3 | PATCH..... | 312 | +| 5.13.3.3.3.4 | POST..... | 313 | +| 5.13.3.3.3.5 | DELETE..... | 313 | +| 5.13.3.4 | Void..... | 314 | + +| | | | +|----------------|---------------------------------------------------------------------|-----| +| 5.13.3.A | Notifications..... | 314 | +| 5.13.3.A.1 | General..... | 314 | +| 5.13.3.A.2 | Configuration Notification..... | 315 | +| 5.13.3.A.2.1 | Description..... | 315 | +| 5.13.3.A.2.2 | Target URI..... | 315 | +| 5.13.3.A.2.3 | Standard Methods..... | 315 | +| 5.13.3.A.2.3.1 | Notification via POST..... | 315 | +| 5.13.3.A.2.3.2 | Notification via Websocket..... | 316 | +| 5.13.4 | Used Features..... | 316 | +| 5.13.5 | Error handling..... | 317 | +| 5.13.5.1 | General..... | 317 | +| 5.13.5.2 | Protocol Errors..... | 317 | +| 5.13.5.3 | Application Errors..... | 317 | +| 5.14 | AsSessionWithQoS API..... | 317 | +| 5.14.1 | Overview..... | 317 | +| 5.14.2 | Data model..... | 317 | +| 5.14.2.1 | Resource data types..... | 317 | +| 5.14.2.1.1 | Introduction..... | 317 | +| 5.14.2.1.2 | Type: AsSessionWithQoSSubscription..... | 320 | +| 5.14.2.1.3 | Type: AsSessionWithQoSSubscriptionPatch..... | 324 | +| 5.14.2.1.4 | Type: UserPlaneNotificationData..... | 327 | +| 5.14.2.1.5 | Type: UserPlaneEventReport..... | 327 | +| 5.14.2.1.6 | Type: QosMonitoringInformation..... | 330 | +| 5.14.2.1.7 | Type: QosMonitoringInformationRm..... | 331 | +| 5.14.2.1.8 | Type: QosMonitoringReport..... | 333 | +| 5.14.2.1.9 | Type: TscQoSRequirement..... | 334 | +| 5.14.2.1.10 | Type: TscQoSRequirementRm..... | 334 | +| 5.14.2.1.11 | Type AdditionalInfoAsSessionWithQos..... | 335 | +| 5.14.2.1.12 | Type: ProblemDetailsAsSessionWithQos..... | 335 | +| 5.14.2.1.13 | Type AsSessionMediaComponent..... | 335 | +| 5.14.2.1.14 | Type AsSessionMediaComponentRm..... | 337 | +| 5.14.2.1.15 | Type: MultiModalFlows..... | 339 | +| 5.14.2.1.16 | Type: UeAddInfo..... | 339 | +| 5.14.2.2 | Referenced simple data types and enumerations..... | 339 | +| 5.14.2.2.1 | Introduction..... | 339 | +| 5.14.2.2.2 | Simple data types..... | 339 | +| 5.14.2.2.3 | Enumeration: UserPlaneEvent..... | 339 | +| 5.14.3 | Resource structure..... | 340 | +| 5.14.3.1 | General..... | 340 | +| 5.14.3.2 | Resource: AS Session with Required QoS subscriptions..... | 341 | +| 5.14.3.2.1 | Introduction..... | 341 | +| 5.14.3.2.2 | Resource definition..... | 341 | +| 5.14.3.2.3 | Resource methods..... | 341 | +| 5.14.3.2.3.1 | GET..... | 341 | +| 5.14.3.2.3.2 | PUT..... | 342 | +| 5.14.3.2.3.3 | PATCH..... | 342 | +| 5.14.3.2.3.4 | POST..... | 342 | +| 5.14.3.2.3.5 | DELETE..... | 343 | +| 5.14.3.3 | Resource: Individual AS Session with Required QoS Subscription..... | 343 | +| 5.14.3.3.1 | Introduction..... | 343 | +| 5.14.3.3.2 | Resource definition..... | 343 | +| 5.14.3.3.3 | Resource methods..... | 344 | +| 5.14.3.3.3.1 | GET..... | 344 | +| 5.14.3.3.3.2 | PUT..... | 345 | +| 5.14.3.3.3.3 | PATCH..... | 346 | +| 5.14.3.3.3.4 | POST..... | 347 | +| 5.14.3.3.3.5 | DELETE..... | 347 | +| 5.14.3.4 | Void..... | 348 | +| 5.14.3.A | Notifications..... | 348 | +| 5.14.3.A.1 | General..... | 348 | +| 5.14.3.A.2 | Event Notification..... | 348 | + +| | | | +|----------------|-------------------------------------------------------|-----| +| 5.14.3.A.2.1 | Description..... | 348 | +| 5.14.3.A.2.2 | Target URI..... | 348 | +| 5.14.3.A.2.3 | Standard Methods..... | 348 | +| 5.14.3.A.2.3.1 | Notification via POST..... | 348 | +| 5.14.3.A.2.3.2 | Notification via Websocket..... | 349 | +| 5.14.4 | Used Features..... | 349 | +| 5.14.5 | Error handling..... | 351 | +| 5.14.5.1 | General..... | 351 | +| 5.14.5.2 | Protocol Errors..... | 351 | +| 5.14.5.3 | Application Errors..... | 351 | +| 5.15 | MsisdnLessMoSms API..... | 352 | +| 5.15.1 | Overview..... | 352 | +| 5.15.2 | Data model..... | 352 | +| 5.15.2.1 | Notification data types..... | 352 | +| 5.15.2.1.1 | Introduction..... | 352 | +| 5.15.2.1.2 | Type: MsisdnLessMoSmsNotification..... | 352 | +| 5.15.2.1.3 | Type: MsisdnLessMoSmsNotificationReply..... | 353 | +| 5.15.3 | Resource structure..... | 353 | +| 5.15.3.1 | General..... | 353 | +| 5.15.3.2 | MSISDN-less MO SMS Notification..... | 353 | +| 5.15.3.2.1 | Introduction..... | 353 | +| 5.15.3.2.2 | Resource definition..... | 354 | +| 5.15.3.2.3 | Standard methods..... | 354 | +| 5.15.3.2.3.1 | Notification via POST..... | 354 | +| 5.15.4 | Used Features..... | 355 | +| 5.15.5 | Error handling..... | 355 | +| 5.15.5.1 | General..... | 355 | +| 5.15.5.2 | Protocol Errors..... | 355 | +| 5.15.5.3 | Application Errors..... | 355 | +| 5.16 | RacsParameterProvisioning API..... | 355 | +| 5.16.1 | Overview..... | 355 | +| 5.16.2 | Data model..... | 356 | +| 5.16.2.1 | Resource data types..... | 356 | +| 5.16.2.1.1 | Introduction..... | 356 | +| 5.16.2.1.2 | Type: RacsProvisioningData..... | 356 | +| 5.16.2.1.3 | Type: RacsFailureReport..... | 357 | +| 5.16.2.1.4 | Type: RacsConfiguration..... | 357 | +| 5.16.2.1.5 | Type: RacsProvisioningDataPatch..... | 358 | +| 5.16.2.1.6 | Type: RacsConfigurationRm..... | 358 | +| 5.16.2.2 | Referenced simple data types and enumerations..... | 359 | +| 5.16.2.2.1 | Introduction..... | 359 | +| 5.16.2.2.2 | Simple data types..... | 359 | +| 5.16.2.2.3 | Enumeration: RacsFailureCode..... | 359 | +| 5.16.3 | Resource structure..... | 359 | +| 5.16.3.1 | General..... | 359 | +| 5.16.3.2 | Resource: RACS Parameter Provisionings..... | 360 | +| 5.16.3.2.1 | Introduction..... | 360 | +| 5.16.3.2.2 | Resource definition..... | 360 | +| 5.16.3.2.3 | Resource methods..... | 360 | +| 5.16.3.2.3.1 | GET..... | 360 | +| 5.16.3.2.3.2 | PUT..... | 361 | +| 5.16.3.2.3.3 | PATCH..... | 361 | +| 5.16.3.2.3.4 | POST..... | 361 | +| 5.16.3.2.3.5 | DELETE..... | 362 | +| 5.16.3.3 | Resource: Individual RACS Parameter Provisioning..... | 362 | +| 5.16.3.3.1 | Introduction..... | 362 | +| 5.16.3.3.2 | Resource definition..... | 362 | +| 5.16.3.3.3 | Resource methods..... | 362 | +| 5.16.3.3.3.1 | GET..... | 362 | +| 5.16.3.3.3.2 | PATCH..... | 363 | +| 5.16.3.3.3.3 | PUT..... | 364 | + +| | | | +|------------------------------------------------------------------------------------------------------|--------------------------------------------|------------| +| 5.16.3.3.3.4 | POST..... | 365 | +| 5.16.3.3.3.5 | DELETE..... | 365 | +| 5.16.4 | Used Features..... | 366 | +| 5.16.5 | Error handling..... | 366 | +| 5.16.5.1 | General..... | 366 | +| 5.16.5.2 | Protocol Errors..... | 366 | +| 5.16.5.3 | Application Errors..... | 366 | +| 6 | Security..... | 367 | +| 7 | Using Common API Framework..... | 367 | +| 7.1 | General..... | 367 | +| 7.2 | Security..... | 367 | +| Annex A (normative): OpenAPI representation for the APIs defined in the present document..... | | 369 | +| A.1 | General..... | 369 | +| A.2 | Data Types applicable to several APIs..... | 369 | +| A.3 | MonitoringEvent API..... | 378 | +| A.4 | ResourceManagementOfBdt API..... | 397 | +| A.5 | ChargeableParty API..... | 403 | +| A.6 | NIDD API..... | 408 | +| A.7 | DeviceTriggering API..... | 425 | +| A.8 | GMDViaMBMS APIs..... | 432 | +| A.8.1 | GMDviaMBMSbyMB2 API..... | 432 | +| A.8.2 | GMDviaMBMSbyxMB API..... | 444 | +| A.9 | ReportingNetworkStatus API..... | 454 | +| A.10 | CpProvisioning API..... | 460 | +| A.11 | PfdManagement API..... | 470 | +| A.12 | ECRControl API..... | 481 | +| A.13 | NpConfiguration API..... | 484 | +| A.14 | AsSessionWithQoS API..... | 490 | +| A.15 | MsisdnLessMoSms API..... | 506 | +| A.16 | RacsParameterProvisioning API..... | 507 | +| Annex B (informative): TS Skeleton Template..... | | 514 | +| Annex C (informative): Change history..... | | 515 | + +--- + +## 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 specification describes the protocol for the T8 reference point between the SCEF and the SCS/AS. The T8 reference point and the related stage 2 functional requirements are defined in 3GPP TS 23.682 [2]. + +# 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 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [3] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [4] Void. +- [5] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [6] Hypertext Transfer Protocol (HTTP) Status Code Registry at IANA, . +- [7] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". +- [8] IETF RFC 9457: "Problem Details for HTTP APIs". +- [9] 3GPP TS 29.154: "Service capability exposure functionality over Nt reference point". +- [10] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point". +- [11] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications". +- [12] 3GPP TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications". +- [13] 3GPP TS 29.201: "Representational State Transfer (REST) reference point between Application Function (AF) and Protocol Converter (PC)". +- [14] 3GPP TS 23.003: "Numbering, addressing and identification". +- [15] IETF RFC 3339: "Date and Time on the Internet: Timestamps". +- [16] IETF RFC 9112: "HTTP/1.1". +- [17] IETF RFC 9110: "HTTP Semantics". +- [18] Void. +- [19] Void. +- [20] IETF RFC 9111: "HTTP Caching". + +- [21] Void. +- [22] IETF RFC 9113: "HTTP/2". +- [23] 3GPP TS 29.155: "Traffic steering control; Representational state transfer (REST) over St reference point". +- [24] 3GPP TS 29.368: "Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)". +- [25] 3GPP TS 29.337: "Diameter-based T4 interface for communications with packet data networks and applications". +- [26] 3GPP TS 29.250: "Nu reference point between SCEF and PFDF for sponsored data connectivity". +- [27] Open API: "OpenAPI Specification Version 3.0.0", . +- [28] IETF RFC 1166: "Internet Numbers". +- [29] IETF RFC 5952: "A recommendation for Ipv6 address text representation". +- [30] 3GPP TS 29.153: "Service capability exposure functionality over Ns reference point". +- [31] 3GPP TS 24.250: "Protocol for Reliable Data Service; Stage 3". +- [32] IETF RFC 6455: "The Websocket Protocol". +- [33] 3GPP TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [34] 3GPP TS 29.338: "Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs)". +- [35] 3GPP TS 33.187: "Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements". +- [36] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE);MB2 Reference Point;Stage 3". +- [37] 3GPP TS 29.116: "Presentational state transfer over xMB reference point between Content Provider and BM-SC". +- [38] IETF RFC 5789: "PATCH method for HTTP". +- [39] IETF RFC 7396: "JSON Merge Patch". +- [40] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [41] YAML (10/2009): "YAML Ain't Markup Language (YAML™) Version 1.2", . +- [42] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3". +- [43] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [44] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [45] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3". +- [46] IETF RFC 6733: "Diameter Base Protocol". +- [47] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2". +- [48] 3GPP TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3". +- [49] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [50] 3GPP TS 29.554: "5G System; Background Data Transfer Policy Control Service; Stage 3". + +- [51] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [52] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3". +- [53] 3GPP TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs". +- [54] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [55] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); stage 2". +- [56] 3GPP TS 26.348, "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point". +- [57] 3GPP TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3". +- [58] 3GPP TR 21.900: "Technical Specification Group working methods". +- [59] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification". +- [60] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification". +- [61] 3GPP TS 29.675: "User Equipment (UE) radio capability provisioning service; Stage 3". +- [62] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3". +- [63] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3". +- [64] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3". +- [65] 3GPP TS 29.515: "5G System; Gateway Mobile Location Services; Stage 3". +- [66] IETF RFC 5322: "Internet Message Format". +- [67] IETF RFC 6902: "JavaScript Object Notation (JSON) Patch". +- [68] 3GPP TS 33.558: "Security aspects of enhancement of support for enabling edge applications; Stage 2". +- [69] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF". +- [70] 3GPP TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3". +- [71] IETF RFC 6901: "JavaScript Object Notation (JSON) Pointer". + +--- + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +### 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|------------------------------------------| +| AF | Application Function | +| AI/ML | Artificial Intelligence/Machine Learning | +| AS | Application Server | + +| | | +|----------|-------------------------------------------------------| +| ASP | Application Service Provider | +| BAT | Burst Arrival Time | +| BDT | Background Data Transfer | +| CAPIF | Common API Framework | +| CP | Communication Pattern | +| DDN | Downlink Data Notification | +| DNN | Data Network Name | +| DL | Downlink | +| eNB | Evolved Node B | +| GMD | Group Message Delivery | +| IMEI-TAC | Type Allocation Code part of an IMEI | +| IWK-SCEF | Interworking SCEF | +| JSON | JavaScript Object Notation | +| LC | Load Control | +| LCI | Load Control Information | +| MIME | Multipurpose Internet Mail Extensions | +| MT | Mobile Terminated | +| MTC | Machine Type Communications | +| MT-LR | Mobile Terminated Location Request | +| NEF | Network Exposure Function | +| NIDD | Non-IP Data Delivery | +| NP | Network Parameter | +| NSAC | Network Slice Admission Control | +| OCI | Overload Control Information | +| OLC | OverLoad Control | +| PCRF | Policy and Charging Rule Function | +| PDN | Packet Data Network | +| PDV | Packet Delay Variation | +| PFD | Packet Flow Description | +| PFDF | Packet Flow Description Function | +| RCAF | RAN Congestion Awareness Function | +| REST | Representational State Transfer | +| SACH | Service Announcement Channel | +| SCEF | Service Capability Exposure Function | +| SCS | Services Capability Server | +| S-NSSAI | Single Network Slice Selection Assistance Information | +| TAI | Tracking Area Identity | +| TLTRI | T8 Long Term Transaction Reference ID | +| TSC | Time Sensitive Communication | +| TSCAI | Time Sensitive Communication Assistance Information | +| WB | Wide Band | +| YAML | YAML Ain't Markup Language | + +--- + +## 4 T8 reference point + +### 4.1 Overview + +The T8 reference point is between the SCS/AS and the SCEF. It specifies APIs that allow the SCS/AS to access the services and capabilities provided by 3GPP network entities and securely exposed by the SCEF. + +This document also specifies the procedures triggered at the SCEF by API requests from the SCS/AS and by event notifications received from 3GPP network entities. + +The stage 2 level requirements and signalling flows for the T8 reference point are defined in 3GPP TS 23.682 [2]. + +The T8 reference point supports the following procedures: + +- Monitoring Procedures +- Procedures for resource management of Background Data Transfer + +- Procedures for changing the chargeable party +- Procedures for Non-IP Data Delivery +- Procedures for Device Triggering +- Procedures for Group Message Delivery +- Procedures for Reporting of Network Status +- Procedures for Communication Pattern Parameters Provisioning +- Procedures for PFD Management +- Procedures for Enhanced Coverage Restriction Control +- Procedures for Network Parameter Configuration +- Procedures for setting up an AS session with required QoS +- Procedures for MSISDN-less Mobile Originated SMS +- Procedures for RACS Parameter Provisioning + +## 4.2 Reference model + +The T8 reference point resides between the SCEF and the SCS/AS as depicted in figure 4.2.1. The overall SCEF architecture is depicted in clause 4.2 of 3GPP TS 23.682 [2]. + +NOTE: The SCS/AS can be provided by a third party. + +![Diagram of the T8 reference model showing the SCS/AS and SCEF connected by the T8 interface.](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +``` +graph TD; SCS/AS[SCS/AS] --- T8[T8]; T8 --- SCEF[SCEF]; +``` + +The diagram illustrates the T8 reference model. It consists of two rectangular boxes, one above the other, connected by a vertical line. The top box is labeled 'SCS/AS' and the bottom box is labeled 'SCEF'. The vertical line between them is labeled 'T8'. + +Diagram of the T8 reference model showing the SCS/AS and SCEF connected by the T8 interface. + +Figure 4.2.1: T8 reference model + +## 4.3 Functional elements + +### 4.3.1 SCEF + +The SCEF is a functional element which provides means to securely expose the services and capabilities provided by 3GPP network interfaces. The SCEF provides access to network capabilities through homogenous application programming interfaces. + +Individual instances of SCEF may vary depending on what service capabilities are exposed and what API features are supported. + +The SCEF shall protect the other PLMN entities (e.g. HSS, MME) from requests exceeding the permission arranged in the SLA with the third-party service provider. + +When needed, the SCEF supports mapping between information exchanged with SCS/AS (e.g. geographical identifiers) and information exchanged with internal PLMN functions (e.g. cell-Id, eNB-Id, TAI, MBMS SAI, etc.). This mapping is assumed to be provided by the SCEF based on local configuration data. + +## 4.3.2 SCS/AS + +The SCS is the entity which connects MTC application servers to the 3GPP network to enable them to communicate through specific 3GPP defined services with UEs used for MTC and with the SCEF in the HPLMN. The SCS offers capabilities for use by one or multiple MTC application servers. The MTC applications in the external network are hosted on one or more ASs. + +An SCS/AS can get services from multiple SCEFs, and an SCEF can provide services to multiple SCS/ASs. + +The SCS is controlled by the operator of the HPLMN or by a MTC Service Provider. + +The AS can be controlled by a 3rd party. + +## 4.4 Procedures over T8 reference point + +### 4.4.1 Introduction + +All procedures that operate across the T8 reference point, as specified in 3GPP TS 23.682 [2], are specified in the following clauses. + +### 4.4.2 Monitoring Procedures + +#### 4.4.2.1 General + +These procedures are used to perform event monitoring functions via the T8 interface, which include: + +- Monitoring event configuration as specified in clause 4.4.2.2; +- Reporting of monitoring event as specified in clause 4.4.2.3; +- Network initiated notifications of monitoring event cancellation, as specified in clause 4.4.2.4 ; and +- Network initiated notifications of applied parameter configuration, as specified in clause 4.4.2.5. + +#### 4.4.2.2 Monitoring Events Configuration + +##### 4.4.2.2.1 General + +In order to subscribe to a new monitoring event configuration, the SCS/AS shall send an HTTP POST request message to the SCEF targeting the "Monitoring Event Subscriptions" resource. The body of the HTTP POST request message shall include: + +- the SCS/AS Identifier; +- the Monitoring Type; +- the Notification Destination Address; and +- the identifier(s) of the targeted UE(s), i.e. one of External Identifier, MSISDN or External Group Identifier. The External Identifier or the MSISDN identifies the subscription of an individual UE and the External Group Identifier points to a group of UEs. + +and may include: + +- the Maximum Number of Reports; +- the Monitoring Duration indicated by the property "monitorExpireTime"; + +- the Group Reporting Guard Time; and +- additional Monitoring Type(s), if the subscription request targets multiple event(s). + +If the Subscription\_modification feature is supported, the SCS/AS may send an HTTP PUT message in order to update an existing monitoring event subscription. The HTTP PUT request targets the resource "Individual Monitoring Event Subscription" replacing all the properties in the existing configuration. The identifier(s) of the targeted UE(s) (i.e. "msisdn", "externalId" or "externalGroupId" attribute), the identifier of the MTC Provider (i.e. "mtcProviderId" attribute) and the supported features (i.e. "supportedFeatures" attribute) provided during the creation of the monitoring event subscription shall not be updated. Also, both the "requestTestNotification" and "websocketNotifConfig" attributes shall not be updated, if previously provided. + +For one-time monitoring type of requests, the SCS/AS shall include the Maximum Number of Reports with a value set to 1 and not include the Monitoring Duration in the HTTP request message sent to the SCEF. + +If the Subscription\_Patch feature is supported, the SCS/AS may send an HTTP PATCH request to request the modification of an existing "Individual Monitoring Event Subscription" resource, with the request body including the modification instructions which may include any applicable attributes (e.g. "notificationDestination", "monitorExpireTime"), except the provided UE Identifier (e.g. "msisdn", "externalId" or "externalGroupId"), "mtcProviderId" and "supportedFeatures" attributes. Also, both the "requestTestNotification" and "websocketNotifConfig" attributes shall not be modified, if previously provided. + +For a group of UEs, if the Partial\_group\_modification feature is supported, the SCS/AS may send an HTTP PATCH request message in order to cancel or add certain UE(s) within an active group. The HTTP PATCH request targets the resource "Individual Monitoring Event Subscription" updates with the corresponding "excludedExternalIds" and/or "excludedMsisdns" attributes in the existing configuration for partial group cancellation, and/or updates with the corresponding "addedExternalIds" and/or "addedMsisdns" attributes in the existing configuration for partial group addition. + +Upon reception of the HTTP POST, PUT or PATCH request message, if the SCS/AS is authorized to perform such request, the SCEF shall check whether the parameters (e.g. Maximum Number of Reports, Monitoring Duration, Maximum Latency, Maximum Response Time, suggested number of downlink packets in the HTTP POST or PUT request message) in the HTTP request body are within the range defined by operator policies. If one or more of these parameters are not within the range, the SCEF shall either: + +- reject the request message by sending an HTTP response to the SCS/AS with a status code set to "403 Forbidden" and may include in the response body the "PARAMETER\_OUT\_OF\_RANGE" application error within the "cause" attribute of the ProblemDetails data structure and indicate which parameters are out of the range within the "invalidParams" attribute of the "ProblemDetails" data structure; or +- modify the parameters which are not within the range by selecting different values which are within the range. + +For individual UE configuration requests, the SCEF shall also check whether the Idle Status Indication is included for the UE reachability event. If the Idle Status Indication is received in the request but not supported by the network, the SCEF may reject the request message by sending an HTTP response to the SCS/AS with a status code set to "403 Forbidden" and may include in the response body the "IDLE\_STATUS\_UNSUPPORTED" error within the "cause" attribute of the "ProblemDetails" structure. + +If the SCEF receives an HTTP POST request to create a subscription resource for a monitoring event, but without an indication of the support for the feature corresponding to the requested monitoring event, the SCEF shall reject the request by sending an HTTP "400 Bad Request" HTTP error response including the "EVENT\_FEATURE\_MISMATCH" application error within the "cause" attribute of the "ProblemDetails" structure. + +If the SCEF receives an HTTP POST request to create a subscription resource for a monitoring event that it does not support, the SCEF shall reject the request by sending an HTTP "500 Internal Server Error" HTTP error response including the "EVENT\_UNSUPPORTED" application error within the "cause" attribute of the "ProblemDetails" structure. + +If the "enNB" feature is supported: + +- if the SCEF receives an HTTP POST request to create a subscription resource for a monitoring event and determines that no more subscriptions are allowed for this client, the SCEF shall reject the request by sending an HTTP "403 Forbidden" error response including the "RESOURCES\_EXCEEDED" application error within the "cause" attribute of the "ProblemDetails" structure; and + +- if the SCEF receives an HTTP POST request to create a subscription resource for a monitoring event and determines that a duplicate subscription already exists for this client, the SCEF shall reject the request by sending an HTTP "400 Bad Request" error response including the "DUPLICATE\_REQUEST" application error within the "cause" attribute of the "ProblemDetails" structure. + +After validation, the SCEF shall store the parameters and: + +- may assign a SCEF Reference ID related to the created monitoring event subscription resource; and +- based on operator policies, shall: + - map the accuracy into permissible granularity for the location reporting event; and + - map the location area into a list of cells, eNodeB(s) and/or RAI(s)/TAI(s) and derive the corresponding MME(s)/SGSN(s), for number of UEs present in a geographic area event. + +In order to delete a previously active configured monitoring event subscription at the SCEF, the SCS/AS shall send an HTTP DELETE request message to the SCEF targeting the "Individual Monitoring Event Subscription" resource using the corresponding resource URI previously received in the response to the request that has created the monitoring events subscription resource. The SCEF shall then determine the SCEF Reference ID related to the active monitoring subscription resource, and if the SCS/AS is authorized to perform such request, the SCEF shall delete the targeted resource. + +#### 4.4.2.2.2 Monitoring Events Configuration via HSS + +##### 4.4.2.2.2.1 General + +The following monitoring events are applicable for the monitoring event configuration via HSS for an individual UE or a group of UEs: + +- Loss of connectivity; +- UE reachability; +- Location Reporting; +- Change of IMSI-IMEI(SV) Association; +- Roaming Status; +- Communication Failure; +- PDN connectivity status; +- Availability after DDN Failure; and +- API support capability. + +Only one-time reporting is supported if the "reachabilityType" attribute sets to "SMS" for the event "UE reachability" or if the "locationType" attribute sets to "LAST\_KNOWN\_LOCATION" for the event "Location Reporting" in the monitoring event request. + +##### 4.4.2.2.2.2 Configuration Request for an individual UE + +Upon receipt of a configuration request from the SCS/AS for an individual UE, the SCEF shall interact with the HSS via S6t, as specified in 3GPP TS 29.336 [11]. + +Upon receipt of a successful response from the HSS, + +- if it is a one-time monitoring request and the monitoring event report is received, the SCEF shall delete the associated configuration, send an HTTP response message to the SCS/AS with a "200 OK" status code and including the received monitoring event report(s) (more than one report may be provided if the "enNB" is supported). +- otherwise, the SCEF shall, + +- for an HTTP POST request, create a new "Individual Monitoring Event Subscription" resource addressed by the URI that contains the SCS/AS identifier and an SCEF-created subscription identifier, and send an HTTP response to the SCS/AS with a "201 Created" status code, containing the final suggested configuration parameter(s) (if modified), indication(s) of the discarded parameter(s) (if discarded), the monitoring event report(s) (more than one report may be provided if the "enNB" is supported), if received, and a location header field containing the URI of the created resource. +- for an HTTP PUT request, update the active "Individual Monitoring Event Subscription" resource addressed by the request URI and send an HTTP response to the SCS/AS with a "200 OK" status code, containing the final suggested configuration parameter(s) (if modified), indication(s) of the discarded parameter(s) (if discarded) and the monitoring event report(s) (more than one report may be provided if the "enNB" is supported), if received, or a "204 No Content" status code. +- for an HTTP DELETE request, delete the active "Individual Monitoring Event Subscription" resource addressed by the request URI and send an HTTP response to the SCS/AS with a "204 No Content" status code, or a "200 OK" status code and including the monitoring event report(s) (more than one report may be provided if the "enNB" is supported), if received. + +If the SCEF receives a response with an error code from the HSS, the SCEF shall not create, update nor delete the concerned resource and respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +#### 4.4.2.2.2.3 Configuration Request for a group of UEs + +Upon receipt of a request from the SCS/AS including an External Group Identifier, then the monitoring configuration is for a group of UEs. The SCEF shall interact with the HSS via S6t as specified in 3GPP TS 29.336 [11]. + +Upon receipt of a successful response from the HSS indicating that group processing is in progress and before beginning the processing of individual UEs, the SCEF shall, + +- for an HTTP POST request, create a new "Individual Monitoring Event Subscription" resource addressed by a URI that contains the SCS/AS identity and an SCEF-created subscription identifier, store the number of UEs received in the response message from the HSS within the resource and send an HTTP response to the SCS/AS with "201 Created" status code and a location header field containing the URI of the created resource, in order to acknowledge the SCS/AS of the successful group processing request. +- for an HTTP PUT request, update the active "Individual Monitoring Event Subscription" resource addressed by the request URL and send an HTTP response with "200 OK" status code to acknowledge the SCS/AS of the successful group processing request, or a "204 No Content" status code. +- for an HTTP DELETE request, delete the active "Individual Monitoring Event Subscription" resource addressed by the request URI and send an HTTP response to the SCS/AS with "204 No Content" status code. + +If the SCEF receives a response with an error code from the HSS, the SCEF shall not create, update nor delete the concerned resource and respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +Upon receipt of the processing result of the individual UEs from the HSS, the SCEF shall behave as follows: + +- if no Group Reporting Guard Time is received, the SCEF shall send an HTTP POST request message to the SCS/AS including a reference to the related monitoring subscription, a list of configuration failure result if received for the group members, and the "monitoringEventReports" attribute including a list of monitoring event reports if received for the group members; +- otherwise, the SCEF shall accumulate all of the configuration results and/or monitoring event reports received from the HSS for the group members until the Group Reporting Guard Time expires. Then the SCEF shall send an HTTP POST request message to the SCS/AS including a reference to the related monitoring subscription, and a list of configuration failure result if received for the group members, and the "monitoringEventReports" attribute including a list of monitoring event reports received before the Group Reporting Guard Time. +- If the Partial\_group\_modification feature is supported, + - upon the cancellation of UE(s) within the active group identified by the "excludedExternalIds" and/or "excludedMsisdns" attributes is successful, the SCEF shall, + +- if the maximum number of reports applies to the monitoring event configuration of the cancelled UE(s), set the stored number of reports of the indicated UE(s) to the maximum number of reports; +- still consider the rest of UE(s) as applicable within the active group based monitoring subscription to the group based Monitoring Event Report identified by the External Group Identifier; +- determine whether the reporting for the group based event subscription is completed or not. If completed, the SCEF shall delete the corresponding "Individual Monitoring Event Subscription" resource with procedures as described in clause 4.4.2.3. +- If the cancellation of UE(s) within the active group is unsuccessful, the SCEF shall respond with proper error code indicating the error and should return the appropriate additional error information in the POST response body. +- upon the addition of UE(s) within the active group identified by the "addedExternalIds" and/or "addedMsisdns" attributes is successful, the SCEF shall, + - still consider the existing of UE(s) as applicable within the active group based monitoring subscription to the group based Monitoring Event Report identified by the External Group Identifier; + - subsequently apply monitoring event subscription to the new group member UEs. +- If the addition of UE(s) within the active group is unsuccessful, the SCEF shall respond with proper error code indicating the error and should return the appropriate additional error information in the POST response body. + +The SCS/AS shall send an HTTP response to acknowledge the SCEF about the handling result of the received HTTP POST request. + +#### 4.4.2.2.3 Monitoring Events Configuration directly via MME/SGSN + +The monitoring event "Number of UEs in a geographic area" is applicable for the monitoring event configuration via MME/SGSN. Only one-time reporting is supported for this event with the value of Maximum Number of Reports indicated by "maximumNumberOfReports" set to 1. + +Upon receipt of an HTTP POST request from the SCS/AS, the SCEF shall + +- resolve the location area to the involved SGSN(s)/MME(s) by local configuration; +- interact with the HSS via the S6t interface as specified in 3GPP TS 29.336 [11] if the External Group ID(s) is included; and +- interact with the SGSN(s)/MME(s) via the T6a/b interface as specified in 3GPP TS 29.128 [12]. + +NOTE: The SCEF uses local configuration to resolve the involved SGSN(s)/MME(s) if the location area is not received. + +After collecting responses from the SGSN(s)/MME(s), if the SCEF does not receive any successful response from the involved SGSN(s)/MME(s), the SCEF shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6; otherwise the SCEF should send a response with 200 OK status code to acknowledge the SCS/AS with one aggregated report in the requested area by including the total count of the number of UEs in the "ueCount" attribute and the External Identifier(s) (if available) or the MSISDN(s) (if available) associated with the External Group ID. + +NOTE: It is possible that the number of UEs does not reflect the actual number of UEs in the designated area (e.g. some SGSN(s)/MME(s) do not respond successfully). The SCEF still provides the result to the SCS/AS if at least one SGSN/MME returns a successful response. + +#### 4.4.2.2.4 Monitoring Events Configuration via PCRF + +##### 4.4.2.2.4.1 General + +The following monitoring events: the location reporting event and communication failure event are applicable for the monitoring event configuration via PCRF for an individual UE. + +NOTE: If monitoring event configuration via PCRF is used for a subscription resource, the Subscription\_modification feature cannot be supported. + +Only the location reporting event is applicable for the monitoring event configuration via PCRF for a group of UEs. + +Only one-time reporting is supported for the monitoring event configuration via PCRF. + +HTTP PUT is not supported for the monitoring event configuration via PCRF. If it is received, the SCEF shall reject the HTTP PUT message with 403 Forbidden during monitoring and may indicate the "OPERATION\_PROHIBITED" error in the "cause" attribute of the "ProblemDetails" structure. + +#### 4.4.2.2.4.2 Configuration Request for an individual UE + +Upon receipt of an HTTP POST request from the SCS/AS for an individual UE, the SCEF shall: + +- interact with the PCRF via the Rx interface by using an existing AF session or establishing a new AF session as specified in 3GPP TS 29.214 [10]; + +NOTE 1: The SCEF can derive the service information over the Rx interface based on SCS/AS ID for communication failure event. + +- after receiving the AAA message from the PCRF, create a resource which represents the monitoring event configuration addressed by a URI that contains the SCS/AS identifier and an SCEF-created subscription identifier; and +- send a corresponding status code to acknowledge the SCS/AS of the successful processing of the request in the HTTP response message. + +Then the SCEF shall wait for the reporting from the PCRF as specified in 3GPP TS 29.214 [10]. + +NOTE 2: Different events can be reported in different messages according to 3GPP TS 29.214 [10], e.g. STR/RAR for communication failure. + +During configuration resource deletion, the SCEF shall also terminate the AF session if it was established and used only for event monitoring. + +#### 4.4.2.2.4.3 Configuration Request for a group of UEs + +Upon receipt of an HTTP POST request from the SCS/AS for a group of UEs, the SCEF shall: + +- interact with all PCRFs in the same PLMN via Nta application of Nt interface as specified in 3GPP TS 29.154 [9]; +- after collecting ECA message from all PCRFs, create a resource which represents the monitoring event configuration addressed by a URI that contains the SCS/AS identifier and an SCEF-created subscription identifier; and +- send a corresponding status code to acknowledge the SCS/AS of the successful processing of the request in the HTTP response message. + +Then the SCEF shall wait for the reporting from the PCRF(s) as specified in 3GPP TS 29.154 [9]. + +#### 4.4.2.3 Reporting of Monitoring Event Procedure + +Upon receipt of a Monitoring Event Report from the HSS or the MME/SGSN as defined in clause 5.6.3 or clause 5.6.8 of 3GPP TS 23.682 [2], from the PCRF as defined in clause 5.6.5 or from the IWK-SCEF as defined in clause 5.6.8 of 3GPP TS 23.682 [2], the SCEF shall determine the monitoring event subscription associated with the corresponding Monitoring Event Report. + +If the monitoring event subscription refers to a Monitoring Event Configuration for a single UE or to a group-based Monitoring Event configuration, and no Group Reporting Guard Time was set, then the SCEF shall send an HTTP POST message including a link to the SCEF-created subscription resource and the received Monitoring Event Report to the identified destination. If the monitoring event subscription refers to a group-based Monitoring Event Configuration and Group Reporting Guard Time was provided during the Monitoring Event configuration procedure, then the SCEF + +shall accumulate all of the received Monitoring Event reports for the group of UEs until the Group Reporting Guard Time expires or the monitoring duration indicated by the property "monitorExpireTime" is reached. + +Upon expiration of Group Reporting Guard Time or expiration of the monitoring duration, the SCEF shall send an HTTP POST message to the identified destination including a link to the SCEF-created subscription resource and the list of accumulated Monitoring Event Reports for each UE identified by either its External Identifier or MSISDN. The destination URL of the HTTP POST message is provided by the SCS/AS during the Monitoring Event Configuration procedure. + +If the monitoring event subscription refers to a one-time monitoring request or a continuous monitoring request, but the maximum number of reports is reached, the SCEF shall consider the reporting as completed, delete the corresponding "Individual Monitoring Event Subscription" resource and send an HTTP POST message including the subscription identifier and a cancellation indication to the identified destination. The cancellation indication shall set to "true" indicating to cancel the configured monitoring subscription. The destination URL of the HTTP POST is provided by the SCS/AS during the Monitoring Event Configuration procedure. In addition, the SCEF shall interact with the HSS to delete the event configuration if the latter was performed via the HSS whereas event reports were performed via the SGSN/MME. The SCEF determines that the reporting for a group is completed by comparing the total number of received reports with the number of UEs of the group (received from the HSS during event configuration for a group of UEs) multiplied by the maximum number of reports. + +If the Partial\_group\_modification feature is supported and one or more MSISDN(s) or External Identifier(s) within the active group based monitor subscription have been cancelled or added, the existing UE(s) within the active group based monitoring subscription are still applicable to the group based Monitoring Event Report identified by the External Group Identifier, the added group member(s) shall be subsequently applied with the monitoring event subscription. + +When the monitoring duration indicated by the property "monitorExpireTime" is reached, the SCEF shall delete the related event subscription and event configuration locally. The SCS/AS shall no longer address the corresponding "Individual Monitoring Event Subscription" resource. + +#### 4.4.2.4 Network-initiated Explicit Monitoring Event Deletion Procedure + +Upon receipt of an SCEF Reference ID for the event to be deleted from the HSS as defined in 3GPP TS 29.336 [11], the SCEF shall determine the subscription identifier associated with the indicated active monitoring subscription. Then the SCEF shall delete the related resource "Individual Monitoring Event Subscription", send an HTTP POST message including the subscription identifier and a cancellation indication to the identified destination. The cancellation indication shall set to "true" indicating to cancel the configured monitoring subscription. The destination URL of the HTTP POST is provided by the SCS/AS during the Monitoring Event Configuration procedure. + +If the Partial\_group\_cancellation feature is supported, upon receipt of one or more MSISDN(s) or External Identifier(s) for the group member(s) to be cancelled within the active group based event subscription from the HSS as defined in 3GPP TS 29.336 [11], the SCEF shall, + +- if the maximum number of reports applies to the monitoring event configuration, set the stored number of reports of the indicated UE(s) to the maximum number of reports; +- include the MSISDN(s) or External Identifier(s) to be cancelled in the MonitoringNotification Request to the destination URL provided by the SCS/AS during the Monitoring Event Configuration procedure; and +- determine whether the reporting for the group based event subscription is completed or not. If completed, the SCEF shall delete the corresponding "Individual Monitoring Event Subscription" resource with procedures as described in clause 4.4.2.3. + +NOTE: The above procedure can be triggered from the HSS due to parameter overwritten by Network Parameter Configuration. + +#### 4.4.2.5 Network initiated notification of applied parameter configuration + +For "LOSS\_OF\_CONNECTIVITY" and "UE\_REACHABILITY" events, if the "Enhanced\_param\_config" feature is supported and the SCEF receives the currently applied parameter configuration from the HSS, the SCEF shall notify the SCS/AS via an HTTP POST message including the parameter changes in the "appliedParam" attribute. + +#### 4.4.3 Procedures for resource management of Background Data Transfer + +These procedures are used by an SCS/AS to perform the resource management of background data transfer (BDT) to a set of UEs, i.e. the SCS/AS requests a time window and related conditions from the SCEF via the T8 interface. + +In order to create a resource for the background data transfer policy, the SCS/AS shall send an HTTP POST message to the SCEF for the "BDT Subscriptions" resource to negotiate the transfer policy. The body of the HTTP POST message shall include SCS/AS Identifier, Volume per UE (total volume for both DL and UL or separate volume for DL and/or UL), Number of UEs, Desired Time Window and optionally a location area information. + +After receiving the HTTP POST message, if the SCS/AS is authorized, the SCEF shall map the SCS/AS Identifier to ASP Identifier and negotiate the transfer policy with the PCRF as defined in 3GPP TS 29.154 [9]. After receiving the response including the determined transfer policies from the PCRF, the SCEF shall create a resource "Individual BDT Subscription" which represents the BDT subscription, addressed by a URI that contains the SCS/AS identifier and an SCEF-created subscription identifier, and shall respond to the SCS/AS with a 201 Created message, including a Location header field containing the URI for the created resource and a message body, which may also include Reference ID and a set of transfer policies. The SCS/AS shall use the URI received in the Location header in subsequent requests to the SCEF to refer to this background data transfer subscription. If the SCEF receives a response with an error code from the PCRF, the SCEF shall not create the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +The SCS/AS may also send an HTTP PUT message to the SCEF for the "Individual BDT Subscription" resource to request starting an update for negotiation of background data transfer policy. The body of the HTTP PUT message shall include data as described in the POST message. The external group identifier shall remain unchanged from previously provided value. After receiving such request, if the SCS/AS is authorized, the SCEF shall negotiate the transfer policy with the PCRF as defined in 3GPP TS 29.154 [9]. After receiving the response including the determined transfer policies from the PCRF, the SCEF shall send an HTTP response to the SCS/AS with a "200 OK" status code and shall include the Bdt data type in the response body, or with a "204 No Content" status code. If the SCEF receives a response with an error code from the PCRF, the SCEF shall not update the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +NOTE 1: The SCEF starts a new BDT policy negotiation in the Nt interface by sending the request to the PCRF without the previously associated BDT Reference ID. + +If more than one policy is included in the HTTP response, the SCS/AS shall send an HTTP PATCH message to inform the SCEF for the "Individual BDT Subscription" resource of the transfer policy selected by the SCS/AS. After receiving the HTTP PATCH message, the SCEF shall send an HTTP response to the SCS/AS with a "200 OK" status code and shall include the Bdt data type in the response body, or with a "204 No Content" status code, then the SCEF shall interact with the PCRF as defined in 3GPP TS 29.154 [9]. If the SCEF identifies any error (e.g. selected policy is not within the set of transfer policies), the SCEF shall not update the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +The SCS/AS may also send an HTTP DELETE message to the SCEF for the "Individual BDT Subscription" resource requesting to remove an individual resource identified by the URI received in the response to the request that has created resource a URI. After receiving such request, the SCEF shall delete the resource and send an HTTP response to the SCS/AS with a corresponding status code. + +NOTE 2: The SCEF can also remove the resource when the last window end time in transfer policies expires. + +#### 4.4.4 Procedures for changing the chargeable party at session set up or during the session + +This procedure is used by an SCS/AS to either request to sponsor the traffic from the beginning or to request becoming the chargeable party at a later point in time via the T8 interface. + +When setting up the connection between the AS and the UE via the SCEF, the SCS/AS shall send an HTTP POST request to the SCEF, targeting the "Chargeable Party Transactions" resource, to become the chargeable party for the session to be set up. The body of the HTTP POST message shall include the SCS/AS Identifier, UE IP address, IP Flow description, Sponsor ID, ASP ID, Sponsoring Status, notification destination URI identifying the recipient of notifications within the "notificationDestination" attribute and may include the time period and/or traffic volume used for sponsoring. The SCS/AS may also request to activate a previously selected policy of background data transfer by + +including the associated Reference ID in the body of the HTTP POST message. If the feature AppId is supported, either the Flow description or an external Application Identifier shall be included. + +After receiving the HTTP POST request, if the authorization performed by the SCEF is successful, the SCEF shall act as an AF and interact with the PCRF via the Rx interface, as defined in 3GPP TS 29.214 [10] or 3GPP TS 29.201 [13], to trigger a PCRF initiated IP-CAN Session Modification. The SCEF may map the SCS/AS Identifier to AF Application Identifier if the external Application Identifier is not provided and only one AF Application Identifier is mapped and may request to be notified about the traffic plane status based on local configuration. If the time period and/or traffic volume are received from the SCS/AS, the SCEF should subscribe with the PCRF to the USAGE\_REPORT event. + +If the "enNB" feature is supported, the SCEF may explicitly receive a list of event(s) that the SCS/AS requests to subscribe to. The SCEF shall subscribe to the corresponding PCRF event(s) (e.g. INDICATION\_OF\_SUCCESSFUL\_RESOURCE\_ALLOCATION) for the received event(s) (e.g. SUCCESSFUL\_RESOURCES\_ALLOCATION) except for SESSION\_TERMINATION. + +NOTE 1: PCRF does not need explicit subscription in order to notify Rx session termination. + +After receiving a successful response from the PCRF, the SCEF shall create a new "Individual Chargeable Party Transaction" resource, which represents the chargeable party transaction, addressed by a URI that contains the SCS/AS identity and an SCEF-created transaction identifier, and shall respond to the SCS/AS with a 201 Created status code, including a Location header field containing the URI of the created resource. The SCS/AS shall use the URI received in the Location header in subsequent requests to the SCEF to refer to this chargeable party transaction. If the SCEF receives a response with an error code from the PCRF, the SCEF shall not create a resource and respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +In order to update the sponsoring status of an established AS session, the SCS/AS shall send an HTTP PATCH message to the SCEF targeting the associated "Individual Chargeable Party Transaction" resource requesting to partial update a chargeable party transaction resource (e.g. change the Sponsoring Status, update the list of event(s) if the "enNB" feature is supported). When receiving the HTTP PATCH message, the SCEF shall make the change and interact with the PCRF to modify the Rx session as defined in 3GPP TS 29.214 [10] or 3GPP TS 29.201 [13]. After receiving a response with successful result code from the PCRF, the SCEF shall send an HTTP response to the SCS/AS with a "200 OK" status code and the result if any in the body of the HTTP response or a "204 No Content" status code. The accumulated usage received from the PCRF shall be included in the HTTP response with the "200 OK" status code if the SCS/AS requested to disable the sponsoring. If the SCEF receives a response with an error code from the PCRF, the SCEF shall not update the resource and respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +NOTE 2: The SCS/AS can assume a successful resource allocation upon receipt of the POST/PATCH response until the FAILED\_RESOURCES\_ALLOCATION event is received. + +NOTE 3: The SCS/AS can update the list of user plane event(s) only for one time specific events, i.e. INDICATION\_OF\_SUCCESSFUL\_RESOURCES\_ALLOCATION, INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION and USAGE\_REPORT events, as specified in clause 5.3.13 of 3GPP TS 29.214 [10]. + +If the SCEF receives a traffic plane notification (e.g. the usage threshold is reached or transmission resource lost) or gets informed that the Rx session is terminated (e.g. due to the release of PDN connection), the SCEF shall send an HTTP POST message including the notified event (e.g. session terminated) and the accumulated usage to the SCS/AS identified by the notification destination URI received during session set up. The SCS/AS shall respond with an HTTP response to confirm the received notification. + +In order to remove an established AS session, the SCS/AS shall send an HTTP DELETE message to the SCEF targeting the associated "Individual Chargeable Party Transaction" resource. After receiving the HTTP DELETE message, the SCEF shall remove all properties of the resource and interact with the PCRF to terminate the Rx session (as defined in 3GPP TS 29.214 [10] or 3GPP TS 29.201 [13]). After receiving the response from the PCRF, the SCEF shall send an HTTP response to the SCS/AS with a corresponding status code and the accumulated usage (if received from the PCRF). + +## 4.4.5 Procedures for Non-IP Data Delivery + +### 4.4.5.1 General + +This procedure is used by an SCS/AS to support the Non-IP Data Delivery (NIDD) via SCEF. It performs the NIDD configuration via the T8 interface. It also includes the mobile terminated (MT) and mobile originated (MO) communication with UEs via the T8 interface. It also includes the group message delivery via MT NIDD via the T8 interface and management of port numbers on UE and SCEF and their dynamic association with different applications. + +Error handling for the procedures in this clause shall be handled based on clause 5.2.6. + +### 4.4.5.2 NIDD Configuration + +#### 4.4.5.2.1 NIDD Configuration for a single UE + +For a NIDD configuration creation, the SCS/AS shall send an HTTP POST message to the SCEF for the "NIDD configurations" resource. The body of the HTTP POST message shall include External Identifier or MSISDN, SCS/AS Identifier, notification destination URI identifying the recipient of notification within the "notificationDestination" attribute and may include NIDD Duration, PDN Connection Establishment Option and Reliable Data Service Configuration. In addition, the SCS/AS may send non-IP data and its associated parameters (e.g. Priority) as described in clause 4.4.5.3.1 in the NIDD configuration creation request. The Reliable Data Service Configuration includes port numbers on UE and SCEF that are used to identify specific applications for data transfer between UE and SCS/AS and an indication if reliable data service acknowledgement is enabled or not. + +Upon receipt of the HTTP POST request from the SCS/AS to create a NIDD configuration, the SCEF shall check whether the SCS/AS is authenticated and authorized to create NIDD configuration, and also authorize the NIDD configuration. If authorization is successful, the SCEF shall interact with the HSS via S6t as specified in 3GPP TS 29.336 [11]. Upon receipt of the successful response from the HSS, the SCEF shall store the UE identity (IMSI and External Identifier or MSISDN) which is associated with the External Identifier or MSISDN and create a resource "Individual NIDD configuration", which represents the NIDD configuration, addressed by a URI that contains the SCS/AS identity and an SCEF-created NIDD configuration identifier, and shall respond to the SCS/AS with a 201 Created message, including a Location header field containing the URI for the created resource. The body of the response message shall include Maximum Packet Size and may include Reliable Data Service Indication. When the SCS/AS receives the URI in the Location header, it shall use this URI in subsequent requests to the SCEF to refer to this NIDD configuration. + +If the SCS/AS includes a downlink non-IP data together with the NIDD configuration creation, the SCEF shall also create the corresponding "Individual NIDD downlink data delivery" sub-resource(s) and send each of the sub-resource(s) within the "self" attribute in the "niddDownlinkDataTransfers" attribute together with the created resource "Individual NIDD configuration" which included in the Location header field in the HTTP POST response. When the SCS/AS receives the URI the "self" attribute in the "niddDownlinkDataTransfers" attribute, it shall use this URI in subsequent requests to the SCEF to refer to this downlink data delivery transfer. + +After sending the HTTP response to NIDD configuration request, the SCEF shall perform the procedure for individual MT NIDD as described in clause 4.4.5.3.1. + +NOTE: Any further interaction with the SCS/AS for the piggybacked individual MT NIDD is performed by the notification of NIDD downlink data delivery status. + +For a NIDD configuration modification, the SCS/AS shall send an HTTP PATCH message to the SCEF for the "Individual NIDD configuration" resource, using the URI received in the response to the request that has created the NIDD configuration resource. Upon receipt of the HTTP PATCH request from the SCS/AS to update the parameters of the NIDD configuration, the SCEF shall check whether the SCS/AS is authenticated and authorized to update NIDD configuration. If the authorization is successful, the SCEF shall verify that the resource to be modified already exists as identified by the URI. If the NIDD configuration resource is found, the SCEF shall update the NIDD configuration as requested. Upon successful update of the requested NIDD configuration including the interaction with the HSS via S6t as specified in 3GPP TS 29.336 [11], the SCEF shall respond to the SCS/AS with a 200 OK success message indicating that the NIDD configuration resource was successfully updated, or with a 204 No Content success message if the NIDD configuration modification is successful updated with no content in the PATCH response message body. + +For a NIDD configuration cancellation, the SCS/AS shall send an HTTP DELETE message to the SCEF for the "Individual NIDD configuration" resource, using the URI received in the response to the request that has created the + +NIDD configuration resource. Upon receipt of the HTTP DELETE message from the SCS/AS, the SCEF shall check whether the SCS/AS is authenticated and authorized to delete NIDD configuration. If the authorization is successful, the SCEF shall verify that the NIDD configuration resource identified by the URI already exists. If the configuration resource exists, the SCEF shall delete the requested configuration, and perform related NIDD procedure to EPC network elements if applicable. Upon successful deletion of requested NIDD configuration, the SCEF shall respond to the SCS/AS with a 200 OK success message indicating that the NIDD configuration was successfully cancelled. As an alternative to the 200 OK success message, the SCEF may send a 204 No Content success message without any message content to the SCS/AS. + +When the NIDD Duration expires, the SCEF may remove the associated NIDD configuration resource and all individual downlink data delivery resources under such NIDD configuration. + +#### 4.4.5.2.2 NIDD Configuration for a group of UEs + +The NIDD configuration procedure for a single UE as described in clause 4.4.5.2.1 shall be applicable for a group of UEs with the following differences: + +- The External Group Identifier shall be included in the POST request instead of MSISDN or External Identifier. +- After receiving the response message from the HSS, the SCEF shall store the list of UE identifiers (IMSI and External Identifier or MSISDN) which are associated with the External Group Identifier. +- The downlink non-IP data is not supported to be handled together with the NIDD configuration. + +#### 4.4.5.3 Mobile Terminated NIDD procedure + +##### 4.4.5.3.1 Mobile Terminated NIDD for a single UE + +If the SCS/AS needs to perform a downlink non-IP data delivery for a single UE, the SCS/AS shall send an HTTP POST message to the SCEF for the "NIDD downlink data deliveries" resource, identifying an existing NIDD configuration resource as parent resource. The body of the HTTP POST message shall include External Identifier or MSISDN and non-IP data and may include PDN Connection Establishment Option, Reliable Data Service Configuration, Maximum Latency and Priority. The Reliable Data Service Configuration includes port numbers on UE and SCEF that are used to identify a specific application for data transfer between UE and SCS/AS and an indication if reliable data service acknowledgement is enabled or not. + +Upon receipt of a HTTP POST request from the SCS/AS for a downlink data delivery for a single UE, the SCEF shall: + +- verify the NIDD configuration resource already exists based on the URI passed, if the configuration resource does not exist, the SCEF shall respond with a 404 Not Found response to reject the downlink data delivery, and +- check whether the SCS/AS is authorised to send NIDD requests, if not authorized, the SCEF shall respond with a 401 Unauthorized response to reject the downlink data delivery, and +- check whether the non-IP packet size is larger than the Maximum Packet Size that was provided to the SCS/AS during NIDD Configuration. If the packet is oversized, the SCEF shall respond with a 403 Forbidden response with a cause value "DATA\_TOO\_LARGE" in the "cause" attribute of the "ProblemDetails" data structure indicating received non-IP packet size is larger than "maximumPacketSize" of the NIDD configuration. +- if the Rds\_port\_verification feature is supported, check whether the RDS port numbers are within the configured RDS port list. If the RDS port numbers are unknown in the SCEF, the SCEF shall respond with a 403 Forbidden response with a cause value "RDS\_PORT\_UNKNOWN" in the "cause" attribute of the "ProblemDetails" data structure. + +If all above checks are successful, the SCEF shall determine the EPS Bearer Context based on the APN associated with the NIDD configuration and the User Identity. If the SCEF EPS bearer context is not found in the SCEF, depending on PDN Connection Establishment Option received in the POST request or from NIDD configuration, the SCEF may: + +- reject the request with an error message to the SCS/AS; +- send a Device Trigger to the UE as described in clause 4.4.6 without buffering the non-IP data and respond the SCS/AS with a 500 Internal Server Error response and a cause value "TRIGGERED" in the "cause" attribute of the "ProblemDetails" data structure; or + +- buffer the non-IP data and create the "Individual NIDD downlink data delivery" sub-resource, then send a 201 Created response to the SCS/AS. The response message also includes an indication of whether the Device Trigger procedure (as described in clause 4.4.6) was performed by the SCEF. A Location header shall be included in the response message that provides the URI of the resource identifying this individual downlink data delivery. The SCS/AS shall use the URI received in the Location header in subsequent requests to the SCEF to refer to this individual downlink data delivery for possible replacement or cancellation. The non-IP data shall be delivered when the non-IP PDN connection is established. + +If the SCEF EPS bearer context is found in the SCEF, the SCEF shall check if the SCS/AS has exceeded the quota or rate of data submission considering the number of existing buffered non-IP data and restriction in APN and serving PLMN rate control. If quota is reached, the SCEF shall respond the SCS/AS with a 403 Forbidden response and a cause value "QUOTA\_EXCEEDED" in the "cause" attribute of the "ProblemDetails" data structure indicating the reason for the failure condition. If rate limit is reached, the SCEF shall respond the SCS/AS with a 429 Too Many Requests response. + +If the check is passed, the SCEF shall continue the downlink non-IP data delivery procedure as the defined 3GPP TS 29.128 [12]. + +If the non-IP data delivery was successful, the SCEF shall send a 200 OK response to the HTTP POST request indicating the downlink non-IP data delivery is successful along with the acknowledge information; otherwise the SCEF may: + +- send a 500 Internal Server Error response and a cause value indicating the reason for the delivery failure within the "cause" attribute of the "ProblemDetails" data structure, i.e.: + 1. if delivery was unsuccessful due to timeout, the cause value "TIMEOUT"; or + 2. if delivery to the next hop was unsuccessful with the cause value "NEXT\_HOP"; or +- if the MME/SGSN indicates UE is temporary not reachable, either: + 1. buffer the non-IP data and create the "Individual NIDD downlink data delivery" sub-resource, then send a 201 Created response to the SCS/AS. The response may include a Requested Re-Transmission time to indicate the SCS/AS when the UE is expected to be reachable so that the SCEF re-transmits the buffered non-IP data; or + 2. send a 500 Internal Server Error response without buffering the non-IP data, and include a cause value "TEMPORARILY\_NOT\_REACHABLE" in the "cause" attribute of the "ProblemDetails" data structure indicating the downlink non-IP data delivery is performed but stopped since UE is temporarily unreachable. The response may include a Requested Re-Transmission time to indicate the SCS/AS when the UE is expected to be reachable so that the SCS/AS may prepare any re-transmission. + +If the MT\_NIDD\_modification\_cancellation feature is supported and the SCS/AS decides to replace the pending downlink data delivery in the SCEF, the SCS/AS shall send an HTTP PUT message to the SCEF, using the URI received in the response to the request that has created the individual downlink data delivery resource. The External Identifier or MSISDN shall remain unchanged from previous values. Upon receipt of the HTTP PUT request from the SCS/AS, the SCEF shall check whether a pending non-IP data exists with the same URI (i.e. resource exists). If it is found, the SCEF shall replace it with the new non-IP data and continue waiting for any message from the MME/SGSN for the UE indicating either the non-IP PDN connection is being established or the UE is reachable (such message may be an MO NIDD); otherwise the SCEF shall respond with a 409 Conflict response with a cause value "SENDING" in the "cause" attribute of the "ProblemDetails" data structure indicating replacement failure. If the buffered data is already delivered, the SCEF shall respond with a 404 Not Found response and include a cause value "ALREADY\_DELIVERED" in the "cause" attribute of the "ProblemDetails" data structure indicating replacement failure. If delivery was unsuccessful due to timeout, the SCEF shall respond with a 500 Internal Server Error response with a cause value "TIMEOUT" in the "cause" attribute of the "ProblemDetails" data structure. If delivery to the next hop was unsuccessful, the SCEF shall respond with a 500 Internal Server Error response with a cause value "NEXT\_HOP" in the "cause" attribute of the "ProblemDetails" data structure. + +If the "PatchUpdate" feature defined in clause 5.6.4 is supported and the SCS/AS decides to partially modify the pending downlink data delivery in the SCEF, the SCS/AS shall send an HTTP PATCH message to the SCEF to the URI received in the response to the request that has created the concerned individual downlink data delivery resource. The request body shall contain the NiddDownlinkDataTransferPatch data structure including only the attributes that shall be updated. Upon reception of this HTTP PATCH request from the SCS/AS, the SCEF shall check whether a pending non-IP data with the received URI exists (i.e. the resource exists). If it is found, the SCEF shall apply the requested + +modifications and continue waiting for any message from the MME/SGSN for the UE indicating either the non-IP PDN connection is being established or the UE is reachable (such message may be an MO NIDD); otherwise the SCEF shall respond with a "409 Conflict" status code including a cause value "SENDING" within the "cause" attribute of the "ProblemDetails" data structure to indicate modification failure. If the buffered data is already delivered, the SCEF shall respond with a "404 Not Found" status code including a cause value "ALREADY\_DELIVERED" within the "cause" attribute of the "ProblemDetails" data structure to indicate modification failure. If delivery was unsuccessful due to timeout, the SCEF shall respond with a 500 Internal Server Error status code with a cause value "TIMEOUT" in the "cause" attribute of the "ProblemDetails" data structure. If delivery to the next hop was unsuccessful, the SCEF shall respond with a 500 Internal Server Error status code with a cause value "NEXT\_HOP" in the "cause" attribute of the "ProblemDetails" data structure. + +If the MT\_NIDD\_modification\_cancellation feature is supported and the SCS/AS decides to cancel the pending downlink data delivery in the SCEF, the SCS/AS shall send an HTTP DELETE message to the SCEF, using the URI received in the response to the request that has created the individual downlink data delivery resource. Upon receipt of the HTTP DELETE request from the SCS/AS, the SCEF shall check whether a pending request exists with the same URI. If such non-IP data has not been delivered, the SCEF shall remove the individual downlink data delivery resource and respond with an HTTP 204 No Content response; otherwise the SCEF shall respond with a 404 Not Found response (i.e. data already delivered) with a cause value "ALREADY\_DELIVERED" in the "cause" attribute of the "ProblemDetails" data structure or 409 Conflict (i.e. data delivery ongoing) response with a cause value "SENDING" in the "cause" attribute of the "ProblemDetails" data structure, and include a cause value indicating cancellation failure. + +If a pending non-IP data is delivered by the SCEF (e.g. due to non-IP PDN connection establishment), and the SCEF gets the delivery result from the MME/SGSN, the SCEF shall remove the "Individual NIDD downlink data delivery" sub-resource and send an HTTP POST message to the SCS/AS, identified by the notification destination URI received during the NIDD configuration, to notify the delivery result for the pending non-IP data. Upon receipt of the request, the SCS/AS shall acknowledge the notification with an HTTP 200 OK or 204 No Content response. + +During MT NIDD delivery, if the UE indicates no support for RDS and the SCEF previously indicated RDS is enabled to the SCS/AS, the SCEF shall stop sending the non-IP data and send MT NIDD delivery notification with "FAILURE\_RDS\_DISABLED" delivery status. + +#### 4.4.5.3.2 Mobile Terminated NIDD for a group of UEs + +If the SCS/AS needs to perform a downlink non-IP data delivery to a group of UEs and if both the SCS/AS and the SCEF support GroupMessageDelivery feature as defined in clause 5.6.4, the SCS/AS shall send an HTTP POST request message to the SCEF for the "NIDD downlink data deliveries" resource, identifying an existing NIDD configuration resource as parent resource. The body of the HTTP POST request message shall include the External Group Identifier and the non-IP data, and may include Reliable Data Service Configuration, PDN Connection Establishment Option and Maximum Latency. + +Upon receipt of such an HTTP POST request from the SCS/AS requesting the group message delivery, the SCEF checks whether the SCS/AS is authorised to send NIDD requests, whether the non-IP packet size is larger than the Maximum Packet Size that was provided to the SCS/AS during NIDD Configuration and if the Rds\_port\_verification feature is supported whether the RDS port numbers are recognized. If any of those checks fails, the SCEF shall respond with a HTTP response with a cause value indicating the reason for the failure condition. If all checks are successful, the SCEF shall create an "Individual NIDD downlink data delivery" resource and sends a 201 Created response to the SCS/AS to acknowledge acceptance of the HTTP POST request. + +Then for each authorized External Identifier associated to the External Group Identifier which is retrieved from the HSS during preceding NIDD configuration procedure (as specified in clause 4.4.5.2.2), the SCEF shall determine the EPS Bearer Context based on the APN associated with the NIDD configuration and the User Identity and continue the procedure as described for MT NIDD for a single UE in clause 4.4.5.3.1 without sending downlink data delivery status notification for any individual UE to the SCS/AS. + +At the end of buffering (duration determined by the Maximum Latency or local policy) or after processing data delivery for all UEs in the group, the SCEF shall send an HTTP POST message to SCS/AS to indicate the aggregated result of data delivery of each UE. The body of the HTTP POST request message shall include MSISDN or External Identifier, Retransmission Time (optional) and delivery result for each UE. Upon receipt of the request, the SCS/AS shall acknowledge the request with an HTTP 200 OK or 204 No Content response. + +The MT\_NIDD\_modification\_cancellation feature is not supported for the group message delivery via NIDD. If a PUT or DELETE request is received for the "Individual NIDD downlink data delivery" resource which was created for a + +group of UEs, the SCEF shall reject the message with a 403 Forbidden response with a cause value "OPERATION\_PROHIBITED" in the "cause" attribute of the "ProblemDetails" data structure. + +During MT NIDD delivery, if the UE indicates no support for RDS and the SCEF previously indicated RDS is enabled to the SCS/AS, the SCEF shall stop sending the non-IP data for the indicated UE. In the aggregated MT NIDD delivery notification, the SCEF shall send "FAILURE\_RDS\_DISABLED" delivery status for each failed UE. + +#### 4.4.5.4 Mobile Originated NIDD procedure + +When the SCEF receives the non-IP data from MME/SGSN (or IWK-SCEF) as defined in 3GPP TS 29.128 [12], and finds an SCEF EPS bearer context and the associated NIDD configuration, the SCEF shall determine the SCS/AS by the corresponding NIDD configuration, and send an HTTP POST request to the SCS/AS identified by the Notification Destination Address received in the NIDD configuration to notify the uplink non-IP data. The body of the HTTP POST message shall include External Identifier or MSISDN, non-IP data, NIDD configuration identifier, Reliable Data Service Configuration (if available). The Reliable Data Service Configuration includes port numbers on UE and SCEF that are used to identify a specific application for data transfer between UE and SCS/AS and an indication if reliable data service acknowledgement is enabled or not. + +Upon receipt of the request, if the SCS/AS knows the NIDD configuration identified by the NIDD configuration identifier, the SCS/AS shall acknowledge a 200 OK or 204 No Content message to the SCEF. + +#### 4.4.5.5 NIDD Authorisation Update procedure + +When the SCEF receives a NIDD Authorisation Update Request message from HSS to update a user's NIDD authorisation as defined in 3GPP TS 29.336 [11], the SCEF shall determine the SCS/AS with the corresponding NIDD Configuration, and send an HTTP POST message to the SCS/AS to notify it of the NIDD Authorisation Update. The body of the HTTP POST message shall include External Identifier or MSISDN, NIDD configuration identifier and the NIDD configuration status. + +Upon receipt of the request, if the SCS/AS knows the corresponding NIDD configuration, then the SCS/AS shall acknowledge the request with an HTTP 200 OK or 204 No Content response. + +If the NIDD configuration is revoked by the HSS within the received NIDD Authorisation Update Request, the SCEF shall release the corresponding T6a/b PDN connection as specified in 3GPP TS 29.128 [12]. In this case, the SCEF shall reject any subsequent MT NIDD deliveries with a 403 Forbidden response. Or 404 Not Found is returned, if the SCEF locally removed the associated NIDD configuration resource when the configuration was revoked. + +If the RDS capability is changed, e.g. when the T6a/b PDN connection is established, the UE indicates no support for RDS but the SCEF previously indicated RDS is supported to the SCS/AS in the NIDD configuration procedure, the SCEF shall send an HTTP POST message to notify the SCS/AS that the NIDD status is active and RDS capability indication. The SCS/AS shall acknowledge the request with an HTTP 200 OK or 204 No Content response. + +If the Rds\_port\_verification feature is supported, before sending the MO NIDD to the SCS/AS as specified in clause 4.4.5.4, the SCEF shall check RDS port numbers (decoded from the uplink non-IP data according to 3GPP TS 24.250 [31]). If the RDS port numbers are not within the configured RDS port list, the SCEF shall notify the SCS/AS with NIDD status set to "RDS\_PORT\_UNKNOWN" and the unknown RDS port numbers. The SCS/AS shall acknowledge the request with an HTTP 200 OK or 204 No Content response. + +#### 4.4.5.6 Port Management Configuration + +##### 4.4.5.6.1 Port Reservation and Release + +As part of the Port Management configuration, operations to reserve a combination of port numbers, release a combination of port numbers, query the list of port numbers that are reserved and notification of reservation of a port number may be performed, if the Rds\_dynamic\_port feature is supported. + +Indication of the supported serialization formats by the SCS/AS, query of the supported and configured serialization formats by the SCS/AS, and notification of the supported and configured serialization formats by the SCS/AS may be performed if the Rds\_serialization\_format feature is supported. + +If the SCS/AS needs to reserve port numbers and associate them with an application, the SCS/AS shall send an HTTP PUT message to the SCEF, using the URI received in the response to the request that has created the NIDD + +configuration resource and the specific part of "/rds-ports/{portId}" as described in clause 5.6.3.9.2. The SCS/AS may use this operation to reserve port numbers on the UE and SCEF and associate them with an application. The SCS/AS may also use this operation to indicate the serialization formats that are supported by the SCS/AS on the port. Upon receipt of the HTTP PUT request from the SCS/AS, + +- if the "skipUeInquiry" is set to "false" and if the "individual ManagePort Configuration" resource already exists in the same NIDD configuration, the SCEF shall respond with a 403 Forbidden response with a cause value "PORT\_NOT\_FREE" in the "cause" attribute of the "ProblemDetails" data structure; otherwise, the SCEF shall interact with the UE via the SGSN/MME to reserve the port and optionally configure the serialization format by using RDS protocol as specified in 3GPP TS 24.250 [31] and return a 202 Accept response to the SCS/AS if successful response is received from the SGSN/MME. Then if the SCEF receives successful UE response, the SCEF shall create the "individual ManagePort Configuration" resource and notify the SCS/AS with the reserved port and configured serialization format as specified in clause 4.4.5.6.2, the SCEF shall also mark the resource is created by the SCS/AS; otherwise, the SCEF shall notify the SCS/AS about the currently reserved ports as specified in clause 4.4.5.6.2. +- if the "skipUeInquiry" is set to "true" and if the requested SCEF port already exists in an NIDD configuration within the same APN, the SCEF shall respond with a 403 Forbidden response with a cause value "PORT\_NOT\_FREE" in the "cause" attribute of the "ProblemDetails" data structure; otherwise, the SCEF shall create the "individual ManagePort Configuration" resource and send an HTTP 201 Created response to the SCS/AS, the SCEF shall also mark the resource is created by the SCS/AS and notify the UE by using RDS protocol as specified in 3GPP TS 24.250 [31]. + +If the SCEF is not able to configure a serialization format for the port and if the Rds\_serialization\_format feature is supported, the SCEF shall respond with a 500 Internal Server Error response with a cause value "SERIALIZATION\_FORMAT\_NOT\_SUPPORTED" in the "cause" attribute of the "ProblemDetails" data structure. + +If the SCS/AS needs to release port numbers associated with an application, the SCS/AS shall send an HTTP DELETE message to the SCEF, using the URI received in the response to the request that has created the "individual ManagePort Configuration" resource. Upon receipt of the HTTP DELETE request from the SCS/AS, if the "individual ManagePort Configuration" resource does not exist in the same NIDD configuration, the SCEF shall respond with a 404 Not Found response with a cause value "PORT\_NOT\_ASSOC\_WITH\_APP" in the "cause" attribute of the "ProblemDetails" data structure; otherwise if the "individual ManagePort Configuration" resource was created by the SCS/AS and + +- if the "skipUeInquiry" is set to "false", the SCEF shall interact with the UE via the SGSN/MME to release the port by using RDS protocol as specified in 3GPP TS 24.250 [31] and return 202 Accept to the SCS/AS if successful response is received from the SGSN/MME. Then upon receipt of the UE response, the SCEF shall notify the SCS/AS with the currently reserved ports as specified in clause 4.4.5.6.2. +- if the "skipUeInquiry" is set to "true", the SCEF shall delete the individual ManagePort Configuration resource and respond with an HTTP 204 No Content response to the SCS/AS. The SCEF shall also notify the UE by using RDS protocol as specified in 3GPP TS 24.250 [31]. + +If the HTTP DELETE request is received for the "Individual ManagePort Configuration" resource which was created by the UE, the SCEF shall reject the message with a 403 Forbidden response with a cause value "OPERATION\_PROHIBITED" in the "cause" attribute of the "ProblemDetails" data structure. + +If the "skipUeInquiry" is set to "false" and the SCEF is not able to interact with the UE because: + +- PDN connection is not established, the SCEF shall reject the HTTP PUT/DELETE request with a 500 Internal Server Error response with a cause value "NO\_PDN\_CONNECTION"; +- UE is not reachable, the SCEF shall reject the HTTP PUT/DELETE request with a 500 Internal Server Error response with a cause value "TEMPORARILY\_NOT\_REACHABLE". The response may include a Requested Re-Transmission time to indicate the SCS/AS when the UE is expected to be reachable so that the SCS/AS may prepare any re-configuration for the RDS port; or +- the interaction with the SGSN/MME is not successful, the SCEF shall reject the HTTP PUT/DELETE request with a 500 Internal Server Error and a proper cause value indicating the reason for the delivery failure. + +If the SCS/AS needs to read the port numbers and serialization formats that are associated with an application, the SCS/AS shall send an HTTP GET message to the SCEF, using the URI received in the response to the request that has created the NIDD configuration resource and the specific part of "/rds-ports/{portId}" as described in clause 5.6.3.9.2. + +#### 4.4.5.6.2 Port Notification + +If the SCEF needs to send the information about reserved ports and their configuration to the SCS/AS (e.g. due to 3GPP network created or released "individual ManagePort Configuration" resource upon UE triggered RDS port management procedures as specified in 3GPP TS 24.250 [31]), the SCEF shall send an HTTP POST message to the SCS/AS, using the URI received within the "notificationDestination" attribute in the NiddConfiguration resource. The body of the message is encoded in JSON format with the data structure defined in table 5.6.2.1.9-1. The SCS/AS shall acknowledge the HTTP POST request with an HTTP 200 OK or 204 No Content response. + +#### 4.4.6 Procedures for Device Triggering + +The procedures are used by the SCS/AS to deliver the device trigger via T8 interface. + +In order to create a new device trigger, the SCS/AS shall send an HTTP POST message to the SCEF for the "Device Triggering Transactions" resource. The body of the HTTP POST message shall include the External Identifier or MSISDN, validity period, priority, Application Port ID and trigger payload. + +Upon receipt of the corresponding HTTP POST message, the SCEF shall check if the SCS/AS is authorised to send a trigger request and if the SCS/AS has exceeded its quota or rate of trigger submission. The SCEF shall also resolve the External Identifier or MSISDN to IMSI and retrieve the "Routing Information" from HSS for the triggering delivery. If the authorisation check fails, or if the quota or rate of trigger submission was exceeded, or if there is no valid subscription information or if the "Routing Information" cannot be found, then the SCEF shall reject the request with an error message to the SCS/AS. Otherwise, the SCEF shall perform the device trigger procedure over Tsp as defined in 3GPP TS 29.368 [24] and T4 as defined in 3GPP TS 29.337 [25]. Upon completion of this procedure, the SCEF shall create a resource "Individual Device Triggering Transaction" which represents the triggering transaction, addressed by a URI that contains the SCS/AS identity and an SCEF-created transaction identifier, and shall respond to the SCS/AS with a 201 Created message, including the trigger and a Location header field containing the URI for the created resource. The SCS/AS shall use the URI received in the Location header in subsequent requests to the SCEF to refer to this device triggering transaction. + +In order to replace an existing device trigger, the SCS/AS shall send an HTTP PUT message to the SCEF for the "Individual Device Triggering Transaction" resource, using the URI received in the response to the request that has created the device triggering transaction resource. The body of the HTTP PUT message shall include the DeviceTriggering data structure containing the requested updates. The properties "msisdn" or "externalId" shall remain unchanged from the previously provided value. + +If the "PatchUpdate" feature defined in clause 5.7.4 is supported, in order to partially modify an existing Individual Device Triggering Transaction resource, the SCS/AS shall send an HTTP PATCH message to the SCEF targeting the concerned "Individual Device Triggering Transaction" resource, using the URI received in the response to the request that has created the concerned Individual Device Triggering Transaction resource. The body of the HTTP PATCH message shall include the DeviceTriggeringPatch data structure containing the requested modifications. + +After receiving the corresponding HTTP PUT / HTTP PATCH message from the SCS/AS, the SCEF shall check if the SCS/AS is authorised to replace/modify an existing device trigger and if the SCS/AS has not exceeded its quota or rate of trigger submission. If any of these checks fail, then the SCEF shall reject the message with a corresponding failure code as described in clause 5.2.6. Otherwise, the SCEF shall replace the device triggering with the SMS-SC by performing the device trigger replace procedure over Tsp as defined in 3GPP TS 29.368 [24] and T4 as defined in 3GPP TS 29.337 [25]. Upon completion of this procedure, the SCEF shall send an HTTP response to the SCS/AS with a "200 OK" status code and include the result in the body of the HTTP response or a "204 No Content" status code to indicate a successful trigger replacement/modification; otherwise, the SCEF shall send a corresponding failure code as described in clause 5.2.6. + +In order to recall an existing device trigger, the SCS/AS shall send an HTTP DELETE message to the SCEF for the "Individual Device Triggering Transaction" resource, using the URI received in the response to the request that has created the device triggering transaction resource. + +After receiving the corresponding HTTP DELETE message from the SCS/AS, the SCEF shall check if the SCS/AS is authorised to send a recall trigger request and if the SCS/AS has not exceeded its quota or rate of trigger submission. The SCEF shall also check if the device triggering transaction resource referenced by the URI exists. If any of these checks fail, then the SCEF shall reject the message with an error. Otherwise, the SCEF shall recall the device triggering with the SMS-SC by performing the device trigger recall procedure over Tsp as defined in 3GPP TS 29.368 [24] and T4 as defined in 3GPP TS 29.337 [25]. Upon completion of this procedure, the SCEF shall send an HTTP response to the SCS/AS to indicate trigger recall success or failure. + +When it receives the Message Delivery Report from the SMS/SC, the SCEF shall send an HTTP POST message to the SCS/AS to report the trigger delivery result. The body of the HTTP POST message shall include the identifier if the transaction and cause. The SCS/AS shall respond with an HTTP 200 OK or 204 No Content response. + +## 4.4.7 Procedures for Group Message Delivery + +### 4.4.7.1 General + +This procedure is used by an SCS/AS to deliver a payload to a group of UEs. Two methods of Group Message Delivery via the T8 are specified: + +- Group Message Delivery via MBMS which is intended to efficiently distribute the same content to the members of a group that are located in a particular geographical area when MBMS is used. This method further includes two varieties: + - the MB2 interface (see stage 2 in 3GPP TS 23.468 [55] and stage 3 in 3GPP TS 29.468 [36]) is used as southbound interface; + - the xMB interface (see stage 2 in 3GPP TS 26.348 [56] and stage 3 in 3GPP TS 29.116 [37]) is used as southbound interface. +- Group Message Delivery via unicast MT NIDD for UEs which are part of the same External Group Identifier. + +NOTE: Group Message Delivery via MT NIDD is defined in clause 4.4.5.3.2. + +Error handling for the procedures in the subsequent clauses shall be handled based on clause 5.2.6. + +### 4.4.7.2 Group Message Delivery via MBMS + +#### 4.4.7.2.1 General + +This procedure is used by an SCS/AS to deliver a payload to a group of UEs via the T8 interface. The SCEF use the Group Message Delivery via MBMS to efficiently distribute the same content to the members of a group that are located in a particular geographical area when MBMS is used. + +The procedure of Group message Delivery via MBMS and MB2 used as southbound interface is described in caluse 4.4.7.2.2 and the procedure of Group message Delivery via MBMS and xMB used as southbound interface is described in caluse 4.4.7.2.3. + +#### 4.4.7.2.2 Group Message Delivery via MBMS by MB2 + +##### 4.4.7.2.2.1 TMGI Allocation + +If the SCS/AS acts as a GCS AS in the application level and if there is no assigned TMGI for an External Group Identifier, the SCS/AS shall send an HTTP message to the SCEF to the resource "TMGI Allocation". The body of the HTTP POST request message shall include the External Group Identifier. The SCS/AS may also include the location information in the body. + +Upon receipt of the HTTP POST request from the SCS/AS to allocate a TMGI, the SCEF shall check whether the SCS/AS is authorized to request TMGI allocation. If authorization is successful, the SCEF shall initiate TMGI allocation by the BM-SC as defined in clause 5.2.1 of 3GPP TS 29.468 [36]. Upon successful allocation of a TMGI, the SCEF shall create the resource which represents the TMGI allocation, addressed by a URI that contains the SCS identity and TMGI, and shall respond to the SCS/AS with a 201 Created message including the TMGI and the TMGI expiration time. + +In order to renew the TMGI expiration time, the SCS/AS shall send an HTTP PUT or PATCH message to the SCEF to the resource "Individual TMGI Allocation". Upon receipt of the HTTP PUT or PATCH request from the SCS/AS to renew TMGI expiration time, the SCEF shall initiate TMGI expiration time renewal to the BM-SC as defined in clause 5.2.1 of 3GPP TS 29.468 [36]. Upon successful result, the SCEF shall update the resource and respond to the SCS/AS by sending an HTTP response with 200 OK including the new TMGI expiration time or 204 No Content if the + +required TMGI expiration time renewal is successful with no content in the HTTP PUT or PATCH response message body. + +If the SCEF receives the response with an error code from the BM-SC for the allocation of TMGI or renewal of expiration time for the existing TMGI, the SCEF shall not create or update the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +Upon the TMGI expiration, the SCEF may delete the resource of the TMGI locally. + +Upon receipt of the notification of TMGI expiration by the BM-SC as defined in clause 5.2.3 of 3GPP TS 29.468 [36], the SCEF shall delete the resource if not yet deleted. + +#### 4.4.7.2.2.2 TMGI Deallocation + +In order to deallocate the TMGI, the SCS/AS shall send an HTTP DELETE message to the SCEF to the resource "Individual TMGI Allocation". Upon receipt of the HTTP DELETE request from the SCS/AS to deallocate the TMGI, the SCEF shall initiate TMGI deallocation by the BM-SC as defined in clause 5.2.2 of 3GPP TS 29.468 [36]. Upon successful deallocation of a TMGI, the SCEF shall delete the resource "Individual TMGI Allocation" together with all sub-resources "GMD via MBMS by MB2" if available, and shall respond to the SCS/AS by sending an HTTP response with 204 No Content. + +#### 4.4.7.2.2.3 Creation of group message delivery + +If the SCS/AS acts as a GCS AS in the application level and if the SCS/AS has an assigned TMGI for the External Group Identifier, in order to perform the group message delivery, the SCS/AS shall send an HTTP POST request message to the SCEF to the resource "GMD via MBMS by MB2". The body of the HTTP POST request message shall include the External Group Identifier and notification destination URI identifying the recipient of notification within the "notificationDestination" attribute. The SCS/AS may also include the Group Message Payload, the location information and a Message Delivery Start Time in the body. + +The SCS/AS may also send an HTTP POST message to the SCEF directly to the resource "TMGI Allocation" without previously requesting TMGI allocation as defined in clause 4.4.7.2.2. The SCEF shall create the resource "Individual TMGI Allocation" and perform the procedure as defined in clause 4.4.7.2.2, and shall also create resource "GMD via MBMS by MB2" and perform the procedure as mentioned in this subclause for MBMS bearer creation. + +Upon receipt of the HTTP POST request from the SCS/AS to deliver the group message, the SCEF shall check whether the SCS/AS is authorized to send a group message request. It also checks to see if the Message Delivery Start Time does not start after the TMGI expiration. If authorization is successful, the SCEF shall initiate the Active MBMS Bearer procedure as defined in clause 5.3.2 of 3GPP TS 29.468 [36] with the difference that the SCEF acts as a GCS AS. The SCEF shall include the location information based on the local configuration if the location information is not provided in the HTTP POST request message. + +Upon successful activation of MBMS bearer, the SCEF shall create resource which represents "Individual GMD via MBMS by MB2", addressed by a URI that contains Transaction Id allocated by the SCEF and respond to the SCS/AS by sending an HTTP response with a 201 Created status code, including a Location header field containing the URI for the created resource. When the SCS/AS receives the URI in the Location header, it shall use this URI in subsequent requests to the SCEF to refer to this active MBMS bearer. If the Group Message Payload was not included in the HTTP POST above, the HTTP response sent from the SCEF shall also include the SCEF message delivery IPv4 address or IPv6 address and port number. + +If the SCEF receives the response with an error code from the BM-SC for the activation of MBMS bearer, the SCEF shall not create the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +If the Group Message Payload was included in the HTTP POST above, the SCEF shall deliver to BM-SC the Group Message Payload(s) as defined in 3GPP TS 29.468 [36] at Message Delivery Start Time. + +If the Group Message Payload was not included in the HTTP POST above, the SCEF shall transfer the contents received from the SCS/AS to the BM-SC at or after the requested Group Message Start Time, but before the TMGI Expiration time. In this case, when the SCEF detects the group message delivery was triggered successful, the SCEF shall send an HTTP POST request message to the SCS/AS. + +NOTE: If Group Message Payload was included, then at Message Delivery Start Time, the SCEF delivers to BM-SC the Group Message Payload(s) to corresponding to MB2-U IP address and port number associated with respective TMGI. + +#### 4.4.7.2.2.4 Modification of previous submitted group message delivery + +If the SCS/AS determines that modification of previous accepted Group Message Delivery Request is required, the SCS/AS shall send an HTTP PATCH or HTTP PUT request message to the SCEF to the resource "Individual GMD via MBMS by MB2". The body of the HTTP PATCH request message shall include the Message Delivery Start Time. The SCS/AS may also include the External Group Identifier, the Group Message Payload and the location information in the body. The body of the HTTP PUT request message shall include the information as the information provided in the HTTP POST in clause 4.4.7.2.2.2.3. The body of the HTTP PATCH request message shall include the information defined in the data type of GMDViaMBMSByMb2Patch as defined in clause 5.8.2.1.1.6. + +Upon receipt of the HTTP PATCH or HTTP PUT request from the SCS/AS to modify the previous group message delivery subscription, the SCEF shall check whether the SCS/AS is authenticated and authorized to modify the submitted group message delivery. If the authorization is successful, the SCEF shall initiate the Modify MBMS Bearer procedure as defined in clause 5.3.4 of 3GPP TS 29.468 [36] with the difference that the SCEF acts as a GCS AS. The SCEF shall include the location information based on the local configuration if the location information is not provided in the HTTP PATCH or HTTP PUT request message. + +Upon successful modification of MBMS bearer, the SCEF shall update the resource and respond to the SCS/AS with a 200 OK success message indicating that previous group message delivery subscription is successfully updated, or 204 No Content if the updates or replacement is successful with no content in the HTTP PATCH or HTTP PUT response message body. + +If the SCEF receives the response with an error code from the BM-SC for the modification of MBMS bearer, the SCEF shall not update the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +#### 4.4.7.2.2.5 Cancellation of previous submitted group message delivery + +If the SCS/AS determines that deletion of previous accepted Group Message Delivery Request is required, the SCS/AS shall send an HTTP DELETE request message to the SCEF. + +Upon receipt of the HTTP DELETE request from the SCS/AS to delete the previous group message delivery, the SCEF shall check whether the SCS/AS is authenticated and authorized to delete an existing group message delivery subscription. If the authorization is successful, the SCEF shall initiate the Delete MBMS Bearer procedure as defined in clause 5.3.3 of 3GPP TS 29.468 [36] with the difference that the SCEF acts as a GCS AS. + +Upon successful deletion of MBMS bearer, the SCEF shall respond to the SCS/AS with a 204 No Content message indicating that submitted group message delivery is successfully deleted. + +#### 4.4.7.2.3 Group message Delivery via MBMS by xMB + +##### 4.4.7.2.3.1 Service Creation + +If the SCS/AS acts as a content provider in the application level and if there is no assigned Service ID for an External Group Identifier, the SCS/AS shall send an HTTP POST message to the SCEF to the resource "xMB Services". The body of the HTTP POST request message shall include the External Group Identifier. + +Upon receipt of the HTTP POST request from the SCS/AS to create a service, the SCEF shall check whether the SCS/AS is authorized to request service creation. If authorization is successful, the SCEF shall initiate service creation by the BM-SC as defined in clause 5.2.1.2.2 of 3GPP TS 29.116 [37]. Upon successful service creation, the SCEF shall create the resource which represents the service creation, addressed by a URI that contains the SCS identity and Service Id, and shall respond to the SCS/AS with a 201 Created message which may include the service announcement information. + +If the SCEF receives the response with an error status code from the BM-SC for the service creation, the SCEF shall not create or update the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +#### 4.4.7.2.3.2 Service Deletion + +In order to delete the service, the SCS/AS shall send an HTTP DELETE message to the SCEF to the resource "Individual xMB Service". Upon receipt of the HTTP DELETE request from the SCS/AS to delete the service, the SCEF shall initiate service deletion by the BM-SC as defined in clause 5.2.1.2.4 of 3GPP TS 29.116 [37]. Upon successful deletion of a service, the SCEF shall delete the resource "Individual xMB Service" together with all sub-resources "GMD via MBMS by xMB" if available, and shall respond to the SCS/AS by sending an HTTP response with 204 No Content. + +#### 4.4.7.2.3.3 Creation of group message delivery + +If the SCS/AS acts as a content provider in the application level, the SCS/AS may send an HTTP POST request message to the SCEF to the resource "GMD via MBMS by xMB". The body of the HTTP POST request message shall include the External Group Identifier and notification destination URI identifying the recipient of notification within the "notificationDestination" attribute. The SCS/AS may also include the Group Message Payload, the location information, a Message Delivery Start Time and Message Delivery Stop Time in the body. + +Upon receipt of the HTTP POST request from the SCS/AS to deliver the group message, the SCEF shall check whether the SCS/AS is authorized to send a group message request. It also checks to see if the Message Delivery Start Time doesn't start after the Message Delivery Stop Time. If authorization is successful, the SCEF shall initiate the Create Session procedure as defined in clause 4.4.5.2 of 3GPP TS 29.116 [37] and the Update Session procedure as defined in clause 4.4.5.3 of 3GPP TS 29.116 [37] with the difference that the SCEF acts as a Content Provider, Session Start is set according to the Message Delivery Start Time and the Session Stop is set according to the Message Delivery Stop Time. The SCEF shall include the location information based on the local configuration if the location information is not provided and include the session type set to "Files" in the HTTP POST request message. + +Upon successful activation of MBMS bearer, the SCEF shall create resource which represents "Individual GMD via MBMS by xMB ", addressed by a URI that contains Transaction Id allocated by the SCEF and respond to the SCS/AS by sending an HTTP response with a 201 Created status code, including a Location header field containing the URI for the created resource. When the SCS/AS receives the URI in the Location header, it shall use this URI in subsequent requests to the SCEF to refer to this active MBMS bearer. If the Group Message Payload was not included in the HTTP POST above, the HTTP response sent from the SCEF shall also include the SCEF message delivery IPv4 address or IPv6 address and port number. + +If the SCEF receives the response with an error code from the BM-SC for the activation of MBMS bearer, the SCEF shall not create the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +If the Group Message Payload was included the HTTP POST above, the SCEF shall deliver to BM-SC the Group Message Payload(s) as defined in 3GPP TS 29.468 [36] at Message Delivery Start Time. + +If the Group Message Payload was not included in the HTTP POST above, the SCEF shall transfer the contents received from the SCS/AS to the BM-SC at or after the requested Message Delivery Start Time, but before the Message Delivery Stop Time. In this case, when the SCEF detects the group message delivery was triggered successful, the SCEF shall send an HTTP POST request message to the SCS/AS. + +#### 4.4.7.2.3.4 Modification of previous submitted group message delivery + +If the SCS/AS determines that modification of previous accepted Group Message Delivery Request is required, the SCS/AS shall send an HTTP PATCH or HTTP PUT request message to the SCEF to the resource "Individual GMD via MBMS by xMB ". The body of the HTTP PATCH request message shall include the Message Delivery Start Time and Message Delivery Stop Time. The SCS/AS may also include the External Group Identifier, the Group Message Payload and the location information in the body. The body of the HTTP PUT request message shall include the information as the information provided in the HTTP POST in clause 4.4.7.2.3.3. The body of the HTTP PATCH request message shall include the information defined in the data type of GMDViaMBMSByxMBPatch as defined in clause 5.8.3.1.1.4. + +Upon receipt of the HTTP PATCH or HTTP PUT request from the SCS/AS to modify the previous group message delivery subscription, the SCEF shall check whether the SCS/AS is authenticated and authorized to modify the submitted group message delivery. If the authorization is successful, the SCEF shall initiate the Update Session procedure as defined in clause 4.4.5.3 of 3GPP TS 29.116 [37] with the difference that the SCEF acts as a Content Provider, Session Start is set according to the Message Delivery Start Time and the Session Stop is set according to the Message Delivery Stop Time. The SCEF shall include the location information based on the local configuration if the location information is not provided in the HTTP PATCH or HTTP PUT request message. + +Upon successful modification of MBMS bearer, the SCEF shall respond to the SCS/AS with a 200 OK success message indicating that previous group message delivery subscription is successfully updated or with a 204 No Content success message if no content in the HTTP PUT or PATCH response message body. + +If the SCEF receives the response with an error code from the BM-SC for the modification of MBMS bearer, the SCEF shall not update the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +#### 4.4.7.2.3.5 Cancellation of previous submitted group message delivery + +If the SCS/AS determines that deletion of previous accepted Group Message Delivery Request is required, the SCS/AS shall send an HTTP DELETE request message to the SCEF. + +Upon receipt of the HTTP DELETE request from the SCS/AS to delete the previous group message delivery, the SCEF shall check whether the SCS/AS is authenticated and authorized to delete an existing group message delivery subscription. If the authorization is successful, the SCEF shall initiate the Delete Session procedure as defined in clause 4.4.5.4 of 3GPP TS 29.116 [37] with the difference that the SCEF acts as a Content Provider. + +Upon successful deletion of MBMS bearer, the SCEF shall respond to the SCS/AS with a 204 No Content message indicating that submitted group message delivery is successfully deleted. + +### 4.4.8 Procedures for Reporting of Network Status + +#### 4.4.8.1 General + +These procedures are used by an SCS/AS to perform reporting of network status via the T8 interface in one time or continuous reporting cases. The SCEF uses the reporting procedures based on the network status information from one or more RCAFs. These procedures can also be used by the SCS/AS to indicate the removal of a previously subscribed reporting request. + +#### 4.4.8.2 Network Status Reporting Subscription + +In order to create a new subscription to request for notifications on network status, the SCS/AS shall send an HTTP POST request message to the SCEF on the "Network Status Reporting Subscriptions" resource. The body of the HTTP POST request shall include a Notification destination address and Location area information, and may include the time duration and threshold(s). + +Upon receiving the HTTP POST request message from the SCS/AS, the SCEF shall check: + +- if the SCS/AS is authorized to perform the request. If not, the SCEF shall respond to the SCS/AS with an HTTP "401 Unauthorized" status code. +- if the SCS/AS has exceeded its quota of submitting requests. If so the SCEF shall respond to the SCS/AS with an HTTP "403 Forbidden" status code and may indicate the failure reason "QUOTA\_EXCEEDED" (i.e. the quota exceeded) within the "cause" attribute of the ProblemDetails data structure in the HTTP POST response. +- if the SCS/AS has exceeded its rate of submitting requests. If so the SCEF shall respond to the SCS/AS with an HTTP "429 Too Many Requests" status code in the HTTP POST response. + +After the SCEF authorized the HTTP request message, the SCEF shall create an "Individual Network Status Reporting Subscription" resource which represents the subscription, addressed by a URI that contains the SCS/AS identity and an SCEF-created subscription identifier, and shall respond to the SCS/AS with an HTTP "201 Created" status code, including a Location header field containing the URI for the created resource, to acknowledge to the SCS/AS the successful subscription creation. The SCS/AS shall use the URI received in the Location header in subsequent requests to the SCEF to refer to this network status reporting subscription. Then, the SCEF shall trigger the network status reporting procedure with the RCAF over Ns interface as defined in 3GPP TS 29.153 [30]. + +In order to update an existing subscription of continuous network status reporting, the SCS/AS shall send an HTTP PUT request message to the SCEF on the "Individual Network Status Reporting Subscription" resource, using the URI received in the response to the request that has created the network status reporting subscription resource. After receiving the HTTP PUT request message, the SCEF shall send an HTTP PUT response to the SCS/AS with an HTTP "200 OK" status code including a representation of the updated "Individual Network Status Reporting Subscription" + +resource in the response body, or a "204 No Content" status code. Then, the SCEF shall apply the requested updates and interact with the RCAF as defined in 3GPP TS 29.153 [30]. + +If the "PatchUpdate" feature defined in clause 5.9.4 is supported, in order to partially modify an existing subscription of continuous network status reporting, the SCS/AS shall send an HTTP PATCH request message to the SCEF on the "Individual Network Status Reporting Subscription" resource, using the URI received in the response to the request that has created the network status reporting subscription resource. The request body shall contain the NetStatusRepSubsPatch data structure including only the attributes that shall be updated. After receiving the HTTP PATCH request message, the SCEF shall send an HTTP response to the SCS/AS with an HTTP "200 OK" status code including a representation of the modified "Individual Network Status Reporting Subscription" resource in the response body, or a "204 No Content" status code. Then, the SCEF shall apply the requested changes and interact with the RCAF as defined in 3GPP TS 29.153 [30]. + +**NOTE:** In order to update an existing subscription, the SCEF needs to send a cancellation to the previously associated RCAF(s) to remove the related SCEF instructions and then send a new request with updated parameters. + +In order to remove an existing subscription of continuous network status reporting, the SCS/AS shall send an HTTP DELETE request message to the SCEF on the "Individual Network Status Reporting Subscription" resource, using the URI received in the response to the request that has created the network status reporting subscription resource. Upon reception of the HTTP DELETE request message, the SCEF shall send an HTTP DELETE response to the SCS/AS with an HTTP "204 No Content" status code. Then, the SCEF shall interact with the RCAF to terminate the continuous reporting of network status as defined in 3GPP TS 29.153 [30]. + +#### 4.4.8.3 Network Status Reporting Notification + +After receiving reports from all the involved RCAF(s) as defined in 3GPP TS 29.153 [30], the SCEF shall send an HTTP POST message to the SCS/AS using the identified destination URL, which is provided by the SCS/AS during the network status reporting subscription. The body of HTTP POST message shall include the NSI. + +#### 4.4.9 Procedures for Communication Pattern Parameters Provisioning + +One or more set of CP parameters may be provisioned by the SCS/AS for a single UE or a group of UEs. + +In order to create resources for one or more CP parameter set(s), the SCS/AS shall send an HTTP POST message to the SCEF for the "CP Provisioning Subscriptions" resource, including one or more new provisioned CP parameter set(s). The body of HTTP POST message shall include External Identifier or MSISDN for a single UE or External Group ID for a group of UEs, SCS/AS Identifier and one or more set of CP information associated with CP parameter set Id(s). + +After receiving the HTTP POST message, the SCEF shall check if the SCS/AS is authorised. The SCEF may also check if the number of CP parameter sets(s) reaches the limitation based on operator policy or configuration. + +After validation, the SCEF shall for each received CP parameter set Id, assign an SCEF Reference ID which may be derived from the CP parameter set Id, and send Update CP Parameter Request message to the HSS for delivering the CP parameter set(s) as specified in 3GPP TS 29.336 [11]. + +After receiving result from the HSS, if the result is successful, the SCEF shall create a resource "Individual CP Provisioning Subscription" and the corresponding sub-resources "Individual CP Set Provisioning" each represents a successfully provisioned CP parameter set indicated by the HSS and respond to the SCS/AS with a "201 Created" including Location header field containing the URI for the created subscription resource "Individual CP Provisioning Subscription" and the sub-resource(s) "Individual CP Set Provisioning" corresponding to each successful CP parameter set within the "self" attribute in the "cpParameterSet" attribute; otherwise, the SCEF shall not create any resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. If not all CP parameters sets are provisioned successfully (i.e. the HSS indicates failure for some or all CP parameter sets and/or the SCEF does not accept the CP parameter provisioning (e.g. one or more CP Set Identifiers in the request are already present in existing subscriptions)), the SCEF shall also include CP report(s) within attribute "cpReports" with a list of failed CP Set Identifier(s) and the corresponding failure code as specified in table 5.10.2.3.5-1 in the body of the HTTP response. + +In order to add new CP parameter set(s), update and/or remove the existing CP parameter set(s) for one or more CP parameter set Id(s), the SCS/AS may send an HTTP PUT message to the SCEF for the "Individual CP Provisioning Subscription" resource requesting to add new CP parameter set(s) by creating new resource(s), change some created properties (e.g. Validity Time) of the existing resource(s), and/or remove some or entire properties of the existing + +resource(s). After receiving the HTTP PUT message, the SCEF shall send the CP parameter changes to the HSS as specified in 3GPP TS 29.336 [11]. After receiving the response from the HSS with a successful code, if the HSS indicates all CP parameter sets or some CP parameter sets are provisioned successfully, the SCEF shall create or update the corresponding sub-resource(s) "Individual CP Set Provisioning" each represents a successfully provisioned CP parameter set indicated by the HSS and send an HTTP response to the SCS/AS with a "200 OK" status code and include a list of successful CP parameter set(s) in the body of the HTTP response, or a "204 No Content" status code. Otherwise, the SCEF shall not create or update the resource(s) and shall send an HTTP response to the SCS/AS with a corresponding failure code as described in clause 5.2.6. If not all CP parameters sets are provisioned successfully (i.e. the HSS indicates failure for some or all CP parameter sets and/or the SCEF does not accept the CP parameter provisioning (e.g. one or more CP Set Identifiers in the request are already present in existing subscriptions)), the SCEF shall also include CP report(s) within attribute "cpReports" with a list of failed CP Set Identifier(s) and the corresponding failure code as specified in table 5.10.2.3.5-1 in the body of the HTTP response. + +The SCS/AS may send a HTTP PUT message to the SCEF for the "Individual CP Set Provisioning" resource requesting to replace an individual resource identified by the CP parameter set Id. The body of the HTTP PUT message shall include set of CP information. After receiving such request, the SCEF shall interact with the HSS as specified in 3GPP TS 29.336 [11]. After receiving the response from the HSS with a successful code, the SCEF shall update the resource and send an HTTP response to the SCS/AS with a "200 OK" status code or a "204 No Content" status code; otherwise, the SCEF shall not update the resource and shall send an HTTP response to the SCS/AS with a corresponding failure code as described in clause 5.2.6. If the provisioning of the CP set fails (i.e. the HSS returns failure for the CP set or the SCEF does not accept the CP set provisioning), the SCEF shall reject the request with a corresponding status code, and include the attribute "cpReports" with the corresponding failure code as specified in table 5.10.2.3.5-1 and the CP Set Identifier for which the provisioning has failed. + +The SCS/AS may send an HTTP DELETE message to the SCEF requesting to delete an individual CP set resource "Individual CP Set Provisioning". After receiving such request, the SCEF shall determine the SCEF Reference ID for Deletion associated with the CP parameter set Id, and interact with the HSS as specified in 3GPP TS 29.336 [11]. After receiving the response from the HSS, the SCEF shall delete the addressed resource and send an HTTP response to the SCS/AS with a "204 No Content" status code. + +The SCS/AS may send an HTTP DELETE message to the SCEF requesting to delete an individual subscription resource "Individual CP Provisioning Subscription". After receiving such request, the SCEF shall determine the SCEF Reference ID (s) for Deletion associated with the CP parameter set Id(s) and interact with the HSS as specified in 3GPP TS 29.336 [11]. After receiving the response from the HSS, the SCEF shall delete the addressed resource and its sub-resources addressed by "Individual CP Set Provisioning" and send an HTTP response to the SCS/AS with a "204 No Content" status code. + +## 4.4.10 Procedures for PFD Management + +The PFDs associated with application identifier(s) may be created, updated or removed by the third party SCS/AS as defined in 3GPP TS 23.682 [2]. + +In order to create PFDs resources for one or more external Application Identifier(s), the SCS/AS shall send an HTTP POST message to the request URI of the resource "PFD Management Transactions" including one or more set of PFDs for external Application Identifier(s). The body of the HTTP POST message shall include external Application Identifier(s) and PFDs associated with its PFD Identifier(s), an Allowed Delay may be included for the external Application Identifier(s) as well. + +After receiving the HTTP POST message, if the SCS/AS is authorized, the SCEF shall provision the PFDs to the PFDF as defined in 3GPP TS 29.250 [26]. When receiving the response from the PFDF, the SCEF shall send an HTTP response to the SCS/AS with a corresponding status code. If one or more external application identifiers are provisioned successfully, the SCEF shall create an "Individual PFD Management Transaction" resource for the request and he corresponding sub-resources "Individual Application PFD Management" each represents a successfully provisioned external application identifier. The SCEF shall respond to the SCS/AS with a 201 Created including Location header field containing the URI for the created transaction resource "Individual PFD Management Transaction" and the sub-resource(s) "Individual Application PFD Management" corresponding to each external application identifier within the "self" attribute in the "PfdData" data type, the SCEF shall also include PFD report(s) with a list of external Application Identifier(s) and result(s) in the body of the HTTP response if some application(s) are not provisioned successfully (i.e. the PFDF returns failure and/or the SCEF does not accept the PFD provisioning (e.g. one or more external Application Identifiers in the request are already present in existing transactions)). + +In order to update the PFDs for an existing individual transaction, the SCS/AS shall send an HTTP PUT message to URI of the resource "Individual PFD Management Transaction" including one or more set of PFDs for external Application Identifier(s). After receiving the HTTP PUT message, the SCEF shall make the change and send the change to the PFDF (i.e. add/update/remove PFDs) as defined in 3GPP TS 29.250 [26]. After receiving the response from the PFDF, the SCEF shall send an HTTP response to the SCS/AS with a corresponding status code. The SCEF shall create or update the corresponding sub-resource(s) "Individual Application PFD Management" each represents a successfully provisioned external application identifier, and also include PFD report(s) with a list of external Application Identifier(s) and result(s) in the body of the HTTP response if some application(s) are not provisioned successfully (i.e. the PFDF returns failure and/or the SCEF does not accept the PFD provisioning (e.g. one or more external Application Identifiers in the request are already present in existing transactions)). + +NOTE 1: When the PUT for "Individual PFD Management Transaction" is received in the SCEF, SCEF can use partial update or full update towards the PFDF. + +If the "PatchUpdate" feature defined in clause 5.11.4 is supported, in order to partially modify an existing PFD Management Transaction, the SCS/AS shall send an HTTP PATCH request message to the SCEF on the "Individual PFD Management Transaction" resource, using the URI received in the response to the request that has created the concerned PFD Management Transaction resource. The request body shall contain the PfdManagementPatch data structure including only the attributes that shall be updated. After receiving the HTTP PATCH request, the SCEF shall apply the requested modifications and interact with the concerned PFDF to add/update/remove PFD(s) as defined in 3GPP TS 29.250 [26]. After receiving the response of the PFDF, the SCEF shall send an HTTP response to the SCS/AS with a corresponding status code. The SCEF shall then create or update the corresponding "Individual Application PFD Management" sub-resource(s), with each represents a successfully provisioned external application identifier. If some application(s) are not provisioned successfully (i.e. the PFDF returns a failure and/or the SCEF does not accept the PFD provisioning (e.g. one or more external Application Identifiers in the request are already present in existing transactions)), the SCEF shall also include PFD report(s) containing a list of external Application Identifier(s) and result(s) in the body of the HTTP response. + +In order to remove the PFDs for an existing individual transaction, the SCS/AS shall send an HTTP DELETE message to the URI of the resource "Individual PFD Management Transaction". After receiving such request, the SCEF shall delete the "Individual PFD Management Transaction" resource and its "Individual Application PFD Management" sub-resource(s), and shall interact with the PFDF as defined in 3GPP TS 29.250 [26]. After receiving the response from the PFDF, the SCEF shall send an HTTP response to the SCS/AS with a corresponding status code. + +For the POST message to the resource "PFD Management Transactions" or the PUT message to the resource "Individual PFD Management Transaction", if the provisioning of all application(s) fails (i.e. the PFDF returns failure and/or the SCEF does not accept the PFD provisioning), the SCEF shall respond with 500 Internal Server Error status code, and include the attribute "pfdReports" with the corresponding failure reason as specified in table 5.11.2.2.3-1 and the external Application Identifier(s) for which the provisioning has failed. + +In order to update the PFDs for an existing external Application Identifier, the SCS/AS shall send an HTTP PUT message to the resource "Individual Application PFD Management" to update the full set of PFDs of an existing resource. After receiving the HTTP PUT message, the SCEF shall make the change and send the change to the PFDF (i.e. add/update/remove PFDs) as defined in 3GPP TS 29.250 [26]. After receiving the response from the PFDF, the SCEF shall send an HTTP response to the SCS/AS with a corresponding status code. + +NOTE 2: When the PUT for "Individual Application PFD Management" is received in the SCEF, SCEF can use partial update or full update towards the PFDF. + +In order to update the PFDs for an existing external Application Identifier, the SCS/AS may also send an HTTP PATCH message to URI of the resource "Individual Application PFD Management" to partially update PFDs. After receiving the HTTP PATCH message, the SCEF shall make the change and send the change to the PFDF (i.e. add/update/remove PFDs) as defined in 3GPP TS 29.250 [26]. After receiving the response from the PFDF, the SCEF shall send an HTTP response to the SCS/AS with a corresponding status code. + +In order to remove the PFDs for an existing individual application, the SCS/AS shall send an HTTP DELETE message to the resource "Individual Application PFD Management". After receiving such request, the SCEF shall delete the resource and interact with the PFDF as defined in 3GPP TS 29.250 [26]. After receiving the response from the PFDF, the SCEF shall send an HTTP response to the SCS/AS with a corresponding status code. + +For the PUT/PATCH message to the resource "Individual Application PFD Management", if the provisioning of the application fails (i.e. the PFDF returns failure or the SCEF does not accept the PFD provisioning), the SCEF shall reject + +the request with a corresponding status code, and include the attribute "pfdReports" with the corresponding failure code as specified in table 5.11.2.2.3-1 and the external Application Identifier for which the provisioning has failed. + +If the SCEF receives PFD management notification including the PFD failure report from the PFDF (as defined in 3GPP TS 29.250 [26]) and if the feature PfdMgmtNotification is supported, the SCEF shall notify the SCS/AS with an HTTP POST message, identified by the notification destination URI received during the PFD provisioning, to notify the failure result for the PFD management by including the PfdReport data type in the body of the message. Within the PfdReport data type, the SCEF shall include the impacted application id(s) within the "externalAppIds" attribute, the "failureCode" attribute set to "PARTIAL\_FAILURE". In addition, if the SCEF receives the location area(s) of PCEF/TDF(s) which are unable to enforce the PFD(s) from the PFDF, the SCEF shall include the location area(s) within the "locationArea" attribute of the PFD report(s). After receiving the HTTP POST message, the SCS/AS shall send a HTTP response with "204 No Content" status code. + +NOTE 3: How the SCS/AS reacts to the failed PFD provisioning is left to implementation. + +NOTE 4: The SCEF maps the 3GPP network area(s) to the geographic area(s) or civic address(es) if the 3GPP network area(s) is not allowed to be exposed to the 3rd party according to the operator policy. + +#### 4.4.11 Procedures for Enhanced Coverage Restriction Control + +The procedures are used by an SCS/AS to query the status of, or to configure the enhanced coverage restriction for a UE via the T8 interface as defined in 3GPP TS 23.682 [2]. + +In order to query the current status of enhanced coverage restriction, the SCS/AS shall send an HTTP POST message to the SCEF using the query custom operation as defined in clause 5.12.13.2. The body of the HTTP POST message shall include External Identifier or MSISDN. + +In order to configure the enhanced coverage restriction, the SCS/AS shall send an HTTP POST message to the SCEF using the configure custom operation as defined in clause 5.12.13.3. The body of the HTTP POST message shall include External Identifier or MSISDN and the Enhanced Coverage Restriction setting (i.e. allowed-PLMN-List or restricted-PLMN-List). + +Upon receiving the HTTP POST message from the SCS/AS, the SCEF shall check: + +- if the SCS/AS is authorized to perform the request. If not the SCEF shall respond to the SCS/AS with a status code set to 401 Unauthorized. +- if the request is malformed. If it is malformed, the SCEF shall respond to the SCS/AS with a status code set to 400 Bad Request. +- if the SCS/AS has exceeded its quota of submitting requests. If so the SCEF shall respond to the SCS/AS with a status code set to 403 Forbidden and may indicate the failure reason "QUOTA\_EXCEEDED" (i.e. the quota exceeded) within the "cause" attribute of the "ProblemDetails" structure in the HTTP POST response. +- if the SCS/AS has exceeded its rate of submitting requests. If so the SCEF shall respond to the SCS/AS with a status code set to 429 Too Many Requests in the HTTP POST response. + +The SCEF shall send a Configuration Information Request to the HSS to query or configure the setting of Enhanced Coverage Restriction as defined in 3GPP TS 29.336 [11]. + +Upon receipt of the response from the HSS, the SCEF shall send an HTTP response to the SCS/AS with a 200 OK message for query or configure custom operation and include the Enhanced Coverage Restriction Data from HSS into the HTTP response. + +If the SCEF receives a response with an error code from the HSS, the SCEF shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +## 4.4.12 Procedures for Network Parameter Configuration + +### 4.4.12.1 General + +The procedures are used by an SCS/AS to request that the network consider setting the suggested network parameter values which can influence certain aspects of UE/network behaviour. The procedures are applicable for an individual UE or a group of UEs. + +In order to create a new network parameter configuration to configure suggested network parameters, the SCS/AS shall send an HTTP POST request message to the SCEF to the resource "NP Configurations". The body of the HTTP request message shall include External Identifier or MSISDN or External Group Identifier, SCS/AS Identifier, and may include Maximum Latency, Maximum Response Time and Suggested Number of Downlink Packets and Group Reporting Guard Time, wherein, the External Identifier or MSISDN indicates the configuration for an individual UE and the External Group Identifier indicates for a group of UEs. If the External Group Identifier is included, the SCS/AS shall provide the Notification Destination Address in the request. + +NOTE: The Notification Delivery as described in clause 5.2.5 is not supported for individual UE configuration case. + +In order to update an existing Network Parameter Configuration, the SCS/AS may send an HTTP PUT message to the resource "Individual NP Configuration" requesting the SCEF to replace all properties in the existing resource. + +The SCS/AS may also use an HTTP PATCH message to request to change some properties in the existing resource. + +Upon receipt of the HTTP POST, PUT or PATCH message, if the SCS/AS is authorized to perform the request, the SCEF shall check whether the Maximum Latency, Maximum Response Time and/or Suggested Number of Downlink Packets in the HTTP request body are within the range defined by operator policies, if one or more of these parameters are not within the range, the SCEF shall: + +- either reject the request message by sending an HTTP response to the SCS/AS with a status code set to "403 Forbidden", in which it may indicate the "PARAMETER\_OUT\_OF\_RANGE" application error in the "cause" attribute of the "ProblemDetails" data structure and it may also indicate which parameters are out of the range in the "invalidParams" attribute of the "ProblemDetails" structure in the response body; or +- modify the parameters which are not within the range by selecting different values which are in the range. + +After validation, the SCEF shall perform the Network Parameter Configuration as described in clause 4.4.12.2 for an individual UE or in clause 4.4.12.3 for a group of UEs. + +In order to delete an existing Network Parameter Configuration at the SCEF, the SCS/AS shall send an HTTP DELETE message to the corresponding resource "Individual NP Configuration" at the SCEF. The SCEF shall determine the SCEF Reference ID for deletion and interact with the HSS via S6t as defined in 3GPP TS 29.336 [11]. Upon receipt of the response from the HSS, the SCEF shall delete active resource "Individual NP Configuration" addressed by the URI and send an HTTP response to the SCS/AS with a "204 No Content" status code. + +### 4.4.12.2 Configuration Request for an individual UE + +If the configuration request from the SCS/AS is for an individual UE, the SCEF shall send the Configuration Information Request command to the HSS via S6t as defined in 3GPP TS 29.336 [11]. + +Upon receipt of the response from the HSS, the SCEF shall, + +- for the HTTP POST message, create a new resource "Individual NP Configuration" addressed by a URI that contains the SCS/AS identifier and an SCEF-created configuration identifier, and send an HTTP POST response to the SCS/AS with "201 Created" status code, the final suggested configuration parameter(s) (if modified), the indication(s) for the discarded parameter(s) (if discarded), and a location header field containing the URI for the created resource. +- for the HTTP PUT or PATCH message, update the active resource "Individual NP Configuration", and send an HTTP response to the SCS/AS with "200 OK" status code, the final suggested network parameter(s) (if modified), the indication(s) for the discarded parameter(s) (if discarded), or a "204 No Content" status code. + +If the SCEF receives a response with an error code from the HSS, the SCEF shall not create or update the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +#### 4.4.12.3 Configuration Request for a group of UEs + +If the configuration request from the SCS/AS is for a group of UEs, the SCS/AS shall provide the Notification Destination Address, the SCEF shall send the Configuration Information Request command to the HSS via S6t as defined in 3GPP TS 29.336 [11]. + +Upon receipt of the successful response indicating that group processing is in progress from the HSS before beginning the processing of individual UEs, the SCEF shall, + +- for the HTTP POST message, create a resource "Individual NP Configuration" addressed by a URI that contains the SCS/AS identity and an SCEF-created configuration identifier. The SCEF shall send an HTTP POST response to the SCS/AS including a location header field containing the URI for the created resource and a "201 Created" status code to acknowledge the SCS/AS of the successful group processing request. +- for the HTTP PUT or PATCH message, update the resource "Individual NP Configuration" addressed by the requested URL, and shall send "200 OK" status code or a "204 No Content" status code to acknowledge the SCS/AS of the successful group processing request in the HTTP response message. + +If the SCEF receives a response with an error code from the HSS, the SCEF shall not create or update the resource and shall respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +Upon receipt of the processing result of the individual UEs from the HSS, the SCEF shall send an HTTP POST request message with a reference to the related network parameter configuration and a list of processing result for the group members to the SCS/AS. + +The SCS/AS shall send an HTTP response to acknowledge the SCEF about the handling result of the received request. + +#### 4.4.12.4 Notification of applied parameter configuration + +If the Enhanced\_param\_config feature is supported and the SCEF receives currently applied parameter configuration from the HSS, the SCEF shall notify the SCS/AS by the HTTP POST message including the parameter changes in the "appliedParam" attribute. + +### 4.4.13 Procedures for setting up an AS session with required QoS + +This procedure is used to set up an AS session with required QoS for the service as defined in 3GPP TS 23.682 [2]. + +For initial AS session creation, the SCS/AS shall send an HTTP POST message to the SCEF for the "AS Session with Required QoS Subscriptions" resource. The body of HTTP POST message shall include SCS/AS Identifier, UE IP address, IP Flow description, QoS reference and notification destination address. And it may also include time period and/or traffic volume for sponsored data connectivity purpose. If the feature AppId is supported, either the Flow description or an external Application Identifier shall be included. + +After receiving the HTTP POST message, the SCEF shall authorize the request and may check if the total number of requested QoS reference has exceeded the limit for the SCS/AS. If the authorization is successful, the SCEF shall map the SCS/AS Identifier to AF Application Identifier if the external Application Identifier is not provided and only one AF Application Identifier is mapped, and if required, map the SCS/AS Identifier to ASP Identity and Sponsor Identity. + +NOTE 1: Before the QoS reference is mapped to Rx parameters, the SCEF can perform a mapping from the name space of the 3rd party SCS/AS to the name space of the operator. + +NOTE 2: The QoS reference referring to pre-defined QoS information in the SCEF can be mapped to media component descriptions (e.g. bandwidth, media type) according to SLA. + +If the authorization performed by the SCEF is successful, then the SCEF shall act as an AF to interact with the PCRF via the Rx interface as defined in 3GPP TS 29.214 [10] or 3GPP TS 29.201 [13] and trigger a PCRF initiated IP-CAN Session Modification. Based on local configuration, the SCEF may also request to be notified about the transmission resource status, i.e. INDICATION\_OF\_SUCCESSFUL\_RESOURCES\_ALLOCATION, INDICATION\_OF\_RELEASE\_OF\_BEARER, INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION, and optionally INDICATION\_OF\_LOSS\_OF\_BEARER and INDICATION\_OF\_RECOVERY\_OF\_BEARER. If the time + +period and/or traffic volume are received from the AF, the SCEF should subscribe to the PCRF on the USAGE\_REPORT event. + +If the "enNB" feature is supported, the SCEF may explicitly receive a list of user plane event(s) that the SCS/AS requests to subscribe to. The SCEF shall subscribe to the corresponding PCRF event(s) (e.g. INDICATION\_OF\_SUCCESSFUL\_RESOURCE\_ALLOCATION) for the received event(s) (e.g. SUCCESSFUL\_RESOURCES\_ALLOCATION), except for the SESSION\_TERMINATION event. + +NOTE 3: The PCRF does not need explicit subscription in order to notify Rx session termination. + +The SCEF, after receiving the AAA message or HTTP 201 Created message over the Rx interface from the PCRF with successful result code, shall create a resource "Individual AS Session with Required QoS Subscription" which represents AS session, addressed by a URI that contains the SCS/AS identity and an SCEF-created AS session identifier, and shall respond to the SCS/AS with a 201 Created message, including the result in the body of the HTTP response and a Location header field containing the URI for the created resource. The SCS/AS shall use the URI received in the Location header in subsequent requests to the SCEF to refer to this AS session. Otherwise, the SCEF shall send an HTTP response to the SCS/AS with a corresponding status code and include the result in the body of the HTTP response. If the SCEF receives a response with an error code from the PCRF, the SCEF shall not create the resource and respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +In order to update the established AS session, the SCS/AS may send an HTTP PUT message to the SCEF for the "Individual AS Session with Required QoS Subscription" resource requesting to replace all properties (e.g. new usage threshold, Flow Description or external Application Identifier) in the existing resource, addressed by the URI received in the response to the request that has created the resource. The UE IP or MAC address shall remain unchanged from previously provided values. After receiving such message, the SCEF shall make the change (e.g. if the usage threshold within the "usageThreshold" attribute is included in the HTTP PUT request and the accumulated usage report for the previously provided usage threshold is not received yet, the SCEF shall completely replace the previously provided one), and interact with the PCRF to modify the Rx session (as defined in 3GPP TS 29.214 [10] or 3GPP TS 29.201 [13]). After receiving the response with successful result code from the PCRF, the SCEF shall replace all properties of the existing resource, send an HTTP response to the SCS/AS with a "200 OK" status code, and include the result in the body of the HTTP response or a "204 No Content" status code. If the SCEF receives a response with an error code from the PCRF, the SCEF shall not update the resource and respond to the SCS/AS with a corresponding failure code as described in clause 5.2.6. + +The SCS/AS may also send an HTTP PATCH message to the SCEF for the "Individual AS Session with Required QoS Subscription" resource requesting to change some created properties (e.g. new usage threshold, Flow Description or external Application Identifier, updated list of user plane event(s) if the "enNB" feature is supported). After receiving the HTTP PATCH message, the SCEF shall make the change (e.g. if the usage threshold within the "usageThreshold" attribute is included in the HTTP PATCH request and the accumulated usage report for the previously provided usage threshold is not received yet, the SCEF shall completely replace the previously provided one), and interact with the PCRF to modify the Rx session (as defined in 3GPP TS 29.214 [10] or 3GPP TS 29.201 [13]). After receiving the response from the PCRF, the SCEF shall send an HTTP response to the SCS/AS with a "200 OK" status code and include the result in the body of the HTTP response, or a "204 No Content" status code. + +NOTE 4: The SCS/AS can assume a successful resource allocation upon receipt of the POST/PUT/PATCH response, until the FAILED\_RESOURCES\_ALLOCATION event is received. + +NOTE 5: The SCS/AS can update the list of user plane event(s) only for one time specific events, i.e. INDICATION\_OF\_SUCCESSFUL\_RESOURCES\_ALLOCATION, INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION and USAGE\_REPORT events, as specified in clause 5.3.13 of 3GPP TS 29.214 [10]. + +If the SCEF receives a traffic plane notification (e.g. the usage threshold is reached or transmission resource lost), or if the SCEF gets informed that the Rx session is terminated (e.g. due to a release of PDN connection), the SCEF shall send an HTTP POST message including the notified event (e.g. session terminated) and the accumulated usage (if received from the PCRF) to the callback URI "notificationUri" provided by the SCS/AS during the creation of individual AS Session with Required QoS Subscription. The SCS/AS shall respond with an HTTP response to confirm the received notification. + +In order to remove the established AS session, the SCS/AS shall send an HTTP DELETE message to the SCEF for the "Individual AS Session with Required QoS Subscription" resource. After receiving the HTTP DELETE message, the SCEF shall remove all properties and interact with the PCRF to terminate the Rx session (as defined in 3GPP TS 29.214 [10] or 3GPP TS 29.201 [13]). After receiving the response from the PCRF, the SCEF shall send an + +HTTP response to the SCS/AS with a corresponding status code and include the accumulated usage (if received from the PCRF). + +## 4.4.14 Procedures for MSISDN-less Mobile Originated SMS + +### 4.4.14.1 General + +The procedures are used by the SCEF to send the MSISDN-less MO-SMS to the SCS/AS via T8 interface. + +### 4.4.14.2 Delivery of MSISDN-less MO SMS + +If the SCEF receives an MSISDN-less MO-SMS via T4 including an destination SME address (long/short code of the SCS/AS), the SCEF will use the IMSI of the UE and application port ID received over T4 to query the HSS/HLR for an external ID, and the SCEF shall then determine the notification destination URL of an SCS/AS based on configured information on the mapping of SME addresses to destination URLs. The SCEF shall send to the determined destination URL an HTTP POST request that shall include an MsisdnLessMoSmsNotification data type with: + +- the short message transfer protocol data unit as received on the T4 interface. +- the Application Port as received on the T4 interface, and +- the external identifier of the UE that send the SMS, as received from the HSS/HLR. + +NOTE: The Notification Delivery using Websocket (see clause 5.2.5.4) and the Notification Test Event (see clause 5.2.5.3) are not supported for the present API. + +## 4.4.15 Procedures for RACS Parameter Provisioning + +The procedures are used by an SCS/AS to request that the network to provision manufacturer specific UE radio capability information. + +In order to create a new parameter provisioning, the SCS/AS shall send an HTTP POST request message to the SCEF to the resource "RACS Parameter Provisionings". The body of the HTTP POST request message shall include a list of RACS IDs, and for each provided RACS ID, its radio capability parameters and the related UE model(s) IMEI-TAC value(s). + +In order to fully replace an existing RACS Parameter Provisioning, the SCS/AS may send an HTTP PUT message to the resource "Individual RACS Parameter Provisioning" requesting the SCEF to change all properties in the existing resource. The body of the HTTP PUT request message shall include a list of RACS IDs, and for each provided RACS ID, its radio capability parameters and the related UE model(s) IMEI-TAC value(s). + +In order to partial update an existing RACS Parameter Provisioning, the SCS/AS may send an HTTP PATCH message to the resource "Individual RACS Parameter Provisioning" requesting the SCEF to change some properties in the existing resource. + +Upon receipt of the HTTP POST, PUT or PATCH message, if the SCS/AS is authorized to perform the request, the SCEF shall interact with the UCMF as described in 3GPP TS 29.675 [61]. After receiving the response from the UCMF, if at least one RACS ID is successfully provisioned, the SCEF shall create or update the resource "Individual RACS Parameter Provisioning" and respond with 201 Created or 200 OK to the SCS/AS respectively with the successfully provisioned RACS information or 204 No Content if the updates or replacement is successful with no content in the PATCH or PUT response message body, the SCEF may include RACS report(s) within attribute "racsReports" with a list of RACS ID(s) and the corresponding failure code for which the provisioning has failed as specified in table 5.16.2.2.3-1 in the body of the HTTP response. Otherwise, the SCEF shall send an HTTP response to the SCS/AS with a corresponding failure code as described in clause 5.16.5. If all the RACS IDs failed to be provisioned successfully, the SCEF may send a "500 Internal Server Error" HTTP response and may include in the response body failure reports as specified in clause 5.16.3. + +In order to delete an existing RACS Parameter Provisioning at the SCEF, the SCS/AS shall send an HTTP DELETE message to the corresponding resource "Individual RACS Parameter Provisioning" at the SCEF. Upon receipt of the DELETE request message, the SCEF shall interact with the UCMF as described in 3GPP TS 29.675 [61]. After receiving the response from the UCMF, the SCEF shall remove the resource and respond with 204 No Content to the SCS/AS. + +## 5 T8 APIs + +### 5.1 Introduction + +The T8 APIs are a set of APIs defining the related procedures and resources for the interaction between the SCEF and the SCS/AS. + +Tables 5.1-1 summarizes the APIs defined in this specification. + +**Table 5.1-1: API Descriptions** + +| Service Name | Clause defined | Description | OpenAPI Specification File | API Name | Annex | +|---------------------------|----------------|--------------------------------------------------------------|----------------------------------------|--------------------------------------|-------| +| MonitoringEvent | 5.3 | Event Monitoring API | TS29122_MonitoringEvent.yaml | 3gpp-monitoring-event | A.3 | +| ResourceManagementOfBdt | 5.4 | Resource Management of Background Data Transfer (BDT) API | TS29122_ResourceManagementOfBdt.yaml | 3gpp-bdt | A.4 | +| ChargeableParty | 5.5 | Chargeable Party API | TS29122_ChargeableParty.yaml | 3gpp-chargeable-party | A.5 | +| NIDD | 5.6 | Non-IP Data Delivery (NIDD) API | TS29122_NIDD.yaml | 3gpp-nidd | A.6 | +| DeviceTriggering | 5.7 | Device Triggering API | TS29122_DeviceTriggering.yaml | 3gpp-device-triggering | A.7 | +| GMDviaMBMSbyMB2 | 5.8.2 | Group Message Delivery via MBMS by MB2 API | TS29122_GMDviaMBMSbyMB2.yaml | 3gpp-group-message-delivery-mb2 | A.8.1 | +| GMDviaMBMSbyxMB | 5.8.3 | Group Message Delivery via MBMS by xMB | TS29122_GMDviaMBMSbyxMB.yaml | 3gpp-group-message-delivery-xmb | A.8.2 | +| ReportingNetworkStatus | 5.9 | Network Status Reporting API | TS29122_ReportingNetworkStatus.yaml | 3gpp-network-status-reporting | A.9 | +| CpProvisioning | 5.10 | Communication Patterns (CP) Parameters Provisioning API | TS29122_CpProvisioning.yaml | 3gpp-cp-parameter-provisioning | A.10 | +| PfdManagement | 5.11 | Packet Flow Description (PFD) Management API | TS29122_PfdManagement.yaml | 3gpp-pfd-management | A.11 | +| ECRControl | 5.12 | Enhanced Coverage Restriction Control API | TS29122_ECRControl.yaml | 3gpp-ecr-control | A.12 | +| NpConfiguration | 5.13 | Network Parameter Configuration API | TS29122_NpConfiguration.yaml | 3gpp-network-parameter-configuration | A.13 | +| AsSessionWithQoS | 5.14 | Application Server (AS) Session with QoS API | TS29122_AsSessionWithQoS.yaml | 3gpp-as-session-with-qos | A.14 | +| MsisdnLessMoSms | 5.15 | MSISDN-less Mobile-Originated SMS API | TS29122_MsisdnLessMoSms.yaml | 3gpp-msisdn-less-mo-sms | A.15 | +| RacsParameterProvisioning | 5.16 | RACS (Radio Capability Signaling) Parameter Provisioning API | TS29122_RacsParameterProvisioning.yaml | 3gpp-racs-parameter-provisioning | A.16 | + +## 5.2 Information applicable to several APIs + +### 5.2.1 Data Types + +#### 5.2.1.1 Introduction + +This clause defines structured data types, simple data types and enumerations that are applicable to several APIs defined in the present specification and can be referenced from data structures defined in the subsequent clauses. In addition, data types that are defined in OpenAPI Specification [27] can also be referenced from data structures defined in the subsequent clauses. + +NOTE: As a convention, data types in the present specification are written with an upper-case letter in the beginning. Parameters are written with a lower-case letter in the beginning. As an exception, data types that are also defined in OpenAPI Specification [27] can use a lower-case case letter in the beginning for consistency. + +Table 5.2.1.1-1 lists these common data types. + +**Table 5.2.1.1-1: Common Data Types applicable to several T8 APIs** + +| Data type | Section defined | Description | Applicability | +|------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| AccumulatedUsage | 5.2.1.2.7 | Represents an accumulated usage. | | +| Acknowledgement | 5.2.1.2.4 | Represents a successful acknowledgement of a notification. | | +| Bandwidth | 5.2.1.3.2 | Represents an integer indicating a bandwidth in bits per second. | | +| BdtReferenceId | 5.2.1.3.2 | Represents a BDT Reference ID. | | +| Binary | 5.2.1.3.2 | String with format "binary" as defined in the OpenAPI Specification. | | +| Bytes | 5.2.1.3.2 | String with format "byte" as defined in the OpenAPI Specification. | | +| ConfigResult | 5.2.1.2.15 | Represents one configuration processing result for a group's members. | | +| DateTime | 5.2.1.3.2 | String with format "date-time" as defined in OpenAPI Specification. | | +| DateTimeRm | 5.2.1.3.2 | Represents the same as the DateTime data type, but with the "nullable: true" property. | | +| DateTimeRo | 5.2.1.3.2 | Represents the same as the DateTime data type, but with the "readOnly=true" property. | | +| DayOfWeek | 5.2.1.3.2 | Integer between 1 and 7 denoting a weekday. 1 shall indicate Monday, and the subsequent weekdays shall be indicated with the next higher numbers. 7 shall indicate Sunday. | | +| DurationMin | 5.2.1.3.2 | Unsigned integer identifying a period of time in units of minutes. | | +| DurationSec | 5.2.1.3.2 | Unsigned integer identifying a period of time in units of seconds. | | +| DurationSecRm | 5.2.1.3.2 | Represents the same as the DurationSec data type, but with the "nullable: true" property. | | +| DurationSecRo | 5.2.1.3.2 | Represents the same as the DurationSec data type, but with the "readOnly=true" property. | | +| Event | 5.2.1.3.3 | Represents a bearer event. | | +| EventReport | 5.2.1.2.6 | Represents an event report. | | +| EthFlowInfo | 5.2.1.2.18 | Represents flow Ethernet flow information | | +| ExternalGroupId | 5.2.1.3.2 | Represents an external group identifier. | | +| ExternalId | 5.2.1.3.2 | Represents an external identifier. | | +| FlowInfo | 5.2.1.2.8 | Represents IP flow information. | | +| InvalidParam | 5.2.1.2.13 | Represents the description of invalid parameters, for a request rejected due to invalid parameters. | | +| Ipv4Addr | 5.2.1.3.2 | Represents an IPv4 address. | | +| Ipv4AddrRo | 5.2.1.3.2 | Represents the same as the Ipv4Addr data type, but with the "readOnly=true" property. | | +| Ipv6Addr | 5.2.1.3.2 | Represents an IPv6 address. | | +| Ipv6AddrRo | 5.2.1.3.2 | Represents the same as the Ipv6Addr data type, but with the "readOnly=true" property. | | +| Link | 5.2.1.3.2 | Represents a link towards a referenced resource. | | +| LinkRm | 5.2.1.3.2 | Represents the same as the Link data type, but with the "nullable: true" property. | | +| LocationArea | 5.2.1.2.11 | Represents a user location area. | | +| LocationArea5G | 5.2.1.2.17 | Represents a user location area when the UE is attached to 5G. | | +| Mcc | 5.2.1.3.2 | Represents a Mobile Country Code. | | +| Mnc | 5.2.1.3.2 | Represents a Mobile Network Code. | | +| Msisdn | 5.2.1.3.2 | Represents an MSISDN. | | +| NotificationData | 5.2.1.2.5 | Represents the information to be conveyed in a bearer level event(s) notification. | | +| PlmnId | 5.2.1.2.14 | Represents the identifier of a PLMN. | | +| Port | 5.2.1.3.2 | Unsigned integer with valid values between 0 and 65535 representing a port. | | +| PortRo | 5.2.1.3.2 | Represents the same as the Port data type, but with the "readOnly=true" property. | | +| ProblemDetails | 5.2.1.2.12 | Represents additional information and details on an error response. | | +| ResourceId | 5.2.1.3.2 | Represents an identifier of a resource within a resource URI. | | + +| | | | | +|--------------------|------------|---------------------------------------------------------------------------------------------------|--| +| ResultReason | 5.2.1.3.4 | Represents a failure result reason. | | +| ScsAsId | 5.2.1.3.2 | Represents an SCS/AS identifier. | | +| SponsorInformation | 5.2.1.2.1 | Represents a sponsor information. | | +| TestNotification | 5.2.1.2.9 | Represents a notification that can be sent to test whether a chosen notification mechanism works. | | +| TimeOfDay | 5.2.1.3.2 | Represents a time in a day. | | +| TimeWindow | 5.2.1.2.3 | Represents a time window identified by a start time and a stop time. | | +| Uri | 5.2.1.3.2 | Represents a URI. | | +| UsageThreshold | 5.2.1.2.2 | Represents a usage threshold. | | +| UsageThresholdRm | 5.2.1.2.16 | Represents the same as the UsageThreshold data type but with the "nullable: true" property. | | +| Volume | 5.2.1.3.2 | Unsigned integer identifying a volume in units of bytes. | | +| VolumeRm | 5.2.1.3.2 | Represents the same as the Volume data type, but with the "nullable: true" property. | | +| WebsockNotifConfig | 5.2.1.2.10 | Represents the configuration information for the delivery of notifications over Websockets. | | + +## 5.2.1.2 Referenced structured data types + +### 5.2.1.2.1 Type: SponsorInformation + +This type represents a sponsor information. It shall comply with the provisions defined in table 5.2.1.2.1-1. + +**Table 5.2.1.2.1-1: Definition of the SponsorInformation data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-----------|-------------|-----------------------------------------------| +| sponsorId | string | 1 | It indicates Sponsor ID. | +| aspId | string | 1 | It indicates Application Service Provider ID. | + +### 5.2.1.2.2 Type: UsageThreshold + +This type represents a usage threshold. It shall comply with the provisions defined in table 5.2.1.2.2-1. + +Only one of DownlinkVolume, UplinkVolume and TotalVolume shall be provided. If the server supports both duration and volume, then the first threshold that has been reached will apply. + +**Table 5.2.1.2.2-1: Definition of the UsageThreshold data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-------------|-------------|------------------------------------------------| +| duration | DurationSec | 0..1 | Indicates the length of time in seconds | +| totalVolume | Volume | 0..1 | Total data octets for both downlink and uplink | +| downlinkVolume | Volume | 0..1 | Downlink data octets | +| uplinkVolume | Volume | 0..1 | Uplink data octets | + +### 5.2.1.2.3 Type: TimeWindow + +This type represents a start time and a stop time of a time window. It shall comply with the provisions defined in table 5.2.1.2.3-1. + +**Table 5.2.1.2.3-1: Definition of the TimeWindow data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-----------|-------------|------------------------------------------------------| +| startTime | DateTime | 1 | Indicates the absolute start time of the time window | +| stopTime | DateTime | 1 | Indicates the absolute stop time of the time window | + +#### 5.2.1.2.4 Type: Acknowledgement + +This type represents a successful acknowledgement for a notification. + +**Table 5.2.1.2.4-1: Definition of the Acknowledgement data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-----------|-------------|--------------------------------------------------------------------------| +| details | string | 1 | A human-readable explanation specific to this successful acknowledgement | + +#### 5.2.1.2.5 Type: NotificationData + +This type represents the parameters which shall be notify the SCS/AS for bearer level event(s). + +**Table 5.2.1.2.5-1: Definition of the NotificationData data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|--------------------|-------------|-------------------------------------------------------------------------| +| transaction | Link | 1 | Link to the transaction resource to which this notification is related. | +| eventReports | array(EventReport) | 1..N | Contains the reported event and applicable information | + +#### 5.2.1.2.6 Type: EventReport + +This type represents an event report. It shall comply with the provisions defined in table 5.2.1.2.6-1. + +**Table 5.2.1.2.6-1: Definition of the EventReport data type** + +| Attribute name | Data type | Cardinality | Description | +|------------------|------------------|-------------|------------------------------------------------------------------| +| event | Event | 1 | Indicates the event reported by the SCEF. | +| accumulatedUsage | AccumulatedUsage | 0..1 | Contains the applicable information corresponding to the event. | +| flowIds | array(integer) | 0..N | Identifies the IP flows that were sent during event subscription | + +#### 5.2.1.2.7 Type: AccumulatedUsage + +This type represents an accumulated usage. It shall comply with the provisions defined in table 5.2.1.2.7-1. + +**Table 5.2.1.2.7-1: Definition of the AccumulatedUsage data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-------------|-------------|------------------------------------------------| +| duration | DurationSec | 0..1 | Indicates the length of time in seconds | +| totalVolume | Volume | 0..1 | Total data octets for both downlink and uplink | +| downlinkVolume | Volume | 0..1 | Downlink data octets | +| uplinkVolume | Volume | 0..1 | Uplink data octets | + +#### 5.2.1.2.8 Type: FlowInfo + +This type represents flow information. It shall comply with the provisions defined in table 5.2.1.2.8-1. + +**Table 5.2.1.2.8-1: Definition of the FlowInfo data type** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|------------------|-------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| flowId | integer | 1 | Indicates the IP flow. | | +| flowDescriptions | array(string) | 0..2 | Indicates the packet filters of the IP flow.
Refer to clause 5.3.8 of 3GPP TS 29.214 [10] for encoding. It shall contain UL and/or DL IP flow description. | | +| tosTC | TosTrafficClasses | 0..1 | Type of service or Traffic Class. | | + +NOTE: The "tosTC" attribute can be included when another packet filter attribute is needed to differentiate between packet flows. For example, packet flows encapsulated and encrypted by a tunnelling protocol can be differentiated by the ToS/TC value of the outer header if appropriately set by the application. To use ToS/TC for service data flow detection, network configuration by the operator (and additionally by the 3rd party Service Provider when the transport network is not fully within the operator control) needs to ensure there is no ToS/TC re-marking applied along the path from the application to the PSA UPF and the specific ToS/TC values are managed properly to avoid potential collision with other usage (e.g., paging policy differentiation). + +#### 5.2.1.2.9 Type: TestNotification + +This type represents a notification that can be sent to test whether a chosen notification mechanism works. It shall be supported if the feature "Notification\_test\_event", as defined for APIs that use notifications, is supported. + +**Table 5.2.1.2.9-1: Definition of the TestNotification data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-----------|-------------|-------------------------------------------------------------------------| +| subscription | Link | 1 | Link of the subscription resource to which the notification is related. | + +#### 5.2.1.2.10 Type: WebsockNotifConfig + +This type represents configuration for the delivery of notifications over Websockets. It shall be supported if the feature "Notification\_websocket", as defined for APIs that use notifications, is supported. + +**Table 5.2.1.2.10-1: Definition of the WebsockNotifConfig data type** + +| Attribute name | Data type | Cardinality | Description | +|---------------------|-----------|-------------|------------------------------------------------------------------------------------------------------------------| +| websocketUri | Link | 0..1 | Set by the SCEF to indicate to the SCS/AS the Websocket URI to be used for delivering notifications.
(NOTE 1) | +| requestWebsocketUri | boolean | 0..1 | Set by the SCS/AS to indicate that the Websocket delivery is requested.
(NOTE 2) | + +NOTE 1: A Websocket URI should use the scheme "wss" (Websocket Secure) for encrypted delivery and may use the scheme "ws" (Websocket) for unencrypted delivery. If the WebsockNotifConfig data type is used in an HTTP response, this attribute shall be present. If the WebsockNotifConfig data type is used in an HTTP request, this attribute shall not be set by the SCS/AS in a request to create a resource, and shall not be modified by the SCS/AS in a request to modify a resource. + +NOTE 2: In a request to create or update a resource, this attribute shall be set to true by the SCS/AS to request the SCEF to provide a Websocket URI for the delivery of notifications, and shall be absent otherwise. In any HTTP response, this attribute shall retain the value that was provided upon resource creation or update. + +#### 5.2.1.2.11 Type: LocationArea + +This data type represents the user location area which is sent from the SCS/AS to the SCEF. + +**Table 5.2.1.2.11-1: Definition of the LocationArea data Type** + +| Attribute name | Data type | Cardinality | Description | +|-----------------|-----------------------|-------------|--------------------------------------------------------------------------------------------------------| +| cellIds | array(string) | 0..N | Indicates a list of Cell Global Identities of the user which identifies the cell the UE is registered. | +| enodeBIds | array(string) | 0..N | Indicates a list of eNodeB identities in which the UE is currently located. | +| routingAreaIds | array(string) | 0..N | Identifies a list of Routing Area Identities of the user where the UE is located. | +| trackingAreaIds | array(string) | 0..N | Identifies a list of Tracking Area Identities of the user where the UE is located. | +| geographicAreas | array(GeographicArea) | 0..N | Identifies a list of geographic area of the user where the UE is located. | +| civicAddresses | array(CivicAddress) | 0..N | Identifies a list of civic addresses of the user where the UE is located. | + +#### 5.2.1.2.12 Type: ProblemDetails + +**Table 5.2.1.2.12-1: Definition of the ProblemDetails data type** + +| Attribute name | Data type | Cardinality | Description | +|-------------------|---------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| type | Uri | 0..1 | A URI reference according to IETF RFC 3986 [6] that identifies the problem type. | +| title | string | 0..1 | A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem. | +| status | integer | 0..1 | The HTTP status code for this occurrence of the problem. | +| detail | string | 0..1 | A human-readable explanation specific to this occurrence of the problem. | +| instance | Uri | 0..1 | A URI reference that identifies the specific occurrence of the problem. | +| cause | string | 0..1 | A machine-readable application error cause specific to this occurrence of the problem. This IE should be present and provide application-related error information, if available. | +| invalidParams | array(InvalidParam) | 0..N | Description of invalid parameters, for a request rejected due to invalid parameters. | +| supportedFeatures | SupportedFeatures | 0..1 | Features supported by the server (SCEF or SCS/AS).

When present, this IE shall indicate the features supported by the server; if the server supports no features, this IE shall be set to the character "0". | + +NOTE 1: See IETF RFC 9457 [8] for detailed information and guidance for each attribute. +NOTE 2: Additional attributes may be defined per API. + +#### 5.2.1.2.13 Type: InvalidParam + +**Table 5.2.1.2.13-1: Definition of the InvalidParam data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-----------|-------------|---------------------------------------------------------------| +| param | string | 1 | Attribute's name encoded as a JSON Pointer, or header's name. | +| reason | string | 0..1 | A human-readable reason, e.g. "must be a positive integer". | + +## 5.2.1.2.14 Type: PlmnId + +**Table 5.2.1.2.14-1: Definition of the PlmnId data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-----------|-------------|---------------------| +| mcc | Mcc | 1 | Mobile Country Code | +| mnc | Mnc | 1 | Mobile Network Code | + +## 5.2.1.2.15 Type: ConfigResult + +This type represents one configuration processing result for the group members. + +**Table 5.2.1.2.15-1: Definition of the ConfigResult data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-------------------|-------------|-----------------------------------------------------------------------------------------| +| externalIds | array(ExternalId) | 0..N | Each element indicates an external identifier of the UE.
(NOTE) | +| msisdns | array(Msisdn) | 0..N | Each element identifies the MS internal PSTN/ISDN number allocated for the UE
(NOTE) | +| resultReason | ResultReason | 1 | Identifies the configuration failure reason for the group members. | + +NOTE: Either "externalId" or "msisdn" shall be included for a group member. + +## 5.2.1.2.16 Type: UsageThresholdRm + +This type represents a usage threshold which is defined in clause 5.2.1.2.2 but defined with "nullable: true" property so it can be removed in "JSON Merge Patch", as defined in IETF RFC 7396 [39]. It shall comply with the provisions defined in table 5.2.1.2.16-1. + +Only one of "downlinkVolume", "uplinkVolume" and "totalVolume" shall be provided. Duration and volume are also removable in "JSON Merge Patch". If the server supports both duration and volume, then the first threshold that has been reached will apply. + +**Table 5.2.1.2.16-1: Definition of the UsageThresholdRm data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|---------------|-------------|------------------------------------------------| +| duration | DurationSecRm | 0..1 | Indicates the length of time in seconds | +| totalVolume | VolumeRm | 0..1 | Total data octets for both downlink and uplink | +| downlinkVolume | VolumeRm | 0..1 | Downlink data octets | +| uplinkVolume | VolumeRm | 0..1 | Uplink data octets | + +## 5.2.1.2.17 Type: LocationArea5G + +This data type represents the user location area which is sent from the AF to the NEF. + +**Table 5.2.1.2.17-1: Definition of the LocationArea5G data Type** + +| Attribute name | Data type | Cardinality | Description | +|-----------------|-----------------------|-------------|--------------------------------------------------------------------------------------| +| geographicAreas | array(GeographicArea) | 0..N | Identifies a list of geographic area of the user where the UE is located. | +| civicAddresses | array(CivicAddress) | 0..N | Identifies a list of civic addresses of the user where the UE is located. | +| nwAreaInfo | NetworkAreaInfo | 0..1 | This IE represents the network area information of the user where the UE is located. | + +### 5.2.1.2.18 Type: EthFlowInfo + +This type represents Ethernet flow information. It shall comply with the provisions defined in table 5.2.1.2.18-1. + +**Table 5.2.1.2.18-1: Definition of the EthFlowInfo data type** + +| Attribute name | Data type | Cardinality | Description | +|---------------------|---------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| flowId | integer | 1 | Indicates the Ethernet flow. | +| ethFlowDescriptions | array(EthFlowDescription) | 0..2 | Indicates the packet filters of the Ethernet flow.
Refer to clause 5.6.2.17 of 3GPP TS 29.514 [52] for encoding of each Ethernet flow. It shall contain UL and/or DL Ethernet flow description. | + +### 5.2.1.3 Referenced Simple data types and enumerations + +#### 5.2.1.3.1 Introduction + +This clause defines simple data types and enumerations that are referenced from data structures. + +#### 5.2.1.3.2 Simple data types + +The reused datatypes defined in OpenAPI Specification [27] listed in table 5.2.1.3.2-1 and the simple data types defined in table 5.2.1.3.2-2 apply to several T8 APIs. + +**Table 5.2.1.3.2-1: Reused OpenAPI data types** + +| Type name | Description | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| boolean | As defined in OpenAPI Specification [27], i.e. either value "true" or value "false" as defined in IETF RFC 7159 [5]. | +| integer | As defined in OpenAPI Specification [27]. | +| number | As defined in OpenAPI Specification [27]. | +| string | As defined in OpenAPI Specification [27]. | +| NOTE: | Data type names defined in OpenAPI Specification [27] do not follow the convention to start with capital letters otherwise used in this specification. | + +**Table 5.2.1.3.2-2: Simple data types applicable to several APIs** + +| Type name | Description | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bandwidth | Integer indicating a bandwidth in bits per second. | +| BdtReferenceId | String identifying a BDT Reference ID as defined in clause 5.3.3 of 3GPP TS 29.154 [9]. | +| Binary | String with format "binary" as defined in OpenAPI Specification [27]. | +| Bytes | String with format "byte" as defined in OpenAPI Specification [27], i.e, base64-encoded characters. | +| DayOfWeek | Integer between and including 1 and 7 denoting a weekday. "1" shall indicate "Monday", and the subsequent weekdays shall be indicated with the next higher numbers. "7" shall indicate "Sunday". | +| DateTime | String with format "date-time" as defined in OpenAPI Specification [27]. | +| DateTimeRm | String with format "date-time" as defined in OpenAPI [27] with "nullable: true" property. | +| DateTimeRo | String with format "date-time" as defined in OpenAPI [27] with "readOnly: true" property. | +| DurationSec | Unsigned integer identifying a period of time in units of seconds. | +| DurationSecRm | Unsigned integer identifying a period of time in units of seconds with "nullable: true" property. | +| DurationSecRo | Unsigned integer identifying a period of time in units of seconds with "readOnly: true" property. | +| DurationMin | Unsigned integer identifying a period of time in units of minutes. | +| ExternalId | String containing a local identifier followed by "@" and a domain identifier. Both the local identifier and the domain identifier shall be encoded as strings that do not contain any "@" characters. See clause 4.6.2 of 3GPP TS 23.682 [2] for more information. | +| ExternalGroupId | String containing a local identifier followed by "@" and a domain identifier. Both the local identifier and the domain identifier shall be encoded as strings that do not contain any "@" characters. See clauses 4.6.2 and 4.6.3 of 3GPP TS 23.682 [2] for more information. | +| Ipv4Addr | String identifying an Ipv4 address formatted in the "dotted decimal" notation as defined in IETF RFC 1166 [28]. | +| Ipv6Addr | String identifying an Ipv6 address formatted according to clause 4 in IETF RFC 5952 [29]. The mixed Ipv4 Ipv6 notation according to clause 5 of IETF RFC 5952 [29] shall not be used. | +| Ipv4AddrRo | String identifying an Ipv4 address formatted in the "dotted decimal" notation as defined in IETF RFC 1166 [28], with "readOnly: true" property. | +| Ipv6AddrRo | String identifying an Ipv6 address formatted according to clause 4 in IETF RFC 5952 [29], with "readOnly: true" property. The mixed Ipv4 Ipv6 notation according to clause 5 of IETF RFC 5952 [29] shall not be used. | +| Link | String formatted according to IETF RFC 3986 [7] identifying a referenced resource. | +| LinkRm | String formatted according to IETF RFC 3986 [7] identifying a referenced resource, but with the "nullable: true" property. | +| Mcc | String encoding a Mobile Country Code part of the PLMN, comprising 3 digits, as defined in 3GPP TS 38.413 [54]. | +| Mnc | String encoding a Mobile Network Code part of the PLMN, comprising 2 or 3 digits, as defined in 3GPP TS 38.413 [54]. | +| Msisdn | String formatted according to clause 3.3 of 3GPP TS 23.003 [14] that describes an MSISDN. | +| Port | Unsigned integer with valid values between 0 and 65535. | +| PortRo | Unsigned integer with valid values between 0 and 65535, with "readOnly: true" property. | +| ResourceId | String chosen by the SCEF to serve as an identifier in a resource URI. | +| ScsAsId | String that identifies an SCS/AS. | +| TimeOfDay | String with format "partial-time" or "full-time" as defined in clause 5.6 of IETF RFC 3339 [15]. Examples: "20:15:00", "20:15:00-08:00" (for 8 hours behind UTC). | +| Uri | String providing an URI formatted according to IETF RFC 3986 [7]. | +| Volume | Unsigned integer identifying a volume in units of bytes. | +| VolumeRm | Unsigned integer identifying a volume in units of bytes with "nullable: true" property. | + +### 5.2.1.3.3 Enumeration: Event + +The enumeration Event represents event reported by the SCEF. + +**Table 5.2.1.3.3-1: Enumeration Event** + +| Enumeration value | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| SESSION_TERMINATION | Indicates that Rx session is terminated. | +| LOSS_OF_BEARER | Indicates a loss of a bearer. (NOTE 2) | +| RECOVERY_OF_BEARER | Indicates a recovery of a bearer. (NOTE 2) | +| RELEASE_OF_BEARER | Indicates a release of a bearer. (NOTE 2) | +| USAGE_REPORT | Indicates the usage report event. | +| FAILED_RESOURCES_ALLOCATION | Indicates the resource allocation is failed. | +| SUCCESSFUL_RESOURCES_ALLOCATION | Indicates the resource allocation is successful. | +| NOTE 1: The "enNB" feature defined in clause 5.5.4 supports both subscription and notification for SUCCESSFUL_RESOURCES_ALLOCATION event, and explicit subscription for all the events.
NOTE 2: The "LOSS_OF_BEARER", RECOVERY_OF_BEARER, and RELEASE_OF_BEARER only apply to 4G. | | + +#### 5.2.1.3.4 Enumeration: ResultReason + +The enumeration ResultReason represents a failure result reason. + +**Table 5.2.1.3.4-1: Enumeration ResultReason** + +| Enumeration value | Description | +|---------------------|---------------------------------------------------------------------------------| +| ROAMING_NOT_ALLOWED | Identifies the configuration parameters are not allowed by roaming agreement. | +| OTHER_REASON | Identifies the configuration parameters are not configured due to other reason. | + +#### 5.2.1.4 Conventions for documenting structured data types + +The structured data types shall represent an object (see IETF RFC 8259 [40]). The structured data types shall contain attributes that are simple data types, structured data types, arrays (see below), maps (see below) or enumerations. + +An array (see IETF RFC 8259 [40]) shall represent a list of values without keys and with significance in the order of sequence. All values shall be of the same type. + +A map shall represent an object (see IETF RFC 8259 [40]) with a list of key-value pairs (with no significance in the order of sequence), where all keys are of type string and shall be unique identifiers assigned by the application rather than by the schema, and where all values shall be of the same type. + +NOTE 1: Maps are supported by the OpenAPI specification [27] as described at . Maps can enable a faster lookup of elements identified by some key in huge data structures compared to arrays that contain the key within the elements. Maps can also be used instead of arrays to modify individual elements when modification instructions of the PATCH method are compliant to IETF RFC 7396 [39]. + +Each structured data type shall be specified in a separate clause as illustrated in table 5.2.1.4-1. + +**Table 5.2.1.4-1: Definition of type ** + +| Attribute name | Data type | Cardinality | Description | +|------------------|-------------------------------------------------------|----------------------------|----------------------| +| | "" or
"array()"
or
"map()" | "0..1", "1",
or "M..N", | | + +**Attribute name:** Name of attributes that belong to the specified data type. + +**Data type:** Data type of the attribute. If the data type is indicated as "", the attribute shall be of data type . If the data type is indicated as "array()", the attribute shall be an array (see IETF RFC 8259 [40]) that contains elements of data type . If the data type is indicated as "map()", the attribute shall be an object (see IETF RFC 8259 [40]) encoding a map (see OpenAPI specification [27]) that contains as values elements of data + +type . can either be "integer", "number", "string" or "boolean" (as defined in the OpenAPI specification [27]), or a data type defined in a 3GPP specification. + +**Cardinality:** Defines the allowed number of occurrence of data type . A cardinality of "M..N", is only allowed for data types "array()" and "map()" and indicates the number of elements within the array or map; the values M and N can either be the characters "M" and "N", respectively, or integer numbers with M being greater than or equal 0, and N being greater than 1 and M, For data type "", the cardinality shall be set to "0..1" or "1". A lower boundary of "0" for the cardinality also indicates that the attribute is optional. A lower boundary of "0" for the cardinality indicates that the attribute is optional. + +NOTE 2: The "0..N" implies the array or map type of the attribute may be optional. If the attribute is present, the minimum number of elements is described in openAPI file. + +**Description:** Describes the meaning and use of the attribute and may contain normative statements. + +## 5.2.2 Usage of HTTP + +### 5.2.2.1 General + +For T8 APIs, support of HTTP/1.1 (IETF RFC 9112 [16], IETF RFC 9110 [17], IETF RFC 9111 [20]) over TLS is mandatory and support of HTTP/2 (IETF RFC 9113 [22]) over TLS is recommended. TLS shall be used as specified in clause 5.5 of 3GPP TS 33.187 [35]. An SCS/AS desiring to use HTTP/2 shall use the HTTP upgrade mechanism to negotiate applicable HTTP version as described in IETF RFC 9113 [22]. + +### 5.2.2.2 Usage of the HTTP PATCH method + +The HTTP PATCH method, as defined in IETF RFC 5789 [38], allows for a partial update of previously sent data, e.g. resources. For a complete replacement of previously sent data, the HTTP PUT method is used. It is defined separately for each resource whether the HTTP PUT and/or the HTTP PATCH are applicable. + +If the HTTP PATCH method is used: + +- if no modification of individual elements within an array needs to be supported, the JSON bodies within the PATCH request shall be encoded according to "JSON Merge Patch", as defined in IETF RFC 7396 [39]; or +- if a modification of individual elements within an array needs to be supported, the "JSON Patch" encoding of changes defined in IETF RFC 6902 [67] shall be used. + +## 5.2.3 Content type + +The bodies of HTTP request and successful HTTP responses shall be encoded in JSON format (see IETF RFC 8259 [5]). + +The MIME media type that shall be used within the related Content-Type header field is "application/json", as defined in IETF RFC 8259 [5]. + +JSON object used in the HTTP PATCH request shall be encoded according to: + +- "JSON Merge Patch" and shall be signalled by the content type "application/merge-patch+json", as defined in IETF RFC 7396 [39]; or +- "JSON Patch" and shall be signalled by the content type "application/json-patch+json", as defined in IETF RFC 6902 [67]. + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [8]. + +NOTE: This release only supports the content type JSON. + +## 5.2.4 URI structure + +### 5.2.4.1 Resource URI structure + +Resources are either individual resources, or structured resources that can contain child resources. It is recommended to design each resource following one of the archetypes provided in the Annex C of 3GPP TS 29.501 [49]. + +All API URIs of T8 APIs shall be: + +**{apiRoot}//** + +"apiRoot" is configured by means outside the scope of the present document. "apiName" and "apiVersion" shall be set dependent on the API, as defined in the corresponding clauses below. All resource URIs in the clauses below are defined relative to the above root API URI. + +NOTE 1: The "apiVersion" will only be increased if the new API version contains not backward compatible changes. Otherwise, the supported feature mechanism defined in clause 5.2.7 can instead be used to negotiate extensions. + +NOTE 2: A different root structure can be used when the Resource URI is preconfigured in the SCS/AS. + +The root structure may be followed by "apiSpecificSuffixes" that are dependent on the API and are defined separately for each API as resource URI where they apply: + +**{apiRoot}///** + +The naming conventions defined in clause 5.1.3 of 3GPP TS 29.501 [49] shall apply. + +### 5.2.4.2 Custom operations URI structure + +The URI of a custom operation which is associated with a resource shall have the following structure: + +**{apiRoot}////** + +Custom operations can also be associated with the service instead of a resource. The URI of a custom operation which is not associated with a resource shall have the following structure: + +**{apiRoot}///** + +In the above URI structures, "apiRoot", "apiName", "apiVersion" and "apiSpecificSuffixes" are as defined in clause 5.2.4.1 and "custOpName" represents the name of the custom operation as defined in clause 5.1.3.2 of 3GPP TS 29.501 [49]. + +### 5.2.4.3 Callback URI structure + +The purpose of the callback URI is to enable an HTTP client (the SCS/AS or SCEF) to provide the URI to be used by an HTTP server (the SCEF or SCS/AS) to send notifications or callback requests. + +The callback URI shall be in the form of an absolute URI as defined in clause 4.3 of IETF RFC 3986 [7], including an authority, and excluding any query component, any fragment component and any userinfo subcomponent. + +Therefore, a callback URI consists of the following components, specified with ABNF syntax (see IETF RFC 5234 [69]): + +URI = scheme ":" "/" host [ ":" port ] / path + +Where 'host' is either an FQDN or an IP address and the 'path' is a path to an HTTP client (the SCS/AS or SCEF) resource. + +## 5.2.5 Notifications + +### 5.2.5.1 General + +The SCEF and SCS/AS shall support the delivery of Notifications using a separate HTTP connection towards an address assigned by the SCS/AS, as described in clause 5.2.5.2. + +An SCEF and SCS/AS may support testing a notification connection as described in clause 5.2.5.3. An SCEF and SCS/AS may support the delivery of Notification using Websocket (IETF RFC 6455 [32]) as described in clause 5.2.5.4. + +### 5.2.5.2 Notification Delivery using a separate HTTP connection + +If a delivery of notifications is required for an API, the SCS/AS shall provide a notification destination URI, which designates to the SCEF where the SCEF shall send the HTTP Notifications. This URI is provided within an attribute (e.g. "notificationDestination", "notifUri", "notificationUri") defined in the data types that are passed in a request to create a resource that represents a subscription to notifications, unless it is specified for that API that a preconfigured destination address is used. + +The SCS/AS may provide the same notification destination URI for several subscriptions, and the SCEF should then use the same HTTP connection to deliver related notifications. + +The SCEF shall take the role of the HTTP client on the HTTP connection for the delivery of Notifications. Clause 5.2.2 shall also apply for this HTTP connection with the exception that an SCEF (rather than an SCS/AS) desiring to use HTTP/2 shall use the HTTP upgrade mechanism to negotiate applicable HTTP version. + +### 5.2.5.3 Notification Test Event + +If the optional "Notification\_test\_event" feature is supported, the SCS/AS may test whether notifications can be received by subscribing to the notification of a test event by providing a "requestTestNotification" attribute set to "true" in the HTTP request to create or update a subscription for notifications. In any other HTTP request or response, this attribute shall retain the value that was provided upon subscription resource creation. + +Upon receiving the "requestTestNotification" attribute as part of a subscription creation or update request, the SCEF shall send immediately after establishing the notification delivery mechanism a test notification containing a body formatted according to the "TestNotification" data type as defined in clause 5.2.1.2.12. If the SCS/AS does not receive the test notification within a configured time, the SCS/AS knows that the notification delivery with the selected method is not possible and may take corrective actions. + +### 5.2.5.4 Notification Delivery using Websocket + +The procedures in the present clause only apply if SCS/AS and SCEF support the "Notification\_websocket" feature. If the feature "Notification\_websocket" is supported, then the feature "Notification\_test\_event" shall also be supported. + +If a delivery of notifications is required for an API and the SCS/AS does not know from previous interactions with the SCEF whether delivery of notifications over a separate HTTP connection works, the SCS/AS should initially request the SCEF to try to establish a separate HTTP connection for notification delivery according to clause 5.2.5.2 by providing a URI to the SCEF designating where to send HTTP Notifications, and shall also subscribe to the notification of a test event as in clause 5.2.5.3. + +If the SCS/AS does not receive the requested notification of the test event during a configured period after the subscription, the SCS/AS may configure the subscription to request the SCEF to provide a URI for an HTTP connection to upgrade to Websocket, setting the "requestWebsocketUri" attribute to "true" as specified in clause 5.2.1.2.13. The SCS/AS may also request the SCEF to provide a URI in a new subscription creation request, and should in this case terminate the original subscription. + +NOTE 1: If the SCS/AS has requested the delivery of notifications to a separate entity, it needs to be informed by that separate entity about the receipt of the test notification. That communication between the separate entity and the SCS/AS is out of scope of the present document. + +When the SCEF receives a subscription creation or update request to use Websockets to deliver notifications (i.e. with the "requestWebsocketUri" attribute set to "true"), it shall assign a Websocket URI where to receive a Websocket connection establishment and provide this URI in the "websocketUri" attribute in the response, as defined in clause 5.1.2.1.13. Once such Websocket URI has been assigned for a particular subscription resource, subsequent update requests to this resource that ask for the assignment of a new Websocket URI for that subscription shall be rejected by the SCEF. + +Upon the reception of the Websocket URI from the SCEF in the "websocketUri" attribute, as specified in clause 5.2.1.2.13-1, in the subscription creation or subscription update response, the SCS/AS or a separate entity that is intended to receive the notification shall establish an HTTP connection towards that URI and shall upgrade that connection to the Websocket protocol (IETF RFC 6455 [32]) using the HTTP upgrade mechanism defined in IETF RFC 9110 [17]. + +NOTE 2: For delivery of Notifications to a separate entity, the SCS/AS needs to provide the Websocket URI to that separate entity. That communication between the SCS/AS and the separate entity is out of scope of the present document. + +The following framing of the request and response shall be used when delivering a notification or acknowledging its delivery through Websockets. + +NOTE 3: The framing is aligned as much as possible with HTTP delivery in order to simplify implementations. + +To deliver a notification towards the SCS/AS, the SCEF shall embed the following structure in a separate Websocket data frame with 0x2 (Binary) opcode in the following order: + +- 1) The string "3GPP-WS-Notif-Seq:", followed by a blank, followed by a four-byte sequence number, encoded as decimal number in ASCII, followed by CRLF +- 2) The following HTTP headers in any order, with the syntax and semantics as defined in IETF RFC 9110 [17]: Content-Type (mandatory), Content-Encoding (optional), Content-Length (mandatory). Every HTTP header line shall be ended by CRLF. +- 3) CRLF to end the headers section. +- 4) The content of the notification, as defined in the individual APIs. + +NOTE 4: The content is the same as the one that would be used if delivering the notification as defined in clause 5.2.5.3. + +To acknowledge the reception of a notification message towards the SCEF, the SCS/AS shall embed the following structure in a separate Websocket data frame with 0x2 (Binary) opcode in the following order: + +- 1) The string "3GPP-WS-Notif-Seq:", followed by a blank, followed by the four-byte sequence number of the notification to be confirmed, encoded as decimal number in ASCII, followed by CRLF. +- 2) The HTTP status code (e.g. 204) and status message (e.g. No Content) as defined for HTTP delivery of the notification in the individual APIs, separated by a single blank character, and ended by CRLF. +- 3) Conditionally, as defined in IETF RFC 9110 [17], the following HTTP headers in any order: Content-Type, Content-Encoding, and Content-Length. Every HTTP header line shall be ended by CRLF. +- 4) CRLF to end the headers section. +- 5) The content of the response, if applicable based on the status code and the HTTP headers, as defined in IETF RFC 9110 [17]. + +NOTE 5: The status code, the status message and the content (if applicable), are the same as if delivering the notification as defined in clause 5.2.5.3. + +Use of CRLF is defined in IETF RFC 9110 [17]. + +The SCEF need not wait for the confirmation of each notification before delivering the next notification. The SCEF shall determine whether a notification has been delivered successfully by correlating the sent notification with the received acknowledgement by checking the sequence numbers of both for equality. The SCEF may re-send a notification, using the same sequence number, if it has not received an acknowledgement with a matching sequence + +number after a configurable time-out. The SCS/AS shall consider notifications with the same sequence number that arrive within a configurable time interval as duplicates. + +The SCS/AS should send periodic Websocket "PING" frames to keep the connection alive. + +NOTE 6: the TCP layer will handle a possible fragmentation and reassembly of large messages. + +The security related clause 6 shall also apply for the HTTP connection that is upgraded to Websocket. + +## 5.2.6 Error handling + +Table 5.2.6-1 lists response bodies that are applicable to all APIs and as responses for all requests in the present specification unless otherwise specified. The HTTP client shall mandatorily support the processing of the status code for all the applicable methods, when received in a HTTP response message. In such cases the HTTP client shall also support the handling of the "ProblemDetails" JSON object with the Content-Type header field set to the value "application/problem+json", if the corresponding API definition in the current specification does not specify another response body for the corresponding status code. + +**Table 5.2.6-1: Response bodies supported for responses to all requests.** + +| Response body | Data type | Cardinality | Response Codes (NOTE 1) | Remarks (NOTE 2, NOTE 4) | Applied Methods | +|---------------|----------------|-------------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| | ProblemDetails | 1 | 400 Bad Request | Incorrect parameters were passed in the request. | GET, POST, PUT, PATCH, DELETE | +| | ProblemDetails | 1 | 401 Unauthorized | The client is not authorized as described in IETF RFC 9110 [17]. | GET, POST, PUT, PATCH, DELETE | +| | ProblemDetails | 1 | 403 Forbidden | This represents the case when the server is able to understand the request but unable to fulfil the request due to errors (e.g. the requested parameters are out of range). More information may be provided in the "invalidParams" attribute of the "ProblemDetails" structure. (NOTE 3) | GET, POST, PUT, PATCH, DELETE | +| | ProblemDetails | 1 | 404 Not Found | The resource URI was incorrect, for instance because of a wrong "scsAsId" field. | GET, POST, PUT, PATCH, DELETE | +| | ProblemDetails | 1 | 406 Not Acceptable | The content format provided in the "Accept" header is not acceptable by the server. | GET | +| | ProblemDetails | 1 | 411 Length Required | The code indicates that the server refuses to accept the request without a Content-Length header field. | POST, PUT, PATCH | +| | ProblemDetails | 1 | 413 Content Too Large | If the received HTTP request contains content larger than the server is able to process, the NF shall reject the HTTP request. | POST, PUT, PATCH | +| | ProblemDetails | 1 | 415 Unsupported Media Type | The code indicates that the resource is in a format which is not supported by the server for the method. | POST, PUT, PATCH | +| | ProblemDetails | 1 | 429 Too Many Requests | The code indicates that due to excessive traffic which, if continued over time, may lead to (or may increase) an overload situation. The HTTP header field "Retry-After" may be added in the response to indicate how long the client has to wait before making a new request. | GET, POST, PUT, PATCH, DELETE | +| | ProblemDetails | 1 | 500 Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. | GET, POST, PUT, PATCH, DELETE | +| | ProblemDetails | 1 | 503 Service Unavailable | The server is unable to handle the request. | GET, POST, PUT, PATCH, DELETE | + +NOTE 1: In addition to the above response codes, the SCEF can also send other valid HTTP response codes, if applicable. The list of all valid HTTP response codes can be found in HTTP Status Code Registry at IANA [6]. + +NOTE 2: The MIME media type that shall be used within the related Content-Type header field is "application/problem+json", as defined in IETF RFC 9457 [8]. + +NOTE 3: The information about which provided parameters are out of range shall be provided in the "invalidParams" attribute of the "ProblemDetails" structure for the API of network parameter configuration. + +NOTE 4: More information may be provided in the "detail" attribute of the "ProblemDetails" structure. + +The protocol and application errors in clause 5.2.7.2 of 3GPP TS 29.500 [44] are applicable for above status codes for the APIs defined in the present specification. Specific errors are contained in the related API definition for each API. + +## 5.2.7 Feature negotiation + +The procedures in clause 6.6.2 of 3GPP TS 29.500 [44] shall be applicable for the APIs defined in the present specification with the difference that the SCEF should not register any feature for northbound APIs in the NRF. + +The supported features are negotiated separately for each API. For each of the APIs defined in the present specification, the applicable list of features is contained in the related API definition. + +## 5.2.8 HTTP custom headers + +### 5.2.8.1 General + +This clause lists reused HTTP custom headers and defines any new HTTP custom headers introduced by this specification. + +### 5.2.8.2 Reused HTTP custom headers + +**Table 5.2.8.2-1: Reused HTTP custom headers** + +| Name | Reference | Description | +|------|-----------|-------------| +| | | | + +### 5.2.8.3 Optional HTTP custom headers + +#### 5.2.8.3.1 General + +The Northbound APIs defined in this specification may support the HTTP custom headers specified in Table 5.2.8.3.1-1 below. A description of each custom header and the normative requirements related to when to include them are also provided in Table 5.2.8.3.1-1. + +**Table 5.2.8.3.1-1: Optional HTTP custom headers** + +| Name | Reference | Description | +|-------------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Nb-Api-Sender-Timestamp | clause 5.2.8.3.2 | This header may be used to indicate the date and time (with a millisecond granularity) at which an HTTP request or response is originated. This may be used e.g. for measuring signalling delays in Northbound interfaces. | +| Nb-Api-Max-Rsp-Time | clause 5.2.8.3.3 | This header may be used in a HTTP request to indicate the duration during which the HTTP client waits for a response. | +| Nb-Api-Lci | clause 5.2.8.3.4 | This header may be used by a SCEF to send Load Control Information (LCI) to the sending entity (e.g. SCS/AS, AF). | +| Nb-Api-Oci | clause 5.2.8.3.5 |

This header may be used by an overloaded SCEF in an API response message, or in a notification request message to signal Overload Control Information (OCI) to the sending entity (e.g. SCS/AS, AF).

This header may also be used by an overloaded sending entity (e.g. SCS/AS, AF) in a notification response or in an API request to signal Overload Control Information (OCI) to the SCEF.

| + +### 5.2.8.3.2 Nbi-Api-Sender-Timestamp + +The provisions of clause 5.2.3.3.2 of 3GPP TS 29.500 [44] also apply to this header. + +NOTE: Any provisions that are specific to 5G SBI APIs (e.g. related to the support of Indirect Communication models) are however not applicable for Northbound APIs. + +### 5.2.8.3.3 Nb-Api-Max-Rsp-Time + +The provisions of clause 5.2.3.3.3 of 3GPP TS 29.500 [44] also apply to this header. + +NOTE: Any provisions that are specific to 5G SBI APIs (e.g. related to the support of Indirect Communication models) are however not applicable for Northbound APIs. + +### 5.2.8.3.4 Nbi-Api-Lci + +The header contains a comma-delimited list (see IETF RFC 9110 [17]) of Load Control Information (LCI). See clause 5.2.11. + +The encoding of the header follows the ABNF as defined in IETF RFC 9110 [17]. + +Nb-Api-Lci = "Nb-Api-Lci:" 1#(RWS timestamp ";" RWS lcMetric ")" + +timestamp = "Timestamp:" RWS DQUOTE date-time DQUOTE + +Mandatory parameter. The date-time type is specified in IETF RFC 5322 [66] and clause 7.1.1.1 of IETF RFC 9110 [17]. It indicates the timestamp associated with the load control information. + +lcMetric = "Load-Metric:" RWS (DIGIT / %x31-39 DIGIT / "100") "%" + +Mandatory parameter. Load-Metric is up to 3 digits long decimal string and the value range shall be from 0 to 100. + +EXAMPLE: Load Control Information: + +Nbi-Api-Lci: Timestamp: "Tue, 04 Feb 2021 08:50:28 GMT"; Load-Metric: 50% + +### 5.2.8.3.5 Nb-Api-Oci + +The header contains a comma-delimited list of Overload Control Information (OCI). See clause 5.2.11. + +The encoding of the header follows the ABNF as defined in IETF RFC 9110 [17]. + +Nb-Api-Oci = "Nb-Api-Oci:" 1#(RWS timestamp ";" RWS validityPeriod ";" RWS olcMetric ")" + +timestamp = "Timestamp:" RWS DQUOTE date-time DQUOTE + +Mandatory parameter. The date-time type is specified in IETF RFC 5322 [66] and clause 7.1.1.1 of IETF RFC 9110 [17]. It indicates the timestamp at which the overload control information was generated. + +validityPeriod = "Period-of-Validity:" RWS 1\*DIGIT "s" + +Mandatory parameter. Period of validity is a timer that is measured in seconds. Once the timer expires, the OCI becomes invalid. + +olcMetric = "Overload-Reduction-Metric:" RWS (DIGIT / %x31-39 DIGIT / "100") "%" + +Mandatory parameter. Overload-Reduction-Metric up to 3 digits long decimal string and the value range shall be from 0 to 100. + +EXAMPLE: Overload Control Information: + +Nbi-Api-Oci: Timestamp: "Tue, 04 Feb 2021 08:50:28 GMT"; Period-of-Validity: 90s; Overload-Reduction-Metric: 25% + +## 5.2.9 Conventions for Open API specification files + +### 5.2.9.1 General + +T8 Open API specification files shall comply with the OpenAPI specification [27] and with the present clause. + +Each API shall be described in one Open API specification file. In addition, 3GPP specifications may contain Open API specification file with common data types. + +For the purpose of referencing (see clause 5.2.9.6), it is assumed that each Open API specification file contained in a 3GPP specification is stored as separate physical, that all Open API specification files are stored in the same directory on the local server, and that the files are named according to the conventions in clause 5.2.9.6. + +### 5.2.9.2 Formatting of OpenAPI files + +The following guidelines shall be used when documenting OpenAPI files: + +- OpenAPI specifications shall be documented using YAML format (see YAML 1.2 [41]). For specific restrictions on the usage of YAML in OpenAPI, see OpenAPI Specification [27]. +- The style used for the specification shall be "PL" (Programming Language). +- The different scopes in the YAML data structures representing collections (objects, arrays...) shall use an indentation of two white spaces. +- Comments may be added by following the standard YAML syntax ("#"). +- Tabs shall not be used in OpenAPI specification files (e.g. within description fields). +- "Unbreakable" spaces (UTF-8 'NO-BREAK SPACE' (U+00A0)) shall not be used in OpenAPI specification files (e.g. within description fields). Only "normal" spaces (UTF-8 'SPACE' (U+0020)) shall be allowed. +- Trailing spaces (i.e. white spaces at the end of a line) should not be used in OpenAPI specification files. + +### 5.2.9.3 Structured data types + +The OpenAPI file shall contain a definition in the components/schemas section defining a schema with the name of the structured data type as key. + +The schema shall contain: + +- "type: object"; +- "description: ", where is the description of the data type in the table defining the structured data type. The "description" attribute should be provided for all data types, specially if they are frequently reused from the same or other OpenAPI specification files; the "description" attribute shall always be provided for data types defined as maps, with a clear indication of the values (strings) used as key of the map; +- if any attributes in the structured data type are marked as mandatory via a minimum cardinality greater than "0", a "required" keyword listing those attributes; and +- a "properties" keyword containing for each attribute in the structured data type an entry with the attribute name as key and: + 1. if the data type is "": + - a. if the data type of the attribute is "string", "number", "integer", or "boolean", a type definition using that data type as value ("type: "); or + - b. otherwise a reference to the data type schema for the data type of the attribute, i.e. "\$ref: '#/components/schemas/'" if that data type schema is contained in the same OpenAPI file and "\$ref: '#/components/schemas/'" if that data type schema is contained in file in the same directory on the same server; + 2. if the data type is "array()": + +- a. a type definition "type: array"; + - b. an "items:" definition containing: + - i). if the data type of the attribute is "string", "number", "integer", or "boolean", a type definition using that data type as value ("type: "); or + - ii). otherwise a reference to the data type schema for the data type of the attribute, i.e. "\$ref: '#/components/schemas/'" if that data type schema is contained in the same OpenAPI file and "\$ref: '/#/components/schemas/'" if that data type schema is contained in file in the same directory on the same server; + - c. if the cardinality contained an integer value as lower boundary, "minItems: "; and + - d. if the cardinality contained an integer value as upper boundary, "maxItems: "; +3. if the data type is "map()": + - a. a type definition "type: object"; + - b. an "additionalProperties:" definition containing: + - i). if the data type of the attribute is "string", "number", "integer", or "boolean", a type definition using that data type as value ("type: "); or + - ii). otherwise a reference to the data type schema for the data type of the attribute, i.e. "\$ref: '#/components/schemas/'" if that data type schema is contained in the same OpenAPI file and "\$ref: '/#/components/schemas/'" if that data type schema is contained in file in the same directory on the same server; + - c. if the cardinality contained an integer value as lower boundary, "min Properties: "; and + - d. if the cardinality contained an integer value as upper boundary, "max Properties: "; and + 4. "description: ", where is the description of the attribute in the table defining the structured data type; the "description" attribute shall always be provided for attributes defined as maps, with a clear indication of the values (strings) used as key of the map. + +NOTE 1: An omission of the "minProperties", and "maxProperties" keywords indicates that no lower or upper boundaries respectively, for the number of properties in an object are defined. An omission of the "minItems", and "maxItems" keywords indicates that no lower or upper boundaries, respectively, for the number of items in an array are defined. + +NOTE 2: The "0..N" implies the array or map type of the attribute may be optional. If the attribute is present, the minimum number of elements is described in openAPI file. + +Example: + +**Table 5.2.9.3-1: Definition of type ExampleStructuredType** + +| Attribute name | Data type | Cardinality | Description | +|-----------------|------------------|-------------|---------------------------------------------------------------------------| +| exSimple | ExSimple | 1 | exSimple attribute description | +| exArrayElements | array(string) | 1..10 | exArrayElements attribute description | +| exMapElements | map(ExStructure) | 1..N | exMapElements attribute description, indicating the values of the map key | + +The data structure in table 5.2.9.3-1 is described in an OpenAPI file as follows: + +``` +components: + schemas: + ExampleStructuredType: + type: object + description: ExampleStructuredType data type description + required: + - exSimple +``` + +``` + +- exMapElements +properties: + exSimple: + $ref: '#/components/schemas/ExSimple' + exArrayElements: + type: array + items: + type: string + minItems: 1 + maxItems: 10 + description: exArrayElements attribute description + exMapElements: + type: object + additionalProperties: + $ref: '#/components/schemas/ExStructure' + minProperties: 1 + description: exMapElements attribute description, indicating the values of the map key + +``` + +NOTE 3: Object schema definitions should not have property names in the "required" attribute for which a corresponding property definition does not exist. + +#### 5.2.9.4 Info + +The Open API specification file of an API shall contain an "info" field with the title and version as defined in clause 4.3 of 3GPP TS 29.501 [49]. + +#### 5.2.9.5 Servers + +As defined in clause 5.2.4, the base URI of an API consists of {apiRoot}//. It shall be encoded in the corresponding Open API specification file as "servers" field with {apiRoot} as variable. + +Example: + +``` + +servers: +- url: '{apiRoot}/3gpp-yyyy/v1' + variables: + apiRoot: + default: https://demohost.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. + +``` + +#### 5.2.9.6 References to other 3GPP-defined Open API specification files + +For the purpose of referencing, it shall be assumed that each Open API specification file contained in a 3GPP specification is stored as separate physical file, that all Open API specification files are stored in the same directory on the local server, and that the files are named according to the following convention: The file name shall consist of (in the order below): + +- the 3GPP specification number in the format "Tsxxxxyy"; +- an "\_" character; +- if the OpenAPI specification file contains an API definition, the API name as defined for corresponding base URL parts (see clause 4.4) of that API. +- if the OpenAPI specification file contains a definition of CommonData, the string "CommonData"; and +- the string ".yaml". + +Examples: + +Reference to Data Type "Xxx" defined in the same file + +``` +$ref: '#/components/schemas/Xxx' +``` + +Reference to Data Type "Xxx" defined as Common Data in 3GPP TS 29.122: + +``` +$ref: 'TS29122_CommonData.yaml#/components/schemas/Xxx' +``` + +Reference to Data Type "Xxx" defined within API "Nxxx\_Yyy" in 3GPP TS ab.cde: + +``` +$ref: 'Tsabcde_Nxxx_Yyy.yaml#/components/schemas/Xxx' +``` + +## 5.2.9.7 Server-initiated communication + +If an API contains notifications as described in clause 5.2.5, it should be described as "callback" in Open API specification files. + +Example: + +``` +paths: + /subscriptions: + post: + requestBody: + required: true + content: + application/json: + schema: + type: object + properties: + callbackUrl: # Callback URL + type: string + format: uri + responses: + '201': + description: Success + callbacks: + myNotification: # arbitrary name + '{$request.body#/callbackUrl}': # refers The callback URL in the POST + post: + requestBody: # Contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/NotificationBody' + responses: # Expected responses to the callback message + '200': + description: xxx +``` + +## 5.2.9.8 Describing the body of HTTP PATCH requests + +### 5.2.9.8.1 General + +As described in clause 5.2.2.2, the bodies of HTTP PATCH requests either use a "JSON Merge Patch" encoding as defined in IETF RFC 7396 [39], or a "JSON Patch" encoding as defined in IETF RFC 6902 [67]. + +It is possible to allow both encodings in an OpenAPI Specification [27] offering both schemas as alternative contents. + +### 5.2.9.8.2 JSON Merge Patch + +In the OpenAPI file, the content field key of the Request Body Object shall contain "application/merge-patch+json". The content field value is a Media Type Object identifying the applicable patch body Schema Object. The patch body Schema Object may contain structured data types derived from the data types used in the schema to describe a complete representation of the resource in such a manner that attributes that are allowed to be modified are listed in the "properties" validation keyword. + +NOTE 1: A derived structured data type is beneficial if the data types used to describe a complete representation of the resource contains mandatory attributes, if attributes are allowed to be removed by the PATCH operation, or if a checking by the OpenAPI tooling that only allowed modifications are done via the "additionalProperties: false" keyword is desired. It also provides a clear description in the OpenAPI file to developers which modifications need to be supported. + +As an alternative, the data types used in the schema to describe a complete representation of the resource may be used if any attributes that are allowed to be removed are marked as "nullable: true" in that schema. + +Any attributes that are allowed to be removed shall be marked as "nullable: true" in the patch body Schema Object. + +The "additionalProperties: false" keyword may be set. + +NOTE 2: The "additionalProperties: false" keyword enables the OpenAPI tooling to check that only allowed modifications are done. Extensions of the object in future releases are still possible under the assumption that the supported features mechanism is used to negotiate the usage of any new attribute prior to the PATCH invocation. If new optional attributes are expected to be introduced without corresponding supported feature or if PATCH can be used as first operation in an API, the usage of the "additionalProperties: false" keyword is not appropriate. + +### 5.2.9.8.3 JSON PATCH + +In the OpenAPI file, the content field key of the Request Body Object shall contain "application/json-patch+json". The content field value is a Media Type Object identifying the applicable patch body. It may contain a mutually exclusive list (using the "oneOf" keyword) of all allowed modifications as tuples, where "path" is a string containing a JSON Pointer value referring to a JSON object that is allowed to be modified, "op" is an enumeration of allowed JSON PATCH operations on the JSON object identified by "path" and "value" representing the schema/type of the value that will be updated or added at the JSON object identified by "path". In addition, an open alternative containing an object with no properties may be added using the "anyOf" keyword. + +NOTE 1: A mutually exclusive list provides a clear description in the OpenAPI specification file to developers which modifications need to be supported. This is of particular interest if only a limited number of modifications need to be supported. If no open alternative is included, the OpenAPI tooling will also check that only allowed modifications are done. + +NOTE 2: The open alternative allows for extensions of the PATCH in scenarios where new optional attributes are expected to be introduced without corresponding supported feature or if PATCH can be used as first operation in an API. + +### 5.2.9.9 Error Responses + +As described in clause 5.2.6, T8 APIs use valid HTTP response codes as error codes in HTTP responses and may include a "ProblemDetails" data structure specified in clause 5.2.1.2.12 or an application-specific data structure. + +Clause 5.2.6 specifies HTTP status code per HTTP method. OpenAPI files should include at least the status codes in that table. + +For the purpose of referencing, HTTP error responses with "ProblemDetails" data structure are specified as part of the CommonData OpenAPI file in Annex A.2. + +Example: + +In the example below, the 400, and 500 and default error response descriptions are referenced. + +``` +Paths: + /users: + get: + responses: + '200': + content: + application/json + schema: + $ref: '#/components/schemas/ExampleGetBody' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +``` + +The following definitions provided in Annex A.2 are used in that example: + +``` +components: + responses: + '400': + description: Bad request + content: + application/problem+json: + schema: +``` + +``` + + $ref: '#/components/schemas/ProblemDetails' + '500': + description: Internal Server Error + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + default: + description: Generic Error + +``` + +## 5.2.9.10 Enumerations + +For enumerations, the OpenAPI file shall contain a definition in the components/schemas section defining a schema with the name of the enumeration as key. + +The naming conventions defined in clause 5.1.4 of 3GPP TS 29.501 [49] shall apply. + +The schema: + +- shall contain the "anyOf" keyword listing as alternatives: + 1. the "type: string" keyword and the "enum" keyword with a list of all defined values for the enumeration; and + 2. the "type: string" keyword and the "description" keyword with a description stating that the string is only provided for extensibility and is not used to encode contents defined in the present version of the specification, and +- should contain a description field, containing the overall meaning and purpose of the enumeration; additionally, this field may contain a list of the defined values of the enumeration together with explanations of those values. + +NOTE: The "enum" keyword restricts the permissible values of the string to the enumerated ones. This can lead to extensibility problems when new values need to be introduced. + +Example: + +ExampleEnumeration represents xxx, and it is used to indicate yyy or zzz; it complies with the provisions defined in table 5.2.9.10-1. + +**Table 5.2.9.10-1: Enumeration ExampleEnumeration** + +| Enumeration value | Description | Applicability | +|-------------------|-----------------------|---------------| +| ONE | Value ONE description | | +| TWO | Value TWO description | | + +The data structure in table 5.2.9.10-1 is described in an OpenAPI file as follows: + +``` + +components: + schemas: + ExampleEnumeration: + anyOf: + - type: string + enum: + - ONE + - TWO + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration and is not used to encode + content defined in the present version of this API. + description: | + ExampleEnumeration represents xxx, and it is used to indicate yyy or zzz; + it complies with the provisions defined in table 5.2.9.10-1 of 3GPP TS ab.cde. + Possible values are: + - ONE: Value ONE description + - TWO: Value TWO description + +``` + +### 5.2.9.11 Read only attribute + +Each OpenAPI specification should include "readOnly: true" for those attributes that are only provided by the SCEF in the HTTP response message to prevent the SCS/AS from provisioning those attributes which is not expected, if the write and read operations (e.g. POST request and response) share the same data type which contains those attributes. + +Example: + +``` +NiddStatus: + anyOf: + - type: string + enum: + - ACTIVE + - TERMINATED_UE_NOT_AUTHORIZED + - TERMINATED + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + Description: > + Possible values are + - ACTIVE: The NIDD configuration is active. + - TERMINATED_UE_NOT_AUTHORIZED: The NIDD configuration was terminated because the UE's +authorisation was revoked. + - TERMINATED: The NIDD configuration was terminated. + readOnly: true +``` + +### 5.2.9.12 externalDocs + +Each OpenAPI specification shall provide in an "externalDoc" field the reference to the 3GPP TS describing the API, as illustrated below. + +Example: + +``` +externalDocs + description: 3GPP TS 29.122 V15.1.0 T8 reference point for Northbound APIs + url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.122/ +``` + +### 5.2.9.13 Operation identifiers + +Service operations defined in an OpenAPI specification file should be assigned an Operation ID. + +EXAMPLE: + +``` +get: + operationId: ReadInfo + summary: Read Information. + tags: + - Information (Document) + parameters: + - name: infoType + in: path + description: Requested information Type + required: true + schema: + type: string + (...) +``` + +### 5.2.9.14 Usage of the "tags" field + +In an OpenAPI specification, all HTTP operations belonging to the same resource should include a "tags" field containing a same value, briefly describing that resource (e.g. using the name of the resource and its archetype). This results in all operations being grouped by the User Interface of OpenAPI tools, which helps with readability of the API documentation. + +EXAMPLE: + +``` +openapi: 3.0.0 +(...) +paths: + /subscriptions/{subscriptionId}: +``` + +``` +get: + summary: Retrieve an existing Individual subscription resource. + operationId: GetIndSubsc + tags: + - Individual Subscription (Document) + + (...) + +put: + summary: Request the update of an existing Individual Subscription resource. + operationId: UpdateIndSubsc + tags: + - Individual Subscription (Document) + + (...) + +patch: + summary: Request the modification of an existing Individual Subscription resource. + operationId: ModifyIndSubsc + tags: + - Individual Subscription (Document) + + (...) +``` + +## 5.2.10 Redirection handling + +An HTTP request may be redirected to a different target entity. + +Upon receipt of an HTTP request from the SCS/AS, when the SCEF redirects the HTTP request to a different target SCEF, the URI of the target SCEF towards which the request is redirected shall be given by the Location header field of the "307 Temporary Redirect" or "308 Permanent Redirect" response. The SCS/AS should then send the HTTP request towards the new target SCEF. + +Upon receipt of a notification/callback request from the SCEF, when the SCS/AS redirects the notification/callback request to a different target SCS/AS, the URI of the target SCS/AS towards which the notification/callback request is redirected shall be given by the Location header field of the "307 Temporary Redirect" or "308 Permanent Redirect" response. The SCEF should then send the HTTP request towards the new target SCS/AS. + +## 5.2.11 Support of Load and Overload Control + +The Load Control mechanisms defined in clause 6.3 of 3GPP TS 29.500 [44] may be supported by T8 APIs with the following differences: + +- The "Load Control based on load signalled via the NRF" mechanism defined in clause 6.3.2 of 3GPP TS 29.500 [44] shall not be supported; and +- The "Load Control based on LCI Header" mechanism defined in clause 6.3.3 of 3GPP TS 29.500 [44] may be supported with the following differences: + - The Load Control "scope" and all the related provisions are not applicable; + - The "NF Service Consumer" corresponds to the sending entity (e.g. SCEF, SCS/AS, AF) of the message in T8 APIs and the "NF Service Producer" corresponds to the receiving entity (e.g. SCEF, SCS/AS, AF) of the message in T8 APIs; + - The provisions related to the SCP (Service Communication Proxy) and SEPP (Security Edge Protection Proxy) entities are not applicable; and + - The "3gpp-Sbi-Lci" custom HTTP header corresponds to the "Nbi-API-Lci" custom HTTP header defined in clause 5.2.8.3.4 for T8 APIs. + - The provisions and mechanisms using the NRF (i.e. 5GC NF Repository Function) are not applicable. + +The Overload Control mechanisms defined in clause 6.4 of 3GPP TS 29.500 [44] may be supported by T8 APIs with the following differences: + +- The "Overload Control based on HTTP status codes" mechanism defined in clause 6.4.2 of 3GPP TS 29.500 [44] may be supported with the following differences: + - The "NF Service Consumer" corresponds to the sending entity (e.g. SCEF, SCS/AS, AF) of the message in T8 APIs and the "NF Service Producer" corresponds to the receiving entity (e.g. SCEF, SCS/AS, AF) of the message in T8 APIs; + +and + +- The "Overload Control based on OCI Header" mechanism defined in clause 6.4.3 of 3GPP TS 29.500 [44] may be supported with the following differences: + - The Overload Control "scope" and all the related provisions are not applicable; + - The "NF Service Consumer" corresponds to the sending entity (e.g. SCEF, SCS/AS, AF) of the message in T8 APIs and the "NF Service Producer" corresponds to the receiving entity (e.g. SCEF, SCS/AS, AF) of the message in T8 APIs; + - The provisions related to the SCP (Service Communication Proxy) and SEPP (Security Edge Protection Proxy) entities are not applicable; and + - The "3gpp-Sbi-Oci" custom HTTP header corresponds to the "Nbi-Api-Oci" custom HTTP header defined in clause 5.2.8.3.5 for T8 APIs. + - The provisions and mechanisms using the NRF (i.e. 5GC NF Repository Function) are not applicable. + +## 5.2.12 Query parameters + +The query component in a URI contains non-hierarchical data that, along with data in the path component, enables to filter the resources identified within the scope of the URI's scheme to a subset of the resources matching the query parameters. The query component is indicated by the first question mark ("?") character and terminated by a number sign ("#") character or by the end of the URI. The syntax of the query component is specified in IETF RFC 3986 [7]. + +When a server receives a request with a query component, it shall parse the query string in order to identify the filters. The first question mark is used to be a separator and is not part of the query string. A query string is composed of a series of "key=value" pairs, separated by "&". If one query parameter contains more than one value, i.e. an array of data elements, then the values shall be separated by comma (","). + +The behaviour of the server when receiving an HTTP/2 method with a query parameter which is of type array, and only some of the members in the array can be matched, depends on each API and the behaviour shall be clearly described. + +When multiple query parameters are defined for a method on the resource, the logical 'AND' is the default logical relationship between the query parameters for this resource. If a different logical relationship between multiple query parameters is specified for a method on a resource in an API, then this logical relationship override the default logical relationship for this specific method on the concerned resource in that API. If multiple query parameters are defined for a method on a resource in an API, but there is no need to specify any logical relationship between these query parameters, the concerned API shall explicitly state how to handle multiple query parameters. + +## 5.2.13 Vendor-specific extensions + +### 5.2.13.1 General + +The vendor specific extensions specified in the below clauses are mechanisms for the APIs to re-use. The applicability of these mechanisms for specific 3GPP Northbound and application layer APIs is specified in the respective API specifications. + +### 5.2.13.2 Vendor-specific extensions to the data model + +Vendor-specific extensions for information elements may be generally supported in the 3GPP northbound and application layer APIs by reusing the same vendor-specific extensions mechanism defined for 5GC APIs in clause 6.6.3 of 3GPP TS 29.500 [44]. + +In the 3GPP northbound and application layer APIs, the vendor may alternatively be identified by setting the placeholder "nnnnn" in the vendor-specific member name to a domain name registered to the vendor, or a URN from the URN space managed by the vendor. + +NOTE: The global uniqueness of the domain name or URN, when used to set the placeholder "nnnnn" in the vendor-specific member name, has to be guaranteed. + +An example for the IANA-assigned enterprise code to identify the vendor is: + +EXAMPLE 1: The vendor-specific member name for vendor "3GPP" based on IANA enterprise number would be: + +``` +"vendorSpecific-010415": { + ... +} +``` + +Examples for the additional alternatives to identify the vendor are: + +EXAMPLE 2: The vendor-specific member name for vendor "3GPP" based on domain name would be: + +``` +"vendorSpecific-3gpp.org": { + ... +} +``` + +EXAMPLE 3: The vendor-specific member name for vendor "3GPP" based on URN would be: + +``` +"vendorSpecific-urn:3gpp:example": { + ... +} +``` + +NOTE: The preferred naming scheme (for the "nnnnn" placeholder) for vendor-specific member names is the one based on the IANA-assigned enterprise code defined in clause 6.6.3 of 3GPP TS 29.500 [44]. + +### 5.2.13.3 Vendor-specific query parameters + +Vendor-specific extensions to the query component of an HTTP request may be supported in the 3GPP northbound and application layer APIs by allowing the provisioning of vendor-specific query parameters in order to support additional vendor-specific filtering criteria. Whether an operation (e.g. using the HTTP GET method) on a specific resource of a 3GPP northbound or application layer API shall support the processing of vendor-specific query parameters shall be explicitly specified (within the corresponding resource or custom operation definition clauses) in the definition of this API operation in the technical specification where it is defined. This pattern applies to querying resources of "collection" or "store" archetype. + +A vendor-specific query parameter shall be encoded as follows: + +- The query parameter name shall start with "vend-spec" followed by the actual name of the query parameter, i.e. "vend-spec-". +- The query parameter value shall be encoded as a JSON object containing two attributes as defined in Table 5.2.13.2-1, wherein: + - the "target" attribute is a JSON pointer (as per RFC 6901 [70]) towards the targeted attribute in the targeted resource representation; and + - the "value" attribute contains the actual value of the query parameter that is to be used for filtering and shall hence be encoded in the same way as the attribute in the resource representation that it targets. + +**Table 5.2.13.2-1: Vendor-specific query parameter value content definition** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-------------------------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| target | String | M | 1 | Contains the JSON pointer (as per RFC 6901 [70]) to the attribute in the resource representation that the provided vendor-specific query parameter is targeting. | | +| value | | M | 1 | Contains the vendor-specific query parameter value. | | + +EXAMPLE 1: Assuming that vendor-specific query parameters are supported for the MonitoringEvent API, if an authorized service consumer wants to retrieve the representations of the "Individual Monitoring Event Subscription" resources that contain a specific value (e.g. 6) for the "maximumNumberOfReports" attribute, then it can send a GET request using the following vendor-specific query parameter: + +GET {apiRoot}/3gpp-monitoring-event/v1/{scsAsId}/subscriptions?vend-spec-max-reports={"target": "/maximumNumberOfReports", value: "6"} + +EXAMPLE 2: Assuming that vendor-specific query parameters are supported for the MonitoringEvent API, if within the representations of the "Individual Monitoring Event Subscription" resources, a vendor-specific extension to the data model is provided by an AF via the "vendorSpecific-010415" attribute as specified in clause 5.2.13.1 and contains additional/alternative target location accuracy values within the "addAccuracy" attribute, and an authorized service consumer wants to retrieve the representations of those "Individual Monitoring Event Subscription" resources that contain a specific value for the "addAccuracy" attribute, then it can send a GET request using the following vendor-specific query parameter: + +GET {apiRoot}/3gpp-monitoring-event/v1/{scsAsId}/subscriptions?vend-spec-accuracy={"target": "/vendorSpecific-010415/addAccuracy", value: "CELL\_OR\_TA"} + +## 5.3 MonitoringEvent API + +### 5.3.1 Overview + +The MonitoringEvent API is a RESTful API that allows the SCS/AS to subscribe to notifications about specific events in 3GPP networks. It also allows the SCEF to report the event by sending notifications to the authorised users when the corresponding event is detected. The API also allows the SCEF to indicate the removal of a previously configured monitoring request. The MonitoringEvent API defines a set of data models, resources and the related procedures for the creation and management of monitoring event subscriptions. The corresponding JSON schema for the representation of the resources and operations defined by the MonitoringEvent API is provided in its complete form in Annex A.3. + +### 5.3.2 Data model + +#### 5.3.2.1 Resource data types + +##### 5.3.2.1.1 Introduction + +This clause defines data structures to be used in resource representations, including subscription resources. + +Table 5.3.2.1.1-1 specifies data types re-used by the MonitoringEvent API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the MonitoringEvent API. + +**Table 5.3.2.1.1-1: MonitoringEvent API re-used Data Types** + +| Data type | Reference | Comments | +|-----------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CivicAddress | 3GPP TS 29.572 [42] | Civic address. | +| CodeWord | 3GPP TS 29.515 [65] | Code word. | +| DIDataDeliveryStatus | 3GPP TS 29.571 [45] | Traffic Descriptor of source of downlink data notifications. | +| DddTrafficDescriptor | 3GPP TS 29.571 [45] | Traffic Descriptor of source of downlink data. | +| Dnn | 3GPP TS 29.571 [45] | Identifies a DNN. | +| Fqdn | 3GPP TS 29.571 [45] | Identifies a FQDN. | +| GeographicArea | 3GPP TS 29.572 [42] | Identifies the geographical information of the user(s). | +| Gpsi | 3GPP TS 29.571 [45] | Represents a GPSI. | +| IpAddr | 3GPP TS 29.571 [45] | UE IP Address. | +| LocationQoS | 3GPP TS 29.572 [42] | Requested location QoS. | +| LdrType | 3GPP TS 29.572 [42] | Location deferred requested event type. | +| MinorLocationQoS | 3GPP TS 29.572 [42] | Minor Location QoS. | +| VelocityRequested | 3GPP TS 29.572 [42] | Velocity of the target UE requested. | +| AgeOfLocationEstimate | 3GPP TS 29.572 [42] | Age of the location estimate for change of location type or motion type of Location deferred report. | +| AccuracyFulfilmentIndicator | 3GPP TS 29.572 [42] | The indication whether the obtained location estimate satisfies the requested QoS or not. | +| VelocityEstimate | 3GPP TS 29.572 [42] | UE velocity, if requested and available. | +| LinearDistance | 3GPP TS 29.572 [42] | This IE shall be present and set to true if a location estimate is required for motion event report. | +| NetworkAreaInfo | 3GPP TS 29.554 [50] | Identifies a network area information. | +| PatchItem | 3GPP TS 29.571 [45] | Contains the list of changes to be made to a resource according to the JSON PATCH format specified in IETF RFC 6902 [67]. | +| PduSessionInformation | 3GPP TS 29.523 [70] | Represents PDU session identification information. | +| PositioningMethod | 3GPP TS 29.572 [42] | Identifies the positioning method used to obtain the location estimate of the UE. | +| SACEventStatus | 3GPP TS 29.571 [45] | Contains the network slice status information related to network slice admission control. | +| SACInfo | 3GPP TS 29.571 [45] | Represents network slice admission control information to control the triggering of notifications or convey network slice status information. | +| Snssai | 3GPP TS 29.571 [45] | Contains a S-NSSAI. | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.3.4-1. | +| ServiceIdentity | 3GPP TS 29.515 [65] | Service identity. | +| SupportedGADShapes | 3GPP TS 29.572 [42] | Supported Geographical Area Description shapes. | +| MacAddr48 | 3GPP TS 29.571 [45] | MAC Address. | +| UcPurpose | 3GPP TS 29.503 [63] | Represents the purpose of a user consent. | +| Uinteger | 3GPP TS 29.571 [45] | Represents an unsigned Integer. | +| Uri | 5.2.1.3.2 | Represents a URI. | +| UserLocation | 3GPP TS 29.571 [6] | Represents a user location. | +| RangingSIResult | 3GPP TS 29.572 [42] | Indicates result type for ranging and sidelink positioning | +| RelatedUE | 3GPP TS 29.572 [42] | Indicates information for related UE for ranging and sidelink positioning | + +Table 5.3.2.1.1-2 specifies the data types defined for the MonitoringEvent API. + +**Table 5.3.2.1.1-2: MonitoringEvent API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|-------------------------------|----------------|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| Accuracy | 5.3.2.4.7 | Represents a desired granularity of accuracy for the requested location information. | Location_notification, eLCS, EDGEAPP | +| ApiCapabilityInfo | 5.3.2.3.9 | Represents the availability information of supported API. | API_support_capability_notification | +| AppliedParameterConfiguration | 5.3.2.3.8 | Represents the parameter configuration applied in the network. | Enhanced_param_config | +| AssociationType | 5.3.2.4.6 | Represents an IMEI or IMEISV to IMSI association. | Change_of_IMSI_IMEI_association_notification | +| ConsentRevocNotif | 5.3.2.3.12 | Represents the user consent revocation information conveyed in a user consent revocation notification. | UserConsentRevocation | +| ConsentRevoked | 5.3.2.3.13 | Represents the information related to revoked user consent(s). | UserConsentRevocation | +| FailureCause | 5.3.2.3.6 | Represents the reason of communication failure. | Communication_failure_notification | +| GroupMembListChanges | 5.3.2.3.13 | Represents information on the change(s) to a group's members list. | GMEC | +| IdleStatusInfo | 5.3.2.3.3 | Represents the information relevant to when the UE transitions into idle mode. | Ue-reachability_notification, Availability_after_DDN_failure_notification | +| InterfaceIndication | 5.3.2.4.10 | Represents the network entity used for data delivery towards the SCS/AS. | Pdn_connectivity_status | +| LocationFailureCause | 5.3.2.4.11 | Represents the cause of location/positioning failure. | eLCS | +| LocationInfo | 5.3.2.3.5 | Represents the user location information. | Location_notification, eLCS | +| LocationType | 5.3.2.4.5 | Represents a location type. | Location_notification, Number_of_UEs_in_an_area_notification, Number_of_UEs_in_an_area_notification_5G, eLCS | +| MonitoringEventReport | 5.3.2.3.2 | Represents an event monitoring report. | | +| MonitoringEventReports | 5.3.2.3.10 | Represents one or multiple event monitoring report(s). | enNB | +| MonitoringEventSubscription | 5.3.2.1.2 | Represents a subscription to event(s) monitoring. | | +| MonitoringNotification | 5.3.2.2.2 | Represents an event monitoring notification. | | +| MonitoringType | 5.3.2.4.3 | Represents a monitoring event type. | | +| PdnConnectionInformation | 5.3.2.3.7 | Represents the PDN connection information of the UE. | Pdn_connectivity_status | +| PdnConnectionStatus | 5.3.2.4.8 | Represents the PDN connection status. | Pdn_connectivity_status | +| PdnType | 5.3.2.4.9 | Represents a PDN connection type. | | +| ReachabilityType | 5.3.2.4.4 | Represents a reachability type. | Ue-reachability_notification | +| SACRepFormat | 5.3.2.4.13 | Represents the NSAC reporting format. | NSAC | +| SubType | 5.3.2.4.12 | Represents a subscription type. | UAV | +| UavPolicy | 5.3.2.3.11 | Represents the policy information included in the UAV presence monitoring request. | UAV | +| UePerLocationReport | 5.3.2.3.4 | Represents the number of UEs found at the indicated location. | Number_of_UEs_in_an_area_notification, Number_of_UEs_in_an_area_ | + +| | | | | +|------------------------|------------|------------------------------------------------------------------------------------|-----------------| +| | | | notification_5G | +| UpCumEvtRep | 5.3.2.3.18 | Represents the cumulative event report for events reported via user plane. | eLCS_en | +| UpLocRepAddrAfRm | 5.3.2.3.17 | Represents the user plane addressing information. | eLCS_en | +| RangeDirection | 5.3.2.3.14 | Represents the range and direction between two points. | Ranging_SL | +| TwodrelativeLocation | 5.3.2.3.15 | Represents 2D local co-ordinates with origin corresponding to another known point. | Ranging_SL | +| ThreedrelativeLocation | 5.3.2.3.16 | Represents 3D local co-ordinates with origin corresponding to another known point. | Ranging_SL | + +#### 5.3.2.1.2 Type: MonitoringEventSubscription + +This type represents a subscription to monitoring an event. The same structure is used in the subscription request and subscription response. + +**Table 5.3.2.1.2-1: Definition of type MonitoringEventSubscription** + +| Attribute name | Data type | Cardinality | Description | Applicability
(NOTE 3) | +|-------------------------|------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| self | Link | 0..1 | Link to the resource "Individual Monitoring Event Subscription". This parameter shall be supplied by the SCEF in HTTP responses. | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7.
This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| mtcProviderId | string | 0..1 | Identifies the MTC Service Provider and/or MTC Application. (NOTE 7) | | +| appId | array(string) | 0..N | Identifies the Application Identifier(s). (NOTE 16) | AppDetection_5G | +| externalId | ExternalId | 0..1 | Identifies a user as defined in Clause 4.6.2 of 3GPP TS 23.682 [2].
This attribute may also be present in a monitoring event subscription response message, if the "UEId_retrieval" feature is supported and the corresponding request message includes the "uelpAddr" attribute or the "ueMacAddr" attribute. (NOTE 1) (NOTE 5) | | +| msisdn | Msisdn | 0..1 | Identifies the MS internal PSTN/ISDN number allocated for a UE. (NOTE 1) (NOTE 5) | | +| addedExternalIds | array(ExternalId) | 0..N | Indicates addition of the external Identifier(s) within the active group. | Partial_group_modification | +| addedMsisdns | array(Msisdn) | 0..N | Indicates addition of the MSISDN(s) within the active group. | Partial_group_modification | +| excludedExternalIds | array(ExternalId) | 0..N | Indicates cancellation of the external Identifier(s) within the active group. | Partial_group_modification | +| excludedMsisdns | array(Msisdn) | 0..N | Indicates cancellation of the MSISDN(s) within the active group. | Partial_group_modification | +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in Clause 4.6.2 of 3GPP TS 23.682 [2]. (NOTE 1) (NOTE 6) | | +| addExtGroupIds | array(ExternalGroupId) | 0..N | Identifies user groups as defined in Clause 4.6.2 of 3GPP TS 23.682 [2]. (NOTE 1) (NOTE 6) | Number_of_UEs_in_an_area_notification, Number_of_UEs_in_an_area_notification_5G | +| ipv4Addr | Ipv4Addr | 0..1 | Identifies the Ipv4 address. (NOTE 1) | Location_notification, Communication_failure_notification | +| ipv6Addr | Ipv6Addr | 0..1 | Identifies the Ipv6 address. (NOTE 1) | Location_notification, Communication_failure_notification | +| dnn | Dnn | 0..1 | Identifies a DNN, a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only. (NOTE 8) (NOTE 16) | Session_Management_Enhancement, UEId_retrieval, AppDetection_5G | +| notificationDestination | Link | 1 | An URI of a notification destination that T8 message shall be delivered to. | | +| requestTestNotification | boolean | 0..1 | Set to "true" by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. | Notification_test_event | + +| | | | | | +|--|--|--|--------------------------------------------------------------------------------------------------------------------|--| +| | | | Set to "false" by the SCS/AS indicates not request SCEF to send a test notification
Default "false" if omitted. | | +|--|--|--|--------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | +|------------------------|--------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| websocketNotifConfig | WebsockNotifConfig | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 5.2.5.4. | Notification_websocket | +| monitoringType | MonitoringType | 1 | Enumeration of monitoring type. Refer to clause 5.3.2.4.3. | | +| maximumNumberOfReports | integer | 0..1 | Identifies the maximum number of event reports to be generated by the HSS, MME/SGSN as specified in clause 5.6.0 of 3GPP TS 23.682 [2].
(NOTE 2, NOTE 9, NOTE 13)

If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to (or contains) the "NUM_OF_REGD_UES" or "NUM_OF_ESTD_PDU_SESSIONS" values, this attribute may also be provided with a value of 1 to indicate that one-time reporting of the network slice status information is requested by the AF. | | +| monitorExpireTime | DateTime | 0..1 | Identifies the absolute time at which the related monitoring event request is considered to expire, as specified in clause 5.6.0 of 3GPP TS 23.682 [2].

When the "monitoringType" attribute (or the "addnMonTypes" attribute) is set to either "NUM_OF_REGD_UES" or "NUM_OF_ESTD_PDU_SESSIONS", this attribute shall be absent in the response to a one-time reporting monitoring subscription request.
(NOTE 2) | | +| repPeriod | DurationSec | 0..1 | Identifies the periodic time for the event reports. (NOTE 8, NOTE 9, NOTE 13)

If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "NUM_OF_REGD_UES" or "NUM_OF_ESTD_PDU_SESSIONS", this attribute may be provided. When provided, it also indicates that periodic reporting of the network slice status information is requested by the AF. | | +| groupReportGuardTime | DurationSec | 0..1 | Identifies the time for which the SCEF can aggregate the monitoring event reports detected by the UEs in a group and report them together to the SCS/AS, as specified in clause 5.6.0 of 3GPP TS 23.682 [2]. | | +| maximumDetectionTime | DurationSec | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOSS_OF_CONNECTIVITY", this parameter may be included to identify the maximum period of time after which the UE is considered to be unreachable. | Loss_of_connectivity_notification | +| reachabilityType | ReachabilityType | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "UE_REACHABILITY", this parameter shall be included to identify whether the request is for "Reachability for SMS" or "Reachability for Data". | Ue-reachability_notification | +| maximumLatency | DurationSec | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "UE_REACHABILITY", this parameter may be included to identify the maximum delay acceptable for downlink data transfers. | Ue-reachability_notification | +| maximumResponseTi | DurationSec | 0..1 | If "monitoringType" attribute (or the | Ue- | + +| | | | | | +|-----------------------------|--------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| me | | | "addnMonTypes" attribute) is set to "UE_REACHABILITY", this parameter may be included to identify the length of time for which the UE stays reachable to allow the SCS/AS to reliably deliver the required downlink data. | reachability_no tification | +| suggestedNumberOfDI Packets | integer | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "UE_REACHABILITY", this parameter may be included to identify the number of packets that the serving gateway shall buffer in case that the UE is not reachable. | Ue- reachability- notification | +| idleStatusIndication | boolean | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "UE_REACHABILITY" or "AVAILABILITY_AFTER_DDN_FAILURE", this parameter may be included to indicate the notification of when a UE, for which PSM is enabled, transitions into idle mode.
- "true": indicate enabling of notification
- "false": indicate no need to notify
Default: "false" if omitted. | Ue- reachability_no tification, Availability_afte r_DDN_failure_ notification, Availability_afte r_DDN_failure_ notification_en hancement | +| locationType | LocationType | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING" or "NUMBER_OF_UES_IN_AN_AREA", this parameter shall be included to identify whether the request is for Current Location, Initial Location or Last known Location.
(NOTE 4) | Location_notific ation, Number_of_UE s_in_an_area_ notification, Number_of_UE s_in_an_area_ notification_5G, eLCS | +| accuracy | Accuracy | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to identify the desired level of accuracy of the requested location information, as described in clause 4.9.2 of 3GPP TS 23.682 [2].
(NOTE 10, NOTE 11)
For 5G, if the eLCS feature is not supported, the default value is "TA_RA". | Location_notific ation, eLCS | +| minimumReportInterval | DurationSec | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to identify a minimum time interval between Location Reporting notifications.
If the "ldrType" attribute is present and set to "ENTERING_INTO_AREA", "LEAVING_FROM_AREA", "BEING_INSIDE_AREA" or "MOTION", this attribute shall not be included if the maximumNumberOfReports attribute is present and set to one time event. | Location_notific ation, eLCS | +| maxRptExpireIntvl | DurationSec | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to identify a maximum time interval between Location Reporting notifications.
If the "ldrType" attribute is present and set to "ENTERING_INTO_AREA", "LEAVING_FROM_AREA", "BEING_INSIDE_AREA" or "MOTION", this attribute shall not be included if the maximumNumberOfReports attribute is | eLCS | + +| | | | | | +|--|--|--|------------------------------------|--| +| | | | present and set to one time event. | | +|--|--|--|------------------------------------|--| + +| | | | | | +|--------------------|-----------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| samplingInterval | DurationSec | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to identify the maximum time interval between consecutive evaluations by a UE of a trigger event. | eLCS | +| reportingLocEstInd | boolean | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to indicate whether event reporting requires the location information.

Set to "true", indicates the location estimation information shall be included in event reporting.

Set to "false", indicates the location estimation information shall not be included in event reporting.

Default: "false" if omitted. | eLCS | +| linearDistance | LinearDistance | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to indicate the linear(straight line) distance threshold for motion event reporting. | eLCS | +| locQoS | LocationQoS | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to indicate the expected location QoS requirement for an immediate MT-LR or deferred MT-LR.

The "Multiple QoS Class" (i.e. the "IcsQoSClass" attribute within the LocationQoS data structure is set to "MULTIPLE_QOS") shall only be used when the "MULTIQOS" feature is supported.

(NOTE 10) | eLCS, MULTIQOS | +| svcId | ServiceIdentity | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to indicate the service identity of AF. | eLCS | +| ldrType | LdrType | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to indicate the event type for a deferred MT-LR. | eLCS | +| velocityRequested | VelocityRequested | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to indicate if the velocity of the target UE is requested or not. | eLCS | +| maxAgeOfLocEst | AgeOfLocationEstimate | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to indicate acceptable maximum age of location estimate. | eLCS | +| locTimeWindow | TimeWindow | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this | eLCS | + +| | | | | | +|--|--|--|-----------------------------------------------------------------------------------------------|--| +| | | | parameter may be included to indicate the starting time and ending time for a deferred MT-LR. | | +|--|--|--|-----------------------------------------------------------------------------------------------|--| + +| | | | | | +|--------------------|---------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| supportedGADShapes | array(SupportedGADShapes) | 0..N | Supported Geographical Area Description shapes. | eLCS | +| codeWord | CodeWord | 0..1 | Code word. | eLCS | +| upLocRepIndAf | boolean | 0..1 |

If the "LOCATION_REPORTING" value is set in either the "monitoringType" attribute or the "addnMonTypes" attribute, this attribute may be included to convey the indication of location reporting over user plane.

When present, this attribute shall be set as follows:
"true": the location reporting over user plane is required.
>false": the location reporting over user plane is not required.
Default: "false" if omitted.

| eLCS_en | +| upLocRepAddrAf | UpLocRepAddrAfRm | 0..1 | If the "upLocRepIndAf" attribute is present and set to "true", this attribute may be present to convey the AF's user plane addressing information to be used for location reporting over user plane. | eLCS_en | +| associationType | AssociationType | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "CHANGE_OF_IMSI_IMEI_ASSOCIATION", this parameter shall be included to identify whether the change of IMSI-IMEI or IMSI-IMEISV association shall be detected. | Change_of_IMSI_IMEI_association_notification | +| plmnIndication | boolean | 0..1 |

If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "ROAMING_STATUS", this parameter may be included to indicate the notification of UE's Serving PLMN ID.

  • - "true": The value shall be used to indicate enabling of notification;
  • - "false": The value shall be used to indicate disabling of notification.

Default: "false" if omitted.

| Roaming_status_notification | +| locationArea | LocationArea | 0..1 |

If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "NUMBER_OF_UES_IN_AN_AREA", this parameter may be included to indicate the area within which the SCS/AS requests the number of UEs.

If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "AREA_OF_INTEREST", this parameter shall be included to indicate the area within which the SCS/AS requests the presence status of a specific UAV.

| Number_of_UEs_in_an_area_notification, UAV | +| locationArea5G | LocationArea5G | 0..1 |

If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "NUMBER_OF_UES_IN_AN_AREA", this parameter may be included to indicate the area within which the AF requests the number of UEs.

If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "LOCATION_REPORTING", this parameter may be included to indicate the area within which the AF requests the area event of the target UE. (NOTE 12)

If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to

| Number_of_UEs_in_an_area_notification_5G, eLCS, UAV | + +| | | | | | +|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | "AREA_OF_INTEREST", this parameter shall be included to indicate the area within which the AF requests the presence status of a specific UAV. | | +|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | +|-----------------------|------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| dddTraDescriptors | array(DddTraffic Descriptor) | 0..N | The traffic descriptor(s) of the downlink data source. May be included for event "DOWNLINK_DATA_DELIVERY_STATUS" or "AVAILABILITY_AFTER_DDN_FAILURE". | Downlink_data_delivery_status_5G, Availability_after_DDN_failure_notification_enhancement | +| dddStati | array(DlDataDeliveryStatus) | 0..N | May be included for event "DOWNLINK_DATA_DELIVERY_STATUS". The subscribed stati (delivered, transmitted, buffered) for the event. If omitted all stati are subscribed. | Downlink_data_delivery_status_5G | +| monitoringEventReport | MonitoringEvent Report | 0..1 | Identifies a monitoring event report which is sent from the SCEF to the SCS/AS. | | +| apiNames | array(string) | 0..N |

If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "API_SUPPORT_CAPABILITY", this parameter may be included. Each element identifies the name of an API.

It shall set as {apiName} part of the URI structure for each T8 or N33 API as defined in the present specification or 3GPP TS 29.522 [62], respectively.

This allows the SCS/AS to request the capability change for its interested APIs. If it is omitted, the SCS/AS requests to be notified for capability change for all APIs the SCEF+NEF supports.

| API_support_capability_notification | +| tgtNsThreshold | SACInfo | 0..1 |

Indicates the monitoring threshold value, for the network slice identified by the "snssai" attribute, upon which event notification(s) are triggered.

This attribute may be provided if the "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "NUM_OF_REGD_UES" or "NUM_OF_ESTP_PDU_SESSIONS". When provided, it also indicates that threshold based reporting of the network slice status information is requested by the AF.

(NOTE 13)

| NSAC | +| nsRepFormat | SACRepFormat | 0..1 |

Indicates the requested NSAC reporting format, i.e. "PERCENTAGE" or "NUMERICAL".

It shall be provided only if the "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "NUM_OF_REGD_UES" or "NUM_OF_ESTP_PDU_SESSIONS" and periodic reporting is requested (i.e. the "repPeriod" attribute is provided instead of the "tgtNsThreshold" attribute) or one-time reporting is requested (i.e. the "maximumNumberOfReports" attribute is provided with a value of 1).

| NSAC | +| afServiceId | string | 0..1 |

Contains the identifier of a service on behalf of which the AF is sending the request.

It may be provided by an untrusted AF and only if the "monitoringType" attribute (or the "addnMonTypes" attribute) is set to

| NSAC | + +| | | | | | +|--|--|--|-------------------------------------------------------------------------|--| +| | | | either "NUM_OF_REGD_UES" or
"NUM_OF_ESTD_PDU_SESSIONS".
(NOTE 15) | | +|--|--|--|-------------------------------------------------------------------------|--| + +| | | | | | +|--------------|-----------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| +| snssai | Snssai | 0..1 | Indicates the S-NSSAI that the event monitoring subscription is targeting.

This attribute may be provided if the "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "NUM_OF_REGD_UES" or "NUM_OF_ESTD_PDU_SESSIONS".

This attribute may also be provided if the "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "PDN_CONNECTIVITY_STATUS" or "DOWNLINK_DATA_DELIVERY_STATUS".

(NOTE 8) (NOTE 15) (NOTE 16) | NSAC, Session_Management_Enhancement, UEId_retrieval, AppDetection_5G | +| immediateRep | boolean | 0..1 | Indicates that immediate reporting is requested or not.
- "true": indicate an immediate reporting is requested.

- "false": indicate an immediate reporting is not requested.

Default value: "false" if omitted.

This attribute may be included if the "monitoringType" attribute (or the "addnMonTypes" attribute) is set to either "NUM_OF_REGD_UES" or "NUM_OF_ESTD_PDU_SESSIONS" when the "NSAC" feature is supported. (NOTE 13)

This attribute may also be included if the SCS/AS requires immediate reporting of the subscribed event(s) when the "enNB1_5G" feature is supported. (NOTE 4) | NSAC, enNB1_5G | +| uavPolicy | UavPolicy | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "AREA_OF_INTEREST", this parameter may be included to indicate the 3GPP network to take corresponding action. | UAV | +| subType | SubType | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "NUMBER_OF_UES_IN_AN_AREA", this parameter may be included to indicate the subscription type to be listed in the Event report.

(NOTE 14) | UAV | +| sesEstInd | boolean | 0..1 | If "monitoringType" attribute (or the "addnMonTypes" attribute) is set to "NUMBER_OF_UES_IN_AN_AREA", this parameter may be included.
If set to "true", it indicates that only UE's with "PDU session established for DNN(s) subject to aerial service" are to be listed in the Event report.

If set to "false", it indicates that UE's with "PDU session established for DNN(s) subject to aerial service" are not to be listed in the Event report.

Default: "false" if omitted. | UAV | + +| | | | | | +|--|--|--|-----------|--| +| | | | (NOTE 14) | | +|--|--|--|-----------|--| + +| | | | | | +|---------------------|-------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| addnMonTypes | array(Monitoring Type) | 0..N | Represents additional monitoring types.
(NOTE 17) | enNB | +| addnMonEventReports | array(Monitoring EventReport) | 0..N | Additional monitoring event reports. May only be provided if the "addnMonTypes" attribute is provided in the corresponding subscription creation/update request. | enNB | +| uelpAddr | lpAddr | 0..1 | UE IP address. | UEId_retrieval | +| ueMacAddr | MacAddr48 | 0..1 | UE MAC address. | UEId_retrieval | +| revocationNotifUri | Uri | 0..1 | Contains the URI via which the AF desires to receive user consent revocation notifications. | UserConsentRevocation | +| reqRangingSIRes | array(RangingSI Result) | 1..N | Contains the type of result requested for ranging and sidelink positioning. | Ranging_SL | +| relatedUEs | array(RelatedUE ) | 1..N | Contains a list of the information for the related UEs for the ranging and sidelink positioning. | Ranging_SL | + +NOTE 1: One of the properties "externalId", "msisdn", "ipv4Addr", "ipv6Addr" or "externalGroupId" shall be included for features "Location\_notification" and "Communication\_failure\_notification". One of the properties "externalId", "msisdn" or "externalGroupId" shall be included for feature "eLCS". "ipv4Addr" or "ipv6Addr" is required for monitoring via the PCRF for an individual UE. One of the properties "externalId", "msisdn" or "externalGroupId" shall be included for features "Pdn\_connectivity\_status", "Loss\_of\_connectivity\_notification", "Ue-reachability\_notification", "Change\_of\_IMSI\_IMEI\_association\_notification", "Roaming\_status\_notification", "Availability\_after\_DDN\_failure\_notification" and "Availability\_after\_DDN\_failure\_notification\_enhancement". The property "externalGroupId" shall be included for the "GMEC" feature to subscribe to the group member list change event reporting. + +NOTE 2: Inclusion of either "maximumNumberOfReports" (with a value higher than 1) or "monitorExpireTime" makes the Monitoring Request a Continuous Monitoring Request, where the SCEF sends Notifications until either the maximum number of reports or the monitoring duration indicated by the property "monitorExpireTime" is exceeded. The "maximumNumberOfReports" with a value 1 makes the Monitoring Request a One-time Monitoring Request. At least one of "maximumNumberOfReports" or "monitorExpireTime" shall be provided. + +NOTE 3: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +NOTE 4: In this release, for features "Number\_of\_UEs\_in\_an\_area\_notification" and "Number\_of\_UEs\_in\_an\_area\_notification\_5G", locationType shall be set to "LAST\_KNOWN\_LOCATION". For 5G, if the "locationType" attribute sets to "LAST\_KNOWN\_LOCATION", the "maximumNumberOfReports" attribute shall set to 1 as a One-time Monitoring Request. For 5G, when the "enNB1\_5G" feature is supported and the "immediateRep" attribute is present set to "true" and outside the scope of the "NSAC" feature, then the "locationType" shall be set to "LAST\_KNOWN\_LOCATION"; when the "immediateRep" is present set to "false" and outside the scope of the "NSAC" feature, then the "locationType" shall be set to "CURRENT\_LOCATION". + +NOTE 5: The property does not apply for the features "Number\_of\_UEs\_in\_an\_area\_notification" and "Number\_of\_UEs\_in\_an\_area\_notification\_5G". + +NOTE 6: For the features "Number\_of\_UEs\_in\_an\_area\_notification" and "Number\_of\_UEs\_in\_an\_area\_notification\_5G", the property "externalGroupId" may be included for single group and "addExtGroupIds" may be included for multiple groups but not both. + +NOTE 7: The SCEF should check received MTC provider identifier and then the SCEF may: + +- override it with local configured value and send it to HSS; +- send it directly to the HSS; or +- reject the monitoring configuration request. + +NOTE 8: This property is only applicable for the NEF. + +NOTE 9: The value of the "maximumNumberOfReports" attribute sets to 1 and the "repPeriod" attribute are mutually exclusive. + +NOTE 10: If the "eLCS" feature is supported, the "accuracy" attribute and "locQoS" attribute are mutually exclusive, and only the "GEO\_AREA" value is applicable for the "accuracy" attribute. + +NOTE 11: The value of "TWAN\_ID" is only applicable when the monitoring subscription is via the PCRF as described in clause 4.4.2.2.4. + +NOTE 12: If the "eLCS" feature is supported, only the "geographicAreas" attribute within the "locationArea5G" attribute is applicable. + +NOTE 13: For the "NSAC" feature, if the "maximumNumberOfReports" attribute is provided with a value of 1, the "repPeriod" attribute and the "tgtNsThreshold" attribute shall not be provided and the "immediateRep" attribute shall be provided and set to true; otherwise, either the "repPeriod" attribute or the "tgtNsThreshold" attribute shall be provided, and if immediate reporting is requested, the "immediateRep" attribute shall be provided and set to true. + +NOTE 14: For the feature "UAV", the event "Number of UEs present in a geographical area" is used, where "subType" indication and/or "sesEstInd" may be used as event filters. + +NOTE 15: For the "NSAC" feature, the "snssai" and "afServiceId" attributes are mutually exclusive. + +NOTE 16: For the "AppDetection\_5G" feature, AF shall provide the "appId" attribute along with "snssai" and "dnn" attributes for subscription of application traffic detection event notification. the subscription request applies to all the UEs associated with the "snssai" and the "dnn" provided in the request. + +NOTE 17: When the "enNB" feature is supported and the "addnMonTypes" attribute is present and contains at least one array element, then this attribute shall not contain an array element set to the same value as the "monitoringType" attribute. + +#### 5.3.2.1.3 Void + +### 5.3.2.2 Notification data types + +#### 5.3.2.2.1 Introduction + +This clause defines data structures to be used in notifications. + +#### 5.3.2.2.2 Type: MonitoringNotification + +This data type represents a monitoring notification which is sent from the SCEF to the SCS/AS. + +**Table 5.3.2.2.2-1: Definition of type MonitoringNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|------------------------|-------------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| subscription | Link | 1 | Link to the subscription resource to which this notification is related. | | +| configResults | array(ConfigResult) | 0..N | Each element identifies a notification of grouping configuration result. | | +| monitoringEventReports | array(MonitoringEventReport) | 0..N | Each element identifies a monitoring event report. | | +| addedExternalIds | array(ExternalId) | 0..N | Identifies the added external Identifier(s) within the active group via the "externalGroupId" attribute within the MonitoringEventSubscription data type. | Partial_group_modification | +| addedMsisdns | array(Msisdn) | 0..N | Identifies the added MSISDN(s) within the active group via the "externalGroupId" attribute within the MonitoringEventSubscription data type. | Partial_group_modification | +| cancelExternalIds | array(ExternalId) | 0..N | Identifies the cancelled external Identifier(s) within the active group via the "externalGroupId" attribute within the MonitoringEventSubscription data type. | Partial_group_modification | +| cancelInd | Boolean | 0..1 | Indicates whether to request to cancel the corresponding monitoring subscription. Set to false or omitted otherwise. | | +| cancelMsisdns | array(Msisdn) | 0..N | Identifies the cancelled MSISDN(s) within the active group via the "externalGroupId" attribute within the MonitoringEventSubscription data. | Partial_group_modification | +| appliedParam | AppliedParameterConfiguration | 0..1 | Indicates the applied parameter configuration in the network. For the attributes included in AppliedParameterConfiguration data type, the "maximumLatency" and "maximumResponseTime" attributes require the "Ue-reachability_notification" feature support, and the "maximumDetectionTime" attribute requires the "Loss_of_connectivity_notification" feature support. | Enhanced_param_config | + +NOTE: Properties marked with a feature as defined in subclause 5.3.4 are applicable as described in subclause 5.2.7. If no features are indicated, the related property applies for all the features. + +### 5.3.2.3 Referenced structured data types + +#### 5.3.2.3.1 Introduction + +This clause defines structured data types that are referenced from data structures defined in the previous clauses. + +#### 5.3.2.3.2 Type: MonitoringEventReport + +This data type represents a monitoring event notification which is sent from the SCEF to the SCS/AS. + +**Table 5.3.2.3.2-1: Definition of type MonitoringEventReport** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-----------------------|-----------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| +| imeiChange | AssociationType | 0..1 | If "monitoringType" is "CHANGE_OF_IMSI_IMEI_ASSOCIATION", this parameter shall be included to identify the event of change of IMSI-IMEI or IMSI-IMEISV association is detected.
Refer to 3GPP TS 29.336 [11] Clause 8.4.22. | Change_of_IMSI_IMEI_association_notification | +| externalId | ExternalId | 0..1 | External identifier.
This attribute may also be present in the monitoring event subscription one-time response message, if the "UEId_retrieval" feature is supported and the corresponding request message includes the "uelpAddr" attribute or the "ueMacAddr" attribute.
(NOTE 2) | | +| appId | string | 0..1 | Represents the detected application. | AppDetection_5G | +| pduSessInfo | PduSessionInformation | 0..1 | Represents PDU session information related to the observed event.
If "monitoringType" is "APPLICATION_START" and/or "APPLICATION_STOP", this parameter may be included to indicate the Application traffic detection details. | AppDetection_5G | +| idleStatusInfo | IdleStatusInfo | 0..1 | If "idleStatusIndication" in the "MonitoringEventSubscription" sets to "true", this parameter shall be included to indicate the information when the UE transitions into idle mode. | Ue-reachability_notification, Availability_after_DDN_failure_notification | +| locationInfo | LocationInfo | 0..1 | If "monitoringType" is "LOCATION_REPORTING", this parameter shall be included to indicate the user location related information. | Location_notification, eLCS | +| locFailureCause | LocationFailureCause | 0..1 | Indicates the location positioning failure cause. | eLCS | +| lossOfConnectReason | integer | 0..1 | If "monitoringType" is "LOSS_OF_CONNECTIVITY", this parameter shall be included if available to identify the reason why loss of connectivity is reported.
Refer to 3GPP TS 29.336 [11] Clause 8.4.58. | Loss_of_connectivity_notification | +| unavailPerDur | DurationSec | 0..1 | If "monitoringType" is "LOSS_OF_CONNECTIVITY", then this parameter shall be included if available to identify the UE's Unavailability Period Duration. | Loss_of_connectivity_notification_5G | +| maxUEAvailabilityTime | DateTime | 0..1 | If "monitoringType" is "UE_REACHABILITY", this parameter may be included to identify the timestamp until which a UE using a power saving mechanism is expected to be reachable for SM delivery. | Ue-reachability_notification | + +| | | | | | +|--|--|--|-----------------------------------------------------|--| +| | | | Refer to Clause 5.3.3.22 of
3GPP TS 29.338 [34]. | | +|--|--|--|-----------------------------------------------------|--| + +| | | | | | +|---------------------|----------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------| +| msisdn | Msisdn | 0..1 | Identifies the MS internal PSTN/ISDN number.
(NOTE 2) | | +| monitoringType | MonitoringType | 1 | Identifies the type of monitoring type as defined in clause 5.3.2.4.3. | | +| uePerLocationReport | UePerLocationReport | 0..1 | If "monitoringType" is "NUMBER_OF_UES_IN_AN_ARE A", this parameter shall be included to indicate the number of UEs found at the location.
If "subType" indicates "AERIAL_UE" subscription type, this parameter shall be included to indicate the number of UAV's found at the location. | Number_of_U Es_in_an_are a_notification, Number_of_U Es_in_an_are a_notification _5G | +| plmnId | PlmnId | 0..1 | If "monitoringType" is "ROAMING_STATUS" and "plmnIndication" in the "MonitoringEventSubscription" sets to "true", this parameter shall be included to indicate the UE's serving PLMN. | Roaming_stat us_notification n | +| reachabilityType | ReachabilityType | 0..1 | If "monitoringType" is "UE_REACHABILITY", this parameter shall be included to identify the reachability of the UE.
Refer to 3GPP TS 29.336 [11] Clause 8.4.20. | Ue- reachability_n otification | +| roamingStatus | boolean | 0..1 | If "monitoringType" is "ROAMING_STATUS", this parameter shall be set to "true" if the new serving PLMN is different from the HPLMN. Set to false or omitted otherwise. | Roaming_stat us_notification n | +| failureCause | FailureCause | 0..1 | If "monitoringType" is "COMMUNICATION_FAILURE", this parameter shall be included to indicate the reason of communication failure. | Communicati on_failure_no tification | +| eventTime | DateTime | 0..1 | Identifies when the event is detected or received.
Shall be included for each group of UEs. | | +| pdnConnInfoList | array(PdnConnectionInf ormation) | 0..N | If "monitoringType" is "PDN_CONNECTIVITY_STATUS", this parameter shall be included to indicate the PDN connection details. | Pdn_connecti vity_status | +| dddStatus | DIDataDeliveryStatus | 0..1 | If "monitoringType" is "DOWNLINK_DATA_DELIVERY_S TATUS", this parameter shall be included to identify the downlink data delivery status detected by the network. | Downlink_dat a_delivery_st atus_5G | +| dddTrafDescriptor | DddTrafficDescriptor | 0..1 | If "monitoringType" is "DOWNLINK_DATA_DELIVERY_S TATUS", this parameter shall be included to identify the downlink data descriptor impacted by the downlink data delivery status change. | Downlink_dat a_delivery_st atus_5G | +| maxWaitTime | DateTime | 0..1 | If "monitoringType" is "DOWNLINK_DATA_DELIVERY_S | Downlink_dat a_delivery_st | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| | | | TATUS", this parameter may be included to identify the time before which the data will be buffered. | atus_5G | +| apiCaps | array(ApiCapabilityInfo) | 0..N | If "monitoringType" is "API_SUPPORT_CAPABILITY", this parameter shall be included to indicate the availability of all APIs supported by the serving network or the availability of interested APIs, indicated by the "apiNames" attribute in "MonitoringEventSubscription", supported by the serving network.
If no API is supported by the serving network, an empty apiCaps shall be provided. | API_support_capability_notification | +| nSStatusInfo | SACEventStatus | 0..1 | If the "monitoringType" attribute is set to "NUM_OF_REGD_UES" or "NUM_OF_ESTD_PDU_SESSIONS", this parameter shall be included to indicate the current network slice status information for the concerned network slice.
(NOTE 3) | NSAC | +| afServiceId | string | 0..1 | Contains the identifier of the service to which the NSAC reporting is related.

It shall be provided only if it is present in the related NSAC subscription request and the "monitoringType" attribute is set to either "NUM_OF_REGD_UES" or "NUM_OF_ESTD_PDU_SESSIONS". | NSAC | +| servLevelDevId | string | 0..1 | If "monitoringType" is "AREA_OF_INTEREST" or "NUMBER_OF_UES_IN_AN_AREA" and "subType" indicate "AERIAL_UE", this parameter may be included to identify the UAV. | UAV | +| uavPresInd | boolean | 0..1 | If "monitoringType" is "AREA_OF_INTEREST", this parameter shall be set to true if the specified UAV is in the monitoring area. Set to false or omitted otherwise. | UAV | +| groupMembListChanges | GroupMembListChanges | 0..1 | Contains information on the change(s) to the group member list.

This attribute shall be present only if the "monitoringType" attribute is set to "GROUP_MEMBER_LIST_CHANGE". | GMEC | +| NOTE 1: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | +| NOTE 2: Identifies the user for which the event occurred. At least one of the properties shall be included. | | | | | +| NOTE 3: If the "eNSAC" feature is supported, the "SACEventStatus" data type shall include an indication to report either the current number of registered UEs or the current number of UEs with at least one PDU session/PDN connection. | | | | | + +### 5.3.2.3.3 Type: IdleStatusInfo + +This data type represents the information when the UE transitions into idle mode. It is sent from the SCEF to the SCS/AS. + +**Table 5.3.2.3.3-1: Definition of type IdleStatusInfo** + +| Attribute name | Data type | Cardinality | Description | +|---------------------------|-------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| activeTime | DurationSec | 0..1 | Identifies the active time granted to the UE. It shall be present if the idle status indication is requested by the SCS/AS with "idleStatusIndication" in the "monitoringEventSubscription" sets to "true". | +| edrxCycleLength | number | 0..1 | Identifies the power saving interval in unit of seconds. It shall be present if the idle status indication is requested by the SCS/AS with "idleStatusIndication" in the "monitoringEventSubscription" sets to "true". | +| suggestedNumberOfDPackets | integer | 0..1 | Identifies the number of packets shall be buffered in the serving gateway. It shall be present if the idle status indication is requested by the SCS/AS with "idleStatusIndication" in the "monitoringEventSubscription" sets to "true". | +| idleStatusTimestamp | DateTime | 0..1 | Identifies the timestamp at which the UE transitions into idle mode. It shall be present if the idle status indication is requested by the SCS/AS with "idleStatusIndication" in the "monitoringEventSubscription" sets to "true". | +| periodicAUTimer | DurationSec | 0..1 | Identifies the subscribed periodic RAU/TAU timer value. It shall be present if the idle status indication is requested by the SCS/AS with "idleStatusIndication" in the "monitoringEventSubscription" sets to "true". | + +### 5.3.2.3.4 Type: UePerLocationReport + +This data type represents the number of UEs found at the indicated location information. It is sent from the SCEF to the SCS/AS. + +**Table 5.3.2.3.4-1: Definition of type UePerLocationReport** + +| Attribute name | Data type | Cardinality | Description | +|---------------------------------------------------------------------------|-------------------|-------------|----------------------------------------------------------------------------------------| +| ueCount | integer | 1 | Identifies the number of UEs. | +| externalIds | array(ExternalId) | 0..N | Each element uniquely identifies a user.
(NOTE) | +| msisdns | array(Msisdn) | 0..N | Each element identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE) | +| servLevelDevIds | array(string) | 0..N | Each element uniquely identifies a UAV. | +| NOTE: The property shall be included if received from the MME(s)/SGSN(s). | | | | + +### 5.3.2.3.5 Type: LocationInfo + +This data type represents the user location information which is sent from the SCEF to the SCS/AS. + +**Table 5.3.2.3.5-1: Definition of LocationInfo data Type** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|---------------------------|------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| ageOfLocationInfo | DurationMin | 0..1 | Indicates the elapsed time since the last network contact of the UE.

Refer to the Age-Of-Location-Information AVP as defined in clause 7.3.126 of 3GPP TS 29.272 [33]. | | +| cellId | string | 0..1 | Indicates the Cell Global Identification of the user which identifies the cell the UE is registered.
Refer to the Cell-Global-Identity AVP or E-UTRAN-Cell-Global-Identity AVP as defined in clause 7.3.119 or clause 7.3.117 of 3GPP TS 29.272 [33]. (NOTE 2) | | +| eNodeBId | string | 0..1 | Indicates the eNodeB in which the UE is currently located.
Refer to the eNodeB-ID AVP or Extended-eNodeB-ID AVP as defined in clause 7.3.198 or clause 7.3.218 of 3GPP TS 29.272 [33]. | | +| routingAreaId | string | 0..1 | Identifies the Routing Area Identity of the user where the UE is located.
Refer to the Routing-Area-Identity AVP as defined in clause 7.3.120 of 3GPP TS 29.272 [33]. | | +| trackingAreaId | string | 0..1 | Identifies the Tracking Area Identity of the user where the UE is located.
Refer to the Tracking-Area-Identity AVP as defined in clause 7.3.118 of 3GPP TS 29.272 [33]. (NOTE 3) | | +| plmnId | string | 0..1 | Identifies the PLMN Identity of the user where the UE is located.
Refer to the Visited-PLMN-Id AVP as defined in clause 7.3.9 of 3GPP TS 29.272 [33]. | | +| twanId | string | 0..1 | Identifies the TWAN Identity of the user where the UE is located. | | +| userLocation | UserLocation | 0..1 | Contains UE location information. (NOTE 4) | enNB1 | +| geographicArea | GeographicArea | 0..1 | Identifies a geographic area of the user where the UE is located. | | +| civicAddress | CivicAddress | 0..1 | The civic address of the target UE. | eLCS | +| positionMethod | PositioningMethod | 0..1 | Identifies the positioning method used to obtain the location estimate of the UE, if it is available at the LCS server and if needed. | eLCS,
Ranging_SL | +| qosFulfillInd | AccuracyFulfillmentIndicator | 0..1 | Represents whether the requested accuracy is fulfilled or not.
(NOTE 1) | eLCS,
Ranging_SL | +| ueVelocity | VelocityEstimate | 0..1 | UE velocity, if requested and available | eLCS,
Ranging_SL | +| ldrType | LdrType | 0..1 | The IE may be included to indicate the type of event that triggers event notification. | eLCS | +| achievedQos | MinorLocationQoS | 0..1 | When present, this IE shall contain the achieved Location QoS Accuracy of the estimated location.

This IE shall be present if received. | MULTIQOS | +| relatedApplicationLayerId | ApplicationLayerId | 0..1 | Identifies the application layer ID of the related UE for ranging and sidelink positioning, such as located UE, reference UE, etc. | Ranging_SL | +| rangeDirection | RangeDirection | 0..1 | Identifies a range and direction from a point A to a point B, comprising a range from point A to point B, an azimuth direction from point A to point B and an elevation direction from point A to point B. | Ranging_SL | +| twodrelativeLocation | TwodrelativeLocation | 0..1 | Identifies a relative 2D location with uncertainty ellipse, characterised by a point | Ranging_SL | + +| | | | | | +|------------------------|------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| | | | described in 2D local co-ordinates with origin corresponding to another known point, distances r1 and r2 and an angle of orientation A. | | +| threeDrelativeLocation | ThreeDrelativeLocation | 0..1 | Identifies a relative 3D location with uncertainty ellipsoid, characterised by a point described in 3D local co-ordinates with origin corresponding to another known point, distances r1 (the "semi-major uncertainty"), r2 (the "semi-minor uncertainty") and r3 (the "vertical uncertainty") and an angle of orientation A (the "angle of the major axis"). | Ranging_SL | +| relativeVelocity | VelocityEstimate | 0..1 | UE velocity relative to the UE identified with relatedApplicationLayerId. | Ranging_SL | +| upCumEvtRep | UpCumEvtRep | 0..1 | Contains the cumulative event report for events reported via user plane. | eLCS_en | + +NOTE 1: For the eLCS feature, if "reportingLocEstInd" attribute is set to false or omitted during the monitoring event request, the location estimation information shall not be included. Otherwise, if the "reportingLocEstInd" attribute is set to true, and + +- if the "qosFulfillInd" attribute is set to "REQUESTED\_ACCURACY\_FULFILLED", the location estimate information may be included if the "lcsQosClass" attribute within the "locQoS" attribute is set to "BEST\_EFFORT"; or +- if the "qosFulfillInd" attribute is set to "REQUESTED\_ACCURACY\_NOT\_FULFILLED", the location estimate shall not be included if the "lcsQosClass" attribute within "locQoS" attribute is set to "ASSURED". + +NOTE 2: For NEF, the context of the property shall refer to the Ecgi or Ncgi data type as defined in clause 5.4.4.5 or clause 5.4.4.6 of 3GPP TS 29.571 [45]. + +NOTE 3: For NEF, the context of the property shall refer to the Tai data type as defined in clause 5.4.4 of 3GPP TS 29.571 [45]. + +NOTE 4: When the enNB1 feature is supported, the "userLocation" attribute may be provided instead of the "ageOfLocationInfo", "cellId", "encodeBld", "routingAreaId", "trackingAreaId", "plmnId" and "twanId" attributes, when applicable. + +### 5.3.2.3.6 Type: FailureCause + +This data type represents the reason of communication failure. It shall comply with the provisions defined in table 5.3.2.3.6-1. + +**Table 5.3.2.3.6-1: Definition of type FailureCause** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bssgpCause | integer | 0..1 | Identifies a non-transparent copy of the BSSGP cause code.
Refer to 3GPP TS 29.128 [12]. | +| causeType | integer | 0..1 | Identify the type of the S1AP-Cause.
Refer to 3GPP TS 29.128 [12]. | +| gmmCause | integer | 0..1 | Identifies a non-transparent copy of the GMM cause code.
Refer to 3GPP TS 29.128 [12]. | +| ranapCause | integer | 0..1 | Identifies a non-transparent copy of the RANAP cause code.
Refer to 3GPP TS 29.128 [12]. | +| ranNasCause | string | 0..1 | Indicates RAN and/or NAS release cause code information, TWAN release cause code information or untrusted WLAN release cause code information.
Refer to 3GPP TS 29.214 [10].
(NOTE) | +| s1ApCause | integer | 0..1 | Identifies a non-transparent copy of the S1AP cause code.
Refer to 3GPP TS 29.128 [12]. | +| smCause | integer | 0..1 | Identifies a non-transparent copy of the SM cause code.
Refer to 3GPP TS 29.128 [12]. | + +NOTE: If this property is provided in the "FailureCause" type, then other properties shall not be provided. + +### 5.3.2.3.7 Type: PdnConnectionInformation + +This data type represents the PDN connection information of the UE. + +**Table 5.3.2.3.7-1: Definition of type PdnConnectionInformation** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|----------------|---------------------|-------------|--------------------------------------------------------------------------------------------------------------------------|------------------------| +| status | PdnConnectionStatus | 1 | Identifies the PDN connection status. | | +| apn | string | 0..1 | Identifies the APN, it is depending on the SCEF local configuration whether or not this attribute is sent to the SCS/AS. | | +| pdnType | PdnType | 1 | PDN type | | +| interfaceInd | InterfaceIndication | 0..1 | Identifies the 3GPP network function used to communicate with the SCS/AS for non-IP PDN type. | | +| ipv4Addr | Ipv4Addr | 0..1 | Identifies the UE Ipv4 address. | | +| ipv6Addrs | array(Ipv6Addr) | 0..N | Identifies the UE Ipv6 address.
(NOTE 2) | | +| macAddrs | array(MacAddr48) | 0..N | Identifies the UE MAC address(es) which is only available for the immediate report. | | + +NOTE 1: Properties marked with a feature as defined in clause 5.5.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. +NOTE 2: ipv6 prefix is included in this attribute if ipv6 full address is not available. + +### 5.3.2.3.8 Type: AppliedParameterConfiguration + +This data type represents the applied parameter configuration in the network. + +**Table 5.3.2.3.8-1: Definition of type AppliedParameterConfiguration** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------------|-------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| externalIds | array(ExternalId) | 0..N | Each element uniquely identifies a user.
(NOTE) | | +| msisdns | array(Msisdn) | 0..N | Each element identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE) | | +| maximumLatency | DurationSec | 0..1 | This parameter may be included to identify the maximum delay acceptable for downlink data transfers, which is applied in the network. | | +| maximumResponseTime | DurationSec | 0..1 | This parameter may be included to identify the length of time for which the UE stays reachable to allow the SCS/AS to reliably deliver the required downlink data, which is applied in the network. | | +| maximumDetectionTime | DurationSec | 0..1 | This parameter may be included to identify the maximum period of time after which the UE is considered to be unreachable, which is applied in the network. | | + +NOTE: If both are omitted, it means the change applies for the whole configuration (i.e. a single UE or a group of UEs). + +### 5.3.2.3.9 Type: ApiCapabilityInfo + +This data type represents the availability information of a supported API. + +**Table 5.3.2.3.9-1: Definition of type ApiCapabilityInfo** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|-------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| apiName | string | 1 | Identifies the name of an available API provided by the SCEF+NEF. It shall set as {apiName} part of the URI structure for each T8 or N33 API as defined in the present specification or 3GPP TS 29.522 [62], respectively. | | +| suppFeat | SupportedFeatures | 1 | Indicates all the features supported by the API in the serving network, which provided by the SCEF+NEF. | | + +## 5.3.2.3.10 Type: MonitoringEventReports + +**Table 5.3.2.3.10-1: Definition of type MonitoringEventReports** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|------------------------|------------------------------|-------------|---------------------------------------------|----------------------| +| monitoringEventReports | array(MonitoringEventReport) | 1..N | Contains a set of event monitoring reports. | | + +NOTE: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +## 5.3.2.3.11 Type: UavPolicy + +This data type represents the policy information included in the UAV presence monitoring request. + +**Table 5.3.2.3.11-1: Definition of type UavPolicy** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| uavMoveInd | boolean | 1 | Indicates the UAV moves in or moves out of the Area of Interest. Set to true if the UAV moves in the Area of Interest. Set to false if the UAV moves out of the Area of Interest. | | +| revokeInd | boolean | 1 | Indicates whether the connectivity between UAV and UAV controller shall be revoked. If set to true, the connectivity between UAV and UAV controller shall be revoked. Set to false otherwise. | | + +## 5.3.2.3.11 Type: ConsentRevocNotif + +**Table 5.3.2.3.11-1: Definition of type ConsentRevocNotif** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|-----------------|-----------------------|-------------|-----------------------------------------------------------------------------------|---------------| +| subscriptionId | string | 1 | Contains the identifier of the subscription to which the notification is related. | | +| consentsRevoked | array(ConsentRevoked) | 1..N | Indicates the revoked user consents. | | + +## 5.3.2.3.12 Type: ConsentRevoked + +**Table 5.3.2.3.12-1: Definition of type ConsentRevoked** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|------------|-------------|------------------------------------------------------------------------------------|---------------| +| ucPurpose | UcPurpose | 1 | Identifies the purpose of the revoked user consent. | | +| externalId | ExternalId | 0..1 | Indicates the user(s) for which user consent was revoked.
(NOTE) | | +| msisdn | Msisdn | 0..1 | Indicates the MSISDN(s) of the users for which user consent was revoked.
(NOTE) | | + +NOTE: One of the "externalId", or "msisdn" attributes shall be present. + +## 5.3.2.3.13 Type: GroupMembListChanges + +**Table 5.3.2.3.13-1: Definition of type GroupMembListChanges** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|-------------|-------------|----------------------------------------------|---------------| +| addedUEs | array(Gpsi) | 1..N | Identifies the UE(s) added to the group. | | +| removedUEs | array(Gpsi) | 1..N | Identifies the UE(s) removed from the group. | | + +NOTE: At least one of the "addedUEs" attributes and the "removedUEs" attribute shall be provided. + +## 5.3.2.3.14 Type: RangeDirection + +**Table 5.3.2.3.14-1: Definition of type RangeDirection** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|--------------------|-----------|-------------|-------------------------------------------------------------|---------------| +| range | number | 1 | Identifies the distance from point A to point B. | | +| azimuthDirection | Angle | 1 | Identifies the azimuth direction from point A to point B. | | +| elevationDirection | Angle | 1 | Identifies the elevation direction from point A to point B. | | + +## 5.3.2.3.15 Type: TwodrelativeLocation + +**Table 5.3.2.3.15-1: Definition of type TwodrelativeLocation** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|------------------|-------------|-------------|-----------------------------------------------------------|---------------| +| semiMinor | Uncertainty | 1 | Indicates the semi-major axis of the uncertainty ellipse. | | +| semiMajor | Uncertainty | 1 | Indicates the semi-minor axis of the uncertainty ellipse. | | +| orientationAngle | Angle | 1 | Identifies the angle of orientation A. | | + +## 5.3.2.3.16 Type: ThreedrelativeLocation + +**Table 5.3.2.3.16-1: Definition of type ThreedrelativeLocation** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|---------------------|-------------|-------------|-----------------------------------------------------------|---------------| +| semiMinor | Uncertainty | 1 | Indicates the semi-major axis of the uncertainty ellipse. | | +| semiMajor | Uncertainty | 1 | Indicates the semi-minor axis of the uncertainty ellipse. | | +| verticalUncertainty | Uncertainty | 1 | Indicates the vertical uncertainty. | | +| orientationAngle | Angle | 1 | Identifies the angle of orientation A. | | + +### 5.3.2.3.17 Type: UpLocRepAddrAfRm + +**Table 5.3.2.3.17-1: Definition of type UpLocRepAddrAfRm** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|-----------------|-------------|--------------------------------------------------------|---------------| +| ipv4Addrs | array(Ipv4Addr) | 1..N | Contains the IPv4 address(es) of the target.
(NOTE) | | +| ipv6Addrs | array(Ipv6Addr) | 1..N | Contains the IPv6 address(es) of the target.
(NOTE) | | +| fqdn | Fqdn | 0..1 | Contains the FQDN of the target.
(NOTE) | | + +NOTE: At least one of these attributes shall be present. + +### 5.3.2.3.18 Type: UpCumEvtRep + +**Table 5.3.2.3.18-1: Definition of type UpCumEvtRep** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|-----------|-------------|----------------------------------------------------------------------------------------------------------------------------|---------------| +| upLocRepStat | UInteger | 0..1 | Contains the number of location event reports transferred over user plane since the last cumulative event report was sent. | | + +## 5.3.2.4 Referenced simple data types and enumerations + +### 5.3.2.4.1 Introduction + +This clause defines simple data types and enumerations that are referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +### 5.3.2.4.2 Simple data types + +The simple data types defined in table 5.3.2.4.2-1 shall be supported. + +**Table 5.3.2.4.2-1: Simple data types** + +| Type name | Description | +|-----------|-------------| +| | | + +### 5.3.2.4.3 Enumeration: MonitoringType + +The enumeration MonitoringType represents a monitoring event type. It shall comply with the provisions defined in table 5.3.2.4.3-1. + +**Table 5.3.2.4.3-1: Enumeration MonitoringType** + +| Enumeration value | Description | Applicability (NOTE 1) | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| LOSS_OF_CONNECTIVITY | The SCS/AS requests to be notified when the 3GPP network detects that the UE is no longer reachable for signalling or user plane communication | Loss_of_connectivity_notification | +| UE_REACHABILITY | The SCS/AS requests to be notified when the UE becomes reachable for sending either SMS or downlink data to the UE | Ue-reachability_notification | +| LOCATION_REPORTING | The SCS/AS requests to be notified of the current location or the last known location of the UE | Location_notification, eLCS | +| CHANGE_OF_IMSI_IMEI_ASSOCIATION | The SCS/AS requests to be notified when the association of an ME (IMEI(SV)) that uses a specific subscription (IMSI) is changed | Change_of_IMSI_IMEI_association_notification | +| ROAMING_STATUS | The SCS/AS queries the UE's current roaming status and requests to get notified when the status changes | Roaming_status_notification | +| COMMUNICATION_FAILURE | The SCS/AS requests to be notified of communication failure events | Communication_failure_notification | +| AVAILABILITY_AFTER_DDN_FAILURE | The SCS/AS requests to be notified when the UE has become available after a DDN failure | Availability_after_DDN_failure_notification,
Availability_after_DDN_failure_notification_enhancement | +| NUMBER_OF_UES_IN_AN_AREA | The SCS/AS requests to be notified the number of UEs in a given geographic area | Number_of_UEs_in_an_area_notification,
Number_of_UEs_in_an_area_notification_5G | +| PDN_CONNECTIVITY_STATUS | The SCS/AS requests to be notified when the 3GPP network detects that the UE's PDN connection is set up or torn down. | Pdn_connectivity_status | +| DOWNLINK_DATA_DELIVERY_STATUS | The AF requests to be notified when the 3GPP network detects that the downlink data delivery status is changed. | Downlink_data_delivery_status_5G | +| API_SUPPORT_CAPABILITY | The SCS/AS requests to be notified of the availability of support of service APIs. | API_support_capability_notification | +| NUM_OF_REGD_UES | The AF requests to be notified of the current number of registered UEs for a network slice. | NSAC | +| NUM_OF_ESTD_PDU_SESSIONS | The AF requests to be notified of the current number of established PDU Sessions for a network slice. | NSAC | +| AREA_OF_INTEREST | The SCS/AS requests to be notified when the UAV moves in or out of the geographic area. | UAV | +| GROUP_MEMBER_LIST_CHANGE | The AF requests to be notified of the changes to a group members list. | GMEC | +| APPLICATION_START | The AF requests to be notified about the start of application traffic has been detected. | AppDetection_5G | +| APPLICATION_STOP | The AF requests to be notified about the stop of application traffic has been detected. | AppDetection_5G | + +NOTE 1: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. +NOTE 2: More monitoring types can be added in the future based on stage 2. + +#### 5.3.2.4.4 Enumeration: ReachabilityType + +The enumeration ReachabilityType represents a reachability type. It shall comply with the provisions defined in table 5.3.2.4.4-1. If reachabilityType set to "SMS", the monitoring event request from SCS/AS shall be only for one-time monitoring request. + +**Table 5.3.2.4.4-1: Enumeration ReachabilityType** + +| Enumeration value | Description | Applicability (NOTE) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------| +| SMS | The SCS/AS requests to be notified when the UE becomes reachable for sending SMS to the UE | Ue-reachability_notification | +| DATA | The SCS/AS requests to be notified when the UE becomes reachable for sending downlink data to the UE | Ue-reachability_notification | +| NOTE: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | + +#### 5.3.2.4.5 Enumeration: LocationType + +The enumeration LocationType represents a location type. It shall comply with the provisions defined in table 5.3.2.4.5-1. If locationType set to "LAST\_KNOWN\_LOCATION", the monitoring event request from SCS/AS shall be only for one-time monitoring request. + +**Table 5.3.2.4.5-1: Enumeration LocationType** + +| Enumeration value | Description | Applicability (NOTE) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| CURRENT_LOCATION | The SCS/AS requests to be notified for current location | Location_notification, eLCS | +| LAST_KNOWN_LOCATION | The SCS/AS requests to be notified for last known location | Location_notification, Number_of_UEs_in_an_area_notification, Number_of_UEs_in_an_area_notification_5G | +| CURRENT_OR_LAST_KNOWN_LOCATION | The AF requests the current or last known location. | eLCS | +| INITIAL_LOCATION | The AF requests the initial location. | eLCS | +| NOTE: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | + +#### 5.3.2.4.6 Enumeration: AssociationType + +The enumeration AssociationType represents an IMEI or IMEISV to IMSI association. It shall comply with the provisions defined in table 5.3.2.4.6-1. + +**Table 5.3.2.4.6-1: Enumeration AssociationType** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|----------------------------------------------| +| IMEI | The value shall be used when the change of IMSI-IMEI association shall be detected | Change_of_IMSI_IMEI_association_notification | +| IMEISV | The value shall be used when the change of IMSI-IMEISV association shall be detected | Change_of_IMSI_IMEI_association_notification | +| NOTE: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.3.2.4.7 Enumeration: Accuracy + +The enumeration Accuracy represents a desired granularity of accuracy of the requested location information. It shall comply with the provisions defined in table 5.3.2.4.7-1. + +**Table 5.3.2.4.7-1: Enumeration Accuracy** + +| Enumeration value | Description | Applicability (NOTE) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------| +| CGI_ECGI | The SCS/AS requests to be notified using cell level location accuracy. | | +| ENODEB | The SCS/AS requests to be notified using eNodeB level location accuracy. | | +| TA_RA | The SCS/AS requests to be notified using TA/RA level location accuracy. | | +| PLMN | The SCS/AS requests to be notified using PLMN level location accuracy. | | +| TWAN_ID | The SCS/AS requests to be notified using TWAN identifier level location accuracy. | | +| GEO_AREA | The SCS/AS requests to be notified using the geographical area accuracy. | | +| CIVIC_ADDR | The SCS/AS requests to be notified using the civic address accuracy. | EDGEAPP | +| NOTE 1: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.3.2.4.8 Enumeration: PdnConnectionStatus + +The enumeration PdnConnectionStatus represents the PDN connection status. It shall comply with the provisions defined in table 5.3.2.4.8-1. + +**Table 5.3.2.4.8-1: Enumeration PdnConnectionStatus** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|-------------------------| +| CREATED | The PDN connection is created. | Pdn_connectivity_status | +| RELEASED | The PDN connection is released. | Pdn_connectivity_status | +| NOTE: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.3.2.4.9 Enumeration: PdnType + +The enumeration PdnType represents the PDN connection type. It shall comply with the provisions defined in table 5.3.2.4.9-1. + +**Table 5.3.2.4.9-1: Enumeration PdnType** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------| +| IPv4 | PDN connection of IPv4 type | | +| IPv6 | PDN connection of IPv6 type | | +| IPv4V6 | PDN connection of IPv4v6 type | | +| NON_IP | PDN connection of non-IP type | | +| ETHERNET | PDN connection of Ethernet type | | +| NOTE: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.3.2.4.10 Enumeration: InterfaceIndication + +The enumeration InterfaceIndication represents the network entity used for data delivery towards the SCS/AS. It shall comply with the provisions defined in table 5.3.2.4.10-1. + +**Table 5.3.2.4.10-1: Enumeration InterfaceIndication** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------|----------------------------------------------------------------|-------------------------| +| EXPOSURE_FUNCTION | SCEF is used for the PDN connection towards the SCS/AS. | Pdn_connectivity_status | +| PDN_GATEWAY | PDN gateway is used for the PDN connection towards the SCS/AS. | Pdn_connectivity_status | + +NOTE: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +#### 5.3.2.4.11 Enumeration: LocationFailureCause + +The enumeration **LocationFailureCause** represents the cause of location positioning failure. It shall comply with the provisions defined in table 5.3.2.4.11-1. **Table 5.3.2.4.11-1: Enumeration LocationFailureCause** + +| Enumeration value | Description | Applicability | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| "POSITIONING_DENIED" | Positioning is denied. | | +| "UNSUPPORTED_BY_UE" | Positioning is not supported by UE. | | +| "NOT_REGISTERED_UE" | UE is not registered. | | +| "UNSPECIFIED" | Unspecified. | | +| "REQUESTED_AREA_NOT_ALLOWED" | The location request is rejected because the location area requested by the AF for area event reporting is not allowed (e.g., does not overlap with the allowed location areas for area event reporting). | eLCS_en | + +#### 5.3.2.4.12 Enumeration: SubType + +The enumeration **SubType** represents a subscription type. It shall comply with the provisions defined in table 5.3.2.4.12-1 + +**Table 5.3.2.4.12-1: Enumeration SubType** + +| Enumeration value | Description | Applicability | +|-------------------|---------------------------------|---------------| +| AERIAL_UE | The UE has Aerial subscription. | UAV | + +#### 5.3.2.4.13 Enumeration: SACRepFormat + +**Table 5.3.2.4.13-1: Enumeration SACRepFormat** + +| Enumeration value | Description | Applicability | +|-------------------|---------------------------------------------------------------------------------|---------------| +| "NUMERICAL" | Indicates that the NSAC reporting should be done in numerical format. | | +| "PERCENTAGE" | Indicates that the NSAC reporting should be done in the format of a percentage. | | + +### 5.3.3 Resource structure + +#### 5.3.3.1 General + +All resource URIs of this API should have the following root: + +{apiRoot}/3gpp-monitoring-event/v1 + +"apiRoot" is set as described in clause 5.2.4. "apiName" shall be set to "3gpp-monitoring-event" and "apiVersion" shall be set to "v1" for the current version defined in the present document. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.3.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|------------------------------------------|-------------------------------------------|-------------|--------------------------------------------------------| +| Monitoring Event Subscriptions | /{scsAsId}/subscriptions | GET | Read all or queried subscriptions for a given SCS/AS | +| | | POST | Create a new subscription of monitoring event | +| Individual Monitoring Event Subscription | /{scsAsId}/subscriptions/{subscriptionId} | PUT | Modify an existing subscription of monitoring event | +| | | PATCH | Modifies an existing subscription of monitoring event. | +| | | GET | Read a subscription of monitoring event | +| | | DELETE | Delete a subscription of monitoring event | + +### 5.3.3.2 Resource: Monitoring Event Subscriptions + +#### 5.3.3.2.1 Introduction + +This resource allows an SCS/AS to read all of the active monitoring event subscriptions or create a new monitoring event subscription for the SCS/AS at the SCEF. + +#### 5.3.3.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-monitoring-event/v1/{scsAsId}/subscriptions + +This resource shall support the resource URI variables defined in table 5.3.3.2.2-1. + +**Table 5.3.3.2.2-1: Resource URI variables for resource "Monitoring Event Subscriptions"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +#### 5.3.3.2.3 Resource methods + +##### 5.3.3.2.3.1 GET + +The GET method allows to read all or queried active subscriptions for a given SCS/AS. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.3.3.2.3.1-1 and table 5.3.3.2.3.1-2. + +**Table 5.3.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | Applicability | +|-----------|------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------| +| ip-addrs | array(IpAddr) | 0..N | The IP address(es) of the requested UE(s).
(NOTE) | enNB | +| ip-domain | string | 0..1 | The IPv4 address domain identifier.
The attribute may only be provided if IPv4 address is included in the ip-addrs query parameter. | enNB | +| mac-addrs | array(MacAddr48) | 0..N | The MAC address(es) of the requested UE(s).
(NOTE) | enNB | + +NOTE: Either the "ip-addrs" parameter or the "mac-addrs" parameter may be provided at the same time. If multiple elements are provided in the array data structure, then each element shall be treated as a separate query parameter. + +**Table 5.3.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------------------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(MonitoringEventSubscription) | 0..N | 200 OK | The subscription information for the SCS/AS in the request URI are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.3.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.3.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.3.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.3.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +## 5.3.3.2.3.4 POST + +The POST method creates a new subscription resource to monitor an event for a given SCS/AS. The SCS/AS shall initiate the HTTP POST request message and the SCEF shall respond to the message. The SCEF shall construct the URI of the created resource. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.3.3.2.3.4-1 and table 5.3.3.2.3.4-2. + +**Table 5.3.3.2.3.4-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.3.3.2.3.4-2: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------------------|-------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MonitoringEventSubscription | 1 | | Parameters to register a subscription to notifications about monitoring event with the SCEF. | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | MonitoringEventSubscription | 1 | 201 Created | The subscription resource was created successfully.
The URI of the created resource shall be returned in the "Location" HTTP header. | +| | MonitoringEventReport | 1 | 200 OK | The operation is successful, and corresponding monitoring event report is included.
This is only applicable for the one-time monitoring request if report is available in the response. | +| | MonitoringEventReports | 1 | 200 OK | The operation is successful and the corresponding monitoring event report(s) are included in the response body.

This is only applicable when the enNB feature is supported, the monitoring request is a one-time reporting request and the event reports are available in the response. | +| | ProblemDetails | 0..1 | 400 Bad Request | (NOTE 2) | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | +| | ProblemDetails | 0..1 | 404 Not Found | (NOTE 2) | +| | ProblemDetails | 0..1 | 500 Internal Server Error | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.3.5.3. + +**Table 5.3.3.2.3.4-3: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-monitoring-event/v1/{scsAsId}/subscriptions/{subscriptionId} | + +### 5.3.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +## 5.3.3.3 Resource: Individual Monitoring Event Subscription + +### 5.3.3.3.1 Introduction + +This resource allows an SCS/AS to read, update or delete an active monitoring event subscription at the SCEF. + +### 5.3.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-monitoring-event/v1/{scsAsId}/subscriptions/{subscriptionId} + +This resource shall support the resource URI variables defined in table 5.2.3.2.2-1. + +**Table 5.3.3.3.2-1: Resource URI variables for resource "Individual Monitoring Event Subscription"** + +| Name | Data type | Definition | +|----------------|-----------|-----------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| subscriptionId | string | Identifier of the subscription resource. The subscriptionId corresponds to the stage 2 TLTRI. | + +### 5.3.3.3.3 Resource methods + +#### 5.3.3.3.3.1 GET + +The GET method allows to read an active subscription resource to obtain details of the subscription. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.3.3.3.3.1-1 and table 5.3.3.3.3.1-2. + +**Table 5.3.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.3.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|--------------|-----------|-------------|----------------|---------| +| | Data type | Cardinality | Response codes | Remarks | +| none | | | | | + +| | | | | | +|--|-----------------------------|---|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MonitoringEventSubscription | 1 | 200 OK | The subscription information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.3.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.3.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.3.3.3.3.2 PUT + +The PUT method modifies an existing subscription resource to update the subscription. The SCS/AS shall initiate the HTTP PUT request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.3.3.3.3.2-1 and table 5.3.3.3.3.2-2. + +**Table 5.3.3.3.3.2-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.3.3.3.2-2: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|-----------------------------|--------------------|--------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MonitoringEventSubscription | 1 | Parameters to update a subscription to notifications about monitoring event with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | MonitoringEventSubscription | 1 | 200 OK | The subscription was updated successfully and the representation of the subscription is returned. | +| | none | | 204 No Content | The subscription was updated successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2, NOTE 3) | + +NOTE 1: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. +NOTE 2: The error case is only applicable for monitoring event configuration via PCRF. +NOTE 3: Failure cases are described in clause 5.3.5.3. + +**Table 5.3.3.3.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.3.3.3.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.3.3.3.3 PATCH + +The PATCH method allows the SCS/AS to modify an existing subscription resource, in order to notify the SCEF about the partial cancellation and/or partial addition of certain UE(s) within an active group. The SCS/AS shall initiate the HTTP PATCH message request with JSON Patch format signalled by the content type "application/json-patch+json". + +This method shall support request and response data structures, and response codes, as specified in the table 5.3.3.3.3-1. + +**Table 5.3.3.3.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | array(PatchItem) | 1..N | Contains the list of changes to be made to an individual subscription resource, according to the JSON PATCH format specified in IETF RFC 6902 [67]. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The resource was modified successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.3.3.3.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.3.3.3.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.3.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.3.3.3.3.5 DELETE + +The DELETE method deletes the related resource and terminates the related monitoring subscription. The SCS/AS shall initiate the HTTP DELETE request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.3.3.3.3.5-1 and table 5.3.3.3.3.5-2. + +**Table 5.3.3.3.3.5-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|------------------|--------------------|----------------| +| none specified | | | | + +**Table 5.3.3.3.3.5-2: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | | +|---------------|------------------------------|-------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | | +| Response body | Data type | | Cardinality | Response codes | Remarks | +| | none | | | 204 No Content | The subscription was terminated successfully. | +| | array(MonitoringEventReport) | | 1..N | 200 OK | The subscription was terminated successfully, the monitoring event report(s) shall be included if received. | +| | none | | | 307 Temporary Redirect | Temporary redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | | 308 Permanent Redirect | Permanent redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.3.3.3.3.5-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.3.3.3.3.5-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.3.3.4 Void + +## 5.3.3A Notifications + +### 5.3.3A.1 General + +The notifications provided by the MonitoringEvent API are specified in this clause. + +**Table 5.3.3A-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|--------------------------------------|---------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Monitoring Notification | {notificationDestination} | POST | Sent from the SCEF to the SCS/AS about the notification of grouping configuration result, detected monitoring event report(s) or notify the SCS/AS to cancel a monitoring subscription | +| User Consent Revocation Notification | {revocationNotifUri} | POST | The user consent revocation notification from the NEF to the AF to inform about the revocation of user consent for one or several UE(s). | + +## 5.3.3A.2 Monitoring Notification + +### 5.3.3A.2.1 Description + +The Monitoring Notification allows the SCEF to send notification about grouping configuration result, monitoring event report(s) or a monitoring subscription cancellation to the SCS/AS. + +### 5.3.3A.2.2 Target URI + +The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 5.3.3A.2.2-1. + +**Table 5.3.3A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|-------------------------|-----------|-----------------------------------------------------------------------------------------------------------------| +| notificationDestination | Link | Callback reference provided by the SCS/AS during creation or modification of the monitoring event subscription. | + +### 5.3.3A.2.3 Standard Methods + +#### 5.3.3A.2.3.1 Notification via POST + +The HTTP POST method reports the notification for a monitoring subscription. The SCEF shall initiate the HTTP POST request message and the SCS/AS shall respond to the message. + +This method shall support the request data structures specified in table 5.3.3A.2.3.1-1 and the response data structures and response codes specified in table 5.3.3A.2.3.1-2. + +**Table 5.3.3A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|------------------------|-------------|---------------------------------------------------| +| MonitoringNotification | 1 | The monitoring notification provided by the SCEF. | + +**Table 5.3.3A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| none | | 204 No Content | The monitoring notification is received successfully. | +| none | | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.3.3A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.3.3A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +### 5.3.3A.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the MonitoringNotification may alternatively be delivered through the Websocket mechanism as defined in subclause 5.2.5.4. + +## 5.3.3A.3 User Consent Revocation Notification + +### 5.3.3A.3.1 Description + +The User Consent Revocation Notification is used by the NEF to report the revocation of user consent for one or several UE(s) to the AF. + +### 5.3.3A.3.2 Target URI + +The Callback URI "{revocationNotifUri}" shall be used with the the callback URI variables defined in table 5.3.3A.3.2-1. + +**Table 5.3.3A.3.2-1: Callback URI variables** + +| Name | Data type | Definition | +|--------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| revocationNotifUri | Uri | Callback reference provided by the AF during the creation or update/modification of the subscription as defined in clauses 5.3.3.2.3.4 and 5.3.3.3.3.2 or 5.3.3.3.3.3. | + +### 5.3.3A.3.3 Operation Definition + +#### 5.3.3A.3.3.1 Notification via HTTP POST + +This method shall support the request data structures specified in table 5.3.3A.3.3.1-1 and the response data structures and response codes specified in table 5.3.3A.3.3.1-2. + +**Table 5.3.3A.3.3.1-1: Data structures supported by the POST Request Body on this resource** + +| Data type | Cardinality | Description | +|-------------------|-------------|---------------------------------------------------| +| ConsentRevocNotif | 1 | Contains the user consent revocation information. | + +**Table 5.3.3A.3.3.1-2: Data structures supported by the POST Response Body on this resource** + +| Data type | Cardinality | Response codes | Description | +|-----------|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | 204 No Content | Successful case. The user consent revocation notification is successfully received. | +| n/a | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI representing the end point of an alternative AF where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | +| n/a | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI representing the end point of an alternative AF where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | + +**Table 5.3.3A.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | Cardinality | Description | +|----------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------| +| Location | string | 1 | An alternative URI representing the end point of an alternative AF towards which the notification should be redirected. | + +**Table 5.3.3A.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | Cardinality | Description | +|----------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------| +| Location | string | 1 | An alternative URI representing the end point of an alternative AF towards which the notification should be redirected. | + +#### 5.3.3A.3.3.2 Notification via Websocket + +If supported by both the AF and the NEF and successfully negotiated, the User Consent Revocation Notification may alternatively be delivered via the Websocket mechanism, as defined in clause 5.2.5.4 of 3GPP TS 29.122 [4]. + +### 5.3.4 Used Features + +The table below defines the features applicable to the MonitoringEvent API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.3.4-1: Features used by MonitoringEvent API** + +| Feature Number | Feature | Description | +|----------------|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Loss_of_connectivity_notification | The SCS/AS is notified when the 3GPP network detects that the UE is no longer reachable for signalling or user plane communication | +| 2 | Ue-reachability_notification | The SCS/AS is notified when the UE becomes reachable for sending either SMS or downlink data to the UE | +| 3 | Location_notification | The SCS/AS is notified of the current location or the last known location of the UE | +| 4 | Change_of_IMSI_IMEI_association_notification | The SCS/AS is notified when the association of an ME (IMEI(SV)) that uses a specific subscription (IMSI) is changed | +| 5 | Roaming_status_notification | The SCS/AS is notified when the UE's roaming status changes | +| 6 | Communication_failure_notification | The SCS/AS is notified of communication failure events | +| 7 | Availability_after_DDN_failure_notification | The SCS/AS is notified when the UE has become available after a DDN failure | +| 8 | Number_of_UEs_in_an_area_notification | The SCS/AS is notified the number of UEs present in a given geographic area
The feature supports pre-5G (e.g. 4G) requirement. | +| 9 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 10 | Notification_test_event | The testing of notification connection is supported according to clause 5.2.5.3. | +| 11 | Subscription_modification | Modifications of an individual subscription resource. | +| 12 | Number_of_UEs_in_an_area_notification_5G | The AF is notified the number of UEs present in a given geographic area.
The feature supports the 5G requirement. This feature may only be supported in 5G. | +| 13 | Pdn_connectivity_status | The SCS/AS requests to be notified when the 3GPP network detects that the UE's PDN connection is set up or torn down. | +| 14 | Downlink_data_delivery_status_5G | The AF requests to be notified when the 3GPP network detects that the downlink data delivery status is changed. The feature is not applicable to pre-5G. | +| 15 | Availability_after_DDN_failure_notification_enhancement | The AF is notified when the UE has become available after a DDN failure and the traffic matches the packet filter provided by the AF. The feature is not applicable to pre-5G. | +| 16 | Enhanced_param_config | This feature supports the co-existence of multiple event configurations for target UE(s) if there are parameters affecting periodic RAU/TAU timer and/or Active Time. Supporting this feature also requires the support of feature number 1 or 2. | +| 17 | API_support_capability_notification | The SCS/AS is notified of the availability of support of service APIs. This feature is only applicable in interworking SCEF+NEF scenario. | +| 18 | eLCS | This feature supports the enhanced location exposure service (e.g. location information preciser than cell level).
The feature is not applicable to pre-5G (e.g. 4G). | +| 19 | NSAC | This feature controls the support of the Network Slice Admission Control (NSAC) functionalities.
The feature is not applicable to pre-5G (e.g. 4G). | +| 20 | Partial_group_modification | This feature supports the partial cancellation and/or partial addition to the group member(s) within the grouped event monitoring subscription. | + +| | | | +|----|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 21 | UAV |

The SCS/AS requests to be notified of the UAV presence status in a specific geographic area. This feature is only applicable in interworking SCEF+NEF scenario, or standalone 5G scenario.

This feature requires that
Number_of_UEs_in_an_area_notification and
Number_of_UEs_in_an_area_notification_5G
features are also supported.

| +| 22 | MULTIQOS |

This feature indicates the support for "Multiple QoS Class" which enables to support more than one Location QoS during LCS procedures.

This feature requires that the eLCS feature is also supported.

| +| 23 | Session_Management_Enhancement |

This feature supports Session Management enhancement with requested DNN and/or S-NSSAI. This feature requires that the Pdn_connectivity_status feature or Downlink_data_delivery_status_5G feature is also supported.

| +| 24 | enNB | Indicates the support of enhancements to the northbound interfaces. | +| 25 | EDGEAPP |

This feature controls the support of EDGE applications related functionalities (e.g. support the civic address as a possible location granularity). The feature is not applicable to pre-5G (e.g. 4G).

| +| 26 | UEId_retrieval | This feature supports AF specific UE ID retrieval which is not applicable to pre-5G (e.g. 4G). | +| 27 | UserConsentRevocation | This feature indicates the support of user consent revocation management and enforcement (e.g. stop data processing) for EDGE applications. | +| 28 | Subscription_Patch | This feature indicates the support of the PATCH method for partial modification of an existing event monitoring subscription. | +| 29 | GMEC |

This feature indicates the support of Generic Group Management, Exposure and Communication Enhancements (e.g. Ggroup Member List Change event reporting).

This feature is not applicable to pre-5G (e.g. 4G).

| +| 30 | Loss_of_connectivity_notification_5G |

The AF is notified when the 3GPP network detects that the UE is no longer reachable for signalling or user plane communication.

This feature is not applicable to pre-5G (e.g. 4G).

| +| 31 | enNB1 | Indicates the support of enhancements to this northbound API in Rel-18. | +| 32 | AppDetection_5G |

This feature indicates the support of Application traffic detection (start and stop) monitoring event.

This feature is not applicable to pre-5G (e.g. 4G).

| +| 33 | enNB1_5G |

Indicates the support of enhancements to this northbound API for 5G in Rel-18.

This feature is not applicable to pre-5G (e.g. 4G).

| +| 34 | eLCS_en |

This feature indicates the support of the enhancements to the eLCS feature.

The following functionalities are supported:

  • - Support the error handling related to the area event reporting for the case where the requested location area is not allowed.
  • - Support location reporting over user plane between UE and AF.

This feature is not applicable to pre-5G (e.g. 4G).

| + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 35 | eNSAC |

This feature indicates the support of the enhancements to the NSAC feature.

The following functionalities are supported:

  • - Support the status notification of the current number of UEs with at least one PDU session/PDN connection. This feature is not applicable to pre-5G (e.g. 4G).
| +| 36 | Ranging_SL |

This feature supports the enhanced location exposure service (e.g. location information for ranging and sidelink positioning), and requires the support of eLCS feature.

The feature is not applicable to pre-5G (e.g. 4G).

| +| Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification".
Description: A clear textual description of the feature. | | | + +## 5.3.5 Error handling + +### 5.3.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.3.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the MonitoringEvent API. + +### 5.3.5.3 Application Errors + +The application errors defined for the MonitoringEvent API are listed in table 5.3.5.3-1. + +**Table 5.3.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|----------------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| EVENT_FEATURE_MISMATCH | 400 Bad Request | Indicates the resource creation is not allowed since the supported feature corresponding to the monitoring event is not supported by the client. | | +| DUPLICATE_REQUEST | 400 Bad Request | Indicates that a duplicate subscription already exists for this client. | enNB | +| PARAMETER_OUT_OF_RANGE | 403 Forbidden | Indicates that the resource is not allowed to be created since one or more of the received parameter are out of range defined by operator policies. | | +| IDLE_STATUS_UNSUPPORTED | 403 Forbidden | Indicates that the resource is not allowed to be created since the Idle Status Indication is received in the request but not supported by the network. | | +| OPERATION_PROHIBITED | 403 Forbidden | Indicates the HTTP method is not supported. | | +| CONSENT_REVOCATION_NOT_SUPPORTED | 403 Forbidden | Indicates that the request is rejected because user consent management and enforcement is not supported by the client. | UserConsentRevocation | +| USER_CONSENT_NOT_GRANTED | 403 Forbidden | Indicates that the request is rejected because user consent is not granted. | UserConsentRevocation | +| RESOURCES_EXCEEDED | 403 Forbidden | Indicates that no more subscriptions are allowed for this client. | enNB | +| REQUEST_NOT_AUTHORIZED | 403 Forbidden | Indicates that the AF specific UE ID retrieval request is not authorized or the AF request to application detection is not authorized. | UEId_retrieval, AppDetection_5G | +| REQUESTED_AREA_NOT_ALLOWED | 403 Forbidden | Indicates that the location request is rejected because the location area requested by the AF for an area event reporting is not allowed. | eLCS_en | +| UE_ID_NOT_AVAILABLE | 404 Not Found | Indicates that the AF specific UE ID is not available. | UEId_retrieval | +| UE_NOT_FOUND | 404 Not Found | Indicates that the requested UE address is not found. | UEId_retrieval | +| EVENT_UNSUPPORTED | 500 Internal Server Error | Indicates the required monitoring event is not supported by the | | + +| | | | | +|--|--|---------|--| +| | | server. | | +|--|--|---------|--| + +## 5.4 ResourceManagementOfBdt API + +### 5.4.1 Overview + +The ResourceManagementOfBdt API is a RESTful API that allows the SCS/AS to request background data transfer related conditions for a set of UEs. The ResourceManagementOfBdt API defines a set of data models, resources and the related procedures for the creation and management of the background data transfer request. The corresponding JSON schema for the representation of the resources and operations defined by the ResourceManagementOfBdt API is provided in its complete form in Annex A.4. + +### 5.4.2 Data model + +#### 5.4.2.1 Resource data types + +##### 5.4.2.1.1 Introduction + +This clause defines data structures to be used in resource representations. + +Table 5.4.2.1.1-1 specifies data types re-used by the ResourceManagementOfBdt API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the ResourceManagementOfBdt API. + +**Table 5.4.2.1.1-1: ResourceManagementOfBdt API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|----------------------------------------------------------------------------------------| +| GeographicArea | 3GPP TS 29.572 [42] | Identifies the geographical information of the user(s). | +| CivicAddress | 3GPP TS 29.572 [42] | Identifies the civic address information of the user(s). | +| NetworkAreaInfo | 3GPP TS 29.554 [50] | Identifies a network area information. | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.4.4-1. | + +Table 5.4.2.1.1-2 specifies the data types defined for the ResourceManagementOfBdt API. + +**Table 5.4.2.1.1-2: ResourceManagementOfBdt API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|-------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Bdt | 5.4.2.1.2 | Represents a Background Data Transfer subscription. | | +| BdtPatch | 5.4.2.1.3 | Represents a Background Data Transfer subscription modification request. | | +| ExNotification | 5.4.2.1.4 | Represents a Background Data Transfer notification. | | +| TrafficDescriptor | 5.4.2.3.2 | Identify a traffic descriptor as defined in Figure 5.2.2 of 3GPP TS 24.526 [64]. | | +| TransferPolicy | 5.4.2.2.2 | Represents an offered transfer policy sent from the SCEF to the SCS/AS, or a selected transfer policy sent from the SCS/AS to the SCEF. | | + +##### 5.4.2.1.2 Type: Bdt + +This type represents a BDT subscription. The same structure is used in the subscription request and subscription response. + +**Table 5.4.2.1.2-1: Definition of type Bdt** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------------|-----------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| self | Link | 0..1 | Link to the resource "Individual BDT Subscription". This parameter shall be supplied by the SCEF in HTTP responses. | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7. This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| aspId | string | 0..1 | Identifies an application service provider. | AspId_5G | +| volumePerUE | UsageThreshold | 1 | Identifies the data volume expected to be transferred per UE. | | +| numberOfUEs | integer | 1 | Identifies the number of UEs. | | +| desiredTimeWindow | TimeWindow | 1 | Identifies the time interval. | | +| locationArea | LocationArea | 0..1 | Identifies the area within which the SCS/AS requests the number of UE. | Bdt | +| locationArea5G | LocationArea5G | 0..1 | Identifies the area within which the AF requests the number of UE. | LocBdt_5G | +| referenceId | BdtReferenceId | 0..1 | Identifies a selected policy of background data transfer. | | +| transferPolicies | array(TransferPolicy) | 0..N | Identifies an offered transfer policy. | | +| selectedPolicy | integer | 0..1 | Identity of the selected background data transfer policy. Shall not be present in initial message exchange, can be provided by NF service consumer in a subsequent message exchange. | | +| externalGroupId | ExternalGroupId | 0..1 | Identifies a group of users. (NOTE 2) | Group_Id | +| notificationDestination | Link | 0..1 | Contains the URI to receive the BDT notification from the NEF. | BdtNotification_5G | +| warnNotifEnabled | boolean | 0..1 | Indicates whether the BDT warning notification is enabled or not. If it is set to true, the BDT warning notification is enabled; if it is set to false or absent, the BDT warning notification is disabled. | BdtNotification_5G | +| trafficDes | TrafficDescriptor | 0..1 | Contains the traffic descriptor of the background data. (NOTE 2) | | + +NOTE 1: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. +NOTE 2: The attribute is only applicable to the NEF. + +#### 5.4.2.1.3 Type: BdtPatch + +This type represents a BDT request for the service provided by the SCS/AS to the SCEF via T8 interface. The structure is used for PATCH request. + +**Table 5.4.2.1.3-1: Definition of type BdtPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-------------------------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| selectedPolicy | integer | 1 | Identity of the selected background data transfer policy. | | +| warnNotifEnabled | boolean | 0..1 | Indicates whether the BDT warning notification is enabled.

- true: the BDT warning notification is enabled;
- false: the BDT warning notification is not enabled. | BdtNotification_5G | +| notificationDestination | Link | 0..1 | Contains the URI to receive the BDT notification from the NEF. | enNB | + +NOTE: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +#### 5.4.2.1.4 Type: ExNotification + +This type represents a BDT notification provided by the NEF to the AF. The structure is used for POST request. + +**Table 5.4.2.1.4-1: Definition of type ExNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|----------------|-----------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| bdtReflId | BdtReferenceId | 1 | This IE indicates transfer policies of background data transfer which the notification corresponds to. | | +| locationArea5G | LocationArea5G | 0..1 | This IE represents a network area where a network performance will go below the criteria set by the operator. | | +| timeWindow | TimeWindow | 0..1 | This IE indicates a time window when a network performance will go below the criteria set by the operator. | | +| candPolicies | array(TransferPolicy) | 0..N | This IE indicates a list of the candidate transfer policies from which the AF may select a new transfer policy due to network performance degradation. | | + +NOTE: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +#### 5.4.2.2 Referenced structured data types + +##### 5.4.2.2.1 Introduction + +This clause defines structured data types that are referenced from data structures defined in the previous clauses. + +##### 5.4.2.2.2 Type: TransferPolicy + +This data type represents an offered transfer policy sent from the SCEF to the SCS/AS, or a selected transfer policy sent from the SCS/AS to the SCEF. + +**Table 5.4.2.2.2-1: Definition of type TransferPolicy** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|----------------------|------------|-------------|----------------------------------------------------------------------------------|----------------------| +| bdtpolicyId | integer | 1 | Identifier for the transfer policy | | +| maxUplinkBandwidth | Bandwidth | 0..1 | Indicates the maximum aggregated bitrate in the uplink authorized by the PCRF. | | +| maxDownlinkBandwidth | Bandwidth | 0..1 | Indicates the maximum aggregated bitrate in the downlink authorized by the PCRF. | | +| ratingGroup | integer | 1 | Indicates the rating group during the time window. | | +| timeWindow | TimeWindow | 1 | Indicates the recommended time window of the transfer policy | | + +NOTE: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +## 5.4.2.3 Referenced simple data types and enumerations + +### 5.4.2.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +### 5.4.2.3.2 Simple data types + +The simple data types defined in table 5.4.2.3.2-1 shall be supported. + +**Table 5.4.2.3.2-1: Simple data types** + +| Type name | Description | +|-------------------|-------------------------------------------------------------------------------------------| +| TrafficDescriptor | String identifying a traffic descriptor as defined in table 5.2.1 of 3GPP TS 24.526 [64]. | + +## 5.4.3 Resource structure + +### 5.4.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-bdt/v1** + +"apiRoot" is set as described in clause 5.2.4. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.4.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|-----------------------------|-------------------------------------------|-------------|--------------------------------------------------------------------------------------------------------------------| +| BDT Subscription | /{scsAsId}/subscriptions | GET | Read all active background data transfer subscription resources for a given SCS/AS | +| | | POST | Create a new background data transfer subscription resource | +| Individual BDT Subscription | /{scsAsId}/subscriptions/{subscriptionId} | PATCH | Modify a background data transfer subscription resource to select one of the transfer policies offered by the SCEF | +| | | PUT | Update a background data transfer subscription resource for negotiation of background data transfer policy | +| | | GET | Read a background data transfer subscription resource | +| | | DELETE | Delete a background data transfer resources | + +### 5.4.3.2 Resource: BDT Subscriptions + +#### 5.4.3.2.1 Introduction + +This resource allows the SCS/AS to read all active long-term transactions related to BDT resource management. + +#### 5.4.3.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-bdt/v1/{scsAsId}/subscriptions + +This resource shall support the resource URI variables defined in table 5.4.3.2.2-1. + +**Table 5.4.3.2.2-1: Resource URI variables for resource "BDT Subscriptions"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +#### 5.4.3.2.3 Resource methods + +##### 5.4.3.2.3.1 GET + +The GET method allows to read all active resources for a given SCS/AS. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.4.3.2.3.1-1 and table 5.4.3.2.3.1-2. + +**Table 5.4.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.4.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(Bdt) | 0..N | 200 OK | The resource information for the SCS/AS in the request URI are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.4.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.4.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.4.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.4.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.4.3.2.3.4 POST + +The POST method creates a new background data transfer subscription resource for a given SCS/AS. The SCS/AS shall initiate the HTTP POST request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.4.3.2.3.4-1 and table 5.4.3.2.3.4-2. + +**Table 5.4.3.2.3.4-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.4.3.2.3.4-2: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|------------------|--------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------| +| | Bdt | 1 | | Parameters to register a subscription to request background data transfer related information with the SCEF. | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | Bdt | 1 | 201
Created | The resource was created successfully.
The URI of the created resource shall be returned in the "Location" HTTP header. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.4.3.2.3.4-3: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-bdt/v1/{scsAsId}/subscriptions/{subscriptionId} | + +#### 5.4.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.4.3.3 Resource: Individual BDT Subscription + +#### 5.4.3.3.1 Introduction + +This resource allows the SCS/AS to manage resources for BDT using a long-term transaction. + +#### 5.4.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-bdt/v1/{scsAsId}/subscriptions/{subscriptionId} + +This resource shall support the resource URI variables defined in table 5.4.3.3.2-1. + +**Table 5.4.3.3.2-1: Resource URI variables for resource "Individual BDT Subscription"** + +| Name | Data type | Definition | +|----------------|------------------|-----------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| subscriptionId | string | Identifier of the subscription resource. The subscriptionId corresponds to the stage 2 TLTRI. | + +#### 5.4.3.3.3 Resource methods + +##### 5.4.3.3.3.1 GET + +The GET method allows to read an individual BDT subscription resource to obtain details of an active resource BDT subscription. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.4.3.3.3.1-1 and table 5.4.3.3.3.1-2. + +**Table 5.4.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.4.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | Bdt | 1 | 200 OK | The resource information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.4.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.4.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.4.3.3.3.2 PUT + +The PUT method allows the SCS/AS to modify an existing subscription resource completely. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.4.3.3.3.2-1. + +**Table 5.4.3.3.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Bdt | 1 | The SCS/AS requests to update the BDT policy subscription. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | Bdt | 1 | 200 OK | The subscription was modified successfully.
The SCEF shall return an updated subscription in the response content. | +| | none | | 204 No Content | The subscription was updated successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.4.3.3.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.4.3.3.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.4.3.3.3.3 PATCH + +The PATCH method allows the SCS/AS to modify an existing subscription resource, in order to notify the SCEF about the selected transfer policy. The SCS/AS shall initiate the HTTP PATCH message and the SCEF shall respond to the message. + +This method shall support request and response data structures, and response codes, as specified in the table 5.4.3.3.3.3-1. + +**Table 5.4.3.3.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | BdtPatch | 1 | Background data transfer policy selected by the SCS/AS. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | Bdt | 1 | 200 OK | The resource was modified successfully.
The SCEF shall return an updated subscription in the response content. | +| | none | | 204 No Content | The resource was modified successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.4.3.3.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.4.3.3.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.4.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.4.3.3.3.5 DELETE + +The DELETE method deletes the resource and terminates the BDT subscription. The SCS/AS shall initiate the HTTP DELETE message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.4.3.3.5-1 and table 5.4.3.3.5-2. + +**Table 5.4.3.3.5-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.4.3.3.3.5-2: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The resource was terminated successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.4.3.3.3.5-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.4.3.3.3.5-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.4.3.4 Void + +### 5.4.3A Notifications + +#### 5.4.3A.1 General + +The notifications provided by the ResourceManagementOfBdt API are specified in this clause. + +**Table 5.4.3A-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|--------------------------|---------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------| +| BDT Warning Notification | {notificationDestination} | POST | Notify the BDT warning from the NEF to the AF identified by the notification destination URI (NOTE) | + +NOTE: This notification may only be supported in 5G. + +## 5.4.3A.2 BDT Warning Notification + +### 5.4.3A.2.1 Description + +The BDT warning notification allows the NEF to notify the AF of the BDT warning notification. The notification may only be supported in 5G. + +### 5.4.3A.2.2 Target URI + +The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 5.4.3A.2.2-1. + +**Table 5.4.3A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|-------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notificationDestination | Link | Reference provided by the AF when the AF requests to send a BDT warning notification when the network performance in the area of interest goes below the criteria set by the operator.
This URI shall be provided within the "notificationDestination" attribute in the Bdt data type. | + +### 5.4.3A.2.3 Standard Methods + +#### 5.4.3A.2.3.1 Notification via POST + +The POST method allows to notify AS identified by the notification destination URI of the BDT warning by the NEF and the AF shall respond to the message. + +This method shall support the request data structures specified in table 5.4.3A.2.3.1-1 and the response data structures and response codes specified in table 5.4.3A.2.3.1-2. + +**Table 5.4.3A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|----------------|-------------|-------------------------------------------------| +| ExNotification | 1 | Representation of the BDT warning notification. | + +**Table 5.4.3A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------------------------------------------------------------------------------------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| none | | 204 No Content | This case represents a successful notification of BDT warning notification. | +| none | | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. | | | | + +**Table 5.4.3A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.4.3A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +#### 5.4.3A.2.3.2 Notification via Websocket + +If supported by both AF and NEF and successfully negotiated, the ExNotification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +### 5.4.4 Used Features + +The table below defines the features applicable to the ResourceManagementOfBdt API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.4.4-1: Features used by ResourceManagementOfBdt API** + +| Feature Number | Feature | Description | +|----------------|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Bdt | The feature supports the pre-5G (e.g. 4G) requirement. | +| 2 | LocBdt_5G | The feature supports the 5G requirement. This feature may only be supported in 5G. | +| 3 | Group_Id | The feature supports forwarding an external group identifier of the user. This feature shall not be supported in pre-5G. | +| 4 | BdtNotification_5G | The feature supports the sending of BDT notification. This feature includes sending of the BDT warning notification to the AF. This feature may only be supported in 5G. | +| 5 | enNB | The feature supports enhancement of northbound interfaces, e.g. enable the SCS/AS to update notification destination during modification procedure. | +| 6 | AspId_5G | Indicates the support of application service provider.
This feature is not applicable to pre-5G (e.g. 4G). | + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification". +Description: A clear textual description of the feature. + +### 5.4.5 Error handling + +#### 5.4.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +#### 5.4.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the ResourceManagementOfBdt API. + +#### 5.4.5.3 Application Errors + +The application errors defined for ResourceManagementOfBdt API are listed in table 5.4.5.3-1. + +**Table 5.4.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 5.5 ChargeableParty API + +### 5.5.1 Overview + +The ChargeableParty API is a RESTful API that allows the SCS/AS to either request to sponsor the traffic from the beginning or to request becoming the chargeable party at a later point in time via the T8 interface. The ChargeableParty API defines a set of data models, resources and the related procedures for the creation and management of the AS sessions with chargeable party change. The corresponding JSON schema for the representation of the resources and operations defined by the Chargeable API is provided in its complete form in Annex A.5. + +### 5.5.2 Data model + +#### 5.5.2.1 Resource data types + +##### 5.5.2.1.1 Introduction + +This clause defines data structures to be used in resource representations. + +Table 5.5.2.1.1-1 specifies data types re-used by the ChargeableParty API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the ChargeableParty API. + +**Table 5.5.2.1.1-1: ChargeableParty API re-used Data Types** + +| Data type | Reference | Comments | +|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| Dnn | 3GPP TS 29.571 [45] | Identifies a DNN. | +| EthFlowDescription | 3GPP TS 29.514 [52] | Defines a packet filter for an Ethernet flow.(NOTE) | +| IpAddr | 3GPP TS 29.571 [45] | UE IP Address. | +| MacAddr48 | 3GPP TS 29.571 [45] | MAC Address. | +| ServAuthInfo | 3GPP TS 29.514 [52] | The authorization result of a request bound to a transfer policy. | +| Snssai | 3GPP TS 29.571 [45] | Identifies the S-NSSAI. | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.5.4-1. | +| NOTE: | In order to support a set of MAC addresses with a specific range in the traffic filter, feature MacAddressRange_5G as specified in clause 5.5.4 shall be supported. | | + +Table 5.5.2.1.1-2 specifies the data types defined for the ChargeableParty API. + +**Table 5.5.2.1.1-2: ChargeableParty API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|----------------------|----------------|-------------------------------------------------------------------|---------------| +| ChargeableParty | 5.5.2.1.2 | Represents the configuration of a chargeable party. | | +| ChargeablePartyPatch | 5.5.2.1.3 | Represents a modification request of a chargeable party resource. | | + +##### 5.5.2.1.2 Type: ChargeableParty + +This type represents the configuration of a chargeable party. The same structure is used in the configuration request and configuration response. + +**Table 5.5.2.1.2-1: Definition of type ChargeableParty** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------------|---------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| self | Link | 0..1 | Link to the resource "Individual Chargeable Party Transaction". This parameter shall be supplied by the SCEF in HTTP responses. | | +| dnn | Dnn | 0..1 | Identifies a DNN, a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only. (NOTE 3) | | +| snssai | Snssai | 0..1 | Identifies an S-NSSAI. (NOTE 3) | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7. This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| notificationDestination | Link | 1 | Contains the URI to receive the notification of bearer level event(s) from the SCEF. | | +| requestTestNotification | boolean | 0..1 | Set to true by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. Set to false or omitted otherwise. | Notification_test_event | +| websocketNotifConfig | WebsockNotifConfig | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 5.2.5.4. | Notification_websocket | +| exterAppId | string | 0..1 | Identifies the external Application Identifier. (NOTE 2) | AppId | +| ipv4Addr | Ipv4Addr | 0..1 | Identifies the Ipv4 address. (NOTE 2) | | +| ipDomain | string | 0..1 | The IPv4 address domain identifier. The attribute may only be provided if the ipv4Addr attribute is present. | | +| ipv6Addr | Ipv6Addr | 0..1 | Identifies the Ipv6 address. (NOTE 2) | | +| macAddr | MacAddr48 | 0..1 | Identifies the MAC address. (NOTE 2) | EthChgParty_5G | +| flowInfo | array(FlowInfo) | 0..N | Describes the IP flows. (NOTE 2) (NOTE 4) | | +| ethFlowInfo | array(EthFlowDescription) | 0..N | Identifies Ethernet packet flows. (NOTE 2) | EthChgParty_5G | +| sponsorInformation | SponsorInformation | 1 | Describes the sponsor information such as who is sponsoring the traffic. | | +| sponsoringEnabled | boolean | 1 | Indicates whether the sponsoring data connectivity is enabled.

- true: the sponsoring data connectivity is enabled;
- false: the sponsoring data connectivity is not enabled. | | +| referenceId | BdtReferenceId | 0..1 | The reference ID for a previously selected policy of background data transfer. | | +| servAuthInfo | ServAuthInfo | 0..1 | Indicates the authorization result for the request bound to the transfer policy indicated by the "referenceId" attribute. Supplied by the SCEF | | +| usageThreshold | UsageThreshold | 0..1 | Time period and/or traffic volume. | | +| events | array(Event) | 0..N | Corresponds to the event(s) to which the SCS/AS requests to subscribe. | enNB | + +NOTE 1: Properties marked with a feature as defined in clause 5.5.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +NOTE 2: One of the "ipv4Addr", "ipv6Addr", or "macAddr" attribute shall be provided. If ipv4 or ipv6 address is + +provided, IP flow information shall be provided. If MAC address is provided and the AppId feature is not supported, Ethernet flow information shall be provided. If the AppId feature is supported, one of IP flow information, Ethernet flow information (if EthChgParty\_5G is supported) or External Application Identifier shall be provided. + +NOTE 3: The property is only applicable for the NEF. + +NOTE 4: The "tosTC" attribute of the "flowInfo" attribute may only be present if the "ToSTC\_5G" feature is supported. + +#### 5.5.2.1.3 Type: ChargeablePartyPatch + +This type represents the configuration of a chargeable party. The structure is used for PATCH request. + +**Table 5.5.2.1.3-1: Definition of type ChargeablePartyPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-------------------------|---------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| flowInfo | array(FlowInfo) | 0..N | Describes the IP flows. (NOTE 2)
(NOTE 3) | | +| exterAppId | string | 0..1 | Identifies the AF Application Identifier.
(NOTE 2) | AppId | +| ethFlowInfo | array(EthFlowDescription) | 0..N | Describes Ethernet packet flows.
(NOTE 2) | EthChgParty_5G | +| sponsoringEnabled | boolean | 0..1 | Indicates whether the sponsoring data connectivity is enabled.

- true: the sponsoring data connectivity is enabled;
- false: the sponsoring data connectivity is not enabled. | | +| referenceId | BdtReferenceId | 0..1 | The reference ID for a previously selected policy of background data transfer. | | +| usageThreshold | UsageThresholdRm | 0..1 | Time period and/or traffic volume. | | +| notificationDestination | Link | 0..1 | Contains the URL to receive the notification event(s) from the SCEF. | | +| events | array(Event) | 0..N | Corresponds to the event(s) to which the SCS/AS requests to subscribe to. | enNB | + +NOTE 1: Properties marked with a feature as defined in clause 5.5.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. +NOTE 2: One of "flowInfo", "exterAppId" or "ethFlowInfo" may be provided. +NOTE 3: The "tosTC" attribute of the "flowInfo" attribute may only be present if the "ToSTC\_5G" feature is supported. + +### 5.5.3 Resource structure + +#### 5.5.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-chargeable-party/v1** + +"apiRoot" is set as described in clause 5.2.4. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.5.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|-----------------------------------------|-----------------------------------------|-------------|-------------------------------------------------------------------------------| +| Chargeable Party Transactions | /{scsAsId}/transactions | GET | Read all or queried chargeable party transaction resources for a given SCS/AS | +| | | POST | Create a new chargeable party transaction resource | +| Individual Chargeable Party Transaction | /{scsAsId}/transactions/{transactionId} | GET | Read a chargeable party transaction resource | +| | | PATCH | Partial update a chargeable party transaction resource. | +| | | DELETE | Delete an existing chargeable party transaction resource | + +## 5.5.3.2 Resource: Chargeable Party Transactions + +### 5.5.3.2.1 Introduction + +This resource allows the SCS/AS to read all active long-term transactions related to setting a chargeable party and create individual long-term transactions. + +### 5.5.3.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-chargeable-party/v1/{scsAsId}/transactions + +This resource shall support the resource URI variables defined in table 5.5.3.2.2-1. + +**Table 5.5.3.2.2-1: Resource URI variables for resource "Chargeable Party Transactions"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +### 5.5.3.2.3 Resource methods + +#### 5.5.3.2.3.1 GET + +The GET method allows to read all or queried active chargeable party transactions for a given SCS/AS. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.5.3.2.3.1-1 and table 5.5.3.2.3.1-2. + +**Table 5.5.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | Applicability | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------|---------------| +| ip-addrs | array(lpAddr) | 0..N | The IP address(es) of the requested UE(s). | enNB | +| ip-domain | string | 0..1 | The IPv4 address domain identifier. The attribute may only be provided if IPv4 address is included in the ip-addrs query parameter. | enNB | +| mac-addrs | array(MacAddr48) | 0..N | The MAC address(es) of the requested UE(s). | enNB | +| NOTE: Either the "ip-addrs" parameter or the "mac-addrs" parameter may be provided at the same time. If multiple elements are provided in the array data structure, then each element shall be treated as a separate query parameter. | | | | | + +**Table 5.5.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------------|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(ChargeableParty) | 0..N | 200 OK | The chargeable party transactions information for the SCS/AS in the request URI are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.5.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.5.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.5.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.5.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.5.3.2.3.4 POST + +The POST method creates a new chargeable party transaction resource for a given SCS/AS. The SCS/AS shall initiate the HTTP POST request message and the SCEF shall respond to the message. The SCEF shall construct the URI of the created resource. + +This method shall support request and response data structures, and response codes, as specified in the table 5.5.3.2.3.4-1. + +**Table 5.5.3.2.3.4-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|------------------|--------------------|--------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| | ChargeableParty | 1 | Parameters to create a chargeable party transaction with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | ChargeableParty | 1 | 201
Created | The transaction was created successfully.
The URI of the created resource shall be returned in the "Location" HTTP header. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.5.3.2.3.4-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-chargeable-party/v1/{scsAsId}/transactions/{transactionId} | + +#### 5.5.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.5.3.3 Resource: Individual Chargeable Party Transaction + +#### 5.5.3.3.1 Introduction + +This resource allows the SCS/AS to configure a chargeable party for some application flows using a long-term transaction. + +#### 5.5.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-chargeable-party/v1/{scsAsId}/transactions/{transactionId} + +This resource shall support the resource URI variables defined in table 5.5.3.3.2-1. + +**Table 5.5.3.3.2-1: Resource URI variables for resource "Individual Chargeable Party Transaction"** + +| Name | Data type | Definition | +|---------------|------------------|------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| transactionId | string | Identifier of the transaction. The transactionId corresponds to the stage 2 TLTRI. | + +#### 5.5.3.3.3 Resource methods + +##### 5.5.3.3.3.1 GET + +The GET method allows to read a transaction resource to obtain details of an active. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.5.3.3.3.1-1 and table 5.5.3.3.3.1-2. + +**Table 5.5.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.5.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | ChargeableParty | 1 | 200 OK | The chargeable party transactions information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.5.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.5.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.5.3.3.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.5.3.3.3.3 PATCH + +The PATCH method allows to change the sponsoring status of an active chargeable party transaction. It also allows to activate a background data transfer policy. The SCS/AS shall initiate the HTTP PATCH request message and the SCEF shall respond to the message. This method shall support request and response data structures, and response codes, as specified in the table 5.5.3.3.3.3-1. + +**Table 5.5.3.3.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|----------------------|--------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ChargeablePartyPatch | 1 | Sponsor status change, usage threshold change and/or background data transfer policy activation. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | ChargeableParty | 1 | 200 OK | The chargeable party transaction resource was modified successfully.
The SCEF shall return a representation of the updated chargeable party transaction resource in the response content. | +| | none | | 204 No Content | The chargeable party transaction resource was modified successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.5.3.3.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.5.3.3.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.5.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.5.3.3.3.5 DELETE + +The DELETE method allows to delete an active chargeable party transaction resource and to terminate the related chargeable party transaction. The SCS/AS shall initiate the HTTP DELETE request message and the SCEF shall respond to the message. + +This method shall support request and response data structures, and response codes, as specified in the table 5.5.3.3.3.5-1. + +**Table 5.5.3.3.3.5-1.: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The subscription was deleted successfully. | +| | NotificationData | 1 | 200 OK | The subscription was deleted successfully. The notification data shall be included in the response. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.5.3.3.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.5.3.3.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.5.3.4 Void + +## 5.5.3A Notifications + +### 5.5.3A.1 General + +The notifications provided by the ChargeableParty API are specified in this clause. + +**Table 5.5.3A-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|--------------------|---------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------| +| Event Notification | {notificationDestination} | POST | Notify the bearer level event(s) from the SCEF to the SCS/AS identified by the notification destination URI | + +## 5.5.3A.2 Event Notification + +### 5.5.3A.2.1 Description + +The Event Notification allows the SCEF to notify the SCS/AS of the bearer level event(s). + +### 5.5.3A.2.2 Target URI + +The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 5.5.3A.2.2-1. + +**Table 5.5.3A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|-------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notificationDestination | Link | Reference provided by the SCS/AS when the SCS/AS requests to sponsor the traffic from the beginning or to become the chargeable party at a later point.
This URI shall be provided within the "notificationDestination" attribute in the ChargeableParty type. | + +### 5.5.3A.2.3 Standard Methods + +#### 5.5.3A.2.3.1 Notification via POST + +The POST method allows to notify SCS/AS identified by the notification destination URI of the bearer level event(s) by the SCEF and the SCS/AS shall respond to the message. + +This method shall support the request data structures specified in table 5.5.3A.2.3.1-1 and the response data structures and response codes specified in table 5.5.3A.2.3.1-2. + +**Table 5.5.3A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|------------------|-------------|--------------------------------------------------| +| NotificationData | 1 | Representation of the bearer level notification. | + +**Table 5.5.3A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------------------------------------------------------------------------------------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| none | | 204 No Content | This case represents a successful notification of bearer level event(s). | +| none | | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. | | | | + +**Table 5.5.3A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.5.3A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +### 5.5.3A.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the NotificationData may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +## 5.5.4 Used Features + +The table below defines the features applicable to the ChargeableParty API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.5.4-1: Features used by ChargeableParty API** + +| Feature Number | Feature | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 2 | Notification_test_event | The testing of notification connection is supported according to clause 5.2.5.3. | +| 3 | EthChgParty_5G | Chargeable Party for Ethernet UE. This feature may only be supported in 5G. | +| 4 | MacAddressRange_5G | Indicates the support of a set of MAC addresses with a specific range in the traffic filter. This feature may only be supported in 5G. | +| 5 | AppId | Indicates the support of dynamically providing the Application Identifier via the API. | +| 6 | enNB | Indicates the support of enhancements to the northbound interfaces, e.g. enable an SCS/AS to explicitly indicate the event(s) that it would like to subscribe to. | +| 7 | ToSTC_5G | Indicates the support of Type of Service or Traffic Class. This feature may only be supported in 5G. | +| Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification".
Description: A clear textual description of the feature. | | | + +## 5.5.5 Error handling + +### 5.5.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.5.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the ChargeableParty API. + +### 5.5.5.3 Application Errors + +The application errors defined for ChargeableParty API are listed in table 5.5.5.3-1. + +**Table 5.5.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 5.6 NIDD API + +### 5.6.1 Overview + +The NIDD API is a RESTful API that allows the SCS/AS to send non-IP data to the UE or receive non-IP data from the UE. The NIDD API defines a set of data models, resources and the related procedures for the non-IP data transfer. The corresponding JSON schema for the representation of the resources and operations defined by the NIDD API is provided in its complete form in Annex A.6. + +### 5.6.2 Data model + +#### 5.6.2.1 Resource data types + +##### 5.6.2.1.1 Introduction + +This clause defines data structures to be used in resource representations, including subscription resources. + +Table 5.6.2.1.1-1 specifies data types re-used by the NIDD API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the NIDD API. + +**Table 5.5.2.1.1-1: NIDD API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|----------------------------------------------------------------------------------------| +| NullValue | 3GPP TS 29.571 [45] | JSON's null value, used as an explicit value of an enumeration. | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.6.4-1. | + +Table 5.6.2.1.1-2 specifies the data types defined for the NIDD API. + +**Table 5.6.2.1.1-2: NIDD API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|--------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| DeliveryStatus | 5.6.2.3.4 | Represents the status of a downlink NIDD data delivery. | | +| GmdNiddDownlinkDataDeliveryNotification | 5.6.2.1.8 | Represents the delivery status of a specific group NIDD downlink data delivery. | | +| GmdResult | 5.6.2.2.3 | Represents the group message delivery result. | GroupMessageDelivery | +| ManageEntity | 5.6.2.3.7 | Represents the origin that manages the RDS port. | | +| ManagePort | 5.6.2.1.9 | Represents the configuration of a RDS dynamic port management. | Rds_dynamic_port | +| ManagePortNotification | 5.6.2.1.10 | Represents a ManagePort notification of port numbers that are reserved. | | +| NiddConfiguration | 5.6.2.1.2 | Represents the configuration for NIDD. | | +| NiddConfigurationPatch | 5.6.2.1.7 | Represents the parameters to update a NIDD configuration. | | +| NiddConfigurationStatusNotification | 5.6.2.1.6 | Represents an NIDD configuration status notification. | | +| NiddDownlinkDataDeliveryFailure | 5.6.2.2.4 | Represents information related to a failure delivery result. | | +| NiddDownlinkDataDeliveryStatusNotification | 5.6.2.1.5 | Represents the delivery status of a specific NIDD downlink data delivery. | | +| NiddDownlinkDataTransfer | 5.6.2.1.3 | Represents the received NIDD downlink data from the SCS/AS. | | +| NiddDownlinkDataTransferPatch | 5.6.2.1.11 | Represents the parameters to request the modification of an Individual NIDD Downlink Data Delivery resource. | PatchUpdate | +| NiddStatus | 5.6.2.3.5 | Represents the status of a NIDD configuration. | | +| NiddUplinkDataNotification | 5.6.2.1.4 | Represents NIDD uplink data to be notified to the SCS/AS. | | +| PdnEstablishmentOptions | 5.6.2.3.3 | Represents PDN establishment options that describe the network behaviour when there is no PDN connection towards the addressed UE. | | +| PdnEstablishmentOptionsRm | 5.6.2.3.6 | Represents the same information as the PdnEstablishmentOptions but with the "nullable: true" property. | | +| RdsDownlinkDataDeliveryFailure | 5.6.2.2.5 | Represents the failure delivery result for RDS. | | +| RdsPort | 5.6.2.2.2 | Represents the port configuration for Reliable Data Transfer. | | +| SerializationFormat | 5.6.2.3.8 | Represents a serialization format associated with an RDS port. | Rds_serialization_format | + +#### 5.6.2.1.2 Type: NiddConfiguration + +This type represents the configuration for NIDD. The same structure is used in the configuration request and configuration response. + +**Table 5.6.2.1.2-1: Definition of type NiddConfiguration** + +| Attribute name | Data type | Cardinality | Description | Applicability
(NOTE 1) | +|-------------------------|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| self | Link | 0..1 | Link to the resource "Individual NIDD configuration". This parameter shall be supplied by the SCEF in HTTP responses | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7.
This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| mtcProviderId | string | 0..1 | Identifies the MTC Service Provider and/or MTC Application. (NOTE 3) | | +| externalId | ExternalId | 0..1 | Each element uniquely identifies a user as defined in clause 4.6.2 of 3GPP TS 23.682 [2].
(NOTE 2) | | +| msisdn | Msisdn | 0..1 | Each element identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE 2) | | +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in clause 4.6.3 of 3GPP TS 23.682 [2].
(NOTE 2) | GroupMessageDelivery | +| duration | DateTime | 0..1 | Identifies the absolute time at which the related NIDD Configuration request is considered to expire, as specified in clause 5.13.2 of 3GPP TS 23.682 [2].
When omitted in the request, it indicates the configuration is requested to be valid forever by the SCS/AS. When omitted in the response, it indicates the configuration is set to valid forever by the SCEF. | | +| reliableDataService | boolean | 0..1 | Indicates whether the reliable data service (as defined in clause 4.5.14.3 of 3GPP TS 23.682 [2]) acknowledgement is requested.

- true: reliable data service acknowledgement is requested;
- false (default): reliable data service acknowledgement is not requested. | | +| rdsPorts | array(RdsPort) | 0..N | Indicates the static port configuration that is used for reliable data transfer between specific applications using RDS (as defined in clause 5.2.4 and 5.2.5 of 3GPP TS 24.250 [31]). | | +| pdnEstablishmentOption | PdnEstablishmentOptions | 0..1 | Indicate what the SCEF should do if the UE has not established the PDN connection and MT non-IP data needs to be sent. (wait for the UE to establish the PDN connection, respond with an error cause, or send a device trigger; see step 2 of the MT NIDD Procedure in clause 5.13.3 of 3GPP TS 23.682 [2])
The SCEF will use the value as the default preference from the SCS/AS when handling all MT non-IP packets associated with the NIDD connection. | | +| notificationDestination | Link | 1 | An URI of a notification destination that T8 message shall be delivered to. | | +| requestTestNotification | boolean | 0..1 | Set to true by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. Set to false or omitted otherwise. | Notification_test_event | +| websocketNotifConfig | WebsockNotifConfig | 0..1 | Configuration parameters to set up | Notification_w | + +| | | | | | +|---------------------------|---------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| | g | | notification delivery over Websocket protocol as defined in clause 5.2.5.4. | ebsocket | +| maximumPacketSize | integer | 0..1 | The Maximum Packet Size is the maximum NIDD packet size that was transferred to the UE by the SCEF in the PCO, see clause 4.5.14.1 of 3GPP TS 23.682 [2]. If no maximum packet size was provided to the UE by the SCEF, the SCEF sends a default configured max packet size to SCS/AS.

Unit: bit. | | +| niddDownlinkDataTransfers | array(NiddDownlinkDataTransfer) | 0..N | The downlink data deliveries that needed to be executed by the SCEF. The cardinality of the property shall be 0..1 in the request and 0..N in the response (i.e. response may contain multiple buffered MT NIDD).

For GroupMessageDelivery feature, this property is only applicable for the configuration response to GET request. | | +| status | NiddStatus | 0..1 | May be supplied by the SCEF | | + +NOTE 1: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features unless stated otherwise. + +NOTE 2: One of the properties "externalId", "msisdn" or "externalGroupId" shall be included. + +NOTE 3: The SCEF should check received MTC provider identifier and then the SCEF may: + +- override it with local configured value and send it to HSS; +- send it directly to the HSS; or +- reject the NIDD configuration request. + +#### 5.6.2.1.3 Type: NiddDownlinkDataTransfer + +This type represents received NIDD downlink data from the SCS/AS. + +**Table 5.6.2.1.3-1: Definition of type NiddDownlinkDataTransfer** + +| Attribute name | Data type | Cardinality | Description | Applicability
(NOTE 1) | +|-----------------------------|-------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| externalId | ExternalId | 0..1 | Each element uniquely identifies a user as defined in clause 4.6.2 of 3GPP TS 23.682 [2].
(NOTE 2) | | +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in clause 4.6.3 of 3GPP TS 23.682 [2].
(NOTE 2) | GroupMessageDelivery | +| msisdn | Msisdn | 0..1 | Each element identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE 2) | | +| self | Link | 0..1 | Link to the resource "Individual NIDD downlink data delivery". This parameter shall be supplied by the SCEF in HTTP responses. | | +| data | Bytes | 1 | The non-IP data that needed to be delivered to UE from the SCS/AS. | | +| reliableDataService | boolean | 0..1 | Indicates whether the reliable data service (as defined in clause 4.5.14.3 of 3GPP TS 23.682 [2]) acknowledgement is requested.

- true: reliable data service acknowledgement is requested;
- false (default): reliable data service acknowledgement is not requested. | | +| rdsPort | RdsPort | 0..1 | Indicates the port configuration that is used for reliable data transfer between specific applications using RDS (as defined in clause 5.2.4 and 5.2.5 of 3GPP TS 24.250 [31]). | | +| maximumLatency | DurationSec | 0..1 | It is used to indicate maximum delay acceptable for downlink data and may be used to configure the buffer duration; a Maximum Latency of 0 indicates that buffering is not allowed. If not provided, the SCEF determines the acceptable delay based on local policies. | | +| priority | integer | 0..1 | It is used to indicate the priority of the non-IP data packet relative to other non-IP data packets.
For GroupMessageDelivery feature, this property is not applicable. | | +| pdnEstablishmentOption | PdnEstablishmentOptions | 0..1 | Indicate what the SCEF should do if the UE has not established the PDN connection and MT non-IP data needs to be sent (wait for the UE to establish the PDN connection, respond with an error cause, or send a device trigger; see step 2 of the MT NIDD Procedure in clause 5.13.3 of 3GPP TS 23.682 [2])

If PDN Connection Establishment Option is not provided with the non-IP packet, the SCEF uses the PDN Connection Establishment Option that was provided during NIDD Configuration to decide how to handle the absence of a PDN connection. | | +| deliveryStatus | DeliveryStatus | 0..1 | Indicates the MT NIDD delivery status. | | +| requestedRetransmissionTime | DateTime | 0..1 | Identifies the absolute time at which the SCEF is expected to retransmit the non-IP data when the deliveryStatus indicates that the non-IP data is buffered in the SCEF. This parameter may be supplied by the SCEF for delivery status | | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|---------------------------------------|--| +| | | | "BUFFERING_TEMPORARILY_NOT_REACHABLE" | | +| NOTE 1: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features unless stated otherwise. | | | | | +| NOTE 2: One of the properties "externalId", "msisdn" or "externalGroupId" shall be included. | | | | | + +#### 5.6.2.1.4 Type: NiddUplinkDataNotification + +This type represents NIDD uplink data to be notified to the SCS/AS. + +**Table 5.6.2.1.4-1: Definition of type NiddUplinkDataNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| niddConfiguration | Link | 1 | Link to the NIDD configuration resource to which this notification is related. | | +| externalId | ExternalId | 0..1 | Each element uniquely identifies a user as defined in Clause 4.6.2 of 3GPP TS 23.682 [2].
(NOTE 2) | | +| msisdn | Msisdn | 0..1 | Each element identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE 2) | | +| data | Bytes | 1 | The non IP data that needed to be delivered from the UE to the SCS/AS. | | +| reliableDataService | boolean | 0..1 | Indicates whether the reliable data service acknowledgement is requested.

- true: reliable data service acknowledgement is requested;
- false: reliable data service acknowledgement is not requested. | | +| rdsPort | RdsPort | 0..1 | Indicates the port configuration that is used for reliable data transfer between specific applications using RDS (as defined in clause 5.2.4 and 5.2.5 of 3GPP TS 24.250 [31]). | | +| NOTE 1: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | +| NOTE 2: One of the properties "externalId" or "msisdn" shall be included. | | | | | + +#### 5.6.2.1.5 Type: NiddDownlinkDataDeliveryStatusNotification + +This type represents the delivery status for a specific NIDD downlink data delivery. + +**Table 5.6.2.1.5-1: Definition of type NiddDownlinkDataDeliveryStatusNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| niddDownlinkDataTransfer | Link | 1 | Link to the NIDD downlink data transfer resource to which this notification is related. | | +| deliveryStatus | DeliveryStatus | 1 | Indicates the MT NIDD delivery status. | | +| requestedRetransmissionTime | DateTime | 0..1 | Identifies the absolute time at which the UE will be reachable.
This parameter may be supplied by the SCEF for delivery status
"FAILURE_TEMPORARILY_NOT_REACHABLE" | | +| NOTE: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | | | + +### 5.6.2.1.6 Type: NiddConfigurationStatusNotification + +This type represents an NIDD configuration status notification. + +**Table 5.6.2.1.6-1: Definition of type NiddConfigurationStatusNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------|------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| niddConfiguration | Link | 1 | Link to the NIDD configuration resource to which this notification is related. | | +| externalId | ExternalId | 0..1 | Each element uniquely identifies a user as defined in Clause 4.6.2 of 3GPP TS 23.682 [2].
(NOTE 2) | | +| msisdn | Msisdn | 0..1 | Each element identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE 2) | | +| status | NiddStatus | 1 | Indicates the NIDD configuration status. | | +| rdsCapIndication | boolean | 0..1 | It indicates whether the network capability for the reliable data service is enabled or not. | | +| rdsPort | RdsPort | 0..1 | Indicates the port configuration that is used for reliable data transfer between specific applications using RDS (as defined in clause 5.2.4 and 5.2.5 of 3GPP TS 24.250 [31]). | Rds_port_verification | + +NOTE 1: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. +NOTE 2: One of the properties "externalId" or "msisdn" shall be included. + +### 5.6.2.1.7 Type: NiddConfigurationPatch + +This type represents an NIDD configuration used in PATCH. + +**Table 5.6.2.1.7-1: Definition of type NiddConfigurationPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| duration | DateTimeRm | 0..1 | Identifies the absolute time at which the related NIDD Configuration request is considered to expire, as specified in clause 5.13.2 of 3GPP TS 23.682 [2]. When set to null in the PATCH request, it indicates the configuration is requested to be valid forever by the SCS/AS. When omitted in the response, it indicates the configuration is set to valid forever by the SCEF. | | +| reliableDataService | boolean | 0..1 | Indicates whether the reliable data service (as defined in clause 4.5.14.3 of 3GPP TS 23.682 [2]) acknowledgement is requested.

- true: reliable data service acknowledgement is requested;
- false: reliable data service acknowledgement is not requested. | | +| rdsPorts | array(RdsPort) | 0..N | Indicates the static port configuration that is used for reliable data transfer between specific applications using RDS (as defined in clause 5.2.4 and 5.2.5 of 3GPP TS 24.250 [31]). | | +| pdnEstablishment Option | PdnEstablishment OptionsRm | 0..1 | Indicate what the SCEF should do if the UE has not established the PDN connection and MT non-IP data needs to be sent. (wait for the UE to establish the PDN connection, respond with an error cause, or send a device trigger; see step 2 of the MT NIDD Procedure in clause 5.13.3 of 3GPP TS 23.682 [2])
The SCEF will use the value as the default preference from the SCS/AS when handling all MT non-IP packets associated with the NIDD connection. | | +| notificationDestination | Link | 0..1 | An URI of a notification destination that the message shall be delivered to. | | +| NOTE: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | | | + +#### 5.6.2.1.8 Type: GmdNiddDownlinkDataDeliveryNotification + +This type represents the delivery status for a specific group NIDD downlink data delivery. + +**Table 5.6.2.1.8-1: Definition of type GmdNiddDownlinkDataDeliveryNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------|-----------------------------------------------------------------------------------------|----------------------| +| niddDownlinkDataTransfer | Link | 1 | Link to the NIDD downlink data transfer resource to which this notification is related. | | +| gmdResults | array(GmdResult) | 1..N | Indicates the group message delivery result. | GroupMessageDelivery | +| NOTE: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | | | + +#### 5.6.2.1.9 Type: ManagePort + +This type represents the configuration for RDS dynamic port management which is applicable for Rds\_dynamic\_port feature. + +**Table 5.6.2.1.9-1: Definition of type ManagePort** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|------------------|----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| self | Link | 0..1 | Link to the resource "Individual ManagePort Configuration". This parameter shall be supplied by the SCEF in HTTP PUT/GET responses and in the notification POST request. | | +| applicationId | string | 1 | Indicates the application that is associated with port configuration specified above (as defined in clause 5.4.2.6 of 3GPP TS 24.250 [31]). | | +| manageEntity | ManageEntity | 0..1 | Indicates the "Individual ManagePort Configuration" resource is created by which function entity (UE or the AS). This attribute is supplied by the SCEF. | | +| skipUeInquiry | boolean | 0..1 | Indicate whether to skip UE inquiry. Set to "true" if the SCS/AS decides to reserve port on the SCEF without confirming with the UE; otherwise set to "false". Default value is "false" if omitted. | | +| supportedFormats | array(SerializationFormat) | 0..N | Indicates the serialization format(s) that are supported by the SCS/AS on the associated RDS port.
This attribute is supplied by the SCS/AS. | Rds_serialization_format | +| configuredFormat | SerializationFormat | 0..1 | Indicates the serialization format that has been configured/negotiated for the RDS port.
This attribute is supplied by the SCEF.
(NOTE) | Rds_serialization_format | + +NOTE: The same serialization format is used in the MO and MT directions. + +#### 5.6.2.1.10 Type: ManagePortNotification + +This type represents a ManagePort notification of port numbers that are reserved. + +**Table 5.6.2.1.10-1: Definition of type ManagePortNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|-------------------|-------------------|-------------|-----------------------------------------------------------------------------------------------------|---------------| +| niddConfiguration | Link | 1 | Link to the NIDD configuration resource to which this notification is related. | | +| externalId | ExternalId | 0..1 | Each element uniquely identifies a user as defined in Clause 4.6.2 of 3GPP TS 23.682 [2].
(NOTE) | | +| msisdn | Msisdn | 0..1 | Each element identifies the MS internal PSTN/SDN number allocated for a UE.
(NOTE) | | +| managedPorts | array(ManagePort) | 0..N | Indicates the reserved RDS port configuration information. | | + +NOTE: One of the properties "externalId" or "msisdn" shall be included. + +#### 5.6.2.1.11 Type: NiddDownlinkDataTransferPatch + +This data type represents the parameters to request the modification of an Individual NIDD Downlink Data Delivery resource. + +**Table 5.6.2.1.11-1: Definition of type NiddDownlinkDataTransferPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|------------------------|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| data | Bytes | 1 | The updated non-IP data that needs to be delivered to the UE from the SCS/AS. | | +| reliableDataService | boolean | 0..1 | Indicates whether the reliable data service (as defined in clause 4.5.14.3 of 3GPP TS 23.682 [2]) acknowledgement is requested.

- true: reliable data service acknowledgement is requested;
- false: reliable data service acknowledgement is not requested. | | +| rdsPort | RdsPort | 0..1 | Indicates the port configuration that is used for reliable data transfer between specific applications using RDS (as defined in clause 5.2.4 and 5.2.5 of 3GPP TS 24.250 [31]). | | +| maximumLatency | DurationSec | 0..1 | It is used to indicate the maximum delay acceptable for downlink data delivery. It may be used to configure the buffer duration. A Maximum Latency of 0 indicates that buffering is not allowed.
If not provided, the SCEF determines the acceptable delay based on local policies. | | +| priority | integer | 0..1 | It is used to indicate the priority of these non-IP data packets relative to other non-IP data packets. | | +| pdnEstablishmentOption | PdnEstablishmentOptions | 0..1 | Indicates what the SCEF should do if the UE has not established the PDN connection and MT non-IP data needs to be sent (wait for the UE to establish the PDN connection, respond with an error cause, or send a device trigger; see step 2 of the MT NIDD Procedure in clause 5.13.3 of 3GPP TS 23.682 [2])

If PDN Connection Establishment Option is not provided with the non-IP packets, the SCEF uses the PDN Connection Establishment Option that was provided during NIDD Configuration to decide how to handle the absence of a PDN connection. | | + +NOTE 1: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features unless stated otherwise. + +## 5.6.2.2 Referenced structured data types + +### 5.6.2.2.1 Introduction + +This clause defines structured data types that are referenced from data structures defined in the previous clauses. + +### 5.6.2.2.2 Type: RdsPort + +This type represents the port configuration for Reliable Data Transfer. It shall comply with the provisions defined in table 5.6.2.2.2-1. + +**Table 5.6.2.2.2-1: Definition of RdsPort data Type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|-----------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| portUE | Port | 1 | Indicates the port number on UE that is used for reliable data transfer with a specific application on UE using RDS (as defined in clause 5.2.4 and 5.2.5 of 3GPP TS 24.250 [31]). | +| portSCEF | Port | 1 | Indicates the port number on SCEF that is used for reliable data transfer with a specific application on SCEF using RDS (as defined in clause 5.2.4 and 5.2.5 of 3GPP TS 24.250 [31]). | + +#### 5.6.2.2.3 Type: GmdResult + +This type represents the group message delivery result. It shall comply with the provisions defined in table 5.6.2.2.3-1. + +**Table 5.6.2.2.3-1: Definition of GmdResult data Type** + +| Attribute name | Data type | Cardinality | Description | +|-------------------------------------------------------------------------|----------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| externalId | ExternalId | 0..1 | Each element uniquely identifies a user as defined in subclause 4.6.2 of 3GPP TS 23.682 [2].
(NOTE) | +| msisdn | Msisdn | 0..1 | Each element identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE) | +| deliveryStatus | DeliveryStatus | 1 | Indicates the MT NIDD delivery status. | +| requestedRetransmissionTime | DateTime | 0..1 | Identifies the absolute time at which the UE will be reachable. This parameter may be supplied by the SCEF for delivery status "FAILURE_TEMPORARILY_NOT_REACHABLE" | +| NOTE: One of the properties "externalId" or "msisdn" shall be included. | | | | + +#### 5.6.2.2.4 Type: NiddDownlinkDataDeliveryFailure + +This type represents the failure delivery result. It shall comply with the provisions defined in table 5.6.2.2.4-1. + +**Table 5.6.2.2.4-1: Definition of NiddDownlinkDataDeliveryFailure data Type** + +| Attribute name | Data type | Cardinality | Description | +|-----------------------------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| problemDetail | ProblemDetails | 1 | Detailed problem as defined in clause 5.2.1.2.12. | +| requestedRetransmissionTime | DateTime | 0..1 | Identifies the absolute time at which the UE will be reachable. This parameter may be supplied by the SCEF for error indicating "TEMPORARILY_NOT_REACHABLE" | + +#### 5.6.2.2.5 Type: RdsDownlinkDataDeliveryFailure + +This type represents the failure delivery result for RDS. It shall comply with the provisions defined in table 5.6.2.2.5-1. + +**Table 5.6.2.2.5-1: Definition of RdsDownlinkDataDeliveryFailure data Type** + +| Attribute name | Data type | Cardinality | Description | +|------------------------------------------------------------------------------------------------------------------|----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| requestedRetransmissionTime | DateTime | 0..1 | Identifies the absolute time at which the UE will be reachable. This parameter may be supplied by the SCEF for error indicating "TEMPORARILY_NOT_REACHABLE" | +| supportedUeFormats | array(SerializationFormat) | 0..N | Indicates the serialization format(s) that are supported by the UE on the associated RDS port. This parameter may be supplied by the SCEF for error indicating "SERIALIZATION_FORMAT_NOT_SUPPORTED" | +| NOTE: This data type also contains all the properties defined for ProblemDetails data type in clause 5.2.1.2.12. | | | | + +### 5.6.2.3 Referenced simple data types and enumerations + +#### 5.6.2.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +#### 5.6.2.3.2 Simple data types + +The simple data types defined in table 5.6.2.3.2-1 shall be supported. + +**Table 5.6.2.3.2-1: Simple data types** + +| Type name | Description | +|-----------|-------------| +| | | + +#### 5.6.2.3.3 Enumeration: PdnEstablishmentOptions + +The enumeration PdnEstablishmentOptions represents PDN establishment options that describe the network behaviour when there is no PDN connection towards the addressed UE. + +**Table 5.6.2.3.3-1: Enumeration PdnEstablishmentOptions** + +| Enumeration value | Description | Applicability (NOTE) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------| +| WAIT_FOR_UE | wait for the UE to establish the PDN connection | | +| INDICATE_ERROR | respond with an error cause | | +| SEND_TRIGGER | send a device trigger | | +| NOTE: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | + +#### 5.6.2.3.4 Enumeration: DeliveryStatus + +The enumeration DeliveryStatus represents the status of a downlink NIDD data delivery resource. + +**Table 5.6.2.3.4-1: Enumeration DeliveryStatus** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|----------------------| +| SUCCESS | Success but details not provided | | +| SUCCESS_NEXT_HOP_ACKNOWLEDGED | Successful delivery to the next hop with acknowledgment. | | +| SUCCESS_NEXT_HOP_UNACKNOWLEDGED | Successful delivery to the next hop without acknowledgment | | +| SUCCESS_ACKNOWLEDGED | Reliable delivery was acknowledged by the UE | | +| SUCCESS_UNACKNOWLEDGED | Reliable delivery was not acknowledged by the UE | | +| TRIGGERED | The SCEF triggered the device and is buffering the data. | | +| BUFFERING | The SCEF is buffering the data due to no PDN connection established. | | +| BUFFERING_TEMPORARILY_NOT_REACHABLE | The SCEF has been informed that the UE is temporarily not reachable but is buffering the data | | +| SENDING | The SCEF has forwarded the data, but they may be stored elsewhere. | | +| FAILURE | Delivery failure but details not provided | | +| FAILURE_RDS_DISABLED | RDS was disabled. | | +| FAILURE_NEXT_HOP | Unsuccessful delivery to the next hop. | | +| FAILURE_TIMEOUT | Unsuccessful delivery due to timeout. | | +| FAILURE_TEMPORARILY_NOT_REACHABLE | The SCEF has been informed that the UE is temporarily not reachable without buffering the data. | | +| NOTE: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +### 5.6.2.3.5 Enumeration: NiddStatus + +The enumeration NiddStatus represents the status of a NIDD configuration. + +**Table 5.6.2.3.5-1: Enumeration NiddStatus** + +| Enumeration value | Description | Applicability (NOTE) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------| +| ACTIVE | The NIDD configuration is active. | | +| TERMINATED_UE_NOT_AUTHORIZED | The NIDD configuration was terminated because the UE's authorisation was revoked. | | +| TERMINATED | The NIDD configuration was terminated. | | +| RDS_PORT_UNKNOWN | The RDS port is unknown. | Rds_port_verification | +| NOTE: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | + +### 5.6.2.3.6 Enumeration: PdnEstablishmentOptionsRm + +The enumeration PdnEstablishmentOptionsRm represents PDN establishment options that describe the network behaviour when there is no PDN connection towards the addressed UE. It is defined in clause 5.6.2.3.3 but also allows null value (specified as "NullValue" data type) so it can be removed in "JSON Merge Patch", as defined in IETF RFC 7396 [39]. + +**Table 5.6.2.3.6-1: Enumeration PdnEstablishmentOptionsRm** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------| +| WAIT_FOR_UE | wait for the UE to establish the PDN connection | | +| INDICATE_ERROR | respond with an error cause | | +| SEND_TRIGGER | send a device trigger | | +| NOTE: Properties marked with a feature as defined in clause 5.6.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +### 5.6.2.3.7 Enumeration: ManageEntity + +The enumeration ManageEntity represents the origin that manages the RDS port. + +**Table 5.6.2.3.7-1: Enumeration ManageEntity** + +| Enumeration value | Description | Applicability | +|-------------------|-------------------------------------|---------------| +| UE | Representing the UE. | | +| AS | Representing the Application Server | | + +### 5.6.2.3.8 Enumeration: SerializationFormat + +The enumeration SerializationFormat represents a serialization format associated with an RDS port which is applicable for the Rds\_serialization\_format feature. + +**Table 5.6.2.3.8-1: Enumeration SerializationFormat** + +| Enumeration value | Description | Applicability
(NOTE) | +|-------------------|------------------------------|-------------------------| +| CBOR | The CBOR Serialzition format | | +| JSON | The JSON Serialzition format | | +| XML | The XML Serialzition format | | + +## 5.6.3 Resource structure + +### 5.6.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-nidd/v1** + +"apiRoot" is set as described in clause 5.2.4. "apiName" shall be set to "3gpp-nidd" and "apiVersion" shall be set to "v1" for the version defined in the present document. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.6.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | HTTP initiator | Meaning | +|----------------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------|-------------------------------------------------------------------------------------------------------------| +| NIDD configurations | /{scsAsId}/configurations | GET | SCS/AS | Read all NIDD configuration resources for a given SCS/AS. | +| | | POST | SCS/AS | Create a new NIDD configuration resource. | +| Individual NIDD configuration | /{scsAsId}/configurations/{configurationId} | PATCH | SCS/AS | Modify an existing NIDD configuration resource. | +| | | GET | SCS/AS | Read an NIDD configuration resource. | +| | | DELETE | SCS/AS | Delete an existing NIDD configuration resource. | +| NIDD downlink data deliveries | /{scsAsId}/configurations/{configurationId}/downlink-data-deliveries | GET | SCS/AS | Read all pending NIDD downlink data delivery resources related to a particular NIDD configuration resource. | +| | | POST | SCS/AS | Create an NIDD downlink data delivery resource related to a particular NIDD configuration resource. | +| Individual NIDD downlink data delivery | /{scsAsId}/configurations/{configurationId}/downlink-data-deliveries/{downlinkDataDeliveryId} | PUT | SCS/AS | Replace an Individual NIDD downlink data delivery resource. | +| | | PATCH | SCS/AS | Modify an Individual NIDD downlink data delivery resource. | +| | | DELETE | SCS/AS | Delete an NIDD downlink data delivery resource. | +| | | GET | SCS/AS | Read pending NIDD downlink data delivery resource. | +| ManagePort Configurations | /{scsAsId}/configurations/{configurationId}/rds-ports | GET | SCS/AS | Read all RDS ManagePort Configurations. | +| Individual ManagePort Configuration | /{scsAsId}/configurations/{configurationId}/rds-ports/{portId} | PUT | SCS/AS | Create a new Individual ManagePort Configuration resource to reserve port numbers. | +| | | DELETE | SCS/AS | Delete an Individual ManagePort Configuration resource to release port numbers. | +| | | GET | SCS/AS | Read an Individual ManagePort Configuration resource to query port numbers. | + +## 5.6.3.2 Resource: NIDD Configurations + +### 5.6.3.2.1 Introduction + +This resource allows the SCS/AS to create an NIDD configuration at the SCEF, and read all NIDD configurations in the SCEF. + +### 5.6.3.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations + +This resource shall support the resource URI variables defined in table 5.6.3.2.2-1. + +**Table 5.6.3.2.2-1: Resource URI variables for resource "NIDD Configurations"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +### 5.6.3.2.3 Resource methods + +#### 5.6.3.2.3.1 GET + +The GET method allows to read all active NIDD configurations for a given SCS/AS. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.6.3.2.3.1-1 and table 5.6.3.2.3.1-2. + +**Table 5.6.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.6.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|--------------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | Response codes | Remarks | +| Response body | array(NiddConfiguration) | 0..N | 200 OK | The configuration information for the SCS/AS in the request URI are returned. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.6.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.6.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.6.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.6.3.2.3.4 POST + +To create a NIDD configuration, the SCS/AS shall use the HTTP POST method on the "configurations" collection resource as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.6.2.1.2-1. + +The possible response messages from the SCEF, depending on whether the POST request is successful or unsuccessful, are shown in table 5.6.3.2.3.4-1. + +**Table 5.6.3.2.3.4-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-------------------|-------------|------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NiddConfiguration | 1 | Parameters to create and authorize a NIDD configuration with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NiddConfiguration | 1 | 201
Created |

The NIDD configuration was created successfully.

The SCEF shall return a data structure of type "NiddConfiguration" in the response content.

The URI of the created resource shall be returned in the "Location" HTTP header.

| + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.6.3.2.3.4-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId} | + +#### 5.6.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.6.3.3 Resource: Individual NIDD Configuration + +#### 5.6.3.3.1 Introduction + +This resource allows the SCS/AS to query/update/cancel the specific NIDD configuration at the SCEF. + +### 5.6.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId} + +This resource shall support the resource URI variables defined in table 5.6.3.3.2-1. + +**Table 5.6.3.3.2-1: Resource URI variables for resource "Individual NIDD Configuration"** + +| Name | Data type | Definition | +|-----------------|-----------|----------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| configurationId | string | Identifier of the configuration. The configurationId corresponds to the stage 2 TLTRI. | + +### 5.6.3.3.3 Resource methods + +#### 5.6.3.3.3.1 GET + +The GET method allows to read a NIDD configuration resource to obtain details of an active configuration. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.6.3.3.3.1-1 and table 5.6.3.3.3.1-2. + +**Table 5.6.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.6.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | None | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NiddConfiguration | 1 | 200 OK | The configuration information related to the request URI is returned. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.6.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.6.3.3.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.6.3.3.3.3 PATCH + +Assuming that a NIDD configuration has been created using the HTTP POST method described in clause 5.6.3.2.3.4, partial updating of its properties can be performed by the SCS/AS by using the HTTP PATCH method on the "configuration" instance resource as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.6.2.1.2-1 + +The possible response messages from the SCEF, depending on whether the PATCH request is successful or unsuccessful, are shown in table 5.6.3.3.3.3-1. + +**Table 5.6.3.3.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------------|-------------|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NiddConfigurationPatch | 1 | Parameters to update a NIDD configuration with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NiddConfiguration | 1 | 200 OK | The NIDD configuration was modified successfully.
The SCEF shall return an updated data structure of type "NiddConfiguration" in the response content. | +| | None | | 204 No Content | The NIDD configuration has been modified successfully and no content is to be sent in the response message body. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.6.3.3.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.3.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.6.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.6.3.3.3.5 DELETE + +To cancel a NIDD configuration, the SCS/AS shall use the HTTP DELETE method on the individual "NIDD configuration" resource which is indicated by the URI in the Location header of the HTTP POST response: + +The possible response messages from the SCEF, depending on whether the DELETE request is successful or unsuccessful, are shown in Table 5.6.3.3.3.5-1. + +**Table 5.6.3.3.3.5-1.: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-------------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | . | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NiddConfiguration | 1 | 200 OK | The NIDD configuration was cancelled successfully.
The SCEF shall return a full representation of the deleted resource including a data structure of type "NiddConfiguration" with a "TERMINATE" status in the response body. | +| | None | | 204 No Content | The NIDD configuration was cancelled successfully.
The response body shall be empty. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.6.3.3.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.3.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.6.3.4 Resource: NIDD downlink data deliveries + +#### 5.6.3.4.1 Introduction + +This resource allows the SCS/AS to read all pending NIDD downlink data delivery resources for a particular NIDD configuration resource. + +This resource also allows the SCS/AS to create an NIDD downlink data delivery. + +This resource is applicable for a single UE and a group of UEs NIDD MT delivery. + +#### 5.6.3.4.2 Resource definition + +Resource URI: {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId}/downlink-data-deliveries + +This resource shall support the resource URI variables defined in table 5.6.3.4.2-1. + +**Table 5.6.3.4.2-1: Resource URI variables for resource "NIDD Downlink Data Deliveries"** + +| Name | Data type | Definition | +|-----------------|-----------|----------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| configurationId | string | Identifier of the configuration. | + +#### 5.6.3.4.3 Resource methods + +##### 5.6.3.4.3.1 GET + +The GET method allows to read all pending NIDD downlink data deliveries for a given SCS/AS and NIDD configuration. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.6.3.4.3.1-1 and table 5.6.3.4.3.1-2. + +**Table 5.6.3.4.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.6.3.4.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|----------------------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | None | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(NiddDownlinkData Transfer) | 0..N | 200 OK | All pending NIDD downlink data deliveries for the SCS/AS and NIDD configuration in the request URI are returned. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.6.3.4.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.4.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**5.6.3.4.3.2 PUT** + +This HTTP method is not supported for the resource. + +**5.6.3.4.3.3 PATCH** + +This HTTP method is not supported for the resource. + +**5.6.3.4.3.4 POST** + +To deliver the downlink non-IP data, the SCS/AS shall use the HTTP POST method on the "NIDD downlink data deliveries" resource with the body of the message is encoded in JSON format with the data structure defined in table 5.6.2.1.3-1. + +The possible response messages from the SCEF, depending on whether the POST request is successful or unsuccessful, are shown in Table 5.6.3.4.3.4-1. + +**Table 5.6.3.4.3.4-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|---------------------------------|--------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NiddDownlinkDataTransfer | 1 | The parameters and non-IP data for the MT delivery. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NiddDownlinkDataTransfer | 1 | 200 OK | The NIDD downlink data delivery was successful.

The SCEF shall return a data structure of type "NiddDownlinkDataTransfer" in the response content. | +| | NiddDownlinkDataTransfer | 1 | 201 Created | The NIDD downlink data delivery request was accepted by the SCEF, the NIDD will be performed later.

The SCEF shall return a data structure of type "NiddDownlinkDataTransfer" in the response content, and shall return the URI of the resource representing the downlink data transfer in the "Location" header. | +| | None | | 307 Temporary Redirect | Temporary redirection, during NIDD downlink data delivery. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during NIDD downlink data delivery. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | NiddDownlinkDataDeliveryFailure | 0..1 | 500 Internal Server Error | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.6.5.3. + +**Table 5.6.3.4.3.4-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.4.3.4-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.4.3.4-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId}/downlink-data-deliveries/{downlinkDataDeliveryId} | + +#### 5.6.3.4.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.6.3.5 Resource: Individual NIDD downlink data delivery + +#### 5.6.3.5.1 Introduction + +For NIDD MT delivery for a single UE, this resource allows the SCS/AS to read a pending NIDD downlink delivery resource, or to replace or cancel an NIDD downlink data delivery resource related to an NIDD configuration resource. + +For NIDD MT delivery for a group of UEs, this resource allows the SCS/AS to read a pending NIDD downlink delivery resource related to a NIDD configuration resource. + +#### 5.6.3.5.2 Resource definition + +Resource URI: {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId}/downlink-data-deliveries/{downlinkDataDeliveryId} + +This resource shall support the resource URI variables defined in table 5.6.3.5.2-1. + +**Table 5.6.3.4.2-1: Resource URI variables for resource "Individual NIDD Downlink Data Delivery"** + +| Name | Data type | Definition | +|------------------------|-----------|-------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| configurationId | string | Identifier of the configuration. | +| downlinkDataDeliveryId | string | Identifier of the downlink data delivery. | + +#### 5.6.3.5.3 Resource methods + +##### 5.6.3.5.3.1 GET + +The GET method allows to read a NIDD downlink data delivery resource to obtain details. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.6.3.5.3.1-1 and table 5.6.3.5.3.1-2. + +**Table 5.6.3.5.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.6.3.5.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|--------------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NiddDownlinkDataTransfer | 1 | 200 OK | Individual NIDD downlink data delivery resource is returned. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.6.3.5.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.5.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.6.3.5.3.2 PUT + +To replace the buffered downlink non-IP data, the SCS/AS shall use the HTTP PUT method on the "Individual NIDD downlink data delivery" resource with the body of the message encoded in JSON format with the data structure defined in table 5.6.2.1.3-1. + +The possible response messages from the SCEF, depending on whether the PUT request is successful or unsuccessful, are shown in Table 5.6.3.5.3.2-1. + +**Table 5.6.3.5.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|---------------------------------|--------------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NiddDownlinkDataTransfer | 1 | The parameters and non-IP data for the MT delivery. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NiddDownlinkDataTransfer | 1 | 200 OK | The update of the Individual NIDD downlink data delivery resource was successful.

The SCEF shall return an updated representation of the resource within the NiddDownlinkDataTransfer data structure in the response message body. | +| | None | | 204 No Content | The update of the Individual NIDD downlink data delivery was successful and no content is to be sent in the response message body. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | +| | ProblemDetails | 0..1 | 404 Not Found | (NOTE 2) | +| | ProblemDetails | 0..1 | 409 Conflict | (NOTE 2) | +| | NiddDownlinkDataDeliveryFailure | 0..1 | 500 Internal Server Error | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.6.5.3. + +**Table 5.6.3.5.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.5.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.6.3.5.3.3 PATCH + +If the "PatchUpdate" feature defined in clause 5.7.4 is supported, to partially modify the buffered downlink non-IP data, the SCS/AS shall use the HTTP PATCH method on the "Individual NIDD downlink data delivery" resource with the body of the message encoded in JSON format with the data structure defined in table 5.6.2.1.11-1. + +The possible response messages from the SCEF, depending on whether the HTTP PATCH request is successful or unsuccessful, are shown in Table 5.6.3.5.3.3-1. + +**Table 5.6.3.5.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|---------------------------------|-------------|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NiddDownlinkDataTransferPatch | 1 | The parameters to modify an existing Individual NIDD downlink data delivery resource. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NiddDownlinkDataTransfer | 1 | 200 OK | The modification of the Individual NIDD downlink data delivery resource was successful.

The SCEF shall return an updated representation of the resource within the NiddDownlinkDataTransfer data structure in the response message body. | +| | n/a | | 204 No Content | The modification of the Individual NIDD downlink data delivery resource was successful and no content is to be sent in the response message body. | +| | n/a | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | n/a | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | +| | ProblemDetails | 0..1 | 404 Not Found | (NOTE 2) | +| | ProblemDetails | 0..1 | 409 Conflict | (NOTE 2) | +| | NiddDownlinkDataDeliveryFailure | 0..1 | 500 Internal Server Error | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the HTTP PATCH method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.6.5.3. + +**Table 5.6.3.5.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | String | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.5.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.6.3.5.3.4 POST + +This HTTP method is not supported for the resource. + +## 5.6.3.5.3.5 DELETE + +To cancel a NIDD downlink data delivery, the SCS/AS shall use the HTTP DELETE method on the "Individual NIDD downlink data delivery" resource which is indicated by the URI in the Location header of the HTTP POST response: + +The possible response messages from the SCEF, depending on whether the DELETE request is successful or unsuccessful, are shown in table 5.6.3.3.5-1. + +**Table 5.6.3.5.3.5-1.: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|---------------------------------|-------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | . | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The NIDD downlink data delivery was cancelled successfully.
The response body shall be empty. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | +| | ProblemDetails | 0..1 | 404 Not Found | (NOTE 2) | +| | ProblemDetails | 0..1 | 409 Conflict | (NOTE 2) | +| | NiddDownlinkDataDeliveryFailure | 0..1 | 500 Internal Server Error | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.6.5.3. + +**Table 5.6.3.5.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.5.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +5.6.3.6 Void + +5.6.3.7 Void + +5.6.3.8 Void + +5.6.3.9 Resource: Individual ManagePort Configuration + +5.6.3.9.1 Introduction + +This resource allows the SCS/AS to create, delete or read the specific ManagePort configuration at the SCEF. + +5.6.3.9.2 Resource definition + +Resource URI: {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId}/rds-ports/{portId} + +This resource shall support the resource URI variables defined in table 5.6.3.9.2-1. + +**Table 5.6.3.9.2-1: Resource URI variables for resource "Individual ManagePort Configuration"** + +| Name | Data type | Definition | +|-----------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| configurationId | string | Identifier of the configuration. The configurationId corresponds to the stage 2 TLTRI. | +| portId | string | UE port identifier including both UE port number and exposure function port number.
Pattern: "^(ue([0-9]{1,0-5}))-ef([0-9]{1,0-5}))\$". | + +5.6.3.9.3 Resource methods + +5.6.3.9.3.1 GET + +The GET method allows to read a ManagePort configuration resource to query the ports reserved. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.6.3.9.3.1-1 and table 5.6.3.9.3.1-2. + +**Table 5.6.3.9.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.6.3.9.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | None | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | ManagePort | 1 | 200 OK | The configuration information related to the request URI is returned. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.6.3.9.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.9.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.6.3.9.3.2 PUT + +To create a ManagePort configuration and reserve a port number, the SCS/AS shall use the HTTP PUT method on the "ManagePort" resource with the body of the message is encoded in JSON format with the data structure defined in table 5.6.3.9.3.2-1. + +The possible response messages from the SCEF, depending on whether the PUT request is successful or unsuccessful, are shown in Table 5.6.3.9.3.2-1. + +**Table 5.6.3.9.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|--------------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| | ManagePort | 1 | The ManagePort configuration to be created which represents the information used for reserving the port configuration for an application. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | ManagePort | 1 | 201
Created | This indicates the reservation of port configuration for specified application is successful. | +| | None | | 202
Accepted | This indicates the request for reservation of port configuration for specified application is accepted and under processing. | +| | ProblemDetails | 0..1 | 403
Forbidden | (NOTE 2) | +| | RdsDownlinkDataDeliveryFailure | 0..1 | 500
Internal Server Error | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +NOTE 2: Failure cases are described in clause 5.6.5.3. + +**5.6.3.9.3.3 PATCH** + +This HTTP method is not supported for the resource. + +**5.6.3.9.3.4 POST** + +This HTTP method is not supported for the resource. + +**5.6.3.9.3.5 DELETE** + +To cancel a ManagePort configuration and release port numbers, the SCS/AS shall use the HTTP DELETE method on the ManagePort resource which is indicated by the URI in the Location header of the HTTP POST response: + +The possible response messages from the SCEF, depending on whether the DELETE request is successful or unsuccessful, are shown in Table 5.6.3.9.3.5-1. + +**Table 5.6.3.9.3.5-1.: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|--------------------------------|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ManagePort | 1 | The ManagePort configuration to be cancelled which represents the information used for releasing the port configuration for an application | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | None | | 204 No Content | The ManagePort configuration was cancelled successfully and the port configuration was released. | +| | None | | 202 Accepted | This indicates the request for cancellation of port configuration for specified application is accepted and under processing. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | ProblemDetails | 0..1 | 404 Not Found | (NOTE 2) | +| | RdsDownlinkDataDeliveryFailure | 0..1 | 500 Internal Server Error | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.6.5.3. + +**Table 5.6.3.9.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.9.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +5.6.3.10 Void + +5.6.3.11 Resource: ManagePort Configurations + +5.6.3.11.1 Introduction + +This resource allows the SCS/AS to read all ManagePort configurations for a given NIDD configuration at the SCEF. + +### 5.6.3.11.2 Resource definition + +Resource URI: {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId}/rds-ports + +This resource shall support the resource URI variables defined in table 5.6.3.11.2-1. + +**Table 5.6.3.11.2-1: Resource URI variables for resource "ManagePort Configurations"** + +| Name | Data type | Definition | +|-----------------|-----------|-------------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| configurationId | string | Identifier of the configuration of type string. The configurationId corresponds to the stage 2 TLTRI. | + +### 5.6.3.11.3 Resource methods + +#### 5.6.3.11.3.1 GET + +The GET method allows to read all ManagePort configurations on the SCEF. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.6.3.11.3.1-1 and table 5.6.3.11.3.1-2. + +**Table 5.6.3.11.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.6.3.11.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | None | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(ManagePort) | 0..N | 200 OK | All RDS dynamic port configuration information related to the request URI are returned. | +| | None | | 307 Temporary Redirect | Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | None | | 308 Permanent Redirect | Permanent redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.6.3.11.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.6.3.11.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.6.3.11.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.6.3.11.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.6.3.11.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.6.3.11.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.6.3A Notifications + +#### 5.6.3A.1 General + +The notifications provided by the NIDD API are specified in this clause. + +**Table 5.6.3A-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|-------------------------------------------------|--------------------|---------------------------------|-----------------------------------------------------------------------------| +| NIDD Configuration Update Notification | {notification_uri} | POST | Send notifications about the status of an NIDD configuration to the SCS/AS. | +| NIDD Downlink Data Delivery Status Notification | {notification_uri} | POST | Report a specific NIDD downlink data delivery result to the SCS/AS. | +| NIDD Uplink Data Notification | {notification_uri} | POST | Send an uplink non-IP data notification from the SCEF to the SCS/AS. | +| ManagePort Notification | {notification_uri} | POST | Send notifications about the port numbers that are reserved. | + +#### 5.6.3A.2 NIDD Configuration Update Notification + +##### 5.6.3A.2.1 Description + +The NIDD Configuration Update Notification allows the SCEF to send notifications about the status of an NIDD configuration to the SCS/AS. + +## 5.6.3A.2.2 Target URI + +The Callback URI "{notification\_uri}" shall be used with the callback URI variables defined in table 5.6.3A.2.2-1. + +**Table 5.6.3A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notification_uri | Link | A URI indicating the notification destination where T8 notification requests shall be delivered.
This URI shall be provided within the "notificationDestination" attribute in the NiddConfiguration type. | + +## 5.6.3A.2.3 Standard Methods + +### 5.6.3A.2.3.1 Notification via POST + +To report the status of the NIDD configuration to the SCS/AS, the SCEF shall use the HTTP POST method on the notification point as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.6.2.1.6-1. + +This method shall support the request data structures specified in table 5.6.3A.2.3.1-1 and the response data structures and response codes specified in table 5.6.3A.2.3.1-2. + +**Table 5.6.3A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|-------------------------------------|-------------|---------------------------------------------| +| NiddConfigurationStatusNotification | 1 | The NIDD configuration status notification. | + +**Table 5.6.3A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Acknowledgement | 1 | 200 OK | The successful acknowledgement of the notification with a body. | +| (None) | | 204 No Content | The successful acknowledgement of the notification without a body. | +| None | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| None | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.6.3A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.6.3A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +### 5.6.3A.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the NiddConfigurationStatusNotification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +## 5.6.3A.3 NIDD Downlink Data Delivery Status Notification + +### 5.6.3A.3.1 Description + +The NIDD Downlink Data Delivery Status Notification allows the SCEF to send notifications about the status of downlink NIDD data delivery to the SCS/AS. This resource is applicable for a single UE and a group of UEs NIDD MT delivery. + +### 5.6.3A.3.2 Target URI + +The Callback URI "{notification\_uri}" shall be used with the callback URI variables defined in table 5.6.3A.3.2-1. + +**Table 5.6.3A.3.2-1: Callback URI variables** + +| Name | Data type | Definition | +|------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notification_uri | Link | A URI indicating the notification destination URI where T8 notification requests shall be delivered.
This URI shall be provided within the "notificationDestination" attribute in the NiddConfiguration type. | + +### 5.6.3A.3.3 Standard Methods + +#### 5.6.3A.3.3.1 Notification via POST + +To report the delivery status of the downlink non-IP data delivery, the SCEF shall use the HTTP POST method on the notification endpoint with the body of the message encoded in JSON format with the data structure defined in table 5.6.2.1.5-1 for a single UE or table 5.6.2.1.8-1 for a group of UEs. + +This method shall support the request and response data structures specified in table 5.6.3A.3.3.1-1 and table 5.6.3A.3.3.1-2 for a single UE, and support the request and response data structures specified in table 5.6.3A.3.3.1-3 and table 5.6.3A.3.3.1-4 for a group of UEs. + +**Table 5.6.3A.3.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|--------------------------------------------|-------------|------------------------------------------------------------------| +| NiddDownlinkDataDeliveryStatusNotification | 1 | The Down link data delivery status notification for a single UE. | + +**Table 5.6.3A.3.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Acknowledgement | 1 | 200 OK | The successful acknowledgement of the notification. | +| (None) | | 204 No Content | The successful acknowledgement of the notification without a body. | +| None | | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| None | | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.6.3A.3.3.1-3: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|-----------------------------------------------|-------------|---------------------------------------------------------------------| +| GmdNiddDownlinkDataDeliveryStatusNotification | 1 | The Down link data delivery status notification for a group of UEs. | + +**Table 5.6.3A.3.3.1-4: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Acknowledgement | 1 | 200 OK | The successful acknowledgement of the notification. | +| (None) | | 204 No Content | The successful acknowledgement of the notification without a body. | +| None | | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| None | | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.6.3A.3.3.1-5: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.6.3A.3.3.1-6: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +### 5.6.3A.3.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the NiddDownlinkDataDeliveryStatusNotification or GmdNiddDownlinkDataDeliveryStatusNotification may alternatively be delivered for a single UE or a group of UEs through the Websocket mechanism as defined in clause 5.2.5.4. + +## 5.6.3A.4 NIDD Uplink Data Notification + +### 5.6.3A.4.1 Description + +The NIDD Uplink Data Notification allows the SCEF to send notifications about received NIDD uplink data.. + +### 5.6.3A.4.2 Target URI + +The Callback URI "{notification\_uri}" shall be used with the callback URI variables defined in table 5.6.3A.4.2-1. + +**Table 5.6.3A.4.2-1: Callback URI variables** + +| Name | Data type | Definition | +|------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notification_uri | Link | A URI indicating the notification destination URI where T8 notification requests shall be delivered.
This URI shall be provided within the "notificationDestination" attribute in the NiddConfiguration type. | + +### 5.6.3A.4.3 Standard Methods + +#### 5.6.3A.4.3.1 Notification via POST + +To send the uplink non-IP data to the SCS/AS, the SCEF shall use the HTTP POST method on the notification endpoint in SCS/AS as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.6.2.1.4-1. + +This method shall support the request data structures specified in table 5.6.3A.4.3.1-1 and the response data structures and response codes specified in table 5.6.3A.4.3.1-2. + +**Table 5.6.3A.4.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|----------------------------|-------------|------------------------------------------------------------------------------| +| NiddUplinkDataNotification | 1 | The parameters and non-IP data for the NIDD uplink non-IP data notification. | + +**Table 5.6.3A.4.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Acknowledgement | 1 | 200 OK | The successful acknowledgement of the uplink data notification | +| (None) | | 204 No Content | The successful acknowledgement of the notification without a body. | +| None | | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| None | | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.6.3A.4.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.6.3A.4.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +#### 5.6.3A.4.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the NiddUplinkDataNotification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +### 5.6.3A.5 ManagePort Notification + +#### 5.6.3A.5.1 Description + +The ManagePort Notification allows the SCEF to send notifications about the port numbers that are reserved. + +#### 5.6.3A.5.2 Target URI + +The Callback URI "{notification\_uri}" shall be used with the callback URI variables defined in table 5.6.3A.5.2-1. + +**Table 5.6.3A.5.2-1: Callback URI variables** + +| Name | Data type | Definition | +|------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notification_uri | Link | A URI indicating the notification destination URI where T8 notification requests shall be delivered.
This URI shall be provided within the "notificationDestination" attribute in the NiddConfiguration type. | + +### 5.6.3A.5.3 Standard Methods + +#### 5.6.3A.5.3.1 Notification via POST + +To send the information about reserved ports and their configuration to the SCS/AS, the SCEF shall use the HTTP POST method on the notification endpoint in SCS/AS as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.6.2.1.10-1. + +This method shall support the request data structures specified in table 5.6.3A.5.3.1-1 and the response data structures and response codes specified in table 5.6.3A.5.3.1-2. + +**Table 5.6.3A.5.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|------------------------|-------------|------------------------------------------------------------------------------------------------------------------| +| ManagePortNotification | 1 | The parameters that represents the information about port numbers that are reserved for use with an application. | + +**Table 5.6.3A.5.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Acknowledgement | 1 | 200 OK | The successful notification of reserved port configuration. | +| (None) | | 204 No Content | The successful acknowledgement of the reserved port configuration without a body. | +| None | | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| None | | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.6.3A.5.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.6.3A.5.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +#### 5.6.3A.5.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the ManagePortNotification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +## 5.6.4 Used Features + +The table below defines the features applicable to the NIDD API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.6.4-1: Features used by NIDD API** + +| Feature Number | Feature | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | GroupMessageDelivery | This feature indicates the support of group message delivery via MT NIDD as defined in clause 5.5.3 of 3GPP TS 23.682 [2]. | +| 2 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 3 | Notification_test_event | The testing of notification connection is supported according to clause 5.2.5.3. | +| 4 | MT_NIDD_modification_cancellation | Modification and cancellation of an individual MT NIDD resource. | +| 5 | Rds_port_verification | This feature indicates the support of RDS port verification in the MO/MT NIDD delivery. | +| 6 | Rds_dynamic_port | This feature indicates the support of RDS dynamic port management. | +| 7 | Rds_serialization_format | This feature indicates the support of RDS Serialization Format reservation, notification, and query. This feature requires that the Rds_dynamic_port is also supported. | +| 8 | PatchUpdate | Indicates the support of enhancements to the northbound interfaces (e.g. support the partial modification of an existing subscription resource). | +| Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification".
Description: A clear textual description of the feature. | | | + +## 5.6.5 Error handling + +### 5.6.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.6.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the NIDD API. + +### 5.6.5.3 Application Errors + +The application errors defined for the NIDD API are listed in table 5.6.5.3-1. + +**Table 5.6.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|------------------------------------|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| QUOTA_EXCEEDED | 403 Forbidden | Not enough quota for the MT NIDD | | +| DATA_TOO_LARGE | 403 Forbidden | The non-IP data size is larger than "maximumPacketSize" of the NIDD configuration. | | +| RDS_PORT_UNKNOWN | 403 Forbidden | The SCEF does not know the RDS port numbers in the MT NIDD, such port numbers does not match with the configured port numbers. | Rds_port_verification | +| OPERATION_PROHIBITED | 403 Forbidden | Indicates the operation is prohibited. | | +| PORT_NOT_FREE | 403 Forbidden | Port is not free as it is already associated with an application | Rds_dynamic_port | +| ALREADY_DELIVERED | 404 Not Found | The SCEF has already delivered the buffered data. | | +| PORT_NOT_ASSOC_WITH_APP | 404 Not Found | Port is free and is not associated with any application. | Rds_dynamic_port | +| SENDING | 409 Conflict | The SCEF is already in sending the buffered non-IP data. | | +| TRIGGERED | 500 Internal Server Error | The SCEF triggered the device but did not buffer the data. The SCS AS may resubmit the data | | +| TEMPORARILY_NOT_REACHABLE | 500 Internal Server Error | The SCEF has aborted the delivery because the UE is temporarily not reachable. The SCEF may in addition indicate a requested re-submission time for the data. | | +| NEXT_HOP | 500 Internal Server Error | Unsuccessful delivery to the next hop. | | +| TIMEOUT | 500 Internal Server Error | Unsuccessful delivery due to timeout. | | +| NO_PDN_CONNECTION | 500 Internal Server Error | The SCEF cannot proceed since there is no PDN connection. | | +| SERIALIZATION_FORMAT_NOT_SUPPORTED | 500 Internal Server Error | The SCEF was not able to configure a Serialization Format for the port | Rds_serialization_format | + +## 5.7 DeviceTriggering API + +### 5.7.1 Overview + +The DeviceTriggering API is a RESTful API that allows the SCS/AS to deliver specific device trigger to the SCEF; it allows the SCS/AS to replace or recall the pending device trigger via the SCEF. If the corresponding device trigger delivery report is received by the SCEF, it also allows the SCEF to indicate the trigger delivery result to the SCS/AS. + +The DeviceTriggering API defines a set of data models, resources and the related procedure for the creation and management of the device triggering. The corresponding JSON schema for the representation of the resources and operations defined by the DeviceTriggering API is provided in its complete form in Annex A.7. + +### 5.7.2 Data model + +#### 5.7.2.1 Resource data types + +##### 5.7.2.1.1 Introduction + +This clause defines data structures to be used in resource representations, including subscription resources. + +Table 5.7.2.1.1-1 specifies data types re-used by the DeviceTriggering API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the DeviceTriggering API. + +**Table 5.7.2.1.1-1: DeviceTriggering API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|----------------------------------------------------------------------------------------| +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.7.4-1. | + +Table 5.7.2.1.1-2 specifies the data types defined for the DeviceTriggering API. + +**Table 5.7.2.1.1-2: DeviceTriggering API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|--------------------------------------------|----------------|----------------------------------------------------------------------------------------------------------------|---------------| +| DeliveryResult | 5.7.2.2.3 | Represents the result of the delivery of a device triggering request. | | +| DeviceTriggering | 5.7.2.1.2 | Represents device triggering related information. | | +| DeviceTriggeringDeliveryReportNotification | 5.7.2.1.3 | Represents a device triggering delivery report notification. | | +| DeviceTriggeringPatch | 5.7.2.1.4 | Represents the parameters to request the modification of an Individual Device Triggering Transaction resource. | PatchUpdate | +| Priority | 5.7.2.2.4 | Represents the priority indication for a trigger payload. | | + +#### 5.7.2.1.2 Type: DeviceTriggering + +This type represents device triggering request. The same structure is used in the request and response. + +**Table 5.7.2.1.2-1: Definition of type DeviceTriggering** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-------------------------|--------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| self | Link | 0..1 | Link to the resource "Individual Device Triggering Transaction". This parameter shall be supplied by the SCEF in HTTP responses. | | +| externalId | ExternalId | 0..1 | Uniquely identifies a user as defined in Clause 4.6.2 of 3GPP TS 23.682 [2].
(NOTE 2) | | +| msisdn | Msisdn | 0..1 | Identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE 2) | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7.
This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| validityPeriod | DurationSec | 1 | The validity time in seconds for the specific action requested. | | +| priority | Priority | 1 | Identifies the priority of the device trigger. | | +| applicationPortId | Port | 1 | This is used to uniquely identify the triggering application addressed in the device for destination port. See clause 9.2.3.24.4 in 3GPP TS 23.040 [43] for further details. | | +| appSrcPortId | Port | 0..1 | This is used to uniquely identify the triggering application addressed in the device for originator port. See clause 9.2.3.24.4 in 3GPP TS 23.040 [43] for further details. | | +| triggerPayload | Bytes | 1 | The device triggering payload. | | +| notificationDestination | Link | 1 | A URI indicating the notification destination for T8 notifications. | | +| requestTestNotification | boolean | 0..1 | Set to true by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. Set to false or omitted otherwise. | Notification_test_event | +| websocketNotifConfig | WebsockNotifConfig | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 5.2.5.4. | Notification_websocket | +| deliveryResult | DeliveryResult | 0..1 | The delivery result shall be included in the HTTP responses that indicate the delivery status of the device triggering. | | + +NOTE 1: Properties marked with a feature as defined in clause 5.7.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. +NOTE 2: One of the properties "externalId" or "msisdn" shall be included. + +### 5.7.2.1.3 Type: DeviceTriggeringDeliveryReportNotification + +This type represents device triggering delivery report notification. + +**Table 5.7.2.1.4-1: Definition of type DeviceTriggeringDeliveryReportNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------|---------------------------------------------------------------------------------------------------|----------------------| +| transaction | Link | 1 | Link to the related device triggering transaction resource to which this notification is related. | | +| Result | DeliveryResult | 1 | OK, unknown or diverse failures | | +| NOTE: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | | | + +#### 5.7.2.1.4 Type: DeviceTriggeringPatch + +This type represents the parameters to request the modification of an Individual Device Triggering Transaction resource. + +**Table 5.7.2.1.4-1: Definition of type DeviceTriggeringPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| validityPeriod | DurationSec | 1 | The validity time in seconds for the specific action requested. | | +| priority | Priority | 1 | Identifies the priority of the device triggering request. | | +| applicationPortId | Port | 1 | This is used to uniquely identify the triggering application addressed in the device for the destination port. See clause 9.2.3.24.4 in 3GPP TS 23.040 [43] for further details. | | +| appSrcPortId | Port | 0..1 | This is used to uniquely identify the triggering application addressed in the device for the originator port. See clause 9.2.3.24.4 in 3GPP TS 23.040 [43] for further details. | | +| triggerPayload | Bytes | 1 | The modified device triggering payload. | | +| notificationDestination | Link | 1 | A URI indicating the notification destination for T8 notifications. | | +| NOTE 1: Properties marked with a feature as defined in clause 5.7.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | | | + +#### 5.7.2.2 Referenced simple data types and enumerations + +##### 5.7.2.2.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +##### 5.7.2.2.2 Simple data types + +The simple data types defined in table 5.7.2.2.2-1 shall be supported. + +**Table 5.7.2.2.2-1: Simple data types** + +| Type name | Description | +|-----------|-------------| +| | | +| | | + +##### 5.7.2.2.3 Enumeration: DeliveryResult + +The enumeration DeliveryResult represents the result of the delivery of a device triggering request + +**Table 5.7.2.2.3-1: Enumeration DeliveryResult** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| SUCCESS | The SCEF includes this value in a device triggering notification.
The value indicates that the device action request was successfully completed. | | +| UNKNOWN | The SCEF includes this value in a device triggering notification.
The value indicates any unspecified errors. | | +| FAILURE | The SCEF includes this value in a device triggering notification.
The value indicates that this trigger encountered a delivery error and is deemed permanently undeliverable. | | +| TRIGGERED | The SCEF includes this value in the response for a successful device triggering request.
The value indicates that device triggering request is accepted by the SCEF. | | +| EXPIRED | The SCEF includes this value in a device triggering notification.
The value indicates that the validity period expired before the trigger could be delivered. | | +| UNCONFIRMED | The SCEF includes this value in a device triggering notification.
The value indicates that the delivery of the device action request is not confirmed. | | +| REPLACED | The SCEF includes this value in the response for a successful device triggering replacement request.
The value indicates that the device triggering replacement request is accepted by the SCEF. | | +| TERMINATE | The SCEF includes this value in the response for a successful device triggering cancellation request.
The value indicates that the delivery of the device action request is terminated by the SCS/AS. | | +| NOTE: Properties marked with a feature as defined in clause 5.7.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.7.2.2.4 Enumeration: Priority + +The enumeration Priority represents the priority indication for a trigger payload. + +**Table 5.7.2.2.4-1: Enumeration Priority** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|----------------------| +| NO_PRIORITY | This value indicates that the device trigger has no priority. | | +| PRIORITY | This value indicates that the device trigger has priority. | | +| NOTE: Properties marked with a feature as defined in clause 5.7.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +### 5.7.3 Resource structure + +#### 5.7.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-device-triggering/v1** + +"apiRoot" is set as described in clause 5.2.4. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.7.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | HTTP initiator | Meaning | +|------------------------------------------|-----------------------------------------|-------------|----------------|-----------------------------------------------------------------------------------------------------------------------| +| Device Triggering Transactions | /{scsAsId}/transactions | GET | SCS/AS | Read all active device triggering transaction resources for a given SCS/AS | +| | | POST | SCS/AS | Create a new device triggering transaction resource | +| Individual Device Triggering Transaction | /{scsAsId}/transactions/{transactionId} | PUT | SCS/AS | Replace an existing Individual Device Triggering Transaction resource and the corresponding device triggering request | +| | | PATCH | SCS/AS | Modify an existing Individual Device Triggering Transaction resource and the corresponding device triggering request. | +| | | GET | SCS/AS | Read a device triggering transaction resource | +| | | DELETE | SCS/AS | Delete an existing device triggering transaction resource and cancel the device triggering | + +### 5.7.3.2 Resource: Device Triggering Transactions + +#### 5.7.3.2.1 Introduction + +This resource allows the SCS/AS to read all active resources related to device triggering, and create a resource for a device triggering transaction with the SCEF. + +#### 5.7.3.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-device-triggering/v1/{scsAsId}/transactions + +This resource shall support the resource URI variables defined in table 5.7.3.2.2-1. + +**Table 5.7.3.2.2-1: Resource URI variables for resource "Device Triggering Transactions"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +#### 5.7.3.2.3 Resource methods + +##### 5.7.3.2.3.1 GET + +The GET method allows to read all active device triggering transactions for a given SCS/AS. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in table 5.7.3.2.3.1-1 and table 5.7.3.2.3.1-2. + +**Table 5.7.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.7.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-------------------------|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(DeviceTriggering) | 0..N | 200 OK | The device triggering transactions information for the SCS/AS in the request URI are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.7.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.7.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.7.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.7.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.7.3.2.3.4 POST + +To create a long-term transaction for a device triggering, the SCS/AS shall use the HTTP POST method on the "transactions" collection resource as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.7.2.1.2-1. + +The possible response messages from the SCEF, depending on whether the POST request is successful or unsuccessful, are shown in Table 5.7.3.2.3.4-1. + +**Table 5.7.3.2.3.4-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------|---------|----------------|--|--|--| +| | DeviceTriggering | | 1 | | | | | +| Response body | Data type | Cardinality | Remarks | | | | | +| | DeviceTriggering | | | 201
Created | | | | +| Parameters to request a device triggering delivery. | | | | | | | | +| The long term transaction for the device triggering was created successfully.
The SCEF shall return a data structure of type "DeviceTriggering" in the response content.
The URI of the created resource shall be returned in the "Location" HTTP header | | | | | | | | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.7.3.2.3.4-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-device-triggering/v1/{scsAsId}/transactions/{transactionId} | + +#### 5.7.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.7.3.3 Resource: Individual Device Triggering Transaction + +#### 5.7.3.3.1 Introduction + +This resource allows the SCS/AS to operate a specific pending device triggering by using a long-term transaction. + +#### 5.7.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-device-triggering/v1/{scsAsId}/transactions/{transactionId} + +This resource shall support the resource URI variables defined in table 5.7.3.3.2-1. + +**Table 5.7.3.3.2-1: Resource URI variables for resource "Individual Device Triggering Transaction"** + +| Name | Data type | Definition | +|---------------|-----------|---------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| transactionId | string | Identifier of the transaction resource. The transactionId corresponds to the stage 2 TLTRI. | + +#### 5.7.3.3.3 Resource methods + +##### 5.7.3.3.3.1 GET + +The GET method allows to read an individual device triggering transaction resource to obtain details of an active transaction. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.7.3.3.3.1-1 and table 5.7.3.3.3.1-2. + +**Table 5.7.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.7.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | DeviceTriggering | 1 | 200 OK | The device triggering transaction information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.7.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.7.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.7.3.3.3.2 PUT + +A pending device triggering delivery can be replaced by the SCS/AS. To replace the pending device triggering, the SCS/AS shall use the HTTP PUT method on the "transaction" instance resource as follows with the body of the message encoded in JSON format including the data structure defined in table 5.7.2.1.2-1 + +The properties "msisdn" or "externalId" shall remain unchanged from previously provided value. + +The possible response messages from the SCEF, depending on whether the PUT request is successful or unsuccessful, are shown in Table 5.7.3.3.3.2-1. + +**Table 5.7.3.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------|-------------|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | DeviceTriggering | 1 | Parameters to replace a device triggering with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | DeviceTriggering | 1 | 200 OK | The device triggering was replaced successfully.

The SCEF shall return an updated representation of the resource within the DeviceTriggering data structure including the "deliveryResult" attribute in the response message body. | +| | none | | 204 No Content | The device triggering was updated successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.7.3.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.7.3.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.7.3.3.3.3 PATCH + +A pending device triggering delivery can be modified by the SCS/AS. If the "PatchUpdate" feature defined in clause 5.7.4 is supported, to partially modify a pending device triggering, delivery, the SCS/AS shall use the HTTP PATCH method on the concerned Individual Device Triggering Transaction resource as follows with the body of the message is encoded in JSON format including the data structure defined in table 5.7.2.1.4-1 + +The possible response messages from the SCEF, depending on whether the PATCH request is successful or unsuccessful, are shown in Table 5.7.3.3.3-1. + +**Table 5.7.3.3.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|-----------------------|--------------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | DeviceTriggeringPatch | 1 | Parameters to request the modification of a pending device triggering delivery. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | DeviceTriggering | 1 | 200 OK | The Individual Device Triggering Transaction resource was successfully modified and a representation of the modified Individual Device Triggering Transaction resource within the DeviceTriggering data structure including the "deliveryResult" attribute is returned by the SCEF in the response message body. | +| | n/a | | 204 No Content | The Individual Device Triggering Transaction resource was successfully modified no content is to be sent in the response message body. | +| | n/a | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | n/a | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.7.3.3.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.7.3.3.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.7.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.7.3.3.3.5 DELETE + +To cancel an ongoing device triggering delivery, the SCS/AS shall use the HTTP DELETE method on the individual "transaction" resource which is indicated by the URI in the Location header of the HTTP POST response: + +The possible response messages from the SCEF, depending on whether the DELETE request is successful or unsuccessful, are shown in Table 5.7.3.3.3.5-1. + +**Table 5.7.3.3.3.5-1: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | DeviceTriggering | 1 | 200 OK | The Device Triggering delivery was cancelled successfully.
The SCEF shall return a data structure of type "DeviceTriggering" with a "TERMINATE" status in the response body. | +| | None | | 204 No Content | The Device Triggering was cancelled successfully.
The SCEF shall not return a response content. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction termination.
The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction termination.
The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.7.3.3.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.7.3.3.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.7.3.4 Void + +## 5.7.3A Notifications + +### 5.7.3A.1 General + +The notifications provided by the DeviceTriggering API are specified in this clause. + +**Table 5.7.3A-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|------------------------------------------------------|--------------------|---------------------------------|-------------------------------------------------------| +| Device Triggering
Delivery Report
Notification | {notification_uri} | POST | Report a device triggering delivery report to SCS/AS. | + +## 5.7.3A.2 Device Triggering Delivery Report Notification + +### 5.7.3A.2.1 Description + +The Device Triggering Delivery Report Notification allows the SCEF to send notifications about device triggering delivery report events to the SCS/AS. + +### 5.7.3A.2.2 Target URI + +The Callback URI "{notification\_uri}" shall be used with the callback URI variables defined in table 5.7.3A.2.2-1. + +**Table 5.7.3A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notification_uri | Link | A URI indicating the notification destination URI where T8 notification requests shall be delivered.
This URI shall be provided within the "notificationDestination" attribute in the DeviceTriggering type. | + +### 5.7.3A.2.3 Standard Methods + +#### 5.7.3A.2.3.1 Notification via POST + +To report the delivery status of the device triggering delivery, the SCEF shall use the HTTP POST method on the notification endpoint as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.7.2.1.4-1. + +This method shall support the request data structures specified in table 5.7.3A.2.3.1-1 and the response data structures and response codes specified in table 5.7.3A.2.3.1-2. + +**Table 5.7.3A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|--------------------------------------------|-------------|----------------------------------------| +| DeviceTriggeringDeliveryReportNotification | 1 | The Device Triggering delivery report. | + +**Table 5.7.3A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Acknowledgement | 1 | 200 OK | The successful acknowledgement of the notification. | +| (None) | | 204 No Content | The successful acknowledgement of the notification without a body. | +| none | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.7.3A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.7.3A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +### 5.7.3a.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the DeviceTriggeringDeliveryReportNotification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +## 5.7.4 Used Features + +The table below defines the features applicable to the DeviceTriggering API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.7.4-1: Features used by DeviceTriggering API** + +| Feature Number | Feature | Description | +|----------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 2 | Notification_test_event | The testing of notification connection is supported according to clause 5.2.5.3. | +| 3 | PatchUpdate | Indicates the support of enhancements to the northbound interfaces (e.g. support the partial modification of an existing subscription resource). | + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification". +Description: A clear textual description of the feature. + +## 5.7.5 Error handling + +### 5.7.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.7.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the DeviceTriggering API. + +### 5.7.5.3 Application Errors + +The application errors defined for DeviceTriggering API are listed in table 5.7.5.3-1. + +**Table 5.7.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 5.8 GMD via MBMS related APIs + +### 5.8.1 Overview + +There are two Group Message Delivery via MBMS related APIs defined: + +- GMDviaMBMSbyMB2 API; +- GMDviaMBMSbyxMB API. + +Both APIs are RESTful APIs that allow the SCS/AS to deliver the group message to the SCEF. They define a set of data models, resources and the related procedures for the creation and management of the group message delivery. The corresponding JSON schema for the representation of the resources and operations defined by the GMDviaMBMSbyMB2 API and GMDviaMBMSbyxMB API are provided in its complete form in Annex A.8.1 and Annex A.8.2, respectively. + +### 5.8.2 GMDviaMBMSbyMB2 API + +#### 5.8.2.1 Data model + +##### 5.8.2.1.1 Resource data types + +###### 5.8.2.1.1.1 Introduction + +This clause defines data structures to be used in resource representations. + +Table 5.8.2.1.1.1-1 specifies data types re-used by the GMDviaMBMSbyMB2 API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the GMDviaMBMSbyMB2 API. + +**Table 5.8.2.1.1.1-1: GMDviaMBMSbyMB2 API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|------------------------------------------------------------------------------------------| +| GeographicArea | 3GPP TS 29.572 [42] | Identifies the geographical information of the user(s). | +| CivicAddress | 3GPP TS 29.572 [42] | Identifies the civic address information of the user(s). | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.8.2.3-1. | + +Table 5.8.2.1.1.1-2 specifies the data types defined for the GMDviaMBMSbyMB2 API. + +**Table 5.8.2.1.1.1-2: GMDviaMBMSbyMB2 API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|----------------------|----------------|-------------------------------------------------------------------------------------------------|---------------| +| GMDBYMB2Notification | 5.8.2.1.1.4 | Represents a group message delivery notification. | | +| GMDViaMBMSByMb2 | 5.8.2.1.1.3 | Represents a group message delivery via MBMS by MB2. | | +| GMDViaMBMSByMb2Patch | 5.8.2.1.1.6 | Represents a modification request of a group message delivery via MBMS by MB2. | | +| MbmsLocArea | 5.8.2.1.1.7 | Represents a user location area within which is sent a group message delivery via MBMS request. | | +| TMGIAllocation | 5.8.2.1.1.2 | Represents an individual TMGI Allocation resource. | | +| TMGIAllocationPatch | 5.8.2.1.1.5 | Represents the parameters to request the modification of a TMGI Allocation resource. | | + +###### 5.8.2.1.1.2 Type: TMGIAllocation + +This type represents TMGI Allocation request. The same structure is used in the request and response. + +**Table 5.8.2.1.1.2-1: Definition of type TMGIAllocation** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-------------------|-------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| self | Link | 0..1 | Link to the resource "Individual TMGI Allocation". This parameter shall be supplied by the SCEF in HTTP responses. | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7.
This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in clause 4.6.2 of 3GPP TS 23.682 [2]. | | +| mbmsLocArea | MbmsLocArea | 0..1 | Represents the location area within which the group message delivery via MBMS is allowed. | | +| tmgiExpiration | DateTimeRo | 0..1 | Identifies the absolute time at which the TMGI is considered to expire. | | + +NOTE: Properties marked with a feature as defined in clause 5.8.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +#### 5.8.2.1.1.3 Type: GMDViaMBMSByMb2 + +This type represents the group message delivery via MBMS by MB2. + +**Table 5.8.2.1.1.3-1: Definition of type GMDViaMBMSByMb2** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|--------------------------|--------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| self | Link | 0..1 | Link to the resource "Individual GMD via MBMS by MB". This parameter shall be supplied by the SCEF in HTTP responses. | | +| notificationDestination | Link | 1 | A URI indicating the notification destination where T8 notification requests shall be delivered | | +| requestTestNotification | boolean | 0..1 | Set to true by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. Set to false or omitted otherwise. | Notification_test_event | +| websocketNotifConfig | WebsockNotifConfig | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 5.2.5.4. | Notification_websocket | +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in clause 4.6.2 of 3GPP TS 23.682 [2]. | | +| mbmsLocArea | MbmsLocArea | 0..1 | Represents the location area within which the group message delivery via MBMS is allowed. | | +| messageDeliveryStartTime | DateTime | 0..1 | Identifies the absolute time at which the SCS/As starts to distribute the data. If absent, it indicates the message shall be sent immediately. | | +| groupMessagePayload | Bytes | 0..1 | Indicates the payload the SCS/AS intends to deliver to the UEs. | | +| scefMessageDeliveryIPv4 | Ipv4AddrRo | 0..1 | Indicates the Ipv4 address where the SCEF wants to receive the data. | | +| scefMessageDeliveryIPv6 | Ipv6AddrRo | 0..1 | Indicates the Ipv6 address where the SCEF wants to receive the data. | | +| scefMessageDeliveryPort | PortRo | 0..1 | Indicates the port number where the SCEF wants to receive the data. | | + +NOTE: Properties marked with a feature as defined in clause 5.8.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +## 5.8.2.1.1.4 Type: GMDBYMb2Notification + +This type represents the group message delivery notification. + +**Table 5.8.2.1.1.4-1: Definition of type GMDBYMb2Notification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-----------------------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------|----------------------| +| transaction | Link | 1 | Link to the transaction resource to which this notification is related. | | +| deliveryTriggerStatus | boolean | 1 | Indicates whether delivery of group message payload corresponding to the TMGI was successful (TRUE) or not (FALSE). | | + +NOTE: Properties marked with a feature as defined in clause 5.8.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +## 5.8.2.1.1.5 Type: TMGIAllocationPatch + +This type represents TMGI Allocation request. The structure is used for PATCH request. + +**Table 5.8.2.1.1.5-1: Definition of type TMGIAllocationPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-----------------|-----------------|-------------|-------------------------------------------------------------------------------------------|----------------------| +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in clause 4.6.2 of 3GPP TS 23.682 [2]. | | +| mbmsLocArea | MbmsLocArea | 0..1 | Represents the location area within which the group message delivery via MBMS is allowed. | | + +NOTE: Properties marked with a feature as defined in clause 5.8.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +## 5.8.2.1.1.6 Type: GMDViaMBMSByMb2Patch + +This type represents group message delivery via MBMS request by MB2. The structure is used for PATCH request. + +**Table 5.8.2.1.1.6-1: Definition of the GMDViaMBMSByMb2Patch data type** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|--------------------------|-----------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in clause 4.6.2 of 3GPP TS 23.682 [2]. | | +| mbmsLocArea | MbmsLocArea | 0..1 | Represents the location area within which the group message delivery via MBMS is allowed. | | +| messageDeliveryStartTime | DateTime | 0..1 | Identifies the absolute time at which the SCS/As starts to distribute the data. If absent, it indicates the message shall be sent immediately. | | +| groupMessagePayload | Bytes | 0..1 | Indicates the payload the SCS/AS intends to deliver to the UEs. | | +| notificationDestination | Link | 0..1 | A URI indicating the notification destination where the notification requests shall be delivered. | | + +NOTE: Properties marked with a feature as defined in clause 5.8.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +#### 5.8.2.1.1.7 Type: MbmsLocArea + +This data type represents the user location area which is sent from the SCS/AS to the SCEF by group message delivery via MBMS request. + +**Table 5.8.2.1.1.7-1: Definition of the MbmsLocArea data type** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------|----------------------------------------------------------------------------------------------------|----------------------| +| cellId | array(string) | 0..N | Indicates a Cell Global Identification of the user which identifies the cell the UE is registered. | | +| enodeBId | array(string) | 0..N | Indicates an eNodeB in which the UE is currently located. | | +| geographicArea | array(Geographic Area) | 0..N | Identifies a geographic area of the user where the UE is located. | | +| mbmsServiceAreaId | array(string) | 0..N | Identifies an MBMS Service Area Identity of the user where the UE is located. | | +| civicAddress | array(CivicAddresses) | 0..N | Identifies a civic address of the user where the UE is located. | | +| NOTE: Properties marked with a feature as defined in clause 5.8.2.3 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | + +#### 5.8.2.2 Resource structure + +##### 5.8.2.2.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-group-message-delivery-mb2/v1** + +"apiRoot" is set as described in clause 5.2.4. "apiName" shall be set to "3gpp-group-message-delivery-mb2" and "apiVersion" shall be set to "v1" for the version defined in the present document. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.8.2.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | HTTP initiator | Meaning | +|--------------------------------|-----------------------------------------------------------------------------|-------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| TMGI Allocation | /{scsAsId}
/tmgi-allocation | GET | SCS/AS | Read all active TMGI resources for a given SCS/AS | +| | | POST | SCS/AS | Create a new TMGI resource for a given SCS/AS | +| Individual TMGI Allocation | /{scsAsId}
/tmgi-allocation/{tmgi} | PUT | SCS/AS | Replace an existing TMGI resource for a given SCS/AS and TMGI | +| | | PATCH | SCS/AS | Modify an existing TMGI resource for a given SCS/AS and TMGI | +| | | GET | SCS/AS | Read a TMGI allocation resource for a given SCS/AS and a TMGI | +| | | DELETE | SCS/AS | Deallocate an existing TMGI resource for a given SCS/AS and TMGI | +| GMD via MBMS by MB2 | /{scsAsId}
/tmgi-allocation/{tmgi}/delivery-via-mbms | GET | SCS/AS | Read all group message delivery resources for a given SCS/AS and TMGI. | +| | | POST | SCS/AS | Create a group message delivery resource for given SCS/AS and TMGI selected by the SCS/AS when MB2 is used as a southbound interface. | +| Individual GMD via MBMS by MB2 | /{scsAsId}
/tmgi-allocation/{tmgi}/delivery-via-mbms/
{transactionId} | PUT | SCS/AS | Replace a group message delivery resource | +| | | PATCH | SCS/AS | Modify a group message delivery resource. | +| | | GET | SCS/AS | Read a group message delivery resource. | +| | | DELETE | SCS/AS | Delete a group message delivery resource. | + +## 5.8.2.2.2 Resource: TMGI Allocation + +### 5.8.2.2.2.1 Introduction + +This resource allows the SCS/AS to read all active TMGI or request a TMGI allocation. + +### 5.8.2.2.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-group-message-delivery-mb2/v1/{scsAsId}/tmgi-allocation + +This resource shall support the resource URI variables defined in table 5.8.2.2.2.2-1. + +**Table 5.8.2.2.2.2-1: Resource URI variables for resource "TMGI Allocation"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +### 5.8.2.2.2.3 Resource methods + +#### 5.8.2.2.2.3.1 GET + +The GET method read all TMGI Allocation resource for a given SCS/AS. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.2.3.1-1. + +**Table 5.8.2.2.2.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(TMGIAllocation) | 0..N | 200 OK | The TMGI allocation for the SCS/AS in the request URI are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.2.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.2.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.2.2.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.8.2.2.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.8.2.2.2.3.4 POST + +The POST method creates a new TMGI Allocation resource for a given SCS/AS. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.2.3.4-1. + +**Table 5.8.2.2.3.4-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|-----------------------------------------------------------------------------------------------------|----------------|-------------|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | TMGIAllocation | 1 | Parameters to create a TMGI allocation resource | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | TMGIAllocation | 1 | 201
Created |

The creation of a TMGI allocation was created successfully.

The SCEF shall return a data structure of type "TMGI Allocation" in the response content.

On success, the HTTP response shall include a "Location" HTTP header that points to the created resource URI identified by the ScsAsId and the TMGI

| +| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. | | | | | + +**Table 5.8.2.2.3.4-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-group-message-delivery-mb2/v1/{scsAsId}/tmgi-allocation/{tmgi} | + +#### 5.8.2.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.8.2.2.3 Resource: Individual TMGI Allocation + +#### 5.8.2.2.3.1 Introduction + +This resource allows the SCS/AS to read an active TMGI or renew an TMGI. + +#### 5.8.2.2.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-group-message-delivery-mb2/v1/{scsAsId}/tmgi-allocation/{tmgi} + +This resource shall support the resource URI variables defined in table 5.8.2.2.3.2-1. + +**Table 5.8.2.2.3.2-1: Resource URI variables for resource "Individual TMGI Allocation"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| Tmgi | string | TMGI. | + +#### 5.8.2.2.3.3 Resource methods + +##### 5.8.2.2.3.3.1 GET + +The GET method reads a TMGI Allocation resource for a given SCS/AS. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.3.3.1-1. + +**Table 5.8.2.2.3.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|----------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | TMGIAllocation | 1 | 200 OK | A TMGI allocation for the SCS/AS in the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.3.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.3.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.2.2.3.3.2 PUT + +The PUT method replaces a TMGI Allocation resource for a given SCS/AS to renew a TMGI expiration time. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.3.3.2-1. + +**Table 5.8.2.2.3.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|----------------|-------------|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | TMGIAllocation | 1 | Parameters to replace a TMGI resource | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | TMGIAllocation | 1 | 200 OK | The replace of a TMGI allocation was created successfully. | +| | none | | 204 No Content | The TMGI expiration time renewal is successful, and no content is to be sent in the response message body. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.3.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.3.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.2.2.3.3.3 PATCH + +The PATCH method modifies a TMGI Allocation resource for a given SCS/AS to renew a TMGI expiration time. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.3.3.3-1. + +**Table 5.8.2.2.3.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|---------------------|-------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | TMGIAllocationPatch | 1 | Parameters to modify a TMGI resource | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | TMGIAllocation | 1 | 200 OK | The modification of a TMGI allocation was created successfully. | +| | none | | 204 No Content | The TMGI expiration time renewal is successful, and no content is to be sent in the response message body. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.3.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.3.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.2.2.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.8.2.2.3.3.5 DELETE + +The DELETE method deletes a TMGI Allocation resource for a given SCS/AS to deallocate a TMGI. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.3.3.5-1. + +**Table 5.8.2.2.3.3.5-1: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The TMGI allocation resource was removed successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.3.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.3.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.8.2.2.4 Resource: GMD via MBMS by MB2 + +### 5.8.2.2.4.1 Introduction + +This resource allows the SCS/AS to read all active group message delivery resources or create a group message delivery when the MB2 is used as a southbound interface. + +### 5.8.2.2.4.2 Resource definition + +Resource URI: {apiRoot}/3gpp-group-message-delivery-mb2/v1/{scsAsId}/tmgi-allocation/{tmgi}/delivery-via-mbms + +This resource shall support the resource URI variables defined in table 5.8.2.2.4.2-1. + +**Table 5.8.2.2.4.2-1: Resource URI variables for resource "GMD via MBMS by MB2"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| Tmgi | string | TMGI | + +## 5.8.2.2.4.3 Resource methods + +## 5.8.2.2.4.3.1 GET + +The GET method reads all group message delivery via MBMS resources for a given SCS/AS and a TMGI. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.4.3.1-1. + +**Table 5.8.2.2.4.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-------------------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(GMDViaMBMSBy Mb2) | 0..N | 200 OK | The TMGI allocation for the SCS/AS in the request URI are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.4.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.4.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.8.2.2.4.3.2 PUT + +This HTTP method is not supported for the resource. + +## 5.8.2.2.4.3.3 PATCH + +This HTTP method is not supported for the resource. + +## 5.8.2.2.4.3.4 POST + +The POST method creates a new group message delivery via MBMS resource for a given SCS/AS and TMGI selected by the SCS/AS. It is initiated by the SCS/AS and answered by the SCEF. The SCEF shall construct the URI of the created resource using that URI. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.4.3.4-1. + +**Table 5.8.2.2.4.3.4-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | GMDViaMBMSByMb2 | 1 | Parameters to create and authorize a group message delivery via MBMS with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | GMDViaMBMSByMb2 | 1 | 201
Created |

The creation of a group message delivery was created successfully.

The SCEF shall return a data structure of type "GMDViaMBMSByMb2" in the response content.

On success, the HTTP response shall include a "Location" HTTP header that points to the created resource URI identified by the ScsAsId and the Transaction Id.

| + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.4.3.4-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-group-message-delivery-mb2/v1/{scsAsId}/tmgi-allocation/{tmgi}/delivery-via-mbms/{transactionId} | + +#### 5.8.2.2.4.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.8.2.2.5 Resource: Individual GMD via MBMS by MB2 + +#### 5.8.2.2.5.1 Introduction + +This resource allows the SCS/AS to modify or delete a group message delivery via MBMS by MB2 resource. + +#### 5.8.2.2.5.2 Resource definition + +Resource URI: {apiRoot}/3gpp-group-message-delivery-mb2/v1/{scsAsId}/tmgi-allocation/{tmgi}/delivery-via-mbms/{transactionId} + +This resource shall support the resource URI variables defined in table 5.8.2.2.5.2-1. + +**Table 5.8.2.2.5.2-1: Resource URI variables for resource "Individual GMD via MBMS by MB2"** + +| Name | Data type | Definition | +|---------------|-----------|-----------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| transactionId | string | TransactionId selected by the SCEF. The transactionId corresponds to the stage 2 TLTRI. | + +#### 5.8.2.2.5.3 Resource methods + +##### 5.8.2.2.5.3.1 GET + +The GET method reads a group message delivery via MBMS by MB2 resource for a given SCS/AS, a TMGI and a transactionId. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.5.3.1-1. + +**Table 5.8.2.2.5.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | GMDViaMBMSbyMb2 | 0..1 | 200 OK | The group message delivery resource for the SCS/AS in the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.5.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.5.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.2.2.5.3.2 PUT + +Assuming that a group message delivery has been created using the HTTP POST method described in clause 5.8.2.2.4.3.4, replace of its properties can be performed by the SCS/AS by using the HTTP PUT method on the "delivery\_via\_mbms" instance resource as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.8.2.2.5.3.2-1. + +The content body of the group message delivery via MBMS update request shall contain updated full representation of the group message delivery resource. Only the properties "locationinfo", "accuracy", "messageDelivervstarttime" and "groupMessagepayload" can be modified. + +The possible response messages from the SCEF, depending on whether the PUT request is successful or unsuccessful, are shown in table 5.8.2.2.5.3.2-1. + +**Table 5.8.2.2.5.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|------------------|--------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | GMDViaMBMSByMb2 | 1 | Parameters to replace group message delivery resource with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | GMDViaMBMSByMb2 | 1 | 200 OK | The group message delivery was modified successfully.
The SCEF shall return an updated data structure of type "GMDViaMBMSByMb2" in the response content. | +| | none | | 204 No Content | The group message delivery is replaced successfully, and no content is to be sent in the response message body. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.5.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.5.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.8.2.2.5.3.3 PATCH + +Assuming that a group message delivery has been created using the HTTP POST method described in clause 5.8.2.2.4.3.4, partial updating of its properties can be performed by the SCS/AS by using the HTTP PATCH method on the "delivery-via-mbms" instance resource. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.2.2.5.3.3-1. + +**Table 5.8.2.2.5.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|----------------------|--------------------|------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | GMDViaMBMSByMb2Patch | 1 | Parameters to partially update a group message delivery with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | GMDViaMBMSByMb2 | 1 | 200 OK | The group message delivery was modified successfully.
The SCEF shall return an updated data structure of type "GMDViaMBMSByMb2" in the response content. | +| | none | | 204 No Content | The group message delivery is modified successfully, and no content is to be sent in the response message body. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.5.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.5.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.2.2.5.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.8.2.2.5.3.5 DELETE + +To cancel a group message delivery, the SCS/AS shall use the HTTP DELETE method on the individual "delivery\_via\_mbms" resource which is indicated by the URI in the Location header of the HTTP POST response: + +The possible response messages from the SCEF, depending on whether the DELETE request is successful or unsuccessful, are shown in table 5.8.2.2.5.3.5-1. + +**Table 5.8.2.2.5.3.5-1.: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The group message delivery subscription was cancelled successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2.5.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.2.2.5.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.8.2.2.6 Void + +## 5.8.2.2A Notifications + +### 5.8.2.2A.1 General + +The notifications provided by the GMDviaMBMSbyMB2 API are specified in this clause. + +**Table 5.8.2.2A.1-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|----------------------------------|---------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------| +| GMD via MBMS by MB2 Notification | {notificationDestination} | POST | Report a specific group message delivery result to the SCS/AS for a given transaction Id selected by the SCEF. | + +## 5.8.2.2A.2 GMD via MBMS by MB2 Notification + +### 5.8.2.2A.2.1 Description + +The GMD via MBMS by MB2 Notification allows the SCEF report the delivery trigger status to the SCS/AS to indicate whether group message delivery was triggered successful. + +### 5.8.2.2A.2.2 Target URI + +The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 5.8.2.2A.2.2-1. + +**Table 5.8.2.2A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|-------------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notificationDestination | Link | A URI indicating the notification destination where T8 notification requests shall be delivered.
This URI shall be provided within the field "notificationDestination" in the GMDViaMBMSByMb2 type. | + +### 5.8.2.2A.2.3 Standard Methods + +#### 5.8.2.2A.2.3.1 Notification via POST + +To report the status of the delivery trigger status to the SCS/AS, the SCEF shall use the HTTP POST method on the notification point as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.8.2.1.1.4-1. + +This method shall support the request data structures specified in table 5.8.2.2A.2.3.1-1 and the response data structures and response codes specified in table 5.8.2.2A.2.3.1-2. + +**Table 5.8.2.2A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|----------------------|-------------|-----------------------------------| +| GMDBYMb2Notification | 1 | The delivery status notification. | + +**Table 5.8.2.2A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Acknowledgement | 1 | 200 OK | The successful acknowledgement of the notification with a body. | +| (None) | | 204 No Content | The successful acknowledgement of the notification without a body. | +| none | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.8.2.2A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.8.2.2A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +#### 5.8.2.2A.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the GMDByMb2Notification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +### 5.8.2.3 Used Features + +The table below defines the features applicable to the GMDviaMBMSbyMB2 API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.8.2.3-1: Features used by GMDviaMBMSbyMB2 API** + +| Feature Number | Feature | Description | +|-----------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 2 | Notification_test_event | The testing of notification connection is supported according to clause 5.2.5.3. | +| Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification". | | | +| Description: A clear textual description of the feature. | | | + +### 5.8.2.4 Error handling + +#### 5.8.2.4.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +#### 5.8.2.4.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the GMDviaMBMSbyMB2 API. + +#### 5.8.2.4.3 Application Errors + +The application errors defined for GMDviaMBMSbyMB2 API are listed in table 5.8.2.4.3-1. + +**Table 5.8.2.4.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 5.8.3 GMDviaMBMSbyxMB API + +### 5.8.3.1 Data model + +#### 5.8.3.1.1 Resource data types + +##### 5.8.3.1.1.1 Introduction + +This clause defines data structures to be used in resource representations. + +Table 5.8.3.1.1.1-1 specifies data types re-used by the GMDviaMBMSbyxMB API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the GMDviaMBMSbyxMB API. + +**Table 5.8.3.1.1.1-1: GMDviaMBMSbyxMB API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|------------------------------------------------------------------------------------------| +| GeographicArea | 3GPP TS 29.572 [42] | Identifies the geographical information of the user(s). | +| CivicAddress | 3GPP TS 29.572 [42] | Identifies the civic address information of the user(s). | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.8.3.3-1. | + +Table 5.8.3.1.1.1-2 specifies the data types defined for the GMDviaMBMSbyxMB API. + +**Table 5.8.3.1.1.1-2: GMDviaMBMSbyxMB API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|-------------------------|----------------|--------------------------------------------------------------------------------------------------|---------------| +| GMDBByxMBNotification | 5.8.3.1.1.4 | Represents a group message delivery notification. | | +| GMDViaMBMSByxMB | 5.8.3.1.1.3 | Represents a group message delivery via MBMS by xMB. | | +| GMDViaMBMSByxMBPatch | 5.8.3.1.1.5 | Represents a modification request of a group message delivery via MBMS by xMB. | | +| MbmsLocArea | 5.8.3.1.1.6 | Represents a user location area whithin which is sent a group message delivery via MBMS request. | | +| ServiceAnnouncementMode | 5.8.3.1.2.3 | Represents the service announcement mode. | | +| ServiceCreation | 5.8.3.1.1.2 | Represents an individual xMB Service resource. | | + +##### 5.8.3.1.1.2 Type: ServiceCreation + +This type represents the service resource. + +**Table 5.8.3.1.1.2-1: Definition of the ServiceCreation data type** + +| Attribute name | Data type | Cardinality | Description | Applicability
(NOTE) | +|-------------------------|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| self | Link | 0..1 | Link to the resource "Individual xMB Service". This parameter shall be supplied by the SCEF in HTTP responses. | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7.
This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in clause 4.6.2 of 3GPP TS 23.682 [2] supplied by the SCS/AS. | | +| userServiceId | string | 0..1 | Identifies the MBMS User Service supplied by the SCEF. | | +| serviceClass | string | 0..1 | The service class that service belongs to supplied by the SCEF. | | +| serviceLanguages | array(string) | 0..N | List of language of the service content supplied by the SCEF. | | +| serviceNames | array(string) | 0..N | List of Service Names supplied by the SCEF | | +| receiveOnlyMode | boolean | 0..1 | When set to 'true', the Content Provider indicates that the service is a Receive Only Mode service. This parameter is supplied by the SCEF | | +| serviceAnnouncementMode | ServiceAnnouncementMode | 0..1 | Enumeration of Service Announcement Mode supplied by the SCEF. | | + +NOTE: Properties marked with a feature as defined in clause 5.8.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +#### 5.8.3.1.1.3 Type: GMDViaMBMSByxMB + +This type represents the group message delivery via MBMS by xMB. + +**Table 5.8.3.1.1.3-1: Definition of type GMDViaMBMSByxMB** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|--------------------------|--------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| self | Link | 0..1 | Link to the resource "Individual GMD via MBMS by xMB". This parameter shall be supplied by the SCEF in HTTP responses. | | +| notificationDestination | Link | 1 | A URI indicating the notification destination where T8 notification requests shall be delivered | | +| requestTestNotification | boolean | 0..1 | Set to true by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. Set to false or omitted otherwise. | Notification_test_event | +| websocketNotifConfig | WebsockNotifConfig | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 5.2.5.4. | Notification_websocket | +| mbmsLocArea | MbmsLocArea | 0..1 | Represents the location area within which the group message delivery via MBMS is allowed. | | +| messageDeliveryStartTime | DateTime | 0..1 | Identifies the absolute time at which the SCS/As starts to distribute the data. If absent, it indicates the message shall be sent immediately. | | +| messageDeliveryStopTime | DateTime | 0..1 | Identifies the absolute time at which the SCS/As is expected to stop distributing the data. If absent, configuration time will be used. | | +| groupMessagePayload | Bytes | 0..1 | Indicates the payload the SCS/AS intends to deliver to the UEs. | | +| scefMessageDeliveryIPv4 | Ipv4AddrRo | 0..1 | Indicates the Ipv4 address where the SCEF wants to receive the data. | | +| scefMessageDeliveryIPv6 | Ipv6AddrRo | 0..1 | Indicates the Ipv6 address where the SCEF wants to receive the data. | | +| scefMessageDeliveryPort | PortRo | 0..1 | Indicates the port number where the SCEF wants to receive the data. | | + +NOTE: Properties marked with a feature as defined in clause 5.8.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +#### 5.8.3.1.1.4 Type: GMDByxMBNotification + +This type represents the group message delivery notification. + +**Table 5.8.3.1.1.4-1: Definition of type GMDByxMbNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-----------------------|-----------|-------------|------------------------------------------------------------------------------------------|----------------------| +| transaction | Link | 1 | Link to the transaction resource to which this notification is related. | | +| deliveryTriggerStatus | boolean | 1 | Indicates whether delivery of group message payload was successful (TRUE) or not (FALSE) | | + +NOTE: Properties marked with a feature as defined in clause 5.8.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +#### 5.8.3.1.1.5 Type: GMDViaMBMSByxMBPatch + +This type represents group message delivery via MBMS request. The structure is used for PATCH request. + +**Table 5.8.3.1.1.5-1: Definition of the GMDViaMBMSByxMBPatch data type** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|--------------------------|-------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| mbmsLocArea | MbmsLocArea | 0..1 | Represents the location area within which the group message delivery via MBMS is allowed. | | +| messageDeliveryStartTime | DateTime | 0..1 | Identifies the absolute time at which the SCS/As starts to distribute the data. If absent, it indicates the message shall be sent immediately. | | +| messageDeliveryStopTime | DateTime | 0..1 | Identifies the absolute time at which the SCS/As is expected to stop distributing the data. If absent, the configuration value will be used. | | +| groupMessagePayload | Bytes | 0..1 | Indicates the payload the SCS/AS intends to deliver to the UEs. | | +| notificationDestination | Link | 0..1 | A URI indicating the notification destination where the notification requests shall be delivered | | + +NOTE: Properties marked with a feature as defined in clause 5.8.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +#### 5.8.3.1.1.6 Type: MbmsLocArea + +This data type represents the user location area which is sent from the SCS/AS to the SCEF by group message delivery via MBMS request. + +**Table 5.8.3.1.1.6-1: Definition of the MbmsLocArea data type** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-------------------|------------------------|-------------|----------------------------------------------------------------------------------------------------|----------------------| +| cellId | array(string) | 0..N | Indicates a Cell Global Identification of the user which identifies the cell the UE is registered. | | +| enodeBId | array(string) | 0..N | Indicates an eNodeB in which the UE is currently located. | | +| geographicArea | array(Geographic Area) | 0..N | Identifies a geographic area of the user where the UE is located. | | +| mbmsServiceAreaId | array(string) | 0..N | Identifies an MBMS Service Area Identity of the user where the UE is located. | | +| civicAddress | array(CivicAddresses) | 0..N | Identifies a civic address of the user where the UE is located. | | + +NOTE: Properties marked with a feature as defined in clause 5.8.2.3 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +#### 5.8.3.1.2 Referenced simple data types and enumerations + +##### 5.8.3.1.2.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +##### 5.8.3.1.2.2 Simple data types + +The simple data types defined in table 5.8.3.1.2.2-1 shall be supported. + +**Table 5.8.3.1.2.2-1: Simple data types** + +| Type name | Description | +|-----------|-------------| +| | | +| | | + +#### 5.8.3.1.2.3 Enumeration: ServiceAnnouncementMode + +The enumeration ServiceAnnouncementMode represents the service announcement mode + +**Table 5.8.3.1.2.3-1: Enumeration ServiceAnnouncementMode** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| SACH | BM-SC performs the service announcement for the current service using the SACH channel. | | +| CONTENT_PROVIDER | BM-SC provides the necessary service access information used by the Content Provider to create the service announcement information. | | +| NOTE: Properties marked with a feature as defined in clause 5.7.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +### 5.8.3.2 Resource structure + +#### 5.8.3.2.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-group-message-delivery-xmb/v1** + +"apiRoot" is set as described in clause 5.2.4. "apiName" shall be set to "3gpp-group-message-delivery-xmb" and "apiVersion" shall be set to "v1" for the version defined in the present document. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.8.3.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | HTTP initiator | Meaning | +|--------------------------------|-----------------------------------------------------------------------|-------------|----------------|----------------------------------------------------------------------------------------------------------------------| +| xMB Services | /{scsAsId}
/services | POST | SCS/AS | Create a service when xMB is used as a southbound interface. | +| | | GET | SCS/AS | Read all active service resources for a given SCS/AS. | +| Individual xMB Service | /{scsAsId}
/services/{serviceId} | GET | SCS/AS | Read an active service resource for a given SCS/AS and Service Id. | +| | | DELETE | SCS/AS | Delete an existing service resource for a given SCS/AS and Service Id. | +| GMD via MBMS by xMB | /{scsAsId}
/services/{serviceId}/delivery-via-mbms | GET | SCS/AS | Read all group message delivery resources for a given SCS/AS and Service Id. | +| | | POST | SCS/AS | Create a group message delivery resource for given SCS/AS and Service Id when xMB is used as a southbound interface. | +| Individual GMD via MBMS by xMB | /{scsAsId}
/services/{serviceId}/delivery-via-mbms/{transactionId} | PUT | SCS/AS | Replace a group message delivery resource | +| | | PATCH | SCS/AS | Modify a group message delivery resource. | +| | | GET | SCS/AS | Read a group message delivery resource. | +| | | DELETE | SCS/AS | Delete a group message delivery resource. | + +### 5.8.3.2.2 Resource: xMB Services + +#### 5.8.3.2.2.1 Introduction + +This resource allows the SCS/AS to create service resource when the xMB is used as a southbound interface. + +#### 5.8.3.2.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-group-message-delivery-xmb/v1/{scsAsId}/services + +This resource shall support the resource URI variables defined in table 5.8.3.2.2.2-1. + +**Table 5.8.3.2.2.2-1: Resource URI variables for resource "GMD via MBMS by xMB"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +#### 5.8.3.2.2.3 Resource methods + +##### 5.8.3.2.2.3.1 GET + +The GET method allows the SCS/AS read all active service resources for a given SCS/AS. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.3.2.2.3.1-1. + +**Table 5.8.3.2.2.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none. | | | | +| Response body | Data type | | Cardinality | Response codes | +| | Remarks | | | | +| | array(ServiceCreation) | 0..N | 200 OK | The service resource for the SCS/AS in the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2.2.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.3.2.2.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.3.2.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.8.3.2.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.8.3.2.2.3.4 POST + +The POST method creates a new service resource for a given SCS/AS. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.3.2.2.3.4-1. + +**Table 5.8.3.2.2.3.4-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|------------------|--------------------|-------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ServiceCreation | 1 | Parameters to create and authorize a service with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | ServiceCreation | 1 | 201
Created | The resource of a service was created successfully.
The SCEF shall return a data structure of type "ServiceCreation" in the response content.
On success, the HTTP response shall include a "Location" HTTP header that points to the created resource URI identified by the ScsAsId and the ServiceId. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2.2.3.4-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-group-message-delivery-xmb/v1/{scsAsId}/services/{serviceId} | + +#### 5.8.3.2.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.8.3.2.3 Resource: Individual xMB Service + +#### 5.8.3.2.3.1 Introduction + +This resource allows the SCS/AS to delete a service resource. + +#### 5.8.3.2.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-group-message-delivery-xmb/v1/{scsAsId}/services/{serviceId} + +This resource shall support the resource URI variables defined in table 5.8.3.2.3.2-1. + +**Table 5.8.3.2.3.2-1: Resource URI variables for resource "Individual Service Creation"** + +| Name | Data type | Definition | +|-------------|------------------|----------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| serviceId | string | Identifier of the service. | + +#### 5.8.3.2.3.3 Resource methods + +##### 5.8.3.2.3.3.1 GET + +The GET method reads a active service resource for a given SCS/AS and a service Id. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.3.2.3.3.1-1. + +**Table 5.8.3.2.3.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | ServiceCreation | 0..1 | 200 OK | The service resource for the SCS/AS and Service Id in the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2.3.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.3.2.3.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.3.2.3.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.8.3.2.3.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.8.3.2.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.8.3.2.3.3.5 DELETE + +To delete a service resource, the SCS/AS shall use the HTTP DELETE method on the "ServiceCreation" resource which is indicated by the URI in the Location header of the HTTP POST response: + +The possible response messages from the SCEF, depending on whether the DELETE request is successful or unsuccessful, are shown in table 5.8.3.2.3.3.5-1. + +**Table 5.8.3.2.3.3.5-1.: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The group message delivery subscription was cancelled successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply + +**Table 5.8.3.2.3.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.3.2.3.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.3.2.4 Resource: GMD via MBMS by xMB + +##### 5.8.3.2.4.1 Introduction + +This resource allows the SCS/AS to: + +- read all of the group message delivery via MBMS by xMB resources for a given SCS/AS and a service identifier; or +- create a group message delivery when the xMB is used as a southbound interface. + +##### 5.8.3.2.4.2 Resource definition + +Resource URI: {apiRoot}/3gpp-group-message-delivery-xmb/v1/{scsAsId}/services/{serviceId}/delivery-via-mbms + +This resource shall support the resource URI variables defined in table 5.8.3.2.4.2-1. + +**Table 5.8.3.2.4.2-1: Resource URI variables for resource "GMD via MBMS by xMB"** + +| Name | Data type | Definition | +|-----------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| ServiceId | string | Identifier of the service | + +## 5.8.3.2.4.3 Resource methods + +## 5.8.3.2.4.3.1 GET + +The GET method reads all of the group message delivery via MBMS by xMB resources for a given SCS/AS and a service identifier. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.3.2.4.3.1-1. + +**Table 5.8.3.2.4.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | None | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(GMDViaMBMSByxMB) | 0..N | 200 OK | The list of "GMDViaMBMSByxMB" data for the SCS/AS and the service identifier are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2.4.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.3.2.4.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.8.3.2.4.3.2 PUT + +This HTTP method is not supported for the resource. + +## 5.8.3.2.4.3.3 PATCH + +This HTTP method is not supported for the resource. + +## 5.8.3.2.4.3.4 POST + +The POST method creates a new group message delivery via MBMS resource for a given SCS/AS and service Id selected by the SCS/AS. It is initiated by the SCS/AS and answered by the SCEF. This method shall support request and response data structures, and response codes, as specified in the table 5.8.3.2.4.3.4-1. + +**Table 5.8.3.2.4.3.4-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | GMDViaMBMSByxMB | 1 | Parameters to create and authorize a group message delivery via MBMS with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | GMDViaMBMSByxMB | 1 | 201
Created |

The creation of a group message delivery was created successfully.

The SCEF shall return a data structure of type "GMDViaMBMSByxMB" in the response content.

On success, the HTTP response shall include a "Location" HTTP header that points to the created resource URI identified by the ScsAsId and the Transaction Id

| + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2.4.3.4-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-group-message-delivery-xmb/v1/{scsAsId}/services/{serviceId}/delivery-via-mbms/{transactionId} | + +#### 5.8.3.2.4.3.5 DELETE + +This HTTP method is not supported for the resource. + +#### 5.8.3.2.5 Resource: Individual GMD via MBMS by xMB + +##### 5.8.3.2.5.1 Introduction + +This resource allows the SCS/AS to modify or delete a group message delivery via MBMS resource. + +##### 5.8.3.2.5.2 Resource definition + +Resource URI: {apiRoot}/3gpp-group-message-delivery-xmb/v1/{scsAsId}/services/{serviceId}/delivery-via-mbms/{transactionId} + +This resource shall support the resource URI variables defined in table 5.8.3.2.5.2-1. + +**Table 5.8.3.2.5.2-1: Resource URI variables for resource "Individual GMD via MBMS by xMB"** + +| Name | Data type | Definition | +|-----------|-----------|-----------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| serviceId | string | Identifier of the service selected by the SCEF. The transactionId corresponds to the stage 2 TLTRI. | + +##### 5.8.3.2.5.3 Resource methods + +###### 5.8.3.2.5.3.1 GET + +The GET method reads a group message delivery via MBMS resource for a given SCS/AS, a service Id and a transactionId. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.3.2.5.3.1-1. + +**Table 5.8.3.2.5.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | GMDViaMBMSByxMB | 0..1 | 200 OK | The group message delivery resource for the SCS/AS in the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2.5.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.3.2.5.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.8.3.2.5.3.2 PUT + +Assuming that a group message delivery has been created using the HTTP POST method described in clause 5.8.3.2.4.3.4, replace of its properties can be performed by the SCS/AS by using the HTTP PUT method on the "delivery-via-mbms" instance resource as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.8.3.1.1.3-1. + +The content body of the group message delivery via MBMS update request shall contain updated full representation of the group message delivery resource. Only the properties "locationinfo", "accuracy", "messageDelivervstarttime", "messageDelivervstoptime" and "groupMessagepayload" can be modified. + +The possible response messages from the SCEF, depending on whether the PUT request is successful or unsuccessful, are shown in table 5.8.3.2.5.3.2-1. + +**Table 5.8.3.2.5.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|------------------|--------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | GMDViaMBMSByxMB | 1 | Parameters to replace group message delivery resource with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | GMDViaMBMSByxMB | 1 | 200 OK | The group message delivery was modified successfully.
The SCEF shall return an updated data structure of type "GMDViaMBMSByxMB" in the response content. | +| | none | | 204 No Content | The group message delivery was modified successfully, and no content is to be sent in the response message body. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2.5.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.3.2.5.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.8.3.2.5.3.3 PATCH + +Assuming that a group message delivery has been created using the HTTP POST method described in clause 5.8.3.2.4.3.4, partial updating of its properties can be performed by the SCS/AS by using the HTTP PATCH method on the "delivery-via-mbms" instance resource. + +This method shall support request and response data structures, and response codes, as specified in the table 5.8.3.2.5.3.3-1. + +**Table 5.8.3.2.5.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|-----------------------|--------------------|------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | GMDViaMBMSByxMB Patch | 1 | Parameters to partially update a group message delivery with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | GMDViaMBMSByxMB | 1 | 200 OK | The group message delivery was modified successfully.
The SCEF shall return an updated data structure of type "GMDViaMBMSByxMB" in the response content. | +| | none | | 204 No Content | The group message delivery was modified successfully, and no content is to be sent in the response message body. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2.5.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.3.2.5.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.3.2.5.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.8.3.2.5.3.5 DELETE + +To cancel a group message delivery, the SCS/AS shall use the HTTP DELETE method on the individual "delivery\_via\_mbms" resource which is indicated by the URI in the Location header of the HTTP POST response: + +The possible response messages from the SCEF, depending on whether the DELETE request is successful or unsuccessful, are shown in table 5.8.3.2.5.3.5-1. + +**Table 5.8.3.2.5.3.5-1: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The group message delivery subscription was cancelled successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2.5.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.8.3.2.5.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.8.3.2.6 Void + +#### 5.8.3.2A Notifications + +##### 5.8.3.2A.1 General + +The notifications provided by the GMDviaMBMSbyxMB API are specified in this clause. + +**Table 5.8.3.2A.1-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|----------------------------------|---------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------| +| GMD via MBMS by xMB Notification | {notificationDestination} | POST | Report a specific group message delivery result to the SCS/AS for a given Transaction Id selected by the SCEF. | + +### 5.8.3.2A.2 GMD via MBMS by xMB Notification + +#### 5.8.3.2A.2.1 Description + +The GMD via MBMS by xMB Notification allows the SCEF report the delivery trigger status to the SCS/AS to indicate whether group message delivery was triggered successful. + +#### 5.8.3.2A.2.2 Target URI + +The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 5.8.3.2A.2.2-1. + +**Table 5.8.3.2A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|-------------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notificationDestination | Link | A URI indicating the notification destination where T8 notification requests shall be delivered.
This URI shall be provided within the field "notificationDestination" in the GMDViaMBMSByxMB type. | + +#### 5.8.3.2A.2.3 Standard Methods + +##### 5.8.3.2A.2.3.1 Notification via POST + +To report the status of the delivery trigger status to the SCS/AS, the SCEF shall use the HTTP POST method on the notification point as follows: + +- the body of the message is encoded in JSON format with the data structure defined in table 5.8.3.1.1.4-1. + +This method shall support the request data structures specified in table 5.8.3.2A.2.3.1-1 and the response data structures and response codes specified in table 5.8.3.2A.2.3.1-2. + +**Table 5.8.3.2A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|-----------------------|-------------|-----------------------------------| +| GMDBByxMBNotification | 1 | The delivery status notification. | + +**Table 5.8.3.2A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Acknowledgement | 1 | 200 OK | The successful acknowledgement of the notification with a body. | +| (None) | | 204 No Content | The successful acknowledgement of the notification without a body. | +| none | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.8.3.2A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.8.3.2A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +#### 5.8.3.2a.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the GMDByxMBNotification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +### 5.8.3.3 Used Features + +The table below defines the features applicable to the GMDviaMBMSbyxMB API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.8.3.3-1: Features used by GMDviaMBMSbyxMB API** + +| Feature Number | Feature | Description | +|----------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 2 | Notification_test_event | The testing of notification connection is supported according to clause 5.2.5.3. | + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification". +Description: A clear textual description of the feature. + +### 5.8.3.4 Error handling + +#### 5.8.3.4.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +#### 5.8.3.4.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the GMDviaMBMSbyxMB API. + +#### 5.8.3.4.3 Application Errors + +The application errors defined for GMDviaMBMSbyxMB API are listed in table 5.8.3.4.3-1. + +**Table 5.8.3.4.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 5.9 ReportingNetworkStatus API + +### 5.9.1 Overview + +The ReportingNetworkStatus API is a RESTful API that allows the SCS/AS to be one-time or continuous notified of the network status in a geographic area. The ReportingNetworkStatus API defines a set of data models, resources and the related procedures for the creation and management of the network status reporting request. The corresponding JSON schema for the representation of the resources and operations defined by the ReportingNetworkStatus API is provided in its complete form in Annex A.9. + +### 5.9.2 Data model + +#### 5.9.2.1 Resource data types + +##### 5.9.2.1.1 Introduction + +This clause defines data structures to be used in resource representations. + +Table 5.9.2.1.1-1 specifies data types re-used by the ReportingNetworkStatus API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the ReportingNetworkStatus API. + +**Table 5.9.2.1.1-1: ReportingNetworkStatus API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|----------------------------------------------------------------------------------------| +| GeographicArea | 3GPP TS 29.572 [42] | Identifies the geographical information of the user(s). | +| CivicAddress | 3GPP TS 29.572 [42] | Identifies the civic address information of the user(s). | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.9.4-1. | + +Table 5.9.2.1.1-2 specifies the data types defined for the ReportingNetworkStatus API. + +**Table 5.9.2.1.1-2: ReportingNetworkStatus API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|------------------------------------|----------------|-------------------------------------------------------------------------------------------------|---------------| +| CongestionType | 5.9.2.3.3 | Represents abstracted values for congestion status. | | +| CongestionValue | 5.9.2.3.2 | Represents the congestion level value | | +| NetStatusRepSubsPatch | 5.9.2.1.3 | Represents the parameters to request the modification of network status reporting subscription. | PatchUpdate | +| NetworkStatusReportingNotification | 5.9.2.2.2 | Represents a network status reporting notification. | | +| NetworkStatusReportingSubscription | 5.9.2.1.2 | Represents a subscription to network status information reporting. | | + +##### 5.9.2.1.2 Type: NetworkStatusReportingSubscription + +This type represents the subscription of reporting the network status. The same structure is used in the subscription request and subscription response. + +**Table 5.9.2.1.2-1: Definition of type NetworkStatusReportingSubscription** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------------|------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| self | Link | 0..1 | Link to the resource "Individual Network Status Reporting subscription". This parameter shall be supplied by the SCEF in HTTP responses. | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7. This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| notificationDestination | Link | 1 | A URI indicating the notification destination where T8 notification requests shall be delivered | | +| requestTestNotification | boolean | 0..1 | Set to true by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. Set to false or omitted otherwise. | Notification_test_event | +| websocketNotifConfig | WebsockNotifConfig | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 5.2.5.4. | Notification_websocket | +| locationArea | LocationArea | 1 | Identifies a location area. It can be either a list of cell IDs, or a list of Tracking Areas, or civic addresses, or a geographic area, or a combination of any of the above. | | +| timeDuration | DateTime | 0..1 | Identifies the time for which a continuous reporting is requested. Shall not be provided for one time reporting case. | | +| thresholdValues | array(CongestionValue) | 0..N | Identifies a list of congestion level(s) with exact value that the SCS/AS requests to be informed of when reached.
(NOTE 2) | | +| thresholdTypes | array(CongestionType) | 0..N | Identifies a list of congestion level(s) with abstracted value that the SCS/AS requests to be informed of when reached.
(NOTE 2) | | + +NOTE 1: Properties marked with a feature as defined in clause 5.9.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. +NOTE 2: thresholdValues and thresholdTypes shall be mutually exclusive. + +### 5.9.2.1.3 Type: NetStatusRepSubsPatch + +This data type represents the parameters to request the modification of network status reporting subscription. + +**Table 5.9.2.1.3-1: Definition of type NetStatusRepSubsPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------------|------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| notificationDestination | Link | 0..1 | A URI indicating the notification destination where T8 notification requests shall be delivered. | | +| locationArea | LocationArea | 0..1 | Identifies a location area. It can be either a list of cell IDs, or a list of Tracking Areas, or civic addresses, or a geographic area, or a combination of any of the above. | | +| timeDuration | DateTimeRm | 0..1 | Identifies the time for which a continuous reporting is requested. Shall not be provided for one time reporting case. | | +| thresholdValues | array(CongestionValue) | 0..N | Identifies a list of congestion level(s) with exact value that the SCS/AS requests to be informed of when reached.
(NOTE 2) | | +| thresholdTypes | array(CongestionType) | 0..N | Identifies a list of congestion level(s) with abstracted value that the SCS/AS requests to be informed of when reached.
(NOTE 2) | | + +NOTE 1: Properties marked with a feature as defined in clause 5.9.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. +NOTE 2: The "thresholdValue" attribute and the "thresholdType" attribute shall be mutually exclusive. + +## 5.9.2.2 Notification data types + +### 5.9.2.2.1 Introduction + +This clause defines data structures to be used in notifications. + +### 5.9.2.2.2 Type: NetworkStatusReportingNotification + +This data type represents a network status reporting notification which is sent from the SCEF to the SCS/AS. + +**Table 5.9.2.2.2-1: Definition of type NetworkStatusReportingNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|----------------|-----------------|-------------|--------------------------------------------------------------------------------------------------------|------------------------| +| subscription | Link | 1 | Link to the subscription resource to which this notification is related. | | +| nsiValue | CongestionValue | 0..1 | Network Status Indicator based on exact value for congestion status received from RCAF(s).
(NOTE 2) | | +| nsiType | CongestionType | 0..1 | Network Status Indicator based on abstracted value for congestion status.
(NOTE 2) | | + +NOTE 1: Properties marked with a feature as defined in clause 5.9.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. +NOTE 2: nsiValue and nsiType shall be mutually exclusive. + +### 5.9.2.3 Referenced simple data types and enumerations + +#### 5.9.2.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +#### 5.9.2.3.2 Simple data types + +The simple data types defined in table 5.9.2.3.2-1 shall be supported. + +**Table 5.9.2.3.2-1: Simple data types** + +| Type name | Description | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CongestionValue | Unsigned integer with valid values between 0 and 31. The value 0 indicates that there is no congestion. The value 1 is the lowest congestion level and value 31 is the highest congestion level. | + +#### 5.9.2.3.3 Enumeration: CongestionType + +The enumeration CongestionType represents abstracted values for congestion status. + +**Table 5.9.2.3.3-1: Enumeration CongestionType** + +| Enumeration value | Description | Applicability
(NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------| +| HIGH | The congestion status is high. | | +| MEDIUM | The congestion status is medium. | | +| LOW | The congestion status is low. | | +| NOTE: Properties marked with a feature as defined in clause 5.9.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +### 5.9.3 Resource structure + +#### 5.9.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-net-stat-report/v1** + +"apiRoot" is set as described in clause 5.2.4. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.9.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|--------------------------------------------------|-------------------------------------------|-------------|-------------------------------------------------------------------------------| +| Network Status Reporting Subscriptions | /{scsAsId}/subscriptions | GET | Read all network status reporting subscription resources for a given SCS/AS. | +| | | POST | Create a new network status reporting subscription resource. | +| Individual Network Status Reporting subscription | /{scsAsId}/subscriptions/{subscriptionId} | GET | Read a network status reporting subscription resource. | +| | | PUT | Update an existing Individual Network Status Reporting Subscription resource. | +| | | PATCH | Modify an existing Individual Network Status Reporting Subscription resource. | +| | | DELETE | Delete an existing continuous network status reporting subscription resource. | + +### 5.9.3.2 Resource: Network Status Reporting Subscriptions + +#### 5.9.3.2.1 Introduction + +This resource allows the SCS/AS to read all active long-term subscriptions related to a network status reporting. + +#### 5.9.3.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-net-stat-report/v1/{scsAsId}/subscriptions + +This resource shall support the resource URI variables defined in table 5.9.3.2.2-1. + +**Table 5.9.3.2.2-1: Resource URI variables for resource "Network Status Reporting Subscriptions"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +#### 5.9.3.2.3 Resource methods + +##### 5.9.3.2.3.1 GET + +The GET method allows to read all active network status reporting subscriptions for a given SCS/AS. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.9.3.2.3.1-1 and table 5.9.3.2.3.1-2. + +**Table 5.9.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.9.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-------------------------------------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(NetworkStatusReportingSubscription) | 0..N | 200 OK | The information about the network status reporting subscriptions related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.9.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.9.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.9.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.9.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.9.3.2.3.4 POST + +The POST method creates a new network status reporting subscription resource for a given SCS/AS. The SCS/AS shall initiate the HTTP POST request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.9.3.2.3.4-1 and table 5.9.3.2.3.4-2. + +**Table 5.9.3.2.3.4-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.9.3.2.3.4-2: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|-------------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| | NetworkStatusReporting Subscription | 1 | Parameters to register a subscription to request notifications about network status information report with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NetworkStatusReporting Subscription | 1 | 201
Created | The subscription was created successfully.
The URI of the created resource shall be returned in the "Location" HTTP header. | +| | ProblemDetails | 0..1 | 403
Forbidden | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.9.5.3. + +**Table 5.9.3.2.3.4-3: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-net-stat-report/v1/{scsAsId}/subscriptions/{subscriptionId} | + +#### 5.9.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.9.3.3 Resource: Individual Network Status Reporting Subscription + +#### 5.9.3.3.1 Introduction + +This resource allows the SCS/AS to request for being notified about the network status using a long-term subscription. + +#### 5.9.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-net-stat-report/v1/{scsAsId}/subscriptions/{subscriptionId} + +This resource shall support the resource URI variables defined in table 5.9.3.3.2-1. + +**Table 5.9.3.3.2-1: Resource URI variables for resource "Individual Network Status Reporting Subscription"** + +| Name | Data type | Definition | +|----------------|------------------|-----------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| subscriptionId | string | Identifier of the subscription resource. The subscriptionId corresponds to the stage 2 TLTRI. | + +#### 5.9.3.3.3 Resource methods + +##### 5.9.3.3.3.1 GET + +The GET method allows to read an active network status reporting subscription resource. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.9.3.3.3.1-1 and table 5.9.3.3.3.1-2. + +**Table 5.9.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.9.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------------------------------------------------------------------------------------|-------------------------------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NetworkStatusReporting Subscription | 1 | 200 OK | The subscription information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. | | | | | + +**Table 5.9.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.9.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.9.3.3.3.2 PUT + +The PUT method updates an existing subscription resource to update a subscription. The SCS/AS shall initiate the HTTP PUT request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.9.3.3.3.2-1 and table 5.9.3.3.3.2-2. + +**Table 5.9.3.3.3.2-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.9.3.3.3.2-2: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|-------------------------------------|--------------------|---------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NetworkStatusReporting Subscription | 1 | Parameters to update a subscription to request notifications about network status information report with the SCEF. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NetworkStatusReporting Subscription | 1 | 200 OK | The subscription was updated successfully. | +| | none | | 204 No Content | The subscription was updated successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.9.3.3.3.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.9.3.3.3.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.9.3.3.3.3 PATCH + +The PATCH method modifies an existing subscription resource to modify a subscription. The SCS/AS shall initiate the HTTP PATCH request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures and response codes specified in the table 5.9.3.3.3.3-1 and table 5.9.3.3.3.3-2. + +**Table 5.9.3.3.3.3-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | Cardinality | Remarks | +|-------------|------------------|--------------------|----------------| +| n/a | | | | + +**Table 5.9.3.3.3.3-2: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|-------------------------------------|--------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NetStatusRepSubsPatch | 1 | Contains the parameters to modify an existing Individual Network Status Reporting Subscription resource. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NetworkStatusReporting Subscription | 1 | 200 OK | The modification of the Individual Network Status Reporting Subscription resource was successfull.

The SCEF shall return an updated representation of the resource within the NetworkStatusReportingSubscription data structure in the response message body. | +| | n/a | | 204 No Content | The modification of the Individual Network Status Reporting Subscription resource was successfull and no content is to be sent in the response message body. | +| | n/a | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | n/a | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | + +NOTE 1: The mandatory HTTP error status codes for the HTTP PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.9.3.3.3.3-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.9.3.3.3.3-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**5.9.3.3.3.4 POST** + +This HTTP method is not supported for the resource. + +**5.9.3.3.3.5 DELETE** + +The DELETE method deletes the resource and terminates the related network status reporting subscription. The SCS/AS shall initiate the HTTP DELETE request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.9.3.3.3.5-1 and table 5.9.3.3.3.5-2. + +**Table 5.9.3.3.3.5-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|------------------|--------------------|----------------| +| none specified | | | | + +**Table 5.9.3.3.3.5-2: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The subscription was terminated successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.9.3.3.3.5-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.9.3.3.3.5-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.9.3.4 Void + +## 5.9.3A Notifications + +### 5.9.3A.1 General + +The notifications provided by the ReportingNetworkStatus API are specified in this clause. + +**Table 5.9.3A-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|---------------------------------------|---------------------------|---------------------------------|---------------------------------------------------------------------------------| +| Network Status Reporting Notification | {notificationDestination} | POST | Report a detected network status for a subscription from the SCEF to the SCS/AS | + +## 5.9.3A.2 Network Status Reporting Notification + +### 5.9.3A.2.1 Description + +The Network Status Reporting Notification allows the SCEF to send notifications about the detected network status to the SCS/AS. + +### 5.9.3A.2.2 Target URI + +The Callback URI "{notification\_uri}" shall be used with the callback URI variables defined in table 5.9.3A.2.2-1. + +**Table 5.9.3A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|-------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------| +| notificationDestination | Link | Callback reference provided by the SCS/AS during creation or modification of the network status reporting subscription. | + +### 5.9.3A.2.3 Standard Methods + +#### 5.9.3A.2.3.1 Notification via POST + +The HTTP POST method reports the detected network status for a network status subscription. The SCEF shall initiate the HTTP POST request message and the SCS/AS shall respond to the message. + +This method shall support the request data structures specified in table 5.9.3A.2.3.1-1 and the response data structures and response codes specified in table 5.9.3A.2.3.1-2. + +**Table 5.9.3A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|------------------------------------|-------------|-----------------------------------------------------------------| +| NetworkStatusReportingNotification | 1 | The network status reporting notification provided by the SCEF. | + +**Table 5.9.3A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| none | | 204 No Content | The network status reporting notification is received successfully. | +| none | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.9.3A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.9.3A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +#### 5.9.3A.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the NetworkStatusReportingNotification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +### 5.9.4 Used Features + +The table below defines the features applicable to the ReportingNetworkStatus API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.9.4-1: Features used by ReportingNetworkStatus API** + +| Feature Number | Feature | Description | +|----------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 2 | Notification_test_event | The testing of notifications connections is supported according to clause 5.2.5.3. | +| 3 | PatchUpdate | Indicates the support of enhancements to the northbound interfaces (e.g. support the partial modification of an existing subscription resource). | + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification". +Description: A clear textual description of the feature. + +### 5.9.5 Error handling + +#### 5.9.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +#### 5.9.5.2 Protocol Errors + +In this release of the specification, there are no additional protocol errors applicable for the ReportingNetworkStatus API. + +#### 5.9.5.3 Application Errors + +The application errors defined for the ReportingNetworkStatus API are listed in table 5.9.5.3-1. + +**Table 5.9.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|-------------------|------------------|------------------------------| +| QUOTA_EXCEEDED | 403 Forbidden | Not enough quota for SCS/AS. | + +## 5.10 CpProvisioning API + +### 5.10.1 Overview + +The CpProvisioning API is a RESTful API that allows the SCS/AS to add, change or delete the communication pattern parameter sets of the UE. The CpProvisioning API defines a set of data models, resources and the related procedures for the creation and management of the resources for communication pattern parameter provisioning. The corresponding JSON schema for the representation of the resources and operations defined by the CpProvisioning API is provided in its complete form in Annex A.10. + +### 5.10.2 Data model + +#### 5.10.2.1 Resource data types + +##### 5.10.2.1.1 Introduction + +This clause defines data structures to be used in resource representations. + +Table 5.10.2.1.1-1 specifies data types re-used by the CpProvisioning API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the CpProvisioning API. + +**Table 5.10.2.1.1-1: CpProvisioning API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|-----------------------------------------------------------------------------------------| +| Dnn | 3GPP TS 29.571 [45] | Identifies a DNN. | +| IpAddr | 3GPP TS 29.571 [45] | UE IP Address. | +| MacAddr48 | 3GPP TS 29.571 [45] | MAC Address. | +| NetworkAreaInfo | 3GPP TS 29.554 [50] | Identifies a network area information. | +| Snssai | 3GPP TS 29.571 [45] | Identifies the S-NSSAI. | +| TimeWindow | 5.2.1.2.3 | Identifies the time window from the start time to the end time. | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.10.4-1. | + +Table 5.10.2.1.1-2 specifies the data types defined for the CpProvisioning API. + +**Table 5.10.2.1.1-2: CpProvisioning API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|----------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| AppExpUeBehaviour | 5.10.2.2.6 | Contains the Application Specific Expected UE Behaviour parameters. | AppExpUeBehaviour | +| BatteryIndication | 5.10.2.3.6 | Represents the type of power consumption. | | +| CommunicationIndicator | 5.10.2.3.3 | Represents the communication type used by the UE. | | +| CpFailureCode | 5.10.2.3.5 | Represents the failure reason of the CP parameter provisioning. | | +| CpInfo | 5.10.2.1.2 | Represents the resources for communication pattern parameter provisioning. | | +| CpParameterSet | 5.10.2.2.2 | Represents an offered communication pattern parameter set. | | +| CpReport | 5.10.2.2.4 | Represents a CP report indicating the CP set identifier(s) which CP parameter(s) are not added or modified successfully and the corresponding failure cause(s). | | +| ScheduledCommunicationTime | 5.10.2.2.3 | Represents an offered scheduled communication time. | | +| ScheduledCommunicationType | 5.10.2.3.8a | Represents the type of scheduled communication. | ScheduledCommType_5G | +| StationaryIndication | 5.10.2.3.4 | Indicates whether the UE is stationary or mobile. | | +| TrafficProfile | 5.10.2.3.7 | Represents the type of data transmission. | | +| UmtLocationArea5G | 5.10.2.2.5 | Represents the user location area describing the UE moving trajectory. | ExpectedUMT_5G,
ExpectedUmtTime_5G | + +#### 5.10.2.1.2 Type: CpInfo + +This type represents the resources for communication pattern parameter provisioning. The same structure is used in the subscription request and subscription response. + +**Table 5.10.2.1.2-1: Definition of type CplInfo** + +| Attribute name | Data type | Cardinality | Description | Applicability
(NOTE 2) | +|-------------------|---------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| self | Link | 0..1 | Link to the resource "Individual CP Provisioning Subscription".
This parameter shall be supplied by the SCEF in HTTP responses. | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7.
This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| mtcProviderId | string | 0..1 | Identifies the MTC Service Provider and/or MTC Application. (NOTE 3) | | +| dnn | Dnn | 0..1 | Identifies a DNN, a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only. | UEId_retrieval | +| externalId | ExternalId | 0..1 | Each element uniquely identifies a user as defined in Clause 4.6.2 of 3GPP TS 23.682 [2].

The attribute may also be present in the CP provisioning subscription response message, if the "UEId_retrieval" feature is supported and the corresponding request message includes the "uelpAddr" attribute or the "ueMacAddr" attribute.
(NOTE 1) | | +| msisdn | Msisdn | 0..1 | Each element identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE 1) | | +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in Clause 4.6.2 of 3GPP TS 23.682 [2].
(NOTE 1) | | +| cpParameterSets | map(CpParameterSet) | 1..N | Identifies a set of CP parameter information that may be part of this CpInfo structure.
Any string value can be used as a key of the map. | | +| cpReports | map(CpReport) | 0..N | Supplied by the SCEF and contains the CP set identifiers for which CP parameter(s) are not added or modified successfully. The failure reason is also included.
Each element provides the related information for one or more CP set identifier(s) and is identified in the map via the failure identifier as key.
(NOTE 4). | | +| snssai | Snssai | 0..1 | Indicate the S-NSSAI. | UEId_retrieval | +| uelpAddr | lpAddr | 0..1 | UE IP address. | UEId_retrieval | +| ueMacAddr | MacAddr48 | 0..1 | UE MAC address. | UEId_retrieval | + +NOTE 1: One of the properties "externalId", "msisdn" or "externalGroupId" shall be included. + +NOTE 2: Properties marked with a feature as defined in clause 5.10.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +NOTE 3: The SCEF should check received MTC provider identifier and then the SCEF may: +- override it with local configured value and send it to HSS; + +- send it directly to the HSS; or +- reject the communication pattern parameter provisioning request. + +NOTE 4: The failure identifier is a string encoded map key. + +## 5.10.2.2 Referenced structured data types + +### 5.10.2.2.1 Introduction + +This clause defines structured data types that are referenced from data structures defined in the previous clauses. + +### 5.10.2.2.2 Type: CpParameterSet + +This data type represents an offered communication pattern parameter set sent from the SCC/AS to the SCEF. + +**Table 5.10.2.2.2-1: Definition of type CpParameterSet** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|--------------------------------|----------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| setId | string | 1 | SCS/AS-chosen correlator provided by the SCS/AS in the request to create a resource for CP parameter set(s).
(NOTE 4) | | +| self | Link | 0..1 | Link to the resource "Individual CP set Provisioning". This parameter shall be supplied by the SCEF in HTTP responses. | | +| validityTime | DateTime | 0..1 | Identifies when the CP parameter set expires and shall be deleted. If absent, it indicates that there is no expiration time for this CP parameter set. | | +| periodicCommunicationIndicator | Communication Indicator | 0..1 | Identifies whether UE communicates periodically or on demand. | | +| communicationDurationTime | DurationSec | 0..1 | Identifies duration time of periodic communication. | | +| periodicTime | DurationSec | 0..1 | Identifies interval time of periodic communication. | | +| scheduledCommunicationTime | ScheduledCommunicationTime | 0..1 | Identifies time zone and day of the week when the UE is available for communication. | | +| scheduledCommunicationType | ScheduledCommunicationType | 0..1 | Indicates the Scheduled Communication Type.
May only be present if the "scheduledCommunicationTime" attribute is provided. | ScheduledCommType_5G | +| stationaryIndication | StationaryIndication | 0..1 | Identifies whether the UE is stationary or mobile. | | +| batteryInds | array(BatteryIndication) | 0..N | Indicates the power consumption type(s) of the UE.
(NOTE 3) | | +| trafficProfile | TrafficProfile | 0..1 | Identifies the type of data transmission. | | +| expectedUmts | array(UmtLocationArea5G) | 0..N | Identifies the UE's expected geographical movement. The attribute is only applicable in 5G.
(NOTE 2) | ExpectedUMT_5G
ExpectedUmtTime_5G | +| expectedUmtDays | DayOfWeek | 0..6 | Identifies the day of the week. If absent, it indicates every day of the week. | ExpectedUmtTime_5G | +| expectedUmtDaysAdd | array(DayOfWeek) | 0..5 | Identifies the additional day(s) of the week.
(NOTE 5) | ExpectedUmtTime_Add | +| appExpUeBehvs | array(AppExpUeBehaviour) | 0..N | Contains the Application Specific Expected UE Behaviour parameters. | AppExpUeBehaviour | +| confidenceLevel | string | 0..1 | When present, this IE indicates the Confidence level for the associated Expected UE Behaviour parameter.

The value shall be between 0.01 and 1.00 with a step size of 0.01, represented as string.

If not present, confidence level 1.00 applies.

Pattern: '^[0]\.[0-9]{2}[1.00]\$' | ConfAccuLevels | +| accuracyLevel | string | 0..1 | When present, this IE indicates the accuracy level for the associated Expected UE Behaviour parameter.

The value shall be between 0.01 and 1.00 with a step size of 0.01, represented as string.

If not present, accuracy level 1.00 applies.

Pattern: '^[0]\.[0-9]{2}[1.00]\$' | ConfAccuLevels | + +| | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | Properties marked with a feature as defined in clause 5.10.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | +| NOTE 2: | The first instance of the attribute represents the start of the location, and the last one represents the stop of the location. | +| NOTE 3: | If "BATTERY_RECHARGE" is provided, "BATTERY_NO_RECHARGE" shall not be provided simultaneously, vice versa; If "BATTERY_REPLACE" is provided, "BATTERY_NO_REPLACE" shall not be provided simultaneously, vice versa; If "NO_BATTERY" is provided, any value indicating UE powered with battery shall not be provided simultaneously, vice versa. | +| NOTE 4: | A setId can only belong to one "Individual CP Provisioning Subscription" resource. | +| NOTE 5: | The "expectedUmtDaysAdd" attribute may only be provided to indicate the additional day(s) if the "expectedUmtDays" attribute is also provided. | + +#### 5.10.2.2.3 Type: ScheduledCommunicationTime + +This data type represents an offered scheduled communication time. + +**Table 5.10.2.2.3-1: Definition of type ScheduledCommunicationTime** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------|-----------------------------------------------------------------------------------|----------------------| +| daysOfWeek | array(DayOfWeek) | 0..6 | Identifies the day(s) of the week. If absent, it indicates every day of the week. | | +| timeOfDayStart | TimeOfDay | 0..1 | Identifies the start time of the day. | | +| timeOfDayEnd | TimeOfDay | 0..1 | Identifies the end time of the day. | | +| NOTE: Properties marked with a feature as defined in subclause 5.10.4 are applicable as described in subclause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | + +#### 5.10.2.2.4 Type: CpReport + +This type represents a CP report to indicate the CP set identifier(s) which CP parameter(s) are not added or modified successfully and corresponding failure reason. + +**Table 5.10.2.2.4-1: Definition of type CpReport** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------|--------------------------------------------------------------------------------------------------|----------------------| +| setIds | array(string) | 0..N | Identifies the CP set identifier(s) which CP parameter(s) are not added or modified successfully | | +| failureCode | CpFailureCode | 1 | Identifies the failure reason | | +| NOTE: Properties marked with a feature as defined in subclause 5.10.4 are applicable as described in subclause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | + +#### 5.10.2.2.5 Type: UmtLocationArea5G + +This data type represents the user location area describing the UE moving trajectory which is sent from the AF. + +**Table 5.10.2.2.5-1: Definition of the UmtLocationArea5G data Type** + +| Attribute name | Data type | Cardinality | Description | Applicability
(NOTE 1) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|--------------------------------------------------------------------------|---------------------------| +| umtTime | TimeOfDay | 0..1 | This IE identifies the time of the day when the UE arrives the location. | ExpectedUmtTime_5G | +| umtDuration | DurationSec | 0..1 | This IE identifies the time duration the UE stays in the location. | ExpectedUmtTime_5G | +| NOTE 1: Properties marked with a feature as defined in clause 5.10.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | +| NOTE 2: This data type also contains all the properties defined for LocationArea5G data type, these properties are applicable for ExpectedUMT_5G. | | | | | + +## 5.10.2.2.6 Type: AppExpUeBehaviour + +**Table 5.10.2.2.6-1: Definition of type AppExpUeBehaviour** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|---------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| appId | string | C | 0..1 | Indicates the Application Identifier.
(NOTE 1) | | +| expPduSesInacTm | TimeWindow | O | 0..1 | Identifies the expected PDU Session Inactivity time during which the UE will not have traffic related to the application. | | +| flowDescriptions | array(string) | C | 0..N | Represents a 3-tuple with protocol, server ip and server port for UL/DL application traffic. The content of the string has the same encoding as the IPFilterRule AVP value as defined in IETF RFC 6733 [46].
(NOTE 1) | | +| confidenceLevel | string | O | 0..1 | When present, this IE indicates the Confidence level for the associated Application-Specific Expected UE Behaviour parameter.

The value shall be between 0.01 and 1.00 with a step size of 0.01, represented as string.

If not present, confidence level 1.00 applies.

Pattern: '^[0]{1}[0-9]{2}[1.00]' | | +| accuracyLevel | string | O | 0..1 | When present, this IE indicates the accuracy level for the associated Application-Specific Expected UE Behaviour parameter.

The value shall be between 0.01 and 1.00 with a step size of 0.01, represented as string.

If not present, accuracy level 1.00 applies.

Pattern: '^[0]{1}[0-9]{2}[1.00]' | | +| failureCode | CpFailureCode | O | 0..1 | Identifies the failure reason for the Application-Specific Expected UE Behaviour parameter is not added or modified successfully.

If absent, the value of the "failureCode" attribute in the higher-level "CpInfo" data type shall be used.
(NOTE 3) | | +| validityTime | DateTime | O | 0..1 | Identifies when the Application-Specific Expected UE Behaviour parameter expires.

If absent, the value of the "validityTime" attribute in the higher-level "CpParameterSet" data type shall be used.
(NOTE 2) | | + +NOTE 1: One of the "appId" attribute or "flowDescriptions" attribute shall be included. +NOTE 2: The attribute if provided, take precedence over the "validityTime" attribute in the higher-level "CpParameterSet" data type. + +NOTE 3: The attribute if provided, take precedence over the "failureCode" attribute in the higher-level "CplInfo" data type. + +### 5.10.2.3 Referenced simple data types and enumerations + +#### 5.10.2.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +#### 5.10.2.3.2 Simple data types + +The simple data types defined in table 5.10.2.3.2-1 shall be supported. + +**Table 5.10.2.3.2-1: Simple data types** + +| Type name | Description | +|-----------|-------------| +| | | +| | | + +#### 5.10.2.3.3 Enumeration: CommunicationIndicator + +**Table 5.10.2.3.3-1: Enumeration CommunicationIndicator** + +| Enumeration value | Description | Applicability (NOTE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|----------------------| +| PERIODICALLY | Identifies the UE communicates periodically | | +| ON_DEMAND | Identifies the UE communicates on demand | | +| NOTE: Properties marked with a feature as defined in clause 5.10.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.10.2.3.4 Enumeration: StationaryIndication + +**Table 5.10.2.3.4-1: Enumeration StationaryIndication** + +| Enumeration value | Description | Applicability (NOTE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------| +| STATIONARY | Identifies the UE is stationary | | +| MOBILE | Identifies the UE is mobile | | +| NOTE: Properties marked with a feature as defined in clause 5.10.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.10.2.3.5 Enumeration: CpFailureCode + +The enumeration FailureCode represents the failure reason of the CP parameter provisioning. + +**Table 5.10.2.3.5-1: Enumeration CpFailureCode** + +| Enumeration value | Description | Applicability (NOTE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| MALFUNCTION | This value indicates that something functions wrongly in CP parameter provisioning or the CP parameter provisioning does not function at all. | | +| SET_ID_DUPLICATED | The received CP set identifier(s) are already provisioned. | | +| OTHER_REASON | Other reason unspecified. | | +| CONFIDENCE_LEVEL_NOT_SUFFICIENT | This value indicate that the confidence level provided is not sufficient | ConfAccuLevels | +| ACCURACY_LEVEL_NOT_SUFFICIENT | This value indicate that the accuracy level provided is not sufficient | ConfAccuLevels | +| NOTE: Properties marked with a feature as defined in clause 5.10.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.10.2.3.6 Enumeration: BatteryIndication + +The enumeration BatteryIndication represents the type of power consumption. + +**Table 5.10.2.3.6-1: Enumeration BatteryIndication** + +| Enumeration value | Description | Applicability (NOTE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|----------------------| +| BATTERY_RECHARGE | UE powered with rechargeable battery. | | +| BATTERY_REPLACE | UE powered with replaceable battery. | | +| BATTERY_NO_RECHARGE | UE powered with no rechargeable battery. | | +| BATTERY_NO_REPLACE | UE powered with no replaceable battery. | | +| NO_BATTERY | UE not battery powered. | | +| NOTE: Properties marked with a feature as defined in clause 5.10.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.10.2.3.7 Enumeration: TrafficProfile + +The enumeration TrafficProfile represents the type of data transmission. + +**Table 5.10.2.3.7-1: Enumeration TrafficProfile** + +| Enumeration value | Description | Applicability (NOTE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|----------------------| +| SINGLE_TRANS_UL | Uplink single packet transmission. | | +| SINGLE_TRANS_DL | Downlink single packet transmission. | | +| DUAL_TRANS_UL_FIRST | Dual packet transmission, firstly uplink packet transmission with subsequent downlink packet transmission. | | +| DUAL_TRANS_DL_FIRST | Dual packet transmission, firstly downlink packet transmission with subsequent uplink packet transmission. | | +| MULTI_TRANS | Multiple packet transmission. | | +| NOTE: Properties marked with a feature as defined in clause 5.10.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | + +#### 5.10.2.3.8A Enumeration: ScheduledCommunicationType + +The enumeration ScheduledCommunicationType represents the type of scheduled communication. + +**Table 5.10.2.3.8A-1: Enumeration ScheduledCommunicationType** + +| Enumeration value | Description | +|-------------------|----------------| +| DOWNLINK | Downlink only | +| UPLINK | Uplink only | +| BIDIRECTIONAL | Bi-directional | + +## 5.10.3 Resource structure + +### 5.10.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-cp-parameter-provisioning/v1** + +"apiRoot" is set as described in clause 5.2.4. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.10.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|-----------------------------------------|----------------------------------------------------------------------------------|-------------|--------------------------------------------------------------------------------------| +| CP provisioning Subscriptions | /{scsAsId}/subscriptions | GET | Read all active CP parameter provisioning subscription resources for a given SCS/AS. | +| | | POST | Create a new subscription resource of provisioning CP parameter set(s). | +| Individual CP Provisioning Subscription | /{scsAsId}/subscriptions/{subscriptionId} | GET | Read a CP parameter provisioning subscription resource. | +| | | PUT | Modify a CP parameter provisioning subscription resource. | +| | | DELETE | Delete a CP parameter provisioning subscription resource. | +| Individual CP set Provisioning | /{scsAsId}/subscriptions/{subscriptionId}/cpSets/{setId}

(NOTE 1, NOTE 2) | PUT | Update CP at individual CP set(s) level associated with a CP parameter set Id. | +| | | GET | Read CP at individual CP set(s) level associated with a CP parameter set Id. | +| | | DELETE | Delete CP at individual CP set(s) level associated with a CP parameter set Id. | + +NOTE 1: This setId as a resource identifier is not necessarily identical as the CP parameter set Id received from the SCS/AS. +NOTE 2: The path segment "cpSets" does not follow the related naming convention defined in clause 5.2.4. The path segment is however kept as currently defined in this specification for backward compatibility considerations. + +### 5.10.3.2 Resource: CP Provisioning Subscriptions + +#### 5.10.3.2.1 Introduction + +This resource allows the SCS/AS to read all active long-term transactions related to CP parameter provisioning resource management. + +#### 5.10.3.2.2 Resource definition + +Resource URI: **{apiRoot}/3gpp-cp-parameter-provisioning/v1/{scsAsId}/subscriptions** + +This resource shall support the resource URI variables defined in table 5.10.3.2.2-1. + +**Table 5.10.3.2.2-1: Resource URI variables for resource "CP Provisioning Subscriptions"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +### 5.10.3.2.3 Resource methods + +#### 5.10.3.2.3.1 GET + +The GET method allows to read all active subscriptions for a given SCS/AS. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.10.3.2.3.1-1 and table 5.10.3.2.3.1-2. + +**Table 5.10.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.10.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(CplInfo) | 0..N | 200 OK | The subscription information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.10.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.10.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.10.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.10.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.10.3.2.3.4 POST + +The POST method allows to create subscription for a given SCS/AS. The SCS/AS shall initiate the HTTP POST request message and the SCEF shall respond to the message. + +This method shall support request and response data structures, and response codes, as specified in the table 5.10.3.2.3.4-1. + +**Table 5.10.3.2.3.4-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | CpInfo | 1 | Change information in CP parameter set. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | CpInfo | 1 | 201 Created | The subscription was created successfully.
The SCEF shall return the created subscription in the response content. CpReport may be included to provide detailed failure information for some CP sets. | +| | array(CpReport) | 1..N | 500 Internal Server Error | The CP parameters for all CP sets were not created successfully. CpReport is included with detailed information. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | +| | ProblemDetails | 0..1 | 404 Not Found | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. +NOTE 2: Failure causes are described in clause 5.10.5. + +**Table 5.10.3.2.3.4-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-cp-parameter-provisioning/v1/{scsAsId}/subscriptions/{subscriptionId} | + +#### 5.10.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.10.3.3 Resource: Individual CP Provisioning Subscription + +#### 5.10.3.3.1 Introduction + +This resource allows the SCS/AS to manage resources for CP parameter provisioning using a subscription Id. + +#### 5.10.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-cp-parameter-provisioning/v1/{scsAsId}/subscriptions/{subscriptionId} + +This resource shall support the resource URI variables defined in table 5.10.3.3.2-1. + +**Table 5.10.3.3.2-1: Resource URI variables for resource "Individual CP Provisioning Subscription"** + +| Name | Data type | Definition | +|----------------|-----------|-----------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| subscriptionId | string | Identifier of the subscription resource. The subscriptionId corresponds to the stage 2 TLTRI. | + +### 5.10.3.3.3 Resource methods + +#### 5.10.3.3.3.1 GET + +The GET method allows to read the subscription for a given SCS/AS and subscription Id. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.10.3.3.3.1-1 and table 5.10.3.3.3.1-2. + +**Table 5.10.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.10.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | Response codes | | +| Response body | CplInfo | 1 | 200 OK | The subscription information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.10.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.10.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.10.3.3.3.2 PUT + +The PUT method allows to change (add/update/remove) one or more CP parameter set(s) resource(s). The SCS/AS shall initiate the HTTP PUT request message and the SCEF shall respond to the message. + +This method shall support request and response data structures, and response codes, as specified in the table 5.14.3.3.3.2-1. + +**Table 5.10.3.3.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | CpInfo | 1 | Change information in CP parameter set(s). | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | CpInfo | 1 | 200 OK | The subscription was modified successfully.
The SCEF shall return an updated subscription in the response content. CpReport may be included to provide detailed failure information for some CP sets. | +| | none | | 204 No Content | The subscription was modified successfully and no content is to be sent in the response message body. | +| | array(CpReport) | 1..N | 500 Internal Server Error | The CP parameters for all CP sets were not created successfully. CpReport is included with detailed information. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.10.3.3.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.10.3.3.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.10.3.3.3.3 PATCH + +This HTTP method is not supported for the resource. + +## 5.10.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +### 5.10.3.3.3.5 DELETE + +The DELETE method allows to remove an active subscription. The SCS/AS shall initiate the HTTP DELETE request message and the SCEF shall respond to the message. + +This method shall support request and response data structures, and response codes, as specified in the table 5.10.3.3.3.5-1. + +**Table 5.10.3.3.3.5-1.: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The subscription was deleted successfully. The content shall be empty. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.10.3.3.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.10.3.3.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.10.3.4 Resource: Individual CP Set Provisioning + +### 5.10.3.4.1 Introduction + +This resource allows the SCS/AS to manage resources for CP parameter set provisioning associated with a CP parameter set Id. + +### 5.10.3.4.2 Resource definition + +Resource URI: {apiRoot}/3gpp-cp-parameter-provisioning/v1/{scsAsId}/subscriptions/{subscriptionId}/cpSets/{setId} + +This resource shall support the resource URI variables defined in table 5.10.3.3.2-1. + +**Table 5.10.3.3.2-1: Resource URI variables for resource "Individual CP Set Provisioning"** + +| Name | Data type | Definition | +|----------------|-----------|------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| subscriptionId | string | Identifier of the subscription resource. | +| setId | string | Identifier of the CP parameter set | + +### 5.10.3.4.3 Resource methods + +#### 5.10.3.4.3.1 GET + +The GET method allows to read a CP parameter set resource. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.10.3.4.3.1-1 and table 5.10.3.4.3.1-2. + +**Table 5.10.3.4.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.10.3.4.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|----------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | CpParameterSet | 1 | 200 OK | The subscription information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.10.3.4.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.10.3.4.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.10.3.4.3.2 PUT + +The PUT method allows to update a CP parameter set resource. The SCS/AS shall initiate the HTTP PUT request message and the SCEF shall respond to the message. + +This method shall support request and response data structures, and response codes, as specified in the table 5.10.3.4.3.2-1. + +**Table 5.10.3.4.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|----------------|-------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | CpParameterSet | 1 | Change information in CP parameter set. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | CpParameterSet | 1 | 200 OK | The CP parameter set resource was modified successfully.
The SCEF shall return an updated CP parameter set resource in the response content. | +| | none | | 204 No Content | The CP parameter set resource was modified successfully and no content is to be sent in the response message body. | +| | CpReport | 1 | 409 Conflict | The CP parameters for the CP set were not updated successfully, applicable for error SET_ID_DUPLICATED in table 5.10.2.3.5-1. | +| | CpReport | 1 | 500 Internal Server Error | The CP parameters for the CP set were not updated successfully, applicable for other errors in table 5.10.2.3.5-1. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.10.3.4.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.10.3.4.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.10.3.4.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.10.3.4.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.10.3.4.3.5 DELETE + +The DELETE method allows to remove an active subscription. The SCS/AS shall initiate the HTTP DELETE request message and the SCEF shall respond to the message. + +This method shall support request and response data structures, and response codes, as specified in the table 5.10.3.4.3.5-1. + +**Table 5.10.3.4.3.5-1.: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The subscription was deleted successfully. The content shall be empty. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.10.3.4.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.10.3.4.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.10.4 Used Features + +The table below defines the features applicable to the CpProvisioning API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.10.4-1: Features used by CpProvisioning API** + +| Feature Number | Feature | Description | +|----------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | ExpectedUMT_5G | The UE's expected geographical movement is supported. This feature may only be supported in 5G. | +| 2 | ExpectedUmtTime_5G | The UE's expected geographical movement with recurrence time is supported. This feature requires the ExpectedUMT_5G feature support and may only be supported in 5G. | +| 3 | ScheduledCommType_5G | Support of scheduled communication type. This feature may only be supported in 5G. | +| 4 | UEId_retrieval | This feature supports AF specific UE ID retrieval. The feature is not applicable to pre-5G (e.g. 4G). | +| 5 | ExpectedUmtTime_Add | This feature supports expected UMT days indication. This feature requires the ExpectedUmtTime_5G feature support. | +| 6 | AppExpUeBehaviour | This feature indicates the support of Application-Specific Expected UE Behaviour parameters. The feature is not applicable to pre-5G (e.g. 4G). | +| 7 | ConfAccuLevels | This feature indicates the support of confidence and accuracy levels for the parameters provisioned. The feature is not applicable to pre-5G (e.g. 4G). | + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification". +Description: A clear textual description of the feature. + +## 5.10.5 Error handling + +### 5.10.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.10.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CpProvisioning API. + +### 5.10.5.3 Application Errors + +The application errors defined for CpProvisioning API are listed in table 5.10.5.3-1. + +**Table 5.10.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------------------|------------------|-----------------------------------------------------------------------------------------------|----------------| +| REQUEST_NOT_AUTHORIZED | 403 Forbidden | Indicates that the the AF specific UE ID retrieval request is not authorized. | UEId_retrieval | +| UE_ID_NOT_AVAILABLE | 404 Not Found | Indicates that the AF specific UE ID is not available. | UEId_retrieval | +| UE_NOT_FOUND | 404 Not Found | Indicates that the requested UE address is not found. | UEId_retrieval | +| CONFIDENCE_LEVEL_OUT_OF_RANGE | 403 Forbidden | Confidence Level of the Expected UE Behaviour Parameter is out or range (e.g. <0.00 or >1.00) | ConfAccuLevels | +| ACCURACY_LEVEL_OUT_OF_RANGE | 403 Forbidden | Confidence Level of the Expected UE Behaviour Parameter is out or range (e.g. <0.00 or >1.00) | ConfAccuLevels | + +## 5.11 PfdManagement API + +### 5.11.1 Overview + +The PfdManagement API allows the SCS/AS to manage the PFDs via the SCEF. The PfdManagement API defines a set of data models, resources and the related procedures for the creation and management of the PFD management request. The corresponding JSON schema for the representation of the resources and operations defined by the PfdManagement API is provided in its complete form in Annex A.11. + +### 5.11.2 Data model + +#### 5.11.2.1 Resource data types + +##### 5.11.2.1.1 Introduction + +This clause defines data structures to be used in resource representations. + +Table 5.11.2.1.1-1 specifies data types re-used by the PfdManagement API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the PfdManagement API. + +**Table 5.11.2.1.1-1: PfdManagement API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|-----------------------------------------------------------------------------------------| +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.11.4-1. | +| Dnai | 3GPP TS 29.571 [45] | DNAI | + +Table 5.11.2.1.1-2 specifies the data types defined for the PfdManagement API. + +**Table 5.11.2.1.1-2: PfdManagement API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|-----------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| DomainNameProtocol | 5.11.2.2.4 | Indicates the additional protocol and protocol field for domain names to be matched. | DomainNameProtocol | +| FailureCode | 5.11.2.2.3 | Represents the failure reason of the PFD management. | | +| Pfd | 5.11.2.1.4 | Represents a PFD for an external Application Identifier. | | +| PfdData | 5.11.2.1.3 | Represents a PFD request to add, update or remove PFD(s) for one external application identifier. | | +| PfdManagement | 5.11.2.1.2 | Represents a PFD management resource for a PFD management request. | | +| PfdManagementPatch | 5.11.2.1.7 | Represents the parameters to request the modification of a PFD management transaction resource. | PatchUpdate | +| PfdReport | 5.11.2.1.5 | Represents a PFD report indicating the external application identifier(s) which PFD(s) are not added or modified successfully and the corresponding failure cause(s). | | +| UserPlaneLocationArea | 5.11.2.1.6 | Represents location area(s) of the user plane functions which are unable to enforce the provisioned PFD(s) successfully. | | + +##### 5.11.2.1.2 Type: PfdManagement + +This type represents a PFD management resource for a PFD management request. + +**Table 5.11.2.1.2-1: Definition of type PfdManagement** + +| Attribute name | Data type | Cardinality | Description | Applicability
(NOTE 1) | +|-------------------------|----------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| self | Link | 0..1 | Link to the resource "Individual PFD Management Transaction".
This parameter shall be supplied by the SCEF in HTTP responses. | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7.
This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| pfdDatas | map(PfdData) | 1..N | Each element uniquely identifies the PFDs for an external application identifier. Each element is identified in the map via an external application identifier as key. The response shall include successfully provisioned PFD data of application(s). | | +| pfdReports | map(PfdReport) | 0..N | Supplied by the SCEF and contains the external application identifiers for which PFD(s) are not added or modified successfully. The failure reason is also included. Each element provides the related information for one or more external application identifier(s) and is identified in the map via the failure identifier as key. (NOTE 2) | | +| notificationDestination | Link | 0..1 | A URI indicating the notification destination for T8 notifications. | PfdMgmtNotification | +| requestTestNotification | boolean | 0..1 | Set to true by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. Set to false or omitted otherwise. | Notification_test_event | +| websocketNotifConfig | WebsocketNotifConfig | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 5.2.5.4. | Notification_websocket | + +NOTE 1: Properties marked with a feature as defined in clause 5.11.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. +NOTE 2: The failure identifier is a string encoded map key. + +### 5.11.2.1.3 Type: PfdData + +This type represents a PFD request to add, update or remove PFD(s) for one external application identifier provided by the SCS/AS to the SCEF via T8 interface. + +**Table 5.11.2.1.3-1: Definition of type PfdData** + +| Attribute name | Data type | Cardinality | Description | Applicability
(NOTE 1) | +|----------------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| externalAppId | string | 1 | Each element uniquely external application identifier
(NOTE 2) | | +| self | Link | 0..1 | Link to the resource "Individual Application PFD Management". This parameter shall be supplied by the SCEF in HTTP responses. | | +| pfds | map(Pfd) | 1..N | Contains the PFDs of the external application identifier. Each PFD is identified in the map via a key containing the PFD identifier.
(NOTE 3) | | +| allowedDelay | DurationSecRm | 0..1 | Indicates that the list of PFDs in this request should be deployed within the time interval indicated by the Allowed Delay | | +| cachingTime | DurationSecRo | 0..1 | SCEF supplied property, inclusion of this property means the allowed delayed cannot be satisfied, i.e. it is smaller than the caching time, but the PFD data is still stored. | | + +NOTE 1: Properties marked with a feature as defined in clause 5.11.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. +NOTE 2: An externalAppId can only belong to one "individual PFD Management Transaction" resource. +NOTE 3: When multiple PFDs are associated with application identifier, the application is detected when any of the PFDs associated with the application identifier is matched. + +#### 5.11.2.1.4 Type: Pfd + +This data type represents a PFD for an external Application Identifier. + +**Table 5.11.2.1.4-1: Definition of type Pfd** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|------------------|--------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| pfdId | string | 1 | Identifies a PFD of an application identifier. | | +| flowDescriptions | array(string) | 0..N | Represents a 3-tuple with protocol, server ip and server port for UL/DL application traffic. The content of the string has the same encoding as the IPFilterRule AVP value as defined in IETF RFC 6733 [46].
(NOTE 2) | | +| urls | array(string) | 0..N | Indicates a URL or a regular expression which is used to match the significant parts of the URL.
(NOTE 2) | | +| domainNames | array(string) | 0..N | Indicates an FQDN or a regular expression as a domain name matching criteria.
(NOTE 2) | | +| dnProtocol | DomainNameProtocol | 0..1 | Indicates the additional protocol and protocol field for domain names to be matched, it may only be provided when domainNames attribute is present. | DomainNameProtocol | + +NOTE 1: Properties marked with a feature as defined in clause 5.11.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +NOTE 2: At least one of the properties "flowDescriptions", "urls" or "domainNames" shall be included. If a PFD contains multiple filter types, the PFD is only matched when every filter type contained in the PFD has a matching value. + +#### 5.11.2.1.5 Type: PfdReport + +This type represents a PFD report to indicate the external application identifier(s) which PFD(s) are not added or modified successfully and corresponding failure reason. + +**Table 5.11.2.1.5-1: Definition of type PfdReport** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|----------------|-----------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| externalAppIds | array(string) | 1..N | Identifies the external application identifier(s) which PFD(s) are not added or modified successfully | | +| failureCode | FailureCode | 1 | Identifies the failure reason | | +| cachingTime | DurationSec | 0..1 | It shall be included when the allowed delayed cannot be satisfied, i.e. it is smaller than the caching time configured in fetching PFD. | | +| locationArea | UserPlaneLocationArea | 0..1 | Identifies a location area of the user plane(s) which are unable to enforce the PFD(s). | | + +NOTE: Properties marked with a feature as defined in clause 5.11.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +#### 5.11.2.1.6 Type: UserPlaneLocationArea + +This data type represents location area(s) of the user plane which is unable to enforce the provisioned PFD(s) successfully. It is sent from the SCEF to the SCS/AS. + +**Table 5.11.2.1.6-1: Definition of the UserPlaneLocationArea data Type** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|----------------|----------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| locationArea | LocationArea | 0..1 | Identifies the network area information served by the user planes functions which are unable to enforce the provisioned PFD(s) successfully. It can be either a list of cell IDs, or a list of Tracking Areas, or civic addresses, or a geographic area, or a combination of any of the above. | | +| locationArea5G | LocationArea5G | 0..1 | Identifies the network area information served by the user planes functions which are unable to enforce the provisioned PFD(s) successfully. It can be either a list of E-UTRA cell IDs, or a list of NR cell ID, or a list of Tracking Areas, or civic addresses, or a geographic area, or a combination of any of the above. | FailureLocation_5G | +| dnais | array(DNAI) | 0..N | Identifies a list of DNAI supported by the user plane functions which are unable to enforce the provisioned PFD(s) successfully. | FailureLocation_5G | + +#### 5.11.2.1.7 Type: PfdManagementPatch + +This type represents the parameters to request the modification of a PFD management transaction resource. + +**Table 5.11.2.1.7-1: Definition of type PfdManagementPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------------|--------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| pfdDatas | map(PfdData) | 1..N | Each element uniquely identifies the PFDs for an external application identifier. Each element is identified in the map via an external application identifier as the key. | | +| notificationDestination | Link | 0..1 | A URI indicating the notification destination for T8 notifications. | | + +NOTE 1: Properties marked with a feature as defined in clause 5.11.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. + +### 5.11.2.2 Referenced simple data types and enumerations + +#### 5.11.2.2.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +#### 5.11.2.2.2 Simple data types + +The simple data types defined in table 5.11.2.2.2-1 shall be supported. + +**Table 5.11.2.2.2-1: Simple data types** + +| Type name | Description | +|-----------|-------------| +| | | +| | | + +### 5.11.2.2.3 Enumeration: FailureCode + +The enumeration FailureCode represents the failure reason of the PFD management. + +**Table 5.11.2.2.3-1: Enumeration FailureCode** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------| +| MALFUNCTION | This value indicates that something functions wrongly in PFD provisioning or the PFD provisioning does not function at all. | | +| RESOURCE_LIMITATION | This value indicates there is resource limitation for PFD storage. | | +| SHORT_DELAY | This value indicates that the allowed delay is too short and PFD(s) are not stored. | | +| APP_ID_DUPLICATED | The received external application identifier(s) are already provisioned. | | +| PARTIAL_FAILURE | The PFD(s) are not provisioned to all PCEFs/TDFs/SMFs. | PfdMgmtNotification | +| OTHER_REASON | Other reason unspecified. | | +| NOTE: Properties marked with a feature as defined in clause 5.11.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | + +### 5.11.2.2.4 Enumeration: DomainNameProtocol + +**Table 5.14.2.2.4-1: Enumeration DomainNameProtocol** + +| Enumeration value | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------| +| DNS_QNAME | Identifies the DNS protocol and the question name in DNS query. | | +| TLS_SNI | Identifies the Server Name Indication in TLS ClientHello message. | | +| TLS_SAN | Identifies the Subject Alternative Name in TLS ServerCertificate message. | | +| TSL_SCN | Identifies the Subject Common Name in TLS ServerCertificate message. (NOTE 2) | | +| NOTE 1: Properties marked with a feature as defined in clause 5.10.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | +| NOTE 2: The enumeration value "TSL_SCN" refers to "TLS_SCN" value in domain name protocol. This enumeration value is however kept as currently defined in this specification for backward compatibility considerations. | | | + +## 5.11.3 Resource structure + +### 5.11.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-pfd-management/v1** + +"apiRoot" is set as described in clause 5.2.4. "apiName" shall be set to "3gpp-pfd-management" and "apiVersion" shall be set to "v1" for the version defined in the present document. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.11.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|---------------------------------------|---------------------------------------------------------------------|-------------|--------------------------------------------------------------------------------------------------------| +| PFD Management Transactions | /{scsAsId}/transactions | GET | Read all or queried PFDs for a given SCS/AS | +| | | POST | Create PFDs for a given SCS/AS and one or more external Application Identifier(s) | +| Individual PFD Management Transaction | /{scsAsId}/transactions/{transactionId} | GET | Read all PFDs for a given SCS/AS and a transaction for one or more external Application Identifier(s) | +| | | PUT | Update PFD(s) for a given SCS/AS and a transaction for one or more external Application Identifier(s) | +| | | PATCH | Modify PFD(s) for a given SCS/AS and a transaction for one or more external Application Identifier(s). | +| | | DELETE | Delete PFDs for a given SCS/AS and a transaction for one or more external Application Identifier(s) | +| Individual Application PFD Management | /{scsAsId}/transactions/{transactionId}/applications/{appId} (NOTE) | PUT | Update PFDs at individual application level | +| | | PATCH | Update PFDs at individual application level | +| | | GET | Read PFDs at individual application level | +| | | DELETE | Delete PFDs at individual application level | + +NOTE: The appId as the resource identifier is not necessarily identical as the external application identifier received from the SCS/AS. + +## 5.11.3.2 Resource: PFD Management Transactions + +### 5.11.3.2.1 Introduction + +This resource allows an SCS/AS to read all PFDs for a given SCS/AS or create PFDs for a given SCS/AS with one or more external Application Identifier(s). + +### 5.11.3.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-pfd-management/v1/{scsAsId}/transactions + +This resource shall support the resource URI variables defined in table 5.11.3.2.2-1. + +**Table 5.11.3.2.2-1: Resource URI variables for resource "PFD Management Transactions"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +### 5.11.3.2.3 Resource methods + +#### 5.11.3.2.3.1 GET + +The GET method allows to read all or queried active PFDs for a given SCS/AS. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support the URI query parameters as specified in the table 5.11.3.2.3.1-0. + +**Table 5.11.3.2.3.1-0: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | Applicability | +|----------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------|-------------------------------------------------------------------|---------------| +| external-app-ids | array(string) | 0..N | The external application identifier(s) of the requested PFD data. | enNB | +| NOTE: If multiple elements are provided in the array data structure, then each element shall be treated as a separate query parameter. | | | | | + +This method shall support the request and response data structures, and response codes, as specified in the table 5.11.3.2.3.1-1. + +**Table 5.11.3.2.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------------------------------------------------------------------------------------|----------------------|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(PfdManagement) | 0..N | 200 OK | All or queried transactions including the PFDs for the SCS/AS in the request URI are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. | | | | | + +**Table 5.11.3.2.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.2.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.11.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +## 5.11.3.2.3.3 POST + +The POST method creates new PFDs resource(s) for a given SCS/AS with one or more external Application Identifier provided by the SCS/AS. It is initiated by the SCS/AS and answered by the SCEF. The SCS/AS shall provide the external Application Identifier in the message body and upon receipt of the HTTP POST message, the SCEF shall generate the resource "Individual PFD Management Transaction" and also the sub-resource(s) "Individual Application PFD Management", the SCEF shall send these resource URI in the HTTP response to the SCS/AS. + +This method shall support the request and response data structures, and response codes, as specified in the table 5.11.3.2.3.3-1. + +**Table 5.11.3.2.3.3-1: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------|-------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| | PfdManagement | 1 | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | PfdManagement | 1 | 201 Created | The PFDs resource was created successfully. PfdReport may be included to provide detailed failure information for some applications. | +| | array(PfdReport) | 1..N | 500 Internal Server Error | The PFDs for all applications were not created successfully. PfdReport is included with detailed information. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.11.3.2.3.3-2: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-pfd-management/v1/{scsAsId}/transactions/{transactionId} | + +## 5.11.3.2.3.4 PATCH + +This HTTP method is not supported for the resource. + +## 5.11.3.2.3.5 DELETE + +To remove all PFDs for a given SCS/AS, the SCS/AS shall use the HTTP DELETE method on the "PFD Management Transactions" resource. + +The possible response messages from the SCEF, depending on whether the DELETE request is successful or unsuccessful, are shown in table 5.11.3.2.3.5-1. + +**Table 5.11.3.2.3.5-1: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | All PFDs were removed successfully. The SCEF shall not return a response content. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. | + +| | | | | | +|-------------------------------------------------------------------------------------------------------|------|--|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | Redirection handling is described in clause 5.2.10. | +| | none | | 308
Permanent Redirect | Permanent redirection, during transaction termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. | | | | | + +**Table 5.11.3.2.3.5-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.2.3.5-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.11.3.3 Resource: Individual PFD Management Transaction + +#### 5.11.3.3.1 Introduction + +This resource allows an SCS/AS to read, or update or delete PFDs for a given SCS/AS and a transaction Id for one or more application identifier(s) at the SCEF. + +#### 5.11.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-pfd-management/v1/{scsAsId}/transactions/{transactionId} + +This resource shall support the resource URI variables defined in table 5.11.3.3.2-1. + +**Table 5.11.3.3.2-1: Resource URI variables for resource "Individual PFD Management Transaction"** + +| Name | Data type | Definition | +|---------------|-----------|------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| transactionId | string | Identifier of the transaction. The transactionId corresponds to the stage 2 TLTRI. | + +#### 5.11.3.3.3 Resource methods + +##### 5.11.3.3.3.1 GET + +The GET method allows to read all PFDs for a given SCS/AS and a transaction Id generated by the SCEF. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.11.3.3.3.1-1. + +**Table 5.11.3.3.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|------------------|--------------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | PfdManagement | 1 | 200 OK | The PFDs for the SCS/AS and the transaction Id for one or more application identifier(s) in the request URI are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.11.3.3.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.3.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.11.3.3.3.2 PUT + +The PUT method modifies the PFDs for a given SCS/AS and an existing transaction Id generated by the SCEF. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support the request and response data structures, and response codes, as specified in the table 5.11.3.3.3.2-1. + +**Table 5.11.3.3.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------|-------------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PfdManagement | 1 | Update of PFD(s) for an existing transaction Id. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | PfdManagement | 1 | 200 OK | The PFDs were updated successfully and a representation is returned. PfdReport may be included to provide detailed failure information for some applications. | +| | none | | 204 No Content | The PFDs were updated successfully. | +| | array(PfdReport) | 1..N | 500 Internal Server Error | The PFDs for all applications were not updated successfully. PfdReport is included with detailed information. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.11.3.3.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.3.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.11.3.3.3.3 PATCH + +The PATCH method modifies an existing PFD Management Transaction resource. The SCS/AS shall initiate the HTTP PATCH request message and the SCEF shall respond to the message. + +This method shall support the request and response data structures, and response codes, as specified in the table 5.11.3.3.3.3-1. + +**Table 5.11.3.3.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|--------------------|-------------|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PfdManagementPatch | 1 | Modify of PFD(s) for an existing transaction ID. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | PfdManagement | 1 | 200 OK | The PFDs were modified successfully and a representation of the modified resource is returned. The PfdReport data structure may be included in the response to provide the detailed failure information if the modification failed for some applications. | +| | none | | 204 No Content | The PFDs were modified successfully. | +| | array(PfdReport) | 1..N | 500 Internal Server Error | The PFDs for all applications were not modified successfully. PFD Report(s) shall be included in the response body with the detailed information. | +| | none | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.11.3.3.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.3.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.11.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.11.3.3.3.5 DELETE + +The DELETE method deletes the PFDs for a given SCS/AS and an transaction Id generated by the SCEF. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.11.3.3.3.5-1 and table 5.11.3.3.3.5-2. + +**Table 5.11.3.3.3.5-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | Cardinality | Remarks | +|------|-----------|-------------|---------| +| N/A | | | | + +**Table 5.11.3.3.5-2: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | None | | 204 No Content | The PFDs for an existing transaction Id were removed successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.11.3.3.5-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.3.5-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.11.3.4 Resource: Individual Application PFD Management + +### 5.11.3.4.1 Introduction + +This resource allows an SCS/AS to read, update or remove the PFDs for a given SCS/AS and an external Application Identifier at the SCEF. + +### 5.11.3.4.2 Resource definition + +Resource URI: {apiRoot}/3gpp-pfd-management/v1/{scsAsId}/transactions/{transactionId}/applications/{appId} + +This resource shall support the resource URI variables defined in table 5.11.3.4.2-1. + +**Table 5.11.3.4.1: Resource URI variables for resource "Individual Application PFD Management"** + +| Name | Data type | Definition | +|---------------|-----------|----------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| transactionId | string | Identifier of the transaction. | +| appId | string | External Application Identifier. | + +### 5.11.3.4.3 Resource methods + +#### 5.11.3.4.3.1 GET + +The GET method allows to read all PFDs at individual application level. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support request and response data structures, and response codes, as specified in the table 5.11.3.4.3.1-1. + +**Table 5.11.3.4.3.1-1: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | None | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | PfdData | 1 | 200 OK | The PFDs at individual application level in the request URI are returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.11.3.4.3.1-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.4.3.1-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.11.3.4.3.2 PUT + +The PUT method modifies the PFDs at individual application level. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support the request and response data structures, and response codes, as specified in the table 5.11.3.4.3.2-1. + +**Table 5.11.3.4.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PfdData | 1 | Update of PFD(s) for an existing external application identifier. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | PfdData | 1 | 200 OK | The PFDs for the existing external application identifier were updated successfully and a representation is returned. | +| | none | | 204 No Content | The PFDs for the existing external application identifier were updated successfully. | +| | PfdReport | 1 | 403 Forbidden | The PFDs for the application were not updated successfully, applicable for error SHORT_DELAY in table 5.11.2.2.3-1. | +| | PfdReport | 1 | 409 Conflict | The PFDs for the application were not updated successfully, applicable for error APP_ID_DUPLICATED in table 5.11.2.2.3-1. | +| | PfdReport | 1 | 500 Internal Server Error | The PFDs for the application were not updated successfully, applicable for other errors in table 5.11.2.2.3-1. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.11.3.4.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.4.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.11.3.4.3.3 PATCH + +The PATCH method modifies the PFDs at individual application level. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support the request and response data structures, and response codes, as specified in the table 5.11.3.4.3.3-1. + +**Table 5.11.3.4.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PfdData | 1 | Update of PFD(s) for an existing external application identifier. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | PfdData | 1 | 200 OK | The PFDs for the existing external application identifier were updated successfully and a representation is returned. | +| | none | | 204 No Content | The PFDs for the existing external application identifier were updated successfully. | +| | PfdReport | 1 | 403 Forbidden | The PFDs for the application were not updated successfully, applicable for error SHORT_DELAY in table 5.11.2.2.3-1. | +| | PfdReport | 1 | 409 Conflict | The PFDs for the application were not updated successfully, applicable for error APP_ID_DUPLICATED in table 5.11.2.2.3-1. | +| | PfdReport | 1 | 500 Internal Server Error | The PFDs for the application were not updated successfully, applicable for other errors in table 5.11.2.2.3-1. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.11.3.4.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.4.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.11.3.4.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.11.3.4.3.5 DELETE + +The DELETE method deletes all the PFDs at individual application level. It is initiated by the SCS/AS and answered by the SCEF. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.11.3.4.3.5-1 and table 5.11.3.4.3.5-2. + +**Table 5.11.3.4.3.5-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | Cardinality | Remarks | +|------|-----------|-------------|---------| +| N/A | | | | + +**Table 5.11.3.4.3.5-2: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | +| Response body | none | | | | +| | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The PFDs were removed successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during transaction termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during transaction termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.11.3.4.3.5-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.11.3.4.3.5-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.11.3.5 Void + +## 5.11.3A Notifications + +### 5.11.3A.1 General + +The notifications provided by the PfdManagement API are specified in this clause. + +**Table 5.11.3A-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|-----------------------------|---------------------------|---------------------------------|------------------------------------------| +| PFD Management Notification | {notificationDestination} | POST | Send asynchronous PFD management result. | + +## 5.11.3A.2 PFD Management Notification + +### 5.11.3A.2.1 Description + +The PFD Management Notification allows the SCEF to send notification about PFD management result to the SCS/AS, if the PFD provisioning fails within the allowed delay. + +### 5.11.3A.2.2 Target URI + +The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 5.11.3A.2.2-1. + +**Table 5.11.3A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|-------------------------|-----------|--------------------------------------------------------------------------------------------------------------| +| notificationDestination | Link | Callback reference provided by the SCS/AS during creation or modification of the PFD management transaction. | + +### 5.11.3A.2.3 Standard Methods + +#### 5.11.3A.2.3.1 Notification via POST + +The HTTP POST method reports the asynchronous PFD management result. The SCEF shall initiate the HTTP POST request message and the SCS/AS shall respond to the message. + +This method shall support the request data structures specified in table 5.11.3A.2.3.1-1 and the response data structures and response codes specified in table 5.11.3A.2.3.1-2. + +**Table 5.11.3A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|-----------|-------------|-------------------------------------------------------| +| PfdReport | 1..N | The PFD management notification provided by the SCEF. | + +**Table 5.11.3A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| none | | 204 No Content | The PFD management notification is received successfully. | +| none | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS instance where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.11.3A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.11.3A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +#### 5.11.3A.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the PfdReport may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +### 5.11.4 Used Features + +The table below defines the features applicable to the PfdManagement API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.11.4-1: Features used by PfdManagement API** + +| Feature Number | Feature | Description | +|----------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | DomainNameProtocol | This feature supports the additional protocol matching condition for the domain name in PFD data. | +| 2 | PfdMgmtNotification | This feature supports PFD management notification. | +| 3 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 4 | Notification_test_event | The testing of notification connection is supported according to clause 5.2.5.3. | +| 5 | FailureLocation_5G | This feature supports the notification of specific failure location area of UPF for PFD management in 5G. This feature is applicable only if PfdMgmtNotification feature is also supported. The feature supports the 5G requirement and may only be supported in 5G. | +| 6 | enNB | Indicates the support of enhancements to the northbound interfaces. | +| 7 | PatchUpdate | Indicates the support of enhancements to the northbound interfaces (e.g. support the partial modification of an existing PFD Management Transaction resource). | + +### 5.11.5 Error handling + +#### 5.11.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +#### 5.11.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the PfdManagement API. + +#### 5.11.5.3 Application Errors + +The application errors defined for PfdManagement API are listed in table 5.11.5.3-1. + +**Table 5.11.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 5.12 ECRControl API + +### 5.12.1 Overview + +The ECRControl API is a custom API (RPC interaction) that allows the SCS/AS to query or configure the enhanced coverage restriction over 3GPP networks. The ECRControl API defines a set of data models and related custom operation procedures for the enhanced coverage restriction control request. The corresponding JSON schema for the representation of the operations defined by the ECRControl API is provided in its complete form in Annex A.12. + +### 5.12.2 Data model + +#### 5.12.2.1 Data types + +##### 5.12.2.1.1 Introduction + +This clause defines data structures to be used in the request and response. + +Table 5.12.2.1.1-1 specifies data types re-used by the ECRControl API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the ECRControl API. + +**Table 5.12.2.1.1-1: ECRControl API re-used Data Types** + +| Data type | Reference | Comments | +|---------------------|---------------------|-----------------------------------------------------------------------------------------| +| EcRestrictionDataWb | 3GPP TS 29.503 [63] | Contains the Enhance Coverage Restriction Data. | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.12.4-1. | + +Table 5.12.2.1.1-2 specifies the data types defined for the ECRControl API. + +**Table 5.12.2.1.1-2: ECRControl API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|-------------------------|----------------|---------------------------------------------------------------------------------------------------------|---------------| +| ECRControl | 5.12.2.1.2 | Represents the parameters to request Enhanced Coverage Restriction control. | | +| ECRData | 5.12.2.1.3 | Represents the current visited PLMN (if any) and the current settings of enhanced coverage restriction. | | +| PlmnEcRestrictionDataWb | 5.12.2.1.4 | Indicates whether enhanced coverage mode is restricted or not for a PLMN ID. | ECR_WB_5G | + +##### 5.12.2.1.2 Type: ECRControl + +This type represents the Enhanced Coverage Restriction control request. The structure is used only for request. + +**Table 5.12.2.1.2-1: Definition of type ECRControl** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------|--------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| supportedFeatures | SupportedFeatures | 1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7. | | +| mtcProviderId | string | 0..1 | Identifier the MTC Service Provider and/or MTC Application. (NOTE 4). | | +| scsAsId | string | 0..1 | Identifier of the SCS/AS. | | +| externalId | ExternalId | 0..1 | Identifies a user as defined in Clause 4.6.2 of 3GPP TS 23.682 [2].
(NOTE 2) | | +| msisdn | Msisdn | 0..1 | Identifies the MS internal PSTN/ISDN number allocated for a UE.
(NOTE 2) | | +| ecrDataWbs | array(PlmnEcRestrictionDataWb) | 0..N | Identifies whether enhanced coverage mode are restricted or not. This attribute shall not be present for the query custom operation. | ECR_WB_5G | +| restrictedPlmnIds | array(PlmnId) | 0..N | Indicates a complete list (and possibly empty) of serving PLMNs where Enhanced Coverage shall be restricted. This attribute shall not be present for the query custom operation. (NOTE 3) | | +| allowedPlmnIds | array(PlmnId) | 0..N | Indicates a complete list (and possibly empty) of serving PLMNs where Enhanced Coverage shall be allowed. This attribute shall not be present for the query custom operation. (NOTE 3) | | + +NOTE 1: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. +NOTE 2: One of the properties "externalId" or "msisdn" shall be included. +NOTE 3: "restrictedPlmnIds" and "allowedPlmnIds" shall be mutually exclusive. +NOTE 4: The SCEF should check received MTC provider identifier and then the SCEF may: +- override it with local configured value and send it to HSS; +- send it directly to the HSS; or +- reject the Enhanced Coverage Restriction control request + +### 5.12.2.1.3 Type: ECRData + +This data type represents the current visited PLMN (if any) and the current settings of enhanced coverage restriction. The structure is used only for response. + +**Table 5.12.2.1.3-1: Definition of type ECRData** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------|--------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------|------------------------| +| supportedFeatures | SupportedFeatures | 1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7. | | +| visitedPlmnId | PlmnId | 0..1 | Indicates the current visited PLMN. | | +| ecrDataWbs | array(PlmnEcRestrictionDataWb) | 0..N | Identifies whether enhanced coverage mode are restricted or not. | ECR_WB_5G | +| restrictedPlmnIds | array(PlmnId) | 0..N | Indicates a complete list (and possibly empty) of serving PLMNs where Enhanced Coverage shall be restricted. (NOTE 2) | | +| allowedPlmnIds | array(PlmnId) | 0..N | Indicates a complete list (and possibly empty) of serving PLMNs where Enhanced Coverage shall be allowed. (NOTE 2) | | + +NOTE 1: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. +NOTE 2: "restrictedPlmnIds" and "allowedPlmnIds" shall be mutually exclusive. + +#### 5.12.2.1.4 Type: PlmnEcRestrictionDataWb + +**Table 5.12.2.1.4-1: Definition of type PlmnEcRestrictionDataWb** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|---------------------|-------------|-----------------------------------------------------------------------------|---------------| +| plmnId | PlmnId | 1 | Indicates the PLMN where enhanced coverage mode shall be restricted or not. | | +| plmnEcrDataWb | EcRestrictionDataWb | 0..1 | Identifies whether enhanced coverage mode are restricted or not. | | + +### 5.12.3 Custom Operations without associated resources + +#### 5.12.3.1 Overview + +Custom operations used for this API are summarized in table 5.12.3.1-1. "apiRoot" is set as described in clause 5.2.4. + +**Table 5.12.3.1-1: Custom operations without associated resources** + +| Operation name | Custom operation URI | Mapped HTTP method | Description | +|----------------|----------------------|--------------------|------------------------------------------------------------| +| query | /query | POST | Query the status of enhanced coverage restriction for a UE | +| configure | /configure | POST | Configure the enhanced coverage restriction for a UE | + +#### 5.12.3.2 Operation: query + +##### 5.12.3.2.1 Description + +This custom operation allows an SCS/AS to query the current status of enhanced coverage restriction for a UE via the T8 interface as defined in 3GPP TS 23.682 [2]. + +##### 5.12.3.2.2 Operation Definition + +This operation shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.12.3.2.2-1 and table 5.12.3.2.2-2. + +**Table 5.12.3.2.2-1: URI query parameters supported by the POST on this operation** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.12.3.2.2-2: Data structures supported by the POST request/response on this operation** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|------------------|--------------------|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ECRControl | 1 | Parameters to query the current status of Enhanced Coverage Restriction. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | ECRData | 1 | 200 OK | The requested information was returned successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.12.5.3. + +**Table 5.12.3.2.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.12.3.2.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.12.3.3 Operation: configure + +### 5.12.3.3.1 Description + +This custom operation allows an SCS/AS to configure the current setting of enhanced coverage restriction for a UE via the T8 interface as defined in 3GPP TS 23.682 [2]. + +### 5.12.3.3.2 Operation Definition + +This operation shall support the request data structures specified in table 5.12.3.3.2-1 and the response data structure and response codes specified in table 5.12.3.3.2-2. + +**Table 5.12.3.3.2-1: URI query parameters supported by the POST on this operation** + +| Name | Data type | Cardinality | Remarks | +|----------------|------------------|--------------------|----------------| +| none specified | | | | + +**Table 5.12.3.3.2-2: Data structures supported by the POST request/response on this operation** + +| Request body | Data type | Cardinality | Remarks | | +|----------------------|------------------|--------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ECRControl | 1 | Parameters to configure the setting of Enhanced Coverage Restriction. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | ECRData | 1 | 200 OK | The Enhanced Coverage Restriction setting was configured successfully | +| | none | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.12.5.3. + +**Table 5.12.3.3.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.12.3.3.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|------------------|----------|--------------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.12.4 Used Features + +The table below defines the features applicable to the ECRControl API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.12.4-1: Features used by ECRControl API** + +| Feature Number | Feature | Description | +|-----------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | ECR_WB_5G | The enhanced coverage restriction control information indicates whether the enhanced coverage modes are restricted or not for the WB UE. The feature is not applicable to the pre-5G. | + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification". +Description: A clear textual description of the feature. + +## 5.12.5 Error handling + +### 5.12.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.12.5.2 Protocol Errors + +In this release of the specification, there are no additional protocol errors applicable for the ECRControl API. + +### 5.12.5.3 Application Errors + +The application errors defined for the ECRControl API are listed in table 5.12.5.3-1. + +**Table 5.12.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|-------------------|------------------|------------------------------| +| QUOTA_EXCEEDED | 403 Forbidden | Not enough quota for SCS/AS. | + +## 5.13 NpConfiguration API + +### 5.13.1 Overview + +The NpConfiguration API is a RESTful API that allows the SCS/AS to send suggested network parameters to influence certain aspects of UE/network behaviour such as the UE's PSM, extended idle mode DRX, and extended buffering configurations. The NpConfiguration API defines a set of data models, resources and the related procedures for the creation and management of the network parameter configuration. The corresponding JSON schema for the representation of the resources and operations defined by the NpConfiguration API is provided in its complete form in Annex A.13. + +### 5.13.2 Data model + +#### 5.13.2.1 Resource data types + +##### 5.13.2.1.1 Introduction + +This clause defines data structures to be used in resource representations. + +Table 5.13.2.1.1-1 specifies data types re-used by the NetworkParameterConfiguration API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the NetworkParameterConfiguration API. + +**Table 5.13.2.1.1-1: NetworkParameterConfiguration API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|-----------------------------------------------------------------------------------------| +| Dnn | 3GPP TS 29.571 [45] | Identifies a DNN. | +| IpAddr | 3GPP TS 29.571 [45] | UE IP Address. | +| MacAddr48 | 3GPP TS 29.571 [45] | MAC Address. | +| Snssai | 3GPP TS 29.571 [45] | Identifies an S-NSSAI. | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.13.4-1. | + +Table 5.13.2.1.1-2 specifies the data types defined for the NpConfiguration API. + +**Table 5.13.2.1.1-2: NpConfiguration API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|---------------------------|-----------------------|--------------------------------------------------------------------------------------------------------|----------------------| +| ConfigurationNotification | 5.13.2.1.4 | Represents a configuration result notification. | | +| NpConfiguration | 5.13.2.1.2 | Represents a network parameters configuration. | | +| NpConfigurationPatch | 5.13.2.1.3 | Represents parameters used to request the modification of a network parameters configuration resource. | | + +#### 5.13.2.1.2 Type: NpConfiguration + +This type represents a configuration of network parameters. The same structure is used in the configuration request and response. + +**Table 5.13.2.1.2-1: Definition of type NpConfiguration** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 2) | +|----------------------------|----------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| self | Link | 0..1 | Link to the resource "Individual NP Configuration". This parameter shall be supplied by the SCEF in HTTP responses. | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7. This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| mtcProviderId | string | 0..1 | Identifies the MTC Service Provider and/or MTC Application. (NOTE 4) | | +| dnn | Dnn | 0..1 | Identifies a DNN, a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only. | UEId_retrieval | +| externalId | ExternalId | 0..1 | Identifies a user as defined in Clause 4.6.2 of 3GPP TS 23.682 [2].
The attribute may also be present in the NP configuration response message, if the "UEId_retrieval" feature is supported and the corresponding request message includes the "ueIpAddr" attribute or the "ueMacAddr" attribute. (NOTE 1) | | +| msisdn | Msisdn | 0..1 | Identifies the MS internal PSTN/ISDN number allocated for a UE. (NOTE 1) | | +| externalGroupId | ExternalGroupId | 0..1 | Identifies a user group as defined in Clause 4.6.2 of 3GPP TS 23.682 [2]. (NOTE 1) | | +| maximumLatency | DurationSec | 0..1 | This parameter may be included to identify the maximum delay acceptable for downlink data transfers. | | +| maximumResponseTime | DurationSec | 0..1 | This parameter may be included to identify the length of time for which the UE stays reachable to allow the SCS/AS to reliably deliver the required downlink data. | | +| suggestedNumberOfDIPackets | integer | 0..1 | This parameter may be included to identify the number of packets that the serving gateway shall buffer in case that the UE is not reachable. | | +| groupReportingGuardTime | DurationSec | 0..1 | Identifies the time for which the SCEF can aggregate the reports detected by the UEs in a group and report them together to the SCS/AS, as specified in clause 5.6.0 of 3GPP TS 23.682 [2]. | | +| notificationDestination | Link | 0..1 | A URI indicating the notification destination where T8 notification requests shall be delivered. The attribute shall be provided if the attribute "externalGroupId" is provided. | | +| requestTestNotification | boolean | 0..1 | Set to true by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. Set to false or omitted otherwise. The attribute may only be provided if the attribute "externalGroupId" is provided. | Notification_test_event | +| websocketNotifConfig | WebsocketNotifConfig | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 5.2.5.4. The attribute may only be provided if the attribute "externalGroupId" is provided. | Notification_websocket | +| validityTime | DateTime | 0..1 | Identifies when the network parameter expires and shall be deleted locally if it expires. The attribute is only applicable in 5G. (NOTE 3) | NpExpiry_5G | +| snssai | Snssai | 0..1 | Indicate the S-NSSAI. | UEId_retrieval | +| ueIpAddr | IpAddr | 0..1 | UE IP address. | UEId_retrieval | +| ueMacAddr | MacAddr48 | 0..1 | UE MAC address. | UEId_retrieval | + +NOTE 1: Only one of the properties "externalId", "msisdn" or "externalGroupId" shall be included. + +| | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 2: | Properties marked with a feature as defined in clause 5.13.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | +| NOTE 3: | If this attribute is omitted, no expiry for network parameter configuration applies. | +| NOTE 4: | The SCEF should check received MTC provider identifier and then the SCEF may:
  • - override it with local configured value and send it to HSS;
  • - send it directly to the HSS; or
  • - reject the network parameter configuration request.
| + +#### 5.13.2.1.3 Type: NpConfigurationPatch + +This type represents a configuration of network parameters provided by the SCS/AS to the SCEF. The structure is used for HTTP PATCH request. + +**Table 5.13.2.1.3-1: Definition of type NpConfigurationPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| maximumLatency | DurationSecRm | 0..1 | This parameter may be included to identify the maximum delay acceptable for downlink data transfers. | | +| maximumResponseTime | DurationSecRm | 0..1 | This parameter may be included to identify the length of time for which the UE stays reachable to allow the SCS/AS to reliably deliver the required downlink data. | | +| suggestedNumberOfDIPackets | integer | 0..1 | This parameter may be included to identify the number of packets that the serving gateway shall buffer in case that the UE is not reachable. | | +| groupReportGuardTime | DurationSecRm | 0..1 | Identifies the time for which the SCEF can aggregate the reports detected by the UEs in a group and report them together to the SCS/AS, as specified in clause 5.6.0 of 3GPP TS 23.682 [2]. | | +| validityTime | DateTimeRm | 0..1 | Identifies when the network parameter expires and shall be deleted locally if it expires. The attribute is only applicable in 5G. | NpExpiry_5G | +| notificationDestination | Link | 0..1 | A URI indicating the notification destination where T8 notification requests shall be delivered. | | +| NOTE: Properties marked with a feature as defined in clause 5.13.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. | | | | | + +#### 5.13.2.1.4 Type: ConfigurationNotification + +This type represents a configuration result notification. + +**Table 5.13.2.1.4-1: Definition of the ConfigurationNotification data type** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| configuration | Link | 1 | Link to the configuration resource to which this notification is related. | | +| configResults | array(ConfigResult) | 0..N | Each element identifies a notification of grouping configuration result. | | +| appliedParam | AppliedParameterConfiguration | 0..1 | Indicates the applied parameter configuration in the network. The "maximumDetectionTime" attribute in AppliedParameterConfiguration data type is not applicable for Network Parameter configuration. | Enhanced_param_config | +| NOTE: Properties marked with a feature as defined in clause 5.13.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | + +## 5.13.3 Resource structure + +### 5.13.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-network-parameter-configuration/v1** + +"apiRoot" is set as described in clause 5.2.4. "apiName" shall be set to "3gpp-network-parameter-configuration" and "apiVersion" shall be set to "v1" for the version defined in the present document. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.13.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|-----------------------------|---------------------------------------------|-------------|---------------------------------------------------------------| +| NP Configurations | /{scsAsId}/configurations | GET | Read all NP configurations for a given SCS/AS | +| | | POST | Create a new NP configuration | +| Individual NP Configuration | /{scsAsId}/configurations/{configurationId} | PUT | Replace all of the properties in an existing NP configuration | +| | | PATCH | Modify some properties in an existing NP configuration | +| | | GET | Read an existing NP configuration | +| | | DELETE | Delete a NP configuration | + +### 5.13.3.2 Resource: NP Configurations + +#### 5.13.3.2.1 Introduction + +This resource allows an SCS/AS to read all active network parameter configurations or create a new configuration to configure network parameters. + +#### 5.13.3.2.2 Resource definition + +Resource URI: **{apiRoot}/3gpp-network-parameter-configuration/v1/{scsAsId}/configurations** + +This resource shall support the resource URI variables defined in table 5.13.3.2.2-1. + +**Table 5.13.3.2.2-1: Resource URI variables for resource "NP Configurations"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +#### 5.13.3.2.3 Resource methods + +##### 5.13.3.2.3.1 GET + +The GET method allows to read all active configurations indicated by the resource URI as defined in clause 5.13.3.2.2. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.13.3.2.3.1-1 and table 5.13.3.2.3.1-2. + +**Table 5.13.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.13.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(NpConfiguration) | 0..N | 200 OK | The NP configuration information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.13.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.13.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.13.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.13.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.13.3.2.3.4 POST + +The POST method creates a new configuration resource for a given SCS/AS. The SCS/AS shall initiate the HTTP POST request message and the SCEF shall respond to the message. The SCEF shall construct the URI of the created resource. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.13.3.2.3.4-1 and table 5.13.3.2.3.4-2. + +**Table 5.13.3.2.3.4-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.13.3.2.3.4-2: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|----------------|---------------------------------------------------------------------------------------------------------------------------------| +| | Data type | Cardinality | Response codes | Remarks | +| | NpConfiguration | 1 | | Parameters to create a new configuration to configure network parameters with the SCEF. | +| Response body | NpConfiguration | 1 | 201 Created | The configuration was created successfully.
The URI of the created resource shall be returned in the "Location" HTTP header. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | +| | ProblemDetails | 0..1 | 404 Not Found | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.13.5.3. + +**Table 5.13.3.2.3.4-3: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-network-parameter-configuration/v1/
{scsAsId}/configurations/{configurationId} | + +### 5.13.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +## 5.13.3.3 Resource: Individual NP Configuration + +### 5.13.3.3.1 Introduction + +This resource allows an SCS/AS to query, update and delete a network parameter configuration indicated by the resource URI as defined in clause 5.13.3.3.2. + +### 5.13.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-network-parameter-configuration/v1/{scsAsId}/configurations/{configurationId} + +This resource shall support the resource URI variables defined in table 5.13.3.2-1. + +**Table 5.13.3.2-1: Resource URI variables for resource "Individual NP Configuration"** + +| Name | Data type | Definition | +|-----------------|-----------|-------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | +| configurationId | string | Identifier of the configuration resource. | + +### 5.13.3.3.3 Resource methods + +#### 5.13.3.3.3.1 GET + +The GET method allows to read an active configuration indicated by the resource URI as defined in subclause 5.13.3.3.2. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.13.3.3.3.1-1 and table 5.13.3.3.3.1-2. + +**Table 5.13.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|------|-----------|-------------|---------| +| | | | | + +**Table 5.13.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NpConfiguration | 1 | 200 OK | The configuration information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.13.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.13.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.13.3.3.3.2 PUT + +The PUT method modifies an existing configuration indicated by the resource URI as defined in clause 5.13.3.3.2. The SCS/AS shall initiate the HTTP PUT request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.13.3.3.3.2-1 and table 5.13.3.3.3.2-2. + +**Table 5.13.3.3.3.2-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.13.3.3.3.2-2: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------|-------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NpConfiguration | 1 | Update of network parameter(s) for an existing Configuration. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NpConfiguration | 1 | 200 OK | The resource was updated successfully.
The SCEF shall return an updated Configuration information in the response. | +| | none | | 204 No Content | The resource was updated successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.13.5.3. + +**Table 5.13.3.3.3.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.13.3.3.3.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.13.3.3.3.3 PATCH + +The PATCH method shall be used to update some properties in an existing configuration indicated by the Resource URI as defined in clause 5.13.3.3.2. The SCS/AS shall initiate the HTTP PATCH request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.13.3.3.3-1 and table 5.13.3.3.3-2. + +**Table 5.13.3.3.3.3-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.13.3.3.3.3-2: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|----------------------|-------------|-------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | NpConfigurationPatch | 1 | Partial update an existing network parameter configuration. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | NpConfiguration | 1 | 200 OK | The configuration was updated successfully.
The SCEF shall return an updated configuration information in the response. | +| | none | | 204 No Content | The configuration was updated successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.13.5.3. + +**Table 5.13.3.3.3.3-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.13.3.3.3.3-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.13.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.13.3.3.3.5 DELETE + +The DELETE method deletes an existing configuration resource "Individual NP Configuration". The SCS/AS shall initiate the HTTP DELETE request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.13.3.3.3.5-1 and table 5.13.3.3.3.5-2. + +**Table 5.13.3.3.5-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | Cardinality | Remarks | +|------|-----------|-------------|---------| +| N/A | | | | + +**Table 5.13.3.3.5-2: Data structures supported by the DELETE request/response on the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|---------------------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(ConfigResult) | 1..N | 200 OK | The configuration was terminated successfully, the configuration failure information for group members shall be included if received. | +| | none | | 204 No Content | The configuration was terminated successfully.
The response body shall be empty. | +| | none | | 307 Temporary Redirect | Temporary redirection, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.

Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.13.3.3.5-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.13.3.3.5-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.13.3.4 Void + +## 5.13.3A Notifications + +### 5.13.3A.1 General + +The notifications provided by the NpConfiguration API are specified in this clause. + +**Table 5.13.3A-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|----------------------------|---------------------------|---------------------------------|--------------------------------------------------------------------| +| Configuration Notification | {notificationDestination} | POST | Report a grouping configuration result from the SCEF to the SCS/AS | + +## 5.13.3A.2 Configuration Notification + +### 5.13.3A.2.1 Description + +The Configuration Notification allows the SCEF to send notifications about grouping configuration result to the SCS/AS. + +### 5.13.3A.2.2 Target URI + +The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 5.13.3A.2.2-1. + +**Table 5.13.3A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|-------------------------|-----------|-----------------------------------------------------------------------------------------------------------------| +| notificationDestination | Link | Callback reference provided by the SCS/AS during creation or modification of the NP configuration subscription. | + +### 5.13.3A.2.3 Standard Methods + +#### 5.13.3A.2.3.1 Notification via POST + +The HTTP POST method reports the grouping configuration results for a NP configuration subscription. The SCEF shall initiate the HTTP POST request message and the SCS/AS shall respond to the message. + +This method shall support the request data structures specified in table 5.13.3A.2.3.1-1 and the response data structures and response codes specified in table 5.13.3A.2.3.1-2. + +**Table 5.13.3A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|---------------------------|-------------|----------------------------------------------------------------------| +| ConfigurationNotification | 1 | The grouping configuration result notification provided by the SCEF. | + +**Table 5.13.3A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| none | | 204 No Content | The notification is received successfully. | +| none | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.13.3A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.13.3A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +#### 5.13.3a.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the ConfigurationNotification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +### 5.13.4 Used Features + +The table below defines the features applicable to the NpConfiguration API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.13.4-1: Features used by NpConfiguration API** + +| Feature Number | Feature | Description | +|----------------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 2 | Notification_test_event | The testing of notification connection is supported according to clause 5.2.5.3. | +| 3 | NpExpiry_5G | The network parameter expiry is supported. This feature may only be supported in 5G. | +| 4 | Enhanced_param_configuring | This feature supports the co-existence of multiple event configurations for target UE(s) if there are parameters affecting periodic RAU/TAU timer and/or Active Time. | +| 5 | UEId_retrieval | This feature supports AF specific UE ID retrieval.
The feature is not applicable to pre-5G (e.g. 4G). | + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification". +Description: A clear textual description of the feature. + +## 5.13.5 Error handling + +### 5.13.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.13.5.2 Protocol Errors + +In this release of the specification, there are no additional protocol errors applicable for the NpConfiguration API. + +### 5.13.5.3 Application Errors + +The application errors defined for the NpConfiguration API are listed in table 5.13.5.3-1. + +**Table 5.13.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|------------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| PARAMETER_OUT_OF_RANGE | 403 Forbidden | Indicates that the resource is not allowed to be created since one or more of the received parameters are out of range defined by operator policies. | | +| REQUEST_NOT_AUTHORIZED | 403 Forbidden | Indicates that the AF specific UE ID retrieval request is not authorized. | UEId_retrieval | +| UE_ID_NOT_AVAILABLE | 404 Not Found | Indicates that the AF specific UE ID is not available. | UEId_retrieval | +| UE_NOT_FOUND | 404 Not Found | Indicates that the requested UE address is not found. | UEId_retrieval | + +## 5.14 AsSessionWithQoS API + +### 5.14.1 Overview + +The AsSessionWithQoS API is a RESTful API that allows the SCS/AS to set up a session with SCEF with required QoS based on the application and service requirement. The AsSessionWithQoS API defines a set of data models, resources and the related procedures for the creation and management of the AS sessions with required QoS. The corresponding JSON schema for the representation of the resources and operations defined by the AsSessionWithQoS API is provided in its complete form in Annex A.14. + +### 5.14.2 Data model + +#### 5.14.2.1 Resource data types + +##### 5.14.2.1.1 Introduction + +This clause defines data structures to be used in resource representations, including subscription resources. + +Table 5.14.2.1.1-1 specifies data types re-used by the AsSessionWithQoS API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the AsSessionWithQoS API. + +**Table 5.14.2.1.1-1: AsSessionWithQoS API re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|------------------------------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| AcceptableServiceInfo | 3GPP TS 29.514 [52] | Acceptable maximum requested bandwidth. | | +| AlternativeServiceRequirementsData | 3GPP TS 29.514 [52] | Contains alternative QoS related parameters and a reference to them. | | +| AverWindow | 3GPP TS 29.571 [45] | Averaging Window. | EnQoSMon | +| AverWindowRm | 3GPP TS 29.571 [45] | This data type is defined in the same way as the "AverWindow" data type, but with the OpenAPI "nullable: true" property. | EnQoSMon | +| BatOffsetInfo | 3GPP TS 29.514 [52] | Contains the offset of the BAT and the optionally adjusted periodicity. | | +| BitRate | 3GPP TS 29.571 [45] | String representing a bit rate that shall be formatted as follows:
Pattern: '^\\d+(\\.\\d+)? (bps Kbps Mbps Gbps Tbps)\$'
Examples:
"125 Mbps", "0.125 Gbps", "125000 Kbps" | | +| BitRateRm | 3GPP TS 29.571 [45] | This data type is defined in the same way as the "BitRate" data type, but with the OpenAPI "nullable: true" property. | | +| Dnn | 3GPP TS 29.571 [45] | Identifies a DNN. | | +| EthFlowDescription | 3GPP TS 29.514 [52] | Defines a packet filter for an Ethernet flow.(NOTE 1) | | +| EventsSubscReqData | 3GPP TS 29.514 [52] | Identifies the events the application subscribes to. | EnQoSMon | +| EventsSubscReqDataRm | 3GPP TS 29.514 [52] | This data type is defined in the same way as the "EventsSubscReqData" data type, but with the OpenAPI "nullable: true" property | EnQoSMon | +| ExtMaxDataBurstVol | 3GPP TS 29.571 [45] | Unsigned integer indicating Maximum Data Burst Volume (see clauses 5.7.3.7 and 5.7.4 of 3GPP TS 23.501 [8]), expressed in Bytes.
Minimum = 4096. Maximum = 2000000. | | +| ExtMaxDataBurstVolRm | 3GPP TS 29.571 [45] | This data type is defined in the same way as the "ExtMaxDataBurstVol" data type, but with the OpenAPI "nullable: true" property. | | +| ExternalGroupId | 5.2.1.3.2 | Represents an external group identifier. | GMEC_5G | +| Gpsi | 3GPP TS 29.571 [45] | Represents a GPSI. | GMEC_5G | +| IpAddr | 3GPP TS 29.571 [45] | UE IP Address. | | +| MacAddr48 | 3GPP TS 29.571 [45] | MAC Address. | | +| MediaType | 3GPP TS 29.514 [52] | Indicates the media type of a single-modal data flow of a multi-modal service. | MultiMedia | +| MultiModalId | 3GPP TS 29.514 [52] | Represents multi-modal service identifier. | MultiMedia | +| PacketDelBudget | 3GPP TS 29.571 [45] | Unsigned integer indicating Packet Delay Budget (see clauses 5.7.3.4 and 5.7.4 of 3GPP TS 23.501 [8]), expressed in milliseconds.
Minimum = 1. | | +| PacketDelBudgetRm | 3GPP TS 29.571 [45] | This data type is defined in the same way as the "PacketDelBudget" data type, but with the OpenAPI "nullable: true" property. | | +| PacketErrRate | 3GPP TS 29.571 [45] | String representing Packet Error | | + +| | | | | +|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | |

Rate (see clauses 5.7.3.5 and 5.7.4 of 3GPP TS 23.501 [8]), expressed as a "scalar x 10-k" where the scalar and the exponent k are each encoded as one decimal digit.
Pattern: '^[0-9]E-[0-9]'

Examples:
Packer Error Rate 4 \times 10^{-6} shall be encoded as "4E-6".
Packer Error Rate 10^{-2} shall be encoded as "1E-2".

| | +|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| PacketErrRateRm | 3GPP TS 29.571 [45] | This data type is defined in the same way as the "PacketErrRate" data type, but with the OpenAPI "nullable: true" property. | | +| PdvMonitoringReport | 3GPP TS 29.514 [52] | Represents a PDV monitoring report. | | +| PeriodicityInfo | 3GPP TS 29.514 [52] | Indicates the time period between the start of the two data bursts in Uplink and/or Downlink direction. | | +| PduSetQosPara | 3GPP TS 29.571 [45] | Represents the PDU Set level QoS parameters. | | +| PduSetQosParaRm | 3GPP TS 29.571 [45] | Represents the PDU Set level QoS parameters to be modified. | | +| PlmnIdNid | 3GPP TS 29.571 [45] | Identifies the network: the PLMN Identifier (the mobile country code and the mobile network code) or the SNPn Identifier (the PLMN Identifier and the NID). | | +| Port | 5.2.1.3.2 | Unsigned integer with valid values between 0 and 65535 representing a port. | ListUE_5G | +| ProblemDetails | 5.2.1.2.12 | Problem Details when returning an error response. | | +| ProtoDesc | 3GPP TS 29.514 [52] | Represents Protocol description of the media flow | | +| RatType | 3GPP TS 29.571 [45] | Identifies the RAT Type. | | +| ReportingFrequency | 3GPP TS 29.512 [8] | Indicates the frequency for the reporting, such as event triggeredand/or periodic. (NOTE 2) | | +| RequestedQosMonitoringParameter | 3GPP TS 29.512 [8] | Indicates the QoS information to be measured, e.g. UL packet delay, DL packet delay or round trip packet delay between the UE and the UPF is to be monitored when the QoS Monitoring for packet delay is enabled for the service data flow. (NOTE 2) | | +| ServAuthInfo | 3GPP TS 29.514 [52] | The authorization result of a request for QoS / QoS monitoring. | EnQoSMon | +| Snssai | 3GPP TS 29.571 [45] | Identifies the S-NSSAI. | | +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.14.4-1. | | +| TscailInputContainer | 3GPP TS 29.514 [52] | TSCAI Input information container. | TSC_5G, MultiMedia | +| TscPriorityLevel | 3GPP TS 29.514 [52] | Represents priority of TSC Flows. | TSC_5G, MultiMedia | +| TscPriorityLevelRm | 3GPP TS 29.514 [52] | Represents the same as the TscPriorityLevel data type, but with the OpenAPI "nullable: true" property. | TSC_5G, MultiMedia | +| TsnQosContainer | 3GPP TS 29.514 [52] | Represents individual QoS parameters | MultiMedia | +| TsnQosContainerRm | 3GPP TS 29.514 [52] | Represents the same as the TsnQosContainer data type, but with the OpenAPI "nullable: true" property. | MultiMedia | +| Uinteger | 3GPP TS 29.571 [45] | Unsigned Integer, i.e. only value 0 and integers above 0 are permissible.
Minimum = 0. | | +| UintegerRm | 3GPP TS 29.571 [45] | This data type is defined in the same way as the "Uinteger" data type, but with the OpenAPI "nullable: true" property. | | +| UplinkDownlinkSupport | 3GPP TS 29.514 [52] | Provides L4S support information. | L4S | +| NOTE 1: In order to support a set of MAC addresses with a specific range in the traffic filter, feature MacAddressRange_5G as specified in clause 5.14.4 shall be supported. | | | | +| NOTE 2: In order to support QoS Monitoring, feature QoSMonitoring_5G as specified in | | | | + +| | | +|-----------------------------------|--| +| clause 5.14.4 shall be supported. | | +|-----------------------------------|--| + +Table 5.14.2.1.1-2 specifies the data types defined for the AsSessionWithQoS API. + +**Table 5.14.2.1.1-2: AsSessionWithQoS API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|-----------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| +| AdditionalInfoAsSessionWithQos | 5.14.2.1.10 | Describes additional error information specific for this API. | | +| AsSessionWithQoSSubscription | 5.14.2.1.2 | Represents an individual AS session with required QoS subscription resource. | | +| AsSessionWithQoSSubscriptionPatch | 5.14.2.1.3 | Represents parameters to modify an AS session with specific QoS subscription. | | +| AsSessionMediaComponent | 5.14.2.1.13 | Represents media component data for a multi-modal service. It contains service data flow information for a single modal data flow of a multi-modal service. | MultiMedia | +| AsSessionMediaComponentRm | 5.14.2.1.14 | Represents the same as the AsSessMediaComponent data type but with the "nullable: true" property. | MultiMedia | +| MultiModalFlows | 5.14.2.1.15 | Represents flow information within a single-modal data flow for a multi-modal service. | MultiMedia | +| ProblemDetailsAsSessionWithQoS | 5.14.2.1.11 | ProblemDetails as defined in clause 5.2.12.12 extended with specific error information for this API, as described in AdditionalInfoAsSessionWithQos. | | +| QosMonitoringInformation | 5.14.2.1.6 | Represents QoS monitoring information. | QoSMonitoring_5G | +| QosMonitoringInformationRm | 5.14.2.1.7 | Represents the same as the QosMonitoringInformation data type but with the "nullable: true" property. | QoSMonitoring_5G | +| QosMonitoringReport | 5.14.2.1.8 | Represents a QoS monitoring report. | QoSMonitoring_5G | +| TscQosRequirement | 5.14.2.1.9 | Represents QoS requirements for time sensitive communication. | TSC_5G
XRM_5G | +| TscQosRequirementRm | 5.14.2.1.10 | Represents the same as the TscQosRequirement data type but with the "nullable: true" property. | TSC_5G
XRM_5G | +| UserPlaneEvent | 5.14.2.2.3 | Represents the user plane event. | enNB | +| UserPlaneEventReport | 5.14.2.1.5 | Represents an event report for user plane. | enNB | +| UserPlaneNotificationData | 5.14.2.1.4 | Represents the parameters to be conveyed in a user plane event(s) notification. | enNB | +| UeAddInfo | 5.14.2.1.16 | Represents the UE address information. | ListUE_5G | + +#### 5.14.2.1.2 Type: AsSessionWithQoSSubscription + +This type represents an AS session request with specific QoS for the service provided by the SCS/AS to the SCEF via T8 interface. The structure is used for subscription request and response. + +**Table 5.14.2.1.2-1: Definition of type AsSessionWithQoSSubscription** + +| Attribute name | Data type | Cardinality | Description | Applicability
(NOTE 1) | +|-------------------------|-------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| self | Link | 0..1 | Link to the resource "Individual AS Session with Required QoS Subscription".
This parameter shall be supplied by the SCEF in HTTP responses. | | +| dnn | Dnn | 0..1 | Identifies a DNN, a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only.
(NOTE 3) | | +| snssai | Snssai | 0..1 | Identifies an S-NSSAI. (NOTE 3) | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7.
This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| notificationDestination | Link | 1 | Contains the URL to receive the notification bearer level event(s) from the SCEF. | | +| exterAppId | string | 0..1 | Identifies the external Application Identifier.
(NOTE 2) (NOTE 9) (NOTE 11) | AppId
ListUE_5G
GMEC_5G | +| extGroupId | ExternalGroupId | 0..1 | Identifies a group of UE(s).
(NOTE 10) | GMEC_5G | +| gpsi | Gpsi | 0..1 | Identifies a UE using its GPSI.
(NOTE 10) | GMEC_5G | +| flowInfo | array(FlowInfo) | 0..N | Describe the IP data flow which requires QoS.
(NOTE 2) (NOTE 7) (NOTE 9) (NOTE 11) | | +| ethFlowInfo | array(EthFlowDescription) | 0..N | Identifies Ethernet packet flows.
(NOTE 2) (NOTE 6) (NOTE 11) | EthAsSessionQoS_5G
GMEC_5G | +| enEthFlowInfo | array(EthFlowInfo) | 0..N | Identifies the Ethernet flows which require QoS. Each Ethernet flow consists of a flow identifier and the corresponding UL and/or DL flows.
(NOTE 2) (NOTE 6) (NOTE 11) | EnEthAsSessionQoS_5G
GMEC_5G | +| qosReference | string | 0..1 | Identifies a pre-defined QoS information.
(NOTE 4) (NOTE 5) | | +| altQoSReferences | array(string) | 0..N | Identifies an ordered list of pre-defined QoS information. The lower the index of the array for a given entry, the higher the priority.
(NOTE 4) | AlternativeQoS_5G | +| altQoSReqs | array(AlternativeServiceRequirementsData) | 0..N | Identifies an ordered list of alternative service requirements that include individual QoS parameter sets. The lower the index of the array for a given entry, the higher the priority. (NOTE 4) | AltQoSWithinDParams_5G | +| disUeNotif | boolean | 0..1 | Indicates whether to disable QoS flow parameters signalling to the UE when the SMF is notified by the NG-RAN of changes in the fulfilled QoS situation. The fulfilled situation is either the QoS profile or an Alternative QoS Profile.

- true: the QoS flow parameters signalling to the UE is disabled;
- false (default): the QoS flow parameters signalling to the UE is not disabled. | DisableUENotification_5G | +| uelpv4Addr | Ipv4Addr | 0..1 | The Ipv4 address of the UE.
(NOTE 2) | | +| ipDomain | string | 0..1 | The IPv4 address domain identifier.
The attribute may only be provided if the | | + +| | | | | | +|--|--|--|----------------------------------|--| +| | | | uelpv4Addr attribute is present. | | +|--|--|--|----------------------------------|--| + +| | | | | | +|-------------------------|------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| uelpv6Addr | Ipv6Addr | 0..1 | The Ipv6 address of the UE.
(NOTE 2) | | +| macAddr | MacAddr48 | 0..1 | Identifies the MAC address.
(NOTE 2) | EthAsSessionQoS_5G | +| listUeAddrs | array(UeAddInfo) | 0..N | Identifies the list of UE address(es).
(NOTE 9) (NOTE 12) | ListUE_5G | +| usageThreshold | UsageThreshold | 0..1 | Time period and/or traffic volume in which the QoS is to be applied. | | +| sponsorInfo | SponsorInformation | 0..1 | Indicates a sponsor information | | +| qosMonInfo | QosMonitoringInformation | 0..1 | Qos Monitoring information. It can be present when the event "QOS_MONITORING" is subscribed. | QoSMonitoring_5G | +| directNotifInd | boolean | 0..1 | Indicates whether the direct event notification is requested.

- true: the direct event notification is requested;
- false (default): the direct event notification is not requested. | ExposureToEAS | +| tscQosReq | TscQosRequirement | 0..1 | Contains the QoS requirements for time sensitive communication. (NOTE 5) | TSC_5G
XRM_5G | +| requestTestNotification | boolean | 0..1 | Set to true by the SCS/AS to request the SCEF to send a test notification as defined in clause 5.2.5.3. Set to false or omitted otherwise. | Notification_test_event | +| websocketNotifConfig | WebsockNotifConfig | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 5.2.5.4. | Notification_websocket | +| events | array(UserPlaneEvent) | 0..N | Corresponds to the list of user plane event(s) to which the SCS/AS requests to subscribe to. | enNB | +| multiModalId | MultiModalId | 0..1 | Multi-modal Service Identifier, as defined in 3GPP TS 29.514 [52]. | MultiMedia | +| multiModDatFlows | map(AsSessionMediaComponent) | 0..N | Each element of the map represents Media Component data for a single-modal data flow(s) of a multi-modal service. The key of the map is the attribute "medCompN".
(NOTE 8) | MultiMedia | +| l4sInfo | UplinkDownlinkSupport | 0..1 | Provides L4S support information. | L4S | +| pduSetQos | PduSetQosPara | 0..1 | Contains the PDU Set QoS Parameters which are used to support PDU Set based QoS handling. | PDUSetHandling | +| rTLatencyInd | boolean | 0..1 | Indicates the service data flow needs to meet the Round-Trip (RT) latency requirement of the service, when it is included and set to "true". The default value is "false" if omitted. | RTLatency | +| protoDesc | ProtoDesc | 0..1 | Protocol description for PDU Set identification and end of Data burst indication in UPF | PDUSetHandling
PowerSaving | +| periodInfo | PeriodicityInfo | 0..1 | Indicates the time period between the start of the two data bursts in Uplink and/or Downlink direction. | PowerSaving | +| pdvMon | QosMonitoringInformation | 0..1 | Contains the Packet Delay Variation information for the subscribed report. It shall be present when the event "PACK_DELAY_VAR" is subscribed. | EnQoSMon | +| qosDuration | DurationSec | 0..1 | Contains the QoS duration to transfer data traffic transmission (e.g., AI/ML transmission). The minimum value of the QoS duration shall be 60 sec. | QoSTiming_5G | +| qosInactInt | DurationSec | 0..1 | Contains the QoS inactivity interval for the given data traffic transmission (e.g., AI/ML transmission). The minimum value of the QoS inactivity interval shall be 60 sec. | QoSTiming_5G | +| rttMon | QosMonitoringInform | 0..1 | Contains the round-trip delay over two | EnQoSMon | + +| | | | | | +|----------------|--------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| | ation | | service data flow information for the subscribed report.
It shall be provided for "RT_DELAY_TWO_QOS_FLOWS" event. | | +| qosMonDatRate | QosMonitoringInformation | 0..1 | Contains the data rate measurements information for the subscribed report. It shall be present when the event "QOS_MONITORING" is subscribed and data rate measurements are required.
(NOTE 12) | EnQoSMonListUE_5G | +| avrgWndw | AverWindow | 0..1 | Averaging window for the calculation of the data rate for the service data flow. It may be present when the "qosMonDatRate" attribute is present. | XRM_5G | +| servAuthInfo | ServAuthInfo | 0..1 | Indicates the authorization result for the QoS monitoring request.
Supplied by the NEF. | EnQoSMon | +| qosMonConReq | QosMonitoringInformation | 0..1 | Contains the requirements of the congestion information (ECN marking percentage) monitoring and reporting. It shall be present when the event "QOS_MONITORING" is subscribed and congestion information measurements are required. | EnQoSMon | +| listUeConsDtRt | array(IpAddr) | 0..N | Identifies the list of UE addresses subject for Consolidated Data Rate monitoring.
(NOTE 12) | ListUE_5G | + +NOTE 1: Properties marked with a feature as defined in clause 5.14.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +NOTE 2: When the GMEC\_5G feature is not supported, one of "uelpv4Addr", "uelpv6Addr" or "macAddr" or "listUeAddrs" shall be included. If ipv4 or ipv6 address is provided, IP flow information shall be provided. If MAC address is provided and the AppId feature is not supported, Ethernet flow information (either "ethFlowInfo", or if the feature EnEthAsSessionQoS\_5G is supported, "enEthFlowInfo") shall be provided. If the AppId feature is supported, one of IP flow information, Ethernet flow information (if EthAsSessionQoS\_5G and/or EnEthAsSessionQoS\_5G is supported) or External Application Identifier shall be provided. + +NOTE 3: The property is only applicable for the NEF. + +NOTE 4: The attributes "altQoSReferences" and "altQoSReqs" are mutually exclusive. The attributes "qosReference" and "altQoSReqs" are also mutually exclusive. + +NOTE 5: The attributes "reqGbrDI", "reqGbrUI", "reqMbrDI", "reqMbrUI", "maxTscBurstSize", "req5Gsdelay", "reqPer" (if the ExtQoS\_5G feature is supported), and "priority" within the "tscQoSReq" attribute may be provided only if the "qosReference" attribute is not provided. + +NOTE 6: When the Ethernet flow information is provided and, the EthAsSessionQoS\_5G and EnEthAsSessionQoS\_5G features are supported, either the "ethFlowInfo" or the "enEthFlowInfo" shall be provided, but not both simultaneously. + +NOTE 7: The "tosTC" attribute of the "flowInfo" attribute may only be present if the "ToSTC\_5G" feature is supported. + +NOTE 8: The attributes "exterAppId", "flowInfo", "ethFlowInfo", "enEthFlowInfo", "qosReference", "altQoSReferences", "altQoSReqs", "tscQoSReq", "qosMonInfo" may be provided only if the "multiModDatFlows" attribute is not provided. + +NOTE 9: When the "ListUE\_5G" feature is supported, the "listUeAddrs" attribute shall be provided, and either "exterAppId" attribute or "flowInfo" attribute shall be provided. + +NOTE 10: When the GMEC\_5G feature is supported and the target UE(s) are not identified by UE address(es) ("uelpv4Addr", "uelpv6Addr", "macAddr", or "listUEAddrs"), the "extGroupId" attribute and the "gpsi" attribute are mutually exclusive. Either one of them shall be provided. If either the "gpsi" attribute or the "extGroupId" attribute are present, then neither the "uelpv4Addr" attribute, the "uelpv6Addr" attribute nor the "macAddr" attribute shall be included. + +NOTE 11: When the GMEC\_5G feature is supported, either the "exterAppId" attribute, "flowInfo" attribute or Ethernet flow information (either "ethFlowInfo" attribute or "enEthFlowInfo" attribute) shall be provided. + +NOTE 12: When the "ListUE\_5G" feature is supported and the "qosMonDatRate" attribute is provided, the "consDataRateThrDI" and "consDataRateThrUI" attributes contained in "qosMonDatRate" attribute indicate the upper bound of the aggregated DL/UL data rate and by default, are applicable to the list of UEs specified by the "listUeAddrs" attribute. If the "listUeConsDtRt" attribute is also provided, then it has to be the subset of "listUeAddrs" attribute. + +Editor's Note: It is FFS whether other IEs within the "tscQoSReq" attribute than "req5Gsdelay" attribute can apply for multi-modal communication services. + +Editor's Note: It is FFS whether the port number requires the transport protocol (like UDP, TCP) for completion or not. + +Editor's Note: Whether the rttMon attribute is needed or the qosMonInfo attribute can be used instead to convey both, packet delay and RTT measurements information requires further discussion. + +Editor's Note: Whether the applicable reporting frequency for the Data Rate QoS monitoring can be event triggered and/or periodic is FFS. + +Editor's Note: It is FFS whether the QoS monitoring requirements for congestion measurements are different than the ones for packet delay, i.e., it is FFS whether reporting period and reporting frequency apply, or different criteria needs to be applied. + +### 5.14.2.1.3 Type: AsSessionWithQoSSubscriptionPatch + +This type represents an AS session request with specific QoS for the service provided by the SCS/AS to the SCEF via T8 interface. The structure is used for PATCH request. + +**Table 5.14.2.1.3-1: Definition of type AsSessionWithQoSSubscriptionPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------------|-------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| exterAppId | string | 0..1 | Identifies the external Application Identifier. (NOTE 2) (NOTE 8) | AppId
ListUE_5G | +| flowInfo | array(FlowInfo) | 0..N | Describe the data flow which requires QoS. (NOTE 2)(NOTE 5) (NOTE 8) | | +| ethFlowInfo | array(EthFlowDescription) | 0..N | Describes Ethernet packet flows. (NOTE 2) | EthAsSessionQoS_5G | +| enEthFlowInfo | array(EthFlowInfo) | 0..N | Identifies the Ethernet flows which require QoS. Each Ethernet flow consists of a flow identifier and the corresponding UL and/or DL flows. (NOTE 2) | EnEthAsSessionQoS_5G | +| listUeAddrs | array(UeAddrInfo) | 0..N | Identifies the list of UE address(es). (NOTE 8) (NOTE 9) | ListUE_5G | +| qosReference | string | 0..1 | Pre-defined QoS reference. (NOTE 3) (NOTE 4) | | +| altQoSReferences | array(string) | 0..N | Identifiers an ordered list of pre-defined QoS information. The lower the index of the array for a given entry, the higher the priority. (NOTE 3) | AlternativeQoS_5G | +| altQosReqs | array(AlternativeServiceRequirementsData) | 1..N | Identifies an ordered list of alternative service requirements that include individual QoS parameter sets. The lower the index of the array for a given entry, the higher the priority. (NOTE 3) | AltQosWithinDParams_5G | +| disUeNotif | boolean | 0..1 | Indicates whether to disable QoS flow parameters signalling to the UE when the SMF is notified by the NG-RAN of changes in the fulfilled QoS situation. The fulfilled situation is either the QoS profile or an Alternative QoS Profile.

- true: the QoS flow parameters signalling to the UE is disabled;
- false: the QoS flow parameters signalling to the UE is not disabled. | DisableUENotification_5G | +| usageThreshold | UsageThresholdRm | 0..1 | Time period and/or traffic volume in which the QoS is to be applied. | | +| qosMonInfo | QosMonitoringInformationRm | 0..1 | Qos Monitoring information. It can be present when the event "QOS_MONITORING" is subscribed. | QoSMonitoring_5G | +| directNotifInd | boolean | 0..1 | Indicates whether the direct event notification is requested.

- true: the direct event notification is requested;
- false: the direct event notification is not requested. | ExposureToEAS | +| tscQosReq | TscQosRequirementRm | 0..1 | Contains the QoS requirements for time sensitive communication. (NOTE 4) | TSC_5G
MultiMedia | +| notificationDestination | Link | 0..1 | Contains the URL to receive the notification event(s) from the SCEF. | | +| events | array(UserPlaneEvent) | 0..N | Corresponds to the list of user plane event(s) to which the SCS/AS requests to subscribe to. | enNB | +| multiModDatFlows | map(AsSessionMediaComponentRm) | 0..N | Each element of the map represents Media Component data for a single-modal data flow(s) of a multi-modal service. The key of the map is the attribute "medCompN". (NOTE 6) | MultiMedia | +| l4sInfo | UplinkDownlinkSupport | 0..1 | Provides L4S support information. | L4S | +| pduSetQos | PduSetQosParaRm | 0..1 | Contains the PDU Set QoS Parameters which are used to support PDU Set based QoS handling. | PDUSetHandling | +| rTLatencyInd | boolean | 0..1 | Indicates the service data flow needs to | RTLatency | + +| | | | | | +|----------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| | | | meet the Round-Trip (RT) latency requirement of the service, when it is included and set to "true". The default value is "false" if omitted. | | +| protoDesc | ProtoDesc | 0..1 | Protocol description for PDU Set identification and end of Data burst indication in UPF | PDUSetHandling
PowerSaving | +| periodInfo | PeriodicityInfo | 0..1 | Indicates the time period between the start of the two data bursts in Uplink and/or Downlink direction. | PowerSaving | +| pdvMon | QosMonitoringInformationRm | 0..1 | Packet Delay Variation information for the subscribed report. | EnQoSMon | +| qosDuration | DurationSecRm | 0..1 | Contains the QoS duration to transfer data transmission (e.g., AI/ML transmission). The minimum value of the QoS duration shall be 60 sec.. | QoSTiming_5G | +| qosInactInt | DurationSecRm | 0..1 | Contains the QoS inactivity interval for the given data transfer transmission (e.g., AI/ML transmission). The minimum value of the QoS inactivity interval shall be 60 sec. | QoSTiming_5G | +| rttMon | QosMonitoringInformationRm | 0..1 | Contains the round-trip delay over two QoS flows information for the subscribed report. It shall be provided for "RT_DELAY_TWO_QOS_FLOWS" event. | EnQoSMon | +| qosMonDatRate | QosMonitoringInformationRm | 0..1 | Contains the data rate measurements information for the subscribed report. It shall be present when the event "QOS_MONITORING" is subscribed and data rate measurements are modified. (NOTE 9) | EnQoSMon
ListUE_5G | +| avrgWndw | AverWindowRm | 0..1 | Averaging window for the calculation of the data rate for the service data flow. | XRM_5G | +| qosMonConReq | QosMonitoringInformationRm | 0..1 | Contains the requirements of the congestion information (ECN marking percentage) monitoring and reporting. It shall be present when the event "QOS_MONITORING" is subscribed and congestion information measurements are required. | EnQoSMon | +| listUeConsDtRt | array(IpAddr) | 0..N | Identifies the list of UE addresses subject for Consolidated Data Rate monitoring. (NOTE 9) | ListUE_5G | + +NOTE 1: Properties marked with a feature as defined in clause 5.14.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +NOTE 2: One of "exterAppId", "flowInfo" or either "ethFlowInfo" or "enEthFlowInfo" may be provided. + +NOTE 3: The attributes "altQoSReferences" and "altQoSReqs" are mutually exclusive. The attributes "qosReference" and "altQoSReqs" are also mutually exclusive. + +NOTE 4: The attributes "reqGbrDI", "reqGbrUI", "reqMbrDI", "reqMbrUI", "maxTscBurstSize", "req5Gsgdelay", "reqPer" (if the ExtQoS\_5G feature is supported), and "priority" within the "tscQoSReq" attribute may be provided only if the "qosReference" attribute is not provided. + +NOTE 5: The "tosTC" attribute of the "flowInfo" attribute may only be present if the "ToSTC\_5G" feature is supported. + +NOTE 6: The attributes "exterAppId", "flowInfo", "ethFlowInfo", "enEthFlowInfo", "qosReference", "altQoSReferences", "altQoSReqs", "tscQoSReq", "qosMonInfo" may be provided only if the "multiModDatFlows" attribute is not provided. + +NOTE 8: When the "ListUE\_5G" feature is supported, the "listUeAddrs" attribute may be provided, and/or either "exterAppId" attribute or "flowInfo" attribute may be provided. + +NOTE 9: When the "ListUE\_5G" feature is supported and the "qosMonDatRate" attribute is provided, the "consDataRateThrDI" and "consDataRateThrUI" attributes contained in "qosMonDatRate" attribute indicate the upper bound of the aggregated DL/UL data rate and by default, are applicable to the list of UEs specified by the "listUeAddrs" attribute. If the "listUeConsDtRt" attribute is also provided, then it has to be the subset of "listUeAddrs" attribute. + +Editor's Note: It is FFS whether other IEs within the "tscQoSReq" attribute than "req5Gsgdelay" attribute can apply for multi-modal communication services. + +Editor's Note: Whether the applicable reporting frequency for the Data Rate QoS monitoring can be event triggered and/or periodic is FFS. + +Editor's Note: It is FFS whether the QoS monitoring requirements for congestion measurements are different than the ones for packet delay, i.e., it is FFS whether reporting period and reporting frequency apply, or different criteria needs to be applied. + +#### 5.14.2.1.4 Type: UserPlaneNotificationData + +This type represents the parameters which shall be notify the SCS/AS for user plane event(s). + +**Table 5.14.2.1.4-1: Definition of the UserPlaneNotificationData data type** + +| Attribute name | Data type | Cardinality | Description | +|----------------|------------------------------|-------------|-------------------------------------------------------------------------| +| transaction | Link | 1 | Link to the transaction resource to which this notification is related. | +| eventReports | array(UserPlaneEvent Report) | 1..N | Contains the reported event and applicable information | + +#### 5.14.2.1.5 Type: UserPlaneEventReport + +This type represents an event report for user plane. It shall comply with the provisions defined in table 5.14.2.1.5-1. + +**Table 5.14.2.1.5-1: Definition of the UserPlaneEventReport data type** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|-------------------|----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| event | UserPlaneEvent | 1 | Indicates the event reported by the SCEF. | | +| accumulatedUsage | AccumulatedUsage | 0..1 | Contains the applicable information corresponding to the event. | | +| flowIds | array(integer) | 0..N | Identifies the affected flows that were sent during event subscription. It may be omitted when the reported event applies to all the flows sent during the subscription. (NOTE 2) | | +| multiModFlows | array(MultiModalFlows) | 0..N | Each element of the array identifies the flow filters for the multi-modal data flows that were sent during event subscription and that are affected by the reported event. It may be omitted when the reported event applies to all the multi-modal data flows sent during the subscription. (NOTE 2) | MultiMedia | +| appliedQosRef | string | 0..1 | The currently applied QoS reference (or applied individual QoS parameter set, if AltQosWithIndParams_5G is supported). Applicable for event QOS_NOT_GUARANTEED or SUCCESSFUL_RESOURCES_ALLOCATION. When it is omitted and the "event" attribute is QOS_NOT_GUARANTEED, the event report indicates that the lowest priority alternative QoS profile could not be fulfilled either. | AlternativeQoS_5G, AltQosWithIndParams_5G | +| altQosNotSupplInd | boolean | 0..1 | It may be set to true when the "event" attribute is QOS_NOT_GUARANTEED to indicate that alternative service requirements are not supported by the access network. The default value false shall apply if the attribute is not present. | AltQoSProfiles SupportReport | +| plmnId | PlmnIdNid | 0..1 | PLMN Identifier or the SNPN Identifier. It may be present when the reported event is "PLMN_CHG" and which is allowed to be exposed to the AF based on the local policy or local configuration. | enNB_5G | +| qosMonReports | array(QosMonitoringReport) | 0..N | Contains the QoS Monitoring Reporting information. | QoSMonitoring_5G | +| pdvMonReports | array(PdvMonitoringReport) | 0..N | Contains the PDV Monitoring Reporting information. (NOTE 3) | EnQoSMon | +| ratType | RatType | 0..1 | RAT type may be present if applicable, when the notified event is "ACCESS_TYPE_CHANGE" and which is allowed to be exposed to the AF based on the local policy or local configuration. | enNB_5G | +| batOffsetInfo | BatOffsetInfo | 0..1 | The BAT offset and the optionally adjusted periodicity. | EnTSCAC | +| aggrDataRateRpts | array(QosMonitoringReport) | 0..1 | Contains QoS Monitoring for aggregated data rate reporting information. It shall be present when the notified event is "QOS_MONITORING" and data rate measurements are available. | ListUE_5G | +| rttMonReports | array(QosMonitoringReport) | 0..N | Round-Trip delay for the indicated UL and DL QoS flows. It shall be present when the notified event is "RT_DELAY_TWO_QOS_FLOWS". | EnQoSMon | +| qosMonDatRateReps | array(QosMonitoringReport) | 0..1 | Contains QoS Monitoring for data rate reporting information. It shall be present when the notified event is "QOS_MONITORING" and data rate measurements are available. | EnQoSMon | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| qosMonConInfoReports | array(QosMonitoringReport) | 0..N | Contains QoS Monitoring for congestion information (ECN marking percentage). It shall be present when the notified event is "QOS_MONITORING" and congestion measurements are available. | EnQoSMon | +| NOTE 1: Properties marked with a feature as defined in clause 5.14.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | +| NOTE 2: The attributes "flowIds" and "multiModFlows" are mutually exclusive. | | | | | +| NOTE 3: The PdvMonitoringReport API does not include the "flows" attribute in this API. | | | | | + +Editor's Note: Whether the rttMonReports attribute is needed or the qosMonReports attribute can be used instead to convey both, packet delay and RTT measurements reports requires further discussion. + +Editor's Note: If the pdvReport can include maximum and minimum UL delay variation and pdmf indication it is FFS whether the QosMonitoringReport can be used instead. + +5.14.2.1.6 Type: QosMonitoringInformation + +**Table 5.14.2.1.6-1: Definition of type QosMonitoringInformation** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|--------------------|----------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| reqQosMonParams | array(RequestedQosMonitoringParameter) | 1..N | Indicates the QoS information to be measured, e.g. UL packet delay, DL packet delay and/or round trip packet delay between the UE and the UPF is to be monitored when the QoS Monitoring for packet delay is enabled for the service data flow. | | +| repFreqs | array(ReportingFrequency) | 1..N | Indicates the frequency for the reporting, such as event triggered and/or periodic. | | +| repThreshDL | UInteger | 0..1 | Unsigned integer identifying a threshold in units of milliseconds for DL packet delay for packet delay or packet delay variation measurement reports. It shall be present when the "reqQosMonParams" attribute includes "DOWNLINK". | | +| repThreshUL | UInteger | 0..1 | Unsigned integer identifying a threshold in units of milliseconds for UL packet delay for packet delay or packet delay variation measurement reports. It shall be present when the "reqQosMonParams" attribute includes "UPLINK". | | +| repThreshRp | UInteger | 0..1 | Unsigned integer identifying a threshold in units of milliseconds for round trip packet delay for packet delay or packet delay variation measurement reports. It shall be present when the "reqQosMonParams" attribute includes "ROUND_TRIP". | | +| conThreshDL | UInteger | 0..1 | Indicates the downlink threshold for congestion reporting, i.e. for the reporting of the received ECN marking percentage for DL. Only applicable when the "repFreqs" attribute is not supplied or the "repFreqs" is set to "EVENT_DETECTION".
Minimum = 0%. | EnQoSMon | +| conThreshUL | UInteger | 0..1 | Indicates the uplink threshold for the congestion reporting, i.e. for the reporting of the received ECN marking percentage for UL. Only applicable when the "repFreqs" attribute is not supplied or the "repFreqs" is set to "EVENT_DETECTION".
Minimum = 0%. | EnQoSMon | +| waitTime | DurationSec | 0..1 | Indicates the minimum waiting time between subsequent reports. It shall be present when the "repFreqs" attribute includes "EVENT_TRIGGERED". | | +| repPeriod | DurationSec | 0..1 | Indicates the time interval between successive reporting. It shall be present when the "repFreqs" attribute includes "PERIODIC".
If the feature "PacketDelayFailureReport" is supported, it also indicates the time interval at which a measurement failure needs to be reported if no measurement result is provided. It shall be present when the "repFreqs" attribute includes "PERIODIC" or "EVENT_TRIGGERED". | | +| repThreshDatRateDL | BitRate | 0..1 | Indicates the bit rate threshold for the DL. It shall be present when the "reqQosMonParams" attribute includes "DOWNLINK_DATA_RATE". | EnQoSMon | +| repThreshDatRateUL | BitRate | 0..1 | Indicates the bit rate threshold for the UL. It shall be present when the "reqQosMonParams" attribute includes "UPLINK_DATA_RATE". | EnQoSMon | +| consDataRateThrDL | BitRate | 0..1 | Indicates the Downlink Consolidated Data Rate Threshold. | ListUE_5G | + +| | | | | | +|-----------------------|---------|------|-----------------------------------------------------------|-----------| +| consDataRateThr
UI | BitRate | 0..1 | Indicates the Uplink Consolidated Data Rate
Threshold. | ListUE_5G | +|-----------------------|---------|------|-----------------------------------------------------------|-----------| + +Editor's Note: It is FFS whether the event reporting frequency applies for congestion (ECN marking percentage) information. + +#### 5.14.2.1.7 Type: QosMonitoringInformationRm + +This type represents a QoS Monitoring Information which is defined in clause 5.14.2.1.7 but defined with "nullable: true" property so it can be removed in "JSON Merge Patch", as defined in IETF RFC 7396 [39]. It shall comply with the provisions defined in table 5.14.2.1.7-1. + +Duration and volume are also removable in "JSON Merge Patch". + +**Table 5.14.2.1.7-1: Definition of type QosMonitoringInformationRm** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|--------------------|----------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| reqQosMonParams | array(RequestedQosMonitoringParameter) | 0..N | Indicates the QoS information to be measured, e.g. UL packet delay, DL packet delay and/or round trip packet delay between the UE and the UPF is to be monitored when the QoS Monitoring for packet delay is enabled for the service data flow. | | +| repFreqs | array(ReportingFrequency) | 0..N | Indicates the frequency for the reporting, such as event triggered and/or periodic. | | +| repThreshDL | UIntegerRm | 0..1 | Unsigned integer identifying a threshold in units of milliseconds for DL packet delay for packet delay or packet delay variation measurement reports. It shall be present when the "reqQosMonParams" attribute includes "DOWNLINK". | | +| repThreshUL | UIntegerRm | 0..1 | Unsigned integer identifying a threshold in units of milliseconds for UL packet delay for packet delay or packet delay variation measurement reports. It shall be present when the "reqQosMonParams" attribute includes "UPLINK". | | +| repThreshRp | UIntegerRm | 0..1 | Unsigned integer identifying a threshold in units of milliseconds for round trip packet delay for packet delay or packet delay variation measurement reports. It shall be present when the "reqQosMonParams" attribute includes "ROUND_TRIP". | | +| conThreshDL | UIntegerRm | 0..1 | Indicates the downlink threshold for congestion reporting, i.e. for the reporting of the received ECN marking percentage for DL. Only applicable when the "repFreqs" attribute is not supplied or the "repFreqs" is set to "EVENT_DETECTION".
Minimum = 0%. | EnQoSMon | +| conThreshUL | UIntegerRm | 0..1 | Indicates the uplink threshold for congestion reporting, i.e. for the reporting of the received ECN marking percentage for UL. Only applicable when the "repFreqs" attribute is not supplied or the "repFreqs" is set to "EVENT_DETECTION".
Minimum = 0%. | EnQoSMon | +| waitTime | DurationSecRm | 0..1 | Indicates the minimum waiting time between subsequent reports. It shall be present when the "repFreqs" attribute includes "EVENT_TRIGGERED". | | +| repPeriod | DurationSecRm | 0..1 | Indicates the time interval between successive reporting. It shall be present when the "repFreqs" attribute includes "PERIODIC".
If the feature "PacketDelayFailureReport" is supported, it also indicates the time interval at which a measurement failure needs to be reported if no measurement result is provided. It shall be present when the "repFreqs" attribute includes "PERIODIC" or "EVENT_TRIGGERED". | | +| repThreshDatRateDL | BitRateRm | 0..1 | Indicates the bit rate threshold for the DL. It shall be present when the "reqQosMonParams" attribute includes "DOWNLINK_DATA_RATE". | EnQoSMon | +| repThreshDatRateUL | BitRateRm | 0..1 | Indicates the bit rate threshold for the UL. It shall be present when the "reqQosMonParams" attribute includes "UPLINK_DATA_RATE". | EnQoSMon | +| consDataRateThrDL | BitRateRm | 0..1 | Indicates the Downlink Consolidated Data Rate Threshold. | ListUE_5G | + +| | | | | | +|-----------------------|-----------|------|--------------------------------------------------------|-----------| +| consDataRateThr
UI | BitRateRm | 0..1 | Indicates the Uplink Consolidated Data Rate Threshold. | ListUE_5G | +|-----------------------|-----------|------|--------------------------------------------------------|-----------| + +Editor's Note: It is FFS whether the event reporting frequency applies for congestion (ECN marking percentage) information. + +#### 5.14.2.1.8 Type: QosMonitoringReport + +**Table 5.14.2.1.8-1: Definition of type QosMonitoringReport** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|-----------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| ulDelays | array(Uinteger) | 0..N | Uplink packet delay in units of milliseconds. (NOTE 1) | | +| dlDelays | array(Uinteger) | 0..N | Downlink packet delay in units of milliseconds. (NOTE 1) | | +| rtDelays | array(Uinteger) | 0..N | Round trip delay in units of milliseconds. (NOTE 1) | | +| pdmf | boolean | 0..1 | Packet delay measurement failure indicator. When set to true, it indicates that a packet delay failure has occurred. Default value is false if omitted. (NOTE 2) | PacketDelay FailureReport | +| ulDataRate | BitRate | 0..1 | UL data rate. (NOTE 3) | EnQoSMon | +| dlDataRate | BitRate | 0..1 | DL data rate. (NOTE 3) | EnQoSMon | +| ulAggrDataRate | BitRate | 0..1 | Indicates the uplink aggregated Data Rate for the applicable list of UEs provided by AF. | ListUE_5G | +| dlAggrDataRate | BitRate | 0..1 | Indicates the downlink aggregated Data Rate for the applicable list of UEs provided by AF. | ListUE_5G | +| ulConInfo | Uinteger | 0..1 | Uplink congestion information, i.e., percentage of ECN marked packets for the UL. | EnQoSMon | +| dlConInfo | Uinteger | 0..1 | Downlink congestion information, i.e., percentage of ECN marked packets for the DL. | EnQoSMon | +| cimf | boolean | 0..1 | Represents the congestion information measurement failure indicator. When set to "true", it indicates that a congestion information measurement failure has occurred. Default value is "false" if omitted. | EnQoSMon | + +NOTE 1: In this release of the specification the maximum number of elements in the array is 2. +NOTE 2: When the "pdmf" attribute is set to true, "ulDelays", "dlDelays" and "rtDelays" and when the feature "EnQoSMon" is supported, "ulDataRate" and "dlDataRate" shall not be present. +NOTE 3: When the "ulDataRate" and/or the "dlDataRate" attribute are included, the parameters related to packet delay and/or congestion information shall not be present. + +Editor's Note: The presence conditions of the parameters of QosMonitoringReport are to be consolidated/detailed once all the possible reports are specified. + +Editor's Note: Whether the maximum and minimum data rate measurements are reported for the data rates calculated during the waiting time is FFS. + +Editor's Note: It is FFS whether the "cimf" attribute is needed. + +Editor's Note: Whether the "ulCongInfo" and "dlCongInfo" attributes are single or plural is FFS. + +## 5.14.2.1.9 Type: TscQosRequirement + +**Table 5.14.2.1.9-1: Definition of type TscQosRequirement** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|------------------|----------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| reqGbrDl | BitRate | 0..1 | Requested GBR in downlink. | | +| reqGbrUl | BitRate | 0..1 | Requested GBR in uplink. | | +| reqMbrDl | BitRate | 0..1 | Requested MBR in downlink. | | +| reqMbrUl | BitRate | 0..1 | Requested MBR in uplink. | | +| maxTscBurstSize | ExtMaxDataBurstVol | 0..1 | Maximum burst size of the TSC traffic in units of Bytes.
Minimum = 4096, Maximum = 2000000. | | +| req5Gsdelay | PacketDelBudget | 0..1 | Requested Delay of the TSC traffic. | | +| reqPer | PacketErrRate | 0..1 | Requested Packet Error Rate of the TSC traffic. | ExtQoS_5G | +| priority | TscPriorityLevel | 0..1 | Unsigned integer indicating the TSC traffic priority in relation to other TSC and non-TSC traffic. | | +| tscaiTimeDom | UInteger | 0..1 | Indicates the (g)PTP domain that the (TSN)AF is located in. | | +| tscaiInputUl | TscailInputContainer | 0..1 | Transports the input parameters for TSC traffic to construct the TSC Assistance Container in uplink direction.
(NOTE) | | +| tscaiInputDl | TscailInputContainer | 0..1 | Transports the input parameters for TSC traffic to construct the TSC Assistance Container in downlink direction.
(NOTE) | | +| capBatAdaptation | boolean | 0..1 | Indicates the capability for AF to adjust the burst sending time, when it is supported and set to "true".
The default value is "false" if omitted.
(NOTE) | EnTSCAC | + +NOTE: The "burstArrivalTimeWnd" attribute, within the "tscaiInputUl" and/or "tscaiInputDl" attributes, and the "capBatAdaptation" attribute are mutually exclusive. + +## 5.14.2.1.10 Type: TscQosRequirementRm + +**Table 5.14.2.1.10-1: Definition of type TscQosRequirementRm** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|------------------|----------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| reqGbrDl | BitRateRm | 0..1 | Requested GBR in downlink. | | +| reqGbrUl | BitRateRm | 0..1 | Requested GBR in uplink. | | +| reqMbrDl | BitRateRm | 0..1 | Requested MBR in downlink. | | +| reqMbrUl | BitRateRm | 0..1 | Requested MBR in uplink. | | +| maxTscBurstSize | ExtMaxDataBurstVolRm | 0..1 | Maximum burst size of the TSC traffic in units of Bytes.
Minimum = 4096, Maximum = 2000000. | | +| req5Gsdelay | PacketDelBudgetRm | 0..1 | Requested Delay of the TSC traffic. | | +| reqPer | PacketErrRateRm | 0..1 | Requested Packet Error Rate of the TSC traffic. | ExtQoS_5G | +| priority | TscPriorityLevelRm | 0..1 | Unsigned integer indicating the TSC traffic priority in relation to other TSC and non-TSC traffic. | | +| tscaiTimeDom | UIntegerRm | 0..1 | Indicates the (g)PTP domain that the (TSN)AF is located in. | | +| tscaiInputUl | TscailInputContainer | 0..1 | Transports the input parameters for TSC traffic to construct the TSC Assistance Container in uplink direction.
(NOTE) | | +| tscaiInputDl | TscailInputContainer | 0..1 | Transports the input parameters for TSC traffic to construct the TSC Assistance Container in downlink direction.
(NOTE) | | +| capBatAdaptation | boolean | 0..1 | Indicates the capability for AF to adjust the burst sending time, when it is supported and set to "true".
The default value is "false" if omitted.
(NOTE) | EnTSCAC | + +NOTE: The "burstArrivalTimeWnd" attribute, within the "tscaiInputUl" and/or "tscaiInputDl" attributes, and the "capBatAdaptation" attribute are mutually exclusive. + +#### 5.14.2.1.11 Type AdditionalInfoAsSessionWithQos + +**Table 5.14.2.1.11-1: Definition of type AdditionalInfoAsSessionWithQos** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------|-----------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| acceptableServInfo | AcceptableServiceInfo | O | 0..1 | Describes information related to the acceptable service information, i.e., the maximum acceptable bandwidth for an AF session and/or for specific media components. | | + +#### 5.14.2.1.12 Type: ProblemDetailsAsSessionWithQos + +**Table 5.14.2.1.12-1: Definition of type ProblemDetailsAsSessionWithQos as a list of to be combined data types** + +| Data type | Cardinality | Description | Applicability | +|--------------------------------|-------------|-------------------------------------------------------------------------------|---------------| +| ProblemDetails | 1 | Problem details as specified in clause 5.2.12.12 to include an error response | | +| AdditionalInfoAsSessionWithQos | 1 | Describes additional error information specific for this API. | | + +#### 5.14.2.1.13 Type AsSessionMediaComponent + +This type represents media component data for a single-modal data flow of a multi-modal service. It shall comply with the provisions defined in table 5.14.2.1.13-1. + +**Table 5.14.2.1.13-1: Definition of type AsSessionMediaComponent** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|-------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| flowInfos | array(FlowInfo) | 0..N | Contains the IP data flow(s) description for a single-modal data flow. | | +| qosReference | string | 0..1 | Identifies a pre-defined QoS information. | | +| altSerReqs | array(string) | 0..N | Ordered list of alternative service requirements that include a set of QoS references. The lower the index of the array for a given entry, the higher the priority.(NOTE) | | +| altSerReqsData | array(AlternativeServiceRequirementsData) | 0..N | Ordered list of alternative service requirements that include individual QoS parameter sets. The lower the index of the array for a given entry, the higher the priority. (NOTE) | | +| disUeNotif | boolean | 0..1 | Indicates to disable QoS flow parameters signalling to the UE when the SMF is notified by the NG-RAN of changes in the fulfilled QoS situation when it is included and set to "true". The fulfilled situation is either the QoS profile or an Alternative QoS Profile. The default value "false" shall apply, if the attribute is not present and has not been supplied previously. | | +| medCompN | integer | 1 | Identifies the media component number, and it contains the ordinal number of the media component. | | +| medType | MediaType | 0..1 | Indicates the media type of the service. | | +| marBwUI | BitRate | 0..1 | Maximum requested bandwidth for the Uplink. | | +| marBwDI | BitRate | 0..1 | Maximum requested bandwidth for the Downlink. | | +| mirBwUI | BitRate | 0..1 | Minimum requested bandwidth for the Uplink. | | +| mirBwDI | BitRate | 0..1 | Minimum requested bandwidth for the Downlink. | | +| tsnQos | TsnQoSContainer | 0..1 | Transports QoS parameters for TSC traffic. | | +| tscaiInputUI | TscaiInputContainer | 0..1 | Transports TSCAI input parameters for TSC traffic at the ingress interface of the DS-TT/UE (uplink flow direction). | | +| tscaiInputDI | TscaiInputContainer | 0..1 | Transports TSCAI input parameters for TSC traffic at the ingress of the NW-TT (downlink flow direction). | | +| rTLatencyReq | boolean | 0..1 | Indicates the service data flow needs to meet the Round-Trip (RT) latency requirement of the service, when it is included and set to "true". The default value is "false" if omitted. | | +| pduSetQos | PduSetQosPara | 0..1 | PDU Set QoS parameters for XRM traffic. | | +| evSubsc | EventsSubscReqData | 0..1 | Identifies the events the application subscribes to at creation of a media component. (NOTE) | EnQoSMon | + +NOTE: If attribute "evSubsc" is present, one or more of the following IEs may be included: "events", "notifUri", "reqQosMonParams", "qosMon", "qosMonDatRate", "pdvReqMonParams", "pdvMon", "congestMon", "notifCorrelId", "afApplIds", "directNotifInd", "avrgWndw". In addition, when present the attribute "events", one or more of the following Enumeration "AfEvent" may be included: "QOS\_MONITORING", "PACK\_DEL\_VAR", "RT\_DELAY\_TWO\_QOS\_FLOWS". + +Editor's Note: the list of IEs of a AsSessionMediaComponent to complete the QoS parameters developed for the MediaComponent data defined in TS 29.514 and applicable to external AFs is FFS. + +Editor's Note: It is FFS whether the notifUri and notifCorreId attributes may be required for the evSubsc attribute. + +#### 5.14.2.1.14 Type AsSessionMediaComponentRm + +This type represents the AsSessionMediaComponent with the "nullable: true" property. It shall comply with the provisions defined in table 5.14.2.1.14-1 + +**Table 5.14.2.1.14-1: Definition of type AsSessionMediaComponentRm** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| flowInfos | array(FlowInfo) | 0..N | Contains the IP data flow(s) description for a single-modal data flow. | | +| qosReference | string | 0..1 | Identifies a pre-defined QoS information. | | +| altSerReqs | array(string) | 0..N | Ordered list of alternative service requirements that include a set of QoS references. The lower the index of the array for a given entry, the higher the priority.(NOTE) | | +| altSerReqsData | array(AlternativeServiceRequirementsData) | 0..N | Ordered list of alternative service requirements that include individual QoS parameter sets. The lower the index of the array for a given entry, the higher the priority. (NOTE) | | +| disUeNotif | boolean | 0..1 | Indicates to disable QoS flow parameters signalling to the UE when the SMF is notified by the NG-RAN of changes in the fulfilled QoS situation when it is included and set to "true". The fulfilled situation is either the QoS profile or an Alternative QoS Profile. The default value "false" shall apply, if the attribute is not present and has not been supplied previously. | | +| medCompN | integer | 1 | Identifies the media component number, and it contains the ordinal number of the media component. | | +| medType | MediaType | 0..1 | Indicates the media type of the service. | | +| marBwUI | BitRateRm | 0..1 | Maximum requested bandwidth for the Uplink. | | +| marBwDI | BitRateRm | 0..1 | Maximum requested bandwidth for the Downlink. | | +| mirBwUI | BitRateRm | 0..1 | Minimum requested bandwidth for the Uplink. | | +| mirBwDI | BitRateRm | 0..1 | Minimum requested bandwidth for the Downlink. | | +| tsnQos | TsnQoSContainerRm | 0..1 | Transports QoS parameters for TSC traffic. | | +| tscaiInputUI | TscailInputContainer | 0..1 | Transports TSCAI input parameters for TSC traffic at the ingress interface of the DS-TT/UE (uplink flow direction). | | +| tscaiInputDI | TscailInputContainer | 0..1 | Transports TSCAI input parameters for TSC traffic at the ingress of the NW-TT (downlink flow direction). | | +| rTLatencyReq | boolean | 0..1 | Indicates the service data flow needs to meet the Round-Trip (RT) latency requirement of the service, when it is included and set to "true". | | +| pduSetQos | PduSetQosPara | 0..1 | PDU Set QoS parameters for XRM traffic. | | +| evSubsc | EventsSubscReqDataRm | 0..1 | Identifies the events the application subscribes to at creation of a media component. (NOTE) | EnQoSMon | +| NOTE: | If attribute "evSubsc" is present, one or more of the following IEs may be included: "events", "notifUri", "reqQosMonParams", "qosMon", "qosMonDatRate", "pdvReqMonParams", "pdvMon", "congestMon", "notifCorrelId", "afApplds", "directNotifInd", "avrgWndw". In addition, when present the attribute "events", one or more of the following Enumeration "AfEvent" may be included: "QOS_MONITORING", "PACK_DEL_VAR", "RT_DELAY_TWO_QOS_FLOWS". | | | | + +Editor's Note: It is FFS whether the notifUri and notifCorrelId attributes may be required for the evSubsc attribute. + +#### 5.14.2.1.15 Type: MultiModalFlows + +This type represents a flow information within a single-modal data flow. It shall comply with the provisions defined in table 5.14.2.1.15-1. + +**Table 5.14.2.1.15-1: Definition of the type MultiModalFlows** + +| Attribute name | Data type | Cardinality | Description | +|----------------|----------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| medCompN | integer | 1 | It contains the ordinal number of the single-modal data flow. Identifies the single-modal data flow | +| flowIds | array(integer) | 0..N | Identifies the affected flows within the single-modal data flow (identified by the medCompN attribute). It may be omitted when all flows are affected. | + +#### 5.14.2.1.16 Type: UeAddrInfo + +This type represents UEs Address information. It shall comply with the provisions defined in table 5.14.2.1.16-1. + +**Table 5.14.2.1.16-1: Definition of the type UeAddrInfo** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|-----------|-------------|----------------------------------------------------------------------------------------------------------------|---------------| +| uelpAddr | lpAddr | 1 | Identifies the UE IP address. | | +| portNumber | Port | 0..1 | Indicates the UDP or TCP port number associated with the UE IP address as provided in the "uelpAddr" attribute | | + +### 5.14.2.2 Referenced simple data types and enumerations + +#### 5.14.2.2.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +#### 5.14.2.2.2 Simple data types + +The simple data types defined in table 5.14.2.2.2-1 shall be supported. + +**Table 5.14.2.2.2-1: Simple data types** + +| Type name | Description | +|-----------|-------------| +| | | + +#### 5.14.2.2.3 Enumeration: UserPlaneEvent + +The enumeration UserPlaneEvent represents the user plane event. + +**Table 5.14.2.2.3-1: Enumeration UserPlaneEvent** + +| Enumeration value | Description | Applicability (NOTE) | +|---------------------------------|------------------------------------------------------------------------------------|----------------------| +| SESSION_TERMINATION | Indicates that Rx session is terminated. | | +| LOSS_OF_BEARER | Indicates a loss of a bearer. (NOTE 3) | | +| RECOVERY_OF_BEARER | Indicates a recovery of a bearer. (NOTE 3) | | +| RELEASE_OF_BEARER | Indicates a release of a bearer. (NOTE 3) | | +| USAGE_REPORT | Indicates the usage report event. | | +| FAILED_RESOURCES_ALLOCATION | Indicates the resource allocation is failed. | | +| SUCCESSFUL_RESOURCES_ALLOCATION | Indicates the resource allocation is successful. | | +| QOS_GUARANTEED | The QoS targets of one or more SDFs are guaranteed again. | AlternativeQoS_5G | +| QOS_NOT_GUARANTEED | The QoS targets of one or more SDFs are not being guaranteed. | AlternativeQoS_5G | +| QOS_MONITORING | Indicates a QoS monitoring event. | QoSMonitoring_5G | +| ACCESS_TYPE_CHANGE | Indicates an Access type change. (NOTE 2) | enNB_5G | +| PLMN_CHG | Indicates a PLMN change. (NOTE 2) | enNB_5G | +| L4S_NOT_AVAILABLE | The ECN marking for L4S of one or more SDFs is not available. | L4S | +| L4S_AVAILABLE | The ECN marking for L4S of one or more SDFs is available again. | L4S | +| BAT_OFFSET_INFO | Indicates the network provided BAT offset and the optionally adjusted periodicity. | EnTSCAC | +| RT_DELAY_TWO_QOS_FLOWS | Indicates round-trip delay on UL and DL flows over two QoS flows. | EnQoSMon | +| PACK_DELAY_VAR | Indicates Packet Delay Variation is enabled for the SDF. | EnQoSMon | + +NOTE 1: Properties marked with a feature as defined in clause 5.14.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +NOTE 2: The exposure of such network information to the AF needs to be authorized based on the local policy or local configuration. + +NOTE 3: The "LOSS\_OF\_BEARER", RECOVERY\_OF\_BEARER, and RELEASE\_OF\_BEARER only apply to 4G. + +## 5.14.3 Resource structure + +### 5.14.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-as-session-with-qos/v1** + +"apiRoot" is set as described in clause 5.2.4. "apiName" shall be set to "3gpp-as-session-with-qos" and "apiVersion" shall be set to "v1" for the version defined in the present document. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.14.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|------------------------------------------------------|-------------------------------------------|-------------|--------------------------------------------------------------------------| +| AS Session with Required QoS Subscriptions | /{scsAsId}/subscriptions | GET | Get all or queried subscription resources for a given SCS/AS. | +| | | POST | Create a new AS session. | +| Individual AS Session with Required QoS Subscription | /{scsAsId}/subscriptions/{subscriptionId} | GET | Read a subscription resource for a given SCS/AS and a subscription Id. | +| | | PUT | Modify a subscription resource for a given SCS/AS and a subscription Id. | +| | | PATCH | Modify a subscription resource for a given SCS/AS and a subscription Id. | +| | | DELETE | Delete a subscription resource for a given SCS/AS and a subscription Id. | + +## 5.14.3.2 Resource: AS Session with Required QoS subscriptions + +### 5.14.3.2.1 Introduction + +This resource allows the SCS/AS to read all active AS session with required QoS subscription resources, or create a new subscription resource for the SCS/AS. + +### 5.14.3.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-as-session-with-qos/v1/{scsAsId}/subscriptions + +This resource shall support the resource URI variables defined in table 5.14.3.2.2-1. + +**Table 5.14.3.2.2-1: Resource URI variables for resource "AS Session with Required QoS Subscriptions"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +### 5.14.3.2.3 Resource methods + +#### 5.14.3.2.3.1 GET + +The GET method allows to read all or queried active subscriptions for a given SCS/AS. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.14.3.2.3.1-1 and table 5.14.3.2.3.1-2. + +**Table 5.14.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | Applicability | +|-----------|------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------| +| ip-addrs | array(IpAddr) | 0..N | The IP address(es) of the requested UE(s). | enNB | +| ip-domain | string | 0..1 | The IPv4 address domain identifier.
The attribute may only be provided if IPv4 address is included in the ip-addrs query parameter. | enNB | +| mac-addrs | array(MacAddr48) | 0..N | The MAC address(es) of the requested UE(s). | enNB | + +NOTE: Either the "ip-addrs" parameter or the "mac-addrs" parameter may be provided at the same time. If multiple elements are provided in the array structure, then each element shall be treated as a separate query parameter. + +**Table 5.14.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-------------------------------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(AsSessionWithQoSSubscription) | 0..N | 200 OK | The subscription information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.14.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.14.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.14.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.14.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.14.3.2.3.4 POST + +The POST method creates a new subscription resource for a given SCS/AS. The SCS/AS shall initiate the HTTP POST request message and the SCEF shall respond to the message. The SCEF shall construct the URI of the created resource using that URI. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.14.3.2.3.4-1 and table 5.14.3.2.3.4-2. + +**Table 5.14.3.2.3.4-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | Cardinality | Remarks | +|------|-----------|-------------|---------| +| | | | | + +**Table 5.14.3.2.3.4-2: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|-------------------------------------------------------------------------------------------------------|--------------------------------|-------------|------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| | AsSessionWithQoSSubscription | 1 | Parameters to create a subscription for an AS session with required QoS for the service requirement. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | AsSessionWithQoSSubscription | 1 | 201 Created | The subscription was created successfully.
The URI of the created resource shall be returned in the "Location" HTTP header. | +| | ProblemDetailsAsSessionWithQoS | 0..1 | 403 Forbidden | (NOTE 2) | +| | ProblemDetails | 0..1 | 500 Internal Server Error | (NOTE 2) | +| NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. | | | | | +| NOTE 2: Failure cases are described in clause 5.14.5.3. | | | | | + +**Table 5.14.3.2.3.4-3: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-as-session-with-qos/v1/{scsAsId}/subscriptions/{subscriptionId} | + +**Table 5.14.3.2.3.4-4: Headers supported by the 403 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|-----------|---|-------------|-------------------------------------------------------------------------------------| +| Retry-After | string | M | 1 | Indicates the time the NF service consumer has to wait before making a new request. | + +#### 5.14.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.14.3.3 Resource: Individual AS Session with Required QoS Subscription + +#### 5.14.3.3.1 Introduction + +This resource allows an SCS/AS to query, update and delete an AS session with required QoS subscription. + +#### 5.14.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-as-session-with-qos/v1/{scsAsId}/subscriptions/{subscriptionId} + +This resource shall support the resource URI variables defined in table 5.14.3.3.2-1. + +**Table 5.14.3.2.2-1: Resource URI variables for resource "Individual AS Session with Required QoS Subscription"** + +| Name | Data type | Definition | +|----------------|-----------|--------------------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS of type ScsAsId. | +| subscriptionId | string | Identifier of the subscription resource of type string. The subscriptionId corresponds to the stage 2 TLTRI. | + +### 5.14.3.3.3 Resource methods + +#### 5.14.3.3.3.1 GET + +The GET method allows to read a subscription resource. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.14.3.3.3.1-1 and table 5.14.3.3.3.1-2. + +**Table 5.14.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|------|-----------|-------------|---------| +| | | | | + +**Table 5.14.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|------------------------------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | AsSessionWithQoSSubscription | 1 | 200 OK | The subscription information related to the resource URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.14.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.14.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.14.3.3.3.2 PUT + +The PUT method allows changing the service information of an active subscription. The properties "ueIpv4Addr" or "ueIpv6Addr" shall remain unchanged from previously provided value. + +This method shall support request and response data structures, and response codes, as specified in the table 5.14.3.3.3.2-1. + +**Table 5.14.3.3.3.2-1: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|--------------------------------|-------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | AsSessionWithQoSSubscription | 1 | Set up AS session with required QoS. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | AsSessionWithQoSSubscription | 1 | 200 OK | The subscription was modified successfully.
The SCEF shall return an updated subscription in the response content. | +| | none | | 204 No Content | The subscription was updated successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | ProblemDetailsAsSessionWithQoS | 0..1 | 403 Forbidden | (NOTE 2) | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +NOTE 2: Failure cases are described in clause 5.14.5.3. + +**Table 5.14.3.3.3.2-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.14.3.3.3.2-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.14.3.3.3.2-4: Headers supported by the 403 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|-----------|---|-------------|-------------------------------------------------------------------------------------| +| Retry-After | string | M | 1 | Indicates the time the NF service consumer has to wait before making a new request. | + +## 5.14.3.3.3.3 PATCH + +The PATCH method allows to change the service information of an active subscription. + +This method shall support request and response data structures, and response codes, as specified in the table 5.14.3.3.3-1. + +**Table 5.14.3.3.3-1: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------------------------|-------------|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | AsSessionWithQoSSubscriptionPatch | 1 | Partial update of an AS session with required QoS. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | AsSessionWithQoSSubscription | 1 | 200 OK | The subscription was modified successfully.
The SCEF shall return an updated subscription in the response content. | +| | none | | 204 No Content | The subscription was modified successfully. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | ProblemDetailsAsSessionWithQoS | 0..1 | 403 Forbidden | (NOTE 2) | +| | ProblemDetails | 0..1 | 403 Forbidden | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. +NOTE 2: Failure cases are described in clause 5.14.5.3. + +**Table 5.14.3.3.3-2: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.14.3.3.3-3: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.14.3.3.3-4: Headers supported by the 403 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------|-----------|---|-------------|-------------------------------------------------------------------------------------| +| Retry-After | string | M | 1 | Indicates the time the NF service consumer has to wait before making a new request. | + +## 5.14.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +## 5.14.3.3.3.5 DELETE + +The DELETE method deletes the AsSessionWithQoSSubscription resource and terminates the related subscription. The SCS/AS shall initiate the HTTP DELETE request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.14.3.3.3.5-1 and table 5.14.3.3.3.5-2. + +**Table 5.14.3.3.3.5-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | Cardinality | Remarks | +|------|-----------|-------------|---------| +| | | | | + +**Table 5.14.3.3.3.5-2: Data structures supported by the DELETE request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|---------------------------|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The subscription was terminated successfully.
The response body shall be empty. | +| | UserPlaneNotificationData | 1 | 200 OK | The subscription was terminated successfully. The user plane notification data shall be included in the response. | +| | none | | 307 Temporary Redirect | Temporary redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. + +**Table 5.14.3.3.3.5-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.14.3.3.3.5-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +### 5.14.3.4 Void + +## 5.14.3A Notifications + +### 5.14.3A.1 General + +The notifications provided by the AsSessionWithQoS API are specified in this clause. + +**Table 5.14.3A-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|--------------------|-------------------|---------------------------------|--------------------------------------------------------------| +| Event Notification | {notificationUri} | POST | Notify the bearer level event(s) from the SCEF to the SCS/AS | + +### 5.14.3A.2 Event Notification + +#### 5.14.3A.2.1 Description + +The Event Notification allows the SCEF to notify the SCS/AS of the bearer level event(s). + +#### 5.14.3A.2.2 Target URI + +The Callback URI "{notificationUri}" shall be used with the callback URI variables defined in table 5.14.3A.2.2-1. + +**Table 5.14.3A.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|-----------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notificationUri | Link | Reference provided by the SCS/AS when the SCS/AS requests to sponsor the traffic from the beginning or to become the chargeable party at a later point.
This URI shall be provided within the "notificationDestination" attribute in the AsSessionWithQoSSubscription type. | + +#### 5.14.3A.2.3 Standard Methods + +##### 5.14.3A.2.3.1 Notification via POST + +The POST method allows to notify SCS/AS of the bearer level event(s) by the SCEF and the SCS/AS shall respond to the message. + +This method shall support the request data structures specified in table 5.14.3A.2.3.1-1 and the response data structures and response codes specified in table 5.14.3A.2.3.1-2. + +**Table 5.14.3A.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | Cardinality | Description | +|---------------------------|-------------|--------------------------------------------------| +| UserPlaneNotificationData | 1 | Representation of the bearer level notification. | + +**Table 5.14.3A.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | Cardinality | Response codes | Description | +|-----------|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| none | | 204 No Content | This case represents a successful notification of bearer level event(s). | +| none | | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.14.3A.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.14.3A.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +#### 5.14.3A.2.3.2 Notification via Websocket + +If supported by both SCS/AS and SCEF and successfully negotiated, the UserPlaneNotificationData may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4. + +### 5.14.4 Used Features + +The table below defines the features applicable to the AsSessionWithQoS API. Those features are negotiated as described in subclause 5.2.7. + +**Table 5.14.4-1: Features used by AsSessionWithQoS API** + +| Feature Number | Feature | Description | +|----------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 5.2.5.4. This feature requires that the Notification_test_event feature is also supported. | +| 2 | Notification_test_event | The testing of notifications connections is supported according to clause 5.2.5.3. | +| 3 | EthAsSessionQoS_5G | Setting up required QoS for Ethernet UE. This feature may only be supported in 5G. | +| 4 | MacAddressRange_5G | Indicates the support of a set of MAC addresses with a specific range in the traffic filter. This feature may only be supported in 5G. | +| 5 | AlternativeQoS_5G | Indicates the support of alternative QoS requirements and the QoS notification (i.e. whether the QoS targets for SDF(s) are not guaranteed or guaranteed again). This feature may only be supported in 5G. | +| 6 | QoSMonitoring_5G | Indicates the support of QoS Monitoring functionality and the report for packet delay monitoring. This feature may only be supported in 5G. | +| 7 | DisableUENotification_5G | Indicates the support of disabling QoS flow parameters signalling to the UE when the SMF is notified by the NG-RAN of changes in the fulfilled QoS situation. This feature may only be supported in 5G. This feature requires that the AlternativeQoS_5G feature is also supported. | +| 8 | TSC_5G | Indicates the support of Time Sensitive Communication. This feature may only be supported in 5G. | +| 9 | AppId | Indicates the support of dynamically providing the Application Identifier via the API. | +| 10 | ExposureToEAS | This feature indicates the support of direct notification in 5GC. This feature requires that the QoSMonitoring_5G feature is also supported. | +| 11 | enNB | Indicates the support of enhancements to the northbound interfaces. | +| 12 | AltQosWithIndParams_5G | This feature indicates the support of provisioning Alternative Service Requirements with individual QoS parameters. This feature requires that the AlternativeQoS_5G feature is also supported. | +| 13 | EnEthAsSessionQoS_5G | Indicates the support of required QoS for Ethernet UE, allowing to indicate separately different UL and/or DL Ethernet flows. This feature may only be supported in 5G. | +| 14 | enNB_5G | Indicates the support of enhancements to the northbound interfaces and only applicable to 5G. | +| 15 | PacketDelayFailureReport | Indicates the support of packet delay failure report as part of QoS Monitoring procedures. This feature requires that QoSMonitoring_5G is supported. This feature may only be supported in 5G. | +| 16 | ToSTC_5G | Indicates the support of Type of Service or Traffic Class. This feature may only be supported in 5G. | +| 17 | EnTSCAC | Indicates the support of extensions to TSCAC and the RAN feedback for BAT offset and adjusted periodicity. This feature may only be supported in 5G, and requires that the TSC_5G feature is also supported. | +| 18 | AltQoSProfilesSupportReport | This feature indicates the support of the report of whether Alternative QoS parameters are supported by the access network. This feature requires that AlternativeQoS_5G and/or AltQosWithIndParams_5G features are also supported. | +| 19 | ExtQoS_5G | This feature indicates the support of extended QoS parameters. This feature may only be supported in 5G. | +| 20 | MultiMedia | Indicates the support for multi-modal or multimedia flows for single UE and multiple UE. This feature may only be supported in 5G. This feature may be used in eXtend Reality (XR) use cases. | +| 21 | ExtErrors | Indicates the support of additional application errors related to authorization or PDU Session availability. | +| 22 | QoSTiming_5G | This feature indicates the support of QoS timing information for the transfer and support of data transmission (e.g., AI/ML transmission). This feature may only be supported in 5G. | +| 23 | ListUE_5G | Indicates the support for the list of UEs This feature may only be supported in 5G. | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 24 | GMEC_5G |

This feature indicates the support of Generic Group Management Exposure and Communication related enhancements.

The following functionalities are supported:

  • - Support AF requested QoS for a UE or group of UE(s) not identified by the UE address.

This feature may only be supported in 5G.

| +| 25 | PDUSetHandling |

This feature indicates the support of PDU Set handling. This feature may be used for eXtended Reality (XR) and interactive media services.

This feature may only be supported in 5G.

| +| 26 | RTLatency |

This feature indicates the support of Round-Trip latency. This feature may be used for eXtended Reality (XR) and interactive media services.

This feature may only be supported in 5G.

| +| 27 | EnQoSMon |

This feature indicates the support of enhanced QoS monitoring functionality, i.e. the report of the congestion information, and/or, the RTT delay over two QoS flows, and/or, the data rate information, and/or, the Packet Delay Variation monitoring.

This feature may only be supported in 5G

| +| 28 | PowerSaving |

This feature indicates the support of the Power Saving for different traffic measurement.

This feature may only be supported in 5G.

| +| 29 | L4S |

This feature indicates the support of the AF indication of ECN marking for L4S support.

This feature may only be supported in 5G.

| +|

Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification".
Description: A clear textual description of the feature.

| | | + +Editor's Note: Whether and/how to indicate the support of end of burst indication, and provision the flow periodicity information within the Power Saving feature is FFS. + +## 5.14.5 Error handling + +### 5.14.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.14.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the AsSessionWithQoS API. + +### 5.14.5.3 Application Errors + +The application errors defined for AsSessionWithQoS API are listed in table 5.14.5.3-1. + +**Table 5.14.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|----------------------------------------------|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| REQUESTED_SERVICE_NOT_AUTHORIZED | 403 Forbidden | The service information provided in the request is rejected. | ExtErrors | +| REQUESTED_SERVICE_TEMPORARILY_NOT_AUTHORIZED | 403 Forbidden | The service information provided in the request is temporarily rejected. | ExtErrors | +| UNAUTHORIZED_SPONSORED_DATA_CONNECTIVITY | 403 Forbidden | The request for sponsored data connectivity is not authorized. | ExtErrors | +| PDU_SESSION_NOT_AVAILABLE | 500 Internal Server Error | The PDU session is not found for the provided UE address. | ExtErrors | +| INVALID_SESSION_UPDATE | 403 Forbidden | Indicates that the session is not allowed to be updated since one or more of the received parameters can not be served in current session. The AF can retry with a new session. | TSC_5G | + +## 5.15 MsisdnLessMoSms API + +### 5.15.1 Overview + +The MsisdnLessMoSms API allows the delivery of MSISDN-less mobile originated SMSs from the SCEF to the SCS/AS. The corresponding JSON schema for the representation of the resources and operations defined by the MsisdnLessMoSms API is provided in its complete form in Annex A.15. + +### 5.15.2 Data model + +#### 5.15.2.1 Notification data types + +##### 5.15.2.1.1 Introduction + +This clause defines data structures to be used in notifications. + +Table 5.15.2.1.1-1 specifies data types re-used by the MsisdnLessMoSms API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the MsisdnLessMoSms API. + +**Table 5.15.2.1.1-1: MsisdnLessMoSms API re-used Data Types** + +| Data type | Reference | Comments | +|-------------------|---------------------|-----------------------------------------------------------------------------------------| +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.15.4-1. | + +Table 5.15.2.1.1-2 specifies the data types defined for the MsisdnLessMoSms API. + +**Table 5.15.2.1.1-2: MsisdnLessMoSms API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|----------------------------------|----------------|----------------------------------------------------------|---------------| +| MsisdnLessMoSmsNotification | 5.15.2.1.2 | Represents a MSISDN-less MO SMS notification. | | +| MsisdnLessMoSmsNotificationReply | 5.15.2.1.3 | Represents a reply to a MSISDN-less MO SMS notification. | | + +##### 5.15.2.1.2 Type: MsisdnLessMoSmsNotification + +This data type represents a MSISDN-less MO SMS, which is sent from the SCEF to the SCS/AS. + +**Table 5.15.2.1.2-1: Definition of type MsisdnLessMoSmsNotification** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| supportedFeatures | SupportedFeatures | 1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7. | | +| sms | Bytes | 1 | The MSISDN-less MO SMS containing a short message transfer protocol data unit (TPDU) which is defined in 3GPP TS 23.040 [43] and represents the user data field carried by the short message service relay sub-layer protocol. | | +| externalId | string | 1 | External identifier has the form username@realm. | | +| applicationPort | Port | 1 | Unsigned integer used to uniquely identify the triggering application addressed in the device, see clause 9.2.3.24.4 in TS 23.040 [43] for further details. | | +| NOTE: Properties marked with a feature as defined in clause 5.15.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | + +#### 5.15.2.1.3 Type: MsisdnLessMoSmsNotificationReply + +This data type represents a reply to an MSISDN-less MO SMS notification and is sent from the SCS/AS to the SCEF. + +**Table 5.15.2.1.3-1: Definition of type MsisdnLessMoSmsNotificationReply** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------|--------------------------------------------------------------------------------------------|----------------------| +| supportedFeatures | SupportedFeatures | 1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7. | | +| NOTE: Properties marked with a feature as defined in clause 5.3.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. | | | | | + +### 5.15.3 Resource structure + +#### 5.15.3.1 General + +All resource URIs of this API should have the following root: + +**{notificationDestination}** + +"{notificationDestination}" is determined based on preconfigured information in the SCEF as described in clause 4.4.14.2. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.15.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|---------------------------------|---------------------------|-------------|-------------------------------------------------------------------| +| MSISDN-less MO SMS Notification | {notificationDestination} | POST | Deliver a received MSISDN-less MO SMS from the SCEF to the SCS/AS | + +#### 5.15.3.2 MSISDN-less MO SMS Notification + +##### 5.15.3.2.1 Introduction + +The MSISDN-less MO SMS Notification allows the SCEF to deliver a received MSISDN-less MO SMS to the SCS/AS. + +### 5.15.3.2.2 Resource definition + +The Callback URI: {notificationDestination} shall support the callback URI variables defined in table 5.15.3.2.2-1. + +**Table 5.15.3.2.2-1: Callback URI variables for resource "MSISDN-less MO SMS Notification"** + +| Name | Data type | Definition | +|-------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| notificationDestination | Link | A URI indicating the notification destination where T8 notification requests shall be delivered to.
This URI shall be preconfigured in the SCEF. | + +### 5.15.3.2.3 Standard methods + +#### 5.15.3.2.3.1 Notification via POST + +The HTTP POST method delivers a received MSISDN-less MO SMS. The SCEF shall initiate the HTTP POST request message and the SCS/AS shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.15.3.2.3.1-1 and table 5.15.3.2.3.1-2. + +**Table 5.15.3.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.15.3.2.3.1-2: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|-----------------------------------------------------------------------------------------------------|----------------------------------|-------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | MsisdnLessMoSmsNotification | 1 | The MSISDN-less MO SMS. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | MsisdnLessMoSmsNotificationReply | | 200 OK | The MSISDN-less MO SMS is received successfully. | +| | none | 0..1 | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| | none | 0..1 | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative SCS/AS where the notification should be sent.
Redirection handling is described in clause 5.2.10. | +| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. | | | | | + +**Table 5.15.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +**Table 5.15.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative SCS/AS towards which the notification should be redirected. | + +## 5.15.4 Used Features + +The table below defines the features applicable to the MsisdnLessMoSms API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.15.4-1: Features used by MsisdnLessMoSms API** + +| Feature Number | Feature | Description | +|----------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------| +| Feature: | A short name that can be used to refer to the bit and to the feature, e.g. "Notification". | Description: A clear textual description of the feature. | + +## 5.15.5 Error handling + +### 5.15.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.15.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the MsisdnLessMoSms API. + +### 5.15.5.3 Application Errors + +The application errors defined for MsisdnLessMoSms API are listed in table 5.15.5.3-1. + +**Table 5.15.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 5.16 RacsParameterProvisioning API + +### 5.16.1 Overview + +The RacsParameterProvisioning API is a RESTful API that allows the SCS/AS to provision manufacturer specific UE radio capability parameters. The RacsParameterProvisioning API defines a set of data models, resources and the related procedures for the creation and management of the parameters. The corresponding JSON schema for the representation of the resources and operations defined by the RacsParameterProvisioning API is provided in its complete form in Annex A.16. + +## 5.16.2 Data model + +### 5.16.2.1 Resource data types + +#### 5.16.2.1.1 Introduction + +This clause defines data structures to be used in resource representations. + +Table 5.16.2.1.1-1 specifies data types re-used by the RacsParameterProvisioning API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the RacsParameterProvisioning API. + +**Table 5.16.2.1.1-1: RacsParameterProvisioning API re-used Data Types** + +| Data type | Reference | Comments | +|--------------------|---------------------|-----------------------------------------------------------------------------------------| +| SupportedFeatures | 3GPP TS 29.571 [45] | Used to negotiate the applicability of the optional features defined in table 5.16.4-1. | +| TypeAllocationCode | 3GPP TS 29.571 [45] | Used to signal UE model's IMEI-TAC values in table 5.16.2.1.4-1. | + +Table 5.16.2.1.1-2 specifies the data types defined for the RacsParameterProvisioning API. + +**Table 5.16.2.1.1-2: RacsParameterProvisioning API specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|---------------------------|----------------|------------------------------------------------------------------------------------------------|---------------| +| RacsConfiguration | 5.16.2.1.4 | Represents a single UE radio capability configuration data. | | +| RacsConfigurationRm | 5.16.2.1.6 | Represents the same as the RacsConfiguration data type but with the "nullable: true" property. | | +| RacsFailureCode | 5.16.2.2.3 | Represents the failure result of UE radio capability provisioning. | | +| RacsFailureReport | 5.16.2.1.3 | Represents a radio capability data provisioning failure report. | | +| RacsProvisioningData | 5.16.2.1.2 | Represents a UE's radio capability data. | | +| RacsProvisioningDataPatch | 5.16.2.1.5 | Represents parameters to request the modification of a UE's radio capability data. | | + +#### 5.16.2.1.2 Type: RacsProvisioningData + +This type represents a UE radio capability data provided by the SCS/AS to the SCEF. + +**Table 5.16.2.1.2-1: Definition of type RacsProvisioningData** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|-------------------|------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| self | Link | 0..1 | Link to the resource "Individual RACS parameter provisioning". This parameter shall be supplied by the SCEF in HTTP responses. | | +| supportedFeatures | SupportedFeatures | 0..1 | Used to negotiate the supported optional features of the API as described in clause 5.2.7. This attribute shall be provided in the POST request and in the response of successful resource creation. | | +| racsConfigs | map(RacsConfiguration) | 1..N | Identifies the configuration related to manufacturer specific UE radio capability. Each element uniquely identifies an RACS configuration for an RACS ID and is identified in the map via the RACS ID as key. The response shall include successfully provisioned RACS data. | | +| racsReports | map(RacsFailureReport) | 0..N | Supplied by the SCEF. Contains the RACS IDs for which the RACS data are not provisioned successfully. Any string value can be used as a key of the map. | | + +NOTE: Properties marked with a feature as defined in clause 5.16.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +#### 5.16.2.1.3 Type: RacsFailureReport + +This type represents a radio capability data provisioning report provided by the SCEF. + +**Table 5.16.2.1.3-1: Definition of type RacsFailureReport** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|----------------|-----------------|-------------|-------------------------------------------------------------------------------------|----------------------| +| racsIds | array(string) | 1..N | Identifies the RACS ID(s) for which the RACS data are not provisioned successfully. | | +| failureCode | RacsFailureCode | 1 | It indicates the failure reason. | | + +NOTE: Properties marked with a feature as defined in clause 5.16.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +#### 5.16.2.1.4 Type: RacsConfiguration + +This type represents a single UE radio capability configuration data provided by the SCS/AS to the SCEF. + +**Table 5.16.2.1.4-1: Definition of type RacsConfiguration** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE 1) | +|----------------|---------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| racsId | string | 1 | The UE radio capability ID provided by the SCS/AS to identify the UE radio capability data. See 3GPP TS 23.003 [14] for the encoding. (NOTE 3) | | +| racsParamEps | string | 0..1 | The UE radio capability data in EPS, its encoding shall comply with the UE-CapabilityRAT-ContainerList as defined in clause 6.3.6 of 3GPP TS 36.331 [59]. (NOTE 2, NOTE 4) | | +| racsParam5Gs | string | 0..1 | The UE radio capability data in 5GS, its encoding shall comply with the UE-CapabilityRAT-ContainerList as defined in clause 6.3.3 of 3GPP TS 38.331 [60]. (NOTE 2, NOTE 4) | | +| imeiTacs | array(TypeAllocationCode) | 1..N | Related UE model's IMEI-TAC values | | + +NOTE 1: Properties marked with a feature as defined in clause 5.16.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. +NOTE 2: At least one of racsParamEps or racsParam5Gs shall be provided. +NOTE 3: A racsId shall only belong to one "Individual RACS Parameter Provisioning" resource. +NOTE 4: UTRAN capabilities shall not be included within the "racsParamEps" attribute and/or the "racsParam5Gs" attribute. + +#### 5.16.2.1.5 Type: RacsProvisioningDataPatch + +This type represents a UE radio capability data provided by the SCS/AS to the SCEF. This structure is used in the PATCH request. + +**Table 5.16.2.1.5-1: Definition of type RacsProvisioningDataPatch** + +| Attribute name | Data type | Cardinality | Description | Applicability (NOTE) | +|----------------|--------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| racsConfigs | map(RacsConfigurationRm) | 0..N | Identifies the configuration related to manufacturer specific UE radio capability. Each element uniquely identifies an RACS configuration for an RACS ID and is identified in the map via the RACS ID as key. | | + +NOTE: Properties marked with a feature as defined in clause 5.16.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. + +#### 5.16.2.1.6 Type: RacsConfigurationRm + +This type represents a single UE radio capability configuration data provided by the SCS/AS to the SCEF. It is defined with "nullable: true" property. + +**Table 5.16.2.1.6-1: Definition of type RacsConfigurationRm** + +| Attribute name | Data type | Cardinality | Description | Applicability | +|----------------|---------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| racsParamEps | string | 0..1 | The UE radio capability data in EPS, its encoding shall comply with the UE-CapabilityRAT-ContainerList as defined in clause 6.3.6 of 3GPP TS 36.331 [59]. | | +| racsParam5Gs | string | 0..1 | The UE radio capability data in 5GS, its encoding shall comply with the UE-CapabilityRAT-ContainerList as defined in clause 6.3.3 of 3GPP TS 38.331 [60]. | | +| imeiTacs | array(TypeAllocationCode) | 0..N | Related UE model's IMEI-TAC values. | | + +## 5.16.2.2 Referenced simple data types and enumerations + +### 5.16.2.2.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced. + +### 5.16.2.2.2 Simple data types + +The simple data types defined in table 5.16.2.2.2-1 shall be supported. + +**Table 5.16.2.2.2-1: Simple data types** + +| Type name | Description | +|-----------|-------------| +| | | + +### 5.16.2.2.3 Enumeration: RacsFailureCode + +The enumeration RacsFailureCode represents the failure result of UE radio capability provisioning. + +**Table 5.16.2.2.3-1: Enumeration RacsFailureCode** + +| Enumeration value | Description | Applicability | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------| +| MALFUNCTION | This value indicates that something functions wrongly in RACS provisioning or the RACS provisioning does not function at all. | | +| RESOURCE_LIMITATION | This value indicates there is resource limitation for RACS data storage. | | +| RACS_ID_DUPLICATED | The received RACS identifier(s) are already provisioned. | | +| OTHER_REASON | Other reason unspecified. | | + +## 5.16.3 Resource structure + +### 5.16.3.1 General + +All resource URIs of this API should have the following root: + +**{apiRoot}/3gpp-racs-pp/v1** + +"apiRoot" is set as described in clause 5.2.4. "apiName" shall be set to "3gpp-racs-pp" and "apiVersion" shall be set to "v1" for the version defined in the present document. All resource URIs in the clauses below are defined relative to the above root URI. + +The following resources and HTTP methods are supported for this API: + +**Table 5.16.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method | Meaning | +|----------------------------------------|--------------------------------------------|-------------|------------------------------------------------------------------| +| RACS Parameter Provisionings | //{scsAsId}/provisionings | GET | Read all RACS parameter provisionings for a given AF | +| | | POST | Create a new RACS parameter provisioning | +| Individual RACS Parameter Provisioning | //{scsAsId}/provisionings/{provisioningId} | PUT | Modify all properties in an existing RACS parameter provisioning | + +| | | | | +|--|--|--------|-------------------------------------------------------------------| +| | | PATCH | Modify some properties in an existing RACS parameter provisioning | +| | | GET | Read an existing RACS parameter provisioning | +| | | DELETE | Delete a RACS parameter provisioning | + +## 5.16.3.2 Resource: RACS Parameter Provisionings + +### 5.16.3.2.1 Introduction + +This resource allows an SCS/AS to read all active RACS parameter provisionings or create a new RACS parameter provisioning. + +### 5.16.3.2.2 Resource definition + +Resource URI: {apiRoot}/3gpp-racs-pp/v1/{scsAsId}/provisionings + +This resource shall support the resource URI variables defined in table 5.16.3.2.2-1. + +**Table 5.16.3.2.2-1: Resource URI variables for resource "Parameter Provisioning"** + +| Name | Data type | Definition | +|---------|-----------|---------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS. | + +### 5.16.3.2.3 Resource methods + +#### 5.16.3.2.3.1 GET + +The GET method allows to read all active RACS parameter provisionings indicated by the resource URI as defined in clause 5.16.3.2.2. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.16.3.2.3.1-1 and table 5.16.3.2.3.1-2. + +**Table 5.16.3.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.16.3.2.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------------------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | array(RacsProvisioningData) | 0..N | 200 OK | The provisioning information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +| | | | | | +|--|------|--|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | none | | 308
Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +|--|------|--|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.16.3.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.16.3.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.16.3.2.3.2 PUT + +This HTTP method is not supported for the resource. + +#### 5.16.3.2.3.3 PATCH + +This HTTP method is not supported for the resource. + +#### 5.16.3.2.3.4 POST + +The POST method creates a new parameter provisioning resource for a given SCS/AS. The SCS/AS shall initiate the HTTP POST request message and the SCEF shall respond to the message. The SCEF shall construct the URI of the created resource. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.16.3.2.3.4-1 and table 5.16.3.2.3.4-2. + +**Table 5.16.3.2.3.4-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.16.3.2.3.4-2: Data structures supported by the POST request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|--------------------------|-------------|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| | RacsProvisioningData | 1 | Parameters to create a new provisioning. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | RacsProvisioningData | 1 | 201 Created | The provisioning was created successfully.
The URI of the created resource shall be returned in the "Location" HTTP header. | +| | array(RacsFailureReport) | 1..N | 500 Internal Server Error | The RACS data for all RACS IDs were not provisioned successfully. | +| | | | | | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. + +**Table 5.16.3.2.3.4-3: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/3gpp-racs-pp/v1/{scsAsId}/provisionings/{provisioningId} | + +#### 5.16.3.2.3.5 DELETE + +This HTTP method is not supported for the resource. + +### 5.16.3.3 Resource: Individual RACS Parameter Provisioning + +#### 5.16.3.3.1 Introduction + +This resource allows an SCS/AS to query, update and delete a parameter provisioning indicated by the resource URI as defined in clause 5.16.3.3.2. + +#### 5.16.3.3.2 Resource definition + +Resource URI: {apiRoot}/3gpp-racs-pp/v1/{scsAsId}/provisionings/{provisioningId} + +This resource shall support the resource URI variables defined in table 5.16.3.3.2-1. + +**Table 5.16.3.2.2-1: Resource URI variables for resource "Individual RACS Parameter Provisioning"** + +| Name | Data type | Definition | +|----------------|-----------|---------------------------------------------------------| +| apiRoot | string | See clause 5.2.4. | +| scsAsId | string | Identifier of the SCS/AS of type ScsAsId. | +| provisioningId | string | Identifier of the provisioning resource of type string. | + +#### 5.16.3.3.3 Resource methods + +##### 5.16.3.3.3.1 GET + +The GET method allows to read an active parameter provisioning indicated by the resource URI as defined in clause 5.16.3.3.2. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.16.3.3.3.1-1 and table 5.16.3.3.3.1-2. + +**Table 5.16.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | Cardinality | Remarks | +|------|-----------|-------------|---------| +| | | | | + +**Table 5.16.3.3.3.1-2: Data structures supported by the GET request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|----------------|---------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | | | | | + +| | | | | | +|--|----------------------|---|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | RacsProvisioningData | 1 | 200 OK | The provisioning information related to the request URI is returned. | +| | none | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| | none | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. + +**Table 5.16.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.16.3.3.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.16.3.3.3.2 PATCH + +The PATCH method shall be used to update some properties in an existing provisioning indicated by the Resource URI as defined in clause 5.16.3.3.2. The SCS/AS shall initiate the HTTP PATCH request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.16.3.3.3.2-1 and table 5.16.3.3.3.2-2. + +**Table 5.16.3.3.3.2-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.16.3.3.3.2-2: Data structures supported by the PATCH request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|---------------------------|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------| +| | Data type | Cardinality | Response codes | Remarks | +| Response body | RacsProvisioningDataPatch | 1 | | Partial update an existing parameter provisioning. | +| | RacsProvisioningData | 1 | 200 OK | The provisioning data was updated successfully. The SCEF shall return an updated provisioning information in the response. | +| | none | | 204 No Content | The provisioning data was updated successfully, and no content is to be sent in the response message body. | + +| | | | | +|--------------------------|------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| array(RacsFailureReport) | 1..N | 500 Internal Server Error | The RACS data for all RACS IDs were not provisioned successfully. | +| none | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 also apply. + +**Table 5.16.3.3.3.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.16.3.3.3.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.16.3.3.3.3 PUT + +The PUT method shall be used to update all properties in an existing provisioning indicated by the Resource URI as defined in clause 5.16.3.3.2. The SCS/AS shall initiate the HTTP PUT request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.16.3.3.3.1 and table 5.16.3.3.3.2. + +**Table 5.16.3.3.3.1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | Cardinality | Remarks | +|----------------|-----------|-------------|---------| +| none specified | | | | + +**Table 5.16.3.3.3.2: Data structures supported by the PUT request/response by the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|----------------------|-------------|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| | RacsProvisioningData | 1 | Replace an existing parameter provisioning. | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | RacsProvisioningData | 1 | 200 OK | The provisioning data was replaced successfully. The SCEF shall return an updated provisioning information in the response. | +| | none | | 204 No Content | The existing RACS Parameter Provisioning has been replaced successfully and no content is to be sent in the response message body. | + +| | | | | +|---------------------------|------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| array(RacsFailureReport ) | 1..N | 500 Internal Server Error | The RACS data for all RACS IDs were not provisioned successfully. | +| none | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | +| none | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 also apply. + +**Table 5.16.3.3.3.3-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.16.3.3.3.3-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +#### 5.16.3.3.3.4 POST + +This HTTP method is not supported for the resource. + +#### 5.16.3.3.3.5 DELETE + +The DELETE method deletes an existing provisioning resource "Individual RACS Parameter Provisioning". The SCS/AS shall initiate the HTTP DELETE request message and the SCEF shall respond to the message. + +This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.16.3.3.3.5-1 and table 5.16.3.3.3.5-2. + +**Table 5.16.3.3.3.5-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | Cardinality | Remarks | +|------|-----------|-------------|---------| +| N/A | | | | + +**Table 5.16.3.3.3.5-2: Data structures supported by the DELETE request/response on the resource** + +| Request body | Data type | Cardinality | Remarks | | +|---------------|-----------|-------------|----------------|--------------------------------------------------------------------------------------------------------| +| | none | | | | +| Response body | Data type | Cardinality | Response codes | Remarks | +| | none | | 204 No Content | The provisioning was terminated successfully. The response body shall be empty. | +| | none | | 307 Temporary | Temporary redirection, during resource termination. The response shall include a Location header field | + +| | | | | | +|-------------------------------------------------------------------------------------------------------|------|--|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Redirect | containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| | none | | 308
Permanent Redirect | Permanent redirection, during resource termination.
The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF.
Redirection handling is described in clause 5.2.10. | +| NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 also apply. | | | | | + +**Table 5.16.3.3.5-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +**Table 5.16.3.3.5-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative SCEF. | + +## 5.16.4 Used Features + +The table below defines the features applicable to the RacsParameterProvisioning API. Those features are negotiated as described in clause 5.2.7. + +**Table 5.16.4-1: Features used by RacsParameterProvisioning API** + +| Feature Number | Feature | Description | +|----------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------| +| Feature: | A short name that can be used to refer to the bit and to the feature, e.g. "Notification". | Description: A clear textual description of the feature. | + +## 5.16.5 Error handling + +### 5.16.5.1 General + +HTTP error handling shall be supported as specified in clause 5.2.6. + +In addition, the requirements in the following clauses shall apply. + +### 5.16.5.2 Protocol Errors + +In this release of the specification, there are no additional protocol errors applicable for the RacsParameterProvisioning API. + +### 5.16.5.3 Application Errors + +The application errors defined for the RacsParameterProvisioning API are listed in table 5.16.5.3-1. + +**Table 5.16.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|-------------------|------------------|-------------| +| | | | + +## 6 Security + +TLS shall be used to support the security communication between the SCEF and the SCS/AS over T8 as defined in clause 5.5 of 3GPP TS 33.187 [35]. The access to the SCEF northbound APIs shall be authorized by means of OAuth2 protocol (see IETF RFC 6749 [51]), based on local configuration, using the "Client Credentials" authorization grant. If OAuth2 is used, a client, prior to consuming services offered by the SCEF Northbound APIs, shall obtain a "token" from the authorization server. + +## 7 Using Common API Framework + +### 7.1 General + +When CAPIF is used with the SCEF, the SCEF shall support the following as defined in 3GPP TS 29.222 [48]: + +- the API exposing function and related APIs over CAPIF-2/2e and CAPIF-3/3e reference points; +- the API publishing function and related APIs over CAPIF-4/4e reference point; +- the API management function and related APIs over CAPIF-5/5e reference point; and +- at least one of the the security methods for authentication and authorization, and related security mechanisms. + +In a centralized deployment as defined in 3GPP TS 23.222 [47], where the CAPIF core function and API provider domain functions are co-located, the interactions between the CAPIF core function and API provider domain functions may be independent of CAPIF-3/3e, CAPIF-4/4e and CAPIF-5/5e reference points. + +When CAPIF is used with the SCEF, the SCEF shall register all the features for northbound APIs in the CAPIF Core Function. + +### 7.2 Security + +When CAPIF is used for external exposure, before invoking the API exposed by the SCEF, the SCS/AS as API invoker shall negotiate the security method (PKI, TLS-PSK or OAUTH2) with CAPIF core function and ensure the SCEF has enough credential to authenticate the SCS/AS (see 3GPP TS 29.222 [48], clause 5.6.2.2 and clause 6.2.2.2). + +If PKI or TLS-PSK is used as the selected security method between the AF and the NEF, upon API invocation, the NEF shall retrieve the authorization information from the CAPIF core function as described in 3GPP TS 29.222 [48], clause 5.6.2.4. + +As indicated in 3GPP TS 33.122 [53], the access to the T8 APIs may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [51]), using the "Client Credentials" authorization grant, where the CAPIF core function (see 3GPP TS 29.222 [48]) plays the role of the authorization server. + +NOTE 1: In this release, only "Client Credentials" authorization grant is supported. + +If OAuth2 is used as the selected security method between the SCS/AS and the SCEF, the SCS/AS, prior to consuming services offered by the T8 APIs, shall obtain a "token" from the authorization server, by invoking the Obtain\_Authorization service, as described in 3GPP TS 29.222 [48], clause 5.6.2.3.2. + +The T8 APIs do not define any scopes for OAuth2 authorization. It is the SCEF responsibility to check whether the SCS/AS is authorized to use an API based on the "token". Once the SCEF verifies the "token", it shall check whether the NEF identifier in the "token" matches its own published identifier, and whether the API name in the "token" + +matches its own published API name. If those checks are passed, the AF has full authority to access any resource or operation for the invoked API. + +NOTE 2: The security requirement in the current clause does not apply for the MsisdnLessMoSms API since it is the SCEF initiated interaction with the SCS/AS. How the security scheme works for the MsisdnLessMoSms API is left to configuration. + +NOTE 3: For aforementioned security methods, the SCEF needs to apply admission control according to access control policies after performing the authorization checks. + +# Annex A (normative): OpenAPI representation for the APIs defined in the present document + +## A.1 General + +This Annex is based on the OpenAPI Specification [27] and provides corresponding representations of all APIs defined in the present specification. + +NOTE 1: An OpenAPIs representation embeds JSON Schema representations of HTTP message bodies. + +This Annex shall take precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s). + +NOTE 2: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5B of the 3GPP TR 21.900 [58] and clause 5.3.1 of the 3GPP TS 29.501 [49] for further information). + +## A.2 Data Types applicable to several APIs + +For the purpose of referencing entities in the Open API file defined in this Annex, it shall be assumed that this Open API file is contained in a physical file named "TS29122\_CommonData.yaml". + +NOTE: For the purpose of referencing the error status codes in the Open API file defined in this Annex, this Open API file contains all the mandatory status codes as defined in table 5.2.6-1, all the API specific error status codes defined for T8 APIs, in addition, some error status codes not used in the current release of this specification but for the purpose of referencing by other specifications. + +``` +openapi: 3.0.0 + +info: + title: TS 29.122 Common Data Types + version: 1.3.0-alpha.4 + description: | + Data types applicable to several APIs. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.122 V18.4.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' + +paths: {} + +components: + schemas: + SponsorInformation: + description: Represents a sponsor information. + type: object + properties: + sponsorId: + type: string + description: It indicates Sponsor ID. + aspId: + type: string + description: It indicates Application Service Provider ID. + required: + - sponsorId + - aspId +``` + +``` +UsageThreshold: + description: Represents a usage threshold. + type: object + properties: + duration: + $ref: '#/components/schemas/DurationSec' + totalVolume: + $ref: '#/components/schemas/Volume' + downlinkVolume: + $ref: '#/components/schemas/Volume' + uplinkVolume: + $ref: '#/components/schemas/Volume' + +UsageThresholdRm: + description: > + Represents the same as the UsageThreshold data type but with the nullable:true property. + type: object + properties: + duration: + $ref: '#/components/schemas/DurationSecRm' + totalVolume: + $ref: '#/components/schemas/VolumeRm' + downlinkVolume: + $ref: '#/components/schemas/VolumeRm' + uplinkVolume: + $ref: '#/components/schemas/VolumeRm' + nullable: true + +TimeWindow: + description: Represents a time window identified by a start time and a stop time. + type: object + properties: + startTime: + $ref: '#/components/schemas/DateTime' + stopTime: + $ref: '#/components/schemas/DateTime' + required: + - startTime + - stopTime + +Acknowledgement: + description: Represents a successful acknowledgement of a notification. + type: object + properties: + details: + type: string + description: A human-readable explanation specific to this successful acknowledgement + required: + - details + +NotificationData: + description: > + Represents the information to be conveyed in a bearer level event(s) notification. + type: object + properties: + transaction: + $ref: '#/components/schemas/Link' + eventReports: + type: array + items: + $ref: '#/components/schemas/EventReport' + minItems: 1 + description: Contains the reported event and applicable information + required: + - transaction + - eventReports + +EventReport: + description: Represents an event report. + type: object + properties: + event: + $ref: '#/components/schemas/Event' + accumulatedUsage: + $ref: '#/components/schemas/AccumulatedUsage' + flowIds: + type: array +``` + +``` + items: + type: integer + minItems: 1 + description: Identifies the IP flows that were sent during event subscription + required: + - event + +AccumulatedUsage: + description: Represents an accumulated usage. + type: object + properties: + duration: + $ref: '#/components/schemas/DurationSec' + totalVolume: + $ref: '#/components/schemas/Volume' + downlinkVolume: + $ref: '#/components/schemas/Volume' + uplinkVolume: + $ref: '#/components/schemas/Volume' + +FlowInfo: + description: Represents IP flow information. + type: object + properties: + flowId: + type: integer + description: Indicates the IP flow identifier. + flowDescriptions: + type: array + items: + type: string + description: > + Indicates the packet filters of the IP flow. Refer to clause 5.3.8 of 3GPP TS 29.214 for + encoding. It shall contain UL and/or DL IP flow description. + minItems: 1 + maxItems: 2 + tosTC: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TosTrafficClass' + required: + - flowId + +TestNotification: + description: > + Represents a notification that can be sent to test whether a chosen notification mechanism + works. + type: object + properties: + subscription: + $ref: '#/components/schemas/Link' + required: + - subscription + +WebsockNotifConfig: + description: > + Represents the configuration information for the delivery of notifications over Websockets. + type: object + properties: + websocketUri: + $ref: '#/components/schemas/Link' + requestWebsocketUri: + type: boolean + description: Set by the SCS/AS to indicate that the Websocket delivery is requested. + +LocationArea: + description: Represents a user location area. + type: object + properties: + cellIDs: + type: array + items: + type: string + minItems: 1 + description: > + Indicates a list of Cell Global Identities of the user which identifies the cell the UE + is registered. + enodeBIDs: + type: array + items: +``` + +``` + type: string + minItems: 1 + description: Indicates a list of eNodeB identities in which the UE is currently located. + routingAreaIds: + type: array + items: + type: string + minItems: 1 + description: > + Identifies a list of Routing Area Identities of the user where the UE is located. + trackingAreaIds: + type: array + items: + type: string + minItems: 1 + description: > + Identifies a list of Tracking Area Identities of the user where the UE is located. + geographicAreas: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea' + minItems: 1 + description: Identifies a list of geographic area of the user where the UE is located. + civicAddresses: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress' + minItems: 1 + description: Identifies a list of civic addresses of the user where the UE is located. + +LocationArea5G: + description: Represents a user location area when the UE is attached to 5G. + type: object + properties: + geographicAreas: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea' + minItems: 0 + description: Identifies a list of geographic area of the user where the UE is located. + civicAddresses: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress' + minItems: 0 + description: Identifies a list of civic addresses of the user where the UE is located. + nwAreaInfo: + $ref: 'TS29554_Npcf_BDTPolicyControl.yaml#/components/schemas/NetworkAreaInfo' + +ProblemDetails: + description: Represents additional information and details on an error response. + type: object + properties: + type: + $ref: '#/components/schemas/Uri' + title: + type: string + description: > + A short, human-readable summary of the problem type. It should not change from +occurrence + to occurrence of the problem. + status: + type: integer + description: The HTTP status code for this occurrence of the problem. + detail: + type: string + description: A human-readable explanation specific to this occurrence of the problem. + instance: + $ref: '#/components/schemas/Uri' + cause: + type: string + description: > + A machine-readable application error cause specific to this occurrence of the problem. + This IE should be present and provide application-related error information, if + available. + invalidParams: + type: array + items: +``` + +``` + $ref: '#/components/schemas/InvalidParam' + minItems: 1 + description: > + Description of invalid parameters, for a request rejected due to invalid parameters. + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + +InvalidParam: + description: > + Represents the description of invalid parameters, for a request rejected due to invalid + parameters. + type: object + properties: + param: + type: string + description: Attribute's name encoded as a JSON Pointer, or header's name. + reason: + type: string + description: A human-readable reason, e.g. "must be a positive integer". + required: + - param + +PlmnId: + description: Represents the identifier of a PLMN. + type: object + properties: + mcc: + $ref: '#/components/schemas/Mcc' + mnc: + $ref: '#/components/schemas/Mnc' + required: + - mcc + - mnc + +ConfigResult: + description: Represents one configuration processing result for a group's members. + type: object + properties: + externalIds: + type: array + items: + $ref: '#/components/schemas/ExternalId' + minItems: 1 + description: Each element indicates an external identifier of the UE. + msisdns: + type: array + items: + $ref: '#/components/schemas/Msisdn' + minItems: 1 + description: > + Each element identifies the MS internal PSTN/ISDN number allocated for the UE. + resultReason: + $ref: '#/components/schemas/ResultReason' + required: + - resultReason + oneOf: + - required: [externalIds] + - required: [msisdns] + +Bandwidth: + type: integer + minimum: 0 + description: integer indicating a bandwidth in bits per second. + +BdtReferenceId: + type: string + description: string identifying a BDT Reference ID as defined in clause 5.3.3 of 3GPP TS +29.154. + +Binary: + type: string + description: string with format "binary" as defined in OpenAPI Specification. + +Bytes: + type: string + description: > + String with format "byte" as defined in OpenAPI Specification, i.e, base64-encoded + characters. +``` + +DayOfWeek: +type: integer +minimum: 1 +maximum: 7 +description: > +integer between and including 1 and 7 denoting a weekday. 1 shall indicate Monday, and the subsequent weekdays shall be indicated with the next higher numbers. 7 shall indicate Sunday. + +DateTime: +format: date-time +type: string +description: string with format "date-time" as defined in OpenAPI. + +DateTimeRm: +format: date-time +type: string +description: > +string with format "date-time" as defined in OpenAPI with "nullable=true" property. +nullable: true + +DateTimeRo: +format: date-time +type: string +description: > +string with format "date-time" as defined in OpenAPI with "readOnly=true" property. +readOnly: true + +DurationSec: +type: integer +minimum: 0 +description: Unsigned integer identifying a period of time in units of seconds. + +DurationSecRm: +type: integer +minimum: 0 +description: > +Unsigned integer identifying a period of time in units of seconds with "nullable=true" property. +nullable: true + +DurationSecRo: +type: integer +minimum: 0 +description: > +Unsigned integer identifying a period of time in units of seconds with "readOnly=true" property. +readOnly: true + +DurationMin: +type: integer +format: int32 +minimum: 0 +description: Unsigned integer identifying a period of time in units of minutes. + +ExternalId: +type: string +description: > +string containing a local identifier followed by "@" and a domain identifier. Both the local identifier and the domain identifier shall be encoded as strings that do not contain any "@" characters. See Clause 4.6.2 of 3GPP TS 23.682 for more information. + +ExternalGroupId: +type: string +description: > +string containing a local identifier followed by "@" and a domain identifier. Both the local identifier and the domain identifier shall be encoded as strings that do not contain any "@" characters. See Clauses 4.6.2 and 4.6.3 of 3GPP TS 23.682 for more information. + +Ipv4Addr: +type: string +description: > +string identifying a Ipv4 address formatted in the "dotted decimal" notation as defined in IETF RFC 1166. + +Ipv6Addr: +type: string +description: > + +``` + string identifying a Ipv6 address formatted according to clause 4 in IETF RFC 5952. + The mixed Ipv4 Ipv6 notation according to clause 5 of IETF RFC 5952 shall not be used. + +Ipv4AddrRo: + type: string + description: > + string identifying a Ipv4 address formatted in the "dotted decimal" notation + as defined in IETF RFC 1166, with "readOnly=true" property. + readOnly: true + +Ipv6AddrRo: + type: string + description: > + string identifying a Ipv6 address formatted according to clause 4 in IETF RFC 5952, + with "readOnly=true" property. The mixed Ipv4 Ipv6 notation according to clause 5 of + IETF RFC 5952 shall not be used. + readOnly: true + +Link: + type: string + description: string formatted according to IETF RFC 3986 identifying a referenced resource. + +LinkRm: + type: string + description: > + String formatted according to IETF RFC 3986 identifying a referenced resource, + but with the nullable property set to true. + nullable: true + +McC: + type: string + description: > + String encoding a Mobile Country Code part of the PLMN, comprising 3 digits, + as defined in 3GPP TS 38.413. + +Mnc: + type: string + description: > + String encoding a Mobile Network Code part of the PLMN, comprising 2 or 3 digits, + as defined in 3GPP TS 38.413. + +Msisdn: + type: string + description: > + string formatted according to clause 3.3 of 3GPP TS 23.003 that describes an MSISDN. + +Port: + type: integer + description: Unsigned integer with valid values between 0 and 65535. + minimum: 0 + maximum: 65535 + +PortRo: + type: integer + description: > + Unsigned integer with valid values between 0 and 65535, with "readOnly=true" property. + minimum: 0 + maximum: 65535 + readOnly: true + +ResourceId: + type: string + description: string chosen by the SCEF to serve as identifier in a resource URI. + +ScsAsId: + type: string + description: string that identifies an SCS/AS. + +TimeOfDay: + type: string + description: > + String with format partial-time or full-time as defined in clause 5.6 of IETF RFC 3339. + Examples, 20:15:00, 20:15:00-08:00 (for 8 hours behind UTC). + +Uri: + type: string + description: string providing an URI formatted according to IETF RFC 3986. + +Volume: +``` + +``` +type: integer +format: int64 +minimum: 0 +description: Unsigned integer identifying a volume in units of bytes. + +VolumeRm: +type: integer +format: int64 +minimum: 0 +description: > + Unsigned integer identifying a volume in units of bytes with "nullable=true" property. +nullable: true + +EthFlowInfo: +description: Represents Ethernet flow information. +type: object +properties: + flowId: + type: integer + description: Indicates the Ethernet flow identifier. + ethFlowDescriptions: + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EthFlowDescription' + description: > + Indicates the packet filters of the Ethernet flow. It shall contain UL and/or DL + Ethernet flow description. + minItems: 1 + maxItems: 2 + required: + - flowId + +Event: +anyOf: +- type: string + enum: + - SESSION_TERMINATION + - LOSS_OF_BEARER + - RECOVERY_OF_BEARER + - RELEASE_OF_BEARER + - USAGE_REPORT + - FAILED_RESOURCES_ALLOCATION + - SUCCESSFUL_RESOURCES_ALLOCATION +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration and is not used to encode + content defined in the present version of this API. +description: | + Represents the event reported by the SCEF. + Possible values are: + - SESSION_TERMINATION: Indicates that Rx session is terminated. + - LOSS_OF_BEARER : Indicates a loss of a bearer. + - RECOVERY_OF_BEARER: Indicates a recovery of a bearer. + - RELEASE_OF_BEARER: Indicates a release of a bearer. + - USAGE_REPORT: Indicates the usage report event. + - FAILED_RESOURCES_ALLOCATION: Indicates the resource allocation is failed. + - SUCCESSFUL_RESOURCES_ALLOCATION: Indicates the resource allocation is successful. + +ResultReason: +anyOf: +- type: string + enum: + - ROAMING_NOT_ALLOWED + - OTHER_REASON +- type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration + and is not used to encode content defined in the present version of this API. +description: | + Represents a failure result reason. + Possible values are: + - ROAMING_NOT_ALLOWED: Identifies the configuration parameters are not allowed by roaming + agreement. + - OTHER_REASON: Identifies the configuration parameters are not configured due to other + reason. + +# +# HTTP responses +``` + +``` +# +responses: + '307': + description: Temporary Redirect + headers: + Location: + description: 'An alternative URI of the resource.' + required: true + schema: + type: string + '308': + description: Permanent Redirect + headers: + Location: + description: 'An alternative URI of the resource.' + required: true + schema: + type: string + '400': + description: Bad request + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + '401': + description: Unauthorized + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + '403': + description: Forbidden + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + '404': + description: Not Found + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + '406': + description: Not Acceptable + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + '409': + description: Conflict + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + '411': + description: Length Required + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + '412': + description: Precondition Failed + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + '413': + description: Content Too Large + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' + '414': + description: URI Too Long + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' +``` + +``` + +'415': + description: Unsupported Media Type + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' +'429': + description: Too Many Requests + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' +'500': + description: Internal Server Error + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' +'503': + description: Service Unavailable + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetails' +default: + description: Generic Error + +``` + +## A.3 MonitoringEvent API + +openapi: 3.0.0 + +``` + +info: + title: 3gpp-monitoring-event + version: 1.3.0-alpha.4 + description: | + API for Monitoring Event. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.122 V18.4.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' + +security: +- {} +- oAuth2ClientCredentials: [] + +servers: +- url: '{apiRoot}/3gpp-monitoring-event/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. + +paths: + /{scsAsId}/subscriptions: + get: + summary: Read all or queried active subscriptions for the SCS/AS. + operationId: FetchAllMonitoringEventSubscriptions + tags: + - Monitoring Event Subscriptions + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: ip-addrs + in: query + description: The IP address(es) of the requested UE(s). + required: false + content: + application/json: + schema: + type: array + +``` + +``` + + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr' + minItems: 1 +- name: ip-domain + in: query + description: > + The IPv4 address domain identifier. The attribute may only be provided if IPv4 address + is included in the ip-addrs query parameter. + required: false + schema: + type: string +- name: mac-addrs + in: query + description: The MAC address(es) of the requested UE(s). + required: false + schema: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' + minItems: 1 +responses: + '200': + description: OK (Successful get all or queried active subscriptions for the SCS/AS) + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/MonitoringEventSubscription' + minItems: 0 + description: Monitoring event subscriptions + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +post: + summary: Creates a new subscription resource for monitoring event notification. + operationId: CreateMonitoringEventSubscription + tags: + - Monitoring Event Subscriptions + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + requestBody: + description: Subscription for notification about monitoring event + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/MonitoringEventSubscription' + callbacks: + - notificationDestination: + '{request.body#/notificationDestination}': + post: + requestBody: # contents of the callback message + +``` + +``` + + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/MonitoringNotification' + responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +UserConsentRevocationNotif: + '{request.body#/revocationNotifUri}': + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ConsentRevocNotif' + responses: + '204': + description: No Content (successful notification). + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + responses: + '201': + description: Created (Successful creation of subscription) + content: + application/json: + schema: + +``` + +``` + + $ref: '#/components/schemas/MonitoringEventSubscription' +headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string +'200': + description: The operation is successful and immediate report is included. + content: + application/json: + schema: + oneOf: + - $ref: '#/components/schemas/MonitoringEventReport' + - $ref: '#/components/schemas/MonitoringEventReports' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/subscriptions/{subscriptionId}: + get: + summary: Read an active subscriptions for the SCS/AS and the subscription Id. + operationId: FetchIndMonitoringEventSubscription + tags: + - Individual Monitoring Event Subscription + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Identifier of the subscription resource + required: true + schema: + type: string + responses: + '200': + description: OK (Successful get the active subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/MonitoringEventSubscription' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + +``` + +``` + + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +put: + summary: Updates/replaces an existing subscription resource. + operationId: UpdateIndMonitoringEventSubscription + tags: + - Individual Monitoring Event Subscription + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Identifier of the subscription resource + required: true + schema: + type: string + requestBody: + description: Parameters to update/replace the existing subscription + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/MonitoringEventSubscription' + responses: + '200': + description: OK (Successful update of the subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/MonitoringEventSubscription' + '204': + description: No Content (Successful update of the subscription) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Modifies an existing subscription of monitoring event. + operationId: ModifyIndMonitoringEventSubscription + tags: + - Individual Monitoring Event Subscription + parameters: + - name: scsAsId + in: path + +``` + +``` + description: Identifier of the SCS/AS. + required: true + schema: + type: string +- name: subscriptionId + in: path + description: Identifier of the subscription resource. + required: true + schema: + type: string +requestBody: + description: > + This is used for PATCH request for partial cancellation and/or partial addition of certain + UE(s) within an active group. + required: true + content: + application/json-patch+json: + schema: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PatchItem' + minItems: 1 +responses: + '204': + description: The resource was modified successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Deletes an already existing monitoring event subscription. + operationId: DeleteIndMonitoringEventSubscription + tags: + - Individual Monitoring Event Subscription + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Identifier of the subscription resource + required: true + schema: + type: string + responses: + '204': + description: No Content (Successful deletion of the existing subscription) + '200': + description: OK (Successful deletion of the existing subscription) + content: + application/json: + schema: +``` + +``` + type: array + items: + $ref: '#/components/schemas/MonitoringEventReport' + minItems: 1 + description: > + The subscription was terminated successfully, the monitoring event report(s) + shall be included if received. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + MonitoringEventSubscription: + description: Represents a subscription to event(s) monitoring. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + mtcProviderId: + type: string + description: Identifies the MTC Service Provider and/or MTC Application. + appIds: + type: array + items: + type: string + description: Identifies the Application Identifier(s) + minItems: 1 + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + addedExternalIds: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + minItems: 1 + description: Indicates the added external Identifier(s) within the active group. + addedMsisdns: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + minItems: 1 + description: Indicates the added MSISDN(s) within the active group. + excludedExternalIds: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + minItems: 1 + description: Indicates cancellation of the external Identifier(s) within the active group. + excludedMsisdns: +``` + +``` + +type: array +items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' +minItems: 1 +description: Indicates cancellation of the MSISDN(s) within the active group. +externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' +addExtGroupId: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + minItems: 2 +ipv4Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv4Addr' +ipv6Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6Addr' +dnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' +notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' +requestTestNotification: + type: boolean + description: > + Set to true by the SCS/AS to request the SCEF to send a test notification + as defined in clause 5.2.5.3. Set to false by the SCS/AS indicates not request SCEF to + send a test notification, default false if omitted otherwise. +websockNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' +monitoringType: + $ref: '#/components/schemas/MonitoringType' +maximumNumberOfReports: + type: integer + minimum: 1 + description: > + Identifies the maximum number of event reports to be generated by the HSS, MME/SGSN + as specified in clause 5.6.0 of 3GPP TS 23.682. +monitorExpireTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' +repPeriod: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' +groupReportGuardTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' +maximumDetectionTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' +reachabilityType: + $ref: '#/components/schemas/ReachabilityType' +maximumLatency: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' +maximumResponseTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' +suggestedNumberOfDlPackets: + type: integer + minimum: 0 + description: > + If "monitoringType" is "UE_REACHABILITY", this parameter may be included to identify + the number of packets that the serving gateway shall buffer in case that + the UE is not reachable. +idleStatusIndication: + type: boolean + description: > + If "monitoringType" is set to "UE_REACHABILITY" or "AVAILABILITY_AFTER_DDN_FAILURE", + this parameter may be included to indicate the notification of when a UE, for which PSM + is enabled, transitions into idle mode. "true" indicates enabling of notification; + "false" indicate no need to notify. Default value is "false" if omitted. +locationType: + $ref: '#/components/schemas/LocationType' +accuracy: + $ref: '#/components/schemas/Accuracy' +minimumReportInterval: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' +maxRptExpireIntvl: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' +samplingInterval: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' +reportingLocEstInd: + type: boolean + description: > + Indicates whether to request the location estimate for event reporting. If + +``` + +"monitoringType" is "LOCATION\_REPORTING", this parameter may be included to indicate whether event reporting requires the location information. If set to true, the location estimation information shall be included in event reporting. If set to "false", indicates the location estimation information shall not be included in event reporting. Default "false" if omitted. + +linearDistance: + \$ref: 'TS29572\_Nlmf\_Location.yaml#/components/schemas/LinearDistance' + +locQoS: + \$ref: 'TS29572\_Nlmf\_Location.yaml#/components/schemas/LocationQoS' + +svcId: + \$ref: 'TS29515\_Ngmlc\_Location.yaml#/components/schemas/ServiceIdentity' + +ldrType: + \$ref: 'TS29572\_Nlmf\_Location.yaml#/components/schemas/LdrType' + +velocityRequested: + \$ref: 'TS29572\_Nlmf\_Location.yaml#/components/schemas/VelocityRequested' + +maxAgeOfLocEst: + \$ref: 'TS29572\_Nlmf\_Location.yaml#/components/schemas/AgeOfLocationEstimate' + +locTimeWindow: + \$ref: 'TS29122\_CommonData.yaml#/components/schemas/TimeWindow' + +supportedGADShapes: + type: array + items: + \$ref: 'TS29572\_Nlmf\_Location.yaml#/components/schemas/SupportedGADShapes' + +codeWord: + \$ref: 'TS29515\_Ngmlc\_Location.yaml#/components/schemas/CodeWord' + +upLocRepIndAf: + description: > + Indicates whether location reporting over user plane is requested or not. + "true" indicates the location reporting over user plane is requested. + "false" indicates the location reporting over user plane is not requested. + Default value is "false" if omitted. + type: boolean + default: false + +upLocRepAddrAf: + \$ref: '#/components/schemas/UpLocRepAddrAfRm' + +associationType: + \$ref: '#/components/schemas/AssociationType' + +plmnIndication: + type: boolean + description: > + If "monitoringType" is "ROAMING\_STATUS", this parameter may be included to indicate the notification of UE's Serving PLMN ID. Value "true" indicates enabling of notification; "false" indicates disabling of notification. Default value is "false" if omitted. + +locationArea: + \$ref: 'TS29122\_CommonData.yaml#/components/schemas/LocationArea' + +locationArea5G: + \$ref: 'TS29122\_CommonData.yaml#/components/schemas/LocationArea5G' + +dddTraDescriptors: + type: array + items: + \$ref: 'TS29571\_CommonData.yaml#/components/schemas/DddTrafficDescriptor' + minItems: 1 + +dddStati: + type: array + items: + \$ref: 'TS29571\_CommonData.yaml#/components/schemas/DlDataDeliveryStatus' + minItems: 1 + +apiNames: + type: array + items: + type: string + minItems: 1 + +monitoringEventReport: + \$ref: '#/components/schemas/MonitoringEventReport' + +snssai: + \$ref: 'TS29571\_CommonData.yaml#/components/schemas/Snssai' + +tgtNsThreshold: + \$ref: 'TS29571\_CommonData.yaml#/components/schemas/SACInfo' + +nsRepFormat: + \$ref: '#/components/schemas/SACRepFormat' + +afServiceId: + type: string + +immediateRep: + type: boolean + description: > + Indicates whether an immediate reporting is requested or not. + "true" indicate an immediate reporting is requested. + "false" indicate an immediate reporting is not requested. + +``` + + Default value "false" if omitted. + uavPolicy: + $ref: '#/components/schemas/UavPolicy' + sesEstInd: + type: boolean + description: > + Set to true by the SCS/AS so that only UAV's with "PDU session established for DNN(s) + subject to aerial service" are to be listed in the Event report. Set to false or default + false if omitted otherwise. + subType: + $ref: '#/components/schemas/SubType' + addnMonTypes: + type: array + items: + $ref: '#/components/schemas/MonitoringType' + addnMonEventReports: + type: array + items: + $ref: '#/components/schemas/MonitoringEventReport' + ueIpAddress: + $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddress' + ueMacAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' + revocationNotifUri: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + reqRangingSlRes: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/RangingSlResult' + minItems: 1 + relatedUEs: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/RelatedUE' + minItems: 1 + required: + - notificationDestination + - monitoringType + anyOf: + - required: [maximumNumberOfReports] + - required: [monitorExpireTime] + +MonitoringNotification: + description: Represents an event monitoring notification. + type: object + properties: + subscription: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + configResults: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ConfigResult' + minItems: 1 + description: Each element identifies a notification of grouping configuration result. + monitoringEventReports: + type: array + items: + $ref: '#/components/schemas/MonitoringEventReport' + minItems: 1 + description: Monitoring event reports. + addedExternalIds: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + minItems: 1 + description: > + Identifies the added external Identifier(s) within the active group via + the "externalGroupId" attribute within the MonitoringEventSubscription data type. + addedMsisdns: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + minItems: 1 + description: > + Identifies the added MSISDN(s) within the active group via the "externalGroupId" + attribute within the MonitoringEventSubscription data type. + cancelExternalIds: + type: array + +``` + +``` +items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' +minItems: 1 +description: > + Identifies the cancelled external Identifier(s) within the active group via + the "externalGroupId" attribute within the MonitoringEventSubscription data type. +cancelMsisdns: +type: array +items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' +minItems: 1 +description: > + Identifies the cancelled MSISDN(s) within the active group via the "externalGroupId" + attribute within the MonitoringEventSubscription data type. +cancelInd: +type: boolean +description: > + Indicates whether to request to cancel the corresponding monitoring subscription. + Set to false or omitted otherwise. +appliedParam: + $ref: '#/components/schemas/AppliedParameterConfiguration' +required: +- subscription + +MonitoringEventReport: +description: Represents an event monitoring report. +type: object +properties: +imeiChange: + $ref: '#/components/schemas/AssociationType' +externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' +appId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ApplicationId' +pduSessInfo: + $ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/PduSessionInformation' +idleStatusInfo: + $ref: '#/components/schemas/IdleStatusInfo' +locationInfo: + $ref: '#/components/schemas/LocationInfo' +locFailureCause: + $ref: '#/components/schemas/LocationFailureCause' +lossOfConnectReason: +type: integer +description: > + If "monitoringType" is "LOSS_OF_CONNECTIVITY", this parameter shall be included + if available to identify the reason why loss of connectivity is reported. + Refer to 3GPP TS 29.336 clause 8.4.58. +unavailPerDur: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' +maxUEAvailabilityTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' +msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' +monitoringType: + $ref: '#/components/schemas/MonitoringType' +uePerLocationReport: + $ref: '#/components/schemas/UePerLocationReport' +plmnId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/PlmnId' +reachabilityType: + $ref: '#/components/schemas/ReachabilityType' +roamingStatus: +type: boolean +description: > + If "monitoringType" is "ROAMING_STATUS", this parameter shall be set to "true" + if the new serving PLMN is different from the HPLMN. Set to false or + omitted otherwise. +failureCause: + $ref: '#/components/schemas/FailureCause' +eventTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' +pdnConnInfoList: +type: array +items: + $ref: '#/components/schemas/PdnConnectionInformation' +minItems: 1 +dddStatus: +``` + +``` +$ref: 'TS29571_CommonData.yaml#/components/schemas/DlDataDeliveryStatus' +dddTrafDescriptor: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DddTrafficDescriptor' +maxWaitTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' +apiCaps: + type: array + items: + $ref: '#/components/schemas/ApiCapabilityInfo' + minItems: 0 +nSStatusInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SACEventStatus' +afServiceId: + type: string +servLevelDevId: + type: string + description: > + If "monitoringType" is "AREA_OF_INTEREST", this parameter may be included + to identify the UAV. +uavPresInd: + type: boolean + description: > + If "monitoringType" is "AREA_OF_INTEREST", this parameter shall be set to true + if the specified UAV is in the monitoring area. Set to false or omitted otherwise. +groupMembListChanges: + $ref: '#/components/schemas/GroupMembListChanges' +required: +- monitoringType + +MonitoringEventReports: + description: Represents a set of event monitoring reports. + type: object + properties: + monitoringEventReports: + type: array + items: + $ref: '#/components/schemas/MonitoringEventReport' + minItems: 1 + required: + - monitoringEventReports + +IdleStatusInfo: + description: Represents the information relevant to when the UE transitions into idle mode. + type: object + properties: + activeTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + edrxCycleLength: + format: float + type: number + minimum: 0 + suggestedNumberOfDlPackets: + type: integer + minimum: 0 + description: > + Identifies the number of packets shall be buffered in the serving gateway. + It shall be present if the idle status indication is requested by the SCS/AS + with "idleStatusIndication" in the "monitoringEventSubscription" sets to "true". + idleStatusTimestamp: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + periodicAUTimer: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + +UePerLocationReport: + description: Represents the number of UEs found at the indicated location. + type: object + properties: + ueCount: + type: integer + minimum: 0 + description: Identifies the number of UEs. + externalIds: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + minItems: 1 + description: Each element uniquely identifies a user. + msisdns: + type: array +``` + +``` + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + minItems: 1 + description: Each element identifies the MS internal PSTN/ISDN number allocated for a UE. + servLevelDevIds: + type: array + items: + type: string + minItems: 1 + description: Each element uniquely identifies a UAV. + required: + - ueCount + +LocationInfo: + description: Represents the user location information. + type: object + properties: + ageOfLocationInfo: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationMin' + cellId: + type: string + description: > + Indicates the Cell Global Identification of the user which identifies the cell the UE + is registered. + enodeBId: + type: string + description: Indicates the eNodeB in which the UE is currently located. + routingAreaId: + type: string + description: Identifies the Routing Area Identity of the user where the UE is located. + trackingAreaId: + type: string + description: Identifies the Tracking Area Identity of the user where the UE is located. + plmnId: + type: string + description: Identifies the PLMN Identity of the user where the UE is located. + twanId: + type: string + description: Identifies the TWAN Identity of the user where the UE is located. + userLocation: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation' + geographicArea: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea' + civicAddress: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress' + positionMethod: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/PositioningMethod' + qosFulfilInd: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AccuracyFulfilmentIndicator' + ueVelocity: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/VelocityEstimate' + ldrType: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LdrType' + achievedQos: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/MinorLocationQoS' + relatedApplicationlayerId: + type: string + rangeDirection: + $ref: '#/components/schemas/RangeDirection' + twodrelativeLocation: + $ref: '#/components/schemas/TwodrelativeLocation' + threedrelativeLocation: + $ref: '#/components/schemas/ThreedrelativeLocation' + relativeVelocity: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/VelocityEstimate' + upCumEvtRep: + $ref: '#/components/schemas/UpCumEvtRep' + +RangeDirection: + description: Represents a range and direction from a point A to a point B. + type: object + properties: + range: + type: number + azimuthDirection: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Angle' + elevationDirection: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Angle' +``` + +``` +TwodrelativeLocation: + description: Represents a relative 2D location with uncertainty ellipse. + type: object + properties: + semiMinor: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Uncertainty' + semiMajor: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Uncertainty' + orientationAngle: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Angle' + +ThreedrelativeLocation: + description: Represents a relative 3D location with uncertainty ellipsoid. + type: object + properties: + semiMinor: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Uncertainty' + semiMajor: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Uncertainty' + verticalUncertainty: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Uncertainty' + orientationAngle: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Angle' + +FailureCause: + description: Represents the reason of communication failure. + type: object + properties: + bssgpCause: + type: integer + description: > + Identifies a non-transparent copy of the BSSGP cause code. Refer to 3GPP TS 29.128. + causeType: + type: integer + description: Identify the type of the SLAP-Cause. Refer to 3GPP TS 29.128. + gmmCause: + type: integer + description: > + Identifies a non-transparent copy of the GMM cause code. Refer to 3GPP TS 29.128. + ranapCause: + type: integer + description: > + Identifies a non-transparent copy of the RANAP cause code. Refer to 3GPP TS 29.128. + ranNasCause: + type: string + description: > + Indicates RAN and/or NAS release cause code information, TWAN release cause code + information or untrusted WLAN release cause code information. Refer to 3GPP TS 29.214. + slapCause: + type: integer + description: > + Identifies a non-transparent copy of the SLAP cause code. Refer to 3GPP TS 29.128. + smCause: + type: integer + description: > + Identifies a non-transparent copy of the SM cause code. Refer to 3GPP TS 29.128. + +PdnConnectionInformation: + description: Represents the PDN connection information of the UE. + type: object + properties: + status: + $ref: '#/components/schemas/PdnConnectionStatus' + apn: + type: string + description: > + Identify the APN, it is depending on the SCEF local configuration whether or + not this attribute is sent to the SCS/AS. + pdnType: + $ref: '#/components/schemas/PdnType' + interfaceInd: + $ref: '#/components/schemas/InterfaceIndication' + ipv4Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv4Addr' + ipv6Addrs: + type: array +``` + +``` + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6Addr' + minItems: 1 + macAddrs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' + minItems: 1 + required: + - status + - pdnType + +AppliedParameterConfiguration: + description: Represents the parameter configuration applied in the network. + type: object + properties: + externalIds: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + minItems: 1 + description: Each element uniquely identifies a user. + msisdns: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + minItems: 1 + description: Each element identifies the MS internal PSTN/ISDN number allocated for a UE. + maximumLatency: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + maximumResponseTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + maximumDetectionTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + +ApiCapabilityInfo: + description: Represents the availability information of supported API. + type: object + properties: + apiName: + type: string + suppFeat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - apiName + - suppFeat + +UavPolicy: + description: > + Represents the policy information included in the UAV presence monitoring request. + type: object + properties: + uavMoveInd: + type: boolean + revokeInd: + type: boolean + required: + - uavMoveInd + - revokeInd + +ConsentRevocNotif: + description: > + Represents the user consent revocation information conveyed in a user consent + revocation notification. + type: object + properties: + subscriptionId: + type: string + consentsRevoked: + type: array + items: + $ref: '#/components/schemas/ConsentRevoked' + minItems: 1 + required: + - subscriptionId + - consentsRevoked + +ConsentRevoked: +``` + +``` +description: Represents the information related to a revoked user consent. +type: object +properties: + ucPurpose: + $ref: 'TS29503_Nudm_SDM.yaml#/components/schemas/UcPurpose' + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' +required: +- ucPurpose +oneOf: +- required: [externalId] +- required: [msisdn] + +GroupMembListChanges: +description: Represents information on the change(s) to a group's members list. +type: object +properties: + addedUEs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' + minItems: 1 + removedUEs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' + minItems: 1 +anyOf: +- required: [addedUEs] +- required: [removedUEs] + +UpLocRepAddrAfRm: +description: Represents the user plane addressing information. +type: object +properties: + ipv4Addrs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' + minItems: 1 + ipv6Addrs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr' + minItems: 1 + fqdn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Fqdn' +nullable: true +anyOf: +- required: [ipv4Addrs] +- required: [ipv6Addrs] +- required: [fqdn] + +UpCumEvtRep: +description: Represents the cumulative event report. +type: object +properties: + upLocRepStat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + +# +# ENUMS +# +MonitoringType: +anyOf: +- type: string +enum: +- LOSS_OF_CONNECTIVITY +- UE_REACHABILITY +- LOCATION_REPORTING +- CHANGE_OF_IMSI_IMEI_ASSOCIATION +- ROAMING_STATUS +- COMMUNICATION_FAILURE +- AVAILABILITY_AFTER_DDN_FAILURE +- NUMBER_OF_UES_IN_AN_AREA +``` + +``` + + - PDN_CONNECTIVITY_STATUS + - DOWNLINK_DATA_DELIVERY_STATUS + - API_SUPPORT_CAPABILITY + - NUM_OF_REGD_UES + - NUM_OF_ESTD_PDU_SESSIONS + - AREA_OF_INTEREST + - GROUP_MEMBER_LIST_CHANGE + - APPLICATION_START + - APPLICATION_STOP +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Represents a monitoring event type. +Possible values are +- LOSS_OF_CONNECTIVITY: The SCS/AS requests to be notified when the 3GPP network detects + that the UE is no longer reachable for signalling or user plane communication +- UE_REACHABILITY: The SCS/AS requests to be notified when the UE becomes reachable for + sending either SMS or downlink data to the UE +- LOCATION_REPORTING: The SCS/AS requests to be notified of the current location or + the last known location of the UE +- CHANGE_OF_IMSI_IMEI_ASSOCIATION: The SCS/AS requests to be notified when the association + of an ME (IMEI(SV)) that uses a specific subscription (IMSI) is changed +- ROAMING_STATUS: The SCS/AS queries the UE's current roaming status and requests to get + notified when the status changes +- COMMUNICATION_FAILURE: The SCS/AS requests to be notified of communication failure events +- AVAILABILITY_AFTER_DDN_FAILURE: The SCS/AS requests to be notified when the UE has become + available after a DDN failure +- NUMBER_OF_UES_IN_AN_AREA: The SCS/AS requests to be notified the number of UEs in a given + geographic area +- PDN_CONNECTIVITY_STATUS: The SCS/AS requests to be notified when the 3GPP network detects + that the UE's PDN connection is set up or torn down +- DOWNLINK_DATA_DELIVERY_STATUS: The AF requests to be notified when the 3GPP network +detects that the downlink data delivery status is changed. +- API_SUPPORT_CAPABILITY: The SCS/AS requests to be notified of the availability of support + of service APIs. +- NUM_OF_REGD_UES: The AF requests to be notified of the current number of registered UEs + for a network slice. +- NUM_OF_ESTD_PDU_SESSIONS: The AF requests to be notified of the current number of + established PDU Sessions for a network slice. +- AREA_OF_INTEREST: The SCS/AS requests to be notified when the UAV moves in or + out of the geographic area. +- GROUP_MEMBER_LIST_CHANGE: The AF requests to be notified of the changes to a group members + list. +- APPLICATION_START: The AF requests to be notified about the start of application traffic + has been detected. +- APPLICATION_STOP: The AF requests to be notified about the stop of application traffic + has been detected. + +ReachabilityType: + anyOf: + - type: string + enum: + - SMS + - DATA + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents a reachability type. + Possible values are + - SMS: The SCS/AS requests to be notified when the UE becomes reachable for sending SMS + to the UE + - DATA: The SCS/AS requests to be notified when the UE becomes reachable for sending + downlink data to the UE. + +LocationType: + anyOf: + - type: string + enum: + - CURRENT_LOCATION + - LAST_KNOWN_LOCATION + - CURRENT_OR_LAST_KNOWN_LOCATION + - INITIAL_LOCATION + +``` + +``` +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents a location type. + Possible values are + - CURRENT_LOCATION: The SCS/AS requests to be notified for current location + - LAST_KNOWN_LOCATION: The SCS/AS requests to be notified for last known location + - CURRENT_OR_LAST_KNOWN_LOCATION: The AF requests the current or last known location + - INITIAL_LOCATION: The AF requests the initial location + +AssociationType: + anyOf: + - type: string + enum: + - IMEI + - IMEISV + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents an IMEI or IMEISV to IMSI association. + Possible values are + - IMEI: The value shall be used when the change of IMSI-IMEI association shall be detected + - IMEISV: The value shall be used when the change of IMSI-IMEISV association shall be detected + +Accuracy: + anyOf: + - type: string + enum: + - CGI_ECGI + - ENODEB + - TA_RA + - PLMN + - TWAN_ID + - GEO_AREA + - CIVIC_ADDR + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents a desired granularity of accuracy of the requested location information. + Possible values are + - CGI_ECGI: The SCS/AS requests to be notified using cell level location accuracy. + - ENODEB: The SCS/AS requests to be notified using eNodeB level location accuracy. + - TA_RA: The SCS/AS requests to be notified using TA/RA level location accuracy. + - PLMN: The SCS/AS requests to be notified using PLMN level location accuracy. + - TWAN_ID: The SCS/AS requests to be notified using TWAN identifier level location accuracy. + - GEO_AREA: The SCS/AS requests to be notified using the geographical area accuracy. + - CIVIC_ADDR: The SCS/AS requests to be notified using the civic address accuracy. + +PdnConnectionStatus: + anyOf: + - type: string + enum: + - CREATED + - RELEASED + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the PDN connection status. + Possible values are + - CREATED: The PDN connection is created. + - RELEASED: The PDN connection is released. + +PdnType: + anyOf: + - type: string +``` + +``` +enum: + - IPV4 + - IPV6 + - IPV4V6 + - NON_IP + - ETHERNET +- type: string +description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Represents the PDN connection type. + Possible values are + - IPV4: PDN connection of IPv4 type. + - IPV6: PDN connection of IPv6 type. + - IPV4V6: PDN connection of IPv4v6 type. + - NON_IP: PDN connection of non-IP type. + - ETHERNET: PDN connection of Ethernet type. + +InterfaceIndication: + anyOf: + - type: string + enum: + - EXPOSURE_FUNCTION + - PDN_GATEWAY + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the network entity used for data delivery towards the SCS/AS. + Possible values are + - EXPOSURE_FUNCTION: SCEF is used for the PDN connection towards the SCS/AS. + - PDN_GATEWAY: PDN gateway is used for the PDN connection towards the SCS/AS. + +LocationFailureCause: + anyOf: + - type: string + enum: + - POSITIONING_DENIED + - UNSUPPORTED_BY_UE + - NOT_REGISTERED_UE + - UNSPECIFIED + - REQUESTED_AREA_NOT_ALLOWED + - type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration but + is not used to encode content defined in the present version of this API. + description: > + Represents the cause of location positioning failure. + Possible values are: + - POSITIONING_DENIED: Positioning is denied. + - UNSUPPORTED_BY_UE: Positioning is not supported by UE. + - NOT_REGISTERED_UE: UE is not registered. + - UNSPECIFIED: Unspecified. + - REQUESTED_AREA_NOT_ALLOWED: The location request is rejected because the location area + requested by the AF for area event reporting is not allowed. + +SubType: + anyOf: + - type: string + enum: + - AERIAL_UE + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents a subscription type. + Possible values are + - AERIAL_UE: The UE has Aerial subscription. + +SACRepFormat: + anyOf: + - type: string +``` + +``` + +enum: + - NUMERICAL + - PERCENTAGE +- type: string +description: > + This string provides forward-compatibility with future extensions to the enumeration but + is not used to encode content defined in the present version of this API. +description: Indicates the NSAC reporting format. + +``` + +## A.4 ResourceManagementOfBdt API + +``` + +openapi: 3.0.0 +info: + title: 3gpp-bdt + version: 1.3.0-alpha.1 + description: | + API for BDT resouce management. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. +externalDocs: + description: 3GPP TS 29.122 V18.2.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' +security: + - {} + - oAuth2ClientCredentials: [] +servers: + - url: '{apiRoot}/3gpp-bdt/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. +paths: + /{scsAsId}/subscriptions: + parameters: + - name: scsAsId + description: String identifying the SCS/AS. + in: path + required: true + schema: + type: string + get: + summary: Fetch all active background data transfer subscription resources for a given SCS/AS. + operationId: FetchAllActiveBDTSubscriptions + tags: + - BDT Subscription + responses: + '200': + description: all BDT policy subscriptions. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/Bdt' + minItems: 0 + description: individual BDT policy subscription. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +post: + summary: Creates a new background data transfer subscription resource. + operationId: CreateBDTSubscription + tags: + - BDT Subscription + requestBody: + description: Contains the data to create a BDT subscription. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/Bdt' + callbacks: + bDTWarningNotification: + '{ $request.body#/notificationDestination }': + post: + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ExNotification' + responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +responses: + '201': + description: Background data transfer policies offered to the SCS/AS. + content: + application/json: + schema: + $ref: '#/components/schemas/Bdt' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '409': + $ref: 'TS29122_CommonData.yaml#/components/responses/409' + '411': + +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/subscriptions/{subscriptionId}: + parameters: + - name: scsAsId + description: String identifying the SCS/AS. + in: path + required: true + schema: + type: string + - name: subscriptionId + description: String identifying the individual BDT policy resource in the SCEF. + in: path + required: true + schema: + type: string + get: + summary: Read a background data transfer subscription resource. + operationId: FetchIndBDTSubscription + tags: + - Individual BDT Subscription + responses: + '200': + description: Background data transfer policies offered to and selected by the SCEF. + content: + application/json: + schema: + $ref: '#/components/schemas/Bdt' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + put: + summary: Update a background data transfer subscription resource for negotiation of background data transfer policy. + operationId: UpdateBDTSubscription + tags: + - Individual BDT Subscription + requestBody: + description: Parameters to update/replace the existing BDT subscription + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/Bdt' + responses: + '200': + description: OK (Successful update of the BDT subscription) + content: + +``` + +``` + application/json: + schema: + $ref: '#/components/schemas/Bdt' + '204': + description: No Content. The Individual BDT Subscription resource was updated +successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + patch: + summary: Modify a background data transfer subscription resource to select one of the transfer +policies offered by the SCEF. + operationId: ModifyBDTSubscription + tags: + - Individual BDT Subscription + requestBody: + description: Contains information to be performed on the Bdt data structure to select a +transfer policy. + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/BdtPatch' + responses: + '200': + description: The Individual BDT Policy resource is modified with a selected policy and a +representation of that resource is returned. + content: + application/json: + schema: + $ref: '#/components/schemas/Bdt' + '204': + description: The Individual BDT Policy resource is modified with a selected policy. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +``` + +``` + + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + summary: Delete a background data transfer resource. + operationId: DeleteBDTSubscription + tags: + - Individual BDT Subscription + responses: + '204': + description: The Individual BDT Policy resource is deleted. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} +schemas: + Bdt: + description: Represents a Background Data Transfer subscription. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + aspId: + type: string + description: Identifies an application service provider. + volumePerUE: + $ref: 'TS29122_CommonData.yaml#/components/schemas/UsageThreshold' + numberOfUEs: + type: integer + minimum: 1 + description: Identifies the number of UEs. + desiredTimeWindow: + $ref: 'TS29122_CommonData.yaml#/components/schemas/TimeWindow' + locationArea: + $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea' + locationArea5G: + $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea5G' + referenceId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/BdtReferenceId' + transferPolicies: + type: array + items: + $ref: '#/components/schemas/TransferPolicy' + minItems: 1 + description: Identifies an offered transfer policy. + readOnly: true + selectedPolicy: + type: integer + description: Identity of the selected background data transfer policy. Shall not be +present in initial message exchange, can be provided by NF service consumer in a subsequent message +exchange. + +``` + +``` + + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + warnNotifEnabled: + type: boolean + description: > + Indicates whether the BDT warning notification is enabled (true) or not (false). Default + value is false. + trafficDes: + $ref: '#/components/schemas/TrafficDescriptor' + required: + - volumePerUE + - numberOfUEs + - desiredTimeWindow + BdtPatch: + description: Represents a Background Data Transfer subscription modification request. + type: object + properties: + selectedPolicy: + type: integer + description: Identity of the selected background data transfer policy. + warnNotifEnabled: + type: boolean + description: > + Indicates whether the BDT warning notification is enabled (true) or not (false). + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + required: + - selectedPolicy + TransferPolicy: + description: Represents an offered transfer policy sent from the SCEF to the SCS/AS, or a + selected transfer policy sent from the SCS/AS to the SCEF. + type: object + properties: + bdtPolicyId: + type: integer + description: Identifier for the transfer policy + maxUplinkBandwidth: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bandwidth' + maxDownlinkBandwidth: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bandwidth' + ratingGroup: + type: integer + minimum: 0 + description: Indicates the rating group during the time window. + timeWindow: + $ref: 'TS29122_CommonData.yaml#/components/schemas/TimeWindow' + required: + - bdtPolicyId + - ratingGroup + - timeWindow + ExNotification: + description: Represents a Background Data Transfer notification. + type: object + properties: + bdtRefId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/BdtReferenceId' + locationArea5G: + $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea5G' + timeWindow: + $ref: 'TS29122_CommonData.yaml#/components/schemas/TimeWindow' + candPolicies: + type: array + items: + $ref: '#/components/schemas/TransferPolicy' + minItems: 1 + description: This IE indicates a list of the candidate transfer policies from which the AF + may select a new transfer policy due to network performance degradation. + required: + - bdtRefId + TrafficDescriptor: + type: string + description: Identify a traffic descriptor as defined in Figure 5.2.2 of 3GPP TS 24.526, + octets v+5 to w. + +``` + +## A.5 ChargeableParty API + +``` + +openapi: 3.0.0 +info: + title: 3gpp-chargeable-party + version: 1.3.0-alpha.1 + description: | + API for Chargeable Party management. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. +externalDocs: + description: 3GPP TS 29.122 V18.1.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' +security: + - {} + - oAuth2ClientCredentials: [] +servers: + - url: '{apiRoot}/3gpp-chargeable-party/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. +paths: + /{scsAsId}/transactions: + get: + summary: Read all or queried chargeable party transaction resources for a given SCS/AS. + operationId: FetchAllChargeablePartyTransactions + tags: + - Chargeable Party Transaction Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: ip-addrs + in: query + description: The IP address(es) of the requested UE(s). + required: false + content: + application/json: + schema: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr' + minItems: 1 + - name: ip-domain + in: query + description: The IPv4 address domain identifier. The attribute may only be provided if IPv4 address is included in the ip-addrs query parameter. + required: false + schema: + type: string + - name: mac-addrs + in: query + description: The MAC address(es) of the requested UE(s). + required: false + schema: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' + minItems: 1 + responses: + '200': + description: OK (successful query of Chargeable Party resource) + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/ChargeableParty' + minItems: 0 + description: individual BDT policy subscription. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +post: + summary: Create a new chargeable party transaction resource. + operationId: CreateChargeablePartyTransaction + tags: + - Chargeable Party Transaction Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + requestBody: + description: representation of the Chargeable Party resource to be Created in the SCEF + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ChargeableParty' + callbacks: + eventNotification: + '{ $request.body#/notificationDestination }': + post: + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/NotificationData' + responses: + '204': + description: No Content (The successful acknowledgement of the notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +``` + +``` +responses: + '201': + description: successful creation of a chargeable party resource + content: + application/json: + schema: + $ref: '#/components/schemas/ChargeableParty' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/transactions/{transactionId}: + get: + summary: Read a chargeable party resource for a given SCS/AS and a transaction Id. + operationId: FetchIndChargeablePartyTransaction + tags: + - Individual chargeable party resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string + responses: + '200': + description: OK (successful query of a chargeable party resource) + content: + application/json: + schema: + $ref: '#/components/schemas/ChargeableParty' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +``` + +``` +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Updates a existing chargeable party resource for a given SCS/AS and transaction Id. + operationId: UpdateChargeablePartyTransaction + tags: + - Individual chargeable party resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string + requestBody: + description: representation of the chargeable party resource to be udpatd in the SCEF + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/ChargeablePartyPatch' + responses: + '200': + description: successful update of a chargeable party resource + content: + application/json: + schema: + $ref: '#/components/schemas/ChargeableParty' + '204': + description: No Content + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Deletes a chargeable party resource for a given SCS/AS and a transcation Id. + operationId: DeleteChargeablePartyTransaction + tags: + - Individual chargeable party resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true +``` + +``` + + schema: + type: string +- name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string +responses: + '204': + description: successful deletion of an resource of chargeable party + '200': + description: OK (Successful deletion of the existing subscription) + content: + application/json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/NotificationData' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} +schemas: + ChargeableParty: + description: Represents the configuration of a chargeable party. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + dnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' + snssai: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + requestTestNotification: + type: boolean + description: Set to true by the SCS/AS to request the SCEF to send a test notification as +defined in clause 5.2.5.3. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + exteraAppId: + type: string + description: Identifies the external Application Identifier. + ipv4Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv4Addr' + ipDomain: + type: string + ipv6Addr : + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6Addr' + macAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' + flowInfo: + +``` + +``` + + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/FlowInfo' + minItems: 1 + description: Describes the application flows. + ethFlowInfo: + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EthFlowDescription' + minItems: 1 + description: Identifies Ethernet packet flows. + sponsorInformation: + $ref: 'TS29122_CommonData.yaml#/components/schemas/SponsorInformation' + sponsoringEnabled: + type: boolean + description: > + Indicates whether the sponsoring data connectivity is enabled (true) or not (false). + referenceId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/BdtReferenceId' + servAuthInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ServAuthInfo' + usageThreshold: + $ref: 'TS29122_CommonData.yaml#/components/schemas/UsageThreshold' + events: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Event' + minItems: 1 + description: Represents the list of event(s) to which the SCS/AS requests to subscribe to. + required: + - notificationDestination + - sponsorInformation + - sponsoringEnabled + ChargeablePartyPatch: + description: Represents a modification request of a chargeable party resource. + type: object + properties: + flowInfo: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/FlowInfo' + minItems: 1 + description: Describes the IP flows. + exterAppId: + type: string + description: Identifies the external Application Identifier. + ethFlowInfo: + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EthFlowDescription' + minItems: 1 + description: Identifies Ethernet packet flows. + sponsoringEnabled: + type: boolean + description: > + Indicates whether the sponsoring data connectivity is enabled (true) or not (false). + referenceId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/BdtReferenceId' + usageThreshold: + $ref: 'TS29122_CommonData.yaml#/components/schemas/UsageThresholdRm' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + events: + description: Represents the list of event(s) to which the SCS/AS requests to subscribe to. + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Event' + minItems: 1 + +``` + +## A.6 NIDD API + +openapi: 3.0.0 + +``` + +info: + title: 3gpp-nidd + +``` + +``` +version: 1.3.0-alpha.1 +description: | + API for non IP data delivery. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.122 V18.1.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' + +security: + - {} + - oAuth2ClientCredentials: [] + +servers: + - url: '{apiRoot}/3gpp-nidd/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. + +paths: + /{scsAsId}/configurations: + parameters: + - name: scsAsId + description: String identifying the SCS/AS. + in: path + required: true + schema: + type: string + get: + summary: Read all NIDD configuration resources for a given SCS/AS. + operationId: FetchAllNIDDConfigurations + tags: + - NIDD configurations + responses: + '200': + description: all NIDD configurations. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/NiddConfiguration' + minItems: 0 + description: individual NIDD configuration. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + post: + summary: Create a new NIDD configuration resource. + operationId: CreateNIDDConfiguration + tags: + - NIDD configurations + requestBody: + description: Contains the data to create a NIDD configuration. + required: true + content: + application/json: +``` + +``` + + schema: + $ref: '#/components/schemas/NiddConfiguration' +responses: + '201': + description: NIDD configuration is successfully created. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddConfiguration' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +callbacks: + niddNotifications: + "{$request.body#/notificationDestination}": + post: + requestBody: + description: > + Notification for NIDD configuration status, MO NIDD, MT NIDD delivery report. + required: true + content: + application/json: + schema: + oneOf: + - $ref: '#/components/schemas/NiddConfigurationStatusNotification' + - $ref: '#/components/schemas/NiddUplinkDataNotification' + - $ref: '#/components/schemas/NiddDownlinkDataDeliveryStatusNotification' + - $ref: '#/components/schemas/GmdNiddDownlinkDataDeliveryNotification' + - $ref: '#/components/schemas/ManagePortNotification' + responses: + '204': + description: Expected response to a successful callback processing without a body + '200': + description: Expected response to a successful callback processing with a body + content: + application/json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Acknowledgement' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + +``` + +``` + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/configurations/{configurationId}: + parameters: + - name: scsAsId + description: String identifying the SCS/AS. + in: path + required: true + schema: + type: string + - name: configurationId + description: String identifying the individual NIDD configuration resource in the SCEF. + in: path + required: true + schema: + type: string + get: + summary: Read an NIDD configuration resource. + operationId: FetchIndNIDDConfiguration + tags: + - Individual NIDD configuration + responses: + '200': + description: The individual NIDD configuration is successfully retrieved. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddConfiguration' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + patch: + summary: Modify an existing NIDD configuration resource. + operationId: ModifyNIDDConfiguration + tags: + - Individual NIDD configuration + requestBody: + description: Contains information to be applied to the individual NIDD configuration. + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/NiddConfigurationPatch' + responses: + '200': + description: > + The Individual NIDD configuration is modified successfully and a representation + of that resource is returned. + content: + application/json: +``` + +``` + + schema: + $ref: '#/components/schemas/NiddConfiguration' + '204': + description: > + The Individual NIDD configuration is modified successfully and no content + is to be sent in the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + summary: Delete an existing NIDD configuration resource. + operationId: DeleteNIDDConfiguration + tags: + - Individual NIDD configuration + responses: + '204': + description: The Individual NIDD configuration is deleted. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/configurations/{configurationId}/downlink-data-deliveries: + parameters: + - name: scsAsId + description: String identifying the SCS/AS. + in: path + required: true + schema: + type: string + - name: configurationId + description: String identifying the individual NIDD configuration resource in the SCEF. + in: path + required: true + schema: + type: string + get: + summary: Read all pending NIDD downlink data delivery resources related to a particular NIDD + configuration resource. + +``` + +``` +operationId: FetchAllDownlinkDataDeliveries +tags: + - NIDD downlink data deliveries +responses: + '200': + description: all NIDD downlink data deliveries. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/NiddDownlinkDataTransfer' + minItems: 0 + description: individual NIDD downlink data delivery. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +post: + summary: Create an NIDD downlink data delivery resource related to a particular NIDD +configuration resource. + operationId: CreateDownlinkDataDelivery + tags: + - NIDD downlink data deliveries + requestBody: + description: Contains the data to create a NIDD downlink data delivery. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataTransfer' + responses: + '200': + description: NIDD downlink data delivery is successful. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataTransfer' + '201': + description: NIDD downlink data delivery is pending. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataTransfer' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +``` + +``` + + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The NIDD downlink data delivery request was not successful. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataDeliveryFailure' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/configurations/{configurationId}/downlink-data-deliveries/{downlinkDataDeliveryId}: + parameters: + - name: scsAsId + description: String identifying the SCS/AS. + in: path + required: true + schema: + type: string + - name: configurationId + description: String identifying the individual NIDD configuration resource in the SCEF. + in: path + required: true + schema: + type: string + - name: downlinkDataDeliveryId + description: String identifying the individual NIDD downlink data delivery in the SCEF. + in: path + required: true + schema: + type: string + get: + summary: Read pending NIDD downlink data delivery resource. + operationId: FetchIndDownlinkDataDelivery + tags: + - Individual NIDD downlink data delivery + responses: + '200': + description: The individual NIDD downlink data delivery is successfully retrieved. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataTransfer' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + put: + summary: Replace an NIDD downlink data delivery resource. + operationId: UpdateIndDownlinkDataDelivery + tags: + +``` + +``` +- Individual NIDD downlink data delivery +requestBody: + description: > + Contains information to be applied to the individual NIDD downlink data delivery. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataTransfer' +responses: + '200': + description: > + The pending NIDD downlink data is replaced successfully but delivery is pending. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataTransfer' + '204': + description: > + The NIDD downlink data delivery has been replaced successfully and no content + is to be sent in the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '409': + $ref: 'TS29122_CommonData.yaml#/components/responses/409' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The NIDD downlink data replacement request was not successful. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataDeliveryFailure' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +patch: + summary: Modify an existing Individual NIDD downlink data delivery resource. + operationId: ModifyIndDownlinkDataDelivery + tags: + - Individual NIDD downlink data delivery + requestBody: + description: > + Contains the parameters to update an individual NIDD downlink data delivery resource. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataTransferPatch' + responses: + '200': + description: > + OK. The modification of the Individual NIDD downlink data delivery resource was + successful and an updated representation of the resource within the + NiddDownlinkDataTransfer data structure in the response message body is returned + by the SCEF. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataTransfer' + '204': +``` + +``` + +description: > + No Content. The modification of the Individual NIDD downlink data delivery resource + was successful and no content is to be sent in the response message body. +'307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' +'308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'409': + $ref: 'TS29122_CommonData.yaml#/components/responses/409' +'411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + description: > + Internal Server Error. The NIDD downlink data modification request was not successful. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataDeliveryFailure' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + summary: Delete an NIDD downlink data delivery resource. + operationId: DeleteIndDownlinkDataDelivery + tags: + - Individual NIDD downlink data delivery + responses: + '204': + description: The pending NIDD downlink data is deleted. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '409': + $ref: 'TS29122_CommonData.yaml#/components/responses/409' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The NIDD downlink data cancellation request was not successful. + content: + application/json: + schema: + $ref: '#/components/schemas/NiddDownlinkDataDeliveryFailure' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/configurations/{configurationId}/rds-ports: + parameters: + - name: scsAsId + description: String identifying the SCS/AS. + in: path + required: true + schema: + type: string + +``` + +``` + +- name: configurationId + description: String identifying the individual NIDD configuration resource in the SCEF. + in: path + required: true + schema: + type: string +get: + summary: Read all RDS ManagePort Configurations. + operationId: FetchAllManagePortConfigurations + tags: + - ManagePort Configurations + responses: + '200': + description: all ManagePort configurations. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/ManagePort' + minItems: 0 + description: individual ManagePort configuration. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/configurations/{configurationId}/rds-ports/{portId}: + parameters: + - name: scsAsId + description: String identifying the SCS/AS. + in: path + required: true + schema: + type: string + - name: configurationId + description: String identifying the individual NIDD configuration resource in the SCEF. + in: path + required: true + schema: + type: string + - name: portId + description: The UE port number. + in: path + required: true + schema: + type: string + pattern: '^(ue([0-9]|(1[0-5]))-ef([0-9]|(1[0-5])) )$' +get: + summary: Read an Individual ManagePort Configuration resource to query port numbers. + operationId: FetchIndManagePortConfiguration + tags: + - Individual ManagePort Configuration + responses: + '200': + description: The individual ManagePort configuration is successfully retrieved. + content: + application/json: + schema: + $ref: '#/components/schemas/ManagePort' + '307': + +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +put: + summary: Create a new Individual ManagePort Configuration resource to reserve port numbers. + operationId: UpdateIndManagePortConfiguration + tags: + - Individual ManagePort Configuration + requestBody: + description: Contains information to be applied to the individual ManagePort configuration. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ManagePort' + responses: + '201': + description: The individual ManagePort configuration is created. + content: + application/json: + schema: + $ref: '#/components/schemas/ManagePort' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '202': + description: The request is accepted and under processing. + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '409': + $ref: 'TS29122_CommonData.yaml#/components/responses/409' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The request was not successful. + content: + application/problem+json: + schema: + $ref: '#/components/schemas/RdsDownlinkDataDeliveryFailure' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + summary: Delete an Individual ManagePort Configuration resource to release port numbers. + +``` + +``` +operationId: DeleteIndManagePortConfiguration +tags: + - Individual ManagePort Configuration +responses: + '202': + description: The request is accepted and under processing. + '204': + description: The individual ManagePort configuration is deleted. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '409': + $ref: 'TS29122_CommonData.yaml#/components/responses/409' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The request was not successful. + content: + application/problem+json: + schema: + $ref: '#/components/schemas/RdsDownlinkDataDeliveryFailure' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + NiddConfiguration: + description: Represents the configuration for NIDD. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + mtcProviderId: + type: string + description: Identifies the MTC Service Provider and/or MTC Application. + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + duration: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + reliableDataService: + type: boolean + description: > + Indicates whether the reliable data service (as defined in clause 4.5.14.3 of 3GPP TS + 23.682) acknowledgement is requested (true) or not (false). Default value is false. + rdsPorts: + type: array + items: + $ref: '#/components/schemas/RdsPort' + minItems: 1 + description: > + Indicates the static port configuration that is used for reliable data transfer between + specific applications using RDS (as defined in clause 5.2.4 and + 5.2.5 of 3GPP TS 24.250). +``` + +``` +pdnEstablishmentOption: + $ref: '#/components/schemas/PdnEstablishmentOptions' +notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' +requestTestNotification: + type: boolean + description: > + Set to true by the SCS/AS to request the SCEF to send a test notification as defined + in clause 5.2.5.3. Set to false or omitted otherwise. +websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' +maximumPacketSize: + type: integer + minimum: 1 + description: > + The Maximum Packet Size is the maximum NIDD packet size that was transferred to + the UE by the SCEF in the PCO, see clause 4.5.14.1 of 3GPP TS 23.682. If no maximum + packet size was provided to the UE by the SCEF, the SCEF sends a default configured + max packet size to SCS/AS. Unit bit. + readOnly: true +niddDownlinkDataTransfers: + type: array + items: + $ref: '#/components/schemas/NiddDownlinkDataTransfer' + minItems: 1 + description: > + The downlink data deliveries that needed to be executed by the SCEF. The cardinality of + the property shall be 0..1 in the request and 0..N in the response (i.e. response may + contain multiple buffered MT NIDD). + status: + $ref: '#/components/schemas/NiddStatus' + required: + - notificationDestination + oneOf: + - required: [externalId] + - required: [msisdn] + - required: [externalGroupId] + +NiddDownlinkDataTransfer: + description: Represents the received NIDD downlink data from the SCS/AS. + type: object + properties: + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + data: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + reliableDataService: + type: boolean + description: > + Indicates whether the reliable data service (as defined in clause 4.5.14.3 of 3GPP TS + 23.682) acknowledgement is requested (true) or not (false). Default value is false. + rdsPort: + $ref: '#/components/schemas/RdsPort' + maximumLatency: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + priority: + type: integer + description: > + It is used to indicate the priority of the non-IP data packet relative to other + non-IP data packets. + pdnEstablishmentOption: + $ref: '#/components/schemas/PdnEstablishmentOptions' + deliveryStatus: + $ref: '#/components/schemas/DeliveryStatus' + requestedRetransmissionTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + required: + - data + oneOf: + - required: [externalId] + - required: [msisdn] + - required: [externalGroupId] +``` + +``` +NiddUplinkDataNotification: + description: Represents NIDD uplink data to be notified to the SCS/AS. + type: object + properties: + niddConfiguration: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + data: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + reliableDataService: + type: boolean + description: > + Indicates whether the reliable data service acknowledgement is requested (true) or + not (false). + rdsPort: + $ref: '#/components/schemas/RdsPort' + required: + - niddConfiguration + - data + oneOf: + - required: [externalId] + - required: [msisdn] + +NiddDownlinkDataDeliveryStatusNotification: + description: Represents the delivery status of a specific NIDD downlink data delivery. + type: object + properties: + niddDownlinkDataTransfer: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + deliveryStatus: + $ref: '#/components/schemas/DeliveryStatus' + requestedRetransmissionTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + required: + - niddDownlinkDataTransfer + - deliveryStatus + +NiddConfigurationStatusNotification: + description: Represents an NIDD configuration status notification. + type: object + properties: + niddConfiguration: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + status: + $ref: '#/components/schemas/NiddStatus' + rdsCapIndication: + type: boolean + description: > + It indicates whether the network capability for the reliable data service is enabled + or not. + rdsPort: + $ref: '#/components/schemas/RdsPort' + required: + - niddConfiguration + - status + oneOf: + - required: [externalId] + - required: [msisdn] + +GmdNiddDownlinkDataDeliveryNotification: + description: Represents the delivery status of a specific group NIDD downlink data delivery. + type: object + properties: + niddDownlinkDataTransfer: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + gmdResults: + type: array + items: + $ref: '#/components/schemas/GmdResult' + minItems: 1 +``` + +``` + description: Indicates the group message delivery result. + required: + - niddDownlinkDataTransfer + - gmdResults + +RdsPort: + description: Represents the port configuration for Reliable Data Transfer. + type: object + properties: + portUE: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Port' + portSCEF: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Port' + required: + - portUE + - portSCEF + +GmdResult: + description: Represents the group message delivery result. + type: object + properties: + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + deliveryStatus: + $ref: '#/components/schemas/DeliveryStatus' + requestedRetransmissionTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + required: + - deliveryStatus + oneOf: + - required: [externalId] + - required: [msisdn] + +NiddDownlinkDataDeliveryFailure: + description: Represents information related to a failure delivery result. + type: object + properties: + problemDetail: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + requestedRetransmissionTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + required: + - problemDetail + +ManagePort: + description: Represents the configuration of a RDS dynamic port management. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + appId: + type: string + description: Identifies the application. + manageEntity: + $ref: '#/components/schemas/ManageEntity' + skipUeInquiry: + type: boolean + description: Indicate whether to skip UE inquiry. + supportedFormats: + type: array + items: + $ref: '#/components/schemas/SerializationFormat' + minItems: 1 + description: > + Indicates the serialization format(s) that are supported by the SCS/AS on the associated + RDS port. + configuredFormat: + $ref: '#/components/schemas/SerializationFormat' + required: + - appId + +ManagePortNotification: + description: Represents a ManagePort notification of port numbers that are reserved. + type: object + properties: + niddConfiguration: +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + managedPorts: + type: array + items: + $ref: '#/components/schemas/ManagePort' + minItems: 1 + description: Indicates the reserved RDS port configuration information. + required: + - niddConfiguration + oneOf: + - required: [externalId] + - required: [msisdn] + +RdsDownlinkDataDeliveryFailure: + description: Represents the failure delivery result for RDS. + allOf: + - $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + - type: object + properties: + requestedRetransmissionTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + supportedUeFormats: + type: array + items: + $ref: '#/components/schemas/SerializationFormat' + minItems: 1 + description: > + Indicates the serialization format(s) that are supported by the UE on the associated + RDS port. + +NiddDownlinkDataTransferPatch: + description: > + Represents the parameters to request the modification of an Individual NIDD Downlink Data + Delivery resource. + type: object + properties: + data: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + reliableDataService: + type: boolean + description: > + Indicates whether the reliable data service (as defined in clause 4.5.14.3 of 3GPP TS + 23.682) acknowledgement is requested (true) or not (false). + rdsPort: + $ref: '#/components/schemas/RdsPort' + maximumLatency: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + priority: + type: integer + description: > + It is used to indicate the priority of the non-IP data packet relative to other + non-IP data packets. + pdnEstablishmentOption: + $ref: '#/components/schemas/PdnEstablishmentOptions' + +PdnEstablishmentOptions: + anyOf: + - type: string + enum: + - WAIT_FOR_UE + - INDICATE_ERROR + - SEND_TRIGGER + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents PDN establishment options that describe the network behaviour when + there is no PDN connection towards the addressed UE. + Possible values are: + - WAIT_FOR_UE: wait for the UE to establish the PDN connection + - INDICATE_ERROR: respond with an error cause + - SEND_TRIGGER: send a device trigger + +``` + +``` + +PdnEstablishmentOptionsRm: + description: > + Represents the same information as the PdnEstablishmentOptions data type with the + difference that it allows also the null value. + anyOf: + - $ref: '#/components/schemas/PdnEstablishmentOptions' + - $ref: 'TS29571_CommonData.yaml#/components/schemas/NullValue' + +DeliveryStatus: + anyOf: + - type: string + enum: + - SUCCESS + - SUCCESS_NEXT_HOP_ACKNOWLEDGED + - SUCCESS_NEXT_HOP_UNACKNOWLEDGED + - SUCCESS_ACKNOWLEDGED + - SUCCESS_UNACKNOWLEDGED + - TRIGGERED + - BUFFERING + - BUFFERING_TEMPORARILY_NOT_REACHABLE + - SENDING + - FAILURE + - FAILURE_RDS_DISABLED + - FAILURE_NEXT_HOP + - FAILURE_TIMEOUT + - FAILURE_TEMPORARILY_NOT_REACHABLE + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the status of a downlink NIDD data delivery resource. + Possible values are: + - SUCCESS: Success but details not provided + - SUCCESS_NEXT_HOP_ACKNOWLEDGED: Successful delivery to the next hop with acknowledgment. + - SUCCESS_NEXT_HOP_UNACKNOWLEDGED: Successful delivery to the next hop without + acknowledgment + - SUCCESS_ACKNOWLEDGED: Reliable delivery was acknowledged by the UE + - SUCCESS_UNACKNOWLEDGED: Reliable delivery was not acknowledged by the UE + - TRIGGERED: The SCEF triggered the device and is buffering the data. + - BUFFERING: The SCEF is buffering the data due to no PDN connection established. + - BUFFERING_TEMPORARILY_NOT_REACHABLE: The SCEF has been informed that the UE is temporarily + not reachable but is buffering the data + - SENDING: The SCEF has forwarded the data, but they may be stored elsewhere + - FAILURE: Delivery failure but details not provided + - FAILURE_RDS_DISABLED: RDS was disabled + - FAILURE_NEXT_HOP: Unsuccessful delivery to the next hop. + - FAILURE_TIMEOUT: Unsuccessful delivery due to timeout. + - FAILURE_TEMPORARILY_NOT_REACHABLE: The SCEF has been informed that the UE is temporarily + not reachable without buffering the data. + readOnly: true + +NiddStatus: + anyOf: + - type: string + enum: + - ACTIVE + - TERMINATED_UE_NOT_AUTHORIZED + - TERMINATED + - RDS_PORT_UNKNOWN + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the status of a NIDD configuration. + Possible values are: + - ACTIVE: The NIDD configuration is active. + - TERMINATED_UE_NOT_AUTHORIZED: The NIDD configuration was terminated because the UE's + authorisation was revoked. + - TERMINATED: The NIDD configuration was terminated. + - RDS_PORT_UNKNOWN: The RDS port is unknown. + readOnly: true + +ManageEntity: + +``` + +``` + +anyOf: +- type: string + enum: + - UE + - AS +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Represents the origin that manages the RDS port. + Possible values are: + - UE: Representing the UE. + - AS: Representing the Application Server. +readOnly: true + +SerializationFormat: +anyOf: +- type: string + enum: + - CBOR + - JSON + - XML +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Represents a serialization format associated with an RDS port which is applicable + for the Rds_serialization_format feature. + Possible values are + - CBOR: The CBOR Serialzition format + - JSON: The JSON Serialzition format + - XML: The XML Serialzition format + +NiddConfigurationPatch: +description: Represents the parameters to update a NIDD configuration. +type: object +properties: + duration: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTimeRm' + reliableDataService: + type: boolean + description: > + Indicates whether the reliable data service (as defined in clause 4.5.14.3 of 3GPP TS + 23.682) acknowledgement is requested (true) or not (false). + nullable: true + rdsPorts: + type: array + items: + $ref: '#/components/schemas/RdsPort' + minItems: 1 + description: > + Indicates the static port configuration that is used for reliable data transfer between + specific applications using RDS (as defined in clause 5.2.4 and 5.2.5 + of 3GPP TS 24.250). + pdnEstablishmentOption: + $ref: '#/components/schemas/PdnEstablishmentOptionsRm' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + +``` + +## A.7 DeviceTriggering API + +openapi: 3.0.0 + +``` + +info: + title: 3gpp-device-triggering + version: 1.3.0-alpha.1 + description: | + API for device trigger. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +``` + +``` +externalDocs: + description: 3GPP TS 29.122 V18.1.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' + +security: +- {} +- oAuth2ClientCredentials: [] + +servers: +- url: '{apiRoot}/3gpp-device-triggering/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. + +paths: + /{scsAsId}/transactions: + get: + summary: read all active device triggering transactions for a given SCS/AS. + operationId: FetchAllDeviceTriggeringTransactions + tags: + - Device Triggering Transactions + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ScsAsId' + responses: + '200': + description: > + OK (Successful get all of the active device triggering transactions for the SCS/AS) + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/DeviceTriggering' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + post: + summary: Create a long-term transaction for a device triggering. + operationId: CreateDeviceTriggeringTransaction + tags: + - Device Triggering API Transactions + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ScsAsId' + requestBody: + description: Parameters to request a device triggering delivery. + required: true + content: + application/json: +``` + +``` + + schema: + $ref: '#/components/schemas/DeviceTriggering' + callbacks: + notificationDestination: + '{request.body#/notificationDestination}': + post: + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/DeviceTriggeringDeliveryReportNotification' + responses: + '200': + description: OK (successful notification) + content: + application/json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Acknowledgement' + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +responses: + '201': + description: Created (Successful creation of subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/DeviceTriggering' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + +``` + +``` +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/transactions/{transactionId}: + get: + summary: Read a device triggering transaction resource. + operationId: FetchIndDeviceTriggeringTransaction + tags: + - Individual Device Triggering Transaction + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ScsAsId' + - name: transactionId + in: path + description: Identifier of the transaction resource + required: true + schema: + type: string + responses: + '200': + description: OK (Successful get the active subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/DeviceTriggering' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + put: + summary: Replace an existing device triggering transaction resource and the corresponding device trigger request. + operationId: UpdateIndDeviceTriggeringTransaction + tags: + - Individual Device Triggering Transaction + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ScsAsId' + - name: transactionId + in: path + description: Identifier of the transaction resource + required: true + schema: + type: string + requestBody: + description: Parameters to update/replace the existing device triggering + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/DeviceTriggering' +``` + +``` +responses: + '200': + description: OK (Successful update of the device triggering) + content: + application/json: + schema: + $ref: '#/components/schemas/DeviceTriggering' + '204': + description: No Content (Successful update of the device triggering) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Modify an existing Individual Device Triggering Transaction resource and the +corresponding device triggering request. + operationId: ModifyIndDeviceTriggeringTransaction + tags: + - Individual Device Triggering Transaction + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ScsAsId' + - name: transactionId + in: path + description: Identifier of the transaction resource + required: true + schema: + type: string + requestBody: + description: Parameters to request the modification of the existing Individual Device +Triggering Transaction resource. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/DeviceTriggeringPatch' + responses: + '200': + description: > + OK. The Individual Device Triggering Transaction resource was successfully modified + and a representation of the modified Individual Device Triggering Transaction resource + within the DeviceTriggering data structure including the "deliveryResult" attribute is + returned by the SCEF. + content: + application/json: + schema: + $ref: '#/components/schemas/DeviceTriggering' + '204': + description: > + No Content. The Individual Device Triggering Transaction resource was successfully + modified no content is returned in the response message body. + '307': +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + summary: Deletes an already existing device triggering transaction. + operationId: DeleteIndDeviceTriggeringTransaction + tags: + - Individual Device Triggering Transaction + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ScsAsId' + - name: transactionId + in: path + description: Identifier of the transaction resource + required: true + schema: + type: string + responses: + '204': + description: No Content (Successful deletion of the existing subscription) + '200': + description: OK (Successful deletion of the existing subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/DeviceTriggering' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + +``` + +``` +clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + DeviceTriggering: + description: Represents device triggering related information. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + validityPeriod: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + priority: + $ref: '#/components/schemas/Priority' + applicationPortId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Port' + appSrcPortId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Port' + triggerPayload: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + requestTestNotification: + type: boolean + description: > + Set to true by the SCS/AS to request the SCEF to send a test notification as defined in + clause 5.2.5.3. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + deliveryResult: + $ref: '#/components/schemas/DeliveryResult' + required: + - validityPeriod + - priority + - applicationPortId + - triggerPayload + - notificationDestination + oneOf: + - required: [externalId] + - required: [msisdn] + + DeviceTriggeringDeliveryReportNotification: + description: Represents a device triggering delivery report notification. + type: object + properties: + transaction: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + result: + $ref: '#/components/schemas/DeliveryResult' + required: + - transaction + - result + + DeviceTriggeringPatch: + description: Represents device triggering related information. + type: object + properties: + validityPeriod: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + priority: + $ref: '#/components/schemas/Priority' + applicationPortId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Port' + appSrcPortId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Port' + triggerPayload: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + requestTestNotification: + type: boolean +``` + +``` + + description: > + Set to true by the SCS/AS to request the SCEF to send a test notification as defined + in clause 5.2.5.3. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + + DeliveryResult: + anyOf: + - type: string + enum: + - SUCCESS + - UNKNOWN + - FAILURE + - TRIGGERED + - EXPIRED + - UNCONFIRMED + - REPLACED + - TERMINATE + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the result of the delivery of a device triggering request. + Possible values are: + - SUCCESS: This value indicates that the device action request was successfully completed. + - UNKNOWN: This value indicates any unspecified errors. + - FAILURE: This value indicates that this trigger encountered a delivery error and is deemed + permanently undeliverable. + - TRIGGERED: This value indicates that device triggering request is accepted by the SCEF. + - EXPIRED: This value indicates that the validity period expired before the trigger could + be delivered. + - UNCONFIRMED: This value indicates that the delivery of the device action request is not + confirmed. + - REPLACED: This value indicates that the device triggering replacement request is accepted + by the SCEF. + - TERMINATE: This value indicates that the delivery of the device action request is + terminated by the SCS/AS. + readOnly: true + + Priority: + anyOf: + - type: string + enum: + - NO_PRIORITY + - PRIORITY + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the priority indication for a trigger payload. + Possible values are: + - NO_PRIORITY: This value indicates that the device trigger has no priority. + - PRIORITY: This value indicates that the device trigger has priority. + +``` + +## A.8 GMDViaMBMS APIs + +### A.8.1 GMDViaMBMSbyMB2 API + +``` + +openapi: 3.0.0 +info: + title: GMDViaMBMSbyMB2 + description: | + API for Group Message Delivery via MBMS by MB2 + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: 1.3.0-alpha.1 +externalDocs: + description: 3GPP TS 29.122 V18.4.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' +security: + +``` + +``` +- {} +- oAuth2ClientCredentials: [] +servers: +- url: '{apiRoot}/3gpp-group-message-delivery-mb2/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. +paths: + /{scsAsId}/tmgi-allocation: + get: + summary: read all TMGI Allocation resource for a given SCS/AS + operationId: FetchAllTMGIAllocations + tags: + - TMGI Allocation Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + responses: + '200': + description: OK (successful query of TMGI Allocation resource) + content: + application/json: + schema: + $ref: '#/components/schemas/TMGIAllocation' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + + post: + summary: Creates a new TMGI Allocation resource for a given SCS/AS. + operationId: CreateTMGIAllocation + tags: + - TMGI Allocation Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + requestBody: + description: representation of the TMGI Allocation to be created in the SCEF + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/TMGIAllocation' + responses: + '201': + description: successful creation of an TMGI Allocation + content: + application/json: + schema: + $ref: '#/components/schemas/TMGIAllocation' +``` + +``` +headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/tmgi-allocation/{tmgi}: + get: + summary: Read a TMGI Allocation resource for a given SCS/AS and a TMGI. + operationId: FetchIndTMGIAllocation + tags: + - Individual TMGI Allocation Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: tmgi + in: path + description: TMGI + required: true + schema: + type: string + responses: + '200': + description: OK (successful query of TMGI Allocation resource) + content: + application/json: + schema: + $ref: '#/components/schemas/TMGIAllocation' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +``` + +``` +put: + summary: Updates an existing TMGI Allocation resource for a given SCS/AS and a TMGI. + operationId: UpdateIndTMGIAllocation + tags: + - Individual TMGI Allocation Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: tmgi + in: path + description: TMGI + required: true + schema: + type: string + requestBody: + description: representation of the TMGI Allocation to be updated in the SCEF + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/TMGIAllocation' + responses: + '200': + description: successful creation of an TMGI Allocation + content: + application/json: + schema: + $ref: '#/components/schemas/TMGIAllocation' + '204': + description: > + The TMGI expiration time renewal is successful, and no content is to be sent in + the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Updates an existing TMGI Allocation resource for a given SCS/AS and a TMGI. + operationId: ModifyIndTMGIAllocation + tags: + - Individual TMGI Allocation Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: tmgi + in: path + description: TMGI +``` + +``` + required: true + schema: + type: string + requestBody: + description: representation of the TMGI Allocation to be updated in the SCEF + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/TMGIAllocationPatch' + responses: + '200': + description: successful creation of an TMGI Allocation + content: + application/json: + schema: + $ref: '#/components/schemas/TMGIAllocation' + '204': + description: > + The TMGI expiration time renewal is successful, and no content is to be sent + in the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Deletes an existing TMGI Allocation resource for a given SCS/AS and a TMGI. + operationId: DeleteTMGIAllocation + tags: + - Individual TMGI Allocation Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: tmgi + in: path + description: TMGI + required: true + schema: + type: string + responses: + '204': + description: No Content, successful deletion of an TMGI Allocation + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/tmgi-allocation/{tmgi}/delivery-via-mbms: + get: + summary: Read all group message delivery via MBMS resource for a given SCS/AS and a TMGI. + operationId: FetchAllGMDViaMBMSByMB2 + tags: + - Delivery via MBMS Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: tmgi + in: path + description: TMGI + required: true + schema: + type: string + responses: + '200': + description: OK (successful query of Delivery via MBMS resource) + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByMb2' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + + post: + summary: Creates a new delivery via MBMS for a given SCS/AS and a TMGI. + operationId: CreateGMDViaMBMSByMB2 + tags: + - Delivery via MBMS Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: tmgi + in: path + description: TMGI + required: true + schema: + +``` + +``` + + type: string + requestBody: + description: representation of the GMD via MBMS by MB2 resource to be Created in the SCEF + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByMb2' + callbacks: + gMDByMb2Notification: + "{$request.body#/notificationDestination}": + post: + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/GMDByMb2Notification' + responses: + '200': + description: OK (The successful acknowledgement of the notification with a body) + content: + application/json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Acknowledgement' + '204': + description: successful notification + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +responses: + '201': + description: successful creation of an GMD via MBMS by MB2 resource + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByMb2' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + +``` + +``` + + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/tmgi-allocation/{tmgi}/deliVery-via-mbms/{transactionId}: + get: + summary: Read all group message delivery via MBMS resource for a given SCS/AS and a TMGI. + operationId: FetchIndDeliveryViaMBMS + tags: + - Individual Delivery via MBMS resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: tmgi + in: path + description: TMGI + required: true + schema: + type: string + - name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string + responses: + '200': + description: OK (successful query of an Delivery via MBMS resource) + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByMb2' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + + put: + summary: Updates a existing delivery via MBMS for a given SCS/AS, a TMGI and transaction Id. + operationId: UpdateIndDeliveryViaMBMS + tags: + - Individual Delivery via MBMS resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + +``` + +``` + +- name: tmgi + in: path + description: TMGI + required: true + schema: + type: string +- name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string +requestBody: + description: representation of the GMD via MBMS by MB2 resource to be updated in the SCEF + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByMb2' +responses: + '200': + description: successful update of an individual GMD via MBMS by MB2 resource + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByMb2' + '204': + description: > + The group message delivery is replaced successfully, and no content is to be sent + in the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Updates a existing delivery via MBMS for a given SCS/AS, a TMGI and transaction Id. + operationId: ModifyIndDeliveryViaMBMS + tags: + - Individual Delivery via MBMS resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: tmgi + in: path + description: TMGI + required: true + schema: + type: string + - name: transactionId + in: path + description: Identifier of transaction + +``` + +``` + + required: true + schema: + type: string + requestBody: + description: representation of the GMD via MBMS by MB2 resource to be udpated in the SCEF + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByMb2Patch' + responses: + '200': + description: successful update of an individual GMD via MBMS by MB2 resource + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByMb2' + '204': + description: > + The group message delivery is modified successfully, and no content is to be sent + in the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Deletes a delivery via MBMS resource for a given SCS/AS, a TMGI and a transcation Id. + operationId: DeleteIndDeliveryViaMBMS + tags: + - Individual Delivery via MBMS resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: tmgi + in: path + description: TMGI + required: true + schema: + type: string + - name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string + responses: + '204': + description: No Content, successful deletion of an resouce of deliery via MBMS + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + TMGIAllocation: + description: Represents an individual TMGI Allocation resource. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + mbmsLocArea: + $ref: '#/components/schemas/MbmsLocArea' + tmgiExpiration: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTimeRo' + + GMDViaMBMSByMb2: + description: Represents a group message delivery via MBMS by MB2. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + requestTestNotification: + type: boolean + description: > + Set to true by the SCS/AS to request the SCEF to send a test notification as + defined in clause 5.2.5.3. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + mbmsLocArea: + $ref: '#/components/schemas/MbmsLocArea' + messageDeliveryStartTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + groupMessagePayload: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + scefMessageDeliveryIPv4: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv4AddrRo' + scefMessageDeliveryIPv6: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6AddrRo' + scefMessageDeliveryPort: + $ref: 'TS29122_CommonData.yaml#/components/schemas/PortRo' + required: + - notificationDestination + + GMDByMb2Notification: + description: Represents a group message delivery notification. + type: object + +``` + +``` +properties: + transaction: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + deliveryTriggerStatus: + type: boolean + description: > + Indicates whether delivery of group message payload corresponding to the TMGI was + successful (TRUE) or not (FALSE) +required: + - transaction + - deliveryTriggerStatus + +TMGIAllocationPatch: + description: > + Represents the parameters to request the modification of a TMGI Allocation resource. + type: object + properties: + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + mbmsLocArea: + $ref: '#/components/schemas/MbmsLocArea' + +GMDViaMBMSByMb2Patch: + description: Represents a modification request of a group message delivery via MBMS by MB2. + type: object + properties: + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + mbmsLocArea: + $ref: '#/components/schemas/MbmsLocArea' + messageDeliveryStartTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + groupMessagePayload: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + +MbmsLocArea: + description: > + Represents a user location area whithin which is sent a group message delivery + via MBMS request. + type: object + properties: + cellId: + type: array + items: + type: string + minItems: 1 + description: > + Indicates a Cell Global Identification of the user which identifies the cell the + UE is registered. + enodeBId: + type: array + items: + type: string + minItems: 1 + description: Indicates an eNodeB in which the UE is currently located. + geographicArea: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea' + minItems: 1 + description: Identifies a geographic area of the user where the UE is located. + mbmsServiceAreaId: + type: array + items: + type: string + minItems: 1 + description: Identifies an MBMS Service Area Identity of the user where the UE is located. + civicAddress: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress' + minItems: 1 + description: Identifies a civic address of the user where the UE is located. +``` + +## A.8.2 GMDviaMBMSbyxMB API + +openapi: 3.0.0 + +info: + +title: GMDviaMBMSbyxMB +description: | + API for Group Message Delivery via MBMS by xMB + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. +version: 1.3.0-alpha.1 + +externalDocs: + +description: 3GPP TS 29.122 V18.1.0 T8 reference point for Northbound APIs +url: 'https://www.3gpp.org/ftp/Specs/archive/29\_series/29.122/' + +security: + +- {} +- oAuth2ClientCredentials: [] + +servers: + +- url: '{apiRoot}/3gpp-group-message-delivery-xmb/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. + +paths: + +/{scsAsId}/services: + +get: + +summary: Read all service resources for a given SCS/AS. +operationId: FetchAllxMBServices +tags: + +- Service Operation + +parameters: + +- name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + +responses: + +'200': + description: OK (successful query of service creation resource) + content: + application/json: + schema: + type: array + items: + \$ref: '#/components/schemas/ServiceCreation' + minItems: 0 + description: The service resource for the SCS/AS in the request URI is returned. +'307': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/307' +'308': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/308' +'400': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/400' +'401': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/401' +'403': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/403' +'404': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/404' +'406': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/406' +'429': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/429' +'500': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/500' +'503': + \$ref: 'TS29122\_CommonData.yaml#/components/responses/503' +default: + \$ref: 'TS29122\_CommonData.yaml#/components/responses/default' + +post: + +summary: Creates a new service creation resource for a given SCS/AS. + +``` + +operationId: CreatexMBSERVICE +tags: + - Service Operation +parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string +requestBody: + description: representation of the service to be created in the SCEF + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceCreation' +responses: + '201': + description: successful creation of a service + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceCreation' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/services/{serviceId}: + get: + summary: Read a service resource for a given SCS/AS and a Service Id. + operationId: FetchIndxMBSERVICE + tags: + - Individual Service Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: serviceId + in: path + description: Service Id + required: true + schema: + type: string + responses: + '200': + description: OK (successful query of service resource) + content: + application/json: + schema: + +``` + +``` + + $ref: '#/components/schemas/ServiceCreation' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Deletes an existing service resource for a given SCS/AS and a service id. + operationId: DeletexMBService + tags: + - Individual Service Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: serviceId + in: path + description: Service Id + required: true + schema: + type: string + responses: + '204': + description: No Content, successful deletion of a service resource + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/services/{serviceId}/delivery-via-mbms: + get: + summary: Read all group message delivery via MBMS resource for a given SCS/AS and a service +id. + operationId: FetchAllGMDViaMBMS + tags: + - Delivery via MBMS Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + +``` + +``` + + schema: + type: string +- name: serviceId + in: path + description: Service Id + required: true + schema: + type: string +responses: + '200': + description: OK (successful query of Delivery via MBMS resource) + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/GMDViaMBMSByxMB' + minItems: 0 + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +post: + summary: Creates a new delivery via MBMS for a given SCS/AS and a service Id. + operationId: CreateGMDViaMBMS + tags: + - Delivery via MBMS Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: serviceId + in: path + description: Service Id + required: true + schema: + type: string + requestBody: + description: representation of the GMD via MBMS by xMB resource to be Created in the SCEF + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByxMB' + callbacks: + gMDByxMBNotification: + '{ $request.body#/notificationDestination }': + post: + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/GMDByxMBNotification' + responses: + '200': + +``` + +``` + + description: OK (The successful acknowledgement of the notification with a body) + content: + application/json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Acknowledgement' + '204': + description: successful notification + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + responses: + '201': + description: successful creation of an GMD via MBMS by xMB resource + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByxMB' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/services/{serviceId}/delivery-via-mbms/{transactionId}: + get: + summary: Read all group message delivery via MBMS resource for a given SCS/AS and a service + Id. + operationId: FetchIndGMDViaMBMS + tags: + - Individual Delivery via MBMS resource Operation + parameters: + - name: scsAsId + +``` + +``` + + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string +- name: serviceId + in: path + description: Service Id + required: true + schema: + type: string +- name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string +responses: + '200': + description: OK (successful query of an Delivery via MBMS resource) + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByxMB' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +put: + summary: Updates an existing delivery via MBMS for a given SCS/AS, a service Id and +transaction Id. + operationId: UpdateIndGMDViaMBMS + tags: + - Individual Delivery via MBMS resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: serviceId + in: path + description: Service Id + required: true + schema: + type: string + - name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string + requestBody: + description: representation of the GMD via MBMS by xMB resource to be udpated in the SCEF + required: true + content: + application/json: + schema: + +``` + +``` + + $ref: '#/components/schemas/GMDViaMBMSByxMB' +responses: + '200': + description: successful update of an individual GMD via MBMS by xMB resource + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByxMB' + '204': + description: > + The group message delivery was modified successfully, and no content is to be sent + in the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Updates an existing delivery via MBMS for a given SCS/AS, a service Id and +transaction Id. + operationId: ModifyIndGMDViaMBMS + tags: + - Individual Delivery via MBMS resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: serviceId + in: path + description: Service Id + required: true + schema: + type: string + - name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string + requestBody: + description: representation of the GMD via MBMS by xMB resource to be udpated in the SCEF + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByxMBPatch' +responses: + '200': + description: successful update of an individual GMD via MBMS by xMB resource + content: + application/json: + schema: + $ref: '#/components/schemas/GMDViaMBMSByxMB' + +``` + +``` +'204': + description: > + The group message delivery was modified successfully, and no content is to be sent + in the response message body. +'307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' +'308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Deletes a delivery via MBMS resource for a given SCS/AS, a service Id and a +transcation Id. + operationId: DeleteIndGMDViaMBMS + tags: + - Individual Delivery via MBMS resource Operation + parameters: + - name: scsAsId + in: path + description: Identifier of SCS/AS + required: true + schema: + type: string + - name: serviceId + in: path + description: Service Id + required: true + schema: + type: string + - name: transactionId + in: path + description: Identifier of transaction + required: true + schema: + type: string + responses: + '204': + description: No Content, successful deletion of an resouce of deliery via MBMS + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: +``` + +``` +$ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + ServiceCreation: + description: Represents an individual xMB Service resource. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + userServiceId: + type: string + description: Identifies the MBMS User Service supplied by the SCEF. + readOnly: true + serviceClass: + type: string + description: The service class that service belongs to supplied by the SCEF. + readOnly: true + serviceLanguages: + type: array + items: + type: string + minItems: 1 + description: List of language of the service content supplied by the SCEF. + readOnly: true + serviceNames: + type: array + items: + type: string + minItems: 1 + description: List of Service Names supplied by the SCEF. + readOnly: true + receiveOnlyMode: + type: boolean + description: > + When set to 'true', the Content Provider indicates that the service is a Receive Only + Mode service. This parameter is supplied by the SCEF. + readOnly: true + serviceAnnouncementMode: + $ref: '#/components/schemas/ServiceAnnouncementMode' + + GMDViaMBMSByxMB: + description: Represents a group message delivery via MBMS by xMB. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + requestTestNotification: + type: boolean + description: > + Set to true by the SCS/AS to request the SCEF to send a test notification as defined + in clause 5.2.5.3. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + mbmsLocArea: + $ref: '#/components/schemas/MbmsLocArea' + messageDeliveryStartTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + messageDeliveryStopTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + groupMessagePayload: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + scefMessageDeliveryIPv4: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv4AddrRo' +``` + +``` + scefMessageDeliveryIPv6: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6AddrRo' + scefMessageDeliveryPort: + $ref: 'TS29122_CommonData.yaml#/components/schemas/PortRo' + required: + - notificationDestination + +GMDBByxMBNotification: + description: Represents a group message delivery notification. + type: object + properties: + transaction: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + deliveryTriggerStatus: + type: boolean + description: > + Indicates whether delivery of group message payload was successful(TRUE) or not (FALSE). + required: + - transaction + - deliveryTriggerStatus + +GMDViaMBMSByxMBPatch: + description: Represents a modification request of a group message delivery via MBMS by xMB. + type: object + properties: + mbmsLocArea: + $ref: '#/components/schemas/MbmsLocArea' + messageDeliveryStartTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + messageDeliveryStopTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + groupMessagePayload: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + +MbmsLocArea: + description: > + Represents a user location area whithin which is sent a group message delivery via MBMS + request. + type: object + properties: + cellId: + type: array + items: + type: string + minItems: 1 + description: > + Indicates a Cell Global Identification of the user which identifies the cell the UE is + registered. + enodeBId: + type: array + items: + type: string + minItems: 1 + description: Indicates an eNodeB in which the UE is currently located. + geographicArea: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea' + minItems: 1 + description: Identifies a geographic area of the user where the UE is located. + mbmsServiceAreaId: + type: array + items: + type: string + minItems: 1 + description: Identifies an MBMS Service Area Identity of the user where the UE is located. + civicAddress: + type: array + items: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress' + minItems: 1 + description: Identifies a civic address of the user where the UE is located. + +ServiceAnnouncementMode: + anyOf: + - type: string +``` + +``` + +enum: + - SACH + - CONTENT_PROVIDER +- type: string +description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Represents the service announcement mode. + Possible values are: + - SACH: BM-SC performs the service announcement for the current service using the + SACH channel. + - CONTENT_PROVIDER: BM-SC provides the necessary service access information used by + the Content Provider to create the service announcement information. +readOnly: true + +``` + +## A.9 ReportingNetworkStatus API + +openapi: 3.0.0 + +``` + +info: + title: 3gpp-network-status-reporting + version: 1.3.0-alpha.1 + description: | + API for reporting network status. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.122 V18.1.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' + +security: + - {} + - oAuth2ClientCredentials: [] + +servers: + - url: '{apiRoot}/3gpp-net-stat-report/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. + +paths: + /{scsAsId}/subscriptions: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ScsAsId' + get: + summary: Read all network status reporting subscription resources for a given SCS/AS. + operationId: FetchAllNwStatusReportSubscriptions + tags: + - Network Status Reporting Subscriptions + responses: + '200': + description: The requested information was returned successfully. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/NetworkStatusReportingSubscription' + minItems: 0 + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + +``` + +``` + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +post: + summary: Create a new network status reporting subscription resource. + operationId: CreateNwStatusReportSubscription + tags: + - Network Status Reporting Subscriptions + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/NetworkStatusReportingSubscription' + callbacks: + notificationDestination: + '{request.body#/notificationDestination}': + post: + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/NetworkStatusReportingNotification' + responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +responses: + '201': + description: > + The subscription was created successfully. The URI of the created resource shall be + returned in the "Location" HTTP header. + content: + application/json: + schema: + $ref: '#/components/schemas/NetworkStatusReportingSubscription' + headers: + Location: + description: 'Contains the URI of the newly created resource' +``` + +``` + + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/subscriptions/{subscriptionId}: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ScsAsId' + - name: subscriptionId + in: path + description: Identifier of the subscription resource of type string + required: true + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ResourceId' + get: + summary: Read an active network status reporting subscription resource. + operationId: FetchIndNwStatusReportSubscription + tags: + - Individual Network Status Reporting subscription + responses: + '200': + description: The requested information was returned successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/NetworkStatusReportingSubscription' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + put: + summary: Modify an existing subscription resource to update a subscription. + operationId: UpdateIndNwStatusReportSubscription + tags: + +``` + +``` + +- Individual Network Status Reporting subscription +requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/NetworkStatusReportingSubscription' +responses: + '200': + description: The subscription was updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/NetworkStatusReportingSubscription' + '204': + description: No Content. The subscription was updated successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +patch: + summary: Modify an existing Individual Network Status Reporting Subscription resource. + operationId: ModifyIndNwStatusReportSubscription + tags: + - Individual Network Status Reporting Subscription + requestBody: + description: > + Contains the parameters to modify an existing Individual Network Status Reporting + Subscription resource. + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/NetStatusRepSubsPatch' + responses: + '200': + description: > + OK. The modification of the Individual Network Status Reporting Subscription resource + was successfull. The SCEF shall return an updated representation of the resource within + the NetworkStatusReportingSubscription data structure in the response message body. + content: + application/json: + schema: + $ref: '#/components/schemas/NetworkStatusReportingSubscription' + '204': + description: > + No Content. The modification of the Individual Network Status Reporting Subscription + resource was successfull and no content is to be sent in the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + +``` + +``` + + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + summary: Delete an existing continuous network status reporting subscription resource. + operationId: DeleteIndNwStatusReportSubscription + tags: + - Individual Network Status Reporting subscription + responses: + '204': + description: The subscription was updated successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + NetworkStatusReportingSubscription: + description: Represents a subscription to network status information reporting. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + requestTestNotification: + type: boolean + description: > + Set to true by the SCS/AS to request the SCEF to send a test notification as defined in + clause 5.2.5.3. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + locationArea: + $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea' + timeDuration: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + +``` + +``` +thresholdValues: + type: array + items: + $ref: '#/components/schemas/CongestionValue' + minItems: 1 + description: > + Identifies a list of congestion level(s) with exact value that the SCS/AS requests + to be informed of when reached. +thresholdTypes: + type: array + items: + $ref: '#/components/schemas/CongestionType' + minItems: 1 + description: Identifies a list of congestion level(s) with abstracted value that the +SCS/AS requests to be informed of when reached. +required: + - notificationDestination + - locationArea +not: + required: [thresholdValues, thresholdTypes] + +NetStatusRepSubsPatch: + description: > + Represents the parameters to request the modification of network status reporting + subscription. + type: object + properties: + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + locationArea: + $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea' + timeDuration: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTimeRm' + thresholdValues: + type: array + items: + $ref: '#/components/schemas/CongestionValue' + minItems: 1 + thresholdTypes: + type: array + items: + $ref: '#/components/schemas/CongestionType' + minItems: 1 + not: + required: [thresholdValues, thresholdTypes] + +NetworkStatusReportingNotification: + description: Represents a network status reporting notification. + type: object + properties: + subscription: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + nsiValue: + $ref: '#/components/schemas/CongestionValue' + nsiType: + $ref: '#/components/schemas/CongestionType' + required: + - subscription + not: + required: [nsiValue, nsiType] + +CongestionValue: + type: integer + minimum: 0 + maximum: 31 + description: > + Unsigned integer with valid values between 0 and 31. The value 0 indicates that there is no + congestion. The value 1 is the lowest congestion level and value 31 is the highest + congestion level. + +CongestionType: + anyOf: + - type: string + enum: + - HIGH + - MEDIUM + - LOW + - type: string +``` + +``` + +description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Represents abstracted values for congestion status. + Possible values are: + - HIGH: The congestion status is high. + - MEDIUM: The congestion status is medium. + - LOW: The congestion status is low. + +``` + +## A.10 CpProvisioning API + +openapi: 3.0.0 + +``` + +info: + title: 3gpp-cp-parameter-provisioning + version: 1.3.0-alpha.4 + description: | + API for provisioning communication pattern parameters. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +``` + +``` + +externalDocs: + description: 3GPP TS 29.122 V18.4.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' + +``` + +``` + +security: + - {} + - oAuth2ClientCredentials: [] + +``` + +``` + +servers: + - url: '{apiRoot}/3gpp-cp-parameter-provisioning/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. + +``` + +``` + +paths: + /{scsAsId}/subscriptions: + get: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + summary: Read all active CP parameter provisioning subscription resources for a given SCS/AS. + operationId: FetchAllCPProvisioningSubscriptions + tags: + - CP provisioning Subscriptions + responses: + '200': + description: OK. The subscription information related to the request URI is returned. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/CpInfo' + minItems: 0 + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + +``` + +``` +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +post: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + summary: Create a new subscription resource of provisioning CP parameter set(s). + operationId: CreateCPProvisioningSubscription + tags: + - CP provisioning Subscriptions + requestBody: + description: > + Create new subscriptions for a given SCS/AS and the provisioning CP parameter sets. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/CpInfo' + responses: + '201': + description: > + Created. The subscription was created successfully. The SCEF shall return the created + subscription in the response content. + content: + application/json: + schema: + $ref: '#/components/schemas/CpInfo' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: > + The CP parameters for all sets were not created successfully. CpReport may be included + with detailed information. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/CpReport' + minItems: 1 + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/subscriptions/{subscriptionId}: +``` + +``` +get: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Subscription ID + required: true + schema: + type: string + summary: Read a CP parameter provisioning subscription resource. + operationId: FetchIndCPProvisioningSubscription + tags: + - Individual CP Provisioning Subscription + responses: + '200': + description: OK. The subscription information related to the request URI is returned. + content: + application/json: + schema: + $ref: '#/components/schemas/CpInfo' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +put: + summary: Modify a CP parameter provisioning subscription resource. + operationId: UpdateIndCPProvisioningSubscription + tags: + - Individual CP Provisioning Subscription + requestBody: + description: Modify a CP parameter provisioning subscription resource. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/CpInfo' + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Subscription ID + required: true + schema: + type: string + responses: + '200': + description: > + OK. The subscription was modified successfully. The SCEF shall return an updated + subscription in the response content. + content: +``` + +``` + + application/json: + schema: + $ref: '#/components/schemas/CpInfo' +'204': + description: > + No Content. The subscription was modified successfully and no content is to be sent + in the response message body. +'307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' +'308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + description: > + The CP parameters for all sets were not updated successfully. CpReport may be included + with detailed information. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/CpReport' + minItems: 1 + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Subscription ID + required: true + schema: + type: string + summary: Delete a CP parameter provisioning subscription resource. + operationId: DeleteIndCPProvisioningSubscription + tags: + - Individual CP Provisioning Subscription + responses: + '204': + description: > + No Content. The subscription was deleted successfully. The content shall be empty. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/subscriptions/{subscriptionId}/cpSets/{setId}: + get: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Subscription ID + required: true + schema: + type: string + - name: setId + in: path + description: Identifier of the CP parameter set + required: true + schema: + type: string + summary: Read CP at individual CP set(s) level associated with a CP parameter set Id. + operationId: FetchIndCPSetProvisioning + tags: + - Individual CP set Provisioning + responses: + '200': + description: OK. The subscription information related to the request URI is returned. + content: + application/json: + schema: + $ref: '#/components/schemas/CpParameterSet' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + put: + summary: Update CP at individual CP set(s) level associated with a CP parameter set Id. + operationId: UpdateIndCPSetProvisioning + tags: + - Individual CP set Provisioning + requestBody: + description: Change information for a CP parameter set. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/CpParameterSet' + parameters: + - name: scsAsId + in: path + +``` + +``` + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string +- name: subscriptionId + in: path + description: Subscription ID + required: true + schema: + type: string +- name: setId + in: path + description: Identifier of the CP parameter set + required: true + schema: + type: string +responses: + '200': + description: > + OK. The CP parameter set resource was modified successfully. The SCEF shall return an + updated CP parameter set resource in the response content. + content: + application/json: + schema: + $ref: '#/components/schemas/CpParameterSet' + '204': + description: > + No Content. The CP parameter set resource was modified successfully and no content + is to be sent in the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '409': + description: The CP parameters for the CP set were not updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/CpReport' + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The CP parameters for the CP set were not updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/CpReport' + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: +``` + +``` + + type: string +- name: subscriptionId + in: path + description: Subscription ID + required: true + schema: + type: string +- name: setId + in: path + description: Identifier of the CP parameter set + required: true + schema: + type: string +summary: Delete CP at individual CP set(s) level associated with a CP parameter set Id. +operationId: DeleteIndCPSetProvisioning +tags: +- Individual CP set Provisioning +responses: + '204': + description: > + No Content. The subscription was deleted successfully. The content shall be empty. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + CpInfo: + description: Represents the resources for communication pattern parameter provisioning. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + mtcProviderId: + type: string + description: Identifies the MTC Service Provider and/or MTC Application. + dnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + cpParameterSets: + type: object + additionalProperties: + $ref: '#/components/schemas/CpParameterSet' + minProperties: 1 + description: > + Identifies a set of CP parameter information that may be part of this CpInfo structure. + +``` + +``` + + Any string value can be used as a key of the map. + cpReports: + type: object + additionalProperties: + $ref: '#/components/schemas/CpReport' + minProperties: 1 + description: > + Supplied by the SCEF and contains the CP set identifiers for which CP parameter(s) are + not added or modified successfully. The failure reason is also included. Each element + provides the related information for one or more CP set identifier(s) and is identified + in the map via the failure identifier as key. + readOnly: true + snssai: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai' + ueIpAddress: + $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddress' + ueMacAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' + required: + - cpParameterSets + oneOf: + - required: [externalId] + - required: [msisdn] + - required: [externalGroupId] + +CpParameterSet: + description: Represents an offered communication pattern parameter set. + type: object + properties: + setId: + type: string + description: > + SCS/AS-chosen correlator provided by the SCS/AS in the request to create a resource + for CP parameter set(s). + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + validityTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + periodicCommunicationIndicator: + $ref: '#/components/schemas/CommunicationIndicator' + communicationDurationTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + periodicTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + scheduledCommunicationTime: + $ref: '#/components/schemas/ScheduledCommunicationTime' + scheduledCommunicationType: + $ref: '#/components/schemas/ScheduledCommunicationType' + stationaryIndication: + $ref: '#/components/schemas/StationaryIndication' + batteryInds: + type: array + items: + $ref: '#/components/schemas/BatteryIndication' + minItems: 1 + trafficProfile: + $ref: '#/components/schemas/TrafficProfile' + expectedUmts: + type: array + items: + $ref: '#/components/schemas/UmtLocationArea5G' + minItems: 1 + description: > + Identifies the UE's expected geographical movement. The attribute is only applicable + in 5G. + expectedUmtDays: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DayOfWeek' + expectedUmtDaysAdd: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DayOfWeek' + minItems: 1 + maxItems: 5 + description: Identifies the additional day(s) of the week. + appExpUeBehvs: + type: array + items: + $ref: '#/components/schemas/AppExpUeBehaviour' + +``` + +``` + + minItems: 1 + description: Contains the Application Specific Expected UE Behaviour parameters. + confidenceLevel: + type: string + pattern: '^[0]\.[0-9]{2}|[1.00]$' + accuracyLevel: + type: string + pattern: '^[0]\.[0-9]{2}|[1.00]$' + required: + - setId + +ScheduledCommunicationTime: + description: Represents an offered scheduled communication time. + type: object + properties: + daysOfWeek: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DayOfWeek' + minItems: 1 + maxItems: 6 + description: > + Identifies the day(s) of the week. If absent, it indicates every day of the week. + timeOfDayStart: + $ref: 'TS29122_CommonData.yaml#/components/schemas/TimeOfDay' + timeOfDayEnd: + $ref: 'TS29122_CommonData.yaml#/components/schemas/TimeOfDay' + +CpReport: + description: > + Represents a CP report indicating the CP set identifier(s) which CP parameter(s) are not + added or modified successfully and the corresponding failure cause(s). + type: object + properties: + setIds: + type: array + items: + type: string + minItems: 1 + description: > + Identifies the CP set identifier(s) which CP parameter(s) are not added or modified + successfully + failureCode: + $ref: '#/components/schemas/CpFailureCode' + required: + - failureCode + +UmtLocationArea5G: + description: Represents the user location area describing the UE moving trajectory. + allOf: + - $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea5G' + - type: object + properties: + umtTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/TimeOfDay' + umtDuration: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + +AppExpUeBehaviour: + description: Contains the Application Specific Expected UE Behaviour parameters. + type: object + properties: + appId: + type: string + description: Indicates the Application Identifier. + expPduSesInacTm: + $ref: 'TS29122_CommonData.yaml#/components/schemas/TimeWindow' + flowDescriptions: + type: array + items: + type: string + minItems: 1 + description: > + Represents a 3-tuple with protocol, server ip and server port for UL/DL application + traffic. The content of the string has the same encoding as the IPFilterRule AVP + value as defined in IETF RFC 6733. + confidenceLevel: + type: string + +``` + +``` + pattern: '^[0]\.[0-9]{2}|[1.00]$' + accuracyLevel: + type: string + pattern: '^[0]\.[0-9]{2}|[1.00]$' + failureCode: + $ref: '#/components/schemas/CpFailureCode' + validityTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' +oneOf: +- required: [appId] +- required: [flowDescriptions] + +CommunicationIndicator: +anyOf: +- type: string + enum: + - PERIODICALLY + - ON_DEMAND +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the type of the communication. + Possible values are: + - PERIODICALLY: Identifies the UE communicates periodically + - ON_DEMAND: Identifies the UE communicates on demand + +StationaryIndication: +anyOf: +- type: string + enum: + - STATIONARY + - MOBILE +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the stationarity of the UE. + Possible values are: + - STATIONARY: Identifies the UE is stationary + - MOBILE: Identifies the UE is mobile + +CpFailureCode: +anyOf: +- type: string + enum: + - MALFUNCTION + - SET_ID_DUPLICATED + - OTHER_REASON + - CONFIDENCE_LEVEL_NOT_SUFFICIENT + - ACCURACY_LEVEL_NOT_SUFFICIENT +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the failure reason of the CP parameter provisioning. + Possible values are + - MALFUNCTION: This value indicates that something functions wrongly in CP parameter + provisioning or the CP parameter provisioning does not function at all. + - SET_ID_DUPLICATED: The received CP set identifier(s) are already provisioned. + - OTHER_REASON: Other reason unspecified. + - CONFIDENCE_LEVEL_NOT_SUFFICIENT: The received confidence level for the expected UE + parameter is not sufficient. + - ACCURACY_LEVEL_NOT_SUFFICIENT: The received accuracy level for the expected UE parameter + is not sufficient. + +BatteryIndication: +anyOf: +- type: string + enum: + - BATTERY_RECHARGE + - BATTERY_REPLACE +``` + +``` + + - BATTERY_NO_RECHARGE + - BATTERY_NO_REPLACE + - NO_BATTERY + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the type of power consumption. + Possible values are: + - BATTERY_RECHARGE: UE powered with rechargeable battery. + - BATTERY_REPLACE: UE powered with replaceable battery. + - BATTERY_NO_RECHARGE: UE powered with no rechargeable battery. + - BATTERY_NO_REPLACE: UE powered with no replaceable battery. + - NO_BATTERY: UE not battery powered. + +TrafficProfile: + anyOf: + - type: string + enum: + - SINGLE_TRANS_UL + - SINGLE_TRANS_DL + - DUAL_TRANS_UL_FIRST + - DUAL_TRANS_DL_FIRST + - MULTI_TRANS + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the type of data transmission. + Possible values are: + - SINGLE_TRANS_UL: Uplink single packet transmission. + - SINGLE_TRANS_DL: Downlink single packet transmission. + - DUAL_TRANS_UL_FIRST: Dual packet transmission, firstly uplink packet transmission with + subsequent downlink packet transmission. + - DUAL_TRANS_DL_FIRST: Dual packet transmission, firstly downlink packet transmission with + subsequent uplink packet transmission. + - MULTI_TRANS: Multiple packet transmission. + +ScheduledCommunicationType: + anyOf: + - type: string + enum: + - DOWNLINK + - UPLINK + - BIDIRECTIONAL + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the type of scheduled communication. + Possible values are: + - DOWNLINK: Downlink only. + - UPLINK: Uplink only. + - BIDIRECTIONAL: Bi-directional. + +``` + +## A.11 PfdManagement API + +openapi: 3.0.0 + +``` + +info: + title: 3gpp-pfd-management + version: 1.3.0-alpha.3 + description: | + API for PFD management. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.122 V18.4.0 T8 reference point for Northbound APIs + +``` + +``` +url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' +``` + +``` +security: +``` + +``` +- {} +- oAuth2ClientCredentials: [] +``` + +``` +servers: +``` + +``` +- url: '{apiRoot}/3gpp-pfd-management/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. +``` + +``` +paths: +``` + +``` +/{scsAsId}/transactions: +``` + +``` +parameters: +``` + +``` +- name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string +``` + +``` +get: +``` + +``` +summary: Read all or queried PFDs for a given SCS/AS. +operationId: FetchAllPFDManagementTransactions +tags: +``` + +``` +- PFD Management Transactions +``` + +``` +parameters: +``` + +``` +- name: external-app-ids + in: query + description: The external application identifier(s) of the requested PFD data. + required: false + schema: + type: array + items: + type: string + minItems: 1 +``` + +``` +responses: +``` + +``` +'200': + description: OK. All or queried transactions related to the request URI are returned. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/PfdManagement' +'307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' +'308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +``` + +``` +post: +``` + +``` +summary: Create PFDs for a given SCS/AS and one or more external Application Identifier(s). +operationId: CreatePFDManagementTransaction +tags: +``` + +``` +- PFD Management Transactions +``` + +``` +requestBody: +``` + +``` +required: true +content: + application/json: + schema: +``` + +``` + + $ref: '#/components/schemas/PfdManagement' + description: Create a new transaction for PFD management. + responses: + '201': + description: > + Created. The transaction was created successfully. The SCEF shall return the created + transaction in the response content. PfdReport may be included to provide detailed + failure information for some applications. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdManagement' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: > + The PFDs for all applications were not created successfully. PfdReport is included with + detailed information. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/PfdReport' + minItems: 1 + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + callbacks: + notificationDestination: + '{request.body#/notificationDestination}': + post: + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/PfdReport' + minItems: 1 + responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + +``` + +``` + + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/transactions/{transactionId}: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + - name: transactionId + in: path + description: Transaction ID + required: true + schema: + type: string + get: + summary: Read all PFDs for a given SCS/AS and a transaction for one or more external + Application Identifier(s). + operationId: FetchIndPFDManagementTransaction + tags: + - Individual PFD Management Transaction + responses: + '200': + description: OK. The transaction information related to the request URI is returned. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdManagement' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + put: + summary: Update PFDs for a given SCS/AS and a transaction for one or more external Application + Identifier(s). + operationId: UpdateIndPFDManagementTransaction + tags: + - Individual PFD Management Transaction + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/PfdManagement' + description: Change information in PFD management transaction. + +``` + +``` +responses: + '200': + description: > + OK. The transaction was modified successfully. The SCEF shall return an updated + transaction in the response content. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdManagement' + '204': + description: No Content. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: > + The PFDs for all applications were not updated successfully. PfdReport is included with + detailed information. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/PfdReport' + minItems: 1 + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Modify an existing PFD Management Transaction resource. + operationId: ModifyIndPFDManagementTransaction + tags: + - Individual PFD Management Transaction + requestBody: + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/PfdManagementPatch' + +responses: + '200': + description: > + OK. The PFD Management Transaction was modified successfully. The SCEF shall return an + updated representation of the resource in the response body. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdManagement' + '204': + description: No Content. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: > + The PFDs for all applications were not modified successfully. A set of PFD Report(s) is + included with detailed information. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/PfdReport' + minItems: 1 + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + summary: Delete PFDs for a given SCS/AS and a transaction for one or more external Application +Identifier(s). + operationId: DeleteIndPFDManagementTransaction + tags: + - Individual PFD Management Transaction + responses: + '204': + description: > + No Content. The transaction was deleted successfully. The content shall be empty. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/transactions/{transactionId}/applications/{appId}: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + - name: transactionId + in: path + description: Transaction ID + required: true + schema: + type: string + - name: appId + in: path + description: Identifier of the application + +``` + +``` + required: true + schema: + type: string +get: + summary: Read PFDs at individual application level. + operationId: FetchIndApplicationPFDManagement + tags: + - Individual Application PFD Management + responses: + '200': + description: OK. The application information related to the request URI is returned. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdData' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +put: + summary: Update PFDs at individual application level. + operationId: UpdateIndApplicationPFDManagement + tags: + - Individual Application PFD Management + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/PfdData' + description: Change information in application. + responses: + '200': + description: > + OK. The application resource was modified successfully. The SCEF shall return an updated + application resource in the response content. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdData' + '204': + description: No Content. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + description: The PFDs for the application were not updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdReport' + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '404': +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '409': + description: The PFDs for the application were not updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdReport' + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The PFDs for the application were not updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdReport' + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +patch: + summary: Update PFDs at individual application level. + operationId: ModifyIndApplicationPFDManagement + tags: + - Individual Application PFD Management + requestBody: + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/PfdData' + description: Change information in PFD management transaction. + responses: + '200': + description: > + OK. The transaction was modified successfully. The SCEF shall return an updated + transaction in the response content. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdData' + '204': + description: No Content + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + description: The PFDs for the application were not updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdReport' + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '409': + description: The PFDs for the application were not updated successfully. + content: + application/json: + schema: + +``` + +``` + + $ref: '#/components/schemas/PfdReport' + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The PFDs for the application were not updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/PfdReport' + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + summary: Delete PFDs at individual application level. + operationId: DeleteIndApplicationPFDManagement + tags: + - Individual Application PFD Management + responses: + '204': + description: > + No Content. The application was deleted successfully. The content shall be empty. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + PfdManagement: + description: Represents a PFD management resource for a PFD management request. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + pfdDatas: + type: object + additionalProperties: + $ref: '#/components/schemas/PfdData' + minProperties: 1 + +``` + +``` + +description: > + Each element uniquely identifies the PFDs for an external application identifier. + Each element is identified in the map via an external application identifier as key. + The response shall include successfully provisioned PFD data of application(s). +pfdReports: + type: object + additionalProperties: + $ref: '#/components/schemas/PfdReport' + minProperties: 1 + description: > + Supplied by the SCEF and contains the external application identifiers for which PFD(s) + are not added or modified successfully. The failure reason is also included. + Each element provides the related information for one or more external application + identifier(s) and is identified in the map via the failure identifier as key. + readOnly: true + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + requestTestNotification: + type: boolean + description: > + Set to true by the SCS/AS to request the SCEF to send a test notification as defined + in clause 5.2.5.3. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + required: + - pfdDatas + +PfdData: + description: > + Represents a PFD request to add, update or remove PFD(s) for one external application + identifier. + type: object + properties: + externalAppId: + type: string + description: Each element uniquely external application identifier + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + pfdData: + type: object + additionalProperties: + $ref: '#/components/schemas/Pfd' + description: > + Contains the PFDs of the external application identifier. Each PFD is identified in + the map via a key containing the PFD identifier. + allowedDelay: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSecRm' + cachingTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSecRo' + required: + - externalAppId + - pfdData + +Pfd: + description: Represents a PFD for an external Application Identifier. + type: object + properties: + pfdId: + type: string + description: Identifies a PFD of an application identifier. + flowDescriptions: + type: array + items: + type: string + minItems: 1 + description: > + Represents a 3-tuple with protocol, server ip and server port for UL/DL application + traffic. The content of the string has the same encoding as the IPFilterRule AVP + value as defined in IETF RFC 6733. + urls: + type: array + items: + type: string + minItems: 1 + description: > + Indicates a URL or a regular expression which is used to match the significant parts + of the URL. + domainNames: + +``` + +``` + type: array + items: + type: string + minItems: 1 + description: Indicates an FQDN or a regular expression as a domain name matching criteria. + dnProtocol: + $ref: '#/components/schemas/DomainNameProtocol' + required: + - pfdId + +PfdReport: + description: > + Represents a PFD report indicating the external application identifier(s) which PFD(s) + are not added or modified successfully and the corresponding failure cause(s). + type: object + properties: + externalAppIds: + type: array + items: + type: string + minItems: 1 + description: > + Identifies the external application identifier(s) which PFD(s) are not added or + modified successfully + failureCode: + $ref: '#/components/schemas/FailureCode' + cachingTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + locationArea: + $ref: '#/components/schemas/UserPlaneLocationArea' + required: + - externalAppIds + - failureCode + +UserPlaneLocationArea: + description: > + Represents location area(s) of the user plane functions which are unable to enforce the + provisioned PFD(s) successfully. + type: object + properties: + locationArea: + $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea' + locationArea5G: + $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea5G' + dnais: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnai' + minItems: 0 + description: Identifies a list of DNAI which the user plane functions support. + +PfdManagementPatch: + description: > + Represents the parameters to request the modification of a PFD management transaction + resource. + type: object + properties: + pfdDatas: + type: object + additionalProperties: + $ref: '#/components/schemas/PfdData' + minProperties: 1 + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + +FailureCode: + anyOf: + - type: string + enum: + - MALFUNCTION + - RESOURCE_LIMITATION + - SHORT_DELAY + - APP_ID_DUPLICATED + - PARTIAL_FAILURE + - OTHER_REASON + - type: string + description: > + This string provides forward-compatibility with future +``` + +``` + + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Represents the failure reason of the PFD management. +Possible values are: +- MALFUNCTION: This value indicates that something functions wrongly in PFD provisioning + or the PFD provisioning does not function at all. +- RESOURCE_LIMITATION: This value indicates there is resource limitation for PFD storage. +- SHORT_DELAY: This value indicates that the allowed delay is too short and PFD(s) + are not stored. +- APP_ID_DUPLICATED: The received external application identifier(s) are already + provisioned. +- PARTIAL_FAILURE: The PFD(s) are not provisioned to all PCEFs/TDFs/SMFs. +- OTHER_REASON: Other reason unspecified. + +DomainNameProtocol: +anyOf: +- type: string + enum: + - DNS_QNAME + - TLS_SNI + - TLS_SAN + - TSL_SCN +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Represents the type of Domain Name Protocol. +Possible values are: +- DNS_QNAME: Identifies the DNS protocol and the question name in DNS query. +- TLS_SNI: Identifies the Server Name Indication in TLS ClientHello message. +- TLS_SAN: Identifies the Subject Alternative Name in TLS ServerCertificate message. +- TSL_SCN: Identifies the Subject Common Name in TLS ServerCertificate message. + +``` + +## A.12 ECRControl API + +``` + +openapi: 3.0.0 +info: + title: 3gpp-ecr-control + version: 1.2.0 + description: | + API for enhanced coverage restriction control. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. +externalDocs: + description: 3GPP TS 29.122 V17.6.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' +security: +- {} +- oAuth2ClientCredentials: [] +servers: +- url: '{apiRoot}/3gpp-ecr-control/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. +paths: + /query: + post: + summary: Query the status of enhanced coverage restriction for a UE. + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ECRControl' + responses: + '200': + description: The requested information was returned successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/ECRData' + +``` + +``` +'307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' +'308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/configure: + post: + summary: Configure the enhanced coverage restriction for a UE. + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ECRControl' + responses: + '200': + description: The Enhanced Coverage Restriction setting was configured successfully.. + content: + application/json: + schema: + $ref: '#/components/schemas/ECRData' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} +schemas: +``` + +``` + +ECRControl: + description: Represents the parameters to request Enhanced Coverage Restriction control. + type: object + properties: + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + mtcProviderId: + type: string + description: Identifies the MTC Service Provider and/or MTC Application. + scsAsId: + type: string + description: Identifier of the SCS/AS. + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + ecrDataWbs: + type: array + items: + $ref: '#/components/schemas/PlmnEcRestrictionDataWb' + minItems: 0 + restrictedPlmnIds: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/PlmnId' + minItems: 0 + description: Indicates a complete list (and possibly empty) of serving PLMNs where +Enhanced Coverage shall be restricted. This attribute shall not be present for the query custom +operation. + allowedPlmnIds: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/PlmnId' + minItems: 0 + description: Indicates a complete list (and possibly empty) of serving PLMNs where +Enhanced Coverage shall be allowed. This attribute shall not be present for the query custom +operation. + required: + - supportedFeatures + oneOf: + - required: [externalId] + - required: [msisdn] + not: + required: [restrictedPlmnIds, allowedPlmnIds] +ECRData: + description: Represents the current visited PLMN (if any) and the current settings of enhanced +coverage restriction. + type: object + properties: + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + visitedPlmnId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/PlmnId' + ecrDataWbs: + type: array + items: + $ref: '#/components/schemas/PlmnEcRestrictionDataWb' + minItems: 0 + restrictedPlmnIds: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/PlmnId' + minItems: 0 + description: Indicates a complete list (and possibly empty) of serving PLMNs where +Enhanced Coverage shall be restricted. + allowedPlmnIds: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/PlmnId' + minItems: 0 + description: Indicates a complete list (and possibly empty) of serving PLMNs where +Enhanced Coverage shall be allowed. + required: + - supportedFeatures + not: + required: [restrictedPlmnIds, allowedPlmnIds] +PlmnEcRestrictionDataWb: + description: Indicates whether enhanced coverage mode is restricted or not for a PLMN ID. + +``` + +``` + +type: object +properties: + plmnId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/PlmnId' + plmnEcrDataWb: + $ref: 'TS29503_Nudm_SDM.yaml#/components/schemas/EcRestrictionDataWb' +required: +- plmnId + +``` + +## A.13 NpConfiguration API + +``` + +openapi: 3.0.0 +info: + title: 3gpp-network-parameter-configuration + version: 1.2.0 + description: | + API for network parameter configuration. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. +externalDocs: + description: 3GPP TS 29.122 V17.6.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' +security: +- {} +- oAuth2ClientCredentials: [] +servers: +- url: '{apiRoot}/3gpp-network-parameter-configuration/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause of 3GPP TS 29.122. +paths: + /{scsAsId}/configurations: + get: + summary: Read all of the active configurations for the SCS/AS. + operationId: FetchAllNPConfigurations + tags: + - Np Configurations + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + responses: + '200': + description: OK (Successful get all of the active NpConfigurations for the SCS/AS) + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/NpConfiguration' + minItems: 0 + description: Network Parameter configurations + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + +``` + +``` +$ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +post: + summary: Creates a new configuration resource for network parameter configuration. + operationId: CreateNPConfiguration + tags: + - Np Configurations + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + requestBody: + description: new configuration creation + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/NpConfiguration' + callbacks: + notificationDestination: + '{request.body#/notificationDestination}': + post: + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ConfigurationNotification' + responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +responses: + '201': + description: Created (Successful creation of configuration) + content: + application/json: + schema: + $ref: '#/components/schemas/NpConfiguration' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/configurations/{configurationId}: + get: + summary: Read an active configuration for the SCS/AS and the configuration Id. + operationId: FetchIndNPConfiguration + tags: + - Individual Np Configuration + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: configurationId + in: path + description: Identifier of the configuration resource + required: true + schema: + type: string + responses: + '200': + description: OK (Successful get the active configuration) + content: + application/json: + schema: + $ref: '#/components/schemas/NpConfiguration' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + + put: + summary: Updates/replaces an existing configuration resource. + operationId: UpdateIndNPConfiguration + tags: + - Individual Np Configuration + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + +``` + +``` + required: true + schema: + type: string +- name: configurationId + in: path + description: Identifier of the configuration resource + required: true + schema: + type: string +requestBody: + description: Parameters to update/replace the existing configuration + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/NpConfiguration' +responses: + '200': + description: OK (Successful update of the existing configuration) + content: + application/json: + schema: + $ref: '#/components/schemas/NpConfiguration' + '204': + description: No Content (Successful update of the configuration) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Updates/replaces an existing configuration resource. + operationId: ModifyIndNPConfiguration + tags: + - Individual Np Configuration + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: configurationId + in: path + description: Identifier of the configuration resource + required: true + schema: + type: string + requestBody: + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/NpConfigurationPatch' + responses: + '200': +``` + +``` + description: OK. The configuration was modified successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/NpConfiguration' + '204': + description: No Content. The configuration was modified successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Deletes an already existing configuration. + operationId: DeleteIndNPConfiguration + tags: + - Individual Np Configuration + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: configurationId + in: path + description: Identifier of the configuration resource + required: true + schema: + type: string + responses: + '204': + description: No Content (Successful deletion of the existing configuration) + '200': + description: OK. (Successful deletion of the existing configuration) + content: + application/json: + schema: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ConfigResult' + minItems: 1 + description: The configuration was terminated successfully, the configuration +failure information for group members shall be included if received. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +``` + +``` + + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} +schemas: + NpConfiguration: + description: Represents a network parameters configuration. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + mtcProviderId: + type: string + description: Identifies the MTC Service Provider and/or MTC Application. + dnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' + externalId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalId' + msisdn: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Msisdn' + externalGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + maximumLatency: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + maximumResponseTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + suggestedNumberOfDLPackets: + type: integer + minimum: 0 + description: This parameter may be included to identify the number of packets that the +serving gateway shall buffer in case that the UE is not reachable. + groupReportingGuardTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + requestTestNotification: + type: boolean + description: Set to true by the SCS/AS to request the SCEF to send a test notification as +defined in clause 5.2.5.3. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + validityTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + snssai: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai' + ueIpAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr' + ueMacAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' + oneOf: + - required: [externalId] + - required: [msisdn] + - required: [externalGroupId] + NpConfigurationPatch: + description: Represents parameters used to request the modification of a network parameters +configuration resource. + type: object + properties: + maximumLatency: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSecRm' + maximumResponseTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSecRm' + suggestedNumberOfDLPackets: + type: integer + +``` + +``` + + minimum: 0 + description: This parameter may be included to identify the number of packets that the +serving gateway shall buffer in case that the UE is not reachable. + nullable: true + groupReportGuardTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSecRm' + validityTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTimeRm' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + ConfigurationNotification: + description: Represents a configuration result notification. + type: object + properties: + configuration: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + configResults: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ConfigResult' + minItems: 1 + description: The grouping configuration result notification provided by the SCEF. + appliedParam: + $ref: 'TS29122_MonitoringEvent.yaml#/components/schemas/AppliedParameterConfiguration' + required: + - configuration + +``` + +## A.14 AsSessionWithQoS API + +openapi: 3.0.0 + +``` + +info: + title: 3gpp-as-session-with-qos + version: 1.3.0-alpha.4 + description: | + API for setting us an AS session with required QoS. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.122 V18.4.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' + +security: + - {} + - oAuth2ClientCredentials: [] + +servers: + - url: '{apiRoot}/3gpp-as-session-with-qos/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. + +paths: + /{scsAsId}/subscriptions: + get: + summary: Read all or queried active subscriptions for the SCS/AS. + operationId: FetchAllASSessionWithQoSSubscriptions + tags: + - AS Session with Required QoS Subscriptions + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: ip-addrs + in: query + description: The IP address(es) of the requested UE(s). + required: false + content: + application/json: + schema: + type: array + +``` + +``` + + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr' + minItems: 1 +- name: ip-domain + in: query + description: > + The IPv4 address domain identifier. The attribute may only be provided if IPv4 address + is included in the ip-addrs query parameter. + required: false + schema: + type: string +- name: mac-addrs + in: query + description: The MAC address(es) of the requested UE(s). + required: false + schema: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' + minItems: 1 +responses: + '200': + description: OK. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/AsSessionWithQoSSubscription' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +post: + summary: Creates a new subscription resource. + operationId: CreateASessionWithQoSSubscription + tags: + - AS Session with Required QoS Subscriptions + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + requestBody: + description: Request to create a new subscription resource + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/AsSessionWithQoSSubscription' + callbacks: + - notificationDestination: + '{request.body#/notificationDestination}': + post: + requestBody: # contents of the callback message + required: true + content: + +``` + +``` + application/json: + schema: + $ref: '#/components/schemas/UserPlaneNotificationData' + responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +responses: + '201': + description: Created (Successful creation of subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/AsSessionWithQoSSubscription' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + description: Forbidden + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetailsAsSessionWithQoS' + headers: + Retry-After: + description: > + Indicates the time the AF has to wait before making a new request. It can be a + non-negative integer (decimal number) indicating the number of seconds the AF + has to wait before making a new request or an HTTP-date after which the AF can + retry a new request. + schema: + type: string + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +``` + +``` +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{scsAsId}/subscriptions/{subscriptionId}: + get: + summary: Read an active subscriptions for the SCS/AS and the subscription Id. + operationId: FetchIndASSessionWithQoSSubscription + tags: + - Individual AS Session with Required QoS Subscription + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Identifier of the subscription resource + required: true + schema: + type: string + responses: + '200': + description: OK (Successful get the active subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/AsSessionWithQoSSubscription' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + + put: + summary: Updates/replaces an existing subscription resource. + operationId: UpdateIndASSessionWithQoSSubscription + tags: + - Individual AS Session with Required QoS Subscription + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Identifier of the subscription resource + required: true + schema: + type: string + requestBody: + description: Parameters to update/replace the existing subscription + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/AsSessionWithQoSSubscription' + responses: +``` + +``` +'200': + description: OK (Successful update of the subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/AsSessionWithQoSSubscription' +'204': + description: No Content (Successful update of the subscription) +'307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' +'308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + description: Forbidden + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetailsAsSessionWithQoS' + headers: + Retry-After: + description: > + Indicates the time the AF has to wait before making a new request. It can be a + non-negative integer (decimal number) indicating the number of seconds the AF + has to wait before making a new request or an HTTP-date after which the AF can + retry a new request. + schema: + type: string +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Updates/replaces an existing subscription resource. + operationId: ModifyIndASSessionWithQoSSubscription + tags: + - Individual AS Session with Required QoS Subscription + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Identifier of the subscription resource + required: true + schema: + type: string + requestBody: + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/AsSessionWithQoSSubscriptionPatch' + responses: + '200': + description: OK. The subscription was modified successfully. + content: + application/json: + schema: +``` + +``` + + $ref: '#/components/schemas/AsSessionWithQoSSubscription' + '204': + description: No Content. The subscription was modified successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + description: Forbidden + content: + application/problem+json: + schema: + $ref: '#/components/schemas/ProblemDetailsAsSessionWithQoS' + headers: + Retry-After: + description: > + Indicates the time the AF has to wait before making a new request. It can be a + non-negative integer (decimal number) indicating the number of seconds the AF + has to wait before making a new request or an HTTP-date after which the AF can + retry a new request. + schema: + type: string + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Deletes an already existing subscription. + operationId: DeleteIndASSessionWithQoSSubscription + tags: + - Individual AS Session with Required QoS Subscription + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Identifier of the subscription resource + required: true + schema: + type: string + responses: + '204': + description: No Content (Successful deletion of the existing subscription) + '200': + description: OK (Successful deletion of the existing subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/UserPlaneNotificationData' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + +``` + +``` + +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + AsSessionWithQoSSubscription: + description: Represents an individual AS session with required QoS subscription resource. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + dnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' + snssai: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + extAppId: + type: string + description: Identifies the external Application Identifier. + extGroupId: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ExternalGroupId' + gsi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' + flowInfo: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/FlowInfo' + minItems: 1 + description: Describe the data flow which requires QoS. + ethFlowInfo: + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EthFlowDescription' + minItems: 1 + description: Identifies Ethernet packet flows. + enEthFlowInfo: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/EthFlowInfo' + minItems: 1 + description: > + Identifies the Ethernet flows which require QoS. Each Ethernet flow consists of a flow + identifier and the corresponding UL and/or DL flows. + listUeAddrs: + type: array + items: + $ref: '#/components/schemas/UeAddInfo' + minItems: 1 + description: Identifies the list of UE address. + multiModalId: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/MultiModalId' + protoDesc: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ProtoDesc' + qosReference: + type: string + description: Identifies a pre-defined QoS information + altQoSReferences: + +``` + +``` + +type: array +items: + type: string +minItems: 1 +description: > + Identifies an ordered list of pre-defined QoS information. The lower the index of the + array for a given entry, the higher the priority. +altQosReqs: + type: array + items: + $ref: + 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AlternativeServiceRequirementsData' + minItems: 1 + description: > + Identifies an ordered list of alternative service requirements that include individual + QoS parameter sets. The lower the index of the array for a given entry, the higher the + priority. +disUeNotif: + description: > + Indicates whether the QoS flow parameters signalling to the UE when the SMF is notified + by the NG-RAN of changes in the fulfilled QoS situation is disabled (true) or + not (false). Default value is false. The fulfilled situation is either the QoS profile + or an Alternative QoS Profile. + type: boolean +ueIpv4Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv4Addr' +ipDomain: + type: string +ueIpv6Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6Addr' +macAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' +usageThreshold: + $ref: 'TS29122_CommonData.yaml#/components/schemas/UsageThreshold' +sponsorInfo: + $ref: 'TS29122_CommonData.yaml#/components/schemas/SponsorInformation' +qosMonInfo: + $ref: '#/components/schemas/QosMonitoringInformation' +pdvMon: + $ref: '#/components/schemas/QosMonitoringInformation' +qosDuration: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' +qosInactInt: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' +directNotifInd: + type: boolean + description: > + Indicates whether the direct event notification is requested (true) or not (false). + Default value is false. +tscQosReq: + $ref: '#/components/schemas/TscQosRequirement' +l4sInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/UplinkDownlinkSupport' +requestTestNotification: + type: boolean + description: > + Set to true by the SCS/AS to request the SCEF to send a test notification as defined + in clause 5.2.5.3. Set to false or omitted otherwise. +websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' +events: + description: > + Represents the list of user plane event(s) to which the SCS/AS requests to subscribe to. + type: array + items: + $ref: '#/components/schemas/UserPlaneEvent' + minItems: 1 +multiModDatFlows: + type: object + additionalProperties: + $ref: '#/components/schemas/AsSessionMediaComponent' + minProperties: 1 + description: > + Contains media component data for a single-modal data flow(s). + The key of the map is the medCompN attribute. +pduSetQos: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSetQosPara' +rTLatencyInd: + +``` + +``` + +type: boolean +description: > + Indicates the service data flow needs to meet the Round-Trip (RT) latency requirement of + the service, when it is included and set to "true". + The default value is "false" if omitted. +periodInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/PeriodicityInfo' +rttMon: + $ref: '#/components/schemas/QosMonitoringInformation' +qosMonDatRate: + $ref: '#/components/schemas/QosMonitoringInformation' +avrgWndw: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindow' +servAuthInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ServAuthInfo' +qosMonConReq: + $ref: '#/components/schemas/QosMonitoringInformation' +listUeConsDtRt: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr' + minItems: 1 + description: > + Identifies the list of UE addresses subject for Consolidated Data Rate monitoring. +required: +- notificationDestination + +AsSessionWithQoSSubscriptionPatch: +description: Represents parameters to modify an AS session with specific QoS subscription. +type: object +properties: + exterAppId: + type: string + description: Identifies the external Application Identifier. + flowInfo: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/FlowInfo' + minItems: 1 + description: Describe the IP data flow which requires QoS. + ethFlowInfo: + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EthFlowDescription' + minItems: 1 + description: Identifies Ethernet packet flows. + enEthFlowInfo: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/EthFlowInfo' + minItems: 1 + description: > + Identifies the Ethernet flows which require QoS. Each Ethernet flow consists of a flow + identifier and the corresponding UL and/or DL flows. + listUeAddrs: + type: array + items: + $ref: '#/components/schemas/UeAddInfo' + minItems: 1 + description: Identifies the list of UE address. + qosReference: + type: string + description: Pre-defined QoS reference + altQoSReferences: + type: array + items: + type: string + minItems: 1 + description: > + Identifies an ordered list of pre-defined QoS information. The lower the index of the + array for a given entry, the higher the priority. + altQoSReqs: + type: array + items: + $ref: + 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AlternativeServiceRequirementsData' + minItems: 1 + description: > + Identifies an ordered list of alternative service requirements that include individual + +``` + +``` + + QoS parameter sets. The lower the index of the array for a given entry, the higher the + priority. +disUeNotif: + type: boolean + description: > + Indicates whether the QoS flow parameters signalling to the UE when the SMF is notified + by the NG-RAN of changes in the fulfilled QoS situation is disabled (true) or + not (false). The fulfilled situation is either the QoS profile or an Alternative QoS + Profile. +usageThreshold: + $ref: 'TS29122_CommonData.yaml#/components/schemas/UsageThresholdRm' +qosMonInfo: + $ref: '#/components/schemas/QosMonitoringInformationRm' +pdvMon: + $ref: '#/components/schemas/QosMonitoringInformationRm' +directNotifInd: + type: boolean + description: > + Indicates whether the direct event notification is requested (true) or not (false). +notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' +tscQosReq: + $ref: '#/components/schemas/TscQosRequirementRm' +l4sInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/UplinkDownlinkSupport' +events: + description: > + Represents the updated list of user plane event(s) to which the SCS/AS requests to + subscribe to. + type: array + items: + $ref: '#/components/schemas/UserPlaneEvent' + minItems: 1 +multiModDatFlows: + type: object + additionalProperties: + $ref: '#/components/schemas/AsSessionMediaComponentRm' + minProperties: 1 + description: > + Contains media component data for a single-modal data flow(s). + The key of the map is the medCompN attribute. +pduSetQos: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSetQosParaRm' +rTLatencyInd: + type: boolean + description: > + Indicates the service data flow needs to meet the Round-Trip (RT) latency requirement of + the service, when it is included and set to "true". + The default value is "false" if omitted. +protoDesc: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ProtoDesc' +periodInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/PeriodicityInfo' +qosDuration: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' +qosInactInt: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' +rttMon: + $ref: '#/components/schemas/QosMonitoringInformationRm' +qosMonDatRate: + $ref: '#/components/schemas/QosMonitoringInformationRm' +avrgWndw: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindowRm' +qosMonConReq: + $ref: '#/components/schemas/QosMonitoringInformationRm' +listUeConsDtRt: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr' + minItems: 1 + description: > + Identifies the list of UE addresses subject for Consolidated Data Rate monitoring. + +QosMonitoringInformation: + description: Represents QoS monitoring information. + type: object + properties: + reqQosMonParams: + +``` + +``` + + type: array + items: + $ref: 'TS29512_Npcf_SMPolicyControl.yaml#/components/schemas/RequestedQosMonitoringParameter' + minItems: 1 + repFreqs: + type: array + items: + $ref: 'TS29512_Npcf_SMPolicyControl.yaml#/components/schemas/ReportingFrequency' + minItems: 1 + repThreshDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + repThreshUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + repThreshRp: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + conThreshDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + conThreshUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + waitTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' + repPeriod: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' + repThreshDatRateDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + repThreshDatRateUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + consDataRateThrDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + consDataRateThrUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + required: + - reqQosMonParams + - repFreqs + +QosMonitoringInformationRm: + description: > + Represents the same as the QosMonitoringInformation data type but with + the nullable:true property. + type: object + properties: + reqQosMonParams: + type: array + items: + $ref: 'TS29512_Npcf_SMPolicyControl.yaml#/components/schemas/RequestedQosMonitoringParameter' + minItems: 1 + repFreqs: + type: array + items: + $ref: 'TS29512_Npcf_SMPolicyControl.yaml#/components/schemas/ReportingFrequency' + minItems: 1 + repThreshDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UIntegerRm' + repThreshUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UIntegerRm' + repThreshRp: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UIntegerRm' + conThreshDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UIntegerRm' + conThreshUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UIntegerRm' + waitTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + repPeriod: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + repThreshDatRateDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + repThreshDatRateUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + consDataRateThrDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + consDataRateThrUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + +QosMonitoringReport: + description: Represents a QoS monitoring report. + +``` + +``` + +type: object +properties: + ulDelays: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + minItems: 1 + dlDelays: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + minItems: 1 + rtDelays: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + minItems: 1 + pdmf: + type: boolean + description: Represents the packet delay measurement failure indicator. + ulDataRate: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + dlDataRate: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + ulAggrDataRate: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + dlAggrDataRate: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + ulConInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + dlConInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + cimf: + type: boolean + description: > + Represents the congestion information measurement failure indicator. When set to "true", + it indicates that a congestion information failure has occurred. Default value is false + if omitted. + +UserPlaneNotificationData: + description: Represents the parameters to be conveyed in a user plane event(s) notification. + type: object + properties: + transaction: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + eventReports: + type: array + items: + $ref: '#/components/schemas/UserPlaneEventReport' + minItems: 1 + description: Contains the reported event and applicable information + required: + - transaction + - eventReports + +UserPlaneEventReport: + description: Represents an event report for user plane. + type: object + properties: + event: + $ref: '#/components/schemas/UserPlaneEvent' + accumulatedUsage: + $ref: 'TS29122_CommonData.yaml#/components/schemas/AccumulatedUsage' + flowIds: + type: array + items: + type: integer + minItems: 1 + description: > + Identifies the affected flows that were sent during event subscription. It might be + omitted when the reported event applies to all the flows sent during the subscription. + multiModFlows: + type: array + items: + $ref: '#/components/schemas/MultiModalFlows' + minItems: 1 + description: > + Identifies the the flow filters for the single-modal data flows thatwere sent + +``` + +``` + during event subscription. + It may be omitted when the reported event applies to all the + single-modal data flows sent during the subscription. + appliedQosRef: + type: string + description: > + The currently applied QoS reference. Applicable for event QOS_NOT_GUARANTEED or + SUCCESSFUL_RESOURCES_ALLOCATION. + altQosNotSuppInd: + type: boolean + description: > + When present and set to true it indicates that the Alternative QoS profiles are not + supported by the access network. Applicable for event QOS_NOT_GUARANTEED. + plmnId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' + qosMonReports: + type: array + items: + $ref: '#/components/schemas/QosMonitoringReport' + minItems: 1 + description: Contains the QoS Monitoring Reporting information + pdvMonReports: + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/PdvMonitoringReport' + minItems: 1 + description: Contains the PDV Monitoring Reporting information + ratType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' + batOffsetInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/BatOffsetInfo' + rttMonReports: + type: array + items: + $ref: '#/components/schemas/QosMonitoringReport' + minItems: 1 + description: Contains the round trip delay over two SDFs reporting information + qosMonDatRateReps: + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/QosMonitoringReport' + minItems: 1 + description: > + Contains QoS Monitoring for data rate information. It shall be present when the notified + event is "QOS_MONITORING" and data rate measurements are available. + aggrDataRateRpts: + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/QosMonitoringReport' + minItems: 1 + description: > + Contains QoS Monitoring for aggregated data rate information. It shall be present when + the notified event is "QOS_MONITORING" and data rate measurements are available. + qosMonConInfoReps: + type: array + items: + $ref: '#/components/schemas/QosMonitoringReport' + minItems: 1 + description: > + Contains QoS Monitoring for congestion information. It shall be present when the + notified event is "QOS_MONITORING" and congestion measurements are available. + required: + - event + +TscQosRequirement: + description: Represents QoS requirements for time sensitive communication. + type: object + properties: + reqGbrDL: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + reqGbrUL: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + reqMbrDL: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + reqMbrUL: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + maxTscBurstSize: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVol' +``` + +``` + +req5Gsgdelay: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketDelBudget' +reqPer: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketErrRate' +priority: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscPriorityLevel' +tscaiTimeDom: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger' +tscaiInputDl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' +tscaiInputUl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' +capBatAdaptation: + type: boolean + description: > + Indicates the capability for AF to adjust the burst sending time, when it is supported + and set to "true". The default value is "false" if omitted. +TscQosRequirementRm: + description: > + Represents the same as the TscQosRequirement data type but with the nullable:true property. + type: object + properties: + reqGbrDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + reqGbrUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + reqMbrDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + reqMbrUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + maxTscBurstSize: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVolRm' + req5Gsgdelay: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketDelBudgetRm' + reqPer: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketErrRateRm' + priority: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscPriorityLevelRm' + tscaiTimeDom: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UintegerRm' + tscaiInputDl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' + tscaiInputUl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' + capBatAdaptation: + type: boolean + description: > + Indicates the capability for AF to adjust the burst sending time, when it is supported + and set to "true". The default value is "false" if omitted. + nullable: true + +AdditionInfoAsSessionWithQos: + description: Describes additional error information specific for this API. + type: object + properties: + acceptableServInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AcceptableServiceInfo' + +ProblemDetailsAsSessionWithQos: + description: Extends ProblemDetails to also include the acceptable service info. + allOf: + - $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + - $ref: '#/components/schemas/AdditionInfoAsSessionWithQos' + +AsSessionMediaComponent: + description: > + Representmedia component data for a single-modal data flow of a multi-modal service. + type: object + required: + - medCompN + allOf: + - not: + - required: [altSerReqs,altSerReqsData] + - not: + - required: [qosReference,altSerReqsData] + properties: + flowInfos: + type: array + +``` + +``` + + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/FlowInfo' + minItems: 1 + nullable: true + description: > + Contains the IP data flow(s) description for a single-modal data flow. + qosReference: + type: string + disUeNotif: + type: boolean + altSerReqs: + type: array + items: + type: string + minItems: 1 + altSerReqsData: + type: array + items: + $ref: + 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AlternativeServiceRequirementsData' + minItems: 1 + description: > + Contains alternative service requirements that include individual QoS parameter sets. + marBwDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + marBwUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + medCompN: + type: integer + medType: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/MediaType' + mirBwDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + mirBwUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + tsnQos: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TsnQosContainer' + tscaiInputDl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' + tscaiInputUl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' + tscaiTimeDom: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + rTLatencyReq: + type: boolean + description: Round-Trip latency requirement of the service data flow. + pduSetQos: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSetQosPara' + evSubsc: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EventsSubscReqData' + +AsSessionMediaComponentRm: + description: > + Represents the AsSessionMediaComponent data type with nullable information. + type: object + required: + - medCompN + not: + required: [altSerReqs,altSerReqsData] + properties: + flowInfos: + type: array + items: + $ref: 'TS29122_CommonData.yaml#/components/schemas/FlowInfo' + minItems: 1 + nullable: true + description: > + Contains the IP data flow(s) description for a single-modal data flow. + qosReference: + type: string + nullable: true + altSerReqs: + type: array + items: + type: string + minItems: 1 + nullable: true + altSerReqsData: + +``` + +``` + + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AlternativeServiceRequirementsData' + minItems: 1 + description: > + Contains removable alternative service requirements that include individual QoS + parameter sets. + nullable: true + disUeNotif: + type: boolean + nullable: true + marBwDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + marBwUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + medCompN: + type: integer + medType: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/MediaType' + mirBwDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + mirBwUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + tsnQos: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TsnQosContainerRm' + tscaiInputDl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' + tscaiInputUl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' + rTLatencyReq: + type: boolean + description: Round-Trip latency requirement of the service data flow. + pduSetQos: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSetQosPara' + evSubsc: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EventsSubscReqDataRm' + nullable: true + +MultiModalFlows: + description: Represents a flow information within a single-modal data flow. + type: object + properties: + medCompN: + type: integer + description: > + It contains the ordinal number of the single-modal data flow. Identifies the + single-modal data flow. + flowIds: + type: array + items: + type: integer + minItems: 1 + description: > + Identifies the affected flow(s) within the single-modal data flow + (identified by the medCompN attribute). + It may be omitted when all flows are affected. + required: + - medCompN + +UeAddrInfo: + description: Represent the UE address information. + properties: + ueIpAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr' + portNumber: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Port' + +UserPlaneEvent: + anyOf: + - type: string + enum: + - SESSION_TERMINATION + - LOSS_OF_BEARER + - RECOVERY_OF_BEARER + - RELEASE_OF_BEARER + - USAGE_REPORT + - FAILED_RESOURCES_ALLOCATION + +``` + +``` + + - QOS_GUARANTEED + - QOS_NOT_GUARANTEED + - QOS_MONITORING + - SUCCESSFUL_RESOURCES_ALLOCATION + - ACCESS_TYPE_CHANGE + - PLMN_CHG + - L4S_NOT_AVAILABLE + - L4S_AVAILABLE + - BAT_OFFSET_INFO + - RT_DELAY_TWO_QOS_FLOWS + - PACK_DELAY_VAR + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the user plane event. + Possible values are: + - SESSION_TERMINATION: Indicates that Rx session is terminated. + - LOSS_OF_BEARER : Indicates a loss of a bearer. + - RECOVERY_OF_BEARER: Indicates a recovery of a bearer. + - RELEASE_OF_BEARER: Indicates a release of a bearer. + - USAGE_REPORT: Indicates the usage report event. + - FAILED_RESOURCES_ALLOCATION: Indicates the resource allocation is failed. + - QOS_GUARANTEED: The QoS targets of one or more SDFs are guaranteed again. + - QOS_NOT_GUARANTEED: The QoS targets of one or more SDFs are not being guaranteed. + - QOS_MONITORING: Indicates a QoS monitoring event. + - SUCCESSFUL_RESOURCES_ALLOCATION: Indicates the resource allocation is successful. + - ACCESS_TYPE_CHANGE: Indicates an Access type change. + - PLMN_CHG: Indicates a PLMN change. + - L4S_NOT_AVAILABLE: The ECN marking for L4S of one or more SDFs is not available. + - L4S_AVAILABLE: The ECN marking for L4S of one or more SDFs is available again. + - BAT_OFFSET_INFO: Indicates the network provided BAT offset and the optionally adjusted +periodicity. + - RT_DELAY_TWO_QOS_FLOWS: Indicates round-trip delay on UL and DL flows over two QoS flows. + - PACK_DELAY_VAR: Indicates Packet Delay Variation is enabled for the SDF. + +``` + +## A.15 MsisdnLessMoSms API + +``` + +openapi: 3.0.0 +info: + title: 3gpp-msisdn-less-mo-sms + version: 1.2.0 + description: | + API for MSISDN-less Mobile Originated SMS. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. +externalDocs: + description: 3GPP TS 29.122 V17.6.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' +security: + - {} + - oAuth2ClientCredentials: [] +servers: + - url: '{apiRoot}' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. +paths: + /: + post: + summary: Deliver a received MSISDN-less MO SMS from the SCEF to the SCS/AS. + operationId: DeliverMSISDNlessMOSMSNotification + tags: + - MSISDN-less MO SMS Notification + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/MsisdnLessMoSmsNotification' + responses: + '200': + +``` + +``` + + description: Success + content: + application/json: + schema: + $ref: '#/components/schemas/MsisdnLessMoSmsNotificationReply' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} +schemas: + MsisdnLessMoSmsNotification: + description: Represents a MSISDN-less MO SMS notification. + type: object + properties: + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + sms: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Bytes' + externalId: + type: string + description: External identifier has the form username@realm. + applicationPort: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Port' + required: + - supportedFeatures + - sms + - externalId + - applicationPort + MsisdnLessMoSmsNotificationReply: + description: Represents a reply to a MSISDN-less MO SMS notification. + type: object + properties: + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - supportedFeatures + +``` + +## A.16 RacsParameterProvisioning API + +openapi: 3.0.0 + +``` + +info: + title: 3gpp-racs-parameter-provisioning + version: 1.2.0-alpha.2 + +``` + +``` + +description: | + API for provisioning UE radio capability parameters. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.122 V18.4.0 T8 reference point for Northbound APIs + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/' + +security: + - {} + - oAuth2ClientCredentials: [] + +servers: + - url: '{apiRoot}/3gpp-racs-pp/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122. + +paths: + /{scsAsId}/provisionings: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + get: + summary: Read all RACS parameter provisioningings for a given AF. + operationId: FetchAllRACSParameterProvisionings + tags: + - RACS Parameter Provisionings + responses: + '200': + description: OK. The provisioning information related to the request URI is returned. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/RacsProvisioningData' + minItems: 0 + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + post: + summary: Create a new RACS parameter provisioning. + operationId: CreateRACSParameterProvisioning + tags: + - RACS Parameter Provisionings + requestBody: + description: create new provisioningings for a given SCS/AS. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/RacsProvisioningData' + +``` + +``` +responses: + '201': + description: Created. The provisioning was created successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/RacsProvisioningData' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The RACS data for all RACS IDs were not provisioned successfully. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/RacsFailureReport' + minItems: 1 + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{scsAsId}/provisionings/{provisioningId}: + parameters: + - name: scsAsId + in: path + description: Identifier of the SCS/AS as defined in clause 5.2.4 of 3GPP TS 29.122. + required: true + schema: + type: string + - name: provisioningId + in: path + description: Provisioning ID + required: true + schema: + type: string + get: + summary: Read an existing RACS parameter provisioning. + operationId: FetchIndRACSParameterProvisioning + tags: + - Individual RACS Parameter Provisioning + responses: + '200': + description: OK. The provisioning information related to the request URI is returned. + content: + application/json: + schema: + $ref: '#/components/schemas/RacsProvisioningData' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +patch: + summary: Modify some properties in an existing RACS parameter provisioning. + operationId: ModifyIndRACSParameterProvisioning + tags: + - Individual RACS Parameter Provisioning + requestBody: + description: update an existing parameter provisioning. + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/RacsProvisioningDataPatch' + responses: + '200': + description: OK. The provisioning data was updated successfully. The SCEF shall return an + updated provisioning information in the response. + content: + application/json: + schema: + $ref: '#/components/schemas/RacsProvisioningData' + '204': + description: > + The provisioning data was updated successfully, and no content is to be sent in + the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The RACS data for all RACS IDs were not provisioned successfully. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/RacsFailureReport' + minItems: 1 + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +put: + summary: Modify all properties in an existing RACS parameter provisioning. + operationId: UpdateIndRACSParameterProvisioning + +``` + +``` +tags: + - Individual RACS Parameter Provisioning +requestBody: + description: update an existing parameter provisioning. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/RacsProvisioningData' +responses: + '200': + description: > + OK. The provisioning data was updated successfully. The SCEF shall return an updated + provisioning information in the response. + content: + application/json: + schema: + $ref: '#/components/schemas/RacsProvisioningData' + '204': + description: > + The provisioning data was updated successfully, and no content is to be sent in + the response message body. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + description: The RACS data for all RACS IDs were not provisioned successfully. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/RacsFailureReport' + minItems: 1 + application/problem+json: + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Delete a RACS parameter provisioning. + operationId: DeleteIndRACSParameterProvisioning + tags: + - Individual RACS Parameter Provisioning + responses: + '204': + description: > + No Content. The provisioning was terminated successfully. The content shall + be empty. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +``` + +``` + + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + RacsProvisioningData: + description: Represents a UE's radio capability data. + type: object + properties: + self: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Link' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + racsConfigs: + type: object + additionalProperties: + $ref: '#/components/schemas/RacsConfiguration' + minProperties: 1 + description: > + Identifies the configuration related to manufacturer specific UE radio capability. + Each element uniquely identifies an RACS configuration for an RACS ID and is identified + in the map via the RACS ID as key. The response shall include successfully provisioned + RACS data. + racsReports: + type: object + additionalProperties: + $ref: '#/components/schemas/RacsFailureReport' + minProperties: 1 + description: > + Supplied by the SCEF. Contains the RACS IDs for which the RACS data are not provisioned + successfully. Any string value can be used as a key of the map. + readOnly: true + required: + - racsConfigs + RacsFailureReport: + description: Represents a radio capability data provisioning failure report. + type: object + properties: + racsIds: + type: array + items: + type: string + minItems: 1 + description: > + Identifies the RACS ID(s) for which the RACS data are not provisioned successfully. + failureCode: + $ref: '#/components/schemas/RacsFailureCode' + required: + - racsIds + - failureCode + + RacsConfiguration: + description: Represents a single UE radio capability configuration data. + type: object + properties: + racsId: + type: string + description: > + The UE radio capability ID provided by the SCS/AS to identify the UE radio capability + data. See 3GPP TS 23.003 for the encoding. + racsParamEps: + type: string + +``` + +``` + + description: The UE radio capability data in EPS. + racsParam5Gs: + type: string + description: The UE radio capability data in 5GS. + imeiTacs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/TypeAllocationCode' + minItems: 1 + description: Related UE model's IMEI-TAC values. + anyOf: + - required: [racsParamEps] + - required: [racsParam5Gs] + required: + - racsId + - imeiTacs + +RacsProvisioningDataPatch: + description: > + Represents parameters to request the modification of a UE's radio capability data. + type: object + properties: + racsConfigs: + type: object + additionalProperties: + $ref: '#/components/schemas/RacsConfigurationRm' + minProperties: 1 + description: > + Identifies the configuration related to manufacturer specific UE radio capability. + Each element uniquely identifies an RACS configuration for an RACS ID and is identified + in the map via the RACS ID as key. + +RacsConfigurationRm: + description: > + Represents the same as the RacsConfiguration data type but with the nullable:true property. + type: object + properties: + racsParamEps: + type: string + description: The UE radio capability data in EPS. + nullable: true + racsParam5Gs: + type: string + description: The UE radio capability data in 5GS. + nullable: true + imeiTacs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/TypeAllocationCode' + minItems: 1 + description: Related UE model's IMEI-TAC values. + nullable: true + +RacsFailureCode: + anyOf: + - type: string + enum: + - MALFUNCTION + - RESOURCE_LIMITATION + - RACS_ID_DUPLICATED + - OTHER_REASON + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Represents the failure result of UE radio capability provisioning. + Possible values are: + - MALFUNCTION: This value indicates that something functions wrongly in RACS provisioning or + the RACS provisioning does not function at all. + - RESOURCE_LIMITATION: This value indicates there is resource limitation for RACS data + storage. + - RACS_ID_DUPLICATED: The received RACS identifier(s) are already provisioned. + - OTHER_REASON: Other reason unspecified. + +``` + +--- + +## Annex B (informative): TS Skeleton Template + +A TS Skeleton Template to be used as a starting point of drafting a 3GPP NBI (i.e. northbound and/or application layer interface) Stage 3 specification is available at the following location: + +[https://www.3gpp.org/ftp/information/All\\_Templates/29.xxx-NBI-Stage3-Template.zip](https://www.3gpp.org/ftp/information/All_Templates/29.xxx-NBI-Stage3-Template.zip) + +--- + +## Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-04 | CT3#89 | | | | | TS skeleton of T8 reference point stage 3. Inclusion of C3-172217, C3-172242, C3-172249 and editorial change from Rapporteur. | 0.0.0 | +| 2017-05 | CT3#90 | | | | | Inclusion of C3-173256, C3-173257, C3-173306, C3-173318, C3-173323, C3-173329 and editorial change from Rapporteur. | 0.1.0 | +| 2017-09 | CT3#91 | | | | | Inclusion of C3-174368, C3-174279, C3-174079, C3-174352, C3-174328, C3-174329, C3-174374, C3-174375, C3-174243, C3-174333, C3-174334, C3-174376, C3-174281, C3-174377, C3-174356, C3-174280, C3-174358, C3-174359, C3-174379, C3-174337, C3-174361, C3-174294, C3-174362, C3-174385, C3-174299 and editorial change from Rapporteur. | 0.2.0 | +| 2017-10 | CT3#92 | | | | | Inclusion of C3-175068, C3-175365, C3-175370, C3-175301, C3-175227, C3-175228, C3-175359, C3-175230, C3-175231, C3-175337, C3-175247, C3-175290, C3-175360 and editorial changes from Rapporteur. | 0.3.0 | +| 2017-12 | CT3#93 | | | | | Inclusion of C3-176329, C3-176218, C3-176356, C3-176375, C3-176357, C3-176334, C3-176378, C3-176067, C3-176335, C3-176073, C3-176337, C3-176380, C3-176390, C3-176362, C3-176339, C3-176340, C3-176233, C3-176089, C3-176267, C3-176383, C3-176365, C3-176366, C3-176272, C3-176273, C3-176274, C3-176391, C3-176368, C3-176369, C3-176385, C3-176279 and editorial changes from Rapporteur. | 0.4.0 | +| 2018-01 | CT3#94 | | | | | Inclusion of C3-180349, C3-180329, C3-180222, C3-180078, C3-180285, C3-180081, C3-180330, C3-180331, C3-180084, C3-180332, C3-180333, C3-180290, C3-180291, C3-180089, C3-180234, C3-180334, C3-180294, C3-180237, C3-180295, C3-180296, C3-180297, C3-180337, C3-180357, C3-180136, C3-180298 and editorial changes from Rapporteur. | 0.5.0 | +| 2018-02 | CT3#95 | | | | | Inclusion of C3-181271, C3-181324, C3-181340, C3-181273, C3-181333, C3-181334, C3-181276, C3-181325 and editorial changes from Rapporteur. | 0.6.0 | +| 2018-03 | CT#79 | CP-181053 | | | | TS sent to plenary for information | 1.0.0 | +| 2018-04 | CT3#96 | | | | | Inclusion of C3-182464, C3-182017, C3-182444, C3-182019, C3-182486, C3-182487, C3-182344, C3-182074, C3-182373, C3-182446, C3-182291, C3-182292, C3-182488, C3-182508, C3-182345, C3-182094, C3-182295, C3-182346, C3-182096, C3-182347, C3-182348, C3-182026, C3-182349, C3-182098, C3-182350, C3-182099, C3-182100, C3-182209, C3-182210, C3-182101, C3-182102, C3-182455, C3-182506, C3-182353, C3-182491, C3-182355, C3-182447, C3-182507, C3-182359, C3-182106, C3-182107, C3-182108, C3-182492, C3-182109, C3-182110, C3-182480, C3-182362, C3-182448, C3-182449, C3-182450, C3-182425, C3-182365, C3-182112, C3-182113, C3-182035, C3-182367, C3-182115, C3-182368, C3-182493, C3-182494, C3-182509, C3-182372 and editorial changes from Rapporteur. | 1.1.0 | +| 2018-05 | CT3#97 | | | | | Inclusion of C3-183028, C3-183029, C3-183030, C3-183474, C3-183051, C3-183475, C3-183476, C3-183054, C3-183055, C3-183056, C3-183478, C3-183479, C3-183336, C3-183337, C3-183832, C3-183340, C3-183609, C3-183611, C3-183612, C3-183833, C3-183614, C3-183834, C3-183883, C3-183616, C3-183343, C3-183088, C3-183617, C3-183618, C3-183741, C3-183625, C3-183626, C3-183122, C3-183123, C3-183124, C3-183635, C3-183792, C3-183634, C3-183619, C3-183786, C3-183082, C3-183083, C3-183084, C3-183622, C3-183835, C3-183624, C3-183627, C3-183075, C3-183737, C3-183836, C3-183419, C3-183630, C3-183066, C3-183347, C3-183861, C3-183788, C3-183862, C3-183789, C3-183637, C3-183837, C3-183863, C3-183639, C3-183864, C3-183067, C3-183068, C3-183069, C3-183641, C3-183059, C3-183071, C3-183606, C3-183779 and editorial changes from Rapporteur. | 1.2.0 | +| 2018-06 | CT#80 | CP-181038 | | | | TS sent to plenary for approval | 2.0.0 | +| 2018-06 | CT#80 | CP-181038 | | | | TS approved by plenary | 15.0.0 | +| 2018-09 | CT#81 | CP-182022 | 0001 | 2 | F | MonitoringEvent API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0002 | 2 | F | ChargeableParty API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0003 | 2 | F | GMDviaMBMSbyMB2 API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0004 | 2 | F | GMDviaMBMSbypxMB API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0005 | 2 | F | ReportingNetworkStatus API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0006 | 2 | F | ECRControl API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0007 | 2 | F | NpConfiguration API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0008 | 2 | F | AsSessionWithQoS API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0009 | | F | Update the Error Handling | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0010 | 2 | F | CpProvisioning OpenAPI schema | 15.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|--------------------------------------------------------------------|--------| +| 2018-09 | CT#81 | CP-182022 | 0011 | 2 | F | Remove the monitoring configuration for a group | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0012 | 1 | F | Resource description in Procedure subclauses | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0013 | 1 | F | Monitoring event API Update | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0014 | 2 | F | BDT API Update | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0015 | | F | Network Parameter Configuration API Update | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0016 | 1 | F | Complete the common openAPI definition | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0017 | 2 | F | Complete the openAPI definition for BDT API | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0018 | | F | NIDD API cleanup | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0019 | 2 | F | Complete the openAPI definition for NIDD API | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0020 | 1 | F | One-time monitoring | 15.1.0 | +| 2018-09 | CT#81 | CP-182178 | 0021 | 3 | F | PATCH data type in ChargeableParty API | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0022 | 1 | F | Procedure correction of PFD management error handling | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0023 | 2 | F | Complete the openAPI definition for PFD API | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0024 | 1 | F | Essential Corrections on TS 29.122 | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0025 | 2 | F | Alignment of error codes with TS 29.500 | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0026 | 2 | F | OpenAPI updates for Device Triggering | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0027 | 1 | F | OpenAPI updates for MSISDN-less Mobile Originated SMS | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0028 | 2 | F | Monitoring event report | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0030 | | F | Add cause in ProblemDetails data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0031 | 1 | F | Remove format keyword for 3GPP defined data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0032 | | F | Correct supported features | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0033 | | F | Correct ConfigResult data type for Monitoring API | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0034 | | F | Correct reachability type in monitoring API | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0035 | | F | Add HSS interaction for NIDD configuration | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0036 | | F | Correct NiddConfigurationPatch data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182179 | 0037 | 2 | F | Removable attribute definition for NIDD configuration | 15.1.0 | +| 2018-09 | CT#81 | CP-182180 | 0038 | 2 | F | Correct MT NIDD procedure | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0039 | 1 | F | Correct group NIDD procedure | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0040 | | F | Device Trigger cleanup | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0041 | | F | Removable attribute definition for PFD management | 15.1.0 | +| 2018-09 | CT#81 | CP-182181 | 0042 | 2 | F | Correct PFD error code | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0043 | | F | Removable attribute definition for NP configuration | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0044 | | F | Correct ConfigResult data type for NP Provisioning API | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0045 | | F | Removable attribute definition for AS required QoS | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0047 | | F | Version numbering update | 15.1.0 | +| 2018-09 | CT#81 | CP-182022 | 0048 | 1 | F | Removal of external docs field | 15.1.0 | +| 2018-09 | CT#81 | CP-182203 | 0049 | | F | paths property in A.2 | 15.1.0 | +| 2018-12 | CT#82 | CP-183116 | 0050 | | F | File naming for Common data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0051 | | F | UE corrections | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0052 | 2 | F | ExternalDocs field | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0053 | 7 | F | Enhancement of LocationArea | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0054 | | F | Data type for Individual TMGI Allocation PATCH operation | 15.2.0 | +| 2018-12 | CT#82 | CP-183127 | 0055 | 2 | F | Correction on Accuracy level | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0056 | 2 | F | Correction on type ConfigResult | 15.2.0 | +| 2018-12 | CT#82 | CP-183128 | 0057 | 5 | F | Monitoring Event Report | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0059 | | F | Correct server definition | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0060 | | F | Correct data type for roamingStatus | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0061 | | F | Correct external identifier and msisdn | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0062 | | F | Correct common data definition | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0063 | 3 | F | Additional data type clarification in openAPI | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0064 | | F | Correct Chargeable Party | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0065 | 2 | F | Correct GMD via MB2 | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0066 | 3 | F | Correct GMD via xMB | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0067 | 5 | F | Correct MT NIDD | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0068 | | F | Correct monitoring API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0069 | | F | Correct CP provisioning | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0070 | | F | Correct Device trigger | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0071 | | F | Correct PFD management | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0072 | | F | Correct report network status | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0073 | | F | Correct NP provisioning | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0074 | | F | Correct MO SMS | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0075 | | F | Correct AS session with QoS | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0076 | 3 | F | Error handling | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0077 | 1 | F | Content type | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0078 | 2 | F | Supporting Ethernet UE in Chargeable Party and AF session with QoS | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0079 | 2 | F | Security adaptation for T8 APIs with CAPIF | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0080 | 1 | F | Remove empty array or map for applicable attributes | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0081 | 3 | F | Presence conditions in yaml file | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0082 | | F | Remove format keyword for TimeOfDay data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0083 | 2 | F | Additional external group ID for number of UE in an area | 15.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------|--------| +| 2018-12 | CT#82 | CP-183116 | 0084 | | F | Correct eDRX cycle length | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0086 | | F | Correct PLMN ID in monitoring API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0088 | | F | Missing ECRData in ECR configuration response | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0089 | | F | Correct GMD via MBMS | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0090 | | F | Missing UE ID in GMD acknowledgement | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0091 | 1 | F | RDS indication in MT NIDD acknowledgement | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0092 | 1 | F | Correct pfdDatas cardinality in PFD management | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0093 | 1 | F | Correct NP configuration yaml definition | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0094 | 6 | F | Different results in CP parameter sets provisioning | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0095 | | F | Correct server URI in Device Trigger | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0096 | | F | Implementation of Binary data | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0097 | | F | Missed GET for resource GMD via MBMS by xMB | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0098 | 1 | F | Notification URI Consistency_ChargableParty | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0099 | 1 | F | Notification URI for GMDviaMBMSbyMB2 API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0100 | 1 | F | Notification URI for GMDviaMBMSbyxMB API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0101 | | F | Resource usage and Notification URI for NIDD API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0102 | 2 | F | Security field | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0103 | 1 | F | Status code support for AsSessionWithQoS API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0104 | 1 | F | Status code support for ChargeableParty API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0105 | 2 | F | Status code support for CpProvisioning API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0106 | 1 | F | Status code support for DeviceTriggering API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0107 | 1 | F | Status code support for ECRControl API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0108 | 1 | F | Status code support for GMDviaMBMSbyMB2 API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0109 | 2 | F | Status code support for GMDviaMBMSbyxMB API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0110 | 3 | F | Status code support for MonitoringEvent API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0111 | 1 | F | Status code support for MsisdnLessMoSms API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0112 | 2 | F | Status code support for NIDD API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0113 | 1 | F | Status code support for NpConfiguration API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0114 | 1 | F | Status code support for PfdManagement API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0115 | 1 | F | Status code support for ReportingNetworkStatus API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0116 | 1 | F | Status code support for ResourceManagementOfBdt API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0117 | 1 | F | Location header | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0118 | 2 | F | API Version Update | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0119 | 1 | F | Link of the created resources for AsSessionWithQoS API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0120 | 1 | F | Link of the created resources for ChargeableParty API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0121 | 1 | F | Link of the created resources for CpProvisioning API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0122 | 1 | F | Link of the created resources for DeviceTriggering API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0123 | 1 | F | Link of the created resources for GMDviaMBMSbyMB2 API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0124 | 1 | F | Link of the created resources for GMDviaMBMSbyxMB API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0125 | 1 | F | Link of the created resources for MonitoringEvent API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0126 | 1 | F | Link of the created resources for NIDD API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0127 | 1 | F | Link of the created resources for NpConfiguration API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0128 | 1 | F | Link of the created resources for PfdManagement API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0129 | 1 | F | Link of the created resources for ReportingNetworkStatus API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0130 | 1 | F | Link of the created resources for ResourceManagementOfBdt API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0132 | | F | API version for MonitoringEvent API | 15.2.0 | +| 2018-12 | CT#82 | CP-183116 | 0133 | | F | Successful code corrections for group message delivery APIs | 15.2.0 | +| 2018-12 | CT#82 | CP-183117 | 0087 | 2 | B | PDN connectivity status monitoring | 16.0.0 | +| 2019-03 | CT#83 | CP-190109 | 0138 | 4 | F | PFD extension | 16.1.0 | +| 2019-03 | CT#83 | CP-190125 | 0140 | | F | Remove SHORT_DELAY_STORED | 16.1.0 | +| 2019-03 | CT#83 | CP-190125 | 0142 | 3 | F | Renew TMGI expiration | 16.1.0 | +| 2019-03 | CT#83 | CP-190125 | 0144 | 2 | F | Corrections related to mandatory features and and MonitoringEvent API errors | 16.1.0 | +| 2019-03 | CT#83 | CP-190125 | 0146 | 1 | F | Correction on MacAddr48 data type reference in the OpenAPI file | 16.1.0 | +| 2019-03 | CT#83 | CP-190159 | 0148 | 2 | F | API Version Update | 16.1.0 | +| 2019-03 | CT#83 | CP-190129 | 0149 | 2 | F | Moving xMB stage 2 to TS 26.348 | 16.1.0 | +| 2019-06 | CT#84 | CP-191073 | 0151 | 1 | A | Correction on 5G location area | 16.2.0 | +| 2019-06 | CT#84 | CP-191092 | 0153 | 1 | A | Failure case when feature required by the monitoring type unsupported | 16.2.0 | +| 2019-06 | CT#84 | CP-191073 | 0155 | 1 | A | 5G feature for Number of UEs in an area notification | 16.2.0 | +| 2019-06 | CT#84 | CP-191210 | 0156 | 4 | B | Notification of Downlink data delivery status and availability after DDN failure notification for multiple Afs | 16.2.0 | +| 2019-06 | CT#84 | CP-191090 | 0157 | 1 | B | Add External Group Id | 16.2.0 | +| 2019-06 | CT#84 | CP-191092 | 0160 | 1 | A | Add openAPI definition for 200 OK in MonitoringEvent API | 16.2.0 | +| 2019-06 | CT#84 | CP-191100 | 0163 | | B | Feature applicability for PDN connectivity status | 16.2.0 | +| 2019-06 | CT#84 | CP-191099 | 0165 | 1 | A | Support of MTC Provider Id | 16.2.0 | +| 2019-06 | CT#84 | CP-191070 | 0166 | 1 | B | Network parameter provisioning support | 16.2.0 | +| 2019-06 | CT#84 | CP-191092 | 0168 | | A | Add openAPI definition for PUT in BDT API | 16.2.0 | +| 2019-06 | CT#84 | CP-191103 | 0171 | 1 | B | PFD management notification | 16.2.0 | +| 2019-06 | CT#84 | CP-191100 | 0173 | 1 | F | Clarify number of UE in an area | 16.2.0 | +| 2019-06 | CT#84 | CP-191070 | 0174 | | F | Update reference to TS 24.250 | 16.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------|--------| +| 2019-06 | CT#84 | CP-191105 | 0175 | 2 | B | BDT Warning Notification Support | 16.2.0 | +| 2019-06 | CT#84 | CP-191092 | 0177 | 1 | A | Precedence and storage of T8 OpenAPI files | 16.2.0 | +| 2019-06 | CT#84 | CP-191092 | 0179 | 2 | A | Copyright Note in YAML file | 16.2.0 | +| 2019-06 | CT#84 | CP-191101 | 0181 | 2 | F | API version Update | 16.2.0 | +| 2019-09 | CT#85 | CP-192139 | 0183 | 1 | A | Correct presence condition in PFD definition | 16.3.0 | +| 2019-09 | CT#85 | CP-192158 | 0184 | 2 | B | Enhancement of Monitoring and Network Parameter Configuration | 16.3.0 | +| 2019-09 | CT#85 | CP-192156 | 0185 | 1 | B | Support a set of MAC addresses in traffic filter | 16.3.0 | +| 2019-09 | CT#85 | CP-192165 | 0187 | 2 | B | Support parameter provisioning in RACS | 16.3.0 | +| 2019-09 | CT#85 | CP-192200 | 0188 | 3 | B | Accurate UE moving trajectory definition | 16.3.0 | +| 2019-09 | CT#85 | CP-192157 | 0189 | 1 | B | Removal of a BDT warning notification request | 16.3.0 | +| 2019-09 | CT#85 | CP-192158 | 0190 | 1 | F | Correction on MSISDN | 16.3.0 | +| 2019-09 | CT#85 | CP-192158 | 0191 | 1 | F | Battery Indication and Traffic Profile for CpProvisioning API | 16.3.0 | +| 2019-09 | CT#85 | CP-192158 | 0192 | 2 | F | Northbound API registration and discovery | 16.3.0 | +| 2019-09 | CT#85 | CP-192158 | 0193 | 1 | F | Corrections on monitoring type | 16.3.0 | +| 2019-09 | CT#85 | CP-192158 | 0194 | 1 | F | Notification of resource allocation failure | 16.3.0 | +| 2019-09 | CT#85 | CP-192197 | 0196 | 3 | B | PFD management partial failure | 16.3.0 | +| 2019-09 | CT#85 | CP-192163 | 0199 | | F | Correction on MSISDN | 16.3.0 | +| 2019-09 | CT#85 | CP-192173 | 0200 | | F | OpenAPI version update for TS 29.122 Rel-16 | 16.3.0 | +| 2019-12 | CT#86 | CP-193216 | 0158 | 9 | B | Update to NIDD APIs for RDS Dynamic Port Management | 16.4.0 | +| 2019-12 | CT#86 | CP-193179 | 0202 | 1 | B | Nnef_APISupportCapability Service | 16.4.0 | +| 2019-12 | CT#86 | CP-193179 | 0203 | 1 | B | Scheduled communication type | 16.4.0 | +| 2019-12 | CT#86 | CP-193198 | 0204 | | F | Correct UMT location area | 16.4.0 | +| 2019-12 | CT#86 | CP-193199 | 0205 | 2 | B | RDS port mismatch in NIDD | 16.4.0 | +| 2019-12 | CT#86 | CP-193199 | 0206 | | F | Reference update: RFC 8259 | 16.4.0 | +| 2019-12 | CT#86 | CP-193206 | 0208 | 4 | A | Correct SCEF aggregation | 16.4.0 | +| 2019-12 | CT#86 | CP-193209 | 0209 | 3 | B | Complete RACS details | 16.4.0 | +| 2019-12 | CT#86 | CP-193199 | 0210 | 1 | B | BatteryIndication data type | 16.4.0 | +| 2019-12 | CT#86 | CP-193220 | 0212 | 3 | B | PFD partial failure notification | 16.4.0 | +| 2019-12 | CT#86 | CP-193206 | 0215 | 1 | A | Correct application port | 16.4.0 | +| 2019-12 | CT#86 | CP-193179 | 0216 | 1 | B | Support API capability change based on API filter | 16.4.0 | +| 2019-12 | CT#86 | CP-193198 | 0217 | 1 | F | openAPI correction for ExNotification | 16.4.0 | +| 2019-12 | CT#86 | CP-193212 | 0218 | 1 | F | Update of API version and TS version in OpenAPI file | 16.4.0 | +| 2020-03 | CT#87e | CP-200198 | 0220 | 1 | B | Update of the DDD status event and availability of DDN failure event | 16.5.0 | +| 2020-03 | CT#87e | CP-200202 | 0222 | 1 | B | QoS Monitoring Report | 16.5.0 | +| 2020-03 | CT#87e | CP-200198 | 0223 | | F | Clarify empty array for API capability change | 16.5.0 | +| 2020-03 | CT#87e | CP-200144 | 0224 | 1 | B | Support PDU session status | 16.5.0 | +| 2020-03 | CT#87e | CP-200208 | 0225 | 1 | B | Support BDT policy candidates in notification | 16.5.0 | +| 2020-03 | CT#87e | CP-200212 | 0226 | 1 | B | Add alternative QoS requirements | 16.5.0 | +| 2020-03 | CT#87e | CP-200219 | 0227 | 1 | B | Adding data type for the BDT Reference ID with "nullable: true" property | 16.5.0 | +| 2020-03 | CT#87e | CP-200209 | 0231 | | F | Enumeration PdnEstablishmentOptionsRm and "nullable" keyword | 16.5.0 | +| 2020-03 | CT#87e | CP-200216 | 0232 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.5.0 | +| 2020-06 | CT#88e | CP-201194 | 0228 | 7 | B | Supporting the Location Services via NEF | 16.6.0 | +| 2020-06 | CT#88e | CP-201243 | 0233 | 1 | F | Addition of IMEI/TAC values for RACS operations | 16.6.0 | +| 2020-06 | CT#88e | CP-201243 | 0234 | 3 | F | Corrections to UE radio capability configuration data | 16.6.0 | +| 2020-06 | CT#88e | CP-201243 | 0235 | 1 | F | Missing bullet in introduction | 16.6.0 | +| 2020-06 | CT#88e | CP-201241 | 0237 | 1 | A | Event of Usage Threshold | 16.6.0 | +| 2020-06 | CT#88e | CP-201235 | 0239 | 3 | F | Periodic reporting by Nnef | 16.6.0 | +| 2020-06 | CT#88e | CP-201210 | 0241 | 1 | F | Correction to the DDD status event | 16.6.0 | +| 2020-06 | CT#88e | CP-201241 | 0243 | | A | Correct GMDViaMBMSByxMB openAPI error | 16.6.0 | +| 2020-06 | CT#88e | CP-201292 | 0245 | 2 | A | Correct NIDD API | 16.6.0 | +| 2020-06 | CT#88e | CP-201213 | 0246 | | F | Correct data type used in QoS monitoring | 16.6.0 | +| 2020-06 | CT#88e | CP-201235 | 0247 | | F | Storage of YAML files | 16.6.0 | +| 2020-06 | CT#88e | CP-201276 | 0248 | 2 | F | Traffic descriptor for xBDT | 16.6.0 | +| 2020-06 | CT#88e | CP-201256 | 0249 | 1 | F | URI of the SCEF northbound APIs | 16.6.0 | +| 2020-06 | CT#88e | CP-201213 | 0250 | 1 | F | Correction to QoS monitoring | 16.6.0 | +| 2020-06 | CT#88e | CP-201243 | 0252 | | F | Avoid using the same data type for PUT and PATCH | 16.6.0 | +| 2020-06 | CT#88e | CP-201250 | 0253 | 1 | B | Complete and fix RDS Port Management | 16.6.0 | +| 2020-06 | CT#88e | CP-201246 | 0254 | 1 | F | Move 5G specific procedure to TS 29.522 | 16.6.0 | +| 2020-06 | CT#88e | CP-201210 | 0255 | 1 | B | Support of Enhanced Coverage Mode control | 16.6.0 | +| 2020-06 | CT#88e | CP-201234 | 0256 | | F | Removal of open issue on external Group Id for ResourceManagementOfBdt API | 16.6.0 | +| 2020-06 | CT#88e | CP-201235 | 0257 | 1 | F | Optionality of ProblemDetails | 16.6.0 | +| 2020-06 | CT#88e | CP-201241 | 0259 | 1 | A | Correction on PfdManagement for PfdManagement API | 16.6.0 | +| 2020-06 | CT#88e | CP-201241 | 0261 | 1 | A | Corrections on APP_ID_DUPLICATED error for PfdManagement API | 16.6.0 | +| 2020-06 | CT#88e | CP-201241 | 0263 | 1 | A | Corrections on SET_ID_DUPLICATED error for CpProvisioning API | 16.6.0 | +| 2020-06 | CT#88e | CP-201235 | 0264 | | F | required field in OpenAPI file | 16.6.0 | +| 2020-06 | CT#88e | CP-201235 | 0265 | 1 | F | Supported headers, Resource Data type and Operation Name | 16.6.0 | +| 2020-06 | CT#88e | CP-201255 | 0267 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.6.0 | +| 2020-09 | CT#89e | CP-202070 | 0271 | | A | Failure response for AsSessionWithQoS API | 16.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-09 | CT#89e | CP-202070 | 0273 | | A | Same IPv4 address for different PDU sessions | 16.7.0 | +| 2020-09 | CT#89e | CP-202077 | 0274 | 1 | F | Remove 5G procedures to TS 29.522 | 16.7.0 | +| 2020-09 | CT#89e | CP-202072 | 0275 | 1 | F | Unique RACS Id | 16.7.0 | +| 2020-09 | CT#89e | CP-202072 | 0276 | | F | Failure response | 16.7.0 | +| 2020-09 | CT#89e | CP-202048 | 0277 | 1 | F | Initial report for multiple PDN connections | 16.7.0 | +| 2020-09 | CT#89e | CP-202070 | 0281 | | A | Use correct code for deleting individual ChargeableParty transaction | 16.7.0 | +| 2020-09 | CT#89e | CP-202021 | 0283 | 2 | A | Removal of an established AS session | 16.7.0 | +| 2020-09 | CT#89e | CP-202072 | 0284 | | F | Usage of PUT and PATCH | 16.7.0 | +| 2020-09 | CT#89e | CP-202070 | 0286 | | A | Corrections to mtcProviderId | 16.7.0 | +| 2020-09 | CT#89e | CP-202086 | 0287 | 1 | F | Updates NpConfiguration with mtcProviderId | 16.7.0 | +| 2020-09 | CT#89e | CP-202084 | 0289 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.7.0 | +| 2020-12 | CT#90e | CP-203139 | 0291 | 1 | F | TS 29.122 Essential Corrections and alignments | 16.8.0 | +| 2020-12 | CT#90e | CP-203079 | 0294 | 2 | F | Essential Corrections to eLCS related monitoring events | 16.8.0 | +| 2020-12 | CT#90e | CP-203132 | 0295 | 1 | F | Correction to Alternative QoS Parameter | 16.8.0 | +| 2020-12 | CT#90e | CP-203139 | 0296 | | F | Storage of YAML files in 3GPP Forge | 16.8.0 | +| 2020-12 | CT#90e | CP-203108 | 0299 | 1 | F | Corrections to MonitoringEventReport | 16.8.0 | +| 2020-12 | CT#90e | CP-203111 | 0300 | 1 | F | Incorrect definition of QosMonitoringInformation | 16.8.0 | +| 2020-12 | CT#90e | CP-203139 | 0301 | 1 | F | Callback URI correction | 16.8.0 | +| 2020-12 | CT#90e | CP-203133 | 0305 | | A | Successful response code for Event Notification | 16.8.0 | +| 2020-12 | CT#90e | CP-203133 | 0307 | 1 | A | Failure response for SCEF northbound APIs | 16.8.0 | +| 2020-12 | CT#90e | CP-203109 | 0308 | | F | Correction on Location Service via NEF | 16.8.0 | +| 2020-12 | CT#90e | CP-203131 | 0310 | 1 | F | Protocol or application errors | 16.8.0 | +| 2020-12 | CT#90e | CP-203133 | 0312 | 1 | A | Solve IP address overlapping for Chargeable Party | 16.8.0 | +| 2020-12 | CT#90e | CP-203100 | 0314 | 2 | A | Correction to NIDD configuration cancellation procedure | 16.8.0 | +| 2020-12 | CT#90e | CP-203133 | 0316 | 1 | A | Correction to device triggering recall procedure | 16.8.0 | +| 2020-12 | CT#90e | CP-203152 | 0322 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.8.0 | +| 2020-12 | CT#90e | CP-203140 | 0290 | | F | DateTime Enhancement | 17.0.0 | +| 2020-12 | CT#90e | CP-203137 | 0293 | 1 | B | Adding Support for Indicating Serialization Format in RDS | 17.0.0 | +| 2020-12 | CT#90e | CP-203153 | 0323 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.0.0 | +| 2020-12 | CT#90e | CP-203149 | 0324 | | F | Failure authorization result of BDT reference Id for ChargeableParty API request | 17.0.0 | +| 2021-03 | CT#91e | CP-210224 | 0325 | | F | Clarification of eLCS feature applicability only to 5G | 17.1.0 | +| 2021-03 | CT#91e | CP-210210 | 0327 | | A | Correct applied QoS reference for QoS not guaranteed | 17.1.0 | +| 2021-03 | CT#91e | CP-210210 | 0331 | 2 | A | Disable UE notifications at changes related to Alternative QoS Profiles | 17.1.0 | +| 2021-03 | CT#91e | CP-210207 | 0333 | 2 | A | Last known location report | 17.1.0 | +| 2021-03 | CT#91e | CP-210207 | 0335 | | A | Default value of accuracy | 17.1.0 | +| 2021-03 | CT#91e | CP-210207 | 0337 | 3 | A | Support Redirection for MonitoringEvent API | 17.1.0 | +| 2021-03 | CT#91e | CP-210219 | 0338 | 1 | F | OpenAPI "description" fields in data type definitions | 17.1.0 | +| 2021-03 | CT#91e | CP-210218 | 0339 | | F | Update of "description" field for map data types | 17.1.0 | +| 2021-03 | CT#91e | CP-210218 | 0340 | | F | OpenAPI reference | 17.1.0 | +| 2021-03 | CT#91e | CP-210189 | 0344 | | A | Correction to AF ID in ECRControl API | 17.1.0 | +| 2021-03 | CT#91e | CP-210189 | 0346 | | A | Correction to mtcProviderId in ECRControl API | 17.1.0 | +| 2021-03 | CT#91e | CP-210221 | 0352 | 1 | F | Removal of invalid tabulations is some attributes description in the MonitoringEvent API OpenAPI file | 17.1.0 | +| 2021-03 | CT#91e | CP-210234 | 0353 | 1 | D | Text style correction | 17.1.0 | +| 2021-03 | CT#91e | CP-210231 | 0355 | 1 | B | Supported features within ProblemDetails | 17.1.0 | +| 2021-03 | CT#91e | CP-210221 | 0356 | 1 | B | Supported features within ProblemDetails | 17.1.0 | +| 2021-03 | CT#91e | CP-210234 | 0359 | 1 | F | Notification URI Correction for AsSessionWithQoS API | 17.1.0 | +| 2021-03 | CT#91e | CP-210207 | 0361 | 1 | A | Support Redirection for NIDD API | 17.1.0 | +| 2021-03 | CT#91e | CP-210207 | 0363 | 1 | A | Support Redirection for ChargeableParty API | 17.1.0 | +| 2021-03 | CT#91e | CP-210207 | 0365 | 1 | A | Support Redirection for CpProvisioning API | 17.1.0 | +| 2021-03 | CT#91e | CP-210207 | 0367 | 1 | A | Support Redirection for DeviceTriggering API | 17.1.0 | +| 2021-03 | CT#91e | CP-210208 | 0369 | 1 | A | Support Redirection for AsSessionWithQoS API | 17.1.0 | +| 2021-03 | CT#91e | CP-210208 | 0371 | 1 | A | Support Redirection for ECRControl API | 17.1.0 | +| 2021-03 | CT#91e | CP-210208 | 0373 | 1 | A | Support Redirection for MsisdnLessMoSms API | 17.1.0 | +| 2021-03 | CT#91e | CP-210208 | 0375 | 1 | A | Support Redirection for NpConfiguration API | 17.1.0 | +| 2021-03 | CT#91e | CP-210208 | 0377 | 1 | A | Support Redirection for PfdManagement API | 17.1.0 | +| 2021-03 | CT#91e | CP-210208 | 0379 | 1 | A | Support Redirection for RacsParameterProvisioning API | 17.1.0 | +| 2021-03 | CT#91e | CP-210208 | 0381 | 1 | A | Support Redirection for ResourceManagementOfBdt API | 17.1.0 | +| 2021-03 | CT#91e | CP-210209 | 0383 | 1 | A | Usage threshold update | 17.1.0 | +| 2021-03 | CT#91e | CP-210248 | 0385 | 2 | A | Updates to Location Failure Cause | 17.1.0 | +| 2021-03 | CT#91e | CP-210212 | 0387 | 1 | A | Resource allocation status | 17.1.0 | +| 2021-03 | CT#91e | CP-210240 | 0389 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.1.0 | +| 2021-06 | CT#92e | CP-211271 | 0341 | 3 | B | Updates to AF Application Identifier in ChargeableParty API | 17.2.0 | +| 2021-06 | CT#92e | CP-211271 | 0342 | 3 | B | Updates to AF Application Identifier in AsSessionWithQoS API | 17.2.0 | +| 2021-06 | CT#92e | CP-211282 | 0347 | 5 | B | Update DNN and S-NSSAI in ChargeableParty API | 17.2.0 | +| 2021-06 | CT#92e | CP-211282 | 0348 | 5 | B | Update DNN and S-NSSAI in AsSessionWithQoS API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0390 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the CommonData API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0392 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the ResourceManagementOfBdt API | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-06 | CT#92e | CP-211238 | 0393 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the ChargeableParty API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0394 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the NIDD API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0395 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the DeviceTriggering API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0396 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the GMDViaMBMS APIs | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0397 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the ReportingNetworkStatus API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0398 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the CpProvisioning API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0399 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the PfdManagement API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0400 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the ECRControl API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0401 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the NpConfiguration API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0402 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the AsSessionWithQoS API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0403 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the MsisdnLessMoSms API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0404 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files of the RacsParameterProvisioning API | 17.2.0 | +| 2021-06 | CT#92e | CP-211238 | 0405 | 1 | F | Removal of invalid unbreakable spaces in some attributes description in the GMDViaMBMS and ReportingNetworkStatus APIs | 17.2.0 | +| 2021-06 | CT#92e | CP-211241 | 0406 | | F | Support redirection for pure 4G SCEF northbound APIs | 17.2.0 | +| 2021-06 | CT#92e | CP-211241 | 0407 | 1 | F | MonitoringEvent API: TAB and missing "description" fields | 17.2.0 | +| 2021-06 | CT#92e | CP-211178 | 0408 | 3 | B | Support Time Sensitive Communication | 17.2.0 | +| 2021-06 | CT#92e | CP-211232 | 0410 | 1 | A | Clarification on Manufacturer Assigned URC | 17.2.0 | +| 2021-06 | CT#92e | CP-211199 | 0412 | 1 | A | Correction to LDR geographic area | 17.2.0 | +| 2021-06 | CT#92e | CP-211227 | 0415 | | A | Resource corrections for SCEF Northbound APIs | 17.2.0 | +| 2021-06 | CT#92e | CP-211228 | 0418 | 1 | A | TWAN level accuracy applicability | 17.2.0 | +| 2021-06 | CT#92e | CP-211119 | 0422 | 1 | F | New Network slice status reporting events for the MonitoringEvent API | 17.2.0 | +| 2021-06 | CT#92e | CP-211241 | 0426 | 1 | F | Respecting 3GPP Forge executing rules | 17.2.0 | +| 2021-06 | CT#92e | CP-211240 | 0427 | 1 | B | Support of 204 No content response code for PFDs update(NB17) | 17.2.0 | +| 2021-06 | CT#92e | CP-211218 | 0428 | 1 | B | Support of Network Exposure to EAS via Local NEF | 17.2.0 | +| 2021-06 | CT#92e | CP-211239 | 0429 | | F | Adding notificationDestination in NpConfigurationPatch data type | 17.2.0 | +| 2021-06 | CT#92e | CP-211240 | 0430 | 1 | F | Supporting 204 No Content during configuration procedure on NpConfiguration API | 17.2.0 | +| 2021-06 | CT#92e | CP-211240 | 0431 | 1 | F | 204 No Content during modification procedure on MonitoringEvent API | 17.2.0 | +| 2021-06 | CT#92e | CP-211240 | 0432 | | F | 204 No Content during modification procedure on AsSessionWithQoS API | 17.2.0 | +| 2021-06 | CT#92e | CP-211185 | 0433 | | F | 204 No Content during modification procedure on ChargeableParty API | 17.2.0 | +| 2021-06 | CT#92e | CP-211240 | 0434 | 1 | F | Update of notification destination for ResourceManagementOfBdt API | 17.2.0 | +| 2021-06 | CT#92e | CP-211240 | 0435 | | F | Update of notification destination for ChargeableParty API | 17.2.0 | +| 2021-06 | CT#92e | CP-211240 | 0436 | | F | Update of notification destination for AsSessionWithQoS API | 17.2.0 | +| 2021-06 | CT#92e | CP-211248 | 0437 | | B | eCAPIF support | 17.2.0 | +| 2021-06 | CT#92e | CP-211269 | 0438 | 1 | B | Update procedures to support HSS initiated GEM partial cancellation | 17.2.0 | +| 2021-06 | CT#92e | CP-211269 | 0439 | 1 | B | Updates to support notification of GEM partial cancellation | 17.2.0 | +| 2021-06 | CT#92e | CP-211240 | 0440 | 1 | F | Updates 204 No Content in NIDD API | 17.2.0 | +| 2021-06 | CT#92e | CP-211240 | 0441 | 1 | F | Updates 204 No Content in RacsParameterProvisioning API | 17.2.0 | +| 2021-06 | CT#92e | CP-211241 | 0444 | 1 | B | Updates notification destination via PATCH operation in NIDD API | 17.2.0 | +| 2021-06 | CT#92e | CP-211228 | 0447 | 1 | A | Format of location information | 17.2.0 | +| 2021-06 | CT#92e | CP-211227 | 0450 | | A | Corrections on PATCH operation for ChargeableParty API | 17.2.0 | +| 2021-06 | CT#92e | CP-211227 | 0453 | | A | Essential corrections to 204 in PATCH in NIDD API | 17.2.0 | +| 2021-06 | CT#92e | CP-211265 | 0454 | | A | Update of OpenAPI version and TS version in externalDocs field | 17.2.0 | +| 2021-09 | CT#93e | CP-212215 | 0455 | 1 | F | Resource URI corrections for PfdManagement and NpConfiguration APIs | 17.3.0 | +| 2021-09 | CT#93e | CP-212224 | 0456 | 1 | B | Clarification to type FlowInfo | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0457 | | F | Correction to Resource URI of ResourceManagementOfBdt API | 17.3.0 | +| 2021-09 | CT#93e | CP-212210 | 0458 | 1 | B | UAV Presence Monitoring | 17.3.0 | +| 2021-09 | CT#93e | CP-212215 | 0459 | 1 | B | Resource allocation status for Chargeable Party | 17.3.0 | +| 2021-09 | CT#93e | CP-212224 | 0460 | | F | Fix AppId feature description | 17.3.0 | +| 2021-09 | CT#93e | CP-212215 | 0463 | 1 | F | Supporting 204 No Content during configuration procedure on DeviceTriggering API | 17.3.0 | +| 2021-09 | CT#93e | CP-212215 | 0464 | 1 | F | Supporting 204 No Content during configuration procedure on ReportingNetworkStatus API | 17.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------|--------| +| 2021-09 | CT#93e | CP-212186 | 0466 | 1 | A | Accuracy attribute correction | 17.3.0 | +| 2021-09 | CT#93e | CP-212213 | 0469 | | A | Correction on Configuration data | 17.3.0 | +| 2021-09 | CT#93e | CP-212204 | 0471 | | A | Correction on User Plane Notification data | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0472 | | F | Corrections on resource root structure and resource URI on MonitoringEvent API | 17.3.0 | +| 2021-09 | CT#93e | CP-212215 | 0473 | 1 | F | Rel-17 Resource URI corrections on AsSessionWithQoS API | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0474 | | F | Resource URI corrections on ChargeableParty API | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0475 | | F | Resource URI correction on DeviceTriggering API | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0476 | | F | Resource URI correction on ReportingNetworkStatus API | 17.3.0 | +| 2021-09 | CT#93e | CP-212215 | 0477 | 1 | F | Add list of data types table to the CommonData API | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0478 | | F | Correction of some remaining invalid characters in OpenAPI specification files | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0479 | | F | Miscellaneous corrections | 17.3.0 | +| 2021-09 | CT#93e | CP-212215 | 0480 | 1 | F | Resource URI correction in the GMD via MBMS APIs | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0481 | | F | Correction to MAC address in MonitoringEvent API | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0482 | | F | Updates 204 No Content in GMDviaMBMSbyMB2 API | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0483 | | F | Updates 204 No Content in GMDviaMBMSbyxMB API | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0484 | | F | Updates notification destination via PATCH operation in GMDviaMBMSbyMB2 API | 17.3.0 | +| 2021-09 | CT#93e | CP-212214 | 0485 | | F | Updates notification destination via PATCH operation in GMDviaMBMSbyxMB API | 17.3.0 | +| 2021-09 | CT#93e | CP-212215 | 0486 | 1 | F | Correct resource URI in NIDD API | 17.3.0 | +| 2021-09 | CT#93e | CP-212215 | 0487 | 1 | F | Correct resource URI in RacsParameterProvisioning API | 17.3.0 | +| 2021-09 | CT#93e | CP-212224 | 0488 | | B | Update DNN and S-NSSAI in MonitoringEvent API | 17.3.0 | +| 2021-09 | CT#93e | CP-212226 | 0489 | 1 | B | Update procedures to support SCSAS initiated GEM partial cancellation | 17.3.0 | +| 2021-09 | CT#93e | CP-212237 | 0490 | 1 | B | Updates to support GEM partial cancellation | 17.3.0 | +| 2021-09 | CT#93e | CP-212187 | 0491 | 1 | B | Support for Multiple QoS Class in deferred location request | 17.3.0 | +| 2021-09 | CT#93e | CP-212215 | 0492 | 2 | B | Supporting Load and Overload Control for northbound APIs | 17.3.0 | +| 2021-09 | CT#93e | CP-212211 | 0494 | | B | Update of TscQosRequirement and TscQosRequirementRm | 17.3.0 | +| 2021-09 | CT#93e | CP-212223 | 0495 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.3.0 | +| 2021-12 | CT#94e | CP-213233 | 0496 | 2 | B | Enhance MonitoringEvent API to support UAV list | 17.4.0 | +| 2021-12 | CT#94e | CP-213247 | 0497 | 1 | F | Correcting "JSON Patch" encoding of changes | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0498 | 1 | B | Updates GET Query in AsSessionWithQoS API | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0499 | 1 | B | Updates GET Query in ChargeableParty API | 17.4.0 | +| 2021-12 | CT#94e | CP-213234 | 0500 | 1 | B | Adding alternative QoS related parameters to AsSessionWithQoS | 17.4.0 | +| 2021-12 | CT#94e | CP-213260 | 0502 | 2 | B | Update the data type definition for MonitoringEvent API | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0503 | 1 | F | Removal of errors from MonitoringEvent OpenAPI file | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0504 | | F | ResourceManagementOfBdt: adding summary, operationId and tags fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0505 | | F | ChargeableParty: adding operationId fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0506 | 1 | F | NIDD: adding summary, operationId and tags fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0507 | 1 | F | DeviceTriggering: adding operationId fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0508 | | F | GMDviaMBMSbyMB2: adding operationId fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0509 | | F | GMDviaMBMSbyxMB: adding operationId fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0510 | | F | ReportingNetworkStatus: adding operationId and tags fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0511 | 1 | F | CpProvisioning: adding summary, operationId and tags fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0512 | | F | PfdManagement: adding summary, operationId and tags fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0513 | | F | NpConfiguration: adding operationId fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0514 | | F | AsSessionWithQoS: adding operationId fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0515 | 1 | F | MsisdnLessMoSms: adding summary, operationId and tags fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0516 | | F | RacsParameterProvisioning: adding summary, operationId and tags fields | 17.4.0 | +| 2021-12 | CT#94e | CP-213247 | 0517 | 1 | B | Update error handling procedures for GEM partial cancellation | 17.4.0 | +| 2021-12 | CT#94e | CP-213212 | 0518 | 1 | F | Resolve editor note for Multiple QoS Class | 17.4.0 | +| 2021-12 | CT#94e | CP-213230 | 0519 | | F | Resolving the subscription to NSAC events related ENs | 17.4.0 | +| 2021-12 | CT#94e | CP-213230 | 0520 | 1 | F | Resolving the reporting type related ENs for NSAC event subscriptions | 17.4.0 | +| 2021-12 | CT#94e | CP-213268 | 0521 | 2 | B | Supporting explicit subscription to user plane events for the AsSessionWithQoS API | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0522 | 1 | B | Updating the support of explicit subscription to bearer events for the ChargeableParty API | 17.4.0 | +| 2021-12 | CT#94e | CP-213235 | 0523 | 1 | F | Supporting 204 No Content during configuration procedure on ResourceManagementOfBdt API | 17.4.0 | +| 2021-12 | CT#94e | CP-213236 | 0524 | | F | Correction to Resource URI of CpProvisioning API | 17.4.0 | +| 2021-12 | CT#94e | CP-213236 | 0525 | 1 | B | Support of 204 No Content during modification procedure on CpProvisioning API | 17.4.0 | +| 2021-12 | CT#94e | CP-213220 | 0526 | | B | Alignment with SA3 supported TLS profiles | 17.4.0 | +| 2021-12 | CT#94e | CP-213223 | 0527 | | B | Clarification of direct notification | 17.4.0 | +| 2021-12 | CT#94e | CP-213230 | 0528 | 1 | B | Supporting network slice status retrieval | 17.4.0 | +| 2021-12 | CT#94e | CP-213236 | 0532 | 1 | B | Updates GET Query in MonitoringEvent API | 17.4.0 | +| 2021-12 | CT#94e | CP-213236 | 0533 | 1 | F | Adding a list of APIs table | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------|--------| +| 2021-12 | CT#94e | CP-213267 | 0534 | 2 | B | Supporting multiple events per subscription on MonitoringEvent API | 17.4.0 | +| 2021-12 | CT#94e | CP-213236 | 0536 | 1 | F | Adding the MonitoringEvent API specific data types tables | 17.4.0 | +| 2021-12 | CT#94e | CP-213236 | 0537 | 1 | F | Adding the DeviceTriggering API specific data types tables | 17.4.0 | +| 2021-12 | CT#94e | CP-213236 | 0538 | 1 | F | Adding the ReportingNetworkStatus API specific data types tables | 17.4.0 | +| 2021-12 | CT#94e | CP-213236 | 0539 | 1 | F | Adding the ECRControl API specific data types tables | 17.4.0 | +| 2021-12 | CT#94e | CP-213236 | 0540 | 1 | F | Adding the NpConfiguration API specific data types tables | 17.4.0 | +| 2021-12 | CT#94e | CP-213246 | 0541 | 1 | F | Update of OpenAPI version and TS version in externalDocs field | 17.4.0 | +| 2022-03 | CT#95e | CP-220203 | 0542 | | F | Correction of mbmsLocArea attribute for GMDViaMBMS APIs | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0543 | | F | Adding the ChargeableParty API specific data types table | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0544 | | F | Adding the PfdManagement API specific data types table | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0545 | 1 | F | Adding the ResourceManagementOfBdt API specific data types table | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0546 | 1 | F | Updating the AsSessionWithQoS API data types table | 17.5.0 | +| 2022-03 | CT#95e | CP-220204 | 0547 | 2 | B | Add the support for PATCH method for the update of a NIDD DL Data transfer resource | 17.5.0 | +| 2022-03 | CT#95e | CP-220204 | 0548 | 3 | B | Add the support of PATCH for the update of a Device Triggering Transaction resource | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0549 | 1 | F | Adding the NIDD API specific data types table | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0550 | | F | Adding the GMDViaMBMS APIs specific data types tables | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0551 | | F | Adding the CpProvisioning API specific data types table | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0552 | | F | Adding the MsisdnLessMoSms API specific data types table | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0553 | | F | Adding the RacsParameterProvisioning API specific data types table | 17.5.0 | +| 2022-03 | CT#95e | CP-220181 | 0554 | 1 | B | Add the support of the civic address type of accuracy | 17.5.0 | +| 2022-03 | CT#95e | CP-220187 | 0555 | 1 | B | Defining the reporting format for NSAC | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0556 | 1 | B | Description of JSON body with "JSON Patch" encoding of changes | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0557 | | F | Updates to GET query supporting in collection level | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0558 | | B | Updates GET query in PfdManagement API | 17.5.0 | +| 2022-03 | CT#95e | CP-220183 | 0559 | 1 | B | Adding alternative QoS related parameter sets to AsSessionWithQoS | 17.5.0 | +| 2022-03 | CT#95e | CP-220203 | 0560 | | F | Correction of the encoding of complex query parameters | 17.5.0 | +| 2022-03 | CT#95e | CP-220199 | 0561 | 1 | B | Support GEM partial addition | 17.5.0 | +| 2022-03 | CT#95e | CP-220185 | 0562 | | F | Feature support handling for Edge Computing | 17.5.0 | +| 2022-03 | CT#95e | CP-220187 | 0564 | 1 | F | One-time reporting | 17.5.0 | +| 2022-03 | CT#95e | CP-220169 | 0567 | | A | Incorrect resource name and attribute name | 17.5.0 | +| 2022-03 | CT#95e | CP-220181 | 0568 | 1 | B | Support AF specific UE ID retrieval in MonitoringEvent API | 17.5.0 | +| 2022-03 | CT#95e | CP-220181 | 0569 | 1 | B | Support AF specific UE ID retrieval in CpProvisioning API | 17.5.0 | +| 2022-03 | CT#95e | CP-220181 | 0570 | 1 | B | Support AF specific UE ID retrieval in NpConfiguration API | 17.5.0 | +| 2022-03 | CT#95e | CP-220204 | 0571 | 1 | B | Support PATCH for the update of a PFD Management Transaction resource | 17.5.0 | +| 2022-03 | CT#95e | CP-220204 | 0572 | 1 | B | Support PATCH for the update of Network Status Reporting Subscription resource | 17.5.0 | +| 2022-03 | CT#95e | CP-220194 | 0573 | | F | Update of info and externalDocs fields | 17.5.0 | +| 2022-06 | CT#96 | CP-221145 | 0575 | 1 | B | Mutual exclusivity of QoS reference and individual QoS parameters | 17.6.0 | +| 2022-06 | CT#96 | CP-221139 | 0576 | 1 | F | Corrections to the AF provided inputs for NSAC | 17.6.0 | +| 2022-06 | CT#96 | CP-221147 | 0577 | 1 | F | Aligning the naming conventions for resource URI components and enumerations with 5GC APIs | 17.6.0 | +| 2022-06 | CT#96 | CP-221147 | 0578 | 1 | F | Resolving the naming convention issues | 17.6.0 | +| 2022-06 | CT#96 | CP-221144 | 0580 | 1 | F | Support of QoS notification control for requested alternative QoS parameters | 17.6.0 | +| 2022-06 | CT#96 | CP-221159 | 0581 | | F | Adding Link data type with "nullable: true" property | 17.6.0 | +| 2022-06 | CT#96 | CP-221159 | 0583 | | B | Missing application errors in the Monitoring API | 17.6.0 | +| 2022-06 | CT#96 | CP-221159 | 0584 | | F | Correction to TscQosRequirement and TscQosRequirementRm | 17.6.0 | +| 2022-06 | CT#96 | CP-221159 | 0585 | | B | Supporting user consent revocation for EDGEAPP on the Nnef_EventExposure API | 17.6.0 | +| 2022-06 | CT#96 | CP-221159 | 0588 | | A | Correcting the DateTime data type name | 17.6.0 | +| 2022-06 | CT#96 | CP-221159 | 0589 | | F | Removing the MonitoringEventSubscriptionPatch data type | 17.6.0 | +| 2022-06 | CT#96 | CP-221159 | 0590 | | F | Defining the default logical relationship between query parameters | 17.6.0 | +| 2022-06 | CT#96 | CP-221159 | 0591 | | F | Update of info and externalDocs fields | 17.6.0 | +| 2022-09 | CT#97e | CP-222097 | 0592 | 1 | F | Updates error handling for AF specific UE Id retrieval in MonitoringEvent API | 17.7.0 | +| 2022-09 | CT#97e | CP-222097 | 0593 | 1 | F | Updates error handling for AF specific UE Id retrieval in CpProvisioning API | 17.7.0 | +| 2022-09 | CT#97e | CP-222097 | 0594 | 1 | F | Updates error handling for AF specific UE Id retrieval in NpConfiguration API | 17.7.0 | +| 2022-09 | CT#97e | CP-222118 | 0595 | 1 | F | The events subscribed by the NEF | 17.7.0 | +| 2022-09 | CT#97e | CP-222113 | 0596 | - | F | Fixing TSC related reused data types in AsSessionWithQoS | 17.7.0 | +| 2022-09 | CT#97e | CP-222118 | 0597 | 1 | F | Application errors handling for the NpConfiguration API | 17.7.0 | +| 2022-09 | CT#97e | CP-222117 | 0598 | - | F | Application errors handling for the RacsParameterProvisioning API | 17.7.0 | +| 2022-09 | CT#97e | CP-222117 | 0599 | 1 | F | Usage of the "tags" field and URI structure | 17.7.0 | +| 2022-09 | CT#97e | CP-222117 | 0600 | - | F | Application errors handling for the NIDD API | 17.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------|--------| +| 2022-09 | CT#97e | CP-222117 | 0601 | 1 | F | Application errors handling for the ReportingNetworkStatus API | 17.7.0 | +| 2022-09 | CT#97e | CP-222117 | 0602 | - | F | Application errors handling for the ECRControl API | 17.7.0 | +| 2022-09 | CT#97e | CP-222117 | 0603 | 1 | F | "Error handling" clause: alignment with other NBI and 5GS APIs | 17.7.0 | +| 2022-09 | CT#97e | CP-222125 | 0605 | 1 | F | Correction of User Plane Event Report | 17.7.0 | +| 2022-09 | CT#97e | CP-222125 | 0607 | 1 | F | Reporting condition for QoS Monitoring Information | 17.7.0 | +| 2022-09 | CT#97e | CP-222090 | 0609 | 1 | A | Corrections on location reporting | 17.7.0 | +| 2022-09 | CT#97e | CP-222117 | 0612 | 1 | F | Boolean types in partial modification | 17.7.0 | +| 2022-09 | CT#97e | CP-222117 | 0613 | 1 | F | Updates on PATCH in MonitoringEvent API | 17.7.0 | +| 2022-09 | CT#97e | CP-222118 | 0614 | 1 | F | Missing description field for enumeration data type in MonitoringEvent API | 17.7.0 | +| 2022-09 | CT#97e | CP-222097 | 0615 | - | F | Correcting the name of the application errors related to user consent revocation support | 17.7.0 | +| 2022-09 | CT#97e | CP-222117 | 0616 | - | F | Application errors handling for the MonitoringEvent API | 17.7.0 | +| 2022-09 | CT#97e | CP-222121 | 0620 | - | F | Update of info and externalDocs fields | 17.7.0 | +| 2022-12 | CT#98e | CP-223184 | 0623 | 1 | F | Corrections on PLMN_CHG event | 17.8.0 | +| 2022-12 | CT#98e | CP-223184 | 0624 | 1 | F | Corrections on ACCESS_TYPE_CHANGE event | 17.8.0 | +| 2022-12 | CT#98e | CP-223188 | 0626 | - | F | Update of info and externalDocs fields | 17.8.0 | +| 2022-12 | CT#98e | CP-223185 | 0622 | 1 | F | ResultReason enumeration definition in the OpenAPI file | 18.0.0 | +| 2022-12 | CT#98e | CP-223189 | 0625 | - | F | Update of info and externalDocs fields | 18.0.0 | +| 2023-03 | CT#99 | CP-230179 | 0628 | 1 | B | Adding PER to AF Session with QoS API | 18.1.0 | +| 2023-03 | CT#99 | CP-230172 | 0629 | 1 | B | Unavailability Period feature for MonitoringEvent API | 18.1.0 | +| 2023-03 | CT#99 | CP-230157 | 0632 | 1 | B | Correction of expectedUmtDays attribute | 18.1.0 | +| 2023-03 | CT#99 | CP-230156 | 0634 | 1 | B | Update Flow Description Information with ToSTC in ChargeableParty API | 18.1.0 | +| 2023-03 | CT#99 | CP-230156 | 0636 | 1 | B | Update Flow Description Information with ToSTC in AsSessionWithQoS API | 18.1.0 | +| 2023-03 | CT#99 | CP-230157 | 0640 | 2 | B | Updates on location reporting | 18.1.0 | +| 2023-03 | CT#99 | CP-230281 | 0641 | 2 | B | Updates to immediate reporting in MonitoringEvent API | 18.1.0 | +| 2023-03 | CT#99 | CP-230156 | 0642 | 1 | F | Correction of the description fields in enumerations | 18.1.0 | +| 2023-03 | CT#99 | CP-230156 | 0643 | - | F | Description fields in enumerations | 18.1.0 | +| 2023-03 | CT#99 | CP-230173 | 0650 | 1 | A | Correction on handling of Packet Delay Failure report Threshold | 18.1.0 | +| 2023-03 | CT#99 | CP-230174 | 0651 | - | F | Generalization of QoS monitoring control description | 18.1.0 | +| 2023-03 | CT#99 | CP-230182 | 0652 | 1 | B | Support of Nnef_AFsessionWithQoS_Create service update for Multi-Modal service XR and Media Services | 18.1.0 | +| 2023-03 | CT#99 | CP-230157 | 0653 | 1 | B | Vendor specific extensions | 18.1.0 | +| 2023-03 | CT#99 | CP-230155 | 0655 | 1 | A | Corrections in MonitoringEvent API | 18.1.0 | +| 2023-03 | CT#99 | CP-230277 | 0656 | 1 | B | Specification of application errors for QoS requests | 18.1.0 | +| 2023-03 | CT#99 | CP-230175 | 0657 | 1 | B | Indication of Alternative Service Requirements not supported | 18.1.0 | +| 2023-03 | CT#99 | CP-230179 | 0658 | 1 | B | Support of BAT window and capability for BAT adaptation | 18.1.0 | +| 2023-03 | CT#99 | CP-230153 | 0659 | - | B | Support of Group Member List Change event | 18.1.0 | +| 2023-03 | CT#99 | CP-230157 | 0660 | 1 | F | Clarification on bearer related events in AsSessionWithQoS API | 18.1.0 | +| 2023-03 | CT#99 | CP-230305 | 0662 | 2 | A | Correction of the procedure when the NEF reject the AF update request | 18.1.0 | +| 2023-03 | CT#99 | CP-230161 | 0664 | - | F | Update of info and externalDocs fields | 18.1.0 | +| 2023-06 | CT#100 | CP-231169 | 0639 | 2 | A | Correction on TLS_SCN in PFD data | 18.2.0 | +| 2023-06 | CT#100 | CP-231139 | 0665 | 1 | F | Corrections on applicability of ToS Traffic Class | 18.2.0 | +| 2023-06 | CT#100 | CP-231130 | 0666 | 2 | B | AsSessionWithQoS enhancements to support multi-modal services | 18.2.0 | +| 2023-06 | CT#100 | CP-231139 | 0669 | 1 | B | Vendor specific extensions – resolve EN | 18.2.0 | +| 2023-06 | CT#100 | CP-231130 | 0671 | 2 | B | Support of ECN marking for L4S | 18.2.0 | +| 2023-06 | CT#100 | CP-231139 | 0672 | 1 | F | Defining a TS skeleton for TSs documenting NBI APIs | 18.2.0 | +| 2023-06 | CT#100 | CP-231143 | 0675 | 1 | F | Support of BAT offset and adjusted periodicity | 18.2.0 | +| 2023-06 | CT#100 | CP-231300 | 0677 | 1 | B | Support of PDU Set QoS Parameters | 18.2.0 | +| 2023-06 | CT#100 | CP-231129 | 0678 | 3 | B | Support of Uplink Downlink transmission coordination to meet RT latency requirement | 18.2.0 | +| 2023-06 | CT#100 | CP-231139 | 0680 | 1 | B | Updates in NpConfiguration API | 18.2.0 | +| 2023-06 | CT#100 | CP-231186 | 0681 | - | F | Clarification on Loss_of_connectivity_notification_5G | 18.2.0 | +| 2023-06 | CT#100 | CP-231126 | 0682 | 1 | B | Enhanced data management for the Monitoring API | 18.2.0 | +| 2023-06 | CT#100 | CP-231164 | 0686 | 1 | A | Corrections in the Notification mechanism description | 18.2.0 | +| 2023-06 | CT#100 | CP-231153 | 0688 | 1 | A | MonitoringEvent resources update for an Error case | 18.2.0 | +| 2023-06 | CT#100 | CP-231262 | 0689 | 1 | B | Adding Monitoring event for application traffic detection. | 18.2.0 | +| 2023-06 | CT#100 | CP-231130 | 0690 | 1 | B | Protocol description parameter support in AS Session with QoS | 18.2.0 | +| 2023-06 | CT#100 | CP-231147 | 0694 | - | A | Removal of unspecified QoS monitoring control options | 18.2.0 | +| 2023-06 | CT#100 | CP-231129 | 0696 | - | B | Support of periodicity measurement and reporting for power saving | 18.2.0 | +| 2023-06 | CT#100 | CP-231128 | 0697 | - | B | Support Application-Specific Expected UE Behaviour parameters | 18.2.0 | +| 2023-06 | CT#100 | CP-231311 | 0699 | 1 | A | Corrections to boolean type in MonitoringEventSubscription | 18.2.0 | +| 2023-06 | CT#100 | CP-231140 | 0700 | 1 | F | Corrections to immediate reporting in MonitoringEvent API | 18.2.0 | +| 2023-06 | CT#100 | CP-231140 | 0701 | 1 | F | Corrections to Location Type and immediate reporting in MonitoringEvent API | 18.2.0 | +| 2023-06 | CT#100 | CP-231313 | 0702 | 1 | B | Updates to BDT on ASP Id | 18.2.0 | +| 2023-06 | CT#100 | CP-231167 | 0705 | - | A | Reporting format for one-time reporting | 18.2.0 | +| 2023-06 | CT#100 | CP-231130 | 0707 | 1 | B | Support of Packet Delay Variation monitoring and reporting | 18.2.0 | +| 2023-06 | CT#100 | CP-231139 | 0711 | - | F | Corrections to the resource update related provisions for the | 18.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------|--------| +| | | | | | | MonitoringEvent API | | +| 2023-06 | CT#100 | CP-231139 | 0712 | | B | Editor Note removal for userLocation attribute | 18.2.0 | +| 2023-06 | CT#100 | CP-231141 | 0715 | | F | Update of info and externalDocs fields | 18.2.0 | +| 2023-09 | CT#101 | CP-232091 | 0721 | 1 | F | Wrong applicability of AsSessionWithQoS error | 18.3.0 | +| 2023-09 | CT#101 | CP-232086 | 0722 | 1 | F | Applicability of new AfSessionWithQoS errors | 18.3.0 | +| 2023-09 | CT#101 | CP-232124 | 0723 | 1 | B | Update application detection event exposure | 18.3.0 | +| 2023-09 | CT#101 | CP-232087 | 0724 | 1 | B | AF QoS Timing info addition | 18.3.0 | +| 2023-09 | CT#101 | CP-232172 | 0725 | 2 | B | AIMLsys service data model update for AsSessionWithQoS | 18.3.0 | +| 2023-09 | CT#101 | CP-232158 | 0727 | 1 | F | Editor note removal for Multimodal id | 18.3.0 | +| 2023-09 | CT#101 | CP-232090 | 0729 | | B | AF request QoS for target UE in AsSessionWithQoS API | 18.3.0 | +| 2023-09 | CT#101 | CP-232109 | 0731 | 1 | B | Reject Location request when area does not overlap with configured "event report allowed area" | 18.3.0 | +| 2023-09 | CT#101 | CP-232113 | 0732 | 1 | B | Network slice admission control notification update for UE with atleast one PDU session/PDN connection | 18.3.0 | +| 2023-09 | CT#101 | CP-232086 | 0735 | | F | Correction in Feature numbering | 18.3.0 | +| 2023-09 | CT#101 | CP-232086 | 0736 | | F | remove useless BdtReferenceIdRm | 18.3.0 | +| 2023-09 | CT#101 | CP-232091 | 0738 | | F | Corrections on the roaming status report | 18.3.0 | +| 2023-09 | CT#101 | CP-232084 | 0739 | 1 | B | Subscription to Round-Trip delay over two service data flows | 18.3.0 | +| 2023-09 | CT#101 | CP-232158 | 0740 | 1 | B | Subscription to data rate monitoring | 18.3.0 | +| 2023-09 | CT#101 | CP-232158 | 0741 | 1 | B | Support of the congestion information measurement and reporting | 18.3.0 | +| 2023-09 | CT#101 | CP-232158 | 0742 | 1 | B | Support of the Packet Delay Variation monitoring | 18.3.0 | +| 2023-09 | CT#101 | CP-232087 | 0745 | 1 | B | Confidence and accuracy levels for UE behaviour parameters | 18.3.0 | +| 2023-09 | CT#101 | CP-232103 | 0746 | 2 | B | Location exposure for Ranging_SL | 18.3.0 | +| 2023-09 | CT#101 | CP-232087 | 0747 | 1 | B | Resolve EN for Application-Specific Expected UE Behaviour parameters | 18.3.0 | +| 2023-09 | CT#101 | CP-232085 | 0748 | | F | Update of info and externalDocs fields | 18.3.0 | +| 2023-12 | CT#102 | CP-233231 | 0691 | 4 | B | Supporting query parameters extensibility | 18.4.0 | +| 2023-12 | CT#102 | CP-233263 | 0718 | 1 | A | Resolving the remaining LOLC related ENs | 18.4.0 | +| 2023-12 | CT#102 | CP-233262 | 0719 | 2 | B | Support of user plane positioning | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0734 | 3 | F | Corrections to MonitoringEventReport | 18.4.0 | +| 2023-12 | CT#102 | CP-233235 | 0749 | | F | Correct the attribute names and add abbreviation | 18.4.0 | +| 2023-12 | CT#102 | CP-233233 | 0750 | 1 | B | Introduction of new features for PDU set handle and RT latency | 18.4.0 | +| 2023-12 | CT#102 | CP-233233 | 0752 | | B | Update Data Rate monitoring | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0753 | | F | Corrections to the monitoringType and addnMonTypes attributes | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0754 | 1 | F | Corrections to the User Consent Revocation Notification definition | 18.4.0 | +| 2023-12 | CT#102 | CP-233234 | 0755 | 3 | B | Support of subscription to flow level events | 18.4.0 | +| 2023-12 | CT#102 | CP-233233 | 0756 | 1 | F | Support of the new feature name EnQoSMon | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0757 | 2 | F | Updating the obsoleted IETF HTTP RFCs | 18.4.0 | +| 2023-12 | CT#102 | CP-233235 | 0760 | 1 | F | associate attributes with corresponding NOTE | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0761 | | B | ProblemDetails RFC 7807 obsoleted by RFC 9457 | 18.4.0 | +| 2023-12 | CT#102 | CP-233268 | 0762 | 1 | B | Update Location exposure for Ranging_SL | 18.4.0 | +| 2023-12 | CT#102 | CP-233257 | 0763 | 1 | F | Corrections in MonitoringEventReport | 18.4.0 | +| 2023-12 | CT#102 | CP-233233 | 0764 | | B | Protocol description - End of burst indication update | 18.4.0 | +| 2023-12 | CT#102 | CP-233208 | 0765 | 2 | B | Feature granularity and definition for MultiModal & PowerSaving | 18.4.0 | +| 2023-12 | CT#102 | CP-233245 | 0766 | 1 | F | Correction on formulating conditions based on feature support | 18.4.0 | +| 2023-12 | CT#102 | CP-233233 | 0771 | | B | Definition of L4S feature | 18.4.0 | +| 2023-12 | CT#102 | CP-233236 | 0772 | 3 | B | Updates to AppExpUeBehaviour Data Type in CpProvisioning API | 18.4.0 | +| 2023-12 | CT#102 | CP-233235 | 0774 | | F | Update the feature description for Application-Specific Expected UE Behaviour | 18.4.0 | +| 2023-12 | CT#102 | CP-233257 | 0775 | 1 | B | Update application detection event exposure | 18.4.0 | +| 2023-12 | CT#102 | CP-233262 | 0776 | 1 | B | Support of cumulative event report | 18.4.0 | +| 2023-12 | CT#102 | CP-233235 | 0777 | | F | Remove the redundant features | 18.4.0 | +| 2023-12 | CT#102 | CP-233235 | 0778 | 1 | B | Support of Consolidated Data Rate for Multi-member AF session | 18.4.0 | +| 2023-12 | CT#102 | CP-233209 | 0780 | 2 | B | Port handling with AsSessionWithQoS | 18.4.0 | +| 2023-12 | CT#102 | CP-233236 | 0781 | 1 | B | Multiple AF Expected UE behaviour | 18.4.0 | +| 2023-12 | CT#102 | CP-233225 | 0782 | | F | Removal of EN related to data management | 18.4.0 | +| 2023-12 | CT#102 | CP-233257 | 0783 | 1 | F | Wrong attribute name | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0784 | | F | Corrections on monitoring event | 18.4.0 | +| 2023-12 | CT#102 | CP-233234 | 0785 | | F | Remove the multiModalId in the update message and update the terminology | 18.4.0 | +| 2023-12 | CT#102 | CP-233237 | 0787 | | F | Update of info and externalDocs fields | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29328/raw.md b/marked/Rel-18/29_series/29328/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2ac42e7bd291d70cddde92218425f22c81cf2a7c --- /dev/null +++ b/marked/Rel-18/29_series/29328/raw.md @@ -0,0 +1,2560 @@ + + +# 3GPP TS 29.328 V18.1.0 (2023-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 9 | +| 4 Main Concept..... | 9 | +| 5 General Architecture ..... | 10 | +| 5.1 Functional requirements of network entities..... | 10 | +| 5.1.1 Functional Requirements of the Application Server ..... | 10 | +| 5.1.2 Functional requirements of HSS ..... | 10 | +| 5.1.3 Functional Requirements of the Presence Network Agent..... | 10 | +| 5.2 Functional classification of Sh interface procedures..... | 10 | +| 6 Procedure Descriptions ..... | 10 | +| 6.1 User data handling procedures..... | 11 | +| 6.1.1 Data read (Sh-Pull) ..... | 11 | +| 6.1.1.1 Detailed behaviour ..... | 13 | +| 6.1.2 Data Update (Sh-Update) ..... | 16 | +| 6.1.2.1 Detailed behaviour ..... | 18 | +| 6.1.3 Subscription to notifications (Sh-Subs-Notif) ..... | 21 | +| 6.1.3.1 Detailed behaviour ..... | 23 | +| 6.1.4 Notifications (Sh-Notif)..... | 25 | +| 6.1.4.1 Detailed behaviour ..... | 26 | +| 6.2 AS permissions list..... | 27 | +| 6.3 Void..... | 27 | +| 6.4 Void..... | 27 | +| 6.5 User identity to HSS resolution..... | 27 | +| 7 Information element contents..... | 29 | +| 7.1 User Identity..... | 29 | +| 7.1.1 IMS Public User Identity / Public Service Identity ..... | 29 | +| 7.1.2 MSISDN ..... | 29 | +| 7.1.3 External Identifier..... | 29 | +| 7.1A Wildcarded PSI ..... | 29 | +| 7.1B Wildcarded Public User Identity..... | 29 | +| 7.2 Requested Domain ..... | 29 | +| 7.2A Requested Nodes..... | 30 | +| 7.2B Serving Node Indication..... | 30 | +| 7.3 Requested Data..... | 30 | +| 7.4 Service Indication..... | 30 | +| 7.5 Result..... | 30 | +| 7.6 Data ..... | 30 | +| 7.6.1 Repository Data ..... | 32 | +| 7.6.2 IMSPublicIdentity ..... | 32 | +| 7.6.3 IMS User State ..... | 33 | +| 7.6.4 S-CSCF Name ..... | 33 | +| 7.6.5 Initial Filter Criteria..... | 34 | +| 7.6.6 Location Information..... | 34 | +| 7.6.6.1 Location information for CS..... | 34 | +| 7.6.6.2 Location information for GPRS..... | 35 | +| 7.6.6.3 Location information for EPS..... | 36 | +| 7.6.6.4 Location Information for TWAN ..... | 36 | +| 7.6.6.5 Location Information for 5GS ..... | 36 | + +| | | | +|----------------------------------------------------------------------------------------|------------------------------------------------------------|-----------| +| 7.6.7 | User state ..... | 37 | +| 7.6.8 | Charging information ..... | 37 | +| 7.6.9 | MSISDN ..... | 38 | +| 7.6.9A | Extended MSISDN ..... | 38 | +| 7.6.10 | PSIActivation ..... | 38 | +| 7.6.11 | DSAI ..... | 38 | +| 7.6.12 | Void ..... | 39 | +| 7.6.13 | Service Level Trace Information ..... | 39 | +| 7.6.14 | IP address secure binding information ..... | 39 | +| 7.6.15 | Service Priority Level ..... | 39 | +| 7.6.15A | Extended Priority ..... | 39 | +| 7.6.16 | SMSRegistrationInfo ..... | 39 | +| 7.6.17 | UE reachability for IP ..... | 39 | +| 7.6.18 | T-ADS Information ..... | 40 | +| 7.6.19 | Private Identity ..... | 40 | +| 7.6.20 | STN-SR ..... | 40 | +| 7.6.21 | UE SRVCC Capability ..... | 40 | +| 7.6.21A | UE 5G SRVCC Capability ..... | 41 | +| 7.6.22 | CSRN ..... | 41 | +| 7.6.23 | Reference Location Information ..... | 41 | +| 7.6.24 | IMSI ..... | 41 | +| 7.6.25 | IMSPrivateUserIdentity ..... | 41 | +| 7.6.26 | IMEISV ..... | 41 | +| 7.7 | Subscription request type ..... | 41 | +| 7.8 | Current Location ..... | 41 | +| 7.9 | Application Server Identity ..... | 41 | +| 7.10 | Application Server Name ..... | 42 | +| 7.11 | Requested Identity Set ..... | 42 | +| 7.12 | Expiry Time ..... | 42 | +| 7.13 | Send Data Indication ..... | 42 | +| 7.14 | DSAI Tag ..... | 42 | +| 7.15 | Session-Priority ..... | 42 | +| 7.16 | One Time Notification ..... | 42 | +| 7.17 | Repository Data ID ..... | 42 | +| 7.18 | Pre-paging Supported ..... | 42 | +| 7.19 | Local Time Zone Indication ..... | 42 | +| 7.20 | UDR Flags ..... | 43 | +| 7.21 | Call Reference Info ..... | 43 | +| 7.22 | Call Reference Number ..... | 43 | +| 7.23 | AS-Number ..... | 43 | +| 8 | Protocol version identification ..... | 43 | +| 9 | Operational Aspects ..... | 43 | +| Annex A (normative): Mapping of Sh operations and terminology to Diameter ..... | | 44 | +| A.1 | Introduction ..... | 44 | +| A.2 | Sh message to Diameter command mapping ..... | 44 | +| A.3 | Void ..... | 44 | +| Annex B (informative): Message flow ..... | | 45 | +| B.1 | Message flows ..... | 45 | +| B.1.1 | Data Update, Registration, Notification Subscription ..... | 45 | + +| | | +|----------------------------------------------------------------------------------------|-----------| +| Annex C (informative): UML model of the data downloaded over Sh interface ..... | 47 | +| C.1 General description ..... | 47 | +| C.2 PublicIdentifiers ..... | 50 | +| C.3 Sh-IMS-Data ..... | 52 | +| Annex D (normative): XML schema for the Sh interface user profile..... | 54 | +| Annex E (informative): T-ADS request handling in the HSS ..... | 64 | +| Annex F (normative): Diameter overload control mechanism ..... | 72 | +| F.1 General..... | 72 | +| F.2 HSS behaviour ..... | 72 | +| F.3 AS behaviour..... | 72 | +| Annex G (Informative): Diameter overload node behaviour..... | 73 | +| G.1 Message prioritization..... | 73 | +| Annex H (Informative): Data shared among multiple subscribers ..... | 73 | +| H.1 General..... | 73 | +| Annex I (normative): Diameter message priority mechanism ..... | 73 | +| I.1 General..... | 73 | +| I.2 Sh/Dh interface ..... | 74 | +| I.2.1 General ..... | 74 | +| I.2.2 AS/OSA SCS behaviour..... | 74 | +| I.2.3 HSS/SLF behaviour..... | 74 | +| I.2.4 Interactions ..... | 75 | +| Annex J (normative): Diameter load control mechanism ..... | 75 | +| J.1 General..... | 75 | +| J.2 HSS behaviour ..... | 75 | +| J.3 AS behaviour..... | 75 | +| Annex K (informative): Change history..... | 76 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +This 3GPP Technical Specification (TS) specifies: + +1. The interactions between the HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. +2. The interactions between the SIP AS and the SLF (Subscription Locator Function) and between the OSA SCS and the SLF. This interface is referred to as the Dh reference point. + +The IP Multimedia (IM) Core Network Subsystem stage 2 is specified in 3GPP TS 23.228 [1] and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in 3GPP TS 24.228 [2]. + +The IP Multimedia (IM) Session Handling with the IP Multimedia (IM) call model is specified in 3GPP TS 23.218 [4]. + +This document addresses the signalling flows and message contents for the protocol at the Sh and Dh interface. + +This document also addresses how the functionality of Ph interface is accomplished. + +The Presence Service Stage 2 description (architecture and functional solution) is specified in 3GPP TS 23.141 [18]. + +# --- 2 References + +- [1] 3GPP TS 23.228: "IP Multimedia (IM) Subsystem – Stage 2". +- [2] 3GPP TS 24.228: "Signalling flows for the IP multimedia call control based on SIP and SDP (Release 5)". +- [3] 3GPP TS 23.002: "Network architecture". +- [4] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IP Multimedia (IM) call model". +- [5] 3GPP TS 29.329: "Sh Interface based on Diameter – Protocol details". +- [6] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx Interface; Signalling flows and Message Elements". +- [7] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol ; Protocol details". +- [8] Void. +- [9] ITU-T recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes". +- [10] 3GPP TS 23.018: "Basic Call Handling; Technical realization". +- [11] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [12] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [13] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". + +- [14] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 - Stage 2". +- [15] IETF RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies". +- [16] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [17] IETF RFC 3966: "The tel URI for Telephone Numbers". +- [18] 3GPP TS 23.141: "Presence Service; Architecture and Functional Description". +- [19] 3GPP TS 23.012: "Location Management Procedures". +- [20] ANSI X3.4: "Coded Character Set - 7-bit American Standard Code for Information Interchange" +- [21] Void +- [22] 3GPP TS 33.203: "Access Security for IP-based services". +- [23] IETF RFC 791: "Internet Protocol". +- [24] IETF RFC 4291: "IP Version 6 Addressing Architecture". +- [25] IETF RFC 4412: "Communications Resource Priority for the Session Initiation Protocol (SIP)". +- [26] 3GPP TS 29.272: "MME and SGSN Related Interfaces Based on Diameter Protocol". +- [27] 3GPP TS 23.008: "Organization of subscriber data". +- [28] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [29] 3GPP TS 23.060: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2". +- [30] 3GPP TS 29.118: "SGs interface specification". +- [31] 3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol". +- [32] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". +- [33] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services; Stage 2". +- [34] 3GPP TS 29.273: "3GPP EPS AAA interfaces". +- [35] IETF RFC 4776: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information". +- [36] IETF RFC 7683: "Diameter Overload Indication Conveyance". +- [37] ETSI ES 283 034: "e4 interface based on the DIAMETER protocol". +- [38] 3GPP TS 22.153: "Multimedia Priority Service". +- [39] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP" – stage 3. +- [40] 3GPP TS 29.364: "IP Multimedia Subsystem (IMS) Application Server (AS) service data description for AS interoperability". +- [41] IETF RFC 5952: "A Recommendation for IPv6 Address Text Representation". +- [42] IETF RFC 7944: "Diameter Routing Message Priority". +- [43] IETF RFC 8583: "Diameter Load Information Conveyance". +- [44] IETF RFC 6733: "Diameter Base Protocol". + +- [45] 3GPP TS 24.323: "3GPP IP Multimedia Subsystem (IMS) service level tracing management object (MO)". +- [46] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [47] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3". +- [48] 3GPP TS 23.632: "User data interworking, coexistence and migration; Stage 2". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**IP Multimedia session:** IP Multimedia session and IP Multimedia call are treated as equivalent in this specification. + +**Transparent data:** Data that is understood syntactically but not semantically by the HSS. It is data that an AS may store in the HSS to support its service logic. One example is data that an AS stores in the HSS, using it as a repository. + +**Non-transparent data:** Data that is understood both syntactically and semantically by the HSS. + +**AS (Application Server):** a term used to denote either of a SIP Application Server or an OSA Service Capability Server. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|------------------------------------| +| AS | Application Server | +| C | Conditional | +| CSCF | Call Session Control Function | +| CSG | Closed Subscriber Group | +| DRMP | Diameter Routing Message Priority | +| DSCP | Differentiated Services Code Point | +| GIBA | GPRS-IMS-Bundled-Authentication | +| HSS | Home Subscriber Server | +| IE | Information Element | +| IP | Internet Protocol | +| IM | IP Multimedia | +| IMS | IP Multimedia Subsystem | +| M | Mandatory | +| O | Optional | +| SIP | Session Initiation Protocol | +| SLF | Subscription Locator Function | +| S-CSCF | Serving CSCF | + +# --- 4 Main Concept + +This document presents the Sh interface related functional requirements of the communicating entities. + +It gives a functional classification of the procedures and describes the procedures and message parameters. + +Error handling flows, protocol version identification, etc. procedures are also included. + +# --- 5 General Architecture + +This clause further specifies the architectural assumptions associated with the Sh reference point, building on 3GPP TS 23.228 [1], 3GPP TS 23.218 [4] and also the Ph reference point building upon 3GPP TS 23.141 [18]. + +## 5.1 Functional requirements of network entities + +### 5.1.1 Functional Requirements of the Application Server + +The Application Server may communicate with the HSS over the Sh interface. + +For functionality of the Application Server refer to 3GPP TS 23.002 [3], 3GPP TS 23.228 [1] and 3GPP TS 23.218 [4]. + +### 5.1.2 Functional requirements of HSS + +The HSS may communicate with the Application Server over the Sh interface and with the Presence Network Agent over the Ph interface. The functionality of the Ph interface shall be the same as the functionality of the Sh interface. + +For functionality of the HSS refer to 3GPP TS 23.002 [3], 3GPP TS 23.228 [1] and 3GPP TS 23.218 [4]. + +### 5.1.3 Functional Requirements of the Presence Network Agent + +The Presence Network Agent may communicate with the HSS over the Ph interface. In this case, all references to an Application Server in this specification apply also to a Presence Network Agent. + +## 5.2 Functional classification of Sh interface procedures + +Operations on the Sh interface are classified in functional groups: + +1. Data handling procedures + - The download of data from the HSS to an AS. + - The update of data in the HSS. +2. Subscription/notification procedures + - An AS can subscribe to receive notifications from the HSS of changes in data. + - The HSS can notify an AS of changes in data for which the AS previously had subscribed. + +# --- 6 Procedure Descriptions + +In the tables that describe the Information Elements transported by each command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional. + +- A mandatory Information Element (marked as (M) in the table) shall always be present in the command. If this Information Element is absent, an application error occurs at the receiver and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER\_MISSING\_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. +- A conditional Information Element (marked as (C) in the table) shall be present in the command if certain conditions are fulfilled. + - If the receiver detects that those conditions are fulfilled and the Information Element is absent, an application error occurs and an answer message shall be sent back to the originator of the request with the Result-Code + +set to DIAMETER\_MISSING\_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. + +- If those conditions are not fulfilled, the Information Element shall be absent. If however this Information Element appears in the message, it shall not cause an application error and it may be ignored by the receiver if this is not explicitly defined as an error case. Otherwise, an application error occurs at the receiver and an answer message with the Result-Code set to DIAMETER\_AVP\_NOT\_ALLOWED shall be sent back to the originator of the request. A Failed-AVP AVP containing a copy of the corresponding Diameter AVP shall be included in this message. +- An optional Information Element (marked as (O) in the table) may be present or absent in the command, at the discretion of the application at the sending entity. Absence or presence of this Information Element shall not cause an application error and may be ignored by the receiver. + +When a procedure is required to determine the Public Identity used for an identity lookup in HSS and SLF, the HSS and SLF shall derive the Public Identity from the SIP URI or Tel URI contained in the Public-Identity AVP, if not already in canonical form as per 3GPP TS 23.003 [11], as described below: + +- If the Public-Identity AVP contains a SIP URI, the HSS and SLF shall follow rules for conversion of SIP URI into canonical form as specified in IETF RFC 3261 [16] clause 10.3. +- If the Public-Identity AVP contains a Tel URI in E.164 format, the HSS and SLF shall remove visual separators and remove all URI parameters. + +When a command contains a ServiceData XML element with or without content (i.e. ), the Service Data element is defined as present in the clauses 6.1 to 6.4. + +Unknown permanent failure error codes shall be treated in the same way as DIAMETER\_UNABLE\_TO\_COMPLY. For unknown transient failure error codes the request may be repeated, or handled in the same way as DIAMETER\_UNABLE\_TO\_COMPLY. + +## 6.1 User data handling procedures + +### 6.1.1 Data read (Sh-Pull) + +This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used: + +- To read transparent and/or non-transparent data for a specified user from the HSS. + +This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in 3GPP TS 29.329 [5]. Tables 6.1.1.1 and 6.1.1.2 detail the involved information elements. + +**Table 6.1.1.1: Sh-Pull** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------------------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity (See 7.1) | User-Identity | M | IMS Public User Identity, Public Service Identity, MSISDN or External Identifier of the user for whom the data is required.
See clause 7.1 for the content of this AVP. | +| Wildcarded PSI (See 7.1A) | Wildcarded-Public-Identity | O | If the request refers to a Wildcarded PSI, the AS may include the corresponding Wildcarded PSI in this information element.

If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public Service Identity in the detailed behaviour refer to the Wildcarded PSI.

If this information element is present, Wildcarded Public User Identity shall not be present. | +| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU | O | If the request refers to a Wildcarded Public User Identity, the AS may include the corresponding Wildcarded Public User Identity in this information element.

If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public User Identity in the detailed behaviour refer to the Wildcarded Public User Identity.

If this information element is present, Wildcarded PSI shall not be present. | +| Requested data (See 7.3) | Data-Reference | M | This information element indicates the reference to the requested information. The set of valid reference values are defined in 7.6. | +| Requested Identity set (See 7.11) | Identity-Set | O | If Data-Reference indicates that IMS Public Identities is the requested data set to be downloaded, this information element should be included and it indicates the information to be downloaded. See clause 7.6.2. | +| Requested domain (See 7.2) | Requested-Domain | C | This information element indicates the domain to which the operation is applicable. Check table 7.6.1 to see when it is applicable. | +| Requested nodes (See 7.2A) | Requested-Nodes | O | This information element indicates the Node Types to which the operation is applicable. Check table 7.6.1 to see when it is applicable. | +| Current Location (See 7.8) | Current-Location | C | This information element indicates whether an active location retrieval has to be initiated or not. It shall be present if Location Information is requested.
If this information element takes the value InitiateActiveLocationRetrieval (1) the HSS shall indicate to the MSC/VLR and/or SGSN and/or MME the need to initiate an active location retrieval.
Check table 7.6.1 to see when it is applicable. | +| Service Indication (See 7.4) | Service-Indication | C | IE that identifies, together with the User Identity included in the User-Identity AVP and Data-Reference, the set of service related transparent data that is being requested.
Check table 7.6.1 to see when it is applicable. | +| Application Server Identity (See 7.9) | Origin-Host | M | IE that identifies the AS originator of the request and that is used to check the AS permission list. | +| Application Server Name (See 7.10) | Server-Name | C | IE that is used, together with the User Identity included in the User-Identity AVP and Data-Reference, as key to identify the filter criteria.
Check table 7.6.1 to see when it is applicable. | +| DSAI Tag (See 7.14) | DSAI-Tag | C | IE that is used, together with the User Identity included in the User-Identity AVP and Data-Reference, as key to identify the instance of Dynamic Service Activation Info (DSAI) requested.
Check table 7.6.1 to see when it is applicable. | +| Session Priority (see 7.15) | Session-Priority | O | This information element, if present, shall indicate the session's priority to the HSS. | +| Private Identity (see 7.6.19) | User-Name | C | Private Identity of the user for whom the data is required.

Check table 7.6.1 to see when it is applicable. | +| Serving Node Indication (See 7.2B) | Serving-Node-Indication | O | This information element shall indicate that only the serving node address/identity associated to the location data is required.

Check table 7.6.1 to see when it is applicable. | + +| | | | | +|---------------------------------------|----------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pre-paging Supported (See 7.18) | Pre-paging-Supported | O | This information element shall indicate whether the AS supports pre-paging or not.
It indicates by its absence that the AS does not support pre-paging. For details see 3GPP TS 23.018 [10]. | +| Local Time Zone Indication (See 7.19) | Local-Time-Zone-Indication | O | This information element shall indicate that the Local Time Zone is requested and shall indicate whether only the Local Time Zone is required or the Local Time Zone is required together with other location data.

Check table 7.6.1 to see when it is applicable. | +| UDR Flags (See 7.20) | UDR-Flags | O | This Information Element contains a bit mask. See 7.x for the meaning of the bits. | +| Call-Reference-Info (See 7.21) | Call-Reference-Info | O | This Information Element contains a Call Reference Number and the AS-Number. May be present when Data Reference is CSRN. It allows a later retry of the call setup in the context of MTRR. See 3GPP TS 23.292 [33] | + +Table 6.1.1.2: Sh-Pull Resp + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------------------------|-----------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result (See 7.5) | Result-Code / Experimental_Result | M | Result of the request.

Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [44]).

Experimental-Result AVP shall be used for Sh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Wildcarded PSI (See 7.1A) | Wildcarded-Public-Identity | O | If the request refers to a specific PSI matching a Wildcarded PSI and the Wildcarded PSI was not included in the request and is not included in the User-Data AVP, the HSS may include the corresponding Wildcarded PSI in this information element. This information may be used by the AS to identify the affected Wildcarded PSI. | +| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU | O | If the request refers to a Public User Identity matching a Wildcarded Public User Identity and the Wildcarded-IMPU AVP was not included in the request and is not included in the User-Data AVP, the HSS may include the corresponding Wildcarded Public User Identity in this information element. This information may be used by the AS to identify the affected Wildcarded Public User Identity. | +| Data (See 7.6) | User-Data | C | Requested data. This information element shall be present if the requested data exists in the HSS and the AS has permissions to read it. | + +#### 6.1.1.1 Detailed behaviour + +The HSS may prioritise the received request message according to priority level received within the Session-Priority AVP. + +NOTE 1: Refer to Annex I for HSS procedures associated with the handling of both the Session-Priority AVP and DRMP AVP received in the request message. + +The conditions for the inclusion of Requested-Domain and Requested-Node as an additional key to the requested data are described in table 7.6.1. If repository data is requested, Service-Indication shall be present in the request. If initial filter criteria are requested, the Server-Name AVP shall contain the SIP URL of the AS that initiates the request; requests for initial filter criteria are limited to those initial filter criteria which are relevant to the requesting AS. If DSAI information is requested, the DSAI-Tag AVP shall be present. + +Upon reception of the Sh-Pull request, the HSS shall, in the following order: + +1. In the AS permission list (see clause 6.2) check that the requested user data is allowed to be read (Sh-Pull) by this AS by checking the combination of the identity of the AS sending the request (identified by the Origin-Host AVP) and the supplied Data-Reference. + +If one or more Data References in the request are not allowed to be read, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_DATA\_CANNOT\_BE\_READ in the Sh-Pull Response. + +2. Check that the User Identity for whom data is asked exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Sh-Pull Response. +- 2a. Check if the Private Identity (if received) corresponds to IMPU/MSISDN/External Identifier received in User-Identity. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH. +3. If the type of the User Identity (i.e. IMS Public User Identity or Public Service Identity, MSISDN or External Identifier) does not apply according to Table 7.6.1 as access key for the Data-Reference (if Notif-Eff is in use: for all the Data-References) indicated in the request, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Pull Response. +- 3a. If data-reference is IPAddressSecureBindingInformation (22) and the User Identity is an IMS Public User Identity that is shared between multiple Private User Identities, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Pull Response. +4. Check whether or not the data that is requested to be downloaded by the AS is currently being updated by another entity. If there is an update of the data in progress, the HSS may delay the Sh-Pull-Resp message until the update has been completed. The HSS shall ensure that the data returned is not corrupted by this conflict. If HSS is not able to delay the Sh-Pull-Resp message e.g. due to timeout the Experimental-Result-Code shall be set to DIAMETER\_USER\_DATA\_NOT\_AVAILABLE. +- 4a. If T-ADS Information is requested, the HSS/UDM shall take into account information possibly received from MME ,SGSN, and/or AMF during the registration, location update or notification procedure, in order to decide whether MME, SGSN and/or AMF need to be contacted before a response is sent to the AS. + - The HSS/UDM shall provide the most recent IMS Voice over PS Sessions support indication as indicated by the serving nodes. The HSS/UDM shall provide the Access Type and RAT type, if available. The HSS/UDM may also provide the last UE activity time, if available which should include a specific timezone. See Annex E. + +NOTE 2: The last UE activity time without a specific timezone can result in IMS receiving unexpected time if timezone is not included, especially for roaming to PLMN with different timezone. + +- If all serving nodes need to be contacted, and if at least one serving node does not support T-ADS Data Retrieval or did not successfully answer to the T-ADS request from the HSS, the HSS shall indicate that IMS Voice over PS Sessions support is unknown, i.e., the HSS shall not indicate support, or non-support, of IMS Voice over PS Sessions unless all registered serving nodes have provided indication of their support, non-support, or detached status. +- If the HSS/UDM knows that one of the registered serving nodes is a Gn/Gp-SGSN, the HSS/UDM shall not contact the MME for T-ADS Data Retrieval, and shall provide the most recent IMS Voice over PS Sessions support indication as indicated by the Gn/Gp-SGSN and/or the AMF. If the Gn/Gp-SGSN needs to be contacted and it does not support T-ADS Data Retrieval, the HSS shall indicate IMS Voice over PS Sessions support is unknown. + +NOTE 3: If the UE is registered with both MME and SGSN, and the HSS knows that the SGSN is a Gn/Gp-SGSN, the HSS does not need to know if the MME supports IMS Voice over PS Sessions or not. The HSS can determine that the SGSN registered is a Gn/Gp-SGSN by different ways, e.g. by configuration, or according to the information (e.g. EPS Subscription Data Not Needed Indicator) received in MAP\_UpdateGPRSLocation request. + +NOTE 4: If the UE is registered with both MME and SGSN, and the HSS is unable to know that the SGSN is a Gn/Gp-SGSN, the HSS will indicate IMS Voice over PS Sessions support as unknown if the MME does not support T-ADS Data Retrieval or did not successfully answer to the T-ADS request from the HSS, even if the Gn/Gp-SGSN indicated IMS Voice over PS Sessions is supported. + +- If the serving node answers successfully to the T-ADS data request, but it does not include any of the T-ADS Information Elements (IMS Voice over PS Sessions Supported, Access Type, RAT Type and Last UE Activity Time), the HSS shall indicate IMS Voice over PS Sessions support is not supported, unless the subscriber is attached in another node that indicates support (if applicable). + +- If at least one serving node provided T-ADS data to the HSS, the HSS may also provide the received last UE activity time which should include a specific timezone, Access Type and RAT type. If all serving nodes successfully answer to the T-ADS request from the HSS, the HSS shall provide the most recent IMS Voice over PS Sessions support indication as indicated by the serving nodes. + +NOTE 5: The last UE activity time without a specific timezone can result in IMS receiving unexpected time if timezone is not included, especially for roaming to PLMN with different timezone. + +- 4b. If CSRN is requested but roaming number retrieval from the MSC/VLR fails, the HSS shall include an empty CSRN element in the xml document returned to the AS. In addition, if MTRR is applicable (see 3GPP TS 23.018 [10]), the HSS shall set an MTRR-Indication in the xml document. See 3GPP TS 23.292 [33]. + +- 5. The HSS shall include the data pertinent to the requested Data Reference in the User-Data AVP. The HSS shall set the Result-Code to DIAMETER\_SUCCESS. This includes cases where the data is not available to the HSS. The pertinent data included shall refer to the received IMPU/MSISDN/External Identifier and Private Identity (if present). + +NOTE 6: Data referred to a Private Identity (e.g. IMS Private User Identity) implies that only the data (e.g. Location Information) specific for that Private Identity is included, regardless of the type of User Identity received (e.g. IMS Public User Identity shared by multiple IMS Private User Identities). + +If both the AS and the HSS have determined via mutual feature evaluation to not support the Notif-Eff feature and in the case that requested data is not available to the HSS, the HSS shall not include the User-Data AVP in the Sh-Pull Response. + +If both the AS and the HSS support the Notif-Eff feature, the HSS shall include the data pertinent to all the requested Data References, Service Indications and Identity Sets in the User-Data AVP. The following applies: + +- If none of the requested data is available to the HSS, the HSS shall not include the User-Data AVP in the Sh-Pull Response. +- If some of the requested data is not available to the HSS, it shall be indicated as follows: + - Empty repository data shall be indicated with the RepositoryData element that contains a Service Indication and a Sequence Number but does not contain a ServiceData element (i.e. ServiceData is not present). + - Unavailable Public Identifiers shall be indicated with an empty PublicIdentifiers element. + - Unavailable location information shall be indicated by an empty CSLocationInformation and/or an empty PSLocationInformation element and/or an empty EPSLocationInformation element and/or an empty TWANLocationInformation and/or an empty Sh-5GSLocationInformation. + - Unavailable CS-UserState shall be indicated by a missing CSUserState element. + - Unavailable PS-UserState shall be indicated by a missing PSUserState element. + - Unavailable EPS-UserState shall be indicated by a missing EPSUserState element. + - Unavailable elements of Sh IMS Data shall be indicated as follows: + - An unavailable S-CSCF name shall be indicated with empty SCSCFName element. + - An unavailable IP Address Secure Binding Information shall be indicated with empty IPv4address element or empty IPv6prefix element. + - If all iFCs for the user that are relevant for the AS are unavailable it shall be indicated with empty IFCs element. + - Not available UE SRVCC capability shall be indicated with missing UE-SRVCC-Capability element. + - Not available UE 5G SRVCC capability shall be indicated with missing UE-5G-SRVCC-Capability element. + - Not available STN-SR shall be indicated with empty STN-SR element. + +NOTE 7: If the HSS supports interworking with UDM, the HSS can also take into account the availability of the STN-SR from the UDM as described in 3GPP TS 23.632 [48]. + +- Not available CSRN shall be indicated with empty CSRN element. +- Not available IMSI shall be indicated with empty IMSI element. + +NOTE 8: If there is no available STN-SR in the HSS, it indicates that the user is not SRVCC subscribed and if there is no available STN-SR from the UDM, it indicates that the user is not 5G-SRVCC subscribed, as described in 3GPP TS 23.008 [27] and 3GPP TS 23.632 [48]. + +If there is an error in any of the above steps, then the HSS shall stop processing and shall return the error code specified in the respective step (see 3GPP TS 29.329 [5] and 3GPP TS 29.229 [7] for an explanation of the error codes). + +If the HSS cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or empty mandatory data elements, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +Otherwise, the requested operation shall take place and the HSS shall return the Result-Code AVP set to DIAMETER\_SUCCESS. Result-Code DIAMETER\_SUCCESS is used also if the requested data does not exist in the HSS i.e. when the HSS is indicating valid empty data elements. + +### 6.1.2 Data Update (Sh-Update) + +This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used: + +- To allow the AS to update the transparent (repository) data stored at the HSS for each IMS Public User Identity (for Public User Identities matching a Wildcarded Public User Identity, the transparent data shall be stored per Wildcarded Public User Identity, and not for each specific Public User Identity matching that Wildcarded Public User Identity) or Public Service Identity (for Public Service Identities matching a Wildcarded PSI, the transparent data shall be stored per Wildcarded PSI, and not for each specific Public Service Identity matching that Wildcarded PSI). +- To allow the AS to update the PSI Activation State of a distinct Public Service Identity in the HSS. +- To allow the AS to update the Dynamic Service Activation Info stored at the HSS. +- To allow the AS to update the Short Message Service Registration Info stored at the HSS. +- To allow the AS to update the STN-SR stored at the HSS and/or the STN-SR stored at the UDM. + +NOTE: In accordance with 3GPP TS 23.632 [48], if there is only an STN-SR available in the UDM, the STN-SR in the UDM is updated. If there is only an STN-SR available in the HSS, the STN-SR in the HSS is updated. If there is an STN-SR available in the UDM and in the HSS, the STN-SR in the UDM and the HSS are updated. + +This procedure is mapped to the commands Profile-Update-Request/Answer in the Diameter application specified in 3GPP TS 29.329 [5]. Tables 6.1.2.1 and 6.1.2.2 detail the involved information elements. + +Table 6.1.2.1: Sh-Update + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------------------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity (See 7.1) | User-Identity | M | IMS Public User Identity or Public Service Identity or MSISDN or External Identifier for which data is updated.
See clause 7.1 for the content of this AVP. | +| Wildcarded PSI (See 7.1A) | Wildcarded-Public-Identity | O | If the request refers to a Wildcarded PSI, the AS may include the corresponding Wildcarded PSI in this information element.

If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public Service Identity in the detailed behaviour refer to the Wildcarded PSI.

If this information element is present, Wildcarded Public User Identity shall not be present. | +| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU | O | If the request refers to a Wildcarded Public User Identity, the AS may include the corresponding Wildcarded Public User Identity in this information element.

If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public User Identity in the detailed behaviour refer to the Wildcarded Public User Identity.

If this information element is present, Wildcarded PSI shall not be present. | +| Requested data (See 7.3) | Data-Reference | M | This information element includes the reference to the data on which updates are required (possible values of the Data Reference are defined in Table 7.6.1). | +| Data (See 7.6) | User-Data | M | Updated data. | +| Application Server Identity (See 7.9) | Origin-Host | M | IE that identifies the AS originator of the request and that is used to check the AS permission list. | +| Private identity (see 7.6.19) | User-Name | C | Private Identity of the user for whom the data is required.

Check table 7.6.1 to see when it is applicable. | + +**Table 6.1.2.2: Sh-Update Resp** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result (See 7.5) | Result-Code / Experimental-Result | M | Result of the update of data in the HSS.

Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [44]).

Experimental-Result AVP shall be used for Sh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Wildcarded PSI (See 7.1A) | Wildcarded-Public-Identity | O | If the request refers to a specific PSI matching a Wildcarded PSI and the Wildcarded-PSI was not included in the request, the HSS may include the corresponding Wildcarded PSI in this information element. This information may be used by the AS to identify the affected Wildcarded PSI. | +| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU | O | If the request refers to a Public User Identity matching a Wildcarded Public User Identity and the Wildcarded-IMPU AVP was not included in the request, the HSS may include the corresponding Wildcarded Public User Identity in this information element. This information may be used by the AS to identify the affected Wildcarded Public User Identity. | +| Repository Data ID (See 7.17) | Repository-Data-ID | O | If the HSS and the AS support the Update-Eff feature or the Update-Eff-Enhance feature and if a Sh-Update Request with multiple repository data fails, this information element shall include the service indication and the sequence number of the repository data instance that has generated the error. | +| Requested data (See 7.3) | Data-Reference | O | If the HSS and the AS support the Update-Eff-Enhance feature and if an Sh-Update Request with multiple data references fails, this information element shall include the Data reference for the data instance that has generated the error. | + +#### 6.1.2.1 Detailed behaviour + +Within the Sh-Update Request, the keys to determine the updated data are part of the information element Data (See 7.6). When data in the repository is updated (i.e. added, modified or removed) Service-Indication and Sequence-Number are also sent as part of the information element Data. + +Newly added transparent data shall be associated with a Sequence Number of 0 in the Sh-Update Request. Sequence Number value 0 is reserved exclusively for indication of newly added transparent data. + +Modified and removed transparent data shall be associated within the Sh-Update Request with a Sequence Number of $n+1$ where $n$ is the original Sequence Number associated with the transparent data before modification or removal. If $n$ equals 65535, then the next modification or deletion of that transparent data shall be associated with a Sequence Number of 1. + +Upon reception of the Sh-Update request, the HSS shall, in the following order: + +1. In the AS permission list (see clause 6.2) check that the data that is requested to be updated (Sh-Update) by this AS, is allowed to be updated by checking the combination of the identity of the AS sending the request (identified by the Origin-Host AVP) and the supplied Data-Reference. + - If the data is not allowed to be updated, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_DATA\_CANNOT\_BE\_MODIFIED in the Sh-Update Response. +2. Check that the User Identity in the request exists in the HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Sh-Update Response. +- 2a. Check if the Private User Identity (if received) corresponds to the IMPU/MSISDN/External Identifier received in User-Identity. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH. +3. If the type of the User Identity (i.e. IMS Public User Identity or Public Service Identity or MSISDN or External Identifier) does not apply according to Table 7.6.1 as access key for the Data-Reference (if Update-Eff-Enhance + +is in use: for all the Data-References) indicated in the request, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Update Response. + +4. If Data-Reference is PSIActivation (18), then the HSS shall check that the User Identity contains a distinct Public Service Identity. If it does, then the HSS shall update the corresponding PSI Activation State and return the Result-Code AVP set to DIAMETER\_SUCCESS. If it does not, then the Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Update Response. + +The change of a Public Service Identity from ACTIVE to INACTIVE shall trigger the network initiated deregistration of the Public Service Identity in the HSS. + +- 4a. If Data-Reference is DSAI (19), check whether or not, for the Public Identity, there is an instance of DSAI matching the DSAI-Tag contained in the Sh-Update command. If so, then the HSS shall update the DSAI value and return the Result-Code AVP set to DIAMETER\_SUCCESS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_DSAI\_NOT\_AVAILABLE. + +The changes of DSAI value shall trigger the procedures described in clause 7.14 in order to determine which initial filter criteria should be masked or unmasked. If these procedures change the set of unmasked initial filter criteria, the HSS should behave as if the initial filter criteria had been administratively changed, which implies e.g. sending Sh-Notif or Cx-Update\_Subscr\_Data messages (see 3GPP TS 29.228 [6]). + +- 4b. If Data-Reference is SMSRegistrationInfo (24), check whether or not, for the IMS Public User Identity or MSISDN or External Identifier, IP-SM-GW number element contained in the Sh-Update command is empty. If it is empty, then the HSS shall delete the stored registered IP-SM-GW number (if any) and the stored registered IP-SM-GW Diameter Identity (if any), and return the Result-Code AVP set to DIAMETER\_SUCCESS. A preconfigured IP-SM-GW number and preconfigured IP-SM-GW Diameter Identity shall not be deleted. + +If it is not empty, the HSS shall store/update the registered IP-SM-GW number and, if S6c is supported, the IP-SM-GW Diameter Identity as received within the Origin-Host and Origin-Realm AVPs, and return the Result-Code AVP set to DIAMETER\_SUCCESS. A preconfigured IP-SM-GW number and preconfigured IP-SM-GW Diameter Identity shall not be overwritten. + +The Service Centre Address in the HSS shall not be updated by this operation. + +NOTE 1: The address of the Short Message Service Centre as defined in 7.6.16 is only applicable to Sh-Pull operation. + +- 4c. If the Data-Reference indicates that repository data is present, and if the HSS and the AS supports the Update-Eff feature, check whether there are multiple repository data instances. If so, then repeat the steps 5 and 6 below for each instance of repository data ensuring that no repository data is changed until the checks done in the steps 5 and 6 have been successful for all the repository data instances. +- 4d. If the Data-Reference is STN-SR (27) and if the STN-SR is different from the one previously stored or provisioned in the HSS, the HSS shall overwrite the STN-SR. If the Data-Reference is STN-SR (27), the HSS supports interworking with the UDM (see in 3GPP TS 23.632 [48]), and if the STN-SR is different from the one previously stored or provisioned in the UDM, the UDM shall overwrite the STN-SR. If the Data-Reference is STN-SR (27), and if there is no stored STN-SR in the HSS and there is no stored STN-SR in the UDM, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Update Response. + +NOTE 2: If there is no stored STN-SR in the HSS, it indicates that the user is not SRVCC subscribed and if there is no stored STN-SR in the UDM, it indicates that the user is not 5G-SRVCC subscribed, as described in 3GPP TS 23.008 [27]. + +5. Check whether or not the data that is requested to be updated by the AS, as identified by the Service-Indication, is currently being updated by another entity. If there is an update of the data in progress, Experimental-Result shall be set to DIAMETER\_PRIOR\_UPDATE\_IN\_PROGRESS in the Sh-Update Response. +6. Check whether or not there is any repository data stored at the HSS already for the specified Service-Indication and the associated IMS Public User Identity (or group if the IMS Public User Identity is alias) or Public Service Identity. + - If repository data identified by the Service-Indication is stored at the HSS for the specified IMS Public User Identity, IMS Public User Identity group or Public Service Identity, check the following premises: + +1. Sequence\_Number\_in\_Sh\_Update is not equal to 0 +2. (Sequence\_Number\_in\_Sh\_Update - 1) is equal to (Sequence\_Number\_In\_HSS modulo 65535) + - If either of the above premises is false then Experimental-Result shall be set to DIAMETER\_ERROR\_TRANSPARENT\_DATA\_OUT\_OF\_SYNC in the Sh-Update Response. + - If both of the above premises are true, then check whether or not Service Data is received within the Sh-Update Req. + - If Service Data element is present in the Sh-Update Req, check whether or not the size of the data is greater than that which the HSS is prepared to accept. + - If there is more data than the HSS is prepared to accept then Experimental-Result shall be set to DIAMETER\_ERROR\_TOO\_MUCH\_DATA and the new data shall be discarded. + - If the HSS is prepared to accept the data, then the repository data stored at the HSS shall be updated with the repository data sent in the Sh-Update Req and the Sequence Number associated with that repository data shall be updated with that sent in the Sh-Update Req. This triggers the sending of Sh-Notif messages to any other ASs that are subscribed to Notifications for updates to the service data for that IMS Public User Identity or Public Service Identity. This also triggers the sending of Sh-Notif messages for an alias of that IMS Public User Identity to any AS that is subscribed to Notifications for updates to the service data for that alias of the received IMS Public User Identity (see clause 6.1.4). + - If Service Data element is not present in the Sh-Update Req, the data stored in the repository at the HSS shall be removed, and as a consequence the Service Indication and the Sequence Number associated with the removed data shall also be removed. This triggers the sending of Sh-Notif messages with that Service Indication and Sequence Number to be deleted but with an absent Service Data element, to any other ASs that are subscribed to Notifications for updates to the service data for that IMS Public User Identity or Public Service Identity (see 6.1.4). After sending Sh-Notif messages, the subscriptions to Notifications for the removed Repository Data shall be deleted. + - If repository data identified by the Service-Indication is not stored for the IMS Public User Identity, IMS Public User Identity group or Public Service Identity i.e. the Sh-Update Req intends to create a new repository data, check whether or not the Sequence Number in the Sh-Update Req is 0. + - If the sequence number is not set to 0, Experimental-Result shall be set to DIAMETER\_ERROR\_TRANSPARENT\_DATA\_OUT\_OF\_SYNC + - If the sequence number is set to 0 check whether Service Data is included within the Sh-Update Req. + - If Service Data is not present in the Sh-Update Req, then Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED and the operation shall be ignored by the HSS. + - If Service Data element is present in the Sh-Update Req, check whether or not the size of the data is greater than that which the HSS is prepared to accept. + - If there is more data than the HSS is prepared to accept then Experimental-Result shall be set to DIAMETER\_ERROR\_TOO\_MUCH\_DATA and the new data shall be discarded. + - If the HSS is prepared to accept the data included in the Sh-Update Req, then the data shall be stored in the data repository in the HSS. + +If the HSS receives a request to update data other than Repository Data while a previous update request of the same data for the same user identity is still in progress, the HSS should stop processing the later request and set the Experimental-Result-Code to DIAMETER\_PRIOR\_UPDATE\_IN\_PROGRESS. + +NOTE 3: If the HSS receives a request to update data other than Repository Data while a previous update request of the same data for the same user identity is still in progress, it identifies either an AS or network misbehavior. If the HSS processed those requests it could cause a network unexpected behaviour. + +If there is an error in any of the above steps then the HSS shall stop processing and shall return the error code specified in the respective step (see 3GPP TS 29.329 [5] and 3GPP TS 29.229 [7] for an explanation of the error codes). + +If the HSS cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +If the HSS and the AS support the Update-Eff feature, the Sh Update is successful only if it is successful for the update of all the repository data instances in the request. Otherwise the HSS shall keep or restore all the stored repository data as they were before receiving the Sh Update request. If the error occurs during the steps 5 or 6 and if there were several repository data instances in the request, the Sh Update response shall contain a Repository Data ID indicating the service indication and the sequence number of (one of) the repository data instance(s) for which an error occurred. + +If the HSS and the AS support the Update-Eff-Enhance feature, the Sh Update is successful only if it is successful for the update of all the data instances in the request. Otherwise the HSS shall keep or restore all the stored data as they were before receiving the Sh Update request. If an error occurs during the steps 5 or 6 with any of the data instance in the request, the Sh Update response shall contain the corresponding Data Reference indicating the first data instance for which an error occurred. If there were several repository data instances in the request, the HSS shall behave the same as specified for Update-Eff feature. + +Otherwise, the requested operation shall take place and the HSS shall return the Result-Code AVP set to DIAMETER\_SUCCESS. + +NOTE 4: When an AS receives DIAMETER\_ERROR\_TRANSPARENT\_DATA\_OUT\_OF\_SYNC the AS may attempt to resolve the inconsistency between the version of the repository data that it holds and that stored at the HSS. It may execute a Sh-Pull to retrieve the current version of the data from the HSS or it may wait to receive a subsequent Sh-Notif message from the HSS for the affected repository data. + +### 6.1.3 Subscription to notifications (Sh-Subs-Notif) + +This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used: + +- To subscribe to Notifications for when particular transparent and/or non-transparent data for a specified IMS Public User Identity or Public Service Identity is updated, from the HSS. +- Optionally to request the user data from the HSS in the same operation. + +This procedure is mapped to the commands Subscribe-Notifications-Request/Answer in the Diameter application specified in 3GPP TS 29.329 [5]. Tables 6.1.3.1 and 6.1.3.2 detail the information elements involved. + +**Table 6.1.3.1: Sh-Subs-Notif** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------------------------------|----------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity (See 7.1) | User-Identity | M | IMS Public User Identity or Public Service Identity or MSISDN or External Identifier for which notifications of data changes are requested. See clause 7.1 for the content of this AVP. | +| Wildcarded PSI (See 7.1A) | Wildcarded-Public-Identity | O |

If the request refers to a Wildcarded PSI, the AS may include the corresponding Wildcarded PSI in this information element.

If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public Service Identity in the detailed behaviour refer to the Wildcarded PSI.

If this information element is present, Wildcarded Public User Identity shall not be present.

| +| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU | O |

If the request refers to a Wildcarded Public User Identity, the AS may include the corresponding Wildcarded Public User Identity in this information element.

If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public User Identity in the detailed behaviour refer to the Wildcarded Public User Identity.

If this information element is present, Wildcarded PSI shall not be present.

| +| Requested Data (See 7.3) | Data-Reference | M | This information element includes the reference to the data on which notifications of change are required (valid reference values are defined in 7.6). | +| Subscription request type (See 7.7) | Subs-Req-Type | M | This information element indicates the action requested on subscription to notifications. | +| Send Data Indication (See 7.13) | Send-Data-Indication | O |

This information element requests that the data is sent in the response.

Send Data Indication is not applicable to one time subscriptions to UE reachability for IP.

| +| Service Indication (See 7.4) | Service-Indication | C |

IE that identifies, together with the User Identity and Data-Reference, the set of service related transparent data for which notifications of changes are requested.

Check table 7.6.1 to see when it is applicable.

| +| Application Server Identity (See 7.9) | Origin-Host | M | IE that identifies the AS originator of the request and that is used to check the AS permission list. | +| Application Server Name (See 7.10) | Server-Name | C |

IE that is used, together with the User Identity and Data-Reference, as key to identify the filter criteria.

Check table 7.6.1 to see when it is applicable.

| +| Expiry Time (See 7.12) | Expiry-Time | O | Gives the absolute time requested at which the subscription expires. | +| Dynamic Service Activation Information Tag (see 7.14) | DSAI-Tag | C |

IE that identifies, together with the User Identity and Data-Reference, the instance of Dynamic Service Activation Info (DSAI) requested.

Check table 7.6.1 to see when it is applicable.

| +| Requested Identity set (See 7.11) | Identity-Set | C |

If Data-Reference indicates that IMS Public Identities is the requested data set, this information element shall be included and it indicates the information to be subscribed to (and optionally to be downloaded).

See clause 7.6.2.

| +| One time notification (See 7.16) | One-Time-Notification | C |

This information element indicates if subscription shall be ended by the HSS after sending the first notification.

This IE shall be present for UE reachability for IP.

| +| Private identity (see 7.6.19) | User-Name | O |

Private Identity of the user for whom the data is required.

Check table 7.6.1 to see when it is applicable.

| + +**Table 6.1.3.2: Sh-Subs-Notif Resp** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expiry Time (See 7.12) | Expiry-Time | O | Acknowledges the absolute time at which the subscription expires. | +| Data (See 7.6) | User-Data | O | Current values of the data for which notifications have been requested.

It should be present if the Send-Data-Indication AVP is set to value USER_DATA_REQUESTED. | +| Wildcarded PSI (See 7.1A) | Wildcarded-Public-Identity | O | If the request refers to a specific PSI matching a Wildcarded PSI and the Wildcarded PSI was not included in the request and is not included in the User-Data AVP, the HSS may include the corresponding Wildcarded PSI in this information element. This information may be used by the AS to identify the affected Wildcarded PSI. | +| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU | O | If the request refers to a Public User Identity matching a Wildcarded Public User Identity and the Wildcarded-IMPU AVP was not included in the request, the HSS may include the corresponding Wildcarded Public User Identity in this information element. This information may be used by the AS to identify the affected Wildcarded Public User Identity. | +| Result (See 7.5) | Result-Code / Experimental-Result | M | Result of the request.

Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [44]).

Experimental-Result AVP shall be used for Sh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +#### 6.1.3.1 Detailed behaviour + +The HSS shall take note of the subscription request on the data identified by User Identity and Data-Reference. If notifications on changes of repository data are requested, Service-Indication shall be present in the request. If notifications on changes of filter criteria are requested, the Server-Name AVP shall be used as key to the filter criteria. If the request contains a specific Public Service Identity matching a Wildcarded PSI, the HSS shall interpret that the subscription refers to the information associated to the Wildcarded PSI. The Server-Name AVP shall contain the SIP URL of the AS sending the request. If notifications on changes of DSAI are requested, the DSAI-Tag AVP shall be used as key of the DSAI whose changes are to be monitored. + +Upon reception of the Sh-Subs-Notif request, the HSS shall, in the following order (if there is an error in any of the following steps the HSS shall stop processing and return the corresponding error code, see 3GPP TS 29.329 [5] and 3GPP TS 29.229 [7]), process the hereafter steps that, unless otherwise stated, apply both for the Subscription request type information element indicating the request is to subscribe or to unsubscribe: + +1. In the AS permission list (see clause 6.2) the HSS shall check that the AS is allowed to subscribe to notifications (Sh-Subs-Notif) for the requested data by checking the combination of the identity of the AS sending the request (identified by the Origin-Host AVP) and the supplied Data-Reference. + - If this AS does not have Sh-Subs-Notif permission for the data referenced, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_DATA\_CANNOT\_BE\_NOTIFIED in the Sh-Subs-Notif Response. +2. The HSS shall check that the User Identity in the request exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Sh-Subs-Notif Response. +- 2a. Check if the Private Identity (if received) corresponds to IMPU/MSISDN/External Identifier received in User-Identity. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH. +3. If the type of the User Identity (i.e. IMS Public User Identity or Public Service Identity or MSISDN or External Identifier) does not apply according to Table 7.6.1 as access key for the Data-Reference (if Notif-Eff is in use: for all the Data-References) indicated in the request, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Subs-Notif Response. + +- 3a. If Data-Reference is DSAI (19), check whether or not, for the Public Identity, there is an instance of DSAI matching the DSAI-Tag contained in the Sh-Subs-Notif command. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_DSAI\_NOT\_AVAILABLE. +4. If the Sh-Subs-Notif Request contains an Expiry Time, the HSS should also include in the Sh-Subs-Notif Response an Expiry Time IE with the absolute time at which the subscription expires in the case of a successful subscription. This time may be earlier than the requested expiry time. If the HSS includes this IE, then no notification shall be sent to the AS after the expiration time. If the HSS receives a Sh-Subs-Notif Request without the Expiry Time IE, the HSS should treat it as a request for an unlimited subscription. + +If the HSS does not include this IE in the response, that indicates an unlimited subscription. + +If a subsequent request is received by the HSS where the Expiry Time IE is present but different from what the HSS has previously stored, the HSS should replace the stored expiration time with what was received in the request. + +5. If Data-Reference is RepositoryData(0) and the transparent data associated with the Service Indication does not exist in the HSS (i.e. Service Data is not present), then Experimental-Result shall be set to DIAMETER\_ERROR\_SUBS\_DATA\_ABSENT. +6. If the Subscription request type information element indicates that this is a request to subscribe, the HSS shall associate the Application Server Identity with the list of entities that need to be notified when the data identified by the request is modified and set the Result-Code to DIAMETER\_SUCCESS in the Sh-Subs-Notify response. If the Subscription request type information element indicates that this is a request to unsubscribe, the HSS shall remove the association of the Application Server Identity with the same list. In this last case, the Result-Code shall be set to DIAMETER\_SUCCESS if the operation is successful or if the Application Server Identity was not present in the list. +7. If the HSS and AS supports the Notif-Eff feature and if multiple Data-Reference AVPs occur in the Sh-Subs-Notif Request, each Data-Reference shall be treated as a request to establish a separate notification request. When multiple notification requests are requested, and all of them succeed, the HSS shall set the Result-Code to DIAMETER\_SUCCESS in the Sh-Subs-Notify response. If one of them is unsuccessful, the HSS shall return the Result code with the relevant Diameter error indication and come back to the situation regarding to subscriptions as before the reception of the Sh-Subs-Notif Request. +8. If the HSS and the AS supports the Notif-Eff feature and if multiple Service-Indication AVPs occur in the Sh-Subs-Notif Request, each Service-Indication shall be treated as a request to establish a separate notification request for change of Transparent data. When multiple notification requests are requested, and all of them are successful, the HSS shall return the Result-Code set to DIAMETER\_SUCCESS in the Sh-Subs-Notify response. If one of them is unsuccessful, the HSS shall return the Result code with the relevant Diameter error value and come back to the situation regarding to subscriptions as before the reception of the Sh-Subs-Notif Request. +- 8a. If the HSS and the AS supports the Notif-Eff feature and if different Identity-Set AVPs occur in the Sh-Subs-Notif Request, each Identity-Set shall be treated as a request to establish a separate notification request. When multiple notification requests are requested, and all of them are successful, the HSS shall return the Result-Code set to DIAMETER\_SUCCESS in the Sh-Subs-Notify response. If one of them is unsuccessful, the HSS shall return the Result code with the relevant Diameter error value and come back to the situation regarding to subscriptions as before the reception of the Sh-Subs-Notif Request. +9. If the Send Data Indication information element is present in the request and the HSS supports the return of the User-Data in this request, check whether or not the data that is requested to be downloaded by the AS is currently being updated by another entity. If there is an update of the data in progress, the HSS may delay the response until the update has been completed. The HSS shall ensure that the data returned is not corrupted by this conflict. +10. If the Send Data Indication information element is present in the request, the HSS should include the data pertinent to the requested Data Reference in the User-Data AVP and if the HSS supports the Notif-Eff feature, the HSS should include the data pertinent to all the requested Data References in the User-Data AVP. The HSS shall set the Result-Code to DIAMETER\_SUCCESS. This includes cases where the data is not available to the HSS and an empty tag is included as follows. + +- Unavailable elements of Sh IMS Data shall be indicated as follows. + - An unavailable S-CSCF name shall be indicated with empty SCSCFName element. + +- If all iFCs for the user that are relevant for the AS are unavailable it shall be indicated with empty IFCs element. +- Similarly for PSI activation information. + +If the HSS cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +### 6.1.4 Notifications (Sh-Notif) + +This procedure is used between the HSS and the AS. The procedure is invoked by the HSS and is used: + +- To inform the AS of changes in transparent and/or non-transparent data to which the AS has previously subscribed to receive Notifications for, using Sh-Subs-Notif (see 6.1.3). + +This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in 3GPP TS 29.329 [5]. Tables 6.1.4.1 and 6.1.4.2 detail the involved information elements. + +**Table 6.1.4.1: Sh-Notif** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------------------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity (See 7.1) | User-Identity | M | IMS Public User Identity or Public Service Identity or MSISDN or External Identifier for which data has changed.
If the request refers to a Wildcarded PSI, the HSS may include any PSI matching the corresponding Wildcarded PSI in this information element. The AS shall find the corresponding Wildcarded PSI with this information. See clause 7.1 for the content of this AVP. | +| Wildcarded PSI (See 7.1A) | Wildcarded-Public-Identity | O | If the request refers to a Wildcarded PSI, the HSS shall include the corresponding Wildcarded PSI in this information element.

If this information element is present, it shall be used by the AS instead of the User Identity to identify the identity affected by the request. If that is the case, the terms User Identity or Public Service Identity in the detailed behaviour refer to the Wildcarded PSI.

If this information element is present, Wildcarded Public User Identity shall not be present. | +| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU | O | If the request refers to a Wildcarded Public User Identity, the HSS shall include the corresponding Wildcarded Public User Identity in this information element.

If this information element is present, it shall be used by the AS instead of the User Identity to identify the identity affected by the request. If that is the case, the terms User Identity or Public User Identity in the detailed behaviour refer to the Wildcarded Public User Identity.

If this information element is present, Wildcarded PSI shall not be present. | +| Data (See 7.6) | User-Data | M | Changed data. | +| Private Identity (see 7.6.19) | User-Name | C | Private Identity of the user for whom the data is required.
This information element shall be present only if the associated request included the Private Identity. | + +**Table 6.1.4.2: Sh-Notif Resp** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|--------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 7.5) | Result-Code /
Experimental-Result | M |

Result of the request.

Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [44]).

Experimental-Result AVP shall be used for Sh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.

| + +#### 6.1.4.1 Detailed behaviour + +The keys to the updated data are part of the information element User-Data AVP. When data repository is updated Service-Indication and Sequence Number shall also be part of the information element User-Data. + +Since authentication pending is a transient state of normally very short duration, notification of an IMS user's state change, to and from the authentication pending state shall not be sent to Application Servers, when the previous state before authentication pending and next state after authentication pending are the same. If the states are different before the authentication pending state is entered and after the authentication pending state is left then notification is sent to the AS of this new state. + +If the HSS and AS supports the Notif-Eff feature and if multiple subscriptions to notifications are associated with a Public User Identity, the HSS may combine the notifications for multiple Data References and Service Indications into a single notification message. + +If the HSS supports the Update-Eff and Notif-Eff features, the HSS may generate only one notification message to be sent to the AS(s) supporting the Notif-eff feature, grouping the data changes notifications according to the subscribed notifications and the resulting successful achievement of a Sh-Update procedure with multiple repository data instances, from an AS that supports the Update-Eff feature. This notification message may also include other notifications as described with the Notif-Eff feature. + +Removal of the subscribed data is indicated with the content of User-Data AVP. The content shall be compliant with the XML-schema defined in Annex D. Removed repository data shall be indicated with RepositoryData element that does not contain ServiceData element. Removed S-CSCF name shall be indicated with empty SCSCFName element. Removed IP Address Secure Binding Information shall be indicated with empty IPv4Addres, or IPv6Prefix and/ or IPv6 interface element respectively. If all iFCs for the user that are relevant for the AS have been removed it shall be indicated with empty IFCs element. + +Removal of Public Identity for which the AS has any active subscription shall be indicated in the DeletedIdentities element. + +If One-Time-Notification AVP was included by the AS in Sh-Subs-Notif, the HSS shall remove the related subscription information after sending Sh-Notif, i.e. no subsequent notifications shall be sent to AS. + +Notifications shall include the data updated for the received IMPU/MSISDN/External Identifier and Private Identity (if present). + +NOTE: Data referred to a Private Identity (e.g. IMS Private User Identity) implies that only the data (e.g. UE reachability) specific for that Private Identity is included, regardless of the type of User Identity received (e.g. IMS Public User Identity shared by multiple IMS Private User Identities). + +Table 6.1.4.1 details the valid result codes that the AS can return in the response. + +**Table 6.1.4.1.1: Sh-Notif response valid result codes** + +| Result-Code AVP value | Condition | +|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| DIAMETER_SUCCESS | The request succeeded. | +| DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED | The request failed. The AS informs the HSS that the received user information contained information, which was not recognized or supported by the AS. | +| DIAMETER_ERROR_USER_UNKNOWN | The request failed because the Public Identity or MSISDN or External Identifier is not found in the AS. | +| DIAMETER_ERROR_TOO_MUCH_DATA | The request failed. The AS informs the HSS that it tried to push too much data into the AS. | +| DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA | The request failed. The AS informs the HSS that the notification refers to information to which the AS is not subscribed. | +| DIAMETER_UNABLE_TO_COMPLY | The request failed. | + +If DIAMETER\_ERROR\_USER\_UNKNOWN is received in the Sh-Notif response, the HSS shall remove all of the subscription to notification information subscribed by the AS related to the specific User Identity. + +## 6.2 AS permissions list + +In table 7.6.1, the contents of the Data-AVP are described. Some of the individual elements carried within Data-AVP may be requested by the AS from the HSS using the Sh-Pull command (see clause 6.1.1) or may be updated at the HSS by the AS using the Sh-Update command (see clause 6.1.2). The AS may also request that the HSS notifies the AS of changes to specific elements within the Data-AVP using the Sh-Subs-Notif command (see clause 6.1.3). The HSS will only allow these operations to take place if the element of the Data-AVP is permitted to be included in the specific command requested by the AS, as indicated in table 7.6.1. + +To manage whether an AS may request each element of Data-AVP with a specific command, the HSS shall maintain a list of AS permissions (the 'AS Permissions List'). AS permissions are identified by AS identity and Data Reference with the possible permissions associated with each Data Reference being Sh-Pull, Sh-Update, Sh-Subs-Notif or any combination of these permissions (see table 7.6.1 for details of which permissions are allowed for each Data Reference). The permissions apply to all users served by the HSS, they are not user specific. When an AS requests Sh-Pull, Sh-Update or Sh-Subs-Notif the HSS shall check permissions and return an error result if the AS does not have the required permission. If the AS permissions change in a later stage, i.e. the AS does not longer have the required permission, the HSS shall remove all the subscription to notifications for the AS for which required permissions have been prohibited. + +## 6.3 Void + +## 6.4 Void + +## 6.5 User identity to HSS resolution + +The User identity to HSS resolution mechanism enables the AS to find the identity of the HSS that holds the subscriber data for a given IMS Public User Identity or Public Service Identity when multiple and separately addressable HSSs have been deployed by the network operator. The resolution mechanism is not required in networks that utilise a single HSS or when an AS is configured to use pre-defined HSS. + +The resolution mechanism described in 3GPP TS 23.228 [1] shall use a Subscription Locator Function (SLF) or a Diameter Proxy Agent. + +The AS accesses the SLF via the Dh interface. The Dh interface shall always be used in conjunction with the Sh interface. The Dh interface shall be based on the Diameter base protocol as specified in IETF RFC 6733 [44]. The SLF functionality shall use the routing mechanism provided by an enhanced Diameter redirect agent. + +The SLF or the Diameter Proxy Agent shall be to determine the HSS identity. + +To get the HSS identity the AS shall send the Sh request normally destined to the HSS to a pre-configured Diameter address/name. + +- If this Sh Request is received by an SLF (acting as a Diameter redirect agent), the SLF shall determine the HSS address and shall send to the AS a notification of redirection towards the HSS identity, in response to the Sh request. Multiple HSS identities may be included in the response, as specified in IETF RFC 6733 [44]. In such a case, the AS shall send the Sh Request to the first HSS identity in the ordered list received in the Sh Response from the SLF. If the AS does not receive a successful response to the Sh Request, the AS shall send a Sh Request to the next HSS identity in the ordered list. This procedure shall be repeated until a successful response from an HSS is received. +- If this Sh Request is received by the Diameter Proxy Agent, the Diameter Proxy Agent shall determine the HSS identity based on the provided user identity and - if the Diameter load control mechanism is supported (see IETF RFC 8583 [43]) - optionally also based on previously received load values from Load AVPs of type HOST. The Diameter Proxy Agent shall then forward the Sh request directly to the determined HSS. The AS shall determine the HSS identity from the response to the Sh request received from the HSS. + +The AS should store the HSS identity/name/Realm and shall use it in further Sh requests associated to the same IMS Public Identity. + +In networks where the use of the user identity to HSS resolution mechanism is required and the AS is not configured to use a predefined HSS, each AS shall be configured with the pre-configured address/name of the SLF or the Diameter Proxy Agent to enable use of these resolution mechanisms. + +# 7 Information element contents + +## 7.1 User Identity + +This information element contains an IMS Public User Identity, Public Service Identity, MSISDN or External Identifier according to the conditions described in table 7.1.1. + +**Table 7.1.1: User Identity content** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------------------------------------|-------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMS Public User Identity / Public Service Identity (See 7.1.1) | Public-Identity | C | IMS Public User Identity or Public Service Identity for which data is required. If the MSISDN and External Identifier are not included in the User-Identity AVP, the Public-Identity AVP shall be included in Sh messages only for allowed Data References as described in Table 7.6.1. | +| MSISDN (See 7.1.2) | MSISDN | C | MSISDN for which data is required. If the Public-Identity AVP and External Identifier are not included in the User-Identity AVP, the MSISDN AVP shall be included in the Sh-Pull or Sh-Subs-Notif or Sh-Update messages only for allowed Data References as described in Table 7.6.1. | +| External Identifier (See 7.1.3) | External-Identifier | C | External Identifier for which data is required. If the Public-Identity AVP and MSISDN are not included in the User-Identity AVP, the External Identifier AVP shall be included in the Sh-Pull or Sh-Subs-Notif or Sh-Update messages only for allowed Data References as described in Table 7.6.1. | + +### 7.1.1 IMS Public User Identity / Public Service Identity + +This information element contains an IMS Public User Identity / Public Service Identity (either SIP URI or tel URI). See 3GPP 23.003 [11]. + +### 7.1.2 MSISDN + +This information element contains the MSISDN, or the Basic MSISDN if multnumbering is used (see 3GPP TS 23.012 [19]). + +### 7.1.3 External Identifier + +This information element contains the External Identifier (see 3GPP TS 23.003 [11]). + +### 7.1A Wildcarded PSI + +This information element contains a Wildcarded PSI that is hosted by an application server. For definition of a Wildcarded PSI, see 3GPP TS 23.003 [11]. + +### 7.1B Wildcarded Public User Identity + +This information element contains a Wildcarded Public User Identity that is stored in the HSS. For definition of a Wildcarded Public User Identity, see 3GPP TS 23.003 [11]. + +## 7.2 Requested Domain + +This information element details the access domains for which certain data (e.g. user state, location information) are requested. See 3GPP TS 29.329 [5] for the list of possible values. + +### 7.2A Requested Nodes + +This information element details the access node types for which certain data (e.g. user state, location information) are requested. See 3GPP TS 29.329 [5] for the list of possible values. + +### 7.2B Serving Node Indication + +This information element indicates that the sender does not require any location information other than the serving node address/identity (i.e. MME name and/or SGSN number and/or AMF address, or VLR number) for the requested domain and the requested nodes (if included). Other location information (e.g. Global Cell ID, Tracking Area ID) may be absent. + +This information element is only applicable to Location Information. + +## 7.3 Requested Data + +- Reference to the data that an AS is requesting from the HSS. +- Reference to the data which, an AS wants to be notified of, when changed. +- Reference to data for which subscription to notification of change is rejected. +- Reference to data for which updates are required. +- Reference to data for which update fails. + +See clause 7.6. + +## 7.4 Service Indication + +Identifier of one set of service related transparent data, which is stored in an HSS in an operator network per Public Identity. The HSS shall allocate memory space to implement a data repository to store transparent data per IMS Public User Identity or Public Service Identity and value of Service Indication with a Sequence Number for verification. For Public Service Identities matching a Wildcarded Public Service Identity, the repository data shall be stored per Wildcarded Public Service Identity and not for each specific Public Service Identity. + +## 7.5 Result + +This information element contains the result code of the operation. See 3GPP TS 29.329 [5] for the list of possible values. + +## 7.6 Data + +This information element contains an XML document conformant to the XML schema defined in Annex D. + +Annex C specifies the UML logical model of the data downloaded via the Sh interface. + +Table 7.6.1 defines the data reference values and tags, access key and recommended AS permissions (as described in clause 6.2) for the operation(s) on data accessible via the Sh interface, i.e. the listed operation(s) in the Operations column are the only ones allowed to be used with this Data Ref value. It is a matter of operator policy to further restrict the AS permission rights defined in table 7.6.1. + +An access key between square brackets is considered as optional, while when more than one access key is separated by logical OR and included between brackets, it means that one (and only one) of these access keys is mandatory. + +Table 7.6.1: Data accessible via Sh interface + +| Data Ref. | XML tag | Defined in | Access key | Operations | +|-----------|---------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| +| 0 | RepositoryData | 7.6.1 | Data Reference
+ ( IMS Public User Identity OR Public Service Identity )
+ Service Indication | Sh-Pull
Sh-Update
Sh-Subs-Notif
(Note 1, Note 3) | +| 10 | IMSPublicIdentity | 7.6.2 | Data Reference
+ ( IMS Public User Identity OR Public Service Identity OR MSISDN OR External Identifier )
+ [ Requested Identity Set ] | Sh-Pull
Sh-Subs-Notif | +| 11 | IMSUserState | 7.6.3 | Data Reference
+ IMS Public User Identity | Sh-Pull
Sh-Subs-Notif | +| 12 | S-CSCFName | 7.6.4 | Data Reference
+ ( IMS Public User Identity OR Public Service Identity ) | Sh-Pull
Sh-Subs-Notif
(Note 1) | +| 13 | InitialFilterCriteria | 7.6.5 | Data Reference
+ ( IMS Public User Identity OR Public Service Identity )
+ Application Server Name | Sh-Pull
Sh-Subs-Notif
(Note 1) | +| 14 | LocationInformation | 7.6.6 | Data Reference
+ ( IMS Public User Identity OR MSISDN OR External Identifier )
+ [ Private Identity ]
+ Requested Domain
+ Current Location
+ [ Serving Node Indication ]
+ [ Requested Nodes ]
+ [ Local Time Zone Indication ]
+ [ RAT-Type Requested ] | Sh-Pull
(Note 5)
(Note 6)
(Note 7)
(Note 10) | +| 15 | UserState | 7.6.7 | Data Reference
+ ( IMS Public User Identity OR MSISDN OR External Identifier )
+ [ Private Identity ]
+ Requested Domain
+ [ Requested Nodes ] | Sh-Pull
(Note 5)
(Note 7) | +| 16 | Charging information | 7.6.8 | Data Reference
+ ( IMS Public User Identity OR Public Service Identity OR MSISDN OR External Identifier ) | Sh-Pull
Sh-Subs-Notif | +| 17 | MSISDN or MSISDN +ExtendedMSISDN | 7.6.9 | Data Reference
+ ( IMS Public User Identity OR MSISDN OR External Identifier )
+ [ Private Identity ] | Sh-Pull
(Note 4) | +| 18 | PSIActivation | 7.6.10 | Data Reference
+ IMS Public Service Identity | Sh-Pull
Sh-Update
Sh-Subs-Notif
(Note 1) | +| 19 | DSAI | 7.6.11 | Data Reference
+ ( IMS Public User Identity OR Public Service Identity )
+ DSAI Tag
+ Application Server Name | Sh-Pull
Sh-Update
Sh-Subs-Notif
(Note 1) | +| 20 | Reserved | | | | +| 21 | ServiceLevelTraceInfo | 7.6.13 | Data Reference
+ ( IMS Public User Identity OR MSISDN OR External Identifier ) | Sh-Pull
Sh-Subs-Notif | +| 22 | IP Address Secure Binding Information | 7.6.14 | Data Reference
+ IMS Public User Identity | Sh-Pull
Sh-Subs-Notif | +| 23 | Service Priority Level | 7.6.15 | Data Reference
+ ( IMS Public User Identity OR MSISDN OR External Identifier ) | Sh-Pull
Sh-Subs-Notif | +| 24 | SMSRegistrationInfo | 7.6.16 | Data Reference
+ ( IMS Public User Identity OR MSISDN OR External Identifier )
+ [ Private Identity ] | Sh-Pull
Sh-Update
(Note 5) | +| 25 | UE reachability for IP | 7.6.17 | Data Reference
+ ( IMS Public User Identity OR MSISDN OR External Identifier )
+ [ Private Identity ] | Sh-Subs-Notif
(Note 5) | +| 26 | T-ADS Information | 7.6.18 | Data Reference
+ ( IMS Public User Identity OR MSISDN )
+ [ Private Identity ] | Sh-Pull
(Note 5) | + +| | | | | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------------------------------------------------------------------------------------------------------------|--------------------------------------| +| 27 | STN-SR | 7.6.20 | Data Reference
+ ( IMS Public User Identity OR MSISDN )
+ [ Private Identity ] | Sh-Pull
Sh-Update
(Note 5) | +| 28 | UE-SRVCC-Capability | 7.6.21 | Data Reference
+ ( IMS Public User Identity OR MSISDN )
+ [ Private Identity ] | Sh-Pull
Sh-Subs-Notif
(Note 5) | +| 29 | ExtendedPriority | 7.6.15A | Data Reference
+ ( IMS Public User Identity OR MSISDN OR
External Identifier) | Sh-Pull
Sh-Subs-Notif | +| 30 | CSRN | 7.6.22 | Data Reference
+ ( IMS Public User Identity OR MSISDN )
+ [ Private Identity ] | Sh-Pull
(Note 5) | +| 31 | Reference Location Information | 7.6.23 | Data Reference
+ IMS Public User Identity
+ [ Private Identity ] | Sh-Pull
(Note 5) | +| 32 | IMSI | 7.6.24 | Data Reference
+ ( IMS Public User Identity OR MSISDN OR
External Identifier )
+ [ Private Identity ] | Sh-Pull
(Note 5)
(Note 8) | +| 33 | IMSPrivateUserIdentity | 7.6.25 | Data Reference
+ IMS Public User Identity | Sh-Pull
Sh-Subs-Notif
(Note 8) | +| 34 | IMEISV | 7.6.26 | Data Reference
+ ( IMS Public User Identity OR MSISDN OR
External Identifier )
+ [ Private Identity ] | Sh-Pull
Sh-Subs-Notif
(Note 5) | +| 35 | UE-5G-SRVCC-Capability | 7.6.21A | Data Reference
+ ( IMS Public User Identity OR MSISDN )
+ [ Private Identity ] | Sh-Pull
Sh-Subs-Notif
(Note 5) | +| Note 1: | If an AS subscribes to a Specific PSI matching a Wildcarded PSI, the notification shall be sent as if the subscription was made to the corresponding Wildcarded PSI.
If an AS requires reading for a Specific PSI matching a Wildcarded PSI, the response shall be sent as if the request was made to the corresponding Wildcarded PSI. | | | | +| Note 2: | If not specified otherwise Public User Identity and Public Service Identity refer also to the wildcarded identities. | | | | +| Note 3: | Any IMS Public User Identity in an Alias Public User Identity Set may be used as a key for the repository data of the group. All IMS Public User Identities within the same set shall be considered alias of each other and shall share the same transparent data. See 3GPP TS 23.008 [27] for the definition of an Alias Public User Identity Set. | | | | +| Note 4: | If several MSISDNs are associated to the Public identity, an AS shall be required to indicate the IMS Private User Identity to fetch the C-MSISDN. See 3GPP TS 23.003 [11] and 3GPP TS 23.237 [32] for the definition of C-MSISDN. ExtendedMSISDN is returned in addition to MSISDN when Additional-MSISDN feature is enabled | | | | +| Note 5: | If a Sh procedure refers to a specific Private Identity within a set of multiple Private identities associated to an IMS Public User Identity or MSISDN, the corresponding Sh request shall include this Private Identity as part of the access key. | | | | +| Note 6: | Serving Node Indication is optionally included only if Current Location takes the value DoNotNeedInitiateActiveLocationRetrieval | | | | +| Note 7: | Requested Nodes is only applicable when Requested Domain is PS | | | | +| Note 8: | IMSI and IMS Private User Identity may be considered sensitive data, which not all ASs may be permitted to retrieve. See clause 6.2. | | | | +| Note 9: | If Data Reference and External Identifier are used as access key, Private Identity is not applicable as additional access key. | | | | +| Note 10: | Local-Time-Zone-Indication shall be absent or shall take the value LOCAL_TIME_ZONE_WITH_LOCATION_INFO_REQUESTED (1) if Current Location takes the value InitiateActiveLocationRetrieval (1) | | | | + +### 7.6.1 Repository Data + +This information element contains transparent data. A data repository may be shared by more than one AS implementing the same service. + +### 7.6.2 IMSPublicIdentity + +This data contents included in the Sh-Pull Resp, Sh-Subs-Notif Resp or Sh-Notif depends on whether Requested Identity Set information element was included in the Sh-Pull or Sh-Subs-Notif, as follows: + +- When this information element takes the value IMPLICIT\_IDENTITIES, the HSS shall provide all non-barred IMS Public Identities that belong to the same implicit registration set as the IMS Public Identity included in the message in the User-Identity AVP. The MSISDN and External Identifier within the User-Identity AVP are not applicable for this value. If the User Identity is a Public Service Identity, the HSS shall return only the User Identity received in the request. + +- When this information element takes the value ALIAS\_IDENTITIES, the HSS shall provide all non-barred IMS Public User Identities that are in the same Alias Public User Identity Set as the IMS Public User Identity included in the message in the User-Identity AVP (see 3GPP TS 23.008 [27] for the definition of Alias Public User Identity Set). The MSISDN, the Public Service Identity and the External Identifier within the User-Identity AVP are not applicable for this value. +- When this information element takes the value REGISTERED\_IDENTITIES, the HSS shall provide all non-barred IMS Public Identities whose state is registered, belonging to all Private Identities that the IMS Public Identity or MSISDN or External Identifier in the User-Identity AVP is associated with. If the User Identity is a Public Service Identity, the HSS shall return no identities in the response. +- When this information element takes the value ALL\_IDENTITIES, the HSS shall provide all non-barred IMS Public Identities, belonging to all Private Identities that the User Identity is associated with. +- When this information element is not included, the HSS shall download the set of IMS Public Identities that would be downloaded if the value of this information element had been ALL\_IDENTITIES. + +An IMS Public Identity would be either: + +- associated with the same Private User Identity or Private Service Identity as the User Identity included in the request or +- associated with the MSISDN present in the request or +- associated with an External Identifier present in the request. + +Multiple instances of this information element may be included in the message. + +### 7.6.3 IMS User State + +This information element contains the IMS User State of the public identifier referenced. Its possible values are: + +- REGISTERED, +- NOT\_REGISTERED, +- AUTHENTICATION\_PENDING, +- REGISTERED\_UNREG\_SERVICES. + +If the IMS Public User Identity is shared between multiple Private User Identities, HSS shall indicate the most registered state of the shared IMS Public User Identity to an AS. The most registered state of a shared IMS Public User Identity is defined as follows: + +- If the shared IMS Public User Identity is registered with any of the Private User Identities, the most registered state of the shared IMS Public User Identity is REGISTERED. +- If the shared IMS Public User Identity is not currently registered with any of the Private User Identities, but it is in state REGISTERED\_UNREG\_SERVICES, then the most registered state of the shared IMS Public User Identity is REGISTERED\_UNREG\_SERVICES. +- If the shared IMS Public User Identity is not currently registered with any of the Private User Identities, and it is not in state REGISTERED\_UNREG\_SERVICES, but it is in the process of being authenticated with any of the Private User Identities, then the most registered state of the shared IMS Public User Identity is AUTHENTICATION\_PENDING. +- If the shared IMS Public User Identity is not currently registered with any of the Private User Identities, and it is not in state REGISTERED\_UNREG\_SERVICES, and it is not in the process of being authenticated with any of the Private User Identities, then the most registered state of the shared IMS Public User Identity is NOT\_REGISTERED. + +### 7.6.4 S-CSCF Name + +This information element contains the name of the S-CSCF assigned to the IMS Subscription. + +### 7.6.5 Initial Filter Criteria + +This information element contains the triggering information for a service. + +For a more detailed description, refer to 3GPP TS 23.218 [4] and 3GPP TS 29.228 [6]. + +### 7.6.6 Location Information + +This information element contains either: + +- the location of the served subscriber in the MSC/VLR if the requested domain is CS, or +- the location of the served subscriber in the SGSN if the requested domain is PS and either the requested node is solely SGSN or the requested node is not present, or +- the location of the served subscriber in the MME if the requested domain is PS and the requested nodes is solely MME, or +- the locations of the served subscriber in the 3GPP AAA Server for TWAN if the requested domain is PS and the requested nodes is solely 3GPP AAA SERVER for TWAN, or +- the location of the served subscriber in the AMF (for 3GPP access) if the requested domain is PS and the requested nodes is solely AMF. +- the locations of the served subscriber in the MME and the SGSN and 3GPP AAA Server for TWAN and AMF if the requested domain is PS and the requested nodes are all of MME and SGSN and 3GPP AAA SERVER for TWAN and AMF, or +- the locations of the served subscriber in any of the two or three serving nodes among the MME, the SGSN, the 3GPP AAA Server for TWAN and the AMF if the requested domain is PS and the requested nodes indicates the corresponding nodes for which the location are to be requested. + +If the HSS has to communicate with the MSC/VLR or SGSN and/or MME and/or 3GPP AAA Server and/or AMF (via UDM) to retrieve location information, it shall make use of the service MAP-PROVIDE-SUBSCRIBER-INFO or S6a/S6d-IDR or SWx-PPR or make use (via UDM) of the Namf Service-Based Interface services. This information element shall contain the location information as received from the access nodes. + +If the HSS or HSS/UDM cannot communicate with the VLR or SGSN or MME or AMF (e.g., because the UE is purged), or if the HSS or HSS/UDM cannot retrieve the location information from the serving nodes because they do not support such feature, the HSS shall provide locally stored location information if available (e.g., serving node name, Visited PLMN ID) received in a previous Update Location message, and the last known UE's location if available e.g. as received in the Purge message from VLR or SGSN or MME or AMF. + +If the Serving Node Indication was present in the request, the location information shall contain the serving node address(es) as stored in the HSS, according to the requested domain and the requested nodes (if received). Other location information may be absent, in order to eliminate unnecessary communication with the MSC/VLR or SGSN and/or MME and/or 3GPP AAA Server and/or AMF when the AS does not require these information elements. + +For both Location Information for CS and Location Information for GPRS, the considerations described in 3GPP TS 23.078 [14] apply. + +#### 7.6.6.1 Location information for CS + +This information element consists of the following subordinate information elements: + +- Location number: defined in ITU-T Recommendation Q.763 [9]. Considerations described in 3GPP TS 23.018 apply [10]. +- Service area ID: defined in 3GPP TS 23.003 [11]. +- Cell Global ID: defined in 3GPP TS 23.003 [11]. +- Location area ID: defined in 3GPP TS 23.003 [11]. + +- Geographical Information: defined in 3GPP TS 23.032 [12]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply. +- Geodetic Information: defined in ITU-T Recommendation Q.763 [9]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply. +- VLR Number: defined in 3GPP TS 23.003 [11]. +- MSC Number: defined in 3GPP TS 23.003 [11]. +- Age of location information: defined in 3GPP TS 23.018 [10]. +- Current Location Retrieved: shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval if the MS is in idle state or when the location was provided if the MS is in active state. +- User CSG information: defined in 3GPP TS 23.060 [29]. +- E-UTRAN Cell Global ID: defined in 3GPP TS 23.003 [11]. +- Tracking Area ID: defined in 3GPP TS 23.003 [11]. +- Local Time Zone: the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26]. + +NOTE: When the MSC receives the location information via SGs interface as specified in 3GPP TS 29.118 [30], the E-UTRAN Cell Global ID and Tracking Area ID are included, rather than Location number, Service area ID, Cell Global ID and Location area ID. + +#### 7.6.6.2 Location information for GPRS + +This information element consists of the following subordinate information elements: + +- Service area ID: defined in 3GPP TS 23.003 [11]. +- Cell Global ID: defined in 3GPP TS 23.003 [11]. +- Location area ID: defined in 3GPP TS 23.003 [11]. +- Geographical Information: defined in 3GPP TS 23.032 [12]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply. +- Geodetic Information: defined in ITU-T Recommendation Q.763 [9]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply. +- SGSN Number: defined in 3GPP TS 23.003 [11]. +- Routing Area ID: defined in 3GPP TS 23.003 [11]. +- Current Location Retrieved: shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval if the UE is in idle mode or when the location was provided if the UE is in connected mode. +- Age of location information: defined in 3GPP TS 23.018 [10]. +- User CSG information: defined in 3GPP TS 23.060 [29]. +- Visited PLMN ID: defined in 3GPP TS 23.003 [11]. +- Local Time Zone: the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26]. +- RAT type: the possible values of RAT type are specified in 3GPP TS 29.212 [28], clause 5.3.31. + +#### 7.6.6.3 Location information for EPS + +This information element consists of the following subordinate information elements: + +- E-UTRAN Cell Global ID: defined in 3GPP TS 23.003 [11]. +- Geographical Information: defined in 3GPP TS 23.032 [12]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply. +- Geodetic Information: defined in ITU-T Recommendation Q.763 [9]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply. +- MME Name: Diameter Identity of the MME as received by the HSS within the S6a ULR Origin-Host AVP; see 3GPP TS 29.272 [31]. +- Tracking Area ID: defined in 3GPP TS 23.003 [11]. +- Current Location Retrieved: shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval if the UE is in idle mode or when the location was provided if the UE is in connected mode. +- Age of location information: defined in 3GPP TS 23.018 [10]. +- Visited PLMN ID: defined in 3GPP TS 23.003 [11]. +- User CSG information: defined in 3GPP TS 23.060 [29]. +- Local Time Zone: the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26]. . +- RAT type: the possible values of RAT type are specified in 3GPP TS 29.212 [28], clause 5.3.31. + +#### 7.6.6.4 Location Information for TWAN + +This information element consists of the following subordinate information elements: + +- TWAN SSID: defined in 3GPP TS 29.273 [34]. +- TWAN BSSID: defined in 3GPP TS 29.273 [34]. +- TWAN PLMN ID: defined in clause 12.1 of 3GPP TS 23.003 [11] for PLMN Identifier. +- Civic Address: defined in clause 3.1 of IETF RFC 4776 [35] excluding the first 3 octets. +- TWAN Operator Name: defined in clause 19.8 of 3GPP TS 23.003 [11]. +- Local Time Zone: the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26]. +- Logical Access ID defined in ETSI ES 283 034 [37]. + +NOTE: The location information defined for EPS in clause 7.6.6.3 is not relevant to the TWAN location information. + +#### 7.6.6.5 Location Information for 5GS + +This information element consists of the following subordinate information elements: + +- NR Cell Global ID: defined in 3GPP TS 23.003 [11]. +- E-UTRAN Cell Global ID: defined in 3GPP TS 23.003 [11]. +- Geographical Information: defined in 3GPP TS 23.032 [12]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply. +- AMF Address: Identity of the serving AMF (for 3GPP access). + +- SMSF Address: Identity of the serving SMSF (for 3GPP access). +- Tracking Area ID: defined in 3GPP TS 23.003 [11] clauses 19.4.2.3 and 28.6. +- Current Location Retrieved: shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval if the UE is in idle mode or when the location was provided if the UE is in connected mode. +- Age of location information: defined in 3GPP TS 23.018 [10]. +- Visited PLMN ID: defined in 3GPP TS 23.003 [11]. +- Local Time Zone: Time zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26]. +- RAT type: the possible values of RAT type are specified in 3GPP TS 29.212 [28], clause 5.3.31. + +### 7.6.7 User state + +This information element indicates the state of the User Identity in the domain/node indicated by the Requested-Domain/Requested-Node (see 7.2), with the values specified in 3GPP TS 23.078 [14] for Subscriber State and PS Domain Subscriber State, and with the values specified in 3GPP TS 29.272 [31] for EPS User State and 3GPP TS 29.518 [47] for the 5GS User State. + +- The HSS shall make use of the operation MAP-PROVIDE-SUBSCRIBER-INFO towards the MSC/VLR to obtain this information if the requested domain is CS. +- The HSS shall make use of the operation S6a-IDR towards the MME to obtain this information if the requested domain is PS and the requested node is MME. +- The HSS shall make use of the operation MAP-PROVIDE-SUBSCRIBER-INFO or S6d-IDR towards the SGSN to obtain this information if the requested domain is PS and either the requested node is SGSN or the requested node is not present. +- The HSS shall make use of the operation S6a-IDR towards the MME and MAP-PROVIDE-SUBSCRIBER-INFO or S6d-IDR towards the SGSN to obtain this information if the requested domain is PS and the Requested Nodes is MME and SGSN. +- The UDM+HSS shall make use of the Namf\_EventExposure Subscribe Service Operation towards the AMF to obtain this information if the requested domain is PS and the requested node is AMF. + +This information element shall contain the information as received from the access nodes. The UDM+HSS may retrieve the User States from the MME, SGSN or AMF within one procedure. + +The UDM+HSS shall include the value "NotProvidedFromSGSN or MME or AMF" in the "EPSUserState" / "PSUserState" / "Sh-5GSUserState" fields, if the MME, SGSN or AMF does not support the retrieval of User State over S6a/S6d-IDR/ Namf\_EventExposure Service, or it did not provide any information on subscriber state even though it was requested by UDM+HSS. + +The UDM+HSS shall include the value "Detached" in the "EPSUserState" / "PSUserState" / "Sh-5GSUserState" fields, if the MME, SGSN or AMF is marked as purged in the UDM+HSS. + +### 7.6.8 Charging information + +This information element contains the addresses of the charging functions: primary Online Charging Function (PrimaryEventChargingFunctionName), secondary Online Charging Function (SecondaryEventChargingFunctionName), primary Charging Data Function (PrimaryChargingCollectionFunctionName), and secondary Charging Data Function (SecondaryChargingCollectionFunctionName). When a clash occurs between the charging function address(es) received over the ISC interface and those received over the Sh interface, the address(es) received over the ISC interface should take precedence. + +NOTE: The use of the Sh interface to retrieve charging function addresses is not intended as a general-purpose alternative to receiving charging function addresses from the ISC interfaces. Rather, it is meant to address a special case where the AS needs to interact with the charging system before initiating a request to a user when the AS has not received the third party REGISTER for that user. + +The AS shall extract the FQDN of the DiameterURI in these information elements and may use it as content of the Destination-Host AVP for the Diameter accounting requests. The parent domain of the FQDN in the DiameterURI shall be used as Destination-Realm. The number of labels used for the Destination-Realm shall be determined before the Charging Information is provisioned and may be a configuration option. + +NOTE: A FQDN is an absolute domain name including a subdomain and its parent domain. The subdomain and the parent domain contain one or more labels separated by dots. + +### 7.6.9 MSISDN + +This information element contains the MSISDN, or the Basic MSISDN if multnumbering is used, that is associated with the User Identity present in the request. See 3GPP TS 23.012 [19] for Basic MSISDN definition. + +Multiple instances of this information element shall only occur if the Public User Identity is shared and no Private Identity was included in the request, otherwise only one instance shall be included in the message. + +If Additional-MSISDN feature is supported by the HSS but the AS has indicated that it does not support it, it is up to operator policy to decide what information is returned by the HSS, either what is provisioned in MSISDN or in Additional MSISDN (A-MSISDN). + +#### 7.6.9A Extended MSISDN + +This information element is returned in addition to MSISDN if Additional-MSISDN feature is supported by the HSS, the AS has indicated as well its support and an Additional MSISDN (A-MSISDN) is provisioned.. + +It contains the Additional-MSISDN that is associated with the User Identity present in the request. + +All valid instances of this information element shall be included in the message. + +### 7.6.10 PSIActivation + +This information element contains the activation state of the Public Service Identity present in the request. Its possible values are: + +- ACTIVE, +- INACTIVE. + +### 7.6.11 DSAI + +When a service is provisioned but not active, an Application Server is typically involved through the ISC interface in sessions where the Application Server is not supposed to perform any task but to proxy incoming transactions. + +In order to avoid this disoptimization, a mechanism is provided for the Application Server to signal the HSS that a set of initial filter criteria should be "masked" for a specific Public User Identity or Public Service Identity. This is, from the Application Server's perspective, just an indication, and an Application Server must be prepared to be involved in sessions even if the trigger that caused its involvement has been masked by that Application Server. + +This information element contains the activation state of a Service (identified by its DSAI-tag, see clause 7.14, for a specific user identified by a Public User Identity or of a Service identified by its PSI). Its possible values are: + +- ACTIVE, +- INACTIVE. + +In the HSS the DSAI can also be associated to a wildcarded PSI. In that case, there is a set of identities matching a specific wildcarded PSI and all the identities in the set share the same DSAIs. Any change in these DSAIs masked from a single identity of the set will apply to all the identities associated to that wildcarded PSI. + +Each DSAI is implicitly bound to a list of (at least one) initial filter criteria. The binding is not exclusive, i.e. one instance of initial filter criteria may be bound to zero or more DSAIs, however all the iFCs bound to a given DSAI should trigger to the same AS (i.e. they should share the same ServerName), which is the only one allowed to update it. + +An instance of initial filter criteria shall be included into the Service-Profile sent through the Cx Interface according to the operations described in 3GPP TS 29.228 [6] if at least one of the following conditions applies: + +- No DSAI is bound to those initial filter criteria; +- At least one of the DSAIs bound to those initial filter criteria is set to ACTIVE. + +### 7.6.12 Void + +### 7.6.13 Service Level Trace Information + +This information element contains the Service Level Tracing Information (see 3GPP TS 24.323 [45]) that is related to a specific Public Identifier. If the ServiceLevelTraceInfo is present, service level tracing shall be enabled in the Application Server for the related Public Identifier according to the configuration data received. If the ServiceLevelTraceInfo is not present, service level tracing is disabled in the Application Server for the related Public Identifier. + +### 7.6.14 IP address secure binding information + +This information element contains the IP address (or the prefix in the case of IPv6 stateless autoconfiguration) at any given time. See 3GPP TS 33.203 [22], Annex T. + +### 7.6.15 Service Priority Level + +This information element contains the Priority Level allowed for Priority Service. If the ServicePriority Level is present, priority services are allowed. See IETF RFC 4412 [25]. + +#### 7.6.15A Extended Priority + +This information element contains the following information elements: + +- The PriorityNamespace information element provides the namespace as specified in IETF RFC 4412 [25] and to which the Extended Priority refers. +- The PriorityLevel information element provides the Priority Level allowed for a given PriorityNamespace. + +### 7.6.16 SMSRegistrationInfo + +This information element contains an IP-SM-GW number and the address of a Short Message Service Centre. For the definition of an IP-SM-GW number and Service Centre Address, see 3GPP TS 23.008[27]. + +If the IP-SM-GW supports SBI-based MT SM transmit, the "SBI support indication" of the IP-SM-GW should be included in the SMSRegistrationInfo. + +### 7.6.17 UE reachability for IP + +This information element reflects the change of URRP-MME and/or URRP-SGSN parameters and indicates whether the UE has become reachable, i.e. when the URRP-MME and/or URRP-SGSN parameters was set and has been cleared due to UE activity notification from the MME and/or the SGSN, see 3GPP TS 29.272 [26]. + +This information element also indicates whether the UE has become reachable at the AMF for 3GPP access and/or at the AMF for non 3GPP access. + +It consists of the following subordinate information elements: + +- UE-IP-REACHABILITY-MME. Its possible values are: + - REACHABLE (0) +- UE-IP-REACHABILITY-SGSN. Its possible values are: + - REACHABLE (0) +- UE-IP-REACHABILITY-AMF-3GPP. Its possible values are: + - REACHABLE (0) +- UE-IP-REACHABILITY-AMF-NON-3GPP. Its possible values are: + - REACHABLE (0) + +### 7.6.18 T-ADS Information + +This information element indicates the RAT type that is serving the UE and whether or not IMS voice over PS Session is supported at the current Routing Area/Tracking Area. + +The HSS shall make use of the appropriate S6a operation towards the MME and/or S6d/MAP operation towards the SGSN to retrieve the T-ADS information. The UDM/HSS shall make use of appropriate Namf service operation towards the AMF to retrieve the T-ADS information. + +The possible values for IMS voice over PS Session support are: + +- IMS-VOICE-OVER-PS-NOT-SUPPORTED (0) +- IMS-VOICE-OVER-PS-SUPPORTED (1) +- IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN (2) + +The possible values of RAT type are specified in 3GPP TS 29.212 [28], clause 5.3.31. + +### 7.6.19 Private Identity + +This information element contains the IMS Private User Identity or the IMSI. See 3GPP TS 23.003 [17]). + +### 7.6.20 STN-SR + +This information element indicates the Session Transfer Number for SRVCC or 5G-SRVCC (see 3GPP TS 23.003 [11]). + +When STN-SR is updated, the HSS shall make use of the service S6a/S6d-IDR to update the STN-SR in the MME/SGSN and, if the HSS supports interworking with the UDM (see in 3GPP TS 23.632 [48]), the UDM shall make use of the Nudm\_MT\_Update operation to update the STN-SR in the AMF. + +### 7.6.21 UE SRVCC Capability + +This information element indicates the SRVCC capability of the UE. + +The possible values for the UE-SRVCC capability are: + +- UE-SRVCC-CAPABILITY-NOT-SUPPORTED (0) +- UE-SRVCC-CAPABILITY-SUPPORTED (1) + +#### 7.6.21A UE 5G SRVCC Capability + +This information element indicates the 5G SRVCC capability of the UE. + +The possible values for the UE-5G-SRVCC capability are: + +- UE-5G-SRVCC-CAPABILITY-NOT-SUPPORTED (0) +- UE-5G-SRVCC-CAPABILITY-SUPPORTED (1) + +### 7.6.22 CSRN + +This information element contains a CS Domain Routeing Number (see 3GPP TS 23.003) associated to the user identity of the request. + +The HSS shall make use of the operation MAP-PROVIDE-ROAMING-NUMBER towards the MSC/VLR to obtain this information and shall indicate the Suppression of Announcement to the MSC/VLR. + +This information element is requested by AS when all terminating services have been already executed, then HSS is only interested in the CSRN received from MSC/VLR. + +### 7.6.23 Reference Location Information + +This information element contains the reference location of the user, e.g. the physical location of the fixed line in the case of a fixed line access, that is associated with the User Identity and Private Identity (if present) in the request. See 3GPP TS 23.008 [27]. + +### 7.6.24 IMSI + +This information element contains the IMSI that is associated with the IMS Public User Identity present in the request. See 3GPP TS 23.003 [11] for IMSI definition. + +### 7.6.25 IMSPrivateUserIdentity + +This information element contains all IMS Private User Identities associated with the IMS Public User Identity present in the request. See 3GPP TS 23.003 [11] for Private User Identity definition. + +### 7.6.26 IMEISV + +This information element contains the IMEI or IMEISV (see 3GPP TS 23.003 [11]) of the UE employed by the user identity of the request, during the attach to the access network. + +## 7.7 Subscription request type + +This information element indicates the action requested for subscription to notifications. See 3GPP TS 29.329 [5] for the list of valid values. + +## 7.8 Current Location + +This information element indicates whether an active location retrieval has to be initiated or not when an AS requested location information. See 3GPP TS 29.329 [5] for the list of possible values. + +## 7.9 Application Server Identity + +This information element contains the identity of the Application Server. It is used for the AS permission check (see 6.2). + +## 7.10 Application Server Name + +This information element indicates application server's SIP URI. See 3GPP TS 29.229 [7] for the detailed definition of the AVP. + +## 7.11 Requested Identity Set + +This information element indicates the set of IMS Public Identities that the AS wishes to download. See 3GPP TS 29.329 [5] for the detailed definition of the AVP. + +## 7.12 Expiry Time + +This information element indicates the expiry time of the subscription to notifications in the HSS. See 3GPP TS 29.329 [5] for the detailed definition of this AVP. + +## 7.13 Send Data Indication + +This information element indicates the request that the User Data is sent in the response. See 3GPP TS 29.329 [5] for the detailed definition of this AVP. + +## 7.14 DSAI Tag + +An instance of Dynamic Service Activation Info is uniquely identified by the Public User/Service Identity and a DSAI tag. The same DSAI tag may be used for all the user profiles when indicating the same type of information, but not all the user profiles may contain the same set of tags. + +Application Servers shall signal that they are not interested in being involved in new sessions by manipulating Dynamic Service Activation Info (DSAI) inside of dynamic service information data, see clause 7.6.11. + +## 7.15 Session-Priority + +This information element indicates the session's priority level to the HSS. See 3GPP TS 29.229 [7]. + +## 7.16 One Time Notification + +This information element indicates that the sender requests to be notified only one time. After the notification, the HSS shall remove the subscription. See 3GPP TS 29.329 [5] for the list of possible values. + +## 7.17 Repository Data ID + +This information element includes the service indication and the sequence number of a repository data. See 3GPP TS 29.329 [5] for the detailed definition of this AVP. + +## 7.18 Pre-paging Supported + +This information element indicates whether Pre-paging is supported by the AS. See 3GPP TS 29.329 [5] for the detailed definition of this AVP. + +## 7.19 Local Time Zone Indication + +This information element indicates that the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached for the requested domain and the requested nodes (if included) is requested and indicates whether only the Local Time Zone is required or the Local Time Zone is required together + +with other location data. If only the Local Time Zone is required, other location information (e.g. Global Cell ID, Tracking Area ID) may be absent. + +This information element is only applicable to Location Information. + +## 7.20 UDR Flags + +This information element carries the following indications (see 3GPP 29.329 [5] for coding details): + +Table 7.20/1: UDR Flags + +| Name | Description | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location-Information-EPS-Supported | Location Information EPS Supported shall be only applicable if CS Location Information is requested.
It indicates that EPS Location Information may be sent to the AS when CS Location Information is requested.
When set, the HSS shall indicate to the MSC/VLR the support of Location Information EPS. | +| RAT-Type-Requested | RAT Type Requested shall be only applicable if PS or EPS Location Information is requested
When set, it indicates that RAT Type is requested as part of the PS or EPS Location Information. | + +## 7.21 Call Reference Info + +This information element contains information used for MTRR (see 3GPP TS 23.018 [10]): + +- Call Reference Number (see 7.22) +- AS-Number (see 7.23) + +The HSS uses this information to populate the parameters callReferenceNumber and gmsc-Address within MAP-Provide-Roaming-Number. + +## 7.22 Call Reference Number + +This information element contains a temporary reference number identifying the call in progress (see 3GPP TS 23.018 [10]). + +## 7.23 AS-Number + +This information element contains the Application Server's E.164 Number. + +# --- 8 Protocol version identification + +See 3GPP TS 29.329 [5]. + +# --- 9 Operational Aspects + +See 3GPP TS 29.329 [5]. + +# --- Annex A (normative): Mapping of Sh operations and terminology to Diameter + +## A.1 Introduction + +This appendix gives mappings from Sh to Diameter protocol elements. Diameter protocol elements are defined in 3GPP TS 29.329 [5]. + +## --- A.2 Sh message to Diameter command mapping + +The following table defines the mapping between stage 2 operations and Diameter commands: + +**Table A.2.1: Sh message to Diameter command mapping** + +| Sh message | Source | Destination | Command-Name | Abbreviation | +|--------------------|--------|-------------|---------------------------------|--------------| +| Sh-Pull | AS | HSS | User-Data-Request | UDR | +| Sh-Pull Resp | HSS | AS | User-Data-Answer | UDA | +| Sh-Update | AS | HSS | Profile-Update-Request | PUR | +| Sh-Update Resp | HSS | AS | Profile-Update-Answer | PUA | +| Sh-Subs-Notif | AS | HSS | Subscribe-Notifications-Request | SNR | +| Sh-Subs-Notif Resp | HSS | AS | Subscribe-Notifications-Answer | SNA | +| Sh-Notif | HSS | AS | Push-Notification-Request | PNR | +| Sh-Notif Resp | AS | HSS | Push-Notification-Answer | PNA | + +## --- A.3 Void + +# Annex B (informative): Message flow + +## B.1 Message flows + +The following message flows give examples regarding which Diameter messages shall be sent in scenarios described in 3GPP TS 23.218 [4]. + +### B.1.1 Data Update, Registration, Notification Subscription. + +![Sequence diagram showing message flows between SCSC, HSS, and AS. The diagram is divided into three main sections. The first section shows an initial registration and update flow. The second section shows a third-party registration flow. The third section shows a data update and notification flow initiated by the AS and HSS respectively.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg) + +Home Network + +``` +sequenceDiagram + participant SCSC + participant HSS + participant AS + Note left of SCSC: At some point, the AS decides to update certain data in the HSS + Note right of AS: At some point, the HSS sends updates to the AS (that previously subscribed) + + Note over SCSC, HSS, AS: Initial Flow + AS->>HSS: 1. Sh-Update + HSS-->>AS: 2. Sh-Update Resp + Note left of SCSC: 3. REGISTER + SCSC->>HSS: 4. User Profile Downloading + HSS-->>SCSC: 5. 200 OK + Note over SCSC, HSS, AS: Third-Party Registration + Note left of AS: 6. REGISTER (Third Party) + AS->>HSS: 6. REGISTER (Third Party) + HSS-->>AS: 7. 200 OK + Note over SCSC, HSS, AS: Notification Flow + HSS->>AS: 8. Sh-Subs_Notif + Send data Ind. + AS-->>HSS: 9. Sh-Subs_Notif Resp + User-Data + Note over SCSC, HSS, AS: Data Update Flow + AS->>HSS: 10. Sh-Update + HSS-->>AS: 11. Sh-Update Resp + HSS->>AS: 12. Sh-Notif + AS-->>HSS: 13. Sh-Notif Resp +``` + +Sequence diagram showing message flows between SCSC, HSS, and AS. The diagram is divided into three main sections. The first section shows an initial registration and update flow. The second section shows a third-party registration flow. The third section shows a data update and notification flow initiated by the AS and HSS respectively. + +**Figure B.1.1: Data Update, Registration, Notification Subscription** + +1. A user subscribes to a new service. The operator provisions the service in an AS. The AS stores some service data for a user in the HSS, Sh-Update (user identity, updated data) e.g. repository data. +2. HSS confirms the data is updated +3. Some time later, user registers with the network + +4. S-CSCF downloads the data from the HSS (during the procedure S-CSCF Registration Notification on Cx interface). Filter criteria specify that the AS wants to be notified that the end user is registered. +5. 200 OK +6. S-CSCF sends third party registration message to the application server to notify that user is registered. +7. 200 OK +8. The AS subscribes to notifications and downloads data needed for providing service from HSS, by means of Sh-Subs-Notif (user identity, requested data, service information and send data indication). +9. HSS confirms the subscription request and sends data to AS +10. At some moment, the AS decides to update user's service data e.g. repository data in the HSS, by means of Sh-Update (user identity, updated data). +11. The HSS confirms the service data is updated. +12. At some moment, user data is updated in the HSS. As the AS subscribed to notifications (step 8), the HSS sends to the AS the requested updates, by means of Sh-Notif (user identity, updated data). +13. The AS acknowledges the notification. + +# Annex C (informative): UML model of the data downloaded over Sh interface + +The purpose of this UML model is to define in an abstract level the structure of the data downloaded over the Sh interface and describe the purpose of the different information classes included in it. + +## C.1 General description + +The following picture gives an outline of the UML model of the user profile, which is exchanged between the HSS and an AS: + +![UML Class Diagram of Sh-Data structure. The diagram shows a central 'Sh Data' class at the top with attributes: CSUserState, PSUserState, EPSUserState, Sh-5GSUserState, IMSI, IMSPrivateUserIdentity, and IMEISV. Below it, a horizontal line connects to several identity classes on the left: PublicIdentifiers, RegisteredIdentities, ImplicitIdentities, AllIdentities, AliasIdentities, and DeletedIdentities, each with a 0..1 multiplicity. To the right of the horizontal line, there are three main branches: 'RepositoryData' (0..n) containing 'Service indication', 'UE reachability' (0..1) containing 'URRP-MME' and 'URRP-SGSN', and 'TADS information' (0..1) containing 'IMS Voice Over PS Session support' and 'RAT type'. Below these, another horizontal line connects to five location information classes: 'CSLocationInformation', 'PSLocationInformation', 'EPSLocationInformation', 'TWANLocationInformation', and '5GSLocationInformation', each with a 0..1 multiplicity. These location classes contain detailed attributes like CellGlobalId, ServiceAreaId, LocationAreaId, TrackingAreaId, GeographicalInformation, etc. At the bottom, a 'Sh-IMS-Data' class (0..1) is connected to the main structure.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +UML Class Diagram of Sh-Data structure. The diagram shows a central 'Sh Data' class at the top with attributes: CSUserState, PSUserState, EPSUserState, Sh-5GSUserState, IMSI, IMSPrivateUserIdentity, and IMEISV. Below it, a horizontal line connects to several identity classes on the left: PublicIdentifiers, RegisteredIdentities, ImplicitIdentities, AllIdentities, AliasIdentities, and DeletedIdentities, each with a 0..1 multiplicity. To the right of the horizontal line, there are three main branches: 'RepositoryData' (0..n) containing 'Service indication', 'UE reachability' (0..1) containing 'URRP-MME' and 'URRP-SGSN', and 'TADS information' (0..1) containing 'IMS Voice Over PS Session support' and 'RAT type'. Below these, another horizontal line connects to five location information classes: 'CSLocationInformation', 'PSLocationInformation', 'EPSLocationInformation', 'TWANLocationInformation', and '5GSLocationInformation', each with a 0..1 multiplicity. These location classes contain detailed attributes like CellGlobalId, ServiceAreaId, LocationAreaId, TrackingAreaId, GeographicalInformation, etc. At the bottom, a 'Sh-IMS-Data' class (0..1) is connected to the main structure. + +Figure C.1.1: Sh-Data + +Class Sh-Data contains the following attributes: + +- An optional instance of CSUserState attribute. +- An optional instance of PSUserState attribute. + +- An optional instance of IMSI attribute. +- Zero or more instances of IMSPrivateUserIdentity attribute. +- An optional instance of IMEISV attribute. + +Class Sh-Data contains the following classes: + +- An optional instance of the class PublicIdentifiers. +- Zero or more instances of the class RepositoryData. +- An optional instance of the class Sh-IMS-Data. +- An optional instance of the class CSLocationInformation. +- An optional instance of the class PSLocationInformation. +- An optional instance of the class RegisteredIdentities. +- An optional instance of the class ImplicitIdentities. +- An optional instance of the class AllIdentities. +- An optional instance of the class AliasIdentities. +- An optional instance of the class DeletedIdentities. + +If the AS and the HSS both support the Notif-Eff feature and the AS requires to read more than one Identity Sets of a Public Identity, or regardless whether or not the Notif-Eff feature is supported, the AS has subscribed to be notified of changes to IMSPublicIdentity for more than one Identity Sets (see table 7.6.1), the class PublicIdentifiers shall not be used to convey IMS Public Identities (it shall however still be used to convey the MSISDNs if so requested). Instead the classes RegisteredIdentities, ImplicitIdentities, AllIdentities and AliasIdentities shall be used and they contain the REGISTERED\_IDENTITIES, IMPLICIT\_IDENTITIES, ALL\_IDENTITIES and ALIAS\_IDENTITIES associated with the IMS Public Identity included in the request respectively. See clause 7.6.2 for the detailed information. The class PublicIdentifiers or the one among the four which may be used to contain the corresponding identity set can both be used to convey IMS Public Identities when AS requires only one identity set of a public identity. + +If Public Identity(ies) are deleted and the AS has any subscription active for the deleted identity(ies), the HSS shall notify the AS of the deletion of the identity(ies) using the class DeletedIdentities. + +Class RepositoryData contains repository data (transparent data) for a given service that are associated to a Public user Identity or a group of alias Public User Identities. It has attributes ServiceIndication, SequenceNumber and ServiceData. + +Class CSUserState contains the state of a user in the CS domain. Its only attribute, State, is an enumeration whose possible values are defined in clause 7.6.7. + +Class PSUserState contains the state of a user in the PS domain (SGSN). Its only attribute, State, is an enumeration whose possible values are defined in clause 7.6.7. + +NOTE: the fact that attribute State is an enumeration is a difference from what can be carried in the MAP protocol. + +Class EPSUserState contains the state of a user in the PS domain (MME). Its only attribute, State, is an enumeration whose possible values are defined in clause 7.6.7. . + +Class Sh-5GSUserState contains the state of a user in the PS domain (AMF). Its only attribute, State, is an enumeration whose possible values are defined in clause 7.6.7. + +Class CSLocationInformation has the attributes LocationNumber, ServiceAreaID, CellGlobalId, LocationAreaId, GeographicalInformation, GeodeticInformation, VLRNumber, MSCNumber, AgeOfLocationInformation, CurrentLocationRetrieved, UserCSGInformation, TrackingAreaId, E-UTRANCellGlobalId and LocalTimeZone. They are defined in 7.6. + +Class PSLocationInformation has the attributes ServiceAreaId, CellGlobalId, LocationAreaID, RoutingAreaID, GeographicalInformation, GeodeticInformation, SGSNNumber, AgeOfLocationInformation, CurrentLocationRetrieved, UserCSGInformation, VisitedPLMNID, LocalTimeZone and RATtype. They are defined in 7.6. + +Class EPSLocationInformation has the attributes E-UTRANCellGlobalId, TrackingAreaID, GeographicalInformation, GeodeticInformation, MMENAME, AgeOfLocationInformation, CurrentLocationRetrieved, UserCSGInformation, VisitedPLMNID, LocalTimeZone and RATtype. They are defined in 7.6. + +Class TWANLocationInformation has the attributes TWAN-SSID, TWAN-BSSID, TWAN-PLMNID, CivicAddress, TWANOOperatorName, LocalTimeZone and LogicalAccessID. They are defined in 7.6. + +Class Sh-5GSLocationInformation has the attributes NRCellGlobalId, E-UTRANCellGlobalId, TrackingAreaID, GeographicalInformation, AMFAddress, SMSFAddress, AgeOfLocationInformation, CurrentLocationRetrieved, VisitedPLMNID, LocalTimeZone and RATtype. They are defined in 7.6. + +Class DeletedIdentities contains Public Identities (IMS Public User Identities or Public Service Identities) removed from the HSS. + +Class UEReachabilityForIP contains the UE reachability for IP. Its attributes, UEIPReachabilityMME, UEIPReachabilitySGSN, UEIPReachabilityAMF3GPP and UEIPReachabilityAMFnon3GPP are enumerations whose possible values are defined in clause 7.6.17. + +Class IMSVoiceOverPSSessionsSupport contains the support of IMS voice over PS at the current access. Its only attribute, SupportIndication, is an enumeration whose possible values are defined in clause 7.6.18. + +Class IMSI contains the UE's IMSI. See clause 7.6.24. + +Class IMSPrivateUserIdentity contains an IMS Private Identity associated with the IMS Public Identity included in the request. + +## C.2 PublicIdentifiers + +The following picture details the UML model of the class PublicIdentifiers: + +![UML Class Diagram showing PublicIdentifiers as the base class for EnhancedIMSPublicIdentifiers and ExtendedMSISDN. PublicIdentifiers has attributes: IMSPublicIdentity (SIP URL or Tel_URL), IdentityType (enumerated), WildcardedPSI (anyURI), WildcardedIMPU (anyURI), and MSISDN (string). EnhancedIMSPublicIdentifiers inherits from PublicIdentifiers and has attributes: IMSPublicIdentity (SIP URL or Tel_URL) and IdentityType (enumerated). ExtendedMSISDN inherits from PublicIdentifiers and has attributes: MSISDN (string) and MSISDNType (enumerated). Both subclasses have a 0..n multiplicity at their end of the inheritance line.](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +``` + +classDiagram + class PublicIdentifiers { + IMSPublicIdentity: SIP URL or Tel_URL + IdentityType: enumerated + WildcardedPSI: anyURI + WildcardedIMPU: anyURI + MSISDN: string + } + class EnhancedIMSPublicIdentifiers { + IMSPublicIdentity: SIP URL or Tel_URL + IdentityType: enumerated + } + class ExtendedMSISDN { + MSISDN: string + MSISDNType: enumerated + } + PublicIdentifiers <|-- "0..n" EnhancedIMSPublicIdentifiers + PublicIdentifiers <|-- "0..n" ExtendedMSISDN + +``` + +UML Class Diagram showing PublicIdentifiers as the base class for EnhancedIMSPublicIdentifiers and ExtendedMSISDN. PublicIdentifiers has attributes: IMSPublicIdentity (SIP URL or Tel\_URL), IdentityType (enumerated), WildcardedPSI (anyURI), WildcardedIMPU (anyURI), and MSISDN (string). EnhancedIMSPublicIdentifiers inherits from PublicIdentifiers and has attributes: IMSPublicIdentity (SIP URL or Tel\_URL) and IdentityType (enumerated). ExtendedMSISDN inherits from PublicIdentifiers and has attributes: MSISDN (string) and MSISDNType (enumerated). Both subclasses have a 0..n multiplicity at their end of the inheritance line. + +**Figure C.2.1: The UML model of the class PublicIdentifiers** + +Class PublicIdentifiers contains the following attributes: + +- Zero or more instances of IMSPublicIdentity attribute. Each instance is a Public Identity. See clause 7.6.2 for information about contents. +- An optional instance of IdentityType attribute. If only one instance of IMSPublicIdentity attribute is included, then this attribute identifies the identity type in the IMSPublicIdentity attribute, it could be either: + - A distinct Public User Identity + - A distinct Public Service Identity + +If more than one instance of IMSPublicIdentity attribute is included, this attribute is assumed to apply to all of them. + +If IdentityType attribute is not present, it is assumed to be a distinct Public User Identity. + +If more than one instance of IMSPublicIdentity shall be returned, if the identities are of different types the EnhancedIMSPublicIdentifiers class should be used instead. + +- An optional instance of WildcardedPSI attribute, if the Public Service Identity in the request matches a Wildcarded PSI. + +NOTE: This attribute can be omitted if this information is conveyed including Wildcarded PSI information element in the response. See clause 6.1.1 and 6.1.3. + +- An optional instance of WildcardedIMPU attribute, if the Public User Identity in the request matches a Wildcarded IMPU. + +NOTE: This attribute can be omitted if this information is conveyed including Wildcarded Public User Identity information element in the response. See clause 6.1.1 and 6.1.3. + +- Zero or more instances of MSISDN attribute, that contains an MSISDN. + +Class PublicIdentifiers contains the following classes: + +- Zero to more instances of EnhancedIMSPublicIdentifiers. This class is required when more than one instance of IMSPublicIdentity shall be returned and the identities are of different types. See clause 7.6.2 for more information about contents. It includes the following attributes: + - One instance of IMSPublicIdentity attribute that contains a Public Identity. +- One instance of the IdentityType attribute that identifies the identity type in the IMSPublicIdentity attribute, it could be either: + - A distinct Public User Identity + - A distinct Public Service Identity + - A Wildcarded Public Service Identity + - A Wildcarded Public User Identity +- Zero or more instances of ExtendedMSISDN, only when Additional-MSISDN feature is enabled. It includes the following attributes: + - One instance of MSISDN attribute that contains an MSISDN. + - One instance of MSISDNType attribute that indicates the MSISDN Type. + +**Figure C.2.2: Void** + +## C.3 Sh-IMS-Data + +The following picture details the UML model of the class Sh-IMS-Data. + +![UML Class Diagram for Sh-IMS-Data](aeb2a26a07219661191294dba528067a_img.jpg) + +``` + +classDiagram + class ShIMSData["Sh-IMS-Data"] { + } + class SCSCFName["S-CSCFName"] { + ServerName: SIP_URL + } + class IFCs["IFCs"] { + IFCs: tIFCs + } + class IMSUserState["IMSUserState"] { + IMSState: enumerated + } + class PSIActivation["PSIActivation"] { + PSIState: enumerated + } + class ChargingInformation["Charging Information"] { + Charging Information : tChargingInformation + } + class DSAI["DSAI"] { + DSAI Tag: string + DSAI Value: enumerated + } + class ServiceLevelTraceInfo["Service Level Trace Information"] { + ServiceLevelTraceInfo: string + } + class IPAddrSecureBindingInfo["IP Address Secure Binding Information"] { + IPv4Address: tIPv4Address + IPv6Prefix: tIPv6Prefix + IPv6InterfaceIdentifier: tIPv6InterfaceIdentifier + } + class ServicePriorityLevel["Service Priority Level"] { + ServicePriorityLevel: enumerated + } + class ExtendedPriority["ExtendedPriority"] { + PriorityNamespace: string + PriorityLevel: string + } + class EnhancedSRVCC["EnhancedSRVCC"] { + STN-SR: tMSISDN + UE-SRVCC-Capability: tUE-SRVCC-Capability + } + class ReferenceLocationInformation["ReferenceLocationInformation"] { + AccessType: string + AccessInfo: string + AccessValue: string + } + class SMSRegistrationInfo["SMSRegistrationInfo"] { + IP-SM-GW-Number: string + SCAddress: tSCAddress + } + class 5GSRVCC["5GSRVCC"] { + UE-5G-SRVCC-Capability: tUE-5G-SRVCC-Capability + } + + ShIMSData "1" *-- "0..1" SCSCFName + ShIMSData "1" *-- "0..1" IFCs + ShIMSData "1" *-- "0..1" IMSUserState + ShIMSData "1" *-- "0..1" PSIActivation + ShIMSData "1" *-- "0..1" ChargingInformation + ShIMSData "1" *-- "0..n" DSAI + ShIMSData "1" *-- "0..1" ServiceLevelTraceInfo + ShIMSData "1" *-- "0..1" IPAddrSecureBindingInfo + ShIMSData "1" *-- "0..n" ServicePriorityLevel + ShIMSData "1" *-- "0..1" ReferenceLocationInformation + ShIMSData "1" *-- "0..1" SMSRegistrationInfo + ShIMSData "1" *-- "0..1" 5GSRVCC + +``` + +The diagram illustrates the UML model for the class Sh-IMS-Data. It is a composite class containing various optional and mandatory components. The relationships are as follows: + +- Sh-IMS-Data** (Class) is the root class, which has a composition relationship with several other classes. The multiplicity of the root class is 1. +- S-CSCFName** (Class): Multiplicity 0..1. Contains attribute `ServerName: SIP_URL`. +- IFCs** (Class): Multiplicity 0..1. Contains attribute `IFCs: tIFCs`. +- IMSUserState** (Class): Multiplicity 0..1. Contains attribute `IMSState: enumerated`. +- PSIActivation** (Class): Multiplicity 0..1. Contains attribute `PSIState: enumerated`. +- Charging Information** (Class): Multiplicity 0..1. Contains attribute `Charging Information : tChargingInformation`. +- DSAI** (Class): Multiplicity 0..n. Contains attributes `DSAI Tag: string` and `DSAI Value: enumerated`. +- Service Level Trace Information** (Class): Multiplicity 0..1. Contains attribute `ServiceLevelTraceInfo: string`. +- IP Address Secure Binding Information** (Class): Multiplicity 0..1. Contains attributes `IPv4Address: tIPv4Address`, `IPv6Prefix: tIPv6Prefix`, and `IPv6InterfaceIdentifier: tIPv6InterfaceIdentifier`. +- Service Priority Level** (Class): Multiplicity 0..n. Contains attribute `ServicePriorityLevel: enumerated`. +- ExtendedPriority** (Class): Multiplicity 0..n. Contains attributes `PriorityNamespace: string` and `PriorityLevel: string`. +- EnhancedSRVCC** (Class): Multiplicity 0..1. Contains attributes `STN-SR: tMSISDN` and `UE-SRVCC-Capability: tUE-SRVCC-Capability`. +- ReferenceLocationInformation** (Class): Multiplicity 0..1. Contains attributes `AccessType: string`, `AccessInfo: string`, and `AccessValue: string`. +- SMSRegistrationInfo** (Class): Multiplicity 0..1. Contains attributes `IP-SM-GW-Number: string` and `SCAddress: tSCAddress`. +- 5GSRVCC** (Class): Multiplicity 0..1. Contains attribute `UE-5G-SRVCC-Capability: tUE-5G-SRVCC-Capability`. + +UML Class Diagram for Sh-IMS-Data + +**Figure C.3.1: Sh-IMS-Data** + +Each instance of the class Sh-IMS-Data contains 0 or 1 instance of the class S-CSCFName, 0 to 1 instance of the class IFCs, 0 or 1 instance of the class IMSUserState, 0 or 1 instance of the class ChargingInformation, 0 or 1 instance of the class PSIActivation, 0 to n instances of the class DSAI, 0 or 1 instance of the class ServiceLevelTraceInfo, 0 or 1 instance of the class IPAddressSecureBindingInformation, and 0 or 1 instance of the class ReferenceLocationInformation. + +Class S-CSCFName contains a SIP URI. See clause 7.6.4 for further details. + +Class IFCs contains 0 to n instances of the initial filter criteria of the multimedia public identity that the AS included in the request. The initial filter criteria is defined in 3GPP TS 29.228 [6]. + +Class IMSUserState contains the registration state of the identity given by the attribute of class Sh-IMS-Data. See clause 7.6 for possible values. + +Class Charging Information contains the online and offline charging function addresses. See clause 7.6 for possible values. + +Class PSIActivation contains the activation state of the Public Service Identity given by the attribute of class Sh-IMS-Data. See clause 7.6 for possible values. + +Class DSAI contains the DSAI Tag and a DSAI Value (reflecting the activation state) for services the user is subscribed to. See clause 7.14 for contents and usage. + +Class ServiceLevelTraceInfo contains the Service Level Trace configuration information to enable the Application Server to perform service level tracing related to a specific Public Identifier. See clause 7.6.13 for contents and usage. + +Class IPAddressSecureBindingInformation contains either 0 or one IPv4 address, either 0 or one IPv6 prefix and/or IPv6 interface identifier. See clause 7.6.14 for contents and usage. + +Class ServicePriorityLevel contains the Service Priority Level allowed for the Public Identity to be used for priority services. See clause 7.6.15 for contents and usage. + +Class SMSRegistrationInfo contains the IP-SM-GW-Number and the Service Centre Address. See clause 7.6.16 for further details. + +Class Enhanced SRVCC contains the Session Transfer Number (see 3GPP TS 23.003 [11]) and the SRVCC Capability of the UE (see 3GPP TS 23.237 [32]). See clauses 7.6.20 and 7.6.21 respectively for further details. + +Class 5G SRVCC contains the 5G SRVCC Capability of the UE (see 3GPP TS 23.237 [32]). See clause 7.6.21A for further details. + +Class ExtendedPriority contains the PriorityNamespace and the PriorityLevel information elements. See Clause 7.6.15A for further details. + +Class Reference Location Information contains zero or one attribute AccessType, zero or one attribute AccessInfo, and zero or one attribute AccessValue, see 3GPP TS 29.228 [6]. + +# Annex D (normative): XML schema for the Sh interface user profile + +The file ShDataType\_Rel15.xsd, attached to this specification, contains the XML schema for the user profile that is sent over the Sh interface. The user profile XML schema defines the data types that are used in the user profile XML. The data that is allowed to be sent in the user profile may vary depending on the features supported by the Diameter end points, see 3GPP TS 29.329 [5]. The user profile XML schema file is intended to be used by an XML parser. The version of the Sh application sending the user profile XML shall be the same as the version of the sent user profile XML and thus it implies the version of the user profile XML schema to be used to validate it. + +Tables D.1 and D.2 describe the data types and the dependencies among them that configure the user profile XML schema. + +**Table D.1: XML schema for the Sh user profile interface: simple data types** + +| Data type | Tag | Base type | Comments | +|-----------------------|----------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tPriority | Priority | integer | >= 0 | +| tProfilePartIndicator | ProfilePartIndicator | enumerated | Possible values:
0 (REGISTERED)
1 (UNREGISTERED) | +| tGroupID | Group | integer | >= 0 | +| tRegistrationType | RegistrationType | enumerated | Possible values:
0 (INITIAL_REGISTRATION)
1 (RE-REGISTRATION)
2 (DE-REGISTRATION) | +| tDefaultHandling | DefaultHandling | enumerated | Possible values:
0 (SESSION_CONTINUED)
1 (SESSION_TERMINATED) | +| tDirectionOfRequest | SessionCase | enumerated | Possible values:
0 (ORIGINATING_SESSION)
1 (TERMINATING_SESSION)
2 (TERMINATING_UNREGISTERED)
3 (ORIGINATING_UNREGISTERED)
4 (ORIGINATING_CDIV) | +| tIMSUserState | IMSUserState | Enumerated | Possible values:
0 (NOT_REGISTERED)
1 (REGISTERED)
2 (REGISTERED_UNREG_SERVICES)
3 (AUTHENTICATION_PENDING) | +| tCSUserState | CSUserState | Enumerated | Possible values (as defined in 3GPP TS 23.078 [14]):
0 (CAMELBusy)
1 (NetworkDeterminedNotReachable)
2 (AssumedIdle)
3 (NotProvidedfromVLR) | +| tPSUserState | PSUserState | Enumerated | Possible values (as defined in 3GPP TS 23.078 [14]):
0 (Detached)
1 (AttachedNotReachableForPaging)
2 (AttachedReachableForPaging)
3 (ConnectedNotReachableForPaging)
4 (ConnectedReachableForPaging)
5 (NotProvidedFromSGSN or MME or AMF)
6 (NetworkDeterminedNotReachable) | +| tLocationNumber | LocationNumber | string | Syntax described in ITU-T Q.763 [9] (Base64 encoded according to IETF RFC 2045 [15]).
Length >=4 and <=16 (multiples of 4). | +| tCellGlobalId | CellGlobalId | string | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).
Length = 12. | +| tServiceAreaId | ServiceAreaId | string | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).
Length = 12. | +| tLocationAreaId | LocationAreaId | string | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC | + +| | | | | +|---------------------------|-------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | 2045 [15]).
Length = 8. | +| tRoutingAreaId | RoutingAreaId | string | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).
Length = 8. | +| tGeographicalInformation | GeographicalInformation | string | Syntax described in 3GPP TS 29.002 (base 64 encoded according to IETF RFC 2045).
Length = 12. | +| tGeodeticInformation | GeodeticInformation | string | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).
Length = 16. | +| tAgeOfLocationInformation | AgeOfLocationInformation | integer | >=0, <=32767 | +| tCSGId | CSGId | string | Syntax described in 3GPP TS 29.002 [13] i.e. 5 octets BER encoded value of 27-bit BIT STRING (Base64 encoded according to IETF RFC 2045 [15]).
Length = 8. | +| tAccessMode | AccessMode | string | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).
Length = 4. | +| tTrackingAreaId | TrackingAreaId | string | See Syntax of TA-Id and NR-TA-Id as described in 3GPP TS 29.002 [13] clause 17.7.8 (Base64 encoded according to IETF RFC 2045 [15]).
Length = 8. | +| tE-UTRANCellGlobalId | E-UTRANCellGlobalId | string | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).
Length = 12. | +| tNRCellGlobalId | NRCellGlobalId | string | Concatenation of MCC, MNC and NrCellId. NrCellId syntax is described in 3GPP TS 29.571 [46].
Length = 14 or 15. | +| tAddressString | Address | string | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).
Length >= 4 and <=28 (multiples of 4). | +| tMSISDN | MSISDN, STN-SR, CSRN | string | Number structure described in 3GPP TS 23.003 [11]. ASCII encoded according to ANSI X3.4 [20]. | +| tSIP_URL | IMSPublicIdentity | anyURI | Syntax described in IETF RFC 3261 [16]. Wildcarded IMPU and Wildcarded PSI syntax described in 3GPP TS 23.003. | +| tTEL_URL | IMSPublicIdentity | anyURI | Syntax described in IETF RFC 3966 [17]. Wildcarded IMPU and Wildcarded PSI syntax described in 3GPP TS 23.003. | +| tDiameterURI | DiameterURI | string | Syntax of a Diameter URI as described in IETF RFC 6733 [44] | +| tIMSPublicIdentity | IMSPublicIdentity | (union) | Union of tSIP_URL and tTEL_URL | +| tIdentityType | IdentityType | enumerated | Possible values:
0 (PUBLIC_USER_IDENTITY)
1 (DISTINCT_PSI)
2 (WILDCARDED_PSI)
3 (WILDCARDED_IMPU) | +| tWildcardedPSI | WildcardedPSI | anyURI | Syntax described in 3GPP TS 23.003 [11]. | +| tWildcardedIMPU | WildcardedIMPU | anyURI | Syntax described in 3GPP TS 23.003 [11]. | +| tServiceInfo | ServiceInfo | string | | +| tDSAI-Tag | DSAI-Tag | string | | +| tString | RequestURI, Method, Header, Content, Line, MMEName, AccessType, AccessInfo, AccessValue, IMEISV | string | | +| tBool | ConditionTypeCNF, ConditionNegated | boolean | Possible values:
0 (false)
1 (true) | +| tSequenceNumber | SequenceNumber | integer | >=0, <=65535 | +| tPSIActivation | PSIActivation | enumerated | Possible Values:
0 (INACTIVE)
1 (ACTIVE) | +| tDSAI-Value | DSAI-Value | enumerated | Possible values are:
0 (ACTIVE) | + +| | | | | +|-------------------------------|------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | 1 (INACTIVE) | +| tServiceLevelTraceInfo | ServiceLevelTraceInfo | String | Syntax described in 3GPP TS 24.323 [45] | +| tIPv4Address | IPv4Address | String | IPv4 address is represented in dotted-decimal notation (a sequence of four decimal numbers in the range 0 to 255, separated by ".", for example 192.168.1.1. | +| tIPv6Prefix | IPv6Prefix | String | ASCII encoded for the text representation of the address prefix. Syntax described in IETF RFC 4291 [24] and IETF RFC 5952 [41]. | +| tIPv6InterfaceIdentifier | IPv6InterfaceIdentifier | String | ASCII encoded for the text representation of the address. Syntax described in IETF RFC 4291 [24] and IETF RFC 5952 [41]. | +| tServicePriorityLevel | ServicePriorityLevel | enumerated | Possible values:
0 (Highest priority)
1
2
3
4 (Lowest priority) | +| tUEIPReachabilityMME | UEIPReachabilityMME | enumerated | Possible values:
0 (REACHABLE) | +| tUEIPReachabilitySGSN | UEIPReachabilitySGSN | enumerated | Possible values:
0 (REACHABLE) | +| tUEIPReachabilityAMF3GPP | UEIPReachabilityAMF3GPP | enumerated | Possible values:
0 (REACHABLE) | +| tUEIPReachabilityAMFnon3GPP | UEIPReachabilityAMFnon3GPP | enumerated | Possible values:
0 (REACHABLE) | +| tIP-SM-GW-Number | IP-SM-GW-Number | String | IP-SM-GW is an E.164 address where the digits are ASCII encoded according to ANSI X3.4 [20]. Leading indicators for the nature of address and the numbering plan shall not be included. | +| tIMSVoiceOverPSSessionSupport | IMSVoiceOverPSSessionSupport | enumerated | Possible Values:
0 (IMS-VOICE-OVER-PS-NOT-SUPPORTED)
1 (IMS-VOICE-OVER-PS-SUPPORTED)
2 (IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN) | +| tRATtype | RATtype | enumerated | Possible Values are defined in 3GPP TS 29.212 [28], clause 5.3.31 | +| tAccessType | AccessType | enumerated | Possible Values:
0 (3GPP-ACCESS)
1 (NON-3GPP-ACCESS) | +| tDateTime | LastUEActivityTime | dateTime | | +| tUE-SRVCC-Capability | UE-SRVCC-Capability | enumerated | Possible Values:
0 (UE-SRVCC-CAPABILITY-NOT-SUPPORTED)
1 (UE-SRVCC-CAPABILITY-SUPPORTED) | +| tPriorityNamespace | PriorityNamespace | string | Possible values are those of the namespaces that are defined in IETF RFC 4412 [25] or defined according to the IANA registration procedure described in IETF RFC 4412 [25] for Resource-Priority Namespaces. | +| tPriorityLevel | PriorityLevel | string | Possible values depend on the PriorityNamespace and are specified with the associated namespace that is defined in IETF RFC 4412 [25] or defined according to the IANA registration procedure described in IETF RFC 4412 [25] for Resource-Priority Namespaces. | +| tSCAddress | SCAddress | string | SCAddress is an E.164 address where the digits are ASCII encoded according to ANSI X3.4 [20]. Leading indicators for the nature of address and the numbering plan shall not be included. | + +| | | | | +|-------------------------|-------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tVisitedPLMNID | VisitedPLMNID | string | Consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) as described in 3GPP TS 23.003 [11]. It is a string with 3 digits MCC and 2 or 3 digits MNC. | +| tTimeZone | TimeZone | string | Syntax described in 3GPP TS 29.272 [26] | +| tDaylightSavingTime | DaylightSavingTime | enumerated | Possible values are defined in 3GPP TS 29.272 [26]. | +| tMSISDNType | MSISDNType | enumerated | Possible values:
0 (BASIC)
1 (ADDITIONAL)
See 3GPP TS 23.003 [11] for the definition of Additional-MSISDN. | +| tIMSI | IMSI | string | Number structure described in 3GPP TS 23.003 [11]. ASCII encoded according to ANSI X3.4 [20]. | +| tTWAN-SSID | TWAN-SSID | string | Syntax described in 3GPP TS 29.273 [34]. | +| tTWAN-BSSID | TWAN-BSSID | string | Syntax described in 3GPP TS 29.273 [34]. | +| tTWANOperatorName | TWANOperatorName | string | Syntax described in 3GPP TS 23.003 [11]. | +| tCivicAddress | CivicAddress | base64Binary | Syntax described in clause 3.1 of IETF RFC 4776 [35] excluding the first 3 octets (Base64 encoded according to IETF RFC 2045 [15]). | +| tLogicalAccessID | LogicalAccessID | string | Syntax described in ETSI ES 283 034 [37]. | +| tIMSPrivateUserIdentity | IMSPrivateUserIdentity | string | Syntax described in 3GPP TS 23.003 [11] | +| tUE-5G-SRVCC-Capability | UE-5G-SRVCC-Capability | enumerated | Possible Values:
0 (UE-5G-SRVCC-CAPABILITY-NOT-SUPPORTED)
1 (UE-5G-SRVCC-CAPABILITY-SUPPORTED) | +| tlpSmGwSbiSupInd | IP-SM-GW-SBISupportIndication | enumerated | Possible Values:
0 (IP-SM-GW-SBI-NOT-SUPPORTED)
1 (IP-SM-GW-SBI- SUPPORTED) | + +Table D.2: XML schema for the Sh user profile interface: complex data types + +| Data type | Tag | Compound of | | | +|---------------------|----------------|---------------------------|--------------------------|-------------| +| | | Tag | Type | Cardinality | +| tSh-Data | Sh-Data | PublicIdentifiers | tPublicIdentity | 0 to 1 | +| | | RepositoryData | tTransparentData | 0 to n | +| | | Sh-IMS-Data | tShIMSData | 0 to 1 | +| | | CSLocationInformation | tCSLocationInformation | 0 to 1 | +| | | PSLocationInformation | tPSLocationInformation | 0 to 1 | +| | | CSUserState | tCSUserState | 0 to 1 | +| | | PSUserState | tPSUserState | 0 to 1 | +| | | Extension | tSh-Data-Extension | 0 to 1 | +| tSh-Data-Extension | Extension | RegisteredIdentities | tPublicIdentity | 0 to 1 | +| | | ImplicitIdentities | tPublicIdentity | 0 to 1 | +| | | AllIdentities | tPublicIdentity | 0 to 1 | +| | | AliasIdentities | tPublicIdentity | 0 to 1 | +| | | Extension | tSh-Data-Extension2 | 0 to 1 | +| tSh-Data-Extension2 | Extension | DeletedIdentities | tPublicIdentity | 0 to 1 | +| | | Extension | tSh-Data-Extension3 | 0 to 1 | +| tSh-Data-Extension3 | Extension | TADSInformation | tTADSInformation | 0 to 1 | +| | | Extension | tSh-Data-Extension4 | 0 to 1 | +| tSh-Data-Extension4 | Extension | EPSUserState | tPSUserState | 0 to 1 | +| | | EPSLocationInformation | tEPSLocationInformation | 0 to 1 | +| | | Extension | tSh-Data-Extension5 | 0 to 1 | +| tSh-Data-Extension5 | Extension | IMSI | tIMSI | 0 to 1 | +| | | TWANLocationInformation | tTWANLocationInformation | 0 to 1 | +| | | IMSPPrivateUserIdentity | tIMSPPrivateUserIdentity | 0 to n | +| | | Extension | tSh-Data-Extension6 | 0 to 1 | +| tSh-Data-Extension6 | Extension | IMEISV | tString (NOTE 6) | 0 to 1 | +| | | Extension | tSh-Data-Extension7 | 0 to 1 | +| tSh-Data-Extension7 | Extension | Sh-5GSLocationInformation | t5GSLocationInformation | 0 to 1 | +| | | Sh-5GSUserState | tPSUserState | 0 to 1 | +| tTransparentData | RepositoryData | ServiceIndication | string | 1 | +| | | SequenceNumber | tSequenceNumber | 1 | +| | | ServiceData | tServiceData | 0 to 1 | +| tServiceData | any | any | any | 1 | +| tIFCs | IFCs | InitialFilterCriteria | tInitialFilterCriteria | 0 to n | +| tShIMSData | Sh-IMS-Data | SCSCFName | tSIP_URL | 0 to 1 | + +| | | | | | +|---------------------|-----------|------------------------------|-------------------------------|--------------------| +| | | IFCs | tIFCs | 0 to 1 | +| | | IMSUState | tIMSUState | 0 to 1 | +| | | ChargingInformation | tChargingInformation | 0 to 1 | +| | | Extension | tShIMSDatExtension | (0 to 1) | +| tShIMSDatExtension | Extension | PSIActivation | tPSIActivation | (0 to 1) | +| | | Extension | tShIMSDatExtension2 | 0 to 1 | +| tShIMSDatExtension2 | Extension | DSA | tDSA | 0 to n | +| | | Extension | tShIMSDatExtension3 | (0 to 1) | +| tShIMSDatExtension3 | Extension | ServiceLevelTraceInfo | tServiceLevelTraceInfo | (0 to 1) | +| | | IPv4Address | tIPv4Address | 0 to 1 | +| | | IPv6Prefix | tIPv6Prefix | 0 to 1 | +| | | IPv6InterfaceIdentifier | tIPv6InterfaceIdentifier | 0 to 1 | +| | | ServicePriorityLevel | tServicePriorityLevel | 0 to 1 | +| | | UEReachabilityForIP | tUEReachabilityForIP | 0 to 1 | +| | | SMSRegistrationInfo | tSMSRegistrationInfo | 0 to 1 | +| tShIMSDatExtension4 | Extension | Extension | tShIMSDatExtension4 | 0 to 1 | +| | | STN-SR | tMSISDN | 0 to 1 | +| | | UE-SRVCC-Capability | tUE-SRVCC-Capability | 0 to 1 | +| | | ExtendedPriority | tExtendedPriority | 0 to n | +| | | CSRN | tMSISDN | 0 to 1 | +| tShIMSDatExtension5 | Extension | Extension | tShIMSDatExtension5 | 0 to 1 | +| | | ReferenceLocationInformation | tReferenceLocationInformation | 0 to n
(NOTE 7) | +| | | Extension | tShIMSDatExtension6 | 0 to 1 | + +| | | | | | | +|-----------------------------------|----------------------------------|--------------------------|--------------|-----------------------------------|--------| +| tShIMSDDataExtension6 | Extension | MTRRIndication | | tBool | 0 to 1 | +| | | Extension | | tShIMSDDataExtension7 | 0 to 1 | +| tShIMSDDataExtension7 | Extension | UE-5G-SRVCC-Capability | | tUE-5G-SRVCC-Capability | 0 to 1 | +| tReferenceLocationInformation | ReferenceLocationInformation | AccessType | | tString (NOTE 3) | 0 to 1 | +| | | AccessInfo | | tString (NOTE 3) | 0 to 1 | +| | | AccessValue | | tString (NOTE 3) | 0 to 1 | +| tCSLocationInformation | CSLocationInformation | LocationNumber | | tLocationNumber | 0 to 1 | +| | | 5.9 | CellGlobalId | tCellGlobalId | 0 to 1 | +| | | ServiceAreaId | | tServiceAreaId | 0 to 1 | +| | | LocationAreaId | | tLocationAreaId | 0 to 1 | +| | | GeographicalInformation | | tGeographicalInformation | 0 to 1 | +| | | GeodeticInformation | | tGeodeticInformation | 0 to 1 | +| | | VLRNumber | | tISDNAddress | 0 to 1 | +| | | MSCNumber | | tISDNAddress | 0 to 1 | +| | | CurrentLocationRetrieved | | tBool | 0 to 1 | +| | | AgeOfLocationInformation | | tAgeOfLocationInformation | 0 to 1 | +| | | Extension | | tCSLocationInformation-Extension | 0 to 1 | +| tCSLocationInformation-Extension | CSLocationInformation-Extension | UserCSGInformation | | tUserCSGInformation | 0 to 1 | +| | | Extension | | tCSLocationInformation-Extension2 | 0 to 1 | +| tCSLocationInformation-Extension2 | CSLocationInformation-Extension2 | E-UTRANCellGlobalId | | tE-UTRANCellGlobalId | 0 to 1 | +| | | TrackingAreaId | | tTrackingAreaId | 0 to 1 | +| | | Extension | | tCSLocationInformation-Extension3 | 0 to 1 | +| tCSLocationInformation-Extension3 | CSLocationInformation-Extension3 | LocalTimeZone | | tLocalTimeZone | 0 to 1 | +| tPSLocationInformation | PSLocationInformation | 5.9 | CellGlobalId | tCellGlobalId | 0 to 1 | +| | | ServiceAreaId | | tServiceAreaId | 0 to 1 | +| | | LocationAreaId | | tLocationAreaId | 0 to 1 | +| | | RoutingAreaId | | tRoutingAreaId | 0 to 1 | +| | | GeographicalInformation | | tGeographicalInformation | 0 to 1 | +| | | GeodeticInformation | | tGeodeticInformation | 0 to 1 | +| | | SGSNNumber | | tISDNAddress | 0 to 1 | +| | | CurrentLocationRetrieved | | tBool | 0 to 1 | +| | | AgeOfLocationInformation | | tAgeOfLocationInformation | 0 to 1 | +| | | Extension | | tPSLocationInformation-Extension | 0 to 1 | +| tPSLocationInformation-Extension | PSLocationInformation-Extension | UserCSGInformation | | tUserCSGInformation | 0 to 1 | +| | | Extension | | tPSLocationInformation-Extension2 | 0 to 1 | +| tPSLocationInformation-Extension2 | PSLocationInformation-Extension2 | VisitedPLMNID | | tVisitedPLMNID | 0 to 1 | + +| | | | | | +|-------------------------------------|------------------------------------|------------------------------|-------------------------------------|--------| +| tLocalTimeZone | LocalTimeZone | LocalTimeZone | tLocalTimeZone | 0 to 1 | +| | | RATtype | tRATtype | 0 to 1 | +| | EPSSLocationInformation | TimeZone | tTimeZone | 1 | +| | | DaylightSavingTime | tDaylightSavingTime | 1 | +| tEPSSLocationInformation | | E-UTRANCellGlobalId | tE-UTRANCellGlobalId | 0 to 1 | +| | | TrackingAreaId | tTrackingAreaId | 0 to 1 | +| | | GeographicalInformation | tGeographicalInformation | 0 to 1 | +| | | GeodeticInformation | tGeodeticInformation | 0 to 1 | +| | | MMEName | tString | 0 to 1 | +| | | CurrentLocationRetrieved | tBool | 0 to 1 | +| | | AgeOfLocationInformation | tAgeOfLocationInformation | 0 to 1 | +| | | UserCSGInformation | tUserCSGInformation | | +| | | Extension | tEPSSLocationInformation-Extension | 0 to 1 | +| tEPSSLocationInformation-Extension | EPSSLocationInformation-Extension | VisitedPLMNID | tVisitedPLMNID | 0 to 1 | +| | | LocalTimeZone | tLocalTimeZone | 0 to 1 | +| | | Extension | tEPSSLocationInformation-Extension2 | 0 to 1 | +| tEPSSLocationInformation-Extension2 | EPSSLocationInformation-Extension2 | RATtype | tRATtype | 0 to 1 | +| tSh-5GSLocationInformation | Sh-5GSLocationInformation | NRCellGlobalId | tNRCellGlobalId | 0 to 1 | +| | | E-UTRANCellGlobalId | tE-UTRANCellGlobalId | 0 to 1 | +| | | TrackingAreaId | tTrackingAreaId | 0 to 1 | +| | | GeographicalInformation | tGeographicalInformation | 0 to 1 | +| | | AMFAddress | tString | 0 to 1 | +| | | SMSFAddress | tString | 0 to 1 | +| | | CurrentLocationRetrieved | tBool | 0 to 1 | +| | | AgeOfLocationInformation | tAgeOfLocationInformation | 0 to 1 | +| | | VisitedPLMNID | tVisitedPLMNID | 0 to 1 | +| | | LocalTimeZone | tLocalTimeZone | 0 to 1 | +| | | RATtype | tRATtype | 0 to 1 | +| tUserCSGInformation | UserCSGInformation | CSGId | tCSGId | 1 | +| | | Extension | tUserCSGInformation-Extension | 0 to 1 | +| tUserCSGInformation-Extension | UserCSGInformation-Extension | AccessMode | tAccessMode | 0 to 1 | +| | | CMI | tBool | 0 to 1 | +| tTADSInformation | TADSInformation | IMSVoiceOverPSSessionSupport | tIMSVoiceOverPSSessionSupport | 1 | +| | | RATtype | tRATtype | 0 to 1 | +| | | Extension | tTADSInformationExtension | 0 to 1 | +| tTWANLocationInformation | TWANLocationInformation | TWAN-SSID | tTWAN-SSID | 0 to 1 | +| | | TWAN-BSSID | tTWAN-BSSID | 0 to 1 | +| | | TWAN-PLMNID | tVisitedPLMNID | 0 to 1 | +| | | CivicAddress | tCivicAddress | 0 to n | +| | | TWANOperatorName | tTWANOperatorName | 0 to 1 | +| | | LocalTimeZone | tLocalTimeZone | 0 to 1 | +| | | LogicalAccessID | tLogicalAccessID | 0 to 1 | +| tTADSInformationExtension | TADSInformationExtension | LastUEActivityTime | tDateTime | 0 to 1 | + +| | | | | | +|-----------------------------|----------------------------------------------------------------------------------------------------------------|------------------------------|-----------------------------|--------------------| +| | | Extension | tTADSInformationExtension2 | 0 to 1 | +| tTADSInformationExtension2 | TADSInformationExtension2 | AccessType | tAccessType | 0 to 1 | +| tISDNAddress | SGSNNumber, VLRNumber, MSCNumber | Address | tAddressString | 1 | +| tPublicIdentity | PublicIdentifiers, RegisteredIdentities, ImplicitIdentities, AllIdentities, AliasIdentities, DeletedIdentities | IMSPublicIdentity | tIMSPublicIdentity | 0 to n | +| | | MSISDN | tMSISDN | 0 to n | +| | | Extension | tPublicIdentityExtension | 0 to 1) | +| tPublicIdentityExtension | Extension | IdentityType | tIdentityType | (0 to 1) | +| | | WildcardedPSI | tWildcardedPSI | (0 to 1) | +| | | Extension | tPublicIdentityExtension2 | (0 to 1) | +| tPublicIdentityExtension2 | Extension | WildcardedIMPU | tWildcardedIMPU | (0 to 1) | +| | | Extension | tPublicIdentityExtension3 | 0 to 1 | +| tPublicIdentityExtension3 | Extension | ExtendedMSISDN | tExtendedMSISDN | 0 to n
(NOTE 5) | +| | | Extension | tPublicIdentityExtension4 | 0 to 1 | +| tPublicIdentityExtension4 | Extension | EnhancedIMSPublicIdentifiers | tEnhancedIMSPublicIdentity | 0 to n | +| tEnhancedIMSPublicIdentity | EnhancedIMSPublicIdentifiers | IMSPublicIdentity | tIMSPublicIdentity | 1 | +| | | IdentityType | tIdentityType | 1 | +| tInitialFilterCriteria | InitialFilterCriteria | Priority | tPriority | 1 | +| | | TriggerPoint | tTrigger | 0 to 1 | +| | | ApplicationServer | tApplicationServer | 1 | +| | | ProfilePartIndicator | tProfilePartIndicator | 0 to 1 | +| tTrigger | TriggerPoint | ConditionTypeCNF | tBool | 1 | +| | | SPT | tSePoTri | 1 to n | +| tSePoTri | SPT | ConditionNegated | tBool | 0 to 1 | +| | | Group | tGroupID | 1 to n | +| | | RequestURI | tString | 1 | +| | | Method | tString | 1 | +| | | SIPHeader | tHeader | 1 | +| | | SessionCase | tDirectionOfRequest | 1 | +| | | SessionDescription | tSessionDescription | 1 | +| tSePoTriExtension | Extension | Extension | tSePoTriExtension | (0 to 1) | +| | | RegistrationType | tRegistrationType | (0 to 2) | +| tHeader | SIPHeader | Header | tString | 1 | +| | | Content | tString | 0 to 1 | +| tSessionDescription | SessionDescription | Line | tString | 1 | +| | | Content | tString | 0 to 1 | +| tApplicationServer | ApplicationServer | ServerName | tSIP_URL | 1 | +| | | DefaultHandling | tDefaultHandling | 0 to 1 | +| | | ServiceInfo | tServiceInfo | 0 to 1 | +| | | Extension | tApplicationServerExtension | 0 to 1 | +| tApplicationServerExtension | Extension | IncludeRegisterRequest | tIncludeRegisterRequest | 0 to 1 | +| | | IncludeRegisterResponse | tIncludeRegisterResponse | 0 to 1 | +| tIncludeRegisterRequest | IncludeRegisterRequest | (NOTE 4) | (NOTE 4) | 0 to 1 | +| tIncludeRegisterResponse | IncludeRegisterResponse | (NOTE 4) | (NOTE 4) | 0 to 1 | + +| | | | | | +|--------------------------------|------------------------------|---------------------------------------------|--------------------------------|--------------------| +| tChargingInformation | ChargingInformation | PrimaryEventChargingFunctionName | tDiameterURI | 0 to 1
(NOTE 2) | +| | | SecondaryEventChargingFunctionName | tDiameterURI | 0 to 1 | +| | | PrimaryCharging
CollectionFunctionName | tDiameterURI | 0 to 1
(NOTE 2) | +| | | SecondaryCharging
CollectionFunctionName | tDiameterURI | 0 to 1 | +| tDSAI | DSAI | DSAI-Tag | tDSAI-Tag | 1 | +| | | DSAI-Value | tDSAI-Value | 1 | +| tUEReachabilityForIP | UEReachabilityForIP | UEIPReachabilityMME | tUEIPReachabilityMME | (0 to 1) | +| | | Extension | tUEReachabilityForIPExtension | (0 to 1) | +| tUEReachabilityForIPExtension | Extension | UEIPReachabilitySGSN | tUEIPReachabilitySGSN | (0 to 1) | +| | | Extension | tUEReachabilityForIPExtension2 | (0 to 1) | +| tUEReachabilityForIPExtension2 | Extension | UEIPReachabilityAMF3GPP | tUEIPReachabilityAMF3GPP | (0 to 1) | +| | | UEIPReachabilityAMFnon3GPP | tUEIPReachabilityAMFnon3GPP | (0 to 1) | +| tSMSRegistrationInfo | SMSRegistrationInfo | IP-SM-GW-Number | tIP-SM-GW-Number | 1 | +| | | Extension | tSMSRegistrationInfoExtension | (0 to 1) | +| tSMSRegistrationInfoExtension | SMSRegistrationInfoExtension | SCAddress | tSCAddress | (0 to 1) | +| | | Extension | tSMSRegistrationInfoExtension2 | 0 to 1 | +| tSMSRegistrationInfoExtension2 | Extension | IP-SM-GW-SBI-SupportIndication | tIpSmGwSbiSupInd | 0 to 1 | +| tExtendedPriority | ExtendedPriority | PriorityNamespace | tPriorityNamespace | 1 | +| | | PriorityLevel | tPriorityLevel | 1 | +| tExtendedMSISDN | ExtendedMSISDN | MSISDN | tMSISDN | 1 | +| | | MSISDNType | tMSISDNType | 1 | + +NOTE 1: "n" shall be interpreted as non-bounded. +NOTE 2: At least one of these two information elements (PrimaryEventChargingFunctionName or PrimaryChargingCollectionFunctionName) shall be present. +NOTE 3: The syntax of AccessType, AccessInfo and AccessValue is as described in 3GPP TS 29.228 [6]. +NOTE 4: empty cells shall be interpreted as complex XML elements without defined content. +NOTE 5: PublicIdentifiers contains ExtendedMSISDN in addition to MSISDN when Additional-MSISDN feature is enabled. +NOTE 6: Syntax described in 3GPP TS 23.003 [11]; it shall contain either an IMEI value (a string of 14 digits) or an IMEISV value (a string of 16 digits). +NOTE 7: The HSS shall not send more than one instance of ReferenceLocationInformation and if the Application Server receives more than one instance of ReferenceLocationInformation it may arbitrarily pick one for further processing. + +# --- Annex E (informative): T-ADS request handling in the HSS + +E.1 T-ADS request handling in the HSS The following figure shows a possible detailed handling of T-ADS Information request in the HSS: + +![Flowchart for T-ADS request handling. It starts with 'Idle', followed by 'T-ADS request'. It then checks if 'MME registered'. If 'no', it checks if 'SGSN registered'. If 'no', it returns 'NOT SUPPORTED' and 'Idle'. If 'yes', it checks 'Homog. Support/ Non-support in SGSN'. If 'yes', it goes to 'Response to AS' and 'Idle'. If 'no', it checks 'Query supported in SGSN'. If 'yes', it sends 'Query SGSN', 'Wait for SGSN', and 'Response from SGSN' to 'Response to AS'. If 'no', it goes to 'UNKNOWN' and 'Idle'. If 'MME registered' is 'yes', it checks 'SGSN registered'. If 'yes', it checks 'Gn/Gp-SGSN'. If 'yes', it checks 'MME and SGSN are combined' (outcomes 'C' or 'both'). If 'no / unknown', it goes to 'UNKNOWN' and 'Idle'. If 'SGSN registered' is 'no', it checks 'Homog. Support/ Non-support in MME'. If 'yes', it goes to 'UNKNOWN' and 'Idle'. If 'no', it checks 'Query supported in MME'. If 'yes', it sends 'Query MME', 'Wait for MME', and 'Response from MME' to 'Response to AS'. If 'no', it goes to 'UNKNOWN' and 'Idle'.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +Procedure in the HSS to handle T-ADS requests from the AS via Sh or MAP-J + +Signals to/from the left are to/from the MME or SGSN +Signals to/from the right are to/from the AS + +``` +graph TD; Idle1([Idle]) --> TADS[T-ADS request]; TADS --> MME_Reg{MME registered}; MME_Reg -- no --> SGSN_Reg1{SGSN registered}; SGSN_Reg1 -- no --> NOT_SUPPORTED[NOT SUPPORTED]; NOT_SUPPORTED --> Idle2([Idle]); SGSN_Reg1 -- yes --> Homog_SGSN{Homog. Support/ Non-support in SGSN}; Homog_SGSN -- yes --> Response_AS1[Response to AS]; Response_AS1 --> Idle3([Idle]); Homog_SGSN -- no --> Query_SGSN_Sup{Query supported in SGSN}; Query_SGSN_Sup -- yes --> Query_SGSN[Query SGSN]; Query_SGSN --> Wait_SGSN([Wait for SGSN]); Wait_SGSN --> Response_SGSN[Response from SGSN]; Response_SGSN --> Response_AS1; Query_SGSN_Sup -- no --> UNKNOWN1[UNKNOWN]; UNKNOWN1 --> Idle3; MME_Reg -- yes --> SGSN_Reg2{SGSN registered}; SGSN_Reg2 -- yes --> Gn_Gp_SGSN{Gn/Gp-SGSN}; Gn_Gp_SGSN -- yes --> MME_SGSN_Comb{MME and SGSN are combined}; MME_SGSN_Comb -- yes --> C((C)); MME_SGSN_Comb -- no --> both((both)); Gn_Gp_SGSN -- no / unknown --> UNKNOWN2[UNKNOWN]; UNKNOWN2 --> Idle3; SGSN_Reg2 -- no --> Homog_MME{Homog. Support/ Non-support in MME}; Homog_MME -- yes --> UNKNOWN3[UNKNOWN]; UNKNOWN3 --> Idle3; Homog_MME -- no --> Query_MME_Sup{Query supported in MME}; Query_MME_Sup -- yes --> Query_MME[Query MME]; Query_MME --> Wait_MME([Wait for MME]); Wait_MME --> Response_MME[Response from MME]; Response_MME --> Response_AS2[Response to AS]; Response_AS2 --> Idle4([Idle]); Query_MME_Sup -- no --> UNKNOWN4[UNKNOWN]; UNKNOWN4 --> Idle4; +``` + +Flowchart for T-ADS request handling. It starts with 'Idle', followed by 'T-ADS request'. It then checks if 'MME registered'. If 'no', it checks if 'SGSN registered'. If 'no', it returns 'NOT SUPPORTED' and 'Idle'. If 'yes', it checks 'Homog. Support/ Non-support in SGSN'. If 'yes', it goes to 'Response to AS' and 'Idle'. If 'no', it checks 'Query supported in SGSN'. If 'yes', it sends 'Query SGSN', 'Wait for SGSN', and 'Response from SGSN' to 'Response to AS'. If 'no', it goes to 'UNKNOWN' and 'Idle'. If 'MME registered' is 'yes', it checks 'SGSN registered'. If 'yes', it checks 'Gn/Gp-SGSN'. If 'yes', it checks 'MME and SGSN are combined' (outcomes 'C' or 'both'). If 'no / unknown', it goes to 'UNKNOWN' and 'Idle'. If 'SGSN registered' is 'no', it checks 'Homog. Support/ Non-support in MME'. If 'yes', it goes to 'UNKNOWN' and 'Idle'. If 'no', it checks 'Query supported in MME'. If 'yes', it sends 'Query MME', 'Wait for MME', and 'Response from MME' to 'Response to AS'. If 'no', it goes to 'UNKNOWN' and 'Idle'. + +![Flowchart for Homogeneous Support determination. It starts with 'both' and branches based on support in MME and SGSN, leading to outcomes like SUPPORTED, UNKNOWN, NOT SUPPORTED, or Idle.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` +graph TD; Start((both)) --> HSM{Homog. Support in MME}; HSM -- yes --> HS{Homog. Support in SGSN}; HSM -- no --> HNM{Homog. Non-support in MME}; HS -- yes --> SUPPORTED[SUPPORTED]; HS -- no --> HNS{Homog. Non-support in SGSN}; HNM -- yes --> A((A)); HNM -- no --> B((B)); HNS -- yes --> QS1{Query supported in SGSN}; HNS -- no --> QS2{Query supported in SGSN}; QS1 -- yes --> QM1{Query supported in MME}; QS1 -- no --> UNKNOWN[UNKNOWN]; QM1 -- yes --> QSGSN1[Query SGSN]; QM1 -- no --> QS2; QSGSN1 --> QMME[Query MME]; QMME --> WSM[Wait for SGSN and MME]; WSM --> RSM[Responses from SGSN and MME]; RSM --> MRJ[Most recent result]; MRJ --> Idle1[Idle]; QS2 -- yes --> QM2{Query supported in MME}; QS2 -- no --> UNKNOWN; QM2 -- yes --> QSGSN2[Query SGSN]; QM2 -- no --> WSS[Wait for SGSN support]; QSGSN2 --> WSS; WSS --> SS[Support from SGSN]; WSS --> OR[Other response]; WSS --> ER[Empty response]; SS --> SUPPORTED2[SUPPORTED]; OR --> UNKNOWN2[UNKNOWN]; ER --> NOTS[NOT SUPPORTED]; SUPPORTED2 --> Idle2[Idle]; UNKNOWN2 --> Idle2[Idle]; NOTS --> Idle2[Idle]; Idle1 --> Idle2; +``` + +Flowchart for Homogeneous Support determination. It starts with 'both' and branches based on support in MME and SGSN, leading to outcomes like SUPPORTED, UNKNOWN, NOT SUPPORTED, or Idle. + + + +![Flowchart for Homogeneous Non-Support in SGSN handling. It starts at point A, checks for homogeneous non-support in SGSN. If yes, it returns NOT SUPPORTED and goes Idle. If no, it checks for homogeneous support in SGSN. If yes, it checks if the query is supported in SGSN. If no, it checks if supported in MME. If yes to either, it queries SGSN then MME, waits for responses, and returns the most recent result. If no to both, it returns UNKNOWN and goes Idle. If no to homogeneous support in SGSN, it checks if the query is supported in SGSN. If yes, it checks if supported in MME. If no, it queries SGSN, waits for non-support response, and returns NOT SUPPORTED. If yes to both, it returns UNKNOWN and goes Idle. If no to query supported in SGSN, it returns UNKNOWN and goes Idle.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` +graph TD; A((A)) --> HNS{Homog. Non-Support in SGSN}; HNS -- yes --> NS[NOT SUPPORTED]; NS --> Idle1([Idle]); HNS -- no --> HS{Homog. support in SGSN}; HS -- yes --> QS1{Query supported in SGSN}; QS1 -- yes --> QM{Query supported in MME}; QM -- yes --> QuerySGSN1[Query SGSN]; QM -- no --> UNKNOWN1[UNKNOWN]; UNKNOWN1 --> Idle2([Idle]); QS1 -- no --> UNKNOWN2[UNKNOWN]; UNKNOWN2 --> Idle3([Idle]); HS -- no --> QS2{Query supported in SGSN}; QS2 -- yes --> QM2{Query supported in MME}; QM2 -- yes --> UNKNOWN3[UNKNOWN]; UNKNOWN3 --> Idle4([Idle]); QM2 -- no --> QuerySGSN2[Query SGSN]; QuerySGSN2 --> WaitNS[Wait for SGSN non-support]; WaitNS --> NSR[Non-Support from SGSN]; WaitNS --> ER[Empty response]; WaitNS --> OR[Other response]; NSR --> NS2[NOT SUPPORTED]; NS2 --> Idle5([Idle]); ER --> UNKNOWN4[UNKNOWN]; OR --> UNKNOWN4; UNKNOWN4 --> Idle5; +``` + +Flowchart for Homogeneous Non-Support in SGSN handling. It starts at point A, checks for homogeneous non-support in SGSN. If yes, it returns NOT SUPPORTED and goes Idle. If no, it checks for homogeneous support in SGSN. If yes, it checks if the query is supported in SGSN. If no, it checks if supported in MME. If yes to either, it queries SGSN then MME, waits for responses, and returns the most recent result. If no to both, it returns UNKNOWN and goes Idle. If no to homogeneous support in SGSN, it checks if the query is supported in SGSN. If yes, it checks if supported in MME. If no, it queries SGSN, waits for non-support response, and returns NOT SUPPORTED. If yes to both, it returns UNKNOWN and goes Idle. If no to query supported in SGSN, it returns UNKNOWN and goes Idle. + +![Flowchart for B (Start) leading to various decision points: Query supported in MME, Query supported in SGSN, Homog. Support in SGSN, Homog. Non-Support in SGSN, Query SGSN, Query MME, Wait For MME support, Wait for SGSN and MME, Responses from SGSN and MME, Support From MME, Empty response, Other response, Non-Support From MME, Most recent result, SUPPORTED, NOT SUPPORTED, UNKNOWN, Idle.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` +graph TD; B((B)) --> Q1{Query supported in MME}; Q1 -- yes --> Q2{Query supported in SGSN}; Q1 -- no --> UNKNOWN1[UNKNOWN]; UNKNOWN1 --> Idle1([Idle]); Q2 -- yes --> QuerySGSN[Query SGSN]; Q2 -- no --> HS{Homog. Support in SGSN}; QuerySGSN --> QueryMME1[Query MME]; QueryMME1 --> WaitSGSNMME([Wait for SGSN and MME]); WaitSGSNMME --> Responses[Responses from SGSN and MME]; Responses --> MostRecent[Most recent result]; MostRecent --> Idle2([Idle]); HS -- yes --> QueryMME2[Query MME]; QueryMME2 --> WaitMME[Wait For MME support]; WaitMME --> SupportMME[Support From MME]; WaitMME --> EmptyMME[Empty response]; WaitMME --> OtherMME[Other response]; SupportMME --> SUPPORTED[SUPPORTED]; SUPPORTED --> Idle3([Idle]); EmptyMME --> NOTSUPPORTED1[NOT SUPPORTED]; NOTSUPPORTED1 --> UNKNOWN2[UNKNOWN]; OtherMME --> UNKNOWN3[UNKNOWN]; HS -- no --> HNS{Homog. Non-Support in SGSN}; HNS -- yes --> QueryMME3[Query MME]; QueryMME3 --> WaitMMENonSupport([Wait For MME non support]); WaitMMENonSupport --> NonSupportMME[Non-Support From MME]; WaitMMENonSupport --> EmptyNonSupport[Empty response]; WaitMMENonSupport --> OtherNonSupport[Other response]; NonSupportMME --> NOTSUPPORTED2[NOT SUPPORTED]; NOTSUPPORTED2 --> Idle4([Idle]); EmptyNonSupport --> UNKNOWN4[UNKNOWN]; OtherNonSupport --> UNKNOWN5[UNKNOWN]; HNS -- no --> UNKNOWN6[UNKNOWN]; UNKNOWN6 --> Idle5([Idle]); +``` + +Flowchart for B (Start) leading to various decision points: Query supported in MME, Query supported in SGSN, Homog. Support in SGSN, Homog. Non-Support in SGSN, Query SGSN, Query MME, Wait For MME support, Wait for SGSN and MME, Responses from SGSN and MME, Support From MME, Empty response, Other response, Non-Support From MME, Most recent result, SUPPORTED, NOT SUPPORTED, UNKNOWN, Idle. + +![Flowchart for T-ADS request handling](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` +graph TD; C((C)) --> H{Homog. Support/ Non-support in combined node}; H -- no --> Q{Query supported in combined node}; H -- yes --> R[Response to AS]; Q -- no --> U[UNKNOWN]; Q -- yes --> QN[Query combined node]; QN --> W[Wait for combined node]; W --> RN[Response from combined node]; RN --> R; U --> R; R --> I[Idle]; +``` + +The flowchart illustrates the T-ADS request handling process. It begins with a connector 'C' leading to a decision node 'Homog. Support/ Non-support in combined node'. If 'no', it proceeds to 'Query supported in combined node'. If 'yes', it proceeds directly to 'Response to AS'. From 'Query supported in combined node', if 'no', it proceeds to 'UNKNOWN' and then to 'Response to AS'. If 'yes', it proceeds to 'Query combined node', then 'Wait for combined node', then 'Response from combined node', and finally to 'Response to AS'. Both 'UNKNOWN' and 'Response to AS' lead to the 'Idle' state. + +Flowchart for T-ADS request handling + +When receiving a T-ADS request from an Application Server, the HSS checks whether serving nodes (i.e. SGSN and/or MME) are registered (i.e. GPRS services and/or EPS services are actually subscribed, serving node addresses are stored and not marked as purged). + +If neither MME nor SGSN is registered, a response indicating that IMS voice over PS sessions is not supported is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported. + +If both MME and SGSN are registered but the registered SGSN is a Gn/Gp-SGSN, the HSS treats the MME as not registered in the following T-ADS request handling. + +Otherwise, + +if in the previous ULR(s) the AVP Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions was received from all the registered serving nodes with the same value (either with SUPPORTED or NOT\_SUPPORTED), a response + +with the received value is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported. + +if in previous ULRs the AVP Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions was received from all the registered serving nodes but with different values, the HSS continues processing as follows: + +if MME or SGSN (or both) did not indicate support of T-ADS Data Retrieval within the previous ULR, a response indicating IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported. + +otherwise the HSS retrieves T-ADS Data from MME and from SGSN. After retrieval, the HSS returns a response to the Application Server indicating the response from MME or SGSN whichever reported the most recent UE Activity Time. UE Activity Time and the Last RAT Type are also reported. + +if in the previous ULR(s) the AVP Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions was not received from at least one of the registered serving nodes, the HSS continues processing as follows: + +if at least one of the registered serving nodes that did not send an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR did not indicate support of T-ADS Data Retrieval within the previous ULR, a response indicating IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported. + +otherwise the HSS retrieves T-ADS Data from all the registered serving nodes that did not send an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR. When all responses are received the HSS continues processing as follows: + +if two T-ADS Data responses were received (one from MME and one from SGSN), the HSS returns a response to the Application Server indicating the response from MME or SGSN whichever reported the most recent UE Activity Time. UE Activity Time and the Last RAT Type are also reported. + +if one T-ADS Data response was received (from MME or SGSN) and the other serving node (SGSN or MME) was not registered, the HSS returns a response to the Application Server indicating the response from responding serving node. UE Activity Time and the Last RAT Type are also reported. + +if one T-ADS Data response was received (from MME or SGSN) and the other serving node (SGSN or MME) has sent an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR, the HSS continues processing as follows: + +if information about support / non-support of IMS voice over PS sessions from both serving nodes are identical, the HSS returns this information to the Application Server. UE Activity Time and the Last RAT Type are not reported. + +if information about support / non-support of IMS voice over PS sessions from both serving nodes are not identical, the HSS continues processing as follows: + +if the serving node that sent an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR did not indicate support of T-ADS Data Retrieval within the previous ULR, a response indicating IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported. + +otherwise the HSS retrieves T-ADS Data from the serving node that sent an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR. When the response is received, the HSS returns a response to the Application Server indicating the response from MME or SGSN whichever reported the most recent UE Activity Time. UE Activity Time and the Last RAT Type are also reported. + +# --- Annex F (normative): Diameter overload control mechanism + +## F.1 General + +Diameter overload control mechanism is an optional feature. + +IETF RFC 7683 [36] specifies a Diameter overload control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes. + +It is recommended to make use of IETF RFC 7683 [36] on the Sh interface where, when applied, the AS shall behave as a reacting node and the HSS as a reporting node. + +Depending on regional/national requirements and network operator policy, priority traffic (e.g. MPS as described in 3GPP TS 22.153 [38]) shall be exempted from throttling due to Diameter overload control up to the point where requested traffic reduction cannot be achieved without throttling the priority traffic. + +## --- F.2 HSS behaviour + +The HSS requests traffic reduction from the AS when the HSS is in an overload situation, including OC-OLR AVP in answer commands as described in IETF RFC 7683 [36]. + +The HSS identifies that it is in an overload situation by implementation specific means. For example, the HSS may take into account the traffic over the Sh interfaces or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources, etc. + +The HSS determines the specific contents of OC-OLR AVP in overload reports and the HSS decides when to send OC-OLR AVPs by implementation specific means. + +## --- F.3 AS behaviour + +The AS applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [36]. + +The AS achieves requested traffic reduction by implementation specific means. For example, the AS may implement message throttling with prioritization or a message retaining mechanism for operations that can be postponed. + +Diameter requests related to priority traffic (e.g. MPS) and emergency, detected via the presence of priority information (e.g., Resource-Priority header field for MPS) in SIP messages as described in 3GPP TS 24.229 [39], have the highest priority. Depending on regional/national regulatory and operator policies, these Diameter requests shall be the last to be throttled, when the AS has to apply traffic reduction. Relative priority amongst various priority traffic (e.g. MPS) and emergency traffic is subject to regional/national regulatory and operator policies. + +# --- Annex G (Informative): Diameter overload node behaviour + +## G.1 Message prioritization + +This clause describes possible behaviours of the AS regarding message prioritization in an informative purpose. + +The AS may take the following into account when making throttling decisions: + +- Identification of the procedures that can be deferred (e.g. Subscription to notification of Data Update), so to avoid to drop non deferrable procedures; +- Prioritization of certain types of request (e.g. between PUR and SNR) according to the context of their use, in particular: + - Higher prioritization of commands for AS that are related to a registered user for a service, so to avoid the interruption of the registered service for the user. + - Lower prioritization of commands for AS that are related to massive subscription data update due to provisioning. + - Priority level of a priority user (e.g., MPS user). + +# --- Annex H (Informative): Data shared among multiple subscribers + +## H.1 General + +This clause applies only to Repository Data. + +As defined by this specification, Repository Data is updated using a Sh-Update procedure per subscriber and Service Indication. This means that when Repository Data needs to be modified, it requires an update operation per subscriber, even if the same Repository Data is also part of other subscribers' data set. + +If Repository Data for a specific Service Indication is shared by a large amount of subscribers, it implies a large amount of update operations, which may trigger a large amount of notifications if any AS subscribed to changes for these corresponding subscribers. + +See 3GPP TS 29.364 [40] for a description of a solution to avoid this massive amount of update operations. However, it is important to remark that there may be other implementation specific solutions that handle data sharing among multiple individual subscribers. + +# --- Annex I (normative): Diameter message priority mechanism + +## I.1 General + +IETF draft-ietf-drmp-02 [42] specifies a Diameter message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation, set the DSCP marking for transport of the associated Diameter message, and also abatement decisions when overload control is applied. + +## 1.2 Sh/Dh interface + +### 1.2.1 General + +The Diameter message priority mechanism is an optional feature. + +It is recommended to make use of IETF draft-ietf-drmp-02 [42] over the Sh/Dh interface of an operator network when the overload control defined in Annex F is applied on this Sh/Dh interface. + +### 1.2.2 AS/OSA SCS behaviour + +When the AS/OSA SCS supports the Diameter message priority mechanism, the AS/OSA SCS shall comply with IETF RFC 7944 [42]. + +The AS/OSA SCS sending a request shall determine the required priority according to its policies. When priority is required, the AS/OSA SCS shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to priority level received. + +When the AS/OSA SCS receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request. + +When the AS/OSA SCS receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response. + +If: + +- the AS/OSA SCS supports using the Diameter message priority mechanism for DSCP marking purposes, +- the transport network utilizes DSCP marking, and +- message-dependant DSCP marking is possible for the protocol stack transporting Diameter, + +then the AS/OSA SCS shall set the DSCP marking for transport of the request or response according to the required priority level. + +Diameter requests related to priority traffic (e.g. MPS as identified by the AS through SIP procedures, emergency) shall contain a DRMP AVP with a high priority of which the level value is operator dependent. + +When not-explicitly requested, the inclusion and priority value of the DRMP AVP in Diameter messages are implementation specific. + +### 1.2.3 HSS/SLF behaviour + +When the HSS/SLF supports the Diameter message priority mechanism, the HSS/SLF shall comply with IETF RFC 7944 [42]. + +The HSS/SLF sending a request shall determine the required priority according to its policies. When priority is required, the HSS/SLF shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level. + +When the HSS/SLF receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request. + +When the HSS/SLF receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response. + +If: + +- the HSS/SLF supports using the Diameter message priority mechanism for DSCP marking purposes, +- the transport network utilizes DSCP marking, and +- message-dependant DSCP marking is possible for the protocol stack transporting Diameter, + +then the HSS/SLF shall set the DSCP marking for transport of the request or response according to the required priority level. + +When not-explicitly requested, the inclusion and priority value of the DRMP AVP in Diameter messages are implementation specific. + +### I.2.4 Interactions + +If the HSS/SLF supporting the Diameter message priority mechanism receives the request message containing both the Session-Priority AVP and DRMP AVP, the HSS/SLF shall prioritize the request according to priority level received within the DRMP AVP. + +# --- Annex J (normative): Diameter load control mechanism + +## J.1 General + +Diameter load control mechanism is an optional feature. + +It is recommended to make use of IETF RFC 8583 [43] on the Sh interface where, when applied, the AS shall behave as reacting nodes and the HSS as a reporting node. + +## --- J.2 HSS behaviour + +The HSS may report its current load by including a Load AVP of type HOST in answer commands as described in IETF RFC 8583 [43]. + +The HSS calculates its current load by implementation specific means. For example, the HSS may take into account the traffic over the Sh interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc. + +The HSS determines when to send Load AVPs of type HOST by implementation specific means. + +## --- J.3 AS behaviour + +When performing next hop Diameter Agent selection for requests that are routed based on realm, the AS may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [43]. + +# Annex K (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|-----------|-------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------|-------| +| Jun 2002 | CN#16 | NP-020277 | | | | Version 2.0.0 approved at CN#16 | 5.0.0 | +| Sep 2002 | CN#17 | NP-020450 | 1 | 1 | | The Correction of Clause 7 Numbering and internal referencing | 5.1.0 | +| Sep 2002 | CN#17 | NP-020450 | 2 | 1 | | Correction of handling of subscriptions to notifications | 5.1.0 | +| Sep 2002 | CN#17 | NP-020450 | 3 | 1 | | Definition of User Location for Sh interface | 5.1.0 | +| Sep 2002 | CN#17 | NP-020450 | 4 | 1 | | Definition of User State for Sh interface | 5.1.0 | +| Sep 2002 | CN#17 | NP-020450 | 5 | - | | Missing references to XML schema for Sh interface | 5.1.0 | +| Sep 2002 | CN#17 | NP-020450 | 6 | - | | Extensibility of XML schema for Sh interface | 5.1.0 | +| Dec 2002 | CN#18 | NP-020592 | 007 | - | | Removal of upper bounds in Sh i/f user profile and correction of mistake in XML schema documentation | 5.2.0 | +| Dec 2002 | CN#18 | NP-020593 | 008 | 1 | | Clarification on update of repository data | 5.2.0 | +| Dec 2002 | CN#18 | NP-020593 | 009 | 1 | | Removing the DDF dependencies from Sh interface | 5.2.0 | +| Dec 2002 | CN#18 | NP-020592 | 013 | 2 | | Error handling in HSS when being updated with too much data | 5.2.0 | +| Dec 2002 | CN#18 | NP-020591 | 014 | - | | Correction of the SPI | 5.2.0 | +| Jan 2003 | | | | | | Restoration of Annex E | 5.2.1 | +| Mar 2003 | CN#19 | NP-030102 | 012 | 3 | | Initial Filter Criteria | 5.3.0 | +| Mar 2003 | CN#19 | NP-030102 | 015 | - | | Deletion of Annex E | 5.3.0 | +| Mar 2003 | CN#19 | NP-030102 | 016 | 2 | | Update after Diameter has become RFC | 5.3.0 | +| Mar 2003 | CN#19 | NP-030102 | 017 | 1 | | Correction to application server identity | 5.3.0 | +| Mar 2003 | CN#19 | NP-030102 | 018 | 2 | | Clarification on Sh interface for charging purposes | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 019 | 2 | | Change of SPI to SPT | 5.3.0 | +| Apr 2003 | | | | | | ShDataType.xsd - file attached | 5.3.1 | +| Apr 2003 | | | | | | Updated ShDataType.xsd - file attached | 5.3.2 | +| Jun 2003 | CN#20 | NP-030216 | 022 | 1 | | Co-ordination of Update of Repository Data | 5.4.0 | +| Jun 2003 | CN#20 | NP-030216 | 023 | 1 | | Enhanced description of Sh-Pull Request and Response | 5.4.0 | +| Jun 2003 | CN#20 | NP-030216 | 024 | 2 | | Enhanced description of Sh-Notif and Sh-Notif-Subs Request and Response | 5.4.0 | +| Jun 2003 | CN#20 | NP-030216 | 025 | 2 | | A range of editorial changes and corrections and additions of references | 5.4.0 | +| Jun 2003 | CN#20 | NP-030216 | 027 | - | | Discrepancy between XML schema of Cx and Sh interface | 5.4.0 | +| Jun 2003 | CN#20 | NP-030216 | 029 | - | | Correction to the use of User-Identity | 5.4.0 | +| Jun 2003 | CN#20 | NP-030216 | 030 | - | | Clarification on the handling of the "Charging Information" via the Sh interface | 5.4.0 | +| Sep 2003 | CN#21 | NP-030384 | 032 | 2 | | Correction of message flow | 5.5.0 | +| Sep 2003 | CN#21 | NP-030384 | 033 | 2 | | Correction of Sh data definition in Annex C and D | 5.5.0 | +| Sep 2003 | CN#21 | NP-030384 | 035 | 2 | | Mistakes in the XML schema | 5.5.0 | +| Dec 2003 | CN#22 | NP-030501 | 038 | - | | XML Schema Correction | 5.6.0 | +| Dec 2003 | CN#22 | NP-030501 | 041 | - | | The extensibility of the XML schema | 5.6.0 | +| Dec 2003 | CN#22 | NP-030518 | 042 | - | | Clarification of inclusion of elements in Charging Information | 5.6.0 | +| Dec 2003 | CN#22 | | | | | Reference [8] updated | 5.6.0 | +| Dec 2003 | CN#22 | NP-030510 | 026 | 3 | | Introduction of Presence Stage 3 (Ph) to the Sh interface | 6.0.0 | +| Mar 2004 | CN#23 | NP-040055 | 036 | 2 | | Dh interface | 6.1.0 | +| Mar 2004 | CN#23 | NP-040055 | 043 | 2 | | Clarification of the AS Permissions List and its relevance to table 7.6.1 | 6.1.0 | +| Mar 2004 | CN#23 | NP-040135 | 045 | 3 | | Clarification of which Public Identities are downloaded | 6.1.0 | +| June 2004 | CN#24 | NP-040220 | 0085 | 2 | | Mapping to Diameter AVP for Requested Identity Set | 6.2.0 | +| Sep 2004 | CN#25 | NP-040401 | 094 | 1 | | Triggering initial REGISTER messages | 6.3.0 | +| Sep 2004 | CN#25 | NP-040401 | 088 | 1 | | XML versioning | 6.3.0 | +| Dec 2004 | CN#26 | NP-040531 | 097 | 2 | | Removal of Notification of the Authentication Pending State upon Registration | 6.4.0 | +| Dec 2004 | CN#26 | NP-040531 | 102 | 2 | | Only One Error Required for the AS Permissions Table Checking Procedure | 6.4.0 | +| Dec 2004 | CN#26 | NP-040531 | 103 | - | | Default Handling of Error Cases | 6.4.0 | +| Dec 2004 | CN#26 | NP-040578 | 104 | - | | Access Key for Charging Information | 6.4.0 | +| Dec 2004 | CN#26 | NP-040578 | 108 | 2 | | Handling of Information Element marked as (M), (C) or (O) | 6.4.0 | +| Dec 2004 | CN#26 | NP-040531 | 101 | 1 | | Sh-Pull Data Download | 6.4.0 | +| Mar 2005 | CN#27 | NP-050031 | 099 | 5 | | Sh-Update needs to include Data-Reference to be future proof | 6.5.0 | +| Mar 2005 | CN#27 | NP-050038 | 111 | 1 | | Clarification on requested identity set | 6.5.0 | +| Mar 2005 | CN#27 | NP-050031 | 113 | - | | Align UML Model and the XML schema for Public Identity | 6.5.0 | +| Mar 2005 | CN#27 | NP-050031 | 116 | 1 | | Conditional Service indication in Sh-Subs-Notif | 6.5.0 | +| Mar 2005 | CN#27 | NP-050031 | 118 | - | | Sh Diameter AVP Mapping Correction | 6.5.0 | +| Mar 2005 | CN#27 | NP-050031 | 121 | 2 | | Clarification of Sh Access Keys | 6.5.0 | +| Mar 2005 | CN#27 | NP-050038 | 122 | 2 | | Multiple Terminals in Sh | 6.5.0 | +| Jun 2005 | CT#28 | CP-050082 | 127 | - | | Sh user-data correction | 6.6.0 | +| Jun 2005 | CT#28 | CP-050087 | 130 | 1 | | Sh procedures applicable to Public Service Identity | 6.6.0 | + +| | | | | | | | | +|----------|-------|-----------|------|---|--|-----------------------------------------------------------------------------------|-------| +| Jun 2005 | CT#28 | CP-050082 | 134 | 1 | | Behavior of HSS when it accepts Sh-Subs-Notif message | 6.6.0 | +| Jun 2005 | CT#28 | CP-050087 | 137 | 1 | | Editorial corrections | 6.6.0 | +| Jun 2005 | CT#28 | CP-050082 | 139 | - | | XML correction for iFC | 6.6.0 | +| Sep 2005 | CT#29 | CP-050283 | 146 | - | | Correction to Sh-IMS-Data for Initial Filter Criteria | 6.7.0 | +| Sep 2005 | CT#29 | CP-050283 | 152 | 1 | | ISDN-address correction | 6.7.0 | +| Sep 2005 | CT#29 | CP-050424 | 154 | - | | Update of the IETF RFC for tel URI | 6.7.0 | +| Sep 2005 | CT#29 | CP-050294 | 155 | 2 | | PSI Activation | 6.7.0 | +| Sep 2005 | CT#29 | CP-050282 | 160 | - | | Charging-Information correction | 6.7.0 | +| Dec 2005 | CT#30 | CP-050604 | 144 | 5 | | XML syntax correction | 6.8.0 | +| Dec 2005 | CT#30 | CP-050611 | 161 | 2 | | Correction of the use of Data Reference 10 for Public Service Identities | 6.8.0 | +| Dec 2005 | CT#30 | CP-050605 | 167 | - | | PSUState correction | 6.8.0 | +| Dec 2005 | CT#30 | CP-050625 | 162 | 3 | | Notification Efficiency | 7.0.0 | +| Dec 2005 | CT#30 | CP-050625 | 163 | 3 | | Management of Sh subscriptions | 7.0.0 | +| Mar 2006 | CT#31 | CP-060084 | 0168 | 2 | | User-Data in the response to Sh-Subs-Notif | 7.1.0 | +| Mar 2006 | CT#31 | CP-060084 | 0169 | 1 | | New error indications for the Sh-Subs-Notif procedure | 7.1.0 | +| Mar 2006 | CT#31 | CP-060065 | 0172 | 2 | | Handling of unknown errors | 7.1.0 | +| Mar 2006 | CT#31 | CP-060154 | 0176 | 2 | | PSI Activation | 7.1.0 | +| Jun 2006 | CT#32 | CP-060319 | 0178 | 2 | | Returning Null Data | 7.2.0 | +| Jun 2006 | CT#32 | CP-060319 | 0181 | 2 | | Modify description of clause 6.1.3 Subscription to notifications | 7.2.0 | +| Jun 2006 | CT#32 | CP-060319 | 0182 | 2 | | Sh interface efficiency improvement | 7.2.0 | +| Jun 2006 | CT#32 | CP-060319 | 0183 | 2 | | Sh result-code correction | 7.2.0 | +| Jun 2006 | CT#32 | CP-060308 | 0186 | 1 | | PSI Activation schema correction | 7.2.0 | +| Sep 2006 | CT#33 | CP-060417 | 0188 | 3 | | Definition of Activation State Information for IMS (DSAI) | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0190 | - | | Applying ORIGINATING UNREGISTERED state to Sh | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0191 | 2 | | Sh-Subs-Notif without Expiry Time | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0195 | 4 | | S-CSCF name in Sh | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0196 | 1 | | Public User Identity Grouping Information | 7.3.0 | +| Sep 2006 | CT#33 | CP-060399 | 0198 | 2 | | Correction of the relationship between Repository Data and Public Identities | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0199 | - | | Error to be sent if the identity can not be used for data reference | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0200 | 1 | | Errors to be sent in response to Sh-Notif | 7.3.0 | +| Dec 2006 | CT#34 | CP-060555 | 0204 | 1 | | Activation Status of a PSI | 7.4.0 | +| Dec 2006 | CT#34 | CP-060566 | 0207 | 1 | | UDA correction for the case that data does not exist in the HSS | 7.4.0 | +| Dec 2006 | CT#34 | CP-060566 | 0208 | - | | Grouping identities update | 7.4.0 | +| Dec 2006 | CT#34 | CP-060735 | 0209 | 3 | | Clarification regarding URI canonicalization – 29.328 | 7.4.0 | +| Mar 2007 | CT#35 | CP-070020 | 0211 | - | | CurrentLocation is a required Access Key for LocationInformation DataRef | 7.5.0 | +| Mar 2007 | CT#35 | CP-070020 | 0212 | - | | Clarification on interaction between DSAI and wildcarded PSI | 7.5.0 | +| Mar 2007 | CT#35 | CP-070020 | 0215 | - | | Presence of Information Elements in Sh-Subs-Notif | 7.5.0 | +| Mar 2007 | CT#35 | CP-070020 | 0219 | 1 | | Restriction in the instances of repository data | 7.5.0 | +| Jun 2007 | CT#36 | CP-070309 | 0221 | - | | Correction of XML schema | 7.6.0 | +| Jun 2007 | CT#36 | CP-070318 | 0224 | - | | Adding the Ability to Notify an AS with Charging Information | 7.6.0 | +| Jun 2007 | CT#36 | CP-070318 | 0227 | 1 | | Application Server subscription for Implicit Identities | 7.6.0 | +| Sep 2007 | CT#37 | CP-070527 | 0231 | 1 | | Handling of Empty Repository Data | 7.7.0 | +| Sep 2007 | CT#37 | CP-070527 | 0234 | - | | Handling of Charging Data by the HSS | 7.7.0 | +| Sep 2007 | CT#37 | CP-070527 | 0235 | 1 | | Wildcarded PSI as key in the Sh Interface | 7.7.0 | +| Sep 2007 | CT#37 | CP-070522 | 0238 | 1 | | Repository Data and Subscriptions for Wildcarded PSIs | 7.7.0 | +| Sep 2007 | CT#37 | CP-070527 | 0239 | 1 | | Aliases definition alignment with 23.228 | 7.7.0 | +| Nov 2007 | CT#38 | CP-070743 | 0241 | - | | PNR for Subscriptions to Notifications for all Identity Sets | 7.8.0 | +| Mar 2008 | CT#39 | CP-080019 | 0243 | - | | Wildcarded Public User Identities | 8.0.0 | +| Jun 2008 | CT#40 | CP-080267 | 0246 | - | | DSAI Corrections | 8.1.0 | +| Jun 2008 | CT#40 | CP-080261 | 0249 | 1 | | Realm and Host to be used for Charging | 8.1.0 | +| Sep 2008 | CT#41 | CP-080460 | 0247 | 4 | | Adding the Deletion Notification of a Public Identity to the AS | 8.2.0 | +| Sep 2008 | CT#41 | CP-080460 | 0257 | 1 | | Removal of subscription data related to AS permission which has been prohibited | 8.2.0 | +| Dec 2008 | CT#42 | CP-080708 | 0258 | 2 | | Usage of Public Identity Deleted Notification | 8.3.0 | +| | | CP-080707 | 0260 | - | | Support for IMS Service Level Trace | 8.3.0 | +| | | CP-080696 | 0261 | 3 | | Diameter Proxy Agent - an alternative User Identity to HSS resolution mechanism | 8.3.0 | +| Mar 2009 | CT#43 | CP-090036 | 0266 | 3 | | HSS Addresses | 8.4.0 | +| | | CP-090028 | 0267 | 4 | | Support for GPRS IMS Bundled Authentication (GIBA) in Sh | 8.4.0 | +| | | CP-090042 | 0268 | 3 | | Alias grouping handling | 8.4.0 | +| Jun 2009 | CT#44 | CP-090305 | 0271 | 1 | | IP address secure binding information shall not be allowed for shared IMPUs | 8.5.0 | +| | | CP-090302 | 0272 | 1 | | Correction for choice of CGI, SAI or LAI | | +| Sep 2009 | CT#44 | CP-090525 | 0280 | 1 | | Correction of the XML schema | 8.6.0 | +| | | CP-090546 | 0277 | 1 | | CR implementation correction | | +| | | CP-090553 | 0274 | - | | Indication that GIBA information is not available in Sh-Pull when using Notif-Eff | | +| Dec 2009 | CT#46 | CP-090778 | 0285 | 2 | | Session-Priority AVP | 8.7.0 | +| Dec 2009 | CT#46 | CP-090790 | 0288 | - | | Correction on Identity Set for PSI | 9.0.0 | + +| | | | | | | | | +|----------|-------|-----------|------|---|--|------------------------------------------------------------------------------------|--------| +| Mar 2010 | CT#47 | CP-100033 | 0293 | 1 | | Priority service attribute in Sh | 9.1.0 | +| | | CP-100033 | 0295 | 1 | | IP-SM-GW UE reachability handling over Sh. | | +| | | | 0300 | 1 | | SMS Registration Information | | +| | | CP-100048 | 0286 | 1 | | Sh handling of T-ADS | | +| | | CP-100017 | 0303 | 1 | | Correction of MSISDN as Access Key via Sh Interface | | +| | | CP-100029 | 0310 | 1 | | User CSG Information | | +| | | CP-100217 | 0311 | 5 | | EPS Subscriber State and Location Information Request | | +| May 2010 | | | | | | Xml-file corrected | 9.1.1 | +| Jun 2010 | CT#48 | CP-100412 | 0317 | 1 | | Update of IETF Reference | 9.2.0 | +| | | CP-100275 | 0314 | | | EPS state and location retrieval | | +| | | CP-100279 | 0322 | 1 | | URRP for SGSN | | +| Sep 2010 | CT#49 | CP-100447 | 0331 | | | Correction to the Values of Data-Reference AVP | 9.3.0 | +| | | CP-100454 | 0333 | | | Sh-Subs-Notif procedure clarification | | +| | | CP-100442 | 0336 | 1 | | Correction to Access IMSIPublicIdentity Data using MSISDN via Sh Interface | | +| Sep 2010 | CT#49 | CP-100522 | 0327 | 3 | | Usage of IMSI and IMPI for user identification over Sh | 10.0.0 | +| | | CP-100466 | 0332 | 3 | | Sh-Update with multiple Repository Data | | +| | | CP-100466 | 0337 | 1 | | Location data including only serving node address | | +| Dec 2010 | CT#50 | CP-100699 | 0340 | 4 | | SRVCC Enhancements | 10.1.0 | +| | | CP-100697 | 0342 | 1 | | Update the Reference of Alias | | +| | | CP-100671 | 0345 | 1 | | C-MSISDN over Sh | | +| | | CP-100671 | 0359 | | | SMS Registration with MSISDN | | +| | | CP-100677 | 0351 | 1 | | IE Requested Nodes is optional for backward compatibility reasons | | +| Jan 2011 | | | | | | Attached xml-file "tShIMSDatExtension4" part corrected. | 10.1.1 | +| Mar 2011 | CT#51 | CP-110044 | 0366 | | | Originating CDIV included as new Session Case | 10.2.0 | +| | | CP-110044 | 0374 | | | Cardinality and extensions corrections in XML schema | | +| | | CP-110060 | 0349 | 3 | | MPS over Sh | | +| | | CP-110075 | 0360 | 3 | | Retrieval of CSRN from HSS | | +| | | CP-110075 | 0363 | 4 | | Correction on Access Keys for data accessible via Sh and table format improvements | | +| | | CP-110082 | 0371 | | | SRVCC Subscription and STN-SR | | +| | | CP-110066 | 0375 | 1 | | Enhancements of T-ADS data retrieval via Sh | | +| | | CP-110075 | 0376 | 1 | | Requested Identity Set updated | | +| | | CP-110075 | 0378 | 1 | | Fix backwards incompatible change for Serving Node Indication | | +| | | CP-110075 | 0378 | 1 | | Fix backwards incompatible change for Serving Node Indication | | +| Jun 2011 | CT#52 | CP-110356 | 0384 | 1 | | Sh-Update with MSISDN | 10.3.0 | +| | | CP-110370 | 0380 | 3 | | SC Address in IP-SM-GW Register Response | | +| | | CP-110370 | 0381 | 2 | | Pre-paging Support Indicator for CSRN | | +| Jun 2011 | CT#52 | CP-110383 | 0377 | 4 | | Reference Location over Sh interface | 11.0.0 | +| Sep 2011 | CT#53 | CP-110576 | 0393 | 2 | | Clarification on Receiving Sh-Notif Error Response | 11.1.0 | +| Dec 2011 | CT#54 | CP-110781 | 0397 | 1 | | Class ApplicationServerExtension in Sh XML Schema | 11.2.0 | +| | | CP-110781 | 0405 | 1 | | Correction on Wildcarded Public Identity | | +| | | CP-110781 | 0408 | 2 | | Service Data with empty content in Sh | | +| | | CP-110809 | 0406 | 1 | | UE Reachability for IP attributes | | +| Mar 2012 | CT#55 | CP-120019 | 0421 | | | MME-Name reference | 11.3.0 | +| | | CP-120027 | 0418 | | | Missing tags in MSISDN type description | | +| | | CP-120027 | 0423 | 1 | | CSRN inconsistency between XML and text | | +| | | CP-120035 | 0415 | 2 | | Update of Multiple Data Instances in Sh-Update | | +| Jun 2012 | CT#56 | CP-120222 | 0427 | | | CSG-Id length | 11.4.0 | +| | | CP-120240 | 0416 | 4 | | Local Time for NPLI | | +| Sep 2012 | CT#57 | CP-120446 | 0437 | 2 | | T-ADS clarification | 11.5.0 | +| | | CP-120445 | 0435 | | | RAT-type coding | | +| | | CP-120445 | 0440 | | | Base64 coding | | +| | | CP-120460 | 0441 | 2 | | Clarification on T-ADS Information | | +| | | CP-120481 | 0442 | 3 | | A-MSISDN handling over Sh | | +| | | CP-120481 | 0443 | 2 | | Local Time Zone | | +| | | CP-120656 | 0444 | 1 | | Reference list correction to align with the corrected TS 29.212 title | | +| Dec 2012 | CT#58 | CP-120743 | 0446 | - | | Applicability of Send Data Indication | 11.6.0 | +| | | CP-120743 | 0450 | 1 | | Unavailable Data Handling | | +| | | CP-120743 | 0453 | 2 | | PS LocationInformation Support | | +| | | CP-120720 | 0449 | 1 | | UserCSGInformation in EPS Location Info | | +| Feb 2013 | | | | | | The version numbers in a history table corrected | 11.6.1 | +| Mar 2013 | CT#59 | CP-130018 | 0458 | 1 | | Private Identity as additional access key | 11.7.0 | +| | | CP-130020 | 0461 | 3 | | PS Location Info request with RAT-type | | +| Mar 2013 | CT#59 | CP-130031 | 0459 | 3 | | Sh IMSI retrieval | 12.0.0 | +| Jun 2013 | CT#60 | CP-130374 | 0466 | - | | IMPU As Access Key for User State and Location Information | 12.1.0 | +| | | CP-130374 | 0463 | 2 | | MTRR on Sh | | +| | | CP-130380 | 0464 | 1 | | Storing Last known Location Information of purged UE in HSS | | +| | | CP-130410 | 0469 | 1 | | HSS handling of T-ADS for detached subscriber | | +| Sep 2013 | CT#61 | CP-130441 | 0476 | 1 | | XML definitions for CS Location Information Extension | 12.2.0 | +| | | CP-130448 | 0471 | 1 | | Missing tags | | +| | | CP-130461 | 0472 | - | | Correction on Wrong Implementation of CR | | + +| | | | | | | | | +|----------|-------|-----------|------|---|--|---------------------------------------------------------------------------------|--------| +| | | CP-130461 | 0477 | - | | tISDNAddress | | +| Dec 2013 | CT#62 | CP-130614 | 0479 | 3 | | T-ADS Information Retrieval for Gn/Gp-SGSN | 12.3.0 | +| | | CP-130627 | 0480 | - | | Annex D alignment with .xsd file | | +| Mar 2014 | CT#63 | CP-140027 | 0483 | - | | Notification of UE SRVCC Capability Update | 12.4.0 | +| | | CP-140027 | 0484 | 1 | | Clarification on Current Location Retrieved | | +| | | CP-140027 | 0485 | 1 | | Clarification to Notif-Eff | | +| | | CP-140027 | 0486 | 2 | | Suppression of Announcement Indication | | +| Jun 2014 | CT#64 | CP-140238 | 0491 | - | | IP-SM-GW address handling clarification | 12.5.0 | +| | | CP-140238 | 0493 | 1 | | Extended priority is missing in UML model | | +| | | CP-140252 | 0487 | 5 | | Retrieval of TWAN-Id over Sh | | +| | | CP-140262 | 0489 | 2 | | Private User Identity retrieval | | +| Sep 2014 | CT#65 | CP-140503 | 0497 | - | | Repository data retrieval | 12.6.0 | +| | | CP-140515 | 0495 | 1 | | Unsuccessful multiple repository data update | | +| | | CP-140509 | 0498 | 1 | | Diameter Overload Control Over Sh | | +| | | CP-140519 | 0499 | 1 | | Add Logical Access ID for Sh | | +| Dec 2014 | CT#66 | CP-140755 | 0502 | 2 | | Access Key for Service Priority Level | 12.7.0 | +| | | CP-140766 | 0501 | - | | tMSISDN Type | | +| | | CP-140790 | 0503 | 1 | | Priority Consideration for Diameter Overload Control | | +| | | CP-140790 | 0509 | - | | DOIC reference update | | +| | | CP-140773 | 0508 | 1 | | T-ADS Clarification | | +| Mar 2015 | CT#67 | CP-150023 | 0510 | 1 | | HSS access keys for multiple data references | 12.8.0 | +| Mar 2015 | CT#67 | CP-150040 | 0511 | 2 | | IMS service data shared among multiple subscribers | 13.0.0 | +| | | CP-150038 | 0512 | - | | T-ADS clarification | | +| Jun 2015 | CT#68 | CP-150243 | 0524 | 1 | | IFC XML alignment with Cx | 13.1.0 | +| | | CP-150246 | 0527 | - | | Location info XML Corrections | | +| | | CP-150251 | 0514 | - | | Sh-Notif when the HSS supports both Update-Eff and Notif-Eff | | +| | | CP-150273 | 0515 | 1 | | Only Repository Data can be shared among multiple subscribers | | +| | | CP-150264 | 0518 | - | | STN-SR Sh-Update introduction clarification | | +| | | CP-150264 | 0525 | 1 | | IP-SM-GW registration with Diameter | | +| | | CP-150264 | 0526 | - | | Access key for ExtendedPriority | | +| Sep 2015 | CT#69 | CP-150444 | 0529 | - | | Update-Eff-Enhance | 13.2.0 | +| Dec 2015 | CT#70 | CP-150743 | 0535 | 1 | | Correction on the Encoding of IP Addresses | 13.3.0 | +| | | CP-150759 | 0539 | 1 | | Update reference to DOIC new IETF RFC | | +| | | CP-150750 | 0536 | 1 | | Only either WPSI or WIMPU present in requests | | +| | | CP-150750 | 0537 | 1 | | DSAI class multiplicity clarification | | +| | | CP-150848 | 0540 | 4 | | DRMP AVP Procedures over Sh/Dh | | +| Mar 2016 | CT#71 | CP-160014 | 0555 | 1 | | Encoding of SC Address | 13.4.0 | +| | | CP-160046 | 0543 | 2 | | Data returned in IMSPublicIdentity correction | | +| | | CP-160013 | 0551 | 1 | | Encoding of IP-SM-GW Number | | +| | | CP-160046 | 0544 | 2 | | Local Time Zone for CS retrieval | | +| | | CP-160046 | 0556 | 1 | | Length correction for tVPLMNID and tTimeZone | | +| Jun 2016 | CT#72 | CP-160213 | 0560 | | | One time notification mandatory in Sh-Subs-Notif for UE reachability for IP | 13.5.0 | +| Jun 2016 | CT#72 | CP-160239 | 0557 | 1 | | Location information alignment with XML | 13.5.0 | +| Jun 2016 | CT#72 | CP-160215 | 0562 | 1 | | Diameter requests for priority traffic during overload control mechanism | 13.5.0 | +| 2016-09 | CT#73 | CP-160415 | 0565 | 1 | | Notification of changes to RepositoryData for an Alias Public User Identity Set | 13.6.0 | +| 2016-09 | CT#73 | CP-160431 | 566 | 1 | | Request to update data while a previous update request is in progress | 14.0.0 | +| 2016-12 | CT#74 | CP-160672 | 0574 | 1 | | Notif-Eff in Sh-Pull | 14.1.0 | +| 2016-12 | CT#74 | CP-160649 | 0583 | - | | Xsd syntax correction | 14.1.0 | +| 2016-12 | CT#74 | CP-160649 | 0584 | 1 | | RAT type included in EPS location information | 14.1.0 | +| 2016-12 | CT#74 | CP-160681 | 0585 | 1 | | Load Control | 14.1.0 | +| 2016-12 | CT#74 | CP-160664 | 0587 | - | | Correction to change IETF drmp draft version to official RFC 7944 | 14.1.0 | +| 2017-03 | CT#75 | CP-170035 | 0589 | - | | Notif-Eff feature corrections in relation to Identity Set | 14.2.0 | +| 2017-03 | CT#75 | CP-170035 | 0591 | 1 | | Notification of changes to concurrent subscriptions to multiple Identity Sets | 14.2.0 | +| 2017-03 | CT#75 | CP-170035 | 0592 | 1 | | DeletedIdentities for IMSPublicIdentities | 14.2.0 | +| 2017-03 | CT#75 | CP-170035 | 0594 | - | | UDR flag description | 14.2.0 | +| 2017-03 | CT#75 | CP-170048 | 0593 | 1 | | Update of reference for the Diameter base protocol | 14.2.0 | +| 2017-06 | CT#76 | CP-171028 | 0595 | 2 | | Handling of EPS Location Information Retrieval | 14.3.0 | +| 2017-06 | CT#76 | CP-171034 | 0598 | 1 | | IMS Trace (ISAT) Reference Updates | 14.3.0 | +| 2017-06 | CT#76 | CP-171018 | 0602 | 2 | | Support for signaling transport level packet marking | 14.3.0 | +| 2017-06 | CT#76 | CP-171040 | 0596 | 1 | | External Identifier on Sh | 15.0.0 | +| 2017-06 | CT#76 | CP-171040 | 0597 | 1 | | IMEI retrieval over Sh | 15.0.0 | +| 2017-09 | CT#77 | CP-172016 | 0604 | - | | Cardinality of Reference Location Information | 15.1.0 | +| 2017-09 | CT#77 | CP-172013 | 0607 | - | | Correction of DRMP Procedures | 15.1.0 | +| 2017-12 | CT#78 | CP-173015 | 0610 | - | | Incorrect Implementation of CR#588 (C4-166303) | 15.2.0 | +| 2018-06 | CT#80 | CP-181131 | 0612 | - | | Sh Location Information in 5GS | 15.3.0 | +| 2018-09 | CT#81 | CP-182069 | 0613 | 2 | | T-ADS info retrieval | 15.4.0 | +| 2018-09 | CT#81 | CP-182069 | 0614 | 1 | | UE reachability in 5GC | 15.4.0 | +| 2018-09 | CT#81 | CP-182069 | 0615 | 2 | | Sh User State in 5GS | 15.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------|--------| +| 2018-12 | CT#82 | CP-183094 | 0618 | 2 | | Time offset for last UE activity time via Sh | 15.5.0 | +| 2018-12 | CT#82 | CP-183094 | 0619 | 2 | | Clarification on TADS procedure | 15.5.0 | +| 2018-12 | CT#82 | CP-183094 | 0617 | | | Sh-IMSI retrieval | 15.5.0 | +| 2019-03 | CT#83 | CP-190048 | 0620 | - | | NR Cell Global ID | 15.6.0 | +| 2019-03 | CT#83 | CP-190035 | 0621 | 1 | | SMSF address in 5GS Location Information | 15.6.0 | +| 2019-03 | CT#83 | CP-190048 | 0622 | 1 | | Clean up and clarification on transmission of the T-ADS information towards the AS | 15.6.0 | +| 2019-03 | CT#83 | CP-190164 | 0623 | - | | Sh XML schema correction | 15.6.0 | +| 2019-09 | CT#85 | CP-192094 | 0626 | 2 | | draft-ietf-dime-load published as RFC 8583 | 15.7.0 | +| 2019-09 | CT#85 | CP-192125 | 0624 | 1 | | 5GS User State | 15.7.0 | +| 2019-12 | CT#86 | CP-193020 | 0630 | - | | Implementation error of CR#0564 | 15.8.0 | +| 2020-03 | CT#87e | CP-200022 | 0631 | 2 | | Introduce support for accessing 5G SRVCC data via Sh | 16.0.0 | +| 2020-06 | CT#88e | CP-201038 | 0623 | 1 | | Introduce support for 5G SRVCC support indication | 16.1.0 | +| 2020-06 | CT#88e | CP-201036 | 0634 | - | | Remove Editor's Note regarding obtaining 4G SRVCC capability from UDM | 16.1.0 | +| 2020-12 | CT#90e | CP-203022 | 0641 | 1 | | Incomplete implemented CR | 16.2.0 | +| 2020-12 | CT#90e | CP-203026 | 0637 | 1 | | 5G Location Information retrieval | 16.2.0 | +| 2020-12 | CT#90e | CP-203056 | 0635 | - | | Subscription to notification of IMEI change | 17.0.0 | +| 2021-03 | CT#91e | CP-210031 | 0642 | - | | Local Time Zone Request | 17.1.0 | +| 2021-06 | CT#92e | CP-211037 | 0643 | - | | 29.328 Table key addition | 17.2.0 | +| 2022-03 | CT#95e | CP-220063 | 0645 | - | F | Unavailable Location Information | 17.3.0 | +| 2022-09 | CT#97e | CP-222027 | 0646 | - | B | Add SBI support Indication for IP-SM-GW registration via Sh | 17.4.0 | +| 2022-09 | CT#97e | CP-222022 | 0648 | - | F | Reference clarification for Tracking Area ID | 18.0.0 | +| 2023-03 | CT#99 | CP-230054 | 0649 | - | F | Serving Node Indication | 18.1.0 | +| 2023-03 | CT#99 | CP-230054 | 0650 | - | F | User State | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29344/raw.md b/marked/Rel-18/29_series/29344/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..650fbc8511ec1b695f0d5e42b79c74ee6a3e6ec9 --- /dev/null +++ b/marked/Rel-18/29_series/29344/raw.md @@ -0,0 +1,1189 @@ + + +# 3GPP TS 29.344 V18.0.0 (2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Proximity-services (ProSe) Function to Home Subscriber Server (HSS) aspects; Stage 3 (Release 18)** + +![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for LTE Advanced Pro, featuring the letters 'lte' in a bold, lowercase font. Above the 'e' is a green signal icon with three bars. To the right of the 'e' are the words 'Advanced' and 'Pro' in a smaller font, with 'Pro' in red. + +LTE Advanced Pro logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized, bold font. The '3' and 'G' are connected at the top. Below the 'P' is a red signal icon with three bars. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 General Description ..... | 7 | +| 4.1 Introduction ..... | 7 | +| 5 Procedure Descriptions ..... | 7 | +| 5.1 Introduction ..... | 7 | +| 5.2 ProSe Subscriber Information Retrieval ..... | 8 | +| 5.2.1 General ..... | 8 | +| 5.2.2 Detailed Behaviour of the ProSe Function ..... | 8 | +| 5.2.3 Detailed Behaviour of the HSS ..... | 9 | +| 5.3 Update ProSe Subscriber Data ..... | 9 | +| 5.3.1 General ..... | 9 | +| 5.3.2 Detailed behaviour of the ProSe Function..... | 10 | +| 5.3.3 Detailed behaviour of the HSS ..... | 11 | +| 5.4 Notification Procedure ..... | 11 | +| 5.4.1 General ..... | 11 | +| 5.4.2 Detailed Behaviour of the ProSe Function ..... | 12 | +| 5.4.3 Detailed Behaviour of the HSS ..... | 12 | +| 5.5 Reset..... | 13 | +| 5.5.1 General ..... | 13 | +| 5.5.2 Detailed behaviour of the ProSe Function..... | 13 | +| 5.5.3 Detailed behaviour of the HSS ..... | 14 | +| 5.6 Initial Location Information Retrieval ..... | 14 | +| 5.6.1 General ..... | 14 | +| 5.6.2 Detailed Behaviour of the ProSe Function ..... | 15 | +| 5.6.3 Detailed Behaviour of the HSS ..... | 15 | +| 6 Protocol Specification and Implementations ..... | 16 | +| 6.1 Introduction ..... | 16 | +| 6.1.1 Use of Diameter Base Protocol ..... | 16 | +| 6.1.2 Securing Diameter Messages ..... | 16 | +| 6.1.3 Accounting Functionality ..... | 16 | +| 6.1.4 Use of Sessions..... | 16 | +| 6.1.5 Transport Protocol..... | 16 | +| 6.1.6 Routing Considerations ..... | 16 | +| 6.1.7 Advertising Application Support..... | 17 | +| 6.1.8 Diameter Application Identifier ..... | 17 | +| 6.1.9 Use of the Supported-Features AVP ..... | 17 | +| 6.2 Commands..... | 17 | +| 6.2.1 Introduction ..... | 17 | +| 6.2.2 Command-Code Values..... | 17 | +| 6.2.3 ProSe-Subscriber-Information-Request (PIR) Command..... | 18 | +| 6.2.4 ProSe-Subscriber-Information-Answer (PIA) Command ..... | 18 | +| 6.2.5 Update-ProSe-Subscriber-Data-Request (UPR) Command ..... | 19 | +| 6.2.6 Update-ProSe-Subscriber-Data-Answer (UPA) Command ..... | 19 | +| 6.2.7 ProSe-Notify-Request (PNR) Command ..... | 20 | +| 6.2.8 ProSe-Notify-Answer (PNA) Command..... | 20 | +| 6.2.9 Reset-Request (RSR) Command ..... | 20 | +| 6.2.10 Reset-Answer (RSA) Command ..... | 21 | +| 6.2.11 ProSe-Initial-Location-Information-Request (PSR) Command..... | 21 | + +| | | | +|-------------------------------|---------------------------------------------------------------|-----------| +| 6.2.12 | ProSe-Initial-Location-Information-Answer (PSA) Command ..... | 21 | +| 6.3 | AVPs ..... | 22 | +| 6.3.1 | General ..... | 22 | +| 6.3.2 | ProSe-Subscription-Data ..... | 23 | +| 6.3.3 | ProSe-Permission ..... | 23 | +| 6.3.4 | ProSe-Allowed-PLMN ..... | 24 | +| 6.3.5 | ProSe-Direct-Allowed ..... | 24 | +| 6.3.6 | UPR-Flags ..... | 25 | +| 6.3.7 | PNR-Flags ..... | 25 | +| 6.3.8 | Feature-List AVP for the PC4a application ..... | 26 | +| 6.3.9 | ProSe-Initial-Location-Information ..... | 26 | +| 6.3.10 | MME-Name ..... | 27 | +| 6.3.11 | OC-Supported-Features ..... | 27 | +| 6.3.12 | OC-OLR ..... | 27 | +| 6.3.13 | Authorized-Discovery-Range ..... | 27 | +| 6.3.14 | DRMP ..... | 27 | +| 6.3.15 | Load ..... | 27 | +| 6.4 | Result-Code AVP and Experimental-Result AVP Values ..... | 27 | +| 6.4.1 | General ..... | 27 | +| 6.4.2 | Success ..... | 27 | +| 6.4.3 | Permanent Failures ..... | 27 | +| 6.4.3.1 | General ..... | 27 | +| 6.4.3.2 | DIAMETER_ERROR_USER_UNKNOWN (5001) ..... | 28 | +| 6.4.3.3 | DIAMETER_ERROR_UNKNOWN_PROSE_SUBSCRIPTION (5610) ..... | 28 | +| 6.4.3.4 | DIAMETER_ERROR_PROSE_NOT_ALLOWED (5611) ..... | 28 | +| 6.4.3.5 | DIAMETER_ERROR_UE_LOCATION_UNKNOWN (5612) ..... | 28 | +| Annex A (normative): | Diameter overload control mechanism ..... | 29 | +| A.1 | General ..... | 29 | +| A.2 | HSS behaviour ..... | 29 | +| A.3 | ProSe Function behaviour ..... | 29 | +| Annex B (Informative): | Diameter overload node behaviour ..... | 29 | +| B.1 | Message prioritization ..... | 29 | +| Annex C (normative): | Diameter message priority mechanism ..... | 30 | +| C.1 | General ..... | 30 | +| C.2 | PC4a interface ..... | 30 | +| C.2.1 | General ..... | 30 | +| C.2.2 | HSS and ProSe Function behaviour ..... | 30 | +| Annex D (normative): | Diameter load control mechanism ..... | 31 | +| D.1 | General ..... | 31 | +| D.2 | HSS behaviour ..... | 31 | +| D.3 | ProSe Function behaviour ..... | 31 | +| Annex E (informative): | Change history ..... | 31 | + +# --- 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 describes the Diameter-based PC4a interface between the Proximity-based Services (ProSe) Function and the Home Subscriber Server (HSS) defined for ProSe. + +This specification defines the Diameter application for PC4a reference point between the ProSe Function and the HSS. The interactions between the ProSe Function and the HSS are specified. + +The stage 2 description for Proximity-based Services (ProSe) features in EPS is specified in 3GPP TS 23.303 [2]. + +# --- 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 23.303: "Proximity based services; Stage 2". +- [3] Void. +- [4] 3GPP TS 33.210: "3G Security; Network Domain Security; IP Network Layer Security". +- [5] IETF RFC 4960: "Stream Control Transmission Protocol". +- [6] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol". +- [7] 3GPP TS 23.003: "Numbering, addressing and identification". +- [8] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF". +- [9] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and Message Elements". +- [10] 3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol". +- [11] 3GPP TS 23.007: "Restoration procedures". +- [12] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol". +- [13] void +- [14] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane LCS". +- [15] IETF RFC 7683: "Diameter Overload Indication Conveyance". +- [16] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3". +- [17] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO); Stage 3". + +- [18] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [19] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging". +- [20] 3GPP TS 32.298: "Charging Management; CDR parameter description". +- [21] IETF RFC 7944: "Diameter Routing Message Priority". +- [22] IETF RFC 8583: "Diameter Load Information Conveyance". +- [23] IETF RFC 6733: "Diameter Base Protocol". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|------------------------------------| +| DRMP | Diameter Routing Message Priority | +| DSCP | Differentiated Services Code Point | +| ProSe | Proximity-based Services | + +# --- 4 General Description + +## 4.1 Introduction + +The PC4a reference point between the ProSe Function and the HSS is defined in the 3GPP TS 23.303 [2]. + +This document describes the PC4a interface related procedures, message parameters and protocol specifications. + +The PC4a interface allows the ProSe Function to retrieve ProSe related subscription data in order to authorise access from the UE for ProSe. + +# --- 5 Procedure Descriptions + +## 5.1 Introduction + +This clause describes the Diameter-based PC4a interface related procedures and information elements exchanged between the ProSe Function and the HSS. + +In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in clause 6 of the 3GPP TS 29.228 [9]. + +## 5.2 ProSe Subscriber Information Retrieval + +### 5.2.1 General + +This procedure shall be used between the ProSe Function and the HSS for authorization of the UE for ProSe. The procedure shall be invoked by the ProSe Function and is used: + +- to request ProSe related subscription data. + +This procedure is mapped to the commands ProSe-Subscriber-Information-Request/Answer (PIR/PIA) in the Diameter application specified in clause 6. Tables 5.2.1-1 and 5.2.1-2 detail the involved information elements. + +**Table 5.2.1-1: ProSe Subscriber Information Retrieval Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|------------------------------------|------|--------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name (See IETF RFC 6733 [23]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [7], clause 2.2. | +| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +**Table 5.2.1-2: ProSe Subscriber Information Retrieval Answer** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result (See 6) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]). The Experimental-Result AVP shall be used for PC4a errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. The following errors are applicable:
- User Unknown
- Unknown ProSe Subscription
- ProSe Not Allowed | +| ProSe Subscription Data (See 6.3.2) | ProSe-Subscription-Data | C | This information element shall contain the ProSe Subscription Data that gives the user permission to use ProSe. | +| MSISDN (See 3GPP TS 29.329 [12]) | MSISDN | C | This information element shall contain the user MSISDN, formatted according to 3GPP TS 29.329 [12]. It shall be present if available. | +| Visited PLMN Id (See 3GPP TS 29.272 [10]) | Visited-PLMN-Id | C | This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPP TS 23.003 [7]. It shall be present if the UE is roaming in a PLMN different from the Home PLMN. | +| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Reset-IDs (See 3GPP TS 29.272 [10]) | Reset-ID | O | The Reset-ID uniquely identifies a fallible resource in the HSS's realm on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers. | + +### 5.2.2 Detailed Behaviour of the ProSe Function + +The ProSe Function shall make use of this procedure to request ProSe related subscription data. + +If the ProSe Function retrieved the ProSe related subscription data, the ProSe Function shall perform the authorisation for ProSe as described in the 3GPP TS 23.303 [2]. + +### 5.2.3 Detailed Behaviour of the HSS + +When receiving a ProSe Subscriber Information Retrieval Request the HSS shall check if the IMSI for whom data is requested exists in the HSS. If not, an Experimental-Result of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If the IMSI exists but there is not any ProSe subscription data for the IMSI, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_UNKNOWN\_PROSE\_SUBSCRIPTION. + +If the UE is not allowed to use ProSe in the visited PLMN, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_PROSE\_NOT\_ALLOWED. Otherwise, the HSS shall return a Result-Code of DIAMETER\_SUCCESS and shall store ProSe Function identity (the ProSe Function identity is received within the Origin-Host AVP) and download the ProSe subscription data to the ProSe Function. The HSS shall provide the Visited PLMN ID of where the UE is registered if the UE is roaming in a PLMN different from the Home PLMN. + +## 5.3 Update ProSe Subscriber Data + +### 5.3.1 General + +The Update ProSe Subscriber Data procedure shall be used between the ProSe Function and the HSS to update the subscriber related data downloaded by means of the ProSe Subscriber Information Retrieval operation (see clause 5.2) and stored in the ProSe Function. + +It shall be used to update subscriber related data in the ProSe Function due to administrative changes of the user data in the HSS, i.e. if the user was given a subscription and the subscription has changed. It shall be used at least to perform the following: + +- update of all of ProSe subscription data of the subscriber, +- update of a subset of the ProSe subscription data of the subscriber, +- deletion of the ProSe subscription data of the subscriber. + +The procedure will also be triggered when the VPLMN has changed. + +This procedure is mapped to the commands Update-ProSe-Subscriber-Data-Request/Answer (UPR/UPA) in the Diameter application specified in clause 6. + +Table 5.3.1-1 specifies the involved information elements for the request. + +Table 5.3.1-2 specifies the involved information elements for the answer. + +**Table 5.3.1-1: Update ProSe Subscriber Data Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|---------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name
(See IETF RFC 6733 [23]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [7], clause 2.2. | +| Supported Features
(See 3GPP TS 29.229 [6]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| ProSe Subscription Data
(See 6.3.2) | ProSe-Subscription-Data | C | This information element shall contain the ProSe Subscription Data that gives the user permission to use ProSe. | +| Visited PLMN Id
(See 3GPP TS 29.272 [10]) | Visited-PLMN-Id | C | This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPP TS 23.003 [7].
It shall be present if the UE is roaming in a PLMN different from the Home PLMN. | +| UPR Flags | UPR-Flags | M | This Information Element shall contain a bit mask. See clause 6.3.6 for the meaning of the bits. | +| Reset-IDs
(See 3GPP TS 29.272 [10]) | Reset-ID | O | The Reset-ID uniquely identifies a fallible resource in the HSS's realm on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers. | + +**Table 5.3.1-2: Update ProSe Subscriber Data Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features
(See 3GPP TS 29.229 [6]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result
(See 6.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]).
The Experimental-Result AVP shall be used for PC4a errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable in this case:
- User Unknown
- Unknown ProSe Subscription | + +### 5.3.2 Detailed behaviour of the ProSe Function + +When receiving a Update ProSe Subscriber Data request, the ProSe Function shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If it is known, the ProSe Function shall update the corresponding data according to the indication as sent in the request, and acknowledge the Update ProSe Subscriber Data message by returning an Update ProSe Subscriber Data Answer. If the UPR-Flags indicates that the ProSe subscription data is to be deleted, the ProSe Function shall delete the associated ProSe UE context if it has been stored before. + +If the update of the subscription data succeeds in the ProSe Function, the Result-Code shall be set to DIAMETER\_SUCCESS. + +If the ProSe Function cannot fulfil the received request for other reasons, e.g. due to a database error, it shall set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. In this case, the ProSe Function shall mark the subscription record "Subscriber data to be restored in the HSS". + +### 5.3.3 Detailed behaviour of the HSS + +The HSS shall make use of this procedure to update the relevant subscriber related data in the the ProSe Function to replace a specific part of the user data stored in the ProSe Function with the data sent. + +If the ProSe related subscription data is updated or revoked, the HSS sends the updated ProSe subscription data to the ProSe Function. The HSS shall include the UPR-Flags to indicate which part of the data is updated. If all of the ProSe subscription data is to be removed, the HSS shall set the "Removal of all ProSe Subscription Data" bit of the UPR-Flags, and the HSS shall delete the ProSe Function Identity if it is stored for this subscriber. + +## 5.4 Notification Procedure + +### 5.4.1 General + +This procedure shall be used between the ProSe Function and the HSS when the HSS needs to be notified about: + +- revocation of authorization for ProSe direct service on one PLMN. +- removal of the subscription data from the ProSe Function either by an MMI interaction or automatically. + +This procedure is mapped to the commands ProSe-Notify-Request/Answer (PNR/PNA) in the Diameter application specified in clause 6. Tables 5.4.1-1 and 5.4.1-2 detail the involved information elements. + +**Table 5.4.1-1: ProSe Notify Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|------------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name (See IETF RFC 6733 [23]) | C | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [7], clause 2.2. It shall be present if the revocation is for a specific UE. | +| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| PLMN ID (see 3GPP TS 29.272 [10]) | Visited-PLMN-Id | C | This information element shall contain the MCC and the MNC of the PLMN where the UE's authorization for ProSe direct service is revoked, see 3GPP TS 23.003 [7]. It shall be present if the ProSe Function revokes the authorization for ProSe direct service in a specific PLMN. | +| PNR Flags (see 6.3.7) | PNR-Flags | C | This Information Element shall contain a bit mask. See 6.3.7 for the meaning of the bits. | + +Table 5.4.1-2: ProSe Notify Answer + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|--------------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6) | Result-Code /
Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]).
The Experimental-Result AVP shall be used for PC4a errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable:
- User Unknown
- Unknown ProSe Subscription | +| Supported Features
(See 3GPP TS 29.229 [6]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +### 5.4.2 Detailed Behaviour of the ProSe Function + +The ProSe Function shall make use of this procedure to revoke authorization for ProSe direct service. + +The ProSe Function shall make use of this procedure to inform the HSS when the subscription data is deleted from the ProSe Function database due to MMI interaction or automatically. + +The ProSe Function shall send the updated ProSe Permission and the PLMN ID for which the ProSe Permission is to be updated. If the revocation is for a single UE in the indicated PLMN, the ProSe Function shall include IMSI in the request. + +### 5.4.3 Detailed Behaviour of the HSS + +When receiving a ProSe Notify Request the HSS shall check if the IMSI, if present in the message, exists in the HSS. If not, an Experimental-Result of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If the IMSI exists but there is not any ProSe subscription data for the IMSI and the PLMN ID as indicated by the Visited-PLMN-Id AVP in the request, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_UNKNOWN\_PROSE\_SUBSCRIPTION. + +If the PNR-Flags indicates revocation of authorization for ProSe direct service, and + +- if the IMSI exists and there is ProSe subscription data for the IMSI and the PLMN ID as indicated by the Visited-PLMN-Id AVP in the request, the HSS shall revoke ProSe direct service as indicated by the PNR Flags received in the request on that PLMN for the user and update the ProSe Subscription data accordingly. The HSS shall set the result code to DIAMETER\_SUCCESS. +- if IMSI is not present in the message, the HSS shall check if there are any users subscribed to ProSe subscription for the PLMN as indicated by the Visited-PLMN-Id AVP in the request, and if yes, revoke ProSe direct service as indicated by the PNR Flags received in the request on that PLMN for all the impacted users and update their ProSe Subscription data accordingly. The HSS shall set the result code to DIAMETER\_SUCCESS. + +If the PNR Flags indicates the subscription data is deleted from the ProSe Function, the HSS shall remove the ProSe Function Identity for the subscriber and set the result code to DIAMETER\_SUCCESS. + +For any other reasons if the HSS cannot fulfil the received request, e.g. due to a database error, it shall set the result code to DIAMETER\_UNABLE\_TO\_COMPLY. + +## 5.5 Reset + +### 5.5.1 General + +The Reset Procedure shall be used by the HSS, after a restart, to indicate to the ProSe Function that a failure has occurred. + +The Reset Procedure may also be used by the HSS as part of operation and maintenance actions e.g. to allow planned HSS outage without service interruption. + +This procedure is mapped to the commands Reset-Request/Answer (RSR/RSA) in the Diameter application specified in clause 6. + +Table 5.5.1-1 specifies the involved information elements for the request. + +Table 5.5.1-2 specifies the involved information elements for the answer. + +**Table 5.5.1-1: Reset Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------------------------|-------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Id List
(See 3GPP TS 29.2 72 [10]) | User-Id | O | This IE shall contain a list of ProSe User-Ids where a ProSe User-Id comprises the leading digits of an IMSI (i.e. MCC, MNC, leading digits of MSIN) and it shall identify the set of subscribers whose IMSIs begin with the User-Id. The HSS may include this information element if the occurred failure is limited to subscribers identified by one or more User-Ids. | +| Supported Features
(See 3GPP TS 29.2 29 [6]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Reset-IDs
(See 3GPP TS 29.2 72 [10]) | Reset-ID | O | If present, this information element identifies together with the HSS's realm the set of impacted subscribers. | + +**Table 5.5.1-2: Reset Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features
(See 3GPP TS 29.2 29 [6]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result
(See 6.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]).
The Experimental-Result AVP shall be used for PC4a errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
There are no Experimental-Result codes applicable for this command. | + +### 5.5.2 Detailed behaviour of the ProSe Function + +When receiving a Reset message the ProSe Function shall mark all impacted subscriber records "Subscriber DataConfirmed in HSS" as "Not Confirmed", as defined in 3GPP TS 23.007 [11]. If the Reset-IDs IE is supported and received, the ProSe Function shall make use of the Reset-IDs (together with the HSS's realm) in order to determine which subscriber records are impacted (i.e. check whether at least one received Reset-ID is associated with the subscriber, and the HSS's realm identity received in the Origin-Realm AVP matches the value stored after successful ProSe-Subscriber-Information retrieval); otherwise the ProSe Function shall make use of the HSS Identity received in + +the Origin-Host AVP (by comparing it with the value stored after successful ProSe-Subscriber-Information retrieval) and may make use of the received User-Id-List (if any) in order to determine which subscriber records are impacted. + +### 5.5.3 Detailed behaviour of the HSS + +The HSS shall make use of this procedure in order to indicate to all relevant ProSe Functions that the HSS has restarted and may have lost the current ProSe Function Identity of some of its subscribers who may be currently roaming in the ProSe Function Area and that the HSS, therefore, cannot send an Update ProSe Subscriber Data messages when needed. + +If the Reset-ID feature is not supported by the ProSe Function and the HSS, the HSS may include a list of User Ids identifying a subset of subscribers served by the HSS, if the occurred failure is limited to those subscribers. + +If the Reset-ID feature is supported by the ProSe Function, the HSS optionally may include one (or several) Reset-ID AVPs identifying e.g. failed hardware components if the occurred failure is limited to those subscribers associated with e.g. the identified failed hardware components. + +## 5.6 Initial Location Information Retrieval + +### 5.6.1 General + +This procedure shall be used between the ProSe Function and the HSS for retrieving the initial location information of the UE for EPC-level ProSe discovery. The procedure shall be invoked by the ProSe Function and is used: + +- to request the initial location information of the UE. + +This procedure is mapped to the commands ProSe-Initial-Location-Information-Request/Answer (PLR/PLA) in the Diameter application specified in clause 6. + +Table 5.4.1/1 specifies the involved information elements for the request. + +Table 5.4.1/2 specifies the involved information elements for the answer. + +**Table 5.6.1/1: ProSe Initial Location Information Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-----------------------------------|------|--------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name (See ETF RFC 6733 [23]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [7], clause 2.2. | +| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +**Table 5.6.1/2: ProSe Initial Location Information Answer** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------------|--------------------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6) | Result-Code /
Experimental-
Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]).
The Experimental-Result AVP shall be used for PC4a errors.
This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable:
- User Unknown
- UE Location Unknown | +| ProSe Initial Location Information
(See 6.3.9) | ProSe-Initial-
Location-
Information | C | This information element shall contain the location information of the UE. | +| Visited PLMN Id
(See 3GPP TS 29.272 [10]) | Visited-PLMN-Id | C | This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPP TS 23.003 [7].
It shall be present if the UE is roaming in a PLMN different from the Home PLMN. | +| Supported Features
(See 3GPP TS 29.229 [6]) | Supported-
Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +### 5.6.2 Detailed Behaviour of the ProSe Function + +To request the initial location information of the targeted UE, the ProSe Function shall include the corresponding IMSI in the user profile of the targeted user in ProSe Initial Location Information Request. + +NOTE: The user profile for the targeted user is stored in the ProSe Function according to clause 7.2.2.3 of 3GPP TS 24.334 [16]. + +### 5.6.3 Detailed Behaviour of the HSS + +When receiving a ProSe Initial Location Information Request the HSS shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If it is known and the MME is not the serving node currently registered in HSS for the UE, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_UE\_LOCATION\_UNKNOWN. If it is known and the MME is the serving node currently registered in HSS for the UE, the HSS shall return a Result-Code of DIAMETER\_SUCCESS and provide the location information of the UE to the ProSe Function. The HSS shall provide the Visited PLMN ID of where the UE is registered if the UE is roaming in a PLMN different from the Home PLMN. + +NOTE: When requesting the UE location via S6a, the HSS does not set the "Current Location Request" bit in the IDR-Flags in the Insert Subscriber Data Request message. + +# 6 Protocol Specification and Implementations + +## 6.1 Introduction + +### 6.1.1 Use of Diameter Base Protocol + +The Diameter base protocol as specified in IETF RFC 6733 [23] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +### 6.1.2 Securing Diameter Messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [4] + +### 6.1.3 Accounting Functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the PC4a interface. + +### 6.1.4 Use of Sessions + +Between the ProSe Function and the HSS, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server. + +The Diameter base protocol specified in IETF RFC 6733 [23] includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [23]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +### 6.1.5 Transport Protocol + +Diameter messages over the PC4a interface shall make use of SCTP, see IETF RFC 4960 [5]. + +### 6.1.6 Routing Considerations + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. + +The PC4a reference point is defined as an intra-operator interface, and both the ProSe Function and the HSS are located in the home PLMN of the UE that requests ProSe. If the ProSe Function knows the address/name of the HSS for a certain user, both the Destination-Realm and Destination-Host AVPs shall be present in the request. Otherwise, the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by the ProSe Function. + +The HSS obtains the Destination-Host AVP to use in requests towards the ProSe Function, from the Origin-Host AVP received in previous requests from the ProSe Function. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the HSS. + +If the Vendor-Specific-Application-ID AVP is received in any of the commands, it shall be ignored by the receiving node, and it shall not be used for routing purposes. + +### 6.1.7 Advertising Application Support + +The ProSe Function and the HSS shall advertise support of the Diameter PC4a Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [23]. + +### 6.1.8 Diameter Application Identifier + +The PC4a interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. + +The Diameter application identifier assigned to the PC4a interface application is 16777336 (allocated by IANA). + +### 6.1.9 Use of the Supported-Features AVP + +When new functionality is introduced on the PC4a interface, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the PC4a interface is consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2 of 3GPP TS 29.229 [6]. + +When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. + +As defined in 3GPP TS 29.229 [6], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another. + +## 6.2 Commands + +### 6.2.1 Introduction + +This clause defines the Command code values and related ABNF for each command described in this specification. + +### 6.2.2 Command-Code Values + +This clause defines Command-Code values for the PC4a interface application as allocated by IANA. + +Every command is defined by means of the ABNF syntax IETF RFC 5234 [8], according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [23]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [23] shall apply. + +The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node. + +**NOTE:** The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with the IETF RFC 6733 [23]. + +The following Command Codes are defined in this specification: + +**Table 6.2.2-1: Command-Code values for PC4a** + +| Command-Name | Abbreviation | Code | Clause | +|--------------------------------------------|--------------|---------|--------| +| ProSe-Subscriber-Information-Request | PIR | 8388664 | 6.2.3 | +| ProSe-Subscriber-Information-Answer | PIA | 8388664 | 6.2.4 | +| Update-ProSe-Subscriber-Data-Request | UPR | 8388665 | 6.2.5 | +| Update-ProSe-Subscriber-Data-Answer | UPA | 8388665 | 6.2.6 | +| ProSe-Notify-Request | PNR | 8388666 | 6.2.7 | +| ProSe-Notify-Answer | PNA | 8388666 | 6.2.8 | +| Reset-Request | RSR | 322 | 6.2.9 | +| Reset-Answer | RSA | 322 | 6.2.10 | +| ProSe-Initial-Location-Information-Request | PSR | 8388713 | 6.2.11 | +| ProSe-Initial-Location-Information-Answer | PSA | 8388713 | 6.2.12 | + +For these commands, the Application-ID field shall be set to 16777336 (application identifier of the PC4a interface application, allocated by IANA). + +### 6.2.3 ProSe-Subscriber-Information-Request (PIR) Command + +The ProSe-Subscriber-Information-Request (PIR) command, indicated by the Command-Code field set to 8388664 and the "R" bit set in the Command Flags field, is sent from the ProSe Function to the HSS. + +Message Format + +``` +< ProSe-Subscriber-Information-Request > ::= < Diameter Header: 8388664, REQ, PXY, 16777336 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ Destination-Host ] +{ Destination-Realm } +{ User-Name } +*[ Supported-Features ] +[ OC-Supported-Features ] +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +### 6.2.4 ProSe-Subscriber-Information-Answer (PIA) Command + +The ProSe-Subscriber-Information-Answer (PIA) command, indicated by the Command-Code field set to 8388664 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the ProSe Function. + +Message Format + +``` +< ProSe-Subscriber-Information-Answer > ::= < Diameter Header: 8388664, PXY, 16777336 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +``` + +``` + +{ Origin-Realm } +[ ProSe-Subscription-Data ] +[ MSISDN ] +[ Visited-PLMN-Id ] +*[ Supported-Features ] +[ OC-Supported-Features ] +[ OC-OLR ] +*[ Load ] +*[ AVP ] +*[ Reset-ID ] +[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.2.5 Update-ProSe-Subscriber-Data-Request (UPR) Command + +The Update-ProSe Subscriber Data-Request (UPR) command, indicated by the Command-Code field set to 8388665 and the 'R' bit set in the Command Flags field, is sent from the HSS to the ProSe Function. + +Message Format when used over the PC4a application: + +``` + +< Update-ProSe-Subscriber-Data-Request > ::= < Diameter Header: 8388665, REQ, PXY, 16777336 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +{ Destination-Host } +{ Destination-Realm } +{ User-Name } +*[ Supported-Features ] +[ ProSe Subscription-Data ] +[ Visited-PLMN-Id ] +{ UPR-Flags } +*[ Reset-ID ] +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.2.6 Update-ProSe-Subscriber-Data-Answer (UPA) Command + +The Update-ProSe Subscriber Data-Answer (UPA) command, indicated by the Command-Code field set to 8388665 and the 'R' bit cleared in the Command Flags field, is sent from the ProSe Function to the HSS. + +Message Format when used over the PC4a application: + +``` + +< Update-ProSe-Subscriber-Data-Answer > ::= < Diameter Header: 8388665, PXY, 16777336 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +*[ Supported-Features ] +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +*[ AVP ] +[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.2.7 ProSe-Notify-Request (PNR) Command + +The ProSe-Notify-Request (PNR) command, indicated by the Command-Code field set to 8388666 and the "R" bit set in the Command Flags field, is sent from the ProSe Function to the HSS. + +#### Message Format + +``` +< ProSe-Notify-Request > ::= < Diameter Header: 8388666, REQ, PXY, 16777336 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + [ User-Name ] + [ ProSe-Permission ] + [ Visited-PLMN-Id ] + [ PNR-Flags ] + *[ Supported-Features ] + [ OC-Supported-Features ] + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +### 6.2.8 ProSe-Notify-Answer (PNA) Command + +The ProSe-Notify-Answer (PNA) command, indicated by the Command-Code field set to 8388666 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the ProSe Function. + +#### Message Format + +``` +< ProSe-Notify-Answer > ::= < Diameter Header: 8388666, PXY, 16777336 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + *[ Supported-Features ] + [ OC-Supported-Features ] + [ OC-OLR ] + *[ Load ] + *[ AVP ] + [ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +### 6.2.9 Reset-Request (RSR) Command + +The Reset-Request (RSR) command, indicated by the Command-Code field set to 322 and the 'R' bit set in the Command Flags field, is sent from HSS to the ProSe Function. + +#### Message Format when used over the PC4a application: + +``` +< Reset-Request > ::= < Diameter Header: 322, REQ, PXY, 16777336 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] +``` + +``` + +{ Origin-Host } +{ Origin-Realm } +{ Destination-Host } +{ Destination-Realm } +*[ Supported-Features ] +*[ User-Id ] +*[ Reset-ID ] +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] + +``` + +### 6.2.10 Reset-Answer (RSA) Command + +The Reset-Answer (RSA) command, indicated by the Command-Code field set to 322 and the 'R' bit cleared in the Command Flags field, is sent from ProSe Function to HSS. + +Message Format when used over the PC4a application: + +``` + +< Reset-Answer > ::= < Diameter Header: 322, PXY, 16777336 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] + *[ Supported-Features ] + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + *[ AVP ] + [ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +### 6.2.11 ProSe-Initial-Location-Information-Request (PSR) Command + +The ProSe-Initial-Location-Information-Request (PSR) command, indicated by the Command-Code field set to 8388713 and the "R" bit set in the Command Flags field, is sent from the ProSe Function to the HSS. + +Message Format + +``` + +< ProSe-Subscriber-Information-Request > ::= < Diameter Header: 8388713, REQ, PXY, 16777336 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + { User-Name } + *[ Supported-Features ] + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +### 6.2.12 ProSe-Initial-Location-Information-Answer (PSA) Command + +The ProSe-Initial-Location-Information-Answer (PSA) command, indicated by the Command-Code field set to 8388713 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the ProSe Function. + +Message Format + +``` + +< ProSe-Subscriber-Information-Answer > ::= < Diameter Header: 8388713, PXY, 16777336 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ ProSe-Initial-Location-Information ] + [ Visited-PLMN-Id ] + *[ Supported-Features ] + *[ AVP ] + [ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +## 6.3 AVPs + +### 6.3.1 General + +The following table specifies the Diameter AVPs defined for the PC4a interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415). + +**Table 6.3.1-1: PC4a specific Diameter AVPs** + +| Attribute Name | AVP Code | Clause defined | Value Type | AVP Flag rules | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | May Encr. | +| ProSe-Subscription-Data | 3701 | 6.3.2 | Grouped | M,V | | | | No | +| ProSe-Permission | 3702 | 6.3.3 | Unsigned32 | M,V | | | | No | +| ProSe-Allowed-PLMN | 3703 | 6.3.4 | Grouped | M,V | | | | No | +| ProSe-Direct-Allowed | 3704 | 6.3.5 | Unsigned32 | M,V | | | | No | +| UPR-Flags | 3705 | 6.3.6 | Unsigned32 | M,V | | | | No | +| PNR-Flags | 3706 | 6.3.7 | Unsigned32 | M,V | | | | No | +| ProSe-Initial-Location-Information | 3707 | 6.3.9 | Grouped | M,V | | | | No | +| NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [23]. | | | | | | | | | +| NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. | | | | | | | | | + +The following table specifies the Diameter AVPs re-used by the PC4a interface protocol from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within PC4a. + +Any other AVPs from existing Diameter Applications, except for the AVPs from Diameter Base Protocol, do not need to be supported. The AVPs from Diameter Base Protocol are not included in table 6.3.1-2, but they may be re-used for the PC4a protocol. + +Table 6.3.1-2: PC4a re-used Diameter AVPs + +| Attribute Name | Reference | Comments | M-bit | +|-------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| Visited-PLMN-Id | 3GPP TS 29.272 [10] | | | +| Supported-Features | 3GPP TS 29.229 [6] | | | +| Feature-List-ID | 3GPP TS 29.229 [6] | | | +| Feature-List | 3GPP TS 29.229 [6] | | | +| User-Id | 3GPP TS 29.272 [10] | See clause 6.3.8 | | +| Reset-ID | 3GPP TS 29.272 [10] | | | +| MSISDN | 3GPP TS 29.329 [12] | | | +| MME-Name | 3GPP TS 29.173 [14] | See clause 6.3.10 | | +| E-UTRAN-Cell-Global-Identity | 3GPP TS 29.272 [10] | | | +| Tracking-Area-Identity | 3GPP TS 29.272 [10] | | | +| Age-Of-Location-Information | 3GPP TS 29.272 [10] | | | +| 3GPP-Charging-Characteristics | 3GPP TS 29.061 [18] | See 3GPP TS 32.251 [19] Annex A and 3GPP TS 32.298 [20] clause 5.1.2.2.7. This attribute holds the ProSe-related Charging Characteristics for a ProSe subscriber. | Must set | +| OC-Supported-Features | IETF RFC 7683 [15] | See clause 6.3.11 | Must set | +| OC-OLR | IETF RFC 7683 [15] | See clause 6.3.12 | Must set | +| DRMP | IETF RFC 7944 [21] | see clause 6.3.14 | Must not set | +| Load | IETF RFC 8583 [22] | See clause 6.3.15 | Must not set | + +NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies. + +NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. + +### 6.3.2 ProSe-Subscription-Data + +The ProSe-Subscription-Data AVP is of type Group. It shall contain the ProSe related subscription data. + +AVP format + +``` +ProSe-Subscription-Data ::= + { ProSe-Permission } + *[ ProSe-Allowed-PLMN ] + [ 3GPP-Charging-Characteristics ] + *[AVP] +``` + +### 6.3.3 ProSe-Permission + +The ProSe-Permission AVP is of type Unsigned32 and it shall contain a bit mask that indicates the permissions for ProSe subscribed by the user. The meaning of the bits shall be as defined in table 6.3.3/1: + +Table 6.3.3-1: ProSe-Permission + +| Bit | Name | Description | +|-------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| 0 | ProSe Direct Discovery | This bit, when set, indicates that the user is allowed to use ProSe Direct Discovery. | +| 1 | EPC-level ProSe Discovery | This bit, when set, indicates that the user is allowed to use EPC-level ProSe Discovery. | +| 2 | EPC support WLAN Direct Discovery and Communication | This bit, when set, indicates that the user is allowed to use EPC support WLAN Direct Discovery and Communication. | +| 3 | one-to-many ProSe Direct Communication | This bit, when set, indicates that the user is allowed to use one-to-many ProSe Direct Communication. | +| 4 | one-to-one ProSe Direct Communication | This bit, when set, indicates that the user is allowed to use one-to-one ProSe Direct Communication. | +| 5 | UE-to-Network Relay | This bit, when set, indicates that the user is allowed to act as a UE-to-Network relay. | +| 6 | Remote-UE-access | This bit, when set, indicates that the user is allowed to act as a Remote-UE. | +| 7 | Restricted ProSe Direct Discovery | This bit, when set, indicates that the user is allowed to use restricted ProSe Direct Discovery. | +| NOTE: | Bits not defined in this table shall be cleared by the HSS and discarded by the receiving ProSe Function. | | + +### 6.3.4 ProSe-Allowed-PLMN + +The ProSe-Allowed-PLMN AVP is of type Group. It shall contain the PLMN where the UE is authorised to announce or monitor or both for ProSe Discovery or to use ProSe direct communication. + +AVP format + +ProSe-Allowed-PLMN ::= + +[ Visited-PLMN-Id ] + +[ Authorized-Discovery-Range ] + +[ ProSe-Direct-Allowed ] + +\*[AVP] + +The Authorized-Discovery-Range Information Element should only be present if the Visited-PLMN-Id is the PLMN-Id of the HPLMN; otherwise it should be absent. + +### 6.3.5 ProSe-Direct-Allowed + +The ProSe-Direct-Allowed AVP is of type Unsigned32 and it shall contain a bit mask that indicates the services the UE is authorised to use for ProSe Direct functionalities in a specific PLMN. The meaning of the bits shall be as defined in table 6.3.5-1: + +**Table 6.3.5-1: ProSe-Direct-Allowed** + +| Bit | Name | Description | +|-----------------------------------------------------------------------------------------------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Announce | This bit, when set, indicates that the user is allowed to announce in the corresponding PLMN for open ProSe Discovery. | +| 1 | Monitor | This bit, when set, indicates that the user is allowed to monitor in the corresponding PLMN for open ProSe Discovery. | +| 2 | Communication | This bit, when set, indicates that the user is allowed for ProSe direct one to many communication in the corresponding PLMN. | +| 3 | One-to-one Communication | This bit, when set, indicates that the user is allowed to perform one-to-one ProSe Direct Communication. | +| 4 | Discoverer | This bit, when set, indicates that the user is allowed to perform discoverer operation in the corresponding PLMN for ProSe Discovery Model B. | +| 5 | Discoveree | This bit, when set, indicates that the user is allowed to perform discoveree operation in the corresponding PLMN for ProSe Discovery Model B. | +| 6 | Restricted-announce | This bit, when set, indicates that the user is allowed to announce in the corresponding PLMN for restricted ProSe Discovery. | +| 7 | Restricted-monitoring | This bit, when set, indicates that the user is allowed to monitor in the corresponding PLMN for restricted ProSe Discovery. | +| 8 | Application-controlled extension | This bit, when set, indicates that the user is allowed to announce or monitor with application-controlled extension in the corresponding PLMN for restricted ProSe Discovery | +| 9 | On-demand announcing | This bit, when set, indicates that the user is allowed to perform on-demand announcing in the corresponding PLMN for restricted ProSe Discovery | +| NOTE: Bits not defined in this table shall be cleared by the HSS and discarded by the receiving ProSe Function. | | | + +### 6.3.6 UPR-Flags + +The UPR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits is defined in table 6.3.6-1: + +**Table 6.3.6-1: UPR-Flags** + +| Bit | Name | Description | +|-------------------------------------------------------------------------------------------------------------------------|------------------|------------------------------------------------------------------------------------------| +| 0 | Update | This bit, when set, indicates that the ProSe subscriber related data are updated. | +| 1 | Removal | This bit, when set, indicates that all of the ProSe subscriber related data are removed. | +| 2 | Reset-ID Update | This bit, when set, indicates that the complete list on Reset-IDs is updated. | +| 3 | Reset-ID Removal | This bit, when set, indicates that the complete list on Reset-IDs is removed. | +| NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving ProSe Function. | | | + +### 6.3.7 PNR-Flags + +The PNR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.7-1: + +**Table 6.3.7-1: PNR-Flags** + +| bit | name | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Direct Discovery Revoked | This bit, when set, shall indicate to the HSS that the authorization for ProSe direct discovery is to be revoked on the indicated PLMN. | +| 1 | Direct Communication Revoked | This bit, when set, shall indicate to the HSS that the authorization for ProSe direct communication is to be revoked on the indicated PLMN. | +| 2 | Purged UE | This bit, when set, shall indicate to the HSS that the subscriber's data has been deleted from the ProSe Function. | +| NOTE 1: Bits not defined in this table shall be cleared by the sending ProSe Function and discarded by the receiving HSS.
NOTE 2: If Purged UE bit is set, all other bits in this table shall be cleared by the sending ProSe Function and discarded by the receiving HSS. | | | + +### 6.3.8 Feature-List AVP for the PC4a application + +The syntax of this AVP is defined in 3GPP TS 29.229 [6]. + +For the PC4a application, the meaning of the bits shall be as defined in table 6.3.8/1 for the Feature-List-ID 1. + +**Table 6.3.8/1: Features of Feature-List-ID 1 used in PC4a** + +| Feature bit | Feature | M/O | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Reset-IDs | O | Support of Reset-IDs
This feature is applicable to the PIR/PIA and UPR/UPA and RSR/RSA command pairs over the PC4a interface.
If the ProSe Function indicates in the PIR command that it does not support Reset-IDs, the HSS shall not include Reset-ID AVPs in RSR commands sent to that Prose Function. | +| Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1".
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "ODB-HPLMN-APN".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").
Description: A clear textual description of the feature. | | | | + +Features that are not indicated in the Supported-Features AVPs within a given application message shall not be used to construct that message. + +### 6.3.9 ProSe-Initial-Location-Information + +The ProSe-Initial-Location-Information AVP is of type Grouped. This AVP shall contain the location information of the UE. + +AVP format + +ProSe-Initial-Location-Information ::= + +[MME-Name] + +[E-UTRAN-Cell-Global-Identity] + +[Tracking-Area-Identity] + +[Age-Of-Location-Information] + +\*[AVP] + +### 6.3.10 MME-Name + +The MME-Name AVP is of type DiameterIdentity. This AVP shall contain the Diameter identity of the serving MME and is specified in 3GPP TS 29.173 [14] clause 6.4.4. + +### 6.3.11 OC-Supported-Features + +The OC-Supported-Features AVP is of type Grouped and it is defined in IETF RFC 7683 [15]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information. + +### 6.3.12 OC-OLR + +The OC-OLR AVP is of type Grouped and it is defined in IETF RFC 7683 [15]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information. + +### 6.3.13 Authorized-Discovery-Range + +The Authorized-Discovery-Range AVP is of type Unsigned32 and it shall contain a value that indicates the authorised announcing range (short/medium/long) at which the UE is allowed to announce in the given PLMN according to the defined announcing authorisation policy for this UE. Refer to 3GPP TS 24.334 [16] for the policy handling and to 3GPP TS 24.333 [17] for the possible values of the range. + +### 6.3.14 DRMP + +The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [21]. This AVP allows the HSS and the ProSe Function to indicate the relative priority of Diameter messages over the PC4a interface. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message. + +### 6.3.15 Load + +The Load AVP is of type Grouped and it is defined in IETF RFC 8583 [22]. This AVP is used to support Diameter load control mechanism, see Annex D for more information. + +## 6.4 Result-Code AVP and Experimental-Result AVP Values + +### 6.4.1 General + +This clause defines result code values that shall be supported by all Diameter implementations that conform to this specification. + +### 6.4.2 Success + +Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter base protocol specified in IETF RFC 6733 [23] shall be applied. + +### 6.4.3 Permanent Failures + +#### 6.4.3.1 General + +Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in Diameter base protocol specified in IETF RFC 6733 [23] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent. + +#### 6.4.3.2 DIAMETER\_ERROR\_USER\_UNKNOWN (5001) + +This result code shall be sent by the HSS to indicate that the user identified by the IMSI is unknown. This error code is defined in 3GPP TS 29.229 [6]. + +#### 6.4.3.3 DIAMETER\_ERROR\_UNKNOWN\_PROSE\_SUBSCRIPTION (5610) + +This result code shall be sent by the HSS to indicate that no ProSe subscription is associated with the IMSI. + +#### 6.4.3.4 DIAMETER\_ERROR\_PROSE\_NOT\_ALLOWED (5611) + +This result code shall be sent by the HSS to indicate that ProSe is not allowed to be used in the specific PLMN where the UE is registered. + +#### 6.4.3.5 DIAMETER\_ERROR\_UE\_LOCATION\_UNKNOWN (5612) + +This result code shall be sent by the HSS to indicate that the initial location of the UE is unknown. + +# --- Annex A (normative): Diameter overload control mechanism + +## A.1 General + +Diameter overload control mechanism is an optional feature. + +IETF RFC 7683 [15] specifies a Diameter overload control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes. + +It is recommended to make use of IETF RFC 7683 [15] on the PC4a interface where, when applied, the ProSe Function shall behave as reacting nodes and the HSS as a reporting node. + +## A.2 HSS behaviour + +The HSS requests traffic reduction from the ProSe Function when it is in an overload situation, including OC-OLR AVP in answer commands as described in IETF RFC 7683 [15]. + +The HSS identifies that it is in an overload situation by implementation specific means. For example, the HSS may take into account the traffic over the PC4a interface or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources, etc. + +The HSS determines the specific contents of OC-OLR AVP in overload reports and the HSS decides when to send OC-OLR AVPs by implementation specific means. + +## A.3 ProSe Function behaviour + +The ProSe Function applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [15]. + +The ProSe Function achieves requested traffic reduction by implementation specific means. For example, the ProSe Function may implement message throttling with prioritization or a message retaining mechanism for operations that can be postponed. As a result of the need to throttle traffic, the ProSe Function may reject Registration Request, Discovery Request, Proximity Requests initiated by UEs. The possible related error messages used over PC3 are described in the 3GPP TS 24.334 [16]. + +# --- Annex B (Informative): Diameter overload node behaviour + +## B.1 Message prioritization + +This clause describes possible behaviours of the ProSe Function regarding message prioritisation in an informative purpose. + +The ProSe Function may take the following into account when making throttling decisions: + +- Identification of the procedures that can be deferred (e.g. Proximity Requests), so to avoid to drop non deferrable procedures; +- Prioritisation of certain types of request (e.g. between ProSe-Subscriber-Information-Request (PIR) and ProSe-Notify-Request (PNR)) according to the context of their use, in particular: + +- Higher prioritisation for commands that are related to a registered user for a service, so to avoid the interruption of the registered service for the user. + +# --- Annex C (normative): Diameter message priority mechanism + +## C.1 General + +IETF RFC 7944 [21] specifies a Diameter routing message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation, set the DSCP marking for transport of the associated Diameter message, and also abatement decisions when overload control is applied. + +## C.2 PC4a interface + +### C.2.1 General + +The Diameter message priority mechanism is an optional feature. + +It is recommended to make use of IETF RFC 7944 [21] over the PC4a interface of an operator network when the overload control defined in Annex A is applied on this PC4a interface. + +### C.2.2 HSS and ProSe Function behaviour + +When the HSS or the ProSe Function support the Diameter message priority mechanism over the PC4a interface, the HSS or the ProSe Function shall comply with IETF RFC 7944 [21]. + +The HSS or the ProSe Function sending a request shall determine the required priority according to its policies. When priority is required, the HSS or the ProSe Function shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level. + +When the HSS or the ProSe Function receive the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request. + +When the HSS or the ProSe Function receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, the HSS or the ProSe Function may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, the HSS or the ProSe Function shall include the DRMP AVP in the response. + +The HSS and the ProSe Function decisions for a required priority and for the priority level value are implementation specific. + +If: + +- the HSS and the ProSe Function supports using the Diameter message priority mechanism for DSCP marking purposes, +- the transport network utilizes DSCP marking, and +- message-dependant DSCP marking is possible for the protocol stack transporting Diameter, + +then the HSS and the ProSe Function shall set the DSCP marking for transport of the request or response according to the required priority level. + +Diameter requests related to high priority traffic shall contain a DRMP AVP with a high priority of which the level value is operator dependent. + +# --- Annex D (normative): Diameter load control mechanism + +## D.1 General + +Diameter load control mechanism is an optional feature. + +IETF RFC 8583 [22] specifies a Diameter load control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes. + +It is recommended to make use of IETF draft-ieft-dime-load-03 [22] on the PC4a interface where, when applied, the ProSe Function shall behave as reacting node and the HSS as a reporting node. + +## D.2 HSS behaviour + +The HSS may report its current load by including a Load AVP of type HOST in answer commands as described in IETF RFC 8583 [22]. + +The HSS calculates its current load by implementation specific means. For example, the HSS may take into account the traffic over the PC4a interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc. + +The HSS determines when to send Load AVPs of type HOST by implementation specific means. + +## D.3 ProSe Function behaviour + +When performing next hop Diameter Agent selection for requests that are routed based on realm, the ProSe Function may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [22]. \ No newline at end of file diff --git a/marked/Rel-18/29_series/29512/raw.md b/marked/Rel-18/29_series/29512/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e614617a71aba759aefd5a622a983de41ab677bd --- /dev/null +++ b/marked/Rel-18/29_series/29512/raw.md @@ -0,0 +1,11593 @@ + + +# 3GPP TS 29.512 V18.4.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Session Management Policy Control Service; Stage 3 (Release 18)** --- + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. + +Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices + +--- + +## Keywords + +## **3GPP** + +## Postal address + +3GPP support office address +650 Route des Lucioles – Sophia Antipolis +Valbonne – FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## Internet + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------|----| +| Foreword..... | 11 | +| 1 Scope..... | 12 | +| 2 References..... | 12 | +| 3 Definitions, symbols and abbreviations..... | 14 | +| 3.1 Definitions..... | 14 | +| 3.2 Abbreviations..... | 16 | +| 4 Npcf_SMPolicyControl Service..... | 17 | +| 4.1 Service Description..... | 17 | +| 4.1.1 Overview..... | 17 | +| 4.1.2 Service Architecture..... | 18 | +| 4.1.3 Network Functions..... | 18 | +| 4.1.3.1 Policy Control Function (PCF)..... | 18 | +| 4.1.3.2 NF Service Consumers..... | 19 | +| 4.1.4 Rules..... | 20 | +| 4.1.4.1 General..... | 20 | +| 4.1.4.2 PCC rules..... | 20 | +| 4.1.4.2.1 PCC rules definition..... | 20 | +| 4.1.4.2.2 PCC rules operation..... | 24 | +| 4.1.4.3 Session rule..... | 25 | +| 4.1.4.3.1 Session rules definition..... | 25 | +| 4.1.4.3.2 Session rules operation..... | 25 | +| 4.1.4.4 Policy Decision types..... | 25 | +| 4.1.4.4.1 General..... | 25 | +| 4.1.4.4.2 Traffic control data definition..... | 25 | +| 4.1.4.4.3 QoS data definition..... | 26 | +| 4.1.4.4.4 Charging data definition..... | 27 | +| 4.1.4.4.5 UsageMonitoring data definition..... | 27 | +| 4.1.4.4.6 QoS Monitoring data definition..... | 28 | +| 4.1.5 Policy control request trigger..... | 28 | +| 4.1.6 Requested rule data..... | 29 | +| 4.1.7 Requested usage data..... | 29 | +| 4.1.8 Condition data..... | 29 | +| 4.2 Service Operations..... | 29 | +| 4.2.1 Introduction..... | 29 | +| 4.2.2 Npcf_SMPolicyControl_Create Service Operation..... | 30 | +| 4.2.2.1 General..... | 30 | +| 4.2.2.2 SM Policy Association establishment..... | 31 | +| 4.2.2.3 Provisioning of charging related information for PDU session..... | 34 | +| 4.2.2.3.1 Provisioning of Charging Addresses..... | 34 | +| 4.2.2.3.2 Provisioning of Default Charging Method..... | 35 | +| 4.2.2.4 Provisioning of revalidation time..... | 36 | +| 4.2.2.5 Policy provisioning and enforcement of authorized AMBR per PDU session..... | 36 | + +# Copyright Notification + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------|----| +| 4.2.2.6 | Policy provisioning and enforcement of authorized default QoS..... | 37 | +| 4.2.2.7 | Provisioning of PCC rule for Application Detection and Control..... | 37 | +| 4.2.2.8 | 3GPP PS Data Off Support..... | 37 | +| 4.2.2.9 | IMS Emergency Session Support..... | 38 | +| 4.2.2.10 | Request Usage Monitoring Control..... | 39 | +| 4.2.2.11 | Access Network Charging Identifier report..... | 39 | +| 4.2.2.12 | Request for the successful resource allocation notification..... | 39 | +| 4.2.2.13 | Request of Presence Reporting Area Change Report..... | 39 | +| 4.2.2.14 | Provisioning of IP Index Information..... | 39 | +| 4.2.2.15 | Negotiation of the QoS flow for IMS signalling..... | 39 | +| 4.2.2.16 | PCF resource cleanup..... | 40 | +| 4.2.2.17 | Access traffic steering, switching and splitting support..... | 40 | +| 4.2.2.18 | DNN Selection Mode Support..... | 41 | +| 4.2.2.19 | Detection of the SM Policy Association enabling Time Sensitive Communications, Time Synchronization and Deterministic Networking..... | 41 | +| 4.2.2.20 | Support of Dual Connectivity end to end redundant User Plane paths..... | 42 | +| 4.2.2.21 | User Plane Remote Provisioning of UE SNPN Credentials in Onboarding Network..... | 42 | +| 4.2.2.22 | Network slice related data rate policy control..... | 43 | +| 4.2.2.23 | Group related data rate policy control..... | 43 | +| 4.2.2.24 | Network slice usage control..... | 43 | +| 4.2.3 | Npcf_SMPolicyControl_UpdateNotify Service Operation..... | 43 | +| 4.2.3.1 | General..... | 43 | +| 4.2.3.2 | SM Policy Association Update request..... | 44 | +| 4.2.3.3 | SM Policy Association termination request..... | 46 | +| 4.2.3.4 | Provisioning of revalidation time..... | 47 | +| 4.2.3.5 | Policy provisioning and enforcement of authorized AMBR per PDU session..... | 47 | +| 4.2.3.6 | Policy provisioning and enforcement of authorized default QoS..... | 47 | +| 4.2.3.7 | Provisioning of PCC rule for Application Detection and Control..... | 48 | +| 4.2.3.8 | 3GPP PS Data Off Support..... | 48 | +| 4.2.3.9 | IMS Emergency Session Support..... | 48 | +| 4.2.3.9.1 | Provisioning of PCC rule..... | 48 | +| 4.2.3.9.2 | Removal of PCC Rules for Emergency Services..... | 49 | +| 4.2.3.10 | Request of Access Network Information..... | 49 | +| 4.2.3.11 | Request Usage Monitoring Control..... | 49 | +| 4.2.3.12 | Ipv6 Multi-homing support..... | 49 | +| 4.2.3.13 | Request for the result of PCC rule removal..... | 49 | +| 4.2.3.14 | Access Network Charging Identifier request..... | 50 | +| 4.2.3.15 | Request for the successful resource allocation notification..... | 50 | +| 4.2.3.16 | PCC Rule Error Report..... | 50 | +| 4.2.3.17 | IMS Restoration Support..... | 50 | +| 4.2.3.18 | P-CSCF Restoration Enhancement Support..... | 51 | +| 4.2.3.19 | Request of Presence Reporting Area Change Report..... | 51 | +| 4.2.3.20 | Session Rule Error Report..... | 51 | +| 4.2.3.21 | Access traffic steering, switching and splitting support..... | 51 | +| 4.2.3.22 | Policy provisioning and enforcement of the AF session with required QoS..... | 52 | +| 4.2.3.23 | Forwarding of TSC user plane node management information and port management information received from the TSN AF or TSCTSF..... | 52 | +| 4.2.3.24 | Provisioning of TSCAI input information and TSC QoS related data..... | 53 | +| 4.2.3.25 | Policy provisioning of QoS Monitoring control..... | 55 | +| 4.2.3.25.1 | General..... | 55 | +| 4.2.3.25.2 | QoS Monitoring when dynamic Satellite Backhaul is used..... | 58 | +| 4.2.3.26 | Policy decision error handling..... | 58 | +| 4.2.3.26.1 | Policy decision types and condition data error handling..... | 58 | +| 4.2.3.26.2 | Policy decision types, condition data and other policy decisions error handling..... | 59 | +| 4.2.3.27 | Network slice related data rate policy control..... | 60 | +| 4.2.3.28 | Group related data rate policy control..... | 60 | +| 4.2.3.29 | Policy provisioning of Traffic Parameter to be measured..... | 60 | +| 4.2.3.30 | Network slice usage control..... | 60 | +| 4.2.4 | Npcf_SMPolicyControl_Update Service Operation..... | 60 | +| 4.2.4.1 | General..... | 60 | +| 4.2.4.2 | Requesting the update of the Session Management related policies..... | 62 | + +| | | | +|--------------|----------------------------------------------------------------------------------------------|-----| +| 4.2.4.3 | Request the policy based on revalidation time..... | 65 | +| 4.2.4.4 | Policy provisioning and enforcement of authorized AMBR per PDU session..... | 65 | +| 4.2.4.5 | Policy provisioning and enforcement of authorized default QoS..... | 66 | +| 4.2.4.6 | Application detection information reporting..... | 66 | +| 4.2.4.7 | Indication of QoS Flow Termination Implications..... | 67 | +| 4.2.4.8 | 3GPP PS Data Off Support..... | 68 | +| 4.2.4.9 | Request and Report of Access Network Information..... | 69 | +| 4.2.4.10 | Request Usage Monitoring Control and Reporting Accumulated Usage..... | 69 | +| 4.2.4.10.1 | General..... | 69 | +| 4.2.4.10.2 | PCC Rule Removal..... | 70 | +| 4.2.4.11 | Ipv6 Multi-homing support..... | 71 | +| 4.2.4.12 | Request and report for the result of PCC rule removal..... | 71 | +| 4.2.4.13 | Access Network Charging Identifier request and report..... | 72 | +| 4.2.4.14 | Request and report for the successful resource allocation notification..... | 72 | +| 4.2.4.15 | PCC Rule Error Report..... | 72 | +| 4.2.4.16 | Presence Reporting Area Information Report..... | 73 | +| 4.2.4.17 | UE initiates a resource modification support..... | 73 | +| 4.2.4.18 | Trace Control..... | 75 | +| 4.2.4.19 | Negotiation of the QoS flow for IMS signalling..... | 75 | +| 4.2.4.20 | Notification about Service Data Flow QoS target enforcement..... | 75 | +| 4.2.4.21 | Session Rule Error Report..... | 77 | +| 4.2.4.22 | Request the termination of SM Policy association..... | 77 | +| 4.2.4.23 | Reporting of TSC user plane node management information and port management information..... | 77 | +| 4.2.4.24 | Notification about Service Data Flow QoS Monitoring..... | 78 | +| 4.2.4.25 | Access traffic steering, switching and splitting support..... | 79 | +| 4.2.4.26 | Policy decision error handling..... | 80 | +| 4.2.4.26.1 | Policy decision types and condition data error handling..... | 80 | +| 4.2.4.26.2 | Policy decision types, condition data and other policy decisions error handling..... | 80 | +| 4.2.4.27 | Policy Control for DDN Events..... | 80 | +| 4.2.4.28 | Network slice related data rate policy control..... | 82 | +| 4.2.4.29 | Group related data rate policy control..... | 82 | +| 4.2.4.30 | Notification on network provided BAT Offset policy control trigger..... | 82 | +| 4.2.4.31 | Network slice usage control..... | 83 | +| 4.2.5 | Npcf_SMPolicyControl_Delete Service Operation..... | 83 | +| 4.2.5.1 | General..... | 83 | +| 4.2.5.2 | SM Policy Association termination..... | 83 | +| 4.2.5.3 | Report Accumulated Usage..... | 84 | +| 4.2.5.4 | Report Access Network Information..... | 84 | +| 4.2.5.5 | Void..... | 85 | +| 4.2.5.6 | Network slice related data rate policy control..... | 85 | +| 4.2.5.7 | Group related data rate policy control..... | 85 | +| 4.2.6 | Provisioning and Enforcement of Policy Decisions..... | 85 | +| 4.2.6.1 | General..... | 85 | +| 4.2.6.2 | PCC Rules..... | 87 | +| 4.2.6.2.1 | Overview..... | 87 | +| 4.2.6.2.2 | Gate Function..... | 89 | +| 4.2.6.2.3 | Policy enforcement for authorized QoS per PCC Rule..... | 90 | +| 4.2.6.2.4 | Redirect Function..... | 90 | +| 4.2.6.2.5 | Usage Monitoring Control..... | 91 | +| 4.2.6.2.6 | Traffic Steering Control support..... | 91 | +| 4.2.6.2.6.1 | Steering the traffic in the N6-LAN or steering the 5G-LAN type of services..... | 91 | +| 4.2.6.2.6.2 | Steering the traffic to a local access of the data network..... | 92 | +| 4.2.6.2.7 | Conditioned PCC rule..... | 95 | +| 4.2.6.2.8 | PCC rule for resource sharing..... | 97 | +| 4.2.6.2.9 | Resource reservation for services sharing priority..... | 97 | +| 4.2.6.2.10 | PCC rule bound to the default QoS flow..... | 99 | +| 4.2.6.2.11 | PCC rule for Application Detection and Control..... | 99 | +| 4.2.6.2.12 | Provisioning of PCC Rules for Multimedia Priority Services..... | 100 | +| 4.2.6.2.12.1 | General..... | 100 | +| 4.2.6.2.12.2 | Invocation/Revocation of Priority PDU connectivity services..... | 101 | +| 4.2.6.2.12.3 | Invocation/Revocation of IMS Multimedia Priority Services..... | 101 | + +| | | | +|--------------|---------------------------------------------------------------------------------------------------|-----| +| 4.2.6.2.12.4 | Invocation/Revocation of MPS for DTS..... | 102 | +| 4.2.6.2.13 | Sponsored Data Connectivity..... | 102 | +| 4.2.6.2.14 | Support for PCC rule versioning..... | 103 | +| 4.2.6.2.15 | Background data transfer support..... | 104 | +| 4.2.6.2.16 | Number of supported packet filter for signalled QoS rule limitation support..... | 104 | +| 4.2.6.2.17 | Access traffic steering, switching and splitting support..... | 104 | +| 4.2.6.2.18 | Void..... | 109 | +| 4.2.6.2.19 | Provisioning of PCC Rules for Mission Critical Services..... | 109 | +| 4.2.6.2.19.1 | General..... | 109 | +| 4.2.6.2.19.2 | Invocation/Revocation of Priority PDU connectivity services..... | 109 | +| 4.2.6.2.19.3 | Invocation/Revocation of IMS Mission Critical Services..... | 110 | +| 4.2.6.2.20 | PCC rules authorization with preliminary service information..... | 110 | +| 4.2.6.2.21 | Policy Control for L4S..... | 111 | +| 4.2.6.2.22 | UL/DL policy control based on Round-Trip latency requirements..... | 112 | +| 4.2.6.2.23 | Policy Decision for AF requested QoS for a UE or group of UEs not identified by a UE address..... | 112 | +| 4.2.6.3 | Session Rules..... | 113 | +| 4.2.6.3.1 | Overview..... | 113 | +| 4.2.6.3.2 | Conditioned Session rule..... | 113 | +| 4.2.6.3.2.1 | General..... | 113 | +| 4.2.6.3.2.2 | Time conditioned authorized Session-AMBR..... | 115 | +| 4.2.6.3.2.3 | Time conditioned authorized default QoS..... | 115 | +| 4.2.6.3.2.4 | Access type conditioned authorized Session-AMBR..... | 115 | +| 4.2.6.3.3 | Provisioning of authorized default QoS..... | 116 | +| 4.2.6.3.4 | Access traffic steering, switching and splitting support..... | 116 | +| 4.2.6.3.5 | Usage Monitoring Control..... | 116 | +| 4.2.6.4 | Policy control request triggers..... | 117 | +| 4.2.6.5 | Encoding of the request of information reporting..... | 117 | +| 4.2.6.5.1 | Request of Access Network Charging Identifier..... | 117 | +| 4.2.6.5.2 | RAN NAS Cause Support..... | 117 | +| 4.2.6.5.3 | Provisioning of the Usage Monitoring Control Policy..... | 117 | +| 4.2.6.5.3.1 | General..... | 117 | +| 4.2.6.5.3.2 | Disabling Usage Monitoring..... | 119 | +| 4.2.6.5.3.3 | PCF Requested Usage Report..... | 120 | +| 4.2.6.5.4 | Request for Access Network Information..... | 120 | +| 4.2.6.5.5 | Request for the successful resource allocation notification..... | 120 | +| 4.2.6.5.6 | Provisioning of Presence Reporting Area Information..... | 120 | +| 4.2.6.5.7 | Policy provisioning and enforcement of reflective QoS..... | 121 | +| 4.2.6.6 | Authorized QoS..... | 122 | +| 4.2.6.6.1 | General..... | 122 | +| 4.2.6.6.2 | Policy provisioning and enforcement of authorized QoS per service data flow..... | 123 | +| 4.2.6.6.3 | Policy provisioning and enforcement of authorized explicitly signalled QoS Characteristics..... | 124 | +| 4.2.6.7 | Monitoring the data rate per network slice for a UE..... | 124 | +| 4.2.6.8 | Network slice related data rate policy control..... | 125 | +| 4.2.6.8.1 | General..... | 125 | +| 4.2.6.8.2 | PCF-based network slice data rate policy control by using QoS parameters..... | 126 | +| 4.2.6.8.3 | Network slice data rate policy control with assistance of the NWDAF..... | 127 | +| 4.2.6.9 | Group related data rate policy control..... | 128 | +| 4.2.6.9.1 | General..... | 128 | +| 4.2.6.10 | Policy Provisioning for eXtended Reality and Interactive Media Services..... | 128 | +| 4.2.6.10.1 | Support for delivery of multi-modal services..... | 128 | +| 4.2.7 | Handling of requests which collide with an existing SM Policy Association..... | 129 | +| 4.2.8 | UE IP address support..... | 129 | +| 5 | Npcf_SMPolicyControl Service API..... | 129 | +| 5.1 | Introduction..... | 129 | +| 5.2 | Usage of HTTP..... | 130 | +| 5.2.1 | General..... | 130 | +| 5.2.2 | HTTP standard headers..... | 130 | +| 5.2.2.1 | General..... | 130 | +| 5.2.2.2 | Content type..... | 130 | +| 5.2.3 | HTTP custom headers..... | 130 | + +| | | | +|-------------|--------------------------------------------------------|-----| +| 5.2.3.1 | General..... | 130 | +| 5.2.3.2 | 3gpp-Sbi-Origination-Timestamp..... | 130 | +| 5.3 | Resources..... | 131 | +| 5.3.1 | Resource Structure..... | 131 | +| 5.3.2 | Resource: SM Policies..... | 131 | +| 5.3.2.1 | Description..... | 131 | +| 5.3.2.2 | Resource definition..... | 131 | +| 5.3.2.3 | Resource Standard Methods..... | 132 | +| 5.3.2.3.1 | POST..... | 132 | +| 5.3.2.4 | Resource Custom Operations..... | 132 | +| 5.3.3 | Resource: Individual SM Policy..... | 133 | +| 5.3.3.1 | Description..... | 133 | +| 5.3.3.2 | Resource definition..... | 133 | +| 5.3.3.3 | Resource Standard Methods..... | 133 | +| 5.3.3.3.1 | GET..... | 133 | +| 5.3.3.4 | Resource Custom Operations..... | 134 | +| 5.3.3.4.1 | Overview..... | 134 | +| 5.3.3.4.2 | Operation: delete..... | 134 | +| 5.3.3.4.2.1 | Description..... | 134 | +| 5.3.3.4.2.2 | Operation Definition..... | 134 | +| 5.3.3.4.3 | Operation: update..... | 135 | +| 5.3.3.4.3.1 | Description..... | 135 | +| 5.3.3.4.3.2 | Operation Definition..... | 135 | +| 5.4 | Custom Operations without associated resources..... | 136 | +| 5.5 | Notifications..... | 137 | +| 5.5.1 | General..... | 137 | +| 5.5.2 | Policy Update Notification..... | 137 | +| 5.5.2.1 | Description..... | 137 | +| 5.5.2.2 | Operation Definition..... | 137 | +| 5.5.3 | Request for termination of the policy association..... | 138 | +| 5.5.3.1 | Description..... | 138 | +| 5.5.3.2 | Operation Definition..... | 139 | +| 5.6 | Data Model..... | 139 | +| 5.6.1 | General..... | 139 | +| 5.6.2 | Structured data types..... | 147 | +| 5.6.2.1 | Introduction..... | 147 | +| 5.6.2.2 | Type SmPolicyControl..... | 147 | +| 5.6.2.3 | Type SmPolicyContextData..... | 148 | +| 5.6.2.4 | Type SmPolicyDecision..... | 151 | +| 5.6.2.5 | Type SmPolicyNotification..... | 153 | +| 5.6.2.6 | Type PccRule..... | 154 | +| 5.6.2.7 | Type SessionRule..... | 157 | +| 5.6.2.8 | Type QosData..... | 158 | +| 5.6.2.9 | Type ConditionData..... | 159 | +| 5.6.2.10 | Type TrafficControlData..... | 160 | +| 5.6.2.11 | Type ChargingData..... | 162 | +| 5.6.2.12 | Type UsageMonitoringData..... | 164 | +| 5.6.2.13 | Type RedirectInformation..... | 165 | +| 5.6.2.14 | Type FlowInformation..... | 166 | +| 5.6.2.15 | Type SmPolicyDeleteData..... | 167 | +| 5.6.2.16 | Type QosCharacteristics..... | 168 | +| 5.6.2.17 | Type ChargingInformation..... | 169 | +| 5.6.2.18 | Type AccuUsageReport..... | 170 | +| 5.6.2.19 | Type SmPolicyUpdateContextData..... | 171 | +| 5.6.2.20 | Type UpPathChgEvent..... | 174 | +| 5.6.2.21 | Type TerminationNotification..... | 175 | +| 5.6.2.22 | Type AppDetectionInfo..... | 175 | +| 5.6.2.23 | Type AccNetChId..... | 176 | +| 5.6.2.24 | Type RequestedRuleData..... | 176 | +| 5.6.2.25 | Type RequestedUsageData..... | 177 | +| 5.6.2.26 | Type UeCampingRep..... | 178 | + +| | | | +|----------|---------------------------------------------------|-----| +| 5.6.2.27 | Type RuleReport..... | 179 | +| 5.6.2.28 | Type RanNasRelCause..... | 179 | +| 5.6.2.29 | Type UeInitiatedResourceRequest..... | 180 | +| 5.6.2.30 | Type PacketFilterInfo..... | 181 | +| 5.6.2.31 | Type RequestedQos..... | 181 | +| 5.6.2.32 | Type QosNotificationControlInfo..... | 182 | +| 5.6.2.33 | Type PartialSuccessReport..... | 182 | +| 5.6.2.34 | Type AuthorizedDefaultQos..... | 183 | +| 5.6.2.35 | Type AccNetChargingAddress..... | 183 | +| 5.6.2.36 | Type ErrorReport..... | 184 | +| 5.6.2.37 | Type SessionRuleReport..... | 184 | +| 5.6.2.38 | Type ServingNfIdentity..... | 184 | +| 5.6.2.39 | Type SteeringMode..... | 185 | +| 5.6.2.40 | Type QosMonitoringData..... | 186 | +| 5.6.2.41 | Type TsnBridgeInfo..... | 188 | +| 5.6.2.42 | Type QosMonitoringReport..... | 189 | +| 5.6.2.43 | Type AdditionalAccessInfo..... | 189 | +| 5.6.2.44 | Void..... | 190 | +| 5.6.2.45 | Type PortManagementContainer..... | 190 | +| 5.6.2.46 | Type IpMulticastAddressInfo..... | 190 | +| 5.6.2.47 | Type BridgeManagementContainer..... | 190 | +| 5.6.2.48 | Type DownlinkDataNotificationControl..... | 191 | +| 5.6.2.49 | Type DownlinkDataNotificationControlRm..... | 191 | +| 5.6.2.50 | Type SgsnAddress..... | 191 | +| 5.6.2.51 | Void..... | 191 | +| 5.6.2.52 | Type ThresholdValue..... | 191 | +| 5.6.2.53 | Type NwdafData..... | 192 | +| 5.6.2.54 | Type CallInfo..... | 192 | +| 5.6.2.55 | Type CalleeInfo..... | 192 | +| 5.6.2.56 | Type TrafficParaData..... | 193 | +| 5.6.2.57 | Type L4sSupportInfo..... | 193 | +| 5.6.2.58 | Void..... | 193 | +| 5.6.2.59 | Type SliceUsgCtrlInfo..... | 193 | +| 5.6.3 | Simple data types and enumerations..... | 193 | +| 5.6.3.1 | Introduction..... | 193 | +| 5.6.3.2 | Simple data types..... | 193 | +| 5.6.3.3 | Enumeration: FlowDirection..... | 194 | +| 5.6.3.4 | Enumeration: ReportingLevel..... | 194 | +| 5.6.3.5 | Enumeration: MeteringMethod..... | 195 | +| 5.6.3.6 | Enumeration: PolicyControlRequestTrigger..... | 196 | +| 5.6.3.7 | Enumeration: RequestedRuleDataType..... | 203 | +| 5.6.3.8 | Enumeration: RuleStatus..... | 203 | +| 5.6.3.9 | Enumeration: FailureCode..... | 204 | +| 5.6.3.10 | Enumeration: AfSigProtocol..... | 206 | +| 5.6.3.11 | Enumeration: RuleOperation..... | 206 | +| 5.6.3.12 | Enumeration: RedirectAddressType..... | 206 | +| 5.6.3.13 | Enumeration: QosFlowUsage..... | 207 | +| 5.6.3.14 | Enumeration: FailureCause..... | 207 | +| 5.6.3.15 | Enumeration: FlowDirectionRm..... | 207 | +| 5.6.3.16 | Enumeration: CreditManagementStatus..... | 207 | +| 5.6.3.17 | Enumeration: SessionRuleFailureCode..... | 208 | +| 5.6.3.18 | Enumeration: SteeringFunctionality..... | 209 | +| 5.6.3.19 | Enumeration: SteerModeValue..... | 209 | +| 5.6.3.20 | Enumeration: MulticastAccessControl..... | 209 | +| 5.6.3.21 | Enumeration RequestedQosMonitoringParameter..... | 210 | +| 5.6.3.22 | Enumeration: ReportingFrequency..... | 210 | +| 5.6.3.23 | Enumeration: SmPolicyAssociationReleaseCause..... | 210 | +| 5.6.3.24 | Enumeration: PduSessionRelCause..... | 210 | +| 5.6.3.25 | Enumeration: MaPduIndication..... | 211 | +| 5.6.3.26 | Enumeration: AtsssCapability..... | 212 | +| 5.6.3.27 | Enumeration: NetLocAccessSupport..... | 213 | + +| | | | +|----------------------------------------------------------------------------|-------------------------------------------------------------------------------|------------| +| 5.6.3.28 | Enumeration: PolicyDecisionFailureCode..... | 213 | +| 5.6.3.29 | Enumeration: NotificationControlIndication..... | 213 | +| 5.6.3.31 | Enumeration: SteerModeIndicator..... | 213 | +| 5.6.3.32 | Enumeration TrafficParameterMeas..... | 214 | +| 5.7 | Error handling..... | 214 | +| 5.7.1 | General..... | 214 | +| 5.7.2 | Protocol Errors..... | 214 | +| 5.7.3 | Application Errors..... | 214 | +| 5.8 | Feature negotiation..... | 218 | +| 5.9 | Security..... | 223 | +| Annex A (normative): OpenAPI specification..... | | 225 | +| A.1 | General..... | 225 | +| A.2 | Npcf_SMPolicyControl API..... | 225 | +| Annex B (normative): 5GC and EPC interworking scenario support..... | | 266 | +| B.1 | Scope..... | 266 | +| B.2 | Npcf_SMPolicyControl Service..... | 266 | +| B.2.1 | Service Description..... | 266 | +| B.2.1.1 | Overview..... | 266 | +| B.2.1.2 | Service Architecture..... | 266 | +| B.3 | Service Operation..... | 267 | +| B.3.1 | Introduction..... | 267 | +| B.3.2 | Npcf_SMPolicyControl_Create Service Operation..... | 267 | +| B.3.2.0 | General..... | 267 | +| B.3.2.1 | UE Location related information..... | 268 | +| B.3.2.2 | Access Type related information..... | 269 | +| B.3.2.3 | Access Network Charging Identifier report..... | 269 | +| B.3.3 | Npcf_SMPolicyControl_UpdateNotify Service Operation..... | 270 | +| B.3.3.0 | General..... | 270 | +| B.3.3.1 | Policy Update When UE suspends..... | 270 | +| B.3.3.2 | Request report of EPS Fallback..... | 270 | +| B.3.3.3 | S-GW Restoration Support..... | 271 | +| B.3.3.4 | Request of Access Network Charging Identifier..... | 271 | +| B.3.3.5 | Forwarding of UE policy container for URSP provisioning in EPS..... | 272 | +| B.3.4 | Npcf_SMPolicyControl_Update Service Operation..... | 272 | +| B.3.4.0 | General..... | 272 | +| B.3.4.1 | Number of Supported Packet Filters Report..... | 273 | +| B.3.4.2 | Policy Update When UE suspends..... | 273 | +| B.3.4.2.1 | Policy Update Error Report..... | 273 | +| B.3.4.2.2 | UE State Change Report..... | 273 | +| B.3.4.3 | UE Location related information..... | 273 | +| B.3.4.4 | Presence Reporting Area Information Report..... | 274 | +| B.3.4.5 | Access Type related information..... | 274 | +| B.3.4.6 | Report of EPS Fallback..... | 275 | +| B.3.4.7 | MA PDU Session..... | 275 | +| B.3.4.8 | EPS RAN NAS Cause Support..... | 276 | +| B.3.4.9 | S-GW Restoration Support..... | 276 | +| B.3.4.10 | UE initiates a resource modification support..... | 277 | +| B.3.4.11 | Report of Access Charging Network Identifier..... | 278 | +| B.3.4.11a | Detection of the SM Policy Association enabling URSP provisioning in EPS..... | 278 | +| B.3.4.12 | Reporting of UE Policy container for URSP provisioning in EPS..... | 279 | +| B.3.5 | Npcf_SMPolicyControl_Delete Service Operation..... | 279 | +| B.3.5.1 | General..... | 279 | +| B.3.5.2 | EPS RAN NAS Cause Support..... | 279 | +| B.3.6 | Provisioning and Enforcement of Policy Decisions..... | 279 | +| B.3.6.1 | QoS mapping performed by the SMF+PGW-C..... | 279 | + +| | | | +|---------|----------------------------------------------------------------------------------------|-----| +| B.3.6.2 | Provisioning of Presence Reporting Area Information..... | 280 | +| B.3.6.3 | Request and Report of Access Network information..... | 280 | +| B.3.6.4 | MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC..... | 281 | +| B.3.6.5 | MA PDU sessions with connectivity over 5GC and non-3GPP access to EPC..... | 281 | +| B.3.7 | Detection and handling of late arriving requests for interworking scenario..... | 281 | +| B.3.7.1 | Handling of requests which collide with an existing SM Policy Association..... | 281 | +| B.3.7.2 | Detection and handling of requests which have timed out at the originating entity..... | 281 | + +**Annex C (normative): Wireless and wireline convergence access support.....282** + +| | | | +|-----------|--------------------------------------------------------------------------------------------------------------------|-----| +| C.1 | Scope..... | 282 | +| C.2 | Npcf_SMPolicyControl Service..... | 282 | +| C.2.1 | Service Description..... | 282 | +| C.2.1.1 | Overview..... | 282 | +| C.2.1.2 | Service Architecture..... | 282 | +| C.2.1.3 | Network Functions..... | 282 | +| C.2.1.3.1 | Policy Control Function (PCF)..... | 282 | +| C.2.1.3.2 | NF Service Consumers..... | 282 | +| C.2.1.4 | Rules..... | 282 | +| C.2.1.4.1 | PCC Rules..... | 282 | +| C.2.1.4.2 | Gate Function..... | 283 | +| C.2.1.5 | Policy control request trigger..... | 283 | +| C.2.1.6 | UE IP address support..... | 284 | +| C.3 | Service Operation..... | 284 | +| C.3.1 | Introduction..... | 284 | +| C.3.2 | Npcf_SMPolicyControl_Create Service Operation..... | 284 | +| C.3.2.1 | General..... | 284 | +| C.3.2.2 | IPTV service support..... | 285 | +| C.3.3 | Npcf_SMPolicyControl_UpdateNotify Service Operation..... | 285 | +| C.3.3.1 | General..... | 285 | +| C.3.3.2 | IPTV service support..... | 285 | +| C.3.4 | Npcf_SMPolicyControl_Update Service Operation..... | 285 | +| C.3.4.1 | General..... | 285 | +| C.3.4.2 | IPTV service support..... | 286 | +| C.3.5 | Npcf_SMPolicyControl_Delete Service Operation..... | 286 | +| C.3.5.1 | General..... | 286 | +| C.3.6 | Provisioning and Enforcement of Policy Decisions..... | 287 | +| C.3.6.0 | General..... | 287 | +| C.3.6.1 | IPTV service support..... | 287 | +| C.3.6.2 | Hybrid Access support..... | 287 | +| C.3.6.2.1 | General..... | 287 | +| C.3.6.2.2 | Hybrid Access with single PDU session..... | 288 | +| C.3.6.2.3 | Hybrid Access with MA PDU session connectivity over NG-RAN and wireline..... | 288 | +| C.3.6.2.4 | Hybrid Access with MA PDU session connectivity over EPC/E-UTRAN and wireline using EPC interworking scenarios..... | 288 | + +**Annex D(informative): Change history.....290** + +--- + +## 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 provides the stage 3 specification of the Session Management Policy Control Service of 5G system. The stage 2 definition and related procedures of the Session Management Policy Control Service are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [6]. The 5G System Architecture is defined in 3GPP TS 23.501 [2]. + +Stage 3 call flows are provided in 3GPP TS 29.513 [7]. + +The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. + +The Policy Control Function with session related policies provides the Session Management Policy Control Service to the NF server consumers (e.g. Session Management Function). + +# 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 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [6] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2". +- [7] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3". +- [8] IETF RFC 9113: "HTTP/2". +- [9] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [10] OpenAPI: "OpenAPI Specification Version 3.0.0", . +- [11] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [12] 3GPP TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3". +- [13] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane of EPC Nodes". +- [14] Void. +- [15] 3GPP TS 29.519: "5G System; Usage of the Unified Data Repository service for Policy Control Data, Application Data and Structured Data for Exposure; Stage 3". +- [16] 3GPP TS 23.228: "IP multimedia subsystem; Stage 2". +- [17] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3". + +- [18] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point 5". +- [19] 3GPP TS 32.291: "5G System; Charging service; Stage 3". +- [20] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [21] 3GPP TS 23.380: "IMS Restoration Procedures". +- [22] 3GPP TS 29.502: "5G System; Session Management Services; Stage 3". +- [23] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [24] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management". +- [25] 3GPP TS 29.507: "5G System; Access and Mobility Policy Control Service; Stage 3". +- [26] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [27] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [28] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [29] 3GPP TS 29.510: "Network Function Repository Services; Stage 3". +- [30] 3GPP TS 32.290: "5G system; Services, operations and procedures of charging using Service Based Interface (SBI)". +- [31] IETF RFC 9457: "Problem Details for HTTP APIs". +- [32] 3GPP TS 29.122: "T8 reference point for Northbound APIs". +- [33] 3GPP TS 23.527: "5G System; Restoration Procedures". +- [34] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3". +- [35] 3GPP TS 32.255: "Charging management; 5G data connectivity domain charging; stage 2". +- [36] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3". +- [37] 3GPP TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3". +- [38] 3GPP TR 21.900: "Technical Specification Group working methods". +- [39] 3GPP TS 29.521: "5G System; Binding Support Management Service; Stage 3". +- [40] 3GPP TS 29.524: "Cause codes mapping between 5GC interfaces; Stage 3". +- [41] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification". +- [42] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)". +- [43] 3GPP TS 24.193: "Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3". +- [44] 3GPP TS 24.519: "Time-Sensitive Networking (TSN) Application Function (AF) to Device-Side TSN Translator (DS-TT) and Network-Side TSN Translator (NW-TT) protocol aspects; Stage 3". +- [45] IEEE Std 802.1Q-2018: "IEEE Standard for Local and metropolitan area networks--Bridges and Bridged Networks". +- [46] 3GPP TS 29.551: "5G System; Packet Flow Description Management Service; Stage 3". +- [47] BBF TR-456: "AGF Functional Requirements". +- [48] CableLabs WR-TR-5WWC-ARCH: "5G Wireless Wireline Converged Core Architecture". +- [49] 3GPP TS 24.539: "5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3". + +- [50] 3GPP TS 29.564: "5G System; User Plane Function Services; Stage 3". +- [51] 3GPP TS 29.520: "5G System; Network Data Analytics Services; Stage 3". +- [52] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [53] 3GPP TS 29.565: "5G System; Time Sensitive Communication and Time Synchronization Function Services; Stage 3". +- [54] 3GPP TS 38.413: "NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP)". +- [55] IETF RFC 8655: "Deterministic Networking Architecture". +- [56] IETF RFC 8344: "A YANG Data Model for IP Management". +- [57] 3GPP TS 29.525: "5G System; UE Policy Control Service; Stage 3". +- [58] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [59] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3". +- [60] 3GPP TS 32.299: "Charging management; Diameter charging applications" +- [61] 3GPP TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3". +- [62] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2". +- [63] 3GPP TS 29.594: "5G System; Spending Limit Control Service; Stage 3". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**5G QoS Flow:** The finest granularity for QoS forwarding treatment in the 5G System. All traffic mapped to the same 5G QoS Flow receive the same forwarding treatment (e.g. scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.). Providing different QoS forwarding treatment requires separate 5G QoS Flow. + +**5G QoS Identifier:** A scalar that is used as a reference to a specific QoS forwarding behaviour (e.g. packet loss rate, packet delay budget) to be provided to a 5G QoS Flow. This may be implemented in the access network by the 5QI referencing node specific parameters that control the QoS forwarding treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.). + +**Access Traffic Steering:** The procedure that selects an access network for a new data flow and transfers the traffic of this data flow over the selected access network. Access traffic steering is applicable between one 3GPP access and one non-3GPP access. + +**Access Traffic Switching:** The procedure that moves all traffic of an ongoing data flow from one access network to another access network in a way that maintains the continuity of the data flow. Access traffic switching is applicable between one 3GPP access and one non-3GPP access. + +**Access Traffic Splitting:** The procedure that splits the traffic of a data flow across multiple access networks. When traffic splitting is applied to a data flow, some traffic of the data flow is transferred via one access and some other traffic of the same data flow is transferred via another access. Access traffic splitting is applicable between one 3GPP access and one non-3GPP access. + +**Application detection filter:** A logic used to detect packets generated by an application based on extended inspection of these packets, e.g., header and/or payload information, as well as dynamics of packet flows. The logic is entirely internal to a UPF, and is out of scope of this specification. + +**Application identifier:** An identifier, referring to a specific application detection filter. + +**Application service provider:** A business entity responsible for the application that is being / will be used by a UE, which may be either an AF operator or has an association with the AF operator. + +**Binding:** The association between a service data flow and the QoS Flow transporting that service data flow. + +**Binding mechanism:** The method for creating, modifying and deleting bindings. + +**Charging control:** The process of associating packets, belonging to a service data flow, to a charging key and applying online charging or offline charging, as appropriate. + +**Charging key:** information used by the CHF for rating purposes. + +**Detected application traffic:** An aggregate set of packet flows that are generated by a given application and detected by an application detection filter. + +**Dynamic PCC Rule:** a PCC rule, for which the definition is provided to the SMF by the PCF. + +**Gating control:** The process of blocking or allowing packets, belonging to a service data flow / detected application's traffic, to pass through to the UPF. + +**MA PDU Session:** A PDU Session that provides a PDU connectivity service, which can use one access network at a time, or simultaneously one 3GPP access network and one non-3GPP access network. + +**Monitoring key:** information used by the SMF and PCF for usage monitoring control purposes as a reference to a given set of service data flows or application (s), that all share a common allowed usage on a per UE and DNN and S-NSSAI basis. + +**Operating System (OS):** Collection of UE software that provides common services for applications. + +**Operating System Identifier (OSId):** An identifier identifying the operating system. + +**PCC decision:** A PCF decision for policy and charging control provided to the SMF (consisting of PCC rules and PDU Session related attributes), a PCF decision for access and mobility related control provided to the AMF, a PCF decision for UE access selection and PDU Session selection related policy provided to the UE or a PCF decision for background data transfer policy provided to the AF. + +**PCC rule:** A set of information enabling the detection of a service data flow and providing parameters for policy control and/or charging control and/or other control or support information. The possible information is described in clause 6.3.1. + +**PDU Session:** Association between the UE and a Data Network that provides a PDU connectivity service. + +**Policy control:** The process whereby the PCF indicates to the SMF how to control the QoS Flow. Policy control includes QoS control and/or gating control. + +**Policy Control Request trigger report:** a notification, possibly containing additional information, of an event which occurs that corresponds with a Policy Control Request trigger. + +**Policy Control Request trigger:** defines a condition when the SMF shall interact again with the PCF. + +**Predefined PCC Rule:** a PCC rule that has been provisioned directly into the SMF by the operator. + +**Redirection:** Redirect the detected service traffic to an application server (e.g. redirect to a top-up / service provisioning page). + +**Service data flow:** An aggregate set of packet flows carried through the UPF that matches a service data flow template. + +**Service data flow filter:** A set of packet flow header parameter values/ranges used to identify one or more of the packet flows in the UPF. The possible service data flow filters are defined in clause 6.2.2.2. + +**Service data flow filter identifier:** A scalar that is unique for a specific service data flow (SDF) filter within a PDU session. + +**Service data flow template:** The set of service data flow filters in a PCC Rule or an application identifier in a PCC rule referring to an application detection filter in the SMF or in the UPF, required for defining a service data flow. + +**Service identifier:** An identifier for a service. The service identifier provides the most detailed identification, specified for flow based charging, of a service data flow. A concrete instance of a service may be identified if additional AF information is available (further details to be found in clause 6.3.1). + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501 [2], subclause 3.1 apply: + +#### **Onboarding Standalone Non-Public Network** + +#### **Onboarding Network** + +## **3.2 Abbreviations** + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|----------|-----------------------------------------------------------------------------| +| ADC | Application Detection and Control | +| 5G-RG | 5G Residential Gateway | +| AF | Application Function | +| AMF | Access and Mobility Management Function | +| API | Application Programming Interface | +| ATSSS | Access Traffic Steering, Switching, Splitting | +| ATSSS-LL | ATSSS Low-Layer | +| BAT | Burst Arrival Time | +| BBF | Broadband Forum | +| CHEM | Coverage and Handoff Enhancements using Multimedia error robustness feature | +| CHF | Charging Function | +| DCS | Default Credentials Server | +| DDD | Downlink Data Delivery | +| DDN | Downlink Data Notification | +| DetNet | Deterministic Networking | +| DN-AAA | Data Network Authentication, Authorization and Accounting | +| DNN | Data Network Name | +| DS-TT | Device-side TSN translator | +| DTS | Data Transport Service | +| EAS | Edge Application Server | +| ECN | Explicit Congestion Notification | +| ePDG | evolved Packet Data Gateway | +| FN-RG | Fixed Network Residential Gateway | +| GEO | Geosynchronous Orbit | +| GFBR | Guaranteed Flow Bit Rate | +| GUAMI | Globally Unique AMF Identifier | +| HFC | Hybrid Fiber Coax | +| HTTP | Hypertext Transfer Protocol | +| HR-SBO | Home Routed-Session BreakOut | +| I-SMF | Intermediate SMF | +| L4S | Low Latency Low Loss Scalable Throughput | +| LEO | Low Earth Orbit | +| MA | Multi-Access | +| MEO | Medium Earth Orbit | +| MPQUIC | Multi-Path QUIC | +| MPTCP | Multi-Path TCP Protocol | +| MTU | Maximum Transmission Unit | +| NAS | Non-Access-Stratum | +| NEF | Network Exposure Function | + +| | | +|---------|----------------------------------------------------------------| +| NF | Network Function | +| NID | Network Identifier | +| NRF | Network Repository Function | +| NWDAF | Network Data Analytics Function | +| NW-TT | Network-side TSN translator | +| ON-SNPN | Onboarding Standalone Non-Public Network | +| ONN | Onboarding Network | +| PCC | Policy and Charging Control | +| PCF | Policy Control Function | +| PFD | Packet Flow Description | +| PFDF | Packet Flow Description Function | +| PMIC | Port Management Information Container | +| PSA | PDU Session Anchor | +| PSAP | Public Safety Answering Point | +| QoS | Quality of Service | +| RSN | Redundancy Session Number | +| RTT | Round-Trip Time | +| SDF | Service Data Flow | +| SFC | Service Function Chain | +| SMF | Session Management Function | +| SNPN | Stand-alone Non-Public Network | +| S-NSSAI | Single Network Slice Selection Assistance Information | +| SSC | Service and Session Continuity | +| SUPL | Secure User Plane for Location | +| TNAN | Trusted Non-3GPP Access Network | +| TWAN | Trusted WLAN Access Network | +| TSC | Time Sensitive Communication | +| TSCAI | Time Sensitive Communication Assistance Information | +| TSCTSF | Time Sensitive Communication and Time Synchronization Function | +| TSN | Time Sensitive Networking | +| TSN GM | TSN Grand Master | +| UDM | Unified Data Management | +| UDR | Unified Data Repository | +| UE | User Equipment | +| UL CL | UpLink Classifier | +| UMIC | User plane node Management Information Container | +| UPF | User Plane Function | +| URLLC | Ultra Reliable Low Latency Communication | +| URSP | UE Route Selection Policy | +| W-5GAN | Wireline 5G Access Network | +| W-5GBAN | Wireline BBF Access Network | +| W-5GCAN | Wireline 5G Cable Access Network | +| W-AGF | Wireline Access Gateway Function | + +## 4 Npcf\_SMPolicyControl Service + +### 4.1 Service Description + +#### 4.1.1 Overview + +The Session Management Policy Control Service performs provisioning, update and removal of session related policies and PCC rules by the Policy Control Function (PCF) to the NF service consumer (e.g. SMF). The Session Management Policy Control Service can be used for charging control, policy control, application detection and control and/or access traffic steering, switching and splitting within a MA PDU Session. Session Management Policy Control Service applies to the cases where the SMF interacts with the PCF in the non-roaming scenario, the SMF interacts with the V-PCF in the local breakout roaming scenario and the H-SMF interacts with the H-PCF in the home-routed scenario. + +## 4.1.2 Service Architecture + +The Session Management Policy Control Service is provided by the PCF to the consumer and shown in the SBI representation model in figure 4.1.2-1 and in the reference point representation model in figure 4.1.2-2. The overall Policy and Charging Control related 5G architecture is depicted in 3GPP TS 29.513 [7]. + +The only known NF service consumer is the SMF. + +![Figure 4.1.2-1: Reference Architecture for the Npcf_SMPolicyControl Service; SBI representation. The diagram shows a PCF (Policy Control Function) box containing an oval labeled 'Npcf'. Below the PCF box is a rectangular box labeled 'Npcf_SMPolicyControl'. At the bottom is an SMF (Session Management Function) box. A vertical line connects the 'Npcf' oval to the 'Npcf_SMPolicyControl' box, and another vertical line connects the 'Npcf_SMPolicyControl' box to the SMF box.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +Figure 4.1.2-1: Reference Architecture for the Npcf\_SMPolicyControl Service; SBI representation. The diagram shows a PCF (Policy Control Function) box containing an oval labeled 'Npcf'. Below the PCF box is a rectangular box labeled 'Npcf\_SMPolicyControl'. At the bottom is an SMF (Session Management Function) box. A vertical line connects the 'Npcf' oval to the 'Npcf\_SMPolicyControl' box, and another vertical line connects the 'Npcf\_SMPolicyControl' box to the SMF box. + +**Figure 4.1.2-1: Reference Architecture for the Npcf\_SMPolicyControl Service; SBI representation** + +![Figure 4.1.2-2: Reference Architecture for the Npcf_SMPolicyControl Service; reference point representation. The diagram shows a PCF (Policy Control Function) box on the left and an SMF (Session Management Function) box on the right. A horizontal line connects them, with a small box labeled 'N7' in the center of the line.](51db757d054ce1ce83c436a3578b56ca_img.jpg) + +Figure 4.1.2-2: Reference Architecture for the Npcf\_SMPolicyControl Service; reference point representation. The diagram shows a PCF (Policy Control Function) box on the left and an SMF (Session Management Function) box on the right. A horizontal line connects them, with a small box labeled 'N7' in the center of the line. + +**Figure 4.1.2-2: Reference Architecture for the Npcf\_SMPolicyControl Service; reference point representation** + +NOTE: The PCF represents the V-PCF in the local breakout scenario. The SMF represents the H-SMF and the PCF represents the H-PCF in the home routed scenario. + +## 4.1.3 Network Functions + +### 4.1.3.1 Policy Control Function (PCF) + +The PCF is responsible for policy control decisions and flow based charging control functionalities. The PCF provides policies to the SMF, for example: + +- policies for application and service data flow detection; +- gating; +- QoS; +- flow based charging; +- traffic steering control; +- usage monitoring control; +- access traffic steering; +- switching and steering within a MA PDU Session; +- access network information report; + +- UMIC, PMIC and TSCAI input container; and +- RAN support information to the SMF. + +The policy decisions made by the PCF may be based on one or more of the following: + +- Information obtained from the AF, e.g. the session, media and subscriber related information; +- Information obtained from the UDR; + +NOTE: For local breakout roaming, session management policy data for the UE as defined in 3GPP TS 29.519 [15] is not available in the VPLMN and V-PCF uses locally configured information according to the roaming agreement with the HPLMN operator. All interactions to the UDR in this document are subject to this restriction. + +- Information obtained from the AMF, e.g. UE related and access related information; +- Information obtained from the SMF; +- Information obtained from the NWDAF; +- Information obtained from the NEF; +- Information from the CHF about spending limits control; +- Information from the TSCTSF or TSN AF; and +- PCF pre-configured policy context. + +#### 4.1.3.2 NF Service Consumers + +The SMF is responsible for the enforcement of session management related policy decisions from the PCF, related to service flow detection, QoS, charging, gating, traffic usage reporting, traffic steering and access traffic steering, switching and splitting within a MA PDU Session. + +The SMF shall support: + +- sending the PDU session related attributes to the PCF; +- requesting and receiving the PCC rule(s) from the PCF; +- binding of service data flows to QoS flow as defined in 3GPP TS 29.513 [7]; +- deriving rule(s) from the PCC rule(s) and then providing those rules to the user plane function or remove the rule(s) from the user plane as defined in 3GPP TS 29.244 [13]; +- deriving the QoS rules towards the UE; +- deriving the QoS profile towards the access network; +- deriving the ATSSS rules towards the UE if applicable; +- transferring the DS-TT PMIC transparently towards/from the UE/DS-TT and transferring the NW-TT U/PMIC transparently towards/from the UPF/NW-TT, if applicable; +- adapting received TSCAI input information (TSC assistance container) to 5GS GM and transferring the TSCAI to the AN-RAN; +- handling the policy control request trigger; and +- handling the PDU session related policy information. + +NOTE: SMF functionality related to event exposure is defined in 3GPP TS 29.508 [12]. + +The SMF is also responsible for forwarding to the PCF the UE Policy information received from the UE in UE Policy Containers (information related to URSP delivery in EPS) and in URSP enforcement reports. + +## 4.1.4 Rules + +### 4.1.4.1 General + +A rule is a set of policy information elements associated with a PDU session, or with service data flows (i.e., with a PCC rule). + +Two types of rules are defined: + +- Session rule; and +- PCC rule. + +Both Session rules and PCC rules are composed of embedded information elements as well as information elements that are part of the referenced objects (e.g. condition data, or usage monitoring policy data type) by the rule. + +PCC rule is defined in clause 4.1.4.2. Session rule is defined in clause 4.1.4.3. + +### 4.1.4.2 PCC rules + +#### 4.1.4.2.1 PCC rules definition + +A PCC rule is a set of information elements enabling the detection of a service data flow and providing parameters for policy control and/or charging control. There are two different types of PCC rules as defined in 3GPP TS 23.503 [6]: + +- Dynamic PCC rules: PCC rules that are dynamically provisioned by the PCF to the SMF. These PCC rules may be either predefined or dynamically generated in the PCF. Dynamic PCC rules can be installed, modified and removed at any time. +- Predefined PCC rules: PCC rules that are preconfigured in the SMF. Predefined PCC rules can be activated or deactivated by the PCF at any time. Predefined PCC rules within the PCF may be grouped allowing the PCF to dynamically activate a set of PCC rules. + +Additionally, predefined PCC rules may be grouped within the SMF as predefined PCC rule bases which allow the PCF to dynamically activate these sets of rules. In this case, the PCC rule identifier is used to hold the predefined PCC rule base identifier. + +NOTE 1: When the SMF interacts with the PCF for a PCC rule base, the PCF has no way of knowing which individual PCC rule of the PCC rule base caused the interaction. If such knowledge is required for specific PCC rules, then these PCC rules need to be implemented either as dynamic PCC rules or as predefined PCC rules that are not grouped in a PCC rule base. The SMF decision logic for interacting (or not) with the PCF about an event related to a PCC rule base is up to implementation and depends on the specific issue that triggered this interaction. + +NOTE 2: The operator can define a predefined PCC rule, to be activated by the SMF. Such a predefined rule is not explicitly known in the PCF. + +A PCC rule consists of: + +**Table 4.1.4.2.1-1: PCC rule information elements** + +| Information name | Description | Category | +|----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Rule identifier | Uniquely identifies the PCC rule, within a PDU Session.
It is used between PCF and SMF for referencing PCC rules. | Mandatory | +| Service data flow detection | | | +| Precedence | Determines the order, in which the service data flow templates are applied at service data flow detection, enforcement and charging. | Mandatory | +| Service Data Flow Template | For IP PDU traffic: Either a list of service data flow filters or an application identifier that references the corresponding application detection filter for the detection of the service data flow.
For Ethernet PDU traffic: Combination of traffic patterns of the Ethernet PDU traffic. | Mandatory | +| Mute for notification | Defines whether application's start or stop notification is to be muted. | Optional | +| Charging | | | +| Charging key | The charging system (CHF) uses the charging key to determine the tariff to apply to the service data flow. | Optional | +| Service identifier | The identity of the service or service component the service data flow in a rule relates to. | Optional | +| Sponsor Identifier | An identifier, provided from the AF, which identifies the Sponsor, used for sponsored flows to correlate measurements from different users for accounting purposes. | Optional | +| Application Service Provider Identifier | An identifier, provided from the AF, which identifies the Application Service Provider, used for sponsored flows to correlate measurements from different users for accounting purposes. | Optional | +| Charging method | Indicates the required charging method for the PCC rule.
Values: online or offline or none. | Optional | +| Service Data flow handling while requesting credit | Indicates whether the service data flow is allowed to start while the SMF is waiting for the response to the credit request.
Only applicable for charging method online. | Optional | +| Measurement method | Indicates whether the service data flow data volume, duration, combined volume/duration or event shall be measured.
This is applicable to reporting, if the charging method is online or offline.
Note: Event based charging is only applicable to predefined PCC rules and PCC rules used for application detection filter (i.e. with an application identifier). | Optional | +| Application Function Record Information | An identifier, provided from the AF, correlating the measurement for the Charging key/Service identifier values in this PCC rule with application level reports. | Optional | +| Service identifier level reporting | Indicates that separate usage reports shall be generated for this Service identifier.
Values: mandated or not required. | Optional | +| Policy control | | | +| 5QI | Identifier of the authorized QoS parameters for the service data flow. | Mandatory | +| ARP | The Allocation and Retention Priority for the service data flow consisting of the priority level, the pre-emption capability and the pre-emption vulnerability. | Mandatory | +| Gate status | The gate status indicates whether the service data flow, detected by the service data flow template, may pass (Gate is open) or shall be discarded (Gate is closed). | Optional | +| QoS Notification Control (QNC) | Indicates whether notifications are requested from 3GPP NG-RAN when the GFBR can no longer (or again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow. | Optional | +| Reflective QoS Control | Indicates to apply reflective QoS for the SDF. | Optional | +| MBR (UL/DL) | The uplink/downlink maximum bitrate authorized for the service data flow. | Optional | +| GBR (UL/DL) | The uplink/downlink guaranteed bitrate authorized for the service data flow. | Optional | +| UL sharing indication | Indicates resource sharing in uplink direction with service data flows having the same value in their PCC rule. | Optional | +| DL sharing indication | Indicates resource sharing in downlink direction with service data flows having the same value in their PCC rule. | Optional | +| Redirect | Redirect state of the service data flow (enabled/disabled). | Optional | +| Redirect Destination | Controlled Address to which the service data flow is redirected when redirect is enabled. | Optional | + +| | | | +|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Bind to default QoS Flow | Indicates that the dynamic PCC rule shall always have its binding with the default QoS Flow. | Optional | +| Priority Level | Indicates a priority in scheduling resources among QoS Flows. | Optional | +| Averaging Window | Represents the duration over which the guaranteed and maximum bitrate shall be calculated. | Optional | +| Maximum Data Burst Volume | Denotes the largest amount of data that is required to be transferred within a period of 5G-AN PDB. | Optional | +| Disable UE notifications at changes related to Alternative QoS Profiles | Indicates to disable QoS flow parameters signalling to the UE when the SMF is notified by the NG-RAN of changes in the fulfilled QoS situation. The fulfilled situation is either the QoS profile or an Alternative QoS Profile. | Optional | +| Precedence for TFT packet filter allocation | Determines the order of TFT packet filter allocation for PCC rules | Optional | +| ECN marking for L4S | The ECN marking for L4S indicates that the UL and/or DL of the service data flow, detected by the service data flow template, supports ECN marking for L4S and enables ECN marking for L4S support.
(NOTE 6) | Optional | +| Data burst end marking indication | Indicates enable or disable the data burst end marking. | Optional | +| | Access Network Information Reporting | | +| User Location Required | The UE location(s) (e.g. the serving cell of the UE) is to be reported. When the corresponding QoS flow is deactivated, and if available, information on when the UE was last known to be in that location is also to be reported. | Optional | +| UE Timezone Required | The time zone of the UE is to be reported. | Optional | +| | Usage Monitoring Control | | +| Monitoring key | The PCF uses the monitoring key to group services that share a common allowed usage. | Optional | +| | N6-LAN Traffic Steering Enforcement Control | | +| Traffic steering policy identifier(s) | Reference to a pre-configured traffic steering policy at the SMF. | Optional | +| Metadata | Metadata of traffic for service function chaining handling | Optional | +| | Application Function influence on traffic routing Enforcement Control | | +| Data Network Access Identifier | Identifier of the target Data Network Access. | Optional | +| Per DNAI: Traffic steering policy identifier | Reference to a pre-configured traffic steering policy at the SMF. | Optional | +| Per DNAI: N6 traffic routing information | Describes the information necessary for traffic steering to the DNAI. | Optional | +| Information on AF subscription to UP path changes events | Indicates whether a notification in case of UP path change is requested, as well as the destination(s) for where to provide the notification. | Optional | +| Indication of UE IP address preservation | Indicates UE IP address should be preserved. | Optional | +| Indication of traffic correlation | Indicates that the target PDU Sessions should be correlated via a common DNAI in the user plane. (NOTE 5) | Optional | +| Information on User Plane Latency requirements | Indicates the user plane latency requirements. | Optional | +| EAS IP replacement information | Contains EAS IP replacement information (i.e. IP addresses and port numbers of source and target EAS). | Optional | +| Indication for simultaneous connectivity at edge relocation | Indicates request from the AF for temporary simultaneous connectivity over source and target PSA at edge relocation. It may provide AF guidance to determine when the connectivity over the source PSA can be removed. | Optional | +| Traffic Correlation ID | Identification of a set of UEs accessing the application identified by the Service data flow template | Optional | +| Common EAS IP address | IP address of the common EAS for the application identified by the Service Data Flow Template for the UEs the AF request aims at | Optional | +| FQDN(s) | FQDN(s) for the application indicated in the PCC rule. | Optional | +| NEF information | Notification Endpoint of NEF subscription to be notified with information related to UE members of the set of UEs identified by traffic correlation ID. | Optional | +| Indication of EAS rediscovery. | Indicates the rediscovery of EAS. | Optional | +| | RAN support information | | +| UL Maximum Packet Loss Rate | The maximum rate for lost packets that can be tolerated in the uplink direction for the service data flow. | Optional | + +| | | | +|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| DL Maximum Packet Loss Rate | The maximum rate for lost packets that can be tolerated in the downlink direction for the service data flow. | Optional | +| MA PDU Session Control | | | +| Application descriptors | Identifies the application traffic for which MA PDU Session control is required based on the Steering functionality, the Steering mode, the Steering mode indicator and the Threshold values. | Optional | +| Steering Functionality | Indicates the applicable traffic steering functionality. | Optional | +| Steering mode (UL/DL) | Indicates the UL and/or DL traffic distribution rules between the 3GPP and Non-3GPP accesses together with associated parameters (when applicable) for the traffic matching the service data flow. | Optional | +| Steering mode indicator | Indicates either autonomous load-balance operation or UE-assistance operation, if the steering mode is set to "LOAD_BALANCING". | Optional | +| Threshold value(s) | Indicates, as applicable for the steering mode, the threshold value(s) for maximum RTT or maximum Packet Loss Rate, or both. | Optional | +| Charging for Non-3GPP access | Indicates parameters used for charging packets carried via Non-3GPP access for a MA PDU Session. The same set of parameters as for the Charging information above applies. If a parameter is not included here, the value provided in the Charging information above applies. | Optional | +| Usage Monitoring for Non-3GPP access | Indicates parameters used to monitor usage of the packets carried via Non-3GPP access for a MA PDU Session. The same set of parameters as for the Usage Monitoring information above applies. If a parameter is not included here, the value provided in the Usage Monitoring information above applies. | Optional | +| Transport Mode | The Transport Mode indicates the transport mode for transmitting a UDP flow between UE and UPF. The transport mode should be applied by the MPQUIC functionality for the matching traffic. It shall only be included when the steering functionality is MPQUIC functionality. | Conditional | +| IPTV (NOTE 1) | | | +| IP Multicast traffic control information | Indicates whether the service data flow, corresponding to the service data flow template, is allowed or not allowed. | Optional | +| QoS Monitoring | | | +| QoS parameter(s) to be measured | Indicates the QoS parameters to be monitored, e.g. UL packet delay, DL packet delay or round trip packet delay. | Optional | +| Reporting frequency | Defines the frequency for the reporting, such as event triggered or periodic. | Optional | +| Target of reporting | Defines the target of the QoS Monitoring reports; it corresponds to the AF, as decided by the PCF or included when the indication of direct event notification is received from the AF. | Optional | +| Indication of direct event notification | Indicates that the QoS Monitoring event shall be reported by the UPF directly to the AF or Local NEF indicated by the Target of reporting. | Optional | +| Data Collection Application Identifier | Indicates that the PCC Rule is associated to a QoS monitoring event exposure subscription initiated by the NF service consumer (e.g. NWDAF) that provides an application identifier that matches this value. | Optional | +| Alternative QoS Parameter Sets (NOTE 2) | | | +| Packet Delay Budget | Indicates the packet delay budget in this Alternative QoS Parameter Set. | Optional | +| Packet Error Rate | Indicates the packet error rate in this Alternative QoS Parameter Set. | Optional | +| GBR (UL/DL) | The uplink/downlink guaranteed bitrate authorized for the service data flow in this Alternative QoS Parameter Set. | Optional | +| TSCAI Input container | | | +| Burst Arrival Time | Indicates the burst arrival time in reference to TSN GM for TSN or external GM for non-TSN applications at ingress port. | Optional | +| Periodicity | The time period (in reference to TSN GM for TSN or external GM for non-TSN applications) between start of two bursts. | Optional | +| Flow Direction | Direction of the flow. | Optional | +| Survival Time | It refers to the time period an application can survive without any burst. It is expressed in reference to the TSN GM for TSN and external GM for non-TSN applications. | Optional | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Time Domain | Indicate the (g)PTP domain the (TSN)AF is located in. | Optional | +| Burst Arrival Time window | Indicates the acceptable earliest and latest arrival time of the data burst in reference to the external GM for non-TSN applications at ingress port. | Optional | +| Capability for BAT adaptation | Indicates the capability for AF to adjust the burst sending time according to the network provided Burst Arrival Time offset. | Optional | +| Periodicity Range | Indicates the capability for AF to adjust the periodicity and provides either the acceptable periodicity range or the acceptable periodicity set. It can be formulated as lower bound and upper bound of the periodicity for the acceptable periodicity range, or as a list of value(s) of the periodicity for the acceptable periodicity set. | Optional | +| Traffic Parameter Information | | | +| Periodicity | Indicates the time period between start of two data bursts in UL/DL direction. | Optional | +| Traffic Parameter Measurement | | | +| Traffic Parameter(s) to be measured | Indicates to measure the N6 jitter range associated with DL Periodicity and, optionally, the UL/DL periodicity. | Optional | +| Reporting condition | Defines the condition for the reporting, such as event triggered or periodic, frequency. | Optional | +| Indirect Feature Negotiation | | | +| Supported Features of NF Service Consumer | Network Function Service Consumer features supported per service. | Optional | +| NOTE 1: Only applicable to the 5G-RG connecting to the 5GC via NG-RAN as defined in Annex C.
NOTE 2: Only applicable for GBR service data flow with QoS Notification Control enabled.
NOTE 3: The parameter "Bind to QoS Flow associated with the default QoS rule and apply PCC rule parameters" defined in table 6.3.1 of 3GPP TS 23.503 [6] is implemented as follows: a default QoS with a GBR type or delay critical GBR type 5QI and a PCC rule bound to the default QoS flow are provisioned as defined in clause 4.2.6.2.1.
NOTE 4: The parameter "Indication of exclusion from session level monitoring" defined in table 6.3.1 of 3GPP TS 23.503 [6] is implemented as follows: a PCC rule identifier is included within the "exUsagePccRuleIds" attribute of the UsageMonitoringData instance of PDU session level usage monitoring to indicate that the service data flow shall be excluded from PDU Session usage monitoring as defined in clause 4.2.6.5.3.
NOTE 5: The indication of traffic correlation shall be provided only when all the PDU sessions related to the 5G VN group member UEs should be correlated by a common DNAI in the user plane for the traffic as described in 3GPP TS 23.501 [2], clause 5.6.7.1 and clause 5.29.
NOTE 6: When the "L4S" feature is supported, the indication of ECN marking for L4S shall be provided only when the PCF is configured to provide an explicit indicator to the SMF to enable ECN marking for L4S for the traffic identified by the SDF template. | | | + +**Editor's note:** Further adjustments transport mode definition are FFS based on the transport mode definition in TS 23.503. + +The above information is organized into a set of decision data objects as defined in clause 4.1.4.4. The exact encoding of PCC rules is defined in clause 5.6.2.6. + +#### 4.1.4.2.2 PCC rules operation + +For dynamic PCC rules, the following applies: + +- Installation: to provision the PCC rules. +- Modification: to modify the PCC rules. +- Removal: to remove the PCC rules. + +For predefined PCC rules, the following operations are available: + +- Activation: to activate the PCC rules. +- Deactivation: to deactivate the PCC rules. + +#### 4.1.4.3 Session rule + +##### 4.1.4.3.1 Session rules definition + +A session rule consists of policy information elements associated with PDU session. A session rule is dynamically provisioned by the PCF to the SMF (i.e., there are only dynamic session rules). The encoding of the SessionRule data type is defined in clause 5.6.2.7. + +A session rule shall include: + +- Session Rule Identifier. + +A session rule may include: + +- Authorized Session-AMBR; +- Authorized Default QoS; +- Reference to Usage Monitoring Data; +- Reference to Usage Monitoring Data for Non-3GPP access of MA PDU session; and +- Reference to Condition Data. + +##### 4.1.4.3.2 Session rules operation + +For Session rules, the following applies: + +- Installation: to provision the session rules. +- Modification: to modify the session rules. +- Removal: to remove the session rules. + +#### 4.1.4.4 Policy Decision types + +##### 4.1.4.4.1 General + +A policy decision is a grouping of cohesive information elements describing a specific type of decision, e.g. QoS, Charging data, etc. A policy decision can be linked to one or more PCC rules or one or more Session rules. A PCC rule or session rule can at most refer to one instance of the policy decision for each type. + +The following types of policy decision are defined: + +- Traffic control data; +- QoS data; +- Charging data; +- Usage Monitoring data; and +- QoS Monitoring data. + +##### 4.1.4.4.2 Traffic control data definition + +Traffic control data defines how traffic data flows associated with a rule are treated (e.g. blocked, redirected). The traffic control data encoding table is defined in clause 5.6.2.10. + +Traffic control data shall include: + +- Traffic Control Data ID. + +Traffic control data may include: + +- Flow status; +- ECN marking for L4S support indication; +- Redirect Information; +- Mute Notification; +- Traffic Steering Policy ID UL; +- Traffic Steering Policy ID DL; +- Metadata; +- Routing requirements; +- UP path change event subscription from the AF; +- Information on User Plane Latency requirements; +- EAS IP replacement information; +- Indication of traffic correlation; +- Correlation information for common EAS and DNAI selection potentially together with the NEF information for the notification related to UE members of the set of UEs identified by traffic correlation ID; +- Indication of simultaneous connectivity temporarily maintained for source and target PSA during edge relocation and guidance about when the connectivity over the source PSA can be removed; +- Access Traffic Steering Functionality; +- Access Traffic Steering Mode DL; + - Access Traffic Steering Mode; and + - Optionally, Access Traffic Steering Mode Indicator or Access Traffic Steering Mode Threshold; +- Access Traffic Steering Mode UL; and + - Access Traffic Steering Mode; and + - Optionally, Access Traffic Steering Mode Indicator or Access Traffic Steering Mode Threshold; +- Multicast Access Control; and +- The data burst end marking indication. + +#### 4.1.4.4.3 QoS data definition + +QoS data defines QoS parameters (e.g. bitrates) associated with a rule. The QoS data encoding table is defined in clause 5.6.2.8. + +QoS data shall include: + +- QoS Data ID; + +QoS data may include: + +- 5QI; +- ARP; +- QNC; +- Maximum Packet Loss Rate UL; +- Maximum Packet Loss Rate DL; + +- Maximum Bit Rate UL; +- Maximum Bit Rate DL; +- Guaranteed Bit Rate UL; +- Guaranteed Bit Rate DL; +- 5QI Priority Level; +- Averaging window; +- Maximum Data Burst Volume; +- Bound to default QoS flow indication; +- Resource Sharing Key UL; +- Resource Sharing Key DL; +- Reflective QoS attribute; +- Packet Delay Budget; and +- Packet Error Rate. + +NOTE: Either 5QI and ARP combination or Bound to default QoS flow indication is provided. + +#### 4.1.4.4.4 Charging data definition + +Charging data defines charging related parameters (e.g. rating group) associated with a rule. The charging data encoding table is defined in clause 5.6.2.11. + +Charging data shall include: + +- Charging Data ID; +- Rating Group. + +Charging data may include: + +- Metering Method; +- Charging Method; +- Service Data flow handling while requesting credit; +- Reporting Level; +- Service ID; +- Sponsor ID; +- Application Service Provider ID; and +- AF Charging ID. + +#### 4.1.4.4.5 UsageMonitoring data definition + +UsageMonitoring data defines usage monitoring information associated with a rule. The UsageMonitoring data encoding table is defined in clause 5.6.2.12. + +Usage Monitoring Data shall include: + +- Usage Monitoring ID. + +NOTE: A Usage Monitoring ID corresponds to a valid Monitoring Key. + +Usage Monitoring Data may include: + +- Volume Threshold; +- Volume Threshold UL; +- Volume Threshold DL; +- Time Threshold; +- Monitoring Time; +- Next Volume Threshold; +- Next Volume Threshold UL; +- Next Volume Threshold DL; +- Next Time Threshold; +- Inactivity Time; and +- PCC rule identifier(s) corresponding to the service data flow(s) which need to be excluded from PDU session level usage monitoring. + +#### 4.1.4.4.6 QoS Monitoring data definition + +QoS Monitoring data defines QoS Monitoring related parameters (e.g. request QoS monitoring parameters to be measured) associated with a rule. The QoS Monitoring data encoding table is defined in clause 5.6.2.40. + +QoS Monitoring data shall include: + +- QoS Monitoring Data ID; +- requested QoS monitoring parameters to be measured; +- reporting frequency. + +QoS monitoring data may include: + +- reporting thresholds; +- wait time; +- reporting period; +- target of reporting; +- indication of direct event notification; and +- data collection application identifier. + +### 4.1.5 Policy control request trigger + +A policy control request trigger is a condition pre-configured in the SMF (i.e. always report) or provisioned by the PCF to the SMF, which defines when the SMF shall interact again with PCF for further policy decision related to a PDU session. + +The policy control request trigger is designed as an Enumeration type defined in clause 5.6.3.6. + +The PCF can provide an array of policy control request triggers in a policy decision to subscribe to the associated triggers in the SMF. + +When the SMF interacts with the PCF when the condition(s) associated with policy control request triggers are met, the SMF shall the corresponding trigger(s) together with the related attribute(s) that have changed if applicable. + +#### 4.1.6 Requested rule data + +Requested rule data consists of requested information by the PCF associated with one or more PCC rules. + +The requested rule data is designed as a subresource of the policy decision within an attribute called "lastReqRuleData". The PCF only records the last requested rule data. + +When requesting rule data, the PCF shall include the types of data requested for the rules within the "reqData" array of the "lastReqRuleData" and shall also provide the corresponding policy control request triggers if the triggers are not yet set. + +The encoding of the requested rule data is further specified in clause 5.6.2.24. + +When the SMF receives the requested rule data, the SMF shall report the corresponding information to the PCF for the associated PCC rule(s). + +#### 4.1.7 Requested usage data + +Requested Usage data consists of the requested accumulated usage reports by the PCF for one or more instances of Usage Monitoring data decision. + +The requested usage data is designed as a sub resource of the policy decision within an attribute called "lastReqUsageData". The PCF only records the last requested usage data. + +The encoding of the requested usage data is further specified in clause 5.6.2.25. + +When the SMF receives the requested usage data attribute, the SMF shall report to the PCF the corresponding accumulated usage reports for the corresponding Usage Monitoring data decision(s). Requested usage data shall not be valid anymore for these Usage Monitoring data decision(s) after the reporting. + +#### 4.1.8 Condition data + +Condition data defines the condition(s) where the PCC rules or session rules are applicable and/or not applicable. The condition data encoding is defined in clause 5.6.2.9. + +Condition data shall include: + +- Condition Data ID. + +Condition data may include: + +- Activation Time; +- Deactivation Time; +- Access Type; and +- RAT Type + +NOTE: Access type and RAT type are only applicable to the session rule. + +### 4.2 Service Operations + +#### 4.2.1 Introduction + +The service operations defined for Npcf\_SMPolicyControl are shown in table 4.2.1-1. + +**Table 4.2.1-1: Npcf\_SMPolicyControl Operations** + +| Service Operation Name | Description | Initiated by | +|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| Npcf_SMPolicyControl_Create | Request to create an SM Policy Association with the PCF to receive the policy for a PDU session. | NF consumer (SMF) | +| Npcf_SMPolicyControl_Update | Request to update the SM Policy association with the PCF to receive the updated policy when Policy Control Request Trigger(s) condition is met. | NF consumer (SMF) | +| Npcf_SMPolicyControl_UpdateNotify | Update and/or delete PCC rule(s), PDU session related policy context at the SMF and Policy Control Request Trigger(s) information. | PCF | +| Npcf_SMPolicyControl_Delete | Request to delete the SM Policy Association and the associated resources. | NF consumer (SMF) | + +## 4.2.2 Npcf\_SMPolicyControl\_Create Service Operation + +### 4.2.2.1 General + +The Npcf\_SMPolicyControl\_Create service operation provides means for the SMF to request the creation of a corresponding SM Policy Association with PCF. + +The Session Management procedures of the SMF and related policies are defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [6]. + +The following procedures using the Npcf\_SMPolicyControl\_Create service operation are supported: + +- Request the creation of a corresponding SM Policy Association with the PCF. +- Provisioning of PCC rules. +- Provisioning of policy control request triggers. +- Provisioning of charging related information for a PDU session. +- Provisioning of revalidation time. +- Policy provisioning and enforcement of authorized AMBR per PDU session. +- Policy provisioning and enforcement of authorized default QoS. +- Provisioning of PCC rule for Application Detection and Control. +- 3GPP PS Data Off Support. +- IMS Emergency Session Support. +- Request Usage Monitoring Control. +- Access Network Charging Identifier report. +- Request for the successful resource allocation notification. +- Provisioning of IP Index Information. +- Negotiation of the QoS flow for IMS signalling. +- PCF resource cleanup. +- Access traffic steering, switching and splitting support. +- DNN Selection Mode Support. +- Detection of the SM Policy Association enabling Time Sensitive Communications, Time Synchronization and Deterministic Networking. + +- Support of Dual Connectivity end to end redundant User Plane paths. +- User Plane Remote Provisioning of UE SNPN Credentials in Onboarding Network. +- Network slice related data rate policy control. +- Request of Presence Reporting Area Change Report. +- Group related data rate policy control. +- Support of Network Slice Usage Control. + +When the EMDBV feature defined in clause 5.8 is supported by both the PCF and the SMF, the PCF shall use the extMaxDataBurstVol attribute instead of the maxDataBurstVol attribute to signal maximum data burst volume values higher than 4095 Bytes. + +When the EMDBV feature is supported by the PCF but not supported by the SMF and the PCF needs to signal maximum data burst volume values higher than 4095 Bytes, the PCF shall use the maxDataBurstVol attribute set to 4095 Bytes. + +For values lower than or equal to 4095 Bytes, the PCF shall use the maxDataBurstVol attribute. + +NOTE: Maximum data burst volume values are sent by the PCF in responses to the SMF or in an SM Policy Association Update request i.e. after feature negotiation, so the PCF knows whether the SMF supports the EMDBV feature. + +#### 4.2.2.2 SM Policy Association establishment + +![Sequence diagram showing SM Policy Association establishment between an NF service consumer and a PCF.](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note right of NF service consumer: 1. POST .../sm-policies + NF service consumer->>PCF: 1. POST .../sm-policies + Note left of PCF: 2. 201 Created + PCF-->>NF service consumer: 2. 201 Created +``` + +The diagram illustrates the interaction for SM Policy Association establishment. It features two lifelines: 'NF service consumer' on the left and 'PCF' on the right. Step 1 shows a horizontal arrow from the NF service consumer to the PCF labeled '1. POST .../sm-policies'. Step 2 shows a horizontal arrow from the PCF back to the NF service consumer labeled '2. 201 Created'. + +Sequence diagram showing SM Policy Association establishment between an NF service consumer and a PCF. + +**Figure 4.2.2.2-1: SM Policy Association establishment** + +When the NF service consumer receives the Nsmf\_PDUSession\_CreateSMContext Request as defined in clause 5.2.2.2 of 3GPP TS 29.502 [22], if the NF service consumer was requested not to interact with the PCF, the NF service consumer shall not interact with the PCF. Otherwise, the NF service consumer shall send an HTTP POST request to the PCF to create an "Individual SM Policy" resource as described in step 1 of figure 4.2.2.2-1. + +NOTE 1: The decision to not interact with the PCF applies for the entire lifetime of the PDU session. + +NOTE 2: The indicator to not interact with the PCF is configured in the UDM. It is delivered by the UDM to the NF service consumer within the Charging Characteristics using the Session Management Subscription Data Retrieval service operation as described in 3GPP TS 29.503 [34]. The indicator is operator specific, therefore it can only be used in non-roaming and home routed roaming cases. + +The NF service consumer shall include the "SmPolicyContextData" data structure in the content of the HTTP POST request in order to request the creation of a representation of the "Individual SM Policy" resource as described below. + +The NF service consumer shall include (if available) in the "SmPolicyContextData" data structure: + +- SUPI of the user within the "supi" attribute; +- PDU Session Id within the "pduSessionId" attribute; +- DNN within the "dnn" attribute; + +- DNN selection mode within the "dnnSelMode" attribute, if the "DNNSelectionMode" feature is supported; +- URL identifying the recipient of SM policies update notifications within the "notificationUri" attribute; +- PDU Session Type within the "pduSessionType" attribute; +- PEI within the "pei" attribute; +- Internal Group Id(s) within the "interGrpIds" attribute; +- type of access within the "accessType" attribute; +- type of the radio access technology within the "ratType" attribute; +- the combination of additional access type and RAT type within the "addAccessInfo" attribute, if the ATSSS feature is supported; +- the UE Ipv4 address within the "ipv4Address" attribute and/or the UE Ipv6 prefix within the "ipv6AddressPrefix" attribute; +- the UE time zone information within the "ueTimeZone" attribute; +- the UDM subscribed Session-AMBR or, if the "DN-Authorization" feature is supported, the DN-AAA authorized Session-AMBR within the "subsSessAmbr" attribute; + +NOTE 3: When both, the UDM subscribed Session-AMBR and the DN-AAA authorized Session-AMBR are available in the NF service consumer, the NF service consumer includes the DN-AAA authorized Session-AMBR. + +- if the "VPLMN-QoS-Control" feature is supported, the highest Session-AMBR and the default QoS supported in the VPLMN within the "vplmnQos" attribute, if available; + +NOTE 4: In home routed roaming, the H-SMF may provide the QoS constraints received from the VPLMN (defined in 3GPP TS 23.502 [3] clause 4.3.2.2.2) to the PCF. + +- the DN-AAA authorization profile index within the "authProfIndex" attribute, if the "DN-Authorization" feature is supported; +- subscribed Default QoS Information within the "subsDefQos" attribute; +- the number of supported packet filters for signalled QoS rules within the "numOfPackFilter" attribute; +- the online charging status within the "online" attribute; +- the offline charging status within the "offline" attribute; +- the charging characteristics within the "chargingCharacteristics" attribute; +- the access network charging identifier within the "accNetChId" attribute; +- the address of the network entity performing charging within the "chargEntityAddr" attribute; +- the 3GPP PS data off status within the "3gppPsDataOffStatus" attribute, if the "3GPP-PS-Data-Off" feature is supported; +- indication of UE support of reflective QoS within the "refQosIndication" attribute; +- user location(s) information within the "userLocationInfo" attribute; + +NOTE 5: The SMF encodes both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute when they are both received from the AMF. + +- the S-NSSAI corresponding to the network slice to which the PDU session is allocated within the "sliceInfo" attribute; +- the required QoS flow usage for the default QoS flow within the "qosFlowUsage" attribute; +- the MA PDU session indication within the "maPduInd" attribute, if the "ATSSS" feature is supported; + +- the ATSSS capability within the "atsssCapab" attribute, if the "ATSSS" feature is supported; +- the identifier of the serving network (the PLMN Identifier or the SNPN Identifier) within the "servingNetwork" attribute; + +NOTE 6: The SNPN Identifier consists of the PLMN Identifier and the NID. + +- one or more framed routes within the "ipv4FrameRouteList" attribute for IPv4 and/or one or more framed routes within the "ipv6FrameRouteList" attribute; + +NOTE 7: When both, the UDM subscribed framed routes and the DN-AAA authorized framed routes are available in the NF service consumer, the NF service consumer includes the DN-AAA authorized framed routes. If the UDM or DN-AAA updates the framed routes during the lifetime of the PDU Session, the NF service consumer releases the PDU Session as defined in clause 4.2.5.2. + +- the serving network function identifier within the "servNfId" attribute; +- when the "PvsSupport" feature is supported, the onboarding indication within the "onboardInd" attribute and the Provisioning Server address(es) within the "pvsInfo" attribute; +- when the "SatBackhaulCategoryChg" feature is supported, the satellite backhaul category within the "satBackhaulCategory" attribute; + +NOTE 8: When the "satBackhaulCategory" attribute is not present, non-satellite backhaul applies. + +- when the "AMInfluence" feature is supported, the PCF for the UE callback URI and, if received, SBA binding information and, when the "EnSatBackhaulCatChg" feature is supported, also the dynamic satellite backhaul category, within the "pcfUeInfo" attribute; +- when the "URSPEnforcement" feature is supported, the URSP rule enforcement information provided by the UE within the "urspEnfInfo" attribute. In this case, the NF service consumer shall also include the SSC mode within the "sscMode" attribute, the UE requested DNN (if available and different from the selected DNN) within the "ueReqDnn" attribute, and if the PDU session is redundant, the RSN and the PDU session pair ID within the "redundantPduSessionInfo" attribute; +- trace control and configuration parameters information within the "traceReq" attribute; +- when the "EneNA" feature is supported, the list of NWDAF instance IDs used for the PDU Session within the "nwdafInstanceId" and their associated Analytic ID(s) within "nwdafEvents" consumed by the NF service consumer, included within the "nwdafDatas" attribute; and +- for HR-SBO scenario, if the "HR-SBO" feature is supported, the HR-SBO support indication within the "hrsboInd" attribute in the SM policy association. + +NOTE 9: VPLMN Specific Offloading Policy can be provisioned in HPLMN per each VPLMN based on the service level agreement between HPLMN and VPLMN. + +The NF service consumer may include in the "SmPolicyContextData" data structure the IPv4 address domain identity within the "ipDomain" attribute. + +NOTE 10: The "ipDomain" attribute is helpful when within a network slice, there are several separate IP address domains, with SMF/UPF(s) that allocate IPv4 IP addresses out of the same private address range to UE PDU Sessions. The same IP address can thus be allocated to UE PDU sessions served by SMF/UPFs in different IPv4 address domains. If one PCF controls several SMF/UPFs in different IP address domains, the UE IP address is thus not sufficient for the AF session binding procedure, as described in 3GPP TS 29.514 [17]. The SMF assists the PCF in the session binding supplying an "ipDomain" attribute denoting the IPv4 address domain identity of the allocated UE IPv4 address. + +When the PCF receives the HTTP POST request from the NF service consumer, the PCF shall make a policy authorization based on the information received from the NF service consumer and, if available, information received from the AMF, the CHF, the AF, the UDR and/or the NWDAF and operator policies pre-configured at the PCF. If the policy authorization is successful, the PCF shall create a new resource, which represents a new "Individual SM Policy" instance, addressed by a URI as defined in clause 5.3.3.2 and containing a PCF created resource identifier. The PCF shall respond to the NF service consumer with an HTTP 201 Created response, including: + +- a Location header field containing the URI of the created resource; and +- a response body providing the session management related policies, e.g. provisioning of PCC rules as defined in clause 4.2.6.2, provisioning of policy control request triggers as defined in clause 4.2.6.4. + +The NF service consumer shall use the URI received in the Location header in subsequent requests to the PCF to refer to the created "Individual SM Policy" resource. + +If the PCF received the list of NWDAF instance IDs used for the PDU Session in "nwdafInstanceId" attribute and their associated Analytic IDs in "nwdafEvents" attribute included within the "nwdafDatas" attribute the PCF may select those NWDAF instances as described in 3GPP TS 29.513 [7]. + +If the PCF received a "traceReq" attribute in the HTTP POST request from the SMF, it shall perform trace procedures as defined in 3GPP TS 32.422 [24]. + +If errors occur when processing the HTTP POST request, the PCF shall apply the error handling procedures specified in clause 5.7. + +If the user information received within the "supi" attribute is unknown, the PCF shall reject the request with an HTTP "400 Bad Request" response message including the "cause" attribute of the ProblemDetails data structure set to "USER\_UNKNOWN". + +If the PCF is not able, due to incomplete, erroneous or missing information (e.g. QoS, RAT type, subscriber information), to provision a policy decision as response to the request for PCC rules from the NF service consumer, the PCF may reject the request with an HTTP "400 Bad Request" response message including the "cause" attribute of the ProblemDetails data structure set to "ERROR\_INITIAL\_PARAMETERS". + +If the NF service consumer receives an HTTP response with the above error codes, the NF service consumer shall reject the PDU session establishment procedure that initiated the HTTP POST Request. + +If the PCF, based on local configuration and/or operator policies, denies the creation of the Individual SM Policy resource, the PCF may reject the request with an HTTP "403 Forbidden" response message including the "cause" attribute of the ProblemDetails data structure set to "POLICY\_CONTEXT\_DENIED". At reception of this error code and based on configured failure actions, the NF service consumer may reject or allow, by applying local policies, the PDU session establishment. + +If the "SamePcf" feature as defined in clause 5.8 is supported, when the PCF determines that the same PCF shall be selected for the SM Policy associations to the same UE ID, S-NSSAI and DNN combination in the non-roaming or home-routed scenario and there is no SM Policy association for the UE ID, S-NSSAI and DNN combination, the PCF, after determining whether the BSF supports the "SamePcf" or the "ExtendedSamePcf" feature as described in 3GPP TS 29.521 [39], shall request the BSF to check if there is an existing PCF binding information for the same UE ID, S-NSSAI and DNN combination registered by other PCF(s) as defined in clause 4.2.2.2 of 3GPP TS 29.521 [39]. If the PCF receives the from the BSF "403 Forbidden" status code with the "cause" attribute of the ProblemDetails data structure set to "EXISTING\_BINDING\_INFO\_FOUND" and the FQDN or description of IP endpoints of the Npcf\_SMPolicyControl service of the existing PCF (i.e. that handles SM Policy association(s) to the same UE ID, S-NSSAI and DNN combination) within the "pcfSmFqdn" attribute or the "pcfSmIpEndpoints" attribute of the BindingResp data structure respectively as defined in clause 4.2.2.2 of 3GPP TS 29.521 [39], the PCF shall reply to the SMF with an HTTP "308 Permanent Redirect" error response and the Location header containing a URI as defined in clause 5.3.2.2, with the FQDN or IP endpoint of this PCF's Npcf\_SMPolicyControl service as {apiRoot}. Upon reception of the response, the NF service consumer shall initiate a new HTTP POST request based on the returned URI. + +The forwarding of the Origination Time Stamp parameter shall apply as described hereafter, if the NF service consumer supports the detection and handling of late arriving requests as specified in clause 5.2.3.3 of 3GPP TS 29.502 [22] and the procedure is enabled by the operator. If the NF service consumer receives a request to create an SM Context or a PDU session context, which includes the 3gpp-Sbi-Origination-Timestamp header as defined in clause 5.2.3.2, the NF service consumer shall forward this header to the PCF as HTTP custom header. See also clause 4.2.7 for the handling at the PCF, when the PCF receives the 3gpp-Sbi-Origination-Timestamp header. + +#### 4.2.2.3 Provisioning of charging related information for PDU session + +##### 4.2.2.3.1 Provisioning of Charging Addresses + +The PCF may provide the SMF with the charging information, i.e. the CHF address(es), and if available, the associated CHF instance ID(s) and CHF set ID(s), during the initial interaction with the SMF defining the charging function respectively based on the operator policy. In this case, the PCF may retrieve the CHF addresses, and if available, the associated CHF instance ID(s) and CHF set ID(s) as follows: + +- The PCF receives it from the UDR as part of the Policy Data Subscription information, as defined in clause 5.2.10 of 3GPP TS 29.519 [15]. +- It is locally configured in the PCF based on operator policies. +- The PCF discovers it by interacting with the NRF, as described in clause 6.1 of 3GPP TS 32.290 [30]. + +In order to provision the CHF information to the SMF, the PCF shall include the "chargingInfo" attribute containing the charging information within the SmPolicyDecision data structure. + +Within the ChargingInformation data structure, both the primary CHF address, within the "primaryChfAddress" attribute, and secondary CHF address, within the "secondaryChfAddress" attribute, shall be provided simultaneously when the feature "CHFsetSupport" is not supported. When the feature "CHFsetSupport" is supported, the PCF shall include the "secondaryChfAddress" attribute if available (i.e. if previously retrieved from the UDR, locally configured in the PCF or discovered from the NRF). + +When the CHF supports redundancy based on NF Set concepts as described in 3GPP TS 29.500 [4], the required charging information consists of CHF address, encoded within the "primaryChfAddress" attribute, CHF instance, encoded within the "primaryChfInstanceId" attribute, and primary CHF set id, encoded within the "primaryChfSetId". The CHF set information may be also complemented by secondary CHF address, encoded within the "secondaryChfAddress", for backwards compatibility purposes with the primary/secondary redundancy mechanism. These shall overwrite any predefined CHF addresses and associated CHF instance ID and CHF set ID at the SMF. + +NOTE: When the feature "CHFsetSupport" is supported by the NF service consumer, it indicates the NF service consumer supports CHF redundancy based on NF Set concepts as described in 3GPP TS 29.500 [4], clause 6.5.3. + +Provisioning charging information without PCC rules for charged service data flows shall not be considered as an error, since such PCC rules may be provided later. If the PCF has provided the charging information within the SmPolicyDecision data structure during the initial interaction with the SMF, the PCF shall not modify the charging information in subsequent interactions. + +If no charging information is provisioned by the PCF, the SMF shall use the charging information obtained via one of the following procedures, with the precedence order highest to lowest (see 3GPP TS 32.255 [35], clause 5.1.8): + +1. UDM provided charging characteristics. +2. NRF based discovery. +3. SMF locally configured charging characteristics. + +##### 4.2.2.3.2 Provisioning of Default Charging Method + +The default charging method indicates what charging method shall be used for every PCC rule within which the charging method is omitted, i.e. either both the "online" and the "offline" attributes are not provided or only one of them is provided and set to "false" within the ChargingData data structure to which the PCC rule refers. The SMF may have a pre-configured default charging method. + +Upon the initial interaction with the PCF, the SMF shall provide the pre-configured default charging method, if available, within the "offline" attribute and/or the "online" attribute, and embedded directly within the SmPolicyContextData data structure of the HTTP POST message sent to the PCF. + +The PCF may provide in the response to the received HTTP POST message the default charging method which applies to the PDU session. In order to do so, if offline charging applies, the PCF shall include the "offline" attribute set to + +"true" within the SmPolicyDecision data structure, or if online charging applies, the PCF shall include the "online" attribute set to "true" within the SmPolicyDecision data structure. The default charging method provided by the PCF shall overwrite any predefined default charging method available at the SMF. If the PCF has provided the default charging method during the initial interaction with the SMF, it shall not modify the default charging method in subsequent interactions. + +When the "OfflineChOnly" feature is supported, the PCF may include the "PDU Session with offline charging only" indication as specified in clause 4.2.2.3.3. + +NOTE: It is possible that there is no default charging method applied to a PDU session. + +#### 4.2.2.3.3 Provisioning of the "PDU Session with offline charging only" indication + +If the "OfflineChOnly" feature, specified in clause 5.8, is supported, the PCF may provide in the response to the received HTTP POST message from the SMF the "PDU Session with offline charging only" indication, within the "offlineChOnly" attribute, to signal that the online charging method shall never be configured for any of the PCC Rules activated during the lifetime of the PDU Session, nor provided as the Default Charging Method, as specified in clause 6.4 of 3GPP TS 23.503. + +If the "OfflineChOnly" feature, specified in clause 5.8, is supported and the PCF includes the "PDU Session with offline charging only" indication set to "true" in the "offlineChOnly" attribute within the SmPolicyDecision data structure, then the default charging method for the PDU session is offline charging, and the "online" attribute and the "offline" attribute shall not be provisioned by the PCF within the SmPolicyDecision data structure. + +NOTE: If the PCF includes the "PDU Session with offline charging only" indication set to "true" in the "offlineChOnly" attribute within the SmPolicyDecision data structure, and the "online" attribute and the "offline" attribute are also provisioned by the PCF within the SmPolicyDecision data structure, then the SMF could ignore the values of the "online" attribute and the "offline" attribute. + +#### 4.2.2.4 Provisioning of revalidation time + +The PCF may provide within the SmPolicyDecision data structure the revalidation time within the "revalidationTime" attribute and the "RE\_TIMEOUT" policy control request trigger within the "policyCtrlReqTriggers" attribute to instruct the SMF to trigger an interaction with the PCF to request PCC rule(s). + +The SMF shall start the timer based on the revalidation time and shall trigger a PCC rule request towards the PCF before the indicated revalidation time. + +#### 4.2.2.5 Policy provisioning and enforcement of authorized AMBR per PDU session + +The SMF shall, if available include either the UDM subscribed Session-AMBR or, if the "DN-Authorization" feature is supported, the DN-AAA authorized Session-AMBR per PDU session within the "subsSessAmbr" attribute in the SmPolicyContextData data structure, as defined in clause 4.2.2.2. When both the UDM subscribed Session-AMBR and the DN-AAA authorized Session-AMBR are available in the SMF, the DN-AAA authorized Session-AMBR shall take precedence over the UDM subscribed Session-AMBR. + +NOTE 1: The SMF always provides either the UDM subscribed Session-AMBR or the DN-AAA authorized Session-AMBR per PDU session during an SM policy association establishment procedure except when the SM policy association corresponds to an emergency PDU session. + +In home routed roaming, and if the "VPLMN-QoS-Control" feature is supported, the SMF shall provide the Session-AMBR constraints received from the VPLMN, if available, within the "vplmnQos" attribute. + +When the SMF provides the subscribed Session-AMBR to the PCF, the PCF shall authorize the Session-AMBR based on the operator's policy and, in the home routed scenario, shall ensure that the authorized Session-AMBR value does not exceed the Session-AMBR value provided by the VPLMN, if available. For emergency PDU sessions, the PCF shall behave as specified in clause 4.2.2.9. + +NOTE 2: If the SMF does not provide the Session-AMBR constraints in the VPLMN to the PCF, the PCF considers that no Session-AMBR constraints apply unless operator policies define any. + +When network slice data rate policy control applies, the PCF shall authorize the Session-AMBR as described in clause 4.2.6.8. + +The PCF shall provision the authorized Session-AMBR to the SMF in the response to the received HTTP POST message, as defined in clauses 4.2.6.3.1 and 4.2.6.3.2. + +Upon reception of the authorized Session-AMBR from the PCF, the SMF shall apply the corresponding procedures towards the access network, the UE and the UPF for the enforcement of the Session-AMBR for the concerned PDU session. + +#### 4.2.2.6 Policy provisioning and enforcement of authorized default QoS + +During PDU session establishment, as defined in clause 4.2.2.2, the SMF shall, if available, include the subscribed default QoS within the "subsDefQos" attribute. + +NOTE 1: The SMF always provides the subscribed default QoS during an SM policy association establishment procedure except when the SM policy association corresponds to an emergency PDU session. + +In home routed roaming, and if the "VPLMN-QoS-Control" feature is supported, the SMF shall provide the default QoS constraints received from the VPLMN, if available, within the "vplmnQos" attribute. + +When the SMF provides the subscribed default QoS to the PCF, the PCF shall authorize the default QoS based on the operator's policy and, in the home routed scenario, shall ensure that the authorized default QoS contains 5QI and ARP values, and MBR/GBR values, if applicable, and if the feature "VPLMN-5QIPrioLevel" is supported, a 5QI Priority Level (when the required 5QI Priority Level is different from the standardized Default Priority Level value in the QoS characteristics Table 5.7.4-1 in 3GPP TS 23.501 [2]), supported by the VPLMN, if available. For emergency PDU sessions, the PCF shall behave as specified in clause 4.2.2.9. + +NOTE 2: If the SMF does not provide the default QoS constraints in the VPLMN to the PCF, the PCF considers that no default QoS constraints apply unless operator policies define any. + +The PCF shall provision the authorized default QoS to the SMF in the response to the received HTTP POST message, as defined in clauses 4.2.6.3.1 and 4.2.6.3.2. + +Upon reception of the authorized default QoS, the SMF enforces it, which may lead to the change of the subscribed default QoS. The SMF shall apply the corresponding procedures towards the access network, the UE and the UPF for this enforcement of the authorized default QoS for the concerned PDU session. + +NOTE 3: If dynamic PCC is not deployed, the SMF can have a DNN based configuration to enable the establishment of a GBR resource type default QoS flow. This configuration contains a standardized GBR 5QI as well as GFBR and MFBR for UL and DL. + +NOTE 4: GBR resource type is not applicable to the default QoS flow of a PDU session that is interworking with EPS. + +#### 4.2.2.7 Provisioning of PCC rule for Application Detection and Control + +If the ADC feature is supported, and the user subscription indicates that application detection and control is required, the PCF may provision PCC rule(s) for application detection and control as defined in clause 4.2.6.2.11 in the response message to the received HTTP POST request from the SMF. + +If the SMF receives a PCC rule for application detection and control, the SMF shall instruct the UPF to detect the associated application traffic as defined in 3GPP TS 29.244 [13]. + +#### 4.2.2.8 3GPP PS Data Off Support + +When the 3GPP-PS-Data-Off feature, as defined in clause 5.8, is supported, and if the SMF is informed that the 3GPP PS Data Off status of the UE is set to active during the establishment of a PDU session over 3GPP access and/or non-3GPP access, it shall include the "3gppPsDataOffStatus" attribute set to true within the SmPolicyContextData data structure in the HTTP POST message that it sends to the PCF, as defined in clause 4.2.2.2. + +If the PCF receives that HTTP POST message with a SmPolicyContextData data structure containing a "3gppPsDataOffStatus" attribute set to true as above and the "accessType" attribute indicating "3GPP\_ACCESS", the PCF shall configure the SMF to block any downlink and optionally uplink IP flows that are not related to a service contained in the list of 3GPP PS Data Off Exempt Services, e.g. by not installing any related dynamic PCC rule(s) or by not activating the related predefined PCC rule(s) such as PCC rule(s) with wild-carded service data flow filters. The + +PCF may also, subject to its normal policies, provide the PCC rule(s) for the service(s) included in the list of 3GPP PS Data Off Exempt Services, as defined in clause 4.2.6.2.1. + +The PCF shall subscribe to the "AC\_TY\_CH" policy control request trigger with the SMF, as defined in clause 4.2.6.4, in order to support this feature, if the PCF determines that the UE is allowed to access the network via non-3GPP access. + +NOTE 1: The PCF can be configured with a list of 3GPP PS Data Off Exempt Services per DNN and S-NSSAI. The list of 3GPP PS Data Off Exempt Services for an DNN and S-NSSAI can also be empty, or can allow for any service within that DNN and S-NSSAI, according to operator policy. + +NOTE 2: For the PDU session used for IMS services, the 3GPP Data Off Exempt Services are enforced in the IMS domain as specified in 3GPP TS 23.228 [16]. Policies configured in the PCF need to ensure that IMS services are allowed when the 3GPP Data Off status of the UE is set to active, e.g. by treating any service within a well-known IMS DNN as part of the 3GPP PS Data Off Exempt Services. + +NOTE 3: The packets transferred over non-3GPP access are unaffected by the 3GPP PS Data Off functionality. + +If the "ATSSS" feature, as defined in clause 5.8 is supported, and the PCF receives in the SmPolicyContextData data structure the "maPduInd" attribute, the "3gppPsDataOffStatus" attribute set to true and the "accessType" attribute or the "addAccInfo" attribute set to "3GPP\_ACCESS", the PCF shall configure the SMF in such a way that: + +- packets for services belonging to the 3GPP PS Data Off Exempt services are forwarded over 3GPP access and non-3GPP access as indicated by the policy for ATSSS Control, as specified in clause 4.2.6.2.17; and +- for downlink and optionally uplink flows not related to a service contained in the list of 3GPP PS Data Off Exempt services, the PCF may configure the SMF to handle the associated traffic only via non-3GPP access, if available, by providing the corresponding ATSSS policy within the related PCC rule, as specified in clause 4.2.6.2.17. + +#### 4.2.2.9 IMS Emergency Session Support + +A SMF that requests PCC Rules at PDU Session Establishment for an IMS emergency session in a PLMN or an SNPN shall send an HTTP POST message to the PCF, as defined in clause 4.2.2.2, including the "dnn" attribute containing the Emergency DNN. The SMF may include the SUPI, within the "supi" attribute, and if the SUPI is not available or unauthenticated, the SMF shall include the PEI, within the "pei" attribute, the "invalidSupi" attribute set to "true" and an implementation specific value within the "supi" attribute. The SMF may include the rest of the attributes described in clause 4.2.2.2. The SMF may also include the GPSI, if available, within the "gpsi" attribute. + +NOTE 1: The SMF will not provide subscribed information (e.g. subscribed default QoS or subscribed Session AMBR) to the PCF when the SUPI is not available, unauthenticated or based on local configuration. + +NOTE 2: IMS Emergency services are not supported for SNPN when the UE accesses the SNPN over NWu via a PLMN. + +The PCF shall detect that a PDU session is restricted to IMS Emergency services when the "dnn" attribute included in the HTTP POST message received from the SMF includes a data network identifier that matches one of the Emergency DNs from the configurable list. The PCF does not perform in this case subscription check procedures with UDR; it uses instead the locally configured operator policies to make authorization and policy decisions. The PCF: + +- shall provision PCC Rules restricting the access to Emergency Services (e.g. P-CSCF(s), DHCP(s), DNS(s) and SUPL(s) addresses), as required by local operator policies, in a response message to the SMF according to the procedures described in clause 4.2.6; +- may provision the authorized QoS that applies to the default QoS flow in the response message to the SMF within the "authDefQos" attribute of a session rule according to the procedures described in clause 4.2.3.6, except for obtaining the authorized QoS upon interaction with the UDR. The value of the "priorityLevel" attribute included within the "arp" attribute shall be assigned as required by local operator policies (e.g. if an IMS Emergency session is prioritized, the "priorityLevel" attribute may contain a value that is reserved for an operator domain use of IMS Emergency sessions). If the "accessType" attribute is set to "3GPP\_ACCESS", the values of the "preemptCap" and the "preemptVuln" attributes included within the "arp" attribute shall be assigned as required by local operator policies, + +- may provision the authorized Session-AMBR in the response message to the SMF, according to the procedures described in clause 4.2.3.5. + +When the SMF detects that the provisioning of PCC Rules failed, the PCC rule error handling procedures shall be performed. + +#### 4.2.2.10 Request Usage Monitoring Control + +If the UMC as defined in clause 5.8 is supported, the PCF may provision the usage monitoring control policy to the SMF as defined in clause 4.2.6.5.3. + +#### 4.2.2.11 Access Network Charging Identifier report + +During the PDU session establishment procedure, if the Access Network Charging Identifier is within the Uint32 value range, the SMF may provide the access network charging identifier information within the "accNetChId" attribute of the SmPolicyContextData data structure. Within the associated AccNetChId data structure, the SMF shall include the "accNetChIdValue" attribute containing the Access Network Charging Identifier for the PDU session (i.e., for the default QoS flow) and the "sessionChScope" attribute set to true. The SMF may provide the address of the network entity performing the charging functionality within the "chargEntityAddr" attribute. + +NOTE: As specified in 3GPP TS 32.255 [35] clause 5.1.4, the SMF assigns a charging identifier per PDU session and is used through the PDU session's lifetime. The report of Access Network Charging Identifier(s) in 5GS and EPS interworking scenarios is described in clause B.3.2.3. + +If the "AccNetChargId\_String" feature is supported by the SMF, and the Access Network Charging Identifier value is longer than Uint32: + +- if the SMF doesn't know if the PCF supports the "AccNetChargId\_String" feature, the SMF shall not provide the access network charging identifier information; +- if the SMF knows the PCF supports the feature "AccNetChargId\_String", the SMF shall encode the access network charging identifier within "accNetChargIdString" attribute. + +#### 4.2.2.12 Request for the successful resource allocation notification + +The PCF may request the SMF to confirm that the resources associated to a PCC rule are successfully allocated as defined in clause 4.2.6.5.5. + +#### 4.2.2.13 Request of Presence Reporting Area Change Report + +If the PRA or ePRA feature, as defined in clause 5.8, is supported, the PCF may provision the Presence Reporting Area Information to the SMF as defined in clause 4.2.6.5.6. + +#### 4.2.2.14 Provisioning of IP Index Information + +If the PDU session type received within the "pduSessionType" attribute is "IPv4" or "IPv6" or "IPv4V6", and no corresponding IP address/prefix is received, the PCF may include within the SmPolicyDecision data structure the IP index information within the "ipv4Index" attribute, for IPv4 address allocation, and/or the "ipv6Index" attribute, for IPv6 address allocation, based on the user's subscription information retrieved from the UDR and operator's policy. + +The SMF may use this IP index information to assist in selecting how the IP address is to be allocated when multiple allocation methods or multiple instances of the same method are supported. + +#### 4.2.2.15 Negotiation of the QoS flow for IMS signalling + +If the SMF includes the "qosFlowUsage" attribute required for the default QoS flow within the SmPolicyContextData data structure during the PDU session establishment procedure, the PCF shall provide the "qosFlowUsage" attribute back in the response with the authorized usage. + +If during PDU session establishment procedure, the SMF includes the "IMS\_SIG" value within the "qosFlowUsage" attribute and the PCF accepts that default QoS flow is dedicated to IMS signalling, the PCF shall within the + +SmPolicyDecision data structure include the "IMS\_SIG" value within the "qosFlowUsage" attribute. In this case, the PCF shall restrict the QoS flow to only be used for IMS signalling as specified in 3GPP TS 23.228 [16] by applying the applicable 5QI for IMS signalling. + +If the SMF include the "IMS\_SIG" value within the "qosFlowUsage" attribute of the SmPolicyContextData data structure, but the PCF does not include the "IMS\_SIG" within the "qosFlowUsage" attribute of SmPolicyDecision data structure, the PCC Rules provided by the PCF shall have a 5QI value different from the 5QI value for the IMS signalling. + +#### 4.2.2.16 PCF resource cleanup + +In the Npcf\_SMPolicyControl\_Create service operation, the SMF as NF service consumer may provide SMF Id in "smfId" attribute and recovery timestamp in "recoveryTime" attribute. The PCF may use the "smfId" attribute to supervise the status of the SMF as described in clause 5.2 of 3GPP TS 29.510 [29] and perform necessary cleanup upon status change of the SMF later, and/or both the "smfId" attribute and the "recoveryTime" attribute in cleanup procedure as described in clause 6.4 of 3GPP TS 23.527 [33]. + +#### 4.2.2.17 Access traffic steering, switching and splitting support + +If the SMF supports the "ATSSS" feature defined in clause 5.8, the SMF shall within the SmPolicyContextData data structure include the ATSSS capability within the "atsssCapab" attribute and the MA PDU session Indication within the "maPduInd" attribute as defined in clause 4.2.2.2. + +The SMF determines the ATSSS capability supported for the MA PDU Session based on the ATSSS capabilities provided by the UE and per DNN configuration on SMF, as follows: + +- a. If the SMF receives the UE's ATSSS capabilities "MPTCP functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode" and; + - i. if the DNN configuration allows both MPTCP and ATSSS-LL with any steering mode, including RTT measurement without using PMF protocol, the SMF shall set the "atsssCapab" attribute to the value "MPTCP\_ATSSS\_LL\_WITH\_ASMODE\_UL"; or; + - ii. if the DNN configuration allows both MPTCP and ATSSS-LL with any steering mode, including RTT measurement without using PMF protocol, but the UPF does not support the RTT measurement without using PMF protocol, the SMF shall set the "atsssCapab" attribute to the value "MPTCP\_ATSSS\_LL\_WITH\_EXSDMODE\_DL\_ASMODE\_UL". + - iii. if the DNN configuration allows MPTCP with any steering mode and ATSSS-LL with only Active-Standby steering mode, the SMF shall set the "atsssCapab" attribute to the value "MPTCP\_ATSSS\_LL\_WITH\_ASMODE\_DLUL". +- b. If the SMF receives the UE's ATSSS capabilities "ATSSS-LL functionality with any steering mode" and the DNN configuration allows ATSSS-LL with any steering mode, the SMF shall set the "atsssCapab" attribute to the value "ATSSS\_LL". +- c. If the SMF receives the UE's ATSSS capabilities "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode", and the DNN configuration allows both MPTCP and ATSSS-LL with any steering mode, the SMF shall set the "atsssCapab" attribute to the value "MPTCP\_ATSSS\_LL". + +If the SMF supports the "EnATSSS\_v2" feature defined in clause 5.8 + +- a. If the SMF receives the UE's ATSSS capabilities "MPQUIC functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode" and; + - i. if the DNN configuration allows both MPQUIC and ATSSS-LL with any steering mode, including RTT measurement without using PMF protocol, the SMF shall set the "atsssCapab" attribute to the value "MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_UL"; + - ii. if the DNN configuration allows both MPQUIC and ATSSS-LL with any steering mode, including RTT measurement without using PMF protocol, but the UPF does not support the RTT measurement without using PMF protocol, the SMF shall set the "atsssCapab" attribute to the value "MPQUIC\_ATSSS\_LL\_WITH\_EXSDMODE\_DL\_ASMODE\_UL"; or + +- iii. if the DNN configuration allows MPQUIC with any steering mode and ATSSS-LL with only Active-Standby steering mode, the SMF shall set the "atsssCapab" attribute to the value "MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_DLUL". +- b. If the SMF receives the UE's ATSSS capabilities "MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode", and the DNN configuration allows both MPQUIC and ATSSS-LL with any steering mode, the SMF shall set the "atsssCapab" attribute to the value "MPQUIC\_ATSSS\_LL". +- c. If the SMF receives the UE's ATSSS capabilities " MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode" and; + - i. if the DNN configuration allows MPTCP, MPQUIC and ATSSS-LL with any steering mode, including RTT measurement without using PMF protocol, the SMF shall set the "atsssCapab" attribute to the value "MPTCP\_MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_UL"; + - ii. if the DNN configuration allows MPTCP, MPQUIC and ATSSS-LL with any steering mode, including RTT measurement without using PMF protocol, but the UPF does not support the RTT measurement without using PMF protocol, the SMF shall set the "atsssCapab" attribute to the value "MPTCP\_MPQUIC\_ATSSS\_LL\_WITH\_EXSDMODE\_DL\_ASMODE\_UL"; or + - iii. if the DNN configuration allows MPTCP and MPQUIC with any steering mode and ATSSS-LL with only Active-Standby steering mode, the SMF shall set the "atsssCapab" attribute to the value "MPTCP\_MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_DLUL". +- d. If the SMF receives the UE's ATSSS capabilities "MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode", and the DNN configuration allows MPTCP, MPQUIC and ATSSS-LL with any steering mode, the SMF shall set the "atsssCapab" attribute to the value "MPTCP\_MPQUIC\_ATSSS\_LL". + +If the SMF receives the MA PDU Request Indication from the UE and the SMF determines that the MA PDU session is allowed based on the Session Management subscription data retrieved from the UDM and the operator policy, the SMF shall include the "MA\_PDU\_REQUEST" within the "maPduInd" attribute; otherwise if the SMF receives the MA PDU Network-Upgrade Allowed indication from the UE and the SMF determines that the MA PDU session is allowed based on the Session Management subscription data retrieved from the UDM and the operator policy, the SMF shall include the "MA\_PDU\_NETWORK\_UPGRADE\_ALLOWED" within the "maPduInd" attribute. + +If the PCF supports the "ATSSS" feature, the PCF may provide PCC rules and/or session rules of ATSSS policy for the MA PDU session as defined in clause 4.2.6.2.17 and clause 4.2.6.3.4; otherwise the PCF shall not provide any PCC rules and/or session rules of ATSSS policy. + +#### 4.2.2.18 DNN Selection Mode Support + +If the SMF supports the "DNNSelectionMode" feature defined in clause 5.8, when the SMF receives from the AMF the DNN selection mode, the SMF shall send an HTTP POST message as defined in clause 4.2.2.2 and shall include the received information in the "dnnSelMode" attribute. + +The "dnnSelMode" attribute indicates whether the DNN supplied in the "dnn" attribute is an explicitly subscribed DNN and thus verified by the network against UDM subscription (regardless of whether it was originally provided by the UE or replaced by the network), or if it is a non-subscribed DNN (and provided by the UE, or replaced by the network). + +If the PCF supports the "DNNSelectionMode" feature, when the "dnnSelMode" attribute indicates: + +- the DNN is not explicitly subscribed, the PCF may provision PCC rules and Session rules according to the PCF local configuration for the UE provided and/or network provided non-subscribed DNN; +- the DNN is explicitly subscribed and verified by the network against UDM subscription, the PCF proceeds according to existing specified procedures. + +#### 4.2.2.19 Detection of the SM Policy Association enabling Time Sensitive Communications, Time Synchronization and Deterministic Networking + +When the feature "TimeSensitiveNetworking" is supported, the PCF detects if the Npcf\_SMPolicyControl\_Create request relates to SM Policy Association enabling Time Sensitive Communications Time Synchronization and/or Deterministic Networking based on the received DNN and S-NSSAI. The PCF then may provide within the SmPolicyDecision data structure the "TSN\_BRIDGE\_INFO" policy control request trigger within the "policyCtrlReqTriggers" attribute to instruct the SMF to trigger a PCF interaction when the trigger is met; i.e., new TSC user plane node information (e.g. TSN Bridge or DetNet router information) is available. + +NOTE: Time sensitive communication, time synchronization and deterministic networking are not supported in home-routed roaming scenarios, and service continuity is not supported when the UE moves from 5GS to EPS. + +#### 4.2.2.20 Support of Dual Connectivity end to end redundant User Plane paths + +Upon the initial interaction with the PCF, if the "Dual-Connectivity-redundant-UP-paths" feature is supported, the PCF shall determine, based on operator's policy (e.g. when some of the allowed services require redundancy), whether the PDU session is a redundant one. + +When the PCF determines that the PDU session is a redundant PDU session, the PCF shall provision the "redSessIndication" attribute set to true within the SmPolicyDecisionData returned in the response to the HTTP POST request. Upon receiving the indication from the PCF that the PDU session is a redundant PDU session, the SMF shall apply the corresponding procedures towards the access network and the UPF for the establishment of the redundant user plane paths as defined in clause 5.33.2.1 of 3GPP TS 23.501 [2]. + +The PCF shall not modify during the PDU session lifetime the indication of whether the redundant user plane paths are allowed for the PDU session. + +#### 4.2.2.21 User Plane Remote Provisioning of UE SNPN Credentials in Onboarding Network + +User Plane Remote Provisioning of UEs SNPN Credentials when in Onboarding Network (ONN) is provided using a PDU session for a DNN and S-NSSAI used for onboarding. + +The PCF may make authorization and policy decisions to restrict the use of the PDU Session established to the DNN and S-NSSAI used for onboarding in an ONN, e.g., by restricting the traffic to/from Provisioning Server address(es) and DNS server address(es) only. An ONN is either an ON-SNPN or a PLMN/SNPN. + +When the ONN is an ON-SNPN and the "PvsSupport" feature is supported, during the PDU session establishment procedure related to a PDU session used for User Plane Remote Provisioning, the SMF shall include the indication that the PDU session is used for onboarding with the "onboardInd" attribute set to true and provide within "pvsInfo" attribute, if available, the information related to the Provisioning Server(s) that provisions the UE with credentials and other data to enable SNPN access. + +NOTE 1: When an SNPN that provides access to localized services is acting as ON-SNPN, the SMF includes both DCS provided and the locally configured PVS IP address(es) and/or PVS FQDN(s), in the request to the PCF. + +If the "onboardInd" attribute set to true is received during the SM policy association establishment, the PCF deducts that the combination of the received DNN within "dnn" attribute and the S-NSSAI within "sliceInfo" attribute corresponds to a PDU session used for User Plane Remote Provisioning. In this case, the PCF shall omit the subscription data check with UDR. Instead, the PCF shall use the locally stored Onboarding Configuration Data for this DNN and S-NSSAI combination to make authorization and policy decisions. + +If the "pvsInfo" attribute with the Provisioning Server(s) information is received in the request, the PCF shall use the received information to create the service data flow template of the Provisioning Server(s) in the derived PCC Rule(s). If the "pvsInfo" attribute is not received, the PCF shall construct this service data flow template(s) based on the local configuration stored as part of the Onboarding Configuration Data. In addition, the PCF may create service data flow templates for the DNS server address(es) stored as part of the Onboarding Configuration Data. The "pvsInfo" attribute provided by the SMF may include, for each provided Provisioning Server, the Provisioning Server IP address(es) and/or FQDN(s). + +NOTE 2: How the PCF resolves a Provisioning Server FQDN to an IP address or IP address range with other mechanism than local configuration in the Onboarding Configuration Data is not specified in this release of the specification + +The PCF shall select the QoS information of the PCC rule(s) applicable to the User Plane Remote Provisioning service based on policies locally configured at the PCF as part of the Onboarding Configuration Data. + +The PCF shall install the derived PCC Rule(s) in the response. The installed PCC Rule(s) shall take precedence over the locally stored PCC Rule(s) in the SMF. + +When the SMF detects that the provisioning of PCC Rules failed, the PCC rule error handling procedures shall be performed. + +NOTE 3: When the ONN is a PLMN or a SNPN, the SMF does not provide the "onboardInd" attribute and the "pvsInfo" attribute. The PCF retrieves policy control subscription profile for this SUPI, DNN, S-NSSAI from UDR, that includes the list of allowed services. If the list of allowed services includes both PVS and DNS services, then the PCF, based on local policies, determines the PVS and DNS address(es) to be used in the SDF template of the PCC Rule(s) and allows traffic to/from these destinations as per currently specified procedures. + +#### 4.2.2.22 Network slice related data rate policy control + +When an Npcf\_SMPolicyControl\_Create request is received, the PCF may check if the S-NSSAI to which the received request relates is subject to network slice data rate policy control. If it is the case, the PCF shall apply network slice data rate control as described in clause 4.2.6.8. + +#### 4.2.2.23 Group related data rate policy control + +When an Npcf\_SMPolicyControl\_Create request is received, the PCF may apply group data rate control as described in clause 4.2.6.9. + +#### 4.2.2.24 Network slice usage control + +When the PCF receives a Npcf\_SMPolicyControl\_Create request and the "NetSliceUsageCtrl" feature is supported, the PCF may check whether the S-NSSAI to which the received request relates is subject to network slice usage control. If it is the case, the PCF may provision in the Npcf\_SMPolicyControl\_Create response the network slice usage control information (e.g., the slice PDU session inactivity timer value) within the "sliceUsgCtrlInfo" attribute of the SmPolicyDecision data structure, as specified in clause 5.15.15.3 of 3GPP TS 23.501 [2]. + +NOTE: In this release of the specification, network slice usage control information provisioning by the PCF is not supported in roaming scenarios. + +### 4.2.3 Npcf\_SMPolicyControl\_UpdateNotify Service Operation + +#### 4.2.3.1 General + +The UpdateNotify service operation provides updated Session Management related policies to the NF service consumer (SMF) or triggers the deletion of the context of SM related policies. The POST method is used for both update and terminate operations. + +The following procedures using the Npcf\_SMPolicyControl\_UpdateNotify service operation are supported: + +- PCF initiated update of the policies associated with a PDU session. +- PCF initiated deletion of the SM Policy Association of a PDU session. +- Provisioning of PCC rules. +- Provisioning of policy control request triggers. +- Provisioning of revalidation time. + +- Policy provisioning and enforcement of the authorized AMBR per PDU session. +- Policy provisioning and enforcement of the authorized default QoS. +- Provisioning of PCC rules for Application Detection and Control. +- 3GPP PS Data Off Support. +- IMS Emergency Session Support. +- Request Access Network Information. +- Request Usage Monitoring Control. +- Request for the result of PCC rule removal. +- Access Network Charging Identifier request. +- Request successful resource allocation notifications. +- IMS Restoration Support. +- P-CSCF Restoration Enhancement Support. +- Access traffic steering, switching and splitting support. +- Policy provisioning and enforcement of AF session with required QoS. +- Forwarding of TSC user plane node management information and port management information received from the TSN AF or TSCTSF. +- Provisioning of TSCAI input information and TSC QoS related data. +- Policy provisioning of QoS Monitoring control. +- Policy decision and condition data error handling. +- Network slice related data rate policy control. +- Request of Presence Reporting Area Change Report. +- PCC Rule Error Report. +- Session Rule Error Report. +- Group related data rate policy control. +- VPLMN Specific Offloading Policy. +- Support of Network Slice Usage Control. + +#### 4.2.3.2 SM Policy Association Update request + +![Sequence diagram for SM Policy Association Update request](67d03c9e89620d73e3786c869e559752_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note left of PCF: 1. POST {notificationUri}/update + NF service consumer->>PCF: Request + Note right of PCF: 2a. 200OK + Note right of PCF: 2b. 204 No Content + PCF-->>NF service consumer: Response +``` + +The diagram illustrates the interaction between an NF service consumer and a PCF for an SM Policy Association Update request. The sequence starts with the NF service consumer sending a POST request to the PCF. The PCF responds with either a 200OK or a 204 No Content status. + +Sequence diagram for SM Policy Association Update request + +Figure 4.2.3.2-1: SM Policy Association Update request + +The PCF may decide to provision policies related to an Individual SM Policy resource without obtaining a request from the NF service consumer, e.g. in response to information provided to the PCF via the Rx or N5 reference points, or in response to an internal trigger within the PCF, e.g., the activation of a pending policy counter provided via the Nchf\_SpendingLimitControl Service (see 3GPP TS 29.594 [63]). The PCF shall send for this purpose a POST request to the NF service consumer (e.g. SMF) using the URI "{notificationUri}/update". The content of the message shall contain a SmPolicyNotification data structure that contains: + +- the representation of the updated policies within the "smPolicyDecision" attribute; and +- the resource URI of the Individual SM Policy resource related to the notification within the "resourceUri" attribute. + +Detailed procedures related to the provisioning and enforcement of the policy decisions contained within the SmPolicyDecision data structure are provided in clause 4.2.6. + +When the PCF has received from an NF service consumer (e.g., an AF) temporal invalidity conditions information for a PDU session of a UE or group of UE(s), the PCF shall evaluate the temporal invalidity conditions of the AF request and may inform the SMF to install, modify or remove the corresponding policy decisions (e.g. PCC rule(s)) according to the evaluation result. + +In case of a successful update of SM policies: + +- if the PCF provisioned policy control request triggers (applicable triggers are as defined in Table 5.6.2.26-1), a "200 OK" response code and a response body with the corresponding available information in the "UeCampingRep" data structure shall be returned in the response; +- otherwise, a "204 No Content" response code shall be returned in the response. + +NOTE: When there is an ongoing procedure that collisions with the update of SM policies (e.g. during handover from 5GS to EPS) the SMF, based on operator policies, can delay the update of SM policies and return a "204 No Content" response code. In this case the SMF will process the request when the procedure is finished. + +If errors occur when processing the HTTP POST request, the NF service consumer shall send an HTTP error response as specified in clause 5.7. + +If the feature "ES3XX" is supported, and the NF service consumer determines the received HTTP POST request needs to be redirected, the NF service consumer shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +If the "SessionRuleErrorHandler" feature is not supported and the NF service consumer received one or more PCC rules from the PCF, but the validation of all these PCC Rules was unsuccessful, the NF service consumer shall reject the request and include in an HTTP "400 Bad Request" response message the ErrorReport data structure. Within the ErrorReport data structure, the NF service consumer shall include the "error" attribute containing the "cause" attribute of the ProblemDetails data structure set to "PCC\_RULE\_EVENT" or "PCC\_QOS\_FLOW\_EVENT" and the "ruleReports" attribute to report the PCC rule status of the affected PCC rules as defined in clause 4.2.3.16. + +If the "SessionRuleErrorHandler" feature is supported and the NF service consumer received one or more PCC rules and/or session rules from the PCF but the validation of all these PCC Rules and/or session rules was unsuccessful, the NF service consumer shall reject the request and include in an HTTP "400 Bad Request" response message the ErrorReport data structure. Within the ErrorReport data structure, the NF service consumer shall include the "error" attribute containing the "cause" attribute of the ProblemDetails data structure set to "RULE\_PERMANENT\_ERROR" or "RULE\_TEMPORARY\_ERROR" and the "ruleReports" attribute to report the PCC rule status of the affected PCC rules as defined in clause 4.2.3.16 and/or the "sessRuleReports" attribute to report the session rule status of the affected session rules as defined in clause 4.2.3.20. + +If in the cases above, if the "PolicyDecisionErrorHandler" feature is supported, the PCF provisioned policy decisions and/or condition data which are not referred by any PCC rules or session rules and, in addition of the report of the faulty PCC rule(s) and/or session rule(s), the NF service consumer needs to report the failed policy decisions and/or condition data, the "policyDecFailureReports" attribute shall also be provided as described in clause 4.2.3.26. Additionally, if the "ExtPolicyDecisionErrorHandler" feature is supported the NF service consumer may also provide the "invalidPolicyDecs" as described in clause 4.2.3.26.2. + +If the "Ext2PolicyDecisionErrorHandling" feature is supported, the NF service consumer did not receive neither PCC rules nor session rules and received policy decision types and/or condition types which are not referred by any PCC rules or session rules, and the storage of all the policy decision types and/or condition data was unsuccessful (e.g. the policy decision could not be successfully stored due to a limitation of resources at the SMF) or there were semantical inconsistencies in the provided data, the NF service consumer shall include in an HTTP "400 Bad Request" response message the ErrorReport data structure including the "error" attribute containing the "cause" attribute of the ProblemDetails data structure set to "POL\_DEC\_ERROR" and shall behave as defined in clause 4.2.3.26. + +If the "SessionRuleErrorHandling" feature is not supported and if the NF service consumer received one or more PCC rules from the PCF but the validation of some of them was unsuccessful, the NF service consumer shall include an HTTP "200 OK" status code together with one or more RuleReport data structure(s) to report the PCC rule status of the affected PCC rules as defined in clause 4.2.3.16 in the "PartialSuccessReport" data structure included in the response message. The "failureCause" attribute of the "PartialSuccessReport" shall be set to "PCC\_RULE\_EVENT" or "PCC\_QOS\_FLOW\_EVENT". + +If the "SessionRuleErrorHandling" feature is supported and the NF service consumer received one or more PCC rule and/or session rules from the PCF but the validation of some of them was unsuccessful, the NF service consumer shall include an HTTP "200 OK" status code together with the "ruleReports" attribute to report the PCC rule status of the affected PCC rules as defined in clause 4.2.3.16 and/or the "sessRuleReports" attribute to report the session rule status of the affected session rules as defined in clause 4.2.3.20 in the "PartialSuccessReport" data structure included in the response message. The "failureCause" attribute of the "PartialSuccessReport" shall be set to "RULE\_PERMANENT\_ERROR" or "RULE\_TEMPORARY\_ERROR". + +If the "PolicyDecisionErrorHandling" feature is supported, the NF service consumer received policy decision types and/or condition types which are not referred by any PCC rules or session rules, and the storage or validation of not all the policy decision types and/or condition data was unsuccessful, the NF service consumer shall reply with an HTTP "200 OK" response message and behave as described in clause 4.2.3.26. + +If the PCF provisioned policy control request triggers and the NF service consumer needs to report partial success information, the NF service consumer may include in the "PartialSuccessReport" data structure the "ueCampingRep" attribute with the corresponding available information. When it is required to report multiple instances of the "PartialSuccessReport" data structure due to different "failureCause" values, the NF service consumer shall use only one instance of the "PartialSuccessReport" data structure to include the "ueCampingRep" attribute with the corresponding available information. + +#### 4.2.3.3 SM Policy Association termination request + +![Sequence diagram showing SM Policy Association termination request. The NF service consumer sends a POST {notificationUri}/terminate request to the PCF, and the PCF responds with a 204 No Content.](18291be12b470a557e8c9f3a74e021be_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note left of NF service consumer: 1. POST {notificationUri}/terminate + NF service consumer->>PCF: 1. POST {notificationUri}/terminate + Note right of PCF: 2. 204 No Content + PCF-->>NF service consumer: 2. 204 No Content +``` + +Sequence diagram showing SM Policy Association termination request. The NF service consumer sends a POST {notificationUri}/terminate request to the PCF, and the PCF responds with a 204 No Content. + +**Figure 4.2.3.3-1: SM Policy Association termination request** + +The PCF may request PDU session termination and the corresponding deletion of the Individual SM policy resource in the following circumstances: + +- If the PCF decides to terminate a PDU session due to an internal trigger or a trigger from the UDR. +- The PCF may also decide to terminate a PDU session upon receiving a POST message from the NF service consumer (e.g. when data usage quota is reached). + +The PCF shall send a POST request to the NF service consumer (e.g. SMF) using the URI {notificationUri}/terminate and include the TerminationNotification data structure in the body of the HTTP POST request. Within the TerminationNotification data structure, the PCF shall include: + +- the resource URI of the Individual SM policy resource related to the termination request within the "resourceUri" attribute; and +- the cause of why the PCF requests the termination of the policy association within the "cause" attribute. + +If the NF service consumer accepts the received POST request, the NF service consumer shall send a "204 No Content" response. + +After the successful processing of the HTTP POST request, the NF service consumer shall invoke the Npcf\_SMPolicyControl\_Delete Service Operation defined in clause 4.2.5 to terminate the policy association and initiate the procedure to terminate the PDU session as defined in 3GPP TS 29.502 [22]. + +If errors occur when processing the HTTP POST request, the NF service consumer shall send an HTTP error response as specified in clause 5.7. + +If the feature "ES3XX" is supported, and the NF service consumer determines the received HTTP POST request needs to be redirected, the NF service consumer shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +#### 4.2.3.4 Provisioning of revalidation time + +During the lifetime of a PDU session, within the SmPolicyDecision data structure, the PCF may provide the revalidation time within the "revalidationTime" attribute and the "RE\_TIMEOUT" policy control request trigger within the "policyCtrlReqTriggers" attribute to instruct the SMF to trigger an interaction with the PCF to request PCC rule(s) if not provided yet. The PCF may also update the revalidation time by including the new value within the "revalidationTime" attribute. The PCF may disable the revalidation function by removing the "RE\_TIMEOUT" policy control request trigger, if it has been previously provided. + +When the SMF receives the revalidation time within the "revalidationTime" attribute, the SMF shall store the received value and start the associated timer based on it. Then, the SMF shall trigger a PCC rule request towards the PCF before the indicated revalidation time. + +If the "RE\_TIMEOUT" policy control request trigger is removed, the SMF shall stop the associated timer. + +NOTE: By disabling the revalidation function, the revalidation time value previously provided to the SMF is not applicable anymore. + +#### 4.2.3.5 Policy provisioning and enforcement of authorized AMBR per PDU session + +The PCF may modify the authorized Session-AMBR at any time during the lifetime of the PDU session and provision it to the SMF by invoking the procedure defined in clause 4.2.3.2. + +If the "VPLMN-QoS-Control" feature is supported, the PCF shall ensure that the authorized Session-AMBR value does not exceed the Session-AMBR supported by the VPLMN, if applicable. + +The PCF shall provision the new authorized session AMBR to the SMF as defined in clauses 4.2.6.3.1 and 4.2.6.3.2. + +Upon reception of the authorized Session-AMBR, the SMF shall apply the corresponding procedures towards the access network, the UE and the UPF for the enforcement of the AMBR for the concerned PDU session. + +For UL Classifier or Multi-homing PDU Sessions, the SMF will provision the policies of session-AMBR for the downlink and uplink directions to the UL Classifier/Branching Point functionality and in addition provision the policies of Session-AMBR for the downlink direction to all the PDU session anchors, as defined in clause 5.4.4 of 3GPP TS 29.244 [13]. + +#### 4.2.3.6 Policy provisioning and enforcement of authorized default QoS + +The PCF may modify the authorized default QoS during the lifetime of the PDU session and provision it to the SMF by invoking the procedure defined in clause 4.2.3.2. + +If the "VPLMN-QoS-Control" feature is supported, the PCF shall ensure that the authorized default QoS contains 5QI and ARP values, and MBR/GBR values, if applicable, and if the feature "VPLMN-5QIPrioLevel" is supported, a 5QI Priority Level (when the required 5QI Priority Level is different from the standardized Default Priority Level value in the QoS characteristics Table 5.7.4-1 in 3GPP TS 23.501 [2]), supported by the VPLMN, if applicable. + +The PCF shall provision the authorized default QoS to the SMF as defined in clauses 4.2.6.3.1 and 4.2.6.3.2. + +Upon reception of the authorized default QoS, the SMF enforces it, which may lead to the change of the subscribed default QoS. The SMF shall apply the corresponding procedures towards the access network, the UE and the UPF for the enforcement of the authorized default QoS for the concerned PDU session. + +#### 4.2.3.7 Provisioning of PCC rule for Application Detection and Control + +If the ADC feature is supported, the user subscription indicates that application detection and control is enabled, and the PCF determines that application detection is required because of e.g. an internal/external trigger or the PCF has received from an NF service consumer (e.g. another PCF or an AF) a subscription to the event for application start/stop traffic detection (see TS 29.514 [17], clause 4.2.6.9 for PCF subscription to application detection control and TS 29.523 [61], clause 4.2.2 for AF subscription to application detection control), the PCF may provision PCC rule(s) for application detection and control as defined in clause 4.2.6.2.11 in the notification (i.e. HTTP POST) request. + +When the PCF provisions PCC rule(s) for application detection and control the PCF update of the mute indication is not allowed during the PDU session lifetime, i.e., if for the PCC rule, the application's start or stop notifications are muted, the PCC rule shall remain with the application's start or stop notifications muted along the PDU session lifetime, and viceversa, if for the PCC rule, the application's start or stop notifications are not muted, the PCC rule shall remain with the application's start or stop notifications not muted along the PDU session lifetime. The SMF shall reject the PCC rule modification as specified in clause 4.2.6.2.11. + +If the SMF receives PCC rule(s) for application detection and control, the SMF shall instruct the UPF to detect the application traffic as defined in 3GPP TS 29.244 [13]. + +#### 4.2.3.8 3GPP PS Data Off Support + +When the PCF receives service information from the AF while the 3GPP PS Data Off handling functionality is active as described in clause 4.2.2.8 or 4.2.4.8, the PCF shall check: + +- for a non-MA PDU session, whether the corresponding service is a 3GPP PS Data Off Exempt Service and permissible according to the user's subscription and the policies of the PCF; +- for a MA PDU session: + - a. whether the corresponding service is a 3GPP Data Off Exempt Service and permissible according to the user's subscription and the policies of the PCF; or + - b. whether the corresponding service does not belong to the 3GPP PS Data Off Exempt Services, but: + - the non-3GPP access is available; and + - the PCF policies allow all the traffic of the service to be forwarded using the non-3GPP access. + +If so, the PCF shall install, modify or delete the corresponding PCC rules. For a MA PDU session and when the service does not belong to the 3GPP PS Data Off Exempt Services, the policy for ATSSS Control included in the PCC rule, as specified in clause 4.2.6.2.17, shall enable all the traffic to be forwarded using only the non-3GPP access. + +Otherwise, the PCF shall reject the service information from the AF. + +If the PCF determines that the 3GPP PS Data Off handling functionality becomes inactive, the PCF shall make the necessary policy control decisions and provision the PCC rules to make sure that services are allowed according to the user's subscription and operator policy (irrespective of whether they belong to the list of 3GPP PS Data Off Exempt Services). + +NOTE: The PCF can then open gates via the "flowStatus" attribute for active PCC rules associated to services not contained in the list of 3GPP PS Data Off Exempt Services. The PCF can also install PCC rules or activate predefined PCC rules for some services not belonging to the list of 3GPP PS Data Off Exempt Services. If the PCF activates or installs a PCC rule with wildcarded filters, it can remove or de-activate PCC rules for 3GPP PS Data Off Exempt Services that are redundant to this PCC rule. + +#### 4.2.3.9 IMS Emergency Session Support + +##### 4.2.3.9.1 Provisioning of PCC rule + +When the PCF receives IMS service information from the AF for an Emergency service and derives authorized PCC Rules from the service information, the "priorityLevel", the "preemptCap" and the "preemptVuln" attributes of the Arp data structure within the QoS data decision to which each PCC Rule refers shall be assigned values (i.e. priority and pre-emption level) as required by local operator policies (e.g. if an IMS Emergency session is prioritized, the "priorityLevel" attribute may contain a value that is reserved for an operator domain use of IMS Emergency session). + +The PCF shall immediately initiate the procedures described in clause 4.2.6.2.1 to provision the necessary PCC Rules and the procedures described in clause 4.2.6.2.3 to provision the authorized QoS perPCC rule. + +The provisioning at the SMF of PCC Rules, which require the establishment of a dedicated QoS flow for emergency services, shall cancel the inactivity timer in the SMF, if it started running as defined in the clause 4.2.3.9.2. + +Any SMF-initiated request for PCC Rules for an IMS Emergency service with the "repPolicyCtrlReqTriggers" attribute containing the "RES\_MO\_RE" value (i.e. UE-initiated resource reservation) shall be rejected by the PCF via an HTTP "403 Forbidden" response message including the "cause" attribute of the ProblemDetails data structure set to "ERROR\_TRAFFIC\_MAPPING\_INFO\_REJECTED". + +The SMF shall execute the procedures to ensure that a new QoS flow is established for the Emergency service. + +When the SMF detects that the provisioning of PCC Rules failed, the PCC rule error handling procedure shall be performed. + +##### 4.2.3.9.2 Removal of PCC Rules for Emergency Services + +The reception by the PCF of a request to terminate an AF session for an IMS Emergency service triggers the removal by the PCF of the PCC Rules assigned to the terminated IMS Emergency Service in the SMF, using the procedure defined in clause 4.2.6.2.1. + +At reception of an HTTP POST message that removes one or several PCC Rules from a PDU Session restricted to emergency services, the SMF shall: + +- initiate a QoS flow termination procedure, when all the PCC Rules bound to a QoS flow are removed; or +- initiate a QoS flow modification procedure, when not all the PCC Rules bound to a QoS flow are removed. + +In addition, the SMF shall initiate an inactivity timer if all PCC Rules with a 5QI other than the 5QI of the default QoS flow or the 5QI used for IMS signalling were removed from the PDU session restricted to Emergency Services (e.g. to enable PSAP Callback session). When the inactivity timer expires, the SMF shall initiate a PDU session termination procedure as defined in clause 4.2.5. + +#### 4.2.3.10 Request of Access Network Information + +If the NetLoc feature defined in clause 5.8 is supported, the PCF may request the SMF to report the access network information as defined in clause 4.2.6.5.4. + +#### 4.2.3.11 Request Usage Monitoring Control + +If the UMC feature defined in clause 5.8 is supported, the PCF may provision the usage monitoring control policy to the SMF, as defined in clause 4.2.6.5.3, to request the activation of usage monitoring control. + +#### 4.2.3.12 IPv6 Multi-homing support + +During the lifetime of the Multi-homing PDU session, the PCF shall provision the PCC rules and session rules to the SMF. The SMF shall derive the appropriate policies based on the policies provisioned by the PCF and provision them to the appropriate UPF, if applicable, access network, if applicable, and UE, if applicable. + +#### 4.2.3.13 Request for the result of PCC rule removal + +If the RAN-NAS-Cause feature is supported, the PCF may request the SMF to inform it of the result of PCC rule(s) removal, when the PCF removes PCC rule(s) as defined in clause 4.2.6.5.2. + +When the SMF receives the request, the SMF shall maintain locally the removed PCC rules(s) until it receives the resource release outcome from the network. + +#### 4.2.3.14 Access Network Charging Identifier request + +The PCF may request the SMF to provide the Access Network Charging Identifier associated to the dynamic PCC rules as defined in clause 4.2.6.5.1. + +#### 4.2.3.15 Request for the successful resource allocation notification + +The PCF may request the SMF to confirm that the resources associated to a PCC rule are successfully allocated as defined in clause 4.2.6.5.5. + +#### 4.2.3.16 PCC Rule Error Report + +If the SMF receives one or more PCC rule(s) as defined in clause 4.2.3.1, but the validation of all the received PCC Rules was unsuccessful, the SMF shall reject the request via an HTTP "400 Bad Request" status code and include in the corresponding response message the "ruleReports" attribute containing RuleReport data structure(s) to report the failure for the affected PCC rule(s) within the ErrorReport data structure; otherwise, if the validation of only some of the received PCC rules was unsuccessful, the SMF shall reply to the PCF with an HTTP "200 OK" status code and include in the corresponding response message one or more RuleReport data structure(s) to report the failure for the affected PCC rule(s) within the PartialSuccessReport data structure. + +Within each RuleReport instance, the SMF shall identify the failed PCC rule(s) by including their identifiers within the "pccRuleIds" attribute, identify the failure reason code by including a "failureCode" attribute, and include the PCC rule(s) status within the "ruleStatus" attribute containing a value as follows: + +- If the installation/activation of one or more new PCC rules (i.e. rules which were not previously successfully installed) fails, the SMF shall set the "ruleStatus" attribute value to "INACTIVE". +- If the modification of a currently active PCC rule fails, the SMF shall retain the existing PCC rule as active without any modification, unless the reason for the failure has an impact also on the existing PCC rule. + +The removal of a PCC rule shall never fail, even if the related PDU session procedures with the UE fail. The SMF shall retain information on the removal of the PDU session and conduct the necessary PDU session procedures with the UE when it is possible. + +Depending on the value of the "failureCode" attribute, the PCF may decide whether retaining, re-installation, modification or removal of the old PCC rule or any other action applies. + +If the "RuleVersioning" feature is supported and the PCF included the "contVer" attribute for a specific PCC rule instance in the "pccRules" attribute when provisioning this PCC rule to the SMF, then if the resource allocation for the corresponding PCC rule was unsuccessful, the SMF shall include the "contVers" attribute in the corresponding RuleReport instance within the "ruleReports" attribute. Depending on the value of the "failureCode" attribute, and when applicable, depending also on the value of the "contVer" attribute, the PCF may decide whether retaining, re-installation, modification, removal of the old PCC rule or any other action applies. + +#### 4.2.3.17 IMS Restoration Support + +If the ProvAFsignalFlow feature defined in clause 5.8 is supported, and in order to support IMS Restoration procedures (refer to 3GPP TS 23.380 [21]), the PCF needs to convey the AF address to the SMF. In order to do so, in case the AF + +provisions information about the AF signalling flows between the UE and the AF, as defined in clause 4.4.5a of 3GPP TS 29.214 [18], or in clauses 4.2.2.16 and 4.2.3.17 of 3GPP TS 29.514 [17], the PCF shall install the corresponding dynamic PCC rules (if not installed before) as defined in clause 4.2.6.2.1. The PCF shall include within the associated PccRule instance(s) the signalling flows between the UE and the AF within the "flowInfos" attribute and the "afSigProtocol" attribute set to the value corresponding to the signalling protocol used between the UE and the AF. + +The SMF shall respond to the PCF with an HTTP "204 no content" and initiate the corresponding QoS flow procedures, if required. The SMF shall extract the AF address from the provisioned PCC rule(s) and use it for the monitoring procedures as defined for the different access types. + +NOTE 1: The SMF can use the extracted AF address from the PCC rule(s) to check if the monitoring procedures have to be started for the corresponding AF. + +In case the AF de-provisions information about the AF signalling flows between the UE and the AF, as defined in clause 4.4.5a of 3GPP TS 29.214 [18], or in clauses 4.2.2.16 and 4.2.3.17 of 3GPP TS 29.514 [17], the PCF shall remove the corresponding dynamic PCC rule(s) by triggering a notification (i.e. HTTP POST) message towards the SMF. The PCF shall then apply the procedures defined in clause 4.2.6.2.1. + +The SMF shall send an HTTP response message to the PCF. + +NOTE 2: The SMF can use the AF address associated with the removed PCC rule(s) to check if it can stop monitoring the corresponding AF. + +#### 4.2.3.18 P-CSCF Restoration Enhancement Support + +This clause is applicable when the PCF-based P-CSCF Restoration Enhancement, as defined in 3GPP TS 23.380 [21] and controlled by the feature "PCSCF-Restoration-Enhancement" defined in clause 5.8, is supported by both the PCF and the SMF. + +If the PCF receives a request for P-CSCF restoration from the P-CSCF as defined in clause 4.4.7 of 3GPP TS 29.214 [18] or in clause 4.2.2.27 of 3GPP TS 29.514 [17], the PCF shall send a notification (i.e. HTTP POST) message to the SMF including the "pcscfRestIndication" attribute set to true for the corresponding PDU session. + +The SMF shall acknowledge the PCF and initiate the corresponding QoS flow procedures for the IMS PDU connection as defined in 3GPP TS 23.380 [21]. + +#### 4.2.3.19 Request of Presence Reporting Area Change Report + +If the PRA or ePRA feature defined in clause 5.8 is supported, the PCF may provision the Presence Reporting Area Information to the SMF as defined in clause 4.2.6.5.6. + +#### 4.2.3.20 Session Rule Error Report + +If the "SessionRuleErrorHandling" feature is supported and the SMF receives one or more session rule(s) as defined in clause 4.2.6.3.1 but the validation of all the received session rules was unsuccessful, the SMF shall reject the request via an HTTP "400 Bad Request" status code and include in the corresponding response message the "sessRuleReports" attribute containing SessionRuleReport data structure(s) to report the failure for the affected session rule(s) within the ErrorReport data structure; otherwise, if the validation of some of the received session rules was unsuccessful, the SMF shall reply to the PCF with an HTTP "200 OK" status code and include in the corresponding response message the "sessRuleReports" attribute containing one or more SessionRuleReport data structure(s) to report the failure for the affected session rule(s) within the PartialSuccessReport data structure. + +Within each SessionRuleReport instance, the SMF shall identify the failed session rule(s) by including their identifier(s) within the "ruleIds" attribute, identify the failure reason code by including a "sessRuleFailureCode" attribute, and include the session rule(s) status within the "ruleStatus" attribute containing a value as follows: + +- If the installation of one or more new session rule(s) (i.e. rules which were not previously successfully installed) fails, the SMF shall set the "ruleStatus" attribute value to "INACTIVE". +- If the modification of a currently provisioned session rule fails, the SMF shall retain the existing session rule as provisioned without any modification, unless the reason for the failure has an impact also on the existing session rule. The SMF shall report the modification failure to the PCF. + +The removal of a session rule shall never fail, even if the related PDU session procedures with the UE fail. The SMF shall then retain information on the removal of the PDU session and conduct the necessary PDU session procedures with the UE when it is possible. + +Depending on the value of the "sessRuleFailureCode" attribute, the PCF may decide whether retaining, re-installation, modification or removal of the old session rule, or any other action applies. + +#### 4.2.3.21 Access traffic steering, switching and splitting support + +If the PCF supports the "ATSSS" feature, the PCF may provide PCC rules and/or session rules for the MA PDU session as defined in clause 4.2.6.2.17 and clause 4.2.6.3.4. + +#### 4.2.3.22 Policy provisioning and enforcement of the AF session with required QoS + +If the PCF receives a QoS reference parameter during the initial provisioning of service information as defined in clause 4.2.2.32 of 3GPP TS 29.514 [17], or if the PCF receives individual QoS parameters during the initial provisioning of service information as defined in clause 4.2.2.24 of 3GPP TS 29.514 [17], the PCF shall authorize the service information from the AF and derive the QoS parameters of the related PCC rule(s) based on the received service information and the indicated QoS reference parameter or the indicated individual QoS parameters (e.g. Requested Maximum Bitrate and Requested Guaranteed Bitrate). + +**NOTE:** A SLA has to be in place between the operator and the ASP defining the possible QoS levels and their charging rates. For each possible pre-defined QoS information set, the PCF needs to be configured with the corresponding QoS parameters and their values as well as the appropriate Charging key (or receive this information from the UDR). + +If the PCF receives a different QoS reference parameter or different individual QoS parameters during the modification of service information as defined in clause 4.2.3.30 of 3GPP TS 29.514 [17], the PCF shall update accordingly the related QoS parameters corresponding to the new QoS parameter in the related PCC rule(s). + +If the AF subscribes to Service Data Flow QoS notification control, the PCF may additionally receive the Alternative Service Requirements during the initial provisioning of service information as defined in clause 4.2.2.32 of 3GPP TS 29.514 [17]. + +In this case, when the PCF authorizes service information based on the indicated QoS reference parameter or individual QoS parameters, and the "AuthorizationWithRequiredQoS" feature is supported, the PCF shall additionally derive alternative QoS parameter sets for the concerned PCC rule(s) based on the QoS reference parameters or individual QoS parameters provided in the Alternative Service Requirements. In order to do so, the PCF shall include one or more references to the QosData data structure within the "refAltQosParams" attribute of the concerned PCC rule(s) and a "qosDecs" attribute containing these QoS data decision(s) within the SmPolicyDecision data structure. In each QoS data decision instance, the PCF shall include the alternative QoS parameter set Id within the "qoSId" attribute, the alternative packet delay budget within the "packetDelayBudget" attribute, the alternative packet error rate within the "packetErrorRate" attribute, the alternative guaranteed bandwidth in uplink within the "gbrUI" attribute and the alternative guaranteed bandwidth in downlink within the "gbrDI" attribute. The "refAltQosParams" attribute is an ordered list of alternative QoS parameter sets, where the lower the index of the array for a given entry, the higher the priority. + +If the AF changes or newly provides the Alternative Service Requirements during the modification of service information as defined in clause 4.2.3.30 of 3GPP TS 29.514 [17], the PCF shall update accordingly or provide the Alternative QoS parameter sets in the related PCC rule(s). + +If the "PDUSetHandling" feature is supported and the PCF receives PDU Set QoS requirements during the initial provisioning of service information as defined in clause 4.2.2.39 of 3GPP TS 29.514 [17], the PCF shall determine the PDU Set QoS parameters based on the received requirements and include them within the "pduSetQoS" attribute. + +The PCF shall provision the related PCC rule(s) with alternative QoS parameter set(s) and enable QoS Notification Control, if it has not been enabled yet, as defined in clause 4.2.3.30 of 3GPP TS 29.514 [17]. + +If the "DisableUENotification" feature is supported and if the AF indicated to the PCF that the UE does not need to be informed about changes related to Alternative QoS Profiles as defined in clause 4.2.2.32 or 4.2.3.30 of 3GPP TS 29.514 [17] and the PCF decides to disable the notifications to the UE when changes related to the Alternative QoS Profiles occur, the PCF shall include the "disUeNotif" attribute set to true within the corresponding the PCC rule instance. + +When the SMF receives PCC rule(s) with alternative QoS parameter sets, the SMF shall enforce these PCC rule(s) and derive in addition the alternative QoS profile(s) towards the access network based on the received alternative QoS parameter set(s). + +#### 4.2.3.23 Forwarding of TSC user plane node management information and port management information received from the TSN AF or TSCTSF + +During the lifetime of a PDU session enabling Time Sensitive Communications, Time Synchronization and Deterministic Networking the PCF may receive a UMIC and/or, when the DS-TT or the NW-TT functions are used, one or more PMIC(s) from the TSN AF or TSCTSF within the service information and/or, the indication of direct notification for the UPF to report the TSC management information as defined in 3GPP TS 29.514 [17]. A UMIC carries TSC user plane node management information. A PMIC carries port management information for a port located in DS-TT and/or NW-TT. + +**NOTE:** The 5GS Architecture to support IETF Deterministic Networking (IETF RFC 8655 [55]) does not require the DS-TT functionality to be supported in the device nor require the user plane NW-TT functionality to be supported in the UPF. However, it can co-exist with such functions. + +If the feature "TimeSensitiveNetworking" or "TimeSensitiveCommunication" is supported the PCF initiates the Npcf\_SMPolicyControl\_UpdateNotify request and sends possibly updated policy information about the PDU Session and/or the UMIC and/or the PMIC(s) to the SMF via the SmPolicyDecision structure, in which the UMIC is encoded in the "tsnBridgeManCont" attribute, the DS-TT PMIC is encoded in the "tsnPortManContDstt" attribute and the one or more NW-TT PMIC(s) are encoded in the "tsnPortManContNwtt" attribute. + +The PMIC(s) are encoded in the "PortManagementContainer" data type, that includes the port management information in the "portManCont" attribute and the related port number in the "portNum" attribute. If the port is on DS-TT the SMF forwards the PMIC(s) to the DS-TT port. If the port is on NW-TT the SMF forwards the PMIC(s) to the NW-TT port. + +The UMIC is encoded in the "BridgeManagementContainer" data type, that includes the TSC user plane node management information in the "bridgeManCont" attribute. The SMF always forwards the UMIC to the TSC user plane node functionality of the UPF/NW-TT. + +If the "ExposureToTSC" feature is supported, and the TSCTSF or TSN AF has requested direct UPF notifications, the PCF shall set the notification URI within the "tscNotifUri" attribute and the notification correlation id within the "tscNotifCorrId" attribute corresponding to values provided by the TSCTSF or TSN AF. In this case, the SMF shall forward the received direct notification information to the UPF. + +**Editor's note:** It is FFS whether further adjustments to direct TSC event notification information are needed based on SA2 definition in TS 23.503. + +#### 4.2.3.24 Provisioning of TSCAI input information and TSC QoS related data + +The PCF may receive the TSCAI input information in the TSC assistance container and TSC traffic QoS related information from the TSN AF or TSCTSF. + +If the feature "TimeSensitiveNetworking" or "TimeSensitiveCommunication" is supported by both the SMF and PCF as described in clause 5.8, the PCF shall provide for the derived PCC rule(s): + +- the 5G QoS parameters and the optional 5G QoS characteristics corresponding to a 5QI for a delay-critical GBR derived from the TSC traffic QoS information received from the TSN AF or TSCTSF encoded within a QosData type referred in the "refQosData" of the PCC rule; and +- the TSCAI input information as received from the TSN AF or TSCTSF, which may contain the periodicity, and burst arrival time encoded in the "tscaiInputUI" attribute and/or "tscaiInputDI" attribute of the PCC rule, when the feature "TimeSensitiveCommunication" is supported, the survival time encoded in the "tscaiInputUI" attribute and/or "tscaiInputDI" attribute and the (TSN)AF (g)PTP domain encoded in the "tscaiTimeDom" attribute, and when the feature "EnTSCAC" is supported, the burst arrival time window within the "burstArrivalTimeWnd" attribute, or capability for BAT adaptation encoded in the "capBatAdaptation" attribute, and either the acceptable periodicity range includes a lower bound encoded in the "lowerBound" attribute and an upper bound encoded in the "upperBound" attribute or a list of the acceptable periodicity value(s) encoded in the "periodicVals" attribute within the "periodicityRange" attribute. + +The values of MDBV and PDB applied to the derived 5QI shall follow principles defined in clause 5.27.3 of 3GPP TS 23.501 [2]. + +For IEEE TSN networks, the value of the MBR, if applicable, and the GBR are derived using the Maximum Bit Rate provided by the TSN AF. For other time sensitive communication networks, the value of the GBR may be derived using the input provided by the TSCTSF (e.g. the Minimum Bit Rate) and applying the QoS mapping procedures as specified in clause 7.3.3 of 3GPP TS 29.513 [7]. + +The ARP is assigned a value preconfigured for TSC services. + +As specified in clause 4.2.3.22, when the PCF receives a QoS reference from the TSCTSF, the PCF shall derive the above QoS parameters based on pre-defined QoS parameters referenced by the QoS reference. When the PCF receives individual QoS parameters from the TSCTSF, the PCF shall set derived QoS parameters based on the received individual QoS parameters and applying the QoS mapping procedures as specified in clause 7.3.3 of 3GPP TS 29.513 [7]. + +If the PCF receives Alternative Service Requirements that contain QoS references from the TSCTSF, the PCF shall derive the alternative QoS parameter set(s) based on the pre-defined QoS parameters referenced by the received Alternative Service Requirements as defined in clause 4.2.3.22. If the PCF receives Alternative Service Requirements that contain Requested Alternative QoS Parameter Set(s) from the TSCTSF, the PCF shall set the alternative QoS parameter set(s) based on the Requested Alternative QoS Parameter Set(s) contained in the received Alternative Service Requirements as defined in clause 4.2.3.22. + +The SMF shall convert the received TSCAI input information from the external GM into the 5G GM based on the time offset and cumulative rateRatio (when available) between external time and 5GS time as measured and reported by the UPF and, forward the derived TSCAI parameters per QoS Flow basis to the AN-RAN as follows: + +- For the traffic in downlink direction, the SMF shall correct the value of the "burstArrivalTime" attribute of the "tscaiInputDI" attribute based on the latest received time offset measurement from the UPF and set the downlink TSCAI Burst Arrival Time as the sum of the corrected value and the CN PDB as described in clause 5.7.3.4 of 3GPP TS 23.501 [2], representing the latest possible time when the first packet of the data bursts arrives at the AN. +- For the traffic in uplink direction, the SMF shall correct the value of "burstArrivalTime" attribute of the "tscaiInputUI" attribute based on the latest received time offset measurement from the UPF and set the uplink TSCAI Burst Arrival Time as the sum of corrected value and the UE-DS-TT Residence Time representing the latest possible time when the first packet of the data burst arrives at the egress of the UE. How the SMF corrects the Burst Arrival Time if the UE-DS-TT residence time has not been provided by the UE is up to SMF implementation. +- The SMF shall correct the value of "periodicity" attribute of the "tscaiInputUI" and/or "tscaiInputDI" using the cumulative rateRatio if the cumulative rateRatio measurement was previously received from the UPF and set the TSCAI Periodicity as the corrected value. Otherwise, the SMF shall set the periodicity in the TSCAI Periodicity without any correction. +- If the "TimeSensitiveCommunication" feature is supported and the TSCAI Survival Time Information is received: + - when the "surTimeInNumMsg" attribute is received, the SMF shall convert the value of "surTimeInNumMsg" attribute of the "tscaiInputUI" and/or "tscaiInputDI" attributes into time units by multiplying its value by the corrected uplink TSCAI Periodicity and/or downlink TSCAI Periodicity respectively, and set the TSCAI Survival Time to the calculated value; or + - when the "surTimeInTime" is received, the SMF shall correct the value of "surTimeInTime" attribute of the "tscaiInputUI" and/or "tscaiInputDI" attributes using the cumulative rateRatio if the cumulative rateRatio measurement was previously received from the UPF and set the TSCAI Survival Time to the corrected value. Otherwise, the SMF shall set the TSCAI Survival Time without correction. +- If the "EnTSCAC" feature is supported and the burst arrival time is provided, either the burst arrival time window or the capability for BAT adaptation may be received: + - when the burst arrival time window is received, for the traffic in downlink direction, the SMF shall correct the value of the "burstArrivalTimeWnd" attribute of the "tscaiInputDI" attribute in the same ways it is described for the correction of the burst arrival time in downlink as above and for the traffic in uplink + +direction, the SMF shall correct the value of "burstArrivalTimeWnd" attribute of the "tscaiInputUI" attribute in the same ways it is described for the correction of the burst arrival time in uplink in this clause; or + +NOTE 1: It is preferred that the range of the "burstArrivalTimeWnd" attribute contains the value of the "burstArrivalTime". + +- when the capability for BAT adaptation is received, the SMF shall set the value of "capBatAdaptation" attribute as the value of capability for BAT adaptation in the TSCAI. +- when the PCF receives the subscription for the notification on network provided BAT offset from the AF/NEF or TSCTSF, then PCF shall include "BAT\_OFFSET\_INFO" policy control request trigger within the "policyCtrlReqTriggers" attribute in the SmPolicyDecision data structure, if it has not been provisioned yet. +- when the burst arrival time window is received, if the periodicity range (either the acceptable periodicity range or the acceptable periodicity set) is received, the SMF shall correct the value of the "lowerBound" attribute and the "upperBound" attribute, or the "periodicVals" attribute within the "periodicityRange" attribute of the "tscaiInputUI" and/or "tscaiInputDI" using the same way as it is described for the correction of the periodicity in this clause. +- If the "EnTSCAC" feature is supported and the burst arrival time is not provided, only the capability for BAT adaptation may be received: + - when the value of the "capBatAdaptation" attribute as the capability for BAT adaptation is received, the SMF enables notification control for the QoS Flow (if not already enabled) in order to receive the BAT offset along with the "GFBR can no longer be guaranteed" notification from the NG-RAN. + +If the "TimeSensitiveCommunication" feature is supported, depending on whether the Time Domain information is included in the "tscaiTimeDom" attribute of the PCC rule, SMF may perform the following: + +- if the "tscaiTimeDom" attribute is not included in the PCC rule, the SMF provisions the UPF/NW-TT to report the clock drifting between 5G clock and the external GM clock for the (g)PTP time domain number that is configured to the NW-TT. +- if the "tscaiTimeDom" attribute is included in the PCC rule and does not indicate Time Domain = "5GS", the SMF provisions the UPF/NW-TT to report the clock drifting between 5G clock and the external GM clock for the received Time Domain information. + +NOTE 2: The Time Domain value corresponding to "5GS" is locally configured in the SMF and in the TSCTSF and indicates that the AF does not provide a Time Domain, as specified in 3GPP TS 29.565 [53], and it is not needed to adjust the TSCAI input information. The omission of the Time Domain within the "tscaiTimeDom" attribute of the PCC rule indicates it is needed to apply the TSN AF time domain, configured in the NW-TT, to adjust the TSCAI input information. + +The SMF shall use the N4 Association Setup or Update procedures as described in 3GPP TS 29.244 [13] to provision the UPF to report the clock drifting. + +If the SMF receives the clock drifting from the UPF for a Time Domain, and + +- if the received Time Domain matches the Time Domain information within the "tscaiTimeDom" attribute included in the PCC rule; or +- the "tscaiTimeDom" attribute is not included within the PCC rule, + +then the SMF may determine the time offset and cumulative rateRatio (when available) based on received Time Domain information and adjust the TSCAI information as described above. + +If the received clock drifting from the UPF does not match the Time Domain information within the "tscaiTimeDom" attribute of the PCC rule or the received "tscaiTimeDom" attribute of the PCC rule indicates Time Domain = "5GS" then the SMF will not adjust the TSCAI information. + +The provisioning of TSCAI input information and TSC traffic QoS configuration per PCC Rule shall be performed using the PCC rule provisioning procedure as defined in clause 4.2.6.2.1. + +#### 4.2.3.25 Policy provisioning of QoS Monitoring control + +##### 4.2.3.25.1 General + +The QoS Monitoring control refers to the real time measurement of QoS parameters between the UE and the UPF for a QoS flow. + +NOTE 1: The AF can request measurements for one or more QoS parameters, which can trigger QoS monitoring control for service data flow(s). This clause describes QoS monitoring control for packet delay, congestion, and data rate. + +If the "QosMonitoring" feature is supported, the PCF may generate the authorized QoS Monitoring data decision for the service data flow for packet delay based on the QoS Monitoring request if received from the AF, or when the feature "EnSatBackhaulCatChg" is supported, based on PCF local policy or configuration as described in subclause 4.2.3.25.2. + +The PCF, when the request is received from the AF, may determine whether the QoS monitoring report is sent to the AF/NEF by the SMF bypassing the PCF or by the PCF. When the feature "ExposureToEAS" is supported and the AF indication of direct notification is received, the PCF may determine whether duplicate notification by the UPF is required, i.e., whether the QoS monitoring report is directly sent to the local AF/NEF and to the PCF/SMF. When the "UPEAS" feature is supported, the PCF may generate a Data Collection Application Identifier based on the AF request or local configuration to be used in the SMF to associate the PCC rule with a QoS monitoring event exposure subscription. + +The PCF shall include within the SmPolicyDecision data structure one or more QosMonitoringData instances within the "qosMonDecs" attribute if not provided yet and, if the PCF determines that the QoS monitoring report shall be sent by the PCF from the SMF, "QOS\_MONITORING" within the "policyCtrlReqTriggers" attribute, if it has not been provisioned yet. + +NOTE 2: The QoS monitoring report can be sent by the SMF to the PCF as described in clause 4.2.4.24. The QoS monitoring report of the PCF to the AF/NEF is described in 3GPP TS 29.514 [17], the QoS monitoring report of the SMF to the AF/NEF bypassing the PCF is described in 3GPP TS 29.508 [12] and the QoS monitoring report to the Local NEF/AF by the UPF is described in 3GPP TS 29.564 [50]. + +When the features "QoSMonitoring" and "NscSupportedFeatures" are supported and if the NEF/AF provided information about the support of "QoSMonitoring" feature on Nsmf\_EventExposure service, the PCF may also include this information within the "nscSuppFeats" attribute included within the PccRule data type. + +For each QosMonitoringData instance, PCF shall include: + +- the requested QoS monitoring parameter(s) to be measured (i.e. DL/UL round trip packet delay and/or, if the "EnQoSMon" feature is supported, congestion information and/or data rate) within the "reqQosMonParams" attribute; +- the frequency(s) of reporting (e.g. event triggered and/or periodic) within the "repFreqs" attribute; +- for the case the "repFreqs" attribute includes the value "EVENT\_TRIGGERED": + - a. for QoS monitoring for packet delay: + - the delay threshold for downlink with the "repThreshDI" attribute if "reqQosMonParams" attribute includes DOWNLINK; + - the delay threshold for uplink with the "repThreshUI" attribute if "reqQosMonParams" attribute includes UPLINK; and/or + - the delay threshold for round trip with the "repThreshRp" attribute if "reqQosMonParams" attribute includes ROUND\_TRIP; + - b. for QoS monitoring for data rate: + - the data rate threshold for downlink within the "repThreshDatRateDI" attribute if the "reqQosMonParams" attribute includes DOWNLINK\_DATA\_RATE; and/or + - the data rate threshold for uplink within the "repThreshDatRateUI" attribute if the "reqQosMonParams" attribute includes UPLINK\_DATA\_RATE; + +- c. for QoS monitoring for congestion information: + - the congestion threshold for downlink within the "repThreshConDI" attribute if the "reqQosMonParams" attribute includes DOWNLINK\_CONGESTION; and/or + - the data rate threshold for uplink within the "repThreshConUI" attribute if the "reqQosMonParams" attribute includes UPLINK\_CONGESTION; and +- d. the minimum waiting time between subsequent reports within the "waitTime" attribute; and +- e. if the feature "PacketDelayFailureReport" or "EnQoSMon" is supported, the maximum period with no QoS measurement results reported within the "repPeriod" attribute; +- for the case the "repFreqs" attribute includes "PERIODIC", the periodic time for reporting and, if the feature "PacketDelayFailureReport" or "EnQoSMon" is supported, the maximum period with no QoS measurement results reported within the "repPeriod" attribute; +- either the notification URI within the "notifyUri" attribute and the notification correlation id within the "notifyCorrId" attribute if the PCF determines that the notification shall be sent to the AF directly from the SMF or the notification URI within the "notifyUri" attribute, the notification correlation id within the "notifyCorrId" attribute corresponding to the Local NEF or AF and the "directNotifInd" attribute set to true if the feature "ExposureToEAS" and/or the feature "EnQoSMon" is supported and the PCF determines that the direct notification by the UPF to the Local NEF or AF is required based on the indication of direct notification received from the AF; and + +**Editor's note:** It is FFS whether new data type structure is needed for QoS monitoring control for multi-modal services. + +**NOTE 3:** If the feature "ExposureToEAS" is supported and if the PCF determines to receive QoS Monitoring report while direct UPF notification is also required, the PCF can provision the "QOS\_MONITORING" policy control request trigger to the SMF together with the "directNotifInd" attribute set to true. + +**Editor's note:** Whether the applicable reporting frequency for the Data Rate QoS monitoring can be event triggered and/or periodic is FFS. + +- the Data Collection Application Identifier within the "dataCollAppId" attribute if the "UPEAS" feature is supported and if the PCF determines that the SMF has to associate the PCC rule with a QoS monitoring event exposure subscription for that application identifier as described in 3GPP TS 29.508 [12]. + +If the feature "EnQoSMon" is supported, and QoS monitoring control is for data rate, may include the averaging window within the "avrgWndw" attribute. + +The PCF shall include the value of QoS Monitoring Data ID of QosMonitoringData instance within the "refQosMon" attribute of the corresponding PCC rule and provide the QoS monitoring data decision together with the PCC rule if it has not been provisioned to the SMF. When the SMF receives the PCC rule, the SMF shall send a QoS Monitoring request to the PSA UPF via N4 as defined in 3GPP TS 29.244 [13] and NG-RAN via N2 signalling to request the QoS monitoring between PSA UPF and NG-RAN as defined in 3GPP TS 29.502 [22]. If the feature "ExposureToEAS" is supported and if the SMF receives both the "QOS\_MONITORING" policy control request trigger and the indication of direct notification, the SMF shall request the UPF to perform duplicated notification as defined in 3GPP TS 29.244 [13]. If the "UPEAS" feature is supported, when the SMF receives the Data Collection Application Identifier within the "dataCollAppId" attribute as part of the QosMonitoringData instance of the PCC rule, the SMF shall associate the PCC rule with the QoS monitoring event exposure subscription related to that application identifier as described in 3GPP TS 29.508 [12]. + +If the PCF receives the request from the local NEF/AF to disable the QoS monitoring from the AF or the Local NEF, the PCF shall update the PCC rule with the "refQosMon" attribute set to NULL. The PCF may also remove the corresponding QoS Monitoring Data if no PCC rule is referring to it. + +If the PCF receives the request to disable the direct event notification to the local NEF or AF by the UPF, the PCF shall determine whether the PCF or the SMF bypassing the PCF sends the QoS monitoring reports to the local AF/NEF: + +- a. if the QoS monitoring reports are sent by the SMF bypassing the PCF: + +- update the PCC rule with the "refQosMon" attribute referring a QosMonitoringData instance which does not include the "directNotifInd" attribute set to true and still includes the "notifyUri", and the "notifyCorreId" attributes; or + - update the corresponding QosMonitoringData instance by including the "directNotifInd" attribute set to false and still keeping the "notifyUri", and the "notifyCorreId" attributes; +- b. if the QoS monitoring reports are sent by the PCF: +- update the PCC rule with the "refQosMon" attribute referring a QosMonitoringData instance which does not include the "directNotifInd", the "notifyUri", and the "notifyCorreId" attributes or update the QosMonitoringData instance by removing the "directNotifInd", the "notifyUri", and the "notifyCorreId" attributes; and + - provision the value "QOS\_MONITORING" within the "policyCtrlReqTriggers" attribute, if not previously provided. + +The SMF shall request to the UPF to disable the notification to the AF/(Local)NEF via N4 as defined in 3GPP TS 29.244 [13] and shall start sending the related notifications to PCF or to the indicated Notification URI and notification correlation Id, as applicable. + +If the PCF determines that QoS monitoring report shall be sent to the PCF from the SMF instead of sent from the SMF bypassing the PCF, the PCF shall replace the QosMonitoringData instance with an instance that does not include the "notifyUri" and the "notifyCorreId" attributes and include "QOS\_MONITORING" within the "policyCtrlReqTriggers" attribute if it has not been provisioned yet. If the PCF determines that QoS monitoring report shall be sent from the SMF bypassing the PCF instead of sent from the SMF to the PCF, the PCF shall update the QosMonitoringData instance by including the the notification URI within the "notifyUri" attribute and the notification correlation id within the "notifyCorreId" attribute, and remove the value "QOS\_MONITORING" within the "policyCtrlReqTriggers" attribute. + +#### 4.2.3.25.2 QoS Monitoring when dynamic Satellite Backhaul is used + +If the features "QosMonitoring" and "EnSatBackhaulCatChg" are supported, and if dynamic satellite backhaul is used, QoS monitoring may be used by the PCF to measure packet delay as specified in clause 4.2.3.25.1. + +If the PCF has subscribed to backhaul category changes within the "SAT\_CATEGORY\_CHG" policy control request trigger as described on clause 5.6.3.6, and the dynamic satellite backhaul is used to serve the PDU session, the PCF may, based on the local policy or configuration, request QoS Monitoring for the packet delay between UE and PSA UPF and the corresponding QoS Monitoring reports. The PCF shall include within the SmPolicyDecision data structure one or more QosMonitoringData instances within the "qosMonDecs" attribute if not provided yet, within the affected PCC rules, a reference to the corresponding QosMonitoringData instance, and the "QOS\_MONITORING" value within the "policyCtrlReqTriggers" attribute, if it has not been provisioned yet The PCF may take the reported packet delay information into account for the policy decision along with other criteria, such as the AF requested QoS requirements. + +#### 4.2.3.26 Policy decision error handling + +##### 4.2.3.26.1 Policy decision types and condition data error handling + +If the "PolicyDecisionErrorHandling" feature is supported and the "ExtPolicyDecisionErrorHandling" feature is not supported, and the SMF receives one or more policy decision type(s) (as defined in clause 4.1.4.4) and/or condition data (as defined in clause 4.1.8), which are not referred by any provisioned PCC rule or session rule as defined in clause 4.2.3.2, but the storage of the policy decision types and/or condition data was unsuccessful (e.g. the policy decision could not be successfully stored due to a limitation of resources at the SMF) or there are semantical inconsistencies in the provided data, the SMF shall behave as follows: + +- Include an HTTP "200 OK" status code and one or more PolicyDecisionFailureCode data types to indicate the type(s) of the failed policy decisions and/or condition data in the response message, if the SMF does not need to report any other information (e.g. the failure reports of the PCC rule(s) or session rule(s) which are provisioned in the same message, are not needed). +- Include an HTTP "200 OK" status code and one or more PartialSuccessReport data structure(s) including the "policyDecFailureReports" attribute to indicate the type(s) of the failed policy decisions and/or condition data and the "failureCause" attribute set to "POL\_DEC\_ERROR" in the response message, if the SMF needs to report + +partial success (e.g. some of the PCC rules and/or session rules provisioned by the PCF in the same message were not installed/activated successfully). + +- Include an HTTP "400 Bad Request" status code and the ErrorReport data structure including the "policyDecFailureReports" attribute to indicate the type(s) of the failed policy decisions and/or condition data in the response message, if the SMF needs to reject the request (e.g. all the PCC rules and/or session rules provisioned by the PCF in the same message were not installed/activated successfully). + +NOTE: An error within a policy decision type and/or condition data not referred by any PCC rules or session rules is encoded within the "policyDecFailureReports" attribute as specified in the PolicyDecisionFailureCode data structure defined in clause 5.6.3.28. + +When the PCF receives the above reports, the PCF shall consider all the instances of the policy decisions and/or condition data which were provisioned in the request message and indicated in the PolicyDecisionFailureCode data type as removed from the SMF. When the PCF receives a response with HTTP "400 Bad Request" status code but the "policyDecFailureReports" attribute is not included in the provided ErrorReport data structure, the PCF shall consider all the provisioned instances of the policy decisions and/or condition data in the request message as removed from the SMF. + +The removal of a policy decision type and/or condition data shall not fail. + +#### 4.2.3.26.2 Policy decision types, condition data and other policy decisions error handling + +If the "ExtPolicyDecisionErrorHandler" feature is supported and the SMF receives one or more policy decision type(s) (as defined in clause 4.1.4.4) and/or condition data (as defined in clause 4.1.8), which are not referred by any provisioned PCC rule or session rule as defined in clause 4.2.3.2, and/or other SM policy decisions (e.g. the SMF receives policy control request triggers and applicable additional information) and the SMF detects that the received policy decision(s) cannot be enforced (e.g. because of semantical inconsistencies in the provided data): + +- If the SMF does not need to reject the request (e.g. none, or only some but not all, of the PCC rule(s) and/or session rule(s) provisioned by the PCF in the same message are not installed/activated successfully), the SMF shall include one or more PartialSuccessReport data structure(s) in the response message with an HTTP "200 OK" status code. In order to report the partial success of policy decision and/or condition data, the SMF shall include in the related PartialSuccessReport data structure(s) the "failureCause" attribute set to "POL\_DEC\_ERROR" and the "policyDecFailureReports" attribute to indicate the failed policy decision type(s) and/or condition data that are not referred by any provisioned PCC rule or session rule and/or in other SM policy decision(s), and may include the "invalidPolicyDecs" attribute to provide more details on these failed policy decision type(s) and/or condition data that are not referred by any provisioned PCC rule or session rule and/or other SM policy decisions. +- If the SMF needs to reject the request (e.g. all the PCC rules and/or session rules provisioned by the PCF in the same message are not installed/activated successfully), the SMF shall include an ErrorReport data structure within a response message with an HTTP "400 Bad Request" status code. The SMF shall include the "policyDecFailureReports" attribute to indicate a failed policy decision type(s) and/or condition data that are not referred by any provisioned PCC rule or session rule and/or in other SM policy decisions, and may include the "invalidPolicyDecs" attribute to provide more details on these failed policy decision types and/or condition data that are not referred by any provisioned PCC rule or session rule and/or other SM policy decisions. In addition, when "Ext2PolicyDecisionErrorHandler" feature is supported and the NF service consumer needs to reject the request because the PCF only provided policy decision/condition data and all of them were faulty, the NF service consumer shall include the ErrorReport data structure with the "error" attribute containing the "cause" attribute of the ProblemDetails data structure set to "POL\_DEC\_ERROR". + +NOTE 1: An error within a policy decision type and/or condition data not referred by any PCC rules or session rules and/or an error in other policy decisions is encoded within the "policyDecFailureReports" attribute as specified in the PolicyDecisionFailureCode data structure defined in clause 5.6.3.28. + +When the PCF receives the above reports, the PCF shall behave as follows: + +- For the policy decisions and/or condition data: + - a. The PCF shall consider all the instances of the policy decision(s) and/or condition data which are provisioned in the request message and indicated in the PolicyDecisionFailureCode data type as removed from the SMF. + +- b. When the PCF receives a response with HTTP "400 Bad Request" status code but the "policyDecFailureReports" attribute is not included in the provided ErrorReport data structure, the PCF shall consider all the provisioned instance(s) of the policy decision(s) and/or condition data in the request message as removed from the SMF. + - c. The removal of a policy decision type and/or condition data shall not fail. +- For the other policy decisions: +- a. The PCF shall consider all the new failed policy decisions provisioned in the request message and indicated in the PolicyDecisionFailureCode data type as not installed in the SMF. + - b. The PCF shall consider all the modified policy decisions provisioned in the request message and indicated in the PolicyDecisionFailureCode data type as unmodified in the SMF. + - c. The PCF shall consider all the removed policy decisions provided in the request message as deleted in the SMF. + +NOTE 2: The removal of a policy decision does not fail. Even if there is an inconsistency e.g. between the deletion of a policy control request trigger and the deletion of the applicable additional information, the whole related policy decision is removed. + +#### 4.2.3.27 Network slice related data rate policy control + +At the time a PCF-initiated change of the authorized Session-AMBR occurs or PCC Rule(s) for GBR service data flow(s) need to be provisioned at the SMF, the PCF may check if the concerned S-NSSAI is subject to network slice data rate policy control. If it is the case, the PCF shall apply network slice data rate control as described in clause 4.2.6.8. + +#### 4.2.3.28 Group related data rate policy control + +At the time a PCF-initiated change of the authorized Session-AMBR occurs or PCC Rule(s) for GBR service data flow(s) need to be provisioned at the SMF, the PCF may apply group data rate control as described in clause 4.2.6.9. + +#### 4.2.3.29 Policy provisioning of Traffic Parameter to be measured + +If the "PowerSaving" feature is supported, the PCF may send the Periodicity information "periodInfo" attribute received from the AF or NEF and together with the indication for SMF to request the UPF to perform the Traffic Parameter(s) measurement within the PCC rules. The Traffic Parameter(s) to be measured includes the downlink periodicity associated N6 jitter range and the Uplink and/or downlink periodicity information "periodInfo" attribute if the Periodicity information is not received from the AF. + +If the PCC rule indicates to perform the Traffic Parameter(s) measurement, the SMF requests the UPF to monitor and periodically report the measured Traffic Parameter(s) using the N4 Session Modification procedure. Upon reception of the measured Traffic Parameter(s) from the UPF, the SMF includes the measured N6 jitter range and the associated downlink periodicity in the TSCAI and forwards it to the NG-RAN to assist configuration UE power saving. + +#### 4.2.3.30 Network slice usage control + +When a PCF-initiated change of the SM policies shall be performed by the PCF via the Npcf\_SMPolicyControl\_UpdateNotify service operation and the "NetSliceUsageCtrl" feature is supported, the PCF may check whether the S-NSSAI of the concerned SM Policy Association is subject to network slice usage control. If it is the case, the PCF may provision/update/remove in the Npcf\_SMPolicyControl\_UpdateNotify request the network slice usage control information (e.g., the slice PDU session inactivity timer value) within the "sliceUsgCtrlInfo" attribute of the SmPolicyDecision data structure provided within the "smPolicyDecision" attribute of the SmPolicyNotification data structure. + +NOTE: In this release of the specification, network slice usage control information provisioning/update/removal by the PCF is not supported in roaming scenarios. + +## 4.2.4 Npcf\_SMPolicyControl\_Update Service Operation + +### 4.2.4.1 General + +The Npcf\_SMPolicyControl\_Update service operation provides means for the NF service consumer to inform the PCF that a policy control request trigger condition has been met and for the PCF to inform the NF service consumer of any resulting update of the Session Management related policies. + +The following procedures using the Npcf\_SMPolicyControl\_Update service operation are supported: + +- Provisioning of PCC rules. +- Provisioning of policy control request triggers. +- Request the policy based on revalidation time. +- Policy provisioning and enforcement of authorized AMBR per PDU session. +- Policy provisioning and enforcement of authorized default QoS. +- Application detection information reporting. +- Indication of QoS Flow Termination Implications. +- 3GPP PS Data Off Support. +- Request and report Access Network Information. +- Request Usage Monitoring Control and report Accumulated Usage. +- Ipv6 Multi-homing support. +- Request and report the result of PCC rule removal. +- Access Network Charging Identifier Request and report. +- Request and report the successful resource allocation notification. +- Negotiation of the QoS flow for IMS signalling. +- Notification about Service Data Flow QoS target enforcement. +- Request the termination of SM Policy association. +- Reporting of TSC user plane node management information and port management information. +- QoS Monitoring Report. +- Policy decision and condition data error handling. +- Request the policy after DDN failure events. +- Network slice related data rate policy control. +- Presence Reporting Area Information Report. +- PCC Rule Error Report. +- Session Rule Error Report. +- UE initiates a resource modification support. +- Trace Control. +- Group related data rate policy control. +- Support of Network Slice Usage Control. + +#### 4.2.4.2 Requesting the update of the Session Management related policies + +![Sequence diagram showing the interaction between an NF service consumer and a PCF. The NF service consumer sends a POST request to the PCF to update an Individual SM Policy resource. The PCF responds with a 200 OK status.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant NF service consumer + participant PCF + Note right of NF service consumer: 1. POST /sm-policies/{smPolicyId}/update + NF service consumer->>PCF: Request + Note left of PCF: 2. 200 OK + PCF-->>NF service consumer: Response + +``` + +Sequence diagram showing the interaction between an NF service consumer and a PCF. The NF service consumer sends a POST request to the PCF to update an Individual SM Policy resource. The PCF responds with a 200 OK status. + +**Figure 4.2.4.2-1: Requesting the update of the Session Management related policies** + +When the NF service consumer detects that one or more policy control request triggers are met, the NF service consumer shall send a POST request to the PCF to update an Individual SM Policy resource. The {smPolicyId} in the URI identifies the Individual SM Policy resource to be updated. The NF service consumer include SmPolicyUpdateContextData data structure in the content of the HTTP POST to request a update of representation of the "Individual SM Policy" resource. The NF service consumer shall include the met policy control request trigger(s) within the "repPolicyCtrlReqTriggers" attribute and applicable updated value(s) in the corresponding attribute(s). + +The NF service consumer shall include (if the corresponding policy control request trigger is met and the applicable information is available) in SmPolicyUpdateContextData data structure: + +- type of access within the "accessType" attribute; +- type of the radio access technology within the "ratType" attribute; +- the new allocated UE Ipv4 address within the "ipv4Address" attribute and/or the UE Ipv6 prefix within the "ipv6AddressPrefix" attribute; +- an additional new allocated UE Ipv6 prefix within the "addIpv6AddrPrefixes" attribute, if the "MultiIpv6AddrPrefix" feature is supported; +- multiple new allocated UE Ipv6 prefixes within the "multiIpv6Prefixes" attribute, if the "UnlimitedMultiIpv6Prefix" feature is supported; +- the released UE Ipv4 address within the "relIpv4Address" attribute and/or the UE Ipv6 prefix within the "relIpv6AddressPrefix" attribute; +- an additional released UE Ipv6 prefix within the "addRelIpv6AddrPrefixes" attribute, if the "MultiIpv6AddrPrefix" feature is supported; +- multiple released UE Ipv6 prefixes within the "multiRelIpv6Prefixes" attribute, if the "UnlimitedMultiIpv6Prefix" feature is supported; +- the UE MAC address within the "ueMac" attribute; +- the released UE MAC address within the "relUeMac" attribute; +- the indication of UE supporting reflective QoS within the "refQosIndication" attribute; +- access network charging identifier within the "accNetChIds" attribute; +- the 3GPP PS data off status within the "3gppPsDataOffStatus" attribute, if the "3GPP-PS-Data-Off" feature is supported; +- the UE time zone information within the "ueTimeZone" attribute; + +- the UDM subscribed Session-AMBR or, if the "DN-Authorization" feature is supported, the DN-AAA authorized Session-AMBR within the "subsSessAmbr" attribute; + +NOTE 1: When both, the UDM subscribed Session-AMBR and the DN-AAA authorized Session-AMBR are available in the NF service consumer, the NF service consumer includes the DN-AAA authorized Session-AMBR. + +- if the "VPLMN-QoS-Control" feature is supported, the highest Session-AMBR and the default QoS supported in the VPLMN within the "vplmnQos" attribute, if available; + +NOTE 2: In home routed roaming, the H-SMF may provide the QoS constraints received from the VPLMN (defined in 3GPP TS 23.502 [3] clause 4.3.2.2.2) to the PCF. + +- if the "DN-Authorization" feature is supported, the DN-AAA authorization profile index within the "authProfIndex" attribute; +- subscribed Default QoS Information within the "subsDefQos" attribute; +- detected application information within the "appDetectionInfos" attribute; +- if the "UMC" feature is supported, the accumulated usage reports within the "accuUsageReports" attribute; +- if the "PRA" feature is supported, the reported presence reporting area information within the "repPraInfos" attribute; +- the QoS flow usage required of the default QoS flow within the "qosFlowUsage" attribute; +- indication whether the QoS targets of one or more SDFs are not guaranteed or guaranteed again within the "qncReports" attribute; +- user location(s) information within the "userLocationInfo" attribute; + +NOTE 3: The SMF encodes both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute when they are both received from the AMF. + +- if the "GroupIdListChange" feature is supported, the Internal Group Identifier(s) of the served UE within the "interGrpIds" attribute; +- if the "SatBackhaulCategoryChg" feature is supported, the satellite backhaul category or non-satellite backhaul and, when the "EnSatBackhaulCatChg" feature is supported, also the dynamic satellite backhaul category, within the "satBackhaulCategory" attribute; +- if the "AMInfluence" feature is supported, the PCF for the UE callback URI and, if received, SBA binding information within the "pcfUeInfo" attribute; +- serving network function identifier within the "servNfId" attribute; +- identifier of the serving network within the "servingNetwork" attribute; +- when the "URSPEnforcement" feature is supported, the URSP rule enforcement information provided by the UE within the "urspEnfInfo" attribute. In this case, the NF service consumer shall also include, if they were not previously provided, the SSC mode within the "sscMode" attribute, the UE requested DNN (if available and different from the selected DNN) within the "ueReqDnn" attribute, and/or if the PDU session is redundant, the RSN and the PDU session pair ID within the "redundantPduSessionInfo" attribute. The NF service consumer shall also provide the "accessType" attribute, if changed compared to the latest reported value; +- if the "EnTSCAC" feature is supported, the BAT offset and the optionally adjusted periodicity within the "batOffsetInfo" attribute; +- when the "EneNA" feature is supported, the list of NWDAF instance IDs used for the PDU Session within the "nwdafInstanceId" and their associated Analytic ID(s) within "nwdafEvents" updated with the new values included within the "nwdafDatas" attribute; + +NOTE 4: The NF service consumer provides the complete updated list of NWDAF instance IDs and associated Analytic ID(s) used for the PDU session. If all NWDAF data is deleted an empty list is included. + +- for HR-SBO scenario, if the "HR-SBO" feature is supported, the H-SMF may include the HR-SBO support indication within the "hrsboInd" attribute; and + +NOTE 5: The "PLMN\_CH" trigger has to be provisioned in order to report this information. + +- if the "NetSliceRepl" feature is supported and the NF service consumer reports a change from the initial S-NSSAI of the PDU Session to the Alternative S-NSSAI via the "NET\_SLICE\_REPL" PCRT, the Alternative S-NSSAI used to replace the existing S-NSSAI for the PDU Session within the "sliceInfo" attribute. + +**Editor's Note:** Whether the initial S-NSSAI is provided to the PCF when the NF service consumer reports a change from the Alternative S-NSSAI to the initial S-NSSAI of the PDU Session via the "NET\_SLICE\_REPL" PCRT is FFS and pending stage 2 feedback. + +The NF service consumer may include in "SmPolicyUpdateContextData" data structure the IPv4 address domain identity within the "ipDomain" attribute. + +In case of a successful update, "200 OK" response shall be returned. The PCF shall include in the "200 OK" response the representation of the updated policies within the SmPolicyDecision data structure. Detailed procedures related to the provisioning and enforcement of the policy decisions within the SmPolicyDecision data structure are contained in clause 4.2.6. + +NOTE 6: An empty SmPolicyDecision data structure is included in the "200 OK" response when the PCF decides not to update policies. + +If the PCF received a new list of NWDAF instance IDs used for the PDU Session in "nwdafInstanceId" attribute and their associated Analytic IDs in "nwdafEvents" attribute included within the "nwdafDatas" attribute the PCF may select those NWDAF instances based on this new list as described in 3GPP TS 29.513 [7]. + +If errors occur when processing the HTTP POST request, the PCF shall send an HTTP error response as specified in clause 5.7. + +If the feature "ES3XX" is supported, and the PCF determines the received HTTP POST request needs to be redirected, the PCF shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +If the PCF is, due to incomplete, erroneous or missing information (e.g. QoS, RAT type, subscriber information) not able to provision a policy decision as response to the request for PCC rules by the NF service consumer, the PCF may reject the request and include in an HTTP "400 Bad Request" response message the "cause" attribute of the ProblemDetails data structure set to "ERROR\_INITIAL\_PARAMETERS". + +If the PCF receives the set of session information which is sent in the message originated due to a trigger being met is incoherent with the previous set of session information for the same session (E.g. trigger met was RAT changed, and the RAT notified is the same as before), the PCF may reject the request and include in an HTTP "400 Bad Request" response message the "cause" attribute of the ProblemDetails data structure set to "ERROR\_TRIGGER\_EVENT". + +If the PCF detects that the packet filters in the request for new PCC rules received from the NF service consumer is covered by the packet filters of outstanding PCC rules that the PCF is provisioning to the NF service consumer, the PCF may reject the request and include in an HTTP "403 Forbidden" response message the "cause" attribute of the ProblemDetails data structure set to "ERROR\_CONFLICTING\_REQUEST". + +If the PCF does not accept one or more of the traffic mapping filters provided by the NF service consumer in an HTTP POST request (e.g. because the PCF does not allow the UE to request enhanced QoS for services not known to the PCF), the PCF shall reject the request and include in an HTTP "403 Forbidden" response message the "cause" attribute of the ProblemDetails data structure set to "ERROR\_TRAFFIC\_MAPPING\_INFO\_REJECTED". + +If the NF service consumer receives HTTP response with these codes, the NF service consumer shall reject the PDU session modification that initiated the HTTP Request. + +The PCF shall not combine a rejection with provisioning of PCC rule operations in the same HTTP response message. + +#### 4.2.4.3 Request the policy based on revalidation time + +If the timer for the policy revalidation is started, the SMF shall send the PCC rule request before the indicated revalidation time. The SMF shall within the SmPolicyUpdateContextData data structure include RE\_TIMEOUT within the "repPolicyCtrlReqTriggers" attribute. The SMF shall stop the timer once the SMF sends the HTTP POST request. + +NOTE 1: The PCF is expected to be prepared to provide a new policy, as desired for the revalidation time, during a preconfigured period before the revalidation time. The preconfigured periods in the SMF and PCF need to be aligned. + +The PCF may instruct the SMF to revalidate the provided PCC rules by including the "revalidationTime" attribute within the SmPolicyDecision in the HTTP POST response. + +NOTE 2: If the PCF omits the "revalidationTime" attribute the revalidation function remains enabled, but the timer remains stopped till the PCF provides a revalidation time within the "revalidationTime" attribute. + +When the SMF receives the HTTP POST response message, the SMF shall start the timer for revalidation based on the received value of revalidation time if the revalidation function is not disabled; otherwise, the SMF shall not start the timer for revalidation. + +The PCF may disable the revalidation function by removing the RE\_TIMEOUT policy control request trigger in the HTTP POST response message. If the revalidation function is disabled, the SMF shall ignore any received value of revalidation time and shall not start the timer for revalidation. + +NOTE 3: By disabling the revalidation function the revalidation time value previously provided to the SMF is not applicable anymore. + +#### 4.2.4.4 Policy provisioning and enforcement of authorized AMBR per PDU session + +When the SMF detects that the Session-AMBR changes, the SMF shall notify of the change to the PCF by invoking the procedure defined in clause 4.2.4.2, and shall include the new Session-AMBR within the "subsSessAmbr" attribute and the "SE\_AMBR\_CH" policy control request trigger within the "repPolicyCtrlReqTriggers" attribute. + +If the "DN-Authorization" feature is supported, when both, the UDM subscribed Session-AMBR and the DN-AAA authorized Session-AMBR are available in the SMF, the DN-AAA authorized/re-authorized Session-AMBR shall take precedence over the changes on UDM subscribed Session-AMBR. + +If the "VPLMN-QoS-Control" feature is supported, + +- in the home routed scenario, when the SMF detects that the Session-AMBR supported in the VPLMN changes (i.e. when the UE moves from the HPLMN to a VPLMN with Session-AMBR constraints or between VPLMNs with different Session-AMBR constraints), the SMF shall notify of the change to the PCF by invoking the procedure defined in clause 4.2.4.2, and shall include the new VPLMN Session-AMBR within the "vplmnQos" attribute and the "VPLMN\_QOS\_CH" policy control request trigger within the "repPolicyCtrlReqTriggers" attribute. +- when the SMF detects that the UE moves from a VPLMN with Session-AMBR constraints to a VPLMN where the QoS constraints are not applicable in the home routed scenario or the UE moves back to the non-roaming scenario, the SMF shall notify the PCF that the QoS constraints in the VPLMN are not applicable by invoking the procedure defined in clause 4.2.4.2, and shall include the "vplmnQosNotApp" attribute set to true and the "VPLMN\_QOS\_CH" policy control request trigger within the "repPolicyCtrlReqTriggers" attribute. + +Upon receiving the change of Session-AMBR, the PCF shall ensure that the authorized Session-AMBR value does not exceed the Session-AMBR supported by the VPLMN, if applicable, and provision the new authorized Session-AMBR to the SMF in the response as defined in clauses 4.2.6.3.1 and 4.2.6.3.2. + +Upon receiving the authorized Session-AMBR from the PCF, the SMF shall apply the corresponding procedures towards the access network, the UE and the UPF for the enforcement of the AMBR per PDU session. + +For UL Classifier or Multi-homing PDU Session, the SMF will provision the policies of session-AMBR for downlink and uplink direction to the UL Classifier/Branching Point functionality and in addition provision the policies of session-AMBR in the downlink direction to all the PDU session anchors as defined in clause 5.4.4 of 3GPP TS 29.244 [13]. + +#### 4.2.4.5 Policy provisioning and enforcement of authorized default QoS + +When the SMF detects that the subscribed default QoS change, the SMF shall notify of the PCF by invoking the procedure as defined in clause 4.2.4.2, include the new subscribed default QoS within the "subsDefQos" attribute and "repPolicyCtrlReqTriggers" set to DEF\_QOS\_CH. + +If the "VPLMN-QoS-Control" feature is supported, + +- in the home routed scenario, when the SMF detects that the default QoS supported in the VPLMN changes (i.e. when the UE moves from the HPLMN to a VPLMN with default QoS constraints or between VPLMNs with different default QoS constraints), the SMF shall notify of the change to the PCF by invoking the procedure defined in clause 4.2.4.2, and shall include the new default QoS value supported in the VPLMN within the "vplmnQos" attribute and the "VPLMN\_QOS\_CH" policy control request trigger within the "repPolicyCtrlReqTriggers" attribute; +- when the SMF detects that the UE moves from a VPLMN with default QoS constraints to a VPLMN where the QoS constraints are not applicable in the home routed scenario or the UE moves back to the non-roaming scenario, the SMF shall notify the PCF that the QoS constraints in the VPLMN are not applicable by invoking the procedure defined in clause 4.2.4.2, and shall include the "vplmnQosNotApp" attribute set to true and the "VPLMN\_QOS\_CH" policy control request trigger within the "repPolicyCtrlReqTriggers" attribute. + +Upon receiving the change of default QoS, the PCF shall ensure that the authorized default QoS contains a 5QI and ARP values supported by the VPLMN, if applicable, and shall provision the authorized default QoS to the SMF in the response of the message as defined in clauses 4.2.6.3.1 and 4.2.6.3.2. + +Upon receiving the authorized default QoS, the SMF enforces it which may lead to the change of the subscribed default QoS. The SMF shall apply the corresponding procedures towards the access network, the UE and the UPF for the enforcement of the authorized default QoS. + +#### 4.2.4.6 Application detection information reporting + +If the ADC feature is supported and if the SMF receives the PCC rule for application detection and control, the SMF shall instruct the UPF as defined in 3GPP TS 29.244 [13] to: + +- Detect the application traffic. +- Report the detected application's traffic start/stop events along with the application instance identifier and service data flow descriptions when service data flow descriptions are deducible. + +When the start of the application's traffic, identified by an application identifier, is received from the UPF, if PCF has previously provisioned the APP\_STA/APP\_STO policy control request trigger, unless a request to mute such a notification (i.e. the "muteNotif" attribute set to true within the Traffic Control Data decision which the PCC rule refers to), the SMF shall report the start of the application to the PCF. + +In order to do so, the SMF shall perform the procedure as defined in clause 4.2.4.2 by including the information regarding the detected application's traffic within the "appDetectionInfos" attribute and the "APP\_STA" within the "repPolicyCtrlReqTriggers" attribute even if the application traffic is discarded due to enforcement actions of the PCC rule. In this case, within the each AppDetectionInfo instance, the SMF shall include the received application identifier within the "appId" attribute, and may include the detected service data flow description within the "sdfDescriptions" attribute if deducible and received and an allocated application instance identifier for the detected service data flow descriptions if received within the "instanceId". The "sdfDescriptions" attribute, if present, shall contain the "flowDescription" attribute and "flowDirection" attribute. The application instance identifier allows the correlation of APP\_STA and APP\_STO policy control request trigger to the specific service data flow descriptions. + +When the stop of the application's traffic, identified by an application identifier is received from the UPF and the SMF has reported the start of the application to the PCF, the SMF shall report the stop of the application to the PCF. In order to do so, the SMF shall perform the procedure as defined in clause 4.2.4.2 by including the information regarding the detected application's traffic within the "appDetectionInfos" attribute and the "APP\_STO" within the "repPolicyCtrlReqTriggers" attribute. For each AppDetectionInfo instance, the SMF shall include the received application identifier within the "appId" attribute and the application instance identifier received from the UPF within the "instanceId" if it is provided along with the APP\_STA to the PCF. + +The PCF then may make policy decisions based on the information received and send the corresponding updated PCC rules to the SMF. + +When a PFD provisioned by the PFDF as specified in 3GPP TS 29.551 [46] is removed/modified and the removed/modified PFD was used to detect application traffic related to an application identifier in a PCC rule installed or activated for a PDU session, if the removed/modified PFD results in that the stop of an application or an application instance is not able to be detected, and if the SMF has reported the application start as described in this clause to the PCF for the application or application instance represented by this PFD, the SMF shall report the application stop to the PCF for the corresponding application or the corresponding application instance, if the stop of the application's traffic, identified by the corresponding application or the corresponding application instance, is received from the UPF. + +NOTE: Multiple PFDs can be associated with the application identifier. When the removed/modified PFD is the last one which is used to detect traffic identified by the "appId" attribute, the SMF reports application stop. + +The PCF is not allowed to update the mute indication of a provisioned PCC rule(s) during the PDU session lifetime, i.e., if for the PCC rule, the application's start or stop notifications are muted, the PCC rule shall remain with the application's start or stop notifications muted along the PDU session lifetime, and viceversa, if for the PCC rule, the application's start or stop notifications are not muted, the PCC rule shall remain with the application's start or stop notifications not muted along the PDU session lifetime. The SMF shall reject the update of the mute indication for a provisioned PCC rule as specified in clause 4.2.6.2.11. + +#### 4.2.4.7 Indication of QoS Flow Termination Implications + +When the SMF detects that a dedicated QoS flow could not be activated or has been terminated it shall remove the affected PCC rules and send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure, including the "ruleReports" attribute containing the RuleReport data instance which specifies the affected PCC rules within the "pccRuleIds" attribute, "INACTIVE" as the value within the "ruleStatus" attribute and the "RES\_ALLO\_FAIL" as the value of the "failureCode" attribute. + +If the RAN-NAS-Cause feature is supported, the SMF shall provide the available access network information within the "userLocationInfo" attribute (if available), "userLocationInfoTime" attribute (if available) and "ueTimezone" attribute (if available). Additionally, if the SMF receives from the access network the RAN cause and/or the NAS cause due to QoS flow termination the SMF shall provide the received cause(s) in the "ranNasRelCauses" attribute included in RuleReport data instance. + +If the NetLoc feature is supported, and if the identifier of the affected PCC rule was included within the "refPccRuleIds" attribute of the RequestedRuleData data structure when the affected PCC rule was installed or modified, the SMF shall provide the access network information to the PCF by including the user location(s) information within the "userLocationInfo" attribute (if requested by the PCF and if provided to the SMF), the information on when the UE was last known to be in that location within "userLocationInfoTime" attribute (if user location information was requested by the PCF and if the corresponding information was provided to the SMF), the PLMN Identifier or the SNPN Identifier (the PLMN Identifier and the NID) within the "servingNetwork" attribute (if the user location information was requested by the PCF but it is not provided to the SMF) and the timezone information within the "ueTimeZone" attribute (if requested by the PCF and available). + +NOTE 1: The SMF derives the value of the "userLocationInfoTime" attribute from the age of location information received from the AMF at PDU session update as described in 3GPP TS 29.502[22]. Whether the "userLocationInfo" attribute also encodes the age of location is implementation specific. + +NOTE 2: The SMF encodes both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute when they are both received from the AMF. + +This shall be done whenever one of these conditions applies: + +- The SMF is requested by the RAN to initiate the deactivation of a QoS flow. +- PCC rule(s) are removed/deactivated by the SMF without PCF request (e.g. due to unsuccessful reservation of resources to satisfy the QoS flow binding). + +NOTE 3: The SMF will not initiate the deactivation of the QoS flow upon reception of the UE-initiated resource modification procedure indicating packet filter deletion. If all the PCC rules associated to a QoS flow have been deleted as a consequence of the PCF interaction, the SMF will initiate the QoS flow termination procedure towards the RAN. + +Signalling flows for the QoS flow termination and details of the binding mechanism are presented in 3GPP TS 29.513 [7]. + +#### 4.2.4.8 3GPP PS Data Off Support + +If the SMF is informed that the 3GPP PS Data Off status of the UE changed, the SMF shall send an HTTP POST message to the PCF, as defined in clause 4.2.4.2, providing the "PS\_DA\_OFF" value within the "repPolicyCtrlReqTriggers" attribute and the "3gppPsDataOffStatus" attribute set to the value indicated by the UE within the "SmPolicyUpdateContextData" data structure. + +Upon reception of this HTTP POST message with the "repPolicyCtrlReqTriggers" attribute set to the value "PS\_DA\_OFF" or "AC\_TY\_CH" the PCF shall determine whether the 3GPP PS Data Off handling functionality (as described below) becomes active or inactive. The 3GPP PS Data Off handling functionality is active if, and only if, + +- the latest received "3gppPsDataOffStatus" attribute is set to true; and + +NOTE 1: If the PS\_DA\_OFF policy control request trigger is received, the latest received value is the one received in the HTTP POST message. Otherwise, it corresponds to the stored value. + +- the UE uses 3GPP access, i.e.: + - for a non MA PDU session, the "accessType" attribute is set to "3GPP\_ACCESS"; and + - for a MA PDU session, either the "accessType" attribute or the "addAccessInfo" attribute indicate "3GPP\_ACCESS", and the "relAccessInfo" attribute either is not available or does not indicate "3GPP\_ACCESS". + +If the PCF determines that the 3GPP PS Data Off handling functionality becomes active, the PCF shall configure the SMF in such a way that: + +- only packets for services belonging to the list of 3GPP PS Data Off Exempt Services are forwarded over 3GPP access; and +- all other downlink packets and optionally uplink packets are: + - for a non-MA PDU session or a MA PDU session where non-3GPP access is not available, discarded by modifying or removing any related dynamic PCC rule(s) or by deactivating any related predefined PCC rule(s); + - for a MA PDU session where non-3GPP access is available, forwarded only via non-3GPP access, if it is ensured by the policy for ATSSS Control as specified in clause 4.2.6.2.17. + +NOTE 2: In order for the UPF to prevent the services that do not belong to the list of 3GPP PS Data Off Exempt Services, if such services are controlled by dynamic PCC rules, the PCF can either close gates for the downlink and optionally the uplink directions via the "flowStatus" attribute in the related dynamic PCC rules or remove those dynamic PCC rules. If the services are controlled by predefined PCC rules, the PCF needs to deactivate those PCC rules. PCC rule(s) with wild-carded service data flow filters can be among the PCC rules that are modified, removed or disabled in that manner. It can then be necessary that the PCF at the same time installs or activates PCC rules for PS Data Off Exempt Services. The network configuration can ensure that at least one PCC rule is bound to the default QoS flow when PS Data Off is activated in order to avoid the deletion of an existing PDU session or to not fail a PDU session establishment. + +If the PCF determines that the 3GPP PS Data Off handling functionality becomes inactive, the PCF shall make the necessary policy control decisions and perform PCC rule operations to make sure that services are allowed according to the user's subscription and operator policy (irrespective of whether they belong to the list of 3GPP PS Data Off Exempt Services or not). + +NOTE 3: The PCF can then open gates via the "flowStatus" attribute for active PCC rules associated to services not contained in the list of 3GPP PS Data Off Exempt Services. The PCF can also install PCC rules or activate predefined PCC rules for some services not belonging to the list of 3GPP PS Data Off Exempt Services. If the PCF activates or installs a PCC rule with wildcared filters, it can remove or de-activate PCC rules for 3GPP PS Data Off Exempt Services that are redundant with this PCC rule. + +#### 4.2.4.9 Request and Report of Access Network Information + +If the NetLoc as defined in clause 5.8 is supported, the PCF may request the SMF to report the access network information as defined in clause 4.2.6.5.4. + +If the AN\_INFO policy control request trigger is set, upon receiving the "lastReqRuleData" attribute with the "reqData" attribute with the value(s) MS\_TIME\_ZONE and/or USER\_LOC\_INFO and the "refPccRuleIds" attribute containing the PCC rule identifier(s) corresponding to the PCC rule(s) which is being installed, modified or removed together, the SMF shall apply the Namf\_EventExposure service for Time-Zone-Report and/or Location-Report event with One-Time Report type as defined in clause 5.3.1 and 5.3.2.2.2 of 3GPP TS 29.518 [36] if the related information is not available to obtain this information. When the SMF then receives access network information from the AMF, the SMF shall provide the required access network information to the PCF by as defined in clause 4.2.4.2 and set the corresponding attributes as follows: + +- If the user location(s) information was requested by the PCF and was provided to the SMF, the SMF shall provide the user location information within the "userLocationInfo" attribute and the time when it was last known within "userLocationInfoTime" attribute (if available). + +NOTE 1: The SMF derives the value of the "userLocationInfoTime" attribute from the age of location information received in the Location-Report (defined in clause 5.3.1 of 3GPP TS 29.518 [36]) from the AMF. Whether the "userLocationInfo" attribute also encodes the age of location is implementation specific. + +NOTE 2: The SMF encodes both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute when they are both received from the AMF. + +- If the user location information was requested by the PCF and was not provided to the SMF, the SMF shall provide the serving PLMN Identifier or the SNPN Identifier (the PLMN Identifier and the NID) within the "servingNetwork" attribute. +- If the time zone was requested by the PCF, the SMF shall provide it within the "ueTimeZone" attribute. + +NOTE 3: If the SMF receives the access network information but receives the rejection of the QoS flow creation or modification, the SMF reports the the enforcement error of the PCC rule to the PCF as defined in clause 4.2.4.15. + +In addition, the SMF shall provide the AN\_INFO policy control request trigger within the "repPolicyCtrlReqTriggers" attribute. + +The SMF shall not report any subsequent access network information updates received from the RAN without any further provisioning or removal of related PCC rules requesting the access network information unless the associated QoS flow or PDU session has been released. + +#### 4.2.4.10 Request Usage Monitoring Control and Reporting Accumulated Usage + +##### 4.2.4.10.1 General + +If the UMC feature, as defined in clause 5.8 is supported, the PCF may provision the usage monitoring control policy to the SMF, as defined in clause 4.2.6.5.3, to request the usage monitoring control. + +The SMF shall report the accumulated usage to the PCF in the following conditions: + +- when a usage threshold is reached, as described in this clause; +- when all PCC rules for which usage monitoring is enabled for a particular usage monitoring key are removed or deactivated, as specified in clause 4.2.4.10.2; +- when usage monitoring is explicitly disabled by the PCF, as specified in clause 4.2.6.5.3.2; +- when a PDU session is terminated, as specified in clause 4.2.5.3; +- when requested by the PCF, as specified in clause 4.2.6.5.3.3. + +The UPF measures the volume and/or the time of usage of all traffic of a PDU session or the corresponding service data flows. When the SMF receives the accumulated usage report from the UPF as defined in clauses 7.5.5.2, 7.5.7.2 or + +7.5.8.3 of 3GPP TS 29.244 [13], the SMF shall send an HTTP POST message as defined in clause 4.2.4.2, including one or more accumulated usage reports within the "accuUsageReports" attribute and the "US\_RE" value within the "repPolicyCtrlReqTriggers" attribute. Each AccuUsageReport data structure shall contain the accumulated usage report within one or two Usage Report information element, i.e. the accumulated usage before the monitoring time or the accumulated usage both before and after the monitoring time, corresponding to one usage monitoring control instance as requested by the PCF. + +If the monitoring time is provided by the PCF for a usage monitoring control instance and: + +- if the SMF receives only one Usage Report information elements corresponding to the usage monitoring control instance from the UPF, within the AccuUsageReport data structure, the SMF shall include the accumulated usage before the monitoring time within the "timeUsage" attribute, "volUsage" attribute, "volUsageUplink" attribute and/or "volUsageDownlink" attribute, if applicable; otherwise, +- if the SMF receives two Usage Report information elements corresponding to the usage monitoring control instance from the UPF, within the AccuUsageReport data structure, the SMF includes the accumulated usage before the monitoring time within the "timeUsage" attribute, "volUsage" attribute, "volUsageUplink" attribute and/or "volUsageDownlink" attribute, if applicable, and the accumulated usage after the monitoring time within the "nextTimeUsage" attribute, "nextVolUsage" attribute, "nextVolUsageUplink" attribute and/or "nextVolUsageDownlink" attribute, if applicable. + +When the PCF receives the accumulated usage report in the HTTP POST message, the PCF shall indicate to the SMF if usage monitoring shall continue for this usage monitoring control instance as follows: + +- if the PCF wishes to continue monitoring for the usage monitoring control instance and: + - if monitoring shall continue for specific level(s), the PCF shall provide in the response to the received HTTP POST message the new threshold(s) corresponding to these level(s) using the same attributes as before (i.e. "volumeThreshold", "volumeThresholdUplink", "volumeThresholdDownlink" and/or "timeThreshold"; "nextVolThreshold", "nextVolThresholdUplink", "nextVolThresholdDownlink", and/or "nextTimeThreshold" if the "monitoringTime" attribute is provided within an entry of the "umDecs" attribute); or + - if the PCF wishes to stop monitoring for specific level(s) the PCF shall not include in the response to the received HTTP POST message updated threshold(s) for these specific level(s), i.e. the corresponding "volumeThreshold" attribute, "volumeThresholdUplink" attribute, "volumeThresholdDownlink" attribute, "timeThreshold" attribute, "nextVolThreshold" attribute, "nextVolThresholdUplink" attribute, "nextVolThresholdDownlink" attribute, and/or "nextTimeThreshold" attribute shall not be included within an entry of the "umDecs" attribute. + - otherwise, if the PCF wishes to stop monitoring for the usage monitoring control instance, the PCF shall not include any thresholds of this usage monitoring control instance in the response to the HTTP POST message or remove the reference to the usage monitoring control instance from the concerned dynamic PCC rule or session rule. + +If both volume and time thresholds were provided by the PCF and only one of these two thresholds is reached, the SMF shall report this event to the PCF and the accumulated usage since last report shall be reported for both measurements. + +Upon reception of the reported usage from the SMF, the PCF shall deduct the value of the usage report from the total allowed usage for that PDU session, usage monitoring key, or both as applicable, and the PCF may also derive and update the PCC rules based on the remaining allowed usage or reported usage and provision them to the SMF. If the remaining allowed usage reaches a value zero (or below zero), the PCF may apply other policy decisions and interact with the SMF accordingly. + +NOTE: The PCF can also update the related usage monitoring information in the UDR as defined in 3GPP TS 29.519 [15] according to the received usage report(s). + +#### 4.2.4.10.2 PCC Rule Removal + +When the PCF removes or deactivates the last PCC rule associated with a usage monitoring key in an Npcf\_SMPolicyControl\_UpdateNotify request as described in clause 4.2.3.2 or in an Npcf\_SMPolicyControl\_Update response as described in clause 4.2.3.4 whose request was not related to reporting usage for the same monitoring key, the SMF shall send a new Npcf\_SMPolicyControl\_Update request including the "US\_RE" value within the "repPolicyCtrlReqTriggers" attribute and one or more accumulated usage reports within the "accuUsageReports" + +attribute within the SmPolicyUpdateContextData data type of the HTTP POST request using the procedures to report accumulated usage defined in clause 4.2.4.10. + +When the SMF reports that the last PCC rule associated with a usage monitoring key is inactive, the SMF shall report the accumulated usage for that monitoring key within the same HTTP POST request if the "ruleReports" attribute was included in the SmPolicyUpdateContextData data type; otherwise, if the "ruleReports" attribute was included in the HTTP POST response of an Npcf\_SMPolicyControl\_UpdateNotify request, the SMF shall invoke the Npcf\_SMPolicyControl\_Update service operation by sending a new HTTP POST request to report accumulated usage for the usage monitoring key. + +#### 4.2.4.11 Ipv6 Multi-homing support + +The SMF may insert an additional PDU Session Anchor to an existing PDU session by using Ipv6 multi-homing mechanism. In this case, the SMF shall inform the PCF when one or more new Ipv6 prefix is allocated to the new PDU Session Anchor as defined in clause 4.2.4.2. The SMF shall, within the SmPolicyUpdateContextData data structure, include the "UE\_IP\_CH" within the "repPolicyCtrlReqTriggers" attribute and include the new Ipv6 prefix within the "ipv6AddressPrefix" attribute, and may include an additional new Ipv6 prefix within the "addIpv6AddrPrefixes" attribute, if the "MultiIpv6AddrPrefix" feature is supported, or multiple new Ipv6 prefixes within the "multiIpv6Prefixes" attribute, if the "UnlimitedMultiIpv6Prefix" feature is supported. + +When the PCF receives the request from the SMF indicating the addition of one or more new Ipv6 prefixes, the PCF shall determine the impacted PCC rules and/or session rules associated with each new Ipv6 prefix and provision them to the SMF as defined in clauses 5.6.2.6 and 5.6.2.7. The SMF shall derive the appropriate policies based on the policies provisioned by the PCF and provision them to the appropriate UPF, if applicable, access network, if applicable, and UE, if applicable. The PCF shall additionally consider the new Ipv6 prefix, or the new Ipv6 prefixes if the "MultiIpv6AddrPrefix" feature is supported or the "UnlimitedMultiIpv6Prefix" feature, during subsequent PCC rules and/or session rules updates. + +When the SMF removes a PDU Session anchor from the Multi-homing PDU session, the SMF shall inform the PCF of the released Ipv6 prefix related to the PDU Session anchor as defined in clause 4.2.5.2. The SMF shall, within the SmPolicyUpdateContextData data structure, include the "UE\_IP\_CH" within the "repPolicyCtrlReqTriggers" attribute and include the released Ipv6 prefix within the "relIpv6AddressPrefix" attribute, and may include an additional released UE Ipv6 prefixes within the "addRelIpv6AddrPrefixes" attribute, if the "MultiIpv6AddrPrefix" feature is supported, or multiple released UE Ipv6 prefixes within the "multiRelIpv6Prefixes" attribute, if the "UnlimitedMultiIpv6Prefix" feature is supported. + +When the PCF receives the request from the SMF indicating the release of one or more Ipv6 prefixes, the PCF shall determine the previously provisioned PCC rules and/or session rules associated with each released Ipv6 prefix and shall remove and/or update them from the SMF as applicable. The PCF shall remove the released Ipv6 prefix, or the multiple released Ipv6 prefixes if the "MultiIpv6AddrPrefix" or the "UnlimitedMultiIpv6Prefix" feature is supported. + +#### 4.2.4.12 Request and report for the result of PCC rule removal + +If the RAN-NAS-Cause feature is supported, the PCF may request the SMF to inform it of the result of the PCC rule removal when the PCF removes the PCC rule as defined in clause 4.2.6.5.2. + +When the SMF receives the request, the SMF shall maintain locally the removed PCC rules until it receives of the resource release outcome from the network. + +The SMF shall notify the PCF by include the "RES\_RELEASE" within the "repPolicyCtrlReqTriggers" attribute and the affected rules indicated within one instance of the "ruleReports" attribute with the "ruleStatus" attribute set to the value INACTIVE. + +If the QoS flow is terminated as a consequence of the removal of one or more PCC rules, the SMF shall inform the PCF about the completion of the QoS flow procedure related to the removal of PCC rules that indicated resource release notification by including the RequestedRuleData instance containing the "reqData" attribute with the RES\_RELEASE referring to the PCC rule. If the SMF received from the access network some RAN/NAS release cause(s), the SMF shall also provide the received cause(s) in the "ruleReports" attribute. The SMF shall also provide the available access network information within the "userLocationInfo" attribute (if available), "userLocationInfoTime" attribute (if available) and "ueTimezone" attribute (if available). + +#### 4.2.4.13 Access Network Charging Identifier request and report + +If the "policyCtrlReqTriggers" attribute with the value "AN\_CH\_COR" has been provided to the SMF, the SMF shall notify to the PCF the Access Network Charging Identifier that the SMF has assigned to the PDU session for the dynamic PCC Rules which referred from the RequestedRuleData data structure containing the CH\_ID within the "reqData" attribute by including an "accNetChIds" attribute within the SmPolicyUpdateContextData data structure in the HTTP POST message. + +If the the Access Network Charging Identifier is within the Uint32 value range; the SMF shall include one AccNetChId instance within the "accNetChIds" attribute and include the Access Network Charging Identifier within the "accNetChIdValue" attribute and the "sessionChScope" attribute set to true; otherwise, if the "AccNetChargId\_String" feature is supported by the SMF and the PCF, and the Access Network Charging Identifier value is longer than Uint32, the SMF shall include one AccNetChId instance within the "accNetChIds" attribute and the Access Network Charging Identifier within the "accNetChargIdString" attribute and the "sessionChScope" attribute set to true. + +NOTE: As specified in 3GPP TS 32.255 [35] clause 5.1.4, the SMF assigns a charging identifier per PDU session and is used through the PDU session's lifetime. The request of Access Network Charging Identifier(s) in 5GS and EPS interworking scenarios is described in clause B.3.4.11. + +When the PCF does not have the access network charging identifier information for the PDU session, the PCF may request the SMF to provide the Access Network Charging Identifier associated to the new dynamic PCC rules as defined in clause 4.2.6.5.1 in the response message. + +#### 4.2.4.14 Request and report for the successful resource allocation notification + +The PCF may request the SMF to confirm that the resources associated to a PCC rule are successfully allocated as defined in clause 4.2.6.5.5. + +If the "policyCtrlReqTriggers" attribute with the value "SUCC\_RES\_ALLO" has been provided to the SMF, the SMF shall notify to the PCF that the resources associated to the PCC rules which were referred from an element of the "lastReqRuleData" attribute containing the "SUCC\_RES\_ALLO" within the "reqData" attribute are successfully allocated. When the SMF received successful resource allocation response from the access network, the SMF shall within the SmPolicyUpdateContextData data structure include the "SUCC\_RES\_ALLO" within the "repPolicyCtrlReqTriggers" attribute and "ruleReports" attribute. Within the RuleReport instance, the SMF shall include the corresponding PCC rule identifier(s) within the "pccRuleIds" attribute and the "ruleStatus" attribute set to value "ACTIVE". + +If the "AuthorizationWithRequiredQoS" feature as defined in clause 5.8 is supported and if the SMF additionally receives the reference to the matching Alternative QoS Profile which the NG-RAN can guarantee, the SMF shall also include the reference to the QosData data structure for the Alternative QoS parameter set corresponding to the reference to the matching alternative QoS profile within the "altQosParamId" attribute. + +If the "RuleVersioning" feature is supported and the PCF included the "contVer" attribute for a specific PCC rule instance, and the resource allocation was successful for this PCC rule, the SMF shall include the rule content version within the "contVers" attribute in the corresponding RuleReport instance. + +#### 4.2.4.15 PCC Rule Error Report + +If the installation/activation of one or more PCC rules fails using the procedure as defined in clause 4.2.2.1 or 4.2.4.1 or the PCF installed, activated or modified one or more PCC rules as defined in clause 4.2.3.1 but resource allocation for the PCC rule was unsuccessful or the UE was found temporarily unavailable, the SMF shall include the "ruleReports" attribute for the affected PCC rules to report the failure within the SmPolicyUpdateContextData data structure. Within each RuleReport instance, the SMF shall identify the failed PCC rule(s) by including the affected PCC rules within the "pccRuleIds" attribute, identify the failed reason code by including a "failureCode" attribute, and shall include rule status within the "ruleStatus" attribute with the value as described below. + +If the installation/activation of one or more new PCC rules (i.e., rules which were not previously successfully installed) fails, the SMF shall set the "ruleStatus" to INACTIVE. + +The removal of a PCC rule shall not fail, even if the PDU session procedures with the UE fail. The SMF shall retain information on the removal and conduct the necessary PDU session procedures with the UE when it is possible. + +If the modification of a currently active PCC rule fails, the SMF shall retain the existing PCC rule as active without any modification unless the reason for the failure has an impact also on the existing PCC rule. The SMF shall report the modification failure to the PCF. + +If a PCC rule was successfully installed/activated, but can no longer be enforced by the SMF, the SMF shall set the "ruleStatus" attribute to INACTIVE. + +NOTE: When the PCF receives "ruleStatus" set to INACTIVE, the PCF does not need request the SMF to remove the inactive PCC rule. + +Depending on the value of the "failureCode" attribute, the PCF may decide whether retaining of the old PCC rule, re-installation, modification, removal of the PCC rule or any other action applies. + +If the feature "UEUnreachable" is supported, when the "failureCode" indicates "UE\_TEMPORARILY\_UNAVAILABLE" and the "retryTimer" is received, the PCF should not reattempt the installation, re-installation or modification of PCC rules until the received retry timer expires. + +If the RAN-NAS-Cause feature is supported and as part of any of the procedures described in this clause the SMF receives from the access network some RAN/NAS release cause(s), the SMF shall also provide the received cause(s) in the RuleReport instance. If RAN-NAS-Cause feature is supported the SMF shall provide the available access network information within the "userLocationInfo" attribute (if available), "userLocationInfoTime" attribute (if available) and "ueTimezone" attribute (if available). + +If the "RuleVersioning" feature is supported and the PCF included the "contVer" attribute for a specific PCC rule instance, and the resource allocation was unsuccessful as for any of the procedures described in this clause the SMF shall include the rule content version within the "contVers" attribute for the corresponding RuleReport instance. + +#### 4.2.4.16 Presence Reporting Area Information Report + +If the PRA or ePRA feature as defined in clause 5.8 is supported and when the SMF receives the presence reporting area information from the serving node as defined in 3GPP TS 29.518 [36] indicating that the UE is inside or outside of one or more presence reporting areas or any of the presence reporting areas is set to inactive, the SMF shall check if the reported presence reporting area identifier corresponds to a presence reporting area that is relevant for the PCF. In that case, the SMF shall within the SmPolicyUpdateContextData data structure include the "PRA\_CH" within the "repPolicyCtrlReqTriggers" attribute and one or more Presence Reporting Area Information Report within the "repPraInfos" attribute. For each PresenceInfo data structure, the SMF shall also include the presence reporting area status within the "presenceState" attribute and the presence reporting area identifier within the "praId" attribute for each of the presence reporting areas reported by the serving node. + +If the SMF receives presence reporting area information for a Set of Core Network predefined Presence Reporting Area encoded within the "praId" attribute together with the individual PRA Identifier encoded within the "additionalPraId" attribute as described in 3GPP TS 29.518 [36], the SMF shall only provide the PCF with the presence reporting area information corresponding to the additional PRA information (i.e. the individual PRA identifier) encoded within the "praId" attribute. + +NOTE 1: The SMF will receive additional presence reporting area information when the UE enters or leaves one or more presence reporting areas related to a PRA set. In that case, the additional presence reporting area information corresponds to the actual individual presence reporting area. The received presence reporting area identifier corresponds to the PRA set id and is used to identify the requester (PCF or CHF) of the notification information. + +NOTE 2: The PCF can acquire the necessary data for presence reporting from the UDR. + +NOTE 3: Homogeneous support of Presence Area reporting in a network is assumed. + +NOTE 4: The serving node can activate the reporting for the PRAs which are inactive as described in the 3GPP TS 23.501 [2]. + +#### 4.2.4.17 UE initiates a resource modification support + +In the case that the UE initiates a resource modification procedure as defined in clause 6.4.2.2 of 3GPP TS 24.501 [20], the SMF shall within the SmPolicyUpdateContextData data structure include the "RES\_MO\_RE" within the "repPolicyCtrlReqTriggers" attribute and shall include the UE request of specific QoS + +handling for selected SDF within the "ueInitResReq" attribute. Within the UeInitiatedResourceRequest data structure, the SMF shall include the "ruleOp" attribute, "packFiltInfo" attribute and "reqQos" attribute if applicable as follows: + +- When the UE requests to "Create new QoS rule", the SMF shall include the "ruleOp" attribute set to "CREATE\_PCC\_RULE", the "packFiltInfo" attribute and "reqQos" attribute containing the requested QoS for the new PCC rule. Each PacketFilterInfo instance shall contain one packet filters requested for creating the new QoS rule. If the PCF authorizes the request, the PCF shall create a new PCC rule by including the new packet filters within the service data flow template of the PCC rule. When the SMF received the PCC rule, the SMF shall derive the QoS rule based on the PCC rule, assign a new QoS rule identifier within the PDU session for the QoS rule. The SMF shall keep the mapping between the PCC rule identifier and the QoS rule identifier. +- When the UE requests to "Modify existing QoS rule and add packet filters" for the QoS rule created as a result of the UE-initiated resource modification, SMF shall include the "ruleOp" attribute set to "MODIFY\_PCC\_RULE\_AND\_ADD\_PACKET\_FILTERS", the "pccRuleId" attribute including the PCC rule identifier corresponding the QoS rule identifier and the "packFiltInfo" attribute. Each PacketFilterInfo instance shall contain one packet filters requested for addition to this QoS Rule. If the UE request includes the modified QoS information the SMF shall also include the "reqQos" attribute to indicate the updated QoS for the affected PCC rule(s). If the PCF authorizes the request, the PCF shall update the PCC rule by adding the new packet filters to the service data flow template of the PCC rule. +- When the UE requests to "Modify existing QoS rule and replace all packet filters" for the QoS rule created as a result of the UE-initiated resource modification, SMF shall include the "ruleOp" attribute set to "MODIFY\_PCC\_RULE\_AND\_REPLACE\_PACKET\_FILTERS", the "pccRuleId" attribute including the PCC rule identifier corresponding the QoS rule identifier and the "packFiltInfo" attribute. Each PacketFilterInfo instance shall contain one packet filters requested for addition to this QoS Rule. If the UE request includes the modified QoS information the SMF shall also include the "reqQos" attribute to indicate the updated QoS for the affected PCC rule. If the PCF authorizes the request, the PCF shall update PCC rule by replacing the all existing packet filters within the service data flow template of the PCC rule with the new packet filter(s). +- When the UE requests to "Modify existing QoS rule and delete packet filters" for the QoS rule created as a result of the UE-initiated resource modification, SMF shall include the "ruleOp" attribute set to "MODIFY\_PCC\_RULE\_AND\_DELETE\_PACKET\_FILTERS", the "pccRuleId" attribute including the PCC rule identifier corresponding the QoS rule identifier and the "packFiltInfo" attribute. Each PacketFilterInfo instance shall within the "packFiltId" attribute include the removed packet filter identifier assigned by the PCF corresponding to the packet filter identifier received from the UE. If the UE request includes modified QoS information the SMF shall also include the "reqQos" attribute to indicate the updated QoS for the affected PCC rule(s). If the PCF authorizes the request, the PCF shall update PCC rule by removing the corresponding packet filters from the service data flow template of the PCC rule. +- When the UE requests to "Modify existing QoS rule without modifying packet filters" for the QoS rule created as a result of the UE-initiated resource modification, SMF shall include the "ruleOp" attribute set to "MODIFY\_PCC\_RULE\_WITHOUT\_MODIFY\_PACKET\_FILTERS", the "pccRuleId" attribute including the PCC rule identifier corresponding the QoS rule identifier, the "packFiltInfo" attribute and the modified QoS information within the "reqQos" attribute. The "packFiltInfo" attribute shall include one PacketFilterInfo instance which includes any packet filter identifier assigned by the PCF for the PCC rule within the "packFiltId" attribute. +- When the UE requests to "Delete existing QoS rule" the SMF shall include the "ruleOp" attribute set to "DELETE\_PCC\_RULE" for the QoS rule created as a result of the UE-initiated resource modification, the "pccRuleId" attribute including the PCC rule identifier corresponding the QoS rule identifier and the "packFiltInfo" attribute. The "packFiltInfo" attribute shall include one PacketFilterInfo instance which includes any packet filter identifier assigned by the PCF for the PCC rule within the "packFiltId" attribute. The PCF shall remove the PCC rule when the PCF receives the request according to the PCC rule identifier. + +NOTE 1: The UE can only modify or delete the packet filters that the UE has introduced and associated resources. The packet filter identifiers contained in the FlowInformation data structure are only used for packet filters created by the UE. + +The SMF shall calculate the requested GBR, for a GBR 5QI, as the sum of the previously authorized GBR for the affected PCC rule, corresponding to the QoS rule, adjusted with the difference between the requested GBR for the QoS flow and previously negotiated GBR for the QoS flow. For the UE request to create a new QoS Rule, the GBR as requested by the UE for the QoS rule shall be used. + +If the request covers all the PCC rules with a QoS flow binding to the same QoS flow, then the SMF may request a change to the 5QI for existing PCC rules. + +For the purpose of creating or modifying a QoS rule with adding, replacing and modifying packet filter, within the UeInitiatedResourceRequest instance, the SMF shall include the precedence information of the QoS rule within the "precedence" attribute, and within each PacketFilterInfo instance, the SMF shall include the "packFiltCont" attribute, "tosTrafficClass" attribute, "spi" attribute, "flowLabel" attribute and "flowDirection" attribute set to the value(s) describing the packet filter provided by the UE. + +NOTE 2: The UE signalling with the network is governed by the applicable NAS signalling TS. The NAS 3GPP TS for a specific access may restrict the UE possibilities to make requests compared to what is stated above. + +Upon receipt of the request from the SMF, the PCF shall check the set of services the user is allowed to access. If the user is not allowed to access AF session based services, the PCF shall check whether the user is allowed to request resources for services not known to the PCF and whether the requested QoS and/or packet filters can be authorized. If the user is not allowed to request resources for services not known to the PCF, the PCF shall reject the request with in an HTTP "403 Forbidden" response message including the "cause" attribute of the ProblemDetails data structure set to "POLICY\_CONTEXT\_DENIED". + +If the PCF authorizes the request from the UE, the PCF shall construct a PCC rule(s) based on the UeInitiatedResourceRequest data structure. For the request to add the filter(s), the PCF shall within the FlowInformation data structure include the assigned packet filter identifier within the "packFiltId" attribute. When the SMF derives the QoS based on the PCC rule, the SMF shall assign a new packet filter identifier for each added packet filter within the QoS rule and keep the mapping between the packet filter identifier for the packet filter within the PCC rule and QoS rule. + +The PCF shall perform the QoS authorization for the new created or modified PCC rules if requested by the UE as defined in clause 4.2.6.6.2. + +If the PCF detects that the packet filters in the request for new PCC rules received from the SMF is covered by the packet filters of outstanding PCC rules that the PCF is provisioning to the SMF, the PCF may reject the request and indicate the cause for the rejection including the "cause" attribute of the ProblemDetails data structure set to "ERROR\_CONFLICTING\_REQUEST" in an HTTP "403 Forbidden" response message. If the SMF receives a response message with this code, the SMF shall ignore the PDU session modification that initiated the HTTP request as specified in 3GPP TS 24.501[20] clause 6.3.2.5. + +If the PCF does not accept one or more of the traffic mapping filters provided by the SMF in an HTTP Request (e.g. because the PCF does not allow the UE to request enhanced QoS for services not known to the PCF), the PCF shall reject the request and indicate the cause for the rejection including the "cause" attribute of the ProblemDetails data structure set to "ERROR\_TRAFFIC\_MAPPING\_INFO\_REJECTED" in an HTTP "403 Forbidden" response message. If the SMF receives an HTTP response with this code, the SMF shall reject the PDU session modification that initiated the HTTP request. + +The PCF shall not combine a rejection with provisioning of PCC rule operations in the same HTTP response. + +#### 4.2.4.18 Trace Control + +When there is the requirement to activate tracing the SMF may provide trace control parameters within the "traceReq" attribute to the PCF via the Npcf\_SMPolicyControl\_Update service operation. The update service operation may also indicate the update or deactivation of the trace session to the PCF. + +#### 4.2.4.19 Negotiation of the QoS flow for IMS signalling + +When UE initiates a resource modification request, if the SMF includes the "qosFlowUsage" attribute containing "IMS\_SIG" within SmPolicyUpdateContextData data structure and the PCF accepts that a QoS flow dedicated to IMS signalling shall be used, the PCF shall return the "qosFlowUsage" containing "IMS\_SIG" value within the SmPolicyDecision data structure. The provided PCC rules shall have the 5QI applicable for IMS signalling. + +#### 4.2.4.20 Notification about Service Data Flow QoS target enforcement + +When the SMF gets the knowledge that for one or more QoS Flows: + +- the GBR QoS targets cannot be guaranteed; or +- the GBR QoS targets can be guaranteed again; + +the SMF shall inform the PCF that the GBR QoS targets cannot be guaranteed or can be guaranteed again for the PCC rules bound to the QoS flows. + +The SMF gets the knowledge that the GBR QoS targets cannot be guaranteed or can be guaranteed again for the QoS flow(s) as follows: + +- upon receiving a notification from the NG-RAN that the GFBR can no longer be guaranteed or can be guaranteed again as defined clause 5.2.2.3.1 of 3GPP TS 29.502 [22]; or +- during a handover, a QoS Flow which is listed as transferred QoS Flow received from the AMF as defined clause 5.2.2.3.1 of 3GPP TS 29.502 [22] can be interpreted as a notification that GFBR can be guaranteed again if the SMF has received a notification from the source NG-RAN that the GFBR can no longer be guaranteed but does not receive an explicit notification that the GFBR can no longer be guaranteed for that QoS Flow from the Target NG-RAN within a configured time as previous bullet. + +The SMF shall send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure, including the "QOS\_NOTIF" within "repPolicyCtrlReqTriggers" attribute and the "qncReports" attribute. In each QosNotificationControlInfo data structure, the SMF shall include the indication that the GBR QoS targets cannot be guaranteed or the GBR QoS targets can be guaranteed again within the "notifType" attribute and affected PCC rule identifiers within the "refPccRuleIds" attribute. + +If the "AuthorizationWithRequiredQoS" feature as defined in clause 5.8 is supported, the SMF shall also include the reference to the QosData data structure for the Alternative QoS parameter set corresponding to the reference to the matching alternative QoS profile within the "altQosParamId" attribute if the SMF additionally receives the reference to the matching Alternative QoS Profile which the NG-RAN can guarantee when the NG-RAN indicates the GBR QoS targets cannot be guaranteed. When the SMF additionally receives an indication that lowest priority Alternative QoS Profile cannot be fulfilled from the NG-RAN the SMF shall omit the "altQosParamId" attribute to indicate that that the lowest priority alternative QoS profile could not be fulfilled either. When the "DisableUENotification" feature is supported, if the corresponding PCC rule does not include the "disUeNotif" attribute set to true, the SMF shall also send the fulfilled QoS profile or Alternative QoS Profile to the UE as defined in clause 5.2.2.3.1.1 of 3GPP TS 29.518 [36], if applicable. + +If the affected PCC rule was provisioned with a content version, the SMF shall include the "contVers" attribute defined in the QosNotificationControlInfo data structure for those corresponding PCC rules. The SMF may include more than one content version in the "contVers" attribute for the same PCC rule within the corresponding QosNotificationControlInfo instance included in the "qncReports" attribute (e.g. the SMF has combined multiple PCC rule versions enforcement into one QoS flow operation). + +When the "AuthorizationWithRequiredQoS" and the "AltQoSProfilesSupportReport" features as defined in clause 5.8 are supported, and the PCF included during PCC rule provisioning the "refAltQosParams" attribute for the concerned PCC rule(s), if the SMF: + +- receives the indication that the GBR QoS targets cannot be guaranteed, as specified in 3GPP TS 38.413 [54]; and +- does not receive a matching Alternative QoS Profile the NG-RAN can guarantee or the indication that the lowest priority Alternative QoS profile cannot be fulfilled, as specified in 3GPP TS 38.413 [54]; + +then the SMF may determine that Alternative QoS Profiles are not supported by the NG-RAN where the UE is currently located and include within the QosNotificationControlInfo data structure the "altQosNotSuppInd" attribute set to true. When Alternative QoS profiles are supported by the NG-RAN where the UE is currently located, the SMF may omit the "altQosNotSuppInd" attribute or set it to false. + +When the PCF receives the HTTP POST request, it shall acknowledge the request by sending a "200 OK" response to the SMF and then notify the AF as defined in 3GPP TS 29.514 [17], clause 4.2.5.4. + +#### 4.2.4.21 Session Rule Error Report + +If the "SessionRuleErrorHandler" feature is supported and if the installation of one or more session rules fails using the procedure as defined in clauses 4.2.2.1 or 4.2.4.1 or the PCF provisioned one or more session rules as defined in clause 4.2.3.1 but enforcement of the session Rule was unsuccessful (e.g. session-AMBR is rejected by the AMF in the roaming scenario, and the SMF determines that the PDU session is kept, the SMF shall include the "sessRuleReports" attribute for the affected session rules to report the failure within the SmPolicyUpdateContextData data structure. Within each SessionRuleReport instance, the SMF shall identify the failed session rule(s) by including the affected session rules within the "ruleIds" attribute, identify the failed reason code by including a "sessRuleFailureCode" attribute, and shall include rule status within the "ruleStatus" attribute with the value as described below. + +If the installation of one or more new session rules fails, the SMF shall set the "ruleStatus" to INACTIVE. + +The removal of a session rule shall not fail, even if the PDU session procedures with the UE fail. The SMF shall retain information on the removal and conduct the necessary PDU session procedures with the UE when it is possible. + +If the modification of a currently provisioned session rule fails, the SMF shall retain the existing session rule as provisioned without any modification unless the reason for the failure has an impact also on the existing session rule. The SMF shall report the modification failure to the PCF. + +If a session rule was successfully installed, but can no longer be enforced by the SMF: + +- If the "ImmediateTermination" feature is supported, and based on operator's policy, the SMF shall evaluate whether the PDU session can be kept. If the SMF determines to terminate the PDU session immediately, the SMF shall trigger the deletion of the SM Policy Association as described in clauses 4.2.5, otherwise the SMF shall set the "ruleStatus" attribute to INACTIVE. +- If the the "ImmediateTermination" feature is not supported, the SMF shall set the "ruleStatus" attribute to INACTIVE. + +NOTE: When the PCF receives "ruleStatus" set to INACTIVE, the PCF does not need to request the SMF to remove the inactive session rule. + +Depending on the value of the "sessRuleFailureCode" attribute, the PCF may decide whether retaining the old session rule, re-installation, modification, removal of the session rule or any other action applies. + +#### 4.2.4.22 Request the termination of SM Policy association + +If "RespBasedSessionRel" feature is supported, PCF may request the PDU session termination upon receiving a POST message from the SMF (e.g. when usage quota reached). In this case, the PCF shall include the "relCause" attribute within the SmPolicyDecision data structure of the response to the POST message. + +After the receipt of a successful HTTP POST response from the PCF containing the "relCause" attribute within the SmPolicyDecision data structure, the SMF shall invoke the Npcf\_SMPolicyControl\_Delete Service Operation defined in clause 4.2.5 to terminate the policy association and initiate the procedure to terminate the PDU session as defined in 3GPP TS 29.502 [22]. + +#### 4.2.4.23 Reporting of TSC user plane node management information and port management information + +If the feature "TimeSensitiveNetworking" or "TimeSensitiveCommunication" is supported and the "TSN\_BRIDGE\_INFO" policy control request trigger is provisioned in the SMF, when new TSC user plane node information is available for TSC or Deterministic Networking PDU sessions, the SMF requests to update the SM Policy Association and provides to the PCF information on the conditions that have been met. + +The Policy Control Request Trigger condition "TSN\_BRIDGE\_INFO" is met when: + +- a. the SMF detects new TSC user plane node port (the UE has indicated support of transferring Port Management Information Containers, or SMF local configuration for the given DNN, S-NSSAI indicates support for Deterministic Networking). The SMF shall send to the PCF, if available: + - the port number for the device side of the PDU session encoded in the "dsttPortNum" attribute allocated by the UPF; + +NOTE 1: The port number of the PDU session corresponds to the device side port of the 5GS bridge/router. When the device supports the DS-TT functionality, the port number represents the DS-TT port number corresponding to the given PDU Session. + +NOTE 2: Port number can refer either to Ethernet port or PTP port or a port of a DetNet router. In Ethernet type PDU Sessions, it is assumed that the PTP port number is the same as the associated Ethernet port number. + +- the TSC user plane node Id received from the UPF encoded in the "bridgeId" attribute; +- when DS-TT functionality is used: + - a. the MAC address of the DS-TT port received from the UE encoded in the "dsttAddr" attribute, if received; and + - b. the UE-DS-TT residence time if received from the UE encoded in the "dsttResidTime" attribute, +- in case of Deterministic Networking, for the device side port, and when the feature "MTU\_Size" is supported, the MTU size (as specified in IETF RFC 8344 [56]) for IPv4 and/or IPv6 encoded in the "mtuIpv4" and/or "mtuIpv6" attributes respectively, + +within the SmPolicyUpdateContextData structure encoded in the "tsnBridgeInfo" attribute of the TsnBridgeInfo data type; and/or + +- b. the SMF receives a UMIC from the TSC user plane node functionality of the UPF/NW-TT and/or, when the DS-TT or the NW-TT functions are used, the SMF receives a PMIC from the DS-TT port and/or one or more PMIC(s) in the corresponding one or more NW-TT ports. The SMF shall transparently forward to the PCF the UMIC encoded within the "tsnBridgeManCont" attribute and/or the DS-TT PMIC encoded within the "tsnPortManContDstt" attribute and/or the one or more NW-TT PMIC(s) encoded within the "tsnPortManContNwtt" attribute within the SmPolicyUpdateContextData structure. + +NOTE 3: The 5GS Architecture to support IETF Deterministic Networking IETF RFC 8655 [55] does not require the DS-TT functionality to be supported in the device nor require the user plane NW-TT functionality to be supported in the UPF. For the reporting of information of network side ports, NW-TT control plane functionality is supported and PMIC(s) carry port management information of NW-TT port(s). + +For IP type of PDU sessions, the UE IP address of the PDU session received within the "ipv4Address" or "ipv6AddressPrefix" attribute, as described in clause 4.2.2.2 and 4.2.4.2 (reported with trigger "UE\_IP\_CH") is used as identifier of the PDU session related to the reported TSC user plane node information. + +For Ethernet type of PDU sessions (IEEE TSN and other time sensitive communications than TSN) the MAC address of the DS-TT port received within the "dsttAddr" attribute is used as identifier of the PDU session related to the reported TSC user plane node information. + +#### 4.2.4.24 Notification about Service Data Flow QoS Monitoring + +When the SMF gets the information about real-time measurements of QoS parameters for one or more SDFs from the UPF and the "QOS\_MONITORING" policy control request trigger was provisioned, then SMF shall inform the PCF for the impacted PCC rules + +When the QoS monitoring applies for packet delay, the SMF shall inform the PCF when it gets information about any of the following items for one or more SDFs from the UPF: + +- uplink packet delay(s); +- downlink packet delay(s); and/or +- round trip delay(s); or +- if the feature "PacketDelayFailureReport" is supported, indicator of packet delay measurement failure. + +When the "EnQoSMon" feature is supported and the QoS monitoring applies for congestion information, the SMF shall inform the PCF when it gets information about any of the following items for one or more SDFs from the UPF: + +- uplink congestion information; and/or + +- downlink congestion information; or +- indicator of congestion information measurement failure. + +When the feature "EnQoSMon" is supported, and QoS monitoring applies for data rate measurements, the SMF shall inform about any of the following items for one or more SDFs from the UPF: + +- uplink data rate; and/or +- downlink data rate. + +The SMF shall send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure, including the "QOS\_MONITORING" within "repPolicyCtrlReqTriggers" attribute and the "qosMonReports" attribute, and/or if the feature "XRM\_5G" is supported, and/or the "qosMonDatRateReps" attribute. In each QosMonitoringReport data structure, the PCF shall include: + +- affected PCC rule identifiers within the "refPccRuleIds" attribute; and + +if QoS monitoring is for packet delay, the PCF shall include within the "qosMonReports" attribute: + +- one or two uplink packet delays within the "ulDelays" attribute; and/or +- one or two downlink packet delays within the "dlDelays" attribute; and/or +- one or two round trip packet delays within the "rtDelays" attribute; and/or +- if the feature "PacketDelayFailureReport" is supported, the packet delay measurement failure indicator within "pdmf" attribute; or + +and/or, if the feature "EnQoSMon" is supported and QoS monitoring is for data rate measurements, the PCF shall include within the "qosMonDatRateReps" attribute: + +- one data rate measurement for the UL within the "ulDataRate" attribute; and/or +- one data rate measurement for the DL within the "dlDataRate" attribute. + +**Editor's note:** Whether the maximum and minimum Data Rate measurements calculated during the waiting time can be reported is FFS. + +and/or, if the feature "EnQoSMon" is supported and QoS monitoring for congestion measurement is enabled, the PCF may include within the "qosMonReports" attribute: + +- the uplink congestion information within the "ulCongInfo" attribute; +- the downlink congestion information within the "dlCongInfo" attribute; or +- the congestion information measurement failure indicator within "cimf" attribute. + +**Editor's Note:** It is FFS whether congestion information measurement failure can occur. + +#### 4.2.4.25 Access traffic steering, switching and splitting support + +If "ATSSS" feature defined in clause 5.8 is supported and the PCF has previously provisioned the AC\_TY\_CH policy control request trigger, when the UE requests to: + +- add an access to an already established MA PDU session (i.e. registers to another access), the SMF shall, within the SmPolicyUpdateContextData data structure, include the "AC\_TY\_CH" within the "repPolicyCtrlReqTriggers" attribute and include the additional Access type and the additional RAT type if available within the "addAccessInfo" attribute. +- release an access from an already established MA PDU session (i.e. deregisters from one access but remains registered on the other access), the SMF shall, within the SmPolicyUpdateContextData data structure, include the "AC\_TY\_CH" within the "repPolicyCtrlReqTriggers" attribute and include the released access type and the released RAT type if available within the "relAccessInfo" attribute. + +When the PCF receives the request from the SMF indicating the addition of Access Type or removal of Access Type, the PCF may provide PCC rules and/or session rules for the MA PDU session as defined in clause 4.2.6.2.17 and clause 4.2.6.3.4. + +#### 4.2.4.26 Policy decision error handling + +##### 4.2.4.26.1 Policy decision types and condition data error handling + +If the "PolicyDecisionErrorHandling" feature is supported and the "ExtPolicyDecisionErrorHandling" feature is not supported, and one or more policy decision types (as defined in clause 4.1.4.4) and/or condition data (as defined in clause 4.1.8) which are not referred by any PCC rules or session rule is provisioned using the procedure as defined in clauses 4.2.2.1, 4.2.3.1 or 4.2.4.1 but the storage was unsuccessful (e.g. the policy decision could not be successfully stored due to a limitation of resources at the SMF), or because there are semantical inconsistencies in the provided data, the SMF shall include the "policyDecFailureReports" attribute to indicate the type(s) of the failed policy decisions and/or condition data within the SmPolicyUpdateContextData data structure. When the PCF receives the above report, the PCF shall consider all the instances of the policy decisions and/or condition data which are not referred by any PCC rule and/or session stored at the SMF and indicated by the PolicyDecisionFailureCode data type are removed from the SMF. + +The removal of a policy decision type and/or condition data shall not fail. + +##### 4.2.4.26.2 Policy decision types, condition data and other policy decisions error handling + +If the "ExtPolicyDecisionErrorHandling" feature is supported and one or more policy decision types (as defined in clause 4.1.4.4) and/or condition data (as defined in clause 4.1.8) which are not referred by any PCC rules or session rules is provisioned using the procedure as defined in clauses 4.2.2.1, 4.2.3.1 or 4.2.4.1, and/or other SM policy decisions (e.g. the SMF receives policy control request triggers and applicable additional information) but the SMF detects the received policy decision cannot be enforced (e.g. because semantical inconsistencies in the provided data), and the SMF determines that the PDU session can be kept, the SMF shall within the SmPolicyUpdateContextData data structure include the "policyDecFailureReports" attribute to indicate a failure in the provided policy decision types and/or condition data not referred by any PCC rules or session rules and/or in other SM policy decisions, and may include the "invalidPolicyDecs" attribute to indicate the failed policy decision types and/or condition data not referred by any PCC rules or session rules and/or other SM policy decisions. + +When the PCF receives the above report, the PCF shall consider: + +- all the instances of the policy decisions and/or condition data which are not referred by any PCC rule and/or session stored at the SMF and indicated by the PolicyDecisionFailureCode data type are removed from the SMF; and +- for the other policy decisions: + - a. All the new failed policy decisions provisioned are not installed in the SMF. + - b. All the modified policy decisions shall remain unmodified in the SMF. + - c. All the removed policy decisions provided in the request message are deleted in the SMF. + +NOTE: The removal of a policy decision does not fail. Even if there is an inconsistency e.g. between the deletion of a policy control request trigger and the deletion of the applicable additional information, the whole related policy decision is removed. + +#### 4.2.4.27 Policy Control for DDN Events + +If the feature "DDNEventPolicyControl" or "DDNEventPolicyControl2" is supported, and if the PCF has previously provisioned "DDN\_FAILURE" policy control request trigger, the SMF shall send the PCC rule request when it receives an event subscription for DDN Failure event including the traffic descriptors. The SMF shall send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure, including the "DDN\_FAILURE" within "repPolicyCtrlReqTriggers" attribute and include one or more traffic descriptor(s) in the "trafficDescriptors" attribute within the SmPolicyUpdateContextData structure for policy evaluation. Upon reception of the HTTP POST message: + +- if the PCF determines that there is an existing PCC rule for the traffic detection of DDD Status event which has the same traffic descriptor(s) as the new request one, the PCF shall update the existing PCC rule for traffic detection of DDD Status event by including both the "DDN\_FAILURE" and "DDD\_STATUS" values within the "notifCtrlInds" attribute of the "ddNotifCtrl" attribute if the "DDNEventPolicyControl" feature is supported or of the "ddNotifCtrl2" attribute if the "DDNEventPolicyControl2" feature is supported to indicate both the DDN Failure and DDD Status event detection; +- if the PCF determines that there is an existing PCC rule for the policy and charging control which has the same traffic descriptor(s) as the new request one, the PCF shall update the existing PCC rule by including the downlink data notification control information within the "ddNotifCtrl" attribute if the "DDNEventPolicyControl" feature is supported or within the "ddNotifCtrl2" attribute if the "DDNEventPolicyControl2" feature is supported to indicate the DDN Failure event detection. Within the DownlinkDataNotificationControl or DownlinkDataNotificationControlRm data type, the PCF shall include the "DDN\_FAILURE" value within the "notifCtrlInds" attribute; +- otherwise the PCF shall make a new PCC rule by including the reported traffic descriptors within the "flowInfos" attribute, setting a lower value to the "precedence" attribute and including the downlink data notification control information within the "ddNotifCtrl" attribute if the "DDNEventPolicyControl" feature is supported or within the "ddNotifCtrl2" attribute if the "DDNEventPolicyControl2" feature is supported and setting the other PCC rule information to the same values as in an existing PCC rule that previously matched the traffic. Within the DownlinkDataNotificationControl or DownlinkDataNotificationControlRm data type, the PCF shall include the "DDN\_FAILURE" value within the "notifCtrlInds" attribute to indicate the DDN Failure event detection. When the new PCC rule has to be bound to the default QoS flow, the PCF shall include the "defQosFlowIndication" attribute set to true within the QosData data structure to which the PCC rule refers. From now on, the PCF needs to keep new PCC rule for event detection fully synchronized with the existing PCC rule that previously matched the traffic for all other policy and charging control settings to ensure the same user experience and traffic treatment according to the operator policy. + +If the feature "DDNEventPolicyControl" or the "DDNEventPolicyControl2" is supported, and if the PCF has previously provisioned "DDN\_DELIVERY\_STATUS" policy control request trigger, the SMF shall send the PCC rule request when it receives an event subscription for DDD Status event including the traffic descriptors. The SMF shall send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure, including the "DDN\_DELIVERY\_STATUS" within "repPolicyCtrlReqTriggers" attribute, include one or more traffic descriptor(s) in the "trafficDescriptors" attribute and the type(s) of notification in the "typesOfNotif" attribute within the SmPolicyUpdateContextData structure for policy evaluation. Upon reception of the HTTP POST message: + +- if the PCF determines that there is an existing PCC rule for traffic detection of DDN Failure event which has the same traffic descriptor(s) as the new request one, the PCF shall update the existing PCC rule for traffic detection of DDN Failure event by including both the "DDN\_FAILURE" and "DDD\_STATUS" values within the "notifCtrlInds" attribute and the type(s) of notifications within the "typesOfNotif" attribute of the "ddNotifCtrl" attribute if the "DDNEventPolicyControl" feature is supported or of the "ddNotifCtrl2" attribute if the "DDNEventPolicyControl2" feature is supported to indicate both the DDN Failure and DDD Status event detection; +- if the PCF determines that there is an existing PCC rule for the policy and charging control which has the same traffic descriptor(s) as the new request one, the PCF shall update the existing PCC rule by including the downlink data notification control information within the "ddNotifCtrl" attribute if the "DDNEventPolicyControl" feature is supported or within the "ddNotifCtrl2" attribute if the "DDNEventPolicyControl2" feature is supported to indicate the DDD Status event detection. Within the DownlinkDataNotificationControl or DownlinkDataNotificationControlRm data type, the PCF shall include the "DDD\_STATUS" value within the "notifCtrlInds" attribute and the type(s) of notifications within the "typesOfNotif" attribute;otherwise the PCF shall make a PCC rule by including the reported traffic descriptors within the "flowInfos" attribute, setting a lower value to the "precedence" attribute and including the downlink data notification control information within the "ddNotifCtrl" attribute if the "DDNEventPolicyControl" feature is supported or within the "ddNotifCtrl2" attribute if the "DDNEventPolicyControl2" feature is supported to indicate the DDD Status event detection and setting the other PCC rule information to the same values as in an existing PCC rule that previously matched the traffic. Within the DownlinkDataNotificationControl or DownlinkDataNotificationControlRm data type, the PCF shall include the "DDD\_STATUS" value within the "notifCtrlInds" attribute and the type(s) of notifications within the "typesOfNotif" attribute to indicate that DDN Status event detection is required. When the new PCC rule has to be bound to the default QoS flow, the PCF shall include the "defQosFlowIndication" attribute set to true within the QosData data structure to which the PCC rule refers. From now on, the PCF needs to keep new PCC rule for event detection fully synchronized with + +the existing PCC rule that previously matched the traffic for all other policy and charging control settings to ensure the same user experience and traffic treatment according to the operator policy. + +If the feature "DDNEventPolicyControl2" is supported, when the SMF receives a request to cancel a subscription of the DDN Failure or DDD status event and if the PCF has previously provisioned "DDN\_FAILURE\_CANCELLATION" and "DDN\_DELIVERY\_STATUS\_CANCELLATION" policy control request trigger, the SMF shall send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure, including the "DDN\_FAILURE\_CANCELLATION" or "DDN\_DELIVERY\_STATUS\_CANCELLATION" within "repPolicyCtrlReqTriggers" attribute respectively and include the rule identifier of the PCC rule which is used for traffic detection of event within the "pccRuleId" attribute. Upon reception of the HTTP POST message: + +- If the PCC rule corresponding to the received PCC rule identifier is only used for the traffic detection of DDN failure or DDD Status respectively, the PCF shall remove the PCC rule locally and request the SMF to remove it too. +- If the PCC rule corresponding to the received PCC identifier is used for the traffic detection of both DDN failure and DDD status events, the PCF shall update the PCC rule by removing the downlink data notification control information for DDN failure or DDD status respectively from the PCC rule. In order to do that, within the DownlinkDataNotificationControlRm data type of the "ddNotifCtrl2" attribute, the PCF shall omit the "DDN\_FAILURE" or "DDD\_STATUS" within the "notifCtrlInds" attribute respectively. If the data notification control information for the DDD status is omitted, the PCF shall also include the "typesOfNotif" attribute set to NULL. +- If the PCC rule corresponding to the received PCC rule identifier is also used for the policy and charging control to the service data flow besides the traffic detection of the DDN failure or DDD status event, the PCF shall update the PCC rule by removing the downlink data notification control information from the PCC rule. In order to do that, the PCF shall include the "ddNotifCtrl2" attribute set to NULL. + +NOTE: The "ddNotifCtrl1" attribute is used to contain the downlink data notification control information if the "DDNEventPolicyControl" feature is supported; while the "ddNotifCtrl2" attribute is used to contain the downlink data notification control information if the "DDNEventPolicyControl2" feature is supported. + +When the SMF receives the new or updated PCC rule within the response message from the PCF, SMF shall perform the DDD Status and/or DDN Failure event based on the downlink data notification control information within the PCC rule as follows: + +- If the downlink data notification control information indicates that the detection of DDD Status event and buffered notification type is required, the SMF shall derive a PDR and a related FAR as defined in clause 5.28 of 3GPP TS 29.244 [13] to request the UPF to report an event of the first buffered downlink data packet identified by the PDR. When the SMF receives the corresponding report, the SMF shall send the notification to the NEF as defined in clause 4.2.2.2 of 3GPP TS 29.508 [12]. +- If the downlink data notification control information indicates that the detection of DDD Status event and transmitted notification type is required, the SMF shall detect event and send the notification as defined in clause 4.2.2.2 of 3GPP TS 29.508 [12]. +- If the downlink data notification control information indicates that the detection of DDN Failure event and/or DDD Status event and discarded notification type is required, the SMF shall derive a PDR and a related FAR as defined in clause 5.28 of 3GPP TS 29.244 [13] to request the UPF to report an event of the first discarded downlink data packet identified by the PDR. When the SMF receives the corresponding report, the SMF shall send the notification to the AMF as defined in clause 5.2.2.5.1 of 3GPP TS 29.502 [22] and/or send the notification to the NEF as defined in clause 4.2.2.2 of 3GPP TS 29.508 [12] respectively. + +#### 4.2.4.28 Network slice related data rate policy control + +When an Npcf\_SMPolicyControl\_Update request that requires a change of the authorized Session-AMBR and/or MBR update(s) for PCC Rule(s) corresponding to GBR service data flow(s) is received, the PCF may check if the S-NSSAI to which the received request relates is subject to network slice data rate policy control. If it is the case, the PCF shall apply network slice data rate control as described in clause 4.2.6.8. + +#### 4.2.4.29 Group related data rate policy control + +When an Npcf\_SMPolicyControl\_Update request that requires a change of the authorized Session-AMBR and/or MBR update(s) for PCC Rule(s) corresponding to GBR service data flow(s) is received, the PCF may apply group data rate control as described in clause 4.2.6.9. + +#### 4.2.4.30 Notification on network provided BAT Offset policy control trigger + +When the BAT\_OFFSET\_INFO policy control request trigger is set, upon receiving the BAT offset and optionally an adjusted periodicity from the NG-RAN, the SMF shall send an HTTP POST request to the PCF with an SmPolicyUpdateContextData data structure, including the "BAT\_OFFSET\_INFO" within the "repPolicyCtrlReqTriggers" attribute and the BAT offset within the "ranBatOffsetNotif" attribute and optionally the adjusted periodicity within the "adjPeriod" attribute. + +The SMF shall adjust the BAT offset value of "ranBatOffsetNotif" attribute received from NG-RAN based on the clock drifting report from UPF. Otherwise, the SMF shall notify the BAT offset value of "ranBatOffsetNotif" attribute to PCF without any adjustment. + +When the BAT\_OFFSET\_INFO policy control request trigger is set and the QoS Notification Control is also enabled for the corresponding PCC rule, upon receiving the BAT offset along with the "GFBR can no longer be guaranteed" notification from the NG-RAN feedback, the SMF shall, in addition to the provisions of clause 4.2.4.20, include the "BAT\_OFFSET\_INFO" within the "repPolicyCtrlReqTriggers" attribute and the BAT offset within the "ranBatOffsetNotif" attribute of the SmPolicyUpdateContextData data structure. Editor's Note: It is FFS how the bat offset is indicated and reported per PCC rule. + +#### 4.2.4.31 Network slice usage control + +When the PCF receives a Npcf\_SMPolicyControl\_Update request and the "NetSliceUsageCtrl" feature is supported, the PCF may check whether the S-NSSAI of the targeted SM Policy Association is subject to network slice usage control. If it is the case, the PCF may provision/update/remove in the Npcf\_SMPolicyControl\_Update response the network slice usage control information (e.g., the slice PDU session inactivity timer value) within the "sliceUsgCtrlInfo" attribute of the SmPolicyDecision data structure. + +NOTE: In this release of the specification, network slice usage control information provisioning/update/removal by the PCF is not supported in roaming scenarios. + +### 4.2.5 Npcf\_SMPolicyControl\_Delete Service Operation + +#### 4.2.5.1 General + +The delete service operation provides means for the NF service consumer to delete the policy context associated with a PDU Session. + +The following procedures using the Npcf\_SMPolicyControl\_Delete service operation are supported: + +- Deletion of the policy context associated with a PDU session. +- Report Accumulated Usage. +- Report Access Network Information. +- Network slice related data rate policy control. +- Group related data rate policy control. + +#### 4.2.5.2 SM Policy Association termination + +![Sequence diagram showing SM Policy Association termination between an NF service consumer and a PCF. Step 1: The NF service consumer sends a POST request to the PCF with the URI .../sm-policies/{smPolicyId}/delete. Step 2: The PCF responds with a 204 No Content status.](18d7d8de298d79e7bc87af5217f11203_img.jpg) + +``` + +sequenceDiagram + participant NF service consumer + participant PCF + Note right of NF service consumer: 1. POST .../sm-policies/{smPolicyId}/delete + NF service consumer->>PCF: Request + Note left of PCF: 2. 204 No Content + PCF-->>NF service consumer: Response + +``` + +Sequence diagram showing SM Policy Association termination between an NF service consumer and a PCF. Step 1: The NF service consumer sends a POST request to the PCF with the URI .../sm-policies/{smPolicyId}/delete. Step 2: The PCF responds with a 204 No Content status. + +**Figure 4.2.5.2-1: SM Policy Association termination** + +When an individual resource of the SM Policy Association collection shall be deleted, the NF service consumer shall invoke the Npcf\_SMPolicyControl\_Delete service operation towards the PCF using an HTTP POST request, as shown in figure 4.2.5.2-1, step 1. + +The NF service consumer shall set the request URI to "{apiRoot}/npcf-smolicycontrol/v1/sm-policies/{smPolicyId}/delete". The {smPolicyId} in the URI identifies the "Individual SM Policy" to be deleted. + +The HTTP POST request sent by the NF service consumer (e.g. SMF) shall contain (if available) the SM Policy Association related information within the SmPolicyDeleteData data structure in the request body: + +- accumulated usage within the "accuUsageReports" attribute as defined in clause 4.2.5.3; +- the user location(s) information within the "userLocationInfo" attribute, the information on when the UE was last known to be in that location within the "userLocationInfoTime" attribute, the PLMN Identifier or the SNPn Identifier (the PLMN Identifier and the NID) within the "servingNetwork" attribute, the timezone information within the "ueTimeZone" attribute and the RAN and/or NAS release cause(s) within the "ranNasRelCauses" attribute as defined in clause 4.2.5.4; + +NOTE 1: The SMF derives the value of the "userLocationInfoTime" attribute from the age of location information received from the AMF at PDU session termination as described in 3GPP TS 29.502[22]. Whether the "userLocationInfo" attribute also encodes the age of location is implementation specific. + +NOTE 2: The SMF encodes both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute when they are both received from the AMF. + +- the "PS\_TO\_CS\_HO" value within the "pduSessRelCause" attribute, if the PDU session is released due to PS to CS handover and the "PDUSessionRelCause" feature defined in clause 5.8 is supported; +- the "RULE\_ERROR" value within the "pduSessRelCause" attribute, if the PDU session is released due to a failed enforcement of the applied session rule as described in clause 4.2.4.21 and the "ImmediateTermination" feature defined in clause 5.8 is supported. + +When the PCF receives the HTTP POST request from the NF service consumer and if the PCF successfully processed and accepted the received HTTP POST request from the NF service consumer, the PCF shall acknowledges the request by sending an HTTP response message with the corresponding status code. The PCF acknowledges the delete request by sending a "204 No Content" response to the NF service consumer, as shown in figure 4.2.5.2-1, step 2. Further, the PCF shall remove the individual resource linked to the delete request. + +If errors occur when processing the HTTP POST request, the PCF shall send an HTTP error response as specified in clause 5.7. + +If the feature "ES3XX" is supported, and the PCF determines the received HTTP POST request needs to be redirected, the PCF shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +#### 4.2.5.3 Report Accumulated Usage + +If the UMC feature is supported, at PDU session termination, the SMF shall send the accumulated usage information for all the monitoring keys for which usage monitoring was previously enabled. When the SMF receives the accumulated usage report from the UPF as defined in clause 7.5.7.2 of 3GPP TS 29.244 [13], the SMF shall include one or more received accumulated usage reports in the "accuUsageReports" attribute of the SmPolicyDeleteData data structure. + +If all PDU sessions related to the same DNN and S-NSSAI combination for a user are terminated, the PCF shall store the remaining allowed usage, i.e. the information about the remaining overall amount of resources, in the UDR as defined in 3GPP TS 29.519 [15]. + +#### 4.2.5.4 Report Access Network Information + +If the RAN-NAS-Cause feature is supported or the NetLoc feature is supported, within the SmPolicyDeleteData data structure, the SMF shall provide the available access network information within the "userLocationInfo" attribute (if available), the information on when the UE was last known to be in that location within the "userLocationInfoTime" attribute (if available), the "ueTimezone" attribute (if available). Additionally, for the NetLoc feature, if the user location information is not available, the SMF shall include the PLMN Identifier or the SNPN Identifier (the PLMN Identifier and the NID) within the "servingNetwork" attribute; for RAN-NAS-Cause feature, if the SMF received from the access network the RAN cause and/or the NAS cause due to PDU session termination, the SMF shall provide the received cause(s) in the "ranNasRelCauses" attribute. + +NOTE 1: The SMF derives the value of the "userLocationInfoTime" attribute from the age of location information received in the Location-Report (defined in clause 5.3.1 of 3GPP TS 29.518 [36]) from the AMF. Whether the "userLocationInfo" attribute also encodes the age of location is implementation specific. + +NOTE 2: The SMF encodes both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute when they are both received from the AMF. + +#### 4.2.5.5 Void + +#### 4.2.5.6 Network slice related data rate policy control + +When an Npcf\_SMPolicyControl\_Delete request is received, the PCF may check if the S-NSSAI to which the received request relates is subject to network slice data rate policy control. If it is the case, the PCF shall apply network slice data rate control as described in clause 4.2.6.8. + +#### 4.2.5.7 Group related data rate policy control + +When an Npcf\_SMPolicyControl\_Delete request is received, the PCF may apply group data rate control as described in clause 4.2.6.9. + +### 4.2.6 Provisioning and Enforcement of Policy Decisions + +#### 4.2.6.1 General + +Policy Decisions are provided from the PCF to the NF service consumer (SMF) as part of the following service operations: + +- the Npcf\_SMPolicyControl\_Create Service Operation described in clause 4.2.2; +- the SM Policy Association Notification request as part of the Npcf\_SMPolicyControl\_UpdateNotify Service Operation as described in clause 4.2.3.2; and +- the Npcf\_SMPolicyControl\_Update service operation as described in clause 4.2.4 + +Policy decisions shall be encoded within the SmPolicyDecision data structure defined in clause 5.6.2.4 + +Policy decisions may include: + +- Session Rule(s), as described in clause 4.1.4.3, encoded within the "sessRules" attribute; + +- PCC Rule(s), as described in clause 4.1.4.2, encoded within the "pccRules" attribute; +- QoS decision(s), as described in clause 4.1.4.4.3, which can be referenced from PCC rule(s), encoded within the "qosDecs" attribute; +- Charging decision(s), as described in clause 4.1.4.4.4, which can be referenced from PCC rule(s), encoded within the "chgDecs" attribute; +- Traffic control decision(s), as described in clause 4.1.4.4.2, which can be referenced from PCC rule(s), encoded within the "traffContDecs" attribute; +- Usage monitoring control decision(s), as described in clause 4.1.4.4.5, which can be referenced from PCC rule(s) and session rule(s), encoded within the "umDecs" attribute; +- QoS monitoring decision, as described in clause 4.1.4.4.6, which can be referenced from PCC rule(s), encoded within the "qosMonDecs" attribute; +- Condition(s) that can be referenced from PCC rule(s) and session rule(s), encoded within the "conds" attribute; +- QoS characteristics for non-standard 5QIs and non-preconfigured 5QIs provided within the "qosChars" attribute; +- A reflective QoS timer; +- Policy control request triggers and applicable additional information, e.g. Revalidation Time, PRA information; +- Last requested rule data; +- Last requested usage data; +- Default charging method of the PDU session; +- "PDU Session with offline charging only" indication; +- Charging information; +- P-CSCF Restoration Indication; +- IP index information; +- Presence Reporting Area information; +- TSC user plane node management information; +- port management information for the DS-TT port; +- port management information for the NW-TT port; +- The request of the PDU session termination; +- Usage of QoS flow; +- Redundant PDU session indication; +- VPLMN Specific Offloading Policy; and +- the network slice usage control information (e.g. the slice PDU session inactivity timer value), if the "NetSliceUsageCtrl" feature is supported. + +NOTE: In this release of the specification, network slice usage control information provisioning/update/removal by the PCF is not supported in roaming scenarios. + +For the Npcf\_SMPolicyControl\_Create Service Operation, the SmPolicyDecision data structure shall contain a full description of all policy decision(s) provided by the PCF for the policy association. + +For the Npcf\_SMPolicyControl\_UpdateNotify service operation for the SM Policy Association Notification request and for the Npcf\_SMPolicyControl\_Update service operation, the SmPolicyDecision data structure shall contain a description of the changes to the policy decision(s) with respect to the last provided policy decision(s) for the corresponding policy association. The redundant PDU session indication, the default charging method of the PDU + +session, the "PDU Session with offline charging only" indication, the charging information, the Reflective QoS Timer and the IP index information shall not be updated by the PCF. + +If no other rule is defined for specific data types within the SmPolicyDecision data structure, the encoding of changes of the policy decision(s) in the SmPolicyDecision data structure shall follow the following principles: + +- 1) To modify an attribute with a value of type map (e.g. the "sessRules" attribute, the "pccRules" attribute, the "qosDecs" attribute, the "traffContDecs" attribute, the "umDecs" attribute, the "conds" attribute, etc.), this attribute shall be provided with a value containing a map with entries according to the following principles: + - A new entry of the map shall be added by supplying a new identifier (e.g. rule / decision identifier) as the key and the corresponding structured data type instance (e.g. PCC rule) with the complete content as the value. + - An existing entry of the map shall be modified by supplying the existing identifier as the key and the corresponding structured data type instance as the value, with the same existing identifier (e.g. set the "qosId" to the same existing QoS data decision identifier), which shall describe the modifications following bullets 1 to 6. + - An existing entry of the map shall be deleted by supplying the existing identifier as the key and "NULL" as the value. + - For an unmodified entry of the map, no entry needs to be provided within the map. +- 2) To modify an attribute with a structured data type instance as the value, the attribute shall be provided with a value containing a structured data type instance with entries according to bullets 1 to 6. +- 3) To modify an attribute with another type than map or structured data type as the value, the attribute shall be provided with a complete representation of its value, which shall replace the previous value. +- 4) To create an attribute of any type, the attribute shall be provided with a complete representation of its value. +- 5) To delete an attribute of any type, the attribute shall be provided with "NULL" as the value. + +NOTE 1: Attributes that are allowed to be deleted need to be marked as "nullable" within the OpenAPI file in Annex A. + +- 6) Attributes that are not added, modified or deleted do not need to be provided. + +NOTE 2: In the related data structures, no attribute can be marked as mandatory except the attribute containing the identifier (e.g. rule / decision identifier). + +The PCF shall not remove a provisioned policy decision data or condition data from the SMF when the associated reference(s) from the PCC rule(s) or session rule(s) are still valid except the usage monitoring data referred by the pre-defined PCC rule(s) (see clause 4.2.6.5.3.2 for further information). If the PCF determines that the policy decision or condition data shall be used for future PCC or session rule(s), the PCF may keep a policy decision data or condition data valid when the PCF removes all the PCC rule or session rule(s) referring to that policy decision data or condition data; otherwise the PCF shall remove the provisioned policy decision data or condition data when the PCF removes all the PCC or session rule(s) referring to the policy decision data or condition data. + +When the NF service consumer (SMF) accepts the notification of policy updates, and/or when after receiving the response to the request of policies the SM Policy association is retained in the NF service consumer (SMF), if the installation/activation of one or more new PCC rule(s) or the installation of one or more session rule(s) (i.e. rules which were not previously successfully installed) fails, although the failed PCC rule(s) or session rule(s) are removed, the policy decision and/or condition data which are referred by the failed PCC rule(s) or session rule(s) may remain applicable in the SMF until the PCF removes them. If the PCF determines that the policy decision or condition data that remain applicable shall be used for future PCC or session rule(s) (e.g. because the PCF reattempts to install the failed PCC rule) the PCF may keep these policy decision data or condition data valid; otherwise the PCF shall immediately remove these policy data or condition data from the SMF. + +NOTE 3: Due to internal policies, the SMF could decide to remove the policy decision and/or condition data not referred by any PCC and/or session rule(s) before the PCF decides to remove them. When the PCF decides to remove the policy decision and/or condition data that were silently removed by the SMF, the SMF accepts the removal indication, as specified in clauses 4.2.3.26 and 4.2.4.26. When the PCF decides to reuse the policy decision and/or condition data that were silently removed by the SMF, the SMF reports PCC and/or session rule error as specified in clauses 4.2.3.16, 4.2.4.15, 4.2.3.20 and 4.2.4.21. + +NOTE 4: When the PCF notification of policy updates is rejected as specified in clauses 4.2.3.16 and 4.2.3.20 with a HTTP "400 Bad Request" status code, the whole update is rejected, including the provided policy decision and/or condition data. When the SMF reports PCC and/or session rule(s) error as specified in clauses 4.2.4.15 and 4.2.4.21 for all the provisioned PCC rule and/or session rule(s), the valid policy decision and/or condition data provided in the corresponding update response can remain valid in the SMF until the PCF removes them. + +The error handling for the policy decision and/or condition data which are not referred by any PCC rule and/or session rule stored at the SMF is defined in clause 4.2.3.26 and 4.2.4.26. + +## 4.2.6.2 PCC Rules + +### 4.2.6.2.1 Overview + +The PCF may perform an operation on a single PCC rule or a group of PCC rules. The impacted PCC rule(s) shall be included in the "pccRules" map attribute within the SmPolicyDecision data structure with the associated "pccRuleId" as the key of the map. For activating a pre-defined PCC rule or installing or modifying a dynamic PCF-provisioned PCC rule, the corresponding PccRule data structure shall be provided as the map entry value. For deactivating or removing a PCC rule, the map entry value shall be set to "NULL". + +NOTE 1: When deactivating a predefined PCC rule that is activated in more than one QoS flow, this predefined PCC rule is deactivated simultaneously in all the QoS flows where it was previously activated. + +In order to activate a pre-defined PCC rule, the PCF shall include within the PccRule data structure the pre-defined PCC rule identifier within the "pccRuleId" attribute and the "refCondData" attribute, if applicable, i.e. the PccRule data structure is empty, except for the "pccRuleId" attribute and the "refCondData" attribute, if applicable. If the "refCondData" attribute is applicable, a "conds" attribute containing the corresponding ConditionData data structure referred by this PCC rule shall be included in the SmPolicyDecision data structure, if it has not been previously provided. + +In order to install a new dynamic PCF-provisioned PCC rule, the PCF shall further set other attributes within the PccRule data structure as follows: + +- It may include the precedence of a PCC rule among the other PCC rules of the PDU session, within the "precedence" attribute. Within a PDU session, the PCF shall authorize different precedence values for the PCC rules whose packet filters contained within the "flowDescription" attribute or the "ethFlowDescription" attribute include the "packetFilterUsage" attribute set to "true". + +NOTE 2: The SMF sets the precedence value of a QoS rule to the precedence value of the PCC rule for which the QoS rule is generated. The UE considers as an error when two or more QoS rules associated with a PDU session have identical precedence values. + +- It shall include either the flow information within the "flowInfos" attribute or the application identifier within the "appId" attribute. +- It shall include one reference to the QosData data structure within the "refQosData" attribute. In this case, a "qosDecs" attribute containing the corresponding QoS data policy decision shall be included in the SmPolicyDecision data structure, if it has not been previously provided. +- It may include one or more reference(s) to the QosData structure within the "refAltQosParams" attribute to refer to the Alternative QoS parameter set(s) of the service data flow. In this case, a "qosDecs" attribute containing the corresponding alternative QoS data policy decision(s) shall be included in the SmPolicyDecision data structure, if it has not been previously provided. +- It shall include one reference to the TrafficControlData data structure within the "refTcData" attribute. In this case, a "traffContDecs" attribute containing the corresponding Traffic Control data policy decision shall be included in the SmPolicyDecision data structure, if it has not been previously provided. +- It may include one reference to the ChargingData data structure within the "refChgData" attribute. In this case, a "chgDecs" attribute containing the corresponding Charging Data policy decision shall be included in the SmPolicyDecision data structure, if it has not been previously provided. + +- It may include one reference to the UsageMonitoringData data structure within the "refUmData" attribute. In this case, a "umDecs" attribute containing the corresponding Usage Monitoring data policy decision shall be included in the SmPolicyDecision data structure, if it has not been previously provided. +- It may include one reference to the QosMonitoringData data structure within the "refQosMon" attribute. In this case, a "qosMonDecs" attribute containing the corresponding QoS Monitoring data policy decision shall be included in the SmPolicyDecision data structure, if it has not been previously provided. +- It may include one reference to the ConditionData data type within the "refCondData" attribute. In this case, a "conds" attribute containing the corresponding Condition Data shall be included in the SmPolicyDecision data structure, if it has not been previously provided. +- If the "PowerSaving" feature is supported, it may include the traffic parameter data within the "traffParaData" attribute. + +In order to modify an existing dynamic PCF-provisioned PCC rule, the PCF shall further set other attributes within the PccRule data structure as follows: + +- If the PCF needs to modify attribute(s) within a PCC rule, the PCF shall include the modified attribute(s) with their new value(s) within the associated PccRule data instance in the SmPolicyDecision data structure. Previously supplied attribute(s) not supplied in the modified PCC rule instance shall remain valid. +- If the PCF only needs to modify the content of the referenced policy decision data (e.g. QosData, ChargingData, etc.) and/or condition data for one or more PCC rule(s), the PCF shall include, within the SmPolicyDecision data structure, the corresponding policy decision data and/or condition data within the corresponding map attribute(s) (e.g. include the QoS data decision(s) within the "qosDecs" attribute). +- In order to modify the content of the referenced condition data for one or more existing pre-defined PCC rule(s), the PCF shall include, within the SmPolicyDecision data structure, the corresponding condition data within the "conds" attribute. + +NOTE 3: To update a policy decision data and/or condition data instance, the PCF can provide only the modified attribute(s) with their new value(s) or could provide both, the modified attribute(s) with their new value(s) and the unmodified attributes. When only the modified attribute(s) are provided, the previously supplied attribute(s) not supplied in the modified policy decision data and/or condition data instance remain valid. + +- PCF may also perform a full replacement of a policy decision data and/or condition data instance by including the new reference to the policy decision data and/or condition data instance within the associated PCC rule and the corresponding policy decision and/or condition data in the SmPolicyDecision data structure, if it has not been previously provided. + +The PCF may combine multiple of the above PCC rule operations in a single message. + +The SMF shall ensure that at least one PCC Rule bound to the default QoS flow is activated for the PDU Session. If the PCF does not provision any PCC rule, the SMF shall activate at least one pre-defined PCC rule which is not known by the PCF and bind it to the default QoS flow. + +If the authorized default QoS is GBR type or delay critical GBR type as defined in clause 4.2.6.3.3, to ensure that one and only one of the authorized PCC rules is bound to the default QoS flow the PCF shall indicate that one and only one PCC rule is bound to the default QoS flow as defined in clause 4.2.6.2.10. The SMF shall not bind any other PCC rule to the default QoS flow with a GBR or delay critical GBR 5QI. + +The SMF shall ensure that the packet filters signalled to UE reflects the QoS Flow binding of PCC rules, except for those extending the inspection beyond what can be signalled to the UE. The SMF shall explicitly signal the packet filters to the UE if the corresponding "packetFilterUsage" attribute is provided and set to true. If the "packetFilterUsage" attribute is absent or set to false, it is an SMF decision whether to signal the packet filters that is redundant from a traffic mapping point of view. + +The default QoS rules shall contain either a Packet Filter Set that allows all UL packets or a Packet Filter Set that is generated from the UL packet filters (and from the DL packet filters if they are available) with the "packetFilterUsage" attribute set to true. + +NOTE 1: If multiple PCC rules with the "packetFilterUsage" attribute set to true are bound to the QoS Flow associated with the default QoS rule, it is up to SMF implementation which one will be chosen to generate the default QoS rule. If the PCC rule that is chosen to generate the default QoS rule is removed/deactivated, another PCC rule bound to the QoS Flow associated with the default QoS rule will be used instead and the default QoS rule would be updated accordingly. + +NOTE 2: For IP type PDU Session or Ethernet type PDU Session, the default QoS rule is the only QoS rule of a PDU Session which may contain a Packet Filter Set that allows all UL packets, and in this case, the highest precedence value can be used for the QoS rule. + +#### 4.2.6.2.2 Gate Function + +The Gate Function is a user plane function that permits to control, i.e. enabling or disabling, the forwarding of data packets belonging to a service data flow. A gate is provisioned by the PCF within a PCC rule, enforced by the SMF and ultimately applied by the UPF. + +If a PCC rule contains the "flowInfos" attribute applicable for uplink service data flow(s), it shall describe a gate for the corresponding uplink service data flow(s). If a PCC rule contains the "flowInfos" attribute(s) applicable for downlink service data flow(s), it shall describe a gate for the corresponding downlink service data flow(s). If the PCC rule contains an "appId" attribute, it shall describe a gate for the corresponding detected application traffic. In order to do so, the "flowStatus" attribute within the TrafficControlData data structure to which the PCC rule refers shall describe if uplink and/or downlink gate(s) is/are open or closed. + +The commands to open or close a gate shall lead to enabling or disabling the passage of the corresponding data packets. If a gate is closed, all data packets of the related service data flow(s) are dropped by the UPF. If a gate is open, the data packets of the related service data flow(s) are allowed to be forwarded by the UPF. + +#### 4.2.6.2.3 Policy enforcement for authorized QoS per PCC Rule + +The PCF may provide the authorized QoS for a PCC rule to the SMF. The Provisioning of the authorized QoS per PCC Rule shall be performed using the PCC rule provisioning procedure defined in clause 4.2.6.2.1. For a PCF-provided PCC rule, the authorized QoS shall be encoded using the QosData data structure. The PCF shall include for this purpose a reference to this QosData data structure within the "refQosData" attribute of the PCC rule and a "qosDecs" attribute containing this QoS data decision within the SmPolicyDecision data structure. + +If the authorized QoS is provided for a PCC rule, the SMF shall derive the associated QoS profile towards the access network, if applicable, the associated QoS rule towards the UE, if applicable, and the associated QoS information with the PDR(s) towards the UPF. + +#### 4.2.6.2.4 Redirect Function + +When the ADC feature is supported, the PCF may provide the redirect instructions for one or several dynamic PCC rule(s) to the SMF. This Provisioning shall be performed using the policy provisioning procedure defined in clause 4.2.6.1. + +The "traffContDecs" attribute within the SmPolicyDecision is used to provide traffic control decision(s). The redirect instructions shall be encoded using the "redirectInfo" attribute within the corresponding TrafficControlData data structure, and used to provide a RedirectInformation data structure with the following components: + +- The "redirectEnabled" attribute to indicate whether redirect is enabled or not. It shall be included and set to true when the redirect instruction is initially provisioned and may be included in subsequent updates of the RedirectInformation to enable or disable the redirect instruction. +- The redirect address may be provided using the "redirectAddressType" and "redirectServerAddress" attributes or it may be preconfigured in the SMF/UPF. A redirect destination provided within the "redirectServerAddress" attribute for a dynamic PCC Rule shall override the redirect destination preconfigured in the SMF/UPF. + +NOTE 1: The SMF/UPF uses the preconfigured redirection address only if it can be applied to the application traffic being detected, e.g. the redirection destination address could be preconfigured on a per application identifier basis. + +If redirect action(s) need to be applied to a dynamic PCC rule, this PCC rule shall reference a traffic control decision with the relevant redirect instructions. If a dynamic PCC rule includes flow information for UE IPv4 address and IPv6 + +prefix address(es) related to the same application identifier and the ADCmultiRedirection feature is supported, the "addRedirectInfo" attribute including more than one RedirectInformation data structure may be provided simultaneously to the redirect instruction. + +If the "redirectInfo" attribute is provided for a dynamic PCC rule, the SMF shall instruct the UPF to perform the requested redirection as defined in 3GPP TS 29.244 [13]. + +If the "redirectServerAddress" attribute is not provided in the dynamic PCC rule and the redirection address is not preconfigured in the SMF/UPF for this PCC rule, the SMF shall perform PCC Rule Error Report, as specified in clauses 4.2.3.16 and 4.2.4.15, and set the "failureCode" attribute to "MISS\_REDI\_SER\_ADDR". + +NOTE 2: When the redirect server address is not provided by the PCC rule, the SMF determines the "MISS\_REDI\_SER\_ADDR" error, e.g. when the SMF determines the redirect destination is not pre-configured at both the SMF and the UPF. + +To disable the redirect function for one or more already installed PCC Rule(s), the PCF shall: + +- update the PCC rule to modify the reference to Traffic Control Data decision to point to another (existing or new) Traffic Control Data decision that does not have "redirectInfo" instructions; or +- update the Traffic Control Data decision that the PCC rule refers to with the "redirectEnabled" attribute set to false, if the PCF disables the redirect function for all the PCC rules that refer to this Traffic Control Data decision. + +For a predefined PCC rule, the redirect information shall be included in the rule definition at the SMF/UPF. Redirect information shall be activated for predefined PCC rules while those rules are active. + +#### 4.2.6.2.5 Usage Monitoring Control + +Usage monitoring may be performed for service data flows associated with one or more PCC rules. + +The provisioning of usage monitoring control per PCC rule shall be performed using the PCC rule provisioning procedure as defined in clause 4.2.6.2.1. For a dynamic PCC rule, the reference to the UsageMonitoringData data structure of the usage monitoring control instance, which is related with the PCC rule, shall be included within the "refUmData" attribute of the PccRule data structure of the PCC rule(s). For a predefined PCC rule, the reference to a usage monitoring control instance shall be included in the rule definition at the SMF. Usage monitoring shall be activated for both service data flows associated with predefined PCC rules and dynamic PCC rules, including rules with deferred activation and/or deactivation times while those rules are active. + +#### 4.2.6.2.6 Traffic Steering Control support + +If the TSC feature is supported, the PCF may instruct the SMF to apply a traffic steering control for the purpose of: + +- steering the subscriber's traffic to an appropriate operator or 3rd party service functions (e.g. NAT, antimalware, parental control, DDoS protection) in the N6-LAN or 5G-LAN type of services according to operator policy or, if the SFC feature is supported, according to the information of AF influenced service function chaining, and/or +- enabling the routing of the user traffic to a local Data Network identified by a DNAI per AF request. When the "CommonEASDNAI" feature is supported, the procedure is also used by the PCF to request to select a common EAS or a common DNAI for a set of UE associated with the same traffic correlation Id accessing the application identified by the service data flow template as requested by the AF or to provide endpoint information for the NEF to be notified with information related to UE members of the set of UEs identified by traffic correlation ID. + +If the SFC feature is supported, the PCF may instruct the SMF to apply both traffic steering controls above simultaneously. + +##### 4.2.6.2.6.1 Steering the traffic in the N6-LAN or steering the 5G-LAN type of services + +This procedure is only applicable in non-roaming and home-routed scenarios. + +For the purpose of steering the subscriber's traffic to an appropriate operator or 3rd party service functions in the N6-LAN or steering the 5G-LAN type of services based on network operator configured policies not related to an AF request to influence service function chaining, the PCF shall include within the PccRule data structure a reference to the relevant Traffic Control Data decision and: + +- include within the PccRule data structure either the application to be detected identified by the "appId" attribute or the service data flow to be detected identified by the "flowInfos" attribute; and +- include a "traffContDecs" attribute containing the corresponding Traffic Control Data decision within the SmPolicyDecision, if it has not been previously provided. In this case, the PCF shall include directly within this Traffic Control Data decision a traffic steering policy identifier for downlink within the "trafficSteeringPolIdDI" attribute and/or a traffic steering policy identifier for uplink within the "trafficSteeringPolIdUI" attribute. + +When the SFC feature is supported, for the purpose of steering the subscriber's traffic to an appropriate operator or 3rd party service functions in the N6-LAN or steering the 5G-LAN type of services related to an AF request to influence service function chaining, the PCF shall determine if the ongoing PDU Session is impacted by the steering of traffic to a Service Function Chain as follows: + +- If the AF request includes the individual IP address/ prefix allocated to a UE or the UE MAC address, the PCF shall store the received traffic steering control information and perform session binding as defined in clause 6.2 of 3GPP TS 29.513 [7] to determine the impacted PDU session. +- Otherwise, the PCF fetches from the UDR, as defined in 3GPP TS 29.519 [15], the traffic steering control information applicable for a UE, any UE or an Internal Group Id (if received in the SMF request). + +Then the PCF authorizes the request for influencing service function chaining. For the impacted PDU Session that corresponds to the AF request, the PCF shall take into account, if available, the service function chaining indication stored in the policy data subscription information in the UDR, as defined in 3GPP TS 29.519 [15], to determine whether it is allowed to generate PCC rules with traffic steering information based on AF request information. When allowed, the PCF shall generate PCC rules with traffic steering control information and provide the corresponding Traffic Control Data decision as described above. In this case the traffic steering policy identifier for downlink and/or uplink traffic may be derived from the SFC ID(s) provided by the AF. Additionally, the Traffic Control Data decision may include metadata if provided by the AF. + +NOTE: In case there are both a network operator configured policy for N6-LAN Traffic Steering in PCF and an AF-provided SFC ID(s) mapping to traffic steering control information, the PCF decides based on local configuration which one takes precedence. + +The PCF may also provision the traffic steering control information by activating pre-defined PCC rule(s) in the SMF. + +If traffic steering policy provided in the "trafficSteeringPolIdUI" and/or "trafficSteeringPolIdDI" attribute are invalid or unknown, or the enforcement of the steering of the traffic failed, the SMF shall return a PCC Rule Error Report, as specified in clauses 4.2.3.16 and 4.2.4.15, and set the "failureCode" attribute to "TRAFFIC\_STEERING\_ERROR". + +#### 4.2.6.2.6.2 Steering the traffic to a local access of the data network + +This procedure is only applicable in non-roaming and visited access (i.e. LBO) scenarios. + +The PCF shall determine if the ongoing PDU Session is impacted by the routing of traffic to a local access to a data network as follows: + +- If the AF request includes the individual IP address/ prefix allocated to a UE or the UE MAC address, the PCF shall store the received traffic routing information and perform session binding as defined in clause 6.2 of 3GPP TS 29.513 [7] to determine the impacted PDU session. +- Otherwise, the PCF fetches from the UDR, as defined in 3GPP TS 29.519 [15], the traffic routing data information applicable for a UE, any UE or one or more Internal Group Id(s) (if received in the SMF request) and/or subscriber category(ies). + +NOTE 1: If the UDR provides as part of the traffic routing data information a list of Internal Group Id(s), this information applies to all the PDU sessions related to UEs that belong to every one of these groups, i.e. a single UE needs to be a member of every group in the list of Internal Group Id(s). If the list of subscriber category(ies) is part of the traffic routing data information, this information applies to all the PDU sessions related to the UEs that belong to every one of these Subscriber Categories. + +Then the PCF authorizes the request for influencing SMF routing decisions. For the impacted PDU Session that corresponds to the AF request, the PCF shall take into account, if available, the local routing indication stored in the policy data subscription information in the UDR, as defined in 3GPP TS 29.519 [15], to determine whether it is allowed + +to generate PCC rules with traffic routing information. When allowed, the PCC rules are generated based on the AF request as follows: + +- When the request is for influencing SMF routing decisions, based on traffic routing information, operator's policy, etc., the PCF determines the traffic steering policy. The traffic steering policy indicates, for each DNAI, a traffic steering policy identifier configured in the SMF and/or if the N6 routing information associated to the application is explicitly provided by the AF, the N6 routing information (as provided by the AF). The traffic steering policy identifier is derived by the PCF from the routing profile Id provided by the AF and is related to the mechanism enabling traffic steering to the DN. Then: +- The PCF shall include within each PccRule data structure the necessary information to identify the concerned traffic within either the "flowInfos" attribute or the "appId" attribute, and include within the TrafficControlData data type that the PCC rule refers to a list of locations that the traffic shall be routed to in the "routeToLocs" attribute, and, if the "AF\_latency" feature is supported, the PCF shall include the maximum allowed user plane latency within the "maxAllowedUpLat" attribute if available. If "EASIPreplacement" feature is supported, the PCF shall include the EAS IP replacement information within the "easIpReplaceInfos" attribute if available. +- Within each RouteToLocation instance, the PCF shall include a DNAI in the "dnai" attribute to indicate the location of the application towards which the traffic routing is applied, and a traffic steering policy identifier in the "routeProfId" attribute, to indicate the traffic steering policy that applies to the indicated DNAI, and/ or the explicit N6 traffic routing information in the "routeInfo" attribute. +- If the AF provides both a routing profile Id and N6 routing information for a DNAI, the PCF may include a RouteToLocation instance with the required information or may include two RouteToLocation instances with the same DNAI within the "dnai" attribute and a traffic steering policy identifier within the "routeProfId" attribute in one instance and explicit routing information within the "routeInfo" attribute in the other instance. + +NOTE 2: The N6 traffic routing requirements are related to the mechanism enabling traffic steering in the local access to the DN. The routing profile ID refers to a pre-agreed policy between the AF and the 5GC. This policy may refer to different steering policy identifier(s) sent to the SMF and e.g. based on time of the day, etc. + +NOTE 3: When per DNAI both, the "routeProfId" and the "routeInfo" attributes are provided, if the pre-configured traffic steering policy referenced by the "routeProfId" attribute contains information that is overlapping with the N6 traffic routing information provided in the "routeInfo" attribute, the N6 traffic routing information takes precedence. + +NOTE 4: In this release of the specification, either a traffic steering policy identifier for UL or a traffic steering policy identifier for DL can be defined per DNAI. + +- When the request is for subscribing to UP path change events of the PDU session, the PCF shall include the information on AF subscription to UP path change events within the PCC rule(s) to request the SMF to create a subscription to such notifications for the AF. In order to do so, the PCF shall include within each PccRule data structure the necessary information to identify the concerned traffic within either the "flowInfos" attribute or the "appId" attribute, and include within the Traffic Control Data decision that the PCC rule refers to the information on AF subscription to events within the "upPathChgEvent" attribute. Within this "upPathChgEvent" attribute, the PCF shall include the "dnaiChgType" attribute to indicate the type of notification (i.e. early notification, late notification or both), the notification URI within the "notificationUri" attribute, the notification correlation Id within the "notifCorreId" attribute, and if the URLLC feature is supported, an indication of AF acknowledgement to be expected within the "afAckInd" attribute. In order to enable the AF to identify the AF request to which the notification corresponds when the AF receives a UP path change notification from the SMF, as defined in clause 4.2.2.2 of 3GPP TS 29.508 [12], the PCF shall set the values of the "notificationUri" attribute and "notifCorreId" attribute respectively as follows: +- If the PCF fetches the traffic routing data information from the UDR, the PCF shall set the value of the "notificationUri" attribute to the value of the "upPathChgNotifUri" attribute of the TrafficInfluData data structure and set the value of the "notifCorreId" attribute to the value of the "upPathChgNotifCorreId" attribute of the TrafficInfluData data structure as defined in 3GPP TS 29.519 [15]. +- If the PCF receives the traffic routing data information from the AF via N5 interface, the PCF shall set the values of the "notificationUri" attribute and the "notifCorreId" attribute according to the "upPathChgSub" attribute within the AfRoutingRequirement data structure as defined in 3GPP TS 29.514 [17]. + +If the NEF/AF provided information about the feature support on Nsmf\_EventExposure service as described in 3GPP TS 29.514 [17] (AF request applies an individual UE address) or 3GPP TS 29.519[15] (AF request applies to PDU sessions not identified by a UE address), the PCF may also include this information within the "nscSuppFeats" attribute included within the PccRule data type. + +- If the AF request includes an indication that application relocation is not possible, the PCF shall include within the PccRule data instance(s) the necessary information to identify the traffic within either the "flowInfos" attribute or the "appId" attribute and the "appReloc" attribute set to true. In this case, the SMF shall ensure that for the traffic related with the concerned application, no DNAI change takes place once selected initially for this application. +- If the "EASDiscovery" feature is supported and the AF request includes an indication that EAS rediscovery is required, the PCF shall include within the PccRule data instance(s) the necessary information to identify the traffic within the "appId" attribute and the "easRedisInd" attribute set to true. +- If the URLLC feature is supported and the AF request includes an indication that the UE IP address preservation should be considered, the PCF shall include within the concerned PccRule data instance(s) the "addrPreserInd" attribute set to true. +- If the AF request includes an indication that the PDU session should be correlated via a common DNAI for a given traffic, the PCF shall include within the TrafficControlData data instance provisioned for one or more PCC rule(s), the "traffCorreInd" attribute set to true. + +NOTE 5: The indication of traffic correlation can be provided together with the traffic routing information by the AF for all the members of the 5G VN group. Referred to clause 5.29.4 of 3GPP TS 23.501 [2]. + +- If the feature "SimultConnectivity" is supported and the AF request includes an indication that the simultaneous connectivity may be temporarily maintained for the target and the source PSA during the edge re-location procedure, the PCF may include within the TrafficControlData data instance provisioned for one or more PCC rule(s) the "simConnInd" attribute set to true, as indicated by the AF. If the feature "SimultConnectivity" is supported and the AF request includes the time interval to be considered for inactivity of the traffic routed through the source PSA after which the simultaneous connectivity can be terminated, the PCF may also include the received duration within the "simConnTerm" attribute. +- If the feature "CommonEASDNAI" is supported and AF includes a traffic correlation information within "tfcCorreInfo" attribute, and + - if the AF request also includes an indication that the PDU session should be correlated via a common DNAI, the PCF shall include the TrafficControlData data instance provisioned for one or more PCC rule(s), "COMMON\_DNAI" within the "corrType" attribute and the identification of a set of UEs accessing the application identified by the service data flow template within the "tfcCorrId" attribute. If the NEF has added its information in the AF request in order to be notified with information related to UE members of the set of UEs identified by traffic correlation ID, then the PCF shall include also the "notifUri" and "notifCorrId" attributes within the "tfcCorreInfo" attribute of the TrafficControlData; or + - if the AF request also includes an indication that a common EAS for the application identified by the service data flow template should be selected, the PCF shall include the TrafficControlData data instance provisioned for one or more PCC rule(s), the "COMMON\_EAS" within the "corrType" attribute, the identification of a set of UEs accessing the application identified by the service data flow template within the "tfcCorrId" attribute, the common EAS address(s) within the "comEasIpv4Addr" attribute and/or "comEasIpv6Addr" attribute and/or the FQDN range corresponding to the application within the "fqdnRange" attribute. If the NEF has added its information in the AF request in order to be notified with information related to UE members of the set of UEs identified by traffic correlation ID, then the PCF shall include also the "notifUri" and "notifCorrId" attributes within the "tfcCorreInfo" attribute of the TrafficControlData. + +NOTE 6: Common EAS selection means the common DNAI is selected. + +The PCF shall provide the PCC rule(s) as defined in clause 4.2.6.2.1. + +If the temporal validity condition is received, the PCF shall evaluate the temporal validity condition of the AF request and inform the SMF to install or remove the corresponding PCC rule(s) according to the evaluation result. When policies specific to the PDU Session and policies general to multiple PDU Sessions exist, the PCF gives precedence to the PDU Session specific policies over the general policies. + +If the spatial validity condition is received, the PCF considers the latest known UE location to determine the PCC rules provided to the SMF. In order to do that, the PCF shall request the SMF to report the notifications about change of UE location in an area of interest (i.e. Presence Reporting Area) as defined in clauses 4.2.2.13 or 4.2.3.19. The subscribed area of interest may be the same as the one provided in spatial validity condition, or may be a subset of the spatial validity condition (e.g. a list of TAs) based on the latest known UE location. When the SMF detects that the UE entered the area of interest subscribed by the PCF, the SMF notifies the PCF and the PCF provides to the SMF the PCC rule(s) described above. When the SMF becomes aware that the UE left the area subscribed by the PCF, the SMF notifies the PCF and the PCF may remove or provide updated PCC rule(s) to the SMF. + +When the PCC rules are installed, the SMF may, based on local policies, take the information in the PCC rule(s) into account to: + +- if the PDU Session is of IP type and the "addrPreserInd" attribute is included and set to true in the PCC rule(s), the SMF should preserve the UE IP address and, if necessary, not reselect the related PSA UPF for the traffic identified in the PCC rule once the PSA UPF is selected; otherwise, the SMF (re)selects UPF(s) as it might be required for PDU Sessions. +- activate mechanisms for traffic multi-homing or enforcement of an UL Classifier (UL CL). +- inform the AF of the (re)selection of the UP path (change of DNAI) and/or the candidate DNAI(s) for the PDU Session if the "CommonEASDNAI" feature is supported and the "candDnaiInd" attribute was set to "true". +- determine the target DNAI(s) for the current UE location, which may imply I-SMF selection or removal to be requested to the AMF as defined in 3GPP TS 29.502 [22]. +- if the "traffCorreInd" attribute set to true is included in the TrafficControlData data type referenced by a set of PCC rules, based on SMF implementation and local configuration, the SMF should select a common DNAI from the list of DNAI included in the "routeToLocs" attribute for the identified traffic of the PDU session. +- if the "simConnInd" attribute set to true is included in the TrafficControlData data type referenced by a set of PCC rules, the SMF may temporarily maintain simultaneous connectivity for the source and target PSA at edge relocation procedure, and may influence the establishment of a temporary N9 forwarding tunnel between the source UL CL and target UL CL. If the "simConnTerm" attribute is also included, the SMF may consider the indicated time interval as the minimum one to be considered for inactivity for the described traffic before the connectivity over the source PSA may be removed. +- if the "maxAllowedUpLat" attribute is received, SMF may use this value to decide whether edge relocation is needed to ensure that the user plane latency does not exceed the value and whether to relocate the PSA UPF to satisfy the user plane latency. +- if the "easIpReplaceInfos" attribute is received, the SMF may instruct the local PSA UPF with the EAS IP replacement information using "Outer Header Creation" as defined in 3GPP TS 29.244 [13] clause 8.2.56 and "Outer Header Removal" as defined in 3GPP TS 29.244 [13] clause 8.2.64. The PSA UPF shall be configured by the SMF to perform one creation and one removal of the appropriate outer header(s) both in the uplink and in the downlink direction in a way that the address information indicated by the "source" attribute (within "easIpReplaceInfos") is used in the headers of the packets towards the UE and the address information indicated by the "target" attribute (within "easIpReplaceInfos") is used in the headers of the packets towards the DN. +- if the "easRedisInd" attribute set to true is included, the SMF may indicate the UE to refresh the cached EAS information as defined in clause 6.3.2 of 3GPP TS 24.501 [20]. +- if the "tfcCorreInfo" attribute is received, and, + - if the "COMMON\_DNAI" is included within the "corrType" attribute in the TrafficControlData data type referenced by a set of PCC rules, based on SMF implementation and local configuration, the SMF should select a common DNAI from the list of DNAI included in the "routeToLocs" attribute for the traffic of the PDU session which have the same traffic correlation Id within the "tfcCorrId" attribute as defined in clause 6.2.3.2.6 of TS 23.548 [62]. The SMF shall use the provided DNAI as the common DNAI when only one is included in the "routeToLocs" attribute; or + - if the "COMMON\_EAS" is included within the "corrType" attribute in the TrafficControlData data type referenced by a set of PCC rules, the SMF should use the value within the "fqdnRange" if received to match the FQDN received from the EASDF via the Neasdf\_DNSContext\_Notify request. If they are matched, the + +SMF may indicate the UE the common EAS address(s) received within the "comEasIpv4Addr" attribute and/or "comEasIpv6Addr" attribute. + +NOTE 7: In order for the SMF to initiate the EASDF-based EAS discovery procedure, the SMF will use the FQDN information received within the "fqdnRange" attribute for setting traffic route and finding DNAI. The "flowInfos" attribute or the "appId" attribute will not be considered for that purpose. + +- if the "notifUri" attribute and "notifCorrId" attribute are included, the SMF shall notify the 5GC determined information for a set of UEs identified by Traffic Correlation ID. + +NOTE 8: Common EAS selection means the common DNAI is selected. + +If routing of traffic to a local access to a data network policy provided in the "routeToLocs" attribute is invalid, unknown or not applicable, or the enforcement of the steering of the traffic to the indicated DNAI failed, the SMF shall return a PCC Rule Error Report, as specified in clauses 4.2.3.16 and 4.2.4.15, and set the "failureCode" attribute to "DNAI\_STEERING\_ERROR". + +#### 4.2.6.2.7 Conditioned PCC rule + +The PCF may control at what time the status of a PCC rule changes. In order to provision a PCC rule with conditional data, the PCF shall provision a PCC rule as defined in clause 4.2.6.2.1 and include within its "refCondData" attribute the value of the "condId" attribute of the targeted ConditionData instance. The PCF shall also ensure that this referenced ConditionData instance is included in the "conds" map attribute within the SmPolicyDecision data structure, following the procedures defined in clause 4.2.6.1. + +Within the ConditionData instance, the PCF shall include the activation time within the "activationTime" attribute and/or the deactivation time within the "deactivationTime" attribute. + +When the SMF receives a conditioned PCC rule, the SMF shall act as follows: + +- 1) If only the "activationTime" attribute is provided by the PCF and the time specified in it is in the future, then the SMF shall set the PCC rule to inactive state and only change it to active state at the specified time. If this time specified in the "activationTime" attribute is in the past, then the SMF shall immediately set the PCC rule to active state. +- 2) If only the "deactivationTime" attribute is provided by the PCF and the time specified in it is in the future, then the SMF shall set the PCC rule to active state and only change it to inactive state at the specified time. If this time specified in the "deactivationTime" is in the past, then the SMF shall immediately set the PCC rule to inactive state. +- 3) If both the "activationTime" attribute and the "deactivationTime" attribute are provided by the PCF, and the value specified in the "activationTime" occurs before the value specified in the "deactivationTime" attribute, and also when the PCC rule is provided before or at the value specified in the "deactivationTime", the SMF shall handle the PCC rule first as defined in 1) and then as defined in 2). +- 4) If both the "activationTime" attribute and the "deactivationTime" attribute are provided by the PCF, and the value specified in the "deactivationTime" attribute occurs before the value specified in the "activationTime", and also when the PCC rule is provided before or at the value specified in the "activationTime" attribute, the SMF shall handle the PCC rule first as defined in 2) and then as defined in 1). +- 5) If both the "activationTime" attribute and the "deactivationTime" attribute are provided by the PCF and are both in the past, and the value specified in the "activationTime" occurs before the value specified in the "deactivationTime" attribute, then the SMF shall immediately set the PCC rule to inactive state. +- 6) If both the "activationTime" attribute and the "deactivationTime" attribute are provided by the PCF and are both in the past, and the value specified in the "deactivationTime" attribute occurs before the value specified in the "activationTime" attribute, then the SMF shall immediately set the PCC rule to active state. +- 7) If both "activationTime" attribute and "deactivationTime" attribute are specified with the same time, the SMF shall report a PCC rule error for the concerned PCC rule(s), as specified in clauses 4.2.3.16 and 4.2.4.15, and set the "failureCode" attribute to "INCORRECT\_COND\_DATA". + +The PCF may modify a currently installed/activated PCC rule, including setting, modifying or deleting its deferred activation and/or deactivation time as follows: + +- 1) When modifying a PCC rule by newly setting the deferred activation time and/or deactivation time, the PCF shall update the PCC rule by including the corresponding ConditionData instance's "condId" attribute value within the "refCondData" attribute and including within the SmPolicyDecision data structure this ConditionData instance within the "conds" map attribute, if not previously provisioned. +- 2) When modifying a PCC rule by modifying the already provisioned deferred activation time and/or deactivation time: + - the PCF may update the PCC rule by replacing the existing ConditionData instance's "condId" attribute value within the "refCondData" attribute with a another one pointing to another ConditionData instance and including within the SmPolicyDecision data structure this new ConditionData instance within the "conds" attribute, if not previously provisioned; or + - the PCF may update the condition data decision to which the PCC rule refers by updating the corresponding ConditionData instance in the SmPolicyDecision data structure, as defined in clause 4.2.6.1. The PCF may add an activation time and/or a deactivation time, update the values of the existing activation time and/or deactivation time, or delete either the existing activation time or the existing deactivation time. +- 3) When modifying a PCC rule by deleting the previously provisioned deferred activation time and/or deactivation time: + - the PCF shall delete the reference to the corresponding ConditionData instance within the PCC rule by updating the "refCondData" attribute of the PCC rule to "NULL" value; and + - the PCF may also delete this condition data decision to which the PCC rule refers as defined in clause 4.2.6.1 (i.e. delete the corresponding ConditionData instance within the SmPolicyDecision data structure), if no other PCC rule is referring to this condition data decision. + +To delete a conditioned PCC rule, the PCF shall run the procedures as defined in clause 4.2.6.2.1. + +The UE timezone information, if available, may be used by the PCF to construct the values of the "activationTime" attribute and/or the "deactivationTime" attribute. + +The PCC rule(s) including a reference to a Condition Data decision which includes an "activationTime" attribute and/or a "deactivationTime" attribute shall be bound to a QoS flow associated with a default QoS rule that allows all UL packets. If such PCC rule(s) are not bound to a QoS flow associated with a default QoS rule, the SMF shall report a failure to the PCF by including the "ruleReports" attribute with the "failureCode" attribute set to the value "NO\_QOS\_FLOW\_BOUND" for the affected PCC rule(s). Changes of the QoS profile or QoS rule which will initiate signalling towards the access network and/or UE in such PCC rule(s) shall also not be applied. + +NOTE: This limitation prevents dependencies on the signalling of changed traffic mapping information towards the UE. + +#### 4.2.6.2.8 PCC rule for resource sharing + +If the ResShare feature is supported by both the SMF and PCF as described in clause 5.8, the PCF may indicate that the SMF should commonly reserve resources for a set of PCC rules. The SMF shall then, for PCC rules bound to the same QoS flow and the same sharing key value, use the highest GBR value among those PCC rules as input for calculating the common GBR value when reserving QoS flow resources. The GBR value for each direction shall be considered separately, so that the uplink and downlink GBR values may originate from different PCC rules. + +The SMF may, based on internal logic, use the highest MBR value among the provided PCC rules indicated to share resources, when determining the MBR for the QoS flow. Each individual PCC rule is still subject to data rate policing based on its own MBR values. + +The PCF shall provide the "sharingKeyDI" attribute and/or "sharingKeyUI" attribute within the QosData data structure which the PCC rules refers to in order to indicate that the related PCC rule may share resources with other PCC rules bound to the same QoS flow. + +The SMF shall apply resource sharing if at least two PCC rules bound to the same QoS flow share the same value in the "sharingKeyDI" attribute and/or "sharingKeyUI" attribute. + +When modifying the value of "sharingKeyDI" attribute and/or "sharingKeyUI" attribute of the QosData data structure, which a PCC rule refers to for the PCC rule that is subject to resource sharing the SMF may adjust the resource sharing of the remaining PCC rules. + +NOTE 1: A PCC rule that is deleted is also removed from the resource sharing, while the remaining PCC rules continue their sharing relationship. + +NOTE 2: The state of resource sharing ends when less than two of the PCC rules in the set remains. + +#### 4.2.6.2.9 Resource reservation for services sharing priority + +When the PCF derives PCC Rules corresponding to a service related to an AF that has indicated that priority sharing is allowed for that service over Rx interface or within the Npcf\_PolicyAuthorization service, it derives the corresponding PCC Rules according to current procedures as described in 3GPP TS 29.513 [7], clause 7.3. The PCF may additionally take the suggested pre-emption capability and vulnerability values into account if the AF provided them when the PCF determines the ARP pre-emption capability and vulnerability. The ARP derived at this point and the priority sharing indicator provided over Rx reference point (see 3GPP TS 29.214 [18] for further information) or over the Npcf\_PolicyAuthorization service (see 3GPP TS 29.514 [17] for further information) related to these derived PCC Rules are stored for later use. + +For PCC Rules related to the same PDU session with the same assigned 5QI and with the priority sharing indicator enabled (see 3GPP TS 29.214 [18], clause 4.4.8, or 3GPP TS 29.514 [17], clauses 4.2.2.21, 4.2.3.21 and 4.2.4.9), the PCF shall rederive the ARP into a shared ARP for these PCC Rules as follows: + +- The Priority Level shall be set to the lowest value (i.e. highest priority) among the Priority Level values derived for the PCC rules that include the priority sharing indicator. +- The Pre-emption Capability shall be set to true if any of the original derived PCC Rules have the Pre-emption Capability value set to true. +- The Pre-emption Vulnerability shall be set to true if all the original derived PCC Rules have the Pre-emption Vulnerability value set to true. + +NOTE 1: Having the same setting for the ARP parameter in the PCC Rules with the priority sharing indicator set enables the usage of the same QoS flow. Furthermore, a combined modification of the ARP parameter in the PCC rules ensures that a QoS flow modification is triggered when a media flow with higher service priority starts. + +If the 5QI and/or ARP related to any of the PCC Rules that share priority is changed (e.g. based on local policies), the PCF shall rederive the ARP for the impacted PCC Rules following the same procedure as defined in this clause. + +The PCF shall provision the PCC Rules according to the rederived ARP information as described in clause 4.2.6.2.1. + +If the PCF receives a report that a PCC rule provisioning or modification failed due to the resource reservation failure as defined in clauses 4.2.3.1.6 and 4.2.4.15 (PCC Rule Error Report) and if the PCF supports the MCPTT-Preemption feature as defined in clause 5.4.1 of 3GPP TS 29.214 [18] or in clause 5.8 of 3GPP TS 29.514 [17], the PCF shall check if pre-emption control based on the pre-emption control information provided by the AF as defined in clauses 4.4.1 or 4.4.2 of 3GPP TS 29.214 [18] or in clauses 4.2.2.21, 4.2.3.21 or 4.2.4.9 of 3GPP TS 29.514 [17] applies. + +NOTE 2: The PCF determines that pre-emption control applies based on the presence of the Pre-emption-Control-Info AVP received over Rx reference point as defined in 3GPP TS 29.214 [18] or "preemptControlInfo" attribute received over N5 reference point as defined in 3GPP TS 29.514 [17] and operator policies. + +If pre-emption control applies, the PCF shall check the corresponding derived PCC Rules (before applying priority sharing procedures). If the Pre-emption Capability of the derived PCC Rule is disabled the PCF shall notify that resource allocation has failed for this PCC rule to the AF as defined in clauses 4.4.1 or 4.4.2 of 3GPP TS 29.214 [18] or in clauses 4.2.2.21, 4.2.3.21 or 4.2.4.9 of 3GPP TS 29.514 [17]. Otherwise, if the Pre-emption Capability of the derived PCC Rule is enabled, the PCF shall perform the pre-emption control as follows: + +- For all the active PCC rule(s) that applied priority sharing mechanism, the PCF shall identify the PCC Rules that have the Pre-emption Vulnerability enabled. For those selected PCC Rule(s), the PCF shall check the Priority Level value. + +- If there is only one PCC Rule with the Priority Level value higher (i.e. lower priority) than the derived Priority Level value of new or modified PCC Rule, the PCF shall remove this PCC rule. The PCF shall retry the PCC rule provisioning or modification procedure for the PCC rule that failed. +- Otherwise, if there are more than one PCC Rule with the Priority Level value higher (i.e. lower priority) than the derived Priority Level value of new or modified PCC Rule, the PCF shall remove the PCC Rule with the highest Priority Level from the SMF. The PCF shall retry the PCC rule provisioning or modification procedure for the PCC rule that failed; If more than one PCC Rule have the same highest Priority Level, the PCF shall check the Pre-Emption-Control-Info AVP received over Rx interface as defined in 3GPP TS 29.214 [18], or the "preemptControlInfo" attribute received over N5 interface as defined in 3GPP TS 29.514 [17] and remove the PCC Rule that matches the condition. +- Otherwise, if there is at least one PCC Rule with the same Priority Level value than the derived Priority Level value of new or modified PCC Rule, the PCF shall check the Pre-emption-Control-Info AVP received over Rx interface as defined in 3GPP TS 29.214 [18] or the "preemptControlInfo" attribute received over N5 interface as defined in 3GPP TS 29.514 [17] for these PCC Rules and remove the PCC Rule that matches the condition. +- Otherwise, the PCF shall notify that resource allocation has failed for this PCC rule to the AF as defined in clauses 4.4.1 or 4.4.2 of 3GPP TS 29.214 [18] or in clauses 4.2.2.21 or 4.2.3.21 of 3GPP TS 29.514 [17]. + +If there is no active PCC Rule with the Pre-emption Vulnerability enabled, the PCF shall notify that resource allocation has failed for this PCC rule to the AF as defined in clauses 4.4.1 or 4.4.2 of 3GPP TS 29.214 [18]. + +NOTE 3: If the PCF receives a report that a PCC rule provisioning or modification failed due to the resource reservation failure and the PCF does not support the MCPTT-Preemption feature as defined in clause 5.4.1 of 3GPP TS 29.214 [18] or clause 5.8 of 3GPP TS 29.514 [17], the PCF can apply pre-emption and remove active PCC rules from the SMF and then retry the PCC rule provisioning or modification procedure. Otherwise, the PCF will notify it to the AF as defined in clauses 4.4.1 or 4.4.2 of 3GPP TS 29.214 [18] or in clauses 4.2.2.21 or 4.2.3.21 of 3GPP TS 29.514 [17]. How the PCF applies the pre-emption depends on the implementation. + +#### 4.2.6.2.10 PCC rule bound to the default QoS flow + +The PCF may indicate to the SMF that a PCC rule shall be bound to the default QoS flow and remain on the default QoS flow. The SMF shall then, for the indicated PCC rule, bind it to the default QoS flow until this PCC rule is removed or until the PCF modifies this PCC rule to set the "defQosFlowIndication" attribute to false. For this second case, the SMF shall evaluate the full QoS information within the QosData data structure to which the PCC rule refers and follow normal policy enforcement procedures for authorized QoS per service data flow as described in clause 4.2.6.2.3. + +NOTE: 5QI, ARP, QNC (if available), Priority Level (if available), Averaging Window (if available) and Maximum Data Burst Volume (if available) within the QoS Data decision referred by the PCC rule are only used by the SMF for QoS flow binding purposes when the "defQosFlowIndication" attribute is not included in the QoS Data decision or it is included and set to false. + +The PCF shall provide the "defQosFlowIndication" attribute set to true in order to indicate that the related PCC rule shall be bound to the default QoS flow. + +If the "defQosFlowIndication" attribute is provided and set to true within the QosData data structure to which the PCC rule refers, the SMF shall bind the related PCC rule to the default QoS flow. This binding remains valid until the related PCC rule is removed or if the PCF indicates to the SMF that the binding to the default QoS flow for this PCC rule no longer applies. + +The SMF shall ignore the values of the other attributes, including 5QI, ARP, QNC (if available), Priority Level (if available), Averaging Window (if available) and Maximum Data Burst Volume (if available), provided within the QosData data structure if the "defQosFlowIndication" attribute is provided by the PCF and set to true. If the PCF has previously indicated to the SMF that a PCC rule shall be bound to the default QoS flow, and desires to indicate that this binding no longer applies the PCF shall update this PCC rule by including the "defQosFlowIndication" attribute set to false. The SMF shall in this case evaluate the full QoS information within the QosData data structure to which the PCC rule refers and follow normal policy enforcement procedures for authorized QoS per service data flow as described in clause 4.2.6.2.3. + +If the PCF has not previously indicated to the SMF that a PCC rule shall be bound to the default QoS flow (i.e. it may be bound to another QoS flow), in order to indicate that the binding to the default QoS flow shall now apply for this PCC rule, the PCF shall update the PCC rule by including (or updating) the "defQosFlowIndication" attribute and set it to true. The SMF shall in this case follow the procedures described in this clause. + +#### 4.2.6.2.11 PCC rule for Application Detection and Control + +If the ADC feature is supported, the user subscription indicates that application detection and control is enabled, and the PCF determines that application detection is required because of e.g. an internal/external trigger or the PCF has received from an NF service consumer (e.g. another PCF or an AF) a subscription to the event for application start/stop traffic detection (see TS 29.514 [17], clause 4.2.6.9 subscription to application detection control and TS 29.523 [61], clause 4.2.2 for AF subscription to application detection control), the PCF may instruct the SMF to detect application(s) by installing or activating PCC rule(s). + +NOTE: When the NF service consumer is an AF, the PCF will identify all the affected PDU sessions based on the received information as specified in TS 29.523 [61] and generate the PCC Rules with instructions to detect application(s) for each affected PDU session. + +An application to be detected is identified by an application identifier, which shall be provided within the "appId" attribute for dynamic PCC rules or pre-provisioned for predefined PCC rules. If the PCF requires to be notified when application start/stop is detected, it shall also provide the APP\_STA and APP\_STO policy control request triggers to the SMF as defined in clause 4.2.4.6. For dynamic PCC rules, the PCF may also mute such notifications for a specific detected application by including a "traffContDecs" attribute to contain a Traffic Control Data decision which contains the "muteNotif" attribute set to true and including a "refTcData" attribute referring to this Traffic Control Data decision within the concerned PCC rule. + +If the application identifier provided in the "appId" attribute is invalid, unknown or not applicable, the SMF shall return a PCC Rule Error Report, as specified in clauses 4.2.3.16 and 4.2.4.15, and set the "failureCode" attribute to "APP\_ID\_ERR". + +The SMF shall reject the update of the mute indication for a provisioned PCC rule as specified in clause 4.2.3.16 and 4.2.4.15, and set the "failureCode" attribute to "MUTE\_CHG\_NOT\_ALLOWED". + +When the application detection control was initiated by an NF service consumer and it unsubscribes to receive these notifications, the PCF shall unsubscribe to the related policy control request triggers as described in clause 4.2.6.4 unless they are used for other purposes. + +In this release of the specification Application Detection and Control applies only to the IP PDU session type. + +#### 4.2.6.2.12 Provisioning of PCC Rules for Multimedia Priority Services + +##### 4.2.6.2.12.1 General + +The provision of PCC Rules corresponding to both MPS and non-MPS service shall be performed as described in clause 4.2.6.2.1 "Provisioning of PCC rules". + +When the PCF derives PCC Rules corresponding to MPS service, the ARP and 5QI shall be set as appropriate for the prioritized service, e.g. an IMS Multimedia Priority Service. The PCF may authorize a standardized 5QI or a standardized 5QI with a specific 5QI priority level as defined in clause 4.2.6.6.2. The PCF may also authorize a non-standardized 5QI with explicitly signalled QoS characteristics as defined in clause 4.2.6.6.3. + +When the PCF derives PCC Rules corresponding to non-MPS service, the PCF shall generate the PCC Rules as per normal procedures. At the time the Priority PDU connectivity services is invoked based on the subscription profile stored in the UDR (i.e. Indication for support of Priority PDU connectivity service and MPS Priority Level are set in the UDR) or by the AF (e.g., MPS for DTS is invoked as described in 3GPP TS 29.214 [18] and 3GPP TS 29.514 [17]), the PCF shall upgrade the ARP and/or change 5QI for the PCC Rules to appropriate values as needed for MPS. The PCF shall change the ARP and/or 5QI (also associated QoS characteristics if applicable) modified for the Priority PDU connectivity service to an appropriate value according to PCF decision. + +When the PCF receives an HTTP POST message as defined in clause 4.2.2.1, the PCF shall check whether any of these parameters is stored in the UDR: indication for support of Priority PDU connectivity service, MPS Priority Level and/or indication of IMS priority service support. The PCF shall derive the applicable PCC rules and default QoS flow QoS based on that information. If the indication of IMS priority service support is set and the "dnn" attribute corresponds to + +a DNN dedicated for IMS, the PCF shall assign an ARP corresponding to MPS for the default QoS flow and for the PCC Rules corresponding to the IMS signalling QoS flow. If the "dnn" does not correspond to a DNN dedicated for IMS, the ARP shall be derived without considering IMS Signalling Priority. + +NOTE 1: Subscription data for MPS is provided to PCF through the Nudr service. + +Once the PCF receives a notification of a change in Priority PDU connectivity services support, MPS Priority Level and/or IMS priority service support from the UDR, the PCF shall make the corresponding policy decisions (i.e. ARP and/or 5QI (also associated QoS characteristics if applicable) change) and, if applicable, shall initiate an HTTP POST message as defined in clause 4.2.3.2 to provision the modified data. + +NOTE 2: The details associated with the UDR service are specified in 3GPP TS 29.519 [15]. + +NOTE 3: The MPS Priority Level is one among other input data such as operator policy for the PCF to set the ARP. + +Whenever one or more AF sessions of an MPS service are active within the same PDU session, the PCF shall ensure that the ARP priority level of the default QoS flow is at least as high as the highest ARP priority level used by any authorized PCC rules belonging to an MPS service. If the ARP pre-emption capability is enabled for any of the authorized PCC rules belonging to an MPS service, the PCF shall also enable the ARP pre-emption capability for the default QoS Flow. + +NOTE 4: This ensures that services using dedicated QoS flows are not terminated because of a default QoS flow with a lower ARP priority level or disabled ARP pre-emption capability being dropped during mobility events. + +NOTE 5: This PCF capability does not cover interactions with services other than MPS services. + +#### 4.2.6.2.12.2 Invocation/Revocation of Priority PDU connectivity services + +When a Priority PDU connectivity services is invoked, the PCF shall: + +- Derive the corresponding PCC Rules with the ARP and 5QI (also associated QoS characteristics if applicable) set as appropriate for a prioritized service. +- Set the ARP of the default QoS flow as appropriate for a Priority PDU connectivity services under consideration of the requirement described in clause 4.2.6.2.12.1. +- Set the 5QI (also associated QoS characteristics if applicable) of the default QoS flow as appropriate for the Priority PDU connectivity services. +- Set the ARP of PCC Rules installed before the activation of the Priority PDU connectivity services to the ARP as appropriate for the Priority PDU connectivity services under the consideration of the requirements described in clause 4.2.6.2.12.1. +- Set the 5QI of the PCC Rules installed before the activation of the Priority PDU connectivity services to the 5QI (also associated QoS characteristics if applicable) as appropriate for the Priority PDU connectivity services if modification of the 5QI of the PCC Rules is required. + +When a Priority PDU connectivity services is revoked, the PCF shall: + +- Delete the PCC Rules corresponding to the Priority PDU connectivity services if they were previously provided. +- Set the ARP of the default QoS flow to the normal ARP under the consideration of the requirements described in clause 4.2.6.2.12.1. +- Set the 5QI of the default QoS flow as appropriate for PCF decision. +- Set the ARP of all active PCC Rules as appropriate for the PCF under the consideration of the requirements described in clause 4.2.6.2.12.1. +- Set the 5QI to an appropriate value according to PCF decision if modification of the 5QI of PCC Rules is required. + +NOTE: Priority PDU connectivity services can be explicitly invoked/revoked via UDR MPS user profile (Indication of Priority PDU connectivity services, MPS Priority Level). An AF for MPS Priority Service can also be used to provide Priority PDU connectivity services using network-initiated resource allocation procedures (via interaction with PCC) for originating accesses. + +The PCF shall provision the SMF with the applicable PCC Rules upon Priority PDU connectivity services activation and deactivation as described above. The provision of the QoS information applicable for the PCC Rules shall be performed as described in clause 4.5.6.2. The provision of QoS information for the default QoS flow shall be performed as described in clause 4.2.6.3. + +#### 4.2.6.2.12.3 Invocation/Revocation of IMS Multimedia Priority Services + +If the PCF receives service information including an MPS session indication and the service priority level from the P-CSCF or at reception of the indication that IMS priority service is active for the PDU session, the PCF shall under consideration of the requirements described in clause 4.2.6.2.12.1: + +- if required, set the ARP and 5QI (also associated QoS characteristics if applicable) of the default QoS flow as appropriate for the prioritized service; +- if required, set the ARP and 5QI (also associated QoS characteristics if applicable) of all PCC rules assigned to the IMS signalling QoS flow as appropriate for IMS Multimedia Priority Services; +- derive the PCC Rules corresponding to the IMS Multimedia Priority Service and set the ARP and 5QI (also associated QoS characteristics if applicable) of these PCC Rules based on the information received over N5/Rx. + +If the PCF detects that the P-CSCF released all the MPS session and the IMS priority service has been deactivated for the PDU session the PCF shall under consideration of the requirements described in clause 4.2.6.2.12.1: + +- delete the PCC Rules corresponding to the IMS Multimedia Priority Service; +- if required, set the ARP and 5QI of the default QoS flow as appropriate for the IMS Multimedia Priority set to inactive; +- replace the ARP and 5QI of all PCC Rules assigned to the IMS signalling QoS flow as appropriate when the IMS Multimedia Priority is inactive. + +#### 4.2.6.2.12.4 Invocation/Revocation of MPS for DTS + +When the PCF receives from the AF an indication of invocation/revocation of MPS for DTS as specified in 3GPP TS 29.514 [17] or 3GPP TS 29.214[10], and if the "MPSforDTS" feature is supported, the PCF shall make the corresponding policy decisions (i.e. ARP and/or 5QI change for the default QoS) and, if applicable, shall initiate an Npcf\_SMPolicyControl\_UpdateNotify to provision the modified data. + +For the invocation of MPS for DTS, the PCF shall: + +- Set the ARP of the default QoS flow as appropriate for MPS for DTS. +- Set the 5QI (also associated QoS characteristics if applicable) of the default QoS flow as appropriate for MPS for DTS. + +NOTE 1: For PCC Rules that had the same ARP and 5QI as the original default QoS flow: the PCF indicates to the SMF that the PCC rule is to be bound to the default QoS flow by setting the "defQosFlowIndication" attribute within the QosData data structure to true; or sets the ARP as appropriate for MPS for DTS and the 5QI (also associated QoS characteristics if applicable) as appropriate for MPS for DTS. + +For the revocation of MPS for DTS, to revert the MPS for DTS values of the default QoS flow and the PCC rules bound to the default QoS flow, the PCF shall set the ARP and the 5QI of the default QoS flow as appropriate for PCF decision. + +NOTE 2: For PCC Rules that had the same ARP and 5QI as the default QoS flow, or had the "defQosFlowIndication" attribute set to true: the PCF sets the ARP; and the 5QI (also associated QoS characteristics if applicable) as appropriate for PCF decision. The provision of the QoS information applicable for the PCC Rules is performed as described in clause 4.2.6.6. + +NOTE 3: Revocation may require more complex logic on the part of the PCF beyond simply restoring the prior ARP and 5QI values as set prior to invocation of MPS for DTS, if these values and/or the defQosFlowIndication were modified by another service during the time that MPS for DTS was enabled. The corresponding logic is dependent on the identification of particular services that may be deployed and the desired interactions between MPS for DTS and any such services. These aspects are not considered in the present specification. + +The PCF shall provision the SMF upon MPS for DTS invocation and revocation as described above for the default QoS flow as described in clause 4.2.3.6. + +On receipt from an AF of a request to report the successful outcome of the MPS for DTS invocation/revocation of priority handling for the default QoS flow (see 3GPP TS 29.214 [18] and 3GPP TS 29.514 [17]), the PCF shall request the SMF to confirm that the resources associated to the MPS for DTS invocation/revocation are successfully allocated. The PCF does this by setting the "policyCtrlReqTriggers" attribute in the "SmPolicyDecision" data structure to the value "SUCC\_QOS\_UPDATE". On receipt of the "repPolicyCtrlReqTriggers" attribute in the SmPolicyUpdateContextData data structure set to the value "SUCC\_QOS\_UPDATE" from the SMF, the PCF shall inform the AF that it successfully acted upon the "mpsAction" attribute as defined in 3GPP TS 29.514 [17] or the MPS-Action AVP as defined in 3GPP TS 29.214 [18]. + +The SMF shall report MPS for DTS invocation/revocation failure to the PCF according to clause 4.2.4.21 if requested to do so by the AF as described in 3GPP TS 29.214 [18], clause 4.4.11 or as described in 3GPP TS 29.514 [17], clause 4.2.2.12.2. + +#### 4.2.6.2.13 Sponsored Data Connectivity + +Sponsored data connectivity may be performed for service data flows associated with one or more PCC rules if the information about the sponsor, the application service provider and optionally the threshold values are provided by the AF and if the AF has not indicated to disable/not enable sponsored data connectivity as described in 3GPP TS 29.214 [18] clauses 4.4.1 and 4.4.2 or 3GPP TS 29.514 [17] clauses 4.2.2.5 and 4.2.3.5. + +The provisioning of sponsored data connectivity per PCC rule shall be performed using the PCC rule provisioning procedure as defined in clause 4.2.6.2.1. The sponsor identity shall be set using the "sponsorId" attribute within the ChargingData data type which the PCC rule refers to. The application service provider identity shall be set using the "appSvcProvId" attribute within the ChargingData data type which the PCC rule refers to. The "sponsorId" attribute and "appSvcProvId" shall be set if the "reportingLevel" attribute within the ChargingData data type which the PCC rule refers to is set to the value "SPON\_CON\_LEVEL". + +When receiving the usage thresholds from the AF, the PCF shall use the sponsor identity to generate a value of "umId" attribute of the UsageMonitoringData data type which the PCC rule refers to and request usage monitoring control for the sponsored data connectivity by following the procedures specified in clauses 4.2.6.2.5. + +When the AF disables sponsoring a service (See 3GPP TS 29.214 [18] clause 4.4.2 or 3GPP TS 29.514 [17] clause 4.2.3.5), the PCF + +- may modify the PCC rules in order to set the "reportingLevel" attribute to "SER\_ID\_LEVEL" or "RAT\_GR\_LEVEL" within the ChargingData data type which the PCC rule refers to and not include the "sponsorId" attribute and "appSvcProvId" attribute if they were included previously. +- may modify the PCC rules to update the charging key by setting the new value of the "ratingGroup" attribute within the ChargingData data type which the PCC rule refers to. + +NOTE: A specific charging key can be applied to the sponsored data connectivity for online charging. + +- shall disable the usage monitoring for the sponsored data connectivity according to clause 4.2.6.2.5 if it was enabled previously. As a result, PCF gets the accumulated usage of the sponsored data connectivity. + +#### 4.2.6.2.14 Support for PCC rule versioning + +The support of PCC rule versioning is optional. When the "RuleVersioning" feature is supported, the SMF and the PCF shall comply with the procedures specified in this clause. + +If required by operator policies, the PCF shall assign a content version for each generated PCC rule and shall include the assigned version in the "contVer" attribute included within the PccRule data structure. Upon each PCC rule + +modification, if the content version was previously assigned to a PCC rule, the PCF shall assign a new content version. In this case, all the content related to that PCC rule shall be included. If the PCF needs to modify the attribute(s) within the PCC rule, the PCF shall include the new content version within the "contVer" attribute together with all modified and unmodified applicable attribute(s) within the PccRule data structure. If the PCF only needs to modify the content of referenced policy decision data and/or condition data for one or more PCC rules, the PCF shall additionally provide the PCC rule(s) which is referring to the modified policy decision data and/or condition data. Within each PCC rule instance, the PCF shall include all unmodified applicable attribute(s) and the new assigned version in the "contVer" attribute. The content version is unique for the lifetime of the PCC rule. + +NOTE 1: The PCF will include all the content of the PCC rule in each modification of the PCC rule in order to ensure that the rule is installed with the proper information regardless of the outcome of the QoS flow procedure related to previous rule provisioning versions that are not reported yet. + +NOTE 2: The operation policies can take into account whether the AF provides the related content version information over Rx reference point (see clause 4.4.9 in 3GPP TS 29.214 [18]), or over Npcf\_PolicyAuthorization service (see clauses 4.2.2.13 and 4.2.3.13 in 3GPP TS 29.514 [17]). + +Whenever the SMF provides a PCC rule report for rules that were provisioned with a content version, the SMF shall include the "contVers" attribute defined in the RuleReport data structure for those corresponding PCC rules. In case it is required to report the content version of multiple PCC rules, the SMF shall use one instance of RuleReport data structure per PCC rule, and shall include in the "pccRuleIds" attribute only the identifier of the corresponding PCC rule. The SMF may include more than one content version in the "contVers" attribute for the same PCC rule within the corresponding RuleReport instance included in the "ruleReports" attribute (e.g. the SMF has combined multiple PCC rule versions enforcement into one QoS flow operation). In this case, the "ruleStatus" attribute shall indicate the final status of the PCC rule. + +NOTE 3: The PCF will use the content version to identify the PCC rule version that failed or succeeded when multiple provisions of the same PCC rule occur in a short period of time. If required by the AF, the PCF will inform the AF according to 3GPP TS 29.214 [18], clause 4.4.9, or according to 3GPP TS 29.514 [17], clause 4.2.5.8 about the failure or success for the media component version associated to the PCC rule version. + +#### 4.2.6.2.15 Background data transfer support + +If the PCF receives Reference Id within the service information from the AF as defined in 3GPP TS 29.514 [17] or 3GPP TS 29.214 [18] or if "EnhancedBackgroundDataTransfer" feature as defined in clause 5.8 is supported and the PCF receives the Reference Id(s) within the PDU session related subscription information from the UDR as defined in 3GPP TS 29.519 [15], the PCF shall retrieve the corresponding transfer policy from the UDR based on the Reference Id(s) as defined in 3GPP TS 29.519 [15]. The PCF shall use the retrieved transfer policy as input for policy decisions (e.g. setting the charging key equal to the charging key of the transfer policy, rule activation/deactivation time according to the time window). + +During PDU session establishment, if "EnhancedBackgroundDataTransfer" feature as defined in clause 5.8 is supported and if validation conditions (i.e. Time Window and/or Location Criteria) of the transfer policy are not satisfied then the PCF may reject corresponding SM Policy Association as defined in clause 4.2.2.2 and include in an HTTP "403 Forbidden" response message the "cause" attribute of the ProblemDetails data structure set to "VALIDATION\_CONDITION\_NOT\_MET". And based on this feedback, the SMF shall reject the PDU session setup. + +After successful PDU session establishment, if "EnhancedBackgroundDataTransfer" feature as defined in clause 5.8 is supported, PCF may request the PDU session termination if the validation conditions become not satisfied as defined in clause 4.2.3.3. Within the TerminationNotification, the PCF shall include the "cause" attribute set to "VALIDATION\_CONDITION\_NOT\_MET". + +If "BDTPolicyRenegotiation" feature as defined in clause 5.8 is supported and if the PCF retrieves the BDT policy and corresponding related information (e.g. network area information, the volume of data to be transferred per UE, etc.) within the BdtData data type, and with the "bdtpStatus" attribute within the BdtData data type set to value "INVALID", the PCF may reject the SM Policy Association establishment or defer to make the policy decisions until the PCF is informed of the result of BDT policy re-negotiation finally. If the PCF determines to reject the SM Policy Association establishment based on the invalid BDT policy, the PCF shall include in an HTTP "403 Forbidden" response message the "cause" attribute of the ProblemDetails data structure set to "INVALID\_BDT\_POLICY". If the PCF defers to make the policy decisions, then based on the result of the BDT policy renegotiation, the PCF may make the policy decisions or terminate the SM Policy Association as defined in this clause. + +#### 4.2.6.2.16 Number of supported packet filter for signalled QoS rule limitation support + +If the PCF includes the flow information within the "flowInfos" attribute and if the number of supported packet filter for signalled QoS rules within the "numOfPackFilter" attribute is received from the SMF during the PDU session establishment, the PCF shall ensure that for all the dynamic PCC rules of a PDU session, the number of packet filters contained within the "flowDescription" attribute or the "ethFlowDescription" attribute with the "packetFilterUsage" set to true does not exceed the value of the "numOfPackFilter" attribute. + +NOTE: The maximum number of packet filters sent to the UE per QoS rule is additionally limited by the access type. When the UE is camping in 5GS the number of packet filters is limited as specified in 3GPP TS 24.501[20]. + +If the PCF determines that there is a possibility to run into a restriction regarding the number of TFT packet filters that can be allocated for the PDU Session, interworking with N26 deployment is supported and "PackFiltAllocPrecedence" feature is supported, the PCF may behave as described in Annex B.3.2.0, B.3.3.0 and B.3.4.0. + +#### 4.2.6.2.17 Access traffic steering, switching and splitting support + +If both the SMF and the PCF support the "ATSSS" feature as defined in clause 5.8, the PCF may enable the control of traffic steering, switching and splitting for a detected service data flow by including MA PDU Session control information within the PCC rule. In order to do so, within the PccRule data structure the PCF: + +- may include one reference to the ChargingData data structure within the "refChgN3gData" attribute if the PCF determines that the specific charging parameters used for packets carried via Non-3GPP access. In this case, a "chgDecs" attribute containing the corresponding Charging Data policy decisions shall be included in the SmPolicyDecision data structure if it has not been provided; +- may include one reference to the UsageMonitoringData data structure within the "refUmN3gData" attribute if the PCF determines that the specific usage monitoring parameters used for packets carried via Non-3GPP access. In this case, a "umDecs" attribute containing the corresponding Usage Monitoring Data policy decisions shall be included in the SmPolicyDecision data structure if it has not been provided; +- may include the ATSSS rule application descriptor within "appDescriptor" attribute if the SDF template included in the PCC rule contains an Application Identifier in the "appId" attribute (see clause 4.2.6.2.1). The PCF may retrieve the OS Id(s) from the "UEPolicySet" resource in the UDR as described in 3GPP TS 29.519 [15] to determine, by internal configuration, the OS Application Identifier supported by the OS Id that corresponds to the application identifier included in the SDF template. If no OS Id is available in the UDR, the PCF may use the PEI to determine the OS Id supported by the UE; + +NOTE 1: If the PCF does not take into account the received PEI and/or the retrieved OSId(s) to derive the application descriptor, then the PCF can include in the PCC rule multiple application descriptors associated to multiple operating systems. + +NOTE 2: If only one UE OSId is stored in the UDR and the PCF takes it into account to derive the application descriptor, then the PCF can omit the OS Id in the application descriptor included in the PCC rule. + +- may include the ATSSS policies within the Traffic Control Data decision which the PCC rule refers to. Within the TrafficControlData data structure, based on the ATSSS capability supported for the MA PDU Session, the PCF shall include: + - the applicable access traffic steering method, "ATSSS\_LL", "MPTCP" or, if the EnATSSS\_v2 feature is supported, "MPQUIC", for the UL and DL traffic, encoded in the "steerFun" attribute; and + +NOTE: When the feature EnATSSS\_v2 is supported, the ATSSS-LL functionality is not supported together with the "REDUNDANT" steering mode. When the UE indicates it supports the ATSSS-LL functionality with any steering mode, it is implied that the UE supports the ATSSS-LL functionality with any steering mode except the "REDUNDANT" steering mode. + +- the steering rule for access traffic distribution across the 3GPP and Non-3GPP accesses encoded in a "SteeringMode" data structure within the "steerModeDI" attribute for the DL traffic and within the "steerModeUI" attribute for the UL traffic. + +The "SteeringMode" data structure shall include: + +- the steering mode value determined by the PCF within the "steerModeValue" attribute as follows: + - a. "ACTIVE\_STANDBY" indicates the traffic of a SDF is steered on one access (the Active access), when this access is available, and switched to the other access (the Standby access), when Active access becomes unavailable. When the Active access becomes available again, the SDF is switched back to this access. If the Standby access is not defined, then the SDF is only allowed on the Active access and cannot be transferred on another access. + - b. "LOAD\_BALANCING" indicates that the traffic of an SDF is split percentually between the 3GPP and Non-3GPP accesses. + - c. "SMALLEST\_DELAY" indicates that the traffic of an SDF is steered and/or switched to the access that has the smallest delay (e.g. smallest RTT). + - d. "PRIORITY\_BASED" indicates that the traffic of an SDF is steered to the high priority access until the access is determined to be congested. In this case, the traffic of the SDF is also sent to the low priority access, i.e. the SDF traffic is split over the two accesses. When the high priority access becomes unavailable, all SDF traffic is switched to the low priority access. How UE and UPF determine when a congestion occurs on an access is implementation dependent. + - e. If both the SMF and the PCF support the "EnATSSS\_v2" feature, "REDUNDANT" indicates that the traffic of an SDF may be duplicated on the 3GPP and Non-3GPP accesses. +- When the access traffic steering mode in the "steerModeValue" attribute is "ACTIVE\_STANDBY", the active access encoded within the "active" attribute, and the standby access, if defined, in the "standby" attribute; or +- When the access traffic steering mode in the "steerModeValue" attribute is "LOAD\_BALANCING", the traffic load distributed across 3GPP and Non-3GPP accesses encoded within the "3gLoad" attribute as the 3GPP access traffic weight percentage. The sum of the Non-3GPP access traffic weight percentage and the 3GPP access traffic weight percentage must be 100; or +- When the access traffic steering mode in the "steerModeValue" attribute is "PRIORITY\_BASED", the high priority access type encoded within the "prioAcc" attribute. + +If the EnATSSS\_v2 feature is supported, when the access traffic steering mode in the "steerModeValue" attribute is "REDUNDANT", the "SteeringMode" data structure may include the primary access encoded within the "primary" attribute. + +If the EnATSSS feature is supported, the PCF may provide either the steering mode indicator or the authorized threshold values for RTT and/or Packet Loss Rate within the "SteeringMode" data structure as follows: + +- a. when the access traffic steering mode within the "steerModeValue" attribute is "LOAD\_BALANCING" with fixed split percentages or "PRIORITY\_BASED" or, when the EnATSSS\_v2 feature is supported, "REDUNDANT", the PCF may provide, within the "thresValue" attribute, the authorized threshold value of RTT encoded in the "rttThres" attribute and/or the authorized threshold value of Packet Loss Rate encoded in the "plrThres" attribute. + - For "LOAD\_BALANCING" steering mode with fixed split percentages (i.e., without the "AUTO\_LOAD\_BALANCE" or "UE\_ASSISTANCE" steering mode indicator), the traffic load distributed across accesses indicated in "3gLoad" attribute shall only apply when the measurement of RTT and/or Packet Loss Rate on both accesses do not exceed the values for RTT and/or Packet Loss Rate provided respectively in the "rttThres" and/or "plrThres" attributes. When at least one measured parameter on one access exceeds the provided threshold value, the UE and UPF may stop sending traffic on this access, or may continue sending traffic on this access, but should reduce the traffic on this access and shall send the amount of reduced traffic on the other access. How UE and UPF adjust the traffic load distributed across accesses is implementation dependent. + - For "PRIORITY\_BASED" steering mode, when the measurement of RTT and/or Packet Loss Rate on the high priority access type exceeds the values for RTT and/or Packet Loss Rate provided respectively in the "rttThres" and/or "plrThres" attributes, this access may be considered as congested by the UE and the UPF. In this case, the traffic of the SDF is also sent to the low priority access. + - For "REDUNDANT" steering mode, and when the feature EnATSSS\_v2 is supported: + +- i. When a threshold value is not provided (i.e., when RTT and Packet Loss Rate are not provided), the traffic of an SDF is duplicated on both accesses if both accesses are available. If a primary access is provided, the UE and the UPF send all data packets of the SDF on the primary access and may duplicate data packets of the SDF on the other access. If a primary access is not provided to the UE and UPF, the UE and UPF send all data packets of the SDF on both accesses. + - ii. When a threshold value is provided, the duplication of the traffic of the SDF, by the UE and UPF, on both accesses shall only apply when the measurement of RTT or Packet Loss Rate on both accesses exceeds the values for RTT or Packet Loss Rate provided respectively in the "rttThres" or "plrThres" attributes. When the measured parameter (i.e., either RTT or Packet Loss Rate) exceeds the provided threshold value on one access only, the UE and UPF shall send the traffic of the SDF only over the other access. When the measured parameter (i.e., either RTT or Packet Loss Rate) does not exceed the provided threshold value on any access, the UE and UPF shall send the traffic of the SDF only over the primary access. If the primary access is not provided to the UE and UPF, UE and UPF select a primary access based on their own implementation (e.g., using the lowest RTT access or the lowest Packet Loss Rate access). If measurement results on an access are not available for a parameter, it is considered that the measured parameter for this access has not exceeded the provided threshold value. When a threshold value is provided, the "REDUNDANT" steering mode is only used for Non-GBR SDF. +- b. when the access traffic steering mode in the "steerModeValue" attribute is "LOAD\_BALANCING", the PCF may provide within the "steerModeInd" attribute: +- "AUTO\_LOAD\_BALANCE", when the UE and UPF are allowed to autonomously determine the traffic load of an SDF distributed across accesses; or + - "UE\_ASSISTANCE", when the UE is allowed to decide how to distribute the UL traffic of an SDF and the UE may inform the UPF how it decided to distribute the UL traffic. In the normal cases, although with this indicator provided, the UE shall apply the Steering Mode provided by the network. + +When the "steerModeInd" attribute is provided, the traffic load distributed across accesses indicated in "3gLoad" attribute may be ignored by the UE and UPF. + +If the value of "atsssCapab" attribute received from the SMF is "MPTCP\_ATSSS\_LL\_WITH\_EXSDMODE\_DL\_ASMODE\_UL", "MPQUIC\_ATSSS\_LL\_WITH\_EXSDMODE\_DL\_ASMODE\_UL" or "MPTCP\_MPQUIC\_ATSSS\_LL\_WITH\_EXSDMODE\_DL\_ASMODE\_UL", the PCF shall provide a PCC Rule for non-MPTCP/non-MPQUIC traffic. To enable non-MPTCP traffic/non-MPQUIC, the PCF shall include a "match all" packet filter within the "flowInfos" attribute, the highest value within the "precedence" attribute of the PCC rule, and within the TrafficControlData data structure referred by the PCC rule, set the "steerFun" attribute to the "ATSSS\_LL", the "steerModeValue" attribute of the "steerModeUI" attribute to "ACTIVE\_STANDBY", and the "steerModeValue" attribute of the "steerModeDI" attribute to any supported steering mode except the "SMALLEST\_DELAY" and, when the EnATSSS\_v2 feature is supported, "REDUNDANT" steering mode. How PCF assigns precedence value in packet filters for MPTCP and MPQUIC traffic, when both are supported, is implementation dependant. + +If the value of "atsssCapab" received from the SMF is "MPTCP\_ATSSS\_LL\_WITH\_ASMODE\_UL", "MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_UL" or "MPTCP\_MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_UL", the PCF shall provide a PCC rule for non-MPTCP/non-MPQUIC traffic. To enable non-MPTCP/non-MPQUIC traffic, the PCF shall include a "match all" packet filter within the "flowInfos" attribute, the highest value within the "precedence" attribute of the PCC rule, and within the TrafficControlData data structure referred by the PCC rule, set the "steerFun" attribute to the "ATSSS\_LL", the "steerModeValue" attribute of the "steerModeUI" attribute to "ACTIVE\_STANDBY", and the "steerModeValue" attribute of the "steerModeDI" attribute to any supported steering mode except, when the feature EnATSSS\_v2 is supported, the "REDUNDANT" steering mode. How PCF assigns precedence value in packet filters for MPTCP and MPQUIC traffic, when both are supported, is implementation dependant. + +If the value of "atsssCapab" received from the SMF is "MPTCP\_ATSSS\_LL\_WITH\_ASMODE\_DLUL", "MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_DLUL" or "MPTCP\_MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_DLUL", the PCF shall provide a PCC rule for non-MPTCP/non-MPQUIC traffic. To enable non-MPTCP/non-MPQUIC traffic, the PCF shall include a "match all" packet filter within the "flowInfos" attribute, the highest value within the "precedence" attribute of the PCC rule, and within the TrafficControlData data structure referred by the PCC rule, set the "steerFun" attribute to the "ATSSS\_LL", the "steerModeValue" attribute of the "steerModeUI" attribute and the "steerModeDI" attribute to "ACTIVE\_STANDBY". How PCF assigns precedence value in packet filters for MPTCP and MPQUIC traffic, when both are supported, is implementation dependant. + +If the value of "atsssCapab" received from the SMF is "MPTCP\_ATSSS\_LL", "MPQUIC\_ATSSS\_LL" or "MPTCP\_MPQUIC\_ATSSS\_LL", the PCF shall provide a PCC rule for non-MPTCP/non-MPQUIC traffic. To enable non-MPTCP/non-MPQUIC traffic, the PCF may include a "match all" packet filter within the "flowInfos" attribute, the highest value within the "precedence" attribute of the PCC rule, and within the TrafficControlData data structure referred by the PCC rule, set the "steerFun" attribute to the "ATSSS\_LL", the "steerModeValue" attribute of the "steerModeUI" attribute and the "steerModeDI" attribute to any supported steering mode except, when the feature EnATSSS\_v2 is supported, the "REDUNDANT" steering mode. How PCF assigns precedence value in packet filters for MPTCP and MPQUIC traffic, when both are supported, is implementation dependant. + +Upon receipt of the PCC rule with the MA PDU Session control information, the SMF shall: + +- derive the ATSSS rules to deliver to the UE for UL traffic steering as defined in 3GPP TS 29.502 [22]. When the EnATSSS feature is supported and the SMF received for UL traffic steering either the steering mode indicator within the "steerModeInd" attribute or the threshold value(s) within the "thresValue" attribute, the SMF includes the received steering mode indication or the received threshold value(s) in the derived ATSSS Rule sent to the UE as defined in 3GPP TS 29.502 [22]. When the EnATSSS\_v2 feature is supported and the SMF received the primary access within the "primary" attribute, the SMF includes the received primary access in the derived ATSSS Rule sent to the UE as defined in 3GPP TS 29.502 [22]; + +NOTE 3: The Traffic Descriptor in the ATSSS rule is generated by the SMF from the SDF template of the PCC rule. If the PccRule data structure contains the "flowInfos" attribute, the SMF uses the UL SDF filters for the generation of the IP descriptors or Non-IP descriptors. If the PccRule data structure contains the "appId" attribute, the SMF includes the application descriptors received from the PCF in the "appDescriptor" attribute of the PCC rule. + +- derive the QoS profile and provide it to the access network(s) as follows: + - for a Non-GBR QoS flow, + - a) the SMF shall provide the QoS profile to both access networks if the UE is registered over both accesses during MA PDU Session Establishment procedure; + - b) the SMF shall provide the QoS profile to the access networks over which the user plane resources are activated during MA PDU Session Modification procedure. + - for a GBR QoS flow, + - a) if the Multi Access policies of the PCC rule indicate the GBR SDF is handled only in one access (i.e. , the SMF shall provide the QoS profile to the access network indicated by the PCC rule; + - b) if the Multi Access policies of the PCC rule indicate the GBR SDF is handled in both accesses, the SMF shall decide to which access network to provide the QoS profile for the GBR SDF based on its local policy (e.g. the local policy is configured the access where the traffic is ongoing according to the Multi Access policies of the PCC rule). + - c) for a GBR QoS flow, traffic splitting is not supported because the QoS profile is provided to a single access network at a given time, and the traffic can be steered or switched as indicated by the "ACTIVE\_STANDBY" steering mode. If the SMF receives the report that the current active access is not available from the UPF, the SMF shall perform as follows: + - if the corresponding PCC rule allows the GBR QoS flow only on this access or if the corresponding PCC rule allows the GBR QoS flow on both accesses but the other access is not available, the SMF shall release the resources for the GBR QoS flow and report to the PCF about the removal of the PCC rule as defined in clause 4.2.4.15. + - if the corresponding PCC rule allows the GBR QoS flow on both accesses and the other access is available, the SMF shall try to move the GBR QoS flow to the other access. The SMF may trigger a PDU session modification procedure to provide the QoS profile to the other access and release the resources for the GBR QoS flow in the current access. + - if the QoS notification control is not enabled for the corresponding PCC rule and the other access does not accept the QoS profile, the SMF shall release the resources for the GBR QoS flow and report to the PCF about the removal of the PCC rule as defined in clause 4.2.4.15. + +- if the QoS notification control is enabled for the corresponding PCC rule, the SMF shall notify the PCF within the "qncReports" attribute that the QoS targets of the SDFs are not guaranteed. After the other access accepts the QoS profile, the SMF shall notify the PCF within the "qncReports" attribute that the QoS targets of the SDFs are guaranteed again. If the other access does not accept the QoS profile, the SMF shall delete the GBR QoS flow and report to the PCF about the removal of the PCC rule as defined in clause 4.2.4.15. +- instruct the UPF for DL access traffic steering as defined in 3GPP TS 29.244 [13]. When the EnATSSS feature is supported and the SMF received for DL traffic steering either the steering mode indicator within the "steerModeInd" attribute or the threshold value(s) within the "thresValue" attribute, the SMF includes the received steering mode indication or the received threshold value(s) in the derived the multi-access rule sent to the UPF as defined in 3GPP TS 29.244 [13]. When the EnATSSS\_v2 feature is supported and the SMF received the primary access within the "primary" attribute, the SMF includes the received primary access in the derived multi-access rule sent to the UPF as defined in 3GPP TS 29.244 [13]; +- apply charging information depending on the used access type if indicated in the PCC rule; and +- apply usage monitoring control depending on the used access type if indicated in the PCC rule. + +The PCF may update the steering rule for access traffic distribution across the 3GPP and Non-3GPP accesses for a PCC rule. In order to do so, the PCF may: + +- within the corresponding PccRule data structure, include a new reference of a Traffic Control Data decision and provide the Traffic Control Data decision if not provided yet. +- update the Traffic Control Data decision by including the appropriate attribute value(s) within the "steerFun" attribute, "steerModeDI" attribute and/or "steerModeUI" attribute. + +#### 4.2.6.2.18 Void + +#### 4.2.6.2.19 Provisioning of PCC Rules for Mission Critical Services + +##### 4.2.6.2.19.1 General + +The provision of PCC Rules corresponding to both MCS and non-MCS service shall be performed as described in clause 4.2.6.2.1 "Provisioning of PCC rules". + +When the PCF derives PCC Rules corresponding to MCS service, the ARP and 5QI shall be set as appropriate for the prioritized service, e.g. an IMS Mission Critical Service. The PCF may authorize a standardized 5QI or a standardized 5QI with a specific 5QI priority level as defined in clause 4.2.6.6.2. The PCF may also authorize a non-standardized 5QI with explicitly signalled QoS characteristics as defined in clause 4.2.6.6.3. + +At the time the Priority PDU connectivity services is invoked (i.e. Indication for support of priority PDU connectivity service and MCS Priority Level are set), the PCF shall upgrade the ARP and/or change 5QI for the PCC Rules to appropriate values as needed for MCS. The PCF shall change the ARP and/or 5QI (also associated QoS characteristics if applicable) modified for the priority PDU connectivity service to an appropriate value according to PCF decision. + +When the PCF receives an HTTP POST message as defined in clause 4.2.2.1, the PCF shall check whether any of these parameters is stored in the UDR: indication for support of priority PDU connectivity service, indication for support of MCS Priority Level. The PCF shall derive the applicable PCC rules and default QoS flow QoS based on that information. If the indication of IMS priority service support is set and the "dnn" attribute corresponds to a DNN dedicated for IMS, the PCF shall assign an ARP corresponding to MCS for the default QoS flow and for the PCC Rules corresponding to the IMS signalling QoS flow. If the "dnn" does not correspond to a DNN dedicated for IMS, the ARP shall be derived without considering IMS Signalling Priority. + +NOTE 1: Subscription data for MCS is provided to the PCF through the Nudr service. + +Once the PCF receives a notification of a change in Priority PDU connectivity services support, MCS Priority Level and/or IMS priority service support from the UDR, the PCF shall make the corresponding policy decisions (i.e. ARP and/or 5QI (also associated QoS characteristics if applicable) change) and, if applicable, shall initiate an HTTP POST message as defined in clause 4.2.3.2 to provision the modified data. + +NOTE 2: The details associated with the UDR service are specified in 3GPP TS 29.519 [15]. + +NOTE 3: The MCS Priority Level is one among other input data such as operator policy for the PCF to set the ARP. + +Whenever one or more AF sessions of an MCS service are active within the same PDU session, the PCF shall ensure that the ARP priority level of the default QoS flow is at least as high as the highest ARP priority level used by any authorized PCC rules belonging to an MCS service. If the ARP pre-emption capability is enabled for any of the authorized PCC rules belonging to an MCS service, the PCF shall also enable the ARP pre-emption capability for the default QoS Flow. + +NOTE 4: This ensures that services using dedicated QoS flows are not terminated because of a default QoS flow with a lower ARP priority level or disabled ARP pre-emption capability being dropped during mobility events. + +NOTE 5: This PCF capability does not cover interactions with services other than MCS services. + +#### 4.2.6.2.19.2 Invocation/Revocation of Priority PDU connectivity services + +When a Priority PDU connectivity services is invoked, the PCF shall: + +- Derive the corresponding PCC Rules with the ARP and 5QI (also associated QoS characteristics if applicable) set as appropriate for a prioritized service. +- Set the ARP of the default QoS flow as appropriate for a Priority PDU connectivity services under consideration of the requirement described in clause 4.2.6.2.19.1. +- Set the 5QI (also associated QoS characteristics if applicable) of the default QoS flow as appropriate for the Priority PDU connectivity services. +- Set the ARP of PCC Rules installed before the activation of the Priority PDU connectivity services to the ARP as appropriate for the Priority PDU connectivity services under the consideration of the requirements described in clause 4.2.6.2.19.1. +- Set the 5QI of the PCC Rules installed before the activation of the Priority PDU connectivity services to the 5QI (also associated QoS characteristics if applicable) as appropriate for the Priority PDU connectivity services if modification of the 5QI of the PCC Rules is required. + +When a Priority PDU connectivity services is revoked, the PCF shall: + +- Delete the PCC Rules corresponding to the Priority PDU connectivity services if they were previously provided. +- Set the ARP of the default QoS flow to the normal ARP under the consideration of the requirements described in clause 4.2.6.2.19.1. +- Set the 5QI of the default QoS flow as appropriate for PCF decision. +- Set the ARP of all active PCC Rules as appropriate for the PCF under the consideration of the requirements described in clause 4.2.6.2.19.1. +- Set the 5QI to an appropriate value according to PCF decision if modification of the 5QI of PCC Rules is required. + +NOTE: Priority PDU connectivity services can be explicitly invoked/revoked via UDR MCS user profile (Indication of Priority PDU connectivity services, MCS Priority Level). An AF for MCS Priority Service can also be used to provide Priority PDU connectivity services using network-initiated resource allocation procedures (via interaction with PCC) for originating accesses. + +The PCF shall provision the SMF with the applicable PCC Rules upon Priority PDU connectivity services activation and deactivation as described above. The provision of the QoS information applicable for the PCC Rules shall be performed as described in clause 4.5.6.2. The provision of QoS information for the default QoS flow shall be performed as described in clause 4.2.6.3. + +#### 4.2.6.2.19.3 Invocation/Revocation of IMS Mission Critical Services + +If the PCF receives service information including an MCS session indication and the service priority level from the P-CSCF or at reception of the indication that IMS priority service is active for the PDU session, the PCF shall under consideration of the requirements described in clause 4.2.6.2.19.1: + +- if required, set the ARP and 5QI (also associated QoS characteristics if applicable) of the default QoS flow as appropriate for the prioritized service; +- if required, set the ARP and 5QI (also associated QoS characteristics if applicable) of all PCC rules assigned to the IMS signalling QoS flow as appropriate for IMS Mission Critical Services; +- derive the PCC Rules corresponding to the IMS Mission Critical Service and set the ARP and 5QI (also associated QoS characteristics if applicable) of these PCC Rules based on the information received over N5/Rx. + +If the PCF detects that the P-CSCF released all the MCS session and the IMS priority service has been deactivated for the PDU session the PCF shall under consideration of the requirements described in clause 4.2.6.2.19.1: + +- delete the PCC Rules corresponding to the IMS Mission Critical Service; +- if required, set the ARP and 5QI of the default QoS flow as appropriate for the IMS Mission Critical set to inactive; +- replace the ARP and 5QI of all PCC Rules assigned to the IMS signalling QoS flow as appropriate when the IMS Mission Critical Service is inactive. + +#### 4.2.6.2.20 PCC rules authorization with preliminary service information + +If the PCF receives a request for PCC rules for a PDU session from the SMF, while no suitable authorized PCC rules are configured in the PCF or can be derived from service information provisioned by an AF, but the user is allowed to access AF session based services, the PCF may, depending e.g. on the user's subscription details or operator policy, authorise the requested QoS for a timer supervised grace period (the timer started by the PCF by the request from the SMF) to wait for AF service information. If an AF session bound to the same PDU session is ongoing and only preliminary service information was received within this AF session, the PCF shall base the authorization of the requested QoS on the preliminary service information. + +NOTE 1: This scenario can for instance be encountered for a UE terminated IMS session establishment or modification with UE initiated resource reservation, refer to 3GPP TS 29.214 [18] or 3GPP TS 29.514 [17]. If the PCF does not authorize a request for PCC rules in this scenario, the IMS session setup can fail. + +NOTE 2: During the grace period, the QoS and packet filters requested by the UE need to be authorized even if the user is not allowed to request for resources for services not known to the PCF or if the requested 5QI is not allowed for services not known to the PCF as it is not clear at this point in time whether the UE resource request belongs to an AF session or to a service not known to the PCF. + +If the preliminary service information is insufficient to construct appropriate PCC rules or no preliminary service information is available, the PCF shall provide preliminary PCC rules to authorize the UE requested QoS and packet filters. Therefore, the preliminary PCC rules shall contain wildcarded flow description or flow description derived from possible packet filters received as part of the request for PCC rules. The PCF may apply a dedicated charging key value to indicate to the charging subsystem that the charging key is preliminary and may be corrected later on. + +NOTE 3: With the dedicated charging key, the PCF instructs the charging subsystem to recalculate the applicable charge for the time when the dedicated charging key value was applied once the dedicated charging key value is replaced with some other value in a new provisioning of PCC rules. For example, if online charging applies, Session Charging with Unit Reservation (SCUR) can be used. When the charging key changes, the SMF will return initially reserved credit units and the CHF then can recalculate the consumed credit units applying the rate derived from the new other charging key value and update the user's credit accordingly. + +NOTE 4: A preliminary PCC rule is a normal PCC rule containing preliminary information. + +If the PCF receives AF service information while the timer-supervised grace period is running, the PCF shall stop the timer and may derive authorized PCC rules from this service information and update or replace the preliminary PCC + +rules that were previously provided for the UE requested QoS and packet filters, for instance by choosing service specific QoS parameters and charging keys. + +NOTE 5: The dedicated preliminary charging key value that was previously provided by the PCF instructs the charging subsystem to recalculate the applicable charge when the new service specific charging key is provided. The recalculation covers the time when the previous dedicated charging key value was active. The new service specific charging key is applied from that time onwards. + +If the timer expires and the PCF has not received any AF service information, the PCF should apply the policy for services not known to the PCF and may downgrade or revoke the authorization for the preliminary PCC rules (previously provided for the UE requested QoS and packet filters) in accordance with the policy for services not known to the PCF. The PCF should adjust the charging keys within the PCC rules and should downgrade the authorized QoS to the allowed value for the services not known to the PCF, if required. + +#### 4.2.6.2.21 Policy Control for L4S + +When the "L4S" feature is supported, and the PCF is configured to provide an explicit indicator to the SMF to enable ECN marking for L4S, this procedure is used by the PCF to explicitly indicate that the UL and/or DL traffic identified by SDF template supports ECN marking for L4S support. + +If the AF provides an explicit indication that the UL and/or DL service data flow supports ECN marking for L4S as defined in 3GPP TS 29.514 [17], or the PCF determines, based on locally configured policies, that the UL and/or DL traffic of the SDF template support ECN marking for L4S, then the PCF may explicitly or implicitly (based on local configuration), indicate to the SMF to enable ECN marking for L4S. + +The PCF shall provide to the SMF the explicit indication of support of ECN marking for L4S by installing PCC rules and the implicit indication by installing or activating PCC rule(s). + +The provisioning of the explicit indication of ECN marking for L4S support per PCC rule shall be performed using the PCC rule provisioning procedure as defined in clause 4.2.6.2.1 and shall be provided using the "l4sInd" attribute within the TrafficControlData the PCC rule refers to. The "l4sInd" attribute shall be set to "UL", "DL" or "UL\_DL" to indicate respectively whether the UL, the DL, or both, UL and DL, service data flow(s) of the SDF template of the PCC rule support ECN marking for L4S. + +When the SMF receives the indication that ECN marking for L4S is supported for the UL and/or DL traffic of the PCC rule, may decide, based on operator's network configuration and policies, to enable for the QoS flow the ECN marking for L4S in either the NG-RAN, as specified in 3GPP TS 29.502 [22], or in the PSA UPF as specified in 3GPP TS 29.244 [13]. + +NOTE: When the ECN marking for L4S is performed by UPF, the NG-RAN is instructed to perform congestion information monitoring, as specified in 3GPP TS 29.502 [22]. + +In case of inter NG-RAN UE mobility, if the ECN marking for L4S has been enabled on source NG-RAN, but the target NG-RAN does not support ECN marking for L4S, then the SMF may enable ECN marking for L4S in PSA UPF. + +When serving PSA UPF or NG-RAN is changed e.g., due to inter-NG-RAN handover or PSA UPF relocation, target NG-RAN and PSA UPF should keep the current congestion exposure method. However, if not available (e.g., ECN marking for L4S is not used anymore in 5GS), the PCF provisioned the "L4S\_SUPP" policy control request trigger, the SMF may notify the PCF about ECN marking not supported. At a subsequent PSA UPF or NG-RAN change, the SMF may determine the target NG-RAN and/or PSA UPF may support the congestion exposure method again and may notify the PCF about ECN marking is supported again. In these cases, the SMF shall invoke the Npcf\_SMPolicyControl\_Update procedure and shall include within the SmPolicyUpdateContextData, including the "L4S\_SUPP" within "repPolicyCtrlReqTriggers" attribute and the "l4sReports" attribute. In each L4sSupportInfo data structure, the SMF shall include the indication that ECN marking for L4S is not available or is available again within the "notifType" attribute and affected PCC rule identifiers within the "refPccRuleIds" attribute. The PCF may notify the affected AF(s) as specified 3GPP TS 29.514 [17]. + +#### 4.2.6.2.22 UL/DL policy control based on Round-Trip latency requirements + +If the "RTLatency" feature is supported, the Round-Trip (RT) latency indication indicates the service data flow needs to meet the RT latency requirement of the service may be provided by the AF, which is twice the single direction delay requirement between the UE and the PSA UPF described by the received QoS reference parameter or the received individual QoS parameter. + +If the AF provided the RT latency indication as defined in 3GPP TS 29.514 [17], the PCF may split the RT latency requirement, i.e. the twice of the single direction delay, into two PDBs of two PCC rules, one for UL service data flow and the other for DL service data flow. The two PDBs can be unequal, but their sum shall not exceed the RT latency requirement. + +NOTE: RT latency requirement may also be locally configured in the PCF together with delay requirement. + +To enable RT latency tracking, the PCF shall generate associated QoS monitoring policies for the two correlated PCC rules as described in clause 4.2.3.25. The uplink and downlink delay for the two PCC rules shall be tracked by PCF independently with same reporting period. When the QoS monitoring results are reported to PCF, the PCF may update the two PCC rules to adjust the UL PDB and DL PDB. + +#### 4.2.6.2.23 Policy Decision for AF requested QoS for a UE or group of UEs not identified by a UE address + +When the AF requested QoS for a UE or group UE(s), the requested QoS data may be either provisioned by the AF/NEF to the TSCTSCF, and later to the PCF for the related active PDU sessions, as specified in 3GPP TS 29.565 [53] and 3GPP TS 29.514 [17], or stored by the AF/NEF at the UDR and later retrieved by the PCF for the related active PDU sessions, as defined in 3GPP TS 29.519 [15]. + +When the PCF needs to make Policy Decision(s) and derive PCC Rule(s) for a PDU session corresponding to the concerned UE or group of UE(s), the PCF shall take into consideration the received AF requested QoS data, if applicable, and may provide to the SMF the policy control triggers corresponding to the AF subscribed event(s) as defined in clause 4.2.6.4, or activate/modify/remove PCC rule(s) as defined in clause 4.2.3.2. + +When the SMF notifies the PCF about a met policy control request trigger corresponding to the AF subscribed event(s), the PCF may notify either the TSCTSF or the AF/NEF, as defined in 3GPP TS 29.514 [17], based on whether the requested QoS data was provisioned via the TSCTSF or the UDR. + +#### 4.2.6.3 Session Rules + +##### 4.2.6.3.1 Overview + +The PCF may perform operations on session rules. The impacted rules shall be included in the "sessRules" map attribute within the SmPolicyDecision data structure with the "sessRuleId" as a key. For installing or modifying a session rule, the corresponding SessionRule data instance shall be provided as the map entry value. For removing a session rule, the map entry value shall be set to NULL. + +In order to install a new session rule, the PCF shall further set other attributes within the SessionRule data structure as follows: + +- if the "subsSessAmbr" has been previously received by the PCF, it shall include the authorized Session-AMBR within the "authSessAmbr" attribute; +- when the "subsDefQos" has been previously received by the PCF, it shall include the authorized default QoS within the "authDefQos" attribute using the procedure as defined in clause 4.2.6.3.3; +- it may include one reference to the UsageMonitoringData data structure within the "refUmData" attribute. In this case, a "umDecs" attribute containing the corresponding Usage Monitoring data policy decisions shall be included in SmPolicyDecision data structure if it has not been previously provided; +- if the "ATSSS" feature is supported, it may include one reference to the UsageMonitoringData data structure to apply for the Non-3GPP access within the "refUmN3gData" attribute. In this case, a "umDecs" attribute containing the corresponding Usage Monitoring data policy decisions shall be included in SmPolicyDecision data structure if it has not been previously provided; and +- it may include one reference to the ConditionData data structure within the "refCondData" attribute. In this case, a "conds" attribute containing the corresponding Condition Data decision shall be included in SmPolicyDecision data structure if it has not been previously provided. + +In order to modify an existing session rule, the PCF shall further set other attributes within the SessionRule data structure as follows: + +- If the PCF needs to modify the attribute(s) within a session rule, the PCF shall include the modified attribute(s) with the new value(s) within the SessionRule data instance. Previously supplied attributes not supplied in the modified PCC rule instance shall remain valid. +- If the PCF only needs to modify the content of referenced policy decision data (e.g. UsageMonitoringData, etc.) and/or condition data for one or more session rules, the PCF shall, within the SmPolicyDecision data structure, include the corresponding policy decision data and/or condition data within the corresponding map attributes (e.g. include the usage monitoring data decision within the "umDecs" attribute). + +The PCF may combine multiple of the above session rule operations in a single message, but the PCF shall ensure that one and only one session rule is enforced in the SMF at a certain point in time. + +NOTE: Either there is always an unconditional session rule provisioned in the NF service consumer (SMF), or there is always a conditioned session rule applicable in the NF service consumer (SMF). + +#### 4.2.6.3.2 Conditioned Session rule + +##### 4.2.6.3.2.1 General + +Up to four conditioned session rules (i.e. authorized Session-AMBR and authorized default QoS) may be provisioned by the PCF. In order to provision a session rule with conditional data, the PCF shall provision a session rule as defined in clause 4.2.6.3.1 and include within its "refCondData" attribute the corresponding ConditionData's "condId" attribute value. The PCF shall also ensure that the referenced ConditionData instance is included in the "conds" map within the SmPolicyDecision data structure following the procedures defined in clause 4.2.6.1 and that the referenced usage monitoring data is the same for all the provisioned conditioned and non-conditioned session rule(s). + +Within the ConditionData instance, the PCF shall include the activation time within the "activationTime" attribute for the time conditioned authorized Session-AMBR and authorized default QoS (deactivation time does not apply for a session rule). If the "AccessTypeCondition" feature as defined in clause 5.8 is supported, the PCF may include for the access type conditioned session rule the access type within the "accessType" attribute and RAT type within the "ratType" attribute if applicable for the access type conditioned authorized Session-AMBR. + +NOTE 1: The SMF retains remaining time conditioned session rules that have an execution time in the future. + +NOTE 2: Time condition and access type condition can both apply to authorize the Session-AMBR within a session rule. + +The PCF shall ensure that a time conditioned session rule and a session rule without time condition for the same session differ only in the authorized session-AMBR and authorized default QoS properties. + +When the SMF detects that the referenced usage monitoring data of the enforced session rule is not the same for all the provisioned session rule(s) the SMF shall report the session rule error for the not enforced session rule(s) as defined in clauses 4.2.3.20 and 4.2.4.21, and shall set the "failureCode" attribute to "INCORRECT\_UM". + +If the SMF receives the conditioned session rule, when the condition indicated in the related attribute(s) within the Condition Data decision (e.g. at the time indicated in the "activationTime" attribute) is met, the SMF shall perform the conditional policy without interaction with the PCF. If the Condition Data decision includes more than one type of conditions and all the types of conditions are met, the SMF shall perform the conditional policy. + +If time conditioned session rule(s) to change the non-conditioned session rule are received by the SMF and the earliest Activation Time is in the past, then the SMF shall immediately enforce the most recent time conditioned instance that is not in the future. + +The PCF may modify a currently installed session rule, including setting, modifying or deleting its condition(s) as follows: + +- 1) When modifying a session rule by setting the condition(s), the PCF shall update the session rule by including the corresponding ConditionData's "condId" attribute value within the "refCondData" attribute and within the SmPolicyDecision data structure include the ConditionData instance within the "conds" attribute if not provisioned yet. +- 2) When modifying a session rule by modifying the condition(s): + +- the PCF may update the session rule by replacing the existing ConditionData instance's "condId" attribute value within the "refCondData" attribute with a new one and within the SmPolicyDecision data structure include the new ConditionData instance within the "conds" attribute if not provisioned yet; or +- the PCF may update the condition data decision which the session rule refers to by updating the corresponding ConditionData instance as defined in clause 4.2.6.1. The PCF may update the value of the condition within the related attribute (e.g. the value of the existing deferred activation time within the "activationTime" attribute). + +3) When modifying a session rule by deleting the condition(s): + +- the PCF shall delete the reference to the ConditionData instance within the session rule by updating session rule with the "refCondData" attribute set to NULL; and +- the PCF may delete the condition data decision which the session rule refers to as defined in clause 4.2.6.1 if no other session rules are referring to the condition data decision. + +To delete a conditioned session rule, the PCF shall perform the deletion of session rule as defined in clause 4.2.6.3.1. The "ueTimeZone" attribute, if available, may be used by the PCF to derive the value for the "activationTime" attribute. + +NOTE 3: Conditioned Session-AMBR and default QoS change helps reducing the signalling load over N7. However, the Session-AMBR and default QoS change needs to be communicated to the UE. Consequently a simultaneous change of the Session-AMBR and default QoS for many UE(s) may introduce a signalling storm in the 5GC (e.g. over N1/N2/N4/N11). The PCF can avoid this simultaneous change of the Session-AMBR and default QoS (e.g. spread the time conditioned change over time for many UEs). + +NOTE 4: For services that depend on specific Session-AMBR and/or default QoS change (e.g. an MPS session), the PCF is responsible to ensure that no conditioned session rules interfere with the service (e.g., ensure proper MPS operation by removing time conditioned settings that would later impact MPS). + +#### 4.2.6.3.2.2 Time conditioned authorized Session-AMBR + +The procedures in clause 4.2.6.3.2.1 apply with clarifications in the present clause. + +Each instance of the session rule shall include authorized Session-AMBR within the "authSessAmbr" attribute. + +If the "VPLMN-QoS-Control" feature is supported and the PCF receives the session AMBR constraints from the SMF, the PCF shall ensure that the authorized session AMBR value within each instance of the session rule does not exceed the session AMBR supported by the VPLMN, if applicable. + +The SMF shall, after applying a time conditioned instruction to change the authorized AMBR, apply the corresponding procedures towards to the access network, the UE and the UPF for the enforcement of the AMBR per PDU session. + +#### 4.2.6.3.2.3 Time conditioned authorized default QoS + +The procedures in clause 4.2.6.3.2.1 apply with clarifications in the present clause. + +Each instance of the session rule shall include authorized default QoS within the "authDefQos" attribute. + +If the "VPLMN-QoS-Control" feature is supported and the PCF receives the default QoS constraints from the SMF, the PCF shall ensure that the authorized default QoS containing 5QI, ARP and, if the feature "VPLMN-5QIPrioLevel" is supported, 5qiPriorityLevel (when the required 5QI Priority Level is different from the standardized Default Priority Level value in the QoS characteristics Table 5.7.4-1 in 3GPP TS 23.501 [2]), values within each instance of the session rule is supported by the VPLMN, if applicable. + +The SMF shall, after applying a time conditioned instruction to change the authorized default QoS, apply the corresponding procedures towards to the access network, the UE and the UPF for the enforcement of the authorized default QoS. All PCC rule(s) with the "defQosFlowIndication" attribute set to true shall remain bound to the default QoS flow. For any other PCC rule previously bound to the default QoS flow, SMF shall then perform the QoS flow binding according to clause 6.4 in 3GPP TS 29.513 [7]. + +#### 4.2.6.3.2.4 Access type conditioned authorized Session-AMBR + +The SMF shall enforce the Session-AMBR values corresponding to the session rule whose referred ConditionData instance contains the "accessType" attribute and "ratType" attribute matching the current access type and RAT type of the UE for the given PDU session. If the "VPLMN-QoS-Control" feature is supported and the PCF receives the session AMBR constraints from the SMF, the PCF shall ensure that the authorized session AMBR value within each instance of the session rule does not exceed the session AMBR supported by the VPLMN, if applicable. + +The PCF shall ensure that an access type conditioned session rule and a session rule without any access type condition for the same session differ only in the authorized session-AMBR property. If more than one access type conditioned session rules are provisioned, and if there is no session rule without any access type condition provisioned in the SMF, the PCF shall ensure that any two access type conditioned session rules for the same session differ only in the authorized session-AMBR property. + +NOTE: Access type conditions are only applicable to the authorized session-AMBR. + +If there is a session rule whose authorized Session-AMBR does not depend on any access type condition provided and there is also a session rule with an access type conditioned authorized Session-AMBR provided, then the access type conditioned session rule where the conditions specified within the Condition Data decision are met shall be enforced. Otherwise, the session rule with the authorized Session-AMBR without any access type condition shall be enforced. + +If conditions from multiple access type conditioned the session rule with authorized Session-AMBR are met at the same time then the session rule related to the most strict matching condition is enforced, e.g. Policy1 specifies access type only and Policy2 specifies access type (with the value same as in Policy1) and an RAT Type, both, then the Policy2 shall be enforced when the UE's current access type and RAT type matches with the condition specified by Policy2. + +If conditions from multiple access type conditioned the session rule with authorized Session-AMBR are met at the same time and all of these policies are equally applicable, e.g. Policy1 specifies access type only and Policy2 specifies RAT type only and if the UE's current access type matches with Policy1 and the UE's current RAT type matches with Policy2, then the SMF should apply the Session-AMBR with Policy2. + +An access type conditioned session rule does not apply to a MA PDU session. When the "ATSSS" feature is supported, and the PDU session is a MA PDU session, the PCF shall not provide to the SMF access type conditioned session rules. If access type conditioned session rules are provisioned in the SMF for a MA PDU session (e.g. because of error in the PCF or EPS to 5GS handover) they shall be ignored. + +#### 4.2.6.3.3 Provisioning of authorized default QoS + +The PCF can provide the authorized default QoS for a session rule to the SMF. The provisioning of authorized default QoS for a session rule shall be performed using the session rule provisioning procedure as defined in clause 4.2.6.3.1. The authorized default QoS shall be encoded using an AuthorizedDefaultQos data structure. + +In order to provision authorized default QoS for a new session rule, the PCF shall include the assigned 5QI value within the "5qi" attribute and the assigned ARP value within the "arp" attribute in the AuthorizedDefaultQos data structure. The PCF may include the "priorityLevel" attribute in the AuthorizedDefaultQos data structure to authorize the particular 5QI priority level to override the default value for a standardized or pre-configured 5QI. The PCF may include a "QosCharacteristics" entry in the "qosChars" attribute map to provide explicitly signalled QoS characteristics associated with a 5QI that is neither standardized nor pre-configured. When the authorized default QoS applies to explicitly signalled QoS Characteristics, it shall be provisioned as defined in clause 4.2.6.6.3. For 5QI of GBR type or delay critical GBR type, the PCF shall additionally include max bandwidth in uplink within the "maxbrUI" attribute and/or max bandwidth in downlink within the "maxbrDI" attribute, the guaranteed bandwidth in uplink within the "gbrUI" attribute and/or the guaranteed bandwidth in downlink within the "gbrDI" attribute and may include the particular averaging window within the "averWindow" attribute and/or particular maximum data burst volume within the "maxDataBurstVol" or "extMaxDataBurstVol" (if supported, see clause 4.2.2.1) attribute to override the default values for a standardized or pre-configured 5QI. + +In order to modify authorized default QoS for an existing session rule, the PCF shall include the modified attribute(s) with the new value(s) within the AuthorizedDefaultQos data structure and provision a new QoS Characteristics if applicable. Previously supplied attributes not supplied in the AuthorizedDefaultQos data structure shall remain valid. + +#### 4.2.6.3.4 Access traffic steering, switching and splitting support + +If both the SMF and the PCF support the "ATSSS" feature, the PCF may enable the control of the PDU session level Usage Monitoring information depending on what access type is used to carry service data flows. + +When the PCF determines that at PDU session level different usage monitoring data shall be defined for the 3GPP and the Non-3GPP access, the PCF shall include within the SessionRule data structure one reference to the UsageMonitoringData policy decision to apply for the Non-3GPP access within the "refUmN3gData" attribute, and a "umDecs" attribute containing the corresponding Usage Monitoring Data policy decisions if it has not been previously provided. When the "refUmN3gData" is omitted, the attribute "refUmData" contains the reference to the UsageMonitoringData policy decision to apply for both, 3GPP and Non-3GPP, accesses. + +**NOTE:** To ensure that the traffic of a set of service data flows is excluded for both, the 3GPP access and Non-3GPP access, from the PDU session level usage monitoring, the "exUsagePccRuleIds" attribute is set to the same value within the Usage Monitoring Control decision referred by the "refUmN3gData" attribute and within the Usage Monitoring Control decision referred by the "refUmData" attribute. + +#### 4.2.6.3.5 Usage Monitoring Control + +Usage monitoring may be performed for all the traffic of a PDU session in the SMF or for all the traffic of a PDU session excluding the traffic of a service data flow or a group of service data flows. + +The provisioning of usage monitoring control for the traffic of a PDU session shall be performed using the session rule provisioning procedure as defined in clause 4.2.6.3.1. When the traffic of a service data flow or a group of service data flows is excluded from the traffic of the PDU session, the UsageMonitoringData policy decision referred within the "refUmData" attribute, and/or the UsageMonitoringData policy decision referred within the "refUmN3gData" attribute when the "ATSSS" feature is supported, shall include the "exUsagePccRuleIds" attribute as defined in clause 4.2.6.5.3.1. + +Usage monitoring for all the session rules (conditioned and non-conditioned) shall refer to the same UsageMonitoringData policy decision(s), i.e., the monitoring key that applies to all the traffic of a PDU session, or to all the traffic of a PDU session except certain service data flow(s), shall not change because of the activation of a conditioned session rule. + +#### 4.2.6.4 Policy control request triggers + +The PCF may provide one or several policy control request trigger(s) to the SMF. In order to do so, the PCF shall include one or several policy control request trigger(s) within the "policyCtrlReqTriggers" attribute within the SmPolicyDecision data structure. + +During the lifetime of the PDU session, the PCF may update or remove the policy control request triggers. In order to update the policy control request trigger, the PCF shall provide the new complete list of applicable policy control request triggers by including one or several policy control request trigger(s) within the "policyCtrlReqTriggers" attribute within the SmPolicyDecision data structure. + +The PCF may remove all previously provided policy control request triggers by providing a "policyCtrlReqTriggers" attribute set to the value NULL. Upon reception of a policy control request trigger with this value, the SMF shall not inform PCF of any trigger except for those triggers that are always reported and do not require provisioning from the PCF. + +Whenever the PCF provisions one or several policy control request trigger(s) by using an HTTP POST message as defined in clause 4.2.3.2, unless otherwise specified in a policy control request trigger's value definition, the SMF shall send the corresponding currently applicable values (e.g. access type, RAT type, user location information, etc.) to the PCF within the UeCampingRep data structure in the response of the HTTP POST message, and in this case, the "repPolicyCtrlReqTriggers" attribute shall not be included. + +#### 4.2.6.5 Encoding of the request of information reporting + +##### 4.2.6.5.1 Request of Access Network Charging Identifier + +When the Access Network Charging Identifier is unknown for an AF session to the PCF, the PCF may request the SMF to provide the Access Network Charging Identifier associated to the dynamic PCC rules. To do so, the PCF shall within + +SmPolicyDecision data structure provide the "policyCtrlReqTriggers" attribute with the value "AN\_CH\_COR" if the policy control request trigger is not previously set and the "lastReqRuleData" attribute. For the RequestedRuleData instance, the PCF shall include the CH\_ID within the "reqData" attribute and reference of the PCC rule within the "refPccRuleIds" attribute. + +The PCF shall interpret that the Access Network Charging Identifier is known when the PCF receives an "accNetChId" attribute with the "sessionChScope" attribute included and set to true as defined in clause 4.2.2.11 and 4.2.4.13. + +#### 4.2.6.5.2 RAN NAS Cause Support + +When the RAN-NAS-Cause feature is supported, the PCF may request the SMF to inform it of the result of PCC rule(s) removal, when the PCF removes PCC rule(s). In order to do so, the PCF shall additionally include the "policyCtrlReqTriggers" attribute containing the "RES\_RELEASE" value if this policy control request trigger was not previously set, and the "lastReqRuleData" attribute. Within the RequestedRuleData instance, the PCF shall include the "RES\_RELEASE" value within the "reqData" attribute and reference the removed PCC rule within the "refPccRuleIds" attribute. + +NOTE: This is done to allow the PCF to notify the AF when there is an abnormal termination of the QoS flow. The PCF does not have to retry the removal of these PCC Rules. + +#### 4.2.6.5.3 Provisioning of the Usage Monitoring Control Policy + +##### 4.2.6.5.3.1 General + +The PCF may indicate the need to apply monitoring control of the accumulated usage of network resources on a per PDU session basis. Usage is defined as volume or time of user plane traffic. Monitoring for traffic volume and traffic time can be performed in parallel. The data collection for usage monitoring control shall be performed per monitoring key, which may apply to a single service data flow, a set of service data flows or all the traffic in a PDU session. If usage monitoring at PDU session level is enabled, the PCF may request the SMF to exclude a single service data flow or a set of service data flows from usage monitoring at PDU session level. + +During PDU session establishment, the PCF may receive information from the UDR about total the allowed usage per DNN / S-NSSAI combination and UE, i.e. the overall amount of allowed traffic volume and/or time of usage that are to be monitored per DNN / S-NSSAI combination and UE and/or the total allowed usage for Monitoring key(s) per DNN / S-NSSAI combination and UE. + +NOTE 1: It depends on the implementation of UDR whether to provide the total allowed usage per DNN / S-NSSAI combination and UE to different PCFs if these different PCFs are serving PDU sessions with the same value of DNN / S-NSSAI combination and UE. + +If the SMF supports the UMC feature, the PCF may request usage monitoring control for a PDU session. If at that time the PCF has not provided "US\_RE" policy control request trigger to the SMF, the PCF shall include the "policyCtrlReqTriggers" attribute with the value "US\_RE" and provide it to the SMF as defined in clause 4.2.6.4. The PCF shall not remove the "US\_RE" policy control request trigger while usage monitoring is still active in the SMF. + +At PDU session establishment and modification, the PCF may provide to the SMF, for each usage monitoring control instance, the applicable threshold(s), i.e. volume threshold, time threshold or both volume threshold and time threshold. To provide the initial threshold(s) for each usage monitoring control instance, the PCF shall include these threshold(s) within the "umDecs" attribute within the SmPolicyDecision data structure. + +The PCF may provide a monitoring time to the SMF for the usage monitoring control instance(s) and optionally specify a subsequent threshold value for the usage after the monitoring time. + +NOTE 2: The PCF can provide only one threshold or one threshold and one subsequent threshold in the case that monitoring time is provided. When only the threshold is provided, the UPF resets the usage threshold to the remaining value of the threshold at the monitoring time; when the threshold and subsequent threshold are provided, the UPF resets the usage threshold to the value of the subsequent threshold at the monitoring time as defined in 3GPP 29.244 [13]. + +Threshold levels may be defined for: + +- the total volume only; or + +- the uplink volume only; or +- the downlink volume only; or +- the uplink and downlink volume; and/or +- the time. + +Threshold levels, monitoring time, if applicable, and inactive time, if applicable, for each usage monitoring control instance may be provisioned within an entry of the "umDecs" attribute as follows: + +- the total volume threshold, if applicable, within the "volumeThreshold" attribute; +- the uplink volume threshold, if applicable, within the "volumeThresholdUplink" attribute; +- the downlink volume threshold, if applicable, within the "volumeThresholdDownlink" attribute; +- the time threshold, if applicable, within the "timeThreshold" attribute; +- the total volume threshold after the monitoring time, if applicable, within the "nextVolThreshold" attribute; +- the uplink volume threshold after the monitoring time, if applicable, within the "nextVolThresholdUplink" attribute; +- the downlink volume threshold after the monitoring time, if applicable, within the "nextVolThresholdDownlink" attribute; +- the time threshold after the monitoring time, if applicable, within the "nextTimeThreshold" attribute; +- the monitoring time, if applicable, within the "monitoringTime" attribute; +- the inactive time, if applicable, within the "inactivityTime" attribute. + +If the SMF reports usage before the monitoring time is reached, the monitoring time is not retained by the SMF. Therefore, the PCF may again provide in the response a monitoring time and optionally the subsequent threshold value(s) for the usage after the monitoring time. + +The "inactivityTime" attribute represents the time interval after which the time measurement shall stop for the Monitoring Key, if no packets belonging to the corresponding Monitoring Key are received. Time measurement shall resume again on receipt of a further packet belonging to the Monitoring Key. Time measurement for a Monitoring key shall also be stopped when time based usage monitoring is disabled, if this happens before the Inactivity Detection Time is reached. If an "inactivityTime" attribute with value of zero is provided, or if no "inactivityTime" attribute is present within the usage monitoring control instance provided by the PCF, the time measurement shall be performed continuously from the point the first packet is received matching the applicable Monitoring Key is received and until time based usage monitoring is disabled. + +If the usage monitoring control instance applies to the PDU session level, the PCF shall include the reference to the Usage Monitoring Data decision within the "refUmData" attribute of the related session rule. + +If the usage monitoring control instance applies to a service data flow or a group of service data flows, the PCF shall include the reference to the Usage Monitoring Data decision within the "refUmData" attribute of the related PCC rule(s). + +The PCF may provide one usage monitoring control instance applicable at PDU session level and one or more usage monitoring control instances applicable at PCC Rule(s) level. + +If the PDU session level usage monitoring is enabled and service data flow(s) need to be excluded from this PDU session level usage monitoring, the PCF shall include the corresponding PCC rule identifier(s) within the "exUsagePccRuleIds" attribute of the UsageMonitoringData instance of PDU session level usage monitoring. If the exclusion is enabled, the PCF may disable the exclusion again for service data flow(s) by removing the corresponding PCC rule identifier(s) from "exUsagePccRuleIds" attribute. + +The PCF may provide new volume threshold(s) and/or a new time threshold to the SMF. The new threshold value(s) override the existing value(s) in the SMF. + +When the SMF receives above the usage monitoring control request from the PCF, the SMF shall initiate the PFCP Session Establishment procedure as defined in clause 7.5.2, or the PFCP Session Modification procedure, as defined in clause 7.5.4 of 3GPP TS 29.244 [13], to request the UPF to perform the usage monitoring control. + +If the reset time of the usage monitoring related information (see clause 5.4.2.7 of 3GPP TS 29.519 [15]) is reached, the PCF shall reset the remaining allowed usage to the value(s) indicated in the usage monitoring related information and shall then interact with the SMF to undo any previously applied policy decisions related to remaining allowed usage of zero (or below zero). + +NOTE 2: The PCF can also update the related usage monitoring information in the UDR as defined in 3GPP TS 29.519 [15] according to the performed reset action. + +#### 4.2.6.5.3.2 Disabling Usage Monitoring + +After usage monitoring is enabled, the PCF may explicitly disable usage monitoring as a result of receiving an SM Policy association update from the SMF which is not related to reporting usage, but to other external triggers (e.g., receiving an AF request, subscriber profile update), or a PCF internal trigger. When the PCF disables usage monitoring, the SMF shall report the accumulated usage which has occurred while usage monitoring was enabled since the last report. + +To disable usage monitoring for a monitoring key, the PCF shall provide either the SMF with the corresponding applicable attributes of the usage monitoring control instance containing a NULL value (e.g. the previous provided "volumeThreshold" is set to NULL), or: + +- for dynamic PCC rule(s) or session rule(s), remove the reference to the corresponding usage monitoring control instance from all the dynamic PCC rule(s) or session rule(s) referencing it; + +NOTE: The PCF could keep the UsageMonitoringData policy decision valid in the SMF. + +- for predefined PCC rule(s), remove the UsageMonitoringData policy decision referred from all the activated predefined PCC rule(s). + +When the PCF disables usage monitoring for usage monitoring key(s) via a Npcf\_SMPolicyControl\_UpdateNotify or a Npcf\_SMPolicyControl\_Update service operation, the SMF shall trigger a new Npcf\_SMPolicyControl\_Update service operation using the procedures specified in clause 4.2.4.10 to report accumulated usage for the disabled usage monitoring key(s). + +#### 4.2.6.5.3.3 PCF Requested Usage Report + +When usage monitoring is enabled, the PCF may request the SMF to report the accumulated usage for one or more enabled usage monitoring control instance(s) regardless of whether associated usage threshold(s) have been reached or not. In order to do so, the PCF shall include the "lastReqUsageData" attribute containing one or more reference(s) to usage monitoring data decision(s) within the "refUmIds" attribute or the "allUmIds" attribute set to true in an HTTP POST request or in the response of an HTTP POST request from the SMF. The PCF shall require the SMF to report accumulated usage for one or more enabled usage monitoring control instance(s) only in a response to received HTTP POST request from the SMF when the SMF has not provided accumulated usage in this HTTP POST request for the same usage monitoring control instance(s). + +#### 4.2.6.5.4 Request for Access Network Information + +When the NetLoc feature is supported, if the AF requests the PCF to report the access network information as described in clauses 4.2.2, 4.2.3 or 4.2.4 of 3GPP TS 29.514 [17] or in clauses 4.1 and 4.2 of 3GPP TS 29.214 [18], the PCF shall perform the PCC rule provisioning procedure as defined in clause 4.2.6.2.1 and additionally provide the requested access network information indication (e.g. user location and/or user timezone information) to the SMF as follows: + +- it shall include the "lastReqRuleData" attribute to contain the "reqData" attribute with the value(s) MS\_TIME\_ZONE and/or USER\_LOC\_INFO and the "refPccRuleIds" attribute to contain the related installed/modified/removed PCC rule identifier(s). +- it shall provide the AN\_INFO policy control request rigger within the "policyCtrlReqTriggers" attribute (if not yet set). + +For those PCC Rule(s) based on preliminary service information as described in 3GPP TS 29.514 [17] or in 3GPP TS 29.214 [18], the PCF may assign the 5QI and ARP of the default QoS flow to avoid signalling to the UE. These PCC Rules shall not include the "packetFilterUsage" attribute set to true within the "flowInfos" attribute. + +For those PCC Rule(s) based on AF signalling as described in 3GPP TS 29.514 [17] or in 3GPP TS 29.214 [18], the PCF may use 5QI and ARP for AF signalling to avoid signalling to the UE. These PCC Rules shall not include the "packetFilterUsage" attribute set to true within the "flowInfos" attribute. + +NOTE: Similarly, for predefined PCC rules based on AF signalling, these PCC Rule(s) could be defined with the 5QI and ARP for AF signalling, and cannot include packet filter usage information. + +#### 4.2.6.5.5 Request for the successful resource allocation notification + +The PCF may request the SMF to confirm that the resources associated to a PCC rule are successfully allocated. To do so, the PCF shall provide within the "policyCtrlReqTriggers" attribute of the SmPolicyDecision data structure the value "SUCC\_RES\_ALLO ", if this policy control request trigger was not previously set, and provide the "lastReqRuleData" attribute as well. For the associated RequestedRuleData instance, the PCF shall include the value "SUCC\_RES\_ALLO" within the "reqData" attribute and the reference to the PCC rule within the "refPccRuleIds" attribute. + +#### 4.2.6.5.6 Provisioning of Presence Reporting Area Information + +When the PRA or ePRA feature is supported, the PCF may determine during the lifetime of the PDU session whether reports on the change of UE presence in Presence Reporting Area(s) are desired for this PDU session based on the subscriber's profile configuration. If such reporting is desired for a PDU session, the PCF shall provide the "praInfos" attribute within the SmPolicyDecision data structure. Within each associated PresenceInfoRm data structure, the PCF shall include the Presence Reporting Area Identifier within the "prald" attribute, and, for a UE-dedicated Presence Reporting Area, the list of elements composing the presence reporting area within the "trackingAreaList" attribute, the "ecgiList" attribute, the "ncgiList" attribute, the "globaleNbIdList" attribute and/or the "globalRanNodeIdList" attribute. The PCF shall also activate the reporting of the changes of UE presence in the provided Presence Reporting Area(s) by provisioning the "PRA\_CH" policy control request trigger to the SMF, within the "policyCtrlReqTriggers" attribute. + +NOTE 1: If this feature is not supported, the PCF can instead activate location change reporting that enables to receive reports of the actual location of the UE. Due to the potential increase in signalling load, careful consideration of the network load is necessary for such reporting, e.g. by limiting the number of subscribers subject to such reporting. + +If the PCF is configured with a Presence Reporting Area identifier referring to a list of Presence Reporting Area Identifier(s) within a Set of Core Network predefined Presence Reporting Areas as defined in 3GPP TS 23.501 [2], the PCF shall include only the identifier of the Presence Reporting Area Set within the "prald" attribute. + +NOTE 2: The Presence Reporting Area Identifier can correspond to a list of Presence Reporting Area Identifier(s) within a Set of Core Network predefined Presence Reporting Areas (PRA set identifier) as defined in 3GPP TS 23.501 [2]. + +The PCF may modify the list of PRA Identifier(s) by providing new Presence Reporting Area(s) or removing existing Presence Reporting Area(s), or modify the list of Presence Reporting Area element(s) by providing the updated Presence Reporting Area(s). In order to do that, + +- when the PRA feature is supported, the PCF shall follow the general procedure defined in clause 4.2.6.1 and supply the Presence Reporting Area identifier(s) as key(s) of "praInfos" the map attribute; or +- when the ePRA feature is supported, the PCF shall follow the general procedure defined in clause 4.2.6.1 and supply the Presence Reporting Area identifier(s) as key(s) of "praInfos" map, with the exception that for the modification of the list of the Presence Reporting Area element(s) the PCF shall fully replace the Presence Reporting Areas(s) previously provided with the new complete list of Presence Reporting Area element(s). + +NOTE 3: When the PRA feature is supported, the PCF cannot indicate the SMF to remove an existing Presence Reporting Area element(s) from a Presence Reporting Area by providing the updated Presence Reporting Area as defined in clause 4.2.6.1. How to support it depends on implementation. + +When PRA or ePRA feature is supported, the PCF may remove the associated policy control request trigger (i.e. "PRA\_CH") as defined in clause 4.2.6.4, if previously activated. + +If the NF service consumer and the PCF support both PRA and ePRA features, the NF service consumer and PCF shall perform the behaviours as the ePRA feature defined. + +If the "PRA\_CH" policy control request trigger is provisioned, when the PCF provides a list of presence reporting areas as described above, the PCF shall ensure that the maximum number of provisioned Presence Reporting Area Identifiers is not exceeded. The maximum number of PRAs may be configured in the PCF. The PCF may have independent configuration of the maximum number for Core Network pre-configured PRAs and UE-dedicated PRAs. + +NOTE 4: For all the Presence Reporting Area(s) provided by the PCF, the SMF can store the Presence Reporting Area Identifier(s) together with an indication that states that it relates to PCF requested PRA status changes. + +NOTE 5: This information is needed so that if both the PCF and the CHF request the reporting of PRA status changes, the SMF is able to differentiate whether the reported PRA changes are relevant to the PCF or the CHF. + +The SMF shall invoke the Namf\_EventExposure service in the AMF to handle the subscription to the presence state of a UE in an area of interest as specified in 3GPP TS 29.518 [36]. + +The PCF may be notified during the lifetime of a PDU session that the targeted UE is located in an access network where local configuration indicates that reporting changes of UE presence in Presence Reporting Area(s) is not supported. The PCF may then remove the associated policy control request trigger (i.e. "PRA\_CH"), if previously activated. In this case, the PCF shall also remove the provisioned Presence Reporting Area(s) by including the "praInfos" attribute set to NULL within the SmPolicyDecision data structure. + +The SMF shall remove the Namf\_EventExposure service subscription with the AMF for the reporting of Changes of UE presence in Presence Reporting Area(s), when the PCF and CHF remove the associated request triggers. + +#### 4.2.6.5.7 Policy provisioning and enforcement of reflective QoS + +If the PCF receives the "refQosIndication" attribute set to true as defined in clauses 4.2.2.2 or 4.2.4.2, and if the PCF determines that Reflective QoS Control will be enabled for the PDU session based on the operator's policy and user subscriptions, the PCF may provision the Reflective QoS Timer by including the "reflectiveQoS Timer" attribute within the SmPolicyDecision data structure in the response message. + +The provisioning of reflective QoS may be performed for service data flows associated with one or more PCC rules, and shall be performed using the PCC rule provisioning procedure. The PCF may within a QoS data decision which a PCC rule refer to include the "reflectiveQos" attribute set to true to enable the Reflective QoS control to a non-GBR downlink service data flow when the PCF authorizes the QoS for the service data flow as defined in clause 4.2.6.6.2. + +The PCF shall ensure that both, uplink and downlink traffic for such non-GBR service data flow are allowed. + +NOTE 1: The PCF can allow both uplink and downlink traffic for the non-GBR service data flow in several ways, e.g. by installing a PCC rule with uplink and downlink flow information, or by installing separate PCC rules for the uplink flows and downlink flows, or by installing a PCC rule with only the application identifier. + +The PCF shall activate the reporting changes of reflective QoS indication by provisioning the "REF\_QOS\_IND\_CH" policy control request trigger to the SMF. + +NOTE 2: While the UE applies a standardized value for the precedence of all UE derived QoS rules, PCC rules precedence values can vary and PCF configuration has to ensure that there is a large enough value range for the precedence of PCC rules corresponding to UE derived QoS rules. To avoid that the precedence of network provided QoS rules need to be changed when Reflective QoS is activated and filters are overlapping, the PCF will take the standardized value for the precedence of UE derived QoS rules into account and will setting the precedence value of PCC rules subject to Reflective QoS to a value in the range from 70 to 99 (decimal), as specified in 3GPP TS 24.501 [20], clause 6.2.5.1.1.3. + +The SMF shall apply reflective QoS control for the downlink traffic of the service data flows of the PCC rules that reference a QosData decision that includes "reflectiveQos" attribute set to true. + +The PCF shall not include the "reflectiveQos" attribute set to true within the QoS data decision which the PCC rule with match-all SDF template refers to. If a PCC rule with match-all SDF template has been provisioned to the SMF, the PCF + +shall not include the "reflectiveQos" attribute within the QoS data decision which contains the "defQosFlowIndication" attribute, either. + +If the PCF receives the "refQosIndication" attribute set to false as defined in clause 4.2.4.2, the PCF shall disable the reflective QoS Control for the PDU session. In order to do so, the PCF shall within the QoS data decision which affected PCC rule refer to include the "reflectiveQos" attribute set to false and may update other QoS parameters within the QoS data decision and/or update the flow information of PCC rule by including the "packetFilterUsage" attribute set to true. + +## 4.2.6.6 Authorized QoS + +### 4.2.6.6.1 General + +The PCF shall provision the authorized QoS. The authorized QoS may apply to a PCC rule or to a PDU session. + +- When the authorized QoS applies to a PCC rule, it shall be provisioned within the corresponding PCC rule as defined in clause 4.2.6.6.2. +- When the authorized QoS for a PCC rule with a GBR QCI is candidate for resource sharing an instruction on the allowed sharing may be provisioned as defined in clause 4.2.6.2.8. +- When the authorized QoS applies to a PDU session, it shall be provisioned as defined in clause 4.2.6.3.1. +- When the authorized QoS applies to the default QoS flow, it shall be provisioned as defined in clause 4.2.6.3.1. +- When the authorized QoS applies to an explicitly signalled QoS Characteristics, it shall be provisioned as defined in clause 4.2.6.6.3. +- When the authorized QoS applies to the Reflective QoS, it shall be provisioned as defined in clause 4.2.6.5.7. + +The authorized QoS provides appropriate values for the resources to be enforced. The authorized QoS for a PCC rule is a request for allocating the corresponding resources. The Provisioning of authorized QoS per PCC rule is a part of PCC rule provisioning procedure. + +If the SMF cannot allocate any of the resources as authorized by the PCF, the SMF informs the PCF and acts as described in clauses 4.2.3.16 and 4.2.4.15. + +The SMF shall interact with the (R)AN, UPF and UE for enforcing the policy based authorization. + +QoS authorization information may be dynamically provisioned by the PCF or it may be a pre-defined PCC rule in the SMF. Moreover, all the parameters of the authorized QoS may be changed. + +NOTE 1: A change of 5QIs cannot be described as an upgrade or downgrade and also no 5QI can be referred to as the higher or lower. Whether the 5QI is permitted to be changed or not is subject to both operator policies and normal restrictions on changing from a non-GBR 5QI value to GBR 5QI value on an IP flow. + +NOTE 2: All attributes of the ARP QoS parameter can be changed but only the ARP priority level represents an ordered range of values. The ARP priority level attribute represents the actual priority for the service/user with the value 1 as the highest and can thus be upgraded and downgraded. + +If the PCF is unable to make a decision for the response to the HTTP POST message by the SMF, the PCF may reject the request as described in clause 5.7. + +### 4.2.6.6.2 Policy provisioning and enforcement of authorized QoS per service data flow + +The Provisioning of authorized QoS per service data flow is a part of PCC rule provisioning procedure, as described in clause 4.2.6.2.1. + +The authorized QoS per service data flow shall be provisioned within a QosData data structure. The PCF shall include a "qosDecs" attribute containing the corresponding QoS data decision within the SmPolicyDecision data structure and include the reference to this QoS data decision within the "refQosData" attribute of the PccRule data instance. + +When network slice data rate policy control applies and the authorized QoS per service data flow refers to a 5QI of GBR type, the PCF shall derive the authorized QoS per service data flow as described in clause 4.2.6.8. + +Within the QoS data decision, for 5QI of GBR type or delay critical GBR type, the PCF shall include the authorized GBR 5QI or delay critical GBR 5QI respectively within the "5qi" attribute, the ARP within the "arp" attribute, and max bandwidth in uplink within the "maxbrUI" attribute and/or max bandwidth in downlink within the "maxbrDI" attribute, the guaranteed bandwidth in uplink within the "gbrUI" attribute and/or the guaranteed bandwidth in downlink within the "gbrDI" attribute. If the PCF determines that the application traffic can be adapted to the change in the QoS based on the configuration (e.g. if the AF is capable to trigger rate adaptation), the PCF may request a notification when authorized GBR or delay critical GBR cannot be guaranteed or can be guaranteed again by including the "qnc" attribute set to true. + +Within the QoS data decision, for 5QI of non-GBR type, the PCF shall include the authorized non-GBR 5QI within the "5qi" attribute and the ARP within the "arp" attribute. The PCF may authorize the max bandwidth in uplink within the "maxbrUI" attribute and/or max bandwidth in downlink within the "maxbrDI" attribute. + +When the PCF authorizes a standardized 5QI but a Priority Level, an Averaging Window and/or a Maximum Data Burst Volume which are different from the standardized value in the table 5.7.4-1 of 3GPP TS 23.501 [2] are required, the PCF shall include the Priority Level within the "priorityLevel" attribute, the Averaging Window within the "averWindow" attribute and/or the Maximum Data Burst Volume within the "maxDataBurstVol" attribute or the "extMaxDataBurstVol" attribute (if supported, see clause 4.2.2.1). + +NOTE 1: For the non-standardized or non-configured 5QI, the PCF needs to authorize explicitly signalled QoS Characteristics associated with the 5QI if the PCF has not provisioned it. + +If the configured policy allows at reception of the service information from the AF and the application of the rules of the QoS mapping procedures defined in 3GPP TS 29.513 [7] clause 7.3.2 for the received service information result in a 5QI of 1 associated with the corresponding flows, and the RAN-Support-Info feature as defined clause 5.8 is supported, the PCF shall determine the Maximum Packet Loss Rate for UL and DL for those flows associated within 5QI of 1. In this case, the PCF shall include the value of Maximum Packet Loss Rate for UL within the "maxPacketLossRateUI" attribute and/or the value of Maximum Packet Loss Rate for DL within the "maxPacketLossRateDI" attribute. + +NOTE 2: If CHEM feature is supported, then PCF as described in clause 7.2.3 of 3GPP TS 29.513 [7] or based on local configuration, the PCF sets the downlink and uplink maximum packet loss rates corresponding to either the most robust codec mode or the least robust codec mode of the negotiated set in each direction. + +If the PCF wants to ensure that a PCC Rule is always bound to the default QoS flow, the policy provisioning for the related authorized QoS shall be done as described in clause 4.2.6.2.10. + +The SMF shall perform a QoS flow binding based on the QoS information within the QoS data decision as defined in clause 6.4 of 3GPP TS 29.513 [7] after the SMF installs or activates the PCC rules. + +The SMF shall reserve the resources necessary for the guaranteed bitrate for the PCC rule upon receipt of a PCC rule provisioning including QoS information. For GBR QoS flows the SMF should set the QoS flow's GBR to the sum of the GBRs of all PCC rules that are active/installed and bound to that GBR QoS flow. For GBR QoS flow the SMF should set the QoS flow's MBR to the sum of the MBRs of all PCC rules that are active/installed and bound to that GBR QoS flow. + +NOTE 3: Since the PCF controls the GBR value in the PCC rule, the PCF can prevent that uplink GBR resources are reserved by providing an uplink GBR value of zero for that PCC rule. This may be useful e.g. for a PCC rule with application identifier as the uplink traffic can be received in other QoS flow than the one the PCC rule is bound to. + +The SMF shall assign a QFI if a new QoS flow needs to be established and shall derive, if applicable, the QoS profile required towards the Access Network, the QoS rule required towards the UE and the QoS information with PDRs towards to the UPF. If multiple PCC rules with the Maximum Packet Loss Rate for UL and DL are bound to the same QoS flow, the SMF shall choose the lowest value per direction related to the PCC rules within the QoS profile towards to the access network. + +For PIN scenarios (defined in 3GPP TS 23.501 [2], clause 5.44), the SMF may, for a (S-NSSAI, DNN) combination of the PDU Session, increase the CN PDB in the derived QoS profile corresponding to a GBR flow if the UE requested non-3GPP delay budget as part of a UE-initiated resource modification procedure based on operator policy and implementation. + +NOTE 4: The non-3GPP delay budget does not impact the QoS flow binding as defined in clause 6.4 in 3GPP TS 29.513 [7]. + +If one or more of the 5QI, ARP, QNC, Priority level, Averaging Window and Maximum Data Burst Volume attributes of a PCC rule are modified to the same updated values for all the PCC rules bound to the same QoS flow, then the SMF should modify the corresponding attributes for that impacted QoS flow. + +Upon deactivation or removal of a PCC rule, the SMF shall free the resources reserved for that PCC rule, and initiate the corresponding procedure with access network, UE and UPF to remove the resources. + +#### 4.2.6.6.3 Policy provisioning and enforcement of authorized explicitly signalled QoS Characteristics + +The PCF may provision a dynamically assigned 5QI value (from the non-standardized and non-preconfigured value range) and the associated 5G QoS characteristics to the SMF. In order to do so, the PCF shall include within the SmPolicyDecision data structure the "qosChars" attribute to contain one or more authorized signalled QosCharacteristics instance(s). For each QosCharacteristics instance, the PCF shall include the assigned 5QI value within the "5qi" attribute, the resource type value within the "resourceType" attribute, the 5QI Priority Level value within the "priorityLevel" attribute, the Packet Delay Budget value within the "packetDelayBudget" attribute, the Packet Error Rate value within the "packetErrorRate" attribute, the Averaging Window value within the "averagingWindow" attribute, if applicable, and the Maximum Data Burst Volume value within the "maxDataBurstVol" attribute or the "extMaxDataBurstVol" attribute (if supported, see clause 4.2.2.1), if applicable. If the PCF has provisioned an authorized signalled QosCharacteristics instance to the SMF, the PCF shall not update nor remove it during the lifetime of the policy association. + +Upon receiving the authorized explicitly signalled QoS characteristics, the SMF shall derive the QoS profile for the access network and provide it to the access network by invoking the corresponding procedure. + +NOTE 1: The SMF can increase the Packet Delay Budget in the QoS profile in PIN scenarios as a result of a UE-requested PDU session modification procedure for certain (S-NSSAI, DNN) combination and signal it to the access network(defined in 3GPP TS 23.501 [2], clause 5.44.3.4). + +NOTE 2: Operator configuration is assumed to ensure that the assigned dynamic 5QI value is unique and references the same set of QoS characteristics within the whole PLMN at a given time. + +#### 4.2.6.7 Monitoring the data rate per network slice for a UE + +The PCF can support monitoring of data rate per S-NSSAI for a UE. + +During PDU session establishment, if the PCF supports monitoring of the data rate per S-NSSAI for a UE, the PCF may retrieve for the UE and S-NSSAI to which the PDU session is allocated the Subscribed UE-Slice-MBR (i.e. the aggregate data rate that can be expected to be provided across all GBR and Non-GBR QoS Flows of a UE for a network slice identified by an S-NSSAI) from the UDR as defined in clause 5.4.2.14 of 3GPP TS 29.519 [15]. The PCF shall monitor the data rate for this S-NSSAI and UE by deriving the utilized data rate based on the authorized Session-AMBR and/or the authorized QoS per service data flow in all PDU session(s) established for the UE in the concerned S-NSSAI and checking the derived value against the UE-Slice-MBR set by the PCF based on the Subscribed UE-Slice-MBR value retrieved from the UDR and operator policies available at the PCF. + +As part of the PDU session modification procedure(s) targeting the PDU session(s) established for the UE in the concerned S-NSSAI, whenever the PCF needs to provide the associated authorized Session-AMBR(s), install new or updated PCC Rule(s) and/or delete PCC Rule(s) related to GBR service data flow(s), the PCF shall calculate the utilized data rate as described in clause 4.2.6.8.2. + +At the termination of a PDU session established for the UE in the concerned S-NSSAI, the PCF shall adjust the utilized data rate for the UE based on the release of the Session-AMBR and the removal of all the PCC Rule(s) related to GBR service data flow(s) associated to that PDU session. + +To enable this monitoring, the SMF shall select the same PCF instance for all PDU sessions of the UE to the S-NSSAI that is subject to this monitoring as defined in clause 8.3 of 3GPP TS 29.513 [7]. + +When the calculated utilized data rate for the S-NSSAI and UE reaches a certain percentage of the Subscribed UE-Slice-MBR value, the PCF may apply a policy decision to strengthen the traffic restrictions for individual PDU session(s) or PCC rule(s) (e.g. change the authorized Session-AMBR as defined in clause 4.2.6.3.1, change the authorized QoS per service data flow as defined in clause 4.2.6.6.2, or change the charging keys) within individual PDU session(s) established for the UE in the concerned S-NSSAI. When the calculated utilized data rate per S-NSSAI for a UE falls below that percentage of the Subscribed UE-Slice-MBR value, the PCF may relax the traffic restrictions for + +individual PDU session(s) or PCC rule(s) within individual PDU session(s) established for the UE in the concerned S-NSSAI. + +As part of the policy decision to strengthen the traffic restrictions for individual PDU session(s), the PCF may reject the establishment or SMF-initiated modification of the associated SM Policy Association(s) with an HTTP "403 Forbidden" response message including the "cause" attribute of the ProblemDetails data structure set to "EXCEEDED\_UE\_SLICE\_DATA\_RATE". + +NOTE: It is recommended to avoid frequent policy decisions which trigger a signalling with the UE (like change of the authorized Session-AMBR or change of the authorized QoS per service data flow). + +#### 4.2.6.8 Network slice related data rate policy control + +##### 4.2.6.8.1 General + +A PCF that supports network slice related data rate policy control shall be able to control and manage the network slice data rate. + +A Maximum Slice Data Rate may be configured by the operator (e.g. based on an SLA related to the associated network slice identified by an S-NSSAI). + +NOTE 1: The Maximum Slice Data Rate defines the maximum allowed aggregate data rate across all GBR and Non-GBR QoS Flows within the network slice identified by an S-NSSAI as defined in 3GPP TS 29.519 [15]. + +NOTE 2: The maximum data rate of Non-GBR QoS Flow(s) is controlled via the authorized Session-AMBR, while the maximum data rate of a GBR QoS Flow is controlled via the authorized MBR value of the associated PCC rule. + +The PCF shall determine, based on local configuration, if the network slice data rate is controlled via PCF-based monitoring by using QoS parameters or with assistance of the NWDAF. + +The PCF shall monitor the data rate of the network slice and ensure that it does not exceed the Maximum Slice Data Rate for that network slice by e.g. rejecting new SM Policy Associations, changing the authorized Session-AMBR values (if allowed by the HPLMN), changing the MBR values in PCC rules belonging to GBR service data flows or other actions depending on operator's policies. + +NOTE 3: Based on operator's policies, it is also possible for the PCF to accept that new PDU session(s) or PCC rule(s) belonging to GBR service data flow(s) lead to exceeding the Maximum Slice Data Rate and apply a different charging for them. Once the Maximum Slice Data Rate is no longer exceeded, the PCF can decide to go back to applying the previous charging. + +NOTE 4: Subject to operator policy and national/regional regulations, prioritised services and emergency services may be exempted from network slice data rate policy control. + +NOTE 5: A single PCF can be used for the monitoring and limitation of the network slice related data rate. To enable this, the SMF has to select the same PCF instance for all PDU Sessions of the UE to the S-NSSAI. + +##### 4.2.6.8.2 PCF-based network slice data rate policy control by using QoS parameters + +If the NWDAF is not deployed or not used for network slice data rate policy control and PCF-based monitoring of network slice data rate by using QoS parameters applies, the UDR shall maintain the Remaining Maximum Slice Data Rate per S-NSSAI as part of the network slice specific policy control data as defined in 3GPP TS 29.519 [15]. + +Whenever the PCF needs to calculate the data rate related to authorized Session-AMBR and/or the MBR(s) of the GBR Service Data Flow(s), the PCF shall obtain the Remaining Maximum Slice Data Rate by interacting with the UDR as defined in 3GPP TS 29.519 [15]. When the PCF interacts with the UDR may be based on operator policies. + +When the PCF needs to provide the authorized Session-AMBR and/or install new or updated PCC Rule(s) and/or delete PCC Rule(s) related to GBR service data flow(s), the PCF shall: + +- calculate the difference between the previously authorized Session-AMBR, if applicable, and the new authorized Session-AMBR; and/or + +- calculate the difference between the previously authorized MBR and the new authorized MBR(s) for the authorized PCC Rule(s) related to GBR service data flow(s); + +And then: + +- Calculate the utilized data rate, i.e. the sum of the previously calculated differences, which is to be subtracted from the Remaining Maximum Slice Data rate. + +NOTE 1: For example, when the PCF modifies as part of the same operation the MBR of PCC Rule A from 100 to 150 and the MBR of PCC Rule B from 30 to 20, deletes PCC Rule C with an MBR of 50 and adds a PCC Rule D of MBR 75, the final calculated value will be $+50-10-50+75$ , i.e. 65. If the authorized Session-AMBR is also updated from 1000 to 2000, the final derived value will be 1065. + +NOTE 2: The utilized data rate can be a negative value. In this case, the final Remaining Maximum Slice Data Rate is increased. + +Therefore, the PCF shall behave as follows: + +- At PDU session establishment, the PCF shall check whether the Remaining Maximum Slice Data Rate is higher than the calculated utilized data rate (e.g. based on the authorized Session-AMBR). If it is the case, the PCF shall deduct the value of the utilized data rate from the Remaining Maximum Slice Data Rate for the concerned S-NSSAI in the UDR. If however the Remaining Maximum Slice Data Rate is not sufficient, the PCF may reject the establishment of the SM Policy Association with an HTTP "403 Forbidden" response message including the "cause" attribute of the ProblemDetails data structure set to "EXCEEDED\_SLICE\_DATA\_RATE". +- At PDU session modification initiated by the SMF, the PCF shall check whether the Remaining Maximum Slice Data Rate is higher than the calculated utilized data rate (e.g. based on the authorized Session-AMBR). If it is the case, the PCF shall deduct the value of the utilized data rate from the Remaining Maximum Slice Data Rate for the concerned S-NSSAI in the UDR. If however the Remaining Maximum Slice Data Rate is not sufficient, the PCF may reject the modification of the SM Policy Association with an HTTP "403 Forbidden" response message including the "cause" attribute of the ProblemDetails data structure set to "EXCEEDED\_SLICE\_DATA\_RATE". +- When a PCC rule of a GBR service data flow is installed, modified, removed, activated or deactivated in the SMF, + - the PCF shall derive the authorized QoS for the service data flow and the associated utilized data rate and update the Remaining Maximum Slice Data Rate for the concerned S-NSSAI in the UDR accordingly; + - the PCF may request the SMF to confirm that the resources associated to that PCC rule are successfully allocated as defined in clause 4.2.6.5.5 or released as defined in clauses 4.2.3.13 and 4.2.4.12; + - if the SMF reports that some of or all the resources cannot be successfully allocated, the PCF shall recalculate the authorized QoS for the service data flow and the associated utilized data rate and update the Remaining Maximum Slice Data Rate for the concerned S-NSSAI in the UDR accordingly. +- When the authorized Session-AMBR changes and/or one or several PCC Rule(s) of a GBR service data flow(s) are installed, removed or modified, the PCF shall calculate the new utilized data rate and update the Remaining Maximum Slice Data Rate for that S-NSSAI in the UDR accordingly. +- At PDU session termination, the PCF shall add the value of the related previously utilized data rate (i.e. based on the authorized Session-AMBR allocated to the PDU session and the previously utilized data rate by the removed PCC Rule(s) related to GBR service data flow(s)) to the Remaining Maximum Slice Data Rate for the concerned S-NSSAI in the UDR. +- If the Remaining Maximum Slice Data Rate for that S-NSSAI reaches a (operator defined) threshold that indicates that it is closer or equal to zero, the PCF may apply policy decision(s) to strengthen the traffic restrictions for the concerned PDU Session(s). +- If the Remaining Maximum Slice Data Rate for that S-NSSAI returns to a value below the (operator defined) threshold, the PCF may apply policy decision(s) to recover the initially derived value(s) for the concerned PDU Session(s). + +NOTE 3: While the Remaining Maximum Slice Data Rate is relatively high, the PCF can be configured to maintain a local Remaining Maximum Slice Data Rate and to only interact with the UDR to update the Remaining Maximum Slice Data Rate when a certain threshold is reached, or a certain time window has passed. The higher the configured values are the lower the chances for an accurate limitation of the slice data rate becomes. When multiple PCFs for the same S-NSSAI are deployed, each PCF can also subscribe to the change of the Network slice specific policy control data in the UDR. The UDR will then send a notification to each subscribed PCF when the Remaining Maximum Slice Data Rate per S-NSSAI changes. + +NOTE 4: Multiple PCFs responsible for PDU Sessions of UEs to the same S-NSSAI can read and update the Remaining Maximum Slice Data Rate for the S-NSSAI in the UDR using the conditional requests with preconditions for the update of the Remaining Maximum Slice Data Rate, this mechanism using Etags is defined in Table 5.2.2.2-2 of 3GPP TS 29.500 [4] to ensure a proper update of the UDR data in case of simultaneous access from different PCFs. + +#### 4.2.6.8.3 Network slice data rate policy control with assistance of the NWDAF + +If the NWDAF is used for network slice data rate policy control, the PCF uses the Data Volume Dispersion Analytics provided by the NWDAF. For this purpose, the PCF subscribes to the NWDAF for periodic reporting of the Data Volume Dispersion Analytics statistics for all the UEs using the concerned network slice. The PCF subscribes to the NWDAF for Data Volume Dispersion Analytics reporting at the establishment of the first PDU session within the concerned S-NSSAI (subject to network slice data rate limitation) and cancels this subscription at the termination of the last PDU session within the concerned S-NSSAI as described in 3GPP TS 29.520 [51]. + +The PCF calculates the utilized data rate of the S-NSSAI by using the Data Volume Dispersion Analytics statistics reported by the NWDAF. When the utilized data rate of the S-NSSAI in UL and/or DL is getting close to or exceeding respectively the value of the "mbrUI" attribute and/or the value of the "mbrDI" attribute of the SlicePolicyData data structure as defined in 3GPP TS 29.519 [15], based on operator policy, the PCF may apply policy decision(s) to strengthen the traffic restrictions for individual PDU sessions and/or PCC rules. For example: + +- The PCF may reject the creation or modification of SM Policy Associations that require the increase of the utilized data rate for the S-NSSAI with an HTTP "403 Forbidden" response message including the "cause" attribute of the ProblemDetails data structure set to "EXCEEDED\_SLICE\_DATA\_RATE". +- The PCF may refrain from sending new and/or updated PCC Rules that require the increase of the utilized data rate. + +When the utilized data rate of the S-NSSAI in UL and/or DL falls below respectively the value of the "mbrUI" attribute and/or the value of the "mbrDI" attribute of the SlicePolicyData data structure, the PCF may relax the traffic restrictions for individual PDU sessions and/or PCC rules. + +When multiple PCFs for the same S-NSSAI are deployed, each PCF subscribes to the analytics from the NWDAF separately. + +NOTE: When multiple PCFs are used for the concerned S-NSSAI, the NWDAF triggers Data Volume Dispersion Analytics notifications towards all these PCFs, but their policy decisions can be different. + +#### 4.2.6.9 Group related data rate policy control + +##### 4.2.6.9.1 General + +A PCF that supports group related data rate policy control shall be able to control and manage the group data rate for 5G VN groups. In order to do so, the PCF shall perform the same procedures as the ones defined for network slice related data rate policy control defined in clauses 4.2.6.8 for the PDU session(s) of the UE(s) belonging to a 5G VN group, with the following differences: + +- Only the PCF-based method shall be applicable for group related data rate policy control, i.e., the provisions of clause 4.2.6.8.3 shall not apply for group related data rate policy control. +- The provisions related to slice related data rate policy control for an S-NSSAI shall apply for group related data rate policy control for a 5G VN Group. + +- Instead of configuring the Maximum Slice Data Rate per S-NSSAI by the operator, the Maximum Group Data Rate per 5G VN Group is either provisioned by the AF to the UDR (for "Subscription Data") via the NEF/UDM as part of the 5G VN group subscription data using the procedures defined in 3GPP TS 29.522 [59] and 3GPP TS 29.503 [34] and/or configured by the operator. When the Maximum Group Data Rate is provisioned by the AF, the PCF shall retrieve it from the UDR (for "Subscription Data"). +- Instead of handling the Remaining Maximum Slice Data Rate per S-NSSAI, the UDR and PCF shall handle the Remaining Maximum Group Data Rate per 5G VN Group. +- Instead of calculating the utilized data rate based on the value(s) of the authorized Session-AMBR and the MBR of every GBR SDF for every PDU Session of a network slice identified by an S-NSSA, the PCF shall calculate the utilized data rate based on the value(s) of the authorized Session-AMBR and the MBR of every GBR SDF for every PDU Session of the concerned 5G VN Group. +- Instead of returning the "EXCEEDED\_SLICE\_DATA\_RATE" application error, the PCF shall return the "EXCEEDED\_GROUP\_DATA\_RATE" application error within the "403 Forbidden" error response. + +#### 4.2.6.10 Policy Provisioning for eXtended Reality and Interactive Media Services + +##### 4.2.6.10.1 Support for delivery of multi-modal services + +Multi-modal services consist of several data flows (named as multi-modal flows) that relate to each other and may come from different sources. Each data flow (single-modal data) may be seen as one type of data (for example audio, video, positioning, haptic data) associated with the same communication service. + +The provision of PCC Rules corresponding to multi-modal services shall be performed as described in clause 4.2.6.2.1 "Provisioning of PCC rules". + +For the delivery of multi-modal services, the PCF shall: + +- derive the applicable PCC rule(s) and apply the required QoS as described in clause 4.2.3.22. The PCF may use the multi-modal Id received from the AF (either directly or via NEF), as specified in 3GPP TS 29.514 [17], to derive the correct PCC rules and apply QoS policies; and +- when the received multi-modal service requirements include QoS monitoring requirements, generate the authorized QoS Monitoring policy for each flow as described in clause 4.2.3.25. The PCF shall use the QoS monitoring requirement received from the AF (either directly or via NEF), as specified in 3GPP TS 29.514 [17]. + +#### 4.2.7 Handling of requests which collide with an existing SM Policy Association + +The PCF may receive an Originating Time Stamp parameter within the 3gpp-Sbi-Origination-Timestamp header, which is set by the AMF, by the Npcf\_SMPolicyControl\_Create service request. + +NOTE 1: The SMF forwards the Origination Time Stamp to the PCF, when received from the AMF to allow the handling of colliding requests at the PCF based on network conditions. + +Upon receipt of a Npcf\_SMPolicyControl\_Create service request which collides with an existing SM Policy Association for the same UE (i.e. same values of "supi" attribute) and the same PDU session Id (i.e. same values of "pduSessionId" attribute), the PCF shall accept the new request only if it contains a more recent timestamp within the 3gpp-Sbi-Origination-Timestamp header than the origination timestamp stored for the existing SM Policy Association. An incoming Npcf\_SMPolicyControl\_Create service request shall be considered as more recent than an existing SM Policy Association and be accepted if no 3gpp-Sbi-Origination-Timestamp header was provided for at least one of the two SM Policy Associations. The PCF shall reject an incoming request whose timestamp is less recent than the timestamp of the existing SM Policy Association with the HTTP status code "403 Forbidden" and the application error "LATE\_OVERLAPPING\_REQUEST". + +NOTE 2: When the PCF accepts the new request that contains a more recent timestamp within the 3gpp-Sbi-Origination-Timestamp header than the timestamp stored for the SM Policy Association, the PCF performs implementation specific, e.g. locally deletes the existing Individual SM Policy Association. + +## 4.2.8 UE IP address support + +As specified in 3GPP TS 23.501 [2], the following types of UE IP addresses may be assigned to a PDU session and may be received by the PCF: + +- IPv4 address; and/or +- /64 IPv6 Prefix; or +- IPv6 prefix shorter than the default /64 prefix when IPv6 Prefix Delegation applies. + +More than one UE IP addresses may be assigned to a PDU session, as specified in clause 4.2.4.11. + +--- + +# 5 Npcf\_SMPolicyControl Service API + +## 5.1 Introduction + +The Npcf\_SMPolicyControl Service shall use the Npcf\_SMPolicyControl API. + +The API URI of the Npcf\_SMPolicyControl API shall be: + +**{apiRoot}/** + +The request URIs used in HTTP request from the NF service consumer towards the PCF shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.: + +**{apiRoot}//** + +with the following components: + +- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5]. +- The shall be "npcf-smpolicycontrol". +- The shall be "v1". +- The shall be set as described in clause 5.3. + +## 5.2 Usage of HTTP + +### 5.2.1 General + +HTTP/2, IETF RFC 9113 [8], shall be used as specified in clause 5 of 3GPP TS 29.500 [4]. + +HTTP/2, shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4]. + +An OpenAPI [10] specification of HTTP messages and content bodies for the Npcf\_SMPolicyControl is contained in Annex A. + +### 5.2.2 HTTP standard headers + +#### 5.2.2.1 General + +See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers. + +### 5.2.2.2 Content type + +JSON, IETF RFC 8259 [9], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json". + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [31]. + +## 5.2.3 HTTP custom headers + +### 5.2.3.1 General + +The Npcf\_SMPolicyControl API shall support HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] and may support HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4]. + +### 5.2.3.2 3gpp-Sbi-Origination-Timestamp + +The header contains the date and time (with a millisecond granularity) when the originating entity initiated the request as specified in clause 6.1.2.3.2 of 3GPP TS 29.502 [22]. + +## 5.3 Resources + +### 5.3.1 Resource Structure + +![Diagram showing the resource URI structure of the Npcf_SMPolicyControl API. The root path is {apiRoot}/npcf-smpolicycontrol/v1. It branches to /sm-policies, which then branches to /{smPolicyId}. From /{smPolicyId}, two optional sub-paths are shown: /update and /delete, both enclosed in dashed boxes.](cd0f8f598fb2fa15165967e75378f42a_img.jpg) + +``` +graph TD; Root["{apiRoot}/npcf-smpolicycontrol/v1"] --- SmPolicies["/sm-policies"]; SmPolicies --- SmPolicyId["/{smPolicyId}"]; SmPolicyId --- Update["/update"]; SmPolicyId --- Delete["/delete"]; style Update stroke-dasharray: 5 5; style Delete stroke-dasharray: 5 5; +``` + +Diagram showing the resource URI structure of the Npcf\_SMPolicyControl API. The root path is {apiRoot}/npcf-smpolicycontrol/v1. It branches to /sm-policies, which then branches to /{smPolicyId}. From /{smPolicyId}, two optional sub-paths are shown: /update and /delete, both enclosed in dashed boxes. + +**Figure 5.3.1-1: Resource URI structure of the Npcf\_SMPolicyControl API** + +Table 5.3.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 5.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|----------------------|----------------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| SM Policies | /sm-policies | POST | Create a new Individual SM Policies resource for a SUPI or a PEI and PDU Session ID supplied by the NF service consumer. | +| Individual SM Policy | /sm-policies/{smPolicyId} | GET | Read an Individual SM Policies resource. | +| | /sm-policies/{smPolicyId}/delete | delete (POST) | Delete an Individual SM Policies resource. | +| | /sm-policies/{smPolicyId}/update | update (POST) | Update an Individual SM Policies resource when a policy control request event is met or an error of policy enforcement occurs. | + +## 5.3.2 Resource: SM Policies + +### 5.3.2.1 Description + +This resource represents the collection of the individual SM Policies created in the PCF. + +### 5.3.2.2 Resource definition + +Resource URI: {apiRoot}/npcf-sm-policycontrol/v1/sm-policies + +This resource shall support the resource URI variables defined in table 5.3.2.2-1. + +**Table 5.3.2.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|---------|-----------|----------------| +| apiRoot | string | See clause 5.1 | + +### 5.3.2.3 Resource Standard Methods + +#### 5.3.2.3.1 POST + +This method shall support the URI query parameters specified in table 5.3.2.3.1-1. + +**Table 5.3.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 5.3.2.3.1-2 and the response data structures and response codes specified in table 5.3.2.3.1-3. + +**Table 5.3.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|---------------------|---|-------------|-----------------------------------------------------------| +| SmPolicyContextData | M | 1 | Parameters to create an individual SM policies resources. | + +**Table 5.3.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SmPolicyDecision | M | 1 | 201 Created | An individual SM Policy resources for the SUPI and PDU session id are created successfully. | +| ProblemDetails | O | 0..1 | 400 Bad Request | (NOTE 2) | +| ProblemDetails | O | 0..1 | 403 Forbidden | (NOTE 2) | +| n/a | | | 308 Permanent Redirect | The URI of the PCF within the existing PCF binding information stored in the BSF for the indicated combination is returned in the non-roaming or home-routed scenario. (NOTE 3) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] shall also apply. +NOTE 2: Failure cases are described in clause 5.7. +NOTE 3: Only applicable to the "SamePcf" feature as defined in clause 5.8. + +**Table 5.3.2.3.1-4: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/npcf-smolicycontrol/v1/sm-policies/{smPolicyId} | + +**Table 5.3.2.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the PCF within the existing PCF binding information stored in the BSF for the indicated combination. | + +## 5.3.2.4 Resource Custom Operations + +None. + +## 5.3.3 Resource: Individual SM Policy + +### 5.3.3.1 Description + +The individual SM Policy resource represents an individual SM Policy created in the PCF and associated with the SUPI and PDU session ID. + +### 5.3.3.2 Resource definition + +Resource URI: {apiRoot}/npcf-smolicycontrol/v1/sm-policies/{smPolicyId} + +This resource shall support the resource URI variables defined in table 5.3.3.2-1. + +**Table 5.3.3.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|------------|-----------|---------------------------------------------------------| +| apiRoot | string | See clause 5.1 | +| smPolicyId | string | Unique identifier of the individual SM Policy resource. | + +### 5.3.3.3 Resource Standard Methods + +#### 5.3.3.3.1 GET + +This method shall support the URI query parameters specified in table 5.3.3.3.1-1. + +**Table 5.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 5.3.3.3.1-2 and the response data structures and response codes specified in table 5.3.3.3.1-3. + +**Table 5.3.3.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 5.3.3.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------| +| SmPolicyControl | M | 1 | 200 OK | An individual SM Policy resources for the SUPI and PDU session id are returned successfully. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during Individual SM policy retrieval.
Applicable if the feature "ES3XX" is supported.
(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during Individual SM policy retrieval.
Applicable if the feature "ES3XX" is supported.
(NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] shall also apply. +NOTE 2: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +**Table 5.3.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected | + +**Table 5.3.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the request is redirected | + +### 5.3.3.4 Resource Custom Operations + +#### 5.3.3.4.1 Overview + +**Table 5.3.3.4.1-1: Custom operations** + +| Operation Name | Custom operation URI | Mapped HTTP method | Description | +|----------------|----------------------------------|--------------------|------------------------------------------| +| delete | /sm-policies/{smPolicyId}/delete | delete (POST) | Delete an individual SM Policy resource. | +| update | /sm-policies/{smPolicyId}/update | update (POST) | Update an individual SM Policy resource. | + +#### 5.3.3.4.2 Operation: delete + +##### 5.3.3.4.2.1 Description + +##### 5.3.3.4.2.2 Operation Definition + +This custom operation deletes an individual SM Policy resource in the PCF. + +This operation shall support the request data structures specified in table 5.3.3.4.2.2-1 and the response data structure and response codes specified in table 5.3.3.4.2.2-2. + +**Table 5.3.3.4.2.2-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|--------------------|---|-------------|--------------------------------------------------------------------------------------------| +| SmPolicyDeleteData | O | 0..1 | Parameters to be sent by the NF service consumer when the individual SM policy is deleted. | + +**Table 5.3.3.4.2.2-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | This case represents a successful deletion of the individual SM policy resource. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during Individual SM policy deletion.
Applicable if the feature "ES3XX" is supported.
(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during Individual SM policy deletion.
Applicable if the feature "ES3XX" is supported.
(NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] shall also apply. + +NOTE 2: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +**Table 5.3.3.4.2.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected | + +**Table 5.3.3.4.2.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected | + +### 5.3.3.4.3 Operation: update + +#### 5.3.3.4.3.1 Description + +#### 5.3.3.4.3.2 Operation Definition + +This custom operation updates an individual SM Policy resource in the PCF. + +This operation shall support the request data structures specified in table 5.3.3.4.3.2-1 and the response data structure and response codes specified in table 5.3.3.4.3.2-2. + +**Table 5.3.3.4.3.2-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|---------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------| +| SmPolicyUpdateContextData | M | 1 | Parameters to be sent by the NF service consumer when the individual SM policy is updated. It indicates the occurred changes. | + +**Table 5.3.3.4.3.2-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| SmPolicyDecision | M | 1 | 200 OK | An individual SM Policy resources is updated successfully. Response body includes the policy decision changes. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during Individual SM policy modification.
Applicable if the feature "ES3XX" is supported.
(NOTE 3) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during Individual SM policy modification.
Applicable if the feature "ES3XX" is supported.
(NOTE 3) | +| ProblemDetails | O | 0..1 | 400 Bad Request | (NOTE 2) | +| ProblemDetails | O | 0..1 | 403 Forbidden | (NOTE 2) | +| ProblemDetails | O | 0..1 | 404 Not Found | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] shall also apply. +NOTE 2: Failure cases are described in clause 5.7. +NOTE 3: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +**Table 5.3.3.4.3.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected | + +**Table 5.3.3.4.3.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected | + +## 5.4 Custom Operations without associated resources + +None. + +## 5.5 Notifications + +### 5.5.1 General + +**Table 5.5.1-1: Notifications** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|---------------------------------------------------|-----------------------------|---------------------------------|----------------------------------------------------| +| Policy Update Notification | {notificationUri}/update | update (POST) | Policy Update Notification. | +| Request for termination of the policy association | {notificationUri}/terminate | terminate (POST) | Request for termination of the policy association. | + +### 5.5.2 Policy Update Notification + +#### 5.5.2.1 Description + +This notification is used by the PCF to update the policy. + +#### 5.5.2.2 Operation Definition + +This operation shall support the request data structures specified in table 5.5.2.2-1 and the response data structure and response codes specified in table 5.5.2.2-2. + +**Table 5.5.2.2-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------|---|-------------|--------------------------------------------| +| SmPolicyNotification | M | 1 | Update the SM policies provided by the PCF | + +**Table 5.5.2.2-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The SM policies are updated successfully. | +| UeCampingRep | O | 0..1 | 200 OK | The current applicable values corresponding to the policy control request trigger is reported. | +| array(PartialSuccessReport) | O | 1..N | 200 OK | Some of the PCC rules and/or session rule provisioned by the PCF are not installed/activated successfully and/or the storage of some of the provisioned policy decisions and/or condition data has failed. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during SM policy notification.
Applicable if the feature "ES3XX" is supported. (NOTE 3) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during SM policy notification.
Applicable if the feature "ES3XX" is supported. (NOTE 3) | +| ErrorReport | M | 1 | 400 Bad Request | The SM policies including all the PCC rules, session rules and policy decisions and condition data provisioned by the PCF are not installed/activated and stored successfully. | +| array(PolicyDecisionFailureCode) | O | 1..N | 200 OK | Provisioning of some of the policy decision and/condition data which are not referred by any PCC rules or session rule has failed. | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] shall also apply. +NOTE 2: Failure cases are described in clause 5.7. +NOTE 3: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +**Table 5.5.2.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected | + +**Table 5.5.2.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected | + +## 5.5.3 Request for termination of the policy association + +### 5.5.3.1 Description + +This notification is used by the PCF to request the termination of a policy association. + +### 5.5.3.2 Operation Definition + +This operation shall support the request data structures specified in table 5.5.3.2-1 and the response data structure and response codes specified in table 5.5.3.2-2. + +**Table 5.5.3.2-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------------|---|-------------|----------------------------------------------| +| TerminationNotification | M | 1 | Request to terminate the policy association. | + +**Table 5.5.3.2-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The request for policy association termination was received. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during SM policy termination notification.
Applicable if the feature "ES3XX" is supported.
(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during SM policy termination notification.
Applicable if the feature "ES3XX" is supported.
(NOTE 2) | + +NOTE: 1 The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] shall also apply. +NOTE 2: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +**Table 5.5.3.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected | + +**Table 5.5.3.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected | + +## 5.6 Data Model + +### 5.6.1 General + +This clause specifies the application data model supported by the API. + +The Npcf\_SMPolicyControl API allows the NF service consumer to retrieve the session management related policy from the PCF as defined in 3GPP TS 23.503 [6]. + +Table 5.6.1-1 specifies the data types defined for the Npcf\_SMPolicyControl service based interface protocol. + +**Table 5.6.1-1: Npcf\_SMPolicyControl specific Data Types** + +| Data type | Section defined | Description | Applicability | +|-----------------------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| 5GSmCause | 5.6.3.2 | Indicates the 5GSM cause code value. | RAN-NAS-Cause | +| AdditionalAccessInfo | 5.6.2.43 | Indicates the combination of additional Access Type and RAT Type for MA PDU session | ATSSS | +| AccNetChargingAddress | 5.6.2.35 | Identifies the address of the network node performing charging and used for charging applications. | | +| AccNetChId | 5.6.2.23 | Contains the access network charging identifier for the PCC rule(s) or whole PDU session. | | +| AccuUsageReport | 5.6.2.18 | Contains the accumulated usage report information. | UMC | +| AfSigProtocol | 5.6.3.10 | Indicates the protocol used for signalling between the UE and the AF. | ProvAFsignalFlow | +| AppDetectionInfo | 5.6.2.22 | Contains the detected application's traffic information. | ADC | +| ApplicationDescriptor | 5.6.3.2 | Defines the Application Descriptor for an ATSSS rule. | ATSSS | +| AtsssCapability | 5.6.3.26 | Contains the ATSSS capability supported for the MA PDU Session. | ATSSS | +| AuthorizedDefaultQos | 5.6.2.34 | Authorized Default QoS. | | +| BridgeManagementContainer | 5.6.2.47 | Contains the UMIC. | TimeSensitive Networking | +| CalleeInfo | 5.6.2.55 | Identifies the callee information. | VBCforIMS | +| CallInfo | 5.6.2.54 | Identifies the caller and callee information. | VBCforIMS | +| ChargingData | 5.6.2.11 | Contains charging related parameters. | | +| ChargingInformation | 5.6.2.17 | Contains the addresses, and if available, the instance ID and set ID, of the charging functions. | | +| ConditionData | 5.6.2.9 | Contains conditions for applicability of a rule. | | +| CreditManagementStatus | 5.6.3.16 | Indicates the reason of the credit management session failure. | | +| DownlinkDataNotificationControl | 5.6.2.48 | Contains the downlink data notification control information. | DDNEventPolicyControl | +| DownlinkDataNotificationControlRm | 5.6.2.49 | This data type is defined in the same way as the "DownlinkDataNotificationControl" data type, but with the OpenAPI "nullable: true" property. | DDNEventPolicyControl2 | +| EpsRanNasRelCause | 5.6.3.2 | Indicates the RAN or NAS release cause code information in 3GPP-EPS access type or indicates the TWAN or untrusted WLAN release cause code information in Non-3GPP-EPS access type. | RAN-NAS-Cause | +| ErrorReport | 5.6.2.36 | Contains the PCC rule and/or session rule and/or policy decision and/or condition data reports. | | +| FailureCause | 5.6.3.14 | Indicates the cause of the failure in a Partial Success Report. | | +| FailureCode | 5.6.3.9 | Indicates the reason of the PCC rule failure. | | +| FlowDescription | 5.6.3.2 | Defines a packet filter for an IP flow. | | +| FlowDirection | 5.6.3.3 | Indicates the direction of the service data flow. | | +| FlowDirectionRm | 5.6.3.15 | This data type is defined in the same way as the "FlowDirection" data type, but allows null value. | | +| FlowInformation | 5.6.2.14 | Contains the flow information. | | +| IpMulticastAddressInfo | 5.6.2.46 | Contains the IP multicast addressing information | WWC | +| L4sSupportInfo | 5.6.2.57 | Indicates whether the ECN marking for L4S is available in 5GS for the indicated PCC rules. | L4S | +| MaPduIndication | 5.6.3.25 | Contains the MA PDU session indication, i.e., MA PDU Request or MA PDU Network-Upgrade Allowed. | ATSSS | +| MeteringMethod | 5.6.3.5 | Indicates the metering method. | | +| MulticastAccessControl | 5.6.3.20 | Indicates whether the service data flow, corresponding to the service data flow template, is allowed or not allowed. | WWC | +| NetLocAccessSupport | 5.6.3.27 | Indicates the access network support of the report of the requested access network information. | NetLoc | +| NotificationControlIndication | 5.6.3.29 | Indicates the notification of DDD Status is requested and/or notification of DDN Failure is requested. | DDNEventPolicyControl | + +| | | | | +|---------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| NwdafData | 5.6.2.53 | Indicates the list of NWDAF instance IDs used for the PDU Session and their associated Analytics ID(s) consumed by the NF service consumer. | EneNA | +| PacketFilterContent | 5.6.3.2 | Defines a packet filter for an IP flow. | | +| PacketFilterInfo | 5.6.2.30 | Contains the information from a single packet filter sent from the NF service consumer to the PCF. | | +| PartialSuccessReport | 5.6.2.33 | Includes the information reported by the NF service consumer when some of the PCC rules and/or session rules and/or policy decisions and/or condition data are not successfully installed/activated or stored. | | +| PccRule | 5.6.2.6 | Contains the PCC rule information. | | +| PduSessionRelCause | 5.6.3.24 | Contains the NF service consumer PDU Session release cause. | PDUSessionRelCause, ImmediateTermination | +| PolicyControlRequestTrigger | 5.6.3.6 | Contains the policy control request trigger(s). | | +| PolicyDecisionFailureCode | 5.6.3.28 | Indicates the type of the failed policy decision and/or condition data. | PolicyDecisionErrorHandlering | +| PortManagementContainer | 5.6.2.45 | Contains the port management information container for a port. | TimeSensitive Networking | +| QosCharacteristics | 5.6.2.16 | Contains QoS characteristics for a non-standardized or non-configured 5QI. | | +| QosData | 5.6.2.8 | Contains the QoS parameters. | | +| QosFlowUsage | 5.6.3.13 | Indicates a QoS flow usage information. | | +| QosMonitoringData | 5.6.2.40 | Contains QoS monitoring related control information. | QosMonitoring | +| QosMonitoringReport | 5.6.2.42 | Contains QoS monitoring reporting information. | QosMonitoring | +| QosNotificationControlInfo | 5.6.2.32 | Contains the QoS Notification Control Information. | | +| RanNasRelCause | 5.6.2.28 | Contains the RAN/NAS release cause. | RAN-NAS-Cause | +| RedirectAddressType | 5.6.3.12 | Indicates the redirect address type. | ADC | +| RedirectInformation | 5.6.2.13 | Contains the redirect information. | ADC | +| ReportingFrequency | 5.6.3.22 | Indicates the frequency for the reporting | QosMonitoring | +| ReportingLevel | 5.6.3.4 | Indicates the reporting level. | | +| RequestedQos | 5.6.2.31 | Contains the QoS information requested by the UE. | | +| RequestedQosMonitoringParameter | 5.6.3.21 | Indicates the requested QoS monitoring parameters to be measured. | QosMonitoring | +| RequestedRuleData | 5.6.2.24 | Contains rule data requested by the PCF to receive information associated with PCC rules. | | +| RequestedRuleDataType | 5.6.3.7 | Contains the type of rule data requested by the PCF. | | +| RequestedUsageData | 5.6.2.25 | Contains usage data requested by the PCF requesting usage reports for the corresponding usage monitoring data instances. | UMC | +| RuleOperation | 5.6.3.11 | Indicates a UE initiated resource operation that causes a request for PCC rules. | | +| RuleReport | 5.6.2.27 | Reports the status of PCC rule(s). | | +| RuleStatus | 5.6.3.8 | Indicates the status of PCC or session rule. | | +| ServingNfIdentity | 5.6.2.38 | Contains the serving Network Function identity. | | +| SessionRule | 5.6.2.7 | Contains session level policy information. | | +| SessionRuleFailureCode | 5.6.3.17 | Indicates the reason of the session rule failure. | SessionRuleErrorHandlering | +| SessionRuleReport | 5.6.2.37 | Reports the status of session rule. | SessionRuleErrorHandlering | +| SgsnAddress | 5.6.2.50 | Contains the serving SGSN address. | 2G3GIWK | +| SliceUsgCtrlInfo | 5.6.2.59 | Represents network slice usage control information. | NetSliceUsageCtrl | +| SmPolicyAssociationReleaseCause | 5.6.3.23 | Represents the cause why the PCF requests the termination of the SM policy association. | | +| SmPolicyControl | 5.6.2.2 | Contains the parameters to request the SM policies and the SM policies authorized by the PCF. | | +| SmPolicyContextData | 5.6.2.3 | Contains the parameters to create individual SM policy resource. | | + +| | | | | +|----------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| SmPolicyDecision | 5.6.2.4 | Contains the SM policies authorized by the PCF. | | +| SmPolicyNotification | 5.6.2.5 | Contains the update of the SM policies. | | +| SmPolicyDeleteData | 5.6.2.15 | Contains the parameters to be sent to the PCF when the individual SM policy is deleted. | | +| SmPolicyUpdateContextData | 5.6.2.19 | Contains the met policy control request trigger(s) and corresponding new value(s) or the error report of the policy enforcement. | | +| SteeringFunctionality | 5.6.3.18 | Indicates functionality to support traffic steering, switching and splitting determined by the PCF. | ATSSS | +| SteeringMode | 5.6.2.39 | Contains the steering mode value and parameters determined by the PCF. | ATSSS | +| SteerModeIndicator | 5.6.3.31 | Contains Autonomous load-balance indicator or UE-assistance indicator. | EnATSSS | +| SteerModeValue | 5.6.3.19 | Indicates the steering mode value determined by the PCF. | ATSSS | +| TerminationNotification | 5.6.2.21 | Termination Notification. | | +| ThresholdValue | 5.6.2.52 | Contains the threshold value(s) for RTT and/or Packet Loss Rate. | EnATSSS | +| TrafficControlData | 5.6.2.10 | Contains parameters determining how flows associated with a PCCRule are treated (blocked, redirected, etc). | | +| TrafficParaData | 5.6.2.56 | Contains Traffic Parameter(s) related control information. | PowerSaving | +| TrafficParameterMeas | 5.6.3.32 | Indicates the traffic parameters to be measured. | PowerSaving | +| TsnBridgeInfo | 5.6.2.41 | Contains parameters that describe and identify the TSC user plane node. | TimeSensitive Networking | +| TsnPortNumber | 5.6.3.2 | Contains a port number. | TimeSensitive Networking | +| UeCampingRep | 5.6.2.26 | Contains the current applicable values corresponding to the policy control request triggers. | | +| UeInitiatedResourceRequest | 5.6.2.29 | Indicates a UE requests specific QoS handling for selected SDF. | | +| UePolicyContainer | 5.6.3.2 | Contains a UE policy container | EpsUrsp | +| UpPathChgEvent | 5.6.2.20 | Contains the UP path change event subscription from the AF. | TSC | +| UrspEnforcementInfo | 5.6.3.2 | Contains the report of URSP rule(s) enforcement information as received from the UE. | URSPEnforcement | +| UsageMonitoringData | 5.6.2.12 | Contains usage monitoring related control information. | UMC | + +Table 5.6.1-2 specifies data types re-used by the Npcf\_SMPolicyControl service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Npcf\_SMPolicyControl service based interface. + +**Table 5.6.1-2: Npcf\_SMPolicyControl re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-----------------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| 5GMmCause | 3GPP TS 29.571 [11] | Contains the cause value of 5GMM protocol. | RAN-NAS-Cause | +| 5Qi | 3GPP TS 29.571 [11] | Unsigned integer representing a 5G QoS Identifier (see clause 5.7.2.1 of 3GPP TS 23.501 [2]), within the range 0 to 255. | | +| 5QiPriorityLevel | 3GPP TS 29.571 [11] | Unsigned integer indicating the 5Qi Priority Level (see clauses 5.7.3.3 and 5.7.4 of 3GPP TS 23.501 [2]), within the range 1 to 127. Values are ordered in decreasing order of priority, i.e. with 1 as the highest priority and 127 as the lowest priority. | | +| 5QiPriorityLevelRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "5QiPriorityLevel" data type, but with the OpenAPI "nullable: true" property. | | +| AccessType | 3GPP TS 29.571 [11] | The identification of the type of access network. | | +| AccessTypeRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "AccessType" data type, but with the OpenAPI "nullable: true" property. | ATSSS | +| Ambr | 3GPP TS 29.571 [11] | Session-AMBR. | | +| AnGwAddress | 3GPP TS 29.514 [17] | Carries the control plane address of the access network gateway. (NOTE 1) | | +| ApplicationChargingId | 3GPP TS 29.571 [11] | Application provided charging identifier allowing correlation of charging information. | AF_Charging_Identifier | +| ApplicationId | 3GPP TS 29.571 [11] | Application Identifier | UPEAS | +| Arp | 3GPP TS 29.571 [11] | ARP. | | +| AverWindow | 3GPP TS 29.571 [11] | Averaging Window. | | +| AverWindowRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "AverWindow" data type, but with the OpenAPI "nullable: true" property. | | +| BatOffsetInfo | 3GPP TS 29.514 [17] | Contains the offset of the BAT and the optionally adjusted periodicity. | EnTSCAC | +| BitRate | 3GPP TS 29.571 [11] | String representing a bit rate that shall be formatted as follows:

pattern: " \d+(\.\d+)? (bps Kbps Mbps Gbps Tbps)"
Examples:
"125 Mbps", "0.125 Gbps", "125000 Kbps". | | +| BitRateRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "BitRate" data type, but with the OpenAPI "nullable: true" property. | | +| Bytes | 3GPP TS 29.571 [11] | String with format "byte". | TimeSensitive Networking | +| ChargingId | 3GPP TS 29.571 [11] | Charging identifier allowing correlation of charging information. | | +| ContentVersion | 3GPP TS 29.514 [17] | Indicates the content version of a PCC rule. It uniquely identifies a version of the PCC rule as defined in clause 4.2.6.2.14. | RuleVersionin
g | +| DateTime | 3GPP TS 29.571 [11] | String with format "date-time" as defined in OpenAPI Specification [10]. | | +| DateTimeRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "DateTime" data type, but with the OpenAPI "nullable: true" property. | | +| DddTrafficDescriptor | 3GPP TS 29.571 [11] | Traffic Descriptor | DDNEventPolicyControl | +| DiDataDeliveryStatus | 3GPP TS 29.571 [11] | Downlink data delivery status. | DDNEventPolicyControl | +| DnaiChangeType | 3GPP TS 29.571 [11] | Describes the types of DNAI change. | | +| Dnn | 3GPP TS 29.571 [11] | The DNN the user is connected to. | | +| DnnSelectionMode | 3GPP TS 29.502 [22] | DNN selection mode. | DNNSelection
Mode | +| DurationSec | 3GPP TS 29.571 [11] | Identifies a period of time in units of seconds. | | + +| | | | | +|-------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| DurationSecRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "DurationSec" data type, but with the OpenAPI "nullable: true" property. | | +| EasIpReplacementInfo | 3GPP TS 29.571 [11] | Contains EAS IP replacement information for a Source and a Target EAS. | EASIPreplacement | +| EthFlowDescription | 3GPP TS 29.514 [17] | Defines a packet filter for an Ethernet flow. (NOTE 2) | | +| ExtMaxDataBurstVol | 3GPP TS 29.571 [11] | Maximum Data Burst Volume. | EMDBV | +| ExtMaxDataBurstVolRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "ExtMaxDataBurstVol" data type, but with the OpenAPI "nullable: true" property. | EMDBV | +| Metadata | 3GPP TS 29.571 [11] | This datatype contains opaque information for the service functions in the N6-LAN that is provided by AF and transparently sent to UPF. | SFC | +| FinalUnitAction | 3GPP TS 32.291 [19] | Indicates the action to be taken when the user's account cannot cover the service cost. | | +| FlowStatus | 3GPP TS 29.514 [17] | Describes whether the IP flow(s) are enabled or disabled. The value "REMOVED" is not applicable to Npcf_SMPolicyControl service. | | +| FqdnPatternMatchingRule | 3GPP TS 29.571 [11] | Identifies the FQDN pattern matching rule. | HR-SBO | +| Gpsi | 3GPP TS 29.571 [11] | Identifies a GPSI. | | +| GroupId | 3GPP TS 29.571 [11] | Identifies a group of internal globally unique ID. | | +| Guami | 3GPP TS 29.571 [11] | Globally Unique AMF Identifier. | | +| InvalidParam | 3GPP TS 29.571 [11] | Invalid Parameters for the reported failed policy decisions | ExtPolicyDecisionErrorHandling | +| IpIndex | 3GPP TS 29.519 [15] | Information that identifies which IP pool or external server is used to allocate the IP address. | | +| IpAddr | 3GPP TS 29.571 [11] | Identifies an IP address. | HR-SBO | +| Ipv4Addr | 3GPP TS 29.571 [11] | Identifies an Ipv4 address. | | +| Ipv4AddrMask | 3GPP TS 29.571 [11] | String identifying an IPv4 address mask. | | +| Ipv6Addr | 3GPP TS 29.571 [11] | Identifies an IPv6 address. | | +| Ipv6Prefix | 3GPP TS 29.571 [11] | The Ipv6 prefix allocated for the user. | | +| MacAddr48 | 3GPP TS 29.571 [11] | MAC Address. | | +| MaxDataBurstVol | 3GPP TS 29.571 [11] | Maximum Data Burst Volume. | | +| MaxDataBurstVolRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "MaxDataBurstVol" data type, but with the OpenAPI "nullable: true" property. | | +| NfInstanceId | 3GPP TS 29.571 [11] | The NF instance identifier. | | +| NfSetId | 3GPP TS 29.571 [11] | The NF set identifier. | | +| NgApCause | 3GPP TS 29.571 [11] | Contains the cause value of NgAP protocol. | RAN-NAS-Cause | +| NullValue | 3GPP TS 29.571 [11] | JSON's null value, used as an explicit value of an enumeration. | | +| NwdafEvent | 3GPP TS 29.520 [51] | Analytics ID consumed by the NF service consumer. | EneNA | +| PacketDelBudget | 3GPP TS 29.571 [11] | Packet Delay Budget. | | +| PacketErrRate | 3GPP TS 29.571 [11] | Packet Error Rate. | | +| PacketLossRateRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "PacketLossRate" data type, but with the OpenAPI "nullable: true" property. | | +| PcfUeCallbackInfo | 3GPP TS 29.571 [11] | Contains the PCF for the UE callback URI and SBA binding information, if available | AMInfluence | +| PduSessionId | 3GPP TS 29.571 [11] | The identification of the PDU session. | | +| PduSessionType | 3GPP TS 29.571 [11] | Indicate the type of a PDU session. | | +| PduSetQosParaRm | 3GPP TS 29.571 [11] | Represents the PDU Set level QoS parameters to be modified. | PDUSetHandling | +| Pei | 3GPP TS 29.571 [11] | The Identification of a Permanent Equipment. | | +| PeriodicityInfo | 3GPP TS 29.514 [17] | Indicates the time period between the start of the two data bursts in Uplink and/or Downlink direction. | PowerSaving | + +| | | | | +|--------------------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| PlmnIdNid | 3GPP TS 29.571 [11] | The identification of the Network: The PLMN Identifier (the mobile country code and the mobile network code) or the SNPN Identifier (the PLMN Identifier and the NID). | | +| PresenceInfo | 3GPP TS 29.571 [11] | Contains the information which describes a Presence Reporting Area. | PRA | +| PresenceInfoRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "PresenceInfo" data type, but with the OpenAPI "nullable: true" property. | PRA | +| ProblemDetails | 3GPP TS 29.571 [11] | Contains a detailed information about an error. | | +| ProtoDesc | 3GPP TS 29.514 [17] | Represents Protocol description of the media flow | PDUSetHandling | +| QosNotifType | 3GPP TS 29.514 [17] | Indicates whether the GBR targets for the indicated SDFs are "NOT_GUARANTEED" or "GUARANTEED" again. | | +| QosResourceType | 3GPP TS 29.571 [11] | Indicates whether the resource type is GBR, delay critical GBR, or non-GBR. | | +| RatingGroup | 3GPP TS 29.571 [11] | Identifier of a rating group. | | +| RatType | 3GPP TS 29.571 [11] | The identification of the RAT type. | | +| RedirectResponse | 3GPP TS 29.571 [11] | Contains redirection related information. | ES3XX | +| RedundantPduSessionInformation | 3GPP TS 29.502 [22] | Contains the Redundant PDU session information, i.e, the RSN and the PDU Session Pair ID. | URSPEnforcement | +| RouteToLocation | 3GPP TS 29.571 [11] | A traffic routes to applications location. | TSC | +| SatelliteBackhaulCategory | 3GPP TS 29.571 [11] | Indicates the satellite backhaul category or non-satellite backhaul. | SatBackhaulCategoryChg | +| ServerAddressingInfo | 3GPP TS 29.571 [11] | Contains the Provisioning Server information that provisions the UE with credentials and other data to enable SNPN access. | PvsSupport | +| ServiceId | 3GPP TS 29.571 [11] | Identifier of a service. | | +| Snssai | 3GPP TS 29.571 [11] | Identifies the S-NSSAI. | | +| SscMode | 3GPP TS 29.571 [11] | Represents the service and session continuity mode. | URSPEnforcement | +| SubscribedDefaultQos | 3GPP TS 29.571 [11] | Subscribed Default QoS. | | +| Supi | 3GPP TS 29.571 [11] | The identification of the user (i.e. IMSI, NAI). | | +| SupportedFeatures | 3GPP TS 29.571 [11] | Used to negotiate the applicability of the optional features defined in table 5.8-1. | | +| TraceData | 3GPP TS 29.571 [11] | | | +| TimeZone | 3GPP TS 29.571 [11] | Contains the user time zone information. | | +| TscailInputContainer | 3GPP TS 29.514 [17] | TSCAI Input information. | TimeSensitive Networking | +| TrafficCorrelationInfo | 3GPP TS 29.519 [15] | Contains the information for traffic correlation. | CommonEAS DNAI | +| UInteger | 3GPP TS 29.571 [11] | Unsigned Integer. | | +| UIntegerRm | 3GPP TS 29.571 [11] | This data type is defined in the same way as the "UInteger" data type, but with the OpenAPI "nullable: true" property. | EnATSSS, AF_latency | +| Uint16 | 3GPP TS 29.571 [11] | Unsigned 16-bit integers. | MTU_Size | +| Uint32 | 3GPP TS 29.571 [11] | Unsigned 32-bit integers. | MTU_Size | +| Uint64 | 3GPP TS 29.571 [11] | Unsigned 64-bit integers. | TimeSensitive Networking | +| UplinkDownlinkSupport | 3GPP TS 29.514 [17] | Represents whether a capability is supported for the UL, the DL or both UL and DL service data flows | L4S | +| Uri | 3GPP TS 29.571 [11] | URI. | | +| UserLocation | 3GPP TS 29.571 [11] | Contains the user location(s). | | +| Volume | 3GPP TS 29.122 [32] | Unsigned integer identifying a volume in units of bytes. | | +| VolumeRm | 3GPP TS 29.122 [32] | This data type is defined in the same way as the "Volume" data type, but with the OpenAPI "nullable: true" property. | | +| VplmnOffloadingInfo | 3GPP TS 29.571 [11] | VPLMN Specific Offloading Information. | HR-SBO | +| VplmnQos | 3GPP TS 29.502 [22] | QoS constraints in the VPLMN. | VPLMN-QoS-Control | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: "AnGwAddress" data structure is only applicable to the 5GS and EPC/E-UTRAN interworking scenario as defined in Annex B.
NOTE 2: In order to support a set of MAC addresses with a specific range in the traffic filter, feature MacAddressRange as specified in clause 5.8 shall be supported. | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 5.6.2 Structured data types + +### 5.6.2.1 Introduction + +This clause defines the structures to be used in resource representations. + +### 5.6.2.2 Type SmPolicyControl + +**Table 5.6.2.2-1: Definition of type SmPolicyControl** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------------|---|-------------|--------------------------------------------------------------------------------|---------------| +| context | SmPolicyContextData | M | 1 | Includes the parameters to request the SM policies by the NF service consumer. | | +| policy | SmPolicyDecision | M | 1 | Includes the SM policies authorized by the PCF. | | + +### 5.6.2.3 Type SmPolicyContextData + +**Table 5.6.2.3-1: Definition of type SmPolicyContextData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|-----------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| +| accNetChld | AccNetChld | O | 0..1 | Indicates the access network charging identifier for the whole PDU session. For EPS interworking scenarios, it indicates the access network charging identifier for the default QoS flow / default EPS bearer or the whole PDU session. | | +| chargEntityAddr | AccNetChargingAddress | O | 0..1 | Address of the network entity performing charging. | | +| gpsi | Gpsi | O | 0..1 | Gpsi shall contain either an External Id or an MSISDN. | | +| supi | Supi | M | 1 | Subscription Permanent Identifier. (NOTE 2) | | +| invalidSupi | boolean | C | 0..1 | When this attribute is included and set to true, it indicates that the "supi" attribute contains an invalid value. This attribute shall be present if the SUPI is not available in the NF service consumer, or the SUPI is unauthenticated. When present it shall be set as follows:
- true: invalid SUPI.
- false (default): valid SUPI. | | +| pduSessionId | PduSessionId | M | 1 | PDU session Id. | | +| dnn | Dnn | M | 1 | The DNN of the PDU session, a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only. (NOTE 4) | | +| dnnSelMode | DnnSelectionMode | O | 0..1 | Indicates whether the requested DNN corresponds to an explicitly subscribed DNN. | DNNSelectionMode | +| interGrpIds | array(GroupId) | O | 1..N | The internal Group Id(s). | | +| notificationUri | Uri | M | 1 | Identifies the recipient of SM policies update notifications sent by the PCF. | | +| pduSessionType | PduSessionType | M | 1 | Indicates the type of a PDU session. | | +| accessType | AccessType | O | 0..1 | The Access Type where the served UE is camping. | | +| ratType | RatType | O | 0..1 | The RAT Type where the served UE is camping. | | +| addAccessInfo | AdditionalAccessInfo | O | 0..1 | Indicates the combination of additional Access Type and RAT Type for MA PDU session. | ATSSS | +| servingNetwork | PlmnIdNid | O | 0..1 | The serving network (a PLMN or an SNPN) where the served UE is camping. For the SNPN the NID together with the PLMN ID identifies the SNPN. | | +| userLocationInfo | UserLocation | O | 0..1 | The location where the served UE is camping. (NOTE 3) | | +| ueTimeZone | TimeZone | O | 0..1 | The time zone where the served UE is camping. | | +| pei | Pei | O | 0..1 | The Permanent Equipment Identifier of the served UE. | | +| ipv4Address | Ipv4Addr | O | 0..1 | The IPv4 Address of the served UE. | | +| ipv6AddressPrefix | Ipv6Prefix | O | 0..1 | The Ipv6 Address Prefix of the served UE. | | +| ipDomain | string | O | 0..1 | IPv4 address domain identifier. (NOTE 1) | | +| subsSessAmbr | Ambr | O | 0..1 | UDM subscribed or DN-AAA authorized Session-AMBR. | | +| authProfIndex | string | O | 0..1 | DN-AAA authorization profile index. | DN-Authorization | + +| | | | | | | +|-------------------------|-----------------------------|---|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| subsDefQos | SubscribedDefaultQos | O | 0..1 | Subscribed Default QoS Information. | | +| vplmnQos | VplmnQos | O | 0..1 | QoS constraints in a VPLMN. | VPLMN-QoS-Control | +| numOfPackFilter | integer | O | 0..1 | Contains the number of supported packet filter for signalled QoS rules. | | +| online | boolean | O | 0..1 | If it is included and set to true, the online charging is applied to the PDU session. | | +| offline | boolean | O | 0..1 | If it is included and set to true, the offline charging is applied to the PDU session. | | +| chargingCharacteristics | string | O | 0..1 | Contains the Charging Characteristics applied to the PDU session. Functional requirements for the Charging Characteristics are defined in 3GPP TS 32.255 [35] Annex A. The charging characteristics are encoded as specified in 3GPP TS 29.503 [34]. | | +| 3gppPsDataOffStatus | boolean | O | 0..1 | If it is included and set to true, the 3GPP PS Data Off is activated by the UE. | 3GPP-PS-Data-Off | +| refQosIndication | boolean | O | 0..1 | If it is included and set to true, the reflective QoS is supported by the UE. | | +| sliceInfo | Snssai | M | 1 | Identifies the S-NSSAI. | | +| qosFlowUsage | QosFlowUsage | O | 0..1 | Indicates the required usage for default QoS flow. | | +| servNfId | ServingNfIdentity | O | 0..1 | Contains the serving network function identity. | | +| suppFeat | SupportedFeatures | C | 0..1 | Indicates the list of Supported features used as described in clause 5.8. This parameter shall be supplied by the NF service consumer in the POST request that requested the creation of an individual SM policy resource. | | +| traceReq | TraceData | O | 0..1 | Trace control and configuration parameters information defined in 3GPP TS 32.422 [24]. | | +| smfId | NfInstanceId | O | 0..1 | SMF instance identifier. | | +| recoveryTime | DateTime | O | 0..1 | It includes the recovery time of the NF service consumer. | | +| maPduInd | MaPduIndication | O | 0..1 | Contains the MA PDU session indication, i.e., MA PDU Request or MA PDU Network-Upgrade Allowed. | ATSSS | +| atsssCapab | AtsssCapability | O | 0..1 | Contains the ATSSS capability supported for the MA PDU Session. | ATSSS | +| ipv4FrameRouteList | array(Ipv4AddrMask) | O | 1..N | List of Framed Route information of IPv4. | | +| ipv6FrameRouteList | array(Ipv6Prefix) | O | 1..N | List of Framed Route information of IPv6. | | +| satBackhaulCategory | SatelliteBackhaulCategory | O | 0..1 | Indicates satellite backhaul category or non-satellite backhaul used for the PDU session. When this attribute is not present, non-satellite backhaul applies. If the "EnSatBackhaulCatChg" feature is supported, the different dynamic satellite backhaul categories may also be provided. | SatBackhaulCategoryChg | +| pcfUeInfo | PcfUeCallbackInfo | O | 0..1 | PCF for the UE callback URI and SBA binding information. | AMInfluence | +| pvsInfo | array(ServerAddressingInfo) | O | 1..N | Provisioning Server(s) information that provision the UE with credentials and other data to enable SNPN access. | PvsSupport | + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---|------|--------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| onboardInd | boolean | O | 0..1 | If it is included and set to true, it indicates that the PDU session is used for UE Onboarding. | PvsSupport | +| nwdafDatas | array(NwdafData) | O | 1..N | List of NWDAF Instance IDs and their associated Analytics IDs consumed by the NF service consumer. | EneNA | +| urspEnfInfo | UrspEnforcementInfo | O | 0..1 | Contains the reporting of URSP rule(s) enforcement from the UE. | URSPEnforcement | +| sscMode | SscMode | C | 0..1 | SSC Mode of the PDU session. It shall be present when the "urspEnfInfo" attribute is present. | URSPEnforcement | +| ueReqDnn | Dnn | O | 0..1 | UE requested DNN.

It shall be present, if available and different from the selected DNN, when the "urspEnfInfo" attribute is present. | URSPEnforcement | +| redundantPduSessionInfo | RedundantPduSessionInformation | O | 0..1 | RSN and PDU session pair ID of the redundant PDU session.

It shall be present, if available, when the "urspEnfInfo" attribute is present. | URSPEnforcement | +| hrsboInd | boolean | O | 0..1 | HR-SBO support indication. If present and set to "true", it indicates that the HR-SBO is supported. Default value is "false" if omitted. | HR-SBO | +| NOTE 1: The value provided in this attribute is implementation specific. The only constraint is that the NF service consumer shall supply a different identifier for each overlapping address domain (e.g. the SMF NF instance identifier). | | | | | | +| NOTE 2: For an emergency session, when the SUPI is not available in the NF service consumer, or if available, the SUPI is unauthenticated, the value provided in the "supi" attribute is implementation specific. | | | | | | +| NOTE 3: The SMF may encode both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute. | | | | | | +| NOTE 4: The PCF uses the DNN as received from the NF service consumer without applying any transformation (e.g. in subsequent requests to the UDR). To successfully perform DNN matching, in a specific deployment a DNN shall always be encoded either with the full DNN (e.g., because there are multiple Operator Identifiers for a Network Identifier) or the DNN Network Identifier only. The NF service consumer may include the DNN Operator Identifier based on local configuration. | | | | | | + +## 5.6.2.4 Type SmPolicyDecision + +**Table 5.6.2.4-1: Definition of type SmPolicyDecision** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------|--------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| sessRules | map(SessionRule) | O | 1..N | A map of Sessionrules with the content being the SessionRule as described in clause 5.6.2.7. The key used in this map for each entry is the sessRuleId attribute of the corresponding SessionRule. (NOTE 2) | | +| pccRules | map(PccRule) | O | 1..N | A map of PCC rules with the content being the PCCRule as described in clause 5.6.2.6. The key used in this map for each entry is the pccRuleId attribute of the corresponding PccRule. | | +| qosDecs | map(QosData) | O | 1..N | Map of QoS data policy decisions. The key used in this map for each entry is the qosId attribute of the corresponding QosData. (NOTE 2) | | +| chgDecs | map(ChargingData) | O | 1..N | Map of Charging data policy decisions. The key used in this map for each entry is the chgId attribute of the corresponding ChargingData. | | +| chargingInfo | ChargingInformation | C | 1 | Contains the CHF addresses, and if available, the associated CHF instance ID(s) and CHF set ID(s) of the PDU session. (NOTE 3) | | +| traffContDecs | map(TrafficControlData) | O | 1..N | Map of Traffic Control data policy decisions. The key used in this map for each entry is the tcId attribute of the corresponding TrafficControlData. (NOTE 2) | | +| umDecs | map(UsageMonitoringData) | O | 1..N | Map of Usage Monitoring data policy decisions. The key used in this map for each entry is the umId attribute of the corresponding UsageMonitoringData. | UMC | +| qosChars | map(QosCharacteristics) | O | 1..N | Map of QoS characteristics for non-standard 5QIs and non-preconfigured 5QIs. This map uses the 5QI values as keys. (NOTE 2) | | +| qosMonDecs | map(QosMonitoringData) | O | 1..N | Map of QoS Monitoring data policy decision. The key used in this map for each entry is the qmId attribute of the corresponding QosMonitoringData. | QosMonitoring | +| reflectiveQoSTimer | DurationSec | O | 0..1 | Defines the lifetime of a UE derived QoS rule belonging to the PDU Session for reflective QoS. (NOTE 2) | | +| offline | boolean | O | 0..1 | Indicates the offline charging is applicable to the PDU session when it is included and set to true. (NOTE 3) (NOTE 4) (NOTE 6) | | +| online | boolean | O | 0..1 | Indicates the online charging is applicable to the PDU session when it is included and set to true. (NOTE 3) (NOTE 4) (NOTE 6) | | +| offlineChOnly | boolean | O | 0..1 | Indicates that the online charging method shall never be used for any PCC rule activated during the lifetime of the PDU session, when this attribute is present and set to "true". The default value is "false", e.g. if this attribute is omitted. (NOTE 3) (NOTE 4) (NOTE 6) | OfflineChOnly | + +| | | | | | | +|-----------------------|------------------------------------|---|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| conds | map(ConditionData) | O | 1..N | A map of condition data with the content being as described in clause 5.6.2.9. The key used in this map for each entry is the condId attribute of the corresponding ConditionData. | | +| revalidationTime | DateTime | O | 0..1 | Defines the time before which the NF service consumer shall have to re-request PCC rules. | | +| pcscfRestIndication | boolean | O | 0..1 | If this attribute is included and set to true, it indicates that P-CSCF Restoration is requested. The default value "FALSE" applies if the attribute is not present and has not been supplied previously. | PCSCF-Restoration-Enhancement | +| policyCtrlReqTriggers | array(PolicyControlRequestTrigger) | O | 1..N | Defines the policy control request triggers subscribed by the PCF. | | +| lastReqRuleData | array(RequestedRuleData) | O | 1..N | Defines the last list of rule control data requested by the PCF. | | +| lastReqUsageData | RequestedUsageData | O | 0..1 | Indicates whether the last accumulated usage report is requested by the PCF or not, and includes references to the targeted usage monitoring data instances. | UMC | +| pralInfos | map(PresenceInfoRm) | O | 1..N | Defines the PRA information provisioned by the PCF. The "pralId" attribute within the PresenceInfo data type shall also be the key of the map. The "presenceState" attribute within the PresenceInfo data type shall not be supplied. | PRA | +| ipv4Index | lpIndex | C | 0..1 | Information that identifies the IP address allocation method for IPv4 address allocation. (NOTE 3) | | +| ipv6Index | lpIndex | C | 0..1 | Information that identifies the IP address allocation method for IPv6 address allocation. (NOTE 3) | | +| qosFlowUsage | QosFlowUsage | O | 0..1 | Indicates the required usage for default QoS flow. | | +| relCause | SmPolicyAssociationReleaseCause | O | 0..1 | The cause for which the PCF requests the termination of the policy association. | RespBasedSessionRel | +| suppFeat | SupportedFeatures | C | 0..1 | Indicates the list of negotiated supported features. This parameter shall be supplied by the PCF in the response to the POST request that requested the creation of an individual SM policy resource. | | +| tsnBridgeManCont | BridgeManagementContainer | O | 0..1 | Transports TSC user plane node management information | TimeSensitive Networking | +| tsnPortManContDs tt | PortManagementContainer | O | 0..1 | Transports port management information for the DS-TT port. | TimeSensitive Networking | +| tsnPortManContNw tts | array(PortManagementContainer) | O | 1..N | Transports port management information for one or more NW-TT ports. | TimeSensitive Networking | +| tscNotifUri | Uri | O | 0..1 | For PMIC/UMIC UPF event, notification target address of the TSCTSF or TSN AF receiving the TSC management information. | ExposureToTSC | +| tscNotifCorrelId | string | C | 0..1 | Correlation identifier for TSC management information notifications. It shall be provided if the "tscNotifUri" attribute is provided. | ExposureToTSC | + +| | | | | | | +|-------------------|---------------------|---|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| redSessIndication | boolean | O | 0..1 | Indicates whether the PDU Session is a redundant PDU session:
true: end to end redundant PDU session;
false: Not end to end redundant PDU session;
If this attribute is absent it means the PDU session is not an end to end redundant PDU session.
(NOTE 2) (NOTE 3) | Dual-Connectivity-redundant-UP-paths | +| uePolCont | UePolicyContainer | O | 0..1 | Indicates a UE policy container for the UE. Only applicable to the 5GS and EPC interworking scenario as defined in Annex B. | EspUrsp | +| vpImnOffload | VpImnOffloadingInfo | O | 0..1 | Indicates the VPLMN Specific Offloading Policy. | HR-SBO | +| sliceUsgCtrlInfo | SliceUsgCtrlInfo | O | 0..1 | Represents the network slice usage control information (e.g., slice PDU Session inactivity timer value) to be used to support and enforce network slice usage control. | NetSliceUsageCtrl | + +NOTE 1: For IPv4v6 PDU session, both the "ipv4Index" attribute and "ipv6Index" attribute may be provisioned by the PCF. + +NOTE 2: This attribute shall not be removed if it was provisioned. + +NOTE 3: This attribute may only be supplied by the PCF in the response to the initial POST request that requested the creation of an individual SM policy resource. + +NOTE 4: If both the "offline" attribute and the "online" attribute are omitted by the PCF, and when the "OfflineChOnly" feature is supported, if the "offlineChOnly" attribute is set to "false" or omitted by the PCF, the default charging method pre-configured at the SMF, if available, shall be applied to the PDU session. If both offline and online charging methods are pre-configured at the SMF, the SMF shall determine which one of them to be applied to the PDU session based on local policy. The "offline" attribute and the "online" attribute shall not be simultaneously present with the same value, i.e., both set to true or both set to false. + +NOTE 5: If the "chargingInfo" attribute is not supplied by the PCF, the charging information configured at the SMF shall be applied to the PDU session. + +NOTE 6: When the "OfflineChOnly" feature is supported and the "offlineChOnly" attribute is present and set to "true", the "online" attribute and the "offline" attribute shall not be present. + +### 5.6.2.5 Type SmPolicyNotification + +**Table 5.6.2.5-1: Definition of type SmPolicyNotification** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|------------------|---|-------------|----------------------------------------------------------------------------------------------|---------------| +| resourceUri | Uri | M | 1 | The resource URI of the individual SM policy resource related to the notification.
(NOTE) | | +| smPolicyDecision | SmPolicyDecision | M | 1 | Session management policy decision (see clause 5.6.2.4). | | + +NOTE: Either the complete resource URI included in the "resourceUri" attribute or the "apiSpecificResourceUriPart" component (see clause 5.1) of the resource URI included in the "resourceUri" attribute can be used by the SMF for the identification of the individual SM policy resource related to the notification. + +## 5.6.2.6 Type PccRule + +**Table 5.6.2.6-1: Definition of type PccRule** + +| Attribute name | Data type | P | Cardinality | Description | +|----------------|------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| flowInfos | array(FlowInformation) | C | 1..N | An array of Ethernet or IP flow filter information. (NOTE 3) | +| appId | string | C | 0..1 | A reference to the application detection filter configured at the UE. (NOTE 3) | +| appDescriptor | ApplicationDescriptor | C | 0..1 | ATSSS rule application descriptor shall be present when the PDN session is a MA PDN session. SDF template contains an App Identifier (i.e. when the "appId" attribute is present). | +| contVer | ContentVersion | O | 0..1 | Indicates the content version of the PCC rule. | +| pccRuleId | string | M | 1 | Univocally identifies the PCC rule within a PDN session. | +| precedence | UInteger | O | 0..1 | Determines the order in which the PCC rule is applied relative to other PCC rules within the same PDN session. It shall be included if the "flowInfos" attribute is included and may be included if the "appId" attribute is included when the initially provisions the PCC rule. (NOTE 2) (NOTE 4) | +| afSigProtocol | AfSigProtocol | O | 0..1 | Indicates the protocol used for signalling between the UE and the AF. The default value "NO_INFORMATION" shall apply if the attribute is not present and has not been supplied previously. | +| appReloc | boolean | O | 0..1 | It indicates that the application cannot be relocated once a location of the application is selected by the 5GC when it is included and set to "true". Indication of application relocation possibility. The default value "false" shall apply, if the attribute is not present and has not been supplied previously. | +| easRedisInd | boolean | O | 0..1 | Indicates the EAS rediscovery required for the application if it is included and set to "true". Default value is "false" if omitted. The indication shall be invalid if it was applied unless it is provided again. | +| addrPreserInd | boolean | O | 0..1 | Indicates whether UE IP address should be preserved. This attribute shall set to "true" if preserved, otherwise, set to "false". The default value "false" shall apply if the attribute is not present and has not been supplied previously. | +| refQosData | array(string) | O | 1..N | A reference to the QosData profile type decision type. It is the qosData described in clause 5.6.2.8. (NOTE 1) | + +| | | | | | +|---------------------|---------------------------------|---|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| refAltQosParameters | array(string) | O | 1..N | A Reference to the QoS Data decisions for the Alternative QoS parameter sets of the service flow. Only the "qosId" attribute, the "gbrUI" attribute, the "gbrDI" attribute, the "packetDelayBudget" attribute and the "packetErrorRate" attribute are applicable within the associated QoSData data types. This attribute represents an ordered list, where lower the index of the array for a given entry, the higher the priority. | +| refTcData | array(string) | O | 1..N | A reference to the TrafficControl policy decision type. It is the type described in clause 5.6.2.10. (NOTE 1) | +| refChgData | array(string) | O | 1..N | A reference to the ChargingData policy decision type. It is the type described in clause 5.6.2.11. (NOTE 1) (NOTE 7) | +| refChgN3gData | array(string) | O | 1..N | A reference to the ChargingData policy decision type only applicable for Non-3GPP access. It is the type described in clause 5.6.2.11. (NOTE 1) (NOTE 5) (NOTE 7) | +| refUmData | array(string) | O | 1..N | A reference to UsageMonitoring policy decision type. It is the type described in clause 5.6.2.12. (NOTE 1) | +| refUmN3gData | array(string) | O | 1..N | A reference to UsageMonitoring policy decision type only applicable for Non-3GPP access. It is the type described in clause 5.6.2.12. (NOTE 1) (NOTE 6) | +| refCondData | string | O | 0..1 | A reference to the condition data described in clause 5.6.2.9. | +| refQosMon | array(string) | O | 1..N | A reference to QosMonitoring policy decision type. It is the type described in clause 5.6.2.40. (NOTE 1) | +| protoDesc | ProtoDesc | O | 0..1 | Protocol description for PDU session identification and/or detection of end of data burst in UPF | +| tscaiInputUI | TscailInputContainer | O | 0..1 | Transports TSCAI input parameters for TSC traffic at the ingress interface of the DS-TT/UE (uplink flow direction). (NOTE 9) | +| tscaiInputDI | TscailInputContainer | O | 0..1 | Transports TSCAI input parameters for TSC traffic at the ingress of the NW-TT (downlink flow direction). (NOTE 9) | +| tscaiTimeDom | UInteger | O | 0..1 | Indicates the (g)PTP domain where the (TSN)AF is located in. | +| capBatAdaptation | boolean | O | 0..1 | Indicates the capability for AF to adjust the burst sending time, if provided and set to "true". The default value is "false" if not present. (NOTE 9) | +| ddNotifCtrl | DownlinkDataNotificationControl | O | 0..1 | The Downlink Data Notification Control applying to the control of DDD Status event notification and DDN Failure event notification attribute shall not be present if the DDNEventPolicyControl2 is supported. | + +| | | | | | | +|--|-----------------|-----------------------------------|---|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ddNotifCtrl2 | DownlinkDataNotificationControlRm | O | 0..1 | The Downlink Data Notification Control applying to the control DDD Status event notification DDN Failure event notification including the removal of providing the downlink data notification information. | +| | disUeNotif | boolean | O | 0..1 | Indicates to disable QoS flow parameters signalling to the UE when the SMF is notified by the NG-RAN changes in the fulfilled QoS status when it is included and set to true. The fulfilled situation is either a QoS profile or an Alternative QoS Profile. The default value "false" apply, if the attribute is not present and has not been supplied previously. | +| | packFiltAllPrec | UInteger | C | 0..1 | Determines the order of TFT packet filter allocation for PCC rules. (NOTE 8) | +| | nscSuppFeats | map(SupportedFeatures) | O | 1..N | A map of Network Function Service Consumer features supported service. The key used in this map for each entry is the ServiceName as defined in 3GPP TS 29.511 (e.g. for Nsmf_EventExposure the key shall be set to nsmf-event-exposure). | +| | callInfo | CallInfo | O | 0..1 | Indicates the caller and the call information. | +| | traffParaData | TrafficParaData | O | 0..1 | Traffic Parameter measurements | + +introduced for future compatibility. In this release of the specification the maximum number of the array is 1. + +With the "appld" attribute, the precedence can be preconfigured in SMF or provided in the PCF. The precedence provided by the PCF shall take precedence. + +"infos" attribute or "appld" attribute shall be supplied by the PCF when the PCC rule is initially. If the "appld" attribute is supplied, the PCF shall not modify the application identifier supplied in the "appld" attribute later. + +"precedence" attribute is used to specify the precedence of the PCC rule among all PCC rules within the PDU session. It includes an integer value in the range from 0 to 255 (decimal). The value of the "precedence" attribute, the lower the precedence of that PCC rule is. The precedence from 70 to 99 (decimal) shall be used for the PCC rules subject to Reflective QoS. + +Session, Charging Data decision referred by the "refChgData" attribute applies to both 3GPP and non-3GPP access. If there is no "refChgN3gData" attribute included, the Charging Data decision referred by the "refChgData" attribute applies to non-3GPP access and the Charging Data decision referred by the "refChgData" attribute applies to 3GPP access. The value(s) of the "chglD" attribute referred by the "refChgN3gData" shall be the same as the one(s) within the Charging Data decision referred by the "refChgData". + +Session, Usage Monitoring Data decision referred by the "refUmData" attribute applies to both 3GPP and non-3GPP access. If there is no "refUmN3gData" attribute included, the Usage Monitoring Data decision referred by the "refUmData" attribute applies to non-3GPP access and the Usage Monitoring Data decision referred by the "refUmData" attribute applies to 3GPP access. + +If the "refChgData" attribute and/or "refChgN3gData" attribute is/are provisioned for a PCC rule, then this PCC rule shall not be subject to charging accordingly. If the "refChgData" attribute and/or "refChgN3gData" attribute is set to NULL for a PCC rule, then charging shall be deactivated accordingly for this PCC rule. If the AllocPrecedence feature is supported, the packFiltAllPrec attribute shall be present in every PDU Session when the PCC rule is installed for the first time. + +"tscailTimeWnd" attribute, within the "tscailInputUI" and/or "tscailInputDI" attributes, and the "tscailOutputUI" attribute are mutually exclusive. + +## 5.6.2.7 Type SessionRule + +**Table 5.6.2.7-1: Definition of type SessionRule** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|----------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| authSessAmbr | Ambr | C | 0..1 | Authorized Session-AMBR. (NOTE 1) | | +| authDefQos | AuthorizedDefaultQos | C | 0..1 | Authorized default QoS information. (NOTE 1) | | +| sessRuleId | string | M | 1 | Univocally identifies the session rule within a PDU session. | | +| refUmData | string | O | 0..1 | A reference to UsageMonitoringData policy decision type. It is the umId described in clause 5.6.2.12. (NOTE 2) | UMC | +| refCondData | string | O | 0..1 | A reference to the condition data. It is the condId described in clause 5.6.2.9. | | +| refUmN3gData | string | O | 0..1 | A reference to UsageMonitoringData policy decision type to apply for Non-3GPP access. It is the umId described in clause 5.6.2.12. (NOTE 2) | UMC, ATSSS | + +NOTE 1: When the "subsDefQos" and "subsSessAmbr" are provided to the PCF, the PCF shall provide both "authSessAmbr" and the "authDefQos" attributes the first time the session rule is provisioned. In this case, the PCF shall ensure that a session rule enforced in the SMF contains the "authSessAmbr" and the "authDefQos" attributes. + +NOTE 2: For a MA PDU session, if the "refUmN3gData" is omitted, the attribute "refUmData" contains the reference to the UsageMonitoringData policy decision to apply for both, 3GPP and Non-3GPP, accesses. + +## 5.6.2.8 Type QosData + +**Table 5.6.2.8-1: Definition of type QosData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------------|--------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| +| qosId | string | M | 1 | Univocally identifies the QoS control policy data within a PDU session. | | +| 5qi | 5Qi | C | 0..1 | Identifier for the authorized QoS parameters for the service data flow. It shall be included when the QoS data decision is initially provisioned and "defQosFlowIndication" is not included or is included and set to false. | | +| maxbrUI | BitRateRm | O | 0..1 | Indicates the maximum bandwidth in uplink. | | +| maxbrDI | BitRateRm | O | 0..1 | Indicates the maximum bandwidth in downlink. | | +| gbrUI | BitRateRm | O | 0..1 | Indicates the guaranteed bandwidth in uplink. (NOTE 3) | | +| gbrDI | BitRateRm | O | 0..1 | Indicates the guaranteed bandwidth in downlink. (NOTE 3) | | +| arp | Arp | C | 1 | Indicates the allocation and retention priority. It shall be included when the QoS data decision is initially provisioned and "defQosFlowIndication" is not included or is included and set to false. | | +| qnc | boolean | O | 0..1 | Indicates whether notifications are requested from 3GPP NG-RAN when the GFBR can no longer (or again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow. The default value "FALSE" is used if this attribute is not present and has not been supplied previously. (NOTE 3) | | +| reflectiveQos | boolean | O | 0..1 | Indicates whether the QoS information is reflective for the corresponding non-GBR service data flow. The default value "FALSE" is used if this attribute is not present and has not been supplied previously. | | +| sharingKeyDI | string | O | 0..1 | Indicates, by containing the same value, what PCC rules may share resources in the downlink direction. | ResShare | +| sharingKeyUI | string | O | 0..1 | Indicates, by containing the same value, what PCC rules may share resources in the uplink direction. | ResShare | +| priorityLevel | 5QiPriorityLevelRm | O | 0..1 | Indicates a priority in scheduling resources among QoS Flows. (NOTE 1) | | +| averWindow | AverWindowRm | O | 0..1 | Represents the duration over which the guaranteed and maximum bitrates shall be calculated. (NOTE 1) (NOTE 3) | | +| maxDataBurstVol | MaxDataBurstVolRm | O | 0..1 | Denotes the largest amount of data that is required to be transferred within a period of 5G-AN PDB. (NOTE 1, NOTE 2) | | +| maxPacketLossRateDI | PacketLossRateRm | O | 0..1 | Indicates the maximum downlink packet loss rate for that can be tolerated for the service data flow. | RAN-Support-Info | +| maxPacketLossRateUI | PacketLossRateRm | O | 0..1 | Indicates the maximum uplink packet loss rate that can be tolerated for the service data flow. | RAN-Support-Info | +| defQosFlowIndication | boolean | O | 0..1 | Indicates that the dynamic PCC rule shall always have its binding with the QoS Flow associated with the default QoS rule. The default value "FALSE" is used if this attribute is not present and has not been supplied previously. | | + +| | | | | | | +|--------------------|----------------------|---|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| extMaxDataBurstVol | ExtMaxDataBurstVolRm | O | 0..1 | Denotes the largest amount of data that is required to be transferred within a period of 5G-AN PDB. (NOTE 1, NOTE 2) | EMDBV | +| packetDelayBudget | PacketDelBudget | O | 0..1 | Unsigned integer. It indicates the Packet Delay Budget expressed in milliseconds. | AuthorizationWithRequiredQoS | +| packetErrorRate | PacketErrRate | O | 0..1 | String indicating the packet error rate. Examples:
Packet Error Rate $4 \times 10^{-6}$ shall be encoded as "4E-6".
Packet Error Rate $10^{-2}$ shall be encoded as "1E-2". | AuthorizationWithRequiredQoS | +| pduSetQoS | PduSetQoSParaRm | O | 0..1 | Contains the PDU Set QoS Parameters which are used to support PDU Set based QoS handling. | PDUSetHandling | + +NOTE 1: Applicable only when a value different from the standardized value for this 5QI, provided in table 5.7.4-1 3GPP TS 23.501 [2], is required. + +NOTE 2: Either the maxDataBurstVol attribute or the extMaxDataBurstVol attribute may be present for a Delay Critical GBR QoS flow. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurstVol attribute is used. If the EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol attribute is used to transmit the maximum data burst volume values higher than 4095 Bytes (see clause 4.2.2.1). + +NOTE 3: This attribute is only applicable to GBR type or delay critical GBR type 5QIs. + +Editor's note: Based on the progress of SA2, it is FFS whether PDU Set QoS parameters are defined within PccRule data type instead of within QosData. + +### 5.6.2.9 Type ConditionData + +**Table 5.6.2.9-1: Definition of type ConditionData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|------------|---|-------------|------------------------------------------------------------------------------------------|---------------------| +| condId | string | M | 1 | Uniquely identifies the condition data within a PDU session. | | +| activationTime | DateTimeRm | O | 0..1 | The time when the decision data shall be activated. | | +| deactivationTime | DateTimeRm | O | 0..1 | The time when the decision data shall be deactivated. (NOTE 1) | | +| accessType | AccessType | O | 0..1 | The condition of access type of the UE when the session AMBR shall be enforced. (NOTE 2) | AccessTypeCondition | +| ratType | RatType | O | 0..1 | The condition of RAT type of the UE when the session AMBR shall be enforced. (NOTE 2) | AccessTypeCondition | + +NOTE 1: It is only included in the ConditionData instance for conditioned PCC rule. + +NOTE 2: At least one of the "accessType" or "ratType" attributes shall be present in an access type conditioned session rule. + +## 5.6.2.10 Type TrafficControlData + +**Table 5.6.2.10-1: Definition of type TrafficControlData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------------------|-----------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| tcId | string | M | 1 | Univocally identifies the traffic control policy data within a PDU session. | | +| l4sInd | UplinkDownlinkSupport | O | 0..1 | When provided, it represents an explicit indication of whether ECN marking for L4S support is supported for the UL, the DL or both, UL and DL. | L4S | +| flowStatus | FlowStatus | O | 0..1 | Enum determining what action to perform on traffic. Possible values are: [enable, disable, enable_uplink, enable_downlink]. The default value "ENABLED" shall apply, if the attribute is not present and has not been supplied previously. (NOTE 3) | | +| redirectInfo | RedirectInformation | O | 0..1 | It indicates whether the detected application traffic should be redirected to another controlled address. | ADC | +| addRedirectInfo | array(RedirectInformation) | O | 1..N | Additional redirection information. Each element indicates whether the detected application traffic should be redirected to another controlled address. | ADCmultiRedirection | +| muteNotif | boolean | O | 0..1 | Indicates whether application's start or stop notifications are to be muted. It shall be set to true to indicate application's start or stop notifications are muted. When it is set to false, it indicates application's start or stop notifications are not muted. The default value false shall apply, if the attribute is not present and has not been supplied previously. | ADC | +| trafficSteeringPolldDI (NOTE 1) | string | O | 0..1 | Reference to a pre-configured traffic steering policy for downlink traffic at the SMF. | TSC | +| trafficSteeringPolldUI (NOTE 1) | string | O | 0..1 | Reference to a pre-configured traffic steering policy for uplink traffic at the SMF. | TSC | +| metadata | Metadata | O | 0..1 | This datatype contains opaque information for the service functions in the N6-LAN that is provided by AF and transparently sent to UPF. May be only provided when "trafficSteeringPolldDI" and/or "trafficSteeringPolldUI" are provided for the first time. | SFC | +| routeToLocs (NOTE 1) | array(RouteToLocation) | O | 1..N | A list of location(s) to which the traffic shall be routed for the AF request. | TSC | +| maxAllowedUpLat | UIntegerRm | O | 0..1 | Indicates the target user plane latency in units of milliseconds. The SMF may use this value to decide whether edge relocation is needed to ensure that the user plane latency does not exceed the value. | AF_latency | +| easIpReplaceInfos | array(EasIpReplacementInfo) | O | 1..N | Contains EAS IP replacement information. | EASIPreplacement | +| traffCorreInd | boolean | O | 0..1 | Indication of traffic correlation. If it is included and set to "true", traffic should be correlated; The default value "false" applies, if the attribute is not present and has not been supplied previously. (NOTE 2) | | +| ttcCorreInfo | TrafficCorrelationInfo | O | 0..1 | Contains the information for traffic correlation. | CommonEAS DNAI | + +| | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| simConnInd | boolean | O | 0..1 | Indication of simultaneous connectivity temporarily maintained for the source and target PSA. If it is included and set to "true", temporary simultaneous connectivity should be kept. The default value "false" applies, if the attribute is not present and has not been supplied previously. | SimultConnectivity | +| simConnTerm | DurationSec | C | 0..1 | Indication of the minimum time interval to be considered for inactivity of the traffic routed via the source PSA during the edge re-location procedure. It may be included when the "simConnInd" attribute is set to true. | SimultConnectivity | +| upPathChgEvent | UpPathChgEvent | O | 0..1 | Contains the information about the AF subscription to UP path change events. | TSC | +| steerFun | SteeringFunctionality | O | 0..1 | Indicates the applicable traffic steering functionality. | ATSSS | +| steerModeDI | SteeringMode | O | 0..1 | Determines the traffic distribution rule across 3GPP and Non-3GPP accesses to apply for downlink traffic. | ATSSS | +| steerModeUI | SteeringMode | O | 0..1 | Determines the traffic distribution rule across 3GPP and Non-3GPP accesses to apply for uplink traffic. | ATSSS | +| mulAccCtrl | MulticastAccessControl | O | 0..1 | Indicates whether the service data flow, corresponding to the service data flow template, is allowed or not allowed. The default value "NOT_ALLOWED" applies, if the attribute is not present and has not been supplied previously. | WWC | +| candDnaiInd | boolean | O | 0..1 | Indication of reporting candidate DNAI(s). If it is included and set to "true", the candidate DNAI(s) for the PDU session need to be reported. Otherwise set to "false" or omitted. | CommonEAS DNAI | +| datEndMarkInd | boolean | O | 0..1 | The data burst end marking is enabled if it is set to "true". Default value is "false" if omitted. | PowerSaving | +| NOTE 1: If SFC feature is not supported, traffic steering policy identifier(s) (i.e. "trafficSteeringPolldDI" attribute and/or "trafficSteeringPolldUI" attribute) and N6 traffic routing requirements (i.e. "routeToLocs" attribute) are mutually exclusive; otherwise, they can be provided simultaneously. | | | | | | +| NOTE 2: The TSC feature shall be supported in order to support this attribute. The Indication of traffic correlation shall be provided only when all the PDU sessions related to the 5G VN group member UEs should be correlated by a common DNAI in the user plane for the traffic as described in 3GPP TS 23.501 [2], clause 5.6.7.1 and clause 5.29. | | | | | | +| NOTE 3: The "flowStatus" attribute and the "mulAccCtrl" attribute are mutually exclusive. | | | | | | + +## 5.6.2.11 Type ChargingData + +**Table 5.6.2.11-1: Definition of type ChargingData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------------|-----------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| chgId | string | M | 1 | Univocally identifies the charging control policy data within a PDU session. | | +| meteringMethod | MeteringMethod | O | 0..1 | Defines what parameters shall be metered for offline charging. If the attribute is not present but it has been supplied previously, the previous information remains valid. If the attribute is not present and it has not been supplied previously or the attribute has been supplied previously but the attribute is set to NULL, the metering method pre-configured at the SMF is applicable as default metering method. | | +| offline | boolean | O | 0..1 | Indicates the offline charging is applicable to the PCC rule when it is included and set of true. (NOTE 1) | | +| online | boolean | O | 0..1 | Indicates the online charging is applicable to the PCC rule when it is included and set of true. (NOTE 1, NOTE 5) | | +| sdfHandl | boolean | O | 0..1 | Indicates whether the service data flow is allowed to start while the SMF is waiting for the response to the credit request. The default value "FALSE" (blocking) shall apply, if the attribute is not present. (NOTE 2) | | +| ratingGroup | RatingGroup | C | 0..1 | The charging key for the PCC rule used for rating purposes. It shall be included when the ChargingData policy decision is initially provisioned. | | +| reportingLevel | ReportingLevel | O | 0..1 | Defines on what level the SMF reports the usage for the related PCC rule. If the attribute is not present but it has been supplied previously, the previous information remains valid. If the attribute is not present and it has not been supplied previously or the attribute has been supplied previously but it is set to NULL, the reporting level pre-configured at the SMF is applicable as default reporting level. | | +| serviceId | ServiceId | O | 0..1 | Indicates the identifier of the service or service component the service data flow in a PCC rule relates to. | | +| sponsorId | string | O | 0..1 | Indicates the sponsor identity. | SponsoredConnectivity | +| appSvcProvId | string | O | 0..1 | Indicates the application service provider identity. | SponsoredConnectivity | +| afChargingIdentifier | ChargingId | C | 0..1 | An identifier, provided from the AF, correlating the measurement for the Charging key/Service identifier values in this PCC rule with application level reports. (NOTE 4) | | +| afChargId | ApplicationChargingId | O | 0..1 | A character string identifier, provided from the AF, correlating the measurement for the Charging key/Service identifier values in this PCC rule with application level reports. (NOTE 3) | AF_Charging_Identifier | + +| | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The absence of both the "offline" attribute and "online" attribute or only one attribute is present and set to false within a Charging Data decision instance indicates that the default charging method of the PDU session is applicable to the PCC rule referring to the Charging Data decision. Either "offline" attribute or "online" attribute set to true shall be provisioned initially if there is no default charging method applied to the PDU session. The "offline" attribute and the "online" attribute shall not be simultaneously present with the same value, i.e. both set to "true" or both set to "false". | +| NOTE 2: | The "sdfHandl" attribute shall not be present when the online charging method does not apply for the PCC rule referring to the Charging Data decision (i.e., when the "online" attribute is present and set to false, or is absent and the online default charging method does not apply for the PDU session, or is absent and there is no online default charging method defined). | +| NOTE 3: | The "afChargId" attribute shall be used instead of the "afChargingIdentifier" attribute when the "AF_Charging_Identifier" feature is supported. | +| NOTE 4: | The "afChargingIdentifier" attribute shall not be present when the "AF_Charging_Identifier" feature is supported. When the "AF_Charging_Identifier" feature is not supported it is out of the scope of the specification what the behaviour of the PCF is when the AF provides charging identifier values that are out of ChargingId data type value range. | +| NOTE 5: | When the "OfflineChOnly" feature is supported and the "offlineChOnly" attribute is present and set to "true" within the SmPolicyDecision data structure, then the "online" attribute shall not be present. | + +## 5.6.2.12 Type UsageMonitoringData + +**Table 5.6.2.12-1: Definition of type UsageMonitoringData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------------|---------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| umId | string | M | 1 | Contains the Usage Monitoring ID, which univocally identifies the usage monitoring policy data instance within a PDU session.
(NOTE) | | +| volumeThreshold | VolumeRm | O | 0..1 | Indicates the total volume threshold. | | +| volumeThresholdUplink | VolumeRm | O | 0..1 | Indicates a volume threshold in uplink. | | +| volumeThresholdDownlink | VolumeRm | O | 0..1 | Indicates a volume threshold in downlink. | | +| timeThreshold | DurationSecRm | O | 0..1 | Indicates a time threshold. | | +| monitoringTime | DateTimeRm | O | 0..1 | Indicates the time at which the UP function is expected to reapply the next thresholds (e.g. nextVolThreshold). | | +| nextVolThreshold | VolumeRm | C | 0..1 | Indicates a volume threshold after the Monitoring Time. | | +| nextVolThresholdUplink | VolumeRm | O | 0..1 | Indicates a volume threshold in uplink after the Monitoring Time. | | +| nextVolThresholdDownlink | VolumeRm | O | 0..1 | Indicates a volume threshold in downlink after the Monitoring Time. | | +| nextTimeThreshold | DurationSecRm | C | 0..1 | Indicates a time threshold after the Monitoring Time. | | +| inactivityTime | DurationSecRm | O | 0..1 | Defines the period of time after which the time measurement shall stop, if no packets are received. | | +| exUsagePccRuleIds | array(string) | C | 1..N | Contains the PCC rule identifier(s) corresponding to service data flow(s) that shall be excluded from PDU Session usage monitoring. It is only included in the UsageMonitoringData instance for session level usage monitoring. | | + +NOTE: A Usage Monitoring ID corresponds to a valid Monitoring Key. + +### 5.6.2.13 Type RedirectInformation + +**Table 5.6.2.13-1: Definition of type RedirectInformation** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------------|---------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| redirectEnabled | boolean | C | 0..1 |

This attribute indicates whether the redirect instruction is enabled. It shall be included and set to true when the redirect instruction is provisioned initially within a PCC rule.

Subsequently:

  • - It may be included to disable or re-enable the redirect instruction.
  • - Otherwise, if the attribute is omitted, the previous value shall apply.
| | +| redirectAddressType | RedirectAddressType | O | 0..1 | Indicates the type of redirect address contained within the "redirectServerAddress" attribute. | | +| redirectServerAddress | string | O | 0..1 |

Indicates the address of the redirect server.

  • - If the "redirectAddressType" attribute indicates "IPV4_ADDR", the encoding is the same as the Ipv4Addr data type defined in 3GPP TS 29.571 [11].
  • - If the "redirectAddressType" attribute indicates "IPV6_ADDR", the encoding is the same as the Ipv6Addr data type defined in 3GPP TS 29.571 [11].
  • - If the "redirectAddressType" attribute indicates "URL" or "SIP_URI", the encoding is the same as the Uri data type defined in 3GPP TS 29.571 [11].
| | + +### 5.6.2.14 Type FlowInformation + +**Table 5.6.2.14-1: Definition of type FlowInformation** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------|--------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| flowDescription | FlowDescription | O | 0..1 | Contains the packet filters of the IP flow(s). | | +| ethFlowDescription | EthFlowDescription | O | 0..1 | Defines a packet filter for an Ethernet flow. If the "fDir" attribute is included, it shall be set to "DOWNLINK". If the "fDir" attribute is never provided, the address information within the "ethFlowDescription" attribute shall be encoded in downlink direction. | | +| packFiltId | string | O | 0..1 | An identifier of packet filter. (NOTE) | | +| packetFilterUsage | boolean | O | 0..1 | The packet shall be sent to the UE. The default value "FALSE" shall apply, if the attribute is not present and has not been supplied previously. | | +| tosTrafficClass | string | O | 0..1 | 2-octet string. The first octet contains the Ipv4 Type-of-Service or the Ipv6 Traffic-Class field and the second octet contains the ToS/Traffic mask field in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. One example is that of a TFT packet filter as defined in 3GPP TS 24.008 [41]. | | +| spi | string | O | 0..1 | 4 octet string, representing the security parameter index of the IPSec packet in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. One example is that of a TFT packet filter as defined in 3GPP TS 24.008 [41]. | | +| flowLabel | string | O | 0..1 | 3-octet string, representing the Ipv6 flow label header field in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. One example is that of a TFT packet filter as defined in 3GPP TS 24.008 [41]. | | +| flowDirection | FlowDirectionRm | O | 0..1 | Indicates the direction/directions that a filter is applicable, downlink only, uplink only or both down- and uplink (bidirectional). | | + +NOTE: The PCF shall only assign the "packFiltId" attribute for PCC rules created as a result of UE-initiated resource allocation. + +### 5.6.2.15 Type SmPolicyDeleteData + +**Table 5.6.2.15-1: Definition of type SmPolicyDeleteData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------------|------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| userLocationInfo | UserLocation | O | 0..1 | The location(s) where the served UE is camping. (NOTE 2) | RAN-NAS-Cause, NetLoc | +| ueTimeZone | TimeZone | O | 0..1 | The time zone where the served UE is camping. | RAN-NAS-Cause, NetLoc | +| userLocationInfoTime | DateTime | O | 0..1 | Contains the NTP time at which the UE was last known to be in the location contained in the "userLocationInfo" attribute. (NOTE 1) | RAN-NAS-Cause, NetLoc | +| servingNetwork | PlmnIdNid | O | 0..1 | The serving network (a PLMN or an SNPN) where the served UE is camping. For the SNPN, the NID together with the PLMN ID identifies the SNPN. | NetLoc | +| ranNasRelCauses | array(RanNasRelCause) | O | 1..N | Indicates the RAN and/or NAS release cause(s) code information. | RAN-NAS-Cause | +| accuUsageReports | array(AccuUsageReport) | O | 1..N | Contains the accumulated usage reporting information. | UMC | +| pduSessRelCause | PduSessionRelCause | O | 0..1 | Indicates PDU session release cause. | PDU Session Rel Cause, Immediate Termination | + +NOTE 1: The age of UE location included within the "userLocationInfoTime" attribute is the age of the 3GPP access UE location received from the AMF and shall be included only when the reported "userLocationInfo" attribute includes the UE location in the 3GPP access. + +NOTE 2: The SMF may encode both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute. + +## 5.6.2.16 Type QosCharacteristics + +**Table 5.6.2.16-1: Definition of type QosCharacteristics** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------|--------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| 5qi | 5Qi | M | 1 | Identifier for the authorized QoS parameters for the service data flow. Applies to PCC rule and PDU session level. | | +| resourceType | QosResourceType | M | 1 | Indicates whether the resource type is GBR, delay critical GBR, or non-GBR. | | +| priorityLevel | 5QIPriorityLevel | M | 1 | Unsigned integer indicating the 5QI Priority Level, within a range of 1 to 127. | | +| packetDelayBudget | PacketDelBudget | M | 1 | Unsigned integer indicates the packet delay budget. Packet Delay Budget expressed in milliseconds. | | +| packetErrorRate | PacketErrRate | M | 1 | String indicating the packet error rate.
Examples:
Packer Error Rate $4 \times 10^{-6}$ shall be encoded as "4E-6".
Packer Error Rate $10^{-2}$ shall be encoded as "1E-2". | | +| averagingWindow | AverWindow | C | 0..1 | Indicates the averaging window. This IE shall be present only for a GBR QoS flow or a Delay Critical GBR QoS flow. | | +| maxDataBurstVol | MaxDataBurstVol | C | 0..1 | Unsigned Integer. Indicates the maximum data burst volume.
(NOTE) | | +| extMaxDataBurstVol | ExtMaxDataBurstVol | C | 0..1 | Unsigned Integer. Indicates the maximum data burst volume.
(NOTE) | EMDBV | + +NOTE: Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present for a Delay Critical GBR QoS flow. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurstVol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes (see clause 4.2.2.1). + +## 5.6.2.17 Type ChargingInformation + +**Table 5.6.2.17-1: Definition of type ChargingInformation** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------------|--------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| primaryChfAddress | Uri | M | 1 | Contains the {apiRoot} part, either in the form of an FQDN or IPAddress/Port Number, of the URI, of the primary CHF instance.
(NOTE 1) (NOTE 2) | | +| secondaryChfAddress | Uri | C | 0..1 | Contains the {apiRoot} part, either in the form of an FQDN or IPAddress/Port Number, of the URI, of the secondary CHF instance.
It shall be present if the feature "CHFsetSupport" is not supported.
It may be omitted if the feature "CHFsetSupport" is supported
(NOTE 1) (NOTE 2) | | +| primaryChfSetId | NfSetId | C | 0..1 | The CHF set ID that the primary CHF instance belongs to may complement the primary CHF address and shall be present, if available.
(NOTE 2) | | +| primaryChfInstanceId | NfInstanceId | C | 0..1 | The CHF instance ID of the primary CHF instance may complement the primary CHF address and shall be present, if available.
(NOTE 2) | | +| secondaryChfSetId | NfSetId | C | 0..1 | The CHF set ID that the secondary CHF instance belongs to may complement the secondary CHF address and shall be present, if available, and the feature "CHFsetSupport" is not supported. It may be omitted if available and the feature "CHFsetSupport" is supported. | | +| secondaryChfInstanceId | NfInstanceId | C | 0..1 | The CHF instance ID of the secondary CHF instance may complement the secondary CHF address and shall be present, if available, and the feature "CHFsetSupport" is not supported. It may be omitted if available and the feature "CHFsetSupport" is supported. | | + +NOTE 1: Based on the {apiRoot} of the CHF instance in the form of an FQDN, the consumer can derive the Nfinstance via NRF lookup. It is up to the consumer to determine which service to invoke from the CHF. The {apiRoot} shall apply to all CHF services. + +NOTE 2: The NF Service Consumer of the CHF may use the "primaryChfAddress"/"secondaryChfAddress" attributes as primary/secondary redundancy mechanism, or alternatively, when CHF instance and CHF set are available, it may also rely on the availability of a CHF instance within the CHF Set for the same purpose. + +### 5.6.2.18 Type AccuUsageReport + +**Table 5.6.2.18-1: Definition of type AccuUsageReport** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------------|-------------|---|-------------|----------------------------------------------------------------------------------|---------------| +| refUmlDs | string | M | 1 | An id referencing UsageMonitoringData objects associated with this usage report. | | +| volUsage | Volume | O | 0..1 | Indicates a total accumulated volume usage. | | +| volUsageUplink | Volume | O | 0..1 | Indicates an accumulated volume usage in uplink. | | +| volUsageDownlink | Volume | O | 0..1 | Indicates an accumulated volume usage in downlink. | | +| timeUsage | DurationSec | O | 0..1 | Indicates an accumulated time usage. | | +| nextVolUsage | Volume | C | 0..1 | Indicates an accumulated volume usage after the Monitoring Time. | | +| nextVolUsageUplink | Volume | O | 0..1 | Indicates an accumulated volume usage in uplink after the Monitoring Time. | | +| nextVolUsageDownlink | Volume | O | 0..1 | Indicates an accumulated volume usage in downlink after the Monitoring Time. | | +| nextTimeUsage | DurationSec | C | 0..1 | Indicates an accumulated time usage after the Monitoring. | | + +## 5.6.2.19 Type SmPolicyUpdateContextData + +**Table 5.6.2.19-1: Definition of type SmPolicyUpdateContextData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------------|------------------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| repPolicyCtrlReqTriggers | array(PolicyControlRequestTrigger) | C | 1..N | The policy control request triggers which are met. It is omitted if no triggers are met such as in clauses 4.2.4.7 and 4.2.4.15. | | +| accNetChlds | array(AccNetChld) | O | 1..N | Indicates the access network charging identifier for the whole PDU session. For EPS interworking scenarios, it indicates the access network charging identifier for the PCC rule(s) or the whole PDU session. | | +| accessType | AccessType | O | 0..1 | The Access Type where the served UE is camping. | | +| ratType | RatType | O | 0..1 | The RAT Type where the served UE is camping. | | +| addAccessInfo | AdditionalAccessInfo | O | 0..1 | Indicates the combination of added Access Type and RAT Type for MA PDU session. | ATSSS | +| relAccessInfo | AdditionalAccessInfo | O | 0..1 | Indicates the combination of released Access Type and RAT Type for MA PDU session. | ATSSS | +| servingNetwork | PlmnIdNid | O | 0..1 | The serving network (a PLMN or an SNPN) where the served UE is camping. For the SNPN the NID together with the PLMN ID identifies the SNPN. | | +| userLocationInfo | UserLocation | O | 0..1 | The location(s) where the served UE is camping. (NOTE 4) | | +| ueTimeZone | TimeZone | O | 0..1 | The time zone where the served UE is camping. | | +| ipv4Address | Ipv4Addr | O | 0..1 | The IPv4 Address of the served UE. | | +| ipDomain | string | O | 0..1 | IPv4 address domain identifier. (NOTE 2) | | +| rellpv4Address | Ipv4Addr | O | 0..1 | Indicates the released IPv4 Address of the served UE. | | +| ipv6AddressPrefix | Ipv6Prefix | O | 0..1 | The Ipv6 Address Prefix of the served UE. (NOTE 6) | | +| rellpv6AddressPrefix | Ipv6Prefix | O | 0..1 | Indicates the released IPv6 Address Prefix of the served UE in multi-homing case. (NOTE 6) | | +| relUeMac | MacAddr48 | O | 0..1 | Indicates the released MAC Address of the served UE. | | +| ueMac | MacAddr48 | O | 0..1 | The MAC Address of the served UE. | | +| subsSessAmbr | Ambr | O | 0..1 | UDM subscribed or DN-AAA authorized Session-AMBR. | | +| authProfIndex | string | O | 0..1 | DN-AAA authorization profile index. | DN-Authorization | +| subsDefQos | SubscribedDefaultQos | O | 0..1 | Subscribed Default QoS Information. | | +| vplmnQos | VplmnQos | O | 0..1 | QoS constraints in a VPLMN (NOTE 5) | VPLMN-QoS-Control | +| vplmnQosNotApp | boolean | O | 0..1 | If it is included and set to true, indicates that the QoS constraints in the VPLMN are not applicable. (NOTE 5) | VPLMN-QoS-Control | +| numOfPackFilter | integer | O | 0..1 | Contains the number of supported packet filter for signalled QoS rules. (NOTE 1) | | +| accuUsageReports | array(AccuUsageReport) | O | 1..N | Contains the accumulated usage report(s). | UMC | +| 3gppPsDataOffStatus | boolean | O | 0..1 | If it is included and set to true, the 3GPP PS Data Off is activated by the UE. | 3GPP-PS-Data-Off | + +| | | | | | | +|------------------------|-----------------------------------|---|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| appDetectionInfos | array(AppDetectionInfo) | O | 1..N | Reports the start/stop of the application traffic and detected SDF descriptions if applicable. | ADC | +| ruleReports | array(RuleReport) | O | 1..N | Used to report the PCC rule failure. | | +| sessRuleReports | array(SessionRuleReport) | O | 1..N | Used to report the session rule failure. | SessionRuleErrorHandling | +| qncReports | array(QosNotificationControlInfo) | O | 1..N | QoS Notification Control information. | | +| qosMonReports | array(QosMonitoringReport) | O | 1..N | QoS Monitoring reporting information. | QosMonitoring | +| qosMonDatRateReps | array(QosMonitoringReport) | O | 1..N | QoS Monitoring reporting information with data rate measurements. It shall be present when the notified event is "QOS_MONITORING" and data rate measurements are available. | EnQoSMon | +| userLocationInfoTime | DateTime | O | 0..1 | Contains the NTP time at which the UE was last known to be in the location. (NOTE 3) | | +| repPralInfos | map(PresenceInfo) | O | 1..N | Reports the changes of presence reporting area. The "prald" attribute within the PresenceInfo data type shall also be the key of the map. The "presenceState" attribute within the PresenceInfo data type shall be supplied. The "additionalPrald" attribute within the PresenceInfo data type shall not be supplied. | PRA | +| ueInitResReq | UeInitiatedResourceRequest | O | 0..1 | Indicates a UE requests specific QoS handling for selected SDF. | | +| refQosIndication | boolean | O | 0..1 | If it is included and set to true, the reflective QoS is supported by the UE. If it is included and set to false, the reflective QoS is revoked by the UE. | | +| qosFlowUsage | QosFlowUsage | O | 0..1 | Indicates the required usage for default QoS flow. | | +| creditManageStatus | CreditManagementStatus | O | 0..1 | Indicates the reason of the credit management session failure. | | +| servNfld | ServingNfIdentity | O | 0..1 | Contains the serving network function identity. | | +| traceReq | TraceData | C | 0..1 | It shall be included if trace is required to be activated, modified or deactivated (see 3GPP TS 32.422 [24]). For trace modification, it shall contain a complete replacement of trace data. For trace deactivation, it shall contain the Null value. | | +| addIpv6AddrPrefixes | Ipv6Prefix | O | 0..1 | An additional Ipv6 Address Prefix of the served UE. (NOTE 6) | MultiIpv6AddrPrefix | +| addRelIpv6AddrPrefixes | Ipv6Prefix | O | 0..1 | Indicates an additional released IPv6 Address Prefix of the served UE. (NOTE 6) | MultiIpv6AddrPrefix | +| multiIpv6Prefixes | array(Ipv6Prefix) | O | 1..N | The Ipv6 Address Prefixes of the served UE. (NOTE 6) | UnlimitedMultiIpv6Prefix | +| multiRelIpv6Prefixes | array(Ipv6Prefix) | O | 1..N | Indicates the released IPv6 Address Prefixes of the served UE. (NOTE 6) | UnlimitedMultiIpv6Prefix | +| tsnBridgeInfo | TsnBridgeInfo | O | 0..1 | Transports TSC user plane node information. | TimeSensitive Networking | +| tsnBridgeManCont | BridgeManagementContainer | O | 0..1 | Transports TSC user plane node management information. | TimeSensitive Networking | +| tsnPortManContDstt | PortManagementContainer | O | 0..1 | When DS-TT functionality is used, transports TSN port management information for the DS-TT port. | TimeSensitive Networking | + +| | | | | | | +|-------------------------|----------------------------------|---|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| tsnPortManContNwtt
s | array(PortManagementContainer) | O | 1..N | When NW-TT functionality is used, transports TSN port management information for one or more NW-TT ports. | TimeSensitive Networking | +| tscNotifUri | Uri | O | 0..1 | For PMIC/UMIC UPF event notification target address of the TSCTSF or TSN AF receiving the TSC management information. | ExposureToTSC | +| tscNotifCorreId | string | O | 0..1 | Correlation identifier for TSC management information notifications. | ExposureToTSC | +| maPduInd | MaPduIndication | O | 0..1 | Contains the MA PDU session indication, i.e., MA PDU Request or MA PDU Network-Upgrade Allowed. (NOTE 1) | ATSSS | +| atsssCapab | AtsssCapability | O | 0..1 | Contains the ATSSS capability supported for the MA PDU session. (NOTE 1) | ATSSS | +| mulAddrInfos | array(IpMulticastAddressInfo) | O | 1..N | Contains the IP multicast address information. | WWC | +| policyDecFailureReports | array(PolicyDecisionFailureCode) | O | 1..N | Indicates the type(s) of the failed policy decision and/or condition data. | PolicyDecision ErrorHandling | +| invalidPolicyDecs | array(InvalidParam) | O | 1..N | Indicates the invalid parameters for the reported type(s) of the failed policy decision and/or condition data. | ExtPolicyDecisionErrorHandling | +| trafficDescriptors | array(DddTrafficDescriptor) | O | 1..N | Contains the traffic descriptor(s) | DDNEventPolicyControl | +| typesOfNotif | array(DlDataDeliveryStatus) | O | 1..N | Contains the type of notification of DDD Status. | DDNEventPolicyControl | +| pccRuleId | string | O | 0..1 | Contains the identifier of the PCC rule which is used for traffic detection of event (e.g. DDN failure). | DDNEventPolicyControl2 | +| interGrpIds | array(GroupId) | O | 1..N | Internal Group Identifier(s) of the served UE. | GroupIdListChange | +| satBackhaulCategory | SatelliteBackhaul Category | O | 0..1 | Indicates the satellite backhaul category or non-satellite backhaul used for the PDU session. If the "EnSatBackhaulCatChg" feature is supported, the dynamic satellite backhaul categories may also be provided. | SatBackhaulCategoryChg | +| pcfUeInfo | PcfUeCallbackInfo | O | 0..1 | PCF for the UE callback URI and SBA binding information. | AMInfluence | +| nwdafDatas | array(NwdafData) | O | 1..N | List of NWDAF Instance IDs and their associated Analytics IDs consumed by the NF service consumer. | EneNA | +| anGwStatus | boolean | O | 1..N | When it is included and set to "true", it indicates that the AN-Gateway has failed and that the PCF should refrain from sending policy decisions to the SMF until it is informed that the AN-Gateway has been recovered. (NOTE 1) | SGWRest | +| uePolCont | UePolicyContainer | C | 0..1 | Indicates a UE policy container received from the UE. (NOTE 1) | EpsUrsp | +| urspEnfInfo | UrspEnforcementInfo | O | 0..1 | Contains the reporting of URSP rule enforcement from the UE. | URSPEnforcement | +| sscMode | SscMode | O | 0..1 | SSC Mode of the PDU session.

It may be present when the "urspEnfInfo" attribute is present. | URSPEnforcement | +| ueReqDnn | Dnn | O | 0..1 | UE requested DNN.

It may be present when the "urspEnfInfo" attribute is present. | URSPEnforcement | + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| redundantPduSessionInfo | RedundantPduSessionInformation | O | 0..1 | RSN and PDU session pair ID of the redundant PDU session. It may be present when the "urspEnfInfo" attribute is present. | URSPEnforcement | +| l4sReports | array(L4sSupportInfo) | O | 1..N | ECN marking for L4S support report information. | L4S | +| sliceInfo | Snssai | O | 0..1 | Identifies the updated S-NSSAI. | NetSliceRepl | +| batOffsetInfo | BatOffsetInfo | O | 0..1 | Contains the BAT offset and the optionally adjusted periodicity. | EnTSCAC | +| hrsboInd | boolean | O | 0..1 | HR-SBO support indication. If present and set to "true", it indicates that the HR-SBO is supported. If present and set to "false", it indicates that the HR-SBO is not supported. (NOTE 7) | HR-SBO | +| NOTE 1: This attribute is only applicable to the 5GS and EPC/E-UTRAN interworking scenario as defined in Annex B. | | | | | | +| NOTE 2: The value provided in this attribute is implementation specific. The only constraint is that the NF service consumer shall supply a different identifier for each overlapping address domain (e.g. the SMF NF instance identifier). | | | | | | +| NOTE 3: The age of UE location included within the "userLocationInfoTime" attribute is the age of the 3GPP access UE location received from the AMF and shall be included only when the reported "userLocationInfo" attribute includes the UE location in the 3GPP access. | | | | | | +| NOTE 4: The SMF may encode both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute. | | | | | | +| NOTE 5: Only one of "vplmnQos" or "vplmnQosNotApp" attributes may be present. | | | | | | +| NOTE 6: When the "WWC" feature is supported, according to 3GPP TS 23.316 [42], clause 8.3.1 and 4.6.2, more than one IPv6 prefix shorter than /64 or more than one full IPv6 address with a /128 prefix may be allocated to the RG. When feature Multilpv6AddrPrefix is supported, additional IPv6 prefix shorter than /64 or full IPv6 address with a /128 prefix may be reported encoded as the "addlpv6AddrPrefixes" and the "addRelIpv6AddrPrefixes" attributes, if the "Multilpv6AddrPrefix" feature is supported, or as the "multilpv6Prefixes" and the "multiRelIpv6Prefixes" attributes, if the "UnlimitedMultilpv6Prefix" feature is supported. If the attribute "multilpv6Prefixes" is provided, then attributes "ipv6AddressPrefix" and "addlpv6AddrPrefixes" shall be both absent. If the attribute "multiRelIpv6Prefixes" is provided, then attributes "relIpv6AddressPrefix" and "addRelIpv6AddrPrefixes" shall be both absent. | | | | | | +| NOTE 7: This attribute may be present when the "PLMN_CH" trigger is included in "repPolicyCtrlReqTriggers" attribute. | | | | | | + +Editor's Note: The content of the "sliceInfo" attribute for the case where the NF service consumer reports a change from the Alternative S-NSSAI to the initial S-NSSAI of the PDU Session via the "NET\_SLICE\_REPL" PCRT is FFS and pending stage 2 feedback. + +Editor's Note: It is FFS how the bat offset is indicated and reported per PCC rule. + +Editor's Note: Whether existing QoS monitoring data types and attributes are reused or new ones are added is to be discussed. + +## 5.6.2.20 Type UpPathChgEvent + +**Table 5.6.2.20-1: Definition of type UpPathChgEvent** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|----------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| notificationUri | Uri | M | 1 | Notification address of AF receiving the event notification. | TSC | +| notifCorrelId | string | M | 1 | It is used to set the value of Notification Correlation ID in the notification sent by the NF service consumer. | TSC | +| dnaiChgType | DnaiChangeType | M | 1 | Indicates the type of DNAI change. | TSC | +| afAckInd | boolean | O | 0..1 | Identifies whether the AF acknowledgement of UP path event notification is expected. Set to "true" if the AF acknowledgement is expected; otherwise set to "false". Default value is "false" if omitted. | URLLC | + +### 5.6.2.21 Type TerminationNotification + +**Table 5.6.2.21-1: Definition of type TerminationNotification** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------------------------|---|-------------|----------------------------------------------------------------------------------------------|---------------| +| resourceUri | Uri | M | 1 | The resource URI of the individual SM policy resource related to the notification.
(NOTE) | | +| cause | SmPolicyAssociationReleaseCause | M | 1 | The cause why the PCF requests the termination of the policy association. | | + +NOTE: Either the complete resource URI included in the "resourceUri" attribute or the "apiSpecificResourceUriPart" component (see clause 5.1) of the resource URI included in the "resourceUri" attribute can be used by the SMF for the identification of the individual SM policy resource related to the notification. + +### 5.6.2.22 Type AppDetectionInfo + +**Table 5.6.2.22-1: Definition of type AppDetectionInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| appId | string | M | 1 | A reference to the application detection filter configured at the UPF and reported to the NF service consumer. | | +| instanceId | string | O | 0..1 | Identifier dynamically assigned by UPF and reported to the NF service consumer in order to allow correlation of application Start and Stop events to the specific service data flow description, if service data flow descriptions are deducible. | | +| sdfDescriptions | array(FlowInformation) | O | 1..N | Contains the detected service data flow descriptions if they are deducible. When present, it shall only include the "flowDescription" and the "flowDirection" attributes of the FlowInformation data type. | | + +### 5.6.2.23 Type AccNetChld + +**Table 5.6.2.23-1: Definition of type AccNetChld** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------|---------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| accNetChldValue | ChargingId | C | 0..1 | Contains a charging identifier. (NOTE 1) | | +| accNetChargIdString | string | C | 0..1 | A character string containing the charging identifier (see clause 5.1.9.1 of 3GPP TS 32.255 [35]). (NOTE 1) | AccNetChargId_String | +| refPccRuleIds | array(string) | O | 1..N | Applicable only to EPS interworking scenarios. Contains the identifier of the PCC rule(s) that are associated to the provided Access Network Charging Identifier. | | +| sessionChScope | boolean | O | 0..1 | When included and set to true, it indicates that the provided Access Network Charging Identifier applies to the whole PDU Session. Default value is false if omitted. Value false applies only to EPS interworking scenarios | | + +NOTE 1: The "accNetChldValue" shall be used to encode the charging identifier when the charging identifier is within the Uint32 value range. The "accNetChargIdString" attribute shall be used to encode the charging identifier when the "AccNetChargId\_String" feature is supported by the SMF and the PCF and the charging identifier is out of the Uint32 range. + +NOTE 2: When the "AccNetChargId\_String" feature is not supported and the value of the charging identifier is out of the ChargingId data type value range (Uint32) it is not possible to ensure a proper charging correlation using value of the "accNetChldValue" attribute. + +### 5.6.2.24 Type RequestedRuleData + +**Table 5.6.2.24-1: Definition of type RequestedRuleData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------|---------------| +| refPccRuleIds | array(string) | M | 1..N | An array of PCC rule id references to the PCC rules associated with the control data. | | +| reqData | array(RequestedRuleDataType) | M | 1..N | Array of requested rule data type elements indicating what type of rule data is requested for the corresponding referenced PCC rules. | | + +### 5.6.2.25 Type RequestedUsageData + +**Table 5.6.2.25-1: Definition of type RequestedUsageData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| refUmlDs | array(string) | C | 1..N | An array of usage monitoring data id references to the usage monitoring data instances for which the PCF is requesting an accumulated usage report. This attribute shall only be provided when allUmlDs is not set to true. | | +| allUmlDs | boolean | C | 0..1 | This boolean indicates whether the requested accumulated usage report applies to all usage monitoring data instances. When it is not included, it means that the requested accumulated usage report shall only apply to the usage monitoring data instances referenced in the refUmlDs attribute. | | + +## 5.6.2.26 Type UeCampingRep + +Table 5.6.2.26-1: Definition of type UeCampingRep + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------------|--------------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| accessType | AccessType | C | 0..1 | The Access Type where the served UE is camping.
It shall be provided for trigger "AC_TY_CH". | | +| ratType | RatType | C | 0..1 | The RAT Type where the served UE is camping.
It shall be provided for triggers "RAT_TY_CH" and/or "AC_TY_CH". | | +| servNfId | ServingNfIdentity | C | 0..1 | Contains the serving network function identity.
It shall be provided for trigger "SCNN_CH". | | +| servingNetwork | PlmnIdNid | C | 0..1 | The serving network (a PLMN or an SNPN) where the served UE is camping. For an SNPN the NID together with the PLMN ID identifies the SNPN.
It shall be provided for trigger "PLMN_CH". | | +| userLocationInfo | UserLocation | C | 0..1 | The location(s) of the served UE.
It shall be provided for trigger "SAREA_CH".
(NOTE) | | +| ueTimeZone | TimeZone | C | 0..1 | The time zone where the served UE is camping.
It shall be provided for trigger "UE_TZ_CH" | | +| netLocAccSupp | NetLocAccessSupport | O | 0..1 | Indicates that the access network does not support the reporting of the requested access network information. | NetLoc | +| satBackhaulCategory | SatelliteBackhaulCategory | C | 0..1 | Indicates satellite backhaul category or non-satellite backhaul used for the PDU session.
If the "EnSatBackhaulCatChg" feature is supported, the different dynamic satellite backhaul categories may also be provided.
It shall be provided for trigger "SAT_CATEGORY_CHG" | SatBackhaulCategoryChg_v2 | +| urspEnfInfo | UrspEnforcementInfo | C | 0..1 | Contains the reporting of URSP rule(s) enforcement received from the UE.
It shall be provided for trigger "URSP_ENFORCEMENT_INFO" | URSPEnforcement | +| sscMode | SscMode | O | 0..1 | SSC Mode of the PDU session.

It may be present when the "urspEnfInfo" attribute is present. | URSPEnforcement | +| ueReqDnn | Dnn | O | 0..1 | UE requested DNN.

It may be present when the "urspEnfInfo" attribute is present. | URSPEnforcement | +| redundantPduSessionInfo | RedundantPduSessionInformation | O | 0..1 | RSN and PDU session pair ID of the redundant PDU session.
It may be present when the "urspEnfInfo" attribute is present. | URSPEnforcement | + +NOTE: The SMF may encode both 3GPP and non-3GPP access UE location in the "userLocationInfo" attribute. + +## 5.6.2.27 Type RuleReport + +**Table 5.6.2.27-1: Definition of type RuleReport** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|-----------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| pccRuleIds | array(string) | M | 1..N | Contains the identifier(s) of the affected PCC rule(s). | | +| ruleStatus | RuleStatus | M | 1 | Indicates the status of the PCC rule(s). | | +| contVers | array(ContentVersion) | C | 1..N | Indicates the version(s) of the PCC rule(s). If the RuleVersioning feature is supported, the content version shall be included in this attribute if it was included when the corresponding PCC rule was installed or modified. | RuleVersioning | +| failureCode | FailureCode | C | 0..1 | Indicates the reason why the PCC Rule(s) are being reported. It shall be included when the NF service consumer reports the failure of the enforcement of the PCC rule(s). | | +| retryAfter | UInteger | O | 0..1 | Indicates the estimate on how long it will take before it can be considered the UE is reachable. It may be provided when the failureCode attribute indicates UE_TEMPORARILY_UNAVAILABLE. The value shall be in seconds. | UEUnreachable | +| finUnitAct | FinalUnitAction | O | 0..1 | Contains the termination action that is applied, when the user's account cannot cover the service cost. | | +| ranNasRelCauses | array(RanNasRelCause) | O | 1..N | Indicates the RAN or NAS release cause code information. | RAN-NAS-Cause | +| altQosParamId | string | O | 0..1 | Indicates the alternative QoS parameter set that the NG-RAN can guarantee. It is included during the report of success resource allocation and indicates that NG-RAN used an alternative QoS profile because the requested QoS could not be allocated. | AuthorizationWithRequiredQoS | + +## 5.6.2.28 Type RanNasRelCause + +**Table 5.6.2.28-1: Definition of type RanNasRelCause** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-------------------|---|-------------|---------------------------------------------|---------------| +| ngApCause | NgApCause | O | 0..1 | Indicates the cause value of NGAP protocol. | RAN-NAS-Cause | +| 5gMmCause | 5GMmCause | O | 0..1 | Indicates the cause value of 5GMM protocol. | RAN-NAS-Cause | +| 5gSmCause | 5GSmCause | O | 0..1 | Indicates the cause value of 5GSM protocol. | RAN-NAS-Cause | +| epsCause | EpsRanNasRelCause | O | 0..1 | Indicates the RAN/NAS cause value for EPS. | RAN-NAS-Cause | + +### 5.6.2.29 Type UeInitiatedResourceRequest + +**Table 5.6.2.29-1: Definition of type UeInitiatedResourceRequest** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-------------------------|---|-------------|----------------------------------------------------------------------------------------------------------|---------------| +| pccRuleId | string | C | 1 | Indicates a PCC rule corresponding to a QoS rule which is requested to be modified or deleted by the UE. | | +| ruleOp | RuleOperation | M | 1 | Indicates an operation for the PCC rule. | | +| packFiltInfo | array(PacketFilterInfo) | M | 1..N | Contains the information from a single packet filter sent from the NF service consumer to the PCF. | | +| precedence | integer | O | 0..1 | The requested order for the PCC rule generated from the QoS rule requested by the UE. | | +| reqQos | RequestedQos | O | 0..1 | Contains the QoS information requested by the UE. | | + +### 5.6.2.30 Type PacketFilterInfo + +**Table 5.6.2.30-1: Definition of type PacketFilterInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|---------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| packFiltId | string | O | 0..1 | An identifier of packet filter. For PCC rules created as a result of UE-initiated resource modification, the packet filter identifier is assigned by the PCF and is unique per UE and PCF instance. | | +| packFiltCont | PacketFilterContent | O | 0..1 | Contains the content of the packet filter as requested by the UE and required by the PCF to create the PCC rules. | | +| tosTrafficClass | string | O | 0..1 | 2-octet string. The first octet contains the Ipv4 Type-of-Service or the Ipv6 Traffic-Class field and the second octet contains the ToS/Traffic mask field in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. One example is that of a TFT packet filter as defined in 3GPP TS 24.008 [41]. | | +| spi | string | O | 0..1 | 4 octet string, representing the security parameter index of the IPSec packet in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. One example is that of a TFT packet filter as defined in 3GPP TS 24.008 [41]. | | +| flowLabel | string | O | 0..1 | 3-octet string, representing the Ipv6 flow label header field in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. One example is that of a TFT packet filter as defined in 3GPP TS 24.008 [41]. | | +| flowDirection | FlowDirection | O | 0..1 | Indicates the direction/directions that a filter is applicable, downlink only, uplink only or both down- and uplink (bidirectional). | | + +### 5.6.2.31 Type RequestedQos + +**Table 5.6.2.31-1: Definition of type RequestedQos** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|-------------------------------------------------------------------------|---------------| +| 5qi | 5Qi | M | 1 | Identifier for the authorized QoS parameters for the service data flow. | | +| gbrUI | BitRate | O | 0..1 | Indicates the guaranteed bandwidth in uplink requested by the UE. | | +| gbrDI | BitRate | O | 0..1 | Indicates the max guaranteed in downlink requested by the UE. | | + +### 5.6.2.32 Type QosNotificationControlInfo + +**Table 5.6.2.32-1: Definition of type QosNotificationControlInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|-----------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| refPccRuleIds | array(string) | M | 1..N | An array of PCC rule id references to the PCC rules associated with the QosNotificationControlInfo. | | +| notifType | QosNotifType | M | 1 | Indicates whether the GBR targets for the indicated SDFs are "NOT_GUARANTEED" or "GUARANTEED" again. | | +| contVers | array(ContentVersion) | C | 1..N | Indicates the version of the PCC rule. If rule versioning feature is supported, the content version shall be included if it was included when the corresponding PCC rule was installed or modified. | RuleVersioning | +| altQosParamId | string | O | 0..1 | Indicates the alternative QoS parameter set the NG-RAN can guarantee. When it is omitted and "notifType" attribute is NOT_GUARANTEED, it indicates that the lowest priority alternative QoS profile could not be fulfilled. | AuthorizationWithRequiredQoS | +| altQosNotSupplnd | boolean | O | 0..1 | It may be set to true when the "notifType" attribute is NOT_GUARANTEED to indicate that the Alternative QoS profiles are not supported by NG-RAN. The default value false shall apply if the attribute is not present.
It may be used when the AuthorizationWithRequiredQoS feature is supported. | AltQoSProfilesSupportReport | + +### 5.6.2.33 Type PartialSuccessReport + +**Table 5.6.2.33-1: Definition of type PartialSuccessReport** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------------|----------------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------|--------------------------------| +| failureCause | FailureCause | M | 1 | Application error cause specific to this report. | | +| ruleReports | array(RuleReport) | C | 1..N | Information about the PCC rules provisioned by the PCF not successfully installed/activated. | | +| sessRuleReports | array(SessionRuleReport) | O | 1..N | Information about the session rules provisioned by the PCF not successfully installed. | SessionRuleErrorHandling | +| ueCampingRep | UeCampingRep | O | 0..1 | Includes the current applicable values corresponding to the provisioned policy control request triggers. | | +| policyDecFailureReports | array(PolicyDecisionFailureCode) | O | 1..N | Used to report the failure of the policy decision and/or condition data. | PolicyDecisionErrorHandling | +| invalidPolicyDecs | array(InvalidParam) | O | 1..N | Indicates the invalid parameters for the reported type(s) of the failed policy decision and/or condition data. | ExtPolicyDecisionErrorHandling | + +NOTE: The "ruleReports" shall be included if the SessionRuleErrorHandling feature or the PolicyDecisionErrorHandling feature is not supported. + +### 5.6.2.34 Type AuthorizedDefaultQos + +**Table 5.6.2.34-1: Definition of type AuthorizedDefaultQos** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------|----------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------|---------------| +| 5qi | 5Qi | C | 0..1 | 5G QoS Identifier. It shall be included when the Authorized Default QoS is initially provisioned. | | +| arp | Arp | C | 0..1 | Indicates the allocation and retention priority. It shall be included when the Authorized Default QoS is initially provisioned. | | +| priorityLevel | 5QIPriorityLevelRm | O | 0..1 | Unsigned integer indicating the 5QI Priority Level, within a range of 1 to 127. | | +| averWindow | AverWindowRm | O | 0..1 | Indicates the averaging window. (NOTE 1) | | +| maxDataBurstVol | MaxDataBurstVolRm | O | 0..1 | Unsigned integer indicating the maximum data burst volume. (NOTE 2) | | +| gbrUl | BitRateRm | O | 0..1 | Indicates the guaranteed bandwidth in uplink. (NOTE 1) | | +| gbrDl | BitRateRm | O | 0..1 | Indicates the guaranteed bandwidth in downlink. (NOTE 1) | | +| maxbrUl | BitRateRm | O | 0..1 | Indicates the max bandwidth in uplink. (NOTE 1) | | +| maxbrDl | BitRateRm | O | 0..1 | Indicates the max bandwidth in downlink. (NOTE 1) | | +| extMaxDataBurstVol | ExtMaxDataBurstVolRm | O | 0..1 | Unsigned integer indicating the maximum data burst volume. (NOTE 2) | EMDBV | + +NOTE 1: This attribute is only applicable to GBR type or delay critical GBR type 5QI. +NOTE 2: Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present for a Delay Critical GBR QoS flow. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurstVol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes (see clause 4.2.2.1). + +### 5.6.2.35 Type AccNetChargingAddress + +**Table 5.6.2.35-1: Definition of type AccNetChargingAddress** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|-----------|---|-------------|--------------------------------------------------------------------------------------------|---------------| +| anChargIpv4Addr | Ipv4Addr | O | 0..1 | Includes the IPv4 address of network entity within the access network performing charging. | | +| anChargIpv6Addr | Ipv6Addr | O | 0..1 | Includes the IPv6 address of network entity within the access network performing charging. | | + +NOTE: At least one address of the access network entity (the IPv4 address or the IPv6 address or both if both addresses are available) shall be included. + +### 5.6.2.36 Type ErrorReport + +**Table 5.6.2.36-1: Definition of type ErrorReport** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------------|----------------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------|--------------------------------| +| error | ProblemDetails | M | 1 | More information on the error shall be provided in the "cause" attribute of the "ProblemDetails" structure. | | +| ruleReports | array(RuleReport) | O | 1..N | Used to report the PCC rule failure. | | +| sessRuleReports | array(SessionRuleReport) | O | 1..N | Used to report the session rule failure. | SessionRuleErrorHandling | +| policyDecFailureReports | array(PolicyDecisionFailureCode) | O | 1..N | Used to report the failure of the policy decision and/or condition data. | PolicyDecisionErrorHandling | +| invalidPolicyDecs | array(InvalidParam) | O | 1..N | Indicates the invalid parameters for the reported type(s) of the failed policy decision and/or condition data. | ExtPolicyDecisionErrorHandling | + +### 5.6.2.37 Type SessionRuleReport + +**Table 5.6.2.37-1: Definition of type SessionRuleReport** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------|------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| ruleIds | array(string) | M | 1..N | Contains the identifier of the affected session rule(s). | | +| ruleStatus | RuleStatus | M | 1 | Indicates the status of the session rule(s). | | +| sessRuleFailureCode | SessionRuleFailureCode | C | 0..1 | Indicates the reason that the session rule(s) is being reported. It shall be included when the NF service consumer reports the enforcement failure of the session rule(s). | | + +### 5.6.2.38 Type ServingNfIdentity + +**Table 5.6.2.38-1: Definition of type ServingNfIdentity** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|--------------|---|-------------|-------------------------------------------------------------------------------------------------------|---------------| +| servNfInstanceId | NfInstanceId | O | 0..1 | Network Function Instance Identifier of the 5G serving CN node. It represents the AMF. | | +| guami | Guami | O | 0..1 | Globally Unique AMF Identifier. | | +| anGwAddr | AnGwAddress | O | 0..1 | Contains the access network control gateway address. It represents the S-GW or ePDG address. (NOTE 2) | | +| sgsnAddr | SgsnAddress | O | 0..1 | Contains the serving SGSN address. (NOTE 3) | 2G3GIWK | + +NOTE 1: At least one of the "servNfInstanceId", "guami", "anGwAddr", or "sgsnAddr" attributes shall be present. +NOTE 2: "anGwAddr" attribute is only applicable to the 5GS and EPC (E-UTRAN and non-3GPP access) interworking scenario as defined in Annex B. +NOTE 3: "sgsnAddr" attribute is only applicable to the 5GS and EPC (GERAN and UTRAN access) interworking scenario as defined in Annex B. + +### 5.6.2.39 Type SteeringMode + +**Table 5.6.2.39-1: Definition of type SteeringMode** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| steerModeValue | SteerModeValue | M | 1 | Indicates the value of the steering mode. | | +| active | AccessType | C | 0..1 | Indicates the Active access. It shall be included when the "steerModeValue" attribute is set to "ACTIVE_STANDBY". | | +| standby | AccessTypeRm | O | 0..1 | Indicates the Standby access. It may be included when the "steerModeValue" attribute is set to "ACTIVE_STANDBY". | | +| 3gLoad | UInteger | C | 0..1 | Indicates the traffic load to steer to the 3GPP Access expressed in one percent.
It shall be set to 0, 10, 20, 30, 40, 50, 60, 70, 80, 90 or 100.
It shall be included when the "steerModeValue" attribute is set to "LOAD_BALANCING". | | +| prioAcc | AccessType | C | 0..1 | Indicates the high priority access.
It shall be included when the "steerModeValue" attribute is set to "PRIORITY_BASED". | | +| thresValue | ThresholdValue | O | 0..1 | Indicates the threshold value(s) for RTT and/or Packet Loss Rate. If the EnATSSS feature is supported, it may be included when the "steerModeValue" attribute is set to "LOAD_BALANCING" with fixed split percentages or "PRIORITY_BASED" or, when the feature EnATSSS_v2 is supported, "REDUNDANT". (NOTE 1) (NOTE 2) | EnATSSS | +| steerModeInd | SteerModeIndicator
or | O | 0..1 | Contains Autonomous load-balance indicator or UE-assistance indicator. If the EnATSSS feature is supported, it may be included when the "steerModeValue" attribute is set to "LOAD_BALANCING". (NOTE 1) | EnATSSS | +| primary | AccessTypeRm | O | 0..1 | Indicates the Primary access. It shall be included when the "steerModeValue" attribute is set to "REDUNDANT". | EnATSSS_v2 | + +NOTE 1: The "thresValue" attribute and "steerModeInd" attribute are mutually exclusive. +NOTE 2: When the feature EnATSSS\_v2 is supported, if the Steering Mode is "REDUNDANT", either a Maximum RTT or a Maximum Packet Loss Rate may be provided, but not both. + +## 5.6.2.40 Type QosMonitoringData + +**Table 5.6.2.40-1: Definition of type QosMonitoringData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|----------------------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| qmId | string | M | 1 | Univocally identifies the QoS monitoring policy data within a PDU session. | | +| reqQosMonParams | array(RequestedQosMonitoringParameter) | M | 1..N | Indicates QoS information to be monitored, e.g. the UL packet delay, DL packet delay and/or round trip packet delay and/or congestion information between the UE and the UPF is to be monitored when the QoS Monitoring is enabled for the service data flow.
(NOTE 1)
If the "EnQoSMon" feature is supported, it indicates the congestion information to be monitored, e.g., the UL congestion information and/or the the DL congestion information | QoSMonitoring
EnQoSMon | +| repFreqs | array(ReportingFrequency) | M | 1..N | Indicates the frequency for the reporting, such as event triggered and/or periodic. | | +| repThreshDl | integer | O | 0..1 | Indicates the threshold in units of milliseconds for DL packet delay. Only applicable when the "reqQosMonParams" attribute includes the "DOWNLINK" value and the "repFreqs" attribute includes the value "EVENT_TRIGGERED".
Minimum = 0. | | +| repThreshUl | integer | O | 0..1 | Indicates the threshold in units of milliseconds for UL packet delay. Only applicable when the "reqQosMonParams" attribute includes the "UPLINK" value and the "repFreqs" attribute includes the value "EVENT_TRIGGERED".
Minimum = 0. | | +| repThreshRp | integer | O | 0..1 | Indicates the threshold in units of milliseconds for round trip packet delay. Only applicable when the "reqQosMonParams" attribute includes the "ROUND_TRIP" value and the "repFreqs" attribute includes the value "EVENT_TRIGGERED".
Minimum = 0. | | +| conThreshDl | UInteger | O | 0..1 | Indicates the downlink threshold for congestion reporting. Only applicable when the "repFreqs" attribute is not supplied or the "repFreqs" is set to "EVENT_DETECTION".
Minimum = 0. | EnQoSMon | +| conThreshUl | UInteger | O | 0..1 | Indicates the downlink threshold for congestion reporting. Only applicable when the "repFreqs" attribute is not supplied or the "repFreqs" is set to "EVENT_DETECTION".
Minimum = 0. | EnQoSMon | +| waitTime | DurationSecRm | O | 0..1 | Indicates the minimum waiting time between subsequent reports. Only applicable when the "repFreqs" attribute includes the value "EVENT_TRIGGERED". | | +| repPeriod | DurationSecRm | O | 0..1 | Indicates the reporting period. Only applicable when the "repFreqs" attribute includes the value "PERIODIC".
If the feature "PacketDelayFailureReport" is supported, it also indicates the time interval at which a measurement failure needs to be reported if no measurement result is provided. Only applicable when the "repFreqs" attribute includes the value "PERIODIC" and "EVENT_TRIGGERED". | | + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------|---------------|---|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| notifyUri | UriRm | O | 0..1 | Notification address of the AF or if the "ExposureToEAS" feature is supported, of the Local NEF or AF receiving the event notification. It shall be included if the PCF determines that the notification shall be sent to the AF directly from the NF service consumer or the PCF determines that the notification shall be sent to the Local NEF or AF directly from the UPF. (NOTE 2). | | +| notifyCorreId | string | O | 0..1 | It is used to set the value of Notification Correlation ID in the notification sent by the NF service consumer or, if the "ExposureToEAS" feature is supported, the UPF. It may be included if the PCF determines that the notification shall be sent to the AF directly from the NF service consumer or the PCF determines that the notification shall be sent to the Local NEF or AF directly from the UPF. (NOTE 2). | | +| directNotifInd | boolean | O | 0..1 | Indicates that the direct event notification sent to the Local NEF or AF by the UPF is requested if it is included and set to true. | ExposureToEAS | +| avrgWndw | AverWindowRm | O | 0..1 | Averaging window for the calculation of the data rate for the service data flow. It may be present when the "repThreshDatRateDI" and/or "repThreshDatRateUI" attributes are present. | EnQoSMon | +| repThreshDatRateDI | BitRateRm | O | 0..1 | Indicates the threshold for DL data rate. Only applicable when the "notifMethod" attribute is not supplied or the "notifMethod" is supplied and set to "EVENT_DETECTION". | EnQoSMon | +| repThreshDatRateUI | BitRateRm | O | 0..1 | Indicates the threshold for UL data rate. Only applicable when the "notifMethod" attribute is not supplied or the "notifMethod" is supplied and set to "EVENT_DETECTION". | EnQoSMon | +| dataCollAppId | ApplicationId | O | 0..1 | Indicates the Data Collection Application Identifier used to identify the QoS monitoring event exposure subscription. | UPEAS | +| NOTE 1: In this release of the specification the maximum number of elements in the array is 3. | | | | | | +| NOTE 2: The attributes "notifyUri" and "notifyCorreId" shall not be set to NULL if the "ExposureToEAS" feature is not supported. | | | | | | + +### 5.6.2.41 Type TsnBridgeInfo + +**Table 5.6.2.41-1: Definition of type TsnBridgeInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| bridgeId | Uint64 | O | 0..1 | Contains a TSC user plane node Id. It may contain the unique TSN Bridge MAC address for IEEE TSN networks (as defined in IEEE Std 802.1Q-2018 [45] clause 14.2.5) or may contain a unique identifier assigned within 5GS (that identifies, e.g. a DetNet Router). | | +| dsttAddr | MacAddr48 | O | 0..1 | When DS-TT functionality is used, contains the MAC address of DS-TT. | | +| dsttPortNum | TsnPortNumber | O | 0..1 | Port allocated to a PDU session. | | +| dsttResidTime | UInteger | O | 0..1 | When DS-TT functionality is used, the time taken within the UE and DS-TT to forward a packet between the UE/DS-TT port encoded as specified in clause 9.11.4.26 of 3GPP TS 24.501 [20] starting with octet 3 and ending with octet 10. | | +| mtulpv4 | Uint16 | O | 0..1 | MTU size, in octets, for the largest IPv4 packet that the interface will send and receive, as specified in IETF RFC 8344 [56].
Minimum = 68 | MTU_Size | +| mtulpv6 | Uint32 | O | 0..1 | MTU size, in octets, of the largest IPv6 packet that the interface will send and receive, as specified in IETF RFC 8344 [55].
Minimum = 1280 | MTU_Size | + +## 5.6.2.42 Type QosMonitoringReport + +**Table 5.6.2.42-1: Definition of type QosMonitoringReport** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|----------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| refPccRuleIds | array(string) | M | 1..N | An array of PCC rule id references to the PCC rules associated with the QoS Monitoring report. | | +| ulDelays | array(integer) | O | 1..N | Uplink packet delay in units of milliseconds. (NOTE 1) | | +| dlDelays | array(integer) | O | 1..N | Downlink packet delay in units of milliseconds. (NOTE 1) | | +| rtDelays | array(integer) | O | 1..N | Round trip delay in units of milliseconds. (NOTE 1) | | +| ulCongInfo | UInteger | O | 1..N | Uplink congestion information (without "%" sign). (NOTE 3) | EnQoSMon | +| dlCongInfo | UInteger | O | 0..1 | Downlink congestion information. (without "%" sign). (NOTE 3) | EnQoSMon | +| pdmf | boolean | O | 0..1 | Packet delay measurement failure indicator. When set to true, it indicates that a packet delay failure has occurred.
Default value is false if omitted. (NOTE 2) | PacketDelayFailureReport | +| cimf | boolean | O | 0..1 | Congestion information measurement failure indicator. When set to true, it indicates that a congestion information failure has occurred.
Default value is false if omitted. (NOTE 3) | EnQoSMon | +| ulDataRate | BitRate | O | 0..1 | Uplink data rate. (NOTE 4) | EnQoSMon | +| dlDataRate | BitRate | O | 0..1 | Downlink data rate. (NOTE 4) | EnQoSMon | + +NOTE 1: In this release of the specification the maximum number of elements in the array is 2. If more than one value is received at one given point of time for UL packet delay, DL packet delay or round trip packet delay respectively, the NF service consumer reports the minimum and maximum packet delays to the PCF; when more than one value is sent at one given point of time for congestion information, they represent the minimum and maximum congestion information. + +NOTE 2: When the "pdmf" attribute is set to true, the rest of parameters shall not be present. + +NOTE 3: When the "ulDataRate" and/or "dlDataRate" attributes are present, the congestion related attributes and the packet delay related attributes shall not be present. + +Editor's note: Whether the "ulCongInfo" and "dlCongInfo" attributes are single or plural is FFS. + +Editor's note: It is FFS whether the "cimf" attribute is needed. + +Editor's Note: It is FFS whether the QoS monitoring requirements for congestion measurements are different than the ones for packet delay, i.e., it is FFS whether reporting period and reporting frequency apply, or different criteria needs to be applied. + +## 5.6.2.43 Type AdditionalAccessInfo + +**Table 5.6.2.43-1: Definition of type AdditionalAccessInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------|---|-------------|-------------------------------------------------|---------------| +| accessType | AccessType | M | 1 | The Access Type where the served UE is camping. | | +| ratType | RatType | O | 0..1 | The RAT Type where the served UE is camping. | | + +## 5.6.2.44 Void + +## 5.6.2.45 Type PortManagementContainer + +Table 5.6.2.45-1: Definition of type PortManagementContainer + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| portManCont | Bytes | M | 1 | Transports port management information for a DS-TT port or a NW-TT port encoded as specified in clause 9.11.4.27 of 3GPP TS 24.501 [20] starting with octet 4. | | +| portNum | TsnPortNumber | M | 1 | Provides port number for a DS-TT port or a NW-TT port. | | + +## 5.6.2.46 Type IpMulticastAddressInfo + +Table 5.6.2.46-1: IpMulticastAddressInfo + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------|---------------| +| srcIpv4Addr | Ipv4Addr | C | 0..1 | Indicates the source IPv4 address of the DL multicast flow. Maybe included if the "ipv4MulAddr" attribute is included. | | +| ipv4MulAddr | Ipv4Addr | O | 0..1 | Indicates the destination IPv4 multicast address of the DL multicast flow. | | +| srcIpv6Addr | Ipv6Addr | C | 0..1 | Indicates the source IPv6 address of the DL multicast flow. Maybe included if the "ipv6MulAddr" attribute is included. | | +| ipv6MulAddr | Ipv6Addr | O | 0..1 | Indicates the destination IPv6 multicast address of the DL multicast flow. | | + +NOTE: Either "ipv4MulAddr" attribute or "ipv6MulAddr" attribute shall be included. + +## 5.6.2.47 Type BridgeManagementContainer + +Table 5.6.2.47-1: Definition of type BridgeManagementContainer + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------|---------------| +| bridgeManCont | Bytes | M | 1 | Transports TSC user plane node management service message encoded as specified in clause 8.7 of 3GPP TS 24.539 [49]. | | + +## 5.6.2.48 Type DownlinkDataNotificationControl + +Table 5.6.2.48-1: Definition of type DownlinkDataNotificationControl + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------------------------|---|-------------|---------------------------------------------------|------------------------| +| notifCtrlInds | array(NotificationControlIndication) | M | 1..N | Indicates the event notification(s) is requested. | DDNEEventPolicyControl | +| typesOfNotif | array(DIDataDeliveryStatus) | O | 1..N | Contains the type of notification of DDD Status. | DDNEEventPolicyControl | + +NOTE: In this release of the specification the maximum number of elements in the array is 2. + +### 5.6.2.49 Type DownlinkDataNotificationControlRm + +This data type is defined in the same way as the "DownlinkDataNotificationControl" data type, but: + +- with the OpenAPI "nullable: true" property; +- the removable attributes "notifCtrlInds", and "typesOfNotif" attribute are defined as nullable in the OpenAPI. + +### 5.6.2.50 Type SgsnAddress + +**Table 5.6.2.50-1: Definition of type SgsnAddress** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------------------------------------------------------------------------------------------------------------------------------|-----------|---|-------------|-----------------------------------------------------------------------|---------------| +| sgsnIpv4Addr | Ipv4Addr | O | 0..1 | Includes the IPv4 address of the access network gateway control node. | | +| sgsnIpv6Addr | Ipv6Addr | O | 0..1 | Includes the IPv6 address of the access network gateway control node. | | +| NOTE: At least one address of the SGSN (the IPv4 address or the IPv6 address or both if both addresses are available) shall be included. | | | | | | + +### 5.6.2.51 Void + +### 5.6.2.52 Type ThresholdValue + +**Table 5.6.2.52 -1: Definition of type ThresholdValue** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------------------------------------------|------------------|---|-------------|-----------------------------------------------------------------------------------------|---------------| +| rttThres | UIntegerRm | O | 0..1 | Unsigned integer identifying a threshold value of Maximum RTT in units of milliseconds. | | +| plrThres | PacketLossRateRm | O | 0..1 | Indicates a threshold value of Maximum Packet Loss Rate. | | +| NOTE: At least one of the attributes shall be included. | | | | | | + +### 5.6.2.53 Type NwdafData + +**Table 5.6.2.53-1: Definition of type NwdafData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|-------------------|---|-------------|--------------------------------------------------------------------------------|---------------| +| nwdafInstanceId | NfInstanceId | M | 1 | Uniquely identifies the NWDAF Instance ID consumed by the NF service consumer. | | +| nwdafEvents | array(NwdafEvent) | O | 1..N | List of Analytics IDs consumed by the NF service consumer. | | + +### 5.6.2.54 Type CallInfo + +**Table 5.6.2.54-1: Definition of type CallInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|---------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| callingPartyAddrs | array(string) | O | 1..N | Identifies the address(es) (SIP URI or Tel URI) which identifies the party (Public User Identity or Public Service Identity) initiating a SIP transaction. The coding of each calling party address is the same as defined as clause 7.2.33 of 3GPP TS 32.299[60] | | +| calleeInfo | CalleeInfo | O | 0..1 | Identifies the callee information | | + +### 5.6.2.55 Type CalleeInfo + +**Table 5.6.2.55-1: Definition of type CalleeInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|---------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| calledPartyAddr | string | O | 0..1 | Holds the address of the party (Public User ID or Public Service ID) to whom the SIP transaction is posted in the context of an end-to-end SIP transaction as defined in clause 7.2.32 in 3GPP TS 32.299 [60]. | | +| requestPartyAddrs | array(string) | O | 1..N | Holds the address(es) of the party (Public User ID or Public Service ID) to whom the SIP transaction was originally posted as defined in clause 7.2.176 in 3GPP TS 32.299 [60]. | | +| calledAssertIds | array(string) | O | 1..N | Holds the address(es) (SIP URI and/or Tel URI) of the party (Public User ID or Public Service ID) of the finally asserted called party as defined in clause 7.2.31 of 3GPP TS 32.299 [60]. | | + +### 5.6.2.56 Type TrafficParaData + +**Table 5.6.2.56-1: Definition of type TrafficParaData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|-----------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| periodInfo | PeriodicityInfo | O | 0..1 | Indicates the time period between the start of the two data bursts in Uplink and/or Downlink direction. | | +| reqTrafficParas | array(TrafficParameterMeas) | M | 1..N | Indicates the traffic parameters to be measured.
(NOTE) | | +| repFreqs | array(Reporting Frequency) | M | 1..N | Represents the notification method (periodic or on event detection). | | +| dlN6JitterThr | UInteger | O | 0..1 | Indicates to measure the downlink N6 jitter range associated with downlink Periodicity. | | +| repPeriod | DurationSecRm | O | 0..1 | Indicates the time interval between successive event notifications. Only applicable when the "notifMethod" attribute includes the value "PERIODIC". | | + +NOTE: The DL\_PERIOD and UL\_PERIOD may be provided in the "reqTrafficParas" attribute if the "periodUI" and "periodUL" attributes contained in "periodInfo" attribute are not included. + +### 5.6.2.57 Type L4sSupportInfo + +**Table 5.6.2.57-1: Definition of type L4sSupportInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------|---|-------------|------------------------------------------------------------------------------------------------------------------|---------------| +| refPccRuleIds | array(string) | M | 1..N | An array of PCC rule id references to the PCC rules associated with the ECN marking for L4S support information. | | +| notifType | L4sNotifType | M | 1 | Indicates whether the ECN marking for L4S for the indicated SDFs are "NOT_AVAILABLE" or "AVAILABLE" again. | | + +### 5.6.2.58 Void + +### 5.6.2.59 Type SliceUsgCtrlInfo + +**Table 5.6.2.59-1: Definition of type SliceUsgCtrlInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------|---------------|---|-------------|----------------------------------------------------------|---------------| +| pduSessInactivTimer | DurationSecRm | O | 0..1 | Represents the slice PDU Session inactivity timer value. | | + +## 5.6.3 Simple data types and enumerations + +### 5.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +### 5.6.3.2 Simple data types + +The simple data types defined in table 5.6.3.2-1 shall be supported. For additional simple data types see 3GPP TS 29.571 [11]. + +**Table 5.6.3.2-1: Simple data types** + +| Type Name | Type Definition | Description | Applicability | +|-----------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| 5GSmCause | UInteger | Indicates the 5GSM cause code value as defined in clause 9.11.4.2 of 3GPP TS 24.501 [20]. | RAN-NAS-Cause | +| EpsRanNasRelCause | string | Indicates the RAN or NAS release cause code information in 3GPP-EPS access type or indicates the TWAN or untrusted WLAN release cause code information in Non-3GPP-EPS access type. It shall be coded as per the RAN/NAS Cause in clause 8.103 of 3GPP TS 29.274 [37], starting with Octet 5. | RAN-NAS-Cause | +| FlowDescription | string | Defines a packet filter for an IP flow. Refer to clause 5.4.2 of 3GPP TS 29.212 [23] for encoding. | | +| PacketFilterContent | string | Defines a packet filter for an IP flow. Refer to clause 5.3.54 of 3GPP TS 29.212 [23] for encoding. | | +| TsnPortNumber | UInteger | Port number for the device side of the PDU session or for the NW-TT port. | TimeSensitiveNetworking | +| ApplicationDescriptor | Bytes | Defines the OS Id and the OS application identifier for an ATSSS rule, where the OS Id is optional. It is a sequence of octets representing the traffic descriptor(s) of the ATSSS rule as Os Id, if applicable, and Os App Id as defined in table 6.1.3.2-1 of 3GPP TS 24.193 [43]. | ATSSS | +| UePolicyContainer | Bytes | Defines a UE policy delivery service message. Refer to Annex D.5 of 3GPP TS 24.501 [20] for encoding. | EpsUrsp | +| UrspEnforcementInfo | Bytes | Defines a UE policy Enforcement Report. Refer to 3GPP TS 24.501 [20], clause 9.11.4 for encoding. | URSPEnforcement | + +### 5.6.3.3 Enumeration: FlowDirection + +**Table 5.6.3.3-1: Enumeration FlowDirection** + +| Enumeration value | Description | Applicability | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| DOWNLINK | The corresponding filter applies for traffic to the UE. | | +| UPLINK | The corresponding filter applies for traffic from the UE. | | +| BIDIRECTIONAL | The corresponding filter applies for traffic both to and from the UE. | | +| UNSPECIFIED | The corresponding filter applies for traffic to the UE (downlink), but has no specific direction declared. The service data flow detection shall apply the filter for uplink traffic as if the filter was bidirectional. The PCF shall not use the value UNSPECIFIED in filters created by the network in NW-initiated procedures. The PCF shall only include the value UNSPECIFIED in filters in UE-initiated procedures if the same value is received from the NF service consumer. | | + +### 5.6.3.4 Enumeration: ReportingLevel + +**Table 5.6.3.4-1: Enumeration ReportingLevel** + +| Enumeration value | Description | Applicability | +|-------------------|----------------------------------------------------------------------------------------------------|---------------| +| SER_ID_LEVEL | Indicates that the usage shall be reported on service id and rating group combination level. | | +| RAT_GR_LEVEL | Indicates that the usage shall be reported on rating group level. | | +| SPON_CON_LEVEL | Indicates that the usage shall be reported on sponsor identity and rating group combination level. | | + +### 5.6.3.5 Enumeration: MeteringMethod + +**Table 5.6.3.5-1: Enumeration MeteringMethod** + +| Enumeration value | Description | Applicability | +|-------------------|-----------------------------------------------------------------------------------------------|---------------| +| DURATION | Indicates that the duration of the service data flow traffic shall be metered. | | +| VOLUME | Indicates that volume of the service data flow traffic shall be metered. | | +| DURATION_VOLUME | Indicates that the duration and the volume of the service data flow traffic shall be metered. | | +| EVENT | Indicates that events of the service data flow traffic shall be metered. | | + +### 5.6.3.6 Enumeration: PolicyControlRequestTrigger + +**Table 5.6.3.6-1: Enumeration PolicyControlRequestTrigger** + +| Enumeration value | Description | Applicability | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| PLMN_CH | PLMN Change. | | +| RES_MO_RE | A request for resource modification has been received by the NF service consumer. (NOTE) | | +| AC_TY_CH | Access Type Change. It also indicates the addition or removal of Access Type for MA PDU session. | | +| UE_IP_CH | UE IP address change. (NOTE) | | +| UE_MAC_CH | A new UE MAC address is detected or a used UE MAC address is inactive for a specific period. | | +| AN_CH_COR | Access Network Charging Correlation Information. | | +| US_RE | The PDU Session or the Monitoring key specific resources consumed by a UE either reached the threshold or needs to be reported for other reasons. | UMC | +| APP_STA | The start of application traffic has been detected. | ADC | +| APP_STO | The stop of application traffic has been detected. | ADC | +| AN_INFO | Access Network Information report. | NetLoc | +| CM_SES_FAIL | Credit management session failure. | | +| PS_DA_OFF | The NF service consumer reports when the 3GPP PS Data Off status changes. (NOTE) | 3GPP-PS-Data-Off | +| DEF_QOS_CH | Default QoS Change. (NOTE) | | +| SE_AMBR_CH | Session-AMBR Change. (NOTE) | | +| QOS_NOTIF | The NF service consumer notify the PCF when receiving notification from RAN that QoS targets of the QoS Flow cannot be guaranteed or can be guaranteed. | | +| NO_CREDIT | Out of credit. | | +| REALLO_OF_CREDIT | Reallocation of credit | ReallocationOfCredit | +| PRA_CH | Change of UE presence in Presence Reporting Area. | PRA | +| SAREA_CH | Location Change with respect to the Serving Area. | | +| SCNN_CH | Location Change with respect to the Serving CN node. | | +| RE_TIMEOUT | Indicates the NF service consumer generated the request because there has been a PCC revalidation timeout (i.e. Enforced PCC rule request defined in table 6.1.3.5.-1 of 3GPP TS 23.503 [6]). | | +| RES_RELEASE | Indicates that the NF service consumer can inform the PCF of the outcome of the release of resources for those rules that require so. | RAN-NAS-Cause | +| SUCC_RES_ALLO | Indicates that the NF service consumer shall inform the PCF of the successful resource allocation for those rules that requires so. | | +| RAT TY_CH | RAT type change. | | +| REF_QOS_IND_CH | Reflective QoS indication Change. | | +| NUM_OF_PACKET_FILTER | Indicates that the NF service consumer shall report the number of supported packet filter for signalled QoS rules. (NOTE) Only applicable to the interworking scenario as defined in Annex B. | | +| UE_STATUS_RESUME | Indicates that the UE's status is resumed. Only applicable to the interworking scenario as defined in Annex B. | PolicyUpdateWhenUESuspends | +| UE_TZ_CH | UE Time Zone Change. | | +| AUTH_PROF_CH | Indicates that the DN-AAA authorization profile index has changed. (NOTE) | DN-Authorization | +| TSN_BRIDGE_INFO | Indicates the NF service consumer has detected information about new TSC user plane node port(s), and/or new/updated UMIC and/or PMIC(s). | TimeSensitiveNetworking | +| QOS_MONITORING | Indicates that the NF service consumer notifies the PCF of the QoS Monitoring information. | QosMonitoring | +| SCELL_CH | Location Change with respect to the Serving Cell. | | +| USER_LOCATION_CH | Indicates that user location has changed, applicable to serving area change and serving cell change. | AggregatedUELocChanges | +| EPS_FALLBACK | EPS Fallback report is enabled in the NF service consumer. Only applicable to the interworking scenario as defined is Annex B. | EPSFallbackReport | +| MA_PDU | Indicates that the NF service consumer notifies the PCF of the MA PDU session request. Only applicable to the interworking scenario as defined in Annex B. (NOTE) | ATSSS | +| 5G_RG_JOIN | The 5G-RG has joined to an IP Multicast Group. | WWC | +| 5G_RG_LEAVE | The 5G-RG has left an IP Multicast Group. | WWC | + +| | | | +|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| DDN_FAILURE | Indicates that the NF service consumer requests policies from PCF if it received an event subscription for DDN Failure event. | DDNEventPolicyControl | +| DDN_DELIVERY_STATUS | Indicates that the NF service consumer requests policies from PCF if it received an event subscription for DDN Delivery Status event. | DDNEventPolicyControl | +| GROUP_ID_LIST_CHG | UE Internal Group Identifier(s) has changed: the NF service consumer reports that UDM provided list of group Ids has changed. (NOTE) | GroupIdListChange | +| DDN_FAILURE_CANCELLATION | Indicates that the event subscription for DDN Failure event is cancelled. | DDNEventPolicyControl2 | +| DDN_DELIVERY_STATUS_CANCELLATION | Indicates that the event subscription for DDD STATUS is cancelled. | DDNEventPolicyControl2 | +| VPLMN_QOS_CH | Indicates that the NF service consumer has detected the change of the QoS supported in the VPLMN, the change from the case where the QoS constraints are applicable to the case where the QoS constraints are not applicable (e.g. the UE moves back from the home routed to the non-roaming scenario) or vice versa. (NOTE) | VPLMN-QoS-Control | +| SUCC_QOS_UPDATE | Indicates that the NF service consumer notifies the PCF of the successful update of the QoS for MPS. | MPSforDTS | +| SAT_CATEGORY_CHG | Indicates that the SMF has detected a change between different satellite category, or non-satellite backhaul. | SatBackhaulCategoryChg | +| PCF_UE_NOTIF_IND | Indicates the SMF has detected the AMF forwarded the PCF for the UE indication to receive/stop receiving notifications of SM Policy association established/terminated events. (NOTE) | AMInfluence | +| NWDAF_DATA_CHG | Indicates that the NWDAF instance IDs used for the PDU session and/or associated Analytics IDs have changed. (NOTE) | EneNA | +| UE_POL_CONT_IND | Indicates that the NF service consumer has received a new UE policy container from the UE in EPC over a PDN connection. Only applicable to the interworking scenario as defined in Annex B. (NOTE) | EpsUrsp | +| URSP_ENFORCEMENT_INFO | Indicates that the NF service consumer has detected a report of URSP rule enforcement information. | URSPEnforcement | +| HR_SBO_IND_CHG | Indicates the HR-SBO support indication has changed. (NOTE) | HR-SBO | +| L4S_SUPP | Indicates whether the ECN marking for L4S support is not available or available again in 5GS. | L4S | +| NET_SLICE_REPL | Indicates network slice replacement, i.e., a change between the initial S-NSSAI of the PDU Session and the Alternative S-NSSAI. (NOTE) | NetSliceRepl | +| BAT_OFFSET_INFO | Indicates that the NF service consumer has detected the information about the BAT offset and optionally adjusted periodicity. | EnTSCAC | +| NOTE: The NF service consumer always reports to the PCF. | | | + +The PCF may provision the values of policy control request trigger which are not always reported by the NF service consumer as defined in clause 4.2.6.4. + +When the NF service consumer detects the corresponding policy control request trigger(s), the NF service consumer shall report the detected trigger(s) to the PCF as defined in clause 4.2.4.1 with the additional information for different independent policy control request triggers as follows: + +If the "PLMN\_CH" is provisioned, when the NF service consumer detects a change of the serving network (a PLMN or an SNPN), the NF service consumer shall include the "PLMN\_CH" within the "repPolicyCtrlReqTriggers" attribute and the current identifier of the serving network within the "servingNetwork" attribute. + +NOTE 1: Handover between non-equivalent SNPNs, and between SNPN and PLMN is not supported. When the UE is operating in SNPN access mode, the trigger reports changes of equivalent SNPNs. + +When the NF service consumer receives the resource modification request from the UE, the NF service consumer shall include the "RES\_MO\_RE" within the "repPolicyCtrlReqTriggers" attribute and the information for requesting the PCC rule as defined in clause 4.2.4.17. + +If the "AC\_TY\_CH" is provisioned, when the NF service consumer detects a change of access type, the NF service consumer shall include the "AC\_TY\_CH" within the "repPolicyCtrlReqTriggers" attribute and the current access type + +within the "accessType" attribute. The RAT type encoded in the "ratType" attribute shall also be provided when applicable to the specific access type. Specific attributes for the EPC interworking case are described in Annex B. If the ATSSS feature is supported, when the NF service consumer detects an access is added or released for MA PDU session, the NF service consumer shall include the added Access Type or released Access type encoded as "accessType" attribute within the AdditionalAccessInfo data structure. The RAT type encoded in the "ratType" attribute shall also be provided within the AdditionalAccessInfo data structure when applicable to the added access type or released access type. + +When the NF service consumer detects an IPv4 address and/or an IPv6 prefix is allocated or released, the NF service consumer shall include the "UE\_IP\_CH" within the "repPolicyCtrlReqTriggers" attribute and new allocated UE IPv4 address within the "ipv4Address" attribute and/or the UE IPv6 prefix within the "ipv6AddressPrefix" attribute or the released UE IPv4 address within the "relIpv4Address" attribute and/or the UE IPv6 prefix within the "relIpv6AddressPrefix" attribute. If the "MultiIpv6AddrPrefix" feature is supported, and if an additional allocated or released IPv6 prefix is detected, the NF service consumer shall include the new allocated UE IPv6 prefix within the "addIpv6AddrPrefixes" attribute and the released UE IPv6 prefix within the "addRelIpv6AddrPrefixes" attribute. If the "UnlimitedMultiIpv6Prefix" feature is supported, and if multiple allocated or released IPv6 prefixes are detected, the NF service consumer shall include the new allocated UE IPv6 prefixes within the "multiIpv6Prefixes" attribute and the released UE IPv6 prefixes within the "mutliRelIpv6Prefixes" attribute. + +When the NF service consumer detects a new UE MAC address or a used UE MAC address is not used any more, the NF service consumer shall include the "UE\_MAC\_CH" within the "repPolicyCtrlReqTriggers" attribute and new detected UE MAC address within the "ueMac" attribute or the not used UE MAC address within the "relUeMac" attribute. + +If the "AN\_CH\_COR" is provisioned, when the NF service consumer is provisioned with the PCC rule as defined in clause 4.2.6.5.1, the NF service consumer shall notify the PCF of access network charging identifier associated with the PCC rules as defined in clause 4.2.4.13. + +If the "US\_RE" is provisioned, when the NF service consumer receives the usage report from the UPF, the NF service consumer shall notify the PCF of the accumulated usage as defined in clause 4.2.4.10. Applicable to functionality introduced with the UMC feature as described in clause 5.8. + +If the "APP\_STA" is provisioned, when the NF service consumer receives the application start report from the UPF, the NF service consumer shall notify the PCF of the application start report as defined in clause 4.2.4.6. Applicable to functionality introduced with the ADC feature as described in clause 5.8. + +If the "APP\_STO" is provisioned, when the NF service consumer receives the application stop report from the UPF, the NF service consumer shall notify the PCF of the application stop report as defined in clause 4.2.4.6. Applicable to functionality introduced with the ADC feature as described in clause 5.8. + +If the "AN\_INFO" is provisioned, when the NF service consumer receives the reported access network information from the access network, the NF service consumer shall notify the PCF of the access network information as defined in clause 4.2.4.9. Applicable to functionality introduced with the NetLoc feature as described in clause 5.8. + +If the "CM\_SES\_FAIL" is provisioned, when the NF service consumer receives a detected transient/permanent failure from the CHF, the NF service consumer shall include the "CM\_SES\_FAIL" within the "repPolicyCtrlReqTriggers" attribute. If the failure does not apply to all PCC Rules, the affected PCC Rules are indicated within the "ruleReports" attribute, with the "ruleStatus" attribute set to value ACTIVE and the "failureCode" attribute set to the corresponding value as reported by the CHF; otherwise if the failure applies to the session, the "creditManageStatus" shall be set to the corresponding value as reported by the CHF. + +If the "PS\_DA\_OFF" is provisioned, when the NF service consumer receives a change of 3GPP PS Data Off status from the UE, the NF service consumer shall notify the PCF as defined in clause 4.2.4.8. Applicable to functionality introduced with the 3GPP-PS-Data-Off feature as described in clause 5.8. + +When the NF service consumer detects a change of subscribed default QoS, the NF service consumer shall include the "DEF\_QOS\_CH" within the "repPolicyCtrlReqTriggers" attribute and the new subscribed default QoS within the "subsDefQos" attribute. + +When the NF service consumer detects a change of Session-AMBR, the NF service consumer shall include the "SE\_AMBR\_CH" within the "repPolicyCtrlReqTriggers" attribute and the new Session-AMBR within the "subsSessAmbr" attribute. + +If the "QOS\_NOTIF" is provisioned, when the NF service consumer receives a notification from access network that QoS targets of the QoS Flow cannot be guaranteed or can be guaranteed again, the NF service consumer shall send the notification as defined in clause 4.2.4.20. + +If the "NO\_CREDIT" is provisioned, when the NF service consumer detects the credit for the PCC rule(s) is no longer available, the NF service consumer shall include the "NO\_CREDIT" within the "repPolicyCtrlReqTriggers" attribute, the termination action the NF service consumer applies to the PCC rules as instructed by the CHF within the "finUnitAct" attribute and the affected PCC rules within the "ruleReports" attribute. + +When the "ReallocationOfCredit" feature is supported, if the "REALLO\_OF\_CREDIT" is provisioned, when the NF service consumer detects the credit for the PCC rule(s) is reallocated, the NF service consumer shall include the "REALLO\_OF\_CREDIT" within the "repPolicyCtrlReqTriggers" attribute and include the affected PCC rules for which credit has been reallocated after credit was no longer available and the "ruleStatus" attribute set to value ACTIVE within the "ruleReports" attribute. + +If the "PRA\_CH" is provisioned, to detect when the UE enters/leaves certain presence reporting areas, the NF service consumer is provisioned the presence reporting area information as defined in clause 4.2.6.5.6. When the NF service consumer receives the presence reporting area information from the serving node, the NF service consumer shall notify the PCF of the reported presence area information as defined in clause 4.2.4.16. This report includes reporting the initial status at the time the request for reports is initiated. Applicable to the functionality introduced by the PRA or ePRA feature as described in clause 5.8. + +If the "SAREA\_CH" is provisioned, when the NF service consumer detects a change of serving area (i.e. tracking area, or if the feature "2G3GIWK" is supported routing area), the NF service consumer shall include the "SAREA\_CH" within the "repPolicyCtrlReqTriggers" attribute and the current TAI within the "userLocationInfo" attribute in either the "eutraLocation" or "nrLocation", or the current Routing Area within the "userLocationInfo" attribute in the "utraLocation" attribute when UTRAN access, or in the "geraLocation" attribute when GERAN access, as applicable. Non-3GPP access user location is reported in the "n3gaLocation" attribute when applicable. The attributes used in case of EPC interworking are described in Annex B. + +If the "SCNN\_CH" is provisioned, when the NF service consumer detects a change of serving Network Function (i.e. the AMF, ePDG, S-GW or if the feature "2G3GIWK" is supported SGSN), the NF service consumer shall include the "SCNN\_CH" within the "repPolicyCtrlReqTriggers" attribute and the current serving Network Function in the "servNfId" attribute if available. When the serving Network Function is an AMF, the NF service consumer shall include the AMF Network Function Instance Identifier within the "servNfInstId" attribute and the Globally Unique AMF Identifier within the "guami" attribute. The attributes included in case of EPC interworking are described in Annex B. + +NOTE 1: In the home-routed roaming case, if the AMF change is unknown to the H-SMF, then the AMF change is not reported. + +If the "RE\_TIMEOUT" is provisioned, when the NF service consumer is provisioned with the revalidation time by the PCF, the NF service consumer shall request the policy before the indicated revalidation time is reached as defined in clause 4.2.4.3. + +If the "RES\_RELEASE" is provisioned, when the NF service consumer receives the request of PCC rule removal as defined in clause 4.2.6.5.2, the NF service consumer shall report the outcome of resource release as defined in clause 4.2.4.12. Applicable to functionality introduced with the RAN-NAS-Cause feature as described in clause 5.8. + +When "SUCC\_RES\_ALLO" is provisioned and PCC rules are provisioned according to clause 4.2.6.5.5, the NF service consumer shall inform the PCF of the successful resource allocation as defined in clause 4.2.4.14. + +If the feature "2G3GIWK" is supported, and if the "RAI\_CH" is provisioned, when the NF service consumer detects a change of routing area, the NF service consumer shall include the "RAI\_CH" within the "repPolicyCtrlReqTriggers" attribute and the current RAI within the "userLocationInfo" attribute as described in Annex B. + +If the "RAT TY\_CH" is provisioned, when the NF service consumer detects a change of the RAT type, the NF service consumer shall include the "RAT TY\_CH" within the "repPolicyCtrlReqTriggers" attribute and the current RAT type within the "ratType" attribute. For MA PDU session, the NF service consumer shall include the current RAT type at the SmPolicyUpdateContextData data type level or AdditionalAccessInfo data type level. If the RAT type is provided at the SmPolicyUpdateContextData data type level, the NF service consumer shall also provide the associated access type within the SmPolicyUpdateContextData data structure. + +If the "REF\_QOS\_IND\_CH" is provisioned, when the NF service consumer receives a change of reflective QoS indication from the UE, the NF service consumer shall include the "REF\_QOS\_IND\_CH" within the "repPolicyCtrlReqTriggers" attribute and the indication within the "refQosIndication" attribute. + +When the NF service consumer receives the number of supported packet filter for signalled QoS rules for the PDU session from the UE during the PDU Session Modification procedure after the first inter-system change from EPS to 5GS for a PDU Session established in EPS and transferred from EPS with N26 interface, the NF service consumer shall include the "NUM\_OF\_PACKET\_FILTER" within the "repPolicyCtrlReqTriggers" attribute and the number of supported packet filter for signalled QoS rules within the "numOfPackFilter" attribute. Only applicable to the interworking scenario as defined in Annex B. + +If the "UE\_STATUS\_RESUME" is provisioned, when the NF service consumer detected the UE's status is resumed from suspend state, the NF service consumer shall inform the PCF of the UE status including the "UE\_STATUS\_RESUME" within "repPolicyCtrlReqTriggers" attribute. The PCF shall after this update the NF service consumer with PCC Rules or session rules if necessary. Applicable to functionality introduced with the PolicyUpdateWhenUESuspends feature as described in clause 5.8. + +If the "UE\_TZ\_CH" is provisioned, when the NF service consumer detects a change of the UE Time Zone, the NF service consumer shall include the "UE\_TZ\_CH" within the "repPolicyCtrlReqTriggers" attribute and the current UE Time Zone within the "ueTimeZone" attribute. + +If the "DN-Authorization" feature is supported, when the NF service consumer detects a change of DN-AAA authorization profile index, the NF service consumer shall include the "AUTH\_PROF\_CH" within the "repPolicyCtrlReqTriggers" attribute and the new DN-AAA authorization profile index within the "authProfIndex" attribute. + +If the "TimeSensitiveNetworking" or "TimeSensitiveCommunication" feature is supported and "TSN\_BRIDGE\_INFO" is provisioned, when the NF service consumer detects: + +- there is information about new TSC user plane node port(s), e.g. a new manageable Ethernet port, the NF service consumer shall include the "TSN\_BRIDGE\_INFO" within the "repPolicyCtrlReqTriggers" attribute and the updated TSC user plane node information within the "tsnBridgeInfo" attribute; and/or +- the NF service consumer detects a UMIC or PMIC, the NF service consumer shall include the "TSN\_BRIDGE\_INFO" within the "repPolicyCtrlReqTriggers" attribute and the UMIC, if available, within the "tsnBridgeManCont" attribute, and/or the PMIC(s), if available, within the "tsnPortManContDstt" and the "tsnPortManContNwts" attributes. + +NOTE 2: When the NF service consumer detects updated Port Management Information of the NW-TT ports, the NF service consumer includes the PMIC within the "tsnPortManContNwts" attribute of SmPolicyUpdateContextData data type. + +If the "QoSMonitoring" feature and/or the "EnQoSMon" is supported and if the "QOS\_MONITORING" is provisioned, upon receiving the QoS Monitoring report from the UPF, the NF service consumer shall send the QoS monitoring report(s) for the concerned PCC rules to the PCF as defined in clause 4.2.4.24. + +If the "SCELL\_CH" is provisioned, when the NF service consumer detects a change of serving cell, the NF service consumer shall include the "SCELL\_CH" within the "repPolicyCtrlReqTriggers" attribute and the current cell Id within the "userLocationInfo" attribute either in the "eutraLocation" attribute when EPC/E-UTRAN access or "nrLocation" attribute when NR access or "geraLocation" attribute when GERAN access or "utraLocation" attribute when UTRAN access, as applicable. + +NOTE 3: Location change of serving cell can increase signalling load on multiple interfaces. Hence, it is recommended that any such serving cell changes event trigger subscription is only applied for a limited number of subscribers. + +If the "AggregatedUELocChanges" feature is supported and the "USER\_LOCATION\_CH" is provisioned, when the NF service consumer detects a change of serving cell and/or a change of serving area (i.e. tracking area), the NF service consumer shall include the "USER\_LOCATION\_CH" within the "repPolicyCtrlReqTriggers" attribute and the current serving area and/or cell Id within the "userLocationInfo" attribute in the "eutraLocation" attribute or "nrLocation" attribute or "geraLocation" attribute or "utraLocation" attribute, as applicable. + +NOTE 4: The access network can be configured to report location changes only when transmission resources are established in the radio access network. + +If the "EPSFallbackReport" feature is supported and the "EPS\_FALLBACK" is provisioned and there is a PCC rule installed that required the reporting, when the NF service consumer receives a PDU session modification response indicating the rejection of the establishment of the QoS flow with 5QI=1, the NF service consumer shall notify the PCF of EPS fallback as defined in clause B.3.4.6. + +When the NF service consumer receives the MA PDU Request Indication or MA PDU Network-Upgrade Allowed Indication and ATSSS Capability from the UE during the PDU Session Modification procedure after the first inter-system change from EPS to 5GS for a PDU Session established in EPS and transferred from EPS with N26 interface, the NF service consumer shall include the "MA\_PDU" within the "repPolicyCtrlReqTriggers" attribute, the MA PDU session Indication in the "maPduInd" attribute, the ATSSS capability of the MA PDU session within the "atsssCapab" attribute. Only applicable to the interworking scenario as defined in Annex B. + +If the "WWC" feature is supported and "5G\_RG\_JOIN" is provisioned and when the NF service consumer detects a 5G-RG has joined to an IP Multicast Group, the NF service consumer shall include the "5G\_RG\_JOIN" within the "repPolicyCtrlReqTriggers" attribute and the IP multicast addressing information within the "mulAddrInfos" attribute. + +If the "WWC" feature is supported and "5G\_RG\_LEAVE" is provisioned and when the NF service consumer detects a 5G-RG has left an IP Multicast Group, the NF service consumer shall include the "5G\_RG\_LEAVE" within the "repPolicyCtrlReqTriggers" attribute and the IP multicast addressing information within the "mulAddrInfos" attribute. + +If "DDNEventPolicyControl" feature is supported, and if "DDN\_FAILURE" is provisioned, when the NF service consumer receives an event subscription for DDN Failure event including the traffic descriptors, the NF service consumer shall include the "DDN\_FAILURE" within the "repPolicyCtrlReqTriggers" attribute and traffic descriptor(s) within the "trafficDescriptors" attribute. + +If "DDNEventPolicyControl" feature is supported, and if "DDN\_DELIVERY\_STATUS" is provisioned, when the NF service consumer receives an event subscription for DDD Status event including the traffic descriptors, the NF service consumer shall include the "DDN\_DELIVERY\_STATUS" within the "repPolicyCtrlReqTriggers" attribute and traffic descriptor(s) within the "trafficDescriptors" attribute and the requested type(s) of notifications (notifications about downlink packets being buffered, and/or discarded). + +If "GroupIdListChange" feature is supported, when the SMF receives the updated Internal Group Identifier(s) from the UDM, the SMF shall include the "GROUP\_ID\_LIST\_CHG" within the "repPolicyCtrlReqTriggers" attribute and the Internal Group Identifier(s) of the served UE within the "interGrpIds" attribute. + +If "DDNEventPolicyControl2" feature is supported, and if "DDN\_FAILURE\_CANCELLATION" is provisioned, when the SMF receives a cancellation of event subscription for DDN Failure event, the SMF shall include the "DDN\_FAILURE\_CANCELLATION" within the "repPolicyCtrlReqTriggers" attribute and the PCC rule identifier of the PCC rule which is used for traffic detection of DDN failure event within the "pccRuleId" attribute. + +If "DDNEventPolicyControl2" feature is supported, and if "DDN\_DELIVERY\_STATUS\_CANCELLATION" is provisioned, when the SMF receives a cancellation of event subscription for DDD Status event, the SMF shall include the "DDN\_DELIVERY\_STATUS\_CANCELLATION" within the "repPolicyCtrlReqTriggers" attribute and the PCC rule identifier of the PCC rule which is used for traffic detection of DDD status event within the "pccRuleId" attribute. + +When the "VPLMN-QoS-Control" feature is supported and if the NF service consumer receives a new QoS value supported in the VPLMN, the NF service consumer shall include the "VPLMN\_QOS\_CH" within the "repPolicyCtrlReqTriggers" attribute and the received QoS constraints within the "vplmnQos" attribute; if the NF service consumer detects that the UE moves from a VPLMN with QoS constraints to the HPLMN or to a VPLMN without QoS constraints, the NF service consumer shall include the "VPLMN\_QOS\_CH" within the "repPolicyCtrlReqTriggers" attribute and the "vplmnQosNotApp" attribute set to true. + +If the "MPSforDTS" feature is supported, and if "SUCC\_QOS\_UPDATE" is provisioned, when the resources for the MPS for DTS invocation/revocation are successfully allocated for MPS for DTS, the NF service consumer shall include the "SUCC\_QOS\_UPDATE" within the "repPolicyCtrlReqTriggers" attribute. + +If "SatBackhaulCategoryChg" is supported, and if "SAT\_CATEGORY\_CHG" is provisioned, the NF service consumer notifies the PCF when there is a change of the backhaul which is used for the PDU session between different satellite backhaul categories or between a satellite backhaul and a non-satellite backhaul. When the "EnSatBackhaulCatChg" feature is supported, the different dynamic satellite backhaul categories may also be reported. The NF service consumer shall include the satellite backhaul category or dynamic satellite backhaul category or non-satellite backhaul within the "satBackhaulCategory" attribute together with the "SAT\_CATEGORY\_CHG" policy control request trigger within the "repPolicyCtrlReqTriggers" attribute. + +NOTE 5: Only a single backhaul category can be indicated. + +If the "AMInfluence" feature is supported, the NF service consumer notifies the PCF about the PCF for the UE request to be notified of PDU session established/terminated events and if applicable, about the PCF for the UE binding information in the initial reporting and when the PCF for the UE changes by forwarding within the "pcfUeInfo" attribute, the received PCF for the UE callback URI within the "callbackUri" attribute and, if received, SBA binding information within the "bindingInfo" attribute, together with the "PCF\_UE\_NOTIF\_IND" policy control request trigger within the "repPolicyCtrlReqTriggers" attribute. The NF service consumer notifies the PCF about the PCF for the UE request to stop being notified about the PDU session established/terminated events by sending the "pcfUeInfo" attribute set to NULL together with the "PCF\_UE\_NOTIF\_IND" policy control request trigger within the "repPolicyCtrlReqTriggers" attribute. + +If "EneNA" feature is supported, the NF service consumer notifies the PCF when there is a change in the list of NWDAF Instance IDs used for the PDU Session and/or associated Analytics IDs. The NF service consumer shall include within the "nwdafDatas" attribute the list of NWDAF instance IDs used for the PDU Session within the "nwdafInstanceId" attribute and their associated Analytic ID(s) within the "nwdafEvents" attribute, and the "NWDAF\_DATA\_CHG" within the "repPolicyCtrlReqTriggers" attribute. + +If the "EpsUrsp" feature is supported, when the NF service consumer receives a new UE policy container from the UE in EPC over a PDN connection, the NF service consumer shall include the "UE\_POL\_CONT\_IND" within the "repPolicyCtrlReqTriggers" attribute and the received UE policy container within the "uePolCont" attribute. Only applicable to the interworking scenario as defined in Annex B. + +If the "URSPEnforcement" feature is supported and "URSP\_ENFORCEMENT\_INFO" is provisioned, when the NF service consumer detects the UE includes URSP enforcement information in the PDU session modification request, the NF service consumer shall include the "URSP\_ENFORCEMENT\_INFO" within the "repPolicyCtrlReqTriggers" attribute and shall forward the received information from the UE within the "urspEnfInfo" attribute. In this case, the NF service consumer shall also include, if they were not previously provided, the SSC mode within the "sscMode" attribute, the UE requested DNN (if available and different from the selected DNN) within the "ueReqDnn" attribute, and if the PDU session is redundant, the RSN and the PDU session pair ID within the "redundantPduSessionInfo" attribute. The NF service consumer shall also include the access type within the "accessType" attribute, if changed compared with the latest provided value. + +If "HR-SBO" feature is supported, the NF service consumer notifies the PCF when the HR-SBO support indication has changed. The NF service consumer shall include the "hrsboInd" attribute and set it to "true" if the HR-SBO is supported, otherwise set it to "false", and the "HR\_SBO\_IND\_CHG" within the "repPolicyCtrlReqTriggers" attribute. + +When the "L4S" feature is supported and the "L4S\_SUPP" is provisioned, when the PCC rules are provisioned with the explicit indication of ECN marking for L4S according to clause 4.2.6.21.3, the NF service consumer shall inform the PCF of the unavailability or availability again in 5GS for ECN marking for L4S support as defined in clause 4.2.6.2.21. + +If "NetSliceRepl" feature is supported, the NF service consumer notifies the PCF about network slice replacement, i.e., when there is a change between the initial S-NSSAI of the PDU Session and the Alternative S-NSSAI by including the "NET\_SLICE\_REPL" PCRT within the "repPolicyCtrlReqTriggers" attribute. When the NF service consumer reports a change from the initial S-NSSAI of the PDU Session to the Alternative S-NSSAI, it shall additionally include the Alternative S-NSSAI within the "sliceInfo" attribute. + +**Editor's Note:** Whether the initial S-NSSAI is provided to the PCF when the NF service consumer reports a change from the Alternative S-NSSAI to the initial S-NSSAI of the PDU Session via the "NET\_SLICE\_REPL" PCRT is FFS and pending stage 2 feedback. + +If "EnTSCAC" feature is supported, and if "BAT\_OFFSET\_INFO" is provisioned, when the SMF receives the notification on BAT offset and optionally adjusted periodicity, the SMF shall include the "BAT\_OFFSET\_INFO" within the "repPolicyCtrlReqTriggers" attribute and the BAT offset and optionally adjusted periodicity within the "batOffsetInfo" attribute. + +**Editor's Note:** It is FFS how the bat offset is indicated and reported per PCC rule. + +### 5.6.3.7 Enumeration: RequestedRuleDataType + +**Table 5.6.3.7-1: Enumeration RequestedRuleDataType** + +| Enumeration value | Description | Applicability | +|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| CH_ID | Indicates that the requested rule data is the charging identifier. | | +| MS_TIME_ZONE | Indicates that the requested access network info type is the UE's timezone. (NOTE) | | +| USER_LOC_INFO | Indicates that the requested access network info type is the UE's location. (NOTE) | | +| RES_RELEASE | Indicates that the requested rule data is the result of the release of resource. | | +| SUCC_RES_ALLO | Indicates that the requested rule data is the successful resource allocation. | | +| EPS_FALLBACK | Indicates that the requested rule data is the report of QoS flow rejection due to EPS fallback. | EPSFallbackReport | +| NOTE: The requested rule data shall also be reported at QoS flow termination and PDU session termination. | | | + +### 5.6.3.8 Enumeration: RuleStatus + +**Table 5.6.3.8-1: Enumeration RuleStatus** + +| Enumeration value | Description | Applicability | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| ACTIVE | Indicates that the PCC rule(s) are successfully installed (for those provisioned from the PCF) or activated (for those pre-defined in the SMF), or that the session rule(s) are successfully installed. | | +| INACTIVE | Indicates that the PCC rule(s) are removed (for those provisioned from the PCF) or inactive (for those pre-defined in the SMF) or that the session rule(s) are removed. | | + +### 5.6.3.9 Enumeration: FailureCode + +**Table 5.6.3.9-1: Enumeration FailureCode** + +| Enumeration value | Description | Applicability | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| UNK_RULE_ID | Indicates that the pre-provisioned PCC rule could not be successfully activated because the provided PCC rule identifier is unknown to the NF service consumer. | | +| RA_GR_ERR | Indicates that the PCC rule could not be successfully installed or enforced because the Rating Group specified within the Charging Data policy decision to which the PCC rule refers is unknown or invalid. | | +| SER_ID_ERR | Indicates that the PCC rule could not be successfully installed or enforced because the Service Identifier specified within the Charging Data policy decision to which the PCC rule refers is invalid, unknown or not applicable to the service being charged. | | +| NF_MAL | Indicates that the PCC rule could not be successfully installed (for those provisioned from the PCF), activated (for those pre-defined in the SMF) or enforced (for those already successfully installed) due to SMF/UPF malfunction. | | +| RES_LIM | Indicates that the PCC rule could not be successfully installed (for those provisioned from the PCF), activated (for those pre-defined in the SMF) or enforced (for those already successfully installed) due to a limitation of resources at the SMF/UPF. | | +| MAX_NR_QoS_FLOW
(NOTE) | Indicates that the PCC rule could not be successfully installed (for those provisioned from the PCF), activated (for those pre-defined in the SMF) or enforced (for those already successfully installed) due to the fact that the maximum number of QoS flows has been reached for the associated PDU session. | | +| MISS_FLOW_INFO | Indicates that the PCC rule could not be successfully installed (for those provisioned from the PCF) or enforced (for those already successfully installed) because neither the "flowInfos" attribute nor the "appld" attribute is specified by the PCF within the PCC rule entry of the "pccRules" attribute during the first PCC rule installation request. | | +| RES_ALLO_FAIL | Indicates that the PCC rule could not be successfully installed or maintained since the associated QoS flow establishment/modification failed or the associated QoS flow was released. | | +| UNSUCC_QOS_VAL | This value is used to:
- indicate that QoS validation has failed; or
- indicate when Guaranteed Bandwidth > Max-Requested-Bandwidth. | | +| INCOR_FLOW_INFO | Indicates that the PCC rule could not be successfully installed or modified at the NF service consumer because the provided flow information is not supported by the network (e.g. the provided IP address(es) or IPv6 prefix(es) do not correspond to an IP version applicable for the PDU session). | | +| PS_TO_CS_HAN | Indicates that the PCC rule could not be maintained because of PS to CS handover. | | +| APP_ID_ERR | Indicates that the PCC rule could not be successfully installed or enforced because the Application Identifier is invalid, unknown, or not applicable to the application required for detection. | ADC | +| NO_QOS_FLOW_BOUND | Indicates that there is no QoS flow to which the SMF can bind the PCC rule. | | +| FILTER_RES | Indicates that the Flow Information within the "flowinfos" attribute cannot be handled by the NF service consumer because at least one of the restrictions defined in clause 5.4.2 of 3GPP TS 29.212 [23] was not respected. | | +| MISS_REDI_SER_ADDR | Indicates that the PCC rule could not be successfully installed or enforced at the NF service consumer because there is no valid Redirect Server Address within the provided Traffic Control Data policy decision to which the PCC rule refers, and no preconfigured redirection address for this PCC rule at the SMF/UPF. | ADC | +| UE_TEMPORARILY_UNAVAILABLE | Indicates that the PCC rule could not be successfully installed/modified because the SMF was informed that the UE was not reachable. | UEUnreachable | +| CM_END_USER_SER_DENIED | Indicates that the charging system denied the service request due to service restrictions (e.g. terminate rating group) or limitations related to the end-user, e.g. the end-user's account could not cover the requested service. | | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| CM_CREDIT_CON_NOT_APP | Indicates that the charging system determined that the service can be granted to the end user but no further credit control is needed for the service (e.g. service is free of charge or is treated via offline charging). | | +| CM_AUTH_REJ | Indicates that the charging system denied the service request in order to terminate the service for which credit is requested. | | +| CM_USER_UNK | Indicates that the specified end user could not be found in the charging system. | | +| CM_RAT_FAILED | Indicates that the charging system cannot rate the service request due to insufficient rating inputs, incorrect combination of inputs or due to an attribute or an attribute value that is not recognized or supported in the rating. | | +| UE_STA_SUSP | Indicates that the UE is in suspend state. Only applicable to the interworking scenario, as defined in Annex B. | PolicyUpdateWhenUESuspends | +| UNKNOWN_REF_ID | Indicates that the PCC rule could not be successfully installed/modified because the referenced identifier to a Policy Decision Data or to a Condition Data is unknown to the NF service consumer. | | +| INCORRECT_COND_DATA | Indicates that the PCC rule could not be successfully installed/modified because the referenced Condition data are incorrect (e.g. the "deactivationTime" and the "activationTime" included in the referenced ConditionData contain the same time value). | | +| REF_ID_COLLISION | Indicates that the PCC rule could not be successfully installed/modified because a Policy Decision referenced within the PCC rule is also referenced by a session rule (e.g. a session rule and this PCC rule refer to the same Usage Monitoring decision data). | | +| TRAFFIC_STEERING_ERROR | This value is used to indicate that:
- the enforcement of the steering of traffic to the N6-LAN or 5G-LAN failed; or
- the dynamic PCC rule could not be successfully installed/modified at the NF service consumer because e.g. there are invalid traffic steering policy identifier(s) within the provided Traffic Control Data policy decision to which the PCC rule refers.
Applicable when the functionality introduced with the TSC feature described in clause 5.8 applies. | | +| DNAI_STEERING_ERROR | This value is used to indicate that:
- the enforcement of the steering of traffic to the indicated DNAI failed; or
- the dynamic PCC rule could not be successfully installed/modified at the NF service consumer because there is invalid route information for a DNAI(s) (e.g. routing profile id is not configured) within the provided Traffic Control Data policy decision to which the PCC rule refers.
Applicable when the functionality introduced with the TSC feature described in clause 5.8 applies. | | +| AN_GW_FAILED | Indicates that the AN-Gateway has failed and that the PCF should refrain from sending policy decisions to the SMF until it is informed that the S-GW has been recovered. This value shall not be used if the SM Policy association modification procedure is initiated for session rule removal only. | SGWRest | +| MAX_NR_PACKET_FILTERS_EXCEEDED | This value is used to indicate that the PCC rule could not be successfully installed, modified or enforced at the NF service consumer because the number of supported packet filters for signalled QoS rules for the PDU session has been reached. | | +| PACKET_FILTER_TFT_ALLOCATION_EXCEEDED | Indicates that the PCC rule is removed at 5GS to EPS mobility because TFT allocation was not possible since the number of active packet filters in the EPC bearer is exceeded. | PackFiltAllocPrecedence | +| MUTE_CHG_NOT_ALLO_WED | Indicates that the PCC rule could not be successfully modified because the mute condition for application detection report cannot be changed.
Applicable when the functionality introduced with the ADC feature described in clause 5.8 applies. | | +| NOTE: The enumeration value does not follow the related naming convention (i.e. "UPPER_WITH_UNDERSCORE") defined in clause 5.1.4 of 3GPP TS 29.501 [6]. This enumeration value is however kept as currently defined in this specification for backward compatibility considerations. | | | + +## 5.6.3.10 Enumeration: AfSigProtocol + +Table 5.6.3.10-1: Enumeration AfSigProtocol + +| Enumeration value | Description | Applicability | +|-------------------|-------------------------------------------------------------------------------------------------------------|------------------| +| NO_INFORMATION | Indicate that no information about the AF signalling protocol is being provided. This is the default value. | ProvAFsignalFlow | +| SIP | Indicate that the signalling protocol is Session Initiation Protocol. | ProvAFsignalFlow | + +## 5.6.3.11 Enumeration: RuleOperation + +Table 5.6.3.11-1: Enumeration RuleOperation + +| Enumeration value | Description | Applicability | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|---------------| +| CREATE_PCC_RULE | Indicates to create a new PCC rule to reserve the resource requested by the UE. | | +| DELETE_PCC_RULE | Indicates to delete a PCC rule corresponding to reserve the resource requested by the UE. | | +| MODIFY_PCC_RULE_AND_ADD_PACKET_FILTERS | Indicates to modify the PCC rule by adding new packet filter(s). | | +| MODIFY_PCC_RULE_AND_REPLACE_PACKET_FILTERS (NOTE) | Indicates to modify the PCC rule by replacing the existing packet filter(s). | | +| MODIFY_PCC_RULE_AND_DELETE_PACKET_FILTERS (NOTE) | Indicates to modify the PCC rule by deleting the existing packet filter(s). | | +| MODIFY_PCC_RULE_WITHOUT_MODIFY_PACKET_FILTERS | Indicates to modify the PCC rule by modifying the QoS of the PCC rule. | | +| NOTE: The enumeration value does not follow the related naming convention (i.e. "UPPER_WITH_UNDERSCORE") defined in clause 5.1.4 of 3GPP TS 29.501 [5]. There is a space between the "MODIFY_" part and the "PCC" part. This enumeration value is however kept as currently defined in this specification for backward compatibility considerations. | | | + +## 5.6.3.12 Enumeration: RedirectAddressType + +Table 5.6.3.12-1: Enumeration RedirectAddressType + +| Enumeration value | Description | Applicability | +|-------------------|------------------------------------------------------------------------------------|---------------| +| IPv4_ADDR | Indicates that the address type is in the form of "dotted-decimal" IPv4 address. | | +| IPv6_ADDR | Indicates that the address type is in the form of IPv6 address. | | +| URL | Indicates that the address type is in the form of Uniform Resource Locator. | | +| SIP_URI | Indicates that the address type is in the form of SIP Uniform Resource Identifier. | | + +## 5.6.3.13 Enumeration: QosFlowUsage + +Table 5.6.3.13-1: Enumeration QosFlowUsage + +| Enumeration value | Description | Applicability | +|-------------------|----------------------------------------------------------------|---------------| +| GENERAL | Indicates no specific QoS flow usage information is available. | | +| IMS_SIG | Indicates that the QoS flow is used for IMS signalling only. | | + +### 5.6.3.14 Enumeration: FailureCause + +**Table 5.6.3.14-1: Enumeration FailureCause** + +| Enumeration value | Description | Applicability | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| PCC_RULE_EVENT | Some of the PCC rules provisioned by the PCF in the request cannot be installed/activated. It is used to inform the PCF that the request failed and should not be attempted again. | | +| PCC_QOS_FLOW_EVENT | For some reason some of the PCC rules provisioned by the PCF in the request cannot be enforced or modified successfully in a network initiated procedure. It is used to inform the PCF that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. | | +| RULE_PERMANENT_ERR
OR | The HTTP request is rejected because some of the PCC and/or session rules provisioned by the PCF in the request cannot be installed/activated. It is used to inform the PCF that the request failed, and should not be attempted again. | SessionRuleError
Handling | +| RULE_TEMPORARY_ERR
OR | The HTTP request is rejected because for some reason some of the PCC and/or session rules provisioned by the PCF in the request cannot be enforced or modified successfully in a network initiated procedure. It is used to inform the PCF that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. | SessionRuleError
Handling | +| POL_DEC_ERROR | Some of the policy decisions (including data that is different than PCC/session rule related data) provided by the PCF in the request cannot be provisioned in the NF service consumer. | PolicyDecisionErr
orHandling | + +### 5.6.3.15 Enumeration: FlowDirectionRm + +This data type is defined in the same way as the "FlowDirection" data type, but also allows null value (specified as "NullValue" data type). + +### 5.6.3.16 Enumeration: CreditManagementStatus + +**Table 5.6.3.16-1: Enumeration CreditManagementStatus** + +| Enumeration value | Description | Applicability | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| END_USER_SER_DENIED | Indicates that the charging system denied the service request due to service restrictions (e.g. terminate rating group) or limitations related to the end-user, for example the end-user's account could not cover the requested service. | | +| CREDIT_CTRL_NOT_APP | Indicates that the charging system determined that the service can be granted to the end user but no further credit control is needed for the service (e.g. service is free of charge or is treated for offline charging). | | +| AUTH_REJECTED | Indicates that the charging system denied the service request in order to terminate the service for which credit is requested. | | +| USER_UNKNOWN | Indicates that the specified end user could not be found in the charging system. | | +| RATING_FAILED | Indicates that the charging system cannot rate the service request due to insufficient rating input, incorrect attribute combination or an attribute value that is not recognized or supported in rating. | | + +### 5.6.3.17 Enumeration: SessionRuleFailureCode + +**Table 5.6.3.17-1: Enumeration SessionRuleFailureCode** + +| Enumeration value | Description | Applicability | +|----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| NF_MAL | Indicates that the session rule could not be successfully installed) or enforced (for those already successfully installed) due to SMF/UPF malfunction. | | +| RES_LIM | Indicates that the session rule could not be successfully installed or enforced (for those already successfully installed) due to a limitation of resources at the SMF/UPF. | | +| SESSION_RESOURCE_ALLOCATION_FAILURE | Indicates the session rule could not be successfully enforced due to failure during the allocation of resources for the PDU session in the UE, RAN or AMF. | | +| UNSUCC_QOS_VAL | Indicates that the QoS validation has failed. | | +| INCORRECT_UM | The usage monitoring data of the enforced session rule is not the same for all the provisioned session rule(s), i.e., the reference identifier to a UsageMonitoringData policy decision is not homogeneously provisioned in all session rules (e.g., some, but not all, session rules contain usage monitoring data, or all session rules contain usage monitoring data, but with different monitoring key). | (NOTE) | +| UE_STA_SUSP | Indicates that the UE is in suspend state. Only applicable to the interworking scenario as defined in Annex B. | PolicyUpdateWhenUESuspends | +| UNKNOWN_REF_ID | Indicates that the session rule could not be successfully installed/modified because the reference identifier to a Policy Decision Data or to a Condition Data is unknown to the NF service consumer. | | +| INCORRECT_COND_DATA | Indicates that the session rule could not be successfully installed/modified because the referenced Condition data are incorrect (e.g. the ConditionData instance contains a "deactivationTime" attribute, or the "ratType" attribute value in a ConditionData instance indicates a RAT type (e.g. "NR") that is not specified for the the "accessType" attribute indicated value (e.g. "NON_3GPP_ACCESS"). | | +| REF_ID_COLLISION | Indicates that the session rule could not be successfully installed/modified because the same Policy Decision is referenced by a PCC rule (e.g. the session rule and the PCC rule refer to the same Usage Monitoring decision data). | | +| DEFAULT_QOS_MODIFICATION_FAILURE | Indicates that the enforcement of the default QoS modification failed.
The SMF shall use this value during the session rule error report specified in clause 4.2.4.21 to indicate to the PCF that the PDU session modification failed because the default QoS modification procedure as specified in clauses 4.2.3.6 and 4.2.4.5 has failed. | SessQoSModEnforcementFailure | +| SESSION_AMBR_MODIFICATION_FAILURE | Indicates that the enforcement of the session-AMBR modification failed.
The SMF shall use this value during the session rule error report specified in clause 4.2.4.21 to indicate to the PCF that the PDU session modification failed because the session-AMBR modification procedure as specified in clauses 4.2.3.5 and 4.2.4.4 has failed. | SessQoSModEnforcementFailure | +| NOTE: The "INCORRECT_UM" value shall only be used when the feature "UMC" is supported. | | | + +### 5.6.3.18 Enumeration: SteeringFunctionality + +**Table 5.6.3.18-1: Enumeration SteeringFunctionality** + +| Enumeration value | Description | Applicability | +|-------------------|----------------------------------------------------------------------------------------------------------------|---------------| +| MPTCP | Indicates that PCF authorizes the MPTCP functionality to support traffic steering, switching and splitting. | ATSSS | +| MPQUIC | Indicates that PCF authorizes the MPQUIC functionality to support traffic steering, switching and splitting. | EnATSSS_v2 | +| ATSSS_LL | Indicates that PCF authorizes the ATSSS-LL functionality to support traffic steering, switching and splitting. | ATSSS | + +### 5.6.3.19 Enumeration: SteerModeValue + +**Table 5.6.3.19-1: Enumeration SteerModeValue** + +| Enumeration value | Description | Applicability | +|--------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| ACTIVE_STANDBY | Indicates the steering mode is Active-Standy. It is used to steer a SDF on one access (the Active access), when this access is available, and to switch the SDF to the other access (the Standby access), when Active access becomes unavailable. | ATSSS | +| LOAD_BALANCING | Indicates the traffic of an SDF is split percentually across accesses. | ATSSS | +| SMALLEST_DELAY | Indicates the traffic of a SDF is steered and/or switch to the access with the smallest delay. | ATSSS | +| PRIORITY_BASED | Indicates all the traffic of an SDF is steered to the high priority access, until this access is determined to be congested. | ATSSS | +| REDUNDANT | Indicates that the traffic of an SDF may be duplicated on the 3GPP and Non-3GPP accesses. | EnATSSS_v2 | +| NOTE: When the steering mode "REDUNDANT" is provided, the steering functionality "ATSSS_LL" shall not be provided. | | | + +### 5.6.3.20 Enumeration: MulticastAccessControl + +**Table 5.6.3.20-1: Enumeration MulticastAccessControl** + +| Enumeration value | Description | Applicability | +|-------------------|--------------------------------------------------------------------------------------------------------------------------|---------------| +| ALLOWED | Indicates the service data flow, corresponding to the service data flow template, is allowed. | WWC | +| NOT_ALLOWED | Indicates the service data flow, corresponding to the service data flow template, is not allowed. This is default value. | WWC | + +### 5.6.3.21 Enumeration RequestedQosMonitoringParameter + +**Table 5.6.3.21-1: Enumeration RequestedQosMonitoringParameter** + +| Enumeration value | Description | Applicability | +|---------------------|-----------------------------------------------------------------------------------------------------------|---------------| +| DOWNLINK | Indicates the DL packet delay between the UE and the UPF is to be monitored. | | +| UPLINK | Indicates the UL packet delay between the UE and the UPF is to be monitored. | | +| ROUND_TRIP | Indicates the round trip packet delay between the UE and the UPF is to be monitored. | | +| DOWNLINK_DATA_RATE | Indicates the DL data rate is to be monitored. | EnQoSMon | +| UPLINK_DATA_RATE | Indicates the UL data rate is to be monitored. | EnQoSMon | +| DOWNLINK_CONGESTION | Indicates that the percentage of DL packets to be marked as congested is to be monitored for the DL flow. | EnQoSMon | +| UPLINK_CONGESTION | Indicates that the percentage of DL packets to be marked as congested is to be monitored for the UL flow. | EnQoSMon | + +### 5.6.3.22 Enumeration: ReportingFrequency + +**Table 5.6.3.22-1: Enumeration ReportingFrequency** + +| Enumeration value | Description | Applicability | +|-------------------|-----------------------------------------------------------------------|---------------| +| EVENT_TRIGGERED | Indicates the delay is reported when the delay exceeds the threshold. | | +| PERIODIC | Indicates the delay is reported periodically. | | + +### 5.6.3.23 Enumeration: SmPolicyAssociationReleaseCause + +The enumeration SmPolicyAssociationReleaseCause represents the cause why the PCF requests the termination of the policy association. It shall comply with the provisions defined in table 5.6.3.23-1. + +**Table 5.6.3.23-1: Enumeration SmPolicyAssociationReleaseCause** + +| Enumeration value | Description | Applicability | +|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| UNSPECIFIED | This value is used for unspecified reasons. | | +| UE_SUBSCRIPTION | This value is used to indicate that the policy association needs to be terminated because the subscription of UE has changed (e.g. was removed). | | +| INSUFFICIENT_RES | This value is used to indicate that the server is overloaded and needs to abort the policy association. | | +| VALIDATION_CONDITION_NOT_MET | This value is used to indicate that the policy association needs to be terminated because the validation condition of background data transfer policy is not met. | EnhancedBackgroundDataTransfer | +| REACTIVATION_REQUESTED | This value is used to indicate that policy association needs to be terminated because the PCF is not able to maintain the existing PDU session and requests that the PDU session is reactivated. | ReleaseToReactivation | + +### 5.6.3.24 Enumeration: PduSessionRelCause + +**Table 5.6.3.24-1: Enumeration PduSessionRelCause** + +| Enumeration value | Description | Applicability | +|-------------------|----------------------------------------------------------------------------------------|----------------------| +| PS_TO_CS_HO | Indicates that the PDU session is terminated due to PS to CS handover. | PduSessionRelCause | +| RULE_ERROR | Indicates that the PDU session is terminated due to a session rule modification error. | ImmediateTermination | + +### 5.6.3.25 Enumeration: MaPduIndication + +**Table 5.6.3.25-1: Enumeration MaPduIndication** + +| Enumeration value | Description | Applicability | +|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| MA_PDU_REQUEST | UE requested MA PDU session and the request is authorized by subscription. | | +| MA_PDU_NETWORK_UPGRADE_ALLOWED | UE requested single access PDU session with indication of network upgrade to MA PDU session supported and the upgrade is authorized by subscription. | | + +## 5.6.3.26 Enumeration: AtsssCapability + +Table 5.6.3.26-1: Enumeration AtsssCapability + +| Enumeration value | Description | Applicability | +|--------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| ATSSS_LL | Indicates that the MA PDU Session supports the ATSSS-LL capability with any steering mode in the uplink and in the downlink. | | +| MPTCP_ATSSS_LL | Indicates that the MA PDU Session supports both the MPTCP and ATSSS-LL capability with any steering mode in the uplink and in the downlink. | | +| MPTCP_ATSSS_LL_WITH_ASMODE_UL | Indicates that the MA PDU Session supports the MPTCP capability with any steering mode in uplink and downlink, and ATSSS-LL capability with any steering mode in the downlink and Active-Standby mode in the uplink. | | +| MPTCP_ATSSS_LL_WITH_EXSDMODE_DL_ASMODE_UL | Indicates that the MA PDU Session supports the MPTCP capability with any steering mode in uplink and downlink, and ATSSS-LL capability with any steering mode except Smallest Delay mode in the downlink and Active-Standby mode in the uplink. | | +| MPTCP_ATSSS_LL_WITH_ASMODE_DLUL | Indicates that the MA PDU Session supports the MPTCP capability with any steering mode and ATSSS-LL capability with Active-Standby mode in uplink and downlink. | | +| MPQUIC_ATSSS_LL | Indicates that the MA PDU Session supports the MPQUIC and ATSSS-LL capability with any steering mode in the uplink and in the downlink. | EnATSSS_v2 | +| MPQUIC_ATSSS_LL_WITH_ASMODE_UL | Indicates that the MA PDU Session supports the MPQUIC capability with any steering mode in uplink and downlink, and ATSSS-LL capability with any steering mode in the downlink and Active-Standby mode in the uplink. | EnATSSS_v2 | +| MPQUIC_ATSSS_LL_WITH_EXSDMODE_DL_ASMODE_UL | Indicates that the MA PDU Session supports the MPQUIC capability with any steering mode in uplink and downlink, and ATSSS-LL capability with any steering mode except Smallest Delay mode in the downlink and Active-Standby mode in the uplink. | EnATSSS_v2 | +| MPQUIC_ATSSS_LL_WITH_ASMODE_DLUL | Indicates that the MA PDU Session supports the MPQUIC capability with any steering mode and ATSSS-LL capability with Active-Standby mode in uplink and downlink. | EnATSSS_v2 | +| MPTCP_MPQUIC_ATSSS_LL | Indicates that the MA PDU Session supports the MPTCP, MPQUIC and ATSSS-LL capability with any steering mode in the uplink and in the downlink. | EnATSSS_v2 | +| MPTCP_MPQUIC_ATSSS_LL_WITH_ASMODE_UL | Indicates that the MA PDU Session supports the MPTCP and MPQUIC capability with any steering mode in uplink and downlink, and ATSSS-LL capability with any steering mode in the downlink and Active-Standby mode in the uplink. | EnATSSS_v2 | +| MPTCP_MPQUIC_ATSSS_LL_WITH_EXSDMODE_DL_ASMODE_UL | Indicates that the MA PDU Session supports the MPTCP and MPQUIC capability with any steering mode in uplink and downlink, and ATSSS-LL capability with any steering mode except Smallest Delay mode in the downlink and Active-Standby mode in the uplink. | EnATSSS_v2 | +| MPTCP_MPQUIC_ATSSS_LL_WITH_ASMODE_DLUL | Indicates that the MA PDU Session supports the MPTCP and MPQUIC capability with any steering mode and ATSSS-LL capability with Active-Standby mode in uplink and downlink. | EnATSSS_v2 | + +### 5.6.3.27 Enumeration: NetLocAccessSupport + +**Table 5.6.3.27-1: Enumeration NetLocAccessSupport** + +| Enumeration value | Description | Applicability | +|-------------------|----------------------------------------------------------------------------------------------|---------------| +| ANR_NOT_SUPPORTED | Indicates that the access network does not support the report of access network information. | | +| TZR_NOT_SUPPORTED | Indicates that the access network does not support the report of UE time zone.
(NOTE 1) | | +| LOC_NOT_SUPPORTED | Indicates that the access network does not support the report of UE Location.
(NOTE 2) | | + +NOTE 1: The UE time zone is not available in EPC untrusted WLAN. +NOTE 2: The SMF+PGW determines the UE Location is not available as described in clause B.3.6.3. + +### 5.6.3.28 Enumeration: PolicyDecisionFailureCode + +**Table 5.6.3.28-1: PolicyDecisionFailureCode** + +| Enumeration value | Description | Applicability | +|-------------------|--------------------------------------------------------------------------------------------------------------------|---------------------------------| +| TRA_CTRL_DECS_ERR | Indicates failure in the provisioning of traffic control decision data. | | +| QOS_DECS_ERR | Indicates failure in the provisioning of QoS decision data. | | +| CHG_DECS_ERR | Indicates failure in the provisioning of charging decision data. | | +| USA_MON_DECS_ERR | Indicates failure in the provisioning of usage monitoring decision data. | UMC | +| QOS_MON_DECS_ERR | Indicates failure in the provisioning of QoS monitoring decision data. | | +| CON_DATA_ERR | Indicates failure in the provisioning of condition data. | | +| POLICY_PARAM_ERR | Indicates the information related to the provisioned policy parameter(s) is incorrect, incomplete or inconsistent. | ExtPolicyDecisionError Handling | + +### 5.6.3.29 Enumeration: NotificationControlIndication + +**Table 5.6.3.29-1: Enumeration NotificationControlIndication** + +| Enumeration value | Description | Applicability | +|-------------------|--------------------------------------------------------------|-----------------------| +| DDN_FAILURE | Indicates that the notification of DDN Failure is requested. | DDNEventPolicyControl | +| DDD_STATUS | Indicates that the notification of DDD status is requested. | DDNEventPolicyControl | + +### 5.6.3.30 Void + +### 5.6.3.31 Enumeration: SteerModelIndicator + +**Table 5.6.3.31-1: Enumeration SteerModelIndicator** + +| Enumeration value | Description | Applicability | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| AUTO_LOAD_BALANCE | Allows the UE and UPF to autonomously determine the traffic load of an SDF distributed across accesses. | | +| UE_ASSISTANCE | Allows the UE to decide how to distribute the UL traffic of an SDF and the UE may inform the UPF how it decided to distribute the UL traffic. | | + +### 5.6.3.32 Enumeration TrafficParameterMeas + +**Table 5.6.3.32-1: Enumeration TrafficParameterMeas** + +| Enumeration value | Description | Applicability | +|-------------------|--------------------------------------------------------------|---------------| +| DL_N6_JITTER | The downlink N6 jitter range associated with DL Periodicity. | | +| DL_PERIOD | The Downlink periodicity. | | +| UL_PERIOD | The Uplink periodicity. | | + +## 5.7 Error handling + +### 5.7.1 General + +HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [4]. + +For the Npcf\_SMPolicyControl API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. + +Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. + +In addition, the requirements in the following clauses shall apply. + +### 5.7.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the Npcf\_SMPolicyControl API. + +### 5.7.3 Application Errors + +The application errors defined for the Npcf\_SMPolicyControl API are listed in table 5.7.3-1 and 5.7.3-2. + +**Table 5.7.3-1: Application errors when PCF acts as a server** + +| Application Error | HTTP status code | Description | +|-------------------------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| USER_UNKNOWN | 400 Bad Request | The HTTP request is rejected because the end user specified in the request is unknown to the PCF. (NOTE 1) (NOTE 3) | +| ERROR_INITIAL_PARAMETERS | 400 Bad Request | The HTTP request is rejected because the set of session or subscriber information needed by the PCF for rule selection is incomplete or erroneous or not available for the decision to be made. (E.g. QoS, RAT type, subscriber information) (NOTE 1) (NOTE 2) (NOTE 3) | +| ERROR_TRIGGER_EVENT | 400 Bad Request | The HTTP request is rejected because the set of session information sent the message originated due to a trigger been met is incoherent with the previous set of session information for the same session. (E.g. trigger met was RAT changed, and the RAT notified is the same as before) (NOTE 2) (NOTE 3) | +| PENDING_TRANSACTION | 400 Bad Request | This error shall be used when the PendingTransaction feature is supported and the PCF receives an incoming request on a policy association while it has an ongoing transaction on the same policy association and cannot handle the request as described in clause 9.2 of 3GPP TS 29.513 [7]. (NOTE 2) | +| ERROR_TRAFFIC_MAPPING_INFO_REJECTED | 403 Forbidden | The HTTP request is rejected because the PCF does not accept one or more of the traffic mapping filters provided by the NF service consumer in a PCC Request. (NOTE 2) (NOTE 3) | +| ERROR_CONFLICTING_REQUEST | 403 Forbidden | The HTTP request is rejected because the PCF cannot accept the UE-initiated resource request as a network-initiated resource allocation is already in progress that has packet filters that cover the packet filters in the received UE-initiated resource request. The NF service consumer shall reject the attempt for UE-initiated resource request. (NOTE 2) (NOTE 3) | +| LATE_OVERLAPPING_REQUEST | 403 Forbidden | The request is rejected because it collides with and exiting Policy Association with a more recent originating timestamp. (NOTE 1) | +| POLICY_CONTEXT_DENIED | 403 Forbidden | The HTTP request is rejected because the PCF does not accept the NF service consumer request due to operator policies and/or local configuration. (NOTE 1) (NOTE 2) (NOTE 3) | +| VALIDATION_CONDITION_NOT_MET | 403 Forbidden | The HTTP request is rejected because the PCF does not accept the NF service consumer request because the validation condition of background data transfer policy is not met. (NOTE 1) (NOTE 3) | +| INVALID_BDT_POLICY | 403 Forbidden | The HTTP request is rejected because the PCF does not accept the NF service consumer request because the background data transfer policy is invalid. (NOTE 1) | +| EXCEEDED_UE_SLICE_DATA_RATE | 403 Forbidden | The HTTP request is rejected because the PCF does not accept the NF service consumer request because the authorized data rate exceeds the consumed data rate for that UE and network slice. (NOTE 1) (NOTE 2) | +| EXCEEDED_SLICE_DATA_RATE | 403 Forbidden | The HTTP request is rejected because the PCF does not accept the NF service consumer request because the authorized data rate exceeds the consumed data rate for that slice. (NOTE 1) (NOTE 2) | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EXCEEDED_GROUP_DATA_RATE | 403 Forbidden | The HTTP request is rejected because the PCF does not accept the NF service consumer request because the authorized group data rate exceeds the consumed data rate for the concerned group. (NOTE 1) (NOTE 2) | +| POLICY_ASSOCIATION_NOT_FOUND | 404 Not Found | The HTTP request is rejected because no policy association corresponding to the request exists in the PCF. (NOTE 2) | +| NOTE 1: These application errors are used by the create service operation (see clause 4.2.2.2) and included in the responses to the POST request.
NOTE 2: These application errors are used by the update service operation (see clause 4.2.4.2) and included in the responses to the POST request.
NOTE 3: The Cause codes mapping performed by NF service consumer between this Application Error and the 5GSM related value is specified in clause 5.2.2.2 of 3GPP TS 29.524 [40].
NOTE 4: Including a "ProblemDetails" data structure with the "cause" attribute in the HTTP response is optional unless explicitly mandated in the service operation clauses. | | | + +**Table 5.7.3-2: Application errors when NF service consumer acts as a server to receive a notification** + +| Application Error | HTTP status code | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PCC_RULE_EVENT | 400 Bad Request | The HTTP request is rejected because all the PCC rules provisioned by the PCF in the request cannot be installed/activated. It is used to inform the PCF that the request failed, and should not be attempted again. (NOTE 1) | +| PCC_QOS_FLOW_EVENT | 400 Bad Request | The HTTP request is rejected because for some reason all the PCC rules provisioned by the PCF in the request cannot be enforced or modified successfully in a network initiated procedure. It is used to inform the PCF that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. (NOTE 1) | +| UE_STATUS_SUSPEND | 400 Bad Request | The HTTP request is rejected because the UE's status is suspended and the policy decisions received from the PCF cannot be enforced by the NF service consumer. Applicable only to functionality introduced with the PolicyUpdateWhenUESuspends feature as described in clause 5.8. (NOTE 1) | +| RULE_PERMANENT_ERROR | 400 Bad Request | The HTTP request is rejected because all the PCC rules and/or session rules provisioned by the PCF in the request cannot be installed/activated. It is used to inform the PCF that the request failed, and should not be attempted again. Applicable only to functionality introduced with the SessionRuleErrorHandler feature as described in clause 5.8. (NOTE 1) | +| RULE_TEMPORARY_ERROR | 400 Bad Request | The HTTP request is rejected because for some reason all the PCC rules and/or session rules provisioned by the PCF in the request cannot be enforced or modified successfully in a network initiated procedure. It is used to inform the PCF that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. Applicable only to functionality introduced with the SessionRuleErrorHandler feature as described in clause 5.8. (NOTE 1) | +| PENDING_TRANSACTION | 400 Bad Request | This error shall be used when the PendingTransaction feature is supported and the NF service consumer receives an incoming request on a policy association while it has an ongoing transaction on the same policy association and cannot handle the request as described in clause 9.2 of 3GPP TS 29.513 [7]. (NOTE 1) | +| AN_GW_FAILED | 400 Bad Request | This error shall be used when SGWRest feature is supported and the received policy decisions (i.e. installation/modification of PCC rules or session rules) cannot be enforced by the SMF because the AN-Gateway has failed. (NOTE 1) | +| POL_DEC_ERROR | 400 Bad Request | This error shall be used when Ext2PolicyDecisionErrorHandler feature is supported, the PCF provides only SM policy decisions and/or condition data and all the policy decisions and/or conditions in the request cannot be stored in the NF service consumer. | +| NOTE 1: These application errors are used by the UpdateNotify service operation (see clause 4.2.3.2) and included in the responses to the POST request. | | | +| NOTE 2: Including a "ProblemDetails" data structure with the "cause" attribute in the HTTP response is optional unless explicitly mandated in the service operation clauses. | | | + +## 5.8 Feature negotiation + +The optional features in table 5.8-1 are defined for the Npcf\_SMPolicyControl API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4]. + +**Table 5.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | TSC | This feature indicates support for traffic steering control in the (S)GI-LAN, steering the 5G-LAN type of services or routing of the user traffic to a local Data Network identified by the DNAI per AF request. If the NF service consumer supports this feature, the PCF shall behave as described in clause 4.2.6.2.6. | +| 2 | ResShare | This feature indicates the support of service data flows that share resources. If the NF service consumer supports this feature, the PCF shall behave as described in clause 4.2.6.2.8. | +| 3 | 3GPP-PS-Data-Off | This feature indicates the support of 3GPP PS Data off status change reporting. | +| 4 | ADC | This feature indicates the support of application detection and control. | +| 5 | UMC | Indicates that the usage monitoring control is supported. | +| 6 | NetLoc | This feature indicates the support of the Access Network Information Reporting for 5GS. | +| 7 | RAN-NAS-Cause | This feature indicates the support for the detailed release cause code information from the access network. (NOTE) | +| 8 | ProvAFsignalFlow | This feature indicates support for the feature of IMS Restoration as described in clause 4.2.3.17. If NF service consumer supports this feature the PCF may provision AF signalling IP flow information. | +| 9 | PCSCF-Restoration-Enhancement | This feature indicates support of P-CSCF Restoration Enhancement. It is used for the NF service consumer to indicate if it supports P-CSCF Restoration Enhancement. | +| 10 | PRA | This feature indicates the support of presence reporting area change reporting. The support of the update of a UE Dedicated Presence Reporting Area is unspecified. | +| 11 | RuleVersioning | This feature indicates the support of PCC rule versioning as defined in clause 4.2.6.2.14. | +| 12 | SponsoredConnectivity | This feature indicates support for sponsored data connectivity feature. If the NF service consumer supports this feature, the PCF may authorize sponsored data connectivity to the subscriber. | +| 13 | RAN-Support-Info | This feature indicates the support of maximum packet loss rate value(s) for uplink and/or downlink voice service data flow(s). | +| 14 | PolicyUpdateWhenUESuspends | This feature indicates the support of report when the UE is suspended and then resumed from suspend state. Only applicable to the interworking scenario as defined in Annex B. | +| 15 | AccessTypeCondition | This feature indicates the support of access type conditioned authorized Session-AMBR as defined in clause 4.2.6.3.2.4. | +| 16 | Multilpv6AddrPrefix | This feature indicates the support of additional new/removed (up to two) IPv6 address prefixes reporting. | +| 17 | SessionRuleErrorHandling | This feature indicates the support of session rule error handling. | +| 18 | AF_Charging_Identifier | This feature indicates the support of long character strings as charging identifiers. | +| 19 | ATSSS | This feature indicates the support of the access traffic switching, steering and splitting functionality as defined in clauses 4.2.6.2.17 and 4.2.6.3.4. | +| 20 | PendingTransaction | This feature indicates support for the race condition handling as defined in 3GPP TS 29.513 [7]. | +| 21 | URLLC | This feature indicates support of Ultra-Reliable Low-Latency Communication (URLLC) requirements, i.e. AF application relocation acknowledgement requirement and UE address(es) preservation. The TSC feature shall be supported in order to support this feature. | +| 22 | MacAddressRange | Indicates the support of a set of MAC addresses with a specific range in the traffic filter. | +| 23 | WWC | Indicates support of wireless and wireline convergence access as defined in annex C. | + +| | | | +|----|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 24 | QosMonitoring | Indicates support of QoS monitoring as defined in clause 4.2.3.25 and 4.2.4.24. Reporting of monitoring data applies to packet delay information when only this feature is supported. | +| 25 | AuthorizationWithRequiredQoS | Indicates support of policy authorization for the AF session with required QoS as defined in clause 4.2.3.22. | +| 26 | EnhancedBackgroundDataTransfer | Indicates the support of applying the Background Data Transfer Policy to a future PDU session. | +| 27 | DN-Authorization | This feature indicates the support of DN-AAA authorization data for policy control. | +| 28 | PDUSessionRelCause | Indicates the support of "PS_TO_CS_HO" PDU session release cause. | +| 29 | SamePcf | This feature indicates the support of same PCF selection for the parameter's combination. | +| 30 | ADCmultiRedirection | This feature indicates support for multiple redirection information in application detection and control. It requires the support of ADC feature. | +| 31 | RespBasedSessionRel | Indicates support of handling PDU session termination functionality as defined in clause 4.2.4.22. | +| 32 | TimeSensitiveNetworking | Indicates that the 5G System is integrated within the external network as a TSN bridge. | +| 33 | EMDBV | This feature indicates the support of the ExtMaxDataBurstVol data type defined in 3GPP TS 29.571 [11]. The use of this data type is specified in clause 4.2.2.1. | +| 34 | DNNSelectionMode | This feature indicates the support of DNN selection mode. | +| 35 | EPSFallbackReport | This feature indicates the support of the report of EPS Fallback as defined in clauses B.3.3.2 and B.3.4.6. | +| 36 | PolicyDecisionErrorHandler | This feature indicates the support of the error report of the policy decision and/or condition data which is not referred by any PCC rule or session rule as defined in clause 4.2.3.26 and 4.2.4.26. | +| 37 | DDNEventPolicyControl | This feature indicates the support for policy control in the case of DDN Failure and Delivery Status events as defined in clause 4.2.4.27. | +| 38 | ReallocationOfCredit | This feature indicates the support of notifications of reallocation of credit. | +| 39 | BDTPolicyRenegotiation | This feature indicates the support of the BDT policy renegotiation. | +| 40 | ExtPolicyDecisionErrorHandler | This feature indicates the support of the error report of a faulty SM policy decision parameter as defined in clause 4.2.3.26 and 4.2.4.26. It requires the support of PolicyDecisionErrorHandler feature. | +| 41 | ImmediateTermination | This feature indicates the support of the termination the PDU session when the NF service consumer cannot ensure the UE, RAN, AMF, or UPF can revert to the status before the PDU session modification occurred, as defined in clause 4.2.4.21. | +| 42 | AggregatedUELocChanges | This feature indicates the support of notifications of serving area (i.e. tracking area) and/or serving cell changes. | +| 43 | ES3XX | Extended Support for 3xx redirections. This feature indicates the support of redirection for any service operation, according to Stateless NF procedures as specified in clauses 6.5.3.2 and 6.5.3.3 of 3GPP TS 29.500 [4] and according to HTTP redirection principles for indirect communication, as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. | +| 44 | GroupIdListChange | This feature indicates the support for the notification of changes in the list of internal group identifiers. | +| 45 | DisableUENotification | Indicates the support of disabling QoS flow parameters signalling to the UE when the SMF is notified by the NG-RAN of changes in the fulfilled QoS situation. This feature requires that the AuthorizationWithRequiredQoS feature is also supported. | +| 46 | OfflineChOnly | This feature enables the PCF to signal the "PDU Session with offline charging only" indication as defined in clause 4.2.2.3.3. | + +| | | | +|----|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 47 | Dual-Connectivity-redundant-UP-paths | Indicates the support of policy authorization of end to end redundant user plane path using dual connectivity as described in clause 4.2.2.20. | +| 48 | DDNEventPolicyControl2 | This feature indicates the support for the policy control removal in the case of DDN Failure and/or Delivery Status event(s) is cancelled as defined in clause 4.2.4.27. The DDNEventPolicyControl feature shall be supported in order to support this feature. | +| 49 | VPLMN-QoS-Control | Indicates the support of QoS constraints from the VPLMN for the derivation of the authorized Session-AMBR and authorized default QoS. | +| 50 | 2G3GIWK | This feature indicates the support of GERAN and UTRAN access over N7 interface. | +| 51 | TimeSensitiveCommunication | Indicates that the 5G System is integrated within the external network as a TSC user plane node to enable the Time Sensitive Communications and Time Synchronization. This feature requires that the TimeSensitiveNetworking feature is also supported. | +| 52 | AF_latency | This feature indicates the support of Edge relocation considering user plane latency. This feature requires that the TSC feature is also supported. | +| 53 | SatBackhaulCategoryChg | This feature indicates the support of notification of a change between different satellite backhaul categories, or between satellite backhaul and non-satellite backhaul. | +| 54 | CHFsetSupport | Indicates the support of CHF redundancy and failover mechanisms based on CHF instance availability within a CHF Set, as described in clause 4.2.2.3.1. | +| 55 | EnATSSS | Indicates the support of ATSSS enhancement. It requires the support of ATSSS feature. | +| 56 | MPSforDTS | Indicates support of the MPSfor DTS feature as described in clause 4.2.6.2.12.4. | +| 57 | RoutingInfoRemoval | Indicates the support of the removal of the "routeToLocs" attribute from the TrafficControlData instance. | +| 58 | ePRA | This feature indicates the support of presence reporting area change reporting. It additionally supports the update of the elements of a UE Dedicated Presence Reporting Area by the full replacement of the previously provided one comparing with the PRA feature. | +| 59 | AMInfluence | Indicates the support of the delivery of the PCF for the UE request to be notified by the PCF for the PDU session about PDU session established/terminated events. | +| 60 | PvsSupport | This feature indicates the support of SNPn UE Remote Provisioning via User Plane as described in clause 4.2.2.21. | +| 61 | EneNA | This feature indicates the support of NWDAF data reporting. | +| 62 | BIUMR | This feature bit indicates whether the NF Service Consumer (e.g. SMF) and PCF supports Binding Indication Update for multiple resource contexts specified in clauses 6.12.1 and 5.2.3.2.6 of 3GPP TS 29.500 [4]. | +| 63 | EASIPreplacement | This feature indicates the support of EAS IP replacement. This feature requires that the TSC feature is also supported. | +| 64 | ExposureToEAS | This feature indicates the support of exposure of QoS monitoring results to local AF. This feature requires that QosMonitoring feature is also supported. | +| 65 | SimultConnectivity | This feature indicates the support of temporary simultaneously connectivity at edge relocation. This feature requires that the TSC feature is also supported. | +| 66 | SGWRest | This feature indicates the support of SGW Restoration procedures. Only applicable to the interworking scenario as defined in Annex B. | +| 67 | ReleaseToReactivate | This feature indicates that the PCF can request the SMF for reactivation of a PDU session based on an SM Policy Association release cause. | +| 68 | EASDiscovery | This feature indicates the support of EAS (re)discovery. | +| 69 | AccNetChargId_String | This feature indicates the support of long character strings as access network charging identifier. | + +| | | | +|----|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 70 | WLAN_Location | This feature indicates the support of the report of the WLAN location information received from the ePDG/EPC, if available. It is only applicable to EPS interworking scenarios as specified in Annex B. | +| 71 | PackFiltAllocPrecedence | This feature indicates the support of the control of the maximum number of packet filters in the EPS network in the EPS interworking scenarios as described in Annex B. | +| 72 | SatBackhaulCategoryChg_v2 | This feature indicates the support of the indication of satellite backhaul categories, or the indication of non-satellite backhaul during the response to the update notify request. | +| 73 | PacketDelayFailureReport | Indicates the support of packet delay failure report as part of QoS Monitoring procedures. This feature requires that QosMonitoring feature is supported. | +| 74 | AltQoSProfilesSupportReport | This feature indicates the support of the report of whether Alternative QoS parameters are supported by NG-RAN. This feature requires that AuthorizationWithRequiredQoS feature is also supported. | +| 75 | Ext2PolicyDecisionErrorHandler | This feature indicates the support of the error report of the policy decision and/or condition data which is not referred by any PCC rule or session rule when no PCC rules and no session rules are provided and the handling of partial errors. It requires the support of ExtPolicyDecisionErrorHandler feature. | +| 76 | UEUnreachable | This feature indicates the support for the reporting of UE temporarily unavailable. | +| 77 | EnTSCAC | Indicates the support of extensions to TSCAC and the RAN feedback for BAT offset and adjusted periodicity. This feature requires that TimeSensitiveCommunication feature is also supported. | +| 78 | MTU_Size | This feature indicates the support of the report of the MTU size of the device side port. This feature requires that the TimeSensitiveCommunication feature is also supported. | +| 79 | EnSatBackhaulCatChg | This feature indicates the support of notification of dynamic satellite backhaul categories. It requires the support of SatBackhaulCategoryChg and SatBackhaulCategoryChg_v2 features. | +| 80 | SFC | This feature indicates support for application function influence on service function chaining(s). It requires the support of TSC feature. | +| 81 | EpsUrsp | This feature indicates the support of URSP provisioning in EPS. Only applicable to the interworking scenario as defined in Annex B. | +| 82 | CommonEASDNAI | This feature controls the support of the common EAS/DNAI selection. It requires the support of TSC feature. | +| 83 | UnlimitedMultilpv6Prefix | This feature indicates the support of multiple IPv6 address prefixes reporting. | +| 84 | NscSupportedFeatures | This feature indicates the support of provisioning of the Network Function Service Consumer features supported in Nsmf_EventExposure service as described in 3GPP TS 29.508 [12]. | +| 85 | URSPEnforcement | This feature indicates the support of awareness of URSP rule enforcement | +| 86 | VBCforIMS | This feature indicates the support of provisioning of the caller and callee informations in volume based charging for IMS as defined in clause A.16 of 3GPP TS 29.214 [18] (replacing PCRF with PCF). | +| 87 | ExposureToTSC | This feature indicates the support of the direct event notification of TSC management information from the UPF to the TSCTSF or TSN AF in 5GC. This feature requires that TimeSensitiveCommunication feature is also supported. | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 88 | NetSliceRepl | This feature indicates the support of the network slice replacement functionality introduced in this specification as part of the end-to-end network slicing functionality.

The following functionalities are supported:
- Support the reporting of the network slice replacement information to the PCF. | +| 89 | SessQoSModEnforcementFailure | This feature indicates the support of the report PDU session modification failure because the enforcement of the default QoS modification or session-AMBR modification of the active session rule failed. | +| 90 | HR-SBO | This feature indicates the support of VPLMN specific Offloading policy in Home Routed deployments with Session Breakout (HR-SBO). | +| 91 | EnATSSS_v2 | Indicates the support of ATSSS enhancements which includes REDUNDANT steering mode, MPQUIC steering functionality and MA PDU session interworking enhancements. It requires the support of the EnATSSS features. | +| 92 | NetSliceUsageCtrl | This feature indicates the support of the network slice usage control functionality introduced in this specification as part of the end-to-end network slicing functionality.

The following functionalities are supported:
- Support the provisioning by the PCF of the network slice usage control information (e.g., slice PDU session inactivity timer value). | +| 93 | VPLMN-5QIPrioLevel | Indicates the support of the indication of the VPLMN supported 5QI priority level when the required 5QI Priority Level is different from the standardized Default Priority Level value in the QoS characteristics Table 5.7.4-1 in 3GPP TS 23.501 [2].
This feature requires that VPLMN-QoS-Control feature is also supported. | +| 94 | PDUSetHandlinge | This feature indicates the support of PDU Set handling. This feature may be used for eXtended Reality (XR) and interactive media services. | +| 95 | RTLatency | This feature indicates the support of Round-Trip latency. This feature may be used for eXtended Reality (XR) and interactive media services | +| 96 | EnQoSMon | This feature indicates the support of enhanced QoS monitoring functionality, i.e. the report of the congestion information, and/or, the data rate information monitoring. | +| 97 | PowerSaving | This feature indicates the support of the Power Saving for different traffic measurement. | +| 98 | L4S | This feature indicates the support of the PCF indication of ECN marking for L4S support. | +| 99 | UPEAS | This feature indicates the support of UPF enhancements for exposure related to the identification of QoS monitoring event exposure subscription. | +| NOTE: 5GS and EPS release cause code information is supported. The EPS release cause code information from the access network is only applicable to EPS interworking scenarios as specified in Annex B. | | | + +Editor's note: Whether and/how to indicate the support of end of burst indication, and provision the flow periodicity information within the Power Saving feature is FFS. + +## 5.9 Security + +As indicated in 3GPP TS 33.501 [27], the access to the Npcf\_SMPolicyControl API shall be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [28]), using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [29]) plays the role of the authorization server. + +An NF service consumer, prior to consuming services offered by the Npcf\_SMPolicyControl API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [29], clause 5.4.2.2. + +NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF service consumer used for discovering the Npcf\_SMPolicyControl service. + +The Npcf\_SMPolicyControl API defines a single scope "npcf-smpolicycontrol" for OAuth2 authorization (as specified in 3GPP TS 33.501 [27]) for the entire API, and it does not define any additional scopes at resource or operation level. + +# Annex A (normative): OpenAPI specification + +## A.1 General + +The present Annex contains an OpenAPI [10] specification of HTTP messages and content bodies used by the Npcf\_SMPolicyControl API. + +This Annex shall take precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API. + +NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification file contained in this 3GPP Technical Specification are available on a Git-based repository, that uses the GitLab software version control system (see clause 5B of the 3GPP TR 21.900 [38] and clause 5.3.1 of the 3GPP TS 29.501 [5] for further information). + +## A.2 Npcf\_SMPolicyControl API + +``` +openapi: 3.0.0 + +info: + title: Npcf_SMPolicyControl API + version: 1.3.0-alpha.5 + description: | + Session Management Policy Control Service + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.512 V18.4.0; 5G System; Session Management Policy Control Service. + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.512/' + +security: + - {} + - oAuth2ClientCredentials: + - npcf-smpolicycontrol + +servers: + - url: '{apiRoot}/npcf-smpolicycontrol/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501 + +paths: + /sm-policies: + post: + summary: Create a new Individual SM Policy. + operationId: CreateSMPolicy + tags: + - SM Policies (Collection) + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SmPolicyContextData' + responses: + '201': + description: Created + content: + application/json: + schema: + $ref: '#/components/schemas/SmPolicyDecision' +``` + +``` + +headers: + Location: + description: Contains the URI of the newly created resource. + required: true + schema: + type: string +'308': + description: Permanent Redirect + headers: + Location: + description: > + Contains the URI of the PCF within the existing PCF binding information stored in + the BSF for the same UE ID, S-NSSAI and DNN combination. + required: true + schema: + type: string +'400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' +'502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' +'503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +callbacks: + SmPolicyUpdateNotification: + '{ $request.body#/notificationUri }/update': + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SmPolicyNotification' +responses: + '200': + description: > + OK. The current applicable values corresponding to the policy control request + trigger is reported. + content: + application/json: + schema: + oneOf: + - $ref: '#/components/schemas/UeCampingRep' + - type: array + items: + $ref: '#/components/schemas/PartialSuccessReport' + minItems: 1 + - type: array + items: + $ref: '#/components/schemas/PolicyDecisionFailureCode' + minItems: 1 + '204': + description: No Content, Notification was successful + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + description: Bad Request. + content: + application/json: + +``` + +``` + + schema: + $ref: '#/components/schemas/ErrorReport' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + SmPolicyControlTerminationRequestNotification: + '{ $request.body#/notificationUri }/terminate': + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/TerminationNotification' + responses: + '204': + description: No Content, Notification was successful + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +/sm-policies/{smPolicyId}: + get: + summary: Read an Individual SM Policy + operationId: GetSMPolicy + tags: + - Individual SM Policy (Document) + parameters: + - name: smPolicyId + in: path + description: Identifier of a policy association. + required: true + schema: + type: string + responses: + +``` + +``` + +'200': + description: OK. Resource representation is returned. + content: + application/json: + schema: + $ref: '#/components/schemas/SmPolicyControl' +'307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' +'308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' +'406': + $ref: 'TS29571_CommonData.yaml#/components/responses/406' +'429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' +'502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' +'503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +/sm-policies/{smPolicyId}/update: + post: + summary: Update an existing Individual SM Policy + operationId: UpdateSMPolicy + tags: + - Individual SM Policy (Document) + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SmPolicyUpdateContextData' + parameters: + - name: smPolicyId + in: path + description: Identifier of a policy association. + required: true + schema: + type: string + responses: + '200': + description: OK. Updated policies are returned + content: + application/json: + schema: + $ref: '#/components/schemas/SmPolicyDecision' + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + +``` + +``` + + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +/sm-policies/{smPolicyId}/delete: + post: + summary: Delete an existing Individual SM Policy. + operationId: DeleteSMPolicy + tags: + - Individual SM Policy (Document) + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SmPolicyDeleteData' + parameters: + - name: smPolicyId + in: path + description: Identifier of a policy association. + required: true + schema: + type: string + responses: + '204': + description: No content + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{nrfApiRoot}/oauth2/token' + scopes: + npcf-smpolicycontrol: Access to the Npcf_SMPolicyControl API + +schemas: + SmPolicyControl: + description: > + Contains the parameters used to request the SM policies and the SM policies authorized by + the PCF. + type: object + properties: + context: + $ref: '#/components/schemas/SmPolicyContextData' + policy: + $ref: '#/components/schemas/SmPolicyDecision' + +``` + +``` +required: + - context + - policy + +SmPolicyContextData: + description: Contains the parameters used to create an Individual SM policy resource. + type: object + properties: + accNetChId: + $ref: '#/components/schemas/AccNetChId' + chargEntityAddr: + $ref: '#/components/schemas/AccNetChargingAddress' + gpsi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' + supi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' + invalidSupi: + type: boolean + description: > + When this attribute is included and set to true, it indicates that the supi attribute + contains an invalid value.This attribute shall be present if the SUPI is not available + in the SMF or the SUPI is unauthenticated. When present it shall be set to true for an + invalid SUPI and false (default) for a valid SUPI. + interGrpIds: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/GroupId' + minItems: 1 + pduSessionId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionId' + pduSessionType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionType' + chargingcharacteristics: + type: string + dnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' + dnnSelMode: + $ref: 'TS29502_Nsmf_PDUSession.yaml#/components/schemas/DnnSelectionMode' + notificationUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + accessType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' + ratType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' + addAccessInfo: + $ref: '#/components/schemas/AdditionalAccessInfo' + servingNetwork: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' + userLocationInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation' + ueTimeZone: + $ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone' + pei: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Pei' + ipv4Address: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' + ipv6AddressPrefix: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' + ipDomain: + type: string + description: Indicates the IPv4 address domain + subsSessAmbr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ambr' + authProfIndex: + type: string + description: Indicates the DN-AAA authorization profile index + subsDefQos: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SubscribedDefaultQos' + vplmnQos: + $ref: 'TS29502_Nsmf_PDUSession.yaml#/components/schemas/VplmnQos' + numOfPackFilter: + type: integer + description: Contains the number of supported packet filter for signalled QoS rules. + online: + type: boolean + description: > + If it is included and set to true, the online charging is applied to the PDU session. + offline: +``` + +``` +type: boolean +description: > + If it is included and set to true, the offline charging is applied to the PDU session. +3gppPsDataOffStatus: + type: boolean + description: > + If it is included and set to true, the 3GPP PS Data Off is activated by the UE. +refQosIndication: + type: boolean + description: If it is included and set to true, the reflective QoS is supported by the UE. +traceReq: + $ref: 'TS29571_CommonData.yaml#/components/schemas/TraceData' +sliceInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai' +qosFlowUsage: + $ref: '#/components/schemas/QosFlowUsage' +servNfId: + $ref: '#/components/schemas/ServingNfIdentity' +suppFeat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' +smfId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' +recoveryTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' +maPduInd: + $ref: '#/components/schemas/MaPduIndication' +atsssCapab: + $ref: '#/components/schemas/AtsssCapability' +ipv4FrameRouteList: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4AddrMask' + minItems: 1 +ipv6FrameRouteList: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' + minItems: 1 +satBackhaulCategory: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SatelliteBackhaulCategory' +pcfUeInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PcfUeCallbackInfo' +pvsInfo: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ServerAddressingInfo' + minItems: 1 +onboardInd: + type: boolean + description: > + If it is included and set to true, it indicates that the PDU session is used for + UE Onboarding. +nwdafDatas: + type: array + items: + $ref: '#/components/schemas/NwdafData' + minItems: 1 +urspEnfInfo: + $ref: '#/components/schemas/UrspEnforcementInfo' +sscMode: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SscMode' +ueReqDnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' +redundantPduSessionInfo: + $ref: 'TS29502_Nsmf_PDUSession.yaml#/components/schemas/RedundantPduSessionInformation' +hrsboInd: + type: boolean + description: > + HR-SBO support indication. If present and set to "true", it indicates that the HR-SBO is + supported. Default value is "false" if omitted. +required: +- supi +- pduSessionId +- pduSessionType +- dnn +- notificationUri +- sliceInfo +``` + +``` +SmPolicyDecision: + description: Contains the SM policies authorized by the PCF. + type: object + properties: + sessRules: + type: object + additionalProperties: + $ref: '#/components/schemas/SessionRule' + minProperties: 1 + description: > + A map of Sessionrules with the content being the SessionRule as described in + clause 5.6.2.7. The key used in this map for each entry is the sessRuleId + attribute of the corresponding SessionRule. + pccRules: + type: object + additionalProperties: + $ref: '#/components/schemas/PccRule' + minProperties: 1 + description: > + A map of PCC rules with the content being the PCCRule as described in + clause 5.6.2.6. The key used in this map for each entry is the pccRuleId + attribute of the corresponding PccRule. + nullable: true + pscfRestIndication: + type: boolean + description: > + If it is included and set to true, it indicates the P-CSCF Restoration is requested. + qosDecs: + type: object + additionalProperties: + $ref: '#/components/schemas/QosData' + minProperties: 1 + description: > + Map of QoS data policy decisions. The key used in this map for each entry is the qosId + attribute of the corresponding QosData. + chgDecs: + type: object + additionalProperties: + $ref: '#/components/schemas/ChargingData' + minProperties: 1 + description: > + Map of Charging data policy decisions. The key used in this map for each entry + is the chgId attribute of the corresponding ChargingData. + nullable: true + chargingInfo: + $ref: '#/components/schemas/ChargingInformation' + traffContDecs: + type: object + additionalProperties: + $ref: '#/components/schemas/TrafficControlData' + minProperties: 1 + description: > + Map of Traffic Control data policy decisions. The key used in this map for each entry + is the tcId attribute of the corresponding TrafficControlData. + umDecs: + type: object + additionalProperties: + $ref: '#/components/schemas/UsageMonitoringData' + minProperties: 1 + description: > + Map of Usage Monitoring data policy decisions. The key used in this map for each entry + is the umId attribute of the corresponding UsageMonitoringData. + nullable: true + qosChars: + type: object + additionalProperties: + $ref: '#/components/schemas/QosCharacteristics' + minProperties: 1 + description: > + Map of QoS characteristics for non standard 5QIs. This map uses the 5QI values as keys. + qosMonDecs: + type: object + additionalProperties: + $ref: '#/components/schemas/QosMonitoringData' + minProperties: 1 + description: > + Map of QoS Monitoring data policy decisions. The key used in this map for each entry + is the qmId attribute of the corresponding QosMonitoringData. +``` + +``` + + nullable: true + reflectiveQoSTimer: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' + cond: + type: object + additionalProperties: + $ref: '#/components/schemas/ConditionData' + minProperties: 1 + description: > + A map of condition data with the content being as described in clause 5.6.2.9. The key + used in this map for each entry is the condId attribute of the corresponding + ConditionData. + nullable: true + revalidationTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' + offline: + type: boolean + description: > + Indicates the offline charging is applicable to the PDU session when it is included and + set to true. + online: + type: boolean + description: > + Indicates the online charging is applicable to the PDU session when it is included and + set to true. + offlineChOnly: + type: boolean + default: false + description: > + Indicates that the online charging method shall never be used for any PCC rule activated + during the lifetime of the PDU session. + policyCtrlReqTriggers: + type: array + items: + $ref: '#/components/schemas/PolicyControlRequestTrigger' + minItems: 1 + description: Defines the policy control request triggers subscribed by the PCF. + nullable: true + lastReqRuleData: + type: array + items: + $ref: '#/components/schemas/RequestedRuleData' + minItems: 1 + description: Defines the last list of rule control data requested by the PCF. + lastReqUsageData: + $ref: '#/components/schemas/RequestedUsageData' + praInfos: + type: object + additionalProperties: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PresenceInfoRm' + minProperties: 1 + description: > + Map of PRA information. The praId attribute within the PresenceInfo data type is the key + of the map. + nullable: true + ipv4Index: + $ref: 'TS29519_Policy_Data.yaml#/components/schemas/IpIndex' + ipv6Index: + $ref: 'TS29519_Policy_Data.yaml#/components/schemas/IpIndex' + qosFlowUsage: + $ref: '#/components/schemas/QosFlowUsage' + relCause: + $ref: '#/components/schemas/SmPolicyAssociationReleaseCause' + suppFeat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + tsnBridgeManCont: + $ref: '#/components/schemas/BridgeManagementContainer' + tsnPortManContDstt: + $ref: '#/components/schemas/PortManagementContainer' + tsnPortManContNwtt: + type: array + items: + $ref: '#/components/schemas/PortManagementContainer' + minItems: 1 + tscNotifUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + tscNotifCorreId: + type: string + +``` + +``` + description: > + Correlation identifier for TSC management information notifications. + redSessIndication: + type: boolean + description: > + Indicates whether the PDU session is a redundant PDU session. If absent it means the PDU + session is not a redundant PDU session. + uePolCont: + $ref: '#/components/schemas/UePolicyContainer' + sliceUsCtrlInfo: + $ref: '#/components/schemas/SliceUsCtrlInfo' + vplmnOffload: + $ref: 'TS29571_CommonData.yaml#/components/schemas/VplmnOffloadingInfo' + +SmPolicyNotification: + description: Represents a notification on the update of the SM policies. + type: object + properties: + resourceUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + smPolicyDecision: + $ref: '#/components/schemas/SmPolicyDecision' + +PccRule: + description: Contains a PCC rule information. + type: object + properties: + flowInfos: + type: array + items: + $ref: '#/components/schemas/FlowInformation' + minItems: 1 + description: An array of IP flow packet filter information. + appId: + type: string + description: A reference to the application detection filter configured at the UPF. + appDescriptor: + $ref: '#/components/schemas/ApplicationDescriptor' + contVer: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ContentVersion' + protoDesc: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ProtoDesc' + pccRuleId: + type: string + description: Univocally identifies the PCC rule within a PDU session. + precedence: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger' + afSigProtocol: + $ref: '#/components/schemas/AfSigProtocol' + appReloc: + type: boolean + description: Indication of application relocation possibility. + easRedisInd: + type: boolean + description: Indicates the EAS rediscovery is required. + refQosData: + type: array + items: + type: string + minItems: 1 + maxItems: 1 + description: > + A reference to the QosData policy decision type. It is the qosId described in + clause 5.6.2.8. + refAltQosParams: + type: array + items: + type: string + minItems: 1 + description: > + A Reference to the QosData policy decision type for the Alternative QoS parameter sets + of the service data flow. + refTcData: + type: array + items: + type: string + minItems: 1 + maxItems: 1 +``` + +``` + +description: > + A reference to the TrafficControlData policy decision type. It is the tcId described in + clause 5.6.2.10. +refChgData: + type: array + items: + type: string + minItems: 1 + maxItems: 1 + description: > + A reference to the ChargingData policy decision type. It is the chgId described in + clause 5.6.2.11. + nullable: true +refChgN3gData: + type: array + items: + type: string + minItems: 1 + maxItems: 1 + description: > + A reference to the ChargingData policy decision type only applicable to Non-3GPP access + if "ATSSS" feature is supported. It is the chgId described in clause 5.6.2.11. + nullable: true +refUmData: + type: array + items: + type: string + minItems: 1 + maxItems: 1 + description: > + A reference to UsageMonitoringData policy decision type. It is the umId described in + clause 5.6.2.12. + nullable: true +refUmN3gData: + type: array + items: + type: string + minItems: 1 + maxItems: 1 + description: > + A reference to UsageMonitoringData policy decision type only applicable to Non-3GPP + access if "ATSSS" feature is supported. It is the umId described in clause 5.6.2.12. + nullable: true +refCondData: + type: string + description: > + A reference to the condition data. It is the condId described in clause 5.6.2.9. + nullable: true +refQosMon: + type: array + items: + type: string + minItems: 1 + maxItems: 1 + description: > + A reference to the QosMonitoringData policy decision type. It is the qmId described in + clause 5.6.2.40. + nullable: true +addrPreserInd: + type: boolean + nullable: true +tscaiInputDl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' +tscaiInputUl: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' +tscaiTimeDom: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' +capBatAdaptation: + type: boolean + description: > + Indicates the capability for AF to adjust the burst sending time, when it is provided + and set to "true". The default value is "false" if omitted. +ddNotifCtrl: + $ref: '#/components/schemas/DownlinkDataNotificationControl' +ddNotifCtrl2: + $ref: '#/components/schemas/DownlinkDataNotificationControlRm' +disUeNotif: + type: boolean + +``` + +``` + + nullable: true + packFiltAllPrec: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + nscSuppFeats: + type: object + additionalProperties: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + minProperties: 1 + description: > + Identifies a list of Network Function Service Consumer supported per service. The key + used in this map for each entry is the ServiceName value as defined in + 3GPP TS 29.510[29]. + callInfo: + $ref: '#/components/schemas/CallInfo' + traffParaData: + $ref: '#/components/schemas/TrafficParaData' + required: + - pccRuleId + nullable: true + + SessionRule: + description: Contains session level policy information. + type: object + properties: + authSessAmbr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ambr' + authDefQos: + $ref: '#/components/schemas/AuthorizedDefaultQos' + sessRuleId: + type: string + description: Univocally identifies the session rule within a PDU session. + refUmData: + type: string + description: > + A reference to UsageMonitoringData policy decision type. It is the umId described in + clause 5.6.2.12. + nullable: true + refUmN3gData: + type: string + description: > + A reference to UsageMonitoringData policy decision type to apply for Non-3GPP access. It + is the umId described in clause 5.6.2.12. + nullable: true + refCondData: + type: string + description: > + A reference to the condition data. It is the condId described in clause 5.6.2.9. + nullable: true + required: + - sessRuleId + nullable: true + + QosData: + description: Contains the QoS parameters. + type: object + properties: + qosId: + type: string + description: Univocally identifies the QoS control policy data within a PDU session. + 5qi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/5Qi' + maxbrUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + maxbrDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + gbrUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + gbrDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + arp: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Arp' + qnc: + type: boolean + description: > + Indicates whether notifications are requested from 3GPP NG-RAN when the GFBR can no +longer + (or again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow. + priorityLevel: + +``` + +``` + + $ref: 'TS29571_CommonData.yaml#/components/schemas/5QiPriorityLevelRm' + averWindow: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindowRm' + maxDataBurstVol: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MaxDataBurstVolRm' + reflectiveQos: + type: boolean + description: > + Indicates whether the QoS information is reflective for the corresponding service data + flow. + sharingKeyDl: + type: string + description: > + Indicates, by containing the same value, what PCC rules may share resource in downlink + direction. + sharingKeyUl: + type: string + description: > + Indicates, by containing the same value, what PCC rules may share resource in uplink + direction. + maxPacketLossRateDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketLossRateRm' + maxPacketLossRateUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketLossRateRm' + defQosFlowIndication: + type: boolean + description: > + Indicates that the dynamic PCC rule shall always have its binding with the QoS Flow + associated with the default QoS rule + extMaxDataBurstVol: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVolRm' + packetDelayBudget: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketDelBudget' + packetErrorRate: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketErrRate' + pduSetQos: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSetQosParaRm' + required: + - qosId + nullable: true + +ConditionData: + description: Contains conditions of applicability for a rule. + type: object + properties: + condId: + type: string + description: Uniquely identifies the condition data within a PDU session. + activationTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTimeRm' + deactivationTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTimeRm' + accessType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' + ratType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' + required: + - condId + nullable: true + +TrafficControlData: + description: > + Contains parameters determining how flows associated with a PCC Rule are treated (e.g. + blocked, redirected, etc). + type: object + properties: + tcId: + type: string + description: Univocally identifies the traffic control policy data within a PDU session. + l4sInd: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/UplinkDownlinkSupport' + flowStatus: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/FlowStatus' + redirectInfo: + $ref: '#/components/schemas/RedirectInformation' + addRedirectInfo: + type: array + items: + +``` + +``` + + $ref: '#/components/schemas/RedirectInformation' + minItems: 1 + muteNotif: + type: boolean + description: Indicates whether application's start or stop notification is to be muted. + trafficSteeringPolIdDl: + type: string + description: > + Reference to a pre-configured traffic steering policy for downlink traffic at the SMF. + nullable: true + trafficSteeringPolIdUl: + type: string + description: > + Reference to a pre-configured traffic steering policy for uplink traffic at the SMF. + nullable: true + metadata: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Metadata' + routeToLocs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RouteToLocation' + minItems: 1 + description: A list of location which the traffic shall be routed to for the AF request + nullable: true + maxAllowedUpLat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UIntegerRm' + easIpReplaceInfos: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/EasIpReplacementInfo' + minItems: 1 + description: Contains EAS IP replacement information. + nullable: true + traffCorreInd: + type: boolean + tfcCorreInfo: + $ref: 'TS29519_Application_Data.yaml#/components/schemas/TrafficCorrelationInfo' + simConnInd: + type: boolean + description: > + Indicates whether simultaneous connectivity should be temporarily maintained for the + source and target PSA. + simConnTerm: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' + upPathChgEvent: + $ref: '#/components/schemas/UpPathChgEvent' + steerFun: + $ref: '#/components/schemas/SteeringFunctionality' + steerModeDl: + $ref: '#/components/schemas/SteeringMode' + steerModeUl: + $ref: '#/components/schemas/SteeringMode' + mulAccCtrl: + $ref: '#/components/schemas/MulticastAccessControl' + candDnaiInd: + type: boolean + description: > + Indication of reporting candidate DNAI(s). If it is included and set to "true", the + candidate DNAI(s) for the PDU session need to be reported. Otherwise set to "false" or + omitted. + datEndMarkInd: + type: boolean + description: > + The data burst end marking is enabled if it is set to "true". Default value is "false" +if + omitted. +required: +- tcId +nullable: true + +ChargingData: + description: Contains charging related parameters. + type: object + properties: + chgId: + type: string + description: Univocally identifies the charging control policy data within a PDU session. + meteringMethod: + +``` + +``` + + $ref: '#/components/schemas/MeteringMethod' + offline: + type: boolean + description: > + Indicates the offline charging is applicable to the PCC rule when it is included and set + to true. + online: + type: boolean + description: > + Indicates the online charging is applicable to the PCC rule when it is included and set + to true. + sdfHandl: + type: boolean + description: > + Indicates whether the service data flow is allowed to start while the SMF is waiting for + the response to the credit request. + ratingGroup: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RatingGroup' + reportingLevel: + $ref: '#/components/schemas/ReportingLevel' + serviceId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ServiceId' + sponsorId: + type: string + description: Indicates the sponsor identity. + appSvcProvId: + type: string + description: Indicates the application service provider identity. + afChargingIdentifier: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ChargingId' + afChargId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ApplicationChargingId' + required: + - chgId + nullable: true + +UsageMonitoringData: + description: Contains usage monitoring related control information. + type: object + properties: + umId: + type: string + description: Univocally identifies the usage monitoring policy data within a PDU session. + volumeThreshold: + $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' + volumeThresholdUplink: + $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' + volumeThresholdDownlink: + $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' + timeThreshold: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + monitoringTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTimeRm' + nextVolThreshold: + $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' + nextVolThresholdUplink: + $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' + nextVolThresholdDownlink: + $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' + nextTimeThreshold: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + inactivityTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + exUsagePccRuleIds: + type: array + items: + type: string + minItems: 1 + description: > + Contains the PCC rule identifier(s) which corresponding service data flow(s) shall be + excluded from PDU Session usage monitoring. It is only included in the + UsageMonitoringData instance for session level usage monitoring. + nullable: true + required: + - umId + nullable: true + +RedirectInformation: + +``` + +``` +description: Contains the redirect information. +type: object +properties: + redirectEnabled: + type: boolean + description: Indicates the redirect is enable. + redirectAddressType: + $ref: '#/components/schemas/RedirectAddressType' + redirectServerAddress: + type: string + description: > + Indicates the address of the redirect server. If "redirectAddressType" attribute + indicates the IPV4_ADDR, the encoding is the same as the Ipv4Addr data type defined in + 3GPP TS 29.571.If "redirectAddressType" attribute indicates the IPV6_ADDR, the encoding + is the same as the Ipv6Addr data type defined in 3GPP TS 29.571.If "redirectAddressType" + attribute indicates the URL or SIP_URI, the encoding is the same as the Uri data type + defined in 3GPP TS 29.571. + +FlowInformation: + description: Contains the flow information. + type: object + properties: + flowDescription: + $ref: '#/components/schemas/FlowDescription' + ethFlowDescription: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EthFlowDescription' + packFiltId: + type: string + description: An identifier of packet filter. + packetFilterUsage: + type: boolean + description: The packet shall be sent to the UE. + tosTrafficClass: + type: string + description: > + Contains the Ipv4 Type-of-Service and mask field or the Ipv6 Traffic-Class field and + mask field. + nullable: true + spi: + type: string + description: the security parameter index of the IPSec packet. + nullable: true + flowLabel: + type: string + description: the Ipv6 flow label header field. + nullable: true + flowDirection: + $ref: '#/components/schemas/FlowDirectionRm' + +SmPolicyDeleteData: + description: > + Contains the parameters to be sent to the PCF when an individual SM policy is deleted. + type: object + properties: + userLocationInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation' + ueTimeZone: + $ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone' + servingNetwork: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' + userLocationInfoTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' + ranNasRelCauses: + type: array + items: + $ref: '#/components/schemas/RanNasRelCause' + minItems: 1 + description: Contains the RAN and/or NAS release cause. + accuUsageReports: + type: array + items: + $ref: '#/components/schemas/AccuUsageReport' + minItems: 1 + description: Contains the usage report + pduSessionRelCause: + $ref: '#/components/schemas/PduSessionRelCause' + +QosCharacteristics: +``` + +``` +description: Contains QoS characteristics for a non-standardized or a non-configured 5QI. +type: object +properties: + 5qi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/5Qi' + resourceType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/QosResourceType' + priorityLevel: + $ref: 'TS29571_CommonData.yaml#/components/schemas/5QiPriorityLevel' + packetDelayBudget: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketDelBudget' + packetErrorRate: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketErrRate' + averagingWindow: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindow' + maxDataBurstVol: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MaxDataBurstVol' + extMaxDataBurstVol: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVol' +required: +- 5qi +- resourceType +- priorityLevel +- packetDelayBudget +- packetErrorRate + +ChargingInformation: +description: Contains the addresses of the charging functions. +type: object +properties: + primaryChfAddress: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + secondaryChfAddress: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + primaryChfSetId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NfSetId' + primaryChfInstanceId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' + secondaryChfSetId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NfSetId' + secondaryChfInstanceId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' +required: +- primaryChfAddress + +AccuUsageReport: +description: Contains the accumulated usage report information. +type: object +properties: + refUmIds: + type: string + description: > + An id referencing UsageMonitoringData objects associated with this usage report. + volUsage: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' + volUsageUplink: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' + volUsageDownlink: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' + timeUsage: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' + nextVolUsage: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' + nextVolUsageUplink: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' + nextVolUsageDownlink: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' + nextTimeUsage: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' +required: +- refUmIds + +SmPolicyUpdateContextData: +description: > + Contains the policy control request trigger(s) that were met and the corresponding new + value(s) or the error report of the policy enforcement. +type: object +properties: +``` + +``` +repPolicyCtrlReqTriggers: + type: array + items: + $ref: '#/components/schemas/PolicyControlRequestTrigger' + minItems: 1 + description: The policy control request triggers which are met. +accNetChIds: + type: array + items: + $ref: '#/components/schemas/AccNetChId' + minItems: 1 + description: > + Indicates the access network charging identifier for the PCC rule(s) or whole PDU + session. +accessType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' +ratType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' +addAccessInfo: + $ref: '#/components/schemas/AdditionalAccessInfo' +relAccessInfo: + $ref: '#/components/schemas/AdditionalAccessInfo' +servingNetwork: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' +userLocationInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation' +ueTimeZone: + $ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone' +relIpv4Address: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' +ipv4Address: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' +ipDomain: + type: string + description: Indicates the IPv4 address domain +ipv6AddressPrefix: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' +relIpv6AddressPrefix: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' +addIpv6AddrPrefixes: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' +addRelIpv6AddrPrefixes: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' +multiIpv6Prefixes: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' + minItems: 1 + description: The multiple allocated IPv6 prefixes of the served UE. +multiRelIpv6Prefixes: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' + minItems: 1 + description: The multiple released IPv6 prefixes of the served UE. +relUeMac: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' +ueMac: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' +subsSessAmbr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ambr' +authProfIndex: + type: string + description: Indicates the DN-AAA authorization profile index +subsDefQos: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SubscribedDefaultQos' +vplmnQos: + $ref: 'TS29502_Nsmf_PDUSession.yaml#/components/schemas/VplmnQos' +vplmnQosNotApp: + type: boolean + description: > + If it is included and set to true, indicates that the QoS constraints in the VPLMN are + not applicable. +numOfPackFilter: + type: integer + description: Contains the number of supported packet filter for signalled QoS rules. +accuUsageReports: + type: array +``` + +``` + items: + $ref: '#/components/schemas/AccuUsageReport' + minItems: 1 + description: Contains the usage report +3gppPsDataOffStatus: + type: boolean + description: > + If it is included and set to true, the 3GPP PS Data Off is activated by the UE. +appDetectionInfos: + type: array + items: + $ref: '#/components/schemas/AppDetectionInfo' + minItems: 1 + description: > + Report the start/stop of the application traffic and detected SDF descriptions + if applicable. +ruleReports: + type: array + items: + $ref: '#/components/schemas/RuleReport' + minItems: 1 + description: Used to report the PCC rule failure. +sessRuleReports: + type: array + items: + $ref: '#/components/schemas/SessionRuleReport' + minItems: 1 + description: Used to report the session rule failure. +qncReports: + type: array + items: + $ref: '#/components/schemas/QosNotificationControlInfo' + minItems: 1 + description: QoS Notification Control information. +qosMonReports: + type: array + items: + $ref: '#/components/schemas/QosMonitoringReport' + minItems: 1 +qosMonDatRateReps: + type: array + items: + $ref: '#/components/schemas/QosMonitoringReport' + minItems: 1 +userLocationInfoTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' +repPraInfos: + type: object + additionalProperties: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PresenceInfo' + minProperties: 1 + description: > + Reports the changes of presence reporting area. The praId attribute within the + PresenceInfo data type is the key of the map. +ueInitResReq: + $ref: '#/components/schemas/UeInitiatedResourceRequest' +refQosIndication: + type: boolean + description: > + If it is included and set to true, the reflective QoS is supported by the UE. If it is + included and set to false, the reflective QoS is revoked by the UE. +qosFlowUsage: + $ref: '#/components/schemas/QosFlowUsage' +creditManageStatus: + $ref: '#/components/schemas/CreditManagementStatus' +servNfId: + $ref: '#/components/schemas/ServingNfIdentity' +traceReq: + $ref: 'TS29571_CommonData.yaml#/components/schemas/TraceData' +maPduInd: + $ref: '#/components/schemas/MaPduIndication' +atsssCapab: + $ref: '#/components/schemas/AtsssCapability' +tsnBridgeInfo: + $ref: '#/components/schemas/TsnBridgeInfo' +tsnBridgeManCont: + $ref: '#/components/schemas/BridgeManagementContainer' +tsnPortManContDstt: +``` + +``` +$ref: '#/components/schemas/PortManagementContainer' +tsnPortManContNwttts: + type: array + items: + $ref: '#/components/schemas/PortManagementContainer' + minItems: 1 +tscNotifUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' +tscNotifCorreId: + type: string + description: > + Correlation identifier for TSC management information notifications. +mulAddrInfos: + type: array + items: + $ref: '#/components/schemas/IpMulticastAddressInfo' + minItems: 1 +policyDecFailureReports: + type: array + items: + $ref: '#/components/schemas/PolicyDecisionFailureCode' + minItems: 1 + description: Contains the type(s) of failed policy decision and/or condition data. +invalidPolicyDecs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/InvalidParam' + minItems: 1 + description: > + Indicates the invalid parameters for the reported type(s) of the failed policy decision + and/or condition data. +trafficDescriptors: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DddTrafficDescriptor' + minItems: 1 +pccRuleId: + type: string + description: > + Contains the identifier of the PCC rule which is used for traffic detection of event. +typesOfNotif: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DlDataDeliveryStatus' + minItems: 1 +interGrpIds: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/GroupId' + minItems: 1 +satBackhaulCategory: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SatelliteBackhaulCategory' +pcfUeInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PcfUeCallbackInfo' +nwdafData: + type: array + items: + $ref: '#/components/schemas/NwdafData' + minItems: 1 + nullable: true +anGwStatus: + type: boolean + description: > + When it is included and set to true, it indicates that the AN-Gateway has failed and + that the PCF should refrain from sending policy decisions to the SMF until it is + informed that the AN-Gateway has been recovered. +uePolCont: + $ref: '#/components/schemas/UePolicyContainer' +urspEnfInfo: + $ref: '#/components/schemas/UrspEnforcementInfo' +sscMode: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SscMode' +ueReqDnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' +redundantPduSessionInfo: + $ref: 'TS29502_Nsmf_PDUSession.yaml#/components/schemas/RedundantPduSessionInformation' +l4sReports: + type: array +``` + +``` + + items: + $ref: '#/components/schemas/L4sSupportInfo' + minItems: 1 + description: ECN marking for L4S support availability in 5GS. + sliceInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai' + batOffsetInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/BatOffsetInfo' + hrsboInd: + type: boolean + description: > + HR-SBO support indication. If present and set to "true", it indicates that the HR-SBO is + supported. If present and set to "false", it indicates that the HR-SBO is not supported. + allOf: + - not: + - required: [multiIpv6Prefixes, ipv6AddressPrefix] + - not: + - required: [multiIpv6Prefixes, addIpv6AddrPrefixes] + - not: + - required: [multiRelIpv6Prefixes, relIpv6AddressPrefix] + - not: + - required: [multiRelIpv6Prefixes, relAddIpv6AddrPrefixes] + +UpPathChgEvent: + description: Contains the UP path change event subscription from the AF. + type: object + properties: + notificationUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + notifCorreId: + type: string + description: > + It is used to set the value of Notification Correlation ID in the notification sent by + the SMF. + dnaiChgType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DnaiChangeType' + afAckInd: + type: boolean + required: + - notificationUri + - notifCorreId + - dnaiChgType + nullable: true + +TerminationNotification: + description: Represents a Termination Notification. + type: object + properties: + resourceUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + cause: + $ref: '#/components/schemas/SmPolicyAssociationReleaseCause' + required: + - resourceUri + - cause + +AppDetectionInfo: + description: Contains the detected application's traffic information. + type: object + properties: + appId: + type: string + description: A reference to the application detection filter configured at the UPF + instanceId: + type: string + description: > + Identifier sent by the SMF in order to allow correlation of application Start and Stop + events to the specific service data flow description, if service data flow descriptions + are deducible. + sdfDescriptions: + type: array + items: + $ref: '#/components/schemas/FlowInformation' + minItems: 1 + description: Contains the detected service data flow descriptions if they are deducible. + required: + - appId + +``` + +``` +AccNetChId: + description: > + Contains the access network charging identifier for the PCC rule(s) or for the whole + PDU session. + type: object + properties: + accNetChaIdValue: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ChargingId' + accNetChargId: + type: string + description: A character string containing the access network charging id. + refPccRuleIds: + type: array + items: + type: string + minItems: 1 + description: > + Contains the identifier of the PCC rule(s) associated to the provided Access Network + Charging Identifier. + sessionChScope: + type: boolean + description: > + When it is included and set to true, indicates the Access Network Charging Identifier + applies to the whole PDU Session + oneOf: + - required: [accNetChaIdValue] + - required: [accNetChargId] + +AccNetChargingAddress: + description: Describes the network entity within the access network performing charging + type: object + anyOf: + - required: [anChargIpv4Addr] + - required: [anChargIpv6Addr] + properties: + anChargIpv4Addr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' + anChargIpv6Addr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr' + +RequestedRuleData: + description: > + Contains rule data requested by the PCF to receive information associated with PCC rule(s). + type: object + properties: + refPccRuleIds: + type: array + items: + type: string + minItems: 1 + description: > + An array of PCC rule id references to the PCC rules associated with the control data. + reqData: + type: array + items: + $ref: '#/components/schemas/RequestedRuleDataType' + minItems: 1 + description: > + Array of requested rule data type elements indicating what type of rule data is + requested for the corresponding referenced PCC rules. + required: + - refPccRuleIds + - reqData + +RequestedUsageData: + description: > + Contains usage data requested by the PCF requesting usage reports for the corresponding + usage monitoring data instances. + type: object + properties: + refUmIds: + type: array + items: + type: string + minItems: 1 + description: > + An array of usage monitoring data id references to the usage monitoring data instances + for which the PCF is requesting a usage report. This attribute shall only be provided +``` + +``` + + when allUmIds is not set to true. + allUmIds: + type: boolean + description: > + This boolean indicates whether requested usage data applies to all usage monitoring data + instances. When it's not included, it means requested usage data shall only apply to the + usage monitoring data instances referenced by the refUmIds attribute. + + UeCampingRep: + description: > + Contains the current applicable values corresponding to the policy control request triggers. + type: object + properties: + accessType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' + ratType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' + servNfId: + $ref: '#/components/schemas/ServingNfIdentity' + servingNetwork: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' + userLocationInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation' + ueTimeZone: + $ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone' + netLocAccSupp: + $ref: '#/components/schemas/NetLocAccessSupport' + satBackhaulCategory: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SatelliteBackhaulCategory' + urspEnfInfo: + $ref: '#/components/schemas/UrspEnforcementInfo' + sscMode: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ScsMode' + ueReqDnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' + redundantPduSessionInfo: + $ref: 'TS29502_Nsmf_PDUSession.yaml#/components/schemas/RedundantPduSessionInformation' + + RuleReport: + description: Reports the status of PCC. + type: object + properties: + pccRuleIds: + type: array + items: + type: string + minItems: 1 + description: Contains the identifier of the affected PCC rule(s). + ruleStatus: + $ref: '#/components/schemas/RuleStatus' + contVers: + type: array + items: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ContentVersion' + minItems: 1 + description: Indicates the version of a PCC rule. + failureCode: + $ref: '#/components/schemas/FailureCode' + retryAfter: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger' + finUnitAct: + $ref: 'TS32291_Nchf_ConvergedCharging.yaml#/components/schemas/FinalUnitAction' + ranNasRelCauses: + type: array + items: + $ref: '#/components/schemas/RanNasRelCause' + minItems: 1 + description: indicates the RAN or NAS release cause code information. + altQosParamId: + type: string + description: > + Indicates the alternative QoS parameter set that the NG-RAN can guarantee. It is + included during the report of successful resource allocation and indicates that NG-RAN + used an alternative QoS profile because the requested QoS could not be allocated.. + required: + - pccRuleIds + - ruleStatus + +``` + +``` +RanNasRelCause: + description: Contains the RAN/NAS release cause. + type: object + properties: + ngApCause: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NgApCause' + 5gMmCause: + $ref: 'TS29571_CommonData.yaml#/components/schemas/5GMmCause' + 5gSmCause: + $ref: '#/components/schemas/5GSmCause' + epsCause: + $ref: '#/components/schemas/EpsRanNasRelCause' + +UeInitiatedResourceRequest: + description: Indicates that a UE requests specific QoS handling for the selected SDF. + type: object + properties: + pccRuleId: + type: string + ruleOp: + $ref: '#/components/schemas/RuleOperation' + precedence: + type: integer + packFiltInfo: + type: array + items: + $ref: '#/components/schemas/PacketFilterInfo' + minItems: 1 + reqQos: + $ref: '#/components/schemas/RequestedQos' + required: + - ruleOp + - packFiltInfo + +PacketFilterInfo: + description: > + Contains the information from a single packet filter sent from the SMF to the PCF. + type: object + properties: + packFiltId: + type: string + description: An identifier of packet filter. + packFiltCont: + $ref: '#/components/schemas/PacketFilterContent' + tosTrafficClass: + type: string + description: > + Contains the Ipv4 Type-of-Service and mask field or the Ipv6 Traffic-Class field and + mask field. + spi: + type: string + description: The security parameter index of the IPSec packet. + flowLabel: + type: string + description: The Ipv6 flow label header field. + flowDirection: + $ref: '#/components/schemas/FlowDirection' + +RequestedQos: + description: Contains the QoS information requested by the UE. + type: object + properties: + 5qi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/5Qi' + gbrUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + gbrDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + required: + - 5qi + +QosNotificationControlInfo: + description: Contains the QoS Notification Control Information. + type: object + properties: + refPccRuleIds: + type: array + items: +``` + +``` + type: string + minItems: 1 + description: > + An array of PCC rule id references to the PCC rules associated with the QoS notification + control info. + notifType: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/QosNotifType' + contVer: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ContentVersion' + altQosParamId: + type: string + description: > + Indicates the alternative QoS parameter set the NG-RAN can guarantee. When it is omitted + and the notifType attribute is set to NOT_GUARANTEED it indicates that the lowest + priority alternative QoS profile could not be fulfilled. + altQosNotSuppInd: + type: boolean + description: > + When present and set to true it indicates that the Alternative QoS profiles are not + supported by NG-RAN. + required: + - refPccRuleIds + - notifType + + PartialSuccessReport: + description: > + Includes the information reported by the SMF when some of the PCC rules and/or session rules + and/or policy decision and/or condition data are not successfully installed/activated or + stored. + type: object + properties: + failureCause: + $ref: '#/components/schemas/FailureCause' + ruleReports: + type: array + items: + $ref: '#/components/schemas/RuleReport' + minItems: 1 + description: > + Information about the PCC rules provisioned by the PCF not successfully + installed/activated. + sessRuleReports: + type: array + items: + $ref: '#/components/schemas/SessionRuleReport' + minItems: 1 + description: > + Information about the session rules provisioned by the PCF not successfully installed. + ueCampingRep: + $ref: '#/components/schemas/UeCampingRep' + policyDecFailureReports: + type: array + items: + $ref: '#/components/schemas/PolicyDecisionFailureCode' + minItems: 1 + description: Contains the type(s) of failed policy decision and/or condition data. + invalidPolicyDecs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/InvalidParam' + minItems: 1 + description: > + Indicates the invalid parameters for the reported type(s) of the failed policy decision + and/or condition data. + required: + - failureCause + + AuthorizedDefaultQos: + description: Represents the Authorized Default QoS. + type: object + properties: + 5qi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/5Qi' + arp: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Arp' + priorityLevel: + $ref: 'TS29571_CommonData.yaml#/components/schemas/5QiPriorityLevelRm' + averWindow: +``` + +``` +$ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindowRm' +maxDataBurstVol: +$ref: 'TS29571_CommonData.yaml#/components/schemas/MaxDataBurstVolRm' +maxbrUl: +$ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' +maxbrDl: +$ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' +gbrUl: +$ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' +gbrDl: +$ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' +extMaxDataBurstVol: +$ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVolRm' + +ErrorReport: + description: Contains the rule,policy decision and/or condition data error reports. + type: object + properties: + error: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ProblemDetails' + ruleReports: + type: array + items: + $ref: '#/components/schemas/RuleReport' + minItems: 1 + description: Used to report the PCC rule failure. + sessRuleReports: + type: array + items: + $ref: '#/components/schemas/SessionRuleReport' + minItems: 1 + description: Used to report the session rule failure. + polDecFailureReports: + type: array + items: + $ref: '#/components/schemas/PolicyDecisionFailureCode' + minItems: 1 + description: Used to report failure of the policy decision and/or condition data. + invalidPolicyDecs: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/InvalidParam' + minItems: 1 + description: > + Indicates the invalid parameters for the reported type(s) of the failed policy decision + and/or condition data. + +SessionRuleReport: + description: Represents reporting of the status of a session rule. + type: object + properties: + ruleIds: + type: array + items: + type: string + minItems: 1 + description: Contains the identifier of the affected session rule(s). + ruleStatus: + $ref: '#/components/schemas/RuleStatus' + sessRuleFailureCode: + $ref: '#/components/schemas/SessionRuleFailureCode' + policyDecFailureReports: + type: array + items: + $ref: '#/components/schemas/PolicyDecisionFailureCode' + minItems: 1 + description: Contains the type(s) of failed policy decision and/or condition data. + required: + - ruleIds + - ruleStatus + +ServingNfIdentity: + description: Contains the serving Network Function identity. + type: object + properties: + servNfInstId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' + guami: +``` + +``` + $ref: 'TS29571_CommonData.yaml#/components/schemas/Guami' + anGwAddr: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AnGwAddress' + sgsnAddr: + $ref: '#/components/schemas/SgsnAddress' + +SteeringMode: + description: Contains the steering mode value and parameters determined by the PCF. + type: object + properties: + steerModeValue: + $ref: '#/components/schemas/SteerModeValue' + active: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' + standby: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessTypeRm' + 3gLoad: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + prioAcc: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' + thresValue: + $ref: '#/components/schemas/ThresholdValue' + steerModeInd: + $ref: '#/components/schemas/SteerModeIndicator' + primary: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessTypeRm' + + required: + - steerModeValue + +AdditionalAccessInfo: + description: > + Indicates the combination of additional Access Type and RAT Type for a MA PDU session. + type: object + properties: + accessType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' + ratType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' + required: + - accessType + +QosMonitoringData: + description: Contains QoS monitoring related control information. + type: object + properties: + qmId: + type: string + description: Univocally identifies the QoS monitoring policy data within a PDU session. + reqQosMonParams: + type: array + items: + $ref: '#/components/schemas/RequestedQosMonitoringParameter' + minItems: 1 + description: > + indicates the QoS information to be monitored when the QoS Monitoring is enabled for + the service data flow. + repFreqs: + type: array + items: + $ref: '#/components/schemas/ReportingFrequency' + minItems: 1 + repThreshDl: + type: integer + description: Indicates the period of time in units of milliseconds for DL packet delay. + nullable: true + repThreshUl: + type: integer + description: Indicates the period of time in units of milliseconds for UL packet delay. + nullable: true + repThreshRp: + type: integer + description: > + Indicates the period of time in units of milliseconds for round trip packet delay. + nullable: true + conThreshDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + nullable: true +``` + +``` + + conThreshUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + nullable: true + waitTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + repPeriod: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + notifyUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UriRm' + notifyCorreId: + type: string + nullable: true + directNotifInd: + type: boolean + description: > + Indicates that the direct event notification sent by UPF to the Local NEF or AF is + requested if it is included and set to true. + avrgWndw: + $ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindowRm' + repThreshDatRateUl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + repThreshDatRateDl: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' + dataCollAppId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ApplicationId' + required: + - qmId + - reqQosMonParams + - repFreqs + nullable: true + + QosMonitoringReport: + description: Contains reporting information on QoS monitoring. + type: object + properties: + refPccRuleIds: + type: array + items: + type: string + minItems: 1 + description: > + An array of PCC rule id references to the PCC rules associated with the QoS monitoring + report. + ulDelays: + type: array + items: + type: integer + minItems: 1 + dlDelays: + type: array + items: + type: integer + minItems: 1 + rtDelays: + type: array + items: + type: integer + minItems: 1 + pdmf: + type: boolean + description: Represents the packet delay measurement failure indicator. + ulDataRate: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + dlDataRate: + $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' + ulCongInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + dlCongInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + cimf: + type: boolean + description: > + Congestion information measurement failure indicator. When set to true, it indicates + that a congestion information failure has occurred. Default value is false if omitted. + required: + - refPccRuleIds + +# +TsnBridgeInfo: + +``` + +``` +description: Contains parameters that describe and identify the TSC user plane node. +type: object +properties: + bridgeId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uint64' + dsttAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' + dsttPortNum: + $ref: '#/components/schemas/TsnPortNumber' + dsttResidTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + mtuIpv4: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uint16' + mtuIpv6: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uint32' +# +PortManagementContainer: + description: Contains the port management information container for a port. + type: object + properties: + portManCont: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Bytes' + portNum: + $ref: '#/components/schemas/TsnPortNumber' + required: + - portManCont + - portNum +BridgeManagementContainer: + description: Contains the UMIC. + type: object + properties: + bridgeManCont: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Bytes' + required: + - bridgeManCont +IpMulticastAddressInfo: + description: Contains the IP multicast addressing information. + type: object + properties: + srcIpv4Addr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' + ipv4MulAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' + srcIpv6Addr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr' + ipv6MulAddr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr' +DownlinkDataNotificationControl: + description: Contains the downlink data notification control information. + type: object + properties: + notifCtrlInds: + type: array + items: + $ref: '#/components/schemas/NotificationControlIndication' + minItems: 1 + typesOfNotif: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DlDataDeliveryStatus' + minItems: 1 +DownlinkDataNotificationControlRm: + description: > + This data type is defined in the same way as the DownlinkDataNotificationControl data type, + but with the nullable:true property. + type: object + properties: + notifCtrlInds: + type: array + items: + $ref: '#/components/schemas/NotificationControlIndication' + minItems: 1 + nullable: true + typesOfNotif: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DlDataDeliveryStatus' + minItems: 1 +``` + +``` + nullable: true + thresholdValue: + description: Indicates the threshold value(s) for RTT and/or Packet Loss Rate. + type: object + properties: + rttThres: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UIntegerRm' + plrThres: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketLossRateRm' + nullable: true + NwdafData: + description: > + Indicates the list of Analytic ID(s) per NWDAF instance ID used for the PDU Session consumed + by the SMF. + type: object + properties: + nwdafInstanceId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' + nwdafEvents: + type: array + items: + $ref: 'TS29520_Nnwdaf_EventsSubscription.yaml#/components/schemas/NwdafEvent' + minItems: 1 + required: + - nwdafInstanceId + + CallInfo: + description: Identifies the caller and callee information. + type: object + properties: + callingPartyAddrs: + type: array + items: + type: string + minItems: 1 + calleeInfo: + $ref: '#/components/schemas/CalleeInfo' + nullable: true + + CalleeInfo: + description: Identifies the callee information. + type: object + properties: + calledPartyAddr: + type: string + requestPartyAddrs: + type: array + items: + type: string + minItems: 1 + calledAssertIds: + type: array + items: + type: string + minItems: 1 + nullable: true + +# +TrafficParaData: + description: Contains Traffic Parameter(s) related control information. + type: object + properties: + periodInfo: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/PeriodicityInfo' + reqTrafficParas: + type: array + items: + $ref: '#/components/schemas/TrafficParameterMeas' + minItems: 1 + description: Indicates the traffic parameters to be measured. + repFreqs: + type: array + items: + $ref: '#/components/schemas/ReportingFrequency' + minItems: 1 + description: Represents the notification method (periodic or on event detection). + dlN6JitterThr: +``` + +``` + + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + repPeriod: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + required: + - reqTrafficParas + +L4sSupportInfo: + description: Contains the ECN marking for L4S support in 5GS information. + type: object + properties: + refPccRuleIds: + type: array + items: + type: string + minItems: 1 + description: > + An array of PCC rule id references to the PCC rules associated with the ECN marking + for L4S support info. + notifType: + $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/L4sNotifType' + required: + - refPccRuleIds + - notifType + +SliceUsgCtrlInfo: + description: Represents network slice usage control information. + type: object + properties: + pduSessInactivTimer: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + +5GSmCause: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' +EpsRanNasRelCause: + type: string + description: Defines the EPS RAN/NAS release cause. +PacketFilterContent: + type: string + description: Defines a packet filter for an IP flow. +FlowDescription: + type: string + description: Defines a packet filter for an IP flow. +TsnPortNumber: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' +ApplicationDescriptor: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Bytes' +UePolicyContainer: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Bytes' +UrspEnforcementInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Bytes' + +FlowDirection: + anyOf: + - type: string + enum: + - DOWNLINK + - UPLINK + - BIDIRECTIONAL + - UNSPECIFIED + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration and is not used to encode + content defined in the present version of this API. + description: | + Indicates the direction of the service data flow. + Possible values are: + - DOWNLINK: The corresponding filter applies for traffic to the UE. + - UPLINK: The corresponding filter applies for traffic from the UE. + - BIDIRECTIONAL: The corresponding filter applies for traffic both to and from the UE. + - UNSPECIFIED: The corresponding filter applies for traffic to the UE (downlink), but has no + specific direction declared. The service data flow detection shall apply the filter for + uplink traffic as if the filter was bidirectional. The PCF shall not use the value + UNSPECIFIED in filters created by the network in NW-initiated procedures. The PCF shall only + include the value UNSPECIFIED in filters in UE-initiated procedures if the same value is + received from the SMF. + +``` + +``` +FlowDirectionRm: + description: > + This data type is defined in the same way as the "FlowDirection" data type, with the only + difference that it allows null value. + anyOf: + - $ref: '#/components/schemas/FlowDirection' + - $ref: 'TS29571_CommonData.yaml#/components/schemas/NullValue' + +ReportingLevel: + anyOf: + - type: string + enum: + - SER_ID_LEVEL + - RAT_GR_LEVEL + - SPON_CON_LEVEL + - $ref: 'TS29571_CommonData.yaml#/components/schemas/NullValue' + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration and is not used to encode + content defined in the present version of this API. + description: | + Indicates the reporting level. + Possible values are: + - SER_ID_LEVEL: Indicates that the usage shall be reported on service id and rating group + combination level. + - RAT_GR_LEVEL: Indicates that the usage shall be reported on rating group level. + - SPON_CON_LEVEL: Indicates that the usage shall be reported on sponsor identity and rating + group combination level. + +MeteringMethod: + anyOf: + - type: string + enum: + - DURATION + - VOLUME + - DURATION_VOLUME + - EVENT + - $ref: 'TS29571_CommonData.yaml#/components/schemas/NullValue' + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration and is not used to encode + content defined in the present version of this API. + description: | + Indicates the metering method. + Possible values are: + - DURATION: Indicates that the duration of the service data flow traffic shall be metered. + - VOLUME: Indicates that volume of the service data flow traffic shall be metered. + - DURATION_VOLUME: Indicates that the duration and the volume of the service data flow + traffic shall be metered. + - EVENT: Indicates that events of the service data flow traffic shall be metered. + +PolicyControlRequestTrigger: + anyOf: + - type: string + enum: + - PLMN_CH + - RES_MO_RE + - AC_TY_CH + - UE_IP_CH + - UE_MAC_CH + - AN_CH_COR + - US_RE + - APP_STA + - APP_STO + - AN_INFO + - CM_SES_FAIL + - PS_DA_OFF + - DEF_QOS_CH + - SE_AMBR_CH + - QOS_NOTIF + - NO_CREDIT + - REALLO_OF_CREDIT + - PRA_CH + - SAREA_CH + - SCNN_CH + - RE_TIMEOUT +``` + +``` + +- RES_RELEASE +- SUCC_RES_ALLO +- RAI_CH +- RAT TY_CH +- REF_QOS_IND_CH +- NUM_OF_PACKET_FILTER +- UE_STATUS_RESUME +- UE_TZ_CH +- AUTH_PROF_CH +- QOS_MONITORING +- SCELL_CH +- USER_LOCATION_CH +- EPS_FALLBACK +- MA_PDU +- TSN_BRIDGE_INFO +- 5G_RG_JOIN +- 5G_RG_LEAVE +- DDN_FAILURE +- DDN_DELIVERY_STATUS +- GROUP_ID_LIST_CHG +- DDN_FAILURE_CANCELLATION +- DDN_DELIVERY_STATUS_CANCELLATION +- VPLMN_QOS_CH +- SUCC_QOS_UPDATE +- SAT_CATEGORY_CHG +- PCF_UE_NOTIF_IND +- NWDAF_DATA_CHG +- UE_POL_CONT_IND +- URSP_ENFORCEMENT_INFO +- HR_SBO_IND_CHG +- L4S_SUPP +- NET_SLICE_REPL +- BAT_OFFSET_INFO +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration and is not used to encode + content defined in the present version of this API. + description: | + Indicates the policy control request trigger(s). + Possible values are: + - PLMN CH: PLMN Change + - RES_MO_RE: A request for resource modification has been received by the SMF. The SMF + always reports to the PCF. + - AC TY_CH: Access Type Change. + - UE_IP_CH: UE IP address change. The SMF always reports to the PCF. + - UE_MAC_CH: A new UE MAC address is detected or a used UE MAC address is inactive for a + specific period. + - AN_CH_COR: Access Network Charging Correlation Information + - US_RE: The PDU Session or the Monitoring key specific resources consumed by a UE either + reached the threshold or needs to be reported for other reasons. + - APP_STA: The start of application traffic has been detected. + - APP_STO: The stop of application traffic has been detected. + - AN_INFO: Access Network Information report. + - CM_SES_FAIL: Credit management session failure. + - PS_DA_OFF: The SMF reports when the 3GPP PS Data Off status changes. The SMF always + reports to the PCF. + - DEF_QOS_CH: Default QoS Change. The SMF always reports to the PCF. + - SE_AMBR_CH: Session-AMBR Change. The SMF always reports to the PCF. + - QOS_NOTIF: The SMF notify the PCF when receiving notification from RAN that QoS targets of + the QoS Flow cannot be guaranteed or gurated again. + - NO_CREDIT: Out of credit. + - REALLO_OF_CREDIT: Reallocation of credit. + - PRA_CH: Change of UE presence in Presence Reporting Area. + - SAREA_CH: Location Change with respect to the Serving Area. + - SCNN_CH: Location Change with respect to the Serving CN node. + - RE_TIMEOUT: Indicates the SMF generated the request because there has been a PCC + revalidation timeout. + - RES_RELEASE: Indicate that the SMF can inform the PCF of the outcome of the release of + resources for those rules that require so. + - SUCC_RES_ALLO: Indicates that the requested rule data is the successful resource + allocation. + - RAI_CH: Location Change with respect to the RAI of GERAN and UTRAN. + - RAT TY_CH: RAT Type Change. + - REF_QOS_IND_CH: Reflective QoS indication Change + - NUM_OF_PACKET_FILTER: Indicates that the SMF shall report the number of supported packet + filter for signalled QoS rules. + - UE_STATUS_RESUME: Indicates that the UE's status is resumed. + +``` + +- UE\_TZ\_CH: UE Time Zone Change. +- AUTH\_PROF\_CH: The DN-AAA authorization profile index has changed. +- QOS\_MONITORING: Indicate that the SMF notifies the PCF of the QoS Monitoring information. +- SCELL\_CH: Location Change with respect to the Serving Cell. +- USER\_LOCATION\_CH: Indicate that user location has been changed, applicable to serving area change and serving cell change. +- EPS\_FALLBACK: EPS Fallback report is enabled in the SMF. +- MA\_PDU: UE Indicates that the SMF notifies the PCF of the MA PDU session request. +- TSN\_BRIDGE\_INFO: TSC user plane node information available. +- 5G\_RG\_JOIN: The 5G-RG has joined to an IP Multicast Group. +- 5G\_RG\_LEAVE: The 5G-RG has left an IP Multicast Group. +- DDN\_FAILURE: Event subscription for DDN Failure event received. +- DDN\_DELIVERY\_STATUS: Event subscription for DDN Delivery Status received. +- GROUP\_ID\_LIST\_CHG: UE Internal Group Identifier(s) has changed: the SMF reports that UDM provided list of group Ids has changed. +- DDN\_FAILURE\_CANCELLATION: The event subscription for DDN Failure event is cancelled. +- DDN\_DELIVERY\_STATUS\_CANCELLATION: The event subscription for DDN STATUS is cancelled. +- VPLMN\_QOS\_CH: Change of the QoS supported in the VPLMN. +- SUCC\_QOS\_UPDATE: Indicates that the requested MPS Action is successful. +- SAT\_CATEGORY\_CHG: Indicates that the SMF has detected a change between different satellite backhaul categories, or between a satellite backhaul and a non-satellite backhaul. +- PCF\_UE\_NOTIF\_IND: Indicates the SMF has detected the AMF forwarded the PCF for the UE indication to receive/stop receiving notifications of SM Policy association established/terminated events. +- NWDAF\_DATA\_CHG: Indicates that the NWDAF instance IDs used for the PDU session and/or associated Analytics IDs used for the PDU session and available in the SMF have changed. +- UE\_POL\_CONT\_IND: Indicates that a UE policy container is received from the UE in EPC over a PDN connection. +- URSP\_ENFORCEMENT\_INFO: Indicates a report of URSP rule enforcement information. +- HR\_SBO\_IND\_CHG: Indicates the HR-SBO support indication has changed. +- L4S\_SUPP: Indicates whether ECN marking for L4S is not available or available again in 5GS. +- NET\_SLICE\_REPL: Indicates network slice replacement, i.e., a change between the initial S-NSSAI of the PDU Session and the Alternative S-NSSAI +- BAT\_OFFSET\_INFO: Indicates that the SMF has detected the BAT offset and optionally adjusted periodicity. + +RequestedRuleDataType: + +anyOf: + +- type: string + - enum: + - CH\_ID + - MS\_TIME\_ZONE + - USER\_LOC\_INFO + - RES\_RELEASE + - SUCC\_RES\_ALLO + - EPS\_FALLBACK +- type: string + - description: > + + +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +description: | + +Indicates the type of rule data requested by the PCF. + +Possible values are: + +- CH\_ID: Indicates that the requested rule data is the charging identifier. +- MS\_TIME\_ZONE: Indicates that the requested access network info type is the UE's timezone. +- USER\_LOC\_INFO: Indicates that the requested access network info type is the UE's location. +- RES\_RELEASE: Indicates that the requested rule data is the result of the release of resource. +- SUCC\_RES\_ALLO: Indicates that the requested rule data is the successful resource allocation. +- EPS\_FALLBACK: Indicates that the requested rule data is the report of QoS flow rejection due to EPS fallback. + +RuleStatus: + +anyOf: + +- type: string + - enum: + - ACTIVE + - INACTIVE +- type: string + - description: > + + +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +description: | + +Indicates the status of PCC or session rule. + +Possible values are + +- ACTIVE: Indicates that the PCC rule(s) are successfully installed (for those provisioned from PCF) or activated (for those pre-defined in SMF), or the session rule(s) are successfully installed +- INACTIVE: Indicates that the PCC rule(s) are removed (for those provisioned from PCF) or inactive (for those pre-defined in SMF) or the session rule(s) are removed. + +FailureCode: + +anyOf: + +- type: string + +enum: + +- UNK\_RULE\_ID +- RA\_GR\_ERR +- SER\_ID\_ERR +- NF\_MAL +- RES\_LIM +- MAX\_NR\_QoS\_FLOW +- MISS\_FLOW\_INFO +- RES\_ALLO\_FAIL +- UNSUCC\_QoS\_VAL +- INCOR\_FLOW\_INFO +- PS\_TO\_CS\_HAN +- APP\_ID\_ERR +- NO\_QoS\_FLOW\_BOUND +- FILTER\_RES +- MISS\_REDI\_SER\_ADDR +- CM\_END\_USER\_SER\_DENIED +- CM\_CREDIT\_CON\_NOT\_APP +- CM\_AUTH\_REJ +- CM\_USER\_UNK +- CM\_RAT\_FAILED +- UE\_STA\_SUSP +- UNKNOWN\_REF\_ID +- INCORRECT\_COND\_DATA +- REF\_ID\_COLLISION +- TRAFFIC\_STEERING\_ERROR +- DNAI\_STEERING\_ERROR +- AN\_GW\_FAIL +- MAX\_NR\_PACKET\_FILTERS\_EXCEEDED +- PACKET\_FILTER\_TFT\_ALLOCATION\_EXCEEDED +- MUTE\_CHG\_NOT\_ALLOWED +- UE\_TEMPORARILY\_UNAVAILABLE + +- type: string + +description: > + +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +description: | + +Indicates the reason of the PCC rule failure. + +Possible values are + +- UNK\_RULE\_ID: Indicates that the pre-provisioned PCC rule could not be successfully activated because the PCC rule identifier is unknown to the SMF. +- RA\_GR\_ERR: Indicate that the PCC rule could not be successfully installed or enforced because the Rating Group specified within the Charging Data policy decision which the PCC rule refers to is unknown or, invalid. +- SER\_ID\_ERR: Indicate that the PCC rule could not be successfully installed or enforced because the Service Identifier specified within the Charging Data policy decision which the PCC rule refers to is invalid, unknown, or not applicable to the service being charged. +- NF\_MAL: Indicate that the PCC rule could not be successfully installed (for those provisioned from the PCF) or activated (for those pre-defined in SMF) or enforced (for those already successfully installed) due to SMF/UPF malfunction. +- RES\_LIM: Indicate that the PCC rule could not be successfully installed (for those provisioned from PCF) or activated (for those pre-defined in SMF) or enforced (for those already successfully installed) due to a limitation of resources at the SMF/UPF. +- MAX\_NR\_QoS\_FLOW: Indicate that the PCC rule could not be successfully installed (for those provisioned from PCF) or activated (for those pre-defined in SMF) or enforced (for those already successfully installed) due to the fact that the maximum number of QoS flows has been reached for the PDU session. +- MISS\_FLOW\_INFO: Indicate that the PCC rule could not be successfully installed or enforced because neither the "flowInfos" attribute nor the "appId" attribute is specified within the PccRule data structure by the PCF during the first install request of the PCC rule. +- RES\_ALLO\_FAIL: Indicate that the PCC rule could not be successfully installed or maintained since the QoS flow establishment/modification failed, or the QoS flow was released. +- UNSUCC\_QoS\_VAL: indicate that the QoS validation has failed or when Guaranteed Bandwidth > Max-Requested-Bandwidth. +- INCOR\_FLOW\_INFO: Indicate that the PCC rule could not be successfully installed or modified at the SMF because the provided flow information is not supported by the network + +(e.g. the provided IP address(es) or Ipv6 prefix(es) do not correspond to an IP version applicable for the PDU session). + +- PS\_TO\_CS\_HAN: Indicate that the PCC rule could not be maintained because of PS to CS handover. + +- APP\_ID\_ERR: Indicate that the rule could not be successfully installed or enforced because the Application Identifier is invalid, unknown, or not applicable to the application required for detection. + +- NO\_QOS\_FLOW\_BOUND: Indicate that there is no QoS flow which the SMF can bind the PCC rule(s) to. + +- FILTER\_RES: Indicate that the Flow Information within the "flowInfos" attribute cannot be handled by the SMF because any of the restrictions defined in clause 5.4.2 of 3GPP TS 29.212 was not met. + +- MISS\_REDI\_SER\_ADDR: Indicate that the PCC rule could not be successfully installed or enforced at the SMF because there is no valid Redirect Server Address within the Traffic Control Data policy decision which the PCC rule refers to provided by the PCF and no preconfigured redirection address for this PCC rule at the SMF. + +- CM\_END\_USER\_SER\_DENIED: Indicate that the charging system denied the service request due to service restrictions (e.g. terminate rating group) or limitations related to the end-user, for example the end-user's account could not cover the requested service. + +- CM\_CREDIT\_CON\_NOT\_APP: Indicate that the charging system determined that the service can be granted to the end user but no further credit control is needed for the service (e.g. service is free of charge or is treated for offline charging). + +- CM\_AUTH\_REJ: Indicate that the charging system denied the service request in order to terminate the service for which credit is requested. + +- CM\_USER\_UNK: Indicate that the specified end user could not be found in the charging system. + +- CM\_RAT\_FAILED: Indicate that the charging system cannot rate the service request due to insufficient rating input, incorrect AVP combination or due to an attribute or an attribute value that is not recognized or supported in the rating. + +- UE\_STA\_SUSP: Indicates that the UE is in suspend state. + +- UNKNOWN\_REF\_ID: Indicates that the PCC rule could not be successfully installed/modified because the referenced identifier to a Policy Decision Data or to a Condition Data is unknown to the SMF. + +- INCORRECT\_COND\_DATA: Indicates that the PCC rule could not be successfully installed/modified because the referenced Condition data are incorrect. + +- REF\_ID\_COLLISION: Indicates that PCC rule could not be successfully installed/modified because the same Policy Decision is referenced by a session rule (e.g. the session rule and the PCC rule refer to the same Usage Monitoring decision data). + +- TRAFFIC\_STEERING\_ERROR: Indicates that enforcement of the steering of traffic to the N6-LAN or 5G-LAN failed; or the dynamic PCC rule could not be successfully installed or modified at the NF service consumer because there are invalid traffic steering policy identifier(s) within the provided Traffic Control Data policy decision to which the PCC rule refers. + +- DNAI\_STEERING\_ERROR: Indicates that the enforcement of the steering of traffic to the indicated DNAI failed; or the dynamic PCC rule could not be successfully installed or modified at the NF service consumer because there is invalid route information for a DNAI(s) (e.g. routing profile id is not configured) within the provided Traffic Control Data policy decision to which the PCC rule refers. + +- AN\_GW\_FAILED: This value is used to indicate that the AN-Gateway has failed and that the PCF should refrain from sending policy decisions to the SMF until it is informed that the S-GW has been recovered. This value shall not be used if the SM Policy association modification procedure is initiated for PCC rule removal only. + +- MAX\_NR\_PACKET\_FILTERS\_EXCEEDED: This value is used to indicate that the PCC rule could not be successfully installed, modified or enforced at the NF service consumer because the number of supported packet filters for signalled QoS rules for the PDU session has been reached. + +- PACKET\_FILTER\_TFT\_ALLOCATION\_EXCEEDED: This value is used to indicate that the PCC rule is removed at 5GS to EPS mobility because TFT allocation was not possible since the number of active packet filters in the EPC bearer is exceeded. + +- MUTE\_CHG\_NOT\_ALLOWED: Indicates that the PCC rule could not be successfully modified because the mute condition for application detection report cannot be changed. Applicable when the functionality introduced with the ADC feature applies. + +#### AfSigProtocol: + +##### anyOf: + +- type: string + +##### enum: + +- NO\_INFORMATION + +- SIP + +- \$ref: 'TS29571\_CommonData.yaml#/components/schemas/NullValue' + +- type: string + +##### description: > + +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +##### description: | + +Indicates the protocol used for signalling between the UE and the AF. +Possible values are + +- NO\_INFORMATION: Indicate that no information about the AF signalling protocol is being provided. +- SIP: Indicate that the signalling protocol is Session Initiation Protocol. + +**RuleOperation:****anyOf:** + +- type: string + +**enum:** + +- CREATE\_PCC\_RULE +- DELETE\_PCC\_RULE +- MODIFY\_PCC\_RULE\_AND\_ADD\_PACKET\_FILTERS +- MODIFY\_PCC\_RULE\_AND\_REPLACE\_PACKET\_FILTERS +- MODIFY\_PCC\_RULE\_AND\_DELETE\_PACKET\_FILTERS +- MODIFY\_PCC\_RULE\_WITHOUT\_MODIFY\_PACKET\_FILTERS + +- type: string + +**description: >** + +This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. + +**description: |** + +Indicates a UE initiated resource operation that causes a request for PCC rules. + +Possible values are + +- CREATE\_PCC\_RULE: Indicates to create a new PCC rule to reserve the resource requested by the UE. +- DELETE\_PCC\_RULE: Indicates to delete a PCC rule corresponding to reserve the resource requested by the UE. +- MODIFY\_PCC\_RULE\_AND\_ADD\_PACKET\_FILTERS: Indicates to modify the PCC rule by adding new packet filter(s). +- MODIFY\_PCC\_RULE\_AND\_REPLACE\_PACKET\_FILTERS: Indicates to modify the PCC rule by replacing the existing packet filter(s). +- MODIFY\_PCC\_RULE\_AND\_DELETE\_PACKET\_FILTERS: Indicates to modify the PCC rule by deleting the existing packet filter(s). +- MODIFY\_PCC\_RULE\_WITHOUT\_MODIFY\_PACKET\_FILTERS: Indicates to modify the PCC rule by modifying the QoS of the PCC rule. + +**RedirectAddressType:****anyOf:** + +- type: string + +**enum:** + +- IPV4\_ADDR +- IPV6\_ADDR +- URL +- SIP\_URI + +- type: string + +**description: >** + +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +**description: |** + +Indicates the redirect address type. + +Possible values are + +- IPV4\_ADDR: Indicates that the address type is in the form of "dotted-decimal" IPv4 address. +- IPV6\_ADDR: Indicates that the address type is in the form of IPv6 address. +- URL: Indicates that the address type is in the form of Uniform Resource Locator. +- SIP\_URI: Indicates that the address type is in the form of SIP Uniform Resource Identifier. + +**QosFlowUsage:****anyOf:** + +- type: string + +**enum:** + +- GENERAL +- IMS\_SIG + +- type: string + +**description: >** + +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +**description: |** + +Indicates a QoS flow usage information. + +Possible values are + +- GENERAL: Indicate no specific QoS flow usage information is available. +- IMS\_SIG: Indicate that the QoS flow is used for IMS signalling only. + +**FailureCause:** + +description: Indicates the cause of the failure in a Partial Success Report. + +**anyOf:** + +``` +- type: string +enum: + - PCC_RULE_EVENT + - PCC_QOS_FLOW_EVENT + - RULE_PERMANENT_ERROR + - RULE_TEMPORARY_ERROR + - POL_DEC_ERROR +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration +and is not used to encode content defined in the present version of this API. +``` + +``` +CreditManagementStatus: +description: Indicates the reason of the credit management session failure. +anyOf: +- type: string +enum: + - END_USER_SER_DENIED + - CREDIT_CTRL_NOT_APP + - AUTH_REJECTED + - USER_UNKNOWN + - RATING_FAILED +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration +and is not used to encode content defined in the present version of this API. +``` + +``` +SessionRuleFailureCode: +anyOf: +- type: string +enum: + - NF_MAL + - RES_LIM + - SESSION_RESOURCE_ALLOCATION_FAILURE + - UNSUCC_QOS_VAL + - INCORRECT_UM + - UE_STA_SUSP + - UNKNOWN_REF_ID + - INCORRECT_COND_DATA + - REF_ID_COLLISION + - AN_GW_FAILED + - DEFAULT_QOS_MODIFICATION_FAILURE + - SESSION_AMBR_MODIFICATION_FAILURE +- type: string +description: > +This string provides forward-compatibility with future +extensions to the enumeration and is not used to encode +content defined in the present version of this API. +description: | +Indicates the reason of the session rule failure. +Possible values are +- NF_MAL: Indicates that the PCC rule could not be successfully installed (for those +provisioned from the PCF) or activated (for those pre-defined in SMF) or enforced (for those +already successfully installed) due to SMF/UPF malfunction. +- RES_LIM: Indicates that the PCC rule could not be successfully installed (for those +provisioned from PCF) or activated (for those pre-defined in SMF) or enforced (for those +already successfully installed) due to a limitation of resources at the SMF/UPF. +- SESSION_RESOURCE_ALLOCATION_FAILURE: Indicates the session rule could not be successfully +enforced due to failure during the allocation of resources for the PDU session in the UE, +RAN or AMF. +- UNSUCC_QOS_VAL: indicates that the QoS validation has failed. +- INCORRECT_UM: The usage monitoring data of the enforced session rule is not the same for +all the provisioned session rule(s). +- UE_STA_SUSP: Indicates that the UE is in suspend state. +- UNKNOWN_REF_ID: Indicates that the session rule could not be successfully +installed/modified because the referenced identifier to a Policy Decision Data or to a +Condition Data is unknown to the SMF. +- INCORRECT_COND_DATA: Indicates that the session rule could not be successfully +installed/modified because the referenced Condition data are incorrect. +- REF_ID_COLLISION: Indicates that the session rule could not be successfully +installed/modified because the same Policy Decision is referenced by a PCC rule (e.g. the +session rule and the PCC rule refer to the same Usage Monitoring decision data). +- AN_GW_FAILED: Indicates that the AN-Gateway has failed and that the PCF should refrain +from sending policy decisions to the SMF until it is informed that the S-GW has been +recovered. This value shall not be used if the SM Policy association modification procedure +is initiated for session rule removal only. +- DEFAULT_QOS_MODIFICATION_FAILURE: Indicates that the enforcement of the default QoS +modification failed. The SMF shall use this value to indicate to the PCF that the default +``` + +QoS modification has failed. +- SESSION\_AMBR\_MODIFICATION\_FAILURE: Indicates that the enforcement of the session-AMBR modification failed. The SMF shall use this value to indicate to the PCF that the session-AMBR modification has failed. + +SteeringFunctionality: + +anyOf: +- type: string +enum: +- MPTCP +- MPQUIC +- ATSSS\_LL +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. +description: | +Indicates functionality to support traffic steering, switching and splitting determined by the PCF. +Possible values are +- MPTCP: Indicates that PCF authorizes the MPTCP functionality to support traffic steering, switching and splitting. +- ATSSS\_LL: Indicates that PCF authorizes the ATSSS-LL functionality to support traffic steering, switching and splitting. + +SteerModeValue: + +description: Indicates the steering mode value determined by the PCF. +anyOf: +- type: string +enum: +- ACTIVE\_STANDBY +- LOAD\_BALANCING +- SMALLEST\_DELAY +- PRIORITY\_BASED +- REDUNDANT +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +MulticastAccessControl: + +description: > +Indicates whether the service data flow, corresponding to the service data flow template, is allowed or not allowed. +anyOf: +- type: string +enum: +- ALLOWED +- NOT\_ALLOWED +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +RequestedQoSMonitoringParameter: + +description: Indicates the requested QoS monitoring parameters to be measured. +anyOf: +- type: string +enum: +- DOWNLINK +- UPLINK +- ROUND\_TRIP + +- DOWNLINK\_DATA\_RATE +- UPLINK\_DATA\_RATE +- DOWNLINK\_CONGESTION +- UPLINK\_CONGESTION +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +ReportingFrequency: + +description: Indicates the frequency for the reporting. +anyOf: +- type: string +enum: + +- EVENT\_TRIGGERED +- PERIODIC +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +SgsnAddress: +description: describes the address of the SGSN +type: object +anyOf: +- required: [sgsnIpv4Addr] +- required: [sgsnIpv6Addr] +properties: +sgsnIpv4Addr: +\$ref: 'TS29571\_CommonData.yaml#/components/schemas/Ipv4Addr' +sgsnIpv6Addr: +\$ref: 'TS29571\_CommonData.yaml#/components/schemas/Ipv6Addr' + +SmPolicyAssociationReleaseCause: +description: > +Represents the cause due to which the PCF requests the termination of the SM policy association. +anyOf: +- type: string +enum: +- UNSPECIFIED +- UE\_SUBSCRIPTION +- INSUFFICIENT\_RES +- VALIDATION\_CONDITION\_NOT\_MET +- REACTIVATION\_REQUESTED +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +PduSessionRelCause: +description: Contains the SMF PDU Session release cause. +anyOf: +- type: string +enum: +- PS\_TO\_CS\_HO +- RULE\_ERROR +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +MaPduIndication: +description: > +Contains the MA PDU session indication, i.e., MA PDU Request or MA PDU Network-Upgrade Allowed. +anyOf: +- type: string +enum: +- MA\_PDU\_REQUEST +- MA\_PDU\_NETWORK\_UPGRADE\_ALLOWED +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration and is not used to encode content defined in the present version of this API. + +AtsssCapability: +description: Contains the ATSSS capability supported for the MA PDU Session. +anyOf: +- type: string +enum: +- MPTCP\_ATSSS\_LL\_WITH\_ASMODE\_UL +- MPTCP\_ATSSS\_LL\_WITH\_EXSDMODE\_DL\_ASMODE\_UL +- MPTCP\_ATSSS\_LL\_WITH\_ASMODE\_DLUL +- ATSSS\_LL +- MPTCP\_ATSSS\_LL +- MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_UL +- MPQUIC\_ATSSS\_LL\_WITH\_EXSDMODE\_DL\_ASMODE\_UL +- MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_DLUL +- MPQUIC\_ATSSS\_LL +- MPTCP\_MPQUIC\_ATSSS\_LL\_WITH\_ASMODE\_UL +- MPTCP\_MPQUIC\_ATSSS\_LL\_WITH\_EXSDMODE\_DL\_ASMODE\_UL + +``` + - MPTCP_MPQUIC_ATSSS_LL_WITH_ASMODE_DLUL + - MPTCP_MPQUIC_ATSSS_LL + - type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration + and is not used to encode content defined in the present version of this API. +# +NetLocAccessSupport: + anyOf: + - type: string + enum: + - ANR_NOT_SUPPORTED + - TZR_NOT_SUPPORTED + - LOC_NOT_SUPPORTED + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration and is not used to encode + content defined in the present version of this API. + description: | + Indicates the access network support of the report of the requested access network + information. + Possible values are + - ANR_NOT_SUPPORTED: Indicates that the access network does not support the report of access + network information. + - TZR_NOT_SUPPORTED: Indicates that the access network does not support the report of UE + time zone. + - LOC_NOT_SUPPORTED: Indicates that the access network does not support the report of UE + Location (or PLMN Id). + +PolicyDecisionFailureCode: + description: Indicates the type of the failed policy decision and/or condition data. + anyOf: + - type: string + enum: + - TRA_CTRL_DECS_ERR + - QOS_DECS_ERR + - CHG_DECS_ERR + - USA_MON_DECS_ERR + - QOS_MON_DECS_ERR + - CON_DATA_ERR + - POLICY_PARAM_ERR + - type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration + and is not used to encode content defined in the present version of this API. +# +NotificationControlIndication: + description: > + Indicates that the notification of DDD Status is requested and/or that the notification of + DDN Failure is requested. + anyOf: + - type: string + enum: + - DDN_FAILURE + - DDD_STATUS + - type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration + and is not used to encode content defined in the present version of this API. +# +SteerModeIndicator: + description: Contains Autonomous load-balance indicator or UE-assistance indicator. + anyOf: + - type: string + enum: + - AUTO_LOAD_BALANCE + - UE_ASSISTANCE + - type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration + and is not used to encode content defined in the present version of this API. +# +TrafficParameterMeas: + description: Indicates the traffic parameters to be measured. + anyOf: + - type: string + enum: +``` + +``` +- DL_N6_JITTER +- DL_PERIOD +- UL_PERIOD +- type: string +description: > +This string provides forward-compatibility with future extensions to the enumeration +and is not used to encode content defined in the present version of this API. +``` + +--- + +## Annex B (normative): 5GC and EPC interworking scenario support + +### B.1 Scope + +This annex defines procedures for 5GC and EPC interworking, which contains the following scenarios: + +- EPS and 5GS interworking (i.e. 3GPP access connected to EPC and 3GPP access connected to 5GC). +- EPC/ePDG and 5GS interworking (i.e. ePDG connected to EPC and 3GPP access connected to 5GC). +- EPS and 5GC/N3IWF interworking (i.e. 3GPP access connected to EPC and N3IWF connected to 5GC). +- EPS and 5GC/TNAN/TWAN interworking (i.e. 3GPP access connected to EPC and TNAN/TWAN connected to 5GC). + +NOTE: In this Release 5GC and EPC interworking is not supported for SNPN. + +--- + +## B.2 Npcf\_SMPolicyControl Service + +### B.2.1 Service Description + +#### B.2.1.1 Overview + +Session Management Policy Control Service applies to the cases where the SMF+PGW-C interacts with the PCF in the non-roaming scenario, the SMF+PGW-C interacts with the V-PCF in the local breakout roaming scenario and the H-SMF+H-PGW-C interacts with the H-PCF in the home-routed scenario. + +#### B.2.1.2 Service Architecture + +The Session Management Policy Control Service is provided by the PCF as shown in the SBI representation model in figure B.2.1.2-1 and in the reference point representation model in figure B.2.1.2.2. + +In this scenario the NF Service Consumer is a combined SMF and PGW-C. + +![Figure B.2.1.2-1: Reference Architecture for the Npcf_SMPolicyControl Service for 5GC and EPC interworking scenario; SBI representation. The diagram shows a PCF (Policy Control Function) connected to an SMF+PGW-C (SMF+PDN Gateway-C) via an Npcf interface. The Npcf interface is represented by a circle labeled 'Npcf' inside the PCF box, and the service name 'Npcf_SMPolicyControl' is shown in a box between the PCF and the SMF+PGW-C.](bf9abec3605f1a8d00ae6524a9af02ed_img.jpg) + +Figure B.2.1.2-1: Reference Architecture for the Npcf\_SMPolicyControl Service for 5GC and EPC interworking scenario; SBI representation. The diagram shows a PCF (Policy Control Function) connected to an SMF+PGW-C (SMF+PDN Gateway-C) via an Npcf interface. The Npcf interface is represented by a circle labeled 'Npcf' inside the PCF box, and the service name 'Npcf\_SMPolicyControl' is shown in a box between the PCF and the SMF+PGW-C. + +**Figure B.2.1.2-1: Reference Architecture for the Npcf\_SMPolicyControl Service for 5GC and EPC interworking scenario; SBI representation** + +![Figure B.2.1.2-2: Reference Architecture for the Npcf_SMPolicyControl Service or 5GC and EPC interworking scenario; reference point representation. The diagram shows a PCF (Policy Control Function) connected to an SMF+PGW-C (SMF+PDN Gateway-C) via an N7 reference point. The N7 reference point is represented by a box labeled 'N7' between the PCF and the SMF+PGW-C.](096a620f7a0b1b639a9da9618c1a3801_img.jpg) + +Figure B.2.1.2-2: Reference Architecture for the Npcf\_SMPolicyControl Service or 5GC and EPC interworking scenario; reference point representation. The diagram shows a PCF (Policy Control Function) connected to an SMF+PGW-C (SMF+PDN Gateway-C) via an N7 reference point. The N7 reference point is represented by a box labeled 'N7' between the PCF and the SMF+PGW-C. + +**Figure B.2.1.2-2: Reference Architecture for the Npcf\_SMPolicyControl Service or 5GC and EPC interworking scenario; reference point representation** + +NOTE: The PCF represents the V-PCF in the local breakout scenario. The SMF+PGW-C represents the H-SMF+H-PGW-C and the PCF represents the H-PCF in the home routed scenario. + +## B.3 Service Operation + +### B.3.1 Introduction + +This clause defines the specific service operations for the 5GC and EPC interworking scenario. In addition, the service operations defined in clause 4.2 shall be applicable. + +NOTE: For brevity reason, the combined SMF and PGW-C is denoted as SMF in what follows. + +### B.3.2 Npcf\_SMPolicyControl\_Create Service Operation + +#### B.3.2.0 General + +When the UE establishes the PDN connection through the EPC network and the SMF+PGW-C receives the Create Session Request message as defined in 3GPP TS 29.274 [37], the SMF+PGW-C shall behave as defined in clause 4.2.2.2 with the differences that the SMF+PGW-C shall include (if available) in SmPolicyContextData data structure: + +- the IMSI of the user within the "supi" attribute; +- the MSISDN of the user within the "gpsi" attribute; +- APN within the "dnn" attribute; + +- PDU Session Id determined by the SMF+PGW-C within "pduSessionId" attribute for a UE that has an EPS subscription that allows 5GC interworking but does not support 5GC NAS. + +NOTE 1: For a PDN connection established via the MME or ePDG, the PDU Session ID value is assigned from a reserved range as specified in Table 5.4.2-1 of 3GPP TS 29.571 [11]. The PDU session ID value assigned at PDN connection establishment remains unchanged along the PDN connection, i.e., it does not change when the UE handovers between EPS and EPC/ePDG. In the scenarios where UE handover between EPS and EPC/ePDG is enabled, to ensure uniqueness of the assigned PDU Session ID value, the SMF+PGW-C can retrieve from UDM the already assigned PDU Session ID values, allocate a non-colliding PDU Session ID value, and register in UDM the allocated PDU session ID; + +- PDN Type within the "pduSessionType" attribute; +- IMEI-SV within the "pei" attribute; +- IP-CAN type within the "accessType" attribute; +- RAT type within the "ratType" attribute; + +NOTE 2: See Annex B.3.2.2 for further information. + +- subscribed APN-AMBR within "subsSessAmbr" attribute; +- subscribed Default EPS bearer QoS within "subsDefQos" attribute; + +NOTE 3: Subscribed APN-AMBR and the QCI within the subscribed default EPS bearer QoS are mapped to subscribed Session-AMBR and 5QI as defined in Annex B.3.6.1 respectively. + +- user location information within the "userLocationInfo" attribute; + +NOTE 4: See Annex B.3.2.1 for further information. + +- the S-NSSAI determined by the SMF+PGW-C within the "sliceInfo" attribute; +- the bearer usage required of the default bearer within the "qosFlowUsage" attribute; +- the UE time zone information within "ueTimeZone" attribute, if available. + +NOTE 5: The UE time zone is not available in EPC untrusted WLAN. + +When the UE establishes the PDN connection in an 5GS-EPC interworking deployment, the SMF+PGW-C shall behave as defined in clause 4.2.2.2 (access through 5GS network) or this clause (access through the EPC network) and additionally, if the feature "PackFiltAllocPrecedence" is supported and there is a possibility to run into a restriction regarding the number of TFT packet filters that can be allocated when interworking with EPS with N26 is supported (see clause 4.11.1 of TS 23.502 [3]), the PCF may provide, as part of the PccRule data type(s) for the PCC Rules to be installed, the "packFiltAllPrec" attribute to indicate the order of the PCC Rules in the allocation of TFT packet filter(s) by the SMF+PGW-C. + +NOTE 6: PCF can know that interworking with EPS with N26 is supported based on the received DNN and S-NSSAI of the PDU Session. + +### B.3.2.1 UE Location related information + +When the UE establishes the PDN connection through the EPC/E-UTRAN network, the SMF+PGW-C shall include, if available, the following user location information: + +- user location information within the "eutraLocation" attribute included in the "userLocationInfo" attribute; and +- S-GW address, if available, within the "anGwAddr" attribute included in the "servNfId" attribute. + +When the UE establishes the PDN connection through the EPC/UTRAN network and the feature "2G3GIWK" is supported, the SMF+PGW-C shall include, if available, the following user location information: + +- user location information within the "utraLocationInfo" attribute included in the "userLocationInfo" attribute; and + +- SGSN address, if available, within the "sgsnAddr" attribute included in the "servNfId" attribute. + +When the UE establishes the PDN connection through the EPC/GERAN network and the feature "2G3GIWK" is supported, the SMF+PGW-C shall include, if available, the following user location information: + +- user location information within the "geraLocationInfo" attribute included in the "userLocationInfo" attribute; and +- SGSN address, if available, within the "sgsnAddr" attribute included in the "servNfId" attribute. + +When the UE establishes the PDN connection through the EPC/ePDG network, the SMF+PGW-C shall include, if available, the following user location information: + +- user location information within the "n3gaLocation" attribute included in the "userLocationInfo" attribute. The "n3gaLocation" attribute includes the "ueIpv4Addr" or "ueIpv6Addr" attributes, and, if available the "portNumber" and "protocol" attributes and, if the feature "WLAN\_Location" is supported, the "twapId" attribute encoding the WLAN location information, if available; and +- ePDG identification within the "anGwAddr" attribute included in the "servNfId" attribute. + +NOTE: The "n3gaLocation" attribute does not include the "n3gppTai" and "n3IwfId" attributes in EPC interworking scenarios. + +### B.3.2.2 Access Type related information + +When the UE establishes the PDN connection through the EPC/E-UTRAN network, the SMF+PGW shall include, if available, the following access type information: + +- the "3GPP\_ACCESS" value within the "accessType" attribute; and +- the "EUTRA" value within the "ratType" attribute. + +When the UE establishes the PDN connection through the EPC/UTRAN network and the feature "2G3GIWK" is supported, the SMF+PGW shall include, if available, the following access type information: + +- the "3GPP\_ACCESS" value within the "accessType" attribute; and +- the "UTRA" value within the "ratType" attribute. + +When the UE establishes the PDN connection through the EPC/GERAN network and the feature "2G3GIWK" is supported, the SMF+PGW shall include, if available, the following access type information: + +- the "3GPP\_ACCESS" value within the "accessType" attribute; and +- the "GERA" value within the "ratType" attribute. + +When the UE establishes the PDN connection through the EPC/ePDG network, the SMF+PGW shall include, if available, the following access type information: + +- the "NON\_3GPP\_ACCESS" value within the "accessType" attribute; +- the "WLAN" or "VIRTUAL" value within the "ratType" attribute, as applicable; and +- the ePDG address in the "servNfId" attribute within the "anGwAddr" attribute. + +### B.3.2.3 Access Network Charging Identifier report + +During PDU session establishment procedure, the SMF+PGW-C may provide the Access Network Charging Identifier for the PDU session (i.e., for the default QoS flow or the default EPS bearer) as specified in clause 4.2.2.11, or may provide the Access Network Charging Identifier for the default EPS bearer and indicate that there is a separate access network charging identifier for each EPS bearer/QoS flow by omitting or setting to false the "sessionChScope" attribute. + +In both cases above, the Access Network Charging Identifier value and the address of the network entity performing the charging are provided as specified in clause 4.2.2.11. + +NOTE: During the PDU Session Establishment procedure, when there are different charging identifiers for each EPS bearer (or QoS flow), the "refPccRuleIds" attribute is not provided within the AccNetChId data structure, since the PCC Rules are not yet authorized at this stage. + +## B.3.3 Npcf\_SMPolicyControl\_UpdateNotify Service Operation + +### B.3.3.0 General + +When the UE has an established PDN connection through the EPC/E-UTRAN network and the PCF provisions the policy to the SMF+PGW-C as defined in clause 4.2.3. The SMF+ PGW-C shall behave as defined in clause 4.2.3 with the differences that the SMF+PGW-C shall map the QoS information within the PCC rule and/or session rule into EPS QoS information as defined in Annex B.3.6.1. + +When the UE has an established PDN connection in an 5GS-EPC interworking deployment, the SMF+PGW-C shall behave as defined in clause 4.2.3 (access through the 5GS network) or this clause (access through the EPC network) and additionally, if the feature "PackFiltAllocPrecedence" is supported and there is a possibility to run into a restriction regarding the number of TFT packet filters that can be allocated when interworking with EPS with N26 is supported as described in Annex B.3.2.0, the PCF may provide, as part of the PccRule data type for the new PCC Rules to be installed, the "packFiltAllPrec" attribute to indicate the order of the PCC Rules in the allocation of TFT packet filter(s) by the SMF+PGW-C. + +### B.3.3.1 Policy Update When UE suspends + +If the PolicyUpdateWhenUESuspends feature as defined in clause 5.8 is supported the PCF and the SMF shall comply with the procedures specified in this clause. During PDU session/PDN connection establishment or modification procedure, the PCF shall subscribe to the "UE\_STATUS\_RESUME" policy control request trigger if not subscribed yet, as described in clause 4.2.6.4. When the SMF receives the policy decision from the PCF as defined in clause 4.2.3.1 for a PDN connection maintained when the UE's status is suspend state, the SMF shall reject the request and include an HTTP "400 Bad Request" status code together with an ErrorReport structure. Within the ErrorReport data structure, the SMF shall include the "error" attribute containing the "cause" attribute of the ProblemDetails data structure set to "UE\_STATUS\_SUSPEND" which indicates the failure to enforce the corresponding policy decision, except if the policy decision is for the PCC rule removal only and/or session rule removal only, and further include the information as follows: + +- If the policy decision includes the installation of one or more PCC rules, the SMF shall invoke the procedure as defined in clause 4.2.3.16 with the "failureCode" attribute set to "UE\_STA\_SUSP" and "ruleStatus" attribute set to INACTIVE to indicate the failure to enforce those PCC rules. +- If the policy decision includes the modification of one or more PCC rules, the SMF shall invoke the procedure as defined in clause 4.2.3.16 with the "failureCode" attribute set to "UE\_STA\_SUSP" and "ruleStatus" attribute set to ACTIVE to indicate the failure to enforce those PCC rules. +- If the policy decision includes the modification of one or more session rules, the SMF shall within a RuleReport data structure include the "sessRuleReports" attribute. Within each SessionRuleReport data structure, the SMF shall include the affected session rules within the "ruleIds" attribute(s), the "sessRuleFailureCode" attribute set to "UE\_STA\_SUSP" and "ruleStatus" attribute set to ACTIVE to indicate the failure to enforce those session rules. + +Upon reception of the "failureCode" attribute and/or "sessRuleFailureCode" attribute set to "UE\_STA\_SUSP" or the ProblemDetails data structure set to "UE\_STATUS\_SUSPEND", the PCF shall not initiate any PDU Session Modification procedure, except if it is initiated for the PCC rule removal only or the session rule removal only, for the given PDU session over N7 until the UE's status is resumed. When the SMF detected the UE's status is resumed from suspend state, the SMF shall inform the PCF of the UE status as defined in Annex B.3.4.2. + +### B.3.3.2 Request report of EPS Fallback + +When the "EPSFallbackReport" feature is supported, if the AF requests the PCF to report the EPS fallback for voice media type as described in clauses 4.2.2.30 or 4.2.3.29 of 3GPP TS 29.514 [17] or in clause E.3 of 3GPP TS 29.214 [18], the PCF shall perform the PCC rule provisioning procedure as defined in clause 4.2.6.2.1 and additionally provide the request of EPS fallback report to the SMF as follows: + +- it shall include the "lastReqRuleData" attribute to contain the "reqData" attribute with the value "EPS\_FALLBACK" and the "refPccRuleIds" attribute to contain the related installed/modified PCC rule identifier(s) with 5QI=1. +- it shall provide the "EPS\_FALLBACK" policy control request rigger within the "policyCtrlReqTriggers" attribute, if not provided before. + +### B.3.3.3 S-GW Restoration Support + +If the SGWRest feature as defined in clause 5.8 is supported, the PCF and the SMF shall comply with the procedures specified in this clause. During PDU session/PDN connection establishment or modification procedure, the PCF shall subscribe to the "SCNN\_CH" policy control request trigger if not subscribed yet, as described in clause 4.2.6.4. + +When the SMF+PGW receives the policy decision from the PCF as defined in clause 4.2.3.1 for a PDN connection maintained during a S-GW failure, the SMF+PGW shall act as follows: + +- For MME/S4-SGSN triggered S-GW Restoration scenarios: + - the SMF+PGW shall reject the request and include an HTTP "400 Bad Request" status code together with an ErrorReport structure. Within the ErrorReport data structure, the SMF shall include the "error" attribute containing the "cause" attribute of the ProblemDetails data structure set to "AN\_GW\_FAILED" which indicates the failure to enforce the corresponding policy decision, except if the policy decision is for the PCC rule removal only and/or session rule removal only, and further include the information as follows: + - If the policy decision is related to one or more PCC rules, the SMF+PGW shall behave as defined in clause 4.2.3.16 with the "failureCode" attribute set to "AN\_GW\_FAILED". + - If the policy decision is related to one or more session rules, the SMF+PGW shall behave as defined in clause 4.2.3.20 with the "sessRuleFailureCode" attribute set to "AN\_GW\_FAILED". + - For SMF+PGW triggered S-GW Restoration scenarios, the SMF+PGW shall accept the procedure as per normal procedures. In the case, the PDN connection is not restored during an operator configured time period, the SMF+PGW shall behave as follows as defined in annex B.3.4.9. + +Upon reception of the "cause" attribute of the ProblemDetails data structure set to "AN\_GW\_FAILED" or the "failureCode" attribute set to "AN\_GW\_FAILED" and/or the "sessRuleFailureCode" attribute set to "AN\_GW\_FAILED", the PCF shall not initiate any SM Policy association modification procedure, except if the I SM Policy association modification procedure is initiated for the PCC rule removal only, for the given SM Policy association over N7 until the S-GW has recovered. + +The SMF+PGW shall maintain the PDN connections affected by the S-GW failure and eligible for restoration for an operator configurable time period. Upon expiry of that time period, the SMF+PGW shall release the PDN connection and inform the PCF about the SM Policy association termination as specified in clause 4.2.5.2. + +The SMF+PGW should maintain the GBR bearers of the PDN connections eligible for restoration for an operator configurable time period. Upon expiry of that time period, the SMF+PGW shall release GBR bearers that have not yet been restored and inform the PCF about the PCC rule removal as specified in clause 4.2.4.7. + +The SMF+PGW shall discard downlink packets received for a PDN connection maintained during a S-GW failure that has not yet been restored. + +The SMF+PGW shall delete the PDN connection locally when it receives an SM Policy association termination from the PCF as described in clause 4.2.4.3. + +### B.3.3.4 Request of Access Network Charging Identifier + +When the PCF received from the SMF+PGW-C the indication that the Access Network Charging Identifier is different per EPS bearer/QoS flow (see clause B.3.2.3), or the Access Network Charging identifier is unknown for an AF session to the PCF, and the PCF received from the AF the request of access network information as specified in 3GPP TS 29.514 [17] or 3GPP TS 29.214 [18], the PCF shall request the access network charging identifier associated to the dynamic PCC rules as specified in clause 4.2.6.5.1. + +### B.3.3.5 Forwarding of UE policy container for URSP provisioning in EPS + +The PCF may receive a UE policy container and/or policy control triggers from the PCF for the UE during the lifetime of the PDU session and forward it to the SMF+PGW-C by invoking the procedure defined in clause 4.2.3.2. + +If the feature "EpsUrsp" is supported the PCF initiates the Npcf\_SMPolicyControl\_UpdateNotify request and transparently forwards the the UE policy container to the SMF+PGW-C via the SmPolicyDecision structure, in which the UE policy container is encoded in the "uePolCont" attribute. + +## B.3.4 Npcf\_SMPolicyControl\_Update Service Operation + +### B.3.4.0 General + +When the established PDN connection through the EPC/E-UTRAN network is modified and SMF+PGW-C receives Modify Bearer Request, Modify Bearer or Delete Bearer Command message and if the SMF detects the policy control request trigger(s) is met or the error(s) needs to be reported or when the UE handed over from the 5GS to the EPS and the SMF detects the policy control request trigger(s) is met, the SMF+PGW-C shall behave as defined in clause 4.2.4.2 with the differences that the SMF+PGW-C shall include (if available) in the SmPolicyUpdateContextData data structure: + +- IP-CAN type within the "accessType" attribute; +- RAT type within the "ratType" attribute; + +NOTE 1: See Annex B.3.4.5 for further information. + +- subscribed APN-AMBR within the "subsSessAmbr" attribute; +- subscribed Default EPS bearer QoS Information within the "subsDefQos" attribute; + +NOTE 2: Subscribed APN-AMBR and the QCI within the subscribed default EPS bearer QoS are mapped to subscribed Session-AMBR and 5QI as defined in Annex B.3.6.1 respectively. + +- the bearer usage required for the dedicated bearer within the "qosFlowUsage" attribute if the UE initiates a resource modification request procedure and the bearer usage request was present in the Bearer Resource Command; +- user location information of EPC within the "userLocationInfo" attribute; and + +NOTE 3: See Annex B.3.4.3 for further information. + +- UE policy container within "uePolCont" attribute, if available. + +The policy control request trigger "RES\_MO\_RE" is not supported when the PDN connection is established through the EPC/E-UTRAN network. The SMF+PGW shall reject the PDU session modification that initiated the UE's resource modification. + +During interworking from 5GS to EPS, if the feature "PackFiltAllocPrecedence" is supported, for QoS Flows without EPS bearer ID(s) assigned or for QoS Flows related to PCC Rules that do not have allocated TFT packet filters, the SMF+PGW-C shall delete those PCC Rules and inform the PCF. The SMF+PGW-C shall include the "ruleReports" attribute containing the RuleReport data instance which specifies the affected PCC rules within the "pccRuleIds" attribute, set to "INACTIVE" the value within the "ruleStatus" attribute and the "PACKET\_FILTER\_TFT\_ALLOCATION\_EXCEEDED" as the value of the "failureCode" attribute. + +If the feature "PackFiltAllocPrecedence" is supported, the PCF may provide, as part of the PccRule data type for the new PCC Rules to be installed the "packFiltAllPrec" attribute to indicate the order of the PCC Rules in the allocation of TFT packet filter(s) by the SMF+PGW-C. The PCF may include this parameter if the feature "PackFiltAllocPrecedence" is supported and there is a possibility to run into a restriction regarding the number of TFT packet filters that can be allocated for the PDU Session and interworking with EPS with N26 deployment is supported as described in Annex B.3.2.0. + +### B.3.4.1 Number of Supported Packet Filters Report + +When the UE handed over from the EPC/E-UTRAN to the 5GS and the number of supported packet filters for signalled QoS rules is received from the UE, the SMF shall include the "NUM\_OF\_PACKET\_FILTER" within the "repPolicyCtrlReqTriggers" attribute and the number of supported packet filters for signalled QoS rules within the "numOfPackFilter". In this case, the PCF shall behave as defined in clause 4.2.6.2.16. + +NOTE: The maximum number of packet filters sent to the UE per QoS rule is additionally limited as specified in 3GPP TS 24.501 [20] when the UE is camping in 5GS. + +### B.3.4.2 Policy Update When UE suspends + +#### B.3.4.2.1 Policy Update Error Report + +If the PolicyUpdateWhenUESuspends feature as defined in clause 5.8 is supported, the PCF and the SMF shall comply with the procedures specified in this clause. During PDU session/PDN connection establishment or modification procedure, the PCF shall subscribe to the "UE\_STATUS\_RESUME" policy control request trigger if not subscribed yet, as described in clause 4.2.6.4. When the SMF receives the policy decision from the PCF as defined in clause 4.2.4.1 for a PDN connection maintained when the UE's status is suspend state, the SMF shall include the "ruleReports" attribute for the affected PCC rules and/or session rules to report the failure within the SmPolicyUpdateContextData data structure. Within the ErrorReport data structure, the SMF shall include the "error" attribute containing the "cause" attribute of the ProblemDetails data structure set to "UE\_STATUS\_SUSPEND" which indicates the failure to enforce the corresponding policy decision, except if the policy decision is for the PCC rule removal only and/or session rule removal only, and further include the information as follows: + +- if the policy decision includes the modification of one or more session rules, within an RuleReport instance, the SMF shall include the "sessRuleReports" attribute. Within each SessionRuleReport data structure, the SMF shall include the affected session rules within the "ruleIds" attribute, the "sessRuleFailureCode" attribute set to "UE\_STA\_SUSP" and the "ruleStatus" attribute set to ACTIVE to indicate the failure to enforce those session rules. +- if the policy decision includes the installation of one or more PCC rules, the SMF shall invoke the procedure as defined in clause 4.2.4.15 with the "failureCode" attribute set to "UE\_STA\_SUSP" and "ruleStatus" attribute set to INACTIVE to indicate the failure to enforce those PCC rules. +- if the policy decision includes the modification of one or more PCC rules, the SMF shall invoke the procedure as defined in clause 4.2.4.15 with the "failureCode" attribute set to "UE\_STA\_SUSP" and "ruleStatus" attribute set to ACTIVE to indicate the failure to enforce those PCC rules. + +Upon reception of the "failureCode" attribute and/or "sessRuleFailureCode" attribute set to "UE\_STA\_SUSP", the PCF shall not initiate any PDU Session Modification procedure, except if it is initiated for the PCC rule removal only and/or session rule removal only, for the given PDU session over N7 until the UE's status is resumed. + +#### B.3.4.2.2 UE State Change Report + +If the SMF detected the UE's status is resumed from suspend state, the SMF shall inform the PCF of the UE status including the "UE\_STATUS\_RESUME" within "repPolicyCtrlReqTriggers" attribute. The PCF shall after this update the SMF with PCC Rules or session rules if necessary. + +### B.3.4.3 UE Location related information + +When the UE handed over from the EPC/GERAN or EPC/UTRAN and the feature "2G3GIWK" is supported, or 5GS to EPC/E-UTRAN the SMF+PGW-C shall include, together with the policy control request triggers met, the following user location information: + +- If the "SAREA\_CH" or "SCELL\_CH" policy control request trigger is provisioned and met, the user location information within the "eutraLocation" attribute included in the "userLocationInfo" attribute. +- If the "SCNN\_CH" policy control request trigger is provisioned and met, the "servNfId" attribute including the S-GW identification within the "anGwAddr" attribute. + +- If the "AN\_INFO" policy control request trigger is met, the user location was requested by the PCF and provided to the SMF+PGW-C, the SMF shall provide the user location information within the "eutraLocation" attribute included in the "userLocationInfo" attribute and the time when it was last known in the 3GPP access within "userLocationInfoTime" attribute (if available). + +When the UE handed over from the EPC/E-UTRAN to the EPC/GERAN or EPC/UTRAN and the feature "2G3GIWK" is supported the SMF+PGW-C shall include, together with the policy control request triggers met, the following user location information: + +- If the "SAREA\_CH" or "SCELL\_CH" policy control request trigger is provisioned and met, the user location information within the "geraLocation" attribute or "utraLocation" attribute included in the "userLocationInfo" attribute. +- If the "SCNN\_CH" policy control request trigger is provisioned and met, the "servNfld" attribute including the SGSN identification within the "sgsnAddr" attribute. + +When the UE handed over from the 5GS to EPC non-3GPP access, the SMF+PGW-C shall include, together with the applicable provisioned policy control request triggers, the following user location information: + +- If the "SAREA\_CH" policy control request trigger is provisioned and met, and the hand over is to EPC untrusted non-3GPP access, the user location information within the "n3gaLocation" attribute included in the "userLocationInfo" attribute as specified in clause B.3.2.1. +- If the "SCNN\_CH" policy control request trigger is provisioned and met, the ePDG identification within the "anGwAddr" attribute included in the "servNfld" attribute. +- If the "AN\_INFO" policy control request trigger is met, the user location was requested by the PCF and provided to the SMF+PGW-C, the SMF shall provide the user location information within the "n3gaLocation" attribute included in the "userLocationInfo" attribute and the time when it was last known in the non-3GPP access within "userLocationInfoTime" attribute (if available). The "n3gaLocation" attribute includes the "ueIpv4Addr" or "ueIpv6Addr" attributes, and, if available the "portNumber" and "protocol" attributes and, if the feature "WLAN\_Location" is supported, the "twapId" attribute encoding the WLAN location information, if available. + +NOTE 1: The "n3gaLocation" attribute does not include the "n3gppTai" and "n3IwflId" attributes in EPC interworking scenarios. + +NOTE 2: SCELL\_CH policy control request trigger is not supported in EPC Non-3GPP access. The PCF will not receive user location information related to this trigger in this case. + +#### B.3.4.4 Presence Reporting Area Information Report + +When the UE is connected through the EPC/E-UTRAN network, the SMF+PGW-C receives the presence reporting area information as defined in 3GPP TS 29.274 [37]. When the PRA or ePRA feature is supported, the SMF+PGW-C provides presence reporting area to the PCF as specified in clause 4.2.4.16. + +If the SMF+PGW-C receives from the MME presence reporting information corresponding to the Set of Core Network predefined Presence Reporting Areas, and the individual presence reporting area as specified in 3GPP TS 29.274 [37], the SMF+PGW shall only provide the PCF with the individual presence reporting area within the "praId" attribute of the PresenceInfo data type. + +#### B.3.4.5 Access Type related information + +The SMF+PGW shall include, when the policy control request trigger "AC\_TY\_CH" is met, the following access type information: + +- If after handover the new access type is EPC/E-UTRAN: + - a) the "3GPP\_ACCESS" value within the "accessType" attribute; and + - b) the "EUTRA" value within the "ratType" attribute. +- If after handover the new access type is EPC/UTRAN and the feature "2G3GIWK" is supported: + - a) the "3GPP\_ACCESS" value within the "accessType" attribute; and + +- b) the "UTRA" value within the "ratType" attribute. +- If after handover the new access type is EPC/GERAN and the feature "2G3GIWK" is supported: + - a) the "3GPP\_ACCESS" value within the "accessType" attribute; and + - b) the "GERA" value within the "ratType" attribute. +- If after handover the new access type is EPC/ePDG: + - a) the "NON\_3GPP\_ACCESS" value within the "accessType" attribute; + - b) the "WLAN" or "VIRTUAL" value within the "ratType" attribute, as applicable; and + - c) the ePDG address in the "servNfId" attribute within the "anGwAddr" attribute. + +NOTE 1: In the interworking scenario, "AC\_TY\_CH" is met when the UE handed over from the 5GC/N3IWF or 5GC/TNAN/TWAN to the EPC/E-UTRAN, or when the UE handed over from the 5GS to the EPC/ePDG. + +The SMF+PGW shall include, when the policy control request trigger "RAT\_TY\_CH" is met, the following RAT type information: + +- If after handover the new RAT type is the E-UTRA, the "EUTRA" value within the "ratType" attribute. +- If after handover the new RAT type is the WLAN, the "WLAN" or "VIRTUAL" value within the "ratType" attribute, as applicable. + +NOTE 2: In the interworking scenario, "RAT\_TY\_CH" is met when the UE handed over from the NR to the E-UTRA or when the UE handed over from the NR to the WLAN (untrusted) and from E-UTRA to WLAN (trusted/untrusted) or from E-UTRA to N3GA. + +### B.3.4.6 Report of EPS Fallback + +When the "EPSFallbackReport" feature is supported, if the "policyCtrlReqTriggers" attribute with the value "EPS\_FALLBACK" has been provided to the SMF, the SMF shall notify to the PCF of EPS fallback when a PCC rule referred from the "lastReqRuleData" attribute required the EPS fallback report within the "reqData" attribute. + +When the SMF received a PDU session modification response from the access network indicating the establishment of the QoS flow with 5QI=1 is rejected due to EPS fallback, the SMF shall within the SmPolicyUpdateContextData data structure include: + +- the "EPS\_FALLBACK" value within the "repPolicyCtrlReqTriggers" attribute; and +- the affected PCC rules within the "pccRuleIds" attribute included in the "ruleReports" attribute, where the "ruleStatus" attribute is set to ACTIVE. + +The PCF shall identify the AF session that requested the voice media type that triggered the EPS fallback and shall notify the AF as described in clauses 4.2.5.15 of 3GPP TS 29.514 [17] or in clause E.3 of 3GPP TS 29.214 [18]. + +### B.3.4.7 MA PDU Session + +If the UE or the network does not support MA PDU Session with 3GPP access connected to EPC, when the UE handed over from the EPC/E-UTRAN to the 5GS and the MA PDU Request Indication or MA PDU Network-Upgrade Allowed Indication and ATSSS Capability are received from the UE, if the "ATSSS" feature defined in clause 5.8 is supported, the SMF shall include the "MA\_PDU" within the "repPolicyCtrlReqTriggers" attribute, and, as defined in clause 4.2.2.17, the SMF shall include the MA PDU session Indication within the "maPduInd" attribute and the ATSSS capability of the MA PDU session within the "atsssCapab" attribute. In this case, the PCF shall behave as defined in clause 4.2.2.17. + +NOTE: If the UE and the network support MA PDU Sessions with 3GPP access connected to EPC, the MA PDU Session can be simultaneously associated with user-plane resources on 3GPP access network connected to EPC and with non-3GPP access network connected to 5GC as specified in clause B.3.6.4. + +### B.3.4.8 EPS RAN NAS Cause Support + +If the RAN-NAS-Cause feature as defined in clause 5.8 is supported, and the PDN connection is established through the EPC network, the SMF shall report the RAN/NAS release cause(s) as specified in clauses 4.2.4.7, 4.2.4.12 and 4.2.4.15, with the exception that the received EPS RAN/NAS cause(s) are encoded within the "epsCause" attribute included in the RanNasRelCause data type. In this Release of the specification, the EPS release cause code information may include RAN/NAS release cause(s), a TWAN release cause or an untrusted WLAN release cause. + +### B.3.4.9 S-GW Restoration Support + +If the SGWRest feature as defined in clause 5.8 is supported, the PCF and the SMF shall comply with the procedures specified in this clause. During PDU session/PDN connection establishment or modification procedure, the PCF shall subscribe to the "SCNN\_CH" policy control request trigger if not subscribed yet, as described in clause 4.2.6.4. + +When the SMF+PGW receives the policy decision from the PCF as defined in clause 4.2.4.1 or for a PDN connection maintained during a S-GW failure for a policy decision received as defined in clause 4.2.3.1 or 4.2.4.1, the SMF+PGW shall act as follows: + +- For MME/S4-SGSN triggered S-GW Restoration scenarios: + - When the SMF receives the policy decision from the PCF as defined in clause 4.2.4.1 for a PDN connection maintained during a S-GW failure, the SMF shall include the "ruleReports" attribute for the affected PCC rules and/or the "sessRuleReports" attribute for the affected session rules to report the failure within the SmPolicyUpdateContextData data structure and further include the information as follows. + - if the policy decision is related to one or more PCC rules, the SMF+PGW shall behave as defined in clause 4.2.4.15 with the "failureCode" attribute set to "AN\_GW\_FAILED". + - if the policy decision is related to one or more session rules the SMF+PGW shall behave as defined in clause 4.2.4.21 with the "sessRuleFailureCode" attribute set to "AN\_GW\_FAILED". +- For SMF+PGW triggered S-GW Restoration scenarios, if the SMF+PGW has accepted the procedure as per normal procedures but the PDN connection is not restored during an operator configured time period, the SMF+PGW shall behave as follows when the related timer expires: + - if the policy decision is related to the PCC rule(s), the SMF+PGW shall behave as defined in clause 4.2.4.15 with the "failureCode" attribute set to "RESOURCE\_ALLOCATION\_FAILURE" + - if the policy decision is related to the session rule(s), and the "SessQoSModEnforcementFailure" feature is not supported the SMF+PGW shall behave as defined in clause 4.2.4.21 with the "sessRuleFailureCode" attribute set to "SESSION\_RESOURCE\_ALLOCATION\_FAILURE". If the "SessQoSModEnforcementFailure" feature is supported, the "sessRuleFailureCode" attribute shall be set to "DEFAULT\_QOS\_MODIFICATION\_FAILURE" or "SESSION\_AMBR\_MODIFICATION\_FAILURE" based on the failure to enforce the corresponding policy decision. + +For MME/S4-SGSN triggered S-GW Restoration scenarios, while the S-GW restoration is in progress, if the SMF+PGW sends a request towards the PCF that is triggered by a different event (e.g. internal event at SMF+PGW), the SMF+PGW shall include the "anGwStatus" attribute set to "AN\_GW\_FAILED". + +Upon reception of the "failureCode" attribute set to "AN\_GW\_FAILED" and/or the "sessRuleFailureCode" attribute set to "AN\_GW\_FAILED" or the "anGwStatus" attribute set to "AN\_GW\_FAILED", the PCF shall not initiate any SM Policy association modification procedure, except if the SM Policy association modification procedure is initiated for the PCC rule removal only, for the given SM Policy association over N7 until the S-GW has recovered. + +If the SMF+PGW indicated AN\_GW\_FAILED previously according to the procedures described above or in annex B.3.3.3, the SMF+PGW shall inform the PCF when the S-GW has recovered by including "repPolicyCtrlReqTriggers" attribute set to the "SCNN\_CH" and the "servNfId" attribute including the S-GW identification within the "anGwAddr" attribute related to the restored or new S-GW. The PCF may after this update the SMF+PGW if necessary. + +NOTE 1: The PCF could reject requests from the AF and UDR when the "cause" attribute of the ProblemDetails data structure set to "AN\_GW\_FAILED", the "failureCode" attribute set to "AN\_GW\_FAILED" and/or the "sessRuleFailureCode" attribute set to "AN\_GW\_FAILED" or the "anGwStatus" attribute set to "AN\_GW\_FAILED" is received until the "repPolicyCtrlReqTriggers" attribute set to the "SCNN\_CH" is received. + +The SMF+PGW shall maintain the PDN connections affected by the S-GW failure and eligible for restoration for an operator configurable time period. Upon expiry of that time period, the SMF+PGW shall release the PDN connection and inform the PCF about the SM Policy association termination as specified in clause 4.2.5.2. + +NOTE 2: The PCF is not aware of which PDN connections are eligible for restoration. When the SMF+PGW detects a S-GW failure, the SMF+PGW requests the PCF to terminate SM Policy associations associated to PDN connections affected by the S-GW failure and not eligible for restoration. + +The SMF+PGW should maintain the GBR bearers of the PDN connections eligible for restoration for an operator configurable time period. Upon expiry of that time period, the SMF+PGW shall release GBR bearers that have not yet been restored and inform the PCF about the PCC rule removal as specified in clause 4.2.4.7. + +The SMF+PGW shall discard downlink packets received for a PDN connection maintained during a S-GW failure that has not yet been restored. + +The SMF+PGW shall delete the PDN connection locally when it receives an SM Policy association termination from the PCF as described in clause 4.2.4.3. + +### B.3.4.10 UE initiates a resource modification support + +In the case that the UE initiates a resource allocation procedure as defined in clause 6.5.3 or UE initiates a resource modification procedure as defined in clause 6.5.4 of 3GPP TS 24.301 [52], the SMF+PGW shall within the SmPolicyUpdateContextData data structure include the "RES\_MO\_RE" within the "repPolicyCtrlReqTriggers" attribute and shall include the UE request of specific QoS handling for selected SDF within the "ueInitResReq" attribute. Within the UeInitiatedResourceRequest data structure, the SMF+PGW shall include the "ruleOp" attribute, "packFiltInfo" attribute and "reqQos" attribute if applicable as follows: + +- When the UE requests to "Create new TFT", the SMF+PGW shall include the "ruleOp" attribute set to "CREATE\_PCC\_RULE", the "packFiltInfo" attribute and "reqQos" attribute containing the requested QoS for the new PCC rule. Each PacketFilterInfo instance shall contain one packet filter provided by the UE. If the PCF authorizes the request, the PCF shall create a new PCC rule by including the new packet filters within the service data flow template of the PCC rule. +- When the UE requests to "Add packet filters to existing TFT", SMF+PGW shall include the "ruleOp" attribute set to "MODIFY\_PCC\_RULE\_AND\_ADD\_PACKET\_FILTERS", the "pccRuleId" attribute including the PCC rule identifier corresponding the packet filter identifier provided by the UE and the "packFiltInfo" attribute. Each PacketFilterInfo instance shall contain one packet filter requested for addition. If the UE request includes the modified QoS information the SMF+PGW shall also include the "reqQos" attribute to indicate the updated QoS for the affected PCC rule(s). If the PCF authorizes the request, the PCF shall update the PCC rule by adding the new packet filters to the service data flow template of the PCC rule. +- When the UE requests to "Replace packet filters in existing TFT", SMF+PGW shall include the "ruleOp" attribute set to "MODIFY\_PCC\_RULE\_AND\_REPLACE\_PACKET\_FILTERS", the "pccRuleId" attribute including the PCC rule identifier corresponding the packet filter identifier provided by the UE and the "packFiltInfo" attribute. Each PacketFilterInfo instance shall within the "packFiltId" attribute include the replaced packet filter identifier assigned by the PCF corresponding to the packet filter identifier received from the UE and one packet filter requested for addition. If the UE request includes the modified QoS information the SMF+PGW shall also include the "reqQos" attribute to indicate the updated QoS for the affected PCC rule. If the PCF authorizes the request, the PCF shall update PCC rule by replacing the existing packet filter with the new packet filter within the service data flow template of the PCC rule. +- When the UE requests to "Delete packet filters from existing TFT", SMF+PGW shall include the "ruleOp" attribute set to "MODIFY\_PCC\_RULE\_AND\_DELETE\_PACKET\_FILTERS", the "pccRuleId" attribute including the PCC rule identifier corresponding the packet filter identifier provided by the UE and the "packFiltInfo" attribute. Each PacketFilterInfo instance shall within the "packFiltId" attribute include the removed packet filter identifier assigned by the PCF corresponding to the packet filter identifier received from the UE. If the UE request includes modified QoS information the SMF+PGW shall also include the "reqQos" + +attribute to indicate the updated QoS for the affected PCC rule(s). If the PCF authorizes the request, the PCF shall update PCC rule by removing the corresponding packet filters from the service data flow template of the PCC rule. + +- When the UE requests to "No TFT operation", SMF+PGW shall include the "ruleOp" attribute set to "MODIFY\_PCC\_RULE\_WITHOUT\_MODIFY\_PACKET\_FILTERS", the "pccRuleId" attribute including the PCC rule identifier corresponding the packet filter identifier provided by the UE and the modified QoS information within the "reqQos" attribute. +- When the UE requests to "Delete existing TFT", the SMF+PGW shall include the "ruleOp" attribute set to "DELETE\_PCC\_RULE", the "pccRuleId" attribute including the PCC rule identifier corresponding the packet filter identifier provided by the UE and the "packFiltInfo" attribute. The PCF shall remove the PCC rule when the PCF receives the request according to the PCC rule identifier. + +NOTE 1: The UE can only modify or delete packet filters that the UE has introduced and associated resources. The packet filter identifiers contained in the FlowInformation data structure are only used for packet filters created by the UE. + +The SMF+PGW shall calculate the requested GBR, for a GBR QCI, as the sum of the previously authorized GBR for the affected PCC rule, adjusted with the difference between the requested GBR for the EPS bearer and previously negotiated GBR for the EPS bearer. For the UE request to "Create new TFT", the GBR as requested by the UE for those filters shall be used. + +If the request covers all the PCC rules with a bearer binding to the same bearer, then the SMF+PGW may request a change to the QCI for existing packet filters. + +For the purpose of creating or modifying a packet filter, replacing and modifying packet filter, within the UeInitiatedResourceRequest instance, the SMF+PGW shall include the precedence information of the packet filter within the "precedence" attribute, and within each PacketFilterInfo instance, the SMF+PGW shall include the "packFiltCont" attribute, "tosTrafficClass" attribute, "spi" attribute, "flowLabel" attribute and "flowDirection" attribute set to the value(s) describing the packet filter provided by the UE. + +NOTE 2: The UE signalling with the network is governed by the applicable NAS signalling TS. The NAS 3GPP TS for a specific access may restrict the UE possibilities to make requests compared to what is stated above. + +If the PCF authorizes the request from the UE, the PCF shall construct a PCC rule(s) based on the UeInitiatedResourceRequest data structure. For "CREATE\_PCC\_RULE" or "MODIFY\_PCC\_RULE\_AND\_ADD\_PACKET\_FILTERS" operation, the PCF shall within the FlowInformation data structure include the assigned packet filter identifier within the "packFiltId" attribute. When the SMF+PGW derives the TFT based on the PCC rule, the SMF+PGW shall assign a new packet filter identifier for each added packet filter and keep the mapping between the packet filter identifier for the packet filter within the PCC rule and TFT sent to the UE. + +### B.3.4.11 Report of Access Charging Network Identifier + +The report of the Access Network Charging Identifier(s) is as specified in clause 4.2.4.13, with the difference that when the SMF assigns an Access Network Charging Identifier per EPS bearer/QoS flow, the SMF shall additionally include, within each AccNetChId instance, all the PCC rule identifier(s) associated to the provided Access Network Charging Identifier within the "refPccRuleIds" attribute. + +#### B.3.4.11a Detection of the SM Policy Association enabling URSP provisioning in EPS + +During UE Initial Attach with default PDN connection establishment in EPS, the UE and the SMF+PGW-C perform ePCO capability negotiation as defined in 3GPP TS 24.301 [52] to ensure that both, the network and the UE support URSP provisioning in EPS PCO. The SMF+PGW-C, when receives from the UE the Indication of URSP Provisioning Support in EPS PCO in the PDN connectivity request, and supports the feature "EpsUrsp" as defined in clause 5.8, the SMF+PGW-C shall select a PCF that supports the feature "EpsUrsp", shall create the SM Policy Association as described in clause B.3.2 and shall provide to the UE the Indication of URSP Provisioning Support in EPS PCO in the PDN Connectivity Accept message as defined in 3GPP TS 24.301 [52]. + +When the UE determines the URSP provisioning in EPS PCO is supported by the network, then the UE initiates the UE requested bearer modification procedure and includes the UE Policy Container ePCO, which will be further forwarded by the MME to the SMF+PGW-C. When the feature "EpsUrsp" is supported and the SMF+PGW-C receives the UE Policy Container ePCO, the SMF+PGW-C shall include the "UE\_POL\_CONT\_IND" within the "repPolicyCtrlReqTriggers" attribute and shall forward transparently the UE Policy Container to the PCF for the PDU session within the "uePolCon" attribute. + +The PCF for the PDU session then detects that the SM Policy Association enables the URSP provisioning in EPS and establishes a UE Policy Association with the PCF for the UE as described in 3GPP TS 29.525 [57] to transparently forward the received UE policy container. The PCF for the PDU session shall subscribe to RAT Type and/or Access-Type changes if not previously subscribed. + +To detect the 5GS to EPS handover or 5GS to EPS Idle Mode mobility (both referred as 5GS to EPS mobility with N26 in the present document) and if the "EpsUrsp" feature described in clause 5.8 is supported, the PCF for the PDU session shall subscribe to RAT Type and/or Access Type changes, if not previously subscribed. During 5GS to EPS mobility with N26, and if the "EpsUrsp" feature described in clause 5.8 is supported, the PCF for the PDU session associated with the SMF+PGW-C serving the PDN connection(s) determines whether 5GS to EPS mobility applies based on the received RAT and/or Access-Type change event. When the reported RAT and Access-Type change event indicates the UE is moving from 5GS to EPS, the PCF for the PDU session then determines that the SM Policy Association(s) enables the URSP provisioning in EPS and establishes a UE Policy Association with the PCF for the UE, if applicable, as described in 3GPP TS 29.525 [57]. + +### B.3.4.12 Reporting of UE Policy container for URSP provisioning in EPS + +When the feature "EpsUrsp" is supported and a UE policy container is received from the UE in EPC over a PDN connection, the SMF+PGW-C requests to update the SM Policy Association and provides to the PCF the received UE policy container. + +The Policy Control Request Trigger condition "UE\_POL\_CONT\_IND" is met when the SMF+PGW-C receives a UE policy container from the UE. The SMF+PGW-C shall include the "UE\_POL\_CONT\_IND" within the "repPolicyCtrlReqTriggers" attribute and shall transparently forward to the PCF the UE policy container encoded within the "uePolCont" attribute. The PCF shall transparently forward the UE policy container to the PCF for the UE in Npcf\_UEPolicyControl\_Update/Create Request as described in 3GPP TS 29.525 [57]. + +## B.3.5 Npcf\_SMPolicyControl\_Delete Service Operation + +### B.3.5.1 General + +When the UE deletes the PDN connection through the EPC network and the SMF+PGW-C shall behave as defined in clause 4.2.5.2 with the difference that the SMF+PGW-C shall include the information elements contained in the Delete Session Request message within the SmPolicyDeleteData data structure. + +NOTE: See Annex B.3.2.1 for location information. + +### B.3.5.2 EPS RAN NAS Cause Support + +If the RAN-NAS-Cause feature as defined in clause 5.8 is supported, and the PDN connection is established through the EPC network, the SMF shall report the RAN/NAS release cause(s) as specified in clause 4.2.5.4.7, with the exception that the received EPS RAN/NAS cause(s) are encoded within the "epsCause" attribute included in the RanNasRelCause data type. In this Release of the specification, the EPS release cause code information may include RAN/NAS release cause(s), a TWAN release cause or an untrusted WLAN release cause. + +## B.3.6 Provisioning and Enforcement of Policy Decisions + +### B.3.6.1 QoS mapping performed by the SMF+PGW-C + +When the UE is served by the 5GC, during PDU Session establishment and GBR QoS flow establishment, SMF+PGW-C performs EPS QoS mappings, from the 5G QoS parameters obtained from the PCF, and allocates TFT with the + +PCC rules obtained from the PCF. If a TFT is to be allocated for a downlink unidirectional EPS bearer mapped from a downlink only QoS Flow, the SMF+ PGW-C shall allocate a TFT packet filter that effectively disallows any useful uplink packet as described in clause 15.3.3.4 of 3GPP TS 23.060 [26]. The SMF+PGW-C sends the mapped QoS parameters and TFT to the UE via PCO. + +When the UE is served by the EPC, during PDN Connection establishment and dedicated bearer establishment/modification, SMF+ PGW-C performs EPS QoS mappings, from the 5G QoS parameters obtained from the PCF, and allocates TFT with the PCC rules obtained from the PCF. Other 5G QoS parameters corresponding to the PDN connection, e.g. Session-AMBR, and QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), are sent to UE in PCO. + +The SMF+PGW-C shall perform EPS QoS mappings as defined in clause 4.11.1.1 and Annex C in 3GPP TS 23.502 [3] as follows: + +- ignore the QNC and reflective QoS indication if received; +- for standardized 5QIs, the authorized 5QI is one to one mapped to the QCI; + +NOTE: The delay critical 5QI mapping to QCI is unspecified in the present specification. + +- for non-standardized 5QI, derive the authorized QCI based on the authorized 5QI and operator policy; +- one to one map the subscribed default QCI to the subscribed default 5QI; +- set the subscribed Session-AMBR according to operator policy (e.g. taking the value of subscribed APN-AMBR into account); and +- set the authorized APN-AMBR according to operator policy (e.g. taking the value of authorized Session-AMBR into account). + +When SMF+PGW-C is used for GERAN/UTRAN access during PDN Connection establishment, dedicated bearer establishment/modification and the feature "2G3GIWK" is supported, SMF+ PGW-C maps R99 QoS to/from EPS parameters as defined in Annex E of TS 23.401 [58]. The EPS and 5G QoS mapping is performed as defined in this clause. + +### B.3.6.2 Provisioning of Presence Reporting Area Information + +When the PRA or ePRA feature is supported, the PCF provides the SMF with Presence Reporting Area(s) information as specified in clause 4.2.6.5.6. When the UE is connected through the EPC/E-UTRAN network, the SMF+PGW-C initiates the appropriate PDN connection specific procedures specified in 3GPP TS 29.274 [37] to obtain or to deactivate the report of the presence state of a UE in a presence reporting area. + +NOTE: Homogeneous support of Presence Area reporting in EPC and 5GC networks is assumed. + +### B.3.6.3 Request and Report of Access Network information + +If the NetLoc feature as defined in clause 5.8 is supported, the PCF may request the SMF+PGW-C to report the access network information as defined in clause 4.2.6.5.4. + +If the AN\_INFO policy control request trigger is set, upon receiving the "lastReqRuleData" attribute with the "reqData" attribute with the value(s) MS\_TIME\_ZONE and/or USER\_LOC\_INFO and the "refPccRuleIds" attribute containing the PCC rule identifier(s) corresponding to the PCC rule(s) being installed, modified or removed: + +- If the "reqData" attribute indicates MS\_TIME\_ZONE and USER\_LOC\_INFO and the SMF+PGW-C determines that the access network does not support the access network information reporting, the SMF+PGW-C shall immediately inform the PCF by including the "netLocAccSupp" attribute set to "ANR\_NOT\_SUPPORTED" value in the "UeCampingRep" data structure returned in the "200 OK" response to the policy update notification request. +- If the "reqData" attribute only includes the MS\_TIME\_ZONE value and the SMF+PGW-C determines that the access network does not support the report of the UE time zone, the SMF+PGW-C shall immediately inform the PCF by including the "netLocAccSupp" attribute set to "TZR\_NOT\_SUPPORTED" value in the "UeCampingRep" data structure returned in the "200 OK" response to the policy update notification request. + +- If the "reqData" attribute only includes the USER\_LOC\_INFO value and the SMF+PGW-C determines that the access network does not support the report of the UE location, the SMF+PGW-C shall immediately inform the PCF by including the "netLocAccSupp" attribute set to "LOC\_NOT\_SUPPORTED" value in the "UeCampingRep" data structure returned in the "200 OK" response to the policy update notification request. +- If the "reqData" attribute includes the USER\_LOC\_INFO value and the MS\_TIME\_ZONE value, and the SMF+PGW-C determines the access network supports the report of UE location and/or UE time zone, the SMF+PGW-C shall apply appropriate procedures to the EPC access network to obtain the requested and supported access network information and shall report the available information as specified in clause 4.2.4.9. + +NOTE: The SMF+PGW determines whether the access network supports access network information reporting based on access type, RAT type and trusted/untrusted type of the access network. + +When the request to report access network information occurs within an EPS Fallback for IMS voice procedure, the SMF shall delay the report of access network information till the handover to EPS has been completed, as specified in 3GPP TS 23.502 [3], clause 4.13.6.1. + +### B.3.6.4 MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC + +If the "EnATSSS" feature defined in clause 5.8 is supported by both the SMF and the PCF, this scenario uses the Access Traffic Steering, Switching and Splitting functionality as described in clauses 4.2.2.17, 4.2.3.21, and 4.2.4.2 with the following specifics: + +- Multi access connectivity is provided using EUTRAN/EPC as 3GPP access and non-3GPP/5GC system as non-3GPP access. +- The ATSSS rules are derived from PCC rules and provided from the PGW-C+SMF to the UE over the non-3GPP access in 5GC system. +- When the UE requests a PDN connection in EPC indicating the association with a MA PDU session, the PDN connection may be handed over to 3GPP access in 5GC without affecting the ATSSS control. + +### B.3.6.5 MA PDU sessions with connectivity over 5GC and non-3GPP access to EPC + +If the "EnATSSS\_v2" feature defined in clause 5.8 is supported by both the SMF and the PCF, this scenario uses the Access Traffic Steering, Switching and Splitting functionality as described in clauses 4.2.2.17, 4.2.3.21, and 4.2.4.2 with the following specifics: + +- Multi access connectivity is provided using 5GS as 3GPP access and ePDG/EPC system as non-3GPP access. +- The ATSSS rules are derived from PCC rules and provided from the PGW-C+SMF to the UE over the 3GPP access in 5GC system. ATSSS rules may be provided to the UE via ePDG/EPC. +- When the UE requests a PDU session in 5GS indicating the association with a MA PDU session, the PDU session may be handed over to 3GPP access in EPC without affecting the ATSSS control. + +## B.3.7 Detection and handling of late arriving requests for interworking scenario + +### B.3.7.1 Handling of requests which collide with an existing SM Policy Association + +When the UE is served by the EPC and the SMF+PGW-C receives the origination time stamp from the originating entity (see clause 13.2 of 3GPP TS 29.274 [37]) during the PDN connection establishment, the SMF+PGW-C shall include the origination time stamp parameter within 3gpp-Sbi-Origination-Timestamp header in the HTTP POST request sent to the PCF, the PCF shall perform the behaviour as defined in clause 4.2.7.1. + +### B.3.7.2 Detection and handling of requests which have timed out at the originating entity + +When the UE is served by the EPC and the SMF+PGW-C receives the origination time stamp and the maximum wait time from the originating entity (see clause 13.3 of 3GPP TS 29.274 [37]), the SMF+PGW-C shall behave as defined in annex B.3.2 with the differences that the SMF+PGW-C: + +- shall include a 3gpp-Sbi-Sender-Timestamp header set to the value of the received origination time stamp; +- shall include a 3gpp-Sbi-Max-Rsp-Time header set to the value of the received maximum wait time. + +When the PCF receives the request from the SMF+PGW-C, the PCF shall behave as defined in clause 6.11.2 of 3GPP TS 29.500 [4]. + +--- + +## Annex C (normative): Wireless and wireline convergence access support + +### C.1 Scope + +This annex defines procedures for wireless and wireline convergence access support for 5GS. The specific stage 2 definition and related procedures are contained in 3GPP TS 23.316 [42]. The System Architecture for wireless and wireline convergence access is defined in 3GPP TS 23.501 [2]. + +--- + +### C.2 Npcf\_SMPolicyControl Service + +#### C.2.1 Service Description + +##### C.2.1.1 Overview + +Clause 4.1.1 applies with the exception that the UE is replaced by the 5G-RG and the W-AGF, which is acting as a UE towards the 5GC on behalf of the FN-RG. + +##### C.2.1.2 Service Architecture + +Clause 4.1.2 applies with the exception that roaming functionality does not apply for session policy control in this Release of the specification for 5G-RG users connecting to the 5GC via W-5GAN and FN-RG users. Roaming architecture is only applicable to a 5G-RG connecting to the 5GC via NG RAN. + +The 5G-RG may support LTE access connected to EPC and EPC interworking as defined in Annex B. + +##### C.2.1.3 Network Functions + +###### C.2.1.3.1 Policy Control Function (PCF) + +The PCF functionality defined in clause 4.1.3.1 shall apply with the exceptions described in this Annex. + +###### C.2.1.3.2 NF Service Consumers + +The functionality defined in clause 4.1.3.2 shall apply. + +The enforcement of the policy decisions applies for a single access PDU session over wireline access and multiaccess PDU sessions over wireline access and 3GPP with the exceptions described in this Annex. + +## C.2.1.4 Rules + +### C.2.1.4.1 PCC Rules + +Functionality as described in clause 4.1.4.2 applies with the following exceptions for the traffic of a PDU session over wireline access: + +- UL/DL Maximum Packet Loss Rate information does not apply. +- QoS Notification Control Information does not apply. + +### C.2.1.4.2 Gate Function + +Functionality as described in clause 4.2.6.2.2 applies with the following exceptions for the traffic of a PDU session over wireline access: + +- for the IPTV service, the "mulAccCtrl" attribute within the TrafficControlData data structure to which the PCC rule refers shall be used to describe if the gate is open or closed instead of the "flowStatus" attribute. + +## C.2.1.5 Policy control request trigger + +The Policy Control Request Triggers defined in clause 5.6.3.6 and related procedures are supported for a 5G-RG connecting to the 5GC via NG-RAN. + +The Policy Control Request Triggers defined in clause 5.6.3.6 are supported for a 5G-RG or FN-RG connecting to the 5GC via W-5GAN with the following not supporting ones: + +- PLMN\_CH +- SAREA\_CH +- SCNN\_CH +- PRA\_CH +- PS\_DA\_OFF +- QOS\_NOTIF +- RES\_RELEASE +- UE\_STATUS\_RESUME +- TSN\_BRIDGE\_INFO +- QOS\_MONITORING +- SCELL\_CH +- EPS\_FALLBACK +- DDN\_FAILURE +- DDN\_DELIVERY\_STATUS +- DDN\_FAILURE\_CANCELLATION +- DDN\_DELIVERY\_STATUS\_CANCELLATION +- USER\_LOCATION\_CH +- UE\_POL\_CONT\_IND + +Consequently, the procedures related to above policy control request triggers are not supported in the corresponding service operations. + +The PS\_DA\_OFF Policy Control Request Trigger may apply for the 5G-RG connecting to the 5GC via W-5GAN (see clause 4.2.2.8 and 4.2.4.8) in an hybrid access scenario (see clause C.3.6.2). + +The RES\_MO\_RE Policy Control Request trigger is not supported for a FN-RG as described in BBF TR-456 [47] and CableLabs WR-TR-5WWC-ARCH [48] specification. + +## C.2.1.6 UE IP address support + +The UE IP address support defined in clause 4.2.8 applies with the following additions, as specified in 3GPP TS 23.316 [57]: + +- IPv6 prefix other than default /64, including individual /128 IPv6 address, for IPv6 address allocation using DHCPv6; +- More than one UE IP addresses may be assigned to a PDU session and may be received by the PCF, where the UE IP addresses may correspond, to: + - a. multiple /128 IPv6 addresses; or + - b. an /64 default prefix used for IPv6 stateless autoconfiguration and IPv6 prefix(es) shorter than the default /64 prefix for IPv6 Prefix Delegation not including the /64 IPv6 Prefix (i.e. when the total IPv6 address space available for the PDU session cannot be aggregated into one single IPv6 prefix). + +--- + +## C.3 Service Operation + +### C.3.1 Introduction + +Clause 4.2.1 applies. + +### C.3.2 Npcf\_SMPolicyControl\_Create Service Operation + +#### C.3.2.1 General + +Clause 4.2.2.2 is applied with the following differences: + +- The allocated /128 IPv6 address or IPv6 /64 prefix or IPv6 prefix shorter than /64 is included within the "ipv6AddressPrefix" attribute. +- Request of Presence Reporting Area Change Report is not applicable when the 5G-RG or FN-RG connects to the 5GC via W-5GAN. +- Global Line ID including the line Id and either PLMN Id or operator Id is encoded within the "gli" attribute of the "n3gaLocation" attribute included in the "userLoc" attribute within the PolicyAssociationRequest data structure when the 5G-RG or FN-RG registers via W-5GBAN. +- The HFC Node Identifier is encoded in the "hfcNodeId" attribute of the "n3gaLocation" attribute included in the "userLocationInfo" attribute within the SmPolicyContextData data structure when the 5G-CRG or FN-CRG connects to the 5GC via W-5GCAN. +- The PEI that may be included within the "pei" attribute shall have one of the following representations: + - i. When the UE supports only wireline access, the PEI shall be a MAC address. + +NOTE: When the PEI includes an indication that the MAC address cannot be used as Equipment identifier, the PEI cannot be trusted for regulatory purposes and cannot be used for equipment based policy evaluation. + +- ii. When the UE supports at least one 3GPP access technology, the PEI shall be the allocated IMEI or IMEISV. + +- To support of Hybrid Access for a 5G-RG with a single PDU session as described in clause C.3.6.2.2, EPC interworking specific attributes and procedures apply as described in clause B.3.2; +- Access Traffic Steering, Switching and Splitting as defined in clause 4.2.2.17 is only applicable to the case that the 5G-RG establishes: + - a) Hybrid Access with a multi-access PDU Session connectivity via NG-RAN and W-5GAN, as described in clause C.3.6.2.3; or + - b) Hybrid Access with a multi-access PDU Session connectivity via EPC/E-UTRAN and W-5GAN, as described in clause C.3.6.2.4. +- The access network transmission technology for the wireline access may be encoded: + - i. within the "ratType" attribute of the SmPolicyContextData type; or + - ii. when Access Traffic Steering, Switching and Splitting is supported, within the "ratType" attribute of the SmPolicyContextData type, or within the "ratType" attribute of the AdditionalAccessInfo type. + +### C.3.2.2 IPTV service support + +If the PCF fetches the Multicast Access Control information from the UDR as defined in 3GPP TS 29.519 [15], the PCF shall authorize a PCC rule as defined in Annex C.3.6.1 and provision it to the SMF in the HTTP response message. + +## C.3.3 Npcf\_SMPolicyControl\_UpdateNotify Service Operation + +### C.3.3.1 General + +The descriptions in clause 4.2.3.1 are applied with the following differences: + +- To support Hybrid Access for a 5G-RG with a single PDU session as described in clause C.3.6.2.2, EPC interworking specific attributes and procedures apply as described in B.3.3; +- Access traffic steering, switching and splitting support as described in clause 4.2.3.21 is only applicable to the case that 5G-RG establishes: + - a) Hybrid Access with a multi-access PDU Session connectivity via NG-RAN and W-5GAN, as described in clause C.3.6.2.3; or + - b) Hybrid Access with a multi-access PDU Session connectivity via EPC/E-UTRAN and W-5GAN, as described in clause C.3.6.2.4. +- Request for the result of PCC rule removal is not applicable when the 5G-RG or FN-RG connects to the 5GC via W-5GAN. + +### C.3.3.2 IPTV service support + +If the PCF fetches the Multicast Access Control information from the UDR as defined in 3GPP TS 29.519 [15], for each impacted PDU session, the PCF shall authorize a PCC rule as defined in Annex C.3.6.1 and provision it to the SMF in the HTTP POST message. + +## C.3.4 Npcf\_SMPolicyControl\_Update Service Operation + +### C.3.4.1 General + +Clause 4.2.4.2 is applied with the following differences: + +- The released /128 IPv6 address or IPv6 /64 prefix or IPv6 prefix shorter than /64 is included within the "relIpv6AddressPrefix" attribute. + +- If the feature "MultiIpv6AddrPrefix" is supported, the additionally allocated IPv6 prefix may be included within the "addIpv6AddrPrefixes" attribute and the additional released IPv6 prefix may be included within the "addRelIpv6AddrPrefixes" attribute. If the "UnlimitedMultiIpv6Prefix" feature is supported, and if multiple allocated or released IPv6 prefixes are detected, the NF service consumer shall include the new allocated UE IPv6 prefixes within the "multiIpv6Prefixes" attribute and the released UE IPv6 prefixes within the "mutliRelIpv6Prefixes" attribute. +- RAN cause and/or the NAS cause information is not applicable when the 5G-RG or FN-RG connects the 5GC via W-5GAN. +- To support Hybrid Access for a 5G-RG with a single PDU session as described in clause C.3.6.2.2, EPC interworking specific attributes and procedures apply as described in B.3.4; +- When the report of access network information described in clause 4.2.4.9 includes the user location information, the "n3gaLocation" attribute shall be included in the "userLocationInfo" attribute and: + - a) if the UE connects via W-5GBAN access: + - Global Line Identifier shall be encoded in the "gli" attribute; and + - the "w5gbanLineType" attribute to indicate whether the W-5GBAN access is DSL or PON may be included; or + - b) if the UE connects via W-5GCAN access, the HFC Node Identifier shall be encoded in the "hfcNodeId" attribute. +- Access traffic steering, switching and splitting support as described in clause 4.2.4.25 is only applicable to the case that 5G-RG establishes: + - a) Hybrid Access with a multi-access PDU Session connectivity via NG-RAN and W-5GAN, as described in clause C.3.6.2.3; or + - b) Hybrid Access with a multi-access PDU Session connectivity via EPC/E-UTRAN and W-5GAN, as described in clause C.3.6.2.4. +- The access network transmission technology for the wireline access may be encoded: + - i. within the "ratType" attribute of the SmPolicyUpdateContextData type; or + - ii. when Access Traffic Steering, Switching and Splitting is supported, within the "ratType" attribute of the SmPolicyContextUpdateData type, or within the "ratType" attribute of the AdditionalAccessInfo type. + +### C.3.4.2 IPTV service support + +If the "WWC" feature is supported and "5G\_RG\_JOIN" and/or "5G\_RG\_LEAVE" are provisioned and when the SMF detects a 5G-RG has joined or left to an IP Multicast Group, the SMF shall send an HTTP POST message as defined in clause 4.2.4.2 and include the "5G\_RG\_JOIN" or "5G\_RG\_LEAVE" within the "repPolicyCtrlReqTriggers" attribute respectively and the received one or more IP multicast addressing information within the "mulAddrInfos" attribute. Within each IpMulticastAddressInfo data structure, the SMF shall include the destination IPv4 multicast address of the DL multicast flow within the "ipv4MulAddr" attribute and the source IPv4 address of the DL multicast flow within the "srcIpv4Addr" attribute if available or the destination IPv6 multicast address of the DL multicast flow within the "ipv6MulAddr" attribute and the source IPv6 address of the DL multicast flow within the "srcIpv6Addr" attribute if available. + +NOTE: The corresponding notification can be used by the PCF to manage Preview Rights related with an IP multicast flow corresponding to an IPTV channel by provisioning the corresponding PCC rule. In this case the PCF is responsible to remove the provisioned PCC rule when the preview duration has elapsed. + +## C.3.5 Npcf\_SMPolicyControl\_Delete Service Operation + +### C.3.5.1 General + +Clause 4.2.5.1 is applied with the following differences and limitations: + +- the "n3gaLocation" attribute shall be included in the "userLocationInfo" attribute and: + - a) if the UE connects via W-5GBAN access: + - Global Line Identifier shall be encoded in the "gli" attribute; and + - the "w5gbnLineType" attribute to indicate whether the W-5GBAN access is DSL or PON may be included; or + - b) if the UE connects via W-5GCAN access, + - the HFC Node Identifier shall be encoded in the "hfcNodeId" attribute; and + - the Global Cable Identifier may be encoded within the "gci" attribute. +- RAN cause and/or the NAS cause information is not applicable when the 5G-RG or FN-RG connects the 5GC via W-5GAN. + +## C.3.6 Provisioning and Enforcement of Policy Decisions + +### C.3.6.0 General + +Clause 4.2.6 applies with the following exceptions for the traffic of a PDU session over wireline access: + +- Policy provisioning and enforcement of authorized QoS per service data flow as described in clause 4.2.6.6.2 applies with the following differences: + - a) Determination of Maximum Packet Loss Rate for UL/DL does not apply. + - b) PCF does not request a notification when authorized GBR or delay critical GBR cannot be guaranteed or can be guaranteed again, i.e. "qnc" attribute does not apply. +- Provisioning of PCC Rules for Multimedia Priority Services is not supported. Clause 4.2.6.2.12 does not apply. +- Provisioning of PCC Rules for Mission Critical Services is not supported. Clause 4.2.6.2.19 does not apply. + +### C.3.6.1 IPTV service support + +If the "WWC" feature is supported by the SMF and PCF as defined in clause 5.8, when the PCF fetches the Multicast Access Control information from the UDR as defined in 3GPP TS 29.519 [15] applicable for a SUPI or Internal Group Id during the PDU session establishment or receives the notification of the Multicast Access Control information from the UDR as defined in 3GPP TS 29.519 [15] applicable for a SUPI(s) and/or Internal Group Id(s) and/or DNN/S-NSSAI combination(s) during the PDU session modification, the PCF authorizes the Multicast Access Control information. For each impacted PDU Session that corresponds to the Multicast Access Control information, the PCF shall determine the PCC rule(s) that are generated based on the Multicast Access Control information as follows: + +- for the multicast channel(s) which is allowed indicated in the Multicast Access Control information, the PCF shall include the corresponding multicast address(es) within the "flowInfos" attribute of the PCC rule and include the "mulAccCtrl" attribute set to "ALLOWED" within a Traffic Control Data instance which the PCC rule refers to. +- for the multicast channel(s) which is not allowed indicated in the Multicast Access Control information, the PCF shall include the corresponding multicast address(es) within the "flowInfos" attribute of the PCC rule and include the "mulAccCtrl" attribute set to "NOT\_ALLOWED" within a Traffic Control Data instance which the PCC rule refers to. + +NOTE 1: The "flowStatus" attribute is not included in this Traffic Control Data instance. The gate function is not applicable to IPTV service, and the control is done with the "mulAccCtrl" attribute. + +NOTE 2: Separate PCC Rules are used to convey the information related to allowed and not allowed multicast channel(s). + +## C.3.6.2 Hybrid Access support + +### C.3.6.2.1 General + +This clause specifies the support of policy control for Hybrid Access considering both, the support of single access PDU sessions and MA PDU sessions. + +Hybrid Access applies to a 5G-RG capable of connecting to: + +- both, NG-RAN and wireline access; and/or +- both, wireline access and EPC/E-UTRAN using EPC interworking as described in Annex B. + +Hybrid Access does not apply to FN-RG. + +### C.3.6.2.2 Hybrid Access with single PDU session + +Hybrid Access scenarios with single PDU sessions shall only use one of the two accesses, but the PDU session can be handover over between the two accesses. + +When the "WWC" feature is supported by the SMF and the PCF as defined in clause 5.8: + +- for a 5G-RG capable of connecting to the NG-RAN and the wireline access, the procedures specified in the main body of this specification apply, except: + - i. the UE is replaced by the 5G-RG; and + - ii. the non-3GPP access is replaced by the wireline access, as specified in this annex; +- for a 5G-RG capable of connecting to the wireline access and the EPC/E-UTRAN access, the procedures specified in the Annex B of this specification apply, except: + - i. the UE is replaced by the 5G-RG; and + - ii. the non-3GPP access is replaced by the wireline access. + +### C.3.6.2.3 Hybrid Access with MA PDU session connectivity over NG-RAN and wireline + +If the "WWC" and the "ATSSS" features are supported by the SMF and the PCF as defined in clause 5.8, this scenario uses the Access Traffic Steering, Switching and Splitting functionality as described in clauses 4.2.2.17, 4.2.3.21, and 4.2.4.25.8 with the following differences: + +- UE is replaced by 5G-RG. +- Non-3GPP access(es) is replaced by wireline access. + +### C.3.6.2.4 Hybrid Access with MA PDU session connectivity over EPC/E-UTRAN and wireline using EPC interworking scenarios + +If the "WWC" and the "ATSSS" features are supported by the SMF and the PCF as defined in clause 5.8, this scenario uses the Access Traffic Steering, Switching and Splitting functionality as described in clauses 4.2.2.17, 4.2.3.21, and 4.2.4.2 with the following specifics: + +- UE is replaced by 5G-RG. +- Non-3GPP access(es) is replaced by wireline access. + +- Multi access connectivity is provided using ATSSS using both, EPC (as 3GPP access) and wireline access/5GC system (as non-3GPP access), where: + - i. the ATSSS rules are derived from PCC rules and provided from the PGW-C+SMF to the 5G-RG over wireline access/5GC system; + - ii. when the 5G-RG requests a PDN connection in EPC indicating the association with a MA PDU session, the PDN connection may be handed over to 3GPP access in 5GC without affecting the ATSSS control. +- MA PDU Sessions of Ethernet PDU Session type where the 3GPP access corresponds to EPC/E-UTRAN are not applicable for 5G-RG. + +### C.3.6.3 Location Dependent Policies for trusted non-3GPP access + +To support location dependent policies when a UE connects using trusted non-3GPP access procedures via TNAP collocated with a 5G-RG, the PCF may retrieve/be notified by the UDR of the AF provided list of TNAP(s) in Service Parameter Data and/or the list of TNAP(s) provided within Session Management Policy Data as defined in 3GPP TS 29.519 [15]. In this case, the PCF may compare the TNAP ID(s) received from the UDR with the TNAP ID received in the user location information (if available) and may apply different policies depending on whether the UE is at a TNAP ID obtained from UDR or not. In case the PCF receives from the UDR TNAP ID(s) both in the Policy Data and in the Service Parameter Data, the PCF decides based on configuration whether to apply both or one of them. + +--- + +## Annex D(informative): Change history + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-10 | | | | | | TS skeleton of Session Management Policy Control Services specification | 0.0.0 | +| 2017-10 | CT3#92 | | | | | Inclusion of C3-175237, C3-175353 and editorial changes from Rapporteur | 0.1.0 | +| 2017-12 | CT3#93 | | | | | Inclusion of C3-176145, C3-176248, C3-176252, C3-176254, C3-176255, C3-176256, C3-176257, C3-176319, C3-176320, C3-176321, C3-176322, C3-176323 and editorial changes from Rapporteur | 0.2.0 | +| 2018-01 | CT3#94 | | | | | Inclusion of C3-180035, C3-180198, C3-180097, C3-180342, C3-180303, C3-180343, C3-180202, C3-180305, C3-180307, C3-180308, C3-180306, C3-180309, C3-180310, C3-1801311, C3-180312 | 0.3.0 | +| 2018-03 | CT3#95 | | | | | Inclusion of C3-181355, C3-181345, C3-181222, C3-181223, C3-181226, C3-181227 | 0.4.0 | +| 2018-04 | CT3#96 | C3-182515 | | | | Inclusion of C3-182056, C3-182318, C3-182322, C3-182463, C3-182325, C3-182327, C3-182330, C3-182331, C3-182132, C3-182332, C3-182324, C3-182482. | 0.5.0 | +| 2018-05 | CT3#97 | C3-183868 | | | | Inclusion of C3-183811, C3-183889, C3-183748, C3-183749, C3-183845, C3-183461, C3-183846, C3-183847, C3-183884, C3-183850, C3-183851, C3-183852, C3-183853, C3-183470, C3-183855, C3-183854, C3-183760, C3-183885, C3-183736, C3-183848, C3-183857, C3-183858, C3-183765, C3-183766, C3-183486, C3-183886, C3-183859, C3-183887, C3-183488, C3-183489, C3-183888, C3-183815, C3-183769, C3-183793, C3-183816, C3-183763, C3-183509, C3-183865, C3-183866, C3-183771, C3-183867, C3-183772, C3-183818, C3-183255, C3-183868, C3-183284 | 0.6.0 | +| 2018-06 | CT#80 | CP-181036 | | | | TS sent to plenary for approval | 1.0.0 | +| 2018-06 | CT#80 | CP-181036 | | | | TS approved by plenary | 15.0.0 | +| 2018-09 | CT#81 | CP-182015 | 0001 | 5 | F | Updates for TS 29.512 structure | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0002 | 4 | F | Update of Npcf_SMPolicyControl_Create Service Operation | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0003 | 5 | F | Update of Npcf_SMPolicyControl_UpdateNotify Service Operation | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0004 | 3 | F | Update of Npcf_SMPolicyControl_Update Service Operation | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0005 | 4 | F | Update of Npcf_SMPolicyControl_Delete Service Operation | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0006 | 5 | F | Multi-homing support | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0007 | 2 | F | Access Network Charging Identifier request and report | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0008 | 3 | F | Request result of PCC rule removal | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0009 | 3 | F | Request the successful resource allocation notification | 15.1.0 | +| 2018-09 | CT#81 | CP-182168 | 0010 | 6 | F | HTTP error handling procedure | 15.1.0 | +| 2018-09 | CT#81 | CP-182169 | 0011 | 7 | F | PCC Rule Error Handling | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0012 | 2 | F | Failure cases of Npcf_SMPolicyControl_Create Service Operation | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0013 | 5 | F | Failure cases of Npcf_SMPolicyControl_UpdateNotify Service Operation | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0014 | 2 | F | Failure cases of Npcf_SMPolicyControl_Update Service Operation | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0015 | 1 | F | Update of PCF and SMF function descriptions | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0016 | 3 | F | Rules, Session rules, PCC rules definition updates | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0017 | 2 | F | Policy Decision types Updates | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0018 | 4 | F | Policy control request trigger definition update | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0019 | 2 | F | Conditioned PCC rule update | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0020 | 2 | F | Conditioned session rule update | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0021 | 2 | F | IMS restoration support | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0022 | 9 | F | PRA support | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0023 | 5 | F | Update of steering the traffic to a local access of the data network | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0024 | 2 | F | Support for Ethernet PDU type | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0025 | 6 | F | Update of Provisioning of charging related information for PDU session | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0026 | 4 | F | UE requests specific QoS handling for selected SDF | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0027 | 6 | F | Provisioning of IP index information | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0028 | 1 | F | Update of Multimedia Priority Services | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0029 | 3 | F | Exclude the traffic from the session level usage monitoring | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0030 | 3 | F | Provisioning of specific QoS parameters together with 5QI | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0031 | 1 | F | Add Unspecified value to the FlowDirection data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0032 | 2 | F | Completion of definitions of UsageMonitoringData and AccuUsageReport | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0033 | 4 | F | Definition of FlowStatus data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0034 | 1 | F | Definition of RedirectAddressType data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0035 | 1 | F | Mandate the TrafficControlData decision | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0036 | 2 | F | Reflective QoS support | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0037 | 1 | F | Remove the DELETE method | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0038 | 1 | F | Remove the Packet Loss Rate from the QoS characteristics | 15.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------|--------| +| 2018-09 | CT#81 | CP-182015 | 0039 | 1 | F | Re-use the ARP data type from 29.571 | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0043 | 1 | F | Definition of DNAI | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0044 | 1 | F | Completion of ConditionData | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0045 | 1 | F | Completion of TrafficControlData data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182023 | 0046 | 1 | B | Trace activation | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0047 | 2 | F | Corrections on the notification URIs defined for the UpdateNotify | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0048 | 4 | F | Corrections on attributes and data types | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0049 | | F | Corrections on Supported Features | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0050 | 1 | F | Update custom operation for Npcf_SMPolicyControl_Update | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0051 | | F | Missing Slice Information | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0052 | 1 | F | Solution to IPv4 overlapping | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0053 | 1 | F | Description of Structured data types | 15.1.0 | +| 2018-09 | CT#81 | CP-182104 | 0054 | 1 | B | Support of PCC rule versioning | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0055 | 1 | F | Update of Sponsored data connectivity support | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0056 | 1 | F | Update of resource structure | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0057 | 1 | F | Correction on cardinality of array and map | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0058 | | F | Update of PccRule data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0059 | 1 | F | Open issues on Reused data types | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0060 | | F | DNAI report | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0061 | | F | Definition of maxPacketLossRate | 15.1.0 | +| 2018-12 | CT#82 | CP-183205 | 0063 | 6 | F | Correction to the AF influence traffic steering control | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0064 | 2 | F | Some corrections to the OpenAPI file | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0065 | 3 | F | Background data transfer support | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0066 | 4 | F | Clarification of default QoS | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0067 | 3 | F | Clarification of Maximum Packet Loss Rate authorization | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0068 | 1 | F | Clarification of PCC rule enforcement | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0069 | | F | Clarification of service data flow template | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0070 | | F | Correction to name of maximumDataBurstVolume attribute | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0071 | 1 | F | Correction to the QoS notification control authorization | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0072 | 3 | F | IMS dedicated signalling QoS flow | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0073 | 2 | F | Internal Group Id during the PDU session establishment | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0074 | 3 | F | Number of packet filters sent to the UE | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0075 | 2 | F | Packet filter identifier | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0076 | 1 | F | Remove two values of policy control request triggers in OpenAPI | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0077 | 1 | F | SM policy association termination | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0078 | 3 | F | The procedure of QoS notification control | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0079 | 4 | F | Architecture of 5GS and EPS interworking scenario support | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0083 | 2 | F | QoS mapping in 5GS and EPS interworking scenario | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0084 | | F | PCC Rules for MPS | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0086 | 2 | F | ExternalDocs field | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0089 | 1 | F | Correction of SMPolicyControl resource URI structure | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0089 | 2 | F | Correction of SMPolicyControl resource URI structure | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0090 | 1 | F | Definition on map keys in SmPolicyDecision | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0091 | 1 | F | Security field | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0092 | 1 | F | Correction of datatypes related to QoS | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0093 | 1 | F | Correction of 404 error information | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0094 | | F | Correction of API name | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0095 | 1 | F | Corrections of external references in OpenAPI | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0096 | 4 | F | Corrections on IP index provisioning | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0097 | 1 | F | Corrections misused data types, attributes and error definitions | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0098 | 2 | F | Application Error POLICY_CONTEXT_DENIED | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0099 | 2 | F | Corrections on RAN-NAS-Cause feature | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0100 | 1 | F | Missing Policy Control Request trigger for RAT Type Change | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0101 | 2 | F | Corrections on rule versioning | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0102 | 1 | F | Corrections for Npcf_SMPolicyControl_UpdateNotify service operation. | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0103 | | F | Default value for apiRoot | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0104 | 1 | F | Correction to RAN-NAS-Cause feature | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0105 | 1 | F | a new PolicyControlRequestTrigger for refQosIndication | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0106 | 1 | F | PCC rule error report triggerconvention | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0108 | 1 | F | Missing SponsoredConnectivity feature | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0109 | 2 | F | Correct DNAI change type in OpenAPI | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0110 | 3 | F | Selection of Predefined PCC Rule Base | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0111 | 3 | F | Correction to treatment of subscribed default QoS and authorized default QoS | 15.2.0 | +| 2018-12 | CT#82 | CP-183123 | 0113 | 1 | F | Address attribute for the network entity performing charging | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0115 | 1 | F | Status code update for Npcf_SMPolicyControl API | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0116 | 1 | F | CHF discovery and selection | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0117 | 1 | F | Condition Data | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0119 | | F | Correction to authDefaultQos attribute | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0120 | 1 | F | Correction to error handling | 15.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|--------------------------------------------------------------------------------------------|--------| +| 2018-12 | CT#82 | CP-183205 | 0121 | | F | Correction to Partial Success handling | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0122 | 2 | F | Correction to precedence of the PCC rule | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0123 | 2 | F | Correction to pre-defined PCC rule activation | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0124 | - | F | Correction to the terminology of QoS notification control | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0125 | 1 | F | Correction to the general descriptions of Provisioning and Enforcement of Policy Decisions | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0126 | 3 | F | Correction to the PCC rule definition | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0128 | 1 | F | Correction to the policy decision data definition | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0129 | 1 | F | Correction to the resource URI | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0130 | | F | Correction to the RuleReport data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0131 | 1 | F | Delay critical GBR resource type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0132 | 1 | F | Correction to the specific data type table | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0133 | 1 | F | HTTP custom headers | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0134 | 1 | F | Inactivity timer for emergency session | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0135 | 1 | F | Provisioning and deletion of the policy decision data | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0136 | 1 | F | QoS authorization for the emergency service | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0137 | 1 | F | Reference number alignment | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0138 | | F | Supported content types | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0140 | 2 | F | Adding "nullable" property to data types | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0141 | 2 | F | VolumeRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0142 | | F | Re-use PresenceInfoRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0143 | 1 | F | Re-use PacketLossRateRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0144 | 1 | F | Re-use MaxDataBurstVolRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0145 | | F | Re-use DurationSecRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0146 | | F | Re-use DateTimeRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0147 | | F | Re-use BitRateRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0148 | | F | Re-use AverWindowRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0150 | | F | Re-use 5QIPriorityLevelRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0151 | | F | FlowDirectionRm data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0152 | 1 | F | Correction to TrafficControlData data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0153 | 1 | F | Correction to the redirect function | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0154 | | F | Correction to the modification of an attribute with a value of type map | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0155 | 3 | F | Correction to SmPolicyDecision data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0157 | 1 | F | Correction to request rule data and request usage data | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0158 | 1 | F | Correction to QosData data structure | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0159 | 2 | F | Correction to Qos Characteristics | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0160 | 1 | F | Correction to PccRule data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0161 | | F | Correction to FlowInformation data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0162 | 1 | F | Correction to ChargingData data type | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0163 | | F | Correct the minProperties of the attributes | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0164 | 1 | F | Correct the minItems of the attributes | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0166 | 1 | F | delete UsageMonitoring in pccRule | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0167 | | F | rename the heading | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0168 | | F | incorrect description of online and offline | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0169 | | F | Location header | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0170 | 1 | F | API Version Update | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0172 | | F | Corrections to OpenAPI file | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0173 | 1 | F | Corrections of user location and session AMBR attributes | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0174 | 1 | F | Common data types | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0176 | 2 | F | Presence Info removal | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0177 | 2 | F | Correction of SmPolicyUpdateContext data type in OpenAPI | 15.2.0 | +| 2019-03 | CT#83 | CP-190111 | 0178 | 1 | F | The SMF may allow traffic to start before quota management for online charging | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0179 | 1 | F | Correction of application error codes | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0180 | | F | Corrections to qosDecs attribute | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0182 | | F | PCF resource cleanup | 15.3.0 | +| 2019-03 | CT#83 | CP-190135 | 0183 | 1 | F | Corrections on Traffic Steering Control | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0184 | 2 | F | Control of QoS parameters for default QoS Flow | 15.3.0 | +| 2019-03 | CT#83 | CP-190157 | 0185 | 1 | F | Correction to UE initiates a resource modification support | 15.3.0 | +| 2019-03 | CT#83 | CP-190136 | 0186 | 1 | F | Completion of the QoS control notification | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0187 | 1 | F | Correction to credit management session failure | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0188 | 1 | F | Correction to OpenAPI file | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0189 | 1 | F | Correction to Provisioning of Default Charging Method | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0191 | 1 | F | Correction to the access network information reporting | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0192 | | F | Correction to the ARP | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0193 | 1 | F | Correction to the QoS data decision | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0194 | 2 | F | Correction to the QoS mapping performed by the SMF+PGW-C | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0195 | 2 | F | Correction to the SmPolicyDecision data type | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0197 | 2 | F | Correction to number of supported Packet Filters for signalled QoS rules | 15.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| 2019-03 | CT#83 | CP-190111 | 0198 | 1 | F | PCC rule enforcement | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0199 | 2 | F | Policy Update When UE suspends | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0200 | 1 | F | Correction to the QoS characteristics | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0201 | 1 | F | Remove two values of failure codes | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0205 | 1 | F | Alignment of attributes | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0206 | 2 | F | HTTP response code 204 for QoS Notification | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0208 | 1 | F | Corrections on Charging Characteristics | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0209 | | F | Correction on Provisioning of Charging Address | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0210 | 1 | F | Corrections for Location Change Policy Control Request Triggers | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0211 | 1 | F | AC_TY_CH related information | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0212 | | F | Time Zone Change Policy Control Request Trigger | 15.3.0 | +| 2019-03 | CT#83 | CP-190111 | 0213 | | F | Corrections on Reflective QoS | 15.3.0 | +| 2019-03 | CT#83 | CP-190167 | 0216 | | F | OpenAPI version number update | 15.3.0 | +| 2019-03 | CT#83 | CP-190121 | 0203 | 2 | B | Access Type conditioned Session-AMBR | 16.0.0 | +| 2019-03 | CT#83 | CP-190121 | 0207 | 1 | B | Multiple IPv6 prefixes allocated or released in PolicyUpdate request | 16.0.0 | +| 2019-03 | CT#83 | CP-190121 | 0215 | | F | OpenAPI version number update | 16.0.0 | +| 2019-06 | CT#84 | CP-191072 | 0218 | 2 | A | Correction of PCC rule base activation | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0220 | 1 | A | Corrections in main body of the specification | 16.1.0 | +| 2019-06 | CT#84 | CP-191089 | 0222 | 2 | B | DN Authorization for Policy Control | 16.1.0 | +| 2019-06 | CT#84 | CP-191087 | 0223 | 1 | B | General description for the support for traffic switching, steering and splitting | 16.1.0 | +| 2019-06 | CT#84 | CP-191087 | 0225 | 1 | B | Session Rule support for traffic switching, steering and splitting | 16.1.0 | +| 2019-06 | CT#84 | CP-191071 | 0227 | 3 | A | Correction to 5GS-EPS interworking support | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0229 | 1 | A | Correction to FlowInformation and rule versioning support | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0231 | 2 | A | Correction to PacketErrRate data type | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0233 | | A | Correction to PartialSuccessReport | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0237 | 2 | A | Correction to the PCC bound to the default QoS flow | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0241 | 1 | A | MBR of Non-GBR type 5QI | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0243 | 3 | A | Precedence of PCC rule | 16.1.0 | +| 2019-06 | CT#84 | CP-191071 | 0245 | 4 | A | Session Rule error handling | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0247 | 2 | A | Usage limitation of the time-conditioned PCC rule | 16.1.0 | +| 2019-06 | CT#84 | CP-191089 | 0248 | 2 | B | Multiple IPv6 prefixes report for Multi-homing support | 16.1.0 | +| 2019-06 | CT#84 | CP-191087 | 0249 | 4 | B | PCC support for traffic switching, steering and splitting | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0254 | 1 | A | Miscellaneous corrections | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0256 | 3 | A | Correction to Npcf_SMPolicyControl_UpdateNotify service operation | 16.1.0 | +| 2019-06 | CT#84 | CP-191089 | 0257 | 1 | F | Update the redirection server address to support dual stack UE | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0262 | | A | Precedence of OpenAPI file | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0263 | 1 | A | Deprecating API version | 16.1.0 | +| 2019-06 | CT#84 | CP-191071 | 0264 | 2 | B | AF acknowledgement to be expected | 16.1.0 | +| 2019-06 | CT#84 | CP-191071 | 0265 | 2 | B | UE IP address preservation indication | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0269 | 1 | A | Corrections to conditioned PCC rule | 16.1.0 | +| 2019-06 | CT#84 | CP-191089 | 0273 | 2 | F | Correction to IPv6 Multihoming support | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0275 | | A | Correction of RuleReport type | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0283 | 1 | A | Correction to access network information report | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0285 | 1 | A | Correction to FailureCode data type | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0291 | 1 | A | Correction to UE_STATUS_RESUME | 16.1.0 | +| 2019-06 | CT#84 | CP-191089 | 0293 | 1 | B | Race condition handling | 16.1.0 | +| 2019-06 | CT#84 | CP-191085 | 0294 | 1 | B | Npcf_SMPolicyControl service extension of 5WVVC | 16.1.0 | +| 2019-06 | CT#84 | CP-191072 | 0296 | 1 | F | Copyright Note in YAML file | 16.1.0 | +| 2019-06 | CT#84 | CP-191101 | 0298 | 1 | F | API version update | 16.1.0 | +| 2019-09 | CT#85 | CP-192167 | 0302 | 1 | B | Handling of requests colliding with an existing context | 16.2.0 | +| 2019-09 | CT#85 | CP-192178 | 0303 | 1 | B | Adding NID as input for policy decisions | 16.2.0 | +| 2019-09 | CT#85 | CP-192156 | 0304 | 1 | B | Support a set of MAC addresses in traffic filter | 16.2.0 | +| 2019-09 | CT#85 | CP-192155 | 0305 | 1 | B | Support of IMS restoration | 16.2.0 | +| 2019-09 | CT#85 | CP-192155 | 0306 | 1 | B | Support of Npcf_PolicyAuthorization invocation of priority sharing | 16.2.0 | +| 2019-09 | CT#85 | CP-192142 | 0308 | 2 | A | Correction to Resource Sharing | 16.2.0 | +| 2019-09 | CT#85 | CP-192176 | 0311 | 1 | B | Support of wireline and wireless access convergence, NFs | 16.2.0 | +| 2019-09 | CT#85 | CP-192142 | 0313 | | A | Correction to appReloc attribute | 16.2.0 | +| 2019-09 | CT#85 | CP-192142 | 0315 | 1 | A | Correction to GBR type default QoS flow | 16.2.0 | +| 2019-09 | CT#85 | CP-192142 | 0317 | 1 | A | Correction to interworking between the 5GC and EPC | 16.2.0 | +| 2019-09 | CT#85 | CP-192142 | 0319 | 2 | A | Correction to serving node change | 16.2.0 | +| 2019-09 | CT#85 | CP-192142 | 0323 | 1 | A | Correction to UE requested resource modification | 16.2.0 | +| 2019-09 | CT#85 | CP-192142 | 0325 | | A | Include ipDomain within SmPolicyUpdateContextData data type | 16.2.0 | +| 2019-09 | CT#85 | CP-192142 | 0327 | 1 | A | Correction to Usage Monitoring Control | 16.2.0 | +| 2019-09 | CT#85 | CP-192142 | 0329 | 1 | A | Packet filters for reflective QoS | 16.2.0 | +| 2019-09 | CT#85 | CP-192153 | 0330 | | B | PCC rule attribute correction for ATSSS | 16.2.0 | +| 2019-09 | CT#85 | CP-192156 | 0331 | | B | Correction to time conditioned PCC rule | 16.2.0 | +| 2019-09 | CT#85 | CP-192152 | 0333 | 1 | B | Npcf_SMPolicyControl_Create Service Operation Update of 5WVVC Correction to time conditioned PCC rule | 16.2.0 | +| 2019-09 | CT#85 | CP-192152 | 0334 | 1 | B | Npcf_SMPolicyControl_UpdateNotify Service Operation Update of 5WVVC | 16.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------|--------| +| 2019-09 | CT#85 | CP-192152 | 0335 | 1 | B | Npcf_SMPolicyControl_Update Service Operation Update of 5WVC | 16.2.0 | +| 2019-09 | CT#85 | CP-192152 | 0336 | 1 | B | Npcf_SMPolicyControl_Delete Service Operation Update of 5WVC | 16.2.0 | +| 2019-09 | CT#85 | CP-192152 | 0337 | 2 | B | IPTV support | 16.2.0 | +| 2019-09 | CT#85 | CP-192175 | 0338 | 2 | B | QoS Monitoring support for URLLC | 16.2.0 | +| 2019-09 | CT#85 | CP-192171 | 0339 | 2 | B | PCC rule decision enhancement for supporting xBDT | 16.2.0 | +| 2019-09 | CT#85 | CP-192173 | 0341 | | B | OpenAPI version update TS 29.512 R-16 | 16.2.0 | +| 2019-12 | CT#86 | CP-193213 | 0345 | 2 | F | Increasing the maximum MDBV value | 16.3.0 | +| 2019-12 | CT#86 | CP-193181 | 0346 | 1 | B | Open issue for AddrPreservation feature | 16.3.0 | +| 2019-12 | CT#86 | CP-193184 | 0349 | 1 | A | Correction to the usage monitoring control | 16.3.0 | +| 2019-12 | CT#86 | CP-193184 | 0351 | 2 | A | Correction to the traffic steering control | 16.3.0 | +| 2019-12 | CT#86 | CP-193193 | 0352 | 2 | B | Usage Monitoring Control for ATSSS | 16.3.0 | +| 2019-12 | CT#86 | CP-193210 | 0353 | 1 | B | Correction to handling of requests colliding with an existing context | 16.3.0 | +| 2019-12 | CT#86 | CP-193223 | 0354 | 1 | B | Multiple BDT Policies | 16.3.0 | +| 2019-12 | CT#86 | CP-193223 | 0355 | 5 | B | New cause value of association termination for xBDT | 16.3.0 | +| 2019-12 | CT#86 | CP-193202 | 0356 | 6 | B | QoS Handling for V2X Communication | 16.3.0 | +| 2019-12 | CT#86 | CP-193197 | 0358 | 4 | B | Serving 4G only UEs by SMF+PGW-C | 16.3.0 | +| 2019-12 | CT#86 | CP-193196 | 0359 | | B | Add reference of 29.514 | 16.3.0 | +| 2019-12 | CT#86 | CP-193181 | 0360 | 1 | B | Report frequency of QoS monitoring | 16.3.0 | +| 2019-12 | CT#86 | CP-193236 | 0361 | 2 | B | Line Identifier | 16.3.0 | +| 2019-12 | CT#86 | CP-193193 | 0364 | 2 | B | remove EN related to SteeringFunctionality datatype | 16.3.0 | +| 2019-12 | CT#86 | CP-193197 | 0366 | | F | Correct the Cardinality of redirectInfo | 16.3.0 | +| 2019-12 | CT#86 | CP-193223 | 0367 | 1 | D | Background data transfer support editorials | 16.3.0 | +| 2019-12 | CT#86 | CP-193222 | 0368 | 2 | B | Transport of TSN information and containers between SMF and PCF | 16.3.0 | +| 2019-12 | CT#86 | CP-193222 | 0369 | 2 | B | Transport of TSC assistance information between SMF and PCF | 16.3.0 | +| 2019-12 | CT#86 | CP-193184 | 0371 | | A | CHF addresses as apiRoot in the form of an FQDN | 16.3.0 | +| 2019-12 | CT#86 | CP-193259 | 0372 | 4 | B | Indication of PS to CS Handover for 5G SRVCC from SMF to PCF | 16.3.0 | +| 2019-12 | CT#86 | CP-193215 | 0373 | 2 | B | Coverage and Handover Enhancements for Media (CHEM) | 16.3.0 | +| 2019-12 | CT#86 | CP-193197 | 0374 | 1 | B | MCS Priority Level | 16.3.0 | +| 2019-12 | CT#86 | CP-193197 | 0375 | 1 | F | Removal of non-breaking spaces, TABs and \$ref descriptions | 16.3.0 | +| 2019-12 | CT#86 | CP-193197 | 0377 | 2 | B | Request of SM Policy Association Termination during the Update procedure | 16.3.0 | +| 2019-12 | CT#86 | CP-193184 | 0379 | | A | Correction to delete a PCC rule requested by the UE | 16.3.0 | +| 2019-12 | CT#86 | CP-193184 | 0381 | | A | Termination action | 16.3.0 | +| 2019-12 | CT#86 | CP-193233 | 0382 | 1 | B | AMF change in the HR scenario | 16.3.0 | +| 2019-12 | CT#86 | CP-193197 | 0383 | 2 | B | Same PCF selection for the same UE ID, S-NSSAI and DNN combination | 16.3.0 | +| 2019-12 | CT#86 | CP-193238 | 0384 | 2 | B | Correction to the QoS monitoring Control | 16.3.0 | +| 2019-12 | CT#86 | CP-193212 | 0385 | | F | Update of API version and TS version in OpenAPI file | 16.3.0 | +| 2019-12 | CT#86 | CP-193197 | 0386 | | F | Correct the redirection server address to support dual stack UE | 16.3.0 | +| 2019-12 | CT#86 | CP-193184 | 0388 | 1 | A | Correction of AF Charging Identifier data type | 16.3.0 | +| 2019-12 | CT#86 | CP-193191 | 0389 | 2 | B | Clarification of PEI format, TS 29.512 | 16.3.0 | +| 2019-12 | CT#86 | CP-193230 | 0390 | 2 | B | HFC node Id in Location information, TS 29.512 | 16.3.0 | +| 2019-12 | CT#86 | CP-193197 | 0393 | 1 | B | Add reference to TS 29.524 | 16.3.0 | +| 2020-03 | CT#87e | CP-200207 | 0402 | 1 | B | Update of the same PCF selection | 16.4.0 | +| 2020-03 | CT#87e | CP-200207 | 0403 | | B | DNN Clarification | 16.4.0 | +| 2020-03 | CT#87e | CP-200207 | 0404 | 1 | B | Cell change trigger | 16.4.0 | +| 2020-03 | CT#87e | CP-200207 | 0405 | 1 | B | Correction to the policy decision data and condition data | 16.4.0 | +| 2020-03 | CT#87e | CP-200207 | 0406 | 1 | B | Reallocation of credit | 16.4.0 | +| 2020-03 | CT#87e | CP-200207 | 0407 | 1 | B | UE initiated resource modification correction | 16.4.0 | +| 2020-03 | CT#87e | CP-200204 | 0408 | 2 | B | Complete the PCC procedure for ATSSS | 16.4.0 | +| 2020-03 | CT#87e | CP-200203 | 0410 | 1 | B | Complete the IPTV support | 16.4.0 | +| 2020-03 | CT#87e | CP-200203 | 0411 | 1 | B | Policy Control Request Triggers for wireline access | 16.4.0 | +| 2020-03 | CT#87e | CP-200203 | 0412 | 1 | B | The data type of GlobalLineId | 16.4.0 | +| 2020-03 | CT#87e | CP-200212 | 0414 | 1 | B | Complete the PCC procedure for V2XARC | 16.4.0 | +| 2020-03 | CT#87e | CP-200202 | 0415 | 1 | B | Complete the QoS Monitoring | 16.4.0 | +| 2020-03 | CT#87e | CP-200218 | 0416 | 1 | B | Indication of traffic correlation | 16.4.0 | +| 2020-03 | CT#87e | CP-200207 | 0417 | 1 | B | DNN selection mode | 16.4.0 | +| 2020-03 | CT#87e | CP-200204 | 0419 | 2 | B | interworking with EPS for ATSSS | 16.4.0 | +| 2020-03 | CT#87e | CP-200285 | 0420 | 3 | B | Additional Access Type for ATSSS | 16.4.0 | +| 2020-03 | CT#87e | CP-200231 | 0423 | 1 | B | Report of EPS Fallback | 16.4.0 | +| 2020-03 | CT#87e | CP-200226 | 0424 | 1 | B | Clarification of DS-TT and NW-TT ports identification | 16.4.0 | +| 2020-03 | CT#87e | CP-200226 | 0425 | 1 | B | Clarification of DS-TT and NW-TT ports management information | 16.4.0 | +| 2020-03 | CT#87e | CP-200218 | 0426 | | B | PCF provisioning of TSN related Policy Control Request triggers | 16.4.0 | +| 2020-03 | CT#87e | CP-200218 | 0427 | 1 | B | TSCAI input container and TSN QoS container | 16.4.0 | +| 2020-03 | CT#87e | CP-200214 | 0428 | | F | OpenAPI: usage of the "tags" keyword | 16.4.0 | +| 2020-03 | CT#87e | CP-200214 | 0429 | | F | Enumerations and "nullable" keyword | 16.4.0 | +| 2020-03 | CT#87e | CP-200215 | 0430 | | F | Referencing enumerations in clause 5.6.1 | 16.4.0 | +| 2020-03 | CT#87e | CP-200200 | 0431 | | B | CHF set and instance Id in charging information | 16.4.0 | +| 2020-03 | CT#87e | CP-200216 | 0435 | | F | 29.512 Rel-16 Update of OpenAPI version and TS version in externalDocs field | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------|--------| +| 2020-06 | CT#88e | CP-201217 | 0437 | 1 | A | Correction to attributes interGrpIds and appDetectionInfos | 16.5.0 | +| 2020-06 | CT#88e | CP-201238 | 0438 | | F | Correction to V2XARC | 16.5.0 | +| 2020-06 | CT#88e | CP-201217 | 0440 | | A | String format of flow information | 16.5.0 | +| 2020-06 | CT#88e | CP-201217 | 0444 | 1 | A | Notification URI | 16.5.0 | +| 2020-06 | CT#88e | CP-201233 | 0445 | 1 | B | Cause Mapping of VALIDATION_CONDITION_NOT_MET | 16.5.0 | +| 2020-06 | CT#88e | CP-201229 | 0446 | | B | ATSSS rule derivation | 16.5.0 | +| 2020-06 | CT#88e | CP-201229 | 0447 | 3 | B | QoS support for ATSSS | 16.5.0 | +| 2020-06 | CT#88e | CP-201229 | 0448 | 1 | B | Enable removing the policy decision | 16.5.0 | +| 2020-06 | CT#88e | CP-201252 | 0449 | 2 | F | Correction to bridge Information report | 16.5.0 | +| 2020-06 | CT#88e | CP-201252 | 0450 | 2 | F | Correction to Port Management Information Container exchange | 16.5.0 | +| 2020-06 | CT#88e | CP-201271 | 0451 | 2 | F | Correction to Provisioning of TSCAI input information and TSC QoS related data | 16.5.0 | +| 2020-06 | CT#88e | CP-201252 | 0452 | 1 | B | PCC rule information update for vertical | 16.5.0 | +| 2020-06 | CT#88e | CP-201252 | 0453 | 1 | B | PCF functionality update for TSN | 16.5.0 | +| 2020-06 | CT#88e | CP-201228 | 0454 | | B | General update of Annex C | 16.5.0 | +| 2020-06 | CT#88e | CP-201262 | 0455 | 3 | B | Support of full Frame Routing feature | 16.5.0 | +| 2020-06 | CT#88e | CP-201228 | 0456 | 1 | B | The data type of GlobalLineId | 16.5.0 | +| 2020-06 | CT#88e | CP-201338 | 0457 | 3 | B | Procedure of policy provisioning of QoS monitoring control | 16.5.0 | +| 2020-06 | CT#88e | CP-201213 | 0458 | 1 | F | QoS Monitoring Control Data correction | 16.5.0 | +| 2020-06 | CT#88e | CP-201217 | 0463 | 1 | A | timeUsage in Accumulated Usage Report | 16.5.0 | +| 2020-06 | CT#88e | CP-201229 | 0464 | | F | Support the update of SteeringFunctionality | 16.5.0 | +| 2020-06 | CT#88e | CP-201228 | 0465 | | B | Not to support Mission Critical Services | 16.5.0 | +| 2020-06 | CT#88e | CP-201228 | 0468 | | F | Removal of MAC address | 16.5.0 | +| 2020-06 | CT#88e | CP-201244 | 0470 | | F | Removal of unbreakable space and TAB | 16.5.0 | +| 2020-06 | CT#88e | CP-201213 | 0471 | 1 | B | Solving Editor's note on UL CL | 16.5.0 | +| 2020-06 | CT#88e | CP-201228 | 0472 | 1 | B | Hybrid Access Support | 16.5.0 | +| 2020-06 | CT#88e | CP-201228 | 0473 | 1 | B | Untrusted PEI | 16.5.0 | +| 2020-06 | CT#88e | CP-201228 | 0474 | 1 | B | RAT type for WWC | 16.5.0 | +| 2020-06 | CT#88e | CP-201229 | 0475 | 1 | B | PS Data Off for a MA PDU session | 16.5.0 | +| 2020-06 | CT#88e | CP-201233 | 0476 | 1 | F | Correction to Reallocation of Credit | 16.5.0 | +| 2020-06 | CT#88e | CP-201233 | 0477 | 1 | B | Local traffic routing policy | 16.5.0 | +| 2020-06 | CT#88e | CP-201238 | 0478 | 1 | F | Referencing alternative QoS in clause 4.2.6.2.1 | 16.5.0 | +| 2020-06 | CT#88e | CP-201252 | 0479 | 1 | B | QoS information for Time Sensitive Networking | 16.5.0 | +| 2020-06 | CT#88e | CP-201252 | 0480 | 1 | B | Update of TSN related PCRTs | 16.5.0 | +| 2020-06 | CT#88e | CP-201252 | 0481 | 1 | B | Completion of traffic correlation | 16.5.0 | +| 2020-06 | CT#88e | CP-201217 | 0482 | 1 | A | Correction to NetLoc feature | 16.5.0 | +| 2020-06 | CT#88e | CP-201217 | 0484 | 1 | A | Correction to PS Data Off | 16.5.0 | +| 2020-06 | CT#88e | CP-201213 | 0486 | 1 | F | Correct data type used in QoS monitoring | 16.5.0 | +| 2020-06 | CT#88e | CP-201244 | 0487 | 1 | F | Storage of YAML files in ETSI Forge | 16.5.0 | +| 2020-06 | CT#88e | CP-201257 | 0489 | 1 | B | DDN Failure and Delivery Policy Control Request triggers | 16.5.0 | +| 2020-06 | CT#88e | CP-201272 | 0490 | 1 | B | Introduction of Bridge management information | 16.5.0 | +| 2020-06 | CT#88e | CP-201267 | 0491 | 1 | B | Clarification of PCF behaviour to honor UE provided maximum packet filter support | 16.5.0 | +| 2020-06 | CT#88e | CP-201233 | 0492 | 1 | B | Policy decision and condition data status report | 16.5.0 | +| 2020-06 | CT#88e | CP-201263 | 0494 | 1 | B | New value of the ATSSS capability | 16.5.0 | +| 2020-06 | CT#88e | CP-201264 | 0495 | 1 | B | PCC rule for Non-MPTCP traffic | 16.5.0 | +| 2020-06 | CT#88e | CP-201265 | 0496 | 1 | B | Steering modes for GBR traffic | 16.5.0 | +| 2020-06 | CT#88e | CP-201252 | 0499 | 1 | B | Correct the reference of the port management info container | 16.5.0 | +| 2020-06 | CT#88e | CP-201256 | 0501 | 1 | F | URI of the Npcf_SMPolicyControl service | 16.5.0 | +| 2020-06 | CT#88e | CP-201233 | 0503 | 1 | F | Correction to the usage of appReloc attribute | 16.5.0 | +| 2020-06 | CT#88e | CP-201217 | 0505 | 1 | A | Correction to session rule error report | 16.5.0 | +| 2020-06 | CT#88e | CP-201297 | 0506 | 2 | B | Clarification on the target of QoS Monitoring report | 16.5.0 | +| 2020-06 | CT#88e | CP-201213 | 0507 | 1 | F | Correction to attributes related to QosMonitoring | 16.5.0 | +| 2020-06 | CT#88e | CP-201229 | 0508 | | F | Clarification on the value of 3gLoad attribute | 16.5.0 | +| 2020-06 | CT#88e | CP-201266 | 0511 | 1 | B | Application Id in a PCC rule for ATSSS | 16.5.0 | +| 2020-06 | CT#88e | CP-201273 | 0513 | 1 | B | QoS parameter mapping | 16.5.0 | +| 2020-06 | CT#88e | CP-201217 | 0517 | 1 | A | Not supporting simultaneous online and offline charging | 16.5.0 | +| 2020-06 | CT#88e | CP-201244 | 0518 | | F | Optionality of ProblemDetails | 16.5.0 | +| 2020-06 | CT#88e | CP-201232 | 0519 | | F | "PCSCF-Restoration-Enhancement" feature corrections | 16.5.0 | +| 2020-06 | CT#88e | CP-201244 | 0520 | 1 | F | Supported headers, Resource Data type, Operation Name and yaml mapping | 16.5.0 | +| 2020-06 | CT#88e | CP-201247 | 0522 | | F | Reallocation of credit reporting to the PCF | 16.5.0 | +| 2020-06 | CT#88e | CP-201255 | 0524 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.5.0 | +| 2020-06 | CT#88e | CP-201282 | 0525 | | F | Correcting feature numbers | 16.5.0 | +| 2020-09 | CT#89e | CP-202068 | 0527 | 1 | F | Correction of the alternative QoS profile | 16.6.0 | +| 2020-09 | CT#89e | CP-202052 | 0529 | | A | rellpv4Address attribute correction | 16.6.0 | +| 2020-09 | CT#89e | CP-202052 | 0531 | 1 | A | Correction to QosData | 16.6.0 | +| 2020-09 | CT#89e | CP-202052 | 0533 | 2 | A | Correction to QoS Flow usage negotiation | 16.6.0 | +| 2020-09 | CT#89e | CP-202052 | 0535 | 1 | A | Correction to RedirectInformation | 16.6.0 | +| 2020-09 | CT#89e | CP-202209 | 0538 | 1 | F | Correction to policy update when UE suspends | 16.6.0 | +| 2020-09 | CT#89e | CP-202059 | 0539 | | F | Correction to policy control request triggers for wireline access | 16.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------|--------| +| 2020-09 | CT#89e | CP-202059 | 0553 | | F | Corrections related to framed routes | 16.6.0 | +| 2020-09 | CT#89e | CP-202077 | 0554 | | F | Correcting feature numbers | 16.6.0 | +| 2020-09 | CT#89e | CP-202052 | 0557 | 1 | A | Correction to ADC | 16.6.0 | +| 2020-09 | CT#89e | CP-202052 | 0559 | | A | Correction to ChfAddress | 16.6.0 | +| 2020-09 | CT#89e | CP-202052 | 0561 | | A | Correction to RAN-NAS Release Cause feature | 16.6.0 | +| 2020-09 | CT#89e | CP-202052 | 0563 | 1 | A | Correction for emergency sessions | 16.6.0 | +| 2020-09 | CT#89e | CP-202059 | 0565 | 1 | F | Support of 5GS and EPC interworking for non-3GPP Trusted Access | 16.6.0 | +| 2020-09 | CT#89e | CP-202048 | 0566 | | F | Multiple traffic descriptors | 16.6.0 | +| 2020-09 | CT#89e | CP-202084 | 0567 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.6.0 | +| 2020-09 | CT#89e | CP-202079 | 0542 | 1 | F | Clarification of default QoS | 17.0.0 | +| 2020-09 | CT#89e | CP-202079 | 0543 | | B | Clarification of IP index provisioning | 17.0.0 | +| 2020-09 | CT#89e | CP-202079 | 0544 | 1 | F | Clarification of usage monitoring control | 17.0.0 | +| 2020-09 | CT#89e | CP-202079 | 0545 | 1 | F | Correction to indication of UE IP address preservation | 17.0.0 | +| 2020-09 | CT#89e | CP-202079 | 0546 | 1 | F | Correction to policy control functions for TSN | 17.0.0 | +| 2020-09 | CT#89e | CP-202079 | 0547 | | F | Correction to the policy decision | 17.0.0 | +| 2020-09 | CT#89e | CP-202079 | 0548 | | F | Correction to the session-AMBR provisioning | 17.0.0 | +| 2020-09 | CT#89e | CP-202080 | 0549 | 1 | B | Traffic steering control for 5G-LAN type of services | 17.0.0 | +| 2020-09 | CT#89e | CP-202079 | 0550 | 1 | B | Update the definitions in 3.1 | 17.0.0 | +| 2020-09 | CT#89e | CP-202079 | 0564 | | F | Clarification of trace control | 17.0.0 | +| 2020-12 | CT#90e | CP-203125 | 0570 | | A | refUmN3gData yaml correction | 17.1.0 | +| 2020-12 | CT#90e | CP-203139 | 0574 | | A | TS 29.512 Essential Corrections and alignments | 17.1.0 | +| 2020-12 | CT#90e | CP-203128 | 0576 | 1 | A | Correction of the condition for the Credit Reallocation event | 17.1.0 | +| 2020-12 | CT#90e | CP-203159 | 0578 | 2 | F | Disambiguation of the reporting and handling of triggers for PCC rule bases | 17.1.0 | +| 2020-12 | CT#90e | CP-203143 | 0582 | 1 | A | Correction to PRA | 17.1.0 | +| 2020-12 | CT#90e | CP-203128 | 0584 | 3 | A | Correction to access type conditioned session AMBR | 17.1.0 | +| 2020-12 | CT#90e | CP-203128 | 0586 | 1 | A | Correction to PolicyDecisionErrorHandling feature | 17.1.0 | +| 2020-12 | CT#90e | CP-203128 | 0587 | 1 | A | Correction to SamePcf Feature | 17.1.0 | +| 2020-12 | CT#90e | CP-203114 | 0594 | | A | Correction to policy based on revalidation time | 17.1.0 | +| 2020-12 | CT#90e | CP-203114 | 0597 | 1 | A | Correction to session rule | 17.1.0 | +| 2020-12 | CT#90e | CP-203114 | 0600 | | A | Correction to usage monitoring control | 17.1.0 | +| 2020-12 | CT#90e | CP-203147 | 0602 | 1 | F | Correction to FailureCode and SessionFailureCode | 17.1.0 | +| 2020-12 | CT#90e | CP-203148 | 0603 | 1 | B | Extension of Policy Decision Failure handling | 17.1.0 | +| 2020-12 | CT#90e | CP-203147 | 0604 | 1 | F | Correction to SM Policy Association termination due to session rule error | 17.1.0 | +| 2020-12 | CT#90e | CP-203147 | 0605 | 1 | F | Correction to SessionRuleFailureCode | 17.1.0 | +| 2020-12 | CT#90e | CP-203084 | 0606 | 1 | F | Correction to usage monitoring control | 17.1.0 | +| 2020-12 | CT#90e | CP-203147 | 0607 | | F | Correction to SMF definition for LBO | 17.1.0 | +| 2020-12 | CT#90e | CP-203114 | 0610 | 1 | A | Correction to usage report during the policy association termination | 17.1.0 | +| 2020-12 | CT#90e | CP-203129 | 0612 | 1 | A | Correction to the BDT policy re-negotiation | 17.1.0 | +| 2020-12 | CT#90e | CP-203150 | 0614 | 1 | A | Remove the NW-TT port from the TSN bridge info | 17.1.0 | +| 2020-12 | CT#90e | CP-203139 | 0618 | | A | Storage of YAML files in 3GPP Forge | 17.1.0 | +| 2020-12 | CT#90e | CP-203132 | 0620 | 2 | A | Correction to Alternative QoS Parameter | 17.1.0 | +| 2020-12 | CT#90e | CP-203111 | 0626 | 1 | A | QoS monitoring report at PDU session termination | 17.1.0 | +| 2020-12 | CT#90e | CP-203111 | 0628 | 1 | A | QoS Monitoring corrections | 17.1.0 | +| 2020-12 | CT#90e | CP-203147 | 0629 | 1 | B | Updates to support User Location Change | 17.1.0 | +| 2020-12 | CT#90e | CP-203128 | 0631 | 1 | A | Location change (serving cell) for Policy Control Request Trigger | 17.1.0 | +| 2020-12 | CT#90e | CP-203153 | 0633 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.1.0 | +| 2021-03 | CT#91e | CP-210226 | 0634 | 1 | F | Miscellaneous corrections to the Npcf_SMPolicyControl_Create service operation | 17.2.0 | +| 2021-03 | CT#91e | CP-210226 | 0635 | 1 | F | Miscellaneous corrections to the Npcf_SMPolicyControl_UpdateNotify service operation | 17.2.0 | +| 2021-03 | CT#91e | CP-210222 | 0637 | 1 | A | Corrections to the procedures of policy provisioning and enforcement of authorized AMBR and default QoS | 17.2.0 | +| 2021-03 | CT#91e | CP-210226 | 0638 | 1 | F | Clarification on the applicability of some attributes and data types to UMC feature | 17.2.0 | +| 2021-03 | CT#91e | CP-210226 | 0639 | 1 | B | Addition of the PDU Session with offline charging only indication | 17.2.0 | +| 2021-03 | CT#91e | CP-210226 | 0640 | 1 | F | Reference to the wrong clause for the SMF initiated PDU session termination procedure | 17.2.0 | +| 2021-03 | CT#91e | CP-210226 | 0641 | 1 | F | Correction of a wrong reference to TS 29.514 related to AF session with required QoS procedures | 17.2.0 | +| 2021-03 | CT#91e | CP-210226 | 0642 | 1 | F | Clarification on the applicability of some data types to the SessionRuleErrorHandling feature | 17.2.0 | +| 2021-03 | CT#91e | CP-210226 | 0643 | 1 | F | Clarification on the applicability of some attributes to the 3GPP-PS-Data-Off feature | 17.2.0 | +| 2021-03 | CT#91e | CP-210226 | 0645 | 1 | F | Miscellaneous corrections to TS 29.512 | 17.2.0 | +| 2021-03 | CT#91e | CP-210205 | 0647 | 1 | A | Correction to the access network information report | 17.2.0 | +| 2021-03 | CT#91e | CP-210191 | 0651 | 2 | A | Support of stateless NFs | 17.2.0 | +| 2021-03 | CT#91e | CP-210237 | 0653 | 1 | A | Correction to the Group Id update | 17.2.0 | +| 2021-03 | CT#91e | CP-210189 | 0655 | 1 | A | PCC control for DDD status and availability after DDN failure events | 17.2.0 | +| 2021-03 | CT#91e | CP-210210 | 0657 | 3 | A | Disable UE notifications at changes related to Alternative QoS | 17.2.0 | + +| | | | | | | | | +|--|--|--|--|--|--|----------|--| +| | | | | | | Profiles | | +|--|--|--|--|--|--|----------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|--------| +| 2021-03 | CT#91e | CP-210228 | 0660 | | F | User Location Change PCRT not supported in wireline access | 17.2.0 | +| 2021-03 | CT#91e | CP-210202 | 0662 | 1 | A | Correction to supported Policy Control Request triggers in wireline access | 17.2.0 | +| 2021-03 | CT#91e | CP-210192 | 0664 | 3 | A | Redundant User Plane Paths | 17.2.0 | +| 2021-03 | CT#91e | CP-210204 | 0666 | | A | Correction to repPolicyCtrlReqTrigger attribute | 17.2.0 | +| 2021-03 | CT#91e | CP-210205 | 0668 | 1 | A | Correction to multiple access type conditioned session rules | 17.2.0 | +| 2021-03 | CT#91e | CP-210205 | 0670 | | A | Correction to QOS_DEC_ERR and CH_DEC_ERR | 17.2.0 | +| 2021-03 | CT#91e | CP-210226 | 0671 | 1 | F | Correction to Monitoring key definition | 17.2.0 | +| 2021-03 | CT#91e | CP-210204 | 0673 | 3 | A | Correction to access type conditioned session rule | 17.2.0 | +| 2021-03 | CT#91e | CP-210191 | 0675 | 2 | A | Correction to "resourceUri" attribute description | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0676 | | F | Correction on UE initiated PDU session modification | 17.2.0 | +| 2021-03 | CT#91e | CP-210237 | 0678 | 1 | A | Correction to TSN scenarios. | 17.2.0 | +| 2021-03 | CT#91e | CP-210218 | 0679 | | F | Update of "description" field for map data types | 17.2.0 | +| 2021-03 | CT#91e | CP-210218 | 0680 | | F | OpenAPI reference | 17.2.0 | +| 2021-03 | CT#91e | CP-210237 | 0686 | 2 | A | Correction to traffic correlation indication | 17.2.0 | +| 2021-03 | CT#91e | CP-210221 | 0691 | 1 | F | Adding some missing description fields to data type definitions in OpenAPI specification files | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0692 | 1 | F | Additional corrections to the Npcf_SMPolicyControl_Create service operation | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0693 | 1 | F | Miscellaneous corrections to the Npcf_SMPolicyControl_Delete service operation | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0694 | 1 | F | Miscellaneous corrections to the Provisioning and Enforcement of Policy Decisions clause | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0695 | 1 | F | Miscellaneous corrections to the data types defined in the Npcf_SMPolicyControl API | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0696 | | F | Corrections of a reference to an non-existent subclause | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0697 | 1 | F | Corrections to the P-CSCF restoration indication mechanism | 17.2.0 | +| 2021-03 | CT#91e | CP-210225 | 0698 | 1 | F | Reference to the wrong attribute name for the QoS Monitoring Decision | 17.2.0 | +| 2021-03 | CT#91e | CP-210195 | 0701 | | A | Correction of a reference to the wrong attribute name for the reported presence reporting area information | 17.2.0 | +| 2021-03 | CT#91e | CP-210204 | 0706 | | A | Correction of the SteerModeValue attribute name in the Npcf_SMPolicyControl specific Data Types table | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0707 | | F | Corrections to the applicability column of the SmPolicyDeleteData data type | 17.2.0 | +| 2021-03 | CT#91e | CP-210195 | 0710 | 1 | A | Correction to authDefQos attribute | 17.2.0 | +| 2021-03 | CT#91e | CP-210195 | 0716 | 1 | A | Correction to the GBR type of default QoS flow | 17.2.0 | +| 2021-03 | CT#91e | CP-210217 | 0722 | | A | The apiSpecificResourceUriPart component | 17.2.0 | +| 2021-03 | CT#91e | CP-210221 | 0723 | 1 | F | NF service consumer terminology | 17.2.0 | +| 2021-03 | CT#91e | CP-210220 | 0724 | | B | Optional header clarification | 17.2.0 | +| 2021-03 | CT#91e | CP-210195 | 0727 | 1 | A | Corrections to RuleOperation | 17.2.0 | +| 2021-03 | CT#91e | CP-210195 | 0730 | 1 | A | repPolicyCtrlReqTriggers attribute correction | 17.2.0 | +| 2021-03 | CT#91e | CP-210195 | 0733 | | A | Correction to session rule | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0734 | 1 | F | deactivationTime for time conditioned session rule | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0735 | 1 | F | Remove exUsagePccRuleIds from PCC rule definition | 17.2.0 | +| 2021-03 | CT#91e | CP-210222 | 0738 | | A | packFiltInfo attribute correction | 17.2.0 | +| 2021-03 | CT#91e | CP-210195 | 0741 | 2 | A | Correction to PCF behavior when removing PCC/Session rules | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0742 | 1 | F | Correction on UE initiated PDU session modification | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0743 | 1 | F | Correction to conditioned rules | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0744 | 1 | F | Correction to Usage Monitoring | 17.2.0 | +| 2021-03 | CT#91e | CP-210227 | 0745 | 1 | F | Clarification about handling of valid unreferred policy decisions | 17.2.0 | +| 2021-03 | CT#91e | CP-210240 | 0748 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.2.0 | +| 2021-06 | CT#92e | CP-211283 | 0681 | 2 | B | Satellite backhaul change policy control request trigger | 17.3.0 | +| 2021-06 | CT#92e | CP-211226 | 0749 | 2 | B | 29.512 PCC support for MPS for DTS | 17.3.0 | +| 2021-06 | CT#92e | CP-211242 | 0751 | 1 | F | Correction to Charging Information | 17.3.0 | +| 2021-06 | CT#92e | CP-211257 | 0752 | 2 | B | Application Detection triggering for dynamic AM policy changes | 17.3.0 | +| 2021-06 | CT#92e | CP-211237 | 0755 | 2 | A | Correct the error code MISS_FLOW_INFO | 17.3.0 | +| 2021-06 | CT#92e | CP-211198 | 0757 | 2 | A | Correction to PCC control for DDD status and availability after DDN failure events | 17.3.0 | +| 2021-06 | CT#92e | CP-211245 | 0759 | 1 | F | Correction to access network info report | 17.3.0 | +| 2021-06 | CT#92e | CP-211273 | 0760 | 3 | B | Support Time Sensing Communication other than TSN | 17.3.0 | +| 2021-06 | CT#92e | CP-211272 | 0761 | 2 | B | Support survival time | 17.3.0 | +| 2021-06 | CT#92e | CP-211218 | 0763 | 3 | B | Add user plane latency requirement in PCC rule | 17.3.0 | +| 2021-06 | CT#92e | CP-211211 | 0764 | | F | Correction to policy control request trigger | 17.3.0 | +| 2021-06 | CT#92e | CP-211246 | 0765 | 1 | F | Correction to usage monitoring for Non-3GPP | 17.3.0 | +| 2021-06 | CT#92e | CP-211211 | 0766 | 1 | F | Clarification of PCF Requested Usage Report | 17.3.0 | +| 2021-06 | CT#92e | CP-211211 | 0767 | 1 | F | Correct the disabling usage monitoring | 17.3.0 | +| 2021-06 | CT#92e | CP-211243 | 0768 | 1 | F | Correct the Redundant PDU Session indication | 17.3.0 | +| 2021-06 | CT#92e | CP-211211 | 0769 | 1 | F | Correct the offline charging only | 17.3.0 | +| 2021-06 | CT#92e | CP-211237 | 0771 | 1 | A | Correction to QoS control in the VPLMN | 17.3.0 | +| 2021-06 | CT#92e | CP-211270 | 0772 | 4 | B | Support of event trigger for GERAN and UTRAN access over N7 interface | 17.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------|--------| +| 2021-06 | CT#92e | CP-211217 | 0774 | 1 | F | Additional corrections to the PDU Session with offline charging only indication | 17.3.0 | +| 2021-06 | CT#92e | CP-211234 | 0775 | | F | Additional missing description fields in OpenAPI specification files | 17.3.0 | +| 2021-06 | CT#92e | CP-211277 | 0776 | 1 | B | Support of Threshold Condition | 17.3.0 | +| 2021-06 | CT#92e | CP-211277 | 0777 | 1 | B | Support of Steering Mode Indicator | 17.3.0 | +| 2021-06 | CT#92e | CP-211256 | 0778 | 2 | F | Correction of tsnPortManContNwts attribute | 17.3.0 | +| 2021-06 | CT#92e | CP-211215 | 0780 | 1 | A | Correction on wrong referenced attributes | 17.3.0 | +| 2021-06 | CT#92e | CP-211276 | 0782 | 1 | B | Support of Network Exposure to EAS via Local NEF | 17.3.0 | +| 2021-06 | CT#92e | CP-211217 | 0783 | 1 | B | Handling of requests which collide with an existing SM Policy Association for interworking scenario | 17.3.0 | +| 2021-06 | CT#92e | CP-211217 | 0785 | 1 | B | Handling of requests which have timed out at the originating entity for interworking scenario | 17.3.0 | +| 2021-06 | CT#92e | CP-211200 | 0786 | 1 | A | Redirect Responses | 17.3.0 | +| 2021-06 | CT#92e | CP-211250 | 0790 | 2 | F | Correction to Same PCF requests to BSF | 17.3.0 | +| 2021-06 | CT#92e | CP-211274 | 0791 | 1 | B | Support of TSCAI time domain | 17.3.0 | +| 2021-06 | CT#92e | CP-211211 | 0792 | 2 | F | Failure handling for traffic steering | 17.3.0 | +| 2021-06 | CT#92e | CP-211204 | 0795 | 1 | A | Wrong referenced SmPolicyDecision data type | 17.3.0 | +| 2021-06 | CT#92e | CP-211265 | 0797 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.3.0 | +| 2021-06 | CT#92e | CP-211211 | 0798 | | F | Updating the UDR upon usage report receipt | 17.3.0 | +| 2021-09 | CT#93e | CP-212212 | 0799 | 1 | B | 29.512 MPS for DTS QoS update failure | 17.4.0 | +| 2021-09 | CT#93e | CP-212224 | 0802 | 1 | F | Correction to PRA information update | 17.4.0 | +| 2021-09 | CT#93e | CP-212198 | 0806 | 2 | B | Duplicated notification | 17.4.0 | +| 2021-09 | CT#93e | CP-212193 | 0807 | 1 | B | Clarification on satellite backhaul | 17.4.0 | +| 2021-09 | CT#93e | CP-212201 | 0808 | 1 | B | Authorization of UE initiates a resource modification | 17.4.0 | +| 2021-09 | CT#93e | CP-212201 | 0809 | 1 | B | PCC rules authorization with preliminary service information | 17.4.0 | +| 2021-09 | CT#93e | CP-212224 | 0810 | | B | Clarification of the charging correlation id | 17.4.0 | +| 2021-09 | CT#93e | CP-212224 | 0811 | | B | Removal of traffic routing information | 17.4.0 | +| 2021-09 | CT#93e | CP-212205 | 0812 | 1 | B | Support of IMS emergency service for SNPN | 17.4.0 | +| 2021-09 | CT#93e | CP-212190 | 0815 | 1 | A | Correction of report of User Location Info Time | 17.4.0 | +| 2021-09 | CT#93e | CP-212220 | 0817 | 1 | A | Support of TCP and UDP ports in non-3GPP UE location | 17.4.0 | +| 2021-09 | CT#93e | CP-212196 | 0818 | 1 | F | Align description with data type for rttThres | 17.4.0 | +| 2021-09 | CT#93e | CP-212196 | 0819 | | B | Congestion handling for priority-based steering mode | 17.4.0 | +| 2021-09 | CT#93e | CP-212196 | 0820 | | B | remove EN related to UE-assistance indicator | 17.4.0 | +| 2021-09 | CT#93e | CP-212211 | 0821 | 1 | F | handling of SMF for TSCAI Survival Time | 17.4.0 | +| 2021-09 | CT#93e | CP-212211 | 0822 | 1 | F | Replacement of TSN Terminology in 29.512 | 17.4.0 | +| 2021-09 | CT#93e | CP-212189 | 0824 | 1 | A | Align description with data type for thresholds in QosMonitoringData | 17.4.0 | +| 2021-09 | CT#93e | CP-212167 | 0826 | 1 | A | correction of description of dsttResidTime | 17.4.0 | +| 2021-09 | CT#93e | CP-212224 | 0827 | 1 | F | Corrections on the sender of the HTTP error response in the update procedure | 17.4.0 | +| 2021-09 | CT#93e | CP-212220 | 0828 | 1 | F | Correction to the declaration of authorization credentials | 17.4.0 | +| 2021-09 | CT#93e | CP-212224 | 0829 | | B | Correction to the report of Netloc access information | 17.4.0 | +| 2021-09 | CT#93e | CP-212224 | 0830 | | B | Removal of network slice instance from service procedures | 17.4.0 | +| 2021-09 | CT#93e | CP-212211 | 0831 | 1 | B | Introduction of TSCTSF | 17.4.0 | +| 2021-09 | CT#93e | CP-212220 | 0832 | 1 | F | Adding a missing description field to the OpenAPI specification file of the Npcf_SMPolicyControl API | 17.4.0 | +| 2021-09 | CT#93e | CP-212223 | 0833 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.4.0 | +| 2021-09 | CT#93e | CP-212224 | 0834 | 1 | F | Report of 3GPP and non-3GPP User Location | 17.4.0 | +| 2021-12 | CT#94e | CP-213216 | 0836 | | F | Correction to the notification of satellite backhaul changes | 17.5.0 | +| 2021-12 | CT#94e | CP-213229 | 0838 | 1 | B | PCC Support of restricted PDU Session for remote provisioning of UE using User Plane | 17.5.0 | +| 2021-12 | CT#94e | CP-213230 | 0839 | 2 | B | Monitoring the data rate per Network Slice | 17.5.0 | +| 2021-12 | CT#94e | CP-213225 | 0840 | 1 | B | Handling of Session Management Policy Data per PLMN | 17.5.0 | +| 2021-12 | CT#94e | CP-213229 | 0841 | | B | SNPN support for IMS Emergency services | 17.5.0 | +| 2021-12 | CT#94e | CP-213229 | 0842 | | B | Direct access to SNPN | 17.5.0 | +| 2021-12 | CT#94e | CP-213234 | 0843 | 1 | B | Clarify the scenario where the TSC and time synchronization are not supported | 17.5.0 | +| 2021-12 | CT#94e | CP-213234 | 0844 | 1 | B | Resolve the editor's note for bridge Id | 17.5.0 | +| 2021-12 | CT#94e | CP-213223 | 0845 | 2 | B | Remove the editor's note for AF preference for the user plane latency | 17.5.0 | +| 2021-12 | CT#94e | CP-213222 | 0846 | | B | Remove the editor's note for UPF service | 17.5.0 | +| 2021-12 | CT#94e | CP-213227 | 0849 | 1 | B | NWDAF instance provisioning to the PCF | 17.5.0 | +| 2021-12 | CT#94e | CP-213230 | 0850 | 1 | B | Support of UE-Slice-MBR | 17.5.0 | +| 2021-12 | CT#94e | CP-213219 | 0852 | 1 | F | Mutual exclusion between thresValue and steerModelInd | 17.5.0 | +| 2021-12 | CT#94e | CP-213219 | 0853 | 1 | F | MA PDU sessions with connectivity over EPC and 5GC | 17.5.0 | +| 2021-12 | CT#94e | CP-213243 | 0854 | 1 | F | Replacing PDU session in Annex B with PDN connection | 17.5.0 | +| 2021-12 | CT#94e | CP-213239 | 0855 | | F | API URI of the Npcf_SMPolicyControl API | 17.5.0 | +| 2021-12 | CT#94e | CP-213194 | 0856 | 1 | B | Indication of request of notification PDU session established/terminated events | 17.5.0 | +| 2021-12 | CT#94e | CP-213234 | 0857 | 1 | B | Handling alternative QoS related parameters received from the AF | 17.5.0 | +| 2021-12 | CT#94e | CP-213234 | 0858 | 1 | F | Correction to TSC QoS information | 17.5.0 | +| 2021-12 | CT#94e | CP-213234 | 0859 | 1 | F | Support of Ethernet PDU sessions and IP PDU sessions for TSC | 17.5.0 | +| 2021-12 | CT#94e | CP-213234 | 0860 | | F | TSCTSF as PCF consumer for TSC | 17.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------|--------| +| 2021-12 | CT#94e | CP-213234 | 0861 | 1 | F | Change the Network to TSN translator (TT) protocol aspects TS referencing | 17.5.0 | +| 2021-12 | CT#94e | CP-213223 | 0862 | 1 | B | Adding EAS IP replacement information in PCC rules | 17.5.0 | +| 2021-12 | CT#94e | CP-213241 | 0864 | 1 | A | PCF authorization for QoS control in the VPLMN | 17.5.0 | +| 2021-12 | CT#94e | CP-213219 | 0865 | 1 | B | Extension of PCC rule definition for ATSSS | 17.5.0 | +| 2021-12 | CT#94e | CP-213244 | 0868 | | F | Correction on reused data type Uinteger | 17.5.0 | +| 2021-12 | CT#94e | CP-213244 | 0869 | 1 | B | Error handling when no SM Policy Association exists | 17.5.0 | +| 2021-12 | CT#94e | CP-213244 | 0870 | | F | Correction to session rule | 17.5.0 | +| 2021-12 | CT#94e | CP-213225 | 0871 | 1 | F | Resolving the PDU Session with offline charging only indication related Ens | 17.5.0 | +| 2021-12 | CT#94e | CP-213223 | 0872 | 1 | B | AF Request for Simultaneous Connectivity over Source and Target PSA at Edge Relocation | 17.5.0 | +| 2021-12 | CT#94e | CP-213246 | 0873 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.5.0 | +| 2022-03 | CT#95e | CP-220178 | 0875 | 1 | F | 29.512 MPS for DTS Notes Correction | 17.6.0 | +| 2022-03 | CT#95e | CP-220178 | 0876 | 1 | F | 29.512 MPS exemption from time conditioning | 17.6.0 | +| 2022-03 | CT#95e | CP-220188 | 0878 | | F | Clarification on threshold values | 17.6.0 | +| 2022-03 | CT#95e | CP-220183 | 0879 | 1 | B | Cleanup of time sensitive communication | 17.6.0 | +| 2022-03 | CT#95e | CP-220183 | 0881 | 1 | B | QoS determination for TSC | 17.6.0 | +| 2022-03 | CT#95e | CP-220182 | 0882 | 1 | F | Onboarding indication | 17.6.0 | +| 2022-03 | CT#95e | CP-220185 | 0883 | 1 | B | Support of AF triggered EAS rediscovery | 17.6.0 | +| 2022-03 | CT#95e | CP-220195 | 0884 | 1 | F | Clarification of the packet filter identifier | 17.6.0 | +| 2022-03 | CT#95e | CP-220195 | 0886 | | F | Correction on UE Location related information in the interworking cases | 17.6.0 | +| 2022-03 | CT#95e | CP-220196 | 0887 | 1 | F | Handling of number of packets in 5G | 17.6.0 | +| 2022-03 | CT#95e | CP-220179 | 0888 | 1 | F | reusing common data type SatelliteBackhaulCategory | 17.6.0 | +| 2022-03 | CT#95e | CP-220195 | 0889 | 1 | F | Alignment of term Session-AMBR | 17.6.0 | +| 2022-03 | CT#95e | CP-220195 | 0890 | | F | Update of service operation general descriptions | 17.6.0 | +| 2022-03 | CT#95e | CP-220187 | 0891 | 1 | F | Update of service operation general descriptions for eNS | 17.6.0 | +| 2022-03 | CT#95e | CP-220182 | 0892 | 1 | F | Update of 4.2.2.1 | 17.6.0 | +| 2022-03 | CT#95e | CP-220190 | 0893 | 1 | F | complete the definition of NWDAF_DATA_CHG trigger | 17.6.0 | +| 2022-03 | CT#95e | CP-220176 | 0894 | 2 | A | Alignment of "Application Errors" clause with SBI TS template | 17.6.0 | +| 2022-03 | CT#95e | CP-220188 | 0895 | 1 | F | Clarification to MA PDU sessions | 17.6.0 | +| 2022-03 | CT#95e | CP-220182 | 0896 | 1 | B | Completion of the Support of restricted PDU Session for remote provisioning of UE using User Plane | 17.6.0 | +| 2022-03 | CT#95e | CP-220195 | 0898 | 2 | B | Enhance SmPolicyAssociationReleaseCause for trigger PDU session reactivation procedure | 17.6.0 | +| 2022-03 | CT#95e | CP-220185 | 0899 | 1 | F | Handling of supported features for Edge Computing | 17.6.0 | +| 2022-03 | CT#95e | CP-220191 | 0900 | | F | Corrections in attribute name and data type description related to NWDAF data. | 17.6.0 | +| 2022-03 | CT#95e | CP-220195 | 0901 | 1 | F | Collision in SMF during UpdateNotify procedure | 17.6.0 | +| 2022-03 | CT#95e | CP-220195 | 0903 | 1 | F | Handling of packet filters when the allowed number is exceeded | 17.6.0 | +| 2022-03 | CT#95e | CP-220187 | 0904 | 1 | F | remove EN related to Dispersion Analytics | 17.6.0 | +| 2022-03 | CT#95e | CP-220201 | 0906 | 1 | F | Formatting of Description Fields | 17.6.0 | +| 2022-03 | CT#95e | CP-220202 | 0907 | 1 | B | Support of AN-GW restoration | 17.6.0 | +| 2022-03 | CT#95e | CP-220202 | 0908 | 1 | B | UE-initiated resource modification support for interworking scenario | 17.6.0 | +| 2022-03 | CT#95e | CP-220167 | 0911 | 1 | A | Corrections to Application Detection and Control | 17.6.0 | +| 2022-03 | CT#95e | CP-220201 | 0912 | | B | Updating Binding Indication for multiple resource contexts feature | 17.6.0 | +| 2022-03 | CT#95e | CP-220197 | 0913 | 1 | F | Correction to the indication of notification to the PCF for the UE about PDU session establishment/termination events | 17.6.0 | +| 2022-03 | CT#95e | CP-220195 | 0915 | 1 | F | Correction to enable retrieval of Network Provided Location information in a MESSAGE request | 17.6.0 | +| 2022-03 | CT#95e | CP-220183 | 0916 | | B | Correction to TSCAI derivation | 17.6.0 | +| 2022-03 | CT#95e | CP-220194 | 0917 | | F | Update of info and externalDocs fields | 17.6.0 | +| 2022-03 | CT#95e | CP-220335 | 0920 | | F | Correction to pvsInfo attribute | 17.6.0 | +| 2022-06 | CT#96 | CP-221154 | 0922 | | F | Correcting the definition of the 404 status code in the OpenAPI description | 17.7.0 | +| 2022-06 | CT#96 | CP-221145 | 0923 | 3 | F | Handling of time domain | 17.7.0 | +| 2022-06 | CT#96 | CP-221144 | 0924 | 2 | F | Resolve the issue of individual QoS parameters | 17.7.0 | +| 2022-06 | CT#96 | CP-221123 | 0926 | 1 | F | MA PDU Session in EPC/E-UTRAN to 5GS handover | 17.7.0 | +| 2022-06 | CT#96 | CP-221126 | 0927 | | F | Correction of supported features for Edge Computing functionality | 17.7.0 | +| 2022-06 | CT#96 | CP-221130 | 0929 | 1 | F | Completion of handling of NWDAF_DATA_CH trigger | 17.7.0 | +| 2022-06 | CT#96 | CP-221138 | 0930 | 1 | F | Completion of User Plane Remote Provisioning | 17.7.0 | +| 2022-06 | CT#96 | CP-221157 | 0931 | 3 | F | Correction to the charging identifier to enable uniqueness in roaming scenarios | 17.7.0 | +| 2022-06 | CT#96 | CP-221157 | 0933 | 1 | F | Correction to the PDU Session ID determination in EPC interworking scenarios | 17.7.0 | +| 2022-06 | CT#96 | CP-221157 | 0935 | 1 | F | Correction to the QoS constraints support | 17.7.0 | +| 2022-06 | CT#96 | CP-221159 | 0936 | 1 | F | Correction to the notification of PCF for a PDU session | 17.7.0 | +| 2022-06 | CT#96 | CP-221145 | 0937 | 1 | B | Burst Arrival Time adjustment | 17.7.0 | +| 2022-06 | CT#96 | CP-221157 | 0939 | 1 | F | Correction to the TrafficData and ConditionData | 17.7.0 | +| 2022-06 | CT#96 | CP-221126 | 0940 | 2 | F | Correction to QoS monitoring report | 17.7.0 | +| 2022-06 | CT#96 | CP-221117 | 0941 | 1 | A | Correction for the handling of QoS monitoring data | 17.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------|--------| +| 2022-06 | CT#96 | CP-221157 | 0942 | | F | Handling of multiple IPv6 prefixes | 17.7.0 | +| 2022-06 | CT#96 | CP-221158 | 0945 | 1 | F | Correction to traffic routing requirements | 17.7.0 | +| 2022-06 | CT#96 | CP-221151 | 0947 | | F | Update of info and externalDocs fields | 17.7.0 | +| 2022-06 | CT#96 | CP-221127 | 0949 | | F | The behaviour of SMF for I-SMF insertion and removal | 17.7.0 | +| 2022-09 | CT#97e | CP-222125 | 0950 | | F | Untrusted WLAN location information | 17.8.0 | +| 2022-09 | CT#97e | CP-222125 | 0951 | 2 | F | Exceeding number of packet filters when interworking with EPS | 17.8.0 | +| 2022-09 | CT#97e | CP-222093 | 0955 | 1 | A | Correction to policyCtrlReqTriggers attribute name | 17.8.0 | +| 2022-09 | CT#97e | CP-222125 | 0957 | 1 | F | Correction to the QoS Monitoring | 17.8.0 | +| 2022-09 | CT#97e | CP-222113 | 0958 | 1 | F | Correction to the references | 17.8.0 | +| 2022-09 | CT#97e | CP-222093 | 0962 | | A | Correction to UP Path change subscription | 17.8.0 | +| 2022-09 | CT#97e | CP-222099 | 0963 | 1 | F | ExposureToEAS feature name correction | 17.8.0 | +| 2022-09 | CT#97e | CP-222125 | 0966 | 1 | F | Rejection of the update of mute indication for ADC | 17.8.0 | +| 2022-09 | CT#97e | CP-222121 | 0968 | | F | Update of info and externalDocs fields | 17.8.0 | +| 2022-12 | CT#98e | CP-223181 | 0970 | 1 | F | Survival time applicability | 17.9.0 | +| 2022-12 | CT#98e | CP-223172 | 0972 | | F | Correction on NWDAF_DATA_CHG handling | 17.9.0 | +| 2022-12 | CT#98e | CP-223196 | 0976 | 1 | F | Correction related to applicability of traffic correlation indicator | 17.9.0 | +| 2022-12 | CT#98e | CP-223163 | 0976 | | A | Correction to the attribute name of policy control request trigger | 17.9.0 | +| 2022-12 | CT#98e | CP-223183 | 0979 | 1 | F | Correction to the attribute name of policy control request trigger | 17.9.0 | +| 2022-12 | CT#98e | CP-223165 | 0984 | | F | Correction to Satellite backhaul change report | 17.9.0 | +| 2022-12 | CT#98e | CP-223197 | 0987 | | F | Correction to the PCF for the UE indication of notification of PDU session events | 17.9.0 | +| 2022-12 | CT#98e | CP-223188 | 0993 | | F | Update of info and externalDocs fields | 17.9.0 | +| 2022-12 | CT#98e | CP-223191 | 0969 | | F | Adding the mandatory error code 502 Bad Gateway | 18.0.0 | +| 2022-12 | CT#98e | CP-223192 | 0971 | | F | Enumeration definitions in the OpenAPI file and name of ServingNfIdentity data type | 18.0.0 | +| 2022-12 | CT#98e | CP-223199 | 0973 | 2 | F | Default QoS and Session AMBR handling in emergency cases | 18.0.0 | +| 2022-12 | CT#98e | CP-223199 | 0974 | 1 | F | Correction on policy decision and condition data error handling | 18.0.0 | +| 2022-12 | CT#98e | CP-223199 | 0975 | 1 | B | Error handling when UE is temporarily unavailable | 18.0.0 | +| 2022-12 | CT#98e | CP-223199 | 0980 | 1 | B | PCC decision based on the input of TSCTSF | 18.0.0 | +| 2022-12 | CT#98e | CP-223198 | 0981 | | F | Correction to the terminology of UMIC | 18.0.0 | +| 2022-12 | CT#98e | CP-223199 | 0982 | 1 | F | Clarification of application detection information report | 18.0.0 | +| 2022-12 | CT#98e | CP-223200 | 0985 | 1 | B | Indication of Alternative QoS not supported by NG-RAN | 18.0.0 | +| 2022-12 | CT#98e | CP-223199 | 0986 | 1 | F | Correction to DNN encoding | 18.0.0 | +| 2022-12 | CT#98e | CP-223198 | 0988 | 1 | F | Clarification to the report of access network charging information | 18.0.0 | +| 2022-12 | CT#98e | CP-223198 | 0989 | 1 | F | Correction to policy update procedures | 18.0.0 | +| 2022-12 | CT#98e | CP-223200 | 0990 | 1 | F | Correction to charging data | 18.0.0 | +| 2022-12 | CT#98e | CP-223200 | 0991 | 1 | F | QoS monitoring support report | 18.0.0 | +| 2022-12 | CT#98e | CP-223178 | 0992 | | B | SNPN mobility | 18.0.0 | +| 2022-12 | CT#98e | CP-223189 | 0994 | | F | Update of info and externalDocs fields | 18.0.0 | +| 2023-03 | CT#99 | CP-230142 | 0997 | 1 | A | Correcting the support of multiple IPv6 prefixes | 18.1.0 | +| 2023-03 | CT#99 | CP-230176 | 0999 | 1 | B | Adding the ability to model multiple IPv6 prefixes | 18.1.0 | +| 2023-03 | CT#99 | CP-230174 | 1000 | | F | Correcting the description of the termination action upon out of credit event | 18.1.0 | +| 2023-03 | CT#99 | CP-230166 | 1002 | | F | Correction of the description fields in enumerations | 18.1.0 | +| 2023-03 | CT#99 | CP-230175 | 1004 | 1 | F | Alignment of packet delay report | 18.1.0 | +| 2023-03 | CT#99 | CP-230170 | 1008 | 1 | B | Support for AF influence on Service Function Chaining | 18.1.0 | +| 2023-03 | CT#99 | CP-230171 | 1009 | | B | Clarification of the usage monitoring with monitoring time and one instance of the thresholds provided | 18.1.0 | +| 2023-03 | CT#99 | CP-230171 | 1010 | 1 | B | Handling of packet filters provided to the UE by SMF | 18.1.0 | +| 2023-03 | CT#99 | CP-230171 | 1011 | 1 | B | Mapping of QoS parameters between Rel-99 QoS parameters and 5G QoS parameters when N7 interface | 18.1.0 | +| 2023-03 | CT#99 | CP-230137 | 1012 | 1 | B | Support for AF traffic influence for common EAS, DNAI selection | 18.1.0 | +| 2023-03 | CT#99 | CP-230140 | 1014 | | A | Correction in QoS monitoring handling | 18.1.0 | +| 2023-03 | CT#99 | CP-230174 | 1016 | | F | Support of indirect feature negotiation | 18.1.0 | +| 2023-03 | CT#99 | CP-230174 | 1017 | | F | Generalization of QoS monitoring control description | 18.1.0 | +| 2023-03 | CT#99 | CP-230173 | 1019 | 1 | A | Correction on setting Packet Delay Failure report Threshold | 18.1.0 | +| 2023-03 | CT#99 | CP-230137 | 1020 | 1 | B | Introducing selection of more granular set of UEs | 18.1.0 | +| 2023-03 | CT#99 | CP-230136 | 1021 | 1 | B | Support of integration with IETF Deterministic Networking | 18.1.0 | +| 2023-03 | CT#99 | CP-230141 | 1024 | | A | Correction to incorrect attribute name capitalization | 18.1.0 | +| 2023-03 | CT#99 | CP-230175 | 1025 | | F | User Plane Remote Provisioning clarifications | 18.1.0 | +| 2023-03 | CT#99 | CP-230150 | 1026 | | B | Onboarding in SNPN supporting localized services | 18.1.0 | +| 2023-03 | CT#99 | CP-230176 | 1027 | 1 | F | Correction to Alternative QoS support | 18.1.0 | +| 2023-03 | CT#99 | CP-230129 | 1031 | 1 | A | Correction of enumerations values | 18.1.0 | +| 2023-03 | CT#99 | CP-230166 | 1032 | | F | Corrections to enumeration values not respecting the naming convention | 18.1.0 | +| 2023-03 | CT#99 | CP-230143 | 1034 | | A | Correction to wrong attribute name | 18.1.0 | +| 2023-03 | CT#99 | CP-230177 | 1038 | 1 | B | Support of IPv6 prefix delegation | 18.1.0 | +| 2023-03 | CT#99 | CP-230179 | 1039 | 1 | B | Support of BAT window and capability for BAT adaptation | 18.1.0 | +| 2023-03 | CT#99 | CP-230179 | 1040 | 1 | B | Support of periodicity range | 18.1.0 | +| 2023-03 | CT#99 | CP-230130 | 1041 | 1 | B | Support of Dynamic Satellite Backhaul | 18.1.0 | +| 2023-03 | CT#99 | CP-230137 | 1043 | 1 | B | Support of common DNAI selection by AF | 18.1.0 | +| 2023-03 | CT#99 | CP-230318 | 1045 | 3 | B | URSP provisioning in EPS | 18.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|--------| +| 2023-03 | CT#99 | CP-230161 | 1047 | | F | Update of info and externalDocs fields | 18.1.0 | +| 2023-06 | CT#100 | CP-231174 | 1048 | 1 | B | Support of Non-3GPP access for SNPN scenarios | 18.2.0 | +| 2023-06 | CT#100 | CP-231163 | 1049 | 1 | B | MA PDU session interworking enhancements | 18.2.0 | +| 2023-06 | CT#100 | CP-231163 | 1050 | 1 | B | MP-QUIC support for traffic steering | 18.2.0 | +| 2023-06 | CT#100 | CP-231163 | 1051 | | B | Redundant traffic steering | 18.2.0 | +| 2023-06 | CT#100 | CP-231143 | 1052 | 1 | B | Network determined BAT offset and periodicity adaption | 18.2.0 | +| 2023-06 | CT#100 | CP-231143 | 1053 | 3 | B | The correction on BAT window and BAT adaptation capability and the support of provisioning Periodicity Set | 18.2.0 | +| 2023-06 | CT#100 | CP-231149 | 1056 | 3 | B | Group related data rate policy control | 18.2.0 | +| 2023-06 | CT#100 | CP-231152 | 1057 | 1 | B | Updates to support the provisioning of the PDU Session inactivity timer value | 18.2.0 | +| 2023-06 | CT#100 | CP-231158 | 1058 | 1 | B | Correction to AF influence on Service Function Chaining | 18.2.0 | +| 2023-06 | CT#100 | CP-231342 | 1059 | 6 | B | Support for URSP awareness | 18.2.0 | +| 2023-06 | CT#100 | CP-231160 | 1060 | 1 | B | Applicability of the policy control request trigger for convergence scenario | 18.2.0 | +| 2023-06 | CT#100 | CP-231160 | 1061 | 1 | B | Clarification of policy control request trigger | 18.2.0 | +| 2023-06 | CT#100 | CP-231160 | 1063 | 1 | B | IPTV service authorization | 18.2.0 | +| 2023-06 | CT#100 | CP-231160 | 1064 | 1 | B | PCF Function Clarification | 18.2.0 | +| 2023-06 | CT#100 | CP-231135 | 1065 | 1 | B | Complete common DNAI and EAS selection | 18.2.0 | +| 2023-06 | CT#100 | CP-231133 | 1067 | | B | New PCC rule parameter for indirect feature negotiation | 18.2.0 | +| 2023-06 | CT#100 | CP-231135 | 1068 | 1 | B | Support of VPLMN Specific Offloading Policy for HR-SBO | 18.2.0 | +| 2023-06 | CT#100 | CP-231157 | 1071 | 3 | B | Support of the direct event notification of TSC management information | 18.2.0 | +| 2023-06 | CT#100 | CP-231129 | 1072 | 1 | B | Support of PDU Set QoS Parameters | 18.2.0 | +| 2023-06 | CT#100 | CP-231129 | 1073 | 1 | B | Support of Uplink Downlink transmission coordination to meet RT latency requirement | 18.2.0 | +| 2023-06 | CT#100 | CP-231129 | 1074 | 1 | B | Npcf_SMPolicyControl Service update for support of multi-modal services | 18.2.0 | +| 2023-06 | CT#100 | CP-231129 | 1075 | 1 | B | Update Npcf_SMPolicyControl Service for support of new QoS monitoring parameters | 18.2.0 | +| 2023-06 | CT#100 | CP-231163 | 1077 | 1 | B | Support of Transport Mode of MPQUIC Steering Functionality | 18.2.0 | +| 2023-06 | CT#100 | CP-231135 | 1081 | 1 | F | Candidate DNAI information in wrong data type | 18.2.0 | +| 2023-06 | CT#100 | CP-231162 | 1082 | 1 | B | Support of application detection event exposure | 18.2.0 | +| 2023-06 | CT#100 | CP-231183 | 1084 | 1 | B | Adapt QoS Monitoring description | 18.2.0 | +| 2023-06 | CT#100 | CP-231130 | 1086 | 1 | B | Protocol description support in Npcf_SMPolicyControl API | 18.2.0 | +| 2023-06 | CT#100 | CP-231136 | 1087 | 1 | B | Support of change of HR-SBO support indication | 18.2.0 | +| 2023-06 | CT#100 | CP-231158 | 1088 | 1 | F | Renaming AF influenced Traffic Steering | 18.2.0 | +| 2023-06 | CT#100 | CP-231147 | 1091 | | A | Removal of unspecified QoS monitoring control options | 18.2.0 | +| 2023-06 | CT#100 | CP-231299 | 1092 | 2 | B | Support of periodicity measurement and reporting for power saving | 18.2.0 | +| 2023-06 | CT#100 | CP-231131 | 1093 | | F | Corrections to the redirection mechanism description | 18.2.0 | +| 2023-06 | CT#100 | CP-231152 | 1094 | 1 | B | updating the S-NSSAI of the PDU Session | 18.2.0 | +| 2023-06 | CT#100 | CP-231145 | 1096 | 1 | B | Completion of URSP provisioning in EPS | 18.2.0 | +| 2023-06 | CT#100 | CP-231134 | 1097 | 1 | B | Session Failure report | 18.2.0 | +| 2023-06 | CT#100 | CP-231336 | 1099 | 3 | B | Support of Caller and Callee information | 18.2.0 | +| 2023-06 | CT#100 | CP-231318 | 1100 | 2 | B | Policy Control for L4S | 18.2.0 | +| 2023-06 | CT#100 | CP-231133 | 1101 | | F | Corrections to the procedures for monitoring the data rate per network slice for a UE | 18.2.0 | +| 2023-06 | CT#100 | CP-231134 | 1102 | 1 | D | Correcting a wrong reference related to PCC rule versioning | 18.2.0 | +| 2023-06 | CT#100 | CP-231141 | 1105 | | F | Update of info and externalDocs fields | 18.2.0 | +| 2023-09 | CT#101 | CP-232086 | 1106 | 1 | B | Priority Level addition to QoS constraints | 18.3.0 | +| 2023-09 | CT#101 | CP-232090 | 1107 | 1 | F | Corrections to the definition of Group related Policy Control Data | 18.3.0 | +| 2023-09 | CT#101 | CP-232093 | 1108 | 1 | B | Completing the support of slice PDU session inactivity timer provisioning by the PCF | 18.3.0 | +| 2023-09 | CT#101 | CP-232101 | 1109 | 1 | B | Considering home TNAPs for policy decisions | 18.3.0 | +| 2023-09 | CT#101 | CP-232158 | 1110 | 1 | F | Editor's note removal for Multimodal id | 18.3.0 | +| 2023-09 | CT#101 | CP-232102 | 1111 | 1 | D | Correction on SFC abbreviation | 18.3.0 | +| 2023-09 | CT#101 | CP-232126 | 1112 | | F | Clarification on Redundant Steering Mode | 18.3.0 | +| 2023-09 | CT#101 | CP-232108 | 1113 | | B | Handling of Packet Delay Budget for PIN scenarios | 18.3.0 | +| 2023-09 | CT#101 | CP-232086 | 1114 | | F | Correction in Feature numbering | 18.3.0 | +| 2023-09 | CT#101 | CP-232107 | 1116 | | A | Incorrect description of NWDAF data | 18.3.0 | +| 2023-09 | CT#101 | CP-232115 | 1118 | 1 | A | Correction of anGwStatus attribute | 18.3.0 | +| 2023-09 | CT#101 | CP-232257 | 1119 | 1 | F | Correcting the value of hrsbolnd attribute | 18.3.0 | +| 2023-09 | CT#101 | CP-232182 | 1120 | 2 | B | Common EAS/DNAI determination for a set of UEs | 18.3.0 | +| 2023-09 | CT#101 | CP-232121 | 1121 | | B | Completion of the reporting of Satellite Backhaul changes | 18.3.0 | +| 2023-09 | CT#101 | CP-232092 | 1122 | 1 | B | Completing URSP rule enforcement | 18.3.0 | +| 2023-09 | CT#101 | CP-232120 | 1125 | | A | Correction to Access Network Charging Identifier | 18.3.0 | +| 2023-09 | CT#101 | CP-232084 | 1126 | 1 | B | Subscription to Data Rate monitoring | 18.3.0 | +| 2023-09 | CT#101 | CP-232181 | 1127 | 2 | B | Support of the congestion information measurement and reporting | 18.3.0 | +| 2023-09 | CT#101 | CP-232158 | 1128 | 1 | B | Support of the congestion information measurement and reporting | 18.3.0 | +| 2023-09 | CT#101 | CP-232085 | 1129 | | F | Update of info and externalDocs fields | 18.3.0 | +| 2023-12 | CT#102 | CP-233239 | 1130 | 1 | B | Update for the VPLMN offloading policy | 18.4.0 | +| 2023-12 | CT#102 | CP-233247 | 1131 | 1 | F | Clarification for the change of PCF for the UE | 18.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------|--------| +| 2023-12 | CT#102 | CP-233233 | 1132 | 1 | B | Introduction of new features for PDU set handle and RT latency | 18.4.0 | +| 2023-12 | CT#102 | CP-233245 | 1133 | 1 | F | Clarification on configuration of maximum group data rate | 18.4.0 | +| 2023-12 | CT#102 | CP-233250 | 1134 | 1 | B | Further progressing the definition of the network slice replacement functionality | 18.4.0 | +| 2023-12 | CT#102 | CP-233250 | 1135 | 1 | B | Further progressing the definition of the network slice replacement functionality | 18.4.0 | +| 2023-12 | CT#102 | CP-233233 | 1136 | 1 | F | Support of the new feature name EnQoSMon | 18.4.0 | +| 2023-12 | CT#102 | CP-233253 | 1138 | 2 | F | Support QoS monitoring for dynamic satellite backhaul | 18.4.0 | +| 2023-12 | CT#102 | CP-233239 | 1139 | 2 | F | Selection of traffic description for Common DNAI | 18.4.0 | +| 2023-12 | CT#102 | CP-233245 | 1140 | 3 | B | Support the management of the temporal invalidity condition | 18.4.0 | +| 2023-12 | CT#102 | CP-233228 | 1141 | 2 | F | HTTP RFCs obsoleted by IETF RFC 9113 | 18.4.0 | +| 2023-12 | CT#102 | CP-233271 | 1142 | 2 | F | Spending limits report for SM Policy | 18.4.0 | +| 2023-12 | CT#102 | CP-233244 | 1143 | 2 | B | Remove the EN for PCC rule generation | 18.4.0 | +| 2023-12 | CT#102 | CP-233267 | 1144 | | F | Presence condition correction | 18.4.0 | +| 2023-12 | CT#102 | CP-233247 | 1145 | | F | Incorrect data type | 18.4.0 | +| 2023-12 | CT#102 | CP-233247 | 1147 | | F | Correction in QoS monitoring when PDU session is released | 18.4.0 | +| 2023-12 | CT#102 | CP-233244 | 1148 | 1 | F | EN resolution on UE policy container PCRT | 18.4.0 | +| 2023-12 | CT#102 | CP-233234 | 1149 | 1 | B | Protocol description update | 18.4.0 | +| 2023-12 | CT#102 | CP-233233 | 1150 | 1 | B | Feature granularity and definition for MultiModal & PowerSaving | 18.4.0 | +| 2023-12 | CT#102 | CP-233280 | 1151 | 1 | B | Editor note removal on SMF DNN configuration | 18.4.0 | +| 2023-12 | CT#102 | CP-233245 | 1153 | 3 | B | Policy Authorization for AF requested QoS for a UE or group of UEs not identified by a UE address | 18.4.0 | +| 2023-12 | CT#102 | CP-233233 | 1155 | | B | Definition of L4S feature | 18.4.0 | +| 2023-12 | CT#102 | CP-233253 | 1163 | 1 | F | Corrections related to EnSatBackhaulCatChg feature | 18.4.0 | +| 2023-12 | CT#102 | CP-233247 | 1164 | 1 | F | Missing PCRT for UeCampingRep | 18.4.0 | +| 2023-12 | CT#102 | CP-233253 | 1166 | 1 | F | Clarifications on the dynamic satellite backhaul categories | 18.4.0 | +| 2023-12 | CT#102 | CP-233239 | 1167 | | F | Corrections on the hrsbolnd attribute | 18.4.0 | +| 2023-12 | CT#102 | CP-233229 | 1168 | 1 | F | ProblemDetails RFC 7807 obsoleted by RFC 9457 | 18.4.0 | +| 2023-12 | CT#102 | CP-233249 | 1169 | 1 | B | Support of Data Collection Application Identifier | 18.4.0 | +| 2023-12 | CT#102 | CP-233234 | 1170 | | F | Correct the reference clause and update the terminology | 18.4.0 | +| 2023-12 | CT#102 | CP-233234 | 1171 | 1 | B | Support of the Data Burst Handling Information in the PCC rule | 18.4.0 | +| 2023-12 | CT#102 | CP-233271 | 1172 | 1 | B | Clarification of PCF authorization during SM policy association establishment | 18.4.0 | +| 2023-12 | CT#102 | CP-233237 | 1176 | 1 | F | Update of info and externalDocs fields | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29541/raw.md b/marked/Rel-18/29_series/29541/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..71138e9a8417d2acc507bac2c8c2a4757b4a73f4 --- /dev/null +++ b/marked/Rel-18/29_series/29541/raw.md @@ -0,0 +1,2430 @@ + + +# 3GPP TS 29.541 V18.2.0 (2023-12) + +*Technical Specification* + +**3rd Generation Partnership Project; +Technical Specification Group Core Network and Terminals; +5G System; Network Exposure (NE) function services for Non- +IP Data Delivery (NIDD) and Short Message Services (SMS); +Stage 3 +(Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 Overview..... | 8 | +| 4.1 Introduction ..... | 8 | +| 5 Services offered by the NEF for NIDD and SMS..... | 9 | +| 5.1 Introduction ..... | 9 | +| 5.2 Nnef_SMContext Service ..... | 10 | +| 5.2.1 Service Description ..... | 10 | +| 5.2.2 Service Operations..... | 10 | +| 5.2.2.1 Introduction..... | 10 | +| 5.2.2.2 Create Service Operation ..... | 10 | +| 5.2.2.2.1 General ..... | 10 | +| 5.2.2.3 Delete Service Operation ..... | 11 | +| 5.2.2.3.1 General ..... | 11 | +| 5.2.2.4 Status Notify Service Operation ..... | 12 | +| 5.2.2.4.1 General ..... | 12 | +| 5.2.2.4.2 Notify of Individual SM Context Release (Nnef_SMContext_DeleteNotify)..... | 13 | +| 5.2.2.5 Update Service Operation..... | 13 | +| 5.2.2.5.1 General ..... | 13 | +| 5.2.2.6 Deliver Service Operation ..... | 14 | +| 5.2.2.6.1 General ..... | 14 | +| 5.3 Nnef_SMService Service ..... | 15 | +| 5.3.1 Service Description ..... | 15 | +| 5.3.2.2 MoForwardSm ..... | 15 | +| 5.3.2.2.1 General ..... | 15 | +| 6 API Definitions ..... | 15 | +| 6.1 Nnef_SMContext Service API ..... | 15 | +| 6.1.1 Introduction ..... | 15 | +| 6.1.2 Usage of HTTP..... | 16 | +| 6.1.2.1 General..... | 16 | +| 6.1.2.2 HTTP standard headers..... | 16 | +| 6.1.2.2.1 General ..... | 16 | +| 6.1.2.2.2 Content type ..... | 16 | +| 6.1.2.3 HTTP custom headers..... | 16 | +| 6.1.3 Resources..... | 16 | +| 6.1.3.1 Overview..... | 16 | +| 6.1.3.2 Resource: SM Contexts Collection..... | 17 | +| 6.1.3.2.1 Description ..... | 17 | +| 6.1.3.2.2 Resource Definition..... | 17 | +| 6.1.3.2.3 Resource Standard Methods..... | 18 | +| 6.1.3.2.4 Resource Custom Operations..... | 19 | +| 6.1.3.3 Resource: Individual SM Context..... | 19 | +| 6.1.3.3.1 Description ..... | 19 | +| 6.1.3.3.2 Resource Definition..... | 19 | +| 6.1.3.3.3 Resource Standard Methods..... | 19 | +| 6.1.3.3.4 Resource Custom Operations..... | 19 | +| 6.1.3.3.4.2.1 Description..... | 20 | +| 6.1.3.3.4.2.2 Operation Definition ..... | 20 | + +| | | | +|---------------|------------------------------------------------------|----| +| 6.1.3.3.4.3.1 | Description..... | 21 | +| 6.1.3.3.4.3.2 | Operation Definition ..... | 21 | +| 6.1.3.3.4.4.1 | Description..... | 22 | +| 6.1.3.3.4.4.2 | Operation Definition ..... | 22 | +| 6.1.4 | Custom Operations without associated resources ..... | 23 | +| 6.1.5 | Notifications ..... | 23 | +| 6.1.5.1 | General ..... | 23 | +| 6.1.5.2 | Status Notification ..... | 23 | +| 6.1.5.2.1 | Description ..... | 23 | +| 6.1.5.2.2 | Target URI..... | 23 | +| 6.1.5.2.3 | Standard Methods..... | 23 | +| 6.1.6 | Data Model ..... | 24 | +| 6.1.6.1 | General ..... | 24 | +| 6.1.6.2 | Structured data types..... | 25 | +| 6.1.6.2.1 | Introduction ..... | 25 | +| 6.1.6.2.2 | Type: SmContextCreateData..... | 26 | +| 6.1.6.2.3 | Type: SmContextCreatedData..... | 27 | +| 6.1.6.2.4 | Type: SmContextReleaseData..... | 27 | +| 6.1.6.2.5 | Type: SmContextReleasedData..... | 28 | +| 6.1.6.2.6 | Type: SmContextStatusNotification ..... | 28 | +| 6.1.6.2.7 | Type: NiddInformation ..... | 28 | +| 6.1.6.2.8 | Type: SmContextConfiguration ..... | 29 | +| 6.1.6.2.9 | Type: SmallDataRateControl ..... | 29 | +| 6.1.6.2.10 | Type: SmContextUpdateData ..... | 30 | +| 6.1.6.2.11 | Type: DeliverReqData..... | 30 | +| 6.1.6.3 | Simple data types and enumerations..... | 30 | +| 6.1.6.3.1 | Introduction ..... | 30 | +| 6.1.6.3.2 | Simple data types ..... | 30 | +| 6.1.6.3.3 | Enumeration: SmContextStatus ..... | 30 | +| 6.1.6.3.4 | Enumeration: SmallDataRateControlTimeUnit ..... | 31 | +| 6.1.6.3.5 | Enumeration: ReleaseCause..... | 31 | +| 6.1.7 | Error Handling ..... | 31 | +| 6.1.7.1 | General ..... | 31 | +| 6.1.7.2 | Protocol Errors ..... | 31 | +| 6.1.7.3 | Application Errors..... | 31 | +| 6.1.8 | Feature negotiation ..... | 32 | +| 6.1.9 | Security ..... | 32 | +| 6.1.10 | HTTP redirection..... | 32 | +| 6.2 | Nnwf_SMService Service API..... | 33 | +| 6.2.1 | Introduction ..... | 33 | +| 6.2.2 | Usage of HTTP..... | 33 | +| 6.2.2.1 | General ..... | 33 | +| 6.2.2.2 | HTTP standard headers..... | 33 | +| 6.2.2.2.1 | General ..... | 33 | +| 6.2.2.2.2 | Content type ..... | 33 | +| 6.2.2.3 | HTTP custom headers..... | 34 | +| 6.2.2.4 | HTTP multipart messages..... | 34 | +| 6.2.3 | Resources..... | 34 | +| 6.2.3.1 | Overview..... | 34 | +| 6.2.3.2 | Resource: MoSmInfo ..... | 35 | +| 6.2.3.2.1 | Description ..... | 35 | +| 6.2.3.2.2 | Resource Definition..... | 35 | +| 6.2.3.2.3 | Resource Standard Methods..... | 35 | +| 6.2.3.2.4 | Resource Custom Operations ..... | 36 | +| 6.2.4 | Custom Operations without associated resources ..... | 38 | +| 6.2.5 | Notifications ..... | 38 | +| 6.2.6 | Data Model ..... | 38 | +| 6.2.6.1 | General ..... | 38 | +| 6.2.6.2 | Structured data types..... | 38 | +| 6.2.6.3 | Simple data types and enumerations..... | 39 | +| 6.2.6.3.1 | Introduction ..... | 39 | +| 6.2.6.3.2 | Simple data types ..... | 39 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------|-----------| +| 6.2.6.4 | Data types describing alternative data types or combinations of data types ..... | 39 | +| 6.2.6.5 | Binary data..... | 39 | +| 6.1.6.5.1 | Binary Data Types..... | 39 | +| 6.2.6.5.2 | SMS Payload Information..... | 39 | +| 6.2.7 | Error Handling..... | 39 | +| 6.2.7.1 | General..... | 39 | +| 6.2.7.2 | Protocol Errors ..... | 39 | +| 6.2.7.3 | Application Errors..... | 39 | +| 6.2.8 | Feature negotiation ..... | 40 | +| 6.2.9 | Security..... | 40 | +| Annex A (normative): | OpenAPI specification ..... | 40 | +| A.1 | General..... | 40 | +| A.2 | Nnef_SMContext API..... | 41 | +| A.3 | Nnef_SMService API ..... | 48 | +| Annex B (informative): | Change history..... | 51 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document specifies the stage 3 protocol and data model for the Nnef Service Based South-Bound Interfaces for NIDD. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NEF. + +The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. + +The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. + +# --- 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 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", . +- [7] 3GPP TR 21.900: "Technical Specification Group working methods". +- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". +- [11] IETF RFC 9113: " HTTP/2". +- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [13] IETF RFC 9457: "Problem Details for HTTP APIs". +- [14] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". + +- [15] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3". +- [16] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3". +- [17] 3GPP TS 29.542: "5G System; Session management services for Non-IP Data Delivery (NIDD); Stage 3". +- [18] 3GPP TS 23.540: "5G System; Technical realization of Service Based Short Message Service Stage 2". +- [19] 3GPP TS 29.577: "5G System; IP Short Message Gateway and SMS Router For Short Message Service; Stage 3". +- [20] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [21] 3GPP TS 24.011: " Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Terms + +Void. + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|------------------------------------------------| +| DNN | Data Network Name | +| MO | Mobile Originated | +| NEF | Network Exposure Function | +| NIDD | Non-IP Data Delivery | +| SM | Session Management | +| SMF | Session Management Function | +| NSSAI | Network Slice Selection Assistance Information | +| RDS | Reliable Data Service | +| SUPI | Subscription Permanent Identifier | + +# --- 4 Overview + +## 4.1 Introduction + +Within the 5GC, the NEF offers NIDD services to the NF (e.g. SMF) or the NEF offers MO SMS service to the NF (e.g. SMS-SC) via the Nnef service based southbound interface (see 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.540 [18]). + +Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the NEF and the scope of the present specification. + +![Figure 4.1-1: Reference model – NEF. The diagram shows three network functions (SMF, AF, and SMS-SC) connected to a central Network Exposure Function (NEF). SMF connects via the N29 interface, AF connects via the N33 interface, and SMS-SC connects via the Nxx interface. All three interfaces point to a common point labeled 'Nnef' on the NEF box.](562f471e8153729557e6a4ee6343c32c_img.jpg) + +Figure 4.1-1: Reference model – NEF. The diagram shows three network functions (SMF, AF, and SMS-SC) connected to a central Network Exposure Function (NEF). SMF connects via the N29 interface, AF connects via the N33 interface, and SMS-SC connects via the Nxx interface. All three interfaces point to a common point labeled 'Nnef' on the NEF box. + +Figure 4.1-1: Reference model – NEF + +The functionalities supported by the NEF are listed in clause 6.2.5 of 3GPP TS 23.501 [2]. + +# 5 Services offered by the NEF for NIDD and SMS + +## 5.1 Introduction + +The table 5.1-1 shows the NEF Services and Service Operations for NIDD and SMS: + +Table 5.1-1 List of NEF Services for NIDD and SMS + +| Service Name | Service Operations | Operation Semantics | Example Consumer(s) | Mapped Service Operation | +|----------------|--------------------|---------------------|---------------------|------------------------------------| +| Nnef_SMContext | Create | Request/Response | SMF | Nnef_SMContext_Create | +| | Delete | Request/Response | SMF | Nnef_SMContext_Delete | +| | Status Notify | Subscribe/Notify | SMF | Nnef_SMContext_DeleteNotify (NOTE) | +| | Update | Request/Response | SMF | | +| | Delivery | Request/Response | SMF | Nnef_SMContext_Delivery | +| Nnef_SMService | MoForwardSm | Request/Response | SMS-SC | Nnef_SMService_MoForwardSm | + +NOTE: The Status Notify service operation models the Nnef\_SMContext\_DeleteNotify service operation specified in 3GPP TS 23.502 [3] (see clause 5.2.2.4.2). + +Table 5.1-2 summarizes the corresponding APIs defined for this specification. + +Table 5.1-2: API Descriptions + +| Service Name | Clause | Description | OpenAPI Specification File | apiName | Annex | +|----------------|--------|------------------------|-----------------------------|----------------|-------| +| Nnef_SMContext | 6.1 | Nnef SMContext Service | TS29541_Nnef_SMContext.yaml | nnef-smcontext | A.2 | +| Nnef_SMService | 6.2 | Nnef SMService Service | TS29541_Nnef_SMService.yaml | nnef-smservice | A.3 | + +## 5.2 Nnef\_SMContext Service + +### 5.2.1 Service Description + +The service allows a NF to manage the SM Contexts on NEF for NIDD. A NF as service consumer (e.g. SMF) can create, update or release SM Contexts for NIDD on NEF. A created SM Context for NIDD may also be released by NEF. + +### 5.2.2 Service Operations + +#### 5.2.2.1 Introduction + +The Nnef\_SMContext service supports following service operations: + +- Create +- Delete +- StatusNotify +- Update +- Deliver + +#### 5.2.2.2 Create Service Operation + +##### 5.2.2.2.1 General + +The Create service operation is used during the following procedure: + +- SMF-NEF Connection Establishment procedure (see 3GPP TS 23.502 [3], clause 4.25.2) + +The Create service operation is invoked by a NF Service Consumer (e.g. a SMF) towards the NEF, when the SMF received a PDU Session establishment request from the UE with PDU Session type of "Unstructured", and the subscription information corresponding to the UE requested DNN includes the "NEF Identity for NIDD". There shall be only one individual SM context per PDU session. + +The NF Service Consumer (e.g. the SMF) shall create the SM Context for NIDD on NEF by sending the HTTP POST request towards the SM Contexts Collection resource as shown in Figure 5.2.2.2.1-1. + +![Sequence diagram showing the Create Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 201 Created status or a 4xx/5xx error status.](cd48273072c5c3a23e11fde892d1b6b6_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant NEF + Note left of NF Service Consumer: + NF Service Consumer->>NEF: 1. POST .../sm-contexts (SmContextCreateData) + Note right of NEF: + NEF-->>NF Service Consumer: -2a. 201 Created (SmContextCreatedData) + Note right of NEF: + NEF-->>NF Service Consumer: -2b. 4xx/5xx (ProblemDetails) or 3xx + +``` + +Sequence diagram showing the Create Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 201 Created status or a 4xx/5xx error status. + +**Figure 5.2.2.2.1-1: Create Service Operation** + +1. The NF Service Consumer shall send a POST request to the resource representing the SM Contexts Collection resource of the NEF with a "SmContextCreateData" object in request body, including: + - SUPI of the UE; + - PDU session ID; + - S-NSSAI associated with the PDU session; + +- DNN of the PDU session; + - NIDD information, such as GPSI, AF ID, etc.; + - NEF ID, indicating the provisioned identity for NIDD service; + - URI of the Individual PDU session resource for downlink data delivery (see clause 6.1.3.2 of 3GPP TS 29.542 [17]); + - Notification URI to receive the SM Context notifications; + - optionally the indication of UE capability to support Reliable Data Service (RDS); + - optionally the configuration parameters, e.g. serving PLMN rate control, small data rate control, etc.; + - optionally small data rate control status, if small data rate control is previously enabled and to be resumed +- 2a. On success, "201 Created" shall be returned and the "Location" header shall be present and shall contain the URI of the created Individual SM Context resource. + +The content of the POST response shall contain a "SmContextCreatedData" object, including: + +- SUPI of the UE; + - PDU session ID; + - S-NSSAI associated with the PDU session; + - DNN of the PDU session; + - NEF ID, indicating the provisioned identity for NIDD service; + - optionally the indication of NEF capability to support Reliable Data Service (RDS); + - optionally the indication of NEF capability to support Extended Buffering; + - optionally Maximum Packet Size in bytes for NIDD data packet. +- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.2.3.1-3 shall be returned, the response body should contain a "ProblemDetails" object with "cause" attribute set to one of the application errors listed in Table 6.1.3.2.3.1-3. + +#### 5.2.2.3 Delete Service Operation + +##### 5.2.2.3.1 General + +The Delete service operation is used during the following procedure: + +- SMF Initiated SMF-NEF Connection Release procedure (see 3GPP TS 23.502 [3], clause 4.25.7) + +The Delete service operation is invoked by a NF Service Consumer (e.g. a SMF) towards the NEF, when the PDU Session Release is initiated and a SM context for NIDD has been previously created on NEF for the PDU session. + +The NF Service Consumer (e.g. the SMF) shall delete the SM Context for NIDD on NEF by invoking the "release" custom operation on the Individual SM Context resource as shown in Figure 5.2.2.3.1-1. + +![Sequence diagram for Delete Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content / 200 OK (SmContextReleasedData) or a 4xx/5xx (ProblemDetails) or 3xx status code.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant NEF + Note left of NF Service Consumer: 1. POST ../sm-contexts/{smContextId}/release (SmContextReleaseData) + NF Service Consumer->>NEF: Request + Note right of NEF: -2a. 204 No Content / 200 OK (SmContextReleasedData) + NEF-->>NF Service Consumer: Response + Note right of NEF: -2b. 4xx/5xx (ProblemDetails) or 3xx + NEF-->>NF Service Consumer: Response + +``` + +Sequence diagram for Delete Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content / 200 OK (SmContextReleasedData) or a 4xx/5xx (ProblemDetails) or 3xx status code. + +**Figure 5.2.2.3.1-1: Delete Service Operation** + +1. The NF Service Consumer shall send a HTTP POST request towards the URI of "release" custom operation on the Individual SM Context resource received from the "Location" header during a successful Create service operation invocation (See clause 5.2.2.2). The request body shall contain a "SmContextReleaseData" object. +- 2a. On success, "204 No Content" shall be returned if no information is to be returned to the NF service consumer; otherwise "200 OK" shall be returned with a "SmContextReleasedData" object in response body including necessary information to the NF service consumer, e.g.: + - Small Data Rate Control status, if Small Data Rate Control is enforced; + - APN Rate Status, if APN Rate Control is enforced +- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.2-2 shall be returned, the response body should contain a "ProblemDetails" object with "cause" attribute set to one of the application errors listed in Table 6.1.3.3.4.2.2-2. + +#### 5.2.2.4 Status Notify Service Operation + +##### 5.2.2.4.1 General + +The Status Notify service operation is used during the following procedure: + +- NEF Initiated SMF-NEF Connection Release procedure (see 3GPP TS 23.502 [3], clause 4.25.8) + +The Status Notify service operation is invoked by the NEF to inform a NF Service Consumer (e.g. a SMF), when the status of the Individual SM Context has changed. + +The NEF shall inform the status change of the Individual SM Context resource by sending the HTTP POST method towards the Notification URI as shown in Figure 5.2.2.4.1-1. + +![Sequence diagram for Status Notify Service Operation. The NEF sends a POST request to the NF Service Consumer. The NF Service Consumer responds with either a 204 No content or a 4xx/5xx (ProblemDetails) or 3xx status code.](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +``` + +sequenceDiagram + participant NEF + participant NF Service Consumer + Note right of NEF: 1. POST {notificationUri} (SmContextStatusNotification) + NEF->>NF Service Consumer: Request + Note left of NF Service Consumer: -2a. 204 No content + NF Service Consumer-->>NEF: Response + Note left of NF Service Consumer: -2b. 4xx/5xx (ProblemDetails) or 3xx + NF Service Consumer-->>NEF: Response + +``` + +Sequence diagram for Status Notify Service Operation. The NEF sends a POST request to the NF Service Consumer. The NF Service Consumer responds with either a 204 No content or a 4xx/5xx (ProblemDetails) or 3xx status code. + +**Figure 5.2.2.4.1-1: Status Notify Service Operation** + +1. The NEF shall send a POST request towards the Notification URI received in the Create service operation request (See clause 5.2.2.2). The request body shall contain a "SmContextStatusNotification" object indicating the changed status of the Individual SM Context resource. The "smContextId" attribute shall contain the URI of the SM Context resource that triggers the notification. +- 2a. On success, "204 No content" shall be returned without response body. +- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.5.2.3.1-2 shall be returned, the response body should contain a "ProblemDetails" object. + +##### 5.2.2.4.2 Notify of Individual SM Context Release (Nnef\_SMContext\_DeleteNotify) + +During NEF initiated SMF-NEF connection release procedure (see 3GPP TS 23.502 [3], clause 4.25.8), the NEF shall send Status Notification to inform the NF service consumer that the Individual SM Context is released. + +The requirements in clause 5.2.2.4.1 shall be applied, with following additions: + +1. Same as step 1 of Figure 5.2.2.4.1-1, the NEF shall set the value of "status" attribute in the request body to "RELEASED". + - If Small Data Rate Control is enforced, the response body should include the Small Data Rate Control status. + - If APN Rate Control is enforced, the response body should include the APN Rate Status. + +#### 5.2.2.5 Update Service Operation + +##### 5.2.2.5.1 General + +The Update service operation is invoked by a NF Service Consumer, e.g. a SMF, towards the NEF, when the SMF detects that some of the configurations of the PDU session has changed and the related SM Context for NIDD needs to be updated accordingly. + +The NF Service Consumer (e.g. the SMF) shall update the SM Context for NIDD on NEF by invoking the "update" custom operation of the Individual SM Context resource as shown in Figure 5.2.2.5.1-1. + +![Sequence diagram for Update Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content or an error status code (4xx/5xx or 3xx).](2e399449b7f62d40167a65ca88888917_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant NEF + Note left of NF Service Consumer: 1. POST ../sm-contexts/{smContextId}/update (SmContextUpdateData) + NF Service Consumer->>NEF: Request + Note right of NEF: 2a. 204 No Content + NEF-->>NF Service Consumer: Response + Note right of NEF: 2b. 4xx/5xx (ProblemDetails) or 3xx + NEF-->>NF Service Consumer: Response + +``` + +Sequence diagram for Update Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content or an error status code (4xx/5xx or 3xx). + +Figure 5.2.2.5.1-1: Update Service Operation + +1. The NF Service Consumer shall send a POST request to the URI of "update" custom operation on an Individual SM Context resource, with a "SmContextUpdateData" object in request body containing the attributes to be updated, e.g.: + - URI of the resource to receive downlink data delivery for NIDD; + - Notification URI to receive the SM Context notifications; + - modified configuration parameters, e.g. serving PLMN rate control, small data rate control, etc. + +NOTE: If both the NEF and the NF service consumer (i.e. the SMF) supports "BIUMR" feature, the SMF can include the updated binding indication(s) for multiple PDU session resources (for NIDD downlink data delivery) and/or notification URIs (for SM Context notifications), as specified in clauses 6.12.1 and 5.2.3.2.6 of 3GPP TS 29.500 [4]. + +2a. On success, "204 No Content" shall be returned. + +2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.3.2-2 shall be returned, the response body should contain a ProblemDetails object with "cause" attribute set to one of the application errors listed in Table 6.1.3.3.4.3.2-2. + +#### 5.2.2.6 Deliver Service Operation + +##### 5.2.2.6.1 General + +The Deliver service operation is invoked by a NF Service Consumer, e.g. a SMF, to transport Mobile Originated data packet via NEF. + +The NF Service Consumer (e.g. the SMF) shall deliver Mobile Originate data via NEF by invoking the "deliver" custom operation of the Individual SM Context resource as shown in Figure 5.2.2.6.1-1. + +![Sequence diagram showing the Deliver Service Operation between an NF Service Consumer and an NEF. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content (success) or a 4xx/5xx (ProblemDetails) or 3xx (failure/redirection) status code.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant NEF + Note left of NF Service Consumer: 1. POST ../sm-contexts/{smContextId}/deliver (DeliverReqData) + NF Service Consumer->>NEF: Request + Note right of NEF: 2a. 204 No Content + NEF-->>NF Service Consumer: Response + Note right of NEF: 2b. 4xx/5xx (ProblemDetails) or 3xx + NEF-->>NF Service Consumer: Response + +``` + +Sequence diagram showing the Deliver Service Operation between an NF Service Consumer and an NEF. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content (success) or a 4xx/5xx (ProblemDetails) or 3xx (failure/redirection) status code. + +**Figure 5.2.2.5.6-1: Deliver Service Operation** + +1. The NF Service Consumer shall send a POST request to the URI of "deliver" custom operation on an Individual SM Context resource, with the request body containing: + - the MO data as binary body part with content type set as "application/octet-stream"; and + - a "DeliverReqData" object as another body part with "data" attribute refer to the MO data binary part. +- 2a. On success, "204 No Content" shall be returned. +- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.4.2-2 shall be returned. The response body should contain a ProblemDetails object with "cause" attribute set to one of the application errors listed in Table 6.1.3.3.4.4.2-2. + +## 5.3 Nnef\_SMService Service + +### 5.3.1 Service Description + +See 3GPP TS 23.540 [18] clause 6.8.1 + +#### 5.3.2.2 MoForwardSm + +##### 5.3.2.2.1 General + +The MoForwardSm service operation shall be used to transmit MO SMS message via NEF. + +It is used in the following procedures: + +- MSISDN-less MO SMS message transfer (see clause 5.2.4 of 3GPP TS 23.540 [18]). + +The NF Service Consumer (e.g. SMS-SC) shall transmit MO SMS message to NEF by using the HTTP POST method as shown in Figure 5.3.2.2.1-1. + +![Sequence diagram showing SBI-based MO SM transfer between NF Service Consumer and NEF. The consumer sends a POST request to the NEF, which responds with either a 200 OK or an error status code.](3f1987804d7d78bc3b3bc560e974280a_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant NEF + Note left of NF Service Consumer: 1. POST ../sm-contexts/{supi}/sendsms (SmsData) + NF Service Consumer->>NEF: Request + Note right of NEF: 2a. 200 OK (SmsDeliveryData) + NEF-->>NF Service Consumer: Response + Note right of NEF: 2b. 4xx/5xx (ProblemDetails) or 3xx + NEF-->>NF Service Consumer: Response + +``` + +Sequence diagram showing SBI-based MO SM transfer between NF Service Consumer and NEF. The consumer sends a POST request to the NEF, which responds with either a 200 OK or an error status code. + +Figure 5.3.2.2.1-1: SBI-based MO SM transfer + +1. The NF Service Consumer shall send a POST request to the resource representing the UE's Mobile Originated Short Message Information resource (i.e. .../sm-contexts/{supi}/sendsms) of the NEF. The content of the POST request shall contain the SMS message to be sent. +- 2a. On success, "200 OK" shall be returned with "SmsDeliveryData" object contains the MO SMS Delivery Report in the response body. +- 2b. On failure, or redirection, one of the HTTP status code listed in Table 6.2.3.2.4.2.2-2 shall be returned. + +# 6 API Definitions + +## 6.1 Nnef\_SMContext Service API + +### 6.1.1 Introduction + +The Nnef\_SMContext service shall use the Nnef\_SMContext service API. + +The request URI used in HTTP request from the NF service consumer towards the NF service producer shall have the structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.: + +**{apiRoot}{apiName}{apiVersion}{apiSpecificResourceUriPart}** + +with the following components: + +- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5]. +- The shall be "nnef-smcontext". +- The shall be "v1". +- The shall be set as described in clause 6.1.3. + +### 6.1.2 Usage of HTTP + +#### 6.1.2.1 General + +HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4]. + +HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4]. + +The OpenAPI [6] specification of HTTP messages and content bodies for the Nnef\_SMContext API is contained in Annex A. + +#### 6.1.2.2 HTTP standard headers + +##### 6.1.2.2.1 General + +See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers. + +##### 6.1.2.2.2 Content type + +JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json". + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13]. + +#### 6.1.2.3 HTTP custom headers + +The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be applicable. In this release of the specification, no specific custom headers are defined for the Nnef\_SMContext service. + +### 6.1.3 Resources + +#### 6.1.3.1 Overview + +Figure 6.1.3.1-1 describes the resource URI structure of the Nnef\_SMContext API. + +![Figure 6.1.3.1-1: Resource URI structure of the Nnef_SMContext API. The diagram shows a hierarchical tree structure. The root is {apiRoot}/nnelf-smcontext/. A line branches down to a box containing /sm-contexts. From this box, a line branches down to /{smContextId}. From /{smContextId}, three lines branch out to three separate dashed boxes containing /update, /release, and /deliver respectively.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +``` + +graph TD + Root["{apiRoot}/nnelf-smcontext/"] --> SMContexts["/sm-contexts"] + SMContexts --> SMContextId["/{smContextId}"] + SMContextId --> Update["/update"] + SMContextId --> Release["/release"] + SMContextId --> Deliver["/deliver"] + +``` + +Figure 6.1.3.1-1: Resource URI structure of the Nnef\_SMContext API. The diagram shows a hierarchical tree structure. The root is {apiRoot}/nnelf-smcontext/. A line branches down to a box containing /sm-contexts. From this box, a line branches down to /{smContextId}. From /{smContextId}, three lines branch out to three separate dashed boxes containing /update, /release, and /deliver respectively. + +**Figure 6.1.3.1-1: Resource URI structure of the Nnef\_SMContext API** + +Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 6.1.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|------------------------|--------------------------------------------------------------------------|---------------------------------|--------------------------------------------| +| SM Contexts Collection | {apiRoot}/nnelf-smcontext//sm-contexts | POST | Creates an Individual SM Context resource. | +| Individual SM Context | {apiRoot}/nnelf-smcontext//sm-contexts/{smContextId}/release | release (POST) | Deletes an Individual SM Context resource. | +| | {apiRoot}/nnelf-smcontext//sm-contexts/{smContextId}/update | update (POST) | Updates an Individual SM Context resource. | +| | {apiRoot}/nnelf-smcontext//sm-contexts/{smContextId}/deliver | deliver (POST) | Delivers Mobile Originated data packet. | + +#### 6.1.3.2 Resource: SM Contexts Collection + +##### 6.1.3.2.1 Description + +This resource represents the collection of the Individual SM Context resources created in the NEF. + +This resource is modelled with the Collection resource archetype (see clause C.2 of 3GPP TS 29.501 [5]). + +##### 6.1.3.2.2 Resource Definition + +Resource URI: {apiRoot}/nnelf-smcontext//sm-contexts + +This resource shall support the resource URI variables defined in table 6.1.3.2.2-1. + +**Table 6.1.3.2.2-1: Resource URI variables for this resource** + +| Name | Definition | +|------------|------------------| +| apiRoot | See clause 6.1.1 | +| apiVersion | See clause 6.1.1 | + +##### 6.1.3.2.3 Resource Standard Methods + +###### 6.1.3.2.3.1 POST + +This method creates an Individual SM Context resource in the SM Context Collection. + +This method shall support the URI query parameters specified in table 6.1.3.2.3.1-1. + +**Table 6.1.3.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 6.1.3.2.3.1-2 and the response data structures and response codes specified in table 6.1.3.2.3.1-3. + +**Table 6.1.3.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|---------------------|---|-------------|------------------------------------------------------------| +| SmContextCreateData | M | 1 | Representation of the Individual SM context to be created. | + +**Table 6.1.3.2.3.1-3: Data structures supported by the Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|---------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SmContextCreateData | M | 1 | 201 Created | Successful creation of an Individual SM context. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection.
(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection.
(NOTE 2) | +| ProblemDetails | O | 1 | 403 Forbidden | The "cause" attribute may be used to indicate the following application errors:
- USER_UNKNOWN
- NIDD_CONFIGURATION_NOT_AVAILABLE

See table 6.1.7.3-1 for the description of these errors. | + +NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] other than those specified in the table above also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). + +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.1.3.2.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.1.3.2.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +##### 6.1.3.2.4 Resource Custom Operations + +None. + +#### 6.1.3.3 Resource: Individual SM Context + +##### 6.1.3.3.1 Description + +This resource represents an Individual SM Context resource in the NEF. + +This resource is modelled with the Document resource archetype (see clause C.2 of 3GPP TS 29.501 [5]). + +##### 6.1.3.3.2 Resource Definition + +Resource URI: {apiRoot}/nnef-smcontext//sm-contexts/{smContextId} + +This resource shall support the resource URI variables defined in table 6.1.3.3.2-1. + +**Table 6.1.3.3.2-1: Resource URI variables for this resource** + +| Name | Definition | +|-------------|--------------------------------------------------------------------------------| +| apiRoot | See clause 6.1.1 | +| apiVersion | See clause 6.1.1 | +| smContextId | SM context identifier assigned by the NEF during the Create service operation. | + +##### 6.1.3.3.3 Resource Standard Methods + +There is no standard HTTP method supported by this resource. + +##### 6.1.3.3.4 Resource Custom Operations + +###### 6.1.3.3.4.1 Overview + +This resource supports custom operation(s) as specified in table 6.1.3.3.4.1-1. + +**Table 6.1.3.3.4.1-1: Custom operations** + +| Custom operation URI | Mapped HTTP method | Description | +|-----------------------|--------------------|---------------------------| +| {resourceUri}/release | POST | Delete service operation. | +| {resourceUri}/update | POST | Update service operation. | +| {resourceUri}/deliver | POST | Deliver service operation | + +6.1.3.3.4.2 Operation: release + +6.1.3.3.4.2.1 Description + +This custom operation releases an Individual SM Context resource previously created in the NEF. + +6.1.3.3.4.2.2 Operation Definition + +This operation shall support the request data structures specified in table 6.1.3.2.4.2.2-1 and the response data structure and response codes specified in table 6.1.3.2.4.2.2-2. + +**Table 6.1.3.3.4.2.2-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------|---|-------------|-------------------------------------------------------------------------| +| SmContextReleaseData | M | 1 | Representation of the information to release the Individual SM context. | + +**Table 6.1.3.3.4.2.2-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SmContextReleasedData | M | 1 | 200 OK | Successful release of an Individual SM context with information sent to the NF service consumer. | +| n/a | | | 204 No Content | Successful release of an Individual SM context without information sent to the NF service consumer. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection.
(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection.
(NOTE 2) | +| ProblemDetails | O | 1 | 404 Not Found | The "cause" attribute may be used to indicate the following application errors:
- CONTEXT_NOT_FOUND

See table 6.1.7.3-1 for the description of these errors. | + +NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] other than those specified in the table above also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). + +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.1.3.3.4.2.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.1.3.3.4.2.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +6.1.3.3.4.3 Operation: update + +6.1.3.3.4.3.1 Description + +This custom operation updates an individual SM Context resource. + +6.1.3.3.4.3.2 Operation Definition + +This operation shall support the request data structures specified in table 6.1.3.3.4.3.2-1 and the response data structure and response codes specified in table 6.1.3.3.4.3.2-2. + +**Table 6.1.3.3.4.3.2-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------|---|-------------|----------------------------------------------------------------------| +| SmContextUpdate Data | M | 1 | Representation of the updates to apply to the Individual SM context. | + +**Table 6.1.3.3.4.3.2-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful update of the Individual SM context, when the NEF does not need to return information in the response. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection. (NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection. (NOTE 2) | +| ProblemDetails | O | 1 | 404 Not Found | The "cause" attribute may be used to indicate the following application errors:
- CONTEXT_NOT_FOUND
See table 6.1.7.3-1 for the description of these errors. | + +NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] other than those specified in the table above also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). + +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.1.3.3.4.3.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.1.3.3.4.3.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +6.1.3.3.4.4 Operation: deliver + +6.1.3.3.4.4.1 Description + +This custom operation transports Mobile Originated data packet via NEF. + +6.1.3.3.4.4.2 Operation Definition + +This operation shall support the request data structures specified in table 6.1.3.3.4.4.2-1 and the response data structure and response codes specified in table 6.1.3.3.4.4.2-2. + +**Table 6.1.3.3.4.4.2-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------|---|-------------|-----------------------------------------------------------------------------------------------------| +| DeliverReqData | M | 1 | The data for Deliver service request, including the Mobile Originated data to be delivered via NEF. | + +**Table 6.1.3.3.4.4.2-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful delivery of Mobile Originate data via NEF. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection. (NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection. (NOTE 2) | +| ProblemDetails | O | 1 | 404 Not Found | The "cause" attribute may be used to indicate the following application errors:
- CONTEXT_NOT_FOUND
See table 6.1.7.3-1 for the description of these errors. | + +NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] other than those specified in the table above also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). + +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.1.3.3.4.4.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.1.3.3.4.4.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +### 6.1.4 Custom Operations without associated resources + +In this release of this specification, no custom operations without associated resources are defined. + +### 6.1.5 Notifications + +#### 6.1.5.1 General + +This clause specifies the notifications provided by the Nnef\_SMContext service. + +Notifications shall comply to clause 6.2 of 3GPP TS 29.500 [4] and clause 4.6.2.3 of 3GPP TS 29.501 [5]. + +#### 6.1.5.2 Status Notification + +##### 6.1.5.2.1 Description + +If the NF Service Consumer (e.g. the SMF) has provided the Notification URI for getting notified about change of SM Context status, the NEF shall notify the NF Service Consumer when the SM Context status is updated. + +##### 6.1.5.2.2 Target URI + +The Notification URI "{notificationUri}" shall be used with the resource URI variables defined in table 6.1.5.2.2-1. + +**Table 6.1.5.2.2-1: Resource URI variables for this resource** + +| Name | Definition | +|-----------------|---------------------------------------------------| +| notificationUri | String formatted as URI with the Notification Uri | + +##### 6.1.5.2.3 Standard Methods + +###### 6.1.5.2.3.1 POST + +This method shall support the request data structures specified in table 6.1.5.2.3.1-1 and the response data structures and response codes specified in table 6.1.5.2.3.1-2. + +**Table 6.1.5.2.3.1-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------------|---|-------------|-------------------------------------------------------| +| SmContextStatusNotification | M | 1 | Representation of the SM Context status notification. | + +**Table 6.1.5.2.3.1-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|---------------------------------------------------------| +| n/a | | | 204 No Content | Successful notification of the SM context status change | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection.
(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection.
(NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). + +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.1.5.2.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | A URI pointing to the endpoint of the NF service consumer to which the notification should be sent. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the notification is redirected | + +**Table 6.1.5.2.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | A URI pointing to the endpoint of the NF service consumer to which the notification should be sent. For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the notification is redirected | + +### 6.1.6 Data Model + +#### 6.1.6.1 General + +This clause specifies the application data model supported by the API. + +Table 6.1.6.1-1 specifies the data types defined for the Nnef\_SMContext service based interface protocol. + +**Table 6.1.6.1-1: Nnef\_SMContext specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|------------------------------|----------------|------------------------------------------------------------------------------|---------------| +| SmContextCreateData | 6.1.6.2.2 | Information within Create SM Context Request | | +| SmContextCreatedData | 6.1.6.2.3 | Information within Create SM Context Response | | +| SmContextReleaseData | 6.1.6.2.4 | | | +| SmContextReleasedData | 6.1.6.2.5 | | | +| SmContextStatusNotification | 6.1.6.2.6 | Information within Notify SM Context Status Request | | +| NiddInformation | 6.1.6.2.7 | NIDD information associated to the SM Context | | +| SmContextConfiguration | 6.1.6.2.8 | NIDD related configurations that should be applied for the SM Context on NEF | | +| SmallDataRateControl | 6.1.6.2.9 | Data rate control information | | +| SmContextUpdateData | 6.1.6.2.10 | Information within Update SM Context Request | | +| DeliverReqData | 6.1.6.2.11 | Information within Deliver Service Operation Request | | +| SmContextStatus | 6.1.6.3.3 | Enumeration of the status for an Individual SM Context | | +| SmallDataRateControlTimeUnit | 6.1.6.3.4 | Enumeration of the time units that are applied to data rate control | | +| ReleaseCause | 6.1.6.3.5 | Enumeration of causes for SM Context release | | + +Table 6.1.6.1-2 specifies data types re-used by the Nnef\_SMContext service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the N service based interface. + +**Table 6.1.6.1-2: Nnef\_SMContext re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|---------------------|---------------------|-------------------------------------------------------|---------------| +| Uri | 3GPP TS 29.571 [14] | Uniform Resource Identifier | | +| Supi | 3GPP TS 29.571 [14] | Subscription Permanent Identifier | | +| Gpsi | 3GPP TS 29.571 [14] | General Public Subscription Identifier | | +| SupportedFeatures | 3GPP TS 29.571 [14] | Supported features | | +| PduSessionId | 3GPP TS 29.571 [14] | PDU Session Identifier | | +| Dnn | 3GPP TS 29.571 [14] | Data Network Name | | +| Snssai | 3GPP TS 29.571 [14] | Single Network Slice Selection Assistance Information | | +| ProblemDetails | 3GPP TS 29.571 [14] | Error description | | +| SmallDataRateStatus | 3GPP TS 29.571 [14] | Small Data Rate Control Status | | +| ExternalGroupId | 3GPP TS 29.571 [14] | External Group Identifier | | +| RefToBinaryData | 3GPP TS 29.571 [14] | Reference to binary data part | | +| RedirectResponse | 3GPP TS 29.571 [14] | Redirect Response | | + +#### 6.1.6.2 Structured data types + +##### 6.1.6.2.1 Introduction + +This clause defines the structures to be used in resource representations. + +##### 6.1.6.2.2 Type: SmContextCreateData + +Table 6.1.6.2.2-1: Definition of type SmContextCreateData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| supi | Supi | M | 1 | This IE shall contain the subscriber permanent identity of the UE. | | +| pduSessionId | PduSessionId | M | 1 | This IE shall contain the PDU Session ID indicating the PDU session associated with the SM Context for NIDD to be created. | | +| dnn | Dnn | M | 1 | This IE shall contain the requested DNN. | | +| snssai | Snssai | M | 1 | This IE shall contain the requested S-NSSAI for the home PLMN. | | +| nefld | string | M | 1 | This IE shall contain the NEF ID of the target NEF (see clause 6.1.6.2.48 of 3GPP TS 29.510 [10]). | | +| dlNiddEndPoint | Uri | M | 1 | This IE shall contain the URI of the Individual PDU session resource (see clause 6.1.3.2 of 3GPP TS 29.542 [17]) provided by the NF service consumer to handle downlink NIDD data delivery. | | +| notificationUri | Uri | M | 1 | This IE shall contain the URI to receive SM Context Status Notifications sent by the NEF. | | +| niddInfo | NiddInformation | O | 0..1 | When present, this IE shall contain the information used for the SM Context. | | +| rdsSupport | boolean | O | 0..1 | When present, this IE shall indicate the UE capability to support RDS.

The value of this IE shall be set as following:
- true: UE supports RDS
- false (default): UE does not support RDS | | +| smContextConfig | SmContextConfiguration | O | 0..1 | When present, this IE shall contain the configuration for the NIDD. | | +| supportedFeatures | SupportedFeatures | C | 0..1 | This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported. | | + +##### 6.1.6.2.3 Type: SmContextCreatedData + +Table 6.1.6.2.3-1: Definition of type SmContextCreatedData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|-------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| supi | Supi | M | 1 | This IE shall contain the subscriber permanent identify of the UE. | | +| pduSessionId | PduSessionId | M | 1 | This IE shall contain the PDU Session ID indicating the PDU session associated with the SM Context for NIDD to be created. | | +| dnn | Dnn | M | 1 | This IE shall contain the requested DNN. | | +| snssai | Snssai | M | 1 | This IE shall contain the requested S-NSSAI for the home PLMN. | | +| nefId | string | M | 1 | This IE shall contain the NEF ID of the target NEF (see clause 6.1.6.2.48 of 3GPP TS 29.510 [10]). | | +| rdsSupport | boolean | O | 0..1 | When present, this IE shall indicate the NEF capability to support RDS.

The value of this IE shall be set as following:
- true: NEF supports RDS
- false (default): NEF does not support RDS | | +| extBufSupport | boolean | O | 0..1 | When present, this IE shall indicate whether Extended Buffering applies or not.

The value of this IE shall be set as following:
- true: Extended Buffering applies
- false (default): Extended Buffering does not apply | | +| supportedFeatures | SupportedFeatures | C | 0..1 | This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported. | | +| maxPacketSize | integer | O | 0..1 | Maximum Packet Size in bytes for NIDD data packet.
When received from the NEF, SMF shall inform the UE of the Maximum Packet Size in the PCO in the PDU Session Establishment Accept message. | | + +##### 6.1.6.2.4 Type: SmContextReleaseData + +Table 6.1.6.2.4-1: Definition of type SmContextReleaseData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------|---|-------------|-------------------------------------|---------------| +| cause | ReleaseCause | M | 1 | The cause to release the SM Context | | + +##### 6.1.6.2.5 Type: SmContextReleasedData + +Table 6.1.6.2.5-1: Definition of type SmContextReleasedData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------|---------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| smallDataRateStatus | SmallDataRateStatus | C | 0..1 | This IE shall be present if the Small Data Rate Control is enabled for the SM Context.

When present, this IE shall contain the Small Data Rate Control Status, as specified in clause 5.31.14.3 of 3GPP TS 23.501 [2]. | | +| apnRateStatus | ApnRateStatus | C | 0..1 | This IE shall be present if the APN Rate Control is enabled for the SM Context.

When present, this IE shall contain the APN Rate Status, as specified in clause 5.4.4.40 of 3GPP TS 29.571 [14]. | | + +##### 6.1.6.2.6 Type: SmContextStatusNotification + +Table 6.1.6.2.6-1: Definition of type SmContextStatusNotification + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------|---------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| status | SmContextStatus | M | 1 | This IE shall contain the current status of the SM Context | | +| smContextId | Uri | M | 1 | This IE shall contain the URI of the SM Context resource that triggers the notification. | | +| cause | ReleaseCause | M | 1 | The cause to release the SM Context | | +| smallDataRateStatus | SmallDataRateStatus | C | 0..1 | This IE shall be present if the SM Context is released and Small Data Rate Control is enabled for the SM Context.

When present, this IE shall contain the Small Data Rate Control Status, as specified in clause 5.31.14.3 of 3GPP TS 23.501 [2]. | | +| apnRateStatus | ApnRateStatus | C | 0..1 | This IE shall be present if the APN Rate Control is enabled for the SM Context.

When present, this IE shall contain the APN Rate Status, as specified in clause 5.4.4.40 of 3GPP TS 29.571 [14]. | | + +##### 6.1.6.2.7 Type: NiddInformation + +Table 6.1.6.2.7-1: Definition of type NiddInformation + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| extGroupId | ExternalGroupId | O | 0..1 | When present, this IE shall contain the External group Id of the UE. | | +| gpsi | Gpsi | O | 0..1 | When present, this IE shall contain the GPSI of the UE. | | +| aflid | string | O | 0..1 | The string identifying the AF as the owner of associated NIDD Configuration, which is received from Nidd Information in UDM (See clause 6.1.6.2.35 of 3GPP TS 29.503 [16]). | | + +NOTE: At least one of the attributes in the table shall be present. + +##### 6.1.6.2.8 Type: SmContextConfiguration + +Table 6.1.6.2.8-1: Definition of type SmContextConfiguration + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------|----------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| smalDataRateControl | SmallDataRateControl | O | 0..1 | When present, this IE shall contain the configured Small Data Rate Control for downlink data, as specified in clause 5.31.14.3 of 3GPP TS 23.501 [2]. | | +| smallDataRateStatus | SmallDataRateStatus | C | 0..1 | This IE shall contain the Small Data Rate Status if the Small Data Rate Status is available (see clause 5.31.14.3 of 3GPP TS 23.501 [2]). | | +| servPlmnDataRateCtl | integer | O | 0..1 | When present, this IE shall contain the maximum allowed number of Downlink NAS Data PDUs per deci hour of the serving PLMN, as specified in clause 5.31.14.2 of 3GPP TS 23.501 [2].

In Update service operation, this IE may be set to null value indicating the Serving PLMN Rate Control is disabled.

Minimum: 10 | | + +NOTE: At least one of the attributes in the table shall be present. + +##### 6.1.6.2.9 Type: SmallDataRateControl + +Table 6.1.6.2.8-1: Definition of type SmallDataRateControl + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------------|------------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| timeUnit | SmallDataRateControlTimeUnit | M | 1 | This IE shall indicate the time unit for which the data rate control is applied. | | +| maxPacketRateUI | integer | O | 0..1 | If present, this IE shall indicate the maximum number of uplink packets allowed to be sent within the time unit.
(NOTE 1) | | +| maxPacketRateDI | integer | O | 0..1 | If present, this IE shall indicate the maximum number of downlink packets allowed to be sent within the time unit.
(NOTE 1) | | +| maxAdditionalPacketRateUI | integer | O | 0..1 | If present, this IE shall indicate the additional maximum number of uplink packets allowed to be sent within the time unit.
(NOTE 2) | | +| maxAdditionalPacketRateDI | integer | O | 0..1 | If present, this IE shall indicate the additional maximum number of downlink packets allowed to be sent within the time unit.
(NOTE 3) | | + +NOTE 1: At least one of parameters maxPacketRateUI, or maxPacketRateDI should be included. + +NOTE 2: Parameter maxAdditionalPacketRateUI should be absent if parameter maxPacketRateUI is absent. + +NOTE 3: Parameter maxAdditionalPacketRateDI should be absent if parameter maxPacketRateDI is absent. + +##### 6.1.6.2.10 Type: SmContextUpdateData + +Table 6.1.6.2.10-1: Definition of type SmContextUpdateData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------------------------------------------------------|------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| dlNiddEndPoint | Uri | O | 0..1 | When present, this IE shall contain a new URI of Individual PDU session resource (see clause 6.1.3.2 of 3GPP TS 29.542 [17]) handling downlink NIDD data delivery.

The NEF shall send downlink data to the resource identified by the new URI after the update is completed. | | +| notificationUri | Uri | O | 0..1 | When present, this IE shall contain a new URI to receive SM Context Status Notifications sent by the NEF.

The NEF shall send SM Context Status Notification to this new URI after the update is completed. | | +| smContextConfig | SmContextConfiguration | O | 0..1 | When present, this IE shall contain the configuration for the NIDD. | | +| NOTE: At least one of the attributes in the table shall be present. | | | | | | + +##### 6.1.6.2.11 Type: DeliverReqData + +Table 6.1.6.2.12-1: Definition of type DeliverReqData + +| Attribute name | Data type | P | Cardinality | Description | +|----------------|-----------------|---|-------------|----------------------------------------------------------------------------------------| +| data | RefToBinaryData | M | 1 | This IE shall contain the reference to Mobile Originated data to be delivered via NEF. | + +#### 6.1.6.3 Simple data types and enumerations + +##### 6.1.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +##### 6.1.6.3.2 Simple data types + +The simple data types defined in table 6.1.6.3.2-1 shall be supported. + +Table 6.1.6.3.2-1: Simple data types + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| | | | | + +##### 6.1.6.3.3 Enumeration: SmContextStatus + +The enumeration SmContextStatus represents status of Individual SM Context in the NEF. It shall comply with the provisions defined in table 6.1.5.3.3-1. + +**Table 6.1.6.3.3-1: Enumeration SmContextStatus** + +| Enumeration value | Description | Applicability | +|-------------------|----------------------------------------------------------------|---------------| +| "RELEASED" | Indicates that the Individual SM Context for NIDD is released. | | + +##### 6.1.6.3.4 Enumeration: SmallDataRateControlTimeUnit + +The enumeration SmallDataRateControlTimeUnit represents the allowed time unit. It shall comply with the provisions defined in table 6.1.5.3.3-1. + +**Table 6.1.6.3.4-1: Enumeration SmallDataRateControlTimeUnit** + +| Enumeration value | Description | Applicability | +|-------------------|------------------------------------------------------|---------------| +| "MINUTE" | Indicates the rate control is applied per minute. | | +| "HOUR" | Indicates the rate control is applied per hour. | | +| "DAY" | Indicates the rate control is applied per day. | | +| "WEEK" | Indicates the rate control is applied per week. | | +| "6MINUTES" | Indicates the rate control is applied per 6 minutes. | | + +##### 6.1.6.3.5 Enumeration: ReleaseCause + +The enumeration ReleaseCause represents cause for release of the SM Context in the NEF. It shall comply with the provisions defined in table 6.1.6.3.5-1. + +**Table 6.1.6.3.5-1: Enumeration ReleaseCause** + +| Enumeration value | Description | Applicability | +|------------------------|------------------------------------------------------------------------------------------|---------------| +| "PDU_SESSION_RELEASED" | Indicates the SM Context is to be released due to corresponding PDU Session is released. | | + +### 6.1.7 Error Handling + +#### 6.1.7.1 General + +For the Nnef\_SMContext API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. + +In addition, the requirements in the following clauses are applicable for the Nnef\_SMContext API. + +#### 6.1.7.2 Protocol Errors + +Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4]. No specific procedures for the Nnef\_SMContext service are specified. + +#### 6.1.7.3 Application Errors + +The application errors defined for the Nnef\_SMContext service are listed in Table 6.1.7.3-1. + +**Table 6.1.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|------------------------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| "USER_UNKNOWN" | 403 | This application error indicates that the User Identity does not exist in the NEF. | +| "NIDD_CONFIGURATION_NOT_AVAILABLE" | 403 | This application error indicates that there is no valid NIDD configuration exists for the requested SM Context in the NEF, and NIDD configuration triggered by the NEF (see clause 4.4.12.2 of 3GPP TS 29.522 [15]) is not supported or has failed. | +| "CONTEXT_NOT_FOUND" | 404 | This application error indicates that the SM Context referred by the requested resource URI does not exist in the NEF. | + +### 6.1.8 Feature negotiation + +The optional features in table 6.1.8-1 are defined for the Nnef\_SMContext API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4]. + +**Table 6.1.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | BIUMR | Binding Indication Update for Multiple Resources

This feature bit indicates whether the NF Service Consumer (i.e. SMF) and NEF supports Binding Indication Update for multiple resources and/or contexts, as specified in clauses 6.12.1 and 5.2.3.2.6 of 3GPP TS 29.500 [4]. | + +### 6.1.9 Security + +As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Nnef\_SMContext API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server. + +If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Nnef\_SMContext API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2. + +NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Nnef\_SMContext service. + +The Nnef\_SMContext API defines a single scope "nnef-smcontext" for the entire service, and it does not define any additional scopes at resource or operation level. + +### 6.1.10 HTTP redirection + +An HTTP request may be redirected to a different NEF service instance, within the same NEF or a different NEF of an NEF set, e.g. when an NEF service instance is part of an NEF (service) set or when using indirect communications (see 3GPP TS 29.500 [4]). + +An SCP that reselects a different NEF producer instance will return the NF Instance ID of the new NEF producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4]. + +If an NEF within an NEF set redirects a service request to a different NEF of the set using an 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new NEF towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +## 6.2 Nnef\_SMService Service API + +### 6.2.1 Introduction + +The Nnef\_SMService shall use the Nnef\_SMService API. + +The API URI of the Nnef\_SMService API shall be: + +**{apiRoot}** + +The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.: + +**{apiRoot}** + +with the following components: + +- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5]. +- The shall be "nnef-smbservice". +- The shall be "v1". +- The shall be set as described in clause 6.1.3. + +### 6.2.2 Usage of HTTP + +#### 6.2.2.1 General + +HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4]. + +HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4]. + +The OpenAPI [6] specification of HTTP messages and content bodies for the Nnef\_SMService API is contained in Annex A. + +#### 6.2.2.2 HTTP standard headers + +##### 6.2.2.2.1 General + +See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers. + +##### 6.2.2.2.2 Content type + +JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json". + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13]. + +Multipart messages shall also be supported (see clause 6.1.2.4) using the content type "multipart/related", comprising: + +- one JSON body part with the "application/json" content type; and +- one binary body part with 3gpp vendor specific content subtypes. + +The 3gpp vendor specific content subtypes defined in Table 6.2.2.2.2-1 shall be supported. + +**Table 6.2.2.2.2-1: 3GPP vendor specific content subtypes** + +| content subtype | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------| +| vnd.3gpp.sms | Binary encoded payload, encoding SMS payload, as specified in 3GPP TS 23.040 [20] and 3GPP TS 24.011 [21]. | +| NOTE: Using 3GPP vendor content subtypes allows to describe the nature of the opaque payload (e.g. SMS payload) without having to rely on metadata in the JSON payload. | | + +See clause 6.1.2.4 for the binary payloads supported in the binary body part of multipart messages. + +#### 6.2.2.3 HTTP custom headers + +The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported. + +#### 6.2.2.4 HTTP multipart messages + +HTTP multipart messages shall be supported, to transfer opaque SMS payload (e.g. SMS message, CP Ack, etc.), in the following service operations (and HTTP messages): + +- MoForwardSm service operation; + +HTTP multipart messages shall include one JSON body part and one binary body part comprising content of SMS payload content (see clause 6.1.6.5). + +The JSON body part shall be the "root" body part of the multipart message. It shall be encoded as the first body part of the multipart message. The "Start" parameter does not need to be included. + +The multipart message shall include a "type" parameter (see IETF RFC 2387 [18]) specifying the media type of the root body part, i.e. "application/json". + +NOTE: The "root" body part (or "root" object) is the first body part the application processes when receiving a multipart/related message, see IETF RFC 2387 [18]. The default root is the first body within the multipart/related message. The "Start" parameter indicates the root body part, e.g. when this is not the first body part in the message. + +A binary body part shall include a Content-ID header (see IETF RFC 2045 [19]), and the JSON body part shall make a reference to the binary body part using the Content-ID header field. + +Examples of multipart/related messages can be found in Annex B. + +### 6.2.3 Resources + +#### 6.2.3.1 Overview + +Figure 6.2.3.1-1 describes the resource URI structure of the Nnef\_SMSService API. + +![Diagram showing the resource URI structure of the Nnef_SMService API. The root path is {apiRoot}/nnef_smbservice/. It branches into /mo-sm-info, which then branches into /{supi}, which finally branches into /sendSMS. The /sendSMS path is shown in a dashed box.](dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg) + +{apiRoot}/nnef\_smbservice/ + +``` + +graph TD + Root["{apiRoot}/nnef_smbservice/"] --> MoSmInfo["/mo-sm-info"] + MoSmInfo --> Supi["/{supi}"] + Supi --> SendSMS["/sendSMS"] + style SendSMS stroke-dasharray: 5 5 + +``` + +Diagram showing the resource URI structure of the Nnef\_SMService API. The root path is {apiRoot}/nnef\_smbservice/. It branches into /mo-sm-info, which then branches into /{supi}, which finally branches into /sendSMS. The /sendSMS path is shown in a dashed box. + +**Figure 6.2.3.1-1: Resource URI structure of the Nnef\_SMService API** + +Table 6.2.3.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 6.2.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|---------------|------------------------------------------------------------------|---------------------------------|---------------------------| +| MoSmInfo | {apiRoot}/nnef-smbservice//mo-sm-info/{supi}/sendSMS | sendSMS (POST) | MO short message transfer | + +#### 6.2.3.2 Resource: MoSmInfo + +##### 6.2.3.2.1 Description + +This resource represents the collection of Mobile Originated Short Message Information in NEF. + +This resource is modelled with the Document resource archetype (see clause C.1 of 3GPP TS 29.501 [5]). + +##### 6.2.3.2.2 Resource Definition + +Resource URI: {apiRoot}/nnef-smcontext//sm-contexts/{supi}/sendSMS + +This resource shall support the resource URI variables defined in table 6.2.3.2.2-1. + +**Table 6.2.3.2.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|---------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 6.1.1 | +| supi | Supi | Represents the Subscription Permanent Identifier (see 3GPP TS 23.501 [2] clause 5.9.2)
pattern: See pattern of type Supi in 3GPP TS 29.571 [15] | + +##### 6.2.3.2.3 Resource Standard Methods + +No HTTP method has been defined for the Mobile Originated Short Message Information collection resource. + +##### 6.2.3.2.4 Resource Custom Operations + +###### 6.2.3.2.4.1 Overview + +**Table 6.2.3.2.4.1-1: Custom operations** + +| Operation name | Custom operation URI | Mapped HTTP method | Description | +|----------------|-----------------------------|--------------------|-----------------------------------------------------| +| sendsms | /sm-contexts/{supi}/sendsms | POST | Send MO SMS message or the related Delivery Report. | + +###### 6.2.3.2.4.2 Operation: sendsms + +###### 6.2.3.2.4.2.1 Description + +This custom operation is used for NF Service Consumers to send SMS message in uplink direction. + +###### 6.2.3.2.4.2.2 Operation Definition + +This custom operation is used to send a SMS payload to an UE's Mobile Originated Short Message Information resource in the NEF. + +This operation shall support the request data structures specified in table 6.2.3.2.4.2.2-1 and the response data structure and response codes specified in table 6.2.3.2.4.2.2-2. + +**Table 6.2.3.2.4.2.2-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|--------------------------------------------------| +| SmsData | M | 1 | Representation of the MO SMS message to be sent. | + +Table 6.2.3.2.4.2.2-2: Data structures supported by the POST Response Body on this resource + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SmsDeliveryData | M | 1 | 200 OK | This case represents the successful of sending SMS message in uplink direction, with necessary response data on the received delivery report. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. | +| ProblemDetails | O | 0..1 | 400 Bad Request | This case represents an unsuccessful delivery of SMS message.
The "cause" attribute may be used to indicate one of the following application errors:
  • - SMS_PAYLOAD_MISSING, if the expected SMS payload content is missing;
  • - SMS_PAYLOAD_ERROR, if error exists in the SMS payload content.
| +| ProblemDetails | O | 0..1 | 403 Forbidden | This case represents an unsuccessful delivery of SMS message.
The "cause" attribute may be used to indicate one of the following application errors:
  • - UNKNOWN_SERVICE_CENTRE_ADDRESS, if the SMS-SC was unknown;
  • - SERVICE_CENTRE_CONGESTION, if the SMS-SC was in congestion;
  • - USER_NOT_SERVICE_CENTER, if the user didn't belongs to the SMS-SC;
  • - FACILITY_NOT_SUPPORTED, if the facility not supported;
  • - INVALID_SME_ADDRESS, if the SME address is invalid..
| +| ProblemDetails | O | 0..1 | 504 Gateway Timeout | This case represents an unsuccessful delivery of SMS message.
The "cause" attribute may be used to indicate one of the following application errors:
  • - UNREACHABLE_SMS_SC, if the response is timeout.
| + +NOTE: The mandatory HTTP error status code for the method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. + +Table 6.2.3.2.4.2.2-3: Headers supported by the 307 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.2.3.2.4.2.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +### 6.2.4 Custom Operations without associated resources + +In this release of this specification, no custom operations without associated resources are defined. + +### 6.2.5 Notifications + +In this release of this specification, no notification procedures are defined. + +### 6.2.6 Data Model + +#### 6.2.6.1 General + +This clause specifies the application data model supported by the API. + +Table 6.2.6.1-1 specifies the data types defined for the Nnef\_SMSService service based interface protocol. + +**Table 6.2.6.1-1: Nnef\_SMSService specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|-----------|----------------|-------------|---------------| +| N/A | | | | + +Table 6.2.6.1-2 specifies data types re-used by the Nnef\_SMContext service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the N service based interface. + +**Table 6.1.6.1-2: Nnef\_SMSService re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|--------------------------------------------------------------------------------------------------------------------|---------------| +| ProblemDetails | 3GPP TS 29.571 [15] | Common Data Type used in response bodies | | +| RedirectResponse | 3GPP TS 29.571 [15] | Redirect Response | | +| Supi | 3GPP TS 29.571 [15] | Subscription Permanent Identifier | | +| RefToBinaryData | 3GPP TS 29.571 [15] | Information for indicating the binary content of SMS payload. | | +| SupportedFeatures | 3GPP TS 29.571 [15] | Supported Features | | +| SmsData | 3GPP TS 29.577 [19] | Information within request message invoking MoForwardSm service operation, for delivering MO SMS. | | +| SmsDeliveryData | 3GPP TS 29.577 [19] | Information within response message invoking MoForwardSm service operation, for delivering MO SMS Delivery Report. | | +| AppPortId | 3GPP TS 29.503 [16] | Application Port Id | | + +#### 6.2.6.2 Structured data types + +In this release of this specification, no structure to be used in resource representations is defined. + +#### 6.2.6.3 Simple data types and enumerations + +##### 6.2.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +##### 6.2.6.3.2 Simple data types + +The simple data types defined in table 6.2.6.3.2-1 shall be supported. + +**Table 6.2.6.3.2-1: Simple data types** + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| N/A | | | | + +#### 6.2.6.4 Data types describing alternative data types or combinations of data types + +None. + +#### 6.2.6.5 Binary data + +##### 6.2.6.5.1 Binary Data Types + +**Table 6.2.6.5.1-1: Binary Data Types** + +| Name | Clause defined | Content type | +|-------------------------|----------------|--------------| +| SMS Payload Information | 6.2.6.5.2 | vnd.3gpp.sms | + +##### 6.2.6.5.2 SMS Payload Information + +SMS Payload Information shall encode a SMS payload as specified in 3GPP TS 23.040 [20] and 3GPP TS 24.011 [21], using the vnd.3gpp.sms content-type. + +SMS Payload Information may encode e.g. the following content: + +- CP-DATA, CP-ACK, CP-ERROR as specified in 3GPP TS 23.040 [20] and 3GPP TS 24.011 [21]. + +### 6.2.7 Error Handling + +#### 6.2.7.1 General + +For the Nnef\_SMSService API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. + +In addition, the requirements in the following clauses are applicable for the Nnef\_SMSService API. + +#### 6.2.7.2 Protocol Errors + +No specific procedures for the Nnef\_SMSService service are specified. + +#### 6.2.7.3 Application Errors + +The application errors defined for the Nnef\_SMSService service are listed in Table 6.2.7.3-1. + +**Table 6.2.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|---------------------------|---------------------|-----------------------------------------------------------------------------------------| +| SMS_PAYLOAD_MISSING | 400 Bad Request | The expected SMS payload content is missing. | +| SMS_PAYLOAD_ERROR | 400 Bad Request | Errors exist in the format of SMS payload. | +| SERVICE_CENTRE_CONGESTION | 403 Forbidden | The delivery of the MO short message failed because SMS-SC was in congestion. | +| USER_NOT_SERVICE_CENTER | 403 Forbidden | The delivery of the short message failed because the user didn't belongs to the SMS-SC. | +| FACILITY_NOT_SUPPORTED | 403 Forbidden | The delivery of the MO short message failed because of facility not supported. | +| INVALID_SME_ADDRESS | 403 Forbidden | The delivery of the MO short message failed because the SME address is invalid. | +| UNREACHABLE_SMS_SC | 504 Gateway Timeout | The delivery of the MO short message failed because the response is timeout. | + +### 6.2.8 Feature negotiation + +The optional features in table 6.2.8-1 are defined for the Nnef\_SMService API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4]. + +**Table 6.2.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| N/A | | | + +### 6.2.9 Security + +As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Nnef\_SMService API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server. + +If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Nnef\_SMService API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2. + +NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Nnef\_SMService service. + +The Nnef\_SMService API defines a single scope "nnef-smbservice" for the entire service, and it does not define any additional scopes at resource or operation level. + +# --- Annex A (normative): OpenAPI specification + +## A.1 General + +This Annex specifies the formal definition of the Nnef\_SMContext API. It consists of OpenAPI 3.0.0 specifications in YAML format. + +This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s). + +NOTE: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository, that uses the GitLab software version control system (see 3GPP TS 29.501 [5] clause 5.3.1 and 3GPP TR 21.900 [7] clause 5B). + +## A.2 Nnef\_SMContext API + +``` + +openapi: 3.0.0 + +info: + title: Nnef_SMContext + version: 1.2.0-alpha.1 + description: | + Nnef SMContext Service. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.541 V18.0.0; 5G System; Session Management Services for Non-IP Data + Delivery (NIDD). + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.541/ + +servers: + - url: '{apiRoot}/nnef-smcontext/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501 + +security: + - {} + - oAuth2ClientCredentials: + - nnef-smcontext + +paths: + /sm-contexts: + post: + summary: Create SM Context + operationId: Create + tags: + - SM Contexts Collection (Collection) + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SmContextCreateData' + responses: + '201': + description: Success + content: + application/json: + schema: + $ref: '#/components/schemas/SmContextCreatedData' + headers: + Location: + description: > + 'Contains the URI of the newly created Individual SM Context resource, according to the +structure: + {apiRoot}/nnef-smcontext//sm-contexts/{smContextId}' + required: true + schema: + type: string + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + +``` + +``` + + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + callbacks: + StatusNotify: + '{ $request.body#/notificationUri }': + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SmContextStatusNotification' + responses: + '204': + description: No Content, Notification was successful + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +/sm-contexts/{smContextId}/release: + post: + summary: Delete SM Context + operationId: Delete + tags: + - Individual SM Context (Document) + parameters: + - name: smContextId + in: path + description: SM Context Resource ID + required: true + schema: + type: string + requestBody: + required: true + content: + +``` + +``` + + application/json: + schema: + $ref: '#/components/schemas/SmContextReleaseData' + responses: + '200': + description: OK. Resource representation is returned + content: + application/json: + schema: + $ref: '#/components/schemas/SmContextReleasedData' + '204': + description: No Content. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29571_CommonData.yaml#/components/responses/406' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +/sm-contexts/{smContextId}/update: + post: + summary: Update SM Context + operationId: Update + tags: + - Individual SM Context (Document) + parameters: + - name: smContextId + in: path + description: SM Context Resource ID + required: true + schema: + type: string + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SmContextUpdateData' + responses: + '204': + description: No Content. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '406': + +``` + +``` + + $ref: 'TS29571_CommonData.yaml#/components/responses/406' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +/sm-contexts/{smContextId}/deliver: + post: + summary: Deliver Uplink MO Data + operationId: Deliver + tags: + - Individual SM Context (Document) + parameters: + - name: smContextId + in: path + description: SM Context Resource ID + required: true + schema: + type: string + requestBody: + required: true + content: + multipart/related: # message with binary body part(s) + schema: + type: object + properties: # Request parts + jsonData: + $ref: '#/components/schemas/DeliverReqData' + binaryMoData: + type: string + format: binary + encoding: + jsonData: + contentType: application/json + binaryMoData: + contentType: application/octet-stream + headers: + Content-Id: + schema: + type: string + responses: + '204': + description: No Content. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29571_CommonData.yaml#/components/responses/406' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + +``` + +``` + + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{nrfApiRoot}/oauth2/token' + scopes: + nnef-smcontext: Access to the Nnef_SMContext API + +schemas: +# +# Structured Data Types +# + +SmContextCreateData: + description: Representation of the Individual SM context to be created. + type: object + properties: + supi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' + pduSessionId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionId' + dnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' + snssai: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai' + nefId: + type: string + description: This IE shall contain the NEF ID of the target NEF. + dlNiddEndPoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + notificationUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + niddInfo: + $ref: '#/components/schemas/NiddInformation' + rdsSupport: + type: boolean + description: | + When present, this IE shall indicate the UE capability to support RDS. + The value of this IE shall be set as following + - true UE supports RDS + - false (default) UE does not support RDS + smContextConfig: + $ref: '#/components/schemas/SmContextConfiguration' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - supi + - pduSessionId + - dnn + - snssai + - nefId + - dlNiddEndPoint + - notificationUri + +SmContextCreatedData: + description: Representation of an Individual SM context successfully created. + type: object + properties: + supi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' + pduSessionId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionId' + dnn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn' + snssai: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai' + nefId: + type: string + description: This IE shall contain the NEF ID of the target NEF. + +``` + +``` + +rdsSupport: + type: boolean + default: false + description: | + When present, this IE shall indicate the NEF capability to support RDS. + The value of this IE shall be set as following + - true NEF supports RDS + - false (default) NEF does not support RDS +extBufSupport: + type: boolean + default: false + description: | + When present, this IE shall indicate whether Extended Buffering applies or not. + The value of this IE shall be set as following + - true Extended Buffering applies + - false (default) Extended Buffering does not apply +supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' +maxPacketSize: + type: integer +required: +- supi +- pduSessionId +- dnn +- snssai +- nefId + +SmContextReleaseData: + description: Representation of the information to release the Individual SM context. + type: object + properties: + cause: + $ref: '#/components/schemas/ReleaseCause' + required: + - cause + +SmContextReleasedData: + description: Successful release of an Individual SM context with information sent to the NF +service consumer. + type: object + properties: + smallDataRateStatus: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SmallDataRateStatus' + apnRateStatus: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ApnRateStatus' + +SmContextStatusNotification: + description: Representation of the SM Context status notification. + type: object + properties: + status: + $ref: '#/components/schemas/SmContextStatus' + smContextId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + cause: + $ref: '#/components/schemas/ReleaseCause' + smallDataRateStatus: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SmallDataRateStatus' + apnRateStatus: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ApnRateStatus' + required: + - status + - smContextId + +NiddInformation: + description: Informaiton related to NIDD used for the SM Context. + type: object + properties: + extGroupId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ExternalGroupId' + gpsi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' + afId: + type: string + description: When present, this IE shall contain the AF Id used for the SM Context. + +SmContextConfiguration: + description: NIDD Configuration for the SM context. + +``` + +``` + +type: object +properties: + smalDataRateControl: + $ref: '#/components/schemas/SmallDataRateControl' + smallDataRateStatus: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SmallDataRateStatus' + servPlmnDataRateCtl: + type: integer + minimum: 10 + nullable: true + description: > + When present, this IE shall contain the maximum allowed number of + Downlink NAS Data PDUs per deci hour of the serving PLMN, as specified + in subclause 5.31.14.2 of 3GPP TS 23.501 [2]. + Minimum 10 + +SmallDataRateControl: + description: Configuration of Small Data Rate Control for the SM Context. + type: object + properties: + timeUnit: + $ref: '#/components/schemas/SmallDataRateControlTimeUnit' + maxPacketRateUl: + type: integer + maxPacketRateDl: + type: integer + maxAdditionalPacketRateUl: + type: integer + maxAdditionalPacketRateDl: + type: integer + required: + - timeUnit + +SmContextUpdateData: + description: Representation of the updates to apply to the Individual SM context. + type: object + properties: + dlNiddEndPoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + notificationUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + smContextConfig: + $ref: '#/components/schemas/SmContextConfiguration' + +DeliverReqData: + description: The data for Deliver service request, including the Mobile Originated data to be +delivered via NEF. + type: object + properties: + data: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData' + required: + - data + +# +# Simple Data Types +# + +# +# Enumeration Data Types +# + +SmContextStatus: + anyOf: + - type: string + enum: + - RELEASED + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Possible values are + - RELEASED: Indicates that the Individual SM Context for NIDD is released. + +SmallDataRateControlTimeUnit: + anyOf: + - type: string + +``` + +``` + +enum: + - MINUTE + - HOUR + - DAY + - WEEK + - 6MINUTES +- type: string +description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Possible values are + - MINUTE: Indicates the rate control is applied per minute. + - HOUR: Indicates the rate control is applied per hour. + - DAY: Indicates the rate control is applied per day. + - WEEK: Indicates the rate control is applied per week. + - 6MINUTES: Indicates the rate control is applied per 6 minutes. + +ReleaseCause: +anyOf: +- type: string +enum: + - PDU_SESSION_RELEASED +- type: string +description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + The cause to release the SM Context. Possible values are + - PDU_SESSION_RELEASED: Indicates that the Individual SM Context for NIDD is released. + +``` + +## A.3 Nnef\_SMService API + +openapi: 3.0.0 + +``` + +info: + title: Nnef_SMService + version: 1.1.0-alpha.1 + description: | + Nnef SMService Service. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.541 V18.0.0; 5G System; Session Management Services for Non-IP Data + Delivery (NIDD). + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.541/ + +servers: +- url: '{apiRoot}/nnef-smbservice/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501 + +security: +- {} +- oAuth2ClientCredentials: + - nnef-smbservice + +paths: +/sm-contexts/{supi}/sendsms: + post: + summary: Send SMS payload for a given UE + operationId: SendSMS + tags: + - Send MO SMS message and the delivery report + parameters: + - name: supi + in: path + required: true + description: Subscription Permanent Identifier (SUPI) + schema: + +``` + +``` + + type: string + requestBody: + content: + multipart/related: # message with a binary body part + schema: + type: object + properties: + jsonData: + $ref: 'TS29577_Nipsmgw_SMService.yaml#/components/schemas/SmsData' + binaryPayload: + type: string + format: binary + encoding: + jsonData: + contentType: application/json + binaryPayload: + contentType: application/vnd.3gpp.sms + headers: + Content-Id: + schema: + type: string + required: true + responses: + '200': + description: sending delivery report + content: + multipart/related: # message with a binary body part + schema: + type: object + properties: + jsonData: + $ref: 'TS29577_Nipsmgw_SMService.yaml#/components/schemas/SmsDeliveryData' + binaryPayload: + type: string + format: binary + encoding: + jsonData: + contentType: application/json + binaryPayload: + contentType: application/vnd.3gpp.sms + headers: + Content-Id: + schema: + type: string + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/504' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{nrfApiRoot}/oauth2/token' + scopes: + nnef-smcontext: Access to the Nnef_SMContext API + +``` + +``` +# schemas: +``` + +``` +# COMPLEX TYPES: +``` + +``` +# SIMPLE TYPES: +``` + +``` +# ENUMS: +``` + +# Annex B (informative): Change history + +| Change history | | | | | | | | | +|----------------|----------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2019-09 | CT4#93 | C4-193889 | | | | Initial Draft. | | 0.1.0 | +| 2019-10 | CT4#94 | C4-194527 | | | | Incorporated pCRs agreed on CT4#94, including: C4-194208, C4-194440, C4-194441, C4-194442, C4-194443. | | 0.2.0 | +| 2019-11 | CT4#95 | C4-195642 | | | | Incorporated pCRs agreed on CT4#95, including: C4-195283, C4-195284, C4-195295. | | 0.3.0 | +| 2019-12 | CT#86 | CP-193072 | | | | TS presented for information | | 1.0.0 | +| 2020-03 | CT4#96-e | C4-201265 | | | | Incorporated pCRs agreed on CT4#96-e, including: C4-200588, C4-200589, C4-200744, C4-200944, C4-200985, C4-201156. | | 1.1.0 | +| 2020-03 | CT#87e | CP-200061 | | | | Presented for approval | | 2.0.0 | +| 2020-03 | CT#87e | | | | | Approved at CT#87e | | 16.0.0 | +| 2020-06 | CT#88e | CP-201046 | 0001 | 2 | B | Add Extended Buffering | | 16.1.0 | +| 2020-06 | CT#88e | CP-201071 | 0002 | | F | Storage of YAML files in ETSI Forge | | 16.1.0 | +| 2020-06 | CT#88e | CP-201046 | 0003 | | F | Revert MO Exception Data Indication | | 16.1.0 | +| 2020-06 | CT#88e | CP-201046 | 0004 | 1 | F | Parameter supplement to Create Service | | 16.1.0 | +| 2020-06 | CT#88e | CP-201046 | 0005 | 1 | F | Parameter supplement to Delete Service | | 16.1.0 | +| 2020-06 | CT#88e | CP-201046 | 0006 | 1 | F | Parameter supplement to Status Notify Service | | 16.1.0 | +| 2020-06 | CT#88e | CP-201046 | 0008 | 1 | F | Miscellaneous Corrections | | 16.1.0 | +| 2020-06 | CT#88e | CP-201073 | 0009 | | F | 29.541 Rel-16 API version and External doc update | | 16.1.0 | +| 2020-12 | CT#90e | CP-203032 | 0010 | | F | YAML files in 3GPP Forge | | 16.2.0 | +| 2021-03 | CT#91e | CP-210037 | 0011 | 1 | F | HTTP 3xx redirection | | 16.3.0 | +| 2021-03 | CT#91e | CP-210078 | 0012 | | F | 29.541 Rel-16 API version and External doc update | | 16.3.0 | +| 2021-06 | CT#92e | CP-210055 | 0013 | 1 | F | Resolving Warning in Nnef_SMContext API | | 17.0.0 | +| 2021-06 | CT#92e | CP-210051 | 0014 | | F | OpenAPI Reference | | 17.0.0 | +| 2021-06 | CT#92e | CP-210059 | 0016 | 1 | F | Redirect Response | | 17.0.0 | +| 2021-06 | CT#92e | CP-210050 | 0017 | | F | 29.541 Rel-17 API version and External doc update | | 17.0.0 | +| 2021-09 | CT#93e | CP-212060 | 0020 | - | A | 3xx description correction for SCP | | 17.1.0 | +| 2022-03 | CT#95e | CP-220023 | 0023 | - | B | Update Binding Indication for Multiple Resources | | 17.2.0 | +| 2022-06 | CT#96 | CP-221045 | 0026 | | F | Description Fields | | 17.3.0 | +| 2022-06 | CT#96 | CP-221051 | 0027 | | F | 29.541 Rel-17 API version and External doc update | | 17.3.0 | +| 2022-09 | CT#97 | CP-222201 | 0028 | 1 | B | Nnef_SMService_MoForwardSm service API | | 17.4.0 | +| 2022-09 | CT#97 | CP-222027 | 0029 | 1 | B | Nnef_SMService_MoForwardSm service operation | | 17.4.0 | +| 2022-09 | CT#97 | CP-222027 | 0030 | 1 | F | Update Reference Model | | 17.4.0 | +| 2022-12 | CT#98 | CP-223028 | 0032 | 1 | F | Missing Mandatory Status Codes in OpenAPI | | 18.0.0 | +| 2022-12 | CT#98 | CP-223033 | 0033 | | F | 29.541 Rel-18 API version and External doc update | | 18.0.0 | +| 2023-06 | CT#100 | CP-231028 | 0034 | 4 | F | Location header description | | 18.1.0 | +| 2023-12 | CT#102 | CP-233027 | 0037 | | F | Add clause 6.1.4 | | 18.2.0 | +| 2023-12 | CT#102 | CP-233029 | 0038 | 1 | F | HTTP RFCs obsoleted by IETF RFC 9110, 9111 and 9113 | | 18.2.0 | +| 2023-12 | CT#102 | CP-233029 | 0039 | | F | ProblemDetails RFC 7807 obsoleted by 9457 | | 18.2.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29577/raw.md b/marked/Rel-18/29_series/29577/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8e9abaaa7c42affc2561e21eb5777166441fc5c4 --- /dev/null +++ b/marked/Rel-18/29_series/29577/raw.md @@ -0,0 +1,2062 @@ + + +# 3GPP TS 29.577 V18.2.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; IP Short Message Gateway and SMS Router For Short Message Services; Stage 3 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis + +Valbonne - FRANCE + +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 9 | +| 4 Overview..... | 9 | +| 4.1 Introduction ..... | 9 | +| 5 Services offered by the IP-SM-GW and SMS Router ..... | 10 | +| 5.1 Introduction ..... | 10 | +| 5.2 Nipsmgw_SMService Service..... | 10 | +| 5.2.1 Service Description ..... | 10 | +| 5.2.2 Service Operations..... | 11 | +| 5.2.2.1 Introduction..... | 11 | +| 5.2.2.2 RoutingInfo..... | 11 | +| 5.2.2.2.1 General ..... | 11 | +| 5.2.2.3 MtForwardSm..... | 12 | +| 5.2.2.3.1 General ..... | 12 | +| 5.3 Nrouter_SMService Service..... | 12 | +| 5.3.1 Service Description ..... | 12 | +| 5.3.2 Service Operations..... | 13 | +| 5.3.2.1 Introduction..... | 13 | +| 5.3.2.2 RoutingInfo..... | 13 | +| 5.3.2.2.1 General ..... | 13 | +| 5.3.2.3 MtForwardSm..... | 14 | +| 5.3.2.3.1 General ..... | 14 | +| 6 API Definitions ..... | 14 | +| 6.1 Nipsmgw_SMService Service API ..... | 14 | +| 6.1.1 Introduction ..... | 14 | +| 6.1.2 Usage of HTTP..... | 15 | +| 6.1.2.1 General..... | 15 | +| 6.1.2.2 HTTP standard headers..... | 15 | +| 6.1.2.2.1 General ..... | 15 | +| 6.1.2.2.2 Content type ..... | 15 | +| 6.1.2.3 HTTP custom headers..... | 16 | +| 6.1.2.4 HTTP multipart messages..... | 16 | +| 6.1.3 Resources..... | 16 | +| 6.1.3.1 Overview..... | 16 | +| 6.1.3.2 Resource: MtSmInfos (Collection)..... | 17 | +| 6.1.3.2.1 Description ..... | 17 | +| 6.1.3.2.2 Resource Definition..... | 17 | +| 6.1.3.2.3 Resource Standard Methods..... | 17 | +| 6.1.3.3 Resource: MtSmInfo (Document) ..... | 17 | +| 6.1.3.3.1 Description ..... | 17 | +| 6.1.3.3.2 Resource Definition..... | 17 | +| 6.1.3.3.3 Resource Standard Methods..... | 18 | +| 6.1.3.3.4 Resource Custom Operations..... | 19 | +| 6.1.4 Custom Operations without associated resources ..... | 21 | +| 6.1.5 Notifications ..... | 21 | +| 6.1.6 Data Model ..... | 21 | +| 6.1.6.1 General..... | 21 | +| 6.1.6.2 Structured data types..... | 22 | +| 6.1.6.2.1 Introduction ..... | 22 | + +| | | | +|-----------|----------------------------------------------------------------------------------|----| +| 6.1.6.2.2 | Type: CreateRoutingData..... | 22 | +| 6.1.6.2.3 | Type: CreatedRoutingData..... | 23 | +| 6.1.6.2.4 | Type: SmsData..... | 23 | +| 6.1.6.2.5 | Type: SmsDeliveryData..... | 23 | +| 6.1.6.3 | Simple data types and enumerations..... | 23 | +| 6.1.6.3.1 | Introduction ..... | 23 | +| 6.1.6.3.2 | Simple data types ..... | 23 | +| 6.1.6.4 | Data types describing alternative data types or combinations of data types ..... | 24 | +| 6.1.6.5 | Binary data..... | 24 | +| 6.1.6.5.1 | Binary Data Types..... | 24 | +| 6.1.6.5.2 | SMS Payload Information..... | 24 | +| 6.1.7 | Error Handling..... | 24 | +| 6.1.7.1 | General..... | 24 | +| 6.1.7.2 | Protocol Errors..... | 24 | +| 6.1.7.3 | Application Errors..... | 24 | +| 6.1.8 | Feature negotiation ..... | 25 | +| 6.1.9 | Security..... | 25 | +| 6.1.10 | HTTP redirection..... | 25 | +| 6.2 | Nrouter_SMSService Service API ..... | 25 | +| 6.2.1 | Introduction ..... | 25 | +| 6.2.2 | Usage of HTTP..... | 26 | +| 6.2.2.1 | General..... | 26 | +| 6.2.2.2 | HTTP standard headers..... | 26 | +| 6.2.2.2.1 | General ..... | 26 | +| 6.2.2.2.2 | Content type ..... | 26 | +| 6.2.2.3 | HTTP custom headers..... | 27 | +| 6.2.2.4 | HTTP multipart messages..... | 27 | +| 6.2.3 | Resources..... | 27 | +| 6.2.3.1 | Overview..... | 27 | +| 6.2.3.2 | Resource: MtSmInfos (Store) ..... | 28 | +| 6.2.3.2.1 | Description ..... | 28 | +| 6.2.3.2.2 | Resource Definition..... | 28 | +| 6.2.3.2.3 | Resource Standard Methods..... | 28 | +| 6.2.3.3 | Resource: MtSmInfo (Document) ..... | 28 | +| 6.2.3.3.1 | Description ..... | 28 | +| 6.2.3.3.2 | Resource Definition..... | 28 | +| 6.2.3.3.3 | Resource Standard Methods..... | 29 | +| 6.2.3.3.4 | Resource Custom Operations..... | 30 | +| 6.2.4 | Custom Operations without associated resources ..... | 32 | +| 6.2.5 | Notifications ..... | 32 | +| 6.2.6 | Data Model..... | 32 | +| 6.2.6.1 | General..... | 32 | +| 6.2.6.2 | Structured data types..... | 33 | +| 6.2.6.2.1 | Introduction ..... | 33 | +| 6.2.6.2.2 | Type: CreatedRoutingData..... | 33 | +| 6.2.6.3 | Simple data types and enumerations..... | 34 | +| 6.2.6.3.1 | Introduction ..... | 34 | +| 6.2.6.3.2 | Simple data types ..... | 34 | +| 6.2.6.3.3 | Enumeration: ..... | 34 | +| 6.2.6.4 | Data types describing alternative data types or combinations of data types ..... | 34 | +| 6.2.6.5 | Binary data..... | 34 | +| 6.2.7 | Error Handling..... | 34 | +| 6.2.7.1 | General..... | 34 | +| 6.2.7.2 | Protocol Errors..... | 34 | +| 6.2.7.3 | Application Errors..... | 34 | +| 6.2.8 | Feature negotiation ..... | 35 | +| 6.2.9 | Security..... | 35 | +| 6.2.10 | HTTP redirection..... | 35 | + +| | | | +|-------------------------------|-----------------------------------------------------------|-----------| +| Annex A (normative): | OpenAPI specification ..... | 36 | +| A.1 | General ..... | 36 | +| A.2 | Nipsmgw_SMService API ..... | 36 | +| A.3 | Nrouter_SMService API ..... | 39 | +| Annex B (Informative): | HTTP Multipart Messages ..... | 42 | +| B.1 | Example of HTTP multipart message ..... | 42 | +| B.2 | Example HTTP multipart message with SMS binary data ..... | 43 | +| Annex C (informative): | Change history ..... | 44 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document specifies the stage 3 protocol and data model for the Nipsmgw and Nrouter Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the IP-SM-GW and SMS Router. + +The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. + +The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 [4] and TS 29.501 [5]. + +The Stage 2 architecture, procedures and services to support service based short message service (SMS) in 5G system (5GS) is specified in 3GPP TS 23.540 [14]. + +# --- 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 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", . +- [7] 3GPP TR 21.900: "Technical Specification Group working methods". +- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". +- [11] IETF RFC 9113: "HTTP/2". +- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [13] IETF RFC 9457: "Problem Details for HTTP APIs". +- [14] 3GPP TS 23.540: "5G System; Technical realization of Service Based Short Message Service; Stage 2". +- [15] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [16] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [17] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". + +- [18] IETF RFC 2387: "The MIME Multipart/Related Content-type". +- [19] IETF RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Gateway MSC For Short Message Service (SMS-GMSC):** function of an MSC capable of receiving a short message from an SC, interrogating an HLR/HSS/UDM for routing information and SMS info, and delivering the short message to the VMSC/SGSN/MME/SMSF of the recipient MS/UE. + +**IP-Short-Message-Gateway (IP-SM-GW):** function responsible for protocol interworking between the IP-based UE and the SC. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|----------|---------------------------------| +| IP-SM-GW | IP Short Message Gateway | +| SM MO | Short Message Mobile Originated | +| SM MT | Short Message Mobile Terminated | +| SMSF | Short Message Service Function | + +# 4 Overview + +## 4.1 Introduction + +Within the 5GC, the IP-SM-GW offers services to the UDM or SMS-GMSC via the Nipsmgw service based interface, the SMS Router offers services to the UDM or SMS-GMSC via the Nrouter service based interface (see 3GPP TS 23.540 [14], 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]). + +Figure 4.1-1 and Figure 4.1-2 provide the reference model (in service based interface representation and in reference point representation), with focus on the IP-SM-GW and SMS Router and the scope of the present specification. + +![Reference model diagram showing UDM and SMS-GMSC connected to IP-SM-GW via Nipsmgw interface with SM3 and SM8 service based interfaces.](a92b1fdf37a74b707e9f03087c8f1377_img.jpg) + +``` + +graph LR + UDM[UDM] -- SM3 --> Nipsmgw((Nipsmgw)) + SMS-GMSC[SMS-GMSC] -- SM8 --> Nipsmgw + Nipsmgw --- IP-SM-GW[IP-SM-GW] + +``` + +The diagram illustrates the reference model for the IP-SM-GW. On the left, two light green rectangular boxes represent the UDM (User Data Management) and the SMS-GMSC (SMS Gateway MSC). Lines from these boxes converge to a central circular interface labeled 'Nipsmgw'. Above the convergence point, the label 'SM3' is associated with the UDM path, and 'SM8' is associated with the SMS-GMSC path. To the right of the 'Nipsmgw' interface, a large light green rectangular box represents the IP-SM-GW (IP Short Message Gateway), which is connected to the interface. + +Reference model diagram showing UDM and SMS-GMSC connected to IP-SM-GW via Nipsmgw interface with SM3 and SM8 service based interfaces. + +Figure 4.1-1: Reference model – IP-SM-GW + +![Figure 4.1-2: Reference model – SMS Router. The diagram shows two green rectangular boxes on the left, labeled 'UDM' and 'SMS-GMSC'. Lines from each box converge to a central point labeled 'Nrouter'. From 'Nrouter', a line connects to a larger green rectangular box on the right labeled 'SMS Router'. The line from UDM to Nrouter is labeled 'SM4', and the line from SMS-GMSC to Nrouter is labeled 'SM6'.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 4.1-2: Reference model – SMS Router. The diagram shows two green rectangular boxes on the left, labeled 'UDM' and 'SMS-GMSC'. Lines from each box converge to a central point labeled 'Nrouter'. From 'Nrouter', a line connects to a larger green rectangular box on the right labeled 'SMS Router'. The line from UDM to Nrouter is labeled 'SM4', and the line from SMS-GMSC to Nrouter is labeled 'SM6'. + +Figure 4.1-2: Reference model – SMS Router + +The functionalities supported by the IP-SM-GW and SMS Router are listed in 3GPP TS 23.540 [14]. + +# 5 Services offered by the IP-SM-GW and SMS Router + +## 5.1 Introduction + +The IP-SM-GW offers to other NFs the following service: + +- Nipsmgw\_SMService + +The SMS Router offers to other NFs the following service: + +- Nrouter\_SMService + +The Nipsmgw\_SMService service and Nrouter\_SMService service are specified in 3GPP TS 23.540 [14]. + +Table 5.1-1 summarizes the corresponding APIs defined for this specification. + +Table 5.1-1: API Descriptions + +| Service Name | Clause | Description | OpenAPI Specification File | apiName | Annex | +|-------------------|--------|------------------------------------|--------------------------------|-------------------|-------| +| Nipsmgw_SMService | 6.1 | IP-SM-GW
SMService
Service | TS29577_Nipsmgw_SMService.yaml | nipsmgw-smservice | A.2 | +| Nrouter_SMService | 6.2 | SMS Router
SMService
Service | TS29577_Nrouter_SMService.yaml | nrouter-smservice | A.3 | + +## 5.2 Nipsmgw\_SMService Service + +### 5.2.1 Service Description + +The Nipsmgw\_SMService service provides SBI-based MT SM transmit through IP-SM-GW. The IP-SM-GW is acting as NF Service Producer, while the UDM or SMS-GMSC is the NF Service Consumer. + +Following functionalities are provided by the Nipsmgw\_SMService service: + +- Provide Routing Information; +- Transmit downlink SMS message. + +The Nipsmgw\_SMService service supports the following service operations. + +**Table 5.2.1-1: Service operations supported by the Nipsmgw\_SMService service** + +| Service Operations | Description | Operation Semantics | Example Consumer(s) | +|--------------------|--------------------------------|---------------------|---------------------| +| RoutingInfo | Provide Routing Information. | Request/Response | UDM | +| MtForwardSm | Transmit downlink SMS message. | Request/Response | SMS-GMSC | + +### 5.2.2 Service Operations + +#### 5.2.2.1 Introduction + +See Table 5.2.1-1 for an overview of the service operations supported by the Nipsmgw\_SMService service. + +#### 5.2.2.2 RoutingInfo + +##### 5.2.2.2.1 General + +The RoutingInfo service operation shall be used to provide the SMSF Instance Id to the IP-SM-GW. + +It is used in the following procedures: + +- Successful Mobile Terminated short message transfer via IP-SM-GW (see clause 5.1.4 of 3GPP TS 23.540 [14]). +- Unsuccessful Mobile Terminated short message transfer via IP-SM-GW (see clause 5.1.6 of 3GPP TS 23.540 [14]). + +The NF Service Consumer (e.g. UDM) shall provide the SMSF Instance Id to the IP-SM-GW by using the HTTP PUT method as shown in Figure 5.2.2.2.1-1. + +![Sequence diagram showing the interaction between an NF Service Consumer and an IP-SM-GW for routing information creation. The consumer sends a PUT request to the IP-SM-GW. The IP-SM-GW responds with either a 201 Created, 200 OK, or 204 No Content, or an error response (4xx/5xx or 3xx).](536951b2bbd94325ae266d8d1363df8f_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant IP-SM-GW + Note left of NF Service Consumer: NF Service Consumer + Note right of IP-SM-GW: IP-SM-GW + NF Service Consumer->>IP-SM-GW: 1. PUT .../mt-sm-infos/{gpsi} (CreateRoutingData) + IP-SM-GW-->>NF Service Consumer: 2a. 201 Created (CreatedRoutingData) + IP-SM-GW-->>NF Service Consumer: 2b. 200 OK or 204 No Content + IP-SM-GW-->>NF Service Consumer: 2c. 4xx/5xx (ProblemDetails) or 3xx + +``` + +Sequence diagram showing the interaction between an NF Service Consumer and an IP-SM-GW for routing information creation. The consumer sends a PUT request to the IP-SM-GW. The IP-SM-GW responds with either a 201 Created, 200 OK, or 204 No Content, or an error response (4xx/5xx or 3xx). + +**Figure 5.2.2.2.1-1: Routing Information creation** + +1. The NF Service Consumer shall send a PUT request to the resource representing the UE's Mobile Terminated Short Message Information resource (i.e. .../mt-sm-infos/{gpsi}) of the IP-SM-GW to update or create the routing information for a given UE. The content of the PUT request shall contain: + +- SMSF Instance Id. + +- 2a. If the resource does not exist (there is no previous routing information stored in IP-SM-GW for that user), IP-SM-GW stores the received routing data and returns a "201 Created" response with the "Location" header containing the URI of the created resource. + +The PUT response body shall include: + +- the IP address of the IP-SM-GW (to be sent by the UDM to the SMS-GMSC); and/or +- the FQDN of the IP-SM-GW (to be sent by the UDM to the SMS-GMSC). + +- 2b. If the resource exists (there is previous routing information stored in IP-SM-GW for that user), the IP-SM-GW updates the routing data by replacing it with the received information, and responds with "200 OK" or "204 No Content". +- 2c. On failure, or redirection, one of the HTTP status code listed in Table 6.1.3.3.3.1-3 shall be returned. + +#### 5.2.2.3 MtForwardSm + +##### 5.2.2.3.1 General + +The MtForwardSm service operation shall be used to transmit downlink SMS message via IP-SM-GW. + +It is used in the following procedures: + +- Successful Mobile Terminated short message transfer via IP-SM-GW (see clause 5.1.4 of 3GPP TS 23.540 [14]). +- Unsuccessful Mobile Terminated short message transfer via IP-SM-GW (see clause 5.1.6 of 3GPP TS 23.540 [14]). + +The NF Service Consumer (e.g. SMS-GMSC) shall transmit downlink SMS message to the IP-SM-GW by using the HTTP POST method as shown in Figure 5.2.2.3.1-1. + +![Sequence diagram showing the interaction between NF Service Consumer and IP-SM-GW for transmitting a downlink SMS message. The NF Service Consumer sends a POST request to the IP-SM-GW. The IP-SM-GW responds with either a 200 OK (SmsDeliveryData) or a 4xx/5xx (ProblemDetails) or 3xx status code.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant IP-SM-GW + Note left of NF Service Consumer: 1. POST .../mt-sm-infos/sendsms (SmsData) + NF Service Consumer->>IP-SM-GW: 1. POST .../mt-sm-infos/sendsms (SmsData) + Note right of IP-SM-GW: -2a. 200 OK (SmsDeliveryData) + IP-SM-GW-->>NF Service Consumer: -2a. 200 OK (SmsDeliveryData) + Note right of IP-SM-GW: -2b. 4xx/5xx (ProblemDetails) or 3xx + IP-SM-GW-->>NF Service Consumer: -2b. 4xx/5xx (ProblemDetails) or 3xx + +``` + +Sequence diagram showing the interaction between NF Service Consumer and IP-SM-GW for transmitting a downlink SMS message. The NF Service Consumer sends a POST request to the IP-SM-GW. The IP-SM-GW responds with either a 200 OK (SmsDeliveryData) or a 4xx/5xx (ProblemDetails) or 3xx status code. + +Figure 5.2.2.3.1-1: Transmit downlink SMS message + +1. The NF Service Consumer shall send a POST request to the resource representing the UE's Mobile Terminated Short Message Information resource (i.e. .../mt-sm-s/{gpsi}/sendsms) of the IP-SM-GW. The content of the POST request shall contain the SMS message to be sent. +- 2a. On success, "200 OK" shall be returned with "SmsDeliveryData" object contains the MT SMS Delivery Report in the response body. +- 2b. On failure, or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.2.2-2 shall be returned. + +## 5.3 Nrouter\_SMService Service + +### 5.3.1 Service Description + +The Nrouter\_SMService service provides SBI-based MT SM transmit through SMS Router. The SMS Router is acting as NF Service Producer, while the UDM or SMS-GMSC is the NF Service Consumer. + +Following functionalities are provided by the Nrouter\_SMService service: + +- Provide Routing Information; +- Transmit downlink SMS message. + +The Nrouter\_SMService service supports the following service operations. + +**Table 5.3.1-1: Service operations supported by the Nrouter\_SMSService service** + +| Service Operations | Description | Operation Semantics | Example Consumer(s) | +|--------------------|--------------------------------|---------------------|---------------------| +| RoutingInfo | Provide Routing Information. | Request/Response | UDM | +| MtForwardSm | Transmit downlink SMS message. | Request/Response | SMS-GMSC | + +### 5.3.2 Service Operations + +#### 5.3.2.1 Introduction + +See Table 5.3.1-1 for an overview of the service operations supported by the Nrouter\_SMSService service. + +#### 5.3.2.2 RoutingInfo + +##### 5.3.2.2.1 General + +The RoutingInfo service operation shall be used to provide the SMSF Instance Id to the SMS Router. + +It is used in the following procedures: + +- Successful Mobile Terminated short message transfer via SMS Router (see clause 5.1.3 of 3GPP TS 23.540 [14]). +- Unsuccessful Mobile Terminated short message transfer via SMS Router (see clause 5.1.9 of 3GPP TS 23.540 [14]). + +The NF Service Consumer (e.g. UDM) shall provide the SMSF Instance Id to the SMS Router by using the HTTP PUT method as shown in Figure 5.3.2.2.1-1. + +![Sequence diagram showing the interaction between an NF Service Consumer and an SMS Router for routing information creation. The NF Service Consumer sends a PUT request to the SMS Router. The SMS Router responds with one of three possible messages: 2a. 201 Created (CreatedRoutingData), 2b. 200 OK or 204 No Content, or 2c. 4xx/5xx (ProblemDetails) or 3xx.](3376375fe7236a570fd0ee9448d9c4ee_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant SMS Router + Note left of NF Service Consumer: 1. PUT .../mt-sm-infos/{gpsi} (CreateRoutingData) + NF Service Consumer->>SMS Router: 1. PUT .../mt-sm-infos/{gpsi} (CreateRoutingData) + Note right of SMS Router: 2a. 201 Created (CreatedRoutingData) + SMS Router-->>NF Service Consumer: 2a. 201 Created (CreatedRoutingData) + Note right of SMS Router: 2b. 200 OK or 204 No Content + SMS Router-->>NF Service Consumer: 2b. 200 OK or 204 No Content + Note right of SMS Router: 2c. 4xx/5xx (ProblemDetails) or 3xx + SMS Router-->>NF Service Consumer: 2c. 4xx/5xx (ProblemDetails) or 3xx + +``` + +Sequence diagram showing the interaction between an NF Service Consumer and an SMS Router for routing information creation. The NF Service Consumer sends a PUT request to the SMS Router. The SMS Router responds with one of three possible messages: 2a. 201 Created (CreatedRoutingData), 2b. 200 OK or 204 No Content, or 2c. 4xx/5xx (ProblemDetails) or 3xx. + +**Figure 5.3.2.2.1-1: Routing Information creation** + +1. The NF Service Consumer shall send a PUT request to the resource representing the UE's Mobile Terminated Short Message Information resource (i.e. .../mt-sm-infos/{gpsi}) of the SMS Router to update or create the routing information for a given UE. The content of the PUT request shall contain: + +- SMSF Instance Id. + +- 2a. If the resource does not exist (there is no previous routing information stored in SMS Router for that user), SMS Router stores the received routing data and returns a "201 Created" response with the "Location" header containing the URI of the created resource. + +The PUT response body shall include: + +- the IP address of the SMS Router (to be sent by the UDM to the SMS-GMSC); and/or +- the FQDN of the SMS Router (to be sent by the UDM to the SMS-GMSC). + +- 2b. If the resource exists (there is previous routing information stored in SMS Router for that user), the SMS Router updates the routing data by replacing it with the received information, and responds with "200 OK" or "204 No Content". +- 2c. On failure, or redirection, one of the HTTP status code listed in Table 6.2.3.3.3.1-3 shall be returned. + +#### 5.3.2.3 MtForwardSm + +##### 5.3.2.3.1 General + +The MtForwardSm service operation shall be used to transmit downlink SMS message via SMS Router. + +It is used in the following procedures: + +- Successful Mobile Terminated short message transfer via SMS Router (see clause 5.1.3 of 3GPP TS 23.540 [14]). +- Unsuccessful Mobile Terminated short message transfer via SMS Router (see clause 5.1.9 of 3GPP TS 23.540 [14]). + +The NF Service Consumer (e.g. SMS-GMSC) shall transmit downlink SMS message to the SMS Router by using the HTTP POST method as shown in Figure 5.3.2.3.1-1. + +![Sequence diagram showing the interaction between NF Service Consumer and SMS Router for transmitting a downlink SMS message. The NF Service Consumer sends a POST request to the SMS Router. The SMS Router responds with either a 200 OK (SmsDeliveryData) or a 4xx/5xx (ProblemDetails) or 3xx status code.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant SMS Router + Note left of NF Service Consumer: 1. POST .../mt-sm-infos/sendsms (SmsData) + NF Service Consumer->>SMS Router: 1. POST .../mt-sm-infos/sendsms (SmsData) + Note right of SMS Router: 2a. 200 OK (SmsDeliveryData) + SMS Router-->>NF Service Consumer: 2a. 200 OK (SmsDeliveryData) + Note right of SMS Router: 2b. 4xx/5xx (ProblemDetails) or 3xx + SMS Router-->>NF Service Consumer: 2b. 4xx/5xx (ProblemDetails) or 3xx + +``` + +Sequence diagram showing the interaction between NF Service Consumer and SMS Router for transmitting a downlink SMS message. The NF Service Consumer sends a POST request to the SMS Router. The SMS Router responds with either a 200 OK (SmsDeliveryData) or a 4xx/5xx (ProblemDetails) or 3xx status code. + +Figure 5.3.2.3.1-1: Transmit downlink SMS message + +1. The NF Service Consumer shall send a POST request to the resource representing the UE's Mobile Terminated Short Message Information resource (i.e. .../mt-sm-s/{gpsi}/sendsms) of the SMS Router. The content of the POST request shall contain the SMS message to be sent. +- 2a. On success, "200 OK" shall be returned with "SmsDeliveryData" object contains the MT SMS Delivery Report in the response body. +- 2b. On failure, or redirection, one of the HTTP status code listed in Table 6.2.3.3.4.2.2-2 shall be returned. + +# 6 API Definitions + +## 6.1 Nipsmgw\_SMService Service API + +### 6.1.1 Introduction + +The Nipsmgw\_SMService shall use the Nipsmgw\_SMService API. + +The API URI of the Nipsmgw\_SMService API shall be: + +{apiRoot}// + +The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.: + +**{apiRoot}** + +with the following components: + +- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5]. +- The shall be "nipsmgw-smsservice". +- The shall be "v1". +- The shall be set as described in clause 6.1.3. + +### 6.1.2 Usage of HTTP + +#### 6.1.2.1 General + +HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4]. + +HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4]. + +The OpenAPI [6] specification of HTTP messages and content bodies for the Nipsmgw\_SMSService API is contained in Annex A. + +#### 6.1.2.2 HTTP standard headers + +##### 6.1.2.2.1 General + +See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers. + +##### 6.1.2.2.2 Content type + +JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json". + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13]. + +Multipart messages shall also be supported (see clause 6.1.2.4) using the content type "multipart/related", comprising: + +- one JSON body part with the "application/json" content type; and +- one binary body part with 3gpp vendor specific content subtypes. + +The 3gpp vendor specific content subtypes defined in Table 6.1.2.2.2-1 shall be supported. + +**Table 6.1.2.2.2-1: 3GPP vendor specific content subtypes** + +| content subtype | Description | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| vnd.3gpp.sms | Binary encoded payload, encoding SMS payload, as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [17]. | +| NOTE: | Using 3GPP vendor content subtypes allows to describe the nature of the opaque payload (e.g. SMS payload) without having to rely on metadata in the JSON payload. | + +See clause 6.1.2.4 for the binary payloads supported in the binary body part of multipart messages. + +#### 6.1.2.3 HTTP custom headers + +The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported. + +#### 6.1.2.4 HTTP multipart messages + +HTTP multipart messages shall be supported, to transfer opaque SMS payload (e.g. SMS message, CP Ack, etc.), in the following service operations (and HTTP messages): + +- MtForwardSm service operation; + +HTTP multipart messages shall include one JSON body part and one binary body part comprising content of SMS payload content (see clause 6.1.6.5). + +The JSON body part shall be the "root" body part of the multipart message. It shall be encoded as the first body part of the multipart message. The "Start" parameter does not need to be included. + +The multipart message shall include a "type" parameter (see IETF RFC 2387 [18]) specifying the media type of the root body part, i.e. "application/json". + +NOTE: The "root" body part (or "root" object) is the first body part the application processes when receiving a multipart/related message, see IETF RFC 2387 [18]. The default root is the first body within the multipart/related message. The "Start" parameter indicates the root body part, e.g. when this is not the first body part in the message. + +A binary body part shall include a Content-ID header (see IETF RFC 2045 [19]), and the JSON body part shall make a reference to the binary body part using the Content-ID header field. + +Examples of multipart/related messages can be found in Annex B. + +### 6.1.3 Resources + +#### 6.1.3.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 6.1.3.1-1 depicts the resource URIs structure for the Nipsmgw\_SMSService API. + +![Diagram showing the resource URI structure for the Nipsmgw_SMSService API. The root URI is {apiRoot}/nipsmgw_smsservice/. It branches to /mt-sm-infos, which then branches to /{gpsf}, which finally branches to /sendsms. The /sendsms box is dashed.](edfd3978d7afc47a1ddaddcc9775ffff_img.jpg) + +``` + +graph TD + Root["{apiRoot}/nipsmgw_smsservice/"] --> MtSmInfos["/mt-sm-infos"] + MtSmInfos --> Gpsf["/{gpsf}"] + Gpsf --> Sendsms["/sendsms"] + style Sendsms stroke-dasharray: 5 5 + +``` + +Diagram showing the resource URI structure for the Nipsmgw\_SMSService API. The root URI is {apiRoot}/nipsmgw\_smsservice/. It branches to /mt-sm-infos, which then branches to /{gpsf}, which finally branches to /sendsms. The /sendsms box is dashed. + +**Figure 6.1.3.1-1: Resource URI structure of the Nipsmgw\_SMSService API** + +Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods. + +Table 6.1.3.1-1: Resources and methods overview + +| Resource purpose/name | Resource URI (relative path after API URI) | HTTP method or custom operation | Description (service operation) | +|------------------------|--------------------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| MtSmInfos (Collection) | /mt-sm-infos | | | +| MtSmInfo (Document) | /mt-sm-infos/{gpsi} | PUT | Create Routing Information for MT SMS. | +| | /mt-sm-infos/{gpsi}/sendSMS | sendSMS (POST) | It is used for the MtForwardSm service operation, to allow NF Service Consumer to send SMS payload in downlink direction. | + +#### 6.1.3.2 Resource: MtSmInfos (Collection) + +##### 6.1.3.2.1 Description + +This resource represents the collection of Mobile Terminated Short Message Information in IP-SM-GW. + +This resource is modelled with the Collection resource archetype (see clause C.2 of 3GPP TS 29.501 [5]). + +No HTTP method has been defined for this resource. + +##### 6.1.3.2.2 Resource Definition + +Resource URI: {apiRoot}/nipsmgw-smservice//mt-sm-infos + +This resource shall support the resource URI variables defined in table 6.1.3.2.2-1. + +Table 6.1.3.2.2-1: Resource URI variables for this resource + +| Name | Data type | Definition | +|---------|-----------|------------------| +| apiRoot | string | See clause 6.1.1 | + +##### 6.1.3.2.3 Resource Standard Methods + +No HTTP method has been defined for the Mobile Terminated Short Message Information collection resource. + +#### 6.1.3.3 Resource: MtSmInfo (Document) + +##### 6.1.3.3.1 Description + +This resource represents an individual Mobile Terminated Short Message Information in IP-SM-GW. + +This resource is modelled with the Document resource archetype (see clause C.1 of 3GPP TS 29.501 [5]). + +##### 6.1.3.3.2 Resource Definition + +Resource URI: {apiRoot}/nipsmgw-smservice//mt-sm-infos/{gpsi} + +This resource shall support the resource URI variables defined in table 6.1.3.3.2-1. + +**Table 6.1.3.3.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|---------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 6.1.1 | +| gpsi | gpsi | Represents the Generic Public Subscription Identifier with MSISDN (see 3GPP TS 23.501 [2] clause 5.9.8)
pattern: See pattern of type Gpsi in 3GPP TS 29.571 [15] | + +##### 6.1.3.3.3 Resource Standard Methods + +###### 6.1.3.3.3.1 PUT + +This method creates an individual resource of Mobile Terminated Short Message Information in the IP-SM-GW, or updates the indicated resource of Mobile Terminated Short Message Information in the IP-SM-GW. + +This method shall support the URI query parameters specified in table 6.1.3.3.3.1-1. + +**Table 6.1.3.3.3.1-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 6.1.3.3.3.1-2 and the response data structures and response codes specified in table 6.1.3.3.3.1-3. + +**Table 6.1.3.3.3.1-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| CreateRoutingData | M | 1 | Representation of the UE's Mobile Terminated Short Message Information to be created in the IP-SM-GW, or to be updated in the IP-SM-GW. | + +**Table 6.1.3.3.3.1-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|--------------------|---|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CreatedRoutingData | M | 1 | 201 Created | This case represents the successful creation of an UE's Mobile Terminated Short Message Information.
The HTTP response shall include a "Location" HTTP header that contains the resource URI of the created resource. | +| CreatedRoutingData | M | 1 | 200 OK | Upon success, a response body containing a representation of the updated UE's Mobile Terminated Short Message Information shall be returned. | +| n/a | | | 204 No Content | Upon success, an empty response body shall be returned | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection.
(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection.
(NOTE 2) | + +NOTE 1: The mandatory HTTP error status code for the PUT method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.1.3.3.3.1-4: Headers supported by the 201 response code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/nipsmgw-smservice//mt-sm-infos/{gpsii} | + +**Table 6.1.3.3.3.1-5: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same IP-SM-GW or IP-SM-GW (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.1.3.3.3.1-6: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same IP-SM-GW or IP-SM-GW (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +##### 6.1.3.3.4 Resource Custom Operations + +##### 6.1.3.3.4.1 Overview + +**Table 6.1.3.3.4.1-1: Custom operations** + +| Operation name | Custom operation URI | Mapped HTTP method | Description | +|----------------|------------------------------|--------------------|-----------------------------------------------------| +| sendsms | /mt-sm-infos/{gpsii}/sendsms | POST | Send MT SMS message or the related Delivery Report. | + +###### 6.1.3.3.4.2 Operation: sendsms + +###### 6.1.3.3.4.2.1 Description + +This custom operation is used for NF Service Consumers to send SMS message in downlink direction. + +###### 6.1.3.3.4.2.2 Operation Definition + +This custom operation is used to send a SMS payload to an UE's Mobile Terminated Short Message Information resource in the IP-SM-GW. + +This operation shall support the request data structures specified in table 6.1.3.3.4.2.2-1 and the response data structure and response codes specified in table 6.1.3.3.4.2.2-2. + +Table 6.1.3.3.4.2.2-1: Data structures supported by the POST Request Body on this resource + +| Data type | P | Cardinality | Description | | +|-----------|---|-------------|--------------------------------------------------|--| +| SmsData | M | 1 | Representation of the MT SMS message to be sent. | | + +Table 6.1.3.3.4.2.2-2: Data structures supported by the POST Response Body on this resource + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SmsDeliveryData | M | 1 | 200 OK | This case represents the successful of sending SMS message in downlink direction, with necessary response data on the received delivery report. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection. (NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection. (NOTE 2) | +| ProblemDetails | O | 0..1 | 400 Bad Request | This case represents an unsuccessful delivery of SMS message.
The "cause" attribute may be used to indicate one of the following application errors:
  • - SMS_PAYLOAD_MISSING, if the expected SMS payload content is missing;
  • - SMS_PAYLOAD_ERROR, if error exists in the SMS payload content.
| +| ProblemDetails | O | 0..1 | 404 Not Found | This case represents an unsuccessful delivery of SMS payload.
The "cause" attribute may be used to indicate one of the following application errors:
  • - ROUTING_INFO_NOT_FOUND, if the routing information for SMS to be operated is invalid or not found in IP-SM-GW.
  • - USER_NOT_FOUND, if the UE identified by the GPSI is not found in the IP-SM-GW.
| + +NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. + +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +Table 6.1.3.3.4.2.2-3: Headers supported by the 307 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same IP-SM-GW or IP-SM-GW (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.1.3.3.4.2.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same IP-SM-GW or IP-SM-GW (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +### 6.1.4 Custom Operations without associated resources + +In this release of this specification, no custom operations without associated resources are defined. + +### 6.1.5 Notifications + +In this release of this specification, no notification procedures are defined. + +### 6.1.6 Data Model + +#### 6.1.6.1 General + +This clause specifies the application data model supported by the API. + +Table 6.1.6.1-1 specifies the data types defined for the Nipsmgw\_SMService service based interface protocol. + +**Table 6.1.6.1-1: Nipsmgw\_SMService specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|--------------------|----------------|--------------------------------------------------------------------------------------------------------------------|---------------| +| CreateRoutingData | 6.1.6.2.2 | Information used for creating or updating the routing information of the user. | | +| CreatedRoutingData | 6.1.6.2.3 | Information used for receiving the MT SMS. | | +| SmsData | 6.1.6.2.4 | Information within request message for delivering SMS. | | +| SmsDeliveryData | 6.1.6.2.5 | Information within response message invoking MtForwardSm service operation, for delivering MT SMS Delivery Report. | | + +Table 6.1.6.1-2 specifies data types re-used by the Nipsmgw\_SMService service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Nipsmgw\_SMService service based interface. + +Table 6.1.6.1-2: Nipsmgw\_SMService re-used Data Types + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|---------------------------------------------------------------|---------------| +| ProblemDetails | 3GPP TS 29.571 [15] | Common Data Type used in response bodies | | +| RedirectResponse | 3GPP TS 29.571 [15] | Redirect Response | | +| Gpsi | 3GPP TS 29.571 [15] | General Public Subscription Identifier | | +| NfInstanceId | 3GPP TS 29.571 [15] | NF Instance ID | | +| RefToBinaryData | 3GPP TS 29.571 [15] | Information for indicating the binary content of SMS payload. | | +| Ipv4Addr | 3GPP TS 29.571 [15] | IPv4 address | | +| Ipv6Addr | 3GPP TS 29.571 [15] | IPv6 address | | +| SupportedFeatures | 3GPP TS 29.571 [15] | Supported Features | | +| Fqdn | 3GPP TS 29.571 [15] | Fully Qualified Domain Name | | +| Supi | 3GPP TS 29.571 [15] | Subscription Permanent Identifier | | + +#### 6.1.6.2 Structured data types + +##### 6.1.6.2.1 Introduction + +This clause defines the structures to be used in resource representations. + +##### 6.1.6.2.2 Type: CreateRoutingData + +Table 6.1.6.2.2-1: Definition of type CreateRoutingData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|-------------------|---|-------------|--------------------------------------------------------------------------------------------------------------|---------------| +| smsfid | NfInstanceId | M | 1 | This IE shall be present, and it shall contain the NF instance ID of the SMSF to receive the downlink MT SM. | | +| supi | Supi | O | 0..1 | SUPI | | +| supportedFeatures | SupportedFeatures | C | 0..1 | This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported. | | + +##### 6.1.6.2.3 Type: CreatedRoutingData + +Table 6.1.6.2.3-1: Definition of type CreatedRoutingData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------------------------------------------------|-------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| ipsmgwIpv4 | Ipv4Addr | C | 0..1 | This IE shall be present if available. When present, this IE indicates the IPv4 address of the IP-SM-GW to receive the downlink short message. See NOTE | | +| ipsmgwIpv6 | Ipv6Addr | C | 0..1 | This IE shall be present if available. When present, this IE indicates the IPv6 address of the IP-SM-GW to receive the downlink short message. See NOTE | | +| ipsmgwFqdn | Fqdn | C | 0..1 | This IE shall be present if available. When present, this IE indicates the FQDN of the IP-SM-GW to receive the downlink short message. See NOTE | | +| correlationId | string | O | 0..1 | Correlation ID | | +| supportedFeatures | SupportedFeatures | C | 0..1 | This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported. | | +| NOTE: At least, one of IP-SM-GW addresses shall be included. | | | | | | + +##### 6.1.6.2.4 Type: SmsData + +Table 6.1.6.2.4-1: Definition of type SmsData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------|---------------| +| smsPayload | RefToBinaryData | M | 1 | This IE shall be present, and it shall contain the reference to the SMS Payload Information binary data (see clause 6.1.6.5) | | + +##### 6.1.6.2.5 Type: SmsDeliveryData + +Table 6.1.6.2.5-1: Definition of type SmsDeliveryData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------|---------------| +| smsPayload | RefToBinaryData | M | 1 | This IE shall be present, and it shall contain the reference to the SMS Payload Information binary data (see clause 6.1.6.5) | | + +#### 6.1.6.3 Simple data types and enumerations + +##### 6.1.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +##### 6.1.6.3.2 Simple data types + +The simple data types defined in table 6.1.6.3.2-1 shall be supported. + +Table 6.1.6.3.2-1: Simple data types + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| | | | | + +#### 6.1.6.4 Data types describing alternative data types or combinations of data types + +In this release of this specification, no alternative data types or combinations of data types are defined. + +#### 6.1.6.5 Binary data + +##### 6.1.6.5.1 Binary Data Types + +Table 6.1.6.5.1-1: Binary Data Types + +| Name | Clause defined | Content type | +|-------------------------|----------------|--------------| +| SMS Payload Information | 6.1.6.5.2 | vnd.3gpp.sms | + +##### 6.1.6.5.2 SMS Payload Information + +SMS Payload Information shall encode a SMS payload as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [17], using the vnd.3gpp.sms content-type. + +SMS Payload Information may encode e.g. the following content: + +- CP-DATA, CP-ACK, CP-ERROR as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [17]. + +### 6.1.7 Error Handling + +#### 6.1.7.1 General + +For the Nipsmgw\_SMService API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. + +In addition, the requirements in the following clauses are applicable for the Nipsmgw\_SMService API. + +#### 6.1.7.2 Protocol Errors + +No specific procedures for the Nipsmgw\_SMService service are specified. + +#### 6.1.7.3 Application Errors + +The application errors defined for the Nipsmgw\_SMService service are listed in Table 6.1.7.3-1. + +Table 6.1.7.3-1: Application errors + +| Application Error | HTTP status code | Description | +|------------------------|------------------|------------------------------------------------------------------------------------| +| SMS_PAYLOAD_MISSING | 400 Bad Request | The expected SMS payload content is missing. | +| SMS_PAYLOAD_ERROR | 400 Bad Request | Errors exist in the format of SMS payload. | +| USER_NOT_FOUND | 404 Not Found | The provided subscriber identifier is not found. | +| ROUTING_INFO_NOT_FOUND | 404 Not Found | The routing information for SMS to be operated is invalid or not found in IP-SM-GW | + +### 6.1.8 Feature negotiation + +The optional features in table 6.1.8-1 are defined for the Nipsmgw\_SMService API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4]. + +**Table 6.1.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| | | | + +### 6.1.9 Security + +As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Nipsmgw\_SMService API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server. + +If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Nipsmgw\_SMService API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2. + +NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Nipsmgw\_SMService service. + +The Nipsmgw\_SMService API defines the following scopes for OAuth2 authorization as specified in 3GPP TS 33.501 [8]: + +**Table 6.1.9-1: OAuth2 scopes defined in Nipsmgw\_SMService API** + +| Scope | Description | +|--------------------------------------|--------------------------------------| +| "nipsmgw_smbservice" | Access to the Nipsmgw_SMService API. | +| "nipsmgw_smbservice:mtsminfos:write" | Access to write MT SM Infos | +| "nipsmgw_smbservice:sendsms:invoke" | Access to invoke Send SMS | + +### 6.1.10 HTTP redirection + +An HTTP request may be redirected to a different IP-SM-GW service instance, within the same IP-SM-GW or a different IP-SM-GW of an IP-SM-GW set, e.g. when an IP-SM-GW service instance is part of an IP-SM-GW (service) set or when using indirect communications (see 3GPP TS 29.500 [4]). + +An SCP that reselects a different IP-SM-GW producer instance will return the NF Instance ID of the new IP-SM-GW producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4]. + +If an IP-SM-GW within an IP-SM-GW set redirects a service request to a different IP-SM-GW of the set using a 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new IP-SM-GW towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +## 6.2 Nrouter\_SMService Service API + +### 6.2.1 Introduction + +The Nrouter\_SMService shall use the Nrouter\_SMService API. + +The API URI of the Nrouter\_SMService API shall be: + +{apiRoot}/{apiName}>/ + +The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.: + +**{apiRoot}** + +with the following components: + +- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5]. +- The shall be "nrouter-smsservice". +- The shall be "v1". +- The shall be set as described in clause 6.2.3. + +### 6.2.2 Usage of HTTP + +#### 6.2.2.1 General + +HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4]. + +HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4]. + +The OpenAPI [6] specification of HTTP messages and content bodies for the Nrouter\_SMSService API is contained in Annex A. + +#### 6.2.2.2 HTTP standard headers + +##### 6.2.2.2.1 General + +See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers. + +##### 6.2.2.2.2 Content type + +JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json". + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13]. + +Multipart messages shall also be supported (see clause 6.2.2.4) using the content type "multipart/related", comprising: + +- one JSON body part with the "application/json" content type; and +- one binary body part with 3gpp vendor specific content subtypes. + +The 3gpp vendor specific content subtypes defined in Table 6.2.2.2.2-1 shall be supported. + +**Table 6.2.2.2.2-1: 3GPP vendor specific content subtypes** + +| content subtype | Description | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| vnd.3gpp.sms | Binary encoded payload, encoding SMS payload, as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [17]. | +| NOTE: | Using 3GPP vendor content subtypes allows to describe the nature of the opaque payload (e.g. SMS payload) without having to rely on metadata in the JSON payload. | + +See clause 6.2.2.4 for the binary payloads supported in the binary body part of multipart messages. + +#### 6.2.2.3 HTTP custom headers + +The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported. + +#### 6.2.2.4 HTTP multipart messages + +HTTP multipart messages shall be supported, to transfer opaque SMS payload (e.g. SMS message, CP Ack, etc.), in the following service operations (and HTTP messages): + +- MtForwardSm service operation; + +HTTP multipart messages shall include one JSON body part and one binary body part comprising content of SMS payload content (see clause 6.2.6.4). + +The JSON body part shall be the "root" body part of the multipart message. It shall be encoded as the first body part of the multipart message. The "Start" parameter does not need to be included. + +The multipart message shall include a "type" parameter (see IETF RFC 2387 [18]) specifying the media type of the root body part, i.e. "application/json". + +NOTE: The "root" body part (or "root" object) is the first body part the application processes when receiving a multipart/related message, see IETF RFC 2387 [18]. The default root is the first body within the multipart/related message. The "Start" parameter indicates the root body part, e.g. when this is not the first body part in the message. + +A binary body part shall include a Content-ID header (see IETF RFC 2045 [19]), and the JSON body part shall make a reference to the binary body part using the Content-ID header field. + +Examples of multipart/related messages can be found in Annex B. + +### 6.2.3 Resources + +#### 6.2.3.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 6.2.3.1-1 depicts the resource URIs structure for the Nrouter\_SMSService API. + +![Figure 6.2.3.1-1: Resource URI structure of the Nrouter_SMSService API. The diagram shows a hierarchical tree structure of URIs. The root is {apiRoot}/nrouter_smservice/. It branches to /mt-sm-infos, which branches to /{gps}, which branches to /sendsms. The /sendsms box is dashed.](198bf4ee62f460036c189eafb90474e5_img.jpg) + +``` + +graph TD + Root["{apiRoot}/nrouter_smservice/"] --> mt_sm_infos["/mt-sm-infos"] + mt_sm_infos --> gps["/{gps}"] + gps --> sendsms["/sendsms"] + style sendsms stroke-dasharray: 5 5 + +``` + +Figure 6.2.3.1-1: Resource URI structure of the Nrouter\_SMSService API. The diagram shows a hierarchical tree structure of URIs. The root is {apiRoot}/nrouter\_smservice/. It branches to /mt-sm-infos, which branches to /{gps}, which branches to /sendsms. The /sendsms box is dashed. + +**Figure 6.2.3.1-1: Resource URI structure of the Nrouter\_SMSService API** + +Table 6.2.3.1-1 provides an overview of the resources and applicable HTTP methods. + +Table 6.2.3.1-1: Resources and methods overview + +| Resource purpose/name | Resource URI (relative path after API URI) | HTTP method or custom operation | Description (service operation) | +|-----------------------|--------------------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| MtSmInfo (Document) | /mt-sm-infos/{gpsi} | PUT | Create Routing Information for MT SMS. | +| | /mt-sm-infos/{gpsi}/sendsms | sendsms (POST) | It is used for the MtForwardSm service operation, to allow NF Service Consumer to send SMS payload in downlink direction. | + +#### 6.2.3.2 Resource: MtSmInfos (Store) + +##### 6.2.3.2.1 Description + +This resource represents the collection of Mobile Terminated Short Message Information in SMS Router. + +This resource is modelled with the Store resource archetype (see clause C.3 of 3GPP TS 29.501 [5]). + +No HTTP method has been defined for this resource. + +##### 6.2.3.2.2 Resource Definition + +Resource URI: {apiRoot}/nrouter-smservice//mt-sm-infos + +This resource shall support the resource URI variables defined in table 6.2.3.2.2-1. + +Table 6.2.3.2.2-1: Resource URI variables for this resource + +| Name | Data type | Definition | +|---------|-----------|------------------| +| apiRoot | string | See clause 6.2.1 | + +##### 6.2.3.2.3 Resource Standard Methods + +No HTTP method has been defined for the Mobile Terminated Short Message Information collection resource. + +#### 6.2.3.3 Resource: MtSmInfo (Document) + +##### 6.2.3.3.1 Description + +This resource represents an individual Mobile Terminated Short Message Information in SMS Router. + +This resource is modelled with the Document resource archetype (see clause C.1 of 3GPP TS 29.501 [5]). + +##### 6.2.3.3.2 Resource Definition + +Resource URI: {apiRoot}/nrouter-smservice//mt-sm-infos/{gpsi} + +This resource shall support the resource URI variables defined in table 6.2.3.3.2-1. + +**Table 6.2.3.3.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|---------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 6.2.1 | +| gpsi | gpsi | Represents the Generic Public Subscription Identifier with MSISDN (see 3GPP TS 23.501 [2] clause 5.9.8)
pattern: See pattern of type Gpsi in 3GPP TS 29.571 [15] | + +##### 6.2.3.3.3 Resource Standard Methods + +###### 6.2.3.3.3.1 PUT + +This method creates an individual resource of Mobile Terminated Short Message Information in the SMS Router, or updates the indicated resource of Mobile Terminated Short Message Information in the SMS Router. + +This method shall support the URI query parameters specified in table 6.2.3.3.3.1-1. + +**Table 6.2.3.3.3.1-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 6.2.3.3.3.1-2 and the response data structures and response codes specified in table 6.2.3.3.3.1-3. + +**Table 6.2.3.3.3.1-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| CreateRoutingData | M | 1 | Representation of the UE's Mobile Terminated Short Message Information to be created in the SMS Router, or to be updated in the SMS Router. | + +**Table 6.2.3.3.3.1-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|--------------------|---|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CreatedRoutingData | M | 1 | 201 Created | This case represents the successful creation of an UE's Mobile Terminated Short Message Information.
The HTTP response shall include a "Location" HTTP header that contains the resource URI of the created resource. | +| CreatedRoutingData | M | 1 | 200 OK | Upon success, a response body containing a representation of the updated UE's Mobile Terminated Short Message Information shall be returned. | +| n/a | | | 204 No Content | Upon success, an empty response body shall be returned | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection.
(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection.
(NOTE 2) | + +NOTE 1: The mandatory HTTP error status code for the PUT method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.2.3.3.3.1-4: Headers supported by the 201 response code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/nrouter-smservice//mt-sm-infos/{gpsii} | + +**Table 6.2.3.3.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same SMS Router or SMS Router (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.2.3.3.3.1-6: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same SMS Router or SMS Router (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +##### 6.2.3.3.4 Resource Custom Operations + +###### 6.2.3.3.4.1 Overview + +**Table 6.2.3.3.4.1-1: Custom operations** + +| Operation name | Custom operation URI | Mapped HTTP method | Description | +|----------------|------------------------------|--------------------|-----------------------------------------------------| +| sendsms | /mt-sm-infos/{gpsii}/sendsms | POST | Send MT SMS message or the related Delivery Report. | + +###### 6.2.3.3.4.2 Operation: sendsms + +###### 6.2.3.3.4.2.1 Description + +This custom operation is used for NF Service Consumers to send SMS message in downlink direction. + +###### 6.2.3.3.4.2.2 Operation Definition + +This custom operation is used to send a SMS payload to an UE's Mobile Terminated Short Message Information resource in the SMS Router. + +This operation shall support the request data structures specified in table 6.2.3.3.4.2.2-1 and the response data structure and response codes specified in table 6.2.3.3.4.2.2-2. + +Table 6.2.3.3.4.2.2-1: Data structures supported by the POST Request Body on this resource + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|--------------------------------------------------| +| SmsData | M | 1 | Representation of the MT SMS message to be sent. | + +Table 6.2.3.3.4.2.2-2: Data structures supported by the POST Response Body on this resource + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SmsDeliveryData | M | 1 | 200 OK | This case represents the successful of sending SMS message in downlink direction, with necessary response data on the received delivery report. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection. (NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection. (NOTE 2) | +| ProblemDetails | O | 0..1 | 400 Bad Request | This case represents an unsuccessful delivery of SMS message.
The "cause" attribute may be used to indicate one of the following application errors:
  • - SMS_PAYLOAD_MISSING, if the expected SMS payload content is missing;
  • - SMS_PAYLOAD_ERROR, if error exists in the SMS payload content.
| +| ProblemDetails | O | 0..1 | 404 Not Found | This case represents an unsuccessful delivery of SMS payload.
The "cause" attribute may be used to indicate one of the following application errors:
  • - ROUTING_INFO_NOT_FOUND, if the routing information for SMS to be operated is invalid or not found in SMS Router.
  • - USER_NOT_FOUND, if the UE identified by the GPSI is not found in the SMS Router.
| + +NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. + +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +Table 6.2.3.3.4.2.2-3: Headers supported by the 307 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same SMS Router or SMS Router (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.2.3.3.4.2.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same SMS Router or SMS Router (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +### 6.2.4 Custom Operations without associated resources + +In this release of this specification, no custom operations without associated resources are defined. + +### 6.2.5 Notifications + +In this release of this specification, no notification procedures are defined. + +### 6.2.6 Data Model + +#### 6.2.6.1 General + +This clause specifies the application data model supported by the API. + +Table 6.2.6.1-1 specifies the data types defined for the Nrouter\_SMSService service based interface protocol. + +**Table 6.2.6.1-1: Nrouter\_SMSService specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|--------------------|----------------|--------------------------------------------|---------------| +| CreatedRoutingData | 6.2.6.2.2 | Information used for receiving the MT SMS. | | + +Table 6.2.6.1-2 specifies data types re-used by the Nrouter\_SMSService service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Nrouter\_SMSService service based interface. + +**Table 6.2.6.1-2: Nrouter\_SMService re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|--------------------------------------------------------------------------------------------------------------------|---------------| +| CreateRoutingData | 6.1.6.2.2 | Information used for creating or updating the routing information of the user. | | +| SmsData | 6.1.6.2.4 | Information within request message invoking MtForwardSm service operation, for delivering MT SMS. | | +| SmsDeliveryData | 6.1.6.2.5 | Information within response message invoking MtForwardSm service operation, for delivering MT SMS Delivery Report. | | +| ProblemDetails | 3GPP TS 29.571 [15] | Common Data Type used in response bodies | | +| RedirectResponse | 3GPP TS 29.571 [15] | Redirect Response | | +| Gpsi | 3GPP TS 29.571 [15] | General Public Subscription Identifier | | +| NfInstanceId | 3GPP TS 29.571 [15] | NF Instance ID | | +| RefToBinaryData | 3GPP TS 29.571 [15] | Information for indicating the binary content of SMS payload. | | +| Ipv4Addr | 3GPP TS 29.571 [15] | IPv4 address | | +| Ipv6Addr | 3GPP TS 29.571 [15] | IPv6 address | | +| SupportedFeatures | 3GPP TS 29.571 [15] | Supported Features | | +| Fqdn | 3GPP TS 29.571 [15] | Fully Qualified Domain Name | | + +#### 6.2.6.2 Structured data types + +##### 6.2.6.2.1 Introduction + +This clause defines the structures to be used in resource representations. + +##### 6.2.6.2.2 Type: CreatedRoutingData + +**Table 6.2.6.2.2-1: Definition of type CreatedRoutingData** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------------------------------------------------------|-------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| routerIpv4 | Ipv4Addr | C | 0..1 | This IE shall be present if available. When present, this IE indicates the IPv4 address of the SMS Router to receive the downlink short message. See NOTE | | +| routerIpv6 | Ipv6Addr | C | 0..1 | This IE shall be present if available. When present, this IE indicates the IPv6 address of the SMS Router to receive the downlink short message. See NOTE | | +| routerFqdn | Fqdn | C | 0..1 | This IE shall be present if available. When present, this IE indicates the FQDN of the SMS Router to receive the downlink short message. See NOTE | | +| supportedFeatures | SupportedFeatures | C | 0..1 | This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported. | | +| NOTE: At least, one of SMS Router addresses shall be included. | | | | | | + +#### 6.2.6.3 Simple data types and enumerations + +##### 6.2.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +##### 6.2.6.3.2 Simple data types + +The simple data types defined in table 6.2.6.3.2-1 shall be supported. + +**Table 6.2.6.3.2-1: Simple data types** + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| | | | | + +##### 6.2.6.3.3 Enumeration: + +The enumeration represents . It shall comply with the provisions defined in table 6.1.6.3.3-1. + +**Table 6.2.6.3.3-1: Enumeration < EnumType1>** + +| Enumeration value | Description | Applicability | +|-------------------|-------------|---------------| +| | | | + +#### 6.2.6.4 Data types describing alternative data types or combinations of data types + +In this release of this specification, no alternative data types or combinations of data types are defined. + +#### 6.2.6.5 Binary data + +See clause 6.1.6.5. + +### 6.2.7 Error Handling + +#### 6.2.7.1 General + +For the Nrouter\_SMSService API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. + +In addition, the requirements in the following clauses are applicable for the Nrouter\_SMSService API. + +#### 6.2.7.2 Protocol Errors + +No specific procedures for the Nrouter\_SMSService service are specified. + +#### 6.2.7.3 Application Errors + +The application errors defined for the Nrouter\_SMSService service are listed in Table 6.2.7.3-1. + +**Table 6.2.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|------------------------|------------------|--------------------------------------------------------------------------------------| +| SMS_PAYLOAD_MISSING | 400 Bad Request | The expected SMS payload content is missing. | +| SMS_PAYLOAD_ERROR | 400 Bad Request | Errors exist in the format of SMS payload. | +| USER_NOT_FOUND | 404 Not Found | The provided subscriber identifier is not found. | +| ROUTING_INFO_NOT_FOUND | 404 Not Found | The routing information for SMS to be operated is invalid or not found in SMS Router | + +### 6.2.8 Feature negotiation + +The optional features in table 6.2.8-1 are defined for the Nrouter\_SMService API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4]. + +**Table 6.2.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| | | | + +### 6.2.9 Security + +As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Nrouter\_SMService API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server. + +If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Nrouter\_SMService API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2. + +NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Nrouter\_SMService service. + +The Nrouter\_SMService API defines the following scopes for OAuth2 authorization as specified in 3GPP TS 33.501 [8]: + +**Table 6.2.9-1: OAuth2 scopes defined in Nrouter\_SMService API** + +| Scope | Description | +|--------------------------------------|--------------------------------------| +| "nrouter_smbservice" | Access to the Nrouter_SMService API. | +| "nrouter_smbservice:mtsminfos:write" | Access to write MT SM Infos | +| "nrouter_smbservice:sendsms:invoke" | Access to invoke Send SMS | + +### 6.2.10 HTTP redirection + +An HTTP request may be redirected to a different SMS Router service instance, within the same SMS Router or a different SMS Router of an SMS Router set, e.g. when an SMS Router service instance is part of an SMS Router (service) set or when using indirect communications (see 3GPP TS 29.500 [4]). + +An SCP that reselects a different SMS Router producer instance will return the NF Instance ID of the new SMS Router producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4]. + +If an SMS Router within an SMS Router set redirects a service request to a different SMS Router of the set using a 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new SMS Router towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +# --- Annex A (normative): OpenAPI specification + +## A.1 General + +This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format. + +This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s). + +NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5.3.1 of 3GPP TS 29.501 [5] and clause 5B of 3GPP TR 21.900 [7]). + +## --- A.2 Nipsmgw\_SMService API + +``` +openapi: 3.0.0 + +info: + version: '1.1.0-alpha.2' + title: 'Nipsmgw_SMService Service API' + description: | + IP-SM-GW SMService. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.577 V18.1.0; 5G System; IP Short Message Gateway and SMS Router For Short Message Services; Stage 3 + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.577/' + +security: + - oAuth2ClientCredentials: + - nipsmgw-smbservice + - {} + +servers: + - url: '{apiRoot}/nipsmgw-smbservice/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501. + +paths: + /mt-sm-infos/{gpsi}: + put: + summary: Create the routing information for a given UE + operationId: RoutingInfo + tags: + - Creation of Routing Info + security: + - {} + - oAuth2ClientCredentials: + - nipsmgw_smbservice + - oAuth2ClientCredentials: + - nipsmgw_smbservice + - nipsmgw_smbservice:mtsminfos:write + parameters: + - name: gpsi + in: path + required: true +``` + +``` + + description: Generic Public Subscription Identifier (GPSI) + schema: + type: string + requestBody: + content: + application/json: + schema: + $ref: '#/components/schemas/CreateRoutingData' + required: true + responses: + '201': + description: Routing Information is created in IP-SM-GW + content: + application/json: + schema: + $ref: '#/components/schemas/CreatedRoutingData' + headers: + Location: + description: > + 'Contains the URI of the newly created resource, according to the structure: + {apiRoot}/nipsmgw-smbservice//mt-sm-infos/{gpsi}' + required: true + schema: + type: string + '200': + description: Routing Information is updated in IP-SM-GW + content: + application/json: + schema: + $ref: '#/components/schemas/CreatedRoutingData' + '204': + description: Routing Information is updated in IP-SM-GW + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +/mt-sm-infos/{gpsi}/sendsms: + post: + summary: Send SMS payload for a given UE + operationId: SendSMS + tags: + - Send MT SMS message and the delivery report + security: + - {} + - oAuth2ClientCredentials: + - nipsmgw_smbservice + - oAuth2ClientCredentials: + - nipsmgw_smbservice + - nipsmgw_smbservice:sendsms:invoke + parameters: + - name: gpsi + in: path + required: true + +``` + +``` +description: Generic Public Subscription Identifier (GPSI) +schema: + type: string +requestBody: + content: + multipart/related: # message with a binary body part + schema: + type: object + properties: + jsonData: + $ref: '#/components/schemas/SmsData' + binaryPayload: + type: string + format: binary + encoding: + jsonData: + contentType: application/json + binaryPayload: + contentType: application/vnd.3gpp.sms + headers: + Content-Id: + schema: + type: string + required: true +responses: + '200': + description: sending delivery report + content: + multipart/related: # message with a binary body part + schema: + type: object + properties: + jsonData: + $ref: '#/components/schemas/SmsDeliveryData' + binaryPayload: + type: string + format: binary + encoding: + jsonData: + contentType: application/json + binaryPayload: + contentType: application/vnd.3gpp.sms + headers: + Content-Id: + schema: + type: string + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +components: + +securitySchemes: +``` + +``` + +oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{nrfApiRoot}/oauth2/token' + scopes: + nipsmgw-smbservice: Access to the nipsmgw-smbservice API + nipsmgw-smbservice:mtminfos:write: Access to write MT SM Infos + nipsmgw-smbservice:sendsms:invoke: Access to invoke Send SMS + +schemas: + +CreateRoutingData: + description: Information used for creating or updating the routing information of the user. + type: object + required: + - smsfId + properties: + smsfId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' + supi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + +CreatedRoutingData: + description: Information used for receiving the MT SMS. + type: object + properties: + ipsmgwIpv4: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' + ipsmgwIpv6: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr' + ipsmgwFqdn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Fqdn' + correlationId: + type: string + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + +SmsData: + description: Information within request message for delivering SMS. + type: object + required: + - smsPayload + properties: + smsPayload: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData' + +SmsDeliveryData: + description: > + Information within response message invoking MtForwardSm service operation, for delivering + MT SMS Delivery Report. + type: object + required: + - smsPayload + properties: + smsPayload: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData' + +``` + +## A.3 Nrouter\_SMService API + +openapi: 3.0.0 + +``` + +info: + version: '1.1.0-alpha.2' + title: 'Nrouter_SMService Service API' + description: | + SMS Router SMService. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +``` + +externalDocs: + +``` +description: 3GPP TS 29.577 V18.1.0; 5G System; IP Short Message Gateway and SMS Router For Short +Message Services; Stage 3 +url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.577/' + +security: +- oAuth2ClientCredentials: +- nrouter-smbservice +- {} + +servers: +- url: '{apiRoot}/nrouter-smbservice/v1' +variables: +apiRoot: +default: https://example.com +description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501. + +paths: +/mt-sm-infos/{gpsi}: +put: +summary: Create the routing information for a given UE +operationId: RoutingInfo +tags: +- Creation of Routing Info +security: +- {} +- oAuth2ClientCredentials: +- nrouter_smbservice +- oAuth2ClientCredentials: +- nrouter_smbservice +- nrouter_smbservice:mtsminfos:write +parameters: +- name: gpsi +in: path +required: true +description: Generic Public Subscription Identifier (GPSI) +schema: +type: string +requestBody: +content: +application/json: +schema: +$ref: 'TS29577_Nipsmgw_SMService.yaml#/components/schemas/CreateRoutingData' +required: true +responses: +'201': +description: Routing Information is created in SMS Router +content: +application/json: +schema: +$ref: '#/components/schemas/CreatedRoutingData' +headers: +Location: +description: > +'Contains the URI of the newly created resource, according to the structure: +{apiRoot}/nrouter-smbservice//mt-sm-infos/{gpsi}' +required: true +schema: +type: string +'200': +description: Routing Information is updated in SMS Router +content: +application/json: +schema: +$ref: '#/components/schemas/CreatedRoutingData' +'204': +description: Routing Information is updated in SMS Router +'307': +$ref: 'TS29571_CommonData.yaml#/components/responses/307' +'308': +$ref: 'TS29571_CommonData.yaml#/components/responses/308' +'400': +$ref: 'TS29571_CommonData.yaml#/components/responses/400' +'401': +$ref: 'TS29571_CommonData.yaml#/components/responses/401' +'403': +$ref: 'TS29571_CommonData.yaml#/components/responses/403' +'404': +$ref: 'TS29571_CommonData.yaml#/components/responses/404' +``` + +``` +'411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' +'502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' +'503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +/mt-sm-infos/{gpsi}/sendsms: + post: + summary: Send SMS payload for a given UE + operationId: SendSMS + tags: + - Send MT SMS message and the delivery report + security: + - {} + - oAuth2ClientCredentials: + - nrouter_smsservice + - oAuth2ClientCredentials: + - nrouter_smsservice + - nrouter_smsservice:sendsms:invoke + parameters: + - name: gpsi + in: path + required: true + description: Generic Public Subscription Identifier (GPSI) + schema: + type: string + requestBody: + content: + multipart/related: # message with a binary body part + schema: + type: object + properties: + jsonData: + $ref: 'TS29577_Nipsmgw_SMSService.yaml#/components/schemas/SmsData' + binaryPayload: + type: string + format: binary + encoding: + jsonData: + contentType: application/json + binaryPayload: + contentType: application/vnd.3gpp.sms + headers: + Content-Id: + schema: + type: string + required: true + responses: + '200': + description: sending delivery report + content: + multipart/related: # message with a binary body part + schema: + type: object + properties: + jsonData: + $ref: 'TS29577_Nipsmgw_SMSService.yaml#/components/schemas/SmsDeliveryData' + binaryPayload: + type: string + format: binary + encoding: + jsonData: + contentType: application/json + binaryPayload: + contentType: application/vnd.3gpp.sms + headers: + Content-Id: +``` + +``` + + schema: + type: string + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +components: + + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{nrfApiRoot}/oauth2/token' + scopes: + nrouter-smbservice: Access to the nrouter-smbservice API + nrouter-smbservice:mtminfos:write: Access to write MT SM Infos + nrouter-smbservice:sendsms:invoke: Access to invoke Send SMS + +schemas: + + CreatedRoutingData: + description: Information used for receiving the MT SMS. + type: object + properties: + routerIpv4: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' + routerIpv6: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr' + routerFqdn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Fqdn' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + +``` + +# --- Annex B (Informative): HTTP Multipart Messages + +## B.1 Example of HTTP multipart message + +This Annex provides a (partial) example of HTTP multipart message. The example does not aim to be a complete representation of the HTTP message, e.g. additional information or headers can be included. + +This Annex is informative and the normative descriptions in this specification prevail over the description in this Annex if there is any difference. + +## B.2 Example HTTP multipart message with SMS binary data + +Example HTTP multipart message with SMS binary data: + +``` +POST /example.com/nipsmgw-smsservice/v1/mt-sm-infos/{gpsi}/sendsms HTTP/2 +Content-Type: multipart/related; boundary=----Boundary +Content-Length: xyz + +-----Boundary +Content-Type: application/json + +{ + "smsPayload": { + "contentId": "sms" + }, +} +-----Boundary +Content-Type: application/vnd.3gpp.sms +Content-Id: sms + +{ ... SMS Message binary data ...} +-----Boundary +``` + +The JSON part of the HTTP POST message includes an attribute named "smsPayload" which refers to RefToBinaryData structure. The "contentId" of RefToBinaryData is encoded as a string and used to reference the value of the Content-ID header field of the binary body part. + +# Annex C (informative): Change history + +| Change history | | | | | | | | | +|----------------|----------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2022-04 | CT4#109e | C4-222401 | | | | TS skeleton | | 0.0.0 | +| 2022-04 | CT4#109e | C4-222341 | | | | Implementation of pCRs agreed at CT4#109e: C4-222279, C4-222280, C4-222283, C4-222398, C4-222399, C4-222402, C4-222403 | | 0.1.0 | +| 2022-05 | CT4#110e | C4-223450 | | | | Implementation of pCRs agreed at CT4#110e: C4-223220, C4-223222, C4-223353 | | 0.2.0 | +| 2022-06 | CT#96 | CP-221078 | | | | TS presented for information and approval | | 1.0.0 | +| 2022-06 | CT#96 | CP-221078 | | | | TS approved at CT#96 | | 17.0.0 | +| 2022-09 | CT#97e | CP-222027 | 0001 | - | F | Alignment on the service name used with template | | 17.1.0 | +| 2022-09 | CT#97e | CP-222027 | 0002 | - | F | Editorial corrections | | 17.1.0 | +| 2022-09 | CT#97e | CP-222027 | 0003 | - | F | Update on the content type for OpenAPI | | 17.1.0 | +| 2022-09 | CT#97e | CP-222058 | 0004 | - | F | 29.577 Rel-17 API version and External doc update | | 17.1.0 | +| 2022-12 | CT#98e | CP-223028 | 0005 | 1 | F | Missing Mandatory Status Codes in OpenAPI | | 18.0.0 | +| 2022-12 | CT#98e | CP-223033 | 0006 | - | F | 29.577 Rel-18 API version and External doc update | | 18.0.0 | +| 2023-06 | CT#100 | CP-231026 | 0007 | 3 | F | Location header description | | 18.1.0 | +| 2023-06 | CT#100 | CP-231026 | 0009 | - | B | OAuth2 scopes in the Nipsmgw SMService API | | 18.1.0 | +| 2023-06 | CT#100 | CP-231028 | 0010 | 1 | B | OAuth2 scopes in the Nrouter SMService API | | 18.1.0 | +| 2023-06 | CT#100 | CP-231070 | 0011 | - | F | 29.577 Rel-18 API version and External doc update | | 18.1.0 | +| 2023-12 | CT#102 | CP-233027 | 0012 | - | F | HTTP RFCs obsoleted by IETF RFC 9113 | | 18.2.0 | +| 2023-12 | CT#102 | CP-233030 | 0013 | - | F | ProblemDetails RFC 7807 obsoleted by 9457 | | 18.2.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29579/raw.md b/marked/Rel-18/29_series/29579/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..77e130946d4bf80b042d61b178700739b5eeb9d2 --- /dev/null +++ b/marked/Rel-18/29_series/29579/raw.md @@ -0,0 +1,878 @@ + + +# 3GPP TS 29.579 V18.3.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Interworking MSC For Short Message Services; Stage 3 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Overview..... | 8 | +| 4.1 Introduction ..... | 8 | +| 5 Services offered by the SMS-IWMSC..... | 8 | +| 5.1 Introduction ..... | 8 | +| 5.2 Niwmsc_SMService Service..... | 9 | +| 5.2.1 Service Description ..... | 9 | +| 5.2.2 Service Operations..... | 9 | +| 5.2.2.1 Introduction..... | 9 | +| 5.2.2.2 MoForwardSm ..... | 9 | +| 5.2.2.2.1 General ..... | 9 | +| 5.2.2.2.2 SBI-based MO SM transfer..... | 9 | +| 6 API Definitions ..... | 10 | +| 6.1 Niwmsc_SMService Service API ..... | 10 | +| 6.1.1 Introduction ..... | 10 | +| 6.1.2 Usage of HTTP..... | 10 | +| 6.1.2.1 General..... | 10 | +| 6.1.2.2 HTTP standard headers..... | 10 | +| 6.1.2.2.1 General ..... | 10 | +| 6.1.2.2.2 Content type ..... | 10 | +| 6.1.2.3 HTTP custom headers..... | 11 | +| 6.1.2.4 HTTP multipart messages..... | 11 | +| 6.1.3 Resources..... | 11 | +| 6.1.3.1 Overview..... | 11 | +| 6.1.3.2 Resource: MoSmInfo..... | 12 | +| 6.1.3.2.1 Description ..... | 12 | +| 6.1.3.2.2 Resource Definition..... | 12 | +| 6.1.3.2.3 Resource Standard Methods..... | 12 | +| 6.1.3.2.4 Resource Custom Operations..... | 13 | +| 6.1.4 Custom Operations without associated resources ..... | 15 | +| 6.1.5 Notifications ..... | 15 | +| 6.1.6 Data Model ..... | 15 | +| 6.1.6.1 General..... | 15 | +| 6.1.6.2 Structured data types..... | 15 | +| 6.1.6.3 Simple data types and enumerations..... | 16 | +| 6.1.6.3.1 Introduction ..... | 16 | +| 6.1.6.3.2 Simple data types ..... | 16 | +| 6.1.6.4 Data types describing alternative data types or combinations of data types ..... | 16 | +| 6.1.6.5 Binary data..... | 16 | +| 6.1.6.5.1 Binary Data Types..... | 16 | +| 6.1.6.5.2 SMS Payload Information..... | 16 | +| 6.1.7 Error Handling..... | 16 | +| 6.1.7.1 General..... | 16 | +| 6.1.7.2 Protocol Errors ..... | 16 | +| 6.1.7.3 Application Errors..... | 16 | +| 6.1.8 Feature negotiation ..... | 17 | +| 6.1.9 Security..... | 17 | +| 6.1.10 HTTP redirection..... | 17 | + +**Annex A (normative): OpenAPI specification ..... 18** +A.1 General..... 18 +A.2 Niwmsc\_SMService API..... 18 +**Annex B (informative): Withdrawn API versions ..... 20** +B.1 General..... 20 +B.2 Niwmsc\_SMService API..... 20 +**Annex C (informative): Change history..... 21** + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document specifies the stage 3 protocol and data model for the Niwmsc Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SMS-IWMSC. + +The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. + +The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. + +Stage 2 requirements for the Niwmsc services are specified in 3GPP TS 23.540 [14]. + +# 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 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", . +- [7] 3GPP TR 21.900: "Technical Specification Group working methods". +- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". +- [11] IETF RFC 9113: "HTTP/2". +- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [13] IETF RFC 9457: "Problem Details for HTTP APIs". +- [14] 3GPP TS 23.540: "Technical realization of Service Based Short Message Service; Stage 2". +- [15] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3". +- [16] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [17] 3GPP TS 29.577: "5G System; IP Short Message Gateway and SMS Router For Short Message Service; Stage 3". +- [18] 3GPP TS 24.011: " Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Niwmsc:** Service-based interface exhibited by the SMS-IWMSC + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|---------------------------------| +| SM MO | Short Message Mobile Originated | +|-------|---------------------------------| + +# 4 Overview + +## 4.1 Introduction + +The SMS-IWMSC offers services to the SMSF via the Niwmsc service based interface (see 3GPP TS 23.501 [2], 3GPP TS 23.502 [3], and 3GPP TS 23.540 [14]). + +Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the SMS-IWMSC. + +![Reference model diagram showing SMSF connected to SMS-IWMSC via SM10 interface and Niwmsc service-based interface.](18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg) + +The diagram illustrates the reference model for the SMS-IWMSC. On the left, a white rectangular box is labeled 'SMSF'. A horizontal line, representing the SM10 interface, connects this box to a green rectangular box on the right labeled 'SMS-IWMSC'. The connection point on the SMS-IWMSC side is marked with a small circle and labeled 'Niwmsc', indicating the service-based interface. + +Reference model diagram showing SMSF connected to SMS-IWMSC via SM10 interface and Niwmsc service-based interface. + +**Figure 4.1-1: Reference model – SMS-IWMSC** + +The functionalities supported by the SMS-IWMSC are listed in clause 6.3 of 3GPP TS 23.540 [14]. + +# 5 Services offered by the SMS-IWMSC + +## 5.1 Introduction + +The SMS-IWMSC offers the following services via the Niwmsc interface: + +- Niwmsc\_SMService Service + +Table 5.1-1 summarizes the corresponding APIs defined for this specification. + +**Table 5.1-1: API Descriptions** + +| Service Name | Clause | Description | OpenAPI Specification File | apiName | Annex | +|------------------|--------|---------------------------------|-------------------------------|-------------------|-------| +| Niwmsc_SMService | 6.1 | SMS-IWMSC short message service | TS29579_Niwmsc_SMService.yaml | niwmsc-smbservice | A.2 | + +## 5.2 Niwmsc\_SMService Service + +### 5.2.1 Service Description + +See 3GPP TS 23.540 [14] clause 6.3.1 + +### 5.2.2 Service Operations + +#### 5.2.2.1 Introduction + +For the Niwmsc\_SMService service the following service operations are defined: + +- MoForwardSm + +The Niwmsc\_SMService Service is used by Consumer NFs (SMSF) to transfer MO short message by means of the MoForwardSm service operation. + +#### 5.2.2.2 MoForwardSm + +##### 5.2.2.2.1 General + +This clause provides a general description of the MoForwardSm service operation. + +##### 5.2.2.2.2 SBI-based MO SM transfer + +The MoForwardSm service operation shall be used to transmit uplink SMS message via SMS-IWMSC. + +It is used in the following procedures: + +- Successful Mobile Originated short message transfer via SMS-IWMSC (see clause 5.2.2 of 3GPP TS 23.540 [14]). +- Unsuccessful Mobile Originated short message transfer via SMS-IWMSC (see clause 5.2.3 of 3GPP TS 23.540 [14]). + +The NF Service Consumer (e.g. SMSF) shall transmit uplink SMS message to the SMS-IWMSC by using the HTTP POST method as shown in Figure 5.2.2.2.1-1. + +![Sequence diagram showing SBI-based MO SM transfer between NF Service Consumer and SMS-IWMSC.](97a08abb8a43f3f8c6ce347199cd909a_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant SMS-IWMSC + Note right of NF Service Consumer: (SMS Data) + NF Service Consumer->>SMS-IWMSC: 1. POST ../mo-sm-info/{supi}/sendsms + SMS-IWMSC-->>NF Service Consumer: 2a. 200 OK (Delivery Report) + SMS-IWMSC-->>NF Service Consumer: 2b. 4xx/5xx (ProblemDetails) or 3xx + +``` + +The diagram illustrates the interaction between an NF Service Consumer and an SMS-IWMSC. The consumer sends a POST request (step 1) to the SMS-IWMSC, including SMS data. The SMS-IWMSC responds with either a 200 OK (Delivery Report) (step 2a) or a 4xx/5xx (ProblemDetails) or 3xx (step 2b). + +Sequence diagram showing SBI-based MO SM transfer between NF Service Consumer and SMS-IWMSC. + +**Figure 5.2.2.2.2.1-1: SBI-based MO SM transfer** + +1. The NF Service Consumer shall send a POST request to the resource representing the UE's Mobile Originated Short Message Information resource (i.e. .../mo-sm-info/{supi}/sendsmss) of the SMS-IWMSC. The content of the POST request shall contain the SMS message to be sent. +- 2a. On success, "200 OK" shall be returned with "SmsDeliveryData" object contains the MO SMS Delivery Report in the response body. +- 2b. On failure, or redirection, one of the HTTP status code listed in Table 6.1.3.2.4.2.2-2 shall be returned. + +# --- 6 API Definitions + +## 6.1 Niwmsc\_SMService Service API + +### 6.1.1 Introduction + +The Niwmsc\_SMService shall use the Niwmsc\_SMService API. + +The API URI of the Niwmsc\_SMService API shall be: + +**{apiRoot}** + +The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.: + +**{apiRoot}** + +with the following components: + +- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5]. +- The shall be "niwmsc-smbservice". +- The shall be "v1". +- The shall be set as described in clause 6.1.3. + +### 6.1.2 Usage of HTTP + +#### 6.1.2.1 General + +HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4]. + +HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4]. + +The OpenAPI [6] specification of HTTP messages and content bodies for the Niwmsc\_SMService API is contained in Annex A. + +#### 6.1.2.2 HTTP standard headers + +##### 6.1.2.2.1 General + +See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers. + +##### 6.1.2.2.2 Content type + +JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json". + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13]. + +Multipart messages shall also be supported (see clause 6.1.2.4) using the content type "multipart/related", comprising: + +- one JSON body part with the "application/json" content type; and +- one binary body part with 3gpp vendor specific content subtypes. + +The 3gpp vendor specific content subtypes defined in Table 6.1.2.2.2-1 shall be supported. + +**Table 6.1.2.2.2-1: 3GPP vendor specific content subtypes** + +| content subtype | Description | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| vnd.3gpp.sms | Binary encoded payload, encoding SMS payload, as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [17]. | +| NOTE: | Using 3GPP vendor content subtypes allows to describe the nature of the opaque payload (e.g. SMS payload) without having to rely on metadata in the JSON content. | + +See clause 6.1.2.4 for the binary payloads supported in the binary body part of multipart messages. + +#### 6.1.2.3 HTTP custom headers + +The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported. + +#### 6.1.2.4 HTTP multipart messages + +HTTP multipart messages shall be supported, to transfer opaque SMS payload (e.g. SMS message, CP Ack, etc.), in the following service operations (and HTTP messages): + +- MoForwardSm service operation; + +HTTP multipart messages shall include one JSON body part and one binary body part comprising content of SMS payload content (see clause 6.1.6.5). + +The JSON body part shall be the "root" body part of the multipart message. It shall be encoded as the first body part of the multipart message. The "Start" parameter does not need to be included. + +The multipart message shall include a "type" parameter (see IETF RFC 2387 [18]) specifying the media type of the root body part, i.e. "application/json". + +NOTE: The "root" body part (or "root" object) is the first body part the application processes when receiving a multipart/related message, see IETF RFC 2387 [18]. The default root is the first body within the multipart/related message. The "Start" parameter indicates the root body part, e.g. when this is not the first body part in the message. + +A binary body part shall include a Content-ID header (see IETF RFC 2045 [19]), and the JSON body part shall make a reference to the binary body part using the Content-ID header field. + +Examples of multipart/related messages can be found in Annex B. + +### 6.1.3 Resources + +#### 6.1.3.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 6.1.3.1-1 depicts the resource URIs structure for the Niwmse\_SMSService API. + +![Diagram showing the hierarchical structure of the Niwmsc_SMSService API URI. The root is {apiRoot}/niwmsc_smbservice/. It branches to /mo-sm-info, which branches to /{supi}, which branches to /send sms (dashed box).](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +{apiRoot}/niwmsc\_smbservice/ + +``` + +graph TD + Root["{apiRoot}/niwmsc_smbservice/"] --> MoSmInfo["/mo-sm-info"] + MoSmInfo --> Supi["/{supi}"] + Supi --> SendSms["/send sms"] + style SendSms stroke-dasharray: 5 5 + +``` + +Diagram showing the hierarchical structure of the Niwmsc\_SMSService API URI. The root is {apiRoot}/niwmsc\_smbservice/. It branches to /mo-sm-info, which branches to /{supi}, which branches to /send sms (dashed box). + +**Figure 6.1.3.1-1: Resource URI structure of the Niwmsc\_SMSService API** + +Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 6.1.3.1-1: Resources and methods overview** + +| Resource purpose/name | Resource URI (relative path after API URI) | HTTP method or custom operation | Description (service operation) | +|-----------------------|--------------------------------------------|---------------------------------|---------------------------------| +| SMSService | /mo-sm-info/{supi}/send sms | send sms (POST) | MO short message transfer | +| | | | | +| | | | | +| | | | | +| | | | | + +#### 6.1.3.2 Resource: MoSmInfo + +##### 6.1.3.2.1 Description + +This resource represents the collection of Mobile Originated Short Message Information in SMS-IWMSC. + +This resource is modelled with the Document resource archetype (see clause C.1 of 3GPP TS 29.501 [5]). + +##### 6.1.3.2.2 Resource Definition + +Resource URI: {apiRoot}///mo-sm-info{supi} + +This resource shall support the resource URI variables defined in table 6.1.3.2.2-1. + +**Table 6.1.3.2.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|---------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 6.1.1 | +| supi | Supi | Represents the Subscription Permanent Identifier (see 3GPP TS 23.501 [2] clause 5.9.2)
pattern: See pattern of type Supi in 3GPP TS 29.571 [15] | + +##### 6.1.3.2.3 Resource Standard Methods + +No HTTP method has been defined for the Mobile Originated Short Message Information collection resource. + +##### 6.1.3.2.4 Resource Custom Operations + +###### 6.1.3.2.4.1 Overview + +**Table 6.1.3.2.4.1-1: Custom operations** + +| Operation name | Custom operation URI | Mapped HTTP method | Description | +|----------------|-----------------------------|--------------------|-----------------------------------------------------| +| sendsms | /mo-sm-infos/{supi}/sendsms | POST | Send MO SMS message or the related Delivery Report. | + +###### 6.1.3.2.4.2 Operation: sendsms + +###### 6.1.3.2.4.2.1 Description + +This custom operation is used for NF Service Consumers to send SMS message in uplink direction. + +###### 6.1.3.2.4.2.2 Operation Definition + +This custom operation is used to send a SMS payload to an UE's Mobile Originated Short Message Information resource in the SMS-IWMSC. + +This operation shall support the request data structures specified in table 6.1.3.2.4.2.2-1 and the response data structure and response codes specified in table 6.1.3.2.4.2.2-2. + +**Table 6.1.3.2.4.2.2-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|--------------------------------------------------| +| SmsData | M | 1 | Representation of the MO SMS message to be sent. | + +**Table 6.1.3.2.4.2.2-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SmsDeliveryData | M | 1 | 200 OK | This case represents the successful of sending SMS message in uplink direction, with necessary response data on the received delivery report. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection. (NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection. (NOTE 2) | +| ProblemDetails | O | 0..1 | 400 Bad Request | This case represents an unsuccessful delivery of SMS message.
The "cause" attribute may be used to indicate one of the following application errors:
  • - SMS_PAYLOAD_MISSING, if the expected SMS payload content is missing;
  • - SMS_PAYLOAD_ERROR, if error exists in the SMS payload content.
| +| ProblemDetails | O | 0..1 | 403 Forbidden | This case represents an unsuccessful delivery of SMS message.
The "cause" attribute may be used to indicate one of the following application errors:
  • - UNKNOWN_SERVICE_CENTRE_ADDRESS, if the SMS-SC was unknown;
  • - SERVICE_CENTRE_CONGESTION, if the SMS-SC was in congestion;
  • - USER_NOT_SERVICE_CENTER, if the user didn't belongs to the SMS-SC;
  • - FACILITY_NOT_SUPPORTED, if the facility not supported;
  • - INVALID_SME_ADDRESS, if the SME address is invalid..
| +| ProblemDetails | O | 0..1 | 504 Gateway Timeout | This case represents an unsuccessful delivery of SMS message.
The "cause" attribute may be used to indicate one of the following application errors:
  • - UNREACHABLE_SMS_SC, if the response is timeout.
| + +NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. + +**Table 6.1.3.2.4.2.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same SMS-IWMSC or SMS-IWMSC (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +**Table 6.1.3.2.4.2.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative service instance within the same SMS-IWMSC or SMS-IWMSC (service) set.
For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance ID towards which the request is redirected | + +### 6.1.4 Custom Operations without associated resources + +In this release of this specification, no custom operations without associated resources are defined. + +### 6.1.5 Notifications + +In this release of this specification, no notification procedures are defined. + +### 6.1.6 Data Model + +#### 6.1.6.1 General + +This clause specifies the application data model supported by the API. + +Table 6.1.6.1-1 specifies the data types defined for the Niwmsc\_SMSService service based interface protocol. + +**Table 6.1.6.1-1: Niwmsc\_SMSService specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|-----------|----------------|-------------|---------------| +| N/A | | | | + +Table 6.1.6.1-2 specifies data types re-used by the Niwmsc\_SMSService service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Niwmsc\_SMSService service based interface. + +**Table 6.1.6.1-2: Niwmsc\_SMSService re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|--------------------------------------------------------------------------------------------------------------------|---------------| +| ProblemDetails | 3GPP TS 29.571 [15] | Common Data Type used in response bodies | | +| RedirectResponse | 3GPP TS 29.571 [15] | Redirect Response | | +| Supi | 3GPP TS 29.571 [15] | Subscription Permanent Identifier | | +| RefToBinaryData | 3GPP TS 29.571 [15] | Information for indicating the binary content of SMS payload. | | +| Ipv4Addr | 3GPP TS 29.571 [15] | IPv4 address | | +| Ipv6Addr | 3GPP TS 29.571 [15] | IPv6 address | | +| SupportedFeatures | 3GPP TS 29.571 [15] | Supported Features | | +| SmsData | 3GPP TS 29.577 [17] | Information within request message invoking MoForwardSm service operation, for delivering MO SMS. | | +| SmsDeliveryData | 3GPP TS 29.571 [17] | Information within response message invoking MoForwardSm service operation, for delivering MO SMS Delivery Report. | | + +#### 6.1.6.2 Structured data types + +In this release of this specification, no structure to be used in resource representations is defined. + +#### 6.1.6.3 Simple data types and enumerations + +##### 6.1.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +##### 6.1.6.3.2 Simple data types + +The simple data types defined in table 6.1.6.3.2-1 shall be supported. + +**Table 6.1.6.3.2-1: Simple data types** + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| N/A | | | | + +#### 6.1.6.4 Data types describing alternative data types or combinations of data types + +None. + +#### 6.1.6.5 Binary data + +##### 6.1.6.5.1 Binary Data Types + +**Table 6.1.6.5.1-1: Binary Data Types** + +| Name | Clause defined | Content type | +|-------------------------|----------------|--------------| +| SMS Payload Information | 6.1.6.4.2 | vnd.3gpp.sms | + +##### 6.1.6.5.2 SMS Payload Information + +SMS Payload Information shall encode a SMS payload as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [18], using the vnd.3gpp.sms content-type. + +SMS Payload Information may encode e.g. the following content: + +- CP-DATA, CP-ACK, CP-ERROR as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [18]. + +### 6.1.7 Error Handling + +#### 6.1.7.1 General + +For the Niwmsc\_SMService API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. + +In addition, the requirements in the following clauses are applicable for the Niwmsc\_SMService API. + +#### 6.1.7.2 Protocol Errors + +No specific procedures for the Niwmsc\_SMService service are specified. + +#### 6.1.7.3 Application Errors + +The application errors defined for the Niwmsc\_SMService service are listed in Table 6.1.7.3-1. + +**Table 6.1.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|---------------------------|---------------------|-----------------------------------------------------------------------------------------| +| SMS_PAYLOAD_MISSING | 400 Bad Request | The expected SMS payload content is missing. | +| SMS_PAYLOAD_ERROR | 400 Bad Request | Errors exist in the format of SMS payload. | +| SERVICE_CENTRE_CONGESTION | 403 Forbidden | The delivery of the MO short message failed because SMS-SC was in congestion. | +| USER_NOT_SERVICE_CENTER | 403 Forbidden | The delivery of the short message failed because the user didn't belongs to the SMS-SC. | +| FACILITY_NOT_SUPPORTED | 403 Forbidden | The delivery of the MO short message failed because of facility not supported. | +| INVALID_SME_ADDRESS | 403 Forbidden | The delivery of the MO short message failed because the SME address is invalid. | +| UNREACHABLE_SMS_SC | 504 Gateway Timeout | The delivery of the MO short message failed because the response is timeout. | + +### 6.1.8 Feature negotiation + +The optional features in table 6.1.8-1 are defined for the Niwmsc\_SMService API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4]. + +**Table 6.1.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| N/A | | | + +### 6.1.9 Security + +As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Niwmsc\_SMService API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server. + +If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Niwmsc\_SMService API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2. + +NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Niwmsc\_SMService service. + +The Niwmsc\_SMService API defines a single scope "niwmsc-smbservice" for the entire service, and it does not define any additional scopes at resource or operation level. + +### 6.1.10 HTTP redirection + +An HTTP request may be redirected to a different SMS-IWMSC service instance, within the same SMS-IWMSC or a different SMS-IWMSC of an SMS-IWMSC set, e.g. when an SMS-IWMSC service instance is part of an SMS-IWMSC (service) set or when using indirect communications (see 3GPP TS 29.500 [4]). + +An SCP that reselects a different SMS-IWMSC producer instance will return the NF Instance ID of the new SMS-IWMSC producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4]. + +If an SMS-IWMSC within an SMS-IWMSC set redirects a service request to a different SMS-IWMSC of the set using a 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new SMS-IWMSC towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +# Annex A (normative): OpenAPI specification + +## A.1 General + +This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format. + +This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s). + +NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5.3.1 of 3GPP TS 29.501 [5] and clause 5B of 3GPP TR 21.900 [7]). + +## A.2 Niwmsc\_SMService API + +``` +openapi: 3.0.0 +info: + title: 'Niwmsc_SMService' + version: '1.1.0-alpha.2' + description: | + SMS-IWMSC Short Message Service. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 29.579 V18.1.0; 5G System; SMS Services; Stage 3. + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.579/ + +servers: + - url: '{apiRoot}/niwmsc-smsservice/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501 + +security: + - oAuth2ClientCredentials: + - niwmsc-smsservice + - {} + +paths: + /mo-sm-infos/{supi}/sendsms: + post: + summary: Send SMS payload for a given UE + operationId: SendSMS + tags: + - Send MO SMS message and the delivery report + parameters: + - name: supi + in: path + required: true + description: Subscription Permanent Identifier (SUPI) + schema: + type: string + requestBody: + content: + multipart/related: # message with a binary body part + schema: + type: object + properties: + jsonData: + $ref: '#/components/schemas/SmsData' + binaryPayload: +``` + +``` + type: string + format: binary + encoding: + jsonData: + contentType: application/json + binaryPayload: + contentType: application/vnd.3gpp.sms + headers: + Content-Id: + schema: + type: string + required: true + responses: + '200': + description: sending delivery report + content: + multipart/related: # message with a binary body part + schema: + type: object + properties: + jsonData: + $ref: '#/components/schemas/SmsDeliveryData' + binaryPayload: + type: string + format: binary + encoding: + jsonData: + contentType: application/json + binaryPayload: + contentType: application/vnd.3gpp.sms + headers: + Content-Id: + schema: + type: string + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '504': + $ref: 'TS29571_CommonData.yaml#/components/responses/504' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +components: + + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{nrfApiRoot}/oauth2/token' + scopes: + niwmsc-smbservice: Access to the niwmsc-smbservice API + +schemas: + + SmsData: + description: > +``` + +``` + + Information within request message invoking MoForwardSm service operation, + for delivering MO SMS. +type: object +required: + - smsPayload +properties: + smsPayload: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData' + +SmsDeliveryData: + description: > + Information within response message invoking MoForwardSm service operation, + for delivering MO SMS Delivery Report. + type: object + required: + - smsPayload + properties: + smsPayload: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData' + +# COMPLEX TYPES: + +# SIMPLE TYPES: + +# ENUMS: + +``` + +# --- Annex B (informative): Withdrawn API versions + +## B.1 General + +This Annex lists withdrawn API versions of the APIs defined in the present specification. 3GPP TS 29.501 [5] clause 4.3.1.6 describes the withdrawal of API versions. + +## --- B.2 Niwmsc\_SMService API + +The API versions listed in table B.2-1 are withdrawn for the Niwmsc\_SMService API. + +**Table B.2-1: Withdrawn API versions of the Niwmsc\_SMService service** + +| API version number | Remarks | +|--------------------|---------| +| | | + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|-------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-04 | CT4#109e | C4-222331 | | | | C4-222331 as basis | 0.1.0 | +| 2022-04 | CT4#109e | C4-222343 | | | | Implementation of C4-222343 in CT4#109e | 0.2.0 | +| 2022-05 | CT4#110e | C4-223452 | | | | Implementation of C4-223219 and C4-223224 in CT4#110e | 0.3.0 | +| 2022-06 | CT#96 | CP-221080 | | | | TS presented for information and approval | 1.0.0 | +| 2022-06 | CT#96 | CP-221080 | | | | TS approved at CT#95 | 17.0.0 | +| 2022-09 | CT#97e | CP-222027 | 0002 | - | B | Add 3xx for the service operation | 17.1.0 | +| 2022-09 | CT#97e | CP-222027 | 0003 | - | F | Alignment on the service name used with template | 17.1.0 | +| 2022-09 | CT#97e | CP-222027 | 0004 | - | F | Corrections on the table name and NOTE | 17.1.0 | +| 2022-09 | CT#97e | CP-222027 | 0005 | - | F | Update on the content type for OpenAPI | 17.1.0 | +| 2022-09 | CT#97e | CP-222027 | 0006 | 1 | F | Update on the reference model | 17.1.0 | +| 2022-09 | CT#97e | CP-222058 | 0007 | - | F | 29.579 Rel-17 API version and External doc update | 17.1.0 | +| 2022-12 | CT#98e | CP-223028 | 0008 | 1 | F | Missing Mandatory Status Codes in OpenAPI | 18.0.0 | +| 2022-12 | CT#98e | CP-223033 | 0009 | - | F | 29.579 Rel-18 API version and External doc update | 18.0.0 | +| 2023-03 | CT#99e | CP-230073 | 0012 | - | A | Rel-18 Niwmsc SMService API HTTP code correction | 18.0.1 | +| 2023-03 | CT#99e | CP-230071 | 0014 | - | F | 29.579 Rel-18 API version and External doc update | 18.0.1 | +| 2023-03 | CT#99e | CP-230321 | 0015 | - | F | 29.579 Rel-18 API version and External doc update | 18.1.0 | +| 2023-06 | CT#99e | CP-231026 | 0013 | 3 | F | Location header description | 18.2.0 | +| 2023-12 | CT#102 | CP-233027 | 0017 | - | F | HTTP RFCs obsoleted by IETF RFC 9113 | 18.3.0 | +| 2023-12 | CT#102 | CP-233028 | 0016 | 1 | F | HTTP RFCs update in TS 29.579 | 18.3.0 | +| 2023-12 | CT#102 | CP-233030 | 0018 | - | F | ProblemDetails RFC 7807 obsoleted by 9457 | 18.3.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29583/raw.md b/marked/Rel-18/29_series/29583/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2a084f3b0d5274eb872305f54986d99cb464d61c --- /dev/null +++ b/marked/Rel-18/29_series/29583/raw.md @@ -0,0 +1,3519 @@ + + +# 3GPP TS 29.583 V18.1.1 (2024-07) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Application layer support for Personal IoT Network (PINAPP); Personal IoT Network (PIN) server services; Stage 3 (Release 18)** --- + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'G' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 +Intpp.org + +## **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 9 | +| 4 Overview..... | 9 | +| 5 Services offered by PIN Server..... | 10 | +| 5.1 Introduction ..... | 10 | +| 5.2 PIN_ASRegistration Service..... | 10 | +| 5.2.1 Service Description ..... | 10 | +| 5.2.2 Service Operations..... | 10 | +| 5.2.2.1 Introduction..... | 10 | +| 5.2.2.2 PIN_ASRegistration_Request ..... | 11 | +| 5.2.2.2.1 General ..... | 11 | +| 5.2.2.2.2 PAS Registration Creation ..... | 11 | +| 5.2.2.3 PIN_ASRegistration_Update..... | 11 | +| 5.2.2.3.1 General ..... | 11 | +| 5.2.2.3.2 Updating an existing Registration..... | 11 | +| 5.2.2.4 PIN_ASRegistration_Deregister..... | 12 | +| 5.2.2.4.1 General ..... | 12 | +| 5.2.2.4.2 Deregistering the Registration..... | 12 | +| 5.3 PIN_ASServiceSwitch Service ..... | 12 | +| 5.3.1 Service Description ..... | 12 | +| 5.3.2 Service Operations..... | 13 | +| 5.3.2.1 Introduction..... | 13 | +| 5.3.2.2 PIN_ASServiceSwitch_Subscribe ..... | 13 | +| 5.3.2.2.1 General ..... | 13 | +| 5.3.2.2.2 Service Switch Information Subscription Creation..... | 13 | +| 5.3.2.3 PIN_ASServiceSwitch_Notify ..... | 13 | +| 5.3.2.3.1 General ..... | 13 | +| 5.3.2.3.2 Service Switch Information Notification ..... | 14 | +| 5.3.2.4 PIN_ASServiceSwitch_Update ..... | 14 | +| 5.3.2.4.1 General ..... | 14 | +| 5.3.2.4.2 Service Switch Information Update ..... | 14 | +| 5.3.2.5 PIN_ASServiceSwitch_Unsubscribe..... | 15 | +| 5.3.2.5.1 General ..... | 15 | +| 5.3.2.5.2 Unsubscribing the Service Switch Information ..... | 15 | +| 5.4 PIN_ASServiceContinuity Service ..... | 15 | +| 5.4.1 Service Description ..... | 15 | +| 5.4.2 Service Operations..... | 15 | +| 5.4.2.1 Introduction..... | 15 | +| 5.4.2.2 PIN_ASServiceContinuity_Subscribe ..... | 16 | +| 5.4.2.2.1 General ..... | 16 | +| 5.4.2.2.2 Service Continuity Information Subscription Creation..... | 16 | +| 5.4.2.3 PIN_ASServiceContinuity_Notify ..... | 16 | +| 5.4.2.3.1 General ..... | 16 | +| 5.4.2.3.2 Service Continuity Information Notification ..... | 17 | +| 5.4.2.4 PIN_ASServiceContinuity_Update ..... | 17 | +| 5.4.2.4.1 General ..... | 17 | +| 5.4.2.4.2 Service Continuity Information Update ..... | 17 | +| 5.4.2.5 PIN_ASServiceContinuity_Unsubscribe..... | 18 | +| 5.4.2.5.1 General ..... | 18 | +| 5.4.2.5.2 Unsubscribing the Service Continuity Information ..... | 18 | + +| | | | +|-------------|-------------------------------------------------------------------|----| +| 6 | API Definitions ..... | 18 | +| 6.1 | PIN_ASRegistration Service API ..... | 18 | +| 6.1.1 | Introduction ..... | 18 | +| 6.1.2 | Usage of HTTP..... | 19 | +| 6.1.3 | Resources..... | 19 | +| 6.1.3.1 | Overview..... | 19 | +| 6.1.3.2 | Resource: PAS Registrations ..... | 20 | +| 6.1.3.2.1 | Description ..... | 20 | +| 6.1.3.2.2 | Resource Definition..... | 20 | +| 6.1.3.2.3 | Resource Standard Methods..... | 20 | +| 6.1.3.2.3.1 | POST ..... | 20 | +| 6.1.3.2.4 | Resource Custom Operations ..... | 21 | +| 6.1.3.3 | Resource: Individual PAS Registration ..... | 21 | +| 6.1.3.3.1 | Description ..... | 21 | +| 6.1.3.3.2 | Resource Definition..... | 21 | +| 6.1.3.3.3 | Resource Standard Methods..... | 21 | +| 6.1.3.3.3.1 | GET ..... | 21 | +| 6.1.3.3.3.2 | PUT..... | 22 | +| 6.1.3.3.3.3 | DELETE..... | 23 | +| 6.1.3.3.3.4 | PATCH..... | 24 | +| 6.1.3.3.4 | Resource Custom Operations ..... | 25 | +| 6.1.4 | Custom Operations without associated resources ..... | 25 | +| 6.1.5 | Notifications ..... | 25 | +| 6.1.6 | Data Model ..... | 25 | +| 6.1.6.1 | General..... | 25 | +| 6.1.6.2 | Structured data types..... | 26 | +| 6.1.6.2.1 | Introduction ..... | 26 | +| 6.1.6.2.2 | Type: PASRegistration..... | 26 | +| 6.1.6.2.3 | Type: ConnectivityInfo ..... | 27 | +| 6.1.6.2.4 | Type: PASRegistrationPatch..... | 27 | +| 6.1.6.3 | Simple data types and enumerations..... | 27 | +| 6.1.6.3.1 | Introduction ..... | 27 | +| 6.1.6.3.2 | Simple data types ..... | 27 | +| 6.1.7 | Error Handling ..... | 27 | +| 6.1.7.1 | General..... | 27 | +| 6.1.7.2 | Protocol Errors ..... | 27 | +| 6.1.7.3 | Application Errors..... | 28 | +| 6.1.8 | Feature negotiation ..... | 28 | +| 6.1.9 | Security ..... | 28 | +| 6.2 | PIN_ASServiceSwitch API..... | 28 | +| 6.2.1 | Introduction ..... | 28 | +| 6.2.2 | Usage of HTTP..... | 28 | +| 6.2.3 | Resources..... | 29 | +| 6.2.3.1 | Overview..... | 29 | +| 6.2.3.2 | Resource: Service Switch Information Subscriptions ..... | 29 | +| 6.2.3.2.1 | Description ..... | 29 | +| 6.2.3.2.2 | Resource Definition..... | 29 | +| 6.2.3.2.3 | Resource Standard Methods..... | 30 | +| 6.2.3.2.3.1 | POST ..... | 30 | +| 6.2.3.2.4 | Resource Custom Operations ..... | 30 | +| 6.2.3.3 | Resource: Individual Service Switch Information Subscription..... | 31 | +| 6.2.3.3.1 | Description ..... | 31 | +| 6.2.3.3.2 | Resource Definition..... | 31 | +| 6.2.3.3.3 | Resource Standard Methods..... | 31 | +| 6.2.3.3.3.1 | GET ..... | 31 | +| 6.2.3.3.3.2 | PATCH..... | 32 | +| 6.2.3.3.3.3 | PUT..... | 33 | +| 6.2.3.3.3.4 | DELETE..... | 34 | +| 6.2.3.3.4 | Resource Custom Operations ..... | 35 | +| 6.2.4 | Custom Operations without associated resources ..... | 35 | +| 6.2.5 | Notifications ..... | 35 | +| 6.2.5.0 | General..... | 35 | + +| | | | +|-------------|-----------------------------------------------------------------------|----| +| 6.2.5.1 | Service Switch Information Notification ..... | 36 | +| 6.2.5.1.1 | Description ..... | 36 | +| 6.2.5.1.2 | Target URI..... | 36 | +| 6.2.5.1.3 | Standard Methods..... | 36 | +| 6.2.5.1.3.1 | POST ..... | 36 | +| 6.2.6 | Data Model ..... | 37 | +| 6.2.6.1 | General ..... | 37 | +| 6.2.6.2 | Structured data types..... | 38 | +| 6.2.6.2.1 | Introduction ..... | 38 | +| 6.2.6.2.2 | Type: ServiceSwitchInfo..... | 38 | +| 6.2.6.2.3 | Type: ServiceSwitchInfoPatch..... | 38 | +| 6.2.6.2.4 | Type: ServiceSwitchInfoNotification ..... | 39 | +| 6.2.6.2.5 | Type: ServiceSwitchReportInfo..... | 39 | +| 6.2.6.3 | Simple data types and enumerations..... | 39 | +| 6.2.6.3.1 | Introduction ..... | 39 | +| 6.2.6.3.2 | Enumeration: EventType..... | 39 | +| 6.2.7 | Error Handling ..... | 39 | +| 6.2.7.1 | General ..... | 39 | +| 6.2.7.2 | Protocol Errors ..... | 39 | +| 6.2.7.3 | Application Errors..... | 40 | +| 6.2.8 | Feature negotiation ..... | 40 | +| 6.2.9 | Security ..... | 40 | +| 6.3 | PIN_ASServiceContinuity API..... | 40 | +| 6.3.1 | Introduction ..... | 40 | +| 6.3.2 | Usage of HTTP..... | 40 | +| 6.3.3 | Resources..... | 41 | +| 6.3.3.1 | Overview..... | 41 | +| 6.3.3.2 | Resource: Service Continuity Information Subscriptions ..... | 41 | +| 6.3.3.2.1 | Description ..... | 41 | +| 6.3.3.2.2 | Resource Definiton..... | 41 | +| 6.3.3.2.3 | Resource Standard Methods..... | 42 | +| 6.3.3.2.3.1 | POST ..... | 42 | +| 6.3.3.2.4 | Resource Custom Operations..... | 42 | +| 6.3.3.3 | Resource: Individual Service Continuity Information Subscription..... | 43 | +| 6.3.3.3.1 | Description ..... | 43 | +| 6.3.3.3.2 | Resource Definiton..... | 43 | +| 6.3.3.3.3 | Resource Standard Methods..... | 43 | +| 6.3.3.3.3.1 | GET ..... | 43 | +| 6.3.3.3.3.2 | PATCH ..... | 44 | +| 6.3.3.3.3.3 | PUT..... | 45 | +| 6.3.3.3.3.4 | DELETE ..... | 46 | +| 6.3.3.3.4 | Resource Custom Operations..... | 47 | +| 6.3.4 | Custom Operations without associated resources ..... | 47 | +| 6.3.5 | Notifications ..... | 47 | +| 6.3.5.0 | General ..... | 47 | +| 6.3.5.1 | Service Continuity Information Notification ..... | 48 | +| 6.3.5.1.1 | Description ..... | 48 | +| 6.3.5.1.2 | Target URI..... | 48 | +| 6.3.5.1.3 | Standard Methods..... | 48 | +| 6.3.5.1.3.1 | POST ..... | 48 | +| 6.3.6 | Data Model ..... | 49 | +| 6.3.6.1 | General ..... | 49 | +| 6.3.6.2 | Structured data types..... | 50 | +| 6.3.6.2.1 | Introduction ..... | 50 | +| 6.3.6.2.2 | Type: ServiceContinuityInfo..... | 50 | +| 6.3.6.2.3 | Type: ServiceContinuityInfoPatch..... | 50 | +| 6.3.6.2.4 | Type: ServiceContinuityInfoNotification ..... | 51 | +| 6.3.6.2.5 | Type: ServiceContinuityReportInfo..... | 51 | +| 6.3.6.3 | Simple data types and enumerations..... | 51 | +| 6.3.6.3.1 | Introduction ..... | 51 | +| 6.3.6.3.2 | Enumeration: EventType..... | 51 | +| 6.3.7 | Error Handling ..... | 51 | + +| | | | +|-------------------------------|------------------------------------|-----------| +| 6.3.7.1 | General ..... | 51 | +| 6.3.7.2 | Protocol Errors ..... | 52 | +| 6.3.7.3 | Application Errors ..... | 52 | +| 6.3.8 | Feature negotiation ..... | 52 | +| 6.3.9 | Security ..... | 52 | +| 7 | Using Common API Framework ..... | 53 | +| 7.1 | General ..... | 53 | +| 7.2 | Security ..... | 53 | +| Annex A (normative): | OpenAPI specification ..... | 54 | +| A.1 | General ..... | 54 | +| A.2 | PIN_ASRegistration API ..... | 54 | +| A.3 | PIN_ASServiceSwitch API ..... | 58 | +| A.4 | PIN_ASServiceContinuity API ..... | 63 | +| Annex B (informative): | Change history ..... | 69 | + +# --- 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 stage 3 protocol and data model for PIN-9 interface between the PIN application server and PIN server. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the PIN server over PIN-9 interface. The stage 2 functional requirements are defined in 3GPP TS 23.542 [10]. + +# --- 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 29.122: "T8 reference point for Northbound Application Programming Interfaces (APIs)". +- [3] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [4] OpenAPI: "OpenAPI Specification Version 3.0.0", . +- [5] 3GPP TR 21.900: "Technical Specification Group working methods". +- [6] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2". +- [7] 3GPP TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3". +- [8] 3GPP TS 33.122: "Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs". +- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [10] 3GPP TS 23.542: "Application layer support for Personal IoT Network". +- [11] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [12] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms 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]. + +**Personal IoT Network (PIN):** A configured and managed group of PIN Element(s) that are able to communicate with each other directly, communicate with each other via PIN Element(s) with Gateway Capability (i.e. PEGC(s)), or use a PEGC to communicate with devices or servers that are outside of the PIN via the 5G network. A PIN includes at least + +one PEGC and is managed by PIN Element(s) with Management Capability (i.e. PEMC(s)) with the support by an AF if AF is deployed. + +**PIN Element with Gateway Capability (PEGC):** A PIN Element with the ability to provide DN connectivity via the 5G network for other PIN Elements and/or is able to provide relay functionality for communication between PIN Elements. Only a UE is able to act as a PEGC. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|-------------------------------------| +| PAS | PIN Application Server | +| PEGC | PIN Element with Gateway Capability | +| PIN | Personal IoT Network | +| PINAPP | Personal IoT Network Application | + +# 4 Overview + +The Personal IoT Network (PIN) Server forms part of the Application layer support for Personal IoT Networks defined in 3GPP TS 23.542 [10]. It is aimed to support the server-side functionalities required for managing the PIN. The PIN Server provides the following functionalities: + +- support PAS registration management procedure (see clause 5.2); +- support PAS service switch subscription procedure (see clause 5.3); and +- support PAS service continuity subscription procedure (see clause 5.4). + +Figure 4-1 shows the reference point representation of the architecture for Personal IoT Network Application. + +![Figure 4-1: PINAPP architecture diagram showing the interaction between Personal IoT Network, 3GPP Core network, and Data network components.](2ba086df3506f81bae3a9b53725dcfea_img.jpg) + +The diagram illustrates the PINAPP architecture across three main components: Personal IoT Network (left), 3GPP Core network (middle), and Data network (right). The Data network contains an Application server and a PIN server (enabler) connected by a reference point labeled PIN-9. The 3GPP Core network connects to the PIN server via a reference point labeled PIN-8. A horizontal line labeled PIN-6 / PIN-7 connects the Personal IoT Network to the PIN server (enabler) within the Data network. + +Figure 4-1: PINAPP architecture diagram showing the interaction between Personal IoT Network, 3GPP Core network, and Data network components. + +**Figure 4-1: PINAPP architecture** + +PIN-9 reference point exists between the application server and PIN server for the interactions related to enabling PINAPP. + +# 5 Services offered by PIN Server + +## 5.1 Introduction + +The PIN Server provides the following services: + +- PIN\_ASRegistration +- PIN\_ASServiceSwitch +- PIN\_ASServiceContinuity + +Table 5.1-1 summarizes the corresponding APIs defined in this specification. + +**Table 5.1-1: PIN server API Descriptions** + +| Service Name | Clause | Description | OpenAPI Specification File | API Name | Annex | +|-------------------------|--------|------------------------------------------|--------------------------------------|--------------------------|-------| +| PIN_ASRegistration | 5.2 | Service for AS registration | TS29583_PIN_ASRegistration.yaml | pin-as-registration | A.2 | +| PIN_ASServiceSwitch | 5.3 | Service for reporting service switch | TS29583_PIN_ASServiceSwitch.yaml | pin-as-serviceswitch | A.3 | +| PIN_ASServiceContinuity | 5.4 | Service for reporting service continuity | TS29583_PIN_ASServiceContinuity.yaml | pin-as-servicecontinuity | A.4 | + +NOTE: When 3GPP TS 29.122 [2] is referenced for the common protocol and interface aspects for API definition in the clauses under clause 5, the PIN Server takes the role of the SCEF and the service consumer takes the role of the SCS/AS. + +## 5.2 PIN\_ASRegistration Service + +### 5.2.1 Service Description + +The PIN\_ASRegistration API exposed by the PIN Server enables a service consumer to: + +- create/update/delete a PAS Registration. + +### 5.2.2 Service Operations + +#### 5.2.2.1 Introduction + +The service operation defined for PIN\_ASRegistration API is shown in the table 5.2.2.1-1. + +**Table 5.2.2.1-1: Operations of the PIN\_ASRegistration API** + +| Service operation name | Description | Initiated by | +|-------------------------------|------------------------------------------------------------------------------------------------------------------|--------------| +| PIN_ASRegistration_Request | This service operation is used by the service consumer to register to the PIN server. | e.g. PAS | +| PIN_ASRegistration_Update | This service operation is used by the service consumer to update the registration information to the PIN server. | e.g. PAS | +| PIN_ASRegistration_Deregister | This service operation is used by the service consumer to deregister from the PIN server. | e.g. PAS | + +#### 5.2.2.2 PIN\_ASRegistration\_Request + +##### 5.2.2.2.1 General + +This service operation is used by the PAS to register to a PIN server. + +##### 5.2.2.2.2 PAS Registration Creation + +Figure 5.2.2.2.2-1 depicts a scenario where a service consumer sends a request to the PIN Server to request the creation of the PAS Registration. + +![Sequence diagram for PAS Registration Creation. A Service Consumer sends a POST request to a PIN Server. The PIN Server responds with either a 201 Created status code and a PASRegistration object, or a 4xx/5xx error status code.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +``` + +sequenceDiagram + participant Service Consumer + participant PIN Server + Note left of Service Consumer: Request PAS Registration Creation + Service Consumer->>PIN Server: 1. POST .../registrations(PASRegistration) + Note right of PIN Server: Success or Error + PIN Server-->>Service Consumer: 2a. 201 Created (PASRegistration) + Note right of PIN Server: Error handling + PIN Server-->>Service Consumer: 2b. 4xx/5xx + +``` + +Sequence diagram for PAS Registration Creation. A Service Consumer sends a POST request to a PIN Server. The PIN Server responds with either a 201 Created status code and a PASRegistration object, or a 4xx/5xx error status code. + +**Figure 5.2.2.2.2-1: Procedure for PAS Registration Creation** + +1. In order to request the creation of the PAS Registration to the PIN server, the service consumer shall send the HTTP POST request request to the PIN Server targeting the URI of the "PAS Registrations" collection resource, with the request body including the PASRegistration data structure. +- 2a. Upon success, the PIN Server shall respond with an HTTP "201 Created" status code with the response body containing a representation of the created "Individual PAS Registration" resource within the PASRegistration data structure. +- 2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.1.7. + +#### 5.2.2.3 PIN\_ASRegistration\_Update + +##### 5.2.2.3.1 General + +This service operation is used by the service consumer to update the registration information at a given PIN server. + +##### 5.2.2.3.2 Updating an existing Registration + +![Sequence diagram for updating a registration. A Service Consumer sends a PUT/PATCH request to a PIN Server for a specific registration ID. The PIN Server responds with either a 200 OK status code and a PASRegistration object, a 204 No Content status code, or a 4xx/5xx error status code.](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg) + +``` + +sequenceDiagram + participant Service Consumer + participant PIN Server + Note left of Service Consumer: Update Registration + Service Consumer->>PIN Server: 1. PUT/PATCH .../registrations/{registrationId} +(PASRegistration or PASRegistrationPatch) + Note right of PIN Server: Success or Error + PIN Server-->>Service Consumer: 2a. 200 OK (PASRegistration) / 204 No Content + Note right of PIN Server: Error handling + PIN Server-->>Service Consumer: 2b. 4xx/5xx + +``` + +Sequence diagram for updating a registration. A Service Consumer sends a PUT/PATCH request to a PIN Server for a specific registration ID. The PIN Server responds with either a 200 OK status code and a PASRegistration object, a 204 No Content status code, or a 4xx/5xx error status code. + +**Figure 5.2.2.3.2-1: Procedure for update of a registration** + +1. In order to update an existing registration information, the service consumer shall send the HTTP PUT/PATCH request to the PIN server, targeting the URI of the corresponding "Individual PAS Registration" collection resource, with the request body either: + +- the updated representation of the resource within the PASRegistration data structure, in case the HTTP PUT method is used; or +- the requested modifications to the resource within the PASRegistrationPatch data structure, in case the HTTP PATCH method is used. + +NOTE: An alternative service consumer (i.e. other than the one that requested the creation of the targeted resource) can initiate this request. + +2a. Upon success, the PIN server shall update the targeted "Individual PAS Registration" resource accordingly and respond with either: + +- an HTTP "200 OK" status code with the response body containing a representation of the updated "Individual PAS Registration" resource within the PASRegistration data structure; or +- an HTTP "204 No Content" status code. + +2b. On failure, the PIN server shall send the error response as specified in clause 6.1.7. + +#### 5.2.2.4 PIN\_ASRegistration\_Deregister + +##### 5.2.2.4.1 General + +This service operation is used by the service consumer to deregister itself from a given PIN server. + +##### 5.2.2.4.2 Deregistering the Registration + +![Sequence diagram showing the procedure for deregistering the registration. A Service Consumer sends a DELETE request to a PIN Server. The PIN Server responds with either a 204 No Content status code (2a) or an error status code (2b).](5a95b187de0044da69b7322e04761b86_img.jpg) + +``` +sequenceDiagram + participant Service Consumer + participant PIN Server + Note left of Service Consumer: 1. DELETE .../registrations/{registrationId} + Service Consumer->>PIN Server: 1. DELETE .../registrations/{registrationId} + Note right of PIN Server: 2a. "204 No Content" +2b. 4xx/5xx + PIN Server-->>Service Consumer: 2a. "204 No Content" +2b. 4xx/5xx +``` + +Sequence diagram showing the procedure for deregistering the registration. A Service Consumer sends a DELETE request to a PIN Server. The PIN Server responds with either a 204 No Content status code (2a) or an error status code (2b). + +**Figure 5.2.2.4.2-1: Procedure for Deregistering the Registration** + +1. In order to request the deletion of an existing PAS registration information, the service consumer shall send an HTTP DELETE request to the PIN server targeting the corresponding "Individual PAS Registration" resource. + +2a. Upon success, the PIN server shall respond with an HTTP "204 No Content" status code. + +2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP DELETE response body, as specified in clause 6.1.7. + +## 5.3 PIN\_ASServiceSwitch Service + +### 5.3.1 Service Description + +The PIN\_ASServiceSwitch API exposed by the PIN Server enables a service consumer to: + +- create/update/delete a Service Switch Information Subscription; and +- receive Service Switch Information Notifications; + +### 5.3.2 Service Operations + +#### 5.3.2.1 Introduction + +The service operation defined for PIN\_ASServiceSwitch API is shown in the table 5.3.2.1-1. + +**Table 5.3.2.1-1: Operations of the PIN\_ASServiceSwitch API** + +| Service operation name | Description | Initiated by | +|-------------------------------|----------------------------------------------------------------------------------------------------------------------|--------------| +| PIN_ASServiceSwitch_Subscribe | This service operation enables a service consumer to create/update/delete a Service Switch Information Subscription. | e.g., PAS | +| PIN_ASServiceSwitch_Notify | This service operation enables a service consumer to receive the Service Switch Information Notifications. | PIN server | + +#### 5.3.2.2 PIN\_ASServiceSwitch\_Subscribe + +##### 5.3.2.2.1 General + +This service operation is used by the service consumer to request the creation of a Service Switch information. + +##### 5.3.2.2.2 Service Switch Information Subscription Creation + +![Sequence diagram showing the procedure for PAS Subscription Creation. A Service Consumer sends a POST request to a PIN Server. The PIN Server responds with a 201 Created status code and the ServiceSwitchInfo data structure. If there is an error, a 4xx/5xx status code is returned.](5dfc130b129ace4df375839020a5700d_img.jpg) + +``` + +sequenceDiagram + participant Service Consumer + participant PIN Server + Note left of Service Consumer: Service Consumer + Service Consumer->>PIN Server: 1. POST .../subscriptions (ServiceSwitchInfo) + Note right of PIN Server: PIN Server + PIN Server-->>Service Consumer: 2a. 201 Created (ServiceSwitchInfo) + Note right of PIN Server: 2b. 4xx/5xx + +``` + +Sequence diagram showing the procedure for PAS Subscription Creation. A Service Consumer sends a POST request to a PIN Server. The PIN Server responds with a 201 Created status code and the ServiceSwitchInfo data structure. If there is an error, a 4xx/5xx status code is returned. + +**Figure 5.3.2.2.2-1: Procedure for PAS Subscription Creation** + +1. In order to subscribe to service switch information reporting, the service consumer shall send the HTTP POST request message to the PIN Server targeting the URI of the "Service Switch Information Subscriptions" collection resource, with the request body including the ServiceSwitchInfo data structure. +- 2a. Upon success, the PIN Server shall respond with an HTTP "201 Created" status code with the response body containing a representation of the created "Individual Service Switch Information Subscription" resource within the ServiceSwitchInfo data structure. +- 2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.2.7. + +#### 5.3.2.3 PIN\_ASServiceSwitch\_Notify + +##### 5.3.2.3.1 General + +This service operation is used by the PIN server to notify a previously subscribed service consumer on: + +- the service switch information. + +The following procedures are supported by the "PIN\_ASServiceSwitch\_Notify" service operation: + +- Service Switch Information Notification. + +##### 5.3.2.3.2 Service Switch Information Notification + +![Sequence diagram for Service Switch Information Notification. The PIN Server sends a POST {notifUri} (ServiceSwitchInfoNotification) to the Service Consumer. The Service Consumer responds with 2a. '204 No Content' or 2b. 4xx/5xx.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +sequenceDiagram + participant PIN Server + participant Service Consumer + Note left of PIN Server: 1. POST {notifUri} (ServiceSwitchInfoNotification) + PIN Server->>Service Consumer: 1. POST {notifUri} (ServiceSwitchInfoNotification) + Note right of Service Consumer: 2a. "204 No Content" +2b. 4xx/5xx + Service Consumer-->>PIN Server: 2a. "204 No Content" +2b. 4xx/5xx + +``` + +Sequence diagram for Service Switch Information Notification. The PIN Server sends a POST {notifUri} (ServiceSwitchInfoNotification) to the Service Consumer. The Service Consumer responds with 2a. '204 No Content' or 2b. 4xx/5xx. + +**Figure 5.3.2.3.2-1: Procedure for Service Switch Information Notification** + +1. In order to notify a previously subscribed service consumer on the service switch information, the service consumer shall send the HTTP POST request to the service consumer with the request URI set to "{notifUri}", where the "notifUri" variable is set to the value received from the service consumer during the creation/update of the corresponding Service Switch Information Subscription using the procedures defined in clauses 5.3.2.2 and 5.3.2.4, with the request body including the ServiceSwitchInfoNotification data structure. +- 2a. Upon success, the service consumer shall respond to the PIN server with "204 No Content" status code to acknowledge the reception of the notification. +- 2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.2.7. + +#### 5.3.2.4 PIN\_ASServiceSwitch\_Update + +##### 5.3.2.4.1 General + +This service operation is used by the service consumer to update a service switch subscription with the PIN Server. + +##### 5.3.2.4.2 Service Switch Information Update + +![Sequence diagram for Service Switch Information Update. The Service Consumer sends a PUT/PATCH .../subscriptions/{subscriptionsId} (ServiceSwitchInfo or ServiceSwitchInfoPatch) to the PIN Server. The PIN Server responds with 2a. 200 OK (ServiceSwitchInfo) or 204 No Content, or 2b. 4xx/5xx.](704082cc3e11776bda29595c76411362_img.jpg) + +``` + +sequenceDiagram + participant Service Consumer + participant PIN Server + Note left of Service Consumer: 1. PUT/PATCH .../subscriptions/{subscriptionsId} +(ServiceSwitchInfo or ServiceSwitchInfoPatch) + Service Consumer->>PIN Server: 1. PUT/PATCH .../subscriptions/{subscriptionsId} +(ServiceSwitchInfo or ServiceSwitchInfoPatch) + Note right of PIN Server: 2a. 200 OK (ServiceSwitchInfo) or 204 No Content +2b. 4xx/5xx + PIN Server-->>Service Consumer: 2a. 200 OK (ServiceSwitchInfo) or 204 No Content +2b. 4xx/5xx + +``` + +Sequence diagram for Service Switch Information Update. The Service Consumer sends a PUT/PATCH .../subscriptions/{subscriptionsId} (ServiceSwitchInfo or ServiceSwitchInfoPatch) to the PIN Server. The PIN Server responds with 2a. 200 OK (ServiceSwitchInfo) or 204 No Content, or 2b. 4xx/5xx. + +**Figure 5.3.2.4.2-1: Procedure for the Service Switch Information Update** + +1. In order to update an existing service switch information subscription, the service consumer shall send an HTTP PUT/PATCH request to the PIN Server, targeting the URI of the corresponding "Individual Service Switch Information Subscription" resource, with the request body including: + - the updated representation of the resource within the ServiceSwitchInfo data structure, in case the HTTP PUT method is used; or + - the requested modifications to the resource within the ServiceSwitchInfoPatch data structure, in case the HTTP PATCH method is used. + +NOTE: An alternative service consumer (i.e. other than the one that requested the creation of the targeted resource) can initiate this request. + +- 2a. Upon success, the PIN Server shall update the targeted "Individual Service Switch Information Subscription" resource accordingly and respond with either: + +- an HTTP "200 OK" status code with the response body containing a representation of the updated "Individual Service Switch Information Subscription" resource within the ServiceSwitchInfo data structure; or +- an HTTP "204 No Content" status code. + +2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.2.7. + +#### 5.3.2.5 PIN\_ASServiceSwitch\_Unsubscribe + +##### 5.3.2.5.1 General + +This service operation is used by the service consumer to remove its subscription at PIN server, for reporting of service switch information. + +##### 5.3.2.5.2 Unsubscribing the Service Switch Information + +![Sequence diagram showing the procedure for unsubscribing the Service Switch Information. A Service Consumer sends a DELETE request to a PIN Server. The PIN Server responds with either a 204 No Content (success) or a 4xx/5xx status code (failure).](a7c51c18111139f9aca2805114108565_img.jpg) + +``` +sequenceDiagram + participant Service Consumer + participant PIN Server + Note left of Service Consumer: + Service Consumer->>PIN Server: 1. DELETE .../subscriptions/{subscriptionId} + Note right of PIN Server: + PIN Server-->>Service Consumer: 2a. "204 No Content" + Note right of PIN Server: + PIN Server-->>Service Consumer: 2b. 4xx/5xx +``` + +Sequence diagram showing the procedure for unsubscribing the Service Switch Information. A Service Consumer sends a DELETE request to a PIN Server. The PIN Server responds with either a 204 No Content (success) or a 4xx/5xx status code (failure). + +**Figure 5.3.2.5.2-1: Procedure for Unsubscribing the Service Switch Information** + +1. In order to request the deletion of an existing service switch information subscription, the service consumer shall send the HTTP DELETE request message to the PIN Server targeting the "Individual Service Switch Information Subscription" collection resource. +- 2a. Upon success, the PIN Server shall respond with an HTTP "204 No content" status code. +- 2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.2.7. + +## 5.4 PIN\_ASServiceContinuity Service + +### 5.4.1 Service Description + +The PIN\_ASServiceContinuity service exposed by the PIN Server enables a service consumer to: + +- create/update/delete a Service Continuity Information Subscription; and +- receive Service Continuity Information Notifications. + +### 5.4.2 Service Operations + +#### 5.4.2.1 Introduction + +The service operation defined for PIN\_ASServiceContinuity API is shown in the table 5.4.2.1-1. + +**Table 5.4.2.1-1: Operations of the PIN\_ASServiceContinuity API** + +| Service operation name | Description | Initiated by | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------|--------------| +| PIN_ASServiceContinuity_Subscribe | This service operation enables a service consumer to create/update/delete a Service Continuity Information Subscription. | e.g., PAS | +| PIN_ASServiceContinuity_Notify | This service operation enables a service consumer to receive Service Continuity Information Notifications.. | PIN server | + +#### 5.4.2.2 PIN\_ASServiceContinuity\_Subscribe + +##### 5.4.2.2.1 General + +This service operation is used by the service consumer to subscribe to PIN server, for reporting of service continuity information. + +##### 5.4.2.2.2 Service Continuity Information Subscription Creation + +![Sequence diagram showing the procedure for Continuity Information Subscription Creation. A Service Consumer sends a POST request to a PIN Server. The PIN Server responds with a 201 Created status and the ServiceContinuityInfo data structure, or an error status code (4xx/5xx).](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +``` + +sequenceDiagram + participant Service Consumer + participant PIN Server + Note right of Service Consumer: 1. POST .../subscriptions (ServiceContinuityInfo) + Service Consumer->>PIN Server: Request + Note left of PIN Server: 2a. 201 Created (ServiceContinuityInfo) +2b. 4xx/5xx + PIN Server-->>Service Consumer: Response + +``` + +Sequence diagram showing the procedure for Continuity Information Subscription Creation. A Service Consumer sends a POST request to a PIN Server. The PIN Server responds with a 201 Created status and the ServiceContinuityInfo data structure, or an error status code (4xx/5xx). + +**Figure 5.4.2.2.2-1: Procedure for Continuity Information Subscription Creation** + +1. In order to subscribe to service continuity information, the service consumer shall send the HTTP POST request to the PIN Server targeting the URI of the "Service Continuity Information Subscriptions" collection resource, with the request body including the ServiceContinuityInfo data structure. +- 2a. Upon success, the PIN Server shall respond with an HTTP "201 Created" status code with the response body containing a representation of the created "Individual Service Continuity Information Subscription" resource within the ServiceContinuityInfo data structure. +- 2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.3.7. + +#### 5.4.2.3 PIN\_ASServiceContinuity\_Notify + +##### 5.4.2.3.1 General + +This service operation is used by the PIN server to notify the service consumer about the service continuity information. + +##### 5.4.2.3.2 Service Continuity Information Notification + +![Sequence diagram for Service Continuity Information Notification](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` +sequenceDiagram + participant Service Consumer + participant PIN Server + Note right of Service Consumer: 1. POST {notifUri} (ServiceContinuityInfoNotification) + Service Consumer->>PIN Server: 1. POST {notifUri} (ServiceContinuityInfoNotification) + Note left of PIN Server: 2a. 204 No Content (ServiceContinuityInfoNotification) +2b. 4xx/5xx + PIN Server-->>Service Consumer: 2a. 204 No Content (ServiceContinuityInfoNotification) +2b. 4xx/5xx +``` + +Sequence diagram for Service Continuity Information Notification + +**Figure 5.4.2.3.2-1: Procedure for Service Continuity Information Notification** + +1. In order to notify a previously subscribed service continuity information, the service consumer shall send the HTTP POST request to the service consumer with the request URI set to "{notifUri}", where the "notifUri" variable is set to the value received from the service consumer during the creation/update of the corresponding Service Continuity Information Subscription using the procedures defined in clauses 5.4.2.2 and 5.4.2.4, with the request body including the ServiceContinuityInfoNotification data structure. +- 2a. Upon success, the service consumer shall respond to the PIN server with "204 No Content" code to acknowledge the reception of the notification. +- 2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.3.7. + +#### 5.4.2.4 PIN\_ASServiceContinuity\_Update + +##### 5.4.2.4.1 General + +This service operation is used by the service consumer to update a service continuity subscription with the PIN Server. + +##### 5.4.2.4.2 Service Continuity Information Update + +![Sequence diagram for Service Continuity Information Update](b0d4609bc46c2d88a8318706bb5321f7_img.jpg) + +``` +sequenceDiagram + participant Service Consumer + participant PIN Server + Note right of Service Consumer: 1. PUT/PATCH .../subscriptions/{subscriptionsId} +(ServiceContinuityInfo or ServiceContinuityInfoPatch) + Service Consumer->>PIN Server: 1. PUT/PATCH .../subscriptions/{subscriptionsId} +(ServiceContinuityInfo or ServiceContinuityInfoPatch) + Note left of PIN Server: 2a. 200 OK (ServiceContinuityInfo) or 204 No Content +2b. 4xx/5xx + PIN Server-->>Service Consumer: 2a. 200 OK (ServiceContinuityInfo) or 204 No Content +2b. 4xx/5xx +``` + +Sequence diagram for Service Continuity Information Update + +**Figure 5.4.2.4.2-1: Procedure for the Service Continuity Information Update** + +1. In order to update an existing service continuity information subscription, the service consumer shall send an HTTP PUT/PATCH request to the PIN Server, targeting the URI of the corresponding "Individual Service Continuity Information Subscription" resource, with the request body including either: + - the updated representation of the resource within the ServiceContinuityInfo data structure, in case the HTTP PUT method is used; or + - the requested modifications to the resource within the ServiceContinuityInfoPatch data structure, in case the HTTP PATCH method is used. + +NOTE: An alternative service consumer (i.e. other than the one that requested the creation of the targeted resource) can initiate this request. + +2a. Upon success, the PIN Server shall update the targeted "Individual Service Continuity Information Subscription" resource accordingly and respond with either: + +- an HTTP "200 OK" status code with the response body containing a representation of the updated "Individual Service Continuity Information Subscription" resource within the ServiceContinuityInfo data structure; or +- an HTTP "204 No Content" status code. + +2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.3.7. + +#### 5.4.2.5 PIN\_ASServiceContinuity\_Unsubscribe + +##### 5.4.2.5.1 General + +This service operation is used by the service consumer to remove its subscription at PIN server, for reporting of service continuity information. + +##### 5.4.2.5.2 Unsubscribing the Service Continuity Information + +![Sequence diagram showing the procedure for unsubscribing the Service Continuity Information. The Service Consumer sends a DELETE request to the PIN Server. The PIN Server responds with either a 204 No Content status code (2a) or an error status code (2b, 4xx/5xx).](e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg) + +``` + +sequenceDiagram + participant Service Consumer + participant PIN Server + Note left of Service Consumer: Service Consumer + Service Consumer->>PIN Server: 1. DELETE .../subscriptions/{subscriptionsId} + Note right of PIN Server: PIN Server + PIN Server-->>Service Consumer: 2a. "204 No Content" +2b. 4xx/5xx + +``` + +Sequence diagram showing the procedure for unsubscribing the Service Continuity Information. The Service Consumer sends a DELETE request to the PIN Server. The PIN Server responds with either a 204 No Content status code (2a) or an error status code (2b, 4xx/5xx). + +Figure 5.4.2.5.2-1: Procedure for Unsubscribing the Service Continuity Information + +1. In order to request the deletion of an existing service continuity information subscription, the service consumer shall send the HTTP DELETE request to the PIN Server targeting the corresponding "Individual Service Continuity Information Subscription" resource. + +2a. Upon success, the PIN Server shall respond with an HTTP "204 No content" status code. + +2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.3.7. + +# 6 API Definitions + +## 6.1 PIN\_ASRegistration Service API + +### 6.1.1 Introduction + +The PIN\_ASRegistration service shall use the PIN\_ASRegistration service API. + +The API URI of the PIN\_ASRegistration service API shall be: + +{apiRoot}// + +The request URIs used in HTTP requests shall have the Resource URI structure defined in clause 5.2.4 of 3GPP TS 29.122 [2], i.e.: + +{apiRoot}/// + +with the following components: + +- The {apiRoot} shall be set as described in clause 5.2.4 of 3GPP TS 29.122 [2]. +- The shall be "pin-as-registration". +- The shall be "v1". +- The shall be set as described in clause 5.2.4 of 3GPP TS 29.122 [2]. + +NOTE: When 3GPP TS 29.122 [2] is referenced for the common protocol and interface aspects for API definition in the clauses under clause 5, the service producer (i.e. PIN Server) takes the role of the SCEF and the service consumer takes the role of the SCS/AS. + +### 6.1.2 Usage of HTTP + +The provisions of clause 5.2.2 of 3GPP TS 29.122 [2] shall apply for the PIN\_ASRegistration API. + +### 6.1.3 Resources + +#### 6.1.3.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 6.1.3.1-1 depicts the resource URIs structure for the PIN\_ASRegistration API. + +![Diagram showing the resource URI structure for the PIN_ASRegistration API. It starts with {apiRoot}/pin-as-registration/, which branches to /registrations, which in turn branches to /{registrationId}.](cf4ac1058c52bc3ca37737740afb7f2c_img.jpg) + +{apiRoot}/pin-as-registration/ + +``` + +graph TD + Root["{apiRoot}/pin-as-registration/"] --> Registrations["/registrations"] + Registrations --> RegistrationId["/{registrationId}"] + +``` + +Diagram showing the resource URI structure for the PIN\_ASRegistration API. It starts with {apiRoot}/pin-as-registration/, which branches to /registrations, which in turn branches to /{registrationId}. + +Figure 6.1.3.1-1: Resource URI structure of the PIN\_ASRegistration API + +Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods. + +Table 6.1.3.1-1: Resources and methods overview + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|-----------------------------|---------------------------------|---------------------------------|-------------------------------------------------------------------------------| +| PAS Registrations | /registrations | POST | Request the creation of a new PAS Registration. | +| Individual PAS Registration | /registrations/{registrationId} | GET | Retrieve an individual PAS registration resource. | +| | | PUT | Request the update of an existing Individual PAS Registration resource. | +| | | PATCH | Request the modification of an existing Individual PAS Registration resource. | +| | | DELETE | Request the deletion of an existing Individual PAS Registration resource. | + +#### 6.1.3.2 Resource: PAS Registrations + +##### 6.1.3.2.1 Description + +This resource represents all the PAS that are registered to the PIN server. + +##### 6.1.3.2.2 Resource Definition + +Resource URI: {apiRoot}/pin-as-registration//registrations + +This resource shall support the resource URI variables defined in table 6.1.3.2.2-1. + +**Table 6.1.3.2.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|---------|-----------|-------------------| +| apiRoot | string | See clause 6.1.1. | + +##### 6.1.3.2.3 Resource Standard Methods + +###### 6.1.3.2.3.1 POST + +The POST method allows an service consumer to request the creation of a new PAS Registration. + +This method shall support the URI query parameters specified in table 6.1.3.2.3.1-1. + +**Table 6.1.3.2.3.1-1: URI query parameters supported by the POST Request Body on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 6.1.3.2.3.1-2 and the response data structures and response codes specified in table 6.1.3.2.3.1-3. + +**Table 6.1.3.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------|---|-------------|---------------------------------------| +| PASRegistration | M | 1 | PAS registration request information. | + +**Table 6.1.3.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PASRegistration | M | 1 | 201
Created | Successful case. The PAS Registration is successfully created and a representation of the created "Individual PAS Registration " resource is returned.
.
The URI of the created resource shall be returned in the "Location" HTTP header. | +| NOTE: The mandatory HTTP error status code for the HTTP POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [2] also apply. | | | | | + +Table 6.1.3.2.3.1-4: Headers supported by the 201 response code on this resource + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/pin-as-registration//registrations/{registrationId} | + +##### 6.1.3.2.4 Resource Custom Operations + +None. + +#### 6.1.3.3 Resource: Individual PAS Registration + +##### 6.1.3.3.1 Description + +This resource represents an "Individual PAS Registration" managed by the PIN server. + +##### 6.1.3.3.2 Resource Definition + +Resource URI: {apiRoot}/pin-as-registration//registrations/{registrationId} + +This resource shall support the resource URI variables defined in the table 6.1.3.3.2-1. + +Table 6.1.3.3.2-1: Resource URI variables for this resource + +| Name | Data Type | Definition | +|----------------|-----------|--------------------------------------------------------------------------| +| apiRoot | string | See clause 6.1.1. | +| registrationId | string | Represents the identifier of the "Individual PAS Registration" resource. | + +##### 6.1.3.3.3 Resource Standard Methods + +###### 6.1.3.3.3.1 GET + +The HTTP GET method allows a service consumer to retrieves an existing "Individual PAS Registration" resource at the PIN server. + +This method shall support the URI query parameters specified in table 6.1.3.3.3.1-1. + +Table 6.1.3.3.3.1-1: URI query parameters supported by the GET method on this resource + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.1.3.3.3.1-2 and the response data structures and response codes specified in table 6.1.3.3.3.1-3. + +Table 6.1.3.3.3.1-2: Data structures supported by the GET Request Body on this resource + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 6.1.3.3.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PASRegistration | M | 1 | 200 OK | Successful case. The requested "Individual PAS Registration" resource is returned. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [6]. | + +NOTE: The mandatory HTTP error status codes for the HTTP GET method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.1.3.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.1.3.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +###### 6.1.3.3.3.2 PUT + +The HTTP PUT method allows a service consumer to request the update of an existing "Individual PAS Registration" resource at the PIN server. + +This method shall support the URI query parameters specified in the table 6.1.3.3.3.2-1. + +**Table 6.1.3.3.3.2-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.1.3.3.3.2-2 and the response data structures and response codes specified in table 6.1.3.3.3.2-3. + +**Table 6.1.3.3.3.2-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------|---|-------------|-----------------------------------------------------------------------------------------------| +| PASRegistration | M | 1 | Represents the updated representation of the existing "Individual PAS Registration" resource. | + +**Table 6.1.3.3.3.2-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PASRegistration | M | 1 | 200 OK | Successful case. The "Individual PAS Registration" resource is successfully updated and a representation of the updated resource shall be returned in the response body. | +| n/a | | | 204 No Content | Successful case. The "Individual PAS Registration" resource is successfully updated and no content is returned in the response body. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP PUT method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.1.3.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.1.3.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +###### 6.1.3.3.3.3 DELETE + +The HTTP DELETE method allows a service consumer to request the deletion of an existing "Individual PAS Registration" resource at the PIN server. + +This method shall support the URI query parameters specified in the table 6.1.3.3.3.3-1. + +**Table 6.1.3.3.3.3-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.1.3.3.3.3-2 and the response data structures and response codes specified in table 6.1.3.3.3.3-3. + +**Table 6.1.3.3.3.3-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 6.1.3.3.3.3-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful case. The targeted "Individual PAS Registration" resource is successfully deleted. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP DELETE method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.1.3.3.3.3-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.1.3.3.3.3-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +###### 6.1.3.3.3.4 PATCH + +The HTTP PATCH method allows a service consumer to request the modification of an existing "Individual PAS Registration" resource at the PIN server. + +This method shall support the URI query parameters specified in the table 6.1.3.3.3.4-1. + +**Table 6.1.3.3.3.4-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.1.3.3.3.4-2 and the response data structures and response codes specified in table 6.1.3.3.3.4-3. + +**Table 6.1.3.3.3.4-2: Data structures supported by the PATCH Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------|---|-------------|--------------------------------------------------------------------------------------------------------------| +| PASRegistrationPatch | M | 1 | Represents the parameters to request the modification of an existing "Individual PAS Registration" resource. | + +**Table 6.1.3.3.3.4-3: Data structures supported by the PATCH Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PASRegistration | M | 1 | 200 OK | Successful case. The "Individual PAS Registration" resource is successfully modified and a representation of the updated resource shall be returned in the response body. | +| n/a | | | 204 No Content | Successful case. The "Individual PAS Registration" resource is successfully updated and no content is returned in the response body. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [6]. | + +NOTE: The mandatory HTTP error status code for the HTTP PUT method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.1.3.3.3.4-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.1.3.3.3.4-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +##### 6.1.3.3.4 Resource Custom Operations + +None. + +### 6.1.4 Custom Operations without associated resources + +None. + +### 6.1.5 Notifications + +None. + +### 6.1.6 Data Model + +#### 6.1.6.1 General + +This clause specifies the application data model supported by the PIN\_ASRegistration API. + +Table 6.1.6.1-1 specifies the data types defined for the PIN\_ASRegistration API. + +**Table 6.1.6.1-1: PIN\_ASRegistration API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|----------------------|-----------------|-----------------------------------------------------------------------------|---------------| +| ConnectivityInfo | 6.1.6.2.3 | Contains the connectivity information used to communicate with the PAS. | | +| PASRegistration | 6.1.6.2.2 | Represents the PAS registration information. | | +| PASRegistrationPatch | 6.1.6.2.4 | Represents the requested modifications to the PAS registration information. | | + +Table 6.1.6.1-2 specifies data types re-used by the PIN\_ASRegistration API from other specifications, including a reference to their respective specifications, and when needed, a short description of their use within the PIN\_ASRegistration API. + +**Table 6.1.6.1-2: PIN\_ASRegistration API re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|---------------------------------------------------------------------------------------------------------------|---------------| +| DateTime | 3GPP TS 29.122 [2] | Used to capture the expiration time of PAS registration. | | +| DateTimeRm | 3GPP TS 29.571 [11] | Used to capture the expiration time of PAS registration patch. | | +| Fqdn | 3GPP TS 29.571 [11] | Used to express the Fully Qualified Domain Name of PAS end point. | | +| Ipv4Addr | 3GPP TS 29.122 [2] | Identifies the IPv4 address of the PAS. | | +| Ipv6Addr | 3GPP TS 29.122 [2] | Identifies the IPv6 address of the PAS. | | +| SupportedFeatures | 3GPP TS 29.571 [11] | Represents the list of supported feature(s) and used to negotiate the applicability of the optional features. | | +| Uri | 3GPP TS 29.122 [2] | Represents a URI. | | + +#### 6.1.6.2 Structured data types + +##### 6.1.6.2.1 Introduction + +This clause defines the structures to be used in resource representations. + +##### 6.1.6.2.2 Type: PASRegistration + +**Table 6.1.6.2.2-1: Definition of type PASRegistration** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| conInfo | ConnectivityInfo | M | 1 | Contains the connectivity information used to communicate with the PAS. | | +| passId | string | M | 1 | Identifies the PIN service that provided by the PAS. | | +| expTime | DateTime | O | 0..1 | Identifies the expiration time for the PAS registration. To maintain an active registration status, a registration update is required before the expiration time. If the expiration time is not present, then it indicates that the registration of PAS never expires. | | +| suppFeat | SupportedFeatures | C | 0..1 | Contains the list of supported features among the ones defined in clause 6.1.8.

This attribute shall be present only when feature negotiation needs to take place. | | + +##### 6.1.6.2.3 Type: ConnectivityInfo + +Table 6.1.6.2.3-1: Definition of type ConnectivityInfo + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------------------------------------------|-----------|---|-------------|-----------------------------------------|---------------| +| fqdn | Fqdn | O | 0..1 | Fully Qualified Domain Name of the PAS. | | +| ipv4Addr | Ipv4Addr | O | 0..1 | IPv4 address of the PAS. | | +| ipv6Addr | Ipv6Addr | O | 0..1 | IPv6 address of the PAS. | | +| uri | Uri | O | 0..1 | URI information of the PAS. | | +| NOTE: At least one of the attributes shall be provided. | | | | | | + +##### 6.1.6.2.4 Type: PASRegistrationPatch + +Table 6.1.6.2.4-1: Definition of type PASRegistrationPatch + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------------------------------------------|------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| passId | string | O | 0..1 | Identifies the PIN service that provided by the PAS. | | +| conInfo | ConnectivityInfo | O | 0..1 | Contains the connectivity information used to communicate with the PAS. | | +| expTime | DateTimeRm | O | 0..1 | Identifies the expiration time for the PAS registration. If the expiration time is not present, then it indicates that the registration of PAS never expires. | | +| NOTE: At least one of the attributes shall be provided. | | | | | | + +#### 6.1.6.3 Simple data types and enumerations + +##### 6.1.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +##### 6.1.6.3.2 Simple data types + +The simple data types defined in table 6.1.6.3.2-1 shall be supported. + +Table 6.1.6.3.2-1: Simple data types + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| n/a | | | | + +### 6.1.7 Error Handling + +#### 6.1.7.1 General + +For the PIN\_ASRegistration API, HTTP error responses shall be supported as specified in clause 5.2.6 of 3GPP TS 29.122 [2]. Protocol errors and application errors specified in clause 5.2.6 of 3GPP TS 29.122 [2] shall be supported for the HTTP status codes specified in table 5.2.6-1 of 3GPP TS 29.122 [2]. + +In addition, the requirements in the following clauses are applicable for the PIN\_ASRegistration API. + +#### 6.1.7.2 Protocol Errors + +No specific procedures for the PIN\_ASRegistration API are specified. + +#### 6.1.7.3 Application Errors + +The application errors defined for the PIN\_ASRegistration API are listed in Table 6.1.7.3-1. + +**Table 6.1.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|-------------------|------------------|-------------| +| n/a | | | + +### 6.1.8 Feature negotiation + +The optional features in table 6.1.8-1 are defined for the PIN\_ASRegistration API. They shall be negotiated using the extensibility mechanism defined in clause 5.2.7 of 3GPP TS 29.122 [2]. + +**Table 6.1.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| n/a | | | + +### 6.1.9 Security + +The provisions of clause 6 of 3GPP TS 29.122 [2] shall apply for the PIN\_ASRegistration API. + +## 6.2 PIN\_ASServiceSwitch API + +### 6.2.1 Introduction + +The PIN\_ASServiceSwitch service shall use the PIN\_ASServiceSwitch API. + +The API URI of the PIN\_ASServiceSwitch API shall be: + +**{apiRoot}//** + +The request URIs used in HTTP requests shall have the Resource URI structure defined in clause 5.2.4 of 3GPP TS 29.122 [2], i.e.: + +**{apiRoot}///** + +with the following components: + +- The {apiRoot} shall be set as described in clause 5.2.4 of 3GPP TS 29.122 [2]. +- The shall be "pin-as-serviceswitch". +- The shall be "v1". +- The shall be set as described in clause 5.2.4 of 3GPP TS 29.122 [2]. + +NOTE: When 3GPP TS 29.122 [2] is referenced for the common protocol and interface aspects for API definition in the clauses under clause 5, the service producer (i.e. PIN Server) takes the role of the SCEF and the service consumer takes the role of the SCS/AS. + +### 6.2.2 Usage of HTTP + +The provisions of clause 5.2.2 of 3GPP TS 29.122 [2] shall apply for the PIN\_ASServiceSwitch API. + +### 6.2.3 Resources + +#### 6.2.3.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 6.2.3.1-1 depicts the resource URIs structure for the PIN\_ASServiceSwitch API. + +{apiRoot}/pin-as-serviceswitch/ + +![Diagram showing the hierarchical structure of resource URIs. A line from the base URI '{apiRoot}/pin-as-serviceswitch/' branches to a box containing '/subscriptions'. From this box, another line branches to a box containing '/{subscriptionId}'.](f2ea0f64a770b22b902820457d262265_img.jpg) + +``` + +graph TD + Base["{apiRoot}/pin-as-serviceswitch/"] --> Subscriptions["/subscriptions"] + Subscriptions --> SubscriptionId["/{subscriptionId}"] + +``` + +Diagram showing the hierarchical structure of resource URIs. A line from the base URI '{apiRoot}/pin-as-serviceswitch/' branches to a box containing '/subscriptions'. From this box, another line branches to a box containing '/{subscriptionId}'. + +**Figure 6.2.3.1-1: Resource URI structure of the PIN\_ASServiceSwitch API** + +Table 6.2.3.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 6.2.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|----------------------------------------------------|---------------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------| +| Service Switch Information Subscriptions | /subscriptions | POST | Request the creation of a Service Switch Information Subscription. | +| Individual Service Switch Information Subscription | /subscriptions/{subscriptionId} | GET | Retrieve an existing "Individual Service Switch Information Subscription" resource. | +| | | PUT | Request the update of an existing "Individual Service Switch Information Subscription" resource. | +| | | PATCH | Request the modification of an existing "Individual Service Switch Information Subscription" resource. | +| | | DELETE | Request the deletion of an existing "Individual Service Switch Information Subscription" resource. | + +#### 6.2.3.2 Resource: Service Switch Information Subscriptions + +##### 6.2.3.2.1 Description + +This resource represents the collection of Service Switch Information Subscriptions managed by the PIN server. + +##### 6.2.3.2.2 Resource Definition + +Resource URI: {apiRoot}/pin-as-serviceswitch//subscriptions + +This resource shall support the resource URI variables defined in the table 6.2.3.2.2-1. + +**Table 6.2.3.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|---------|-----------|-------------------| +| apiRoot | string | See clause 6.2.1. | + +##### 6.2.3.2.3 Resource Standard Methods + +###### 6.2.3.2.3.1 POST + +The HTTP POST method allows a service consumer to request the creation of the Service Switch Information Subscription at the PIN server. + +This method shall support the URI query parameters specified in the table 6.2.3.2.3.1-1. + +**Table 6.2.3.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.2.3.2.3.1-2 and the response data structures and response codes specified in table 6.2.3.2.3.1-3. + +**Table 6.2.3.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------|---|-------------|-------------------------------------------------------------------------------------------------| +| ServiceSwitchInfo | M | 1 | Represents the parameters to request the creation of a Service Switch Information Subscription. | + +**Table 6.2.3.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|--------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceSwitchInfo | M | 1 | 201 Created |

Successful case. The Service Switch Information Subscription is successfully created and a representation of the created "Individual Service Switch Information Subscription" resource shall be returned.

The URI of the created resource shall be returned in the "Location" HTTP header.

| +| NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] also apply. | | | | | + +**Table 6.2.3.2.3.1-4: Headers supported by the 201 response code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure: {apiRoot}/pin-as-serviceswitch//subscriptions/{subscriptionId} | + +##### 6.2.3.2.4 Resource Custom Operations + +None. + +#### 6.2.3.3 Resource: Individual Service Switch Information Subscription + +##### 6.2.3.3.1 Description + +This resource represents the "Individual Service Switch Information Subscription" managed by the PIN server. + +##### 6.2.3.3.2 Resource Definition + +Resource URI: {apiRoot}/pin-as-serviceswitch//subscriptions/{subscriptionId} + +This resource shall support the resource URI variables defined in the table 6.2.3.3.2-1. + +**Table 6.2.3.3.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|----------------|-----------|-------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 6.2.1. | +| subscriptionId | string | Represents the identifier of the "Individual Service Switch Information Subscription" resource. | + +##### 6.2.3.3.3 Resource Standard Methods + +###### 6.2.3.3.3.1 GET + +The HTTP GET method allows a service consumer to retrieve an existing "Individual Service Switch Information Subscription" resource at PIN server. + +This method shall support the URI query parameters specified in the table 6.2.3.3.3.1-1. + +**Table 6.2.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.2.3.3.3.1-2 and the response data structures and response codes specified in table 6.2.3.3.3.1-3. + +**Table 6.2.3.3.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 6.2.3.3.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceSwitchInfo | M | 1 | 200 OK | Successful case. The requested "Individual Service Switch Information Subscription" resource shall be returned. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP GET method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.2.3.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.2.3.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +###### 6.2.3.3.3.2 PATCH + +The HTTP PUT method partially allows a service consumer to request the modification of an existing "Individual Service Switch Information Subscription" resource at the PIN server. + +This method shall support the URI query parameters specified in the table 6.2.3.3.3.2-1. + +**Table 6.2.3.3.3.2-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.2.3.3.3.2-2 and the response data structures and response codes specified in table 6.2.3.3.3.2-3. + +**Table 6.2.3.3.3.2-2: Data structures supported by the PATCH Request Body on this resource** + +| Data type | P | Cardinality | Description | +|------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------| +| ServiceSwitchInfoPatch | M | 1 | Request to parameters to request the modification of the "Individual Service Switch Information Subscription" resource. | + +**Table 6.2.3.3.3.2-3: Data structures supported by the PATCH Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceSwitchInfo | M | 1 | 200 OK | Successful case. The "Individual Service Switch Information Subscription" resource is successfully modified and a representation of the updated resource shall be returned in the response body. | +| n/a | | | 204 No Content | Successful case. The "Individual Service Switch Information Subscription" resource is successfully updated and no content is returned in the response body. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP PATCH method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.2.3.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.2.3.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +###### 6.2.3.3.3.3 PUT + +The HTTP PUT method allows a service consumer to request the update of an existing "Individual Service Switch Information Subscription" resource at the PIN server. + +This method shall support the URI query parameters specified in the table 6.2.3.3.3.3-1. + +**Table 6.2.3.3.3.3-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.2.3.3.3.3-2 and the response data structures and response codes specified in table 6.2.3.3.3.3-3. + +**Table 6.2.3.3.3.3-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------|---|-------------|-------------------------------------------------------------------------------------------------------------| +| ServiceSwitchInfo | M | 1 | Represents the updated representation of the "Individual Service Switch Information Subscription" resource. | + +**Table 6.2.3.3.3.3-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceSwitchInfo | M | 1 | 200 OK | Successful case. The "Individual Service Switch Information Subscription" resource is successfully updated and a representation of the updated resource shall be returned in the response body. | +| n/a | | | 204 No Content | Successful case. The "Individual Service Switch Information Subscription" resource is successfully updated and no content is returned in the response body. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP PUT method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.2.3.3.3.3-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.2.3.3.3.3-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +###### 6.2.3.3.3.4 DELETE + +The HTTP DELETE method allows a service consumer to request the deletion of an existing "Individual Service Switch Information Subscription" resource at the PIN server. + +This method shall support the URI query parameters specified in the table 6.2.3.3.3.4-1. + +**Table 6.2.3.3.3.4-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.2.3.3.3.4-2 and the response data structures and response codes specified in table 6.2.3.3.3.4-3. + +**Table 6.2.3.3.3.4-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +Table 6.2.3.3.3.4-3: Data structures supported by the DELETE Response Body on this resource + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful case. The targeted "Individual Service Switch Information Subscription" resource is successfully deleted. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status code for the DELETE method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] also apply. + +Table 6.2.3.3.3.4-4: Headers supported by the 307 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +Table 6.2.3.3.3.4-5: Headers supported by the 308 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +##### 6.2.3.3.4 Resource Custom Operations + +None. + +### 6.2.4 Custom Operations without associated resources + +None. + +### 6.2.5 Notifications + +#### 6.2.5.0 General + +Table 6.2.5.1-1: Notifications overview + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|-----------------------------------------|--------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------| +| Service Switch Information Notification | {notificationAddr} | POST | This service operation enables to notify a previously subscribed service consumer on Service Switch Information. | + +#### 6.2.5.1 Service Switch Information Notification + +##### 6.2.5.1.1 Description + +The Service Switch Information Notification is used by the PIN server to notify a previously subscribed service consumer on Service Switch Information. + +##### 6.2.5.1.2 Target URI + +The Callback URI {notificationAddr} shall be used with the callback URI variables defined in table 6.2.5.1.2-1. + +**Table 6.2.5.1.2-1: Callback URI variables** + +| Name | Data type | Definition | +|------------------|-----------|---------------------------------------------------------------------| +| notificationAddr | Uri | Represents the callback URI encoded as a string formatted as a URI. | + +##### 6.2.5.1.3 Standard Methods + +###### 6.2.5.1.3.1 POST + +This method shall support the request data structures specified in table 6.2.5.1.3.1-1 and the response data structures and response codes specified in table 6.2.5.1.3.1-2. + +**Table 6.2.5.1.3.1-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------------------|---|-------------|-------------------------------------------------------| +| ServiceSwitchInfoNotification | M | 1 | Represents a Service Switch Information Notification. | + +**Table 6.2.5.1.3.1-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful case. The Service Switch Information Notification is successfully received and acknowledged. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI representing the end point of an alternative EAS where the notification should be sent.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI representing the end point of an alternative EAS where the notification should be sent.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] also apply. + +**Table 6.2.5.1.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative PAS towards which the notification should be redirected. | + +**Table 6.2.5.1.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative PAS towards which the notification should be redirected. | + +### 6.2.6 Data Model + +#### 6.2.6.1 General + +This clause specifies the application data model supported by the API. + +Table 6.2.6.1-1 specifies the data types defined for the PIN\_ASServiceSwitch API. + +**Table 6.2.6.1-1: PIN\_ASServiceSwitch API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|-------------------------------|-----------------|--------------------------------------------------------------------------------|---------------| +| EventType | 6.2.6.3.2 | Represents the event type for service switch information subscription. | | +| ServiceSwitchInfo | 6.2.6.2.2 | Represents the service switch information subscription. | | +| ServiceSwitchInfoPatch | 6.2.6.2.3 | Used to request the partial update of service switch information subscription. | | +| ServiceSwitchInfoNotification | 6.2.6.2.4 | Service switch information for notification | | +| ServiceSwitchReportInfo | 6.2.6.2.5 | List of notifications that include the information of the service switch. | | + +Table 6.2.6.1-2 specifies data types re-used by the PIN\_ASServiceSwitch API from other specifications, including a reference to their respective specifications, and when needed, a short description of their use within the PIN\_ASServiceSwitch API. + +**Table 6.2.6.1-2: PIN\_ASServiceSwitch API re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|---------------------------------------------------------------------------------------------------------------|---------------| +| DateTime | 3GPP TS 29.122 [2] | Used to capture the expiration time of PAS subscription for service switch information reporting. | | +| FlowInfo | 3GPP TS 29.122 [2] | Represents IP flow information. | | +| SupportedFeatures | 3GPP TS 29.571 [11] | Represents the list of supported feature(s) and used to negotiate the applicability of the optional features. | | +| Uri | 3GPP TS 29.122 [2] | Represents a URI. | | + +#### 6.2.6.2 Structured data types + +##### 6.2.6.2.1 Introduction + +##### 6.2.6.2.2 Type: ServiceSwitchInfo + +**Table 6.2.6.2.2-1: Definition of type ServiceSwitchInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|--------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| subsEvent | EventType | M | 1 | Identifies the event type for which the subscriber is to be notified. | | +| notificationAddr | Uri | M | 1 | URI where the notification should be delivered to. This attribute shall be present in HTTP POST message to PIN server and maybe present in HTTP PUT request. | | +| pinId | string | M | 1 | Identifies a PIN. (see 3GPP TS 23.542 [10]).
Its encoding shall comply with the UE policy part type URSP as defined in clause 5.2 of 3GPP TS 24.526 [12]. | | +| expTime | DateTime | O | 0..1 | Indicates the expiration time of the subscription. To maintain an active registration status, a registration update is required before the expiration time. If the expiration time is not present, then it indicates that the PAS subscription never expires. | | +| suppFeat | Supported Features | C | 0..1 | Contains the list of supported features among the ones defined in clause 6.2.8.

This attribute shall be present only when feature negotiation needs to take place. | | + +##### 6.2.6.2.3 Type: ServiceSwitchInfoPatch + +**Table 6.2.6.2.3-1: Definition of type ServiceSwitchInfoPatch** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| expTime | DateTime | O | 0..1 | Indicates the proposed expiration time of the subscription. | | +| notificationAddr | Uri | O | 0..1 | Updated URI where the service switch information notification should be delivered to. | | +| pinId | string | O | 0..1 | Identifies a PIN. (see 3GPP TS 23.542 [10]).
Its encoding shall comply with the UE policy part type URSP as defined in clause 5.2 of 3GPP TS 24.526 [12]. | | +| subsEvent | EventType | O | 0..1 | Updated event type for which the subscriber is to be notified. | | + +##### 6.2.6.2.4 Type: ServiceSwitchInfoNotification + +Table 6.2.6.2.4-1: Definition of type ServiceSwitchInfoNotification + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-------------------------|---|-------------|----------------------------------------------------------------------------------------------------------|---------------| +| subsId | string | M | 1 | Contains the identifier of the subscription to which Service Switch Information Notification is related. | | +| repInfo | ServiceSwitchReportInfo | M | 1 | Contains the report of the service switch information. | | + +##### 6.2.6.2.5 Type: ServiceSwitchReportInfo + +Table 6.2.6.2.5-1: Definition of type ServiceSwitchReportInfo + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| acId | string | M | 1 | Identifies an application client identifier. | | +| pinId | string | M | 1 | Identifies a PIN. (see 3GPP TS 23.542 [10]). Its encoding shall comply with the UE policy part type URSP as defined in clause 5.2 of 3GPP TS 24.526 [12]. | | +| sessionId | string | M | 1 | Identifies an application session. | | +| targetPinId | string | M | 1 | Identifies the target PINE that the service is switched to. | | +| sessionDes | FlowInfo | O | 0..1 | Identifies the descriptor of application traffic flows | | + +#### 6.2.6.3 Simple data types and enumerations + +##### 6.2.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +##### 6.2.6.3.2 Enumeration: EventType + +The enumeration EventType represents the supported event type of service switch. + +Table 6.2.6.3.2-1: Enumeration EventType + +| Enumeration value | Description | Applicability | +|---------------------|-----------------------------------|---------------| +| SERVICE_SWITCH_INFO | Service switch happens in the PIN | | + +### 6.2.7 Error Handling + +#### 6.2.7.1 General + +For the PIN\_ASServiceSwitch API, HTTP error responses shall be supported as specified in clause 5.2.6 of 3GPP TS 29.122 [2]. Protocol errors and application errors specified in clause 5.2.6 of 3GPP TS 29.122 [2] shall be supported for the HTTP status codes specified in table 5.2.6-1 of 3GPP TS 29.122 [2]. + +In addition, the requirements in the following clauses are applicable for the PIN\_ASServiceSwitch API. + +#### 6.2.7.2 Protocol Errors + +No specific protocol errors for the PIN\_ASServiceSwitch API are specified. + +#### 6.2.7.3 Application Errors + +The application errors defined for the PIN\_ASServiceSwitch API are listed in Table 6.2.7.3-1. + +**Table 6.2.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +### 6.2.8 Feature negotiation + +The optional features in table 6.2.8-1 are defined for the PIN\_ASServiceSwitch API. They shall be negotiated using the extensibility mechanism defined in clause 5.2.7 of 3GPP TS 29.122 [2]. + +**Table 6.2.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| n/a | | | + +### 6.2.9 Security + +The provisions of clause 6 of 3GPP TS 29.122 [2] shall apply for the PIN\_ASServiceSwitch API. + +## 6.3 PIN\_ASServiceContinuity API + +### 6.3.1 Introduction + +The PIN\_ASServiceContinuity service shall use the PIN\_ASServiceContinuity API. + +The API URI of the PIN\_ASServiceContinuity API shall be: + +**{apiRoot}/** + +The request URIs used in HTTP requests shall have the Resource URI structure defined in clause 5.2.4 of 3GPP TS 29.122 [2], i.e.: + +**{apiRoot}//** + +with the following components: + +- The {apiRoot} shall be set as described in clause 5.2.4 of 3GPP TS 29.122 [2]. +- The shall be "pin-as-servicecontinuity". +- The shall be "v1". +- The shall be set as described in clause 5.2.4 of 3GPP TS 29.122 [2]. + +NOTE: When 3GPP TS 29.122 [2] is referenced for the common protocol and interface aspects for API definition in the clauses under clause 5, the service producer (i.e. PIN Server) takes the role of the SCEF and the service consumer takes the role of the SCS/AS. + +### 6.3.2 Usage of HTTP + +The provisions of clause 5.2.2 of 3GPP TS 29.122 [2] shall apply for the PIN\_ASServiceContinuity API. + +### 6.3.3 Resources + +#### 6.3.3.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 6.3.3.1-1 depicts the resource URIs structure for the PIN\_ASServiceContinuity API. + +![Diagram showing the hierarchy of resource URIs. The root URI is {apiRoot}/pin-as-servicecontinuity/. A line branches down to a box containing /subscriptions. From this box, another line branches down to a box containing /{subscriptionId}.](52e112d1ba42a3c660bf62a0fea927d3_img.jpg) + +{apiRoot}/pin-as-servicecontinuity/ + +``` + +graph TD + Root["{apiRoot}/pin-as-servicecontinuity/"] --> Subscriptions["/subscriptions"] + Subscriptions --> SubscriptionId["/{subscriptionId}"] + +``` + +Diagram showing the hierarchy of resource URIs. The root URI is {apiRoot}/pin-as-servicecontinuity/. A line branches down to a box containing /subscriptions. From this box, another line branches down to a box containing /{subscriptionId}. + +**Figure 6.3.3.1-1: Resource URI structure of the PIN\_ASServiceContinuity API** + +Table 6.3.3.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 6.3.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|--------------------------------------------------------|---------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------| +| Service Continuity Information Subscriptions | /subscriptions | POST | Request the creation of a Service Continuity Information Subscription. | +| Individual Service Continuity Information Subscription | /subscriptions/{subscriptionId} | GET | Retrieve the Individual service continuity information subscription information identified by subscriptionId. | +| | | PUT | Fully replace the individual service continuity information subscription identified by subscriptionId. | +| | | PATCH | Partially update the individual service continuity information subscription identified by subscriptionId. | +| | | DELETE | Remove the individual service continuity information subscription identified by subscriptionId. | + +#### 6.3.3.2 Resource: Service Continuity Information Subscriptions + +##### 6.3.3.2.1 Description + +This resource represents the collection of Service Continuity Information Subscriptions managed by the PIN server. + +##### 6.3.3.2.2 Resource Definition + +Resource URI: {apiRoot}/pin-as-servicecontinuity//subscriptions + +This resource shall support the resource URI variables defined in the table 6.3.3.2.2-1. + +**Table 6.3.3.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|---------|-----------|-------------------| +| apiRoot | string | See clause 6.3.1. | + +##### 6.3.3.2.3 Resource Standard Methods + +###### 6.3.3.2.3.1 POST + +The HTTP POST method allows a service consumer to request the creation of a Service Continuity Information Subscription at the PIN server. + +This method shall support the URI query parameters specified in the table 6.3.3.2.3.1-1. + +**Table 6.3.3.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.3.3.2.3.1-2 and the response data structures and response codes specified in table 6.3.3.2.3.1-3. + +**Table 6.3.3.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------|---|-------------|---------------------------------------------------------------------------------------------------------| +| ServiceContinuityInfo | M | 1 | Represents the parameters to request the creation of a new Service Continuity Information Subscription. | + +**Table 6.3.3.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|--------------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceContinuityInfo | M | 1 | 201 Created | Successful case. The Service Continuity Information Subscription is successfully created and a representation of the created "Individual Service Continuity Information Subscription" resource shall be returned.
The URI of the created resource shall be returned in the "Location" HTTP header. | +| NOTE: The mandatory HTTP error status codes for the HTTP POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. | | | | | + +**Table 6.3.3.2.3.1-4: Headers supported by the 201 response code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure: {apiRoot}/pin-as-servicecontinuity//subscriptions/{subscriptionId} | + +##### 6.3.3.2.4 Resource Custom Operations + +None. + +#### 6.3.3.3 Resource: Individual Service Continuity Information Subscription + +##### 6.3.3.3.1 Description + +This resource represents an Individual Service Continuity Information Subscription managed by the PIN server. + +##### 6.3.3.3.2 Resource Definition + +Resource URI: {apiRoot}/pin-as-servicecontinuity//subscriptions/{subscriptionId} + +This resource shall support the resource URI variables defined in the table 6.3.3.3.2-1. + +**Table 6.3.3.3.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|----------------|-----------|-----------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 6.3.1. | +| subscriptionId | string | Represents the identifier of the "Individual Service Continuity Information Subscription" resource. | + +##### 6.3.3.3.3 Resource Standard Methods + +###### 6.3.3.3.3.1 GET + +The HTTP GET method allows a service consumer to retrieve an existing "Individual Service Continuity Information Subscription" resource at PIN server. + +This method shall support the URI query parameters specified in the table 6.3.3.3.3.1-1. + +**Table 6.3.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.3.3.3.3.1-2 and the response data structures and response codes specified in table 6.3.3.3.3.1-3. + +**Table 6.3.3.3.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 6.3.3.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceContinuityInfo | M | 1 | 200 OK | Successful case. The requested "Individual Service Continuity Information Subscription" resource shall be returned. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP GET method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.3.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.3.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +##### 6.3.3.3.2 PATCH + +The HTTP PATCH method allows a service consumer to request the modification of an existing "Individual Service Continuity Information Subscription" resource at the PIN server. + +This method shall support the URI query parameters specified in the table 6.3.3.3.2-1. + +**Table 6.3.3.3.2-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.3.3.3.2-2 and the response data structures and response codes specified in table 6.3.3.3.2-3. + +**Table 6.3.3.3.2-2: Data structures supported by the PATCH Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------| +| ServiceContinuityInfoPatch | M | 1 | Represents the parameters to request the modification of the "Individual Service Continuity Information Subscription" resource. | + +**Table 6.3.3.3.3.2-3: Data structures supported by the PATCH Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceContinuityInfo | M | 1 | 200 OK | Successful case. The "Individual Service Continuity Information Subscription" resource is successfully modified and a representation of the updated resource shall be returned in the response body. | +| n/a | | | 204 No Content | Successful case. The "Individual Service Continuity Information Subscription" resource is successfully updated and no content is returned in the response body. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP PATCH method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.3.3.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.3.3.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +###### 6.3.3.3.3.3 PUT + +The HTTP PUT method allows a service consumer to request the update of an existing "Individual Service Continuity Information Subscription" resource at the PIN server. + +This method shall support the URI query parameters specified in the table 6.3.3.3.3.3-1. + +**Table 6.3.3.3.3.3-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.3.3.3.3.3-2 and the response data structures and response codes specified in table 6.3.3.3.3.3-3. + +**Table 6.3.3.3.3.3-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------| +| ServiceContinuityInfo | M | 1 | Represents the updated representation of the "Individual Service Continuity Information Subscription" resource. | + +**Table 6.3.3.3.3.3-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceContinuityInfo | M | 1 | 200 OK | Successful case. The "Individual Service Continuity Information Subscription" resource is successfully updated and a representation of the updated resource shall be returned in the response body. | +| n/a | | | 204 No Content | Successful case. The "Individual Service Continuity Information Subscription" resource is successfully updated and no content is returned in the response body. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP PUT method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.3.3.3.3.3-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +**Table 6.3.3.3.3.3-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +###### 6.3.3.3.3.4 DELETE + +The HTTP DELETE method allows a service consumer to request the deletion of an existing "Individual Service Continuity Information Subscription" resource at the PIN server. + +This method shall support the URI query parameters specified in the table 6.3.3.3.3.4-1. + +**Table 6.3.3.3.3.4-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 6.3.3.3.3.4-2 and the response data structures and response codes specified in table 6.3.3.3.3.4-3. + +Table 6.3.3.3.3.4-2: Data structures supported by the DELETE Request Body on this resource + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +Table 6.3.3.3.3.4-3: Data structures supported by the DELETE Response Body on this resource + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful case. The targeted "Individual Service Continuity Information Subscription" resource is successfully deleted. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PIN server.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP DELETE method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +Table 6.3.3.3.3.4-4: Headers supported by the 307 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +Table 6.3.3.3.3.4-5: Headers supported by the 308 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative PIN server. | + +##### 6.3.3.3.4 Resource Custom Operations + +None. + +### 6.3.4 Custom Operations without associated resources + +None. + +### 6.3.5 Notifications + +#### 6.3.5.0 General + +Table 6.3.5.1-1: Notifications overview + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|---------------------------------------------|--------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Service Continuity Information Notification | {notificationAddr} | POST | This service operation enables to notify a previously subscribed service consumer on service continuity information. | + +#### 6.3.5.1 Service Continuity Information Notification + +##### 6.3.5.1.1 Description + +The Service Continuity Information Notification is used by the PIN server to notify a previously subscribed service consumer on service continuity information. + +##### 6.3.5.1.2 Target URI + +The callback URI {notificationAddr} shall be used with the callback URI variables defined in table 6.3.5.1.2-1. + +**Table 6.3.5.1.2-1: Callback URI variables** + +| Name | Data type | Definition | +|------------------|-----------|---------------------------------------------------------------------| +| notificationAddr | Uri | Represents the callback URI encoded as a string formatted as a URI. | + +##### 6.3.5.1.3 Standard Methods + +###### 6.3.5.1.3.1 POST + +This method shall support the request data structures specified in table 6.3.5.1.3.1-1 and the response data structures and response codes specified in table 6.3.5.1.3.1-2. + +**Table 6.3.5.1.3.1-1: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------------------|---|-------------|-----------------------------------------------------------| +| ServiceContinuityInfoNotification | M | 1 | Represents a Service Continuity Information Notification. | + +**Table 6.3.5.1.3.1-2: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful case. The Service Continuity Information Notification is successfully received and acknowledged. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI representing the end point of an alternative EAS where the notification should be sent.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI representing the end point of an alternative EAS where the notification should be sent.

Redirection handling is described in clause 5.2.10 of TS 29.122 [2]. | + +NOTE: The mandatory HTTP error status codes for the HTTP POST method listed in Table 5.2.6-1 of 3GPP TS 29.122 [2] shall also apply. + +**Table 6.3.5.1.3.1-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative PAS towards which the notification should be redirected. | + +**Table 6.3.5.1.3.1-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative PAS towards which the notification should be redirected. | + +### 6.3.6 Data Model + +#### 6.3.6.1 General + +This clause specifies the application data model supported by the API. + +Table 6.3.6.1-1 specifies the data types defined for the PIN\_ASServiceContinuity API. + +**Table 6.3.6.1-1: PIN\_ASServiceContinuity API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|-----------------------------------|-----------------|------------------------------------------------------------------------------------|---------------| +| EventType | 6.3.6.3.2 | Represents the event type for service continuity information subscription. | | +| ServiceContinuityInfo | 6.3.6.2.2 | Represents the service continuity information subscription. | | +| ServiceContinuityInfoPatch | 6.3.6.2.3 | Used to request the partial update of service continuity information subscription. | | +| ServiceContinuityInfoNotification | 6.3.6.2.4 | Service continuity information for notification | | +| ServiceContinuityReportInfo | 6.3.6.2.5 | List of notifications that include the information of the service continuity. | | + +Table 6.3.6.1-2 specifies data types re-used by the PIN\_ASServiceContinuity API from other specifications, including a reference to their respective specifications, and when needed, a short description of their use within the PIN\_ASServiceContinuity API. + +**Table 6.3.6.1-2: PIN\_ASServiceContinuity API re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|---------------------------------------------------------------------------------------------------------------|---------------| +| DateTime | 3GPP TS 29.122 [2] | Used to capture the expiration time of PAS subscription for service continuity information reporting. | | +| FlowInfo | 3GPP TS 29.122 [2] | Represents IP flow information. | | +| SupportedFeatures | 3GPP TS 29.571 [11] | Represents the list of supported feature(s) and used to negotiate the applicability of the optional features. | | +| Uri | 3GPP TS 29.122 [2] | Represents a URI. | | + +#### 6.3.6.2 Structured data types + +##### 6.3.6.2.1 Introduction + +##### 6.3.6.2.2 Type: ServiceContinuityInfo + +**Table 6.3.6.2.2-1: Definition of type ServiceContinuityInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|-------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| subsEvent | EventType | M | 1 | Identifies the event type for which the subscriber is to be notified. | | +| notificationAddr | Uri | M | 1 | URI where the notification should be delivered to. This attribute shall be present in HTTP POST to PIN server and maybe present in HTTP PUT request. | | +| pinId | string | M | 1 | Identifies a PIN. (see 3GPP TS 23.542 [10]).
Its encoding shall comply with the UE policy part type URSP as defined in clause 5.2 of 3GPP TS 24.526 [12]. | | +| expTime | DateTime | O | 0..1 | Indicates the expiration time of the subscription. To maintain an active registration status, a registration update is required before the expiration time. If the expiration time is not present, then it indicates that the PAS subscription never expires. | | +| suppFeat | SupportedFeatures | C | 0..1 | Contains the list of supported features among the ones defined in clause 6.3.8.

This attribute shall be present only when feature negotiation needs to take place. | | + +##### 6.3.6.2.3 Type: ServiceContinuityInfoPatch + +**Table 6.3.6.2.3-1: Definition of type ServiceContinuityInfoPatch** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| expTime | DateTime | O | 0..1 | Indicates the proposed expiration time of the subscription. | | +| notificationAddr | Uri | O | 0..1 | Updated URI where the service continuity information notification should be delivered to. | | +| pinId | string | O | 0..1 | Identifies a PIN. (see 3GPP TS 23.542 [10]).
Its encoding shall comply with the UE policy part type URSP as defined in clause 5.2 of 3GPP TS 24.526 [12]. | | +| subsEvent | EventType | O | 0..1 | Updated event type for which the subscriber is to be notified. | | + +##### 6.3.6.2.4 Type: ServiceContinuityInfoNotification + +Table 6.3.6.2.4-1: Definition of type ServiceContinuityInfoNotification + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| subsId | string | M | 1 | Identifies the individual service continuity information subscription for which the service continuity information notification is delivered. | | +| repInfo | ServiceContinuityReportInfo | M | 1 | List of service continuity report information applicable to the subscription identifier. | | + +##### 6.3.6.2.5 Type: ServiceContinuityReportInfo + +Table 6.3.6.2.5-1: Definition of type ServiceContinuityReportInfo + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| acId | string | M | 1 | Identifies an application client identifier. | | +| pegcId | string | M | 1 | Identifies a PEGC. | | +| pinId | string | M | 1 | Identifies a PIN. (see 3GPP TS 23.542 [10]).
Its encoding shall comply with the UE policy part type URSP as defined in clause 5.2 of 3GPP TS 24.526 [12]. | | +| serviceId | string | M | 1 | Identifies a PIN service. | | +| sessionId | string | M | 1 | Identifies an application session. | | +| targetPinId | string | M | 1 | Identifies the target PINE. | | +| sessionDes | FlowInfo | O | 0..1 | Identifies the descriptor of application traffic flows | | + +#### 6.3.6.3 Simple data types and enumerations + +##### 6.3.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +##### 6.3.6.3.2 Enumeration: EventType + +The enumeration EventType represents the supported event type of service continuity. + +Table 6.3.6.3.2-1: Enumeration EventType + +| Enumeration value | Description | Applicability | +|-------------------------|---------------------------------------|---------------| +| SERVICE_CONTINUITY_INFO | Service continuity happens in the PIN | | + +### 6.3.7 Error Handling + +#### 6.3.7.1 General + +For the PIN\_ASServiceContinuity API, HTTP error responses shall be supported as specified in clause 5.2.6 of 3GPP TS 29.122 [2]. Protocol errors and application errors specified in clause 5.2.6 of 3GPP TS 29.122 [2] shall be supported for the HTTP status codes specified in table 5.2.6-1 of 3GPP TS 29.122 [2]. + +In addition, the requirements in the following clauses are applicable for the PIN\_ASServiceContinuity API. + +#### 6.3.7.2 Protocol Errors + +No specific protocol errors for the PIN\_ASServiceContinuity API are specified. + +#### 6.3.7.3 Application Errors + +The application errors defined for the PIN\_ASServiceContinuity API are listed in Table 6.3.7.3-1. + +**Table 6.3.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +### 6.3.8 Feature negotiation + +The optional features in table 6.3.8-1 are defined for the PIN\_ASServiceContinuity API. They shall be negotiated using the extensibility mechanism defined in clause 5.2.7 of 3GPP TS 29.122 [2]. + +**Table 6.3.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| n/a | | | + +### 6.3.9 Security + +The provisions of clause 6 of 3GPP TS 29.122 [2] shall apply for the PIN\_ASServiceContinuity API. + +# 7 Using Common API Framework + +## 7.1 General + +When CAPIF is used with a PIN Server service, the PIN Server shall support the following functionalities as defined in 3GPP TS 29.222 [7]: + +- the API exposing function and the related APIs over CAPIF-2/2e and CAPIF-3/3e reference points; +- the API publishing function and the related APIs over CAPIF-4/4e reference point; +- the API management function and the related APIs over CAPIF-5/5e reference point; and +- at least one of the security methods for authentication and authorization, and the related security mechanisms. + +In a centralized deployment as defined in 3GPP TS 23.222 [6], where the CAPIF core function and the API provider domain functions are co-located, the interactions between the CAPIF core function and the API provider domain functions may be independent of the CAPIF-3/3e, CAPIF-4/4e and CAPIF-5/5e reference points. + +When CAPIF is used with a PIN Server service, the PIN Server shall register all the northbound APIs features in the CAPIF Core Function. + +## 7.2 Security + +When CAPIF is used for external exposure, before invoking an API exposed by the PIN Server, the service API consumer acting as an API invoker shall negotiate the security method (PKI, TLS-PSK or OAuth 2.0) with the CAPIF core function and ensure that the PIN Server has enough credentials to authenticate the service API consumer, as defined in clauses 5.6.2.2 and 6.2.2.2 of 3GPP TS 29.222 [7]. + +If PKI or TLS-PSK is selected as the security method to be used between the service API consumer and the PIN Server, upon API invocation, the PIN Server shall retrieve the authorization information from the CAPIF core function as described in clause 5.6.2.4 of 3GPP TS 29.222 [7]. + +As indicated in 3GPP TS 33.122 [8], the access to the PIN Server APIs may be authorized by means of the OAuth 2.0 protocol (see IETF RFC 6749 [9]), using the "Client Credentials" authorization grant, where the CAPIF core function (see 3GPP TS 29.222 [7]) plays the role of the authorization server. + +NOTE 1: In this release, only "Client Credentials" authorization grant is supported. + +If OAuth 2.0 is selected as the security method to be used between the service API consumer and the PIN Server, the service API consumer shall, prior to consuming the services offered by the PIN Server APIs, obtain a "token" from the authorization server, by invoking the Obtain\_Authorization service operation as described in clause 5.6.2.3.2 of 3GPP TS 29.222 [7]. + +The PIN Server APIs do not define any scopes for OAuth 2.0 authorization. It is the PIN Server responsibility to check whether the service API consumer is authorized to use an API based on the provided "token". Once the PIN Server verifies the "token", it shall check whether the PIN Server identifier in the "token" matches its own published identifier, and whether the API name in the "token" matches its own published API name. If those checks are passed, the service API consumer has full authority to access any resource or operation provided by the invoked API. + +NOTE 2: For the aforementioned security methods, the PIN Server needs to apply admission control according to access control policies after performing the authorization checks. + +# --- Annex A (normative): OpenAPI specification + +## A.1 General + +This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format. + +This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s). + +NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5.3.1 of 3GPP TS 29.501 [5] and clause 5B of 3GPP TR 21.900 [7]). + +## --- A.2 PIN\_ASRegistration API + +``` +openapi: 3.0.0 + +info: + title: PIN Server PAS Registration Service + version: 1.0.0 + description: | + PIN Server PAS Registration Service. + © 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: > + 3GPP TS 29.583 V18.1.0; Application layer support for Personal IoT Network (PINAPP); + Personal IoT Network (PIN) Server Services; Stage 3. + url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.583/ + +servers: + - url: '{apiRoot}/pin-as-registration/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 6.1 of 3GPP TS 29.583. + +security: + - {} + - oAuth2ClientCredentials: [] + +paths: + /registrations: + post: + summary: Create a new PAS Registration + operationId: CreatePASRegistration + tags: + - PAS Registrations (Collection) + description: Register a new PAS at the PIN Server. + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/PASRegistration' + responses: + '201': + description: PAS information is registered successfully at PIN server. + content: +``` + +``` + application/json: + schema: + $ref: '#/components/schemas/PASRegistration' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/registrations/{registrationId}: + parameters: + - name: registrationId + in: path + description: Registration Id. + required: true + schema: + type: string + + get: + summary: Get an Individual PAS Registration + operationId: GetIndPASReg + tags: + - Individual PAS Registration (Document) + description: Retrieve an Individual PAS registration resource. + responses: + '200': + description: OK (The PAS registration information at the PIN Server). + content: + application/json: + schema: + $ref: '#/components/schemas/PASRegistration' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + + put: +``` + +``` +summary: Fully update an Individual PAS Registration +operationId: UpdateIndPASReg +tags: + - Individual PAS Registration (Document) +requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/PASRegistration' +responses: + '200': + description: OK (The PAS registration information is updated successfully). + content: + application/json: + schema: + $ref: '#/components/schemas/PASRegistration' + '204': + description: No Content. The PAS registration information is updated successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Modify an Individual PAS Registration + operationId: ModifyIndPASReg + tags: + - Individual PAS Registration (Document) + requestBody: + description: Partial update an existing PAS registration resource. + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/PASRegistrationPatch' + responses: + '200': + description: > + The Individual PAS registration is successfully modified and + the updated registration information is returned in the response. + content: + application/json: + schema: + $ref: '#/components/schemas/PASRegistration' + '204': + description: No Content. The Individual PAS registration is successfully modified. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Delete an Individual PAS Registration + operationId: DeleteIndPASReg + tags: + - Individual PAS Registration (Document) + responses: + '204': + description: The individual PAS registration is deleted. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + +# +# STRUCTURED DATA TYPES +# + +PASRegistration: + type: object + description: Represents an PAS registration information. + properties: + conInfo: + $ref: '#/components/schemas/ConnectivityInfo' + expTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + passId: + type: string + description: Indentifies a PIN service + suppFeat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - conInfo + - passId + +``` + +``` +ConnectivityInfo: + type: object + description: Represents a connection information of PAS. + properties: + fqdn: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Fqdn' + ipv4Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv4Addr' + ipv6Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6Addr' + uri: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + anyOf: + - required: [uri] + - required: [fqdn] + - required: [ipv4Addr] + - required: [ipv6Addr] + +PASRegistrationPatch: + type: object + description: Represents partial update request of individual PAS registration information. + properties: + conInfo: + $ref: '#/components/schemas/ConnectivityInfo' + expTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTimeRm' + passId: + type: string + description: Identifies a PIN service provided by PAS. + anyOf: + - required: [conInfo] + - required: [expTime] + - required: [passId] +``` + +## A.3 PIN\_ASServiceSwitch API + +openapi: 3.0.0 + +``` +info: + title: PIN Server Service Switch Information Service + version: 1.0.0 + description: | + PIN Server Service Switch Information Service. + © 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: > + 3GPP TS 29.583 V18.1.0; Application layer support for Personal IoT Network (PINAPP); + Personal IoT Network (PIN) Server Services; Stage 3. + url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.583/ + +servers: + - url: '{apiRoot}/pin-as-serviceswitch/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 6.2 of 3GPP TS 29.583. + +security: + - {} + - oAuth2ClientCredentials: [] + +paths: + /subscriptions: + post: + summary: Creates a new Individual Service Switch Information Subscriptions resource + operationId: CreateServiceSwitchInfo + tags: + - Service Switch Information Subscriptions (Collection) + description: Create a Subscription for reporting service switch information to PAS. + requestBody: + required: true + content: +``` + +``` + application/json: + schema: + $ref: '#/components/schemas/ServiceSwitchInfo' +responses: + '201': + description: > + Created. The Individual Service Switch Information Subscription resource is created + successfully + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSwitchInfo' + headers: + Location: + description: > + Contains the URI of the created Individual Service Switch Information + Subscription resource. + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +callbacks: + ServiceSwitchInfoNotification: + '{ $request.body#/notificationAddr }': + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSwitchInfoNotification' +responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/subscriptions/{subscriptionId}: + parameters: + - name: subscriptionId + in: path + description: Subscription Id. + required: true + schema: + type: string + + get: + summary: Read an Individual Service Switch Information Subscriptions resource + operationId: ReadIndServiceSwitchInfo + tags: + - Individual Service Switch Information Subscription (Document) + responses: + '200': + description: OK (Successfully get the Service Switch information subscription). + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSwitchInfo' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + + put: + summary: Request the fullyupdate an Individual Service Switch Information Subscriptions +resource. + operationId: UpdateIndServiceSwitchInfo + tags: + - Individual Service Switch Information Subscription (Document) + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSwitchInfo' + responses: + '200': + description: OK (Successfully modified The individual Service Switch information). + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSwitchInfo' + '204': + description: No Content. + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + +``` + +``` +$ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Modify an Individual Service Switch Information Subscriptions resource + operationId: ModifyIndServiceSwitchInfo + tags: + - Individual Service Switch Information Subscription (Document) + requestBody: + description: Partial update an existing Individual ServiceSwitch information. + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/ServiceSwitchInfoPatch' + responses: + '200': + description: > + OK (The Individual ServiceSwitch information Subscription is successfully modified + and the updated subscription information is returned in the response). + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSwitchInfo' + '204': + description: > + No Content (The individual Service Switch information subscription was modified + successfully). + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Delete an Individual Service Switch Information Subscriptions resource. + operationId: DeleteIndServiceSwitchInfo + tags: + - Individual Service Switch Information Subscription (Document) + responses: + '204': + description: The individual subscription is deleted. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' +``` + +``` +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +# Components + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + +# +# STRUCTURED DATA TYPES +# + +ServiceSwitchInfo: + type: object + description: Represents an Individual Service Switch Information Subscription. + properties: + subsEvent: + $ref: '#/components/schemas/EventType' + notificationAddr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + pinId: + type: string + description: Identifies a PIN. + expTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + suppFeat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - subsEvent + - notificationAddr + - pinId + +ServiceSwitchInfoPatch: + type: object + description: Represents the partial update of Individual Service Switch Information. + properties: + subsEvent: + $ref: '#/components/schemas/EventType' + notificationAddr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + pinId: + type: string + description: Identifies a PIN. + expTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + +ServiceSwitchInfoNotification: + type: object + description: Represent the service switch information for notification. + properties: + subsId: + type: string + description: > + Identifies the individual service switch information subscription for which + the service switch information notification is delivered. + repInfo: +``` + +``` + + $ref: '#/components/schemas/ServiceSwitchReportInfo' + required: + - subsId + - repInfo + +ServiceSwitchReportInfo: + type: object + description: List of notifications that include the information of the service switch. + properties: + acId: + type: string + description: Identifies an application client identifier. + pinId: + type: string + description: Identifies a PIN. + sessionId: + type: string + description: Identifies an application session. + targetPineId: + type: string + description: Identifies the PINE that the service is switched to. + sessionDes: + $ref: 'TS29122_CommonData.yaml#/components/schemas/FlowInfo' + required: + - acId + - pinId + - sessionId + - targetPineId + +# +# ENUMERATIONS +# + +EventType: + anyOf: + - type: string + enum: + - SERVICE_SWITCH_INFO + - type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration + and is not used to encode content defined in the present version of this API. + description: | + Indicates service switch type. + Possible values are: + - SERVICE_SWITCH_INFO: Indicates service switch type(s). + +``` + +## A.4 PIN\_ASServiceContinuity API + +openapi: 3.0.0 + +``` + +info: + title: PIN Server Service Continuity Service + version: 1.0.0 + description: | + PIN Server Service Continuity Information Service. + © 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: > + 3GPP TS 29.583 V18.1.0; Application layer support for Personal IoT Network (PINAPP); + Personal IoT Network (PIN) Server Services; Stage 3. + url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.583 + +servers: + - url: '{apiRoot}/pin-as-servicecontinuity/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 6.3.1 of 3GPP TS 29.583. + +security: + - {} + - oAuth2ClientCredentials: [] + +``` + +``` +paths: + /subscriptions: + post: + summary: Creates a new Individual Service Continuity Information Subscriptions resource + operationId: CreateServiceContinuityInfo + tags: + - Service Continuity Information Subscriptions (Collection) + description: Create a Subscription for reporting service continuity information to PAS. + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceContinuityInfo' + responses: + '201': + description: > + Created. The individual Service Continuity information subscription resource is + created successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceContinuityInfo' + headers: + Location: + description: 'Contains the URI of the newly created resource' + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + callbacks: + ServiceContinuityInfoNotification: + '{$request.body#/notificationAddr}': + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceContinuityInfoNotification' + responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': +``` + +``` + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/subscriptions/{subscriptionId}: + parameters: + - name: subscriptionId + in: path + description: Subscription Id. + required: true + schema: + type: string + + get: + summary: Read an Individual Service Continuity Information Subscriptions resource + operationId: ReadIndServiceContinuityInfo + tags: + - Individual Service Continuity Information Subscription (Document) + responses: + '200': + description: OK (Successfully get the Service Continuity information subscription). + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceContinuityInfo' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + + put: + summary: Update an Individual Service Continuity Information Subscriptions resource + operationId: UpdateIndServiceContinuityInfo + tags: + - Individual Service Continuity Information Subscription (Document) + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceContinuityInfo' + responses: + '200': + description: OK (Successfully modified The individual Service Continuity information). + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceContinuityInfo' + '204': + description: No Content. +``` + +``` +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + summary: Modify an Individual Service Continuity Information Subscriptions resource + operationId: ModifyIndServiceContinuityInfo + tags: + - Individual Service Continuity Information Subscription (Document) + requestBody: + description: Partial update an existing Individual ServiceContinuity information. + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/ServiceContinuityInfoPatch' + responses: + '200': + description: > + OK (The Individual ServiceContinuity information Subscription is successfully modified + and the updated subscription information is returned in the response). + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceContinuityInfo' + '204': + description: > + No Content (The individual Service Continuity information subscription was modified + successfully). + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + summary: Delete an Individual Service Continuity Information Subscriptions resource + operationId: DeleteIndServiceContinuityInfo +``` + +``` +tags: + - Individual Service Continuity Information Subscription (Document) +responses: + '204': + description: The individual subscription is deleted. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +# Components + +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{tokenUrl}' + scopes: {} + +schemas: + ServiceContinuityInfo: + type: object + description: Represents an Individual Service Continuity Information Subscription. + properties: + subsEvent: + $ref: '#/components/schemas/EventType' + notificationAddr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + pinId: + type: string + description: Identifies a PIN. + expTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + suppFeat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - subsEvent + - notificationAddr + - pinId + + ServiceContinuityInfoPatch: + type: object + description: Represents the partial update of Individual Service Continuity Information. + properties: + subsEvent: + $ref: '#/components/schemas/EventType' + notificationAddr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + pinId: + type: string + description: Identifies a PIN. + expTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + + ServiceContinuityInfoNotification: + type: object + description: Represent the service continuity information for notification. + properties: + subsId: + type: string +``` + +``` + + description: > + Identifies the individual service continuity information subscription for which + the service continuity information notification is delivered. + repInfo: + $ref: '#/components/schemas/ServiceContinuityReportInfo' + required: + - subsId + - repInfo + +ServiceContinuityReportInfo: + type: object + description: List of notifications that include the information of the service continuity. + properties: + acId: + type: string + description: Identifies an application client identifier. + pinId: + type: string + description: Identifies a PIN. + pegcId: + type: string + description: Identifies a PEGC. + serviceId: + type: string + description: Identifies a PIN service. + sessionId: + type: string + description: Identifies an application session. + targetPineId: + type: string + description: Identifies the PINE. + sessionDes: + $ref: 'TS29122_CommonData.yaml#/components/schemas/FlowInfo' + required: + - acId + - pinId + - pegcId + - serviceId + - sessionId + - targetPineId +``` + +# + +# # ENUMERATIONS + +# + +``` + +EventType: + anyOf: + - type: string + enum: + - SERVICE_CONTINUITY_INFO + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration and is not used to encode + content defined in the present version of this API. + description: | + Indicates service continuity happens in a PIN. + Possible values are: + - SERVICE_CONTINUITY_INFO: Indicates service continuity happens in a PIN. +``` + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | CT3#126 | | | | | TS skeleton for Application layer support for Personal IoT Network (PINAPP); Personal IoT Network (PIN) Server Services. | 0.0.0 | +| 2023-04 | CT3#127e | C3-231511 | | | | Inclusion of C3-231265 | 0.1.0 | +| 2023-09 | CT3#129 | C3-233739 | | | | Inclusion of C3-233576, C3-233688, C3-233689, C3-233690
Editorial correction from the rapporteur. | 0.2.0 | +| 2023-10 | CT3#130 | C3-234662 | | | | Inclusion of C3-234511, C3-234512, C3-234514, C3-234602, C3-234603
Editorial correction from the rapporteur. | 0.3.0 | +| 2023-11 | CT3#131 | C3-235465 | | | | Inclusion of C3-235521, C3-235522, C3-235546, C3-235552
Editorial correction from the rapporteur. | 0.4.0 | +| 2023-12 | CT#102 | CP-233291 | | | | Presentation to TSG CT for information. | 1.0.0 | +| 2024-03 | CT3#133 | C3-241655 | | | | Inclusion of C3-241545, C3-241546, C3-241547, C3-241575, C3-241592
Editorial correction from the rapporteur. | 1.1.0 | +| 2024-03 | CT#103 | CP-240216 | | | | Presentation to TSG CT for approval. | 2.0.0 | +| 2024-03 | CT#103 | CP-240216 | | | | Approved by TSG CT. | 18.0.0 | +| 2024-06 | CT#104 | CP-241110 | 0001 | 1 | F | Clarification on procedure name in overview clause | 18.1.0 | +| 2024-06 | CT#104 | CP-241110 | 0002 | 3 | F | Correction on Service Switch Information Update | 18.1.0 | +| 2024-06 | CT#104 | CP-241110 | 0003 | 1 | F | Several OpenAPI Corrections | 18.1.0 | +| 2024-06 | CT#104 | CP-241110 | 0004 | - | F | Corrections to the data structures in the response body. | 18.1.0 | +| 2024-06 | CT#104 | CP-241110 | 0005 | 2 | F | Corrections to PIN_ASRegistration data model and open API | 18.1.0 | +| 2024-06 | CT#104 | CP-241110 | 0006 | 1 | F | Corrections on PIN_ASRegistration API | 18.1.0 | +| 2024-06 | CT#104 | CP-241110 | 0007 | 1 | F | Corrections on PIN_ASServiceContinuity API | 18.1.0 | +| 2024-06 | CT#104 | CP-241110 | 0008 | 1 | F | Corrections on PIN_ASServiceSwitch API | 18.1.0 | +| 2024-06 | CT#104 | CP-241086 | 0009 | - | F | Update of info and externalDocs fields | 18.1.0 | +| 2024-07 | CT#104 | | | | | Correction to fix OpenAPI parsing errors | 18.1.1 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37104/raw.md b/marked/Rel-18/37_series/37104/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9cde0ba353a93e2e3fa9818c3fe9e40a0d7ae29e --- /dev/null +++ b/marked/Rel-18/37_series/37104/raw.md @@ -0,0 +1,3804 @@ + + +# 3GPP TS 37.104 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions, symbols and abbreviations ..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.2 Symbols..... | 15 | +| 3.3 Abbreviations ..... | 17 | +| 4 General..... | 19 | +| 4.1 Relation between the MSR specification and the single-RAT specifications..... | 19 | +| 4.2 Relationship between minimum requirements and test requirements..... | 19 | +| 4.3 Base station classes ..... | 19 | +| 4.4 Regional requirements..... | 20 | +| 4.5 Operating bands and Band Categories ..... | 21 | +| 4.5.1 Band category 1 aspects (BC1) ..... | 25 | +| 4.5.2 Band category 2 aspects (BC2) ..... | 25 | +| 4.5.3 Band category 3 aspects (BC3) ..... | 25 | +| 4.6 Channel arrangement..... | 25 | +| 4.6.1 Channel spacing..... | 25 | +| 4.6.1A CA Channel spacing ..... | 26 | +| 4.6.2 Channel raster..... | 27 | +| 4.6.3 Carrier frequencies and numbering ..... | 27 | +| 4.7 Requirements for contiguous and non-contiguous spectrum ..... | 28 | +| 4.8 Requirements for BS capable of multi-band operation..... | 28 | +| 5 Applicability of requirements ..... | 29 | +| 5.1 Band category 1..... | 29 | +| 5.2 Band category 2..... | 32 | +| 5.3 Band category 3..... | 35 | +| 5.4 Inclusion of requirements by reference ..... | 38 | +| 6 Transmitter characteristics ..... | 38 | +| 6.1 General ..... | 38 | +| 6.2 Base station output power ..... | 39 | +| 6.2.1 Minimum requirement..... | 39 | +| 6.2.2 Additional requirement (regional)..... | 39 | +| 6.2.3 E-UTRA minimum requirement for DL RS power..... | 40 | +| 6.2.4 UTRA FDD minimum requirement for primary CPICH power ..... | 40 | +| 6.2.4A UTRA FDD minimum requirement for secondary CPICH power..... | 40 | +| 6.2.5 UTRA TDD minimum requirement for primary CCPCH power..... | 40 | +| 6.2.6 NB-IoT minimum requirement for DL NRS power..... | 40 | +| 6.3 Output power dynamics ..... | 40 | +| 6.3.1 E-UTRA minimum requirement..... | 40 | +| 6.3.2 UTRA FDD minimum requirement ..... | 41 | +| 6.3.3 UTRA TDD minimum requirement ..... | 41 | +| 6.3.4 GSM/EDGE minimum requirement..... | 41 | +| 6.3.5 NB-IoT minimum requirement..... | 41 | +| 6.3.6 NR minimum requirement..... | 41 | +| 6.4 Transmit ON/OFF power ..... | 41 | +| 6.4.1 Transmitter OFF power ..... | 41 | +| 6.4.1.1 Minimum Requirement..... | 41 | +| 6.4.2 Transmitter transient period ..... | 41 | +| 6.4.2.1 Minimum requirements..... | 42 | +| 6.5 Transmitted signal quality..... | 43 | +| 6.5.1 Modulation quality ..... | 43 | +| 6.5.1.1 E-UTRA minimum requirement..... | 43 | + +| | | | +|------------|-------------------------------------------------------------------|----| +| 6.5.1.2 | UTRA FDD minimum requirement..... | 43 | +| 6.5.1.3 | UTRA TDD minimum requirement ..... | 43 | +| 6.5.1.4 | GSM/EDGE minimum requirement ..... | 43 | +| 6.5.1.5 | NB-IoT minimum requirement ..... | 43 | +| 6.5.1.6 | NR minimum requirement ..... | 43 | +| 6.5.2 | Frequency error ..... | 43 | +| 6.5.2.1 | E-UTRA minimum requirement ..... | 44 | +| 6.5.2.2 | UTRA FDD minimum requirement..... | 44 | +| 6.5.2.3 | UTRA TDD minimum requirement ..... | 44 | +| 6.5.2.4 | GSM/EDGE minimum requirement ..... | 44 | +| 6.5.2.5 | NB-IoT minimum requirement ..... | 44 | +| 6.5.2.6 | NR minimum requirement ..... | 44 | +| 6.5.3 | Time alignment error ..... | 44 | +| 6.5.3.1 | E-UTRA minimum Requirement..... | 44 | +| 6.5.3.2 | UTRA FDD minimum requirement..... | 44 | +| 6.5.3.3 | UTRA TDD minimum requirement ..... | 44 | +| 6.5.3.4 | NB-IoT minimum Requirement..... | 45 | +| 6.5.3.5 | NR minimum Requirement..... | 45 | +| 6.6 | Unwanted emissions..... | 45 | +| 6.6.1 | Transmitter spurious emissions ..... | 45 | +| 6.6.1.1 | Mandatory Requirements..... | 46 | +| 6.6.1.1.1 | Minimum requirement (Category A) ..... | 46 | +| 6.6.1.1.2 | Minimum requirement (Category B)..... | 46 | +| 6.6.1.1.3 | Additional minimum requirement for BC2 (Category B)..... | 46 | +| 6.6.1.2 | Protection of the BS receiver of own or different BS..... | 47 | +| 6.6.1.2.1 | Minimum Requirement ..... | 47 | +| 6.6.1.3 | Additional spurious emissions requirements ..... | 47 | +| 6.6.1.3.1 | Minimum Requirement ..... | 47 | +| 6.6.1.4 | Co-location with other base stations..... | 58 | +| 6.6.1.4.1 | Minimum Requirement ..... | 58 | +| 6.6.2 | Operating band unwanted emissions ..... | 64 | +| 6.6.2.1 | General minimum requirement for Band Categories 1 and 3 ..... | 64 | +| 6.6.2.2 | General minimum requirement for Band Category 2 ..... | 72 | +| 6.6.2.3 | GSM/EDGE single-RAT requirements ..... | 81 | +| 6.6.2.4 | Additional requirements ..... | 81 | +| 6.6.2.4.1 | Limits in FCC Title 47 ..... | 81 | +| 6.6.2.4.2 | Unsynchronized operation for BC3..... | 81 | +| 6.6.2.4.3 | Protection of DTT ..... | 81 | +| 6.6.2.4.4 | Void..... | 82 | +| 6.6.2.4.5 | Co-existence with RNSS/GPS services in North America ..... | 82 | +| 6.6.2.4.6 | Void..... | 82 | +| 6.6.2.4.7 | Additional band 32, 50, 51, 74, 75 and 76 unwanted emissions..... | 82 | +| 6.6.2.4.8 | Additional requirements for band 45 ..... | 84 | +| 6.6.2.4.9 | Additional requirements for band 48 ..... | 84 | +| 6.6.2.4.10 | Additional requirements for band 53 ..... | 84 | +| 6.6.3 | Occupied bandwidth..... | 85 | +| 6.6.3.1 | Minimum requirement ..... | 85 | +| 6.6.4 | Adjacent Channel Leakage Power Ratio (ACLR)..... | 85 | +| 6.6.4.1 | E-UTRA minimum requirement..... | 85 | +| 6.6.4.2 | UTRA FDD minimum requirement..... | 87 | +| 6.6.4.3 | UTRA TDD minimum requirement ..... | 87 | +| 6.6.4.4 | Cumulative ACLR requirement in non-contiguous spectrum ..... | 87 | +| 6.6.4.5 | NB-IoT minimum requirement ..... | 89 | +| 6.6.4.6 | NR minimum requirement ..... | 89 | +| 6.7 | Transmitter intermodulation..... | 91 | +| 6.7.1 | General minimum requirement..... | 91 | +| 6.7.2 | Additional minimum requirement (BC1 and BC2) ..... | 92 | +| 6.7.3 | Additional minimum requirement (BC3) ..... | 92 | +| 6.7.4 | Additional requirements ..... | 93 | +| 7 | Receiver characteristics..... | 93 | +| 7.1 | General ..... | 93 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------|------------| +| 7.2 | Reference sensitivity level ..... | 94 | +| 7.2.1 | E-UTRA minimum requirement..... | 94 | +| 7.2.2 | UTRA FDD minimum requirement ..... | 94 | +| 7.2.3 | UTRA TDD minimum requirement ..... | 94 | +| 7.2.4 | GSM/EDGE minimum requirement..... | 94 | +| 7.2.5 | NB-IoT minimum requirement..... | 94 | +| 7.2.6 | NR minimum requirement..... | 94 | +| 7.2.7 | Void ..... | 94 | +| 7.3 | Dynamic range ..... | 94 | +| 7.3.1 | E-UTRA minimum requirement..... | 94 | +| 7.3.2 | UTRA FDD minimum requirement ..... | 94 | +| 7.3.3 | UTRA TDD minimum requirement ..... | 95 | +| 7.3.4 | GSM/EDGE minimum requirement..... | 95 | +| 7.3.5 | NB-IoT minimum requirement..... | 95 | +| 7.3.6 | NR minimum requirement..... | 95 | +| 7.4 | In-band selectivity and blocking ..... | 95 | +| 7.4.1 | General blocking minimum requirement..... | 95 | +| 7.4.2 | General narrowband blocking minimum requirement..... | 97 | +| 7.4.3 | Additional Narrowband blocking minimum requirement for GSM/EDGE ..... | 98 | +| 7.4.4 | GSM/EDGE requirements for AM suppression..... | 98 | +| 7.4.5 | Additional BC3 blocking minimum requirement..... | 98 | +| 7.5 | Out-of-band blocking ..... | 99 | +| 7.5.1 | General minimum requirement..... | 99 | +| 7.5.2 | Co-location minimum requirement ..... | 100 | +| 7.6 | Receiver spurious emissions ..... | 105 | +| 7.6.1 | General minimum requirement..... | 105 | +| 7.6.2 | Additional minimum requirement for BC2 (Category B) ..... | 105 | +| 7.7 | Receiver intermodulation ..... | 106 | +| 7.7.1 | General intermodulation minimum requirement ..... | 106 | +| 7.7.2 | General narrowband intermodulation minimum requirement ..... | 109 | +| 7.7.3 | Additional narrowband intermodulation minimum requirement for GSM/EDGE ..... | 113 | +| 7.8 | In-channel selectivity ..... | 113 | +| 7.8.1 | E-UTRA minimum requirement..... | 113 | +| 7.8.2 | NR minimum requirement..... | 114 | +| 8 | Performance requirements ..... | 114 | +| 8.1 | E-UTRA minimum requirement ..... | 114 | +| 8.2 | UTRA FDD minimum requirement ..... | 114 | +| 8.3 | UTRA TDD minimum requirement..... | 114 | +| 8.4 | GSM/EDGE minimum requirement..... | 114 | +| 8.5 | NR minimum requirement ..... | 114 | +| 8.6 | NB-IoT minimum requirement ..... | 114 | +| Annex A (normative): | Characteristics of interfering signals ..... | 115 | +| A.1 | UTRA FDD interfering signal ..... | 115 | +| A.2 | UTRA TDD interfering signal ..... | 115 | +| A.3 | E-UTRA interfering signal..... | 115 | +| Annex B (normative): | Environmental requirements for the BS equipment ..... | 116 | +| Annex C (informative): | Change history ..... | 117 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document establishes the minimum RF characteristics of NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT Multi-Standard Radio (MSR) Base Station (BS). Requirements for multi-RAT and single-RAT operation of MSR BS are covered in the present document. The requirements in the present document for E-UTRA, UTRA and NB-IoT single-RAT operation of MSR BS are also applicable to E-UTRA, UTRA and NB-IoT multi-carrier capable single-RAT BS. Requirements for GSM BS that are only single-RAT capable in all supported operating bands are not covered. + +# 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.104, Technical Specification, "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Base Station (BS) radio transmission and reception (FDD)" +- [3] 3GPP TS 25.105. Technical Specification, "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Base Station (BS) radio transmission and reception (TDD)" +- [4] 3GPP TS 36.104, Technical Specification, "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception" +- [5] 3GPP TS 45.005, Technical Specification, "3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Radio transmission and reception" +- [6] ITU-R Recommendation SM.329-10, "Unwanted emissions in the spurious domain". +- [7] 3GPP TR 25.942, "Technical Report 3rd Generation Partnership Project; Technical Specification Group Radio Access Networks; Radio Frequency (RF) system scenarios" +- [8] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission. +- [9] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [10] 3GPP TS 37.141, Technical Specification, "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing" +- [11] IEC 60721-3-3: "Classification of environmental conditions - Part 3-3: Classification of groups of environmental parameters and their severities - Stationary use at weather protected locations". +- [12] IEC 60721-3-4: "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations". + +- [13] ETSI EN 300 019-1-3, *European Standard (Telecommunications series)*, "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-3: Classification of environmental conditions; Stationary use at weather protected locations" +- [14] ETSI EN 300 019-1-4, *European Standard (Telecommunications series)*, "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-4: Classification of environmental conditions; Stationary use at non-weather protected locations" +- [15] CEPT ECC Decision (13)03, "The harmonised use of the frequency band 1452-1492 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL)". +- [16] CEPT ECC Decision (17)06, "The harmonised use of the frequency bands 1427-1452 MHz and 1492-1518 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL)". +- [17] 3GPP TS 38.104: Technical Specification, "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Base Station (BS) radio transmission and reception". +- [18] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [19] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" + +# --- 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]. + +**Band category:** group of operating bands for which the same MSR scenarios apply + +**Base Station RF Bandwidth:** bandwidth in which a base station transmits and/or receives single or multiple carrier(s) and/or RATs simultaneously within a supported operating band + +NOTE: In single carrier operation, the Base Station RF Bandwidth is equal to the channel bandwidth. + +**Base Station RF Bandwidth edge:** frequency of one of the edges of the Base Station RF Bandwidth + +**Carrier:** modulated waveform conveying the NR, E-UTRA, UTRA or GSM/EDGE physical channels + +**Carrier aggregation:** aggregation of two or more NR or E-UTRA component carriers in order to support wider transmission bandwidths + +**Carrier aggregation band:** set of one or more operating bands across which multiple E-UTRA carriers are aggregated with a specific set of technical requirements. + +**Channel bandwidth:** RF bandwidth supporting a single NR, E-UTRA, UTRA or GSM/EDGE RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. + +NOTE: The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE: The term channel bandwidth is referred to as BS channel bandwidth in the NR specifications, since for NR the BS and UE may operate with differing bandwidths. + +**Contiguous carriers:** set of two or more carriers configured in a spectrum block where there are no RF requirements based on co-existence for un-coordinated operation within the spectrum block. + +**Carrier power:** power at the antenna connector in the channel bandwidth of the carrier averaged over at least one subframe for NR or E-UTRA, at least one slot for UTRA and the useful part of the burst for GSM/EDGE. + +**Configured carrier power:** target maximum power for a specific carrier for the operating mode set in the base station + +**Contiguous spectrum:** spectrum consisting of a contiguous block of spectrum with no sub-block gap(s). + +**Downlink operating band:** part of the operating band designated for downlink. + +**Highest Carrier:** carrier with the highest carrier centre frequency transmitted/received in the specified operating band(s). + +**Inter RF Bandwidth gap:** frequency gap between two consecutive Base Station RF Bandwidths that are placed within two supported operating bands. + +**Inter-band carrier aggregation:** carrier aggregation of NR or E-UTRA component carriers in different operating bands. + +NOTE: Carriers aggregated in each band can be contiguous or non-contiguous. + +**Inter-band gap:** The frequency gap between two supported consecutive operating bands. + +**Intra-band contiguous carrier aggregation:** contiguous NR or E-UTRA carriers aggregated in the same operating band. + +**Intra-band non-contiguous carrier aggregation:** non-contiguous NR or E-UTRA carriers aggregated in the same operating band. + +**Lowest Carrier:** carrier with the lowest carrier centre frequency transmitted/received in the specified operating band(s). + +**Lower Base Station RF Bandwidth edge:** frequency of the lower edge of the Base Station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements. + +**Lower sub-block edge:** frequency at the lower edge of one sub-block. + +NOTE: It is used as a frequency reference point for both transmitter and receiver requirements. + +**Maximum Base Station RF Bandwidth:** maximum RF bandwidth supported by a BS within each supported operating band. + +NOTE: The maximum Base Station RF Bandwidth for BS configured for contiguous and non-contiguous operation within each supported operating band is declared separately. + +**Maximum carrier output power:** carrier power available at the antenna connector for a specified reference condition. + +**Maximum RAT output power:** sum of the power of all carriers of the same RAT available at the antenna connector for a specified reference condition. + +**Maximum throughput:** maximum achievable throughput for a reference measurement channel. + +**Maximum total output power:** sum of the power of all carriers available at the antenna connector for a specified reference condition. + +**MB-MSR Base Station:** MSR Base Station characterized by the ability of its transmitter and/or receiver to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different operating band (which is not a sub-band or superseding-band of another supported operating band) than the other carrier(s). + +**Measurement bandwidth:** RF bandwidth in which an emission level is specified. + +**MSR Base station:** base station characterized by the ability of its receiver and transmitter to process two or more carriers in common active RF components simultaneously in a declared Base Station RF Bandwidth, where at least one carrier is of a different RAT than the other carrier(s). + +**Multi-band transmitter:** transmitter characterized by the ability to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different operating band (which is not a sub-band or superseding-band of another supported operating band) than the other carrier(s). + +**Multi-band receiver:** receiver characterized by the ability to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different operating band (which is not a sub-band or superseding-band of another supported operating band) than the other carrier(s). + +**Non-contiguous spectrum:** spectrum consisting of two or more sub-blocks separated by sub-block gap(s). + +**NB-IoT In-band operation:** NB-IoT is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier. + +**NB-IoT guard band operation:** NB-IoT is operating in guard band when it utilizes the unused resource block(s) within a E-UTRA carrier's guard-band. + +**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment. + +**NB-IoT operation in NR in-band:** NB-IoT is operating in-band when it is located within a NR transmission bandwidth configuration plus 15 kHz at each edge but not within the NR minimum guard band $GB_{\text{Channel}}$ . + +**NB-IoT operation in NR guard band:** NB-IoT is operating in guard band when it is located within a NR BS channel bandwidth but is not NB-IoT operation in NR in-band. + +**Occupied bandwidth:** width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage $\beta/2$ of the total mean power of a given emission. + +**Operating band:** frequency range in which NR, E-UTRA, UTRA or GSM/EDGE operates (paired or unpaired), that is defined with a specific set of technical requirements. + +NOTE: The operating band(s) for a BS is declared by the manufacturer. + +**Radio Bandwidth:** frequency difference between the upper edge of the highest used carrier and the lower edge of the lowest used carrier. + +**Rated total output power:** The total power level that the manufacturer has declared to be available at the antenna connector. + +**RRC filtered mean power:** The mean power of a UTRA carrier as measured through a root raised cosine filter with roll-off factor $\alpha$ and a bandwidth equal to the chip rate of the radio access mode. + +NOTE: The RRC filtered mean power of a perfectly modulated UTRA signal is 0.246 dB lower than the mean power of the same signal + +**Single-RAT operation:** operation of a base station in an operating band with only one RAT configured in that operating band. + +**Sub-band:** A sub-band of an operating band contains a part of the uplink and downlink frequency range of the operating band. + +**Sub-block:** one contiguous allocated block of spectrum for use by the same base station. + +NOTE: There may be multiple instances of sub-blocks within a Base Station RF Bandwidth. + +**Sub-block bandwidth:** RF bandwidth of one sub-block. + +**Sub-block gap:** frequency gap between two consecutive sub-blocks within a Base Station RF Bandwidth, where the RF requirements in the gap are based on co-existence for un-coordinated operation. + +**Superseding-band:** A superseding-band of an operating band includes the whole of the uplink and downlink frequency range of the operating band. + +**Synchronized operation:** operation of TDD in two different systems, where no simultaneous uplink and downlink occur. + +**Throughput:** number of payload bits successfully received per second for a reference measurement channel in a specified reference condition. + +**Transmission bandwidth:** RF bandwidth of an instantaneous E-UTRA or NR transmission from a UE or BS, measured in resource block units. + +**Transmitter ON period:** time period during which the BS transmitter is transmitting data and/or reference symbols + +**Transmitter OFF period:** time period during which the BS transmitter is not allowed to transmit + +**Transmitter transient period:** time period during which the transmitter is changing from the OFF period to the ON period or vice versa + +**Unsynchronized operation:** operation of TDD in two different systems, where the conditions for synchronized operation are not met. + +**Uplink operating band:** part of the operating band designated for uplink. + +**Upper Base Station RF Bandwidth edge:** frequency of the upper edge of the Base Station RF Bandwidth, used as a frequency reference point for transmitter and receiver requirements + +**Upper sub-block edge:** frequency at the upper edge of one sub-block. + +NOTE: It is used as a frequency reference point for both transmitter and receiver requirements. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\beta$ | Percentage of the mean transmitted power emitted outside the occupied bandwidth on the assigned channel | +| $BW_{\text{Channel}}$ | Channel bandwidth (for E-UTRA and NR) | +| $BW_{\text{Config}}$ | Transmission bandwidth configuration (for E-UTRA), where $BW_{\text{Config}} = N_{\text{RB}} \times 180 \text{ kHz}$ in the uplink and $BW_{\text{Config}} = 15 \text{ kHz} + N_{\text{RB}} \times 180 \text{ kHz}$ in the downlink. Transmission bandwidth configuration (for NR), where $BW_{\text{Config}} = N_{\text{RB}} \times \text{SCS} \times 12$ . | +| $BW_{\text{RF}}$ | Base Station RF Bandwidth, where $BW_{\text{RF}} = F_{\text{BW RF,high}} - F_{\text{BW RF,low}}$ | +| $BW_{\text{RF,max}}$ | Maximum Base Station RF Bandwidth | +| $DwPTS$ | Downlink part of the special subframe (for E-UTRA TDD operation) | +| $f$ | Frequency | +| $\Delta f$ | Separation between the Base Station RF Bandwidth edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency | +| $\Delta f_{\text{max}}$ | The largest value of $\Delta f$ used for defining the requirement | +| $\Delta f_{\text{OBUE}}$ | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| $\Delta f_{\text{OOB}}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $F_{\text{C}}$ | Carrier centre frequency | +| $F_{\text{filter}}$ | Filter centre frequency | +| $f\_offset$ | Separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter | +| $f\_offset_{\text{max}}$ | The maximum value of $f\_offset$ used for defining the requirement | +| $F_{\text{block,high}}$ | Upper sub-block edge, where $F_{\text{block,high}} = F_{\text{C,block,high}} + F_{\text{offset, RAT}}$ | +| $F_{\text{block,low}}$ | Lower sub-block edge, where $F_{\text{block,low}} = F_{\text{C,block,low}} - F_{\text{offset, RAT}}$ | +| $F_{\text{BW RF,high}}$ | Upper Base Station RF Bandwidth edge, where $F_{\text{BW RF,high}} = F_{\text{C,high}} + F_{\text{offset, RAT}}$ | +| $F_{\text{BW RF,low}}$ | Lower Base Station RF Bandwidth edge, where $F_{\text{BW RF,low}} = F_{\text{C,low}} - F_{\text{offset, RAT}}$ | +| $F_{\text{C band, high}}$ | Center frequency of the highest transmitted/received carrier in a band. | +| $F_{\text{C band, low}}$ | Center frequency of the lowest transmitted/received carrier in a band. | +| $F_{\text{C,block, high}}$ | Centre frequency of the highest transmitted/received carrier in a sub-block. | +| $F_{\text{C,block, low}}$ | Centre frequency of the lowest transmitted/received carrier in a sub-block. | +| $F_{\text{C,high}}$ | Centre frequency of the highest transmitted/received carrier. | +| $F_{\text{C,low}}$ | Centre frequency of the lowest transmitted/received carrier. | + +| | | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $F_{\text{offset, RAT}}$ | Frequency offset from the centre frequency of the highest transmitted/received carrier to the upper Base Station RF Bandwidth edge, sub-block edge or Inter-RF Bandwidth edge, or from the centre frequency of the lowest transmitted/received to the lower Base Station RF Bandwidth edge, sub-block edge or Inter-RF Bandwidth edge for a specific RAT. | +| $F_{\text{DL\_low}}$ | The lowest frequency of the downlink operating band | +| $F_{\text{DL\_high}}$ | The highest frequency of the downlink operating band | +| $F_{\text{UL\_low}}$ | The lowest frequency of the uplink operating band | +| $F_{\text{UL\_high}}$ | The highest frequency of the uplink operating band | +| $GB_{\text{Channel}}$ | Minimum guard band defined in subclause 5.3.3 of TS 38.104 [17] | +| $P_{\text{EM,N}}$ | Declared emission level for channel N | +| $P_{\text{EM,B32,B75,B76,ind}}$ | Declared emission level in Band 32, Band 75 and Band 76, ind=a, b, c | +| $P_{\text{EM,B32,ind}}$ | Declared emission level in Band 32, ind= d, e | +| $P_{\text{EM,B50,B74,B75,ind}}$ | Declared emission level for Band 50, Band 74 and Band 75, ind=a,b | +| $P_{\text{EM,B54,ind}}$ | Declared emission level in Band 54, ind=a,b,c,d,e,f | +| $P_{\text{max}}$ | Maximum total output power | +| $P_{\text{max,RAT}}$ | Maximum RAT output power | +| $P_{\text{max,c}}$ | Maximum carrier output power | +| $P_{\text{Rated,c}}$ | Rated carrier output power | +| $P_{\text{REFSENS}}$ | Reference Sensitivity power level | +| $W_{\text{gap}}$ | Sub-block gap or Inter RF Bandwidth gap size | + +![Figure 3.2-1: Illustration of Base Station RF Bandwidth related symbols and definitions for Multi-Standard Radio. The diagram shows a horizontal frequency axis with a grey bar representing the RF bandwidth (BW_RF) from F_BW_RF,low to F_BW_RF,high. Above this bar, three colored blocks represent different RATs: RAT_low (orange), Multiple carriers / RATs (light blue), and RAT_high (green). Vertical dashed lines indicate the center frequencies F_C,low and F_C,high. Horizontal double-headed arrows show the frequency offsets F_offset, RAT, low and F_offset, RAT, high from the center frequencies to the bandwidth edges.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +The diagram illustrates the Base Station RF Bandwidth related symbols and definitions for Multi-Standard Radio. It shows a horizontal frequency axis with a grey bar representing the RF bandwidth ( $BW_{\text{RF}}$ ) from $F_{\text{BW RF,low}}$ to $F_{\text{BW RF,high}}$ . Above this bar, three colored blocks represent different RATs: $\text{RAT\_low}$ (orange), $\text{Multiple carriers / RATs}$ (light blue), and $\text{RAT\_high}$ (green). Vertical dashed lines indicate the center frequencies $F_{\text{C,low}}$ and $F_{\text{C,high}}$ . Horizontal double-headed arrows show the frequency offsets $F_{\text{offset, RAT, low}}$ and $F_{\text{offset, RAT, high}}$ from the center frequencies to the bandwidth edges. + +Figure 3.2-1: Illustration of Base Station RF Bandwidth related symbols and definitions for Multi-Standard Radio. The diagram shows a horizontal frequency axis with a grey bar representing the RF bandwidth (BW\_RF) from F\_BW\_RF,low to F\_BW\_RF,high. Above this bar, three colored blocks represent different RATs: RAT\_low (orange), Multiple carriers / RATs (light blue), and RAT\_high (green). Vertical dashed lines indicate the center frequencies F\_C,low and F\_C,high. Horizontal double-headed arrows show the frequency offsets F\_offset, RAT, low and F\_offset, RAT, high from the center frequencies to the bandwidth edges. + +Figure 3.2-1: Illustration of Base Station RF Bandwidth related symbols and definitions for Multi-Standard Radio. + +![Figure 3.2-2: Illustration of Base Station RF Bandwidth related symbols and definitions for non-contiguous Multi-Standard Radio.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +This diagram illustrates the RF bandwidth for a non-contiguous Multi-Standard Radio. It shows two sub-blocks, Sub block 1 and Sub block n, separated by a gap. Each sub-block contains multiple carriers / RATs, represented by three colored segments: red (FC block 1, low (Fc, low) or FC block n, low), cyan (FC block 1, high or FC block n, high (Fc, high)), and green. The left edge of Sub block 1 is labeled FBW RF, low, and the right edge of Sub block n is labeled FBW RF, high. The total bandwidth between these edges is labeled BW RF. The offset from the sub-block edge to the start of the first carrier is labeled Foffset, RAT. The right edge of each sub-block is also labeled as a 'Sub block edge'. + +Figure 3.2-2: Illustration of Base Station RF Bandwidth related symbols and definitions for non-contiguous Multi-Standard Radio. + +Figure 3.2-2: Illustration of Base Station RF Bandwidth related symbols and definitions for non-contiguous Multi-Standard Radio. + +![Figure 3.2-3: Illustration of Radio Bandwidth related symbols and definitions for Multi-band Multi-standard Radio (Dual-band Base Station).](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +This diagram illustrates the RF bandwidth for a Multi-band Multi-standard Radio (Dual-band Base Station). It shows two bands, Band X and Band Y, separated by an 'Inter RF bandwidth gap'. Band X has a bandwidth labeled BWRF of Band X, and Band Y has a bandwidth labeled BWRF of Band Y. The total RF bandwidth is defined as the sum of the bandwidths of Band X and Band Y: Total RF bandwidth = BWRF of Band X + BWRF of Band Y. This total bandwidth is also labeled as 'Maximum radio bandwidth'. Each band contains multiple carriers / RATs, represented by three colored segments: red (FC band X, low or FC band Y, low), cyan (FC band X, high or FC band Y, high), and green. The offset from the band edge to the start of the first carrier is labeled Foffset, RAT. The gap between the bands is labeled as a 'BWRF edge'. + +Figure 3.2-3: Illustration of Radio Bandwidth related symbols and definitions for Multi-band Multi-standard Radio (Dual-band Base Station). + +Figure 3.2-3: Illustration of Radio Bandwidth related symbols and definitions for Multi-band Multi-standard Radio (Dual-band Base Station) + +## 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]. + +| | | +|-------|-----------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| ARFCN | Absolute Radio Frequency Channel Number | +| AWGN | Additive White Gaussian Noise | +| BC | Band Category | +| BER | Bit Error Ratio | +| BS | Base Station | + +| | | +|-------------|------------------------------------------------| +| BTS | Base Transceiver Station | +| CA | Carrier Aggregation | +| CACLR | Cumulative Adjacent Channel Leakage Ratio | +| CP | Cyclic prefix | +| CW | Continuous Wave | +| DB-DC-HSDPA | Dual Band Dual Cell HSDPA | +| DC-HSDPA | Dual Cell HSDPA | +| DC-HSUPA | Dual Cell HSUPA | +| DTT | Digital Terrestrial Television | +| EARFCN | E-UTRA Absolute Radio Frequency Channel Number | +| EDGE | Enhanced Data rates for GSM Evolution | +| EIRP | Effective Isotropic Radiated Power | +| EVM | Error Vector Magnitude | +| FCC | Federal Communications Commission | +| FDD | Frequency Division Duplex | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| GP | Guard Period (for E-UTRA TDD operation) | +| GSM | Global System for Mobile Communications | +| HSDPA | High Speed Downlink Packet Access | +| HSUPA | High Speed Uplink Packet Access | +| ICS | In-Channel Selectivity | +| ITU-R | Radiocommunication Sector of the ITU | +| LA | Local Area | +| LNA | Low Noise Amplifier | +| MB-MSR | Multi-Band Multi-Standard Radio | +| MFCN | Mobile/Fixed Communications Network | +| MIMO | Multiple Input Multiple Output | +| MR | Medium Range | +| MS | Mobile Station | +| MSR | Multi-Standard Radio | +| NB-IoT | Narrowband - Internet of Things | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NRS | Narrowband Reference Signal | +| OBUE | Operating Band Unwanted Emissions | +| PA | Power Amplifier | +| PHS | Personal Handyphone System | +| QPSK | Quadrature Phase-Shift Keying | +| RAT | Radio Access Technology | +| RB | Resource Block (for E-UTRA and NR) | +| RF | Radio Frequency | +| RMS | Root Mean Square (value) | +| RS | Reference Symbol | +| RX | Receiver | +| SCS | Sub-Carrier Spacing | +| SNR | Signal-to-Noise Ratio | +| TDD | Time Division Duplex | +| TX | Transmitter | +| UARFCN | UTRA Absolute Radio Frequency Channel Number | +| UE | User Equipment | +| UEM | operating band Unwanted Emissions Mask | +| WA | Wide Area | + +# 4 General + +## 4.1 Relation between the MSR specification and the single-RAT specifications + +The requirements for MSR are in most parts specified in the present document, while many requirements are also specified through normative references to the respective single-RAT specifications in [2], [3], [4], [5] and [17]. The resulting set of requirements for an MSR BS can be divided into three types, depending on their relation to the single-RAT specifications: + +1. **Generic MSR requirement:** A common generic requirement is specified in the present document that applies for all RATs and for BS configured for both multi-RAT and single-RAT operation. In some cases, there are additional requirement(s) that apply only in some Band Category. There are no references to the single-RAT specifications. +2. **Generic MSR requirement, with additional single-RAT requirements:** A common generic requirement is specified in the present document which applies as in point 1. In addition, some single RAT requirement(s) apply, included by normative reference(s) to the single-RAT specification(s). +3. **Single-RAT only requirements:** In this case, no common generic requirement is defined. The existing single-RAT requirement applies for each RAT, included by normative reference(s) to the single-RAT specification(s). + +The applicability of each requirement is described in clause 5. + +## 4.2 Relationship between minimum requirements and test requirements + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 37.141 [10] 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. For some requirements, including regulatory requirements, the test tolerance is set to zero. + +For MSR single-RAT requirements, the principle used to define the test requirement remains from the existing specifications. + +For both MSR single-RAT and multi-RAT requirements, the measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle. The Shared Risk principle is defined in ITU-R M.1545 [9]. + +## 4.3 Base station classes + +The requirements in this specification apply to Wide Area Base Stations, Medium Range Base Stations and Local Area Base Stations unless otherwise stated. + +Wide Area Base Stations are characterised by requirements derived from Macro Cell scenarios with a BS to UE minimum coupling loss equal to 70 dB. The Wide Area Base Station class has the same requirements as the base station for General Purpose application in Release 9 and 10. + +Medium Range Base Stations are characterised by requirements derived from Micro Cell scenarios with a BS to UE minimum coupling loss equals to 53 dB. + +Local Area Base Stations are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum coupling loss equal to 45 dB. + +For GSM/EDGE operation of an MSR BS, the requirements according to the applicable multicarrier BTS class apply. The Wide Area BS, Medium Range BS and Local Area BS in the present specification correspond to the Wide Area multicarrier BTS, Medium Range multicarrier BTS and Local Area multicarrier BTS respectively in the GSM/EDGE specifications. MSR requirements for multi-RAT operation only apply for the highest GSM/EDGE static power step. + +## 4.4 Regional requirements + +Some requirements in the present document may only apply in certain regions either as optional requirements, or set by local and regional regulation as mandatory requirements. It is normally not stated in the 3GPP specifications under what exact circumstances that the requirements apply, since this is defined by local or regional regulation. + +Table 4.4-1 lists all requirements in the present specification that may be applied differently in different regions. There are additional single-RAT regional requirements that may apply. These are referenced from the present specification, but listed in the specification for the RATs concerned [2][3][4][5][17]. + +**Table 4.4-1: List of regional requirements** + +| Clause number | Requirement | Comments | +|---------------|--------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.5 | Operating bands and Band Categories | Some bands may be applied regionally. | +| 6.2.2 | Base station output power | These requirements apply in Japan for a BS operating in band 34 and Band 41. | +| 6.6.1.1 | Mandatory requirements (spurious emissions) | Category A limits are mandatory for regions where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply. Category B limits are mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply. | +| 6.6.1.3 | Additional spurious emissions requirements | These requirements may be applied for the protection of system operating in frequency ranges other than the MSR BS operating band. | +| 6.6.1.3 | Additional spurious emissions requirements | In addition to the requirements in subclauses 6.6.1.1, 6.6.1.2 and 6.6.1.3, the BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. | +| 6.6.1.4 | Co-location (spurious emissions) | These requirements may be applied for the protection of other BS receivers when a BS operating in another frequency band is co-located with an MSR BS. | +| 6.6.2.1 | Operating band unwanted emissions | For BS operating in Band 41 in Japan, the operating band unwanted emissions limits shall be applied to the sum of the emission power over all antenna connectors . | +| 6.6.2.4.1 | Additional requirement (Operating band unwanted emissions) | In addition to the requirements in subclauses 6.6.2.1 and 6.6.2.2, the BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied and under the conditions declared by the manufacturer. | +| 6.6.2.4.2 | Unsynchronized operation for BC3 (Operating band unwanted emissions) | The requirements for unsynchronized TDD co-existence may apply regionally. | +| 6.6.2.4.3 | Protection of DTT (Operating band unwanted emissions) | The requirements for protection of DTT may apply regionally. | +| 6.6.2.4.4 | Co-existence with services in adjacent frequency bands (Operating band unwanted emissions) | This regional requirement may be applied for the protection of systems operating in frequency bands adjacent to band 1 as defined in clause 4.5, in geographic areas in which both an adjacent band service and UTRA and/or E-UTRA are deployed. | +| 6.6.2.4.7 | Additional band 32 unwanted emissions | These requirements may apply in certain regions | +| 6.6.3 | Occupied bandwidth | The requirement may be applied regionally. There may also be regional requirements to declare the Occupied bandwidth according to the definition. | +| 6.6.5.3 | Transmitter spurious emissions | For BS operating in Band 41 in Japan, the spurious emissions limits shall be applied to the sum of the emission power over all antenna connectors | +| 6.7.3, 6.7.4 | Additional requirements | These requirements may apply in certain regions. | +| 7.4.5 | Additional BC3 blocking minimum requirement | This requirement may be applied for the protection of the BS receiver when an MSR BS is operating in the same geographical area as UTRA TDD. | +| 7.5.2 | Co-location requirement (blocking) | These requirements may be applied for the protection of the BS receiver when a BS operating in another frequency band is co-located with an MSR BS. | + +## 4.5 Operating bands and Band Categories + +MSR requirements are applicable for band definitions and band numbering as defined in the specifications TS 45.005 [5], TS 25.104 [2], TS 25.105 [3], TS 36.104 [4] and TS 38.104 [17]. For the purpose of defining the BS requirements, the operating bands are divided into three band categories as follows: + +- Band Category 1 (BC1): Bands for NR FDD, E-UTRA FDD and/or UTRA FDD operation. Bands in this category are also used for NB-IoT operation (all modes) +- Band Category 2 (BC2): Bands for NR FDD, E-UTRA FDD, UTRA FDD and/or GSM/EDGE operation. Bands in this category are also used for NB-IoT operation (all modes) +- Band Category 3 (BC3): Bands for NR TDD, E-UTRA TDD and/or UTRA TDD operation. Bands in this category are also used for NB-IoT operation (all modes) + +NOTE: For UTRA TDD, requirements in the present document cover the 1.28 Mcps UTRA TDD option. + +The paired and unpaired bands for the three Band Categories are shown in Table 4.5-1 and 4.5-2, together with the supported RATs and corresponding NR, E-UTRA, UTRA and GSM/EDGE band designations. + +**Table 4.5-1: Paired bands in NR, E-UTRA, UTRA and GSM/EDGE.** + +| MSR Band number | Supported RATs and Band Numbers | | | | | Uplink (UL)
BS receive,
UE transmit
(MHz) | Downlink (DL)
BS transmit,
UE receive
(MHz) | BC | Notes | +|-----------------|---------------------------------|--------|--------|-----------|----------|----------------------------------------------------|------------------------------------------------------|----|---------------| +| | NR | E-UTRA | NB-IoT | UTRA | GSM/EDGE | | | | | +| 1 | n1 | 1 | X | I | - | 1920 – 1980 | 2110 – 2170 | 1 | | +| 2 | n2 | 2 | X | II | PCS 1900 | 1850 – 1910 | 1930 – 1990 | 2 | | +| 3 | n3 | 3 | X | III | DCS 1800 | 1710 – 1785 | 1805 – 1880 | 2 | | +| 4 | - | 4 | X | IV | - | 1710 – 1755 | 2110 – 2155 | 1 | | +| 5 | n5 | 5 | X | V | GSM 850 | 824 – 849 | 869 – 894 | 2 | | +| 6 | - | - | - | VI | - | 830 – 840 | 875 – 885 | 1 | | +| 7 | n7 | 7 | X | VII | - | 2500 – 2570 | 2620 – 2690 | 1 | | +| 8 | n8 | 8 | X | VIII | E-GSM | 880 – 915 | 925 – 960 | 2 | | +| 9 | - | 9 | - | IX | - | 1749.9 – 1784.9 | 1844.9 – 1879.9 | 1 | | +| 10 | - | 10 | - | X | - | 1710 – 1770 | 2110 – 2170 | 1 | | +| 11 | - | 11 | X | XI | - | 1427.9 – 1447.9 | 1475.9 – 1495.9 | 1 | | +| 12 | n12 | 12 | X | XII | - | 699 – 716 | 729 – 746 | 1 | | +| 13 | n13 | 13 | X | XIII | - | 777 – 787 | 746 – 756 | 1 | | +| 14 | n14 | 14 | X | XIV | - | 788 – 798 | 758 – 768 | 1 | | +| 15 | - | - | - | - | - | Reserved | | | | +| 16 | - | - | - | - | - | Reserved | | | | +| 17 | - | 17 | X | - | - | 704 – 716 | 734 – 746 | 1 | | +| 18 | n18 | 18 | X | - | - | 815 – 830 | 860 – 875 | 1 | | +| 19 | - | 19 | X | XIX | - | 830 – 845 | 875 – 890 | 1 | | +| 20 | n20 | 20 | X | XX | - | 832 – 862 | 791 – 821 | 1 | | +| 21 | - | 21 | X | XXI | - | 1447.9 – 1462.9 | 1495.9 – 1510.9 | 1 | | +| 22 | - | 22 | - | XXII | - | 3410 – 3490 | 3510 – 3590 | 1 | | +| 23 | - | 23 | - | - | - | 2000 – 2020 | 2180 – 2200 | 1 | Note 4 | +| 24 | n24 | 24 | X | - | - | 1626.5 – 1660.5 | 1525 – 1559 | 1 | Note 6 | +| 25 | n25 | 25 | X | XXV | - | 1850 – 1915 | 1930 – 1995 | 1 | | +| 26 | n26 | 26 | X | XXVI | - | 814 – 849 | 859 – 894 | 1 | | +| 27 | - | 27 | - | - | - | 807 – 824 | 852 – 869 | 1 | | +| 28 | n28 | 28 | X | - | - | 703 – 748 | 758 – 803 | 1 | | +| 29 | n29 | 29 | - | - | - | N/A | 717 – 728 | 1 | Note 1 | +| 30 | n30 | 30 | - | - | - | 2305 – 2315 | 2350 – 2360 | 1 | | +| 31 | n31 | 31 | X | - | - | 452.5 – 457.5 | 462.5 – 467.5 | 1 | | +| 32 | - | 32 | - | XXXI
I | - | N/A | 1452 – 1496 | 1 | Note1, Note 2 | +| 64 | - | - | - | - | - | Reserved | | | | +| 65 | n65 | 65 | X | - | - | 1920 – 2010 | 2110 – 2200 | 1 | | +| 66 | n66 | 66 | X | - | - | 1710 – 1780 | 2110 – 2200 | 1 | Note 3 | +| 67 | n67 | 67 | - | - | - | N/A | 738 – 758 | 1 | Note 1 | +| 68 | - | 68 | - | - | - | 698 – 728 | 753 – 783 | 1 | | +| 69 | - | 69 | - | - | - | N/A | 2570 – 2620 | 1 | Note 1 | +| 70 | n70 | 70 | X | - | - | 1695 – 1710 | 1995 – 2020 | 1 | Note 5 | +| 71 | n71 | 71 | X | - | - | 663 – 698 | 617 – 652 | 1 | | +| 72 | n72 | 72 | X | - | - | 451 – 456 | 461 – 466 | 1 | | +| 73 | - | 73 | X | - | - | 450 – 455 | 460 – 465 | 1 | | +| 74 | n74 | 74 | X | - | - | 1427 – 1470 | 1475 – 1518 | 1 | | +| 75 | n75 | 75 | - | - | - | N/A | 1432 – 1517 | 1 | Note 1 | +| 76 | n76 | 76 | - | - | - | N/A | 1427 – 1432 | 1 | Note 1 | +| 85 | n85 | 85 | X | - | - | 698 – 716 | 728 – 746 | 1 | | +| 87 | - | 87 | X | - | - | 410 – 415 | 420 – 425 | 1 | | + +| MSR Band number | Supported RATs and Band Numbers | | | | | Uplink (UL)
BS receive,
UE transmit
(MHz) | Downlink (DL)
BS transmit,
UE receive
(MHz) | BC | Notes | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|--------|--------|------|----------|----------------------------------------------------|------------------------------------------------------|----|-------| +| | NR | E-UTRA | NB-IoT | UTRA | GSM/EDGE | | | | | +| 88 | - | 88 | X | - | - | 412 – 417 | 422 – 427 | 1 | | +| 106 | n106 | 106 | X | - | - | 896 – 901 | 935 – 940 | 1 | | +| NOTE 1: For NR and/or E-UTRA, the band is restricted to operation when carrier aggregation is configured. The downlink operating band is paired with the uplink operating band (external) of the carrier aggregation configuration that is supporting the configured Pcell. | | | | | | | | | | +| NOTE 2: For UTRA, the band is restricted to operation when dual band is configured (e.g., DB-DC-HSDPA or dual band 4C-HSDPA). The down link frequenc(ies) of this band are paired with the uplink frequenc(ies) of the other FDD band (external) of the dual band configuration. | | | | | | | | | | +| NOTE 3: For NR and E-UTRA, the range 2180-2200 MHz of the DL operating band is restricted to operation when carrier aggregation is configured. | | | | | | | | | | +| NOTE 4: Band 23 is not applicable. | | | | | | | | | | +| NOTE 5: For E-UTRA, the range 2010-2020 MHz of the DL operating band is restricted to operation when carrier aggregation is configured, and TX-RX separation is 300 MHz. For E-UTRA, the range 2005-2020 MHz of the DL operating band is restricted to operation when carrier aggregation is configured, and TX-RX separation is 295 MHz. | | | | | | | | | | +| NOTE 6: DL operation is restricted to 1526-1536 MHz frequency range. UL operation is restricted to 1627.5 – 1637.5 MHz and 1646.5 – 1656.5 MHz per FCC Order DA 20-48. | | | | | | | | | | + +UTRA FDD can operate with DB-DC-HSDPA for the band configurations listed in subclause 5.2 c) of TS 25.104 [2]. + +NOTE: For BS capable of multi-band operation, the supported operating bands may belong to different Band Categories. + +**Table 4.5-2: Unpaired bands in NR, E-UTRA and UTRA.** + +| MSR Band number | Supported RATs and Band Numbers | | | | Uplink (UL)
BS receive,
UE transmit
(MHz) | Downlink (DL)
BS transmit,
UE receive
(MHz) | BC | Notes | +|-----------------------------------------------------|---------------------------------|--------|--------|------|----------------------------------------------------|------------------------------------------------------|----|--------| +| | NR | E-UTRA | NB-IoT | UTRA | | | | | +| 33 | - | 33 | - | a) | 1900 – 1920 | 1900 – 1920 | 3 | | +| 34 | n34 | 34 | - | a) | 2010 – 2025 | 2010 – 2025 | 3 | | +| 35 | - | 35 | - | b) | 1850 – 1910 | 1850 – 1910 | 3 | | +| 36 | - | 36 | - | b) | 1930 – 1990 | 1930 – 1990 | 3 | | +| 37 | - | 37 | - | c) | 1910 – 1930 | 1910 – 1930 | 3 | | +| 38 | n38 | 38 | - | d) | 2570 – 2620 | 2570 – 2620 | 3 | | +| 39 | n39 | 39 | - | f) | 1880 – 1920 | 1880 – 1920 | 3 | | +| 40 | n40 | 40 | - | e) | 2300 – 2400 | 2300 – 2400 | 3 | | +| 41 | n41 | 41 | X | - | 2496 – 2690 | 2496 – 2690 | 3 | Note 1 | +| 42 | - | 42 | X | - | 3400 – 3600 | 3400 – 3600 | 3 | | +| 43 | - | 43 | X | - | 3600 – 3800 | 3600 – 3800 | 3 | | +| 44 | - | 44 | - | - | 703 – 803 | 703 – 803 | 3 | | +| 45 | - | 45 | - | - | 1447 – 1467 | 1447 – 1467 | 3 | | +| 48 | n48 | 48 | X | - | 3550 – 3700 | 3550 – 3700 | 3 | | +| 50 | n50 | 50 | - | - | 1432 – 1517 | 1432 – 1517 | 3 | | +| 51 | n51 | 51 | - | - | 1427 – 1432 | 1427 – 1432 | 3 | | +| 52 | - | 52 | - | - | 3300 – 3400 | 3300 – 3400 | 3 | | +| 53 | n53 | 53 | - | - | 2483.5 – 2495 | 2483.5 – 2495 | 3 | | +| 54 | n54 | 54 | X | - | 1670 – 1675 | 1670 – 1675 | 3 | | +| 77 | n77 | - | - | - | 3300 – 4200 | 3300 – 4200 | 3 | | +| 78 | n78 | - | - | - | 3300 – 3800 | 3300 – 3800 | 3 | | +| NOTE 1: Band 41 supports NB-IoT in certain regions. | | | | | | | | | + +E-UTRA is designed to operate for the carrier aggregation bands defined in TS 36.101 [18]. The E-UTRA channel bandwidth $BW_{\text{Channel}}$ for a single carrier and the Aggregated Channel Bandwidth $BW_{\text{Channel\_CA}}$ for E-UTRA carrier aggregation are specified in Clause 5.6 of TS 36.104 [4]. + +The NB-IoT channel bandwidth $BW_{\text{Channel}}$ is specified in Clause 5.6 of TS 36.104 [4]. + +The NR BS channel bandwidth and PRB utilization is specified in Clause 5.3 of TS 38.104 [17]. + +### 4.5.1 Band category 1 aspects (BC1) + +For each BC1 band, BC1 requirements for receiver and transmitter shall apply with a frequency offset $F_{\text{offset, RAT}}$ from the Lowest and Highest Carriers to the Base Station RF Bandwidth edges and sub-block edges (if any) as defined in Table 4.5.1-1. + +**Table 4.5.1-1: $F_{\text{offset, RAT}}$ for Band Category 1** + +| RAT | $F_{\text{offset, RAT}}$ | +|---------------------------------|-------------------------------------------| +| 1.4, 3 MHz E-UTRA | $BW_{\text{Channel}}/2 + 200 \text{ kHz}$ | +| 5, 10, 15, 20 MHz E-UTRA and NR | $BW_{\text{Channel}}/2$ | +| UTRA FDD | 2.5 MHz | +| Standalone NB-IoT | 200 kHz | + +### 4.5.2 Band category 2 aspects (BC2) + +For each BC2 band, BC2 requirements for receiver and transmitter shall apply with a frequency offset $F_{\text{offset, RAT}}$ from the Lowest and Highest Carriers to the Base Station RF Bandwidth edges and sub-block edges (if any) as defined in Table 4.5.2-1. + +**Table 4.5.2-1: $F_{\text{offset, RAT}}$ for Band Category 2** + +| RAT | $F_{\text{offset, RAT}}$ | +|-------------------|--------------------------| +| E-UTRA and NR | $BW_{\text{Channel}}/2$ | +| UTRA FDD | 2.5 MHz | +| GSM/EDGE | 200 kHz | +| Standalone NB-IoT | 200 kHz | + +### 4.5.3 Band category 3 aspects (BC3) + +For each BC3 band, BC3 requirements for receiver and transmitter shall apply with a frequency offset $F_{\text{offset, RAT}}$ from the Lowest and Highest Carriers to the Base Station RF Bandwidth edges and sub-block edges (if any) as defined in Table 4.5.3-1. + +**Table 4.5.3-1: $F_{\text{offset, RAT}}$ for Band Category 3** + +| RAT | $F_{\text{offset, RAT}}$ | +|---------------------------------|-------------------------------------------| +| 1.4, 3 MHz E-UTRA | $BW_{\text{Channel}}/2 + 200 \text{ kHz}$ | +| 5, 10, 15, 20 MHz E-UTRA and NR | $BW_{\text{Channel}}/2$ | +| 1.28 Mcps UTRA TDD | 1 MHz | +| Standalone NB-IoT | 200 kHz | + +## 4.6 Channel arrangement + +### 4.6.1 Channel spacing + +The GSM/EDGE carrier spacing is 200 kHz [5]. + +The nominal UTRA FDD channel spacing is 5 MHz. The nominal channel spacing is 1.6MHz for the 1.28 Mcps UTRA TDD Option. These can be adjusted to optimise performance in a particular deployment scenario [2,3]. + +In E-UTRA the spacing between carriers will depend on the deployment scenario, the size of the frequency block available and the channel bandwidths. The nominal channel spacing between two adjacent E-UTRA carriers is defined as following: + +$$\text{Nominal Channel spacing} = (BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2$$ + +where $BW_{\text{Channel}(1)}$ and $BW_{\text{Channel}(2)}$ are the channel bandwidths of the two respective E-UTRA carriers. The channel spacing can be adjusted to optimize performance in a particular deployment scenario [4]. + +The standalone NB-IoT carrier spacing is 200kHz. + +In NR the spacing between carriers will depend on the deployment scenario, the size of the frequency block available and the *BS channel bandwidths*. The nominal channel spacing between two adjacent NR carriers is defined as following: + +- For NR FR1 operating bands with 100 kHz channel raster, + +$$\text{Nominal Channel spacing} = (BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2$$ + +- For NR FR1 operating bands with 15 kHz channel raster, + - Nominal Channel spacing = $(BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2 + \{-5 \text{ kHz}, 0 \text{ kHz}, 5 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 15 kHz + - Nominal Channel spacing = $(BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2 + \{-10 \text{ kHz}, 0 \text{ kHz}, 10 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 30 kHz + +where $BW_{\text{Channel}(1)}$ and $BW_{\text{Channel}(2)}$ are the *BS channel bandwidths* of the two respective NR carriers. The channel spacing can be adjusted depending on the channel raster to optimize performance in a particular deployment scenario [17]. + +The spacing between E-UTRA and NR carriers will depend on the deployment scenario, the size of the frequency block available and the channel bandwidths. The nominal channel spacing between and E-UTRA carrier and an adjacent NR carrier is defined as following: + +- For NR operating bands with 100 kHz channel raster, + +$$\text{Nominal Channel spacing} = (BW_{\text{E-UTRA\_Channel}} + BW_{\text{NR\_Channel}})/2$$ + +- For NR operating bands with 15 kHz channel raster, + +$$\text{Nominal Channel spacing} = (BW_{\text{E-UTRA\_Channel}} + BW_{\text{NR\_Channel}})/2 + \{-5 \text{ kHz}, 0 \text{ kHz}, 5 \text{ kHz}\} \text{ for } \Delta F_{\text{Raster}} \text{ equals to 15 kHz}$$ + +$$\text{Nominal Channel spacing} = (BW_{\text{E-UTRA\_Channel}} + BW_{\text{NR\_Channel}})/2 + \{-10 \text{ kHz}, 0 \text{ kHz}, 10 \text{ kHz}\} \text{ for } \Delta F_{\text{Raster}} \text{ equals to 30 kHz}$$ + +where $BW_{\text{E-UTRA\_Channel}}$ and $BW_{\text{NR\_Channel}}$ are the channel bandwidths of the E-UTRA and NR carriers, $\Delta F_{\text{Raster}}$ is the band dependent channel raster granularity defined in TS38.101-1[19]. The channel spacing can be adjusted depending on the channel raster to optimize performance in a particular deployment scenario. + +### 4.6.1A CA Channel spacing + +In E-UTRA for contiguously aggregated carriers the channel spacing between adjacent component carriers shall be multiple of 300 kHz. + +The nominal channel spacing between two adjacent aggregated E-UTRA carriers is defined as follows: + +$$\text{Nominal channel spacing} = \left\lceil \frac{BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)} - 0.1 |BW_{\text{Channel}(1)} - BW_{\text{Channel}(2)}|}{0.6} \right\rceil 0.3$$ + +where $BW_{Channel(1)}$ and $BW_{Channel(2)}$ are the channel bandwidths of the two respective E-UTRA component carriers according to Table 5.6-1 with values in MHz. The channel spacing for intra-band contiguous carrier aggregation can be adjusted to any multiple of 300 kHz less than the nominal channel spacing to optimize performance in a particular deployment scenario. + +In NR for intra-band contiguously aggregated carriers, the channel spacing between adjacent component carriers shall be multiple of least common multiple of channel raster and sub-carrier spacing. + +The nominal channel spacing between two adjacent aggregated NR carriers is defined as follows: + +For NR operating bands with 100 kHz channel raster: + +$$\text{Nominal channel spacing} = \left\lceil \frac{BW_{Channel(1)} + BW_{Channel(2)} - 2|GB_{Channel(1)} - GB_{Channel(2)}|}{0.6} \right\rceil 0.3 \text{ [MHz]}$$ + +For NR operating bands with 15 kHz channel raster: + +$$\text{Nominal channel spacing} = \left\lceil \frac{BW_{Channel(1)} + BW_{Channel(2)} - 2|GB_{Channel(1)} - GB_{Channel(2)}|}{0.015 * 2^{n+1}} \right\rceil 0.015 * 2^n \text{ [MHz]}$$ + +with + +$$n = \mu_0$$ + +where $BW_{Channel(1)}$ and $BW_{Channel(2)}$ are the *BS channel bandwidths* of the two respective NR component carriers according to Table 5.3.3-1 and 5.3.3-2 in TS 38.104 [17] with values in MHz, $\mu_0$ the largest $\mu$ value among the subcarrier spacing configurations supported in the operating band for both of the channel bandwidths according to Table 5.3.5-1 and Table 5.3.5-2 in TS 38.104 [17] and $GB_{Channel(i)}$ the minimum guard band for channel bandwidth $i$ according to Table 5.3.3-1 and Table 5.3.3-2 in TS 38.104 [17] for the said $\mu$ value, with $\mu$ as defined in TS 38.211. In case there is no common $\mu$ value for both of the channel bandwidths, $\mu_0=1$ is selected for NR *operating bands* with 15 kHz channel raster and $GB_{Channel(i)}$ is the minimum guard band for channel bandwidth $i$ according to Table 5.3.3-1 in TS38.104 [17] for $\mu=1$ with $\mu$ as defined in TS 38.211. + +In NR the channel spacing for intra-band contiguous carrier aggregation can be adjusted to any multiple of least common multiple of channel raster and sub-carrier spacing less than the nominal channel spacing to optimize performance in a particular deployment scenario. + +### 4.6.2 Channel raster + +The GSM/EDGE channel raster is 200 kHz for all bands [5]. + +The UTRA FDD and TDD 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 for UTRA FDD according to [2], which means that the centre frequencies for UTRA FDD channels are shifted 100 kHz relative to the general raster. + +The E-UTRA channel raster is 100 kHz for all bands, which means that the carrier centre frequency must be an integer multiple of 100 kHz [4]. + +NB-IoT channel raster is 100 kHz for all bands [4]. + +NR channel raster is specified in Clause 5.4.2 of TS 38.104 [17]. + +### 4.6.3 Carrier frequencies and numbering + +The carrier frequencies and corresponding numbering is defined for each RAT in the respective specifications TS 38.104 [17], 36.104 [4] TS25.104 [2], TS 25.105 [3] and TS 45.005 [5]. In the context of MSR, the frequency numbering scheme for each RAT will remain. + +- The E-UTRA carrier frequency numbering (EARFCN) is defined in subclause 5.7 of TS 36.104 [4]. + +- The UTRA FDD carrier frequency numbering (UARFCN) is defined in subclause 5.4 of TS 25.104 [2]. +- The UTRA TDD carrier frequency numbering (UARFCN) is defined in subclause 5.4 of TS 25.105 [3]. +- The GSM/EDGE carrier frequency numbering (ARFCN) is defined subclause 2 of TS 45.005 [5]. +- The NB-IoT carrier frequency numbering (EARFCN) is defined in subclause 5.7 of TS 36.104 [4]. +- The NR carrier frequency numbering (NR-ARFCN) is defined in subclause 5.4.2.3 of TS 38.104 [17]. + +NOTE: The numbering schemes for UTRA FDD and TDD are not coordinated, while both are called UARFCN. + +## 4.7 Requirements for contiguous and non-contiguous spectrum + +A spectrum allocation where an MSR BS operates can either be contiguous or non-contiguous. Unless otherwise stated, the requirements in the present specification apply for BS configured for both contiguous spectrum operation and non-contiguous spectrum operation. + +For MSR BS operation in non-contiguous spectrum, some requirements apply both at the Base Station RF Bandwidth edges and inside the sub-block gaps. For each such requirement, it is stated how the limits apply relative to the Base Station RF Bandwidth edges and the sub-block edges respectively. + +## 4.8 Requirements for BS capable of multi-band operation + +For BS capable of multi-band operation (for NR this refers to BS type 1-C with a multi-band antenna connector), the RF requirements in clause 6 and 7 apply for each supported operating band unless otherwise stated. For some requirements it is explicitly stated that specific additions or exclusions to the requirement apply for BS capable of multi-band operation. In the case of multiband operation of a BS, single-RAT operation and the corresponding applicability of the requirements for each operating band is determined based on the RAT configuration within only that operating band, unless otherwise stated. A BS may operate multi-RAT where the individual RATs are operated in different RAT specific bands that partially or fully overlap; $\Delta f_{\text{OBUE}}$ and $\Delta f_{\text{OOB}}$ are according to the combined frequency range occupied by the overlapping bands. + +For BS capable of multi-band operation, various structures in terms of combinations of different transmitter and receiver implementations (multi-band or single band) with mapping of transceivers to one or more antenna port(s) in different ways are possible. In the case where multiple bands are mapped on an antenna connector, the exclusions or provisions for multi-band capable BS are applicable to this antenna connector. In the case where a single band is mapped on an antenna connector, the following applies: + +- Single-band transmitter spurious emissions, operating band unwanted emissions, ACLR, transmitter intermodulation and receiver spurious emissions requirements apply to this antenna connector that is mapped to single-band. +- If the BS is configured for single-band operation, single-band requirements shall apply to this antenna connector configured for single-band operation and no exclusions or provisions for multi-band capable BS are applicable. Single-band requirements are tested separately at the antenna connector configured for single-band operation, with all other antenna connectors terminated. + +For a band supported by a Base Station where the transmitted carriers are not processed in active RF components together with carriers in any other band, single-band transmitter requirements shall apply. For a band supported by a Base Station where the received carriers are not processed in active RF components together with carriers in any other band, single-band receiver requirements shall apply. + +For a BS capable of multi-band operation supporting BC3 bands for TDD, the RF requirements in the present specification assume synchronized operation, where no simultaneous uplink and downlink occur between the bands. + +The RF requirements for multi-band operation supporting bands for both FDD and TDD are not covered by the present release of this specification. + +# --- 5 Applicability of requirements + +## 5.1 Band category 1 + +For all BS operating in bands belonging to Band Category 1, the RF requirements listed in Table 5.1-1 apply for each supported operating band. Requirements apply according to the RAT configuration of the Base Station, as listed in the heading of the table. Some requirements listed in the table may not be mandatory or they may apply only regionally. This is further specified in the clause of each requirement and in Table 4.4-1. For multiband operation, the applicability of the requirements for each operating band is determined based on the RAT configuration within only that operating band, unless otherwise stated. + +**Table 5.1-1: Applicability of requirements for MSR BS operation in Band Category 1** + +| RF requirement | BS configured for multi-RAT operation in the band | BS configured for single-RAT E-UTRA FDD operation in the band | BS configured for single-RAT UTRA FDD operation in the band | BS configured for single-RAT NB-IoT FDD standalone operation in the band | BS configured for single-RAT NR operation in the band | +|-----------------------------------|---------------------------------------------------|---------------------------------------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------|-------------------------------------------------------| +| Base station output power | 6.2.1
6.2.3
6.2.4
6.2.4A
6.2.6 | 6.2.1
6.2.3 | 6.2.1
6.2.4
6.2.4A | 6.2.1
6.2.6 | 6.2.1 | +| Output power dynamics | 6.3.1
6.3.2
6.3.5
6.3.6 | 6.3.1 | 6.3.2 | 6.3.5 | 6.3.6 | +| Transmitted signal quality | | | | | | +| Modulation quality | 6.5.1.1
6.5.1.2
6.5.1.5
6.5.1.6 | 6.5.1.1 | 6.5.1.2 | 6.5.1.5 | 6.5.1.6 | +| Frequency error | 6.5.2.1
6.5.2.2
6.5.2.5
6.5.2.6 | 6.5.2.1 | 6.5.2.2 | 6.5.2.5 | 6.5.2.6 | +| Time alignment error | 6.5.3.1
6.5.3.2
6.5.3.4
6.5.3.5 | 6.5.3.1 | 6.5.3.2 | 6.5.3.4 | 6.5.3.5 | +| Unwanted emissions | | | | | | +| Transmitter spurious emissions | 6.6.1 (except for 6.6.1.1.3) | 6.6.1 (except for 6.6.1.1.3) | 6.6.1 (except for 6.6.1.1.3) | 6.6.1 (except for 6.6.1.1.3) | 6.6.1 (except for 6.6.1.1.3) | +| Operating band unwanted emissions | 6.6.2.1
6.6.2.4 | 6.6.2.1
6.6.2.4 | 6.6.2.1
6.6.2.4 | 6.6.2.1
6.6.2.4 | 6.6.2.1
6.6.2.4 | +| Occupied bandwidth | 6.6.3 | 6.6.3 | 6.6.3 | 6.6.3 | 6.6.3 | +| ACLR | 6.6.4.1
6.6.4.2
6.6.4.5
6.6.4.6 | 6.6.4.1 | 6.6.4.2 | 6.6.4.5 | 6.6.4.6 | +| Cumulative ACLR | 6.6.4.4 (NOTE 3) | 6.6.4.4 (NOTE 3) | 6.6.4.4 (NOTE 3) | 6.6.4.4 (NOTE 3) | 6.6.4.4 (NOTE 3) | +| Transmitter intermodulation | 6.7.1
6.7.2 (NOTE 2) | 6.7.1
6.7.2 (NOTE 2) | 6.7.1
6.7.2 (NOTE 2) | 6.7.1
6.7.2 (NOTE 2) | 6.7.1
6.7.2 (NOTE 2) | +| Reference sensitivity level | 7.2.1
7.2.2
7.2.5
7.2.6 | 7.2.1 | 7.2.2 | 7.2.5 | 7.2.6 | +| Dynamic range | 7.3.1
7.3.2
7.3.5
7.3.6 | 7.3.1 | 7.3.2 | 7.3.5 | 7.3.6 | +| In-band selectivity and blocking | | | | | | +| Blocking | 7.4.1 | 7.4.1 | 7.4.1 | 7.4.1 | 7.4.1 | +| Narrowband blocking | 7.4.2 | 7.4.2 | 7.4.2 | 7.4.2 | 7.4.2 | +| Out-of-band blocking | 7.5 | 7.5 | 7.5 | 7.5 | 7.5 | +| Receiver spurious emissions | 7.6.1 | 7.6.1 | 7.6.1 | 7.6.1 | 7.6.1 | +| Receiver intermodulation | | | | | | +| Intermodulation | 7.7.1 | 7.7.1 | 7.7.1 | 7.7.1 | 7.7.1 | +| Narrowband intermodulation | 7.7.2 | 7.7.2 | 7.7.2 | 7.7.2 | 7.7.2 | +| In-channel selectivity | 7.8 | 7.8 | - | 7.8 | 7.8.2 | +| Performance requirements | 8.1
8.2
8.5 | 8.1 | 8.2 | 8.6 | 8.5 | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: For some requirements in BS configured for multi-RAT operation, there is no general MSR multi-RAT requirement. Instead, the requirement is defined by the respective single-RAT requirement for each RAT supported by the BS as referenced in the table.
NOTE 2: The requirement in sub-clause 6.7.2 is only applied for BS operating in non-contiguous spectrum.
NOTE 3: The requirement in sub-clause 6.6.4.4 is only applied for BS operating in non-contiguous spectrum. | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 5.2 Band category 2 + +For all BS operating in bands belonging to Band Category 2, the RF requirements listed in Table 5.2-1 apply for each supported operating band. Requirements apply according to the RAT configuration of the Base Station, as listed in the heading of the table. Some requirements listed in the table may not be mandatory or they may apply only regionally. This is further specified in the clause of each requirement and in Table 4.4-1. For multiband operation, the applicability of the requirements for each operating band is determined based on the RAT configuration within only that operating band, unless otherwise stated. + +**Table 5.2-1: Applicability of requirements for MSR BS operation in Band Category 2** + +| RF requirement | BS configured for multi-RAT operation not including GSM/EDGE in the band | BS configured for multi-RAT operation including GSM/EDGE in the band | BS configured for single-RAT E-UTRA FDD operation in the band | BS configured for single-RAT UTRA FDD operation in the band | BS configured for single-RAT GSM/EDGE operation in the band | BS configured for single-RAT NB-IoT FDD standalone operation in the band | BS configured for single-RAT NR operation in the band | +|-----------------------------------|--------------------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------|-------------------------------------------------------| +| Base station output power | 6.2.1
6.2.3
6.2.4
6.2.4A
6.2.6 | 6.2.1
6.2.3
6.2.4
6.2.4A
6.2.6 | 6.2.1
6.2.3 | 6.2.1
6.2.4
6.2.4A | 6.2.1 | 6.2.1
6.2.6 | 6.2.1 | +| Output power dynamics | 6.3.1
6.3.2
6.3.5
6.3.6 | 6.3.1
6.3.2
6.3.4
6.3.5
6.3.6 | 6.3.1 | 6.3.2 | 6.3.4 | 6.3.5 | 6.3.6 | +| Transmit ON/OFF power | - | - | - | - | - | - | - | +| Transmitted signal quality | | | | | | | | +| Modulation quality | 6.5.1.1
6.5.1.2
6.5.1.5
6.5.1.6 | 6.5.1.1
6.5.1.2
6.5.1.4
6.5.1.5
6.5.1.6 | 6.5.1.1 | 6.5.1.2 | 6.5.1.4 | 6.5.1.5 | 6.5.1.6 | +| Frequency error | 6.5.2.1
6.5.2.2
6.5.2.5
6.5.2.6 | 6.5.2.1
6.5.2.2
6.5.2.4
6.5.2.5
6.5.2.6 | 6.5.2.1 | 6.5.2.2 | 6.5.2.4 | 6.5.2.5 | 6.5.2.6 | +| Time alignment error | 6.5.3.1
6.5.3.2
6.5.3.4
6.5.3.5 | 6.5.3.1
6.5.3.2
6.5.3.4
6.5.3.5 | 6.5.3.1 | 6.5.3.2 | - | 6.5.3.4 | 6.5.3.5 | +| Unwanted emissions | | | | | | | | +| Transmitter spurious emissions | 6.6.1
(except for 6.6.1.1.3) | 6.6.1
(NOTE 3) | 6.6.1
(except for 6.6.1.1.3) | 6.6.1
(except for 6.6.1.1.3) | 6.6.1
(NOTE 3) | 6.6.1
(except for 6.6.1.1.3) | 6.6.1
(except for 6.6.1.1.3) | +| Operating band unwanted emissions | 6.6.2.2
6.6.2.4 | 6.6.2.2
6.6.2.4 | 6.6.2.2
6.6.2.4 | 6.6.2.2
6.6.2.4 | 6.6.2.3
6.6.2.4 | 6.6.2.2
6.6.2.4 | 6.6.2.2,
6.6.2.4 | +| Occupied bandwidth | 6.6.3 | 6.6.3 | 6.6.3 | 6.6.3 | - | 6.6.3 | 6.6.3 | +| ACLR | 6.6.4.1
6.6.4.2
6.6.4.5
6.6.4.6 | 6.6.4.1
6.6.4.2
6.6.4.5
6.6.4.6 | 6.6.4.1 | 6.6.4.2 | - | 6.6.4.5 | 6.6.4.6 | +| Cumulative ACLR | 6.6.4.4
(NOTE 2) | 6.6.4.4
(NOTE 2) | 6.6.4.4
(NOTE 2) | 6.6.4.4
(NOTE 2) | - | 6.6.4.4
(NOTE 2) | 6.6.4.4
(NOTE 2) | +| Transmitter intermodulation | 6.7.1
6.7.2 | 6.7.1
6.7.2 | 6.7.1
6.7.2 | 6.7.1
6.7.2 | 6.7.2 | 6.7.1
6.7.2 | 6.7.1
6.7.2 | +| Reference sensitivity level | 7.2.1
7.2.2
7.2.5
7.2.6 | 7.2.1
7.2.2
7.2.4
7.2.5
7.2.6 | 7.2.1 | 7.2.2 | 7.2.4 | 7.2.5 | 7.2.6 | +| Dynamic range | 7.3.1
7.3.2
7.3.5
7.3.6 | 7.3.1
7.3.2
7.3.4
7.3.5
7.3.6 | 7.3.1 | 7.3.2 | 7.3.4 | 7.3.5 | 7.3.6 | +| In-band selectivity and blocking | | | | | | | | + +| | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------|-------|-------|----------------------------|-------|-------| +| Blocking | 7.4.1 | 7.4.1 | 7.4.1 | 7.4.1 | 7.4.1 | 7.4.1 | 7.4.1 | +| Narrowband blocking | 7.4.2 | 7.4.2
7.4.3 | 7.4.2 | 7.4.2 | 7.4.2
7.4.3
7.4.4 | 7.4.2 | 7.4.2 | +| Out-of-band blocking | 7.5 | 7.5 | 7.5 | 7.5 | 7.5 | 7.5 | 7.5 | +| Receiver spurious emissions | 7.6.1 | 7.6.1
7.6.2
(NOTE 3) | 7.6.1 | 7.6.1 | 7.6.1
7.6.2
(NOTE 3) | 7.6.1 | 7.6.1 | +| Receiver intermodulation | | | | | | | | +| Intermodulation | 7.7.1 | 7.7.1 | 7.7.1 | 7.7.1 | 7.7.1 | 7.7.1 | 7.7.1 | +| Narrowband intermodulation | 7.7.2 | 7.7.2
7.7.3 | 7.7.2 | 7.7.2 | 7.7.2
7.7.3 | 7.7.2 | 7.7.2 | +| In-channel selectivity | 7.8 | 7.8 | 7.8 | - | - | 7.8 | 7.8.2 | +| Performance requirements | 8.1
8.2
8.5 | 8.1
8.2
8.4
8.5 | 8.1 | 8.2 | 8.4 | 8.6 | 8.5 | +| NOTE 1: For some requirements in BS configured for multi-RAT operation, there is no general MSR multi-RAT requirement. Instead, the requirement is defined by the respective single-RAT requirement for each RAT supported by the BS as referenced in the table. | | | | | | | | +| NOTE 2: The requirement in sub-clause 6.6.4.4 is only applied for BS operating in non-contiguous spectrum. | | | | | | | | +| NOTE 3: For BS capable of multi-band operation, the limits in subclause 6.6.1.1.3 and 7.6.2 are only applicable when all supported operating bands belong to BC2 and GSM/EDGE is configured in all operating bands. | | | | | | | | + +## 5.3 Band category 3 + +For all BS operating in bands belonging to Band Category 3, the RF requirements listed in Table 5.3-1 apply for each supported operating band. Requirements apply according to the RAT configuration of the Base Station, as listed in the heading of the table. Some requirements listed in the table may not be mandatory or they may apply only regionally. This is further specified in the clause of each requirement and in Table 4.4-1. + +**Table 5.3-1: Applicability of requirements for MSR BS operation in Band Category 3** + +| RF requirement | BS configured for multi-RAT operation | BS configured for single-RAT E-UTRA TDD operation | BS configured for single-RAT UTRA TDD operation | BS configured for single-RAT NR TDD operation | BS configured for single-RAT NB-IoT standalone operation | +|-----------------------------------|------------------------------------------|---------------------------------------------------|-------------------------------------------------|-----------------------------------------------|----------------------------------------------------------| +| Base station output power | 6.2.1
6.2.2
6.2.3
6.2.5 | 6.2.1
6.2.2
6.2.3 | 6.2.1
6.2.5 | 6.2.1 | 6.2.1
6.2.6 | +| Output power dynamics | 6.3.1
6.3.3
6.3.6 | 6.3.1 | 6.3.3 | 6.3.6 | 6.3.5 | +| Transmit ON/OFF power | 6.4 | 6.4 | 6.4 | 6.4 | 6.4 | +| Transmitted signal quality | | | | | | +| Modulation quality | 6.5.1.1
6.5.1.3
6.5.1.6 | 6.5.1.1 | 6.5.1.3 | 6.5.1.6 | 6.5.1.5 | +| Frequency error | 6.5.2.1
6.5.2.3
6.5.2.6 | 6.5.2.1 | 6.5.2.3 | 6.5.2.6 | 6.5.2.5 | +| Time alignment error | 6.5.3.1
6.5.3.3
6.5.3.5 | 6.5.3.1 | 6.5.3.3 | 6.5.3.5 | 6.5.3.4 | +| Unwanted emissions | | | | | | +| Transmitter spurious emissions | 6.6.1 (except for 6.6.1.1.3 and 6.6.1.2) | 6.6.1 (except for 6.6.1.1.3 and 6.6.1.2) | 6.6.1 (except for 6.6.1.1.3 and 6.6.1.2) | 6.6.1 (except for 6.6.1.1.3 and 6.6.1.2) | 6.6.1 (except for 6.6.1.1.3) | +| Operating band unwanted emissions | 6.6.2.1
6.6.2.4 | 6.6.2.1
6.6.2.4 | 6.6.2.1
6.6.2.4 | 6.6.2.1
6.6.2.4 | 6.6.2.1
6.6.2.4 | +| Occupied bandwidth | 6.6.3 | 6.6.3 | 6.6.3 | 6.6.3 | 6.6.3 | +| ACLR | 6.6.4.1
6.6.4.3
6.6.4.6 | 6.6.4.1 | 6.6.4.3 | 6.6.4.6 | 6.6.4.5 | +| Cumulative ACLR | 6.6.4.4 (NOTE 2) | 6.6.4.4 (NOTE 2) | 6.6.4.4 (NOTE 2) | 6.6.4.4 (NOTE 2) | 6.6.4.4 (NOTE 2) | +| Transmitter intermodulation | 6.7.1
6.7.3 | 6.7.1
6.7.3
6.7.4 | 6.7.1
6.7.3 | 6.7.1
6.7.3 | 6.7.1
6.7.3 | +| Reference sensitivity level | 7.2.1
7.2.3
7.2.6 | 7.2.1 | 7.2.3 | 7.2.6 | 7.2.5 | +| Dynamic range | 7.3.1
7.3.3
7.3.6 | 7.3.1 | 7.3.3 | 7.3.6 | 7.3.5 | +| In-band selectivity and blocking | | | | | | +| Blocking | 7.4.1
7.4.5 | 7.4.1
7.4.5 | 7.4.1
7.4.5 | 7.4.1 | 7.4.1 | +| Narrowband blocking | 7.4.2 | 7.4.2 | 7.4.2 | 7.4.2 | 7.4.2 | +| Out-of-band blocking | 7.5 | 7.5 | 7.5 | 7.5 | 7.5 | +| Receiver spurious emissions | 7.6.1 | 7.6.1 | 7.6.1 | 7.6.1 | 7.6.1 | +| Receiver intermodulation | | | | | | +| Intermodulation | 7.7.1 | 7.7.1 | 7.7.1 | 7.7.1 | 7.7.1 | +| Narrowband intermodulation | 7.7.2 | 7.7.2 | 7.7.2 | 7.7.2 | 7.7.2 | +| In-channel selectivity | 7.8 | 7.8 | - | 7.8.2 | 7.8 | +| Performance requirements | 8.1
8.3
8.5 | 8.1 | 8.3 | 8.5 | 8.6 | + +Note 1: For some requirements in BS configured for multi-RAT operation, there is no general MSR multi-RAT requirement. Instead, the requirement is defined by the respective single-RAT requirement for each RAT supported by the BS as referenced in the table. + +NOTE 2: The requirement in sub-clause 6.6.4.4 is only applied for BS operating in non-contiguous spectrum. + +## 5.4 Inclusion of requirements by reference + +Many requirements in the present specification are not explicitly stated in the clauses listed in Tables 5.1-1, 5.2-1 and 5.3-1, but are instead included by reference to the respective single-RAT specifications. Each reference is normative and identifies the clause where the requirement is specified. + +In some cases, the referenced clause may contain requirements that for different reasons do not apply for an MSR base station. It is in those cases stated that "applicable parts of" the referenced clause applies. What parts are applicable is determined by the scope of the MSR specification. For example: + +- In a referenced clause including requirements for multiple operating bands, only requirements for bands listed in the present document apply. +- In a referenced clause that includes requirements for different types of base stations, only requirements for the BS classes specified for each RAT apply, see subclause 4.3. + +# 6 Transmitter characteristics + +## 6.1 General + +Unless otherwise stated, the requirements in clause 6 are expressed for a single transmitter antenna connector. In case of multi-carrier transmission with multiple transmitter antenna connectors, transmit diversity, DB-DC-HSDPA or MIMO transmission, the requirements apply for each transmitter antenna connector. + +A BS supporting DC-HSDPA and DB-DC-HSDPA transmits two UTRA FDD cells simultaneously. A BS supporting DC-HSDPA transmits two UTRA FDD cells simultaneously on adjacent carrier frequencies. + +Unless otherwise stated, the transmitter characteristics are specified at the BS antenna connector (test port A) with a full complement of transceivers for the configuration in normal operating conditions. If any external apparatus such as a TX amplifier, a filter or the combination of such devices is used, requirements apply at the far end antenna connector (test port B). + +Unless otherwise stated the requirements in subclause 6 applies at all times, i.e. during the Transmitter ON period, the Transmitter OFF period and the Transmitter transient period. + +![Diagram of transmitter test ports showing a BS cabinet connected to an External PA (if any) and an External device (e.g. TX filter, if any), with Test port A at the BS cabinet and Test port B at the external device output towards the antenna connector.](10d81b2cc455e3563e3e562a7f451124_img.jpg) + +The diagram illustrates the transmitter test ports. It shows a sequence of components connected in series: a 'BS cabinet', an 'External PA (if any)', and an 'External device e.g. TX filter (if any)'. The 'BS cabinet' has a connector labeled 'Test port A'. The 'External PA' and 'External device' are connected by cables. The output of the 'External device' is labeled 'Test port B' and has an arrow pointing towards the 'Towards antenna connector'. + +Diagram of transmitter test ports showing a BS cabinet connected to an External PA (if any) and an External device (e.g. TX filter, if any), with Test port A at the BS cabinet and Test port B at the external device output towards the antenna connector. + +Figure 6.1-1: Transmitter test ports + +Values for $F_{\text{offset, RAT}}$ to meet transmitter requirements are specific for each RAT in each Band Category as specified in subclause 4.5.1 for Band Category 1, subclause 4.5.2 for Band Category 2 and subclause 4.5.3 for Band Category 3. + +Unless otherwise stated the requirements for NB-IoT in subclause 6 applies for all operation modes (In-band operation, Guard-band operation and Stand-alone operation). + +## 6.2 Base station output power + +Output power of the base station is the mean power delivered to a load with resistance equal to the nominal load impedance of the transmitter. + +The configured carrier power is the target maximum power for a specific carrier for the operating mode set in the BS within the limits given by the manufacturer's declaration. + +The maximum total output power, $P_{\max}$ , of the base station is the mean power level measured at the antenna connector during the transmitter ON period in a specified reference condition. + +The maximum RAT output power, $P_{\max, \text{RAT}}$ , of the base station is the mean power level measured at the antenna connector during the transmitter ON period for a specific RAT in a specified reference condition. + +The maximum carrier output power, $P_{\max, c}$ , of the base station is the mean power level measured at the antenna connector during the transmitter ON period for a specific carrier in a specified reference condition. + +The rated carrier output power, $P_{\text{Rated}, c}$ , of the base station is the mean power level for a specific carrier that the manufacturer has declared to be available at the antenna connector during the transmitter ON period. + +NOTE: For NB-IoT in-band and guard band operation, the LTE carrier and NB-IoT carrier shall be seen as a single carrier occupied LTE channel bandwidth, the output power over this carrier is shared between LTE and NB-IoT. For *NB-IoT operation in NR in-band*, the NR carrier and NB-IoT carrier shall be seen as a single carrier occupied NR channel bandwidth, the output power over this carrier is shared between NR and NB-IoT. This note is applied for $P_{\text{out}}$ , $P_{\text{Rated}}$ , total output power, $P_{\max, c}$ and $P_{\text{Rated}, c}$ . + +The rated carrier output power of the BS shall be as specified in Table 6.2-1. + +**Table 6.2-1 Base Station rated carrier output power** + +| BS class | $P_{\text{Rated}, c}$
(note) | +|-----------------|-------------------------------------------------------------------------------------------| +| Wide Area BS | | +| Medium Range BS | $\leq +38$ dBm | +| Local Area BS | $\leq +24$ dBm | +| NOTE: | There is no upper limit for the rated carrier output power of the Wide Area Base Station. | + +In addition, for Band 85 NB-IoT standalone operation, the BS rated output power limit of 43 dBm applies over the NB-IoT carriers in the range 728-729 MHz of the DL operating band. The BS output power limit of 43 dBm shall be considered as shared among all NB-IoT carriers in the 728-729 MHz frequency range or as the maximum value per NB-IoT carrier in the case where only one NB-IoT carrier is deployed in 728-729 MHz frequency range. + +### 6.2.1 Minimum requirement + +In normal conditions, the maximum carrier output power shall remain within +2 dB and -2 dB of the configured carrier power declared by the manufacturer. + +In extreme conditions, maximum carrier output power shall remain within +2.5 dB and -2.5 dB of the configured carrier power declared by the manufacturer. + +The definition of the output power parameters declared by the manufacturer can be found in TS 37.141 [10]. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +### 6.2.2 Additional requirement (regional) + +For Band 34 operation in Japan, the rated E-UTRA output power declared by the manufacturer shall be less than or equal to the values specified in Table 6.2.2-1. + +**Table 6.2.2-1: Regional requirements for Band 34 for rated output power declared by the manufacturer.** + +| Channel bandwidth
BW Channel [MHz] | 1.4 | 3 | 5 | 10 | 15 | 20 | +|--------------------------------------------------|-----|-----|----|----|----|-----| +| Maximum output power
[W] | N/A | N/A | 20 | 40 | 60 | N/A | + +For Band 41 E-UTRA operation in Japan, the rated output power per BS declared by the manufacturer shall be less than or equal to the values specified in Table 6.2.2-2. + +**Table 6.2.2-2: Regional requirements for Band 41 for rated output power declared by the manufacturer.** + +| Channel bandwidth
BW Channel [MHz] | 1.4 | 3 | 5 | 10 | 15 | 20 | +|--------------------------------------------------|-----|-----|-----|----|-----|----| +| Maximum output power
[W] | N/A | N/A | N/A | 20 | N/A | 40 | + +For Band 41 NR operation in Japan, the sum of Prated,c,AC over all *antenna connectors* declared by the manufacturer shall be equal to or less than 20 W per 10 MHz bandwidth. + +### 6.2.3 E-UTRA minimum requirement for DL RS power + +For E-UTRA, the minimum requirement for DL RS power is specified in TS 36.104 [4], subclause 6.5.4. + +### 6.2.4 UTRA FDD minimum requirement for primary CPICH power + +For UTRA FDD, the minimum requirements for primary CPICH power is specified in TS 25.104 [2], subclause 6.4.4. + +### 6.2.4A UTRA FDD minimum requirement for secondary CPICH power + +For UTRA FDD, the minimum requirements for secondary CPICH power is specified in TS 25.104 [2], subclause 6.4.4A. + +### 6.2.5 UTRA TDD minimum requirement for primary CCPCH power + +For UTRA TDD, the minimum requirements for Primary CCPCH power and Differential accuracy of primary CCPCH power specified in TS 25.105 [3], subclause 6.4.5 and 6.4.6 respectively. + +### 6.2.6 NB-IoT minimum requirement for DL NRS power + +For NB-IoT, the minimum requirement for DL NRS power is specified in TS 36.104 [4], subclause 6.5.4. + +## 6.3 Output power dynamics + +Output power dynamics is defined by the BS transmitter's ability to operate at varying output power levels. + +### 6.3.1 E-UTRA minimum requirement + +For E-UTRA, the minimum requirement for output power dynamics is specified in TS 36.104 [4], subclause 6.3. + +### 6.3.2 UTRA FDD minimum requirement + +For UTRA FDD, the minimum requirement for output power dynamics is specified in TS 25.104 [2], subclause 6.4. + +### 6.3.3 UTRA TDD minimum requirement + +For UTRA TDD, the minimum requirement for output power dynamics is specified in TS 25.105 [3], subclause 6.4. + +### 6.3.4 GSM/EDGE minimum requirement + +For GSM/EDGE, the minimum requirement for output power dynamics is specified in TS 45.005[5], subclause 4.1.2-c. The minimum requirement for output level dynamic operation is specified in TS 45.005[5], subclause 4.5.1. + +### 6.3.5 NB-IoT minimum requirement + +For NB-IoT E-UTRA in-band or guard band operation, the minimum requirement for output power dynamics is specified in TS 36.104 [4], subclause 6.3. + +For *NB-IoT operation in NR in-band*, the minimum requirement for output power dynamics is specified in TS 38.104 [17], subclause 6.3. + +### 6.3.6 NR minimum requirement + +For NR, the minimum requirement for output power dynamics (BS type 1-C) is specified in TS 38.104 [17], subclause 6.3. + +## 6.4 Transmit ON/OFF power + +The requirements in subclause 6.4 are only applied for BC3 BS. + +### 6.4.1 Transmitter OFF power + +For UTRA and E-UTRA, transmitter OFF power is defined as the mean power measured over 70 $\mu$ s filtered with a square filter of bandwidth equal to the Base Station RF Bandwidth(s) of the BS centred on the central frequency of the Base Station RF Bandwidth(s) during the transmitter OFF period. + +In NR transmitter OFF power is defined as the mean power measured over 70/N $\mu$ s filtered with a square filter of bandwidth equal to the transmission bandwidth configuration of the BS ( $BW_{Config}$ ) centred on the central frequency of the Base Station RF Bandwidth(s) during the transmitter OFF period. $N = SCS/15$ , where SCS is Sub Carrier Spacing in kHz. + +For BS supporting intra-band contiguous CA, the transmitter OFF power is defined as the mean power measured over 70/N $\mu$ s filtered with a square filter of bandwidth equal to the *Aggregated BS Channel Bandwidth* $BW_{Channel\_CA}$ centred on $(F_{edge,high} + F_{edge,low})/2$ during the *transmitter OFF period*. N is equal to 1 if there are any UTRA or E-UTRA carriers, or for NR $N = SCS/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *Aggregated BS Channel Bandwidth*. + +#### 6.4.1.1 Minimum Requirement + +The transmitter OFF power spectral density shall be less than -85 dBm/MHz. + +For BS capable of multi-band operation, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +### 6.4.2 Transmitter transient period + +The transmitter transient period is the time period during which the transmitter is changing from the OFF period to the ON period or vice versa. The transmitter transient period is illustrated in Figure 6.4.2-1 and Figure 6.4.2-2. + +![Figure 6.4.2-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for E-UTRA/UTRA).](673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg) + +This graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two horizontal dashed lines: 'ON power level (Informative)' and 'OFF power level'. The curve shows a transition from OFF to ON, reaching the ON power level, and then back to OFF. The 'Transmitter ON period (DL Timeslots and DwPTS)' is the duration where the power is at the ON level. The 'Transmitter transient period' is the time interval between the start of the ON period and the start of the OFF period. The 'Transmitter OFF period' is the duration where the power is at the OFF level. The graph is divided into 'UL Timeslots' and 'GP and UpPTS' by vertical dashed lines. The OFF power level is indicated by hatched rectangular areas. + +Figure 6.4.2-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for E-UTRA/UTRA). + +Figure 6.4.2-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for E-UTRA/UTRA) + +![Figure 6.4.2-2: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for NR).](455c842681aadb4969bd61d71f556744_img.jpg) + +This graph shows Transmitter output power on the y-axis and Time on the x-axis. The y-axis has two horizontal dashed lines: 'ON power level (Informative)' and 'OFF power level'. The curve shows a transition from OFF to ON, reaching the ON power level, and then back to OFF. The 'Transmitter ON period (DL transmission)' is the duration where the power is at the ON level. The 'Transmitter transient period' is the time interval between the start of the ON period and the start of the OFF period. The 'Transmitter OFF period' is the duration where the power is at the OFF level. The graph is divided into 'UL transmission' and 'GP or UL transmission' by vertical dashed lines. The OFF power level is indicated by hatched rectangular areas. + +Figure 6.4.2-2: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for NR). + +Figure 6.4.2-2: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for NR) + +#### 6.4.2.1 Minimum requirements + +The transmitter transient period shall be shorter than the values listed in Table 6.4.2.1-1, Table 6.4.2.1-1a and Table 6.4.2.1-2. + +Table 6.4.2.1-1: Minimum requirements for the transmitter transient period for a BS supporting UTRA + +| Transition | Transient period length [ $\mu\text{s}$ ] | +|------------|-------------------------------------------| +| OFF to ON | 6.25 | +| ON to OFF | 17 | + +**Table 6.4.2.1-1a: Minimum requirements for the transmitter transient period for a BS supporting E-UTRA and not supporting NR nor UTRA** + +| Transition | Transient period length [ $\mu\text{s}$ ] | +|------------|-------------------------------------------| +| OFF to ON | 17 | +| ON to OFF | 17 | + +**Table 6.4.2.1-2: Minimum requirements for the transmitter transient period for a BS supporting NR and not supporting UTRA** + +| Transition | Transient period length [ $\mu\text{s}$ ] | +|------------|-------------------------------------------| +| OFF to ON | 10 | +| ON to OFF | 10 | + +## 6.5 Transmitted signal quality + +### 6.5.1 Modulation quality + +Modulation quality is defined by the difference between the measured carrier signal and a reference signal. Modulation quality can e.g. be expressed as Error Vector Magnitude (EVM), Peak Code Domain Error (PCDE) or Relative Code domain Error (RCDE). + +#### 6.5.1.1 E-UTRA minimum requirement + +For E-UTRA, the minimum requirement for modulation quality, EVM, is specified in TS 36.104 [4], subclause 6.5.2. + +#### 6.5.1.2 UTRA FDD minimum requirement + +For UTRA FDD, the minimum requirements for modulation quality, EVM, PCDE and RCDE, are specified in TS 25.104 [2], subclause 6.8.2, 6.8.3 and 6.8.5 respectively. The UTRA transmit pulse shape filter is defined in subclause 6.8.1. + +#### 6.5.1.3 UTRA TDD minimum requirement + +For UTRA TDD, the minimum requirements for modulation quality, EVM, PCDE and RCDE, are specified in TS 25.105 [3], subclause 6.8.2, 6.8.3 and 6.8.4 respectively. + +#### 6.5.1.4 GSM/EDGE minimum requirement + +For GSM/EDGE, the minimum requirements for modulation accuracy are specified in TS 45.005 [5], subclause 4.6. + +#### 6.5.1.5 NB-IoT minimum requirement + +For NB-IoT, the minimum requirement for modulation quality, EVM, is specified in TS 36.104 [4], subclause 6.5.2. + +#### 6.5.1.6 NR minimum requirement + +For NR, the minimum requirement for modulation quality, EVM (BS type 1-C) is specified in TS 38.104 [17], subclause 6.5.2. + +### 6.5.2 Frequency error + +Frequency error is a measure of the difference between the actual BS transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation. + +#### 6.5.2.1 E-UTRA minimum requirement + +For E-UTRA, the minimum requirement for frequency error is specified in TS 36.104 [4], subclause 6.5.1. + +#### 6.5.2.2 UTRA FDD minimum requirement + +For UTRA FDD, the minimum requirement for frequency error is specified in TS 25.104 [2], subclause 6.3.1. + +#### 6.5.2.3 UTRA TDD minimum requirement + +For UTRA TDD, the minimum requirement for frequency error is specified in TS 25.105 [3], subclause 6.3.1. + +#### 6.5.2.4 GSM/EDGE minimum requirement + +For GSM/EDGE, the minimum requirement for frequency error is specified in TS 45.005 [5], subclause 4.4. + +#### 6.5.2.5 NB-IoT minimum requirement + +For NB-IoT, the minimum requirement for frequency error is specified in TS 36.104 [4], subclause 6.5.1. + +#### 6.5.2.6 NR minimum requirement + +For NR, the minimum requirement for frequency error (BS type 1-C) is specified in TS 38.104 [17], subclause 6.5.1. + +### 6.5.3 Time alignment error + +This requirement applies to frame timing in: + +- UTRA single/multi-carrier transmissions, and their combinations with MIMO or TX diversity. +- E-UTRA single/multi-carrier transmissions, and their combinations with MIMO or TX diversity. +- NR single/multi-carrier transmissions, and their combinations with MIMO. +- E-UTRA Carrier Aggregation, with or without MIMO or TX diversity. +- NR Carrier Aggregation, with or without MIMO. +- NB-IoT transmissions with TX diversity. + +Frames of the WCDMA/LTE/NR/NB-IoT signals present at the BS transmitter antenna connector(s) are not perfectly aligned in time. In relation to each other, the RF signals present at the BS transmitter antenna connector(s) experience certain timing differences. + +For a specific set of signals/transmitter configuration/transmission mode, the Time Alignment Error (TAE) is defined as the largest timing difference between any two signals. + +#### 6.5.3.1 E-UTRA minimum Requirement + +For E-UTRA, the minimum requirement for time alignment is specified in TS 36.104 [4], subclause 6.5.3. + +#### 6.5.3.2 UTRA FDD minimum requirement + +For UTRA FDD, the minimum requirement for time alignment is specified in TS 25.104 [2], subclause 6.8.4. + +#### 6.5.3.3 UTRA TDD minimum requirement + +For UTRA TDD, the minimum requirement for time alignment is specified in TS 25.105 [3], subclause 6.8.5. + +#### 6.5.3.4 NB-IoT minimum Requirement + +For NB-IoT, the minimum requirement for time alignment is specified in TS 36.104 [4], subclause 6.5.3. + +#### 6.5.3.5 NR minimum Requirement + +For NR, the minimum requirement for time alignment (BS type 1-C) is specified in TS 38.104 [17], subclause 6.5.3. + +## 6.6 Unwanted emissions + +Unwanted emissions consist of out-of-band emissions and spurious emissions [6]. 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. 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 the BS transmitter is specified in terms of an Operating band unwanted emissions requirement that defines limits for emissions in each supported downlink operating band plus the frequency ranges $\Delta f_{\text{OBUE}}$ above and $\Delta f_{\text{OBUE}}$ below each band. Emissions outside of this frequency range are limited by a spurious emissions requirement. The values of $\Delta f_{\text{OBUE}}$ are defined in table 6.6-1. + +**Table 6.6-1: Maximum offset of OBUE outside the downlink operating band** + +| Operating band characteristics | $\Delta f_{\text{OBUE}}$ [MHz] | +|-----------------------------------------------------------------------------------|--------------------------------| +| $F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 200 \text{ MHz}$ | 10 | +| $200 \text{ MHz} < F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 900 \text{ MHz}$ | 40 | + +There is in addition a requirement for occupied bandwidth and an ACLR requirement applicable for some RATs. + +### 6.6.1 Transmitter spurious emissions + +The transmitter spurious emission limits apply from 9 kHz to 12.75 GHz, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the downlink operating band up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the downlink operating band. For BS capable of multi-band operation where multiple bands are mapped on the same antenna connector, this exclusion applies for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply and the multi-band exclusions and provisions are not applicable. + +Exceptions are the requirements in Table 6.6.1.3.1-2 and specifically stated exceptions in Table 6.6.1.3.1-1 that apply also closer than $\Delta f_{\text{OBUE}}$ from the downlink operating band. For some operating bands the upper frequency limit is higher than 12.75 GHz. + +The requirements shall apply whatever the type of transmitter considered. It applies for all transmission modes foreseen by the manufacturer's specification. Unless otherwise stated, all requirements are measured as mean power (RMS). + +#### 6.6.1.1 Mandatory Requirements + +The requirements of either subclause 6.6.1.1.1 (Category A limits) or subclause 6.6.1.1.2 (Category B limits) shall apply. In addition, for a BS operating in Band Category 2, the requirements of 6.6.1.1.3 shall apply in case of Category B limits when GSM/EDGE is configured. + +##### 6.6.1.1.1 Minimum requirement (Category A) + +The power of any spurious emission shall not exceed the limits in Table 6.6.1.1.1-1 + +**Table 6.6.1.1.1-1: BS Spurious emission limits, Category A** + +| Frequency range | Maximum level | Measurement Bandwidth | Note | +|--------------------------------------------------------------------------------------------------|---------------|-----------------------|----------------| +| 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 operating band in GHz | | 1 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [2], s4.1 +NOTE 2: Bandwidth as in ITU-R SM.329 [2], s4.1. Upper frequency as in ITU-R SM.329 [2], s2.5 table 1 +NOTE 3: This spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the DL *operating band* is reaching beyond 12.75 GHz. + +##### 6.6.1.1.2 Minimum requirement (Category B) + +The power of any spurious emission shall not exceed the limits in Table 6.6.1.1.2-1 + +**Table 6.6.1.1.2-1: BS Spurious emissions limits, Category B** + +| Frequency range | 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 operating band in GHz | -30 dBm | 1 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [2], s4.1 +NOTE 2: Bandwidth as in ITU-R SM.329 [2], s4.1. Upper frequency as in ITU-R SM.329 [2], s2.5 table 1 +NOTE 3: This spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the DL *operating band* is reaching beyond 12.75 GHz. + +##### 6.6.1.1.3 Additional minimum requirement for BC2 (Category B) + +For a BS operating in Band Category 2 when GSM/EDGE is configured, the power of any spurious emission shall not exceed the limits in Table 6.6.1.1.3-1. + +For BS capable of multi-band operation, the limits in Table 6.6.1.1.3-1 are only applicable when all supported operating bands belong to BC2 and GSM/EDGE is configured in all bands. + +**Table 6.6.1.1.3-1: Additional BS Spurious emissions limits for BC2, Category B** + +| Frequency range | Frequency offset from downlink operating band edge (Note1) | Maximum Level | Measurement Bandwidth | +|-----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|---------------|-----------------------| +| 500 MHz $\leftrightarrow$ 1 GHz | 10 – 20 MHz | -36 dBm | 300 kHz | +| | 20 – 30 MHz | -36 dBm | 1 MHz | +| | $\geq 30$ MHz | -36 dBm | 3 MHz | +| 1 GHz $\leftrightarrow$ 12.75 GHz | $\geq 30$ MHz | -30 dBm | 3 MHz | +| NOTE 1: For BS capable of multi-band operation, the frequency offset is relative to the closest operating band. | | | | + +#### 6.6.1.2 Protection of the BS receiver of own or different BS + +This requirement shall be applied for FDD operation in order to prevent the receivers of Base Stations being desensitised by emissions from the BS transmitter. It is measured at the transmit antenna port for any type of BS which has common or separate Tx/Rx antenna ports. + +##### 6.6.1.2.1 Minimum Requirement + +The power of any spurious emission shall not exceed the limits in Table 6.6.1.2.1-1 depending on the declared Base Station class and Band Category. + +**Table 6.6.1.2.1-1: BS Spurious emissions limits for protection of the BS receiver** + +| BS-class | Band category | Frequency range | Maximum Level | Measurement Bandwidth | Note | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|------------------------------|---------------|-----------------------|------| +| Wide Area BS | BC1 | $F_{UL\_low} - F_{UL\_high}$ | -96 dBm | 100 kHz | | +| Wide Area BS | BC2 | $F_{UL\_low} - F_{UL\_high}$ | -98 dBm | 100 kHz | | +| Medium Range BS | BC1, BC2 | $F_{UL\_low} - F_{UL\_high}$ | -91 dBm | 100 kHz | | +| Local Area BS | BC1, BC2 | $F_{UL\_low} - F_{UL\_high}$ | -88 dBm | 100 kHz | | +| Note 1: For E-UTRA Band 28 BS operating in regions where Band 28 is only partially allocated for E-UTRA operations, this requirement only applies in the UL frequency range of the partial allocation. | | | | | | + +#### 6.6.1.3 Additional spurious emissions requirements + +These requirements may be applied for the protection of system operating in frequency ranges other than the BS downlink operating band. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the BS, or they may be set by local or regional regulation as a mandatory requirement for an operating band. It is in some cases not stated in the present document whether a requirement is mandatory or under what exact circumstances that a limit applies, since this is set by local or regional regulation. An overview of regional requirements in the present document is given in subclause 4.4. + +Some requirements may apply for the protection of specific equipment (UE, MS and/or BS) or equipment operating in specific systems (GSM/EDGE, CDMA, UTRA, E-UTRA, NR, etc.) as listed below. + +##### 6.6.1.3.1 Minimum Requirement + +The power of any spurious emission shall not exceed the limits of Table 6.6.1.3.1-1 for a BS where requirements for co-existence with the system listed in the first column apply. For BS capable of multi-band operation, the exclusions and conditions in the Note column of Table 6.6.1.3.1-1 apply for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the exclusions and conditions in the Note column of Table 6.6.1.3.1-1 apply for the operating band supported at that antenna connector. + +**Table 6.6.1.3.1-1: BS Spurious emissions limits for co-existence with systems operating in other frequency bands** + +| System type to co-exist with | Frequency range for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|-----------------------------------------------------------------------|----------------------------------------------|---------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | -57 dBm | 100 kHz | This requirement does not apply to BS operating in band 8. | +| | 876 - 915 MHz | -61 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to BS operating in band 8, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| DCS1800
(Note 3) | 1805 - 1880 MHz | -47 dBm | 100 kHz | This requirement does not apply to BS operating in band 3. | +| | 1710 - 1785 MHz | -61 dBm | 100 kHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| PCS1900 | 1930 - 1990 MHz | -47 dBm | 100 kHz | This requirement does not apply to BS operating in band 2, 25, 36, 70. | +| | 1850 - 1910 MHz | -61 dBm | 100 kHz | This requirement does not apply to BS operating in band 2 or 25, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in band 35. | +| GSM850 or
CDMA850 | 869 - 894 MHz | -57 dBm | 100 kHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -61 dBm | 100 kHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| UTRA FDD Band I
or
E-UTRA Band 1 or
NR Band n1 | 2110 - 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, | +| | 1920 - 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| UTRA FDD Band II
or
E-UTRA Band 2 or
NR Band n2 | 1930 - 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25, 70. | +| | 1850 - 1910 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 2 or 25, since it is already covered by the requirement in sub-clause 6.6.1.2 | +| UTRA FDD Band III
or
E-UTRA Band 3 or
NR Band n3
(Note 3) | 1805 - 1880 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9. | +| | 1710 - 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in sub-clause 6.6.1.2.
For BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in sub-clause 6.6.1.2. | +| UTRA FDD Band IV
or
E-UTRA Band 4 | 2110 - 2155 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66 | +| | 1710 - 1755 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| UTRA FDD Band V
or
E-UTRA Band 5 or
NR Band n5 | 869 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | + +| | | | | | +|---------------------------------------------------------------|---------------------|---------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 824 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 18, 19 or NR Band n18 | 860 - 890 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 18, 19 | +| | 815 - 830 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 18 since it is already covered by the requirement in sub-clause 6.6.1.2. | +| | 830 - 845 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 19, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2620 - 2690 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 7. | +| | 2500 - 2570 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 7, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 - 960 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 8. | +| | 880 - 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 8, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9. | +| | 1749.9 - 1784.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10, 66 | +| | 1710 - 1770 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 10, 66, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 4, it applies for 1755 MHz to 1770 MHz, while the rest is covered in sub-clause 6.6.1.2. | +| 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 BS operating in band 11, 21, 32, 50, 74, 75 | +| | 1427.9 - 1447.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 11 or 74, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in band 32, 50, 51, 75, 76. | +| | 1447.9 – 1462.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 21 or 74, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in band 32, 50, 75 or n75. | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 729 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 12 or 85. | +| | 699 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 12 or 85, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7) | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 746 - 756 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 13. | +| | 777 - 787 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 13, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 758 - 768 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 14. | +| | 788 - 798 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 14, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| E-UTRA Band 17 | 734 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 17. | +| | 704 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 17, since it is already covered by the requirement in subclause 6.6.1.2. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7) | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 791 - 821 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, 28. | +| | 832 - 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, since it is already covered by the requirement in subclause 6.6.1.2. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, 42, 48, 49, 77 or 78. | +| | 3410 – 3490 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, since it is already covered by the requirement in subclause 6.6.1.2. This requirement does not apply to Band 42, 77 or 78. | +| E-UTRA Band 24 or NR Band n24 | 1525 – 1559 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 24. | +| | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 24, since it is already covered by the requirement in subclause 6.6.1.2. | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR Band n25 | 1930 - 1995 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25, 70. | +| | 1850 - 1915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 25, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in sub-clause 6.6.1.2. | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 814 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 26, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 5, it applies for 814 MHz to 824 MHz, while the rest is covered in sub-clause 6.6.1.2. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| E-UTRA Band 27 | 852 – 869 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in bands 5, 26 or 27. | + +| | | | | | +|---------------------------------------------------|-------------------|---------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 807 – 824 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 27, since it is already covered by the requirement in subclause 6.6.1.2. For BS operating in Band 26, it applies for 807 MHz to 814 MHz, while the rest is covered in sub-clause 6.6.1.2. This requirement also applies to BS operating in Band 28, starting 4 MHz above the Band 28 downlink operating band (Note 6). | +| E-UTRA Band 28 or NR Band n28 | 758 - 803 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, 28, 44, 67 or 68. | +| | 703 - 748 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in Band 44. For BS operating in Band 67, it applies for 703-736MHz. For E-UTRA BS operating in Band 68, it applies for 728MHz to 733MHz. | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 29 or 85. | +| E-UTRA Band 30 or NR Band n30 | 2350 - 2360 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 30 or 40. | +| | 2305 - 2315 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 30, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in Band 40. | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 452.5 – 457.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in band 72 or 73. | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50, 74, 75. | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR Band n34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 2, 25 or 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570 – 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 38 or 69. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR Band n39 | 1880 – 1920MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or NR Band n41 | 2496 – 2690MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42 43, 48, 49, 52, 77 or 78 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 42, 43, 48, 49, 77 or 78 | +| E-UTRA Band 44 | 703 - 803 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 - 1467 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 45 | + +| | | | | | +|-------------------------------|-------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 47 | 5855 - 5925 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 - 3700 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 77 or 78. | +| E-UTRA Band 49 | 3550 - 3700 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 77 or 78. | +| E-UTRA Band 50 or NR Band n50 | 1432 - 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | +| E-UTRA Band 51 or NR Band n51 | 1427 - 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75, 76. | +| E-UTRA Band 52 | 3300 – 3400 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 42 or 52 | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 41 or 53. | +| E-UTRA Band 54 or NR Band n54 | 1670 - 1675 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 54. | +| E-UTRA Band 65 or NR Band n65 | 2110 - 2200 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, | +| | 1920 - 2010 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 65, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 1, it applies for 1980 MHz to 2010 MHz, while the rest is covered in sub-clause 6.6.1.2. | +| E-UTRA Band 66 or NR Band n66 | 2110 - 2200 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10, 23, 66. | +| | 1710 - 1780 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 66, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in sub-clause 6.6.1.2. For BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in sub-clause 6.6.1.2. | +| E-UTRA Band 67 or NR band n67 | 738 – 758 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 28 or 67. | +| E-UTRA Band 68 | 753 -783 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, or 68. | +| | 698-728 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 68, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 28, it applies between 698 MHz and 703 MHz, while the rest is covered in sub-clause 6.6.1.2. | +| E-UTRA Band 69 | 2570 - 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 38 or 69. | +| E-UTRA Band 70 or NR Band n70 | 1995 - 2020 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25, 70 | +| | 1695 – 1710 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 70, since it is already covered by the requirement in sub-clause 6.6.1.2 | +| E-UTRA Band 71 or NR Band n71 | 617 – 652 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 71 | +| | 663 – 698 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 71, since it is already covered by the requirement in sub-clause 6.6.1.2 | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 451 - 456 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 72, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in band 73. | +| E-UTRA Band 73 | 460 - 465 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | + +| | | | | | +|-------------------------------|----------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 450 - 455 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 73, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| E-UTRA Band 74 or NR band n74 | 1475 – 1518 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50, 74, 75. | +| | 1427 – 1470 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in Band 74 or n74, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in band 32, 45, 50, 51, 75, 76. | +| E-UTRA Band 75 or NR Band n75 | 1432 - 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | +| E-UTRA Band 76 or NR Band n76 | 1427 - 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75, 76. | +| NR Band n77 | 3300 – 4200 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52, 77 or 78 | +| NR Band n78 | 3300 – 3800 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52, 77 or 78 | +| NR Band n79 | 4400 – 5000 MHz | -52 dBm | 1 MHz | | +| NR Band n80 | 1710 - 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in sub-clause 6.6.1.2.
For BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in sub-clause 6.6.1.2. | +| NR Band n81 | 880 - 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 8, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| NR Band n82 | 832 - 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, since it is already covered by the requirement in subclause 6.6.1.2. | +| NR Band n83 | 703 - 748 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in Band 44. For BS operating in Band 67, it applies for 703-736MHz. For E-UTRA BS operating in Band 68, it applies for 728MHz to 733MHz. | +| NR Band n84 | 1920 - 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| E-UTRA Band 85 or NR band n85 | 728 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 12, 29 or 85. | +| | 698 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 85, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7). | +| NR Band n86 | 1710 - 1780 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 66, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in sub-clause 6.6.1.2. For BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in sub-clause 6.6.1.2. | +| E-UTRA Band 87 | 420 - 425 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 87 or 88. | +| | 410 – 415 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 87, since it is already covered by the requirement in sub-clause 6.6.1.2 | +| E-UTRA Band 88 | 422 - 427 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 87 or 88. | + +| | | | | | +|---------------------------------|---------------------|---------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 412 - 417 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 88, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to E-UTRA BS operating in band 87. | +| NR Band n89 | 824 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in sub-clause 6.6.1.2. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| NR Band n91 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 50, 51, 75, 76. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 20, since it is already covered by the requirement in subclause 6.6.1.2. | +| NR Band n92 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 20, since it is already covered by the requirement in subclause 6.6.1.2. | +| NR Band n93 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 50, 51, 75, 76. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 8, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| NR Band n94 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 8, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| NR Band n95 | 2010 - 2025 MHz | -52 dBm | 1 MHz | | +| NR Band n96 | 5925 - 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n97 | 2300 - 2400MHz | -52 dBm | 1 MHz | | +| NR Band n98 | 1880 – 1920MHz | -52 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 24, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| NR Band n100 | 919.4 – 925 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 8. | +| | 874.4 – 880 MHz | -49 dBm | 1 MHz | | +| NR Band n101 | 1900 – 1910 MHz | -52 dBm | 1 MHz | | +| NR Band n102 | 5925 – 6425 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -52 dBm | 1 MHz | | +| | 787 – 788 MHz | -49 dBm | 1 MHz | | +| NR Band n104 | 6425 – 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n105 | 612 – 652 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 71 | +| | 663 – 703 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 106 or NR Band n106 | 935 - 940 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 106. | +| | 896 – 901 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in Band 106, since it is already covered by the requirement in clause 6.6.1.2. The requirement does not apply to BS operating in Band 5 or 26. | +| NR Band n109 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | + +| | | | | | +|--------------|---------------|---------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 703 – 733 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 28, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in Band 44. For E-UTRA BS operating in Band 68, it applies for 728MHz to 733MHz | +| NOTE 5: Void | | | | | + +- NOTE 1: As defined in the scope for spurious emissions in this subclause, except for the cases where the noted requirements apply to a BS operating in Band 25, Band 27, Band 28 or Band 29, the co-existence requirements in Table 6.6.1.3.1-1 do not apply for the 10 MHz frequency range immediately outside the downlink operating band (see Tables 4.5-1 and 4.5-2). Emission limits for this excluded frequency range may be covered by local or regional requirements. +- NOTE 2: Table 6.6.1.3.1-1 assumes that two operating bands, where the frequency ranges in Table 4.5-1 or Table 4.5-2 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 3: For the protection of DCS1800, UTRA Band III, E-UTRA Band 3 or NR Band n3 in China, the frequency ranges of the downlink and uplink protection requirements are 1805 – 1850 MHz and 1710 – 1755 MHz respectively. +- NOTE 4: TDD base stations deployed in the same geographical area, that are synchronized and use the same or adjacent operating bands can transmit without additional co-existence requirements. For unsynchronized base stations (except in Band 46), special co-existence requirements may apply that are not covered by the 3GPP specifications. +- NOTE 6: For Band 28 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with Band 27 UL operating band. +- NOTE 7: For Band 29 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with UTRA Band XII or E-UTRA Band 12 or NR Band n12 UL operating band or E-UTRA Band 17 UL operating band or E-UTRA Band 85 UL operating band. + +The following requirement may be applied for the protection of PHS. This requirement is also applicable at specified frequencies falling between $\Delta f_{\text{OBUE}}$ below the lowest BS transmitter frequency of the downlink operating band and $\Delta f_{\text{OBUE}}$ above the highest BS transmitter frequency of the downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.6.1.3.1-2: BS Spurious emissions limits for BS for co-existence with PHS** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|---------------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------| +| 1884.5 - 1915.7 MHz | -41 dBm | 300 kHz | Applicable for co-existence with PHS system operating in 1884.5-1915.7 MHz | +| NOTE: The requirement is not applicable in China. | | | | + +The following requirement may apply to BS operating in Band 41 in certain regions. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS downlink operating band up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS downlink operating band. + +For Band 41 NR operation in Japan, the operating band unwanted emissions limits shall be applied to the sum of the emission power over all *antenna connectors*. + +The power of any spurious emission shall not exceed: + +**Table 6.6.1.3.1-3: Additional BS Spurious emissions limits for BS operating in Band 41** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|-----------------------------------------------------------------------------|---------------|-----------------------|------| +| 2505MHz – 2535MHz | -42dBm | 1 MHz | | +| NOTE: This requirement applies for carriers allocated within 2545-2645 MHz. | | | | + +The following requirement may apply to BS operating in Band 30 in certain regions. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the BS downlink operating band up to 10 MHz above the highest frequency of the BS downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.6.1.3.1-4: Additional BS Spurious emissions limits for Band 30** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|---------------------|---------------|-----------------------|------| +| 2200MHz – 2345MHz | -45dBm | 1 MHz | | +| 2362.5MHz – 2365MHz | -25dBm | 1 MHz | | +| 2365MHz – 2367.5MHz | -40dBm | 1 MHz | | +| 2367.5MHz – 2370MHz | -42dBm | 1 MHz | | +| 2370MHz – 2395MHz | -45dBm | 1 MHz | | + +The following requirement may apply to BS operating in Band 48 in certain regions. The power of any spurious emission shall not exceed: + +**Table 6.6.1.3.1-5: Additional BS Spurious emissions limits for Band 48** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|----------------------------------------|---------------|-----------------------|-------------------------------------------------| +| 3530MHz – 3720MHz | -25dBm | 1 MHz | Applicable 10MHz from the assigned channel edge | +| 3100MHz – 3530MHz
3720MHz – 4200MHz | -40dBm | 1 MHz | | + +In addition to the requirements in subclauses 6.6.1.1, 6.6.1.2 and above in the present subclause, the BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +The following requirement may also apply to BS operating in Band 54 in certain regions. The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to Table 6.6.1.3.1-6 shall not exceed the maximum emission levels $P_{EM,B54,a}$ , $P_{EM,B54,b}$ , $P_{EM,B54,c}$ , $P_{EM,B54,d}$ , $P_{EM,B54,e}$ and $P_{EM,B54,f}$ declared by the manufacturer. + +**Table 6.6.1.3.1-6: Declared Band 54 emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range | Declared emission level (dBW) (Measurement bandwidth = 1 MHz) | Declared emission level (dBW) of discrete emissions of less than 700 Hz bandwidth (Measurement bandwidth = 1 kHz) | Declared emission level (dBW) of discrete emissions of less than 2 kHz bandwidth (Measurement bandwidth = 1 kHz) | +|----------------|-----------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| 54 | 1541 - 1559 MHz | $P_{EM,B54,a}$ | | $P_{EM,B54,f}$ | +| | 1559 - 1610 MHz | $P_{EM,B54,b}$ | $P_{EM,B54,d}$ | | +| | 1610 - 1650 MHz | $P_{EM,B54,c}$ | $P_{EM,B54,e}$ | | + +Note: The regional requirements specified in attachment to the FCC reference document, 0007135419, are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The EIRP level is calculated using: $P_{\text{EIRP}} = P_{\text{E}} + G_{\text{ant}}$ where $P_{\text{E}}$ denotes the BS unwanted emission level at the antenna connector, $G_{\text{ant}}$ equals the BS antenna gain minus feeder loss. The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. + +#### 6.6.1.4 Co-location with other base stations + +These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA, NB-IoT and/or NR BS are co-located with a BS. + +The requirements assume a 30 dB coupling loss between transmitter and receiver and are based on co-location with base stations of the same class. + +NOTE: For co-location with UTRA, the requirements are based on co-location with UTRA FDD or TDD base stations. + +##### 6.6.1.4.1 Minimum Requirement + +The power of any spurious emission shall not exceed the limits of Table 6.6.1.4.1-1 for a BS where requirements for co-location with a BS type listed in the first column apply, depending on the declared Base Station class. For BS capable of multi-band operation, the exclusions and conditions in the Note column of Table 6.6.1.4.1-1 apply for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the exclusions and conditions in the Note column of Table 6.6.1.4.1-1 apply for the operating band supported at that antenna connector. + +**Table 6.6.1.4.1-1: BS Spurious emissions limits for BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Bandwidth | Note | +|-----------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|-----------------------|---------------------------------------------------------------| +| GSM900 | 876-915 MHz | -98 dBm | -91 dBm | -88 dBm | 100 kHz | | +| DCS1800 | 1710 - 1785 MHz | -98 dBm | -91 dBm | -88 dBm | 100 kHz | | +| PCS1900 | 1850 - 1910 MHz | -98 dBm | -91 dBm | -88 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 - 849 MHz | -98 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 1920 - 1980 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1850 - 1910 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 | 1710 - 1785 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 824 - 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 - 845 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2500 - 2570 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 880 - 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1447.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 50, 51, 75, 76 | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 699 - 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 777 - 787 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 788 - 798 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 - 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | + +| | | | | | | | +|-----------------------------------------------------|---------------------|---------|---------|---------|---------|-----------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 18 or NR Band n18 | 815 - 830 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 832 - 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 32, 50, 75 | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 – 3490 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 77 or 78 | +| E-UTRA Band 24 or NR Band n24 | 1626.5 – 1660.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR Band n25 | 1850 - 1915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 814 - 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 27 | 807 - 824 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 28 or NR Band n28 | 703 – 748 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | +| E-UTRA Band 30 or NR Band n30 | 2305 - 2315 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 40 | +| E-UTRA Band 31 or NR Band n31 | 452.5 – 457.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR Band n34 | 2010 - 2025 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 2, n2 and 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | + +| | | | | | | | +|---------------------------------------------------|-------------------|---------|---------|---------|---------|---------------------------------------------------------------------------------| +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570 – 2620 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR Band n39 | 1880 – 1920MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 33 and 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or NR Band n41 | 2496 – 2690MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52, 77 or 78 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48, 49, 77 or 78 | +| E-UTRA Band 44 | 703 – 803 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48, 49, 77 or 78 | +| E-UTRA Band 49 | 3550 – 3700 MHz | N/A | N/A | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48, 49, 77 or 78 | +| E-UTRA Band 50 or NR Band n50 | 1432 – 1517 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 11, 21, 32, 51, n51, 74, 75, 76 | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 50, 75, 76 | +| E-UTRA Band 52 | 3300 – 3400 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42 or 52 | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | + +| | | | | | | | +|-------------------------------|---------------------|---------|---------|---------|---------|---------------------------------------------------------------------------------| +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 54 | +| E-UTRA Band 65 or NR Band n65 | 1920 - 2010 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 66 or NR Band n66 | 1710 – 1780 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 68 | 698 – 728 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 70 or NR Band n70 | 1695 – 1710 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 71 or NR Band n71 | 663 – 698 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 72 or NR Band n72 | 451 – 456 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 73 | 450 – 455 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 74 or NR band n74 | 1427 – 1470 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 50, 51 | +| NR Band n77 | 3300 – 4200 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42 43, 48, 49, 52, 77 or 78 | +| NR Band n78 | 3300 – 3800 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52, 77 or 78 | +| NR Band n79 | 4400 – 5000 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n80 | 1710 – 1785 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n81 | 880 – 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n82 | 832 – 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n83 | 703 – 748 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | +| NR Band n84 | 1920 – 1980 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 85 or NR band n85 | 698 - 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n86 | 1710 – 1780 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 87 | 410 - 415 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 88 | 412 - 417 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n89 | 824 - 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n91 | 832 – 862 MHz | N/A | N/A | -88 dBm | 100 kHz | | +| NR Band n92 | 832 – 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n93 | 880 – 915 MHz | N/A | N/A | -88 dBm | 100 kHz | | +| NR Band n94 | 880 – 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n95 | 2010 - 2025 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n96 | 5925 - 7125 MHz | N/A | -90dBm | -87 dBm | 100 kHz | | +| NR Band n97 | 2300 - 2400MHz | -96dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n98 | 1880 – 1920MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n100 | 874.4 – 880 MHz | -96 dBm | N/A | N/A | 100 kHz | | +| NR Band n101 | 1900 – 1910 MHz | -96 dBm | N/A | N/A | 100 kHz | | + +| | | | | | | | +|---------------------------------|-----------------|---------|---------|---------|---------|---------------------------------------------------| +| NR Band n102 | 5925 – 6425 MHz | N/A | -90dBm | -87 dBm | 100 kHz | | +| E-UTRA Band 103 | 787 – 788 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n104 | 6425 – 7125 MHz | -95 dBm | -90 dBm | -87 dBm | 100 kHz | | +| NR Band n105 | 663 – 703 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 106 or NR Band n106 | 896 – 901 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n109 | 703 – 733 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | + +NOTE 1: As defined in the scope for spurious emissions in this subclause, the co-location requirements in Table 6.6.1.4.1-1 do not apply for the $\Delta f_{OBUE}$ frequency range immediately outside the BS transmit frequency range of a downlink operating band (see Tables 4.5-1 and 4.5-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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [7]. + +NOTE 2: Table 6.6.1.4.1-1 assumes that two operating bands, where the corresponding BS transmit and receive frequency ranges in Table 4.5-1 or Table 4.5-2 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 3: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can transmit without special co-locations requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +### 6.6.2 Operating band unwanted emissions + +Unless otherwise stated, the Operating band unwanted emission limits are defined from $\Delta f_{OBUE}$ below the lowest frequency of each supported downlink operating band to the lower Base Station RF Bandwidth edge located at $F_{BW,RF,low}$ and from the upper Base Station RF Bandwidth edge located at $F_{BW,RF,high}$ up to $\Delta f_{OBUE}$ above the highest frequency of each supported downlink operating band. The values of $\Delta f_{OBUE}$ are defined in table 6.6-1. The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification, except for any operating band with GSM/EDGE single RAT operation. The requirements in TS 45.005 [5] as defined in subclause 6.6.2.3 apply to an MSR Base Station for any operating band with GSM/EDGE single RAT operation in Band Category 2. + +For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply and the cumulative evaluation of the emission limit in the Inter-RF Bandwidth gap are not applicable. + +#### 6.6.2.1 General minimum requirement for Band Categories 1 and 3 + +For a Wide Area BS operating in Band Category 1 or Band Category 3 the requirement applies outside the Base Station RF Bandwidth edges. In addition, for a Wide Area BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for a Wide Area BS operating in multiple bands, the requirements apply inside any Inter RF Bandwidth gap. + +For a Medium Range BS operating in Band Category 1 the requirement applies outside the Base Station RF Bandwidth edges. In addition, for a Medium Range BS operating in non-contiguous spectrum, it applies inside any sub-block gap. + +In addition, for a Medium Range BS operating in multiple bands, the requirements apply inside any Inter RF Bandwidth gap. + +For a Local Area BS operating in Band Category 1 the requirement applies outside the Base Station RF Bandwidth edges. In addition, for a Local Area BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for a Local Area BS operating in multiple bands, the requirements apply inside any Inter RF Bandwidth gap. + +Outside the Base Station RF Bandwidth edges, emissions shall not exceed the maximum levels specified in Tables 6.6.2.1-1 to 6.6.2.1-4 below, where: + +- $\Delta f$ is the separation between the Base Station RF Bandwidth edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is the offset to the frequency $\Delta f_{OBUE}$ outside the downlink operating band. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a BS operating in multiple bands, inside any Inter RF Bandwidth gaps with $W_{gap} < 2 * \Delta f_{OBUE}$ , emissions shall not exceed the cumulative sum of the minimum requirements specified at the Base Station RF Bandwidth edges on each side of the Inter-RF Bandwidth gap. The minimum requirement for Base Station RF Bandwidth edge is specified in Table 6.6.2.1-1 to 6.6.2.1-4 below, where in this case: + +- $\Delta f$ is the separation between the Base Station RF Bandwidth edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the inter Base Station RF Bandwidth gap minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For BS capable of multi-band operation where multiple bands are mapped on the same antenna connector, the operating band unwanted emission limits apply also in a supported operating band without any carriers transmitted, in the case where there are carriers transmitted in other operating band(s). In this case where there is no carrier transmitted in an operating band, the operating band unwanted emission limit, as defined in the tables of the present subclause for the largest frequency offset ( $\Delta f_{max}$ ), of a band where there is no carrier transmitted shall apply from $\Delta f_{OBUE}$ below the lowest frequency, up to $\Delta f_{OBUE}$ above the highest frequency of the supported downlink operating band without any carrier transmitted. And no cumulative limits are applied in the inter-band gap between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted. + +Inside any sub-block gap for a BS operating in non-contiguous spectrum, emissions shall not exceed the cumulative sum of the minimum requirements specified for the adjacent sub blocks on each side of the sub block gap. The minimum requirement for each sub block is specified in Tables 6.6.2.1-1 to 6.6.2.1-4 below, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f\_offset$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the sub block gap bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For Band 41 NR operation in Japan, the operating band unwanted emissions limits shall be applied to the sum of the emission power over all *antenna connectors*. + +Applicability of Wide Area operating band unwanted emission requirements in Tables 6.6.2.1-1, 6.6.2.1-1b and 6.6.2.1-1c is specified in Table 6.6.2.1-0. + +Note: Option 1 and Option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [4] and TS 38.104 [17]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [2]. + +**Table 6.6.2.1-0: Applicability of operating band unwanted emission requirements for BC1 and BC3 Wide Area BS** + +| NR Band operation | Standalone NB-IoT carrier adjacent to the BS RF bandwidth edge or UTRA supported | Applicable requirement table | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------| +| None | Y/N | 6.6.2.1-1 (Option 2) | +| In certain regions (NOTE 2), bands 1, 7, 38, 65 | N | 6.6.2.1-1 (Option 2) | +| Any | Y | 6.6.2.1-1 (Option 2) | +| Any below 1GHz | N | 6.6.2.1-1b (Option 1) | +| Any above 1GHz except for, in certain regions (NOTE 2), bands 1, 7, 38, 65 | N | 6.6.2.1-1c (Option 1) | +| NOTE 1: Void
NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [6] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [4] and TS 38.104 [17] are applied. | | | + +**Table 6.6.2.1-1: WA BS OBUE in BC1 and BC3 bands – option 2.** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-14 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$
(Note 4) | 30 kHz | +| (Note 6) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm (Note 4) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -13 dBm (Note 4) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 4, 8) | 1 MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the sub-block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -15dBm/MHz (for MSR BS supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands <1GHz). + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.1-1a apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 4: For MSR BS supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ , whichever is less stringent, shall apply for operating bands <1GHz. + +**Table 6.6.2.1-1a: WA BS OBUE in BC1 and BC3 bands applicable for: BS with standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2, 3, 4) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $Max(5dBm - 60 \cdot \left( \frac{f\_offset}{MHz} - 0.015 \right) dB + XdB, -14dBm)$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $Max(2dBm - 160 \cdot \left( \frac{f\_offset}{MHz} - 0.065 \right) dB + XdB, -14dBm)$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{OBUE}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the RF bandwidth edge is a standalone NB-IoT carrier, the value of $X = P_{NB-IoTcarrier} - 43$ , where $P_{NB-IoTcarrier}$ is the power level of the standalone NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +**Table 6.6.2.1-1b: WA BS OBUE in BC1 and BC3 bands $\leq 1 \text{ GHz}$ - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|----------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7dBm - \frac{7}{5} \cdot \left( \frac{f\_offset}{MHz} - 0.05 \right) dB$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -16 dBm (Note 8) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -16dBm/100kHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{OBUE}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +Table 6.6.2.1-1c: WA BS OBUE in BC1 and BC3 bands > 1 GHz - option 1 + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 8) | 1MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -15dBm/1MHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +Table 6.6.2.1-2: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38 \text{ dBm}$ and not supporting NR; or BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38 \text{ dBm}$ , supporting NR, and supporting UTRA + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{Rated,c}} - 58 \text{ dB} - 5/3(f\_offset/\text{MHz} - 0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{Rated,c}} - 53 \text{ dB} - 15(f\_offset/\text{MHz} - 0.215) \text{ dB}$ | 30 kHz | +| (Note 6) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{Rated,c}} - 65 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.1 \text{ MHz}$ | $P_{\text{Rated,c}} - 52 \text{ dB}$ | 1 MHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.1 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{Rated,c}} - 52 \text{ dB}, -15 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P_{\text{Rated,c}} - 56 \text{ dB}$ (Note 8) | 1 MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $(P_{\text{Rated,c}} - 56 \text{ dB}) / \text{MHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.1-2a apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.1-2a: MR BS OBUE in BC1 and BC3 bands applicable for: BS with maximum output power $31 < P_{\text{Rated}} \leq 38$ dBm and with standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2, 3) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$
(Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $P_{\text{Rated,c}} - 38 \text{ dB} - 60(f\_offset/\text{MHz} - 0.015) \text{ dB}$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $P_{\text{Rated,c}} - 41 \text{ dB} - 160(f\_offset/\text{MHz} - 0.065) \text{ dB}$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.2.1-2b: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{Rated,c}} - 53 \text{ dB} - 7.5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{Rated,c}} - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{Rated,c}} - 60 \text{ dB}, -25 \text{ dBm})$ (Note 8) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $\min(P_{\text{Rated,c}} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.1-2a apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.1-3: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm and not supporting NR; or BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm, supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-27 \text{ dBm} - \frac{5}{3} \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-22 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz | +| (Note 6) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -34 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -21 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm | 1 MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be - 25 dBm/MHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.1-3a apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.1-3a: MR BS OBUE in BC1 and BC3 bands applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm BS and standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2, 3, 4) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$
(Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $\text{Max}(-7 \text{ dBm} - 60 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB} + X \text{ dB}, -27 \text{ dBm})$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $\text{Max}(-10 \text{ dBm} - 160 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.065 \right) \text{ dB} + X \text{ dB}, -27 \text{ dBm})$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the RF bandwidth edge is a standalone NB-IoT carrier, the value of $X = P_{\text{NB-IoTcarrier}} - 31$ , where $P_{\text{NB-IoTcarrier}}$ is the power level of the standalone NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +**Table 6.6.2.1-3b: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-22 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -29 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -29 dBm (Note 8) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -29dBm/100kHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.1-3a apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.1-4: LA BS OBUE in BC1 bands** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-30 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -37 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 8) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -37dBm/100 kHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.1-14a apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.1-4a: LA BS OBUE in BC1 and BC3 bands applicable for: BS with standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2, 3, 4) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$
(Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $\text{Max}(-14\text{dBm} - 60 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{dB} + X\text{dB}, -35\text{dBm})$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.175 \text{ MHz}$ | $\text{Max}(-17\text{dBm} - 160 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.065 \right) \text{dB} + X\text{dB}, -35\text{dBm})$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the RF bandwidth edge is a standalone NB-IoT carrier, the value of $X = \text{PNB-IoTCarrier} - 24$ , where $\text{PNB-IoTCarrier}$ is the power level of the standalone NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +#### 6.6.2.2 General minimum requirement for Band Category 2 + +For a BS operating in Band Category 2 the requirement applies outside the Base Station RF Bandwidth edges. In addition, for a BS operating in non-contiguous spectrum, it applies inside any sub-block gap. + +Outside the Base Station RF Bandwidth edges, emissions shall not exceed the maximum levels specified in Tables 6.6.2.2-1 to 6.6.2.2-8 below, where: + +- $\Delta f$ is the separation between the Base Station RF Bandwidth edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter. +- $f\_offset_{\text{max}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink operating band. +- $\Delta f_{\text{max}}$ is equal to $f\_offset_{\text{max}}$ minus half of the bandwidth of the measuring filter. + +For a BS operating in multiple bands, inside any Inter-RF Bandwidth gaps with $W_{\text{gap}} < 2 \times \Delta f_{\text{OBUE}}$ , emissions shall not exceed the cumulative sum of the minimum requirements specified at the Base Station RF Bandwidth edges on each side of the Inter-RF Bandwidth gap. The minimum requirement for Base Station RF Bandwidth edge is specified in Table 6.6.2.2-1 to 6.6.2.2-8 below, where in this case: + +- $\Delta f$ is the separation between the Base Station RF Bandwidth edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter. +- $f\_offset_{\text{max}}$ is equal to the Inter RF Bandwidth gap minus half of the bandwidth of the measuring filter. +- $\Delta f_{\text{max}}$ is equal to $f\_offset_{\text{max}}$ minus half of the bandwidth of the measuring filter. + +For a BS capable of multi-band operation where multiple bands are mapped on the same antenna connector and where there is no carrier transmitted in an operating band, the operating band unwanted emission limit, as defined in the tables of the present subclause for the largest frequency offset ( $\Delta f_{\text{max}}$ ), of a band where there is no carrier transmitted shall apply from $\Delta f_{\text{OBUE}}$ below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the supported downlink + +operating band without any carrier transmitted. And no cumulative limits are applied in the inter-band gap between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted. + +Inside any sub-block gap for a BS operating in non-contiguous spectrum, emissions shall not exceed the cumulative sum of the minimum requirement specified for the adjacent sub blocks on each side of the sub block gap. The minimum requirement for each sub block is specified in Tables 6.6.2.2-1 to 6.6.2.2-8 below, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f\_offset$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the sub block gap bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +Applicability of Wide Area operating band unwanted emission requirements in Tables 6.6.2.2-1, 6.6.2.2-2a and 6.6.2.2-2b is specified in Table 6.6.2.2-0. + +Note: Option 1 and option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [4] and TS 38.104 [17]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [2] with GSM related modifications. + +**Table 6.6.2.2-0: Applicability of operating band unwanted emission requirements for BC2 Wide Area BS** + +| NR Band operation | Standalone NB-IoT carrier adjacent to the BS RF bandwidth edge or EUTRA or GSM supported | Applicable requirement table | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|------------------------------| +| None | Y/N | 6.6.2.2-1 (option 2) | +| In certain regions (NOTE 2), bands 3, 8 | N | 6.6.2.2-1 (option 2) | +| Any | Y | 6.6.2.2-1 (option 2) | +| Any below 1 GHz except for, in certain regions (NOTE 2), band 8 | N | 6.6.2.2-2a (option 1) | +| Any above 1 GHz except for, in certain regions (NOTE 2), band 3 | N | 6.6.2.2-2b (option 1) | +| NOTE 1: Void.
NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [6] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [4] and TS 38.104 [17] are applied. | | | + +Table 6.6.2.2-1: WA BS OBUE in BC2 bands - option 2. + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 2, 3) | Measurement bandwidth (Note 7) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$
(Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-14 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$
(Note 4) | 30 kHz | +| (Note 6) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm (Note 4) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -13 dBm (Note 4) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 4, 8) | 1 MHz | + +NOTE 1: For operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.2-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the sub-block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -15dBm/MHz (for MSR BS supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ ). + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ operation the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 4: For MSR BS supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ . + +**Table 6.6.2.2-2: WA BS OBUE in BC2 bands applicable for: BS with GSM/EDGE or standalone NB-IoT or E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2, 3,4, 5) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $Max(5dBm - 60 \cdot \left( \frac{f\_offset}{MHz} - 0.015 \right) dB + X dB, -14dBm)$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $Max(2dBm - 160 \cdot \left( \frac{f\_offset}{MHz} - 0.065 \right) dB + X dB, -14dBm)$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{OBUE}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge is a GSM/EDGE carrier, the value of $X = P_{GSMcarrier} - 43$ , where $P_{GSMcarrier}$ is the power level of the GSM/EDGE carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. In other cases, $X = 0$ . + +NOTE 5: In case the carrier adjacent to the RF bandwidth edge is a NB-IoT carrier, the value of $X = P_{NB-IoTcarrier} - 43$ , where $P_{NB-IoTcarrier}$ is the power level of the NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +**Table 6.6.2.2-2a: WA BS OBUE in BC2 bands $\leq 1 \text{ GHz}$ - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|----------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7dBm - \frac{7}{5} \cdot \left( \frac{f\_offset}{MHz} - 0.05 \right) dB$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -16 dBm (Note 8) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -16dBm/100kHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{OBUE}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with an E-UTRA 1.4 or 3MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.2-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +Table 6.6.2.2-2b: WA BS OBUE in BC2 bands > 1 GHz - option 1 + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 8) | 1MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -15dBm/1MHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with an E-UTRA 1.4 or 3MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.2-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +Table 6.6.2.2-3: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38 \text{ dBm}$ and not supporting NR; or BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38 \text{ dBm}$ and supporting NR with UTRA and/or GSM + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 2, 3) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{Rated,c}} - 58 \text{ dB} - 5/3(f\_offset/\text{MHz} - 0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{Rated,c}} - 53 \text{ dB} - 15(f\_offset/\text{MHz} - 0.215) \text{ dB}$ | 30 kHz | +| (Note 6) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{Rated,c}} - 65 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | $P_{\text{Rated,c}} - 52 \text{ dB}$ | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.3 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{Rated,c}} - 52 \text{ dB}, -15 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P_{\text{Rated,c}} - 56 \text{ dB}$ (Note 8) | 1 MHz | + +NOTE 1: For operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.2-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $(P_{\text{Rated,c}} - 56 \text{ dB})/\text{MHz}$ . + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 6.6.2.2-3a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm, supporting NR, not supporting UTRA, and not supporting GSM** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{Rated,c}} - 53\text{dB} - 7/5(f\_offset/\text{MHz} - 0.05)\text{dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{Rated,c}} - 60\text{dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{Rated,c}} - 60\text{dB}, -25\text{dBm})$ (Note 8) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10\text{MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $\min(P_{\text{Rated,c}} - 60\text{dB}, -25\text{dBm})/100\text{kHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT or an E-UTRA 1.4 or 3MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.2-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.2-4: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm and not supporting NR; or BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm and supporting NR with UTRA and/or GSM** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 2, 3) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------| +| 0 MHz $\leq \Delta f < 0.6$ MHz (Note 1) | 0.015MHz $\leq f\_offset < 0.615$ MHz | $-27\text{dBm} - \frac{5}{3} \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{dB}$ | 30 kHz | +| 0.6 MHz $\leq \Delta f < 1$ MHz | 0.615MHz $\leq f\_offset < 1.015$ MHz | $-22\text{dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{dB}$ | 30 kHz | +| (Note 6) | 1.015MHz $\leq f\_offset < 1.5$ MHz | -34 dBm | 30 kHz | +| 1 MHz $\leq \Delta f \leq 5$ MHz | 1.5 MHz $\leq f\_offset < 5.5$ MHz | -21 dBm | 1 MHz | +| 5 MHz $\leq \Delta f \leq \Delta f_{\text{max}}$ | 5.5 MHz $\leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm (Note 8) | 1 MHz | + +NOTE 1: For operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.2-6 apply for 0 MHz $\leq \Delta f < 0.15$ MHz. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10$ MHz from both adjacent sub-blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -25dBm/MHz. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 6.6.2.2-4a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm, supporting NR, not supporting UTRA, and not supporting GSM** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|--------------------------------------------------------------------|----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------| +| 0 MHz $\leq \Delta f < 5$ MHz | 0.05 MHz $\leq f\_offset < 5.05$ MHz | $-22\text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{dB}$ | 100 kHz | +| 5 MHz $\leq \Delta f < \min(10\text{ MHz}, \Delta f_{\text{max}})$ | 5.05 MHz $\leq f\_offset < \min(10.05\text{ MHz}, f\_offset_{\text{max}})$ | -29 dBm | 100 kHz | +| 10 MHz $\leq \Delta f \leq \Delta f_{\text{max}}$ | 10.05 MHz $\leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm (Note 8) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10$ MHz from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -29dBm/100kHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT or an E-UTRA 1.4 or 3MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.2-6 apply for 0 MHz $\leq \Delta f < 0.15$ MHz. + +**Table 6.6.2.2-5: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm and with GSM/EDGE or E-UTRA 1.4 or 3 MHz carriers or standalone NB-IoT adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 2, 3) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $P_{\text{Rated,c}} - 38 \text{ dB} - 60(f\_offset/\text{MHz} - 0.015) \text{ dB}$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $P_{\text{Rated,c}} - 41 \text{ dB} - 160(f\_offset/\text{MHz} - 0.065) \text{ dB}$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.2.2-6: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31 \text{ dBm}$ and with GSM/EDGE or E-UTRA 1.4 or 3 MHz carriers or standalone NB-IoT adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 2, 3, 4) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $\text{Max}(-7 \text{ dBm} - 60 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB} + X \text{ dB}, -27 \text{ dBm})$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $\text{Max}(-10 \text{ dBm} - 160 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.065 \right) \text{ dB} + X \text{ dB}, -27 \text{ dBm})$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge is a GSM/EDGE carrier, the value of $X = P_{\text{GSMcarrier}} - 31$ , where $P_{\text{GSMcarrier}}$ is the power level of the GSM/EDGE carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. In other cases, $X = 0$ . + +NOTE 5: In case the carrier adjacent to the RF bandwidth edge is a NB-IoT carrier, the value of $X = P_{\text{NB-IoTcarrier}} - 31$ , where $P_{\text{NB-IoTcarrier}}$ is the power level of the NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +Table 6.6.2.2-7: LA BS OBUE in BC2 bands + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 2, 3) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ (Note 1) | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-30 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -37 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 8) | 100 kHz | + +NOTE 1: For operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.2-8 apply for $0 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ . + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -37 dBm/100 kHz. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +Table 6.6.2.2-8: LA BS OBUE in BC2 bands applicable for: BS with GSM/EDGE or E-UTRA 1.4 or 3 MHz carriers or standalone NB-IoT adjacent to the Base Station RF Bandwidth edge or the sub-block edge + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 2, 3, 4) | Measurement bandwidth (Note 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $\text{Max}(-14 \text{ dBm} - 60 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB} + X \text{ dB}, -35 \text{ dBm})$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.175 \text{ MHz}$ | $\text{Max}(-17 \text{ dBm} - 160 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.065 \right) \text{ dB} + X \text{ dB}, -35 \text{ dBm})$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the RF bandwidth edge is a GSM/EDGE carrier, the value of $X = P_{\text{GSMcarrier}} - 24$ , where $P_{\text{GSMcarrier}}$ is the power level of the GSM/EDGE carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. In other cases, $X = 0$ . + +NOTE 5: In case the carrier adjacent to the RF bandwidth edge is a NB-IoT carrier, the value of $X = P_{\text{NB-IoTcarrier}} - 24$ , where $P_{\text{NB-IoTcarrier}}$ is the power level of the NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +The following notes are common to all subclauses in 6.6.2: + +NOTE 6: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 7: As a general rule for the requirements in the present subclause, 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 may 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. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < \Delta f_{\text{OBUE}}$ . + +NOTE 9: All limits in Table 6.6.2.2-1, Table 6.6.2.2-3, Table 6.6.2.2-4 and Table 6.6.2.2-7 are identical to the corresponding limits for Band Category 1 and 3. + +#### 6.6.2.3 GSM/EDGE single-RAT requirements + +The following requirements in TS 45.005 [5] shall apply to an MSR Base Station for any operating band with GSM/EDGE single RAT operation in Band Category 2: + +- Spectrum due to the modulation and wide band noise, applicable parts of subclause 4.2.1.1, 4.2.1.2, 4.2.1.3-a2, 4.2.1.3-b2, 4.2.1.3-c2 and 4.2.1.4.2. +- Spectrum due to switching transients, applicable parts of subclause 4.2.2.1-b. +- Emission requirement for frequency offsets of between 2 and 10 MHz outside relevant transmit band, applicable parts of subclause 4.3.1 and 4.3.2.1. +- Intra BTS Intermodulation, applicable parts of subclause 4.7.2, 4.7.2.1-b, 4.7.2.3-b and 4.7.2.3-c. + +#### 6.6.2.4 Additional requirements + +##### 6.6.2.4.1 Limits in FCC Title 47 + +In addition to the requirements in subclauses 6.6.2.1 and 6.6.2.2, the BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +##### 6.6.2.4.2 Unsynchronized operation for BC3 + +In certain regions, the following requirements may apply to a TDD BS operating in BC3 in the same geographic area and in the same operating band as another TDD system without synchronisation. For this case the emissions shall not exceed -52 dBm/MHz in each supported downlink operating band except in: + +- The frequency range from 10 MHz below the lower Base Station RF Bandwidth edge to the frequency 10 MHz above the upper Base Station RF Bandwidth edge of each supported band. + +NOTE 1: Local or regional regulations may specify another excluded frequency range, which may include frequencies where synchronised TDD systems operate. + +NOTE 2: TDD base stations that are synchronized and operating in BC3 can transmit without these additional co-existence requirements. + +NOTE 3: Unsynchronized operation for BC3 BS with any NR configuration is not covered by the present release of this specification. + +##### 6.6.2.4.3 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For a BS operating in Band 20, the level of emissions in the band 470-790 MHz, measured in an 8 MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to Table 6.6.2.4.3-1, shall not exceed the maximum emission level $P_{\text{EM,N}}$ declared by the manufacturer. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 6.6.2.4.3-1: Declared emissions levels for protection of DTT** + +| Filter centre frequency,
$F_{\text{filter}}$ | 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 BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in Annex G of TS 36.104 [4]. + +##### 6.6.2.4.4 Void + +**Table 6.6.2.4.4-1: Void** + +##### 6.6.2.4.5 Co-existence with RNSS/GPS services in North America + +In regions where FCC regulation applies, requirements for protection of GPS according to FCC Order DA 20-48 applies for operation in Band 24. The following normative requirement covers the base station, to be used together with other information about the site installation to verify compliance with the requirement in FCC Order DA 20-48. The requirement applies to BS operating in Band 24 to ensure that appropriate interference protection is provided to the 1541 – 1650 MHz band. This requirement applies to the frequency range 1541-1650 MHz. + +The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to Table 6.6.2.4.5-1 shall not exceed the maximum emission levels $P_{EM,B24,a}$ , $P_{EM,B24,b}$ , $P_{EM,B24,c}$ , $P_{EM,B24,d}$ , $P_{EM,B24,e}$ and $P_{EM,B24,f}$ declared by the manufacturer. + +**Table 6.6.2.4.5-1: Declared emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range | Declared emission level (dBW)
(Measurement bandwidth = 1 MHz) | Declared emission level (dBW) of discrete emissions of less than 700 Hz bandwidth
(Measurement bandwidth = 1 kHz) | Declared emission level (dBW) of discrete emissions of less than 2 kHz bandwidth
(Measurement bandwidth = 1 kHz) | +|----------------|-----------------|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| 24 | 1541 - 1559 MHz | $P_{EM,B24,a}$ | | $P_{EM,B24,f}$ | +| | 1559 - 1610 MHz | $P_{EM,B24,b}$ | $P_{EM,B24,d}$ | | +| | 1610 - 1650 MHz | $P_{EM,B24,c}$ | $P_{EM,B24,e}$ | | + +Note: The regional requirements in FCC Order DA 20-48 are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The EIRP level is calculated using: $P_{EIRP} = P_E + G_{ant}$ where $P_E$ denotes the BS unwanted emission level at the antenna connector, $G_{ant}$ equals the BS antenna gain minus feeder loss. The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. + +##### 6.6.2.4.6 Void + +**Table 6.6.2.4.6-1: Void** + +##### 6.6.2.4.7 Additional band 32, 50, 51, 74, 75 and 76 unwanted emissions + +In certain regions, the following requirements may apply to BS operating in Band 32 within 1452-1492 MHz, in Band 75 within 1432-1517 MHz and in Band 76 within 1427-1432 MHz. The level of operating band unwanted emissions, measured on centre frequencies $f_{offset}$ with filter bandwidth, according to Table 6.6.2.4.7-1, shall neither exceed the maximum emission level $P_{EM,B32,B75,B76,a}$ , $P_{EM,B32,B75,B76,b}$ nor $P_{EM,B32,B75,B76,c}$ declared by the manufacturer. + +For Band 32, this requirement applies in the frequency range 1452-1492 MHz when non-Mobile/Fixed Communications Network (MFCN) services are deployed in adjacent frequency ranges, while it applies also within 1427-1452 MHz and/or 1492-1517 MHz when MFCN services are deployed in such frequency ranges, even though part of the ranges falls in the spurious domain. For Band 75, this requirement applies in the frequency range 1427-1517 + +MHz. For Band 76, this requirement applies in the frequency range 1432-1517 MHz even though part of the range falls in the spurious domain. + +**Table 6.6.2.4.7-1: Declared operating band 32, 75, 76 unwanted emission within 1427-1517 MHz** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Declared emission level [dBm] | Measurement bandwidth | +|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| 2.5 MHz | $P_{EM,B32,B75,B76,a}$ | 5 MHz | +| 7.5 MHz | $P_{EM,B32,B75,B76,b}$ | 5 MHz | +| $12.5 \text{ MHz} \leq f\_offset \leq f\_offset_{max}$ | $P_{EM,B32,B75,B76,c}$ | 5 MHz | +| NOTE: | For Band 32, when non-MFCN services are deployed in the adjacent bands, $f\_offset_{max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1454.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1489.5 MHz for the set channel position. For Band 32, when MFCN services are deployed in the adjacent frequencies, Band 75, n75, 76 and n76, $f\_offset_{max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1429.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1514.5 MHz for the set channel position. | | + +NOTE: The regional requirement, included in [16], is defined in terms of EIRP per antenna, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS 36.104 [4]. + +In certain regions, the following requirement may apply to BS operating in Band 32 within 1452-1492MHz for the protection of non-MFCN services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{filter}$ with filter bandwidth according to Table 6.6.2.4.7-2, shall neither exceed the maximum emission level $P_{EM,B32,d}$ nor $P_{EM,B32,e}$ declared by the manufacturer. This requirement applies in the frequency range 1429-1518MHz even though part of the range falls in the spurious domain. + +**Table 6.6.2.4.7-2: Operating band 32 declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{filter}$ | Declared emission level [dBm] | Measurement bandwidth | +|--------------------------------------------------------------|-------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{filter} \leq 1448.5 \text{ MHz}$ | $P_{EM,B32,d}$ | 1 MHz | +| $F_{filter} = 1450.5 \text{ MHz}$ | $P_{EM,B32,e}$ | 3 MHz | +| $F_{filter} = 1493.5 \text{ MHz}$ | $P_{EM,B32,e}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{filter} \leq 1517.5 \text{ MHz}$ | $P_{EM,B32,d}$ | 1 MHz | + +NOTE: The regional requirement, included in [15], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS 36.104 [4]. + +In certain regions, the following requirement may apply to BS operating in Band 50 and Band 75 within 1492-1517 MHz and in Band 74 within 1492-1518 MHz. The level of emissions, measured on centre frequencies $F_{filter}$ with filter bandwidth according to Table 6.6.2.4.7-3, shall neither exceed the maximum emission level $P_{EM,B50,B74,B75,a}$ nor $P_{EM,B50,B74,B75,b}$ declared by the manufacturer. + +**Table 6.6.2.4.7-3: Operating band 50, 74 and 75 declared emission above 1518 MHz** + +| Filter centre frequency, $F_{filter}$ | Declared emission level [dBm] | Measurement bandwidth | +|--------------------------------------------------------------|-------------------------------|-----------------------| +| $1518.5 \text{ MHz} \leq F_{filter} \leq 1519.5 \text{ MHz}$ | $P_{EM,B50,B74,B75,a}$ | 1 MHz | +| $1520.5 \text{ MHz} \leq F_{filter} \leq 1558.5 \text{ MHz}$ | $P_{EM,B50,B74,B75,b}$ | 1 MHz | + +NOTE: The regional requirement, included in [16], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H. + +In certain regions, the following requirement may apply to NR or E-UTRA BS operating in Band 50 and Band 75 within 1432-1452 MHz, and in Band 51 and Band 76. Emissions shall not exceed the maximum levels specified in Table 6.6.2.4.7-4. + +**Table 6.6.2.4.7-4: Additional operating band unwanted emission limits for BS operating in Band 50 and 75 within 1432-1452 MHz, and in Band 51 and 76** + +| Filter centre frequency, $F_{\text{filter}}$ | Maximum Level [dBm] | Measurement Bandwidth | +|----------------------------------------------|---------------------|-----------------------| +| $F_{\text{filter}} = 1413.5 \text{ MHz}$ | -42 | 27 MHz | + +##### 6.6.2.4.8 Additional requirements for band 45 + +In certain regions the following requirement may apply to E-UTRA BS operating in Band 45. Emissions shall not exceed the maximum levels specified in Table 6.6.2.4.8-1. + +**Table 6.6.2.4.8-1: Emissions limits for protection of adjacent band services** + +| Operating Band | Filter centre frequency, $F_{\text{filter}}$ | Maximum Level [dBm] | Measurement Bandwidth | +|----------------|---------------------------------------------------------------------|---------------------|-----------------------| +| 45 | $F_{\text{filter}} = 1467.5$ | -20 | 1 MHz | +| | $F_{\text{filter}} = 1468.5$ | -23 | 1 MHz | +| | $F_{\text{filter}} = 1469.5$ | -26 | 1 MHz | +| | $F_{\text{filter}} = 1470.5$ | -33 | 1 MHz | +| | $F_{\text{filter}} = 1471.5$ | -40 | 1 MHz | +| | $1472.5 \text{ MHz} \leq F_{\text{filter}} \leq 1491.5 \text{ MHz}$ | -47 | 1 MHz | + +##### 6.6.2.4.9 Additional requirements for band 48 + +The following requirement may apply to BS operating in Band 48 in certain regions. Emissions shall not exceed the maximum levels specified in Table 6.6.2.4.9-1. + +**Table 6.6.2.4.9-1: Additional operating band unwanted emission limits for Band 48** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Minimum requirement | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|------------------------------------------------------------------------------|---------------------|-----------------------| +| All | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f_{\text{offset}} < 9.5 \text{ MHz}$ | -13 dBm | 1 MHz | + +##### 6.6.2.4.10 Additional requirements for band 53 + +The following requirement may apply to BS operating in Band 53 in certain regions. Emissions shall not exceed the maximum levels specified in Table 6.6.2.4.10-1. + +**Table 6.6.2.4.10-1: Additional operating band unwanted emission limits for Band 53** + +| Channel bandwidth [MHz] | Frequency range [MHz] | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth | +|-------------------------|-----------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| 1.4, 3, 5 | 2400 - 2477.5 | $6 \text{ MHz} \leq \Delta f < 83.5 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 83 \text{ MHz}$ | -25 dBm | 1 MHz | +| 10 | 2400 - 2473.5 | $10 \text{ MHz} \leq \Delta f < 83.5 \text{ MHz}$ | $10.5 \text{ MHz} \leq f\_offset < 83 \text{ MHz}$ | -25 dBm | 1 MHz | +| 1.4, 3, 5 | 2477.5 - 2478.5 | $5 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | 5.5 MHz | -13 dBm | 1 MHz | +| 10 | 2473.5 - 2478.5 | $5 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $5.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| All | 2478.5 - 2483.5 | $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 4.5 \text{ MHz}$ | -10 dBm | 1 MHz | +| 1.4, 3, 5 | 2495 - 2501 | $0 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| 10 | 2495 - 2505 | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| 1.4, 3, 5 | 2501 - 2690 | $6 \text{ MHz} \leq \Delta f < 195 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 194.5 \text{ MHz}$ | -25 dBm | 1 MHz | +| 10 | 2505 - 2690 | $10 \text{ MHz} \leq \Delta f < 195 \text{ MHz}$ | $10.5 \text{ MHz} \leq f\_offset < 194.5 \text{ MHz}$ | -25 dBm | 1 MHz | + +### 6.6.3 Occupied bandwidth + +The occupied bandwidth is the width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage $\beta/2$ of the total mean transmitted power. See also ITU-R Recommendation SM.328 [11]. + +The value of $\beta/2$ shall be taken as 0.5%. + +The requirement in the present clause applies during the transmitter ON period for a single transmitted carrier. For E-UTRA intra-band contiguous carrier aggregation, the requirement in clause 6.6.1 of TS 36.104 [4] applies for the E-UTRA component carriers that are aggregated. For NR intra-band contiguous carrier aggregation, the requirement in clause 6.6.2.2 of TS 38.104 [17] applies for the NR component carriers that are aggregated. The minimum requirement below may be applied regionally. There may also be regional requirements to declare the occupied bandwidth according to the definition in the present clause. + +#### 6.6.3.1 Minimum requirement + +The occupied bandwidth shall be less than values listed in Table 6.6.3.1-1. + +**Table 6.6.3.1-1: Occupied bandwidth** + +| RAT | Occupied bandwidth limit | +|--------------------|--------------------------| +| E-UTRA and NR | $BW_{\text{Channel}}$ | +| UTRA FDD | 5 MHz | +| 1.28 Mcps UTRA TDD | 1.6 MHz | +| NB-IoT | 200 kHz | + +### 6.6.4 Adjacent Channel Leakage Power Ratio (ACLR) + +Adjacent Channel Leakage Power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. + +#### 6.6.4.1 E-UTRA minimum requirement + +For E-UTRA, the minimum requirement for ACLR is specified in Table 6.6.4.1-1 and 6.6.4.1-2 and applies outside the Base Station RF Bandwidth or Radio Bandwidth. + +For a BS operating in non-contiguous spectrum, the ACLR also applies for the first adjacent channel inside any sub-block gap with a gap size $W_{\text{gap}} \geq 15 \text{ MHz}$ . The ACLR requirement for the second adjacent channel applies inside any sub-block gap with a gap size $W_{\text{gap}} \geq 20 \text{ MHz}$ . The CACLR requirement in subclause 6.6.4.4 applies in sub block gaps for the frequency ranges defined in Table 6.6.4.4-1. + +For a BS operating in multiple bands, where multiple bands are mapped onto the same antenna connector, the ACLR also applies for the first adjacent channel inside any Inter RF Bandwidth gap with a gap size $W_{\text{gap}} \geq 15 \text{ MHz}$ . The ACLR requirement for the second adjacent channel applies inside any Inter RF Bandwidth gap with a gap size $W_{\text{gap}} \geq 20 \text{ MHz}$ . + +The CACLR requirement in subclause 6.6.4.4 applies in Inter-RF Bandwidth gaps for the frequency ranges defined in Table 6.6.4.4-1. + +The requirements apply during the transmitter ON period. + +The ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal ( $BW_{Config}$ ) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +For Category A Wide Area BS, either the ACLR limits in the tables below or the absolute limit of -13dBm/MHz shall apply, whichever is less stringent. + +For Category B Wide Area BS, either the ACLR limits in the tables below or the absolute limit of -15dBm/MHz shall apply, whichever is less stringent. For Medium Range BS, either the ACLR limits in the tables below or the absolute limit of -25 dBm/MHz shall apply, whichever is less stringent. + +For Local Area BS, either the ACLR limits in the tables below or the absolute limit of -32dBm/MHz shall apply, whichever is less stringent. + +For operation in paired spectrum, the ACLR shall be higher than the value specified in Table 6.6.4.1-1. + +**Table 6.6.4.1-1: Base Station ACLR in paired spectrum** + +| Channel bandwidth of E-UTRA Lowest/Highest Carrier transmitted $BW_{Channel}$ [MHz] | BS adjacent channel centre frequency offset below the lower or above the upper Base Station RF bandwidth edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| 1.4, 3.0, 5, 10, 15, 20 | 0.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 45 dB | +| | 1.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 45 dB | +| | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 45 dB | +| | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 45 dB | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +For operation in unpaired spectrum, the ACLR shall be higher than the value specified in Table 6.6.4.1-2. + +**Table 6.6.4.1-2: Base Station ACLR in unpaired spectrum with synchronized operation** + +| Channel bandwidth of E-UTRA Lowest/Highest Carrier transmitted $BW_{Channel}$ [MHz] | BS adjacent channel centre frequency offset below the lower or above the upper Base Station RF Bandwidth edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| 1.4, 3 | 0.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 45 dB | +| | 1.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 45 dB | +| | 0.8 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 45 dB | +| | 2.4 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 45 dB | +| 5, 10, 15, 20 | 0.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 45 dB | +| | 1.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 45 dB | +| | 0.8 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 45 dB | +| | 2.4 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 45 dB | +| | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 45 dB | +| | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 45 dB | +| | 5 MHz | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 45 dB | +| | 15 MHz | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 45 dB | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.105 [3], with a chip rate as defined in this table. + +For operation in non-contiguous paired spectrum, the ACLR shall be higher than the value specified in Table 6.6.4.1-3. + +**Table 6.6.4.1-3: Base Station ACLR in non-contiguous paired spectrum** + +| Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| $W_{\text{gap}} \geq 15 \text{ MHz}$ | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 45 dB | +| $W_{\text{gap}} \geq 20 \text{ MHz}$ | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 45 dB | +| NOTE: | The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | | | + +For operation in non-contiguous unpaired spectrum, the ACLR shall be higher than the value specified in Table 6.6.4.1-4. + +**Table 6.6.4.1-4: Base Station ACLR in non-contiguous unpaired spectrum** + +| Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| $W_{\text{gap}} \geq 15 \text{ MHz}$ | 2.5 MHz | 5MHz E-UTRA carrier | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| $W_{\text{gap}} \geq 20 \text{ MHz}$ | 7.5 MHz | 5MHz E-UTRA carrier | Square ( $BW_{\text{Config}}$ ) | 45 dB | + +#### 6.6.4.2 UTRA FDD minimum requirement + +For UTRA FDD, the minimum requirement for ACLR is specified in TS 25.104 [2], subclause 6.6.2.2, and applies outside the Base Station RF Bandwidth or Radio Bandwidth. + +For a BS operating in non-contiguous spectrum, ACLR requirement also applies for the first adjacent channel, inside any sub-block gap with a gap size $W_{\text{gap}} \geq 15 \text{ MHz}$ . The ACLR requirement for the second adjacent channel applies inside any sub-block gap with a gap size $W_{\text{gap}} \geq 20 \text{ MHz}$ . The CACLR requirement in subclause 6.6.4.4 applies in sub block gaps for the frequency ranges defined in Table 6.6.4.4-1. + +For a BS operating in multiple bands, where multiple bands are mapped onto the same antenna connector, ACLR requirement also applies for the first adjacent channel, inside any Inter RF Bandwidth gap with a gap size $W_{\text{gap}} \geq 15 \text{ MHz}$ . The ACLR requirement for the second adjacent channel applies inside any Inter RF Bandwidth gap with a gap size $W_{\text{gap}} \geq 20 \text{ MHz}$ . The CACLR requirement in subclause 6.6.4.4 applies in Inter RF Bandwidth gaps for the frequency ranges defined in Table 6.6.4.4-1. + +#### 6.6.4.3 UTRA TDD minimum requirement + +For UTRA TDD, the minimum requirement for ACLR is specified in TS 25.105 [3], subclause 6.6.2.2.1.2, and applies outside the Base Station RF Bandwidth or Radio Bandwidth. + +#### 6.6.4.4 Cumulative ACLR requirement in non-contiguous spectrum + +The following requirement applies for the sub-block or Inter RF Bandwidth gap sizes listed in Table 6.6.4.4-1: + +- Inside a sub-block gap within an operating band for a BS operating in non-contiguous spectrum. +- Inside an Inter RF Bandwidth gap for a BS operating in multiple bands, where multiple bands are mapped on the same antenna connector. + +The Cumulative Adjacent Channel Leakage Power Ratio (CACLR) in a sub-block gap or the Inter RF Bandwidth gap is the ratio of + +- the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the sub-block gap or the Inter RF Bandwidth gap, and +- the filtered mean power centred on a frequency channel adjacent to one of the respective sub-block edges or Base Station RF Bandwidth edges. + +The requirement applies to adjacent channels of NR, E-UTRA or UTRA carriers allocated adjacent to each side of the sub-block gap or the Inter RF Bandwidth gap. The assumed filter for the adjacent channel frequency is defined in Table 6.6.4.4-1 and the filters on the assigned channels are defined in Table 6.6.4.4-2. + +NOTE: If the RAT on the assigned channel frequencies are different, the filters used are also different. + +For Wide Area Category A BS, either the CACLR limits in Table 6.6.4.4-1 or the absolute limit of -13dBm/MHz shall apply, whichever is less stringent. + +For Wide Area Category B BS, either the CACLR limits in Table 6.6.4.4-1 or the absolute limit of -15dBm/MHz shall apply, whichever is less stringent. + +For Medium Range BS, either the CACLR limits in Table 6.6.4.4-1 or the absolute limit of -25 dBm/MHz shall apply, whichever is less stringent. + +For Local Area BS, either the CACLR limits in Table 6.6.4.4-1 or the absolute limit of -32 dBm/MHz shall apply, whichever is less stringent. + +The CACLR for E-UTRA and UTRA carriers located on either side of the sub-block gap or the Inter RF Bandwidth gap shall be higher than the value specified in Table 6.6.4.4-1. + +**Table 6.6.4.4-1: Base Station CACLR in non-contiguous spectrum or multiple bands** + +| Band Category | Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies [MHz] | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|---------------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------| +| BC1, BC2 | $5 \leq W_{\text{gap}} < 15$ (Note 3) | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 45 dB | +| BC1, BC2 | $10 < W_{\text{gap}} < 20$ (Note 3) | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 45 dB | +| BC3 | $5 \leq W_{\text{gap}} < 15$ (Note 3) | 2.5 MHz | 5MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| BC3 | $10 < W_{\text{gap}} < 20$ (Note 3) | 7.5 MHz | 5MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| BC1, BC2, BC3 | $5 \leq W_{\text{gap}} < 45$ (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| BC1, BC2, BC3 | $10 \leq W_{\text{gap}} < 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| BC1, BC2, BC3 | $20 \leq W_{\text{gap}} < 30$ (Note 3, 5) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| BC1, BC2, BC3 | $20 \leq W_{\text{gap}} < 60$ (Note 4) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| BC1, BC2, BC3 | $40 \leq W_{\text{gap}} < 50$ (Note 3, 5) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| BC1, BC2, BC3 | $40 \leq W_{\text{gap}} < 80$ (Note 4) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | + +NOTE 1: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{\text{Config}}$ ). + +NOTE 3: Applicable in case the *channel bandwidth* of the carrier transmitted at the other edge of the gap is 5, 10, 15, 20 MHz. + +NOTE 4: Applicable in case the *channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 25, 30, 40, 50, 60, 70, 80, 90, 100 MHz. + +NOTE 5: Applicable in case the *channel bandwidth* of the NR carrier transmitted adjacent to sub-block gap or inter RF Bandwidth gap is 25, 30, 40, 50, 60, 70, 80, 90, 100 MHz. + +**Table 6.6.4.4-2: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the sub-block and Inter RF Bandwidth gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| E-UTRA | E-UTRA of same BW | +| UTRA FDD | RRC (3.84 Mcps) | +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | +| NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | + +#### 6.6.4.5 NB-IoT minimum requirement + +For NB-IoT in-band and guard band operation, the E-UTRA minimum requirement specified in clause 6.6.4.1 shall apply. + +For NB-IoT standalone operation, the ACLR shall be higher than the value specified in Table 6.6.4.5-1. + +**Table 6.6.4.5-1: Base Station ACLR for NB-IoT standalone operation** + +| Channel bandwidth of standalone NB-IoT lowest/highest carrier transmitted BWChannel | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 200 kHz | 300 kHz | Standalone NB-IoT | Square (BW Config ) | 40 dB | +| | 500 kHz | Standalone NB-IoT | Square (BW Config ) | 50 dB | +| NOTE 1: BW Config is the transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. | | | | | + +#### 6.6.4.6 NR minimum requirement + +For NR, the minimum requirements shall apply outside the Base Station RF Bandwidth or Radio Bandwidth whatever the type of transmitter considered (single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification. + +For a BS operating in non-contiguous spectrum, the ACLR requirement shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.4.6-2a, while the CACLR requirement shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.4.4-1. + +For BS operating in multiple bands, where multiple bands are mapped onto the same *antenna connector*, the ACLR requirement shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.4.6-2a, while the CACLR requirement in subclause 6.6.4.4 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.4.4-1. + +The requirement shall apply during the *transmitter ON period*. The ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal (BWConfig) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +The ACLR absolute *limit* in table 6.6.4.6-2 or the ACLR (CACLR) *limit* in table 6.6.4.6-1, 6.6.4.6-2a or 6.6.4.4-1, whichever is less stringent, shall apply for each *antenna connector*. + +For operation in paired and unpaired spectrum, the ACLR shall be higher than the value specified in table 6.6.4.6-1. + +For Band 41 NR operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all *antenna connectors*. + +Table 6.6.4.6-1: Base station ACLR limit + +| Channel bandwidth of lowest/highest NR carrier transmitted $BW_{Channel}$ [MHz] | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|----------------| +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | +| | $2 \times BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | +| | $BW_{Channel}/2 + 2.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 45 dB (Note 3) | +| | $BW_{Channel}/2 + 7.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 45 dB (Note 3) | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the *channel bandwidth* and transmission bandwidth configuration of the lowest/highest NR carrier transmitted on the assigned channel frequency. +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). +NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. + +The ACLR absolute limit is specified in table 6.6.4.6-2. + +Table 6.6.4.6-2: Base station ACLR absolute limit + +| BS category / BS class | ACLR absolute limit | +|-------------------------|---------------------| +| Category A Wide Area BS | -13 dBm/MHz | +| Category B Wide Area BS | -15 dBm/MHz | +| Medium Range BS | -25 dBm/MHz | +| Local Area BS | -32 dBm/MHz | + +For operation in non-contiguous spectrum or multiple bands, the ACLR shall be higher than the value specified in Table 6.6.4.6-2a. + +Table 6.6.4.6-2a: Base Station ACLR limit in non-contiguous spectrum or multiple bands + +| Channel bandwidth of lowest/highest NR carrier transmitted $BW_{Channel}$ [MHz] | Sub-block or Inter RF Bandwidth gap size ( $W_{gap}$ ) where the limit applies [MHz] | BS adjacent channel centre frequency offset below or above the sub-block or Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| 5, 10, 15, 20 | $W_{gap} \geq 15$ (Note 3)
$W_{gap} \geq 45$ (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | +| | $W_{gap} \geq 20$ (Note 3)
$W_{gap} \geq 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $W_{gap} \geq 60$ (Note 4)
$W_{gap} \geq 30$ (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | +| | $W_{gap} \geq 80$ (Note 4)
$W_{gap} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | BW Config is the transmission bandwidth configuration of the assumed adjacent channel carrier. | +| NOTE 2: | With SCS that provides largest transmission bandwidth configuration (BW Config ). | +| NOTE 3: | Applicable in case the channel bandwidth of the carrier transmitted at the other edge of the gap is 5, 10, 15, 20 MHz. | +| NOTE 4: | Applicable in case the channel bandwidth of the NR carrier transmitted at the other edge of the gap is 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 MHz.. | + +## 6.7 Transmitter intermodulation + +The transmitter intermodulation requirement is a measure of the capability of the transmitter to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. The requirement applies during the transmitter ON period and the transmitter transient period. + +For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply regardless of the interfering signals position relative to the Inter-RF Bandwidth gap. + +### 6.7.1 General minimum requirement + +The transmitter intermodulation level is the power of the intermodulation products when an interfering signal is injected into the antenna connector. + +The transmitter intermodulation level shall not exceed the unwanted emission limits in subclause 6.6.1, 6.6.2, 6.6.4 in the presence of a wanted signal and an interfering signal according to Table 6.7.1-1 for BS operation in BC1, BC2 and BC3. + +The requirement is applicable outside the Base Station RF Bandwidth or Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum, the requirement is also applicable inside a sub-block gap for interfering signal offsets where the interfering signal falls completely within the sub-block gap. The interfering signal offset is defined relative to the sub-block edges. + +For BS capable of multi-band operation, the requirement applies relative to the Base Station RF Bandwidth edges of each operating band. In case the Inter RF Bandwidth gap is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the Inter RF Bandwidth gap. + +**Table 6.7.1-1: Interfering signals for the Transmitter intermodulation requirement** + +| Parameter | Value | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| Interfering signal type | E-UTRA signal of channel bandwidth 5 MHz | +| Interfering signal level | Rated total output power in the operating band – 30dB | +| Interfering signal centre frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap | ±2.5 MHz
±7.5 MHz
±12.5 MHz | +| NOTE 1: Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band, TS 37.141 [10] provides further guidance regarding appropriate test requirements. | | +| NOTE 2: In certain regions, NOTE 1 is not applied in Band 1, 3, 8, 9, 11, 18, 19, 21, 28, 32 operating within 1475.9-1495.9MHz, 34. | | + +### 6.7.2 Additional minimum requirement (BC1 and BC2) + +The transmitter intermodulation level shall not exceed the unwanted emission limits in subclause 6.6.1, 6.6.2, 6.6.4 in the presence of a wanted signal and an interfering signal according to Table 6.7.2-1 for BS operation in BC2. + +The requirement is applicable outside the Base Station RF Bandwidth and Radio Bandwidth for BC2. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum in BC1 or BC2, the requirement is also applicable inside a sub-block gap with a gap size larger than or equal to two times the interfering signal centre frequency offset. For BS operating in non-contiguous spectrum in BC1, the requirement is not applicable inside a sub-block gap with a gap size equal to or larger than 5 MHz. The interfering signal offset is defined relative to the sub-block edges. + +For BS capable of multi-band operation, the requirement applies relative to the Base Station RF Bandwidth edges of a BC2 operating band. The requirement is also applicable for BC1 and BC2 inside an Inter RF Bandwidth gap equal to or larger than two times the interfering signal centre frequency offset. For BS capable of multi-band operation, the requirement is not applicable for BC1 band inside an Inter RF Bandwidth gap with a gap size equal to or larger than 5 MHz. + +**Table 6.7.2-1: Interfering signal for the transmitter intermodulation requirement** + +| Parameter | Value | +|-------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Interfering signal type | CW | +| Interfering signal level | Rated total output power in the operating band – 30dB | +| Interfering signal centre frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap | > abs(800) kHz for CW interferer | +| NOTE: | Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are excluded from the requirement. | + +### 6.7.3 Additional minimum requirement (BC3) + +This additional requirement shall only apply for BS co-located with an UTRA TDD BS. + +The transmitter intermodulation level shall not exceed the unwanted emission limits in subclause 6.6.1, 6.6.2, 6.6.4 in the presence of a wanted signal and an interfering signal according to Table 6.7.3-1 for BS operation in BC3. + +For BS capable of multi-band operation, the requirement applies relative to the Base Station RF Bandwidth edges of each operating band. In case the Inter RF Bandwidth gap is less than 3.2 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the Inter RF Bandwidth gap. + +**Table 6.7.3-1: Interfering signals for the Transmitter intermodulation requirement (BC3)** + +| Parameter | Value | +|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Interfering signal type | 1.28Mcps UTRA TDD signal of channel bandwidth 1.6MHz | +| Interfering signal level | Rated total output power in the operating band – 30dB | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or sub-block edge inside a gap | ±0.8 MHz
±1.6 MHz
±2.4 MHz | +| NOTE: | Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are excluded from the requirement. | + +### 6.7.4 Additional requirements + +In certain regions the following requirement may apply. For BS E-UTR single-RAT operating in Band 41, the transmitter intermodulation level shall not exceed the maximum levels specified in Table 6.6.1.3.1-3 and Table 6.6.4.1-2 with a square filter in the first adjacent channel, in the presence of an interfering signal according to Table 6.7.4-1. + +**Table 6.7.4-1 Interfering and wanted signals for the additional transmitter intermodulation requirement for Band 41** + +| Parameter | Value | +|-------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| Wanted signal | E-UTRA single carrier (NOTE) | +| Interfering signal type | E-UTRA signal of the same channel bandwidth as the wanted signal | +| Interfering signal level | Rated total output power in the operating band – 30dB | +| Interfering signal centre frequency offset from the lower/upper centre frequency of the wanted signal | $\pm BW_{\text{Channel}}$
$\pm 2 \times BW_{\text{Channel}}$ | +| NOTE: | This requirement applies for 10 or 20 MHz E-UTRA carriers allocated within 2545-2645 MHz. | + +# 7 Receiver characteristics + +## 7.1 General + +The requirements in clause 7 are expressed for a single receiver antenna connector. For receivers with antenna diversity or in case of multi-carrier reception with multiple receiver antenna connectors, the requirements apply for each receiver antenna connector. + +For blocking and intermodulation characteristics, the negative offsets of the interfering signal apply relative to the assigned channel frequency of the lowest carrier frequency received and positive offsets of the interfering signal apply relative to the assigned channel frequency of the highest carrier frequency received. + +A BS supporting DC-HSUPA receives two UTRA FDD cells simultaneously on adjacent carrier frequencies. + +Unless otherwise stated, the receiver characteristics are specified at the BS antenna connector (test port A) with a full complement of transceivers for the configuration in normal operating conditions. For FDD operation the requirements in clause 7 shall be met with the transmitter(s) on. If any external apparatus such as a RX amplifier, a filter or the combination of such devices is used, requirements apply at the far end antenna connector (test port B). + +NOTE: In normal operating conditions the BS in FDD operation is configured to transmit and receive at the same time. The transmitter may be off for some of the tests as specified in 37.141 [10]. + +Unless otherwise stated the requirements in clause 7 apply during the base station receive period. + +Unless otherwise stated the requirements for NB-IoT in subclause 7 applies for all operation modes (In-band operation, Guard-band operation and Stand-alone operation). + +![Diagram of receiver test ports showing a BS cabinet connected to an External LNA (if any) and an External device (e.g. RX filter, if any). Test port A is at the BS cabinet connector, and Test port B is at the far end connector. An arrow labeled 'From antenna connector' points towards Test port B.](c67407c82ad10179bcb338347ded4245_img.jpg) + +The diagram illustrates the signal path for receiver testing. It starts with a 'BS cabinet' on the left. A cable connects it to an 'External LNA (if any)' block. Another cable connects the LNA to an 'External device e.g. RX filter (if any)' block. 'Test port A' is indicated by an arrow pointing to the connector between the BS cabinet and the External LNA. 'Test port B' is indicated by an arrow pointing to the connector between the External device and the antenna. A dashed line with an arrow labeled 'From antenna connector' points towards Test port B, representing the incoming signal path. + +Diagram of receiver test ports showing a BS cabinet connected to an External LNA (if any) and an External device (e.g. RX filter, if any). Test port A is at the BS cabinet connector, and Test port B is at the far end connector. An arrow labeled 'From antenna connector' points towards Test port B. + +**Figure 7.1-1: Receiver test ports** + +E-UTRA and NR throughput requirements defined for the receiver characteristics in this clause do not assume HARQ retransmissions. + +Values for $F_{\text{offset, RAT}}$ to meet receiver requirements are specific for each RAT in each Band Category as specified in subclause 4.5.1 for Band Category 1, subclause 4.5.2 for Band Category 2 and subclause 4.5.3 for Band Category 3. + +## 7.2 Reference sensitivity level + +The reference sensitivity power level $P_{\text{REFSENS}}$ is the minimum mean power received at the antenna connector at which a reference performance requirement shall be met for a specified reference measurement channel. + +### 7.2.1 E-UTRA minimum requirement + +For E-UTRA, the minimum requirement for reference sensitivity is specified in TS 36.104 [4], subclause 7.2. + +### 7.2.2 UTRA FDD minimum requirement + +For UTRA FDD, the minimum requirement for reference sensitivity is specified in TS 25.104 [2], subclause 7.2. + +### 7.2.3 UTRA TDD minimum requirement + +For UTRA TDD, the minimum requirement for reference sensitivity is specified in TS 25.105 [3], subclause 7.2. + +### 7.2.4 GSM/EDGE minimum requirement + +For GSM/EDGE, the minimum requirement for reference sensitivity is specified in TS 45.005 [5], applicable parts of subclause 6.2. + +The conditions specified in TS 45.005 [5], Annex P.1 apply for GSM/EDGE reference sensitivity. + +### 7.2.5 NB-IoT minimum requirement + +For NB-IoT, the minimum requirement for reference sensitivity is specified in TS 36.104 [4], subclause 7.2. + +### 7.2.6 NR minimum requirement + +For NR, the minimum requirement for reference sensitivity (BS type 1-C) is specified in TS 38.104 [17], subclause 7.2. + +### 7.2.7 Void + +## 7.3 Dynamic range + +The dynamic range is a measure of the capability of the receiver to receive a wanted signal in the presence of an interfering signal inside the received channel bandwidth or the capability of receiving high level of wanted signal. + +### 7.3.1 E-UTRA minimum requirement + +For E-UTRA, the minimum requirement for dynamic range is specified in TS 36.104 [4], subclause 7.3. + +### 7.3.2 UTRA FDD minimum requirement + +For UTRA FDD, the minimum requirement for dynamic range is specified in TS 25.104 [2], subclause 7.3. + +### 7.3.3 UTRA TDD minimum requirement + +For UTRA TDD, the minimum requirement for dynamic range is specified in TS 25.105 [3], subclause 7.3. + +### 7.3.4 GSM/EDGE minimum requirement + +For GSM/EDGE, the minimum requirement for dynamic range is expressed as Nominal Error Rate and is specified in TS 45.005 [5], applicable parts of subclause 6.1.1.1, 6.1.1.3, 6.1.2.2 and 6.1.3.2. + +### 7.3.5 NB-IoT minimum requirement + +For NB-IoT standalone operation, E-UTRA in-band or guard band operation, the minimum requirement for dynamic range is specified in TS 36.104 [4], subclause 7.3. + +For *NB-IoT operation in NR in-band*, the minimum requirement for dynamic range is specified in TS 38.104 [17], subclause 7.3.2. + +### 7.3.6 NR minimum requirement + +For NR, the minimum requirement for dynamic range (BS type 1-C) is specified in TS 38.104 [17], subclause 7.3. + +## 7.4 In-band selectivity and blocking + +The in-band selectivity and blocking characteristics are measures of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer inside the operating band and are defined by a (wideband) and a narrowband blocking requirement. + +The in-band blocking requirement applies from $F_{UL\_low} - \Delta f_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ , excluding the downlink frequency range of the FDD *operating band*. The values of $\Delta f_{OOB}$ are defined in table 7.4-1. + +**Table 7.4-1: Maximum $\Delta f_{OOB}$ offset outside the uplink operating band** + +| Operating band characteristics | \Delta f_{OOB} [MHz] | +|---------------------------------------------------------------------|------------------------------------------| +| $200 \text{ MHz} \geq F_{UL\_high} - F_{UL\_low}$ | 20 | +| $200 \text{ MHz} < F_{UL\_high} - F_{UL\_low} \leq 900 \text{ MHz}$ | 60 | + +### 7.4.1 General blocking minimum requirement + +For the general blocking requirement, the interfering signal shall be a UTRA FDD signal as specified in annex A for a UTRA, E-UTRA, NB-IOT, GSM/EDGE or NR ( $\leq 20 \text{ MHz}$ ) wanted signal. The interfering signal shall be a 20 MHz E-UTRA signal for NR wanted signal channel bandwidth greater than 20MHz. + +The requirement is applicable outside the Base Station RF Bandwidth or Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum, the requirement applies in addition inside any sub-block gap, in case the sub-block gap size is at least 15 MHz. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +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 15 MHz. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +For the wanted and interfering signal coupled to the base station antenna input, using the parameters in Table 7.4.1-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. + +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], subclause 7.2. +- For any UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [3], subclause 7.2. +- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.1. +- For any NB-IoT carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [17], subclause 7.2. + +For BS capable of multi-band operation, the requirement applies according to Table 7.4.1-1 for the in-band blocking frequency ranges of each supported operating band. + +**Table 7.4.1-1: General blocking requirement** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] (Note 1) | Centre Frequency of Interfering Signal | Interfering signal centre frequency minimum frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap [MHz] | +|-------------------|----------------------------------------|-----------------------------------------|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | -40+y (Note 7) | $P_{REFSENS} + x$ dB (Note 2) | $F_{UL\_low} - \Delta f_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ (Note 8) | $\pm (7.5 + z)$ (Note 9) | +| Medium Range BS | -35+y (Note 7) | $P_{REFSENS} + x$ dB (Note 3, 5) | | | +| Local Area BS | -30+y (Note 7) | $P_{REFSENS} + x$ dB (Note 4, 5) | | | + +NOTE 1: $P_{REFSENS}$ depends on the RAT, the BS class and on the channel bandwidth, see subclause 7.2. + +NOTE 2: For WA BS supporting GSM and/or UTRA, "x" is equal to 6 in case of NR or E-UTRA or UTRA or NB-IoT wanted signals and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 3: For MR BS supporting GSM and/or UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA or NB-IoT wanted signal and 3 in case of GSM/EDGE wanted signal. + +NOTE 4: For LA BS supporting GSM and/or UTRA, "x" is equal to 11 in case of NR or E-UTRA or NB-IoT wanted signal, 6 in case of UTRA wanted signal and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 5: For a BS neither supporting UTRA nor GSM, x is equal to 6 for all BS classes if NR is supported, otherwise "x" is equal to 6 for WA BS, 9 for MR BS or 11 for LA BS if NR is not supported. + +NOTE 6: For a BS capable of multi-band operation, "x" in Note 2, 3, 4, 5 applies in case of interfering signals that are in the in-band blocking frequency range of the operating band where the wanted signal is present or in the in-band blocking frequency range of an adjacent or overlapping operating band. For other in-band blocking frequency ranges of the interfering signal for the supported operating bands, "x" is equal to 1.4 dB. + +NOTE 7: For a BS supporting NR but neither supporting UTRA nor GSM, "y" is equal to -3 for the WA and MR BS class and -5 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. + +NOTE 8: The downlink frequency range of an FDD operating band is excluded from the general blocking requirement. + +NOTE 9: For NR wanted signal channel bandwidth greater than 20 MHz, $z = 22.5$ . For all other cases, $z = 0$ . + +**Table 7.4.1-2: Void** + +NOTE: The requirement in Table 7.4.1-1 assumes that two operating bands, where the downlink operating band (see Table 4.5-1 and Table 4.5-2) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +### 7.4.2 General narrowband blocking minimum requirement + +For the general narrowband blocking requirement, the interfering signal shall be an E-UTRA 1RB signal as specified in Annex A. + +The requirement is applicable outside the Base Station RF Bandwidth or Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum, the requirement applies in addition inside any sub-block gap, in case the sub-block gap size is at least 3 MHz. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +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 3 MHz. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +For the wanted and interfering signal coupled to the base station antenna input, using the parameters in Table 7.4.2-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], subclause 7.2. +- For any UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [3], subclause 7.2. +- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.1. +- For any NB-IoT carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [17], subclause 7.2. + +**Table 7.4.2-1: Narrowband blocking requirement** + +| Base Station Type | RAT of the carrier | Wanted signal mean power [dBm] (Note 1, 2, 7) | Interfering signal mean power [dBm] | Interfering RB (Note 3) centre frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap [kHz] | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-----------------------------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------|--|--|--| +| Wide Area BS | NR, E-UTRA, NB-IoT (Note 4)
UTRA and GSM/EDGE | $P_{\text{REFSENS}} + x$ dB | -49 | $\pm(240 + m \cdot 180)$ ,
$m=0, 1, 2, 3, 4, 9, 14$ (Note 5) | | | | +| Medium Range BS | | | -44 | | | | | +| Local Area BS | | | -41 | | | | | +| NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth, see subclause 7.2. | | | | | | | | +| NOTE 2: "x" is equal to 6 in case of NR, E-UTRA or UTRA wanted signals and equal to 3 in case of GSM/EDGE wanted signal. "x" is specified in Table 7.4.2-2 for NB-IoT operation in E-UTRA in-band/guard band and NB-IoT standalone, and in Table 7.4.2-2A for NB-IoT operation in NR in-band. | | | | | | | | +| NOTE 3: Interfering signal (E-UTRA 3MHz) consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the Base Station RF Bandwidth edge. | | | | | | | | +| NOTE 4: For NB-IoT, the mentioned desensitized values consider only one NB-IoT PRB in the guard band, which is placed adjacent to the E-UTRA PRB edge as close as possible (i.e., away from edge of channel bandwidth). | | | | | | | | +| NOTE 5: Applicable for channel bandwidths equal to or below 20 MHz. | | | | | | | | +| NOTE 6: Applicable for channel bandwidths above 20 MHz. | | | | | | | | +| NOTE 7: 7.5 kHz shift is not applied to the wanted signal of NR. | | | | | | | | +| NOTE 8: Void | | | | | | | | + +**Table 7.4.2-2: "x" for NB-IoT wanted signals operation in E-UTRA in-band/guard band and NB-IoT standalone** + +| Operation mode | LTE channel bandwidth for in-band/guard band operation | x | +|----------------|--------------------------------------------------------|----| +| Standalone | - | 12 | +| In Band | 3 MHz | 11 | +| | 5 MHz | 9 | +| | 10 MHz | 6 | +| | 15 MHz | 6 | +| | 20 MHz | 6 | +| Guard band | 5 MHz | 13 | +| | 10 MHz | 6 | +| | 15 MHz | 6 | +| | 20 MHz | 6 | + +**Table 7.4.2-2A: "x" for NB-IoT wanted signals operation in NR in-band** + +| Operation mode | NR BS channel bandwidth | x | +|----------------|-------------------------|---| +| NR in-band | 5 MHz | 9 | +| | 10 MHz | 6 | +| | 15 MHz | 6 | +| | $\geq 20$ MHz | 6 | + +### 7.4.3 Additional Narrowband blocking minimum requirement for GSM/EDGE + +The GSM/EDGE in-band blocking requirement as stated in TS 45.005 [5], applicable parts of subclauses 5.1.3 and 5.1.4, shall apply for any GSM/EDGE carrier. + +The conditions specified in TS 45.005 [5], Annex P.2.1 apply for GSM/EDGE in-band narrowband blocking. + +### 7.4.4 GSM/EDGE requirements for AM suppression + +The GSM/EDGE AM suppression requirement as stated in TS 45.005 [5], applicable parts of subclauses 5.2.2, shall apply for any GSM/EDGE carrier. + +The conditions specified in TS 45.005 [5], Annex P.2.3 apply for GSM/EDGE AM suppression. + +### 7.4.5 Additional BC3 blocking minimum requirement + +This additional requirement only applies for BS operating in the same geographical area as UTRA TDD. + +The interfering signal is a 1.28 Mcps UTRA TDD modulated signal as specified in Annex A. + +The requirement is always applicable outside the Base Station RF Bandwidth or Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or 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 4.8 MHz. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +For the wanted and interfering signal coupled to the base station antenna input, using the parameters in Table 7.4.5-1, the following requirements shall be met: + +- For any E-UTRA, E-UTRA with NB-IoT and/or NB-IoT TDD carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [3], subclause 7.2. + +**Table 7.4.5-1: Additional blocking requirement for Band Category 3** + +| Operating Band | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Interfering signal centre frequency minimum frequency offset from the Base Station RF Bandwidth edge [MHz] | +|----------------------------------------------------------------------------------------|---------------------------------------------------|-------------------------------------|--------------------------------|------------------------------------------------------------------------------------------------------------| +| 33 - 40 | ( $F_{UL\_low} - 20$ ) to ( $F_{UL\_high} + 20$ ) | -40, | $P_{REFSENS} + 6$ dB* | $\pm 2.4$ | +| NOTE *: $P_{REFSENS}$ depends on the RAT and on the channel bandwidth, see clause 7.2. | | | | | + +## 7.5 Out-of-band blocking + +The Out-of-band blocking characteristic is a measure of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer outside the uplink operating band. + +### 7.5.1 General minimum requirement + +For a wanted and an interfering signal coupled to BS antenna input using the parameters in Table 7.5.1-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], subclause 7.2. +- For any UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [3], subclause 7.2. +- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.1. +- For any NB-IoT carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [17], subclause 7.2. + +For BS capable of multi-band operation, the requirement applies for each supported operating band. The in-band blocking frequency ranges of all supported operating bands according to Table 7.4.1-1 shall be excluded from the requirement. + +The out-of-band blocking requirement applies from 1 MHz to $F_{UL\_low} - \Delta f_{OOB}$ and from $F_{UL\_high} + \Delta f_{OOB}$ up to 12750MHz, including the downlink frequency range of the FDD *operating band for BS supporting FDD*. $\Delta f_{OOB}$ is defined in table 7.4-1 + +**Table 7.5.1-1: Out-of-band blocking performance requirement** + +| Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------| +| -15 (NOTE2) | P REFSENS +x dB (NOTE1) | CW carrier | +|

NOTE1: PREFSENS depends on the RAT, the BS class and the channel bandwidth, see subclause 7.2.
"x" is equal to 6 in case of NR, E-UTRA, UTRA or NB-IoT wanted signals and equal to 3 in case of GSM/EDGE wanted signal.

NOTE2: For NB-IoT, up to 24 exceptions are allowed for spurious response frequencies in each wanted signal frequency when measured using a 1MHz step size. For these exceptions the above throughput requirement shall be met when the blocking signal is set to a level of -40 dBm for 15 kHz subcarrier spacing and -46 dBm for 3.75 kHz subcarrier spacing. In addition, each group of exceptions shall not exceed three contiguous measurements using a 1MHz step size.

| | | + +### 7.5.2 Co-location minimum requirement + +This additional blocking requirement may be applied for the protection of BS receivers when NR, E-UTRA, NB-IoT, UTRA, CDMA or GSM/EDGE BS operating in a different frequency band are co-located with a BS. + +The requirements in this subclause assume a 30 dB coupling loss between the interfering transmitter and the BS receiver and are based on co-location with base stations of the same class. + +For a wanted and an interfering signal coupled to BS antenna input using the parameters in Table 7.5.2-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], subclause 7.2. +- For any UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [3], subclause 7.2. +- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.1. +- For any NB-IoT carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [17], subclause 7.2. + +**Table 7.5.2-1: Blocking requirement for co-location with BS in other frequency bands.** + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|--------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 – 894 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| GSM900 | 921 – 960 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| DCS1800 | 1805 – 1880 (Note 4) | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| PCS1900 | 1930 – 1990 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 2110 – 2170 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1930 – 1990 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 | 1805 – 1880 (Note 4) | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 869 – 894 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 – 885 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2620 – 2690 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 – 960 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 – 1495.9 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 729 – 746 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 746 – 756 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 758 – 768 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 17 | 734 – 746 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 18 or NR Band n18 | 860 – 875 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 – 890 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 791 – 821 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 – 1510.9 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 24 or NR Band n24 | 1525 – 1559 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | + +| | | | | | | | +|-------------------------------------------------------|-------------------------|-------|------|------|--------------------------------|------------| +| UTRA FDD Band XXV or E-UTRA Band 25 or NR Band n25 | 1930 – 1995 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 – 894 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 27 | 852 - 869 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 28 or NR Band n28 | 758 – 803 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 | +16** | +8** | -6** | $P_{REFSENS} + 6\text{dB}^*$ | CW carrier | +| E-UTRA Band 30 or NR Band n30 | 2350-2360 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 | +16** | +8** | -6** | $P_{REFSENS} + 6\text{dB}^*$ | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 – 1496
(NOTE 5) | +16** | +8** | -6** | $P_{REFSENS} + 6\text{dB}^*$ | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 33 | 1900-1920 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 34 or NR Band n34 | 2010-2025 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 35 | 1850-1910 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 36 | 1930-1990 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band c) or E-UTRA TDD Band 37 | 1910-1930 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570-2620 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR Band n39 | 1880-1920 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300-2400 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 41 or NR Band n41 | 2496 - 2690 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 42 | 3400 – 3600 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 43 | 3600 – 3800 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 44 | 703 – 803 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 45 | 1447 – 1467 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 | N/A | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 49 | 3550 – 3700 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 50 or NR Band n50 | 1432 – 1517 | +16 | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 51 or NR Band n51 | 1427– 1432 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 52 | 3300 – 3400 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 | N/A | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 65 or NR Band n65 | 2110 – 2200 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | + +| | | | | | | | +|---------------------------------|-------------|-------|------|------|--------------------------------|------------| +| E-UTRA Band 66 or NR Band n66 | 2110 – 2200 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 69 | 2570-2620 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 70 or NR Band n70 | 1995 - 2020 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 71 or NR Band n71 | 617 - 652 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +16** | +8** | -6** | $P_{REFSENS} + 6 \text{ dB}^*$ | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +16** | +8** | -6** | $P_{REFSENS} + 6 \text{ dB}^*$ | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 75 or NR Band n75 | 1432 - 1517 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 76 or NR Band n76 | 1427 - 1432 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n77 | 3300 - 4200 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n78 | 3300 - 3800 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 - 746 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 87 | 420 – 425 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 88 | 422 – 427 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n91 | 1427 – 1432 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n92 | 1432 – 1517 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n93 | 1427 – 1432 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n94 | 1432 – 1517 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n96 | 5925 – 7125 | N/A | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n100 | 919.4 – 925 | +16 | N/A | N/A | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n101 | 1900 – 1910 | +16 | N/A | N/A | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n102 | 5925 – 6425 | N/A | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 103 | 757 – 758 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n104 | 6425 – 7125 | +16 | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n105 | 612 - 652 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 106 or NR Band n106 | 935 - 940 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n109 | 1432 - 1517 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | + +NOTE 1 (\*): $P_{REFSENS}$ depends on the RAT, the BS class and the channel bandwidth, see subclause 7.2. + +"x" is equal to 3 in case of GSM/EDGE wanted signal and equal to 6 in case of NR or UTRA or E-UTRA or NB-IoT wanted signals. + +NOTE 2: Except for a BS operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported uplink operating band or in the $\Delta f_{00B}$ immediately outside any of the supported uplink operating band. + +For a BS operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768-797 MHz. + +NOTE 3: 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 or E-UTRA TDD or NR TDD with E-UTRA FDD or NR 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 [7]. + +NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805-1850MHz. + +NOTE 5: For a BS operating in band 11, 21, 74, the requirement for co-location with Band 32 applies for interfering signal within the frequency range 1475.9-1495.9 MHz. + +NOTE 6: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can receive without special co-location requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +NOTE 7 (\*\*): For NB-IoT, up to 24 exceptions are allowed for spurious response frequencies in each wanted signal frequency when measured using a 1MHz step size. For these exceptions the above throughput requirement shall be met when the blocking signal is set to a level of -40 dBm for 15 kHz subcarrier spacing and -46 dBm for 3.75 kHz subcarrier spacing. In addition, each group of exceptions shall not exceed three contiguous measurements using a 1MHz step size. + +## 7.6 Receiver spurious emissions + +The receiver spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the BS receiver antenna connector. The requirements apply to all BS with separate RX and TX antenna ports. In this case for FDD BS the test shall be performed when both TX and RX are on, with the TX port terminated. + +For TDD BS with common RX and TX antenna port the requirement applies during the Transmitter OFF period. For FDD BS with common RX and TX antenna port the transmitter spurious emission limits as specified in subclause 6.6.1 are valid. + +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. + +### 7.6.1 General minimum requirement + +The power of any spurious emission shall not exceed the levels in Table 7.6.1-1: + +**Table 7.6.1-1: General spurious emissions requirement** + +| Frequency range | Maximum level | Measurement Bandwidth | Note | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 30MHz - 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz – 12.75 GHz | -47 dBm | 1 MHz | | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -47 dBm | 1 MHz | This spurious frequency range applies only for operating bands for which the 5 th harmonic of the upper frequency edge of the UL operating band is reaching beyond 12.75 GHz. | +| NOTE: The frequency range from $F_{BW, RF, DL, low} - \Delta f_{OBUE}$ to $F_{BW, RF, DL, high} + \Delta f_{OBUE}$ may be excluded from the requirement. 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. | | | | + +In addition to the requirements in Table 7.6.1-1, the power of any spurious emission shall not exceed the Additional spurious emissions requirements in subclause 6.6.1.3 and in case of FDD BS (for BC1 and BC2) emission shall not exceed the levels specified for Protection of the BS receivers of own or different BS in subclause 6.6.1.2. In addition, the requirements for co-location with other base stations specified in subclause 6.6.1.4 may also be applied. + +### 7.6.2 Additional minimum requirement for BC2 (Category B) + +For a BS operating in Band Category 2 when GSM/EDGE is configured and where Category B spurious emissions apply, the power of any spurious emissions shall not exceed the limits in Table 7.6.2-1. + +For BS capable of multi-band operation, the limits in Table 7.6.2-1 are only applicable when all supported operating bands belong to BC2 and GSM/EDGE is configured in all bands. + +**Table 7.6.2-1: Additional BS spurious emissions limits for BC2, Category B** + +| Frequency range | Frequency offset from downlink operating band edge (Note 1) | Maximum level | Measurement Bandwidth | +|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|---------------|-----------------------| +| 500 MHz – 1 GHz | 10 – 20 MHz | -57 dBm | 300 kHz | +| | 20 – 30 MHz | -57 dBm | 1 MHz | +| | ≥ 30 MHz | -57 dBm | 3 MHz | +| 1 GHz – 12.75 GHz | ≥ 30 MHz | -47 dBm | 3 MHz | +| NOTE 1: For BS capable of multi-band operation, the frequency offset is relative to the closest supported operating band. | | | | + +## 7.7 Receiver intermodulation + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. + +### 7.7.1 General intermodulation minimum requirement + +Interfering signals shall be a CW signal and an E-UTRA or UTRA signal as specified in Annex A. + +The requirement is applicable outside the Base Station RF Bandwidth or Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or 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 twice as wide as the UTRA/E-UTRA interfering signal centre frequency offset from the Base Station RF Bandwidth edge. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the inter Base Station RF Bandwidth gap. + +For the wanted signal at the assigned channel frequency and two interfering signals coupled to the base station antenna input, using the parameters in Table 7.7.1-1 and 7.7.1-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], subclause 7.2. +- For any UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [3], subclause 7.2. +- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.2. +- For any NB-IoT carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [17], subclause 7.2. + +**Table 7.7.1-1: General intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] | Type of interfering signal | +|-------------------|-----------------------------------------|----------------------------------|----------------------------| +| Wide Area BS | -48+y (Note 6) | $P_{REFSENS} + x$ dB (Note 2) | See Table 7.7.1-2 | +| Medium Range BS | -44+y (Note 6) | $P_{REFSENS} + x$ dB (Note 3, 5) | | +| Local Area BS | -38+y (Note 6) | $P_{REFSENS} + x$ dB (Note 4, 5) | | + +NOTE 1: $P_{REFSENS}$ depends on the RAT, the BS class and on the channel bandwidth, see subclause 7.2. + +NOTE 2: For WA BS supporting GSM and/or UTRA, "x" is equal to 6 in case of NR or E-UTRA or UTRA or NB-IoT wanted signals and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 3: For MR BS supporting GSM and/or UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA or NB-IoT wanted signal and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 4: For LA BS supporting GSM and/or UTRA, "x" is equal to 12 in case of NR or E-UTRA or NB-IoT wanted signals, 6 in case of UTRA wanted signal and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 5: For a BS neither supporting GSM nor UTRA, x is equal to 6 for all BS classes if NR is supported, otherwise x is equal to 6 for WA BS or, 9 for MR BS and 12 for LA BS if NR is not supported. + +NOTE 6: For a BS supporting NR but neither UTRA nor GSM; "y" is equal to -4 for the WA BS class, -3 for the MR BS class and -6 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes + +**Table 7.7.1-2: Interfering signals for intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge | Interfering signal centre frequency offset from the Base Station RF Bandwidth edge [MHz] | Type of interfering signal | +|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|----------------------------| +| E-UTRA 1.4 MHz | ±2.0 (BC1 and BC3) /
±2.1 (BC2) | CW | +| | ±4.9 | 1.4MHz E-UTRA signal | +| E-UTRA or E-UTRA with NB-IoT in-band 3 MHz | ±4.4 (BC1 and BC3) /
±4.5 (BC2) | CW | +| | ±10.5 | 3MHz E-UTRA signal | +| UTRA FDD and E-UTRA or E-UTRA with NB-IoT in-band/guard band 5 MHz | ±7.5 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 10 MHz | ±7.375 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 15 MHz | ±7.25 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 20 MHz | ±7.125 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| GSM/EDGE/NB-IoT standalone | ±7.575 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| 1.28 Mcps UTRA TDD | ±2.3 (BC3) | CW | +| | ±5.6 (BC3) | 1.28Mcps UTRA TDD signal | +| NR 5 MHz or NR with NB-IoT operation in NR in-band | ±7.5 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 10 MHz or NR with NB-IoT operation in NR in-band | ±7.465 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 15 MHz or NR with NB-IoT operation in NR in-band | ±7.43 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 20 MHz or NR with NB-IoT operation in NR in-band | ±7.395 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 25 MHz or NR with NB-IoT operation in NR in-band | ±7.465 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 30 MHz or NR with NB-IoT operation in NR in-band | ±7.43 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 35 MHz or NR with NB-IoT operation in NR in-band | ±7.44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| | ±7.45 | CW | + +| | | | +|------------------------------------------------------------|-------|---------------------| +| NR 40 MHz or NR with NB-IoT operation in NR in-band | ±25 | 20MHz E-UTRA signal | +| NR 45 MHz or NR with NB-IoT operation in NR in-band | ±7.37 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 50 MHz or NR with NB-IoT operation in NR in-band | ±7.35 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 60 MHz | ±7.49 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 70 MHz | ±7.42 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 80 MHz | ±7.44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 90 MHz | ±7.46 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 100 MHz | ±7.48 | CW | +| | ±25 | 20MHz E-UTRA signal | + +### 7.7.2 General narrowband intermodulation minimum requirement + +Interfering signals shall be a CW signal and an E-UTRA 1RB signal as specified in Annex A. + +The requirement is applicable outside the Base Station RF Bandwidth or Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum within each supported operating band, the requirement applies in addition inside any sub-block gap in case the sub-block gap is at least as wide as the channel bandwidth of the E-UTRA interfering signal in Table 7.7.2-2. The interfering signal offset is defined relative to the sub-block edges inside the gap. + +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 as wide as the E-UTRA interfering signal in Table 7.7.2-2. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +For the wanted signal at the assigned channel frequency and two interfering signals coupled to the base station antenna input, using the parameters in Table 7.7.2-1 and 7.7.2-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], subclause 7.2. +- For any UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [3], subclause 7.2. +- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.2. +- For any NB-IoT carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [4], subclause 7.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [17], subclause 7.2. + +**Table 7.7.2-1: General narrowband intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] | Type of interfering signal | +|-------------------|-----------------------------------------|--------------------------------|----------------------------| +| Wide Area BS | -52 | $P_{REFSENS} + x$ dB (NOTE 1) | See Table 7.7.2-2 | +| Medium Range BS | -47 | | | +| Local Area BS | -44 | | | + +NOTE 1: $P_{REFSENS}$ depends on the RAT, the BS class and on the channel bandwidth, see subclause 7.2. +"x" is equal to 6 in case of NR, NB-IoT, E-UTRA or UTRA wanted signals and equal to 3 in case of GSM/EDGE wanted signal. + +**Table 7.7.2-1a: Void** + +**Table 7.7.2-2: Interfering signals for narrowband intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge or sub-block edge | CW or 1RB interfering signal centre frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap [kHz] | Type of interfering signal | +|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| E-UTRA 1.4 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±970 (BC1 and BC3) / ±790 (BC2) | 1.4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band 3 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±960 (BC1 and BC3) / ±780 (BC2) | 3.0 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 5 MHz | ±360 (NOTE 3) | CW | +| | ±1060 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 10 MHz (NOTE 2) | ±325 (NOTE 3) | CW | +| | ±1240 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 15 MHz (NOTE 2) | ±380 (NOTE 3) | CW | +| | ±1600 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 20 MHz (NOTE 2) | ±345 (NOTE 3) | CW | +| | ±1780 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| UTRA FDD | ±345 (BC1 and BC2) | CW | +| | ±1780 (BC1 and BC2) | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| GSM/EDGE | ±340 | CW | +| | ±880 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| NB-IoT standalone | ±340 | CW | +| | ±880 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| 1.28Mcps UTRA TDD | ±190 (BC3) | CW | +| | ±970 (BC3) | 1.4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| NR 5 MHz or NR with NB-IoT operation in NR in-band | ±360 | CW | +| | ±1420 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 10 MHz or NR with NB-IoT operation in NR in-band | ±370 | CW | +| | ±1960 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 15 MHz or NR with NB-IoT operation in NR in-band (Note 2) | ±380 | CW | +| | ±1960 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 20 MHz or NR with NB-IoT operation in NR in-band (Note 2) | ±390 | CW | +| | ±2320 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 25 MHz or NR with NB-IoT operation in NR in-band (Note 2) | ±325 | CW | +| | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | +| | ±335 | CW | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------| +| NR 30 MHz or NR with NB-IoT operation in NR in-band (Note 2) | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 35 MHz or NR with NB-IoT operation in NR in-band (Note 2) | ±345 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 40 MHz or NR with NB-IoT operation in NR in-band (Note 2) | ±355 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 45 MHz or NR with NB-IoT operation in NR in-band (Note 2) | ±365 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 50 MHz or NR with NB-IoT operation in NR in-band (Note 2) | ±375 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 60 MHz (Note 2) | ±395 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 70 MHz (Note 2) | ±415 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 80 MHz (Note 2) | ±435 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 90 MHz (Note 2) | ±365 | CW | +| | ±2530 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 100 MHz (Note 2) | ±385 | CW | +| | ±2530 | E-UTRA signal, 1 RB (NOTE 1) | +| NOTE 1: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the Base Station RF Bandwidth edge. | | | +| NOTE 2: This requirement shall apply only for an E-UTRA FRC A1-3 or NR G-FRC mapped to the frequency range at the channel edge adjacent to the interfering signals. | | | +| NOTE 3: The frequency offset shall be adjusted to accommodate the IMD product to fall in the NB-IoT RB for NB-IoT in-band/guard band operation. | | | +| NOTE 4: If a BS RF receiver fails the test of the requirement, the test shall be performed with the CW interfering signal frequency shifted away from the wanted signal by 180 kHz and the E-UTRA interfering signal frequency shifted away from the wanted signal by 360 kHz. If the BS RF receiver still fails the test after the frequency shift, then the BS RF receiver shall be deemed to fail the requirement. | | | + +### 7.7.3 Additional narrowband intermodulation minimum requirement for GSM/EDGE + +The GSM/EDGE MC-BTS receiver intermodulation requirement as stated in TS 45.005 [5], applicable parts of subclause 5.3.2 shall apply for any GSM/EDGE carrier. + +The conditions specified in TS 45.005 [5], Annex P.2.2 apply for the GSM/EDGE intermodulation requirement. + +## 7.8 In-channel selectivity + +In-channel selectivity (ICS) is a measure of the receiver ability to receive a wanted signal at its assigned resource block locations in the presence of an interfering signal received at a larger power spectral density. In this condition a throughput requirement shall be met for a specified reference measurement channel. + +### 7.8.1 E-UTRA minimum requirement + +For E-UTRA, the minimum requirement for in-channel selectivity is specified in TS 36.104 [4], subclause 7.4. + +For NB-IoT, the minimum requirement for in-channel selectivity is specified in TS 36.104 [4], subclause 7.4. + +### 7.8.2 NR minimum requirement + +For NR, the minimum requirement for in-channel selectivity (BS type 1-C) is specified in TS 38.104 [17], subclause 7.8. + +For *NB-IoT operation in NR in-band*, the minimum requirement for in-channel selectivity (BS type 1-C) is specified in TS 38.104 [17], subclause 7.8. + +# --- 8 Performance requirements + +Performance requirements specify the ability of the BS to correctly demodulate signals in various conditions and configurations. For NR, UTRA and E-UTRA the requirements specify a minimum throughput or maximum BLER or BER that shall be achieved at a specific SNR. For GSM/EDGE the requirements specify a maximum FER, BLER or BER that shall be achieved at specific sensitivity levels (C) and specific carrier-to-interference ratios (C/I). + +## 8.1 E-UTRA minimum requirement + +For E-UTRA, the minimum requirements for performance are specified in TS 36.104 [4], clause 8. + +## 8.2 UTRA FDD minimum requirement + +For UTRA FDD, the minimum requirements for performance are specified in TS 25.104 [2], clause 8. + +## 8.3 UTRA TDD minimum requirement + +For UTRA TDD, the minimum requirements for performance are specified in TS 25.105 [3], clause 8. + +## 8.4 GSM/EDGE minimum requirement + +For GSM/EDGE, the minimum requirements for reference sensitivity level and reference interference level are specified in TS 45.005 [5], applicable parts of clauses 6.2, 6.3, 6.4, 6.5 and 6.6. The conditions specified in TS 45.005 [5], Annex P.1 are valid for GSM sensitivity and interference performance. + +## 8.5 NR minimum requirement + +For NR, the minimum requirements for performance (BS type 1-C) are specified in TS 38.104 [17], clause 8. + +## 8.6 NB-IoT minimum requirement + +For NB-IoT, the minimum requirements for performance are specified in TS 36.104 [4], clause 8.5. + +# Annex A (normative): Characteristics of interfering signals + +## A.1 UTRA FDD interfering signal + +The UTRA FDD interfering signal shall be a DPCH containing the DPCCH and one DPDCH. The data content for each channelization code shall be uncorrelated with each other and to the wanted signal and spread and modulated according to clause 4 of TS 25.213. Further characteristics of DPDCH and DPCCH are specified in Table A.1-1. + +**Table A.1-1: Characteristics of UTRA FDD interfering signal** + +| Channel | Bit Rate | Spreading Factor | Channelization Code | Relative Power | +|----------------------------------------------------------------------------------------------------------|----------|------------------|---------------------|----------------| +| DPDCH | 240 kbps | 16 | 4 | 0 dB | +| DPCCH | 15 kbps | 256 | 0 | -5.46 dB | +| NOTE: The DPDCH and DPCCH settings are chosen to simulate a signal with realistic Peak to Average Ratio. | | | | | + +## A.2 UTRA TDD interfering signal + +The UTRA TDD interfering signal shall be 1.28 Mcps UTRA TDD signal with one code. The data content shall be uncorrelated to the wanted signal. They are specified in Table A.2-1. + +**Table A.2-1: Characteristics of UTRA TDD interfering signal** + +| UTRA TDD option | Type of Interfering Signal | +|----------------------------------------------------------------------------------------------------|------------------------------------------| +| 1.28 Mcps UTRA TDD | 1,28 Mcps UTRA TDD signal with one code* | +| NOTE *: The channelization code ID and Midamble shift shall be different with the wanted signal's. | | + +## A.3 E-UTRA interfering signal + +The E-UTRA interfering signal shall be a PUSCH containing data and reference symbols. Normal CP is used. The data content shall be uncorrelated to the wanted signal and modulated according to clause 5 of TS 36.211. Mapping of PUSCH modulation to receiver requirement are specified in Table A.3-1. + +**Table A.3-1: Modulation of the E-UTRA interfering signal** + +| Receiver requirement | Modulation | +|--------------------------|------------| +| Narrowband blocking | QPSK | +| Receiver intermodulation | QPSK | + +# --- Annex B (normative): Environmental requirements for the BS equipment + +The BS equipment shall fulfil all the requirements in the full range of environmental conditions for the relevant environmental class. The environmental conditions and class shall be from the relevant IEC specifications or the corresponding ETSI specifications listed below. + +IEC specifications for environmental requirements: + +IEC 60 721-3-3 "Stationary use at weather protected locations" [11] + +IEC 60 721-3-4 "Stationary use at non weather protected locations" [12] + +ETSI specifications for environmental requirements: + +ETSI EN 300 019-1-3 "Stationary use at weather protected locations" [13] + +ETSI EN 300 019-1-4 "Stationary use at non weather protected locations" [14] + +Normally it should be sufficient for all tests to be conducted using normal test conditions except where otherwise stated. For guidance on the use of test conditions to be used in order to show compliance refer to TS 37.141 [10]. + +# --- Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2009-07 | R4#51bis | R4-092358 | | | | Specification skeleton | 0.0.1 | +| 2009-08 | R4#52 | R4-093257 | | | | Agreed Text Proposals in RAN4#52:
R4-093005 , "TS 37.104: TP on Relationship between minimum requirements and test requirements (TS ch 4.2)"
R4-093006 , "TS 37.104: TP on Base station classes (TS ch 4.3)"
R4-093008 , "TS 37.104: TP on Operating bands and Band Categories (TS ch 4.5)"
R4-093009 , "TS 37.104: TP on Channel arrangement (TS ch 4.6)"
R4-093011 , "TS 37.104: TP on Transmitter characteristics - General (TS ch 6.1)"
R4-093012 , "TS 37.104: TP on Output power dynamics (TS ch 6.3)"
R4-093016 , "TS 37.104: TP on Transmitter Intermodulation (TS ch 6.7)"
R4-093017 , "TS 37.104: TP on Receiver characteristics General (TS ch 7.1)"
R4-093018 , "TS 37.104: TP on Reference sensitivity level (TS ch 7.2)"
R4-093019 , "TS 37.104: TP on Dynamic range (TS ch 7.3)"
R4-093022 , "TS 37.104: TP on Receiver spurious emissions (TS ch 7.6)"
R4-093024 , "TS 37.104: TP on In-channel selectivity (TS ch 7.8)"
R4-093375 , "TS 37.104: TP on MSR References and definitions (TS ch 2 and 3)"
R4-093376 , "TS 37.104: TP on Regional requirements (TS ch 4.4)"
R4-093378 , "TS 37.104: TP on Transmitted signal quality (TS ch 6.5)"
R4-093379 , "TS 37.104: TP on Transmitter spurious emissions (TS ch 6.6 and 6.6.1)"
R4-093380 , "TS 37.104: TP on Operating band unwanted emissions (TS ch 6.6.2)"
R4-093381 , "TS 37.104: TP on In-band selectivity and blocking (TS ch 7.4)"
R4-093382 , "TS 37.104: TP on Out-of-band blocking (TS ch 7.5)"
R4-093383 , "TS 37.104: TP on Receiver intermodulation (TS ch 7.7)" | 0.1.0 | +| 2009-09 | RAN #45 | RP-090764 | | | | Presentation to TSG RAN for information | 1.0.0 | +| 2009-10 | R4#52bis | R4-093979 | | | | Agreed Text Proposals in RAN4#52bis:
R4-093788 , "TS 37.104: TP on Relation to other RAN and GERAN specifications (TS ch 4.2)"
R4-093792 , "TS 37.104: TP on Spurious emissions requirements in BC2 (TS ch 6.6.2 and 7.6)"
R4-093796 , "TS 37.104: TP on Characteristics of interfering signals"
R4-094013 , "Clarification on Spurious emissions limits for BS co-existed with another BS (37.104)"
R4-094050 , "TS 37.104: TP on Additional spurious emissions requirement (TS ch 6.6.1.3)"
R4-094051 , "TS 37.104: TP on Introduction of BC2 transmitter requirements (TS ch 6)"
R4-094052 , "TS 37.104: TP on Introduction of BC2 receiver requirements (TS ch 7)"
R4-094053 , "TS 37.104: TP on Applicability of requirements (TS ch 5)"
R4-094054 , "TS 37.104: TP on Performance requirements (TS ch 8)"
R4-094058 , "TP for 37.104 Maximum power requirements" | 1.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2009-11 | R4#53 | R4-094476 | | | | Agreed Text Proposals in RAN4#52bis:
R4-094061 , "A Note of 37.104 MSR category 3 on additional spurious emission requirement when BC3 is deployed in the same geographical area as the PHS"
R4-094062 , "TP of 37.104 on Transmitter intermodulation requirement of MSR category 3"
R4-094063 , "TP of 37.104 on Out-of-band blocking requirement of MSR category 3"
R4-094075 , "Text proposal of transmitter off power for TS37.104"
R4-094076 , "Text proposal of receiver intermodulation of BC3 for TS37.104" | 1.2.0 | +| 2009-11 | R4#53 | R4-094777 | | | | Agreed Text Proposals in RAN4#53:
R4-094403 , "Corrections on frequency range of unwanted emissions requirements (37.104)"
R4-094479 , "TS 37.104: TP on Occupied bandwidth (TS ch 6.6.3)"
R4-094480 , "TS 37.104: TP on remaining BC3 transmitter requirements (TR ch 6)"
R4-094484 , "TS 37.104: TP on Inclusion of requirements by reference (TS ch 5.4)"
R4-094485 , "TS 37.104: TP on additional emission requirements for GSM (TS ch 6.6.2.3)"
R4-094486 , "TS 37.104: TP on General updates"
R4-094540 , "Output Power clarification"
R4-094662 , "TS 37.104: TP for scope update (TS ch 1)"
R4-094663 , "TS 37.104: TP on Environmental requirements for the BS equipment (TS Annex B)"
R4-094862 , "TS 37.104: TP for ACLR requirement (TS ch 6.6.4)"
R4-094863 , "TS 37.104: TP on Applicability of requirements for BC3"
R4-094881 , "Proposed updates of references to TS 45.005 in MSR specification TR 37.104 (GERAN1 AHG1-090157)"
R4-094882 , "TS 37.104: TP on Declared output power parameters"
R4-094883 , "TS 37.104: TP on remaining BC3 receiver requirements (TS ch 7)" | 1.3.0 | +| 2009-12 | RAN #46 | RP-091107 | | | | Presentation to TSG RAN for approval. | 2.0.0 | +| 2009-12 | RAN #46 | RP-091107 | | | | Approved in TSG RAN#46 | 9.0.0 | +| 2010-03 | RAN #47 | RP-100265 | 1 | | | Correction of additional spurious emission requirement for BC2 | 9.1.0 | +| 2010-03 | RAN #47 | RP-100265 | 7 | | | ACLR requirement E-UTRA channel BW <5 MHz | 9.1.0 | +| 2010-03 | RAN #47 | RP-100265 | 3 | | | MSR corrections in TS 37.104 | 9.1.0 | +| 2010-03 | RAN #47 | RP-100265 | 5 | 1 | | Alignment of MSR specification with new items in single-RAT specifications | 9.1.0 | +| 2010-03 | RAN #47 | RP-100265 | 6 | | | Correction of scope | 9.1.0 | +| 2010-06 | RP-48 | RP-100625 | 014 | | | Corrections to clause 7.1 | 9.2.0 | +| 2010-06 | RP-48 | RP-100625 | 013 | 1 | | Corrections to MSR core requirements | 9.2.0 | +| 2010-06 | RP-48 | RP-100625 | 012 | | | Correction to Clause 6.1 | 9.2.0 | +| 2010-06 | RP-48 | RP-100625 | 010 | 1 | | Clarification to the receiver narrowband blocking requirement | 9.2.0 | +| 2010-06 | RP-48 | RP-100625 | 009 | 1 | | Clarification to the receiver narrowband intermodulation requirement | 9.2.0 | +| 2010-06 | RP-48 | RP-100625 | 008 | 2 | | Co-existence with services in adjacent frequency bands | 9.2.0 | +| 2010-06 | RP-48 | RP-100625 | 015 | | | Spurious emissions limits and blocking requirements for coexistence with CDMA850 | 9.2.0 | +| 2010-09 | RP-49 | RP-100922 | 018 | 1 | | TS 37.104 Subclause 7.7; Receiver intermodulation | 9.3.0 | +| 2010-09 | RP-49 | RP-100927 | 016 | | | CR LTE_TDD_2600_US spectrum band definition additions to TS 37.104 | 10.0.0 | +| 2010-12 | RP-50 | RP-101345 | 023 | | | Band XII/12 frequency range | 10.1.0 | +| 2010-12 | RP-50 | RP-101356 | 019 | 4 | | Band 42 and 43 parameters for UMTS/LTE 3500 (TDD) for TS 37.104 | 10.1.0 | +| 2010-12 | RP-50 | RP-101359 | 024 | | | Introduction of Carrier Aggregation for LTE in TS 37.104 | 10.1.0 | +| 2010-12 | RP-50 | RP-101361 | 020 | | | Protection of E-UTRA Band 24 | 10.1.0 | +| 2011-04 | RP-51 | RP-110357 | 0029 | - | | Band 42 and 43 co-existence for UMTS/LTE 3500 (TDD) for TS 37.104 | 10.2.0 | +| 2011-06 | RP-52 | RP-110794 | 033 | | | Modifications to Band 3 to allow LTE Band 3 operation in Japan (Rel-10 TS37.104 CR) | 10.3.0 | +| 2011-06 | RP-52 | RP-110812 | 034 | | | Add 2GHz S-Band (Band 23) in 37.104 | 10.3.0 | +| 2011-06 | RP-52 | RP-110804 | 035 | | | Add Expanded 1900MHz band in 37.104 | 10.3.0 | +| 2011-06 | RP-52 | RP-110794 | 041 | | | Correction of RX spurious emissions for non-GSM/EDGE configurations | 10.3.0 | +| 2011-06 | RP-52 | RP-110802 | 044 | | | Co-existence/co-location between Band 42 and 43 in TS 37.104 | 10.3.0 | +| 2011-06 | RP-52 | RP-110807 | 043 | 1 | | LTE CA alignment of definitions in TS 37.104 | 10.3.0 | + +| | | | | | | | | +|---------|-------|-----------|-----|---|--|-------------------------------------------------------------------------------------------|--------| +| 2011-06 | RP-52 | RP-110794 | 039 | 1 | | General corrections for TS 37.104 | 10.3.0 | +| 2011-06 | RP-52 | RP-110795 | 037 | 3 | | Fixing Band 24 inclusion in TS 37.104 | 10.3.0 | +| 2011-06 | RP-52 | RP-110805 | 042 | 1 | | MSR-NC Core requirements | 10.3.0 | +| 2011-06 | RP-52 | RP-110794 | 046 | 2 | | Revision of Time Alignment Error definition | 10.3.0 | +| 2011-09 | RP-53 | RP-111252 | 051 | | | Correcting the time alignment text in the applicability tables | 10.4.0 | +| 2011-09 | RP-53 | RP-111255 | 052 | 1 | | Add Band 22/XXII for LTE/UMTS 3500 (FDD) to TS 37.104 | 10.4.0 | +| 2011-09 | RP-53 | RP-111262 | 049 | | | Co-existence and co-location corrections in 37.104 | 10.4.0 | +| 2011-12 | RP-54 | RP-111735 | 053 | | | Definition of multi-carrier configuration | 10.5.0 | +| 2011-12 | RP-54 | RP-111734 | 054 | | | Clarification of general blocking requirements for co-existence in TS 37.104 | 10.5.0 | +| 2011-12 | RP-54 | RP-111735 | 055 | | | CR to TS37.104 Adding the OBW requirements for carrier aggregation | 10.5.0 | +| 2011-12 | RP-54 | RP-111735 | 056 | | | Correction of MSR NC requirements | 10.5.0 | +| 2011-12 | RP-54 | RP-111687 | 058 | 2 | | TX ON or OFF CR 37.104 | 10.5.0 | +| 2011-12 | RP-54 | RP-111733 | 059 | | | Correction of frequency range for spurious emission requirements | 10.5.0 | +| 2012-03 | RP-55 | RP-120303 | 062 | | | Update to improve readability of tables in section 4.5 of 37.104 | 10.6.0 | +| 2012-03 | RP-55 | RP-120303 | 063 | | | Absolute limit for CACL: Removal of brackets | 10.6.0 | +| 2012-03 | RP-55 | RP-120304 | 065 | 1 | | Definition of synchronized operation | 10.6.0 | +| 2012-03 | RP-55 | RP-120303 | 066 | 1 | | Introduction of NC operation for TDD in 37.104 | 10.6.0 | +| 2012-03 | RP-55 | RP-120305 | 061 | | | Add Extending 850 MHz Upper Band (814 - 849 MHz) to TS37.104 | 11.0.0 | +| 2012-06 | RP-56 | RP-120793 | 069 | - | | Introduction of APAC700(FDD) into TS 37.104 | 11.1.0 | +| 2012-06 | RP-56 | RP-120771 | 072 | - | | Introduction of Japanese Regulatory Requirements to W-CDMA Band VIII (R11) | 11.1.0 | +| 2012-06 | RP-56 | RP-120777 | 074 | - | | Additional BC3 blocking | 11.1.0 | +| 2012-06 | RP-56 | RP-120793 | 075 | 1 | | Introduction of Band 44 | 11.1.0 | +| 2012-06 | RP-56 | RP-120791 | 076 | 2 | | Introduction of E850 LB (Band 27) to MSR TS 37.104 | 11.1.0 | +| 2012-09 | RP-57 | RP-121310 | 078 | - | | Applicability of Cumulative ACLR | 11.2.0 | +| 2012-09 | RP-57 | RP-121310 | 080 | - | | Correct the f_offsetmax definition for TS 37.104 | 11.2.0 | +| 2012-09 | RP-57 | RP-121308 | 081 | 2 | | Reusing band 41 requirements for the Japan 2.5G TDD band | 11.2.0 | +| 2012-09 | RP-57 | RP-121310 | 083 | 1 | | Intra-band non-contiguous receiver requirements | 11.2.0 | +| 2012-09 | RP-57 | RP-121310 | 085 | - | | Deleting additional BC3 transmitter intermodulation requirement for NC MSR | 11.2.0 | +| 2012-09 | RP-57 | RP-121300 | 088 | - | | Modifications of frequency ranges on spurious emission requirements for Band 6, 18, 19 | 11.2.0 | +| 2012-09 | RP-57 | RP-121310 | 090 | 1 | | Clean-up of ACLR wording for MSR-NC | 11.2.0 | +| 2012-09 | RP-57 | RP-121340 | 091 | 1 | | Modification to increase GSM Carrier Power in MSR BS for Band Category 2 | 11.2.0 | +| 2012-09 | RP-57 | | | | | Editorial correction in Table 6.6.2.2-2 | 11.2.1 | +| 2012-12 | RP-58 | RP-121906 | 094 | | | Introduction of new BS classes to MSR specification (general parts) | 11.3.0 | +| 2012-12 | RP-58 | RP-121857 | 095 | | | Correction to additional BS spurious emissions limits for BC2 | 11.3.0 | +| 2012-12 | RP-58 | RP-121859 | 098 | | | Correction of PHS protection requirement | 11.3.0 | +| 2012-12 | RP-58 | RP-121906 | 101 | 2 | | Introduction of new BS classes to MSR specification (Clause 6) | 11.3.0 | +| 2012-12 | RP-58 | RP-121906 | 102 | | | Introduction of new BS classes to MSR specification (receiver part) | 11.3.0 | +| 2012-12 | RP-58 | RP-121867 | 104 | 1 | | Modification on ACLR requirement | 11.3.0 | +| 2012-12 | RP-58 | RP-121867 | 107 | | | Clean up of specification R11 | 11.3.0 | +| 2012-12 | RP-58 | RP-121905 | 108 | 1 | | Introduction of multi-band operation to MSR specification (section 4) | 11.3.0 | +| 2012-12 | RP-58 | RP-121905 | 109 | 1 | | CR for TS37.104(Clause 1-3) due to introduction of multi-band MSR operation | 11.3.0 | +| 2012-12 | RP-58 | RP-121905 | 110 | 1 | | Introduction of MB-MSR to MSR specification (Clause 6) | 11.3.0 | +| 2012-12 | RP-58 | RP-121864 | 112 | | | Transmitter IM correction for MSR-NC | 11.3.0 | +| 2012-12 | RP-58 | RP-121905 | 113 | | | Applicability of requirements for MB-MSR | 11.3.0 | +| 2012-12 | RP-58 | RP-121899 | 115 | | | Update CA reference to include Non Contiguous CA band combinations | 11.3.0 | +| 2012-12 | RP-58 | RP-121901 | 116 | | | Introduction of Band 29 | 11.3.0 | +| 2012-12 | RP-58 | RP-121905 | 117 | 1 | | Introduction of MB-MSR to MSR core specification (Clause 7) | 11.3.0 | +| 2012-12 | RP-58 | RP-121857 | 118 | | | Modification to increase GSM Carrier Power in MSR BS for Band Category 2 | 11.3.0 | +| 2012-12 | | | | | | Editorial Correction | 11.3.0 | +| 2013-03 | RP-59 | RP-130282 | 121 | | | Clarify unclear description in UEM requirement for MB-MSR in TS 37.104 | 11.4.0 | +| 2013-03 | RP-59 | RP-130282 | 125 | | | Some clarifications on MB-MSR requirement in TS 37.104 | 11.4.0 | +| 2013-03 | RP-59 | RP-130282 | 126 | 1 | | Introduction of MB-MSR to MR/LA BS in TS 37.104 | 11.4.0 | +| 2013-03 | RP-59 | RP-130287 | 129 | | | Correction of co-existence spurious emission requirement with Band 23 for TS 37.104 (R11) | 11.4.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------|--------| +| 2013-03 | RP-59 | RP-130287 | 130 | | | Band 41 requirements for operation in Japan | 11.4.0 | +| 2013-06 | RP-60 | RP-130769 | 135 | | | Definition of Inter RF bandwidth gap | 11.5.0 | +| 2013-06 | RP-60 | RP-130764 | 138 | | | Corrections to transmitter intermodulation test requirement | 11.5.0 | +| 2013-06 | RP-60 | RP-130763 | 142 | | | channel raster | 11.5.0 | +| 2013-06 | RP-60 | RP-130769 | 144 | 2 | | Mapping of requirements on antenna ports | 11.5.0 | +| 2013-06 | RP-60 | RP-130791 | 145 | 1 | | Introduction of Band 30 | 12.0.0 | +| 2013-06 | RP-60 | RP-130790 | 147 | | | Introduction of LTE 450 into TS 37.104 | 12.0.0 | +| 2013-09 | RP-61 | RP-131289 | 154 | | | Single-RAT operation for MB-MSR | 12.1.0 | +| 2013-09 | RP-61 | RP-131280 | 155 | | | UEM requirement in BC2 for lower BS output power | 12.1.0 | +| 2013-09 | RP-61 | RP-131289 | 157 | | | Clarification on single-band operation for MB-MSR | 12.1.0 | +| 12-2013 | RP-62 | RP-131927 | 160 | | | Clarification of Tx IM requirement for BC1 band supporting non-contiguous operation | 12.2.0 | +| 12-2013 | RP-62 | RP-131930 | 162 | | | Inclusion of requirements by reference for BS classes | 12.2.0 | +| 12-2013 | RP-62 | RP-131959 | 167 | | | Changes to TS 37.104 for LTE CA_C B27 | 12.2.0 | +| 12-2013 | RP-62 | RP-131934 | 169 | | | CR for clarification for receiver requirement on MB-MSR BS | 12.2.0 | +| 12-2013 | RP-62 | RP-131926 | 172 | | | Introduction of secondary CPICH requirement | 12.2.0 | +| 12-2013 | RP-62 | RP-131930 | 174 | | | Corrections to requirements for multi-band operation | 12.2.0 | +| 12-2013 | RP-62 | RP-131967 | 176 | | | Band 41 deployment in Japan | 12.2.0 | +| 12-2013 | RP-62 | RP-131925 | 182 | | | Correction of references | 12.2.0 | +| 03-2014 | RP-63 | RP-140370 | 193 | | | Clarification of interfering signals for receiver intermodulation requirement in MSR | 12.3.0 | +| 06-2014 | RP-64 | RP-140913 | 196 | | | Update of TS 37.104 | 12.4.0 | +| 06-2014 | RP-64 | RP-140913 | 207 | | | Clarification on definitions and ACLR requirement in TS37.104 | 12.4.0 | +| 06-2014 | RP-64 | RP-140913 | 211 | | | Correction of UEM for Medium Range and Local Area BS | 12.4.0 | +| 06-2014 | RP-64 | RP-140914 | 202 | | | Band 29 correction | 12.4.0 | +| 06-2014 | RP-64 | RP-140918 | 219 | | | Clarification of Foffset-RAT in relation to radio bandwidth in TS 37.104 (Rel-12) | 12.4.0 | +| 06-2014 | RP-64 | RP-140926 | 208 | 1 | | Introduction of Band 32/XXXII | 12.4.0 | +| 09-2014 | RP-65 | RP-141528 | 232 | | | Correction on UEM related to multi-band operation in TS37.104 | 12.5.0 | +| 09-2014 | RP-65 | RP-141562 | 233 | 1 | | Update of definitions to support supplemental DL in TS37.104 | 12.5.0 | +| 12-2014 | RP-66 | RP-142146 | 242 | | | Tx intermodulation corrections | 12.6.0 | +| 03-2015 | RP-67 | RP-150382 | 250 | | | Co-location between Band 42 and Band 43 in TS 37.104 | 12.7.0 | +| 03-2015 | RP-67 | RP-150388 | 251 | | | MB and TDD+FDD | 12.7.0 | +| 07-2015 | RP-68 | RP-150955 | 255 | | | Clarification of parameter P for emission requirements | 12.8.0 | +| 07-2015 | RP-68 | RP-150955 | 259 | | | Some corrections related to RF bandwidth edge | 12.8.0 | +| 12-2015 | RP-70 | RP-152132 | 0269 | - | | Tx IM requirement correction | 12.9.0 | +| 12-2015 | RP-70 | RP-152132 | 0274 | - | | BS Spec improvements: TS 37.104 Corrections | 12.9.0 | +| 12-2015 | RP-70 | RP-152132 | 0276 | - | | Corrections on definition of f_offsetmax for BS operating in multiple bands or non-contiguous spectrum | 12.9.0 | +| 12-2015 | RP-70 | RP-152132 | 0280 | - | | Correction of Unwanted Emission Mask (UEM) for MSR BS capable of multiband operation | 12.9.0 | +| 12-2015 | RP-70 | RP-152171 | 0265 | - | | Introduction of Band 66 | 13.0.0 | +| 12-2015 | RP-70 | RP-152157 | 0270 | 1 | | Introduction of Band 67 to 37.104 | 13.0.0 | +| 12-2015 | RP-70 | RP-152172 | 0271 | - | | Introduction of Band 66 | 13.0.0 | +| 12-2015 | RP-70 | RP-152173 | 0272 | - | | Introduction of 1447-1467MHz Band into 37.104 | 13.0.0 | +| 03/2016 | RP-71 | RP-160483 | 0281 | 2 | B | Introduction of Band 68 into 37.104 | 13.1.0 | +| 03/2016 | RP-71 | RP-160488 | 0285 | | A | Band 20 and Band 28 BS co-existence | 13.1.0 | +| 06/2016 | RP-72 | RP-161141 | 288 | 1 | A | Corrections to BS spurious emissions requirements in TS37.104 (Rel-13) | 13.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------|--------| +| 06/2016 | RP-72 | RP-161140 | 292 | 1 | F | Corrections on definition of multi-band definition and blocking | 13.2.0 | +| 06/2016 | RP-72 | RP-161126 | 293 | - | B | CR on introduction of NB-IoT in TS 37.104 | 13.2.0 | +| 06/2016 | RP-72 | RP-161142 | 294 | 1 | F | Introduction of Band 46 in 37.104 | 13.2.0 | +| 06/2016 | RP-72 | RP-161125 | 291 | - | B | Introduction of Band 70 to 37.104 | 14.0.0 | +| 06/2016 | RP-72 | RP-161124 | 295 | - | B | Introduction of Band 69 to 37.104 | 14.0.0 | +| 09/2016 | RP-73 | RP-161637 | 297 | | A | Corrections on NB-IoT BS unwanted emissions requirements | 14.1.0 | +| 09/2016 | RP-73 | RP-161640 | 299 | | A | Corrections to operating band unwanted emissions notes in TS37.104 (Rel-14) | 14.1.0 | +| 12/2016 | RP-74 | RP-162434 | 0307 | 1 | F | NB-IoT corrections to operating bands | 14.2.0 | +| 12/2016 | RP-74 | RP-162407 | 0308 | - | B | Addition of new operating bands for NB-IoT | 14.2.0 | +| 12/2016 | RP-74 | RP-162434 | 0309 | - | A | Spurious responses for NB-IoT BS receiver blocking requirements | 14.2.0 | +| 12/2016 | RP-74 | RP-162413 | 0312 | - | A | Removal of redundant figure in clause 3.2 | 14.2.0 | +| 12/2016 | RP-74 | RP-162395 | 0313 | 1 | B | Necessary changes to the core requirements for Multi-Band Base Station testing with three or more bands | 14.2.0 | +| 12/2016 | RP-74 | RP-162405 | 0315 | - | B | Introduction of Band 48 | 14.2.0 | +| 03/2017 | RP-75 | RP-170553 | 0316 | - | B | CR on eLAA BS for TS 37.104 | 14.3.0 | +| 03/2017 | RP-75 | RP-170598 | 0320 | - | A | Corrections on NB-IoT narrowband intermodulation performance requirement | 14.3.0 | +| 06/2017 | RP-76 | RP-171279 | 0321 | 1 | B | Introduction of new bands for NB-IoT in 37.104 | 14.4.0 | +| 06/2017 | RP-76 | RP-171297 | 0329 | 1 | A | TS 37.104: Correction of reference | 14.4.0 | +| 06/2017 | RP-76 | RP-171282 | 0776 | 1 | F | CR on BS for protection of V2X UE in TS 37.104 | 14.4.0 | +| 06/2017 | RP-76 | RP-171300 | 0778 | - | A | Missing clarification note related to BS output power when considering NB-IoT | 14.4.0 | +| 06/2017 | RP-76 | RP-171299 | 0780 | - | A | Remove NB-IoT inband support for 1.4 MHz | 14.4.0 | +| 06/2017 | RP-76 | RP-171299 | 0783 | - | A | Narrowband blocking requirement for NB-IoT guard band operation (TS 37.104) | 14.4.0 | +| 06/2017 | RP-76 | RP-171300 | 0785 | - | A | Intermodulation performance requirement for NB-IoT operation (TS 37.104) | 14.4.0 | +| 09/2017 | RP-77 | RP-171966 | 0787 | - | A | Operating band unwanted emissions for MB MSR BS (TS 37.104) | 14.5.0 | +| 09/2017 | RP-77 | RP-171948 | 0788 | 2 | B | Introduction of the FDD L-band (Band 74) into TS 37.104 | 15.0.0 | +| 09/2017 | RP-77 | RP-171946 | 0789 | - | B | CR to 37.104: Introduction of Band 72 | 15.0.0 | +| 09/2017 | RP-77 | RP-171952 | 0790 | - | B | CR to 37.104: Introduction of Band 71 | 15.0.0 | +| 09/2017 | RP-77 | RP-171950 | 0792 | 1 | B | CR to 37.104: Introduction of B75 and B76 | 15.0.0 | +| 09/2017 | RP-77 | RP-171949 | 0793 | 1 | B | Introduction of TDD L-band into TS 37.104 | 15.0.0 | +| 09/2017 | RP-77 | RP-172050 | 0794 | - | B | CR to 37.104: Support of NB-IoT for Bands 4, 14 and 71 | 15.0.0 | +| 2017-12 | RAN#78 | RP-172593 | 0795 | 1 | B | Introduction of Band 73 into TS 37.104 | 15.1.0 | +| 2017-12 | RAN#78 | RP-172613 | 0798 | - | A | CR to 37.104: BS Spurious emissions limits for protection of the BS receiver for B28 in Europe | 15.1.0 | +| 2017-12 | RAN#78 | RP-172605 | 0801 | 1 | A | Corrections for MB MSR BS supporting non-contiguous spectrum operation (TS 37.104) | 15.1.0 | +| 2017-12 | RAN#78 | RP-172584 | 0803 | - | A | CR to 37.104: Corrections to co-location tables for B48 | 15.1.0 | +| 2017-12 | RAN#78 | RP-172594 | 0804 | 1 | B | CR to 37.104: Introduction of Band 49 | 15.1.0 | +| 2017-12 | RAN#78 | RP-172588 | 0805 | - | B | Addition of NB-IoT small cells support | 15.1.0 | +| 2018-03 | RAN#79 | RP-180279 | 0806 | - | B | CR to 37.104: Introduction of Band 85 | 15.2.0 | +| 2018-03 | RAN#79 | RP-180281 | 0807 | 1 | B | CR to 37.104: Introduction of new additional unwanted emission limit for L-Band | 15.2.0 | +| 2018-03 | RAN#79 | RP-180267 | 0808 | 1 | F | CR NB-IoT small cells: co-location requirements fix | 15.2.0 | +| 2018-03 | RAN#79 | RP-180278 | 0809 | - | B | Introduction of TDD 3.3-3.4GHz band (band 52) | 15.2.0 | +| 2018-06 | RAN#80 | RP-181100 | 0815 | - | F | CR to 37.104: Medium Range BS UEM corrections | 15.3.0 | +| 2018-06 | RAN#80 | RP-181075 | 0816 | - | B | Introduction of NR operation in MSR specification 37.104 | 15.3.0 | +| 2018-09 | RAN#81 | RP-181896 | 0817 | 1 | F | CR on spurious emission in 37.104 | 15.4.0 | +| 2018-09 | RAN#81 | RP-181899 | 0818 | | B | CR of BS REFSENS for SubPRB feature | 15.4.0 | +| 2018-09 | RAN#81 | RP-181896 | 0820 | | F | Clarification on UEM requirements applicability | 15.4.0 | +| 2018-09 | RAN#81 | RP-181896 | 0821 | | B | Addition parameters about n50 in TS 37.104 | 15.4.0 | +| 2018-12 | RAN#82 | RP-182386 | 0822 | | B | Re-submission of endorsed CR R4-1806736: Introduction of NB-IoT TDD support | 15.5.0 | +| 2018-12 | RAN#82 | RP-182361 | 0825 | | F | Corrections to NR operation in MSR specification 37.104 | 15.5.0 | +| 2018-12 | RAN#82 | RP-182362 | 0826 | 1 | B | Update the title to add NR of TS 37.104 | 15.5.0 | +| 2018-12 | RAN#82 | RP-182360 | 0828 | | F | Addition of NR band n74 | 15.5.0 | +| 2018-12 | RAN#82 | RP-182360 | 0829 | 1 | F | Correction of CS16/17 NBB requirement | 15.5.0 | +| 2018-12 | RAN#82 | RP-182361 | 0831 | | F | Corrections to NR operation in MSR specification 37.104 | 15.5.0 | +| 2018-12 | RAN#82 | RP-182377 | 0823 | | B | CR of adding B65 for NB1/NB2 | 16.0.0 | +| 2018-12 | RAN#82 | RP-182375 | 0824 | | F | Removal of CA bands list for E-UTRA | 16.0.0 | +| 2018-12 | RAN#82 | RP-182376 | 0830 | | B | CR to 37.104: Introduction of Band 53 | 16.0.0 | +| 2019-03 | RAN#83 | RP-190402 | 0834 | | A | Correction of TDD OFF requirement | 16.1.0 | +| 2019-03 | RAN#83 | RP-190401 | 0838 | | A | CR to TS 37.104 – Blocking requirement for MSR | 16.1.0 | +| 2019-03 | RAN#83 | RP-190401 | 0842 | | A | CR to TS 37.104: Corrections on transmitter co-existence and co-location | 16.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------|--------| +| 2019-03 | RAN#83 | RP-190421 | 0844 | | A | CR to 37.104: clean up for LTE-M related text | 16.1.0 | +| 2019-03 | RAN#83 | RP-190401 | 0846 | | A | CR to 37.104 on Corrections for NR | 16.1.0 | +| 2019-06 | RAN#84 | RP-191236 | 0849 | 1 | A | Correction to unwanted emissions mask for bands n7 and n38 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191248 | 0852 | | B | CR to 37.104: Introduction of Band n48 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191242 | 0853 | | B | CR to TS 37.104: Introduction of band n14 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191246 | 0854 | | B | CR to TS 37.104: Introduction of band n30 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191250 | 0857 | 1 | B | n65 introduction to 37.104 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191236 | 0859 | | A | Correction to n66 and n70 band information | 16.2.0 | +| 2019-06 | RAN#84 | RP-191256 | 0861 | | B | CR to 37.104: Introduction of Band 87 and 88 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191245 | 0862 | | B | CR to 37.104: Introduction of Band n18 | 16.2.0 | +| 2019-09 | RAN#85 | RP-192025 | 0863 | | B | Introduction of requirements for NR + UTRA/GSM combinations | 16.3.0 | +| 2019-09 | RAN#85 | RP-192046 | 0865 | | A | CR to TS 37.104 some clarification as blocking test range Cat.A | 16.3.0 | +| 2019-09 | RAN#85 | RP-192046 | 0867 | | A | CR to TS 37.104 TX&RX spurious emission range subclause 6.6.1.1&7.6.1 Cat.A | 16.3.0 | +| 2019-09 | RAN#85 | RP-192046 | 0869 | | A | CR to TS 37.104: CA channel spacing | 16.3.0 | +| 2019-09 | RAN#85 | RP-192046 | 0873 | | A | CR to TS37.104: removal of Tx diversity for NR (section 6.5.3) | 16.3.0 | +| 2019-09 | RAN#85 | RP-192046 | 0875 | | A | CR to TS37.104 Corrections on NBB requirement (section 7.4.2) | 16.3.0 | +| 2019-09 | RAN#85 | RP-192030 | 0876 | | F | CR on Protection of SUL band n89 to TS 37.104 | 16.3.0 | +| 2019-09 | RAN#85 | RP-192034 | 0877 | 1 | B | n29 introduction to 37.104 | 16.3.0 | +| 2019-09 | RAN#85 | RP-192044 | 0878 | 1 | B | CR of adding LTE B42/B43 for UE category NB1/NB2 in R16 | 16.3.0 | +| 2019-09 | RAN#85 | RP-192043 | 0879 | 1 | B | CR of adding LTE B7 for UE category NB1/NB2 in R16 | 16.3.0 | +| 2019-12 | RAN#86 | RP-193014 | 0880 | | B | Introduction of 2010-2025MHz SUL band into Rel-16 TS 37.104 | 16.4.0 | +| 2019-12 | RAN#86 | RP-193037 | 0883 | | A | CR to 37.104 on Receiver Intermodulation signal offset correction | 16.4.0 | +| 2019-12 | RAN#86 | RP-193023 | 0886 | 1 | B | CR to TS 37.104: introduction of NB-IoT operation in NR in-band | 16.4.0 | +| 2019-12 | RAN#86 | RP-193037 | 0888 | | A | Introduction of channel spacing between E-UTRA and NR carriers | 16.4.0 | +| 2019-12 | RAN#86 | RP-193037 | 0890 | | A | Narrowband blocking corrections | 16.4.0 | +| 2019-12 | RAN#86 | RP-193037 | 0890 | | A | CR to TS 37.104: Correction to Tx transient period of MSR | 16.4.0 | +| 2019-12 | RAN#86 | RP-193149 | 0892 | 1 | B | CR to 37.104 on variable duplex FDD bands | 16.4.0 | +| 2020-03 | RAN#87 | RP-200381 | 0893 | | B | Introduction of n26 | 16.5.0 | +| 2020-03 | RAN#87 | RP-200382 | 0894 | | B | Introduction of n53 | 16.5.0 | +| 2020-03 | RAN#87 | RP-200393 | 0896 | | A | CR to TS 37.104 on channel spacing correction | 16.5.0 | +| 2020-06 | RAN#88 | RP-200984 | 0899 | | A | [R16]CR to TS 37.104 on channel spacing correction | 16.6.0 | +| 2020-06 | RAN#88 | RP-200984 | 0901 | | A | CR to TS37.104[R16]_ Correction on the CA nominal channel spacing catA | 16.6.0 | +| 2020-06 | RAN#88 | RP-200990 | 0903 | | A | CR to 37.104 on Removal of TBD for NB-IoT (Rel-16) | 16.6.0 | +| 2020-09 | RAN#89 | RP-201917 | 0907 | | B | CR to 37.104: Introduction of NR-U co-existence requirements | 16.7.0 | +| 2020-12 | RAN#90 | RP-202509 | 0912 | | F | CR to TS 37.104: addition of missing note for BC1/BC3 OBUE applicability table for WA BS, Rel-16 | 16.8.0 | +| 2020-12 | RAN#90 | RP-202488 | 0914 | | A | CR to 37.104: Correction to ACLR limit in non-contiguous spectrum (Rel-16) | 16.8.0 | +| 2020-12 | RAN#90 | RP-202414 | 0915 | | B | CR to 37.104: Introduction of n96 medium range requirements | 16.8.0 | +| 2020-12 | RAN#90 | RP-202510 | 0917 | | A | CR to 37.104 on Removal of additional limit for Band 1 | 16.8.0 | +| 2020-12 | RAN#90 | RP-202510 | 0919 | | A | CR to 37.104 on MSR Blocking correction | 16.8.0 | +| 2020-12 | RAN#90 | RP-202451 | 0908 | | B | Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.104 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202452 | 0909 | | B | Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.104 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202448 | 0911 | | B | CR to TS 37.104: introduction of NR band n13 | 17.0.0 | +| 2021-03 | RAN#91 | RP-210096 | 0920 | | B | CR to 37.104 on introducing new SUL band n99 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210110 | 0921 | 1 | B | CR of adding LTE B24 for UE category NB1/NB2 in R17 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210084 | 0923 | | A | CR to TS 37.104: corrections of NR-U BS RF requirements | 17.1.0 | +| 2021-03 | RAN#91 | RP-210097 | 0924 | | B | CR to 37.104: Introduction of n24 requirements | 17.1.0 | +| 2021-03 | RAN#91 | RP-210111 | 0932 | | A | CR to 37.104: Correction to Band 24 requirements (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210121 | 0936 | | A | CR to 37.104 on OBUE table headings and applicability | 17.1.0 | +| 2021-06 | RAN#92 | RP-211076 | 0939 | | A | CR to TS 37.104: Regional requirements for band 41, n41, and n90 in Japan, Rel-17 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0940 | | B | CR to TS 37.104: Introduction of band n67 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0941 | | B | CR to TS 37.104: Introduction of band n85 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211090 | 0944 | | A | CR to 37.104: In-band blocking for multi-band Base Stations | 17.2.0 | +| 2021-06 | RAN#92 | RP-211091 | 0947 | | F | CR to 37.104: Correction of NR bands for MSR BS | 17.2.0 | +| 2021-09 | RAN#93 | RP-211909 | 0949 | | B | CR to 37.104: Introduction of requirements for 35 and 45MHz channel bandwidths | 17.3.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|----------------------------------------------------------------|--------| +| 2021-09 | RAN#93 | RP-211922 | 0951 | | F | Big CR for TS 37.104 Maintenance (Rel-17, CAT F) | 17.3.0 | +| 2021-12 | RAN#94 | RP-212854 | 0955 | | A | Big CR for TS 37.104 Maintenance (Rel-17, CAT A) | 17.4.0 | +| 2022-03 | RAN#95 | RP-220357 | 0958 | | B | CR to 37.104 on introduction of n102 co-existence requirements | 17.5.0 | +| 2022-03 | RAN#95 | RP-220347 | 0956 | 1 | B | CR to TS37.104 on introduction of upper 700MHz A block | 17.5.0 | +| 2022-03 | RAN#95 | RP-220331 | 0961 | | A | Big CR for TS 37.104 Maintenance (Rel-17, CAT A) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220376 | 0962 | | B | CR to TS 37.104: RMR 1900MHz band n101 introduction | 17.5.0 | +| 2022-06 | RAN#96 | RP-221684 | 0963 | | B | CR to 37.104 on introduction of n100 co-existence requirements | 17.6.0 | +| 2022-06 | RAN#96 | RP-221673 | 0964 | | B | CR to 37.104 on introduction of n104 co-existence requirements | 17.6.0 | +| 2022-06 | RAN#96 | RP-221664 | 0967 | | A | CR to 37.104: Corrections to notes in OBUE requirements | 17.6.0 | +| 2022-06 | RAN#96 | RP-221669 | 0968 | | B | CR on adding B48 for M1/M2/NB1/NB2 | 17.6.0 | +| 2022-09 | RAN#97-e | RP-222023 | 0971 | | A | Big CR for TS 37.104 Maintenance (Rel-17, CAT A) | 17.7.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | RP-223315 | 0972 | | B | CR to 37.104 on introduction of Band 54 | 18.0.0 | +| 2022-12 | RAN#98-e | RP-223319 | 0973 | 1 | B | CR to 37.104 on introduction of Band n105 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230527 | 0975 | | F | Adds reference for additional spurious emission levels for Band 54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230524 | 0976 | 1 | B | CR related to Introduction of support of NB1/NB2 for LTE TDD Band 54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230535 | 0977 | | B | CR to 37.104 on introduction of Band n54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230508 | 0982 | | A | CR to TS 37.104: Additional requirements for BC3 | 18.1.0 | +| 2023-06 | RAN#100 | RP-231352 | 0985 | | A | CR to 37.104: Clarification on the OBUE limites when narrow carrier adjacent to the sub block edge | 18.2.0 | +| 2023-06 | RAN#100 | RP-231362 | 0986 | | B | CR to 37.104 on introduction of Band 106 | 18.2.0 | +| 2023-09 | RAN#101 | RP-232487 | 0991 | | A | CR to 37.104: Correction to ACLR and CACLR requirement | 18.3.0 | +| 2023-09 | RAN#101 | RP-232500 | 0999 | 1 | A | [RInImp9-Rfmulti, TE18] CR to TS 37.104: FFS removal, Rel-18 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 1000 | 1 | B | CR to TS 37.104 Introduction of n109 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233332 | 1006 | | A | CR to 37.104: Correction to table note for band 66 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 1007 | | B | CR to 37.104 on introduction of Band n31 and n72 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 1008 | | B | CR to 37.104 on introduction of Band n106 | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37105/raw.md b/marked/Rel-18/37_series/37105/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..98adbe04054974ee6602b888cf5b984118d14855 --- /dev/null +++ b/marked/Rel-18/37_series/37105/raw.md @@ -0,0 +1,9081 @@ + + +# 3GPP TS 37.105 V18.3.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Active Antenna System (AAS) Base Station (BS) transmission and reception (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------|----| +| Foreword..... | 19 | +| 1 Scope..... | 21 | +| 2 References..... | 21 | +| 3 Definitions, symbols and abbreviations..... | 23 | +| 3.1 Definitions..... | 23 | +| 3.2 Symbols..... | 27 | +| 3.3 Abbreviations..... | 28 | +| 4 General..... | 29 | +| 4.1 Relationship between the AAS BS specification and non-AAS BS single RAT & MSR specifications..... | 29 | +| 4.2 Relationship between minimum requirements and test requirements..... | 30 | +| 4.3 Conducted and radiated requirement reference points..... | 30 | +| 4.4 Base station classes for AAS BS..... | 31 | +| 4.5 Regional requirements..... | 32 | +| 4.6 Operating Bands and Band Categories..... | 34 | +| 4.7 Channel arrangements..... | 34 | +| 4.8 Requirements for contiguous and non-contiguous spectrum..... | 34 | +| 4.9 Requirements for AAS BS capable of operation in multiple operating bands..... | 34 | +| 4.10 OTA Co-location with other base stations..... | 35 | +| 5 Applicability of Requirements..... | 36 | +| 5.1 General..... | 36 | +| 5.2 Band category 1 (BC1) and band category 2 (BC2)..... | 37 | +| 5.3 Band category 3 (BC3)..... | 40 | +| 6 Conducted transmitter characteristics..... | 42 | +| 6.1 General..... | 42 | +| 6.2 Base station output power..... | 43 | +| 6.2.1 General..... | 43 | +| 6.2.2 Maximum output power..... | 43 | +| 6.2.2.1 General..... | 43 | +| 6.2.2.2 Minimum requirement for MSR operation..... | 44 | +| 6.2.2.2.1 General..... | 44 | +| 6.2.2.2.2 Additional requirements (regional)..... | 44 | +| 6.2.2.3 Minimum requirement for single RAT UTRA operation..... | 44 | +| 6.2.2.4 Minimum requirement for single RAT E-UTRA operation..... | 44 | +| 6.2.2.4.1 General..... | 44 | +| 6.2.2.4.2 Additional requirements (regional)..... | 44 | +| 6.2.3 UTRA FDD primary CPICH power..... | 44 | +| 6.2.3.1 General..... | 44 | +| 6.2.3.2 Minimum requirement for MSR operation..... | 44 | +| 6.2.3.3 Minimum requirement for single RAT UTRA operation..... | 44 | +| 6.2.3.4 Minimum requirement for single RAT E-UTRA operation..... | 45 | +| 6.2.4 UTRA TDD primary CCPCH power..... | 45 | +| 6.2.4.1 General..... | 45 | +| 6.2.4.2 Minimum requirement for MSR operation..... | 45 | +| 6.2.4.3 Minimum requirement for single RAT UTRA operation..... | 45 | +| 6.2.4.4 Minimum requirement for single RAT E-UTRA operation..... | 46 | +| 6.2.5 UTRA FDD additional CPICH power for MIMO mode..... | 46 | +| 6.2.5.1 General..... | 46 | +| 6.2.5.2 Minimum requirement for MSR operation..... | 46 | +| 6.2.5.3 Minimum requirement for single RAT UTRA operation..... | 46 | +| 6.2.5.4 Minimum requirement for single RAT E-UTRA operation..... | 47 | +| 6.2.6 E-UTRA DL RS power..... | 47 | +| 6.2.6.1 General..... | 47 | +| 6.2.6.2 Minimum requirement for MSR operation..... | 48 | +| 6.2.6.3 Minimum requirement for single RAT UTRA operation..... | 48 | + +| | | | +|---------|----------------------------------------------------------|----| +| 6.2.6.4 | Minimum requirement for single RAT E-UTRA operation..... | 48 | +| 6.3 | Output power dynamics..... | 48 | +| 6.3.1 | General..... | 48 | +| 6.3.2 | UTRA Inner loop power control in the downlink..... | 48 | +| 6.3.2.1 | General..... | 48 | +| 6.3.2.2 | Minimum requirement for MSR operation..... | 48 | +| 6.3.2.3 | Minimum requirement for single RAT UTRA operation..... | 48 | +| 6.3.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 49 | +| 6.3.3 | Power control dynamic range..... | 49 | +| 6.3.3.1 | General..... | 49 | +| 6.3.3.2 | Minimum requirement for MSR operation..... | 49 | +| 6.3.3.3 | Minimum requirement for single RAT UTRA operation..... | 49 | +| 6.3.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 50 | +| 6.3.4 | Total power dynamic range..... | 50 | +| 6.3.4.1 | General..... | 50 | +| 6.3.4.2 | Minimum requirement for MSR operation..... | 50 | +| 6.3.4.3 | Minimum requirement for single RAT UTRA operation..... | 50 | +| 6.3.4.4 | Minimum requirement for single RAT E-UTRA operation..... | 50 | +| 6.3.5 | IPDL time mask..... | 50 | +| 6.3.5.1 | General..... | 50 | +| 6.3.5.2 | Minimum requirement for MSR operation..... | 51 | +| 6.3.5.3 | Minimum requirement for single RAT UTRA operation..... | 51 | +| 6.3.5.4 | Minimum requirement for single RAT E-UTRA operation..... | 51 | +| 6.3.6 | RE Power control dynamic range..... | 51 | +| 6.3.6.1 | General..... | 51 | +| 6.3.6.2 | Minimum requirement for MSR operation..... | 51 | +| 6.3.6.3 | Minimum requirement for single RAT UTRA operation..... | 51 | +| 6.3.6.4 | Minimum requirement for single RAT E-UTRA operation..... | 51 | +| 6.4 | Transmit ON/OFF power..... | 51 | +| 6.4.1 | General..... | 51 | +| 6.4.2 | Transmitter OFF power..... | 52 | +| 6.4.2.1 | General..... | 52 | +| 6.4.2.2 | Minimum requirement for MSR operation..... | 52 | +| 6.4.2.3 | Minimum requirement for single RAT UTRA operation..... | 52 | +| 6.4.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 52 | +| 6.4.3 | Transmitter transient period..... | 52 | +| 6.4.3.1 | General..... | 52 | +| 6.4.3.2 | Minimum requirement for MSR operation..... | 53 | +| 6.4.3.3 | Minimum requirement for single RAT UTRA operation..... | 53 | +| 6.4.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 53 | +| 6.5 | Transmitted signal quality..... | 53 | +| 6.5.1 | General..... | 53 | +| 6.5.2 | Frequency Error..... | 53 | +| 6.5.2.1 | General..... | 53 | +| 6.5.2.2 | Minimum requirement for MSR operation..... | 53 | +| 6.5.2.3 | Minimum requirement for single RAT UTRA operation..... | 53 | +| 6.5.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 54 | +| 6.5.3 | Time alignment error..... | 54 | +| 6.5.3.1 | General..... | 54 | +| 6.5.3.2 | Minimum requirement for MSR operation..... | 54 | +| 6.5.3.3 | Minimum requirement for single RAT UTRA operation..... | 54 | +| 6.5.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 54 | +| 6.5.4 | Modulation quality..... | 55 | +| 6.5.4.1 | General..... | 55 | +| 6.5.4.2 | Minimum requirement for MSR operation..... | 55 | +| 6.5.4.3 | Minimum requirement for single RAT UTRA operation..... | 55 | +| 6.5.4.4 | Minimum requirement for single RAT E-UTRA operation..... | 56 | +| 6.5.5 | Transmit pulse shape filter..... | 56 | +| 6.5.5.1 | General..... | 56 | +| 6.5.5.2 | Void..... | 56 | +| 6.5.5.3 | Void..... | 56 | + +| | | | +|-------------|---------------------------------------------------------------------|----| +| 6.5.5.4 | Void..... | 56 | +| 6.6 | Unwanted Emissions..... | 56 | +| 6.6.1 | General..... | 56 | +| 6.6.2 | Occupied bandwidth..... | 57 | +| 6.6.2.1 | General..... | 57 | +| 6.6.2.2 | Minimum requirement for MSR operation..... | 57 | +| 6.6.2.3 | Minimum requirement for single RAT UTRA operation..... | 57 | +| 6.6.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 57 | +| 6.6.3 | Adjacent Channel Leakage power Ratio..... | 57 | +| 6.6.3.1 | General..... | 57 | +| 6.6.3.2 | Minimum requirement for MSR operation..... | 58 | +| 6.6.3.3 | Minimum requirement for single RAT UTRA operation..... | 58 | +| 6.6.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 58 | +| 6.6.4 | Spectrum emission mask..... | 59 | +| 6.6.4.1 | General..... | 59 | +| 6.6.4.2 | Minimum requirement for MSR operation..... | 59 | +| 6.6.4.3 | Minimum requirement for single RAT UTRA operation..... | 59 | +| 6.6.4.3.1 | General..... | 59 | +| 6.6.4.3.2 | Basic limits for single RAT UTRA FDD operation..... | 59 | +| 6.6.4.3.3 | Basic limits for single RAT UTRA TDD 1,28Mcps operation..... | 64 | +| 6.6.4.4 | Minimum requirement for single RAT E-UTRA operation..... | 66 | +| 6.6.5 | Operating band unwanted emission..... | 67 | +| 6.6.5.1 | General..... | 67 | +| 6.6.5.2 | Minimum requirement for MSR operation..... | 67 | +| 6.6.5.2.1 | General..... | 67 | +| 6.6.5.2.2 | Basic limits for Band Categories 1 and 3..... | 67 | +| 6.6.5.2.3 | Basic limit for Band Category 2..... | 72 | +| 6.6.5.2.4 | Additional requirements..... | 80 | +| 6.6.5.3 | Minimum requirement for single RAT UTRA operation..... | 80 | +| 6.6.5.4 | Minimum requirement for single RAT E-UTRA operation..... | 80 | +| 6.6.5.4.1 | General..... | 80 | +| 6.6.5.4.2 | Basic limits for Wide Area BS (Category A)..... | 82 | +| 6.6.5.4.3 | Basic limits for Wide Area BS (Category B)..... | 84 | +| 6.6.5.4.3.1 | General..... | 84 | +| 6.6.5.4.3.2 | Category B requirements (Option 1)..... | 84 | +| 6.6.5.4.3.3 | Category B (Option 2)..... | 87 | +| 6.6.5.4.4 | Basic limits for Local Area BS (Category A and B)..... | 89 | +| 6.6.5.4.5 | Basic limits for Medium Range BS (Category A and B)..... | 90 | +| 6.6.5.4.7 | Additional requirements..... | 92 | +| 6.6.6 | Spurious emission..... | 92 | +| 6.6.6.1 | General..... | 92 | +| 6.6.6.2 | Minimum requirement for MSR operation..... | 92 | +| 6.6.6.3 | Minimum requirement for single RAT UTRA operation..... | 93 | +| 6.6.6.4 | Minimum requirement for single RAT E-UTRA operation..... | 93 | +| 6.7 | Transmitter intermodulation..... | 93 | +| 6.7.1 | General..... | 93 | +| 6.7.2 | Minimum requirement for MSR operation..... | 94 | +| 6.7.2.1 | General co-location minimum requirement..... | 94 | +| 6.7.2.2 | Additional co-location minimum requirement (BC1 and BC2)..... | 95 | +| 6.7.2.3 | Additional co-location minimum requirement (BC3)..... | 95 | +| 6.7.2.4 | Additional co-location minimum requirements..... | 96 | +| 6.7.2.5 | Intra-system minimum requirement..... | 96 | +| 6.7.3 | Minimum requirement for single RAT UTRA operation..... | 96 | +| 6.7.3.1 | General co-location minimum requirement for FDD UTRA..... | 96 | +| 6.7.3.2 | General co-location minimum requirement for 1,28 Mcps TDD UTRA..... | 97 | +| 6.7.3.3 | Intra-system minimum requirement..... | 98 | +| 6.7.4 | Minimum requirement for single RAT E-UTRA operation..... | 98 | +| 6.7.4.1 | General co-location minimum requirement..... | 98 | +| 6.7.4.2 | Void..... | 99 | +| 6.7.4.3 | Intra-system minimum requirement..... | 99 | + +| | | | +|---------|------------------------------------------------------------------------------|-----| +| 7 | Conducted receiver characteristics..... | 100 | +| 7.1 | General..... | 100 | +| 7.2 | Reference sensitivity level..... | 100 | +| 7.2.1 | General..... | 100 | +| 7.2.2 | Minimum requirement for MSR operation..... | 100 | +| 7.2.3 | Minimum requirement for single RAT UTRA operation..... | 101 | +| 7.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 101 | +| 7.3 | Dynamic range..... | 101 | +| 7.3.1 | General..... | 101 | +| 7.3.2 | Minimum requirement for MSR operation..... | 101 | +| 7.3.3 | Minimum requirement for single RAT UTRA operation..... | 101 | +| 7.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 102 | +| 7.4 | Adjacent channel selectivity, general blocking, and narrowband blocking..... | 102 | +| 7.4.1 | General..... | 102 | +| 7.4.2 | Minimum requirement for MSR operation..... | 102 | +| 7.4.2.1 | General minimum requirement..... | 102 | +| 7.4.2.2 | General narrowband blocking minimum requirement..... | 103 | +| 7.4.2.3 | Additional BC3 blocking minimum requirement..... | 104 | +| 7.4.3 | Minimum requirement for single RAT UTRA operation..... | 105 | +| 7.4.4 | Minimum requirement for single RAT E-UTRA operation..... | 105 | +| 7.5 | Blocking..... | 105 | +| 7.5.1 | General..... | 105 | +| 7.5.2 | Minimum requirement for MSR operation..... | 106 | +| 7.5.2.1 | General minimum requirement..... | 106 | +| 7.5.2.2 | Co-location minimum requirement..... | 106 | +| 7.5.3 | Minimum requirement for single RAT UTRA operation..... | 111 | +| 7.5.3.1 | General minimum requirement..... | 111 | +| 7.5.3.2 | Co-location minimum requirement..... | 111 | +| 7.5.4 | Minimum requirement for single RAT E-UTRA operation..... | 112 | +| 7.5.4.1 | General minimum requirement..... | 112 | +| 7.5.4.2 | Co-location minimum requirement..... | 116 | +| 7.6 | Receiver spurious emissions..... | 116 | +| 7.6.1 | General..... | 116 | +| 7.6.2 | Minimum requirement for MSR operation..... | 117 | +| 7.6.2.1 | General minimum requirement..... | 117 | +| 7.6.3 | Minimum requirement for single RAT UTRA operation..... | 117 | +| 7.6.4 | Minimum requirement for single RAT E-UTRA operation..... | 118 | +| 7.7 | Receiver intermodulation..... | 118 | +| 7.7.1 | General..... | 118 | +| 7.7.2 | Minimum requirement for MSR operation..... | 118 | +| 7.7.2.1 | General intermodulation minimum requirement..... | 118 | +| 7.7.2.2 | General narrowband intermodulation minimum requirement..... | 120 | +| 7.7.3 | Minimum requirement for single RAT UTRA operation..... | 124 | +| 7.7.4 | Minimum requirement for single RAT E- UTRA operation..... | 124 | +| 7.8 | In-channel selectivity..... | 124 | +| 7.8.1 | General..... | 124 | +| 7.8.2 | Minimum requirement for MSR operation..... | 124 | +| 7.8.3 | Minimum requirement for single RAT UTRA operation..... | 124 | +| 7.8.4 | Minimum requirement for single RAT E-UTRA operation..... | 125 | +| 8 | Performance requirements..... | 125 | +| 8.1 | General..... | 125 | +| 8.1.1 | UTRA operation..... | 125 | +| 8.1.2 | E-UTRA operation..... | 126 | +| 8.2 | Minimum requirements for MSR operation..... | 127 | +| 8.3 | Minimum requirements for UTRA operation..... | 127 | +| 8.4 | Minimum requirements for E-UTRA operation..... | 127 | +| 9 | Radiated transmitter characteristics..... | 127 | +| 9.1 | General..... | 127 | +| 9.2 | Radiated transmit power..... | 128 | +| 9.2.1 | General..... | 128 | + +| | | | +|-----------|----------------------------------------------------------|-----| +| 9.2.2 | Minimum requirement for MSR operation..... | 128 | +| 9.2.3 | Minimum requirement for single RAT UTRA operation..... | 128 | +| 9.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 128 | +| 9.3 | OTA Base Station output power..... | 129 | +| 9.3.1 | General..... | 129 | +| 9.3.2 | OTA Maximum output power..... | 129 | +| 9.3.2.1 | General..... | 129 | +| 9.3.2.2 | Minimum requirement for MSR operation..... | 129 | +| 9.3.2.2.1 | General..... | 129 | +| 9.3.2.2.2 | Additional requirements (regional)..... | 129 | +| 9.3.2.3 | Minimum requirement for single RAT UTRA operation..... | 129 | +| 9.3.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 129 | +| 9.3.2.4.1 | General..... | 129 | +| 9.3.2.4.2 | Additional requirements (regional)..... | 130 | +| 9.3.3 | OTA E-UTRA DL RS power..... | 130 | +| 9.3.3.1 | General..... | 130 | +| 9.3.3.2 | Minimum requirement for MSR operation..... | 130 | +| 9.3.3.3 | Minimum requirement for single RAT UTRA operation..... | 130 | +| 9.3.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 130 | +| 9.4 | OTA Output power dynamics..... | 130 | +| 9.4.1 | General..... | 130 | +| 9.4.2 | OTA UTRA Inner loop power control in the downlink..... | 130 | +| 9.4.2.1 | General..... | 130 | +| 9.4.2.2 | Minimum requirement for MSR operation..... | 130 | +| 9.4.2.3 | Minimum requirement for single RAT UTRA operation..... | 131 | +| 9.4.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 131 | +| 9.4.3 | OTA Power control dynamic range..... | 131 | +| 9.4.3.1 | General..... | 131 | +| 9.4.3.2 | Minimum requirement for MSR operation..... | 131 | +| 9.4.3.3 | Minimum requirement for single RAT UTRA operation..... | 131 | +| 9.4.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 132 | +| 9.4.4 | OTA Total power dynamic range..... | 132 | +| 9.4.4.1 | General..... | 132 | +| 9.4.4.2 | Minimum requirement for MSR operation..... | 132 | +| 9.4.4.3 | Minimum requirement for single RAT UTRA operation..... | 132 | +| 9.4.4.4 | Minimum requirement for single RAT E-UTRA operation..... | 132 | +| 9.4.5 | OTA IPDL time mask..... | 133 | +| 9.4.5.1 | General..... | 133 | +| 9.4.5.2 | Minimum requirement for MSR operation..... | 133 | +| 9.4.5.3 | Minimum requirement for single RAT UTRA operation..... | 133 | +| 9.4.5.4 | Minimum requirement for single RAT E-UTRA operation..... | 133 | +| 9.4.6 | OTA RE Power control dynamic range..... | 133 | +| 9.4.6.1 | General..... | 133 | +| 9.4.6.2 | Minimum requirement for MSR operation..... | 134 | +| 9.4.6.3 | Minimum requirement for single RAT UTRA operation..... | 134 | +| 9.4.6.4 | Minimum requirement for single RAT E-UTRA operation..... | 134 | +| 9.5 | OTA Transmit ON/OFF power..... | 134 | +| 9.5.1 | General..... | 134 | +| 9.5.2 | OTA Transmitter OFF power..... | 134 | +| 9.5.2.1 | General..... | 134 | +| 9.5.2.2 | Minimum requirement for MSR operation..... | 135 | +| 9.5.2.3 | Minimum requirement for single RAT UTRA operation..... | 135 | +| 9.5.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 135 | +| 9.5.3 | OTA Transmitter transient period..... | 135 | +| 9.5.3.1 | General..... | 135 | +| 9.5.3.2 | Minimum requirement for MSR operation..... | 135 | +| 9.5.3.3 | Minimum requirement for single RAT UTRA operation..... | 136 | +| 9.5.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 136 | +| 9.6 | OTA Transmitted signal quality..... | 136 | +| 9.6.1 | General..... | 136 | +| 9.6.2 | OTA Frequency Error..... | 136 | + +| | | | +|--------------|-------------------------------------------------------------------|-----| +| 9.6.2.1 | General..... | 136 | +| 9.6.2.2 | Minimum requirement for MSR operation..... | 136 | +| 9.6.2.3 | Minimum requirement for single RAT UTRA operation..... | 136 | +| 9.6.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 136 | +| 9.6.3 | OTA Time alignment error..... | 137 | +| 9.6.3.1 | General..... | 137 | +| 9.6.3.2 | Minimum requirement for MSR operation..... | 137 | +| 9.6.3.3 | Minimum requirement for single RAT UTRA operation..... | 137 | +| 9.6.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 137 | +| 9.6.4 | OTA Modulation quality..... | 138 | +| 9.6.4.1 | General..... | 138 | +| 9.6.4.2 | Minimum requirement for MSR operation..... | 138 | +| 9.6.4.3 | Minimum requirement for single RAT UTRA operation..... | 138 | +| 9.6.4.4 | Minimum requirement for single RAT E-UTRA operation..... | 138 | +| 9.6.5 | OTA Transmit pulse shape filter..... | 138 | +| 9.6.5.1 | General..... | 138 | +| 9.7 | OTA Unwanted Emissions..... | 139 | +| 9.7.1 | General..... | 139 | +| 9.7.2 | OTA occupied bandwidth..... | 139 | +| 9.7.2.1 | General..... | 139 | +| 9.7.2.2 | Minimum requirement for MSR operation..... | 140 | +| 9.7.2.3 | Minimum requirement for single RAT UTRA operation..... | 140 | +| 9.7.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 140 | +| 9.7.3 | OTA Adjacent Channel Leakage power Ratio..... | 140 | +| 9.7.3.1 | General..... | 140 | +| 9.7.3.2 | Minimum requirement for MSR operation..... | 140 | +| 9.7.3.3 | Minimum requirement for single RAT UTRA operation..... | 141 | +| 9.7.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 141 | +| 9.7.4 | OTA Spectrum emission mask..... | 142 | +| 9.7.4.1 | General..... | 142 | +| 9.7.4.2 | Minimum requirement for MSR operation..... | 142 | +| 9.7.4.3 | Minimum requirement for single RAT UTRA operation..... | 142 | +| 9.7.4.3.1 | General..... | 142 | +| 9.7.4.3.2 | Minimum requirements for single RAT UTRA FDD operation..... | 142 | +| 9.7.4.4 | Minimum requirement for single RAT E-UTRA operation..... | 148 | +| 9.7.5 | OTA Operating band unwanted emission..... | 148 | +| 9.7.5.1 | General..... | 148 | +| 9.7.5.2 | Minimum requirement for MSR operation..... | 149 | +| 9.7.5.2.1 | General..... | 149 | +| 9.7.5.2.2 | Minimum requirements for Band Categories 1 and 3..... | 149 | +| 9.7.5.2.3 | Minimum requirement for Band Category 2..... | 154 | +| 9.7.5.2.4 | Additional requirements..... | 160 | +| 9.7.5.2.4.1 | Limits in FCC Title 47..... | 160 | +| 9.7.5.2.4.2 | Unsynchronized operation for BC3..... | 160 | +| 9.7.5.2.4.3 | Protection of DTT..... | 161 | +| 9.7.5.2.4.4 | Void..... | 161 | +| 9.7.5.2.4.5 | Co-existence with RNSS/GPS services in North America..... | 161 | +| 9.7.5.2.4.6 | Void..... | 162 | +| 9.7.5.2.4.7 | Additional band 32, 50, 51, 74, 75 and 76 unwanted emissions..... | 162 | +| 9.7.5.2.4.8 | Additional requirements for band 45..... | 163 | +| 9.7.5.2.4.9 | Additional requirements for band 48..... | 163 | +| 9.7.5.2.4.10 | Additional requirements for band 53..... | 164 | +| 9.7.5.3 | Minimum requirement for single RAT UTRA operation..... | 164 | +| 9.7.5.4 | Minimum requirement for single RAT E-UTRA operation..... | 164 | +| 9.7.5.4.1 | General..... | 164 | +| 9.7.5.4.2 | Minimum requirements for Wide Area BS (Category A)..... | 164 | +| 9.7.5.4.3 | Minimum requirements for Wide Area BS (Category B)..... | 167 | +| 9.7.5.4.3.1 | General..... | 167 | +| 9.7.5.4.3.2 | Category B requirements (Option 1)..... | 167 | +| 9.7.5.4.3.3 | Category B requirements (Option 2)..... | 170 | +| 9.7.5.4.4 | Minimum requirements for Local Area BS (Category A and B)..... | 172 | + +| | | | +|-------------|--------------------------------------------------------------------------|-----| +| 9.7.5.4.5 | Minimum requirements for Medium Range BS (Category A and B)..... | 173 | +| 9.7.5.4.6 | Additional requirements..... | 176 | +| 9.7.5.4.6.1 | Additional operating band unwanted emission limits for E-UTRA bands..... | 176 | +| 9.7.5.4.6.2 | Protection of DTT..... | 177 | +| 9.7.5.4.6.3 | Co-existence with RNSS/GPS services in North America..... | 177 | +| 9.7.5.4.6.4 | Void..... | 178 | +| 9.7.5.4.6.5 | Additional band 32, 50, 51, 74, 75 and 76 unwanted emissions..... | 178 | +| 9.7.5.4.6.6 | Additional requirements for band 45..... | 179 | +| 9.7.5.4.6.7 | Additional requirements for band 48..... | 180 | +| 9.7.6 | OTA Spurious emission..... | 180 | +| 9.7.6.1 | General..... | 180 | +| 9.7.6.2 | MSR operation..... | 181 | +| 9.7.6.2.1 | Minimum requirement for MSR operation..... | 181 | +| 9.7.6.2.1.1 | Minimum requirement (Category A)..... | 181 | +| 9.7.6.2.1.2 | Minimum requirement (Category B)..... | 181 | +| 9.7.6.2.1.3 | (void)..... | 181 | +| 9.7.6.2.2 | Protection of the BS receiver of own or different BS..... | 181 | +| 9.7.6.2.3 | Additional spurious emissions requirements..... | 182 | +| 9.7.6.2.4 | Co-location with other base stations..... | 182 | +| 9.7.6.3 | Minimum requirement for single RAT UTRA operation..... | 182 | +| 9.7.6.3.1 | Mandatory Requirements..... | 182 | +| 9.7.6.3.1.1 | Minimum requirement (Category A)..... | 182 | +| 9.7.6.3.1.2 | Minimum requirement (Category B)..... | 182 | +| 9.7.6.3.2 | Protection of the BS receiver of own or different BS..... | 183 | +| 9.7.6.3.3 | Additional spurious emissions requirements..... | 184 | +| 9.7.6.3.4 | Co-location with other base stations..... | 192 | +| 9.7.6.3.4.1 | General..... | 192 | +| 9.7.6.3.4.2 | Minimum Requirement..... | 192 | +| 9.7.6.4 | Minimum requirement for single RAT E-UTRA operation..... | 199 | +| 9.7.6.4.1 | Mandatory Requirements..... | 199 | +| 9.7.6.4.1.1 | Minimum requirement (Category A)..... | 199 | +| 9.7.6.4.1.2 | Minimum Requirement (Category B)..... | 199 | +| 9.7.6.4.2 | Protection of the BS receiver of own or different BS..... | 199 | +| 9.7.6.4.3 | Additional spurious emissions requirements..... | 199 | +| 9.7.6.4.3.1 | General..... | 199 | +| 9.7.6.4.3.2 | Minimum Requirement..... | 200 | +| 9.7.6.4.4 | Co-location with other base stations..... | 211 | +| 9.7.6.4.4.1 | General..... | 211 | +| 9.7.6.4.4.2 | Minimum Requirement..... | 212 | +| 9.8 | OTA Transmitter intermodulation..... | 219 | +| 9.8.1 | General..... | 219 | +| 9.8.2 | Minimum requirement for MSR operation..... | 219 | +| 9.8.2.1 | General minimum requirement..... | 219 | +| 9.8.2.2 | Additional minimum requirement (BC1 and BC2)..... | 220 | +| 9.8.2.3 | Additional minimum requirement (BC3)..... | 221 | +| 9.8.2.4 | Additional minimum requirements..... | 221 | +| 9.8.3 | Minimum requirement for single RAT UTRA operation..... | 221 | +| 9.8.3.1 | General minimum requirement for FDD UTRA..... | 221 | +| 9.8.4 | Minimum requirement for single RAT E-UTRA operation..... | 222 | +| 9.8.4.1 | General minimum requirement..... | 222 | +| 9.8.4.2 | Void..... | 223 | +| 10 | Radiated receiver characteristics..... | 223 | +| 10.1 | General..... | 223 | +| 10.2 | OTA sensitivity..... | 224 | +| 10.2.1 | General..... | 224 | +| 10.2.2 | Minimum requirement for MSR operation..... | 224 | +| 10.2.3 | Minimum requirement for single RAT UTRA operation..... | 224 | +| 10.2.4 | Minimum requirement for single RAT E-UTRA operation..... | 225 | +| 10.3 | OTA Reference sensitivity level..... | 225 | +| 10.3.1 | General..... | 225 | +| 10.3.2 | Minimum requirement for MSR operation..... | 225 | + +| | | | +|----------|----------------------------------------------------------------------------------|-----| +| 10.3.3 | Minimum requirement for single RAT UTRA operation..... | 226 | +| 10.3.4 | Minimum requirement for single RAT E-UTRA operation..... | 226 | +| 10.4 | OTA Dynamic range..... | 227 | +| 10.4.1 | General..... | 227 | +| 10.4.2 | Minimum requirement for MSR operation..... | 227 | +| 10.4.3 | Minimum requirement for single RAT UTRA operation..... | 227 | +| 10.4.4 | Minimum requirement for single RAT E-UTRA operation..... | 228 | +| 10.5 | OTA Adjacent channel selectivity, general blocking, and narrowband blocking..... | 230 | +| 10.5.1 | General..... | 230 | +| 10.5.2 | Minimum requirement for MSR operation..... | 231 | +| 10.5.2.1 | General minimum requirement..... | 231 | +| 10.5.2.2 | General narrowband blocking minimum requirement..... | 232 | +| 10.5.2.3 | Additional BC3 blocking minimum requirement..... | 233 | +| 10.5.3 | Minimum requirement for single RAT UTRA operation..... | 234 | +| 10.5.3.1 | General..... | 234 | +| 10.5.3.2 | Minimum requirement..... | 234 | +| 10.5.3.3 | Minimum requirement - Co-location with UTRA-TDD..... | 234 | +| 10.5.4 | Minimum requirement for single RAT E-UTRA operation..... | 235 | +| 10.5.4.1 | General..... | 235 | +| 10.5.4.2 | Minimum requirement..... | 235 | +| 10.6 | OTA Blocking..... | 237 | +| 10.6.1 | General..... | 237 | +| 10.6.2 | Minimum requirement for MSR operation..... | 238 | +| 10.6.2.1 | General minimum requirement..... | 238 | +| 10.6.2.2 | Co-location minimum requirement..... | 238 | +| 10.6.3 | Minimum requirement for single RAT UTRA operation..... | 243 | +| 10.6.3.1 | General minimum requirement..... | 243 | +| 10.6.3.2 | Co-location minimum requirement..... | 244 | +| 10.6.4 | Minimum requirement for single RAT E-UTRA operation..... | 249 | +| 10.6.4.1 | General minimum requirement..... | 249 | +| 10.6.4.2 | Co-location minimum requirement..... | 250 | +| 10.7 | OTA Receiver spurious emissions..... | 255 | +| 10.7.1 | General..... | 255 | +| 10.7.2 | Minimum requirement for MSR operation..... | 255 | +| 10.7.2.1 | General minimum requirement..... | 255 | +| 10.7.3 | Minimum requirement for single RAT UTRA operation..... | 255 | +| 10.7.4 | Minimum requirement for single RAT E-UTRA operation..... | 256 | +| 10.8 | OTA Receiver intermodulation..... | 256 | +| 10.8.1 | General..... | 256 | +| 10.8.2 | Minimum requirement for MSR operation..... | 256 | +| 10.8.2.1 | General intermodulation minimum requirement..... | 256 | +| 10.8.2.2 | General narrowband intermodulation minimum requirement..... | 258 | +| 10.8.3 | Minimum requirement for single RAT UTRA operation..... | 262 | +| 10.8.4 | Minimum requirement for single RAT E- UTRA operation..... | 263 | +| 10.9 | OTA In-channel selectivity..... | 267 | +| 10.9.1 | General..... | 267 | +| 10.9.2 | Minimum requirement for MSR operation..... | 267 | +| 10.9.3 | Minimum requirement for single RAT UTRA operation..... | 268 | +| 10.9.4 | Minimum requirement for single RAT E- UTRA operation..... | 268 | +| 11 | Radiated performance requirements..... | 269 | +| 11.1 | General..... | 269 | +| 11.1.1 | OTA demodulation branches..... | 269 | +| 11.1.2 | UTRA operation..... | 269 | +| 11.1.3 | E-UTRA operation..... | 270 | +| 11.2 | Minimum requirements for MSR operation..... | 271 | +| 11.3 | Minimum requirements for UTRA operation..... | 271 | +| 11.4 | Minimum requirements for E-UTRA operation..... | 271 | + +**Annex A (normative): Environmental requirements for the BS equipment.....272** + +**Annex B (Informative): Calculation of EIRP based on fixed assumption of passive antenna gain.....272** + +B.1 Calculation of EIRP based on fixed assumption of passive antenna gain.....272 + +**Annex C (informative): Change history.....274** + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document establishes 2 sets of minimum requirements and minimum performance requirements; *hybrid requirements set* which specify requirements for a *hybrid AAS BS* with both a conducted and a radiated interface and *OTA requirements set* which specify requirements for an *OTA AAS BS* which has a radiated interface only. + +The *hybrid AAS BS* requirements are specified for E-UTRA AAS Base Station (BS), the FDD mode of UTRA AAS Base Station (BS), the 1,28 Mcps TDD mode of UTRA AAS Base Station (BS) in single RAT and any MSR AAS Base Station (BS) implementation of these RATs (including NR BS type 1-H MSR configurations). + +The *OTA AAS BS* requirements are specified for E-UTRA AAS Base Station (BS), the FDD mode of UTRA AAS Base Station (BS), in single RAT and any MSR AAS Base Station (BS) implementation of these RATs (including NR BS type 1-O MSR configurations). + +NOTE 1: The present document does not establish minimum RF characteristics or minimum performance requirements for Narrow-Band Internet of Things (NB-IoT) in band, NB-IoT guard band, or standalone NB-IoT operation, for AAS BS in *single RAT E-UTRA operation* or in *MSR operation* using E-UTRA. + +NOTE 2: The present document does not establish minimum RF characteristics for MBMS for AAS BS in *single RAT E-UTRA operation*. + +# 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.104: "Base Station (BS) radio transmission and reception (FDD)". +- [3] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD)". +- [4] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". +- [5] 3GPP TS 37.104: "NR, E-UTRA, UTRA and GSM/EDGE Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception". +- [6] 3GPP TS 25.104 (V16.0.00): "Base Station (BS) radio transmission and reception (FDD) (Release 16)". +- [7] 3GPP TS 25.105 (V16.0.0): "Base Station (BS) radio transmission and reception (TDD) (Release 16)". +- [8] 3GPP TS 36.104 (V16.7.0): "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception (Release 16)". +- [9] 3GPP TS 37.104 (V16.8.0): "E-UTRA, UTRA and GSM/EDGE Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception (Release 16)". +- [10] 3GPP TS 25.142 (V16.0.0): "Base Station (BS) conformance testing (TDD) (Release 16)". +- [11] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". + +- [12] 3GPP TS 25.942: "Radio Frequency (RF) system scenarios". +- [13] Void +- [14] Recommendation ITU-R SM.329-10: "Unwanted emissions in the spurious domain". +- [15] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission. +- [16] 3GPP TS 25.331 (V14.3.0): "Radio Resource Control (RRC); Protocol specification (Release 14)". +- [17] Recommendation ITU-R SM.328-11: "Spectra and bandwidth of emissions". +- [18] FCC publication number 662911: "Emissions Testing of Transmitters with Multiple Outputs in the Same Band". +- [19] 3GPP TS 37.141: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing". +- [20] 3GPP TS 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing". +- [21] IEC 60721-3-3: "Classification of environmental conditions - Part 3-3: Classification of groups of environmental parameters and their severities - Stationary use at weather protected locations". +- [22] IEC 60721-3-4: "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations". +- [23] ETSI EN 300 019-1-3: "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-3: Classification of environmental conditions; Stationary use at weather protected locations". +- [24] ETSI EN 300 019-1-4: "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-4: Classification of environmental conditions; Stationary use at non-weather protected locations". +- [25] CEPT ECC Decision (13)03, "The harmonised use of the frequency band 1452-1492 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL)". +- [26] 3GPP TS 45.004: "Digital cellular telecommunications system (Phase 2+); Modulation". +- [27] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception" +- [28] 3GPP TS 38.104 (V15.1.0): "NR; Base Station (BS) radio transmission and reception (Release 15)" +- [29] 3GPP TS 37.145-1: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 1: Conducted conformance testing" +- [30] 3GPP TS 37.145-2: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: radiated conformance testing" +- [31] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation" + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +NOTE: Multi-word definitions are treated as linguistic expressions and printed in italic font throughout this requirement specification. Linguistic expressions may not be split and are to be printed in their entirety. + +**AAS BS receiver:** composite receiver function of an AAS BS receiving in an *uplink operating band* + +**active antenna system base station:** base station system which combines an antenna array with a transceiver unit array and a *radio distribution network* + +**active transmitter unit:** transmitter unit which is ON, and has the ability to send modulated data streams that are parallel and distinct to those sent from other transmitter units to one or more *TAB connectors* at the *transceiver array boundary* + +**band category:** group of *operating bands* for which the same MSR scenarios apply + +**Base Station RF Bandwidth:** bandwidth in which a base station transmits and/or receives single or multiple carrier(s) and/or RATs simultaneously within a supported *operating band* + +NOTE: In single carrier operation, the *Base Station RF Bandwidth* is equal to the *channel bandwidth*. + +**Base Station RF Bandwidth edge:** frequency of one of the edges of the *Base Station RF Bandwidth* + +**basic limit:** emissions limit taken from the *non-AAS BS* specifications that is converted into a per *TAB connector TX min cell group* AAS BS emissions limit, or into a per *TAB connector RX min cell group* AAS BS emissions limit by scaling, depending on the context + +**beam:** main lobe of a radiation pattern from an AAS BS + +NOTE: For certain AAS BS antenna array, there may be more than one beam. + +**beam centre direction:** direction equal to the geometric centre of the half-power EIRP contour of the beam + +**beam direction pair:** data set consisting of the *beam centre direction* and the related *beam peak direction* + +**beam peak direction:** direction where the maximum EIRP is supposed to be found + +**beamwidth:** angles describing the major and minor axes of an ellipsoid closest fit to an essentially elliptic half-power EIRP contour of the beam + +**carrier:** modulated waveform conveying the E-UTRA or UTRA physical channels + +**carrier aggregation:** aggregation of two or more NR or E-UTRA component carriers in order to support wider *transmission bandwidths* + +**channel bandwidth:** RF bandwidth supporting a single RF carrier with the *transmission bandwidth* configured in the uplink or downlink of a cell + +NOTE 1: The *channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE 2: For UTRA FDD, the *channel bandwidth* is the nominal channel spacing specified in 3GPP TS 25.104 [2]. For UTRA TDD 1,28 Mcps, the *channel bandwidth* is the nominal channel spacing specified in 3GPP TS 25.105 [3]. + +NOTE 3: For E-UTRA, the *channel bandwidths* are specified in 3GPP TS 36.104 [4]. Standalone NB-IoT *channel bandwidths* specified in 3GPP TS 36.104 [4] are not applicable to AAS BS. + +NOTE 4: In TS 38.104 [28] for NR, *channel bandwidths* are referred to as BS channel bandwidths, since for NR BS and UE channel bandwidths may differ. + +**code domain power:** part of the mean power which correlates with a particular (OVSF) code channel in a UTRA signal + +NOTE: The sum of all powers in the code domain equals the mean power in a bandwidth of $(1+\alpha)$ times the chip rate of the radio access mode. + +**co-location reference antenna:** a passive antenna used as reference for base station to base station co-location requirements. + +**demodulation branch:** single input of the *AAS BS receiver* to the demodulation algorithms. + +NOTE 1: For UTRA *non-AAS BS* a *demodulation branch* is referred to as a receive diversity branch or an UL MIMO branch. For E-UTRA *non-AAS BS* a *demodulation branch* is referred to as an RX antenna in the performance requirement tables. + +NOTE 2: The term "RX antenna" in chapter 8 (i.e. Performance requirements) of the E-UTRA specification 3GPP TS 36.104 [4] does not refer to physical receiver antennas. + +**downlink operating band:** part of the (FDD) *operating band* designated for downlink transmission + +**enhanced performance requirements type A:** This defines performance requirements assuming baseline receiver as demodulation reference signal based linear minimum mean square error interference rejection combining + +**enhanced performance requirements type B:** This defines performance requirements assuming baseline receiver as code word level interference cancellation for intra-cell inter-user interference plus demodulation reference signal based linear minimum mean square error interference rejection combining for inter-cell interference + +**equivalent isotropic radiated power:** equivalent power radiated from an isotropic directivity device producing the same field intensity at a point of observation as the field intensity radiated in the direction of the same point of observation by the discussed device + +NOTE: Isotropic directivity is equal in all directions (i.e. 0 dBi). + +**equivalent isotropic sensitivity:** sensitivity for an isotropic directivity device equivalent to the sensitivity of the discussed device exposed to an incoming wave from a defined AoA + +NOTE 1: The sensitivity is the minimum received power level at which a RAT specific requirement is met. + +NOTE 2: Isotropic directivity is equal in all directions (i.e. 0 dBi). + +**hybrid AAS BS:** AAS BS which has both a conducted RF interface and a radiated RF interface in the far field and conforms to a *hybrid requirements set* + +**hybrid requirements set:** complete set of requirements applied to a *hybrid AAS BS* with both conducted and radiated requirements + +**inter-band gap:** frequency gap between two supported consecutive operating bands + +**Inter RF Bandwidth gap:** frequency gap between two consecutive *Base Station RF Bandwidths* that are placed within two supported *operating bands* + +**maximum carrier output power per TAB connector:** mean power level measured on a particular carrier at the *TAB connector(s)*, during the *transmitter ON period* in a specified reference condition + +**maximum throughput:** maximum achievable throughput for a reference measurement channel + +**minSENS RoAoA:** the *reference RoAoA* associated with the OSDD with the lowest declared EIS value. + +**MSR operation:** operation of AAS BS declared to be MSR in particular *operating band(s)* (including any of UTRA, E-UTRA and/or NR operation as SR or multi-RAT based on 37.104) + +**multi-band requirements:** requirements applying per one single *operating band* with exclusion bands or other multi-band provisions as defined for each requirement + +**multi-band RIB:** operating band specific RIB associated with a transmitter or receiver that is characterized by the ability to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different operating band than the other carrier(s) and where this different operating band is not a sub-band or superseding-band of another supported operating band in which the same RAT is operated. + +**multi-band TAB connector:** *TAB connector* associated with a transmitter or receiver that is characterized by the ability to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different operating band than the other carrier(s) and where this different operating band is not a sub-band or superseding-band of another supported operating band in which the same RAT is operated. + +**non-AAS BS:** BS conforming to one of the specifications in 3GPP TS 25.104 [2], 3GPP TS 25.105 [3], 3GPP TS 36.104 [4] or 3GPP TS 37.104 [5] + +NOTE: For AAS BS in *single RAT E-UTRA operation* or in *MSR operation* using E-UTRA, the NB-IoT operation (including in-band, guard band and standalone operation) is excluded from the consideration in the performance comparison among AAS BS and *non-AAS BS* in this specification. + +**non-contiguous spectrum:** spectrum consisting of two or more *sub-blocks* separated by *sub-block gap(s)* + +**OTA AAS BS:** AAS BS which has $\geq 8$ *transceiver units* for E-UTRA or MSR and $\geq 4$ *transceiver units* for UTRA per cell and has a radiated RF interface only and conforms to the *OTA requirements set*. + +**OTA coverage range:** a common range of directions within which TX OTA requirements that are neither specified in the *OTA peak directions sets* nor as TRP requirement are intended to be met + +**OTA peak directions set:** set(s) of *beam peak directions* within which certain TX OTA requirements are intended to be met, where all *OTA peak directions set(s)* are subsets of the *OTA coverage range* + +NOTE 1: The *beam peak directions* are related to a corresponding contiguous range or discrete list of *beam centre directions* by the *beam direction pairs* included in the set. + +NOTE 2: *OTA peak directions set* definition (applicable to multiple *directional requirements*) is replacing the Rel-13/14 *EIRP accuracy directions set* definition (which was applicable to EIRP requirement only). + +**OTA REFSSENS RoAoA:** Is the RoAoA determined by the contour defined by the points at which the achieved EIS is 3dB higher than the achieved EIS in the reference direction assuming that for any AoA, the receiver gain is optimized for that AoA. + +NOTE: This contour will be related to the average element/sub-array radiation pattern 3dB beam width. + +**OTA requirements set:** complete set of OTA requirements applied to an *OTA AAS BS*. + +**OTA sensitivity directions declaration:** set of manufacturer declarations comprising at least one set of declared minimum EIS values (with related RAT and *channel bandwidth*), and related directions over which the EIS applies + +NOTE: All the directions apply to all the EIS values in an OSDD. + +**output power at a TAB connector:** mean power delivered to a load with resistance equal to the nominal load impedance of the *TAB connector* + +**polarization match:** condition that exists when a plane wave, incident upon an antenna from a given direction, has a polarization that is the same as the receiving polarization of the antenna in that direction + +**radiated interface boundary:** operating band specific radiated requirements reference where the radiated requirements apply. + +NOTE: For requirements based on EIRP/EIS, the *radiated interface boundary* is associated to the far-field region. + +**Radio Bandwidth:** frequency difference between the upper edge of the highest used carrier and the lower edge of the lowest used carrier + +**radio distribution network:** linear passive network which distributes the RF power generated by the transceiver unit array to the antenna array, and/or distributes the radio signals collected by the antenna array to the transceiver unit array + +NOTE: In the case when the active transceiver units are physically integrated with the array elements of the antenna array, the *radio distribution network* is a one-to-one mapping. + +**rated beam EIRP:** EIRP that is declared as being achieved in the *beam peak direction* associated with a particular *beam direction pair* + +**rated carrier output power per TAB connector:** mean power level associated with a particular carrier the manufacturer has declared to be available at the *TAB connector*, during the *transmitter ON period* in a specified reference condition + +**rated total output power per TAB connector:** mean power level associated with a particular *operating band* the manufacturer has declared to be available at the *TAB connector*, during the *transmitter ON period* in a specified reference condition + +**receive period:** time during which the AAS BS is receiving data sub-frames (or UpPTS in case of E-UTRA frame Type2) on a (TDD) carrier + +**receiver target:** AoA in which reception is performed by AAS BS + +**receiver target redirection range:** union of all the *sensitivity RoAoA* achievable through redirecting the *receiver target* related to particular OSDD + +**receiver target reference direction:** direction inside the *OTA sensitivity directions declaration* declared by the manufacturer for conformance testing. For an OSDD without *receiver target redirection range*, this is a direction inside the *sensitivity RoAoA* + +**reference beam direction pair:** declared *beam direction pair*, including reference *beam centre direction* and reference *beam peak direction* where the reference *beam peak direction* is the direction for the intended maximum EIRP within the *OTA peak directions set* + +**reference RoAoA:** the *sensitivity RoAoA* associated with the *receiver target reference direction* for each OSDD. + +**sensitivity RoAoA:** RoAoA within the *OTA sensitivity directions declaration*, within which the declared EIS(s) of an OSDD is intended to be achieved at any instance of time for a specific AAS BS direction setting + +**single band requirements:** requirements applying per one single *operating band* without exclusion bands or other multi-band provisions + +**single band RIB:** operating band specific RIB supporting operation either in a single *operating band* only, or in multiple *operating bands* but does not meet the conditions for a *multi-band connector*. + +**single band TAB connector:** *TAB connector* supporting operation either in a single *operating band* only, or in multiple *operating bands* but does not meet the conditions for a *multi-band RIB*. + +**single direction requirement:** AAS BS requirement which is applied in a specific direction within the *OTA coverage range* for the Tx and when the AoA of the incident wave of a received signal is within the OTA REFSSENS RoAoA or the minSENS RoAoA as appropriate for the receiver. + +**single RAT E-UTRA operation:** operation of AAS BS declared to be single RAT E-UTRA in the *operating band* + +NOTE: *Single RAT E-UTRA operation* does not cover in-band NB-IoT, nor guardband NB-IoT operation. + +**single RAT UTRA operation:** operation of AAS BS declared to be single RAT UTRA in the *operating band* + +**sTTI:** A transmission time interval (TTI) of either one slot or one subslot as defined in TS 36.211 [31] on either uplink or downlink. + +**sub-block:** one contiguous allocated block of spectrum for use by the same Base Station + +NOTE: There may be multiple instances of *sub-blocks* within a *Base Station RF Bandwidth*. + +**sub-block gap:** frequency gap between two consecutive *sub-blocks* within a *Base Station RF Bandwidth*, where the RF requirements in the gap are based on co-existence for uncoordinated operation + +**Synchronized operation:** Operation of TDD in two different systems, where no simultaneous uplink and downlink occur. + +**TAB connector:** *transceiver array boundary connector* + +**TAB connector RX min cell group:** *operating band* specific declared group of *TAB connectors* to which RX requirements are applied. + +NOTE: Within this definition, the group corresponds to the group of *TAB connectors* which are responsible for receiving a cell when the AAS BS setting corresponding to the declared minimum number of cells with transmission on all *TAB connectors* supporting an *operating band*, but its existence is not limited to that condition. + +**TAB connector TX min cell group:** *operating band* specific declared group of *TAB connectors* to which TX requirements are applied. + +NOTE: Within this definition, the group corresponds to the group of *TAB connectors* which are responsible for transmitting a cell when the AAS BS setting corresponding to the declared minimum number of cells with transmission on all *TAB connectors* supporting an *operating band*, but its existence is not limited to that condition. + +**throughput:** number of payload bits successfully received per second for a reference measurement channel in a specified reference condition + +**total radiated power:** is the total power radiated by the antenna. + +NOTE 1: The *total radiated power* is the power radiating in all direction for two orthogonal polarizations. + +NOTE 2: *total radiated power* is defined in both the near-field region and the far-field region. + +**transceiver array boundary:** conducted interface between the transceiver unit array and the composite antenna + +**transmission bandwidth:** RF bandwidth of an instantaneous E-UTRA transmission from a UE or BS, measured in resource Block units + +**transmitter OFF period:** time period during which the transmitter is scheduled not to transmit + +NOTE: For AAS BS, this definition applies per *TAB connector* and *operating band*. + +**transmitter ON period:** time period during which the transmitter is transmitting data and/or reference symbols + +NOTE: For AAS BS, this definition applies per *TAB connector* and *operating band*. + +**transmitter transient period:** time period during which the transmitter unit belonging to the transceiver unit array is changing from the OFF period to the ON period or vice versa + +NOTE: For AAS BS, this definition applies per *TAB connector* and *operating band*. + +**Unsynchronized operation:** Operation of TDD in two different systems, where the conditions for synchronized operation are not met. + +**uplink operating band:** part of the (FDD) *operating band* designated for uplink transmission + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------------| +| $BeW_{\theta,REFSENS}$ | The beamwidth equivalent to the OTA REFSENS RoAoA in the $\theta$ -axis in degrees. | +| $BeW_{\phi,REFSENS}$ | The beamwidth equivalent to the OTA REFSENS RoAoA in the $\phi$ -axis in degrees. | +| $\Delta f_{OBUE}$ | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| $\Delta f_{OOB}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $\Delta_{minSENS}$ | Difference between conducted reference sensitivity and $EIS_{minSENS}$ | +| $\Delta_{OTAREFSENS}$ | Difference between conducted reference sensitivity and OTA REFSENS | +| $EIS_{minSENS}$ | The EIS declared for the $minSENS$ RoAoA | +| $F_{DL\_low}$ | The lowest frequency of the downlink operating band | +| $F_{DL\_high}$ | The highest frequency of the downlink operating band | + +| | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $N_{\text{cells}}$ | The declared number corresponding to the minimum number of cells that can be transmitted by an AAS BS in a particular band with transmission on all TAB connectors supporting the operating band. | +| $N_{\text{RXU,active}}$ | The number of active receiver units. The same as the number of demodulation branches to which compliance is declared for chapter 8 performance requirements. | +| $N_{\text{RXU,counted}}$ | The number of active receiver units that are taken into account for unwanted emission scaling, as calculated in subclause 7.1. | +| $N_{\text{RXU,countedpercell}}$ | The number of active receiver units that are taken into account for unwanted emissions scaling per cell, as calculated in subclause 7.6. The number is defined in subclause 7.1. | +| $N_{\text{TXU,active}}$ | The number of active transmitter units . | +| $N_{\text{TXU,counted}}$ | The number of active transmitter units , as calculated in subclause 6.1, that are taken into account for conducted TX power limit in subclause 6.2, and for unwanted emissions scaling. | +| $N_{\text{TXU,countedpercell}}$ | The number of active transmitter units that are taken into account for emissions scaling per cell, as calculated in subclause 6.6. The number is defined in subclause 6.1. | +| $P_{\text{max,c,cell}}$ | The maximum carrier output power per TAB connector TX min cell group | +| $P_{\text{max,c,TABC}}$ | The maximum carrier output power per TAB connector | +| $P_{\text{max,c,TRP}}$ | The maximum carrier output power per cell | +| $P_{\text{max,t,TRP}}$ | The maximum total output power per cell | +| $P_{\text{Rated,c,TABC}}$ | The rated carrier output power per TAB connector | +| $P_{\text{rated,c,TRP}}$ | The rated carrier TRP | +| $P_{\text{Rated,c,sys}}$ | The sum of $P_{\text{Rated,c,TABC}}$ for all TAB connectors for a single carrier | +| $P_{\text{Rated,t,group}}$ | The sum of $P_{\text{Rated,t,TABC}}$ for all TAB connectors belonging to a specified group | +| $P_{\text{Rated,t,TABC}}$ | The rated total output power per TAB connector | +| $P_{\text{rated,t,TRP}}$ | Rated transmitter TRP declared per RIB | +| $P_{\text{REFSENS}}$ | Conducted reference Sensitivity power level | + +### 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|---------|-----------------------------------------| +| AAS BS | Active Antenna System Base Station | +| ACLR | Adjacent Channel Leakage power Ratio | +| ACS | Adjacent Channel Selectivity | +| AoA | Angle of Arrival | +| BC | Band Category | +| BER | Bit Error Rate | +| BLER | Block Error Rate | +| CACLR | Cumulative ACLR | +| CW | Continuous Wave (unmodulated signal) | +| D-CPICH | Demodulation Common Pilot Channel | +| DIP | Dominant Interferer Proportion | +| EIRP | Equivalent Isotropic Radiated Power | +| EIS | Equivalent Isotropic Sensitivity | +| FCC | Federal Communications Commission | +| FDD | Frequency Division Duplex | +| FRC | Fixed Reference Channel | +| HARQ | Hybrid Automatic Repeat Request | +| HS-DSCH | High Speed Downlink Shared Channel | +| ITU | International Telecommunication Union | +| ITU-R | Radio communication Sector of the ITU | +| MIMO | Multiple Inputs Multiple Outputs | +| MSR | Multi-Standard Radio | +| NB-IoT | Narrowband – Internet of Things | +| OBUE | Operating Band Unwanted Emission | +| OSDD | OTA Sensitivity Directions Declaration | +| OTA | Over The Air | +| OVSF | Orthogonal variable spreading factor | +| PCCPCH | Primary Common Control Physical CHannel | +| RAT | Radio Access Technology | + +| | | +|--------|---------------------------------------------| +| RB | Resource Block (for E-UTRA) | +| RDN | Radio Distribution Network | +| RE | Resource Element | +| RF | Radio Frequency | +| RIB | Radiated Interface Boundary | +| RoAoA | Range of Angles of Arrival | +| sPDCCH | shortened Physical Downlink Control Channel | +| sPDSCH | shortened Physical Downlink Shared Channel | +| TAB | Transceiver Array Boundary | +| TDD | Time Division Duplex | +| TRP | Total Radiated Power | +| TTI | Transmission Time Interval | + +--- + +## 4 General + +### 4.1 Relationship between the AAS BS specification and non-AAS BS single RAT & MSR specifications + +An AAS BS is distinguished from a *non-AAS BS* by including a dedicated antenna system in its design. + +The transceiver to antenna RF interface of the AAS BS (referred to as the *transceiver array boundary*) comprises one or several *TAB connectors*. There is no general one-to-one relationship between *non-AAS BS* antenna connectors and AAS BS *TAB connectors*, but it can be expected the number of *TAB connectors* in AAS BS will be greater than or equal to the number of *non-AAS BS* antenna connectors for respective base stations with corresponding functionality. + +For the conducted requirements, the AAS BS requirements are formulated in such a way that the impact of what they are meant to regulate is expected to be "equivalent" to the corresponding *non-AAS BS* requirements; i.e. the outside world sees the same level of emissions, power levels, or can expect the same demodulation performance at the UE from the AAS BS as it would from a *non-AAS BS* with equivalent functionality. All *non-AAS BS* RF requirements (referenced to the *non-AAS BS* antenna connector) have been adapted to AAS BS conducted requirements. Many requirements are also direct references to the *non-AAS BS* RF specifications 3GPP TS 25.104 [2], 3GPP TS 25.105 [3], 3GPP TS 36.104 [4] and 3GPP TS 37.104 [5]. + +NOTE 1: Applying *non-AAS BS* antenna connector requirements directly to individual *TAB connectors* renders certain AAS BS requirements excessively strict from a system perspective. + +NOTE 2: Both specific references and non-specific references occur. + +In addition, some new OTA requirements are introduced. These requirements have no corresponding *non-AAS BS* requirements. + +For a *OTA AAS BS* there are no conducted requirements. The radiated requirements have been derived based on the principle that they offer the same level of performance and protection as the *hybrid AAS BS* requirements. The radiated requirements therefore use the same equivalence to the non-AAS requirements. The *non-AAS BS* RF requirements have therefore been further adapted to apply to OTA metrics in the far field. Some requirements are direct references to the *non-AAS BS* RF specifications 3GPP TS 25.104 [2], 3GPP TS 25.105 [3], 3GPP TS 36.104 [4] and 3GPP TS 37.104 [5]. Some co-location requirements which have been developed from assumptions on BS-to-BS coupling do not have direct OTA equivalents. The radiated co-location requirements use the same scenarios used to develop the *non-AAS* RF requirements. + +In this specification, the term "requirements for *single RAT operation*" refers to requirements that are derived from the 3GPP TS 25.104 [2], 3GPP TS 25.105 [3], or 3GPP TS 36.104 [4] specifications baseline, whilst "requirements for *MSR operation*" refers to requirements derived from the 3GPP TS 37.104 [5] specification baseline (including NR operation as part of MSR). + +NB-IoT in-band, NB-IoT guard band, or standalone NB-IoT operation is not supported by AAS BS. When referring to standalone E-UTRA requirements for *single RAT operation* in 3GPP TS 36.104 [4] or to E-UTRA requirements for *MSR operation* in 3GPP TS 37.104 [5], any requirements specified in those specifications for E-UTRA with NB-IoT (in-band or guard band) or for standalone NB-IoT, shall not be considered for the AAS BS. Unless otherwise stated, the + +exclusion of the NB-IoT requirements in this specification applies to all operation modes (i.e. *in-band NB-IoT operation*, *guard band NB-IoT operation* and *standalone NB-IoT operation*). NR requirements for *single RAT operation* are not specified in the present document because AAS RF requirements for single RAT NR are fully captured in the NR specification 38.104 [27]. + +Band 46 operation and Band 49 operation is not supported by AAS BS. When referring to standalone E-UTRA requirements for *single RAT operation* in 3GPP TS 36.104 [4] or to E-UTRA requirements for *MSR operation* in 3GPP TS 37.104 [5], any requirements specified in those specifications for Band 46 or Band 49 operation shall not be considered for the AAS BS with E-UTRA. + +## 4.2 Relationship between minimum requirements and test requirements + +Conformance to the present specification is demonstrated by fulfilling the test requirements specified in the conformance specifications TS 37.145-1 [29] and TS 37.145-2 [30]. + +The minimum requirements given in this specification make no allowance for measurement uncertainty. The test specifications TS 37.145-1 [29] and TS 37.145-2 [30] define 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. For some requirements, including regulatory requirements, the test tolerance is set to zero. + +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 Recommendation ITU-R M.1545 [11]. + +## 4.3 Conducted and radiated requirement reference points + +AAS BS requirements are defined for two points of reference, signified by radiated requirements and conducted requirements. + +![Diagram illustrating the radiated and conducted points of reference for a hybrid AAS BS. The diagram shows a Transceiver unit array (TRXUA) with multiple units (labeled #1, #2, ..., #K) connected to a Radio Distribution Network (RDN). The RDN is connected to an Antenna Array (AA). The TRXUA is enclosed in a dashed box labeled 'Transceiver unit array (TRXUA) 1 to M'. The RDN and AA are enclosed in a dashed box labeled 'Composite antenna'. A vertical dashed line labeled 'Transceiver array boundary' separates the TRXUA from the RDN. A vertical dashed line labeled 'Radiated interface boundary' is located to the right of the AA. An arrow labeled 'far field region' points from the AA towards the radiated interface boundary. A label 'Transceiver array boundary connector (TAB)' points to the connection point between the TRXUA and the RDN.](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg) + +Diagram illustrating the radiated and conducted points of reference for a hybrid AAS BS. The diagram shows a Transceiver unit array (TRXUA) with multiple units (labeled #1, #2, ..., #K) connected to a Radio Distribution Network (RDN). The RDN is connected to an Antenna Array (AA). The TRXUA is enclosed in a dashed box labeled 'Transceiver unit array (TRXUA) 1 to M'. The RDN and AA are enclosed in a dashed box labeled 'Composite antenna'. A vertical dashed line labeled 'Transceiver array boundary' separates the TRXUA from the RDN. A vertical dashed line labeled 'Radiated interface boundary' is located to the right of the AA. An arrow labeled 'far field region' points from the AA towards the radiated interface boundary. A label 'Transceiver array boundary connector (TAB)' points to the connection point between the TRXUA and the RDN. + +**Figure 4.3-1: Radiated and conducted points of reference of hybrid AAS BS** + +![Diagram of radiated points of reference of OTA AAS BS. It shows a 'Transceiver unit array (TRXUA) 1 to P' connected to a 'Composite antenna' which contains a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A large arrow points from the composite antenna to a vertical dashed line labeled 'Radiated interface boundary'.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +The diagram illustrates the radiated points of reference for an OTA AAS BS. On the left, a dashed box labeled 'Transceiver unit array (TRXUA) 1 to P' is shown. It is connected via horizontal lines to a central dashed box labeled 'Composite antenna'. Inside the 'Composite antenna' box, there are two sub-components: 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'. A large arrow points from the 'Composite antenna' box to a vertical dashed line on the right, which is labeled 'Radiated interface boundary'. + +Diagram of radiated points of reference of OTA AAS BS. It shows a 'Transceiver unit array (TRXUA) 1 to P' connected to a 'Composite antenna' which contains a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A large arrow points from the composite antenna to a vertical dashed line labeled 'Radiated interface boundary'. + +**Figure 4.3-2: Radiated points of reference of OTA AAS BS** + +Radiated characteristics are defined over the air (OTA) at the *radiated interface boundary* (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) directions in which the OTA requirements apply are detailed for each requirement. + +Some OTA requirements are specified as co-location requirements where the requirements are specified at the conducted interface of the *co-location reference antenna*, co-location requirements are further defined in subclause 4.10. + +Conducted characteristics are defined at individual or groups of *TAB connectors* at the *transceiver array boundary*, which is the conducted interface between the transceiver unit array and the composite antenna. + +The transceiver unit array is part of the composite transceiver functionality generating modulated transmit signal structures and performing receiver combining and demodulation. + +The transceiver unit array contains an implementation specific number of transmitter units and an implementation specific number of receiver units. Transmitter units and receiver units may be combined into transceiver units. The transmitter/receiver units have the ability to transmit/receive parallel independent modulated symbol streams. + +The composite antenna contains a *radio distribution network* (RDN) and an antenna array. The RDN is a linear passive network which distributes the RF power generated by the transceiver unit array to the antenna array, and/or distributes the radio signals collected by the antenna array to the transceiver unit array, in an implementation specific way. + +How a conducted requirement is applied to the *transceiver array boundary* is detailed in the respective requirement subclause. + +## 4.4 Base station classes for AAS BS + +The requirements in the present document apply to AAS BS of Wide Area BS, Medium Range BS and Local Area BS classes unless otherwise stated. The associated deployment scenarios and definitions of BS classes are exactly the same for AAS BS with and without connectors. + +BS classes for *OTA AAS BS* are defined as indicated below: + +- Wide Area Base Stations are characterised by requirements derived from Macro Cell scenarios with a BS to UE minimum distance along the ground equal to 35 m. +- Medium Range Base Stations are characterised by requirements derived from Micro Cell scenarios with a BS to UE minimum distance along the ground equal to 5 m. +- Local Area Base Stations are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum distance along the ground equal to 2 m. + +BS classes for *hybrid AAS BS* are defined as indicated below: + +- Wide Area BS are characterized by requirements derived from Macro Cell scenarios. For *AAS BS* of Wide Area BS class, the minimum coupling loss between any *TAB connector* and the UE is 70 dB. +- Medium Range BS are characterized by requirements derived from Micro Cell scenarios. For *AAS BS* of Medium Range BS class, the minimum coupling loss between any *TAB connector* and the UE is 53 dB. +- Local Area BS are characterized by requirements derived from Pico Cell scenarios. For *AAS BS* of Local Area BS class, the minimum coupling loss between any *TAB connector* and the UE is 45 dB. + +NOTE: Whenever WA BS is referred in this specification, the NB-IoT Wide Area BS and related requirements as defined in 3GPP TS 36.104 [4], are not applicable for *OTA AAS BS*, nor for *hybrid AAS BS*. + +## 4.5 Regional requirements + +Some requirements in the present document may only apply in certain regions either as optional requirements, or as mandatory requirements set by local and regional regulation. It is normally not stated in the 3GPP specifications under what exact circumstances the regional requirements apply, since this is defined by local or regional regulation. + +Table 4.5-1 lists all requirements in the present specification that may be applied differently in different regions. *Non-AAS BS* requirements are applicable as defined in the present document. In many cases, such requirements include regional requirements that are implicitly referenced from the present specification, and listed in the specification for the specifications concerned 3GPP TS 25.104 [2], 3GPP TS 25.105 [3], 3GPP TS 36.104 [4] and 3GPP TS 37.104 [5]. + +**Table 4.5-1: List of regional requirements** + +| Clause number | Requirement | Comments | +|-------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.6 | Operating bands and Band Categories | Some operating bands may be applied regionally. | +| 6.6.2, 9.7.2 | Occupied bandwidth and OTA Occupied bandwidth | The requirement may be applied regionally. There may also be regional requirements to declare the Occupied bandwidth according to the definition. | +| 6.6.4, 9.7.4 | Spectrum emission mask and OTA Spectrum emission mask | The mask specified may be mandatory in certain regions. In other regions this mask may not be applied. Additional spectrum protection requirements may apply regionally. | +| 6.6.5, 9.7.5 | Operating band unwanted emissions and OTA Operating band unwanted emissions | Category A or Category B operating band unwanted emissions limits may be applied regionally. | +| 6.6.5, 9.7.5 | Operating band unwanted emissions and OTA Operating band unwanted emissions | The BS may have to comply with the applicable emission limits established by FCC Title 47 [15], when deployed in regions where those limits are applied and under the conditions declared by the manufacturer. | +| 6.6.5, 9.7.5 | Operating band unwanted emissions and OTA Operating band unwanted emissions | The requirements for protection of DTT may apply regionally. | +| 6.6.5, 9.7.5 | Operating band unwanted emissions and OTA Operating band unwanted emissions | Regional requirement as defined in 3GPP TS 37.104, subclause 6.6.2.4.4 [9] may be applied for the protection of systems operating in frequency bands adjacent to band 1 as defined in 3GPP TS 37.104, subclause 4.5, [9] in geographic areas in which both an adjacent band service and UTRA and/or E-UTRA are deployed. | +| 6.6.5, 9.7.5 | Operating band unwanted emissions and OTA Operating band unwanted emissions | Additional requirements defined for Band 24 in 3GPP TS 37.104, subclause 6.6.2.4.5 may apply in regions where FCC regulation applies. | +| 6.6.5, 9.7.5 | Operating band unwanted emissions and OTA Operating band unwanted emissions | Additional band 32 unwanted emissions requirements may apply in certain regions | +| 6.6.6, 9.7.6 | Spurious emissions and OTA Spurious emissions | Category A limits are mandatory for regions where Category A limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [14] apply. Category B limits are mandatory for regions where Category B limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [14] apply. | +| 6.6.6, 9.7.6 | Spurious emissions and OTA Spurious emissions | Additional spurious emissions requirements may be applied for the protection of system operating in frequency ranges other than the AAS BS operating band as described in 3GPP TS 37.104 [9] subclause 6.6.1.3 (NOTE). | +| 6.6.6, 9.7.6 | Spurious emissions and OTA Spurious emissions | In addition to 3GPP requirements, the BS may have to comply with the applicable emission limits established by FCC Title 47 [15], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. | +| 6.6.6, 9.7.6 | Spurious emissions and OTA Spurious emissions | The emission limits specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | +| 6.6.6, 9.7.6 | Spurious emissions and OTA Spurious emissions | Additional requirements defined for Band 54 in 3GPP TS 37.104 [9], subclause 6.6.1.3.1 may apply in regions where FCC regulation applies. | +| 6.7, 9.8 | Transmitter intermodulation and OTA Transmitter intermodulation | Additional requirements may apply in certain regions. | +| 7.4.2.3, 10.5.2.3 | Additional BC3 blocking requirement | This requirement may be applied for the protection of the BS receiver when an MSR BS is operating in the same geographical area as UTRA TDD. | +| 7.5, 10.6 | Blocking and OTA Blocking | For the Public Safety LTE BS in Korea from 718 to 728 MHz in Band 28, regional blocking requirement is specified in TS 36.104 [8], subclause 7.6.3. | +| 7.6, 10.7.4 | Rx spurious emissions and OTA Rx Spurious emissions | The emission limits specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | + +## 4.6 Operating Bands and Band Categories + +The operating bands and *band categories* for AAS BS are the same as for *non-AAS BS*, as described in 3GPP TS 37.104 [5]. + +NOTE 1: AAS BS does not support GSM, but BC2 is still applicable for protection of and against GSM operation in BC2 operating bands. + +NOTE 2: AAS BS does not support Band 46 (and all its sub-bands defined in 3GPP TS 36.104 [8], subclause 5.5) operation nor Band 49 operation, but Band 46 or Band 49 requirements are still applicable for AAS BS for protection of and against Band 46 or Band 49 operation. + +## 4.7 Channel arrangements + +The channel arrangements for AAS BS are the same as those for UTRA *non-AAS BS*, E-UTRA *non-AAS BS* and NR *non-AAS BS* as described in 3GPP TS 37.104 [5]. + +NOTE: Requirements for nominal carrier spacing of 19.8 MHz and 20.1 MHz for carriers in Band 46 as specified in 36.104 [8] subclause 5.7.1, are not applicable for AAS BS. + +## 4.8 Requirements for contiguous and non-contiguous spectrum + +A spectrum allocation where an AAS BS operates can be either contiguous or non-contiguous. Unless otherwise stated, the requirements in the present specification apply for AAS BS configured for both *contiguous spectrum* operation and *non-contiguous spectrum* operation. + +For AAS BS operation in *non-contiguous spectrum*, some requirements apply both at the *Base Station RF Bandwidth edges* and inside the *sub-block gaps*. For each such requirement, it is stated how the limits apply relative to the *Base Station RF Bandwidth edges* and the *sub-block edges* respectively. + +## 4.9 Requirements for AAS BS capable of operation in multiple operating bands + +For AAS BS capable of operation in multiple operating bands, the RF requirements in clause 6, 7, 9, and 10 apply separately to each supported operating band unless otherwise stated. + +A *hybrid AAS BS* may be capable of supporting operation in multiple operating bands with one of the following implementations of *TAB connectors* in the *transceiver array boundary*: + +- All *TAB connectors* are *single band TAB connectors*. + - Different sets of *single band TAB connectors* support different operating bands, but each *TAB connector* supports only operation in one single operating band. + - Sets of *single band TAB connectors* support operation in multiple operating bands with some *single band TAB connectors* supporting more than one operating band. +- All *TAB connectors* are *multiband TAB connectors*. +- A combination of single band sets and multi-band sets of *TAB connectors* provides support of the *hybrid AAS BS* capability of operation in multiple operating bands. + +Unless otherwise stated all requirements specified for an operating band apply only to the set of *TAB connectors* supporting that operating band. + +In certain requirements it is explicitly stated that specific additions or exclusions to the requirement apply at *multi-band TAB connectors* as detailed in the requirement subclause. When referencing the NR specification 3GPP TS 38.104 [27] for a BS type 1-H the multi-band connector term is equivalent to a *multi-band TAB connector* in this specification. + +In the case of an operating band being supported only by *single band TAB connectors* in a *TAB connector TX min cell group* or a *TAB connector RX min cell group*, *single band requirements* apply to that set of *TAB connectors*. + +NOTE: Each supported operating band needs to be operated separately during conformance testing on *single band TAB connectors*. + +For a band supported by a *TAB connector* where the transmitted carriers are not processed in active RF components together with carriers in any other band, *TX single band requirements* shall apply. For a band supported by a *TAB connector* where the received carriers are not processed in active RF components together with carriers in any other band, *RX single band requirements* shall apply. + +In the case of an operating band being supported only by *multi-band TAB connectors* supporting the same operating band combination in a *TAB connector TX min cell group* or a *TAB connector RX min cell group*, *multi-band requirements* apply to that set of *TAB connectors*. + +The case of an operating band being supported by both *multi-band TAB connectors* and *single band TAB connectors* in a *TAB connector TX min cell group* or a *TAB connector RX min cell group* is not covered by the present release of this specification. + +The case of an operating band being supported by *multi-band TAB connectors* which are not all supporting the same operating band combination in a *TAB connector TX min cell group* or a *TAB connector RX min cell group* is not covered by the present release of this specification. + +An *OTA AAS BS* may be capable of supporting operation in multiple operating bands with one of the following implementations at the *radiated interface boundary*: + +- All RIBs are *single band RIBs*. +- All RIBs are *multiband RIBs*. +- A combination of *single band RIBs* and *multi-band RIBs* provides support of the *OTA AAS BS* capability of operation in multiple operating bands. + +In certain requirements it is explicitly stated that specific additions or exclusions to the requirement apply at *multi-band RIBs* as detailed in the requirement subclause. + +NOTE: Each supported operating band needs to be operated separately during conformance testing for single RIBs. + +For *multi-band TAB connectors* and *multi-band RIBs* supporting the bands for TDD, the RF requirements in the present specification assume no simultaneous uplink and downlink occur between the bands. + +The RF requirements for *multi-band TAB connectors* and *multi-band RIBs* supporting bands for both FDD and TDD are not covered by the present release of this specification. + +A RIB may operate multi-RAT where the individual RATs are operated in different RAT specific bands that partially or fully overlap; $\Delta f_{\text{OBUE}}$ and $\Delta f_{\text{FOB}}$ are according to the combined frequency range occupied by the overlapping bands. + +## 4.10 OTA Co-location with other base stations + +Co-location requirements are requirements which are based on assuming the AAS BS is co-located with another BS of the same base station class, they ensure that both co-located systems can operate with minimal degradation to each other. + +Unwanted emissions and out-of-band blocking co-location requirements are optional requirements based on declaration. TX OFF and TX IMD are mandatory requirements and have the form of a co-location requirement as it represents the worst-case scenario of all the interference cases. + +NOTE: Due to the low level of the unwanted emissions for the spurious emissions and TX OFF level, co-location is the most suitable method to show conformance. + +The *co-location reference antenna*, shall be a single column passive antenna which has the same vertical radiating dimension (h), frequency range, polarization, as the composite antenna of AAS BS and nominal 65° horizontal half- + +power beamwidth (suitable for 3-sector deployments) and is placed at a distance $d$ from the edge of the AAS BS, as shown in Figure 4.10-1. + +![Figure 4.10-1: Illustration of AAS BS enclosure and co-location reference antenna. The diagram shows two views: Front View and Top View. In the Front View, the AAS BS is a rectangle with an 'Enclosure' label pointing to its left edge. To its right is the 'Co-location Reference antenna', also a rectangle. The distance between their right edges is labeled 'd'. The height of the reference antenna is labeled 'h'. In the Top View, both the AAS BS and the reference antenna are shown as semi-circles. The distance between their flat edges is labeled 'd'. Both are labeled 'Radiatingface'.](474a819357587e34949a3e110ff19b30_img.jpg) + +Figure 4.10-1: Illustration of AAS BS enclosure and co-location reference antenna. The diagram shows two views: Front View and Top View. In the Front View, the AAS BS is a rectangle with an 'Enclosure' label pointing to its left edge. To its right is the 'Co-location Reference antenna', also a rectangle. The distance between their right edges is labeled 'd'. The height of the reference antenna is labeled 'h'. In the Top View, both the AAS BS and the reference antenna are shown as semi-circles. The distance between their flat edges is labeled 'd'. Both are labeled 'Radiatingface'. + +**Figure 4.10-1 Illustration of AAS BS enclosure and co-location reference antenna** + +Edge-to-edge separation $d$ , between the AAS BS and the *co-location reference antenna* shall be set to 0.1 m. + +The AAS BS and the *co-location reference antenna* shall be aligned in a common plane perpendicular to the mechanical bore-sight direction, as shown in figure 4.10-1. + +The *co-location reference antenna* and the AAS can have different width. + +The vertical radiating regions of the *co-location reference antenna* and the AAS composite antenna shall be aligned. + +For co-location requirements where the frequency range of the signal at the *co-location reference antenna* is different from the AAS BS, a *co-location reference antenna* suitable for the frequency stated in the requirement is assumed. + +OTA co-location requirements are based on the power at the conducted interface of a *co-location reference antenna*, depending on the requirement this interface is either an input or an output. + +For AAS BS with dual polarization the *co-location reference antenna* has two conducted interfaces each representing one polarization. + +## 5 Applicability of Requirements + +### 5.1 General + +The applicability of requirements is related to the band categories described in 3GPP TS 37.104 [5]. This clause captures the requirement clauses' applicability for the respective band categories depending on the operating band specific BS RAT/MSR capability. For each individual band, the manufacturer declares whether the AAS BS conforms to MSR or single RAT requirements. + +The applicability of requirements is further related to the declared AAS BS architecture, either a *hybrid AAS BS* or a *OTA AAS BS*. This clause captures the requirement clauses applicability to either the *hybrid AAS BS requirement set* or the *OTA AAS BS requirement set*. The manufacturer declares whether the AAS BS conforms to the *hybrid AAS BS requirement set* or the *OTA AAS BS requirement set*. + +In the present specification, requirements for *MSR operation* and for *single RAT operation* are defined. If the AAS BS is declared to be single RAT in an operating band, the respective requirements for *single RAT operation* (derived from 3GPP TS 25.104 [2], 3GPP TS 25.105 [3] or 3GPP TS 36.104 [4]) apply in that operating band. If the AAS BS is declared to be MSR (operating one or more RATs) in the operating band, the requirements for *MSR operation* (derived from 3GPP TS 35.104 [5]) apply to that operating band. Where requirements for *MSR operation* comprise RAT specific requirements, these apply only when the AAS BS is operating the RAT in the operating band. + +NOTE: An AAS BS declared MSR in an operating band and operating only one RAT is differentiated from an AAS BS declared single RAT in the operating band by the fact that requirements are derived from 3GPP TS 37.104 [5] rather than from the single RAT specifications 3GPP TS 25.104 [2], 3GPP TS 25.105 [3] or 3GPP TS 36.104 [4]. + +## 5.2 Band category 1 (BC1) and band category 2 (BC2) + +The RF requirements listed in table 5.2-1 apply to AAS BS for each supported operating band belonging to BC1 and BC2. Requirements apply according to the RAT/MSR capability of the AAS BS in the operating band, as listed in the heading of the table and the declared requirement set (hybrid or OTA). Some requirements listed in the table may not be mandatory or they may apply only regionally. This is further specified in the subclause treating each requirement and in table 4.5-1. + +NOTE: Bands in BC1 and BC2 categories are also used for NB-IoT operation. NB-IoT is not applicable for AAS BS. + +For operation in multiple operating bands, the applicability of the requirements in table 5.2-1 is determined based on the manufacturer declared AAS BS RAT and single RAT/MSR conformance for each operating band. The applicability of *multi-band requirements* respective *single band requirements* is defined in clause 4.9 and in each referred clause in the table but it cannot be determined by the table itself. + +**Table 5.2-1: Applicability of RF requirements for AAS BS operation in BC1 and BC2** + +| RF requirement | AAS BS is MSR capable in the band | | AAS BS is MSR capable and operating UTRA only in the band | | AAS BS is MSR capable and operating E-UTRA only in the band | | AAS BS is single-RAT UTRA FDD in the band | | AAS BS is single-RAT E-UTRA FDD in the band | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------|-------------------|-----------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------|-------------------| +| | hybrid AAS BS | OTA AAS BS | hybrid AAS BS | OTA AAS BS | hybrid AAS BS | OTA AAS BS | hybrid AAS BS | OTA AAS BS | hybrid AAS BS | OTA AAS BS | +| Base station output power | 6.2.1
6.2.2.1
6.2.2.2
6.2.3.1
6.2.3.2
6.2.5.1
6.2.5.2
6.2.6.1
6.2.6.2 | | 6.2.1
6.2.2.1
6.2.2.2
6.2.3.1
6.2.3.2
6.2.5.1
6.2.5.2 | | 6.2.1
6.2.2.1
6.2.2.2
6.2.6.1
6.2.6.2 | | 6.2.1
6.2.2.1
6.2.2.3
6.2.3.1
6.2.3.3
6.2.5.1
6.2.5.3 | | 6.2.1
6.2.2.1
6.2.2.4
6.2.6.1
6.2.6.4 | | +| Output power dynamics | 6.3.1
6.3.2.1
6.3.2.2
6.3.3.1
6.3.3.2
6.3.4.1
6.3.4.2
6.3.5.1
6.3.5.2
6.3.6.1
6.3.6.2 | | 6.3.1
6.3.2.1
6.3.2.2
6.3.3.1
6.3.3.2
6.3.4.1
6.3.4.2
6.3.5.1
6.3.5.2 | | 6.3.1
6.3.4.1
6.3.4.2
6.3.6.1
6.3.6.2 | | 6.3.1
6.3.2.1
6.3.2.3
6.3.3.1
6.3.3.3
6.3.4.1
6.3.4.3
6.3.5.1
6.3.5.3 | | 6.3.1
6.3.4.1
6.3.4.4
6.3.6.1
6.3.6.4 | | +| Transmit ON/OFF power | - | - | - | - | - | - | - | - | - | - | +| Transmitted signal | 6.5.1 | - | 6.5.1 | - | 6.5.1 | - | 6.5.1 | - | 6.5.1 | - | + +| | | | | | | | | | | | +|------------------------------------------------------|--------------------|-----------------------------------------------------------------------------------------------|--------------------|-------------------------------------------------------------------------|--------------------|---------------------------------------------------|--------------------|-------------------------------------------------------------------------|--------------------|---------------------------------------------------| +| quality | | | | | | | | | | | +| Frequency error | 6.5.2.1
6.5.2.2 | - | 6.5.2.1
6.5.2.2 | - | 6.5.2.1
6.5.2.2 | - | 6.5.2.1
6.5.2.3 | - | 6.5.2.1
6.5.2.4 | - | +| Time alignment error | 6.5.3.1
6.5.3.2 | - | 6.5.3.1
6.5.3.2 | - | 6.5.3.1
6.5.3.2 | - | 6.5.3.1
6.5.3.3 | - | 6.5.3.1
6.5.3.4 | - | +| Modulation quality | 6.5.4.1
6.5.4.2 | - | 6.5.4.1
6.5.4.2 | - | 6.5.4.1
6.5.4.2 | - | 6.5.4.1
6.5.4.3 | - | 6.5.4.1
6.5.4.4 | - | +| Transmit pulse shape filter | 6.5.5.1
6.5.5.2 | - | 6.5.5.1
6.5.5.2 | - | - | - | 6.5.5.1
6.5.5.3 | - | - | - | +| Unwanted emissions | 6.6.1 | - | 6.6.1 | - | 6.6.1 | - | 6.6.1 | - | 6.6.1 | - | +| Occupied bandwidth | 6.6.2.1
6.6.2.2 | - | 6.6.2.1
6.6.2.2 | - | 6.6.2.1
6.6.2.2 | - | 6.6.2.1
6.6.2.3 | - | 6.6.2.1
6.6.2.4 | - | +| ACLR (and Cumulative ACLR) | 6.6.3.1
6.6.3.2 | - | 6.6.3.1
6.6.3.2 | - | 6.6.3.1
6.6.3.2 | - | 6.6.3.1
6.6.3.3 | - | 6.6.3.1
6.6.3.4 | - | +| Spectrum emission mask | - | - | - | - | - | - | 6.6.4.1
6.6.4.3 | - | - | - | +| Operating band unwanted emissions | 6.6.5.1
6.6.5.2 | - | 6.6.5.1
6.6.5.2 | - | 6.6.5.1
6.6.5.2 | - | - | - | 6.6.5.1
6.6.5.4 | - | +| Transmitter spurious emissions | 6.6.6.1
6.6.6.2 | - | 6.6.6.1
6.6.6.2 | - | 6.6.6.1
6.6.6.2 | - | 6.6.6.1
6.6.6.3 | - | 6.6.6.1
6.6.6.4 | - | +| Transmitter intermodulation | 6.7.1
6.7.2 | - | 6.7.1
6.7.2 | - | 6.7.1
6.7.2 | - | 6.7.1
6.7.3 | - | 6.7.1
6.7.4 | - | +| Reference sensitivity level | 7.2.1
7.2.2 | - | 7.2.1
7.2.2 | - | 7.2.1
7.2.2 | - | 7.2.1
7.2.3 | - | 7.2.1
7.2.4 | - | +| Dynamic range | 7.3.1
7.3.2 | - | 7.3.1
7.3.2 | - | 7.3.1
7.3.2 | - | 7.3.1
7.3.3 | - | 7.3.1
7.3.4 | - | +| Adjacent channel selectivity and narrowband blocking | 7.4.1
7.4.2 | - | 7.4.1
7.4.2 | - | 7.4.1
7.4.2 | - | 7.4.1
7.4.3 | - | 7.4.1
7.4.4 | - | +| Blocking | 7.5.1
7.5.2 | - | 7.5.1
7.5.2 | - | 7.5.1
7.5.2 | - | 7.5.1
7.5.3 | - | 7.5.1
7.5.4 | - | +| Receiver spurious emissions | 7.6.1
7.6.2 | - | 7.6.1
7.6.2 | - | 7.6.1
7.6.2 | - | 7.6.1
7.6.3 | - | 7.6.1
7.6.4 | - | +| Receiver intermodulation | 7.7.1
7.7.2 | - | 7.7.1
7.7.2 | - | 7.7.1
7.7.2 | - | 7.7.1
7.7.3 | - | 7.7.1
7.7.4 | - | +| In-channel selectivity | 7.8.1
7.8.2 | - | - | - | 7.8.1
7.8.2 | - | - | - | 7.8.1
7.8.4 | - | +| Radiated transmit power | 9.2.1
9.2.2 | | 9.2.1
9.2.2 | | 9.2.1
9.2.2 | | 9.2.1
9.2.3 | | 9.2.1
9.2.4 | | +| OTA Base Station output power | - | 9.3.1
9.3.2.1
9.3.2.2
9.3.3.1
9.3.3.2
9.3.5.1
9.3.5.2
9.3.6.1
9.3.6.2 | - | 9.3.1
9.3.2.1
9.3.2.2
9.3.3.1
9.3.3.2
9.3.5.1
9.3.5.2 | - | 9.3.1
9.3.2.1
9.3.2.2
9.3.6.1
9.3.6.2 | - | 9.3.1
9.3.2.1
9.3.2.3
9.3.3.1
9.3.3.3
9.3.5.1
9.3.5.3 | - | 9.3.1
9.3.2.1
9.3.2.4
9.3.6.1
9.3.6.4 | + +| | | | | | | | | | | | +|----------------------------------------------------------|---|---------------------------------------------------------------------------------------------------------------------|---|-----------------------------------------------------------------------------------------------|---|---------------------------------------------------|---|-----------------------------------------------------------------------------------------------|---|---------------------------------------------------| +| OTA Output power dynamics | | 9.4.1
9.4.2.1
9.4.2.2
9.4.3.1
9.4.3.2
9.4.4.1
9.4.4.2
9.4.5.1
9.4.5.2
9.4.6.1
9.4.6.2 | | 9.4.1
9.4.2.1
9.4.2.2
9.4.3.1
9.4.3.2
9.4.4.1
9.4.4.2
9.4.5.1
9.4.5.2 | | 9.4.1
9.4.4.1
9.4.4.2
9.4.6.1
9.4.6.2 | | 9.4.1
9.4.2.1
9.4.2.3
9.4.3.1
9.4.3.3
9.4.4.1
9.4.4.3
9.4.5.1
9.4.5.3 | | 9.4.1
9.4.4.1
9.4.4.4
9.4.6.1
9.4.6.4 | +| OTA Transmit ON/OFF power | - | - | - | - | - | - | - | - | - | - | +| OTA Transmitted signal quality | - | 9.6.1 | - | 9.6.1 | - | 9.6.1 | - | 9.6.1 | - | 9.6.1 | +| OTA Frequency Error | - | 9.6.2.1
9.6.2.2 | - | 9.6.2.1
9.6.2.2 | - | 9.6.2.1
9.6.2.2 | - | 9.6.2.1
9.6.2.3 | - | 9.6.2.1
9.6.2.4 | +| OTA Time alignment error | - | 9.6.3.1
9.6.3.2 | - | 9.6.3.1
9.6.3.2 | - | 9.6.3.1
9.6.3.2 | - | 9.6.3.1
9.6.3.3 | - | 9.6.3.1
9.6.3.4 | +| OTA modulation quality | - | 9.6.4.1
9.6.4.2 | - | 9.6.4.1
9.6.4.2 | - | 9.6.4.1
9.6.4.2 | - | 9.6.4.1
9.6.4.3 | - | 9.6.4.1
9.6.4.4 | +| OTA Transmit pulse shape filter | - | 9.6.5.1
9.6.5.2 | - | 9.6.5.1
9.6.5.2 | - | - | - | 9.6.5.1
9.6.5.3 | - | - | +| OTA Unwanted Emissions | - | 9.7.1 | - | 9.7.1 | - | 9.7.1 | - | 9.7.1 | - | 9.7.1 | +| OTA Occupied bandwidth | - | 9.7.2.1
9.7.2.2 | - | 9.7.2.1
9.7.2.2 | - | 9.7.2.1
9.7.2.2 | - | 9.7.2.1
9.7.2.3 | - | 9.7.2.1
9.7.2.4 | +| OTA Adjacent Channel Leakage power Ratio | - | 9.7.3.1
9.7.3.2 | - | 9.7.3.1
9.7.3.2 | - | 9.7.3.1
9.7.3.2 | - | 9.7.3.1
9.7.3.3 | - | 9.7.3.1
9.7.3.4 | +| OTA Spectrum emission mask | - | - | - | - | - | - | - | 9.7.4.1
9.7.4.3 | - | - | +| OTA Operating band unwanted emission | - | 9.7.5.1
9.7.5.2 | - | 9.7.5.1
9.7.5.2 | - | 9.7.5.1
9.7.5.2 | - | - | - | 9.7.5.1
9.7.5.4 | +| OTA Spurious emission | - | 9.7.6.1
9.7.6.2 | - | 9.7.6.1
9.7.6.2 | - | 9.7.6.1
9.7.6.2 | - | 9.7.6.1
9.7.6.3 | - | 9.7.6.1
9.7.6.4 | +| OTA Transmitter intermodulation | - | 9.8.1
9.8.2 | - | 9.8.1
9.8.2 | - | 9.8.1
9.8.2 | - | 9.8.1
9.8.3 | - | 9.8.1
9.8.4 | +| OTA sensitivity | | 10.2.1
10.2.2 | | 10.2.1
10.2.2 | | 10.2.1
10.2.2 | | 10.2.1
10.2.3 | | 10.2.1
10.2.4 | +| OTA Reference sensitivity level | - | 10.3.1
10.3.2 | - | 10.3.1
10.3.2 | - | 10.3.1
10.3.2 | - | 10.3.1
10.3.3 | - | 10.3.1
10.3.4 | +| OTA Dynamic range | - | 10.4.1
10.4.2 | - | 10.4.1
10.4.2 | - | 10.4.1
10.4.2 | - | 10.4.1
10.4.3 | - | 10.4.1
10.4.4 | +| OTA Adjacent channel selectivity and narrowband blocking | - | 10.5.1
10.5.2 | - | 10.5.1
10.5.2 | - | 10.5.1
10.5.2 | - | 10.5.1
10.5.3 | - | 10.5.1
10.5.4 | +| OTA Blocking | - | 10.6.1
10.6.2 | - | 10.6.1
10.6.2 | - | 10.6.1
10.6.2 | - | 10.6.1
10.6.3 | - | 10.6.1
10.6.4 | +| OTA Receiver spurious emissions | - | 10.7.1
10.7.2 | - | 10.7.1
10.7.2 | - | 10.7.1
10.7.2 | - | 10.7.1
10.7.3 | - | 10.7.1
10.7.4 | +| OTA Receiver intermodulation | - | 10.8.1
10.8.2 | - | 10.8.1
10.8.2 | - | 10.8.1
10.8.2 | - | 10.8.1
10.8.3 | - | 10.8.1
10.8.4 | +| OTA In-channel selectivity | - | 10.9.1
10.9.2 | - | - | - | 10.9.1
10.9.2 | - | - | - | 10.9.1
10.9.4 | + +NOTE: For some requirements, the requirement is defined by reference to the respective *non-AAS BS*. These requirements cannot be identified from this table. + +## 5.3 Band category 3 (BC3) + +The RF requirements listed in table 5.3-1 apply to AAS BS for each supported operating band belonging to BC3. Requirements apply according to the RAT/MSR capability of the AAS BS in the operating band, as listed in the heading of the table and the declared requirement set (hybrid or OTA). Some requirements listed in the table may not be mandatory or they may apply only regionally. This is further specified in the clause of each requirement and in table 4.5-1. + +For operation in multiple operating bands, the applicability of the requirements in table 5.3-1 is determined based on the manufacturer declared AAS BS RAT and single RAT/MSR conformance for each operating band. The applicability of *multi-band requirements* respective *single band requirements* is defined in clause 4.9 and in each referred clause in the table but it cannot be determined by the table itself. + +**Table 5.3-1: Applicability of RF requirements for AAS BS operation in BC3** + +| RF requirement | AAS BS is MSR capable in the band | | AAS BS is MSR capable and operating UTRA only in the band | | AAS BS is MSR capable and operating E-UTRA only in the band | | AAS BS is single-RAT UTRA TDD in the band | | AAS BS is single-RAT E-UTRA TDD in the band | | +|-----------------------------|-----------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|------------|-------------------------------------------------------------|------------|---------------------------------------------------|------------|---------------------------------------------------|------------| +| | hybrid AAS BS | OTA AAS BS | hybrid AAS BS | OTA AAS BS | hybrid AAS BS | OTA AAS BS | hybrid AAS BS | OTA AAS BS | hybrid AAS BS | OTA AAS BS | +| Base station output power | 6.2.1
6.2.2.1
6.2.2.2
6.2.4.1
6.2.4.2
6.2.6.1
6.2.6.2 | - | 6.2.1
6.2.2.1
6.2.2.2
6.2.4.1
6.2.4.2 | - | 6.2.1
6.2.2.1
6.2.2.2
6.2.6.1
6.2.6.2 | - | 6.2.1
6.2.2.1
6.2.2.3
6.2.4.1
6.2.4.3 | - | 6.2.1
6.2.2.1
6.2.2.4
6.2.6.1
6.2.6.4 | - | +| Output power dynamics | 6.3.1
6.3.2.1
6.3.2.2
6.3.3.1
6.3.3.2
6.3.4.1
6.3.4.2
6.3.6.1
6.3.6.2 | - | 6.3.1
6.3.2.1
6.3.2.2
6.3.3.1
6.3.3.2 | - | 6.3.1
6.3.4.1
6.3.4.2
6.3.6.1
6.3.6.2 | - | 6.3.1
6.3.2.1
6.3.2.3
6.3.3.1
6.3.3.3 | - | 6.3.1
6.3.4.1
6.3.4.4
6.3.6.1
6.3.6.4 | - | +| Transmit ON/OFF power | 6.4 | - | 6.4 | - | 6.4 | - | 6.4 | - | 6.4 | - | +| Transmitted signal quality | 6.5.1 | - | 6.5.1 | - | 6.5.1 | - | 6.5.1 | - | 6.5.1 | - | +| Frequency error | 6.5.2.1
6.5.2.2 | - | 6.5.2.1
6.5.2.2 | - | 6.5.2.1
6.5.2.2 | - | 6.5.2.1
6.5.2.3 | - | 6.5.2.1
6.5.2.4 | - | +| Time alignment error | 6.5.3.1
6.5.3.2 | - | 6.5.3.1
6.5.3.2 | - | 6.5.3.1
6.5.3.2 | - | 6.5.3.1
6.5.3.3 | - | 6.5.3.1
6.5.3.4 | - | +| Modulation quality | 6.5.4.1
6.5.4.2 | - | 6.5.4.1
6.5.4.2 | - | 6.5.4.1
6.5.4.2 | - | 6.5.4.1
6.5.4.3 | - | 6.5.4.1
6.5.4.4 | - | +| Transmit pulse shape filter | 6.5.5.1
6.5.5.2 | - | 6.5.5.1
6.5.5.2 | - | - | - | 6.5.5.1
6.5.5.3 | - | - | - | +| Unwanted emissions | 6.6.1 | - | 6.6.1 | - | 6.6.1 | - | 6.6.1 | - | 6.6.1 | - | + +| | | | | | | | | | | | +|------------------------------------------------------|--------------------|-----------------------------------------------------------------------------------------------|--------------------|---------------------------------------------------|--------------------|---------------------------------------------------|--------------------|---------------------------------------------------|--------------------|---------------------------------------------------| +| Occupied bandwidth | 6.6.2.1
6.6.2.2 | - | 6.6.2.1
6.6.2.2 | - | 6.6.2.1
6.6.2.2 | - | 6.6.2.1
6.6.2.3 | - | 6.6.2.1
6.6.2.4 | - | +| ACLR (and Cumulative ACLR) | 6.6.3.1
6.6.3.2 | - | 6.6.3.1
6.6.3.2 | - | 6.6.3.1
6.6.3.2 | - | 6.6.3.1
6.6.3.3 | - | 6.6.3.1
6.6.3.4 | - | +| Spectrum emission mask | - | - | - | - | - | - | 6.6.4.1
6.6.4.3 | - | - | - | +| Operating band unwanted emissions | 6.6.5.1
6.6.5.2 | - | 6.6.5.1
6.6.5.2 | - | 6.6.5.1
6.6.5.2 | - | - | - | 6.6.5.1
6.6.5.4 | - | +| Transmitter spurious emissions | 6.6.6.1
6.6.6.2 | - | 6.6.6.1
6.6.6.2 | - | 6.6.6.1
6.6.6.2 | - | 6.6.6.1
6.6.6.3 | - | 6.6.6.1
6.6.6.4 | - | +| Transmitter intermodulation | 6.7.1
6.7.2 | - | 6.7.1
6.7.2 | - | 6.7.1
6.7.2 | - | 6.7.1
6.7.3 | - | 6.7.1
6.7.4 | - | +| Reference sensitivity level | 7.2.1
7.2.2 | - | 7.2.1
7.2.2 | - | 7.2.1
7.2.2 | - | 7.2.1
7.2.3 | - | 7.2.1
7.2.4 | - | +| Dynamic range | 7.3.1
7.3.2 | - | 7.3.1
7.3.2 | - | 7.3.1
7.3.2 | - | 7.3.1
7.3.3 | - | 7.3.1
7.3.4 | - | +| Adjacent channel selectivity and narrowband blocking | 7.4.1
7.4.2 | - | 7.4.1
7.4.2 | - | 7.4.1
7.4.2 | - | 7.4.1
7.4.3 | - | 7.4.1
7.4.4 | - | +| Blocking | 7.5.1
7.5.2 | - | 7.5.1
7.5.2 | - | 7.5.1
7.5.2 | - | 7.5.1
7.5.3 | - | 7.5.1
7.5.4 | - | +| Receiver spurious emissions | 7.6.1
7.6.2 | - | 7.6.1
7.6.2 | - | 7.6.1
7.6.2 | - | 7.6.1
7.6.3 | - | 7.6.1
7.6.4 | - | +| Receiver intermodulation | 7.7.1
7.7.2 | - | 7.7.1
7.7.2 | - | 7.7.1
7.7.2 | - | 7.7.1
7.7.3 | - | 7.7.1
7.7.4 | - | +| In-channel selectivity | 7.8.1
7.8.2 | - | - | - | 7.8.1
7.8.2 | - | - | - | 7.8.1
7.8.4 | - | +| | | | | | | | | | | | +| Radiated transmit power | 9.2.1
9.2.2 | | 9.2.1
9.2.2 | | 9.2.1
9.2.2 | | 9.2.1
9.2.3 | | 9.2.1
9.2.4 | | +| OTA Base Station output power | - | 9.3.1
9.3.2.1
9.3.2.2
9.3.4.1
9.3.4.2
9.3.6.1
9.3.6.2 | - | 9.3.1
9.3.2.1
9.3.2.2
9.3.4.1
9.3.4.2 | - | 9.3.1
9.3.2.1
9.3.2.2
9.3.6.1
9.3.6.2 | - | 9.3.1
9.3.2.1
9.3.2.3
9.3.4.1
9.3.4.3 | - | 9.3.1
9.3.2.1
9.3.2.4
9.3.6.1
9.3.6.4 | +| OTA Output power dynamics | - | 9.4.1
9.4.2.1
9.4.2.2
9.4.3.1
9.4.3.2
9.4.4.1
9.4.4.2
9.4.6.1
9.4.6.2 | - | 9.4.1
9.4.2.1
9.4.2.2
9.4.3.1
9.4.3.2 | - | 9.4.1
9.4.4.1
9.4.4.2
9.4.6.1
9.4.6.2 | - | 9.4.1
9.4.2.1
9.4.2.3
9.4.3.1
9.4.3.3 | - | 9.4.1
9.4.4.1
9.4.4.4
9.4.6.1
9.4.6.4 | +| OTA Transmit ON/OFF power | - | 9.5 | - | 9.5 | - | 9.5 | - | 9.5 | - | 9.5 | +| OTA Transmitted signal quality | - | 9.6.1 | - | 9.6.1 | - | 9.6.1 | - | 9.6.1 | - | 9.6.1 | +| OTA Frequency Error | - | 9.6.2.1
9.6.2.2 | - | 9.6.2.1
9.6.2.2 | - | 9.6.2.1
9.6.2.2 | - | 9.6.2.1
9.6.2.3 | - | 9.6.2.1
9.6.2.4 | + +| | | | | | | | | | | | +|----------------------------------------------------------|------------------|--------------------|------------------|--------------------|------------------|--------------------|------------------|--------------------|------------------|--------------------| +| OTA Time alignment error | - | 9.6.3.1
9.6.3.2 | - | 9.6.3.1
9.6.3.2 | - | 9.6.3.1
9.6.3.2 | - | 9.6.3.1
9.6.3.3 | - | 9.6.3.1
9.6.3.4 | +| OTA modulation quality | - | 9.6.4.1
9.6.4.2 | - | 9.6.4.1
9.6.4.2 | - | 9.6.4.1
9.6.4.2 | - | 9.6.4.1
9.6.4.3 | - | 9.6.4.1
9.6.4.4 | +| OTA Transmit pulse shape filter | - | 9.6.5.1
9.6.5.2 | - | 9.6.5.1
9.6.5.2 | - | - | - | 9.6.5.1
9.6.5.3 | - | - | +| OTA Unwanted Emissions | - | 9.7.1 | - | 9.7.1 | - | 9.7.1 | - | 9.7.1 | - | 9.7.1 | +| OTA Occupied bandwidth | - | 9.7.2.1
9.7.2.2 | - | 9.7.2.1
9.7.2.2 | - | 9.7.2.1
9.7.2.2 | - | 9.7.2.1
9.7.2.3 | - | 9.7.2.1
9.7.2.4 | +| OTA Adjacent Channel Leakage power Ratio | - | 9.7.3.1
9.7.3.2 | - | 9.7.3.1
9.7.3.2 | - | 9.7.3.1
9.7.3.2 | - | 9.7.3.1
9.7.3.3 | - | 9.7.3.1
9.7.3.4 | +| OTA Spectrum emission mask | - | - | - | - | - | - | - | 9.7.4.1
9.7.4.3 | - | - | +| OTA Operating band unwanted emission | - | 9.7.5.1
9.7.5.2 | - | 9.7.5.1
9.7.5.2 | - | 9.7.5.1
9.7.5.2 | - | - | - | 9.7.5.1
9.7.5.4 | +| OTA Spurious emission | - | 9.7.6.1
9.7.6.2 | - | 9.7.6.1
9.7.6.2 | - | 9.7.6.1
9.7.6.2 | - | 9.7.6.1
9.7.6.3 | - | 9.7.6.1
9.7.6.4 | +| OTA Transmitter intermodulation | - | 9.8.1
9.8.2 | - | 9.8.1
9.8.2 | - | 9.8.1
9.8.2 | - | 9.8.1
9.8.3 | - | 9.8.1
9.8.4 | +| OTA sensitivity | 10.2.1
10.2.2 | | 10.2.1
10.2.2 | | 10.2.1
10.2.2 | | 10.2.1
10.2.3 | | 10.2.1
10.2.4 | | +| OTA Reference sensitivity level | - | 10.3.1
10.3.2 | - | 10.3.1
10.3.2 | - | 10.3.1
10.3.2 | - | 10.3.1
10.3.3 | - | 10.3.1
10.3.4 | +| OTA Dynamic range | - | 10.4.1
10.4.2 | - | 10.4.1
10.4.2 | - | 10.4.1
10.4.2 | - | 10.4.1
10.4.3 | - | 10.4.1
10.4.4 | +| OTA Adjacent channel selectivity and narrowband blocking | - | 10.5.1
10.5.2 | - | 10.5.1
10.5.2 | - | 10.5.1
10.5.2 | - | 10.5.1
10.5.3 | - | 10.5.1
10.5.4 | +| OTA Blocking | - | 10.6.1
10.6.2 | - | 10.6.1
10.6.2 | - | 10.6.1
10.6.2 | - | 10.6.1
10.6.3 | - | 10.6.1
10.6.4 | +| OTA Receiver spurious emissions | - | 10.7.1
10.7.2 | - | 10.7.1
10.7.2 | - | 10.7.1
10.7.2 | - | 10.7.1
10.7.3 | - | 10.7.1
10.7.4 | +| OTA Receiver intermodulation | - | 10.8.1
10.8.2 | - | 10.8.1
10.8.2 | - | 10.8.1
10.8.2 | - | 10.8.1
10.8.3 | - | 10.8.1
10.8.4 | +| OTA In-channel selectivity | - | 10.9.1
10.9.2 | - | - | - | 10.9.1
10.9.2 | - | - | - | 10.9.1
10.9.4 | + +NOTE: For some requirements, the requirement is defined by reference to the respective *non-AAS BS*. These requirements cannot be identified from this table. + +## 6 Conducted transmitter characteristics + +### 6.1 General + +Unless otherwise stated, the transmitter characteristics are specified with a full complement of transceiver units for the configuration in normal operating conditions. + +The manufacturer shall declare the minimum number of supported geographical cells (i.e. geographical areas). The minimum number of supported geographical cells ( $N_{\text{cells}}$ ) relates to the AAS BS setting with the minimum amount of cell splitting supported with transmission on all *TAB connectors* supporting the operating band. The manufacturer shall also declare *TAB connector TX min cell groups*. Every *TAB connector* supporting transmission in an operating band + +shall map to one *TAB connector TX min cell group* supporting the same operating band. The mapping of *TAB connectors* to cells is implementation dependent. + +The number of *active transmitter units* that are considered when calculating the emissions limit ( $N_{TXU, counted}$ ) for an AAS BS is calculated as follows: + +$$N_{TXU, counted} = \min(N_{TXU, active}, 8 \times N_{cells}) \text{ for AAS BS in } \textit{single RAT E-UTRA operation} \text{ and MSR AAS BS (except UTRA only MSR AAS BS)}$$ + +and + +$$N_{TXU, counted} = \min(N_{TXU, active}, 4 \times N_{cells}) \text{ for AAS BS in } \textit{single RAT UTRA operation} \text{ and UTRA only MSR AAS BS}$$ + +Further: + +$$N_{TXU, countedpercell} = N_{TXU, counted} / N_{cells}$$ + +$N_{TXU, countedpercell}$ is used for scaling the *basic limits* as described in subclause 6.6. + +NOTE: $N_{TXU, active}$ depends on the actual number of *active transmitter units* and is independent to the declaration of $N_{cells}$ . + +Any transmitter requirement specified for NB-IoT in-band, NB-IoT guard band, or standalone NB-IoT operation in 3GPP TS 36.104 [4] for E-UTRA with NB-IoT (in-band or guard band) or for standalone NB-IoT, or in 3GPP TS 37.104 [5] for E-UTRA with NB-IoT or standalone NB-IoT in *MSR operation*, and referred in clause 6, is not applicable for AAS BS. + +Any transmitter requirement specified for Band 46 operation or for Band 49 operation in 3GPP TS 36.104 [4] for E-UTRA, or in 3GPP TS 37.104 [5] for E-UTRA in *MSR operation*, and referred in clause 6, is not applicable for AAS BS. + +## 6.2 Base station output power + +### 6.2.1 General + +The configured carrier power is the target maximum power for a specific carrier for the operating mode set in the BS within the limits given by the manufacturer's declaration. + +### 6.2.2 Maximum output power + +#### 6.2.2.1 General + +The rated carrier output power of the AAS BS shall be as specified in table 6.2.2.1-1. + +**Table 6.2.2.1-1: AAS BS rated output power limits for BS classes** + +| AAS BS class | $P_{Rated,c,sys}$ | $P_{Rated,c,TABC}$ | +|--------------------------------------------------------------------------------------------------------------|---------------------------------------------------|-----------------------| +| Wide Area BS | (NOTE) | (NOTE) | +| Medium Range BS | $\leq 38 \text{ dBm} + 10 \log(N_{TXU, counted})$ | $\leq 38 \text{ dBm}$ | +| Local Area BS | $\leq 24 \text{ dBm} + 10 \log(N_{TXU, counted})$ | $\leq 24 \text{ dBm}$ | +| NOTE: There is no upper limit for the $P_{Rated,c,sys}$ or $P_{Rated,c,TABC}$ of the Wide Area Base Station. | | | + +#### 6.2.2.2 Minimum requirement for MSR operation + +##### 6.2.2.2.1 General + +In normal conditions, $P_{max,c,TABC}$ shall remain within +2 dB and -2 dB of the configured carrier power for each *TAB connector* as declared by the manufacturer. + +In extreme conditions, $P_{\max,c,TABC}$ shall remain within +2,5 dB and -2,5 dB of the configured carrier power for each *TAB connector* as declared by the manufacturer. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +#### 6.2.2.2.2 Additional requirements (regional) + +#### 6.2.2.3 Minimum requirement for single RAT UTRA operation + +The minimum requirement for single RAT UTRA BS is the same as that defined in subclause 6.2.2.2. + +#### 6.2.2.4 Minimum requirement for single RAT E-UTRA operation + +##### 6.2.2.4.1 General + +The minimum requirement for single RAT E-UTRA BS is the same as that defined in subclause 6.2.2.2. + +##### 6.2.2.4.2 Additional requirements (regional) + +### 6.2.3 UTRA FDD primary CPICH power + +#### 6.2.3.1 General + +This requirement applies to the *TAB connector* group(s) transmitting primary CPICH. + +Primary CPICH (P-CPICH) power is the *code domain power* of the Primary Common Pilot Channel summed over the *TAB connectors* transmitting the P-CPICH for a cell. P-CPICH power is indicated on the BCH. + +NOTE 1: A *TAB connector* group may comprise all *TAB connectors*. + +NOTE 2: A *TAB connector* may be mapped to several groups. + +NOTE 3: The manufacturer declares the *TAB connector* mapping to the P-CPICH transmission group(s) as specified in TS 37.145-1 [29] or TS 37.145-2 [30]. + +#### 6.2.3.2 Minimum requirement for MSR operation + +The minimum requirement for MSR UTRA FDD operation is the same as that defined in subclause 6.2.3.3. There is no CPICH power requirement for UTRA TDD 1,28 Mcps operation. + +There is no CPICH power requirement for E-UTRA operation. + +There is no CPICH power requirement for NR operation. + +#### 6.2.3.3 Minimum requirement for single RAT UTRA operation + +The difference between the P-CPICH power and the P-CPICH power indicated on the BCH shall be within $\pm 2,1$ dB. + +Alternatively, the P-CPICH power measured at each *TAB connector* shall be within $\pm 2,1$ dB of the P-CPICH power level indicated on the BCH multiplied by a *TAB connector* specific beamforming weight. Beamforming weights on P-CPICH are set by the AAS BS to achieve an intended radiated pattern. + +There is no P-CPICH power requirement for UTRA TDD 1,28 Mcps operation. + +#### 6.2.3.4 Minimum requirement for single RAT E-UTRA operation + +There is no CPICH power requirement for E-UTRA *AAS BS*. + +## 6.2.4 UTRA TDD primary CCPCH power + +### 6.2.4.1 General + +This requirement applies to the *TAB connector* group(s) transmitting primary CCPCH. It comprises primary CCPCH (PCCPCH) absolute power accuracy, and differential accuracy. + +Primary CCPCH power is the *code domain power* of the primary common control physical channel averaged over the transmit timeslot and summed over the *TAB connectors* transmitting the PCCPCH for a cell. Primary CCPCH power is signalled over the BCH. + +The differential accuracy of the Primary CCPCH power is the relative transmitted power accuracy of PCCPCH in consecutive frames when the nominal PCCPCH power is not changed. + +NOTE 1: A *TAB connector* group may comprise all *TAB connectors*. + +NOTE 2: A *TAB connector* may be mapped to several groups. + +NOTE 3: The manufacturer declares the *TAB connector* mapping to the PCCPCH transmission group(s). + +### 6.2.4.2 Minimum requirement for MSR operation + +The minimum requirement for MSR UTRA TDD 1,28 Mcps operation is the same as that defined in subclause 6.2.4.3. + +There is no CCPCH power requirement for UTRA FDD operation. + +There is no CCPCH power requirement for E-UTRA operation. + +There is no CCPCH power requirement for NR operation. + +### 6.2.4.3 Minimum requirement for single RAT UTRA operation + +For UTRA TDD 1,28 Mcps operation, the difference between the BCH-broadcast value of the Primary CCPCH power and the Primary CCPCH power averaged over the timeslot shall not exceed the values in table 6.2.4.3-1. The requirement is a function of the output power from the *TAB connector* group transmitting PCCPCH averaged over the transmit timeslot, $P_{out}$ , and the manufacturer's rated total power of the group, $P_{rated,t,group}$ . + +**Table 6.2.4.3-1: Difference between Primary CCPCH power and the broadcast value** + +| Output power in slot (dB) | PCCPCH power tolerance | +|-------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| $P_{rated,t,group} - 3 < P_{out} \leq P_{rated,t,group} + 2$ | $\pm 2,5$ dB | +| $P_{rated,t,group} - 6 < P_{out} \leq P_{rated,t,group} - 3$ | $\pm 3,5$ dB | +| $P_{rated,t,group} - 13 < P_{out} \leq P_{rated,t,group} - 6$ | $\pm 5$ dB | +| NOTE: $P_{rated,t,group}$ is the power sum of $P_{rated,t,TABC}$ of all the TAB connectors in the group transmitting PCCPCH. | | + +The differential accuracy of PCCPCH power shall be within $\pm 0,5$ dB. + +Alternatively, the PCCPCH power measured at each *TAB connector* and averaged over the timeslot shall be within the tolerance indicated in table 6.2.4.3-1 of the PCCPCH power level indicated on the BCH that is multiplied by a *TAB connector* specific beamforming weight. Beamforming weights on PCCPCH are set by the AAS BS to achieve an intended radiated pattern. + +In this case, the differential accuracy of PCCPCH power shall be within $\pm 0,5$ dB on each *TAB connector* in the *TAB connector* group. + +There is no PCCPCH power requirement for UTRA FDD operation. + +### 6.2.4.4 Minimum requirement for single RAT E-UTRA operation + +There is no CCPCH power requirement for E-UTRA operation. + +## 6.2.5 UTRA FDD additional CPICH power for MIMO mode + +### 6.2.5.1 General + +This clause includes requirements on secondary CPICH power level, for two and four *TAB connector* groups, as well as Demodulation CPICH requirements. The requirements apply to all *TAB connector* groups associated with UTRA FDD MIMO transmission as "antenna 2", "antenna 3" or "antenna 4" in the *AAS BS*. + +The concept of "antenna 2", "antenna 3" and "antenna 4" is described in 3GPP TS 25.104 [2]. The group(s) of *TAB connectors* mapped to P-CPICH transmission represents "antenna 1". + +NOTE 1: The manufacturer declares the mapping of *TAB connectors* to "antenna 1", "antenna 2", "antenna 3" and "antenna 4" (as defined in 3GPP TS 25.331 [16]) where applicable for AAS BS capable of UTRA FDD operation. The required declarations are specified in TS 37.145-1 [29] and TS 37.145-2 [30]. + +For UTRA FDD *AAS BS* operating only "antenna 1" and "antenna 2", the secondary CPICH (S-CPICH) power is the *code domain power* of the Secondary Common Pilot Channel. S-CPICH power is equal to the (dB) sum of the P-CPICH power and the power offset, which are signalled to the UE. The power offset is signalled in the IE "Power Offset for S-CPICH for MIMO", for MIMO mode as defined in clause 10.3.6.41b in 3GPP TS 25.331 [16]. + +When the UE supports MIMO mode with four BS transmit antennas, the power offset of S-CPICH on antenna 2 is signalled in the IE "Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna2" as defined in subclause 10.3.6.143 in 3GPP TS 25.331 [16]. The power offset of S-CPICH on antenna 3 and 4 is signalled in the IE "Common Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4", as defined in subclause 10.3.6.143 in 3GPP TS 25.331 [16]. + +Demodulation CPICH (D-CPICH) power is the *code domain power* of the Demodulation Common Pilot Channel. D-CPICH power is equal to the (dB) sum of the P-CPICH power and the power offset, which are signalled to the UE. The power offset of D-CPICH on antenna 3 and 4 is signalled in the IE "Common Power Offset for D-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4", as defined in subclause 10.3.6.143 in 3GPP TS 25.331 [16]. + +NOTE 2: The accuracy level of the power offset for S-CPICH may affect both MIMO HS-DSCH demodulation and CQI reporting performance. + +NOTE 3: The accuracy level of the power offset for D-CPICH transmitted on antennas 3 and 4 may affect both MIMO HS-DSCH demodulation and CQI reporting performance. + +NOTE 4: At high geometry level PDSCH performance may be affected if D-CPICH is not scheduled. + +NOTE 5: A *TAB connector* group may comprise all *TAB connectors*. + +NOTE 6: A *TAB connector* may be mapped to several groups. + +### 6.2.5.2 Minimum requirement for MSR operation + +The minimum requirements for MSR UTRA FDD operation are the same as those defined in subclause 6.2.5.3. + +There is no CPICH power requirement for UTRA TDD 1,28 Mcps operation. + +There is no CPICH power requirement for E-UTRA operation. + +There is no CPICH power requirement for NR operation. + +### 6.2.5.3 Minimum requirement for single RAT UTRA operation + +When operating MIMO only "antenna 1" and "antenna 2"; + +The difference between the P-CPICH power transmitted at the group of *TAB connectors* mapped to "antenna 1", and the S-CPICH power transmitted at the corresponding group of *TAB connectors* mapped to "antenna 2" shall be within $\pm 2$ dB of the IE "Power Offset for S-CPICH for MIMO". + +Alternatively, the measured power of the P-CPICH mapped to "antenna 1" and the measured power of the S-CPICH mapped to "antenna 2" at each *TAB connector* shall be within 2 dB of the corresponding IE "Power Offset for S-CPICH for MIMO" that is multiplied by a *TAB connector* specific beamforming weight and the P-CPICH power level indicated on the BCH. The same beamforming weights applied to P-CPICH and S-CPICH are set by the AAS BS to achieve an intended radiated pattern. + +When operating MIMO "antenna 1", "antenna 2", "antenna 3", and "antenna 4". + +The difference between the P-CPICH power transmitted at the group of *TAB connectors* mapped to "antenna 1", and the S-CPICH power transmitted at the corresponding group of *TAB connectors* mapped to "antenna 2" shall be within $\pm 2$ dB of the IE "Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna2". + +The difference between the P-CPICH power transmitted at the group of *TAB connectors* mapped to "antenna 1" and the S-CPICH power transmitted at the corresponding groups of *TAB connectors* mapped to "antenna 3" and "antenna 4" respectively, shall be within $\pm 2$ dB of the IE "Common Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4". + +Alternatively, the measured power of the P-CPICH mapped to "antenna 1" and the measured power of the S-CPICH mapped to "antenna 2" at each *TAB connector* shall be within $\pm 2$ dB of the corresponding IE "Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna2" that is multiplied by a *TAB connector* specific beamforming weight and the P-CPICH power level indicated on the BCH. The measured power of the P-CPICH mapped to "antenna 1" and the measured power of the S-CPICH mapped to "antenna 3" and "antenna 4", respectively, at each *TAB connector* shall be within $\pm 2$ dB of the corresponding IE "Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4" that is multiplied by a *TAB connector* specific beamforming weight and the P-CPICH power level indicated on the BCH. The same beamforming weights applied to P-CPICH and S-CPICH are set by the AAS BS to achieve an intended radiated pattern. + +If D-CPICH is scheduled: + +The difference between the P-CPICH power transmitted at the group of *TAB connectors* mapped to "antenna 1" and the D-CPICH power transmitted at the corresponding groups of *TAB connectors* mapped to "antenna 3" and "antenna 4" respectively, shall be within $\pm 2$ dB of the IE "Common Power Offset for D-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4". + +Alternatively, the measured power of the P-CPICH mapped to "antenna 1" and the measured power of the D-CPICH mapped to "antenna 3" and "antenna 4", respectively, at each *TAB connector* shall be within $\pm 2$ dB of the corresponding IE "Common Power Offset for D-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4" that is multiplied by a *TAB connector* specific beamforming weight and the P-CPICH power level indicated on the BCH. The same beamforming weights applied to P-CPICH and D-CPICH are set by the AAS BS to achieve an intended radiated pattern. + +There is no CPICH power requirement for UTRA TDD 1,28 Mcps operation. + +#### 6.2.5.4 Minimum requirement for single RAT E-UTRA operation + +There is no CPICH power requirement for E-UTRA *AAS BS*. + +### 6.2.6 E-UTRA DL RS power + +#### 6.2.6.1 General + +This requirement applies to the *TAB connector* group(s) transmitting primary DL RS. + +The DL RS power is the resource element power of the Downlink Reference Symbol summed over the group of *TAB connectors* transmitting the DL RS for a cell. + +The absolute DL RS power is indicated on the DL-SCH. The absolute accuracy is defined as the maximum deviation between the DL RS power indicated on the DL-SCH and the DL RS power of each E-UTRA carrier. + +NOTE 1: A *TAB connector* group may comprise all *TAB connectors*. + +NOTE 2: A *TAB connector* may be mapped to several groups. + +NOTE 3: The manufacturer declares the *TAB connector* mapping to the DL RS transmission group(s). + +#### 6.2.6.2 Minimum requirement for MSR operation + +There is no DL RS power requirement for UTRA operation. + +There is no DL RS power requirement for NR operation. + +The minimum requirement for MSR E-UTRA operation is the same as that defined in subclause 6.2.6.4. + +#### 6.2.6.3 Minimum requirement for single RAT UTRA operation + +There is no DL RS power requirement for UTRA operation. + +#### 6.2.6.4 Minimum requirement for single RAT E-UTRA operation + +The DL RS power of each E-UTRA carrier shall be within $\pm 2,1$ dB of the DL RS power indicated on the DL-SCH. + +Alternatively, the DL RS power measured at each *TAB connector* shall be within $\pm 2,1$ dB of the DL RS power level indicated on the DL-SCH multiplied by a *TAB connector* specific beamforming weight. Beamforming weights on P-CPICH are set by the AAS BS to achieve an intended radiated pattern. + +### 6.3 Output power dynamics + +#### 6.3.1 General + +The requirements in subclause 6.3 apply during the *transmitter ON period*. Transmit signal quality (as specified in subclause 6.5) shall be maintained for the output power dynamics requirements. + +#### 6.3.2 UTRA Inner loop power control in the downlink + +##### 6.3.2.1 General + +Inner loop power control in the downlink is the ability of the AAS BS to adjust the transmitted output power of a code channel in accordance with the corresponding TPC commands received in the uplink. + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +##### 6.3.2.2 Minimum requirement for MSR operation + +For UTRA FDD operation the minimum requirements for MSR AAS BS inner loop power control in the DL are the same as in subclause 6.3.2.3. + +For UTRA TDD 1,28 Mcps operation the minimum requirements for MSR AAS BS inner loop power control in the DL are the same as in 3GPP TS 25.105 [7], subclause 6.4.2.1. + +This requirement does not apply to E-UTRA or NR operation. + +##### 6.3.2.3 Minimum requirement for single RAT UTRA operation + +For UTRA FDD operation, the Single RAT AAS BS shall have the capability of setting the inner loop *code domain power* on each *TAB connector* with a step sizes of 1dB mandatory and 0.5, 1.5, 2.0 dB optional. + +- The tolerance of the power control step due to inner loop power control shall be within the range shown in table 6.3.2.3-1. +- The tolerance of the combined output power change due to inner loop power control shall be within the range shown in table 6.3.2.3-2. + +**Table 6.3.2.3-1: UTRA FDD TAB connector power control step tolerance** + +| Power control commands in the down link | Transmitter power control step tolerance | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------|-------------------------|----------|----------------|---------|-------------------------|----------| +| | 2 dB step size (NOTE) | | 1,5 dB step size (NOTE) | | 1 dB step size | | 0,5 dB step size (NOTE) | | +| | Lower | Upper | Lower | Upper | Lower | Upper | Lower | Upper | +| Up (TPC command "1") | +1,0 dB | +3,0 dB | +0,75 dB | +2,25 dB | +0,5 dB | +1,5 dB | +0,25 dB | +0,75 dB | +| Down (TPC command "0") | -1,0 dB | -3,0 dB | -0,75 dB | -2,25 dB | -0,5 dB | -1,5 dB | -0,25 dB | -0,75 dB | +| NOTE: These requirements are optional for AAS BS in single RAT UTRA operation , or in MSR operation using UTRA FDD. | | | | | | | | | + +**Table 6.3.2.3-2: UTRA FDD TAB connector aggregated power control step range** + +| Power control commands in the down link | Transmitter aggregated power control step change after 10 consecutive equal commands (up or down) | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|--------|-------------------------|--------|----------------|--------|-------------------------|-------| +| | 2 dB step size (NOTE) | | 1,5 dB step size (NOTE) | | 1 dB step size | | 0,5 dB step size (NOTE) | | +| | Lower | Upper | Lower | Upper | Lower | Upper | Lower | Upper | +| Up (TPC command "1") | +16 dB | +24 dB | +12 dB | +18 dB | +8 dB | +12 dB | +4 dB | +6 dB | +| Down (TPC command "0") | -16 dB | -24 dB | -12 dB | -18 dB | -8 dB | -12 dB | -4 dB | -6 dB | +| NOTE: These requirements are optional for AAS BS in single RAT UTRA operation , or in MSR operation using UTRA FDD. | | | | | | | | | + +For UTRA TDD 1,28 Mcps operation; the minimum requirements for AAS BS in *single RAT UTRA operation* using TDD inner loop power control in the DL are the same as in 3GPP TS 25.105 [7], subclause 6.4.2.1. + +### 6.3.2.4 Minimum requirement for single RAT E-UTRA operation + +This requirement does not apply to E-UTRA operation. + +## 6.3.3 Power control dynamic range + +### 6.3.3.1 General + +The power control dynamic range is the difference between the maximum and the minimum *code domain power* of a code channel for a specified reference condition. + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +### 6.3.3.2 Minimum requirement for MSR operation + +For UTRA FDD operation the minimum requirements for MSR *AAS BS* power control dynamic range are the same as in 3GPP TS 25.104 [6], subclause 6.4.2.1. + +For UTRA TDD 1,28 Mcps operation the minimum requirement for MSR *AAS BS* power control dynamic range is the same as in 3GPP TS 25.105 [7], subclause 6.4.3.1. + +This requirement does not apply to E-UTRA or NR operation. + +### 6.3.3.3 Minimum requirement for single RAT UTRA operation + +For UTRA FDD operation the minimum requirements for single RAT *AAS BS* power control dynamic range are the same as in 3GPP TS 25.104 [6], subclause 6.4.2.1. + +For UTRA TDD 1,28 Mcps operation the minimum requirement for single RAT *AAS BS* power control dynamic range is the same as in 3GPP TS 25.105 [7], subclause 6.4.3.1. + +### 6.3.3.4 Minimum requirement for single RAT E-UTRA operation + +This requirement does not apply to E-UTRA operation. + +## 6.3.4 Total power dynamic range + +### 6.3.4.1 General + +The total power dynamic range is the difference between the maximum and the minimum output power for a specified reference condition. + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +NOTE 1: The upper limit of the dynamic range is the BS maximum output power ( $P_{\text{Rated,c,TABC}}$ ). The lower limit of the dynamic range is the lowest minimum power from the BS when no traffic channels are activated. + +Particularly for E-UTRA and NR, the total power dynamic range is the difference between the maximum and the minimum transmit power of an OFDM symbol for a specified reference condition. + +NOTE 2: The upper limit of the dynamic range at a *TAB connector* is the OFDM symbol power when transmitting on all RBs at maximum output power ( $P_{\text{Rated,c,TABC}}$ ). The lower limit of the dynamic range at a *TAB connector* is the OFDM symbol power when one resource block is transmitted. The OFDM symbol carries PDSCH or sPDSCH and not contain RS, PBCH or synchronization signals. + +### 6.3.4.2 Minimum requirement for MSR operation + +For UTRA FDD operation; the minimum requirements for MSR AAS BS total power dynamic range are the same as in 3GPP TS 25.104 [6], subclause 6.4.3.1. + +This requirement does not apply to UTRA TDD operation. + +For E-UTRA operation, the minimum requirements for MSR AAS BS total power dynamic range are the same as in 3GPP TS 36.104 [8], subclause 6.3.2.1. + +For NR operation, the minimum requirements for MSR AAS BS total power dynamic range are the same as those for *BS type 1-H* in 3GPP TS 38.104 [28], subclause 6.3.3.2. + +### 6.3.4.3 Minimum requirement for single RAT UTRA operation + +For UTRA FDD operation; the minimum requirements for single RAT AAS BS total power dynamic range are the same as in 3GPP TS 25.104 [6], subclause 6.4.3.1. + +This requirement does not apply to UTRA TDD operation. + +### 6.3.4.4 Minimum requirement for single RAT E-UTRA operation + +For E-UTRA operation; the minimum requirements for single RAT AAS BS total power dynamic range are the same as in 3GPP TS 36.104 [8], subclause 6.3.2.1. + +## 6.3.5 IPDL time mask + +### 6.3.5.1 General + +To support IPDL location method in UTRA FDD operation, the AAS BS shall interrupt all transmitted signals in the downlink (i.e. common and dedicated channels). The IPDL time mask specifies the limits of the *TAB connector* output power during these idle periods. + +This requirement applies only to AAS BS supporting IPDL. The requirement applies at each *TAB connector* supporting transmission in the operating band. + +### 6.3.5.2 Minimum requirement for MSR operation + +For UTRA FDD operation; the minimum requirement for MSR AAS BS IPDL time mask is the same as in 3GPP TS 25.104 [6], subclause 6.4.5.1. + +This requirement does not apply to UTRA TDD operation. + +This requirement does not apply to E-UTRA operation. + +This requirement does not apply to NR operation. + +### 6.3.5.3 Minimum requirement for single RAT UTRA operation + +For UTRA FDD operation; the minimum requirement for single RAT AAS BS IPDL time mask is the same as in 3GPP TS 25.104 [6], subclause 6.4.5.1. + +This requirement does not apply to UTRA TDD operation. + +### 6.3.5.4 Minimum requirement for single RAT E-UTRA operation + +This requirement does not apply to E-UTRA operation. + +## 6.3.6 RE Power control dynamic range + +### 6.3.6.1 General + +The RE power control dynamic range is the difference between the power of an RE and the average RE power for a BS at maximum output power ( $P_{\text{Rated,c,TABC}}$ ) for a specified reference condition. + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +### 6.3.6.2 Minimum requirement for MSR operation + +This requirement does not apply to UTRA operation. + +For E-UTRA operation; the minimum requirements for MSR AAS BS RE power control dynamic range are the same as in 3GPP TS 36.104 [8], subclause 6.3.1.1. + +For NR operation, the minimum requirements for MSR AAS BS RE power control dynamic range are the same as those for *BS type 1-H* in 3GPP TS 38.104 [28], subclause 6.3.2.2. + +### 6.3.6.3 Minimum requirement for single RAT UTRA operation + +This requirement does not apply to UTRA operation. + +### 6.3.6.4 Minimum requirement for single RAT E-UTRA operation + +For E-UTRA operation; the minimum requirements for single RAT AAS BS RE power control dynamic range are the same as in 3GPP TS 36.104 [8], subclause 6.3.1.1. + +## 6.4 Transmit ON/OFF power + +### 6.4.1 General + +Transmitter ON/OFF power requirements apply only to TDD operation of UTRA and E-UTRA. + +## 6.4.2 Transmitter OFF power + +### 6.4.2.1 General + +Transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *Base Station RF Bandwidth (s)* centred on the central frequency of the *Base Station RF Bandwidth (s)* during the *transmitter OFF period*. N is equal to 1 for UTRA and E\_UTRA SCS/15 for NR, where SCS is Sub Carrier Spacing in kHz. + +The requirement applies at each *TAB connector* supporting transmission in the operating band. + +For *multi-band TAB connectors* and for *single band TAB connectors* supporting transmission in multiple operating bands, the requirement is only applicable during the *transmitter OFF period* in all supported operating bands. + +For AAS BS supporting intra-band contiguous CA, the transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *Aggregated BS Channel Bandwidth* $BW_{\text{Channel\_CA}}$ centred on $(F_{\text{edge,high}} + F_{\text{edge,low}})/2$ during the *transmitter OFF period*. N is equal to 1 if there are any UTRA or E-UTRA carriers, or for NR $N = \text{SCS}/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *Aggregated BS Channel Bandwidth*. + +### 6.4.2.2 Minimum requirement for MSR operation + +The transmitter OFF power spectral density shall be less than -85 dBm/MHz. + +### 6.4.2.3 Minimum requirement for single RAT UTRA operation + +The minimum requirement for UTRA operation is the same as that defined in subclause 6.4.2.2. + +### 6.4.2.4 Minimum requirement for single RAT E-UTRA operation + +The minimum requirement for UTRA operation is the same as that defined in subclause 6.4.2.2. + +## 6.4.3 Transmitter transient period + +### 6.4.3.1 General + +The *transmitter transient period* is the time period during which the transmitter unit is changing from the OFF period to the ON period or vice versa. The *transmitter transient period* is illustrated in figure 6.4.3.1-1. + +![Figure 6.4.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two levels: 'ON power level (Informative)' and 'OFF power level'. The x-axis is divided into three main segments: 'UL Timeslots', 'Transmitter ON period (DL Timeslots and DwPTS)', and 'GP and UpPTS'. The 'Transmitter ON period' is the duration where the power is at the ON level. The 'Transmitter OFF period' is the duration where the power is at the OFF level. The 'Transmitter transient period' is the duration of the power transition between the ON and OFF levels.](068b3a3247570c4b78342a943f15de9e_img.jpg) + +Figure 6.4.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two levels: 'ON power level (Informative)' and 'OFF power level'. The x-axis is divided into three main segments: 'UL Timeslots', 'Transmitter ON period (DL Timeslots and DwPTS)', and 'GP and UpPTS'. The 'Transmitter ON period' is the duration where the power is at the ON level. The 'Transmitter OFF period' is the duration where the power is at the OFF level. The 'Transmitter transient period' is the duration of the power transition between the ON and OFF levels. + +**Figure 6.4.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period** + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +#### 6.4.3.2 Minimum requirement for MSR operation + +The minimum requirements for MSR *AAS BS transmitter transient period* are the same as in 3GPP TS 37.104 [9], subclause 6.4.2.1. + +#### 6.4.3.3 Minimum requirement for single RAT UTRA operation + +The minimum requirements for single RAT *AAS BS transmitter transient period* are the same as in 3GPP TS 25.105 [7], subclause 6.5.2.1.2. + +#### 6.4.3.4 Minimum requirement for single RAT E-UTRA operation + +The minimum requirements for single RAT *AAS BS transmitter transient period* are the same as in 3GPP TS 36.104 [8], subclause 6.4.2.1. + +### 6.5 Transmitted signal quality + +#### 6.5.1 General + +Unless otherwise stated, the requirements in clause 6.5 apply during the *transmitter ON period*. + +#### 6.5.2 Frequency Error + +##### 6.5.2.1 General + +This requirement applies per *TAB connector*. + +Frequency error is the measure of the difference between the actual AAS BS transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation. + +##### 6.5.2.2 Minimum requirement for MSR operation + +The minimum requirement for a UTRA frequency error is the same as defined in subclause 6.5.2.3. + +The minimum requirement for an E-UTRA frequency error is the same as defined in subclause 6.5.2.4. + +The minimum requirement for an NR frequency error is the same as those for *BS type 1-H* defined in 3GPP TS 38.104 [28] subclause 6.5.1.2. + +### 6.5.2.3 Minimum requirement for single RAT UTRA operation + +The single RAT UTRA FDD AAS BS of wide area BS class shall fulfil the frequency error minimum requirements for wide area BS described in 3GPP TS 25.104 [6], subclause 6.3.1. + +The single RAT UTRA FDD AAS BS of medium range BS class shall fulfil the frequency error minimum requirements for medium range BS described in 3GPP TS 25.104 [6], subclause 6.3.1. + +The single RAT UTRA FDD AAS BS of local area BS class shall fulfil the frequency error minimum requirements for local area BS described in 3GPP TS 25.104 [6], subclause 6.3.1. + +The single RAT UTRA TDD 1,28Mcps option AAS BS of wide area BS class shall fulfil the frequency error minimum requirements for wide area BS described in 3GPP TS 25.105 [7], subclause 6.3.1.2. + +The single RAT UTRA TDD 1,28Mcps option AAS BS of local area BS class shall fulfil the frequency error minimum requirements for local area BS described in 3GPP TS 25.105 [7], subclause 6.3.1.2. + +### 6.5.2.4 Minimum requirement for single RAT E-UTRA operation + +The single RAT E-UTRA AAS BS of wide area BS class shall fulfil the frequency error minimum requirements for wide area BS described in 3GPP TS 36.104 [8], subclause 6.5.1.1. + +The single RAT E-UTRA AAS BS of medium range BS class shall fulfil the frequency error minimum requirements for medium range BS described in 3GPP TS 36.104 [8], subclause 6.5.1.1. + +The single RAT E-UTRA AAS BS of local area BS class shall fulfil the frequency error minimum requirements for local area BS described in 3GPP TS 36.104 [8], subclause 6.5.1.1. + +## 6.5.3 Time alignment error + +### 6.5.3.1 General + +This requirement applies to frame timing in: + +- UTRA single/multi-carrier transmissions and their combinations with MIMO or TX diversity. +- E-UTRA single/multi-carrier transmissions and their combinations with MIMO or TX diversity. +- E-UTRA *carrier aggregation*, with or without MIMO or TX diversity. +- NR single/multi-carrier transmissions, and their combinations with MIMO. +- NR Carrier Aggregation, with or without MIMO. + +Frames of the WCDMA/LTE/NR signals present at the *TAB connectors* are not perfectly aligned in time. In relation to each other, the RF signals present at the *transceiver array boundary* may experience certain timing differences. + +For a specific set of signals/transmitter configuration/transmission mode, the Time Alignment Error (TAE) is defined as the largest timing difference between any two different LTE signals or any two different WCDMA signals or any two different NR signals belonging to different *TAB Connectors* belonging to different transmitter groups at the *transceiver array boundary*, where transmitter groups are associated with the *TAB connectors* in the transceiver unit array corresponding to TX diversity (except NR), MIMO transmission, *carrier aggregation*, etc. + +### 6.5.3.2 Minimum requirement for MSR operation + +The minimum requirement for a UTRA time alignment error is the same as defined in subclause 6.5.3.3. + +The minimum requirement for an E-UTRA time alignment error is the same as defined in subclause 6.5.3.4. + +The minimum requirement for an NR time alignment error is the same as those for *BS type 1-H* defined in 3GPP TS 38.104[28] in subclause 6.5.1.2. + +### 6.5.3.3 Minimum requirement for single RAT UTRA operation + +This requirement applies to frame timing in Tx diversity, MIMO transmission, DC-HSDPA, DB-DC-HSDPA, 4C-HSDPA, NC-4C-HSDPA, 8C-HSDPA and their combinations. + +The TAE between any two *TAB connectors* from different transmitter groups shall not exceed the specified minimum requirements below. + +For UTRA FDD, the minimum requirement for time alignment are the same as those in 3GPP TS 25.104 [6], subclause 6.8.4.1. + +For UTRA TDD, the minimum requirement for time alignment are the same as those in 3GPP TS 25.105 [7], subclause 6.8.5.1. + +### 6.5.3.4 Minimum requirement for single RAT E-UTRA operation + +This requirement applies to frame timing in TX diversity, MIMO transmission, *carrier aggregation* and their combinations. + +The TAE between any two *TAB connectors* from different transmitter groups shall not exceed the specified minimum requirements below. + +For E-UTRA, the minimum requirement for time alignment are the same as those in 3GPP TS 36.104 [8], subclause 6.5.3.1. + +## 6.5.4 Modulation quality + +### 6.5.4.1 General + +Modulation quality is defined by the difference between the measured carrier signal and an ideal signal. Modulation quality can be expressed e.g. as Peak Code domain Error (PCDE) or Relative Code domain Error (RCDE) or Error Vector Magnitude (EVM) for UTRA and Error Vector Magnitude (EVM) for E-UTRA. + +These requirements apply per *TAB connector*. + +### 6.5.4.2 Minimum requirement for MSR operation + +The minimum requirement for a UTRA modulation quality are defined in subclause 6.5.4.3. + +The minimum requirement for an E-UTRA modulation quality are defined in subclause 6.5.4.4. + +The minimum requirement for an NR modulation quality is defined as the same as those for *BS type 1-H* in 3GPP TS 38.104 [28] in subclause 6.5.2.2. + +### 6.5.4.3 Minimum requirement for single RAT UTRA operation + +The Error Vector Magnitude is a measure of the difference between the ideal waveform and the measured waveform. This difference is called the error vector. Both waveforms pass through a matched Root Raised Cosine filter to the considered chip rate and roll-off $\alpha=0.22$ . Both waveforms are then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing to minimize the error vector. The EVM result is defined as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. + +For UTRA FDD the measurement interval is one timeslot as defined by the C-PICH (when present) otherwise the measurement interval is one timeslot starting with the beginning of the SCH. The requirement is valid over the total power dynamic range as specified in subclause 6.3.4.3. The minimum requirements are the same as those in 3GPP TS 25.104 [6], subclause 6.8.2.1. + +For UTRA TDD the measurement interval is one timeslot. The requirement is valid over the total power dynamic range as specified in subclause 6.3.4.3. See annex C of 3GPP TS 25.142 [10] for further details. The minimum requirements are the same as those in 3GPP TS 25.105 [7], subclause 6.8.2.1. + +For UTRA FDD the Peak Code Domain Error is computed by projecting the error vector onto the code domain at a specified 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 ideal 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 timeslot as defined by the C-PICH (when present) otherwise the measurement interval is one timeslot starting with the beginning of the SCH. The minimum requirements are the same as those in 3GPP TS 25.104 [6], subclause 6.8.3.1. + +For UTRA FDD the Relative Code Domain Error is computed by projecting the error vector onto the code domain at a specified spreading factor. Only the active code channels in the composite ideal 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 ideal waveform. This ratio is expressed in dB. The measurement interval is one frame. The minimum requirements are the same as those in 3GPP TS 25.104 [6], subclause 6.8.5.1. + +For UTRA TDD 1,28Mcps option, the minimum requirements for modulation quality, PCDE and RCDE, are the same as in 3GPP TS 25.105 [7], subclauses 6.8.2, 6.8.3 and 6.8.4 respectively. The requirement for Relative Code Domain Error is only applicable for 64QAM modulated codes (UTRA FDD and UTRA TDD). + +#### 6.5.4.4 Minimum requirement for single RAT E-UTRA operation + +For E-UTRA, the minimum requirement for modulation quality, EVM, is specified in 3GPP TS 36.104 [8], subclause 6.5.2. + +### 6.5.5 Transmit pulse shape filter + +#### 6.5.5.1 General + +Transmit pulse shape filter for *single RAT UTRA operation* in FDD and for *MSR operation* in UTRA FDD is defined in 3GPP TS 25.104 [6] subclause 6.8.1. + +Transmit pulse shape filter for *single RAT UTRA operation* in TDD and for *MSR operation* in UTRA TDD is defined in 3GPP TS 25.105 [7] subclause 6.8.1. + +Transmit pulse shape filter is not defined for a *single RAT E-UTRA operation*, nor for *MSR operation* using E-UTRA and/or NR. + +#### 6.5.5.2 Void + +#### 6.5.5.3 Void + +#### 6.5.5.4 Void + +### 6.6 Unwanted Emissions + +#### 6.6.1 General + +Unwanted emissions consist of so-called out-of-band emissions and spurious emissions according to ITU definitions ITU-R SM.329 [14]. In ITU terminology, 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. 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. + +For AAS BS in *single RAT E-UTRA operation* and *MSR operation*, the out-of-band emissions requirement for the AAS BS transmitter is specified in terms of an operating band unwanted emissions requirement that defines limits for emissions in each supported *downlink operating band* plus the frequency ranges $\Delta f_{\text{OBUE}}$ above and $\Delta f_{\text{OBUE}}$ below each band, where $\Delta f_{\text{OBUE}}$ is the maximum offset of the operating band unwanted emission mask from the operating band edge. Emissions outside of this frequency range are limited by a spurious emissions requirement. For UTRA FDD single RAT AAS BS, the out of band emission requirement for AAS BS transmitter is specified in terms of spectrum emission mask requirement. + +The values of $\Delta f_{\text{OBUE}}$ are defined for *hybrid AAS BS* for E-UTRA and UTRA operating bands in Table 6.6.1-1. + +**Table 6.6.1-1: Maximum offset of OBUE outside the downlink operating band** + +| BS type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ [MHz] | +|----------------------|------------------------------------------------------------------------------------|--------------------------------| +| Hybrid AAS BS | $F_{\text{DL high}} - F_{\text{DL low}} < 100 \text{ MHz}$ | 10 | +| | $100 \text{ MHz} \leq F_{\text{DL high}} - F_{\text{DL low}} \leq 900 \text{ MHz}$ | 40 | + +The unwanted emission level limit of a *TAB connector TX min cell group* is in general defined by the unwanted emission *basic limit* which is the same as the corresponding applicable *non-AAS BS* per transmitter requirement specified in 3GPP TS 25.104 [2], 3GPP TS 25.105 [3], 3GPP TS 36.104 [4] or 3GPP TS 37.104 [5], and its scaling by $N_{\text{TXU, counted per cell}}$ . The unwanted emission requirements are applied per the *TAB connector TX min cell groups* for all the configurations supported by the AAS BS. The *basic limits* and corresponding scaling are defined in each relevant subclause. + +There is in addition a requirement for occupied bandwidth and an ACLR requirement. + +## 6.6.2 Occupied bandwidth + +### 6.6.2.1 General + +The occupied bandwidth is the width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage $\beta/2$ of the total mean transmitted power. See also Recommendation ITU-R SM.328 [17]. + +The value of $\beta/2$ shall be taken as 0.5%. + +The occupied bandwidth requirement applies during the *transmitter ON period* for a single transmitted carrier. The minimum requirement below may be applied regionally. There may also be regional requirements to declare the occupied bandwidth according to the definition in the present clause. + +### 6.6.2.2 Minimum requirement for MSR operation + +For MSR AAS BS, the minimum requirement for occupied bandwidth is the same as that stated in 3GPP TS 37.104 [9], subclause 6.6.3. + +### 6.6.2.3 Minimum requirement for single RAT UTRA operation + +For single RAT UTRA FDD AAS BS, the minimum requirement for occupied bandwidth is the same as that stated in 3GPP TS 25.104 [6] subclause 6.6.1. + +For single RAT UTRA TDD, 1,28Mcps option AAS BS, the minimum requirement for occupied bandwidth is the same as that stated in 3GPP TS 25.105 [7], subclause 6.6.1. + +### 6.6.2.4 Minimum requirement for single RAT E-UTRA operation + +For single RAT E-UTRA AAS BS, the minimum requirement for occupied bandwidth is the same as that stated in 3GPP TS 36.104 [8], subclause 6.6.1. + +## 6.6.3 Adjacent Channel Leakage power Ratio + +### 6.6.3.1 General + +Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. + +NOTE: Conformance to the AAS BS ACLR requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The ratio of the sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the assigned channel frequency to the sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the adjacent channel frequency shall be greater than or equal to the ACLR limit of AAS BS. This applies for each *TAB connector TX min cell group*. + +Or + +- 2) The ratio of the filtered mean power at the *TAB connector* centred on the assigned channel frequency to the filtered mean power at each *TAB connector* centred on the adjacent channel frequency shall be greater than or equal to the ACLR limit of AAS BS for every *TAB connector* in the *TAB connector TX min cell group*, for each *TAB connector TX min cell group*. + +In case the ACLR absolute limit of AAS BS is applied, the conformance can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the adjacent channel frequency shall be less than or equal to the ACLR absolute limit AAS BS. This applies to each *TAB connector TX min cell group*. + +Or + +- 2) The filtered mean power at each *TAB connector* centred on the adjacent channel frequency shall be less than or equal to the ACLR absolute limit of AAS BS scaled by $-10\log_{10}(n)$ for every *TAB connector* in the *TAB connector TX min cell group*, for each *TAB connector TX min cell group*, where *n* is the number of *TAB connectors* in the *TAB connector TX min cell group*. + +### 6.6.3.2 Minimum requirement for MSR operation + +For E-UTRA and/or NR MSR operation, the ACLR limits for AAS BS are the same as those specified in 3GPP TS 37.104 [9] subclauses 6.6.4.1. The *basic limits* are also the same as the absolute limits of MSR E-UTRA and/or NR operation specified in 3GPP TS 37.104 [9] subclauses 6.6.4.1. The ACLR absolute limit of AAS BS is specified as the *basic limit* + $10\log_{10}(N_{\text{TXU, counted per cell}})$ . The ACLR limit or the ACLR absolute limit of AAS BS, whichever is less stringent, shall apply outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. + +For UTRA FDD operation, the minimum requirement for ACLR are the same as those specified in 3GPP TS 25.104 [6], subclause 6.6.2.2, and applies outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. + +For UTRA TDD 1,28 Mcps operation, the minimum requirement for ACLR are the same as those specified in 3GPP TS 25.105 [7], subclause 6.6.2.2.1.2, and applies outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. + +For a *TAB connector* or *TAB connector cell group* supporting operation in *non-contiguous spectrum*, the ACLR requirement also applies for the first adjacent channel inside any *sub-block gap* with a gap size $W_{\text{gap}} \geq 15\text{MHz}$ . The ACLR requirement for the second adjacent channel applies inside any *sub-block gap* with a gap size $W_{\text{gap}} \geq 20\text{ MHz}$ . + +CACLR requirements apply in *sub-block gaps* as defined in 3GPP TS 37.104 [9], subclause 6.6.4.4. Either the CACLR limit or the ACLR absolute limit of AAS BS shall apply, whichever is less stringent. + +For a *multi-band TAB connector* or *TAB connector cell group* supporting operation in multiple operating bands through *multi-band TAB connectors*, the ACLR requirement also applies for the first adjacent channel inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 15\text{MHz}$ . The ACLR requirement for the second adjacent channel applies inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 20\text{ MHz}$ . + +CACLR requirements apply in *Inter RF Bandwidth gaps* as defined in 3GPP TS 37.104 [9], subclause 6.6.4.4. Either the CACLR limit or the ACLR absolute limit of AAS BS shall apply, whichever is less stringent. + +### 6.6.3.3 Minimum requirement for single RAT UTRA operation + +For single RAT UTRA FDD operation, the AAS BS ACLR minimum requirements are the same as those specified in 3GPP TS 25.104 [6], subclauses 6.6.2.2.1. + +For single RAT UTRA FDD operation, the AAS BS CACLR limits are the same as those specified in 3GPP TS 25.104 [6], subclauses 6.6.2.2.2. The *basic limits* are also the same as the absolute limits of UTRA specified in 3GPP TS 25.104 [6], subclauses 6.6.2.2.2. The ACLR (CACLR) absolute *basic limits* of AAS BS are specified as the *basic limit* + $10\log_{10}(N_{\text{TXU, counted per cell}})$ . The ACLR (CACLR) limit or the ACLR (CACLR) absolute *basic limit* of AAS BS shall apply, whichever is less stringent. + +For single RAT UTRA TDD 1,28 Mcps operation, the AAS BS minimum requirements are the same as those specified in 3GPP TS 25.105 [7], subclause 6.6.2.2. + +### 6.6.3.4 Minimum requirement for single RAT E-UTRA operation + +For *single RAT E-UTRA operation*, the AAS BS ACLR and CACLR limits are the same as those specified in 3GPP TS 36.104 [8], subclauses 6.6.2.1 and 6.6.2.2. The *basic limits* are also the same as the absolute limits of E-UTRA specified in 3GPP TS 36.104 [8], subclauses 6.6.2.1 and 6.6.2.2. The ACLR (CACLR) absolute *basic limits* of AAS BS are specified as the *basic limit* + $10\log_{10}(N_{\text{TXU, counted per cell}})$ . The ACLR (CACLR) limit or the ACLR (CACLR) absolute *basic limit* of AAS BS shall apply, whichever is less stringent. + +## 6.6.4 Spectrum emission mask + +### 6.6.4.1 General + +This requirement is applicable for single RAT UTRA AAS BS operation only. + +### 6.6.4.2 Minimum requirement for MSR operation + +There is no spectrum emission mask requirement for an MSR AAS BS. + +### 6.6.4.3 Minimum requirement for single RAT UTRA operation + +#### 6.6.4.3.1 General + +The spectrum emission mask requirements for a UTRA single RAT AAS BS are that for each applicable *basic limit* as specified in 3GPP TS 25.104 [2] or TS 25.105 [7], and for each *TAB connector TX min cell group* the power sum of emissions at the *TAB connectors* of the *TAB connector TX min cell group* shall not exceed an AAS BS limit specified as the *basic limits* + $10\log_{10}(N_{\text{TXU, counted per cell}})$ . + +NOTE: Conformance to the AAS BS spectrum emission mask requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the AAS limit as defined in this subclause for the respective frequency span. +- Or +- 2) The spectrum emission mask power at each *TAB connector* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span, scaled by $-10\log_{10}(n)$ , where *n* is the number of *TAB connectors* in the *TAB connector TX min cell group*. + +#### 6.6.4.3.2 Basic limits for single RAT UTRA FDD operation + +The *basic limit* is specified in tables 6.6.4.3.2-1 to 6.6.4.3.2-10 for the appropriate $P_{\text{Rated,c,sys}}$ , where: + +- $\Delta f$ is the separation between the carrier frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the carrier frequency and the centre of the measurement filter; +- $f\_offset_{max}$ is either 12.5 MHz or the offset to the UMTS Tx band edge as defined in clause 5.2, whichever is the greater. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +Inside any *Inter RF Bandwidth gaps* with $W_{gap} < 2 \times \Delta f_{OBUE}$ for a *multi-band TAB connector*, emissions shall not exceed the cumulative sum of the *basic limits* specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *basic limit* for *Base Station RF Bandwidth edge* is specified in tables 6.6.4.3.2-1 to 6.6.4.3.2-10 below, where in this case: + +- $\Delta f$ is equal to 2.5MHz plus the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the *Base Station RF Bandwidth edge*. +- $f\_offset$ is equal to 2.5MHz plus the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is either 12.5 MHz or the offset to the UMTS Tx band edge as defined in clause 5.2, whichever is the greater. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector*, the operating band unwanted emission *basic limits* apply also in a supported operating band without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported operating band. In this case, no cumulative limit is applied in the *inter-band gap* between a supported *downlink operating band* with carrier(s) transmitted and a supported *downlink operating band* without any carrier transmitted and + +- In case the *inter-band gap* between a downlink band with carrier(s) transmitted and a downlink band without any carrier transmitted is less than $2 \times \Delta f_{OBUE}$ , $f\_offset_{max}$ shall be the offset to the frequency $\Delta f_{OBUE}$ outside the outermost edges of the two *downlink operating bands* and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present subclause, shall apply across both downlink bands. +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present subclause for the largest frequency offset ( $\Delta f_{max}$ ), shall apply from $\Delta f_{OBUE}$ below the lowest frequency, up to $\Delta f_{OBUE}$ above the highest frequency of the *downlink operating band* without any carrier transmitted. + +Inside any *sub-block gap* for a *TAB connector* operating in *non-contiguous spectrum*, emissions shall not exceed the cumulative sum of the *basic limits* specified for the adjacent sub blocks on each side of the *sub-block gap*. The *basic limit* for each sub block is specified in tables 6.6.4.3.2-1 to 6.6.4.3.2-10 below, where in this case: + +- $\Delta f$ is equal to 2.5MHz plus the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f\_offset$ is equal to 2.5MHz plus the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter plus 2.5MHz. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring 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 2.5, 2.7, 3.5, 7.5, and Δf_max. The mask is defined by several power levels: P = 43 dBm (0 dBm on the right axis) for Δf > 7.5 MHz, P = 39 dBm (-10 dBm on the right axis) for 3.5 MHz < Δf < 7.5 MHz, and P = 31 dBm (-20 dBm on the right axis) for Δf < 3.5 MHz. The mask also shows a transition between 2.5 MHz and 3.5 MHz.](201de44da5d99899a8cf58eac2fa7bc9_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 2.5, 2.7, 3.5, 7.5, and Δf\_max. The mask is defined by several power levels: P = 43 dBm (0 dBm on the right axis) for Δf > 7.5 MHz, P = 39 dBm (-10 dBm on the right axis) for 3.5 MHz < Δf < 7.5 MHz, and P = 31 dBm (-20 dBm on the right axis) for Δf < 3.5 MHz. The mask also shows a transition between 2.5 MHz and 3.5 MHz. + +Illustrative diagram of spectrum emission mask + +Figure 6.6.4.3.2-1: Spectrum emission mask + +Table 6.6.4.3.2-1: Spectrum emission mask values, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) \geq 43 \text{ dBm}$ for UTRA FDD + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|----------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f_{\text{offset}} < 2.715 \text{ MHz}$ | -14 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f_{\text{offset}} < 3.515 \text{ MHz}$ | | 30 kHz | +| (NOTE 3) | $3.515 \text{ MHz} \leq f_{\text{offset}} < 4.0 \text{ MHz}$ | -26 dBm | 30 kHz | +| $3.5 \text{ MHz} < \Delta f < 7.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f_{\text{offset}} < 8.0 \text{ MHz}$ | -13 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offset,max}}$ | -13 dBm | 1 MHz | + +NOTE 1: For a TAB connector supporting non-contiguous spectrum operation the basic limit within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission basic limit s in clause 6.6.6.5.2.2 and 6.6.6.5.5.3 shall be met. + +NOTE 2: For a multi-band TAB connector with $\text{Inter RF Bandwidth gap} < 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or Base Station RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or Base Station RF Bandwidth. + +**Table 6.6.4.3.2-2: Spectrum emission mask values, $39 \text{ dBm} \leq P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 43 \text{ dBm}$ for UTRA FDD bands** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -14 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (NOTE 3) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -26 dBm | 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 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For a TAB connector supporting non-contiguous spectrum operation the basic limit within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission basic limit in clause 6.6.6.5.2.2 and 6.6.6.5.5.3 shall be met. + +NOTE 2: For a multi-band TAB connector with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the basic limit within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 6.6.4.3.2-3: Spectrum emission mask values, $31 \text{ dBm} \leq P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 39 \text{ dBm}$ for UTRA FDD bands** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|----------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 53 \text{ dB}$ | 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_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 53 \text{ dB} - 15 \cdot (f\_offset/\text{MHz} - 2.715) \text{ dB}$ | 30 kHz | +| (NOTE 3) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 65 \text{ dB}$ | 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_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 52 \text{ dB}$ | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For a TAB connector supporting non-contiguous spectrum operation the basic limit within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission basic limits in clause 6.6.6.5.2.2 and 6.6.6.5.5.3 shall be met. + +NOTE 2: For a multi-band TAB connector with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the basic limit within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 6.6.4.3.2-4: Spectrum emission mask values, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) < 31 \text{ dBm}$ for UTRA FDD bands** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|----------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f_{\text{offset}} < 2.715 \text{ MHz}$ | -22 dBm | 30 kHz | +| $2.7 \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f_{\text{offset}} < 3.515 \text{ MHz}$ | | 30 kHz | +| (NOTE 3) | $3.515 \text{ MHz} \leq f_{\text{offset}} < 4.0 \text{ MHz}$ | -34 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f < 7.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f_{\text{offset}} < 8.0 \text{ MHz}$ | -21 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offsetmax}}$ | -25 dBm | 1 MHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation the *basic limit* within *sub-block gaps* within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the spurious emission *basic limits* in clause 6.6.6.5.2.2 and 6.6.6.5.3 shall be met. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +For operation in band II, IV, V, X, XII, XIII, XIV, XXV and XXVI, the additional requirement in tables 6.6.4.3.2-5 to 6.6.4.3.2-7 apply in addition to the *basic limits* in tables 6.6.4.3.2-1 to 6.6.4.3.2-4. + +**Table 6.6.4.3.2-5: Additional spectrum emission *basic limits* for Bands II, IV, X, XXV** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Additional basic limit | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f_{\text{offset}} < 3.515 \text{ MHz}$ | -15 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $4.0 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offsetmax}}$ | -13 dBm | 1 MHz | + +**Table 6.6.4.3.2-6: Additional spectrum emission *basic limits* for Bands V, XXVI** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Additional basic limit | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f_{\text{offset}} < 3.515 \text{ MHz}$ | -15 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $3.55 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offsetmax}}$ | -13 dBm | 100 kHz | + +**Table 6.6.4.3.2-7: Additional spectrum emission *basic limits* for Bands XII, XIII, XIV** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Additional basic limit | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.6 \text{ MHz}$ | $2.515 \text{ MHz} \leq f_{\text{offset}} < 2.615 \text{ MHz}$ | -13 dBm | 30 kHz | +| $2.6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $2.65 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offsetmax}}$ | -13 dBm | 100 kHz | + +In certain regions the following requirement may apply for protection of DTT. For a *TAB connector* operating in Band XX, the level of emissions in the band 470-790 MHz, measured in an 8MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to table 6.6.4.3.2-8, shall not exceed the maximum emission *basic limit* $P_{\text{EM,N}}$ declared by the manufacturer. + +**Table 6.6.4.3.2-8: Declared emissions levels for protection of DTT** + +| Filter centre frequency, $F_{\text{filter}}$ | Measurement bandwidth | Declared emission basic limit [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 BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The *basic limit* defined above provides the characteristics of the AAS base station needed to verify compliance with the regional requirement. Compliance with the regional requirement for protection of DTT can be determined using the method outlined in annex D of 3GPP TS 25.104 [2]. + +In certain regions, the following *basic limits* may apply to a *TAB connector* operating in Band XXXII within 1452-1492 MHz. The level of unwanted emissions, measured on centre frequencies $f_{\text{offset}}$ with filter bandwidth, according to table 6.6.4.3.2-9, shall neither exceed the maximum emission *basic limit* $P_{\text{EM,B32,a}}$ , $P_{\text{EM,B32,b}}$ nor $P_{\text{EM,B32,c}}$ declared by the manufacturer. + +**Table 6.6.4.3.2-9: Declared frequency band XXXII unwanted emission within 1452-1492 MHz** + +| Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Declared emission basic limit [dBm] | Measurement bandwidth | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-----------------------| +| 5 MHz | $P_{\text{EM,B32,a}}$ | 5 MHz | +| 10 MHz | $P_{\text{EM,B32,b}}$ | 5 MHz | +| $15 \text{ MHz} \leq f_{\text{offset}} \leq f_{\text{offset,max,B32}}$ | $P_{\text{EM,B32,c}}$ | 5 MHz | +| NOTE: $f_{\text{offset,max,B32}}$ denotes the frequency difference between the lower channel carrier frequency and 1454.5 MHz, and the frequency difference between the upper channel carrier frequency and 1489.5 MHz for the set channel position. | | | + +NOTE: The regional requirement, included in CEPT ECC Decision (13)03 [25], is defined in terms of EIRP per antenna, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The *basic limit* defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in annex H of 3GPP TS 36.104 [4]. + +In certain regions, the following *basic limit* may apply to *TAB connector* operating in Band XXXII within 1452-1492MHz for the protection of services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to table 6.6.4.3.2-10, shall neither exceed the maximum emission *basic limit* $P_{\text{EM,B32,d}}$ nor $P_{\text{EM,B32,e}}$ declared by the manufacturer. This requirement applies in the frequency range 1429-1518MHz even though part of the range falls in the spurious domain. + +**Table 6.6.4.3.2-10: Frequency band XXXII declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission level [dBm] | Measurement bandwidth | +|---------------------------------------------------------------------|-------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{\text{filter}} \leq 1448.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | +| $F_{\text{filter}} = 1450.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $F_{\text{filter}} = 1493.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{\text{filter}} \leq 1517.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | + +NOTE: The regional requirement, included in CEPT ECC Decision (13)03 [25], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The *basic limit* defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in annex H of 3GPP TS 36.104 [4]. + +Notes for the tables in this subclause: + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 4: 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. + +### 6.6.4.3.3 Basic limits for single RAT UTRA TDD 1,28Mcps operation + +The *basic limit* is specified in tables 6.6.4.3.3-1 to 6.6.4.3.3-3 for the appropriate $P_{\text{Rated,c,sys}}$ , where: + +The mask defined in table 6.6.4.3.3-1 to 6.6.4.3.3-3 may be mandatory in certain regions. In other regions this mask may not be applied. + +For regions where this clause applies, the *basic limit* is for a *TAB connector* transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall use the *basic limits* specified in table 6.6.4.3.3-1 to 6.6.4.3.3-3 for the appropriate $P_{\text{rated,c,cell}}$ , in the frequency range from $\Delta f = 0.8$ MHz to $\Delta f_{\text{max}}$ from the carrier frequency, where: + +- $\Delta f$ is the separation between the carrier frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the carrier frequency and the centre frequency of the measuring filter. - $f\_offset_{\text{max}}$ is either 4 MHz or the offset to the UTRA TDD Tx band edge as defined in subclause 4.6, whichever is the greater. +- $\Delta f_{\text{max}}$ is equal to $f\_offset_{\text{max}}$ minus half of the bandwidth of the measurement filter. Inside any *Inter RF bandwidth gaps* with $W_{\text{gap}} < 8$ MHz for *multi-band TAB connector*, emissions shall not exceed the cumulative sum of the *basic limits* specified at the *Base Station RF bandwidth edges* on each side of *Inter RF bandwidth gap*. The *basic limit* for *Base Station RF bandwidth edge* is specified in tables 6.6.4.3.3-1 to 6.6.4.3.3-3 below, where in this case. +- $\Delta f$ equal to 0.8MHz plus the separation between the *Base Station RF bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the *Base Station RF bandwidth edge*. +- $f\_offset$ is equal to 0.8MHz plus the separation between the *Base Station RF bandwidth edge* frequency and the centre frequency of the measuring filter. +- $f\_offset_{\text{max}}$ is either 4 MHz or the offset to the UTRA TDD Tx band edge as defined in subclause 4.6, whichever is the greater. +- $\Delta f_{\text{max}}$ is equal to $f\_offset_{\text{max}}$ minus half of the bandwidth of the measurement filter. + +For a multi-carrier *TAB connector*, the definitions above apply to the lower edge of the carrier transmitted at the lowest carrier frequency and the upper edge of the carrier transmitted at the highest carrier frequency within a specified frequency. + +![Illustrative diagram of spectrum emission mask. The graph shows power density in 30 kHz [dBm] on the left y-axis (ranging from -45 to -20) and power density in 1 MHz [dBm] on the right y-axis (ranging from -30 to -5). The x-axis represents frequency separation Δf from the carrier [MHz] with markers at 0.8, 1.0, 1.8, 2.4, and Δf_max. The mask is defined by two lines: P = 34 dBm (upper limit) and P = 26 dBm (lower limit). The mask starts at -20 dBm for 0.8 MHz ≤ Δf < 1.0 MHz, drops to -28 dBm for 1.0 MHz ≤ Δf < 1.8 MHz, and then drops to -34 dBm for 1.8 MHz ≤ Δf ≤ Δf_max. The right y-axis shows the equivalent power density in 1 MHz bandwidth, which is 10*log10(30) ≈ 14.77 dB higher than the 30 kHz bandwidth power density.](730b6615db6d402580db1024a7f4e163_img.jpg) + +Illustrative diagram of spectrum emission mask. The graph shows power density in 30 kHz [dBm] on the left y-axis (ranging from -45 to -20) and power density in 1 MHz [dBm] on the right y-axis (ranging from -30 to -5). The x-axis represents frequency separation Δf from the carrier [MHz] with markers at 0.8, 1.0, 1.8, 2.4, and Δf\_max. The mask is defined by two lines: P = 34 dBm (upper limit) and P = 26 dBm (lower limit). The mask starts at -20 dBm for 0.8 MHz ≤ Δf < 1.0 MHz, drops to -28 dBm for 1.0 MHz ≤ Δf < 1.8 MHz, and then drops to -34 dBm for 1.8 MHz ≤ Δf ≤ Δf\_max. The right y-axis shows the equivalent power density in 1 MHz bandwidth, which is 10\*log10(30) ≈ 14.77 dB higher than the 30 kHz bandwidth power density. + +Illustrative diagram of spectrum emission mask + +Figure 6.6.4.3.3-1 + +Table 6.6.4.3.3-1: Basic Limits for spectrum emission mask values, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \geq 34$ dBm for 1,28 Mcps TDD + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit | Measurement bandwidth | +|----------------------------------------------------------------------|-------------|-----------------------| +| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$ | -20 dBm | 30 kHz | +| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$ | -28 dBm | 30 kHz | +| (NOTE) | -13 dBm | 30 kHz | +| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | -13 dBm | 1 MHz | + +NOTE: For a multi-band TAB connector with Inter RF Bandwidth gap less than 8MHz, the basic limit within the Inter RF Bandwidth gap is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the Inter RF Bandwidth gap, where the contribution from the far-end RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end RF Bandwidth. + +Table 6.6.4.3.3-2: Basic Limits for spectrum emission mask values, $26 \text{ dBm} \leq P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 34$ dBm for 1,28 Mcps TDD + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit | Measurement bandwidth | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 54 \text{ dB}$ | 30 kHz | +| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 54 - 10 \cdot (f\_offset - 1,015) \text{ dB}$ | 30 kHz | +| (NOTE) | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 62 \text{ dB}$ | 30 kHz | +| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 47 \text{ dB}$ | 1 MHz | + +NOTE: For a multi-band TAB connector with Inter RF Bandwidth gap less than 8MHz, the basic limit within the Inter RF Bandwidth gap is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the Inter RF Bandwidth gap, where the contribution from the far-end RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end RF Bandwidth. + +**Table 6.6.4.3.3-3: Basic Limits for spectrum emission mask values, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 26 \text{ dBm}$ for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit | Measurement bandwidth | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------| +| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$ | -28 dBm | 30 kHz | +| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$ | | 30 kHz | +| (NOTE) | -36 dBm | 30 kHz | +| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | -21 dBm | 1 MHz | +| NOTE: For a multi-band TAB connector with Inter RF Bandwidth gap less than 8MHz, the basic limit within the Inter RF Bandwidth gap is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the Inter RF Bandwidth gap , where the contribution from the far-end RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end RF Bandwidth . | | | + +NOTE: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +#### 6.6.4.4 Minimum requirement for single RAT E-UTRA operation + +There is no spectrum emission mask requirement for a single RAT E-UTRA AAS BS. + +### 6.6.5 Operating band unwanted emission + +#### 6.6.5.1 General + +Unless otherwise stated, for E-UTRA single band and MSR the operating band unwanted emission limits are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported *downlink operating band* to the lower *Base Station RF Bandwidth edge* located at $F_{\text{BW,RF,low}}$ and from the upper *Base Station RF Bandwidth edge* located at $F_{\text{BW,RF,high}}$ up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported *downlink operating band*. The values of $\Delta f_{\text{OBUE}}$ are defined in table 6.6.1-1. + +For AAS BS capable of operation in multiple operating bands, using *single band TAB connectors*, the single-band requirements apply to those connectors and the cumulative evaluation of the emission limit in the *Inter RF Bandwidth gap* is not applicable. + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. + +#### 6.6.5.2 Minimum requirement for MSR operation + +##### 6.6.5.2.1 General + +The MSR operating band unwanted emission *basic limits* are the same as those specified in 3GPP TS 37.104 [9], subclauses 6.6.2.1, 6.6.2.2 and 6.6.2.4. + +The operating band unwanted emission requirements for an MSR AAS BS are that for each *TAB connector TX min cell group* and each applicable *basic limit* as specified in 3GPP TS 37.104 [5], the power summation of the emissions at the *TAB connectors* of the *TAB connector TX min cell group* shall not exceed an AAS BS limit specified as the *basic limit* + $10 \log_{10}(N_{\text{TXU,countedpercell}})$ . + +NOTE: Conformance to the AAS BS operating band unwanted emission requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span. + +Or + +- 2) The unwanted emissions power at each *TAB connector* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span, scaled by $-10\log_{10}(n)$ , where $n$ is the number of *TAB connector* in the *TAB connector TX min cell group*. + +#### 6.6.5.2.2 Basic limits for Band Categories 1 and 3 + +For a *TAB connector* operating in Band Category 1 or Band Category 3 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for an AAS BS of Wide Area BS class operating in *non-contiguous spectrum*, it applies inside any *sub-block gap*. In addition, for an AAS BS of Wide Area BS class operating in multiple bands, the requirements apply inside any *Inter RF Bandwidth gap*. + +For an AAS BS of Medium Range BS class operating in Band Category 1 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for an AAS BS of Medium Range BS class operating in *non-contiguous spectrum*, it applies inside any *sub-block gap*. In addition, for an AAS BS of Medium Range BS class operating in multiple bands, the requirements apply inside any *Inter RF Bandwidth gap*. + +For an AAS BS of Local Area BS class operating in Band Category 1 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for an AAS BS of Local Area BS class operating in *non-contiguous spectrum*, it applies inside any *sub-block gap*. In addition, for an AAS BS Local Area BS class operating in multiple bands, the requirements apply inside any *Inter RF Bandwidth gap*. + +Outside the *Base Station RF Bandwidth edges*, *basic limits* are specified in tables 6.6.5.2.2-1 to 6.6.5.2.2-4 below, where: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is the offset to the frequency $\Delta f_{OBUE}$ outside the *downlink operating band*. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector*, inside any *Inter RF Bandwidth gaps* with $W_{gap} < 2 \times \Delta f_{OBUE}$ MHz, a combined *basic limit* shall be applied which is the cumulative sum of emissions shall not exceed the cumulative sum of the *basic limits* specified at the *Base Station RF Bandwidth edges* on each side of the *Inter-RF Bandwidth gap*. The *basic limit* for *Base Station RF Bandwidth edge* is specified in table 6.6.5.2.2-1 to 6.6.5.2.2-4 below, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the inter *Base Station RF Bandwidth gap* minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector*, the operating band unwanted emission *basic limits* apply also in a supported operating band without any carriers transmitted, in the case where there are carriers transmitted in other operating band(s). In this case where there is no carrier transmitted in an operating band, the operating band unwanted emission limit, as defined in the tables of the present subclause for the largest frequency offset ( $\Delta f_{max}$ ), of a band where there is no carrier transmitted shall apply from 10 MHz below the lowest frequency, up to 10 MHz above the highest frequency of the supported downlink operating band without any carrier transmitted. And no cumulative *basic limits* are applied in the *inter-band gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted. + +Inside any *sub-block gap* for a *TAB connector* operating in *non-contiguous spectrum*, a combined *basic limit* shall be applied which is the cumulative sum of the *basic limits* specified for the adjacent sub blocks on each side of the *sub-block gap*. The *basic limit* for each sub block is specified in tables 6.6.5.2.2-1 to 6.6.5.2.2-4 below, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f\_offset$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +Applicability of Wide Area operating band unwanted emission requirements in tables 6.6.5.2.2-1, 6.6.5.2.2-1a and 6.6.5.2.2-1b is specified in table 6.6.2.1-0. + +Note: Option 1 and Option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [4] and TS 38.104 [27]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [2]. + +**Table 6.6.5.2.2-0: Applicability of operating band unwanted emission requirements for BC1 and BC3 Wide Area BS** + +| NR band operation | UTRA supported | Applicable requirement table | +|------------------------------------------------------------------------|----------------|------------------------------| +| None | Y/N | 6.6.5.2.2-1 (Option 2) | +| In certain regions (NOTE 2), band 1, 7, 38, 65 | N | 6.6.5.2.2-1 (Option 2) | +| Any | Y | 6.6.5.2.2-1 (Option 2) | +| Any below 1 GHz | N | 6.6.5.2.2-1a (Option 1) | +| Any above 1 GHz except for certain regions (NOTE 2), band 1, 7, 38, 65 | N | 6.6.2.1-1b (Option 1) | + +NOTE 1: Void. +NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [14] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [8] and TS 38.104 [27] are applied. + +**Table 6.6.5.2.2-1: WA BS OBUE in BC1 and BC3 bands - option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------|-------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | (Note 6) | 30 kHz | +| (NOTE 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm (Note 6) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{max}, 10.5 \text{ MHz})$ | -13 dBm (Note 6) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm (NOTE 5, 6) | 1 MHz | + +NOTE 1: For MSR *TAB connector* supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -15dBm/MHz (for MSR *multi-band TAB connector*, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands < 1 GHz). + +NOTE 2: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 6: For MSR *multi-band TAB connector*, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands < 1 GHz. + +**Table 6.6.5.2.2-1a: WA BS OBUE in BC1 and BC3 bands $\leq 1$ GHz - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (Note 1, 2) | Measurement bandwidth (Note 4) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 5) | 100 kHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -16dBm/100kHz. + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base station *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.2.2-1b: WA BS OBUE in BC1 and BC3 bands $> 1$ GHz - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (Note 1, 2) | Measurement bandwidth (Note 4) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 5) | 1MHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within sub-block gaps shall be -15dBm/1MHz. + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +**Table 6.6.5.2.2-2: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm and not supporting NR; or BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 65 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.1 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 52 \text{ dB}$ | 1 MHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.1 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 52 \text{ dB}, -15 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For MSR TAB connector supporting non-contiguous spectrum operation within any operating band the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the sub-block gap, where the basic limit within sub-block gaps shall be $(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB}) / \text{MHz}$ . + +NOTE 2: For MSR multi-band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or Base Station RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or Base Station RF Bandwidth. + +**Table 6.6.5.2.2-2a: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm, supporting NR and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (Note 1, 2) | Measurement bandwidth (Note 4) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 53 \text{ dB} - (7/5) \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})$ (Note 5) | 100 kHz | + +NOTE 1: For MSR TAB connector supporting non-contiguous spectrum operation within any operating band the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the basic limit within sub-block gaps shall be $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm}) / 100 \text{ kHz}$ . + +NOTE 2: For MSR multi band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.5.2.2-3: MR BS OBUE in BC1 bands applicable for: BS with maximum output power** + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm and not supporting NR; or BS with maximum output power + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm supporting NR, and supporting UTRA + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-27 \text{ dBm} - \frac{5}{3} \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-22 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz | +| (NOTE 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -34 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -21 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -25 dBm | 1 MHz | + +NOTE 1: For MSR TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -25 dBm/MHz. + +NOTE 2: For MSR multi-band TAB connector with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 6.6.5.2.2-3a: MR BS OBUE in BC1 bands applicable for: BS with maximum output power** + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm, supporting NR and not supporting UTRA + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth (Note 4) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -29 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -29 dBm (Note 5) | 100 kHz | + +NOTE 1: For MSR TAB connector supporting non-contiguous spectrum operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -29dBm/100kHz. + +NOTE 2: For MSR multi band TAB connector with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.2.2-4: LA BS OBUE in BC1 bands** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (Note 1, 2) | Measurement bandwidth (NOTE 4) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -37 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (NOTE 5) | 100 kHz | + +NOTE 1: For MSR TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -37dBm/100 kHz. + +NOTE 2: For MSR multi-band TAB connector with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 4: As a general rule for the requirements in the present subclause, 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 may 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. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10$ MHz. + +#### 6.6.5.2.3 Basic limit for Band Category 2 + +For a *TAB connector* operating in Band Category 2 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for a *TAB connector* operating in *non-contiguous spectrum*, it applies inside any *sub-block gap*. + +Outside the *Base Station RF Bandwidth edges*, *basic limits* are specified in tables 6.6.5.2.3-1 to 6.6.5.2.3-8 below, where: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{\max}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the *downlink operating band*. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector*, inside any *Inter-RF Bandwidth gaps* with $W_{\text{gap}} < 2 \times \Delta f_{\text{OBUE}}$ MHz, a combined *basic limit* shall be applied which is the cumulative sum of the *basic limits* specified at the *Base Station RF Bandwidth edges* on each side of the *Inter-RF Bandwidth gap*. The *basic limit* for *Base Station RF Bandwidth edge* is specified in table 6.6.5.2.3-1 to 6.6.5.2.3-8 below, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{\max}$ is equal to the *Inter RF Bandwidth gap* minus half of the bandwidth of the measuring filter. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector* where multiple bands are mapped on the same antenna connector and where there is no carrier transmitted in an operating band, the operating band unwanted emission limit, as defined in the tables of the present subclause for the largest frequency offset ( $\Delta f_{\max}$ ), of a band where there is no carrier transmitted shall apply from 10 MHz below the lowest frequency, up to 10 MHz above the highest frequency of the supported downlink operating band without any carrier transmitted. And no cumulative *basic limits* are applied in the *inter-band gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted. + +Inside any *sub-block gap* for a *TAB connector* operating in *non-contiguous spectrum*, a combined *basic limit* shall be applied which is the cumulative sum of the *basic limit* specified for the adjacent sub blocks on each side of the *sub-block gap*. The *basic limit* for each sub block is specified in tables 6.6.5.2.3-1 to 6.6.5.2.3-8 below, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f\_offset$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{\max}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +Applicability of Wide Area operating band unwanted emission requirements in Tables 6.6.5.2.31, 6.6.5.2.3-1a and 6.6.5.2.3-1b is specified in table 6.6.5.2.3-0. + +Note: Option 1 and option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [4] and TS 38.104 [27]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [2]. + +**Table 6.6.5.2.3-0: Applicability of operating band unwanted emission requirements for BC2 Wide Area BS** + +| NR band operation | UTRA supported | Applicable requirement table | +|-------------------------------------------------------------|----------------|------------------------------| +| None | Y/N | 6.6.5.2.3-1 (option 2) | +| In certain regions (NOTE 2), bands 3, 8 | N | 6.6.5.2.3-1 (option 2) | +| Any | Y | 6.6.5.2.3-1 (option 2) | +| Any below 1 GHz except for certain regions (NOTE 2), band 8 | N | 6.6.5.2.3-1a (option 1) | +| Any above 1 GHz except for certain regions (NOTE 2), band 3 | N | 6.6.5.2.3-1b (option 1) | + +NOTE 1: Void. +NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [14] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [8] and TS 38.104 [27] are applied. + +**Table 6.6.5.2.3-1: WA BS OBUE in BC2 bands – option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------|-------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ (NOTE 1) | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ (NOTE 9) | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | (Note 13) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{max}, 10 \text{ MHz})$ | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm (Note 13) | 30 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{max}, 10.5 \text{ MHz})$ | -13 dBm (Note 13) | 1 MHz | +| | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm (NOTE 11, 13) | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.2.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . +NOTE 2: For MSR *TAB connector* supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -15dBm/MHz (for MSR *multi-band TAB connector*, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ ). +NOTE 3: For a MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ operation the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. +NOTE 13: For MSR *multi-band TAB connector*, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ . + +**Table 6.6.5.2.3-1a: WA BS OBUE in BC2 bands $\leq 1$ GHz – option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 11) | 100 kHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -16dBm/100kHz. + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the *sub-block edge*, the limits in table 6.6.5.2.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.5.2.3-1b: WA BS OBUE in BC2 bands $> 1$ GHz – option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 11) | 1MHz | + +NOTE 1: For MSR *TAB connectors* supporting non-contiguous spectrum operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -15dBm/1MHz. + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the *sub-block edge*, the limits in table 6.6.5.2.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.5.2.3-2: WA BS OBUE in BC2 bands applicable for: BS operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 5, 6) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 4: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the *sub-block edge*. + +NOTE 5: For MSR *TAB connector* supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. + +NOTE 6: For a MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.2.3-3: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm and not supporting NR; or BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ (NOTE 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 58 \text{ dB} - (5/3) \cdot (f\_offset/\text{MHz} - 0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 53 \text{ dB} - 15 \cdot (f\_offset/\text{MHz} - 0.215) \text{ dB}$ | 30 kHz | +| (NOTE 9) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 65 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 52 \text{ dB}$ | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.3 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 52 \text{ dB}, -15 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.2.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For a MSR TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be $(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB})/\text{MHz}$ . + +NOTE 3: For a MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 6.6.5.2.3-3a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm, supporting NR and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 53 \text{ dB} - (7/5) \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})$ (Note 11) | 100 kHz | + +NOTE 1: For MSR TAB connectors supporting non-contiguous spectrum operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.2.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.5.2.3-4: MR BS OBUE in BC2 bands applicable for: BS with maximum output power** + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ and not supporting NR, or BS with maximum output power + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ supporting NR, and supporting UTRA + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$
(NOTE 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-27 \text{ dBm} - \frac{5}{3} \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$
(NOTE 9) | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-22 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz | +| | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -34 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -21 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.2.3-6 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For a MSR *TAB connector* supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -25dBm/MHz. + +NOTE 3: For a MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 6.6.5.2.3-4a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power** + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ , supporting NR and not supporting UTRA + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -29 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm (Note 11) | 100 kHz | + +NOTE 1: For MSR *TAB connectors* supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -29dBm/100kHz. + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.2.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.5.2.3-5: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm and operating E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 5, 6) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 38 \text{ dB} - 60 \cdot (f\_offset/\text{MHz} - 0.015) \text{ dB}$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 41 \text{ dB} - 160 \cdot (f\_offset/\text{MHz} - 0.065) \text{ dB}$ | 30 kHz | + +NOTE 4: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 5: For a MSR TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. + +NOTE 6: For a MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.2.3-6: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm and operating E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 5, 6) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset <$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 4: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 5: For a MSR TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. + +NOTE 6: For a MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.2.3-7: LA BS OBUE in BC2 bands** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ (NOTE 1) | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -37 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (NOTE 11) | 100 kHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.2.3-8 apply for $0 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ . + +NOTE 2: For a MSR *TAB connector* supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -37dBm/100 kHz. + +NOTE 3: For a MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.2.3-8: LA BS OBUE in BC2 bands applicable for: BS operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic Limit (NOTE 5, 6) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.175 \text{ MHz}$ | | 30 kHz | + +NOTE 4: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 5: For a MSR *TAB connector* supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. + +NOTE 6: For a MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +The following notes are common to all subclauses in 6.6.5.2.3: + +NOTE 9: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 10: As a general rule for the requirements in the present subclause, 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 may 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. + +NOTE 11: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +NOTE 12: All limits in table 6.6.5.2.3-1, table 6.6.5.2.3-3, table 6.6.5.2.3-4 and table 6.6.5.2.3-7 are identical to the corresponding limits for Band Category 1 and 3. + +#### 6.6.5.2.4 Additional requirements + +The MSR operating band unwanted emission *basic limits* for additional requirements are the same as the *basic limits* specified in 3GPP TS 37.104 [9], subclause 6.6.2.4. + +### 6.6.5.3 Minimum requirement for single RAT UTRA operation + +There is no operating band unwanted emission requirement for a single RAT UTRA FDD or single RAT UTRA TDD AAS BS. + +### 6.6.5.4 Minimum requirement for single RAT E-UTRA operation + +#### 6.6.5.4.1 General + +The single RAT E-UTRA operating band unwanted emission *basic limits* are given in subclauses 6.6.5.4.2, 6.6.5.4.3 and 6.6.5.4.4. + +The operating band unwanted emission requirements for AAS BS in *single RAT E-UTRA operation* are that for each *TAB connector TX min cell group* and each applicable *basic limit*, the power sum of the emissions at the *TAB connectors* of the *TAB connector TX min cell group* shall not exceed an AAS limit specified as the *basic limit* + $10\log_{10}(N_{\text{TXU, counted per cell}})$ . + +NOTE: Conformance to the AAS BS operating band unwanted emission requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span. +- Or +- 2) The unwanted emissions power at each *TAB connector* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span, scaled by $-10\log_{10}(n)$ , where *n* is the number of *TAB connectors* in the *TAB connector TX min cell group*. + +The requirements shall apply whatever the type of *TAB connector* is considered (single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification. In addition, for a *TAB connector* operating in *non-contiguous spectrum*, the requirements apply inside any *sub-block gap*. In addition, for a *multi-band TAB connector* the requirements apply inside any *Inter RF Bandwidth gap*. + +The unwanted emission *basic limits* in the part of the *downlink operating band* that falls in the spurious domain are consistent with ITU-R Recommendation SM.329 [14]. + +Emissions shall use the *basic limits* specified in the tables below, where: + +- $\Delta f$ is the separation between the channel edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the channel edge frequency and the centre of the measuring filter. +- $f\_offset_{\max}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the *downlink operating band*. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector* inside any *Inter RF Bandwidth gaps* with $W_{\text{gap}} < 2 \times \Delta f_{\text{OBUE}}$ MHz, a combined *basic limit* shall be applied which is the cumulative sum of the *basic limits* specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *basic limit* for *Base Station RF Bandwidth edge* is specified in the tables subclause 6.6.5.4.2 to 6.6.5.4.7 below, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the *Base Station RF Bandwidth edge*. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{\max}$ is equal to the *Inter RF Bandwidth gap* minus half of the bandwidth of the measuring filter. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +For *multi-band TAB connector* where multiple bands are mapped on the same antenna connector, the operating band unwanted emission *basic limits* apply also in a supported operating band without any carrier transmitted, in the case where there are carrier(s) transmitted in other supported operating band(s). In this case where there is no carrier transmitted in an operating band, the operating band unwanted emission limit, as defined in the tables of the present subclause for the largest frequency offset ( $\Delta f_{max}$ ), of a band where there is no carrier transmitted shall apply from 10 MHz below the lowest frequency, up to 10 MHz above the highest frequency of the supported downlink operating band without any carrier transmitted. And no cumulative *basic limit* is applied in the *inter-band gap* between a supported downlink operating band with carrier(s) transmitted and a supported downlink operating band without any carrier transmitted. + +For a multicarrier E-UTRA *TAB connector* or a *TAB connector* configured for intra-band contiguous or non-contiguous *carrier aggregation* the definitions above apply to the lower edge of the carrier transmitted at the lowest carrier frequency and the upper edge of the carrier transmitted at the highest carrier frequency within a specified frequency band. + +In addition inside any *sub-block gap* for a *TAB connector* operating in *non-contiguous spectrum*, a combined *basic limit* shall be applied which is the cumulative sum of the *basic limits* specified for the adjacent sub blocks on each side of the *sub-block gap*. The *basic limit* for each sub block is specified in the tables subclause 6.6.5.4.2 to 6.6.5.4.7 below, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f\_offset$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For an AAS BS of Wide Area BS class, the requirements of either subclause 6.6.5.4.2 (Category A limits) or subclause 6.6.5.4.3 (Category B limits) shall apply. + +For an AAS BS of Local Area BS class, the requirements of subclause 6.6.5.4.4 shall apply (Category A and B). + +For an AAS BS of Medium Range BS class, the requirements in subclause 6.6.5.4.5 shall apply (Category A and B). + +The application of either Category A or Category B *basic limits* shall be the same as for Transmitter spurious emissions (Mandatory Requirements) in subclause 6.6.6. + +#### 6.6.5.4.2 Basic limits for Wide Area BS (Category A) + +For E-UTRA *TAB connector* operating in Bands 5, 6, 8, 12, 13, 14, 17, 18, 19, 26, 27, 28, 29, 31, 44, 68, 71, 72, 73, 85, 87, 88 the *basic limits* are specified in tables 6.6.5.4.2-1 to 6.6.5.4.2-3. + +**Table 6.6.5.4.2-1: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands <1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-1 \text{ dBm} - \frac{10}{1.4} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -11 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm | 100 kHz | +| NOTE 1: For a TAB connector supporting non-contiguous spectrum operation within any operating band, the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap . Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap , where the basic limit within sub-block gaps shall be -13dBm/100kHz. | | | | +| NOTE 2: For a multi-band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{TOBUE}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap . | | | | + +**Table 6.6.5.4.2-2: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands <1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-5 \text{ dBm} - \frac{10}{3} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -15 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm | 100 kHz | +| NOTE 1: For a TAB connector supporting non-contiguous spectrum operation within any operating band, the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the basic limit within sub-block gaps shall be -13dBm/100kHz. | | | | +| NOTE 2: For a multi-band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap. | | | | + +**Table 6.6.5.4.2-3: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands <1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (NOTE 7) | 100 kHz | +| NOTE 1: For a TAB connector supporting non-contiguous spectrum operation within any operating band, the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the basic limit within sub-block gaps shall be -13dBm/100kHz. | | | | +| NOTE 2: For a multi-band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap. | | | | + +For a E-UTRA TAB connector operating in Bands 1, 2, 3, 4, 7, 9, 10, 11, 21, 22, 23, 24, 25, 30, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 45, 48, 50, 52, 54, 65, 66, 69, 70, 74, 75 emissions shall use the basic limits specified in tables 6.6.5.4.2-4 to 6.6.5.4.2-6: + +**Table 6.6.5.4.2-4: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands >1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-1 \text{ dBm} - \frac{10}{1.4} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -11 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm | 1MHz | +| NOTE 1: For a TAB connector supporting non-contiguous spectrum operation within any operating band, the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the basic limit within sub-block gaps shall be -13dBm/1MHz. | | | | +| NOTE 2: For a multi-band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or Base Station RF Bandwidth. | | | | + +**Table 6.6.5.4.2-5: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands >1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-5 \text{ dBm} - \frac{10}{3} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -15 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm | 1MHz | +| NOTE 1: For a TAB connector supporting non-contiguous spectrum operation within any operating band, the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the basic limit within sub-block gaps shall be -13dBm/1MHz. | | | | +| NOTE 2: For a multi-band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or Base Station RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or Base Station RF Bandwidth. | | | | + +**Table 6.6.5.4.2-6: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands >1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (NOTE 7) | 1MHz | +| NOTE 1: For a TAB connector supporting non-contiguous spectrum operation within any operating band, the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the basic limit within sub-block gaps shall be -13dBm/1MHz. | | | | +| NOTE 2: For a multi-band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or Base Station RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or Base Station RF Bandwidth. | | | | + +#### 6.6.5.4.3 Basic limits for Wide Area BS (Category B) + +##### 6.6.5.4.3.1 General + +For Category B Operating band unwanted emissions, there are two options for the *basic limits* that may be applied regionally. Either the *basic limits* in subclause 6.6.3.2.1 or subclause 6.6.3.2.2 shall be applied. + +##### 6.6.5.4.3.2 Category B requirements (Option 1) + +For a E-UTRA TAB connector operating in Bands 5, 8, 12, 13, 14, 17, 20, 26, 27, 28, 29, 31, 44, 67, 68, 71, 72, 73, 85, 87, 88 emissions shall use the *basic limits* specified in tables 6.6.5.4.3.2-1 to 6.6.5.4.3.2-3: + +**Table 6.6.5.4.3.2-1: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands <1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-1 \text{ dBm} - \frac{10}{1.4} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -11 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -16dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.4.3.2-2: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands <1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-5 \text{ dBm} - \frac{10}{3} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -15 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -16dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.4.3.2-3: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands <1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (NOTE 7) | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -16dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +For a E-UTRA TAB connector operating in Bands 1, 2, 3, 4, 7, 10, 22, 25, 30, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 45, 48, 50, 52, 65, 66, 69, 70, 75 emissions shall use the *basic limits* specified in tables 6.6.5.4.3.2-4 to 6.6.5.4.3.2-6: + +**Table 6.6.5.4.3.2-4: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands >1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-1 \text{ dBm} - \frac{10}{1.4} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -11 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm | 1MHz | +| NOTE 1: For a TAB connector supporting non-contiguous spectrum operation within any operating band, the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap , where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap , where the basic limit within sub-block gaps shall be -15dBm/1MHz. | | | | +| NOTE 2: For a multi-band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap , where the contribution from the far-end sub-block or Base Station RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or Base Station RF Bandwidth . | | | | + +**Table 6.6.5.4.3.2-5: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands >1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-5 \text{ dBm} - \frac{10}{3} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -15 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm | 1MHz | +| NOTE 1: For a TAB connector supporting non-contiguous spectrum operation within any operating band, the basic limit within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub-block gap , where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap , where the basic limit within sub-block gaps shall be -15dBm/1MHz. | | | | +| NOTE 2: For a multi-band TAB connector with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the basic limit within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or Base Station RF Bandwidth on each side of the Inter RF Bandwidth gap , where the contribution from the far-end sub-block or Base Station RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or Base Station RF Bandwidth . | | | | + +**Table 6.6.5.4.3.2-6: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands >1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (NOTE 7) | 1MHz | + +NOTE 1: For a *TAB connector* supporting *non-contiguous spectrum* operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -15dBm/1MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +#### 6.6.5.4.3.3 Category B (Option 2) + +The *basic limits* in this subclause are intended for Europe and may be applied regionally for a *TAB connector* operating in band 1, 3, 8, 32, 33, 34 or 65. + +For a *TAB connector* operating in band 1, 3, 8, 32, 33, 34 or 65, emissions shall use the *basic limits* specified in table 6.6.5.4.3.3-1 below for 5, 10, 15 and 20 MHz *channel bandwidth*: + +**Table 6.6.5.4.3.3-1: Regional Wide Area BS operating band unwanted emission limits in band 1, 3, 8, 32, 33, 34 or 65 for 5, 10, 15 and 20 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|-------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 6) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $1.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -13 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (NOTE 7) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting *non-contiguous spectrum* operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -15dBm/1MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +For a *TAB connector* operating in band 3, 8, or 65 emissions shall use the *basic limits* specified in table 6.6.5.4.3.3-2 below for 3 MHz *channel bandwidth*: + +**Table 6.6.5.4.3.3-2: Regional Wide Area BS operating band unwanted emission limits in band 3, 8, or 65 for 3 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | +| $0.15 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.165 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 6) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm | 1 MHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -15dBm/1MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +For a TAB connector operating in band 3, 8 or 65, emissions shall not use the *basic limits* specified in table 6.6.5.4.3.3-3 below for 1.4 MHz channel bandwidth: + +**Table 6.6.5.4.3.3-3: Regional Wide Area BS operating band unwanted emission limits in band 3, 8, or 65 for 1.4 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | +| $0.15 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.165 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 6) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | -13 dBm | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm | 1 MHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -15dBm/1MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +#### 6.6.5.4.4 Basic limits for Local Area BS (Category A and B) + +For Local Area BS, *basic limits* are specified in tables 6.6.5.4.4-1 to 6.6.5.4.4-3. + +**Table 6.6.5.4.4-1: Local Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-21 \text{ dBm} - \frac{10}{1.4} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -31 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -31 dBm | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -31dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.4.4-2: Local Area BS operating band unwanted emission limits for 3 MHz channel bandwidth** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -35 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -35 dBm | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -35dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.4.4-3: Local Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2)] | Measurement bandwidth (NOTE 5) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -37 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (NOTE 7) | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -37dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +#### 6.6.5.4.5 Basic limits for Medium Range BS (Category A and B) + +For Medium Range BS, *basic limits* are specified in tables 6.6.5.4.5-1 to 6.6.5.4.5-6. + +**Table 6.6.5.4.5-1: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) \leq 38$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 45 \text{ dB} - (10/1.4) \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 55 \text{ dB}$ | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25dBm | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -25dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.4.5-2: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) \leq 31$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -24 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25dBm | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -25dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.4.5-3: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) \leq 38$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 49 \text{ dB} - (10/3) \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 59 \text{ dB}$ | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 59 \text{ dB}, -25 \text{ dBm})$ | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be $\text{Min}(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 59 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.4.5-4: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) \leq 31 \text{ dBm}$** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -28 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -28 dBm | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -28dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.4.5-5: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) \leq 38 \text{ dBm}$** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 53 \text{ dB} - (7/5) \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 60 \text{ dB}, -25 \text{ dBm})$ (NOTE 6) | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.4.5-6: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) \leq 31 \text{ dBm}$** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (NOTE 1, 2) | Measurement bandwidth (NOTE 5) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -29 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm (NOTE 6) | 100 kHz | + +NOTE 1: For a TAB connector supporting *non-contiguous spectrum* operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within *sub-block gaps* shall be -29dBm/100kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +#### 6.6.5.4.6 Void + +#### 6.6.5.4.7 Additional requirements + +The E-UTRA operating band unwanted emission *basic limits* for additional requirements are the same as the *basic limit* is specified in 3GPP TS 36.104 [8], subclause 6.6.3.3. + +Additional requirements specified in TS 36.104 [8], subclause 6.6.3.3 for Band 41 and Band 49 are not applicable for AAS BS. + +## 6.6.6 Spurious emission + +### 6.6.6.1 General + +The conducted transmitter spurious emission limits apply from 9 kHz to 12.75 GHz, excluding the following RAT-specific frequency ranges: + +- UTRA TDD BS, 1.28 Mcps option as specified in TS 25.105 [3]: from 4 MHz below the lowest frequency of each operating band to 4 MHz above the highest frequency of each operating band. +- UTRA FDD BS as specified in TS 25.104 [2]: from 12.5MHz below the lowest carrier frequency used up to 12.5MHz above the highest carrier frequency used. +- E-UTRA BS as specified in TS 36.104 [4]: from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band*, where $\Delta f_{\text{OBUE}}$ is defined subclause 6.6.1. +- MSR BS as specified in TS 37.104 [5]: from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band*, where $\Delta f_{\text{OBUE}}$ is defined subclause 6.6.1. + +For some operating bands the upper frequency limit is higher than 12.75 GHz in order to comply with the 5th harmonic limit of the *downlink operating band*, as specified in ITU-R recommendation SM.329 [14]. In some exceptional cases, requirements apply also closer than $\Delta f_{\text{OBUE}}$ MHz from the *downlink operating band*; these cases are highlighted in the requirement tables in respective referenced UTRA, E-UTRA or MSR specifications. For operating bands supported by *multi-band TAB connectors* exclusion bands apply to each supported band. + +The requirements apply for both *single band TAB connectors* and *multi-band TAB connectors* (except for frequencies at which exclusion bands or other multi-band provisions apply) and for all transmission modes foreseen by the manufacturer's specification. Unless otherwise stated, all requirements are measured as mean power. + +For operation in Region 2, where the FCC guidance for MIMO systems in [18] is applicable, $N_{\text{TXU, counted per cell}}$ shall be equal to 1 for the purposes of calculating the spurious emissions limits in subclauses 6.6.6.2, 6.6.6.3 or 6.6.6.4. For all other unwanted emissions requirements, $N_{\text{TXU, counted per cell}}$ shall be the value calculated according to subclause 6.1, unless stated differently in regional regulation. + +The AAS BS requirements for spurious emissions limits which are specified for Band 46 or Band 49 in 3GPP TS 37.104 [5], are applicable for AAS BS. + +### 6.6.6.2 Minimum requirement for MSR operation + +The MSR spurious emission *basic limits* are the same as those specified in 3GPP TS 37.104 [9], subclauses 6.6.1.1, 6.6.1.2, 6.6.1.3 and 6.6.1.4. + +The spurious emission requirements for an MSR AAS BS are that for each *TAB connector TX min cell group* and each applicable *basic limit* as specified in 3GPP TS 37.104 [5], the power summation emissions at the *TAB connectors* of the *TAB connector TX min cell group* shall not exceed an AAS limit specified as the *basic limit* + X, where $X = 10 \log_{10}(N_{\text{TXU, counted per cell}})$ , unless stated differently in regional regulation. + +NOTE: Conformance to the AAS BS spurious emission requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span. + +Or + +- 2) The unwanted emissions power at each *TAB connector* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span, scaled by $-10\log_{10}(n)$ , where $n$ is the number of *TAB connectors* in the *TAB connector TX min cell group*. + +### 6.6.6.3 Minimum requirement for single RAT UTRA operation + +The single RAT UTRA FDD spurious emission *basic limits* are the same as those specified in 3GPP TS 25.104 [6], subclauses 6.6.3.1-6.6.3.8. + +The single RAT UTRA TDD spurious emission *basic limits* are the same as those specified in 3GPP TS 25.105 [7], subclauses 6.6.3.1-6.6.3.5. + +The spurious emission requirements for a UTRA single RAT AAS BS are that for each *TAB connector TX min cell group* and each applicable *basic limit* as specified in 3GPP TS 25.104 [6] or 3GPP TS 25.105 [7], the power sum of the emissions at the *TAB connectors* associated with the *TAB connector TX min cell group* shall not exceed an AAS limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{\text{TXU, counted per cell}})$ , unless stated differently in regional regulation. + +NOTE: Conformance to the AAS BS spurious emission requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span. +- Or +- 2) The unwanted emissions power at each *TAB connector* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span, scaled by $-10\log_{10}(n)$ , where $n$ is the number of *TAB connectors* in the *TAB connector TX min cell group*. + +### 6.6.6.4 Minimum requirement for single RAT E-UTRA operation + +*Single RAT E-UTRA operation* spurious emission *basic limits* are the same as those specified in 3GPP TS 36.104 [8], subclauses 6.6.4.1-6.6.4.4. Spurious emission limits specified in TS 36.104 [8], subclauses 6.6.4.1-6.6.4.4 for Band 41, Band 46 and Band 49 are not applicable for AAS BS. + +The spurious emission requirements for AAS BS in *single RAT E-UTRA operation* are that for each *TAB connector TX min cell group* and for each applicable *basic limit* as specified in 3GPP TS 36.104 [4], the total emissions at the *TAB connectors* associated with the *TAB connector TX min cell group* shall not exceed an AAS limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{\text{TXU, counted per cell}})$ , unless stated differently in regional regulation. + +NOTE: Conformance to the AAS BS spurious emission requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span. +- Or +- 2) The unwanted emissions power at each *TAB connector* shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span, scaled by $-10\log_{10}(n)$ , where $n$ is the number of *TAB connectors* in the *TAB connector TX min cell group*. + +## 6.7 Transmitter intermodulation + +### 6.7.1 General + +The transmitter intermodulation requirement is a measure of the capability of the transmitter unit to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter unit via the RDN and antenna array. The requirement applies during the *transmitter ON period* and the *transmitter transient period*. + +The requirement applies at each *TAB connector* supporting transmission in the operating band. + +The transmitter intermodulation level is the power of the intermodulation products when an interfering signal is injected into the *TAB connector*. + +For AAS BS there are two types of transmitter intermodulation cases captured by the transmitter intermodulation requirement: + +- 1) Co-location transmitter intermodulation in which the interfering signal is from a co-located base station. +- 2) Intra-system transmitter intermodulation in which the interfering signal is from other transmitter units within the AAS BS. + +For AAS BS, the co-location transmitter intermodulation requirement is considered sufficient if the interfering signal for the co-location requirement is higher than the declared interfering signal for intra-system transmitter intermodulation requirement. + +## 6.7.2 Minimum requirement for MSR operation + +### 6.7.2.1 General co-location minimum requirement + +The transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in subclause 6.6.6, operating band unwanted emission in subclause 6.6.5 and ACLR in subclause 6.6.3 in the presence of a wanted signal and an interfering signal according to table 6.7.2.1-1 for AAS BS operation in BC1, BC2 and BC3. + +The requirement is applicable outside the *Base Station RF Bandwidth edges*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *TAB connectors* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block edges*. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement applies relative to the *Base Station RF Bandwidth edges* of each operating band. In case the inter *Base Station RF Bandwidth gap* is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth gap*. + +**Table 6.7.2.1-1: Interfering signal for the co-location transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA or NR signal | +| Interfering signal type | E-UTRA signal of channel bandwidth 5 MHz | +| Interfering signal level | Rated total output power per TAB connector in the operating band ( $P_{\text{Rated,t,TABc}} - 30\text{dB}$ ) | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or edge of sub-block inside a gap | $\pm 2.5$ MHz
$\pm 7.5$ MHz
$\pm 12.5$ MHz | +| NOTE 1: | Interfering signal positions that are partially or completely outside of any downlink operating band of the TAB connector are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band , 3GPP TS 37.141 [19] provides further guidance regarding appropriate test requirements. | +| NOTE 2: | In certain regions, NOTE 1 is not applied in Band 1, 3, 8, 9, 11, 18, 19, 21, 28, 32 operating within 1 475.9 MHz to 1 495.9 MHz, 34. | + +### 6.7.2.2 Additional co-location minimum requirement (BC1 and BC2) + +The transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in subclause 6.6.6, operating band unwanted emission in subclause 6.6.5 and ACLR in subclause 6.6.3 in the presence of a wanted signal and an interfering signal according to table 6.7.2.2-1 for BS operation in BC2. + +The requirement is applicable outside the *Base Station RF Bandwidth* edges for BC2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth* edges. + +For *TAB connectors* supporting operation in *non-contiguous spectrum* in BC1 or BC2, the requirement is also applicable inside a *sub-block gap* with a gap size larger than or equal to two times the interfering signal centre frequency offset. For *TAB connectors* supporting operation in *non-contiguous spectrum* in BC1, the requirement is not applicable inside a *sub-block gap* with a gap size equal to or larger than 5 MHz. The interfering signal offset is defined relative to the *sub-block* edges. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement applies relative to the *Base Station RF Bandwidth edges* of a BC2 operating band. The requirement is also applicable for BC1 and BC2 inside an inter *Base Station RF Bandwidth* gap equal to or larger than two times the interfering signal centre frequency offset. For *TAB connectors* supporting operation in multiple operating bands, the requirement is not applicable for BC1 band inside an inter *Base Station RF Bandwidth* gap with a gap size equal to or larger than 5 MHz. + +**Table 6.7.2.2-1: Interfering signal for the co-location transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA or NR or UTRA signal | +| Interfering signal type | CW | +| Interfering signal level | Rated total output power per TAB connector in the operating band ( $P_{\text{Rated,TABc}} - 30\text{dB}$ ) | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or edge of sub-block inside a gap | $> \text{abs}(800) \text{ kHz}$ for CW interferer | +| NOTE: | Interfering signal positions that are partially or completely outside of any downlink operating band of the TAB connector are excluded from the requirement. | + +### 6.7.2.3 Additional co-location minimum requirement (BC3) + +This additional requirement shall only apply for BS co-located with an UTRA TDD BS. + +The transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in subclause 6.6.6, operating band unwanted emission in subclause 6.6.5 and ACLR in subclause 6.6.3 in the presence of a wanted signal and an interfering signal according to table 6.7.2.3-1 for AAS BS operation in BC3. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement applies relative to the *Base Station RF Bandwidth edges* of each operating band. In case the *Inter RF Bandwidth gap* is less than 3.2 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth* gap. + +**Table 6.7.2.3-1: Interfering signal for the co-location transmitter intermodulation requirement (BC3)** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA or NR or UTRA signal | +| Interfering signal type | 1,28 Mcps UTRA TDD signal of channel bandwidth 1,6 MHz | +| Interfering signal level | Rated total output power per TAB connector in the operating band ( $P_{\text{Rated,t,TABC}} - 30\text{dB}$ ) | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or edge of sub-block inside a gap | $\pm 0,8$ MHz
$\pm 1,6$ MHz
$\pm 2,4$ MHz | +| NOTE: | Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are excluded from the requirement. | + +## 6.7.2.4 Additional co-location minimum requirements + +## 6.7.2.5 Intra-system minimum requirement + +The transmitter intermodulation level shall not exceed the unwanted emission limits specified for operating band unwanted emission in subclause 6.6.5 and ACLR in subclause 6.6.3 in the presence of a wanted signal and an interfering signal according to table 6.7.2.5-1 for BS operation in BC1, BC2 and BC3. + +**Table 6.7.2.5-1: Interfering signal for intra-system transmitter intermodulation requirement** + +| Parameter | Value | +|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA or NR or UTRA | +| Interfering signal type | NR, E-UTRA or UTRA signal of the same type and channel bandwidth as the wanted signal (NOTE 1). | +| Interfering signal level | Power level declared by the base station manufacturer (NOTE 2). | +| Frequency offset between interfering signal and wanted signal | 0 MHz | +| NOTE 1: | The interfering signal shall be incoherent with the wanted signal. | +| NOTE 2: | The declared interfering signal power level at each TAB connector is the sum of the co-channel leakage power coupled via the combined RDN and Antenna Array from all the other TAB connectors , but does not comprise power radiated from the Antenna Array and reflected back from the environment. The power at each of the interfering TAB connectors is $P_{\text{Rated,c,TABC}}$ . | + +## 6.7.3 Minimum requirement for single RAT UTRA operation + +### 6.7.3.1 General co-location minimum requirement for FDD UTRA + +The transmitter intermodulation level shall not exceed the out of band emission or the spurious emission requirements of subclause 6.6.5 and subclause 6.6.6 in the presence of interfering signal according to table 6.7.3.1-1. + +**Table 6.7.3.1-1: Interfering and wanted signal frequency offset for co-location requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | UTRA | +| Interfering signal type | UTRA | +| Interfering signal level | Rated total output power per TAB connector in the operating band ( $P_{\text{Rated,t,TABC}} - 30\text{dB}$ ) | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal or edge of sub-block inside a gap | -2,5 MHz
-7,5 MHz
-12,5 MHz
+2,5 MHz
+7,5 MHz
+12,5 MHz | +| NOTE 1: | Interference frequencies that are outside of any allocated frequency band for UTRA-FDD downlink specified in subclause 4.6 are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. | +| NOTE 2: | NOTE 1 is not applied in Band I, III, VI, VIII, IX, XI, XIX, XXI, and XXXII operating within 1 475.9 MHz to 1 495.9MHz, in certain regions. | + +For *TAB connectors* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block* edges. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement is also applicable inside an inter *Base Station RF Bandwidth* gap for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth* gap. + +### 6.7.3.2 General co-location minimum requirement for 1,28 Mcps TDD UTRA + +The transmitter intermodulation level shall not exceed the out of band emission or the spurious emission requirements of subclause 6.6.5 and subclause 6.6.6 in the presence of interfering signal according to table 6.7.3.2-1. + +**Table 6.7.3.2-1: Interfering and wanted signals frequency offset for co-location requirement** + +| Parameter | Value | +|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | 1,28 Mcps TDD UTRA | +| Interfering signal type | 1,28 Mcps TDD UTRA | +| Interfering signal level | Rated total output power per TAB connector in the operating band ( $P_{\text{Rated,t,TABC}} - 30\text{dB}$ ) | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal | -0,8 MHz
-2,4MHz
-4,0 MHz
+0,8 MHz
+2,4 MHz
+4,0 MHz | +| NOTE: | Interference frequencies that are outside of the allocated frequency band specified in subclause 4.6 are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. | + +For *TAB connectors* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block* edges. + +For *TAB connectors* supporting operation in multiple operating band, the requirement is also applicable inside an inter *Base Station RF Bandwidth* gap for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth* gap. + +### 6.7.3.3 Intra-system minimum requirement + +The transmitter intermodulation level shall not exceed the unwanted emission limits specified for operating band unwanted emission in subclause 6.6.5 and ACLR in subclause 6.6.3 in the presence of a wanted signal and an interfering signal according to table 6.7.3.3-1 for AAS BS. + +**Table 6.7.3.3-1: Interfering and wanted signals for intra-system transmitter intermodulation requirement** + +| Parameter | Value | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| Wanted signal type | UTRA or 1,28 Mcps TDD UTRA | +| Interfering signal type | UTRA or 1,28 Mcps TDD UTRA signal of the same channel bandwidth as the wanted signal (NOTE 1). | +| Interfering signal level | Power level declared by the base station manufacturer (NOTE 2). | +| Frequency offset between interfering signal and wanted signal | 0 MHz | +| NOTE 1: The interfering signal shall be incoherent with the wanted signal.
NOTE 2: The declared interfering signal power level at each TAB connector is the sum of the co-channel leakage power coupled via the combined RDN and Antenna Array from all the other TAB connectors , but does not comprise power radiated from the Antenna Array and reflected back from the environment. The power at each of the interfering TAB connectors is $P_{\text{Rated,c,TABC}}$ . | | + +## 6.7.4 Minimum requirement for single RAT E-UTRA operation + +### 6.7.4.1 General co-location minimum requirement + +The transmitter intermodulation level shall not exceed the unwanted emission limits in subclauses 6.6.6, 6.6.5 and 6.6.3 in the presence of an E-UTRA interfering signal according to table 6.7.4.1-1. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *TAB connectors* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block edges*. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement applies relative to the *Base Station RF Bandwidth edges* of each supported operating band. In case the inter *Base Station RF Bandwidth* gap is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth* gap. + +The wanted signal and interfering signal centre frequency is specified in table 6.7.4.1-1. + +**Table 6.7.4.1-1: Interfering and wanted signals for the co-location transmitter intermodulation requirement** + +| Parameter | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal | E-UTRA single carrier, or multi-carrier, or multiple intra-band contiguously or non-contiguously aggregated carriers | +| Interfering signal type | E-UTRA signal of channel bandwidth 5 MHz | +| Interfering signal level | Rated total output power per TAB connector in the operating band ( $P_{\text{Rated,t,TABC}} - 30\text{dB}$ ) | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal or edge of sub-block inside a sub-block gap | ±2,5 MHz
±7,5 MHz
±12,5 MHz | +| NOTE 1: | Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band , 3GPP TS 36.141 [20] provides further guidance regarding appropriate test requirements. | +| NOTE 2: | In certain regions, NOTE 1 is not applied in Band 1, 3, 8, 9, 11, 18, 19, 21, 28, 32 operating within 1 475.9 MHz to 1 495.9 MHz, 34, 74. | + +## 6.7.4.2 Void + +**Table 6.7.4.2-1: Void** + +## 6.7.4.3 Intra-system minimum requirement + +The transmitter intermodulation level shall not exceed the unwanted emission limits specified for operating band unwanted emission in subclause 6.6.5 and ACLR in subclause 6.6.3 in the presence of a wanted signal and an interfering signal according to table 6.7.4.3-1 for AAS BS. + +**Table 6.7.4.3-1: Interfering and wanted signals for intra-system transmitter intermodulation requirement** + +| Parameter | Value | +|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA | +| Interfering signal type | E-UTRA signal of the same channel bandwidth as the wanted signal (NOTE 1). | +| Interfering signal level | Power level declared by the base station manufacturer (NOTE 2). | +| Frequency offset between interfering signal and wanted signal | 0 MHz | +| NOTE 1: | The interfering signal shall be incoherent with the wanted signal. | +| NOTE 2: | The declared interfering signal power level at each TAB connector is the sum of the co-channel leakage power coupled via the combined RDN and Antenna Array from all the other TAB connectors , but does not comprise power radiated from the Antenna Array and reflected back from the environment. The power at each of the interfering TAB connectors is $P_{\text{Rated,c,TABC}}$ . | + +## 7 Conducted receiver characteristics + +### 7.1 General + +Unless otherwise stated, the receiver characteristics are specified at the AAS BS *TAB connector* with full complement of transceivers for the configuration in normal operating condition. For FDD operation the requirements in clause 7 shall be met with the transmitter unit(s) on. + +NOTE 1: In normal operating condition the BS in FDD operation is configured to transmit and receive at the same time. + +NOTE 2: In normal operating condition the BS in TDD operation is configured to TX OFF power during *receive period*. + +The manufacturer shall declare the minimum number of supported geographical cells (i.e. geographical areas). The minimum number of supported geographical cells ( $N_{\text{cells}}$ ) relates to the AAS BS setting with minimum amount of cell splitting. The manufacturer shall also declare *TAB connector RX min cell groups* for this minimum number of cells configuration. Every *TAB connector* supporting reception in an operating band shall map to one *TAB connector RX min cell group* supporting the same. The mapping of *TAB connectors* to cells is implementation dependent. + +The number of active receiver units that are considered when calculating the emission limit ( $N_{\text{RXU, counted}}$ ) for an AAS BS is calculated as follows: + +$N_{\text{RXU, counted}} = \min(N_{\text{RXU, active}}, 8 \times N_{\text{cells}})$ for AAS BS in *single RAT E-UTRA operation* and MSR AAS BS (excluding UTRA only MSR AAS BS). + +And + +$N_{\text{RXU, counted}} = \min(N_{\text{RXU, active}}, 4 \times N_{\text{cells}})$ for AAS BS in *single RAT UTRA operation* and UTRA only MSR AAS BS. + +Further: + +$$N_{\text{RXU, counted per cell}} = N_{\text{RXU, counted}} / N_{\text{cells}}$$ + +$N_{\text{RXU, counted per cell}}$ is used for scaling the *basic limits* as described in subclause 7.6. + +NOTE 3: $N_{\text{RXU, active}}$ is the number of actually active receiver units and is independent to the declaration of $N_{\text{cells}}$ . + +Any receiver requirement specified for NB-IoT in-band, NB-IoT guard band, or standalone NB-IoT operation in 3GPP TS 36.104 [4] for E-UTRA with NB-IoT (in-band or guard band) or for standalone NB-IoT, or in 3GPP TS 37.104 [5] for E-UTRA with NB-IoT or standalone NB-IoT in *MSR operation*, and referred in clause 7, is not applicable for AAS BS. + +Any receiver requirement specified for Band 46 operation or for Band 49 operation in 3GPP TS 36.104 [4] for E-UTRA, or in 3GPP TS 37.104 [5] for E-UTRA in *MSR operation*, and referred in clause 7, is not applicable for AAS BS. The requirements for co-location blocking for Band 46 or Band 49 are applicable for AAS BS. + +## 7.2 Reference sensitivity level + +### 7.2.1 General + +The reference sensitivity power level $P_{\text{REFSENS}}$ is the minimum mean power received at the *TAB connector* at which a reference performance requirement shall be met for a specified reference measurement channel. + +### 7.2.2 Minimum requirement for MSR operation + +For UTRA, the minimum requirement for reference sensitivity is specified in subclause 7.2.3. + +For E-UTRA, the minimum requirement for reference sensitivity is specified in subclause 7.2.4. + +For NR, the minimum requirement for reference sensitivity is that same as that specified for *BS type 1-H* in 3GPP TS 38.104 [28] in subclause 7.2.2. + +### 7.2.3 Minimum requirement for single RAT UTRA operation + +The single RAT UTRA FDD AAS BS of Wide Area BS class shall fulfil minimum requirements for reference sensitivity specified in 3GPP TS 25.104 [6], subclause 7.2.1. + +The single RAT UTRA FDD AAS BS of Medium Range BS class shall fulfil minimum requirements for reference sensitivity specified in 3GPP TS 25.104 [6], subclause 7.2.1. + +The single RAT UTRA FDD AAS BS of Local Area BS class shall fulfil minimum requirements for reference sensitivity specified in 3GPP TS 25.104 [6], subclause 7.2.1. + +The single RAT UTRA TDD AAS BS of Wide Area BS class shall fulfil minimum requirements for reference sensitivity specified in 3GPP TS 25.105 [7], subclause 7.2.1.1. + +The single RAT UTRA TDD AAS BS of Local Area BS class shall fulfil minimum requirements for reference sensitivity specified in 3GPP TS 25.105 [7], subclause 7.2.1.1. + +### 7.2.4 Minimum requirement for single RAT E-UTRA operation + +The single RAT E-UTRA AAS BS of Wide Area BS class shall fulfil minimum requirements for reference sensitivity specified in 3GPP TS 36.104 [8], subclause 7.2.1. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for reference sensitivity specified in 3GPP TS 36.104 [8], subclause 7.2.1. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for reference sensitivity specified in 3GPP TS 36.104 [8], subclause 7.2.1. + +## 7.3 Dynamic range + +### 7.3.1 General + +The dynamic range is a measure of the capability of the receiver unit to receive a wanted signal in the presence of an interfering signal at the *TAB connector* inside the received *channel bandwidth* or the capability of receiving high level of wanted signal. + +### 7.3.2 Minimum requirement for MSR operation + +For UTRA, the minimum requirement for dynamic range is specified in subclause 7.3.3. + +For E-UTRA, the minimum requirement for dynamic range is specified in subclause 7.3.4. + +For NR, the minimum requirement for dynamic range is is that same as that specified for *BS type 1-H* in 3GPP TS 38.104 [28] in subclause 7.3.2. + +### 7.3.3 Minimum requirement for single RAT UTRA operation + +The single RAT UTRA FDD AAS BS of Wide Area BS class shall fulfil minimum requirements for dynamic range specified in 3GPP TS 25.104 [6], subclause 7.3.1. + +The single RAT UTRA FDD AAS BS of Medium Range BS class shall fulfil minimum requirements for dynamic range specified in 3GPP TS 25.104 [6], subclause 7.3.1. + +The single RAT UTRA FDD AAS BS of Local Area BS class shall fulfil minimum requirements for dynamic range specified in 3GPP TS 25.104 [6], subclause 7.3.1. + +The single RAT UTRA TDD AAS BS of Wide Area BS class shall fulfil minimum requirements for dynamic range specified in 3GPP TS 25.105 [7], subclause 7.3.1.1. + +The single RAT UTRA TDD AAS BS of Local Area BS class shall fulfil minimum requirements for dynamic range specified in 3GPP TS 25.105 [7], subclause 7.3.1.1. + +### 7.3.4 Minimum requirement for single RAT E-UTRA operation + +The single RAT E-UTRA AAS BS of Wide Area BS class shall fulfil minimum requirements for dynamic range specified in 3GPP TS 36.104 [8], subclause 7.3.1. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for dynamic range specified in 3GPP TS 36.104 [8], subclause 7.3.1. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for dynamic range specified in 3GPP TS 36.104 [8], subclause 7.3.1. + +## 7.4 Adjacent channel selectivity, general blocking, and narrowband blocking + +### 7.4.1 General + +The adjacent channel selectivity (ACS), general blocking and narrowband blocking characteristics are measures of the receiver unit ability to receive a wanted signal at its assigned channel at the *TAB connector* in the presence of an unwanted interferer inside the operating band. + +NOTE: For Single RAT requirements, the in-band selectivity characteristics is referred to as "adjacent channel selectivity", whereas for the MSR requirements, the corresponding property is referred to as "general blocking" since the adjacent frequency range may not carry a channel addressable from the interfered carrier. + +The in-band blocking requirement applies from $F_{UL\_low} - \Delta f_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ , excluding the downlink frequency range of the FDD *operating band*. The values of $\Delta f_{OOB}$ are defined in table 7.4.1-1. + +**Table 7.4.1-1: $\Delta f_{OOB}$ offset for operating bands** + +| Operating band characteristics | $\Delta f_{OOB}$ [MHz] | +|----------------------------------------------------------|------------------------| +| $F_{UL\_high} - F_{UL\_low} < 100$ MHz | 20 | +| $100$ MHz $\leq F_{UL\_high} - F_{UL\_low} \leq 900$ MHz | 60 | + +### 7.4.2 Minimum requirement for MSR operation + +#### 7.4.2.1 General minimum requirement + +For the general blocking requirement, the interfering signal shall be a UTRA FDD signal as specified in 3GPP TS 37.104 [9], annex A.1 for a UTRA, E-UTRA or NR ( $\leq 20$ MHz) wanted signal. The interfering signal shall be a 20 MHz E-UTRA signal for NR wanted signal channel bandwidth greater than 20MHz. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges* applicable to each *TAB connector*. + +For *TAB connector* supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 15 MHz. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band TAB connectors*, the requirement applies in addition inside any *Inter RF Bandwidth gap* at those connectors, in case the gap size is at least 15 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal coupled to the *TAB connector*, using the parameters in tables 7.4.2.1-1 and 7.4.2.1-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any UTRA TDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.105 [7], subclause 7.2.1.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined for *BS type 1-H* in TS 38.104 [28], subclause 7.2.2. For *multi-band TAB connectors*, the requirement applies according to table 7.4.2.1-1 at those connectors for the in-band blocking frequency ranges of each supported operating band. + +**Table 7.4.2.1-1: General blocking requirement** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] (NOTE 1) | Centre Frequency of Interfering Signal | Interfering signal centre frequency minimum offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap (MHz) | +|-------------------|----------------------------------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | $-40 + y$ (NOTE 7) | $P_{\text{REFSENS}} + x$ dB (NOTE 2,5) | $F_{\text{UL\_low}} - \Delta f_{\text{O0B}}$ to $F_{\text{UL\_high}} + \Delta f_{\text{O0B}}$ (Note 7) | $\pm(7.5+z)$ (NOTE 9) | +| Medium Range BS | $-35 + y$ (NOTE 7) | $P_{\text{REFSENS}} + x$ dB (NOTE 3,5) | | | +| Local Area BS | $-30 + y$ (NOTE 7) | $P_{\text{REFSENS}} + x$ dB (NOTE 4,5) | | | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the *channel bandwidth*, see subclause 7.2.2. +NOTE 2: For WA BS supporting UTRA, "x" is equal to 6 in case of NR or E-UTRA or UTRA wanted signals. +NOTE 3: For MR BS supporting UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA wanted signal. +NOTE 4: For LA BS supporting UTRA, "x" is equal to 11 in case of NR or E-UTRA wanted signal, 6 in case of UTRA wanted signal. +NOTE 5: For a BS not supporting UTRA, x is equal to 6 for all BS classes if NR is supported, otherwise "x" is equal to 6 for WA BS or 9 for MR BS or 11 for LA BS if NR is not supported. +NOTE 6: For a BS capable of multi-band operation, "x" in Note 2, 3, 4, 5 applies in case of interfering signals that are in the in-band blocking frequency range of the operating band where the wanted signal is present or in the in-band blocking frequency range of an adjacent or overlapping operating band. For other in-band blocking frequency ranges of the interfering signal for the supported operating bands, "x" is equal to 1.4 dB. +NOTE 7: For a BS that supports NR but does not support UTRA, "y" is equal to -3 for the WA and MR BS class and -5 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. +NOTE 8: The downlink frequency range of an FDD operating band is excluded from the general blocking requirement. +NOTE 9: For NR wanted signal channel bandwidth greater than 20 MHz, $z = 22.5$ . For all other cases, $z = 0$ . + +**Table 7.4.2.1-2: Void** + +NOTE: The requirement in table 7.4.2.1-1 assumes that two operating bands, where the *downlink operating band* (see subclause 4.5 in 3GPP TS 37.104 [9]) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +## 7.4.2.2 General narrowband blocking minimum requirement + +For the general narrowband blocking requirement, the interfering signal shall be an E-UTRA 1RB signal as specified in 3GPP TS 37.104 [9], annex A.3. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *TAB connectors* supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 3 MHz. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band TAB connectors*, the requirement applies in addition inside any *Inter RF Bandwidth gap* at those connectors, in case the gap size is at least 3 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal coupled to the *TAB connector* using the parameters in table 7.4.2.2-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any UTRA TDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.105 [7], subclause 7.2.1.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined for *BS type 1-H* in TS 38.104 [28], subclause 7.2.2. + +**Table 7.4.2.2-1: Narrowband blocking requirement** + +| Base Station Type | RAT of the carrier | Wanted signal mean power [dBm] (NOTE 1, 2, 6) | Interfering signal mean power [dBm] | Interfering RB (NOTE 3) centre frequency offset from the AAS Base Station RF Bandwidth edge or edge of sub-block inside a gap [kHz] | +|-------------------|--------------------|-----------------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | E-UTRA, UTRA, NR | $P_{\text{REFSENS}} + x$ dB | -49 | $\pm(240 + m \cdot 180)$ ,
$m=0, 1, 2, 3, 4, 9, 14$
(Note 4) | +| Medium Range BS | | | -44 | | +| Local Area BS | | | -41 | $\pm(550 + m \cdot 180)$ ,
$m=0, 1, 2, 3, 4, 29, 54, 79, 99$ (Note 5) | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the AAS BS class and on the *channel bandwidth*, see subclause 7.2.2. +NOTE 2: "x" is equal to 6 dB in case of E-UTRA or UTRA or NR wanted signals. +NOTE 3: Interfering signal (E-UTRA 3 MHz) consisting of one resource block positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the AAS *Base Station RF Bandwidth edge*. +NOTE 4: Applicable for *channel bandwidths* equal to or below 20 MHz. +NOTE 5: Applicable for *channel bandwidths* above 20 MHz. +NOTE 6: 7.5 kHz shift is not applied to the wanted signal of NR. +NOTE 7: Void + +### 7.4.2.3 Additional BC3 blocking minimum requirement + +This additional requirement only applies for BS operating in the same geographical area as UTRA TDD. + +For the additional BC3 blocking requirement, the interfering signal is a 1,28 Mcps UTRA TDD signal as specified in 3GPP TS 37.104 [9], annex A.2. + +The requirement is always applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *multi-band TAB connectors*, the requirement applies in addition inside any *Inter RF Bandwidth gap* at those connectors, in case the gap size is at least 4.8 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal coupled to the *TAB connector*, using the parameters in table 7.4.2.3-1, the following requirements shall be met: + +- For any E-UTRA TDD carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA TDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.105 [7], subclause 7.2.1.2. + +**Table 7.4.2.3-1: Additional blocking requirement for BC3** + +| Operating Band | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Interfering signal centre frequency minimum offset from the Base Station RF Bandwidth edge [MHz] | +|----------------|---------------------------------------------------|-------------------------------------|--------------------------------|--------------------------------------------------------------------------------------------------| +| 33 - 39 | ( $F_{UL\_low} - 20$ ) to ( $F_{UL\_high} + 20$ ) | -40 | $P_{REFSENS} + 6$ dB (NOTE) | $\pm 2,4$ | +| 40 | ( $F_{UL\_low} - 60$ ) to ( $F_{UL\_high} + 60$ ) | -40 | $P_{REFSENS} + 6$ dB (NOTE) | $\pm 2,4$ | + +NOTE: $P_{REFSENS}$ depends on the RAT and on the *channel bandwidth*, see subclause 7.2.2. + +### 7.4.3 Minimum requirement for single RAT UTRA operation + +The single RAT UTRA FDD AAS BS of Wide Area BS class shall fulfil minimum requirements for ACS and narrowband blocking specified in 3GPP TS 25.104 [6], subclause 7.4. + +The single RAT UTRA FDD AAS BS of Medium Range BS class shall fulfil minimum requirements for ACS and narrowband blocking specified in 3GPP TS 25.104 [6], subclause 7.4. + +The single RAT UTRA FDD Local Area BS class shall fulfil minimum requirements for ACS and narrowband blocking specified in 3GPP TS 25.104 [6], subclause 7.4. + +The single RAT UTRA TDD AAS BS of Wide Area BS class shall fulfil minimum requirements for ACS and narrowband blocking specified in 3GPP TS 25.105 [7], subclause 7.4. + +The single RAT UTRA TDD AAS BS of Local Area BS class shall fulfil minimum requirements for ACS and narrowband blocking specified in 3GPP TS 25.105 [7], subclause 7.4. + +### 7.4.4 Minimum requirement for single RAT E-UTRA operation + +The single RAT E-UTRA AAS BS of Wide Area BS class shall fulfil minimum requirements for ACS and narrowband blocking specified in 3GPP TS 36.104 [8], subclause 7.5. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for ACS and narrowband blocking specified in 3GPP TS 36.104 [8], subclause 7.5. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for ACS and narrowband blocking specified in 3GPP TS 36.104 [8], subclause 7.5. + +## 7.5 Blocking + +### 7.5.1 General + +The blocking characteristics are a measure of the receiver unit ability to receive a wanted signal at the *TAB connector* at its assigned channel in the presence of an unwanted interferer. + +## 7.5.2 Minimum requirement for MSR operation + +### 7.5.2.1 General minimum requirement + +For a wanted and an interfering signal coupled to the *TAB connector* using the parameters in table 7.5.2.1-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any UTRA TDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.105 [7], subclause 7.2.1.2. +- For any NR carrier, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channel defined for *BS type I-H* in TS 38.104 [28], subclause 7.2.2. + +For *multi-band TAB connectors*, the requirement applies for each supported operating band. The in-band blocking frequency ranges of all supported operating bands according to table 7.4.2.1-1 shall be excluded from the requirement. + +The out-of-band blocking requirement applies from 1 MHz to $F_{UL\_low} - \Delta f_{OOB}$ and from $F_{UL\_high} + \Delta f_{OOB}$ up to 12750 MHz, including the downlink frequency range of the FDD *operating band* for BS supporting FDD. $\Delta f_{OOB}$ is defined in table 7.4.1-1. + +**Table 7.5.2.1-1: Blocking performance requirement** + +| Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------| +| -15 | $P_{REFSENS} + x$ dB
(NOTE1) | CW carrier | +| NOTE1: $P_{REFSENS}$ depends on the RAT, the BS class and the channel bandwidth, see subclause 7.2.
"x" is equal to 6 in case of NR, E-UTRA or UTRA wanted signals. | | | + +### 7.5.2.2 Co-location minimum requirement + +This additional blocking requirement may be applied for the protection of *AAS BS receivers* when NR, E-UTRA BS, UTRA BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with an AAS BS. + +The requirements in this subclause assume a 30 dB coupling loss between the interfering transmitter and the *AAS BS receiver* and are based on co-location with base stations of the same class. + +For a wanted and an interfering signal coupled to the *TAB connector* using the parameters in table 7.5.2.2-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any UTRA TDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.105 [7], subclause 7.2.1.2. +- For any NR carrier, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channel defined for *BS type I-H* in TS 38.104 [28], subclause 7.2.2. + +**Table 7.5.2.2-1: Blocking requirement for co-location with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|----------------------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| GSM900 | 921 - 960 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| DCS1800 | 1 805 - 1 880 (NOTE 4) | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| PCS1900 | 1 930 - 1 990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2 110 - 2 170 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1 930 - 1 990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1 805 - 1 880 (NOTE 4) | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2 110 - 2 155 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 - 885 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2 620 - 2 690 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1 844.9 - 1 879.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2 110 - 2 170 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1 475.9 - 1 495.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 - 768 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 17 | 734 - 746 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 18 or NR Band n18 | 860 - 875 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 - 890 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 791 - 821 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1 495.9 - 1 510.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3 510 - 3 590 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1 525 - 1 559 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|----------------------------------------------|----------------------------| +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1 930 - 1 995 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 859 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 27 | 852 - 869 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 28 or NR band n28 | 758 - 803 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717 - 728 | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6 \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2 350 - 2 360 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6 \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1 452 - 1 496 (NOTE-5) | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6 \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 33 | 1 900 - 1 920 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 34 or NR band n34 | 2 010 - 2 025 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 35 | 1 850 - 1 910 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 36 | 1 930 - 1 990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA TDD Band c) or E-UTRA TDD Band 37 | 1 910 - 1 930 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2 570 - 2 620 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1 880 - 1 920 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2 300 - 2 400 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2 496 - 2 690 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE1) | CW carrier | +| E-UTRA Band 42 | 3 400 - 3 600 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 43 | 3 600 - 3 800 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 44 | 703 - 803 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 48 or NR band n48 | 3550 - 3700 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 49 | 3550 - 3700 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 50 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|----------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|--------------------------------|----------------------------| +| | | | | | dB* | | +| E-UTRA Band 51 or NR band n51 | 1427 – 1432 | N/A | N/A | -6 | PREFSENS + x dB* | CW carrier | +| E-UTRA Band 52 | 3300 - 3400 MHz | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | N/A | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 - 1675 | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 – 2200 | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 66 or NR band n66 | 2110 – 2200 | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 69 | 2570 - 2620 | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 70 or NR band n70 | 1995 – 2020 | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 71 or or NR band n71 | 617 - 652 | +16 | +8 | -6 | PREFSENS + x dB* | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +16 | +8 | -6 | PREFSENS + 6dB* | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +16 | +8 | -6 | PREFSENS + 6dB* | CW carrier | +| E-UTRA Band 74 | 1475 - 1518 | +16 | +8 | -6 | PREFSENS + x dB* | CW carrier | +| NR band n77 | 3300-4200 | +16 | +8 | -6 | PREFSENS + x dB* | CW carrier | +| NR band n78 | 3300 - 3800 | +16 | +8 | -6 | PREFSENS + x dB* | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 - 746 | +16 | +8 | -6 | PREFSENS + x dB* | CW carrier | +| E-UTRA Band 87 | 420 - 425 | +16 | +8 | -6 | PREFSENS + 6dB* | CW carrier | +| E-UTRA Band 88 | 422 - 427 | +16 | +8 | -6 | PREFSENS + 6dB* | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|---------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|--------------------------------|----------------------------| +| NR Band n96 | 5925 - 7125 | N/A | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| NR band n100 | 919.4 - 925 | +16 | N/A | N/A | PREFSENS + x dB (NOTE 1) | CW carrier | +| NR Band n101 | 1900 - 1910 | +16 | N/A | N/A | PREFSENS + x dB (NOTE 1) | CW carrier | +| NR Band n102 | 5925 - 6425 | N/A | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 103 | 757 - 758 | +16 | +8 | -6 | PREFSENS + 6dB* | CW carrier | +| NR Band n105 | 612 – 652 | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | +| E-UTRA Band 106 or NR band n106 | 935 - 940 | +16 | +8 | -6 | PREFSENS + x dB (NOTE 1) | CW carrier | + +NOTE 1: PREFSENS depends on the RAT, the BS class and the *channel bandwidth*, see subclause 7.2.2. +"x" is equal to 6 dB in case of UTRA or E-UTRA or NR wanted signals. + +NOTE 2: Except for a BS operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported *uplink operating band* or in the $\Delta f_{\text{OOB}}$ immediately outside any of the supported *uplink operating band*. +For a BS operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768 - 797 MHz. + +NOTE 3: 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 or E-UTRA TDD or NR TDD with E-UTRA FDD or NR TDD on adjacent frequencies for 30 dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in 3GPP TR 25.942 [12]. + +NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1 805 - 1 850 MHz. + +NOTE 5: For an AAS BS operating in band 11,21, or 74 the requirement for co-location with Band 32 applies for interfering signal within the frequency range 1 475.9 - 1 495.9 MHz. + +NOTE 6: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can receive without special co-location requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +## 7.5.3 Minimum requirement for single RAT UTRA operation + +### 7.5.3.1 General minimum requirement + +The single RAT UTRA FDD AAS BS of Wide Area BS class shall fulfil minimum requirements for blocking specified in 3GPP TS 25.104 [6], subclause 7.5.1. + +The single RAT UTRA FDD AAS BS of Medium Range BS class shall fulfil minimum requirements for blocking specified in 3GPP TS 25.104 [6], subclause 7.5.1. + +The single RAT UTRA FDD AAS BS of Local Area BS class shall fulfil minimum requirements for blocking specified in 3GPP TS 25.104 [6], subclause 7.5.1. + +The single RAT UTRA 1,28 Mcps TDD AAS BS of Wide Area BS class shall fulfil minimum requirements for blocking specified in 3GPP TS 25.105 [7], subclause 7.5.0.2. + +The single RAT UTRA 1,28 Mcps TDD AAS BS of Local Area BS class shall fulfil minimum requirements for blocking specified in 3GPP TS 25.105 [7], subclause 7.5.0.2. + +### 7.5.3.2 Co-location minimum requirement + +The single RAT UTRA FDD AAS BS of Wide Area BS class may optionally fulfil minimum requirements for co-location blocking specified in 3GPP TS 25.104 [6], subclause 7.5.2. + +The single RAT UTRA FDD AAS BS of Medium Range BS class may optionally fulfil minimum requirements for co-location blocking specified in 3GPP TS 25.104 [6], subclause 7.5.2. + +The single RAT UTRA FDD AAS BS of Local Area BS class may optionally fulfil minimum requirements for co-location blocking specified in 3GPP TS 25.104 [6], subclause 7.5.2. + +The single RAT UTRA 1,28 Mcps TDD AAS BS of Wide Area BS class may optionally fulfil minimum requirements for co-location blocking specified in 3GPP TS 25.105 [7], subclause 7.5.1.2. + +The single RAT UTRA 1,28 Mcps TDD AAS BS of Local Area BS class may optionally fulfil minimum requirements for co-location blocking specified in 3GPP TS 25.105 [7], subclause 7.5.1.2. + +## 7.5.4 Minimum requirement for single RAT E-UTRA operation + +### 7.5.4.1 General minimum requirement + +For E-UTRA, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with a wanted and an interfering signal coupled to BS antenna input using the parameters in Tables 7.5.4.1-1, 7.5.4.1-2, 7.5.4.1-3 and 7.5.4.1-4. The reference measurement channel is defined in 3GPP TS 36.104 [8], subclause 7.2.1. + +The blocking requirement is applicable outside the Base Station RF Bandwidth or Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Radio Bandwidth edges. + +For a BS operating in non-contiguous spectrum within any operating band, the blocking requirement applies in addition inside any sub-block gap, in case the sub-block gap size is at least as wide as twice the interfering signal minimum offset in Table 7.5.4.1-4. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +For a BS capable of multi-band operation, the requirement in the in-band blocking frequency ranges applies for each supported operating band. The requirement applies in addition inside any Inter RF Bandwidth gap, in case the Inter RF Bandwidth gap size is at least as wide as twice the interfering signal minimum offset in Table 7.5.4.1-4. + +For a BS capable of multi-band operation, the requirement in the out-of-band blocking frequency ranges apply for each operating band, with the exception that the in-band blocking frequency ranges of all supported operating bands according to Tables 7.5.4.1-1, 7.5.4.1-2 and 7.5.4.1-3 shall be excluded from the out-of-band blocking requirement. + +**Table 7.5.4.1-1: Blocking performance requirement for Wide Area BS for E-UTRA** + +| Operating Band | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Interfering signal centre frequency minimum offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of Interfering Signal | +|---------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1-7, 9-11, 13, 14, 18, 19, 21-23, 24, 27, 30, 33-39, 45, 50, 54, 65, 66, 68, 70 | (F UL_low -20) to (F UL_high +20) | -43 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +20) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 40-44, 48, 52 | (F UL_low -60) to (F UL_high +60) | -43 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -60)
(F UL_high +60) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 8, 26, 28 | (F UL_low -20) to (F UL_high +10) | -43 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +10) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 12 | (F UL_low -20) to (F UL_high +13) | -43 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +13) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 17 | (F UL_low -20) to (F UL_high +18) | -43 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +18) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 20, 71 | (F UL_low -11) to (F UL_high +20) | -43 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -11)
(F UL_high +20) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 25 | (F UL_low -20) to (F UL_high +15) | -43 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +15) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 31, 72, 73, 74, 87, 88 | (F UL_low -20) to (F UL_high +5) | -43 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +5) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 85 | (F UL_low -20) to (F UL_high +12) | -43 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +12) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | + +Note\*: PREFSENS depends on the channel bandwidth as specified in 3GPP TS 36.104 [8], subclause 7.2.1. +Note\*\*: For a BS capable of multiband operation, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, and not in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to PREFSENS + 1.4 dB. + +NOTE: Table 7.5.4.1-1 assumes that two operating bands, where the downlink operating band of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.5.4.1-2: Blocking performance requirement for Local Area BS for E-UTRA** + +| Operating Band | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Interfering signal centre frequency minimum offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of Interfering Signal | +|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1-7, 9-11, 13, 14, 18, 19, 21-23, 24, 27, 30, 33-39, 45, 50, 51, 54, 65, 66, 68, 70 | (F UL_low -20) to (F UL_high +20) | -35 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +20) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 40-44, 48, 52 | (F UL_low -60) to (F UL_high +60) | -35 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -60)
(F UL_high +60) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 8, 26, 28 | (F UL_low -20) to (F UL_high +10) | -35 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +10) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 12 | (F UL_low -20) to (F UL_high +13) | -35 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +13) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 17 | (F UL_low -20) to (F UL_high +18) | -35 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +18) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 20, 71 | (F UL_low -11) to (F UL_high +20) | -35 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -11)
(F UL_high +20) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 25 | (F UL_low -20) to (F UL_high +15) | -35 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +15) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 31, 72, 73, 74, 87, 88 | (F UL_low -20) to (F UL_high +5) | -35 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +5) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 85 | (F UL_low -20) to (F UL_high +12) | -35 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +12) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | + +Note\*: PREFSENS depends on the channel bandwidth as specified in 3GPP TS 36.104 [8], subclause 7.2.1. + +Note\*\*: For a BS capable of multiband operation, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, and not in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to PREFSENS + 1.4 dB. + +NOTE: Table 7.5.4.1-2 assumes that two operating bands, where the downlink operating band of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.5.4.1-3: Blocking performance requirement for Medium Range BS for E-UTRA** + +| Operating Band | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Interfering signal centre frequency minimum offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of Interfering Signal | +|---------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1-7, 9-11, 13, 14, 18, 19, 21-23, 24, 27, 30, 33-39, 45, 50, 54, 65, 66, 68, 70 | (F UL_low -20) to (F UL_high +20) | -38 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +20) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 40-44, 48, 52 | (F UL_low -60) to (F UL_high +60) | -38 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -60)
(F UL_high +60) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 8, 26, 28 | (F UL_low -20) to (F UL_high +10) | -38 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +10) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 12 | (F UL_low -20) to (F UL_high +13) | -38 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +13) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 17 | (F UL_low -20) to (F UL_high +18) | -38 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +18) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 20, 71 | (F UL_low -11) to (F UL_high +20) | -38 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -11)
(F UL_high +20) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 25 | (F UL_low -20) to (F UL_high +15) | -38 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +15) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 31, 72, 73, 74, 87, 88 | (F UL_low -20) to (F UL_high +5) | -38 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +5) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | +| 85 | (F UL_low -20) to (F UL_high +12) | -38 | P REFSENS +6dB* | See table 7.5.4.1-4 | See table 7.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +12) to 12750 | -15 | P REFSENS +6dB* | — | CW carrier | + +Note\*: PREFSENS depends on the channel bandwidth as specified in 3GPP TS 36.104 [8], subclause 7.2.1. +Note\*\*: For a BS capable of multiband operation, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, and not in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to PREFSENS + 1.4 dB. + +NOTE: Table 7.5.4.1-3 assumes that two operating bands, where the downlink operating band of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.5.4.1-4: Interfering signals for blocking performance requirement** + +| E-UTRA channel BW of the lowest/highest carrier received [MHz] | Interfering signal centre frequency minimum offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of interfering signal | +|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| 1.4 | ±2.1 | 1.4 MHz E-UTRA signal | +| 3 | ±4.5 | 3 MHz E-UTRA signal | +| 5 | ±7.5 | 5 MHz E-UTRA signal | +| 10 | ±7.5 | 5 MHz E-UTRA signal | +| 15 | ±7.5 | 5 MHz E-UTRA signal | +| 20 | ±7.5 | 5 MHz E-UTRA signal (Note 1) | +| 20 | ±30 | 20 MHz E-UTRA signal (Note 2) | + +## 7.5.4.2 Co-location minimum requirement + +The single RAT E-UTRA AAS BS of Wide Area BS class may optionally fulfil minimum requirements for co-location blocking specified in 3GPP TS 36.104 [8], subclause 7.6.2. + +The single RAT E-UTRA AAS BS of Medium Range BS class may optionally fulfil minimum requirements for co-location blocking specified in 3GPP TS 36.104 [8], subclause 7.6.2. + +The single RAT E-UTRA AAS BS of Local Area BS class may optionally fulfil minimum requirements for co-location blocking specified in 3GPP TS 36.104 [8], subclause 7.6.2. + +# 7.6 Receiver spurious emissions + +## 7.6.1 General + +The receiver spurious emissions power is the power of emissions generated or amplified in a receiver unit that appear at the *TAB connector*. The requirements apply to all AAS BS with separate RX and TX *TAB connectors*. + +NOTE: In this case for FDD AAS BS the test is performed when both TX and RX are ON, with the TX *TAB connector* terminated. + +For a *TAB connector* supporting both RX and TX in TDD, the requirements apply during the *transmitter OFF period*. For a *TAB connector* supporting both RX and TX in FDD, the receiver spurious requirements are superseded by the TX spurious requirements in subclause 6.6.6. + +For RX only *multi-band TAB connector(s)*, the RX spurious emissions requirements are subject to exclusion zones in each supported operating band. For *multi-band TAB connector(s)* that both transmit and receive in operating band supporting TDD, RX spurious emissions requirements are applicable during the TX OFF period, and are subject to exclusion zones in each supported operating band. The unwanted emission level limit of a *TAB connector RX min cell group* is in general defined by the unwanted emission *basic limit* which is the same as the corresponding applicable *non-AAS BS* per transmitter requirement specified in 3GPP TS 25.104 [2], 3GPP TS 25.105 [3], 3GPP TS 36.104 [4] or 3GPP TS 37.104 [5], and its scaling by $N_{RXU, countedpercell}$ . The *basic limits* and corresponding scaling are defined in each relevant subclause. The receiver spurious emission requirements are applied per the *TAB connector RX min cell groups* for all the configurations supported by the AAS BS. + +## 7.6.2 Minimum requirement for MSR operation + +### 7.6.2.1 General minimum requirement + +The general MSR RX spurious emission *basic limits* are provided in table 7.6.2.1-1. + +**Table 7.6.2.1-1: General spurious emissions *basic limits*** + +| Frequency range | Basic limits | Measurement bandwidth | NOTE | +|--------------------------------------------------------------------------------------------------|---------------------|-----------------------|------------------------| +| 30MHz - 1 GHz | -57 dBm | 100 kHz | Note 1 | +| 1 GHz - 12.75 GHz | -47 dBm | 1 MHz | Note 1, Note 2 | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -47 dBm | 1 MHz | Note 1, Note 2, Note 3 | + +NOTE 1: *Measurement bandwidths* as in ITU-R SM.329 [14], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [14], s2.5 table 1. +NOTE 3: This spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the UL *operating band* is reaching beyond 12.75 GHz. +NOTE 4: The frequency range from $F_{BW, RF, DL, low} - \Delta f_{OBUE}$ (i.e. $\Delta f_{OBUE}$ below the lowest frequency of the BS transmitter *operating band*) to $F_{BW, RF, DL, high} + \Delta f_{OBUE}$ (i.e. $\Delta f_{OBUE}$ above the highest frequency of the BS transmitter *operating band*) may be excluded from the requirement. $\Delta f_{OBUE}$ is defined in clause 6.6.1. For *multi-band TAB connectors*, the exclusion applies for all supported operating bands for those connectors. + +The RX spurious emissions requirements for an MSR AAS BS are that for each applicable *basic limit* specified in table 7.6.2.1-1 for each *TAB connector RX min cell group*, the power sum of emissions at the *TAB connectors* of the *TAB connector RX min cell group* shall not exceed an AAS BS limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{RXU, countedpercell})$ , unless stated differently in regional regulation. + +In addition to the *basic limits* in table 7.6.2.1-1, additional spurious emissions requirements in 3GPP TS 37.104 [9], subclause 6.6.1.3 form *basic limits* for additional receiver spurious emission requirements. + +In case of FDD BS (for BC1 and BC2), the levels specified for Protection of the BS receivers of own or different BS in 3GPP TS 37.104 [9], subclause 6.6.1.2 form *basic limits* for additional receiver spurious emission requirements. + +In addition, the requirements for co-location with other base stations specified in 3GPP TS 37.104 [9], subclause 6.6.1.4 may also form *basic limits* for co-location spurious emission requirements. + +NOTE: Conformance to the *AAS BS receiver* spurious emissions requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the spurious emissions power measured on each *TAB connector* in the *TAB connector RX min cell group* shall be less than or equal to the AAS BS limit as defined above for the respective frequency span. + +Or + +- 2) The spurious emissions power at each *TAB connector* shall be less than or equal to the AAS BS limit as defined above for the respective frequency span, scaled by $-10\log_{10}(n)$ , where $n$ is the number of *TAB connectors* in the *TAB connector RX min cell group*. + +## 7.6.3 Minimum requirement for single RAT UTRA operation + +The single RAT UTRA FDD wide area, medium range area and local area RX spurious emissions *basic limits* are the same as those specified in 3GPP TS 25.104 [6], subclause 7.7.1. + +The single RAT UTRA TDD wide area and local area RX spurious emissions *basic limits* are the same as those specified in 3GPP TS 25.105 [7], subclause 7.7.1.2. + +The RX spurious emissions requirements for a single RAT UTRA AAS BS are that for each applicable *basic limit* as specified in 3GPP TS 25.104 [6] or 3GPP TS 25.105 [7], for each *TAB connector RX min cell group*, the power sum of emissions at the *TAB connectors* of the *TAB connector RX min cell group* shall not exceed an AAS BS limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{\text{RXU, counted per cell}})$ , unless stated differently in regional regulation. + +NOTE: Conformance to the *AAS BS receiver* spurious emissions requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the spurious emissions power measured on each *TAB connector* in the *TAB connector RX min cell group* shall be less than or equal to the AAS BS limit as defined above for the respective frequency span. + +Or + +- 2) The spurious emissions power at each *TAB connector* shall be less than or equal to the AAS BS limit as defined above for the respective frequency span, scaled by $-10\log_{10}(n)$ , where *n* is the number of *TAB connectors* in the *TAB connector RX min cell group*. + +## 7.6.4 Minimum requirement for single RAT E-UTRA operation + +The single RAT E-UTRA wide area, medium range area and local area RX spurious emissions *basic limits* are the same as those specified in 3GPP TS 36.104 [8], subclause 7.7.1 with the exception that the frequency range around the band edge (within which the requirement is not applicable) is $\Delta f_{\text{OBUE}}$ . + +The RX spurious emissions requirements for a single RAT E-UTRA AAS BS are that for each applicable *basic limit* specified in 3GPP TS 36.104 [4] for each *TAB connector RX min cell group*, the power sum of emissions at the *TAB connectors* of the *TAB connector RX min cell group* shall not exceed an AAS limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{\text{RXU, counted per cell}})$ , unless stated differently in regional regulation. + +NOTE: Conformance to the *AAS BS receiver* spurious emissions requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector RX min cell group* shall be less than or equal to the AAS BS limit as defined above for the respective frequency span. + +Or + +- 2) The spurious emission power at each *TAB connector* shall be less than or equal to the AAS BS limit as defined above for the respective frequency span, scaled by $-10\log_{10}(n)$ , where *n* is the number of *TAB connectors* in the *TAB connector RX min cell group*. + +## 7.7 Receiver intermodulation + +### 7.7.1 General + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver unit to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. The requirement applies per *TAB connector*. + +### 7.7.2 Minimum requirement for MSR operation + +#### 7.7.2.1 General intermodulation minimum requirement + +Interfering signals shall be a CW signal and an E-UTRA or UTRA signal as specified in 3GPP TS 37.104 [9], annex A. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *multi-band TAB connectors*, the requirement applies in addition inside any *Inter RF Bandwidth gap* at those connectors, in case the gap size is at least twice as wide as the UTRA/E-UTRA interfering signal centre frequency offset from the *Base Station RF Bandwidth edge*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted signal at the assigned channel frequency and two interfering signals coupled to the *TAB connector*, using the parameters in tables 7.7.2.1-1 and 7.7.2.1-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any UTRA TDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.105 [7], subclause 7.2.1.2. +- For any NR carrier, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channel defined for *BS type 1-H* in TS 38.104 [28], subclause 7.2.2 + +**Table 7.7.2.1-1: General intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] | Type of interfering signals | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------|--| +| Wide Area BS | -48 + y (NOTE 6) | $P_{\text{REFSENS}} + x$ dB (NOTE 2, 5) | See table 7.7.2.1-2 | | +| Medium Range BS | -44 + y (NOTE 6) | $P_{\text{REFSENS}} + x$ dB (NOTE 3, 5) | | | +| Local Area BS | -38 + y (NOTE 6) | $P_{\text{REFSENS}} + x$ dB (NOTE 4, 5) | | | +| NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth , see subclause 7.2.2. | | | | | +| NOTE 2: For WA BS supporting UTRA, "x" is equal to 6 in case of NR or E-UTRA or UTRA wanted signals. | | | | | +| NOTE 3: For MR BS supporting UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA wanted signal. | | | | | +| NOTE 4: For LA BS supporting UTRA, "x" is equal to 12 in case of NR or E-UTRA wanted signals, 6 in case of UTRA wanted signal. | | | | | +| NOTE 5: For a BS not supporting UTRA, x is equal to 6 for all BS classes if NR is supported, otherwise x is equal to 6 for WA BS or 9 for MR or 12 for LA BS if NR is not supported. | | | | | +| NOTE 6: For a BS that supports NR but not UTRA; "y" is equal to -4 for the WA BS class, -3 for the MR BS class and -6 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. | | | | | + +**Table 7.7.2.1-2: Interfering signals for intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge | Interfering signal centre frequency offset from the Base Station RF Bandwidth edge [MHz] | Type of interfering signal | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------------------| +| E-UTRA 1.4 MHz | ±2,0 (BC1 and BC3) /
±2,1 (BC2) | CW | +| | ±4,9 | 1,4 MHz E-UTRA signal | +| E-UTRA 3 MHz | ±4,4 (BC1 and BC3) /
±4,5 (BC2) | CW | +| | ±10,5 | 3 MHz E-UTRA signal | +| UTRA FDD and E-UTRA 5 MHz | ±7,5 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| E-UTRA 10 MHz | ±7,375 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| E-UTRA 15 MHz | ±7,25 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| E-UTRA 20 MHz | ±7,125 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| GSM/EDGE | ±7,575 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| 1,28 Mcps UTRA TDD | ±2,3 (BC3) | CW | +| | ±5,6 (BC3) | 1,28 Mcps UTRA TDD signal | +| NR 5 MHz | ±7,5 | CW | +| | ±17,5 | 5MHz E-UTRA signal | +| NR 10 MHz | ±7,465 | CW | +| | ±17,5 | 5MHz E-UTRA signal | +| NR 15 MHz | ±7,43 | CW | +| | ±17,5 | 5MHz E-UTRA signal | +| NR 20 MHz | ±7,395 | CW | +| | ±17,5 | 5MHz E-UTRA signal | +| NR 25 MHz | ±7,465 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 30 MHz | ±7,43 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 35 MHz | ±7,44 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 40 MHz | ±7,45 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 45 MHz | ±7,37 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 50 MHz | ±7,35 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 60 MHz | ±7,49 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 70 MHz | ±7,42 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 80 MHz | ±7,44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 90 MHz | ±7,46 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 100 MHz | ±7,48 | CW | +| | ±25 | 20MHz E-UTRA signal | + +## 7.7.2.2 General narrowband intermodulation minimum requirement + +Interfering signals shall be a CW signal and an E-UTRA 1RB signal as specified in 3GPP TS 37.104 [9], annex A. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *TAB connector* supporting operation in *non-contiguous spectrum* within each supported operating band, the requirement applies in addition inside any *sub-block gap* in case the *sub-block gap* is at least as wide as the *channel bandwidth* of the E-UTRA interfering signal in table 7.7.2.2-2. The interfering signal offset is defined relative to the *sub-block* edges inside the gap. + +For *multi-band TAB connectors*, the requirement applies in addition inside any *Inter RF Bandwidth gap* at those connectors in case the gap size is at least as wide as the E-UTRA interfering signal in table 7.7.2.2-2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted signal at the assigned channel frequency and two interfering signals coupled to the *TAB connector*, using the parameters in tables 7.7.2.2-1 and 7.7.2.2-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any UTRA TDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.105 [7], subclause 7.2.1.2. +- For any NR carrier, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channel defined for *BS type I-H* in TS 38.104 [28], subclause 7.2.2 + +**Table 7.7.2.2-1: General narrowband intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] | Type of interfering signals | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------|-----------------------------| +| Wide Area BS | -52 | $P_{\text{REFSENS}} + x$ dB (NOTE) | See table 7.7.2.2-2 | +| Medium Range BS | -47 | | | +| Local Area BS | -44 | | | +| NOTE: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth , see subclause 7.2.2. "x" is equal to 6 dB in case of E-UTRA or UTRA or NR wanted signals. | | | | + +**Table 7.7.2.2-2: Interfering signals for narrowband intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge or edge of the sub-block | CW or 1RB interfering signal centre frequency offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap [kHz] | Type of interfering signal | +|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| E-UTRA 1.4 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±970 (BC1 and BC3) / ±790 (BC2) | 1,4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 3 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±960 (BC1 and BC3) / ±780 (BC2) | 3,0 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 5 MHz | ±360 | CW | +| | ±1 060 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 10 MHz (NOTE 2) | ±325 | CW | +| | ±1 240 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 15 MHz (NOTE 2) | ±380 | CW | +| | ±1 600 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 20 MHz (NOTE 2) | ±345 | CW | +| | ±1 780 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| UTRA FDD | ±345 (BC1 and BC2) | CW | +| | ±1 780 (BC1 and BC2) | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| GSM/EDGE | ±340 | CW | +| | ±880 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| 1,28 Mcps UTRA TDD | ±190 (BC3) | CW | +| | ±970 (BC3) | 1,4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| NR 5 MHz | ±360 | CW | +| | ±1420 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 10 MHz | ±370 | CW | +| | ±1960 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 15 MHz (Note 2) | ±380 | CW | +| | ±1960 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 20 MHz (Note 2) | ±390 | CW | +| | ±2320 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 25 MHz (Note 2) | ±325 | CW | +| | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 30 MHz (Note 2) | ±335 | CW | +| | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 35 MHz (Note 2) | ±345 | CW | +| | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 40 MHz (Note 2) | ±355 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 45 MHz (Note 2) | ±365 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 50 MHz (Note 2) | ±375 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 60 MHz (Note 2) | ±395 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 70 MHz (Note 2) | ±415 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 80 MHz (Note 2) | ±435 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 90 MHz (Note | ±365 | CW | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------| +| 2) | ±2530 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 100 MHz (Note 2) | ±385 | CW | +| 2) | ±2530 | E-UTRA signal, 1 RB (NOTE 1) | +| NOTE 1: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the Base Station RF Bandwidth edge . | | | +| NOTE 2: This requirement shall apply only for an E-UTRA FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals. | | | + +### 7.7.3 Minimum requirement for single RAT UTRA operation + +The single RAT UTRA FDD AAS BS of Wide Area BS class shall fulfil minimum requirements for receiver intermodulation specified in 3GPP TS 25.104 [6], subclause 7.6.1. + +The single RAT UTRA FDD AAS BS of Medium Range BS class shall fulfil minimum requirements for receiver intermodulation specified in 3GPP TS 25.104 [6], subclause 7.6.1. + +The single RAT UTRA FDD AAS BS of Local Area BS class shall fulfil minimum requirements for receiver intermodulation specified in 3GPP TS 25.104 [6], subclause 7.6.1. + +The single RAT UTRA TDD AAS BS of Wide Area BS class shall fulfil minimum requirements for receiver intermodulation specified in 3GPP TS 25.105 [7], subclause 7.6.1.2. + +The single RAT UTRA TDD AAS BS of Local Area BS class shall fulfil minimum requirements for receiver intermodulation specified in 3GPP TS 25.105 [7], subclause 7.6.1.2. + +### 7.7.4 Minimum requirement for single RAT E- UTRA operation + +The single RAT E-UTRA AAS BS of Wide Area BS class shall fulfil minimum requirements for receiver intermodulation specified in 3GPP TS 36.104 [8], subclause 7.8. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for receiver intermodulation specified in 3GPP TS 36.104 [8], subclause 7.8. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for receiver intermodulation specified in 3GPP TS 36.104 [8], subclause 7.8. + +## 7.8 In-channel selectivity + +### 7.8.1 General + +In-channel selectivity (ICS) is a measure of the receiver unit ability to receive a wanted signal at its assigned resource block locations in the presence of an interfering signal received at a larger power spectral density. In this condition a throughput requirement shall be met for a specified reference measurement channel. The requirement applies per *TAB connector*. + +### 7.8.2 Minimum requirement for MSR operation + +For E-UTRA, the minimum requirement for in-channel selectivity is specified in subclause 7.8.4. + +For NR, the minimum requirement for in-channel selectivity is specified in 3GPP TS 38.104 [28] for *BS type 1-H* in subclause 7.8.2. + +This requirement is not applicable for UTRA operation. + +### 7.8.3 Minimum requirement for single RAT UTRA operation + +This requirement is not applicable for UTRA BS. + +## 7.8.4 Minimum requirement for single RAT E-UTRA operation + +The single RAT E-UTRA AAS BS of Wide Area BS class shall fulfil minimum requirements for in-channel selectivity specified in 3GPP TS 36.104 [8], subclause 7.4.1. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for in-channel selectivity specified in 3GPP TS 36.104 [8], subclause 7.4.1. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for in-channel selectivity specified in 3GPP TS 36.104 [8], subclause 7.4.1. + +The interfering signal shall be an E-UTRA signal as specified in 3GPP TS 36.104 [8], annex C and shall be time aligned with the wanted signal. + +--- + +# 8 Performance requirements + +## 8.1 General + +Performance requirements specify the ability of the AAS BS to correctly demodulate signals in various conditions and configurations. + +The demodulation requirements for an AAS BS are the same as *non-AAS BS* demodulation requirements specified for: + +- *Single RAT UTRA operation* in TS 25.104 [9] clause 8 for FDD operation, and in TS 25.105 [10] clause 8 for TDD operation, +- *Single RAT E-UTRA operation* in TS 36.104 [11], subclauses 8.2 – 8.4 and 8.6 – 8.7. + +### 8.1.1 UTRA operation + +Performance requirements for *single RAT UTRA operation* in FDD are specified for the measurement channels defined in 3GPP TS 25.104 [2] and 3GPP TS 25.105 [3]. The requirements only apply to those measurement channels that are supported by AAS BS. For FRC8 in 3GPP TS 25.104 [2] the non E-DPCCH boosting and E-DPCCH boosting requirement only apply for the option supported by the AAS BS. The performance requirements for the high speed train scenarios defined in 3GPP TS 25.104 [2] and 3GPP TS 25.105 [3] are optional. + +Unless stated otherwise, performance requirements apply for a single cell only. Performance requirements for an AAS BS supporting UTRA FDD DC-HSUPA or DB-DC-HSUPA and UTRA TDD MC-HSUPA are defined in terms of single carrier requirements. For FDD operation the requirements in clause 8 shall be met with the transmitter unit(s) associated with the *TAB connectors(s)* in the operating band ON. + +NOTE: In normal operating conditions the *TAB connectors(s)* in UTRA FDD operation are configured to transmit and receive at the same time. The transmitter unit(s) associated with the *TAB connectors* may be OFF for some of the tests as specified in TS 37.145-1 [29] and TS 37.145-2 [30]. + +In the referred UTRA specifications and in this clause, the term BS with RX diversity refers to performance requirements for two *demodulation branches*, and BS without RX diversity refers to performance requirements for one *demodulation branch*. + +For AAS BS with RX diversity, only the BS performance requirements with RX diversity apply, the required $E_b/N_0$ for UTRA FDD and $\hat{I}_{or}/I_{oc}$ for UTRA TDD shall be applied separately for each *demodulation branch*. + +For AAS BS without RX diversity, only the BS performance requirements without RX diversity apply. The required $E_b/N_0$ for UTRA FDD and $\hat{I}_{or}/I_{oc}$ for UTRA TDD shall be applied for each AAS BS *demodulation branch*. + +The $E_b/N_0$ used for UTRA FDD is defined as: + +Where: + +is the received total energy of DPDCH, DPCCH, S-DPCCH, HS-DPCCH, E-DPDCH, S-E-DPDCH, E-DPCCH and S-E-DPCCH per PN chip per *demodulation branch* from all branches + +is the total one-sided noise power spectral density due to all noise sources + +is the number of chips per frame + +is the number of information bits in DTCH excluding CRC bits per frame + +**Table 8.1.1-1: Summary of AAS BS performance targets for single RAT UTRA operation** + +| Physical channel | Measurement channel | Static | Multi-path Case 1 | Multi-path Case 2 | Multi-path Case 3 | Moving (NOTE 1) | Birth / Death (NOTE 1) | High Speed Train | +|------------------|---------------------|------------------------------------------|------------------------------------------|------------------------------------------|-------------------------------------------------------------|------------------------------------------|------------------------------------------|---------------------------------------------------| +| | | Performance metric | | | | | | | +| DCH | 12.2 kbps | BLER<10 -2 | BLER<10 -2 | 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 | BLER<10 -1 , 10 -2 | BLER<10 -1 , 10 -2 (NOTE 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 1: UTRA FDD only. + +NOTE 2: UTRA TDD only. + +NOTE 3: If not stated otherwise, the above performance targets are applicable to UTRA TDD and to UTRA FDD. + +NOTE 4: In case of multiple BLER level thresholds listed for single requirement and measurement channel combination, those BLER level values are reflected by set multiple requirements in 3GPP TS 25.104 [2], or 3GPP TS 25.105 [3]. + +## 8.1.2 E-UTRA operation + +Performance requirements for the AAS BS are specified for the fixed reference channels (FRC) and propagation conditions defined in 3GPP TS 36.104 [8] annex A and annex B, respectively. The requirements only apply to those FRCs that are supported by the AAS BS. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for an AAS BS E-UTRA supporting *carrier aggregation* are defined in terms of single carrier requirements. For FDD operation the requirements shall be met with the transmitter unit(s) associated with the *TAB connectors(s)* in the operating band ON. + +NOTE: In normal operating conditions *TAB connectors* in FDD operation are configured to transmit and receive at the same time. The transmitter unit(s) associated with the *TAB connectors* may be OFF for some of the tests as specified in TS 37.145-1 [29] and TS 37.145-2 [30]. + +In the referred E-UTRA specification, the term "RX antennas" refers to *demodulation branches* (and not physical antennas). + +The SNR used in this clause is specified based on a single carrier and defined as: + +$$\text{SNR} = S / N$$ + +Where: + +S is the total signal energy in the subframe on a single *TAB connector*. + +N is the noise energy in a bandwidth corresponding to the *transmission bandwidth* over the duration of a subframe. + +For *enhanced performance requirements type A* and *type B*, the SINR used in this clause is specified based on a single carrier and defined as: + +$$SINR = S/N'$$ + +Where: + +$S$ is the total signal energy of one intra-cell UE in the subframe on a single *TAB connector*. + +$N'$ is the summation of the received energy of the strongest inter-cell interferers explicitly defined in a test procedure plus the white noise energy $N$ , in a bandwidth corresponding to the *transmission bandwidth* over the duration of a subframe on a single *TAB connector*. The respective energy of each inter-cell interferer relative to $N'$ is defined by its associated DIP value + +## 8.2 Minimum requirements for MSR operation + +For *single RAT UTRA operation*, minimum requirements for demodulation performance are specified in subclause 8.3. + +For *single RAT E-UTRA operation*, minimum requirements for demodulation performance are specified in subclause 8.4. + +## 8.3 Minimum requirements for UTRA operation + +The *single RAT UTRA operation* in FDD shall fulfil all mandatory BS demodulation performance requirements specified in subclauses 8.2 to 8.12 of 3GPP TS 25.104 [6]. + +The *single RAT UTRA operation* in TDD shall fulfil all mandatory BS demodulation performance requirements specified in subclauses 8.2 to 8.5 of 3GPP TS 25.105 [7]. + +In the referred UTRA specifications, the term BS with RX diversity refers to performance requirements for two *demodulation branches*, and BS without RX diversity refers to performance requirements for one *demodulation branch*. + +## 8.4 Minimum requirements for E-UTRA operation + +The *single RAT E-UTRA operation* shall fulfil all mandatory BS demodulation performance requirements specified in subclauses 8.2 to 8.4 of 3GPP TS 36.104 [8]. + +In the referred E-UTRA specification, the term "RX antennas" refers to *demodulation branches* (i.e. not physical antennas). + +# 9 Radiated transmitter characteristics + +## 9.1 General + +Radiated transmitter characteristics requirements apply on the AAS BS including all its functional components active and for all foreseen modes of operation of the AAS BS unless otherwise stated. + +Unless otherwise stated, the transmitter characteristics are specified with a full complement of transceiver units for the configuration in normal operating conditions. + +The manufacturer shall declare the minimum number of supported geographical cells (i.e. geographical areas). The minimum number of supported geographical cells ( $N_{cells}$ ) relates to the AAS BS setting with the minimum amount of cell splitting supported. + +*OTA AAS BS* transmitter requirements apply per geographical cell . + +Radiated emissions with requirements described as TRP are defined as follows: + +where $P_D(r, \theta, \phi)$ is the power density in $\text{W/m}^2$ at a distance $r$ of two orthogonal polarizations. + +## 9.2 Radiated transmit power + +### 9.2.1 General + +An AAS BS is declared to support one or more beams. Radiated transmit power is defined as the EIRP level for a declared beam at a specific *beam peak direction*. + +For each beam, the requirement is based on declaration of a beam identity, *reference beam direction pair*, *beamwidth*, *rated beam EIRP*, *OTA peak directions set*, the *beam direction pairs* at the maximum steering directions and their associated *rated beam EIRP* and *beamwidth(s)*. + +For a declared beam and *beam direction pair*, the *rated beam EIRP* level is the maximum power that the base station is declared to radiate at the associated *beam peak direction* during the *transmitter ON period*. + +For each *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a specific *rated beam EIRP* level may be claimed. Any claimed value shall be met within the accuracy requirement as described below. *Rated beam EIRP* is only required to be declared for the *beam direction pairs* subject to conformance testing as detailed in TS 37.145-2 [30]. + +NOTE 1: *OTA peak directions set* is set of *beam peak directions* for which the EIRP accuracy requirement is intended to be met. The *beam peak directions* are related to a corresponding contiguous range or discrete list of *beam centre directions* by the *beam direction pairs* included in the set. + +NOTE 2: A *beam direction pair* is data set consisting of the *beam centre direction* and the related *beam peak direction*. + +NOTE 3: A declared EIRP value is a value provided by the manufacturer for verification according to the conformance specification declaration requirements, whereas a claimed EIRP value is provided by the manufacturer to the equipment user for normal operation of the equipment and is not subject to formal conformance testing. + +### 9.2.2 Minimum requirement for MSR operation + +For each declared beam, in normal conditions, for any specific *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a manufacturer claimed EIRP level in the corresponding *beam peak direction* shall be achievable to within +2,2 dB and -2,2 dB of the claimed value. + +For each declared beam, in extreme conditions, for any specific *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a manufacturer claimed EIRP level in the corresponding *beam peak direction* shall be achievable to within +2,7 dB and -2,7 dB of the claimed value. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +### 9.2.3 Minimum requirement for single RAT UTRA operation + +The minimum requirement for UTRA FDD and UTRA TDD 1,28Mcps option carrier radiated transmit power is in each case same as defined in subclause 9.2.2. + +### 9.2.4 Minimum requirement for single RAT E-UTRA operation + +The minimum requirement for E-UTRA carrier radiated transmit power is same as defined in subclause 9.2.2. + +## 9.3 OTA Base Station output power + +### 9.3.1 General + +The *OTA AAS BS* base station output power is declared as TRP. + +### 9.3.2 OTA Maximum output power + +#### 9.3.2.1 General + +The rated carrier output power of the *OTA AAS BS* shall be as specified for UTRA in table 9.3.2.1-1, and for E-UTRA and NR in table 9.3.2.1-2 + +**Table 9.3.2.1-1: UTRA OTA AAS Base Station rated output power limits for BS classes** + +| OTA AAS BS class | $P_{\text{Rated,c,TRP}}$ | +|-----------------------------------------------------------------------------------------------|--------------------------| +| Wide Area BS | (NOTE) | +| Medium Range BS | $\leq 44$ dBm | +| Local Area BS | $\leq 30$ dBm | +| NOTE: There is no upper limit for the $P_{\text{Rated,c,TRP}}$ of the Wide Area Base Station. | | + +**Table 9.3.2.1-2: E-UTRA and NR OTA AAS Base Station rated output power limits for BS classes** + +| OTA AAS BS class | $P_{\text{Rated,c,TRP}}$ | +|-----------------------------------------------------------------------------------------------|--------------------------| +| Wide Area BS | (NOTE) | +| Medium Range BS | $\leq 47$ dBm | +| Local Area BS | $\leq 33$ dBm | +| NOTE: There is no upper limit for the $P_{\text{Rated,c,TRP}}$ of the Wide Area Base Station. | | + +#### 9.3.2.2 Minimum requirement for MSR operation + +##### 9.3.2.2.1 General + +In normal conditions, $P_{\text{max,c,TRP}}$ shall remain within +2,0 dB and -2,0 dB of the configured carrier TRP as declared by the manufacturer. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +##### 9.3.2.2.2 Additional requirements (regional) + +#### 9.3.2.3 Minimum requirement for single RAT UTRA operation + +The minimum requirement for single RAT UTRA BS is the same as that defined in subclause 9.3.2.2. + +#### 9.3.2.4 Minimum requirement for single RAT E-UTRA operation + +##### 9.3.2.4.1 General + +The minimum requirement for single RAT E-UTRA BS is the same as that defined in subclause 9.3.2.2. + +#### 9.3.2.4.2 Additional requirements (regional) + +### 9.3.3 OTA E-UTRA DL RS power + +#### 9.3.3.1 General + +This requirement applies to the RIB(s) transmitting primary DL RS. + +The DL RS power is the resource element power of the Downlink Reference Symbol at the RIB transmitting the DL RS for a cell. + +The absolute DL RS power is indicated on the DL-SCH. The absolute accuracy is defined as the maximum deviation between the DL RS power indicated on the DL-SCH and the DL RS power of each E-UTRA carrier. + +#### 9.3.3.2 Minimum requirement for MSR operation + +There is no DL RS power requirement for UTRA operation. + +There is no DL RS power requirement for NR operation. + +The minimum requirement for MSR E-UTRA operation is the same as that defined in subclause 9.3.6.4. + +#### 9.3.3.3 Minimum requirement for single RAT UTRA operation + +There is no DL RS power requirement for UTRA operation. + +#### 9.3.3.4 Minimum requirement for single RAT E-UTRA operation + +The DL RS power of each E-UTRA carrier shall be within $\pm 2,1$ dB of the DL RS power indicated on the DL-SCH. + +### 9.4 OTA Output power dynamics + +#### 9.4.1 General + +The requirements in subclause 9.4 apply during the *transmitter ON period*. Transmit signal quality (as specified in subclause 9.6) shall be maintained for the output power dynamics requirements. Power control is used to limit the interference level. The TA output power requirements are *single direction requirements* and apply to the *beam peak directions* associated with the *beam direction pairs* over the *OTA peak directions set*. + +#### 9.4.2 OTA UTRA Inner loop power control in the downlink + +##### 9.4.2.1 General + +Inner loop power control in the downlink is the ability of the AAS BS transmitter to adjust the transmitter output power of a code channel in accordance with the corresponding TPC symbols received in the uplink. + +##### 9.4.2.2 Minimum requirement for MSR operation + +For UTRA FDD operation; the minimum requirements for MSR AAS BS inner loop power control in the DL are the same as subclause 9.4.2.3. + +This requirement does not apply to E-UTRA operation. + +This requirement does not apply to NR operation. + +### 9.4.2.3 Minimum requirement for single RAT UTRA operation + +For UTRA FDD operation, the Single RAT AAS BS shall have the capability of setting the inner loop *code domain power* on each RIB with a step sizes of 1dB mandatory and 0.5, 1.5, 2.0 dB optional + +- The tolerance of the power control step due to inner loop power control shall be within the range shown in table 9.4.2.3-1. +- The tolerance of the combined output power change due to inner loop power control shall be within the range shown in table 9.4.2.3-2. + +**Table 9.4.2.3-1: UTRA FDD power control step tolerance** + +| Power control commands in the down link | Transmitter power control step tolerance | | | | | | | | +|-----------------------------------------|------------------------------------------|---------|------------------|----------|----------------|---------|------------------|----------| +| | 2 dB step size | | 1,5 dB step size | | 1 dB step size | | 0,5 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | Lower | Upper | +| Up (TPC command "1") | +1,0 dB | +3,0 dB | +0,75 dB | +2,25 dB | +0,5 dB | +1,5 dB | +0,25 dB | +0,75 dB | +| Down (TPC command "0") | -1,0 dB | -3,0 dB | -0,75 dB | -2,25 dB | -0,5 dB | -1,5 dB | -0,25 dB | -0,75 dB | + +**Table 9.4.2.3-2: UTRA FDD aggregated power control step range** + +| Power control commands in the down link | Transmitter aggregated power control step change after 10 consecutive equal commands (up or down) | | | | | | | | +|-----------------------------------------|---------------------------------------------------------------------------------------------------|--------|------------------|--------|----------------|--------|------------------|-------| +| | 2 dB step size | | 1,5 dB step size | | 1 dB step size | | 0,5 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | Lower | Upper | +| Up (TPC command "1") | +16 dB | +24 dB | +12 dB | +18 dB | +8 dB | +12 dB | +4 dB | +6 dB | +| Down (TPC command "0") | -16 dB | -24 dB | -12 dB | -18 dB | -8 dB | -12 dB | -4 dB | -6 dB | + +### 9.4.2.4 Minimum requirement for single RAT E-UTRA operation + +This requirement does not apply to E-UTRA operation. + +## 9.4.3 OTA Power control dynamic range + +### 9.4.3.1 General + +The power control dynamic range is the difference between the maximum and the minimum *code domain power* of a code channel for a specified reference condition. + +This requirement applies at each RIB supporting transmission in the operating band. + +This requirement applies to UTRA operation only. + +### 9.4.3.2 Minimum requirement for MSR operation + +For UTRA FDD operation; the minimum requirements for MSR *AAS BS* power control dynamic range are the same as subclause 9.4.3.3 + +This requirement does not apply to E-UTRA operation. + +This requirement does not apply to NR operation. + +### 9.4.3.3 Minimum requirement for single RAT UTRA operation + +Down link (DL) power control dynamic range shall be: + +Maximum *code domain power*: $P_{\max,c,TRP} - 3$ dB or greater + +Minimum *code domain power*: $P_{\max,c,TRP} - 28$ dB or less + +#### 9.4.3.4 Minimum requirement for single RAT E-UTRA operation + +This requirement does not apply to E-UTRA operation. + +### 9.4.4 OTA Total power dynamic range + +#### 9.4.4.1 General + +The total power dynamic range is the difference between the maximum and the minimum output power for a specified reference condition. + +This requirement applies at each RIB supporting transmission in the operating band. + +NOTE 1: The upper limit of the dynamic range is the BS maximum output power ( $P_{\text{Rated,c,TRP}}$ ). The lower limit of the dynamic range is the lowest minimum power from the AAS BS when no traffic channels are activated. + +Particularly for E-UTRA, the total power dynamic range is the difference between the maximum and the minimum transmit power of an OFDM symbol for a specified reference condition. + +NOTE 2: The upper limit of the dynamic range at a RIB is the OFDM symbol power at maximum output power ( $P_{\text{Rated,c,TRP}}$ ) when transmitting on all RBs. The lower limit of the dynamic range at a RIB is the OFDM symbol power when one resource block is transmitted. The OFDM symbol carries PDSCH or sPDSCH and not contain RS, PBCH or synchronization signals. + +#### 9.4.4.2 Minimum requirement for MSR operation + +For UTRA FDD operation; the minimum requirements for MSR AAS BS total power dynamic range are the same as subclause 9.4.4.3. + +For E-UTRA operation; the minimum requirements for MSR AAS BS total power dynamic range are the same as subclause 9.4.4.4. + +For NR operation, the minimum requirements for MSR AAS BS total power dynamic range are the same as those for BS type I-O in TS 38.104 [28] subclause 9.4.3.2. + +#### 9.4.4.3 Minimum requirement for single RAT UTRA operation + +The downlink (DL) total power dynamic range shall be 18 dB or greater. + +#### 9.4.4.4 Minimum requirement for single RAT E-UTRA operation + +The downlink (DL) total power dynamic range for each E-UTRA carrier shall be larger than or equal to the level in table 9.4.4.4-1. + +**Table 9.4.4.4-1: E-UTRA BS total power dynamic range** + +| E-UTRA
channel bandwidth [MHz] | Total power dynamic
range (dB) | +|-----------------------------------|-----------------------------------| +| 1.4 | 7.7 | +| 3 | 11.7 | +| 5 | 13.9 | +| 10 | 16.9 | +| 15 | 18.7 | +| 20 | 20 | + +The requirement does not apply to Band 46 nor Band 49. + +## 9.4.5 OTA IPDL time mask + +### 9.4.5.1 General + +To support IPDL location method in UTRA FDD operation, the AAS BS shall interrupt all transmitted signals in the downlink (i.e. common and dedicated channels). The IPDL time mask specifies the limits at the RIB output power during these idle periods. + +This requirement applies only to AAS BS supporting IPDL. The requirement applies at each RIB supporting transmission in the operating band. + +### 9.4.5.2 Minimum requirement for MSR operation + +For UTRA FDD operation; the minimum requirement for MSR AAS BS IPDL time mask is the same as subclause 9.4.5.3. + +This requirement does not apply to E-UTRA operation. + +This requirement does not apply to NR operation. + +### 9.4.5.3 Minimum requirement for single RAT UTRA operation + +The mean power measured over a period starting 27 chips after the beginning of the IPDL period and ending 27 chips before the expiration of the IPDL period shall be equal to or less than + +![Figure 9.4.5.3-1: IPDL Time Mask diagram. The diagram shows a power level P_max,c,TRP as a solid horizontal line. A dashed horizontal line is 35 dB below it. A rectangular pulse is shown, starting at the dashed line and dropping to a lower level. The duration of this pulse is labeled IP_Length. The pulse starts 27 chips after the beginning of the IPDL period and ends 27 chips before the expiration of the IPDL period. The duration of the pulse is labeled IP_Length.](352b3d74149de2a9edaaeb0e8c6851a4_img.jpg) + +$P_{\max,c,TRP} - 35 \text{ dB}$ + +The diagram illustrates the IPDL Time Mask. A solid horizontal line represents the maximum power level $P_{\max,c,TRP}$ . A dashed horizontal line is 35 dB below this level. A rectangular pulse is shown, starting at the dashed line and dropping to a lower level. The duration of this pulse is labeled $IP\_Length$ . The pulse starts 27 chips after the beginning of the IPDL period and ends 27 chips before the expiration of the IPDL period. The duration of the pulse is labeled $IP\_Length$ . + +Figure 9.4.5.3-1: IPDL Time Mask diagram. The diagram shows a power level P\_max,c,TRP as a solid horizontal line. A dashed horizontal line is 35 dB below it. A rectangular pulse is shown, starting at the dashed line and dropping to a lower level. The duration of this pulse is labeled IP\_Length. The pulse starts 27 chips after the beginning of the IPDL period and ends 27 chips before the expiration of the IPDL period. The duration of the pulse is labeled IP\_Length. + +**Figure 9.4.5.3-1: IPDL Time Mask** + +The requirement applies to all output powers within the total power dynamic range as specified in subclause 9.4.4. + +### 9.4.5.4 Minimum requirement for single RAT E-UTRA operation + +This requirement does not apply to E-UTRA operation. + +## 9.4.6 OTA RE Power control dynamic range + +### 9.4.6.1 General + +The RE power control dynamic range is the difference between the power of an RE and the average RE power for an AAS BS at maximum output power ( $P_{\text{Rated,c,TRP}}$ ) for a specified reference condition. + +This requirement applies at each RIB supporting transmission in the operating band. + +#### 9.4.6.2 Minimum requirement for MSR operation + +This requirement does not apply to UTRA operation. + +For E-UTRA operation; the minimum requirements for MSR AAS BS RE power control dynamic range are the same as in subclause 9.4.6.4. + +For NR operation, the minimum requirements for MSR AAS BS RE power control dynamic range are the same as those for *BS type 1-O* in TS 38.104 [28] subclause 9.4.2.2. + +#### 9.4.6.3 Minimum requirement for single RAT UTRA operation + +This requirement does not apply to UTRA operation. + +#### 9.4.6.4 Minimum requirement for single RAT E-UTRA operation + +The RE power control dynamic range is specified in table 9.4.6.4-1. + +**Table 9.4.6.4-1: E-UTRA BS RE power control dynamic range** + +| Modulation scheme used on the RE | RE power control dynamic range (dB) | | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| | (down) | (up) | +| QPSK (PDCCH) | -6 | +4 | +| QPSK (PDSCH) | -6 | +3 | +| QPSK (sPDCCH) | -6 | +4 | +| QPSK (sPDSCH) | -6 | +3 | +| 16QAM (PDSCH) | -3 | +3 | +| 16QAM (sPDSCH) | -3 | +3 | +| 64QAM (PDSCH) | 0 | 0 | +| 64QAM (sPDSCH) | 0 | 0 | +| 256QAM (PDSCH) | 0 | 0 | +| 1024QAM (PDSCH) | 0 | 0 | +| NOTE: | The output power per carrier ( $P_{\text{Rated,c,TRP}}$ ) shall always be less or equal to the maximum output power of the base station ( $P_{\text{Rated,t,TRP}}$ ). | | + +### 9.5 OTA Transmit ON/OFF power + +#### 9.5.1 General + +OTA transmitter ON/OFF power requirements apply only to TDD operation of E-UTRA. + +The OTA Transmit ON/OFF power requirements are co-location requirements and specified as the power sum of the supported polarization(s) at the *co-location reference antenna* conducted output(s). + +#### 9.5.2 OTA Transmitter OFF power + +##### 9.5.2.1 General + +OTA transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *Base Station RF Bandwidth(s)* centred on the central frequency of the *Base Station RF Bandwidth(s)* during the *transmitter OFF period*. N is equal to 1 for UTRA and E\_UTRA SCS/15 for NR, where SCS is Sub Carrier Spacing in kHz. + +For *multi-band RIBs* and *single band RIBs* supporting transmission in multiple bands, the requirement is only applicable during the *transmitter OFF period* in all supported operating bands. + +For AAS BS supporting intra-band contiguous CA, the transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *Aggregated BS Channel Bandwidth* $BW_{\text{Channel\_CA}}$ centred on $(F_{\text{edge,high}} + F_{\text{edge,low}})/2$ during the *transmitter OFF period*. N is equal to 1 if there are any UTRA or E-UTRA + +carriers, or for NR $N = \text{SCS}/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *Aggregated BS Channel Bandwidth*. + +### 9.5.2.2 Minimum requirement for MSR operation + +There is no OTA transmitter OFF power requirement for UTRA operation. + +For NR and E-UTRA operation, the total power from all *co-location reference antenna* conducted output(s) shall be less than -106 dBm/MHz. + +### 9.5.2.3 Minimum requirement for single RAT UTRA operation + +There is no OTA transmitter OFF power requirement for UTRA operation. + +### 9.5.2.4 Minimum requirement for single RAT E-UTRA operation + +The total power from all *co-location reference antenna* conducted output(s) shall be less than -106 dBm/MHz. + +## 9.5.3 OTA Transmitter transient period + +### 9.5.3.1 General + +The OTA *transmitter transient period* is the time period during which the transmitter unit is changing from the OFF period to the ON period or vice versa. The OTA *transmitter transient period* is illustrated in figure 9.5.3.1-1. + +![Figure 9.5.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows power level over time. The y-axis has 'ON power level (Informative)' and 'OFF power level'. The x-axis is 'Time'. The graph shows a curve representing power level. It starts at OFF power level, rises sharply during the 'Transmitter transient period' to the ON power level, stays at ON power level during the 'Transmitter ON period (DL Timeslots and DwPTS)', falls sharply during another 'Transmitter transient period' back to OFF power level, and stays at OFF power level during the 'Transmitter OFF period'. The 'UL Timeslots' are indicated above the ON power level, and 'GP and UpPTS' are indicated above the OFF power level.](cecc0df27c56332ebd6f78c3b9df631d_img.jpg) + +Figure 9.5.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows power level over time. The y-axis has 'ON power level (Informative)' and 'OFF power level'. The x-axis is 'Time'. The graph shows a curve representing power level. It starts at OFF power level, rises sharply during the 'Transmitter transient period' to the ON power level, stays at ON power level during the 'Transmitter ON period (DL Timeslots and DwPTS)', falls sharply during another 'Transmitter transient period' back to OFF power level, and stays at OFF power level during the 'Transmitter OFF period'. The 'UL Timeslots' are indicated above the ON power level, and 'GP and UpPTS' are indicated above the OFF power level. + +**Figure 9.5.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period** + +This requirement applies at each *co-location reference antenna conducted* output supporting transmission in the operating band. + +### 9.5.3.2 Minimum requirement for MSR operation + +For E-UTRA operation, the minimum requirements for MSR *AAS BS OTA transmitter transient period* shall be shorter than the values in table 9.5.3.4-1. + +For NR operation, the minimum requirements for MSR *AAS BS OTA transmitter transient period* shall be shorter than the values specified in 3GPP TS 37.104 [5] subclause 6.4.2.1. + +### 9.5.3.3 Minimum requirement for single RAT UTRA operation + +There is no OTA *Transmitter transient period* requirement for UTRA operation. + +### 9.5.3.4 Minimum requirement for single RAT E-UTRA operation + +For single RAT *AAS BS*, the OTA *transmitter transient period* shall be shorter than the values in table 9.5.3.4-1. + +**Table 9.5.3.4-1: Minimum requirements for the *transmitter transient period*** + +| Transition | Transient period length [ $\mu\text{s}$ ] | +|------------|-------------------------------------------| +| OFF to ON | 17 | +| ON to OFF | 17 | + +## 9.6 OTA Transmitted signal quality + +### 9.6.1 General + +Unless otherwise stated, the requirements in clause 9.6 apply during the *transmitter ON period*. + +### 9.6.2 OTA Frequency Error + +#### 9.6.2.1 General + +OTA frequency error is the measure of the difference between the actual AAS BS transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation. + +The OTA frequency error requirement is defined as a *single direction requirement* at the RIB and shall be met within the *OTA coverage range*. + +#### 9.6.2.2 Minimum requirement for MSR operation + +The minimum requirement for a UTRA OTA frequency error is the same as defined in subclause 9.6.2.3. + +The minimum requirement for an E-UTRA OTA frequency error is the same as defined in subclause 9.6.2.4. + +The minimum requirement for an NR OTA frequency error is the same as that for *BS type I-O* defined in 3GPP TS 38.104 [28] subclause 9.6.1.2. + +#### 9.6.2.3 Minimum requirement for single RAT UTRA operation + +The single RAT UTRA FDD AAS BS of wide area BS class shall fulfil the frequency error minimum requirements for wide area BS described in 3GPP TS 25.104 [6], subclause 6.3.1. + +The single RAT UTRA FDD AAS BS of medium range BS class shall fulfil the frequency error minimum requirements for medium range BS described in 3GPP TS 25.104 [6], subclause 6.3.1. + +The single RAT UTRA FDD AAS BS of local area BS class shall fulfil the frequency error minimum requirements for local area BS described in 3GPP TS 25.104 [6], subclause 6.3.1. + +#### 9.6.2.4 Minimum requirement for single RAT E-UTRA operation + +The single RAT E-UTRA AAS BS of wide area BS class shall fulfil the frequency error minimum requirements for wide area BS described in 3GPP TS 36.104 [8], subclause 6.5.1.1. + +The single RAT E-UTRA AAS BS of medium range BS class shall fulfil the frequency error minimum requirements for medium range BS described in 3GPP TS 36.104 [8], subclause 6.5.1.1. + +The single RAT E-UTRA AAS BS of local area BS class shall fulfil the frequency error minimum requirements for local area BS described in 3GPP TS 36.104 [8], subclause 6.5.1.1. + +## 9.6.3 OTA Time alignment error + +### 9.6.3.1 General + +This requirement applies to frame timing in: + +- UTRA single/multi-carrier transmissions and their combinations with MIMO or TX diversity. +- E-UTRA single/multi-carrier transmissions and their combinations with MIMO or TX diversity. +- E-UTRA *carrier aggregation*, with or without MIMO or TX diversity. +- NR single/multi-carrier transmissions, and their combinations with MIMO. +- NR Carrier Aggregation, with or without MIMO. + +Frames of the WCDMA/LTE/NR signals present in the radiated domain are not perfectly aligned in time. In relation to each other, the RF signals present in the radiated domain may experience certain timing differences. + +For a specific set of signals/transmitter configuration/transmission mode, the OTA Time Alignment Error (OTA TAE) is defined as the largest timing difference between any two different E-UTRA signals or any two different UTRA signals or any two different NR signals belonging to different *reference symbols* (e.g. CRS0 or CRS1 for E-UTRA, PDSCH DMRS on ports 1000 and 1001 for NR) in the radiated domain. The OTA time alignment error requirement is defined as a *single direction requirement* at the RIB and shall be met within the *OTA coverage range*. + +### 9.6.3.2 Minimum requirement for MSR operation + +The minimum requirement for a UTRA time alignment error is the same as defined in subclause 9.6.3.3. + +The minimum requirement for an E-UTRA time alignment error is the same as defined in subclause 9.6.3.4. + +The minimum requirement for an NR time alignment error is the same as that for *BS type 1-O* defined in 3GPP TS 38.104 [28] subclause 9.6.3.2. + +### 9.6.3.3 Minimum requirement for single RAT UTRA operation + +This requirement applies to frame timing in Tx diversity, MIMO transmission, DC-HSDPA, DB-DC-HSDPA, 4C-HSDPA, NC-4C-HSDPA, 8C-HSDPA and their combinations. + +The OTA TAE between any two reference symbols shall not exceed the specified minimum requirements described in 3GPP TS 25.104 [6], subclause 6.8.4.1. + +### 9.6.3.4 Minimum requirement for single RAT E-UTRA operation + +This requirement applies to frame timing in TX diversity, MIMO transmission, *carrier aggregation* and their combinations. + +The OTA TAE between any two reference symbols shall not exceed the specified minimum requirements described in 3GPP TS 36.104 [8], subclause 6.5.3.1. + +## 9.6.4 OTA Modulation quality + +### 9.6.4.1 General + +OTA modulation quality is defined by the difference between the measured carrier signal and a reference signal. Modulation quality can be expressed e.g. as Peak Code Domain Error (PCDE) or Relative Code Domain Error (RCDE) or Error Vector Magnitude (EVM) for UTRA and Error Vector Magnitude (EVM) for E-UTRA. + +The OTA modulation quality requirement is defined as a *single direction requirement* at the RIB and shall be met within the *OTA coverage range*. + +### 9.6.4.2 Minimum requirement for MSR operation + +The minimum requirement for a UTRA modulation quality are defined in subclause 9.6.4.3. + +The minimum requirement for an E-UTRA modulation quality are defined in subclause 9.6.4.4. + +The minimum requirement for an NR modulation quality is the same as that for *BS type 1-O* defined in 3GPP TS 38.104 [28] in subclause 9.6.2.2. + +### 9.6.4.3 Minimum requirement for single RAT UTRA operation + +The Error Vector Magnitude is a measure of the difference between the ideal waveform and the measured waveform. This difference is called the error vector. Both waveforms pass through a matched Root Raised Cosine filter to the considered chip rate and roll-off $\alpha=0.22$ . Both waveforms are then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing to minimize the error vector. The EVM result is defined as the square root of the ratio of the mean error vector power to the mean reference power expressed as a percentage. + +For UTRA FDD the measurement interval is one timeslot as defined by the C-PICH (when present) otherwise the measurement interval is one timeslot starting with the beginning of the SCH. The requirement is valid over the total power dynamic range as specified in subclause 9.4.4. The minimum requirements are the same as those in 3GPP TS 25.104 [6], subclause 6.8.2.1. + +For UTRA FDD the Peak Code Domain Error is computed by projecting the error vector onto the code domain at a specified 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 ideal 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 timeslot as defined by the C-PICH (when present) otherwise the measurement interval is one timeslot starting with the beginning of the SCH. The minimum requirements are the same as those in 3GPP TS 25.104 [6], subclause 6.8.3.1. + +For UTRA FDD the Relative Code Domain Error is computed by projecting the error vector onto the code domain at a specified spreading factor. Only the active code channels in the composite ideal 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 ideal waveform. This ratio is expressed in dB. The measurement interval is one frame. The minimum requirements are the same as those in 3GPP TS 25.104 [6], subclause 6.8.5.1. + +The requirement for Relative Code Domain Error is only applicable for 64QAM modulated codes. + +### 9.6.4.4 Minimum requirement for single RAT E-UTRA operation + +For E-UTRA, the minimum requirement for modulation quality, EVM, is specified in 3GPP TS 36.104 [8], subclause 6.5.2. + +## 9.6.5 OTA Transmit pulse shape filter + +### 9.6.5.1 General + +Transmit pulse shape filter for *single RAT UTRA operation* in FDD and for *MSR operation* in UTRA FDD is defined in 3GPP TS 25.104 [6] subclause 6.8.1. + +Transmit pulse shape filter is not defined for a *single RAT E-UTRA operation*, nor for *MSR operation* using E-UTRA and/or NR. + +## 9.7 OTA Unwanted Emissions + +### 9.7.1 General + +Unwanted emissions consist of so-called out-of-band emissions and spurious emissions according to ITU definitions 3GPP TS 25.331 [16]. In ITU terminology, 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. 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. + +OTA unwanted emissions for *OTA AAS BS* in *single RAT E-UTRA operation* and *MSR operation* using E-UTRA consist of an OTA operating band unwanted emissions requirement and OTA spurious emissions requirement. OTA operating band unwanted emissions requirement defines limits for emissions in each supported *downlink operating band* plus the frequency ranges $\Delta f_{\text{OBUE}}$ above and $\Delta f_{\text{OBUE}}$ below each band, where $\Delta f_{\text{OBUE}}$ is the maximum offset of the operating band unwanted emission mask from the operating band edge. Emissions outside of this frequency range are limited by OTA spurious emissions requirement. + +The values of $\Delta f_{\text{OBUE}}$ are defined for *OTA AAS BS* for E-UTRA and UTRA operating bands in Table 9.7.1-1. + +**Table 9.7.1-1: Maximum offset of OBUE outside the downlink operating band** + +| BS type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ [MHz] | +|-------------------|--------------------------------------------------------------------------------------|--------------------------------| +| OTA AAS BS | $F_{\text{DL\_high}} - F_{\text{DL\_low}} < 100 \text{ MHz}$ | 10 | +| | $100 \text{ MHz} \leq F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 900 \text{ MHz}$ | 40 | + +OTA unwanted emissions for *OTA AAS BS* in *single UTRA operation* and *MSR operation* using UTRA consist of OTA spectrum emission mask requirement and OTA spurious emissions requirement. + +NOTE: for definitions of conducted unwanted emissions requirements refer to clause 6.6 + +The unwanted emission requirements are applied per cell for all the configurations supported by *OTA AAS BS*. Requirements for OTA unwanted emissions are captured using TRP, *single direction requirements* or co-location requirements as described per requirement. + +There is in addition a requirement for occupied bandwidth and an ACLR requirement. + +## 9.7.2 OTA occupied bandwidth + +### 9.7.2.1 General + +The OTA occupied bandwidth is the width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage $\beta/2$ of the total mean transmitted power. See also recommendation ITU-R SM.328 [17]. + +The value of $\beta/2$ shall be taken as 0.5%. + +The OTA occupied bandwidth requirement applies during the *transmitter ON period* for a single transmitted carrier. The minimum requirement below may be applied regionally. There may also be regional requirements to declare the OTA occupied bandwidth according to the definition in the present clause. + +The OTA occupied bandwidth is defined as a *single direction requirement* and shall be met in the manufacturer's declared *OTA coverage range* at the RIB. + +#### 9.7.2.2 Minimum requirement for MSR operation + +For AAS BS in MSR operation, the minimum requirement for OTA occupied bandwidth is the same as that stated in 3GPP TS 37.104 [9], subclause 6.6.3. + +#### 9.7.2.3 Minimum requirement for single RAT UTRA operation + +For AAS BS in *single RAT UTRA operation* FDD, the minimum requirement for OTA occupied bandwidth is the same as that stated in 3GPP TS 25.104 [6] subclause 6.6.1. + +#### 9.7.2.4 Minimum requirement for single RAT E-UTRA operation + +For AAS BS in *single RAT E-UTRA operation*, the minimum requirement for OTA occupied bandwidth is the same as that stated in 3GPP TS 36.104 [8], subclause 6.6.1. + +### 9.7.3 OTA Adjacent Channel Leakage power Ratio + +#### 9.7.3.1 General + +OTA Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. The measured power is TRP. + +#### 9.7.3.2 Minimum requirement for MSR operation + +For AAS BS in *MSR operation* using E-UTRA, the OTA ACLR limits for AAS BS are the same as those specified in 3GPP TS 37.104 [9] subclauses 6.6.4.1. The ACLR absolute limits in 3GPP TS 37.104 [9] subclauses 6.6.4.1 are replaced with the following: + +- For E-UTRA or NR Category A AAS BS of Wide Area BS class the OTA ACLR absolute limit of -4dBm/MHz shall apply, +- For E-UTRA or NR Category B AAS BS Wide Area BS class the OTA ACLR absolute limit of -6dBm/MHz shall apply. +- For E-UTRA or NR AAS BS of Medium Range BS class the OTA ACLR absolute limit of -16 dBm/MHz shall apply. +- For E-UTRA or NR AAS BS of Local Area BS class the OTA ACLR absolute limit of -23dBm/MHz shall apply. + +The OTA ACLR limit or the ACLR absolute limit of AAS BS, whichever is less stringent, shall apply outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. + +For AAS BS in *MSR operation* using UTRA FDD, the minimum requirement for OTA ACLR are the same as those specified in 3GPP TS 25.104 [6], subclause 6.6.2.2, where the ACLR absolute limit is replaced with the following: + +- For UTRA FDD Category A AAS BS of Wide Area BS class the OTA ACLR absolute limit of -7dBm/MHz shall apply. +- For UTRA FDD Category B AAS BS Wide Area BS class the OTA ACLR absolute limit of -9dBm/MHz shall apply. +- For E-UTRA FDD AAS BS of Medium Range BS class the OTA ACLR absolute limit of -19 dBm/MHz shall apply. + +- For E-UTRA FDD AAS BS of Local Area BS class the OTA ACLR absolute limit of -26dBm/MHz shall apply. + +The OTA ACLR limit or the ACLR absolute limit of AAS BS, whichever is less stringent, shall apply outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. + +For a RIB supporting operation in *non-contiguous spectrum*, the OTA ACLR requirement also applies for the first adjacent channel inside any *sub-block gap* with a gap size $W_{\text{gap}} \geq 15\text{MHz}$ . The OTA ACLR requirement for the second adjacent channel applies inside any *sub-block gap* with a gap size $W_{\text{gap}} \geq 20\text{ MHz}$ . + +OTA CACLR requirements apply in *sub-block gaps* as defined in 3GPP TS 37.104 [9], subclause 6.6.4.4. Either the OTA CACLR limit or the OTA ACLR absolute limit of AAS BS shall apply, whichever is less stringent. + +For a *multi-band RIB*, the OTA ACLR requirement also applies for the first adjacent channel inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 15\text{MHz}$ . The OTA ACLR requirement for the second adjacent channel applies inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 20\text{ MHz}$ . + +OTA CACLR requirements apply in *Inter RF Bandwidth gaps* as defined in 3GPP TS 37.104 [9], subclause 6.6.4.4. Either the OTA CACLR limit or the OTA ACLR absolute limit of AAS BS shall apply, whichever is less stringent. + +### 9.7.3.3 Minimum requirement for single RAT UTRA operation + +For AAS BS in *single RAT UTRA operation* FDD, the OTA ACLR minimum requirements are the same as those specified in 3GPP TS 25.104 [6], subclauses 6.6.2.2.1, where the ACLR absolute limit is replaced with the following: + +- For UTRA FDD Category A AAS BS of Wide Area BS class the OTA ACLR absolute limit of -7dBm/MHz shall apply. +- For UTRA FDD Category B AAS BS Wide Area BS class the OTA ACLR absolute limit of -9dBm/MHz shall apply. +- For UTRA FDD AAS BS of Medium Range BS class the OTA ACLR absolute limit of -19 dBm/MHz shall apply. +- For UTRA FDD AAS BS of Local Area BS class the OTA ACLR absolute limit of -26dBm/MHz shall apply. + +The OTA ACLR limits or the absolute ACLR limits apply whichever is less stringent. + +For AAS BS in *single RAT UTRA operation* FDD, the OTA CACLR limits are the same as those specified in 3GPP TS 25.104 [6], subclauses 6.6.2.2.2. The ACLR absolute limit of AAS BS is replaced with the following: + +- For UTRA FDD Category A AAS BS of Wide Area BS class the OTA ACLR absolute limit of -7dBm/MHz shall apply. +- For UTRA FDD Category B AAS BS Wide Area BS class the OTA ACLR absolute limit of -9dBm/MHz shall apply. +- For UTRA FDD AAS BS of Medium Range BS class the OTA ACLR absolute limit of -19 dBm/MHz shall apply. +- For UTRA FDD AAS BS of Local Area BS class the OTA ACLR absolute limit of -26dBm/MHz shall apply. + +The OTA CACLR limit or the OTA ACLR absolute limit of AAS BS shall apply, whichever is less stringent. + +### 9.7.3.4 Minimum requirement for single RAT E-UTRA operation + +For AAS BS in *single RAT E-UTRA operation*, the OTA ACLR and OTA CACLR limits are the same as those specified in 3GPP TS 36.104 [8], subclauses 6.6.2.1 and 6.6.2.2. The ACLR absolute limits in 3GPP TS 36.104 [8] subclauses 6.6.2.1 and 6.6.2.2 are replaced with the following: + +- For E-UTRA Category A AAS BS of Wide Area BS class the ACLR absolute limit of -4dBm/MHz shall apply. +- For E-UTRA Category B AAS BS Wide Area BS class the ACLR absolute limit of -6dBm/MHz shall apply. +- For E-UTRA AAS BS of Medium Range BS class the ACLR absolute limit of -16 dBm/MHz shall apply. + +- For E-UTRA AAS BS of Local Area BS class the ACLR absolute limit of -23dBm/MHz shall apply. + +The OTA ACLR (CACLR) limit or the ACLR absolute limit of AAS BS shall apply, whichever is less stringent. + +## 9.7.4 OTA Spectrum emission mask + +### 9.7.4.1 General + +This requirement is applicable for single RAT UTRA AAS BS operation only. + +The spectrum emission mask minimum requirements are quoted as TRP unless otherwise stated. + +### 9.7.4.2 Minimum requirement for MSR operation + +There is no spectrum emission mask requirement for an MSR AAS BS. + +### 9.7.4.3 Minimum requirement for single RAT UTRA operation + +#### 9.7.4.3.1 General + +The spectrum emission mask requirements for a UTRA single RAT AAS BS is based upon the minimum requirement as specified in 3GPP TS 25.104 [2] or TS 25.105 [7], and for each RIB the emissions shall not exceed an AAS BS minimum requirement specified as $10\log_{10}(4)$ . + +NOTE: Conformance to the AAS BS spectrum emission mask requirement can be demonstrated by meeting the spectrum emission mask power at each RIB shall be less than or equal to the AAS BS limit as defined in this subclause for the respective frequency span, by $-10\log_{10}(4)$ + +#### 9.7.4.3.2 Minimum requirements for single RAT UTRA FDD operation + +The minimum requirement is specified in table's 9.7.4.3.2-1 to 9.7.3.4.2-10 for the appropriate $P_{\max,c,TRP}$ , where: + +- $\Delta f$ is the separation between the carrier frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the carrier frequency and the centre of the measurement filter; +- $f\_offset_{\max}$ is either 12.5 MHz or the offset to the UMTS Tx band edge as defined in clause 5.2, whichever is the greater. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +Inside any *Inter RF Bandwidth gaps* with $W_{gap} < 2 \times \Delta f_{OBUE}$ for a *multi-band RIB*, emissions shall not exceed the cumulative sum of the *minimum requirements* specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *minimum requirements* for *Base Station RF Bandwidth edge* is specified in tables 9.7.3.4.2-1 to 9.7.3.4.2-10 below, where in this case: + +- $\Delta f$ is equal to 2.5MHz plus the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the *Base Station RF Bandwidth edge*. +- $f\_offset$ is equal to 2.5MHz plus the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{\max}$ is either 12.5 MHz or the offset to the UMTS Tx band edge as defined in clause 5.2, whichever is the greater. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band RIB*, the operating band unwanted emission minimum requirements apply also in a supported operating band without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported operating band. In this case, no cumulative limit is applied in the *inter-band gap* between a supported *downlink operating band* with carrier(s) transmitted and a supported *downlink operating band* without any carrier transmitted and + +- In case the *inter-band gap* between a downlink band with carrier(s) transmitted and a downlink band without any carrier transmitted is less than $2 \times \Delta f_{\text{OBUE}}$ , $f_{\text{offset,max}}$ shall be the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the outermost edges of the two *downlink operating bands* and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present subclause, shall apply across both downlink bands. +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present subclause for the largest frequency offset ( $\Delta f_{\text{max}}$ ), shall apply from $\Delta f_{\text{OBUE}}$ below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band* without any carrier transmitted. + +Inside any *sub-block gap* for a RIB operating in *non-contiguous spectrum*, emissions shall not exceed the cumulative sum of the *minimum requirements* specified for the adjacent sub blocks on each side of the *sub-block gap*. The *minimum requirement* for each sub block is specified in tables 9.7.4.3.2-1 to 9.7.4.3.2-10 below, where in this case: + +- $\Delta f$ is equal to 2.5MHz plus the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f_{\text{offset}}$ is equal to 2.5MHz plus the separation between the sub block edge frequency and the centre of the measuring filter. +- $f_{\text{offset,max}}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter plus 2.5MHz. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset,max}}$ minus half of the bandwidth of the measuring filter. + +![Illustrative diagram of spectrum emission mask showing power density in 30kHz and 1 MHz versus frequency separation from the carrier.](31d28c91958950ee8785840552992758_img.jpg) + +The figure is a graph titled 'Frequency separation $\Delta f$ from the carrier [MHz]' on the x-axis and 'Power density in 30kHz [dBm]' on the left y-axis and 'Power density in 1 MHz [dBm]' on the right y-axis. The x-axis has markers at 2.5, 2.7, 3.5, 7.5, and $\Delta f_{\text{max}}$ , with break symbols between 3.5 and 7.5. The left y-axis ranges from -40 to -15 dBm in 5 dBm increments. The right y-axis ranges from -25 to 0 dBm in 5 dBm increments. The graph shows a spectrum emission mask with three horizontal power density levels indicated by labels: $P_{\text{max,c,TRP}} = 49 \text{ dBm}$ (at 0 dBm on the right axis), $P_{\text{max,c,TRP}} = 45 \text{ dBm}$ (at -4 dBm on the right axis), and $P_{\text{max,c,TRP}} = 37 \text{ dBm}$ (at -12 dBm on the right axis). The mask is represented by a green shaded area with a black outline. It starts at -15 dBm (left axis) for $\Delta f < 2.5$ MHz, drops linearly to -35 dBm at $\Delta f = 3.5$ MHz, then drops to -40 dBm at $\Delta f = 7.5$ MHz, and finally drops to -45 dBm at $\Delta f = \Delta f_{\text{max}}$ . The right y-axis values correspond to the left y-axis values shifted upwards by 34 dBm. + +Illustrative diagram of spectrum emission mask showing power density in 30kHz and 1 MHz versus frequency separation from the carrier. + +Illustrative diagram of spectrum emission mask + +Figure 9.7.4.3.2-1: Spectrum emission mask + +**Table 9.7.4.3.2-1: Spectrum emission mask values, $P_{\text{rated,c,TRP}} \geq 49$ dBm for UTRA FDD** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|----------------------------------------------------------------|------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f_{\text{offset}} < 2.715 \text{ MHz}$ | -8 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f_{\text{offset}} < 3.515 \text{ MHz}$ | | 30 kHz | +| (NOTE 3) | $3.515 \text{ MHz} \leq f_{\text{offset}} < 4.0 \text{ MHz}$ | -20 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f < 7.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f_{\text{offset}} < 8.0 \text{ MHz}$ | -7 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offset,max}}$ | -7 dBm | 1 MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation the *minimum requirement* within *sub-block gaps* within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the spurious emission *minimum requirement* in subclause 9.7.6 shall be met. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.4.3.2-2: Spectrum emission mask values, $45 \text{ dBm} \leq P_{\text{rated,c,TRP}} < 49 \text{ dBm}$ for UTRA FDD bands** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|----------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f_{\text{offset}} < 2.715 \text{ MHz}$ | -8 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f_{\text{offset}} < 3.515 \text{ MHz}$ | | 30 kHz | +| (NOTE 3) | $3.515 \text{ MHz} \leq f_{\text{offset}} < 4.0 \text{ MHz}$ | -20 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f < 7.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f_{\text{offset}} < 8.0 \text{ MHz}$ | -7 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offset,max}}$ | $P_{\text{rated,c,TRP}} - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation the *minimum requirement* within *sub-block gaps* within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the spurious emission *minimum requirement* in subclause 9.7.6 shall be met. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.4.3.2-3: Spectrum emission mask values, $37 \text{ dBm} \leq P_{\text{rated,c,TRP}} < 45 \text{ dBm}$ for UTRA FDD bands** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 53 \text{ dB}$ | 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_{\text{rated,c,TRP}} - 53 \text{ dB} - 15 \cdot (f\_offset/\text{MHz} - 2,715) \text{ dB}$ | 30 kHz | +| (NOTE 3) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 65 \text{ dB}$ | 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_{\text{rated,c,TRP}} - 52 \text{ dB}$ | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,TRP}} - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation the *minimum requirement* within *sub-block gaps* within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the spurious emission *minimum requirements* in subclause 9.7.6 shall be met. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.4.3.2-4: Spectrum emission mask values, $P_{\text{rated,c,TRP}} < 37 \text{ dBm}$ for UTRA FDD bands** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|----------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -16 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (NOTE 3) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -28 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f < 7.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f\_offset < 8.0 \text{ MHz}$ | -15 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -19 dBm | 1 MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation the *minimum requirement* within *sub-block gaps* within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the spurious emission *minimum requirements* in subclause 9.7.6 shall be met. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +For operation in band II, IV, V, X, XII, XIII, XIV, XXV and XXVI, the additional requirement in tables 9.7.4.3.2-5 to 9.7.4.3.2-7 apply in addition to the *minimum requirements* in tables 9.7.4.3.2-1 to 9.7.4.3.2-4. + +**Table 9.7.4.3.2-5: Additional spectrum emission minimum requirements 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 minimum requirement | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | -9 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $4.0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm | 1 MHz | + +**Table 9.7.4.3.2-6: Additional spectrum emission minimum requirements for Bands V, XXVI** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional minimum requirement | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | -9 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3.55 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm | 100 kHz | + +**Table 9.7.4.3.2-7: Additional spectrum emission minimum requirements for Bands XII, XIII, XIV** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional minimum requirement | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.6 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.615 \text{ MHz}$ | -7 dBm | 30 kHz | +| $2.6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.65 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm | 100 kHz | + +In certain regions the following requirement may apply for protection of DTT. For a RIB operating in Band XX, the level of emissions in the band 470-790 MHz, measured in an 8MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to table 9.7.4.3.2-8, shall not exceed the emission TRP limits as specified in table 9.7.4.3.2-8 + +**Table 9.7.4.3.2-8: Emissions levels for protection of DTT** + +| Case | Measurement filter centre frequency | Condition on BS maximum aggregate EIRP / 10 MHz, $P_{\text{EIRP\_10MHz}}$ (NOTE) | Maximum Level $P_{\text{EIRP,N,MAX}}$ | Measurement Bandwidth | +|---------------------------------------------------------------------------------------------|-----------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------|-----------------------| +| A: for DTT frequencies where broadcasting is protected | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{EIRP\_10MHz}} \geq 59 \text{ dBm}$ | 0 dBm | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $36 \leq P_{\text{EIRP\_10MHz}} < 59 \text{ dBm}$ | $P_{\text{EIRP\_10MHz}} - 59 \text{ dBm}$ | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{EIRP\_10MHz}} < 36 \text{ dBm}$ | -23 dBm | 8 MHz | +| B: for DTT frequencies where broadcasting is subject to an intermediate level of protection | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{EIRP\_10MHz}} \geq 59 \text{ dBm}$ | 10 dBm | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $36 \leq P_{\text{EIRP\_10MHz}} < 59 \text{ dBm}$ | $P_{\text{EIRP\_10MHz}} - 49 \text{ dBm}$ | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{EIRP\_10MHz}} < 36 \text{ dBm}$ | -13 dBm | 8 MHz | +| C: for DTT frequencies where broadcasting is not protected | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | N.A. | 22 dBm | 8 MHz | + +NOTE: $P_{\text{EIRP\_10MHz}}$ (dBm) is defined by the expression $P_{\text{EIRP\_10MHz}} = P_{10\text{MHz}} + G_{\text{ant}} + 6 \text{ dB}$ for UTRA and $P_{\text{EIRP\_10MHz}} = P_{10\text{MHz}} + G_{\text{ant}} + 9 \text{ dB}$ for E-UTRA, where $G_{\text{ant}}$ is 17 dBi. + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B1 Indicates how the limit in table 9.7.4.3.2-8 demonstrates compliance to the regional requirement. + +In certain regions, the following *basic limits* may apply to a RIB operating in Band XXXII within 1452-1492 MHz. The level of unwanted emissions, measured on centre frequencies $f\_offset$ with filter bandwidth, according to table 9.7.4.3.2-9, shall not exceed the maximum TRP limits indicated in the table. + +**Table 9.7.4.3.2-9: Declared frequency band XXXII unwanted emission within 1452-1492 MHz** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum Level [dBm] | Measurement bandwidth | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-----------------------| +| 5 MHz | $P_{EIRP} - 17 \text{ dBi} + 6 \text{ dB}$ | 5 MHz | +| 10 MHz | $P_{EIRP} - 17 \text{ dBi} + 6 \text{ dB}$ | 5 MHz | +| $15 \text{ MHz} \leq f\_offset \leq f\_offset_{max, B32}$ | $P_{EIRP} - 17 \text{ dBi} + 6 \text{ dB}$ | 5 MHz | +| NOTE: $f\_offset_{max, B32}$ denotes the frequency difference between the lower channel carrier frequency and 1454.5 MHz, and the frequency difference between the upper channel carrier frequency and 1489.5 MHz for the set channel position. | | | + +NOTE: The regional requirement, included in CEPT ECC Decision (13)03 [25], is defined in terms of EIRP per antenna, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B1 Indicates how the limit in table 9.7.4.3.2-9 demonstrates compliance to the regional requirement. + +In certain regions, the following *basic limit* may apply to RIB operating in Band XXXII within 1452-1492 MHz for the protection of services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{filter}$ with filter bandwidth according to table 9.7.4.3.2-10, shall not exceed the maximum emission TRP limits in the table. This requirement applies in the frequency range 1429-1518 MHz even though part of the range falls in the spurious domain. + +**Table 9.7.4.3.2-10: Frequency band XXXII declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{filter}$ | Maximum level [dBm] | Measurement bandwidth | +|--------------------------------------------------------------|--------------------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{filter} \leq 1448.5 \text{ MHz}$ | $P_{EIRP} - 17 \text{ dBi} + 6 \text{ dB}$ | 1 MHz | +| $F_{filter} = 1450.5 \text{ MHz}$ | $P_{EIRP} - 17 \text{ dBi} + 6 \text{ dB}$ | 3 MHz | +| $F_{filter} = 1493.5 \text{ MHz}$ | $P_{EIRP} - 17 \text{ dBi} + 6 \text{ dB}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{filter} \leq 1517.5 \text{ MHz}$ | $P_{EIRP} - 17 \text{ dBi} + 6 \text{ dB}$ | 1 MHz | + +NOTE: The regional requirement, included in CEPT ECC Decision (13)03 [25], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B1 Indicates how the limit in table 9.7.4.3.2-10 demonstrates compliance to the regional requirement. + +Notes for the tables in this subclause: + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 4: 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.7.4.4 Minimum requirement for single RAT E-UTRA operation + +There is no spectrum emission mask requirement for a single RAT E-UTRA AAS BS. + +## 9.7.5 OTA Operating band unwanted emission + +### 9.7.5.1 General + +Unless otherwise stated, for E-UTRA single band and MSR the operating band unwanted emission limits are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported *downlink operating band* to the lower *Base Station RF Bandwidth edge* located at $F_{\text{BW RF,low}}$ and from the upper *Base Station RF Bandwidth edge* located at $F_{\text{BW RF,high}}$ up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported *downlink operating band*. The values of $\Delta f_{\text{OBUE}}$ are defined in table 9.7.1-1. + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. + +The operating band unwanted emissions minimum requirements are quoted as TRP per *RIB* unless otherwise stated. + +The requirements shall apply whatever the type of RIB is considered (single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification. In addition, for a RIB operating in *non-contiguous spectrum*, the requirements apply inside any *sub-block gap*. In addition, for a *multi-band RIB* the requirements apply inside any *Inter RF Bandwidth gap*. + +The unwanted emission limits in the part of the *downlink operating band* that falls in the spurious domain are consistent with ITU-R Recommendation SM.329 [14]. + +Additional limits in clause 9.7.5.2.4.7 may apply outside OBUE frequency domain. + +Emissions shall use the minimum requirements specified in the tables below, where: + +- $\Delta f$ is the separation between the channel edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the channel edge frequency and the centre of the measuring filter. +- $f_{\text{offset,max}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ MHz outside the *downlink operating band*. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset,max}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band RIB* inside any *Inter RF Bandwidth gaps* with $W_{\text{gap}} < 2 \times \Delta f_{\text{OBUE}}$ , emissions shall not exceed the cumulative sum of the minimum requirements specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The minimum requirement for *Base Station RF Bandwidth edge* is specified in the subclause 9.7.5.4.2 to 9.7.5.4.7 below, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the *Base Station RF Bandwidth edge*. +- $f_{\text{offset}}$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f_{\text{offset,max}}$ is equal to the *Inter RF Bandwidth gap* minus half of the bandwidth of the measuring filter. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset,max}}$ minus half of the bandwidth of the measuring filter. + +For *multi-band RIB*, the operating band unwanted emission limits apply also in a supported operating band without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported operating band. In this case, no cumulative limit is applied in the *inter-band gap* between a supported *downlink operating band* with carrier(s) transmitted and a supported *downlink operating band* without any carrier transmitted and + +- In case the *inter-band gap* between a supported *downlink operating band* with carrier(s) transmitted and a supported *downlink operating band* without any carrier transmitted is less than $2 \times \Delta f_{\text{OBUE}}$ , $f_{\text{offset,max}}$ shall be the offset to the frequency $\Delta f_{\text{OBUE}}$ MHz outside the outermost edges of the two supported *downlink operating bands* and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present subclause, shall apply across both downlink bands. +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present subclause for the largest frequency offset ( $\Delta f_{\text{max}}$ ), shall apply from $\Delta f_{\text{OBUE}}$ + +MHz below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ MHz above the highest frequency of the supported *downlink operating band* without any carrier transmitted. + +For a multicarrier E-UTRA RIB or a RIB configured for intra-band contiguous or non-contiguous *carrier aggregation* the definitions above apply to the lower edge of the carrier transmitted at the lowest carrier frequency and the upper edge of the carrier transmitted at the highest carrier frequency within a specified frequency band. + +In addition, inside any *sub-block gap* for a RIB operating in *non-contiguous spectrum*, emissions shall not exceed the cumulative sum of the minimum requirements specified for the adjacent sub blocks on each side of the *sub-block gap*. The minimum requirement for each sub block is specified in the tables sub-clause 9.7.5.4.2 to 9.7.5.4.7 below, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f_{\text{offset}}$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. +- $\Delta f_{\text{OBUE}}$ is defined in clause 6.6.1. + +## 9.7.5.2 Minimum requirement for MSR operation + +### 9.7.5.2.1 General + +The MSR operating band unwanted emission minimum requirements are given in subclauses 9.7.5.2.2, 9.7.5.2.3, and 9.7.5.2.4. + +### 9.7.5.2.2 Minimum requirements for Band Categories 1 and 3 + +For an MSR RIB operating in BC1 or BC3 bands, the minimum requirements are specified in tables 9.7.5.2.2-1 to 9.7.5.2.2-4, dependent on BS class and output power. + +Applicability of Wide Area operating band unwanted emission requirements in tables 9.7.5.2.2-1, 9.7.5.2.2-1a and 9.7.5.2.2-1b is specified in table 9.7.5.2.2-0. + +**Table 9.7.5.2.2-0: Applicability of operating band unwanted emission requirements for BC1 and BC3 Wide Area BS** + +| NR band operation | UTRA supported | Applicable requirement table | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------------------------------| +| None | Y/N | 9.7.5.2.2-1 (option 2) | +| In certain regions (NOTE 2), bands 3, 8 | N | 9.7.5.2.2-1 (option 2) | +| Any below 1 GHz except for certain regions (NOTE 2), band 8 | N | 9.7.5.2.2-1a (option 1) | +| Any above 1 GHz except for certain regions (NOTE 2), band 3 | N | 9.7.5.2.2-1b (option 1) | +| NOTE 1: Void.
NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [14] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [8] and TS 38.104 [27] are applied. | | | + +**Table 9.7.5.2.2-1: WA BS OBUE in BC1 and BC3 bands applicable for: BS not supporting NR; or BS supporting NR in Band n1 or n65** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -17 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -4 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (NOTE 5) | 1 MHz | + +NOTE 1: For MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -6dBm/MHz. + +NOTE2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 9.7.5.2.2-1a: WA BS OBUE in BC1 and BC3 bands $\leq 1 \text{ GHz}$ applicable for: BS supporting NR and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 4) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm (Note 5) | 100 kHz | + +NOTE 1: For MSR *RIB* supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -7dBm/100kHz. + +NOTE 2: For MSR *multi band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3MHz carrier adjacent to the Base Station RF Bandwidth edge, the limits in Table 6.6.2.2-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 9.7.5.2.2-1b: WA BS OBUE in BC1 and BC3 bands > 1 GHz applicable for: BS supporting NR, not operating in band n1 or n65, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 4) | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | -5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -6 dBm (Note 5) | 1MHz | + +NOTE 1: For MSR *R/B* supporting non-contiguous spectrum operation within any operating band, the *minimum requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within sub-block gaps shall be -6dBm/1MHz. + +NOTE 2: For MSR *multi band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3MHz carrier adjacent to the Base Station RF Bandwidth edge, the limits in Table 6.6.2.2-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 9.7.5.2.2-2: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $40 < P_{rated,c,TRP} \leq 47 \text{ dBm}$ and not supporting NR** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{rated,c,TRP} - 58 \text{ dB} - (5/3) \cdot (f\_offset - 0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{rated,c,TRP} - 53 \text{ dB} - 15 \cdot (f\_offset - 0.015) \text{ dB}$ | 30 kHz | +| (NOTE 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{rated,c,TRP} - 65 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.1 \text{ MHz}$ | $P_{rated,c,TRP} - 52 \text{ dB}$ | 1 MHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.1 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{rated,c,TRP} - 52 \text{ dB}, -6 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $P_{rated,c,TRP} - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For MSR *R/B* supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be $(P_{rated,c,TRP} - 56 \text{ dB}) / \text{MHz}$ . + +NOTE 2: For MSR *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.5.2.2-2a: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm BS, supporting NR and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 4) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 53 \text{ dB} - (7/5) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,c,TRP}} - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$ (Note 4) | 100 kHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For MSR *multi band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.2.2-3: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm and not supporting NR** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -25 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -12 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm | 1 MHz | + +NOTE 1: For MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -16 dBm/MHz. + +NOTE 2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.5.2.2-3a: MR BS OBUE in BC1 bands applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm, supporting NR and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 4) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-13 \text{ dBm} - 7/5 \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -20 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -20 dBm (Note 4) | 100 kHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -20 dBm/100 kHz. + +NOTE 2: For MSR *multi band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.2.2-4: LA BS OBUE in BC1 bands** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 4) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -28 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm (NOTE 5) | 100 kHz | + +NOTE 1: For MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -28dBm/100 kHz. + +NOTE 2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 4: As a general rule for the requirements in the present subclause, 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 may 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. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +### 9.7.5.2.3 Minimum requirement for Band Category 2 + +For an MSR RIB operating in BC2 bands, the minimum requirements are specified in tables 9.7.5.2.3-1 to 9.7.5.2.3-8. + +Applicability of Wide Area operating band unwanted emission requirements in tables 9.7.5.2.3-1, 9.7.5.2.3-1a and 9.7.5.2.3-1b is specified in table 9.7.5.2.3-0. + +**Table 9.7.5.2.3-0: Applicability of operating band unwanted emission requirements for BC2 Wide Area BS** + +| NR band operation | UTRA supported | Applicable requirement table | +|-------------------------------------------------------------|----------------|------------------------------| +| None | Y/N | 9.7.5.2.3-1 (option 2) | +| In certain regions (NOTE 2), bands 3, 8 | N | 9.7.5.2.3-1 (option 2) | +| Any below 1 GHz except for certain regions (NOTE 2), band 8 | N | 9.7.5.2.3-1a (option 1) | +| Any above 1 GHz except for certain regions (NOTE 2), band 3 | N | 9.7.5.2.3-1b (option 1) | + +NOTE 1: Void. + +NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [14] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [8] and TS 38.104 [27] are applied. + +**Table 9.7.5.2.3-1: WA BS OBUE in BC2 bands applicable for: BS not supporting NR; or BS supporting NR in Band n3 or n8** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------|---------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$
(NOTE 1) | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$
(NOTE 9) | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{max}, 10 \text{ MHz})$ | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -17 dBm | 30 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{max}, 10.5 \text{ MHz})$ | -4 dBm | 1 MHz | +| | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -6 dBm (NOTE 11) | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*, the limits in table 9.7.5.2.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -6dBm/MHz. + +NOTE 3: For a MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ operation the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.5.2.3-1a: WA BS OBUE in BC2 bands $\leq 1 \text{ GHz}$ applicable for: BS supporting NR, not operating in band n8, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 10) | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $2 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | -5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -7 dBm (Note 11) | 100 kHz | + +NOTE 1: For MSR *RIB* supporting non-contiguous spectrum operation within any operating band, the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the minimum requirement within *sub-block gaps* shall be -7 dBm/100 kHz. + +NOTE 2: For MSR *multi band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*, the limits in table 9.7.5.2.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 9.7.5.2.3-1b: WA BS OBUE in BC2 bands > 1 GHz applicable for: BS supporting NR, not operating in band n3, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $2 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm (Note 11) | 1MHz | + +NOTE 1: For MSR RIBs supporting non-contiguous spectrum operation within any operating band, the minimum requirement within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the minimum requirement within sub-block gaps shall be -7dBm/1MHz. + +NOTE 2: For MSR *multi band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*, the limits in table 9.7.5.2.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 9.7.5.2.3-2: WA BS OBUE in BC2 bands applicable for: BS operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*. + +NOTE 2: For MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. + +NOTE 3: For a MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 4: (Void) + +**Table 9.7.5.2.3-3: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm and not supporting NR** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ (NOTE 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 58 \text{ dB} - (5/3) * (f\_offset - 0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ (NOTE 9) | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 53 \text{ dB} - 15 * (f\_offset - 0.215) \text{ dB}$ | 30 kHz | +| | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 65 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 52 \text{ dB}$ | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.3 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 52 \text{ dB}, -6 \text{ dBm}$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,TRP}} - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*, the limits in table 9.7.5.2.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For a MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be $(P_{\text{rated,c,TRP}} - 56 \text{ dB})/\text{MHz}$ . + +NOTE 3: For a MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 * \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.5.2.3-3a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm, supporting NR and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 53 \text{ dB} - (7/5) * (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,TRP}} - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$ (Note 11) | 100 kHz | + +NOTE 1: For MSR *RIBs* supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For MSR *multi band RIB* with *Inter RF Bandwidth gap* $< 2 * \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*, the limits in table 9.7.5.2.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 9.7.5.2.3-4: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm and not supporting NR** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$
(NOTE 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 9) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -25 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -12 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $5.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -16 dBm | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*, the limits in table 6.6.2.2-6 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For a MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -16dBm/MHz. + +NOTE 3: For a MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.5.2.3-4a: MR BS OBUE in BC2 bands applicable for: BS maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm, supporting NR and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-----------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-13 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -20 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -20 dBm (Note 11) | 100 kHz | + +NOTE 1: For MSR RIBs supporting non-contiguous spectrum operation within any operating band the minimum requirement within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the minimum requirement within sub-block gaps shall be -20 dBm/100 kHz. + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*, the limits in table 9.7.5.2.3-6 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 9.7.5.2.3-5: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm and operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the *Base Station RF Bandwidth edge*** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 38 \text{ dB} - 60 \cdot (f\_offset - 0.015) \text{ dB}$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 41 \text{ dB} - 160 \cdot (f\_offset - 0.065) \text{ dB}$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*. + +NOTE 2: For a MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. + +NOTE 3: For a MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.2.3-6: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm and operating E-UTRA 1.4 or 3 MHz carriers adjacent to the *Base Station RF Bandwidth edge*** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset <$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*. + +NOTE 2: For a MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. + +NOTE 3: For a MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 4: (Void) + +**Table 9.7.5.2.3-7: LA BS OBUE in BC2 bands** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ (NOTE 1) | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -28 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm (NOTE 11) | 100 kHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*, the limits in table 9.7.5.2.3-8 apply for $0 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ . + +NOTE 2: For a MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -28dBm/100 kHz. + +NOTE 3: For a MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.2.3-8: LA BS OBUE for operation in BC2 bands applicable for: BS operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 2, 3) | Measurement bandwidth (NOTE 10) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.175 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge*. + +NOTE 2: For a MSR RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. + +NOTE 3: For a MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 4: (Void) + +The following notes are common to all subclauses in 9.7.5.2.3: + +NOTE 9: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 10: As a general rule for the requirements in the present subclause, 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 may 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. + +NOTE 11: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +NOTE 12: All limits in table 9.7.5.2.3-1, table 9.7.5.2.3-3, table 9.7.5.2.3-4 and table 9.7.5.2.3-7 are identical to the corresponding limits for Band Category 1 and 3. + +## 9.7.5.2.4 Additional requirements + +### 9.7.5.2.4.1 Limits in FCC Title 47 + +In addition to the AAS BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +#### 9.7.5.2.4.2 Unsynchronized operation for BC3 + +In certain regions, the following requirements may apply to a TDD AAS BS operating in BC3 in the same geographic area and in the same operating band as another TDD system without synchronisation. For this case the emissions shall not exceed -52 dBm/MHz in each supported *downlink operating band* except in: + +- The frequency range from $\Delta f_{\text{OBU}}$ below the lower *Base Station RF Bandwidth edge* to the frequency $\Delta f_{\text{OBU}}$ above the upper *Base Station RF Bandwidth edge* of each supported band. + +NOTE 1: Local or regional regulations may specify another excluded frequency range, which may include frequencies where synchronised TDD systems operate. + +NOTE 2: TDD base stations that are synchronized and operating in BC3 can transmit without these additional co-existence requirements. + +#### 9.7.5.2.4.3 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For an AAS BS operating in Band 20, the level of emissions in the band 470-790 MHz, measured in an 8 MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to table 9.7.5.2.4.3-1, shall not exceed the maximum emission TRP level shown in the table. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 9.7.5.2.4.3-1: Declared emissions levels for protection of DTT** + +| Case | Measurement filter centre frequency | Condition on BS maximum aggregate TRP / 10 MHz, $P_{\text{TRP\_10MHz}}$ (NOTE) | Maximum Level $P_{\text{TRP,N,MAX}}$ | Measurement Bandwidth | +|---------------------------------------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------------------------------------|------------------------------------------|-----------------------| +| A: for DTT frequencies where broadcasting is protected | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} \geq 59 \text{ dBm}$ | 0 dBm | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $36 \leq P_{\text{TRP\_10MHz}} < 59 \text{ dBm}$ | $P_{\text{TRP\_10MHz}} - 59 \text{ dBm}$ | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} < 36 \text{ dBm}$ | -23 dBm | 8 MHz | +| B: for DTT frequencies where broadcasting is subject to an intermediate level of protection | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} \geq 59 \text{ dBm}$ | 10 dBm | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $36 \leq P_{\text{TRP\_10MHz}} < 59 \text{ dBm}$ | $P_{\text{TRP\_10MHz}} - 49 \text{ dBm}$ | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} < 36 \text{ dBm}$ | -13 dBm | 8 MHz | +| C: for DTT frequencies where broadcasting is not protected | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | N.A. | 22 dBm | 8 MHz | + +NOTE: $P_{\text{TRP\_10MHz}}$ (dBm) is defined by the expression $P_{\text{TRP\_10MHz}} = P_{10\text{MHz}} + G_{\text{ant}} + 6\text{dB}$ for UTRA and $P_{\text{TRP\_10MHz}} = P_{10\text{MHz}} + G_{\text{ant}} + 9\text{dB}$ for E-UTRA, where $G_{\text{ant}}$ is 17 dBi + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions and the deployment (including antenna gain and feeder loss). The method outlined in annex B1 indicates how the limit in table 5.2.4.3-1 demonstrates compliance to the regional requirement. + +#### 9.7.5.2.4.4 Void + +**Table 9.7.5.2.4.4-1: Void** + +#### 9.7.5.2.4.5 Co-existence with RNSS/GPS services in North America + +In regions where FCC regulation applies, requirements for protection of GPS according to FCC Order DA 20-48 applies for operation in Band 24. The following normative requirement covers the base station, to be used together with other information about the site installation to verify compliance with the requirement in FCC Order DA 20-48. The + +requirement applies to BS operating in Band 24 to ensure that appropriate interference protection is provided to the GPS. This requirement applies in the frequency range 1541-1650 MHz even though part of the range falls in the spurious domain. + +The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to table 9.7.5.2.4.5-1 shall not exceed the maximum TRP limits indicated in the table. + +**Table 9.7.5.2.4.5-1: Emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range (MHz) | Emission level (dBW) (Measurement bandwidth = 1 MHz) | Emission level (dBW) of discrete emissions of less than 700 Hz bandwidth (Measurement bandwidth = 1 kHz) | Emission level (dBW) of discrete emissions of less than 2 kHz bandwidth (Measurement bandwidth = 1 kHz) | +|----------------|-----------------------|------------------------------------------------------|----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| 24 | 1541 - 1559 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | +| | 1559 - 1610 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | +| | 1610 - 1650 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | + +NOTE: The regional requirements, included in FCC Order DA 20-48 are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B1 indicates how the limit in table 9.7.5.2.4.5-1 demonstrates compliance to the regional requirement. $P_{\text{EIRP}}$ values in table 9.7.5.2.4.5-1 are the effective isotropic power (or radiated power spectral density) set in the FCC Order DA 20-48 for the specified frequency ranges and bandwidths. + +#### 9.7.5.2.4.6 Void + +**Table 9.7.5.2.4.6-1: Void** + +#### 9.7.5.2.4.7 Additional band 32, 50, 51, 74, 75 and 76 unwanted emissions + +In certain regions, the following requirements may apply to BS operating in Band 32 within 1452-1492 MHz, in Band 75 within 1432-1517 MHz and in Band 76 within 1427-1432 MHz. The maximum level of operating band unwanted emissions, measured as EIRP, on centre frequencies $f_{\text{offset}}$ with filter bandwidth, according to table 9.7.5.2.4.7-1, shall not exceed the EIRP limits indicated in the table. + +For Band 32, this requirement applies in the frequency range 1452-1492 MHz when non-Mobile/Fixed Communications Network (MFCN) services are deployed in adjacent frequency ranges, while it applies also within 1427-1452 MHz and/or 1492-1517 MHz when MFCN services are deployed in such frequency ranges, even though part of the ranges falls in the spurious domain. For Band 75, this requirement applies in the frequency range 1427-1517 MHz. For Band 76, this requirement applies in the frequency range 1432-1517 MHz even though part of the range falls in the spurious domain. + +**Table 9.7.5.2.4.7-1: Unwanted emission limits within 1427-1517 MHz** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | EIRP limit [dBm] | Measurement bandwidth | +|----------------------------------------------------------------------|------------------|-----------------------| +| 2.5 MHz | 16.3 | 5 MHz | +| 7.5 MHz | 11 | 5 MHz | +| $12.5 \text{ MHz} \leq f\_offset \leq f\_offset_{max}$ | 9 | 5 MHz | + +NOTE: For Band 32, when non-MFCN services are deployed in the adjacent bands, $f\_offset_{max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1454.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1489.5 MHz for the set channel position. For Band 32, when MFCN services are deployed in the adjacent frequencies, Band 75 and Band 76, $f\_offset_{max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1429.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1514.5 MHz for the set channel position. + +In certain regions, the following requirement may apply to BS operating in Band 32 within 1452-1492 MHz for the protection of non-MFCN services in spectrum adjacent to the frequency range 1452-1492 MHz. The maximum level of emissions, measured as EIRP, on centre frequencies $F_{filter}$ with filter bandwidth according to Table 9.7.5.2.4.7-2, shall not exceed the EIRP limits indicated in the table. This requirement applies in the frequency range 1429-1518 MHz even though part of the range falls in the spurious domain. + +**Table 9.7.5.2.4.7-2: Unwanted emission limits outside 1452-1492 MHz** + +| Filter centre frequency, $F_{filter}$ | EIRP limit [dBm] | Measurement bandwidth | +|--------------------------------------------------------------|------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{filter} \leq 1448.5 \text{ MHz}$ | 20 | 1 MHz | +| $F_{filter} = 1450.5 \text{ MHz}$ | 14 | 3 MHz | +| $F_{filter} = 1493.5 \text{ MHz}$ | 14 | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{filter} \leq 1517.5 \text{ MHz}$ | 20 | 1 MHz | + +In certain regions, the following requirement may apply to BS operating in Band 50 and Band 75 within 1492-1517 MHz and in Band 74 within 1492-1518 MHz. The maximum level of emissions, measured as EIRP, on centre frequencies $F_{filter}$ with filter bandwidth according to table 9.7.5.2.4.7-3, shall not exceed the EIRP limits indicated in the table. + +**Table 9.7.5.2.4.7-3: Operating band 50, 74 and 75 emission test limits above 1518 MHz** + +| Filter centre frequency, $F_{filter}$ | EIRP limit (dBm) | Measurement bandwidth | +|--------------------------------------------------------------|------------------|-----------------------| +| $1518.5 \text{ MHz} \leq F_{filter} \leq 1519.5 \text{ MHz}$ | -0.8 | 1 MHz | +| $1520.5 \text{ MHz} \leq F_{filter} \leq 1558.5 \text{ MHz}$ | -30 | 1 MHz | + +In certain regions, the following requirement may apply to E-UTRA BS operating in Band 50 and Band 75 within 1432-1452 MHz, and in Band 51 and Band 76. Emissions shall not exceed the maximum levels specified in table 9.7.5.2.4.7-4. + +**Table 9.7.5.2.4.7-4: Additional emission limits for BS operating in Band 50 and 75 within 1432-1452 MHz, and in Band 51 and 76** + +| Filter centre frequency, $F_{filter}$ | Maximum Level [dBm] | Measurement Bandwidth | +|---------------------------------------|---------------------|-----------------------| +| $F_{filter} = 1413.5 \text{ MHz}$ | -42 | 27 MHz | + +#### 9.7.5.2.4.8 Additional requirements for band 45 + +In certain regions the following requirement may apply to E-UTRA BS operating in Band 45. Emissions shall not exceed the maximum levels specified in table 9.7.5.2.4.8-1. + +**Table 9.7.5.2.4.8-1: Emissions limits for protection of adjacent band services** + +| Operating Band | Filter centre frequency, $F_{\text{filter}}$ | Maximum Level [dBm] | Measurement Bandwidth | +|----------------|---------------------------------------------------------------------|---------------------|-----------------------| +| 45 | $F_{\text{filter}} = 1467.5$ | -11 | 1 MHz | +| | $F_{\text{filter}} = 1468.5$ | -14 | 1 MHz | +| | $F_{\text{filter}} = 1469.5$ | -17 | 1 MHz | +| | $F_{\text{filter}} = 1470.5$ | -24 | 1 MHz | +| | $F_{\text{filter}} = 1471.5$ | -31 | 1 MHz | +| | $1472.5 \text{ MHz} \leq F_{\text{filter}} \leq 1491.5 \text{ MHz}$ | -38 | 1 MHz | + +#### 9.7.5.2.4.9 Additional requirements for band 48 + +The following requirement may apply to BS operating in Band 48 in certain regions. Emissions shall not exceed the maximum levels specified in table 9.7.5.2.4.9-1. + +**Table 9.7.5.2.4.9-1: Additional operating band unwanted emission limits for Band 48** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| All | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -4 dBm | 1 MHz | + +#### 9.7.5.2.4.10 Additional requirements for band 53 + +The following requirement may apply to BS operating in Band 53 in certain regions. Emissions shall not exceed the maximum levels specified in table 9.7.5.2.4.10-1. + +**Table 9.7.5.2.4.10 -1: Additional operating band unwanted emission limits for Band 53** + +| Channel bandwidth [MHz] | Frequency range [MHz] | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth | +|-------------------------|-----------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| 1.4, 3, 5 | 2400 - 2477.5 | $6 \text{ MHz} \leq \Delta f < 83.5 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 83 \text{ MHz}$ | -16 dBm | 1 MHz | +| 10 | 2400 - 2473.5 | $10 \text{ MHz} \leq \Delta f < 83.5 \text{ MHz}$ | $10.5 \text{ MHz} \leq f\_offset < 83 \text{ MHz}$ | -16 dBm | 1 MHz | +| 1.4, 3, 5 | 2477.5 - 2478.5 | $5 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $5.5 \text{ MHz}$ | -4 dBm | 1 MHz | +| 10 | 2473.5 - 2478.5 | $5 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $5.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -4 dBm | 1 MHz | +| All | 2478.5 - 2483.5 | $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 4.5 \text{ MHz}$ | -1 dBm | 1 MHz | +| 1.4, 3, 5 | 2495 - 2501 | $0 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -4 dBm | 1 MHz | +| 10 | 2495 - 2505 | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -4 dBm | 1 MHz | +| 1.4, 3, 5 | 2501 - 2690 | $6 \text{ MHz} \leq \Delta f < 195 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 194.5 \text{ MHz}$ | -16 dBm | 1 MHz | +| 10 | 2505 - 2690 | $10 \text{ MHz} \leq \Delta f < 195 \text{ MHz}$ | $10.5 \text{ MHz} \leq f\_offset < 194.5 \text{ MHz}$ | -16 dBm | 1 MHz | + +#### 9.7.5.3 Minimum requirement for single RAT UTRA operation + +There is no operating band unwanted emission requirement for a single RAT UTRA FDD AAS BS. + +#### 9.7.5.4 Minimum requirement for single RAT E-UTRA operation + +##### 9.7.5.4.1 General + +The single RAT E-UTRA operating band unwanted emission minimum requirements are given in subclauses 9.7.5.4.2, 9.7.5.4.3, 9.7.5.4.4, 9.7.5.4.5 and 9.7.5.4.6. + +For an AAS BS of Wide Area BS class, the requirements of either subclause 9.7.5.4.2 (Category A limits) or subclause 9.7.5.4.3 (Category B limits) shall apply. + +For an AAS BS of Local Area BS class, the requirements of subclause 9.7.5.4.4 shall apply (Category A and B). + +For an AAS BS of Medium Range BS class, the requirements in subclause 9.7.5.4.5 shall apply (Category A and B). + +The application of either Category A or Category B limits shall be the same as for Transmitter spurious emissions (Mandatory Requirements) in subclause 9.7.6. + +#### 9.7.5.4.2 Minimum requirements for Wide Area BS (Category A) + +For E-UTRA RIB operating in Bands 5, 6, 8, 12, 13, 14, 17, 18, 19, 26, 27, 28, 29, 31, 44, 68, 71, 72, 73, 85, 87, 88 the *minimum requirements* are specified in tables 9.7.5.4.2-1 to 9.7.5.4.2-3. + +**Table 9.7.5.4.2-1: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands <1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -13dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.2-2: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands <1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -6 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -4dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.2-3: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands <1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (NOTE 9) | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -4dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +For a E-UTRA RIB operating in Bands 1, 2, 3, 4, 7, 9, 10, 11, 21, 22, 23, 24, 25, 30, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 45, 48, 50, 54, 65, 66, 69, 70, 74, 75, emissions shall use the *minimum requirements* specified in tables 9.7.5.4.2-4 to 9.7.5.4.2-6: + +**Table 9.7.5.4.2-4: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands >1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm | 1MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -4dBm/1MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.5.4.2-5: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands >1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -6 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm | 1MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -4dBm/1MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.5.4.2-6: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands >1GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (NOTE 7) | 1MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -4dBm/1MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +### 9.7.5.4.3 Minimum requirements for Wide Area BS (Category B) + +#### 9.7.5.4.3.1 General + +For Category B Operating band unwanted emissions, there are two options for the limits that may be applied regionally. Either the limits in subclause 9.7.5.4.3.2 or subclause 9.7.5.4.3 shall be applied. + +#### 9.7.5.4.3.2 Category B requirements (Option 1) + +For a E-UTRA RIB operating in Bands 5, 8, 12, 13, 14, 17, 20, 26, 27, 28, 29, 31, 44, 67, 68, 71, 72, 73, 85, 87, 88 emissions shall use the minimum requirements specified in tables 6.6.5.4.3.2-1 to 6.6.5.4.3.2-3: + +**Table 9.7.5.4.3.2-1: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands <1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -7dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.3.2-2: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands <1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -6 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -7dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.3.2-3: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands <1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm (NOTE 7) | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -7dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +For a E-UTRA RIB operating in Bands 1, 2, 3, 4, 7, 10, 22, 25, 30, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 45, 48, 50, 65, 66, 69, 70, 75, emissions shall use the *minimum requirements* specified in tables 9.7.5.4.3.2-4 to 9.7.5.4.3.2-6: + +**Table 9.7.5.4.3.2-4: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands >1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm | 1MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -6dBm/1MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.5.4.3.2-5: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands >1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -6 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm | 1MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -6dBm/1MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +**Table 9.7.5.4.3.2-6: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands >1GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (NOTE 7) | 1MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -6dBm/1MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +#### 9.7.5.4.3.3 Category B requirements (Option 2) + +The limits in this subclause are intended for Europe and may be applied regionally for a RIB operating in band 1, 3, 8, 32, 33, 34 or 65. + +For a RIB operating in band 1, 3, 8, 32, 33, 34 or 65, emissions shall use the minimum requirements specified in table 9.7.5.4.3.3-1 below for 5, 10, 15 and 20 MHz *channel bandwidth*: + +**Table 9.7.5.4.3.3-1: Regional Wide Area BS operating band unwanted emission limits in band 1, 3, 8, 32, 33, 34 or 65 for 5, 10, 15 and 20 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -17 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $1.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -4 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (NOTE 7) | 1 MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement within sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement within sub-block gaps* shall be -6dBm/1MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement within the Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +For a RIB operating in band 3 or 8, emissions shall use the *minimum requirements* specified in table 9.7.5.4.3.3-2 below for 3 MHz *channel bandwidth*. + +**Table 9.7.5.4.3.3-2: Regional Wide Area BS operating band unwanted emission limits in band 3 or 8 for 3 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | +| $0.15 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.165 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -17 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$ | -4 dBm | 1 MHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -6 dBm | 1 MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -6dBm/1MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +For a RIB operating in band 3 or 8, emissions shall not use the minimum requirements specified in table 9.7.5.4.3.3-3 below for 1.4 MHz channel bandwidth. + +**Table 9.7.5.4.3.3-3: Regional Wide Area BS operating band unwanted emission limits in band 3 or 8 for 1.4 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | +| $0.15 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.165 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (NOTE 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -17 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | -4 dBm | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -6 dBm | 1 MHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band, the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -6dBm/1MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +#### 9.7.5.4.4 Minimum requirements for Local Area BS (Category A and B) + +For Local Area BS, *minimum requirements* are specified in tables 9.7.5.4.4-1 to 9.7.5.4.4-3. + +**Table 9.7.5.4.4-1: Local Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -22 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -22 dBm | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -22dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.4-2: Local Area BS operating band unwanted emission limits for 3 MHz channel bandwidth** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -26 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -26 dBm | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -26dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.4-3: Local Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -28 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm (NOTE 7) | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -28dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +#### 9.7.5.4.5 Minimum requirements for Medium Range BS (Category A and B) + +For Medium Range BS, *minimum requirements* are specified in tables 9.7.5.4.5-1 to 9.7.5.4.5-6. + +**Table 9.7.5.4.5-1: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 45 \text{ dB} - (10/1.4) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 55 \text{ dB}$ | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -16dBm | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -16dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.5-2: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $P_{\text{rated,c,TRP}} \leq 40$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -15 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -16dBm | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -16dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.5-3: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 49 \text{ dB} - (10/3) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 59 \text{ dB}$ | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(P_{\text{rated,c,TRP}} - 59 \text{ dB}, -16 \text{ dBm})$ | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be $\text{Min}(P_{\text{rated,c,TRP}} - 59 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.5-4: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $P_{\text{rated,c,TRP}} \leq 40$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -19 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -19 dBm | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -19dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.5-5: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 53 \text{ dB} - (7/5) \times (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,TRP}} - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$ (NOTE 6) | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 9.7.5.4.5-6: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $P_{\text{rated,c,TRP}} \leq 40$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (NOTE 1, 2) | Measurement bandwidth (NOTE 7) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 13 \text{ dB} - (7/5) \times (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -20 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -20 dBm (NOTE 8) | 100 kHz | + +NOTE 1: For a RIB supporting *non-contiguous spectrum* operation within any operating band the *minimum requirement* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *minimum requirement* within *sub-block gaps* shall be -20dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *minimum requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +#### 9.7.5.4.6 Additional requirements + +##### 9.7.5.4.6.1 Additional operating band unwanted emission limits for E-UTRA bands + +These requirements may be applied for the protection of other systems operating inside or near each supported E-UTRA, E-UTRA with NB-IoT and NB-IoT BS downlink operating band. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the E-UTRA BS, or they may be set by + +local or regional regulation as a mandatory requirement for an E-UTRA operating band. It is in some cases not stated in the present document whether a requirement is mandatory or under what exact circumstances that a limit applies, since this is set by local or regional regulation. An overview of regional requirements in the present document is given in subclause 4.3. + +In certain regions the following requirement may apply. For E-UTRA, emissions shall not exceed the maximum levels specified in Tables 9.7.5.4.6.1-1. + +**Table 9.7.5.4.6.1-1: Additional operating band unwanted emission limits for E-UTRA bands <1GHz** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 8) | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|--------------------------------| +| 200 kHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.005 \text{ MHz} \leq f\_offset < 0.995 \text{ MHz}$ | -6 dBm | 10 kHz | +| 1.4 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.005 \text{ MHz} \leq f\_offset < 0.995 \text{ MHz}$ | -14 dBm | 10 kHz | +| 3 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -13 dBm | 30 kHz | +| 5 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -15 dBm | 30 kHz | +| 10 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -13 dBm | 100 kHz | +| 15 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -13 dBm | 100 kHz | +| 20 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -13 dBm | 100 kHz | +| All | $1 \text{ MHz} \leq \Delta f < \Delta f_{max}$ | $1.05 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm | 100 kHz | + +In certain regions the following requirement may apply. For E-UTRA BS operating in Bands 2, 4, 10, 23, 25, 30, 35, 36, 41, 66, 70, emissions shall not exceed the maximum levels specified in Table 9.7.5.4.6.1-2. + +**Table 9.7.5.4.6.1-2: Additional operating band unwanted emission limits for E-UTRA bands >1GHz** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 8) | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|--------------------------------| +| 1.4 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.005 \text{ MHz} \leq f\_offset < 0.995 \text{ MHz}$ | -14 dBm | 10 kHz | +| 3 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -13 dBm | 30 kHz | +| 5 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -15 dBm | 30 kHz | +| 10 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -13 dBm | 100 kHz | +| 15 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -15 dBm | 100 kHz | +| 20 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -16 dBm | 100 kHz | +| All | $1 \text{ MHz} \leq \Delta f < \Delta f_{max}$ | $1.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm | 1 MHz | + +In certain regions the following requirement may apply. For E-UTRA BS operating in Bands 12, 13, 14, 17, 29, 71, 85 emissions shall not exceed the maximum levels specified in Table 9.7.5.4.6.1-3. + +**Table 9.7.5.4.6.1-3: Additional operating band unwanted emission limits for E-UTRA (bands 12, 13, 14, 17, 29, 71 and 85)** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 8) | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|--------------------------------| +| All | $0 \text{ MHz} \leq \Delta f < 100 \text{ kHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.085 \text{ MHz}$ | -13 dBm | 30 kHz | +| All | $100 \text{ kHz} \leq \Delta f < \Delta f_{max}$ | $150 \text{ kHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm | 100 kHz | + +In certain regions, the following requirements may apply to an E-UTRA, E-UTRA with NB-IoT and NB-IoT TDD BS operating in the same geographic area and in the same operating band as another E-UTRA TDD system without synchronisation. For this case the emissions shall not exceed -52 dBm/MHz in each supported downlink operating band except in: + +- The frequency range from 10 MHz below the lower channel edge to the frequency 10 MHz above the upper channel edge of each supported band. + +#### 9.7.5.4.6.2 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For an AAS BS operating in Band 20, the level of emissions in the band 470-790 MHz, measured in an 8 MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to table 9.7.5.4.6.2-1, shall not exceed the maximum emission TRP level shown in the table. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 9.7.5.4.6.2-1: Declared emissions levels for protection of DTT** + +| Case | Measurement filter centre frequency | Condition on BS maximum aggregate TRP / 10 MHz, $P_{\text{TRP\_10MHz}}$ (NOTE) | Maximum Level $P_{\text{TRP,N,MAX}}$ | Measurement Bandwidth | +|---------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------------------------------------|--------------------------------------|-----------------------| +| A: for DTT frequencies where broadcasting is protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} \geq 59$ dBm | 0 dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{TRP\_10MHz}} < 59$ dBm | $P_{\text{TRP\_10MHz}} - 59$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} < 36$ dBm | -23 dBm | 8 MHz | +| B: for DTT frequencies where broadcasting is subject to an intermediate level of protection | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} \geq 59$ dBm | 10 dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{TRP\_10MHz}} < 59$ dBm | $P_{\text{TRP\_10MHz}} - 49$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} < 36$ dBm | -13 dBm | 8 MHz | +| C: for DTT frequencies where broadcasting is not protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | N.A. | 22 dBm | 8 MHz | + +NOTE: $P_{\text{TRP\_10MHz}}$ (dBm) is defined by the expression $P_{\text{TRP\_10MHz}} = P_{10\text{MHz}} + G_{\text{ant}} + 6\text{dB}$ for UTRA and $P_{\text{TRP\_10MHz}} = P_{10\text{MHz}} + G_{\text{ant}} + 9\text{dB}$ for E-UTRA, where $G_{\text{ant}}$ is 17 dBi + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions and the deployment (including antenna gain and feeder loss). The method outlined in annex B1 Indicates how the limit in table 9.7.5.4.6.2-1 demonstrates compliance to the regional requirement. + +#### 9.7.5.4.6.3 Co-existence with RNSS/GPS services in North America + +In regions where FCC regulation applies, requirements for protection of GPS according to FCC Order DA 20-48 applies for operation in Band 24. The following normative requirement covers the base station, to be used together with other information about the site installation to verify compliance with the requirement in FCC Order DA 20-48. The requirement applies to BS operating in Band 24 to ensure that appropriate interference protection is provided to the GPS. This requirement applies in the frequency range 1541-1650 MHz even though part of the range falls in the spurious domain. + +The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to table 9.7.5.4.6.3-1 shall not exceed the maximum TRP limits indicated in the table. + +**Table 9.7.5.4.6.3-1: Emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range (MHz) | Emission level (dBW)
(Measurement bandwidth = 1 MHz) | Emission level (dBW) of discrete emissions of less than 700 Hz bandwidth
(Measurement bandwidth = 1 kHz) | Emission level (dBW) of discrete emissions of less than 2 kHz bandwidth
(Measurement bandwidth = 1 kHz) | +|----------------|-----------------------|---------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------| +| 24 | 1541 - 1559 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | +| | 1559 - 1610 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | +| | 1610 - 1650 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | + +NOTE: The regional requirements, included in FCC Order DA 20-48 are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B1 indicates how the limit in table 9.7.5.4.6.3-1 demonstrates compliance to the regional requirement. $P_{\text{EIRP}}$ values in table 9.7.5.4.6.3-1 are the effective isotropic power (or radiated power spectral density) set in the FCC Order DA 20-48 for the specified frequency ranges and bandwidths. + +9.7.5.4.6.4 Void + +**Table 9.7.5.4.6.4-1: Void** + +9.7.5.4.6.5 Additional band 32, 50, 51, 74, 75 and 76 unwanted emissions + +In certain regions, the following requirements may apply to BS operating in Band 32 within 1452-1492 MHz, in Band 75 within 1432-1517 MHz and in Band 76 within 1427-1432 MHz. The level of operating band unwanted emissions, measured on centre frequencies $f\_offset$ with filter bandwidth, according to table 9.7.5.4.6.5-1, shall not exceed the maximum TRP limits indicated in the table.. + +For Band 32, this requirement applies in the frequency range 1452-1492 MHz when non-Mobile/Fixed Communications Network (MFCN) services are deployed in adjacent frequency ranges, while it applies also within 1427-1452 MHz and/or 1492-1517 MHz when MFCN services are deployed in such frequency ranges, even though part of the ranges falls in the spurious domain. For Band 75, this requirement applies in the frequency range 1427-1517 MHz. For Band 76, this requirement applies in the frequency range 1432-1517 MHz even though part of the range falls in the spurious domain. + +**Table 9.7.5.4.6.5-1: Declared operating band 32, 75 and 76 unwanted emission within 1427-1517 MHz** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Declared emission level [dBm] | Measurement bandwidth | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| 2.5 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | 5 MHz | +| 7.5 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | 5 MHz | +| $12.5 \text{ MHz} \leq f\_offset \leq f\_offset_{\max}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | 5 MHz | +| NOTE: | For Band 32, when non-MFCN services are deployed in the adjacent bands, $f\_offset_{\max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1454.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1489.5 MHz for the set channel position. For Band 32, when MFCN services are deployed in the adjacent frequencies, Band 75 and Band 76, $f\_offset_{\max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1429.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1514.5 MHz for the set channel position. | | + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B.1 indicates how the limit in table 9.7.5.4.6.5-1 demonstrates compliance to the regional requirement. + +In certain regions, the following requirement may apply to BS operating in Band 32 within 1452-1492MHz for the protection of non-MFCN services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to Table 9.7.5.4.6.5-2, shall not exceed the maximum TRP limits indicated in the table. This requirement applies in the frequency range 1429-1518MHz even though part of the range falls in the spurious domain. + +**Table 9.7.5.4.6.5-2: Operating band 32 declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission level [dBm] | Measurement bandwidth | +|---------------------------------------------------------------------|---------------------------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{\text{filter}} \leq 1448.5 \text{ MHz}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | 1 MHz | +| $F_{\text{filter}} = 1450.5 \text{ MHz}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | 3 MHz | +| $F_{\text{filter}} = 1493.5 \text{ MHz}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{\text{filter}} \leq 1517.5 \text{ MHz}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | 1 MHz | + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B.1 indicates how the limit in table 9.7.5.4.6.5-2 demonstrates compliance to the regional requirement. + +In certain regions, the following requirement may apply to BS operating in Band 50 and Band 75 within 1492-1517 MHz and in Band 74 within 1492-1518 MHz. The level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to table 9.7.5.4.6.5-3, shall not exceed the maximum TRP limits indicated in the table. + +**Table 9.7.5.4.6.5-3: Operating band 50, 74 and 75 declared emission above 1520 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission level [dBm] | Measurement bandwidth | +|---------------------------------------------------------------------|---------------------------------------------------|-----------------------| +| $1520.5 \text{ MHz} \leq F_{\text{filter}} \leq 1558.5 \text{ MHz}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | 1 MHz | + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B.1 indicates how the limit in table 9.7.5.4.6.5-3 demonstrates compliance to the regional requirement. + +In certain regions, the following requirement may apply to E-UTRA BS operating in Band 50 and Band 75 within 1432-1452 MHz, and in Band 51 and Band 76. Emissions shall not exceed the maximum levels specified in table 9.7.5.4.6.5-4. + +**Table 9.7.5.4.6.5-4: Additional operating band unwanted emission limits for BS operating in Band 50 and 75 within 1432-1452 MHz, and in Band 51 and 76** + +| Filter centre frequency, $F_{\text{filter}}$ | Maximum Level [dBm] | Measurement Bandwidth | +|----------------------------------------------|---------------------|-----------------------| +| $F_{\text{filter}} = 1413.5 \text{ MHz}$ | -33 | 27 MHz | + +#### 9.7.5.4.6.6 Additional requirements for band 45 + +In certain regions the following requirement may apply to E-UTRA BS operating in Band 45. Emissions shall not exceed the maximum levels specified in table 9.7.5.4.6.6-1. + +**Table 9.7.5.4.6.6-1: Emissions limits for protection of adjacent band services** + +| Operating Band | Filter centre frequency, $F_{\text{filter}}$ | Maximum Level [dBm] | Measurement Bandwidth | +|----------------|---------------------------------------------------------------------|---------------------|-----------------------| +| 45 | $F_{\text{filter}} = 1467.5$ | -11 | 1 MHz | +| | $F_{\text{filter}} = 1468.5$ | -14 | 1 MHz | +| | $F_{\text{filter}} = 1469.5$ | -17 | 1 MHz | +| | $F_{\text{filter}} = 1470.5$ | -24 | 1 MHz | +| | $F_{\text{filter}} = 1471.5$ | -31 | 1 MHz | +| | $1472.5 \text{ MHz} \leq F_{\text{filter}} \leq 1491.5 \text{ MHz}$ | -38 | 1 MHz | + +#### 9.7.5.4.6.7 Additional requirements for band 48 + +The following requirement may apply to BS operating in Band 48 in certain regions. Emissions shall not exceed the maximum levels specified in table 9.7.5.4.6.7-1. + +**Table 9.7.5.4.6.7-1: Additional operating band unwanted emission limits for Band 48** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| All | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -4 dBm | 1 MHz | + +## 9.7.6 OTA Spurious emission + +### 9.7.6.1 General + +The OTA spurious emissions limits are specified as TRP per *RIB* unless otherwise specified. + +The OTA transmitter spurious emission limits apply from 30 MHz to 12.75 GHz, excluding the following RAT-specific frequency ranges: + +- UTRA FDD BS as specified in TS 25.104 [2]: from 12.5MHz below the lowest carrier frequency used up to 12.5MHz above the highest carrier frequency used. +- E-UTRA BS as specified in TS 36.104 [4]: from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band*, where $\Delta f_{\text{OBUE}}$ is defined in subclause 9.7.1. +- MSR BS as specified in TS 37.104 [5]: from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band*, where $\Delta f_{\text{OBUE}}$ is defined in subclause 9.7.1. + +For some operating bands the upper frequency limit is higher than 12.75 GHz in order to comply with the 5th harmonic limit of the *downlink operating band*, as specified in ITU-R recommendation SM.329 [14]. In some exceptional cases, requirements apply also closer than $\Delta f_{\text{OBUE}}$ MHz from the *downlink operating band*; these cases are highlighted in the requirement tables in respective referenced UTRA, E-UTRA or MSR specifications. For operating bands supported by *multi-band RIB* each supported band including the $\Delta f_{\text{OBUE}}$ around the band are excluded from the spurious emissions requirements. + +The requirements applies for both *single band RIBs* and *multi-band RIBs* (except for frequencies at which exclusion bands or other multi-band provisions apply) and for all transmission modes foreseen by the manufacturer's specification. Unless otherwise stated, all requirements are measured as mean power. + +For operation in Region 2, where the FCC guidance for MIMO systems in [18] is applicable, the emissions limits are the same regardless of the number of transceiver units so the limits are equivalent to those for a single transceiver unit as specified in the as the corresponding applicable *non-AAS BS* per transmitter requirement specified in 3GPP TS 25.104 [2], 3GPP TS 25.105 [3], 3GPP TS 36.104 [4] or 3GPP TS 37.104 [5]. For E-UTRA the limits will be 9dB lower and for UTRA FDD the limits will be 6 dB lower, unless stated differently in regional regulation. + +The AAS BS requirements for spurious emissions limits which are specified for Band 46 or for Band 49 in 3GPP TS 37.104 [5], are applicable for AAS BS. + +For BS operating in bands n50, n51, n74, n75 and n76 additional emission limits that might be applicable in the spurious emissions frequency domain are specified in clause 9.7.5.2.4.7. + +## 9.7.6.2 MSR operation + +### 9.7.6.2.1 Minimum requirement for MSR operation + +#### 9.7.6.2.1.1 Minimum requirement (Category A) + +The TRP of any spurious emission shall not exceed the limits in table 9.7.6.2.1.1-1 + +**Table 9.7.6.2.1.1-1: AAS BS OTA Spurious emission limits, Category A** + +| Frequency range | Maximum level | Measurement bandwidth | NOTE | +|--------------------------------------------------------------------------------------------------|----------------------------|-----------------------|------------------------| +| 30MHz - 1GHz | -13 + X dBm

NOTE 4, | 100 kHz | NOTE 1 | +| 1GHz - 12.75 GHz | | 1 MHz | NOTE 1, NOTE 2 | +| 12.75 GHz – 5 th harmonic of the upper frequency edge of the DL operating band in GHz | | 1 MHz | NOTE 1, NOTE 2, NOTE 3 | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [14], s4.1 +NOTE 2: Upper frequency as in ITU-R SM.329 [14] , s2.5 table 1 +NOTE 3: This spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the UL *operating band* is reaching beyond 12.75 GHz. +NOTE 4: X = 9 dB for E-UTRA, X = 6 dB for UTRA, unless stated differently in regional regulation. +NOTE 5: The frequency range from $F_{BW,RF,DL,low} - \Delta f_{OBUE}$ (i.e. $\Delta f_{OBUE}$ below the lowest frequency of the BS transmitter *operating band*) to $F_{BW,RF,DL,high} + \Delta f_{OBUE}$ (i.e. $\Delta f_{OBUE}$ above the highest frequency of the BS transmitter *operating band*) may be excluded from the requirement. $\Delta f_{OBUE}$ is defined in clause 6.6.1. For a *multiband RIB*, the exclusion applies for all supported operating bands. + +#### 9.7.6.2.1.2 Minimum requirement (Category B) + +For UTRA, the minimum requirement is specified in subclause 9.7.6.3.1.2 + +For E-UTRA, the minimum requirement is specified in subclause 9.7.6.4.1.2 + +For NR, the minimum requirement is specified in 3GPP TS 38.104 [27] in subclause 9.7.5.2.2. + +#### 9.7.6.2.1.3 (void) + +## 9.7.6.2.2 Protection of the BS receiver of own or different BS + +This requirement shall be applied for FDD operation in order to prevent the receivers of own or a different BS of the same band being desensitised by emissions from a *OTA AAS BS*. + +The requirement is a co-location requirement. The power levels are specified at the *co-location reference antenna* output. + +The power sum of any spurious emissions is specified over all supported polarizations of the *co-location reference antenna* and shall not exceed the limits in table 9.7.6.2.2-1 depending on the declared Base Station class and Band Category. + +**Table 9.7.6.2.2-1: BS Spurious emissions limits for protection of the BS receiver** + +| BS-class | Band category | Frequency range | Maximum Level | Measurement Bandwidth | NOTE | +|-----------------|---------------|------------------------------|---------------|-----------------------|------| +| Wide Area BS | BC1 | $F_{UL\_low} - F_{UL\_high}$ | -117 dBm | 100 kHz | | +| Wide Area BS | BC2 | $F_{UL\_low} - F_{UL\_high}$ | -119 dBm | 100 kHz | | +| Medium Range BS | BC1,BC2 | $F_{UL\_low} - F_{UL\_high}$ | -112 dBm | 100 kHz | | +| Local Area BS | BC1,BC2 | $F_{UL\_low} - F_{UL\_high}$ | -109 dBm | 100 kHz | | + +### 9.7.6.2.3 Additional spurious emissions requirements + +For UTRA, the minimum requirement is specified in subclause 9.7.6.3.3 + +For E-UTRA, the minimum requirement is specified in subclause 9.7.6.4.3 + +For NR, the minimum requirement is specified in 3GPP TS 38.104 [27] subclause 9.7.5.2.4. + +### 9.7.6.2.4 Co-location with other base stations + +For UTRA, the minimum requirement for Co-location with other base stations is specified in subclause 9.7.6.3.4 + +For E-UTRA, the minimum requirement for Co-location with other base stations is specified in subclause 9.7.6.4.4 + +For NR, the minimum requirement for Co-location with other base stations is specified in 3GPP TS 38.104 [27] subclause 9.7.5.2.5 + +## 9.7.6.3 Minimum requirement for single RAT UTRA operation + +### 9.7.6.3.1 Mandatory Requirements + +#### 9.7.6.3.1.1 Minimum requirement (Category A) + +The minimum requirement for single RAT UTRA BS is the same as that defined for an MSR BS in subclause 9.7.6.2.1.1. + +#### 9.7.6.3.1.2 Minimum requirement (Category B) + +The following limits shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [17], are applied. + +The TRP of any spurious emission shall not exceed the limits in table 9.7.6.2.1.1-2 + +**Table 9.7.6.3.1.2-1: OTA AAS BS Mandatory spurious emissions limits, operating band I, II, III, IV, VII, X, XXII, XXV, XXXII (Category B)** + +| Band | Maximum Level (Note 5) | Measurement Bandwidth | Notes | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------|----------------| +| 30 MHz $\leftrightarrow$ 1 GHz | $-36 + X$ dBm | 100 kHz | NOTE 1 | +| 1 GHz $\leftrightarrow F_{\text{low}} - 10$ MHz | $-30 + X$ dBm | 1 MHz | NOTE 1 | +| $F_{\text{low}} - 10$ MHz $\leftrightarrow F_{\text{high}} + 10$ MHz | $-15 + X$ dBm | 1 MHz | NOTE 2 | +| $F_{\text{high}} + 10$ MHz $\leftrightarrow 12.75$ GHz | $-30 + X$ dBm | 1 MHz | NOTE 3 | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the DL operating band in GHz | $-30 + X$ dBm | 1 MHz | NOTE 3, NOTE 4 | +| NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [14], s4.1 | | | | +| NOTE 2: Limit based on ITU-R Recommendation SM.329 [14], s4.3 and Annex 7 | | | | +| NOTE 3: Bandwidth as in ITU-R Recommendation SM.329 [14], s4.1. Upper frequency as in ITU-R SM.329 [17], s2.5 table 1 | | | | +| NOTE 4: This spurious frequency range applies only for operating bands for which the 5 th harmonic of the upper frequency edge of the UL operating band is reaching beyond 12.75 GHz. | | | | +| NOTE 5: $X = 6$ dB, unless stated differently in regional regulation. | | | | +| Key:
$F_{\text{low}}$ : The lowest downlink frequency of the operating band as defined in subclause 9.7.1
$F_{\text{high}}$ : The highest downlink frequency of the operating band as defined in subclause 9.7.1 | | | | + +**Table 9.7.6.3.1.2-2: BS Mandatory spurious emissions limits, operating band V, VIII, XII, XIII, XIV, XX, XXVI (Category B)** + +| Band | Maximum Level (Note 4) | Measurement Bandwidth | Notes | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------|--------| +| 30 MHz $\leftrightarrow F_{\text{low}} - 10$ MHz | $-36 + X$ dBm | 100 kHz | NOTE 1 | +| $F_{\text{low}} - 10$ MHz $\leftrightarrow F_{\text{high}} + 10$ MHz | $-16 + X$ dBm | 100 kHz | NOTE 2 | +| $F_{\text{high}} + 10$ MHz $\leftrightarrow 1$ GHz | $-36 + X$ dBm | 100 kHz | NOTE 1 | +| 1GHz $\leftrightarrow 12.75$ GHz | $-30 + X$ dBm | 1 MHz | NOTE 3 | +| NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [17], s4.1 | | | | +| NOTE 2: Limit based on ITU-R Recommendation SM.329 [17], s4.3 and Annex 7 | | | | +| NOTE 3: Bandwidth as in ITU-R Recommendation SM.329 [17], s4.1. Upper frequency as in ITU-R SM.329 [17], s2.5 table 1 | | | | +| NOTE 4: $X = 6$ dB, unless stated differently in regional regulation. | | | | +| Key:
$F_{\text{low}}$ : The lowest downlink frequency of the operating band as defined in subclause 9.7.1
$F_{\text{high}}$ : The highest downlink frequency of the operating band as defined in subclause 9.7.1 | | | | + +### 9.7.6.3.2 Protection of the BS receiver of own or different BS + +This requirement shall be applied for UTRA FDD operation in order to prevent the receivers of own or a different BS of the same band being desensitised by emissions from a *OTA AAS BS*. + +The requirement is a co-location requirement. The power levels are specified at the *co-location reference antenna* output. + +The power sum of any spurious emission is specified over all supported polarizations of the *co-location reference antenna* and shall not exceed the limits in table 9.7.6.3.2-1. + +**Table 9.7.6.3.2-1: BS Spurious emissions limits for protection of the BS receiver** + +| | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|-----------------|------------------------------------------|---------------|-----------------------|-------| +| Wide Area BS | $F_{\text{UL low}} - F_{\text{UL high}}$ | $-120$ dBm | 100 kHz | | +| Medium Range BS | $F_{\text{UL low}} - F_{\text{UL high}}$ | $-110$ dBm | 100 kHz | | +| Local Area BS | $F_{\text{UL low}} - F_{\text{UL high}}$ | $-106$ dBm | 100 kHz | | + +### 9.7.6.3.3 Additional spurious emissions requirements + +The TRP of any spurious emission shall not exceed the limits of table 9.7.6.3.3-1 for a AAS BS where requirements for co-existence with the system listed in the first column apply. For a *multi-band RIB*, the exclusions and conditions in the notes column of table 9.7.6.3.3-1 apply for each supported operating band. + +**Table 9.7.6.3.3-1 OTA AAS BS Spurious emissions limits for UTRA FDD BS 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 | Notes | +|-----------------------------------------------------------------|-----------------------------------|---------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | -51 dBm | 100 kHz | This requirement does not apply to UTRA FDD operating in band VIII | +| | 876 - 915 MHz | -55 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to UTRA FDD operating in band VIII, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| DCS1800 | 1805 - 1880 MHz | -41 dBm | 100 kHz | This requirement does not apply to UTRA FDD operating in band III | +| | 1710 - 1785 MHz | -55 dBm | 100 kHz | This requirement does not apply to UTRA FDD operating in band III, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| PCS1900 | 1930 - 1990 MHz | -41 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band II or band XXV | +| | 1850 - 1910 MHz | -55 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band II or band XXV, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| GSM850 or CDMA850 | 869 - 894 MHz | -51 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band V or XXVI | +| | 824 - 849 MHz | -55 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band V or XXVI, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band I, | +| | 1920 - 1980 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band I, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band II or band XXV | +| | 1850 - 1910 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band II or band XXV, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III or band IX | +| | 1710 - 1785 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III, since it is already covered by the requirement in subclause 9.7.6.3.2.
For UTRA BS operating in band IX, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in subclause 9.7.6.3.2. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band IV or band X | +| | 1710 - 1755 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band IV or band X, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or XXVI | +| | 824 - 849 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or XXVI, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band VI or XIX, E-UTRA Band 6, 18 or 19 or NR Band n18 | 860 - 890 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VI or XIX | +| | 815 - 845 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VI or XIX, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 - 2690 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VII, | +| | 2500 - 2570 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VII, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band VIII or | 925 - 960 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VIII. | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 8 or NR band n8 | 880 - 915 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VIII, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III or band IX | +| | 1749.9 - 1784.9 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III or band IX, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band IV or band X. | +| | 1710 - 1770 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band X, since it is already covered by the requirement in subclause 9.7.6.3.2. For UTRA FDD BS operating in Band IV, it applies for 1755 MHz to 1770 MHz, while the rest is covered in subclause 9.7.6.3.2. | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 - 1510.9 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI , XXI or XXXII. | +| | 1427.9 - 1447.9 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI, since it is already covered by the requirement in subclause 9.7.6.3.2. For UTRA BS operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. | +| | 1447.9 - 1462.9 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXI, since it is already covered by the requirement in subclause 9.7.6.3.2. For UTRA BS operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII | +| | 699 - 716 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIII | +| | 777 - 787 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIII, since it is already covered by the requirement in sub-clause 9.7.6.3.2. | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 - 768 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIV | +| | 788 - 798 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIV, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| E-UTRA Band 17 | 734 - 746 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII | +| | 704 - 716 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 791 - 821 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XX | +| | 832 - 862 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XX, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 -3590 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXII. | +| | 3410 -3490 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXII, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| E-UTRA Band 24 or NR band n24 | 1525 – 1559 MHz | -46 dBm | 1 MHz | | +| | 1626.5 – 1660.5 MHz | -43 dBm | 1 MHz | | +| UTRA FDD Band XXV or | 1930 - 1995 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band II or band XXV | + +| | | | | | +|------------------------------------------------------|------------------|---------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 25 or NR band n25 | 1850 - 1915 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXV, since it is already covered by the requirement in subclause 9.7.6.3.2. For UTRA FDD BS operating in Band II, it applies for 1910 MHz to 1915 MHz, while the rest is covered in sub-clause 9.7.6.3.2. | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 859-894 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or band XXVI | +| | 814-849 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXVI, since it is already covered by the requirements in subclause 9.7.6.3.2 For UTRA FDD BS operating in band V, it applies for 814MHz to 824MHz, while the rest is covered in subclause 9.7.6.3.2 | +| E-UTRA Band 27 | 852 – 869 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in Band V or XXVI. | +| | 807 – 824 MHz | -43 dBm | 1 MHz | For UTRA BS operating in Band XXVI, it applies for 807 MHz to 814 MHz, while the rest is covered in subclause 9.7.6.3.2. | +| E-UTRA Band 28 or NR band n28 | 758 – 803 MHz | -46 dBm | 1 MHz | | +| | 703 – 748 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 29 or NR band n29 | 717 – 728 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 30 or NR band n30 | 2350 - 2360 MHz | -46 dBm | 1 MHz | | +| | 2305 - 2315 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 31 or NR Band n31 | 462.5 -467.5 MHz | -46 dBm | 1 MHz | | +| | 452.5 -457.5 MHz | -43 dBm | 1 MHz | | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 – 1496 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in Band XI, XXI, or XXXII | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -46 dBm | 1 MHz | | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 – 2025 MHz | -46 dBm | 1 MHz | | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -46 dBm | 1 MHz | | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -46 dBm | 1 MHz | | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -46 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 MHz | -46 dBm | 1 MHz | | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920 MHz | -46 dBm | 1 MHz | Applicable in China | +| UTRA TDD in Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 42 | 3400 – 3600 MHz | -46 dBm | 1 MHz | | + +| | | | | | +|-------------------------------|-------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 43 | 3600 – 3800 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 - 803 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 45 | 1447 - 1467 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 47 | 5855 - 5925 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 49 | 3550 – 3700 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 52 | 3300 – 3400 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 65 or NR band n65 | 2110 - 2200 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in band I, | +| | 1920 - 2010 MHz | -43 dBm | 1 MHz | For UTRA BS operating in Band I, it applies for 1980 MHz to 2010 MHz, while the rest is covered in subclause 9.7.6.3.2 | +| E-UTRA Band 66 or NR band n66 | 2110 - 2200 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in band IV or X . | +| | 1710 - 1780 MHz | -43 dBm | 1 MHz | For UTRA BS operating in Band IV, this requirement applies for 1755 MHz to 1780 MHz, while the rest is covered in subclause 9.7.6.3.2. For UTRA BS operating in Band X, this requirement applies for 1770 MHz to 1780 MHz, while the rest is covered in subclause 9.7.6.3.2. | +| E-UTRA Band 67 or NR band n67 | 738 - 758 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 68 | 753 -783 MHz | -46 dBm | 1 MHz | | +| | 698-728 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 69 | 2570 - 2620 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 70 or NR band n70 | 1995 – 2020 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in band II or XXV. | +| | 1695 – 1710 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 71 | 617 - 652 MHz | -52 dBm | 1 MHz | | +| | 663 – 698 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 MHz | -52 dBm | 1 MHz | | +| | 451 - 456 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 73 | 460 - 465 MHz | -52 dBm | 1 MHz | | +| | 450 - 455 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 74 or NR Band n74 | 1475 – 1518 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI, XXI or XXXII. | +| | 1427 – 1470 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 75 or NR Band n75 | 1432 - 1517 MHz | -46 dBm | 1 MHz | | + +| | | | | | +|---------------------------------|---------------------|---------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 76 or NR Band n76 | 1427 - 1432 MHz | -46 dBm | 1 MHz | | +| NR Band n77 | 3300 MHz – 4200 MHz | -46 dBm | 1 MHz | | +| NR Band n78 | 3300 MHz – 3800 MHz | -46 dBm | 1 MHz | | +| NR Band n79 | 4.4 – 5.0 GHz | -46 dBm | 1 MHz | | +| NR Band n80 | 1710 – 1785 MHz | -43 dBm | 1 MHz | | +| NR Band n81 | 880 – 915 MHz | -43 dBm | 1 MHz | | +| NR Band n82 | 832 – 862 MHz | -43 dBm | 1 MHz | | +| NR Band n83 | 703 – 748 MHz | -43 dBm | 1 MHz | | +| NR Band n84 | 1920 – 1980 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 85 or NR band n85 | 728 - 746 MHz | -46 dBm | 1 MHz | | +| | 698 - 716 MHz | -43 dBm | 1 MHz | | +| NR Band n86 | 1710 – 1780 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 87 | 420 - 425 MHz | -52 dBm | 1 MHz | | +| | 410 – 415 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 88 | 422 - 427 MHz | -52 dBm | 1 MHz | | +| | 412 - 417 MHz | -49 dBm | 1 MHz | | +| NR Band n89 | 824 - 849 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or XXVI, since it is already covered by the requirement in clause 9.7.6.3.2. | +| NR Band n91 | 1427 - 1432 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI , XXI or XXXII. | +| | 832 – 862 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XX, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| NR Band n92 | 1432 - 1517 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI , XXI or XXXII. | +| | 832 – 862 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XX, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| NR Band n93 | 1427 - 1432 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI , XXI or XXXII. | +| | 880 – 915 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VIII, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| NR Band n94 | 1432 - 1517 MHz | -46 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI , XXI or XXXII. | +| | 880 – 915 MHz | -43 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VIII, since it is already covered by the requirement in subclause 9.7.6.3.2. | +| NR band n95 | 2010 – 2025 MHz | -46 dBm | 1 MHz | | +| NR band n96 | 5925 – 7125 MHz | -46 dBm | 1 MHz | | +| NR band n97 | 2300 – 2400 MHz | -46 dBm | 1 MHz | | +| NR band n98 | 1880 – 1920 MHz | -46 dBm | 1 MHz | | +| NR band n99 | 1626.5 – 1660.5 | -43 dBm | 1 MHz | | +| NR band n102 | 5925 – 6425 MHz | -46 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -46 dBm | 1 MHz | | +| | 787 – 788 MHz | -43 dBm | 1 MHz | | +| NR band n104 | 6425 – 7125 MHz | -46 dBm | 1 MHz | | +| NR band n105 | 612 – 652 MHz | -46 dBm | 1 MHz | | +| | 663 – 703 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 MHz | -46 dBm | 1 MHz | | +| | 896 – 901 MHz | -43 dBm | 1 MHz | | +| NR Band n109 | 1432 - 1517 MHz | -46 dBm | 1 MHz | | +| | 703 – 733 MHz | -43 dBm | 1 MHz | | + +- NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the *downlink operating band* (see subclause 9.7.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. + +The following requirement may be applied for the protection of PHS in geographic areas in which both PHS and UTRA FDD are deployed. This requirement is also applicable at specified frequencies falling between 12.5MHz below the first carrier frequency used and 12.5MHz above the last carrier frequency used. + +The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.3.3-2: AAS BS OTA Spurious emissions limits for BS in geographic coverage area of PHS** + +| Band | Maximum Level | Measurement Bandwidth | Notes | +|---------------------|---------------|-----------------------|-------| +| 1884.5 - 1915.7 MHz | -35 dBm | 300 kHz | | + +**Table 9.7.6.3.3-3: Void** + +NOTE: This requirement for the frequency range 2610-2615 MHz may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD are deployed. + +The following requirement shall be applied to AAS BS 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. + +The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.3.3-4: AAS BS OTA Spurious emissions limits** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Notes | +|----------------|---------------|---------------|-----------------------|-------| +| XIII | 763 - 775 MHz | -40 dBm | 6.25 kHz | | +| XIII | 793 - 805 MHz | -40 dBm | 6.25 kHz | | +| XIV | 769 - 775 MHz | -40 dBm | 6.25 kHz | | +| XIV | 799 - 805 MHz | -40 dBm | 6.25 kHz | | + +The following requirement shall be applied to AAS BS operating in Bands XXVI to ensure that appropriate interference protection is provided to 800 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. + +The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.3.3-5: AAS BS OTA Spurious emissions limits** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Notes | +|----------------|---------------|---------------|-----------------------|--------------------------------------------------------| +| XXVI | 851 - 859 MHz | -7 dBm | 100 kHz | Applicable for offsets > 37.5kHz from the channel edge | + +#### 9.7.6.3.4 Co-location with other base stations + +##### 9.7.6.3.4.1 General + +These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA BS and/or NR BS are co-located with a BS. + +The requirements assume with base stations of the same class. + +NOTE: For co-location with UTRA, the requirements are based on co-location with UTRA FDD or TDD base stations. + +The requirements are co-location emission requirements are specified as the power sum of the supported polarization(s) at the *co-location reference antenna* conducted output(s). + +##### 9.7.6.3.4.2 Minimum Requirement + +The output of the *co-location reference antenna* of any spurious emission shall not exceed the limits of table 9.7.6.3.4.2-1 for a AAS BS where requirements for co-location with a BS type listed in the first column apply, depending on the declared Base Station class. For a *multi-band RIB*, the exclusions and conditions in the Notes column of table 9.7.6.3.4.2-1 apply for each supported operating band. + +**Table 9.7.6.3.4.2-1: UTRA AAS BS OTA Spurious emissions limits for AAS BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|---------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|-------| +| GSM900 | 876-915 MHz | -122 dBm | -115 dBm | -112 dBm | 100 kHz | | +| DCS1800 | 1710 - 1785 MHz | -122 dBm | -115 dBm | -112 dBm | 100 kHz | | +| PCS1900 | 1850 - 1910 MHz | -122 dBm | -115 dBm | -112 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 - 849 MHz | -122 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 1920 - 1980 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1850 - 1910 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1710 - 1785 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 824 - 849 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 - 845 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2500 - 2570 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 880 - 915 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1447.9 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | + +| | | | | | | | +|-----------------------------------------------------|---------------------|----------|----------|----------|---------|---------------------------------------------------| +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 699 - 716 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 777 - 787 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 788 - 798 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 - 716 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 18 or NR Band n18 | 815 - 830 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 832 - 862 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 – 3490 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 42 | +| E-UTRA Band 24 or NR band n24 | 1626.5 – 1660.5 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1850 - 1915 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 814 - 849 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 27 | 807 - 824 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 28 or NR band n28 | 703 – 748 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | +| E-UTRA Band 30 or NR band n30 | 2305 - 2315 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 40 | +| E-UTRA Band 31 or NR Band n31 | 452.5 – 457.5 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | + +| | | | | | | | +|---------------------------------------------------|-----------------|----------|----------|----------|---------|-----------------------------------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 - 2025 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 2 and 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 33 and 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or NR band n41 | 2496 – 2690MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42 or 43 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 42 or 43 | +| E-UTRA Band 44 | 703 – 803 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 49 | 3550 – 3700 MHz | N/A | N/A | -112 dBm | 100 kHz | | + +| | | | | | | | +|-------------------------------|---------------------|----------|----------|----------|---------|---------------------------------------------------------| +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -112 dBm | 100 kHz | | +| E-UTRA Band 52 | 3300 – 3400 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | N/A | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 65 or NR band n65 | 1920 - 2010 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 66 or NR band n66 | 1710 – 1780 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 68 | 698 – 728 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 70 or NR band n70 | 1695 – 1710 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 71 or NR Band n71 | 663 – 698 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 72 or NR Band n72 | 451 – 456 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 73 | 450 – 455 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 74 or NR band n74 | 1427 – 1470 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR Band n77 | 3300 MHz – 4200 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR Band n78 | 3300 MHz – 3800 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR Band n79 | 4.4 – 5.0 GHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR Band n80 | 1710 – 1785 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR Band n81 | 880 – 915 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR Band n82 | 832 – 862 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR Band n83 | 703 – 748 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR Band n84 | 1920 – 1980 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | + +| | | | | | | | +|---------------------------------|---------------------|----------|----------|----------|---------|---------------------------------------------------| +| E-UTRA Band 85 or NR band n85 | 698 - 716 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR Band n86 | 1710 – 1780 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 87 | 410 – 415 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 88 | 412 – 417 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n89 | 824 - 849 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n91 | 832 – 862 MHz | N/A | N/A | -112 dBm | 100 kHz | | +| NR band n92 | 832 – 862 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n93 | 880 – 915 MHz | N/A | N/A | -112 dBm | 100 kHz | | +| NR band n94 | 880 – 915 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n95 | 2010 - 2025 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n96 | 5925 - 7125 MHz | N/A | -114 dBm | -111 dBm | 100 kHz | | +| NR band n97 | 2300 – 2400MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n98 | 1880 – 1920MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n99 | 1626.5 – 1660.5 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n102 | 5925 -6425 MHz | N/A | -114 dBm | -111 dBm | 100 kHz | | +| E-UTRA Band 103 | 787 – 788 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n104 | 6425 – 7125 MHz | -119 dBm | -114 dBm | -111 dBm | 100k Hz | | +| NR band n105 | 663 – 703 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| E-UTRA Band 106 or NR band n106 | 896 – 901 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | | +| NR band n109 | 703 – 733 MHz | -120 dBm | -115 dBm | -112 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | + +NOTE 1: As defined in the scope for spurious emissions in this subclause, the co-location requirements in table 9.7.6.3.4.2-1 do not apply for the 10 MHz frequency range immediately outside the BS transmit frequency range of a *downlink operating band* (see subclause 9.7.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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [12]. + +NOTE 2: Table 9.7.6.3.4.2-1 assumes that two operating bands, where the corresponding BS transmit and receive frequency ranges in subclause 9.7.1 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 3: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can transmit without special co-locations requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +### 9.7.6.4 Minimum requirement for single RAT E-UTRA operation + +#### 9.7.6.4.1 Mandatory Requirements + +##### 9.7.6.4.1.1 Minimum requirement (Category A) + +The minimum requirement for single RAT E-UTRA BS is the same as that defined for an MSR BS in subclause 9.7.6.2.1.1. + +##### 9.7.6.4.1.2 Minimum Requirement (Category B) + +The TRP of any spurious emission shall not exceed the limits in table 9.7.6.4.1.2-1 + +**Table 9.7.6.4.1.2-1: AAS BS OTA Spurious emissions limits, Category B** + +| Frequency range | Maximum Level (Note 4) | Measurement Bandwidth | Notes | +|------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------|----------------| +| 30 MHz $\leftrightarrow$ 1 GHz | -36 + X dBm | 100 kHz | NOTE 1 | +| 1 GHz $\leftrightarrow$ 12.75 GHz | -30 + X dBm | 1 MHz | NOTE 2 | +| 12.75 GHz $\leftrightarrow$ 5 th harmonic of the upper frequency edge of the DL operating band in GHz | -36 + X dBm | 1 MHz | NOTE 2, NOTE 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [14], s4.1 +NOTE 2: Bandwidth as in ITU-R SM.329 [14], s4.1. Upper frequency as in ITU-R SM.329 [14], s2.5 table 1 +NOTE 3: Applies only for Bands 22, 42, 43 and 48. +NOTE 4: X = 9 dB, unless stated differently in regional regulation. + +#### 9.7.6.4.2 Protection of the BS receiver of own or different BS + +This requirement shall be applied for E-UTRA FDD operation in order to prevent the receivers of own or a different BS of the same band being desensitised by emissions from a *OTA AAS BS*. + +The requirement is a co-location requirement. The power levels are specified at the *co-location reference antenna* output. + +The power sum of any spurious emission is specified over all supported polarizations of the *co-location reference antenna* and shall not exceed the limits in table 9.7.6.4.2-1. + +**Table 9.7.6.4.2-1: BS Spurious emissions limits for protection of the BS receiver** + +| | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|-----------------|------------------------------|---------------|-----------------------|-------| +| Wide Area BS | $F_{UL\_low} - F_{UL\_high}$ | - 117 dBm | 100 kHz | | +| Medium Range BS | $F_{UL\_low} - F_{UL\_high}$ | - 112 dBm | 100 kHz | | +| Local Area BS | $F_{UL\_low} - F_{UL\_high}$ | -109 dBm | 100 kHz | | + +#### 9.7.6.4.3 Additional spurious emissions requirements + +##### 9.7.6.4.3.1 General + +These requirements may be applied for the protection of system operating in frequency ranges other than the BS *downlink operating band*. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the BS, or they may be set by local or regional regulation as a mandatory requirement for an operating band. It is in some cases not stated in the present document whether a requirement is mandatory or under what exact circumstances that a limit applies, since this is set by local or regional regulation. An overview of regional requirements in the present document is given in subclause 4.5. + +Some requirements may apply for the protection of specific equipment (UE, MS and/or BS) or equipment operating in specific systems (GSM/EDGE, CDMA, UTRA, E-UTRA, NR, etc.) as listed below. + +All additional spurious requirements are TRP unless otherwise stated. + +#### 9.7.6.4.3.2 Minimum Requirement + +The TRP of any spurious emission shall not exceed the limits of table 9.7.6.4.3.2-1 for an AAS BS where requirements for co-existence with the system listed in the first column apply. For a *multi-band RIB*, the exclusions and conditions in the notes column of table 9.7.6.4.3.2-1 apply for each supported operating band. + +**Table 9.7.6.4.3.2-1: AAS BS OTA Spurious emissions limits for co-existence with systems operating in other frequency bands** + +| System type to co-exist with | Frequency range for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|-----------------------------------------------------------|----------------------------------------------|---------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | -48 dBm | 100 kHz | This requirement does not apply to BS operating in band 8 | +| | 876 - 915 MHz | -52 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to BS operating in band 8, since it is already covered by the requirement in subclause 9.7.6.4.2 | +| DCS1800 (NOTE 3) | 1805 - 1880 MHz | -38 dBm | 100 kHz | This requirement does not apply to BS operating in band 3. | +| | 1710 - 1785 MHz | -52 dBm | 100 kHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| PCS1900 | 1930 - 1990 MHz | -38 dBm | 100 kHz | This requirement does not apply to BS operating in band 2, 25, band 36 or band 70. | +| | 1850 - 1910 MHz | -52 dBm | 100 kHz | This requirement does not apply to BS operating in band 2 or 25, since it is already covered by the requirement in subclause 9.7.6.4.2. This requirement does not apply to BS operating in band 35. | +| GSM850 or CDMA850 | 869 - 894 MHz | -48 dBm | 100 kHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -52 dBm | 100 kHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band . | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65/n65. | +| | 1920 - 1980 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65/n65, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25 or 70. | +| | 1850 - 1910 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 2 or 25, since it is already covered by the requirement in subclause 9.7.6.4.2 | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 (NOTE 3) | 1805 - 1880 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9. | +| | 1710 - 1785 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in subclause 9.7.6.4.2. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66 | +| | 1710 - 1755 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band . | +| UTRA FDD Band VI, XIX or | 860 - 890 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 18, 19 | +| | 815 - 830 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 18 since it is already covered by the requirement in subclause 9.7.6.4.2. | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 6, 18, 19 | 830 - 845 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 19, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 - 2690 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 7. | +| | 2500 - 2570 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 7, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 8. | +| | 880 - 915 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 8, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9. | +| | 1749.9 - 1784.9 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66 | +| | 1710 - 1770 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 10 or 66, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 4, it applies for 1755 MHz to 1770 MHz, while the rest is covered in subclause 9.7.6.4.2. | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 - 1510.9 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50, 74, 75 | +| | 1427.9 - 1447.9 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 11 or 74, since it is already covered by the requirement in subclause 9.7.6.4.2. This requirement does not apply to BS operating in band 32, 50, 51, 75 or 76. | +| | 1447.9 - 1462.9 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 21 or 74, since it is already covered by the requirement in subclause 9.7.6.4.2. This requirement does not apply to BS operating in band 32, 50 or 75. | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 12 or 85. | +| | 699 - 716 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 12 or 85, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (NOTE 7) | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 13. | +| | 777 - 787 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 13, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| UTRA FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 14. | +| | 788 - 798 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 14, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| E-UTRA Band 17 | 734 - 746 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 17. | +| | 704 - 716 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 17, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (NOTE 7) | +| UTRA FDD Band XX or | 791 - 821 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 20 or 28. | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 20 or NR band n20 | 832 - 862 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, 42, 48, 49, 77 or 78. | +| | 3410 – 3490 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, since it is already covered by the requirement in subclause 9.7.3.3. This requirement does not apply to Band 42, 77 or 78. | +| E-UTRA Band 24 or NR band n24 | 1525 – 1559 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 24. | +| | 1626.5 – 1660.5 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 24, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 - 1995 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25 or 70. | +| | 1850 - 1915 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 25, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in subclause 9.7.6.4.2. | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 859 - 894 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 814 - 849 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 26, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 5, it applies for 814 MHz to 824 MHz, while the rest is covered in subclause 9.7.6.4.2. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band . | +| E-UTRA Band 27 | 852 – 869 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in bands 5, 26 or 27. | +| | 807 – 824 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 27, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 26, it applies for 807 MHz to 814 MHz, while the rest is covered in subclause 9.7.6.4.2. This requirement also applies to BS operating in Band 28, starting 4 MHz above the Band 28 downlink operating band (NOTE 6). | +| E-UTRA Band 28 or NR band n28 | 758 - 803 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, 28, 44, 67 or 68. | +| | 703 - 748 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in subclause 9.7.6.4.2. This requirement does not apply to BS operating in Band 44. For BS operating in Band 67, it applies for 703-736MHz. For E-UTRA BS operating in Band 68, it applies for 728MHz to 733MHz. | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 29 or 85 | +| E-UTRA Band 30 or NR Band n30 | 2350 - 2360 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 30 or 40. | +| | 2305 - 2315 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 30, since it is already covered by the requirement in subclause 9.7.6.4.2. This requirement does not apply to BS operating in Band 40. | + +| | | | | | +|---------------------------------------------------|-------------------|---------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72, 73. | +| | 452.5 – 457.5 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, since it is already covered by the requirement in subclause 9.7.6.4.2. This requirement does not apply to BS operating in band 72, 73. | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50, 74 or 75. | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 - 2025 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 2, 25 or 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 38 or 69. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or NR band n41 | 2496 – 2690MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 42, 43, 48 | +| E-UTRA Band 44 | 703 - 803 MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 - 1467 MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 47 | 5855 - 5925 MHz | -43 dBm | 1 MHz | | + +| | | | | | +|-------------------------------|-------------------|---------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 48 or NR Band n48 | 3550 - 3700 MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48 | +| E-UTRA Band 49 | 3550 - 3700 MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48 | +| E-UTRA Band 50 or NR band n50 | 1432 - 1517 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | +| E-UTRA Band 51 or NR Band n51 | 1427 - 1432 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75, 76. | +| E-UTRA Band 52 | 3300 - 3400 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 42 or 52. | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 41 or 53. | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 54 | +| E-UTRA Band 65 or NR band n65 | 2110 - 2200 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65/n65. | +| | 1920 - 2010 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 65/n65, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 1, it applies for 1980 MHz to 2010 MHz, while the rest is covered in subclause 9.7.6.4.2. | +| E-UTRA Band 66 or NR band n66 | 2110 - 2200 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10, 23 or 66. | +| | 1710 - 1780 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 66, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in subclause 9.7.6.4.2. For BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in subclause 9.7.6.4.2. | +| E-UTRA Band 67 or NR band n67 | 738 – 758 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 28 or 67. | +| E-UTRA Band 68 | 753 -783 MHz | -43 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 28, or 68. | +| | 698-728 MHz | -40 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 68, since it is already covered by the requirement in subclause 9.7.3.3. For E-UTRA BS operating in Band 28, it applies between 698 MHz and 703 MHz, while the rest is covered in subclause 9.7.3.3. | +| E-UTRA Band 69 | 2570 - 2620 MHz | -43 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 38 or 69. | +| E-UTRA Band 70 or NR band n70 | 1995 - 2020 MHz | -43 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 2, 25 or 70 | +| | 1695 – 1710 MHz | -40 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 70, since it is already covered by the requirement in subclause 9.7.6.4.2 | +| E-UTRA Band 71 or NR Band n71 | 617 – 652 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 71 or n105 | +| | 663 – 698 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 71 or n105, since it is already covered by the requirement in sub-clause 6.6.1.2 | +| E-UTRA Band 72 or | 461 - 466 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | + +| | | | | | +|-------------------------------|---------------------|---------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n72 | 451 - 456 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 72, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in band 73. | +| E-UTRA Band 73 | 460 - 465 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 450 - 455 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 73, since it is already covered by the requirement in sub-clause 6.6.1.2. | +| E-UTRA Band 74 or NR Band n74 | 1475 – 1518 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50, 74, 75. | +| | 1427 – 1470 MHz | -40 dBm | 1MHz | This requirement does not apply to BS operating in Band 74, since it is already covered by the requirement in sub-clause 6.6.1.2. This requirement does not apply to BS operating in band 32, 45, 50, 51, 75, 76. | +| E-UTRA Band 75 or NR Band n75 | 1432 - 1517 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | +| E-UTRA Band 76 or NR Band n76 | 1427 - 1432 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75, 76. | +| NR Band n77 | 3300 MHz – 4200 MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52. | +| NR Band n78 | 3300 MHz – 3800 MHz | -43 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52. | +| NR Band n79 | 4.4 – 5.0 GHz | -43 dBm | 1 MHz | | +| NR Band n80 | 1710 – 1785 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 | +| NR Band n81 | 880 – 915 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 8 | +| NR Band n82 | 832 – 862 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 20. | +| NR Band n83 | 703 – 748 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 28 | +| NR Band n84 | 1920 – 1980 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 | +| E-UTRA Band 85 or NR band n85 | 728 - 746 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 12, 29, 85. | +| | 698 - 716 MHz | -40 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 85, since it is already covered by the requirement in subclause 6.6.1.2. For E-UTRA BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7). | +| NR Band n86 | 1710 – 1780 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 66 | +| E-UTRA Band 87 | 420 - 425 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 87 or 88. | +| | 410 – 415 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 87, since it is already covered by the requirement in subclause 6.6.1.2 | +| E-UTRA Band 88 | 422 - 427 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band 87 or 88. | +| | 412 - 417 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 88, since it is already covered by the requirement in subclause 6.6.1.2. This requirement does not apply to BS operating in band 87. | +| NR Band n89 | 824 - 849 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in subclause 9.7.6.4.2. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | + +| | | | | | +|---------------------------------|---------------------|---------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n91 | 1427 - 1432 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75, 76. | +| | 832 – 862 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 20. | +| NR Band n92 | 1432 - 1517 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | +| | 832 – 862 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 20. | +| NR Band n93 | 1427 - 1432 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75, 76. | +| | 880 – 915 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 8 | +| NR Band n94 | 1432 - 1517 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | +| | 880 – 915 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 8 | +| NR Band n95 | 2010 - 2025 MHz | -43 dBm | 1 MHz | | +| NR Band n96 | 5925 - 7125 MHz | -43 dBm | 1 MHz | | +| NR Band n97 | 2300 – 2400MHz | -43 dBm | 1 MHz | | +| NR Band n98 | 1880 – 1920MHz | -43 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 24, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| NR Band n102 | 5925 - 6425 MHz | -43 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -43 dBm | 1 MHz | | +| | 787 – 788 MHz | -40 dBm | 1 MHz | | +| NR Band n104 | 6425 – 7125 MHz | -43 dBm | 1 MHz | | +| NR Band n105 | 612 – 652 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in band n71 or n105. | +| | 663 – 703 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band n105, since it is already covered by the requirement in subclause 9.7.6.4.2. | +| E-UTRA Band 106 or NR band n106 | 935 – 940 MHz | -43 dBm | 1 MHz | | +| | 896 – 901 MHz | -40 dBm | 1 MHz | | +| NR Band n109 | 1432 - 1517 MHz | -43 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75, 76. | +| | 703 - 733 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in subclause 9.7.6.4.2. This requirement does not apply to BS operating in Band 44. For E-UTRA BS operating in Band 68, it applies for 728MHz to 733MHz. | + +NOTE 1: As defined in the scope for spurious emissions in this subclause, except for the cases where the noted requirements apply to a BS operating in Band 25, Band 27, Band 28 or Band 29, the co-existence requirements in table 9.7.6.2.3.2-1 do not apply for the $\Delta f_{\text{OBUE}}$ frequency range immediately outside the *downlink operating band* (see subclause 9.7.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. + +NOTE 2: Table 9.7.6.2.3.2-1 assumes that two operating bands, where the frequency ranges in subclause 9.7.1 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 3: For the protection of DCS1800, UTRA Band III or E-UTRA Band 3 in China, the frequency ranges of the downlink and uplink protection requirements are 1805 – 1850 MHz and 1710 – 1755 MHz respectively. + +NOTE 4: TDD base stations deployed in the same geographical area, that are synchronized and use the same or adjacent operating bands can transmit without additional co-existence requirements. For unsynchronized base stations (except in Band 46, or in Band 49), special co-existence requirements may apply that are not covered by the 3GPP specifications. + +NOTE 6: For Band 28 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with Band 27 UL operating band. + +NOTE 7: For Band 29 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with UTRA Band XII or E-UTRA Band 12 UL operating band, E-UTRA Band 17 UL operating band or E-UTRA Band 85 UL operating band. + +The following requirement may be applied for the protection of PHS. This requirement is also applicable at specified frequencies falling between $\Delta f_{\text{OBUE}}$ below the lowest BS transmitter frequency of the *downlink operating band* and $\Delta f_{\text{OBUE}}$ above the highest BS transmitter frequency of the *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.4.3.2-2: AAS BS OTA Spurious emissions limits for BS for co-existence with PHS** + +| Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|---------------------------------------------------|---------------|-----------------------|---------------------------------------------------------------------------| +| 1884.5 - 1915.7 MHz | -32 dBm | 300 kHz | Applicable for co-existence with PHS system operating in 1884.5-1915.7MHz | +| NOTE: The requirement is not applicable in China. | | | | + +The following requirement shall be applied to AAS BS operating in Bands 13 and 14 to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.4.3.2-3: AAS BS OTA Spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|-------| +| 13 | 763 - 775 MHz | -37 dBm | 6.25 kHz | | +| 13 | 793 - 805 MHz | -37 dBm | 6.25 kHz | | +| 14 | 769 - 775 MHz | -37 dBm | 6.25 kHz | | +| 14 | 799 - 805 MHz | -37 dBm | 6.25 kHz | | + +The following requirement shall be applied to AAS BS operating in Band 26 to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.4.3.2-4: AAS BS OTA Spurious emissions limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|--------------------------------------------------------| +| 26 | 851 - 859 MHz | -4 dBm | 100 kHz | Applicable for offsets > 37.5kHz from the channel edge | + +**Table 9.7.6.4.3.2-5: Void** + +The following requirement may apply to AAS BS operating in Band 30 in certain regions. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.4.3.2-6: Additional AAS BS OTA Spurious emissions limits for Band 30** + +| Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|---------------------|---------------|-----------------------|-------| +| 2200MHz – 2345MHz | -36 dBm | 1 MHz | | +| 2362.5MHz – 2365MHz | -16 dBm | 1 MHz | | +| 2365MHz – 2367.5MHz | -31 dBm | 1 MHz | | +| 2367.5MHz – 2370MHz | -33 dBm | 1 MHz | | +| 2370MHz – 2395MHz | -36 dBm | 1 MHz | | + +The following requirement may apply to AAS BS operating in Band 48 in certain regions. The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.4.3.2-7: Additional AAS BS OTA Spurious emissions limits for Band 48** + +| Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------------------------------|---------------|-----------------------|-------------------------------------------------| +| 3530MHz – 3720MHz | -16 dBm | 1 MHz | Applicable 10MHz from the assigned channel edge | +| 3100MHz – 3530MHz
3720MHz – 4200MHz | -31 dBm | 1 MHz | | + +In addition to the requirements in subclauses 9.7.6.2.1, 9.7.6.2.2 and above in the present subclause, the AAS BS may have to comply with the applicable emission limits established by FCC Title 47 [15], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +**Table 9.7.6.4.3.2-8: Void** + +The following requirement shall be applied to AAS BS operating in Bands 13 and 14 to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.4.3.2-9: AAS BS OTA Spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|-------| +| 13 | 763 - 775 MHz | -37 dBm | 6.25 kHz | | +| 13 | 793 - 805 MHz | -37 dBm | 6.25 kHz | | +| 14 | 769 - 775 MHz | -37 dBm | 6.25 kHz | | +| 14 | 799 - 805 MHz | -37 dBm | 6.25 kHz | | + +The following requirement shall be applied to AAS BS operating in Band 26 to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 9.7.6.4.3.2-10: AAS BS OTA Spurious emissions limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|--------------------------------------------------------| +| 26 | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5kHz from the channel edge | + +The following requirement may apply to BS operating in Band 54 in certain regions, to be used together with other information about the site installation to verify the compliance. + +The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to table 9.7.6.4.3.2-11 shall not exceed the maximum TRP limits indicated in the table. + +**Table 9.7.6.4.3.2-11: Emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range | Declared emission level (dBW) (Measurement bandwidth = 1 MHz) | Declared emission level (dBW) of discrete emissions of less than 700 Hz bandwidth (Measurement bandwidth = 1 kHz) | Declared emission level (dBW) of discrete emissions of less than 2 kHz bandwidth (Measurement bandwidth = 1 kHz) | +|----------------|-----------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| 54 | 1541 - 1559 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | +| | 1559 - 1610 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | +| | 1610 - 1650 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | + +Note: The regional requirements specified in attachment to the FCC reference document, 0007135419, are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B1 indicates how the limit in table 9.7.6.4.3.2-11 demonstrates compliance to the regional requirement. + +#### 9.7.6.4.4 Co-location with other base stations + +##### 9.7.6.4.4.1 General + +These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD E-UTRA BS and/or NR BS are co-located with a BS. + +The requirements assume with base stations of the same class. + +NOTE: For co-location with UTRA, the requirements are based on co-location with UTRA FDD or TDD base stations. + +The requirement is a co-location requirement. The power levels are specified at the *co-location reference antenna* output. + +##### 9.7.6.4.4.2 Minimum Requirement + +The power sum of any spurious emission is specified over all supported polarizations of the *co-location reference antenna* and shall not exceed the limits of table 9.7.6.4.4.2-1 for a AAS BS where requirements for co-location with a BS type listed in the first column apply, depending on the declared Base Station class. For a *multi-band RIB*, the exclusions and conditions in the notes column of table 9.7.6.4.4.2-1 apply for each supported operating band. + +**Table 9.7.6.4.4.2-1: AAS BS OTA Spurious emissions limits for AAS BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|---------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|----------------------------------------------------------------| +| GSM900 | 876-915 MHz | -119 dBm | -112 dBm | -109 dBm | 100 kHz | | +| DCS1800 | 1710 - 1785 MHz | -119 dBm | -112 dBm | -109 dBm | 100 kHz | | +| PCS1900 | 1850 - 1910 MHz | -119 dBm | -112 dBm | -109 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 - 849 MHz | -119 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 1920 - 1980 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1850 - 1910 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1710 - 1785 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 824 - 849 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 - 845 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2500 - 2570 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 880 - 915 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1447.9 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to E-UTRA BS operating in Band 50 or 75 | + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|-----------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|--------------------------------------------------------------------| +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 699 - 716 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 777 - 787 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 788 - 798 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 - 716 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 18 or NR Band n18 | 815 - 830 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 832 - 862 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to E-UTRA BS operating in Band 32, 50 or 75 | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 – 3490 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 42 | +| E-UTRA Band 24 or NR band n24 | 1626.5 – 1660.5 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1850 - 1915 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 814 - 849 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 27 | 807 - 824 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 28 or NR band n28 | 703 – 748 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|---------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 30 or NR band n30 | 2305 - 2315 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 40 | +| E-UTRA Band 31 or NR Band n31 | 452.5 – 457.5 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 - 2025 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 2 and 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 33 and 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or NR band n41 | 2496 – 2690MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48 | +| E-UTRA Band 44 | 703 – 803 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 28 or 44 | + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|-------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|----------------------------------------------------------------------------| +| E-UTRA Band 45 | 1447 – 1467 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48. | +| E-UTRA Band 49 | 3550 – 3700 MHz | N/A | N/A | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48. | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 11, 21, 32, 51, 74, 75, 76. | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 50, 75, 76. | +| E-UTRA Band 52 | 3300 – 3400 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 42 or 52 | +| E-UTRA Band 53 or NR band n53 | 2483.5 – 2495 MHz | N/A | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 65 or NR band n65 | 1920 – 2010 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 66 or NR band n66 | 1710 – 1780 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 68 | 698 – 728 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 70 or NR band n70 | 1695 – 1710 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 71 or NR Band n71 | 663 – 698 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 72 or NR Band n72 | 451 – 456 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 73 | 450 – 455 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 74 or NR band n74 | 1427 – 1470 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 50, 51 | + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|---------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|--------------------------------------------------------------------| +| NR Band n77 | 3300 MHz – 4200 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52. | +| NR Band n78 | 3300 MHz – 3800 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52. | +| NR Band n79 | 4.4 – 5.0 GHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n80 | 1710 – 1785 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n81 | 880 – 915 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n82 | 832 – 862 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n83 | 703 – 748 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n84 | 1920 – 1980 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 85 or NR band n85 | 698 – 716 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n86 | 1710 – 1780 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 87 | 410 – 415 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 88 | 412 – 417 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n89 | 824 – 849 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n91 | 832 – 862 MHz | N/A | N/A | -109 dBm | 100 kHz | | +| NR Band n92 | 832 – 862 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n93 | 880 – 915 MHz | N/A | N/A | -109 dBm | 100 kHz | | +| NR Band n94 | 880 – 915 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n95 | 2010 – 2025 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n96 | 5925 – 7125 MHz | N/A | -111 dBm | -108 dBm | 100 kHz | | +| NR Band n97 | 2300 – 2400 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n98 | 1880 – 1920 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n102 | 5925 – 6425 MHz | N/A | -111 dBm | -108 dBm | 100 kHz | | +| E-UTRA Band 103 | 787 – 788 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR Band n104 | 6425 – 7125 MHz | -116 dBm | -111 dBm | -108 dBm | 100 kHz | | +| NR band n105 | 663 – 703 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| E-UTRA Band 106 or NR band n106 | 896 – 901 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | | +| NR band n109 | 703 – 733 MHz | -117 dBm | -112 dBm | -109 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | + +- NOTE 1: As defined in the scope for spurious emissions in this subclause, the co-location requirements in table 9.7.6.4.4.2-1 do not apply for the $\Delta f_{\text{OBUE}}$ frequency range immediately outside the BS transmit frequency range of a *downlink operating band* (see subclause 9.7.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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [12]. +- NOTE 2: Table 9.7.6.4.4.2-1 assumes that two operating bands, where the corresponding BS transmit and receive frequency ranges in subclause 9.7.1 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 3: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can transmit without special co-locations requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +## 9.8 OTA Transmitter intermodulation + +### 9.8.1 General + +The OTA transmitter intermodulation requirement is a measure of the capability of the transmitter unit to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter unit via the RDN and antenna array from a co-located base station. The requirement applies during the *transmitter ON period* and the *transmitter transient period*. + +The requirement applies at each RIB supporting transmission in the operating band. + +The transmitter intermodulation level is the *total radiated power* of the intermodulation products when an interfering signal is injected into the *co-location reference antenna*. + +### 9.8.2 Minimum requirement for MSR operation + +#### 9.8.2.1 General minimum requirement + +The transmitter intermodulation level shall not exceed the unwanted emission limits specified for OTA transmitter spurious emission in subclause 9.7.6.1, 9.7.6.2.1 and 9.7.6.2.3, OTA operating band unwanted emission in subclause 9.7.5 and OTA ACLR in subclause 9.7.3 in the presence of a wanted signal and an interfering signal according to table 9.8.2.1-1 for *OTA AAS BS* operation in BC1, BC2 and BC3. + +The requirement is applicable outside the *Base Station RF Bandwidth edges*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIBs supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block edges*. + +For *multi-band RIBs*, the requirement applies relative to the *Base Station RF Bandwidth edges* of each operating band. In case the inter *Base Station RF Bandwidth gap* is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth gap*. + +**Table 9.8.2.1-1: Interfering signal for the OTA transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA or NR signal | +| Interfering signal type | E-UTRA signal of channel bandwidth 5 MHz | +| Interfering signal power level applied to the co-location reference antenna | min(46 dBm, $P_{\text{rated,t,TRP}}$ ) | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or edge of sub-block inside a gap | ±2.5 MHz
±7.5 MHz
±12.5 MHz | +| NOTE 1: | Interfering signal positions that are partially or completely outside of any downlink operating band of the RIB is excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band , 3GPP TS 37.141 [19] provides further guidance regarding appropriate test requirements. | +| NOTE 2: | In certain regions, NOTE 1 is not applied in Band 1, 3, 8, 9, 11, 18, 19, 21, 28, 32 operating within 1 475.9 MHz to 1 495.9 MHz, 34. | +| NOTE 3: | For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the co-location reference antenna . | + +## 9.8.2.2 Additional minimum requirement (BC1 and BC2) + +The transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in subclause 9.7.6.1, 9.7.6.2.1 and 9.7.6.2.3 operating band unwanted emission in subclause 9.7.5 and ACLR in subclause 9.7.3 in the presence of a wanted signal and an interfering signal according to table 9.8.2.2-1 for BS operation in BC2. + +The requirement is applicable outside the *Base Station RF Bandwidth* edges for BC2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth* edges. + +For RIBs supporting operation in *non-contiguous spectrum* in BC1 or BC2, the requirement is also applicable inside a *sub-block gap* with a gap size larger than or equal to two times the interfering signal centre frequency offset. For RIBs supporting operation in *non-contiguous spectrum* in BC1, the requirement is not applicable inside a *sub-block gap* with a gap size equal to or larger than 5 MHz. The interfering signal offset is defined relative to the *sub-block* edges. + +For *multi-band RIBs*, the requirement applies relative to the *Base Station RF Bandwidth* edges of a BC2 operating band. The requirement is also applicable for BC1 and BC2 inside an inter *Base Station RF Bandwidth* gap equal to or larger than two times the interfering signal centre frequency offset. For RIBs supporting operation in multiple operating bands, the requirement is not applicable for BC1 band inside an inter *Base Station RF Bandwidth* gap with a gap size equal to or larger than 5 MHz. + +**Table 9.8.2.2-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA or NR or UTRA signal | +| Interfering signal type | CW | +| Interfering signal power level applied to the co-location reference antenna | min(46 dBm, $P_{\text{rated,t,TRP}}$ ) | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or edge of sub-block inside a gap | > abs(800) kHz for CW interfering signal | +| NOTE 1: | Interfering signal positions that are partially or completely outside of any downlink operating band of the RIB are excluded from the requirement. | +| NOTE 2: | For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the co-location reference antenna . | + +### 9.8.2.3 Additional minimum requirement (BC3) + +This additional requirement shall only apply for BS co-located with an UTRA TDD BS. + +The transmitter intermodulation level shall not exceed the unwanted emission limits specified for OTA transmitter spurious emission in subclause 9.7.6.1, 9.7.6.2.1 and 9.7.6.2.3 OTA operating band unwanted emission in subclause 9.7.5 and OTA ACLR in subclause 9.7.3 in the presence of a wanted signal and an interfering signal according to table 9.8.2.3-1 for AAS BS operation in BC3. + +For *multi-band RIBs*, the requirement applies relative to *the Base Station RF Bandwidth edges* of each operating band. In case the *Inter RF Bandwidth gap* is less than 3.2 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth gap*. + +**Table 9.8.2.3-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement (BC3)** + +| Parameter | Value | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| Wanted signal type | E-UTRA or NR or UTRA signal | +| Interfering signal type | 1,28 Mcps UTRA TDD signal of channel bandwidth 1,6 MHz | +| Interfering signal power level applied to the co-location reference antenna | min(46 dBm, $P_{\text{rated,t,TRP}}$ ) | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or edge of sub-block inside a gap | $\pm 0,8$ MHz
$\pm 1,6$ MHz
$\pm 2,4$ MHz | +| NOTE 1: Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are excluded from the requirement. | | +| NOTE 2: For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the co-location reference antenna . | | + +### 9.8.2.4 Additional minimum requirements + +## 9.8.3 Minimum requirement for single RAT UTRA operation + +### 9.8.3.1 General minimum requirement for FDD UTRA + +The transmitter intermodulation level shall not exceed the OTA out of band emission or the OTA spurious emission requirements of subclause 9.7.5 and subclause 9.7.6.1, 9.7.6.3.1 and 9.7.6.3.3, in the presence of interfering signal according to table 9.8.3.1-1. + +**Table 9.8.3.1-1: Interfering and wanted signal frequency offset for OTA transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | UTRA | +| Interfering signal type | UTRA | +| Interfering signal power level applied to the co-location reference antenna | min(46 dBm, $P_{\text{rated,t,TRP}}$ ) | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal or edge of sub-block inside a gap | -2,5 MHz
-7,5 MHz
-12,5 MHz
+2,5 MHz
+7,5 MHz
+12,5 MHz | +| NOTE 1: | Interference frequencies that are outside of any allocated frequency band for UTRA-FDD downlink specified in subclause 4.6 are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. | +| NOTE 2: | NOTE 1 is not applied in Band I, III, VI, VIII, IX, XI, XIX, XXI, and XXXII operating within 1 475.9 MHz to 1 495.9MHz, in certain regions. | +| NOTE 3: | For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the co-location reference antenna . | + +For RIBs supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block* edges. + +For *multi-band RIBs*, the requirement is also applicable inside an inter *Base Station RF Bandwidth* gap for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth* gap. + +## 9.8.4 Minimum requirement for single RAT E-UTRA operation + +### 9.8.4.1 General minimum requirement + +The transmitter intermodulation level shall not exceed the unwanted emission limits in subclauses 9.7.6.1, 9.7.6.4.1, 9.7.6.4.3, 9.7.5 and 9.7.3 in the presence of an E-UTRA interfering signal according to table 9.8.4.1-1. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIBs supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block* edges. + +For *multi-band RIBs*, the requirement applies relative to the *Base Station RF Bandwidth edges* of each supported operating band. In case the inter *Base Station RF Bandwidth* gap is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth* gap. + +The wanted signal and interfering signal centre frequency is specified in table 9.8.4.1-1. + +**Table 9.8.4.1-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement** + +| Parameter | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal | E-UTRA single carrier, or multi-carrier, or multiple intra-band contiguously or non-contiguously aggregated carriers | +| Interfering signal type | E-UTRA signal of channel bandwidth 5 MHz | +| Interfering signal power level applied to the co-location reference antenna | $\min(46 \text{ dBm}, P_{\text{rated,t,TRP}})$ | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal or edge of sub-block inside a sub-block gap | $\pm 2,5 \text{ MHz}$
$\pm 7,5 \text{ MHz}$
$\pm 12,5 \text{ MHz}$ | +| NOTE 1: | Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band , 3GPP TS 36.141 [20] provides further guidance regarding appropriate test requirements. | +| NOTE 2: | In certain regions, NOTE 1 is not applied in Band 1, 3, 8, 9, 11, 18, 19, 21, 28, 32 operating within 1 475.9 MHz to 1 495.9 MHz, 34, 74. | +| NOTE 3: | For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the co-location reference antenna . | + +## 9.8.4.2 Void + +**Table 9.8.4.2-1: Void** + +# 10 Radiated receiver characteristics + +## 10.1 General + +OTA receiver characteristics requirements apply to the *AAS BS* including all its functional components active unless otherwise stated in each requirement. + +Unless otherwise stated the requirements in clause 10 apply during the AAS BS *receive period*. + +The requirements in clause 10 shall be met for any transmitter setting. + +The (E-UTRA) and NR throughput requirements defined for the receiver characteristics in this clause do not assume HARQ retransmissions. + +When the AAS BS is configured to receive multiple carriers, all the throughput requirements are applicable for each received carrier. + +Each requirement shall be met over the RoAoA specified. + +For requirements which are to be met over the *OTA REFSSENS RoAoA* absolute requirement values are offset by the following term: + +$$\Delta_{\text{OTAREFSSENS}} = 44.1 - 10 \cdot \log_{10}(\text{BeW}_{\theta, \text{REFSENS}} \cdot \text{BeW}_{\phi, \text{REFSENS}}) \text{ (dB) for the reference direction.}$$ + +And + +$$\Delta_{\text{OTAREFSSENS}} = 41.1 - 10 \cdot \log_{10}(\text{BeW}_{\theta, \text{REFSENS}} \cdot \text{BeW}_{\phi, \text{REFSENS}}) \text{ (dB) for all other directions.}$$ + +For requirements which are to be met over the *minSENS RoAoA* absolute requirement values are offset by the following term: + +$$\Delta_{\min\text{SENS}} = P_{\text{REFSENS}} - \text{EIS}_{\min\text{SENS}} \text{ (dB)}$$ + +## 10.2 OTA sensitivity + +### 10.2.1 General + +The OTA sensitivity requirement is based upon the declaration of one or more *OTA sensitivity direction declarations* (OSDD), related to an *AAS BS receiver*. + +The *AAS BS receiver* may optionally be capable of redirecting/changing the *receiver target* by means of adjusting BS settings resulting in multiple *sensitivity RoAoA*. The *sensitivity RoAoA* resulting from the current AAS BS settings is the active *sensitivity RoAoA*. + +If the AAS BS is capable of redirecting the *receiver target* related to the OSDD then the OSDD shall include: + +- The set(s) of RAT, *Channel bandwidth* and declared minimum EIS level applicable to any active *sensitivity RoAoA* inside the *receiver target redirection range* in the OSDD. +- A declared *receiver target redirection range*, describing all the angles of arrival that can be addressed for the OSDD through alternative settings in the AAS BS. +- Five declared *sensitivity RoAoA* comprising the conformance testing directions as detailed in TS 37.145-2 [30]. +- The *receiver target reference direction*. + +NOTE 1: Some of the declared *sensitivity RoAoA* may coincide depending on the redirection capability. + +NOTE 2: In addition to the declared *sensitivity RoAoA*, several *sensitivity RoAoA* may be implicitly defined by the *receiver target redirection range* without being explicitly declared in the OSDD. + +NOTE 3: (Void) + +If the *AAS BS* is not capable of redirecting the *receiver target* related to the OSDD, then the OSDD includes only: + +- The set(s) of RAT, *Channel bandwidth* and declared minimum EIS level applicable to the *sensitivity RoAoA* in the OSDD. +- One declared active *sensitivity RoAoA*. +- The *receiver target reference direction*. + +NOTE 4: For AAS BS without target redirection capability, the declared (fixed) *sensitivity RoAoA* is always the active *sensitivity RoAoA*. + +The OTA sensitivity EIS level declaration shall apply to each supported polarization, under the assumption of *polarization match*. + +### 10.2.2 Minimum requirement for MSR operation + +The minimum requirements for a UTRA FDD and for UTRA TDD 1,28 Mcps option carrier OTA sensitivity are defined in subclause 10.2.3. + +The minimum requirement for an E-UTRA carrier OTA sensitivity is defined in subclause 10.2.4. + +The minimum requirement for an NR carrier OTA sensitivity is the same as that defined for *BS type 1-O* in 3GPP TS 38.104 [28] in subclause 10.2.1.2 + +### 10.2.3 Minimum requirement for single RAT UTRA operation + +For a received signal whose AoA of the incident wave is within the active *sensitivity RoAoA* of an OSDD, the error rate criterion as described below shall be met when the level of the arriving signal is equal to the minimum EIS level in the respective declared set of EIS level, RAT and *channel bandwidth*. + +For UTRA FDD, the BER shall not exceed 0,001, using the 12,2 kbps data rate reference measurement channel specified in 3GPP TS 25.104 [2]. + +For UTRA TDD 1,28 Mcps option, the BER shall not exceed 0,001, using the 12,2 kbps data rate reference measurement channel specified in 3GPP TS 25.105 [3]. + +NOTE: The requirement applies for all declared sets of EIS, RAT and *channel bandwidth*, within the OSDD comprising UTRA, and for all related active *sensitivity RoAoA* settings within the AAS BS capability. + +## 10.2.4 Minimum requirement for single RAT E-UTRA operation + +For a received signal whose AoA of the incident wave is within the active *sensitivity RoAoA* of an OSDD the throughput criterion, as described below, shall be met when the level of the arriving signal is equal to the minimum EIS level in the respective declared set of EIS level, RAT and *channel bandwidth*. + +The throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel as specified in 3GPP TS 36.104 [4] with parameters specified in table 10.2.4-1. + +NOTE 1: The requirement applies for all declared sets of EIS level, RAT and *channel bandwidth*, within the OSDD comprising E-UTRA, and for all related active *sensitivity RoAoA* settings within the AAS BS capability. + +**Table 10.2.4-1: E-UTRA AAS BS reference measurement channel** + +| E-UTRA
channel bandwidth [MHz] | Reference measurement channel | +|------------------------------------------|--------------------------------------------------| +| 1.4 | FRC A1-1 in 3GPP TS 36.104 [8], annex A.1 | +| 3 | FRC A1-2 in 3GPP TS 36.104 [8], annex A.1 | +| 5 | FRC A1-3 in 3GPP TS 36.104 [8], annex A.1 | +| 10 | FRC A1-3 in 3GPP TS 36.104 [8], annex A.1 (NOTE) | +| 15 | FRC A1-3 in 3GPP TS 36.104 [8], annex A.1 (NOTE) | +| 20 | FRC A1-3 in 3GPP TS 36.104 [8], annex A.1 (NOTE) | + +NOTE: The declared minimum EIS level is applied to a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. This reference measurement channel is not applied for Band 46 nor for Band 49. + +NOTE 2: Several OSDD EIS level declarations corresponding to different *channel bandwidths* may be made. + +## 10.3 OTA Reference sensitivity level + +### 10.3.1 General + +The OTA REFSENS requirement is intended to ensure the OTA reference sensitivity level for a declared *OTA REFSENS RoAoA*. + +The OTA reference sensitivity power level $EIS_{REFSENS}$ is the mean power received at the RIB at which a reference performance requirement shall be met for a specified reference measurement channel. + +The OTA REFSENS requirement shall apply to each supported polarization, under the assumption of *polarization match*. + +### 10.3.2 Minimum requirement for MSR operation + +For UTRA, the minimum requirement for reference sensitivity is specified in subclause 10.3.3. + +For E-UTRA, the minimum requirement for reference sensitivity is specified in subclause 10.3.4. + +For NR, the minimum requirement for reference sensitivity is the same as that specified for *BS type I-O* in 3GPP TS 38.104 [28] in subclause 10.3.2. + +### 10.3.3 Minimum requirement for single RAT UTRA operation + +If the AoA of the incident wave of a received signal is within the *OTA REFSENS RoAoA*, the error rate criterion as described below shall be met when the level of the arriving signal is equal to $EIS_{REFSENS}$ . + +For UTRA FDD, using the reference measurement channel specified in 3GPP TS 25.104 [2], the OTA reference sensitivity level and performance shall be as specified in table 10.3.3-1. + +**Table 10.3.3-1: UTRA FDD OTA reference sensitivity levels** + +| BS Class | Reference measurement channel data rate | $EIS_{REFSENS}$ [dBm] | BER | +|-----------------|-----------------------------------------|------------------------------|----------------------------| +| Wide Area BS | 12.2 kbps | $-121 - \Delta_{OTAREFSENS}$ | BER shall not exceed 0.001 | +| Medium Range BS | 12.2 kbps | $-111 - \Delta_{OTAREFSENS}$ | BER shall not exceed 0.001 | +| Local Area | 12.2 kbps | $-107 - \Delta_{OTAREFSENS}$ | BER shall not exceed 0.001 | + +### 10.3.4 Minimum requirement for single RAT E-UTRA operation + +If the AoA of the incident wave of a received signal is within the *OTA REFSENS RoAoA*, the throughput criterion as described below shall be met when the level of the arriving signal is equal to $EIS_{REFSENS}$ in the respective declared *channel bandwidth*. + +The throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel as specified in 3GPP TS 36.104 [4] with parameters specified in table 10.3.4-1 for Wide Area BS, in table 10.3.4-2 for Local Area BS and in table 10.3.4-3 for Medium Range BS. + +**Table 10.3.4-1: E-UTRA Wide area AAS BS OTA reference measurement channel** + +| E-UTRA channel bandwidth [MHz] | Reference measurement channel | $EIS_{REFSENS}$ [dBm] | +|--------------------------------|--------------------------------------------------|--------------------------------| +| 1.4 | FRC A1-1 in 3GPP TS 36.104 [8], annex A.1 | $-106.8 - \Delta_{OTAREFSENS}$ | +| 3 | FRC A1-2 in 3GPP TS 36.104 [8], annex A.1 | $-103.0 - \Delta_{OTAREFSENS}$ | +| 5 | FRC A1-3 in 3GPP TS 36.104 [8], annex A.1 | $-101.5 - \Delta_{OTAREFSENS}$ | +| 10 | FRC A1-3 in 3GPP TS 36.104 [8], annex A.1 (NOTE) | $-101.5 - \Delta_{OTAREFSENS}$ | +| 15 | FRC A1-1 in 3GPP TS 36.104 [8], annex A.1 (NOTE) | $-101.5 - \Delta_{OTAREFSENS}$ | +| 20 | FRC A1-2 in 3GPP TS 36.104 [8], annex A.1 (NOTE) | $-101.5 - \Delta_{OTAREFSENS}$ | + +NOTE: $EIS_{REFSENS}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +**Table 10.3.4-2: E-UTRA Local Area AAS BS OTA reference sensitivity levels** + +| E-UTRA channel bandwidth [MHz] | Reference measurement channel | $EIS_{REFSENS}$ [dBm] | +|--------------------------------|--------------------------------|-------------------------------| +| 1.4 | FRC A1-1 in Annex A.1 | $-98.8 - \Delta_{OTAREFSENS}$ | +| 3 | FRC A1-2 in Annex A.1 | $-95.0 - \Delta_{OTAREFSENS}$ | +| 5 | FRC A1-3 in Annex A.1 | $-93.5 - \Delta_{OTAREFSENS}$ | +| 10 | FRC A1-3 in Annex A.1 (NOTE 1) | $-93.5 - \Delta_{OTAREFSENS}$ | +| 15 | FRC A1-3 in Annex A.1 (NOTE 1) | $-93.5 - \Delta_{OTAREFSENS}$ | +| 20 | FRC A1-3 in Annex A.1 (NOTE 1) | $-93.5 - \Delta_{OTAREFSENS}$ | + +NOTE 1: $EIS_{REFSENS}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. This reference measurement channel is not applied for Band 46 nor for Band 49. + +NOTE 2: Void + +**Table 10.3.4-3: E-UTRA Medium Range BS reference sensitivity levels** + +| E-UTRA
channel bandwidth [MHz] | Reference measurement channel | EISREFSENS
[dBm] | +|-------------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------------------| +| 1.4 | FRC A1-1 in Annex A.1 | -101.8 - $\Delta_{\text{OTAREFSENS}}$ | +| 3 | FRC A1-2 in Annex A.1 | -98.0 - $\Delta_{\text{OTAREFSENS}}$ | +| 5 | FRC A1-3 in Annex A.1 | -96.5 - $\Delta_{\text{OTAREFSENS}}$ | +| 10 | FRC A1-3 in Annex A.1 (NOTE 1)
FRC A1-8 in Annex A.1 (NOTE 2) | -96.5 - $\Delta_{\text{OTAREFSENS}}$
-99.2 - $\Delta_{\text{OTAREFSENS}}$ | +| 15 | FRC A1-3 in Annex A.1 (NOTE 1) | -96.5 - $\Delta_{\text{OTAREFSENS}}$ | +| 20 | FRC A1-3 in Annex A.1 (NOTE 1)
FRC A1-9 in Annex A.1 (NOTE 2) | -96.5 - $\Delta_{\text{OTAREFSENS}}$
-99.2 - $\Delta_{\text{OTAREFSENS}}$ | + +NOTE 1: EISREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. This reference measurement channel is not applied for Band 46. + +NOTE 2: EISREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each single interlace of FRC A1-8 and A1-9. This reference measurement channel is only applied for Band 46. + +## 10.4 OTA Dynamic range + +### 10.4.1 General + +The OTA dynamic range is a measure of the capability of the receiver unit to receive a wanted signal in the presence of an interfering signal inside the received *channel bandwidth* or the capability of receiving high level of wanted signal. + +The requirement applies at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction and are within the OTA REFSENS *RoAoA*. + +The wanted and interfering signals apply to each supported polarization, under the assumption of *polarization match*. + +### 10.4.2 Minimum requirement for MSR operation + +For UTRA, the minimum requirement for dynamic range is specified in subclause 10.4.3. + +For E-UTRA, the minimum requirement for dynamic range is specified in subclause 10.4.4. + +For NR, the minimum requirement for dynamic range is the same as that specified for BS type 1-O in 3GPP TS 38.104 [28] in subclause 10.4.2 + +### 10.4.3 Minimum requirement for single RAT UTRA operation + +The BER shall not exceed 0.001 for the parameters specified in table 10.4.3-1 + +**Table 10.4.3-1: Dynamic range** + +| Parameter | Level
Wide Area BS | Level Medium
Range BS | Level Local Area
BS | Unit | +|-----------------------------------------|------------------------------------|------------------------------------|------------------------------------|--------------| +| Reference measurement channel data rate | 12.2 | 12.2 | 12.2 | kbps | +| Wanted signal mean power | -91 - $\Delta_{\text{OTAREFSENS}}$ | -81 - $\Delta_{\text{OTAREFSENS}}$ | -77 - $\Delta_{\text{OTAREFSENS}}$ | dBm | +| Interfering AWGN signal | -73 - $\Delta_{\text{OTAREFSENS}}$ | -63 - $\Delta_{\text{OTAREFSENS}}$ | -59 - $\Delta_{\text{OTAREFSENS}}$ | dBm/3.84 MHz | + +## 10.4.4 Minimum requirement for single RAT E-UTRA operation + +For E-UTRA, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel as specified in 3GPP TS 36.104 [8], annex A with parameters specified in table 10.4.4-1 for Wide Area BS, in table 10.4.4-2 for Local Area BS and in table 10.4.4-3 for Medium Range BS. + +**Table 10.4.4-1: Wide Area BS dynamic range for E-UTRA carrier** + +| E-UTRA channel bandwidth $h$ [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] / $BW_{\text{Config}}$ | Type of interfering signal | +|------------------------------------|--------------------------------------------------|--------------------------------------|------------------------------------------------------------|----------------------------| +| 1.4 | FRC A2-1 in 3GPP TS 36.104 [8], annex A.2 | $-76.3 - \Delta_{\text{OTAREFSENS}}$ | $-88.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 3 | FRC A2-2 in 3GPP TS 36.104 [8], annex A.2 | $-72.4 - \Delta_{\text{OTAREFSENS}}$ | $-84.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 5 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 | $-70.2 - \Delta_{\text{OTAREFSENS}}$ | $-82.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 10 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 (NOTE) | $-70.2 - \Delta_{\text{OTAREFSENS}}$ | $-79.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 15 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 (NOTE) | $-70.2 - \Delta_{\text{OTAREFSENS}}$ | $-77.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 20 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 (NOTE) | $-70.2 - \Delta_{\text{OTAREFSENS}}$ | $-76.4 - \Delta_{\text{OTAREFSENS}}$ | AWGN | + +NOTE: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A2-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +**Table 10.4.4-2: Local Area BS dynamic range for E-UTRA carrier** + +| E-UTRA channel bandwidth h [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] / BW_{Config} | Type of interfering signal | +|------------------------------------------------------|----------------------------------------------------|---------------------------------------|-----------------------------------------------------------------------|-----------------------------------| +| 1.4 | FRC A2-1 in 3GPP TS 36.104 [8], annex A.2 | $-68.3 - \Delta_{OTAREFSENS}$ | $-80.7 - \Delta_{OTAREFSENS}$ | AWGN | +| 3 | FRC A2-2 in 3GPP TS 36.104 [8], annex A.2 | $-64.4 - \Delta_{OTAREFSENS}$ | $-76.7 - \Delta_{OTAREFSENS}$ | AWGN | +| 5 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 | $-62.2 - \Delta_{OTAREFSENS}$ | $-74.5 - \Delta_{OTAREFSENS}$ | AWGN | +| 10 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 (NOTE 1) | $-62.2 - \Delta_{OTAREFSENS}$ | $-71.5 - \Delta_{OTAREFSENS}$ | AWGN | +| 15 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 (NOTE 1) | $-62.2 - \Delta_{OTAREFSENS}$ | $-69.7 - \Delta_{OTAREFSENS}$ | AWGN | +| 20 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 (NOTE 1) | $-62.2 - \Delta_{OTAREFSENS}$ | $-68.4 - \Delta_{OTAREFSENS}$ | AWGN | + +NOTE 1: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A2-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. This reference measurement channel is not applied for Band 46 nor for Band 49. + +NOTE 2: Void + +**Table 10.4.4-3: Medium Range BS dynamic range for E-UTRA carrier** + +| E-UTRA channel bandwidth $h$ [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] / BWConfig | Type of interfering signal | +|------------------------------------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------|----------------------------| +| 1.4 | FRC A2-1 in 3GPP TS 36.104 [8], annex A.2 | $-71.3 - \Delta_{\text{OTAREFSENS}}$ | $-83.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 3 | FRC A2-2 in 3GPP TS 36.104 [8], annex A.2 | $-67.4 - \Delta_{\text{OTAREFSENS}}$ | $-79.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 5 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 | $-65.2 - \Delta_{\text{OTAREFSENS}}$ | $-77.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 10 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 (NOTE 1)
FRC A2-4 in 3GPP TS 36.104 [8], annex A.2 (NOTE 2) | $-65.2 - \Delta_{\text{OTAREFSENS}}$
$-68.3 - \Delta_{\text{OTAREFSENS}}$ | $-74.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 15 | FRC A2-3 in Annex A.2 (NOTE 1) | $-65.2 - \Delta_{\text{OTAREFSENS}}$ | $-72.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 20 | FRC A2-3 in 3GPP TS 36.104 [8], annex A.2 (NOTE 1)
FRC A2-5 in 3GPP TS 36.104 [8], annex A.2 (NOTE 2) | $-65.2 - \Delta_{\text{OTAREFSENS}}$
$-68.3 - \Delta_{\text{OTAREFSENS}}$ | $-71.4 - \Delta_{\text{OTAREFSENS}}$ | AWGN | + +NOTE 1: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A2-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. This reference measurement channel is not applied for Band 46. + +NOTE 2: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each single interlace of FRC A2-4 and A2-5. This reference measurement channel is only applied for Band 46. + +## 10.5 OTA Adjacent channel selectivity, general blocking, and narrowband blocking + +### 10.5.1 General + +The adjacent channel selectivity (ACS), general blocking and narrowband blocking characteristics are measures of the receiver unit ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer inside the operating band. + +The requirement applies at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction, and: + +- when the wanted signal is based on $\text{EIS}_{\text{REFSENS}}$ : the AoA of the incident wave of a received signal and the interfering signal are within the OTA $\text{REFSENS RoAoA}$ . +- when the wanted signal is based on $\text{EIS}_{\text{minSENS}}$ : the AoA of the incident wave of a received signal and the interfering signal are within the $\text{minSENS RoAoA}$ . + +The wanted and interfering signals apply to each supported polarization, under the assumption of *polarization match*. + +NOTE: For Single RAT requirements, the in-band selectivity characteristics is referred to as "adjacent channel selectivity", whereas for the MSR requirements, the corresponding property is referred to as "general blocking" since the adjacent frequency range may not carry a channel addressable from the interfered carrier. + +The in-band blocking requirement applies from $F_{UL\_low} - \Delta f_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ , excluding the downlink frequency range of the FDD *operating band*. The $\Delta f_{OOB}$ is defined in table 10.5-1. + +**Table 10.5-1: $\Delta f_{OOB}$ offset for operating bands** + +| Operating band characteristics | \Delta f_{OOB} [MHz] | +|----------------------------------------------------------|------------------------------------------| +| $F_{UL\_high} - F_{UL\_low} < 100$ MHz | 20 | +| $100$ MHz $\leq F_{UL\_high} - F_{UL\_low} \leq 900$ MHz | 60 | + +## 10.5.2 Minimum requirement for MSR operation + +### 10.5.2.1 General minimum requirement + +For the general blocking requirement, the interfering signal shall be a UTRA FDD signal as specified in 3GPP TS 37.104 [9], annex A for a UTRA, E-UTRA or NR ( $\leq 20$ MHz) wanted signal. The interfering signal shall be a 20 MHz E-UTRA signal for NR wanted signal channel bandwidth greater than 20MHz. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges* applicable to each RIB. + +For RIB supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 15 MHz. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least 15 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal at the RIB, using the parameters in tables 7.4.2.1-1 and 7.4.2.1-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any NR carrier, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channel defined for *BS type 1-O* in TS 38.104 [28], subclause 10.3.2 + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{OTAREFSENS}$ and $\Delta_{minSENS}$ . + +For *multi-band RIBs*, the requirement applies according to table 10.5.2.1-1 for the in-band blocking frequency ranges of each supported operating band. + +**Table 10.5.2.1-1: General blocking requirement** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] (NOTE 1) | Centre Frequency of Interfering Signal | Interfering signal centre frequency minimum offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap [MHz] | +|-------------------|-------------------------------------------------|----------------------------------------------------------|--------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | $-40 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 7) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 2, 5) | $F_{\text{UL\_low}} - \Delta f_{\text{OOB}}$ to
$F_{\text{UL\_high}} + \Delta f_{\text{OOB}}$ | $(\pm 7.5 + z)$ (NOTE 9) | +| | $-40 + y - \Delta_{\text{minSENS}}$ (NOTE 7) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 2, 5) | | | +| Medium Range BS | $-35 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 7) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 3, 5) | | | +| | $-35 + y - \Delta_{\text{minSENS}}$ (NOTE 7) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 3, 5) | | | +| Local Area BS | $-30 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 7) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 4, 5) | | | +| | $-30 + y - \Delta_{\text{minSENS}}$ (NOTE 7) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 4, 5) | | | + +NOTE 1: $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{minSENS}}$ depend on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +NOTE 2: For WA BS supporting UTRA, "x" is equal to 6 in case of NR or E-UTRA or UTRA wanted signals. + +NOTE 3: For MR BS supporting UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA wanted signal. + +NOTE 4: For LA BS supporting UTRA, "x" is equal to 11 in case of NR or E-UTRA wanted signal, 6 in case of UTRA wanted signal. + +NOTE 5: For a BS not supporting UTRA, x is equal to 6 for all BS classes if NR is supported, otherwise "x" is equal to 6 for WA BS or 9 for MR BS or 11 for LA BS if NR is not supported. + +NOTE 6: For a BS capable of multi-band operation, "x" in Note 2, 3, 4, 5 applies in case of interfering signals that are in the in-band blocking frequency range of the operating band where the wanted signal is present or in the in-band blocking frequency range of an adjacent or overlapping operating band. For other in-band blocking frequency ranges of the interfering signal for the supported operating bands, "x" is equal to 1.4 dB. + +NOTE 7: For a BS that supports NR but does not support UTRA, "y" is equal to -3 for the WA and MR BS class and -5 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. + +NOTE 8: The downlink frequency range of an FDD operating band is excluded from the general blocking requirement. + +NOTE 9: For NR wanted signal channel bandwidth greater than 20 MHz, $z = 22.5$ . For all other cases, $z = 0$ . + +**Table 10.5.2.1-2: (Void)** + +NOTE: The requirement in table 10.5.2.1-1 assumes that two operating bands, where the *downlink operating band* (see subclause 4.5 in 3GPP TS 37.104 [9]) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +## 10.5.2.2 General narrowband blocking minimum requirement + +For the general narrowband blocking requirement, the interfering signal shall be an E-UTRA 1RB signal as specified in 3GPP TS 37.104 [9], annex A. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIBs supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 3 MHz. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least 3 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal at the RIB using the parameters in table 10.5.2.2-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined for *BS type 1-O* in TS 38.104 [28], subclause 10.3.2 + +**Table 10.5.2.2-1: Narrowband blocking requirement** + +| Base Station Type | RAT of the carrier | Wanted signal mean power [dBm] (NOTE 1, 2, 6) | Interfering signal mean power [dBm] | Interfering RB (NOTE 3) centre frequency offset from the AAS Base Station RF Bandwidth edge or edge of sub-block inside a gap [kHz] | | +|-------------------|--------------------|-----------------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|--| +| Wide Area BS | E-UTRA, UTRA, NR | $EIS_{REFSENS} + x$ dB | $-49 - \Delta_{OTAREFSENS}$ | $\pm(240 + m*180)$ ,
$m=0, 1, 2, 3, 4, 9, 14$
(Note 4) | | +| | | $EIS_{minSENS} + x$ dB | $-49 - \Delta_{minSENS}$ | | | +| Medium Range BS | | $EIS_{REFSENS} + x$ dB | $-44 - \Delta_{OTAREFSENS}$ | | | +| | | $EIS_{minSENS} + x$ dB | $-44 - \Delta_{minSENS}$ | | | +| Local Area BS | | $EIS_{REFSENS} + x$ dB | $-41 - \Delta_{OTAREFSENS}$ | $\pm(550 + m*180)$ ,
$m=0, 1, 2, 3, 4, 29, 54, 79, 99$ (Note 5) | | +| | | $EIS_{minSENS} + x$ dB | $-41 - \Delta_{minSENS}$ | | | + +NOTE 1: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depend on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +NOTE 2: "x" is equal to 6 dB in case of E-UTRA or UTRA or NR wanted signals. + +NOTE 3: Interfering signal (E-UTRA 3 MHz) consisting of one resource block positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the AAS *Base Station RF Bandwidth* edge. + +NOTE 4: Applicable for *channel bandwidths* equal to or below 20 MHz. + +NOTE 5: Applicable for *channel bandwidths* above 20 MHz. + +NOTE 6: 7.5 kHz shift is not applied to the wanted signal of NR. + +NOTE 7: Void + +### 10.5.2.3 Additional BC3 blocking minimum requirement + +This additional requirement only applies for BS operating in the same geographical area as UTRA TDD. + +For the additional BC3 blocking requirement, the interfering signal is a 1,28 Mcps UTRA TDD signal as specified in 3GPP TS 37.104 [9], annex A. + +The requirement is always applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least 4.8 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal at the RIB, using the parameters in table 10.5.2.3-1, the following requirements shall be met: + +- For any E-UTRA TDD carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. + +**Table 10.5.2.3-1: Additional blocking requirement for BC3** + +| Operating Band | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] (NOTE) | Interfering signal centre frequency minimum offset from the Base Station RF Bandwidth edge [MHz] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|-------------------------------------|---------------------------------------|--------------------------------------------------------------------------------------------------| +| 33 - 39 | (F UL_low - 20) to (F UL_high + 20) | -40 - Δ OTAREFSENS | EIS REFSENS + 6 dB | ±2,4 | +| | | -40 - Δ minSENS | EIS minSENS + 6 dB | | +| 40 | (F UL_low - 60) to (F UL_high + 60) | -40 - Δ OTAREFSENS | EIS REFSENS + 6 dB | ±2,4 | +| | | -40 - Δ minSENS | EIS minSENS + 6 dB | | +| NOTE: EIS REFSENS and EIS minSENS depend on the RAT, the BS class and on the channel bandwidth , see subclauses 10.3 and 10.2. | | | | | + +## 10.5.3 Minimum requirement for single RAT UTRA operation + +### 10.5.3.1 General + +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 an adjacent channel signal at a given frequency offset from the centre 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). + +The interference signal is offset from the wanted signal by the frequency offset Fuw. The interference signal shall be a W-CDMA signal as specified in 3GPP TS 25.104 [6] Annex C. + +For RIBs supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 5 MHz. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap* and is equal to -2.5MHz/+2.5MHz, respectively. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap* at the RIB, in case the gap size is at least 5 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -2.5MHz/+2.5MHz, respectively. + +The OTA levels are applied referenced to ΔminSENS. + +### 10.5.3.2 Minimum requirement + +The BER shall not exceed 0.001 for the parameters specified in table 10.5.3.2-1. + +**Table 10.5.3.2-1: Adjacent channel selectivity** + +| Parameter | Level Wide Area BS | Level Medium Range BS | Level Local Area / Home BS | Unit | +|-------------------------------|-----------------------------|-----------------------------|-----------------------------|------| +| Data rate | 12.2 | 12.2 | 12.2 | kbps | +| Wanted signal mean power | -115 - Δ minSENS | -105 - Δ minSENS | -101 - Δ minSENS | dBm | +| Interfering signal mean power | -52 - Δ minSENS | -42 - Δ minSENS | -38 - Δ minSENS | dBm | +| Fuw offset (Modulated) | ±5 | ±5 | ±5 | MHz | + +### 10.5.3.3 Minimum requirement - Co-location with UTRA-TDD + +The current state-of-the-art technology does not allow a single generic solution for co-location with UTRA-TDD on adjacent frequencies for 30dB BS-BS minimum coupling loss. + +Further information and analysis for this scenario can be found in TR 25.942 [12]. + +## 10.5.4 Minimum requirement for single RAT E-UTRA operation + +### 10.5.4.1 General + +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 an adjacent channel signal with a specified centre frequency offset of the interfering signal to the band edge of a victim system. For E-UTRA *OTA AAS BS*, the interfering signal shall be an E-UTRA signal as specified in 3GPP TS 36.104 [8] Annex C. + +### 10.5.4.2 Minimum requirement + +The throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel. + +For E-UTRA Wide Area BS, the wanted and the interfering signal coupled to the BS antenna input are specified in tables 10.5.4.2-1 and 10.5.4.2-2 for narrowband blocking and in table 10.5.4.2-3 for ACS. The reference measurement channel for the wanted signal is identified in table 10.3.4-1 for each *channel bandwidth* and further specified in 3GPP TS 36.104 [8] Annex A. + +For E-UTRA Medium Range BS, the wanted and the interfering signal coupled to the BS antenna input are specified in tables 10.5.4.2-1 and 10.5.4.2-2 for narrowband blocking and in table 10.5.4.2-6 for ACS. Narrowband blocking requirements are not applied for Band 46. The reference measurement channel for the wanted signal is identified in table 10.3.4-3 for each *channel bandwidth* and further specified in 3GPP TS 36.104 [8] Annex A. + +For E-UTRA Local Area BS, the wanted and the interfering signal coupled to the BS antenna input are specified in tables 10.5.4.2-1 and 10.5.4.2-2 for narrowband blocking and in table 10.5.4.2-4 for ACS. Narrowband blocking requirements are not applied for Band 46 nor for Band 49. The reference measurement channel for the wanted signal is identified in table 10.3.4-2 for each *channel bandwidth* and further specified in 3GPP TS 36.104 [8] Annex A. + +For narrowband blocking the OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +For ACS the OTA levels are applied referenced to $\Delta_{\text{minSENS}}$ . + +The ACS and narrowband blocking requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIBs supporting operation in *non-contiguous spectrum* within any operating band, the ACS requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least as wide as the E-UTRA interfering signal in table 10.5.4.2-3, 10.5.4.2-4 and 10.5.4.2-5. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the ACS requirement applies in addition inside any *Inter RF Bandwidth gap* at the RIB, in case the gap size is at least as wide as the E-UTRA interfering signal in table 10.5.4.2-3, 10.5.4.2-4 and 10.5.4.2-5. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For a RIBs operating in *non-contiguous spectrum* within any operating band, the narrowband blocking requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least as wide as the *channel bandwidth* of the E-UTRA interfering signal in table 10.5.4.2-2. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the narrowband blocking requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least as wide as the E-UTRA interfering signal in table 10.5.4.2-2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 10.5.4.2-1: Narrowband blocking requirement for E-UTRA BS** + +| | Wanted signal mean power [dBm] (NOTE) | Interfering signal mean power [dBm] | Type of interfering signal | +|-----------------|---------------------------------------|-------------------------------------|----------------------------| +| Wide Area BS | $EIS_{REFSENS} + 6\text{dB}$ | $-49 - \Delta_{OTAREFSENS}$ | See table 10.5.4.2-2 | +| | $EIS_{minSENS} + 6\text{dB}$ | $-49 - \Delta_{minSENS}$ | | +| Medium Range BS | $EIS_{REFSENS} + 6\text{dB}$ | $-44 - \Delta_{OTAREFSENS}$ | See table 10.5.4.2-2 | +| | $EIS_{minSENS} + 6\text{dB}$ | $-44 - \Delta_{minSENS}$ | | +| Local Area BS | $EIS_{REFSENS} + 6\text{dB}$ | $-41 - \Delta_{OTAREFSENS}$ | See table 10.5.4.2-2 | +| | $EIS_{minSENS} + 6\text{dB}$ | $-41 - \Delta_{minSENS}$ | | + +NOTE: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depend on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +**Table 10.5.4.2-2: Interfering signal for Narrowband blocking requirement for E-UTRA BS** + +| E-UTRA channel BW of the lowest/highest carrier received [MHz] | Interfering RB centre frequency offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [kHz] | Type of interfering signal | +|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| 1.4 | $\pm(252.5 + m \cdot 180)$ , $m=0, 1, 2, 3, 4, 5$ | 1.4 MHz E-UTRA signal, 1 RB (NOTE) | +| 3 | $\pm(247.5 + m \cdot 180)$ , $m=0, 1, 2, 3, 4, 7, 10, 13$ | 3 MHz E-UTRA signal, 1 RB (NOTE) | +| 5 | $\pm(342.5 + m \cdot 180)$ , $m=0, 1, 2, 3, 4, 9, 14, 19, 24$ | 5 MHz E-UTRA signal, 1 RB (NOTE) | +| 10 | $\pm(347.5 + m \cdot 180)$ , $m=0, 1, 2, 3, 4, 9, 14, 19, 24$ | 5 MHz E-UTRA signal, 1 RB (NOTE) | +| 15 | $\pm(352.5 + m \cdot 180)$ , $m=0, 1, 2, 3, 4, 9, 14, 19, 24$ | 5 MHz E-UTRA signal, 1 RB (NOTE) | +| 20 | $\pm(342.5 + m \cdot 180)$ , $m=0, 1, 2, 3, 4, 9, 14, 19, 24$ | 5 MHz E-UTRA signal, 1 RB (NOTE) | + +NOTE: Interfering signal consisting of one resource block is positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the lower/upper Base Station RF Bandwidth edge. + +**Table 10.5.4.2-3: Adjacent channel selectivity for E-UTRA Wide Area BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE) | Interfering signal mean power [dBm] | Interfering signal centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of interfering signal | +|-----------------------------------------------------------------------|---------------------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1.4 | $EIS_{minSENS} + 11\text{dB}$ | $-52 - \Delta_{minSENS}$ | $\pm 0.7025$ | 1.4MHz E-UTRA signal | +| 3 | $EIS_{minSENS} + 8\text{dB}$ | $-52 - \Delta_{minSENS}$ | $\pm 1.5075$ | 3MHz E-UTRA signal | +| 5 | $EIS_{minSENS} + 6\text{dB}$ | $-52 - \Delta_{minSENS}$ | $\pm 2.5025$ | 5MHz E-UTRA signal | +| 10 | $EIS_{minSENS} + 6\text{dB}$ | $-52 - \Delta_{minSENS}$ | $\pm 2.5075$ | 5MHz E-UTRA signal | +| 15 | $EIS_{minSENS} + 6\text{dB}$ | $-52 - \Delta_{minSENS}$ | $\pm 2.5125$ | 5MHz E-UTRA signal | +| 20 | $EIS_{minSENS} + 6\text{dB}$ | $-52 - \Delta_{minSENS}$ | $\pm 2.5025$ | 5MHz E-UTRA signal | + +NOTE: $EIS_{minSENS}$ depends on the *channel bandwidth* as specified see subclause 10.2. + +**Table 10.5.4.2-4: Adjacent channel selectivity for E-UTRA Local Area BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering signal centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| 1.4 | EIS minSENS + 11dB | -44 – Δ minSENS | ±0.7025 | 1.4 MHz E-UTRA signal | +| 3 | EIS minSENS + 8dB | -44 – Δ minSENS | ±1.5075 | 3 MHz E-UTRA signal | +| 5 | EIS minSENS + 6dB | -44 – Δ minSENS | ±2.5025 | 5 MHz E-UTRA signal | +| 10 | EIS minSENS + 6dB | -44 – Δ minSENS | ±2.5075 | 5 MHz E-UTRA signal (NOTE 2) | +| 15 | EIS minSENS + 6dB | -44 – Δ minSENS | ±2.5125 | 5 MHz E-UTRA signal | +| 20 | EIS minSENS + 6dB | -44 – Δ minSENS | ±2.5025 | 5 MHz E-UTRA signal (NOTE 2) | + +NOTE 1: EISminSENS depends on the *channel bandwidth* as specified see subclause 10.2. +NOTE 2: This type of interfering signal is not applied for Band 46 nor for Band 49. +NOTE 3: Void + +**Table 10.5.4.2-5: Adjacent channel selectivity for E-UTRA Medium Range BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering signal centre frequency offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| 1.4 | EIS minSENS + 11dB | -47 – Δ minSENS | ±0.7025 | 1.4 MHz E-UTRA signal | +| 3 | EIS minSENS + 8dB | -47 – Δ minSENS | ±1.5075 | 3 MHz E-UTRA signal | +| 5 | EIS minSENS + 6dB | -47 – Δ minSENS | ±2.5025 | 5 MHz E-UTRA signal | +| 10 | EIS minSENS + 6dB | -47 – Δ minSENS | ±2.5075 | 5 MHz E-UTRA signal (NOTE 2) | +| 15 | EIS minSENS + 6dB | -47 – Δ minSENS | ±2.5125 | 5 MHz E-UTRA signal | +| 20 | EIS minSENS + 6dB | -47 – Δ minSENS | ±2.5025 | 5 MHz E-UTRA signal (NOTE 2) | + +NOTE 1: EISminSENS depends on the *channel bandwidth* as specified see subclause 10.2. +NOTE 2: This type of interfering signal is not applied for Band 46 nor for Band 49. +NOTE 3: Void + +## 10.6 OTA Blocking + +### 10.6.1 General + +The blocking characteristics are a measure of the receiver unit ability to receive a wanted signal at the RIB at its assigned channel in the presence of an unwanted interferer. + +The requirement applies at the *RIB* when the AoA of the incident wave of the received signal and the interfering signal are the same direction and are within the *minSENS RoAoA* + +The wanted signal applies to each supported polarization, under the assumption of *polarization match*. The interferer shall be polarization matched in-band and the polarization maintained for out-of-band frequencies. + +The out-of-band blocking requirement applies from 30 MHz to FUL\_low – ΔfOOB and from FUL\_high + ΔfOOB up to 12750 MHz, including the downlink frequency range of the FDD *operating band* for BS supporting FDD. ΔfOOB is defined in table 10.5-1. + +## 10.6.2 Minimum requirement for MSR operation + +### 10.6.2.1 General minimum requirement + +The OTA interfering signal RMS field-strength shall be set to 0.36 V/m at the RIB. + +NOTE: The RMS field-strength level in V/m is related to the interferer EIRP level at a distance described as $r$ , where EIRP is in W and $r$ is in m; for example, 0.36 V/m is equivalent to 36 dBm at fixed distance of 30 m. + +For a wanted and an interfering signal coupled to the RIB using the parameters in table 10.6.2.1-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined for *BS type 1-O* in TS 38.104 [28], subclause 10.3.2. + +For *multi-band RIB*, the requirement applies for each supported operating band. The in-band blocking frequency ranges of all supported operating bands according to table 10.6.2.1-1 shall be excluded from the requirement. + +**Table 10.6.2.1-1: Blocking performance requirement** + +| Interfering Signal mean power | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|----------------------------| +| 0.36 V/m | EIS minSENS +x dB (NOTE 1) | CW carrier | +| NOTE 1: EIS minSENS depends on the RAT, the BS class and the channel bandwidth, see subclause 7.2.
"x" is equal to 6 in case of NR, E-UTRA or UTRA wanted signals. | | | + +### 10.6.2.2 Co-location minimum requirement + +This additional blocking requirement may be applied for the protection of *AAS BS receivers* when E-UTRA BS, NR BS, UTRA BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with an AAS BS. + +The requirement is a co-location requirement. The interferer power levels are specified at the *co-location reference antenna* conducted input. The interfering power is specified per supported polarization. + +The requirement is valid over *minSENS RoAoA*. + +When the wanted and an interfering signal using the parameters in table 10.6.2.2-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. + +**Table 10.6.2.2-1: OTA Blocking requirement for co-location with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 - 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| GSM900 | 921 - 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| DCS1800 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| PCS1900 | 1930 - 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 - 885 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 - 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 - 1495.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 - 768 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 17 | 734 - 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 18 or NR Band n18 | 860 - 875 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 - 890 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band 20 | 791 - 821 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 - 1510.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3 590 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1525 - 1559 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band | 1930 - 1995 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| XXV or E-UTRA Band 25 or NR band n25 | | | | | (NOTE 1) | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 859 - 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 27 | 852 – 869 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 28 or or NR band n28 | 758 – 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717 - 728 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2350 - 2360 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 (NOTE-5) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 33 | 1900 - 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 34 or NR band n34 | 2010 - 2025 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 35 | 1850 - 1910 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 36 | 1930 - 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band c) or E-UTRA TDD Band 37 | 1910 - 1930 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 - 2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 - 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 - 2400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 42 | 3400 - 3600 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 43 | 3600 - 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 44 | 703 - 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 49 | 3550 – 3700 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|----------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| E-UTRA Band 51 or or NR band n51 | 1427– 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 52 | 3300 - 3400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 53 or NR band n53 | 2483.5 - 2495 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 66 or or NR band n66 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 69 | 2570-2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 70 or or NR band n70 | 1995 - 2020 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 71 or or NR band n71 | 617 - 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 75 or or NR band n75 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 76 or or NR band n76 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n77 | 3300 - 4200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n78 | 3300 - 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n79 | 4400 - 5000 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 85 or or NR band n85 | 728 - 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 87 | 420 - 425 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 88 | 422 - 427 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n91 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n92 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n93 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n94 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n96 | 5925 - 7125 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n102 | 5925 - 6425 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 103 | 757 - 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n105 | 612 – 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 106 or | 935 – 940 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-------------------------------------------|----------------------------| +| or NR band n106 | | | | | (NOTE 1) | | +| NR band n109 | 1432 - 1517 | +46 | +38 | +24 | EIS minSENS + x dB
(NOTE 1) | CW carrier | + +NOTE 1: EISminSENS depends on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +NOTE 2: Except for a BS operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported *uplink operating band* or in the $\Delta f_{\text{foob}}$ immediately outside any of the supported *uplink operating band*. +For a BS operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768 - 797 MHz. + +NOTE 3: 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 or E-UTRA TDD or NR TDD with E-UTRA FDD or NR FDD on adjacent frequencies with closely spaced antennas. However, there are certain site-engineering solutions that can be used. These techniques are addressed in 3GPP TR 25.942 [12]. + +NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805 - 1850 MHz. + +NOTE 5: For an AAS BS operating in band 11, 21, or 74 the requirement for co-location with Band 32 applies for interfering signal within the frequency range 1475.9 - 1495.9 MHz. + +## 10.6.3 Minimum requirement for single RAT UTRA operation + +### 10.6.3.1 General minimum requirement + +In addition to the following in-band and narrowband requirements, the general minimum requirements relating to out of band blocking defined for MSR in subclause 10.6.2.1 shall also be applied for single RAT UTRA operation. + +The minimum requirement for in-band blocking and narrowband blocking UTRA operation is defined below: + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges* applicable to each RIB. + +For RIB supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 15MHz. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap* and is equal to -7.5MHz/+7.5MHz, respectively. + +For a RIB supporting operation in *non-contiguous spectrum* the narrowband blocking requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 400kHz or 600kHz, depending on the operating band. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap* and is equal to -200kHz/+200kHz or -300kHz/+300kHz, respectively. + +For *multi-band RIBs* the requirement in the in-band blocking frequency range applies for each supported operating band. The requirement applies in addition inside any *Inter RF Bandwidth gap*, in case *Inter RF Bandwidth gap* size is at least 15MHz. The interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -7.5MHz/+7.5MHz, respectively. + +For *multi-band RIBs* the narrowband blocking requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least 400kHz or 600kHz, depending on the operating band. The interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -200kHz/+200kHz or -300kHz/+300kHz, respectively. + +For the wanted and interfering signal at the RIB, using the parameters in tables 10.6.4.1-1 and 10.6.4.1-2, the following requirements shall be met: + +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +**Table 10.6.3.1-1: In-band blocking requirement for Single RAT UTRA AAS BS** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|-------------------|----------------------------------------|----------------------------------------------|--------------------------------------|----------------------------| +| Wide Area BS | $-40 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | $\pm 10 \text{ MHz}$ | WCDMA signal (NOTE 1) | +| | $-40 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Medium Range BS | $-35 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-35 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Local Area BS | $-30 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-30 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | + +NOTE 1: The characteristics of the W-CDMA interference signal are specified in Annex C of TS 25.104 [6]. +NOTE 2: For *multi-band RIBs*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, and not in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted Signal mean power is equal to $-119.6 - \Delta_{\text{OTAREFSENS}}$ dBm or $-119.6 - \Delta_{\text{minSENS}}$ dBm as appropriate. + +NOTE: Table 10.6.4.1 assumes that two operating bands, where the downlink frequencies (see subclause 4.6) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 10.6.3.1-2: Blocking performance requirement (narrowband) for Single RAT UTRA AAS BS** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|-------------------|----------------------------------------|----------------------------------------------|------------------------------------------------------------------|----------------------------| +| Wide Area BS | $-47 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | $\pm 2.7 \text{ MHz}$ (NOTE 2)
$\pm 2.8 \text{ MHz}$ (NOTE 3) | GMSK modulated (NOTE 1) | +| | $-47 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Medium Range BS | $-42 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-42 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Local Area BS | $-37 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-37 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | + +NOTE 1: GMSK modulation as defined in TS 45.004 [26]. +NOTE 2: applies for bands II, IV, V, VIII, X, XII, XIV, XXV, XXVI +NOTE 3: applies for bands III, VIII + +### 10.6.3.2 Co-location minimum requirement + +This additional blocking requirement may be applied for the protection of *AAS BS receivers* when E-UTRA BS, NR BS, UTRA BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with an AAS BS. + +The requirement is a co-location requirement. The interferer power levels are specified at the *co-location reference antenna* conducted input. The interfering power is specified per supported polarization. + +The requirement is valid over *minSENS RoAoA*. + +When the wanted and an interfering signal using the parameters in table 10.6.2.2-1 for co-location with UTRA or E-UTRA systems and table 10.6.3.2-1 for co-location with GSM systems, the following requirements shall be met: + +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. + +**Table 10.6.3.2-1: UTRA additional OTA blocking requirement for co-location with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 - 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| GSM900 | 921 - 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| DCS1800 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| PCS1900 | 1930 - 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 - 885 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 - 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 - 1495.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 - 768 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 17 | 734 - 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 18 or NR Band n18 | 860 - 875 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 - 890 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band 20 | 791 - 821 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 - 1510.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3 590 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1525 - 1559 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band | 1930 - 1995 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| XXV or E-UTRA Band 25 or NR band n25 | | | | | (NOTE 1) | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 859 - 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 27 | 852 – 869 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 28 or or NR band n28 | 758 – 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717 - 728 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2350 - 2360 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 (NOTE-5) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 33 | 1900 - 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 34 or NR band n34 | 2010 - 2025 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 35 | 1850 - 1910 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 36 | 1930 - 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band c) or E-UTRA TDD Band 37 | 1910 - 1930 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 - 2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 - 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 - 2400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 42 | 3400 - 3600 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 43 | 3600 - 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 44 | 703 - 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 49 | 3550 – 3700 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| E-UTRA Band 51 or or NR band n51 | 1427– 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 53 or NR band n53 | 2483.5 - 2495 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 66 or or NR band n66 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 69 | 2570-2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 70 or or NR band n70 | 1995 - 2020 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 71 or or NR band n71 | 617 - 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 75 or or NR band n75 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 76 or or NR band n76 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n77 | 3300 - 4200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n78 | 3300 - 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n79 | 4400 - 5000 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 87 | 420 - 425 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 88 | 422 - 427 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n91 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n92 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n93 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n94 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n96 | 5925 - 7125 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n102 | 5925 - 6425 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 103 | 757 - 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n105 | 612 – 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 106 or or NR band n106 | 935 – 940 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n109 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|--------------------------------|----------------------------| +| | | | | | (NOTE 1) | | +| NOTE 1: EIS minSENS depends on the BS class and on the channel bandwidth , see subclause 10.2. | | | | | | | +| NOTE 2: Except for a BS operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported uplink operating band or in the $\Delta f_{\text{ooB}}$ immediately outside any of the supported uplink operating band .
For a BS operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768 - 797 MHz. | | | | | | | +| NOTE 3: 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 or E-UTRA TDD or NR TDD with E-UTRA FDD or NR FDD on adjacent frequencies with closely spaced antennas. However, there are certain site-engineering solutions that can be used. These techniques are addressed in 3GPP TR 25.942 [12]. | | | | | | | +| NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805 - 1850 MHz. | | | | | | | +| NOTE 5: For an AAS BS operating in band 11, 21, or 74 this requirement applies for interfering signal within the frequency range 1475.9 - 1495.9 MHz. | | | | | | | + +## 10.6.4 Minimum requirement for single RAT E-UTRA operation + +### 10.6.4.1 General minimum requirement + +In addition to the following in-band and narrowband requirements, the general minimum requirements relating to out of band blocking defined for MSR in subclause 10.6.2.1 shall also be applied for single RAT E-UTRA operation. + +The minimum requirement for in-band blocking E-UTRA operation is defined below: + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges* applicable to each RIB. + +For RIB supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 15 MHz. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least 15 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal at the RIB, using the parameters in tables 10.6.4.1-1 and 10.6.4.1-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +For *multi-band RIBs*, the requirement applies according to table 10.6.4.1-1 for the in-band blocking frequency ranges of each supported operating band. + +**Table 10.6.4.1-1: In-band blocking requirement for single RAT E-UTRA** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] (NOTE 1,2) | Type of Interfering Signal | Interfering signal centre frequency minimum offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap [MHz] | +|-------------------|----------------------------------------|----------------------------------------------|----------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | $-43 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | See table 10.6.4.1-2 | See table 10.6.4.1-2 | +| | $-43 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Medium Range BS | $-38 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-38 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Local Area BS | $-35 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-35 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | + +NOTE 1: $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{minSENS}}$ depend on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +NOTE 2: For *multi-band RIBs*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, and not in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to $\text{EIS}_{\text{REFSENS}} + 1.4 \text{ dB}$ or $\text{EIS}_{\text{minSENS}} + 1.4 \text{ dB}$ as appropriate. + +**Table 10.6.4.1-2: Interfering signals for single RAT E-UTRA in-band blocking performance requirement** + +| E-UTRA channel BW of the lowest/highest carrier received [MHz] | Interfering signal centre frequency minimum offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of interfering signal | +|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1.4 | $\pm 2.1$ | 1.4 MHz E-UTRA signal | +| 3 | $\pm 4.5$ | 3 MHz E-UTRA signal | +| 5 | $\pm 7.5$ | 5 MHz E-UTRA signal | +| 10 | $\pm 7.5$ | 5 MHz E-UTRA signal | +| 15 | $\pm 7.5$ | 5 MHz E-UTRA signal | +| 20 | $\pm 7.5$ | 5 MHz E-UTRA signal | +| 20 | $\pm 30$ | 20 MHz E-UTRA signal | + +## 10.6.4.2 Co-location minimum requirement + +This additional blocking requirement may be applied for the protection of *AAS BS receivers* when E-UTRA BS, NR BS, UTRA BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with an AAS BS. + +The requirement is a co-location requirement. The interferer power levels are specified at the *co-location reference antenna* conducted input. The interfering power is specified per supported polarization. + +The requirement is valid over *minSENS RoAoA*. + +When the wanted and an interfering signal using the parameters in table 10.6.2.2-1 for co-location with UTRA or E-UTRA systems and table 10.6.4.2-1 for co-location with GSM systems, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95 \%$ of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. + +**Table 10.6.4.2-1: E-UTRA additional OTA blocking requirement for co-location with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 - 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| GSM900 | 921 - 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| DCS1800 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| PCS1900 | 1930 - 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 - 885 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 - 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 - 1495.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 - 768 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 17 | 734 - 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 18 or NR Band n18 | 860 - 875 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 - 890 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band 20 | 791 - 821 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 - 1510.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3 590 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1525 - 1559 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band | 1930 - 1995 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| XXV or E-UTRA Band 25 or NR band n25 | | | | | (NOTE 1) | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 859 - 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 27 | 852 – 869 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 28 or or NR band n28 | 758 – 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717 - 728 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2350 - 2360 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 (NOTE-5) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 33 | 1900 - 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 34 or NR band n34 | 2010 - 2025 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 35 | 1850 - 1910 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 36 | 1930 - 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band c) or E-UTRA TDD Band 37 | 1910 - 1930 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 - 2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 - 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 - 2400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 42 | 3400 - 3600 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 43 | 3600 - 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 44 | 703 - 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 49 | 3550 – 3700 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| E-UTRA Band 51 or or NR band n51 | 1427– 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 53 or NR band n53 | 2483.5 - 2495 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 66 or or NR band n66 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 69 | 2570-2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 70 or or NR band n70 | 1995 - 2020 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 71 or or NR band n71 | 617 - 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 75 or or NR band n75 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 76 or or NR band n76 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n77 | 3300 - 4200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n78 | 3300 - 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n79 | 4400 - 5000 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 87 | 420 - 425 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 88 | 422 - 427 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n91 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n92 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n93 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n94 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n96 | 5925 - 7125 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n102 | 5925 - 6425 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 103 | 757 - 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n105 | 612 – 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 106 or or NR band n106 | 935 – 940 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n109 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|--------------------------------|----------------------------| +| | | | | | (NOTE 1) | | +| NOTE 1: EIS minSENS depends on the BS class and on the channel bandwidth , see subclause 10.2. | | | | | | | +| NOTE 2: Except for a BS operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported uplink operating band or in the $\Delta f_{oob}$ immediately outside any of the supported uplink operating band .
For a BS operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768 - 797 MHz. | | | | | | | +| NOTE 3: 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 or E-UTRA TDD or NR TDD with E-UTRA FDD or NR FDD on adjacent frequencies with closely spaced antennas. However, there are certain site-engineering solutions that can be used. These techniques are addressed in 3GPP TR 25.942 [12]. | | | | | | | +| NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805 - 1850 MHz. | | | | | | | +| NOTE 5: For an AAS BS operating in band 11, 21, or 74 the requirement for co-location with Band 32 applies for interfering signal within the frequency range 1475.9 - 1495.9 MHz. | | | | | | | + +## 10.7 OTA Receiver spurious emissions + +### 10.7.1 General + +The receiver spurious emission requirement is the power of the emissions radiated from the antenna array from a receiver unit. For an *OTA AAS BS* operating in FDD, OTA RX spurious emissions requirement do not apply as they are superseded by the OTA TX spurious emissions requirement. This is due to the fact that TX and RX spurious emissions cannot be distinguished in OTA domain. + +NOTE: The OTA receiver spurious emission requirement applicability for the AAS BS with the RX-only capabilities is not covered by the present release of this specification. + +For an *OTA AAS BS* operating in TDD, the OTA receiver spurious emissions requirement applies during the *transmitter OFF period* only. + +For RX only *multi-band RIB*, the RX spurious emissions requirements are subject to exclusion zones in each supported operating band. + +### 10.7.2 Minimum requirement for MSR operation + +#### 10.7.2.1 General minimum requirement + +There are no OTA receiver spurious emissions requirements for UTRA FDD. + +For E-UTRA, the minimum requirement is specified in subclause 10.7.4 + +For NR, the minimum requirement is the same as that specified for *BS type 1-O* in TS 38.104 [28] in subclause 10.7.2 + +### 10.7.3 Minimum requirement for single RAT UTRA operation + +There are no OTA receiver spurious emissions requirements for single RAT UTRA FDD. + +### 10.7.4 Minimum requirement for single RAT E-UTRA operation + +The TRP of any spurious emission shall not exceed the limits in table 10.7.4-1: + +**Table 10.7.4-1: General spurious emission minimum requirement** + +| Frequency range | Maximum level
(Note 2, Note 3) | Measurement
bandwidth | NOTE | +|--------------------------------------------------------------------------------------------------|-----------------------------------|--------------------------|------------------------| +| 30MHz - 1 GHz | -36 + X dBm | 100 kHz | Note 4 | +| 1 GHz - 12.75 GHz | -30 + X dBm | 1 MHz | Note 4, Note 5 | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -30 + X dBm | 1 MHz | Note 5, Note 5, Note 6 | + +NOTE 1: The frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS transmitter *operating band* to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS transmitter *operating band* may be excluded from the requirement. $\Delta f_{\text{OBUE}}$ is defined in clause 6.6.1. For a *multiband RIB*, the exclusion applies for all supported operating bands. + +NOTE 2: X = 9 dB, unless stated differently in regional regulation. + +NOTE 3: Additional limits may apply regionally. + +NOTE 4: Measurement bandwidths as in ITU-R SM.329 [x], s4.1. + +NOTE 5: Upper frequency as in ITU-R SM.329 [x], s2.5 table 1. + +NOTE 6: This spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the UL *operating band* is reaching beyond 12.75 GHz. + +In addition to the requirements in table 10.7.4-1, the power of any spurious emission shall not exceed the levels specified for Protection of the E-UTRA FDD BS receiver of own or different BS in subclause 9.7.6.4.2 and for Co-existence with other systems in the same geographical area in subclause 9.7.6.4.3. In addition, the co-existence requirements for co-located base stations specified in subclause 9.7.6.4.4 may also be applied. + +## 10.8 OTA Receiver intermodulation + +### 10.8.1 General + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver unit to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. + +The requirement applies at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction, and: + +- when the wanted signal is based on $\text{EIS}_{\text{REFSENS}}$ : the AoA of the incident wave of a received signal and the interfering signal are within the OTA $\text{REFSENS}$ *RoAoA*. +- when the wanted signal is based on $\text{EIS}_{\text{minSENS}}$ : the AoA of the incident wave of a received signal and the interfering signal are within the *minSENS* *RoAoA*. + +The wanted and interfering signals apply to each supported polarization, under the assumption of *polarization match*. + +### 10.8.2 Minimum requirement for MSR operation + +#### 10.8.2.1 General intermodulation minimum requirement + +Interfering signals shall be a CW signal and an E-UTRA or UTRA signal as specified in 3GPP TS 37.104 [9], annex A. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least twice as wide as the UTRA/E-UTRA interfering signal centre frequency offset from the *Base Station RF Bandwidth edge*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted signal at the assigned channel frequency and two interfering signals at the RIB, using the parameters in tables 10.8.2.1-1 and 10.8.2.1-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any NR carrier, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channel defined for *BS type 1-O* in TS 38.104 [28], subclause 10.3.2 + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +**Table 10.8.2.1-1: General intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE 1) | Type of interfering signals | +|-------------------|-------------------------------------------------|----------------------------------------------------------|-----------------------------| +| Wide Area BS | $-48 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 6) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 2, 5) | See table 10.8.2.1-2 | +| | $-48 + y - \Delta_{\text{minSENS}}$ (NOTE 6) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 2, 5) | | +| Medium Range BS | $-44 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 6) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 3, 5) | | +| | $-44 + y - \Delta_{\text{minSENS}}$ (NOTE 6) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 3, 5) | | +| Local Area BS | $-38 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 6) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 4, 5) | | +| | $-38 + y - \Delta_{\text{minSENS}}$ (NOTE 6) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 4, 5) | | + +NOTE 1: $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{minSENS}}$ depend on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +NOTE 2: For WA BS supporting UTRA, "x" is equal to 6 in case of NR or E-UTRA or UTRA wanted signals. + +NOTE 3: For MR BS supporting UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA wanted signal. + +NOTE 4: For LA BS supporting UTRA, "x" is equal to 12 in case of E-UTRA wanted signals, 6 in case of NR or UTRA wanted signal. + +NOTE 5: For a BS and not supporting UTRA, x is equal to 6 for all BS classes if NR is supported, otherwise x is equal to 6 for WA BS or 9 for MR or 12 for LA BS if NR is not supported. + +NOTE 6: For a BS that supports NR but not UTRA; "y" is equal to -4 for the WA BS class, -3 for the MR BS class and -6 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. + +**Table 10.8.2.1-2: Interfering signals for intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge | Interfering signal centre frequency offset from the Base Station RF Bandwidth edge [MHz] | Type of interfering signal | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------------------| +| E-UTRA 1.4 MHz | ±2,0 (BC1 and BC3) /
±2,1 (BC2) | CW | +| | ±4,9 | 1,4 MHz E-UTRA signal | +| E-UTRA 3 MHz | ±4,4 (BC1 and BC3) /
±4,5 (BC2) | CW | +| | ±10,5 | 3 MHz E-UTRA signal | +| UTRA FDD and E-UTRA 5 MHz | ±7,5 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| E-UTRA 10 MHz | ±7,375 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| E-UTRA 15 MHz | ±7,25 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| E-UTRA 20 MHz | ±7,125 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| GSM/EDGE | ±7,575 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| 1,28 Mcps UTRA TDD | ±2,3 (BC3) | CW | +| | ±5,6 (BC3) | 1,28 Mcps UTRA TDD signal | +| NR 5 MHz | ±7,5 | CW | +| | ±17,5 | 5MHz E-UTRA signal | +| NR 10 MHz | ±7,45 | CW | +| | ±17,5 | 5MHz E-UTRA signal | +| NR 15 MHz | ±7,43 | CW | +| | ±17,5 | 5MHz E-UTRA signal | +| NR 20 MHz | ±7,38 | CW | +| | ±17,5 | 5MHz E-UTRA signal | +| NR 25 MHz | ±7,45 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 30 MHz | ±7,43 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 35 MHz | ±7,44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 40 MHz | ±7,45 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 45 MHz | ±7,37 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 50 MHz | ±7,35 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 60 MHz | ±7,49 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 70 MHz | ±7,42 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 80 MHz | ±7,44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 90 MHz | ±25 | CW | +| | ±7,43 | 20MHz E-UTRA signal | +| NR 100 MHz | ±7,45 | CW | +| | ±25 | 20MHz E-UTRA signal | + +## 10.8.2.2 General narrowband intermodulation minimum requirement + +Interfering signals shall be a CW signal and an E-UTRA 1RB signal as specified in 3GPP TS 37.104 [9], annex A. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIB supporting operation in *non-contiguous spectrum* within each supported operating band, the requirement applies in addition inside any *sub-block gap* in case the *sub-block gap* is at least as wide as the *channel bandwidth* of the E-UTRA interfering signal in table 10.8.2.2-2. The interfering signal offset is defined relative to the *sub-block* edges inside the gap. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least as wide as the E-UTRA interfering signal in table 10.8.2.2-2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted signal at the assigned channel frequency and two interfering signals at the RIB, using the parameters in tables 10.8.2.2-1 and 10.8.2.2-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in 3GPP TS 36.104 [8], subclause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in 3GPP TS 25.104 [6], subclause 7.2.1. +- For any NR carrier, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channel defined in TS 38.104 [17], subclause 7.2. + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +**Table 10.8.2.2-1: General narrowband intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Type of interfering signals | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------|-----------------------------| +| Wide Area BS | $-52 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | See table 10.8.2.2-2 | +| | $-52 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | +| Medium Range BS | $-47 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | +| | $-47 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | +| Local Area BS | $-44 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | +| | $-44 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | +| NOTE $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{minSENS}}$ depend on the RAT, the BS class and on the channel bandwidth , see subclauses 10.3 and 10.2. | | | | + +**Table 10.8.2.2-2: Interfering signals for narrowband intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge or edge of the sub-block | CW or 1RB interfering signal centre frequency offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap [kHz] | Type of interfering signal | +|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| E-UTRA 1.4 MHz | ±260 (BC1 and BC3) /
±270 (BC2) | CW | +| | ±970 (BC1 and BC3) /
±790 (BC2) | 1,4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 3 MHz | ±260 (BC1 and BC3) /
±270 (BC2) | CW | +| | ±960 (BC1 and BC3) /
±780 (BC2) | 3,0 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 5 MHz | ±360 | CW | +| | ±1 060 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 10 MHz (NOTE 2) | ±325 | CW | +| | ±1 240 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 15 MHz (NOTE 2) | ±380 | CW | +| | ±1 600 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 20 MHz (NOTE 2) | ±345 | CW | +| | ±1 780 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| UTRA FDD | ±345 (BC1 and BC2) | CW | +| | ±1 780 (BC1 and BC2) | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| GSM/EDGE | ±340 | CW | +| | ±880 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| 1,28 Mcps UTRA TDD | ±190 (BC3) | CW | +| | ±970 (BC3) | 1,4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| NR 5 MHz | ±360 | CW | +| | ±1420 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 10 MHz | ±325 | CW | +| | ±1780 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 15 MHz (Note 2) | ±380 | CW | +| | ±1600 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 20 MHz (Note 2) | ±345 | CW | +| | ±1780 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 25 MHz (Note 2) | ±325 | CW | +| | ±1990 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 30 MHz (Note 2) | ±320 | CW | +| | ±1990 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 35 MHz (Note 2) | ±355 | CW | +| | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 40 MHz (Note 2) | ±310 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 45 MHz (Note 2) | ±365 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 50 MHz (Note 2) | ±330 | CW | +| | ±3250 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 60 MHz (Note 2) | ±350 | CW | +| | ±3790 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 70 MHz (Note 2) | ±400 | CW | +| | ±4870 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 80 MHz (Note 2) | ±390 | CW | +| | ±4870 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 90 MHz (Note 2) | ±340 | CW | +| | ±5770 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 100 MHz (Note 2) | ±340 | CW | +| | ±5770 | E-UTRA signal, 1 RB (NOTE 1) | + +NOTE 1: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the Base Station RF Bandwidth edge. + +NOTE 2: This requirement shall apply only for an E-UTRA FRC A1-3 mapped to the + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge or edge of the sub-block | CW or 1RB interfering signal centre frequency offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap [kHz] | Type of interfering signal | +|----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| frequency range at the channel edge adjacent to the interfering signals | | | + +### 10.8.3 Minimum requirement for single RAT UTRA operation + +The static reference performance as specified in subclause 10.3 and 10.2 shall be met for a Wide Area BS when the signals in table 10.8.3-1 and table 10.8.3-2 are at the RIB. + +The static reference performance as specified in subclause 10.3 and 10.2 shall be met for a Medium range BS when the signals in table 10.8.3-3 and table 10.8.3-4 are at the RIB. + +The static reference performance as specified in subclause 10.3 and 10.2 shall be met for a Local Area BS when the signals in table 10.8.3-5 and table 10.8.3-6 are at the RIB. + +For RIB supporting operation in *non-contiguous spectrum* within each supported operating band, the requirement applies in addition inside any *sub-block gap* in case the *sub-block gap* is at least 6.8MHz. The CW interfering signal offset is defined relative to the lower/upper *sub-block* edge inside the *sub-block gap* and is equal to -1MHz/+1MHz, respectively. The GMSK modulated interfering signal offset is defined relative to the lower/upper *sub-block* edge inside the *sub-block gap* and is equal to -3.4MHz/+3.4MHz, respectively. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least 6.8MHz. The CW interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth* edges inside the *Inter RF Bandwidth gap* and is equal to -1MHz/+1MHz, respectively. The GMSK modulated interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth* edges inside the *Inter RF Bandwidth gap* and is equal to -3.4MHz/+3.4MHz, respectively. + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +**Table 10.8.3-1: Intermodulation performance requirement (Wide Area BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signals | +|---------------------------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------|--------------|-----------------------------| +| All bands | - 48 - $\Delta_{\text{OTAREFSENS}}$ | - 115 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 10$ MHz | CW signal | +| | -48 - $\Delta_{\text{minSENS}}$ | -115 - $\Delta_{\text{minSENS}}$ | | | +| | - 48 - $\Delta_{\text{OTAREFSENS}}$ | - 115 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 20$ MHz | WCDMA signal (NOTE) | +| | -48 - $\Delta_{\text{minSENS}}$ | -115 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: The characteristics of the WCDMA interference signal are specified in 3GPP TS 25.104 [6] Annex C. | | | | | + +**Table 10.8.3-2: Narrowband intermodulation performance requirement (Wide Area BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signals | +|----------------------------------------------------|-----------------------------------------|---------------------------------------|---------------|-----------------------------| +| II, III, IV, V, VIII, X, XII, XIII, XIV, XXV, XXVI | - 47 - $\Delta_{\text{OTAREFSENS}}$ | - 115 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 3.5$ MHz | CW signal | +| | -47 - $\Delta_{\text{minSENS}}$ | -115 - $\Delta_{\text{minSENS}}$ | | | +| | - 47 - $\Delta_{\text{OTAREFSENS}}$ | - 115 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 5.9$ MHz | GMSK modulated (NOTE) | +| | -47 - $\Delta_{\text{minSENS}}$ | -115 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: GMSK as defined in TS45.004 [26] | | | | | + +**Table 10.8.3-3: Intermodulation performance requirement (Medium Range BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signals | +|---------------------------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------|--------------|-----------------------------| +| All bands | - 44 - $\Delta_{\text{OTAREFSENS}}$ | - 105 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 10$ MHz | CW signal | +| | -44 - $\Delta_{\text{minSENS}}$ | -105 - $\Delta_{\text{minSENS}}$ | | | +| | - 44 - $\Delta_{\text{OTAREFSENS}}$ | - 105 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 20$ MHz | WCDMA signal (NOTE) | +| | -44 - $\Delta_{\text{minSENS}}$ | -105 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: The characteristics of the WCDMA interference signal are specified in 3GPP TS 25.104 [6] Annex C. | | | | | + +**Table 10.8.3-4: Narrowband intermodulation performance requirement (Medium Range BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signals | +|----------------------------------------------------|-----------------------------------------|---------------------------------------|---------------|-----------------------------| +| II, III, IV, V, VIII, X, XII, XIII, XIV, XXV, XXVI | - 43 - $\Delta_{\text{OTAREFSENS}}$ | - 105 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 3.5$ MHz | CW signal | +| | -43 - $\Delta_{\text{minSENS}}$ | -105 - $\Delta_{\text{minSENS}}$ | | | +| | - 43 - $\Delta_{\text{OTAREFSENS}}$ | - 105 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 5.9$ MHz | GMSK modulated (NOTE) | +| | -43 - $\Delta_{\text{minSENS}}$ | -105 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: GMSK as defined in TS45.004 [26] | | | | | + +**Table 10.8.3-5: Intermodulation performance requirement (Local Area BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signals | +|---------------------------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------|--------------|-----------------------------| +| All bands | - 38 - $\Delta_{\text{OTAREFSENS}}$ | - 101 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 10$ MHz | CW signal | +| | -38 - $\Delta_{\text{minSENS}}$ | -101 - $\Delta_{\text{minSENS}}$ | | | +| | - 38 - $\Delta_{\text{OTAREFSENS}}$ | - 101 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 20$ MHz | WCDMA signal (NOTE) | +| | -38 - $\Delta_{\text{minSENS}}$ | -101 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: The characteristics of the WCDMA interference signal are specified in 3GPP TS 25.104 [6] Annex C. | | | | | + +**Table 10.8.3-6: Narrowband intermodulation performance requirement (Local Area BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signal | +|----------------------------------------------------|-----------------------------------------|---------------------------------------|---------------|----------------------------| +| II, III, IV, V, VIII, X, XII, XIII, XIV, XXV, XXVI | - 38 - $\Delta_{\text{OTAREFSENS}}$ | - 101 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 3.5$ MHz | CW signal | +| | -38 - $\Delta_{\text{minSENS}}$ | -101 - $\Delta_{\text{minSENS}}$ | | | +| | - 38 - $\Delta_{\text{OTAREFSENS}}$ | - 101 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 5.9$ MHz | GMSK modulated (NOTE) | +| | -38 - $\Delta_{\text{minSENS}}$ | -101 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: GMSK as defined in TS45.004 [26] | | | | | + +## 10.8.4 Minimum requirement for single RAT E- UTRA operation + +For E-UTRA, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel, with a wanted signal at the assigned channel frequency and two interfering signals at the RIB, with the conditions specified in tables 10.8.4-1 and 10.8.4-2 for intermodulation performance and in tables 10.8.4-3, 10.8.4-4, and 10.8.4-5 for narrowband intermodulation performance. Narrowband intermodulation requirements are not applied for Band 46 nor for Band 49. The reference measurement channel for the wanted signal is identified in table 10.8.4-1 to 6 for each *channel bandwidth* and further specified in 3GPP TS 36.104 [8] Annex A. + +The receiver intermodulation requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth edges*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIB supporting operation in *non-contiguous spectrum* within each supported operating band, the requirement applies in addition inside any *sub-block gap* in case the *sub-block gap* is at least as wide as the *channel bandwidth* of the + +E-UTRA interfering signal in table 10.8.4-3. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the intermodulation requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least as wide as the E-UTRA interfering signal centre frequency offset from the *Base Station RF Bandwidth edge*. + +For *multi-band RIBs*, the narrowband intermodulation requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least as wide as the E-UTRA interfering signal in tables 10.8.4-3, 10.8.4-4 and 10.8.4-5. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +**Table 10.8.4-1: Intermodulation performance requirement for E-UTRA** + +| BS type | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] (NOTE) | Type of interfering signal | +|-----------------|---------------------------------------------|--------------------------------------------|----------------------------| +| Wide Area BS | $\text{EIS}_{\text{REFSENS}} + 6\text{dB}$ | $-52 - \Delta_{\text{OTAREFSENS}}$ | See table 10.8.4-2 | +| | $\text{EIS}_{\text{minSENS}} + 6\text{ dB}$ | $-52 - \Delta_{\text{minSENS}}$ | | +| Medium Range BS | $\text{EIS}_{\text{REFSENS}} + 6\text{dB}$ | $-47 - \Delta_{\text{OTAREFSENS}}$ | | +| | $\text{EIS}_{\text{minSENS}} + 6\text{ dB}$ | $-47 - \Delta_{\text{minSENS}}$ | | +| Local Area BS | $\text{EIS}_{\text{REFSENS}} + 6\text{dB}$ | $-44 - \Delta_{\text{OTAREFSENS}}$ | | +| | $\text{EIS}_{\text{minSENS}} + 6\text{ dB}$ | $-44 - \Delta_{\text{minSENS}}$ | | + +NOTE: $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{minSENS}}$ depend on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +**Table 10.8.4-2: Interfering signal for Intermodulation performance requirement for E-UTRA** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Interfering signal centre frequency offset from the lower/upper Base Station RF Bandwidth edge [MHz] | Type of interfering signal | +|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------| +| 3 | $\pm 4.5$ | CW | +| | $\pm 10.5$ | 3 MHz E-UTRA signal (NOTE 3) | +| 5 | $\pm 7.5$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | +| 10 | $\pm 7.375$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | +| 15 | $\pm 7.25$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | +| 20 | $\pm 7.125$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal (NOTE 1) | + +NOTE 1: This type of interfering signal is not applied for Band 46 nor for Band 49. +NOTE 2: Void +NOTE 3: 3 MHz *channel bandwidth* is not applicable to guard band operation. + +**Table 10.8.4-3: Narrowband intermodulation performance requirement for Wide Area BS for E-UTRA** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering RB | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| | | | centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [kHz] | | +| 1.4 | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±790 | 1.4 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 3 | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±780 | 3.0 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 5 | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±360 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±1060 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 10
(NOTE 3) | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±325 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±1240 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 15
(NOTE 3) | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±380 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±1600 | 5MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 20
(NOTE 3) | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±345 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ OTAREFSENS | ±1780 | 5MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | + +NOTE 1: EISREFSENS and EISminSENS depend on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +NOTE 2: Interfering signal consisting of one resource block positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the lower/upper *Base Station RF Bandwidth edge*. + +NOTE 3: This requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals + +**Table 7.8.1-4: Narrowband intermodulation performance requirement for Local Area BS for E-UTRA** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [kHz] | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| 1.4 | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±790 | 1.4 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 3 | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±780 | 3.0 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 5 | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±360 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±1060 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 10
(NOTE 3) | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±325 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±1240 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 15
(NOTE 3) | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±380 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±1600 | 5MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 20
(NOTE 3) | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±345 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±1780 | 5MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | + +NOTE 1: EISREFSENS and EISminSENS depend on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +NOTE 2: Interfering signal consisting of one resource block positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the lower/upper Base Station RF Bandwidth edge. + +NOTE 3: This requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals + +**Table 10.8.4-5: Narrowband intermodulation performance requirement for Medium Range BS for E-UTRA** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering RB | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| | | | centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [kHz] | | +| 1.4 | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±790 | 1.4 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 3 | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±780 | 3.0 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 5 | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±360 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±1060 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 10
(NOTE 3) | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±325 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±1240 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 15
(NOTE 3) | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±380 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±1600 | 5MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 20
(NOTE 3) | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±345 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ OTAREFSENS | ±1780 | 5MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | + +NOTE 1: EISREFSENS and EISminSENS depend on the RAT, the BS class and on the *channel bandwidth*, see subclauses 10.3 and 10.2. + +NOTE 2: Interfering signal consisting of one resource block positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the lower/upper *Base Station RF Bandwidth edge*. + +NOTE 3: This requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals + +## 10.9 OTA In-channel selectivity + +### 10.9.1 General + +In-channel selectivity (ICS) is a measure of the receiver unit ability to receive a wanted signal at its assigned resource block locations in the presence of an interfering signal received at a larger power spectral density. In this condition a throughput requirement shall be met for a specified reference measurement channel. + +The requirement applies at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction and are within the *minSENS RoAoA*. + +The wanted and interfering signals apply to each supported polarization, under the assumption of *polarization match*. + +### 10.9.2 Minimum requirement for MSR operation + +For E-UTRA, the minimum requirement for in-channel selectivity is specified in subclause 10.9.4. + +For NR, the minimum requirement for in channel selectivity is the same as that specified for *BS type 1-O* in 3GPP TS 38.104 [28] in subclause 10.9.2 + +This requirement is not applicable for UTRA operation. + +### 10.9.3 Minimum requirement for single RAT UTRA operation + +This requirement is not applicable for UTRA BS. + +### 10.9.4 Minimum requirement for single RAT E- UTRA operation + +For E-UTRA, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel as specified in 3GPP 36.104 [8] Annex A with parameters specified in table 10.9.4-1 for Wide Area BS, in table 10.9.4-2 for Local Area BS and in table 10.9.4-3 for Medium Range BS. + +The OTA levels are applied referenced to $\Delta_{\min\text{SENS}}$ . + +**Table 10.9.4-1 Wide Area BS in-channel selectivity for E-UTRA** + +| E-UTRA channel bandwidth [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] | Type of interfering signal | +|--------------------------------|------------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------| +| 1.4 | A1-4 in 3GPP 36.104 [8] Annex A.1 | $-106.9 - \Delta_{\min\text{SENS}}$ | $-87 - \Delta_{\min\text{SENS}}$ | 1.4 MHz E-UTRA signal, 3 RBs | +| 3 | A1-5 in 3GPP 36.104 [8] Annex A.1 | $-102.1 - \Delta_{\min\text{SENS}}$ | $-84 - \Delta_{\min\text{SENS}}$ | 3 MHz E-UTRA signal, 6 RBs | +| 5 | A1-2 in 3GPP 36.104 [8] Annex A.1 | $-100.0 - \Delta_{\min\text{SENS}}$ | $-81 - \Delta_{\min\text{SENS}}$ | 5 MHz E-UTRA signal, 10 RBs | +| 10 | A1-3 in 3GPP 36.104 [8] Annex A.1 | $-98.5 - \Delta_{\min\text{SENS}}$ | $-77 - \Delta_{\min\text{SENS}}$ | 10 MHz E-UTRA signal, 25 RBs | +| 15 | A1-3 in 3GPP 36.104 [8] Annex A.1 (NOTE) | $-98.5 - \Delta_{\min\text{SENS}}$ | $-77 - \Delta_{\min\text{SENS}}$ | 15 MHz E-UTRA signal, 25 RBs (NOTE) | +| 20 | A1-3 in 3GPP 36.104 [8] Annex A.1 (NOTE) | $-98.5 - \Delta_{\min\text{SENS}}$ | $-77 - \Delta_{\min\text{SENS}}$ | 20 MHz E-UTRA signal, 25 RBs (NOTE) | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ . + +**Table 10.9.4-2 Local Area BS in-channel selectivity for E-UTRA** + +| E-UTRA channel bandwidth [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] | Type of interfering signal | +|--------------------------------|--------------------------------------------|------------------------------------|-------------------------------------|---------------------------------------| +| 1.4 | A1-4 in 3GPP 36.104 [8] Annex A.1 | $-98.9 - \Delta_{\min\text{SENS}}$ | $-79 - \Delta_{\min\text{SENS}}$ | 1.4 MHz E-UTRA signal, 3 RBs | +| 3 | A1-5 in 3GPP 36.104 [8] Annex A.1 | $-94.1 - \Delta_{\min\text{SENS}}$ | $-76 - \Delta_{\min\text{SENS}}$ | 3 MHz E-UTRA signal, 6 RBs | +| 5 | A1-2 in 3GPP 36.104 [8] Annex A.1 | $-92.0 - \Delta_{\min\text{SENS}}$ | $-73 - \Delta_{\min\text{SENS}}$ | 5 MHz E-UTRA signal, 10 RBs | +| 10 | A1-3 in 3GPP 36.104 [8] Annex A.1 (NOTE 3) | $-90.5 - \Delta_{\min\text{SENS}}$ | $-69 - \Delta_{\min\text{SENS}}$ | 10 MHz E-UTRA signal, 25 RBs (NOTE 3) | +| 15 | A1-3 in 3GPP 36.104 [8] Annex A.1 (NOTE 1) | $-90.5 - \Delta_{\min\text{SENS}}$ | $-69 - \Delta_{\min\text{SENS}}$ | 15 MHz E-UTRA signal, 25 RBs (NOTE 1) | +| 20 | A1-3 in 3GPP 36.104 [8] Annex A.1 (NOTE 1) | $-90.5 - \Delta_{\min\text{SENS}}$ | $-69 - \Delta_{\min\text{SENS}}$ | 20 MHz E-UTRA signal, 25 RBs (NOTE 1) | + +NOTE 1: Wanted and interfering signal are placed adjacently around $F_c$ , this reference measurement channel and interfering signal are not applied for Band 46 nor for Band 49. + +NOTE 2: Void + +NOTE 3: This reference measurement channel and interfering signal are not applied for Band 46 nor for Band 49. + +**Table 10.9.4-3 Medium Range BS in-channel selectivity for E-UTRA** + +| E-UTRA channel bandwidth [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] | Type of interfering signal | +|--------------------------------|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| 1.4 | A1-4 in 3GPP 36.104 [8] Annex A.1 | $-101.9 - \Delta_{\min\text{SENS}}$ | $-82 - \Delta_{\min\text{SENS}}$ | 1.4 MHz E-UTRA signal, 3 RBs | +| 3 | A1-5 in 3GPP 36.104 [8] Annex A.1 | $-97.1 - \Delta_{\min\text{SENS}}$ | $-79 - \Delta_{\min\text{SENS}}$ | 3 MHz E-UTRA signal, 6 RBs | +| 5 | A1-2 in 3GPP 36.104 [8] Annex A.1 | $-95.0 - \Delta_{\min\text{SENS}}$ | $-76 - \Delta_{\min\text{SENS}}$ | 5 MHz E-UTRA signal, 10 RBs | +| 10 | A1-3 in 3GPP 36.104 [8] Annex A.1 (NOTE 3)
A1-8 in 3GPP 36.104 [8] Annex A.1 (NOTE 2) | $-93.5 - \Delta_{\min\text{SENS}}$
$-96.2 - \Delta_{\min\text{SENS}}$ | $-72 - \Delta_{\min\text{SENS}}$
$-74.8 - \Delta_{\min\text{SENS}}$ | 10 MHz E-UTRA signal, 25 RBs (NOTE 3)
10 MHz E-UTRA interlace signal, 10 RBs (NOTE 2) | +| 15 | A1-3 in 3GPP 36.104 [8] Annex A.1 (NOTE 1) | $-93.5 - \Delta_{\min\text{SENS}}$ | $-72 - \Delta_{\min\text{SENS}}$ | 15 MHz E-UTRA signal, 25 RBs (NOTE 1) | +| 20 | A1-3 in 3GPP 36.104 [8] Annex A.1 (NOTE 1)
A1-9 in 3GPP 36.104 [8] Annex A.1 (NOTE 2) | $-93.5 - \Delta_{\min\text{SENS}}$
$-96.2 - \Delta_{\min\text{SENS}}$ | $-72 - \Delta_{\min\text{SENS}}$
$-74.8 - \Delta_{\min\text{SENS}}$ | 20 MHz E-UTRA signal, 25 RBs (NOTE 1)
20 MHz E-UTRA interlace signal, 10 RBs (NOTE 2) | + +NOTE 1: Wanted and interfering signal are placed adjacently around $F_c$ , this reference measurement channel and interfering signal are not applied for Band 46. + +NOTE 2: Wanted and interfering signal interlaces are mirrored around $F_c$ , this reference measurement channel and interfering signal are only applied for Band 46. + +NOTE 3: This reference measurement channel and interfering signal are not applied for Band 46. + +## 11 Radiated performance requirements + +### 11.1 General + +#### 11.1.1 OTA demodulation branches + +OTA performance requirements are only specified for up to 2 *demodulation branches*. + +If the OTA AAS BS uses polarization diversity and has the ability to maintain isolation between the signals for each of the *demodulation branches*, then OTA performance requirements can be tested for up to two *demodulation branches*. When tested for two *demodulation branches*, each demodulation branch maps to one polarization. + +If the OTA AAS BS does not use polarization diversity then OTA performance requirements can only be tested for a single *demodulation branch*. + +#### 11.1.2 UTRA operation + +Performance requirements for *single RAT UTRA operation* in FDD are specified for the measurement channels defined in 3GPP TS 25.104 [2]. The requirements only apply to those measurement channels that are supported by AAS BS. For FRC8 in 3GPP TS 25.104 [2] the non E-DPCCH boosting and E-DPCCH boosting requirement only apply for the option supported by the AAS BS. The performance requirements for the high speed train scenarios defined in 3GPP TS 25.104 [2] are optional. + +Unless stated otherwise, performance requirements apply for a single cell only. Performance requirements for an AAS BS supporting UTRA FDD DC-HSUPA or DB-DC-HSUPA and UTRA TDD MC\_HSUPA are defined in terms of single carrier requirements. For FDD operation the requirements in clause 11 shall be met with the transmitter unit(s) associated with the RIB in the operating band ON. + +NOTE: In normal operating conditions the *transceiver units* in UTRA FDD operation are configured to transmit and receive at the same time. The transmitter unit(s) associated with the RIB may be OFF for some of the tests as specified in 3GPP TS 37.145 [13]. + +In the referred UTRA specifications and in this clause, the term BS with RX diversity refers to performance requirements for two *demodulation branches*, and BS without RX diversity refers to performance requirements for one *demodulation branch*. + +For AAS BS with RX diversity, only the BS performance requirements with RX diversity apply, the required $E_b/N_0$ for UTRA FDD and $\hat{I}_{or}/I_{oc}$ for UTRA TDD shall be applied separately for each *demodulation branch*. + +For AAS BS without RX diversity, only the BS performance requirements without RX diversity apply. The required $E_b/N_0$ for UTRA FDD and $\hat{I}_{or}/I_{oc}$ for UTRA TDD shall be applied for each AAS BS *demodulation branch*. + +The $E_b/N_0$ used for UTRA FDD is defined as: + +Where: + +is the received total energy of DPDCH, DPCCH, S-DPCCH, HS-DPCCH, E-DPDCH, S-E-DPDCH, E-DPCCH and S-E-DPCCH per PN chip per *demodulation branch* from all branches + +is the total one-sided noise power spectral density due to all noise sources + +is the number of chips per frame + +is the number of information bits in DTCH excluding CRC bits per frame + +**Table 11.1.2-1: Summary of AAS BS performance targets for single RAT UTRA operation** + +| Physical channel | Measurement channel | Static | Multi-path Case 1 | Multi-path Case 2 | Multi-path Case 3 | Moving | Birth / Death | High Speed Train | +|------------------|---------------------|------------------------------------------|------------------------------------------|------------------------------------------|-------------------------------------------------------------|------------------------------------------|------------------------------------------|-----------------------| +| | | Performance metric | | | | | | | +| DCH | 12.2 kbps | BLER<10 -2 | BLER<10 -2 | 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 | 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: In case of multiple BLER level thresholds listed for single requirement and measurement channel combination, those BLER level values are reflected by set multiple requirements in 3GPP TS 25.104 [2]. + +### 11.1.3 E-UTRA operation + +Performance requirements for the AAS BS are specified for the fixed reference channels (FRC) and propagation conditions defined in 3GPP TS 36.104 [8] annex A and annex B, respectively. The requirements only apply to those FRCs that are supported by the AAS BS. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for an AAS BS E-UTRA supporting *carrier aggregation* are defined in terms of single carrier requirements. For FDD operation the requirements shall be met with the transmitter unit(s) associated with the RIB in the operating band ON. + +NOTE: In normal operating conditions the *transceiver units* in FDD operation are configured to transmit and receive at the same time. The transmitter unit(s) associated with the RIB may be OFF for some of the tests as specified in 3GPP TS 37.145 [13]. + +In the referred E-UTRA specification, the term "RX antennas" refers to *demodulation branches* (and not physical antennas). + +The SNR used in this clause is specified based on a single carrier and defined as: + +$$SNR = S / N$$ + +Where: + +$S$ is the total signal energy in the subframe. + +$N$ is the noise energy in a bandwidth corresponding to the *transmission bandwidth* over the duration of a subframe. + +For enhanced performance requirements type A, the SINR used in this clause is specified based on a single carrier and defined as: + +$$SINR = S/N'$$ + +Where: + +$S$ is the total signal energy in the subframe. + +$N'$ is the summation of the received energy of the strongest interferers explicitly defined in a test procedure plus the white noise energy $N$ , in a bandwidth corresponding to the *transmission bandwidth* over the duration of a subframe. The respective energy of each interferer relative to $N'$ is defined by its associated DIP value. + +## 11.2 Minimum requirements for MSR operation + +For *single RAT UTRA operation*, minimum requirements for demodulation performance are specified in subclause 8.3. + +For *single RAT E-UTRA operation*, minimum requirements for demodulation performance are specified in subclause 8.4. + +## 11.3 Minimum requirements for UTRA operation + +The *single RAT UTRA operation* in FDD shall fulfil all mandatory BS demodulation performance requirements specified in subclauses 8.2 to 8.12 of 3GPP TS 25.104 [6]. + +In the referred UTRA specifications, the term BS with RX diversity refers to performance requirements for two *demodulation branches*, and BS without RX diversity refers to performance requirements for one *demodulation branch*. + +## 11.4 Minimum requirements for E-UTRA operation + +The *single RAT E-UTRA operation* shall fulfil all mandatory BS demodulation performance requirements specified in subclauses 8.2 - 8.4 (for PUSCH, PUCCH and PRACH) and 8.6 – 8.7 (for subslot-PUSCH and sPUCCH) of TS 36.104 [8]. + +In the referred E-UTRA specification, the term "RX antennas" refers to *demodulation branches* (i.e. not physical antennas). + +--- + +## Annex A (normative): Environmental requirements for the BS equipment + +The AAS BS equipment shall fulfil all the requirements in the full range of environmental conditions for the relevant environmental class. The environmental conditions and class shall be from the relevant IEC specifications or the corresponding ETSI specifications listed below. + +IEC specifications for environmental requirements: + +IEC 60721-3-3 [21]: "Stationary use at weather protected locations". + +IEC 60721-3-4 [22]: "Stationary use at non weather protected locations". + +ETSI specifications for environmental requirements: + +ETSI EN 300 019-1-3 [23]: "Stationary use at weather protected locations". + +ETSI EN 300 019-1-4 [24]: "Stationary use at non weather protected locations". + +Normally it should be sufficient for all tests to be conducted using normal test conditions except where otherwise stated. For guidance on the use of test conditions to be used in order to show compliance refer to TS 37.145-1 [29] or TS 37.145-2 [30]. + +--- + +## Annex B (Informative): Calculation of EIRP based on fixed assumption of passive antenna gain + +### B.1 Calculation of EIRP based on fixed assumption of passive antenna gain + +Some regional requirements are defined per effective isotropic radiated power (EIRP), which is a combination of the transmitted power (or in some cases spectral density) and the effective antenna gain which is a site specific condition. Such requirements may be applied per antenna, per cell, or per base station. It shall be noted that the definition of BS or cell may differ between regulations. Where the regulator prescribes a method for EIRP calculation, that method supersedes the proposed assessment in this annex. + +The regulations set an EIRP limit considering a passive antenna BS. Although the gain of passive antennas may vary somewhat, the gain variation is in the order of a few dBs. The instantaneous gain of an AAS BS may be much larger. However AAS unwanted emissions requirements are defined as TRP, since TRP impacts co-existence properties. + +In order to relate the EIRP values in the specifications to TRP, a fixed assumption has been made on the gain of a typical passive BS antenna. + +Thus, the maximum TRP can be estimated using the following formulas: + +TRP limit per antenna: $P_{\text{TRP, antenna}} = P_{\text{EIRP}} - G_{\text{Ant}}$ + +E-UTRA TRP limit per cell or per BS: $P_{\text{TRP}} = P_{\text{TRP, antenna}} + 9\text{dB}$ + +UTRA TRP limit per cell or per BS: $P_{\text{TRP}} = P_{\text{TRP, antenna}} + 6\text{dB}$ + +It is noted that the AAS architecture assumes that a BS subject to OTA requirements will have at least 8 antennas. + +In case the TRP requirement is set per polarisation, the summation shall be made per polarisation. + +" $P_{\text{EIRP}}$ " is the effective isotropic radiated power (or radiated power spectral density) set in the regulation (assuming a passive BS antenna) in dBm (or dBm/measurement BW). + +" $G_{Ant}$ " is the effective antenna gain, the antenna gain (dBi) is a fixed reference value of 17 dBi. Directivity value should be used in above equations, however with all antenna losses are assumed zero then we can use effective antenna gain. + +--- + +## Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2015-10 | RAN4#76 bis | R4-156540 | | | | Specification structure | 0.0.1 | +| 2015-10 | RAN4#77 | R4-157517 | | | | Approved text proposals in the following documents were implemented:
R4-156802 - TP - Text for TS, structure update
R4-156926 - TP - Text for TS, General clauses
R4-156804 - TP for TS Conducted transmitter requirements - subclause 6.5
R4-156805 - TP for TS Conducted transmitter requirements - clause 7
R4-156806 - Proposed OTA TX power TS text - clause 9
R4-156807 - TP - Text for TS, OTA sensitivity - clause 10 | 0.1.0 | +| 2016-02 | RAN4#78 | R4-161119 | | | | Approved text proposals in the following documents were implemented:
R4-157316 - TP for TS37.105: correction on base station classes
R4-157529 - TP - Text for TS, clean up missing references
R4-157657 - TP for TS 37.105: Additions to OTA sensitivity in section 10
R4-158287 - TP for TS - clean up based on modification in section 4.9
R4-158288 - TP - Text for TS, definitions clean up.
R4-158289 - TP - Text for TS, General section
R4-158290 - TP - Text for TS, Section 5
R4-158291 - TP - Text for TS, Conducted Transmitter Requirements - section 6, 6.1, 6.2, 6.3, 6.4
R4-158292 - TP for 37.105: Unwanted Emissions
R4-158293 - TP for TS 37.105: Radiated transmit power additions to section 9
R4-158294 - TP for TS 37.105: Adding transmitter IMD requirement text to section 6.7
R4-158295 - TP for TS 37.105: Adding receiver emission scaling to section 7.6 | 0.2.0 | +| 2016-02 | RAN4#78 | R4-161308 | | | | Approved text proposals in the following documents were implemented:
R4-160932 - TP to TS 37.105 - EIRP accuracy value
R4-160933 - TP to TS 37.105 - final clean up
R4-160935 - TP to TS 37.105 - add clarification of conformance requirements
R4-160699 - TP for TS 37.105: Editorial corrections to radiated transmit power in clause 9
R4-161362 - TP for TS 37.105: AAS TS overall cleanup
R4-161358 - TP for TS 37.105: Improvements to Radiated transmit power in section 3 and 9
R4-161364 - TP - to TS37.105 - Text amendment regarding multi-band exclusion bands for RX spurious emission
R4-161363 - TP to TS 37.105 - add annexes
R4-161360 - TP for TS37.105 on UEM requirements
R4-161236 - TP for 37.104: core specification design for AAS demodulation requirements
R4-161495 - TP to 37.105 on Multi-band Tx/Rx TAB connector | 0.3.0 | +| 2016-03 | RAN#71 | RP-160400 | | | | Presented to RAN for approval.
Editorial corrections recommended by ETSI editHelp | 1.0.0 | +| 2016-03 | RP-71 | | | | | TR is approved by RAN plenary | 13.0.0 | +| 06/2016 | RP-72 | RP-161142 | 2 | 1 | F | Editorial corrections - alignment with 3GPP drafting rules | 13.1.0 | +| 06/2016 | RP-72 | RP-161127 | 5 | 1 | F | Clarifying UTRA TDD option in Performance section | 13.1.0 | +| 06/2016 | RP-72 | RP-161142 | 6 | - | F | Correction of interfering signal level for Tx intermodulation | 13.1.0 | +| 06/2016 | RP-72 | RP-161142 | 7 | 1 | F | Correct spectrum emission mask and operating band UEM absolute basic limits | 13.1.0 | +| 06/2016 | RP-72 | RP-161142 | 11 | 1 | D | 37.105: Readability improvements and corrections (sections 4 - 10) | 13.1.0 | +| 09/2016 | RP-73 | RP-161635 | 15 | | D | TS 37.105: Readability improvements and corrections (section 3) | 13.2.0 | +| 09/2016 | RP-73 | RP-161635 | 13 | 1 | F | Correction of AAS Base Station performance targets | 13.2.0 | +| 12/2016 | RP-74 | RP-162422 | 0018 | 1 | F | MB MSR related corrections on receiver blocking | 13.3.0 | +| 12/2016 | RP-74 | RP-162422 | 0020 | 2 | D | CR to TS 37.105: Clarifications, definitions alignment and text improvements | 13.3.0 | +| 12/2016 | RP-74 | RP-162422 | 0021 | 1 | F | TS 37.105: Removal of operating band unwanted emissions for Band 46 | 13.3.0 | +| 12/2016 | RP-74 | RP-162422 | 0024 | 1 | F | AAS ACLR absolute limit | 13.3.0 | +| 12/2016 | RP-74 | RP-162422 | 0026 | - | F | Clarification on the Rx diversity branches vs. demodulation branches terminology | 13.3.0 | +| 03/2017 | RP-75 | RP-170586 | 0027 | - | F | Corrections of the power range for SEM and OBUE requirement. | 13.4.0 | +| 03/2017 | RP-75 | RP-170586 | 0028 | 1 | F | TS 37.105: Alignment with legacy specifications on bands 45, 65, | 13.4.0 | + +| | | | | | | | +|--|--|--|--|--|-------------|--| +| | | | | | 66, 67, 68. | | +|--|--|--|--|--|-------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 03/2017 | RP-75 | RP-170586 | 0029 | 1 | F | TS 37.105: Corrections on references | 13.4.0 | +| 03/2017 | RP-75 | RP-170586 | 0030 | - | B | CR to TS 37.105: Isolation of the NB-IoT feature from the AAS BS specification | 13.4.0 | +| 03/2017 | RP-75 | RP-170586 | 0031 | 1 | B | CR to TS 37.105: Isolation of Band 46 from the AAS BS specification | 13.4.0 | +| 03/2017 | RP-75 | RP-170586 | 0032 | 1 | D | CR to TS 37.105: editorial corrections | 13.4.0 | +| 03/2017 | RP-75 | RP-170586 | 0033 | - | F | CR to TS 37.105: Rel-13 single RAT and MSR specification reference updates: MB MSR correction | 13.4.0 | +| 03/2017 | RP-75 | - | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 06/2017 | RP-76 | RP-171305 | 0060 | 1 | A | CR to TS 37.105: Correction of the spurious emissions requirement | 14.1.0 | +| 06/2017 | RP-76 | RP-171305 | 0061 | | A | CR to TS 37.105: BS demodulation requirements update | 14.1.0 | +| 06/2017 | RP-76 | RP-171305 | 0062 | | A | CR to TS 37.105: Addition of 1.4 and 3 MHz channel bandwidths for Band 65 | 14.1.0 | +| 09/2017 | RP-77 | RP-171968 | 0064 | | A | CR to TS 37.105: Corrections of the UTRA Inner loop power control and the frequency error requirements; Rel-14 | 14.2.0 | +| 09/2017 | RP-77 | RP-171968 | 0065 | 1 | B | CR to TS 37.105: introduction of bands 48, 69, 70 | 14.2.0 | +| 09/2017 | RP-77 | RP-171968 | 0067 | | A | Transmit pulse shape filter for TDD operation | 14.2.0 | +| 09/2017 | RP-77 | RP-171968 | 0068 | | F | CR to TS 37.105: versioned reference updates to Rel-14 non-AAS specifications | 14.2.0 | +| 09/2017 | RP-77 | RP-171968 | 0070 | | A | CR to 37.105 on PS-LTE BS regional requirements for Band 28 in Korea | 14.2.0 | +| 2017-12 | RAN#78 | RP-172599 | 0073 | | B | CR to TS 37.105: AAS RF specification, v15.0.0 | 15.0.0 | +| 2018-03 | RAN#79 | RP-180282 | 0074 | 1 | F | CR to TS 37.105 | 15.1.0 | +| 2018-06 | RAN#80 | RP-181109 | 0077 | | A | CR to TS 37.105: absolute ACLR limit | 15.2.0 | +| 2018-06 | RAN#80 | RP-181109 | 0081 | | A | CR to TS 37.105: Correction of regional requirements - removal of co-location and co-existence (4.5), Rel-15
This CR was not implemented as the changes are not based on the latest version | 15.2.0 | +| 2018-06 | RAN#80 | RP-181109 | 0086 | | A | CR to TR 37.105: Clarifications on OTA sensitivity requirement (10.2.1) | 15.2.0 | +| 2018-06 | RAN#80 | RP-181075 | 0090 | | B | Introduction of NR to eAAS | 15.2.0 | +| 2018-09 | RAN#81 | RP-181896 | 0095 | 1 | F | Correction on unwanted emission mask for TS 37.105 | 15.3.0 | +| 2018-09 | RAN#81 | RP-181917 | 0096 | | F | CR to TS 37.105: corrections of the regional requirements (4.5) | 15.3.0 | +| 2018-09 | RAN#81 | RP-181917 | 0097 | | F | CR to TS 37.105: Correction of the OTA blocking requirement (10.6.2.1) | 15.3.0 | +| 2018-12 | RAN#82 | RP-182360 | 0099 | 2 | F | Corrections to AAS receiver requirements for NR | 15.4.0 | +| 2018-12 | RAN#82 | RP-182360 | 0100 | 2 | F | Addition of NR to of OTA out of band blocking requirements | 15.4.0 | +| 2018-12 | RAN#82 | RP-182360 | 0101 | 2 | F | Addition of NR to co-existence and co-location related emissions for single RAT BS | 15.4.0 | +| 2018-12 | RAN#82 | RP-182360 | 0102 | 1 | F | Correction of NR related OBUE emissions tables | 15.4.0 | +| 2018-12 | RAN#82 | RP-182380 | 0108 | | A | CR to TS 37.105: TS37.145 reference correction, Rel-15 | 15.4.0 | +| 2018-12 | RAN#82 | RP-182386 | 0109 | | F | CR to TS 37.105: correction of the "EIRP accuracy directions set" into "OTA peak directions set" | 15.4.0 | +| 2018-12 | RAN#82 | RP-182386 | 0110 | 1 | F | CR to 37.105: Corrections to co-location requirements | 15.4.0 | +| 2018-12 | RAN#82 | RP-182387 | 0112 | | F | CR to TS 37.105: Text alignment for the OTA demodulation branches | 15.4.0 | +| 2018-12 | RAN#82 | RP-182360 | 0113 | 1 | F | Correction of narrowband blocking requirement for NR | 15.4.0 | +| 2018-12 | RAN#82 | RP-182380 | 0116 | | A | Cleanup to conducted requirements text | 15.4.0 | +| 2018-12 | RAN#82 | RP-182386 | 0117 | 1 | F | Cleanup to OTA requirements text | 15.4.0 | +| 2018-12 | RAN#82 | RP-182387 | 0118 | 2 | F | CR to TS 37.105 - polarisation wording improvements for OTA s reference sensitivity | 15.4.0 | +| 2018-12 | RAN#82 | RP-182386 | 0120 | | F | CR for TS37.105: Clean up multi-band RIBs | 15.4.0 | +| 2018-12 | RAN#82 | RP-182387 | 0121 | | F | CR to TS 37.105 Removal of referencing error for in-band blocking | 15.4.0 | +| 2019-03 | RAN#83 | RP-190418 | 0123 | 3 | F | Correction to definition of OTA reference sensitivity | 15.5.0 | +| 2019-03 | RAN#83 | RP-190418 | 0124 | 1 | F | Correction to TDD OFF power requirement | 15.5.0 | +| 2019-03 | RAN#83 | RP-190412 | 0129 | 1 | F | CR to TS 37.105 on Correction of unwanted emissions scaling | 15.5.0 | +| 2019-03 | RAN#83 | RP-190418 | 0130 | | F | CR to TS 37.105: Implementation of 1024QAM for E-UTRA, Rel-15 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190418 | 0131 | 1 | F | CR to TS 37.105: Implementation of sTTI for E-UTRA, Rel-15 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190418 | 0132 | 2 | F | CR to TS 37.105: new Rel-15 bands and isolation of band 49, Tx, Rel-15 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190418 | 0133 | 1 | F | CR to TS 37.105: new Rel-15 bands and isolation of band 49, Rx, Rel-15 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190418 | 0135 | 1 | F | CR to TS37.105 Correction to OTA test requirements | 15.5.0 | +| 2019-06 | RAN#84 | RP-191262 | 0136 | 1 | F | CR to TS 37.105: Corrections on out-of-band blocking requirement | 15.6.0 | +| 2019-06 | RAN#84 | RP-191262 | 0137 | | F | CR to TS 37.105: addition of Band 35, 36, 37 to Tx spurious colocation requirement | 15.6.0 | +| 2019-06 | RAN#84 | RP-191262 | 0138 | | F | Corrections to operation in Band 46 and 49 | 15.6.0 | +| 2019-06 | RAN#84 | RP-191262 | 0140 | | F | Correction on $\Delta$ FOOB for 37.105 | 15.6.0 | +| 2019-06 | RAN#84 | RP-191262 | 0141 | 1 | F | Blocking requirement for MSR/NR operation | 15.6.0 | +| 2019-06 | RAN#84 | RP-191262 | 0142 | | F | Correction to OTA Narrowband blocking requirement | 15.6.0 | +| 2019-06 | RAN#84 | RP-191262 | 0143 | 1 | F | Correction to out of band blocking requirement | 15.6.0 | +| 2019-06 | RAN#84 | RP-191262 | 0146 | | F | Non-AAS CRs mirroring to the AAS specification | 15.6.0 | +| 2019-06 | RAN#84 | RP-191236 | 0152 | 1 | F | CR for TS37.105: correction on TX Diversity and CRS for NR for TAE requirement | 15.6.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------|--------| +| 2019-06 | RAN#84 | RP-191250 | 0144 | 1 | B | n65 introduction to 37.105 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191257 | 0147 | | B | CR to 37.105: Introduction of Band 87 and 88 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191249 | 0148 | | B | CR to 37.105: Introduction of n48 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191245 | 0149 | | B | Introduce Band n18 to 37.105 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191243 | 0150 | | B | Introduction of Band n14 in TS 37.105 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191247 | 0151 | | B | Introduction of Band n30 in TS 37.105 | 16.0.0 | +| 2019-09 | RAN#85 | RP-192053 | 0154 | | A | Correction to RX spurious emissions applicability range for SR E-UTRA BS | 16.1.0 | +| 2019-09 | RAN#85 | RP-192053 | 0156 | | A | CR for TS37.105: definition of synchronization operation | 16.1.0 | +| 2019-09 | RAN#85 | RP-192053 | 0158 | | A | CR to TS 37.105: Clarification on application of OTA receiver requirements for BS supporting polarization | 16.1.0 | +| 2019-09 | RAN#85 | RP-192046 | 0162 | | A | CR to TS 37.105: Correction on operation band unwanted emission | 16.1.0 | +| 2019-09 | RAN#85 | RP-192046 | 0164 | | A | CR to TS37.105 Corrections on NBB requirement (section 7.4 and 10.5) | 16.1.0 | +| 2019-09 | RAN#85 | RP-192030 | 0165 | | F | CR on Protection of SUL band n89 to TS 37.105 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192034 | 0166 | | B | n29 introduction to 37.105 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192050 | 0170 | | A | CR to 37.105: correction of TAB connectors mapping to TAB connector TX min cell group, Rel-16 | 16.1.0 | +| 2019-12 | RAN#86 | RP-193014 | 0171 | | B | Introduction of 2010-2025MHz SUL band into Rel-16 TS 37.105 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193037 | 0173 | | A | CR to 37.105 on Receiver spurious emission requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-193037 | 0175 | 1 | A | CR to 37.105 on Receiver Intermodulation signal offset correction | 16.2.0 | +| 2019-12 | RAN#86 | RP-193037 | 0177 | | A | CR to TS37.105 Corrections on NBB requirement (section 7.4 and 10.5) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193048 | 0179 | | A | CR to TS 37.105: Requirement set applicability | 16.2.0 | +| 2019-12 | RAN#86 | RP-192844 | 0180 | | B | CR to 37.105 on variable duplex FDD bands | 16.2.0 | +| 2020-03 | RAN#87 | RP-200381 | 0181 | | B | Introduction of n26 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200382 | 0182 | | B | Introduction of n53 | 16.3.0 | +| 2020-06 | RAN#88 | RP-200984 | 0184 | | F | CR to TS 37.105: removal of [], Rel-16 | 16.4.0 | +| 2020-09 | RAN#89 | RP-201512 | 0191 | | A | CR to TS 37.105: Rel-13 non-AAS CRs mirroring, Rel-16 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0194 | | A | CR to TS 37.105: Rel-14 non-AAS CRs mirroring, Rel-16 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0196 | | A | CR to TS 37.105: Rel-15 non-AAS CRs mirroring, Rel-16 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0197 | | F | CR to TS 37.105: Rel-15 non-AAS CRs mirroring, Rel-15 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0199 | | B | CR to 37.105: Introduction of NR-U co-existence requirements | 16.5.0 | +| 2020-12 | RAN#90 | RP-202510 | 0206 | | A | CR to TS 37.105: Corrections to core requirements including UEM additional requirements, Rel-16 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202414 | 0207 | | B | CR to 37.105: Introduction of n96 medium range requirements | 16.6.0 | +| 2020-12 | RAN#90 | RP-202510 | 0209 | | A | CR to 37.105 on Removal of additional limit for Band 1 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202510 | 0213 | | A | CR to TS 37.105: addition of the OBUE applicability table, Rel-16 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202451 | 0200 | | B | Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.105 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202452 | 0201 | | B | Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.105 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202448 | 0203 | | B | CR to TS 37.105: introduction of NR band n13 | 17.0.0 | +| 2021-03 | RAN#91e | RP-210097 | 0214 | | B | CR for 37.105 Introduction of NR band n24 | 17.1.0 | +| 2021-03 | RAN#91e | RP-210096 | 0216 | | B | CR for TS 37.105 Introduction of SUL for UL of NR band n24 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210110 | 0218 | | A | CR for 37.105: Corrections related to Band 24 regulatory updates | 17.1.0 | +| 2021-03 | RAN#91e | RP-210118 | 0223 | | A | CR to TS 37.105: Introduction of new BS capability set for NR+EUTRA+UTRA, Rel-17 | 17.1.0 | +| 2021-06 | RAN#92 | RP-211076 | 0232 | | A | CR to TS 37.105: Regional requirements for band 41 in Japan, Rel-17 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0233 | | B | CR to TS 37.105: Introduction of band n67 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0234 | 1 | B | CR to TS 37.105: Introduction of band n85 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211090 | 0238 | | A | CR to 37.105: In-band blocking for multi-band Base Stations | 17.2.0 | +| 2021-09 | RAN#93 | RP-211909 | 0239 | | B | CR to TS 37.105: Introduction of 35 MHz and 45 MHz | 17.3.0 | +| 2021-09 | RAN#93 | RP-211925 | 0242 | | A | Big CR for TS 37.105 Maintenance (Rel-17, CAT A) | 17.3.0 | +| 2021-12 | RAN#94 | RP-212853 | 0246 | | A | Big CR for TS 37.105 Maintenance (Rel-17, CAT A) | 17.4.0 | +| 2022-03 | RAN#95 | RP-220357 | 0249 | | B | CR for 37.105 on Introduction of lower 6GHz NR unlicensed operation for Europe | 17.5.0 | +| 2022-03 | RAN#95 | RP-220347 | 0248 | 1 | B | CR to TS37.105 on introduction of upper 700MHz A block | 17.5.0 | +| 2022-03 | RAN#95 | RP-220331 | 0252 | | A | Big CR for TS 37.105 Maintenance (Rel-17, CAT A) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220376 | 0253 | | B | CR to TS 37.105: RMR 1900MHz band n101 introduction | 17.5.0 | +| 2022-06 | RAN#96 | RP-221684 | 0255 | | B | CR to TS 37.105: introduction of n100 co-existence requirements, Rel-17 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221673 | 0254 | 1 | B | Introducing 6GHz licensed operation into 37.105 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221652 | 0258 | | A | Big CR for TS 37.105 Maintenance (Rel-17, CAT A) | 17.6.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | RP-223315 | 0259 | | B | CR to TS 37.105: Introduction of LTE TDD band 54 | 18.0.0 | +| 2022-12 | RAN#98-e | RP-223319 | 0260 | | B | CR to TS 37.105: Introduction of NR band n105 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230500 | 0263 | | A | CR to TS 37.105: The aplicability of additional BC3 requirements | 18.1.0 | +| 2023-03 | RAN#99 | RP-230500 | 0266 | | A | CR to 37.105: Operating band unwanted emission requirements | 18.1.0 | +| 2023-03 | RAN#99 | RP-230535 | 0268 | | B | CR related to Introduction of NR TDD Band n54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230503 | 0272 | | A | CR to TS 37.105 - Wrong reference to NR additional spurious requirement | 18.1.0 | +| 2023-03 | RAN#99 | RP-230527 | 0274 | | F | CR to TS 37.105: Band 54 additional spurious clarification | 18.1.0 | +| 2023-06 | RAN#100 | RP-231352 | 0277 | | A | CR to 37.105: Clarification on the OBUE limites when narrow carrier adjacent to the sub block edge | 18.2.0 | +| 2023-12 | RAN#102 | RP-233366 | 0278 | | B | CR to TS37.105: introduction of NR bands n31 and n72 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0279 | | B | CR to TS 37.105 - Introduction of band n106 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0280 | | B | CR to 37.105 on introduction of Band n109 | 18.3.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37106/raw.md b/marked/Rel-18/37_series/37106/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c55a09cb7a64b913715054762485d2cfb4928494 --- /dev/null +++ b/marked/Rel-18/37_series/37106/raw.md @@ -0,0 +1,167 @@ + + +# 3GPP TS 37.106 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) requirements for shared spectrum channel access (Release 18)** --- + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +--- + +## ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|--------------------------------------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Symbols..... | 5 | +| 3.3 Abbreviations ..... | 6 | +| 4 General..... | 6 | +| 4.1 Relationship between minimum requirements and test requirements..... | 6 | +| 4.2 Applicability of minimum requirements ..... | 6 | +| 5 Channel access procedures..... | 6 | +| 5.1 Uplink channel access procedure ..... | 6 | +| 5.1.1 Channel access parameters ..... | 6 | +| 5.1.2 Minimum requirement..... | 7 | +| Annex A (informative): Change history..... | 7 | + +# --- 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 UE RF characteristics for shared spectrum channel access. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [3] Void +- [4] 3GPP TS 36.101: "User Equipment (UE) radio transmission and reception". +- [5] 3GPP TS 36.521-1 : "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Conformance testing". +- [6] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access". +- [7] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 standalone". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Channel bandwidth:** The RF bandwidth supporting a single E-UTRA RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----------------------|-------------------| +| BW Channel | Channel bandwidth | +|-----------------------|-------------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|--------------------------------------------| +| BS | Base Station | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| NR | New Radio | +| PUSCH | Physical Uplink Shared Channel | +| UE | User Equipment | + +# --- 4 General + +## 4.1 Relationship between minimum requirements and test requirements + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 36.521-1 [5] Annex F defines Test Tolerances for E-UTRA, and the test specification TS 38.521-1 [7] Annex F defines Test Tolerances for NR. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements. + +The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle. + +The Shared Risk principle is defined in ITU-R M.1545 [2]. + +## 4.2 Applicability of minimum requirements + +- In this specification the Minimum Requirements are specified as general requirements and additional requirements. Where the Requirement is specified as a general requirement, the requirement is mandated to be met in all scenarios +- For specific scenarios for which an additional requirement is specified, in addition to meeting the general requirement, the UE is mandated to meet the additional requirements. +- The requirements in this specification for E-UTRA TDD operating bands apply for downlink and uplink operations using Frame Structure Type 3. + +# --- 5 Channel access procedures + +## 5.1 Uplink channel access procedure + +For uplink operation in Band 46, Band 49, Band n46 and Band n96, a channel access procedure for PUSCH transmission as described in TS 37.213 [6], Clause 4.2.1 is specified. + +### 5.1.1 Channel access parameters + +Channel access related parameters for PUSCH are listed in Table 5.1.1-1. + +**Table 5.1.1-1: Channel access parameters for PUSCH** + +| Parameter | Unit | Value | | +|--------------------------------|--------------|--------------|-----| +| LBT measurement bandwidth (BW) | MHz | 20 | 10 | +| Energy detection threshold | dBm/BW | -72 | -75 | +| Detection timing | microseconds | 25 | | + +### 5.1.2 Minimum requirement + +The UE shall be able to assess whether the medium is busy or idle with at least 90% probability, using a channel access procedure with the parameters in Table 5.1.1-1. \ No newline at end of file diff --git a/marked/Rel-18/37_series/37107/raw.md b/marked/Rel-18/37_series/37107/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..232d145d8dcfe229e431c96fc21aa2336b31d5c3 --- /dev/null +++ b/marked/Rel-18/37_series/37107/raw.md @@ -0,0 +1,298 @@ + + +# 3GPP TS 37.107 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Base Station (BS) requirements and conformance tests for shared spectrum channel access (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis + +Valbonne - FRANCE + +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|--------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 General..... | 8 | +| 4.1 Relationship between minimum requirements and test requirements..... | 8 | +| 5 Channel access procedures (core part)..... | 8 | +| 5.1 Downlink channel access procedure ..... | 8 | +| 5.1.1 Channel access parameters ..... | 8 | +| 5.1.2 Minimum requirement..... | 8 | +| 6 Channel access procedures (performance part) ..... | 9 | +| 6.1 Downlink channel access procedure ..... | 9 | +| 6.1.1 Definition and applicability ..... | 9 | +| 6.1.2 Minimum requirement..... | 9 | +| 6.1.3 Test purpose..... | 9 | +| 6.1.4 Method of test..... | 9 | +| 6.1.4.1 Initial conditions for band 46 and band 49 ..... | 9 | +| 6.1.4.1a Initial conditions for band n46 and band n96 ..... | 9 | +| 6.1.4.2 Procedure ..... | 9 | +| 6.1.5 Test Requirements ..... | 10 | +| Annex A (informative): Change history..... | 11 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document specifies the minimum Radio Frequency (RF) characteristics, minimum performance requirements, and the RF test methods and conformance requirements for E-UTRA with LAA Base Stations (BS) and for NR-U Base Stations (BS). + +# --- 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 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing". +- [3] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [4] Void. +- [5] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access". +- [6] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +## 3.2 Symbols + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|--------------------------------------------| +| BS | Base Station | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| NR | New Radio | + +| | | +|-------|----------------------------------| +| LBT | Listen-Before-Talk | +| PDSCH | Physical Downlink Shared Channel | +| RF | Radio Frequency | + +# 4 General + +## 4.1 Relationship between minimum requirements and test requirements + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 36.141 [2] Annex G defines Test Tolerances for E-UTRA, and the test specification TS 38.141-1 [6] Annex C defines Test Tolerances for NR. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements. + +The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle. + +The Shared Risk principle is defined in ITU-R M.1545 [3]. + +# 5 Channel access procedures (core part) + +## 5.1 Downlink channel access procedure + +For downlink operation in Band 46, Band 49, Band n46 and Band n96, a channel access procedure for PDSCH transmission as described in TS 37.213 [5], Clause 4.1.1 is specified. + +### 5.1.1 Channel access parameters + +Channel access related parameters for PDSCH are listed in Table 5.1.1-1. + +**Table 5.1.1-1: Channel access parameters for PDSCH** + +| Parameter | Unit | Value | +|-------------------------------------------------------|-----------|-----------------------| +| LBT measurement bandwidth | MHz | 10, 20 | +| Energy detection threshold | dBm/20MHz | -72
or
X (Note) | +| | dBm/10MHz | -75 | +| Maximum channel occupancy time | ms | 8 | +| NOTE: The specific value X is declared by the vendor. | | | + +### 5.1.2 Minimum requirement + +The Base Station shall be able to assess whether the medium is busy or idle with at least 90% probability, using a channel access procedure with the parameters in Table 5.1.1-1. + +# 6 Channel access procedures (performance part) + +## 6.1 Downlink channel access procedure + +### 6.1.1 Definition and applicability + +Channel access procedure for downlink operation in band 46, band 49, band n46 and band n96 for PDSCH transmission is described in TS 37.213 [5], Clause 4. + +### 6.1.2 Minimum requirement + +The minimum requirement is in clause 5.1. + +### 6.1.3 Test purpose + +The test purpose is to verify the accuracy of the energy detection threshold, maximum channel occupancy time (MCOT) and minimum idle time under normal conditions for all band 46 and band 49 transmitters in the BS. + +### 6.1.4 Method of test + +#### 6.1.4.1 Initial conditions for band 46 and band 49 + +Test environment: normal; see Annex D.2 of TS 36.141 [2]. + +RF channels to be tested for single carrier: B, M and T; see clause 4.7 of TS 36.141 [2]. + +Connect the signal analyzer to the base station antenna connector as shown in Annex I of TS 36.141 [2]. + +#### 6.1.4.1a Initial conditions for band n46 and band n96 + +Test environment: Normal, see annex B.2 of TS 38.141-1 [6]. + +RF channels to be tested: M; see clause 4.9.1 of TS 38.141-1 [6]. + +Set the channel set-up of the connector under as shown in annex D.1 for BS type 1-C and annex D.3 for BS type 1-H in [6]. + +#### 6.1.4.2 Procedure + +##### MCOT and minimum idle time + +- 1) Set the base station to transmit a signal according to E-TM 1.1 at manufacturer's declared rated output power with corresponding channel bandwidth (i.e. 10 MHz or 20 MHz) for band 46 and 49, or + +Set the base station to transmit a signal according to NR-FR1-TM1.1 at manufacturer's declared rated output power with corresponding channel bandwidth i.e. 10 MHz (only for band n46) or 20 MHz for band n46 or n96. + +- 2) Measure the transmitter ON period during the continuous transmission (after the first channel access). +- 3) Measure the transmitter OFF period between two consecutive transmitter ON periods. +- 4) Verify minimum idle time as follows: + +The transmitter OFF period between two consecutive transmitter ON periods shall not be less than 25 $\mu\text{s}$ . + +- 5) Verify maximum channel occupancy time (MCOT) as follows: + +- a) The duration of each transmitter ON period continuous transmission shall not exceed the maximum channel occupancy time (MCOT) requirement specified in clause 6.1.5. + +##### Energy detection accuracy + +- 6) Generate the interfering signal of AWGN with corresponding channel bandwidth (i.e. 10 MHz or 20 MHz) at the same centre frequency as the tested channel. The interfering signal shall be at a level as specified in table 6.1.5-1. The base station shall stop transmission on the current operating channel and will not resume normal transmissions as long as the interference signal is present. +- 7) The step 6) is repeated multiple times considering the following sub-steps: + - Interferer ON: if the interfering signal is present, the interfering signal should be present for 10ms. + - Interferer OFF: if the interfering signal is removed, the interfering signal should be absent for 10ms. + - The total number of interferer ON duration is assumed to be N and the total number of interferer OFF duration is assumed to be M. The value N, M and the sequence of interferer ON/OFF pattern shall be generated randomly for the test. +- 8) In the test, a counter is maintained with initial value set to 0 when the test starts. +- 9) For every 10ms Interferer ON period, the counter is increased by 1 if there is either an ON/OFF transition or no transmission by the DUT. To pass the test, the counter shall not be less than $N * 0.9$ . + +### 6.1.5 Test Requirements + +In normal conditions, the measurement result shall meet channel access related test requirements for PDSCH as listed in Table 6.1.5-1. + +**Table 6.1.5-1: Channel access test requirements for PDSCH** + +| Parameter | Unit | Value | +|-------------------------------------------------------|-----------|-----------------------------------| +| LBT measurement bandwidth | MHz | 10, 20 | +| Maximum energy detection threshold | dBm/20MHz | -72 + 4dB
or
X + 4dB (Note) | +| | dBm/10MHz | -75 + 4dB | +| Maximum channel occupancy time | ms | 8 | +| NOTE: The specific value X is declared by the vendor. | | | + +The Base Station shall be able to assess whether the medium is busy or idle with at least 90% probability, using a channel access procedure with the parameters in Table 6.1.5-1. \ No newline at end of file diff --git a/marked/Rel-18/37_series/37113/raw.md b/marked/Rel-18/37_series/37113/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5ea25bd1a7fcc7294779e47ce89243148985dce9 --- /dev/null +++ b/marked/Rel-18/37_series/37113/raw.md @@ -0,0 +1,1542 @@ + + +# 3GPP TS 37.113 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations ..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Symbols..... | 14 | +| 3.3 Abbreviations ..... | 14 | +| 4 Test conditions ..... | 15 | +| 4.1 General ..... | 15 | +| 4.2 Arrangements for establishing a communication link..... | 15 | +| 4.2.1 Multiple enclosure BS solution ..... | 16 | +| 4.3 Narrow band responses on receivers..... | 16 | +| 4.4 Exclusion bands..... | 16 | +| 4.4.1 Transmitter exclusion band ..... | 17 | +| 4.4.2 Receiver exclusion band..... | 17 | +| 4.5 BS test configurations ..... | 17 | +| 4.6 Manufacturer declarations..... | 21 | +| 5 Performance assessment ..... | 21 | +| 5.1 General ..... | 21 | +| 5.2 Assessment of performance in Downlink ..... | 22 | +| 5.3 Assessment of performance in Uplink ..... | 22 | +| 5.4 Ancillary equipment..... | 22 | +| 6 Performance criteria..... | 22 | +| 6.1 Performance criteria for continuous phenomena for BS..... | 23 | +| 6.1.1 E-UTRA performance criteria ..... | 23 | +| 6.1.2 UTRA performance criteria..... | 23 | +| 6.1.3 GSM/EDGE performance criteria ..... | 24 | +| 6.1.3.1 GSM/EDGE downlink..... | 24 | +| 6.1.3.2 GSM/EDGE uplink..... | 24 | +| 6.1.4 NB-IoT performance criteria ..... | 24 | +| 6.1.5 NR performance criteria ..... | 25 | +| 6.2 Performance criteria for transient phenomena for BS..... | 25 | +| 6.3 Performance criteria for continuous phenomena for Ancillary equipment..... | 26 | +| 6.4 Performance criteria for transient phenomena for Ancillary equipment..... | 26 | +| 7 Applicability overview..... | 26 | +| 7.1 Emission..... | 26 | +| 7.2 Immunity ..... | 27 | +| 8 Emission..... | 27 | +| 8.1 Test configurations..... | 27 | +| 8.2 Radiated emission from Base Station and ancillary equipment..... | 28 | +| 8.2.1 Radiated emission for Base Stations ..... | 28 | +| 8.2.1.1 Definition ..... | 28 | +| 8.2.1.2 Test method..... | 28 | +| 8.2.1.3 Limits ..... | 28 | +| 8.2.1.4 Interpretation of the measurement results..... | 29 | +| 8.2.2 Radiated emission, ancillary equipment..... | 29 | +| 8.2.2.1 Definition ..... | 30 | +| 8.2.2.2 Test method..... | 30 | +| 8.2.2.3 Limits ..... | 30 | +| 8.3 Conducted emission DC power input/output port..... | 30 | +| 8.3.1 Definition..... | 30 | +| 8.3.2 Test method ..... | 30 | + +| | | | +|--------------------------------------------------------------|------------------------------------------------------------------------------------|-----------| +| 8.3.3 | Limits..... | 31 | +| 8.4 | Conducted emissions, AC mains power input/output port..... | 31 | +| 8.4.1 | Definition..... | 31 | +| 8.4.2 | Test method ..... | 31 | +| 8.4.3 | Limits..... | 31 | +| 8.5 | Harmonic current emissions (AC mains input port) ..... | 31 | +| 8.6 | Voltage fluctuations and flicker (AC mains input port)..... | 31 | +| 8.7 | Telecommunication ports..... | 32 | +| 8.7.1 | Definition..... | 32 | +| 8.7.2 | Test method ..... | 32 | +| 8.7.3 | Limits..... | 32 | +| 9 | Immunity ..... | 32 | +| 9.1 | Test configurations..... | 32 | +| 9.2 | RF electromagnetic field (80 MHz - 6000 MHz)..... | 33 | +| 9.2.1 | Definition..... | 33 | +| 9.2.2 | Test method and level..... | 33 | +| 9.2.3 | Performance criteria ..... | 34 | +| 9.3 | Electrostatic discharge..... | 34 | +| 9.3.1 | Definition..... | 34 | +| 9.3.2 | Test method and level..... | 34 | +| 9.3.3 | Performance criteria ..... | 34 | +| 9.4 | Fast transients common mode..... | 34 | +| 9.4.1 | Definition..... | 35 | +| 9.4.2 | Test method and level..... | 35 | +| 9.4.3 | Performance criteria ..... | 35 | +| 9.5 | RF common mode (0,15 MHz - 80 MHz)..... | 35 | +| 9.5.1 | Definition..... | 35 | +| 9.5.2 | Test method and level..... | 35 | +| 9.5.3 | Performance criteria ..... | 36 | +| 9.6 | Voltage dips and interruptions ..... | 36 | +| 9.6.1 | Definition..... | 36 | +| 9.6.2 | Test method and level..... | 36 | +| 9.6.3 | Performance criteria ..... | 36 | +| 9.7 | Surges, common and differential mode..... | 37 | +| 9.7.1 | Definition..... | 37 | +| 9.7.2 | Test method and level..... | 37 | +| 9.7.2.1 | Test method for telecommunication ports directly connected to outdoor cables ..... | 37 | +| 9.7.2.2 | Test method for telecommunication ports connected to indoor cables..... | 37 | +| 9.7.2.3 | Test method for AC power ports ..... | 37 | +| 9.7.3 | Performance criteria ..... | 37 | +| Annex A (normative): BER assessment for GSM/EDGE..... | | 39 | +| A.1 | Assessment of BER at the output of a transmitter ..... | 39 | +| A.1.1 | Assessment of BER using static layer 1 functions..... | 39 | +| A.1.2 | Assessment of BER using RXQUAL..... | 39 | +| A.2 | Assessment of BER at the output of a receiver..... | 39 | +| A.2.1 | Assessment of BER using RXQUAL..... | 39 | +| A.2.2 | Assessment of BER using reported BER..... | 39 | +| Annex B (normative): Simplified immunity testing..... | | 40 | +| B.1 | Applicability..... | 40 | +| B.2 | Capability Sets for simplified immunity testing ..... | 40 | +| Annex C (informative): Change history..... | | 42 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document covers the assessment of NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT Multi-Standard Radio (MSR) Base Stations and associated ancillary equipment in respect of Electromagnetic Compatibility (EMC). + +The present document specifies the applicable test conditions, performance assessment and performance criteria for NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT Base Stations and associated ancillary equipment in one of the following categories: + +- Multi-Standard Radio (MSR) Base Stations for NR, E-UTRA, UTRA and GSM/EDGE meeting the requirements of TS 37.104 [6], with conformance demonstrated by compliance to TS 37.141 [11]. + +NOTE: For NR, scope of this specification is limited to *BS type 1-C*. For EMC requirements of the MSR BS for *BS type 1-H* and *BS type 1-O*, refer to TS 37.114 [39]. + +- *BS type 1-C* for NR meeting the requirements of TS 38.104 [35], with conformance demonstrated by compliance to TS 38.141-1 [36] +- Base Stations for E-UTRA meeting the requirements of TS 36.104 [4], with conformance demonstrated by compliance to TS 36.141 [9]. +- Base Stations for UTRA FDD meeting the requirements of TS 25.104 [2], with conformance demonstrated by compliance to TS 25.141 [7]. +- Base Stations for UTRA TDD meeting the requirements of TS 25.105 [3], with conformance demonstrated by compliance to TS 25.142 [8]. +- Base Stations for GSM/EDGE meeting the requirements of TS 45.005 [5], with conformance demonstrated by compliance to TS 51.021 [10]. +- Base Stations for NB-IoT meeting the requirements of TS 36.104 [4], with conformance demonstrated by compliance to TS 36.141 [9]. + +In addition to MSR base stations, the present document covers other BS supporting more than one RAT. + +Technical requirements related to the antenna port of Base Stations are not included in the present document. These are found in the relevant product standards [2-11, 35, 36]. + +The environment classification used in the present document refers to the residential, commercial, and light industrial environment classification used in IEC 61000-6-1 [12], IEC 61000-6-3 [13] and IEC 61000-6-8 [41]. + +The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)". + +- [3] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD)". +- [4] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception ". +- [5] 3GPP TS 45.005: "Radio transmission and reception". +- [6] 3GPP TS 37.104: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception". +- [7] 3GPP TS 25.141: "Base Station (BS) conformance testing (FDD)". +- [8] 3GPP TS 25.142: "Base Station (BS) conformance testing (TDD)". +- [9] 3GPP TS 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing". +- [10] 3GPP TS 51.021: "Base Station System (BSS) equipment specification; Radio aspects". +- [11] 3GPP TS 37.141: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing". +- [12] IEC 61000-6-1: 2005: "Electromagnetic compatibility (EMC) - Part 6-1: Generic standards – Immunity for residential, commercial and light-industrial environments". +- [13] IEC 61000-6-3: 2020: "Electromagnetic compatibility (EMC) - Part 6-3: Generic standards – Emission standard for equipment in residential environments". +- [14] IEC 60050-161: "International Electrotechnical Vocabulary (IEV) - Part 161: Electromagnetic compatibility". +- [15] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain". +- [16] ITU-R Recommendation SM.1539-1 (2001): "Variation of the boundary between the out-of-band and spurious domains required for the application of Recommendations ITU-R SM.1541 and ITU-R SM.329". +- [17] Void +- [18] Void +- [19] IEC 61000-3-2 (2004): "Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current $\leq 16$ A)". +- [20] IEC 61000-3-12 (2005): "Electromagnetic compatibility (EMC) - Part 3-12: Limits - Limits for harmonic current produced by equipment connected to public low-voltage system with input current $> 16$ A and $\leq 75$ A". +- [21] IEC 61000-3-3 (2002): "Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage fluctuations and flicker in low-voltage supply systems for equipment with rated current $\leq 16$ A". +- [22] IEC 61000-3-11 (2000): "Electromagnetic compatibility (EMC) - Part 3-11: Limits – Limitation of voltage fluctuations and flicker in low-voltage supply systems for equipment with rated current $\leq 75$ A and subject to conditional connections". +- [23] IEC 61000-4-3: "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency electromagnetic field immunity test". +- [24] IEC 61000-4-2: "Electromagnetic compatibility (EMC) - Part 4-2: Testing and measurement techniques - Electrostatic discharge immunity test". +- [25] IEC 61000-4-4: "Electromagnetic compatibility (EMC) - Part 4-4: Testing and measurement techniques - Electrical fast transient/burst immunity test". +- [26] IEC 61000-4-6: "Electromagnetic compatibility (EMC) - Part 4-6: Testing and measurement techniques - Immunity to contacted disturbances, induced by radio frequency fields". + +- [27] IEC 61000-4-11: "Electromagnetic compatibility (EMC) - Part 4-11: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations. Immunity tests". +- [28] IEC 61000-4-5: "Electromagnetic compatibility (EMC) - Part 4-5: Testing and measurement techniques - Surge immunity test". +- [29] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)". +- [30] 3GPP TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)". +- [31] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [32] 3GPP TS 45.008: "Radio subsystem link control". +- [33] 3GPP TS 51.010-1: " Mobile Station (MS) conformance specification; Part 1: Conformance specification". +- [34] CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements". +- [35] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [36] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing; Part 1: Conducted conformance testing". +- [37] 3GPP TS 38.141-2: "NR; Base Station (BS) conformance testing; Part 2: Radiated conformance testing". +- [38] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements". +- [39] 3GPP TS 37.114: "Active Antenna System (AAS) Base Station (BS), Electromagnetic Compatibility (EMC)". +- [40] IEC 61000-4-21: "Electromagnetic Compatibility (EMC) Part 4-21: Testing And Measurement Techniques Reverberation Chamber Test Methods". +- [41] IEC 61000-6-8: 2020: "Electromagnetic compatibility (EMC) - Part 6-8: Generic standards - Emission standard for professional equipment in commercial and light-industrial locations". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Ancillary equipment:** Equipment (apparatus), used in connection with a receiver, transmitter or transceiver is considered as an ancillary equipment (apparatus) if: + +- the equipment is intended for use in conjunction with a receiver, transmitter or transceiver to provide additional operational and/or control features to the radio equipment, (e.g. to extend control to another position or location); and +- the equipment cannot be used on a stand-alone basis to provide user functions independently of a receiver, transmitter or transceiver; and +- the receiver, transmitter or transceiver to which it is connected, is capable of providing some intended operation such as transmitting and/or receiving without the ancillary equipment (i.e. it is not a sub-unit of the main equipment essential to the main equipment basic functions). + +**antenna connector:** connector at the conducted interface of the *BS type 1-C* + +**Band category:** group of operating bands for which the same MSR scenarios apply + +**Base Station equipment:** Radio and/or ancillary equipment intended for operation at a fixed location and powered directly or indirectly (e.g. via an AC/DC converter or power supply) by AC mains network, or an extended local DC mains network. + +**Base Station RF bandwidth:** The bandwidth in which a Base Station transmits and/or receives multiple carriers and/or RATs simultaneously. + +**Base Station RF bandwidth edge:** The frequency of one of the edges of the Base Station RF bandwidth. + +**BS type 1-C:** NR base station operating at FR1 with requirements set consisting only of conducted requirements defined at individual *antenna connectors*. + +**Channel bandwidth:** The RF bandwidth supporting a single E-UTRA RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +**Continuous phenomena (continuous disturbance):** Electromagnetic disturbance, the effects of which on a particular device or equipment cannot be resolved into a succession of distinct effects (IEC 60050-161 [14]). + +**Lower RF bandwidth edge:** The frequency of the lower edge of the Base Station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements. + +**Maximum Base Station RF bandwidth:** The maximum RF bandwidth supported by a BS within an operating band. + +**Maximum throughput:** The maximum achievable throughput for a reference measurement channel. + +**MB-MSR Base Station:** MSR Base Station characterized by the ability of its transmitter and/or receiver to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different non-overlapping operating band than the other carrier(s). + +**MSR Base station:** Base Station characterized by the ability of its receiver and transmitter to process two or more carriers in common active RF components simultaneously in a declared RF bandwidth, where at least one carrier is of a different RAT than the other carrier(s). + +NOTE: A Base Station where receiver or transmitter processes carriers of different RATs simultaneously, but not through common active RF components, is not an MSR BS according to the above definition. Such a BS is in the present specification referred to as "other BS supporting more than one RAT". + +**NB-IoT In-band operation:** NB-IoT is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier. + +**NB-IoT guard band operation:** NB-IoT is operating in guard band when it utilizes the unused resource block(s) within an E-UTRA carrier's guard-band. + +**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment. + +**Radio communications equipment:** Telecommunications equipment which includes one or more transmitters and/or receivers and/or parts thereof for use in a fixed, mobile or portable application. It can be operated with ancillary equipment but if so, is not dependent on it for basic functionality. + +**Radio equipment:** Equipment which contains Radio digital unit and Radio unit. + +**Radio digital unit:** Equipment which contains base band and functionality for controlling Radio unit. + +**Radio unit:** Equipment which contains transmitter and/or receiver. + +**Port:** A particular interface, of the specified equipment (apparatus), with the electromagnetic environment. For example, any connection point on an equipment intended for connection of cables to or from that equipment is considered as a port (see figure 3.1.1). + +**Receiver exclusion band:** The receiver exclusion band is the band of frequencies over which no tests of radiated immunity of a receiver are made. The exclusion band for receivers is expressed relative to the base station receive band. + +**Signal and control port:** Port which carries information or control signals, excluding antenna ports. + +**Telecommunication port:** Ports which are intended to be connected to telecommunication networks (e.g. public switched telecommunication networks, integrated services digital networks), local area networks (e.g. Ethernet, Token Ring) and similar networks. + +NOTE: *Telecommunication port* is called "wired network port" in CISPR 32 [34]. + +**Throughput:** The number of payload bits successfully received per second for a reference measurement channel in a specified reference condition. + +**Transient phenomena:** Pertaining to or designating a phenomena or a quantity which varies between two consecutive steady states during a time interval short compared with the time-scale of interest (IEC 60050-161 [14]). + +**Transmitter exclusion band:** The transmitter exclusion band is the band of frequencies over which no tests of radiated immunity of a transmitter are made. The exclusion band for transmitters is expressed relative to the carrier frequencies used (the carrier frequencies of the base stations activated transmitter(s)). + +**Upper RF bandwidth edge:** The frequency of the upper edge of the Base Station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements. + +![Diagram of an Apparatus with various ports.](b3c108e7145f2017957569d06ea359cb_img.jpg) + +The diagram shows a central rectangular box labeled "Apparatus". Above this box is a larger rectangular box labeled "Enclosure Port". To the left of the "Apparatus" box, three horizontal lines extend to the left, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". To the right of the "Apparatus" box, three horizontal lines extend to the right, labeled from top to bottom: "Antenna port", "Signal/control port", and "Telecommunication port". + +Diagram of an Apparatus with various ports. + +Figure 3.1-1: Examples of ports + +![Diagram of BS Equipment with a single enclosure solution.](f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg) + +The diagram shows a large rectangular box labeled "BS Equipment". Inside this box, in the bottom right corner, is a smaller rectangular box labeled "Radio Equipment". + +Diagram of BS Equipment with a single enclosure solution. + +Figure 3.1-2: BS with single enclosure solution + +![Diagram of BS with multiple enclosure solution. A large dashed rectangle labeled 'BS Equipment' contains two sub-components: 'Radio Equipment' and 'Radio unit'. 'Radio Equipment' is a dashed rectangle containing a solid rectangle labeled 'Radio digital unit'. 'Radio unit' is a solid rectangle. A solid line connects 'Radio digital unit' to 'Radio unit'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +BS Equipment + +Diagram of BS with multiple enclosure solution. A large dashed rectangle labeled 'BS Equipment' contains two sub-components: 'Radio Equipment' and 'Radio unit'. 'Radio Equipment' is a dashed rectangle containing a solid rectangle labeled 'Radio digital unit'. 'Radio unit' is a solid rectangle. A solid line connects 'Radio digital unit' to 'Radio unit'. + +**Figure 3.1-3: BS with multiple enclosure solution** + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BW Channel | Channel bandwidth | +| F C,high | Center frequency of the highest transmitted/received carrier. | +| F C,low | Center frequency of the lowest transmitted/received carrier. | +| F DL_high | The highest frequency of the downlink operating band | +| F DL_low | The lowest frequency of the downlink operating band | +| f offset | Frequency offset used for discovering narrowband response for receivers | +| F offset, RAT | Frequency offset from F C,high to the upper RF bandwidth edge or F C,low to the lower RF bandwidth edge for a specific RAT | +| F UL_high | The highest frequency of the uplink operating band | +| F UL_low | The lowest frequency of the uplink operating band | +| Δf OBUE | Maximum offset of the operating band unwanted emissions mask from the operating band edge | +| Δf OOB | Maximum offset of the out-of-band boundary from the uplink operating band edge | + +## 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]. + +| | | +|----------|------------------------------------------------| +| AC | Alternating Current | +| AMN | Artificial Mains Network | +| ARFCN | Absolute Radio Frequency Channel Number | +| BC | Band Category | +| BER | Bit Error Ratio | +| BLER | Block Error Ratio | +| CDN | Coupling/Decoupling Network | +| CS | Capability Set | +| DC | Direct Current | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| EARFCN | E-UTRA Absolute Radio Frequency Channel Number | +| EMC | Electromagnetic Compatibility | +| EPC | Evolved Packet Core | +| ESD | Electrostatic discharge | +| EUT | Equipment Under Test | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| MB-MSR | Multi-Band Multi-Standard Radio | +| MSR | Multi-Standard Radio | +| NB-IoT | Narrowband – Internet of Things | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | + +| | | +|--------|-------------------------------------------------| +| NTC | Test Configuration for Non-contiguous operation | +| RAT | Radio Access Technology | +| RF | Radio frequency | +| rms | root mean square | +| TC | Test Configuration | +| UARFCN | UTRA Absolute Radio Frequency Channel Number | +| UTRA | Universal Terrestrial Radio Access | + +# --- 4 Test conditions + +## 4.1 General + +The equipment shall be tested in normal test environment defined in base station conformance testing specification TS 37.141 [11]. The test conditions shall be recorded in the test report. + +For a EUT which contains more than one BS, it is sufficient to perform tests relating to each type of port of each representative type of the BS forming part of the EUT. For an MSR BS or other BS supporting more than one RAT, tests shall be performed with RATs activated according to the test configuration in subclause 4.5. Tests shall be performed relating to each type of port, and need not be repeated for each RAT if operating RATs are assessed simultaneously during the test. For other BS supporting more than one RAT however (other than MSR BS), tests relating to the antenna port(s) shall always be performed for each supported RAT. + +For BS capable of multi-band operation, the requirements in the present document apply for each supported operating band unless otherwise stated. Operating bands and RATs shall be activated according to the test configuration in subclause 4.5. Tests shall be performed relating to each type of port and all RATs per band shall be assessed during the tests. + +The manufacturer shall declare the supported operating band(s) according to subclause 4.4 of TS 37.141 [11]. Requirements apply only for the declared operating band and corresponding Band Category. + +The manufacturer shall declare the supported capability set(s) according to subclause 4.7 of TS 37.141 [11]. Tests performed on a Base Station according to a declared Capability Set cover all single RAT and multi-RAT configurations included in the declared Capability Set. Exception can be made for immunity testing based on declaration DEMC.2 and DEMC.4 (see table 4.6-1), as detailed in Annex B. + +## 4.2 Arrangements for establishing a communication link + +The wanted RF signal nominal frequency shall be selected by setting the channel number according to the following: + +- The NR Absolute Radio Frequency Channel Number (NR-ARFCN) for NR carrier, +- The Absolute Radio Frequency Channel Number (EARFCN) for E-UTRA carrier, +- The Absolute Radio Frequency Channel Number (UARFCN) for UTRA carrier, +- The Absolute Radio Frequency Channel Number (ARFCN) for GSM/EDGE carrier, +- NB-IoT Narrowband – Internet of Things + +A communication link shall be set up with a suitable test system capable of evaluating the required performance criteria (hereafter called "the test system") at the radio interface and telecommunication port/ports (the S1/Iub/Abis interface). The test system shall be located outside of the test environment. + +When the EUT is required to be in the transmit/receive mode, the following conditions shall be met: + +- The EUT shall be commanded to operate at maximum rated transmit power; +- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment; +- The wanted RF input signal level shall be set to a level where the performance is not limited by the receiver noise floor or strong signal effects. + +NOTE: 15 dB above the reference sensitivity level has been used as an example of the wanted input signal level in UTRA TDD, UTRA FDD, E-UTRA or NB-IoT EMC specifications for establishing a stable communication link. The RAT-specific reference sensitivity levels are specified in: + +- TS 25.142 [8] for UTRA TDD, + - TS 25.141 [7] for UTRA FDD, + - TS 36.141 [9] for E-UTRA or for NB-IoT, + - TS 38.141-1 [36] for NR. +- For GSM/EDGE the wanted receiver input signal level shall be set to a nominal value of -47 dBm. + +For immunity tests subclause 4.3 shall additionally apply. + +### 4.2.1 Multiple enclosure BS solution + +For a BS with multiple enclosures, the BS part with Radio digital unit and the Radio unit may be tested separately. Communication link shall be set up in the same way as if they are in single BS enclosure. The Radio Digital unit and the Radio unit shall communicate over an interface enabling establishment of a communication link. + +## 4.3 Narrow band responses on receivers + +Responses on receivers or duplex transceivers occurring during the immunity test at discrete frequencies which are narrow band responses (spurious responses), are identified by the following method: + +- if during an immunity test the quantity being monitored goes outside the specified tolerances (clause 6), it is necessary to establish whether the deviation is due to a narrow band response or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency first increased, and then decreased by an offset $f_{\text{offset}}$ , where: + - For E-UTRA or for NR, $f_{\text{offset}} = 2 \times BW_{\text{Channel}}$ , where $BW_{\text{Channel}}$ is the channel bandwidth as defined in TS 36.104 [9] for E-UTRA, or in TS 38.104 [35] for NR; + - For UTRA, $f_{\text{offset}} = 10 \text{ MHz}$ + - For GSM/EDGE, $f_{\text{offset}} = 400 \text{ kHz}$ + - For NB-IoT, $f_{\text{offset}} = 400 \text{ kHz}$ +- if the deviation disappears in either or both of the above offset cases, then the response is considered as a narrow band response; +- if the deviation does not disappear, this may be due to the fact that the offset has made the frequency of the unwanted signal correspond to the frequency of another narrow band response. Under these circumstances the procedure is repeated with the increase and decrease of the frequency of the unwanted signal set to $1.25 \times f_{\text{offset}}$ ; +- if the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test. + +Narrow band responses are disregarded. + +For an MSR BS or other BS supporting more than one RAT, the method above shall be applied for each tested RAT. For BS capable of multi-band operation, all supported operating bands shall be considered for narrowband responses. + +## 4.4 Exclusion bands + +An exclusion band is a band of frequencies over which no tests of radiated immunity are made. + +### 4.4.1 Transmitter exclusion band + +For testing of radiated immunity there shall be no transmitter exclusion band. + +### 4.4.2 Receiver exclusion band + +The receiver exclusion band for Base Stations is the band of frequencies over which no tests of radiated immunity of a receiver are made. + +The range of the exclusion band shall be: + +$$F_{UL\_low} - \Delta f_{OOB} < f < F_{UL\_high} + \Delta f_{OOB}$$ + +Where: + +The value of $F_{UL\_low}$ and $F_{UL\_high}$ are defined for each operating band for NR, E-UTRA, UTRA and GSM/EDGE in TS 37.104 [6]. + +The values of $\Delta f_{OOB}$ are defined in table 4.4.2-1. + +**Table 4.4.2-1: Maximum $\Delta f_{OOB}$ offset outside the uplink operating band** + +| Operating band characteristics | \Delta f_{OOB} (MHz) | +|---------------------------------------------------------------------|------------------------------------------| +| $200 \text{ MHz} \geq F_{UL\_high} - F_{UL\_low}$ | 20 | +| $200 \text{ MHz} < F_{UL\_high} - F_{UL\_low} \leq 900 \text{ MHz}$ | 60 | + +For BS capable of multi-band operation, the total receiver exclusion band shall be the combination of the exclusion bands for each operating band supported by the BS. + +**Table 4.4-2: Void** + +**Table 4.4-3: Void** + +## 4.5 BS test configurations + +The present clause defines the BS test configurations that shall be used for demonstrating conformance. This is specified in table 4.5-1, 4.5-1a, 4.5-1b, and 4.5-1c for multi-RAT capable MSR Base Stations, in table 4.5-2 for single-RAT capable BS and in table 4.5-3 for multi-band capable BS. For other BS supporting more than one RAT (other than MSR BS), table 4.5-2 applies separately for each RAT supported. + +The test configurations apply according to the declared RAT Capability Set (CS) of the MSR Base Station according to clause 4.7 of TS 37.141 [11] and the Band Category of the declared operating band (BC1, BC2 or BC3), as listed in the heading of each table. + +The test configurations (TCx) are defined in TS 37.141 [11], clause 4.8. + +For a BS declared to be capable of contiguous operation only, the test configuration(s) in tables 4.5-1 and 4.5-2 denoted by a "C" shall be used for testing. + +For a BS declared to be capable of contiguous and non-contiguous operation and where the parameters in the manufacture's declaration according to clause 4.7.2 of TS 37.141 [11] are identical for contiguous and non-contiguous operation, the test configurations denoted by "CNC" shall be used. + +For a BS declared to be capable of contiguous and non-contiguous operation and where the parameters in the manufacture's declaration according to clause 4.7.2 of TS 37.141 [11] are not identical for contiguous and non-contiguous operation, the test configurations denoted by "C/NC" shall be used for testing. + +For a BS declared to support NB-IoT operating in-band, the test configuration(s) in table 4.5-1 and 4.5-2 denoted by "NI" shall be used for testing. + +For a BS declared to support NB-IoT operating in guard band, the test configuration(s) in table 4.5-1 and 4.5-2 denoted by "NG" shall be used for testing. + +For a BS declared to support NB-IoT operating in guard band and in-band, the test configuration(s) in table 4.5-1 and 4.5-2 denoted by "NG" or/and "NI" shall be used for testing. + +For a BS declared to support NB-IoT standalone, the test configuration(s) in table 4.5-1a, 4.5-1b and 4.5-2 and entries that refer to single-RAT specifications shall be used for testing. + +For a MSR BS where signals from supported RATs are processed in common active components (see DEMC.2 and DEMC.4 in table 4.6-1), it is sufficient to consider a reduced set of CSs for immunity testing, as described in Annex B. + +For immunity tests: + +- The communication link for the RAT(s) listed in the table shall be established according to clause 4.2. +- Tests for ports relating to the RAT(s) supported shall be performed according to clause 4.1. + +**Table 4.5-1: Test configurations for single-band Multi-RAT capable MSR BS (CS3-7)** + +| Capability Set | UTRA + E-UTRA.
NB-IoT in-band,
NB-IoT guard band
(Note 2, Note 3) (CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT
in-band,
NB-IoT
guard
band
(Note 2,
Note 3)
(CS 5) | GSM +
UTRA + E-
UTRA,
(CS 6) | GSM+UTRA/
E-UTRA, UTRA+
E-UTRA,
NB-IoT in-band,
NB-IoT guard
band
(Note 2,
Note 3)
(CS7) | +|----------------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------|---------------------------------|--------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| Emission tests | C: TC3a
CNC:
NTC3
C/NC:
TC3a and
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC:
NTC3
C/NC:
TC3a and
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC4a
CNC:
NTC4a
C/NC:
TC4a and
NTC4a | C: TC4b
CNC:
NTC4b
C/NC:
TC4b and
NTC4b
NI: TC15
NG: TC18 | C: TC4c
CNC:
NTC4c
C/NC:
TC4c and
NTC4c | C: (TC4a, TC3a)
(Note 4), TC4b

CNC: (NTC4a,
NTC3) (Note 4),
NTC4b

C/NC: (TC4a,
NTC4a, TC3a,
NTC3) (Note 4),
TC4b, NTC4b

NI: TC15, (TC16)
(Note 4)

NG: TC18, (TC19)
(Note 4) | +| Immunity tests | C: TC3a
CNC:
NTC3
C/NC:
TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC:
NTC3
C/NC:
TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC5a
CNC:
NTC5a
C/NC:
TC5a,
NTC5a | C: TC5b
CNC:
NTC5b
C/NC:
TC5b,
NTC5b
NI: TC15
NG: TC18 | C: TC5b
CNC:
NTC5c,
C/NC:
TC5b,
NTC5c | C: TC5b
CNC: NTC5b
C/NC: TC5b,
NTC5b
NI: TC15
NG: TC18 | + +NOTE 1: Void + +NOTE 2: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing. + +NOTE 3: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing. + +NOTE 4: For Band 3, the test configuration is only applicable if UTRA is declared to be supported in Band 3. + +Table 4.5-1a: Test configurations for single-band Multi-RAT capable MSR BS (CS9-13) + +| Capability Set | GSM+NB-IoT standalone (CS 9) | UTRA + NB-IoT standalone (CS 10) | | E-UTRA + NB-IoT standalone (CS 11) | | | GSM+UTRA+NB-IoT standalone (CS 12) | GSM+ E-UTRA+ NB-IoT standalone (CS 13) | +|----------------|------------------------------|----------------------------------|------|------------------------------------|------|------|------------------------------------|----------------------------------------| +| BS test case | BC2 | BC1 | BC2 | BC1 | BC2 | BC3 | BC2 | BC2 | +| Emission tests | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Immunity tests | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | + +Table 4.5-1b: Test configurations for single-band Multi-RAT capable MSR BS (CS14-17) + +| Capability Set | UTRA + E-UTRA + NB-IoT standalone (CS 14) | | | GSM + UTRA + E-UTRA + NB-IoT standalone (CS 15) | NR + E-UTRA NB-IoT in-band(Note2) NB-IoT guard band(Note3) (CS 16) | | NR + NB-IoT standalone + E-UTRA NB-IoT in-band(Note2) NB-IoT guard band(Note3) (CS 17) | | +|----------------|-------------------------------------------|------|------|-------------------------------------------------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|---------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | +| Emission tests | TC14 | TC14 | TC14 | TC13, (TC12, TC13) (NOTE4) | C, NI, NG: TC21
CNC, NCNI, NCNG: NTC21
C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21
CNC, NCNI, NCNG: NTC21
C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | +| Immunity tests | TC14 | TC14 | TC14 | TC13 | C, NI, NG: TC21
CNC, NCNI, NCNG: NTC21
C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21
CNC, NCNI, NCNG: NTC21
C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | + +NOTE 1: Void + +NOTE 2: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing. + +NOTE 3: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing. + +NOTE 4: For Band 3, the test configuration is only applicable if UTRA is declared to be supported in Band 3. + +**Table 4.5-1c: Test configurations for single-band Multi-RAT capable MSR BS (CS18-19)** + +| Capability Set | GSM + NR + E-UTRA
NB-IoT in-band (NOTE 2)
NB-IoT guard band (NOTE 3)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (NOTE 2)
NB-IoT guard band (NOTE 3)
(CS19) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| BS test case | BC2 | BC2 | +| Emission tests | C, NI, NG: TC21a
CNC, NCNI, NCNG: NTC21a
C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b
CNC, NCNI, NCNG: NTC21b
C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| Immunity tests | C, NI, NG: TC21a
CNC, NCNI, NCNG: NTC21a
C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b
CNC, NCNI, NCNG: NTC21b
C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| NOTE 1: Void | | | +| NOTE 2: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing. | | | +| NOTE 3: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing. | | | + +**Table 4.5-2: Test configurations for single-band Single-RAT multi-carrier capable BS** + +| Capability Set | UTRA (MC) capable BS (CS1) | | | E-UTRA (MC) capable BS (CS2)
NB-IoT in-band,
NB-IoT guard band
(Note 2, Note 3) | | | NB-IoT (MC)
capable BS (CS8) | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------|------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------|---------------------------------|-----|-----| +| BS test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| Emission tests | C: TC1a
CNC: NTC1a
C/NC: TC1a and NTC1a | C: TC1a
CNC: NTC1a
C/NC: TC1a and NTC1a | C: TC1b | C: TC2
CNC: NTC2
C/NC: TC2 and NTC2
NI: TC17
NG: TC20 | C: TC2
CNC: NTC2
C/NC: TC2 and NTC2
NI: TC17
NG: TC20 | C: TC2
CNC: NTC2
C/NC: TC2 and NTC2
NI: TC17
NG: TC20 | TC8 | TC8 | TC8 | +| Immunity tests | C: TC1a
CNC: NTC1a
C/NC: TC1a, NTC1a | C: TC1a
CNC: NTC1a
C/NC: TC1a, NTC1a | C: TC1b | C: TC2
CNC: NTC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | C: TC2
CNC: NTC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | C: TC2
CNC: NTC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | TC8 | TC8 | TC8 | +| NOTE 1: Void | | | | | | | | | | +| NOTE 2: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing. | | | | | | | | | | +| NOTE 3: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing. | | | | | | | | | | + +**Table 4.5-3: Test configurations for multi-band capable BS (CS1-CS7, CS16 and CS18-CS19)** + +| Capability Set | Multi-band testing | | +|----------------|--------------------|------| +| BS test case | BC1/BC2 | BC3 | +| Emission tests | TC7b | TC7b | +| Immunity tests | TC7b | TC7b | + +## 4.6 Manufacturer declarations + +The following EMC-specific manufacturer's declarations listed in table 4.6-1 are required, except as noted, to be provided by the manufacturer for MSR BS requirements testing. + +NOTE: The below listed manufacturer's declarations are supplementary to declarations covered in TS 37.141 [11]. + +**Table 4.6-1: EMC-specific manufacturer declarations** + +| Declaration identifier | Declaration | Description | +|------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DEMC.1
(NOTE 1) | Declaration of ports intended to be used with cables less than 3 m | Declaration of any ports intended to be used with cables less than 3 m. | +| DEMC.2 | Common and/or RAT-specific active RF components | Declaration of common and/or RAT-specific active RF components and other HW blocks for a communication link in MSR BS or other BS supporting more than one RAT. | +| DEMC.3 | Common and/or band-specific active RF components | Declaration of common and/or band-specific active RF components and other HW blocks for a communication link in BS capable of multi-band operation. | +| DEMC.4
(NOTE 1) | RAT dependencies for simplified immunity testing | Declaration of RAT dependencies for simplified immunity testing.

For the case where BS employs common active RF components (DEMC.2), declare RATs which are handled per operating band in common active components in the radio digital unit.

Declared per supported operating band (in case supported by multiple RATs). | + +NOTE 1: This manufacturer declaration is optional. + +# 5 Performance assessment + +## 5.1 General + +The following information shall be recorded in or annexed to the test report: + +- the primary functions of the radio equipment to be tested during and after the EMC testing; +- the intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment; +- the method to be used to verify that a communications link is established and maintained; +- the user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress; +- the ancillary equipment to be combined with the radio equipment for testing (where applicable); +- the information about ancillary equipment intended to be used with the radio equipment; +- information about the common and/or RAT-specific active RF components and other HW blocks for a communication link in MSR BS or other BS supporting more than one RAT (see declaration DEMC.2); +- information about the common and/or band-specific active RF components and other HW blocks for a communication link in BS capable of multi-band operation (see declaration DEMC.3); +- an exhaustive list of ports, classified as either power or signal/control. Power ports shall further be classified as AC or DC power. + +Performance assessment of a BS with multiple enclosures may be done separately for the BS part with the Radio digital unit and the Radio unit respectively, according to the manufacturer's choice. + +A communication link used by more than one tested RAT or more than one tested operating band, shall be assessed on all tested RATs and operating bands. Communication link(s) and/or radio performance parameters for the RATs and operating bands can during the test be assessed simultaneously or separately for each RAT and band, depending on the test environment capability. + +## 5.2 Assessment of performance in Downlink + +In the immunity tests, the output of the transmitter shall be connected to equipment which meets the requirements for the performance assessment of RAT and bearer used in the immunity tests according to the following: + +- Throughput assessment in TS 38.101-4 [38] in case of NR +- Throughput assessment in TS 36.101 [31] in case of E-UTRA +- BLER assessment in TS 25.101 [29] in case of UTRA FDD +- BLER assessment in TS 25.102 [30] in case of UTRA TDD +- BER assessment in annex A.1 in case of GSM/EDGE +- Throughput assessment in TS 36.101 [31] in case of NB-IoT + +Power control shall be OFF during the immunity testing. + +## 5.3 Assessment of performance in Uplink + +In the immunity tests, the performance in the uplink shall be monitored at a telecommunications port(s) by using suitable test equipment according to the following: + +- The value of the throughput shall be monitored in case of E-UTRA, and/or in case of NR +- The value of the BLER shall be monitored in case of UTRA FDD and UTRA TDD +- The value of the BER shall be monitored in case of GSM/EDGE (see annex A.2) +- The value of the throughput shall be monitored in case of NB-IoT + +## 5.4 Ancillary equipment + +At the manufacturer's discretion the test may be performed on the ancillary equipment separately or on a representative configuration of the combination of radio and ancillary equipment. In each case EUT is tested against all applicable immunity and emission clauses of the present document and in each case, compliance enables the ancillary equipment to be used with different radio equipment. + +# --- 6 Performance criteria + +The test should, where possible, be performed using a bearer with the characteristics of data rate and performance criteria defined for NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT below. If the test is not performed using one of these bearers (for example, if none of them are supported by the BS) the characteristics of the bearer used shall be recorded in the test report. + +## 6.1 Performance criteria for continuous phenomena for BS + +### 6.1.1 E-UTRA performance criteria + +The throughput in table 6.1.1-1 is stated relative to the maximum throughput of the FRC. The maximum throughput for an FRC is equal to the payload size \* the number of uplink subframes per second. + +The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 6.1.1-1 during the test. If the Uplink and Downlink paths are evaluated as a one loop then the criteria is two times the throughput reduction shown in table 6.1.1-1. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained. + +**Table 6.1.1-1: E-UTRA BS Performance criteria for continuous phenomena for BS** + +| E-UTRA channel bandwidth (MHz) | Bearer information data rate | Performance criteria (Note 1, Note 2) | +|--------------------------------|---------------------------------------------------------------------------------|-----------------------------------------| +| 1.4 | FRC A1-1 in Annex A.1 in TS 36.104 [2] | Throughput > 95 %
No loss of service | +| 3 | FRC A1-2 in Annex A.1 in TS 36.104 [2] | | +| 3 | FRC A1-6 in Annex A.1 in TS 36.104 [2] for E-UTRA with NB-IoT in-band operation | | +| 5 | FRC A1-3 in Annex A.1 in TS 36.104 [2] | | +| 5 | FRC A1-7 in Annex A.1 in TS 36.104 [2] for E-UTRA with NB-IoT in-band operation | | +| 10 | FRC A1-3 in Annex A.1 in TS 36.104 [2] (Note 3) | | +| 15 | FRC A1-3 in Annex A.1 in TS 36.104 [2] (Note 3) | | +| 20 | FRC A1-3 in Annex A.1 in TS 36.104 [2] (Note 3) | | + +NOTE 1: The performance criteria, "Throughput > 95 % / No loss of service", applies also if a bearer with another characteristics is used in the test. + +NOTE 2: The performance criteria, "Throughput > 90 % / No loss of service", applies instead if the Uplink and Downlink paths are evaluated as a one loop. + +NOTE 3: This is the information data rate of a single instance of the bearer mapped to 25 resource blocks. The performance criteria shall be met for each consecutive application of a single instance of the bearer mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +### 6.1.2 UTRA performance criteria + +The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 6.1.2-1 during the test. If the Uplink and Downlink paths are evaluated as a one loop, then the criterion is two times the value shown in table 6.1.2-1. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained. + +**Table 6.1.2-1: UTRA BS performance criteria for continuous phenomena for BS** + +| Bearer information data rate | Performance criteria | +|-------------------------------------|----------------------------------------| +| 12.2 kbps | BLER < $10^{-2}$
No loss of service | +| 64 kbps | | +| 144 kbps | | +| 384 kbps | | + +NOTE: The performance criteria, "BLER < $10^{-2}$ / No loss of service", applies also if a bearer with another characteristics is used in the test. + +### 6.1.3 GSM/EDGE performance criteria + +#### 6.1.3.1 GSM/EDGE downlink + +The BER of the downlink shall be assessed during the test according to one of the test methods of Annex A.1. + +If the test method of Annex A.1.1 is used, the measured BER of the class 2 bits of TCH/FS shall not exceed 1,6 % during the test. + +NOTE: This BER is the upper limit in TS 45.008 [32] for RXQUAL = 3. + +If the test method of Annex A.1.2 is used, the value of RXQUAL shall not exceed 3 during the test. + +At the conclusion of the test the EUT shall operate as intended with no loss of user control functions or stored data, and the communication link shall have been maintained. + +#### 6.1.3.2 GSM/EDGE uplink + +The BER of the uplink shall be assessed during the test according to one of the test methods of Annex A.2. + +If the test method of Annex A.2.1 is used, the value of RXQUAL shall not exceed 3 during the test. + +If the test method of Annex A.2.2 is used, the measured BER of the class 2 bits of TCH/FS shall not exceed 1,6 % during the test. + +NOTE: This BER is the upper limit in TS 45.008 [32] for RXQUAL = 3. + +For a base station, the RXQUAL of the uplink shall not exceed three (3) measured during the test sequence. + +At the conclusion of the test the EUT shall operate as intended with no loss of user control functions or stored data, and the communication link shall have been maintained. + +### 6.1.4 NB-IoT performance criteria + +The throughput in table 6.1.4-1 is stated relative to the maximum throughput of the FRC. The Maximum throughput for an FRC equals the Payload size / (Number of Resource Unit \* time to send one Resource Unit). + +The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 6.1.4-1 during the test. If the Uplink and Downlink paths are evaluated as a one loop, then the criterion is two times the throughput reduction shown in table 6.1.4-1. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained. + +**Table 6.1.4-1: NB-IoT BS Performance criteria for continuous phenomena for BS** + +| NB-IoT
Sub-carrier spacing
[kHz] | Reference measurement
channel | Performance criteria
(Note 1, Note 2) | +|-------------------------------------------------|------------------------------------------|--------------------------------------------------| +| 15 | FRC A14-1 in Annex A.14 in TS 36.104 [2] | Throughput > 95 %
No loss of service | +| 3.75 | FRC A14-2 in Annex A.14 in TS 36.104 [2] | | + +NOTE 1: The performance criteria, "Throughput > 95 % / No loss of service", applies also if a bearer with another characteristics is used in the test. + +NOTE 2: The performance criteria, "Throughput > 90 % / No loss of service", applies instead if the Uplink and Downlink paths are evaluated as a one loop. + +### 6.1.5 NR performance criteria + +The throughput in table 6.1.5-1 is stated relative to the maximum throughput of the FRC. The maximum throughput for an FRC is equal to the [payload size \* the number of uplink subframes per second]. + +The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 6.1.5-1 during the test. If the Uplink and Downlink paths are evaluated as a one loop, then the criterion is two times the throughput reduction shown in table 6.1.5-1. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained. + +**Table 6.1.5-1: NR BS performance criteria for continuous phenomena for BS** + +| NR channel bandwidth as defined in TS
38.104 section 5.3.2-1 [35]
(MHz) | Sub-carrier
spacing (kHz) | Bearer information
data rate
(as in TS 38.104 [35],
annex A.1) | Performance
criteria
(Note1, Note 2) | +|----------------------------------------------------------------------------------------|--------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------| +| 5, 10, 15 | 15 | G-FR1-A1-1 | Throughput > 95 %,
No loss of service | +| 10, 15 | 30 | G-FR1-A1-2 | | +| 10, 15 | 60 | G-FR1-A1-3 | | +| 20 to 50 | 15 | G-FR1-A1-4 | | +| 20 to 100 | 30 | G-FR1-A1-5 | | +| 20 to 100 | 60 | G-FR1-A1-6 | | + +NOTE 1: The performance criteria, throughput > 95 %, no loss of service, applies also if a bearer with another characteristics is used in the test. + +NOTE 2: The performance criteria, throughput > 90 %, no loss of service, applies instead if the uplink and downlink paths are evaluated as a one loop. + +## 6.2 Performance criteria for transient phenomena for BS + +At the conclusion of the total test comprising the series of individual exposures the EUT shall operate as intended with no loss of user control functions or stored data, as specified by the manufacturer, and the communication link shall have been maintained. + +The below characteristics should be chosen based on manufacture declaration as defined in related single RAT BS RF testing specification, and are defined as: + +The below characteristics should be chosen based on manufacture declaration and are defined as: + +- The E-UTRA channel bandwidth and bearer information data rate are defined in table 6.1.1-1, based on declaration defined in TS 36.141 [9]. +- The UTRA bearer information data rate are defined in table 6.1.2-1, based on declaration defined in TS 25.141 [7]. + +- The GSM/EDGE the test BER assessment are defined in clause 6.1.3.1 for downlink and clause 6.1.3.2 for uplink, while the criteria is defined in clause 6.2, based on declaration defined in TS 51.021 [10]. +- The NB-IoT sub-carrier spacing and reference measurement channel are defined in table 6.1.4-1, based on declaration defined in TS 36.141 [9]. +- The NR channel bandwidth, sub-carrier spacing and bearer information data rate are defined in table 6.1.5-1, based on declaration defined in TS 38.141-1 [36], and/or TS 38.141-2 [37]. + +## 6.3 Performance criteria for continuous phenomena for Ancillary equipment + +The apparatus shall continue to operate as intended during and after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended. + +## 6.4 Performance criteria for transient phenomena for Ancillary equipment + +The apparatus shall continue to operate as intended after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss. During the test, degradation of performance is however allowed. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended. + +# --- 7 Applicability overview + +## 7.1 Emission + +Table 7.1-1: Emission applicability + +| Phenomenon | Application | Equipment test requirement | | Reference subclause in the present document | Reference standard | +|----------------------------------|----------------------------|----------------------------|---------------------|---------------------------------------------|-------------------------------------------| +| | | BS equipment | Ancillary equipment | | | +| Radiated emission (NOTE) | Enclosure | applicable | | 8.2.1 | ITU-R SM.329 [15] | +| Radiated emission | Enclosure | | applicable | 8.2.2 | CISPR 32 [34] | +| Conducted emission | DC power input/output port | applicable | applicable | 8.3 | CISPR 32 [34] | +| Conducted emission | AC mains input/output port | applicable | applicable | 8.4 | CISPR 32 [34] | +| Harmonic current emissions | AC mains input port | applicable | applicable | 8.5 | IEC 61000-3-2 [19] or IEC 61000-3-12 [20] | +| Voltage fluctuations and flicker | AC mains input port | applicable | applicable | 8.6 | IEC 61000-3-3 [21] or IEC 61000-3-11 [22] | +| Conducted emission | Telecommunication port | applicable | applicable | 8.7 | CISPR 32 [34] | + +NOTE: The radiated emissions requirement for the BS equipment covers radiated emissions in the spurious domain. For GSM/EDGE, it corresponds to the "Radiated spurious emissions" requirement in TS 51.021 [10] for radio aspects. + +## 7.2 Immunity + +**Table 7.2-1: Immunity applicability** + +| Phenomenon | Application | Equipment test requirement | | Reference subclause in the present document | Reference Standard | +|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------|---------------------------------------------|---------------------| +| | | BS equipment | Ancillary equipment | | | +| RF electromagnetic field (80 - 6000 MHz) | Enclosure | applicable | applicable | 9.2 | IEC 61000-4-3 [23] | +| Electrostatic discharge | Enclosure | applicable | applicable | 9.3 | IEC 61000-4-2 [24] | +| Fast transients common mode | Signal, telecommunications and control ports, DC and AC power input ports | applicable | applicable | 9.4 | IEC 61000-4-4 [25] | +| RF common mode 0,15 - 80 MHz | Signal, telecommunications and control ports, DC and AC power input ports | applicable | applicable | 9.5 | IEC 61000-4-6 [26] | +| Voltage dips and interruptions | AC mains power input ports | applicable | applicable | 9.6 | IEC 61000-4-11 [27] | +| Surges, common and differential mode | AC power input ports and telecommunications port | applicable | applicable | 9.7 | IEC 61000-4-5 [28] | + +# 8 Emission + +## 8.1 Test configurations + +This subclause defines the configurations for emission tests as follows: + +- the equipment shall be tested under normal test conditions as specified in the functional standards; +- the test configuration shall be as close to normal intended use as possible; +- if the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports; +- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- the test conditions, test configuration and mode of operation shall be recorded in the test report; +- ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment, Radio Frequency (RF) input/output ports shall be correctly terminated; +- ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in + +order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; + +- the test arrangements for transmitter and receiver clauses of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter clause and receiver clause of the EUT may be carried out simultaneously to reduce test time. + +## 8.2 Radiated emission from Base Station and ancillary equipment + +### 8.2.1 Radiated emission for Base Stations + +This test is applicable to BS, except for BS that are only single-RAT GSM/EDGE capable. This test shall be performed on a representative configuration of the BS. + +For BS that are only single-RAT GSM/EDGE capable, the test method and limits in clause 8 of TS 51.021 [10] apply. + +#### 8.2.1.1 Definition + +This test assesses the ability of BS to limit unwanted emission from the enclosure port. + +#### 8.2.1.2 Test method + +- A test site fulfilling the requirements of ITU-R SM. 329 [15] shall be used. The BS shall be placed on a non-conducting support and shall be operated from a power source via a RF filter to avoid radiation from the power leads. + +Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). At each frequency at which a component is detected, the BS shall be rotated and the height of the test antenna adjusted to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement. The measurement shall be repeated with the test antenna in the orthogonal polarization plane. + +NOTE: Effective radiated power (e.r.p.) refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2,15 dB between e.i.r.p. and e.r.p. + +$$\text{e.r.p. (dBm)} = \text{e.i.r.p. (dBm)} - 2,15 \text{ Ref: ITU-R SM.329 ANNEX 1 [15]}.$$ + +- The BS shall transmit with rated power declared by the manufacturer with all transmitters active. Set the BS to transmit a signal as stated in subclause 4.5. +- The received power shall be measured over the frequency range from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ and from $F_{DL\_high} + \Delta f_{OBUE}$ up to 12.75 GHz. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. Unless otherwise stated, all measurements are done as mean power (RMS). $\Delta f_{OBUE}$ is defined in table 8.2.1.3-2. + +#### 8.2.1.3 Limits + +The frequency boundary and reference bandwidths for the detailed transitions of the limits between the requirements for out of band emissions and spurious emissions are based on ITU-R Recommendations SM.329 [10] and SM.1539 [23]. + +The BS shall meet the limits below: + +**Table 8.2.1.3-1: Limits for radiated emissions from BS** + +| Frequency range | Minimum requirement (e.r.p.)/Reference bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$ | -36 dBm/ 100 kHz | +| $1 \text{ GHz} \leq f < 12.75 \text{ GHz}$ | -30 dBm/ 1MHz | +| $F_{DL\_low} - \Delta f_{OBUE} < f < F_{DL\_high} + \Delta f_{OBUE}$ (NOTE) | Not defined | +| NOTE: For BS capable of multi-band operation, the frequency ranges relating to the RF bandwidths of all supported bands apply. | | + +**Table 8.2.1.3-2: Maximum offset of OBUE outside the downlink operating band** + +| Operating band characteristics | $\Delta f_{OBUE}$ (MHz) | +|---------------------------------------------------------------------|-------------------------| +| $F_{DL\_high} - F_{DL\_low} \leq 200 \text{ MHz}$ | 10 | +| $200 \text{ MHz} < F_{DL\_high} - F_{DL\_low} \leq 900 \text{ MHz}$ | 40 | + +#### 8.2.1.4 Interpretation of the measurement results + +The interpretation of the results recorded in a test report for the radiated emission measurements described in the present document shall be as follows: + +- the measured value related to the corresponding limit will be used to decide whether an equipment meets the requirements of the present document; +- the value of the measurement uncertainty for the measurement of each parameter shall be included in the test report; +- the recorded value of the measurement uncertainty shall be, for each measurement, equal to or lower than the figures in table 8.2.1.4-1 for BS. + +Table 8.2.2 specifies the Maximum measurement uncertainty of the Test System. The Test System shall enable the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated. + +A confidence level of 95% is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment. + +**Table 8.2.1.4-1: Maximum measurement uncertainty (BS)** + +| Parameter | Uncertainty for EUT dimension $\leq 1 \text{ m}$ | Uncertainty for EUT dimension $> 1 \text{ m}$ | +|---------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-----------------------------------------------| +| Effective radiated RF power between 30 MHz to 180 MHz | $\pm 6 \text{ dB}$ | $\pm 6 \text{ dB}$ | +| Effective radiated RF power between 180 MHz to 4 GHz | $\pm 4 \text{ dB}$ | $\pm 6 \text{ dB}$ | +| Effective radiated RF power between 4 GHz to 12,75 GHz | $\pm 6 \text{ dB}$ | $\pm 9 \text{ dB}$ (NOTE) | +| NOTE: This value may be reduced to $\pm 6 \text{ dB}$ when further information on the potential radiation characteristic of the EUT is available. | | | + +NOTE: If the Test System for a test is known to have a measurement uncertainty greater than that specified in table 8.2.2, this equipment can still be used, provided that an adjustment is made follows: + +Any additional uncertainty in the Test System over and above that specified in table 8.2.1.4-1 is used to tighten the Test Requirements - making the test harder to pass. This procedure will ensure that a Test System not compliant with table 8.2.1.4-1 2 does not increase the probability of passing a EUT that would otherwise have failed a test if a Test System compliant with table 8.2.1.4-1 had been used. + +### 8.2.2 Radiated emission, ancillary equipment + +This test is applicable to ancillary equipment. This test shall be performed on a representative configuration of the ancillary equipment. + +#### 8.2.2.1 Definition + +This test assesses the ability of ancillary equipment to limit unwanted emission from the enclosure port. + +#### 8.2.2.2 Test method + +The test method shall be in accordance with CISPR 32 [34]. + +#### 8.2.2.3 Limits + +The ancillary equipment shall meet the limits according to CISPR 32 [34] table A.4 and table A.5. + +For the referred limit values, the following shall apply: + +- Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. +- Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +**Table 8.2.2.3-1: Void** + +**Table 8.2.2.3-2: Void** + +Alternatively, for *ancillary equipment* intended to be used in telecommunication centres only, the class A limits given in CISPR 32 [34], annex A, table A.2 and table A.3 may be used. + +## 8.3 Conducted emission DC power input/output port + +This test is applicable to equipment which may have DC cables longer than 3 m. + +If the DC power cable of the radio equipment is intended to be less than 3 m in length and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in subclause 8.4. + +This test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment. + +### 8.3.1 Definition + +This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the DC power input/output ports. + +### 8.3.2 Test method + +The test method shall be in accordance with CISPR 32 [34] and the Artificial Mains Network (AMN) shall be connected to a DC power source. + +In the case of DC output ports, the ports shall be connected via an AMN to a load drawing the rated current of the source. + +A measuring receiver shall be connected to each AMN measurement port in turn and the conducted emission recorded. + +The equipment shall be installed with a ground plane as defined in CISPR 32 [34]. The reference earth point of the AMNs shall be connected to the reference ground plane with a conductor as short as possible. + +The measurement receiver shall be in accordance with the requirements of CISPR 32 [34]. + +### 8.3.3 Limits + +The equipment shall meet the limits according to CISPR 32 [11] table A.9, which are defined for average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +Where there is a step in the referred limit values, the lower value shall be applied at the transition frequency. + +**Table 8.3.3-1: Void** + +## 8.4 Conducted emissions, AC mains power input/output port + +This test is applicable to equipment powered by the AC mains. + +This test is not applicable to AC output ports which are connected directly (or via a circuit breaker) to the AC power port of the EUT. + +This test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment. + +### 8.4.1 Definition + +This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the AC mains power input/output ports. + +### 8.4.2 Test method + +The test method shall be in accordance with CISPR 32 [34]. + +### 8.4.3 Limits + +The equipment shall meet the limits according to CISPR 32 [11] table A.10, which are defined the average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +For the referred limit values following shall apply: + +- Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. +- Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +**Table 8.4.3-1: Void** + +Alternatively, for equipment intended to be used in telecommunication centres the limits given in CISPR 32 [11] table A.9 shall be used. + +**Table 8.4.3-2: Void** + +## 8.5 Harmonic current emissions (AC mains input port) + +The requirements of IEC 61000-3-2 [19] for harmonic current emission apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-12 [20] applies. + +## 8.6 Voltage fluctuations and flicker (AC mains input port) + +The requirements of IEC 61000-3-3 [21] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-12 [20] applies. + +## 8.7 Telecommunication ports + +This test is applicable for radio equipment and/or ancillary equipment for fixed use which have telecommunication ports. + +This test shall be performed on a representative configuration of radio equipment, the associated ancillary equipment, or a representative configuration of the combination of radio and ancillary equipment. + +### 8.7.1 Definition + +This test assesses the EUT unwanted emission present at the telecommunication ports. + +### 8.7.2 Test method + +The test method shall be in accordance with CISPR 32 [34]. + +The measurement frequency range extends from 150 kHz to 30 MHz. + +### 8.7.3 Limits + +The telecommunication ports shall meet the limits according to CISPR 32 [34] table A.12, clause A12.2. + +For the referred limit values, following shall apply: + +- Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. +- Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +#### Table 8.7.3-1: Void + +Alternatively, for equipment intended to be used in telecommunication centres only, the limits given in CISPR 32 [11] table A.11 clause A11.2 shall be used. + +#### Table 8.7.3-2: Void + +# --- 9 Immunity + +## 9.1 Test configurations + +This subclause defines the configurations for immunity tests as follows: + +- the equipment shall be tested under normal test conditions as specified in the functional standards; +- the test configuration shall be as close to normal intended use as possible; +- if the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports; +- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- the test conditions, test configuration and mode of operation shall be recorded in the test report; +- ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment, Radio Frequency (RF) input/output ports shall be correctly terminated; + +- ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- Immunity tests on the entire base station shall be performed by establishing communication links at the radio interface (e.g. with the mobile simulator) and the S1/Iub/ Abis interface (e.g. with an RNC/EPC/BSC simulator) and evaluating the BLER/throughput/BER (see Figure 9.1-1); +- Immunity tests shall be performed on both the Uplink and Downlink paths. The tests shall also include both the radio interface and the S1/Iub/ Abis interface. BLER/throughput/BER evaluation may be carried out at either interface, where appropriate, and the measurements for the Uplink and Downlink paths may be carried out as a single path looped at either the radio interface or S1/Iub/ Abis interface. In case of looping is used care have to be taken that the BLER/throughput/BER information doesn't change due to looping. +- For BS capable of multi-RAT and/or multi-band operation, communication links shall be established in such a way that all tested RATs and operating band(s) are activated during the test according to the applicable test configurations in subclause 4.5. Performance assessment may be done separately for each tested RAT and/or operating band. + +![Figure 9.1-1: Communication link set up for BS immunity measurement. The diagram shows a 'Mobile simulator' box on the left connected to a 'Base station' box in the center. The 'Base station' box contains 'TX' (transmitter), 'RX 1', 'RX 2', and '(terminated)'. Arrows indicate bidirectional communication between the 'Mobile simulator' and the 'Base station'. The 'Base station' is also connected to an 'EPC/RNC/BSC simulator' box on the right, with bidirectional arrows indicating communication links.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` + +graph LR + MS[Mobile simulator] <--> BS[Base station +TX +RX 1 +RX 2 +(terminated)] + BS <--> EPC[EPC/RNC/BSC simulator] + +``` + +Figure 9.1-1: Communication link set up for BS immunity measurement. The diagram shows a 'Mobile simulator' box on the left connected to a 'Base station' box in the center. The 'Base station' box contains 'TX' (transmitter), 'RX 1', 'RX 2', and '(terminated)'. Arrows indicate bidirectional communication between the 'Mobile simulator' and the 'Base station'. The 'Base station' is also connected to an 'EPC/RNC/BSC simulator' box on the right, with bidirectional arrows indicating communication links. + +Figure 9.1-1: Communication link set up for BS immunity measurement + +## 9.2 RF electromagnetic field (80 MHz - 6000 MHz) + +The test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment. + +### 9.2.1 Definition + +This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. + +### 9.2.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-3 [23], which specifies test methodology based on anechoic chamber. The use of reverberation chamber test method according to IEC 61000-4-21 [40], clause 6.1 and Annex D as alternative method is allowed. + +The following requirements shall apply: + +- the test level shall be 3 V/m amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- the stepped frequency increments shall be 1 % of the momentary frequency; +- the test shall be performed over the frequency range 80 MHz - 6000 MHz with the exception of the exclusion band for receivers (see subclause 4.4); +- responses in stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see subclause 4.3; + +- the frequencies selected during the test shall be recorded in the test report. + +### 9.2.3 Performance criteria + +#### Base station: + +The performance criteria of subclause 6.1 shall apply. + +#### Ancillary equipment: + +The performance criteria of subclause 6.3 shall apply. + +## 9.3 Electrostatic discharge + +The test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment. + +### 9.3.1 Definition + +This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the event of an electrostatic discharge. + +### 9.3.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-2 [24]: + +- for contact discharge, the equipment shall pass at $\pm 4$ kV; +- for air discharge shall pass at $\pm 8$ kV; +- electrostatic discharge shall be applied to all exposed surfaces of the EUT except where the user documentation specially indicates a requirement for appropriate protective measures. + +NOTE: Ensure that the EUT is fully discharged between each ESD exposure. + +### 9.3.3 Performance criteria + +#### Base station: + +The performance criteria of subclause 6.2 shall apply. + +#### Ancillary equipment: + +The performance criteria of subclause 6.4 shall apply. + +## 9.4 Fast transients common mode + +The test shall be performed on AC mains power input ports. + +This test shall be performed on signal ports, telecommunication ports, control ports and DC power input/output ports if the cables may be longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares in DEMC.1 (see table 4.6-1) that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment. + +### 9.4.1 Definition + +This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the event of fast transients present on one of the input/output ports. + +### 9.4.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-4 [25]: + +- the test level for signal ports, telecommunication ports and control ports shall be 0,5 kV open circuit voltage as given in IEC 61000-4-4 [25]; +- the test level for DC power input/output ports shall be 0,5 kV open circuit voltage as given in IEC 61000-4-4 [25]; +- the test level for AC mains power input ports shall be 1 kV open circuit voltage as given in IEC 61000-4-4 [25]. + +For AC and DC power input ports the transients shall be applied (in parallel) to all the conductors in the cable with reference to the cabinet reference earth (true common mode) and the source impedance shall be 50 Ω. + +### 9.4.3 Performance criteria + +#### Base station: + +The performance criteria of subclause 6.2 shall apply. + +#### Ancillary equipment: + +The performance criteria of subclause 6.4 shall apply. + +## 9.5 RF common mode (0,15 MHz - 80 MHz) + +The test shall be performed on AC mains power input/output ports. + +This test shall be performed on signal ports, telecommunication ports, control and DC power input/output ports, which may have cables longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares in DEMC.1 (see table 4.6-1) that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment. + +NOTE: This test can also be performed using the clamp injection method, where appropriate, see IEC 61000-4-6 [26]. + +### 9.5.1 Definition + +This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic disturbance. + +### 9.5.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-6 [26]: + +- the test signal shall be amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- the stepped frequency increments shall be 50 kHz in the frequency range 150 kHz to 5 MHz and 1% frequency increment of the momentary frequency in the frequency range 5 MHz to 80 MHz; + +- the test level shall be severity level 2 as given in IEC 61000-4-6 [26] corresponding to 3 V rms, at a transfer impedance of 150 $\Omega$ ; +- the test shall be performed over the frequency range 150 kHz - 80 MHz; +- the injection method to be used shall be selected according to the basic standard IEC 61000-4-6 [26]; +- responses of stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see subclause 4.3; +- the frequencies of the immunity test signal selected and used during the test shall be recorded in the test report. + +### 9.5.3 Performance criteria + +#### Base station: + +The performance criteria of subclause 6.1 shall apply. + +#### Ancillary equipment: + +The performance criteria of subclause 6.3 shall apply. + +## 9.6 Voltage dips and interruptions + +The tests shall be performed on AC mains power input ports. + +These tests shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment. + +### 9.6.1 Definition + +These tests assess the ability of radio equipment and ancillary equipment to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports. + +### 9.6.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-11 [27], where the test levels shall be: + +- Voltage dip: 0 % residual voltage for 0.5 cycle; +- Voltage dip: 0 % residual voltage for 1 cycle; +- Voltage dip: 70 % residual voltage for 25/30 cycles (at 50/60 Hz); +- Voltage interruption: 0 % residual voltage for 250/300 cycles (at 50/60 Hz). + +### 9.6.3 Performance criteria + +For a 0 % residual voltage dip test, the performance criteria for transient phenomena shall be applied: + +- Criteria 6.2 for base station +- Criteria 6.4 for ancillary equipment + +For a 70% residual voltage dip test and for voltage interruption test, the following applies: + +1. In the case where the equipment is fitted with or connected to a battery back-up, the following performance criteria shall be applied: + - Criteria 6.2 for base station + - Criteria 6.4 for ancillary equipment + +2. In the case where the equipment is powered solely from the AC mains supply (without the use of a parallel battery back-up) volatile user data may have been lost and if applicable the communication link need not to be maintained and lost functions should be recoverable by user or operator: + - No unintentional responses shall occur at the end of the test, when the voltage is restored to nominal + - In the event of loss of communications link or in the event of loss of user data, this fact shall be recorded in the test report + +## 9.7 Surges, common and differential mode + +The tests shall be performed on AC mains power input ports. + +This test shall be additionally performed on telecommunication ports. + +These tests shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment. + +### 9.7.1 Definition + +These tests assess the ability of radio equipment and ancillary equipment to operate as intended in the event of surges being present at the AC mains power input ports and telecommunication ports. + +### 9.7.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-5 [28]. + +The requirements and evaluation of test results given in subclause 9.7.2.1 (telecommunication ports, outdoor cables), subclause 9.7.2.2 (telecommunication ports, indoor cables) and subclause 9.7.2.3 (AC power ports) shall apply, but no test shall be required where normal functioning cannot be achieved, because of the impact of the CDN on the EUT. + +#### 9.7.2.1 Test method for telecommunication ports directly connected to outdoor cables + +The test level for telecommunications ports, intended to be directly connected to the telecommunications network via outdoor cables, shall be 1 kV line to ground as given in IEC 61000-4-5 [28]. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [28]. + +The test generator shall provide the 1,2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [28]. + +#### 9.7.2.2 Test method for telecommunication ports connected to indoor cables + +The test level for telecommunication ports, intended to be connected to indoor cables (longer than 10 m) shall be 0,5 kV line to ground. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [28]. + +The test generator shall provide the 1,2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [28]. + +#### 9.7.2.3 Test method for AC power ports + +The test level for AC power input ports shall be 2 kV line to ground, and 1 kV line to line, with the output impedance of the surge generator as given in IEC 61000-4-5 [28]. + +In telecommunication centres 1 kV line to ground and 0,5 kV line to line shall be used. + +The test generator shall provide the 1,2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [28]. + +### 9.7.3 Performance criteria + +**Base station:** + +The performance criteria of subclause 6.2 shall apply. + +#### **Ancillary equipment:** + +The performance criteria of subclause 6.4 shall apply. + +# --- Annex A (normative): BER assessment for GSM/EDGE + +## A.1 Assessment of BER at the output of a transmitter + +The BER at the output of the transmitter may be assessed using either of the techniques described below. + +### A.1.1 Assessment of BER using static layer 1 functions + +The transmitter under test shall be operated according to the test case of TS 51.021 [10], subclause 6.1.2. + +The bit sequence from the output of the transmitter shall be monitored by the test system according to the test case of TS 51.021 [10], subclause 7.1.2, and the BER of the class 2 bits for TCH/FS assessed. The BER shall not exceed the values specified in subclause 6.1 of the present document. + +If the EUT does not support TCH/FS, the manufacturer shall declare the logical channel for which the performance shall be assessed, and the corresponding performance criteria. + +### A.1.2 Assessment of BER using RXQUAL + +The output of the transmitter shall be connected to an equipment which meets the requirements of TS 51.010-1 [33] for the assessment of RXQUAL. The level of the signal supplied to the equipment should be within the range for which the assessment of RXQUAL is not impaired. The RXQUAL shall be monitored during the test. The RXQUAL shall not exceed the values specified in subclause 6.1 of the present document. + +NOTE: This equipment can be a GSM mobile station with suitable provision for the monitoring of RXQUAL. + +## --- A.2 Assessment of BER at the output of a receiver + +The BER at the output of the receiver may be assessed using either of the techniques described below. + +### A.2.1 Assessment of BER using RXQUAL + +The value of the RXQUAL reported by the BTS or BSS shall be monitored using suitable test equipment. + +### A.2.2 Assessment of BER using reported BER + +The BER of the class 2 bits at the output of the receiver shall be assessed using suitable test equipment. + +If the EUT does not support TCH/FS, the manufacturer shall declare the logical channel for which the performance shall be assessed, and the corresponding performance criteria. + +NOTE: This can be performed by a "test loopback" which uses the transmitter of the BTS to return the data which has been decoded by the receiver back to the test equipment which generated the bit sequence. For immunity tests of signal ports, the "test loopback" includes an external connection between signal ports. + +# Annex B (normative): Simplified immunity testing + +## B.1 Applicability + +Simplified immunity testing applies, per operating band, only to the BS which satisfies both of the following conditions: + +- Radio unit employs common active RF components for supported RATs, as described in DEMC.2. +- Radio digital unit employs common active components for supported RATs, as described in DEMC.4. + +Note: If the above condition is not met, all applicable test configurations in clause 4.5 apply for testing. + +## B.2 Capability Sets for simplified immunity testing + +The set of RATs which are considered sufficient for the immunity testing purposes depends on the BS hardware capabilities declared by the manufacturer in DEMC.2 and DEMC.4. + +The following RAT combinations were identified as candidates for the immunity testing simplification: + +- For MSR BS declared to support E-UTRA and UTRA, UTRA does not have to be configured. +- For MSR BS declared to support NR and UTRA, UTRA does not have to be configured. +- For MSR BS declared to support NB-IoT and GSM, GSM needs not to be configured. + +The above RAT combinations were further translated into the Capability Sets in tables below. + +For single-band multi-RAT capable MSR BS, the sufficient CSs in tables B.2-1 to B.2-4 may be followed, instead of the declared CSs in tables 4.5-1 to 4.5-1c, respectively. + +The test configurations (TCx) are associated to the sufficient CSs according to tables 4.5-1, 4.5-1a, 4.5-1b and 4.5-1c. + +Example: A BS declared to support CS9 (corresponding to TC9 in table 4.5-1a) in table B.2-2, will be tested using TC8 (corresponding to CS8 in table 4.5-2). + +**Table B.2-1: Declared and sufficient CSs for testing** + +| Declared Capability Set | CS3 (U, E, IoT NI/NG) | CS4 (G, U) | CS5 (G, E, IoT NI/NG) | CS6 (G, U, E) | CS7 (G, U, E, IoT NI/NG) | +|---------------------------|-----------------------|------------|--------------------------------------|---------------|--------------------------------------| +| Sufficient CS for testing | CS2 (E, IoT NI/NG) | CS4 (G, U) | CS2 NOTE 1 (E, IoT NI/NG) | CS5 (G, E) | CS2 NOTE 1 (E, IoT NI/NG) | +| | | | CS5 (G, E) | | CS5 (G, E) | + +NOTE 1: either NB-IoT in-band or guard band is supported, otherwise, no EMC enhancement for GSM for the declared CS. +NOTE 2: G, U, E and IoT NI/NG stand for GSM, UTRA, E-UTRA and NB-IoT in-band/guard band. + +**Table B.2-2: Declared and sufficient CSs for testing** + +| Declared Capability Set | CS9 (G, IoT SA) | CS10 (U, IoT SA) | CS11 (E, IoT SA) | CS12 (G, U, IoT SA) | CS13 (G, E, IoT SA) | +|-------------------------------------------------------------------------------|-----------------|------------------|------------------|---------------------|---------------------| +| Sufficient CS for testing | CS8 (IoT SA) | CS10 (U, IoT SA) | CS11 (E, IoT SA) | CS10 (U, IoT SA) | CS11 (E, IoT SA) | +| NOTE 1: G, U, E and IoT SA stand for GSM, UTRA, E-UTRA and NB-IoT standalone. | | | | | | + +**Table B.2-3: Declared and sufficient CSs for testing** + +| Declared Capability Set | CS14 (U, E, IoT SA) | CS15 (G, U, E, IoT SA) | CS16 (N, E, IoT NI/NG) | CS17 (N, IoT SA, E, IoT NI/NG) | +|----------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------|------------------------|--------------------------------| +| Sufficient CS for testing | CS11 (E, IoT SA) | CS11 (E, IoT SA) | CS16 (N, E, IoT NI/NG) | CS17 (N, IoT SA, E, IoT NI/NG) | +| NOTE 1: G, U, E, IoT NI/NG, IoT SA and N stand for GSM, UTRA, E-UTRA, NB-IoT in-band/guard band, NB IoT standalone and NR. | | | | | + +**Table B.2-4: Declared and sufficient CSs for testing** + +| Declared Capability Set | CS18 (G, N, E, IoT NI/NG) | CS19 (U, N, E, IoT NI/NG) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------------------| +| Sufficient CS for testing | CS16 NOTE 1 (N, E, IoT NI/NG) | CS16 (N, E, IoT NI/NG) | +| | CS18 (G, N, E) | | +| NOTE 1: either NB-IoT in-band or guard band is supported, otherwise, no EMC enhancement for GSM for the declared CS.
NOTE 2: G, U, E, IoT NI/NG and N stand for GSM, UTRA, E-UTRA, NB-IoT in-band/guard band and NR. | | | + +For multi-band multi-RAT capable MSR BS, the rationale described above applies for each band. + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2010-02 | R4#54 | R4-100572 | | | | Specification skeleton | 0.0.1 | +| 2010-04 | R4#55 | R4-101577 | | | | E-mail approved Text Proposals after RAN4 AH#2:
R4-101189, "TS 37.113: TP on References, Definitions, symbols and abbreviations (TS ch 2 and 3) "
R4-101190, "TS 37.113: TP on Test conditions (TS ch 4)"
R4-101191, "TS 37.113: TP on Performance assessment (TS ch 5)"
R4-101192, "TS 37.113: TP on Performance Criteria (TS ch 6)"
R4-101193, "TS 37.113: TP on Applicability overview (TS ch 7)"
R4-101194, "TS 37.113: TP on Emission (TS ch 8)"
R4-101195, "TS 37.113: TP on Immunity (TS ch 9)" | 0.1.0 | +| 2010-06 | RP#48 | RP-100581 | | | | Presentation to TSG RAN. | 1.0.0 | +| 2010-06 | RP#48 | RP-100581 | | | | Approval by TSG RAN. | 9.0.0 | +| 2010-09 | RP-49 | RP-100923 | 002 | 1 | | EMC updates for multi-RAT operation | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 003 | | | Clarification of radiated emissions requirement | 9.1.0 | +| 2010-09 | RP-49 | RP-100927 | 001 | | | CR LTE_TDD_2600_US spectrum band definition additions for MSR BS to TS 37.113 | 10.0.0 | +| 2010-12 | RP-50 | RP-101345 | 010 | | | Band XII/12 frequency range | 10.1.0 | +| 2010-12 | RP-50 | RP-101346 | 006 | | | MSR test configuration for EMC | 10.1.0 | +| 2010-12 | RP-50 | RP-101346 | 008 | | | Correction of CR implementation in clause 6.2 of TS 37.113 | 10.1.0 | +| 2010-12 | RP-50 | RP-101356 | 004 | 1 | | Band 42 and 43 parameters for UMTS/LTE 3500 (TDD) for TS 37.113 | 10.1.0 | +| 2011-06 | RP-52 | RP-110812 | 014 | 1 | | Add 2GHz S-Band (Band 23) in 37.113 | 10.2.0 | +| 2011-09 | RP-53 | RP-111255 | 017 | | | Add Band 22/XXII for LTE/UMTS 3500 (FDD) to TS 37.113 | 10.3.0 | +| 2011-12 | RP-54 | RP-111734 | 018 | 1 | | Removal of references to operating bands i) and h) | 10.4.0 | +| 2011-12 | RP-54 | RP-111735 | 019 | 1 | | EMC requirements for MSR-NC | 10.4.0 | +| 2012-03 | RP-55 | RP-120305 | 020 | | | Add Extending 850 MHz Upper Band (814 - 849 MHz) to TS37.113 | 11.0.0 | +| 2012-06 | RP-56 | RP-120793 | 023 | | | Introduction of APAC700(FDD) into TS 37.113 | 11.1.0 | +| 2012-06 | RP-56 | RP-120793 | 024 | | | Introduction of APAC700(TDD) into TS 37.113 | 11.1.0 | +| 2012-06 | RP-56 | RP-120791 | 025 | | | Introduction of e850_LB (Band 27) to TS 37.113 | 11.1.0 | +| 2013-06 | RP-60 | RP-130792 | 026 | | | Introduction of Band 30 in TS 37.113 | 12.0.0 | +| 2013-06 | RP-60 | RP-130790 | 027 | | | Introduction of LTE 450 into TS 37.113 | 12.0.0 | +| 2014-06 | RP-64 | RP-140914 | 033 | | | Introduction of band 29 in TS 37.113 | 12.1.0 | +| 2014-06 | RP-64 | RP-140926 | 029 | | | Introduction of Band 32/XXXII in TS 37.113 | 12.1.0 | +| 2014-09 | RP-65 | RP-141562 | 0036 | 1 | | Update of definitions to support supplemental DL in TS37.113 | 12.2.0 | +| 2014-12 | RP-66 | RP-142146 | 038 | | | EMC testing of multi-band operation for MSR BS | 12.3.0 | +| 2015-12 | RP-70 | RP-152171 | 0039 | | | Introduction of Band 65 | 13.0.0 | +| 2015-12 | RP-70 | RP-152172 | 0040 | | | Introduction of Band 66 | 13.0.0 | +| 2015-12 | RP-70 | RP-152157 | 0041 | | | Introduction of Band 67 | 13.0.0 | +| 2015-12 | RP-70 | RP-152173 | 0042 | | | Introduction of 1447-1467MHz Band into 37.113 | 13.0.0 | +| 2016-03 | RP-71 | RP-160483 | 0043 | | B | Introduction of Band 68 into 37.113 | 13.1.0 | +| 2016-03 | RP-71 | RP-160490 | 0044 | | F | Introduction of Band 46 in TS 37.113 | 13.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2016-06 | RP-72 | RP-161142 | 0047 | - | F | Clarification in EMC environmental conditions references | 13.2.0 | +| 2016-06 | RP-72 | RP-161141 | 0052 | - | F | Necessary updates in 37.113 on receiver exclusion bands | 13.2.0 | +| 2016-06 | RP-72 | RP-161125 | 0045 | - | B | Introduction of Band 70 to 37.113 | 14.0.0 | +| 2016-06 | RP-72 | RP-161124 | 0048 | - | B | CR to 37.113 on receiver exclusion band update due to Band 69 | 14.0.0 | +| 2016-12 | RP-74 | RP-162379 | 0054 | - | A | CR to TS 37.113 – Introduction of NB-IoT | 14.1.0 | +| 2016-12 | RP-74 | RP-162405 | 0055 | - | B | Introduction of Band 48 | 14.1.0 | +| 2017-06 | RP-76 | RP-171285 | 0068 | - | A | CR on eLAA BS for TS 37.113 | 14.2.0 | +| 2017-09 | RP-77 | RP-171948 | 0070 | - | B | Introduction of the FDD L-band (Band 74) into TS 37.113 | 15.0.0 | +| 2017-09 | RP-77 | RP-171952 | 0071 | - | B | CR to 37.113: Introduction of Band 71 | 15.0.0 | +| 2017-09 | RP-77 | RP-171950 | 0073 | - | B | CR to 37.113: Introduction of B75 and B76 | 15.0.0 | +| 2017-09 | RP-77 | RP-171946 | 0074 | - | B | Introduction of Band 72 into TS37.113 | 15.0.0 | +| 2017-09 | RP-77 | RP-171949 | 0075 | 1 | B | Introduction of TDD L-band into TS 37.113 | 15.0.0 | +| 2017-12 | RAN#78 | RP-172593 | 0076 | - | B | Introduction of Band 73 into TS 37.113 | 15.1.0 | +| 2018-03 | RAN#79 | RP-180279 | 0078 | - | B | CR to 37.113: Introduction of Band 85 | 15.2.0 | +| 2018-03 | RAN#79 | RP-180282 | 0079 | 1 | F | CR to TS 37.113: correction of the CISPR reference and ESD levels | 15.2.0 | +| 2018-03 | RAN#79 | RP-180278 | 0080 | - | B | Introduction of TDD 3.3-3.4GHz band (band 52) | 15.2.0 | +| 2018-06 | RAN#80 | RP-181075 | 0082 | 1 | B | CR to TS 37.113 (MSR EMC): NR EMC Core Requirements updates | 15.3.0 | +| 2018-09 | RAN#81 | RP-181896 | 0084 | 1 | F | CR to TS 37.113: correction of the exclusion band for BS radiated emission test (8.2.1) | 15.4.0 | +| 2018-09 | RAN#81 | RP-181896 | 0085 | - | F | CR to TS 37.113: CISPR32 requirements tables correction | 15.4.0 | +| 2018-12 | RAN#82 | RP-182362 | 0088 | 1 | B | Update the title to add NR of TS 37.113 | 15.5.0 | +| 2018-12 | RAN#82 | RP-182361 | 0089 | 1 | F | CR to TS 37.113 (subclause 2 and 8.4.2 ) | 15.5.0 | +| 2018-12 | RAN#82 | RP-182362 | 0092 | - | B | CR to TS 37.113: introduction of the NR to MSR EMC specification | 15.5.0 | +| 2019-06 | RAN#84 | RP-191236 | 0094 | 1 | F | CR to TS 37.113 subclause 4.5 | 15.6.0 | +| 2019-09 | RAN#85 | RP-192019 | 0095 | 1 | F | CR to TS 37.113 Correction on CISPR 16-1-1 for DC conducted Emission(clause 7.1 and subclause 8.3.2 ) | 15.7.0 | +| 2019-09 | RAN#85 | RP-192019 | 0096 | - | F | CR to TS 37.113 Correction on NR performance criteria(subclause 6.1.5 ) | 15.7.0 | +| 2019-09 | RAN#85 | RP-192019 | 0097 | - | F | CR to TS 37.113 Correction on surge test level for outdoor telecommunication ports(subclause 9.7.2.1 ) | 15.7.0 | +| 2019-09 | RAN#85 | RP-192019 | 0098 | - | F | CR to TS 37.113 subclause 4.5
- Implementation comment: The proposed changes in this CR are already captured in the latest version. | 15.7.0 | +| 2019-09 | RAN#85 | RP-192046 | 0100 | 1 | F | CR to 37.113 Editorial Corrections | 15.7.0 | +| 2019-12 | RAN#86 | RP-193002 | 0105 | - | F | CR to TS 37.113 Correction on definitions subclause 3.1 | 15.8.0 | +| 2019-12 | RAN#86 | RP-193002 | 0106 | - | F | CR to TS 37.113 Correction on radiated emission subclause 8.2 | 15.8.0 | +| 2019-12 | RAN#86 | RP-193002 | 0107 | - | F | CR to TS 37.113 Correction on transient phenomena performance criteria subclause6.2 | 15.8.0 | +| 2020-06 | RAN#88 | RP-200984 | 0109 | 1 | F | Draft CR to 37.113 Introducing Reverberation Chamber | 15.9.0 | +| 2020-06 | RAN#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2020-12 | RAN#90 | RP-202489 | 0111 | 1 | A | CR to TS 37.113 on Voltage dips and interruptions, Release 16 | 16.1.0 | +| 2021-06 | RAN#92 | RP-211086 | 0113 | - | A | CR to TS 37.113: Radiated emission, ancillary equipment | 16.2.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | SA#95 | | | | | Update to Rel-17 version (MCC) | 17.0.0 | +| 2023-03 | RAN#99 | RP-230502 | 0118 | | A | CR to TS 37.113 MSR base station test configuration R17 | 17.1.0 | +| 2023-03 | RAN#99 | RP-230505 | 0121 | | A | TS 37.113: Corrections in clause 9 Immunity | 17.1.0 | +| 2023-06 | RAN#100 | RP-231358 | 0123 | 1 | F | CR on TS 37.113 MSR base station test configuration and performance criteria R17 | 17.2.0 | +| 2023-12 | RAN#102 | RP-233334 | 0133 | | A | CR to TS 37.113 on adding link between telecommunication port and wired network port | 17.3.0 | +| 2023-12 | RAN#102 | RP-233330 | 0136 | | A | [RnImp9-RFmulti, TE15] CR to TS 37.113: Test configurations correction for CS7, Rel-17 | 17.3.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37114/raw.md b/marked/Rel-18/37_series/37114/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..31bc5dfbf3aa6ea49128563fe58bae1b557fce67 --- /dev/null +++ b/marked/Rel-18/37_series/37114/raw.md @@ -0,0 +1,979 @@ + + +# 3GPP TS 37.114 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Active Antenna System (AAS) Base Station (BS) Electromagnetic Compatibility (EMC) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Symbols..... | 11 | +| 3.3 Abbreviations ..... | 11 | +| 4 Test conditions ..... | 12 | +| 4.1 Exclusion bands..... | 13 | +| 4.1.1 Transmitter exclusion band ..... | 13 | +| 4.1.2 Receiver exclusion band..... | 13 | +| 4.2 Arrangements for establishing a communication link..... | 14 | +| 4.3 Narrow band responses on receivers..... | 14 | +| 4.4 BS test configurations ..... | 14 | +| 4.5 Manufacturer declarations..... | 18 | +| 5 Performance assessment ..... | 18 | +| 5.1 General ..... | 18 | +| 5.2 Assessment of performance in Downlink ..... | 19 | +| 5.3 Assessment of performance in Uplink ..... | 19 | +| 6 Performance criteria..... | 19 | +| 7 Applicability overview..... | 20 | +| 7.1 Emission..... | 20 | +| 7.2 Immunity ..... | 20 | +| 8 Emission..... | 20 | +| 8.1 Test configurations..... | 20 | +| 8.2 Radiated emission from base station..... | 21 | +| 8.2.1 Radiated emission, hybrid AAS BS ..... | 21 | +| 8.2.2 Radiated emission, OTA AAS BS..... | 21 | +| 8.3 Conducted emissions, DC power input/output port ..... | 22 | +| 8.4 Conducted emissions, AC mains power input/output port..... | 22 | +| 8.5 Harmonic current emissions (AC mains input port) ..... | 22 | +| 8.6 Voltage fluctuations and flicker (AC mains input port)..... | 22 | +| 8.7 Conducted emissions, telecommunication ports ..... | 22 | +| 9 Immunity ..... | 23 | +| 9.1 Test configurations..... | 23 | +| 9.2 RF electromagnetic field (80 MHz - 6000 MHz)..... | 24 | +| 9.2.1 RF electromagnetic field, hybrid AAS BS ..... | 24 | +| 9.2.2 RF electromagnetic field, OTA AAS BS ..... | 24 | +| 9.3 Electrostatic discharge..... | 25 | +| 9.4 Fast transients common mode..... | 25 | +| 9.5 RF common mode (0.15 MHz - 80 MHz)..... | 26 | +| 9.6 Voltage dips and interruptions ..... | 26 | +| 9.7 Surges, common and differential mode..... | 26 | +| Annex A (normative): Simplified immunity testing..... | 27 | +| A.1 Applicability..... | 27 | +| A.2 Capability Sets for simplified immunity testing ..... | 27 | +| Annex B (informative): Change history ..... | 28 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document covers the assessment of UTRA TDD, UTRA FDD, E-UTRA, NR and Multi-Standard Radio (MSR) Active Antenna Systems Base Stations in respect of Electromagnetic Compatibility (EMC). + +NOTE 1: Whenever the AAS BS in *single RAT UTRA operation*, or AAS BS in *MSR operation* using UTRA is referred in this specification, UTRA TDD and UTRA FDD shall be considered, unless otherwise stated. + +NOTE 2: For NR, scope of this specification is limited to *BS type 1-H* and *BS type 1-O*. For EMC requirements of the MSR BS for *BS type 1-C*, refer to TS 37.113 [4]. + +The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations in the following categories: + +- Active Antenna System Base Station for UTRA TDD, UTRA FDD, E-UTRA, NR and MSR meeting the conducted requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-1 [3], +- Active Antenna System Base Station for UTRA FDD, E-UTRA, NR and MSR meeting the OTA requirements of 3TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-2 [10]. + +Technical requirements related to the TAB connector are not included in the present document. These are found in the relevant product standards [2, 3, 10]. + +The present document does not cover ancillary equipment requirements, where ancillary equipment is not incorporated in the radio equipment and can be assessed on a stand-alone basis, as declared by the manufacturer. Ancillary equipment EMC requirements are still applicable to the AAS BS and are covered by other EMC specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30]. + +The present document does not specify test conditions, performance assessment and performance criteria for the Narrow-Band Internet of Things (NB-IoT) in band, NB-IoT guard band, or standalone NB-IoT operation, for AAS BS in *single RAT E-UTRA operation* as defined in TS 36.113 [6], or for AAS BS in *MSR operation* using E-UTRA as defined in TS 37.113 [4]. + +The present document does not specify test conditions, performance assessment and performance criteria for Band 46 operation as it is not supported by AAS BS. + +The scope of the present document is twofold: + +- Requirement, procedures and values of a *hybrid AAS BS* with *TAB connectors* for every transceiver unit at the *transceiver array boundary* (TAB), subject to conducted requirements, + +NOTE 3: *hybrid AAS BS* in the single RAT NR operation is equivalent to *BS type 1-H* defined in NR BS specification TS 38.104 [31]. + +- Requirements, procedures and values of an OTA AAS BS without *TAB connectors* and relying in the radiated interface, subject to radiated requirements. + +NOTE 4: OTA AAS BS in the single RAT NR operation is equivalent to *BS type 1-O* defined in NR BS specification TS 38.104 [31]. + +The electromagnetic environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [7] and IEC 61000-6-3 [8]. + +The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 37.105: "Active Antenna System (AAS) Base Station (BS) transmission and reception". +- [3] 3GPP TS 37.145-1: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 1: Conducted conformance testing". +- [4] 3GPP TS 37.113: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC)". +- [5] 3GPP TS 25.113: "Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)". +- [6] 3GPP TS 36.113: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)". +- [7] IEC 61000-6-1: 2016: "Electromagnetic compatibility (EMC) - Part 6-1: Generic standards - Immunity standard for residential, commercial and light-industrial environments". +- [8] IEC 61000-6-3: 2006/AMD1:2010: "Electromagnetic compatibility (EMC) - Part 6-3: Generic standards - Emission standard for residential, commercial and light-industrial environments". +- [9] Void. +- [10] 3GPP TS 37.145-2: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: radiated conformance testing". +- [11] IEC 61000-3-2: 2014: "Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current $\leq 16$ A per phase)". +- [12] IEC 61000-3-3: 2013: "Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems, for equipment with rated current $\leq 16$ A per phase and not subject to conditional connection". +- [13] IEC 61000-3-11: 2017 "Electromagnetic compatibility (EMC) - Part 3-11: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems - Equipment with rated current $\leq 75$ A and subject to conditional connection". +- [14] IEC 61000-3-12: 2011: "Electromagnetic compatibility (EMC) - Part 3-12: Limits - Limits for harmonic currents produced by equipment connected to public low-voltage systems with input current $>16$ A and $\leq 75$ A per phase". +- [15] IEC 61000-4-2: 2008: "Electromagnetic compatibility (EMC) - Part 4-2: Testing and measurement techniques - Electrostatic discharge immunity test". +- [16] IEC 61000-4-3: 2006+AMD1:2007+AMD2:2010: "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency, electromagnetic field immunity test". +- [17] IEC 61000-4-4: 2012: "Electromagnetic compatibility (EMC) – Part 4-4: Testing and measurement techniques – Electrical fast transient/burst immunity test". +- [18] IEC 61000-4-5: 2014+AMD1:2017: "Electromagnetic compatibility (EMC) - Part 4-5: Testing and measurement techniques - Surge immunity test". +- [19] IEC 61000-4-6: 2013: "Electromagnetic compatibility (EMC) - Part 4-6: Testing and measurement techniques - Immunity to conducted disturbances, induced by radio-frequency fields". + +- [20] IEC 61000-4-11: 2004+AMD1:2017: "Electromagnetic compatibility (EMC) - Part 4-11: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations immunity tests". +- [21] ETSI EN 301 489-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements". +- [22] Void +- [23] Void +- [24] ITU-R SM.329-10: "Unwanted emissions in the spurious domain". +- [25] ETSI EN 301 489-50, v2.1.0: "ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 50: Specific conditions for Cellular Communication Base Station (BS), repeater and ancillary equipment; Harmonised Standard covering the essential requirements of article 3.1(b) of Directive 2014/53/EU". +- [26] 3GPP TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)". +- [27] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)". +- [28] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [29] CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements". +- [30] 3GPP TS 38.113: "NR; Base Station (BS) ElectroMagnetic Compatibility (EMC)". +- [31] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [32] Void +- [33] 3GPP TS 37.104: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception". +- [34] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements". +- [35] IEC 61000-4-21: "Electromagnetic compatibility (EMC) - Part 4-21: Testing and measurement techniques - Reverberation chamber test methods". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 37.113 [4] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] or TS 37.113 [4]. + +NOTE: Multi-word definitions are treated as linguistic expressions and printed in italic font throughout this requirement specification. Linguistic expressions may not be split and are printed in their entirety. + +**active antenna system base station:** BS system which combines an *antenna array* with a transceiver unit array and a *radio distribution network*. + +**antenna array:** group of radiating elements characterized by the geometry and the properties of the *array elements*. + +**antenna port:** RF interface at the *transceiver array boundary*, specifically the *TAB connectors*. + +**BS type 1-H:** NR base station operating at FR1 with a requirement set consisting of conducted requirements defined at individual *TAB connectors* and OTA requirements defined at RIB. + +**BS type 1-O:** NR base station operating at FR1 with a requirement set consisting only of OTA requirements defined at the RIB. + +**hybrid AAS BS:** AAS BS which has both a conducted RF interface and a radiated RF interface in the far field and conforms to a *hybrid requirements set*. + +**MSR operation:** operation of AAS BS declared to be MSR in particular *operating band(s)*, including any of UTRA, E-UTRA and/or NR operation as single RAT or multi-RAT based on TS 37.104 [33] (see manufacturer's declaration D6.12 in TS 37.145-1 [3] and/or D9.25 in TS 37.145-2 [10]). + +**NB-IoT In-band operation:** NB-IoT is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier. + +**NB-IoT guard band operation:** NB-IoT is operating in guard band when it utilizes the unused resource block(s) within an E-UTRA carrier's guard-band. + +**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment. + +**OTA AAS BS:** AAS BS which has $\geq 8$ *transceiver units* for E-UTRA or MSR and $\geq 4$ *transceiver units* for UTRA per cell and has a radiated RF interface only and conforms to the *OTA requirements set*. + +**OTA requirements set:** complete set of OTA requirements applied to an OTA AAS BS. + +**port:** particular interface of EUT used for EMC requirements testing purposes. + +NOTE: Any connection point on EUT intended for connection of cables to or from EUT during the EMC testing is considered as a port. + +EXAMPLE 1: Examples of ports for *hybrid AAS BS* are as presented in figure 3.1-1: + +![Diagram of a hybrid AAS BS showing various ports.](5a24ac755b962fd5f0183f13de0726de_img.jpg) + +The diagram shows a central rectangular box labeled "Apparatus" inside a larger outer box. Above the outer box is the label "Enclosure Port". To the left of the outer box, three lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". To the right of the outer box, three lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "Antenna port", "Signal/control port", and "Telecommunication port". + +Diagram of a hybrid AAS BS showing various ports. + +**Figure 3.1-1: Examples of ports for *hybrid AAS BS*** + +EXAMPLE 2: Examples of ports for OTA AAS BS (i.e. with no antenna ports) are as presented in figure 3.1-2: + +![Diagram of an OTA AAS BS showing various ports, with no antenna port.](2a0f333f04f8e672bebf288c511c1db5_img.jpg) + +The diagram shows a central rectangular box labeled "Apparatus" inside a larger outer box. Above the outer box is the label "Enclosure Port". To the left of the outer box, three lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". To the right of the outer box, two lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "Signal/control port" and "Telecommunication port". There is no "Antenna port" shown on the right side. + +Diagram of an OTA AAS BS showing various ports, with no antenna port. + +**Figure 3.1-2: Examples of ports for OTA AAS BS** + +**radiated interface boundary:** operating band specific radiated requirements reference where the radiated requirements apply. + +**radio distribution network:** linear passive network which distributes the RF power generated by the transceiver unit array to the *antenna array*, and/or distributes the radio signals collected by the *antenna array* to the transceiver unit array. + +NOTE: In the case when the active transceiver units are physically integrated with the *array elements* of the *antenna array*, the *radio distribution network* is a one-to-one mapping. + +**single RAT E-UTRA operation:** operation of AAS BS declared to be single RAT E-UTRA in the operating band (see manufacturer's declaration D6.12 in TS 37.145-1 [3] and/or D9.25 in TS 37.145-2 [10]). + +NOTE: *Single RAT E-UTRA operation* does not cover in-band NB-IoT, nor guardband NB-IoT operation. + +**single RAT UTRA operation:** operation of AAS BS declared to be single RAT UTRA in the operating band (see manufacturer's declaration D6.12 in TS 37.145-1 [3] and/or D9.25 in TS 37.145-2 [10]). + +**spatial exclusion zone:** range of angles where no tests of radiated immunity are made for *OTA AAS BS* (i.e. half sphere around the EUT's radiating direction). + +**TAB connector:** *transceiver array boundary* connector. + +**transceiver array boundary:** conducted interface between the transceiver unit array and the composite antenna. + +**transceiver unit:** active unit consisting of transmitter and/or receiver which transmits and/or receives radio signals, and which may include passive RF filters. + +**telecommunication port:** ports which are intended to be connected to telecommunication networks (e.g. public switched telecommunication networks, integrated services digital networks), local area networks (e.g. Ethernet, Token Ring) and similar networks. + +NOTE: ETSI EN 301 489-1 [21] calls *telecommunication port* as the "wired network port". + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| $BW_{\text{Channel}}$ | Channel bandwidth | +| $f_{\text{offset}}$ | Frequency offset used for discovering narrowband response for receivers | +| $F_{\text{UL\_high}}$ | The highest frequency of the uplink operating band | +| $F_{\text{UL\_low}}$ | The lowest frequency of the uplink operating band | +| $\Delta f_{\text{OOB}}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $\Delta f_{\text{R exclusion}}$ | Maximum offset of the Radiated Immunity exclusion band from the uplink operating band edge for test without spatial exclusion zone applied | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. + +An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|-------------------------------------------------| +| AAS | Active Antenna System | +| AAS BS | AAS Base Station | +| CSA | Capability Set supported by the AAS BS | +| EMC | ElectroMagnetic Compatibility | +| EUT | Equipment Under Test | +| FR1 | Frequency Range 1 | +| MSR | Multi-Standard Radio | +| NB-IoT | Narrowband – Internet of Things | +| NR | New Radio | +| RCSA | Radiated Capability Set supported by the AAS BS | + +| | | +|-----|-----------------------------| +| RDN | Radio Distribution Network | +| RF | Radio Frequency | +| RIB | Radiated Interface Boundary | +| TAB | Transceiver Array Boundary | + +# 4 Test conditions + +The equipment shall be tested in normal test environment defined in base station conformance testing specification TS 37.145-1 [3], or TS 37.145-2 [10]. The test conditions shall be recorded in the test report. + +For an AAS BS supporting more than one RAT (see D6.12 in TS 37.145-1 [3], or D9.25 in TS 37.145-2 [10]), tests shall be performed with RATs activated according to the test configurations in subclause 4.4. Tests shall be performed relating to each type of port and RIB, and need not be repeated for each RAT if operating RATs are assessed simultaneously during the test. + +For AAS BS supporting single RAT operation only (see D6.12 in TS 37.145-1 [3], or D9.25 in TS 37.145-2 [10]), tests relating to the *antenna port(s)* and RIBs shall be performed for each supported RAT. + +For AAS BS capable of multi-band operation (see D6.13 in TS 37.145-1 [3], or D9.15 in TS 37.145-2 [10]), the requirements in the present document apply for each supported operating band unless otherwise stated. Operating bands and RATs shall be activated according to the respective test configurations in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4], or TS 38.113 [30]. Tests shall be performed relating to each type of port and RIB, and all RATs per band shall be assessed during the tests. + +Requirements apply only for the declared operating band(s) (see manufacturer's declaration D6.1 in TS 37.145-1 [3], or D9.4 in TS 37.145-2 [10]), and corresponding Band Categories as per CSA (see D6.12 in TS 37.145-1 [3]) and/or RCSA capability sets (see D9.25 in TS 37.145-2 [10]). + +The manufacturer shall declare the supported capability set(s) according to TS 37.145-1 [3] and TS 37.145-2 [10]. Tests performed on an AAS BS according to a declared capability set(s) cover all single RAT and multi-RAT configurations included in the declared capability set. Exception can be made for immunity testing based on declaration DEMC.1, DEMC.2, DEMC.3, and DEMC.4 (see table 4.5-1), as detailed in annex A. + +NOTE 1: *TAB connector* capability sets (CSA) for *hybrid AAS BS* are defined in TS 37.145-1 [3] and declared in D6.12 declaration. + +NOTE 2: Radiated capability sets (RCSA) for *hybrid AAS BS* and OTA AAS BS are defined in TS 37.145-2 [10] and declared by D9.25 declaration. + +Where the *hybrid AAS BS* has multiple *TAB connectors* which are declared to be equivalent then it is sufficient to perform EMC tests on a single representative *TAB connector*. For the definition of the *TAB connector* equivalence declaration (D6.70), refer to TS 37.145-1 [3]. + +EMC test shall not be performed with the AAS BS *antenna array* radiating, all *TAB connectors* shall be disconnected from the *radio distribution network* (RDN)/antenna array as specified in TS 37.105 [2] and terminated in an appropriate load impedance. For the description of the general AAS BS radio architecture and relations between the RDN/*antenna array* and the Transceiver Array Boundary, refer to TS 37.105 [2]. + +Depending on RAT capability sets supported by the AAS BS, the following test conditions shall be referred and applied for the BS test configurations: + +- For AAS BS in *single RAT UTRA operation* the test conditions from TS 25.113 [5] apply. +- For AAS BS in *single RAT E-UTRA operation* the test conditions from TS 36.113 [6] apply. +- For AAS BS in single RAT NR operation the test conditions from TS 38.113 [30] apply. +- For AAS BS in *MSR operation* the test conditions from TS 37.113 [4] apply. + +Whenever ports are considered for the emissions and immunity testing in the referred TS 25.113 [5], TS 36.113 [6] and TS 37.113 [4] specifications, special considerations shall be taken to test conditions specification for OTA AAS BS due to lack of *antenna ports*. + +NOTE 3: The receiver exclusion bands defined in E-UTRA and MSR specifications for Band 46 operation are not applicable for AAS BS, as the Band 46 operation is not supported by AAS BS. + +NOTE 4: The NB-IoT operation is not supported by AAS BS. + +## 4.1 Exclusion bands + +### 4.1.1 Transmitter exclusion band + +The *transmitter exclusion band* for BS is the frequency range over which no tests of radiated immunity of a transmitter are made. The *transmitter exclusion band* only applies to OTA AAS BS. + +The *transmitter exclusion band* is defined as: + +$$F_{DL,low} - \Delta f_{OBUE} < f < F_{DL,high} + \Delta f_{OBUE}$$ + +Where: + +The value of $\Delta f_{OBUE}$ , $F_{UL,low}$ and $F_{UL,high}$ are defined for each *operating band* for NR, E-UTRA, UTRA in TS 37.105 [2]. + +NOTE: For BS capable of multi-band operation, the frequency ranges relating to the RF bandwidths of all supported bands apply. + +### 4.1.2 Receiver exclusion band + +An exclusion band is a band of frequencies over which no tests of radiated immunity are made. + +In case the *spatial exclusion* (as discussed in subclause 9.2.2 and depicted in figure 9.2.2-1) is used during the EMC RI testing, the receiver exclusion band for OTA AAS BS is defined as: + +$$F_{UL,low} - \Delta f_{OOB} < f < F_{UL,high} + \Delta f_{OOB}$$ + +Where: + +- Values of $F_{UL,low}$ and $F_{UL,high}$ are defined for each *operating band* in TS 37.104 [33]. +- The values of $\Delta f_{OOB}$ are defined in table 4.1.2-1. + +**Table 4.1.2-1: Maximum $\Delta f_{OOB}$ offset outside the uplink operating band** + +| Operating band characteristics | $\Delta f_{OOB}$ (MHz) | +|-------------------------------------------------------------------|------------------------| +| $100 \text{ MHz} \geq F_{UL,high} - F_{UL,low}$ | 20 | +| $100 \text{ MHz} < F_{UL,high} - F_{UL,low} \leq 900 \text{ MHz}$ | 60 | + +In case the *spatial exclusion zone* (as discussed in subclause 9.2.2 and depicted in figure 9.2.2-1) is not used during the EMC RI testing, the receiver exclusion band for OTA AAS BS and *BS type I-O* is defined as: + +$$F_{UL,low} - \Delta f_{RIexclusion} < f < F_{UL,high} + \Delta f_{RIexclusion}$$ + +Where the values of $\Delta f_{RIexclusion}$ are defined in table 4.1.2-2. + +**Table 4.1.2-2: Maximum $\Delta f_{RIexclusion}$ offset outside the uplink operating band** + +| Operating band characteristics | $\Delta f_{RIexclusion}$ (MHz) | +|-------------------------------------------------|--------------------------------| +| $100 \text{ MHz} \geq F_{UL,high} - F_{UL,low}$ | 60 | +| $100 \text{ MHz} < F_{UL,high} - F_{UL,low}$ | 200 | + +For BS capable of multi-band operation, the total receiver exclusion band shall be the combination of the exclusion bands for each operating band supported by AAS BS. + +NOTE 1: The receiver exclusion bands do not apply for SDL bands. + +NOTE 2: Void + +## 4.2 Arrangements for establishing a communication link + +Depending on RAT capability sets supported by the AAS BS, the following arrangements for establishing a communication link shall be referred and applied: + +- For AAS BS in single RAT UTRA operation, the arrangements for establishing a communication link from TS 25.113 [5] apply. +- For AAS BS in single RAT E-UTRA operation, the arrangements for establishing a communication link from TS 36.113 [6] apply. +- For AAS BS in MSR operation, the arrangements for establishing a communication link from TS 37.113 [4] apply. +- For AAS BS in single RAT NR operation, the arrangements for establishing a communication link from TS 38.113 [30] apply. + +## 4.3 Narrow band responses on receivers + +Depending on RAT capability sets supported by the AAS BS, the following narrow band responses on receivers shall be referred and applied: + +- For AAS BS in single RAT UTRA operation, the narrow band responses on receivers from TS 25.113 [5] apply. +- For AAS BS in single RAT E-UTRA operation, the narrow band responses on receivers from TS 36.113 [6] apply. +- For AAS BS in MSR operation the arrangements for narrow band responses on receivers from TS 37.113 [4] apply. +- For AAS BS in single RAT NR operation, the arrangements for narrow band responses on receivers from TS 38.113 [30] apply. + +## 4.4 BS test configurations + +The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations in the following categories: + +- AAS BS for UTRA TDD, UTRA FDD, E-UTRA, NR and MSR meeting the conducted requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-1 [3]. In this case, the EMC test configuration are listed in tables 4.4-1, 4.4-3, 4.4-5, 4.4-7, 4.4-9, 4.4-11 respectively. +- AAS BS for UTRA FDD, E-UTRA, NR and MSR meeting the OTA requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-2 [10]. In this case, the EMC test configuration are listed in table 4.4-2, 4.4-4, 4.4-6, 4.4-8, 4.4-10, 4.4-12 respectively. + +The test configurations apply according to the declared RAT capability sets (i.e. CSA as declared in D6.12 in TS 37.145-1 [3], or RCSA as declared in D9.25 in TS 37.145-2 [10]) of the AAS BS and the Band Category of the declared operating band (i.e. BC1, BC2 or BC3). + +The AAS BS test configurations are defined as ATCx in TS 37.145-1 [3] and ATCRx in TS 37.145-2 [10], clause 4.11. + +- For AAS BS declared to be capable of contiguous operation only (see D6.14 in TS 37.145-1 [3], or D9.28 in TS 37.145-2 [10]), the test configuration(s) in tables 4.4-1, 4.4-2 and 4.4-3, 4.4-4 denoted by a "C" shall be used for testing. +- For AAS BS declared to be capable of contiguous and non-contiguous operation (see D6.14 in TS 37.145-1 [3], or D9.28 in TS 37.145-2 [10]), and where the parameters in the manufacture's declaration D6.15 in TS 37.145-1 [3] or D9.29 in TS 37.145-2 [10] are identical for contiguous and non-contiguous operation, the test configurations denoted by "CNC" shall be used. + +- For AAS BS declared to be capable of contiguous and non-contiguous operation (see D6.14 in TS 37.145-1 [3], or D9.28 in TS 37.145-2 [10]), and where the parameters in the manufacturer's D6.15 in TS 37.145-1 [3] or D9.29 in TS 37.145-2 [10] are not identical for contiguous and non-contiguous operation, the test configurations denoted by "C/NC" shall be used for testing. + +For AAS BS where signals from supported RATs are processed in common active components (see DEMC.2 and DEMC.4 in table 4.5-1), it is sufficient to consider a reduced set of CSs for immunity testing, as described in Annex A. + +For immunity tests: + +- The communication link for the RAT(s) listed in the table shall be established according to subclause 4.2. +- Tests for ports relating to the RAT(s) supported shall be performed according to subclause 4.1. + +**Table 4.4-1: Test configuration applicability to requirements and capability sets for TAB connectors supporting MSR operation** + +| TAB connector test case | UTRA + E-UTRA (CSA3) | | | E-UTRA + NR (CSA3A) | | | UTRA + E-UTRA + NR (CSA3B) | +|-------------------------|-------------------------------------------------------|-------------------------------------------------------|----------|-----------------------------------------------------|-----------------------------------------------------|-----------------------------------------------|--------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1,BC2 | +| Emission tests | C: ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C: ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C: ATC3b | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC: ANTC6
C/NC: ATC6,
ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| Immunity tests | C: ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C: ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C: ATC3b | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC: ANTC6
C/NC: ATC6,
ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | + +**Table 4.4-2: Test configuration applicability to requirements and capability sets for AAS BS supporting MSR operation** + +| Test case | UTRA + E-UTRA (RCSA 3) | | | E-UTRA + NR (RCSA 3A) | | | UTRA + E-UTRA + NR (RCSA 3B) | +|----------------|-----------------------------------------------------------|-----------------------------------------------------------|-----|---------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------|------------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1,BC2 | +| Emission tests | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C: ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR7
CNC: ANTCR7
C/NC: ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9, ANTCR9 | +| Immunity tests | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C: ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR7
CNC: ANTCR7
C/NC: ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9, ANTCR9 | + +**Table 4.4-3: Test configuration applicability to requirements and capability sets for TAB connectors supporting one RAT only MSR operation** + +| Capability set | UTRA (MC) capable BS (CSA1) | | | E-UTRA (MC) capable BS (CSA2) | | | +|-------------------------|---------------------------------------------------|---------------------------------------------------|----------|----------------------------------------------|----------------------------------------------|-------------------------------------------------| +| TAB connector test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| Emission tests | C: ATC1a
CNC: ANTC1a
C/NC: ATC1a,
ANTC1a | C: ATC1a CNC:
ANTC1a C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a CNC:
ANTC2 C/NC:
ATC2a, ANTC2 | C: ATC2a CNC:
ANTC2 C/NC:
ATC2a, ANTC2 | C: ATC2a CNC:
ANTC2 C/NC:
ATC2a, ANTC2 | +| Immunity tests | C: ATC1a CNC:
ANTC1a C/NC:
ATC1a,
ANTC1a | C: ATC1a CNC:
ANTC1a C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a CNC:
ANTC2 C/NC:
ATC2a, ANTC2 | C: ATC2a CNC:
ANTC2 C/NC:
ATC2a, ANTC2 | C: ATC2a
CNC: ANTC2
C/NC: ATC2a,
ANTC2 | + +**Table 4.4-4: Test configuration applicability to requirements and capability sets for operating bands supporting one RAT only MSR operation** + +| Capability set | UTRA (MC) capable BS (RCSA1) | | | E-UTRA (MC) capable BS (RCSA2) | | | +|----------------|-------------------------------------------------------------|-------------------------------------------------------------|-----|--------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------| +| Test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| Emission tests | C: ATCR1a
CNC:
ANTCR1a
C/NC:
ATCR1a,
ANTCR1a | C: ATCR1a
CNC:
ANTCR1a
C/NC:
ATCR1a,
ANTCR1a | N/A | C: ATCR2a
CNC: ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C: ATCR2a
CNC: ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C: ATCR2a
CNC: ANTCR2
C/NC:
ATCR2a,
ANTCR2 | +| Immunity tests | C: ATCR1a
CNC:
ANTCR1a
C/NC:
ATCR1a,
ANTCR1a | C: ATCR1a
CNC:
ANTCR1a
C/NC:
ATCR1a,
ANTCR1a | N/A | C: ATCR2a
CNC: ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C: ATCR2a
CNC: ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C: ATCR2a
CNC: ANTCR2
C/NC:
ATCR2a,
ANTCR2 | + +**Table 4.4-5: Test configurations for a TAB connector supporting single-RAT UTRA operation** + +| TAB connector test case | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C capable only | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC capable TAB connector (CSA4) C capable only | +|-------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| Emission tests | ATC1a | ANTC1 | ATC1a, ANTC1 | ATC1b | +| Immunity tests | ATC1a | ANTC1 | ATC1a, ANTC1 | ATC1b | + +**Table 4.4-6: Test configurations for an AAS BS supporting single-RAT UTRA operation** + +| Test case | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C capable only | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC AAS BS operating band (RCSA4) C capable only | +|----------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------| +| Emission tests | ATC1a | ANTC1 | ATC1a, ANTC1 | N/A | +| Immunity tests | ATCR1a | ANTCR1 | ATCR1a, ANTCR1 | N/A | + +**Table 4.4-7: Test configurations for a *TAB connector* supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band** + +| TAB connector test case | Single-RAT E-UTRA MC capable TAB connector (CSA5)
C capable only | Single-RAT E-UTRA MC capable TAB connector (CSA5)
C and NC capable BS with identical parameters (CNC) | Single-RAT E-UTRA MC capable TAB connector (CSA5)
C and NC capable BS with different parameters (CNC) | +|--------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| Emission tests | ATC2a | ANTC2 | ATC2a, ANTC2 | +| Immunity tests | ATC2a | ANTC2 | ATC2a, ANTC2 | + +**Table 4.4-8: Test configurations for an AAS BS supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band** + +| Test case | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)
C capable only | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)
C and NC capable BS with identical parameters | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)
C and NC capable BS with different parameters | +|----------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| +| Emission tests | ATCR2a | ANTCR2 | ATCR2a, ANTCR2 | +| Immunity tests | ATCR2a | ANTCR2 | ATCR2a, ANTCR2 | + +**Table 4.4-9: Test configuration for *multi-band TAB connectors* supporting MSR operation** + +| TAB connector test case | Test configuration for MBT | | +|--------------------------------|----------------------------|-------| +| | BC1/BC2 | BC3 | +| Emission tests | ATC5b | ATC5b | +| Immunity tests | ATC5b | ATC5b | + +**Table 4.4-10: Test configuration for AAS BS operating bands containing beams with multi-band dependencies supporting MSR operation** + +| TAB connector test case | Test configuration for MBT | | +|--------------------------------|----------------------------|--------| +| | BC1/BC2 | BC3 | +| Emission tests | ATCR5b | ATCR5b | +| Immunity tests | ATCR5b | ATCR5b | + +**Table 4.4-11: Test configuration for *multi-band TAB connectors* supporting Single-RAT only** + +| TAB connector test case | UTRA FDD CSA4 | UTRA TDD CSA4 | E-UTRA Test CSA5 | +|--------------------------------|-------------------------------|-----------------------|--------------------------------| +| Emission test | ATC1a/ANTC1 (note 1)
ATC5b | ATC1b (note 2), ATC5a | ATC2a/ANTC2 (note 3),
ATC5b | +| Immunity test | ATC5b | ATC5a | ATC5b | + +NOTE 1: ATC1a and/or ANTC1 shall be applied in each supported operating band according to table 4.4-3a. +NOTE 2: ATC1b shall be applied in each supported operating band according to table 4.4-3a. +NOTE 3: ATC2 and/or ANTC2 shall be applied in each supported operating band according to table 4.4-4a. + +**Table 4.4-12: Test configuration for AAS BS operating bands with multi-band dependencies supporting single-RAT only** + +| TAB connector test case | UTRA FDD CSA4 | UTRA TDD CSA4 | E-UTRA Test CSA5 | +|--------------------------------|----------------------------------|---------------|-----------------------------------| +| Emission test | ATCR1a/ANTCR1 (note 1)
ATCR5b | N/A | ATCR2a/ANTCR2 (note 2),
ATCR5b | +| Immunity test | ATCR5b | N/A | ATCR5b | + +NOTE 1: ATCR1a and/or ANTCR1 shall be applied in each supported operating band according to table 4.4-3b. +NOTE 2: ATCR2 and/or ANTCR2 shall be applied in each supported operating band according to table 4.4-4b. + +## 4.5 Manufacturer declarations + +The following EMC-specific manufacturer's declarations listed in table 4.5-1 are required to be provided by the manufacturer for AAS BS requirements testing. + +NOTE: The below listed manufacturer's declarations are supplementary to declarations covered in TS 37.145-1 [3], and in TS 37.145-2 [10]. + +**Table 4.5-1: EMC-specific manufacturer declarations** + +| Declaration identifier | Declaration | Description | +|--------------------------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DEMC.1
(NOTE) | Ports intended to be used with cables less than 3 m | Declaration of any port(s) intended to be used with cables less than 3 m. | +| DEMC.2 | Common and/or RAT-specific active RF components | Declaration of common and/or RAT-specific active RF components and other HW blocks for a communication link in AAS BS or other BS supporting more than one RAT. | +| DEMC.3 | Common and/or band-specific active RF components | Declaration of common and/or band-specific active RF components and other HW blocks for a communication link in BS capable of multi-band operation. | +| DEMC.4
(NOTE) | RAT dependencies for simplified immunity testing | Declaration of RAT dependencies for simplified immunity testing. For the case where BS employs common active RF components (DEMC.2), declare RATs which are handled per operating band in common active components in the radio digital unit. Declared per supported operating band (in case supported by multiple RATs). | +| NOTE: This manufacturer declaration is optional. | | | + +# 5 Performance assessment + +## 5.1 General + +The following information shall be recorded in or annexed to the test report: + +- the primary functions of the radio equipment to be tested during and after the EMC testing; +- the intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment; +- the method to be used to verify that a communications link is established and maintained; +- the user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress; +- the ancillary equipment to be combined with the radio equipment for testing (where applicable); +- the information about ancillary equipment intended to be used with the radio equipment; +- information about the common and/or RAT-specific active RF components and other HW blocks for a communication link in AAS BS supporting more than one RAT; (see declaration DEMC.2); +- information about the common and/or band-specific active RF components and other HW blocks for a communication link in AAS BS capable of multi-band operation; (see declaration DEMC.3); +- an exhaustive list of ports (and RIBs), classified as either power or signal/control. Power ports shall further be classified as AC or DC power. + +A communication link used by more than one tested RAT or more than one tested operating band, shall be assessed on all tested RATs and operating bands. Communication link(s) and/or radio performance parameters for the RATs and operating bands can during the test be assessed simultaneously or separately for each RAT and band, depending on the test environment capability. + +NOTE 1: The present document does not cover ancillary equipment requirements. However, the ancillary equipment EMC requirements are still applicable to the AAS BS and for the ancillary equipment performance assessment the appropriate non-AAS specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30] shall be referred. + +NOTE 2: The NB-IoT operation is not supported by AAS BS. + +## 5.2 Assessment of performance in Downlink + +In the immunity tests, the output of the transmitter shall be connected (via port for hybrid AAS BS, or via RIB for OTA AAS BS) to test equipment which meets the requirements for the performance assessment of RAT and bearer used in the immunity tests according to the following: + +- BLER assessment in TS 25.102 [26] in case of UTRA TDD +- BLER assessment in TS 25.101 [27] in case of UTRA FDD +- Throughput assessment in TS 36.101 [28] in case of E-UTRA +- Throughput assessment in TS 38.101-4 [34] in case of NR + +The level of the signal supplied to the equipment should be within the range for which the assessment of throughput is not impaired. Power control shall be OFF during the immunity testing. + +## 5.3 Assessment of performance in Uplink + +In the immunity tests, the performance in the uplink shall be monitored at a telecommunications port(s) by using suitable test equipment according to the following: + +- The value of the throughput shall be monitored in case of E-UTRA or in case of NR +- The value of the BLER shall be monitored in case of UTRA FDD or in case of UTRA TDD + +# --- 6 Performance criteria + +The test should, where possible, be performed using a bearer with the characteristics of data rate and performance criteria defined for UTRA TDD, UTRA FDD, E-UTRA, or NR. If the test is not performed using one of these bearers (for example, if none of them are supported by the BS) the characteristics of the bearer used shall be recorded in the test report. + +Depending on RAT capability sets supported by the AAS BS, the following performance criteria for continuous or for transient phenomena shall be referred and applied: + +- For AAS BS in *single RAT UTRA operation*, the performance criteria from TS 25.113 [5] apply. +- For AAS BS in *single RAT E-UTRA operation*, the performance criteria from TS 36.113 [6] apply. +- For AAS BS in *MSR operation*, the performance criteria from TS 37.113 [4] apply. +- For AAS BS in *single RAT NR operation*, the performance criteria from TS 38.113 [30] apply. + +NOTE 1: The present document does not cover ancillary equipment requirements. However, the ancillary equipment EMC requirements are still applicable to the AAS BS and for the ancillary equipment performance criteria the appropriate non-AAS specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30] shall be referred. + +NOTE 2: The NB-IoT operation is not supported by AAS BS. + +# 7 Applicability overview + +## 7.1 Emission + +Table 7.1-1: Emission requirements applicability + +| Phenomenon | Application | Equipment test requirement | Reference subclause in the present document | Reference standard | +|----------------------------------|----------------------------|--------------------------------------------|---------------------------------------------|-------------------------------------------------| +| | | BS equipment | | | +| Radiated emission | Enclosure | applicable for hybrid AAS BS (Note) | 8.2.1 | ITU-R SM.329 [24] | +| Conducted emission | DC power input/output port | applicable | 8.3 | CISPR 32 [29] | +| Conducted emission | AC mains input/output port | applicable | 8.4 | CISPR 32 [29] | +| Conducted emission | Telecommunication port | applicable | 8.5 | CISPR 32 [29] | +| Harmonic current emissions | AC mains input port | applicable | 8.6 | IEC 61000-3-2 [11]
or
IEC 61000-3-12 [14] | +| Voltage fluctuations and flicker | AC mains input port | applicable | 8.7 | IEC 61000-3-3 [12]
or
IEC 61000-3-11 [13] | + +NOTE: The EMC radiated emissions requirements for the OTA AAS BS are covered by the RF radiated emissions requirement in TS 37.105 [2], conforming to the TS 37.145-2 [10]. + +## 7.2 Immunity + +Table 7.2-1: Immunity requirements applicability + +| Phenomenon | Application | Equipment test requirement | Reference subclause in the present document | Reference standard | +|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------------------------------|---------------------| +| | | BS equipment | | | +| RF electromagnetic field (80 – 6000 MHz) | Enclosure | applicable | 9.2 | IEC 61000-4-3 [16] | +| Electrostatic discharge | Enclosure | applicable | 9.3 | IEC 61000-4-2 [15] | +| Fast transients common mode | Signal, telecommunications and control ports, DC and AC power input ports | applicable | 9.4 | IEC 61000-4-4 [17] | +| RF common mode 0.15 - 80 MHz | Signal, telecommunications and control ports, DC and AC power input ports | applicable | 9.5 | IEC 61000-4-6 [19] | +| Voltage dips and interruptions | AC mains power input ports | applicable | 9.6 | IEC 61000-4-11 [20] | +| Surges, common and differential mode | AC power input ports and telecommunications port | applicable | 9.7 | IEC 61000-4-5 [18] | + +# 8 Emission + +## 8.1 Test configurations + +This subclause defines the configurations for emission tests as follows: + +- The equipment shall be tested under normal test conditions as specified in the functional standards; + +- The test configuration shall be as close to normal intended use as possible; +- If the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports; +- If the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- The test conditions, test configuration and mode of operation shall be recorded in the test report; +- Ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment. In case of *hybrid AAS BS*, Radio Frequency (RF) input/output ports shall be correctly terminated; +- For OTA AAS BS without Radio Frequency (RF) input/output ports but intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup suitable for the radiated power; +- Ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- The test arrangements for transmitter and receiver clauses of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter clause and receiver clause of the EUT may be carried out simultaneously to reduce test time. + +## 8.2 Radiated emission from base station + +### 8.2.1 Radiated emission, hybrid AAS BS + +This test is applicable to *hybrid AAS BS*. This test shall be performed on a representative configuration of the *hybrid AAS BS*. + +Depending on RAT capability sets supported by the *hybrid AAS BS*, the following radiated emission requirements apply: + +- For *hybrid AAS BS* in *single RAT UTRA operation*, the base stations radiated emission requirements from TS 25.113 [5] apply. +- For *hybrid AAS BS* in *single RAT E-UTRA operation* the base stations radiated emission requirements from TS 36.113 [6] apply. +- For *hybrid AAS BS* in *MSR operation*, the base stations radiated emission requirements from TS 37.113 [4] apply. +- For *hybrid AAS BS* in *single RAT NR operation*, the *BS type I-H* radiated emission requirements from TS 38.113 [30] apply. + +### 8.2.2 Radiated emission, OTA AAS BS + +This test is applicable to OTA AAS BS. This test shall be performed on a representative configuration of the OTA AAS BS. + +For OTA AAS BS, the radiated emission requirement is covered by RF radiated spurious emission requirement in TS 37.105 [2], conforming to the test requirement in TS 37.145-2 [10]. + +- NOTE: As the EMC radiated emissions of the OTA AAS BS cannot be distinguished between the intended emissions (nor to any spurious emissions related to these intentional transmissions) a single radiated emissions requirement is used for the OTA AAS BS. + +## 8.3 Conducted emissions, DC power input/output port + +This test is applicable to equipment which may have DC cables longer than 3 m. + +If the DC power cable of the radio equipment is intended to be less than 3 m in length, and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in subclause 8.4. + +This test shall be performed on a representative configuration of the radio equipment. + +Depending on RAT capability sets supported by the BS, the following conducted emission requirements apply: + +- For AAS BS in *single RAT UTRA operation*, the DC power input/output port conducted emissions requirements from TS 25.113 [5] apply. +- For AAS BS in *single RAT E-UTRA operation*, the DC power input/output port conducted emissions requirements from TS 36.113 [6] apply. +- For AAS BS in *MSR operation*, the DC power input/output port conducted emissions requirements from TS 37.113 [4] apply. +- For AAS BS in *single RAT NR operation*, the DC power input/output port conducted emissions requirements from TS 38.113 [30] apply. + +## 8.4 Conducted emissions, AC mains power input/output port + +This test is applicable to equipment powered by the AC mains. + +This test is not applicable to AC output ports which are connected directly (or via a circuit breaker) to the AC power port of the EUT. + +This test shall be performed on a representative configuration of the radio equipment. + +Depending on RAT capability sets supported by the BS, the following conducted emission requirements apply: + +- For AAS BS in *single RAT UTRA operation*, the AC mains power input/output port conducted emissions requirements from TS 25.113 [5] apply. +- For AAS BS in *single RAT E-UTRA operation*, the AC mains power input/output port conducted emissions requirements from TS 36.113 [6] apply. +- For AAS BS in *MSR operation*, the AC mains power input/output port conducted emissions requirements from TS 37.113 [4] apply. +- For AAS BS in *single RAT NR operation*, the AC mains power input/output port conducted emissions requirements from TS 38.113 [30] apply. + +## 8.5 Harmonic current emissions (AC mains input port) + +The requirements of IEC 61000-3-2 [11] for harmonic current emission apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-12 [14] applies. + +## 8.6 Voltage fluctuations and flicker (AC mains input port) + +The requirements of IEC 61000-3-3 [12] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-11 [13] applies. + +## 8.7 Conducted emissions, telecommunication ports + +This test is applicable for radio equipment for fixed use which have telecommunication ports. + +This test shall be performed on a representative configuration of radio equipment. + +The test method and limits shall be in accordance with CISPR 32 [29], as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. + +# --- 9 Immunity + +## 9.1 Test configurations + +This subclause defines the configurations for immunity tests as follows: + +- The equipment shall be tested under normal test conditions as specified in the functional standards; +- During test, the RF output power may be reduced to a power level sufficient for establishing and maintaining the required communication link; +- The test configuration shall be as close to normal intended use as possible; +- If the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports; +- If the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- The test conditions, test configuration and mode of operation shall be recorded in the test report; +- Ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment. In case of *hybrid AAS BS*, Radio Frequency (RF) input/output ports shall be correctly terminated; +- For OTA AAS BS intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup capable to reduce the power to a level sufficient for establishing and maintaining the communication link; +- Ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- Immunity tests on the entire AAS BS shall be performed by establishing communication links at the radio interface (e.g. with the mobile simulator) and the S1/Iub interface (e.g. with an RNC/EPC simulator) and evaluating the BLER/throughput (see figures 9.1-1 and 9.1-2); +- Immunity tests shall be performed on both the Uplink and Downlink paths. The tests shall also include both the radio interface and the S1/Iub interface. BLER/throughput evaluation may be carried out at either interface, where appropriate, and the measurements for the Uplink and Downlink paths may be carried out as a single path looped at either the radio interface or S1/Iub interface. In case of looping is used care have to be taken that the BLER/throughput information doesn't change due to looping; +- For AAS BS capable of multi-RAT and/or multi-band operation, communication links shall be established in such a way that all tested RATs and operating band(s) are activated during the test according to the applicable test configurations in subclause 4.5. Performance assessment may be done separately for each tested RAT and/or operating band + +![Figure 9.1-1: Communication link set up for hybrid AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, a 'hybrid AAS BS (TAB connectors terminated)' in the center, and an 'EPC / RNC simulator' on the right. Arrows indicate bidirectional communication links between the UE simulator and the hybrid AAS BS, and between the hybrid AAS BS and the EPC / RNC simulator.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 9.1-1: Communication link set up for hybrid AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, a 'hybrid AAS BS (TAB connectors terminated)' in the center, and an 'EPC / RNC simulator' on the right. Arrows indicate bidirectional communication links between the UE simulator and the hybrid AAS BS, and between the hybrid AAS BS and the EPC / RNC simulator. + +**Figure 9.1-1: Communication link set up for *hybrid AAS BS* immunity measurement** + +![Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, an 'OTA AAS BS' in the center, and an 'EPC / RNC simulator' on the right. A bidirectional arrow labeled 'OTA link' connects the UE simulator and the OTA AAS BS. A bidirectional arrow also connects the OTA AAS BS and the EPC / RNC simulator.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, an 'OTA AAS BS' in the center, and an 'EPC / RNC simulator' on the right. A bidirectional arrow labeled 'OTA link' connects the UE simulator and the OTA AAS BS. A bidirectional arrow also connects the OTA AAS BS and the EPC / RNC simulator. + +**Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement** + +## 9.2 RF electromagnetic field (80 MHz - 6000 MHz) + +### 9.2.1 RF electromagnetic field, hybrid AAS BS + +This test assesses the ability of radio equipment to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. This test is applicable to *hybrid AAS BS* and shall be performed on a representative configuration of the *hybrid AAS BS*. + +The test method and levels shall be in accordance with IEC 61000-4-3 [16] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. The use of reverberation chamber test method according to IEC 61000-4-21 [35], clause 6.1 and Annex D as alternative method is allowed. + +### 9.2.2 RF electromagnetic field, OTA AAS BS + +This test assesses the ability of radio equipment operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. The OTA AAS BS includes an antenna which is an intentional radiator and does not form part of the EMC enclosure, application of RF electromagnetic fields in these directions may damage the BS receivers unintentionally. + +In the operational range of angles of the OTA AAS BS antenna receivers are protected by the RF blocking requirements defined in TS 37.105 [2], conforming to the test requirement in TS 37.145-2 [10] and are not part of the EMC RF electromagnetic field immunity requirement. + +In the range of angles except the operational range of angles of the OTA AAS BS antenna (i.e. except for the half sphere around the DUT radiating direction as depicted on figure 9.2.2-1) and for the frequency range above 690 MHz (according to ETSI EN 301 489-50 [25]), the EMC RF electromagnetic field immunity requirement with a level of 10 V/m applies on the non-radiating faces of the OTA AAS BS, as depicted on figure 9.2.2-1. + +When no spatial exclusion is implemented the use of reverberation chamber test method according to IEC 61000-4-21 [35], clause 6.1 and Annex D as alternative method is allowed. + +![Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS. The diagram shows a Device Under Test (DUT) represented by a semi-circular shape on the left. A dashed rectangular box labeled 'Spatial exclusion zone' is positioned to the right of the DUT. Three arrows indicate testing directions: 'RI testing direction' from the top pointing down towards the DUT, 'RI testing direction' from the bottom pointing up towards the DUT, and 'DUT radiating direction' from the DUT pointing horizontally to the right. Another 'RI testing direction' arrow points horizontally from the left towards the DUT.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS. The diagram shows a Device Under Test (DUT) represented by a semi-circular shape on the left. A dashed rectangular box labeled 'Spatial exclusion zone' is positioned to the right of the DUT. Three arrows indicate testing directions: 'RI testing direction' from the top pointing down towards the DUT, 'RI testing direction' from the bottom pointing up towards the DUT, and 'DUT radiating direction' from the DUT pointing horizontally to the right. Another 'RI testing direction' arrow points horizontally from the left towards the DUT. + +**Figure 9.2.2-1 EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS (horizontal plane depicted) with the spatial exclusion zone applied** + +Depending on RAT capability sets supported by the OTA AAS BS, the following RF electromagnetic field requirements apply over the range of angles covered by the EMC RF electromagnetic field immunity requirement: + +- For OTA AAS BS in *single RAT UTRA operation*, the RF electromagnetic field immunity requirements from TS 25.113 [5] apply. +- For OTA AAS BS in *single RAT E-UTRA operation*, the RF electromagnetic field immunity requirements from TS 36.113 [6] apply. +- For OTA AAS BS in *MSR operation*, the RF electromagnetic field immunity requirements from TS 37.113 [4] apply. +- For OTA AAS BS in *single RAT NR operation*, the *BS type I-O* requirements for the RF electromagnetic field immunity from TS 38.113 [30] apply. + +## 9.3 Electrostatic discharge + +This test assesses the ability of radio equipment to operate as intended in the event of an electrostatic discharge. + +The test shall be performed on a representative configuration of the radio equipment. + +The test method and levels shall be in accordance with IEC 61000-4-2 [15] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. + +## 9.4 Fast transients common mode + +The test shall be performed on AC mains power input ports. + +This test shall be performed on signal ports, telecommunication ports, control ports and DC power input/output ports if the cables may be longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares in DEMC.1 (see table 4.5-1) that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment. + +The test method and levels shall be in accordance with IEC 61000-4-4 [17] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. + +## 9.5 RF common mode (0.15 MHz - 80 MHz) + +The test shall be performed on AC mains power input/output ports. + +This test shall be performed on signal ports, telecommunication ports, control and DC power input/output ports, which may have cables longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares in DEMC.1 (see table 4.5-1) that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment. + +The test method and levels shall be in accordance with IEC 61000-4-6 [19] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. + +NOTE: This test can also be performed using the clamp injection method, where appropriate, see IEC 61000-4-6 [19]. + +## 9.6 Voltage dips and interruptions + +These tests assess the ability of radio equipment to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports. + +The tests shall be performed on AC mains power input ports. + +These tests shall be performed on a representative configuration of the equipment. + +The test method and levels shall be in accordance with IEC 61000-4-11 [20] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. + +## 9.7 Surges, common and differential mode + +These tests assess the ability of radio equipment to operate as intended in the event of surges being present at the AC mains power input ports and telecommunication ports. + +The tests shall be performed on AC mains power input ports. + +This test shall be additionally performed on telecommunication ports. + +These tests shall be performed on a representative configuration of the equipment. + +The test method and levels shall be in accordance with IEC 61000-4-5 [18] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. + +# Annex A (normative): Simplified immunity testing + +## A.1 Applicability + +Simplified immunity testing applies, per operating band, only to the BS which satisfies both of the following conditions: + +- Radio unit employs common active RF components for supported RATs, as described in DEMC.2. +- Radio digital unit employs common active components for supported RATs, as described in DEMC.4. + +NOTE: If the above condition is not met, all applicable test configurations in clause 4.4 apply for testing. + +## A.2 Capability Sets for simplified immunity testing + +The set of RATs which are considered sufficient for the immunity testing purposes depends on the BS hardware capabilities declared by the manufacturer in DEMC.4. + +The following RAT combinations were identified as candidates for the immunity testing reductions: + +- For AAS BS declared to support E-UTRA and UTRA, UTRA does not have to be configured. +- For AAS BS declared to support NR and UTRA, UTRA does not have to be configured. + +The above RAT combinations were further translated into the Capability Sets in tables below. + +For single-band AAS BS, the sufficient CSs in tables A.2-1 and A.2-2 may be considered, instead of the CSs in tables 4.4-1 and 4.4-2, respectively. + +The test configurations (TCx) are associated to the sufficient CSs according to tables 4.4-1 and 4.4-2. + +Example: BS declared to support CS9 (corresponding to TC9) in table A.2-2, will be tested using TC8 (corresponding to CS8). + +**Table A.2-1: Declared and sufficient CSs for testing** + +| Declared Capability Set | UTRA + E-UTRA (CSA3) | E-UTRA + NR (CSA3A) | UTRA + E-UTRA + NR (CSA3B) | +|---------------------------|-------------------------------|---------------------|----------------------------| +| Sufficient CS for testing | E-UTRA (MC) capable BS (CSA2) | E-UTRA + NR (CSA3A) | E-UTRA + NR (CSA3A) | + +**Table A.2-2: Declared and sufficient CSs for testing** + +| Declared Capability Set | UTRA + E-UTRA (RCSA 3) | E-UTRA + NR (RCSA 3A) | UTRA + E-UTRA + NR (RCSA 3B) | +|---------------------------|--------------------------------|-----------------------|------------------------------| +| Sufficient CS for testing | E-UTRA (MC) capable BS (RCSA2) | E-UTRA + NR (RCSA 3A) | E-UTRA + NR (RCSA 3A) | + +For multi-band multi-RAT capable MSR BS, the rationale described above applies for each band. + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-02 | RAN4#78 | R4-161123 | | | | First version of TS | 0.1.0 | +| 2016-03 | RAN#71 | RP-160401 | | | | Presented to RAN for approval.
Editorial corrections recommended by ETSI editHelp | 1.0.0 | +| 2016-03 | RP-71 | | | | | TR approved by RAN plenary | 13.0.0 | +| 2016/06 | RP-72 | RP-161142 | 0002 | 1 | F | Clarification in EMC environmental conditions references | 13.1.0 | +| 2017/03 | RP-75 | RP-170586 | 0004 | - | F | CR to TS 37.114: Clarification of the EMC specification's scope | 13.2.0 | +| 2017-03 | RP-75 | - | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2017/06 | RP-76 | RP-171306 | 0009 | | A | CR to TS 37.114: Isolation of Band 46 and NB-IoT from the AAS BS specification | 14.1.0 | +| 2017-12 | RAN#78 | RP-172599 | 0059 | 1 | B | Big CR to TS 37.114: eAAS EMC specification, v15.0.0 | 15.0.0 | +| 2018-03 | RAN#79 | RP-180282 | 0064 | | F | CR to TS37.114 | 15.1.0 | +| 2018-06 | RAN#80 | RP-181075 | 0067 | 1 | B | CR to TS 37.114: NR introduction into AAS EMC specification | 15.2.0 | +| 2018-12 | RAN#82 | RP-182362 | 0071 | 2 | B | CR to TS 37.114: Clarification on Exclusion Bands for Radiated Immunity Test in FR2 | 15.3.0 | +| 2018-12 | RAN#82 | RP-182386 | 0073 | 1 | F | CR to TS 37.114: additional inputs for introduction of NR to the AAS EMC specification | 15.3.0 | +| 2018-12 | RAN#82 | RP-182386 | 0074 | | F | CR to TS 37.114: RAT-specific AAS BS operation terminology corrections | 15.3.0 | +| 2018-12 | RAN#82 | RP-182386 | 0075 | 1 | B | CR to TS 37.114: Consideration of the narrowband responses and communication link | 15.3.0 | +| 2018-12 | RAN#82 | RP-182386 | 0076 | | F | CR to TS 37.114: clarification on CSA and RCSA capability sets | 15.3.0 | +| 2019-03 | RAN#83 | RP-190401 | 0077 | 1 | B | Draft CR to TS 37.114 Exclusion Bands for Radiated | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0078 | 1 | F | CR to TS 37.114: Updates for Rx exclusion zone size and terminology for EMC RI testing purposes | 15.5.0 | +| 2019-06 | RAN#84 | RP-191262 | 0080 | 1 | F | CR to TS 37.114 subclause 4.2 | 15.5.0 | +| 2019-06 | RAN#84 | RP-191262 | 0084 | | F | CR to 37.114 Subsections index in Section 4.1 | 15.5.0 | +| 2019-09 | RAN#85 | RP-192019 | 0085 | | F | CR to TS 37.114 Correction on CISPR 16-1-1 for DC conducted Emission(clause 2 and subclause 7.1) | 15.6.0 | +| 2019-09 | RAN#85 | RP-192053 | 0087 | 1 | F | CR to 37.114 Editorial Corrections | 15.6.0 | +| 2019-12 | RAN#86 | RP-193002 | 0093 | | F | CR to TS 37.114 Correction on definitions subclause 3.1 | 15.7.0 | +| 2019-12 | RAN#86 | RP-193002 | 0094 | | F | CR to TS 37.114 Correction on notes in subclause 7.1 | 15.7.0 | +| 2020-03 | RAN#87 | RP-200393 | 0095 | 1 | F | CR to TS 37.114 Add the transmitter exclusion band for MSR BS(subclause 4.1) | 15.8.0 | +| 2020-06 | RAN#88 | RP-201005 | 0096 | | F | CR to TS 37.114: internal TR reference corrections, Rel-15 | 15.9.0 | +| 2020-06 | RAN#88 | RP-200984 | 0097 | 1 | F | [R15]CR to TS 37.114 Add the reverberation chamber for radiated immunity testing (clause 2) | 15.9.0 | +| 2020-06 | RAN#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | SA#95 | | | | | Update to Rel-17 version (MCC) | 17.0.0 | +| 2023-03 | RAN#99 | RP-230502 | 0100 | | F | CR to TS 37.114 AAS BS test configuration R15 | 17.1.0 | +| 2023-03 | RAN#99 | RP-230505 | 0106 | | F | TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity | 17.1.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | RP-233360 | 0108 | 1 | F | [AAS_BS_LTE_UTRA-Core, TE118] CR to TS 37.114: framework for the EMC-specific manufacturer's declarations, Rel-18 | 18.0.0 | +| 2023-12 | RAN#102 | RP-233364 | 0109 | 1 | B | CR to TS 37.114: Implementation of AAS BS testing simplifications, Rel-18 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37141/raw.md b/marked/Rel-18/37_series/37141/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d8dad9c4c9ace3ab9679d69f711eb795024ee18f --- /dev/null +++ b/marked/Rel-18/37_series/37141/raw.md @@ -0,0 +1,7716 @@ + + +# 3GPP TS 37.141 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------|----| +| Foreword..... | 11 | +| 1 Scope..... | 13 | +| 2 References..... | 13 | +| 3 Definitions, symbols and abbreviations..... | 14 | +| 3.1 Definitions..... | 14 | +| 3.2 Symbols..... | 18 | +| 3.3 Abbreviations..... | 20 | +| 4 General test conditions and declarations..... | 21 | +| 4.1 Measurement uncertainties and test requirements..... | 21 | +| 4.1.1 General..... | 21 | +| 4.1.2 Acceptable uncertainty of Test System..... | 22 | +| 4.1.2.1 Measurement of transmitter..... | 23 | +| 4.1.2.2 Measurement of receiver..... | 24 | +| 4.1.3 Interpretation of measurement results..... | 26 | +| 4.2 Base Station classes..... | 27 | +| 4.3 Regional requirements..... | 27 | +| 4.4 Operating bands and band categories..... | 29 | +| 4.4.1 Band category 1 aspects (BC1)..... | 33 | +| 4.4.2 Band category 2 aspects (BC2)..... | 33 | +| 4.4.3 Band category 3 aspects (BC3)..... | 33 | +| 4.5 Channel arrangement..... | 34 | +| 4.5.1 Channel spacing..... | 34 | +| 4.5.1A CA Channel spacing..... | 34 | +| 4.5.2 Channel raster..... | 35 | +| 4.5.3 Carrier frequencies and numbering..... | 35 | +| 4.6 Manufacturer's declarations of regional and optional requirements..... | 36 | +| 4.6.1 Operating band and frequency range..... | 36 | +| 4.6.2 Spurious emissions category..... | 36 | +| 4.6.3 Additional operating band unwanted emissions..... | 36 | +| 4.6.4 Co-existence with other systems..... | 37 | +| 4.6.5 Co-location with other Base Stations..... | 37 | +| 4.6.6 NB-IoT sub-carrier spacing..... | 37 | +| 4.6.7 NB-IoT power dynamic range..... | 38 | +| 4.7 Capability set definition and manufacturer's declarations of supported RF configurations..... | 38 | +| 4.7.1 Definition of Capability Sets (CS)..... | 38 | +| 4.7.2 Manufacturer's declarations of supported RF configurations..... | 43 | +| 4.8 MSR test configurations..... | 47 | +| 4.8.1 TC1: UTRA multicarrier operation..... | 47 | +| 4.8.1.1 TC1a generation..... | 47 | +| 4.8.1.2 TC1b generation..... | 47 | +| 4.8.1.3 TC1 power allocation..... | 48 | +| 4.8.1a NTC1: UTRA multicarrier non-contiguous operation..... | 48 | +| 4.8.1a.1 NTC1a generation..... | 48 | +| 4.8.1a.2 NTC1 power allocation..... | 48 | +| 4.8.2 TC2: E-UTRA multicarrier operation..... | 48 | +| 4.8.2.1 TC2 generation..... | 48 | +| 4.8.2.2 TC2 power allocation..... | 49 | +| 4.8.2a NTC2: E-UTRA multicarrier non-contiguous operation..... | 49 | +| 4.8.2a.1 NTC2 generation..... | 49 | +| 4.8.2a.2 NTC2 power allocation..... | 49 | +| 4.8.3 TC3: UTRA and E-UTRA multi RAT operation..... | 49 | +| 4.8.3.1 TC3a generation..... | 49 | +| 4.8.3.2 TC3b generation..... | 50 | +| 4.8.3.3 TC3 power allocation..... | 50 | +| 4.8.3a NTC3: UTRA and E-UTRA multi RAT non-contiguous operation..... | 50 | + +| | | | +|-----------|-------------------------------------------------------------------------------------|----| +| 4.8.3a.2 | NTC3 power allocation..... | 51 | +| 4.8.4 | TC4: BC2 transmitter operation..... | 51 | +| 4.8.4.1 | TC4a generation..... | 51 | +| 4.8.4.2 | TC4b generation..... | 51 | +| 4.8.4.3 | TC4c generation..... | 52 | +| 4.8.4.4 | TC4d generation..... | 52 | +| 4.8.4.5 | TC4e generation..... | 52 | +| 4.8.4.6 | TC4 power allocation..... | 53 | +| 4.8.4a | NTC4: Non-contiguous multi RAT operations with GSM for the transmitter..... | 53 | +| 4.8.4a.1 | NTC4a generation..... | 53 | +| 4.8.4a.2 | NTC4b generation..... | 54 | +| 4.8.4a.3 | NTC4c generation..... | 55 | +| 4.8.4a.4 | NTC4 power allocation..... | 55 | +| 4.8.5 | TC5: BC2 receiver operation..... | 55 | +| 4.8.5.1 | TC5a generation..... | 55 | +| 4.8.5.2 | TC5b generation..... | 56 | +| 4.8.5a | NTC5: Non-contiguous multi RAT operations with GSM for the receiver..... | 56 | +| 4.8.5a.1 | NTC5a generation..... | 56 | +| 4.8.5a.2 | NTC5b generation..... | 56 | +| 4.8.5a.3 | NTC5c generation..... | 56 | +| 4.8.6 | TC6: Single carrier for receiver tests..... | 57 | +| 4.8.6.1 | TC6a generation..... | 57 | +| 4.8.6.2 | TC6b generation..... | 57 | +| 4.8.6.3 | TC6c generation..... | 57 | +| 4.8.7 | Generation of MB-MSR test configurations..... | 57 | +| 4.8.7.1 | TC7a: MB-MSR test configuration for full carrier allocation..... | 57 | +| 4.8.7.1.1 | TC7a generation..... | 57 | +| 4.8.7.1.2 | TC7a power allocation..... | 58 | +| 4.8.7.2 | TC7b: MB-MSR test configuration with high PSD per carrier..... | 58 | +| 4.8.7.2.1 | TC7b generation..... | 58 | +| 4.8.7.2.2 | TC7b power allocation..... | 59 | +| 4.8.7.3 | TC7c: MB-MSR test configuration with GSM/EDGE single RAT operation in one band..... | 59 | +| 4.8.7.3.1 | TC7c generation..... | 59 | +| 4.8.7.3.2 | TC7c power allocation..... | 60 | +| 4.8.8 | TC8: NB-IoT standalone multi-carrier operation..... | 60 | +| 4.8.8.1 | TC8 generation..... | 60 | +| 4.8.8.2 | TC8 power allocation..... | 60 | +| 4.8.9 | TC9: GSM and NB-IoT standalone multi-carrier operation..... | 61 | +| 4.8.9.1 | TC9 generation..... | 61 | +| 4.8.9.2 | TC9 power allocation..... | 61 | +| 4.8.10 | TC10: UTRA and NB-IoT standalone multi-carrier operation..... | 61 | +| 4.8.10.1 | TC10 generation..... | 61 | +| 4.8.10.2 | TC10 power allocation..... | 61 | +| 4.8.11 | TC11: E-UTRA and NB-IoT standalone multi-carrier operation..... | 62 | +| 4.8.11.1 | TC11 generation..... | 62 | +| 4.8.11.2 | TC11 power allocation..... | 62 | +| 4.8.12 | TC12: GSM and UTRA and NB-IoT standalone multi-carrier operation..... | 62 | +| 4.8.12.1 | TC12 generation..... | 62 | +| 4.8.12.2 | TC12 power allocation..... | 63 | +| 4.8.13 | TC13: GSM and E-UTRA and NB-IoT standalone multi-carrier operation..... | 63 | +| 4.8.13.1 | TC13 generation..... | 63 | +| 4.8.13.2 | TC13 power allocation..... | 63 | +| 4.8.14 | TC14: UTRA and E-UTRA and NB-IoT standalone multi-carrier operation..... | 63 | +| 4.8.14.1 | TC14 generation..... | 63 | +| 4.8.14.2 | TC14 power allocation..... | 64 | +| 4.8.15 | TC15: GSM and E-UTRA with NB-IoT in-band multi-carrier operation..... | 64 | +| 4.8.15.1 | TC15 generation..... | 64 | +| 4.8.15.2 | TC15 power allocation..... | 64 | +| 4.8.16 | TC16: UTRA and E-UTRA with NB-IoT in-band multi-carrier operation..... | 64 | +| 4.8.16.1 | TC16 generation..... | 65 | +| 4.8.16.2 | TC16 power allocation..... | 65 | + +| | | | +|-----------|------------------------------------------------------------------------------|-----| +| 4.8.17 | TC17: E-UTRA and E-UTRA with NB-IoT in-band multi-carrier operation..... | 65 | +| 4.8.17.1 | TC17 generation..... | 65 | +| 4.8.17.2 | TC17 power allocation..... | 65 | +| 4.8.18 | TC18: GSM and E-UTRA with NB-IoT guard-band multi-carrier operation..... | 65 | +| 4.8.18.1 | TC18 generation..... | 66 | +| 4.8.18.2 | TC18 power allocation..... | 66 | +| 4.8.19 | TC19: UTRA and E-UTRA with NB-IoT guard-band multi-carrier operation..... | 66 | +| 4.8.19.1 | TC19 generation..... | 66 | +| 4.8.19.2 | TC19 power allocation..... | 66 | +| 4.8.20 | TC20: E-UTRA and E-UTRA with NB-IoT guard-band multi-carrier operation..... | 66 | +| 4.8.20.1 | TC20 generation..... | 67 | +| 4.8.20.2 | TC20 power allocation..... | 67 | +| 4.8.21 | TC21: Contiguous operation in CS16, 18, 19..... | 67 | +| 4.8.21.0 | General..... | 67 | +| 4.8.21.1 | TC21 generation..... | 67 | +| 4.8.21.1A | TC21a generation..... | 68 | +| 4.8.21.1B | TC21b generation..... | 69 | +| 4.8.21.2 | TC21 power allocation..... | 69 | +| 4.8.22 | NTC21: Non-contiguous operation in CS16, 18, 19..... | 70 | +| 4.8.22.0 | General..... | 70 | +| 4.8.22.1 | NTC21 generation..... | 70 | +| 4.8.22.1A | NTC21a generation..... | 70 | +| 4.8.22.1B | NTC21b generation..... | 71 | +| 4.8.22.2 | NTC21 power allocation..... | 72 | +| 4.8.23 | TC22: Contiguous operation in CS17..... | 72 | +| 4.8.23.1 | TC22 generation..... | 72 | +| 4.8.23.2 | TC22 power allocation..... | 73 | +| 4.9 | RF channels and test models..... | 73 | +| 4.9.1 | RF channels..... | 73 | +| 4.9.2 | Test models..... | 74 | +| 4.10 | BS configurations..... | 75 | +| 4.10.1 | Transmit configurations..... | 75 | +| 4.10.1.1 | Transmission with multiple transmitter antenna connectors..... | 75 | +| 4.10.2 | Receive configurations..... | 75 | +| 4.10.2.1 | Reception with multiple receiver antenna connectors, receiver diversity..... | 76 | +| 4.10.3 | Duplexers..... | 76 | +| 4.10.4 | Power supply options..... | 76 | +| 4.10.5 | Ancillary RF amplifiers..... | 76 | +| 4.10.6 | BS with integrated Iuant BS modem..... | 77 | +| 4.10.7 | BS using antenna arrays..... | 77 | +| 4.10.7.1 | Receiver tests..... | 77 | +| 4.10.7.2 | Transmitter tests..... | 78 | +| 4.11 | Format and interpretation of tests..... | 78 | +| 4.12 | Requirements for BS capable of multi-band operation..... | 79 | +| 4.13 | Tests for BS capable of multi-band operation with three or more bands..... | 80 | +| 5 | Applicability of requirements and test configurations..... | 80 | +| 5.1 | Multi-RAT capable Base Stations..... | 82 | +| 5.2 | Single-RAT Multi-carrier capable Base Stations..... | 110 | +| 5.3 | Multi-band capable Base Stations..... | 122 | +| 6 | Transmitter characteristics..... | 125 | +| 6.1 | General..... | 125 | +| 6.2 | Base Station output power..... | 125 | +| 6.2.1 | Base Station maximum output power..... | 125 | +| 6.2.1.1 | Definition and applicability..... | 125 | +| 6.2.1.2 | Minimum requirement..... | 126 | +| 6.2.1.2A | Additional requirement (regional)..... | 126 | +| 6.2.1.3 | Test purpose..... | 126 | +| 6.2.1.4 | Method of test..... | 126 | +| 6.2.1.4.1 | Initial conditions..... | 126 | +| 6.2.1.4.2 | Procedure..... | 126 | + +| | | | +|-----------|----------------------------------------------------------------------------------|-----| +| 6.2.1.5 | Test requirements..... | 127 | +| 6.2.2 | E-UTRA DL RS power..... | 127 | +| 6.2.2.1 | Definition and applicability..... | 127 | +| 6.2.2.2 | Minimum requirement..... | 127 | +| 6.2.2.3 | Test purpose..... | 127 | +| 6.2.2.4 | Method of test..... | 127 | +| 6.2.2.5 | Test requirements..... | 127 | +| 6.2.3 | UTRA FDD primary CPICH power..... | 127 | +| 6.2.3.1 | Definition and applicability..... | 127 | +| 6.2.3.2 | Minimum requirement..... | 128 | +| 6.2.3.3 | Test purpose..... | 128 | +| 6.2.3.4 | Method of test..... | 128 | +| 6.2.3.5 | Test requirements..... | 128 | +| 6.2.3A | UTRA FDD secondary CPICH power..... | 128 | +| 6.2.3A.1 | Definition and applicability..... | 128 | +| 6.2.3A.2 | Minimum requirement..... | 128 | +| 6.2.3A.3 | Test purpose..... | 128 | +| 6.2.3A.4 | Method of test..... | 128 | +| 6.2.3A.5 | Test requirements..... | 128 | +| 6.2.4 | UTRA TDD primary CCPCH power..... | 129 | +| 6.2.4.1 | Definition and applicability..... | 129 | +| 6.2.4.2 | Minimum requirement..... | 129 | +| 6.2.4.3 | Test purpose..... | 129 | +| 6.2.4.4 | Method of test..... | 129 | +| 6.2.4.5 | Test requirements..... | 129 | +| 6.2.5 | NB-IoT DL NRS power..... | 129 | +| 6.2.5.1 | Definition and applicability..... | 129 | +| 6.2.5.2 | Minimum requirement..... | 129 | +| 6.2.5.3 | Test purpose..... | 129 | +| 6.2.5.4 | Method of test..... | 130 | +| 6.2.5.5 | Test requirements..... | 130 | +| 6.3 | Output power dynamics..... | 130 | +| 6.3.1 | Definition and applicability..... | 130 | +| 6.3.2 | Minimum Requirement..... | 130 | +| 6.3.3 | Test purpose..... | 130 | +| 6.3.4 | Method of test..... | 130 | +| 6.3.4.1 | Initial conditions for GSM/EDGE output power dynamics for CS7, CS15 or CS18..... | 130 | +| 6.3.4.2 | Procedure for GSM/EDGE output power dynamics for CS7, CS15 or CS18..... | 131 | +| 6.3.5 | Test Requirement..... | 131 | +| 6.4 | Transmit ON/OFF power..... | 131 | +| 6.4.1 | Definition and applicability..... | 131 | +| 6.4.2 | Minimum Requirement..... | 132 | +| 6.4.3 | Test purpose..... | 132 | +| 6.4.4 | Method of test..... | 133 | +| 6.4.4.1 | Initial conditions..... | 133 | +| 6.4.4.2 | Procedure..... | 133 | +| 6.4.5 | Test requirement..... | 133 | +| 6.5 | Transmitted signal quality..... | 133 | +| 6.5.1 | Modulation quality..... | 133 | +| 6.5.1.1 | Definition and applicability..... | 133 | +| 6.5.1.2 | Minimum Requirement..... | 133 | +| 6.5.1.3 | Test purpose..... | 134 | +| 6.5.1.4 | Method of test..... | 134 | +| 6.5.1.4.1 | Initial conditions..... | 134 | +| 6.5.1.4.2 | Procedure..... | 134 | +| 6.5.1.5 | Test Requirements..... | 134 | +| 6.5.1.5.1 | E-UTRA test requirement..... | 134 | +| 6.5.1.5.2 | UTRA FDD test requirement..... | 134 | +| 6.5.1.5.3 | UTRA TDD test requirement..... | 135 | +| 6.5.1.5.4 | GSM/EDGE test requirement..... | 135 | +| 6.5.1.5.5 | NB-IoT test requirement..... | 135 | + +| | | | +|-----------|-------------------------------------------------------------|-----| +| 6.5.1.5.6 | NR test requirement..... | 135 | +| 6.5.2 | Frequency error..... | 135 | +| 6.5.2.1 | Definition and applicability..... | 135 | +| 6.5.2.2 | Minimum Requirement..... | 135 | +| 6.5.2.3 | Test purpose..... | 135 | +| 6.5.2.4 | Method of test..... | 135 | +| 6.5.2.5 | Test Requirements..... | 135 | +| 6.5.2.5.1 | E-UTRA test requirement..... | 135 | +| 6.5.2.5.2 | UTRA FDD test requirement..... | 135 | +| 6.5.2.5.3 | UTRA TDD test requirement..... | 135 | +| 6.5.2.5.4 | GSM/EDGE test requirement..... | 135 | +| 6.5.2.5.5 | NB-IoT test requirement..... | 136 | +| 6.5.2.5.6 | NR test requirement..... | 136 | +| 6.5.3 | Time alignment error..... | 136 | +| 6.5.3.1 | Definition and applicability..... | 136 | +| 6.5.3.2 | Minimum requirement..... | 136 | +| 6.5.3.3 | Test purpose..... | 136 | +| 6.5.3.4 | Method of test..... | 136 | +| 6.5.3.5 | Test requirement..... | 137 | +| 6.6 | Unwanted emissions..... | 137 | +| 6.6.1 | Transmitter spurious emissions..... | 137 | +| 6.6.1.1 | Definition and applicability..... | 137 | +| 6.6.1.2 | Minimum requirement..... | 137 | +| 6.6.1.3 | Test purpose..... | 138 | +| 6.6.1.4 | Method of test..... | 138 | +| 6.6.1.4.1 | Initial conditions..... | 138 | +| 6.6.1.4.2 | Procedure..... | 138 | +| 6.6.1.5 | Test requirements..... | 138 | +| 6.6.1.5.1 | Spurious emissions (Category A)..... | 139 | +| 6.6.1.5.2 | Spurious emissions (Category B)..... | 139 | +| 6.6.1.5.3 | Additional test requirement for BC2 (category B)..... | 139 | +| 6.6.1.5.4 | Protection of the BS receiver of own or different BS..... | 140 | +| 6.6.1.5.5 | Additional spurious emission requirements..... | 140 | +| 6.6.1.5.6 | Co-location with other Base Stations..... | 151 | +| 6.6.2 | Operating band unwanted emissions..... | 157 | +| 6.6.2.1 | Definition and applicability..... | 157 | +| 6.6.2.2 | Minimum requirement..... | 158 | +| 6.6.2.3 | Test purpose..... | 158 | +| 6.6.2.4 | Method of test..... | 158 | +| 6.6.2.4.1 | Initial conditions..... | 158 | +| 6.6.2.4.2 | Procedure..... | 159 | +| 6.6.2.5 | Test requirement..... | 159 | +| 6.6.2.5.1 | Test requirements for Band Categories 1 and 3..... | 159 | +| 6.6.2.5.2 | Test requirements for Band Category 2..... | 169 | +| 6.6.2.5.3 | Test requirements for GSM/EDGE single-RAT requirements..... | 177 | +| 6.6.2.5.4 | Test requirements for additional requirements..... | 177 | +| 6.6.3 | Occupied bandwidth..... | 180 | +| 6.6.3.1 | Definition and applicability..... | 180 | +| 6.6.3.2 | Minimum requirements..... | 180 | +| 6.6.3.3 | Test purpose..... | 180 | +| 6.6.3.4 | Method of test..... | 180 | +| 6.6.3.5 | Test requirement..... | 181 | +| 6.6.4 | Adjacent Channel Leakage Power Ratio (ACLR)..... | 181 | +| 6.6.4.1 | Definition and applicability..... | 181 | +| 6.6.4.2 | Minimum requirement..... | 181 | +| 6.6.4.3 | Test purpose..... | 181 | +| 6.6.4.4 | Method of test..... | 181 | +| 6.6.4.4.1 | Initial conditions..... | 181 | +| 6.6.4.4.2 | Procedure..... | 182 | +| 6.6.4.5 | Test requirements..... | 182 | +| 6.6.4.5.1 | E-UTRA test requirement..... | 182 | + +| | | | +|-----------|-------------------------------------------------------------------|-----| +| 6.6.4.5.2 | UTRA FDD test requirement..... | 184 | +| 6.6.4.5.3 | UTRA TDD test requirement..... | 184 | +| 6.6.4.5.4 | Cumulative ACLR requirement in non-contiguous spectrum..... | 184 | +| 6.6.4.5.5 | NB-IoT test requirement..... | 186 | +| 6.6.4.5.6 | NR test requirement..... | 186 | +| 6.7 | Transmitter intermodulation..... | 188 | +| 6.7.1 | Definition and applicability..... | 188 | +| 6.7.2 | Minimum requirement..... | 189 | +| 6.7.2A | Additional requirement for Band 41..... | 189 | +| 6.7.3 | Test purpose..... | 189 | +| 6.7.4 | Method of test..... | 189 | +| 6.7.4.1 | Initial conditions..... | 189 | +| 6.7.4.2 | Procedure..... | 189 | +| 6.7.4.2.1 | General minimum requirement test procedure..... | 189 | +| 6.7.4.2.2 | Additional minimum requirement (BC1 and BC2) test procedure..... | 190 | +| 6.7.4.2.3 | Additional minimum requirement (BC3) test procedure..... | 190 | +| 6.7.5 | Test requirements..... | 191 | +| 6.7.5.1 | General test requirement..... | 191 | +| 6.7.5.2 | Additional test requirement (BC1 and BC2)..... | 192 | +| 6.7.5.3 | Additional test requirement (BC3)..... | 192 | +| 6.7.5.4 | Additional test requirement for Band 41..... | 192 | +| 7 | Receiver characteristics..... | 192 | +| 7.1 | General..... | 192 | +| 7.2 | Reference sensitivity level..... | 193 | +| 7.2.1 | Definition and applicability..... | 193 | +| 7.2.2 | Minimum requirement..... | 193 | +| 7.2.3 | Test purpose..... | 193 | +| 7.2.4 | Method of test..... | 193 | +| 7.2.4.1 | Initial conditions for GSM/EDGE reference sensitivity level..... | 193 | +| 7.2.4.2 | Procedure for GSM/EDGE reference sensitivity level..... | 194 | +| 7.2.5 | Test requirements..... | 194 | +| 7.3 | Dynamic range..... | 194 | +| 7.3.1 | Definition and applicability..... | 194 | +| 7.3.2 | Minimum requirement..... | 194 | +| 7.3.3 | Test purpose..... | 194 | +| 7.3.4 | Method of test..... | 194 | +| 7.3.4.1 | Initial conditions for GSM/EDGE dynamic range..... | 195 | +| 7.3.4.2 | Procedure for GSM/EDGE dynamic range..... | 195 | +| 7.3.5 | Test requirements..... | 195 | +| 7.4 | In-band selectivity and blocking..... | 195 | +| 7.4.1 | Definition and applicability..... | 195 | +| 7.4.2 | Minimum requirement..... | 196 | +| 7.4.3 | Test purpose..... | 196 | +| 7.4.4 | Method of test..... | 196 | +| 7.4.4.1 | Initial conditions..... | 196 | +| 7.4.4.2 | Procedure for general blocking..... | 196 | +| 7.4.4.3 | Procedure for narrowband blocking..... | 197 | +| 7.4.4.4 | Procedure for additional narrowband blocking for GSM/EDGE..... | 197 | +| 7.4.4.4.1 | Initial conditions for additional narrowband blocking..... | 197 | +| 7.4.4.4.2 | Procedure for additional narrowband blocking..... | 197 | +| 7.4.4.5 | Procedure for GSM/EDGE AM suppression..... | 198 | +| 7.4.4.5.1 | Initial conditions for GSM/EDGE AM suppression..... | 198 | +| 7.4.4.5.2 | Procedure for GSM/EDGE AM suppression..... | 198 | +| 7.4.4.6 | Procedure for additional BC3 blocking requirement..... | 198 | +| 7.4.5 | Test requirements..... | 199 | +| 7.4.5.1 | General blocking test requirement..... | 199 | +| 7.4.5.2 | General narrowband blocking test requirement..... | 200 | +| 7.4.5.3 | Additional narrowband blocking test requirement for GSM/EDGE..... | 202 | +| 7.4.5.4 | GSM/EDGE test requirements for AM suppression..... | 202 | +| 7.4.5.5 | Additional BC3 blocking test requirement..... | 202 | +| 7.5 | Out-of-band blocking..... | 203 | + +| | | | +|----------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------| +| 7.5.1 | Definition and applicability..... | 203 | +| 7.5.2 | Minimum requirement..... | 203 | +| 7.5.3 | Test purpose..... | 203 | +| 7.5.4 | Method of test..... | 203 | +| 7.5.4.1 | Initial conditions..... | 203 | +| 7.5.4.2 | Procedure..... | 204 | +| 7.5.5 | Test requirements..... | 204 | +| 7.5.5.1 | General out-of-band blocking test requirements..... | 204 | +| 7.5.5.2 | Co-location test requirements..... | 205 | +| 7.6 | Receiver spurious emissions..... | 210 | +| 7.6.1 | Definition and applicability..... | 210 | +| 7.6.2 | Minimum requirements..... | 210 | +| 7.6.3 | Test purpose..... | 210 | +| 7.6.4 | Method of test..... | 211 | +| 7.6.4.1 | Initial conditions..... | 211 | +| 7.6.4.2 | Procedure..... | 211 | +| 7.6.5 | Test requirements..... | 211 | +| 7.6.5.1 | General test requirements..... | 211 | +| 7.6.5.2 | Additional test requirement for BC2 (Category B)..... | 212 | +| 7.7 | Receiver intermodulation..... | 212 | +| 7.7.1 | Definition and applicability..... | 212 | +| 7.7.2 | Minimum requirement..... | 212 | +| 7.7.3 | Test purpose..... | 212 | +| 7.7.4 | Method of test..... | 212 | +| 7.7.4.1 | Initial conditions..... | 212 | +| 7.7.4.2 | Procedure for general and narrowband intermodulation..... | 213 | +| 7.7.4.3 | Procedure for additional narrowband intermodulation for GSM/EDGE..... | 213 | +| 7.7.4.3.1 | Initial conditions for additional narrowband intermodulation..... | 213 | +| 7.7.4.3.2 | Procedure for additional narrowband intermodulation..... | 214 | +| 7.7.5 | Test requirements..... | 214 | +| 7.7.5.1 | General intermodulation test requirement..... | 214 | +| 7.7.5.2 | General narrowband intermodulation test requirement..... | 218 | +| 7.7.5.3 | Additional narrowband intermodulation test requirement for GSM/EDGE..... | 223 | +| 7.8 | In-channel selectivity..... | 223 | +| 7.8.1 | Definition and applicability..... | 223 | +| 7.8.2 | Minimum requirement..... | 223 | +| 7.8.3 | Test purpose..... | 223 | +| 7.8.4 | Method of testing..... | 223 | +| 7.8.5 | Test requirements..... | 223 | +| 8 | Performance requirements..... | 224 | +| Annex A (normative): Characteristics of interfering signals..... | | 225 | +| A.1 | UTRA FDD interfering signal..... | 225 | +| A.2 | UTRA TDD interfering signal..... | 225 | +| A.3 | E-UTRA interfering signal..... | 225 | +| Annex B (normative): Environmental requirements for the BS equipment..... | | 226 | +| B.1 | General..... | 226 | +| B.2 | Normal test environment..... | 226 | +| B.3 | Extreme test environment..... | 226 | +| B.3.1 | Extreme temperature..... | 226 | + +| | | | +|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| B.4 | Vibration..... | 227 | +| B.5 | Power supply..... | 227 | +| B.6 | Measurement of test environments..... | 227 | +| Annex C (informative): Test Tolerances and Derivation of test requirements..... | | 228 | +| C.1 | Measurement of transmitter..... | 229 | +| C.2 | Measurement of receiver..... | 233 | +| Annex D (informative): Measurement system set-up..... | | 236 | +| D.1 | Transmitter..... | 236 | +| D.1.1 | Base station output power, transmitter ON/OFF power, modulation quality, transmitter spurious emissions and operating band unwanted emissions..... | 236 | +| D.1.2 | Transmitter intermodulation..... | 236 | +| D.2 | Receiver..... | 237 | +| D.2.1 | Blocking characteristics..... | 237 | +| D.2.2 | Receiver spurious emissions..... | 237 | +| D.2.3 | Receiver intermodulation..... | 237 | + +| | | +|-------------------------------------------------------------------|------------| +| Annex E (normative): E-UTRA Test model for BC3 CS3 BS..... | 238 | +| E.0 BC3 CS3 Test model description..... | 238 | +| E.0A BC3 CS16/17 Test model description..... | 239 | +| E.1 E-UTRA Test Model 1.1 (E-TM1.1_BC3CS3)..... | 239 | +| E.1A NR FR1 Test Model 1.1 (NR-FR1-TM1.1_BC3CS16/17)..... | 239 | +| E.2 E-UTRA Test Model 1.2 (E-TM1.2_BC3CS3)..... | 240 | +| E.2A NR FR1 Test Model 1.2 (NR-FR1-TM1.2_BC3CS16/17)..... | 240 | +| E.3 E-UTRA Test Model 2 (E-TM2_BC3CS3)..... | 240 | +| E.3A NR FR1 Test Model 2 (NR-FR1-TM2_BC3CS16/17)..... | 240 | +| E.3B NR FR1 Test Model 2a (NR-FR1-TM2a_BC3CS16/17)..... | 240 | +| E.3BA NR FR1 Test Model 2b (NR-FR1-TM2b_BC3CS16/17)..... | 240 | +| E.3C E-UTRA Test Model 2a (E-TM2a_BC3CS3)..... | 240 | +| E.3D E-UTRA Test Model 2b (E-TM2b_BC3CS3)..... | 240 | +| E.4 E-UTRA Test Model 3.1 (E-TM3.1_BC3CS3)..... | 241 | +| E.4Y E-UTRA Test Model 3.1a (E-TM3.1a_BC3CS3)..... | 241 | +| E.4Z E-UTRA Test Model 3.1b (E-TM3.1b_BC3CS3)..... | 241 | +| E.4ZA NR Test Model 3.1a (NR-FR1-TM3.1a_BC3CS16/17)..... | 241 | +| E.4ZB NR Test Model 3.1b (NR-FR1-TM3.1b_BC3CS16/17)..... | 241 | +| E.4A NR FR1 Test Model 3.1 (NR-FR1-TM3.1_BC3CS16/17)..... | 241 | +| E.5 E-UTRA Test Model 3.2 (E-TM3.2_BC3CS3)..... | 241 | +| E.5A NR FR1 Test Model 3.2 (NR-FR1-TM3.2_BC3CS16/17)..... | 241 | +| E.6 E-UTRA Test Model 3.3 (E-TM3.3_BC3CS3)..... | 241 | +| E.6A NR FR1 Test Model 3.3 (NR-FR1-TM3.3_BC3CS16/17)..... | 242 | +| Annex F (informative): Change history..... | 243 | + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document specifies the Radio Frequency (RF) test methods and conformance requirements for NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT Multi-Standard Radio (MSR) Base Station (BS). These have been derived from, and are consistent with the NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT MSR BS specification defined in [2]. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 37.104: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception". +- [3] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD) ". +- [4] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD) ". +- [5] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". +- [6] 3GPP TS 45.005: "Radio transmission and reception". +- [7] ITU-R Recommendation M.1545, "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [8] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission. +- [9] 3GPP TS 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing". +- [10] 3GPP TS 25.141: "Base Station (BS) conformance testing (FDD) ". +- [11] 3GPP TS 51.021: "Base Station System (BSS) equipment specification; Radio aspects". +- [12] 3GPP TS 25.142: "Base Station (BS) conformance testing (TDD) ". +- [13] Recommendation ITU-R SM.329-10, "Unwanted emissions in the spurious domain". +- [14] 3GPP TR 25.942: "Radio Frequency (RF) system scenarios". +- [15] ITU-R recommendation SM.328: "Spectra and bandwidth of emissions". +- [16] IEC 60721: "Classification of environmental conditions". +- [17] IEC 60721-3-3: "Classification of environmental conditions - Part 3-3: Classification of groups of environmental parameters and their severities - Stationary use at weather protected locations". +- [18] IEC 60721-3-4: "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations". + +- [19] ETSI EN 300 019-1-3, *European Standard (Telecommunications series)*, "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-3: Classification of environmental conditions; Stationary use at weather protected locations" +- [20] ETSI EN 300 019-1-4, *European Standard (Telecommunications series)*, "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-4: Classification of environmental conditions; Stationary use at non-weather protected locations" +- [21] IEC 60068-2-1 (2007): "Environmental testing - Part 2: Tests. Tests A: Cold". +- [22] IEC 60068-2-2 (2007): "Environmental testing - Part 2: Tests. Tests B: Dry heat". +- [23] IEC 60068-2-6 (2007): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)". +- [24] CEPT ECC Decision (13)03, "The harmonised use of the frequency band 1452-1492 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL)". +- [25] CEPT ECC Decision (17)06, "The harmonised use of the frequency bands 1427-1452 MHz and 1492-1518 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL)". +- [26] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing". +- [27] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [28] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [29] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" + +--- + +## 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]. + +**Band category:** group of operating bands for which the same MSR scenarios apply. + +**Base Station RF Bandwidth:** RF bandwidth in which a base station transmits and/or receives single or multiple carrier(s) and/or RATs simultaneously within a supported operating band. + +NOTE: In single carrier operation, the Base Station RF Bandwidth is equal to the channel bandwidth. + +**Base Station RF Bandwidth edge:** frequency of one of the edges of the Base Station RF Bandwidth. + +**Carrier:** modulated waveform conveying the NR, E-UTRA, UTRA or GSM/EDGE physical channels. + +**Carrier aggregation:** aggregation of two or more NR or E-UTRA component carriers in order to support wider transmission bandwidths. + +**Carrier aggregation band:** set of one or more operating bands across which multiple NR or E-UTRA carriers are aggregated with a specific set of technical requirements. + +NOTE: Carrier aggregation band(s) for an E-UTRA BS is declared by the manufacturer. + +**Channel bandwidth:** RF bandwidth supporting a single NR, E-UTRA, UTRA or GSM/EDGE RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. + +NOTE: The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE: The term channel bandwidth is referred to as BS channel bandwidth in the NR specifications, since for NR the BS and UE may operate with differing bandwidths. + +**Contiguous carriers:** set of two or more carriers configured in a spectrum block where there are no RF requirements based on co-existence for un-coordinated operation within the spectrum block. + +**Carrier power:** power at the antenna connector in the channel bandwidth of the carrier averaged over at least one subframe for NR or E-UTRA, at least one slot for UTRA and the useful part of the burst for GSM/EDGE. + +**Contiguous spectrum:** spectrum consisting of a contiguous block of spectrum with no sub-block gap(s). + +**Downlink operating band:** part of the operating band designated for downlink. + +**Highest Carrier:** carrier with the highest carrier centre frequency transmitted/received in the specified operating band(s). + +**Inter RF Bandwidth gap:** frequency gap between two consecutive Base Station RF Bandwidths that are placed within two supported operating bands. + +**Inter-band carrier aggregation:** carrier aggregation of NR or E-UTRA component carriers in different operating bands. + +NOTE: Carriers aggregated in each band can be contiguous or non-contiguous. + +**Inter-band gap:** The frequency gap between two supported consecutive operating bands. + +**Intra-band contiguous carrier aggregation:** contiguous NR or E-UTRA carriers aggregated in the same operating band. + +**Intra-band non-contiguous carrier aggregation:** non-contiguous NR or E-UTRA carriers aggregated in the same operating band. + +**Lowest Carrier:** carrier with the lowest carrier centre frequency transmitted/received in the specified operating band(s). + +**Lower Base Station RF Bandwidth edge:** frequency of the lower Base Station RF Bandwidth edge, used as a frequency reference point for transmitter and receiver requirements. + +**Lower sub-block edge:** frequency at the lower edge of one sub-block. + +NOTE: It is used as a frequency reference point for both transmitter and receiver requirements. + +**Maximum Base Station RF Bandwidth:** maximum RF bandwidth supported by a BS within each supported operating band. + +NOTE: The maximum Base Station RF Bandwidth for BS configured for contiguous and non-contiguous operation within each supported operating band is declared separately. + +**Maximum carrier output power:** carrier power available at the antenna connector for a specified reference condition. + +**Maximum Radio Bandwidth:** maximum frequency difference between the upper edge of the highest used carrier and the lower edge of the lowest used carrier. + +**Maximum RAT output power:** sum of the power of all carriers of the same RAT available at the antenna connector for a specified reference condition. + +**Maximum throughput:** maximum achievable throughput for a reference measurement channel. + +**Maximum total output power:** sum of the power of all carriers available at the antenna connector for a specified reference condition. + +**MB-MSR Base Station:** MSR base station characterized by the ability of its transmitter and/or receiver to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different operating band (which is not a sub-band or superseding-band of another supported operating band) than the other carrier(s). + +**Mean power:** power measured in the bandwidth and period of measurement applicable for each RAT + +NOTE: Mean power for an E-UTRA carrier is defined in TS 36.141 [9] and mean power for a UTRA carrier is defined in TS 25.141 [10]. In case of multiple carriers, the mean power is the sum of the mean power of all carriers. + +**Measurement bandwidth:** RF bandwidth in which an emission level is specified. + +**MSR Base Station:** base station characterized by the ability of its receiver and transmitter to process two or more carriers in common active RF components simultaneously in a declared Base Station RF Bandwidth, where at least one carrier is of a different RAT than the other carrier(s). + +**Multi-band connector:** *antenna* connector of the *BS type 1-C* associated with a transmitter or receiver that is characterized by the ability to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different *operating band* than the other carrier(s) and where this different *operating band* is not a sub-band or superseding-band of another supported operating band. + +**Multi-band transmitter:** transmitter characterized by the ability to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different operating band (which is not a sub-band or superseding-band of another supported operating band) than the other carrier(s). + +**Multi-band receiver:** receiver characterized by the ability to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different operating band (which is not a sub-band or superseding-band of another supported operating band) than the other carrier(s). + +**Non-contiguous spectrum:** spectrum consisting of two or more sub-blocks separated by sub-block gap(s). + +**NB-IoT In-band operation:** NB-IoT is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier. + +**NB-IoT guard band operation:** NB-IoT is operating in guard band when it utilizes the unused resource block(s) within a E-UTRA carrier's guard-band. + +**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment. + +**NB-IoT operation in NR in-band:** NB-IoT is operating in-band when it is located within a NR transmission bandwidth configuration plus 15 kHz at each edge but not within the NR minimum guard band $GB_{\text{Channel}}$ . + +**NB-IoT operation in NR guard band:** NB-IoT is operating in guard band when it is located within a NR BS channel bandwidth but is not NB-IoT operation in NR in-band + +**Occupied bandwidth:** width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage $\beta/2$ of the total mean power of a given emission. + +**Operating band:** A frequency range in which NR, E-UTRA, UTRA or GSM/EDGE operates (paired or unpaired), that is defined with a specific set of technical requirements. + +NOTE: The operating band(s) for a base station is declared by the manufacturer. + +**Sub-band:** A sub-band of an operating band contains a part of the uplink and downlink frequency range of the operating band. + +**Sub-block:** one contiguous allocated block of spectrum for use by the same base station. + +NOTE: There may be multiple instances of sub-blocks within an RF bandwidth. + +**Sub-block bandwidth:** RF bandwidth of one sub-block. + +**Sub-block gap:** frequency gap between two consecutive sub-blocks within an Base Station RF Bandwidth, where the RF requirements in the gap are based on co-existence for un-coordinated operation. + +**Superseding-band:** A superseding-band of an operating band includes the whole of the uplink and downlink frequency range of the operating band. + +**Single-RAT operation:** operation of a base station in an operating band with only one RAT configured in that operating band. + +**Synchronized operation:** operation of TDD in two different systems, where no simultaneous uplink and downlink occur. + +**RAT power:** sum of all carrier powers for all carriers of the same type. + +**Rated carrier output power:** mean power level per carrier that the manufacturer has declared to be available at the antenna connector. + +**Rated RAT output power:** mean power level per RAT that the manufacturer has declared to be available at the antenna connector. + +**Rated total output power:** total mean power level that the manufacturer has declared to be available at the antenna connector. + +**RRC filtered mean power:** mean power of a UTRA carrier as measured through a root raised cosine filter with roll-off factor $\alpha$ and a bandwidth equal to the chip rate of the radio access mode. + +NOTE: The RRC filtered mean power of a perfectly modulated UTRA signal is 0.246 dB lower than the mean power of the same signal. + +**Throughput:** number of payload bits successfully received per second for a reference measurement channel in a specified reference condition. + +**Total output power:** sum of all carrier powers for all carriers transmitted by the BS. + +**Total RF Bandwidth:** maximum sum of Base Station RF Bandwidths in all supported operating bands. + +**Transmission bandwidth:** bandwidth of an instantaneous NR or E-UTRA transmission from a UE or BS, measured in resource block units. + +**Transmission bandwidth configuration:** highest NR or E-UTRA transmission bandwidth allowed for uplink or downlink in a given channel bandwidth, measured in resource block units. + +**Transmitter ON period:** time period during which the base station transmitter is transmitting data and/or reference symbols. + +**Transmitter OFF period:** time period during which the base station transmitter is not allowed to transmit. + +**Transmitter transient period:** time period during which the transmitter is changing from the OFF period to the ON period or vice versa. + +**Unsynchronized operation:** operation of TDD in two different systems, where the conditions for synchronized operation are not met. + +**Uplink operating band:** part of the operating band designated for uplink. + +**Upper Base Station RF Bandwidth edge:** frequency of the upper Base Station RF Bandwidth edge, used as a frequency reference point for transmitter and receiver requirements. + +**Upper sub-block edge:** frequency at the upper edge of one sub-block. + +NOTE: It is used as a frequency reference point for both transmitter and receiver requirements. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\alpha$ | Roll-off factor | +| $\beta$ | Percentage of the mean transmitted power emitted outside the occupied bandwidth on the assigned channel | +| $BW_{\text{Channel}}$ | Channel bandwidth (for E-UTRA and NR) | +| $BW_{\text{Config}}$ | Transmission bandwidth configuration (for E-UTRA), expressed in MHz, where $BW_{\text{Config}} = N_{\text{RB}} \times 180 \text{ kHz}$ in the uplink and $BW_{\text{Config}} = 15 \text{ kHz} + N_{\text{RB}} \times 180 \text{ kHz}$ in the downlink. Transmission bandwidth configuration (for NR), where $BW_{\text{Config}} = N_{\text{RB}} \times \text{SCS} \times 12$ . | +| $BW_{\text{RF}}$ | Base Station RF Bandwidth, where $BW_{\text{RF}} = F_{\text{BW RF,high}} - F_{\text{BW RF,low}}$ | +| $BW_{\text{RF,max}}$ | Maximum Base Station RF Bandwidth | +| $DwPTS$ | Downlink part of the special subframe (for E-UTRA TDD operation) | +| $f$ | Frequency | +| $\Delta f$ | Separation between the Base Station RF Bandwidth edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency | +| $\Delta f_{\text{max}}$ | The largest value of $\Delta f$ used for defining the requirement | +| $\Delta f_{\text{OBUE}}$ | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| $\Delta f_{\text{OOB}}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $F_{\text{C}}$ | Carrier centre frequency | +| $F_{\text{filter}}$ | Filter centre frequency | +| $f_{\text{offset}}$ | Separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter | +| $f_{\text{offset,max}}$ | The maximum value of $f_{\text{offset}}$ used for defining the requirement | +| $F_{\text{block,high}}$ | Upper sub-block edge, where $F_{\text{block,high}} = F_{\text{C,block,high}} + F_{\text{offset, RAT}}$ | +| $F_{\text{block,low}}$ | Lower sub-block edge, where $F_{\text{block,low}} = F_{\text{C,block,low}} - F_{\text{offset, RAT}}$ | +| $F_{\text{BW RF,high}}$ | Upper Base Station RF Bandwidth edge, where $F_{\text{BW RF,high}} = F_{\text{C,high}} + F_{\text{offset, RAT}}$ | +| $F_{\text{BW RF,low}}$ | Lower Base Station RF Bandwidth edge, where $F_{\text{BW RF,low}} = F_{\text{C,low}} - F_{\text{offset, RAT}}$ | +| $F_{\text{C band, high}}$ | Center frequency of the highest transmitted/received carrier in a band. | +| $F_{\text{C band, low}}$ | Center frequency of the lowest transmitted/received carrier in a band. | +| $F_{\text{C,block, high}}$ | Centre frequency of the highest transmitted/received carrier in a sub-block. | +| $F_{\text{C,block, low}}$ | Centre frequency of the lowest transmitted/received carrier in a sub-block. | +| $F_{\text{C,high}}$ | Centre frequency of the highest transmitted/received carrier. | +| $F_{\text{C,low}}$ | Centre frequency of the lowest transmitted/received carrier. | +| $F_{\text{offset, RAT}}$ | Frequency offset from the centre frequency of the highest transmitted/received carrier to the upper Base Station RF Bandwidth edge, sub-block edge or Inter RF Bandwidth edge, or from the centre frequency of the lowest transmitted/received carrier to the lower Base Station RF Bandwidth edge, sub-block edge or Inter RF Bandwidth edge for a specific RAT. | +| $F_{\text{DL_low}}$ | The lowest frequency of the downlink operating band | +| $F_{\text{DL_high}}$ | The highest frequency of the downlink operating band | +| $F_{\text{UL_low}}$ | The lowest frequency of the uplink operating band | +| $F_{\text{UL_high}}$ | The highest frequency of the uplink operating band | +| $GB_{\text{Channel}}$ | Minimum guard band defined in TS 38.104 [27] clause 5.3.3 | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in units of resource blocks (for E-UTRA) | +| $P_{\text{EM,B32,B75,B76,ind}}$ | Declared emission level in Band 32, Band 75 and Band 76, ind=a, b, c | +| $P_{\text{EM,B32,ind}}$ | Declared emission level in Band 32, ind= d, e | +| $P_{\text{EM,B50,B74,B75,ind}}$ | Declared emission level for Band 50, Band 74 and Band 75, ind=a,b | +| $P_{\text{EM,B54,ind}}$ | Declared emission level in Band 54, ind=a,b,c,d,e,f | +| $P_{\text{max}}$ | Maximum total output power | +| $P_{\text{max,c}}$ | Maximum carrier output power | +| $P_{\text{max,RAT}}$ | Maximum RAT output power | +| $P_{\text{Rated,c}}$ | Rated carrier output power | +| $P_{\text{REFSENS}}$ | Reference Sensitivity power level | +| $W_{\text{gap}}$ | Sub-block gap size or Inter RF Bandwidth gap size | + +![Figure 3.2-1: Illustration of Base Station RF Bandwidth related symbols and definitions for Multi-Standard Radio. The diagram shows a continuous frequency spectrum on a horizontal axis labeled 'Frequency'. The total RF bandwidth is denoted as BW_RF, bounded by vertical black bars at F_BW RF,low and F_BW RF,high. Inside this bandwidth, there are three colored blocks: an orange block labeled 'RAT_low', a light blue block labeled 'Multiple carriers / RATs', and a green block labeled 'RAT_high'. Vertical dashed lines indicate the center frequencies: F_C,low for the orange block and F_C,high for the green block. Horizontal double-headed arrows indicate offsets: F_offset, RAT, low is the distance from the left boundary to F_C,low, and F_offset, RAT, high is the distance from F_C,high to the right boundary.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Figure 3.2-1: Illustration of Base Station RF Bandwidth related symbols and definitions for Multi-Standard Radio. The diagram shows a continuous frequency spectrum on a horizontal axis labeled 'Frequency'. The total RF bandwidth is denoted as BW\_RF, bounded by vertical black bars at F\_BW RF,low and F\_BW RF,high. Inside this bandwidth, there are three colored blocks: an orange block labeled 'RAT\_low', a light blue block labeled 'Multiple carriers / RATs', and a green block labeled 'RAT\_high'. Vertical dashed lines indicate the center frequencies: F\_C,low for the orange block and F\_C,high for the green block. Horizontal double-headed arrows indicate offsets: F\_offset, RAT, low is the distance from the left boundary to F\_C,low, and F\_offset, RAT, high is the distance from F\_C,high to the right boundary. + +Figure 3.2-1: Illustration of Base Station RF Bandwidth related symbols and definitions for Multi-Standard Radio + +![Figure 3.2-2: Illustration of Base Station RF Bandwidth related symbols and definitions for non-contiguous Multi-Standard Radio. The diagram shows two distinct sub-blocks on a frequency axis: 'Sub block 1' and 'Sub block n', separated by a gap labeled 'Sub block edge'. The total bandwidth from the start of the first sub-block to the end of the last is BW RF. Each sub-block contains three colored segments: red, cyan (Multiple carriers / RATs), and green. For Sub block 1, the red segment's center is F_C block 1, low (F_c, low) and the green segment's center is F_C block 1, high. For Sub block n, the red segment's center is F_C block n, low and the green segment's center is F_C block n, high (F_c, high). Offsets F_offset, RAT are shown between the sub-block edges and the respective outer carrier center frequencies. The overall boundaries are F_BW RF, low and F_BW RF, high.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +Figure 3.2-2: Illustration of Base Station RF Bandwidth related symbols and definitions for non-contiguous Multi-Standard Radio. The diagram shows two distinct sub-blocks on a frequency axis: 'Sub block 1' and 'Sub block n', separated by a gap labeled 'Sub block edge'. The total bandwidth from the start of the first sub-block to the end of the last is BW RF. Each sub-block contains three colored segments: red, cyan (Multiple carriers / RATs), and green. For Sub block 1, the red segment's center is F\_C block 1, low (F\_c, low) and the green segment's center is F\_C block 1, high. For Sub block n, the red segment's center is F\_C block n, low and the green segment's center is F\_C block n, high (F\_c, high). Offsets F\_offset, RAT are shown between the sub-block edges and the respective outer carrier center frequencies. The overall boundaries are F\_BW RF, low and F\_BW RF, high. + +Figure 3.2-2: Illustration of Base Station RF Bandwidth related symbols and definitions for non-contiguous Multi-Standard Radio + +![Figure 3.2-3: Illustration of Maximum Radio Bandwidth and Total RF Bandwidth for Multi-band Multi-standard Radio. The diagram shows two radio bands, Band X and Band Y, each with low and high frequency components. Band X consists of three segments: a red segment (F_C band X, low), a cyan segment, and a green segment (F_C band X, high). Band Y consists of three segments: a red segment (F_C band Y, low), a cyan segment, and a green segment (F_C band Y, high). The distance between the start of Band X and the start of Band Y is labeled 'Inter RF bandwidth gap'. The total RF bandwidth is the sum of the bandwidths of Band X and Band Y. The maximum radio bandwidth is the total RF bandwidth plus the inter RF bandwidth gap. The offset from the center frequency to the edge of each band is labeled F_offset, RAT.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The diagram illustrates the frequency spectrum for a multi-band multi-standard radio. It shows two bands, Band X and Band Y, each with a low-frequency component (red) and a high-frequency component (green), separated by a cyan segment. The bandwidth of each band is labeled $BW_{RF}$ of Band X and $BW_{RF}$ of Band Y. The gap between the bands is labeled 'Inter RF bandwidth gap'. The total RF bandwidth is the sum of the bandwidths of Band X and Band Y, labeled 'Total RF bandwidth = $BW_{RF}$ of Band X + $BW_{RF}$ of Band Y'. The maximum radio bandwidth is the total RF bandwidth plus the inter RF bandwidth gap. The offset from the center frequency to the edge of each band is labeled $F_{offset, RAT}$ . + +Figure 3.2-3: Illustration of Maximum Radio Bandwidth and Total RF Bandwidth for Multi-band Multi-standard Radio. The diagram shows two radio bands, Band X and Band Y, each with low and high frequency components. Band X consists of three segments: a red segment (F\_C band X, low), a cyan segment, and a green segment (F\_C band X, high). Band Y consists of three segments: a red segment (F\_C band Y, low), a cyan segment, and a green segment (F\_C band Y, high). The distance between the start of Band X and the start of Band Y is labeled 'Inter RF bandwidth gap'. The total RF bandwidth is the sum of the bandwidths of Band X and Band Y. The maximum radio bandwidth is the total RF bandwidth plus the inter RF bandwidth gap. The offset from the center frequency to the edge of each band is labeled F\_offset, RAT. + +**Figure 3.2-3: Illustration of Maximum Radio Bandwidth and Total RF Bandwidth for Multi-band Multi-standard Radio** + +### 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]. + +| | | +|----------|------------------------------------------------| +| ACIR | Adjacent Channel Interference Ratio | +| ACLR | Adjacent Channel Leakage Ratio | +| ACK | Acknowledgement (in HARQ protocols) | +| ACS | Adjacent Channel Selectivity | +| ARFCN | Absolute Radio Frequency Channel Number | +| AWGN | Additive White Gaussian Noise | +| BC | Band Category | +| BER | Bit Error Ratio | +| BS | Base Station | +| BTS | Base Transceiver Station | +| BW | Bandwidth | +| CA | Carrier Aggregation | +| CACLR | Cumulative Adjacent Channel Leakage Ratio | +| CP | Cyclic prefix | +| CRC | Cyclic Redundancy Check | +| CW | Continuous Wave | +| DC | Direct Current | +| DC-HSDPA | Dual Cell HSDPA | +| DTX | Discontinuous Transmission | +| EARFCN | E-UTRA Absolute Radio Frequency Channel Number | +| EDGE | Enhanced Data rates for GSM Evolution | +| EIRP | Effective Isotropic Radiated Power | +| E-UTRA | Evolved UTRA | +| EVM | Error Vector Magnitude | +| FCC | Federal Communications Commission | +| FDD | Frequency Division Duplex | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| GP | Guard Period (for E-UTRA TDD operation) | +| GSM | Global System for Mobile Communications | +| HSDPA | High Speed Downlink Packet Access | + +| | | +|----------|----------------------------------------------| +| ICS | In-Channel Selectivity | +| ITU-R | Radiocommunication Sector of the ITU | +| LA | Local Area | +| LNA | Low Noise Amplifier | +| MCL | Minimum Coupling Loss | +| MCS | Modulation and Coding Scheme | +| MIMO | Multiple Input Multiple Output | +| MB-MSR | Multi-Band Multi-Standard Radio | +| MBT | Multi-Band Testing | +| MFCN | Mobile/Fixed Communications Network | +| MR | Medium Range | +| MS | Mobile Station | +| MSR | Multi-Standard Radio | +| NB-IoT | Narrowband-Internet of Things | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NRS | Narrowband Reference Signal | +| OBUE | Operating Band Unwanted Emissions | +| OFDM | Orthogonal Frequency Division Multiplex | +| OOB | Out-Of-band | +| PA | Power Amplifier | +| PHS | Personal Handyphone System | +| QAM | Quadrature Amplitude Modulation | +| QPSK | Quadrature Phase-Shift Keying | +| RAT | Radio Access Technology | +| RB | Resource Block | +| REFSENS | Reference Sensitivity | +| RF | Radio Frequency | +| RMS | Root Mean Square (value) | +| RS | Reference Symbol | +| RX | Receiver | +| RR | Root Raised Cosine | +| SCS | Sub-Carrier Spacing | +| SBT | Single Band Testing | +| SNR | Signal-to-Noise Ratio | +| TAE | Time Alignment Error | +| TDD | Time Division Duplex | +| TT | Test Tolerance | +| TX | Transmitter | +| UARFCN | UTRA Absolute Radio Frequency Channel Number | +| UE | User Equipment | +| UEM | operating band Unwanted Emissions Mask | +| WA | Wide Area | + +--- + +## 4 General test conditions and declarations + +### 4.1 Measurement uncertainties and test requirements + +#### 4.1.1 General + +The requirements of this clause apply to all applicable tests in this specification. + +The minimum requirements are given in TS 37.104 [2] and the references therein. Test requirements are given in this specification or are included by reference to TS 25.141 [10], TS 25.142 [12], TS 36.141 [9], TS 38.141-1 [26] or TS 51.021 [11]. Test Tolerances for the test requirements explicitly stated in the present specification are defined in Annex C of this specification. Test Tolerances for test requirements included by reference are defined in the respective referred test specification. + +Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the minimum requirements to create test requirements. + +When a test requirement differs from the corresponding minimum requirement, then the Test Tolerance applied for the test is non-zero. The Test Tolerance for the test and the explanation of how the minimum requirement has been relaxed by the Test Tolerance are given in Annex C. + +#### 4.1.2 Acceptable uncertainty of Test System + +The maximum acceptable uncertainty of the Test System is specified below for each test defined explicitly in the present specification, where appropriate. The maximum acceptable uncertainty of the Test System for test requirements included by reference is defined in the respective referred test specification. + +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 tests, it should be noted that the uncertainties in clause 4.1.2 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. + +Unless otherwise stated, the uncertainties in clause 4.1.2 apply to the Test System for testing NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT MSR BS. + +#### 4.1.2.1 Measurement of transmitter + +**Table 4.1.2-1: Maximum Test System uncertainty for transmitter tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| 6.2.1 Base Station maximum output power | ±0.7 dB for UTRA, E-UTRA and NR, $f \leq 3.0$ GHz
±1.0 dB, $3.0$ GHz $< f \leq 4.2$ GHz for UTRA, E-UTRA and NR
±1.0 dB for GSM/EDGE or standalone NB-IoT | | +| 6.4 Transmit ON/OFF power | ±2.0 dB, $f \leq 3.0$ GHz
±2.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.6.1.5.1 Transmitter spurious emissions, Mandatory Requirements | $9$ kHz $< f \leq 4$ GHz: ±2.0 dB
$4$ GHz $< f \leq 19$ GHz: ±4.0 dB | | +| 6.6.1.5.2 Transmitter spurious emissions, Mandatory Requirements | $9$ kHz $< f \leq 4$ GHz: ±2.0 dB
$4$ GHz $< f \leq 19$ GHz: ±4.0 dB | | +| 6.6.1.5.3 Transmitter spurious emissions, Additional BC2 Requirement | $9$ kHz $< f \leq 4$ GHz: ±2.0 dB
$4$ GHz $< f \leq 12.75$ GHz: ±4.0 dB | | +| 6.6.1.5.4 Transmitter spurious emissions, Protection of BS receiver | ±3.0 dB | | +| 6.6.1.5.5 Transmitter spurious emissions, Additional spurious emission requirements | ±2.0 dB for $> -60$ dBm, $f \leq 3.0$ GHz
±2.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz
±3.0 dB for $\leq -60$ dBm, $f \leq 3.0$ GHz
±3.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.6.1.5.6 Transmitter spurious emissions, Co-location | ±3.0 dB | | +| 6.6.2 Operating band unwanted emissions | ±1.5 dB, $f \leq 3.0$ GHz
±1.8 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.6.3 Occupied bandwidth | For NR:
5 MHz, 10 MHz BS Channel BW: ±100 kHz
15 MHz, 20 MHz, 25 MHz, 30 MHz, 40 MHz, 50 MHz BS Channel BW: ±300 kHz
60 MHz, 70 MHz, 80 MHz, 90 MHz, 100 MHz BS Channel BW: ±600 kHz

For E-UTRA:
1.4MHz, 3MHz Channel BW: ±30kHz
5MHz, 10MHz Channel BW: ±100kHz
15MHz, 20MHz: Channel BW: ±300kHz

For UTRA: ±100kHz | | +| 6.6.4 Adjacent Channel Leakage Power Ratio (ACLR) | ACLR
$BW \leq 20$ MHz: ±0.8 dB
$BW > 20$ MHz: ±1.2 dB

Absolute power ±2.0 dB, $f \leq 3.0$ GHz
Absolute power ±2.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz

CACL
$BW \leq 20$ MHz: ±0.8 dB
$BW > 20$ MHz: ±1.2 dB
CACL absolute power ±2.0 dB, $f \leq 3.0$ GHz
CACL absolute power ±2.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.7 Transmitter intermodulation (interferer requirements)
This tolerance applies to the stimulus and not the measurements defined in 6.6.1, 6.6.2 and 6.6.4 | The value below applies only to the interfering signal and is unrelated to the measurement uncertainty of the tests (6.6.1, 6.6.2 and 6.6.4) which have to be carried out in the presence of the interferer.

±1.0 dB | The uncertainty of interferer has double the effect on the result due to the frequency offset | + +#### 4.1.2.2 Measurement of receiver + +**Table 4.1.2-2: Maximum Test System Uncertainty for receiver tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|-------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.4 In-band selectivity and blocking (General blocking requirements) | $\pm 1.4$ dB, $f \leq 3.0$ GHz
$\pm 1.8$ dB, $3.0$ GHz $< f \leq 4.2$ GHz |

Overall system uncertainty comprises three quantities:

  1. Wanted signal level error
  2. Interferer signal level error
  3. Additional impact of interferer leakage

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared to provide the ratio error of the two signals. The interferer leakage effect is systematic and is added arithmetically.

Test System uncertainty = [\text{SQRT}(\text{wanted\_level\_error}^2 + \text{interferer\_level\_error}^2)] + \text{leakage effect.}

f \leq 3.0 GHz
Wanted signal level \pm 0.7 dB
Interferer signal level \pm 0.7 dB
3.0 GHz < f \leq 4.2 GHz
Wanted signal level \pm 1.0 dB
Interferer signal level \pm 1.0 dB

f \leq 4.2 GHz
Impact of interferer leakage 0.4 dB.

| +| 7.4 In-band selectivity and blocking (Narrowband blocking requirements) | $\pm 1.4$ dB, $f \leq 3.0$ GHz
$\pm 1.8$ dB, $3.0$ GHz $< f \leq 4.2$ GHz | Same as In-band selectivity and blocking (General blocking requirements). | +| 7.4 In-band selectivity and blocking (BC3 blocking requirements) | $\pm 1.4$ dB, $f \leq 3.0$ GHz
$\pm 1.8$ dB, $3.0$ GHz $< f \leq 4.2$ GHz | Same as In-band selectivity and blocking (General blocking requirements). | +| 7.5 Out-of-band blocking | $1$ MHz $\leq f_{\text{interferer}} \leq 3$ GHz: $\pm 1.3$ dB
$3$ GHz $< f_{\text{interferer}} \leq 12.75$ GHz: $\pm 3.2$ dB |

Overall system uncertainty comprises three quantities:

  1. Wanted signal level error
  2. Interferer signal level error
  3. Interferer broadband noise

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared to provide the ratio error of the two signals. The Interferer Broadband noise effect is systematic and is added arithmetically.

Test System uncertainty = [\text{SQRT}(\text{wanted\_level\_error}^2 + \text{interferer\_level\_error}^2)] + \text{Broadband noise effect.}

Out of band blocking, using CW interferer:
Wanted signal level:
\pm 0.7 dB up to 3 GHz
\pm 1.0 dB up to 4.2 GHz
Interferer signal level:
\pm 1.0 dB up to 3 GHz
\pm 3.0 dB up to 12.75 GHz
Impact of interferer Broadband noise 0.1 dB

| +| 7.6 Receiver spurious emissions | $30$ MHz $\leq f \leq 4$ GHz: $\pm 2.0$ dB
$4$ GHz $< f \leq 19$ GHz: $\pm 4.0$ dB | | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.7.5 Receiver intermodulation (General requirements) | ±1.8 dB, $f \leq 3.0$ GHz
±2.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz |

Overall system uncertainty comprises four quantities:

  1. 1. Wanted signal level error
  2. 2. CW Interferer level error
  3. 3. Modulated Interferer level error
  4. 4. Impact of interferer ACLR

The effect of the closer CW signal has twice the effect.

Items 1, 2 and 3 are assumed to be uncorrelated so can be root sum squared to provide the combined effect of the three signals. The interferer ACLR effect is systematic and is added arithmetically.

Test System uncertainty = \text{SQRT} [(2 \times \text{CW\_level\_error})^2 + (\text{mod interferer\_level\_error})^2 + (\text{wanted signal\_level\_error})^2] + \text{ACLR effect.}

f \leq 3.0 GHz
Wanted signal level \pm 0.7 dB
CW interferer level \pm 0.5 dB
Mod interferer level \pm 0.7 dB
3.0 GHz < f \leq 4.2 GHz
Wanted signal level \pm 1.0 dB
CW Interferer level \pm 0.7 dB
Mod Interferer level \pm 1.0 dB

f \leq 4.2 GHz
Impact of interferer ACLR 0.4 dB

| +| 7.7.5 Receiver intermodulation (Narrowband requirements) | ±1.8 dB, $f \leq 3.0$ GHz
±2.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz | Same as Receiver intermodulation (General requirements). | +| NOTE 1: Unless otherwise noted, only the Test System stimulus error is considered here. The effect of errors in the throughput measurements or the BER/FER due to finite test duration is not considered. | | | + +### 4.1.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 Shared Risk principle. + +The Shared Risk principle is defined in ITU-R M.1545 [7]. + +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 clause 4.1.2 of this specification. + +If the Test System for a test is known to have a measurement uncertainty greater than that specified in clause 4.1.2, 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 clause 4.1.2 shall be used to tighten the test requirement, making the test harder to pass. (For some tests e.g. receiver tests, this may require modification of stimulus signals). This procedure (defined in Annex C) will ensure that a Test System not compliant with clause 4.1.2 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 clause 4.1.2 had been used. + +## 4.2 Base Station classes + +The requirements in this specification apply to Wide Area Base Stations, Medium Range Base Stations and Local Area Base Stations unless otherwise stated. + +Wide Area Base Stations are characterised by requirements derived from Macro Cell scenarios with a BS to UE minimum coupling loss equal to 70 dB. The Wide Area Base Station class has the same requirements as the base station for General Purpose application in Release 9 and 10. + +Medium Range Base Stations are characterised by requirements derived from Micro Cell scenarios with a BS to UE minimum coupling loss equals to 53 dB. + +Local Area Base Stations are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum coupling loss equal to 45 dB. + +For GSM/EDGE operation of an MSR BS, the requirements according to the applicable multicarrier BTS class apply. The Wide Area BS, Medium Range BS and Local Area BS in the present specification correspond to the Wide Area multicarrier BTS, Medium Range multicarrier BTS and Local Area multicarrier BTS respectively in the GSM/EDGE specifications. MSR requirements for multi-RAT operation only apply for the highest GSM/EDGE static power step. + +The manufacturer shall declare the intended class of the BS under test. + +## 4.3 Regional requirements + +Some requirements in the present document may only apply in certain regions either as optional requirements, or set by local and regional regulation as mandatory requirements. It is normally not stated in the 3GPP specifications under what exact circumstances that the requirements apply, since this is defined by local or regional regulation. + +Table 4.3-1 lists all requirements in the present specification that may be applied differently in different regions. There are additional single-RAT regional requirements that may apply. These are referenced from the present specification, but listed in the specification for the RATs concerned [3][4][5][6][27]. + +**Table 4.3-1: List of regional requirements** + +| Clause number | Requirement | Comments | +|------------------|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.5 | Operating bands and Band Categories | Some bands may be applied regionally. | +| 6.2.1.2A | Base station output power | Additional requirements may apply as defined in TS 37.104 [2] clause 6.2.2. | +| 6.6.1.5.1 | Spurious emissions (Category A) | Category A limits are mandatory for regions where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [13] apply. | +| 6.6.1.5.2 | Spurious emissions (Category B) | Category B limits are mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [13] apply. | +| 6.6.1.5.3 | Additional requirement for BC2 (Category B) | Category B limits are mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [13] apply. | +| 6.6.1.5.5 | Additional spurious emissions requirements | These requirements may be applied for the protection of system operating in frequency ranges other than the MSR BS operating band. In addition to the requirements in clauses 6.6.1.5.1, 6.6.1.5.2, 6.6.1.5.3, 6.6.1.5.4 and 6.6.1.5.5, the BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. | +| 6.6.1.5.6 | Co-location (spurious emissions) | These requirements may be applied for the protection of other BS receivers when a BS operating in another frequency band is co-located with any BS. | +| 6.6.2.5.4.1 | Additional requirements (Operating band unwanted emissions) | In addition to the requirements in clauses 6.6.2.5.1 and 6.6.2.5.2, the BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied and under the conditions declared by the manufacturer. | +| 6.6.2.5.4.2 | Unsynchronized operation for BC3 (Operating band unwanted emissions) | The requirements for unsynchronized TDD co-existence may apply regionally. | +| 6.6.2.5.4.3 | Protection of DTT (Operating band unwanted emissions) | The requirements for protection of DTT may apply regionally. | +| 6.6.2.5.4.4 | Co-existence with services in adjacent frequency bands (Operating band unwanted emissions) | This regional requirement may be applied for the protection of systems operating in frequency bands adjacent to band 1 as defined in clause 4.5, in geographic areas in which both an adjacent band service and UTRA and/or E-UTRA are deployed. | +| 6.6.2.5.4.6 | Additional band 32 unwanted emissions | These requirements may apply in certain regions | +| 6.6.3.5 | Occupied bandwidth | The requirement may be applied regionally. There may also be regional requirements to declare the Occupied bandwidth according to the definition. | +| 6.6.4.5.6 | Adjacent Channel Leakage Power Ratio (ACLR) | For Band 41 operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all antenna connectors . | +| 6.7.2A | Additional requirements for Band 41 | These requirements may apply in certain regions for Band 41 | +| 6.7.5.3, 6.7.5.4 | Additional test requirements | These requirements may apply in certain regions | +| 7.4.5.5 | Additional BC3 blocking test requirement | This requirement may be applied for the protection of the BS receiver when an MSR BS is operating in the same geographical area as UTRA TDD. | +| 7.5.2.5 | Co-location requirement (blocking) | These requirements may be applied for the protection of the BS receiver when a BS operating in another frequency band is co-located with any BS. | + +## 4.4 Operating bands and band categories + +MSR requirements are applicable for band definitions and band numbering as defined in the specifications TS 45.005 [6], TS 25.104 [3], TS 25.105 [4], TS 36.104 [5] and TS 38.104 [27]. For the purpose of defining the BS requirements, the operating bands are divided into three band categories as follows: + +- Band Category 1 (BC1): Bands for NR FDD, E-UTRA FDD and/or UTRA FDD operation. Bands in this category are also used for NB-IoT operation (all modes). +- Band Category 2 (BC2): Bands for NR FDD, E-UTRA FDD, UTRA FDD and/or GSM/EDGE operation. Bands in this category are also used for NB-IoT operation (all modes). +- Band Category 3 (BC3): Bands for NR TDD, E-UTRA TDD and/or UTRA TDD operation. Bands in this category are also used for NB-IoT operation (all modes). + +NOTE: For UTRA TDD, requirements in the present document cover the 1.28 Mcps UTRA TDD option. + +The paired and unpaired bands for the three Band Categories are shown in Table 4.4-1 and 4.4-2, together with the supported RATs and corresponding NR, E-UTRA, UTRA and GSM/EDGE band designations. + +**Table 4.4-1: Paired bands in NR, E-UTRA, UTRA and GSM/EDGE** + +| MSR Band number | Supported RATs and Band Numbers | | | | | Uplink (UL) BS receive, UE transmit (MHz) | Downlink (DL) BS transmit, UE receive (MHz) | BC | Notes | +|-----------------|---------------------------------|--------|--------|-------|----------|-------------------------------------------|---------------------------------------------|----|---------------| +| | NR | E-UTRA | NB-IoT | UTRA | GSM/EDGE | | | | | +| 1 | n1 | 1 | X | I | - | 1920 – 1980 | 2110 – 2170 | 1 | | +| 2 | n2 | 2 | X | II | PCS 1900 | 1850 – 1910 | 1930 – 1990 | 2 | | +| 3 | n3 | 3 | X | III | DCS 1800 | 1710 – 1785 | 1805 – 1880 | 2 | | +| 4 | - | 4 | X | IV | - | 1710 – 1755 | 2110 – 2155 | 1 | | +| 5 | n5 | 5 | X | V | GSM 850 | 824 – 849 | 869 – 894 | 2 | | +| 6 | - | - | - | VI | - | 830 – 840 | 875 – 885 | 1 | | +| 7 | n7 | 7 | X | VII | - | 2500 – 2570 | 2620 – 2690 | 1 | | +| 8 | n8 | 8 | X | VIII | E-GSM | 880 – 915 | 925 – 960 | 2 | | +| 9 | - | 9 | - | IX | - | 1749.9 – 1784.9 | 1844.9 – 1879.9 | 1 | | +| 10 | - | 10 | - | X | - | 1710 – 1770 | 2110 – 2170 | 1 | | +| 11 | - | 11 | X | XI | - | 1427.9 – 1447.9 | 1475.9 – 1495.9 | 1 | | +| 12 | n12 | 12 | X | XII | - | 699 – 716 | 729 – 746 | 1 | | +| 13 | n13 | 13 | X | XIII | - | 777 – 787 | 746 – 756 | 1 | | +| 14 | n14 | 14 | X | XIV | - | 788 – 798 | 758 – 768 | 1 | | +| 15 | - | - | - | - | - | Reserved | | | | +| 16 | - | - | - | - | - | Reserved | | | | +| 17 | - | 17 | X | - | - | 704 – 716 | 734 – 746 | 1 | | +| 18 | n18 | 18 | X | - | - | 815 – 830 | 860 – 875 | 1 | | +| 19 | - | 19 | X | XIX | - | 830 – 845 | 875 – 890 | 1 | | +| 20 | n20 | 20 | X | XX | - | 832 – 862 | 791 – 821 | 1 | | +| 21 | - | 21 | X | XXI | - | 1447.9 – 1462.9 | 1495.9 – 1510.9 | 1 | | +| 22 | - | 22 | - | XXII | - | 3410 – 3490 | 3510 – 3590 | 1 | | +| 23 | - | 23 | - | - | - | 2000 – 2020 | 2180 – 2200 | 1 | Note 4 | +| 24 | n24 | 24 | X | - | - | 1626.5 – 1660.5 | 1525 – 1559 | 1 | Note 6 | +| 25 | n25 | 25 | X | XXV | - | 1850 – 1915 | 1930 – 1995 | 1 | | +| 26 | n26 | 26 | X | XXVI | - | 814 – 849 | 859 – 894 | 1 | | +| 27 | - | 27 | - | - | - | 807 – 824 | 852 – 869 | 1 | | +| 28 | n28 | 28 | X | - | - | 703 – 748 | 758 – 803 | 1 | | +| 29 | n29 | 29 | - | - | - | N/A | 717 – 728 | 1 | Note 1 | +| 30 | n30 | 30 | - | - | - | 2305 – 2315 | 2350 – 2360 | 1 | | +| 31 | n31 | 31 | X | - | - | 452.5 – 457.5 | 462.5 – 467.5 | 1 | | +| 32 | - | 32 | - | XXXII | - | N/A | 1452 – 1496 | 1 | Note1, Note 2 | +| 64 | - | - | - | - | - | Reserved | | | | +| 65 | n65 | 65 | X | - | - | 1920 – 2010 | 2110 – 2200 | 1 | | +| 66 | n66 | 66 | X | - | - | 1710 – 1780 | 2110 – 2200 | 1 | Note 3 | +| 67 | n67 | 67 | - | - | - | N/A | 738 – 758 | 1 | Note 1 | +| 68 | - | 68 | - | - | - | 698 – 728 | 753 – 783 | 1 | | +| 69 | - | 69 | - | - | - | N/A | 2570 – 2620 | 1 | Note 1 | +| 70 | n70 | 70 | X | - | - | 1695 – 1710 | 1995 – 2020 | 1 | Note 5 | +| 71 | n71 | 71 | X | - | - | 663 – 698 | 617 – 652 | 1 | | +| 72 | n72 | 72 | X | - | - | 451 – 456 | 461 – 466 | 1 | | +| 73 | - | 73 | X | - | - | 450 – 455 | 460 – 465 | 1 | | +| 74 | n74 | 74 | X | - | - | 1427 – 1470 | 1475 – 1518 | 1 | | +| 75 | n75 | 75 | - | - | - | N/A | 1432 – 1517 | 1 | Note 1 | +| 76 | n76 | 76 | - | - | - | N/A | 1427 – 1432 | 1 | Note 1 | +| 85 | n85 | 85 | X | - | - | 698 – 716 | 728 – 746 | 1 | | +| 87 | - | 87 | X | - | - | 410 – 415 | 420 – 425 | 1 | | +| 88 | - | 88 | X | - | - | 412 – 417 | 422 – 427 | 1 | | +| 106 | n106 | 106 | X | - | - | 896 – 901 | 935 – 940 | 1 | | + +NOTE 1: For NR and/or E-UTRA, the band is restricted to operation when carrier aggregation is configured. The downlink operating band is paired with the uplink operating band (external) of the carrier aggregation configuration that is supporting the configured Pcell. + +| MSR Band number | Supported RATs and Band Numbers | | | | | Uplink (UL)
BS receive,
UE transmit
(MHz) | Downlink (DL)
BS transmit,
UE receive
(MHz) | BC | Notes | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|--------|--------|------|----------|----------------------------------------------------|------------------------------------------------------|----|-------| +| | NR | E-UTRA | NB-IoT | UTRA | GSM/EDGE | | | | | +| NOTE 2: For UTRA, the band is restricted to operation when dual band is configured (e.g., DB-DC-HSDPA or dual band 4C-HSDPA). The down link frequenc(ies) of this band are paired with the uplink frequenc(ies) of the other FDD band (external) of the dual band configuration.
NOTE 3: For NR and E-UTRA, the range 2180-2200 MHz of the DL operating band is restricted to operation when carrier aggregation is configured.
NOTE 4: Band 23 is not applicable.
NOTE 5: For E-UTRA, the range 2010-2020 MHz of the DL operating band is restricted to operation when carrier aggregation is configured, and TX-RX separation is 300 MHz. For E-UTRA, the range 2005-2020 MHz of the DL operating band is restricted to operation when carrier aggregation is configured, and TX-RX separation is 295 MHz.
NOTE 6: DL operation is restricted to 1526-1536 MHz frequency range. UL operation is restricted to 1627.5 – 1637.5 MHz and 1646.5 – 1656.5 MHz per FCC Order DA 20-48. | | | | | | | | | | + +NOTE: For BS capable of multi-band operation, the supported operating bands may belong to different Band Categories. + +**Table 4.4-2: Unpaired bands in NR, E-UTRA and UTRA** + +| MSR Band number | Supported RATs and Band Numbers | | | | Uplink (UL)
BS receive,
UE transmit
(MHz) | Downlink (DL)
BS transmit,
UE receive
(MHz) | BC | Notes | +|-----------------------------------------------------|---------------------------------|--------|--------|------|----------------------------------------------------|------------------------------------------------------|----|--------| +| | NR | E-UTRA | NB-IoT | UTRA | | | | | +| 33 | - | 33 | - | a) | 1900 – 1920 | 1900 – 1920 | 3 | | +| 34 | n34 | 34 | - | a) | 2010 – 2025 | 2010 – 2025 | 3 | | +| 35 | - | 35 | - | b) | 1850 – 1910 | 1850 – 1910 | 3 | | +| 36 | - | 36 | - | b) | 1930 – 1990 | 1930 – 1990 | 3 | | +| 37 | - | 37 | - | c) | 1910 – 1930 | 1910 – 1930 | 3 | | +| 38 | n38 | 38 | - | d) | 2570 – 2620 | 2570 – 2620 | 3 | | +| 39 | n39 | 39 | - | f) | 1880 – 1920 | 1880 – 1920 | 3 | | +| 40 | n40 | 40 | - | e) | 2300 – 2400 | 2300 – 2400 | 3 | | +| 41 | n41 | 41 | X | - | 2496 – 2690 | 2496 – 2690 | 3 | Note 1 | +| 42 | - | 42 | X | - | 3400 – 3600 | 3400 – 3600 | 3 | | +| 43 | - | 43 | X | - | 3600 – 3800 | 3600 – 3800 | 3 | | +| 44 | - | 44 | - | - | 703 – 803 | 703 – 803 | 3 | | +| 45 | - | 45 | - | - | 1447 – 1467 | 1447 – 1467 | 3 | | +| 48 | n48 | 48 | X | - | 3550 – 3700 | 3550 – 3700 | 3 | | +| 50 | n50 | 50 | - | - | 1432 – 1517 | 1432 – 1517 | 3 | | +| 51 | n51 | 51 | - | - | 1427 – 1432 | 1427 – 1432 | 3 | | +| 52 | - | 52 | - | - | 3300 – 3400 | 3300 – 3400 | 3 | | +| 53 | n53 | 53 | - | - | 2483.5 – 2495 | 2483.5 – 2495 | 3 | | +| 54 | n54 | 54 | X | - | 1670 – 1675 | 1670 – 1675 | 3 | | +| 77 | n77 | - | - | - | 3300 – 4200 | 3300 – 4200 | 3 | | +| 78 | n78 | - | - | - | 3300 – 3800 | 3300 – 3800 | 3 | | +| NOTE 1: Band 41 supports NB-IoT in certain regions. | | | | | | | | | + +**Table 4.4-3. Void****Table 4.4-4. Void** + +E-UTRA is designed to operate for the carrier aggregation bands defined in TS 36.101 [28]. The E-UTRA channel bandwidth $BW_{\text{Channel}}$ for a single carrier and the Aggregated Channel Bandwidth $BW_{\text{Channel\_CA}}$ for E-UTRA carrier aggregation are specified in clause 5.6 of TS 36.104 [5]. + +The NB-IoT channel bandwidth $BW_{\text{Channel}}$ is specified in clause 5.6 of TS 36.104 [5]. + +The NR BS channel bandwidth and PRB utilization is specified in clause 5.3 of TS 38.104 [27]. + +#### 4.4.1 Band category 1 aspects (BC1) + +For each BC1 band, BC1 requirements for receiver and transmitter shall apply with a frequency offset $F_{\text{offset, RAT}}$ from the lowest and highest carriers to the Base Station RF Bandwidth edges and sub-block edges (if any) as defined in Table 4.4.1-1. + +**Table 4.4.1-1: $F_{\text{offset, RAT}}$ for band category 1** + +| RAT | $F_{\text{offset, RAT}}$ | +|---------------------------------|-------------------------------------------| +| 1.4, 3 MHz E-UTRA | $BW_{\text{Channel}}/2 + 200 \text{ kHz}$ | +| 5, 10, 15, 20 MHz E-UTRA and NR | $BW_{\text{Channel}}/2$ | +| UTRA FDD | 2.5 MHz | +| Standalone NB-IoT | 200 kHz | + +#### 4.4.2 Band category 2 aspects (BC2) + +For each BC2 band, BC2 requirements for receiver and transmitter shall apply with a frequency offset $F_{\text{offset, RAT}}$ from the lowest and highest carriers to the Base Station RF Bandwidth edges and sub-block edges (if any) as defined in Table 4.4.2-1. + +**Table 4.4.2-1: $F_{\text{offset, RAT}}$ for band category 2** + +| RAT | $F_{\text{offset, RAT}}$ | +|-------------------|--------------------------| +| E-UTRA and NR | $BW_{\text{Channel}}/2$ | +| UTRA FDD | 2.5 MHz | +| GSM/EDGE | 200 kHz | +| Standalone NB-IoT | 200 kHz | + +#### 4.4.3 Band category 3 aspects (BC3) + +For each BC3 band, BC3 requirements for receiver and transmitter shall apply with a frequency offset $F_{\text{offset, RAT}}$ from the lowest and highest carriers to the Base Station RF Bandwidth edges and sub-block edges (if any) as defined in Table 4.4.3-1. + +**Table 4.4.3-1: $F_{\text{offset, RAT}}$ for band category 3** + +| RAT | $F_{\text{offset, RAT}}$ | +|---------------------------------|-------------------------------------------| +| 1.4, 3 MHz E-UTRA | $BW_{\text{Channel}}/2 + 200 \text{ kHz}$ | +| 5, 10, 15, 20 MHz E-UTRA and NR | $BW_{\text{Channel}}/2$ | +| 1.28 Mcps UTRA TDD | 1 MHz | +| Standalone NB-IoT | 200 kHz | + +## 4.5 Channel arrangement + +### 4.5.1 Channel spacing + +The GSM/EDGE carrier spacing is 200 kHz [6]. + +The nominal UTRA FDD channel spacing is 5 MHz. The nominal channel spacing is 1.6 MHz for the 1.28 Mcps UTRA TDD Option. These can be adjusted to optimise performance in a particular deployment scenario [3,4]. + +In E-UTRA the spacing between carriers will depend on the deployment scenario, the size of the frequency block available and the channel bandwidths. The nominal channel spacing between two adjacent E-UTRA carriers is defined as following: + +$$\text{Nominal Channel spacing} = (\text{BW}_{\text{Channel}(1)} + \text{BW}_{\text{Channel}(2)})/2$$ + +where $\text{BW}_{\text{Channel}(1)}$ and $\text{BW}_{\text{Channel}(2)}$ are the channel bandwidths of the two respective E-UTRA carriers. The channel spacing can be adjusted to optimize performance in a particular deployment scenario [5]. + +The standalone NB-IoT carrier spacing is 200 kHz. + +In NR the spacing between carriers will depend on the deployment scenario, the size of the frequency block available and the *BS channel bandwidths*. The nominal channel spacing between two adjacent NR carriers is defined as following: + +- For NR FR1 operating bands with 100 kHz channel raster, + +$$\text{Nominal Channel spacing} = (\text{BW}_{\text{Channel}(1)} + \text{BW}_{\text{Channel}(2)})/2$$ + +- For NR FR1 operating bands with 15 kHz channel raster, + - Nominal Channel spacing = $(\text{BW}_{\text{Channel}(1)} + \text{BW}_{\text{Channel}(2)})/2 + \{-5 \text{ kHz}, 0 \text{ kHz}, 5 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 15 kHz + - Nominal Channel spacing = $(\text{BW}_{\text{Channel}(1)} + \text{BW}_{\text{Channel}(2)})/2 + \{-10 \text{ kHz}, 0 \text{ kHz}, 10 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 30 kHz + +where $\text{BW}_{\text{Channel}(1)}$ and $\text{BW}_{\text{Channel}(2)}$ are the *BS channel bandwidths* of the two respective NR carriers. The channel spacing can be adjusted depending on the channel raster to optimize performance in a particular deployment scenario [27]. + +The spacing between E-UTRA and NR carriers will depend on the deployment scenario, the size of the frequency block available and the channel bandwidths. The nominal channel spacing between and E-UTRA carrier and an adjacent NR carrier is defined as following: + +- For NR operating bands with 100 kHz channel raster, + +$$\text{Nominal Channel spacing} = (\text{BW}_{\text{E-UTRA\_Channel}} + \text{BW}_{\text{NR\_Channel}})/2$$ + +- For NR operating bands with 15 kHz channel raster, + +$$\text{Nominal Channel spacing} = (\text{BW}_{\text{E-UTRA\_Channel}} + \text{BW}_{\text{NR\_Channel}})/2 + \{-5 \text{ kHz}, 0 \text{ kHz}, 5 \text{ kHz}\} \text{ for } \Delta F_{\text{Raster}} \text{ equals to 15 kHz}$$ + +$$\text{Nominal Channel spacing} = (\text{BW}_{\text{E-UTRA\_Channel}} + \text{BW}_{\text{NR\_Channel}})/2 + \{-10 \text{ kHz}, 0 \text{ kHz}, 10 \text{ kHz}\} \text{ for } \Delta F_{\text{Raster}} \text{ equals to 30 kHz}$$ + +where $\text{BW}_{\text{E-UTRA\_Channel}}$ and $\text{BW}_{\text{NR\_Channel}}$ are the channel bandwidths of the E-UTRA and NR carriers, $\Delta F_{\text{Raster}}$ is the band dependent channel raster granularity defined in TS38.101-1[29]. The channel spacing can be adjusted depending on the channel raster to optimize performance in a particular deployment scenario. + +### 4.5.1A CA Channel spacing + +In E-UTRA, for intra-band contiguously aggregated carriers the channel spacing between adjacent component carriers shall be multiple of 300 kHz. + +The nominal channel spacing between two adjacent aggregated E-UTRA carriers is defined as follows: + +where $BW_{\text{Channel}(1)}$ and $BW_{\text{Channel}(2)}$ are the channel bandwidths of the two respective E-UTRA component carriers according to Table 5.6-1 with values in MHz. The channel spacing for intra-band contiguous carrier aggregation can be adjusted to any multiple of 300 kHz less than the nominal channel spacing to optimize performance in a particular deployment scenario. + +In NR for intra-band contiguously aggregated carriers, the channel spacing between adjacent component carriers shall be multiple of least common multiple of channel raster and sub-carrier spacing. + +The nominal channel spacing between two adjacent aggregated NR carriers is defined as follows: + +For NR operating bands with 100 kHz channel raster: + +For NR operating bands with 15 kHz channel raster: + +with + +where $BW_{\text{Channel}(1)}$ and $BW_{\text{Channel}(2)}$ are the *BS channel bandwidths* of the two respective NR component carriers according to Table 5.3.3-1 and 5.3.3-2 in TS 38.104 [17] with values in MHz, $\mu_0$ the largest $\mu$ value among the subcarrier spacing configurations supported in the operating band for both of the channel bandwidths according to Table 5.3.5-1 and Table 5.3.5-2 in TS 38.104 [17] and $GB_{\text{Channel}(i)}$ the minimum guard band for channel bandwidth $i$ according to Table 5.3.3-1 and Table 5.3.3-2 in TS 38.104 [17] for the said $\mu$ value, with $\mu$ as defined in TS 38.211. In case there is no common $\mu$ value for both of the channel bandwidths, $\mu_0=1$ is selected for NR *operating bands* with 15 kHz channel raster and $GB_{\text{Channel}(i)}$ is the minimum guard band for channel bandwidth $i$ according to Table 5.3.3-1 in TS 38.104 [17] for $\mu=1$ with $\mu$ as defined in TS 38.211. + +In NR the channel spacing for intra-band contiguous carrier aggregation can be adjusted to any multiple of least common multiple of channel raster and sub-carrier spacing less than the nominal channel spacing to optimize performance in a particular deployment scenario. + +## 4.5.2 Channel raster + +The GSM/EDGE channel raster is 200 kHz for all bands [6]. + +The UTRA FDD and TDD 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 for UTRA FDD according to [3], which means that the centre frequencies for UTRA FDD channels are shifted 100 kHz relative to the general raster. + +The E-UTRA channel raster is 100 kHz for all bands, which means that the carrier centre frequency must be an integer multiple of 100 kHz [5]. + +NB-IoT channel raster is 100 kHz for all bands [5]. + +NR channel raster is specified in clause 5.4.2 of TS 38.104 [27]. + +## 4.5.3 Carrier frequencies and numbering + +The carrier frequencies and corresponding numbering is defined for each RAT in the respective specifications TS 38.104 [27], TS 36.104 [5] TS 25.104 [3], TS 25.105 [4] and TS 45.005 [6]. In the context of MSR, the frequency numbering scheme for each RAT will remain. + +- The E-UTRA carrier frequency numbering (EARFCN) is defined in clause 5.7 of TS 36.104 [5]. + +- The UTRA FDD carrier frequency numbering (UARFCN) is defined in clause 5.4 of TS 25.104 [3]. +- The UTRA TDD carrier frequency numbering (UARFCN) is defined in clause 5.4 of TS 25.105 [4]. +- The GSM/EDGE carrier frequency numbering (ARFCN) is defined clause 2 of TS 45.005 [6]. +- The NB-IoT carrier frequency numbering is defined in clause 5.7 of TS 36.104 [5]. +- The NR carrier frequency numbering (NR-ARFCN) is defined in clause 5.4.2.3 of TS 38.104 [27]. + +NOTE: The numbering schemes for UTRA FDD and TDD are not coordinated, while both are called UARFCN. + +## 4.6 Manufacturer's declarations of regional and optional requirements + +### 4.6.1 Operating band and frequency range + +The manufacturer shall declare which operating band(s) specified in clause 4.4 that is supported by the BS under test and if applicable, which frequency ranges within the operating band(s) that the Base Station can operate in. Requirements for other operating bands and frequency ranges need not be tested. + +The manufacturer shall declare which operating band(s) specified in clause 4.4 are supported by the BS under test for carrier aggregation. + +The manufacturer shall declare which NB-IoT operating mode (standalone, NB-IoT operation in E-UTRA in-band and/or guard band, NB-IoT operation in NR in-band) the BS supports for the declared supported band. + +For standalone NB-IoT operating mode, the manufacturer shall declare the number of supported NB-IoT carriers. + +For each supported E-UTRA channel bandwidth, the manufacturer shall declare if BS supports NB-IoT in-band and/or guard band operation and the number of supported NB-IoT PRBs. + +For each supported NR channel bandwidth, manufacturer shall declare if BS supports NB-IoT operation in NR in-band and the number of supported NB-IoT PRBs. + +### 4.6.2 Spurious emissions category + +The manufacturer shall declare one of the following: + +- a) The BS is tested against Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [13]. In this case + - conformance with the spurious emissions requirements in clause 6.6.1.5.1 is mandatory, and the requirements specified in clause 6.6.1.5.2 and 6.6.1.5.3 need not be demonstrated. +- b) The BS is tested against Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [13]. In this case, + - conformance with the spurious emissions requirements in clause 6.6.1.5.2 and 6.6.1.5.3 (for BC2) are mandatory, and the requirements specified in clause 6.6.1.5.1 need not be demonstrated. + +### 4.6.3 Additional operating band unwanted emissions + +The manufacturer shall declare whether the BS under test is intended to operate in geographic areas where the additional operating band unwanted emission limits defined in clause 6.6.2.4 of TS 37.104 [2] apply. If this is the case, conformance with the applicable emission limits shall be demonstrated. + +NOTE: For the emission limits established by FCC Title 47 [8], there is no test method or requirement defined in the present specification. + +For a BS declared to support Band 20 and to operate in geographic areas within the CEPT in which frequencies are allocated to broadcasting (DTT) service, the manufacturer shall additionally declare the following quantities associated with the applicable test conditions of Table 6.6.2.5.4.4-1 and information in annex G of TS 36.104 [5] : + +$P_{EM,N}$ Declared emission level for channel N + +$P_{10MHz}$ Maximum output Power in 10 MHz + +Conformance with the declared emission level $P_{EM,N}$ shall be demonstrated. + +For a BS declared to support Band 32, 75 or 76 and to operate in geographic areas within the CEPT, the manufacturer shall additionally declare the following quantities associated with the applicable test conditions of Table 6.6.2.5.4.6-1 and Table 6.6.2.5.4.6-2: + +$P_{EM,B32,B75,B76,ind}$ Declared emission level in Band 32, Band 75 and Band 76, ind=a, b, c + +$P_{EM,B32,ind}$ Declared emission level in Band 32, ind= d, e + +Conformance with the declared emission level $P_{EM,B32,B75,B76,ind}$ and $P_{EM,B32,ind}$ shall be demonstrated. + +For a BS declared to support Band 50, 74 or 75 and to operate in geographic areas where the additional unwanted emission limit defined in Table 6.6.2.5.4.6-3 applies, the manufacturer shall additionally declare the following quantity associated with the applicable test conditions of Table 6.6.2.5.4.6-3: + +$P_{EM,B50,B74,B75,ind}$ Declared emission level for Band 50, Band 74 and Band 75, ind=a,b + +Conformance with the declared emission level $P_{EM,B50,B74,B75,ind}$ shall be demonstrated. + +For a BS declared to support Band 54 and to operate in geographic areas where the additional unwanted emission limit defined in Table 6.6.1.5.5-7 applies, the manufacturer shall additionally declare the following quantity associated with the applicable test conditions of Table 6.6.1.5.5-7: + +$P_{EM,B54,ind}$ Declared emission level for Band 54, ind=a,b,c,d,e,f + +Conformance with the declared emission level $P_{EM,B54,ind}$ shall be demonstrated. + +#### 4.6.4 Co-existence with other systems + +The manufacturer shall declare whether the BS under test is intended to operate in geographic areas where one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD, E-UTRA, NR and/or PHS operating in another band are deployed. If this is the case, conformance with the applicable test requirement for spurious emissions specified in clause 6.6.1.5.5 shall be demonstrated. + +#### 4.6.5 Co-location with other Base Stations + +The manufacturer shall declare whether the BS under test is intended to operate co-located with Base Stations of one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD, E-UTRA and/or NR operating in another band. If this is the case, + +- Conformance with the applicable test requirement for spurious emissions specified in clause 6.6.1.5.6 shall be demonstrated. +- Conformance with the applicable test requirement for receiver blocking specified in clause 7.5.5.2 shall be demonstrated. + +#### 4.6.6 NB-IoT sub-carrier spacing + +If the BS supports NB-IoT, manufacturer shall declare if it supports 15 kHz sub-carrier spacing, 3.75 kHz sub-carrier spacing, or both for NPUSCH. + +## 4.6.7 NB-IoT power dynamic range + +If the BS supports E-UTRA with NB-IoT operating in-band and/or in guard band, manufacturer shall declare the maximum power dynamic range it could support with a minimum of +6dB as mentioned in TS 36.104 [5] clause 6.3.3. + +If the BS supports 5 MHZ E-UTRA with NB-IoT operating in guard band, manufacturer shall also declare the maximum power that could be allocated to this NB-IoT PRB. + +If the BS supports NB-IoT operation in NR in-band, manufacturer shall declare the maximum power dynamic range it could support with a minimum requirement as defined in TS 38.104 [27] clause 6.3.4. + +## 4.7 Capability set definition and manufacturer's declarations of supported RF configurations + +### 4.7.1 Definition of Capability Sets (CS) + +Capability set is defined as the BS capability to support certain RAT combinations in an operating band. + +The manufacturer shall declare the supported capability set(s) according to Table 4.7.1-1 and Table 4.7.1-2 for each supported operating band. + +**Table 4.7.1-1: Capability sets** + +| Capability Set supported by the BS | CS1 | CS2 | CS3 | CS4 | CS5 | CS6 | CS7 | +|------------------------------------|------------------|-------------------------------------|------------------------------------------------------------------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported RATs | UTRA (MC) | E-UTRA (MC) 3 | UTRA, E-UTRA 3 | GSM, UTRA | GSM, E-UTRA 3 | GSM, UTRA, E-UTRA | GSM, UTRA, E-UTRA 3 | +| Supported configurations | SR UTRA (SC, MC) | SR E-UTRA 3 (SC, MC, CA) | MR UTRA + E-UTRA 3
SR UTRA (SC, MC)
SR E-UTRA 3 (SC, MC, CA) | MR GSM + UTRA
SR GSM (MCBTS)
SR UTRA (SC, MC) | MR GSM + E-UTRA 3
SR GSM (MCBTS)
SR E-UTRA 3 (SC, MC, CA) | MR GSM + UTRA + E-UTRA
MR GSM + UTRA
MR GSM + E-UTRA
MR UTRA + E-UTRA
SR GSM (MCBTS)
SR UTRA (SC, MC)
SR E-UTRA (SC, MC, CA) | MR GSM + UTRA 2
MR GSM + E-UTRA 3
MR E-UTRA 3 + UTRA 2
SR UTRA (SC, MC) 2
SR E-UTRA 3 (SC, MC) | +| Applicable BC | BC1, BC2 or BC3 | BC1, BC2 or BC3 | BC1, BC2 or BC3 | BC2 | BC2 | BC2 | BC2 | + +NOTE 1: MC denotes multi-carrier in single RAT; +SC denotes single carrier; +MR denotes multi-RAT; +SR denotes single-RAT. + +NOTE 2: For this configuration related to BC2 bands, the support of UTRA in band 3 is declared by the manufacturer. + +NOTE 3: Includes optional (declared by the manufacturer) support of NB-IoT in-band and/or NB-IoT guard band operation within E-UTRA carrier(s) + +NOTE 4: Void + +NOTE 5: Void + +**Table 4.7.1-1A: Capability sets** + +| Capability Set supported by the BS | CS16 | CS18 | CS19 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported RATs | NR4, E-UTRA3 | GSM, E-UTRA3, NR4 | UTRA, E-UTRA3, NR4 | +| Supported configurations | MR E-UTRA 3 + NR 4
SR NR 4 (SC, MC, CA)
SR E-UTRA 3 (SC, MC, CA) | SR E-UTRA 3 (SC, MC, CA)
SR NR 4 (SC, MC, CA)
MR GSM + E-UTRA 3
MR GSM + NR 4
MR E-UTRA 3 + NR 4
MR GSM + E-UTRA 3 + NR 4 | SR UTRA (SC, MC)
SR E-UTRA 3 (SC, MC, CA)
SR NR 4 (SC, MC, CA)
MR UTRA + E-UTRA 3
MR UTRA + NR 4
MR E-UTRA 3 + NR 4
MR UTRA + E-UTRA 3 + NR 4 | +| Applicable BC | BC1, BC2 or BC3 | BC2 | BC1, BC2 | +| NOTE 1: MC denotes multi-carrier in single RAT;
SC denotes single carrier;
MR denotes multi-RAT;
SR denotes single-RAT.
NOTE 2: For this configuration related to BC2 bands, the support of UTRA in band 3 is declared by the manufacturer.
NOTE 3: Includes optional (declared by the manufacturer) support of NB-IoT in-band and/or NB-IoT guard band operation within E-UTRA carrier(s)
NOTE 4: Includes optional (declared by the manufacturer) support of NB-IoT operation in NR in-band within NR carrier(s). | | | | + +**Table 4.7.1-2 Capability sets with NB-IoT standalone operation** + +| Capability Set supported by the BS | CS8 | CS9 | CS10 | CS11 | CS12 | CS13 | CS14 | CS15 | CS17 | +|------------------------------------|-------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported RATs | NB-IoT standalone | GSM, NB-IoT standalone | UTRA, NB-IoT standalone | E-UTRA, NB-IoT standalone | GSM, UTRA, NB-IoT standalone | GSM, E-UTRA, NB-IoT standalone | UTRA, E-UTRA, NB-IoT standalone | GSM, UTRA, E-UTRA, NB-IoT standalone | NR 6 , E-UTRA 3 , NB-IoT standalone | +| Supported configurations | SR NB-IoT standalone (SC, MC) | MR GSM + NB-IoT standalone
SR GSM (MCBTS)
SR NB-IoT standalone (SC, MC) | MR UTRA + NB-IoT standalone
SR UTRA (SC, MC)
SR NB-IoT standalone (SC, MC) | MR E-UTRA + NB-IoT standalone
SR E-UTRA (SC, MC, CA)
SR NB-IoT standalone (SC, MC) | MR GSM + UTRA + NB-IoT standalone
SR GSM (MCBTS)
SR UTRA (SC, MC)
SR NB-IoT standalone (SC, MC)
MR GSM + NB-IoT standalone
MR UTRA + NB-IoT standalone
MR GSM + UTRA | MR GSM + E-UTRA + NB-IoT standalone
SR GSM (MCBTS)
SR E-UTRA (SC, MC, CA)
SR NB-IoT standalone (SC, MC)
MR GSM + NB-IoT standalone
MR E-UTRA + NB-IoT standalone
MR GSM + E-UTRA | MR UTRA + E-UTRA + NB-IoT standalone
SR UTRA (SC, MC)
SR E-UTRA (SC, MC, CA)
SR NB-IoT standalone (SC, MC)
MR UTRA + NB-IoT standalone
MR E-UTRA + NB-IoT standalone
MR UTRA + E-UTRA | MR GSM + UTRA 2 + NB-IoT standalone
MR GSM + E-UTRA + NB-IoT standalone
MR UTRA 2 + E-UTRA + NB-IoT standalone
MR GSM + NB-IoT standalone
MR UTRA 2 + NB-IoT standalone
MR GSM + UTRA 2
MR GSM + E-UTRA
MR E-UTRA + UTRA 2
SR UTRA (SC, MC) 2 | MR E-UTRA 3 + NR 6
SR NR 6 (SC, MC, CA)
SR E-UTRA 3 (SC, MC, CA)
SR NB-IoT standalone (SC, MC)
MR E-UTRA 3 + NB-IoT standalone
MR NR 6 + NB-IoT standalone
MR NR 6 + E-UTRA 3 + NB-IoT standalone | + +| | | | | | | | | | | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----|--------------------|--------------------|-----|-----|--------------------|-------------------------------------|--------------------| +| | | | | | | | | SR E-UTRA
(SC, MC) | | +| | | | | | | | | SR NB-IoT
standalone
(SC, MC) | | +| Applicable
BC | BC1, BC2
or BC3 | BC2 | BC1, BC2
or BC3 | BC1, BC2
or BC3 | BC2 | BC2 | BC1, BC2
or BC3 | BC2 | BC1, BC2 or
BC3 | +| NOTE 1: | MC denotes multi-carrier in single RAT;
SC denotes single carrier;
MR denotes multi-RAT;
SR denotes single-RAT. | | | | | | | | | +| NOTE 2: | For this configuration related to BC2 bands, the support of UTRA in band 3 is declared by the manufacturer. | | | | | | | | | +| NOTE 3: | Includes optional (declared by the manufacturer) support of NB-IoT in-band and/or NB-IoT guard band operation within E-UTRA carrier(s). | | | | | | | | | +| NOTE 4: | Void | | | | | | | | | +| NOTE 5: | Void | | | | | | | | | +| NOTE 6: | Includes optional (declared by the manufacturer) support of NB-IoT operation in NR in-band within NR carrier(s). | | | | | | | | | + +The applicable test configurations for each RF requirement are defined in clause 5.1 and 5.2 for the declared capability set(s). For a BS declared to be capable of multi-band operation, the applicable test configurations for each RF requirement are defined in clause 5.3 for the declared capability set(s). + +NOTE: Not every supported configuration within a CS is tested, but the tables in clause 5.1, 5.2 and 5.3 provide a judicious choice among the supported configurations and test configurations to ensure proper test coverage. + +## 4.7.2 Manufacturer's declarations of supported RF configurations + +The manufacturer shall declare which operational configurations the BS supports by declaring the following parameters: + +a) General Parameters: + +- Support of the BS in non-contiguous spectrum operation. If the BS does not support non-contiguous spectrum operation the parameters for non-contiguous spectrum operation below shall not be declared. +- The supported operating bands defined in clause 4.4. +- The frequency range within the above frequency band(s) supported by the BS. +- Supported capability set(s) in each supported operating band +- The maximum Base Station RF Bandwidth supported by a MSR BS within an operating band when the BS is configured with carriers of different RATs. + - for contiguous spectrum operation. + - for non-contiguous spectrum operation +- The rated total output power as a sum over all RATs + - for contiguous spectrum operation. + - for non-contiguous spectrum operation + +NOTE 1: If a BS is capable of 256QAM DL operation but not capable of 1024QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. + +NOTE 2: If a BS is capable of 1024QAM DL operation then up to three rated output power declarations may be made. One declaration is applicable when configured for 1024QAM transmissions, a different declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when configured neither for 256 nor 1024QAM transmissions. + +- Maximum supported power difference between carriers +- Total number of supported carriers + +For MSR BS supporting CS7, the rated total output power as a sum over all RATs, total number of supported carriers and the maximum Base Station RF Bandwidth is declared in e). + +If the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, the manufacturer shall declare the following additional parameters: + +- The reduced number of supported carriers at the rated total output power in Multi-RAT operations (i.e. < total number of supported carriers) +- The reduced total output power at the total number of supported carriers in Multi-RAT operations (i.e. < rated total output power) + +NOTE 1: If a BS is capable of 256QAM DL operation but not capable of 1024QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. + +NOTE 2: If a BS is capable of 1024QAM DL operation then up to three rated output power declarations may be made. One declaration is applicable when configured for 1024QAM transmissions, a different declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when configured neither for 256 nor 1024QAM transmissions. + +b) Parameters related to operation of GSM: + +- The maximum number of supported GSM carriers +- The maximum Base Station RF Bandwidth supported by the MSR BS when configured with GSM carriers only + - for contiguous spectrum operation + - for non-contiguous spectrum operation +- The rated carrier output power for GSM for each supported number of GSM carriers up to the maximum, for the case that all carriers are operated at the same nominal output power. + - for contiguous spectrum operation + - for non-contiguous spectrum operation + +The declaration shall be given for each supported modulation. + +c) Parameters related to operation of UTRA: + +- The maximum number of supported UTRA carriers +- The maximum Base Station RF Bandwidth supported by the MSR BS when configured with UTRA carriers only + - for contiguous spectrum operation + - for non-contiguous spectrum operation +- The rated RAT output power for UTRA as a sum of all UTRA carriers + - for contiguous spectrum operation + - for non-contiguous spectrum operation + +- The rated carrier output power for UTRA + - for contiguous spectrum operation + - for non-contiguous spectrum operation + +d) Parameters related to operation of E-UTRA: + +- Which of the E-UTRA channel bandwidths specified in TS 36.104 [5] clause 5.6 are supported +- The maximum number of supported E-UTRA carriers +- The maximum Base Station RF Bandwidth supported by the MSR BS when configured with E-UTRA carriers only + - for contiguous spectrum operation + - for non-contiguous spectrum operation + +The rated RAT output power for E-UTRA as a sum of all E-UTRA carriers + +- for contiguous spectrum operation +- for non-contiguous spectrum operation + +NOTE 1: If a BS is capable of 256QAM DL operation but not capable of 1024QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. + +NOTE 2: If a BS is capable of 1024QAM DL operation then up to three rated output power declarations may be made. One declaration is applicable when configured for 1024QAM transmissions, a different declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when configured neither for 256 nor 1024QAM transmissions. + +- The rated carrier output power for E-UTRA + - for contiguous spectrum operation + - for non-contiguous spectrum operation + +NOTE 1: If a BS is capable of 256QAM DL operation but not capable of 1024QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. + +NOTE 2: If a BS is capable of 1024QAM DL operation then up to three rated output power declarations may be made. One declaration is applicable when configured for 1024QAM transmissions, a different declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when configured neither for 256 nor 1024QAM transmissions. + +- The supported component carrier combinations at nominal channel spacing within each operating band. + +e) Parameters related to CS7: + +- The RAT combinations can be categorized into two sub-groups, where all RAT combinations of both sub-groups are mandatory. + - Sub-group 1: + - MR UTRA+E-UTRA + - SR UTRA + - SR E-UTRA + - Sub-group 2: + - MR GSM+UTRA + +- MR GSM+E-UTRA +- For above CS7 configurations including UTRA and related to BC2 bands, the manufacturer shall declare support of UTRA in Band 3. +- Total number of supported carriers + - for Sub-group 1 + - for Sub-group 2 +- The manufacturer shall declare the rated total output power as a sum over all RATs and the maximum Base Station RF Bandwidth supported by the MSR BS for Sub-group 1 + - for contiguous spectrum operation + - for non-contiguous spectrum operation +- The manufacturer shall declare the rated total output power as a sum over all RATs and the maximum Base Station RF Bandwidth supported by the MSR BS for Sub-group 2 + - for contiguous spectrum operation + - for non-contiguous spectrum operation + +f) Parameters related to operation of NR: + +- Which of the NR channel bandwidths and SCS specified in TS 38.104 [27] clause 5.3 are supported +- The maximum number of supported NR carriers +- The maximum Base Station RF Bandwidth supported by the MSR BS when configured with NR carriers only + - for contiguous spectrum operation + - for non-contiguous spectrum operation + +The rated RAT output power for NR as a sum of all NR carriers + +- for contiguous spectrum operation +- for non-contiguous spectrum operation + +NOTE 1: If a BS is capable of 256QAM DL operation but not capable of 1024QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. + +NOTE 2: If a BS is capable of 1024QAM DL operation then up to three rated output power declarations may be made. One declaration is applicable when configured for 1024QAM transmissions, a different declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when configured neither for 256 nor 1024QAM transmissions. + +- The rated carrier output power for NR + - for contiguous spectrum operation + - for non-contiguous spectrum operation + +NOTE 1: If a BS is capable of 256QAM DL operation but not capable of 1024QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. + +NOTE 2: If a BS is capable of 1024QAM DL operation then up to three rated output power declarations may be made. One declaration is applicable when configured for 1024QAM transmissions, a different declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when configured neither for 256 nor 1024QAM transmissions. + +- The supported component carrier combinations at nominal channel spacing within each operating band. + +For BS capable of multi-band operation, the parameters in a) to e) shall be declared for each supported operating band, in which declarations of supported capability set, the maximum Base Station RF Bandwidth, total number of supported carriers, the rated carrier output power and rated total output power are applied for single-band operation only. In addition the manufacturer shall declare the following additional parameters for BS capable of multi-band operation: + +- Supported operating band combinations of the BS +- Supported operating band(s) of each antenna connector +- Supported capability set in each supported operating band in multi-band operation +- Support of multi-band transmitter and/or multi-band receiver, including mapping to antenna connector(s) +- Total number of supported carriers for the declared band combinations of the BS +- Maximum number of supported carriers per band in multi-band operation +- Total RF Bandwidth of transmitter and receiver for the declared band combinations of the BS +- Maximum Base Station RF Bandwidth of each supported operating band in multi-band operation +- Maximum Radio Bandwidth in transmit and receive direction for the declared band combinations of the BS +- Any other limitations under simultaneous operation in the declared band combinations of the BS which have any impact on the test configuration generation +- Rated total output power as a sum over all supported operating bands in the declared band combinations of the BS +- Maximum supported power difference between any two carriers in any two different supported operating bands +- The rated carrier output power in multi-band operation +- Rated total output power of each supported operating band in multi-band operation + +NOTE: Certain parameter combinations may result in test configurations that are not possible to use for testing. The manufacturer shall ensure that the declared parameters generate test configurations possible to use for test. + +## 4.8 MSR test configurations + +The test configurations shall be constructed using the methods defined below subject to the parameters declared by the manufacturer as listed in clause 4.7. + +For test contiguous operation configurations used in receiver tests only the outermost carriers need to be generated by the test equipment. For non-contiguous operation test configurations used in receiver tests, outermost carriers for each sub-block need to be generated by the test equipment. + +The applicable test models for generation of the carrier transmit test signal are defined in clause 4.9.2. + +NOTE: In case carriers are shifted to align with the channel raster Foffset, RAT as defined in clauses 4.4.1 and 4.4.2 may be different. + +### 4.8.1 TC1: UTRA multicarrier operation + +The purpose of TC1 is to test UTRA multi-carrier aspects. + +#### 4.8.1.1 TC1a generation + +TC1a is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. + +- Place two UTRA FDD carriers adjacent to the upper and lower Base Station RF Bandwidth edges. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, alternately place a UTRA FDD carrier adjacent to the already placed carriers at the lower and upper Base Station RF Bandwidth edges until there is no more space to fit a carrier or the BS does not support more carriers. The nominal carrier spacing defined in clause 4.5.1 shall apply. +- The carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. + +#### 4.8.1.2 TC1b generation + +TC1b is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place two UTRA TDD carriers adjacent to the upper and lower Base Station RF Bandwidth edges. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, alternately place a UTRA TDD carrier adjacent to the already placed carriers at the lower and upper Base Station RF Bandwidth edges until there is no more space to fit a carrier or the BS does not support more carriers. The nominal carrier spacing defined in clause 4.5.1 shall apply. + +#### 4.8.1.3 TC1 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated RAT output power for UTRA according to the manufacturer's declaration in clause 4.7.2 c). + +### 4.8.1a NTC1: UTRA multicarrier non-contiguous operation + +The purpose of NTC1 is to test UTRA multicarrier non-contiguous aspects. + +#### 4.8.1a.1 NTC1a generation + +The purpose of NTC1a is to test UTRA multicarrier non-contiguous aspects. NTC1a is constructed using the following method: + +- The Base Station RF Bandwidth shall be the maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- For transmitter tests, place one UTRA carrier adjacent to the upper Base Station RF Bandwidth edge and one UTRA carrier adjacent to the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For receiver tests, place one UTRA carrier adjacent to the upper Base Station RF Bandwidth edge and one UTRA carrier adjacent to the lower Base Station RF Bandwidth edge. +- For single-band operation receiver tests, if the maximum Base Station RF Bandwidth is at least 35 MHz and the BS supports at least 4 UTRA FDD carriers, place a UTRA FDD carrier adjacent to each already placed carrier for each sub-block. The nominal carrier spacing defined in clause 4.5.1 shall apply. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier adjacent to the sub-block gap. +- The UTRA FDD carrier in the lower sub-block may be shifted maximum 100 kHz towards lower frequencies and the UTRA FDD carrier in the upper sub-block may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. + +#### 4.8.1a.2 NTC1 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated RAT output power according to the manufacturer's declaration in clause 4.7.2 c). + +## 4.8.2 TC2: E-UTRA multicarrier operation + +The purpose of the TC2 is to test E-UTRA multi-carrier aspects. + +### 4.8.2.1 TC2 generation + +TC2 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Select the narrowest supported E-UTRA carrier and place it adjacent to the lower Base Station RF Bandwidth edge. Place a 5 MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, select as many 5 MHz E-UTRA carriers that the BS supports and that fit in the rest of the Base Station RF Bandwidth. Place the carriers adjacent to each other starting from the high Base Station RF Bandwidth edge. The nominal carrier spacing defined in clause 4.5 shall apply. The specified $F_{\text{Offset-RAT}}$ shall apply. +- If 5 MHz E-UTRA carriers are not supported by the BS the narrowest supported channel BW shall be selected instead. + +### 4.8.2.2 TC2 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated RAT output power for E-UTRA according to the manufacturer's declaration in sub clause 4.7.2 d). + +## 4.8.2a NTC2: E-UTRA multicarrier non-contiguous operation + +The purpose of NTC2 is to test E-UTRA multicarrier non-contiguous aspects. + +### 4.8.2a.1 NTC2 generation + +The purpose of NTC2 is to test E-UTRA multicarrier non-contiguous aspects. NTC2 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- For transmitter tests, place a 5MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge and a 5MHz E-UTRA carrier adjacent to the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. +- For receiver tests, place a 5MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge and a 5MHz E-UTRA carrier adjacent to the lower Base Station RF Bandwidth edge. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. +- For single-band operation receiver tests, if the remaining gap is at least 15 MHz plus two times the channel BW used in the previous step and the BS supports at least 4 E-UTRA carriers, place a E-UTRA carrier of this BW adjacent to each already placed carrier for each sub-block. The nominal carrier spacing defined in clause 4.5.1 shall apply. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier adjacent to the sub-block gap. + +### 4.8.2a.2 NTC2 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated RAT output power according to the manufacturer's declaration in clause 4.7.2 d). + +### 4.8.3 TC3: UTRA and E-UTRA multi RAT operation + +The purpose of TC3 is to test UTRA and E-UTRA multi-RAT aspects. + +If the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, two instances of TC3 shall be generated using the following values for rated total output power and the total number of supported carriers: + +- 1) The rated total output power and the reduced number of supported carriers at the rated total output power in Multi-RAT operations +- 2) The reduced total output power at the total number of supported carriers in Multi-RAT operations and the total number of supported carriers. + +Tests that use TC3 shall be performed using both instances 1) and 2) of TC3. + +#### 4.8.3.1 TC3a generation + +TC3a is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Select an FDD UTRA carrier to be placed at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- Place a 5 MHz E-UTRA carrier at the upper Base Station RF Bandwidth edge. If that is not possible use the narrowest E-UTRA carrier supported by the BS. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, alternately add FDD UTRA carriers at the low end and 5 MHz E-UTRA carriers at the high end adjacent to the already placed carriers until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. The nominal carrier spacing defined in clause 4.5.1 shall apply. + +#### 4.8.3.2 TC3b generation + +TC3b is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Select a UTRA TDD carrier to be placed at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place a 5 MHz E-UTRA carrier at the upper Base Station RF Bandwidth edge. If that is not possible use the narrowest E-UTRA carrier supported by the BS. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, alternately add UTRA TDD carriers at the low end and 5 MHz E-UTRA carriers at the high end adjacent to the already placed carriers until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. The nominal carrier spacing defined in clause 4.5.1 shall apply. + +#### 4.8.3.3 TC3 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2 c) and d). + +### 4.8.3a NTC3: UTRA and E-UTRA multi RAT non-contiguous operation + +The purpose of NTC3 is to test UTRA and E-UTRA multi RAT non-contiguous aspects. + +#### 4.8.3a.1 NTC3 generation + +The purpose of NTC3 is to test UTRA and E-UTRA multi RAT non-contiguous aspects. NTC3 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- For transmitter tests, place an UTRA carrier at the lower RF Bandwidth edge and a 5 MHz E-UTRA carrier at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. The UTRA FDD carrier may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. In case rated total output power is not reached, the narrowest E-UTRA channel BW which supports rated carrier output power shall be selected. If still there are some output power room, alternately place an E-UTRA carrier of this BW adjacent to the carrier at the lower Base Station RF Bandwidth edge and UTRA carrier adjacent to the carrier at the upper Base Station RF Bandwidth edge until the rated total output power or the total number of supported carriers is reached. +- For receiver tests, place an UTRA carrier at the lower RF Bandwidth edge and a 5 MHz E-UTRA carrier at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. The UTRA FDD carrier may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- For single-band operation receiver tests, if the remaining gap is at least 20 MHz plus the channel BW of the E-UTRA carrier used in the previous step and the BS supports at least 2 UTRA and 2 E-UTRA carriers, place a E-UTRA carrier of this BW adjacent to the carrier at the lower Base Station RF Bandwidth edge and UTRA carrier adjacent to the carrier at the upper Base Station RF Bandwidth edge. The nominal carrier spacing defined in clause 4.5.1 shall apply. The UTRA FDD carrier may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier adjacent to the sub-block gap. + +#### 4.8.3.a.2 NTC3 power allocation + +Set the power of each carrier to the same power unless the rated carrier output power for RATs are different so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2 c) and d). + +#### 4.8.4 TC4: BC2 transmitter operation + +The purpose of TC4 is to test multi-RAT operations with GSM for the transmitter. + +If the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, two instances of TC4 shall be generated using the following values for rated total output power and the total number of supported carriers: + +- 1) The rated total output power and the reduced number of supported carriers at the rated total output power in Multi-RAT operations +- 2) The reduced rated total output power at the total number of supported carriers in Multi-RAT operations and the total number of supported carriers. + +If the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, tests that use TC4 shall be performed using both instances 1) and 2) of TC4, except tests for modulation accuracy in which only TC4 according to 2) shall be used. + +##### 4.8.4.1 TC4a generation + +TC4a is only applicable for a BS that supports UTRA and GSM. TC4a is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- In the case of a BS supporting only one GSM carrier and one UTRA carrier, place a GSM carrier at the lower edge and a UTRA carrier at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply + +- Place a GSM carrier at the upper edge and a GSM carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place two UTRA FDD carriers in the middle of the Base Station RF Bandwidth. If two UTRA FDD carriers do not fit, place only one carrier in the middle of the Base Station RF Bandwidth. The UTRA FDD carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. +- Add GSM carriers at the edges using 600 kHz spacing until no more GSM carriers are supported or no more GSM carriers fit. +- Add additional UTRA FDD carriers in the middle if possible. + +#### 4.8.4.2 TC4b generation + +TC4b is only applicable for a BS that supports E-UTRA and GSM. TC4b is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- In the case of a BS supporting only one GSM carrier and one E-UTRA carrier, place a GSM carrier at the lower edge and a E-UTRA carrier at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place a GSM carrier at the upper edge and a GSM carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place two 5 MHz E-UTRA carriers in the middle of the Base Station RF Bandwidth. If the BS does not support 5 MHz channel BW use the narrowest supported BW, if two carriers do not fit place only one carrier. +- Add GSM carriers at the edges using 600 kHz spacing until no more GSM carriers are supported or no more GSM carriers fit. +- Add additional E-UTRA carriers of the same bandwidth as the already allocated E-UTRA carriers in the middle if possible. + +#### 4.8.4.3 TC4c generation + +TC4c is only applicable for a BS that supports UTRA, E-UTRA and GSM. TC4c is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a GSM carrier at the upper edge and a GSM carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- In the case of a BS supporting only one GSM carrier and one E-UTRA or UTRA carrier, place a GSM carrier at the lower edge and a E-UTRA carrier at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place one 5 MHz E-UTRA carrier and one UTRA carrier in the middle of the Base Station RF Bandwidth. If the BS does not support 5 MHz E-UTRA channel BW use the narrowest supported BW. The carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. +- Add GSM carriers at the edges using 600 kHz spacing until no more GSM carriers are supported or no more GSM carriers fit. +- Add additional UTRA and E-UTRA carriers in the middle if possible. For E-UTRA the same bandwidth as the already allocated E-UTRA carriers shall be used. + +#### 4.8.4.4 TC4d generation + +TC4d is only applicable for a BS that supports UTRA and GSM. TC4d is only applicable when any of the following conditions is satisfied: + +- 1) The declared Base Station RF Bandwidth for GSM single-RAT operation is not equal to the declared Base Station RF Bandwidth for multi-RAT operations and the frequency range supported by the BS is a subset of the operating band. +- 2) The maximum Base Station RF Bandwidth covers the entire operating band. + +TC4d is constructed using the following method: + +- The Base Station RF Bandwidth shall be 600 kHz less than the declared maximum Base Station RF Bandwidth. +- The Base Station RF Bandwidth shall be adjacent to the high end of the frequency range supported by the BS. +- Place a GSM carrier at the lower Base Station RF Bandwidth edge. Add one GSM carrier, if the BS supports more than one GSM carrier, at the lower edge using 600 kHz spacing. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place one UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. The carrier may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. + +#### 4.8.4.5 TC4e generation + +TC4e is only applicable for a BS that supports E-UTRA and GSM. TC4e is only applicable when any of the following conditions is satisfied: + +- 1) The declared Base Station RF Bandwidth for GSM single-RAT operation is not equal to the declared Base Station RF Bandwidth for multi-RAT operations and the frequency range supported by the BS is a subset of the operating band. +- 2) The maximum Base Station RF Bandwidth covers the entire operating band. + +TC4e is constructed using the following method: + +- The Base Station RF Bandwidth shall be 600 kHz less than the declared maximum Base Station RF Bandwidth. +- The Base Station RF Bandwidth shall be adjacent to the upper edge of the frequency range supported by the BS. +- Place a GSM carrier at the lower Base Station RF Bandwidth edge. Add one GSM carrier, if the BS supports more than one GSM carrier, at the lower edge using 600 kHz spacing. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place one 5 MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. If the BS does not support 5 MHz channel BW use the narrowest supported BW. The specified $F_{\text{Offset-RAT}}$ shall apply. + +#### 4.8.4.6 TC4 power allocation + +- a) Unless otherwise stated, set each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to manufacturer's declarations in clause 4.7.2 a) +- b) In case that TC4 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in clause 4.7.2, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacture's declaration, the power in the other RAT(s) does not need to be increased. + +#### 4.8.4a NTC4: Non-contiguous multi RAT operations with GSM for the transmitter + +The purpose of NTC4 is to test non-contiguous multi RAT operations with GSM for the transmitter. + +If the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, two instances of NTC4 shall be generated using the following values for rated total output power and the total number of supported carriers: + +- 1) The rated total output power and the reduced number of supported carriers at the rated total output power in Multi-RAT operations +- 2) The reduced rated total output power at the total number of supported carriers in Multi-RAT operations and the total number of supported carriers. + +If the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, tests that use NTC4 shall be performed using both instances 1) and 2) of NTC4, except: + +- 1) Tests for modulation accuracy in which only NTC4 according to 2) shall be used. +- 2) If the reduced number of supported carriers is 6 or more, only instance 1) of NTC4 shall be used. + +#### 4.8.4a.1 NTC4a generation + +NTC4a is only applicable for a BS that supports UTRA and GSM. NTC4a is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. The sub-block bandwidth shall be equal to 6MHz. +- If the BS supports up to 3 carriers, place one GSM carrier adjacent to the lower sub-block edge and one GSM carrier adjacent to the upper sub-block edge of the lower sub-block. Place a UTRA FDD carrier adjacent to the upper Base Station RF Bandwidth edge. The upper sub-block edge adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the UTRA carrier in the upper sub-block. The UTRA FDD carrier may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. +- If the BS supports up to 4 carriers, place one GSM carrier adjacent to the lower Base Station RF Bandwidth edge and one GSM carrier adjacent to the upper Base Station RF Bandwidth edge. Place one UTRA FDD carrier adjacent to the upper sub-block edge of the lower sub-block and one UTRA FDD carrier adjacent to the lower sub-block edge of the upper sub-block. The specified $F_{\text{Offset-RAT}}$ shall apply. The UTRA FDD carrier in the lower sub-block may be shifted maximum 100 kHz towards higher frequencies and the UTRA FDD carrier in the upper sub-block may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- If the BS supports up to 5 carriers, place one GSM carrier adjacent to the lower Base Station RF Bandwidth edge and one GSM carrier adjacent to the upper Base Station RF Bandwidth edge. Place one GSM carrier adjacent to the upper sub-block edge of the lower sub-block, one UTRA FDD carrier adjacent to the lower sub-block edge of the upper sub-block and one UTRA FDD carrier in the middle of the lower sub-block bandwidth. The specified $F_{\text{Offset-RAT}}$ shall apply. The UTRA FDD carrier in the upper sub-block may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- If the BS supports at least 6 carriers, place one GSM carrier adjacent to the lower Base Station RF Bandwidth edge and one GSM carrier adjacent to the upper Base Station RF Bandwidth edge. Place one GSM carrier adjacent to the upper sub-block edge of the lower sub-block and one GSM carrier adjacent to the lower sub-block edge of the upper sub-block. Place one UTRA FDD carrier in the middle of each sub-block bandwidth. The specified $F_{\text{Offset-RAT}}$ shall apply. + +#### 4.8.4a.2 NTC4b generation + +NTC4b is only applicable for a BS that supports E-UTRA and GSM. NTC4b is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- If the BS supports up to 3 carriers, place one GSM carrier adjacent to the lower sub-block edge and one GSM carrier adjacent to the upper sub-block edge of the lower sub-block. Place a 5MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. The lower sub-block bandwidth shall be equal to 6MHz. The upper sub-block edge adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier in the upper sub-block. + +- If the BS supports up to 4 carriers, place one GSM carrier adjacent to the lower Base Station RF Bandwidth edge and one GSM carrier adjacent to the upper Base Station RF Bandwidth edge. Place one E-UTRA FDD carrier adjacent to the upper sub-block edge of the lower sub-block and one 5MHz E-UTRA carrier adjacent to the lower sub-block edge of the upper sub-block. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. The sub-block bandwidth shall be equal to the bandwidth of the allocated non-GSM carrier in that sub-block plus 1MHz. The specified $F_{\text{Offset-RAT}}$ shall apply. +- If the BS supports up to 5 carriers, place one GSM carrier adjacent to the lower Base Station RF Bandwidth edge and one GSM carrier adjacent to the upper Base Station RF Bandwidth edge. Place one GSM carrier adjacent to the upper sub-block edge of the lower sub-block, Place one 5 MHz E-UTRA carrier adjacent to the lower sub-block edge of the upper sub-block and one 5MHz E-UTRA carrier in the middle of the lower sub-block bandwidth. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. The sub-block bandwidth shall be equal to the bandwidth of the allocated non-GSM carrier in that sub-block plus 1MHz. The specified $F_{\text{Offset-RAT}}$ shall apply. +- If the BS supports at least 6 carriers, place one GSM carrier adjacent to the lower Base Station RF Bandwidth edge and one GSM carrier adjacent to the upper Base Station RF Bandwidth edge. Place one GSM carrier adjacent to the upper sub-block edge of the lower sub-block and one GSM carrier adjacent to the lower sub-block edge of the upper sub-block. Place one 5MHz E-UTRA carrier in the middle of the lower sub-block bandwidth and one 5MHz E-UTRA carrier in the middle of the upper sub-block bandwidth. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. The sub-block bandwidth shall be equal to the bandwidth of the allocated non-GSM carrier in that sub-block plus 1MHz. The specified $F_{\text{Offset-RAT}}$ shall apply. + +#### 4.8.4a.3 NTC4c generation + +NTC4c is only applicable for a BS that supports UTRA, E-UTRA and GSM. NTC4c is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- If the BS supports up to 3 carriers, place one GSM carrier adjacent to the lower sub-block edge and one UTRA FDD carrier adjacent to the upper sub-block edge of the lower sub-block. Place a 5MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. The lower sub-block bandwidth shall be equal to 6MHz. The upper sub-block edge adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier in the upper sub-block. The UTRA FDD carrier may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. +- If the BS supports up to 4 carriers, place one GSM carrier adjacent to the lower Base Station RF Bandwidth edge and one GSM carrier adjacent to the upper Base Station RF Bandwidth edge. Place one UTRA FDD carrier adjacent to the upper sub-block edge of the lower sub-block and one 5MHz E-UTRA carrier adjacent to the lower sub-block edge of the upper sub-block. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. The sub-block bandwidth shall be equal to the bandwidth of the allocated non-GSM carrier in that sub-block plus 1MHz. The specified $F_{\text{Offset-RAT}}$ shall apply. The UTRA FDD carrier may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. +- If the BS supports up to 5 carriers, place one GSM carrier adjacent to the lower Base Station RF Bandwidth edge and one GSM carrier adjacent to the upper Base Station RF Bandwidth edge. Place one GSM carrier adjacent to the upper sub-block edge of the lower sub-block. Place one 5MHz E-UTRA carrier adjacent to the lower sub-block edge of the upper sub-block and one UTRA FDD carrier in the middle of the lower sub-block bandwidth. If 5 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW shall be selected instead. The sub-block bandwidth shall be equal to the bandwidth of the allocated non-GSM carrier in that sub-block plus 1MHz. The specified $F_{\text{Offset-RAT}}$ shall apply. +- If the BS supports at least 6 carriers, place one GSM carrier adjacent to the lower Base Station RF Bandwidth edge and one GSM carrier adjacent to the upper Base Station RF Bandwidth edge. Place one GSM carrier adjacent to the upper sub-block edge of the lower sub-block and one GSM carrier adjacent to the lower sub-block edge of the upper sub-block. Place one UTRA FDD carrier in the middle of the lower sub-block bandwidth and one 5MHz E-UTRA carrier in the middle of the upper sub-block bandwidth. If 5 MHz E-UTRA carriers are + +not supported by the BS, the narrowest supported channel BW shall be selected instead. The sub-block bandwidth shall be equal to the bandwidth of the allocated non-GSM carrier in that sub-block plus 1MHz. The specified $F_{\text{Offset-RAT}}$ shall apply. + +#### 4.8.4.a.4 NTC4 power allocation + +- Unless otherwise stated, set each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to manufacturer's declarations in clause 4.7.2 a) +- In case that NTC4 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in clause 4.7.2, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacture's declaration the power in the other RAT(s) does not need to be increased. + +### 4.8.5 TC5: BC2 receiver operation + +#### 4.8.5.1 TC5a generation + +TC5a is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a GSM carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place a UTRA FDD carrier at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. The UTRA FDD carrier may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. + +#### 4.8.5.2 TC5b generation + +TC5b is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a GSM carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place a 5MHz E-UTRA carrier at the upper Base Station RF Bandwidth edge. If the BS does not support 5 MHz channel BW select the narrowest supported channel BW. The specified $F_{\text{Offset-RAT}}$ shall apply. + +### 4.8.5.a NTC5: Non-contiguous multi RAT operations with GSM for the receiver + +The purpose of NTC5 is to test non-contiguous multi RAT operations with GSM for the receiver. + +#### 4.8.5.a.1 NTC5a generation + +NTC5a is only applicable for a BS that supports UTRA and GSM. NTC5a is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. The sub-block bandwidth shall be equal to 6MHz. +- If the BS supports up to 3 carriers use the method to generate NTC4a for up to 3 carriers. +- If the BS supports at least 4 carriers use the method to generate NTC4a for up to 4 carriers. + +#### 4.8.5a.2 NTC5b generation + +NTC5b is only applicable for a BS that supports E-UTRA and GSM. NTC5b is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- If the BS supports up to 3 carriers use the method to generate NTC4b for up to 3 carriers. +- If the BS supports at least 4 carriers use the method to generate NTC4b for up to 4 carriers. + +#### 4.8.5a.3 NTC5c generation + +NTC5c is only applicable for a BS that supports UTRA, E-UTRA and GSM. NTC5c is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- If the BS supports up to 3 carriers use the method to generate NTC4c for up to 3 carriers. +- If the BS supports at least 4 carriers use the method to generate NTC4c for up to 4 carriers. + +### 4.8.6 TC6: Single carrier for receiver tests + +#### 4.8.6.1 TC6a generation + +TC6a is constructed using the following method: + +- Place a single UTRA carrier in the middle of the maximum Base Station RF Bandwidth. The carrier may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. + +#### 4.8.6.2 TC6b generation + +TC6b is constructed using the following method: + +- Place the narrowest supported E-UTRA carrier in the middle of the maximum Base Station RF Bandwidth. + +#### 4.8.6.3 TC6c generation + +TC6c is constructed using the following method: + +- Place a single UTRA TDD carrier in the middle of the maximum Base Station RF Bandwidth. + +### 4.8.7 Generation of MB-MSR test configurations + +#### 4.8.7.1 TC7a: MB-MSR test configuration for full carrier allocation + +The purpose of TC7a is to test multi-band operation aspects considering maximum supported number of carriers. + +##### 4.8.7.1.1 TC7a generation + +TC7a is based on re-using the existing test configurations applicable per band involved in multi-band operation. TC7a is constructed using the following method: + +- The Base Station RF Bandwidth of each supported operating band shall be the declared maximum Base Station RF Bandwidth in multi-band operation. + +- The number of carriers of each supported operating band shall be the declared maximum number of supported carriers in multi-band operation. Carriers shall first be placed at the outermost edges of the declared Maximum Radio Bandwidth for outermost bands and the Base Station RF Bandwidth edges for middle band(s) if any. Additional carriers shall next be placed at the Base Station RF Bandwidth edges, if possible. +- The allocated Base Station RF Bandwidth of the outermost bands shall be located at the outermost edges of the declared Maximum Radio Bandwidth. +- Each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to the test configuration referenced in Table 4.8.7.1.1-1, where the declared parameters for multi-band operation shall apply. The mirror image of the single band test configuration shall be used in each alternate band(s) and in the highest band being tested for the BS. +- If only one carrier can be placed for the concerned band(s), the carrier(s) shall be placed at the outermost edges of the declared maximum radio bandwidth for outermost band(s) and at one of the outermost edges of the supported frequency range within the Base Station RF Bandwidths for middle band(s) if any. +- If the sum of the maximum Base Station RF Bandwidth of each supported operating bands is larger than the declared Total RF Bandwidth of transmitter and receiver for the declared band combinations of the BS, repeat the steps above for test configurations where the Base Station RF Bandwidth of one of the operating band shall be reduced so that the Total RF Bandwidth of transmitter and receiver is not exceeded and vice versa. +- If the sum of the maximum number of supported carrier of each supported operating bands in multi-band operation is larger than the declared total number of supported carriers for the declared band combinations of the BS, repeat the steps above for test configurations where in each test configuration the number of carriers of one of the operating band shall be reduced so that the total number of supported carriers is not exceeded and vice versa. + +**Table 4.8.7.1.1-1: The applicability of test configuration for carrier placement in each band** + +| BC | CS 1 | CS 2 | CS 3 | CS 4 | CS 5 | CS 6 | CS 7 | CS16 | CS18 | CS19 | +|-----|------|------|------|------|------|------|---------------------|------|-----------|-----------| +| BC1 | TC1a | TC2 | TC3a | N/A | N/A | N/A | N/A | TC21 | N/A | TC21
b | +| BC2 | TC1a | TC2 | TC3a | TC4a | TC4b | TC4c | TC4a
and
TC4b | TC21 | TC21
a | TC21
b | +| BC3 | TC1b | TC2 | TC3b | N/A | N/A | N/A | N/A | TC21 | N/A | N/A | + +#### 4.8.7.1.2 TC7a power allocation + +Unless otherwise stated, set the power of each carrier in all supported operating bands to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration. + +If the allocated power of a supported operating band(s) exceeds the declared rated total output power of the operating band(s) in multi-band operation, the exceeded part shall, if possible, be reallocated into the other band(s). If the power allocated for a carrier exceeds the rated carrier output power declared for that carrier, the exceeded power shall, if possible, be reallocated into the other carriers. + +#### 4.8.7.2 TC7b: MB-MSR test configuration with high PSD per carrier + +The purpose of TC7b is to test multi-band operation aspects considering higher PSD cases with reduced number of carriers and non-contiguous operation (if supported) in multi-band mode. + +Unless otherwise stated, for all test configurations in this clause, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth and the narrowest supported E-UTRA channel bandwidth for each operating band shall be used in the test configuration. + +##### 4.8.7.2.1 TC7b generation + +TC7b is based on re-using the existing test configurations applicable per band involved in multi-band operation. TC7b is constructed using the following method: + +- The Base Station RF Bandwidth of each supported operating band shall be the declared maximum Base Station RF Bandwidth in multi-band operation. +- The allocated Base Station RF Bandwidth of the outermost bands shall be located at the outermost edges of the declared Maximum Radio Bandwidth. +- The maximum number of carriers for a BC2 band is limited to three per band for transmitter tests when the BS supports CS4, CS5, CS6, CS7 or CS18. For other transmitter tests and for all receiver tests, the maximum number of carriers is limited to two per band. Carriers shall first be placed at the outermost edges of the declared Maximum Base Station Radio Bandwidth, for outermost bands and the Base Station RF Bandwidth edges for middle band(s) if any. Additional carriers shall next be placed at the Base Station RF Bandwidth edges. +- For BS supporting CS1, CS2, CS3, CS16 or CS19 in the band, each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to the test configuration referenced in Table 4.8.7.2.1-1, where the declared parameters for multi-band operation shall apply. The mirror image of the single band test configuration shall be used in each alternate band(s) and in the highest band being tested for the BS. +- If the maximum supported number of carriers is two for a BC2 band when the BS supports CS4, CS5, CS6 or CS7, place the UTRA/E-UTRA carrier at the Base Station RF Bandwidth edge adjacent to the Inter RF Bandwidth gap and place the GSM/EDGE carrier at the edge of the declared Maximum Base Station Radio Bandwidth. +- If the maximum supported number of carriers is three or more for a BC2 band when the BS supports CS4, CS5, CS6, CS7 or CS18, place one GSM/EDGE carrier at the Base Station RF Bandwidth edge adjacent to the Inter RF Bandwidth gap, place the second GSM/EDGE carrier at the edge of the declared Maximum Base Station Radio Bandwidth and place the UTRA/E-UTRA/NR carrier adjacent to the GSM/EDGE carrier at the inter RF bandwidth gap. The adjacent UTRA/E-UTRA/NR carrier shall be placed with its channel BW edge aligned with the channel BW edge of the GSM/EDGE carrier by applying $F_{\text{offset,RAT}}$ in clause 4.4.2. +- If the sum of the maximum Base Station RF Bandwidth of each supported operating bands is larger than the declared Total RF Bandwidth of transmitter and receiver for the declared band combinations of the BS, repeat the steps above for test configurations where the Base Station RF Bandwidth of one of the operating band shall be reduced so that the Total RF Bandwidth of transmitter and receiver is not exceeded and vice versa. + +**Table 4.8.7.2.1-1: The applicability of test configuration for carrier placement in each band** + +| BC | CS 1 | CS 2 | CS 3 | CS16 | CS19 | +|-----|-------|------|------|-------|--------| +| BC1 | NTC1a | NTC2 | NTC3 | NTC21 | NTC21b | +| BC2 | NTC1a | NTC2 | NTC3 | NTC21 | NTC21b | +| BC3 | TC1b | NTC2 | NTC3 | NTC21 | N/A | + +#### 4.8.7.2.2 TC7b power allocation + +Unless otherwise stated, set the power of each carrier in all supported operating bands to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration. + +If the allocated power of a supported operating band(s) exceeds the declared rated total output power of the operating band(s) in multi-band operation, the exceeded part shall, if possible, be reallocated into the other band(s). If the power allocated for a carrier exceeds the rated carrier output power declared for that carrier, the exceeded power shall, if possible, be reallocated into the other carriers. + +#### 4.8.7.3 TC7c: MB-MSR test configuration with GSM/EDGE single RAT operation in one band + +The purpose of TC7c is to test single-RAT GSM/EDGE UEM requirement for multi-band base station supporting GSM/EDGE single-RAT operation in BC2 band. + +##### 4.8.7.3.1 TC7c generation + +TC7c is constructed using the following method: + +- The Base Station RF Bandwidth of each supported operating band shall be the declared maximum Base Station RF Bandwidth in multi-band operation. +- The allocated Base Station RF Bandwidth of the outermost bands shall be located at the outermost edges of the declared Maximum Radio Bandwidth. +- If the BS supports one BC1 band and one BC2 band, the maximum number of carriers in a test configuration for BC1 band is limited to two. A UTRA/E-UTRA carrier from BC1 shall first be placed at the outermost edge of the declared Maximum Radio Bandwidth. If two or more carriers are supported in BC1 band, additional UTRA/E-UTRA carrier shall next be placed at the BC1 Base Station RF Bandwidth edge adjacent to the Inter RF Bandwidth gap. For BC2 band, where GSM/EDGE single-RAT operation is supported, one GSM/EDGE carrier shall first be placed at the other outermost edge of the declared Maximum Radio Bandwidth and additional GSM/EDGE carriers shall be placed within the declared maximum Base Station RF Bandwidth for the GSM/EDGE single-RAT BC2 band according to test case b) in TS 51.021 clause 6.12.2. +- If the BS supports two BC2 bands, the maximum number of carriers in a test configuration is two for a BC2 band where CS1, CS2 or CS3 is supported. + +One UTRA/E-UTRA carrier from the BC2 band, where CS1, CS2 or CS3 is supported, shall first be placed at the outermost edge of the declared Maximum Radio Bandwidth. If two or more carriers are supported in this BC2 band, additional UTRA/E-UTRA carrier shall next be placed at the Base Station RF Bandwidth edge adjacent to the Inter RF Bandwidth gap. For BC2 band, where GSM/EDGE single-RAT operation is supported, place GSM/EDGE carrier at the other outermost edge of the declared Maximum Radio Bandwidth, additional GSM/EDGE carriers shall be placed within the declared maximum Base Station RF Bandwidth for the GSM/EDGE single-RAT BC2 band according to test case b) in TS 51.021 clause 6.12.2. + +- If the BS supports two BC2 bands with GSM/EDGE operation (CS4, CS5, CS6 or CS7) and in at least one band CS4, CS5 or CS6 is supported, the maximum number of carriers for one BC2 band configured to multi-RAT operation is limited to three. + - For the GSM/EDGE single-RAT BC2 band, one GSM/EDGE carrier shall first be placed at the outermost edge of the declared Maximum Radio Bandwidth, additional GSM/EDGE carriers for the BC2 band shall be placed within the declared maximum Base Station RF Bandwidth for the GSM/EDGE single-RAT BC2 band according to test case b) in TS 51.021 clause 6.12.2. + - For the multi-RAT BC2 band, if the maximum supported number of carriers is two, place the UTRA/E-UTRA carrier at the Base Station RF Bandwidth edge adjacent to the Inter RF Bandwidth gap, then place the GSM/EDGE carrier at the other edge of the declared Maximum Radio Bandwidth. + - For the multi-RAT BC2 band, if the maximum supported number of carriers is three or more, place one GSM/EDGE carrier at the Base Station RF Bandwidth edge adjacent to the Inter RF Bandwidth gap, then place the second GSM/EDGE carrier at the other edge of the declared Maximum Radio Bandwidth, then place the UTRA/E-UTRA carrier in the middle of the Base Station RF Bandwidth. + +If both BC2 bands are declared as CS4, CS5 or CS6, repeat the steps above with the allocated carriers swapped between the two BC2 bands so that each BC2 band is tested once according to test case b) in TS 51.021 clause 6.12.2. + +- The narrowest supported E-UTRA channel bandwidth shall be used in the test configuration. +- If the sum of the maximum Base Station RF Bandwidth of each supported operating bands is larger than the declared total bandwidth of transmitter and receiver for the declared band combinations of the BS, repeat the steps above for test configurations where the Base Station RF Bandwidth of one of the operating band shall be reduced so that the Total RF Bandwidth of transmitter and receiver is not exceeded and vice versa. + +#### 4.8.7.3.2 TC7c power allocation + +Unless otherwise stated, set the power of each carrier in all supported operating bands to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration. + +If the allocated power of a supported operating band(s) exceeds the declared rated total output power of the operating band(s) in multi-band operation, the exceeded part shall, if possible, be reallocated into the other band(s). If the power allocated for a carrier exceeds the rated carrier output power declared for that carrier, the exceeded power shall, if possible, be reallocated into the other carriers. + +## 4.8.8 TC8: NB-IoT standalone multi-carrier operation + +The purpose of the TC8 is to test NB-IoT standalone multi-carrier aspects. + +### 4.8.8.1 TC8 generation + +TC8 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a NB-IoT carrier at the upper edge and a NB-IoT carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, add NB-IoT carriers at the edges using 600 kHz spacing until no more NB-IoT carriers are supported or no more NB-IoT carriers fit. + +### 4.8.8.2 TC8 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +## 4.8.9 TC9: GSM and NB-IoT standalone multi-carrier operation + +The purpose of the TC9 is to test GSM and NB-IoT standalone multi-carrier aspects. + +### 4.8.9.1 TC9 generation + +TC9 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a NB-IoT carrier at the upper edge and a GSM carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, alternately add NB-IoT carriers at the upper edge and GSM carriers at the lower edge using 600 kHz spacing until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. + +### 4.8.9.2 TC9 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +## 4.8.10 TC10: UTRA and NB-IoT standalone multi-carrier operation + +The purpose of the TC10 is to test UTRA and NB-IoT standalone multi-carrier aspects. + +### 4.8.10.1 TC10 generation + +TC10 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- For receiver tests, place a NB-IoT carrier at the lower edge and a UTRA FDD carrier at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests and in the case of a BS supporting only one NB-IoT carrier, place a NB-IoT carrier at the lower edge and a UTRA FDD carrier at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. Add additional UTRA FDD carriers in the middle if possible. The UTRA FDD carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. + +- For transmitter tests and in the case of a BS supporting more than one NB-IoT carrier, carry out the following steps. + - Place a NB-IoT carrier at the upper edge and a NB-IoT carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - Place two UTRA FDD carriers in the middle of the Base Station RF Bandwidth. If only one UTRA FDD carrier is supported or two UTRA FDD carriers do not fit, place only one carrier in the middle of the Base Station RF Bandwidth. The UTRA FDD carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. + - Add NB-IoT carriers at the edges using 600 kHz spacing until no more NB-IoT carriers are supported or no more NB-IoT carriers fit. + - Add additional UTRA FDD carriers in the middle if possible. + +#### 4.8.10.2 TC10 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +### 4.8.11 TC11: E-UTRA and NB-IoT standalone multi-carrier operation + +The purpose of the TC11 is to test E-UTRA and NB-IoT standalone multi-carrier aspects. + +#### 4.8.11.1 TC11 generation + +TC11 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- For receiver tests, place a NB-IoT carrier at the lower edge and a 5MHz E-UTRA carrier at the upper Base Station RF Bandwidth edge. If the BS does not support 5 MHz channel BW use the narrowest supported BW. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests and in the case of a BS supporting only one NB-IoT carrier, place a NB-IoT carrier at the lower edge and a 5MHz E-UTRA carrier at the upper Base Station RF Bandwidth edge. If the BS does not support 5 MHz channel BW use the narrowest supported BW. The specified $F_{\text{Offset-RAT}}$ shall apply. Add additional E-UTRA carriers of the same bandwidth as the already allocated E-UTRA carriers in the middle if possible. +- For transmitter tests and in the case of a BS supporting more than one NB-IoT carrier, carry out the following steps. + - Place a NB-IoT carrier at the upper edge and a NB-IoT carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - Place two 5 MHz E-UTRA carriers in the middle of the Base Station RF Bandwidth. If the BS does not support 5 MHz channel BW use the narrowest supported BW, if only one carrier is supported or two carriers do not fit place only one carrier. + - Add NB-IoT carriers at the edges using 600 kHz spacing until no more NB-IoT carriers are supported or no more NB-IoT carriers fit. + - Add additional E-UTRA carriers of the same bandwidth as the already allocated E-UTRA carriers in the middle if possible. + +#### 4.8.11.2 TC11 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +## 4.8.12 TC12: GSM and UTRA and NB-IoT standalone multi-carrier operation + +The purpose of the TC12 is to test GSM and UTRA and NB-IoT standalone multi-carrier aspects. + +### 4.8.12.1 TC12 generation + +TC12 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a NB-IoT carrier at the upper edge and a GSM carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place two UTRA FDD carriers in the middle of the Base Station RF Bandwidth. If only one UTRA FDD carrier is supported or two UTRA FDD carriers do not fit, place only one carrier in the middle of the Base Station RF Bandwidth. The UTRA FDD carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. +- For transmitter tests, alternately add NB-IoT carriers at the upper edge and GSM carriers at the lower edge using 600 kHz spacing until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. +- For transmitter tests, add additional UTRA FDD carriers in the middle if possible. + +### 4.8.12.2 TC12 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +## 4.8.13 TC13: GSM and E-UTRA and NB-IoT standalone multi-carrier operation + +The purpose of the TC13 is to test GSM and E-UTRA and NB-IoT standalone multi-carrier aspects. + +### 4.8.13.1 TC13 generation + +TC13 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a NB-IoT carrier at the upper edge and a GSM carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place two 5 MHz E-UTRA carriers in the middle of the Base Station RF Bandwidth. If the BS does not support 5 MHz channel BW use the narrowest supported BW, if only one carrier is supported or two carriers do not fit place only one carrier. +- For transmitter tests, alternately add NB-IoT carriers at the upper edge and GSM carriers at the lower edge using 600 kHz spacing until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. +- For transmitter tests, add additional E-UTRA carriers of the same bandwidth as the already allocated E-UTRA carriers in the middle if possible. + +### 4.8.13.2 TC13 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +## 4.8.14 TC14: UTRA and E-UTRA and NB-IoT standalone multi-carrier operation + +The purpose of the TC14 is to test UTRA and E-UTRA and NB-IoT standalone multi-carrier aspects. + +### 4.8.14.1 TC14 generation + +TC14 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- For receiver tests, place a NB-IoT carrier at the lower edge and a 5MHz E-UTRA carrier at the upper Base Station RF Bandwidth edge. If the BS does not support 5 MHz channel BW use the narrowest supported BW. The specified $F_{\text{Offset-RAT}}$ shall apply. Place a UTRA FDD carrier in the middle of the Base Station RF Bandwidth. The UTRA FDD carrier may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. +- For transmitter tests and in the case of a BS supporting only one NB-IoT carrier, place a NB-IoT carrier at the lower edge and a 5MHz E-UTRA carrier at the upper Base Station RF Bandwidth edge. If the BS does not support 5 MHz channel BW use the narrowest supported BW. The specified $F_{\text{Offset-RAT}}$ shall apply. Place a UTRA FDD carrier in the middle of the Base Station RF Bandwidth. The UTRA FDD carrier may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. Add additional UTRA and E-UTRA carriers in the middle if possible. For E-UTRA the same bandwidth as the already allocated E-UTRA carriers shall be used. +- For transmitter tests and in the case of a BS supporting more than one NB-IoT carrier, carry out the following steps. + - Place a NB-IoT carrier at the upper edge and a NB-IoT carrier at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - Place one 5 MHz E-UTRA carrier and one UTRA FDD carrier in the middle of the Base Station RF Bandwidth. If the BS does not support 5 MHz E-UTRA channel BW use the narrowest supported BW. The carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. + - Add NB-IoT carriers at the edges using 600 kHz spacing until no more NB-IoT carriers are supported or no more NB-IoT carriers fit. + - Add additional UTRA and E-UTRA carriers in the middle if possible. For E-UTRA the same bandwidth as the already allocated E-UTRA carriers shall be used. + +### 4.8.14.2 TC14 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +## 4.8.15 TC15: GSM and E-UTRA with NB-IoT in-band multi-carrier operation + +The purpose of the TC15 is to test GSM and NB-IoT in-band multi-carrier aspects. + +### 4.8.15.1 TC15 generation + +TC15 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a GSM carrier at the lower Base Station RF Bandwidth edge. Place a 5 MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. Place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + +- For transmitter tests, add GSM carriers at the edges using 600 kHz spacing until no more GSM carriers are supported or no more GSM carriers fit, then select as many 5 MHz E-UTRA carriers that the BS supports and that fit in the rest of the Base Station RF Bandwidth. Place the carriers adjacent to each other starting from the high Base Station RF Bandwidth edge. The nominal carrier spacing defined in clause 4.5.1 shall apply. +- If 5 MHz E-UTRA carriers are not supported by the BS the narrowest supported channel BW shall be selected instead. + +#### 4.8.15.2 TC15 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +#### 4.8.16 TC16: UTRA and E-UTRA with NB-IoT in-band multi-carrier operation + +The purpose of the TC16 is to test UTRA and NB-IoT in-band multi-carrier aspects. + +##### 4.8.16.1 TC16 generation + +TC16 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place an UTRA FDD carrier at the lower Base Station RF Bandwidth edge. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. Place a 5 MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. Place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, select as many 5 MHz E-UTRA carriers that the BS supports and that fit in the rest of the Base Station RF Bandwidth. Place the carriers adjacent to each other starting from the high Base Station RF Bandwidth edge. The nominal carrier spacing defined in clause 4.5.1 shall apply. +- If 5 MHz E-UTRA carriers are not supported by the BS the narrowest supported channel BW shall be selected instead. + +##### 4.8.16.2 TC16 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +#### 4.8.17 TC17: E-UTRA and E-UTRA with NB-IoT in-band multi-carrier operation + +The purpose of the TC17 is to test E-UTRA and NB-IoT in-band multi-carrier aspects. + +##### 4.8.17.1 TC17 generation + +TC17 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a 5 MHz E-UTRA carrier adjacent to the lower Base Station RF Bandwidth edge. Place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the lower Base Station RF Bandwidth edge. Place a 5 MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. In the case of a BS supporting more than one NB-IoT in-band carrier, place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + +- For transmitter tests, select as many 5 MHz E-UTRA carriers that the BS supports and that fit in the rest of the Base Station RF Bandwidth. Place the carriers adjacent to each other starting from the high Base Station RF Bandwidth edge. The nominal carrier spacing defined in clause 4.5.1 shall apply. +- If 5 MHz E-UTRA carriers are not supported by the BS the narrowest supported channel BW shall be selected instead. + +#### 4.8.17.2 TC17 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +### 4.8.18 TC18: GSM and E-UTRA with NB-IoT guard-band multi-carrier operation + +The purpose of the TC18 is to test GSM and NB-IoT guard-band multi-carrier aspects. + +#### 4.8.18.1 TC18 generation + +TC18 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a GSM carrier at the lower Base Station RF Bandwidth edge. Place a 10 MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. Place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the upper Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, add GSM carriers at the edge using 600 kHz spacing until no more GSM carriers are supported or no more GSM carriers fit, then select as many 10 MHz E-UTRA carriers that the BS supports and that fit in the rest of the Base Station RF Bandwidth. Place the carriers adjacent to each other starting from the high Base Station RF Bandwidth edge. The nominal carrier spacing defined in clause 4.5.1 shall apply. +- If 10 MHz E-UTRA carriers are not supported by the BS the narrowest supported channel BW shall be selected instead. + +#### 4.8.18.2 TC18 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +### 4.8.19 TC19: UTRA and E-UTRA with NB-IoT guard-band multi-carrier operation + +The purpose of the TC19 is to test UTRA and NB-IoT guard-band multi-carrier aspects. + +#### 4.8.19.1 TC19 generation + +TC19 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place an UTRA FDD carrier at the lower Base Station RF Bandwidth edge. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. Place a 10 MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. Place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the upper Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. + +- For transmitter tests, select as many UTRA FDD carriers that the BS supports and that fit in the rest of the Base Station RF Bandwidth. Place the carriers adjacent to each other starting from the high Base Station RF Bandwidth edge. The carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. The nominal carrier spacing defined in clause 4.5.1 shall apply. + +#### 4.8.19.2 TC19 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +#### 4.8.20 TC20: E-UTRA and E-UTRA with NB-IoT guard-band multi-carrier operation + +The purpose of the TC20 is to test E-UTRA and NB-IoT guard-band multi-carrier aspects. + +##### 4.8.20.1 TC20 generation + +TC20 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Place a 10 MHz E-UTRA carrier adjacent to the lower Base Station RF Bandwidth edge. Place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the lower Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the lower Base Station RF Bandwidth edge). Place a 10 MHz E-UTRA carrier adjacent to the upper Base Station RF Bandwidth edge. In the case of a BS supporting more than one NB-IoT guard-band carrier, place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the upper Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, select as many 10 MHz E-UTRA carriers that the BS supports and that fit in the rest of the Base Station RF Bandwidth. Place the carriers adjacent to each other starting from the high Base Station RF Bandwidth edge. The nominal carrier spacing defined in clause 4.5.1 shall apply. +- If 10 MHz E-UTRA carriers are not supported by the BS, the narrowest supported channel BW > 10 MHz shall be selected instead. + +##### 4.8.20.2 TC20 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +#### 4.8.21 TC21: Contiguous operation in CS16, 18, 19 + +##### 4.8.21.0 General + +The purpose of TC21, TC21a and TC21b is to test multi-RAT operations with NR. + +Unless otherwise stated, for all test configurations in this clause, the NR channel bandwidth shall be 5 MHz. If the BS doesn't support NR 5 MHz channel bandwidth, the NR channel bandwidth shall then be the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth for the operating band. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5 MHz unless the BS does not support 5 MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth for the operating band. + +##### 4.8.21.1 TC21 generation + +TC21 is only applicable for a BS that supports E-UTRA and NR. TC21 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Adjacent to the lower Base Station RF Bandwidth edge: + - If NB-IoT operation in NR in-band is supported, place an NR carrier with NB-IoT operation in NR in-band. Place the power boosted NB-IoT RB at the lower outermost eligible (according to clause 5.7.3 of TS 36.104 [5] and the definition in clause 3.1) RB position for NB-IoT operation in NR in-band which is closest to NR minimum guard band at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT operation in NR in-band is not supported, place an NR carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Adjacent to the upper Base Station RF Bandwidth edge: + - If NB-IoT guard band operation is supported, place a 10 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the upper Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT guard-band operation is not supported and NB-IoT in-band operation is supported, place a 5 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - If neither NB-IoT guard-band nor NB-IoT in-band operation is supported, place an E-UTRA carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, alternately add NR carriers at the low end and E-UTRA carriers at the high end adjacent to the already placed carriers until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. The nominal carrier spacing defined in clause 4.5.1 shall apply. + +#### 4.8.21.1A TC21a generation + +TC21a is only applicable for a BS that supports GSM, E-UTRA and NR. TC21a is constructed using the following method: + +For transmitter tests, if the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, two instances of TC21a shall be generated using the following values for rated total output power and the total number of supported carriers: + +- 1) The rated total output power and the reduced number of supported carriers at the rated total output power in Multi-RAT operations +- 2) The reduced rated total output power at the total number of supported carriers in Multi-RAT operations and the total number of supported carriers. + +If the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, tests that use TC21a shall be performed using both instances 1) and 2) of TC21a except tests for modulation accuracy in which only TC21a according to 2) shall be used. + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Adjacent to the lower Base Station RF Bandwidth edge: + - Place a GSM carrier. +- Adjacent to the upper Base Station RF Bandwidth edge: + - If NB-IoT operation in NR in-band is supported, place an NR carrier with NB-IoT operation in NR in-band. Place the power boosted NB-IoT RB at the upper outermost eligible (according to clause 5.7.3 of TS 36.104 [5] and the definition in clause 3.1) RB position for NB-IoT operation in NR in-band which is closest to NR minimum guard band at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT operation in NR in-band is not supported: + +- If NB-IoT guard band operation is supported, place a 10 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the upper Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. +- If NB-IoT guard-band operation is not supported and NB-IoT in-band operation is supported, place a 5 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. +- If neither NB-IoT guard-band nor NB-IoT in-band operation is supported, place a GSM carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. Place one E-UTRA carrier adjacent to the already placed GSM carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place one NR carrier adjacent to the already placed carrier at the upper Base Station RF bandwidth edge. +- For transmitter tests, add GSM carriers at the lower edge using 600 kHz spacing until no more GSM carriers are supported or no more GSM carriers fit. Add alternately NR carriers and E-UTRA carriers at the high end adjacent to the already placed carriers until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. The nominal carrier spacing defined in clause 4.5.1 shall apply. + +#### 4.8.21.1B TC21b generation + +TC21b is only applicable for a BS that supports UTRA, E-UTRA and NR. TC21b is constructed using the following method: + +For transmitter tests, if the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, two instances of TC21b shall be generated using the following values for rated total output power and the total number of supported carriers: + +- 1) The rated total output power and the reduced number of supported carriers at the rated total output power in Multi-RAT operations +- 2) The reduced rated total output power at the total number of supported carriers in Multi-RAT operations and the total number of supported carriers. + +If the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, tests that use TC21b shall be performed using both instances 1) and 2) of TC21b. + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Adjacent to the lower Base Station RF Bandwidth edge: + - If NB-IoT operation in NR in-band is supported, place an NR carrier with NB-IoT operation in NR in-band. Place the power boosted NB-IoT RB at the lower outermost eligible (according to clause 5.7.3 of TS 36.104 [5] and the definition in clause 3.1) RB position for NB-IoT operation in NR in-band which is closest to NR minimum guard band at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT operation in NR in-band is not supported, place an NR carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Adjacent to the upper Base Station RF Bandwidth edge: + - If NB-IoT guard band operation is supported, place a 10 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the upper Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT guard-band operation is not supported and NB-IoT in-band operation is supported, place a 5 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - If neither NB-IoT guard-band nor NB-IoT in-band operation is supported, place a E-UTRA carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. + +- Place UTRA carrier adjacent to the already placed E-UTRA carrier. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- For transmitter tests, alternately add NR carriers at the low end and E-UTRA carriers at the high end adjacent to the already placed carriers until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. The nominal carrier spacing defined in clause 4.5.1 shall apply. + +#### 4.8.21.2 TC21 power allocation + +- Unless otherwise stated, set each carrier to the same power so that the sum of the carrier powers equals the rated total output power as appropriate for the test configuration according to manufacturer's declarations in clause 4.7.2 +- In case that TC21 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in clause 4.7.2, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacture's declaration the power in the other RAT(s) does not need to be increased. + +### 4.8.22 NTC21: Non-contiguous operation in CS16, 18, 19 + +#### 4.8.22.0 General + +The purpose of NTC21, NTC21a and NTC21b is to test multi-RAT operations with NR. + +Unless otherwise stated, for all test configurations in this clause, the NR channel bandwidth shall be 5 MHz. If the BS doesn't support NR 5 MHz channel bandwidth, the NR channel bandwidth shall then be the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth for the operating band. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5 MHz unless the BS does not support 5 MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth. + +#### 4.8.22.1 NTC21 generation + +NTC21 is only applicable for a BS that supports E-UTRA and NR. NTC21 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- Adjacent to the lower Base Station RF Bandwidth edge: + - If NB-IoT operation in NR in-band is supported, place an NR carrier with NB-IoT operation in NR in-band. Place the power boosted NB-IoT RB at the lower outermost eligible (according to clause 5.7.3 of TS 36.104 [5] and the definition in clause 3.1) RB position for NB-IoT operation in NR in-band which is closest to NR minimum guard band at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT operation in NR in-band is not supported, place an NR carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Adjacent to the upper Base Station RF Bandwidth edge: + - If NB-IoT guard band operation is supported, place a 10 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the upper Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT guard-band operation is not supported and NB-IoT in-band operation is supported, place a 5 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + +- If neither NB-IoT guard-band nor NB-IoT in-band operation is supported, place an E-UTRA carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. +- In case rated total output power is not reached, the narrowest E-UTRA and/or NR channel BW which supports rated carrier output power shall be selected. If still there is some output power room, alternately place an E-UTRA carrier of this BW adjacent to the carrier at the lower Base Station RF Bandwidth edge and NR carrier of this BW adjacent to the carrier at the upper Base Station RF Bandwidth edge until the rated total output power or the total number of supported carriers is reached. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier adjacent to the sub-block gap. + +#### 4.8.22.1A NTC21a generation + +NTC21a is only applicable for a BS that supports GSM, E-UTRA and NR. NTC21a is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- Adjacent to the lower Base Station RF Bandwidth edge: + - Place a GSM carrier at the lower RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. Place one GSM carrier adjacent to the upper sub-block edge of the lower sub-block and: + - If NB-IoT operation in NR in-band is supported, place an NR carrier with NB-IoT operation in NR in-band in the middle of the lower sub-block bandwidth and place the power boosted NB-IoT RB at the lower outermost eligible (according to clause 5.7.3 of TS 36.104 [5] and the definition in clause 3.1) RB position for NB-IoT operation in NR in-band which is closest to NR minimum guard band. + - If NB-IoT operation in NR in-band is not supported, place NR carrier in the middle of the lower sub-block bandwidth. +- Adjacent to the upper Base Station RF Bandwidth edge: + - If NB-IoT guard band operation is supported, place a 10 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the upper Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT guard-band operation is not supported and NB-IoT in-band operation is supported, place a 5 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - If neither NB-IoT guard-band nor NB-IoT in-band operation is supported, place a GSM carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. + - Place a GSM carrier adjacent to the lower sub-block edge of the upper sub-block. Place an E-UTRA carrier in the middle of the upper sub-block bandwidth. +- The nominal carrier spacing defined in clause 4.5.1 shall apply. The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier adjacent to the sub-block gap. In case rated total output power is not reached, the narrowest E-UTRA and/or NR channel BW which supports rated carrier output power shall be selected. + +#### 4.8.22.1B NTC21b generation + +NTC21b is only applicable for a BS that supports UTRA, E-UTRA and NR. NTC21b is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- Adjacent to the lower Base Station RF Bandwidth edge: + - If NB-IoT operation in NR in-band is supported, place an NR carrier with NB-IoT operation in NR in-band. Place the power boosted NB-IoT RB at the lower outermost eligible (according to clause 5.7.3 of TS 36.104 [5] and the definition in clause 3.1) RB position for NB-IoT operation in NR in-band which is closest to NR minimum guard band at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT operation in NR in-band is not supported, place an NR carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Adjacent to the upper Base Station RF Bandwidth edge: + - If NB-IoT guard band operation is supported, place a 10 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the upper Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. + - If NB-IoT guard-band operation is not supported and NB-IoT in-band operation is supported, place a 5 MHz E-UTRA carrier. Place the power boosted NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the upper Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. + - If neither NB-IoT guard-band nor NB-IoT in-band operation is supported, place an E-UTRA carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. + - Place a UTRA carrier adjacent to the lower sub-block edge of the upper sub-block. +- For transmitter tests, place one UTRA adjacent to the upper sub-block edge of the lower sub-block. The nominal carrier spacing defined in clause 4.5.1 shall apply. In case rated total output power is not reached, the narrowest E-UTRA and/or NR channel BW which supports rated carrier output power shall be selected. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier adjacent to the sub-block gap. The carrier(s) may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. + +#### 4.8.22.2 NTC21 power allocation + +- a) Unless otherwise stated, set each carrier to the same power unless the rated carrier output power for RATs are different so that the sum of the carrier powers equals the rated total output power appropriate for the test configuration according to manufacturer's declarations in clause 4.7.2. +- b) In case that NTC21 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in clause 4.7.2, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacture's declaration the power in the other RAT(s) does not need to be increased. + +#### 4.8.23 TC22: Contiguous operation in CS17 + +##### 4.8.23.1 TC22 generation + +TC22 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. +- Adjacent to the upper Base Station RF Bandwidth edge: + +- Place a standalone NB-IoT carrier. +- Adjacent to the lower Base Station RF Bandwidth edge: + - If NB-IoT operation in NR in-band is supported, place a 5MHz / 15kHz SCS NR carrier with NB-IoT operation in NR in-band. Place the power boosted NB-IoT RB at the lower outermost eligible (according to clause 5.7.3 of TS 36.104 [5] and the definition in clause 3.1) RB position for NB-IoT operation in NR in-band which is closest to NR minimum guard band at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. Place a 5MHz E-UTRA carrier adjacent to the NR carrier. + - If NB-IoT operation in NR in-band is not supported and: + - If NB-IoT guard band operation is supported, place a 10 MHz E-UTRA carrier. Place the NB-IoT PRB at the outermost guard-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the lower Base Station RF Bandwidth edge and adjacent to the E-UTRA PRB edge as close as possible (i.e., away from the lower Base Station RF Bandwidth edge). The specified $F_{\text{Offset-RAT}}$ shall apply. Place a 5MHz / 15kHz SCS NR carrier adjacent to the 10 MHz E-UTRA carrier. + - If NB-IoT guard-band operation is not supported and NB-IoT in-band operation is supported, place a 5 MHz E-UTRA carrier. Place the NB-IoT PRB at the outermost in-band position eligible for NB-IoT PRB (according to clause 4.5.3) at the lower Base Station RF Bandwidth edge. The specified $F_{\text{Offset-RAT}}$ shall apply. Place a 5MHz / 15kHz SCS NR carrier adjacent to the 5 MHz E-UTRA carrier. + - If neither NB-IoT guard-band nor NB-IoT in-band operation is supported, place a 5MHz/15kHz SCS NR carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. Place a 5 MHz E-UTRA carrier adjacent to the 5MHz / 15kHz SCS NR carrier. +- For transmitter tests, alternately add 5MHz E-UTRA carriers at the low end and NB-IoT standalone carriers at the high end adjacent to the already placed carriers using 600 kHz spacing until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. The nominal carrier spacing defined in clause 4.5.1 shall apply for E-UTRA. +- If NR 5MHz and/or E-UTRA 5/10 MHz channel bandwidth is not supported, the narrowest carrier shall be selected. If 15kHz SCS is not supported for particular NR operating band, the smallest supported SCS declared per operating band shall be selected. + +#### 4.8.23.2 TC22 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in clause 4.7.2. + +### 4.9 RF channels and test models + +#### 4.9.1 RF channels + +Many tests in this TS are performed with the maximum Base Station RF Bandwidth located at the bottom, middle and top of the supported frequency range in the operating band. These are denoted as $B_{\text{RFBW}}$ (bottom), $M_{\text{RFBW}}$ (middle) and $T_{\text{RFBW}}$ (top). + +Unless otherwise stated, the test shall be performed at $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ defined as following: + +$B_{\text{RFBW}}$ : maximum Base Station RF Bandwidth located at the bottom of the supported frequency range in the operating band. + +$M_{\text{RFBW}}$ : maximum Base Station RF Bandwidth located in the middle of the supported frequency range in the operating band. $M_{\text{RFBW}}$ may be shifted maximum 100 kHz towards lower frequencies to align carriers with the channel raster. + +$T_{\text{RFBW}}$ : maximum Base Station RF Bandwidth located at the top of the supported frequency range in the operating band. + +For the test of certain RF requirements the present specification refers to test procedures defined in the single-RAT specifications. In this case, the interpretation of the RF channels to be tested shall be according to the definitions in the corresponding single-RAT specifications. + +For BS capable of multi-band operation, unless otherwise stated, the test shall be performed at $B_{\text{RFBW\_T'}}$ and $B'_{\text{RFBW\_T}}$ defined as following: + +- $B_{\text{RFBW\_T'}}$ : the Base Station RF Bandwidths located at the bottom of the supported frequency range in the lowest operating band and at the highest possible simultaneous frequency position, within the Maximum Radio Bandwidth, in the highest operating band. The Base Station RF Bandwidth(s) are located at the bottom of the supported frequency range(s) in the middle band(s). +- $B'_{\text{RFBW\_T}}$ : the Base Station RF Bandwidths located at the top of the supported frequency range in the highest operating band and at the lowest possible simultaneous frequency position, within the Maximum Radio Bandwidth, in the lowest operating band. The Base Station RF Bandwidth(s) are located at the top of the supported frequency range(s) in the middle band(s). + +NOTE: $B_{\text{RFBW\_T'}}$ = $B'_{\text{RFBW\_T}}$ = $B_{\text{RFBW\_T}}$ when the declared Maximum Radio Bandwidth spans all operating bands. $B_{\text{RFBW\_T'}}$ means the Base Station RF Bandwidths are located at the bottom of the supported frequency range in the lowest operating band and at the top of the supported frequency range in the highest operating band, and the Base Station RF Bandwidth(s) are located at the bottom of the supported frequency range(s) in the middle band(s) in the first test and then at the top of the supported frequency range(s) in the middle band(s) in the second test. + +When a test is performed by a test laboratory, the position of $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in each supported operating band, the position of $B_{\text{RFBW\_T'}}$ and $B'_{\text{RFBW\_T}}$ in the supported operating band combinations shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies. + +## 4.9.2 Test models + +a) Unless otherwise stated, carriers within MSR test configurations used for transmitter tests shall be configured as follows: + +- UTRA FDD carriers shall be configured according to TM1 as defined in TS 25.141 [10] clause 6.1.1.1. +- UTRA TDD carriers shall be configured according to Table 6.1A as defined in TS 25.142 [12] clause 6.2.4.1.2. +- E-UTRA carriers shall be configured according to E-TM1.1 as defined in clause 6.1.1.1 of TS 36.141 [9], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [9]. + +For BC3 CS3, BC3 CS16 and BC3 CS17 BS testing, E-UTRA carriers shall be configured according to E-TM1.1\_BC3CS3 defined in Annex E. + +For BC3 CS2 BS testing with NB-IoT inband and/or guard band, E-UTRA carriers shall be configured according to E-TM1.1\_BC3CS3 defined in Annex E. + +- GSM carriers shall use GMSK modulation as defined in TS 51.021 [11] clause 6.2.2. +- NB-IoT carriers shall be configured according to N-TM as defined in TS 36.141 [9] clauses 6.1.3, 6.1.4, 6.1.5 and 6.1.6. +- NR carriers shall be configured according to NR-FR1-TM1.1 as defined in clause 4.9.2 of TS 38.141-1 [26], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [26]. + +b) The configuration of the carriers in test configurations used for testing modulation quality and frequency error shall be as follows: + +- For the case that modulation accuracy is measured for UTRA FDD, the UTRA FDD carriers shall be configured according to the supported TM1, TM4 and if HS-PDSCH transmission using 16QAM is supported also TM5 as defined in TS 25.141 [10] clause 6.1.1.1, 6.1.1.4 and 6.1.1.4A whilst any remaining carriers from other RAT(s) shall be configured according to a). + +- For the case that modulation accuracy is measured for UTRA TDD, the UTRA TDD carriers shall be configured according to the supported modulation in Table 6.2A, Table 6.39A, Table 6.39B, Table 6.39C, Table 6.39D, Table 6.40A, Table 6.40B, Table 6.41A, Table 6.41B as defined in TS 25.142 [12] clause 6.3.4, 6.8.1, 6.8.2 and 6.8.3 whilst any remaining carriers from other RAT(s) shall be configured according to a). +- For the case that modulation accuracy is measured for E-UTRA, the E-UTRA carriers shall be configured according to the supported E-TM3.1, E-TM3.1a, E-TM3.1b, E-TM3.2, E-TM3.3 and E-TM2 as defined in clauses 6.1.1.4, 6.1.1.5, 6.1.1.6 and 6.1.1.3 of TS 36.141 [9], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [9], whilst any remaining carriers from other RAT(s) shall be configured according to a). + +For BC3 CS3, BC3 CS16 and BC3 CS17 BS testing, E-UTRA carriers shall be configured according to E-TM3.1\_BC3CS3, E-TM3.1a\_BC3CS3, E-TM3.1b\_BC3CS3, E-TM3.2\_BC3CS3, E-TM3.3\_BC3CS3, E-TM2\_BC3CS3, E-TM2a\_BC3CS3 and E-TM2b\_BC3CS3 defined in Annex E. + +- For the case that modulation accuracy is measured for GSM, the GSM carriers shall be configured for the supported modulation according to TS 51.021 [11] clause 6.2.2 whilst any remaining carriers from other RAT(s) shall be configured according to a). +- For the case that modulation accuracy is measured for NR, the NR carriers shall be configured according to the supported NR-FR1-TM2, NR-FR1-TM2a, NR-FR1-TM3.1, NR-FR1-TM3.1a, NR-FR1-TM3.2 and NR-FR1-TM3.3, as defined in clauses 4.9.2.2.3, 4.9.2.2.4, 4.9.2.2.5, 4.9.2.2.6, 4.9.2.2.7 and 4.9.2.2.8 of TS 38.141-1 [26], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [26], whilst any remaining carriers from other RAT(s) shall be configured according to a). + +For the test of certain RF requirements clause 5 refers to the test configurations as defined in the single-RAT specifications. In this case, the transmitter test signals and test models as defined within the referred test specification for the RF requirement shall be used. + +## 4.10 BS configurations + +### 4.10.1 Transmit configurations + +Unless otherwise stated, the transmitter characteristics in clause 6 are specified at the BS antenna connector (test port A) with a full complement of transceivers for the configuration in normal operating conditions. If any external apparatus such as a TX amplifier, a filter or the combination of such devices is used, requirements apply at the far end antenna connector (test port B). + +![Diagram of transmitter test ports showing a BS cabinet connected to an External PA (if any) and an External device (e.g. TX filter, if any). Test port A is at the BS cabinet output, and Test port B is at the External device output. An arrow points from Test port B towards the antenna connector.](453a1dc18dd2dd3334d19f453b04d11b_img.jpg) + +The diagram illustrates the transmitter test ports. It shows a sequence of components connected in series: a 'BS cabinet', an 'External PA (if any)', and an 'External device e.g. TX filter (if any)'. The connection between the BS cabinet and the External PA is labeled 'Test port A'. The connection between the External device and the antenna is labeled 'Test port B'. An arrow points from Test port B towards the antenna connector, with the text 'Towards antenna connector' and a dashed line indicating the path. + +Diagram of transmitter test ports showing a BS cabinet connected to an External PA (if any) and an External device (e.g. TX filter, if any). Test port A is at the BS cabinet output, and Test port B is at the External device output. An arrow points from Test port B towards the antenna connector. + +Figure 4.10.1-1: Transmitter test ports + +#### 4.10.1.1 Transmission with multiple transmitter antenna connectors + +Unless otherwise stated, for the tests in clause 6 of the present document, the requirement applies for each transmitter antenna connector in the case of transmission with multiple transmitter antenna connectors. + +Transmitter requirements are tested at the antenna connector, with the remaining antenna connector(s) being terminated. If the manufacturer has declared the transmitter paths to be equivalent, it is sufficient to measure the signal at any one of the transmitter antenna connectors. + +## 4.10.2 Receive configurations + +Unless otherwise stated, the receiver characteristics in clause 7 are specified at the BS antenna connector (test port A) with a full complement of transceivers for the configuration in normal operating conditions. If any external apparatus such as a RX amplifier, a filter or the combination of such devices is used, requirements apply at the far end antenna connector (test port B). + +![Diagram of receiver test ports showing a BS cabinet connected to an External LNA (if any) and an External device (e.g., RX filter, if any). Test port A is at the BS cabinet connector, and Test port B is at the far end antenna connector. A signal path is shown from the BS cabinet through the external devices to Test port B, with a label 'From antenna connector' and an arrow pointing towards Test port B.](57939c16065211317c5442cf2a4009e0_img.jpg) + +The diagram illustrates the receiver test ports. It shows a 'BS cabinet' connected to an 'External LNA (if any)' and then to an 'External device e.g. RX filter (if any)'. A signal path is shown from the BS cabinet through these external devices. 'Test port A' is indicated at the connector between the BS cabinet and the External LNA. 'Test port B' is indicated at the far end connector, with an arrow pointing to it from the text 'From antenna connector'. + +Diagram of receiver test ports showing a BS cabinet connected to an External LNA (if any) and an External device (e.g., RX filter, if any). Test port A is at the BS cabinet connector, and Test port B is at the far end antenna connector. A signal path is shown from the BS cabinet through the external devices to Test port B, with a label 'From antenna connector' and an arrow pointing towards Test port B. + +Figure 4.10.2-1: Receiver test ports + +### 4.10.2.1 Reception with multiple receiver antenna connectors, receiver diversity + +For the tests in clause 7 of the present document, the requirement applies at each receiver antenna connector for receivers with antenna diversity or in the case of multi-carrier reception with multiple receiver antenna connectors. + +Receiver requirements are tested at the antenna connector, with the remaining receiver(s) disabled or their antenna connector(s) being terminated. If the manufacturer has declared the receiver paths to be equivalent, it is sufficient to apply the specified test signal at any one of the receiver antenna connectors. + +For a multi-band BS, multi-band tests for blocking and intermodulation are performed with the interferer(s) applied to each antenna connector mapped to the receiver for the wanted signal(s), however only to one antenna at a time. Antenna connectors to which no signals are applied are terminated. + +## 4.10.3 Duplexers + +The requirements of the present document shall be met with a duplexer fitted, if a duplexer is supplied as part of the BS. + +NOTE: The present release of this specification does not contain test requirements for the case that the duplexer is supplied as an option by the manufacturer. This is left for future releases. + +## 4.10.4 Power supply options + +If the BS 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. + +This applies particularly if a BS contains a DC rail which can be supplied either externally or from an internal mains power supply. In this case, the conditions of extreme power supply for the mains power supply options can be tested by testing only the external DC supply option. The range of DC input voltages for the test should be sufficient to verify the performance with any of the power supplies, over its range of operating conditions within the BS, including variation of mains input voltage, temperature and output current. + +## 4.10.5 Ancillary RF amplifiers + +The requirements of the present document shall be met with the ancillary RF amplifier fitted. At tests according to clauses 6 and 7 for TX and RX respectively, the ancillary amplifier is connected to the BS by a connecting network (including any cable(s), attenuator(s), etc.) with applicable loss to make sure the appropriate operating conditions of the ancillary amplifier and the BS. The applicable connecting network loss range is declared by the manufacturer. Other + +characteristics and the temperature dependence of the attenuation of the connecting network are neglected. The actual attenuation value of the connecting network is chosen for each test as one of the applicable extreme values. The lowest value is used unless otherwise stated. + +Sufficient tests should be repeated with the ancillary amplifier fitted and, if it is optional, without the ancillary RF amplifier to verify that the BS meets the requirements of the present document in both cases. + +When testing, the following tests shall be repeated with the optional ancillary amplifier fitted according to Table 4.10.5-1, where x denotes that the test is applicable: + +**Table 4.10.5-1: Tests applicable to ancillary RF Amplifiers** + +| Receiver Tests | Clause | TX amplifier only | RX amplifier only | TX/RX amplifiers combined (Note) | +|-------------------|--------|-------------------|-------------------|----------------------------------| +| | 7.2 | | X | X | +| | 7.4 | | X | X | +| | 7.5 | | X | X | +| | 7.6 | | X | X | +| | 7.7 | | X | | +| Transmitter Tests | 6.2 | X | | X | +| | 6.6.1 | X | | X | +| | 6.6.2 | X | | X | +| | 6.6.3 | X | | X | +| | 6.6.4 | X | | X | +| | 6.7 | X | | X | + +NOTE: Combining can be by duplex filters or any other network. The amplifiers can either be in RX or TX branch or in both. Either one of these amplifiers could be a passive network. + +In test according to clauses 6.2 and 7.2 highest applicable attenuation value is applied. + +#### 4.10.6 BS with integrated Iuant BS modem + +Unless otherwise stated, for the tests in the present document, the integrated Iuant BS modem shall be switched off. Spurious emissions according to clauses 6.6.4 and 7.7 shall be measured only for frequencies above 20MHz with the integrated Iuant BS modem switched on. + +#### 4.10.7 BS using antenna arrays + +A BS may be configured with a multiple antenna port connection for some or all of its transceivers or with an antenna array related to one cell (not one array per transceiver). This clause applies to a BS which meets at least one of the following conditions: + +- the transmitter output signals from one or more transceiver appear at more than one antenna port; or +- there is more than one receiver antenna port for a transceiver or per cell and an input signal is required at more than one port for the correct operation of the receiver thus the outputs from the transmitters as well as the inputs to the receivers are directly connected to several antennas (known as "aircombining"); or +- transmitters and receivers are connected via duplexers to more than one antenna. + +In case of diversity or spatial multiplexing, multiple antennas are not considered as an antenna array. + +If a BS is used, in normal operation, in conjunction with an antenna system which contains filters or active elements which are necessary to meet the BS requirements, the conformance tests may be performed on a system comprising the BS together with these elements, supplied separately for the purposes of testing. In this case, it must be demonstrated that the performance of the configuration under test is representative of the system in normal operation, and the conformance assessment is only applicable when the BS is used with the antenna system. + +For conformance testing of such a BS, the following procedure may be used. + +#### 4.10.7.1 Receiver tests + +For each test, the test signals applied to the receiver antenna connectors shall be such that the sum of the powers of the signals applied equals the power of the test signal(s) specified in the test. + +An example of a suitable test configuration is shown in figure 4.10.7.1-1. + +![Figure 4.10.7.1-1: Receiver test set-up diagram. A 'Test input port' labeled P_s is connected to a 'Splitting network'. The 'Splitting network' has three output ports, each labeled P_i, which are connected to a 'Base Station'. A dashed vertical line labeled 'Rx antenna interface' is positioned between the splitting network and the base station. To the right of the base station, the text P_s = sum(P_i), where P_s is the required input power specified is shown.](ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg) + +Figure 4.10.7.1-1: Receiver test set-up diagram. A 'Test input port' labeled P\_s is connected to a 'Splitting network'. The 'Splitting network' has three output ports, each labeled P\_i, which are connected to a 'Base Station'. A dashed vertical line labeled 'Rx antenna interface' is positioned between the splitting network and the base station. To the right of the base station, the text P\_s = sum(P\_i), where P\_s is the required input power specified is shown. + +**Figure 4.10.7.1-1: Receiver test set-up** + +For spurious emissions from the receiver antenna connector, the test may be performed separately for each receiver antenna connector. + +#### 4.10.7.2 Transmitter tests + +For each test, the test signals applied to the transmitter antenna connectors ( $P_i$ ) shall be such that the sum of the powers of the signals applied equals the power of the test signal(s) ( $P_s$ ) specified in the test. This may be assessed by separately measuring the signals emitted by each antenna connector and summing the results, or by combining the signals and performing a single measurement. The characteristics (e.g. amplitude and phase) of the combining network should be such that the power of the combined signal is maximised. + +An example of a suitable test configuration is shown in figure 4.10.7.2-1. + +![Figure 4.10.7.2-1: Transmitter test set-up diagram. A 'Base Station' has three output ports, each labeled P_i, which are connected to a 'Combining network'. A dashed vertical line labeled 'Tx antenna interface' is positioned between the base station and the combining network. The 'Combining network' has a single output port labeled P_s, which is connected to a 'Test output port'. To the right of the test output port, the text P_s = sum(P_i), where P_s is the required output power specified is shown.](fa3258abeaa067802e97eb4d1901572f_img.jpg) + +Figure 4.10.7.2-1: Transmitter test set-up diagram. A 'Base Station' has three output ports, each labeled P\_i, which are connected to a 'Combining network'. A dashed vertical line labeled 'Tx antenna interface' is positioned between the base station and the combining network. The 'Combining network' has a single output port labeled P\_s, which is connected to a 'Test output port'. To the right of the test output port, the text P\_s = sum(P\_i), where P\_s is the required output power specified is shown. + +**Figure 4.10.7.2-1: Transmitter test set-up** + +For Intermodulation attenuation, the test may be performed separately for each transmitter antenna connector. + +## 4.11 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 clause 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. Required manufacturer declarations may be included here. + +## **X.2 Minimum requirement** + +This clause contains the reference to the clause to the 3GPP reference (or core) specification which defines the minimum requirement. + +## **X.3 Test purpose** + +This clause defines the purpose of the test. + +## **X.4 Method of test** + +### **X.4.1 Initial conditions** + +This clause defines the initial conditions for each test, including the test environment, the RF channels to be tested and the basic measurement set-up. For the test of certain RF requirements the present specification refers to the test method of the single-RAT specifications. In this case, the initial conditions as defined within the referred test specification for the RF requirement shall be used. + +### **X.4.2 Procedure** + +This clause describes the steps necessary to perform the test and provides further details of the test definition like point of access (e.g. test port), domain (e.g. frequency-span), range, weighting (e.g. bandwidth), and algorithms (e.g. averaging). For the test of certain RF requirements the present specification refers to the test method of the single-RAT specifications. In this case, the test procedure as defined within the referred test specification for the RF requirement shall be used. + +## **X.5 Test requirement** + +This clause defines the pass/fail criteria for the equipment under test. See clause 4.1.3 Interpretation of measurement results. For the test of certain RF requirements the present specification refers to the requirements of the single-RAT specifications. In this case, the test requirement as defined within the referred test specification for the RF requirement shall be used. + +# **4.12 Requirements for BS capable of multi-band operation** + +For BS capable of multi-band operation (for NR this refers to BS type 1-C with a multi-band connector), the RF requirements in clause 6 and 7 apply for each supported operating band unless otherwise stated. For some requirements it is explicitly stated that specific additions or exclusions to the requirement apply for BS capable of multi-band operation. In the case of multiband operation of a BS, single-RAT operation and the corresponding applicability of the requirements for each operating band is determined based on the RAT configuration within only that operating band, unless otherwise stated. + +For BS capable of multi-band operation, various structures in terms of combinations of different transmitter and receiver implementations (multi-band or single band) with mapping of transceivers to one or more antenna port(s) in different ways are possible. In the case where multiple bands are mapped on an antenna connector, the exclusions or provisions for multi-band capable BS are applicable to this antenna connector. In the case where a single band is mapped on an antenna connector, the following applies: + +- Single-band transmitter spurious emissions, operating band unwanted emissions, ACLR, transmitter intermodulation and receiver spurious emissions requirements apply to this antenna connector that is mapped to single-band. +- If the BS is configured for single-band operation, single-band requirements shall apply to this antenna connector configured for single-band operation and no exclusions or provisions for multi-band capable BS are applicable. Single-band requirements are tested separately at the antenna connector configured for single-band operation, with all other antenna connectors terminated. + +For a band supported by a Base Station where the transmitted carriers are not processed in active RF components together with carriers in any other band, single-band transmitter requirements shall apply. For a band supported by a + +Base Station where the received carriers are not processed in active RF components together with carriers in any other band, single-band receiver requirements shall apply. + +For a BS capable of multi-band operation supporting BC3 bands for TDD, the RF requirements in the present specification assume synchronized operation, where no simultaneous uplink and downlink occur between the bands. + +The RF requirements in the present specification are FFS for multi-band operation supporting bands for both FDD and TDD. + +## 4.13 Tests for BS capable of multi-band operation with three or more bands + +For BS supports multiple multi-band combinations, the test(s) shall be applied using the following principles: + +- 1) The supported multi-band combination covering the widest radio bandwidth should be tested. +- 2) Among the remaining supported multi-band combinations, the following ones should also be tested: + - Those with a larger rated total output power (per band or per band combination). + - Those with a larger total number of supported carriers (per band or per band combination). + - Those with a larger Maximum Base Station RF Bandwidth (per band). + +--- + +## 5 Applicability of requirements and test configurations + +The present clause defines for each RF test requirement the set of mandatory test configurations which shall be used for demonstrating conformance. This is specified in the Table 5.2-1 and Table 5.2-1a for single-RAT Multi-carrier, Table 5.1-1, Table 5.1-1a, Table 5.1-1b and Table 5.1-1c for multi-RAT Base Stations and Table 5.3-1 for multi-band capable Base Station. + +Requirements apply according to the declared RAT Capability Set (CS) within each supported operating band of the MSR Base Station and the Band Category of the declared operating band (BC1, BC2 or BC3), as listed in the heading of each table. Some RF requirements listed in the tables may not be mandatory or they may apply only regionally. This is further specified for each requirement in clause 6 and 7, and in Table 4.3-1. + +For a declared RAT Capability Set (CS) in Table 5.1-1, 5.1-1a, 5.1-1b, 5.1-1c and 5.2-1, only the requirements listed in the column for that CS apply. Requirements listed under CS other than the declared CS(s) need not be tested. In case the BS is declared to support more than one CS, the tests that are common between different supported CSs are not repeated. + +For a BS declared to be capable of contiguous operation only, the test configuration(s) in Tables 5.1-1, 5.1-1c and 5.2-1 denoted by a "C" and entries that refer to single-RAT specifications shall be used for testing. + +For a BS declared to be capable of contiguous and non-contiguous operation and where the parameters in the manufacturer's declaration according to clause 4.7.2 are identical for contiguous and non-contiguous operation (within subgroup in case of CS7), the test configuration(s) in Table 5.1-1, 5.1-1c and 5.2-1 denoted by "CNC" and entries that refer to single-RAT specifications shall be used. + +For a BS declared to be capable of contiguous and non-contiguous operation and where the parameters in the manufacturer's declaration according to clause 4.7.2 are not identical for contiguous and non-contiguous operation (within subgroup in case of CS7), the test configuration(s) in Table 5.1-1, 5.1-1c and 5.2-1 denoted by "C/NC" and entries that refer to single-RAT specifications shall be used for testing. + +For a BS declared to support NB-IoT operating in-band, the test configuration(s) in Table 5.1-1 and 5.2-1 denoted by "NI" and entries that refer to single-RAT specifications shall be used for testing. For a BS declared to support NB-IoT operating in-band, the test configuration(s) in Table 5.1-1c denoted by "NI" for BS capable of contiguous operation only, by "NCNI" for BS capable of contiguous and non-contiguous operation with same declared parameters, by "C/NCNI" for BS capable of contiguous and non-contiguous operation with different declared parameters and entries that refer to single-RAT specifications shall be used for testing. + +For a BS declared to support NB-IoT operating in guard band, the test configuration(s) in Table 5.1-1 and 5.2-1 denoted by "NG" and entries that refer to single-RAT specifications shall be used for testing. For a BS declared to support NB-IoT operating in guard band, the test configuration(s) in Table 5.1-1c denoted by "NG" for BS capable of contiguous operation only, by "NCNG" for BS capable of contiguous and non-contiguous operation with same declared parameters, by "C/NCNG" for BS capable of contiguous and non-contiguous operation with different declared parameters and entries that refer to single-RAT specifications shall be used for testing. + +For a BS declared to support NB-IoT operating in guard band and in-band, the test configuration(s) in Table 5.1-1, 5.1-1c and 5.2-1 denoted by "NG" or/and "NI" and entries that refer to single-RAT specifications shall be used for testing. + +For a BS declared to support NB-IoT standalone, the test configuration(s) in Table 5.1-1a, 5.1-1b, 5.1-1c and 5.2-1 and entries that refer to single-RAT specifications shall be used for testing. + +For some of the RF test requirements entries within Tables 5.1-1 and 5.2-1 refer to the single-RAT specifications; this is denoted by "(TS 25.141)", "(TS 25.142)", "(TS 36.141)", "(TS 51.021)" or "(TS 38.141-1)". In this case the following shall apply: + +- transmitter test signals and test models as defined within the referred test specification shall be used, see clause 4.9.2. For some RF requirements this comprises a mandatory test case in addition to a test case using the MSR test configurations defined in clause 4.8. +- for some RF requirements the initial conditions and test procedure as defined within the referred single-RAT test specification for the RF requirement shall be used. This is specified in further detail in clauses 6, 7 and 8 of the present document. +- for some RF requirements the test requirement as defined within the referred single-RAT test specification for the RF requirement shall be used. This is specified in further detail in clauses 6, 7 and 8 of the present document. In this case (see clause 4.1): + - The maximum acceptable uncertainty of the Test System for test requirements are defined in the respective referred test specification + - Test Tolerances are defined in the respective referred test specification. + - If the parameters in the manufacturer's declarations according to clause 4.7.2 are not identical for contiguous and non-contiguous operation, the parameters for contiguous operation shall be used for the test in the single RAT test specification. + +For a BS declared to be capable of multi-band operation, the applicability of the requirement for each operating band is determined by the RAT configuration within that operating band as identified in Tables 5.1-1, 5.1-1c and 5.2-1, unless otherwise stated. The testing of multi-band capable BS shall be according to Table 5.3-1 as follows: + +- For requirements test denoted by SBT (Single Band Test), the test configuration (s) in Table 5.1-1, 5.1-1c and 5.2-1 shall be used for each operating band depending on the RAT configuration within that band. +- For requirements test denoted by MBT (Multi-Band Test), the test configuration (s) in Table 5.3-1 shall be used depending on the Band Category of the declared operating band combination. + +## 5.1 Multi-RAT capable Base Stations + +**Table 5.1-1: Test configurations for capability sets (CS 3-7) for Multi-RAT capable BS** + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|----------------------------------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------|-----------------------------------------------|----------------------------------------------|-------------------------------------------------------------------------------------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| 6.2 Base Station output power | - | - | - | - | - | - | - | +| Base Station maximum output power | C: TC3a
CNC: TC3a
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC: TC3a
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC4a
CNC: TC4a
C/NC: TC4a,
NTC4a | C: TC4b
CNC: TC4b
C/NC: TC4b,
NTC4b
NI: TC15
NG: TC18 | C: TC4c
CNC: TC4c
C/NC: TC4c,
NTC4c | C: TC4a*,
TC4b, TC3a*

CNC: TC4a*,
TC4b, TC3a*

C/NC: TC4a*,
NTC4a*, TC4b,
NTC4b, TC3a*,
NTC3*

NI:
TC15,TC16*

NG:
TC18,TC19* | +| Additional regional requirement (only for band 34) | N/A | N/A | Compliance stated by manufacturer declaration | N/A | N/A | N/A | N/A | +| E-UTRA for DL RS power | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT for DL RS power | (TS 36.141) | (TS 36.141) | N/A | N/A | (TS 36.141) | N/A | (TS 36.141) | +| UTRA FDD primary CPICH power | (TS 25.141) | (TS 25.141) | N/A | (TS 25.141) | N/A | (TS 25.141) | (TS 25.141)* | +| UTRA FDD secondary CPICH power | (TS 25.141) | (TS 25.141) | N/A | (TS 25.141) | N/A | (TS 25.141) | (TS 25.141)* | +| UTRA TDD primary CCPCH power | N/A | N/A | (TS 25.142) | N/A | N/A | N/A | N/A | +| 6.3 Output power dynamics | - | - | - | - | - | - | - | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD | (TS 25.141) | (TS 25.141) | N/A | (TS 25.141) | N/A | (TS 25.141) | (TS 25.141)* | +| UTRA TDD | N/A | N/A | (TS 25.142) | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | (TS 51.021) | TC4b | +| NB-IoT | (TS 36.141) | (TS 36.141) | N/A | N/A | (TS 36.141) | N/A | (TS 36.141) | +| 6.4 Transmit ON/OFF power | - | - | - | - | - | - | - | +| Transmitter OFF power | N/A | N/A | C: TC3b | N/A | N/A | N/A | N/A | +| Transmitter transient period | N/A | N/A | C: TC3b | N/A | N/A | N/A | N/A | +| 6.5 Transmitted signal quality | - | - | - | - | - | - | - | +| 6.5.1 Modulation quality | - | - | - | - | - | - | - | +| E-UTRA | C: TC3a
CNC: TC3a
C/NC: TC3a, | C: TC3a
CNC: TC3a
C/NC: TC3a, | C: TC3b
NI/NG :
(Note2) | N/A | C: TC4b
CNC: TC4b
C/NC: TC4b, | C: TC4c
CNC: TC4c
C/NC: TC4c, | C: TC4b
CNC: TC4b
C/NC: TC4b, | + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|----------------|------------------------------------------------------------------------|----------------------------|-----|------------------------|-------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| | NTC3
NI/NG :
(Note2) | NTC3
NI/NG :
(Note2) | | | NTC4b
NI/NG:
(Note2) | NTC4c | NTC4b
NI/NG: (Note2) | + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|-----------------------------------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------|--------------------------------------------------|-----------------------------------------------|-------------------------------------------------------------------------------------|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| UTRA FDD | C: TC3a
CNC: TC3a
C/NC: TC3a,
NTC3 | C: TC3a
CNC: TC3a
C/NC: TC3a,
NTC3 | N/A | C: TC4a
CNC: TC4a
C/NC: TC4a,
NTC4a | N/A | C: TC4c
CNC: TC4c
C/NC: TC4c,
NTC4c | C: TC4a*
CNC: TC4a*
C/NC: TC4a*,
NTC4a* | +| UTRA TDD | N/A | N/A | C: TC3b | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | C: TC4a
CNC: TC4a
C/NC: TC4a,
NTC4a | C: TC4b
CNC: TC4b
C/NC: TC4b,
NTC4b | C: TC4c
CNC: TC4c
C/NC: TC4c,
NTC4c | C: TC4b
CNC: TC4b
C/NC: TC4b,
NTC4b | +| NB-IoT | N/A : (Note2) | N/A : (Note2) | N/A: (Note 2) | N/A | N/A: (Note2) | N/A | N/A: (Note2) | +| 6.5.2 Frequency
error | - | - | - | - | - | - | - | +| E-UTRA | Same TC as
used in 6.5.1
NI/NG:
(Note2) | Same TC as
used in 6.5.1
NI/NG:
(Note2) | Same TC as
used in 6.5.1
NI/NG:
(Note2) | N/A | Same TC as
used in 6.5.1
NI/NG:
(Note2) | Same TC as
used in 6.5.1 | Same TC as
used in 6.5.1
NI/NG: (Note2) | +| UTRA FDD | Same TC as
used in 6.5.1 | Same TC as
used in 6.5.1 | N/A | Same TC as
used in 6.5.1 | N/A | Same TC as
used in 6.5.1 | Same TC as
used in 6.5.1 | +| UTRA TDD | N/A | N/A | Same TC as
used in 6.5.1 | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | Same TC as
used in 6.5.1 | Same TC as
used in 6.5.1 | Same TC as
used in 6.5.1 | Same TC as
used in 6.5.1 | +| NB-IoT | N/A: (Note2) | N/A: (Note2) | N/A: (Note2) | N/A | N/A: (Note2) | N/A | N/A: (Note2) | +| 6.5.3 Time
alignment error | - | - | - | - | - | - | - | +| E-UTRA | (TS 36.141)
NI/NG:
(Note2) | (TS 36.141)
NI/NG:
(Note2) | (TS 36.141)
NI/NG:
(Note2) | N/A | (TS 36.141)
NI/NG:
(Note2) | (TS 36.141) | (TS 36.141)
NI/NG: (Note2) | +| UTRA FDD | (TS 25.141) | (TS 25.141) | N/A | (TS 25.141) | N/A | (TS 25.141) | (TS 25.141)* | +| UTRA TDD | N/A | N/A | (TS 25.142) | N/A | N/A | N/A | N/A | +| NB-IoT | N/A: (Note2) | N/A: (Note2) | N/A: (Note2) | N/A | N/A: (Note2) | N/A | N/A: (Note2) | +| 6.6 Unwanted
emissions | - | - | - | - | - | - | - | +| 6.6.1 Transmitter
spurious
emissions | - | - | - | - | - | - | - | +| (Category A) | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC4a
CNC: NTC4a
C/NC: TC4a,
NTC4a | C: TC4b
CNC: NTC4b
C/NC: TC4b,
NTC4b
NI: TC15
NG: TC18 | C: TC4c
CNC: NTC4c
C/NC: TC4c,
NTC4c | C: (TC4a,
TC3a)*, TC4b

CNC: (NTC4a,
NTC3)*,
NTC4b

C/NC: (TC4a,
NTC4a,TC3a,
NTC3)*,
TC4b,NTC4b

NI: TC15,
(TC16)*

NG: TC18,
(TC19)* | +| (Category B) | C: TC3a
CNC: NTC3
C/NC: TC3a, | C: TC3a
CNC: NTC3
C/NC: TC3a, | C: TC3b
NI: TC16
NG: TC19 | C: TC4a
CNC: NTC4a
C/NC: TC4a, | C: TC4b
CNC: NTC4b
C/NC: TC4b, | C: TC4c
CNC: NTC4c
C/NC: TC4c, | C: (TC4a,
TC3a)*, TC4b | + +| Capability Set | UTRA + E-UTRA
NB-loT in-band***,
NB-loT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-loT in-
band***,
NB-loT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-loT in-
band***,
NB-loT guard
band****
(CS7) | +|----------------|------------------------------------------------------------------------|------------------------------|-----|------------------------|-------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| | NTC3
NI: TC16
NG: TC19 | NTC3
NI: TC16
NG: TC19 | | NTC4a | NTC4b
NI: TC15
NG: TC18 | NTC4c | CNC: (NTC4a,
NTC3)*,
NTC4b

C/NC: (TC4a,
NTC4a, TC3a,
NTC3)*,
TC4b,NTC4b

NI: TC15,
(TC16)*

NG: TC18,
(TC19)* | + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|------------------------------------------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------|-----------------------------------------------|-------------------------------------------------------------------------------------|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| Additional
requirement for
BC2 (Category B) | N/A | N/A | N/A | C: TC4a
CNC: NTC4a
C/NC: TC4a,
NTC4a | C: TC4b
CNC: NTC4b
C/NC: TC4b,
NTC4b
NI: TC15
NG: TC18 | C: TC4c
CNC: NTC4c
C/NC: TC4c,
NTC4c | C: TC4a*,
TC4b
CNC: NTC4a*,
NTC4b

C/NC: (TC4a,
NTC4a)*,
TC4b,NTC4b

NI: TC15

NG: TC18 | +| Protection of the
BS receiver of own
or different BS | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC4a
CNC: NTC4a
C/NC: TC4a,
NTC4a | C: TC4b
CNC: NTC4b
C/NC: TC4b,
NTC4b
NI: TC15
NG: TC18 | C: TC4c
CNC: NTC4c
C/NC: TC4c,
NTC4c | C: (TC4a,
TC3a)*, TC4b

CNC: (NTC4a,
NTC3)*,
NTC4b

C/NC: (TC4a,
NTC4a, TC3a,
NTC3)*, TC4b,
NTC4b

NI: TC15,
(TC16)*

NG: TC18,
(TC19)* | +| Additional spurious
emissions
requirements | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC4a
CNC: NTC4a
C/NC: TC4a,
NTC4a | C: TC4b
CNC: NTC4b
C/NC: TC4b,
NTC4b
NI: TC15
NG: TC18 | C: TC4c
CNC: NTC4c
C/NC: TC4c,
NTC4c | C: (TC4a,
TC3a)*, TC4b

CNC: (NTC4a,
NTC3)*,
NTC4b

C/NC: (TC4a,
NTC4a, TC3a,
NTC3)*, TC4b,
NTC4b

NI: TC15,
(TC16)*

NG: TC18,
(TC19)* | +| Co-location with
other Base Stations | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC4a
CNC: NTC4a
C/NC: TC4a,
NTC4a | C: TC4b
CNC: NTC4b
C/NC: TC4b,
NTC4b
NI: TC15
NG: TC18 | C: TC4c
CNC: NTC4c
C/NC: TC4c,
NTC4c | C: (TC4a,
TC3a)*, TC4b

CNC: (NTC4a,
NTC3)*,
NTC4b

C/NC: (TC4a,
NTC4a, TC3a,
NTC3)*, TC4b,
NTC4b | + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|----------------|------------------------------------------------------------------------|-----|-----|------------------------|-------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| | | | | | | | NI: TC15,
(TC16)*

NG: TC18,
(TC19)* | + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|----------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| | BC1 | BC2 | BC3 | | | | | +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| 6.6.2 Operating band unwanted emissions | - | - | - | - | - | - | - | +| General requirement for Band Categories 1 and 3 | (TS 25.141)
(TS 36.141)
C: TC3a
CNC: TC3a, NTC3
C/NC: TC3a, NTC3
NI: TC16
NG: TC19 | N/A | (TS 25.142)
(TS 36.141)
C: TC3b
NI: TC16
NG: TC19 | N/A | N/A | N/A | N/A | +| General requirement for Band Category 2 | N/A | (TS 25.141)
(TS 36.141)
C: TC3a
CNC: TC3a, NTC3
C/NC: TC3a, NTC3
NI: TC16
NG: TC19 | N/A | (TS 25.141)
C: TC4a, TC4d (note1)
CNC:TC4a, TC4d(note1), NTC4a
C/NC: TC4a, TC4d(note1), NTC4a | (TS 36.141)
C: TC4b, TC4e (note1)
CNC:TC4b, TC4e(note1), NTC4b
C/NC: TC4b, TC4e(note1), NTC4b
NI: TC15
NG: TC18 | (TS 25.141)
(TS 36.141)
C: TC4c, TC4e (note1)
CNC: TC4c, TC4e (note1), NTC4c
C/NC: TC4c, TC4e (note1), NTC4c | (TS 36.141)
(TS 25.141)*
C: TC4b, TC3a*
CNC:TC4b, NTC4b, TC3a*, NTC3*
C/NC: TC4b, NTC4b, TC3a*, NTC3*
NI: TC15
NG: TC18 | +| GSM/EDGE single-RAT requirement | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | (TS 51.021) | N/A | +| Additional requirements | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | +| 6.6.3 Occupied bandwidth | - | - | - | - | - | - | - | +| Minimum requirement | (TS 25.141)
(TS 36.141) | (TS 25.141)
(TS 36.141) | (TS 25.142)
(TS 36.141) | (TS 25.141) | (TS 36.141) | (TS 25.141)
(TS 36.141) | (TS 25.141)*
(TS 36.141) | +| 6.6.4 Adjacent Channel Leakage power Ratio (ACLR) | - | - | - | - | - | - | - | +| E- UTRA | C: TC2
CNC: NTC2
C/NC:TC2, NTC2 | C: TC2
CNC: NTC2
C/NC:TC2, NTC2 | C: TC2
CNC: NTC2
C/NC:TC2, NTC2 | N/A | C: TC2
CNC: NTC2
C/NC:TC2, NTC2 | C: TC2
CNC: NTC2
C/NC:TC2, NTC2 | C: TC2
CNC: NTC2
C/NC:TC2, NTC2 | +| UTRA FDD | (TS 25.141) | (TS 25.141) | N/A | (TS 25.141) | N/A | N/A | (TS 25.141)* | +| UTRA TDD | N/A | N/A | (TS 25.142) | N/A | N/A | N/A | N/A | +| NB-IoT | NI: TC16
NG: TC19 | NI: TC16
NG: TC19 | NI: TC16
NG: TC19 | N/A | NI: TC15
NG: TC18 | N/A | NI: TC15, (TC16)*
NG: TC18, (TC19)* | +| Cumulative ACLR | CNC: NTC3
C/NC: NTC3 | CNC: NTC3
C/NC: NTC3 | | CNC: NTC1a
C/NC: NTC1a | CNC: NTC2
C/NC: NTC2 | CNC: NTC3
C/NC: NTC3 | CNC: NTC3*, NTC2**
C/NC: NTC3*, NTC2** | +| 6.7 Transmitter intermodulation | - | - | - | - | - | - | - | +| General requirement | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|---------------------------------------------------------|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| Additional requirement (BC1 and BC2) | CNC: NTC3
C/NC: NTC3 | Same TC as used in 6.6 | N/A | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | +| Additional requirement (BC3) | N/A | N/A | Same TC as used in 6.6 | N/A | N/A | N/A | N/A | +| 7.2 Reference sensitivity level | - | - | - | - | - | - | - | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD | (TS 25.141) | (TS 25.141) | N/A | (TS 25.141) | N/A | (TS 25.141) | (TS 25.141)* | +| UTRA TDD | N/A | N/A | (TS 25.142) | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | (TS 51.021) | TC5b | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | N/A | (TS 36.141) | +| 7.3 Dynamic range | - | - | - | - | - | - | - | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD | (TS 25.141) | (TS 25.141) | N/A | (TS 25.141) | N/A | (TS 25.141) | (TS 25.141)* | +| UTRA TDD | N/A | N/A | (TS 25.142) | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | (TS 51.021) | TC5b | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | N/A | (TS 36.141) | +| 7.4 In- band selectivity and blocking | - | - | - | - | - | - | - | +| General blocking requirement | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC5a
CNC: NTC5a
C/NC: TC5a,
NTC5a | C: TC5b
CNC: NTC5b
C/NC: TC5b,
NTC5b
NI: TC15
NG: TC18 | C: TC5b
CNC: NTC5c
C/NC: TC5b,
NTC5c | C: TC5b
CNC: NTC5b
C/NC: TC5b,
NTC5b
NI: TC15
NG: TC18 | +| General narrowband blocking requirement | C: TC3a,
TC6b
CNC: NTC3,
TC6b
C/NC: TC3a,
NTC3, TC6b
NI: TC16
NG: TC19 | C: TC3a,
TC6b
CNC: NTC3,
TC6b
C/NC: TC3a,
NTC3, TC6b
NI: TC16
NG: TC19 | C: TC3b,
TC6b
NI: TC16
NG: TC19 | C: TC5a,
TC6a
CNC:
NTC5a,
TC6a
C/NC: TC5a,
NTC5a,
TC6a | C: TC5b,
TC6b
CNC:
NTC5b,
TC6b
C/NC: TC5b,
NTC5b,
TC6b
NI: TC15
NG: TC18 | C: TC5b, TC6a
CNC: NTC5c,
TC6a
C/NC: TC5b,
NTC5c, TC6a | C: TC5b,
TC6a*
CNC: NTC5b,
TC6a*
C/NC: TC5b,
NTC5b, TC6a*
NI: TC15
NG: TC18 | +| Additional narrowband blocking requirement for GSM/EDGE | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | (TS 51.021) | TC5b | +| GSM/EDGE requirements for AM suppression | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | (TS 51.021) | TC5b | +| Additional BC3 blocking requirement | N/A | N/A | C: TC3b | N/A | N/A | N/A | N/A | +| 7.5 Out-of-band blocking | - | - | - | - | - | - | - | +| General requirement | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16 | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16 | C: TC3b
NI: TC16
NG: TC19 | C: TC5a
CNC: NTC5a
C/NC: TC5a,
NTC5a | C: TC5b
CNC: NTC5b
C/NC: TC5b,
NTC5b
NI: TC15 | C: TC5b
CNC: NTC5c,
C/NC: TC5b,
NTC5c | C: TC5b
CNC: NTC5b
C/NC: TC5b,
NTC5b
NI: TC15 | + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|----------------|------------------------------------------------------------------------|----------|-----|------------------------|-------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| | NG: TC19 | NG: TC19 | | | NG: TC18 | | NG: TC18 | + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|----------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|------------------------------------------|----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| Co-location
requirement | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC5a
CNC: NTC5a
C/NC: TC5a,
NTC5a | C: TC5b
CNC: NTC5b
C/NC: TC5b,
NTC5b
NI: TC15
NG: TC18 | C: TC5b
CNC: NTC5c
C/NC: TC5b,
NTC5c | C: TC5b
CNC: NTC5b
C/NC: TC5b,
NTC5b
NI: TC15
NG: TC18 | +| 7.6 Receiver
spurious
emissions | - | - | - | - | - | - | - | +| General
requirement | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC4a
CNC: NTC4a
C/NC: TC4a,
NTC4a | C: TC4b
CNC: NTC4b
C/NC: TC4b,
NTC4b
NI: TC15
NG: TC18 | C: TC4c
CNC: NTC4c
C/NC: TC4c,
NTC4c | C: (TC4a,
TC3a)*, TC4b

CNC: (NTC4a,
NTC3)*,
NTC4b

C/NC: (TC4a,
NTC4a, TC3a,
NTC3)*, TC4b,
NTC4b

NI: TC15,
(TC16)*

NG: TC18,
(TC19)* | +| Additional
requirement for
BC2 (Category B) | N/A | N/A | N/A | C: TC4a
CNC: NTC4a
C/NC: TC4a,
NTC4a | C: TC4b
CNC: NTC4b
C/NC: TC4b,
NTC4b
NI: TC15
NG: TC18 | C: TC4c
CNC: NTC4c
C/NC: TC4c,
NTC4c | C: TC4a*,
TC4b
CNC: NTC4a*,
NTC4b
C/NC: (TC4a,
NTC4a)*,
TC4b, NTC4b
NI: TC15
NG: TC18 | +| 7.7 Receiver
intermodulation | - | - | - | - | - | - | - | +| General
intermodulation
requirement | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3a
CNC: NTC3
C/NC: TC3a,
NTC3
NI: TC16
NG: TC19 | C: TC3b
NI: TC16
NG: TC19 | C: TC5a
CNC: NTC5a
C/NC: TC5a,
NTC5a | C: TC5b
CNC: NTC5b
C/NC: TC5b,
NTC5b
NI: TC15
NG: TC18 | C: TC5b
CNC: NTC5c
C/NC: TC5b,
NTC5c | C: TC5b
CNC: NTC5b
C/NC: TC5b,
NTC5b
NI: TC15
NG: TC18 | +| General
narrowband
intermodulation
requirement | C: TC3a,
TC6b
CNC: NTC3,
TC6b
C/NC: TC3a,
NTC3, TC6b
NI: TC16
NG: TC19 | C: TC3a
TC6b
CNC: NTC3,
TC6b
C/NC: TC3a,
NTC3; TC6b
NI: TC16
NG: TC19 | C: TC3b,
TC6b
NI: TC16
NG: TC19 | C: TC5a,
TC6a
CNC:
NTC5a,
TC6a
C/NC: TC5a
NTC5a,
TC6a | C: TC5b,
TC6b
CNC:
NTC5b,
TC6b
C/NC: TC5b,
NTC5b,
TC6b
NI:
TC15
NG: TC18 | C: TC5b, TC6a
CNC: NTC5c,
TC6a
C/NC: TC5b,
NTC5c, TC6a | C: TC5b,
TC6a*
CNC: NTC5b,
TC6a*
C/NC: TC5b
NTC5b, TC6a*
NI: TC15,
(TC16)*
NG: TC18,
(TC19)* | +| Additional
narrowband
intermodulation
requirement for | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | (TS 51.021) | TC5b | + +| Capability Set | UTRA + E-UTRA
NB-IoT in-band***,
NB-IoT guard band****
(CS 3) | | | GSM+
UTRA
(CS 4) | GSM +
E-UTRA,
NB-IoT in-
band***,
NB-IoT
guard
band****
(CS 5) | GSM + UTRA
+ E-UTRA
(CS 6) | GSM+UTRA/
E-UTRA,
UTRA+
E-UTRA,
NB-IoT in-
band***,
NB-IoT guard
band****
(CS7) | +|---------------------------------------|------------------------------------------------------------------------|-------------|-------------|------------------------|-------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | BC2 | BC2 | BC2 | +| GSM/EDGE | | | | | | | | +| 7.8 In-channel
selectivity | - | - | - | - | - | - | - | +| E-UTRA
requirement | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT
requirement | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | N/A | (TS 36.141) | + +NOTE 1: The TC shall be used for performing tests when the declared Base Station RF Bandwidth for GSM single-RAT operation is not equal to the declared Base Station RF Bandwidth for multi-RAT operations and the frequency range supported by the BS is a subset of the operating band, or when the maximum Base Station RF Bandwidth covers the entire operating band. + +NOTE 2: There is no specific test with NB-IoT for those requirements, tests could be performed using E-UTRA signal only, without NB-IoT. + +NOTE \*: For Band 3, the test configuration is only applicable if UTRA is declared to be supported in Band 3. +For other BC2 bands, the test configurations are always applicable. + +NOTE \*\*: For Band 3 only, the test configuration is only applicable if UTRA is not declared to be supported in Band 3. + +NOTE \*\*\*: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing. + +NOTE \*\*\*\*: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing. + +**Table 5.1-1a: Test configurations for capability sets (CS9-13) for Multi-RAT capable BS** + +| Capability Set | GSM+NB-IoT standalone (CS 9) | UTRA + NB-IoT standalone (CS 10) | | E-UTRA + NB-IoT standalone (CS 11) | | | GSM+UTRA+NB-IoT standalone (CS 12) | GSM+ E-UTRA+NB-IoT standalone (CS 13) | +|----------------------------------------------------|------------------------------|----------------------------------|-------------|------------------------------------|-------------|-------------|------------------------------------|---------------------------------------| +| | | BC1 | BC2 | BC1 | BC2 | BC3 | | | +| BS test case | BC2 | BC1 | BC2 | BC1 | BC2 | BC3 | BC1 | BC2 | +| 6.2 Base Station output power | - | - | - | - | - | - | - | - | +| Base Station maximum output power | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Additional regional requirement (only for band 34) | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| E-UTRA for DL RS power | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | +| NB-IoT for DL RS power | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD primary CPICH power | N/A | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | (TS 25.141) | N/A | +| UTRA FDD secondary CPICH power | N/A | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | (TS 25.141) | N/A | +| UTRA TDD primary CCPCH power | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| 6.3 Output power dynamics | - | - | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | +| UTRA FDD | N/A | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | (TS 25.141) | N/A | +| UTRA TDD | N/A | N/A | N/A | N/A | N/A | N/A | | N/A | +| GSM/EDGE | (TS 51.021) | N/A | N/A | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 6.4 Transmit ON/OFF power | - | - | - | - | - | - | - | - | +| Transmitter OFF power | N/A | N/A | N/A | N/A | N/A | TC11 | N/A | N/A | +| Transmitter transient period | N/A | N/A | N/A | N/A | N/A | TC11 | N/A | N/A | +| 6.5 Transmitted signal quality | - | - | - | - | - | - | - | - | +| 6.5.1 Modulation quality | - | - | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | TC11 | TC11 | TC11 | N/A | TC13 | +| UTRA FDD | N/A | TC10 | TC10 | N/A | N/A | N/A | TC12 | N/A | +| UTRA TDD | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| GSM/EDGE | TC9 | N/A | N/A | N/A | N/A | N/A | TC12 | TC13 | + +| NB-IoT | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +|------------------------------------------------------|--------------------------|------------------------------------|--------------------------|--------------------------|--------------------------|--------------------------|--------------------------|--------------------------| +| 6.5.2 Frequency error | - | - | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | N/A | Same TC as used in 6.5.1 | +| UTRA FDD | N/A | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | N/A | N/A | N/A | Same TC as used in 6.5.1 | N/A | +| UTRA TDD | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| GSM/EDGE | Same TC as used in 6.5.1 | N/A | N/A | N/A | N/A | N/A | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | +| NB-IoT | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | +| 6.5.3 Time alignment error | - | - | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | +| UTRA FDD | N/A | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | (TS 25.141) | N/A | +| UTRA TDD | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 6.6 Unwanted emissions | - | - | - | - | - | - | - | - | +| 6.6.1 Transmitter spurious emissions | - | - | - | - | - | - | - | - | +| (Category A) | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| (Category B) | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Additional requirement for BC2 (Category B) | TC9 | TC10 | TC10 | TC11 | TC11 | N/A | TC12 | TC13 | +| Protection of the BS receiver of own or different BS | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Additional spurious emissions requirements | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Co-location with other Base Stations | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| 6.6.2 Operating band unwanted emissions | - | - | - | - | - | - | - | - | +| General requirement for Band Categories 1 and 3 | N/A | (TS 36.141)
(TS 25.141)
TC10 | N/A | (TS 36.141)
TC11 | N/A | (TS 36.141)
TC11 | N/A | N/A | +| General | (TS 36.141) | N/A | (TS 36.141) | N/A | (TS 36.141) | N/A | (TS 36.141) | (TS 36.141) | + +| | | | | | | | | | +|----------------------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------| +| requirement for Band Category 2 | 1) TC9 | | 41) (TS 25.141) TC10 | | 41) TC11 | | ) (TS 25.141) TC12 | TC13 | +| GSM/EDGE single-RAT requirement | (TS 51.021) | N/A | N/A | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | +| Additional requirements | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | +| 6.6.3 Occupied bandwidth | - | - | - | - | - | - | - | - | +| Minimum requirement | (TS 36.141) | (TS 25.141) (TS 36.141) | (TS 25.141) (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 25.141) (TS 36.141) | (TS 36.141) | +| 6.6.4 Adjacent Channel Leakage Power Ratio (ACLR) | - | - | - | - | - | - | - | - | +| E- UTRA | N/A | N/A | N/A | TC11 | TC11 | TC11 | N/A | TC13 | +| UTRA FDD | N/A | TC10 | TC10 | N/A | N/A | N/A | TC12 | N/A | +| UTRA TDD | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| NB-IoT | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Cumulative ACLR | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| 6.7 Transmitter intermodulation | | - | | - | | | | | +| General requirement | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | +| Additional requirement (BC1 and BC2) | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | N/A | Same TC as used in 6.6 | Same TC as used in 6.6 | +| Additional requirement (BC3) | N/A | N/A | N/A | N/A | N/A | Same TC as used in 6.6 | N/A | N/A | +| 7.2 Reference sensitivity level | - | - | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | +| UTRA FDD | N/A | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | (TS 25.141) | N/A | +| UTRA TDD | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| GSM/EDGE | (TS 51.021) | N/A | N/A | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 7.3 Dynamic range | - | - | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | N/A | (TS 36.141) | +| UTRA FDD | N/A | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | (TS 25.141) | N/A | + +| | | | | | | | | | +|--|--|-----|-----|--|--|--|---|--| +| | | 41) | 41) | | | | ) | | +|--|--|-----|-----|--|--|--|---|--| + +| | | | | | | | | | +|----------------------------------------------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------| +| UTRA TDD | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| GSM/EDGE | (TS 51.021) | (TS 51.021) | N/A | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 7.4 In-band selectivity and blocking | - | - | - | - | - | - | - | - | +| General blocking requirement | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| General narrowband blocking requirement | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Additional narrowband blocking requirement for GSM/EDGE | (TS 51.021) | N/A | N/A | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | +| GSM/EDGE requirements for AM suppression | (TS 51.021) | N/A | N/A | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | +| Additional BC3 blocking requirement | N/A | N/A | N/A | N/A | N/A | TC11 | N/A | N/A | +| 7.5 Out-of-band blocking | - | - | - | - | - | - | - | - | +| General requirement | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Co-location requirement | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| 7.6 Receiver spurious emissions | - | - | - | - | - | - | - | - | +| General requirement | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Additional requirement for BC2 (Category B) | TC9 | N/A | TC10 | N/A | TC11 | TC11 | TC12 | TC13 | +| 7.7 Receiver intermodulation | - | - | - | - | - | - | - | - | +| General intermodulation requirement | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| General narrowband intermodulation requirement | TC9 | TC10 | TC10 | TC11 | TC11 | TC11 | TC12 | TC13 | +| Additional narrowband intermodulation requirement for GSM/EDGE | (TS 51.021) | N/A | N/A | N/A | N/A | N/A | (TS 51.021) | (TS 51.021) | +| 7.8 In-channel selectivity | - | - | - | - | - | - | - | - | + +| | | | | | | | | | +|--------------------|-----|-----|-----|-------------|-------------|--------------|-----|-------------| +| E-UTRA requirement | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141 ) | N/A | (TS 36.141) | +| NB-IoT | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | + +**Table 5.1-1b: Test configurations for capability sets (CS14-15) for Multi-RAT capable BS** + +| Capability Set | UTRA + E-UTRA + NB-IoT standalone (CS 14) | | | GSM + UTRA + E-UTRA + NB-IoT standalone (CS 15) | +|----------------------------------------------------|-------------------------------------------|--------------------------|--------------------------|-------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | +| 6.2 Base Station output power | - | - | - | - | +| Base Station maximum output power | TC14 | TC14 | TC14 | TC13, TC12* | +| Additional regional requirement (only for band 34) | N/A | N/A | N/A | N/A | +| E-UTRA for DL RS power | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT for DL RS power | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD primary CPICH power | (TS 25.141) | (TS 25.141) | (TS 25.141) | (TS 25.141)* | +| UTRA FDD secondary CPICH power | (TS 25.141) | (TS 25.141) | (TS 25.141) | (TS 25.141)* | +| UTRA TDD primary CCPCH power | N/A | N/A | N/A | N/A | +| 6.3 Output power dynamics | - | - | - | - | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD | (TS 25.141) | (TS 25.141) | (TS 25.141) | (TS 25.141)* | +| UTRA TDD | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | TC13 | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 6.4 Transmit ON/OFF power | - | - | - | - | +| Transmitter OFF power | N/A | N/A | TC14 | N/A | +| Transmitter transient period | N/A | N/A | TC14 | N/A | +| 6.5 Transmitted signal quality | - | - | - | - | +| 6.5.1 Modulation quality | - | - | - | - | +| E-UTRA | TC14 | TC14 | TC14 | TC13 | +| UTRA FDD | TC14 | TC14 | TC14 | TC12* | +| UTRA TDD | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | TC13 | +| NB-IoT | TC14 | TC14 | TC14 | TC13 | +| 6.5.2 Frequency error | - | - | - | - | +| E-UTRA | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | +| UTRA FDD | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | +| UTRA TDD | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | Same TC as used in 6.5.1 | +| NB-IoT | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | +| 6.5.3 Time alignment error | - | - | - | - | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD | (TS 25.141) | (TS 25.141) | (TS 25.141) | (TS 25.141)* | +| UTRA TDD | N/A | N/A | N/A | N/A | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 6.6 Unwanted emissions | - | - | - | - | +| 6.6.1 Transmitter spurious emissions | - | - | - | - | +| (Category A) | TC14 | TC14 | TC14 | TC13, (TC12, TC13)* | +| (Category B) | TC14 | TC14 | TC14 | TC13, (TC12, TC13)* | +| Additional requirement for BC2 (Category B) | N/A | TC14 | N/A | TC13, (TC12, TC13)* | + +| Capability Set | UTRA + E-UTRA + NB-IoT standalone (CS 14) | | | GSM + UTRA + E-UTRA + NB-IoT standalone (CS 15) | +|----------------------------------------------------------|--------------------------------------------------|-----------------------------------------------|-----------------------------------------------|--------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | +| Protection of the BS receiver of own or different BS | TC14 | TC14 | TC14 | TC13, (TC12, TC13)* | +| Additional spurious emissions requirements | TC14 | TC14 | TC14 | TC13, (TC12, TC13)* | +| Co-location with other Base Stations | TC14 | TC14 | TC14 | TC13, (TC12, TC13)* | +| 6.6.2 Operating band unwanted emissions | - | - | - | - | +| General requirement for Band Categories 1 and 3 | (TS 36.141)
(TS 25.141)
TC14 | N/A | (TS 36.141)
(TS 25.141)
TC14 | N/A | +| General requirement for Band Category 2 | N/A | (TS 36.141)
(TS 25.141)
TC14 | N/A | (TS 36.141)
(TS 25.141)*
TC14, TC12* | +| GSM/EDGE single-RAT requirement | N/A | N/A | N/A | N/A | +| Additional requirements | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | +| 6.6.3 Occupied bandwidth | - | - | - | - | +| Minimum requirement | (TS 25.141)
(TS 36.141) | (TS 25.141)
(TS 36.141) | (TS 25.141)
(TS 36.141) | (TS 25.141)*
(TS 36.141) | +| 6.6.4 Adjacent Channel Leakage Power Ratio (ACLR) | - | - | - | - | +| E- UTRA | TC14 | TC14 | TC14 | TC13 | +| UTRA FDD | (TS 25.141) | (TS 25.141) | (TS 25.141) | (TS 25.141)* | +| UTRA TDD | N/A | N/A | N/A | N/A | +| NB-IoT | TC14 | TC14 | TC14 | TC13 | +| Cumulative ACLR | N/A | N/A | N/A | N/A | +| 6.7 Transmitter intermodulation | - | - | - | - | +| General requirement | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | +| Additional requirement (BC1 and BC2) | Same TC as used in 6.6 | Same TC as used in 6.6 | N/A | Same TC as used in 6.6 | +| Additional requirement (BC3) | N/A | N/A | Same TC as used in 6.6 | N/A | +| 7.2 Reference sensitivity level | - | - | - | - | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD | (TS 25.141) | (TS 25.141) | (TS 25.141) | (TS 25.141)* | +| UTRA TDD | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | TC13 | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 7.3 Dynamic range | - | - | - | - | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD | (TS 25.141) | (TS 25.141) | (TS 25.141) | (TS 25.141)* | +| UTRA TDD | N/A | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | TC13 | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 7.4 In- band selectivity and blocking | - | - | - | - | +| General blocking requirement | TC14 | TC14 | TC14 | TC13 | +| General narrowband blocking requirement | TC14 | TC14 | TC14 | TC13 | +| Additional narrowband | N/A | N/A | N/A | TC13 | + +| Capability Set | UTRA + E-UTRA +
NB-IoT standalone (CS 14) | | | GSM + UTRA + E-
UTRA + NB-IoT
standalone
(CS 15) | +|----------------------------------------------------------------|------------------------------------------------------|-------------|-------------|---------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC2 | +| blocking requirement for GSM/EDGE | | | | | +| GSM/EDGE requirements for AM suppression | N/A | N/A | N/A | TC13 | +| Additional BC3 blocking requirement | N/A | N/A | TC14 | N/A | +| 7.5 Out-of-band blocking | - | - | - | - | +| General requirement | TC14 | TC14 | TC14 | TC13 | +| Co-location requirement | TC14 | TC14 | TC14 | TC13 | +| 7.6 Receiver spurious emissions | - | - | - | - | +| General requirement | TC14 | TC14 | TC14 | TC13 | +| Additional requirement for BC2 (Category B) | TC14 | TC14 | TC14 | TC13 | +| 7.7 Receiver intermodulation | - | - | - | - | +| General intermodulation requirement | TC14 | TC14 | TC14 | TC13 | +| General narrowband intermodulation requirement | TC14 | TC14 | TC14 | TC13 | +| Additional narrowband intermodulation requirement for GSM/EDGE | N/A | N/A | N/A | TC13 | +| 7.8 In-channel selectivity | - | - | - | - | +| E-UTRA requirement | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT | N/A | N/A | N/A | N/A | + +**Table 5.1-1c: Test configurations for capability sets (CS16-19) for Multi-RAT capable BS** + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|---------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| +| BS test case | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | BC2 | BC1 and BC2 | +| 6.2 Base Station output power | - | - | - | - | | | +| Base Station maximum output power | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG:TC22 | C: TC22
NI: TC22
NG:TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| E-UTRA for DL RS power | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT for DL RS power | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD primary CPICH power | N/A | N/A | N/A | N/A | N/A | (TS 25.141) | +| UTRA FDD secondary CPICH power | N/A | N/A | N/A | N/A | N/A | (TS 25.141) | +| 6.3 Output power dynamics | - | - | - | - | - | - | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NR | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | +| UTRA FDD | N/A | N/A | N/A | N/A | N/A | (TS 25.141) | +| GSM/EDGE | N/A | N/A | N/A | N/A | TC4b | N/A | +| 6.4 Transmit ON/OFF power | - | - | - | - | - | - | +| Transmitter OFF power | N/A | C: TC21
CNC: NTC21 | N/A | C: TC22 | N/A | N/A | +| Transmitter transient period | N/A | C: TC21
CNC: NTC21 | N/A | C: TC22 | N/A | N/A | +| 6.5 Transmitted signal quality | - | - | - | - | - | - | +| 6.5.1 Modulation quality | - | - | - | - | - | - | +| E-UTRA | C: TC21
NI, NG: (Note 4)
CNC: TC21
NCNI, NCNG: (Note 4)
C/NC: NTC21, TC21 | C: TC21
NI, NG: (Note 4)
CNC: TC21
NCNI, NCNG: (Note 4)
C/NC: NTC21, TC21
C/NCNI, C/NCNG: | C: TC22
NI, NG: (Note 4) | C: TC22
NI, NG: (Note 4) | C: TC21a
NI, NG: (Note 4)
CNC: TC21a
NCNI, NCNG: (Note 4)
C/NC: NTC21a, TC21a
C/NCNI, | C: TC21b
NI, NG: (Note 4)
CNC: TC21b
NCNI, NCNG: (Note 4)
C/NC: NTC21b, TC21b
C/NCNI, | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|----------------|---------------------------------------------------------------------------------|----------|-----------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| BS test case | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | BC2 | BC1 and BC2 | +| | C/NCNI,
C/NCNG:
(Note 4) | (Note 4) | | | C/NCNG:
(Note 4) | C/NCNG:
(Note 4) | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|---------------------------------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| BS test case | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | BC2 | BC1 and BC2 | +| NB-IoT | N/A (Note 4) | N/A (Note 4) | Standalone:
C: TC22
NI, NG: (Note 4) | Standalone
C: TC22
NI, NG: (Note 4) | N/A (Note 4) | N/A (Note 4) | +| NR | C: TC21
CNC: TC21
C/NC:
NTC21,
TC21 | C: TC21
CNC: TC21
C/NC:
NTC21, TC21 | C: TC22 | C: TC22 | C: TC21a
CNC: TC21a
C/NC:
NTC21a,
TC21a | C: TC21b
CNC: TC21b
C/NC:
NTC21b,
TC21b | +| UTRA FDD | N/A | N/A | N/A | N/A | N/A | C: TC21b
CNC: TC21b
C/NC:
NTC21b,
TC21b | +| GSM/EDGE | N/A | N/A | N/A | N/A | C: TC21a
CNC: TC21a
C/NC:
NTC21a,
TC21a | N/A | +| 6.5.2 Frequency error | - | - | - | - | - | - | +| E-UTRA | Same TC as 6.5.1 | Same TC as 6.5.1 | Same TC as 6.5.1 | Same TC as 6.5.1 | Same TC as 6.5.1 | Same TC as 6.5.1 | +| NB-IoT | N/A (Note 4) | N/A (Note 4) | Same TC as 6.5.1 | Same TC as 6.5.1 | N/A (Note 4) | N/A (Note 4) | +| NR | Same TC as 6.5.1 | Same TC as 6.5.1 | Same TC as 6.5.1 | Same TC as 6.5.1 | Same TC as 6.5.1 | Same TC as 6.5.1 | +| UTRA FDD | N/A | N/A | N/A | N/A | N/A | Same TC as 6.5.1 | +| GSM/EDGE | N/A | N/A | N/A | N/A | Same TC as 6.5.1 | N/A | +| 6.5.3 Time alignment error | - | - | - | - | - | - | +| E-UTRA | (TS 36.141)
NI, NG: (Note 4)
NCNI,
NCNG: (Note 4)
C/NCNI,
C/NCNG: (Note 4) | (TS 36.141)
NI, NG: (Note 4)
NCNI, NCNG: (Note 4)
C/NCNI,
C/NCNG: (Note 4) | (TS 36.141)
NI, NG: (Note 4) | (TS 36.141)
NI, NG: (Note 4) | (TS 36.141)
NI, NG: (Note 4)
NCNI, NCNG: (Note 4)
C/NCNI,
C/NCNG: (Note 4) | (TS 36.141)
NI, NG: (Note 4)
NCNI, NCNG: (Note 4)
C/NCNI,
C/NCNG: (Note 4) | +| NB-IoT | N/A (Note 4) | N/A (Note 4) | Standalone:
(TS 36.141)
NI, NG: (Note 4) | Standalone:
(TS 36.141)
NI, NG: (Note 4) | N/A (Note 4) | N/A (Note 4) | +| NR | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | +| UTRA FDD | N/A | N/A | N/A | N/A | N/A | (TS 25.141) | +| 6.6 Unwanted emissions | - | - | - | - | - | - | +| 6.6.1 Transmitter spurious emissions | - | - | - | - | - | - | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| BS test case | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | BC2 | BC1 and BC2 | +| (Category A) | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| (Category B) | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| Additional requirement for BC2 (Category B) | N/A | N/A | N/A | N/A | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | N/A | +| Protection of the BS receiver of own or different BS | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| Additional spurious emissions requirements | C, NI, NG: TC21

CNC, NCNI, NCNG: | C, NI, NG: TC21

CNC, NCNI, NCNG: | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: | C, NI, NG: TC21b

CNC, NCNI, NCNG: | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR +
E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR +
E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|----------------|---------------------------------------------------------------------------------|---------------------------------------------------------|-----------------------------------------------------------------------------------------------------|-----|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| BS test case | BC1 and
BC2 | BC3 | BC1 and
BC2 | BC3 | BC2 | BC1 and
BC2 | +| | NTC21

C/NC,
C/NCNI,
C/NCNG:
NTC21,
TC21 | NTC21

C/NC,
C/NCNI,
C/NCNG:
NTC21, TC21 | | | NTC21a

C/NC,
C/NCNI,
C/NCNG:
NTC21a,
TC21a | NTC21b

C/NC,
C/NCNI,
C/NCNG:
NTC21b,
TC21b | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------| +| BS test case | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | BC2 | BC1 and BC2 | +| Co-location with other Base Stations | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| 6.6.2 Operating band unwanted emissions | - | - | - | - | - | - | +| General requirement for Band Categories 1 and 3 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21

SC: (Note 3) | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21

SC: (Note 3) | C: TC22
NI: TC22
NG: TC22
SC: (Note 3) | C: TC22
NI: TC22
NG: TC22
SC: (Note 3) | N/A | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b

SC: (Note 3) | +| General requirement for Band Category 2 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21

SC: (Note 3) | N/A | C: TC22
NI: TC22
NG: TC22
SC: (Note 3) | N/A | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a

SC: (Note 3) | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b

SC: (Note 3) | +| Additional requirements | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | +| 6.6.3 Occupied bandwidth | - | - | - | - | - | - | +| Minimum requirement | (TS 36.141)
(TS 38.141-1) | (TS 36.141)
(TS 38.141-1) | (TS 36.141)
(TS 38.141-1) | (TS 36.141)
(TS 38.141-1) | (TS 36.141)
(TS 38.141-1) | (TS 25.141)
(TS 36.141)
(TS 38.141-1) | +| 6.6.4 Adjacent Channel Leakage power Ratio (ACLR) | - | - | - | - | - | - | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|----------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| BS test case | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | BC2 | BC1 and BC2 | +| E-UTRA | C: TC21
CNC: NTC21
C/NC:
NTC21,
TC21 | C: TC21
CNC: NTC21
C/NC:
NTC21, TC21 | C: TC21 | C: TC21 | C: TC21
CNC: NTC21
C/NC:
NTC21, TC21 | C: TC21b
CNC:
NTC21b
C/NC:
NTC21b,
TC21b | +| NB-IoT | NI: TC21
NG: TC21
NCNI:
NTC21
NCNG:
NTC21
C/NCNI,
C/NCNG:
NTC21,
TC21 | NI: TC21
NG: TC21
NCNI: NTC21
NCNG:
NTC21
C/NCNI,
C/NCNG:
NTC21, TC21 | TC22 | TC22 | NI: TC21
NG: TC21
NCNI: NTC21
NCNG:
NTC21
C/NCNI,
C/NCNG:
NTC21, TC21 | NI: TC21b
NG: TC21b
NCNI:
NTC21b
NCNG:
NTC21b
C/NCNI,
C/NCNG:
NTC21b,
TC21b | +| NR | C: TC21
CNC: NTC21
C/NC:
NTC21,
TC21 | C: TC21
CNC: NTC21
C/NC:
NTC21, TC21 | C: TC21 | C: TC21 | C: TC21
CNC: NTC21
C/NC:
NTC21, TC21 | C: TC21b
CNC:
NTC21b
C/NC:
NTC21b,
TC21b | +| UTRA FDD | N/A | N/A | N/A | N/A | N/A | C: TC21b
CNC:
NTC21b
C/NC:
NTC21b,
TC21b | +| Cumulative ACLR | CNC: NTC21
C/NC:
NTC21 | CNC: NTC21
C/NC: NTC21 | N/A | N/A | CNC: NTC21
C/NC: NTC21 | CNC:
NTC21b
C/NC:
NTC21b | +| 6.7 Transmitter intermodulation | - | - | - | - | | | +| General requirement | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | +| Additional requirement (BC1 and BC2) | CNC: NTC21
C/NC:
NTC21 | N/A | Same TC as used in 6.6 | | CNC:
NTC21a
C/NC:
NTC21a | CNC:
NTC21b
C/NC:
NTC21b | +| Additional requirement (BC3) | | N/A | | N/A | | | +| 7.2 Reference sensitivity level | - | - | - | - | - | - | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NR | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | +| UTRA FDD | N/A | N/A | N/A | N/A | N/A | (TS 25.141) | +| GSM/EDGE | N/A | N/A | N/A | N/A | TC5b | N/A | +| 7.3 Dynamic range | | | | | | | +| E-UTRA | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|---------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| BS test case | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | BC2 | BC1 and BC2 | +| NR | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | +| UTRA FDD | N/A | N/A | N/A | N/A | N/A | (TS 25.141) | +| GSM/EDGE | N/A | N/A | N/A | N/A | TC5b | N/A | +| 7.4 In-band selectivity and blocking | - | - | - | - | | | +| General blocking requirement | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| General narrowband blocking requirement | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| Additional narrowband blocking requirement for GSM/EDGE | N/A | N/A | N/A | N/A | TC5b | N/A | +| GSM/EDGE requirements for AM suppression | N/A | N/A | N/A | N/A | TC5b | N/A | +| Additional BC3 blocking requirement | N/A | N/A | N/A | N/A | N/A | N/A | +| 7.5 Out-of-band blocking | - | - | - | - | | | +| General requirement | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|----------------|---------------------------------------------------------------------------------|-----|-----------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| BS test case | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | BC2 | BC1 and BC2 | +| | TC21 | | | | TC21a | TC21b | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 18) | UTRA + NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 19) | +|---------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| BS test case | BC1 and BC2 | BC3 | BC1 and BC2 | BC3 | BC2 | BC1 and BC2 | +| Co-location requirement | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| 7.6 Receiver spurious emissions | - | - | - | - | - | - | +| General requirement | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | +| Additional requirement for BC2 (Category B) | N/A | N/A | C: TC22
NI: TC22
NG: TC22 | N/A | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | N/A | +| 7.7 Receiver intermodulation | - | - | - | - | - | - | +| General intermodulation requirement | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21

CNC, NCNI, NCNG: NTC21

C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG: TC21a

CNC, NCNI, NCNG: NTC21a

C/NC, C/NCNI, C/NCNG: NTC21a, TC21a | C, NI, NG: TC21b

CNC, NCNI, NCNG: NTC21b

C/NC, C/NCNI, C/NCNG: NTC21b, TC21b | + +| Capability Set | NR + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 16) | | NR + NB-IoT standalone + E-UTRA
NB-IoT in-band (Note 1)
NB-IoT guard band (Note 2)
(CS 17) | | GSM + NR +
E-UTRA
NB-IoT in-
band (Note
1)
NB-IoT
guard band
(Note 2)
(CS 18) | UTRA + NR +
E-UTRA
NB-IoT in-
band (Note
1)
NB-IoT
guard band
(Note 2)
(CS 19) | +|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| BS test case | BC1 and
BC2 | BC3 | BC1 and
BC2 | BC3 | BC2 | BC1 and
BC2 | +| General
narrowband
intermodulation
requirement | C, NI, NG:
TC21

CNC, NCNI,
NCNG:
NTC21

C/NC,
C/NCNI,
C/NCNG:
NTC21,
TC21 | C, NI, NG:
TC21

CNC, NCNI,
NCNG:
NTC21

C/NC,
C/NCNI,
C/NCNG:
NTC21, TC21 | C: TC22
NI: TC22
NG: TC22 | C: TC22
NI: TC22
NG: TC22 | C, NI, NG:
TC21a

CNC, NCNI,
NCNG:
NTC21a

C/NC,
C/NCNI,
C/NCNG:
NTC21a,
TC21a | C, NI, NG:
TC21b

CNC, NCNI,
NCNG:
NTC21b

C/NC,
C/NCNI,
C/NCNG:
NTC21b,
TC21b | +| Additional
narrowband
intermodulation
requirement for
GSM/EDGE | N/A | N/A | N/A | N/A | TC5b | N/A | +| 7.8 In-channel
selectivity | - | - | - | - | - | - | +| E-UTRA
requirement | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NR | (TS 38.141-
1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | (TS 38.141-1) | + +NOTE 1: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing. + +NOTE 2: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing. + +NOTE 3: For Operating band unwanted emissions, NR shall also be tested with SC with widest supported channel bandwidth and highest supported sub-carrier spacing. + +NOTE 4: There is no specific test with NB-IoT for those requirements, tests could be performed using E-UTRA signal only, without NB-IoT. + +## 5.2 Single-RAT Multi-carrier capable Base Stations + +This clause includes E-UTRA MC BS with one E-UTRA carrier supporting NB-IoT in-band and/or guard band. + +**Table 5.2-1: Test configurations for capability sets for Single-RAT capable BS** + +| Capability Set | UTRA (MC) capable BS (CS1) | | | E-UTRA (MC) capable BS
NB-IoT in-band*,
NB-IoT guard band** (CS2) | | | | +|----------------------------------------------------|----------------------------|-------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------| +| | BS test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| 6.2 Base Station output power | | - | - | - | - | - | - | +| Base Station maximum output power | | C: TC1a
CNC: TC1a
C/NC: TC1a, NTC1a | C: TC1a
CNC: TC1a
C/NC: TC1a, NTC1a | C: TC1b | C: TC2
CNC: TC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | C: TC2
CNC: TC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | C: TC2
CNC: TC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | +| Additional regional requirement (only for band 34) | | N/A | N/A | N/A | N/A | N/A | Compliance stated by manufacturer declaration | +| E-UTRA DL RS power | | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT for DL RS power | | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD primary CPICH power | | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | N/A | +| UTRA FDD secondary CPICH power | | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | N/A | +| UTRA TDD primary CCPCH power | | N/A | N/A | (TS 25.142) | N/A | N/A | N/A | +| 6.3 Output power dynamics | | - | - | - | - | - | - | +| E-UTRA | | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD | | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | N/A | +| UTRA TDD | | N/A | N/A | (TS 25.142) | N/A | N/A | N/A | +| GSM/EDGE | | N/A | N/A | N/A | N/A | N/A | N/A | +| NB-IoT | | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 6.4 Transmit ON/OFF power | | - | - | - | - | - | - | +| Transmitter OFF power | | N/A | N/A | C: TC1b | N/A | N/A | C: TC2
CNC: TC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | +| Transmitter transient period | | N/A | N/A | C: TC1b | N/A | N/A | C: TC2
CNC: TC2
C/NC: | + +| Capability Set | UTRA (MC) capable BS (CS1) | | | E-UTRA (MC) capable BS
NB-IoT in-band*,
NB-IoT guard band** (CS2) | | | +|----------------|----------------------------|-----|-----|-------------------------------------------------------------------------|-----|--------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| | | | | | | TC2,
NTC2
NI: TC17
NG: TC20 | + +| Capability Set | UTRA (MC) capable BS (CS1) | | | E-UTRA (MC) capable BS
NB-IoT in-band*,
NB-IoT guard band** (CS2) | | | +|---------------------------------------------|----------------------------------------------|----------------------------------------------|--------------------------|-------------------------------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| 6.5 Transmitted signal quality | - | - | - | - | - | - | +| 6.5.1 Modulation quality | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | C: TC2
CNC: TC2
C/NC: TC2,
NTC2
NI/NG: (Note 1) | C: TC2
CNC: TC2
C/NC: TC2,
NTC2
NI/NG: (Note 1) | C: TC2
CNC: TC2
C/NC: TC2,
NTC2
NI/NG: (Note 1) | +| UTRA FDD | C: TC1a
CNC: TC1a
C/NC: TC1a,
NTC1a | C: TC1a
CNC: TC1a
C/NC: TC1a,
NTC1a | N/A | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | C: TC1b | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | N/A | N/A | N/A | +| NB-IoT | N/A | N/A | N/A | N/A: (Note 1) | N/A: (Note 1) | N/A: (Note 1) | +| 6.5.2 Frequency error | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | Same TC as used in 6.5.1
NI/NG: (Note 1) | Same TC as used in 6.5.1
NI/NG: (Note 1) | Same TC as used in 6.5.1
NI/NG: (Note 1) | +| UTRA FDD | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | N/A | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | Same TC as used in 6.5.1 | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | N/A | N/A | N/A | +| NB-IoT | N/A | N/A | N/A | N/A: (Note 1) | N/A: (Note 1) | N/A: (Note 1) | +| 6.5.3 Time alignment error | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | (TS 36.141)
NI/NG: (Note 1) | (TS 36.141)
NI/NG: (Note 1) | (TS 36.141)
NI/NG: (Note 1) | +| UTRA FDD | (TS 25.141) | (TS 25.141) | N/A | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | (TS 25.142) | N/A | N/A | N/A | +| NB-IoT | N/A | N/A | N/A | N/A: (Note 1) | N/A: (Note 1) | N/A: (Note 1) | +| 6.6 Unwanted emissions | - | - | - | - | - | - | +| 6.6.1 Transmitter spurious emissions | - | - | - | - | - | - | + +| Capability Set | UTRA (MC) capable BS (CS1) | | | E-UTRA (MC) capable BS
NB-IoT in-band*,
NB-IoT guard band** (CS2) | | | +|------------------------------------------------------|------------------------------------------------------------------------------|-----------------------------------------------------|-------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| (Category A) | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| (Category B) | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| Additional requirement for BC2 (Category B) | N/A | N/A | N/A | N/A | N/A | N/A | +| Protection of the BS receiver of own or different BS | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| Additional spurious emissions requirements | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| Co-location with other Base Stations | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| 6.6.2 Operating band unwanted emissions | - | - | - | - | - | - | +| General requirement for Band Categories 1 and 3 | (TS 25.14 1)
C: TC1a
CNC:
TC1a,
NTC1a
C/NC:
TC1a,
NTC1a | N/A | (TS 25.14 2) C:
TC1b | (TS 36.14 1)
C: TC2
CNC:
TC2,
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | N/A | (TS 36.14 1)
C: TC2
CNC:
TC2,
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| General requirement | N/A | (TS 25.14 1) | N/A | N/A | (TS 36.14 1) | N/A | + +| Capability Set | UTRA (MC) capable BS (CS1) | | | E-UTRA (MC) capable BS
NB-IoT in-band*,
NB-IoT guard band** (CS2) | | | +|----------------------------------------------------------|-----------------------------------------------|--------------------------------------------------------|-----------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------------------------------|----------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| for Band Category 2 | | C: TC1a
CNC: TC1a,
NTC1a
C/NC: TC1a,
NTC1a | | | C: TC2
CNC: TC2,
NTC2
C/NC: TC2,
NTC2
NI: TC17
NG: TC20 | | +| GSM/EDGE single-RAT requirements | N/A | N/A | N/A | N/A | N/A | N/A | +| Additional requirements | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | +| 6.6.3 Occupied bandwidth | - | - | - | - | - | - | +| Minimum requirement | (TS 25.14 1) | (TS 25.14 1) | (TS 25.14 2) | (TS 36.14 1) | (TS 36.14 1) | (TS 36.14 1) | +| 6.6.4 Adjacent Channel Leakage Power Ratio (ACLR) | | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | C: TC2
CNC: NTC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | C: TC2
CNC: NTC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | C: TC2
CNC: NTC2
C/NC: TC2, NTC2
NI: TC17
NG: TC20 | +| UTRA FDD | (TS 25.14 1) | (TS 25.14 1) | N/A | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | (TS 25.14 2) | N/A | N/A | N/A | +| NB-IoT | N/A | N/A | N/A | NI: TC17
NG: TC20 | NI: TC17
NG: TC20 | NI: TC17
NG: TC20 | +| Cumulative ACLR | CNC: NTC1a
C/NC: NTC1a | CNC: NTC1a
C/NC: NTC1a | - | CNC: NTC2
C/NC: NTC2 | CNC: NTC2
C/NC: NTC2 | CNC: NTC2
C/NC: NTC2 | +| 6.7 Transmitter intermodulation | - | - | - | - | - | - | +| General requirement | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | +| Additional requirement (BC1 and BC2) | CNC: NTC1a
C/NC: NTC1a | Same TC as used in 6.6 | N/A | CNC: NTC2
C/NC: NTC2
NI: TC17
NG: TC20 | Same TC as used in 6.6 | N/A | +| Additional requirement | N/A | N/A | Same TC as used in | N/A | N/A | Same TC as used in | + +| Capability Set | UTRA (MC) capable BS (CS1) | | | E-UTRA (MC) capable BS
NB-IoT in-band*,
NB-IoT guard band** (CS2) | | | +|---------------------------------------------------------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| (BC3) | | | 6.6 | | | 6.6 | +| 7.2 Reference sensitivity level | - | - | - | - | - | - | +| E-UTRA requirement | N/A | N/A | N/A | (TS 36.14 1) | (TS 36.14 1) | (TS 36.14 1) | +| UTRA FDD requirement | (TS 25.14 1) | (TS 25.14 1) | N/A | N/A | N/A | N/A | +| UTRA TDD requirement | N/A | N/A | (TS 25.14 2) | N/A | N/A | N/A | +| GSM/EDGE requirement | N/A | N/A | N/A | N/A | N/A | N/A | +| NB-IoT requirement | N/A | N/A | N/A | (TS 36.14 1) | (TS 36.14 1) | (TS 36.14 1) | +| 7.3 Dynamic range | - | - | - | - | - | - | +| E-UTRA | N/A | N/A | N/A | (TS 36.14 1) | (TS 36.14 1) | (TS 36.14 1) | +| UTRA FDD | (TS 25.14 1) | (TS 25.14 1) | N/A | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | (TS 25.14 2) | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | N/A | N/A | N/A | +| NB-IoT | N/A | N/A | N/A | (TS 36.14 1) | (TS 36.14 1) | (TS 36.14 1) | +| 7.4 In-band selectivity and blocking | - | - | - | - | - | - | +| General blocking requirement | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| General narrowband blocking requirement | C: TC1a,
TC6a
CNC:
NTC1a,
TC6a
C/NC:
TC1a,
NTC1a,
TC6a | C: TC1a,
TC6a
CNC:
NTC1a,
TC6a
C/NC:
TC1a,
NTC1a,
TC6a | C: TC1b
TC6c | C: TC2,
TC6b
CNC:
NTC2,
TC6b
C/NC:
TC2,
NTC2,
TC6b
NI: TC17
NG: TC20 | C: TC2,
TC6b
CNC:
NTC2,
TC6b
C/NC:
TC2,
NTC2,
TC6b
NI: TC17
NG: TC20 | C: TC2,
TC6b
CNC:
NTC2,
TC6b
C/NC:
TC2,
NTC2,
TC6b
NI: TC17
NG: TC20 | +| Additional narrowband blocking requirement for GSM/EDGE | N/A | N/A | N/A | N/A | N/A | N/A | +| GSM/EDGE requirements for AM suppression | N/A | N/A | N/A | N/A | N/A | N/A | + +| Capability Set | UTRA (MC) capable BS (CS1) | | | E-UTRA (MC) capable BS
NB-IoT in-band*,
NB-IoT guard band** (CS2) | | | +|------------------------------------------------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------|------------------|----------------------------------------------------------------------------|----------------------------------------------------------------------------|----------------------------------------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| Additional BC3 blocking minimum requirement | N/A | N/A | C: TC1b | N/A | N/A | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| 7.5 Out-of-band blocking | - | - | - | - | - | - | +| General requirement | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| Co-location requirement | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| 7.6 Receiver spurious emissions | - | - | - | - | - | - | +| General requirement | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| Additional requirement for BC2 (Category B) | N/A | N/A | N/A | N/A | N/A | N/A | +| 7.7 Receiver intermodulation | - | - | - | - | - | - | +| General intermodulation requirement | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1a
CNC:
NTC1a
C/NC:
TC1a,
NTC1a | C: TC1b | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | C: TC2
CNC:
NTC2
C/NC:
TC2,
NTC2
NI: TC17
NG: TC20 | +| General narrowband intermodulation requirement | C: TC1a,
TC6a
CNC:
NTC1a,
TC6a
C/NC:
TC1a,
NTC1a,
TC6a | C: TC1a,
TC6a
CNC:
NTC1a,
TC6a
C/NC:
TC1a,
NTC1a,
TC6a | C: TC1b,
TC6c | C: TC2,
TC6b
CNC:
NTC2,
TC6b
C/NC:
TC2,
NTC2,
TC6b | C: TC2,
TC6b
CNC:
NTC2,
TC6b
C/NC:
TC2,
NTC2,
TC6b | C: TC2,
TC6b
CNC:
NTC2,
TC6b
C/NC:
TC2,
NTC2,
TC6b | + +| Capability Set | UTRA (MC) capable BS (CS1) | | | E-UTRA (MC) capable BS
NB-IoT in-band*,
NB-IoT guard band** (CS2) | | | +|----------------------------------------------------------------|----------------------------|-----|-----|-------------------------------------------------------------------------|----------------------|----------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| BS test case | | | | NI: TC17
NG: TC20 | NI: TC17
NG: TC20 | NI: TC17
NG: TC20 | +| Additional narrowband intermodulation requirement for GSM/EDGE | N/A | N/A | N/A | N/A | N/A | N/A | +| 7.8 In-channel selectivity | - | - | - | - | - | - | +| E-UTRA requirement | N/A | N/A | N/A | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| NB-IoT requirement | N/A | N/A | N/A | (NI: TS 36.141) | (NI: TS 36.141) | (NI: TS 36.141) | + +**Table 5.2-1a: Test configurations for capability sets for Single-RAT capable BS** + +| Capability Set | NB-IoT (MC) capable (CS 8) | | | +|----------------------------------------------------|-----------------------------------|--------------------------|--------------------------| +| BS test case | BC1 | BC2 | BC3 | +| 6.2 Base Station output power | - | - | - | +| Base Station maximum output power | TC8 | TC8 | TC8 | +| Additional regional requirement (only for band 34) | N/A | N/A | N/A | +| E-UTRA DL RS power | N/A | N/A | N/A | +| NB-IoT for DL RS power | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| UTRA FDD primary CPICH power | N/A | N/A | N/A | +| UTRA FDD secondary CPICH power | N/A | N/A | N/A | +| UTRA TDD primary CCPCH power | N/A | N/A | N/A | +| 6.3 Output power dynamics | - | - | - | +| E-UTRA | N/A | N/A | N/A | +| UTRA FDD | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 6.4 Transmit ON/OFF power | - | - | - | +| Transmitter OFF power | N/A | N/A | TC8 | +| Transmitter transient period | N/A | N/A | TC8 | +| 6.5 Transmitted signal quality | - | - | - | +| 6.5.1 Modulation quality | - | - | - | +| E-UTRA | N/A | N/A | N/A | +| UTRA FDD | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | +| NB-IoT | TC8 | TC8 | TC8 | +| 6.5.2 Frequency error | - | - | - | +| E-UTRA | N/A | N/A | N/A | +| UTRA FDD | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | +| NB-IoT | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | Same TC as used in 6.5.1 | +| 6.5.3 Time alignment error | - | - | - | + +| Capability Set | NB-IoT (MC) capable (CS 8) | | | +|----------------------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------| +| BS test case | BC1 | BC2 | BC3 | +| E-UTRA | N/A | N/A | N/A | +| UTRA FDD | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | N/A | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 6.6 Unwanted emissions | - | - | - | +| 6.6.1 Transmitter spurious emissions | - | - | - | +| (Category A) | TC8 | TC8 | TC8 | +| (Category B) | TC8 | TC8 | TC8 | +| Additional requirement for BC2 (Category B) | N/A | N/A | N/A | +| Protection of the BS receiver of own or different BS | TC8 | TC8 | TC8 | +| Additional spurious emissions requirements | TC8 | TC8 | TC8 | +| Co-location with other Base Stations | TC8 | TC8 | TC8 | +| 6.6.2 Operating band unwanted emissions | - | - | - | +| General requirement for Band Categories 1 and 3 | (TS 36.141) TC8 | N/A | (TS 36.141) TC8 | +| General requirement for Band Category 2 | N/A | (TS 36.141) TC8 | N/A | +| GSM/EDGE single-RAT requirements | N/A | N/A | N/A | +| Additional requirements | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | +| 6.6.3 Occupied bandwidth | - | - | - | +| Minimum requirement | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 6.6.4 Adjacent Channel Leakage Power Ratio (ACLR) | - | - | - | +| E-UTRA | N/A | N/A | N/A | +| UTRA FDD | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | N/A | +| NB-IoT | TC8 | TC8 | TC8 | +| Cumulative ACLR | N/A | N/A | N/A | + +| Capability Set | NB-IoT (MC) capable (CS 8) | | | +|---------------------------------------------------------|-----------------------------------|------------------------|------------------------| +| BS test case | BC1 | BC2 | BC3 | +| 6.7 Transmitter intermodulation | - | - | - | +| General requirement | Same TC as used in 6.6 | Same TC as used in 6.6 | Same TC as used in 6.6 | +| Additional requirement (BC1 and BC2) | Same TC as used in 6.6 | Same TC as used in 6.6 | N/A | +| Additional requirement (BC3) | N/A | N/A | Same TC as used in 6.6 | +| 7.2 Reference sensitivity level | - | - | - | +| E-UTRA requirement | N/A | N/A | N/A | +| UTRA FDD requirement | N/A | N/A | N/A | +| UTRA TDD requirement | N/A | N/A | N/A | +| GSM/EDGE requirement | N/A | N/A | N/A | +| NB-IoT requirement | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 7.3 Dynamic range | - | - | - | +| E-UTRA | N/A | N/A | N/A | +| UTRA FDD | N/A | N/A | N/A | +| UTRA TDD | N/A | N/A | N/A | +| GSM/EDGE | N/A | N/A | N/A | +| NB-IoT | (TS 36.141) | (TS 36.141) | (TS 36.141) | +| 7.4 In-band selectivity and blocking | - | - | - | +| General blocking requirement | TC8 | TC8 | TC8 | +| General narrowband blocking requirement | TC8 | TC8 | TC8 | +| Additional narrowband blocking requirement for GSM/EDGE | N/A | N/A | N/A | +| GSM/EDGE requirements for AM suppression | N/A | N/A | N/A | +| Additional BC3 blocking minimum requirement | N/A | N/A | TC8 | +| 7.5 Out-of-band blocking | - | - | - | +| General requirement | TC8 | TC8 | TC8 | +| Co-location requirement | TC8 | TC8 | TC8 | + +| Capability Set | NB-IoT (MC) capable (CS 8) | | | +|----------------------------------------------------------------|-----------------------------------|------------|------------| +| BS test case | BC1 | BC2 | BC3 | +| 7.6 Receiver spurious emissions | - | - | - | +| General requirement | TC8 | TC8 | TC8 | +| Additional requirement for BC2 (Category B) | N/A | N/A | N/A | +| 7.7 Receiver intermodulation | - | - | - | +| General intermodulation requirement | TC8 | TC8 | TC8 | +| General narrowband intermodulation requirement | TC8 | TC8 | TC8 | +| Additional narrowband intermodulation requirement for GSM/EDGE | N/A | N/A | N/A | +| 7.8 In-channel selectivity | - | - | - | +| E-UTRA requirement | N/A | N/A | N/A | +| NB-IoT requirement | N/A | N/A | N/A | + +## 5.3 Multi-band capable Base Stations + +**Table 5.3-1: Test configurations for Multi-Band capable BS (CS1-CS7, CS16 and CS18-CS19)** + +| BS test case | Test for Multi-Band capable BS | | Test configuration for MBT | | +|----------------------------------------------------------|--------------------------------|----------------------------------------|----------------------------|------| +| | Common antenna connector | Separate antenna connector | BC1/BC2 | BC3 | +| 6.2 Base Station output power | - | - | - | - | +| Base Station maximum output power | SBT, MBT | SBT, MBT | TC7a | TC7a | +| Additional regional requirement (only for band 34) | N/A | N/A | N/A | - | +| E-UTRA for DL RS power | SBT | SBT | - | - | +| UTRA FDD primary CPICH power | SBT | SBT | - | - | +| UTRA TDD primary CCPCH power | SBT | SBT | - | - | +| NB-IoT for DL RS power | SBT | SBT | - | - | +| 6.3 Output power dynamics | - | - | - | - | +| E-UTRA | SBT | SBT | - | - | +| UTRA FDD | SBT | SBT | - | - | +| UTRA TDD | SBT | SBT | - | - | +| GSM/EDGE | SBT | SBT | - | - | +| NB-IoT | SBT | SBT | - | - | +| NR | SBT | SBT | - | - | +| 6.4 Transmit ON/OFF power | | | - | - | +| Transmitter OFF power | MBT, SBT 7 | MBT, SBT 7 | N/A | TC7a | +| Transmitter transient period | MBT, SBT 7 | MBT, SBT 7 | N/A | TC7a | +| 6.5 Transmitted signal quality | | | | | +| 6.5.1 Modulation quality | | | | | +| E-UTRA | SBT, MBT | SBT, MBT | TC7a | TC7a | +| UTRA FDD | SBT, MBT | SBT, MBT | TC7a | N/A | +| UTRA TDD | SBT, MBT | SBT, MBT | N/A | TC7a | +| GSM/EDGE | SBT, MBT | SBT, MBT | TC7a | N/A | +| NB-IoT | N/A (Note 8) | N/A (Note 8) | - | - | +| NR | SBT, MBT | SBT, MBT | TC7a | TC7a | +| 6.5.2 Frequency error | | | | | +| E-UTRA | SBT, MBT | SBT, MBT | TC7a | TC7a | +| UTRA FDD | SBT, MBT | SBT, MBT | TC7a | N/A | +| UTRA TDD | SBT, MBT | SBT, MBT | N/A | TC7a | +| GSM/EDGE | SBT, MBT | SBT, MBT | TC7a | N/A | +| NB-IoT | N/A (Note 8) | N/A (Note 8) | - | - | +| NR | SBT, MBT | SBT, MBT | TC7a | TC7a | +| 6.5.3 Time alignment between transmitter branches | | | | | +| E-UTRA | SBT, MBT 1 | SBT, MBT 1 | TC7b | TC7b | +| UTRA FDD | SBT, MBT 1 | SBT, MBT 1 | TC7b | N/A | +| UTRA TDD | SBT | SBT | N/A | - | +| NB-IoT | N/A (Note 8) | N/A (Note 8) | - | - | +| NR | SBT, MBT 1 | SBT, MBT 1 | TC7b | TC7b | +| 6.6 Unwanted emissions | | | | | +| 6.6.1 Transmitter spurious emissions | | | | | +| (Category A) | SBT, MBT | SBT 2 , MBT 2 | TC7b | TC7b | +| (Category B) | SBT, MBT | SBT 2 , MBT 2 | TC7b | TC7b | +| Additional requirement for BC2 (Category B) | SBT, MBT 3 | SBT 2 , MBT 2, 3 | TC7b | N/A | +| Protection of the BS receiver of own or different BS | SBT, MBT | SBT 2 , MBT 2 | TC7b | TC7b | +| Additional spurious emissions requirements | SBT, MBT | SBT 2 , MBT 2 | TC7b | TC7b | +| Co-location with other Base Stations | SBT, MBT | SBT 2 , MBT 2 | TC7b | TC7b | +| 6.6.2 Operating band unwanted emissions | | | | | +| General requirement for Band Categories 1 and 3 | SBT, MBT | SBT 2 , MBT 2 | TC7b | TC7b | +| General requirement for Band | SBT, MBT | SBT 2 , MBT 2 | TC7b | N/A | + +| | | | | | +|-------------------------------------------------------------------------------|-----------------------|----------------------------------------|------|------| +| Category 2 | | | | | +| GSM/EDGE single-RAT requirement | SBT, MBT 6 | SBT 2 , MBT 2,6 | TC7c | N/A | +| Additional requirements | SBT, MBT | SBT 2 , MBT 2 | - | - | +| | | | | | +| 6.6.3 Occupied bandwidth | | | | | +| Minimum requirement | SBT | SBT | - | - | +| 6.6.4 Adjacent Channel Leakage Power Ratio (ACLR) | | | - | - | +| E- UTRA | SBT, MBT 4 | SBT 2 , MBT 2, 4 | TC7b | TC7b | +| UTRA FDD | SBT, MBT 4 | SBT 2 , MBT 2, 4 | TC7b | N/A | +| UTRA TDD | SBT, MBT 4 | SBT 2 , MBT 2, 4 | N/A | TC7b | +| Cumulative ACLR | SBT, MBT 4 | SBT 2 | TC7b | TC7b | +| NB-IoT | SBT, MBT 4 | SBT 2 , MBT 2, 4 | TC7b | TC7b | +| NR | SBT, MBT 4 | SBT 2 , MBT 2, 4 | TC7b | TC7b | +| 6.7 Transmitter intermodulation | | | | | +| General requirement | SBT | SBT 2 | - | - | +| Additional requirement (BC1 and BC2) | SBT | SBT 2 | - | N/A | +| Additional requirement (BC3) | SBT | SBT 2 | N/A | - | +| 7.2 Reference sensitivity level | | | | | +| E-UTRA | SBT | SBT | - | - | +| UTRA FDD | SBT | SBT | - | - | +| UTRA TDD | SBT | SBT | - | - | +| GSM/EDGE | SBT | SBT | - | - | +| NB-IoT | SBT | SBT | - | - | +| NR | SBT | SBT | - | - | +| 7.3 Dynamic range | | | | | +| E-UTRA | SBT | SBT | - | - | +| UTRA FDD | SBT | SBT | - | - | +| UTRA TDD | SBT | SBT | - | - | +| GSM/EDGE | SBT | SBT | - | - | +| NB-IoT | SBT | SBT | - | - | +| NR | SBT | SBT | - | - | +| 7.4 In- band selectivity and blocking | | | | | +| General blocking requirement | MBT, SBT 7 | SBT, MBT 5 | TC7b | TC7b | +| General narrowband blocking requirement | MBT, SBT 7 | SBT, MBT 5 | TC7b | TC7b | +| Additional narrowband blocking requirement for GSM/EDGE | SBT | SBT | - | - | +| GSM/EDGE requirements for AM suppression | SBT | SBT | - | - | +| Additional BC3 blocking requirement | MBT, SBT 7 | SBT, MBT 5 | N/A | TC7b | +| 7.5 Out-of-band blocking | | | | | +| General requirement | MBT, SBT 7 | SBT, MBT 5 | TC7b | TC7b | +| Co-location requirement | MBT, SBT 7 | SBT, MBT 5 | TC7b | TC7b | +| 7.6 Receiver spurious emissions | | | | | +| General requirement | SBT, MBT | SBT 2 MBT 2 | TC7b | TC7b | +| Additional requirement for BC2 (Category B) | SBT, MBT 3 | SBT 2 , MBT 2, 3 | TC7b | N/A | +| 7.7 Receiver intermodulation | | | | | +| General intermodulation requirement | MBT, SBT 7 | SBT, MBT 5 | TC7b | TC7b | +| General narrowband intermodulation requirement | MBT, SBT 7 | SBT, MBT 5 | TC7b | TC7b | +| Additional narrowband intermodulation requirement for GSM/EDGE | SBT | SBT | - | N/A | +| 7.8 In-channel selectivity | | | | | +| E-UTRA requirement | SBT | SBT | - | - | +| NB-IoT | SBT | SBT | - | - | +| NR | SBT | SBT | - | - | +| NOTE 1: MBT is only applicable when DB-DC-HSDPA / inter-band CA is supported. | | | | | + +- NOTE 2: Single-band requirement apply to each antenna connector for both multi-band operation test and single-band operation test. For single-band operation test, other antenna connector(s) is (are) terminated. + +NOTE 3: For multi-band operation, this additional requirement for BC2 is applicable only when all supported operating bands belong to BC2 and GSM/EDGE is configured in all operating bands. + +NOTE 4: For ACLR, MBT shall be applied for the Inter RF Bandwidth gap only. In case of a BS capable of CS4, CS5, CS6, CS7 or CS18, the referenced test configuration shall be the corresponding one for CS1, CS2, CS3 or CS16 respectively, i.e. without GSM/EDGE carriers. + +NOTE 5: MBT is only applied for multi-band receiver. + +NOTE 6: MBT is only applicable for multi-band BS supporting CS4, CS5 or CS6 in at least one band. + +NOTE 7: SBT is only applicable if different Capability Sets are declared for single-band and multi-band operation. + +NOTE 8: There is no specific test with NB-IoT for those requirements, tests could be performed using E-UTRA signal only, without NB-IoT. + +--- + +## 6 Transmitter characteristics + +### 6.1 General + +General test conditions for transmitter tests are given in clause 4, including interpretation of measurement results and configurations for testing. BS configurations for the tests are defined in clause 4.10. + +Unless otherwise stated, a BS declared to be capable of E-UTRA with NB-IoT in-band or guard band operations (or any combination with GSM and/or UTRA or NR) is only required to pass the transmitter tests for E-UTRA with NB-IoT in-band or guard band (or any combination with GSM and/or UTRA or NR); it is not required to perform the transmitter tests again for E-UTRA only (or any combination with GSM and/or UTRA or NR). + +Unless otherwise stated, a BS declared to be capable of E-UTRA with NB-IoT in-band and guard band operations (or any combination with GSM and/or UTRA or NR) needs only to pass the transmitter tests for E-UTRA with guard band operation (or any combination with GSM and/or UTRA or NR). + +Unless otherwise stated, a BS declared to be capable of NB-IoT operation in NR in-band (or any combination with GSM and/or UTRA or E-UTRA) is only required to pass the transmitter tests for NB-IoT operation in NR in-band (or any combination with GSM and/or UTRA or E-UTRA); it is not required to perform the transmitter tests again for NR only (or any combination with GSM and/or UTRA or E-UTRA). + +### 6.2 Base Station output power + +#### 6.2.1 Base Station maximum output power + +##### 6.2.1.1 Definition and applicability + +Output power of the Base Station is the mean power delivered to a load with resistance equal to the nominal load impedance of the transmitter. + +The maximum total output power, $P_{\max}$ , of the Base Station is the mean power level measured at the antenna connector during the transmitter ON period in a specified reference condition. + +The maximum RAT output power, $P_{\max,\text{RAT}}$ , of the Base Station is the mean power level measured at the antenna connector during the transmitter ON period for a specific RAT in a specified reference condition. + +The maximum carrier output power, $P_{\max,c}$ of the Base Station is the mean power level measured at the antenna connector during the transmitter ON period for a specific carrier in a specified reference condition. + +The rated carrier output power, $P_{\text{Rated},c}$ , of the base station is the mean power level for a specific carrier that the manufacturer has declared to be available at the antenna connector during the transmitter ON period. + +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 Annex B. + +The rated carrier output power of the BS shall be as specified in Table 6.2-1. + +**Table 6.2-1: Base Station rated carrier output power** + +| BS class | P Rated,c | +|-------------------------------------------------------------------------------------------------|----------------------| +| Wide Area BS | (note) | +| Medium Range BS | ≤+ 38 dBm | +| Local Area BS | ≤+ 24 dBm | +| NOTE: There is no upper limit for the rated carrier output power of the Wide Area Base Station. | | + +In addition, for Band 85 NB-IoT standalone operation, the BS rated output power limit of 43 dBm applies over the NB-IoT carriers in the range 728-729 MHz of the DL operating band. The BS output power limit of 43 dBm shall be considered as shared among all NB-IoT carriers in the 728-729 MHz frequency range or as the maximum value per NB-IoT carrier in the case where only one NB-IoT carrier is deployed in 728-729 MHz frequency range. + +### 6.2.1.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.2.1. + +#### 6.2.1.2A Additional requirement (regional) + +The additional requirement is in TS 37.104 [2] clause 6.2.2. + +### 6.2.1.3 Test purpose + +The test purpose is to verify the accuracy of the maximum carrier output power across the frequency range and under normal and extreme conditions for all transmitters in the BS. + +### 6.2.1.4 Method of test + +#### 6.2.1.4.1 Initial conditions + +Test environment: normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: BRFBW, MRFBW and TRFBW in single-band operation, see clause 4.9.1; BRFBW\_TRFBW and B'RFBW\_TRFBW in multi-band operation, see clause 4.9.1. + +In addition, a single test shall be performed under extreme power supply conditions as defined in Annex B.5. In this case, it is sufficient to test on a single combination of one ARFCN, UARFCN, E-ARFCN or NR-ARFCN, one Base Station RF Bandwidth position and with only one applicable test configuration defined in clause 5. + +NOTE: Tests under extreme power supply also test extreme temperature. + +Connect the power measuring equipment to the MSR Base Station antenna connector as shown in Annex D.1.1. + +#### 6.2.1.4.2 Procedure + +- 1) Set the Base Station to transmit at maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.9.2. +- 2) Measure the mean power for each carrier at the Base Station antenna connector. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 3) For multi-band capable BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS + +with separate antenna connector, the antenna connector not being under test in case of SBT or MBT shall be terminated. + +### 6.2.1.5 Test requirements + +In normal conditions, the measurement result in step 2 of clause 6.2.1.4.2 shall for UTRA, E-UTRA and NR remain: within +2.7 dB and –2.7 dB of the manufacturer's rated carrier output power for carrier frequency $f \leq 3.0$ GHz, within +3.0 dB and –3.0 dB of the manufacturer's rated output power for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz, and for GSM/EDGE and NB-IoT remain within +3.0 dB and –3.0 dB of the manufacturer's rated carrier output power. In extreme conditions, measurement result in step 2 of clause 6.2.1.4.2 shall for UTRA, E-UTRA and NR remain: within +3.2 dB and –3.2 dB of the manufacturer's rated carrier output power for carrier frequency $f \leq 3.0$ GHz, within +3.5 dB and –3.5 dB of the manufacturer's rated output power for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz, and for GSM/EDGE and NB-IoT remain within +3.5 dB and –3.5 dB of the manufacturer's rated carrier output power. + +## 6.2.2 E-UTRA DL RS power + +### 6.2.2.1 Definition and applicability + +E-UTRA DL RS power is the resource element power of Downlink Reference Symbol. + +The absolute DL RS power is indicated on the DL-SCH. The absolute accuracy is defined as the maximum deviation between the DL RS power indicated on the DL-SCH and the DL RS power at the BS antenna connector. + +### 6.2.2.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.2.3. + +### 6.2.2.3 Test purpose + +The test purpose is to verify that the E-UTRA DL RS power is within the limits specified by the minimum requirement. + +### 6.2.2.4 Method of test + +For this requirement Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5. The following shall apply: + +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 6.5.4.4. + +In addition, for a multi-band capable BS, the following step shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band where single carrier test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +### 6.2.2.5 Test requirements + +The test requirement for DL RS power is specified in TS 36.141 [9], clause 6.5.4.5. + +## 6.2.3 UTRA FDD primary CPICH power + +### 6.2.3.1 Definition and applicability + +UTRA FDD primary CPICH power is the code domain power of the Common Pilot Channel. Primary CPICH power is indicated on the BCH. CPICH power accuracy is defined as the maximum deviation between the Primary CPICH code domain power indicated on the BCH and the Primary CPICH code domain power measured at the TX antenna interface. + +### 6.2.3.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.2.4. + +### 6.2.3.3 Test purpose + +The test purpose is to verify that the UTRA FDD primary CPICH power is within the limits specified by the minimum requirement. + +### 6.2.3.4 Method of test + +For this requirement Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5. The following shall apply: + +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 6.2.2.4. + +In addition, for a multi-band capable BS, the following step shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +### 6.2.3.5 Test requirements + +For UTRA FDD the test requirement for CPICH power is specified in TS 25.141 [10], clause 6.2.2.5. + +## 6.2.3A UTRA FDD secondary CPICH power + +### 6.2.3A.1 Definition and applicability + +UTRA FDD secondary CPICH power is the code domain power of the Secondary Common Pilot Channel. Secondary CPICH power is equal to the sum of the Primary CPICH power and the power offset, which are signalled to the UE. Secondary CPICH power accuracy is defined as the maximum deviation of the relevant IE between the Primary CPICH power transmitted at the first antenna connector and the Secondary CPICH power transmitted at the second antenna connector. + +### 6.2.3A.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.2.4A. + +### 6.2.3A.3 Test purpose + +The test purpose is to verify that the UTRA FDD secondary CPICH power is within the limits specified by the minimum requirement. + +### 6.2.3A.4 Method of test + +For this requirement Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5. The following shall apply: + +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 6.2.3.4. + +In addition, for a multi-band capable BS, the following step shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +#### 6.2.3A.5 Test requirements + +For UTRA FDD the test requirement for CPICH power is specified in TS 25.141 [10], clause 6.2.3.5. + +### 6.2.4 UTRA TDD primary CCPCH power + +#### 6.2.4.1 Definition and applicability + +UTRA TDD primary CCPCH power is the code domain power of the Primary Common Control Physical Channel averaged over the transmit timeslot. Primary CCPCH power is signalled on the BCH. + +UTRA TDD differential accuracy of the Primary CCPCH power is the relative transmitted power accuracy of PCCPCH in consecutive frames when the nominal PCCPCH power is not changed. + +#### 6.2.4.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.2.5. + +#### 6.2.4.3 Test purpose + +The test purpose is to verify that the UTRA TDD primary CCPCH power and differential accuracy of Primary CCPCH power are within the limits specified by the minimum requirement. + +#### 6.2.4.4 Method of test + +For this requirement Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5. The following shall apply: + +- For references to TS 25.142, the methods of test are specified in TS 25.142 [12], clause 6.4.5.4 and 6.4.6.4 respectively. + +In addition, for a multi-band capable BS, the following step shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +#### 6.2.4.5 Test requirements + +For UTRA TDD, the test requirement for primary CCPCH power and the differential accuracy of Primary CCPCH power are specified in TS 25.142 [12], clause 6.4.5.5 and 6.4.6.5, respectively. + +### 6.2.5 NB-IoT DL NRS power + +#### 6.2.5.1 Definition and applicability + +For NB-IoT, DL NRS power is the resource element power of the Downlink Narrow-band Reference Signal. + +The absolute DL NRS power is indicated on the DL-SCH. The absolute accuracy is defined as the maximum deviation between the DL NRS power indicated on the DL-SCH and the DL NRS power of each NB-IoT carrier at the BS antenna connector. + +#### 6.2.5.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.2.6. + +### 6.2.5.3 Test purpose + +The test purpose is to verify that the NB-IoT DL NRS power is within the limits specified by the minimum requirement. + +### 6.2.5.4 Method of test + +For this requirement Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5. The following shall apply: + +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 6.5.4.4. + +### 6.2.5.5 Test requirements + +The test requirement for DL RS power is specified in TS 36.141 [9], clause 6.5.4.5. + +## 6.3 Output power dynamics + +### 6.3.1 Definition and applicability + +Output power dynamics is defined by the MSR BS transmitter's ability to operate at varying output power levels. + +### 6.3.2 Minimum Requirement + +The minimum requirement is in TS 37.104 [2] clause 6.3. + +### 6.3.3 Test purpose + +The test purpose is to verify that the output power dynamics are met as specified by the minimum requirement. + +### 6.3.4 Method of test + +For this requirement Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5, for a BS declared to support CS1 to CS6, CS8 to CS14, CS16 to CS17 or CS19. The following shall apply for a BS declared to support CS1 to CS6, CS8 to CS14, CS16 to CS17 or CS19: + +- For references to TS 38.141-1 [26], the method of test is specified in TS 38.141-1 [26], clause 6.3.3.4 and 6.3.4.4. +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 6.3.2.4 and 6.3.3.4. +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 6.4.2.4, 6.4.3.4, 6.4.4.4 and 6.4.5.4. +- For references to TS 25.142 [12], the method of test is specified in TS 25.142 [12], clause 6.4.2.4, 6.4.3.4, 6.4.4.4, 6.4.5.4 and 6.4.6.4. +- For references to TS 51.021 [11], the method of test is specified in TS 51.021 [11], clause 6.3 and 6.4. + +If a BS is declared to support CS7, CS15 or CS18, the following shall apply: + +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 6.3.2.4 and 6.3.3.4. +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 6.4.2.4, 6.4.3.4, 6.4.4.4 and 6.4.5.4. +- For testing GSM/EDGE output power dynamics, steps in clause 6.3.4.1 and 6.3.4.2 shall apply. + +#### 6.3.4.1 Initial conditions for GSM/EDGE output power dynamics for CS7, CS15 or CS18 + +Base Station RF Bandwidth positions to be tested: $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1, + +- 1) Set up the equipment as shown in Annex D.1.1. + +### 6.3.4.2 Procedure for GSM/EDGE output power dynamics for CS7, CS15 or CS18 + +- 1) Set the BS to transmit according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.9.2. The highest possible power shall be allocated to GSM carriers taking into account declared rated total output power for Sub-group 2 and maximum supported power difference between carriers. +- 2) Perform the measurement on a GSM/EDGE carrier as follows: For every measured GSM/EDGE carrier, the requirement and the method of test is specified in TS 51.021 [11], applicable parts of clause 6.3 and 6.4. + +In addition, for a multi-band capable BS, the following step shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band where single carrier test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +### 6.3.5 Test Requirement + +For E-UTRA, the test requirement is specified in TS 36.141 [9], clause 6.3.2.5. + +For UTRA FDD, the test requirement is specified in TS 25.141 [10], clause 6.4.2.5, 6.4.3.5, 6.4.4.5 and 6.4.5.5. + +For UTRA TDD, the test requirement is specified in TS 25.142 [12], clause 6.4.2.5, 6.4.3.5, 6.4.4.5, 6.4.5.5 and 6.4.6.5. + +For GSM/EDGE, the test requirement is specified in TS 51.021 [11], clause 6.3.4 and 6.4.4. + +For NB-IoT operation in E-UTRA in-band or guard band, the test requirement is specified in TS 36.141 [9], clause 6.3.3.5. + +For NB-IoT operation in NR in-band, the test requirement is specified in TS 38.141-1 [26], clause 6.3.4.5. + +For NR, the test requirement is specified in TS 38.141-1 [26], clause 6.3.3.5. + +## 6.4 Transmit ON/OFF power + +The requirements in clause 6.4 are only applied for BC3 BS. + +### 6.4.1 Definition and applicability + +For UTRA and E-UTRA, transmitter OFF power is defined as the mean power measured over 70 us filtered with a square filter of bandwidth equal to the Base Station RF Bandwidth(s) of the BS centred on the central frequency of the Base Station RF Bandwidth(s) during the transmitter OFF period. + +For NR, transmitter OFF power is defined as the mean power measured over 70/N us filtered with a square filter of bandwidth equal to the transmission bandwidth configuration of the BS ( $BW_{Config}$ ) centred on the central frequency of the Base Station RF Bandwidth(s) during the transmitter OFF period. $N = SCS/15$ , where SCS is Sub Carrier Spacing in kHz. + +For BS supporting intra-band contiguous CA, the transmitter OFF power is defined as the mean power measured over 70/N us filtered with a square filter of bandwidth equal to the *Aggregated BS Channel Bandwidth* $BW_{Channel\_CA}$ centred on $(F_{edge,high} + F_{edge,low})/2$ during the *transmitter OFF period*. N is equal to 1 if there are any UTRA or E-UTRA carriers, or for NR $N = SCS/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *Aggregated BS Channel Bandwidth*. + +The transmitter transient period is the time period during which the transmitter is changing from the OFF period to the ON period or vice versa. The transmitter transient period is illustrated in Figure 6.4.1-1 and Figure 6.4.1-2. + +![Figure 6.4.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for E-UTRA/UTRA).](c601df62ca80fea7ce44bb54bc9ec7ed_img.jpg) + +This graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two reference levels: 'ON power level (Informative)' and 'OFF power level'. The power curve starts at the OFF level, rises during a 'Transmitter transient period', reaches the ON level during the 'Transmitter ON period (DL Timeslots and DwPTS)', and then falls back to the OFF level during another 'Transmitter transient period'. The 'Transmitter OFF period' is indicated before the first transient and after the second. The ON period is further divided into 'UL Timeslots' and 'GP and UpPTS'. + +Figure 6.4.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for E-UTRA/UTRA). + +**Figure 6.4.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for E-UTRA/UTRA)** + +![Figure 6.4.1-2: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for NR).](bc4bd26e47f7f041d024ed458839cb7f_img.jpg) + +This graph shows Transmitter output power on the y-axis and Time on the x-axis. The y-axis has two reference levels: 'ON power level (Informative)' and 'OFF power level'. The power curve starts at the OFF level, rises during a 'Transmitter transient period', reaches the ON level during the 'Transmitter ON period (DL transmission)', and then falls back to the OFF level during another 'Transmitter transient period'. The 'Transmitter OFF period' is indicated before the first transient and after the second. The ON period is further divided into 'UL transmission' and 'GP or UL transmission'. The area between the OFF power level and the start of the first transient period is shaded with diagonal lines. + +Figure 6.4.1-2: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for NR). + +**Figure 6.4.1-2: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period (for NR)** + +## 6.4.2 Minimum Requirement + +The minimum requirement is in TS 37.104 [2] clause 6.4.1.1 and clause 6.4.2.1. + +## 6.4.3 Test purpose + +The purpose of this test is to verify the BC3 BS transmitter OFF power and transient periods are within the limits of the minimum requirements. + +## 6.4.4 Method of test + +### 6.4.4.1 Initial conditions + +Test environment: normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $M_{\text{RFBW}}$ in single band operation, see clause 4.9.1; $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B_{\text{RFBW\_T}}^{\text{RFBW}}$ in multi-band operation; see clause 4.9.1. + +Connect the signal analyzer to the MSR BS antenna connector as shown in Annex D.1.1. + +### 6.4.4.2 Procedure + +- 1) Set the BS to transmit a signal according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.9.2. +- 2) For UTRA and E-UTRA, measure the mean power spectral density measured over 70 $\mu\text{s}$ filtered with a square filter of bandwidth equal to the Base Station RF Bandwidth centred on the central frequency of the Base Station RF Bandwidth. 70 $\mu\text{s}$ average window centre is set from 35 $\mu\text{s}$ after end of one transmitter ON period + 17 $\mu\text{s}$ to 35 $\mu\text{s}$ before start of next transmitter ON period – 6.25 $\mu\text{s}$ . + +For NR, measure the mean power spectral density over 70/N $\mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth of the *antenna connector* centred on the central frequency of the RF bandwidth. 70/N $\mu\text{s}$ average window centre is set from 35/N $\mu\text{s}$ after end of one transmitter ON period + 10 $\mu\text{s}$ to 35/N $\mu\text{s}$ before start of next transmitter ON period – 10 $\mu\text{s}$ . N = SCS/15, where SCS is Sub Carrier Spacing in kHz. + +For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +## 6.4.5 Test requirement + +The transmitter OFF power spectral density shall be less than -83 dBm/MHz. + +For BS capable of multi-band operation, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +The measured mean power spectral density according to clause 6.4.4.2 shall be less than -83 dBm/MHz for carrier frequency $f \leq 3.0$ GHz. + +The measured mean power spectral density shall be less than -82.5dBm/MHz for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +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 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance are given in Annex C. + +## 6.5 Transmitted signal quality + +### 6.5.1 Modulation quality + +#### 6.5.1.1 Definition and applicability + +Modulation quality is defined by the difference between the measured carrier signal and a reference signal. Modulation quality can e.g. be expressed as Error Vector Magnitude (EVM), Peak Code Domain Error (PCDE) or Relative Code Domain Error (RCDE). + +#### 6.5.1.2 Minimum Requirement + +The minimum requirement is in TS 37.104 [2] clause 6.5.1. + +### 6.5.1.3 Test purpose + +The test purpose is to verify that modulation quality is within the limit specified by the minimum requirement. + +### 6.5.1.4 Method of test + +#### 6.5.1.4.1 Initial conditions + +Test environment: normal; see Annex B.2. + +Base Station RF Bandwidth position to be tested: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ single-band operation, see clause 4.9.1 single-band operation. + +- 1) Connect measurement device to the base station antenna connector as shown in Annex D.1.1. + +#### 6.5.1.4.2 Procedure + +- 1) Set the BS to transmit according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.9.2. +- 2) Perform the modulation quality measurement on each carrier as outlined in respective measurement procedures in RAT-specific specifications, with the test configurations, test models or corresponding set of physical channels as defined in step 1: + - For EVM measurement on a NR carrier, see TS 38.141-1 [26] clause 6.5.3.4.2. + - For EVM measurement on an E-UTRA carrier, see TS 36.141 [9] clause 6.5.2.4.2. + - For EVM measurement on a UTRA FDD carrier, see TS 25.141 [10] clause 6.7.1.4.2. + - For PCDE measurement on a UTRA FDD carrier, see TS 25.141 [10] clause 6.7.2.4.2. + - For RCDE measurement on a UTRA FDD carrier, see TS 25.141 [10] clause 6.7.4.4.2. + - For EVM measurement on a UTRA TDD carrier, see TS 25.142 [12] clause 6.8.1.4.2.2. + - For PCDE measurement on a UTRA TDD carrier, see TS 25.142 [12] clause 6.8.2.4.1.2. + - For RCDE measurement on a UTRA TDD carrier, see TS 25.142 [12] clause 6.8.3.4.1.1. + - For EVM measurement on a GSM/EDGE carrier, see TS 51.021 [11] clause 6.2.2. + - For EVM measurement on an NB-IoT carrier, see TS 36.141 [9] clause 6.5.2.4.2. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 3) For multi-band capable BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of SBT or MBT shall be terminated. + +### 6.5.1.5 Test Requirements + +#### 6.5.1.5.1 E-UTRA test requirement + +For every measured E-UTRA carrier, the test requirement is specified in TS 36.141 [9] clause 6.5.2.5. + +#### 6.5.1.5.2 UTRA FDD test requirement + +For every measured UTRA FDD carrier, the test requirement is specified in TS 25.141 [10] clause 6.7.1.5, 6.7.2.5 and 6.7.4.5. + +#### 6.5.1.5.3 UTRA TDD test requirement + +For every measured UTRA TDD carrier, the test requirement is specified in TS 25.142 [12] clause 6.8.1.5, 6.8.2.5 and 6.8.3.5. + +#### 6.5.1.5.4 GSM/EDGE test requirement + +For every measured GSM/EDGE carrier, the test requirement is specified in TS 51.021 [11] clause 6.2.3. + +#### 6.5.1.5.5 NB-IoT test requirement + +For every measured NB-IoT carrier, the test requirement is specified in TS 36.141 [9] clause 6.5.2.5. + +#### 6.5.1.5.6 NR test requirement + +For every measured NR carrier, the test requirement is specified in TS 38.141-1 [26] clause 6.5.3.5. + +### 6.5.2 Frequency error + +#### 6.5.2.1 Definition and applicability + +Frequency error is the measure of the difference between the actual BS transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation. + +It is not possible to verify by testing that the data clock is derived from the same frequency source as used for RF generation. This may be confirmed by the manufacturer's declaration. + +#### 6.5.2.2 Minimum Requirement + +The minimum requirement is in TS 37.104 [2] clause 6.5.2. + +#### 6.5.2.3 Test purpose + +The test purpose is to verify that frequency error is within the limit specified by the minimum requirement. + +#### 6.5.2.4 Method of test + +Requirement is tested together with Error Vector Magnitude test, as described in clause 6.5.1. + +#### 6.5.2.5 Test Requirements + +##### 6.5.2.5.1 E-UTRA test requirement + +For every measured E-UTRA carrier, the test requirement is specified in TS 36.141 [9] clause 6.5.1.5. + +##### 6.5.2.5.2 UTRA FDD test requirement + +For every measured UTRA FDD carrier, the test requirement is specified in TS 25.141 [10] clause 6.3.5. + +##### 6.5.2.5.3 UTRA TDD test requirement + +For every measured UTRA TDD carrier, the test requirement is specified in TS 25.142 [12] clause 6.3.5. + +##### 6.5.2.5.4 GSM/EDGE test requirement + +For every measured GSM/EDGE carrier, the test requirement is specified in TS 51.021 [11] clause 6.2.3. + +#### 6.5.2.5.5 NB-IoT test requirement + +For every measured NB-IoT carrier, the test requirement is specified in TS 36.141 [9] clause 6.5.1.5. + +#### 6.5.2.5.6 NR test requirement + +For every measured NR carrier, the test requirement is specified in TS 38.141-1 [26] clause 6.5.2.5. + +### 6.5.3 Time alignment error + +#### 6.5.3.1 Definition and applicability + +This requirement applies to frame timing in: + +- UTRA single/multi-carrier transmissions, and their combinations with MIMO or TX diversity. +- E-UTRA single/multi-carrier transmissions, and their combinations with MIMO or TX diversity. +- NR single/multi-carrier transmissions, and their combinations with MIMO. +- E-UTRA Carrier Aggregation, with or without MIMO or TX diversity. +- NR Carrier Aggregation, with or without MIMO. +- NB-IoT transmissions with TX diversity. + +Frames of the WCDMA/LTE/NR/NB-IoT signals present at the BS transmitter antenna connector(s) are not perfectly aligned in time. In relation to each other, the RF signals present at the BS transmitter antenna connector(s) experience certain timing differences. + +For a specific set of signals/transmitter configuration/transmission mode, Time Alignment Error (TAE) is defined as the largest timing difference between any two signals. + +#### 6.5.3.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.5.3. + +#### 6.5.3.3 Test purpose + +To verify that the time alignment error is within the limit specified by the minimum requirement. + +#### 6.5.3.4 Method of test + +For this requirement Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5. The following shall apply: + +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 6.7.3.4. +- For references to TS 25.142 [12], the method of test is specified in TS 25.142 [12], clause 6.8.4.4. +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 6.5.3.4. +- For references to TS 38.141-1 [26], the method of test is specified in TS 38.141-1 [26], clause 6.5.4.4. + +In addition, for a multi-band capable BS, the following step shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of SBT or MBT shall be terminated. + +### 6.5.3.5 Test requirement + +For E-UTRA, the test requirement for time alignment error is specified in TS 36.141 [9], clause 6.5.3.5. + +For UTRA FDD, the test requirement for time alignment error is specified in TS 25.141 [10], clause 6.7.3.5. + +For UTRA TDD, the test requirement for time alignment error is specified in TS 25.142 [12], clause 6.8.4.5. + +For NB-IoT, the test requirement for time alignment error is specified in TS 36.141 [9], clause 6.5.3.5. + +For NR, the test requirement for time alignment error is specified in TS 38.141-1 [26], clause 6.5.4.5. + +## 6.6 Unwanted emissions + +Unwanted emissions consist of out-of-band emissions and spurious emissions [13]. 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. 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 the BS transmitter is specified in terms of an Operating band unwanted emissions requirement that defines limits for emissions in each supported downlink operating band plus the frequency ranges $\Delta f_{\text{OBUE}}$ above and $\Delta f_{\text{OBUE}}$ below each band. Emissions outside of this frequency range are limited by a spurious emissions requirement. The values of $\Delta f_{\text{OBUE}}$ are defined in table 6.6-1. For a BS with multi-RAT operation where the individual RATs are in different RAT specific bands that partially or fully overlap; $\Delta f_{\text{OBUE}}$ is according to the combined frequency range occupied by the overlapping bands. + +**Table 6.6-1: Maximum offset of OBUE outside the downlink operating band** + +| Operating band characteristics | $\Delta f_{\text{OBUE}}$ [MHz] | +|-----------------------------------------------------------------------------------|--------------------------------| +| $F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 200 \text{ MHz}$ | 10 | +| $200 \text{ MHz} < F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 900 \text{ MHz}$ | 40 | + +There is in addition a requirement for occupied bandwidth and an ACLR requirement applicable for some RATs. + +### 6.6.1 Transmitter spurious emissions + +#### 6.6.1.1 Definition and applicability + +The transmitter spurious emission limits apply from 9 kHz to 12.75 GHz, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the downlink operating band up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the downlink operating band. For BS capable of multi-band operation where multiple bands are mapped on the same antenna connector, this exclusion applies for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply and the multi-band exclusions and provisions are not applicable. + +Exceptions are the requirement in Table 6.6.1.3.1-2 in TS 37.104 [2], and specifically stated exceptions in Table 6.6.1.5.5-1 that apply also closer than $\Delta f_{\text{OBUE}}$ from the downlink operating band. For some operating bands the upper frequency limit is higher than 12.75 GHz. + +The requirements shall apply whatever the type of transmitter considered. It applies for all transmission modes foreseen by the manufacturer's specification. Unless otherwise stated, all requirements are measured as mean power (RMS). + +#### 6.6.1.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.6.1. + +### 6.6.1.3 Test purpose + +This test measures conducted spurious emission from the MSR BS transmitter antenna connector, while the transmitter is in operation. + +### 6.6.1.4 Method of test + +#### 6.6.1.4.1 Initial conditions + +Test environment: normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ single-band operation, see clause 4.9.1; $B_{\text{RFBW\_T}}$ $T_{\text{RFBW}}$ and $B_{\text{RFBW\_T}}$ $T_{\text{RFBW}}$ in multi-band operation, see clause 4.9.1. + +- 1) Connect the BS antenna connector to a measurement receiver according to Annex D.1.1 using an attenuator or a directional coupler if necessary +- 2) Measurements shall use a measurement bandwidth in accordance to the conditions in TS 37.104 [2] clause 6.6.1. +- 3) Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2-1. + +#### 6.6.1.4.2 Procedure + +- 1) Set the Base Station to transmit at maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.9.2. +- 2) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 4) For multi-band capable BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of SBT or MBT shall be terminated. + +### 6.6.1.5 Test requirements + +The measurement result in step 2 of 6.6.1.4.2 shall not exceed the maximum level specified in Table 6.6.1.5.1-1 to Table 6.6.1.5.6-1 if applicable for the BS under test. + +The test requirements of either clause 6.6.1.5.1 (Category A limits) or clause 6.6.1.5.2 (Category B limits) shall apply. In addition for a BS operating in Band Category 2, the test requirements of 6.6.1.5.3 shall apply in case of Category B limits. + +#### 6.6.1.5.1 Spurious emissions (Category A) + +The power of any spurious emission shall not exceed the limits in Table 6.6.1.5.1-1 + +**Table 6.6.1.5.1-1: BS Spurious emission limits, Category A** + +| Frequency range | Maximum level | Measurement Bandwidth | Note | +|--------------------------------------------------------------------------------------------------|---------------|-----------------------|----------------| +| 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 operating band in GHz | | 1 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [13], s4.1 +NOTE 2: Bandwidth as in ITU-R SM.329 [13], s4.1. Upper frequency as in ITU-R SM.329 [13], s2.5 table 1 +NOTE 3: This spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the DL *operating band* is reaching beyond 12.75 GHz. + +#### 6.6.1.5.2 Spurious emissions (Category B) + +The power of any spurious emission shall not exceed the limits in Table 6.6.1.5.2-1 + +**Table 6.6.1.5.2-1: BS Spurious emissions limits, Category B** + +| Frequency range | 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 operating band in GHz | -30 dBm | 1 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [13], s4.1 +NOTE 2: Bandwidth as in ITU-R SM.329 [13], s4.1. Upper frequency as in ITU-R SM.329 [13], s2.5 table 1 +NOTE 3: This spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the DL *operating band* is reaching beyond 12.75 GHz. + +#### 6.6.1.5.3 Additional test requirement for BC2 (category B) + +For a BS operating in Band Category 2 when GSM/EDGE is configured, the power of any spurious emission shall not exceed the limits in Table 6.6.1.5.3-1. + +For BS capable of multi-band operation, the limits in Table 6.6.1.5.3-1 are only applicable when all supported operating bands belong to BC2 and GSM/EDGE is configured in all bands. + +**Table 6.6.1.5.3-1: Additional BS Spurious emissions limits for BC2, Category B** + +| Frequency range | Frequency offset from transmitter operating band edge (Note1) | Maximum Level | Measurement Bandwidth | +|-------------------|---------------------------------------------------------------|---------------|-----------------------| +| 500 MHz ↔ 1 GHz | 10 – 20 MHz | -36 dBm | 300 kHz | +| | 20 – 30 MHz | -36 dBm | 1 MHz | +| | ≥ 30 MHz | -36 dBm | 3 MHz | +| 1 GHz ↔ 12.75 GHz | ≥ 30 MHz | -30 dBm | 3 MHz | + +NOTE 1: For BS capable of multi-band operation, the frequency offset is relative to the closest operating band. + +#### 6.6.1.5.4 Protection of the BS receiver of own or different BS + +This requirement shall be applied for FDD operation in order to prevent the receivers of Base Stations being desensitised by emissions from the BS transmitter. It is measured at the transmit antenna port for any type of BS which has common or separate Tx/Rx antenna ports. + +The power of any spurious emission shall not exceed the limits in Table 6.6.1.5.4-1, depending on the declared Base Station class and Band Category. + +**Table 6.6.1.5.4-1: BS Spurious emissions limits for protection of the BS receiver** + +| BS Class | Band category | Frequency range | Maximum Level | Measurement Bandwidth | Note | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|------------------------------|---------------|-----------------------|------| +| Wide Area BS | BC1 | $F_{UL\_low} - F_{UL\_high}$ | -96 dBm | 100 kHz | | +| Wide Area BS | BC2 | $F_{UL\_low} - F_{UL\_high}$ | -98 dBm | 100 kHz | | +| Medium Range BS | BC1,BC2 | $F_{UL\_low} - F_{UL\_high}$ | -91 dBm | 100 kHz | | +| Local Area BS | BC1,BC2 | $F_{UL\_low} - F_{UL\_high}$ | -88 dBm | 100 kHz | | +| Note 1: For E-UTRA Band 28 BS operating in regions where Band 28 is only partially allocated for E-UTRA operations, this requirement only applies in the UL frequency range of the partial allocation. | | | | | | + +#### 6.6.1.5.5 Additional spurious emission requirements + +These requirements may be applied for the protection of system operating in frequency ranges other than the BS downlink operating band. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the BS, or they may be set by local or regional regulation as a mandatory requirement for an operating band. It is in some cases not stated in the present document whether a requirement is mandatory or under what exact circumstances that a limit applies, since this is set by local or regional regulation. An overview of regional requirements in the present document is given in clause 4.4. + +Some requirements may apply for the protection of specific equipment (UE, MS and/or BS) or equipment operating in specific systems (GSM/EDGE, CDMA, UTRA, E-UTRA, NR, etc.) as listed below. The power of any spurious emission shall not exceed the limits of Table 6.6.1.5.5-1 for a BS where requirements for co-existence with the system listed in the first column apply. For BS capable of multi-band operation, the exclusions and conditions in the Note column of Table 6.6.1.5.5-1 apply for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the exclusions and conditions in the Note column of Table 6.6.1.5.5-1 apply for the operating band supported at that antenna connector. + +**Table 6.6.1.5.5-1: BS Spurious emissions limits for co-existence with systems operating in other frequency bands** + +| System type to co-exist with | Frequency range for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|---------------------------------------------------------------|----------------------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | -57 dBm | 100 kHz | This requirement does not apply to BS operating in band 8 | +| | 876 - 915 MHz | -61 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to BS operating in band 8, since it is already covered by the requirement in clause 6.6.1.5.4. | +| DCS1800 (Note 3) | 1805 - 1880 MHz | -47 dBm | 100 kHz | This requirement does not apply to BS operating in band 3. | +| | 1710 - 1785 MHz | -61 dBm | 100 kHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in clause 6.6.1.5.4. | +| PCS1900 | 1930 - 1990 MHz | -47 dBm | 100 kHz | This requirement does not apply to BS operating in band 2, 25, band 36 or band 70. | +| | 1850 - 1910 MHz | -61 dBm | 100 kHz | This requirement does not apply to BS operating in band 2 or 25, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in band 35. | +| GSM850 or CDMA850 | 869 - 894 MHz | -57 dBm | 100 kHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -61 dBm | 100 kHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 2110 - 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65. | +| | 1920 - 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, since it is already covered by the requirement in clause 6.6.1.5.4. | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1930 - 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25 or 70. | +| | 1850 - 1910 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 2 or 25, since it is already covered by the requirement in clause 6.6.1.5.4 | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 (Note 3) | 1805 - 1880 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9. | +| | 1710 - 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in clause 6.6.1.5.4.
For BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in clause 6.6.1.5.4. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66. | +| | 1710 - 1755 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66, since it is already covered by the requirement in clause 6.6.1.5.4. | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 869 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 18, 19 or NR Band n18 | 860 - 890 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 18, 19 | +| | 815 - 830 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 18 since it is already covered by the requirement in clause 6.6.1.5.4. | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 830 - 845 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 19, since it is already covered by the requirement in clause 6.6.1.5.4. | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2620 - 2690 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 7. | +| | 2500 - 2570 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 7, since it is already covered by the requirement in clause 6.6.1.5.4. | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 - 960 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 8. | +| | 880 - 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 8, since it is already covered by the requirement in clause 6.6.1.5.4. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9. | +| | 1749.9 - 1784.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9, since it is already covered by the requirement in clause 6.6.1.5.4. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66. | +| | 1710 - 1770 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 10 or 66, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in band 4, it applies for 1755 MHz to 1770 MHz, while the rest is covered in clause 6.6.1.5.4. | +| 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 BS operating in band 11, 21, 32, 50, 74 or 75. | +| | 1427.9 - 1447.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 11 or 74, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in band 32, 50, 51, 75 or 76. | +| | 1447.9 – 1462.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 21 or 74, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in band 32, 50 or 75. | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 729 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 12 or 85. | +| | 699 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 12 or 85, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7). | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 746 - 756 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 13. | +| | 777 - 787 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 13, since it is already covered by the requirement in clause 6.6.1.5.4. | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 758 - 768 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 14. | +| | 788 - 798 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 14, since it is already covered by the requirement in clause 6.6.1.5.4. | +| E-UTRA Band 17 | 734 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 17. | +| | 704 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 17, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7). | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 791 - 821 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 20 or 28. | +| | 832 - 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, since it is already covered by the requirement in clause 6.6.1.5.4. | +| UTRA FDD Band XXII or | 3510 – 3590 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, 42, 48, 49, 77 or 78. | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 22 | 3410 – 3490 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to Band 42, 77 or 78. | +| E-UTRA Band 24 or NR Band n24 | 1525 – 1559 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 24. | +| | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 24, since it is already covered by the requirement in clause 6.6.1.5.4. | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR Band n25 | 1930 - 1995 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25 or 70. | +| | 1850 - 1915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 25, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in band 2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.6.1.5.4. | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 814 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 26, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in band 5, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.6.1.5.4. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| E-UTRA Band 27 | 852 – 869 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 5, 26 or 27. | +| | 807 – 824 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 27, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 26, it applies for 807 MHz to 814 MHz, while the rest is covered in clause 6.6.1.5.4. This requirement also applies to BS operating in Band 28, starting 4 MHz above the Band 28 downlink operating band (Note 6). | +| E-UTRA Band 28 or NR Band n28 | 758 - 803 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, 28, 44 or 67. | +| | 703 - 748 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in Band 44. For BS operating in Band 67, it applies for 703-736MHz. For E-UTRA BS operating in Band 68, it applies for 728MHz to 733MHz. | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 29 or 85. | +| E-UTRA Band 30 or NR Band n30 | 2350 - 2360 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 30 or 40. | +| | 2305 - 2315 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 30, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in Band 40. | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | + +| | | | | | +|---------------------------------------------------|-------------------|---------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 452.5 – 457.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in band 72 or 73. | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50, 74 or 75. | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR Band n34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 2, 25 or 36 | +| UTRA TDD in Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570 – 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 38 or 69. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR Band n39 | 1880 – 1920MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or NR Band n41 | 2496 – 2690MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52, 77 or 78. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 42, 43, 48, 49, 77 or 78. | +| E-UTRA Band 44 | 703 - 803 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 - 1467 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 47 | 5855 - 5925 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 77 or 78 | +| E-UTRA Band 49 | 3550 – 3700 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 77 or 78 | +| E-UTRA Band 50 or NR Band n50 | 1432 - 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76. | +| E-UTRA Band 51 or NR Band n51 | 1427 - 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 50, 51, 75 or 76. | + +| | | | | | +|-------------------------------|-------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 52 | 3300 – 3400 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 42 or 52. | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 41 or 53. | +| E-UTRA Band 54 or NR Band n54 | 1670 - 1675 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 54. | +| E-UTRA Band 65 or NR Band n65 | 2110 - 2200 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, | +| | 1920 - 2010 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 65, since it is already covered by the requirement in clause 6.6.1.5.4.
For BS operating in Band 1, it applies for 1980 MHz to 2010 MHz, while the rest is covered in clause 6.6.1.5.4. | +| E-UTRA Band 66 or NR Band n66 | 2110 - 2200 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10, 23 or 66. | +| | 1710 - 1780 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 66, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in clause 6.6.1.5.4. For BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in clause 6.6.1.5.4. | +| E-UTRA Band 67 or NR band n67 | 738 – 758 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 28 or 67. | +| E-UTRA Band 68 | 753 -783 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 28 or 68. | +| | 698-728 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 68, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 28, it applies between 698 MHz and 703 MHz, while the rest is covered in clause 6.6.1.5.4. | +| E-UTRA Band 69 | 2570 - 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 38 or 69. | +| E-UTRA Band 70 or NR Band n70 | 1995 - 2020 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25 or 70 | +| | 1695 – 1710 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 70, since it is already covered by the requirement in clause 6.6.1.5.4. | +| E-UTRA Band 71 or NR Band n71 | 617 - 652 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 71. | +| | 663 – 698 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 71, since it is already covered by the requirement in clause 6.6.1.5.4. | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 451 - 456 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 72, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in band 73. | +| E-UTRA Band 73 | 460 - 465 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 450 - 455 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 73, since it is already covered by the requirement in clause 6.6.1.5.4. | +| E-UTRA Band 74 or NR Band n74 | 1475 – 1518 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50, 74 or 75. | + +| | | | | | +|-------------------------------|-----------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 1427 – 1470 MHz | -49 dBm | 1MHz | This requirement does not apply to BS operating in Band 74, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in band 32, 45, 50, 51, 75 or 76. | +| E-UTRA Band 75 or NR Band n75 | 1432 - 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76. | +| E-UTRA Band 76 or NR Band n76 | 1427 - 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75 or 76. | +| NR Band n77 | 3300 – 4200 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52, 77 or 78 | +| NR Band n78 | 3300 – 3800 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52, 77 or 78 | +| NR Band n79 | 4400 – 5000 MHz | -52 dBm | 1 MHz | | +| NR Band n80 | 1710 - 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in clause 6.6.1.5.4.
For BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in clause 6.6.1.5.4. | +| NR Band n81 | 880 - 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 8, since it is already covered by the requirement in clause 6.6.1.5.4. | +| NR Band n82 | 832 - 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, since it is already covered by the requirement in clause 6.6.1.5.4. | +| NR Band n83 | 703 - 748 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in Band 44. For BS operating in Band 67, it applies for 703-736MHz. For BS operating in Band 68, it applies for 728MHz to 733MHz. | +| NR Band n84 | 1920 - 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, since it is already covered by the requirement in clause 6.6.1.5.4. | +| E-UTRA Band 85 or NR band n85 | 728 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 12, 29 or 85. | +| | 698 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 85, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7). | +| NR Band n86 | 1710 - 1780 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 66, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in clause 6.6.1.5.4. For BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in clause 6.6.1.5.4. | +| E-UTRA Band 87 | 420 - 425 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 87 or 88. | +| | 410 – 415 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 87, since it is already covered by the requirement in clause 6.6.1.5.4 | +| E-UTRA Band 88 | 422 - 427 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 87 or 88. | +| | 412 - 417 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 88, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to E-UTRA BS operating in band 87. | + +| | | | | | +|---------------------------------|--------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n89 | 824 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in clause 6.6.1.5.4. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| NR Band n91 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 50, 51, 75 or 76. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 20. | +| NR Band n92 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 20. | +| NR Band n93 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 50, 51, 75 or 76. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 8. | +| NR Band n94 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 8. | +| NR Band n95 | 2010 - 2025 MHz | -52 dBm | 1 MHz | | +| NR Band n96 | 5925 - 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n97 | 2300 – 2400MHz | -52 dBm | 1 MHz | | +| NR Band n98 | 1880 – 1920MHz | -52 dBm | 1 MHz | | +| NR Band n99 | 1626.5 -1660.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 24, since it is already covered by the requirement in subclause 6.6.1.5.4. | +| NR Band n100 | 919.4 – 925 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 8. | +| | 874.4 – 880 MHz | -49 dBm | 1 MHz | | +| NR Band n101 | 1900 – 1910 MHz | -52 dBm | 1 MHz | | +| NR Band n102 | 5925 – 6425 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -52 dBm | 1 MHz | | +| | 787 – 788 MHz | -49 dBm | 1 MHz | | +| NR Band n104 | 6425 – 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n105 | 612 – 652 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 71 | +| | 663 – 703 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 106. | +| | 896 – 901 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 106, since it is already covered by the requirement in clause 6.6.1.5.4.
This requirement does not apply to BS operating in band 5 or 26. | +| NR Band n109 | 1432 - 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76. | +| | 703 - 733 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in clause 6.6.1.5.4. This requirement does not apply to BS operating in Band 44. For E-UTRA BS operating in Band 68, it applies for 728MHz to 733MHz. | + +NOTE 5: Void + +NOTE 1: As defined in the scope for spurious emissions in this clause, except for the cases where the noted requirements apply to a BS operating in Band 25, Band 27, Band 28 or Band 29, the co-existence requirements in Table 6.6.1.5.5-1 do not apply for the 10 MHz frequency range immediately outside the downlink operating band (see Tables 4.4-1 and 4.4-2). Emission limits for this excluded frequency range may be covered by local or regional requirements. + +- NOTE 2: Table 6.6.1.5.5-1 assumes that two operating bands, where the frequency ranges in Table 4.4-1 or Table 4.4-2 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 3: For the protection of DCS1800, UTRA Band III, E-UTRA Band 3 or NR Band n3 in China, the frequency ranges of the downlink and uplink protection requirements are 1805 – 1850 MHz and 1710 – 1755 MHz respectively. +- NOTE 4: TDD base stations deployed in the same geographical area, that are synchronized and use the same or adjacent operating bands can transmit without additional co-existence requirements. For unsynchronized base stations (except in Band 46), special co-existence requirements may apply that are not covered by the 3GPP specifications. +- NOTE 6: For Band 28 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with Band 27 UL operating band. +- NOTE 7: For Band 29 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with UTRA Band XII or E-UTRA Band 12 or NR Band n12 UL operating band or E-UTRA Band 17 UL operating band or E-UTRA Band 85 UL operating band. + +The following requirement may be applied for the protection of PHS. This requirement is also applicable at specified frequencies falling between $\Delta f_{OBUE}$ below the lowest BS transmitter frequency of the downlink operating band and $\Delta f_{OBUE}$ above the highest BS transmitter frequency of the downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.6.1.5.5-2: BS Spurious emissions limits for BS for co-existence with PHS** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|---------------------------------------------------|---------------|-----------------------|---------------------------------------------------------------------------| +| 1884.5 - 1915.7 MHz | -41 dBm | 300 kHz | Applicable for co-existence with PHS system operating in 1884.5-1915.7MHz | +| NOTE: The requirement is not applicable in China. | | | | + +The following requirement may apply to BS operating in Band 41 in certain regions. This requirement is also applicable at the frequency range from $\Delta f_{OBUE}$ below the lowest frequency of the BS downlink operating band up to $\Delta f_{OBUE}$ above the highest frequency of the BS downlink operating band. + +For Band 41 NR operation, the additional BS spurious emissions limits shall be applied to the sum of the emission power over all *antenna connectors*. + +The power of any spurious emission shall not exceed: + +**Table 6.6.1.5.5-3: Additional BS Spurious emissions limits for BS operating in Band 41** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|-----------------------------------------------------------------------------|---------------|-----------------------|------| +| 2505MHz – 2535MHz | -42dBm | 1 MHz | | +| NOTE: This requirement applies for carriers allocated within 2545-2645 MHz. | | | | + +In addition to the requirements in clauses 6.6.1.5.1 to 6.6.1.5.4 and above in the present clause, the BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +The following requirement may apply to BS operating in Band 30 in certain regions. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the BS downlink operating band up to 10 MHz above the highest frequency of the BS downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.6.1.5.5-4: Additional BS Spurious emissions limits for Band 30** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|---------------------|---------------|-----------------------|------| +| 2200MHz – 2345MHz | -45dBm | 1 MHz | | +| 2362.5MHz – 2365MHz | -25dBm | 1 MHz | | +| 2365MHz – 2367.5MHz | -40dBm | 1 MHz | | +| 2367.5MHz – 2370MHz | -42dBm | 1 MHz | | +| 2370MHz – 2395MHz | -45dBm | 1 MHz | | + +In certain regions the following requirement may apply to E-UTRA BS operating in Band 45. Emissions shall not exceed the maximum levels specified in Table 6.6.1.5.5-5. + +**Table 6.6.1.5.5-5: Emissions limits for protection of adjacent band services** + +| Operating Band | Filter centre frequency, $F_{\text{filter}}$ | Maximum Level [dBm] | Measurement Bandwidth | +|----------------|---------------------------------------------------------------------|---------------------|-----------------------| +| 45 | $F_{\text{filter}} = 1467.5$ | -20 | 1 MHz | +| | $F_{\text{filter}} = 1468.5$ | -23 | 1 MHz | +| | $F_{\text{filter}} = 1469.5$ | -26 | 1 MHz | +| | $F_{\text{filter}} = 1470.5$ | -33 | 1 MHz | +| | $F_{\text{filter}} = 1471.5$ | -40 | 1 MHz | +| | $1472.5 \text{ MHz} \leq F_{\text{filter}} \leq 1491.5 \text{ MHz}$ | -47 | 1 MHz | + +The following requirement may apply to E-UTRA BS operating in Band 48 in certain regions. The power of any spurious emission shall not exceed: + +**Table 6.6.1.5.5-6: Additional BS Spurious emissions limits for Band 48** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|----------------------------------------|---------------|-----------------------|-------------------------------------------------| +| 3530MHz – 3720MHz | -25dBm | 1 MHz | Applicable 10MHz from the assigned channel edge | +| 3100MHz – 3530MHz
3720MHz – 4200MHz | -40dBm | 1 MHz | | + +The following requirement may also apply to BS operating in Band 54 in certain regions. The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to Table 6.6.1.5.5-7 shall not exceed the maximum emission levels $P_{\text{EM,B54,a}}$ , $P_{\text{EM,B54,b}}$ , $P_{\text{EM,B54,c}}$ , $P_{\text{EM,B54,d}}$ , $P_{\text{EM,B54,e}}$ and $P_{\text{EM,B54,f}}$ declared by the manufacturer. + +**Table 6.6.1.5.5-7: Declared Band 54 emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range | Declared emission level (dBW) (Measurement bandwidth = 1 MHz) | Declared emission level (dBW) of discrete emissions of less than 700 Hz bandwidth (Measurement bandwidth = 1 kHz) | Declared emission level (dBW) of discrete emissions of less than 2 kHz bandwidth (Measurement bandwidth = 1 kHz) | +|----------------|-----------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| 54 | 1541 - 1559 MHz | $P_{\text{EM,B54,a}}$ | | $P_{\text{EM,B54,f}}$ | +| | 1559 - 1610 MHz | $P_{\text{EM,B54,b}}$ | $P_{\text{EM,B54,d}}$ | | +| | 1610 - 1650 MHz | $P_{\text{EM,B54,c}}$ | $P_{\text{EM,B54,e}}$ | | + +Note: The regional requirements specified in attachment to the FCC reference document, 0007135419, are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The EIRP level is calculated using: $P_{\text{EIRP}} = P_{\text{E}} + G_{\text{ant}}$ where $P_{\text{E}}$ denotes the BS unwanted emission level at the antenna connector, $G_{\text{ant}}$ equals the BS antenna gain minus feeder loss. The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. + +#### 6.6.1.5.6 Co-location with other Base Stations + +These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA and/or NR BS are co-located with a BS. + +The requirements assume a 30 dB coupling loss between transmitter and receiver and are based on co-location with base stations of the same class. + +The power of any spurious emission shall not exceed the limits of Table 6.6.1.5.6-1 for a BS where requirements for co-location with a BS type listed in the first column apply, depending on the declared Base Station class. For BS capable of multi-band operation, the exclusions and conditions in the Note column of Table 6.6.1.5.6-1 apply for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the exclusions and conditions in the Note column of Table 6.6.1.5.6-1 apply for the operating band supported at that antenna connector. + +**Table 6.6.1.5.6-1: BS Spurious emissions limits for BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA BS) | Maximum Level (MR BS) | Maximum Level (LA BS) | Measurement Bandwidth | Note | +|-----------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------------------------------------------------| +| GSM900 | 876-915 MHz | -98 dBm | -91 dBm | -88 dBm | 100 kHz | | +| DCS1800 | 1710 - 1785 MHz | -98 dBm | -91 dBm | -88 dBm | 100 kHz | | +| PCS1900 | 1850 - 1910 MHz | -98 dBm | -91 dBm | -88 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 - 849 MHz | -98 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 1920 - 1980 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1850 - 1910 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 | 1710 - 1785 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 824 - 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 - 845 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2500 - 2570 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 880 - 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1447.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 50, 51, 75 or 76 | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 699 - 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 777 - 787 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 788 - 798 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 - 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 18 or NR Band n18 | 815 - 830 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 832 - 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 32, 50 or 75 | + +| | | | | | | | +|-----------------------------------------------------|---------------------|---------|---------|---------|---------|--------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 – 3490 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 77 or 78 | +| E-UTRA Band 24 or NR Band n24 | 1626.5 – 1660.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR Band n25 | 1850 - 1915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 814 - 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 27 | 807 - 824 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 28 or NR Band n28 | 703 – 748 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | +| E-UTRA Band 30 or NR Band n30 | 2305 - 2315 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 40 | +| E-UTRA Band 31 or NR Band n31 | 452.5 – 457.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR Band n34 | 2010 - 2025 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 2 and 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 37.
This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | + +| | | | | | | | +|---------------------------------------------------------|-----------------|---------|---------|---------|---------|---------------------------------------------------------------------------------| +| UTRA TDD Band d)
or E-UTRA Band 38
or NR Band n38 | 2570 – 2620 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 38. | +| UTRA TDD Band f)
or E-UTRA Band 39
or NR Band n39 | 1880 – 1920MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 33 and 39 | +| UTRA TDD Band e)
or E-UTRA Band 40
or NR Band n40 | 2300 – 2400MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or
NR Band n41 | 2496 – 2690MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52 77 or 78. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48, 49 77 or 78. | +| E-UTRA Band 44 | 703 – 803 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or
NR Band n46 | 5150 – 5925 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 48 or
NR Band n48 | 3550 – 3700 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48, 49, 77 or 78 | +| E-UTRA Band 49 | 3550 – 3700 MHz | N/A | N/A | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48, 49, 77 or 78 | + +| | | | | | | | +|-------------------------------|-------------------|---------|---------|---------|---------|---------------------------------------------------------------------------------| +| E-UTRA Band 50 or NR Band n50 | 1432 – 1517 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 11, 21, 32, 51, 74, 75 or 76 | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -88 dBm | 100 kHz | This is not applicable to E-UTRA BS operating in Band 50, 75 or 76 | +| E-UTRA Band 52 | 3300 – 3400 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42 or 52. | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 54 | +| E-UTRA Band 65 or NR Band n65 | 1920 - 2010 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 66 or NR Band n66 | 1710 – 1780 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 68 | 698 – 728 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 70 or NR Band n70 | 1695 – 1710 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 71 or NR Band 71 | 663 – 698 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 72 or NR Band n72 | 451 – 456 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 73 | 450 – 455 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 74 or NR Band n74 | 1427 – 1470 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 50 or 51 | +| NR Band n77 | 3300 – 4200 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52, 77 or 78 | +| NR Band n78 | 3300 – 3800 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 49, 52, 77 or 78 | +| NR Band n79 | 4400 – 5000 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | + +| | | | | | | | +|---------------------------------|---------------------|---------|---------|---------|---------|---------------------------------------------------| +| NR Band n80 | 1710 – 1785 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n81 | 880 – 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n82 | 832 – 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n83 | 703 – 748 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | +| NR Band n84 | 1920 – 1980 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 85 or NR band n85 | 698 - 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n86 | 1710 – 1780 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 87 | 410 - 415 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 88 | 412 - 417 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n89 | 824 - 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n91 | 832 – 862 MHz | N/A | N/A | -88 dBm | 100 kHz | | +| NR Band n92 | 832 – 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n93 | 880 – 915 MHz | N/A | N/A | -88 dBm | 100 kHz | | +| NR Band n94 | 880 – 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n95 | 2010 - 2025 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n96 | 5925 - 7125 MHz | N/A | -90dBm | -87 dBm | 100 kHz | | +| NR Band n97 | 2300 – 2400MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n98 | 1880 – 1920MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n100 | 874.4 – 880 MHz | -96 dBm | N/A | N/A | 100 kHz | | +| NR Band n101 | 1900 – 1910 MHz | -96 dBm | N/A | N/A | 100 kHz | | +| NR Band n102 | 5925 – 6425 MHz | N/A | -90dBm | -87 dBm | 100 kHz | | +| E-UTRA Band 103 | 787 – 788 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n104 | 6425 – 7125 MHz | -95 dBm | -90 dBm | -87 dBm | 100 kHz | | +| NR Band n105 | 663 – 703 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 106 or NR Band n106 | 896 – 901 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n109 | 703 – 733 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | + +NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in Table 6.6.1.5.6-1 do not apply for the $\Delta f_{OBUE}$ frequency range immediately outside the BS transmit frequency range of a downlink operating band (see Tables 4.4-1 and 4.4-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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [14]. + +NOTE 2: Table 6.6.1.5.6-1 assumes that two operating bands, where the corresponding BS transmit and receive frequency ranges in Table 4.4-1 or Table 4.4-2 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 3: Co-located TDD Base Stations that are synchronized and using the same or adjacent operating band can transmit without special co-locations requirements. For unsynchronized Base Stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +## 6.6.2 Operating band unwanted emissions + +### 6.6.2.1 Definition and applicability + +The Operating band unwanted emission limits are defined from $\Delta f_{OBUE}$ below the lowest frequency of each supported downlink operating band to the lower Base Station RF Bandwidth edge located at $F_{BW RF,low}$ and from the upper Base Station RF Bandwidth edge located at $F_{BW RF,high}$ up to $\Delta f_{OBUE}$ above the highest frequency of each supported downlink + +operating band. In addition, for a BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for a BS operating in multiple bands, it applies inside any Inter RF Bandwidth gap. The values of $\Delta f_{\text{OBUE}}$ are defined in table 6.6-1. + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification, except for any operating band with GSM/EDGE single RAT operation. The requirements in TS 45.005 [6] as defined in clause 6.6.2.3 apply to an MSR Base Station for any operating band with GSM/EDGE single RAT operation in Band Category 2. + +For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply and the cumulative evaluation of the emission limit in the Inter RF Bandwidth gap are not applicable. + +### 6.6.2.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.6.2.1, 6.6.2.2, 6.6.2.3 and 6.6.2.4. + +### 6.6.2.3 Test purpose + +This test measures the emissions of the MSR BS, close to the assigned channel bandwidth of the wanted signal, while the transmitter is in operation. + +### 6.6.2.4 Method of test + +For some of the test cases Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5. In this case the following shall apply: + +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 6.5.2.1.4. +- For references to TS 25.142 [12], the method of test is specified in TS 25.142 [12], clause 6.6.2.1.4. +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 6.6.3.4. +- For references to TS 38.141-1 [26], the method of test is specified in TS 38.141-1 [26], clause 6.6.4.4. + +NOTE: In this case the test requirements of the present document defined in clause 6.6.2.5 apply. + +For GSM/EDGE single-RAT requirements, the method of test is specified in TS 51.021 [11], applicable parts of clause 6.5.1, 6.5.2, 6.6.2 and 6.12. + +For test requirements of operating band unwanted emissions using the MSR test configurations defined in clause 4.8, the, method of test described in clauses 6.6.2.4.1 and 6.6.2.4.2 applies. + +#### 6.6.2.4.1 Initial conditions + +Test environment: normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single-band operation, see clause 4.9.1; $B_{\text{RFBW\_T}}$ $T_{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}$ $T_{\text{RFBW}}$ in multi-band operation, see clause 4.9.1. + +- 1) Connect the signal analyzer to the Base Station antenna connector as shown in Annex D.1.1. + +As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity, efficiency and to avoid e.g. carrier leakage, the resolution bandwidth may 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. + +- 2) Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2-1. + +#### 6.6.2.4.2 Procedure + +- 1) Set the Base Station to transmit at maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.9.2. +- 2) Step the centre frequency of the measurement filter in contiguous steps and measure the emission within the specified frequency ranges with the specified measurement bandwidth. For BS operating in multiple bands or non-contiguous spectrum, the emission within the Inter RF Bandwidth or sub-block gap shall be measured using the specified measurement bandwidth from the closest RF Bandwidth or sub block edge. +- 3) Repeat the test for the remaining test cases with channel set-up according to clause 5 and clause 4.9.2. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 4) For multi-band capable BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of SBT or MBT shall be terminated. + +#### 6.6.2.5 Test requirement + +##### 6.6.2.5.1 Test requirements for Band Categories 1 and 3 + +For a Wide Area BS operating in Band Category 1 or Band Category 3, the requirement applies outside the Base Station RF Bandwidth edges. In addition, for a Wide Area BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for a Wide Area BS operating in multiple bands, it applies inside any Inter RF Bandwidth gap. + +For a Medium Range BS operating in Band Category 1 the requirement applies outside the Base Station RF Bandwidth edges. In addition, for a Medium Range BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for a Medium Range BS operating in multiple bands, it applies inside any Inter RF Bandwidth gap. + +For a Local Area BS operating in Band Category 1 the requirement applies outside the Base Station RF Bandwidth edges. In addition, for a Local Area BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for a Local Area BS operating in multiple bands, it applies inside any Inter RF Bandwidth gap. + +Outside the Base Station RF Bandwidth edges, emissions shall not exceed the maximum levels specified in Tables 6.6.2.5.1-1 to 6.6.2.5.1-4b below, where: + +- $\Delta f$ is the separation between the Base Station RF Bandwidth edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is the offset to the frequency $\Delta f_{OBUE}$ outside the downlink operating band. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a BS operating in multiple bands, inside any Inter RF Bandwidth gaps with $W_{gap} < 2 * \Delta f_{OBUE}$ , emissions shall not exceed the cumulative sum of the test requirements specified at the Base Station RF Bandwidth edges on each side of the Inter RF Bandwidth gap. The test requirement for Base Station RF Bandwidth edge is specified in Table 6.6.2.5.1-1 to 6.6.2.5.1-4b below, where in this case: + +- $\Delta f$ is the separation between the Base Station RF Bandwidth edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the Inter RF Bandwidth gap minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For BS capable of multi-band operation where multiple bands are mapped on the same antenna connector, the operating band unwanted emission limits apply also in a supported operating band without any carriers transmitted, in the case + +where there are carriers transmitted in other supported operating band(s). In this case where there is no carrier transmitted in an operating band the operating band unwanted emission limit, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{\max}$ ), of a band where there are no carriers transmitted shall apply from $\Delta f_{\text{OBUE}}$ below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the supported downlink operating band without any carrier transmitted. And no cumulative limits are applied in the inter-band gap between a supported downlink band with carrier(s) transmitted and a downlink band without any carrier transmitted. + +Inside any sub-block gap for a BS operating in non-contiguous spectrum, emissions shall not exceed the cumulative sum of the test requirements specified for the adjacent sub blocks on each side of the sub block gap. The test requirement for each sub block is specified in Tables 6.6.2.5.1-1 to 6.6.2.5.1-4b below, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge frequency. +- $f_{\text{offset}}$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is equal to the sub block gap bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{\max}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +For Band 41 NR operation in Japan, the operating band unwanted emissions limits shall be applied to the sum of the emission power over all *antenna connectors*. + +Applicability of Wide Area operating band unwanted emission requirements in Tables 6.6.2.5.1-1/1a, 6.6.2.5.1-1c and 6.6.2.5.1-1d/1e is specified in Table 6.6.2.5.1-0. + +Note: Option 1 and Option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [5] and TS 38.104 [27]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [3]. + +**Table 6.6.2.5.1-0: Applicability of operating band unwanted emission requirements for BC1 and BC3 Wide Area BS** + +| NR Band operation | Standalone NB-IoT carrier adjacent to the BS RF bandwidth edge or UTRA supported | Applicable requirement table | +|----------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------| +| None | Y/N | 6.6.2.5.1-1/1a (option 2) | +| In certain regions (NOTE 2), bands 1, 7, 38, 65 | N | 6.6.2.5.1-1/1a (option 2) | +| Any | Y | 6.6.2.5.1-1/1a (option 2) | +| Any below 1GHz | N | 6.6.2.5.1-1c (option 1) | +| Any above 1GHz except for, in certain regions (NOTE 2), bands 1, 7, 38, 65 | N | 6.6.2.5.1-1d/1e (option 1) | + +NOTE 1: Void. +NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [13] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [5] and TS 38.104 [27] are applied. + +**Table 6.6.2.5.1-1: WA BS OBUE in BC1 and BC3 bands $\leq 3$ GHz - option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-12.5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$
(Note 4) | 30 kHz | +| (Note 5) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.5 dBm (Note 4) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -11.5 dBm (Note 4) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 4, 7) | 1 MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -15dBm/MHz (for MSR BS supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ ). + +NOTE2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.1-1b apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 4: For MSR BS supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ . + +**Table 6.6.2.5.1-1a: WA BS OBUE in BC1 and BC3 bands $> 3$ GHz - option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.2 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 5) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.2 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -11.2 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 7) | 1 MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -15dBm/MHz. + +NOTE2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 6.6.2.5.1-1b: WA BS OBUE in BC1 and BC3 bands $\leq 3$ GHz applicable for: BS with standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2, 3, 4) | Measurement bandwidth (Note 6) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $Max(6.5 \text{ dBm} - 60 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB} + X \text{ dB}, -12.5 \text{ dBm})$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $Max(3.5 \text{ dBm} - 160 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.065 \right) \text{ dB} + X \text{ dB}, -12.5 \text{ dBm})$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the RF bandwidth edge is a standalone NB-IoT carrier, the value of $X = P_{\text{NB-IoTcarrier}} - 43$ , where $P_{\text{NB-IoTcarrier}}$ is the power level of the standalone NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +**Table 6.6.2.5.1-1c: WA BS OBUE in BC1 and BC3 bands $\leq 1$ GHz - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.5 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $-12.5 \text{ dBm}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-16 \text{ dBm}$ (Note 7) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $-16 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.2.5.1-1d: WA BS OBUE in BC1 and BC3 bands $> 1$ GHz and $\leq 3$ GHz - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.5 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $-12.5 \text{ dBm}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-15 \text{ dBm}$ (Note 7) | 1 MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $-15 \text{ dBm}/1 \text{ MHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 6.6.2.5.1-1e: WA BS OBUE in BC1 and BC3 bands above 3 GHz - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.2 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -12.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 7) | 1MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -15dBm/1MHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 6.6.2.5.1-2: MR BS OBUE in BC1 bands $\leq 3 \text{ GHz}$ applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38 \text{ dBm}$ and not supporting NR; or BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38 \text{ dBm}$ , supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{Rated,c}} - 56.5 \text{ dB} - 7/5(f\_offset/\text{MHz} - 0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{Rated,c}} - 51.5 \text{ dB} - 15(f\_offset/\text{MHz} - 0.215) \text{ dB}$ | 30 kHz | +| (Note 5) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{Rated,c}} - 63.5 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.1 \text{ MHz}$ | $P_{\text{Rated,c}} - 50.5 \text{ dB}$ | 1 MHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.1 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{Rated,c}} - 50.5 \text{ dB}, -13.5 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | $P_{\text{Rated,c}} - 54.5 \text{ dB}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P_{\text{Rated,c}} - 56 \text{ dB}$ (Note 7) | 1MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $(P_{\text{Rated,c}} - 56 \text{ dB})/\text{MHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.1-2b apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.5.1-2a: MR BS OBUE in BC1 bands > 3 GHz applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm and not supporting NR; or BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{Rated,c}} - 56.2 \text{ dB} - 7/5(f\_offset/\text{MHz}-0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{Rated,c}} - 51.2 \text{ dB} - 15(f\_offset/\text{MHz}-0.215) \text{ dB}$ | 30 kHz | +| (Note 5) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{Rated,c}} - 63.2 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.1 \text{ MHz}$ | $P_{\text{Rated,c}} - 50.2 \text{ dB}$ | 1 MHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.1 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{Rated,c}} - 50.2 \text{ dB}, -13.2 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | $P_{\text{Rated,c}} - 54.2 \text{ dB}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P_{\text{Rated,c}} - 56 \text{ dB}$ (Note 7) | 1 MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $(P_{\text{Rated,c}} - 56 \text{ dB})/\text{MHz}$ . + +NOTE2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 6.6.2.5.1-2b: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $31 < P_{\text{Rated}} \leq 38$ dBm and with standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2, 3) | Measurement bandwidth (Note 6) | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$
(Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $P_{\text{Rated,c}} - 36.5 \text{ dB} - 60(f\_offset/\text{MHz}-0.015) \text{ dB}$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $P_{\text{Rated,c}} - 39.5 \text{ dB} - 160(f\_offset/\text{MHz}-0.065) \text{ dB}$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.2.5.1-2c: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{Rated,c}} - 51.5 \text{ dB} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{Rated,c}} - 58.5 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{Rated,c}} - 60 \text{ dB}, -25 \text{ dBm})$ (Note 7) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $\min(P_{\text{Rated,c}} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.1-2b apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.5.1-2d: MR BS OBUE in BC1 bands $> 3$ GHz applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{Rated,c}} - 51.2 \text{ dB} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{Rated,c}} - 58.2 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{Rated,c}} - 60 \text{ dB}, -25 \text{ dBm})$ (Note 7) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $\min(P_{\text{Rated,c}} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.2.5.1-3: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm and not supporting NR; or BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-25.5 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-20.5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz | +| (Note 5) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -32.5 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -19.5 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -23.5 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -25 dBm (Note 7) | 1 MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -25dBm/MHz. + +NOTE2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.1-3b apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.5.1-3a: MR BS OBUE in BC1 bands $> 3$ GHz applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm and not supporting NR; or BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-25.2 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-20.2 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz | +| (Note 5) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -32.2 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -19.2 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -23.2 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -25 dBm (Note 7) | 1 MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -25dBm/MHz. + +NOTE2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 6.6.2.5.1-3b: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm BS and standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2, 3, 4) | Measurement bandwidth (Note 6) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$
(Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the RF bandwidth edge is a standalone NB-IoT carrier, the value of $X = P_{\text{NB-IoTCarrier}} - 31$ , where $P_{\text{NB-IoTCarrier}}$ is the power level of the standalone NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +**Table 6.6.2.5.1-3c: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-20.5 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -27.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm (Note 7) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -29dBm/100kHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.1-3b apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.5.1-3d: MR BS OBUE in BC1 bands $> 3$ GHz applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-20.2 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -27.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm (Note 7) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -29dBm/100kHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.2.5.1-4: LA BS OBUE in BC1 bands $\leq 3$ GHz** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -35.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 7) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -37dBm/100 kHz. + +NOTE2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.1-4b apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.5.1-4a: LA BS OBUE in BC1 bands $> 3$ GHz** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2) | Measurement bandwidth (Note 6) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -35.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 7) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -37dBm/100 kHz. + +NOTE2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.2.5.1-4b: LA BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2, 3, 4) | Measurement bandwidth (Note 6) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$
(Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.175 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a standalone NB-IoT carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the RF bandwidth edge is a standalone NB-IoT carrier, the value of $X = P_{\text{NB-IoTCarrier}} - 24$ , where $P_{\text{NB-IoTCarrier}}$ is the power level of the standalone NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +NOTE 5: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 6: As a general rule for the requirements in the present clause, 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 may 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. + +NOTE 7: The requirement is not applicable when $\Delta f_{\max} < \Delta f_{\text{OBUE}}$ . + +#### 6.6.2.5.2 Test requirements for Band Category 2 + +For a BS operating in Band Category 2 the requirement applies outside the Base Station RF Bandwidth edges. In addition, for a BS operating in non-contiguous spectrum, it applies inside any sub-block gap. + +Outside the Base Station RF Bandwidth edges, emissions shall not exceed the maximum levels specified in Table 6.6.2.5.2-1 to 6.6.2.5.2-8 below, where: + +- $\Delta f$ is the separation between the Base Station RF Bandwidth edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink operating band. +- $\Delta f_{\max}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +For a BS operating in multiple bands, inside any Inter RF Bandwidth gaps with $W_{\text{gap}} < 2 * \Delta f_{\text{OBUE}}$ , emissions shall not exceed the cumulative sum of the test requirements specified at the Base Station RF Bandwidth edges on each side of the Inter RF Bandwidth gap. The test requirement for Base Station RF Bandwidth edge is specified in Table 6.6.2.5.2-1 to 6.6.2.5.2-8 below, where in this case: + +- $\Delta f$ is the separation between the Base Station RF Bandwidth edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the Base Station RF Bandwidth edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is equal to the Inter RF Bandwidth gap minus half of the bandwidth of the measuring filter. +- $\Delta f_{\max}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +For a BS capable of multi-band operation where multiple bands are mapped on the same antenna connector and where there is no carrier transmitted in an operating band, the operating band unwanted emission limit, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{\max}$ ), of a band where there are no carriers transmitted shall apply from $\Delta f_{\text{OBUE}}$ below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the supported downlink operating band without any carrier transmitted. And no cumulative limits are applied in the inter-band gap between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted. + +Inside any sub-block gap for a BS operating in non-contiguous spectrum, emissions shall not exceed the cumulative sum of the test requirement specified for the adjacent sub blocks on each side of the sub block gap. The test requirement for each sub block is specified in Tables 6.6.2.5.2-1 to 6.6.2.5.2-8 below, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f_{\text{offset}}$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is equal to the sub block gap bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{\max}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +Applicability of Wide Area operating band unwanted emission requirements in Tables 6.6.2.5.2-1, 6.6.2.5.2-2a and 6.6.2.5.2-2b is specified in Table 6.6.2.5.2-0. + +Note: Option 1 and option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [5] and TS 38.104 [27]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [3] with GSM related modifications. + +**Table 6.6.2.5.2-0: Applicability of operating band unwanted emission requirements for BC2 Wide Area BS** + +| NR Band operation | Standalone NB-IoT carrier adjacent to the BS RF bandwidth edge or UTRA or GSM supported | Applicable requirement table | +|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------------| +| None | Y/N | 6.6.2.5.2-1 (option 2) | +| In certain regions (NOTE 2), bands 3, 8 | N | 6.6.2.5.2-1 (option 2) | +| Any | Y | 6.6.2.5.2-1 (option 2) | +| Any below 1GHz except for, in certain regions (NOTE 2), band 8 | N | 6.6.2.5.2-2a (option 1) | +| Any above 1GHz except for, in certain regions (NOTE 2), bands 3 | N | 6.6.2.5.2-2b (option 1) | + +NOTE 1: Void. +NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [13] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [5] and TS 38.104 [27] are applied. + +**Table 6.6.2.5.2-1: WA BS OBUE in BC2 bands - option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 2, 3) | Measurement bandwidth (Note 9) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-12.5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ (Note 4) | 30 kHz | +| (Note 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.5 dBm (Note 4) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -11.5 dBm (Note 4) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 4, 10) | 1 MHz | + +NOTE 1: For operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -15dBm/MHz (for MSR BS supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands <1GHz). + +NOTE3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ operation the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 4: For MSR BS supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands <1GHz. + +**Table 6.6.2.5.2-2: WA BS OBUE in BC2 bands applicable for: BS with GSM/EDGE or standalone NB-IoT or E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 2, 3, 4, 5) | Measurement bandwidth (Note 9) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{OBUE}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge is a GSM/EDGE carrier, the value of $X = P_{GSMcarrier} - 43$ , where $P_{GSMcarrier}$ is the power level of the GSM/EDGE carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. In other cases, $X = 0$ . + +NOTE 5: In case the carrier adjacent to the RF bandwidth edge is a NB-IoT carrier, the value of $X = P_{NB-IoTcarrier} - 43$ , where $P_{NB-IoTcarrier}$ is the power level of the NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +**Table 6.6.2.5.2-2a: WA BS OBUE in BC2 bands $\leq 1 \text{ GHz}$ - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 9) | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.5 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | $-12.5 \text{ dBm}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-16 \text{ dBm}$ (Note 10) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $-16 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{OBUE}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with an E-UTRA 1.4 or 3MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.2-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.5.2-2b: WA BS OBUE in BC2 bands $> 1 \text{ GHz}$ - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 9) | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.5 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | $-12.5 \text{ dBm}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-15 \text{ dBm}$ (Note 10) | 1MHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $-15 \text{ dBm}/1 \text{ MHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{OBUE}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with an E-UTRA 1.4 or 3MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.2-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.5.2-3: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm and not supporting NR; or BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm and supporting NR with UTRA and/or GSM** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 2, 3) | Measurement bandwidth (Note 9) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{Rated,c}} - 56.5 \text{ dB} - 7/5(f\_offset/\text{MHz}-0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{Rated,c}} - 51.5 \text{ dB} - 15(f\_offset/\text{MHz}-0.215) \text{ dB}$ | 30 kHz | +| (Note 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{Rated,c}} - 63.5 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | $P_{\text{Rated,c}} - 50.5 \text{ dB}$ | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.3 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{Rated,c}} - 50.5 \text{ dB}, -13.5 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | $P_{\text{Rated,c}} - 54.5 \text{ dB}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P_{\text{Rated,c}} - 56 \text{ dB}$ (Note 10) | 1 MHz | + +NOTE 1: For operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.2-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $(P_{\text{Rated,c}} - 56 \text{ dB})/\text{MHz}$ . + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 6.6.2.5.2-3a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm, supporting NR, not supporting UTRA, and not supporting GSM** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 9) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{Rated,c}} - 51.5 \text{ dB} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{Rated,c}} - 58.5 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{Rated,c}} - 60 \text{ dB}, -25 \text{ dBm})$ (Note 10) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $\min(P_{\text{Rated,c}} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.2-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.5.2-4: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm and not supporting NR; or BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm and supporting NR with UTRA and/or GSM** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 2, 3) | Measurement bandwidth (Note 9) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-25.5 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-20.5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz | +| (Note 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -32.5 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -19.5 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -23.5 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -25dBm (Note 10) | 1MHz | + +NOTE 1: For operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.2-6 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -25dBm/MHz. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +**Table 6.6.2.5.2-4a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm BS, supporting NR, not supporting UTRA, and not supporting GSM** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 9) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-20.5 \text{ dBm} - \frac{7}{5} (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -27.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -29 dBm (Note 10) | 100 kHz | + +NOTE 1: For MSR BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -29dBm/100kHz. + +NOTE 2: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with a standalone NB-IoT or an E-UTRA 1.4 or 3MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.2-6 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.2.5.2-5: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{Rated,c}} \leq 38$ dBm and with GSM/EDGE or E-UTRA 1.4 or 3 MHz carriers or standalone NB-IoT adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 2, 3) | Measurement bandwidth (Note 9) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $P_{\text{Rated,c}} - 36.5 \text{ dB} - 60(f\_offset/\text{MHz} - 0.015) \text{ dB}$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $P_{\text{Rated,c}} - 39.5 \text{ dB} - 160(f\_offset/\text{MHz} - 0.065) \text{ dB}$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a GSM/EDGE or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.2.5.2-6: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{Rated,c}} \leq 31$ dBm and with GSM/EDGE or E-UTRA 1.4 or 3 MHz carriers or standalone NB-IoT adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 2, 3, 4) | Measurement bandwidth (Note 9) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a GSM/EDGE or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge is a GSM/EDGE carrier, the value of $X = P_{\text{GSMcarrier}} - 31$ , where $P_{\text{GSMcarrier}}$ is the power level of the GSM/EDGE carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. In other cases, $X = 0$ . + +NOTE 5: In case the carrier adjacent to the RF bandwidth edge is a NB-IoT carrier, the value of $X = P_{\text{NB-IoTcarrier}} - 31$ , where $P_{\text{NB-IoTcarrier}}$ is the power level of the NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +**Table 6.6.2.5.2-7: LA BS OBUE in BC2 bands** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 2, 3) | Measurement bandwidth (Note 9) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ (Note 1) | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -35.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 10) | 100 kHz | + +NOTE 1: For operation with a GSM/EDGE or standalone NB-IoT or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.6.2.5.2-8 apply for $0 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ . + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -37dBm/100 kHz. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +**Table 6.6.2.5.2-8: LA BS OBUE in in BC2 bands applicable for: BS with GSM/EDGE or E-UTRA 1.4 or 3 MHz carriers or standalone NB-IoT adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 2, 3, 4) | Measurement bandwidth (Note 9) | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.175 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with a GSM/EDGE or an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. + +NOTE 2: For MSR BS supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 4: In case the carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge is a GSM/EDGE carrier, the value of $X = P_{\text{GSMcarrier}} - 24$ , where $P_{\text{GSMcarrier}}$ is the power level of the GSM/EDGE carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge. In other cases, $X = 0$ . + +NOTE 5: In case the carrier adjacent to the RF bandwidth edge is a NB-IoT carrier, the value of $X = P_{\text{NB-IoTcarrier}} - 24$ , where $P_{\text{NB-IoTcarrier}}$ is the power level of the NB-IoT carrier adjacent to the RF bandwidth edge. In other cases, $X = 0$ . + +NOTE 8: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 9: As a general rule for the requirements in the present clause, 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 may 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. + +NOTE 10: The requirement is not applicable when $\Delta f_{\max} < \Delta f_{\text{OBUE}}$ . + +### 6.6.2.5.3 Test requirements for GSM/EDGE single-RAT requirements + +The following test requirements and the corresponding test method specified in TS 51.021 [11] apply to an MSR Base Station for any operating band with GSM/EDGE single RAT operation in Band Category 2: + +- Spectrum due to the modulation and wide band noise, applicable parts of clause 6.5.1. + +- Spectrum due to switching transients, applicable parts of clause 6.5.2. +- Emission requirement for frequency offsets of between 2 and 10 MHz outside relevant transmit band, applicable parts of clause 6.6.2. +- Intra BTS Intermodulation, applicable parts of clause 6.12. + +#### 6.6.2.5.4 Test requirements for additional requirements + +##### 6.6.2.5.4.1 Limits in FCC Title 47 + +In addition to the requirements in clauses 6.6.2.5.1 and 6.6.2.5.2, the BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +##### 6.6.2.5.4.2 Unsynchronized operation for BC3 + +In certain regions, the following requirements may apply to a TDD BS operating in BC3 in the same geographic area and in the same operating band as another TDD system without synchronisation. For this case the emissions shall not exceed -52 dBm/MHz in each supported downlink operating band except in: + +- The frequency range from 10 MHz below the lower Base Station RF Bandwidth edge to the frequency 10 MHz above the upper Base Station RF Bandwidth edge of each supported band. + +NOTE 1: Local or regional regulations may specify another excluded frequency range, which may include frequencies where synchronised TDD systems operate. + +NOTE 2: TDD Base Stations that are synchronized and operating in BC3 can transmit without these additional co-existence requirements. + +NOTE 3: Unsynchronized operation for BC3 BS with any NR configuration is FFS. + +##### 6.6.2.5.4.3 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For a BS operating in Band 20, the level of emissions in the band 470-790 MHz, measured in an 8 MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to Table 6.6.2.5.4.3-1, shall not exceed the maximum emission level $P_{\text{EM,N}}$ declared by the manufacturer. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 6.6.2.5.4.3-1: Declared emissions levels for protection of DTT** + +| Filter centre frequency,
$F_{\text{filter}}$ | 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 BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the Base Station needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in Annex G of TS 36.104 [5]. + +##### 6.6.2.5.4.4 Void + +**Table 6.6.2.5.4.4-1: Void** + +## 6.6.2.5.4.5 Void + +**Table 6.6.2.5.4.5-1: Void** + +## 6.6.2.5.4.6 Additional band 32, 50, 51, 74, 75 and 76 unwanted emissions + +In certain regions, the following requirements may apply to BS operating in Band 32 within 1452-1492 MHz, in Band 75 within 1432-1517 MHz and in Band 76 within 1427-1432 MHz. The level of operating band unwanted emissions, measured on centre frequencies $f\_offset$ with filter bandwidth, according to Table 6.6.2.5.4.6-1, shall neither exceed the maximum emission level $P_{EM,B32,B75,B76,a}$ , $P_{EM,B32,B75,B76,b}$ nor $P_{EM,B32,B75,B76,c}$ declared by the manufacturer. + +For Band 32, this requirement applies in the frequency range 1452-1492 MHz when non-Mobile/Fixed Communications Network (MFCN) services are deployed in adjacent frequency ranges, while it applies also within 1427-1452 MHz and/or 1492-1517 MHz when MFCN services are deployed in such frequency ranges, even though part of the ranges falls in the spurious domain. For Band 75, this requirement applies in the frequency range 1427-1517 MHz. For Band 76, this requirement applies in the frequency range 1432-1517 MHz even though part of the range falls in the spurious domain. + +**Table 6.6.2.5.4.6-1: Declared operating band 32, 75 and 76 unwanted emission within 1427-1517 MHz** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Declared emission level [dBm] | Measurement bandwidth | +|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| 2.5 MHz | $P_{EM,B32,B75,B76,a}$ | 5 MHz | +| 7.5 MHz | $P_{EM,B32,B75,B76,b}$ | 5 MHz | +| $12.5 \text{ MHz} \leq f\_offset \leq f\_offset_{max}$ | $P_{EM,B32,B75,B76,c}$ | 5 MHz | +| NOTE: | For Band 32, when non-MFCN services are deployed in the adjacent bands, $f\_offset_{max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1454.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1489.5 MHz for the set channel position. For Band 32, when MFCN services are deployed in the adjacent frequencies, Band 75 and Band 76, $f\_offset_{max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1429.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1514.5 MHz for the set channel position | | + +NOTE: The regional requirement, included in [25], is defined in terms of EIRP per antenna, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS 36.104 [5]. + +In certain regions, the following requirement may apply to BS operating in Band 32 within 1452-1492 MHz for the protection of non-MFCN services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{filter}$ with filter bandwidth according to Table 6.6.2.5.4.6-2, shall neither exceed the maximum emission level $P_{EM,B32,d}$ nor $P_{EM,B32,e}$ declared by the manufacturer. This requirement applies in the frequency range 1429-1518 MHz even though part of the range falls in the spurious domain. + +**Table 6.6.2.5.4.6-2: Operating band 32 declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{filter}$ | Declared emission level [dBm] | Measurement bandwidth | +|--------------------------------------------------------------|-------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{filter} \leq 1448.5 \text{ MHz}$ | $P_{EM,B32,d}$ | 1 MHz | +| $F_{filter} = 1450.5 \text{ MHz}$ | $P_{EM,B32,e}$ | 3 MHz | +| $F_{filter} = 1493.5 \text{ MHz}$ | $P_{EM,B32,e}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{filter} \leq 1517.5 \text{ MHz}$ | $P_{EM,B32,d}$ | 1 MHz | + +NOTE: The regional requirement, included in [24], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS 36.104 [5]. + +In certain regions, the following requirement may apply to BS operating in Band 50 and Band 75 within 1492-1517 MHz and in Band 74 within 1492-1518 MHz. The level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to Table 6.6.2.5.4.6-3, shall neither exceed the maximum emission level $P_{\text{EM,B50,B74,B75,a}}$ nor $P_{\text{EM,B50,B74,B75,b}}$ declared by the manufacturer. + +**Table 6.6.2.5.4.6-3: Operating band 50, 74 and 75 declared emission above 1518 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission level [dBm] | Measurement bandwidth | +|---------------------------------------------------------------------|-------------------------------|-----------------------| +| $1518.5 \text{ MHz} \leq F_{\text{filter}} \leq 1519.5 \text{ MHz}$ | $P_{\text{EM,B50,B74,B75,a}}$ | 1 MHz | +| $1520.5 \text{ MHz} \leq F_{\text{filter}} \leq 1558.5 \text{ MHz}$ | $P_{\text{EM,B50,B74,B75,b}}$ | 1 MHz | + +NOTE: The regional requirement, included in [25], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H. + +In certain regions, the following requirement may apply to E-UTRA or NR BS operating in Band 50 and Band 75 within 1432-1452 MHz, and in Band 51 and Band 76. Emissions shall not exceed the maximum levels specified in Table 6.6.2.5.4.6-4. + +**Table 6.6.2.5.4.6-4: Additional operating band unwanted emission limits for BS operating in Band 50 and 75 within 1432-1452 MHz, and in Band 51 and 76** + +| Filter centre frequency, $F_{\text{filter}}$ | Maximum Level [dBm] | Measurement Bandwidth | +|----------------------------------------------|---------------------|-----------------------| +| $F_{\text{filter}} = 1413.5 \text{ MHz}$ | -42 | 27 MHz | + +#### 6.6.2.5.4.7 Additional requirements for band 48 + +The following requirement may apply to BS operating in Band 48 in certain regions. Emissions shall not exceed the maximum levels specified in Table 6.6.2.4.9-1. + +**Table 6.6.2.5.4.7-1: Additional operating band unwanted emission limits for Band 48** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Minimum requirement | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|------------------------------------------------------------------------------|---------------------|-----------------------| +| All | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f_{\text{offset}} < 9.5 \text{ MHz}$ | -13 dBm | 1 MHz | + +#### 6.6.2.5.4.8 Additional requirements for band 53 + +The following requirement may apply to BS operating in Band 53 in certain regions. Emissions shall not exceed the maximum levels specified in Table 6.6.2.5.4.8-1. + +**Table 6.6.2.5.4.8-1: Additional operating band unwanted emission limits for Band 53** + +| Channel bandwidth [MHz] | Frequency range [MHz] | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth | +|-------------------------|-----------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| 1.4, 3, 5 | 2400 - 2477.5 | $6 \text{ MHz} \leq \Delta f < 83.5 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 83 \text{ MHz}$ | -25 dBm | 1 MHz | +| 10 | 2400 - 2473.5 | $10 \text{ MHz} \leq \Delta f < 83.5 \text{ MHz}$ | $10.5 \text{ MHz} \leq f\_offset < 83 \text{ MHz}$ | -25 dBm | 1 MHz | +| 1.4, 3, 5 | 2477.5 - 2478.5 | $5 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $5.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| 10 | 2473.5 - 2478.5 | $5 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $5.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| All | 2478.5 - 2483.5 | $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 4.5 \text{ MHz}$ | -10 dBm | 1 MHz | +| 1.4, 3, 5 | 2495 - 2501 | $0 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| 10 | 2495 - 2505 | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| 1.4, 3, 5 | 2501 - 2690 | $6 \text{ MHz} \leq \Delta f < 195 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 194.5 \text{ MHz}$ | -25 dBm | 1 MHz | +| 10 | 2505 - 2690 | $10 \text{ MHz} \leq \Delta f < 195 \text{ MHz}$ | $10.5 \text{ MHz} \leq f\_offset < 194.5 \text{ MHz}$ | -25 dBm | 1 MHz | + +## 6.6.3 Occupied bandwidth + +### 6.6.3.1 Definition and applicability + +The occupied bandwidth is the width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage $\beta/2$ of the total mean transmitted power. See also ITU-R Recommendation SM.328 [15]. + +The value of $\beta/2$ shall be taken as 0.5%. + +### 6.6.3.2 Minimum requirements + +The minimum requirement is in TS 37.104 [2] clause 6.6.3. + +### 6.6.3.3 Test purpose + +The occupied bandwidth, defined in the Radio Regulations of the International Telecommunication Union ITU, is a useful concept for specifying the spectral properties of a given emission in the simplest possible manner; see also ITU-R Recommendation SM.328 [15]. The test purpose is to verify that the emission of the BS does not occupy an excessive bandwidth for the service to be provided and is, therefore, not likely to create interference to other users of the spectrum beyond undue limits. + +### 6.6.3.4 Method of test + +For this requirement Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5. The following shall apply: + +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 6.5.1.4. +- For references to TS 25.142 [12], the method of test is specified in TS 25.142 [12], clause 6.6.1.4. +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 6.6.1.4. +- For references to TS 38.141-1 [26], the method of test is specified in TS 38.141-1 [26], clause 6.6.2.4. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band where single carrier test models shall apply, with no carrier activated in the other band. In addition, when contiguous CA is supported, single band test configurations and test models shall apply with no carrier activated in the other band. +- For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +### 6.6.3.5 Test requirement + +The occupied bandwidth of a single carrier shall be less than the values listed in Table 6.6.3.5-1. For E-UTRA intra-band contiguous carrier aggregation, test requirement in clause 6.6.1.5 of TS 36.141 [9] applies for the E-UTRA component carriers that are aggregated. For NR intra-band contiguous carrier aggregation, test requirement in clause 6.6.2.5 of TS 38.141-1 [26] applies for the NR component carriers that are aggregated. + +**Table 6.6.3.5-1: Occupied bandwidth** + +| RAT | Occupied bandwidth limit | +|--------------------|--------------------------| +| E-UTRA and NR | BW channel | +| UTRA FDD | 5 MHz | +| 1.28 Mcps UTRA TDD | 1.6 MHz | +| NB-IoT | 200 kHz | + +## 6.6.4 Adjacent Channel Leakage Power Ratio (ACLR) + +### 6.6.4.1 Definition and applicability + +Adjacent Channel Leakage Power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. + +### 6.6.4.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.6.4. + +### 6.6.4.3 Test purpose + +To verify that the adjacent channel leakage power ratio requirement shall be met as specified by the minimum requirement. + +### 6.6.4.4 Method of test + +For this requirement Tables 5.1-1 and 5.2-1 also refer to single-RAT specifications for UTRA; see clause 5. The following shall apply for references to UTRA single-RAT specifications: + +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 6.5.2.2.4. +- For references to TS 25.142 [12], the method of test is specified in TS 25.142 [12], clause 6.6.2.2.4. + +For NR and E-UTRA ACLR requirement outside the Base Station RF Bandwidth edges and the ACLR requirement applied inside sub-block gap, in addition, for non-contiguous spectrum operation or Inter RF Bandwidth gap for multi-band operation using, the test configurations defined in clause 4.8, the method of test described in clauses 6.6.4.4.1 and 6.6.4.4.2 applies. + +#### 6.6.4.4.1 Initial conditions + +Test environment: normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: BRFBW, MRFBW and TRFBW in single-band operation; see clause 4.9.1; BRFBW\_TRFBW and B'RFBW\_TRFBW in multi-band operation, see clause 4.9.1. + +- 1) Connect the signal analyzer to the Base Station antenna connector as shown in Annex D.1.1. +- 2) The measurement device characteristics shall be: + - measurement filter bandwidth: defined in clause 6.6.4.5; + - detection mode: true RMS voltage or true average power. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2-1. + +#### 6.6.4.4.2 Procedure + +- 1) Set the Base Station to transmit at maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.9.2. +- 2) For E-UTRA with NB-IoT (in-band and/or guard band operation), measure ACLR outside the Base Station RF Bandwidth edges and ACLR inside sub-block gap or Inter RF Bandwidth gap, in addition, for non-contiguous spectrum operation as specified in clause 6.6.4.5.1. For NB-IoT stand-alone operation, measure ACLR as specified in clause 6.6.4.5.5. For NR, measure ACLR outside the Base Station RF Bandwidth edges and ACLR inside sub-block gap or Inter RF Bandwidth gap, in addition, for non-contiguous spectrum operation as specified in clause 6.6.4.5.6. +- 3) For UTRA FDD, measure ACLR inside sub-block gap or Inter RF Bandwidth gap as specified in clause 6.6.4.5.2. +- 4) Measure Cumulative Adjacent Channel Leakage Power Ratio (CACLR) inside sub-block gap or the Inter RF Bandwidth gap as specified in clause 6.6.4.5.4. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 5) For multi-band capable BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of SBT or MBT shall be terminated. + +#### 6.6.4.5 Test requirements + +##### 6.6.4.5.1 E-UTRA test requirement + +For E-UTRA, the test requirement is specified in Tables 6.6.4.5.1-1 and 6.6.4.5.1-2, and applies outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. + +For a BS operating in non-contiguous spectrum, the ACLR also applies for the first adjacent channel inside any sub-blockgap with a gap size $W_{\text{gap}} \geq 15\text{MHz}$ . The ACLR requirement for the second adjacent channel applies inside any sub-block gap with a gap size $W_{\text{gap}} \geq 20\text{ MHz}$ . The CACLR test requirement in clause 6.6.4.5.4 applies in sub block gaps for the frequency ranges defined in Table 6.6.4.5.4-1. + +For a BS operating in multiple bands, where multiple bands are mapped onto the same antenna connector, the ACLR also applies for the first adjacent channel inside any Inter RF Bandwidth gap with a gap size $W_{\text{gap}} \geq 15\text{MHz}$ . The ACLR requirement for the second adjacent channel applies inside any Inter RF Bandwidth gap with a gap size $W_{\text{gap}} \geq 20\text{ MHz}$ . The CACLR requirement in clause 6.6.4.5.4 applies in Inter RF Bandwidth gaps for the frequency ranges defined in Table 6.6.4.5.4-1. + +The requirement applies during the transmitter on period. + +The ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal ( $BW_{\text{Config}}$ ) centred on the assigned channel frequency and a filter centered on the adjacent channel frequency according to the tables below. + +For Category A Wide Area BS, either the ACLR limits in the tables below or the absolute limit of -13dBm/MHz shall apply, whichever is less stringent. + +For Category B Wide Area BS, either the ACLR limits in the tables below or the absolute limit of -15 dBm/MHz shall apply, whichever is less stringent. + +For Medium Range BS, either the ACLR limits in the tables below or the absolute limit of -25 dBm/MHz shall apply, whichever is less stringent. + +For Local Area BS, either the ACLR limits in the tables below or the absolute limit of -32dBm/MHz shall apply, whichever is less stringent. + +For operation in paired spectrum, the ACLR shall be higher than the value specified in Table 6.6.4.5.1-1. + +**Table 6.6.4.5.1-1: Base Station ACLR in paired spectrum** + +| Channel bandwidth of E-UTRA Lowest/Highest Carrier transmitted $BW_{Channel}$ [MHz] | BS adjacent channel centre frequency offset below the lower or above the upper Base Station RF Bandwidth edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| 1.4, 3.0, 5, 10, 15, 20 | 0.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44.2 dB | +| | 1.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44.2 dB | +| | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [3], with a chip rate as defined in this table. + +For operation in unpaired spectrum, the ACLR shall be higher than the value specified in Table 6.6.4.5.1-2. + +**Table 6.6.4.5.1-2: Base Station ACLR in unpaired spectrum with synchronized operation** + +| Channel bandwidth of E-UTRA Lowest/Highest Carrier transmitted $BW_{Channel}$ [MHz] | BS adjacent channel centre frequency offset below the lower or above the upper Base Station RF Bandwidth edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| 1.4, 3 | 0.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44.2 dB | +| | 1.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44.2 dB | +| | 0.8 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| | 2.4 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| 5, 10, 15, 20 | 0.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44.2 dB | +| | 1.5 x $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44.2 dB | +| | 0.8 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| | 2.4 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| | 5 MHz | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 44.2 dB | +| | 15 MHz | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 44.2 dB | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.105 [4], with a chip rate as defined in this table. + +For operation in non-contiguous paired spectrum, the ACLR shall be higher than the value specified in Table 6.6.4.5.1-3. + +**Table 6.6.4.5.1-3: Base Station ACLR in non-contiguous paired spectrum** + +| Sub-block gap size ( $W_{gap}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|----------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| $W_{gap} \geq 15$ MHz | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| $W_{gap} \geq 20$ MHz | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | + +NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [3], with a chip rate as defined in this table. + +For operation in non-contiguous unpaired spectrum, the ACLR shall be higher than the value specified in Table 6.6.4.5.1-4. + +**Table 6.6.4.5.1-4: Base Station ACLR in non-contiguous unpaired spectrum** + +| Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| $W_{\text{gap}} \geq 15$ MHz | 2.5 MHz | 5MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| $W_{\text{gap}} \geq 20$ MHz | 7.5 MHz | 5MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | + +#### 6.6.4.5.2 UTRA FDD test requirement + +For UTRA FDD, the test requirement is specified in TS 25.141 [10] clause 6.5.2.2.5, and applies outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. + +For a BS operating in non-contiguous spectrum, ACLR requirement also applies for the first adjacent channel, inside any sub-block gap with a gap size $W_{\text{gap}} \geq 15$ MHz. The ACLR requirement for the second adjacent channel applies inside any sub-block gap with a gap size $W_{\text{gap}} \geq 20$ MHz. The CACLR test requirement in clause 6.6.4.5.4 applies in sub block gaps for the frequency ranges defined in Table 6.6.4.5.4-1. + +For a BS operating in multiple bands, where multiple bands are mapped onto the same antenna connector, ACLR requirement also applies for the first adjacent channel, inside any Inter RF Bandwidth gap with a gap size $W_{\text{gap}} \geq 15$ MHz. The ACLR requirement for the second adjacent channel applies inside any Inter RF Bandwidth gap with a gap size $W_{\text{gap}} \geq 20$ MHz. The CACLR requirement in clause 6.6.4.5.4 applies in Inter RF Bandwidth gaps for the frequency ranges defined in Table 6.6.4.5.4-1. + +#### 6.6.4.5.3 UTRA TDD test requirement + +For UTRA TDD, the test requirement is specified in TS 25.142 [12] clause 6.6.2.2.5, and applies outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. + +#### 6.6.4.5.4 Cumulative ACLR requirement in non-contiguous spectrum + +The following test requirement applies for sub-block or Inter RF Bandwidth gap sizes listed in Table 6.6.4.5.4-1, + +- Inside a sub-block gap within an operating band for a BS operating in non-contiguous spectrum. +- Inside an Inter RF Bandwidth gap for a BS operating in multiple bands, where multiple bands are mapped on the same antenna connector. + +The Cumulative Adjacent Channel Leakage Power Ratio (CACLR) in a sub-block gap or the Inter RF Bandwidth gap is the ratio of + +- a) the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the sub-block gap or the Inter RF Bandwidth gap, and +- b) the filtered mean power centred on a frequency channel adjacent to one of the respective sub-block edges or Base Station RF Bandwidth edges. + +The requirement applies to adjacent channels of NR, E-UTRA or UTRA carriers allocated adjacent to each side of the sub-block gap or the Inter RF Bandwidth gap. The assumed filter for the adjacent channel frequency is defined in Table 6.6.4.5.4-1 and the filters on the assigned channels are defined in Table 6.6.4.5.4-2. + +NOTE: If the RAT on the assigned channel frequencies is different, the filters used are also different. + +For Wide Area Category A BS, either the CACLR limits in Table 6.6.4.5.4-1 or the absolute limit of -13dBm/MHz shall apply, whichever is less stringent. + +For Wide Area Category B BS, either the CACLR limits in Table 6.6.4.5.4-1 or the absolute limit of -15dBm/MHz shall apply, whichever is less stringent. + +For Medium Range BS, either the CACLR limits in Table 6.6.4.4-1 or the absolute limit of -25 dBm/MHz shall apply, whichever is less stringent. + +For Local Area BS, either the CACLR limits in Table 6.6.4.4-1 or the absolute limit of -32 dBm/MHz shall apply, whichever is less stringent. + +The CACLR for E-UTRA and UTRA carriers located on either side of the sub-block gap or the Inter RF Bandwidth gap shall be higher than the value specified in Table 6.6.4.5.4-1. + +**Table 6.6.4.5.4-1: Base Station CACLR in non-contiguous spectrum or multiple bands** + +| Band Category | Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies (MHz) | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|---------------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------| +| BC1, BC2 | $5 \leq W_{\text{gap}} < 15$ (Note 3) | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| BC1, BC2 | $10 \leq W_{\text{gap}} < 20$ (Note 3) | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| BC3 | $5 \leq W_{\text{gap}} < 15$ (Note 3) | 2.5 MHz | 5MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| BC3 | $10 < W_{\text{gap}} < 20$ (Note 3) | 7.5 MHz | 5MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| BC1, BC2, BC3 | $5 \leq W_{\text{gap}} < 45$ (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| BC1, BC2, BC3 | $10 \leq W_{\text{gap}} < 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| BC1, BC2, BC3 | $20 \leq W_{\text{gap}} < 30$ (Note 3, 5) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| BC1, BC2, BC3 | $20 \leq W_{\text{gap}} < 60$ (Note 4) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| BC1, BC2, BC3 | $40 \leq W_{\text{gap}} < 50$ (Note 3, 5) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| BC1, BC2, BC3 | $40 \leq W_{\text{gap}} < 80$ (Note 4) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | + +NOTE 1: For BC1 and BC2 the RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [3], with a chip rate as defined in this table. + +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{\text{Config}}$ ). + +NOTE 3: Applicable in case the *channel bandwidth* of the carrier transmitted at the other edge of the gap is 5, 10, 15, 20 MHz. + +NOTE 4: Applicable in case the *channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 25, 30, 40, 50, 60, 70, 80, 90, 100 MHz. + +NOTE 5: Applicable in case the *channel bandwidth* of the NR carrier transmitted adjacent to sub-block gap or inter RF Bandwidth gap is 25, 30, 40, 50, 60, 70, 80, 90, 100 MHz. + +**Table 6.6.4.5.4-2: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the sub-block or Inter RF Bandwidth gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| E-UTRA | E-UTRA of same BW | +| UTRA FDD | RRC (3.84 Mcps) | +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | +| NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [3], with a chip rate as defined in this table. | | + +#### 6.6.4.5.5 NB-IoT test requirement + +For NB-IoT in-band and guard band operation, the E-UTRA minimum requirement specified in clause 6.6.4.5.1 shall apply. + +For NB-IoT operation in NR in-band, the NR minimum requirement specified in clause 6.6.4.5.6 shall apply. + +For NB-IoT standalone operation, the ACLR shall be higher than the value specified in Table 6.6.4.5.5-1. + +**Table 6.6.4.5.5-1: Base Station ACLR for NB-IoT standalone operation** + +| Channel bandwidth of standalone NB-IoT lowest/highest carrier transmitted $BW_{\text{Channel}}$ | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| 200 kHz | 300 kHz | Standalone NB-IoT | Square ( $BW_{\text{Config}}$ ) | 39.2 dB | +| | 500 kHz | Standalone NB-IoT | Square ( $BW_{\text{Config}}$ ) | 49.2 dB | + +NOTE 1: $BW_{\text{Config}}$ is the transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. + +#### 6.6.4.5.6 NR test requirement + +For NR, the requirements shall apply outside the Base Station RF Bandwidth or Radio Bandwidth whatever the type of transmitter considered (single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification. + +For a BS operating in non-contiguous spectrum, the ACLR requirement shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.4.5.6-2a, while the CACLR requirement shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.4.5.4-1. + +For BS operating in multiple bands, where multiple bands are mapped onto the same *antenna connector*, the ACLR requirement shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.4.5.6-2a, while the CACLR requirement in clause 6.6.4.5.4 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.4.5.4-1. + +The requirement shall apply during the *transmitter ON period*. The ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal ( $BW_{\text{Config}}$ ) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +The ACLR absolute *limit* in table 6.6.4.5.6-2 or the ACLR (CACLR) *limit* in table 6.6.4.5.6-1, 6.6.4.5.6-2a or 6.6.4.5.4-1, whichever is less stringent, shall apply for each *antenna connector*. + +For Band 41 operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all *antenna connectors*. + +For operation in paired and unpaired spectrum, the ACLR shall be higher than the value specified in table 6.6.4.5.6-1. + +**Table 6.6.4.5.6-1: Base station ACLR limit** + +| Channel bandwidth of lowest/highest NR carrier transmitted BW_{Channel} [MHz] | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|---------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | +| | $2 \times BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | +| | $BW_{Channel}/2 + 2.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 44.2 dB (Note 3) | +| | $BW_{Channel}/2 + 7.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 44.2 dB (Note 3) | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the *channel bandwidth* and transmission bandwidth configuration of the lowest/highest NR carrier transmitted on the assigned channel frequency. +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). +NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. + +The ACLR absolute limit is specified in table 6.6.4.5.6-2. + +**Table 6.6.4.5.6-2: Base station ACLR absolute limit** + +| BS category / BS class | ACLR absolute limit | +|-------------------------------|----------------------------| +| Category A Wide Area BS | -13 dBm/MHz | +| Category B Wide Area BS | -15 dBm/MHz | +| Medium Range BS | -25 dBm/MHz | +| Local Area BS | -32 dBm/MHz | + +For operation in non-contiguous spectrum or multiple bands, the ACLR shall be higher than the value specified in Table 6.6.4.5.6-2a. + +**Table 6.6.4.5.6-2a: Base Station ACLR limit in non-contiguous spectrum or multiple bands** + +| Channel bandwidth of NR carrier transmitted adjacent to sub-block gap or inter RF Bandwidth gap BW_{Channel} [MHz] | Sub-block or Inter RF Bandwidth gap size (W_{gap}) where the limit applies [MHz] | BS adjacent channel centre frequency offset below or above the sub-block or Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 5, 10, 15, 20 | $W_{gap} \geq 15$ (Note 3)
$W_{gap} \geq 45$ (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | +| | $W_{gap} \geq 20$ (Note 3)
$W_{gap} \geq 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $W_{gap} \geq 60$ (Note 4)
$W_{gap} \geq 30$ (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | +| | $W_{gap} \geq 80$ (Note 4)
$W_{gap} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | + +NOTE 1: $BW_{Config}$ is the transmission bandwidth configuration of the assumed adjacent channel carrier. +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). +NOTE 3: Applicable in case the *channel bandwidth* of the carrier transmitted at the other edge of the gap is 5, 10, 15, 20 MHz. +NOTE 4: Applicable in case the *channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 MHz. + +## 6.7 Transmitter intermodulation + +### 6.7.1 Definition and applicability + +The transmitter intermodulation requirement is a measure of the capability of the transmitter to inhibit the generation of signals in its nonlinear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. The requirement applies during the transmitter ON period and the transmitter transient period. The transmitter intermodulation level is the power of the intermodulation products when an interfering signal is injected into the antenna connector. + +For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply regardless of the interfering signals position relative to the Inter RF Bandwidth gap. + +In case the test signal in clause 5 refer to single-RAT specifications following shall apply: + +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 6.6.4. +- For references to TS 25.142 [12], the method of test is specified in TS 25.142 [12], clause 6.7.4. +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 6.7.4. +- For references to TS 38.141-1 [26], the method of test is specified in TS 38.141-1 [26], clause 6.7.4. + +NOTE: In this case the test requirements of the present document defined in clauses 6.6.2.5 and 6.6.4.5 apply. + +- For GSM/EDGE single-RAT requirements, the method of test is specified in TS 51.021 [11], applicable parts of clauses 6.7 and 6.11. + +NOTE: In this case the test requirements of 51.021 [11] defined in the applicable clauses 6.7.3, 6.7.4, 6.11.3 and 6.11.4 apply. + +### 6.7.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 6.7.1, 6.7.2 and 6.7.3. + +### 6.7.2A Additional requirement for Band 41 + +The additional requirement for Band 41 in certain regions is in TS 37.104 [2] clause 6.7.4. + +### 6.7.3 Test purpose + +The test purpose is to verify the ability of the MSR BS transmitter to restrict the generation of intermodulation products in its nonlinear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna to below specified levels. + +### 6.7.4 Method of test + +#### 6.7.4.1 Initial conditions + +Test environment: normal; see Annex B.2. + +Base Station RF Bandwidth position to be tested: according to the initial conditions specified in clauses 6.6.1, 6.6.2 and 6.6.4. + +Connect the signal analyzer to the Base Station antenna connector as shown in Annex D.1.2. + +## 6.7.4.2 Procedure + +### 6.7.4.2.1 General minimum requirement test procedure + +- 1) Set the BS to transmit the test signal according to clause 5 at maximum output power according to the applicable test configuration. +- 2) Generate the interfering signal using E-TM1.1 as defined in TS 36.141 [9] clause 6.1.1.1, with 5 MHz channel bandwidth, at a centre frequency offset according to the conditions in Table 6.7.1-1 in TS 37.104 [2], but exclude interfering frequencies that are outside of the allocated downlink operating band or interfering frequencies that are not completely within the sub-block gap or within the Inter RF Bandwidth gap. +- 3) Adjust ATT1 so that level of the E-UTRA interfering signal is as defined in Table 6.7.1-1 in TS 37.104 [2]. +- 4) If the test signal is applicable according to clause 5, perform the Out-of-band emission tests as specified in clauses 6.6.2 and 6.6.4, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clauses 6.6.2 and 6.6.4. The width of the intermodulation products shall be taken into account. +- 5) If the test signal is applicable according to clause 5, perform the Transmitter spurious emissions test as specified in clause 6.6.1, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clause 6.6.1. The width of the intermodulation products shall be taken into account. +- 6) Verify that the emission level does not exceed the required level with the exception of interfering signal frequencies. +- 7) Repeat the test for the remaining interfering signal centre frequency offsets according to the conditions of Table 6.7.1-1 in TS 37.104 [2]. +- 8) Repeat the test for the remaining test signals defined in clause 5 for requirements 6.6.1, 6.6.2 and 6.6.4. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 9) For multi-band capable BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +NOTE: The third order intermodulation products are centred at $2F1 \pm F2$ and $2F2 \pm F1$ . The fifth order intermodulation products are centred at $3F1 \pm 2F2$ , $3F2 \pm 2F1$ , $4F1 \pm F2$ , and $4F2 \pm F1$ where $F1$ represents the test signal centre frequency or centre frequency of each sub-block and $F2$ represents the interfering signal centre frequency. The widths of intermodulation products are + +$$(n * BW_{F1} + m * 5\text{MHz}) \text{ for the } nF1 \pm mF2 \text{ products}$$ + +$$(n * 5\text{MHz} + m * BW_{F1}) \text{ for the } nF2 \pm mF1 \text{ products}$$ + +where $BW_{F1}$ represents the test signal RF bandwidth, or channel bandwidth in case of single carrier, or sub-block bandwidth. + +### 6.7.4.2.2 Additional minimum requirement (BC1 and BC2) test procedure + +- 1) Set the BS to transmit the test signal according to clause 5 at maximum output power according to the applicable test configuration. +- 2) Generate a CW signal as the interfering signal with a centre frequency offset of 0.8 MHz, but exclude interfering frequencies that are outside of the allocated downlink operating band or interfering frequencies in a sub-block gap or in the Inter RF Bandwidth gap, in case the gap is smaller than two times the interfering signal centre frequency offset. +- 3) Adjust ATT1 so that level of the interfering signal is as defined in Table 6.7.2-1 in TS 37.104 [2]. +- 4) If the test signal is applicable according to clause 5, perform the Out-of-band emission tests as specified in clauses 6.6.2 and 6.6.4, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clauses 6.6.2 and 6.6.4. + +- 5) If the test signal is applicable according to clause 5, perform the Transmitter spurious emissions test as specified in clause 6.6.1, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clause 6.6.1. +- 6) Verify that the emission level does not exceed the required level with the exception of interfering signal frequencies. +- 7) Repeat the test for interfering signal centre frequency offsets of 2.0MHz, 3.2MHz and 6.2MHz. +- 8) Repeat the test for the remaining test signals defined in clause 5 for requirements 6.6.1, 6.6.2 and 6.6.4. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 9) For multi-band capable BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +NOTE: The third order intermodulation products are centred at $2F1 \pm F2$ and $2F2 \pm F1$ . The fifth order intermodulation products are centred at $3F1 \pm 2F2$ , $3F2 \pm 2F1$ , $4F1 \pm F2$ , and $4F2 \pm F1$ where F1 represents the test signal centre frequency or centre frequency of each sub-block and F2 represents the interfering signal centre frequency. The widths of intermodulation products are + +$(n * BW_{F1})$ for the $nF1 \pm mF2$ products + +$(m * BW_{F1})$ for the $nF2 \pm mF1$ products + +where $BW_{F1}$ represents the test signal RF bandwidth, or channel bandwidth in case of single carrier, or sub-block bandwidth. + +#### 6.7.4.2.3 Additional minimum requirement (BC3) test procedure + +- 1) Set the BS to transmit the test signal according to clause 5 at maximum output power according to the applicable test configuration. +- 2) Generate the interfering signal according to Table 6.38A in TS 25.142 [12] at a centre frequency offset according to the conditions in Table 6.7.3-1 in TS 37.104 [2], but exclude interfering frequencies that are outside of the allocated downlink operating band. +- 3) Adjust ATT1 so that level of the interfering signal is as defined in Table 6.7.3-1 in TS 37.104 [2]. +- 4) If the test signal is applicable according to clause 5, perform the Out-of-band emission tests as specified in clauses 6.6.2 and 6.6.4, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clauses 6.6.2 and 6.6.4. The width of the intermodulation products shall be taken into account. +- 5) If the test signal is applicable according to clause 5, perform the Transmitter spurious emissions test as specified in clause 6.6.1, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clause 6.6.1. The width of the intermodulation products shall be taken into account. +- 6) Verify that the emission level does not exceed the required level with the exception of interfering signal frequencies. +- 7) Repeat the test for the remaining interfering signal centre frequency offsets according to the conditions of Table 6.7.3-1 in TS 37.104 [2]. +- 8) Repeat the test for the remaining test signals and physical channels in Table 4.9.2-1. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 9) For multi-band capable BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +NOTE: The third order intermodulation products are centred at $2F1 \pm F2$ and $2F2 \pm F1$ . The fifth order intermodulation products are centred at $3F1 \pm 2F2$ , $3F2 \pm 2F1$ , $4F1 \pm F2$ , and $4F2 \pm F1$ where $F1$ represents the test signal centre frequency or centre frequency of each sub-block and $F2$ represents the interfering signal centre frequency. The widths of intermodulation products are + +$$(n * BW_{F1} + m * 1.6\text{MHz}) \text{ for the } nF1 \pm mF2 \text{ products}$$ + +$$(n * 1.6\text{MHz} + m * BW_{F1}) \text{ for the } nF2 \pm mF1 \text{ products}$$ + +where $BW_{F1}$ represents the test signal RF bandwidth or channel bandwidth in case of single carrier, or sub-block bandwidth. + +## 6.7.5 Test requirements + +### 6.7.5.1 General test requirement + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits in clause 6.6.1, 6.6.2 and 6.6.4 in the presence of a wanted signal and an interfering signal according to Table 6.7.1-1 in TS 37.104 [2] for BS operation in BC1, BC2 and BC3. The measurement may be limited to frequencies on which third and fifth order intermodulation products appear, considering the width of these products and excluding the bandwidths of the wanted and interfering signals. + +The requirement is applicable outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Maximum Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum, the requirement is also applicable inside a sub-block gap for interfering signal offsets where the interfering signal falls completely within the sub-block gap. The interfering signal offset is defined relative to the sub-block edges. + +For BS capable of multi-band operation, the requirement applies relative to the Base Station RF Bandwidth edges of each operating band. In case the Inter RF Bandwidth gap is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the Inter RF Bandwidth gap. + +### 6.7.5.2 Additional test requirement (BC1 and BC2) + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits in clause 6.6.1, 6.6.2 and 6.6.4 in the presence of a wanted signal and an interfering signal according to Table 6.7.2-1 in TS 37.104 [2] for BS operation in BC2. The measurement may be limited to frequencies on which third and fifth order intermodulation products appear, considering the width of these products and excluding the bandwidths of the wanted and interfering signals. + +The requirement is applicable outside the Base Station RF Bandwidth or Maximum Radio Bandwidth for BC2. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Maximum Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum in BC1 or BC2, the requirement is also applicable inside a sub-block gap larger than or equal to two times the interfering signal centre frequency offset. For BS operating in non-contiguous spectrum in BC1, the requirement is not applicable inside a sub-block gap with a gap size equal or larger than 5MHz. The interfering signal offset is defined relative to the sub-block edges. + +For BS capable of multi-band operation, the requirement applies relative to the Base Station RF Bandwidth edges of a BC2 operating band. The requirement is also applicable for BC1 and BC2 inside an Inter RF Bandwidth gap equal to or larger than two times the interfering signal centre frequency offset. For BS capable of multi-band operation, the requirement is not applicable for BC1 band inside an Inter RF Bandwidth gap with a gap size equal to or larger than 5MHz. + +### 6.7.5.3 Additional test requirement (BC3) + +This additional requirement shall only apply for BS co-located with an UTRA TDD BS. + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits in clause 6.6.1, 6.6.2 and 6.6.4 in the presence of a wanted signal and an interfering signal according to + +Table 6.7.3-1 in TS 37.104 [2] for BS operation in BC3. The measurement may be limited to frequencies on which third and fifth order intermodulation products appear, considering the width of these products and excluding the bandwidths of the wanted and interfering signals. + +For BS capable of multi-band operation, the requirement applies relative to the Base Station RF Bandwidth edges of each operating band. In case the Inter RF Bandwidth gap is less than 3.2 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the Inter RF Bandwidth gap. + +#### 6.7.5.4 Additional test requirement for Band 41 + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the maximum levels according to Table 6.6.1.5.5-3 and Table 6.6.4.5.1-2 with a square filter in the first adjacent channel, in the presence of a wanted signal and an interfering signal according to Table 6.7.4-1 in TS 37.104 [2] for a BS E-UTRA single-RAT operating in Band 41. The measurement may be limited to frequencies on which third and fifth order intermodulation products appear, considering the width of these products and excluding the bandwidths of the wanted and interfering signals. + +--- + +## 7 Receiver characteristics + +### 7.1 General + +General test conditions for receiver tests are given in clause 4, including interpretation of measurement results and configurations for testing. BS configurations for the tests are defined in clause 4.10. + +Unless otherwise stated the requirements in clause 7 apply during the Base Station receive period. + +Unless otherwise stated, a BS declared to be capable of E-UTRA with NB-IoT in-band or guard band operations (or any combination with GSM and/or UTRA and/or NR) is only required to pass the receiver tests for E-UTRA with NB-IoT in-band or guard band (or any combination with GSM and/or UTRA and/or NR); it is not required to perform the receiver tests again for E-UTRA only (or any combination with GSM and/or UTRA and/or NR). + +For a BS declared to be capable of E-UTRA (and where applicable NR) with NB-IoT in-band operations, it is not required to perform the receiver test for subPRB allocation. + +Unless otherwise stated, a BS declared to be capable of NB-IoT operation in NR in-band (or any combination with GSM and/or UTRA and/or E-UTRA) is only required to pass the receiver tests for NB-IoT operation in NR in-band (or any combination with GSM and/or UTRA and/or E-UTRA); it is not required to perform the receiver tests again for NR only (or any combination with GSM and/or UTRA and/or E-UTRA). + +For a BS declared to be capable of NB-IoT operation in NR in-band (and where applicable E-UTRA), it is not required to perform the receiver test for subPRB allocation. + +### 7.2 Reference sensitivity level + +#### 7.2.1 Definition and applicability + +The reference sensitivity power level PREFSENS is the minimum mean power received at the antenna connector at which a reference performance requirement shall be met for a specified reference measurement channel. + +Additional details are in TS 38.141-1 [26] clause 7.2, TS 36.141 [9] clause 7.2, TS 25.141 [10] clause 7.2, TS 25.142 [12] clause 7.2, and TS 51.021 [11] clause 7.3. + +#### 7.2.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clauses 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5 and 7.2.6. + +### 7.2.3 Test purpose + +To verify that at the BS Reference sensitivity level the performance requirements shall be met for a specified reference measurement channel. + +### 7.2.4 Method of test + +For this requirement the tables for applicability of requirements and test configurations in Clause 5 refer either to the single-RAT specification or to a specific test configuration. The following shall apply: + +- For references to TS 51.021 [11], the method of test is specified in TS 51.021 [11], clause 7.3. +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 7.2.4. +- For references to TS 25.142 [12], the method of test is specified in TS 25.142 [12], clause 7.2.4. +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 7.2.4. +- For references to TS 38.141-1 [26], the method of test is specified in TS 38.141-1 [26], clause 7.2.4. +- For reference to a specific test configuration TCx for GSM/EDGE, the steps in clause 7.2.4.1 and 7.2.4.2. + +#### 7.2.4.1 Initial conditions for GSM/EDGE reference sensitivity level + +Test environment: Normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1, + +- 1) Set up the equipment as shown in Annex I.2.1 TS 36.141[9]. +- 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the BS under test as follows: + - For GSM see clauses 7.3 in TS 51.021 [11] and Annex P in TS 45.005 [6] for reference channels TCH/FS and PDTCH/MCS5 to test. + +#### 7.2.4.2 Procedure for GSM/EDGE reference sensitivity level + +- 1) Set the BS according to the applicable test configuration(s) (see clause 5). +- 2) Adjust the GSM/EDGE signal generator to the wanted signal levels as specified in TS 51.021, applicable parts of clauses 7.3. +- 3) Measure the performance of the GSM/EDGE wanted signal at the BS receiver, as defined in TS 51.021, applicable parts of clauses 7.3 and. + +In addition, for a multi-band capable BS, the following step shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band where single carrier test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +### 7.2.5 Test requirements + +For E-UTRA the test requirement is in TS 36.141 [9] clause 7.2.5. + +For UTRA-FDD the test requirement is in TS 25.141 [10] clause 7.2.5. + +For UTRA-TDD the test requirement is in TS 25.142 [12] clause 7.2.5. + +For GSM-EDGE the test requirement is in TS 51.021 [11] clauses 7.3. + +For NB-IoT standalone or operation in E-UTRA in-band/guard band the test requirement is in TS 36.141 [9] clause 7.2.5. + +For NB-IoT operation in NR in-band, the test requirement is in TS 38.141-1 [26] clause 7.2.5. + +For NR the test requirement is in TS 38.141-1 [26] clause 7.2.5. + +## 7.3 Dynamic range + +### 7.3.1 Definition and applicability + +The dynamic range is a measure of the capability of the receiver to receive a wanted signal in the presence of an interfering signal inside the received channel bandwidth or the capability of receiving high level of the wanted signal. + +### 7.3.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clauses 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5 and 7.3.6. + +### 7.3.3 Test purpose + +To verify that at the BS receiver dynamic range, the receiver performance shall fulfil the specified limit. + +### 7.3.4 Method of test + +For this requirement the tables for applicability of requirements and test configurations in Clause 5 refer either to the single-RAT specification or to a specific test configuration. The following shall apply. The following shall apply: + +- For references to TS 51.021 [11], the method of test is specified in TS 51.021 [11], clause 7.1. +- For references to TS 25.141 [10], the method of test is specified in TS 25.141 [10], clause 7.3.4. +- For references to TS 25.142 [12], the method of test is specified in TS 25.142 [12], clause 7.3.4. +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 7.3.4. +- For references to TS 38.141-1 [26], the method of test is specified in TS 38.141-1 [26], clause 7.3.4. +- For q reference to a specific test configuration TCx for GSM/EDGE, the steps in clause 7.3.4.1 and 7.3.4.2. + +#### 7.3.4.1 Initial conditions for GSM/EDGE dynamic range + +Test environment: Normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1, + +- 1) Set up the equipment as shown in Annex I.2.1 TS 36.141[9]. +- 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the BS under test as follows: + - For GSM see clause 7.1 in TS 51.021 [11] for reference channels to test. + +#### 7.3.4.2 Procedure for GSM/EDGE dynamic range + +- 1) Set the BS according to the applicable test configuration(s) (see clause 5). +- 2) Adjust the GSM/EDGE signal generator to the wanted signal levels as specified in TS 51.021, applicable parts of clauses 7.1 +- 3) Measure the performance of the GSM/EDGE wanted signal at the BS receiver, as defined in TS 51.021, applicable parts of clause 7.1. + +In addition, for a multi-band capable BS, the following step shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +### 7.3.5 Test requirements + +For E-UTRA the test requirement is in TS 36.141 [9] clause 7.3.5. + +For UTRA-FDD the test requirement is in TS 25.141 [10] clause 7.3.5. + +For UTRA-TDD the test requirement is in TS 25.142 [12] clause 7.3.5. + +For GSM-EDGE the test requirement is in TS 51.021 [11] clause 7.1. + +For NB-IoT standalone or operation in E-UTRA in-band/guard band the test requirement is in TS 36.141 [9] clause 7.3.5. + +For NB-IoT operation in NR in-band the test requirement is in TS 38.141-1 [26] clause 7.3.5. + +For NR the test requirement is in TS 38.141-1 [26] clause 7.3.5. + +## 7.4 In-band selectivity and blocking + +### 7.4.1 Definition and applicability + +The in-band selectivity and blocking characteristics are measures of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer inside the operating band and are defined by a wideband and a narrowband blocking requirement. + +The in-band blocking requirement applies from $F_{UL\_low} - \Delta f_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ , excluding the downlink frequency range of the FDD *operating band*. The values of $\Delta f_{OOB}$ are defined in table 7.4.1-1. For a BS with multi-RAT operation where the individual RATs are in different RAT specific bands that partially or fully overlap; $\Delta f_{OOB}$ is according to the combined frequency range occupied by the overlapping bands. + +**Table 7.4.1-1: Maximum $\Delta f_{OOB}$ offset outside the uplink operating band** + +| Operating band characteristics | \Delta f_{OOB} [MHz] | +|---------------------------------------------------------------------|------------------------------------------| +| $200 \text{ MHz} \geq F_{UL\_high} - F_{UL\_low}$ | 20 | +| $200 \text{ MHz} < F_{UL\_high} - F_{UL\_low} \leq 900 \text{ MHz}$ | 60 | + +Unless otherwise stated, a BS declared to be capable of E-UTRA with NB-IoT in-band and guard band operations (or any combination with GSM and/or UTRA) is only required to pass the in-band selectivity and blocking receiver tests for E-UTRA with guard band operation (or any combination with GSM and/or UTRA). It's not required to perform the in-band selectivity and blocking receiver tests again for E-UTRA with in-band operation (or any combination with GSM and/or UTRA). + +### 7.4.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clauses 7.4.1, 7.4.2, 7.4.3, 7.4.4, and 7.4.5. + +### 7.4.3 Test purpose + +The test stresses the ability of the BS receiver to withstand high-level interference from unwanted signals at specified frequency offsets without undue degradation of its sensitivity. + +## 7.4.4 Method of test + +### 7.4.4.1 Initial conditions + +Test environment: Normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1, $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B_{\text{RFBW\_T}}^{\text{RFBW}}$ in multi-band operation, see clause 4.9.1. + +- 1) Set up the equipment as shown in Annex D.2.1. +- 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the BS under test as follows: + - For E-UTRA see Annex A.1 in TS 36.141 [9]. + - For UTRA FDD see Annex A.2 in TS 25.141 [10]. + - For UTRA TDD see Annex A.2.1 in TS 25.142 [12]. + - For GSM see clause 7.6.2 in TS 51.021 [11] and Annex P in TS 45.005 [6] for reference channels to test. + - For NB-IoT see Annex A.14 in TS 36.141 [9]. + - For NR see Annex A.1 in TS 38.141-1 [26]. + +### 7.4.4.2 Procedure for general blocking + +- 1) Set the BS to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). +- 2) Adjust the signal generators to the type of interfering signal, levels and the frequency offsets as specified in Table 7.4.5.1-1. +- 3) The interfering signal shall be swept with a step size of 1 MHz starting from the minimum offset to the channel edges of the wanted signals as specified in Table 7.4.5.1-1 +- 4) Measure the performance of the wanted signal at the BS receiver, as defined in clause 7.4.5, for the relevant carriers specified by the test configuration in clause 4.8. + +In addition, for a multi-band capable BS with separate antenna connectors, the following steps shall apply: + +- 5) For single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. +- 6) For multi-band tests, 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 wanted signal. Any antenna connector with no signal applied shall be terminated. +- 7) Repeat step 6 with the wanted signal for the other band(s) applied on the respective port(s). + +### 7.4.4.3 Procedure for narrowband blocking + +- 1) Set the BS to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). +- 2) Adjust the signal generators to the type of interfering signal, levels and the frequency offsets as specified in Tables 7.4.5.2-1 and 7.4.5.2-2. +- 3) Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to Tables 7.4.5.2-1 and 7.4.5.2-2. +- 4) Measure the performance of the wanted signal at the BS receiver, as defined in clause 7.4.5, for the relevant carriers specified by the test configuration in clause 4.8. + +In addition, for a multi-band capable BS with separate antenna connectors, the following steps shall apply: + +- 5) For single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. +- 6) For multi-band tests, 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 shall be terminated. +- 7) Repeat step 6 with the wanted signal for the other band(s) applied on the respective port(s). + +#### 7.4.4.4 Procedure for additional narrowband blocking for GSM/EDGE + +For this requirement, the tables for applicability of requirements and test configurations in Clause 5 refer either to the single-RAT specification or to a specific test configuration. The following shall apply. The following method of test shall apply for GSM/EDGE carriers: + +- For references to TS 51.021 [11], the GSM/EDGE in-band blocking method of test in TS 51.021 [11], applicable parts of clause 7.6. The conditions specified in TS 45.005 [6], Annex P.2.1 apply for GSM/EDGE in-band narrowband blocking. +- For reference to a specific test configuration TCx, the steps in clause 7.4.4.4.1 and 7.4.4.4.2 for testing additional narrowband blocking for GSM/EDGE. + +##### 7.4.4.4.1 Initial conditions for additional narrowband blocking + +Test environment: Normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1, + +- 1) Set up the equipment as shown in Annex D.2.1. +- 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the BS under test as follows: + - For GSM see clause 7.6.2 in TS 51.021 [11] and Annex P.2.1 in TS 45.005 [6] for reference channels to test. + +##### 7.4.4.4.2 Procedure for additional narrowband blocking + +- 1) Set the BS according to the applicable test configuration(s) (see clause 5). +- 2) Adjust the GSM/EDGE signal generator to the wanted signal levels as specified in TS 51.021, applicable parts of clauses 7.6. +- 3) Set-up the interfering signal as specified in TS 51.021, applicable parts of clauses 7.6. +- 4) Measure the performance of the GSM/EDGE wanted signal at the BS receiver, as defined in TS 51.021, applicable parts of clause 7.6. + +In addition, for multi-band capable BS and single band tests, repeat the procedure above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. Any antenna connector with no signal applied shall be terminated. + +#### 7.4.4.5 Procedure for GSM/EDGE AM suppression + +For this requirement, the tables for applicability of requirements and test configurations in Clause 5 refer either to the single-RAT specification or to a specific test configuration. The following shall apply. The following method of test shall apply for GSM/EDGE carriers: + +- For references to TS 51.021 [11], the GSM/EDGE AM suppression method of test in TS 51.021 [11], applicable parts of clause 7.8. The conditions specified in TS 45.005 [6], Annex P.2.3 apply for GSM/EDGE AM suppression. + +- For reference to a specific test configuration TCx, the steps in clause 7.4.4.5.1 and 7.4.4.5.2 for testing GSM/EDGE AM suppression shall apply. + +#### 7.4.4.5.1 Initial conditions for GSM/EDGE AM suppression + +Test environment: Normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $M_{RFBW}$ in single-band operation, see clause 4.9.1. + +- 1) Set up the equipment as shown in Annex D.2.1. +- 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the BS under test as follows: + - For GSM see clause 7.8 in TS 51.021 [11] and Annex P.2.3 in TS 45.005 [6] for reference channels to test. + +#### 7.4.4.5.2 Procedure for GSM/EDGE AM suppression + +- 1) Set the BS according to the applicable test configuration(s) (see clause 5). +- 2) Adjust the GSM/EDGE signal generator to the wanted signal levels as specified in TS 51.021, applicable parts of clauses 7.8. +- 3) Set-up the interfering signal as specified in TS 51.021, applicable parts of clauses 7.8. +- 4) Measure the performance of the GSM/EDGE wanted signal at the BS receiver, as defined in TS 51.021, applicable parts of clause 7.8. + +In addition, for multi-band capable BS and single band tests, repeat the procedure above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. Any antenna connector with no signal applied shall be terminated. + +#### 7.4.4.6 Procedure for additional BC3 blocking requirement + +- 1) Adjust the signal generators to the type of interfering signal, levels and the frequency offsets as specified in Table 7.4.5.5-1 +- 2) Measure the performance of the wanted signal at the BS receiver, as defined in clause 7.4.5, for the relevant carriers specified by the test configuration in clause 4.8. + +### 7.4.5 Test requirements + +#### 7.4.5.1 General blocking test requirement + +For the general blocking requirement, the interfering signal shall be a UTRA FDD signal as specified in Annex A.1 for a UTRA, E-UTRA, NB-IOT, GSM/EDGE or NR ( $\leq 20$ MHz) wanted signal. The interfering signal shall be a 20 MHz E-UTRA signal for NR wanted signal channel bandwidth greater than 20MHz. + +The requirement is applicable outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Maximum Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum, the requirement applies in addition inside any sub-block gap, in case the sub-block gap size is at least 15MHz. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +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 15MHz. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +For the wanted and interfering signal coupled to the Base Station antenna input, using the parameters in Table 7.4.5.1-1, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [3], clause 7.2. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [4], clause 7.2. +- For any measured GSM/EDGE carrier, the conditions are specified in TS 45.005 [6], Annex P.2.1. +- For any measured NB-IoT carrier (standalone or operating in E-UTRA in-band/guard band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2 +- For any measured NB-IoT carrier (operating in NR in-band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. + +For BS capable of multi-band operation, the requirement applies according to Table 7.4.5.1-1 for the in-band blocking frequency ranges of each supported operating band. + +**Table 7.4.5.1-1: General blocking requirement** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] (Note 1) | Centre Frequency of Interfering Signal | Interfering signal centre frequency minimum frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap [MHz] | +|-------------------|----------------------------------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | -40+y (Note 7) | $P_{\text{REFSENS}} + x$ dB (Note 2) | $F_{\text{UL\_low}} - \Delta f_{\text{OOB}}$ to $F_{\text{UL\_high}} + \Delta f_{\text{OOB}}$ (Note 8) | $\pm (7.5 + z)$ (Note 9) | +| Medium Range BS | -35+y (Note 7) | $P_{\text{REFSENS}} + x$ dB (Note 3, 6) | | | +| Local Area BS | -30+y (Note 7) | $P_{\text{REFSENS}} + x$ dB (Note 4, 6) | | | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth, see clause 7.2 in TS 37.104. + +NOTE 2: For WA BS supporting GSM and/or UTRA, "x" is equal to 6 in case of NR or E-UTRA or UTRA or NB-IoT wanted signals and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 3: For MR BS supporting GSM and/or UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA or NB-IoT wanted signal and 3 in case of GSM/EDGE wanted signal. + +NOTE 4: For LA BS supporting GSM and/or UTRA, "x" is equal to 11 in case of NR or E-UTRA or NB-IoT wanted signal, 6 in case of UTRA wanted signal and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 5: For a BS capable of multi-band operation, "x" in Note 2, 3, 4, 6 applies in case of interfering signals that are in the in-band blocking frequency range of the operating band where the wanted signal is present or in the in-band blocking frequency range of an adjacent or overlapping operating band. For other in-band blocking frequency ranges of the interfering signal for the supported operating bands, "x" is equal to 1.4 dB. + +NOTE 6: For a BS neither supporting UTRA nor GSM, x is equal to 6 for all BS classes if NR is supported, otherwise "x" is equal to 6 for WA BS, 9 for MR BS or 11 for LA BS if NR is not supported. + +NOTE 7: For a BS supporting NR but neither UTRA nor GSM, "y" is equal to -3 for the WA and MR BS class and -5 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. + +NOTE 8: The downlink frequency range of an FDD operating band is excluded from the general blocking requirement. + +NOTE 9: For NR wanted signal channel bandwidth greater than 20 MHz, z = 22.5. For all other cases, z = 0. + +**Table 7.4.5.1-2: Void** + +NOTE: The requirement in Table 7.4.5.1-1 assumes that two operating bands, where the downlink operating band (see Table 4.4-1 and Table 4.4-2) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +## 7.4.5.2 General narrowband blocking test requirement + +For the narrowband blocking requirement, the interfering signal shall be an E-UTRA 1RB signal as specified in Annex A.3. + +The requirement is applicable outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Maximum Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum, the requirement applies in addition inside any sub-block gap, in case the sub-block gap size is at least 3MHz. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +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 3MHz. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +For the wanted and interfering signal coupled to the Base Station antenna input, using the parameters in Table 7.4.5.2-1 the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [3], clause 7.2. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [4], clause 7.2. +- For any measured NB-IoT carrier (standalone or operating in E-UTRA in-band/guard band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured NB-IoT carrier (operating in NR in-band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. + +**Table 7.4.5.2-1: Narrowband blocking requirement** + +| Base Station Type | RAT of the carrier | Wanted signal mean power [dBm] (Note 1, 2, 6) | Interfering signal mean power [dBm] | Interfering RB (Note 3) centre frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap [kHz] | +|-------------------|------------------------------------------------------|-----------------------------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | NR, E-UTRA, NB-IoT (Note 4),
UTRA and
GSM/EDGE | $P_{\text{REFSENS}} + x$ dB | -49 | $\pm(240 + m \cdot 180)$ ,
$m=0, 1, 2, 3, 4, 9, 14$
(Note 5) | +| Medium Range BS | | | -44 | | +| Local Area BS | | | -41 | | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth, see clause 7.2 in TS 37.104. + +NOTE 2: "x" is equal to 6 in case of NR, E-UTRA or UTRA wanted signals and equal to 3 in case of GSM/EDGE wanted signal. "x" is specified in Table 7.4.2-2 for NB-IoT standalone and NB-IoT operation in E-UTRA in-band/guard band and in Table 7.4.2-3 for NB-IoT operation in NR in-band. + +NOTE 3: Interfering signal (E-UTRA 3MHz) consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the Base Station RF Bandwidth edge. + +NOTE 4: For NB-IoT, the mentioned desensitized values consider only one NB-IoT PRB in the guard band, which is placed adjacent to the E-UTRA PRB edge as close as possible (i.e., away from edge of channel bandwidth). + +NOTE 5: Applicable for *channel bandwidths* equal to or below 20 MHz. + +NOTE 6: Applicable for *channel bandwidths* above 20 MHz. + +NOTE 6: 7.5 kHz shift is not applied to the wanted signal of NR. + +NOTE 7: Void + +**Table 7.4.5.2-2: "x" for NB-IoT wanted signals operation in E-UTRA in-band/guard band and NB-IoT standalone** + +| Operation mode | LTE channel bandwidth for in-band/guard band operation | x | +|----------------|--------------------------------------------------------|----| +| Standalone | - | 12 | +| In Band | 3 MHz | 11 | +| | 5 MHz | 9 | +| | 10 MHz | 6 | +| | 15 MHz | 6 | +| | 20 MHz | 6 | +| Guard band | 5 MHz | 13 | +| | 10 MHz | 6 | +| | 15 MHz | 6 | +| | 20 MHz | 6 | + +**Table 7.4.5.2-3: "x" for NB-IoT wanted signals operation in NR in-band** + +| Operation mode | NR channel bandwidth for in-band operation | x | +|----------------|--------------------------------------------|---| +| In Band | 5 MHz | 9 | +| | $\geq 10$ MHz | 6 | + +### 7.4.5.3 Additional narrowband blocking test requirement for GSM/EDGE + +The GSM/EDGE in-band blocking test requirements are stated in TS 51.021 [11], applicable parts of clause 7.6. + +The conditions specified in TS 45.005 [6], Annex P.2.1 apply for GSM/EDGE in-band narrowband blocking. + +#### 7.4.5.4 GSM/EDGE test requirements for AM suppression + +The GSM/EDGE in-band blocking test requirements are stated in TS 51.021 [11], applicable parts of clause 7.8. + +The conditions specified in TS 45.005 [6], Annex P.2.3 apply for GSM/EDGE AM suppression. + +#### 7.4.5.5 Additional BC3 blocking test requirement + +This additional requirement only applies for BS operating in the same geographical area as UTRA TDD. + +The interfering signal is a 1.28Mcps UTRA TDD modulated signal as specified in Annex A.2. + +The requirement is applicable outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges 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 4.8MHz. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +For the wanted and interfering signal coupled to the Base Station antenna input, using the parameters in Table 7.4.5.5-1, the following requirements shall be met: + +- For any measured E-UTRA TDD carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [4], clause 7.2. + +**Table 7.4.5.5-1: Additional blocking requirement for Band Category 3** + +| Operating Band | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Interfering signal centre frequency minimum frequency offset from the Base Station RF Bandwidth edge [MHz] | +|---------------------------------------------------------------------------------------|---------------------------------------------------|-------------------------------------|--------------------------------|------------------------------------------------------------------------------------------------------------| +| 33 - 40 | ( $F_{UL\_low} - 20$ ) to ( $F_{UL\_high} + 20$ ) | -40, | $P_{REFSENS} + 6$ dB* | $\pm 2.4$ | +| NOTE*: $P_{REFSENS}$ depends on the RAT and on the channel bandwidth, see clause 7.2. | | | | | + +## 7.5 Out-of-band blocking + +### 7.5.1 Definition and applicability + +The Out-of-band blocking characteristic is a measure of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer outside the uplink operating band. + +The blocking performance requirement applies as specified in the Table 7.5.5.1-1 and Table 7.5.5.2-1. + +Unless otherwise stated, a BS declared to be capable of E-UTRA with NB-IoT in-band and guard band operations (or any combination with GSM and/or UTRA) is only required to pass the out-of-band blocking tests for E-UTRA with guard band operation (or any combination with GSM and/or UTRA). It's not required to perform the out-of-band blocking receiver tests again for E-UTRA with in-band operation (or any combination with GSM and/or UTRA). + +### 7.5.2 Minimum requirement + +The general minimum requirement is in TS 37.104 [2] clause 7.5.1. The co-location minimum requirement is in TS 37.104 [2] clause 7.5.2. + +### 7.5.3 Test purpose + +The test stresses the ability of the BS receiver to withstand high-level interference from unwanted signals at specified frequency bands, without undue degradation of its sensitivity. + +### 7.5.4 Method of test + +#### 7.5.4.1 Initial conditions + +Test environment: normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1, $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B_{\text{RFBW\_T}}^{\text{RFBW}}$ in multi-band operation, see clause 4.9.1. + +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) Set up the equipment as shown in Annex D.2.1. + - 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using reference measurement channel to the BS under test as follows: + - For E-UTRA see Annex A.1 in TS 36.141 [9]. + - For UTRA FDD see Annex A.2 in TS 25.141 [10]. + - For UTRA TDD see Annex A.2.1 in TS 25.142 [12]. + - For GSM see clause 7.6.2 in TS 51.021 [11] and Annex P in TS 45.005 [6] for reference channels to test. + - For NB-IoT see Annex A.14 in TS 36.141 [9]. + - For NR see Annex A.1 in TS 38.141-1 [26]. + +#### 7.5.4.2 Procedure + +- 1) Set the BS to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +The transmitter may be turned off for the out-of-band blocker tests when the frequency of the blocker is such that no IM2 or IM3 products fall inside the bandwidth of the wanted signal. + +- 2) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified for general test requirements in Table 7.5.5.1-1 and, when applicable, for co-location test requirements in Table 7.5.5.2-1. +- 3) The CW interfering signal shall be swept with a step size of 1 MHz within the specified range. +- 4) Measure the performance of the wanted signal at the BS receiver, as defined in the clause 7.5.5, for the relevant carriers specified by the test configuration in clause 4.8. + +In addition, for a multi-band capable BS with separate antenna connectors, the following steps shall apply: + +- 5) For single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. +- 6) For multi-band tests, 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 shall be terminated. +- 7) Repeat step 6 with the wanted signal for the other band(s) applied on the respective port(s). + +## 7.5.5 Test requirements + +### 7.5.5.1 General out-of-band blocking test requirements + +For a wanted and an interfering signal coupled to BS antenna input using the parameters in Table 7.5.5.1-1, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [3], clause 7.2. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [4], clause 7.2. +- For any measured GSM/EDGE carrier, the conditions are specified in TS 45.005 [6], Annex P.2.1. +- For any measured NB-IoT carrier (standalone or operating in E-UTRA in-band/guard band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured NB-IoT carrier (operating in NR in-band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. + +For BS capable of multi-band operation, the requirement applies for each supported operating band. The in-band blocking frequency ranges of all supported operating bands according to Table 7.4.5.1-1 shall be excluded from the requirement. + +The out-of-band blocking requirement applies from 1 MHz to $F_{UL\_low} - \Delta f_{OOB}$ and from $F_{UL\_high} + \Delta f_{OOB}$ up to 12750 MHz, including the downlink frequency range of the FDD *operating band* for BS supporting FDD. $\Delta f_{OOB}$ is defined in table 7.4.1-1. + +**Table 7.5.5.1-1: Out-of-band blocking performance requirement** + +| Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------| +| -15 (NOTE2) | $P_{REFSENS} + x\text{dB}$ (NOTE1) | CW carrier | +|

NOTE1: P_{REFSENS} depends on the RAT, the BS class and the channel bandwidth, see clause 7.2.
"x" is equal to 6 in case of NR, E-UTRA, UTRA or NB-IoT wanted signals and equal to 3 in case of GSM/EDGE wanted signal.
NOTE2: For NB-IoT, up to 24 exceptions are allowed for spurious response frequencies in each wanted signal frequency when measured using a 1MHz step size. For these exceptions the above throughput requirement shall be met when the blocking signal is set to a level of -40 dBm for 15 kHz subcarrier spacing and -46 dBm for 3.75 kHz subcarrier spacing. In addition, each group of exceptions shall not exceed three contiguous measurements using a 1MHz step size.

| | | + +### 7.5.5.2 Co-location test requirements + +This additional blocking requirement may be applied for the protection of BS receivers when NR, E-UTRA, UTRA, CDMA or GSM/EDGE BS operating in a different frequency band are co-located with a BS. + +The requirements in this clause assume a 30 dB coupling loss between the interfering transmitter and the BS receiver and are based on co-location with base stations of the same class. + +For a wanted and an interfering signal coupled to BS antenna input using the parameters in Table 7.5.5.2-1, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [3], clause 7.2. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [4], clause 7.2. +- For any measured GSM/EDGE carrier, the conditions are specified in TS 45.005 [6], Annex P.2.1. +- For any measured NB-IoT carrier (standalone or operating in E-UTRA in-band/guard band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured NB-IoT carrier (operating in NR in-band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. + +**Table 7.5.5.2-1: Blocking requirement for co-location with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 – 894 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| GSM900 | 921 – 960 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| DCS1800 | 1805 – 1880 (Note 4) | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| PCS1900 | 1930 – 1990 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 2110 – 2170 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1930 – 1990 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 | 1805 – 1880 (Note 4) | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 869 – 894 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 – 885 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2620 – 2690 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 – 960 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 – 1495.9 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 729 – 746 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 746 – 756 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 758 – 768 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 17 | 734 – 746 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 18 or NR Band n18 | 860 – 875 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 – 890 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | + +| | | | | | | | +|-----------------------------------------------------|-------------------------|-------|------|------|---------------------------------------|------------| +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 791 - 821 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 – 1510.9 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 24 or NR Band n24 | 1525 – 1559 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR Band n25 | 1930 – 1995 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 – 894 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 27 | 852 - 869 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 28 or NR Band n28 | 758 – 803 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717-728 | +16** | +8** | -6** | $P_{\text{REFSENS}} + 6\text{dB}^*$ | CW carrier | +| E-UTRA Band 30 or NR Band n30 | 2350-2360 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5–467.5 | +16** | +8** | -6** | $P_{\text{REFSENS}} + 6\text{dB}^*$ | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 – 1496
(NOTE 5) | +16** | +8** | -6** | $P_{\text{REFSENS}} + 6\text{dB}^*$ | CW carrier | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900-1920 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band a) or E-UTRA Band 34 or NR Band n34 | 2010-2025 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850-1910 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930-1990 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910-1930 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570-2620 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR Band n39 | 1880-1920 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300-2400 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 41 or NR Band n41 | 2496 - 2690 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 42 | 3400 – 3600 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 43 | 3600 – 3800 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 44 | 703 - 803 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +16** | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 46 | 5150 - 5925 | N/A | +8** | -6** | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | + +| | | | | | | | +|---------------------------------|---------------|-------|------|------|--------------------------------|------------| +| or NR Band n46 | | | | | | | +| E-UTRA Band 48 or NR Band n48 | 3550 - 3700 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 49 | 3550 - 3700 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 50 or NR Band n50 | 1432 - 1517 | +16 | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 51 or NR Band n51 | 1427 - 1432 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 52 | 3300 - 3400 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 | N/A | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 - 1675 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 65 or NR Band n65 | 2110 - 2200 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 66 or NR Band n66 | 2110 - 2200 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 69 | 2570-2620 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 70 or NR Band n70 | 1995 - 2020 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 71 or NR Band n71 | 617 - 652 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 74 or NR Band n74 | 1475 - 1518 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 75 or NR Band n75 | 1432 - 1517 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 76 or NR Band n76 | 1427 - 1432 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n77 | 3300 - 4200 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n78 | 3300 - 3800 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 - 746 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 87 | 420 - 425 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 88 | 422 - 427 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n91 | 1427 - 1432 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n92 | 1432 - 1517 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n93 | 1427 - 1432 | N/A | N/A | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n94 | 1432 - 1517 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n96 | 5925 - 7125 | N/A | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n100 | 919.4 - 925 | +16 | N/A | N/A | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n101 | 1900 - 1910 | +16 | N/A | N/A | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n102 | 5925 - 6425 | N/A | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 103 | 757 - 758 | +16** | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n104 | 6425 - 7125 | +16 | +8 | -6 | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n105 | 612 - 652 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 106 or NR Band n106 | 935 - 940 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | +| NR Band n109 | 1432 - 1517 | +16** | +8** | -6** | $P_{REFSENS} + x \text{ dB}^*$ | CW carrier | + +NOTE 1 (\*): $P_{REFSENS}$ depends on the RAT, the BS class and the channel bandwidth, see clause 7.2. + +"x" is equal to 3 in case of GSM/EDGE wanted signal and equal to 6 in case of NR, UTRA or E-UTRA wanted signals. + +NOTE 2: Except for a BS operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported uplink operating band or in the $\Delta f_{OOB}$ immediately outside any of the supported uplink operating band. + +For a BS operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768-797MHz. + +NOTE 3: 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 or E-UTRA TDD or NR TDD with E-UTRA FDD or NR 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 [14]. + +- NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805-1850MHz. +- NOTE 5: For a BS operating in band 11, 21 or 74, the requirement for co-location with Band 32 applies for interfering signal within the frequency range 1475.9-1495.9 MHz. +- NOTE 6: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can receive without special co-location requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. +- NOTE 7 (\*\*): For NB-IoT, up to 24 exceptions are allowed for spurious response frequencies in each wanted signal frequency when measured using a 1MHz step size. For these exceptions the above throughput requirement shall be met when the blocking signal is set to a level of -40 dBm for 15 kHz subcarrier spacing and -46 dBm for 3.75 kHz subcarrier spacing. In addition, each group of exceptions shall not exceed three contiguous measurements using a 1MHz step size. + +## 7.6 Receiver spurious emissions + +### 7.6.1 Definition and applicability + +The receiver spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the BS receiver antenna connector. The requirements apply to all BS with separate RX and TX antenna ports. In this case for FDD BS the test shall be performed when both TX and RX are on, with the TX port terminated. + +For TDD BS with common RX and TX antenna port the requirement applies during the Transmitter OFF period. For FDD BS with common RX and TX antenna port the transmitter spurious emission limits as specified in clause 6.6.1 are valid. + +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. + +Unless otherwise stated, a BS declared to be capable of E-UTRA with NB-IoT in-band and guard band operations (or any combination with GSM and/or UTRA) is only required to pass the receiver spurious emissions tests for E-UTRA with guard band operation (or any combination with GSM and/or UTRA). It's not required to perform the receiver spurious emissions tests again for E-UTRA with in-band operation (or any combination with GSM and/or UTRA). + +### 7.6.2 Minimum requirements + +The minimum requirement is in TS 37.104 [2] clause 7.6.1. + +### 7.6.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.6.4 Method of test + +#### 7.6.4.1 Initial conditions + +Test environment: Normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1, $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B_{\text{RFBW\_T}}^{\text{RFBW}}$ in multi-band operation, see clause 4.9.1. + +- 1) Set up the equipment as shown in Annex D.2.1. +- 2) Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2-2. + +### 7.6.4.2 Procedure + +- 1) Set the measurement equipment parameters as specified in Table 7.6.5.1-1. For BC2, the parameters in Table 7.6.5.2-1 apply in addition. +- 2) Set the BS to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +For TDD connectors capable of transmit and receive ensure the transmitter is OFF. + +- 3) Measure the spurious emissions over each frequency range described in clause 7.6.5. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 4) For multi-band capable BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of SBT or MBT shall be terminated. + +## 7.6.5 Test requirements + +### 7.6.5.1 General test requirements + +The power of any spurious emission shall not exceed the levels in Table 7.6.5.1-1. + +**Table 7.6.5.1-1: General spurious emission test requirement** + +| Frequency range | Maximum level | Measurement Bandwidth | Note | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 30 MHz - 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz - 12.75 GHz | -47 dBm | 1 MHz | | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -47 dBm | 1 MHz | This spurious frequency range applies only for operating bands for which the 5 th harmonic of the upper frequency edge of the UL operating band is reaching beyond 12.75 GHz. | +| NOTE: The frequency range from $F_{BW,RF,DL,low} - \Delta f_{OBUE}$ to $F_{BW,RF,DL,high} + \Delta f_{OBUE}$ may be excluded from the requirement. 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. | | | | + +In addition to the requirements in Table 7.6.5.1-1, the power of any spurious emission shall not exceed the additional spurious emissions requirements in clause 6.6.1.5.5 and in case of FDD BS (for BC1 and BC2) emission shall not exceed the levels specified for protection of the BS receivers of own or different BS in clause 6.6.1.5.4. In addition, the requirements for co-location with other Base Stations specified in clause 6.6.1.5.6 may also be applied. + +### 7.6.5.2 Additional test requirement for BC2 (Category B) + +For a BS operating in Band Category 2 when GSM/EDGE is configured and where Category B spurious emissions apply, the power of any spurious emissions shall not exceed the limits in Table 7.6.5.2-1. + +For BS capable of multi-band operation, the limits in Table 7.6.5.2-1 are only applicable when all supported operating bands belong to BC2 and GSM/EDGE is configured in all bands. + +**Table 7.6.5.2-1: Additional BS spurious emissions limits for BC2, Category B** + +| Frequency range | Frequency offset from transmitter operating band edge (Note 1) | Maximum level | Measurement Bandwidth | +|-------------------|----------------------------------------------------------------|---------------|-----------------------| +| 500 MHz – 1 GHz | 10 – 20 MHz | -57 dBm | 300 kHz | +| | 20 – 30 MHz | -57 dBm | 1 MHz | +| | ≥ 30 MHz | -57 dBm | 3 MHz | +| 1 GHz – 12.75 GHz | ≥ 30 MHz | -47 dBm | 3 MHz | + +NOTE 1: For BS capable of multi-band operation, the frequency offset is relative to the closest supported operating band. + +## 7.7 Receiver intermodulation + +### 7.7.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 receiver to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. + +Unless otherwise stated, a BS declared to be capable of E-UTRA with NB-IoT in-band and guard band operations (or any combination with GSM and/or UTRA) is only required to pass the receiver intermodulation tests for E-UTRA with guard band operation (or any combination with GSM and/or UTRA). It's not required to perform the receiver intermodulation tests again for E-UTRA with in-band operation (or any combination with GSM and/or UTRA). + +### 7.7.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2], clauses 7.7.1, 7.7.2 and 7.7.3. + +### 7.7.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.7.4 Method of test + +#### 7.7.4.1 Initial conditions + +Test environment: Normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: In single-band operation: $M_{\text{RFBW}}$ if TC6 is applicable; $B_{\text{RFBW}}$ and $T_{\text{RFBW}}$ for other TC, see clause 4.9.1, Table 5.1-1 and Table 5.2-1. In multi-band operation: $B_{\text{RFBW\_T}}$ and $B_{\text{RFBW\_T}}$ , see clause 4.9.1. + +- 1) Set-up the measurement system as shown in Annex D.2.3. +- 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using reference measurement channel to the BS under test as follows: + - For E-UTRA see Annex A.1 in TS 36.141 [9]. + - For UTRA FDD see Annex A.2 in TS 25.141 [10]. + - For UTRA TDD see Annex A.2.1 in TS 25.142 [12]. + - For GSM see clause 7.7.2 in TS 51.021 [11] and Annex P in TS 45.005 [6] for reference channels to test. + - For NB-IoT see Annex A.14 in TS 36.141 [9]. + +- For NR see Annex A.1 in TS 38.141-1 [26]. + +#### 7.7.4.2 Procedure for general and narrowband intermodulation + +- 1) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified in Table 7.7.5.1-1 and Table 7.7.5.1-2 for general intermodulation requirement, and Table 7.7.5.2-1 and Table 7.7.5.2-2 for narrowband intermodulation requirement. +- 2) Measure the performance of the wanted signal at the BS receiver, as defined in clause 7.7.5.1 and 7.7.5.2, for the relevant carriers specified by the test configuration in clause 4.8. + +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 where single band test configurations shall apply with no carrier activated in the other band. +- 4) For multi-band tests, 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 shall be terminated. +- 5) Repeat step 6 with the wanted signal for the other band(s) applied on the respective port(s). + +#### 7.7.4.3 Procedure for additional narrowband intermodulation for GSM/EDGE + +For this requirement, the tables for applicability of requirements and test configurations in Clause 5 refer either to the single-RAT specification or to a specific test configuration. The following shall apply. The following method of test shall apply for GSM/EDGE carriers: + +- For references to TS 51.021 [11], the GSM/EDGE MC-BTS receiver intermodulation method of test is stated in TS 51.021 [11], applicable parts of clause 7.7. The conditions specified in TS 45.005 [6], Annex P.2.2 apply for the GSM/EDGE intermodulation requirement. +- For reference to a specific test configuration TCx, the steps in clause 7.7.4.3.1 and 7.7.4.3.2 for testing additional narrowband intermodulation for GSM/EDGE shall apply. + +##### 7.7.4.3.1 Initial conditions for additional narrowband intermodulation + +Test environment: Normal; see Annex B.2. + +Base Station RF Bandwidth positions to be tested: $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1, + +- 1) Set up the equipment as shown in Annex D.2.3. +- 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the BS under test as follows: + - For GSM see clause 7.7 in TS 51.021 [11] and Annex P.2.2 in TS 45.005 [6] for reference channels to test. + +##### 7.7.4.3.2 Procedure for additional narrowband intermodulation + +- 1) Set the BS according to the applicable test configuration(s) (see clause 5). +- 2) Adjust the GSM/EDGE signal generator to the wanted signal levels as specified in TS 51.021, applicable parts of clauses 7.7. +- 3) Set-up the interfering signal as specified in TS 51.021, applicable parts of clauses 7.7. +- 4) Measure the performance of the GSM/EDGE wanted signal at the BS receiver, as defined in TS 51.021, applicable parts of clause 7.7. + +In addition, for multi-band capable BS and single band tests, repeat the procedure above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. Any antenna connector with no signal applied shall be terminated. + +## 7.7.5 Test requirements + +### 7.7.5.1 General intermodulation test requirement + +Interfering signals shall be a CW signal and an E-UTRA or UTRA signal, as specified in Annex A. + +The requirement is applicable outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges 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 twice as wide as the UTRA/E-UTRA interfering signal centre frequency offset from the Base Station RF Bandwidth edge. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +For the wanted signal at the assigned channel frequency and two interfering signals coupled to the Base Station antenna input, using the parameters in Table 7.7.5.1-1 and 7.7.5.1-2, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [3], clause 7.2. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [4], clause 7.2. +- For any measured NB-IoT carrier (standalone or operating in E-UTRA in-band/guard band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured NB-IoT carrier (operating in NR in-band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. + +**Table 7.7.5.1-1: General intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] | Type of interfering signal | +|-------------------|-----------------------------------------|-----------------------------------------|----------------------------| +| Wide Area BS | -48+y (Note 6) | $P_{\text{REFSENS}} + x$ dB (Note 2, 5) | See Table 7.7.5.1-2 | +| Medium Range BS | -44+y (Note 6) | $P_{\text{REFSENS}} + x$ dB (Note 3, 5) | | +| Local Area BS | -38+y (Note 6) | $P_{\text{REFSENS}} + x$ dB (Note 4, 5) | | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth, see clause 7.2 in TS 37.104 [2]. For E-UTRA channel bandwidths 10, 15 and 20 MHz this requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals. + +NOTE 2: For WA BS supporting GSM and/or UTRA, "x" is equal to 6 in case of NR or E-UTRA or UTRA or NB-IoT wanted signals and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 3: For MR BS supporting GSM and/or UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA or NB-IoT wanted signal and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 4: For LA BS supporting GSM and/or UTRA, "x" is equal to 12 in case of NR or E-UTRA or NB-IoT wanted signals, 6 in case of UTRA wanted signal and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 5: For a BS neither supporting GSM nor UTRA, x is equal to 6 for all BS classes if NR is supported, otherwise x is equal to 6 for WA BS or, 9 for MR BS and 12 for LA BS if NR is not supported. + +NOTE 6: For a BS supporting NR but neither UTRA nor GSM; "y" is equal to -4 for the WA BS class, -3 for the MR BS class and -6 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. + +**Table 7.7.5.1-2: Interfering signals for intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge | Interfering signal centre frequency offset from the Base Station RF Bandwidth edge [MHz] | Type of interfering signal | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------------------| +| E-UTRA 1.4 MHz | ±2.0 (BC1 and BC3) / ±2.1 (BC2) | CW | +| | ±4.9 | 1.4MHz E-UTRA signal | +| E-UTRA 3 MHz or E-UTRA with NB-IoT in-band | ±4.4 (BC1 and BC3) / ±4.5 (BC2) | CW | +| | ±10.5 | 3MHz E-UTRA signal | +| UTRA FDD and E-UTRA or E-UTRA with NB-IoT in-band/guard band 5 MHz | ±7.5 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 10 MHz | ±7.375 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 15 MHz | ±7.25 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 20 MHz | ±7.125 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| GSM/EDGE | ±7.575 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NB-IoT standalone | ±7.575 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| 1.28 Mcps UTRA TDD | ±2.3 (BC3) | CW | +| | ±5.6 (BC3) | 1.28Mcps UTRA TDD signal | +| NR 5 MHz or NR with NB-IoT operation in NR in-band | ±7.5 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 10 MHz or NR with NB-IoT operation in NR in-band | ±7.465 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 15 MHz or NR with NB-IoT operation in NR in-band | ±7.43 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 20 MHz or NR with NB-IoT operation in NR in-band | ±7.395 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 25 MHz or NR with NB-IoT operation in NR in-band | ±7.465 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 30 MHz or NR | ±7.43 | CW | + +| | | | +|------------------------------------------------------------|-------|---------------------| +| with NB-IoT operation in NR in-band | ±25 | 20MHz E-UTRA signal | +| | | | +| NR 35 MHz or NR with NB-IoT operation in NR in-band | ±7.44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 40 MHz or NR with NB-IoT operation in NR in-band | ±7.45 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 45 MHz or NR with NB-IoT operation in NR in-band | ±7.37 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 50 MHz or NR with NB-IoT operation in NR in-band | ±7.35 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 60 MHz | ±7.49 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 70 MHz | ±7.42 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 80 MHz | ±7.44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 90 MHz | ±7.46 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 100 MHz | ±7.48 | CW | +| | ±25 | 20MHz E-UTRA signal | + +### 7.7.5.2 General narrowband intermodulation test requirement + +Interfering signals shall be a CW signal and an E-UTRA 1RB signal, as specified in Annex A. + +The requirement is applicable outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges or Maximum Radio Bandwidth edges. + +For BS operating in non-contiguous spectrum within each supported operating band, the requirement applies in addition inside any sub-block gap in case the sub-block gap is at least as wide as the channel bandwidth of the E-UTRA interfering signal in Table 7.7.5.2-2. The interfering signal offset is defined relative to the sub-block edges inside the gap. + +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 as wide as the E-UTRA interfering signal in Table 7.7.5.2-2. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +For the wanted signal at the assigned channel frequency and two interfering signals coupled to the Base Station antenna input, using the parameters in Table 7.7.5.2-1 and 7.7.5.2-2, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [3], clause 7.2. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.105 [4], clause 7.2. +- For any measured GSM/EDGE carrier, the conditions are specified in TS 45.005 [6], Annex P.2.2. + +- For any measured NB-IoT carrier (standalone or operating in E-UTRA in-band/guard band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 36.104 [5], clause 7.2. +- For any measured NB-IoT carrier (operating in NR in-band), the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. +- Maximum throughput of the reference measurement channel defined in TS 38.104 [27], clause 7.2. + +**Table 7.7.5.2-1: General narrowband intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] | Type of interfering signal | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------|----------------------------| +| Wide Area BS | -52 | $P_{\text{REFSENS}} + x$ dB
(NOTE 1) | See Table 7.7.5.2-2 | +| Medium Range BS | -47 | | | +| Local Area BS | -44 | | | +| NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth, see clause 7.2 in TS 37.104.
"x" is equal to 6 in case of NR, NB-IoT, E-UTRA or UTRA wanted signals and equal to 3 in case of GSM/EDGE wanted signal. "x" is specified in Table 7.7.5.2-1a for NB-IoT | | | | + +**Table 7.7.5.2-2: Interfering signals for narrowband intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge or sub-block edge | Interfering signal centre frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap [kHz] | Type of interfering signal | +|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| E-UTRA 1.4 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±970 (BC1 and BC3) / ±790 (BC2) | 1.4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band 3 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±960 (BC1 and BC3) / ±780 (BC2) | 3.0 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 5 MHz | ±360 (NOTE 3) | CW | +| | ±1060 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 10 MHz (NOTE 2) | ±325 (NOTE 3) | CW | +| | ±1240 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 15 MHz (NOTE 2) | ±380 (NOTE 3) | CW | +| | ±1600 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA with NB-IoT in-band/guard band 20 MHz (NOTE 2) | ±345 (NOTE 3) | CW | +| | ±1780 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| UTRA FDD | ±345 (BC1 and BC2) | CW | +| | ±1780 (BC1 and BC2) | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| GSM/EDGE | ±340 | CW | +| | ±880 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| NB-IoT standalone | ±340 | CW | +| | ±880 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| 1.28Mcps UTRA TDD | ±190 (BC3) | CW | +| | ±970 (BC3) | 1.4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| NR 5 MHz or NR with NB-IoT operation in NR in-band | ±360 | CW | +| | ±1420 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| NR 10 MHz or NR with NB-IoT operation in NR in-band | ±370 | CW | +| | ±1960 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| NR 15 MHz or NR with NB-IoT operation in NR in-band | ±380 | CW | + +| | | | +|---------------------------------------------------------------------------|------------|----------------------------------------| +| band
(Note 2) | $\pm 1960$ | 5 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 20 MHz or NR
with NB-IoT
operation in NR in-
band
(Note 2) | $\pm 390$ | CW | +| | $\pm 2320$ | 5 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 25 MHz or NR
with NB-IoT
operation in NR in-
band
(Note 2) | $\pm 325$ | CW | +| | $\pm 2350$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 30 MHz or NR
with NB-IoT
operation in NR in-
band
(Note 2) | $\pm 335$ | CW | +| | $\pm 2350$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 35 MHz or NR
with NB-IoT
operation in NR in-
band (Note 2) | $\pm 345$ | CW | +| | $\pm 2710$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 40 MHz or NR
with NB-IoT
operation in NR in-
band
(Note 2) | $\pm 355$ | CW | +| | $\pm 2710$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 45 MHz or NR
with NB-IoT
operation in NR in-
band (Note 2) | $\pm 365$ | CW | +| | $\pm 2710$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 50 MHz or NR
with NB-IoT
operation in NR in-
band
(Note 2) | $\pm 375$ | CW | +| | $\pm 2710$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 60 MHz
(Note 2) | $\pm 395$ | CW | +| | $\pm 2710$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 70 MHz
(Note 2) | $\pm 415$ | CW | +| | $\pm 2710$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 80 MHz
(Note 2) | $\pm 435$ | CW | +| | $\pm 2710$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 90 MHz
(Note 2) | $\pm 365$ | CW | +| | $\pm 2530$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | +| NR 100 MHz
(Note 2) | $\pm 385$ | CW | +| | $\pm 2530$ | 20 MHz E-UTRA signal, 1 RB
(NOTE 1) | + +NOTE 1: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the Base Station RF Bandwidth edge or sub-block edge inside a gap. + +NOTE 2: This requirement shall apply only for an E-UTRA FRC A1-3 or NR G-FRC mapped to the frequency range at the channel edge adjacent to the interfering signals. + +NOTE 3: The frequency offset shall be adjusted to accommodate the IMD product to fall in the NB-IoT RB for NB-IoT in-band/guard band operation. + +NOTE 4: The frequency offset shall be adjusted to accommodate the IMD product to fall in the NB-IoT RB for NB-IoT in-band/guard band operation. + +NOTE 5: If a BS RF receiver fails the test of the requirement, the test shall be performed with the CW interfering signal frequency shifted away from the wanted signal by 180 kHz and the E-UTRA interfering signal frequency shifted away from the wanted signal by 360 kHz. If the BS RF receiver still fails the test after the frequency shift, then the BS RF receiver shall be deemed to fail the requirement. + +### 7.7.5.3 Additional narrowband intermodulation test requirement for GSM/EDGE + +The GSM/EDGE MC-BTS receiver intermodulation test requirements are stated in TS 51.021 [11], applicable parts of clause 7.7, shall apply for GSM/EDGE carriers. + +The conditions specified in TS 45.005 [6], Annex P.2.2 apply for the GSM/EDGE intermodulation requirement. + +## 7.8 In-channel selectivity + +### 7.8.1 Definition and applicability + +In-channel selectivity (ICS) is a measure of the receiver ability to receive a wanted signal at its assigned resource block locations in the presence of an interfering signal received at a larger power spectral density. In this condition a throughput requirement shall be met for a specified reference measurement channel. This requirement is applicable for NR, NB-IoT operation in NR in-band ,E-UTRA carriers and E-UTRA with NB-IoT in-band operation carrier. + +### 7.8.2 Minimum requirement + +The minimum requirement is in TS 37.104 [2] clause 7.8.1. + +### 7.8.3 Test purpose + +The purpose of this test is to verify the BS receiver ability to suppress the IQ leakage. + +### 7.8.4 Method of testing + +For this requirement Tables 5.1-1 and 5.2-1 refer to single-RAT specifications; see clause 5. The following shall apply: + +- For references to TS 36.141 [9], the method of test is specified in TS 36.141 [9], clause 7.4.4. +- For references to TS 38.141-1 [26], the method of test is specified in TS 38.141-1 [26], clause 7.8.4. + +In addition, for a multi-band capable BS, the following step shall apply: + +- For multi-band capable BS and single band tests, repeat the tests per involved band with no carrier activated in the other band. For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +### 7.8.5 Test requirements + +The test requirements are in TS 36.141 [9], clause 7.4.5 and in TS 38.141-1 [26], clause 7.8.5. + +--- + +## 8 Performance requirements + +Void + +## Annex A (normative): Characteristics of interfering signals + +### A.1 UTRA FDD interfering signal + +The UTRA FDD interfering signal shall be a DPCH containing the DPCCH and one DPDCH. The data content for each channelization code shall be uncorrelated with each other and to the wanted signal and spread and modulated according to clause 4 of TS 25.213. Further characteristics of DPDCH and DPCCH are specified in Table A.1-1. + +**Table A.1-1: Characteristics of UTRA FDD interfering signal** + +| Channel | Bit Rate | Spreading Factor | Channelization Code | Relative Power | +|----------------------------------------------------------------------------------------------------------|----------|------------------|---------------------|----------------| +| DPDCH | 240 kbps | 16 | 4 | 0 dB | +| DPCCH | 15 kbps | 256 | 0 | -5.46 dB | +| NOTE: The DPDCH and DPCCH settings are chosen to simulate a signal with realistic Peak to Average Ratio. | | | | | + +### A.2 UTRA TDD interfering signal + +The UTRA TDD interfering signal shall be 1.28 Mcps UTRA TDD signal with one code. The data content shall be uncorrelated to the wanted signal. They are specified in Table A.2-1. + +**Table A.2-1: Characteristics of UTRA TDD interfering signal** + +| UTRA TDD option | Type of Interfering Signal | +|----------------------------------------------------------------------------------------------------|------------------------------------------| +| 1.28 Mcps UTRA TDD | 1,28 Mcps UTRA TDD signal with one code* | +| NOTE *: The channelisation code ID and Midamble shift shall be different with the wanted signal's. | | + +### A.3 E-UTRA interfering signal + +The E-UTRA interfering signal shall be a PUSCH containing data and reference symbols. Normal CP is used. The data content shall be uncorrelated to the wanted signal and modulated according to clause 5 of TS 36.211. Mapping of PUSCH modulation to receiver requirement are specified in Table A.3-1. + +**Table A.3-1: Modulation of the E-UTRA interfering signal** + +| Receiver requirement | Modulation | +|--------------------------|------------| +| Narrowband blocking | QPSK | +| Receiver intermodulation | QPSK | + +--- + +## Annex B (normative): Environmental requirements for the BS equipment + +### B.1 General + +For each test in the present document, the environmental conditions under which the BS is to be tested are defined. The environmental conditions and class shall be from the relevant IEC specifications or the corresponding ETSI specifications. + +--- + +### B.2 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 B.1. + +**Table B.1: 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. + +--- + +### B.3 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 60721-3-3 [17] or ETSI EN 300 019-1-3 [19] ("Stationary use at weather protected locations"); +- 2) The equipment class for the equipment under test, as defined in the IEC 60721-3-4 [18] or ETSI EN 300 019-1-4 [20] ("Stationary use at non weather protected locations"); +- 3) The equipment that does not comply to the mentioned classes, the relevant classes from IEC 60721 [16] 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. + +#### B.3.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 60068-2-1 [21]. + +##### 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 60068-2-2 [22]. + +NOTE: It is recommended that the equipment is made fully operational prior to the equipment being taken to its lower operating temperature. + +--- + +## B.4 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 60068-2-6 [23]. Other environmental conditions shall be within the ranges specified in clause B.2. + +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. + +--- + +## B.5 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 60068-2-1 [21] Test Ab/Ad and IEC 60068-2-2 [22] 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 60068-2-1 [21] Test Ab/Ad and IEC 60068-2-2 [22] Test Bb/Bd: Dry Heat. + +--- + +## B.6 Measurement of test environments + +The measurement accuracy of the BS test environments shall be. + +| | | +|----------------------|------------------| +| Pressure: | $\pm 5$ kPa. | +| Temperature: | $\pm 2$ degrees. | +| Relative Humidity: | $\pm 5$ %. | +| DC Voltage: | $\pm 1,0$ %. | +| AC Voltage: | $\pm 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. + +--- + +## Annex C (informative): Test Tolerances and Derivation of test requirements + +The test requirements explicitly defined in this specification have been calculated by relaxing the minimum requirements of the core specification using the Test Tolerances defined here. 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 the following tables. + +Test requirements which are included by reference to TS 25.141 [10], TS 25.142[12], TS 36.141[9] or TS 51.021[11] have been calculated within the referred test specification using the Test Tolerances defined therein. + +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.). + +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 where the Test System uncertainty is greater than that allowed in clause 4.1.2. 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 this Annex. + +Unless otherwise stated, the uncertainties in clause 4.1.2 apply to the Test System for testing E-UTRA, UTRA, GSM/EDGE and NB-IoT MSR BS. + +--- + +## C.1 Measurement of transmitter + +**Table C.1-1: Derivation of test requirements (Transmitter tests)** + +| Test | Minimum requirement in TS 37.104 | Test Tolerance (TT) | Test requirement | +|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2.1 Base Station maximum output power |

UTRA, E-UTRA and NR

In normal conditions:
within \pm 2 dB of manufacturer's rated output power

In extreme conditions:
within \pm 2.5 dB of manufacturer's rated output power

GSM/EDGE or standalone NB-IoT

In normal conditions:
within \pm 2 dB of manufacturer's rated output power

In extreme conditions:
within \pm 2.5 dB of manufacturer's rated output power

|

0.7 dB, f \leq 3.0 GHz

1.0 dB, 3.0 GHz < f \leq 4.2 GHz

0.7 dB, f \leq 3.0 GHz

1.0 dB, 3.0 GHz < f \leq 4.2 GHz

1.0 dB

1.0 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, f \leq 3.0 GHz;
within +3 dB and -3 dB of the manufacturer's rated output power, 3.0 GHz < f \leq 4.2 GHz

In extreme conditions:
within +3.2 dB and -3.2 dB of the manufacturer's rated output power, f \leq 3.0 GHz;
within +3.5 dB and -3.5 dB of the manufacturer's rated output power, 3.0 GHz < f \leq 4.2 GHz

In normal conditions:
within +3.0 dB and -3.0 dB of the manufacturer's rated output power

In extreme conditions:
within +3.5 dB and -3.5 dB of the manufacturer's rated output power

| +| 6.4 Transmit ON/OFF power | -85 dBm/MHz. |

2 dB, f \leq 3.0 GHz

2.5 dB, 3.0 GHz < f \leq 4.2 GHz

| Formula: Minimum Requirement + TT | +| 6.6.1.5.1 Transmitter spurious emissions, Mandatory Requirements | Maximum level defined in Table 6.6.1.1.1-1 of TS 37.104 [2]. | 0 dB | Formula: Minimum Requirement + TT | +| 6.6.1.5.2 Transmitter spurious emissions, Mandatory Requirements | Maximum level defined in Table 6.6.1.1.2-1 of TS 37.104 [2]. | 0 dB | Formula: Minimum Requirement + TT | +| 6.6.1.5.3 Transmitter spurious emissions, Additional BC2 Requirement | Maximum level defined in Table 6.6.1.1.3-1 of TS 37.104 [2]. | 0 dB | Formula: Minimum Requirement + TT | +| 6.6.1.5.4 Transmitter spurious emissions, Protection of BS receiver | Maximum level defined in Table 6.6.1.2.1-1 of TS 37.104 [2]. | 0 dB | Formula: Minimum Requirement + TT | +| 6.6.1.5.5 Transmitter spurious emissions, Additional spurious emission requirements | Maximum level defined in Tables 6.6.1.3.1-1 and 6.6.1.3.1-2 of TS 37.104 [2]. | 0 dB | Formula: Minimum Requirement + TT | +| 6.6.1.5.6 Transmitter spurious emissions, Co-location | Maximum level defined in Table 6.6.1.4.1-1 of TS 37.104 [2]. | 0 dB | Formula: Minimum Requirement + TT | + +| | | | | +|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| 6.6.2 Operating band unwanted emissions | For BC1 and BC2: | | Formula: Minimum requirement + TT | +| | Offset < 1 MHz
-14dBm/30kHz to -26dBm/30kHz | 1.5 dB, $f \leq 3.0$ GHz
1.8 dB, $3.0$ GHz < $f \leq 4.2$ GHz | -12.5 dBm/30kHz to
-24.5 dBm/30kHz, $f \leq 3.0$ GHz;
-12.2 dBm/30kHz to
-24.2 dBm/30kHz, $3.0$ GHz < $f \leq 4.2$ GHz | +| | $1$ MHz $\leq$ Offset < $10$ MHz
-13 dBm/1 MHz | 1.5 dB, $f \leq 3.0$ GHz
1.8 dB, $3.0$ GHz < $f \leq 4.2$ GHz | -11.5 dBm/1 MHz, $f \leq 3.0$ GHz;
-11.2 dBm/1 MHz, $3.0$ GHz < $f \leq 4.2$ GHz | +| | $10$ MHz $\leq$ Offsets
-15 dBm/1 MHz | 0 dB | -15 dBm/1 MHz | +| | For BC1 with adjacent standalone NB-IoT carriers: | | | +| | Offset < 0.05 MHz
2 dBm/30kHz to 5 dBm/30 kHz | 1.5 dB | 3.5 dBm/30kHz to 6.5 dBm/30 kHz | +| | $0.05$ MHz $\leq$ Offset
-14 dBm/30kHz to 2 dBm/30 kHz | 1.5 dB | -12.5 dBm/30kHz to 3.5 dBm/30 kHz | +| | For BC2 with adjacent GSM/EDGE or standalone NB-IoT or E-UTRA 1.4 and 3 MHz carriers: | | | +| | Offset < 0.05 MHz
2 dBm/30kHz to 5 dBm/30 kHz | 1.5 dB | 3.5 dBm/30kHz to 6.5 dBm/30 kHz | +| | $0.05$ MHz $\leq$ Offset
-14 dBm/30kHz to 2 dBm/30 kHz | 1.5 dB | -12.5 dBm/30kHz to 3.5 dBm/30 kHz | +| 6.6.3 Occupied bandwidth | BW Channel for E-UTRA and NR
5 MHz for UTRA FDD
1.6 MHz for UTRA TDD
200 kHz for standalone NB-IoT | 0 kHz | Formula: Minimum Requirement + TT | +| 6.6.4 Adjacent Channel Leakage Power Ratio (ACLR) | | | Formula:
ACLR Minimum Requirement - TT
Absolute limit +TT | +| | Paired spectrum ACLR:
45 dB for E-UTRA | 0.8 dB | Paired spectrum ACLR:
44.2 dB | +| | Standalone NB-IoT:
40 dB (ACLR1) | 0.8 dB | Standalone NB-IoT:
39.2 dB (ACLR1) | +| | 50 dB (ACLR2) | 0.8 dB | 49.2 dB (ACLR2) | +| | Unpaired spectrum ACLR:
45 dB for E-UTRA and NR | 0.8 dB | Unpaired spectrum ACLR:
44.2 dB | +| | CACLR:
45 dB for E-UTRA and NR | 0.8 dB | CACLR Minimum Requirement - TT
44.2 dB | +| | 45 dB for UTRA | 0.8 dB | 44.2 dB | +| | Absolute limit -13 dBm/MHz | 0 dB | Absolute limit -13 dBm/MHz | +| | Absolute limit -15 dBm/MHz | 0 dB | Absolute limit -15 dBm/MHz | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------|-------------------------------------------------------------------------------| +| 6.7 Transmitter intermodulation (interferer requirements)
This tolerance applies to the stimulus and not the measurements defined in 6.6.1, 6.6.2 and 6.6.4. | Wanted signal level - interferer level = 30 dB | 0 dB | Formula: Ratio + TT

Wanted signal level - interferer level = 30 + 0 dB | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------|-------------------------------------------------------------------------------| + +--- + +## C.2 Measurement of receiver + +**Table C.2-1: Derivation of test requirements (Receiver tests)** + +| Test | Minimum Requirement in TS 37.104 | Test Tolerance (TT) | Test Requirement | +|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------------------------------------------------------| +| 7.4.5.1 In-band selectivity and blocking, General blocking requirement | Wanted Signal mean power = $P_{\text{REFSENS}} + x$ dB, where x is equal to 6 in case of E-UTRA or UTRA or NB-IoT or NR and equal to 3 in case of GSM/EDGE.

Interferer signal mean power: -40 dBm. | 0 dB | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | +| 7.4.5.2 In-band selectivity and blocking, General narrowband blocking requirement | Wanted Signal mean power = $P_{\text{REFSENS}} + x$ dB, where x is equal to 6 in case of NR or E-UTRA or UTRA and equal to 3 in case of GSM/EDGE, and equal to the following in case of NB-IoT.

For in-band NB-IoT, 1.4 MHz and 3 MHz BW:
$X = 11$
For in-band NB-IoT, 5 MHz BW:
$X = 9$
For in-band NB-IoT, 10MHz, 15MHz and 20MHz BW:
$X = 6$
For guard-band NB-IoT, 5 MHz BW:
$X = 13$
For guard-band NB-IoT, 10MHz, 15MHz and 20MHz BW:
$X = 6$
For standalone NB-IoT, 200 kHz BW:
$X = 12$

For NB-IoT operation in NR in-band:
For 5 MHz BW: $X = 9$
For channel BW $\geq 10$ MHz: $X = 6$ .

Interferer signal mean power: -49 dBm. | 0 dB | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | +| 7.4.5.5 In-band selectivity and blocking, Additional BC3 requirement | Wanted Signal mean power = $P_{\text{REFSENS}} + x$ dB, where x is equal to 6 in case of NR or E-UTRA or UTRA [or NB-IoT].

Interferer signal mean power: -40 dBm. | 0 dB | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | +| 7.5.5.1 Out-of-band blocking, General requirement | Wanted Signal mean power = $P_{\text{REFSENS}} + x$ dB, where x is equal to 6 in case of NR or E-UTRA or UTRA or NB-IoT and equal to 3 in case of GSM/EDGE.

Interferer signal mean power: -15 dBm. | 0 dB | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | +| 7.5.5.2 Out-of-band blocking, Co-location | Wanted Signal mean power = $P_{\text{REFSENS}} + x$ dB, where x is equal to 6 in case of NR or E-UTRA or UTRA or NB-IoT and equal to 3 in case of GSM/EDGE.

Interferer signal mean power: +16 dBm. | 0 dB | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | + +| | | | | +|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------| +| 7.6.5 Receiver spurious emissions | Maximum level defined in Tables 7.6.5.1-1 and 7.6.5.2-1 of TS 37.104 [2]. | 0 dB | Formula: Maximum level + TT | +| 7.7.5.1 Receiver intermodulation, General requirement | Wanted Signal mean power = $P_{\text{REFSENS}} + x$ dB, where x is equal to 6 in case of NR or E-UTRA or UTRA or NB-IoT and equal to 3 in case of GSM/EDGE.

Interferer signal mean power: -48 dBm. | 0 dB | Formula: Wanted signal mean power + TT.

CW interferer signal power unchanged.

Modulated interferer signal power unchanged. | +| 7.7.5.2 Receiver intermodulation, General narrowband requirement | Wanted Signal mean power = $P_{\text{REFSENS}} + x$ dB, where x is equal to 6 in case of NR or E-UTRA or UTRA or NB-IoT and equal to 3 in case of GSM/EDGE.

Interferer signal mean power: -52 dBm. | 0 dB | Formula: Wanted signal mean power + TT.

CW interferer signal power unchanged.

Modulated interferer signal power unchanged. | + +## Annex D (informative): Measurement system set-up + +Example of measurement system set-ups are attached below as an informative annex. + +### D.1 Transmitter + +#### D.1.1 Base station output power, transmitter ON/OFF power, modulation quality, transmitter spurious emissions and operating band unwanted emissions + +![Figure D.1-1: Measuring system set-up for base station output power, transmitter ON/OFF power, modulation quality, transmitter spurious emissions and operating band unwanted emissions](923c3bd3420f28b00798eed4f8eeacd1_img.jpg) + +A block diagram showing a 'BS under test' connected to a 'TX' (transmitter), which is then connected to 'Measurement equipment'. + +Figure D.1-1: Measuring system set-up for base station output power, transmitter ON/OFF power, modulation quality, transmitter spurious emissions and operating band unwanted emissions + +Figure D.1-1: Measuring system set-up for base station output power, transmitter ON/OFF power, modulation quality, transmitter spurious emissions and operating band unwanted emissions + +#### D.1.2 Transmitter intermodulation + +![Figure D.1-2: Measuring system set-up for transmitter intermodulation](40933a545dbad72be6f3656384eed721_img.jpg) + +A block diagram showing a 'BS under test' connected to a 'TX' (transmitter). The output of the 'TX' is connected to a summing junction (represented by a circle with a cross). The output of the summing junction is connected to an 'ATT' (attenuator), which is then connected to a 'Signal generator for the interfering signal'. The output of the summing junction is also connected to a 'Spectrum analyser'. + +Figure D.1-2: Measuring system set-up for transmitter intermodulation + +Figure D.1-2: Measuring system set-up for transmitter intermodulation + +## D.2 Receiver + +### D.2.1 Blocking characteristics + +![Block diagram of the measuring system set-up for blocking characteristics. It shows two signal generators (one for wanted signal, one for interfering signal) connected to attenuators (ATT1, ATT2). The outputs of the attenuators are combined in a hybrid coupler. One output of the hybrid is connected to the BS under test (RX1, RX2), and the other output is connected to a termination.](587ce8b2f9b66fa0db33410888d35966_img.jpg) + +``` +graph LR; SG1[Signal generator for the wanted signal] --> ATT1[ATT1]; SG2[Signal generator for the interfering signal] --> ATT2[ATT2]; ATT1 --> H1[Hybrid]; ATT2 --> H1; H1 --> RX1[RX1 BS under test]; H1 --> T[Termination]; +``` + +Block diagram of the measuring system set-up for blocking characteristics. It shows two signal generators (one for wanted signal, one for interfering signal) connected to attenuators (ATT1, ATT2). The outputs of the attenuators are combined in a hybrid coupler. One output of the hybrid is connected to the BS under test (RX1, RX2), and the other output is connected to a termination. + +Figure D.2-1: Measuring system set-up for blocking characteristics + +### D.2.2 Receiver spurious emissions + +![Block diagram of the measuring system set-up for receiver spurious emissions. It shows a measurement receiver connected to a TX notch filter. The output of the TX notch filter is connected to a hybrid coupler. One output of the hybrid is connected to the BS under test (RX1, RX2), and the other output is connected to a termination.](df5bcfbbc47175b4c9fa8c54e89663a9_img.jpg) + +``` +graph LR; MR[Measurement receiver] --> TN[TX notch]; TN --> H1[Hybrid]; H1 --> RX1[RX1 BS under test]; H1 --> T[Termination]; +``` + +Block diagram of the measuring system set-up for receiver spurious emissions. It shows a measurement receiver connected to a TX notch filter. The output of the TX notch filter is connected to a hybrid coupler. One output of the hybrid is connected to the BS under test (RX1, RX2), and the other output is connected to a termination. + +Figure D.2-2: Measuring system set-up for receiver spurious emissions + +### D.2.3 Receiver intermodulation + +![Block diagram of the measuring system set-up for receiver intermodulation. It shows three signal generators (wanted signal, CW interfering signal, and modulated interfering signal) connected to attenuators (ATT1, ATT2, ATT3). The outputs of ATT2 and ATT3 are combined in a hybrid coupler. The output of this hybrid is then combined with the output of ATT1 in a second hybrid coupler. One output of the second hybrid is connected to the BS under test (RX1, RX2), and the other output is connected to a termination.](5fd16676038d9a043ba514ae71a784b7_img.jpg) + +``` +graph LR; SG1[Signal generator for the wanted signal] --> ATT1[ATT1]; SG2[Signal generator for the CW interfering signal] --> ATT2[ATT2]; SG3[Signal generator for the modulated interfering signal] --> ATT3[ATT3]; ATT2 --> H1[Hybrid]; ATT3 --> H1; H1 --> H2[Hybrid]; ATT1 --> H2; H2 --> RX1[RX1 BS under test]; H2 --> T[Termination]; +``` + +Block diagram of the measuring system set-up for receiver intermodulation. It shows three signal generators (wanted signal, CW interfering signal, and modulated interfering signal) connected to attenuators (ATT1, ATT2, ATT3). The outputs of ATT2 and ATT3 are combined in a hybrid coupler. The output of this hybrid is then combined with the output of ATT1 in a second hybrid coupler. One output of the second hybrid is connected to the BS under test (RX1, RX2), and the other output is connected to a termination. + +Figure D.2-3: Measuring system set-up for receiver intermodulation + +## Annex E (normative): E-UTRA Test model for BC3 CS3 BS + +### E.0 BC3 CS3 Test model description + +The set-up of physical channels for E-UTRA TDD in part of BC3 CS3, BC3 CS16 and BC3 CS17 (and CS2 when NB-IoT in-band and/or guard band is supported) BS transmitter tests shall be according to the applicable test models shown below. A detailed reference to the applicable test model is made in clause 4.9.2. + +The parameters in 36.141 clause 6.1.1 shall be reused by the test models in E.1 to E.6 (E.2 shall not be used for BC3 CS2 BS testing when NB-IoT in-band and/or guard band is supported) with the following exceptions, + +- Duration is 30 subframes (30ms), e.g. number of frames for the test model is 3. +- Uplink/downlink configuration 1 and special subframe configuration 7 shall be used as shown in table E-1. + +**Table E-1: Configurations** + +| Downlink-to-Uplink
Switch-point
periodicity | Number of UL/DL sub-frames per half frame (10 ms) | | DwPTS | GP | UpPTS | +|---------------------------------------------------|---------------------------------------------------|------|-------|----|-------| +| | DL | UL | | | | +| a) 5ms | a) 2 | a) 2 | a) | | | + +The test models in E.1 to E.6 shall be constructed based on the corresponding test model in 36.141 along with the principles on data mapping between the test models in E.1 to E.6 and the test models in 36.141 Clause 6.1.1.1 to 6.1.1.6 as shown in Table E-2. + +**Table E-2: Numbers () of the boosted PRBs** + +| Frame1 | Subframe 0 | Subframe 1 | Subframe 4 | Subframe 5 | Subframe 6 | Subframe 9 | +|--------|------------|------------|------------|------------|------------|------------| +| Note | NOTE 1 | NOTE 1 | NOTE 2 | NOTE 1 | NOTE 3 | NOTE 1 | + +| Frame2 | Subframe 0 | Subframe 1 | Subframe 4 | Subframe 5 | Subframe 6 | Subframe 9 | +|--------|------------|------------|------------|------------|------------|------------| +| Note | NOTE 1 | NOTE 1 | NOTE 4 | NOTE 1 | NOTE 3 | NOTE 1 | + +| Frame3 | Subframe 0 | Subframe 1 | Subframe 4 | Subframe 5 | Subframe 6 | Subframe 9 | +|--------|------------|------------|------------|------------|------------|------------| +| Note | NOTE 5 | NOTE 3 | NOTE 6 | NOTE 7 | NOTE 3 | NOTE 8 | + +NOTE 1: The data in this subframe shall re-use the same data as specified in the corresponding subframe of the corresponding test models in 36.141 clause 6.1.1. + +NOTE 2: The data in this subframe shall re-use the same data as specified in subframe 7 of Frame 1 in the corresponding test model in 36.141 clause 6.1.1. + +NOTE 3: The data in this subframe shall re-use the same data as specified in subframe 1 of Frame 1 in the corresponding test model in 36.141 clause 6.1.1. + +NOTE 4: The data in this subframe shall re-use the same data as specified in subframe 8 of Frame 1 in the corresponding test model in 36.141 clause 6.1.1. + +NOTE 5: The data in this subframe shall re-use the same data as specified in subframe 7 of Frame 2 in the corresponding test model in 36.141 clause 6.1.1. + +NOTE 6: The data in this subframe shall re-use the same data as specified in subframe 8 of Frame 2 in the corresponding test model in 36.141 clause 6.1.1. + +NOTE 7: The data in this subframe shall re-use the same data as specified in subframe 6 of Frame 1 in the corresponding test model in 36.141 clause 6.1.1. + +NOTE 8: The data in this subframe shall re-use the same data as specified in subframe 6 of Frame 2 in the corresponding test model in 36.141 clause 6.1.1. + +## E.0A BC3 CS16/17 Test model description + +The set-up of physical channels for NR TDD in part of BC3 CS16/17 BS transmitter tests shall be according to the applicable test models shown below. A detailed reference to the applicable test model is made in clause 4.9.2. + +The parameters in TS 38.141-1 [26] clause 4.9.2.2 shall be reused by the test models in E.1A to E.6A with the following exceptions: + +- Duration is 3 radio frames (30ms). + +**Table E.0A-1: Configurations** + +| Field name | 15 kHz SCS | 30 kHz SCS | 60 kHz SCS | +|-----------------------------------------------------------|----------------|---------------|-------------------------------| +| Tdd-UL-DL-Configuration | | | | +| referenceSubcarrierSpacing | 15 | 30 | 60 | +| Periodicity (ms) for dl-UL-TransmissionPeriodicity | 5 | 5 | 5 | +| nrofDownlinkSlots | 1 | 2 | 4 | +| nrofDownlinkSymbols | 0 | 0 | 0 | +| nrofUplinkSlots | 0 | 0 | 0 | +| nrofUplinkSymbols | 0 | 0 | 0 | +| Tdd-UL-DL-ConfigDedicated | | | | +| nrofDownlinkSymbols | For Slot#1: 10 | For Slot#3: 6 | For Slot#6:12
For Slot#7:0 | +| nrofUplinkSymbols | For Slot#1: 2 | For Slot#3: 4 | For Slot#6:0
For Slot#7:8 | +| slotIndex | 1 | 3 | 6,7 | +| nrofDownlinkSymbols | 10 | 6 | 12,0 | +| nrofUplinkSymbols | 2 | 4 | 0,8 | +| slotIndex | 2,3 | 4,5,6,7 | 8,9,10,11,12,
13,14,15 | +| symbols | allUplink | allUplink | allUplink | +| slotIndex | 4 | 2,8,9 | 4,5,16,17,18,
19 | +| symbols | allDownlink | allDownlink | allDownlink | + +The test models in E.1a to E.6a shall be constructed based on the corresponding test model in TS 38.141-1 [26]. + +## E.1 E-UTRA Test Model 1.1 (E-TM1.1\_BC3CS3) + +This test model shall be constructed based on E-TM1.1 in TS 36.141 [9] clause 6.1.1.1 according to the data mapping principals elaborated in Table E-2. + +## E.1A NR FR1 Test Model 1.1 (NR-FR1-TM1.1\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM1.1 in TS 38.141-1 [26] clause 4.9.2.2.1. + +--- + +## E.2 E-UTRA Test Model 1.2 (E-TM1.2\_BC3CS3) + +This test model shall be constructed based on E-TM1.2 in TS 36.141 [9] clause 6.1.1.2 according to the data mapping principles elaborated in Table E-2. + +This Test Model shall not be used when testing for BC3 CS2 BS and when NB-IoT in-band and/or guard band is supported. + +--- + +## E.2A NR FR1 Test Model 1.2 (NR-FR1-TM1.2\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM1.2 in TS 38.141-1 [26] clause 4.9.2.2.2. + +--- + +## E.3 E-UTRA Test Model 2 (E-TM2\_BC3CS3) + +This test model shall be constructed based on E-TM2 in TS 36.141 [9] clause 6.1.1.3 according to the data mapping principles elaborated in Table E-2. + +--- + +## E.3A NR FR1 Test Model 2 (NR-FR1-TM2\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM2 in TS 38.141-1 [26] clause 4.9.2.2.3. + +--- + +## E.3B NR FR1 Test Model 2a (NR-FR1-TM2a\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM2a in TS 38.141-1 [26] clause 4.9.2.2.4. + +--- + +## E.3BA NR FR1 Test Model 2b (NR-FR1-TM2b\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM2b in TS 38.141-1 [26] clause 4.9.2.2.4a. + +--- + +## E.3C E-UTRA Test Model 2a (E-TM2a\_BC3CS3) + +This test model shall be constructed based on E-TM2a in TS 36.141 [9] clause 6.1.1.3a according to the data mapping principles elaborated in Table E-2. + +--- + +## E.3D E-UTRA Test Model 2b (E-TM2b\_BC3CS3) + +This test model shall be constructed based on E-TM2b in TS 36.141 [9] clause 6.1.1.3b according to the data mapping principles elaborated in Table E-2. + +--- + +## E.4 E-UTRA Test Model 3.1 (E-TM3.1\_BC3CS3) + +This test model shall be constructed based on E-TM3.1 in TS 36.141 [9] clause 6.1.1.4 according to the data mapping principles elaborated in Table E-2. + +--- + +## E.4Y E-UTRA Test Model 3.1a (E-TM3.1a\_BC3CS3) + +This test model shall be constructed based on E-TM3.1a in TS 36.141 [9] clause 6.1.1.4a according to the data mapping principles elaborated in Table E-2. + +--- + +## E.4Z E-UTRA Test Model 3.1b (E-TM3.1b\_BC3CS3) + +This test model shall be constructed based on E-TM3.1b in TS 36.141 [9] clause 6.1.1.4b according to the data mapping principles elaborated in Table E-2. + +--- + +## E.4ZA NR Test Model 3.1a (NR-FR1-TM3.1a\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM3.1a in TS 38.141-1 [26] clause 4.9.2.2.6. + +--- + +## E.4ZB NR Test Model 3.1b (NR-FR1-TM3.1b\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM3.1b in TS 38.141-1 [26] clause 4.9.2.2.6a. + +--- + +## E.4A NR FR1 Test Model 3.1 (NR-FR1-TM3.1\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM3.1 in TS 38.141-1 [26] clause 4.9.2.2.5. + +--- + +## E.5 E-UTRA Test Model 3.2 (E-TM3.2\_BC3CS3) + +This test model shall be constructed based on E-TM3.2 in TS 36.141 [9] clause 6.1.1.5 according to the data mapping principles elaborated in Table E-2. + +--- + +## E.5A NR FR1 Test Model 3.2 (NR-FR1-TM3.2\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM3.2 in TS 38.141-1 [26] clause 4.9.2.2.7. + +--- + +## E.6 E-UTRA Test Model 3.3 (E-TM3.3\_BC3CS3) + +This test model shall be constructed based on E-TM3.3 in TS 36.141 [9] clause 6.1.1.6 according to the data mapping principles elaborated in Table E-2. + +--- + +## E.6A NR FR1 Test Model 3.3 (NR-FR1-TM3.3\_BC3CS16/17) + +This test model shall be constructed based on NR-FR1-TM3.3 in TS 38.141-1 [26] clause 4.9.2.2.8. + +--- + +## Annex F (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|----|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2009-10 | R4#52bis | R4-093772 | | | | Specification skeleton created from 3GPP TS template | 0.0.1 | +| 2009-11 | R4#53 | R4-094778 | | | | Agreed Text Proposals in RAN4#53:
R4-094507 , "TP for TS 37.141 clause 2 and 3."
R4-094805 , "TP for TS 37.141 clause 4.11; BS Configurations. "
R4-094871 , "TP for TS 37.141 clause 4.1, 4.2, 4.3, 4.4 and 4.5."
R4-094872 , "TP for TS 37.141 Annex C; Test Tolerances and derivation of test requirements. " | 0.1.0 | +| 2010-02 | R4#54 | R4-100579 | | | | Agreed Text Proposals in RAN4 AH#1:
R4-100026 , "TP for TS37.141: Format and interpretation of tests"
R4-100028 , "TP for TS37.141: Selection of configurations for testing"
R4-100241 , "TP for TS 37.141 clause 2, 3 and 4." | 0.2.0 | +| 2010-02 | R4#54 | R4-100975 | | | | Agreed Text Proposals in RAN4#54:
R4-100405 , "TP for TS37.141: Manufacturers declarations of regional and optional requirements"
R4-100863 , "TP Manufacturers declaration of supported RF configurations for section 4.7"
R4-100986 , "TP for TS 37.141 clause 6.6.1; Transmitter spurious emissions"
R4-101036 , "TP MSR test configurations for section 4.8" | 0.3.0 | +| 2010-04 | R4#55 | R4-101576 | | | | Agreed Text Proposals in RAN4 AH#2 and E-mail approved Text Proposals after RAN4 AH#2:
R4-101186 , "TP for TS 37.141 clause 6.6.4; Adjacent Channel Leakage power Ratio (ACLR)"
R4-101207 , "TP for manufacturers declaration, clause 4.7.2"
R4-101208 , "TP TDD test configurations, clause 4.8"
R4-101510 , "TP for requirements and test configuration applicability, clause 5.1"
R4-101511 , "TP for requirements and test configuration applicability, clause 5.2"
R4-101512 , "TP for capability set, clause 4.7.1"
R4-101514 , "TP for update of Transmitter spurious emissions test in TS 37.141"
R4-101515 , "TP for TS 37.141 clause 6.7; Transmitter intermodulation"
R4-101520 , "Text proposal for 37.141 on B, M and T channels definition"
R4-101521 , "TP for TS 37.141, clause 7.2 MSR Receiver reference sensitivity level"
R4-101522 , "TP for TS 37.141 clause 7.3; Dynamic range"
R4-101523 , "TP for TS 37.141 clause 6.6.2;Operating band unwanted emissions"
R4-101524 , "TP for TS 37.141, clause 7.4 MSR Receiver in-band selectivity and blocking"
R4-101525 , "TP for TS 37.141, clause 7.5 MSR Receiver out-of-band-blocking"
R4-101526 , "TP for TS 37.141, clause 7.6 MSR Receiver spurious emissions"
R4-101527 , "TP for TS 37.141, clause 7.7 MSR Receiver intermodulation"
R4-101528 , "TP for TS 37.141, clause 7.8 MSR Receiver in-channel selectivity"
R4-101542 , "TP for TS 37.141 clause 6.6.3: Occupied bandwidth" | 0.4.0 | +| 2010-05 | R4#55 | R4-102216 | | | | Agreed Text Proposals in RAN4#54:
R4-101882 , "TP for TS 37.141; Transmitter Test uncertainties"
R4-101884 , "TP for TS 37.141; clause 4.4 Operating band update"
R4-101885 , "TP for TS 37.141; Adding missing text in clause 4.11.5 and 4.11.7"
R4-102058 , "Corrections for clause 4.1"
R4-102059 , "Corrections for Annex C"
R4-102060 , "Corrections for clauses 4.9, 4.10"
R4-102061 , "Corrections for clauses 4.11, 4.12"
R4-102062 , "Corrections for clause 5"
R4-102086 , "Corrections to clause 7.1" | 0.5.0 | + +| | | | | | | | | +|--|--|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | | | | R4-102087 , "Corrections to clause 7.2"
R4-102088 , "Corrections to clause 7.3"
R4-102093 , "Corrections to clause 7.8"
R4-102096 , "TS 37.141: TP for Co-existence with services in adjacent frequency bands"
R4-102129 , "Spurious emissions limits and blocking requirements for coexistence with CDMA850"
R4-102173 , "TP for TS 37.141; clause 4.3 Regional Requirements"
R4-102245 , "TP for TS 37.141 clause 6.5.3; Time alignment between transmitter branches"
R4-102249 , "Corrections to clause 7.4"
R4-102250 , "Corrections to clause 7.5"
R4-102251 , "Corrections to clause 7.6"
R4-102252 , "Corrections to clause 7.7"
R4-102273 , "TP for TS 37.141; Clause 6.2 BS output power"
R4-102274 , "TP for Clause 4.9.2"
R4-102275 , "Corrections for clause 6.6.1"
R4-102276 , "Corrections for clause 6.6.2"
R4-102277 , "Corrections for clause 6.6.3"
R4-102278 , "Corrections for clause 6.6.4"
R4-102282 , "Corrections for clause 4.8"
R4-102279 , "TP for TS 37.141; Clause 6.7 Tx IM clarification" | | +|--|--|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | | | | +|---------|-------|-----------|-----|---|--|------------------------------------------------------------------------------------------|--------| +| 2010-06 | RP#48 | RP-100580 | | | | Presentation to TSG RAN plenary. | 1.0.0 | +| 2010-06 | RP#48 | RP-100580 | | | | Approved by TSG RAN plenary. | 9.0.0 | +| 2010-09 | RP-49 | RP-100923 | 002 | 1 | | Clarifications on Base Station transmit and receive configurations | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 003 | 2 | | Annex B: Environmental conditions | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 006 | | | Adding transmitter test tolerances | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 008 | | | Adding test System Uncertainty for transmitter spurious emission tests | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 009 | 1 | | Correction of the Ancillary RF Amplifiers references and references to Annex A, B and D | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 010 | | | Update of the Transmitter characteristics General clause | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 013 | 1 | | Adding Modulation quality and Frequency error test cases | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 014 | | | Correction of the NOTEs in the transmitter intermodulation procedure | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 015 | | | Characteristics of interfering signals | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 021 | 1 | | Test configuration and power allocation completion | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 023 | | | TS 37.141 Clause 6.3; Output power dynamics | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 024 | | | General corrections for the MSR test specification | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 025 | | | Maximum Test system Uncertainty for Occupied bandwidth and Transmitter intermodulation | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 026 | 1 | | Adding test tolerances and test system uncertainty for receiver spurious emissions tests | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 027 | 1 | | Measurement set-ups for transmitter and receiver tests | 9.1.0 | +| 2010-09 | RP-49 | RP-100923 | 028 | | | Modification on testing of time mask of BC3 base station | 9.1.0 | +| 2010-09 | RP-49 | RP-100928 | 022 | | | CR LTE_TDD_2600_US spectrum band definition additions to TS 37.141 | 10.0.0 | +| 2010-12 | RP-50 | RP-101345 | 036 | | | Band XII/12 frequency range | 10.1.0 | +| 2010-12 | RP-50 | RP-101346 | 032 | | | Adding missing Test System Uncertainty for the receiver tests | 10.1.0 | +| 2010-12 | RP-50 | RP-101346 | 034 | | | TS 37.141 Clause 7.7; Receiver intermodulation | 10.1.0 | +| 2010-12 | RP-50 | RP-101356 | 029 | 4 | | Band 42 and 43 parameters for UMTS/LTE 3500 (TDD) for TS 37.141 | 10.1.0 | +| 2010-12 | RP-50 | RP-101361 | 030 | | | Protection of E-UTRA Band 24 | 10.1.0 | +| 2011-04 | RP-51 | RP-110344 | 039 | 1 | | Receiver intermodulation reference correction | 10.2.0 | +| 2011-04 | RP-51 | RP-110352 | 043 | 1 | | Correction of the test port description for TS 37.141 Rel-10 | 10.2.0 | +| 2011-04 | RP-51 | RP-110357 | 044 | - | | Band 42 and 43 co-existence for UMTS/LTE 3500 (TDD) for TS 37.141 | 10.2.0 | +| 2011-06 | RP-52 | RP-110814 | 051 | | | Fixing Band 24 inclusion in TS 37.141 | 10.3.0 | +| 2011-06 | RP-52 | RP-110794 | 053 | | | Modifications to Band 3 to allow LTE Band 3 operation in Japan (Rel-10 TS37.141 CR) | 10.3.0 | +| 2011-06 | RP-52 | RP-110804 | 054 | | | Add Expanded 1900MHz band in 37.141 | 10.3.0 | +| 2011-06 | RP-52 | RP-110794 | 058 | | | Correction of RX spurious emissions for non-GSM/EDGE configurations | 10.3.0 | +| 2011-06 | RP-52 | RP-110802 | 063 | | | Co-existence/co-location between Band 42 and 43 in TS 37.141 | 10.3.0 | +| 2011-06 | RP-52 | RP-110794 | 073 | 1 | | Correction for TS 37.141 | 10.3.0 | +| 2011-06 | RP-52 | RP-110794 | 060 | 1 | | General corrections for TS 37.141 | 10.3.0 | +| 2011-06 | RP-52 | RP-110813 | 056 | 1 | | Add 2GHz S-Band (Band 23) in 37.141 | 10.3.0 | +| 2011-06 | RP-52 | RP-110794 | 071 | 2 | | Correction on Modulation Quality Testing in TS 37.141 | 10.3.0 | +| 2011-06 | RP-52 | RP-110794 | 065 | 2 | | Revision of Time Alignment Error definition | 10.3.0 | +| 2011-06 | RP-52 | RP-110794 | 068 | 1 | | Correction on MSR Test Configuration (Rel-10) | 10.3.0 | +| 2011-09 | RP-53 | RP-111252 | 076 | | | Correction of receiver conformance testing | 10.4.0 | +| 2011-09 | RP-53 | RP-111252 | 083 | | | Correction on TR 37.141 clause 6.6.2.5 | 10.4.0 | +| 2011-09 | RP-53 | RP-111255 | 081 | | | Add Band 22/XXII for LTE/UMTS 3500 (FDD) to TS 37.141 | 10.4.0 | +| 2011-09 | RP-53 | RP-111256 | 085 | | | Introduction of test requirements for MSR-NC in 37.141 | 10.4.0 | +| 2011-09 | RP-53 | RP-111262 | 078 | | | Co-existence and co-location corrections in 37.141 | 10.4.0 | +| 2011-09 | RP-53 | RP-111265 | 066 | 2 | | Introduction of Carrier Aggregation for LTE in TS 37.141 | 10.4.0 | +| 2011-09 | RP-53 | RP-111267 | 084 | 1 | | Two carrier test case for MSR | 10.4.0 | +| 2011-12 | RP-54 | RP-111735 | 086 | | | Definition of multi-carrier configuration | 10.5.0 | +| 2011-12 | RP-54 | RP-111734 | 087 | | | Clarification of general blocking requirements for co-existence in TS 37.141 | 10.5.0 | +| 2011-12 | RP-54 | RP-111735 | 088 | | | CR to TS37.141 Adding the OBW requirements for carrier aggregation | 10.5.0 | +| 2011-12 | RP-54 | RP-111690 | 092 | 1 | | update to improve readability of tables in section 4.4 of 37.141 | 10.5.0 | +| 2011-12 | RP-54 | RP-111735 | 093 | | | Correction of MSR NC requirements | 10.5.0 | + +| | | | | | | | | +|---------|-------|-----------|-----|---|--|--------------------------------------------------------------------------------------------|--------| +| 2011-12 | RP-54 | RP-111683 | 096 | 1 | | Alignment of TC carrier position with channel raster in TS 37.141 (Rel-10) | 10.5.0 | +| 2011-12 | RP-54 | RP-111735 | 097 | | | Clarification of multi-carrier transmission and reception with multiple antenna connectors | 10.5.0 | +| 2011-12 | RP-54 | RP-111687 | 098 | 2 | | TX ON or OFF CR 37.141 | 10.5.0 | +| 2011-12 | RP-54 | RP-111733 | 099 | | | Correction of frequency range for spurious emission requirements | 10.5.0 | +| 2012-03 | RP-55 | RP-120303 | 106 | | | Correction on BS Spurious emissions limits for co-existence with Band 25 uplink | 10.6.0 | +| 2012-03 | RP-55 | RP-120303 | 107 | | | Absolute limit for CACLR: Removal of brackets | 10.6.0 | +| 2012-03 | RP-55 | RP-120304 | 109 | 1 | | Definition of synchronized operation | 10.6.0 | +| 2012-03 | RP-55 | RP-120303 | 110 | 1 | | Introduction of NC operation for TDD in 37.141 | 10.6.0 | +| 2012-03 | RP-55 | RP-120305 | 105 | | | Add Extending 850 MHz Upper Band (814 - 849 MHz) to TS37.141 | 11.0.0 | +| 2012-06 | RP-56 | RP-120770 | 114 | | | Correct maximum test system uncertainty for transmit ON/OFF power | 11.1.0 | +| 2012-06 | RP-56 | RP-120778 | 118 | | | Correcting a test configuration in TS 37.141 | 11.1.0 | +| 2012-06 | RP-56 | RP-120779 | 121 | | | Correction on ACLR procedure and test requirement | 11.1.0 | +| 2012-06 | RP-56 | RP-120771 | 124 | | | Transmitter intermodulation applicability clarification for single-RAT specifications | 11.1.0 | +| 2012-06 | RP-56 | RP-120793 | 125 | | | Introduction of APAC700(FDD) into TS 37.141 | 11.1.0 | +| 2012-06 | RP-56 | RP-120778 | 127 | | | Correction of the manufacturer's declaration | 11.1.0 | +| 2012-06 | RP-56 | RP-120778 | 129 | 1 | | Correction of test case for transmitter intermodulation requirement of BC1 | 11.1.0 | +| 2012-06 | RP-56 | RP-120779 | 131 | | | Corrections for MSR and MSR-NC | 11.1.0 | +| 2012-06 | RP-56 | RP-120777 | 135 | | | Additional BC3 blocking | 11.1.0 | +| 2012-06 | RP-56 | RP-120793 | 136 | 1 | | Introduction of Band 44 | 11.1.0 | +| 2012-06 | RP-56 | RP-120792 | 137 | 2 | | Introduction of e850_LB (Band 27) to TS 37.141 | 11.1.0 | +| 2012-09 | RP-57 | RP-121310 | 139 | - | | Correct the f_offsetmax definition for TS 37.141 | 11.2.0 | +| 2012-09 | RP-57 | RP-121308 | 140 | 2 | | Reusing band 41 requirements for the Japan 2.5G TDD band | 11.2.0 | +| 2012-09 | RP-57 | RP-121310 | 142 | 1 | | Intra-band non-contiguous receiver requirements | 11.2.0 | +| 2012-09 | RP-57 | RP-121310 | 144 | - | | Deleting additional BC3 transmitter intermodulation requirement for NC MSR | 11.2.0 | +| 2012-09 | RP-57 | RP-121300 | 147 | - | | Modifications of frequency ranges on spurious emission requirements for Band 6, 18, 19 | 11.2.0 | +| 2012-09 | RP-57 | RP-121311 | 149 | - | | Clarification of non-contiguous BC1 transmitter intermodulation requirements | 11.2.0 | +| 2012-09 | RP-57 | RP-121311 | 151 | 1 | | Clean-up of ACLR wording for MSR-NC | 11.2.0 | +| 2012-09 | RP-57 | RP-121312 | 153 | - | | BS test uncertainties above 3 GHz | 11.2.0 | +| 2012-09 | RP-57 | RP-121340 | 155 | - | | Modification to increase GSM Carrier Power in MSR BS for Band Category 2 | 11.2.0 | +| 2012-09 | RP-57 | | | | | Editorial correction in Table 6.6.2.5.2-2 | 11.2.1 | +| 2012-12 | RP-58 | RP-121857 | 158 | - | | Correction to additional BS spurious emissions limits for BC2 | 11.3.0 | +| 2012-12 | RP-58 | RP-121859 | 161 | - | | Correction of PHS protection requirement | 11.3.0 | +| 2012-12 | RP-58 | RP-121867 | 165 | - | | Clean up of specification R11 | 11.3.0 | +| 2012-12 | RP-58 | RP-121907 | 166 | - | | Introduction of new BS classes to MSR specification (general parts) | 11.3.0 | +| 2012-12 | RP-58 | RP-121867 | 167 | - | | Correction to test requirements of operating band unwanted emissions | 11.3.0 | +| 2012-12 | RP-58 | RP-121907 | 169 | - | | Introduction of new BS classes to TS37.141 (Transmitter part) | 11.3.0 | +| 2012-12 | RP-58 | RP-121864 | 171 | - | | Transmitter IM correction for MSR-NC | 11.3.0 | +| 2012-12 | RP-58 | RP-121907 | 172 | - | | Introduction of new BS classes to MSR test specification (receiver part) | 11.3.0 | +| 2012-12 | RP-58 | RP-121867 | 175 | - | | Removal of conflicts in ACLR requirement | 11.3.0 | +| 2012-12 | RP-58 | RP-121861 | 178 | - | | Change to CA combination list from table to reference | 11.3.0 | +| 2012-12 | RP-58 | RP-121867 | 180 | - | | Clarification of BS output power test under extreme power supply conditions | 11.3.0 | +| 2012-12 | RP-58 | RP-121902 | 181 | - | | Introduction of Band 29 | 11.3.0 | +| 2012-12 | RP-58 | RP-121857 | 182 | | | Modification to increase GSM Carrier Power in MSR BS for Band Category 2 | 11.3.0 | +| 2013-03 | RP-59 | RP-130274 | 187 | | | Correction to MSR BS classes conformance test requirements | 11.4.0 | +| 2013-03 | RP-59 | RP-130287 | 188 | | | Band 41 requirements for operation in Japan | 11.4.0 | +| 2013-06 | RP-60 | RP-130763 | 189 | | | Correcting Time alignment between transmitter branches title in section 5 in TS37.141 | 11.5.0 | +| 2013-06 | RP-60 | RP-130764 | 193 | | | Corrections to transmitter intermodulation test requirement | 11.5.0 | +| 2013-06 | RP-60 | RP-130764 | 198 | | | Correction on UTRA and E-UTRA multi RAT non-contiguous test configuration | 11.5.0 | +| 2013-06 | RP-60 | RP-130763 | 201 | | | channel raster | 11.5.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2013-06 | RP-60 | RP-130792 | 202 | 1 | | Introduction of Band 30 | 12.0.0 | +| 2013-06 | RP-60 | RP-130790 | 203 | | | Introduction of LTE 450 into TS 37.141 | 12.0.0 | +| 2013-09 | RP-61 | RP-131280 | 207 | | | Correction on reference number | 12.1.0 | +| 2013-09 | RP-61 | RP-131280 | 212 | | | UEM requirement in BC2 for lower BS output power | 12.1.0 | +| 2013-12 | RP-62 | RP-131927 | 215 | | | Clarification of Tx IM requirement for BC1 band supporting non-contiguous operation | 12.2.0 | +| 2013-12 | RP-62 | RP-131934 | 217 | | | Introduction of receiver test requirements for multi-band BS | 12.2.0 | +| 2013-12 | RP-62 | RP-131934 | 219 | | | Introduction of multi-band operation to TS 37.141 (Clause 6)
Partially Implemented: changes to section 6.6.4.5.4 are not implemented as are not based on the latest version of the spec | 12.2.0 | +| 2013-12 | RP-62 | RP-131925 | 223 | | | Correction on capability of test configurations for BC3 | 12.2.0 | +| 2013-12 | RP-62 | RP-131934 | 225 | | | Introduction of Multi-band operation in TS37.141(clause 1~3) | 12.2.0 | +| 2013-12 | RP-62 | RP-131960 | 233 | | | Changes to TS 37.141 for LTE_CA_C_B27 | 12.2.0 | +| 2013-12 | RP-62 | RP-131934 | 235 | | | Introduction of MB-MSR Manufacturer's declaration to TS 37.141 | 12.2.0 | +| 2013-12 | RP-62 | RP-131926 | 242 | | | Introduction of secondary CPICH requirement | 12.2.0 | +| 2013-12 | RP-62 | RP-131934 | 244 | | | Introduction of multi-band BS testing to TS 37.141 (Clauses 4.8 4.11) | 12.2.0 | +| 2013-12 | RP-62 | RP-131934 | 246 | | | Update of TS 37.141 for MB-MSR | 12.2.0 | +| 2013-12 | RP-62 | RP-131934 | 251 | | | Applicability of requirements and test configurations for MB-MSR | 12.2.0 | +| 2013-12 | RP-62 | RP-131967 | 252 | 1 | | Band 41 deployment in Japan | 12.2.0 | +| 03-2014 | RP-63 | RP-140372 | 259 | | | Correction on manufacturer's declaration in TS37.141 | 12.3.0 | +| 03-2014 | RP-63 | RP-140372 | 261 | | | Some corrections for MB-MSR in TS 37.141 | 12.3.0 | +| 03-2014 | RP-63 | RP-140368 | 265 | | | Correction on RF channels | 12.3.0 | +| 03-2014 | RP-63 | RP-140367 | 269 | | | Test models for BC3 BS | 12.3.0 | +| 03-2014 | RP-63 | RP-140367 | 273 | | | Differential accuracy of Primary CCPCH power | 12.3.0 | +| 03-2014 | RP-63 | RP-140368 | 281 | | | Clarification of interfering signals for receiver intermodulation requirement in MSR | 12.3.0 | +| 03-2014 | RP-63 | RP-140372 | 282 | | | Multi-band corrections in 37.141 chapter 6 | 12.3.0 | +| 03-2014 | RP-63 | RP-140372 | 284 | | | Multi-band corrections in 37.141 chapter 7 | 12.3.0 | +| 06-2014 | RP-64 | RP-140910 | 291 | | | Clarification of power allocation for RX test cases in TS 37.141 (Rel-12) | 12.4.0 | +| 06-2014 | RP-64 | RP-140913 | 303 | | | Clarification on definitions and ACLR requirement in TS37.141 | 12.4.0 | +| 06-2014 | RP-64 | RP-140913 | 286 | | | Multi-band corrections in 37.141 chapter 6 | 12.4.0 | +| 06-2014 | RP-64 | RP-140913 | 288 | 1 | | Multi-band corrections in 37.141 chapter 7 | 12.4.0 | +| 06-2014 | RP-64 | RP-140913 | 312 | | | Correction of UEM for Medium Range and Local Area BS | 12.4.0 | +| 06-2014 | RP-64 | RP-140914 | 299 | | | Band 29 correction | 12.4.0 | +| 06-2014 | RP-64 | RP-140918 | 321 | | | Clarification of Foffset-RAT in relation to radio bandwidth in TS 37.141 (Rel-12) | 12.4.0 | +| 06-2014 | RP-64 | RP-140918 | 309 | | | BS output power definitions and testing | 12.4.0 | +| 06-2014 | RP-64 | RP-140926 | 307 | 1 | | Introduction of Band 32/XXXII | 12.4.0 | +| 09-2014 | RP-65 | RP-141526 | 324 | 1 | | Removal of FFS for TC4 | 12.5.0 | +| 09-2014 | RP-65 | RP-141528 | 336 | - | | Correction on UEM related to multi-band operation in TS37.141 | 12.5.0 | +| 09-2014 | RP-65 | RP-141562 | 337 | 2 | | Update of definitions to support supplemental DL in TS37.141 | 12.5.0 | +| 12-2014 | RP-66 | RP-142143 | 351 | | | Correction of procedure for general and narrowband intermodulation | 12.6.0 | +| 12-2014 | RP-66 | RP-142143 | 341 | 1 | | Modification on BC3 MSR BS test model | 12.6.0 | +| 12-2014 | RP-66 | RP-142146 | 357 | | | Tx intermodulation corrections | 12.6.0 | +| 12-2014 | RP-66 | RP-142146 | 359 | | | Multi-band test configurations corrections | 12.6.0 | +| 12-2014 | RP-66 | RP-142143 | 367 | | | Clarification of Capability Set per band | 12.6.0 | +| 03-2015 | RP-67 | RP-150382 | 375 | | | Co-location between Band 42 and Band 43 in TS 37.141 | 12.7.0 | +| 03-2015 | RP-67 | RP-150388 | 382 | | | MB and TDD+FDD | 12.7.0 | +| 07-2015 | RP-68 | RP-150955 | 392 | | | Clarification of parameter P for emission requirements | 12.8.0 | +| 07-2015 | RP-68 | RP-150953 | 393 | | | The applicability of TC4d and TC4e | 12.8.0 | +| 07-2015 | RP-68 | RP-150955 | 402 | | | Some corrections related to RF bandwidth edge | 12.8.0 | +| 07-2015 | RP-68 | RP-150953 | 400 | 1 | | New capability set for excluding GSM/EDGE single-RAT operation | 13.0.0 | +| 12-2015 | RP-70 | RP-152157 | 0422 | 1 | | Introduction of Band 67 to 37.141 | 13.1.0 | +| 12-2015 | RP-70 | RP-152172 | 0427 | - | | Introduction of Band 66 | 13.1.0 | +| 12-2015 | RP-70 | RP-152171 | 0428 | - | | Introduction of Band 65 | 13.1.0 | +| 12-2015 | RP-70 | RP-152173 | 0429 | - | | Introduction of 1447-1467MHz Band into 37.141 | 13.1.0 | +| 12-2015 | RP-70 | RP-152132 | 0432 | - | | BS Spec improvements: TS 37.141 Corrections | 13.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------|--------| +| 12-2015 | RP-70 | RP-152132 | 0435 | - | | Multi-band test configuration clarification | 13.1.0 | +| 12-2015 | RP-70 | RP-152132 | 0438 | - | | Corrections on definition of f_offsetmax for BS operating in multiple bands or non-contiguous spectrum | 13.1.0 | +| 12-2015 | RP-70 | RP-152132 | 0444 | - | | Clarification on the transmitter intermodulation requirement in TS37.141 | 13.1.0 | +| 12-2015 | RP-70 | RP-152132 | 0447 | - | | Correction of Unwanted Emission Mask (UEM) for MSR BS capable of multiband operation | 13.1.0 | +| 03/2016 | RP-71 | RP-160483 | 0448 | 2 | B | Introduction of Band 68 into 37.141 | 13.2.0 | +| 03/2016 | RP-71 | RP-160488 | 0453 | - | A | Band 20 and Band 28 BS co-existence | 13.2.0 | +| 03/2016 | RP-71 | RP-160490 | 0450 | - | F | Correction on spurious emissions for co-existence | 13.2.0 | +| 06/2016 | RP-72 | RP-161140 | 455 | 1 | F | Clarification in MB test configuration TC7b | 13.3.0 | +| 06/2016 | RP-72 | RP-161141 | 456 | 1 | A | Corrections to BS spurious emissions requirements in TS37.141 (Rel-13) | 13.3.0 | +| 06/2016 | RP-72 | RP-161140 | 461 | 1 | F | Corrections on definition of multi-band definition and blocking | 13.3.0 | +| 06/2016 | RP-72 | RP-161134 | 462 | 1 | B | Introduction of Band 46 in TS 37.141 | 13.3.0 | +| 06/2016 | RP-72 | RP-161125 | 460 | - | B | Introduction of Band 70 to 37.141 | 14.0.0 | +| 06/2016 | RP-72 | RP-161124 | 463 | - | B | Introduction of Band 69 to 37.141 | 14.0.0 | +| 09/2016 | RP-73 | RP-161631 | 0467 | - | A | Minor clarifications in MSR NTC1a and NTC3a | 14.1.0 | +| 09/2016 | RP-73 | RP-161784 | 0470 | - | A | TS 37.141 Corrections | 14.1.0 | +| 09/2016 | RP-73 | RP-161633 | 0474 | - | A | TC7b correction | 14.1.0 | +| 12/2016 | RP-74 | RP-162395 | 0475 | 1 | B | CR for TS 37.141: Multi-band testing with 3 or more bands. | 14.2.0 | +| 12/2016 | RP-74 | RP-162379 | 0477 | - | A | CR to TS 37.141 introducing NB-IoT | 14.2.0 | +| 12/2016 | RP-74 | RP-162405 | 0478 | 1 | B | Introduction of Band 48 | 14.2.0 | +| 03/2017 | RP-75 | RP-170600 | 0483 | - | A | Corrections on NB-IoT narrowband intermodulation performance requirement | 14.3.0 | +| 03/2017 | RP-75 | RP-170600 | 0485 | - | A | Corrections on NB-IoT Test Configurations | 14.3.0 | +| 06/2017 | RP-76 | RP-171282 | 0493 | 1 | F | CR on BS for protection of V2X UE in TS 37.141 | 14.4.0 | +| 06/2017 | RP-76 | RP-171297 | 0498 | 1 | A | TS 37.141: Correction of reference | 14.4.0 | +| 06/2017 | RP-76 | RP-171255 | 0775 | 1 | B | CR on eLAA BS for TS 37.141 | 14.4.0 | +| 06/2017 | RP-76 | RP-171302 | 0777 | - | A | Remove NB-IoT inband support for 1.4 MHz - Tests | 14.4.0 | +| 06/2017 | RP-76 | RP-171279 | 0778 | 1 | B | Add NB-IoT support to Band 21 | 14.4.0 | +| 06/2017 | RP-76 | RP-171300 | 0781 | - | A | Narrowband blocking requirement for NB-IoT guard band operation (TS 37.141) | 14.4.0 | +| 06/2017 | RP-76 | RP-171303 | 0783 | - | A | Intermodulation performance requirement for NB-IoT operation (TS 37.141) | 14.4.0 | +| 06/2017 | RP-76 | RP-171302 | 0785 | 1 | A | Testing for BS supporting NB-IoT operation (TS 37.141) | 14.4.0 | +| 09/2017 | RP-77 | RP-171966 | 0787 | - | A | Operating band unwanted emissions for MB MSR BS (TS 37.141) | 14.5.0 | +| 09/2017 | RP-77 | RP-171943 | 0790 | - | F | CR to 37.141: NB-IoT inconsistency with 37.104 | 14.5.0 | +| 09/2017 | RP-77 | RP-171948 | 0788 | 2 | B | Introduction of the FDD L-band (Band 74) into TS 37.141 | 15.0.0 | +| 09/2017 | RP-77 | RP-171946 | 0789 | - | B | CR to 37.141: Introduction of Band 72 | 15.0.0 | +| 09/2017 | RP-77 | RP-171952 | 0791 | - | B | CR to 37.141: Introduction of Band 71 | 15.0.0 | +| 09/2017 | RP-77 | RP-171950 | 0793 | 1 | B | CR to 37.141: Introduction of B75 and B76 | 15.0.0 | +| 09/2017 | RP-77 | RP-171949 | 0794 | 1 | B | Introduction of TDD L-band into TS 37.141 | 15.0.0 | +| 09/2017 | RP-77 | RP-172051 | 0795 | - | B | CR to 37.141: Support of NB-IoT for Bands 4, 14 and 71 | 15.0.0 | +| 2017-12 | RAN#78 | RP-172593 | 0796 | 1 | B | Introduction of Band 73 into TS 37.141 | 15.1.0 | +| 2017-12 | RAN#78 | RP-172613 | 0799 | - | A | CR to 37.141: BS Spurious emissions limits for protection of the BS receiver for B28 in Europe | 15.1.0 | +| 2017-12 | RAN#78 | RP-172605 | 0802 | 1 | A | Corrections for MB MSR BS supporting non-contiguous spectrum operation (TS 37.141) | 15.1.0 | +| 2017-12 | RAN#78 | RP-172584 | 0804 | - | A | CR to 37.141: Corrections to co-location tables for B48 | 15.1.0 | +| 2017-12 | RAN#78 | RP-172594 | 0805 | 1 | B | CR to 37.141: Introduction of Band 49 | 15.1.0 | +| 2017-12 | RAN#78 | RP-172588 | 0806 | - | B | Introduction of Microcell and Picocell NB-IoT BS into 37.141 | 15.1.0 | +| 2018-03 | RAN#79 | RP-180279 | 0807 | - | B | CR to 37.141: Introduction of Band 85 | 15.2.0 | +| 2018-03 | RAN#79 | RP-180287 | 0810 | - | A | Correction to GSM/EDGE output power dynamics | 15.2.0 | +| 2018-03 | RAN#79 | RP-180267 | 0811 | - | F | CR NB-IoT small cells: co-location requirements fix | 15.2.0 | +| 2018-03 | RAN#79 | RP-180281 | 0812 | 1 | B | CR to 37.141: Introduction of new additional unwanted emission limit for L-Band | 15.2.0 | +| 2018-03 | RAN#79 | RP-180278 | 0813 | 1 | B | Introduction of TDD 3.3-3.4GHz band into TS 37.141 | 15.2.0 | +| 2018-06 | RAN#80 | RP-181100 | 0814 | - | F | CR to 37.141: Medium Range BS UEM corrections | 15.3.0 | +| 2018-09 | RAN#81 | RP-181900 | 0815 | 2 | B | Introduction of NB-IoT TDD support | 15.4.0 | +| 2018-09 | RAN#81 | RP-181899 | 0816 | 1 | B | CR of test on BS REFSENS for subPRB feature | 15.4.0 | +| 2018-12 | RAN#82 | RP-182381 | 0828 | - | A | CR to TS 37.141: Clarification on NB-IoT test models | 15.5.0 | +| 2018-12 | RAN#82 | RP-182362 | 0831 | 1 | B | Introduction of NR operation in MSR specification 37.141 | 15.5.0 | +| 2018-12 | RAN#82 | RP-182377 | 0821 | - | B | CR of adding B65 for NB1 | 16.0.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2018-12 | RAN#82 | RP-182375 | 0822 | | F | Removal of CA bands list for E-UTRA | 16.0.0 | +| 2018-12 | RAN#82 | RP-182376 | 0830 | | B | CR to 37.141: Introduction of Band 53 | 16.0.0 | +| 2019-03 | RAN#83 | RP-190415 | 0834 | | A | CR for TS 37.141 Rel-16: Correction of UTRA operation in CS7 | 16.1.0 | +| 2019-03 | RAN#83 | RP-190420 | 0837 | | A | Correction to 256QAM and 1024QAM test models and declarations | 16.1.0 | +| 2019-03 | RAN#83 | RP-190402 | 0839 | | A | Correction to TDD OFF description | 16.1.0 | +| 2019-03 | RAN#83 | RP-190402 | 0843 | | A | CR to TS 37.141: Corrections on transmitter co-existence and co-location requirements | 16.1.0 | +| 2019-03 | RAN#83 | RP-190421 | 0845 | | A | CR to 37.141: clean up for LTE-M related text | 16.1.0 | +| 2019-03 | RAN#83 | RP-190401 | 0847 | | A | CR to 37.141 on Corrections for NR | 16.1.0 | +| 2019-03 | RAN#83 | RP-190402 | 0849 | | A | CR to TS 37.141 – Blocking requirement for MSR | 16.1.0 | +| 2019-06 | RAN#84 | RP-191236 | 0851 | 1 | A | Correction to unwanted emissions mask for bands n7 and n38 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191267 | 0853 | | A | CR to 37.141: Correction on Definition of Capability Sets (CS) | 16.2.0 | +| 2019-06 | RAN#84 | RP-191248 | 0855 | | B | CR to 37.141: Introduction of Band n48 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191236 | 0857 | | A | Correction to 256QAM and 1024QAM test models and declarations for NR and E-UTRA | 16.2.0 | +| 2019-06 | RAN#84 | RP-191242 | 0858 | | B | Introduction of band n14 - CR to TS 37.141 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191246 | 0859 | | B | Introduction of band n30 - CR to TS 37.141 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191250 | 0861 | 1 | B | n65 introduction to 37.141 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191236 | 0863 | | A | Correction to n66 and n70 band information | 16.2.0 | +| 2019-06 | RAN#84 | RP-191256 | 0865 | | B | CR to 37.141: Introduction of Band 87 and 88 | 16.2.0 | +| 2019-06 | RAN#84 | RP-191259 | 0869 | | A | CR to 37.141: Simplification of capability sets definition | 16.2.0 | +| 2019-06 | RAN#84 | RP-191245 | 0870 | | B | Introduce Band n18 to 37.141 | 16.2.0 | +| 2019-09 | RAN#85 | RP-192025 | 0871 | 1 | B | Introduction of requirements for NR + UTRA/GSM combinations | 16.3.0 | +| 2019-09 | RAN#85 | RP-192020 | 0873 | | A | CR to TS 37.141 some clarification as blocking test range Cat.A | 16.3.0 | +| 2019-09 | RAN#85 | RP-192020 | 0875 | | A | CR to TS 37.141 TX&RX spurious emission range clause 6.6.1.5.1&7.6.5.1 Cat.A | 16.3.0 | +| 2019-09 | RAN#85 | RP-192020 | 0877 | | A | CR to TS37.141: removal of Tx diversity for NR (section 6.5.3) | 16.3.0 | +| 2019-09 | RAN#85 | RP-192020 | 0879 | | A | CR to TS37.141 Corrections on NBB requirement (section 7.4) | 16.3.0 | +| 2019-09 | RAN#85 | RP-192020 | 0881 | | A | CR to TS 37.141: CA channel spacing | 16.3.0 | +| 2019-09 | RAN#85 | RP-192030 | 0882 | | F | CR on Protection of SUL band n89 to TS 37.141 | 16.3.0 | +| 2019-09 | RAN#85 | RP-192020 | 0884 | | A | CR to TS 37.141 with addition of reference to data content for test models | 16.3.0 | +| 2019-09 | RAN#85 | RP-192034 | 0885 | 1 | B | n29 introduction to 37.141 | 16.3.0 | +| 2019-09 | RAN#85 | RP-192043 | 0886 | 1 | B | CR of adding LTE B42/B43 for UE category NB1 in R16 | 16.3.0 | +| 2019-09 | RAN#85 | RP-192043 | 0887 | 1 | B | CR of adding LTE B7 for UE category NB1 in R16 | 16.3.0 | +| 2019-09 | RAN#85 | RP-192020 | 0889 | | A | Correction of NTC21 | 16.3.0 | +| 2019-12 | RAN#86 | RP-193014 | 0892 | | B | Introduction of 2010-2025MHz SUL band into Rel-16 TS 37.141 | 16.4.0 | +| 2019-12 | RAN#86 | RP-193002 | 0895 | | A | CR to 37.141 on Receiver Intermodulation signal offset correction | 16.4.0 | +| 2019-12 | RAN#86 | RP-193045 | 0899 | | A | CR to TS 37.141: Correction of references for NB-IoT testing | 16.4.0 | +| 2019-12 | RAN#86 | RP-193002 | 0903 | | A | CR to 37.141: Update of procedure in Modulation quality test | 16.4.0 | +| 2019-12 | RAN#86 | RP-193002 | 0905 | | A | CR to TS 37.141 - CS14-TC22 inconsistency fix | 16.4.0 | +| 2019-12 | RAN#86 | RP-193002 | 0907 | | A | Introduction of channel spacing between E-UTRA and NR carriers | 16.4.0 | +| 2019-12 | RAN#86 | RP-193002 | 0909 | | A | Narrowband blocking corrections | 16.4.0 | +| 2019-12 | RAN#86 | RP-193045 | 0915 | | A | NB-IoT corrections | 16.4.0 | +| 2019-12 | RAN#86 | RP-193150 | 0917 | 1 | B | CR to 37.141 on variable duplex FDD bands | 16.4.0 | +| 2020-03 | RAN#87 | RP-200381 | 0918 | | B | Introduction of n26 | 16.5.0 | +| 2020-03 | RAN#87 | RP-200382 | 0919 | | B | Introduction of n53 | 16.5.0 | +| 2020-03 | RAN#87 | RP-200393 | 0921 | | A | CR to TS 37.141: Update on Tx transient period definition | 16.5.0 | +| 2020-03 | RAN#87 | RP-200410 | 0922 | 1 | B | Introduction of NB-IoT into TS37.141 | 16.5.0 | +| 2020-03 | RAN#87 | RP-200393 | 0926 | | A | CR to TS 37.141 channel spacing R16 catA | 16.5.0 | +| 2020-06 | RAN#88 | RP-200968 | 0927 | | F | CR to TS 37.141: Correction on optional support of NB-IoT operation in NR in-band with CS17 | 16.6.0 | +| 2020-06 | RAN#88 | RP-200984 | 0930 | | A | TS 37.141: Corrections related to Foffset
Note: The corresponding Cat F CR0929 is not implementable and hence CR0930 is not implemented either. | 16.6.0 | +| 2020-06 | RAN#88 | RP-200984 | 0934 | | F | CR to TS 37.141 Rel-16 - Issues with TC applicabilities CS17-CS18 | 16.6.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88 | RP-200984 | 0936 | | A | [R16]CR to TS 37.141 on channel spacing correction | 16.6.0 | +| 2020-06 | RAN#88 | RP-200984 | 0938 | | A | CR to TS37.141[R16]_ Correction on the CA nominal channel spacing catA | 16.6.0 | +| 2020-06 | RAN#88 | RP-200984 | 0940 | | F | CR to 37.141: Rel | 16.6.0 | +| 2020-06 | RAN#88 | RP-200968 | 0928 | 1 | F | CR to TS 37.141: Clarifications on test configurations for NB-IoT operation in NR in-band | 16.6.0 | +| 2020-09 | RAN#89 | RP-201512 | 0946 | | A | CR to TS 37.141: Clarification on manufacturer's declaration of the number of supported NB-IoT carriers | 16.7.0 | +| 2020-09 | RAN#89 | RP-201512 | 0948 | | A | CR to 37.141: Correction to applicability of additional BC3 requirement (Rel-16) | 16.7.0 | +| 2020-12 | RAN#90 | RP-202489 | 0954 | | A | CR to 37.141: Correction to ACLR limit in non-contiguous spectrum (Rel-16) | 16.8.0 | +| 2020-12 | RAN#90 | RP-202510 | 0956 | | A | CR to 37.141 on Removal of additional limit for Band 1 | 16.8.0 | +| 2020-12 | RAN#90 | RP-202510 | 0958 | | A | CR to 37.141 on MSR Blocking correction | 16.8.0 | +| 2020-12 | RAN#90 | RP-202451 | 0949 | - | B | Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.141 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202452 | 0950 | - | B | Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.141 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202448 | 0952 | - | B | CR to TS 37.141: introduction of NR band n13 | 17.0.0 | +| 2021-03 | RAN#91e | RP-210096 | 0959 | - | B | CR for TS 37.141 Introduction of SUL for UL of NR band n24 | 17.1.0 | +| 2021-03 | RAN#91e | RP-210110 | 0960 | 1 | B | CR of adding LTE B24 for UE category NB1/NB2 in R17 | 17.1.0 | +| 2021-03 | RAN#91e | RP-210116 | 0963 | 1 | A | CR to 37.141: Correction to ACLR limit in non-contiguous spectrum (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91e | RP-210097 | 0964 | | B | CR to 37.141: Introduction of n24 requirements | 17.1.0 | +| 2021-03 | RAN#91e | RP-210111 | 0972 | | A | CR to 37.141: Correction to Band 24 requirements (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91e | RP-210121 | 0975 | | A | CR to 37.141 on OBUE table headings and applicability | 17.1.0 | +| 2021-06 | RAN#92 | RP-211076 | 0978 | | A | CR to TS 37.141: Regional requirements for band 41, n41, and n90 in Japan, Rel-17 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0979 | | B | CR to TS 37.141: Introduction of band n67 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0980 | | B | CR to TS 37.141: Introduction of band n85 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211090 | 0983 | | A | CR to 37.141: In-band blocking for multi-band Base Stations | 17.2.0 | +| 2021-06 | RAN#92 | RP-211091 | 0986 | | F | CR to 37.141: Correction of NR bands for MSR BS | 17.2.0 | +| 2021-06 | RAN#92 | RP-211094 | 0989 | 1 | A | CR to 37.141: Introduction of NR-U co-existence requirements (Rel-17) | 17.2.0 | +| 2021-09 | RAN#93 | RP-211909 | 0990 | | B | CR for TS 37.141: introduction of channel bandwidths 35MHz and 45MHz | 17.3.0 | +| 2021-09 | RAN#93 | RP-211925 | 0992 | | F | Big CR for TS 37.141 Maintenance (Rel-17, CAT F) | 17.3.0 | +| 2021-12 | RAN#94 | RP-212856 | 0996 | | A | Big CR for TS 37.141 Maintenance (Rel-17, CAT A) | 17.4.0 | +| 2022-03 | RAN#95 | RP-220349 | 0997 | | B | CR for TS 37.141 on BS RF conformance testing for 1024QAM for NR FR1 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220347 | 0998 | 1 | B | CR to TS37.141 on introduction of upper 700MHz A block | 17.5.0 | +| 2022-03 | RAN#95 | RP-220357 | 1000 | | B | CR to 37.141 on introduction of n102 co-existence requirements | 17.5.0 | +| 2022-03 | RAN#95 | RP-220331 | 1003 | | F | Big CR for TS 37.141 Maintenance (Rel-17, CAT F) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220376 | 1004 | | B | CR to TS 37.141: RMR 1900MHz band n101 introduction | 17.5.0 | +| 2022-06 | RAN#96 | RP-221675 | 1005 | | F | CR to 37.141: BS RF conformance requirements for 1024QAM in FR1 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221660 | 1008 | | A | CR for TS 37.141 On sweep time for unwanted emission testing (Rel-17) | 17.6.0 | +| 2022-06 | RAN#96 | RP-221673 | 1010 | | B | CR to 37.141 on introduction of n104 co-existence requirements | 17.6.0 | +| 2022-06 | RAN#96 | RP-221684 | 1009 | 1 | B | CR to 37.141 on introduction of n100 co-existence requirements | 17.6.0 | +| 2022-06 | RAN#96 | RP-221669 | 1014 | | B | CR on adding B48 for NB1/NB2 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221664 | 1017 | | A | Big CR for TS 37.141 Maintenance (Rel-17, CAT A) | 17.6.0 | +| 2022-09 | RAN#97-e | RP-222025 | 1020 | | A | Big CR for TS 37.141 Maintenance (Rel-17, CAT A) | 17.7.0 | +| 2022-12 | RAN#98-e | RP-223292 | 1023 | | A | CR to 37.141 - TC22 generation misalignment when supporting multiple NB-IoT standalone carriers | 17.8.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|--------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | RP-223315 | 1024 | | B | CR to 37.141 on introduction of Band 54 | 18.0.0 | +| 2022-12 | RAN#98-e | RP-223319 | 1027 | | B | CR to 37.141 on introduction of Band n105 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230527 | 1028 | | F | Adds reference for additional spurious emission levels for Band 54 | 18.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|----------------------------------------------------------------------------------------------------|--------| +| 2023-03 | RAN#99 | RP-230535 | 1029 | | B | CR to 37.141 on introduction of Band n54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230524 | 1033 | | B | CR related to Introduction of support of NB1/NB2 for LTE TDD Band 54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230508 | 1034 | | A | CR to TS 37.141 - Additional requirements for BC3 BSs | 18.1.0 | +| 2023-06 | RAN#100 | RP-231352 | 1041 | | A | CR to 37.141: Clarification on the OBUE limites when narrow carrier adjacent to the sub block edge | 18.2.0 | +| 2023-06 | RAN#100 | RP-231352 | 1044 | | A | CR to 37.141: Receiver spurious emissions | 18.2.0 | +| 2023-06 | RAN#100 | RP-231362 | 1045 | | B | CR to TS37.141: the introduction of 900 MHz LTE new band | 18.2.0 | +| 2023-09 | RAN#101 | RP-232488 | 1049 | | A | [MSR_NC-Perf] CR to TS 37.141 NR with Multipath fading of GSM for MSR BS | 18.3.0 | +| 2023-09 | RAN#101 | RP-232488 | 1053 | | A | [MSR_NC-Perf] CR to TS 37.141 with correction to interference signal bandwidth for MSR BS | 18.3.0 | +| 2023-09 | RAN#101 | RP-232488 | 1056 | | A | [MSR_NC-Perf] CR to TS 37.141 with the rated output power definition of the test signal for MSR BS | 18.3.0 | +| 2023-09 | RAN#101 | RP-232504 | 1061 | | A | CR to 37.141: Correction to ACLR and CACLR requirement | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 1062 | | B | CR to TS37.141: the introduction of band n106 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233371 | 1063 | | F | [NR_600MHz_APT-Perf] CR to TS37.141: Addition of missing band n105 for co-location requirement | 18.4.0 | +| 2023-12 | RAN#102 | RP-233334 | 1067 | | A | CR to 37.141: Correction to method of test for GSM/EDGE requirements | 18.4.0 | +| 2023-12 | RAN#102 | RP-233337 | 1074 | | A | [MSR_GSM_UTRA_LTE_NR-Perf] CR to 37.141: Power allocation for NC operation | 18.4.0 | +| 2023-12 | RAN#102 | RP-233334 | 1077 | | A | CR to 37.141: Correction to table note for band 66 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 1078 | | B | CR to 37.141 on introduction of Band n31 and n72 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 1079 | | B | CR to 37.141 on introduction of Band n109 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233363 | 1068 | 1 | B | CR to TS 37.141 - Consideration of NR 3 MHz channel bandwidth | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37144/raw.md b/marked/Rel-18/37_series/37144/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..765559247bb92a6db97de4ce07a19d611163b018 --- /dev/null +++ b/marked/Rel-18/37_series/37144/raw.md @@ -0,0 +1,2019 @@ + + +# 3GPP TS 37.144 V18.2.0 (2024-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) and Mobile Station (MS) GSM, UTRA and E-UTRA over the air performance requirements (Release 18)** --- + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +--- + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 General..... | 8 | +| 4.1 Minimum requirements for roaming bands..... | 8 | +| 4.2 Relationship between minimum requirements for roaming bands and test requirements ..... | 8 | +| 4.3 Terminal classes..... | 9 | +| 4.3.1 Mechanical modes ..... | 9 | +| 4.4 UTRA chip rates..... | 9 | +| 5 Frequency bands ..... | 9 | +| 5.1 GSM frequency bands..... | 9 | +| 5.2 UTRA FDD frequency bands..... | 9 | +| 5.3 UTRA TDD frequency bands ..... | 10 | +| 5.4 E-UTRA FDD frequency bands..... | 10 | +| 5.5 E-UTRA TDD frequency bands..... | 10 | +| 6 Transmitter total radiated power ..... | 11 | +| 6.1 Minimum requirement for roaming bands for handheld UE..... | 11 | +| 6.1.1 Beside the head phantom position..... | 11 | +| 6.1.1.1 GSM..... | 11 | +| 6.1.1.2 UTRA FDD..... | 12 | +| 6.1.1.3 UTRA LCR TDD..... | 12 | +| 6.1.2 Beside the head and hand phantom position ..... | 12 | +| 6.1.2.1 UTRA FDD..... | 12 | +| 6.1.2.2 UTRA LCR TDD..... | 13 | +| 6.1.2.3 E-UTRA FDD..... | 13 | +| 6.1.2.4 E-UTRA TDD..... | 13 | +| 6.1.3 Hand phantom browsing mode position..... | 13 | +| 6.1.3.1 UTRA FDD..... | 13 | +| 6.1.3.2 UTRA LCR TDD..... | 14 | +| 6.1.3.3 E-UTRA FDD..... | 14 | +| 6.1.3.4 E-UTRA TDD..... | 14 | +| 6.2 Minimum requirement for roaming bands for LME ..... | 14 | +| 6.2.1 GSM ..... | 15 | +| 6.2.2 UTRA FDD ..... | 15 | +| 6.2.3 UTRA LCR TDD ..... | 15 | +| 6.2.4 E-UTRA FDD ..... | 16 | +| 6.2.5 E-UTRA TDD ..... | 16 | +| 6.3 Minimum requirement for roaming bands for LEE ..... | 16 | +| 6.3.1 GSM ..... | 16 | +| 6.3.2 UTRA FDD..... | 17 | +| 6.3.3 UTRA LCR TDD ..... | 18 | +| 6.3.4 E-UTRA FDD ..... | 18 | +| 6.3.5 E-UTRA TDD ..... | 19 | +| 7 Receiver total radiated sensitivity ..... | 19 | +| 7.1 Minimum requirement for roaming bands for handheld UE..... | 19 | +| 7.1.1 Beside the head phantom position..... | 19 | +| 7.1.1.1 GSM..... | 19 | +| 7.1.1.2 UTRA FDD..... | 20 | +| 7.1.1.3 UTRA LCR TDD..... | 20 | +| 7.1.2 Beside the head and hand phantoms position..... | 21 | + +| | | | +|-------------------------------|------------------------------------------------------------|-----------| +| 7.1.2.1 | UTRA FDD..... | 21 | +| 7.1.2.2 | UTRA LCR TDD..... | 21 | +| 7.1.2.3 | E-UTRA FDD..... | 22 | +| 7.1.2.4 | E-UTRA TDD..... | 22 | +| 7.1.3 | Hand phantom browsing mode position..... | 22 | +| 7.1.3.1 | UTRA FDD..... | 22 | +| 7.1.3.2 | UTRA LCR TDD..... | 22 | +| 7.1.3.3 | E-UTRA FDD..... | 23 | +| 7.1.3.4 | E-UTRA TDD..... | 23 | +| 7.2 | Minimum requirement for roaming bands for LME ..... | 23 | +| 7.2.1 | GSM ..... | 23 | +| 7.2.2 | UTRA FDD ..... | 23 | +| 7.2.3 | UTRA LCR TDD ..... | 24 | +| 7.2.4 | E-UTRA FDD ..... | 24 | +| 7.2.5 | E-UTRA TDD ..... | 24 | +| 7.3 | Minimum requirement for roaming bands for LEE ..... | 24 | +| 7.3.1 | GSM ..... | 25 | +| 7.3.2 | UTRA FDD ..... | 25 | +| 7.3.3 | UTRA LCR TDD ..... | 26 | +| 7.3.4 | E-UTRA FDD ..... | 26 | +| 7.3.5 | E-UTRA TDD ..... | 27 | +| 8 | Receiver total radiated multi-antenna sensitivity..... | 27 | +| 8.1 | Minimum requirement for roaming bands for handheld UE..... | 27 | +| 8.1.1 | Free Space ..... | 27 | +| 8.1.1.1 | E-UTRA FDD..... | 28 | +| 8.1.1.2 | E-UTRA TDD..... | 28 | +| Annex A (normative): | Environmental conditions..... | 30 | +| A.1 | General..... | 30 | +| A.2 | Environmental requirements..... | 30 | +| A.2.2 | Temperature ..... | 30 | +| A.2.3 | Voltage ..... | 30 | +| Annex B (informative): | Recommended performance..... | 31 | +| B.1 | General..... | 31 | +| B.2 | Transmitter total radiated power ..... | 31 | +| B.2.1 | Recommended performance for handheld UE..... | 31 | +| B.2.1.1 | Beside the head phantom position..... | 31 | +| B.2.1.1.1 | GSM..... | 31 | +| B.2.1.1.2 | UTRA FDD..... | 31 | +| B.2.1.1.3 | UTRA LCR TDD..... | 32 | +| B.2.1.2 | Beside the head and hand phantoms position..... | 32 | +| B.2.1.2.1 | UTRA FDD..... | 32 | +| B.2.1.2.2 | UTRA LCR TDD..... | 32 | +| B.2.1.2.3 | E-UTRA FDD..... | 33 | +| B.2.1.2.4 | E-UTRA TDD..... | 33 | +| B.2.1.3 | Hand phantom browsing mode position..... | 33 | +| B.2.1.3.1 | UTRA FDD..... | 33 | +| B.2.1.3.2 | UTRA LCR TDD..... | 33 | +| B.2.1.3.3 | E-UTRA FDD..... | 34 | +| B.2.1.3.4 | E-UTRA TDD..... | 34 | +| B.2.2 | Recommended performance for LME..... | 34 | +| B.2.2.1 | GSM ..... | 34 | +| B.2.2.2 | UTRA FDD ..... | 34 | +| B.2.2.3 | UTRA LCR TDD ..... | 34 | +| B.2.2.4 | E-UTRA FDD ..... | 35 | +| B.2.2.5 | E-UTRA TDD ..... | 35 | +| B.2.3 | Recommended performance for LEE..... | 35 | +| B.2.3.1 | GSM ..... | 35 | + +| | | | +|-------------------------------|-------------------------------------------------|-----------| +| B.2.3.2 | UTRA FDD ..... | 36 | +| B.2.3.3 | UTRA LCR TDD ..... | 36 | +| B.2.3.4 | E-UTRA FDD ..... | 37 | +| B.2.3.5 | E-UTRA TDD ..... | 37 | +| B.3 | Receiver total radiated sensitivity ..... | 37 | +| B.3.1 | Recommended performance for handheld UE..... | 37 | +| B.3.1.1 | Beside the head phantom position..... | 37 | +| B.3.1.1.1 | GSM..... | 37 | +| B.3.1.1.2 | UTRA FDD..... | 38 | +| B.3.1.1.3 | UTRA LCR TDD..... | 38 | +| B.3.1.2 | Beside the head and hand phantoms position..... | 39 | +| B.3.1.2.1 | UTRA FDD..... | 39 | +| B.3.1.2.2 | UTRA LCR TDD..... | 39 | +| B.3.1.2.3 | E-UTRA FDD..... | 40 | +| B.3.1.2.4 | E-UTRA TDD..... | 40 | +| B.3.1.3 | Hand phantom browsing mode position..... | 40 | +| B.3.1.3.1 | UTRA FDD..... | 40 | +| B.3.1.3.2 | UTRA LCR TDD..... | 40 | +| B.3.1.3.3 | E-UTRA FDD..... | 41 | +| B.3.1.3.4 | E-UTRA TDD..... | 41 | +| B.3.2 | Recommended performance for LME..... | 41 | +| B.3.2.1 | GSM ..... | 41 | +| B.3.2.2 | UTRA FDD ..... | 41 | +| B.3.2.3 | UTRA LCR TDD ..... | 41 | +| B.3.2.4 | E-UTRA FDD ..... | 42 | +| B.3.2.5 | E-UTRA TDD ..... | 42 | +| B.3.3 | Recommended performance for LEE..... | 42 | +| B.3.3.1 | GSM ..... | 42 | +| B.3.3.2 | UTRA FDD ..... | 42 | +| B.3.3.3 | UTRA LCR TDD ..... | 43 | +| B.3.3.4 | E-UTRA FDD ..... | 44 | +| B.3.3.5 | E-UTRA TDD ..... | 44 | +| Annex C (informative): | Change history..... | 45 | + +# --- 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). + +Handheld UE requirements are defined for roaming bands for the speech position (beside the head and beside the head and hand) and hand phantom browsing mode position. Laptop mounted equipment requirements are defined for roaming bands for the data transfer position (laptop ground plane phantom). Laptop embedded equipment requirements are defined for roaming bands for the data transfer position (free space). + +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 cannot 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". +- [6] 3GPP TR 25.914: "Measurements of radio performances for UMTS terminals in speech mode" +- [7] 3GPP TR 37.977: "Verification of radiated multi-antenna reception performance of User Equipment (UE)" +- [8] 3GPP TR 37.902: "Measurements of User Equipment (UE) radio performances for LTE/UMTS terminals; Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) test methodology" +- [9] 3GPP TS 36.521-1: "User Equipment (UE) conformance specification Radio transmission and reception; Part 1: Conformance Testing;" +- [10] 3GPP TS 38.161: "NR; User Equipment (UE) TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements; Range 1 Standalone and Range 1 Interworking operation with other radios". + +# 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], TR 37.977 [7] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] or TR 37.977 [7]. + +**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, applicable for LME and LEE devices. + +**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 + +| | | +|-----------------|------------------------------------------------------------------------------------------| +| $TRP_{average}$ | the average measured total radiated power of low, mid and high channel | +| $TRP_{min}$ | the lowest measured total radiated power of each channel within an operating band | +| $TRS_{average}$ | the average measured total radiated sensitivity of low, mid and high channel | +| $TRS_{max}$ | the highest measured total radiated sensitivity of each channel within an operating band | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], TR 37.977 [7] 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] or TR 37.977 [7]. + +| | | +|------|------------------------------------------| +| DUT | Device Under Test | +| OTA | Over The Air | +| TRMS | Total Radiated Multi-antenna Sensitivity | +| 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 device under test (DUT) are declared by the manufacturer. A DUT shall have at least one mechanical mode. If only one mode is supported, then this is defined as the primary. + +## 4.4 UTRA chip rates + +The requirements defined in this specification for UTRA are based on a chip rate of 3.84 Mcps (FDD) and 1.28 Mcps (TDD). + +NOTE: Other chip rates may be considered in future releases. + +# 5 Frequency bands + +## 5.1 GSM frequency bands + +The requirements defined in this specification for GSM apply to the frequency bands defined in Table 5.1-1. + +**Table 5.1-1: GSM frequency bands** + +| Operating band | UL frequencies
MS transmit, BTS receive | DL frequencies
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 | + +## 5.2 UTRA FDD frequency bands + +The requirements defined in this specification for UTRA FDD apply to the frequency bands defined in Table 5.2-1. + +**Table 5.2-1: UTRA FDD frequency bands** + +| Operating Band | UL frequencies
UE transmit, Node B receive | DL frequencies
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 - 845 MHz | 875 - 890 MHz | + +Deployment in other frequency bands is not precluded + +## 5.3 UTRA TDD frequency bands + +The requirements defined in this specification for UTRA TDD apply to the frequency bands defined in Table 5.3-1. + +**Table 5.3-1: UTRA LCR TDD frequency bands** + +| Operating Band | Frequencies | +|----------------|------------------------------------| +| a | 1900 - 1920 MHz
2010 - 2025 MHz | +| b* | 1850 - 1910 MHz
1930 - 1990 MHz | +| c* | 1910 - 1930 MHz | +| d** | 2570 - 2620 MHz | +| e | 2300 - 2400 MHz | +| f | 1880 - 1920 MHz | + +NOTE: Deployment in other frequency bands is not precluded. + +\* Used in ITU Region 2 + +\*\* Used in ITU Region 1 + +## 5.4 E-UTRA FDD frequency bands + +The requirements defined in this specification for E-UTRA FDD apply to the frequency bands defined in Table 5.4-1. + +**Table 5.4-1 E-UTRA FDD operating bands** + +| E-UTRA Operating Band | Uplink (UL) operating band | Downlink (DL) operating band | Duplex Mode | +|-----------------------|--------------------------------------------|--------------------------------------------|------------------| +| | BS receive
UE transmit | BS transmit
UE receive | | +| | F UL_low – F UL_high | F DL_low – F DL_high | | +| 1 | 1920 MHz – 1980 MHz | 2110 MHz – 2170 MHz | FDD | +| 2 | 1850 MHz – 1910 MHz | 1930 MHz – 1990 MHz | FDD | +| 3 | 1710 MHz – 1785 MHz | 1805 MHz – 1880 MHz | FDD | +| 4 | 1710 MHz – 1755 MHz | 2110 MHz – 2155 MHz | FDD | +| 5 | 824 MHz – 849 MHz | 869 MHz – 894 MHz | FDD | +| 7 | 2500 MHz – 2570 MHz | 2620 MHz – 2690 MHz | FDD | +| 8 | 880 MHz – 915 MHz | 925 MHz – 960 MHz | FDD | +| 12 | 699 MHz – 716 MHz | 729 MHz – 746 MHz | FDD | +| 13 | 777 MHz – 787 MHz | 746 MHz – 756 MHz | FDD | +| 19 | 830 MHz – 845 MHz | 875 MHz – 890 MHz | FDD | +| 20 | 832 MHz – 862 MHz | 791 MHz – 821 MHz | FDD | +| 21 | 1447.9 MHz – 1462.9 MHz | 1495.9 MHz – 1510.9 MHz | FDD | +| 28 | 703 MHz – 748 MHz | 758 MHz – 803 MHz | FDD | +| 32 | N/A | 1452 MHz – 1496 MHz | FDD 1 | + +NOTE 1: Restricted to E-UTRA operation when carrier aggregation is configured. The downlink operating band is paired with the uplink operating band (external) of the carrier aggregation configuration that is supporting the configured Pcell. + +Deployment in other frequency bands is not precluded. + +## 5.5 E-UTRA TDD frequency bands + +The requirements defined in this specification for E-UTRA TDD apply to the frequency bands defined in Table 5.5-1. + +Table 5.5-1 E-UTRA TDD operating bands + +| E-UTRA Operating Band | Uplink (UL) operating band
BS receive
UE transmit | | Downlink (DL) operating band
BS transmit
UE receive | | Duplex Mode | +|-----------------------|---------------------------------------------------------|------------------|-----------------------------------------------------------|------------------|--------------------| +| | $F_{UL\_low}$ | $- F_{UL\_high}$ | $F_{DL\_low}$ | $- F_{DL\_high}$ | | +| 38 | 2570 MHz | – 2620 MHz | 2570 MHz | – 2620 MHz | TDD | +| 39 | 1880 MHz | – 1920 MHz | 1880 MHz | – 1920 MHz | TDD | +| 40 | 2300 MHz | – 2400 MHz | 2300 MHz | – 2400 MHz | TDD | +| 41 | 2496 MHz | – 2690 MHz | 2496 MHz | – 2690 MHz | TDD | +| 42 | 3400 MHz | – 3600 MHz | 3400 MHz | – 3600 MHz | TDD | +| 46 | 5150 MHz | – 5925 MHz | 5150 MHz | – 5925 MHz | TDD 1,2 | + +NOTE 1: This band is an unlicensed band restricted to licensed-assisted operation using Frame Structure Type 3 + +NOTE 2: In this version of the specification, restricted to E-UTRA DL operation when carrier aggregation is configured. + +Deployment in other frequency bands is not precluded. + +# 6 Transmitter total radiated power + +## 6.1 Minimum requirement for roaming bands for handheld UE + +The average measured total radiated power (TRP) of low, mid and high channel for handheld UE shall be higher than the average TRP requirement specified in subclauses 6.1.1, 6.1.2 and 6.1.3. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head in case of beside the head phantom and beside the head and hand phantom positions. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements. Average TRP requirement is shown in the column “Average” on the requirement tables. + +$$TRP_{average} = 10 \log \left[ \frac{10^{P_{left\_low}/10} + 10^{P_{left\_mid}/10} + 10^{P_{left\_high}/10} + 10^{P_{right\_low}/10} + 10^{P_{right\_mid}/10} + 10^{P_{right\_high}/10}}{6} \right]$$ + +In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in subclauses 6.1.1, 6.1.2 and 6.1.3. Minimum TRP requirement is shown in the column “Min” on the requirement tables. + +$$TRP_{min} = 10 \log \left[ \min \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$ + +### 6.1.1 Beside the head phantom position + +Beside the head phantom test method is defined in TR 25.914 [6] subclauses 5.1.1 and 5.1.2. + +#### 6.1.1.1 GSM + +Handheld MS TRP minimum performance requirements for GMSK in beside the head phantom position and the primary mechanical mode are defined in Table 6.1.1.1-1. + +Table 6.1.1.1-1: Handheld UE TRP minimum performance requirement for GSM roaming bands in beside the head phantom 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.2 UTRA FDD + +Handheld UE TRP minimum performance requirements for UTRA FDD in beside the head phantom position and the primary mechanical mode are defined in Table 6.1.1.2-1. + +**Table 6.1.1.2-1: Handheld UE TRP minimum performance requirement for UTRA FDD roaming bands in beside the head phantom 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.3 UTRA LCR TDD + +Handheld UE TRP minimum performance requirements for UTRA LCR TDD in beside the head phantom position and the primary mechanical mode are defined in Table 6.1.1.3-1. + +**Table 6.1.1.3-1: Handheld UE TRP minimum performance requirement for UTRA LCR TDD roaming bands in beside the head phantom 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.1.2 Beside the head and hand phantom position + +Beside the head and hand phantom position is defined in TR 25.914 [6] subclauses 5.1.5 and 5.1.6. + +The Wide Grip hand related positioning guideline for talk mode shall be the same as described in TS 38.161 Clause B.3.2.2 [10]. + +#### 6.1.2.1 UTRA FDD + +Handheld UE TRP minimum performance requirements for UTRA FDD in beside the head and hand phantom position and the primary mechanical mode are defined in Table 6.1.2.1-1. + +**Table 6.1.2.1-1: Handheld UE TRP minimum performance requirement for FDD roaming bands in beside the head and hand phantom 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 | - | - | 13,25 | TBD | TBD | TBD | TBD | TBD | +| II | - | - | 13,25 | TBD | TBD | TBD | TBD | TBD | +| III | - | - | TBD | TBD | TBD | TBD | TBD | TBD | +| IV | - | - | TBD | TBD | TBD | TBD | TBD | TBD | +| V | - | - | 9,40 | TBD | TBD | TBD | TBD | TBD | +| VI | - | - | 9,40 | TBD | TBD | TBD | TBD | TBD | +| VII | - | - | TBD | TBD | TBD | TBD | TBD | TBD | +| VIII | - | - | 9,40 | TBD | TBD | TBD | TBD | TBD | +| IX | - | - | TBD | TBD | TBD | TBD | TBD | TBD | +| XIX | - | - | 9,40 | TBD | TBD | TBD | TBD | TBD | + +NOTE 1: Applicable for dual-mode GSM/UMTS. + +NOTE 2: Applicable for devices narrower than 72mm as defined in TR 25.914. + +NOTE 3: Not applicable for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation). + +#### 6.1.2.2 UTRA LCR TDD + +Handheld UE TRP minimum performance requirements for UTRA LCR TDD in beside the head and hand phantom position and the primary mechanical mode are defined in Table 6.1.2.2-1. + +**Table 6.1.2.2-1: Handheld UE TRP minimum performance requirement for UTRA LCR TDD roaming bands beside the head and hand phantom 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 | - | - | TBD | TBD | - | - | - | - | +| b | - | - | TBD | TBD | - | - | - | - | +| c | - | - | TBD | TBD | - | - | - | - | +| d | - | - | TBD | TBD | - | - | - | - | +| e | - | - | TBD | TBD | - | - | - | - | +| f | - | - | TBD | TBD | - | - | - | - | + +NOTE: Applicable for dual-mode GSM /UTRA LCR TDD. + +#### 6.1.2.3 E-UTRA FDD + +#### 6.1.2.4 E-UTRA TDD + +### 6.1.3 Hand phantom browsing mode position + +Hand phantom browsing mode position is defined in TR 25.914 [6] subclauses 5.1.5 and 5.1.7. + +The Wide Grip hand related positioning guideline for browsing mode shall be the same as described in TS 38.161 Clause B.3.1.1 [10]. + +#### 6.1.3.1 UTRA FDD + +Handheld UE TRP minimum performance requirements for UTRA FDD in hand phantom browsing mode position are defined in Table 6.1.3.1-1. + +**Table 6.1.3.1-1: Handheld UE TRP minimum performance requirement for UTRA FDD roaming bands in hand phantom browsing mode 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: Applicable for dual-mode GSM/UMTS. + +#### 6.1.3.2 UTRA LCR TDD + +Handheld UE TRP minimum performance requirements for UTRA LCR TDD UE in hand phantom browsing mode position are defined in Table 6.1.3.2-1. + +**Table 6.1.3.2-1: Handheld UE TRP minimum performance requirement for UTRA LCR TDD roaming bands in hand phantom browsing mode 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: Applicable for dual-mode GSM /UTRA LCR TDD. + +#### 6.1.3.3 E-UTRA FDD + +#### 6.1.3.4 E-UTRA TDD + +## 6.2 Minimum requirement for roaming bands for LME + +The average measured TRP of low, mid and high channel for laptop mounted equipment shall be higher than the average TRP requirement specified in this subclause. The averaging shall be done in linear scale for the TRP results. Average TRP requirement is shown in the column “Average” on the requirement tables. + +$$TRP_{average} = 10 \log \left[ \frac{10^{P_{low}/10} + 10^{P_{mid}/10} + 10^{P_{high}/10}}{3} \right]$$ + +In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in this subclause. Minimum TRP requirement is shown in the column “Min” on the requirement tables. + +$$TRP_{min} = 10 \log \left[ \min \left( 10^{P_{low}/10}, 10^{P_{mid}/10}, 10^{P_{high}/10} \right) \right]$$ + +LME requirements in this clause are defined to be measured with laptop ground plane phantom as defined in TR 25.914 [6] subclauses 5.1.3 and 5.1.4. + +### 6.2.1 GSM + +LME TRP minimum performance requirements for GSM with laptop ground plane phantom in data transfer position are defined in Table 6.2.1-1. + +**Table 6.2.1-1: LME TRP minimum performance requirement for GSM 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. + +### 6.2.2 UTRA FDD + +LME TRP minimum performance requirements for UTRA FDD with laptop ground plane phantom in data transfer position are defined in Table 6.2.2-1. + +**Table 6.2.2-1: LME TRP minimum performance requirement for UTRA FDD in the 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 | 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. + +### 6.2.3 UTRA LCR TDD + +LME TRP minimum performance requirements for UTRA LCR TDD with laptop ground plane phantom in data transfer position are defined in Table 6.2.3-1. + +**Table 6.2.3-1: LME TRP minimum performance requirement for UTRA LCR TDD 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. + +### 6.2.4 E-UTRA FDD + +### 6.2.5 E-UTRA TDD + +## 6.3 Minimum requirement for roaming bands for LEE + +The average measured TRP of low, mid and high channel for laptop embedded equipment shall be higher than the average TRP requirement specified in this subclause. The averaging shall be done in linear scale for the TRP results. Average TRP requirement is shown in the column “Average” on the requirement tables. + +$$TRP_{average} = 10 \log \left[ \frac{10^{P_{low}/10} + 10^{P_{mid}/10} + 10^{P_{high}/10}}{3} \right]$$ + +In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in this subclause. Minimum TRP requirement is shown in the column “Min” on the requirement tables. + +$$TRP_{min} = 10 \log \left[ \min \left( 10^{P_{low}/10}, 10^{P_{mid}/10}, 10^{P_{high}/10} \right) \right]$$ + +LEE requirements in this clause are defined to be measured as defined in TR 25.914 [6]: subclause 5.3.1 applies to notebook devices, and subclause 5.3.2 applies to tablet devices. + +### 6.3.1 GSM + +LEE TRP minimum performance requirements for GSM are defined in Tables 6.3.1-1 and 6.3.1-2. + +**Table 6.3.1-1: Notebook TRP minimum performance requirement for GSM 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. + +Table 6.3.1-2: Tablet TRP minimum performance requirement for GSM 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 tablet devices. + +### 6.3.2 UTRA FDD + +LEE TRP minimum performance requirements for UTRA FDD are defined in Tables 6.3.2-1 and 6.3.2-2. + +Table 6.3.2-1: Notebook TRP minimum performance requirement for UTRA FDD 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 | - | - | 19,0 | 17,5 | 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 | - | - | 18,5 | 16,5 | TBD | TBD | TBD | TBD | +| VII | - | - | TBD | TBD | TBD | TBD | TBD | TBD | +| VIII | - | - | 18,5 | 16,5 | TBD | TBD | TBD | TBD | +| IX | - | - | TBD | TBD | TBD | TBD | TBD | TBD | +| XIX | - | - | 18,5 | 16,5 | TBD | TBD | TBD | TBD | + +NOTE 1: Applicable for multi-mode GSM/UMTS/LTE. +NOTE 2: Applicable for notebook devices. + +NOTE: TRP minimum performance requirements in table 6.3.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not. + +Table 6.3.2-2: Tablet TRP minimum performance requirement for UTRA FDD in the 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 | Min | Average | Min | Average | Min | +| I | - | - | 19 | 17,5 | 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 | - | - | 17 | 15,0 | 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 | - | - | 17 | 15,0 | TBD | TBD | TBD | TBD | + +NOTE 1: Applicable for dual-mode GSM/UMTS. +NOTE 2: Applicable for tablet devices with two antennas. + +### 6.3.3 UTRA LCR TDD + +LEE TRP minimum performance requirements for UTRA LCR TDD are defined in Tables 6.3.3-1 and 6.3.3-2. + +**Table 6.3.3-1: Notebook TRP minimum performance requirement for UTRA LCR TDD 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. + +**Table 6.3.3-2: Tablet TRP minimum performance requirement for UTRA LCR TDD 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 tablet devices. + +### 6.3.4 E-UTRA FDD + +LEE TRP minimum performance requirements for E-UTRA FDD are defined in Table 6.3.4-1 for Tablet devices. + +Table 6.3.4-1: Tablet TRP minimum requirements for E-UTRA FDD 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 | | +| 1 | | | 18.5 | 17.0 | | +| 2 | | | | | | +| 3 | | | 18.5 | 17.0 | | +| 4 | | | | | | +| 5 | | | | | | +| 7 | | | 18.0 | 16.5 | | +| 8 | | | | | | +| 12 | | | | | | +| 13 | | | | | | +| 19 | | | 17.5 | 15.5 | | +| 20 | | | 17.5 | 15.5 | | +| 21 | | | 17.5 | 16.0 | | +| 28 | | | | | | + +NOTE 1: Applicable for multi-mode GSM/UMTS/LTE. +NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS. + +### 6.3.5 E-UTRA TDD + +# 7 Receiver total radiated sensitivity + +## 7.1 Minimum requirement for roaming bands for handheld UE + +The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in subclauses 7.1.1, 7.1.2 and 7.1.3. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head in case of beside the head phantom and beside the head and hand phantom positions. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column “Average” on the requirement tables. + +$$TRS_{average} = 10 \log \left[ 6 / \left( \frac{1}{10^{P_{left\_low}/10}} + \frac{1}{10^{P_{left\_mid}/10}} + \frac{1}{10^{P_{left\_high}/10}} + \frac{1}{10^{P_{right\_low}/10}} + \frac{1}{10^{P_{right\_mid}/10}} + \frac{1}{10^{P_{right\_high}/10}} \right) \right]$$ + +In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in subclauses 7.1.1, 7.1.2 and 7.1.3. Maximum TRS requirement is shown in the column “Max” on the requirement tables. + +$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$ + +### 7.1.1 Beside the head phantom position + +Beside the head phantom test method is defined in TR 25.914 [6] subclauses 5.1.1 and 5.1.2. + +#### 7.1.1.1 GSM + +Handheld MS TRS minimum performance requirements for GMSK in beside the head phantom position and the primary mechanical mode for TCH/FS at 2% class II (RBER) [3] are defined in Table 7.1.1.1-1. + +**Table 7.1.1.1-1: Handheld UE TRS minimum requirements for GSM roaming bands in beside the head phantom position and the primary mechanical mode** + +| Operating band | Unit | 10 > | | +|----------------|------|----------------------|-------| +| | | 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. +NOTE 2: Applicable for dual-mode GSM/UMTS. + +#### 7.1.1.2 UTRA FDD + +Handheld UE TRS minimum performance requirements for UTRA FDD in beside the head phantom position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.1.2-1. + +**Table 7.1.1.2-1: Handheld UE TRS minimum requirements for UTRA FDD roaming bands in beside the head phantom position and the primary mechanical mode** + +| Operating band | Unit | 10 > | | +|----------------|--------------|----------------------|-----| +| | | 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 10> [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 10> level of -98 dBm/3,84 MHz and max 10> 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 10> level of -100 dBm/3,84 MHz and max 10> level of -97 dBm/3,84 MHz shall apply for Band IV. + +#### 7.1.1.3 UTRA LCR TDD + +Handheld UE TRS minimum performance requirements for UTRA LCR FDD in beside the head phantom position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.1.3-1. + +**Table 7.1.1.3-1: Handheld UE TRS minimum requirement for UTRA LCR TDD roaming bands in beside the head phantom position and 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.1.2 Beside the head and hand phantoms position + +Beside the head and hand phantom position is defined in TR 25.914 [6] subclauses 5.1.5 and 5.1.6. + +The Wide Grip hand related positioning guideline for talk mode shall be the same as described in TS 38.161 Clause B.3.2.2 [10]. + +#### 7.1.2.1 UTRA FDD + +Handheld UE TRS minimum performance requirements for UTRA FDD in beside the head and hand phantoms position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.2.1-1. + +**Table 7.1.2.1-1: Handheld UE TRS minimum requirements for UTRA FDD roaming bands in beside the head and hand phantoms position and the primary mechanical mode** + +| Operating band | Unit | ior > | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------|-----| +| | | Average | Max | +| I | dBm/3,84 MHz | -101,00 | TBD | +| II | dBm/3,84 MHz | -99,00 | TBD | +| III | dBm/3,84 MHz | TBD | TBD | +| IV | dBm/3,84 MHz | TBD | TBD | +| V | dBm/3,84 MHz | -96,75 | TBD | +| VI | dBm/3,84 MHz | -96,75 | TBD | +| VII | dBm/3,84 MHz | TBD | TBD | +| VIII | dBm/3,84 MHz | -96,75 | TBD | +| IX | dBm/3,84 MHz | TBD | TBD | +| XIX | dBm/3,84 MHz | -96,75 | TBD | +| 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. | | | | +| NOTE 6: Applicable for devices narrower than 72mm as defined in TR 25.914. | | | | +| NOTE 7: Not applicable for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation). | | | | + +#### 7.1.2.2 UTRA LCR TDD + +Handheld UE TRS minimum performance requirements for UTRA LCR TDD in beside the head and hand phantoms position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.2.2-1. + +**Table 7.1.2.2-1: Handheld UE TRS minimum requirement for UTRA LCR TDD roaming bands in beside the head and hand phantoms position and the primary mechanical mode** + +| Operating band | Unit | ior > | | +|--------------------------------------------------|--------------|-----------------------|-----| +| | | 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: Applicable for dual-mode GSM/UTRA LCR TDD. | | | | + +#### 7.1.2.3 E-UTRA FDD + +#### 7.1.2.4 E-UTRA TDD + +### 7.1.3 Hand phantom browsing mode position + +Hand phantom browsing mode position is defined in TR 25.914 [6] subclauses 5.1.5 and 5.1.7. + +The Wide Grip hand related positioning guideline for browsing mode shall be the same as described in TS 38.161 Clause B.3.1.1 [10]. + +#### 7.1.3.1 UTRA FDD + +Handheld UE TRS minimum performance requirements for UTRA FDD in hand phantom browsing mode position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.3.1-1. + +**Table 7.1.3.1-1: Handheld UE TRS minimum requirements for UTRA FDD roaming bands in hand phantom browsing mode position** + +| Operating band | Unit | ior > | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------|-----| +| | | 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: 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.1.3.2 UTRA LCR TDD + +Handheld UE TRS minimum performance requirements for UTRA LCR TDD in hand phantom browsing mode position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.3.2-1. + +**Table 7.1.3.2-1: Handheld UE TRS minimum requirement for UTRA LCR TDD roaming bands in hand phantom browsing mode position** + +| Operating band | Unit | | | +|--------------------------------------------------|--------------|----------|-----| +| | | 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: Applicable for dual-mode GSM/UTRA LCR TDD. | | | | + +#### 7.1.3.3 E-UTRA FDD + +#### 7.1.3.4 E-UTRA TDD + +## 7.2 Minimum requirement for roaming bands for LME + +The average measured TRS of low, mid and high channel for laptop mounted equipment shall be lower than average TRS requirement specified in this subclause. The averaging shall be done in linear scale for the TRS results. Average TRS requirement is shown in the column “Average” on the requirement tables. + +$$TRS_{average} = 10 \log \left[ 3 / \left( \frac{1}{10^{P_{low}/10}} + \frac{1}{10^{P_{mid}/10}} + \frac{1}{10^{P_{high}/10}} \right) \right]$$ + +In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in this subclause. Maximum TRS requirement is shown in the column “Max” on the requirement tables. + +$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{low}/10}, 10^{P_{mid}/10}, 10^{P_{high}/10} \right) \right]$$ + +### 7.2.1 GSM + +LME TRS minimum performance requirements for GPRS PDTCH/CS1 at 10% BLER [3] with laptop ground plane phantom in data transfer position are defined in Table 7.2.1-1. + +**Table 7.2.1-1: LME TRS minimum requirements for GSM in data transfer position** + +| Operating band | Unit | | | +|-------------------------------------------------------------------------------------|------|----------|-----| +| | | 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. | | | | + +### 7.2.2 UTRA FDD + +LME TRS minimum performance requirements for UTRA FDD with laptop ground plane phantom in data transfer position mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.2.2-1. [The values in the tables are $\hat{I}_r$ for with no interference.] + +**Table 7.2.2-1: LME TRS minimum requirements for UTRA FDD in data transfer position** + +| Operating band | Unit | | | +|----------------|--------------|--------------------|-----| +| | | 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. + +### 7.2.3 UTRA LCR TDD + +LME TRS minimum performance requirements for UTRA LCR TDD with laptop ground plane phantom in data transfer position mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.2.3-1. [The values in the tables are $\hat{I}_r$ for with no interference.] + +**Table 7.2.3-1: LME TRS minimum requirements for UTRA LCR TDD in data transfer position** + +| Operating band | Unit | | | +|----------------|--------------|--------------------|-----| +| | | 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. + +### 7.2.4 E-UTRA FDD + +### 7.2.5 E-UTRA TDD + +## 7.3 Minimum requirement for roaming bands for LEE + +The average measured TRS of low, mid and high channel for laptop embedded equipment shall be lower than average TRS requirements specified in this subclause. The averaging shall be done in linear scale for the TRS results. Average TRS requirement is shown in the column “Average” on the requirement tables. + +$$TRS_{average} = 10 \log \left[ 3 / \left( \frac{1}{10^{P_{low}/10}} + \frac{1}{10^{P_{mid}/10}} + \frac{1}{10^{P_{high}/10}} \right) \right]$$ + +In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in this subclause. Maximum TRS requirement is shown in the column “Max” on the requirement tables. + +$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{low}/10}, 10^{P_{mid}/10}, 10^{P_{high}/10} \right) \right]$$ + +### 7.3.1 GSM + +LEE TRS minimum performance requirements for GPRS PDTCH/CS1 at 10% BLER [3] are defined in Tables 7.3.1-1 and 7.3.1-2. + +**Table 7.3.1-1: Notebook TRS minimum requirements for GSM in data transfer position** + +| Operating band | Unit | ior > | | +|----------------|------|-----------------------|-----| +| | | 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. + +**Table 7.3.1-2: Tablet TRS minimum requirements for GSM in data transfer position** + +| Operating band | Unit | ior > | | +|----------------|------|-----------------------|-----| +| | | 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 tablet devices. + +### 7.3.2 UTRA FDD + +LEE TRS minimum performance requirements for UTRA FDD in data transfer position mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Tables 7.3.2-1 and 7.3.2-2. [The values in the tables are for with no interference.] + +**Table 7.3.2-1: Notebook TRS minimum requirements for UTRA FDD in data transfer position** + +| Operating band | Unit | ior > | | +|----------------|--------------|-----------------------|--------| +| | | Average | Max | +| I | dBm/3,84 MHz | -103,5 | -102,0 | +| 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 | -101,5 | -99,5 | +| VII | dBm/3,84 MHz | TBD | TBD | +| VIII | dBm/3,84 MHz | -101,5 | -99,5 | +| IX | dBm/3,84 MHz | TBD | TBD | +| XIX | dBm/3,84 MHz | -101,5 | -99,5 | + +NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power. +NOTE 2: Applicable for multi-mode GSM/UMTS/LTE. +NOTE 3: Applicable for notebook devices. + +NOTE: TRS minimum performance requirements in table 7.3.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not. + +**Table 7.3.2-2: Tablet TRS minimum requirements for UTRA FDD in data transfer position** + +| Operating band | Unit | or > | | +|----------------|--------------|-----------------------|---------| +| | | Average | Max | +| I | dBm/3,84 MHz | -105,75 | -104,25 | +| 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 | -103 | -101,0 | +| 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 | -103 | -101,0 | + +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 tablet devices with two antennas. + +### 7.3.3 UTRA LCR TDD + +LEE TRS minimum performance requirements for UTRA LCR TDD in data transfer position mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Tables 7.3.3-1 and 7.3.2-2. [The values in the tables are Îor with no interference.] + +**Table 7.3.3-1: LEE TRS minimum requirements for UTRA LCR TDD in data transfer position** + +| Operating band | Unit | | | +|----------------|--------------|----------|-----| +| | | 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. + +**Table 7.3.3-2: Tablet TRS minimum requirements for UTRA LCR TDD in data transfer position** + +| Operating band | Unit | | | +|----------------|--------------|----------|-----| +| | | 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 tablet devices. + +### 7.3.4 E-UTRA FDD + +LEE TRS minimum performance requirements for E-UTRA FDD in data transfer position mode for throughput $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in section 7.3 of TS 36.521-1 [9] and Annex A of TS 36.521-1 [9] are defined in Table 7.3.4-1 for Tablet devices. + +Table 7.3.4-1: Tablet TRS minimum requirements for E-UTRA FDD in data transfer position + +| Operating band | Channel bandwidth | Sensitivity (dBm) | | +|----------------|-------------------|-------------------|--------| +| | | Average | Max | +| 1 | 10 MHz | -93.75 | -92.25 | +| 2 | 10 MHz | | | +| 3 | 10 MHz | -95.0 | -93.5 | +| 4 | 10 MHz | | | +| 5 | 10 MHz | | | +| 7 | 10 MHz | -93.5 | -92.0 | +| 8 | 10 MHz | | | +| 12 | 10 MHz | | | +| 13 | 10 MHz | | | +| 19 | 10 MHz | -91.5 | -89.5 | +| 20 | 10 MHz | -92.5 | -90.5 | +| 21 | 15 MHz | -90.0 | -88.5 | +| 28 | 10 MHz | | | +| 32 | 10 MHz | | | + +NOTE 1: Applicable for multi-mode GSM/UMTS/LTE. +NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS. + +### 7.3.5 E-UTRA TDD + +# 8 Receiver total radiated multi-antenna sensitivity + +## 8.1 Minimum requirement for roaming bands for handheld UE + +### 8.1.1 Free Space + +Requirements in this section are stated for the free space configuration, are applicable to handheld devices, and are not applicable to wrist-worn devices. + +For the reference MPAC methodology and the harmonized RTS methodology defined in [7], the average TRMS of free space data mode portrait (FS\_DMP), free space data mode landscape (FSDML), and free space data mode screen up (FS\_DMSU), as defined in Annex E of TR 37.977 [7], when measured at the mid channel shall be lower than the average TRMS requirements specified in subclauses 8.1.1.1 and 8.1.1.2. The averaging shall be done in linear scale for the TRMS results at these DUT positions. Two average TRMS quantities are calculated from sensitivity measurements at 70% and 95% throughput, respectively. Average TRMS requirement are shown in the column “Average, 70” and “Average, 95” on the requirement tables. + +$$TRMS_{average,70} = 10\log \left[ 3 / \left( \frac{1}{10^{S_{FS\_DMP,70/10}}} + \frac{1}{10^{S_{FS\_DML,70/10}}} + \frac{1}{10^{S_{FS\_DMSU,70/10}}} \right) \right]$$ + +$$TRMS_{average,95} = 10\log \left[ 3 / \left( \frac{1}{10^{S_{FS\_DMP,95/10}}} + \frac{1}{10^{S_{FS\_DML,95/10}}} + \frac{1}{10^{S_{FS\_DMSU,95/10}}} \right) \right]$$ + +Where + +$$S_{MODE,x} = 10\log \left[ 12 / \left( \frac{1}{10^{P_{MODE,x,0/10}}} + \frac{1}{10^{P_{MODE,x,1/10}}} + \dots + \frac{1}{10^{P_{MODE,x,11/10}}} \right) \right]$$ + +Such that *MODE* is one of {*FS\_DMP*, *FS\_DML*, *FS\_DMSU*}, *x* is one of {70, 95}, and {*PMODE,x,0*, ..., *PMODE,x,11*} are the measured sensitivity values at each azimuth position. + +For the reference MPAC methodology and the harmonized RTS methodology defined in [7], if 1 azimuth position does not result in a defined measured sensitivity at 70% or 95% throughput, *SMODE,70* or *SMODE,95* are calculated using the 11 measured sensitivities and the maximum downlink RS-EPRE *PRS-EPRE-MAX* (substitution approach) for the one missing + +result. If 2 azimuth positions do not result in a defined measured sensitivity at 95% throughput, $S_{MODE,95}$ is calculated using the 10 measured sensitivities and $P_{RS-EPRE-MAX}$ for the two missing results. If more azimuth positions result in undefined values for measured sensitivity at the 70% and/or 95% throughput, then the TRMS requirement for the corresponding throughput levels has not been met by such a device. $P_{RS-EPRE-MAX}$ is defined as -80 dBm/15 kHz and is the maximum downlink RS-EPRE supported by the test system. + +#### 8.1.1.1 E-UTRA FDD + +Handheld UE TRMS minimum performance requirements for E-UTRA FDD in free space and the primary mechanical mode for 70% and 95% DL throughput with the reference measurement channel defined in Clause 7 of TR 37.977 [7] are defined in Table 8.1.1.1-1. + +**Table 8.1.1.1-1: Handheld UE TRMS minimum requirements for E-UTRA FDD roaming bands in free space and the primary mechanical mode** + +| Channel Model as defined in clause 8.2 in [7] | | Test 1 | | +|-----------------------------------------------|------------|-----------------------|-------------| +| | | SCME urban micro-cell | | +| Operating band | Unit | or > | | +| | | Average, 70 | Average, 95 | +| 1 | dBm/15 kHz | -94.75 | -92.75 | +| 2 | dBm/15 kHz | TBD | TBD | +| 3 | dBm/15 kHz | -93.75 | -91.75 | +| 4 | dBm/15 kHz | TBD | TBD | +| 5 | dBm/15 kHz | -91.5 | -89.5 | +| 7 | dBm/15 kHz | -92.5 | -90.5 | +| 8 | dBm/15 kHz | TBD | TBD | +| 12 | dBm/15 kHz | TBD | TBD | +| 13 | dBm/15 kHz | TBD | TBD | +| 19 | dBm/15 kHz | -91.5 | -89.5 | +| 20 | dBm/15 kHz | TBD | TBD | +| 28 | dBm/15 kHz | TBD | TBD | +| 32 (1) | dBm/15 kHz | TBD | TBD | + +NOTE 1: Restricted to E-UTRA operation when carrier aggregation is configured. The downlink operating band is paired with the uplink operating band (external) of the carrier aggregation configuration that is supporting the configured Pcell. + +NOTE 2: Applicability for devices supporting 4-receiver architectures is not confirmed. + +#### 8.1.1.2 E-UTRA TDD + +Handheld UE TRMS minimum performance requirements for E-UTRA TDD in free space and the primary mechanical mode for 70% and 95% DL throughput with the reference measurement channel defined in Clause 7 of TR 37.977 [7] are defined in Table 8.1.1.2-1. + +**Table 8.1.1.2-1: Handheld UE TRMS minimum requirements for E-UTRA TDD roaming bands in free space and the primary mechanical mode** + +| | | Test 1 | | +|------------------------------------------------------|-------------|----------------------------------|--------------------| +| Channel Model as defined in clause 8.2 in [7] | | SCME urban micro-cell | | +| Operating band | Unit | <REFIor> | | +| | | Average, 70 | Average, 95 | +| 38 | dBm/15 kHz | -95.5 | -93.5 | +| 39 | dBm/15 kHz | TBD | TBD | +| 40 | dBm/15 kHz | TBD | TBD | +| 41 | dBm/15 kHz | -95.5 | -93.5 | +| 42 | dBm/15 kHz | TBD | TBD | +| 46 (1,2) | dBm/15 kHz | TBD | TBD | + +NOTE 1: This band is an unlicensed band restricted to licensed-assisted operation using Frame Structure Type 3 + +NOTE 2: In this version of the specification, restricted to E-UTRA DL operation when carrier aggregation is configured. + +NOTE 3: Applicability for devices supporting 4-receiver architectures is not confirmed. + +# --- 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 + +All test cases shall be performed in the normal voltage condition with the DUT operated in stand-alone battery powered mode. No extreme voltage testing is required. It is recommended to start testing with a fully charged battery and conclude and/or pause testing before the battery has completely lost its charge. + +# 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 Transmitter total radiated power + +The OTA TRP performance for GSM, UTRA and E-UTRA should be greater or equal than the recommended values in this clause. + +### B.2.1 Recommended performance for handheld UE + +#### B.2.1.1 Beside the head phantom position + +Beside the head phantom test method is defined in TR 25.914 [6] subclauses 5.1.1 and 5.1.2. + +##### B.2.1.1.1 GSM + +**Table B.2.1.1.1-1: Handheld UE TRP recommended performance for GSM in beside the head phantom 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. + +##### B.2.1.1.2 UTRA FDD + +**Table B.2.1.1.2-1: Handheld UE TRP recommended performance for UTRA FDD in beside the head phantom 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 | +| 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. + +##### B.2.1.1.3 UTRA LCR TDD + +**Table B.2.1.1.3-1: Handheld UE TRP recommended performance for UTRA LCR TDD in beside the head phantom 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. + +#### B.2.1.2 Beside the head and hand phantoms position + +##### B.2.1.2.1 UTRA FDD + +**Table B.2.1.2.1-1: Handheld UE TRP recommended performance for UTRA FDD beside the head and hand phantoms 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 | - | - | 16,25 | TBD | TBD | +| II | - | - | 16,25 | TBD | TBD | +| III | - | - | TBD | TBD | TBD | +| IV | - | - | TBD | TBD | TBD | +| V | - | - | 12,40 | TBD | TBD | +| VI | - | - | 12,40 | TBD | TBD | +| VII | - | - | TBD | TBD | TBD | +| VIII | - | - | 12,40 | TBD | TBD | +| IX | - | - | TBD | TBD | TBD | +| XIX | - | - | 12,40 | TBD | TBD | + +NOTE 1: Applicable for dual-mode GSM/UMTS. +NOTE 2: Applicable for devices narrower than 72mm as defined in TR 25.914. +NOTE 3: Not applicable for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation). + +##### B.2.1.2.2 UTRA LCR TDD + +**Table B.2.1.2.2-1: Handheld UE TRP recommended performance for UTRA LCR TDD in beside the head and hand phantoms 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 | | | | +| a | - | TBD | - | - | - | +| b | - | TBD | - | - | - | +| c | - | TBD | - | - | - | +| d | - | TBD | - | - | - | +| e | - | TBD | - | - | - | +| f | - | TBD | - | - | - | + +Note: Applicable for dual-mode GSM/UTRA LCR TDD. + +##### B.2.1.2.3 E-UTRA FDD + +##### B.2.1.2.4 E-UTRA TDD + +#### B.2.1.3 Hand phantom browsing mode position + +##### B.2.1.3.1 UTRA FDD + +Table B.2.1.3.1-1: Handheld UE TRP recommended performance for UTRA FDD in the hand phantom browsing mode 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: Applicable for dual-mode GSM/UMTS. + +##### B.2.1.3.2 UTRA LCR TDD + +Table B.2.1.3.2-1: Handheld UE TRP recommended performance for UTRA LCR TDD in the hand phantom browsing mode 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 | | | | +| a | - | TBD | - | - | - | +| b | - | TBD | - | - | - | +| c | - | TBD | - | - | - | +| d | - | TBD | - | - | - | +| e | - | TBD | - | - | - | +| f | - | TBD | - | - | - | + +Note : Applicable for dual-mode GSM/UTRA LCR TDD. + +##### B.2.1.3.3 E-UTRA FDD + +##### B.2.1.3.4 E-UTRA TDD + +### B.2.2 Recommended performance for LME + +#### B.2.2.1 GSM + +Table B.2.2.1-1: LME TRP recommended performance for GSM 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. + +#### B.2.2.2 UTRA FDD + +Table B.2.2.2-1: LME TRP recommended performance for UTRA FDD 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 | +| 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. + +#### B.2.2.3 UTRA LCR TDD + +Table B.2.2.3-1: LME TRP recommended performance for UTRA LCR TDD 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. + +#### B.2.2.4 E-UTRA FDD + +Table B.2.2.4-1: Tablet TRP recommended performance for E-UTRA FDD 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 | | | | +| 1 | | | 21.0 | | +| 2 | | | | | +| 3 | | | 20.5 | | +| 4 | | | | | +| 5 | | | | | +| 7 | | | 20.0 | | +| 8 | | | | | +| 12 | | | | | +| 13 | | | | | +| 19 | | | 20.0 | | +| 20 | | | 19.5 | | +| 21 | | | 20.0 | | +| 28 | | | | | + +NOTE 1: Applicable for multi-mode GSM/UMTS/LTE. +NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS. + +#### B.2.2.5 E-UTRA TDD + +### B.2.3 Recommended performance for LEE + +#### B.2.3.1 GSM + +Table B.2.3.1-1: Notebook TRP recommended performance for GSM 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.2.3.1-2: Tablet TRP recommended performance for GSM 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 tablet devices. + +#### B.2.3.2 UTRA FDD + +**Table B.2.3.2-1: Notebook TRP recommended performance for UTRA FDD 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 | +| I | - | - | 21,5 | TBD | TBD | +| II | - | - | TBD | TBD | TBD | +| III | - | - | TBD | TBD | TBD | +| IV | - | - | TBD | TBD | TBD | +| V | - | - | TBD | TBD | TBD | +| VI | - | - | 21,0 | TBD | TBD | +| VII | - | - | TBD | TBD | TBD | +| VIII | - | - | 21,0 | TBD | TBD | +| IX | - | - | TBD | TBD | TBD | +| XIX | - | - | 21,0 | TBD | TBD | + +NOTE 1: Applicable for multi-mode GSM/UMTS/LTE. +NOTE 2: Applicable for notebook devices. + +NOTE: TRP minimum performance requirements in table B.2.3.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not. + +**Table B.2.3.2-2: Tablet TRP recommended performance for UTRA FDD 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 | +| I | - | - | 21,5 | TBD | TBD | +| II | - | - | TBD | TBD | TBD | +| III | - | - | TBD | TBD | TBD | +| IV | - | - | TBD | TBD | TBD | +| V | - | - | 19,5 | TBD | TBD | +| VI | - | - | TBD | TBD | TBD | +| VII | - | - | TBD | TBD | TBD | +| VIII | - | - | TBD | TBD | TBD | +| IX | - | - | TBD | TBD | TBD | +| XIX | - | - | 19,5 | TBD | TBD | + +NOTE 1: Applicable for dual-mode GSM/UMTS. +NOTE 2: Applicable for tablet devices with two antennas. + +#### B.2.3.3 UTRA LCR TDD + +**Table B.2.3.3-1: Notebook TRP recommended performance for UTRA LCR TDD 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. + +Table B.2.3.3-2: Tablet TRP recommended performance for UTRA LCR TDD 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 tablet devices. + +#### B.2.3.4 E-UTRA FDD + +#### B.2.3.5 E-UTRA TDD + +## B.3 Receiver total radiated sensitivity + +The OTA TRS performance for GSM, UTRA and E-UTRA should be lower or equal than the recommended values shown in this clause. + +### B.3.1 Recommended performance for handheld UE + +#### B.3.1.1 Beside the head phantom position + +Beside the head phantom test method is defined in TR 25.914 [6] subclauses 5.1.1 and 5.1.2. + +##### B.3.1.1.1 GSM + +Table B.3.1.1.1-1: Handheld UE TRS recommended performance for GSM in beside the head phantom position and the primary mechanical mode. + +| Operating band | Unit | 1or >
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. + +##### B.3.1.1.2 UTRA FDD + +Table B.3.1.1.2-1: Handheld UE TRS recommended performance for FDD in beside the head phantom position for the primary mechanical mode + +| Operating band | Unit | ior † > | +|----------------|--------------|------------------------------------| +| 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 ior†> level of -101 dBm/3.84 shall apply for Band II. + +NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average ior†> level of -103 dBm/3.84 MHz shall apply for Band IV. + +##### B.3.1.1.3 UTRA LCR TDD + +Table B.3.1.1.3-1: Handheld UE TRS recommended performance for UTRA LCR TDD in beside the head phantom position and the primary mechanical mode. + +| Operating band | Unit | ior † >
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. + +#### B.3.1.2 Beside the head and hand phantoms position + +##### B.3.1.2.1 UTRA FDD + +**Table B.3.1.2.1-1: TRS recommended performance for UTRA FDD in the beside the head and hand phantoms position for the primary mechanical mode** + +| Operating band | Unit | ior >
Average | +|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------| +| I | dBm/3,84 MHz | -104,00 | +| II | dBm/3,84 MHz | -102,00 | +| III | dBm/3,84 MHz | TBD | +| IV | dBm/3,84 MHz | TBD | +| V | dBm/3,84 MHz | -99,75 | +| VI | dBm/3,84 MHz | TBD | +| VII | dBm/3,84 MHz | TBD | +| VIII | dBm/3,84 MHz | -99,75 | +| IX | dBm/3,84 MHz | TBD | +| XIX | dBm/3,84 MHz | TBD | +| NOTE 1: For the UE which supports DB-DC-HSDPA configuration 2, average ior > level of -101 dBm/3,84 shall apply for Band II. | | | +| NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average ior > level of -103 dBm/3,84 MHz shall apply for Band IV. | | | +| NOTE 3: Applicable for devices narrower than 72mm as defined in TR 25.914 | | | +| NOTE 4: Not applicable for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) | | | + +##### B.3.1.2.2 UTRA LCR TDD + +**Table B.3.1.2.2-1: TRS recommended performance for UTRA LCR TDD in the beside the head and hand phantoms position and the primary mechanical mode** + +| Operating band | Unit | ior >
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: Applicable for dual-mode GSM/UTRA LCR TDD. | | | + +##### B.3.1.2.3 E-UTRA FDD + +##### B.3.1.2.4 E-UTRA TDD + +#### B.3.1.3 Hand phantom browsing mode position + +##### B.3.1.3.1 UTRA FDD + +Table B.3.1.3.1-1: TRS recommended performance for UTRA FDD in hand phantom browsing mode position + +| Operating band | Unit | lor >
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: For the UE which supports DB-DC-HSDPA configuration 2, average lor> level of -101 dBm/3,84 shall apply for Band II. + +NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average lor> level of -103 dBm/3,84 MHz shall apply for Band IV. + +##### B.3.1.3.2 UTRA LCR TDD + +Table B.3.1.3.2-1: TRS recommended performance for UTRA LCR TDD in hand phantom browsing mode position + +| Operating band | Unit | lor >
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: Applicable for dual-mode GSM/UTRA LCR TDD. + +##### B.3.1.3.3 E-UTRA FDD + +##### B.3.1.3.4 E-UTRA TDD + +### B.3.2 Recommended performance for LME + +#### B.3.2.1 GSM + +Table B.3.2.1-1: LME TRS recommended performance for GSM 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 USB plug-in devices. + +#### B.3.2.2 UTRA FDD + +Table B.3.2.2-1: LME TRS recommended performance for UTRA FDD in the data transfer position + +| Operating band | Unit | or >
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: Applicable for USB plug-in devices. + +#### B.3.2.3 UTRA LCR TDD + +Table B.3.2.3-1: LME TRS recommended performance for UTRA LCR TDD 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. + +#### B.3.2.4 E-UTRA FDD + +#### B.3.2.5 E-UTRA TDD + +### B.3.3 Recommended performance for LEE + +#### B.3.3.1 GSM + +Table B.3.3.1-1: Notebook TRS recommended performance for GSM 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.3.3.1-2: Tablet TRS recommended performance for GSM 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 tablet devices. + +#### B.3.3.2 UTRA FDD + +Table B.3.3.2-1: Notebook TRS recommended performance for UTRA FDD in the data transfer position + +| Operating band | Unit | or >
Average | +|----------------|--------------|----------------------------------| +| I | dBm/3,84 MHz | -106.5 | +| 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 | -104.5 | +| VII | dBm/3,84 MHz | TBD | +| VIII | dBm/3,84 MHz | -104.5 | +| IX | dBm/3,84 MHz | TBD | +| XIX | dBm/3,84 MHz | -104.5 | + +NOTE 1: Applicable for multi-mode GSM/UMTS/LTE. +NOTE 2: Applicable for notebook devices. + +NOTE: TRS minimum performance requirements in table B.3.3.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not. + +Table B.3.3.2-2: Tablet TRS recommended performance for UTRA FDD in the data transfer position + +| Operating band | Unit | or >
Average | +|----------------|--------------|----------------------------------| +| I | dBm/3,84 MHz | -108,75 | +| II | dBm/3,84 MHz | TBD | +| III | dBm/3,84 MHz | TBD | +| IV | dBm/3,84 MHz | TBD | +| V | dBm/3,84 MHz | -106,0 | +| 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 | -106,0 | + +NOTE: Applicable for tablet devices with two antennas. + +#### B.3.3.3 UTRA LCR TDD + +Table B.3.3.3-1: Notebook TRS recommended performance for UTRA LCR TDD 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 notebook devices. + +Table B.3.3.3-2: Tablet TRS recommended performance for UTRA LCR TDD 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 tablet devices. + +#### B.3.3.4 E-UTRA FDD + +Table B.3.3.4-1: Tablet TRS recommended performance for E-UTRA FDD in data transfer position + +| Operating band | Channel bandwidth | Sensitivity (dBm) | +|----------------|-------------------|-------------------| +| | | Average | +| 1 | 10 MHz | -96.0 | +| 2 | 10 MHz | | +| 3 | 10 MHz | -97.0 | +| 4 | 10 MHz | | +| 5 | 10 MHz | | +| 7 | 10 MHz | -95.75 | +| 8 | 10 MHz | | +| 12 | 10 MHz | | +| 13 | 10 MHz | | +| 19 | 10 MHz | -94.5 | +| 20 | 10 MHz | -94.5 | +| 21 | 15 MHz | -93.0 | +| 28 | 10 MHz | | +| 32 | 10 MHz | | + +NOTE 1: Applicable for multi-mode GSM/UMTS/LTE. +NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS. + +#### B.3.3.5 E-UTRA TDD \ No newline at end of file diff --git a/marked/Rel-18/37_series/37145-1/raw.md b/marked/Rel-18/37_series/37145-1/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ae2f4559c8971acc71c0f622da9212ed9851686b --- /dev/null +++ b/marked/Rel-18/37_series/37145-1/raw.md @@ -0,0 +1,11248 @@ + + +# 3GPP TS 37.145-1 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Active Antenna System (AAS) Base Station (BS) conformance testing; Part 1: Conducted conformance testing (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------|----| +| Foreword..... | 21 | +| 1 Scope..... | 23 | +| 2 References..... | 23 | +| 3 Definitions, symbols and abbreviations..... | 25 | +| 3.1 Definitions..... | 25 | +| 3.2 Symbols..... | 29 | +| 3.3 Abbreviations..... | 31 | +| 4 General test conditions and declarations..... | 32 | +| 4.1 Measurement uncertainties and test requirements..... | 32 | +| 4.1.1 General..... | 32 | +| 4.1.2 Acceptable uncertainty of Test System..... | 33 | +| 4.1.2.1 General..... | 33 | +| 4.1.2.2 Measurement of transmitter..... | 34 | +| 4.1.2.3 Measurement of receiver..... | 35 | +| 4.1.3 Interpretation of measurement results..... | 37 | +| 4.2 Conducted and radiated requirement reference points..... | 38 | +| 4.3 Base station classes for AAS BS..... | 38 | +| 4.4 Regional requirements..... | 39 | +| 4.5 Operating bands and band categories..... | 40 | +| 4.6 Channel arrangements..... | 40 | +| 4.7 Requirements for AAS BS capable of multi-band operation..... | 40 | +| 4.8 AAS BS configurations..... | 41 | +| 4.8.1 Transmit configurations..... | 41 | +| 4.8.2 Receive configurations..... | 41 | +| 4.8.3 Power supply options..... | 42 | +| 4.8.4 BS with integrated Iuant BS modem..... | 42 | +| 4.9 Capability sets..... | 42 | +| 4.10 Manufacturer declarations for AAS BS testing..... | 43 | +| 4.11 Test signal configurations for AAS BS..... | 49 | +| 4.11.1 General..... | 49 | +| 4.11.1a NR Test signal used to build Test Configurations..... | 49 | +| 4.11.2 Test signal configurations..... | 50 | +| 4.11.2.1 ATC1: UTRA multicarrier operation..... | 50 | +| 4.11.2.1.1 General..... | 50 | +| 4.11.2.1.2 ATC1a generation..... | 50 | +| 4.11.2.1.3 ATC1b generation..... | 50 | +| 4.11.2.1.4 ATC1 power allocation..... | 50 | +| 4.11.2.2 ANTC1: UTRA FDD multicarrier non-contiguous operation..... | 50 | +| 4.11.2.2.1 General..... | 50 | +| 4.11.2.2.2 ANTC1 generation..... | 50 | +| 4.11.2.2.3 ANTC1 power allocation..... | 51 | +| 4.11.2.3 ATC2: E-UTRA multicarrier operation..... | 51 | +| 4.11.2.3.1 General..... | 51 | +| 4.11.2.3.2 ATC2a generation..... | 51 | +| 4.11.2.3.3 ATC2b generation..... | 51 | +| 4.11.2.3.4 ATC2 power allocation..... | 52 | +| 4.11.2.4 ANTC2: E-UTRA multicarrier non-contiguous operation..... | 52 | +| 4.11.2.4.1 General..... | 52 | +| 4.11.2.4.2 ANTC2 generation..... | 52 | +| 4.11.2.4.3 ANTC2 power allocation..... | 53 | +| 4.11.2.5 ATC3: UTRA and E-UTRA multi-RAT operation..... | 53 | +| 4.11.2.5.1 General..... | 53 | +| 4.11.2.5.2 ATC3a generation..... | 53 | +| 4.11.2.5.3 ATC3b generation..... | 53 | +| 4.11.2.5.4 ATC3 power allocation..... | 54 | + +| | | | +|-------------|------------------------------------------------------------------------------------------------------------------------------------|----| +| 4.11.2.6 | ANTC3: UTRA and E-UTRA multi-RAT non-contiguous operation..... | 54 | +| 4.11.2.6.1 | General..... | 54 | +| 4.11.2.6.2 | ANTC3 generation..... | 54 | +| 4.11.2.6.3 | ANTC3 power allocation..... | 54 | +| 4.11.2.7 | ATC4: Single carrier for receiver tests..... | 54 | +| 4.11.2.7.1 | ATC4a generation..... | 54 | +| 4.11.2.7.2 | ATC4b generation..... | 55 | +| 4.11.2.7.3 | ATC4c generation..... | 55 | +| 4.11.2.7.4 | ATC4d generation..... | 55 | +| 4.11.2.8 | ATC5: MB-MSR operation..... | 55 | +| 4.11.2.8.1 | ATC5a: MB-MSR test configuration for full carrier allocation..... | 55 | +| 4.11.2.8.2 | ATC5b: MB-MSR test configuration with high PSD per carrier..... | 56 | +| 4.11.2.9 | ATC6: E-UTRA and NR multi-RAT operation..... | 57 | +| 4.11.2.9.1 | General..... | 57 | +| 4.11.2.9.2 | ATC6 generation..... | 57 | +| 4.11.2.9.3 | ATC6 power allocation..... | 58 | +| 4.11.2.10 | ANTC6: E-UTRA and NR multi RAT non-contiguous operation..... | 58 | +| 4.11.2.10.1 | General..... | 58 | +| 4.11.2.10.2 | ANTC6 generation..... | 58 | +| 4.11.2.10.3 | ANTC6 power allocation..... | 58 | +| 4.11.2.11 | ATC7: NR multicarrier operation..... | 59 | +| 4.11.2.11.1 | General..... | 59 | +| 4.11.2.11.2 | ATC7 generation..... | 59 | +| 4.11.2.11.3 | ATC7 power allocation..... | 59 | +| 4.11.2.12 | ANTC7: NR multicarrier non-contiguous operation..... | 59 | +| 4.11.2.12.1 | General..... | 59 | +| 4.11.2.12.2 | ANTC7 generation..... | 59 | +| 4.11.2.12.3 | ANTC7 power allocation..... | 60 | +| 4.11.2.13 | ATC8: UTRA, E-UTRA and NR multi-RAT operation..... | 60 | +| 4.11.2.13.1 | General..... | 60 | +| 4.11.2.13.2 | ATC8 generation..... | 60 | +| 4.11.2.13.3 | ATC8 power allocation..... | 60 | +| 4.11.2.14 | ANTC8: UTRA, E-UTRA and NR multi-RAT non-contiguous operation..... | 61 | +| 4.11.2.14.1 | ANTC8 generation..... | 61 | +| 4.11.2.14.2 | ANTC8 power allocation..... | 61 | +| 4.12 | RF channels and test models..... | 62 | +| 4.12.1 | RF channels..... | 62 | +| 4.12.2 | Test models..... | 63 | +| 4.13 | Format and interpretation of tests..... | 64 | +| 5 | Applicability of Requirements..... | 65 | +| 5.1 | General..... | 65 | +| 5.2 | Test configurations for TAB connectors for operating bands where MSR is supported..... | 66 | +| 5.3 | Test configurations for multi-carrier capable TAB connector(s) in operating bands where one RAT capability sets are supported..... | 71 | +| 5.3.1 | General..... | 71 | +| 5.3.2 | TAB connector supporting one RAT only MSR in the operating band..... | 72 | +| 5.3.3 | TAB connector supporting Single-RAT UTRA in the operating band..... | 76 | +| 5.3.4 | TAB connector supporting Single-RAT E-UTRA in the operating band..... | 77 | +| 5.4 | Test configurations for Multi-band TAB connectors ..... | 78 | +| 5.4.1 | Multi-band TAB connector supporting MSR operation..... | 78 | +| 5.4.2 | Multi-band TAB connector supporting Single-RAT only..... | 80 | +| 6 | Conducted transmitter characteristics..... | 81 | +| 6.1 | General..... | 81 | +| 6.2 | Base station output power..... | 82 | +| 6.2.1 | General..... | 82 | +| 6.2.2 | Maximum output power..... | 82 | +| 6.2.2.1 | Definition and applicability..... | 82 | +| 6.2.2.2 | Minimum Requirement..... | 82 | +| 6.2.2.3 | Test Purpose..... | 82 | +| 6.2.2.4 | Method of test..... | 82 | + +| | | | +|-----------|----------------------------------------------------|----| +| 6.2.2.4.1 | Initial conditions..... | 82 | +| 6.2.2.4.2 | Procedure..... | 83 | +| 6.2.2.5 | Test Requirements..... | 83 | +| 6.2.3 | UTRA FDD primary CPICH power..... | 83 | +| 6.2.3.1 | Definition and applicability..... | 83 | +| 6.2.3.2 | Minimum requirement..... | 83 | +| 6.2.3.3 | Test purpose..... | 84 | +| 6.2.3.4 | Method of test..... | 84 | +| 6.2.3.4.1 | Initial conditions..... | 84 | +| 6.2.3.4.2 | Procedure..... | 84 | +| 6.2.3.5 | Test requirements..... | 84 | +| 6.2.4 | UTRA TDD primary CCPCH power..... | 85 | +| 6.2.4.1 | Definition and applicability..... | 85 | +| 6.2.4.2 | Minimum requirement..... | 85 | +| 6.2.4.3 | Test purpose..... | 85 | +| 6.2.4.4 | Method of test..... | 85 | +| 6.2.4.4.1 | Initial conditions..... | 85 | +| 6.2.4.4.2 | Procedure..... | 86 | +| 6.2.4.5 | Test requirements..... | 86 | +| 6.2.5 | UTRA FDD additional CPICH power for MIMO mode..... | 87 | +| 6.2.5.1 | Definition and applicability..... | 87 | +| 6.2.5.2 | Minimum requirement..... | 87 | +| 6.2.5.3 | Test purpose..... | 88 | +| 6.2.5.4 | Method of test..... | 88 | +| 6.2.5.4.1 | Initial conditions..... | 88 | +| 6.2.5.4.2 | Procedure..... | 88 | +| 6.2.5.5 | Test requirements..... | 88 | +| 6.2.6 | E-UTRA DL RS power..... | 89 | +| 6.2.6.1 | Definition and applicability..... | 89 | +| 6.2.6.2 | Minimum requirement..... | 89 | +| 6.2.6.3 | Test purpose..... | 89 | +| 6.2.6.4 | Method of test..... | 89 | +| 6.2.6.4.1 | Initial conditions..... | 89 | +| 6.2.6.4.2 | Procedure..... | 90 | +| 6.2.6.5 | Test requirements..... | 90 | +| 6.3 | Output power dynamics..... | 90 | +| 6.3.1 | General..... | 90 | +| 6.3.2 | UTRA Inner loop power control in the downlink..... | 90 | +| 6.3.2.1 | Definition and applicability..... | 90 | +| 6.3.2.2 | Minimum requirement..... | 90 | +| 6.3.2.3 | Test purpose..... | 91 | +| 6.3.2.4 | Method of test..... | 91 | +| 6.3.2.4.1 | Initial conditions..... | 91 | +| 6.3.2.4.2 | Procedure..... | 92 | +| 6.3.2.5 | Test requirements..... | 93 | +| 6.3.2.5.1 | UTRA FDD..... | 93 | +| 6.3.2.5.2 | UTRA TDD..... | 93 | +| 6.3.3 | Power control dynamic range..... | 94 | +| 6.3.3.1 | Definition and applicability..... | 94 | +| 6.3.3.2 | Minimum requirement..... | 94 | +| 6.3.3.3 | Test purpose..... | 94 | +| 6.3.3.4 | Method of test..... | 94 | +| 6.3.3.4.1 | Initial conditions..... | 94 | +| 6.3.3.4.2 | Procedure..... | 95 | +| 6.3.3.5 | Test requirements..... | 96 | +| 6.3.3.5.1 | UTRA FDD..... | 96 | +| 6.3.3.5.2 | UTRA TDD..... | 96 | +| 6.3.4 | Total power dynamic range..... | 96 | +| 6.3.4.1 | Definition and applicability..... | 96 | +| 6.3.4.2 | Minimum requirement..... | 97 | +| 6.3.4.3 | Test purpose..... | 97 | + +| | | | +|-----------|-------------------------------------|-----| +| 6.3.4.4 | Method of test..... | 97 | +| 6.3.4.4.1 | Initial conditions..... | 97 | +| 6.3.4.4.2 | Procedure..... | 97 | +| 6.3.4.5 | Test requirements..... | 98 | +| 6.3.4.5.1 | UTRA FDD..... | 98 | +| 6.3.4.5.2 | E-UTRA..... | 99 | +| 6.3.4.5.3 | NR..... | 99 | +| 6.3.5 | IPDL time mask..... | 100 | +| 6.3.5.1 | Definition and applicability..... | 100 | +| 6.3.5.2 | Minimum requirement..... | 100 | +| 6.3.5.3 | Test purpose..... | 100 | +| 6.3.5.4 | Method of test..... | 100 | +| 6.3.5.4.1 | Initial conditions..... | 100 | +| 6.3.5.4.2 | Procedure..... | 100 | +| 6.3.5.5 | Test requirements..... | 101 | +| 6.3.6 | RE Power control dynamic range..... | 101 | +| 6.3.6.1 | Definition and applicability..... | 101 | +| 6.3.6.2 | Minimum requirement..... | 101 | +| 6.3.6.3 | Method of test..... | 101 | +| 6.4 | Transmit ON/OFF power..... | 101 | +| 6.4.1 | General..... | 101 | +| 6.4.2 | Transmitter OFF power..... | 102 | +| 6.4.2.1 | Definition and applicability..... | 102 | +| 6.4.2.2 | Minimum requirement..... | 102 | +| 6.4.2.3 | Test purpose..... | 102 | +| 6.4.2.4 | Method of test..... | 102 | +| 6.4.2.4.1 | Initial conditions..... | 102 | +| 6.4.2.4.2 | Procedure..... | 102 | +| 6.4.2.5 | Test requirements..... | 103 | +| 6.4.3 | Transmitter transient period..... | 103 | +| 6.4.3.1 | Definition and applicability..... | 103 | +| 6.4.3.2 | Minimum requirement..... | 104 | +| 6.4.3.3 | Test purpose..... | 104 | +| 6.4.3.4 | Method of test..... | 104 | +| 6.4.3.4.1 | Initial conditions..... | 104 | +| 6.4.3.4.2 | Procedure..... | 105 | +| 6.4.3.5 | Test requirements..... | 106 | +| 6.4.3.5.1 | MSR operation..... | 106 | +| 6.4.3.5.1 | UTRA TDD operation..... | 106 | +| 6.4.3.5.1 | E-UTRA operation..... | 106 | +| 6.5 | Transmitted signal quality..... | 106 | +| 6.5.1 | General..... | 106 | +| 6.5.2 | Frequency error..... | 106 | +| 6.5.2.1 | Definition and applicability..... | 106 | +| 6.5.2.2 | Minimum Requirement..... | 106 | +| 6.5.2.3 | Test purpose..... | 106 | +| 6.5.2.4 | Method of test..... | 107 | +| 6.5.2.5 | Test Requirements..... | 107 | +| 6.5.2.5.1 | UTRA FDD test requirement..... | 107 | +| 6.5.2.5.2 | UTRA TDD test requirement..... | 107 | +| 6.5.2.5.3 | E-UTRA and NR test requirement..... | 107 | +| 6.5.3 | Time alignment error..... | 107 | +| 6.5.3.1 | Definition and applicability..... | 107 | +| 6.5.3.2 | Minimum requirement..... | 108 | +| 6.5.3.3 | Test purpose..... | 108 | +| 6.5.3.4 | Method of test..... | 108 | +| 6.5.3.4.1 | Initial conditions..... | 108 | +| 6.5.3.4.2 | Procedure..... | 109 | +| 6.5.3.5 | Test requirement..... | 110 | +| 6.5.3.5.1 | UTRA FDD test requirement..... | 110 | +| 6.5.3.5.2 | UTRA TDD test requirement..... | 110 | + +| | | | +|-----------|-------------------------------------------|-----| +| 6.5.3.5.3 | E-UTRA test requirement..... | 110 | +| 6.5.3.5.4 | NR test requirement..... | 111 | +| 6.5.4 | Modulation quality..... | 111 | +| 6.5.4.1 | Definition and applicability..... | 111 | +| 6.5.4.2 | Minimum Requirement..... | 111 | +| 6.5.4.3 | Test purpose..... | 111 | +| 6.5.4.4 | UTRA FDD method of test..... | 111 | +| 6.5.4.4.1 | Initial conditions..... | 111 | +| 6.5.4.4.2 | Procedure..... | 111 | +| 6.5.4.5 | UTRA TDD method of test..... | 113 | +| 6.5.4.5.1 | Initial conditions..... | 113 | +| 6.5.4.5.2 | Procedure..... | 113 | +| 6.5.4.6 | E-UTRA and NR method of test..... | 115 | +| 6.5.4.6.1 | Initial conditions..... | 115 | +| 6.5.4.6.2 | Procedure..... | 115 | +| 6.5.4.7 | Test Requirements..... | 116 | +| 6.5.4.7.1 | UTRA FDD test requirement..... | 116 | +| 6.5.4.7.2 | UTRA TDD test requirement..... | 116 | +| 6.5.4.7.3 | E-UTRA and NR test requirement..... | 116 | +| 6.6 | Unwanted Emissions..... | 117 | +| 6.6.1 | General..... | 117 | +| 6.6.2 | Occupied bandwidth..... | 118 | +| 6.6.2.1 | Definition and applicability..... | 118 | +| 6.6.2.2 | Minimum requirement..... | 118 | +| 6.6.2.3 | Test purpose..... | 118 | +| 6.6.2.4 | Method of test..... | 118 | +| 6.6.2.4.1 | Initial conditions..... | 118 | +| 6.6.2.4.2 | Procedure..... | 119 | +| 6.6.2.5 | Test requirements..... | 121 | +| 6.6.2.5.1 | MSR..... | 121 | +| 6.6.2.5.2 | UTRA FDD..... | 121 | +| 6.6.2.5.3 | UTRA TDD..... | 121 | +| 6.6.2.5.4 | E-UTRA..... | 122 | +| 6.6.3 | Adjacent Channel Leakage power Ratio..... | 122 | +| 6.6.3.1 | Definition and applicability..... | 122 | +| 6.6.3.2 | Minimum requirement..... | 122 | +| 6.6.3.3 | Test purpose..... | 122 | +| 6.6.3.4 | Method of test..... | 123 | +| 6.6.3.4.1 | Initial conditions..... | 123 | +| 6.6.3.4.2 | Procedure..... | 124 | +| 6.6.3.5 | Test requirements..... | 126 | +| 6.6.3.5.1 | General Requirements..... | 126 | +| 6.6.3.5.2 | Absolute Limits..... | 126 | +| 6.6.3.5.3 | MSR..... | 127 | +| 6.6.3.5.4 | UTRA FDD..... | 132 | +| 6.6.3.5.5 | UTRA TDD, 1,28Mcps option..... | 133 | +| 6.6.3.5.6 | E-UTRA..... | 134 | +| 6.6.4 | Spectrum emission mask..... | 136 | +| 6.6.4.1 | Definition and applicability..... | 136 | +| 6.6.4.2 | Minimum requirement..... | 136 | +| 6.6.4.3 | Test purpose..... | 136 | +| 6.6.4.4 | Method of test..... | 137 | +| 6.6.4.4.1 | Initial conditions..... | 137 | +| 6.6.4.4.2 | Procedure..... | 138 | +| 6.6.4.5 | Test requirements..... | 139 | +| 6.6.4.5.1 | General..... | 139 | +| 6.6.4.5.2 | Basic Limits..... | 139 | +| 6.6.5 | Operating band unwanted emission..... | 151 | +| 6.6.5.1 | Definition and applicability..... | 151 | +| 6.6.5.2 | Minimum requirement..... | 152 | +| 6.6.5.3 | Test purpose..... | 152 | + +| | | | +|-----------|---------------------------------------------------|-----| +| 6.6.5.4 | Method of test..... | 152 | +| 6.6.5.4.1 | Initial conditions..... | 152 | +| 6.6.5.4.2 | Procedure..... | 152 | +| 6.6.5.5 | Test requirements..... | 153 | +| 6.6.5.5.1 | General..... | 153 | +| 6.6.5.5.2 | Basic Limits for MSR Band Categories 1 and 3..... | 153 | +| 6.6.5.5.3 | Basic Limits for MSR Band Category 2..... | 163 | +| 6.6.5.5.4 | Basic Limits for MSR Additional requirements..... | 170 | +| 6.6.5.5.5 | Basic Limits for E-UTRA..... | 173 | +| 6.6.6 | Spurious emission..... | 195 | +| 6.6.6.1 | Definition and applicability..... | 195 | +| 6.6.6.2 | Minimum requirement..... | 196 | +| 6.6.6.3 | Test purpose..... | 196 | +| 6.6.6.4 | Method of test..... | 196 | +| 6.6.6.4.1 | Initial conditions..... | 196 | +| 6.6.6.4.2 | Procedure..... | 196 | +| 6.6.6.5 | Test requirements..... | 197 | +| 6.6.6.5.1 | General..... | 197 | +| 6.6.6.5.2 | Basic limits..... | 197 | +| 6.7 | Transmitter intermodulation..... | 221 | +| 6.7.1 | Definition and applicability..... | 221 | +| 6.7.1.1 | General..... | 221 | +| 6.7.2 | Minimum requirement..... | 222 | +| 6.7.3 | Test purpose..... | 222 | +| 6.7.4 | Method of test..... | 222 | +| 6.7.4.1 | Initial conditions..... | 222 | +| 6.7.4.2 | Procedure..... | 222 | +| 6.7.5 | Test requirements..... | 225 | +| 6.7.5.1 | MSR test requirements..... | 225 | +| 6.7.5.1.1 | General test requirement..... | 225 | +| 6.7.5.1.2 | Additional test requirement (BC1 and BC2)..... | 225 | +| 6.7.5.1.3 | Additional test requirement (BC3)..... | 226 | +| 6.7.5.1.4 | Intra-system test requirement..... | 226 | +| 6.7.5.2 | Single RAT UTRA operation..... | 226 | +| 6.7.5.2.1 | General test requirement for UTRA FDD..... | 226 | +| 6.7.5.2.2 | General test requirement for UTRA TDD..... | 227 | +| 6.7.5.2.3 | Intra-system test requirement..... | 227 | +| 6.7.5.4 | Single RAT E-UTRA operation..... | 227 | +| 6.7.5.4.1 | General test requirement..... | 227 | +| 6.7.5.4.2 | Void..... | 227 | +| 6.7.5.4.3 | Intra-system test requirement..... | 227 | +| 7 | Conducted receiver characteristics..... | 228 | +| 7.1 | General..... | 228 | +| 7.2 | Reference sensitivity level..... | 228 | +| 7.2.1 | Definition and applicability..... | 228 | +| 7.2.2 | Minimum Requirement..... | 228 | +| 7.2.3 | Test Purpose..... | 229 | +| 7.2.4 | Method of test..... | 229 | +| 7.2.4.1 | Initial conditions..... | 229 | +| 7.2.4.2 | Procedure..... | 229 | +| 7.2.5 | Test Requirements..... | 230 | +| 7.2.5.1 | UTRA FDD operation..... | 230 | +| 7.2.5.2 | UTRA TDD 1,28 Mcps option operation..... | 230 | +| 7.2.5.3 | E-UTRA operation..... | 231 | +| 7.2.5.4 | NR operation..... | 232 | +| 7.3 | Dynamic range..... | 233 | +| 7.3.1 | Definition and applicability..... | 233 | +| 7.3.2 | Minimum requirement..... | 233 | +| 7.3.3 | Test purpose..... | 234 | +| 7.3.4 | Method of test..... | 234 | +| 7.3.4.1 | Initial conditions..... | 234 | + +| | | | +|-----------|------------------------------------------------------------|-----| +| 7.3.4.2 | Procedure..... | 234 | +| 7.3.5 | Test requirements..... | 235 | +| 7.3.5.1 | UTRA FDD operation..... | 235 | +| 7.3.5.2 | UTRA TDD 1,28 Mcps option operation..... | 235 | +| 7.3.5.3 | E-UTRA operation..... | 235 | +| 7.3.5.4 | NR operation..... | 237 | +| 7.4 | Adjacent channel selectivity and narrowband blocking..... | 241 | +| 7.4.1 | Definition and applicability..... | 241 | +| 7.4.2 | Minimum requirement..... | 241 | +| 7.4.4 | Method of test..... | 241 | +| 7.4.4.1 | Initial conditions..... | 241 | +| 7.4.4.2 | Procedure..... | 242 | +| 7.4.4.2.1 | General procedure..... | 242 | +| 7.4.4.2.2 | MSR operation..... | 242 | +| 7.4.4.2.3 | Single RAT UTRA FDD operation..... | 243 | +| 7.4.4.2.4 | Single RAT UTRA TDD 1,28 Mcps option operation..... | 243 | +| 7.4.4.2.5 | Single RAT E-UTRA operation..... | 243 | +| 7.4.5 | Test requirements..... | 244 | +| 7.4.5.1 | MSR operation..... | 244 | +| 7.4.5.1.1 | General blocking test requirement..... | 244 | +| 7.4.5.1.2 | General narrowband blocking test requirement..... | 245 | +| 7.4.5.1.3 | Additional BC3 blocking test requirement..... | 246 | +| 7.4.5.2 | Single RAT UTRA FDD operation..... | 247 | +| 7.4.5.3 | Single RAT UTRA TDD 1,28 Mcps option operation..... | 247 | +| 7.4.5.4 | Single RAT E-UTRA operation..... | 248 | +| 7.5 | Blocking..... | 250 | +| 7.5.1 | Definition and applicability..... | 250 | +| 7.5.2 | Minimum requirement..... | 250 | +| 7.5.3 | Test purpose..... | 251 | +| 7.5.4 | Method of test..... | 251 | +| 7.5.4.1 | Initial conditions..... | 251 | +| 7.5.4.2 | Procedure..... | 251 | +| 7.5.4.2.1 | General Procedure..... | 251 | +| 7.5.4.2.2 | MSR operation..... | 251 | +| 7.5.4.2.3 | Single RAT UTRA FDD operation..... | 252 | +| 7.5.4.2.4 | Single RAT UTRA TDD 1,28 Mcps option operation..... | 252 | +| 7.5.4.2.5 | Single RAT E-UTRA operation..... | 253 | +| 7.5.5 | Test requirements..... | 253 | +| 7.5.5.1 | MSR operation..... | 253 | +| 7.5.5.1.1 | General out-of-band blocking test requirements..... | 253 | +| 7.5.5.1.2 | Co-location test requirements..... | 254 | +| 7.5.5.2 | Single RAT UTRA FDD operation..... | 259 | +| 7.5.5.3 | Single RAT UTRA TDD 1,28 Mcps option operation..... | 277 | +| 7.5.5.3.1 | General requirements..... | 277 | +| 7.5.5.3.2 | Co-location with GSM, DCS, UTRA FDD and/or E-UTRA TDD..... | 281 | +| 7.5.5.4 | Single RAT E-UTRA operation..... | 285 | +| 7.5.5.4.1 | General test requirement..... | 285 | +| 7.5.5.4.2 | Co-location with other base stations..... | 289 | +| 7.6 | Receiver spurious emissions..... | 294 | +| 7.6.1 | Definition and applicability..... | 294 | +| 7.6.2 | Minimum Requirement..... | 294 | +| 7.6.3 | Test Purpose..... | 295 | +| 7.6.4 | Method of test..... | 295 | +| 7.6.4.1 | Initial conditions..... | 295 | +| 7.6.4.2 | Procedure..... | 295 | +| 7.6.4.2.1 | General procedure..... | 295 | +| 7.6.4.2.2 | MSR operation..... | 295 | +| 7.6.4.2.3 | Single RAT UTRA FDD operation..... | 295 | +| 7.6.4.2.4 | Single RAT UTRA TDD 1,28 Mcps option operation..... | 296 | +| 7.6.4.2.5 | Single RAT E-UTRA operation..... | 297 | + +| | | | +|-----------|----------------------------------------------------------|-----| +| 7.6.5 | Test Requirements..... | 297 | +| 7.6.5.1 | General..... | 297 | +| 7.6.5.2 | Basic limits..... | 298 | +| 7.6.5.2.1 | MSR operation..... | 298 | +| 7.6.5.2.2 | Single RAT UTRA FDD operation..... | 298 | +| 7.6.5.2.3 | Single RAT UTRA TDD 1,28Mcps option operation..... | 299 | +| 7.6.5.2.4 | Single RAT E-UTRA operation..... | 299 | +| 7.7 | Receiver intermodulation..... | 300 | +| 7.7.1 | Definition and applicability..... | 300 | +| 7.7.2 | Minimum requirement..... | 300 | +| 7.7.3 | Test purpose..... | 300 | +| 7.7.4 | Method of test..... | 300 | +| 7.7.4.1 | Initial conditions..... | 300 | +| 7.7.4.2 | Procedure..... | 301 | +| 7.7.4.2.1 | General procedure..... | 301 | +| 7.7.4.2.2 | MSR operation..... | 301 | +| 7.7.4.2.3 | Single RAT UTRA FDD operation..... | 301 | +| 7.7.4.2.4 | Single RAT UTRA TDD 1,28Mcps option operation..... | 302 | +| 7.7.4.2.5 | Single RAT E-UTRA operation..... | 302 | +| 7.7.5 | Test requirements..... | 302 | +| 7.7.5.1 | MSR operation..... | 302 | +| 7.7.5.1.1 | General intermodulation test requirement..... | 302 | +| 7.7.5.1.2 | General narrowband intermodulation test requirement..... | 304 | +| 7.7.5.2 | Single RAT UTRA FDD operation..... | 308 | +| 7.7.5.3 | Single RAT UTRA TDD 1,28Mcps option operation..... | 309 | +| 7.7.5.4 | Single RAT E-UTRA operation..... | 310 | +| 7.8 | In-channel selectivity..... | 313 | +| 7.8.1 | Definition and applicability..... | 313 | +| 7.8.2 | Minimum requirement..... | 313 | +| 7.8.3 | Test purpose..... | 313 | +| 7.8.4 | Method of test..... | 314 | +| 7.8.4.1 | Initial conditions..... | 314 | +| 7.8.4.2 | Procedure..... | 314 | +| 7.8.5 | Test requirements..... | 314 | +| 8 | Performance requirements..... | 318 | +| 8.1 | General..... | 318 | +| 8.2 | Performance requirements for MSR..... | 319 | +| 8.3 | Performance requirements for UTRA FDD..... | 319 | +| 8.3.1 | Definition and applicability..... | 319 | +| 8.3.2 | Minimum Requirement..... | 320 | +| 8.3.3 | Test purpose..... | 320 | +| 8.3.4 | Method of test..... | 320 | +| 8.3.4.1 | Initial Conditions..... | 320 | +| 8.3.4.2 | Procedure..... | 320 | +| 8.3.5 | Test Requirement..... | 320 | +| 8.4 | Performance requirements for UTRA TDD..... | 321 | +| 8.4.1 | Definition and applicability..... | 321 | +| 8.4.2 | Minimum Requirement..... | 321 | +| 8.4.3 | Test purpose..... | 321 | +| 8.4.4 | Method of test..... | 322 | +| 8.4.4.1 | Initial Conditions..... | 322 | +| 8.4.4.2 | Procedure..... | 322 | +| 8.4.5 | Test Requirement..... | 322 | +| 8.5 | Performance requirements for E-UTRA..... | 322 | +| 8.5.1 | Definition and applicability..... | 322 | +| 8.5.2 | Minimum Requirement..... | 323 | +| 8.5.3 | Test purpose..... | 323 | +| 8.5.4 | Method of test..... | 323 | +| 8.5.4.1 | Initial Conditions..... | 323 | +| 8.5.4.2 | Procedure..... | 323 | +| 8.5.5 | Test Requirement..... | 323 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------|------------| +| 8.6 | Performance requirements for NR..... | 323 | +| 8.6.1 | Definition and applicability..... | 323 | +| 8.6.2 | Minimum Requirement..... | 324 | +| 8.6.3 | Test purpose..... | 324 | +| 8.6.4 | Method of test..... | 324 | +| 8.6.4.1 | Initial conditions..... | 324 | +| 8.6.4.2 | Procedure..... | 324 | +| 8.6.5 | Test Requirement..... | 324 | +| Annex A (normative): | Characteristics of interfering signals..... | 326 | +| Annex B (normative): | Environmental requirements for the BS equipment..... | 327 | +| B.1 | General..... | 327 | +| B.2 | Normal test environment..... | 327 | +| B.3 | Extreme test environment..... | 327 | +| B.3.1 | General..... | 327 | +| B.3.2 | Extreme temperature..... | 327 | +| B.4 | Vibration..... | 328 | +| B.5 | Power supply..... | 328 | +| B.6 | Measurement of test environments..... | 328 | +| Annex C (informative): | Test tolerances and derivation of test requirements..... | 329 | +| Annex D (informative): | Measurement system set-up..... | 330 | +| D.1 | Transmitter..... | 330 | +| D.1.1 | AAS BS output power, transmitter ON/OFF power, modulation quality, frequency error and operating band unwanted emissions..... | 330 | +| D.1.2 | Transmitter intermodulation..... | 331 | +| D.1.3 | Transmitter spurious emissions..... | 331 | +| D.2 | Receiver..... | 333 | +| D.2.1 | Reference sensitivity level..... | 333 | +| D.2.2 | Receiver Dynamic Range..... | 333 | +| D.2.3 | Receiver Adjacent channel selectivity and narrowband blocking..... | 334 | +| D.2.4 | Receiver spurious emissions..... | 334 | +| D.2.5 | Receiver In-channel selectivity..... | 335 | +| D.2.6 | Receiver Intermodulation..... | 336 | +| Annex E (informative): | Change history..... | 337 | + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document specifies the conducted test methods and conformance requirements for *single RAT E-UTRA operation*, *single RAT UTRA operation* (FDD and TDD) and Multi-Standard Radio (MSR) UTRA, E-UTRA and NR Active Antenna System (AAS) Base Station (BS). These have been derived from, and are consistent with the non-AAS BS specifications in TS 25.104 [2], TS 25.105 [3], TS 36.104 [4], TS 38.104 [36] or TS 37.104 [5]. The technical specification TS 37.145 is in 2 parts, part TS 37.145-1 (the present document) covers conducted requirements and part TS 37.145-2 [40] covers radiated requirements. + +The present document does not establish conducted test methods and conformance requirements for Band 46 operation as it is not supported by AAS BS, but Band 46 test requirements are still applicable for AAS BS for protection of and against Band 46 operation. + +The present document does not establish conducted test methods and conformance requirements for Narrow-Band Internet of Things (NB-IoT) in band, NB-IoT guard band, or standalone NB-IoT operation, for AAS BS in *single RAT E-UTRA operation* as defined in TS 36.141 [14], or for AAS BS in *MSR operation* using E-UTRA as defined in TS 37.141 [13]. + +# 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.104: "Base Station (BS) radio transmission and reception (FDD)" +- [3] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD)" +- [4] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception" +- [5] 3GPP TS 37.104: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception" +- [6] 3GPP TS 37.105: "Active Antenna System (AAS) Base Station (BS) transmission and reception" +- [7] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000" +- [8] 3GPP TS 37.105 (V14.1.0): "Active Antenna System (AAS) Base Station (BS) radio transmission and reception (Release 14)" +- [9] 3GPP TS 25.104 (V14.2.0): "Base Station (BS) radio transmission and reception (FDD) (Release 14)" +- [10] 3GPP TS 25.105 (V14.0.0): "Base Station (BS) radio transmission and reception (TDD) (Release 14)" +- [11] 3GPP TS 36.104 (V14.4.0): "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception (Release 14)" + +- [12] 3GPP TS 37.104 (V14.4.0): "E-UTRA, UTRA and GSM/EDGE Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception (Release 14)" +- [13] 3GPP TS 37.141:"NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing" +- [14] 3GPP TS 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing" +- [15] 3GPP TS 25.141: "Base Station (BS) conformance testing (FDD)" +- [16] 3GPP TS 37.141 (V14.4.0): "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing (Release 14)" +- [17] 3GPP TS 36.141 (V14.4.0): "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing (Release 14)" +- [18] 3GPP TS 25.141 (V14.2.0): "Base Station (BS) conformance testing (FDD) (Release 14)" +- [19] 3GPP TS 25.142: "Base Station (BS) conformance testing (TDD)" +- [20] 3GPP TS 25.142 (V14.0.0): "Base Station (BS) conformance testing (TDD) (Release 14)" +- [21] 3GPP TR 25.942: "Radio Frequency (RF) system scenarios" +- [22] 3GPP TS 45.004: "Digital cellular telecommunications system (Phase 2+); Modulation" +- [23] 3GPP TS 25.214: "Physical layer procedures (FDD)" +- [24] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission +- [25] CEPT ECC Decision (13)03: "The harmonised use of the frequency band 1452-1492 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL)" +- [26] IEC 60721: "Classification of environmental conditions" +- [27] IEC 60721-3-3: "Classification of environmental conditions - Part 3-3: Classification of groups of environmental parameters and their severities - Stationary use at weather protected locations" +- [28] IEC 60721-3-4: "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations" +- [29] ETSI EN 300 019-1-3: "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-3: Classification of environmental conditions; Stationary use at weatherprotected locations" +- [30] ETSI EN 300 019-1-4: "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-4: Classification of environmental conditions; Stationary use at non-weatherprotected locations" +- [31] IEC 60068-2-1 (2007): "Environmental testing - Part 2: Tests. Tests A: Cold" +- [32] IEC 60068-2-2 (2007): "Environmental testing - Part 2: Tests. Tests B: Dry heat" +- [33] IEC 60068-2-6 (2007): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)" +- [34] Recommendation ITU-T O.153: "Basic parameters for the measurement of error performance at bit rates below the primary rate" +- [35] Recommendation ITU-R SM.329: "Unwanted emissions in the spurious domain" +- [36] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception" +- [37] 3GPP TS 38.141-1: "NR;Base Station (BS) conformance testing; Part 1: Conducted conformance testing" + +- [38] FCC publication number 662911: "Emissions Testing of Transmitters with Multiple Outputs in the Same Band" +- [39] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation" +- [40] 3GPP TS 37.145-2: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: radiated conformance testing" +- [41] 3GPP TS 38.104 (V15.6.0): "NR; Base Station (BS) radio transmission and reception (Release 15)" +- [42] ECC/DEC/(17)06: "The harmonised use of the frequency bands 1427-1452 MHz and 1492-1518 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL)" + +--- + +## 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]. + +**active antenna system base station:** base station system which combines an Antenna Array with an Active transceiver unit array and a *Radio Distribution Network* + +**active receiver unit:** number of active receivers is the same as the [number of receiver diversity branches] to which compliance is declared for clause 8 performance requirements + +**active transmitter unit:** transmitter unit which is ON, and has the ability to send modulated data streams that are parallel and distinct to those sent from other transmitter units to one or more *TAB connectors* at the *transceiver array boundary* + +**band category:** group of operating bands for which the same MSR scenarios apply + +**Base Station RF Bandwidth:** bandwidth in which a base station transmits and/or receives single or multiple carrier(s) and/or RATs simultaneously within a supported operating band + +NOTE: In single carrier operation, the *Base Station RF Bandwidth* is equal to the channel bandwidth. + +**Base Station RF Bandwidth edge:** frequency of one of the edges of the *Base Station RF Bandwidth* + +**basic limit:** emissions limit taken from the non AAS specifications that is converted into a per *TAB connector TX cell group* AAS emissions limit by scaling + +**beam:** main lobe of a radiation pattern from an AAS BS + +NOTE: For certain AAS antenna array, there may be more than one beam. + +**beam centre direction:** direction equal to the geometric centre of the -3 dB EIRP contour of the beam + +**beam direction pair:** data set consisting of the *beam centre direction* and the related *beam peak direction* + +**beam peak direction:** direction where the maximum EIRP is supposed to be found + +**beamwidth:** angles describing the major and minor axes of an ellipsoid closest fit to an essentially elliptic half-power contour of a beam + +**carrier:** modulated waveform conveying the physical channels + +**carrier aggregation:** aggregation of two or more NR or E-UTRA component carriers in order to support wider *transmission bandwidths* + +**channel bandwidth:** RF bandwidth supporting a single RF carrier with the *transmission bandwidth* configured in the uplink or downlink of a cell + +NOTE 1: The *channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE 2: For UTRA FDD, the *channel bandwidth* is the nominal channel spacing specified in TS 25.104 [2]. For UTRA TDD 1,28 Mcps option, the *channel bandwidth* is the nominal channel spacing specified in TS 25.105 [3]. + +NOTE 3: For E-UTRA, the *channel bandwidths* are specified in TS 36.104 [4]. Standalone NB-IoT channel bandwidths specified in TS 36.104 [4] are not applicable to AAS BS. + +NOTE 4: In TS 38.104 [33] for NR, *channel bandwidths* are referred to as BS channel bandwidths, since for NR BS and UE channel bandwidths may differ. + +**channel edge:** lowest or highest frequency of an NR carrier, separated by the *BS channel bandwidth* + +**code domain power:** part of the mean power which correlates with a particular (OVSF) code channel in a UTRA signal + +NOTE: The sum of all powers in the code domain equals the mean power in a bandwidth of $(1 + \alpha)$ times the chip rate of the radio access mode. + +**contiguous spectrum:** spectrum consisting of a contiguous block of spectrum with no *sub-block gap(s)* + +**downlink operating band:** part of the (FDD) operating band designated for downlink + +**EIRP accuracy directions set:** *beam peak directions* for which the EIRP accuracy requirement is intended to be met. + +NOTE: The *beam peak directions* are related to a corresponding contiguous range or discrete list of *beam centre directions* by the *beam direction pairs* included in the set. + +**equivalent isotropic radiated power:** equivalent power radiated from an isotropic directivity device producing the same field intensity at a point of observation as the field intensity radiated in the direction of the same point of observation by the discussed device + +NOTE: Isotropic directivity is equal in all directions (0 dBi). + +**equivalent isotropic sensitivity:** sensitivity for an isotropic directivity device equivalent to the sensitivity of the discussed device exposed to an incoming wave from a defined AoA + +NOTE 1: The sensitivity is the minimum received power level at which a RAT specific requirement is met. + +NOTE 2: Isotropic directivity is equal in all directions (0 dBi). + +**highest carrier:** The carrier with the highest carrier frequency transmitted/received in a specified operating band + +**hybrid AAS BS:** AAS BS which has both a conducted RF interface and a radiated RF interface in the far field and conforms to a *hybrid requirements set* + +NOTE: For NR operation, a *hybrid AAS BS* corresponds to NR *type 1-H* in [37]. + +**hybrid requirements set:** complete set of requirements applied to a *hybrid AAS BS* with both conducted and radiated requirements. + +**inter-band gap:** frequency gap between two supported consecutive operating bands + +**inter-band carrier aggregation:** carrier aggregation of component carriers in different operating bands + +NOTE: Carriers aggregated in each band can be contiguous or non-contiguous. + +**intra-band contiguous carrier aggregation:** *contiguous carriers* aggregated in the same operating band + +**intra-band non-contiguous carrier aggregation:** non-contiguous carriers aggregated in the same operating band + +**Inter RF Bandwidth gap:** frequency gap between two consecutive *Base Station RF Bandwidths* that are placed within two supported operating bands + +**lowest carrier:** the carrier with the lowest carrier frequency transmitted/received in a specified operating band + +**maximum carrier output power per TAB connector:** *mean power level measured on a particular carrier at the array boundary antenna connectors, during the transmitter ON period in a specified reference condition* + +**maximum throughput:** maximum achievable throughput for a reference measurement channel + +**MSR operation:** operation of AAS BS declared to be MSR in particular *operating band(s)* + +**multi-band requirements:** requirements applying per one single operating band with exclusion bands or other multi-band provisions as defined for each requirement + +**multi-band TAB connector:** *TAB connector* supporting operation in multiple *operating bands* through common active electronic component(s) + +NOTE: For common TX and RX *TAB connectors*, the definition applies where common active electronic components are in the transmit path and/or in the receive path. + +**NB-IoT in-band operation:** NB-IoT is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier + +**NB-IoT guard band operation:** NB-IoT is operating in guard band when it utilizes the unused resource block(s) within a E-UTRA carrier's guard-band + +**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment + +**non-AAS BS:** BS conforming to one of the RF requirement specifications TS 25.104 [2], TS 25.105 [3], TS 36.104 [4] or TS37.104 [5] + +NOTE: For AAS BS in *single RAT E-UTRA operation* or in *MSR operation* using E-UTRA, the NB-IoT operation (including in-band, guard band and standalone operation) is excluded from the consideration in the performance comparison among AAS BS and *non-AAS BS* in this specification. + +**non-contiguous spectrum:** *spectrum consisting of two or more sub-blocks separated by sub-block gap(s)* + +**operating band:** frequency range in which the AAS BS operates (paired or unpaired), that is defined with a specific set of technical requirements + +**OTA sensitivity directions declaration:** set of manufacturer declarations comprising one or more EIS values (with related RAT and *channel bandwidth*), and the directions where it (they) applies + +NOTE: All the directions apply to all the EIS values in an OSDD. + +**Radio Bandwidth:** frequency difference between the upper edge of the highest used carrier and the lower edge of the lowest used carrier + +**radio distribution network:** passive network which distributes radio signals generated by the transceiver unit array to the antenna array, and/or distributes the radio signals collected by the antenna array to the transceiver unit array + +NOTE: In the case when the active transceiver units are physically integrated with the array elements of the antenna array, the radio distribution network is a one-to-one mapping + +**rated carrier output power per TAB connector:** mean power level associated with a particular carrier the manufacturer has declared to be available at the *TAB connector*, during the *transmitter ON period* in a specified reference condition + +**rated total output power per TAB connector:** mean power level associated with a particular operating band the manufacturer has declared to be available at the *TAB connector*, during the *transmitter ON period* in a specified reference condition + +**receiver target:** angles of arrival in which reception is performed + +**receiver target redirection range:** union of all the *sensitivity RoAoA* achievable through redirecting the *receiver target* related to the OSDD + +**receiver target reference direction:** direction inside the *receiver target redirection range* declared by the manufacturer for conformance testing. For an OSDD without *receiver target redirection range*, this is a direction inside the *sensitivity RoAoA* + +**reference beam direction:** declared *beam direction pair*, including reference *beam centre direction* and reference *beam peak direction* where the reference *beam peak direction* is the direction for the intended maximum EIRP within the EIRP accuracy compliance directions set + +**sensitivity RoAoA:** RoAoA within which the declared EIS(s) of an OSDD is intended to be achieved at any instance of time for a specific AAS BS direction setting + +**single band requirements:** requirements applying per one single operating band without exclusion bands or other multi-band provisions + +**single band TAB connector:** *TAB connector* supporting operation either in a single operating band only, or in multiple operating bands but without any common active electronic component(s) + +**single RAT E-UTRA operation:** operation of AAS BS declared to be single RAT E-UTRA in the operating band + +NOTE: *Single RAT E-UTRA operation* does not cover in-band NB-IoT, nor guardband NB-IoT operation. + +**single RAT UTRA operation:** operation of AAS BS declared to be single RAT UTRA in the operating band + +**sTTI:** A transmission time interval (TTI) of either one slot or one subslot as defined in TS 36.211 [39] on either uplink or downlink. + +**sub-block:** one contiguous allocated block of spectrum for use by the same Base Station + +NOTE: There may be multiple instances of *sub-blocks* within an *Base Station RF Bandwidth*. + +**sub-block gap:** frequency gap between two consecutive *sub-blocks* within an *Base Station RF Bandwidth*, where the RF requirements in the gap are based on co-existence for un-coordinated operation + +**Synchronized operation:** Operation of TDD in two different systems, where no simultaneous uplink and downlink occur. + +**TAB connector:** transceiver array boundary connector + +**TAB connectors beam forming group:** Group of *TAB connectors* associated with an EIRP beam declaration, comprising of the complete set of *TAB connectors* from which a declared beam is transmitted + +**TAB connector RX min cell group:** operating band specific declared group of *TAB connectors* to which requirements are applied + +NOTE: The group corresponds to the group of *TAB connectors* which are responsible for receiving a cell when the AAS BS setting corresponding to the declared minimum number of cells with transmission on all *TAB connectors* supporting an operating band, but its existence is not limited to that condition. + +**TAB connector TX min cell group:** operating band specific declared group of *TAB connectors* to which requirements are applied. + +NOTE: The group corresponds to the group of *TAB connectors* which are responsible for transmitting a cell when the AAS BS setting corresponding to the declared minimum number of cells with transmission on all *TAB connectors* supporting an operating band, but its existence is not limited to that condition. + +**throughput:** number of payload bits successfully received per second for a reference measurement channel in a specified reference condition + +**total RF bandwidth:** maximum sum of Base Station RF Bandwidths in all supported *operating bands* + +**transceiver array boundary:** conducted interface between the transceiver unit array and the composite antenna + +**transmission bandwidth:** bandwidth of an instantaneous E-UTRA transmission from a UE or BS, measured in resource block units + +**transmitter OFF period:** time period during which the transmitter is scheduled not to transmit + +NOTE: For AAS BS, this definition applies per *TAB connector* and operating band. + +**transmitter ON period:** time period during which the transmitter is transmitting data and/or reference symbols + +NOTE: For AAS BS, this definition applies per *TAB connector* and operating band. + +**transmitter transient period:** time period during which the transmitter is changing from the OFF period to the ON period or vice versa + +NOTE: For AAS BS, this definition applies per *TAB connector* and operating band. + +**Unsynchronized operation:** Operation of TDD in two different systems, where the conditions for synchronized operation are not met. + +**uplink operating band:** part of the (FDD) operating band designated for uplink + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\alpha$ | Roll-off factor | +| $\beta$ | Percentage of the mean transmitted power emitted outside the occupied bandwidth on the assigned channel | +| $BW_{\text{Channel}}$ | Channel bandwidth (for E-UTRA) | +| $BW_{\text{Channel\_CA}}$ | Aggregated channel bandwidth, expressed in MHz. $BW_{\text{Channel\_CA}} = F_{\text{edge\_high}} - F_{\text{edge\_low}}$ | +| $BW_{\text{Config}}$ | Transmission bandwidth configuration (for E-UTRA), expressed in MHz, where $BW_{\text{Config}} = N_{\text{RB}} \times 180 \text{ kHz}$ in the uplink and $BW_{\text{Config}} = 15 \text{ kHz} + N_{\text{RB}} \times 180 \text{ kHz}$ in the downlink | +| $BW_{\text{tot}}$ | Total RF bandwidth | +| $DwPTS$ | Downlink part of the special subframe (for E-UTRA TDD operation) | +| $f$ | Frequency | +| $\Delta f$ | Separation between the Base Station RF bandwidth edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency | +| $\Delta f_{\text{max}}$ | The largest value of $\Delta f$ used for defining the requirement | +| $\Delta f_{\text{OBUE}}$ | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| $\Delta f_{\text{OOB}}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $F_{\text{C}}$ | Carrier centre frequency | +| $F_{\text{filter}}$ | Filter centre frequency | +| $f_{\text{offset}}$ | Separation between the Base Station RF bandwidth edge frequency and the centre of the measuring filter | +| $f_{\text{offset}}_{\text{max}}$ | The maximum value of $f_{\text{offset}}$ used for defining the requirement | +| $F_{\text{BW RF,high}}$ | Upper RF bandwidth edge, where $F_{\text{BW RF,high}} = F_{\text{C,high}} + F_{\text{offset, RAT}}$ | +| $F_{\text{BW RF,low}}$ | Lower RF bandwidth edge, where $F_{\text{BW RF,low}} = F_{\text{C,low}} - F_{\text{offset, RAT}}$ | +| $F_{\text{C,high}}$ | Centre frequency of the highest transmitted/received carrier | +| $F_{\text{C,low}}$ | Centre frequency of the lowest transmitted/received carrier | +| $F_{\text{edge\_low}}$ | The lower edge of aggregated channel bandwidth, expressed in MHz. $F_{\text{edge\_low}} = F_{\text{C,low}} - F_{\text{offset, RAT}}$ | +| $F_{\text{edge\_high}}$ | The upper edge of aggregated channel bandwidth, expressed in MHz. $F_{\text{edge\_high}} = F_{\text{C,high}} + F_{\text{offset, RAT}}$ | +| $F_{\text{offset, RAT}}$ | Frequency offset from the centre frequency of the highest transmitted/received carrier to the upper RF bandwidth edge, sub-block edge or inter-RF bandwidth edge, or from the centre frequency of the lowest transmitted/received carrier to the lower RF bandwidth edge, sub-block edge or inter-RF bandwidth edge for a specific RAT | +| $F_{\text{UL\_low}}$ | The lowest frequency of the uplink operating band | +| $F_{\text{UL\_high}}$ | The highest frequency of the uplink operating band | +| $F_{\text{uw}}$ | Frequency offset of unwanted signal | +| $N_{\text{cells}}$ | A declared number corresponding to the minimum number of cells that can be transmitted by an AAS BS in a particular band with transmission on all TAB connectors supporting the operating band | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in units of resource blocks (for E-UTRA) | +| $N_{\text{RXU,active}}$ | The number of active receiver units. The same as the [number of receiver diversity branches] to which compliance is declared for chapter 8 performance requirements. | +| $N_{\text{RXU,counted}}$ | The number of active receiver units that are taken into account for unwanted emission scaling. | + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| $N_{RXU,countedpercell}$ | The number of active receiver units that are taken into account for unwanted emissions scaling per cell | +| $N_{TXU,active}$ | The number of active transmitter units | +| $N_{TXU,counted}$ | The number of active transmitter units , as calculated in clause 6.1, that are taken into account for conducted TX power limit | +| $N_{TXU,countedpercell}$ | The number of active transmitter units that are taken into account for emissions scaling per cell | +| $P_{EM,B32,ind}$ | Declared emission level in Band 32, ind=a, b, c, d, e (see table 4.10, D6.8) | +| $P_{EM,B54,ind}$ | Declared emission level in Band 54, ind=a,b,c,d,e,f | +| $P_{max,c,cell}$ | The maximum carrier output power per TAB connector TX min cell group | +| $P_{max,c,TABC}$ | The maximum carrier output power per TAB connector | +| $P_{Rated,c,TABC}$ | The rated carrier output power per TAB connector | +| $P_{Rated,c,sys}$ | The sum of $P_{Rated,c,TABC}$ for all TAB connectors for a single carrier | +| $P_{Rated,t,group}$ | The sum of $P_{Rated,t,TABC}$ for all TAB connectors belonging to a specified group | +| $P_{Rated,t,TABC}$ | The rated total output power per TAB connector | +| $P_{REFSENS}$ | Reference Sensitivity power level | +| $W_{gap}$ | Sub-block gap size or Inter RF Bandwidth gap size | + +![Figure 3.2-1: Illustration of RF bandwidth related symbols and definitions for Multi-standard Radio. The diagram shows a frequency axis with a horizontal line. Above the axis, there are three colored blocks: an orange block labeled 'RAT_low', a light blue block labeled 'Multiple carriers / RATs', and a green block labeled 'RAT_high'. Vertical dashed lines mark the center frequencies 'F_C,low' and 'F_C,high'. Horizontal double-headed arrows indicate offsets 'F_offset, RAT, low' and 'F_offset, RAT, high' from the center lines to the edges of the blocks. Below the axis, a grey bar spans the width of the blocks, with vertical lines marking 'F_BW RF,low' and 'F_BW RF,high'. A bracket below the grey bar is labeled 'BW_RF'. The axis is labeled 'Frequency' at the right end.](a3472689858b068ef469213682965325_img.jpg) + +Figure 3.2-1: Illustration of RF bandwidth related symbols and definitions for Multi-standard Radio. The diagram shows a frequency axis with a horizontal line. Above the axis, there are three colored blocks: an orange block labeled 'RAT\_low', a light blue block labeled 'Multiple carriers / RATs', and a green block labeled 'RAT\_high'. Vertical dashed lines mark the center frequencies 'F\_C,low' and 'F\_C,high'. Horizontal double-headed arrows indicate offsets 'F\_offset, RAT, low' and 'F\_offset, RAT, high' from the center lines to the edges of the blocks. Below the axis, a grey bar spans the width of the blocks, with vertical lines marking 'F\_BW RF,low' and 'F\_BW RF,high'. A bracket below the grey bar is labeled 'BW\_RF'. The axis is labeled 'Frequency' at the right end. + +Figure 3.2-1: Illustration of RF bandwidth related symbols and definitions for Multi-standard Radio + +![Figure 3.2-2: Illustration of RF bandwidth related symbols and definitions for non-contiguous Multi-standard Radio. The diagram shows two sub-blocks, Sub block 1 and Sub block n, separated by a gap. Each sub-block contains multiple carriers/RATs. The frequency range of Sub block 1 is from F_C block 1, low (F_C, low) to F_C block 1, high. The frequency range of Sub block n is from F_C block n, low to F_C block n, high (F_C, high). The offset from the center frequency to the edge of the sub-block is F_offset, RAT. The total RF bandwidth is labeled BW_RF, with the bottom edge at F_BW RF, low and the top edge at F_BW RF, high. The gap between sub-blocks is labeled Sub block edge.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 3.2-2: Illustration of RF bandwidth related symbols and definitions for non-contiguous Multi-standard Radio. The diagram shows two sub-blocks, Sub block 1 and Sub block n, separated by a gap. Each sub-block contains multiple carriers/RATs. The frequency range of Sub block 1 is from F\_C block 1, low (F\_C, low) to F\_C block 1, high. The frequency range of Sub block n is from F\_C block n, low to F\_C block n, high (F\_C, high). The offset from the center frequency to the edge of the sub-block is F\_offset, RAT. The total RF bandwidth is labeled BW\_RF, with the bottom edge at F\_BW RF, low and the top edge at F\_BW RF, high. The gap between sub-blocks is labeled Sub block edge. + +**Figure 3.2-2: Illustration of RF bandwidth related symbols and definitions for non-contiguous Multi-standard Radio** + +![Figure 3.2-3: Illustration of maximum Radio Bandwidth and Total RF bandwidth for Multi-band Multi-standard Radio. The diagram shows two bands, Band X and Band Y, separated by an inter RF bandwidth gap. Band X has a frequency range from F_C band X, low to F_C band X, high. Band Y has a frequency range from F_C band Y, low to F_C band Y, high. The offset from the center frequency to the edge of the band is F_offset, RAT. The RF bandwidth of Band X is labeled BW_RF of Band X, and the RF bandwidth of Band Y is labeled BW_RF of Band Y. The gap between the bands is labeled BW_RF edge. The total RF bandwidth is labeled Total RF bandwidth = BW_RF of Band X + BW_RF of Band Y. The maximum radio bandwidth is indicated by a bracket spanning the entire range from the bottom of Band X to the top of Band Y.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +Figure 3.2-3: Illustration of maximum Radio Bandwidth and Total RF bandwidth for Multi-band Multi-standard Radio. The diagram shows two bands, Band X and Band Y, separated by an inter RF bandwidth gap. Band X has a frequency range from F\_C band X, low to F\_C band X, high. Band Y has a frequency range from F\_C band Y, low to F\_C band Y, high. The offset from the center frequency to the edge of the band is F\_offset, RAT. The RF bandwidth of Band X is labeled BW\_RF of Band X, and the RF bandwidth of Band Y is labeled BW\_RF of Band Y. The gap between the bands is labeled BW\_RF edge. The total RF bandwidth is labeled Total RF bandwidth = BW\_RF of Band X + BW\_RF of Band Y. The maximum radio bandwidth is indicated by a bracket spanning the entire range from the bottom of Band X to the top of Band Y. + +**Figure 3.2-3: Illustration of maximum *Radio Bandwidth* and Total RF bandwidth for Multi-band Multi-standard Radio** + +### 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|------------------------------------------| +| AAS BS | Active Antenna System Base Station | +| ACLR | Adjacent Channel Leakage power Ratio | +| ACS | Adjacent Channel Selectivity | +| AoA | Angle of Arrival | +| ARFCN | Absolute Radio Frequency Channel Number | +| B | Bottom RF channel (for testing purposes) | + +| | | +|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| BC | Band Category | +| BER | Bit Error Rate | +| BLER | Block Error Rate | +| CA | Carrier Aggregation | +| CACLR | Cumulative ACLR | +| CP | Cyclic prefix | +| CRC | Cyclic Redundancy Check | +| CW | Continuous Wave (unmodulated signal) | +| DC-HSDPA | Dual Cell HSDPA | +| D-CPICH | Demodulation Common Pilot Channel | +| DIP | Dominant Interferer Proportion | +| EARFCN | E-UTRA Absolute Radio Frequency Channel Number | +| EIRP | Equivalent Isotropic Radiated Power | +| EIS | Equivalent Isotropic Sensitivity | +| EVM | Error Vector Magnitude | +| FCC | Federal Communications Commission | +| FDD | Frequency Division Duplex | +| FRC | Fixed Reference Channel | +| GSCN | Global Synchronization Channel Number | +| GSM | Global System for Mobile communication | +| HS-DSCH | High Speed Downlink Shared Channel | +| ICS | In-Channel Selectivity | +| Iuant | E-Node B internal logical interface between the implementation specific O&M function and the RET antennas and TMAs control unit function of the E-Node B | +| ITU | International Telecommunication Union | +| ITU-R | Radio communication Sector of the ITU | +| LA | Local Area | +| M | Middle RF channel (for testing purposes) | +| MB-MSR | Multi-Band Multi-Standard Radio | +| MBT | Multi-Band Testing | +| MIMO | Multiple Inputs Multiple Outputs | +| MR | Medium Range | +| MSR | Multi-Standard Radio | +| NB-IoT | Narrowband – Internet of Things | +| NR | New Radio | +| OBUE | Operating Band Unwanted Emissions | +| OBW | Occupied Band Width | +| OFDM | Orthogonal Frequency Division Multiplex | +| OSDD | OTA Sensitivity Directions Declaration | +| OTA | Over The Air | +| PCCPCH | Primary Common Control Physical CHannel | +| QAM | Quadrature Amplitude Modulation | +| QPSK | Quadrature Phase-Shift Keying | +| RAT | Radio Access Technology | +| RB | Resource Block (for E-UTRA) | +| RDN | Radio Distribution Network | +| RE | Resource Element | +| REFSENS | Reference Sensitivity | +| RF | Radio Frequency | +| RMS | Root Mean Square (value) | +| RoAoA | Range of Angles of Arrival | +| RRc | Root Raised Cosine | +| RS | Reference Symbol | +| RX | Receiver | +| SBT | Single Band Testing | +| SC | Single Carrier | +| SCS | Sub-Carrier Spacing | +| SNR | Signal-to-Noise Ratio | +| sPDSCH | shortened Physical Downlink Shared Channel | +| T | Top RF channel (for testing purposes) | +| TAB | Transceiver Array Boundary | + +| | | +|--------|----------------------------------------------| +| TAE | Time Alignment Error | +| TDD | Time Division Duplex | +| TT | Test Tolerance | +| TX | Transmitter | +| UARFCN | UTRA Absolute Radio Frequency Channel Number | +| UE | User Equipment | +| WA | Wide Area | + +--- + +## 4 General test conditions and declarations + +### 4.1 Measurement uncertainties and test requirements + +#### 4.1.1 General + +The requirements of this clause apply to all applicable tests in part 1 of this specification, i.e. to all conducted test + +The minimum requirements are given in TS 37.105 [6] and the references therein. Test requirements are given in this specification or are included by reference to TS 25.141 [15], TS 25.142 [19], TS 36.141 [14], TS 38.141-1 [37] or TS 37.141 [13]. Test Tolerances for the conducted test requirements explicitly stated in the present document are given in annex C of the present document. Test Tolerances for test requirements included by reference to TS 25.141 [15], TS 25.142 [19], TS 36.141 [14], TS 38.141-1 [37] or TS 37.141 [13] are defined in the respective referred test specification. + +Test requirements and Test Tolerances for NB-IoT in-band, NB-IoT guard band, or standalone NB-IoT operation are not supported by AAS BS and not covered by this specification. When referring to standalone E-UTRA test requirements for *single RAT operation* in TS 36.141 [14] or to E-UTRA test requirements for *MSR operation* in TS 37.141 [13], any test requirements specified in those specifications for E-UTRA with NB-IoT (in-band or guard band) or for standalone NB-IoT, shall not be considered for the AAS BS. Unless otherwise stated, the exclusion of the NB-IoT test requirements in this specification applies to all operation modes (i.e. *in-band NB-IoT operation*, *guard band NB-IoT operation* and *standalone NB-IoT operation*). + +Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the minimum requirements to create test requirements. + +When a test requirement differs from the corresponding minimum requirement, then the Test Tolerance applied for the test is non-zero. The Test Tolerance for the test and the explanation of how the minimum requirement has been relaxed by the Test Tolerance are given in annex C. + +#### 4.1.2 Acceptable uncertainty of Test System + +##### 4.1.2.1 General + +The maximum acceptable uncertainty of the Test System is specified below for each test defined explicitly in the present specification, where appropriate. The maximum acceptable uncertainty of the Test System for test requirements included by reference is defined in the respective referred test specification. + +When a requirement is applied per *TAB connector* then the test uncertainty is applied to the measured value. When a requirement is applied for a group of *TAB connectors* then the test uncertainty is applied to sum of the measured power on each *TAB connector* in the group. + +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 tests, it should be noted that the uncertainties in clause 4.1.2 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. + +#### 4.1.2.2 Measurement of transmitter + +**Table 4.1.2.2-1: Maximum Test System uncertainty for transmitter tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| 6.2 Base Station output power | ±0.7 dB for UTRA and E-UTRA and NR, $f \leq 3.0$ GHz
±1.0 dB, $3.0$ GHz $< f \leq 4.2$ GHz for UTRA and E-UTRA and NR | | +| 6.4 Transmit ON/OFF power | ±2.0 dB , $f \leq 3.0$ GHz
±2.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.6.6 Transmitter spurious emissions, Mandatory Requirements | 9 kHz $< f \leq 4$ GHz: ±2.0 dB
4 GHz $< f \leq 19$ GHz: ±4.0 dB | | +| 6.6.6 Transmitter spurious emissions, Additional BC2 Requirement | 9 kHz $< f \leq 4$ GHz: ±2.0 dB
4 GHz $< f \leq 12.75$ GHz: ±4.0 dB | | +| 6.6.6 Transmitter spurious emissions, Protection of BS receiver | ±3.0 dB | | +| 6.6.6 Transmitter spurious emissions, Additional spurious emission requirements | ±2.0 dB for $> -60$ dBm , $f \leq 3.0$ GHz
±2.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz
±3.0 dB for $\leq -60$ dBm , $f \leq 3.0$ GHz
±3.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.6.6 Transmitter spurious emissions, Co-location | ±3.0 dB | | +| 6.6.5 Operating band unwanted emissions | ±1.5 dB , $f \leq 3.0$ GHz
±1.8 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.6.2 Occupied bandwidth | For E-UTRA:
1.4 MHz, 3 MHz Channel BW: ±30 kHz
5 MHz, 10 MHz Channel BW: ±100 kHz
15 MHz, 20 MHz: Channel BW: ±300 kHz

For UTRA:
±100 kHz

For NR:
5 MHz, 10 MHz BS Channel BW: ±100 kHz
15 MHz, 20 MHz, 25 MHz, 30 MHz, 40 MHz, 50 MHz
BS Channel BW: ±300 kHz
60 MHz, 70 MHz, 80 MHz, 90 MHz, 100 MHz BS
Channel BW: ±600 kHz | | +| 6.6.3 Adjacent Channel Leakage power Ratio (ACLR) | Relative ACLR:
BW $\leq 20$ MHz: ±0.8 dB
BW $> 20$ MHz: ±1.2 dB

ACLR Absolute power ±2.0 dB, $f \leq 3.0$ GHz
ACLR Absolute power ±2.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz

Relative CACLR
BW $\leq 20$ MHz: ±0.8 dB
BW $> 20$ MHz: ±1.2 dB

CACLR absolute power ±2.0 dB , $f \leq 3.0$ GHz
CACLR absolute power ±2.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.7 Transmitter intermodulation (interferer requirements)
This tolerance applies to the stimulus and not the measurements defined in 6.6.6, 6.6.5 and 6.6.3 | The value below applies only to the interfering signal and is unrelated to the measurement uncertainty of the tests (6.6.1, 6.6.2 and 6.6.4) which have to be carried out in the presence of the interferer.

±1.0 dB | The uncertainty of interferer has double the effect on the result due to the frequency offset | + +#### 4.1.2.3 Measurement of receiver + +**Table 4.1.2.3-1: Maximum Test System Uncertainty for receiver tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.4 Adjacent channel selectivity, general blocking and narrowband blocking | $\pm 1.4$ dB , $f \leq 3.0$ GHz
$\pm 1.8$ dB, $3.0$ GHz $< f \leq 4.2$ GHz |

Overall system uncertainty comprises three quantities:

  1. Wanted signal level error
  2. Interferer signal level error
  3. Additional impact of interferer leakage

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared to provide the ratio error of the two signals. The interferer leakage effect is systematic, and is added arithmetically.

Test System uncertainty = \sqrt{(\text{wanted\_level\_error}^2 + \text{interferer\_level\_error}^2)} + \text{leakage effect}.

f \leq 3.0 GHz
Wanted signal level \pm 0.7 dB
Interferer signal level \pm 0.7 dB
3.0 GHz < f \leq 4.2 GHz
Wanted signal level \pm 1.0 dB
Interferer signal level \pm 1.0 dB

f \leq 4.2 GHz
Impact of interferer leakage 0.4 dB

| +| 7.5 Blocking | $1$ MHz $\leq f_{\text{interferer}} \leq 3$ GHz: $\pm 1.3$ dB
$3$ GHz $< f_{\text{interferer}} \leq 12.75$ GHz: $\pm 3.2$ dB |

Overall system uncertainty comprises three quantities:

  1. Wanted signal level error
  2. Interferer signal level error
  3. Interferer broadband noise

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared to provide the ratio error of the two signals. The Interferer Broadband noise effect is systematic, and is added arithmetically.

Test System uncertainty = \sqrt{(\text{wanted\_level\_error}^2 + \text{interferer\_level\_error}^2)} + \text{Broadband noise effect}.

Out of band blocking, using CW interferer:
Wanted signal level:
\pm 0.7 dB up to 3 GHz
\pm 1.0 dB up to 4.2 GHz
Interferer signal level:
\pm 1.0 dB up to 3 GHz
\pm 3.0 dB up to 12.75 GHz
Impact of interferer Broadband noise 0.1 dB

| +| 7.6 Receiver spurious emissions | $30$ MHz $\leq f \leq 4$ GHz: $\pm 2.0$ dB
$4$ GHz $< f \leq 19$ GHz: $\pm 4.0$ dB | | + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.7 Receiver intermodulation (General requirements) | $\pm 1.8$ dB , $f \leq 3.0$ GHz
$\pm 2.4$ dB, $3.0$ GHz $< f \leq 4.2$ GHz |

Overall system uncertainty comprises four quantities:

  1. Wanted signal level error
  2. CW Interferer level error
  3. Modulated Interferer level error
  4. Impact of interferer ACLR

The effect of the closer CW signal has twice the effect.

Items 1, 2 and 3 are assumed to be uncorrelated so can be root sum squared to provide the combined effect of the three signals. The interferer ACLR effect is systematic, and is added arithmetically.

Test System uncertainty = \text{SQRT} [(2 \times \text{CW\_level\_error})^2 + (\text{mod interferer\_level\_error})^2 + (\text{wanted signal\_level\_error})^2] + \text{ACLR effect.}

f \leq 3.0 GHz
Wanted signal level \pm 0.7 dB
CW interferer level \pm 0.5 dB
Mod interferer level \pm 0.7 dB

3.0 GHz < f \leq 4.2 GHz
Wanted signal level \pm 1.0 dB
CW Interferer level \pm 0.7 dB
Mod Interferer level \pm 1.0 dB

f \leq 4.2 GHz
Impact of interferer ACLR 0.4 dB

| +| 7.7 Receiver intermodulation (Narrowband requirements) | $\pm 1.8$ dB , $f \leq 3.0$ GHz
$\pm 2.4$ dB, $3.0$ GHz $< f \leq 4.2$ GHz | Same as Receiver intermodulation (General requirements). | +| NOTE: Unless otherwise noted, only the Test System stimulus error is considered here. The effect of errors in the throughput measurements or the BER/FER due to finite test duration is not considered. | | | + +### 4.1.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 Shared Risk principle. + +The Shared Risk principle is defined in Recommendation ITU-R M.1545 [7]. + +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 clause 4.1.2 of the present document. + +If the Test System for a test is known to have a measurement uncertainty greater than that specified in clause 4.1.2, 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 clause 4.1.2 shall be used to tighten the test requirement, making the test harder to pass. For some tests e.g. receiver tests, this may require modification of stimulus signals. This procedure will ensure that a Test System not compliant with clause 4.1.2 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 clause 4.1.2 had been used. + +## 4.2 Conducted and radiated requirement reference points + +AAS BS requirements are defined for two points of reference, signified by radiated requirements and conducted requirements. + +![Diagram illustrating the radiated and conducted points of reference for an AAS BS. It shows a 'transceiver unit array' on the left and a 'composite antenna' on the right, separated by a 'transceiver array boundary'. The composite antenna contains an 'RDN' and an 'Antenna array'. The 'far field region' is indicated to the right. Conducted reference points are marked as #1, #2, ..., #K at the boundary, with an arrow pointing to one labeled 'Transceiver array boundary connector TAB(n)'. A large arrow on the right indicates the 'transmitted radiation direction (reception opposite)'.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +Diagram illustrating the radiated and conducted points of reference for an AAS BS. It shows a 'transceiver unit array' on the left and a 'composite antenna' on the right, separated by a 'transceiver array boundary'. The composite antenna contains an 'RDN' and an 'Antenna array'. The 'far field region' is indicated to the right. Conducted reference points are marked as #1, #2, ..., #K at the boundary, with an arrow pointing to one labeled 'Transceiver array boundary connector TAB(n)'. A large arrow on the right indicates the 'transmitted radiation direction (reception opposite)'. + +**Figure 4.2-1: Radiated and conducted points of reference of AAS BS** + +Radiated characteristics are defined over the air (OTA) with a point of reference in the far field (Fraunhofer) region. Radiated requirements are also referred to as OTA requirements. + +Conducted characteristics are defined at individual or groups of *TAB connectors* at the *transceiver array boundary*, which is the conducted interface between the transceiver unit array and the composite antenna. + +The transceiver unit array is part of the composite transceiver functionality generating modulated transmit signal structures and performing receiver combining and demodulation. + +The transceiver unit array contains an implementation specific number of transmitter units and an implementation specific number of receiver units. Transmitter units and receiver units may be combined into transceiver units. The transmitter/receiver units have the ability to receive/send parallel independent modulated symbol streams. + +The composite antenna contains a *radio distribution network* (RDN) and an antenna array. The RDN is a linear passive network that distributes the RF power between the *transceiver array boundary* and the antenna array, in an implementation specific way. + +How a conducted requirement is applied to the *transceiver array boundary* is detailed in the respective requirement clause. + +Part 1 of this specification details the test requirements of the conducted requirements only and hence only requires the conducted reference points. + +## 4.3 Base station classes for AAS BS + +The requirements in this specification apply to AAS BS of Wide Area BS, Medium Range BS and Local Area BS classes unless otherwise stated. + +Wide Area BS are characterised by requirements derived from Macro Cell scenarios. For a hybrid *AAS BS* of Wide Area BS class, the minimum coupling loss between any *TAB connector* and the UE is 70 dB. + +NOTE: Whenever WA BS is referred in this specification, the NB-IoT Wide Area BS and related requirements as defined in TS 36.104 [4], are not applicable for AAS BS. + +Medium Range BS are characterised by requirements derived from Micro Cell scenarios. For a hybrid *AAS BS* of Medium Range BS class, the minimum coupling loss between any *TAB connector* and the UE is 53 dB. + +Local Area BS are characterised by requirements derived from Pico Cell scenarios. For a hybrid *AAS BS* of Local Area BS class, the minimum coupling loss between any *TAB connector* and the UE is 45 dB. + +## 4.4 Regional requirements + +Some requirements in the present document may only apply in certain regions either as optional requirements, or set by local and regional regulation as mandatory requirements. It is normally not stated in the 3GPP specifications under what exact circumstances that the requirements apply, since this is defined by local or regional regulation. + +Table 4.4-1 lists all requirements in the present specification that may be applied differently in different regions. Non-AAS requirements are applicable as defined in the present document. In many cases, such requirements include regional requirements that are implicitly referenced from the present specification, and listed in the specification for the specifications concerned [2] [5]. + +**Table 4.4-1: List of regional requirements** + +| Clause number | Requirement | Comments | +|---------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.5 | Operating bands and Band Categories | Some bands may be applied regionally. | +| 6.6.2 | Occupied bandwidth | The requirement may be applied regionally. There may also be regional requirements to declare the Occupied bandwidth according to the definition. | +| 6.6.4 | Spectrum emission mask | The mask specified may be mandatory in certain regions. In other regions this mask may not be applied. Additional spectrum protection requirements may apply regionally. | +| 6.6.5 | Operating band unwanted emissions | The BS may have to comply with the applicable emission limits established by FCC Title 47 [15], when deployed in regions where those limits are applied and under the conditions declared by the manufacturer. | +| 6.6.5 | Operating band unwanted emissions | The requirements for protection of DTT may apply regionally. | +| 6.6.5 | Operating band unwanted emissions | Regional requirement as defined in TS 37.104, clause 6.6.2.4.4 [12] may be applied for the protection of systems operating in frequency bands adjacent to Band 1 as defined in TS 37.104, clause 4.5, [12] in geographic areas in which both an adjacent band service and UTRA and/or E-UTRA are deployed. | +| 6.6.5 | Operating band unwanted emissions | Additional requirements defined for Band 24 in 3GPP TS 37.104, subclause 6.6.2.4.5 may apply in regions where FCC regulation applies. | +| 6.6.5 | Operating band unwanted emissions | Additional Band 32 unwanted emissions requirements may apply in certain regions. | +| 6.6.6 | Spurious emissions | Category A limits are mandatory for regions where Category A limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [35] apply. Category B limits are mandatory for regions where Category B limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [35] apply. | +| 6.6.6 | Spurious emissions | Additional spurious emissions requirements may be applied for the protection of system operating in frequency ranges other than the AAS BS operating band as described in TS 37.104 [12] clause 6.6.1.3. | +| 6.6.6 | Spurious emissions | In addition to 3GPP requirements, the BS may have to comply with the applicable emission limits established by FCC Title 47 [15], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. | +| 6.6.6 | Spurious emissions | The emission limits specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | +| 6.6.6 | Spurious emissions | Additional requirements defined for Band 54 in 3GPP TS 37.104, subclause 6.6.1.3.1 may apply in regions where FCC regulation applies. | +| 6.7 | Transmitter intermodulation | Additional requirements may apply in certain regions. | +| 7.4.5 | Additional BC3 blocking requirement | This requirement may be applied for the protection of the BS receiver when an MSR BS is operating in the same geographical area as UTRA TDD. | +| 7.6 | Rx spurious emissions | The emission limits specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | + +## 4.5 Operating bands and band categories + +The operating bands and band categories for AAS BS are the same as for *non-AAS BS*, as described in TS 37.104 [5]. In addition, band category aspects described in TS 37.141, clauses 4.4.1, 4.4.2 and 4.4.3, shall apply. + +NOTE 1: *AAS BS* does not support GSM, but BC2 is still applicable for protection of/against GSM operation in BC2 operating bands. + +NOTE 2: AAS BS does not support Band 46 (and all its sub-bands defined in TS 36.104 [12], clause 5.5) operation, but Band 46 test requirements are still applicable for AAS BS for protection of and against Band 46 operation. + +NOTE 3: Bands in BC1 and BC2 categories are also used for NB-IoT operation. NB-IoT is not applicable for AAS BS. + +## 4.6 Channel arrangements + +The channel arrangements for AAS BS are the same as those for UTRA *non-AAS BS* and/or E-UTRA *non-AAS BS* and/or NR *non-AAS BS* as described in TS 37.104 [5]. + +NOTE: Test requirements for nominal carrier spacing of 19.8 MHz and 20.1 MHz for carriers in Band 46 as specified in 36.104 [12] clause 5.7.1, are not applicable for AAS BS. + +## 4.7 Requirements for AAS BS capable of multi-band operation + +For AAS BS capable of operation in multiple operating bands, the RF requirements in clause 6 and 7 apply separately to each supported operating band unless otherwise stated. + +An AAS BS may be capable of supporting operation in multiple operating bands with one of the following implementations of *TAB connectors* in the *transceiver array boundary*: + +- All TAB connectors are single band TAB connectors: + - Different sets of *single band TAB connectors* support different operating bands, but each *TAB connector* supports only operation in one single operating band. + - Sets of *single band TAB connectors* support operation in multiple operating bands with some *single band TAB connectors* supporting more than one operating band. +- All TAB connectors are multiband TAB connectors. +- A combination of single band sets and multi-band sets of TAB connectors provides support of the AAS BS capability of operation in multiple operating bands. + +Unless otherwise stated all requirements specified for an operating band apply only to the set of *TAB connectors* supporting that operating band. + +In certain requirements it is explicitly stated that specific additions or exclusions to the requirement apply at *multi-band TAB connectors* as detailed in the requirement clause. + +In the case of an operating band being supported only by *single band TAB connectors* in a *TAB connector TX min cell group* or a *TAB connector RX min cell group*, *single band requirements* apply to that set of *TAB connectors*. + +NOTE: Each supported operating band needs to be operated separately during conformance testing on *single band TAB connectors*. + +In the case of an operating band being supported only by *multi-band TAB connectors* supporting the same operating band combination in a *TAB connector TX min cell group* or a *TAB connector RX min cell group*, *multi-band requirements* apply to that set of *TAB connectors*. + +The case of an operating band being supported by both *multi-band TAB connectors* and *single band TAB connectors* in a *TAB connector TX min cell group* or a *TAB connector RX min cell group* is not covered by the present release of this specification. + +The case of an operating band being supported by *multi-band TAB connectors* which are not all supporting the same operating band combination in a *TAB connector TX min cell group* or a *TAB connector RX min cell group* is not covered by the present release of this specification. + +For *multi-band TAB connectors* supporting the bands for TDD, the RF requirements in the present specification assume no simultaneous uplink and downlink occur between the bands. + +The RF requirements for *multi-band TAB connectors* supporting bands for both FDD and TDD are not covered by the present release of this specification. + +## 4.8 AAS BS configurations + +### 4.8.1 Transmit configurations + +Unless otherwise stated, the conducted transmitter characteristics in clause 6 are specified at the AAS BS *transceiver array boundary* at the *TAB connector(s)* antenna connector with a full complement of transceiver units for the configuration in normal operating conditions. + +![Diagram of transmitter test ports for an AAS BS. A dashed box on the left represents the 'transceiver unit array'. A vertical dashed line to its right represents the 'transceiver array boundary'. At this boundary, there are multiple test ports labeled #1, #2, ..., #K. Port #1 is connected to a 'Measurement Equipment' box. Port #2 is connected to a 'Load' box. Port #K is also connected to a 'Load' box. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +The diagram illustrates the transmitter test ports for an AAS BS. On the left, a dashed box represents the 'transceiver unit array'. To its right, a vertical dashed line indicates the 'transceiver array boundary'. At this boundary, there are multiple test ports labeled #1, #2, ..., #K. Port #1 is connected to a 'Measurement Equipment' box. Port #2 is connected to a 'Load' box. Port #K is also connected to a 'Load' box. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Diagram of transmitter test ports for an AAS BS. A dashed box on the left represents the 'transceiver unit array'. A vertical dashed line to its right represents the 'transceiver array boundary'. At this boundary, there are multiple test ports labeled #1, #2, ..., #K. Port #1 is connected to a 'Measurement Equipment' box. Port #2 is connected to a 'Load' box. Port #K is also connected to a 'Load' box. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure 4.8.1-1: Transmitter test ports** + +Unless otherwise stated, for the tests in clause 6 of the present document, the requirement applies for each transmit *TAB connector*. + +### 4.8.2 Receive configurations + +Unless otherwise stated, the conducted receiver characteristics in clause 7 are specified at the *TAB connector* with a full complement of transceiver units for the configuration in normal operating conditions. + +![Diagram of receiver test ports showing a transceiver unit array connected to a measurement equipment and loads via TAB connectors.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +The diagram illustrates the receiver test ports for a transceiver unit array. A dashed rectangle on the left represents the 'transceiver unit array'. A vertical dashed line to its right marks the 'transceiver array boundary'. Along this boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Measurement Equipment' box. Connectors #2 and #K are each connected to a 'Load' box. Vertical ellipses between #2 and #K indicate additional connectors. An arrow points to one of the connectors on the boundary, labeled 'Transceiver array boundary connector TAB(n)'. + +Diagram of receiver test ports showing a transceiver unit array connected to a measurement equipment and loads via TAB connectors. + +**Figure 4.8.2-1: Receiver test ports** + +For the tests in clause 7 of the present document, the requirement applies at each receive *TAB connector*. + +Conducted receive requirements are tested at the *TAB connector*, with the remaining receiver unit(s) disabled or their *TAB connector(s)* being terminated. + +### 4.8.3 Power supply options + +If the AAS BS 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. + +### 4.8.4 BS with integrated Iuant BS modem + +Unless otherwise stated, for the tests in the present document, the integrated Iuant BS modem shall be switched off. Spurious emissions according to clauses 6.6.4 and 7.6 shall be measured only for frequencies above 20 MHz with the integrated Iuant BS modem switched on. + +## 4.9 Capability sets + +Capability set is defined as the *TAB connectors* capability to support certain RAT combinations in an operating band. + +The manufacturer shall declare (D6.12) the supported capability set(s) according to table 4.9-1 for each supported *TAB connector(s)* and supported operating band(s). + +Table 4.9-1 Capability sets + +| Capability set supported by the AAS BS | CSA1 | CSA2 | CSA3 | CSA3A | CSA3B | CSA4 | CSA5 | +|----------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|-------------------------------------------------------------| +| Supported RATs | TAB connector supports MSR operation of UTRA only in the band | TAB connector supports MSR operation of E-UTRA only in the band | TAB connector supports UTRA and E-UTRA MSR in the band | TAB connector supports NR and E-UTRA MSR in the band | TAB connector supports UTRA, E-UTRA, NR MSR in the band | TAB connector supports single-RAT UTRA in the band | TAB connector supports single-RAT E-UTRA in the band | +| Supported configurations | SR UTRA (SC, MC) | SR E-UTRA (SC, MC, CA) | MR UTRA + E-UTRA
SR UTRA (SC, MC)
SR E-UTRA (SC, MC, CA) | MR E-UTRA + NR
SR NR (SC, MC, CA)
SR E-UTRA (SC, MC, CA) | SR UTRA (SC, MC)
SR E-UTRA (SC, MC, CA)
SR NR (SC, MC, CA)
MR UTRA + E-UTRA
MR UTRA + NR
MR E-UTRA + NR
MR UTRA + E-UTRA + NR | SR UTRA (SC, MC) | SR E-UTRA (SC, MC, CA) | +| Applicable BC | BC1, BC2 or BC3 | BC1, BC2 or BC3 | BC1, BC2 or BC3 | BC1, BC2 or BC3 | BC1, BC2 | BC1, BC2 or BC3 | BC1, BC2 or BC3 | + +The applicable test configurations for each RF requirement are defined in clauses 5.1, 5.2 and 5.3 for the declared capability set(s). For a *multi-band TAB connector* the applicable test configurations for each RF requirement are defined in clause 5.4 for the declared capability set(s). + +NOTE: Not every supported configuration within a capability set is tested, but the tables in clauses 5.2, 5.3 and 5.4 provide a judicious choice among the supported configurations and test configurations to ensure proper test coverage. + +## 4.10 Manufacturer declarations for AAS BS testing + +The following declarations are required. + +**Table 4.10-1 Manufacturers declarations** + +| Declaration identifier | Declaration | Description | +|------------------------|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D6.1 | Operating bands and frequency ranges | List of operating band(s) supported by TAB connector(s) of the BS and if applicable, frequency range(s) within the operating band(s) that the BS can operate in.
Declarations shall be made per TAB connector . | +| D6.3 | Spurious emission category | Declare the AAS BS spurious emission category as either category A or B with respect to the limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [35]. | +| D6.4 | Geographic area support | The manufacturer shall declare the regions the AAS BS may operate in. e.g. CEPT. | +| D6.5 | Band 20 or Band XX support, operating in geographical areas allocated to broadcasting (DTT) | If the AAS BS has TAB connectors declared to support Band 20 the manufacturer shall declare if the AAS BS may operate in geographical areas allocated to broadcasting (DTT). | +| D6.6 | Band 20 or Band XX support, emission level for channel N ( $P_{EM,N}$ ) | If the AAS BS has TAB connectors declared to support Band 20 or Band XX and has been declared to operate in geographical areas allocated to broadcasting (DTT), the emission level for channel N (Annex G of TS 36.104 [11]) shall be declared. | +| D6.7 | Band 20 or Band XX support, Maximum output Power in 10 MHz ( $P_{10MHz}$ ) | If the AAS BS has TAB connectors declared to support Band 20 or Band XX and has been declared to operate in geographical areas allocated to broadcasting (DTT), the maximum output power in 10 MHz (Annex G of TS 36.104 [11]) shall be declared. | +| D6.8 | Band 32 or Band XXXII support, Declared emission level in Band 32/XXXII ( $P_{EM,B32,ind}$ ) | If the AAS BS has TAB connectors declared to support Band 32 or Band XXXII the manufacturer shall declare if the AAS BS may operate in geographical areas allocated to broadcasting (DTT), the emission level in Band 32/XXXII ( $P_{EM,B32,ind, ind=a, b, c, d, e}$ ) shall be declared. | +| D6.9 | Band 24 support, Declared emission level in Band 24 ( $P_{EM,B24,ind}$ ) | If the AAS BS has TAB connectors declared to support Band 24 the manufacturer shall declare if the AAS BS may operate in geographical areas where FCC regulations apply, the emission level in Band 24 ( $P_{EM,B24,ind, ind=a, b, c, d, e, f}$ ) shall be declared. | +| D6.10 | Co-existence with other systems | The manufacturer shall declare whether the AAS BS under test is intended to operate in geographic areas where one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD, E-UTRA and/or PHS operating in another band are deployed. | +| D6.11 | Co-location with other base stations | The manufacturer shall declare whether the AAS BS under test is intended to operate co-located with Base Stations of one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD and/or E-UTRA operating in another band. | +| D6.12 | TAB connector capability set (CSA) | The manufacturer shall declare the supported capability set(s) according to table 4.9-1 for all TAB connector(s) and supported operating band(s).
NOTE: in case of hybrid AAS BS , set of operating band specific CSA declarations shall be aligned with the set of RCSA's declared by D9.25 in TS 37.145-2 [38] for the radiated testing for the operating band in question. | +| D6.13 | Single or Multi-band TAB connector | Multi-band TAB connector or single band TAB connector .
Declared for every TAB connector | +| D6.14 | Contiguous or non-contiguous spectrum | Ability to support contiguous or non-contiguous (or both) frequency distribution of carriers when operating multi-carrier, per TAB connector , per band, per RAT. | +| D6.15 | Contiguous and non-contiguous parameters identical | If contiguous and non-contiguous operation is possible then parameters are the same. | +| D6.16 | Maximum Radio Bandwidth of the multi-band TAB connector . | Largest radio bandwidth that can be supported by the multi-band TAB connector . May be different for transmit and receive.
Declared for each supported operating band and operating band combination (D6.41) supported for every multi-band TAB connector . | +| D6.17 | Maximum Base Station RF Bandwidth | Largest Base Station RF Bandwidth in the operating band, declared for each supported operating band for every TAB connector . | +| D6.18 | Maximum Base Station RF Bandwidth for contiguous operation. | Largest Base Station RF Bandwidth for contiguous spectrum operation, declared for each supported operating band and CS for every TAB connector . | +| D6.19 | Maximum Base Station RF Bandwidth for non- contiguous operation. | Largest Base Station RF Bandwidth for non-contiguous spectrum operation, declared for each supported operating band and CS for every TAB connector . | +| D6.20 | E-UTRA supported channel bandwidths | E-UTRA channel bandwidth supported for each supported operating band for every TAB connector . | + +| Declaration identifier | Declaration | Description | +|------------------------|-------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D6.21 | TAB connector operating band support | List of operational bands and band combinations supported by the TAB connector , declared for every TAB connector . | +| D6.22 | CA only operation | Capable of operating with CA only but not multiple carriers. Declared per operating band per TAB connector . | +| D6.23 | Single or multiple carrier | Capable of operating with a single carrier (only) or multiple carriers per operating band, per RAT for all TAB connectors . | +| D6.24 | maximum number of supported carriers per band | Maximum number of supported carriers per supported band, made per band, per RAT for all TAB connectors . | +| D6.25 | Total maximum number of supported carriers | Maximum number of supported carriers for all supported bands, declared for every TAB connector . | +| D6.26 | Reduced number of supported carriers at the rated total output power in Multi-RAT operations | Declared for each supported operating band for all TAB connectors . | +| D6.27 | Reduced total output power at the total number of supported carriers in Multi-RAT operations | Declared for each supported operating band for all TAB connectors (Note 1, Note 2). | +| D6.28 | Other band combination multi-band restrictions | Declare any other limitations under simultaneous operation in the declared band combinations (D6.41) for each multi-band TAB connector which have any impact on the test configuration generation.
For every multi-band TAB connector . | +| D6.30 | The rated carrier output power for each TAB connector $P_{\text{Rated,c,TABC}}$ | $P_{\text{Rated,c,TABC}}$ , is declared per supported operating band, per supported RAT for all TAB connector(s) (Note 1, Note 2). | +| D6.31 | The rated carrier output power per TAB connector , for contiguous spectrum operation | The rated carrier output power per TAB connector , for contiguous spectrum operation. Declared for each supported operational band and CS, for all TAB connectors (Note 1, Note 2). | +| D6.32 | The rated carrier output power per TAB connector , for non-contiguous spectrum operation | The rated carrier output power per TAB connector , for non-contiguous spectrum operation. Declared for each supported operational band and CS, for all TAB connectors (Note 1, Note 2). | +| D6.33 | The rated output power per RAT for each TAB connector , $P_{\text{Rated,RAT,TABC}}$ | $P_{\text{Rated,RAT,TABC}}$ is declared per supported operating band, per supported RAT for all TAB connector(s) (Note 1, Note 2). | +| D6.34 | The rated total output power per TAB connector , $P_{\text{Rated,t,TABC}}$ | The rated total output power $P_{\text{Rated,t,TABC}}$ is declared for supported operating band, for all TAB connector(s) (Note 1, Note 2).
For multi-band TAB connectors $P_{\text{Rated,t,TABC}}$ is declared for each supported band in each supported band combination. | +| D6.35 | The rated total output power per TAB connector , for contiguous spectrum operation | The rated total output power per TAB connector , for contiguous spectrum operation. Declared for each supported operational band and CS, for all TAB connectors (Note 1, Note 2). | +| D6.36 | The rated total output power per TAB connector , for non-contiguous spectrum operation | The rated total output power per TAB connector , for non-contiguous spectrum operation. Declared for each supported operational band and CS, for all TAB connectors (Note 1, Note 2). | +| D6.37 | The rated multi-band total output power per TAB connector , $P_{\text{Rated,MB,TABC}}$ | The rated multi-band total output power ( $P_{\text{Rated,MB,TABC}}$ ), declared for all declared operating band combinations for every multi-band TAB connector . (Note 1, Note 2) | +| D6.38 | $N_{\text{cells}}$ | Number corresponding to the minimum number of cells that can be transmitted by an AAS BS in a particular band with transmission on all TAB connectors supporting the operating band. | +| D6.39 | Maximum supported power difference between carriers | Maximum supported power difference between carriers in each supported operating band, for all TAB connector(s) . | +| D6.40 | Maximum supported power difference between carriers in different operating bands | Supported power difference between any two carriers in any two different supported operating bands, for all declared operating band combination for every multi-band TAB connector(s) .. | +| D6.41 | AAS BS operating band combination support | List of operational bands combinations supported by the AAS BS. | +| D6.42 | Total number of supported carriers for the declared band combinations of the AAS BS | Total number of supported carriers for the declared band combinations (D6.41) of the AAS BS. | +| D6.43 | Intra-system interfering signal TAB connector declaration list | List of TAB connectors for which an intra-system interfering signal level is required to be declared. Declaration is required if the intra-system interfering signal level is larger than the co-location interfering signal level. | +| D6.44 | Intra-system interfering signal level | The interfering signal level in dBm per TAB connector declared for each supported operational band, for all TAB connectors covered by D6.43. | + +| Declaration identifier | Declaration | Description | +|------------------------|-------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| D6.45 | P-CPICH transmission group(s) | Groups of TAB connectors which are declared to transmit the P-CPICH. Declared per operating band, UTRA FDD only. | +| D6.48 | CCPCH transmission group(s) | Groups of TAB connectors which are declared to transmit the CCPCH.
Declared per operating band, UTRA TDD only | + +| Declaration identifier | Declaration | Description | +|------------------------|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D6.51 | UTRA FDD MIMO support. | Number of 'antennas' supported by the UTRA FDD MIMO mode (i.e. 2 or 4).
The concept of "antenna 2", "antenna 3" and "antenna 4" is described in TS 25.104 [2].
Declared per operating band, UTRA FDD only. | +| D6.52 | S-CPICH transmission group(s) | Groups of TAB connectors which are declared to transmit the S-CPICH for each of the 'antennas' declared in D6.49
For UTRA FDD AAS BS operating only "antenna 1" and "antenna 2", mapping for 'antenna 2' is declared.
For UTRA FDD AAS BS operating "antenna 1", "antenna 2", "antenna 3" and "antenna 4", mapping for "antenna 2", "antenna 3", and "antenna 4", is declared.
Declared per operating band, UTRA FDD only.
NOTE: Mapping for "antenna 1" is the same as D6.45. | +| D6.54 | DL RS transmission groups | Groups of TAB connectors which are declared to transmit the DL RS.
Declared per operating band, E-UTRA only. | +| D6.57 | UTRA Inner loop power control dynamic range | Power control dynamic range for UTRA inner loop power control.
Declared for each supported operating band, for all TAB connector(s) . UTRA only. | +| D6.58 | TAE groups | Set of declared TAB connector beam forming groups on which the TAE requirements apply.
All TAB connectors belong to at least 1 TAB connector beam forming group (even if it's a TAB connector beam forming group consisting of 1 connector).
The smallest possible number of TAB connector beam forming groups need to be declared such that there is no TAB connector not contained in at least one of the declared TAB connector beam forming groups .
Declared for each supported RAT and operating band. | +| D6.59 | Inter-band CA or HSDPA | Band combinations declared to support inter-band CA or multi-band HSDPA.
Declared for every multi-band TAB connector which support CA or multi-band HSDPA.
NOTE: Inter-band HSDPA is called multi-band HSDPA in UTRA specifications. Examples of the multi-band HSDPA are DB-DC-HSDPA or Dual band 4C-HSDPA. | +| D6.60 | Intra-band contiguous CA or HSDPA | Bands declared to support intra-band contiguous CA (per CA capable TAB connector , as in D6.22) or contiguous multi-carrier HSDPA.
Declared for every TAB connector which support CA or multi-band HSDPA.
NOTE: Intra-band HSDPA is called multi-carrier HSDPA in UTRA specifications. Examples of the contiguous multi-carrier HSDPA are DC-HSDPA, 4C-HSDPA, or 8C-HSDPA. | +| D6.61 | Intra-band non-contiguous CA or HSDPA | Bands declared to support intra-band non-contiguous CA (per CA capable TAB connector , as in D6.22) or non-contiguous multi-carrier HSDPA.
Declared for every TAB connector which support CA or multi-band HSDPA.
NOTE: Intra-band HSDPA is called multi-carrier HSDPA in UTRA specifications. Example of the non-contiguous multi-carrier HSDPA is NC-4C-HSDPA. | +| D6.70 | Equivalent TAB connectors | List of TAB connectors which have been declared equivalent.
Equivalent TAB connectors imply that the TAB connectors are expected to behave in the same way when presented with identical signals under the same operating conditions. All declarations made for the TAB connectors are identical and the transmitter unit and/or receiver unit driving the TAB connector are of identical design. | +| D6.71 | BS class | BS Class of the AAS BS, declared as Wide Area BS, Medium Range BS, or Local Area BS. | +| D6.72 | TAB connector RX min cell group | Declared as a group of TAB connectors to which RX requirements are applied. This declaration corresponds to group of TAB connectors which are responsible for receiving a cell when the hybrid AAS BS setting corresponding to the declared minimum number of cells (Ncells) with transmission on all TAB connectors supporting an operating band. | +| D6.73 | TAB connector TX min cell group | Declared group of TAB connectors to which TX requirements are | + +| Declaration identifier | Declaration | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | applied. This declaration corresponds to group of TAB connectors which are responsible for transmitting a cell when the hybrid AAS BS setting corresponding to the declared minimum number of cells (Ncells) with transmission on all TAB connectors supporting an operating band. | +| D6.74 | TAB connectors used for performance requirement testing | To reduce test complexity, declaration of a representative (sub)set of TAB connectors to be used for performance requirement test purposes. At least one TAB connector mapped to each demodulation branch is declared. | +| D6.75 | NR supported channel bandwidths and SCS | NR channel bandwidth and SCS supported. Declared per supported operating band and TAB connector. | +| D6.76 | Total RF bandwidth (BW tot ) | Total RF bandwidth BW tot of transmitter/receiver, declared per the band combination. | +| D6.77 | Band 54 support, Declared emission level in Band 54 (P EM,B54,ind ) | If the AAS BS has TAB connectors declared to support Band 54 the manufacturer shall declare if the AAS BS may operate in geographical areas where FCC regulations apply, the emission level in Band 54 (P EM,B54,ind , ind=a, b, c, d, e, f) shall be declared. | +| NOTE 1: If a BS is capable of 256QAM DL operation but not capable of 1024QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. | | | +| NOTE 2: If a BS is capable of 1024QAM DL operation then up to three rated output power declarations may be made. One declaration is applicable when configured for 1024QAM transmissions, a different declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when configured neither for 256 QAM nor 1024QAM transmissions. | | | + +## 4.11 Test signal configurations for AAS BS + +### 4.11.1 General + +The test configurations shall be constructed using the methods defined below subject to the parameters declared by the manufacturer as listed in clause 4.10. + +For test contiguous spectrum operation configurations used in receiver tests only the carriers in the outermost frequency positions in the *TAB connector Base Station RF Bandwidth* need to be generated by the test equipment. For non-contiguous spectrum operation test configurations used in receiver tests, outermost carriers for each sub-block need to be generated by the test equipment. + +The applicable test models for generation of the carrier transmit test signal are defined in clause 4.12.2. + +NOTE: If required, carriers are shifted to align with the channel raster Foffset. + +#### 4.11.1a NR Test signal used to build Test Configurations + +The signal's Channel Bandwidth and Subcarrier spacing used to build NR Test Configurations shall be selected according to table 4.11.1a-1. + +**Table 4.11.1a-1: Signal to be used to build NR TCs** + +| Operating Band characteristics | | F DL_high – F DL_low < 100 MHz | F DL_high – F DL_low ≥ 100 MHz | +|--------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------|------------------------------------------------------| +| TC signal characteristics | BW channel | 5 MHz (Note 1) | 20 MHz (Note 1) | +| | Subcarrier spacing | Smallest supported subcarrier spacing | | +| Note 1: If this channel bandwidth is not supported, the narrowest supported channel bandwidth shall be used. | | | | + +## 4.11.2 Test signal configurations + +### 4.11.2.1 ATC1: UTRA multicarrier operation + +#### 4.11.2.1.1 General + +The purpose of ATC1 is to test UTRA multi-carrier aspects. + +#### 4.11.2.1.2 ATC1a generation + +ATC1 should be constructed using the following method: + +- The *Base Station RF Bandwidth* shall be the declared maximum *Base Station RF Bandwidth* for contiguous operation (see table 4.10-1, D6.18). +- Place one UTRA FDD carrier adjacent to the upper *Base Station RF Bandwidth edge* and one UTRA FDD carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, alternately place a UTRA FDD carrier adjacent to the already placed carriers at the low and high *Base Station RF Bandwidth edges* until there is no more space to fit a carrier or the *TAB connector* does not support more carriers. The nominal carrier spacing defined in clause 4.6 shall apply. +- The carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. + +#### 4.11.2.1.3 ATC1b generation + +ATC1b is constructed using the following method: + +- The *Base Station RF Bandwidth* shall be the declared maximum *Base Station RF Bandwidth* for contiguous operation (see table 4.10-1, D6.18). +- Place one UTRA TDD carrier adjacent to the upper *Base Station RF Bandwidth edge* and one UTRA TDD carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, alternately place a UTRA TDD carrier adjacent to the already placed carriers at the low and high *Base Station RF Bandwidth edges* until there is no more space to fit a carrier or the *TAB connector* does not support more carriers. The nominal carrier spacing defined in clause 4.6 shall apply. + +#### 4.11.2.1.4 ATC1 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals $P_{\text{rated,RAT,TABC}}$ for UTRA according to the manufacturer's declaration in clause 4.10. + +### 4.11.2.2 ANTC1: UTRA FDD multicarrier non-contiguous operation + +#### 4.11.2.2.1 General + +The purpose of ANTC1 is to test UTRA FDD multicarrier non-contiguous aspects. + +#### 4.11.2.2.2 ANTC1 generation + +The purpose of ANTC1a is to test UTRA multicarrier non-contiguous aspects. ANTC1 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* for non-contiguous operation (see table 4.10-1, D6.19) of the *TAB connector*. The *station RF bandwidth* consists of one *sub-block gap* and two sub-blocks located at the edges of the declared maximum *Base Station RF Bandwidth* for non-contiguous operation. + +- For transmitter tests, place one UTRA carrier adjacent to the upper *Base Station RF Bandwidth edge* and one UTRA carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For receiver tests, place one UTRA carrier adjacent to the upper *Base Station RF Bandwidth edge* and one UTRA carrier adjacent to the lower *Base Station RF Bandwidth edge*. For single-band operation, if the maximum *Base Station RF Bandwidth* for non-contiguous operation is at least 35 MHz and the *TAB connector* supports at least 4 UTRA FDD carriers, place a UTRA FDD carrier adjacent to each already placed carrier for each sub-block. The nominal carrier spacing defined in clause 4.6 shall apply. +- The sub-block edges adjacent to the *sub-block gap* shall be determined using the specified $F_{\text{offset, RAT}}$ for the carrier adjacent to the *sub-block gap*. +- The UTRA FDD carrier in the lower sub-block may be shifted maximum 100 kHz towards lower frequencies and the UTRA FDD carrier in the upper sub-block may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. + +#### 4.11.2.2.3 ANTC1 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals $P_{\text{Rated,RAT,TABC}}$ according to the manufacturer's declaration in clause 4.10. + +#### 4.11.2.3 ATC2: E-UTRA multicarrier operation + +##### 4.11.2.3.1 General + +The purpose of ATC2a is to test E-UTRA multi-carrier aspects excluding CA occupied bandwidth. + +The purpose of ATC2b is to test E-UTRA contiguous CA occupied bandwidth. + +##### 4.11.2.3.2 ATC2a generation + +ATC2a is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* for contiguous operation (see table 4.10-1, D6.18) of the *TAB connector*. +- Select the narrowest supported E-UTRA carrier and place it adjacent to the low *Base Station RF Bandwidth edge*. Place a 5 MHz E-UTRA carrier adjacent to the high *Base Station RF Bandwidth edge*. The specified $F_{\text{Offset-RAT}}$ shall apply. +- For transmitter tests, select as many 5 MHz E-UTRA carriers that the *TAB connector* supports and that fit in the rest of the *Base Station RF Bandwidth*. Place the carriers adjacent to each other starting from the high *Base Station RF Bandwidth edge*. The nominal carrier spacing defined in clause 4.6 shall apply. The specified $F_{\text{Offset-RAT}}$ shall apply. +- If 5 MHz E-UTRA carriers are not supported by the *TAB connector* the narrowest supported *channel bandwidth* shall be selected instead. + +The test configuration should be constructed on a per band basis for all component carriers of the inter-band CA bands declared to be supported by the *TAB connector* (see table 4.10-1, D6.29). All configured component carriers are transmitted simultaneously in the tests where the transmitter should be on. + +##### 4.11.2.3.3 ATC2b generation + +ATC2b is constructed on a per band basis using the following method: + +- Of all component carrier combinations supported by the *TAB connector*, those which have smallest or largest sum of *channel bandwidth* of component carrier, shall be tested. Of all component carrier combinations which have smallest or largest sum of channel bandwidth of component carriers supported by the BS, only one combination having largest sum and one combination having smallest sum shall be tested irrespective of the number of component carriers. + +- Of all component carrier combinations which have same sum of *channel bandwidth* of component carrier, select those with the narrowest carrier at the lower *Base Station RF Bandwidth edge*. +- Of the combinations selected in the previous step, select one with the narrowest carrier at the upper *Base Station RF Bandwidth edge*. +- If there are multiple combinations fulfilling previous steps, select the one with the smallest number of component carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier being adjacent to the lowest carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier being adjacent to the highest carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier being adjacent to the carrier which has been selected in the previous step. +- If there are multiple combinations fulfilling previous steps, repeat the previous step until there is only one combination left. +- The nominal carrier spacing defined in clause 4.6 shall apply. + +#### 4.11.2.3.4 ATC2 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals $P_{\text{rated,RAT,TABC}}$ for E-UTRA (see table 4.10-1, D6.33). + +For a *TAB connector* declared to support only CA operation (see table 4.10-1, D6.22), set the power spectral density of each carrier to the same level so that the sum of the carrier powers equals the rated total output power $P_{\text{Rated,t,TABC}}$ (see table 4.10-1, D6.34). + +#### 4.11.2.4 ANTC2: E-UTRA multicarrier non-contiguous operation + +##### 4.11.2.4.1 General + +The purpose of ANTC2 is to test E-UTRA multi-carrier non-contiguous aspects. + +##### 4.11.2.4.2 ANTC2 generation + +ANTC2 is constructed as NTC2 in TS 37.141 [16] clause 4.8.2a.1. + +ANTC2 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* for non-contiguous operation (see table 4.10-1, D6.19) of the *TAB connector*. The *Base Station RF Bandwidth* consists of one *sub-block gap* and two sub-blocks located at the edges of the declared maximum *Base Station RF Bandwidth* (see table 4.10-1, D.17). +- For transmitter tests, place a 5 MHz E-UTRA carrier adjacent to the upper *Base Station RF Bandwidth edge* and a 5 MHz E-UTRA carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset,RAT}}$ shall apply. If 5 MHz E-UTRA carriers are not supported by the *TAB connector*, the narrowest supported *channel bandwidth* shall be selected instead. +- For receiver tests, place a 5 MHz E-UTRA carrier adjacent to the upper *Base Station RF Bandwidth edge* and a 5 MHz E-UTRA carrier adjacent to the lower *Base Station RF Bandwidth edge*. If 5 MHz E-UTRA carriers are not supported by the *TAB connector*, the narrowest supported *channel bandwidth* shall be selected instead. +- For single-band operation receiver tests, if the remaining gap is at least 15 MHz plus two times the *channel bandwidth* used in the previous step and the *TAB connector* supports at least 4 E-UTRA carriers, place a E-UTRA carrier of this *channel bandwidth* adjacent to each already placed carrier for each sub-block. The nominal carrier spacing defined in clause 4.6 shall apply. + +- The sub-block edges adjacent to the *sub-block gap* shall be determined using the specified $F_{\text{offset, RAT}}$ for the carrier adjacent to the *sub-block gap*. + +#### 4.11.2.4.3 ANTC2 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals $P_{\text{rated,RAT,TABC}}$ for E-UTRA (see table 4.10-1, D6.33). + +#### 4.11.2.5 ATC3: UTRA and E-UTRA multi-RAT operation + +##### 4.11.2.5.1 General + +The purpose of ATC3 is to test UTRA and E-UTRA multi-RAT aspects. + +If the rated total output power per *TAB connector* $P_{\text{Rated,t,TABC}}$ (see table 4.10-1, D.34) and total number of supported carriers (see table 4.10-1, D.25) are not simultaneously supported in multi-RAT operations, two instances of ATC3 shall be generated using the following values for rated total output power and the total number of supported carriers: + +- 1) The rated total output power per *TAB connector* $P_{\text{Rated,t,TABC}}$ (see table 4.10-1, D6.34) and the reduced number of supported carriers at the rated total output power in multi-RAT operations (see table 4.10-1, D6.26). +- 2) The reduced total output power at the total number of supported carriers in multi-RAT operations (see table 4.10-1, D6.27) and the total number of supported carriers (see table 4.10-1, D6.25). + +Tests that use ATC3 shall be performed using both instances 1) and 2) of ATC3. + +##### 4.11.2.5.2 ATC3a generation + +ATC3a is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* (see table 4.10-1, D6.17) of the *TAB connector*. +- Select an FDD UTRA carrier to be placed at the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- Place a 5 MHz E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. If that is not possible use the narrowest E-UTRA carrier supported by the *TAB connector*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, alternately add FDD UTRA carriers at the low end and 5 MHz E-UTRA carriers at the high end adjacent to the already placed carriers until the *Base Station RF Bandwidth* is filled or the total number of supported carriers (see table 4.10-1, D6.25) is reached. The nominal carrier spacing defined in clause 4.6 shall apply. + +##### 4.11.2.5.3 ATC3b generation + +ATC3b is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* (see table 4.10-1, D6.17) of the *TAB connector*. +- Select a UTRA TDD carrier to be placed at the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- Place a 5 MHz E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. If that is not possible use the narrowest E-UTRA carrier supported by the *TAB connector*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, alternately add UTRA TDD carriers at the low end and 5 MHz E-UTRA carriers at the high end adjacent to the already placed carriers until the *Base Station RF Bandwidth* is filled or the total number of supported carriers (see table 4.10-1, D6.25) is reached. The nominal carrier spacing defined in clause 4.6 shall apply. + +#### 4.11.2.5.4 ATC3 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals $P_{\text{Rated,RAT,TABC}}$ according to the manufacturer's declaration in clause 4.10. + +#### 4.11.2.6 ANTC3: UTRA and E-UTRA multi-RAT non-contiguous operation + +##### 4.11.2.6.1 General + +The purpose of ANTC3 is to test UTRA and E-UTRA multi RAT non-contiguous aspects. + +##### 4.11.2.6.2 ANTC3 generation + +ANTC3 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* for non-contiguous operation (see table 4.10-1, D6.19) of the *TAB connector*. The *Base Station RF Bandwidth* consists of one *sub-block gap* and two sub-blocks located at the edges of the declared maximum *Base Station RF Bandwidth* for non-contiguous operation (see table 4.10-1, D6.19). +- For transmitter tests, place an UTRA carrier at the lower *Base Station RF Bandwidth edge* and a 5 MHz E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset,RAT}}$ shall apply. If 5 MHz E-UTRA carriers are not supported by the *TAB connector*, the narrowest supported *channel bandwidth* shall be selected instead. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. In case rated total output power is not reached, the narrowest E-UTRA channel BW which supports rated carrier output power shall be selected. If still there are some output power room, alternately place an E-UTRA carrier of this BW adjacent to the carrier at the lower *Base Station RF Bandwidth edge* and UTRA carrier adjacent to the carrier at the upper *Base Station RF Bandwidth edge* until the rated total output power or the total number of supported carriers is reached. +- For receiver tests, place an UTRA carrier at the lower *Base Station RF Bandwidth edge* and a 5 MHz E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset,RAT}}$ shall apply. If 5 MHz E-UTRA carriers are not supported by the *TAB connector*, the narrowest supported *channel bandwidth* shall be selected instead. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- For single-band operation receiver tests, if the remaining gap is at least 20 MHz plus the *channel bandwidth* of the E-UTRA carrier used in the previous step and the *TAB connector* supports at least 2 UTRA and 2 E-UTRA carriers, place a E-UTRA carrier of this *channel bandwidth* adjacent to the carrier at the lower *Base Station RF Bandwidth edge* and UTRA carrier adjacent to the carrier at the upper *Base Station RF Bandwidth edge*. The nominal carrier spacing defined in clause 4.6 shall apply. The UTRA FDD may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. +- The sub-block edges adjacent to the *sub-block gap* shall be determined using the specified $F_{\text{offset,RAT}}$ for the carrier adjacent to the *sub-block gap*. + +##### 4.11.2.6.3 ANTC3 power allocation + +Set the power of each carrier to the same power unless the rated carrier output power for RATs are different so that the sum of the carrier powers equals the $P_{\text{Rated,TABC}}$ according to manufacturer's declarations in subclause 4.10. + +#### 4.11.2.7 ATC4: Single carrier for receiver tests + +##### 4.11.2.7.1 ATC4a generation + +ATC4a is constructed using the following method: + +- Place a single UTRA carrier in the middle of the maximum supported *Base Station RF Bandwidth*. The carrier may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. + +#### 4.11.2.7.2 ATC4b generation + +ATC4b is constructed using the following method: + +- Place the narrowest supported E-UTRA carrier in the middle of the maximum supported *Base Station RF Bandwidth*. + +#### 4.11.2.7.3 ATC4c generation + +ATC4c is constructed using the following method: + +- Place a single UTRA TDD carrier in the middle of the maximum supported *Base Station RF Bandwidth*. + +#### 4.11.2.7.4 ATC4d generation + +ATC4d is constructed using the following method: + +- Place a single NR carrier as specified in clause 4.11.1a in the middle of the maximum radiated *Base Station RF Bandwidth*. + +### 4.11.2.8 ATC5: MB-MSR operation + +#### 4.11.2.8.1 ATC5a: MB-MSR test configuration for full carrier allocation + +##### 4.11.2.8.1.1 General + +The purpose of ATC5a is to test *multi-band TAB connectors*, considering maximum supported number of carriers. + +##### 4.11.2.8.1.2 ATC5a generation + +ATC5a is based on re-using the existing test configurations applicable per band on *multi-band TAB connectors*. ATC5a is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* (see table 4.10-1, D6.17) of the *multi-band TAB connector*. +- The number of carriers of each supported operating band shall be the declared maximum number of supported carriers by the *multi-band TAB connector* in each band (see table 4.10-1, D6.25). Carriers shall first be placed at the outermost edges of the declared maximum *Radio Bandwidth* (see table 4.10-1, D6.16). Additional carriers shall next be placed at the edges of the *Base Station RF Bandwidths*, if possible. +- The allocated *Base Station RF Bandwidth* of the outermost bands shall be located at the outermost edges of the declared maximum *Radio Bandwidth* (see table 4.10-1, D6.16). +- Each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to the test configuration referenced in Table 4.11.2.8.1.2-1, where the declared parameters for multi-band operation shall apply. The mirror image of the single band test configuration shall be used in the highest band being tested for the *TAB connector*. +- If a *multi-band TAB connector* supports three carriers only, two carriers shall be placed in one band according to the relevant test configuration while the remaining carrier shall be placed at the edge of the maximum *Radio Bandwidth* (see table 4.10-1, D6.16) in the other band. +- If the sum of the maximum *Base Station RF bandwidths* of each of the supported operating bands is greater than the declared *Total RF Bandwidth* BWtot (D6.76) of transmitter/receiver for the declared band combinations (see table 4.10-1, D6.41) of the *TAB connector* then repeat the steps above for test configurations where the *Base Station RF Bandwidth* of one of the operating band shall be reduced so that the declared *Total RF Bandwidth* of the *TAB connector* is not exceeded and vice versa. +- If the sum of the maximum number of supported carrier of each supported operating bands for the *multi-band TAB connector* is larger than the declared total number of supported carriers for the declared band combinations (see table 4.10-1, D6.42) of the AAS BS, repeat the steps above for test configurations where in each test + +configuration the number of carriers of one of the operating band shall be reduced so that the total number of supported carriers is not exceeded and vice versa. + +**Table 4.11.2.8.1.2-1: The applicability of test configuration for carrier placement in each band** + +| BC | CSA1 | CSA2 | CSA3 | CSA3A | CSA3B | CSA4 | CSA5 | +|-----|-------|-------|-------|-------|-------|-------|-------| +| BC1 | ATC1a | ATC2a | ATC3a | ATC6 | ATC8 | ATC1a | ATC2a | +| BC2 | ATC1a | ATC2a | ATC3a | ATC6 | ATC8 | ATC1a | ATC2a | +| BC3 | ATC1b | ATC2a | ATC3b | ATC6 | N/A | ATC1b | ATC2a | + +#### 4.11.2.8.1.3 ATC5a power allocation + +Unless otherwise stated, set the power of each carrier ( $P_{\text{Rated,c,TABC}}$ ) in all supported operating bands to the same power so that the sum of the carrier powers equals the rated total output power ( $P_{\text{Rated,MB,TABC}}$ ) according to the manufacturer's declaration. + +If the allocated power of a supported operating band(s) exceeds the declared rated total output power of the operating band(s) ( $P_{\text{Rated,MB,TABC}}$ ) in multi-band operation, the exceeded part shall, if possible, be reallocated into the other band(s). If the power allocated for a carrier exceeds the rated carrier output power declared for that carrier ( $P_{\text{Rated,c,TABC}}$ ), the exceeded power shall, if possible, be reallocated into the other carriers. + +#### 4.11.2.8.2 ATC5b: MB-MSR test configuration with high PSD per carrier + +##### 4.11.2.8.2.1 General + +The purpose of ATC5b is to test multi-band operation aspects considering higher PSD cases with reduced number of carriers and non-contiguous operation (if supported) in multi-band mode. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth and the narrowest supported E-UTRA channel bandwidth for each operating band shall be used in the test configuration. + +##### 4.11.2.8.2.2 ATC5b generation + +ATC5b is based on re-using the existing test configurations applicable per band on *multi-band TAB connectors*. ATC5b is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* (see table 4.10-1, D6.16) of the *multi-band TAB connector*. +- The allocated *Radio Bandwidth* of the outermost bands shall be located at the outermost edges of the declared maximum *Radio Bandwidth* (see table 4.10-1, D6.16). +- The maximum number of carriers is limited to two per band. Carriers shall be placed at the outermost edges of the declared maximum *Radio Bandwidth* (see table 4.10-1, D6.16). +- Each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to the test configuration referenced in Table 4.11.2.8.2.2-1, where the declared parameters for multi-band operation shall apply. The mirror image of the single band test configuration shall be used in the highest band being tested for the *TAB connector*. +- For AAS BS supporting CSA4 in the band, if a *multi-band TAB connector* supports three carriers only, two carriers shall be placed in one band according to ATC2 while the remaining carrier shall be placed at the edge of the Maximum *Base Station RF Bandwidth* in the other band. +- If the sum of the maximum *Base Station RF bandwidths* of each of the supported operating bands is greater than the declared *Total RF Bandwidth* $BW_{\text{tot}}$ (D6.76) of transmitter/receiver for the declared band combinations (see table 4.10-1, D6.41) of the *TAB connector* then repeat the steps above for test configurations where the *Base Station RF Bandwidth* of one of the operating band shall be reduced so that the declared *Total RF Bandwidth* of the *TAB connector* is not exceeded and vice versa. + +**Table 4.11.2.8.2.2-1: The applicability of test configuration for carrier placement in each band** + +| BC | CSA1 | CSA2 | CSA3 | CSA3A | CSA3B | CSA4 | CSA5 | +|-----|--------|-------|-------|-------|-------|-------|-------| +| BC1 | ANTC1a | ANTC2 | ANTC3 | ANTC6 | ANTC8 | ANTC1 | ANTC2 | +| BC2 | ANTC1a | ANTC2 | ANTC3 | ANTC6 | ANTC8 | ANTC1 | ANTC2 | +| BC3 | ATC1b | ANTC2 | ANTC3 | ANTC6 | N/A | N/A | ANTC2 | + +#### 4.11.2.8.2.3 ATC5b power allocation + +Unless otherwise stated, set the power of each carrier ( $P_{\text{Rated,c,TABC}}$ ) in all supported operating bands to the same power so that the sum of the carrier powers equals the rated total output power ( $P_{\text{Rated,MB,TABC}}$ ) according to the manufacturer's declaration. + +If the allocated power of a supported operating band(s) exceeds the declared rated total output power of the operating band(s) ( $P_{\text{Rated,t,TABC}}$ ) in multi-band operation, the exceeded part shall, if possible, be reallocated into the other band(s). If the power allocated for a carrier exceeds the rated carrier output power declared for that carrier ( $P_{\text{Rated,c,TABC}}$ ), the exceeded power shall, if possible, be reallocated into the other carriers. + +#### 4.11.2.9 ATC6: E-UTRA and NR multi-RAT operation + +##### 4.11.2.9.1 General + +The purpose of ATC6 is to test E-UTRA and NR multi-RAT aspects. + +If the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, two instances of ATC6 shall be generated using the following values for rated total output power and the total number of supported carriers: + +- 1) The rated total output power and the reduced number of supported carriers at the rated total output power in Multi-RAT operations. +- 2) The reduced total output power at the total number of supported carriers in Multi-RAT operations and the total number of supported carriers. + +Tests that use ATC6 shall be performed using both instances 1) and 2) of ATC6. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth for the operating band shall be used in the test configuration. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5 MHz unless the BS does not support 5 MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth for the operating band. + +##### 4.11.2.9.2 ATC6 generation + +ATC6 is only applicable for a BS that supports E-UTRA and NR. ATC6 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* (D6.17) of the *TAB connector*. +- Select a NR carrier as specified in subclause 4.11.1a to be placed at the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset,RAT}}$ shall apply. +- Place an E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset,RAT}}$ shall apply. +- For transmitter tests, alternately add NR carriers as specified in subclause 4.11.1a at the low end and E-UTRA carriers at the high end adjacent to the already placed carriers until the *Base Station RF Bandwidth* is filled or the total number of supported carriers (see table 4.10-1, D9.14) is reached. The nominal carrier spacing defined in subclause 4.6 shall apply. + +#### 4.11.2.9.3 ATC6 power allocation + +- a) Unless otherwise stated, set each carrier to the same power so that the sum of the carrier powers equals the rated total output power as appropriate for the test configuration according to manufacturer's declarations in subclause 4.10. +- b) In case that ATC6 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in subclause 4.10, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacturer's declaration the power in the other RAT(s) does not need to be increased. + +#### 4.11.2.10 ANTC6: E-UTRA and NR multi RAT non-contiguous operation + +##### 4.11.2.10.1 General + +The purpose of ANTC6 is to test E-UTRA and NR multi RAT non-contiguous aspects. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth shall be used in the test configuration. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5 MHz unless the BS does not support 5 MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth. + +##### 4.11.2.10.2 ANTC6 generation + +ANTC6 is only applicable for a BS that supports E-UTRA and NR. ANTC6 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* for non-contiguous operation (D6.19) of the *TAB connector*. The *Base Station RF Bandwidth* consists of one *sub-block gap* and two sub-blocks located at the edges of the declared maximum *Base Station RF Bandwidth* for non-contiguous operation (D6.19). +- For transmitter tests, place an NR carrier as specified in subclause 4.11.1a at the lower *Base Station RF Bandwidth edge* and an E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. In case rated total output power is not reached, the narrowest E-UTRA and/or NR channel BW which supports rated carrier output power shall be selected. If still there are some output power room, alternately place an E-UTRA carrier adjacent to the carrier at the lower *Base Station RF Bandwidth edge* and NR carrier adjacent to the carrier at the upper *Base Station RF Bandwidth edge* until the rated total output power or the total number of supported carriers is reached. +- For receiver tests, place a NR carrier as specified in subclause 4.11.1a at the lower *Base Station RF Bandwidth edge* and an E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{offset, RAT}}$ for the carrier adjacent to the sub-block gap. + +##### 4.11.2.10.3 ANTC6 power allocation + +- a) Unless otherwise stated, set each carrier to the same power unless the rated carrier output power for RATs are different so that the sum of the carrier powers equals the rated total output power appropriate for the test configuration according to manufacturer's declarations in subclause 4.10. +- b) In case that ANTC6 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in subclause 4.10, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacturer's declaration the power in the other RAT(s) does not need to be increased. + +#### 4.11.2.11 ATC7: NR multicarrier operation + +##### 4.11.2.11.1 General + +The purpose of ATC7 is to test NR multi-carrier aspects excluding CA occupied bandwidth. + +##### 4.11.2.11.2 ATC7 generation + +ATC7 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* for contiguous operation (see table 4.10-1, D6.18) of the *TAB connector*. +- Select the NR carrier as specified in clause 4.11.1a and place it adjacent to the low *Base Station RF Bandwidth edge*. Place a similar NR carrier adjacent to the high *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, select as many similar NR carriers that the *TAB connector* supports and that fit in the rest of the *Base Station RF Bandwidth*. Place the carriers adjacent to each other starting from the high *Base Station RF Bandwidth edge*. The nominal carrier spacing defined in clause 4.6 shall apply. The specified $F_{\text{offset, RAT}}$ shall apply. + +The test configuration should be constructed on a per band basis for all component carriers of the inter-band CA bands declared to be supported by the *TAB connector* (see table 4.10-1, D6.29). All configured component carriers are transmitted simultaneously in the tests where the transmitter should be on. + +##### 4.11.2.11.3 ATC7 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals $P_{\text{rated,RAT,TABC}}$ for NR according to the manufacturer's declaration in clause 4.10. + +For a *TAB connector* declared to support only CA operation (see table 4.10-1, D6.22), set the power spectral density of each carrier to the same level so that the sum of the carrier powers equals the rated total output power ( $P_{\text{Rated,t,TABC}}$ ) according to the manufacturer's declaration in clause 4.10. + +#### 4.11.2.12 ANTC7: NR multicarrier non-contiguous operation + +##### 4.11.2.12.1 General + +The purpose of ANTC7 is to test NR multicarrier non-contiguous aspects. + +##### 4.11.2.12.2 ANTC7 generation + +ANTC7 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum *Base Station RF Bandwidth* for non-contiguous operation (D6.19) of the *TAB connector*. The *Base Station RF Bandwidth* consists of one *sub-block gap* and two sub-blocks located at the edges of the declared maximum *Base Station RF Bandwidth* (D.17). +- For transmitter tests, place a NR carrier as specified in clause 4.11.1a adjacent to the upper *Base Station RF Bandwidth edge* and a similar NR carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For receiver tests, place a similar NR carrier adjacent to the upper *Base Station RF Bandwidth edge* and a similar NR carrier adjacent to the lower *Base Station RF Bandwidth edge*. +- The sub-block edges adjacent to the *sub-block gap* shall be determined using the specified $F_{\text{offset, RAT}}$ for the carrier adjacent to the *sub-block gap*. + +#### 4.11.2.12.3 ANTC7 power allocation + +Set the power of each carrier to the same power so that the sum of the carrier powers equals $P_{\text{rated,RAT,TABC}}$ according to the manufacturer's declaration in clause 4.10. + +#### 4.11.2.13 ATC8: UTRA, E-UTRA and NR multi-RAT operation + +##### 4.11.2.13.1 General + +The purpose of ATC8 is to test UTRA, E-UTRA and NR multi-RAT aspects. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth for the operating band shall be used in the test configuration. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5 MHz unless the BS does not support 5 MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth for the operating band. + +##### 4.11.2.13.2 ATC8 generation + +ATC8 is only applicable for a BS that supports UTRA, E-UTRA and NR. ATC8 is constructed using the following method: + +For transmitter tests, if the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, two instances of ATC8 shall be generated using the following values for rated total output power and the total number of supported carriers: + +- 1) The rated total output power and the reduced number of supported carriers at the rated total output power in multi-RAT operations +- 2) The reduced rated total output power at the total number of supported carriers in multi-RAT operations and the total number of supported carriers. + +If the rated total output power and total number of supported carriers are not simultaneously supported in multi-RAT operations, tests that use ATC8 shall be performed using both instances 1) and 2) of ATC8. + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth. + - Adjacent to the lower Base Station RF Bandwidth edge: Place an NR carrier. The specified FOffset-RAT shall apply. + - Adjacent to the upper Base Station RF Bandwidth edge: Place a E-UTRA carrier. The specified FOffset-RAT shall apply. + - Place UTRA carrier adjacent to the already placed E-UTRA carrier. + - The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- For transmitter tests, alternately add NR carriers at the low end and E-UTRA carriers at the high end adjacent to the already placed carriers until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. The nominal carrier spacing defined in subclause 4.6 shall apply. + +##### 4.11.2.13.3 ATC8 power allocation + +- a) Unless otherwise stated, set each carrier to the same power so that the sum of the carrier powers equals the rated total output power as appropriate for the test configuration according to manufacturer's declarations in subclause 4.10. +- b) In case that ATC8 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in subclause 4.10, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacturer's declaration the power in the other RAT(s) does not need to be increased. + +#### 4.11.2.14 ANTC8: UTRA, E-UTRA and NR multi-RAT non-contiguous operation + +The purpose of ANTC8 is to test UTRA, E-UTRA and NR multi RAT non-contiguous aspects. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth shall be used in the test configuration. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5MHz unless the BS does not support 5MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth. + +##### 4.11.2.14.1 ANTC8 generation + +ANTC8 is only applicable for a BS that supports UTRA, E-UTRA and NR. ANTC8 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- Adjacent to the lower Base Station RF Bandwidth edge: + - Place an NR carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Adjacent to the upper Base Station RF Bandwidth edge: + - Place an E-UTRA carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. + - Place a UTRA carrier adjacent to the lower sub-block edge of the upper sub-block. +- For transmitter tests, place one UTRA adjacent to the upper sub-block edge of the lower sub-block. The nominal carrier spacing defined in subclause 4.6 shall apply. In case rated total output power is not reached, for the NR carrier adjacent to the lower Base Station RF Bandwidth edge, the narrowest NR channel BW which supports rated carrier output power shall be selected. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier adjacent to the sub-block gap. The carrier(s) may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. + +##### 4.11.2.14.2 ANTC8 power allocation + +- a) Unless otherwise stated, set each carrier to the same power unless the rated carrier output power for RATs are different so that the sum of the carrier powers equals the rated total output power appropriate for the test configuration according to manufacturer's declarations in subclause 4.10. +- b) In case that ANTC8 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in subclause 4.10, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacturer's declaration the power in the other RAT(s) does not need to be increased. + +## 4.12 RF channels and test models + +### 4.12.1 RF channels + +For single carrier tests unless otherwise stated the tests shall be performed with a single carrier at each of the RF channels B, M and T. + +Many tests in this TS are performed with the maximum *Base Station RF Bandwidth* located at the bottom, middle and top of the supported frequency range in the operating band. These are denoted as $B_{\text{RFBW}}$ (bottom), $M_{\text{RFBW}}$ (middle) and $T_{\text{RFBW}}$ (top). + +Unless otherwise stated, the test shall be performed at $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ defined as following: + +- $B_{\text{RFBW}}$ : maximum *Base Station RF Bandwidth* located at the bottom of the supported frequency range in the operating band. +- $M_{\text{RFBW}}$ : maximum *Base Station RF Bandwidth* located in the middle of the supported frequency range in the operating band. $M_{\text{RFBW}}$ may be shifted maximum 100 kHz towards lower frequencies to align carriers with the channel raster. +- $T_{\text{RFBW}}$ : maximum *Base Station RF Bandwidth* located at the top of the supported frequency range in the operating band. + +For the test of certain conducted RF requirements the present specification refers to test procedures defined in the single-RAT specifications [15], [14], [19]. In this case, the interpretation of the RF channels to be tested shall be according to the definitions in the corresponding single-RAT specifications [15], [14], [19]. + +Occupied bandwidth test in this TS is performed with the Aggregated Channel Bandwidth and sub-block bandwidths located at the bottom, middle and top of the supported frequency range in the operating band. These are denoted as $B_{\text{BW Channel CA}}$ (bottom), $M_{\text{BW Channel CA}}$ (middle) and $T_{\text{BW Channel CA}}$ (top) for contiguous spectrum operation. + +Unless otherwise stated, the test for contiguous spectrum operation shall be performed at $B_{\text{BW Channel CA}}$ , $M_{\text{BW Channel CA}}$ and $T_{\text{BW Channel CA}}$ defined as following: + +- $B_{\text{BW Channel CA}}$ : Aggregated Channel Bandwidth located at the bottom of the supported frequency range in each operating band; +- $M_{\text{BW Channel CA}}$ : Aggregated Channel Bandwidth located close in the middle of the supported frequency range in each operating band, with the center frequency of each component carrier aligned to the channel raster; +- $T_{\text{BW Channel CA}}$ : Aggregated Channel Bandwidth located at the top of the supported frequency range in each operating band. + +For a *multi-band TAB connector* capable of dual-band operation, unless otherwise stated, the test shall be performed at $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T_RFBW}}$ defined as following: + +- $B_{\text{RFBW\_T'RFBW}}$ : the *Base Station RF Bandwidths* located at the bottom of the supported frequency range in the lower operating band and at the highest possible simultaneous frequency position, within the maximum *Radio Bandwidth*, in the upper operating band. +- $B'_{\text{RFBW\_T_RFBW}}$ : the *Base Station RF Bandwidths* located at the top of the supported frequency range in the upper operating band and at the lowest possible simultaneous frequency position, within the maximum *Radio Bandwidth*, in the lower operating band. + +NOTE: $B_{\text{RFBW\_T'RFBW}} = B'_{\text{RFBW\_T_RFBW}} = B_{\text{RFBW\_T_RFBW}}$ when the declared maximum *Radio Bandwidth* (see table 4.10-1, D6.16) spans both operating bands. $B_{\text{RFBW\_T_RFBW}}$ means the *Base Station RF Bandwidths* are located at the bottom of the supported frequency range in the lower operating band and at the top of the supported frequency range in the upper operating band. + +When a test is performed by a test laboratory, the position of B, M and T for single carrier, $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ for single band operation, $B_{\text{BW Channel CA}}$ , $M_{\text{BW Channel CA}}$ and $T_{\text{BW Channel CA}}$ for contiguous spectrum operation in each supported operating band, the position of $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T_RFBW}}$ in the supported operating band combinations shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies. + +## 4.12.2 Test models + +a) Unless otherwise stated, carriers used for transmitter tests shall be configured as follows: + +- UTRA FDD carriers shall be configured according to TM1 as defined in TS 25.141 [18], clause 6.1.1.1. +- UTRA TDD carriers shall be configured according to table 6.1A as defined in TS 25.142 [20], clause 6.2.4.1.2. +- E-UTRA carriers shall be configured according to E-TM1 as defined in clause 6.1.1.1 of TS 36.141 [17], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [17]. + +For BC3 CS3 BS testing, E-UTRA carriers shall be configured according to E-TM1\_BC3CS3 defined in Annex E of TS 37.141 [16]. + +- NR carriers shall be configured according to NR-FR1-TM1.1 as defined in clause 4.9.2.2 of TS 38.141-1 [37], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [37]. + +For BC3 BS testing, NR carriers shall be configured according to NR-FR1-TM1\_CS3 defined in Annex E of TS 37.141 [13]. + +b) The configuration of the carriers in test configurations used for testing modulation quality and frequency error shall be as follows: + +- For the case that modulation accuracy is measured for UTRA FDD, the UTRA FDD carriers shall be configured according to the supported TM1 and TM4, as defined in TS 25.141 [18], clause 6.1.1, whilst any remaining carriers from other RAT(s) shall be configured according to bullet a) above. +- If HS-PDSCH transmission using 16QAM is supported, the UTRA FDD carriers shall be configured according to TM4 and TM5, as defined in TS 25.141 [18], clauses 6.1.1. +- For the case that modulation accuracy is measured for UTRA TDD, the UTRA TDD carriers shall be configured according to the supported modulation in table 6.2A, table 6.39A, table 6.39B, table 6.39C, table 6.39D, table 6.40A, table 6.40B, table 6.41A, table 6.41B as defined in TS 25.142 [20], clauses 6.3.4, 6.8.1, 6.8.2 and 6.8.3 whilst any remaining carriers from other RAT(s) shall be configured according to bullet a) above. +- For the case that modulation accuracy is measured for E-UTRA, the E-UTRA carriers shall be configured according to the supported E-TM3.1, E-TM3.2, E-TM3.3 and E-TM2 as defined in clause 6.1.1 of TS 36.141 [17], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [17], whilst any remaining carriers from other RAT(s) shall be configured according to bullet a) above. +- If transmission using 256QAM is supported, the E-UTRA carriers shall be configured according to E-TM 2a and E-TM3.1a as defined in clause 6.1.1 of TS 36.141 [17], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [17]. +- If transmission using 1024QAM is supported, the E-UTRA carriers shall be configured according to E-TM2b and E-TM3.1b as defined in clause 6.1.1 of TS 36.141 [17], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [17]. + +For BC3 CS3 BS testing, E-UTRA carriers shall be configured according to E-TM3.1\_BC3CS3, E-TM3.2\_BC3CS3, E-TM3.3\_BC3CS3 and E-TM2\_BC3CS3 defined in Annex E of TS 37.141 [16]. + +- For the case that modulation accuracy is measured for E-UTRA with sTTI, the E-UTRA carriers shall be configured according to the supported sE-TM3.1-1 and sE-TM2-1 (for subslot TTI), or sE-TM3.1-2 and sE-TM2-2 (for slot TTI) as defined in clause 6.1.1 of TS 36.141 [17], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [17], whilst any remaining carriers from other RAT(s) shall be configured according to bullet a) above. +- For the case that modulation accuracy is measured for NR, the NR carriers shall be configured according to the supported NR-FR1-TM3.1, NR-FR1-TM3.2, NR-FR1-TM3.3 and NR-FR1-TM2 as defined in clause 4.9.2.2 of TS 38.141-1 [37], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [37], whilst any remaining carriers from other RAT(s) shall be configured according to bullet a) above. + +- If transmission using 256QAM is supported, the NR carriers shall be configured according to NR-FR1-TM2a and NR-FR1-TM3.1a as defined in clause 4.9.2.2 of TS 38.141-1 [37], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [37]. +- If transmission using 1024QAM is supported, the NR carriers shall be configured according to NR-FR1-TM2b and NR-FR1-TM3.1b as defined in clause 4.9.2.2 of TS 38.141-1 [37], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [37]. + +For BC3 BS testing, NR carriers shall be configured according to NR-FR1-TM3.1\_BC3CS16/17, NR-FR1-TM3.1a\_BC3CS16/17, NR-FR1-TM3.1b\_BC3CS16/17, NR-FR1-TM3.2\_BC3CS16/17, NR-FR1-TM3.3\_BC3CS16/17, NR-FR1-TM2\_BC3CS16/17, NR-FR1-TM2a\_BC3CS16/17, and NR-FR1-TM2b\_BC3CS16/17 defined in Annex E of TS 37.141 [13]. + +- c) Unless otherwise stated, transmitter carriers used for receiver tests shall be configured as follows: + - UTRA FDD carriers shall be configured according to TM1 as defined in TS 25.141 [18], clause 6.1.1.1. + - UTRA TDD carriers shall be configured according to table 6.1A as defined in TS 25.142 [20], clause 6.2.4.1.2. + - E-UTRA carriers shall be configured according to E-TM1 as defined in clause 6.1.1.1 of TS 36.141 [17], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [17]. For BC3 CS3 BS testing, E-UTRA carriers shall be configured according to E-TM1\_BC3CS3 defined in Annex E of TS 37.141 [16]. + - NR carriers shall be configured according to NR-FR1-TM1.1 as defined in clause 4.9.2.2 of TS 38.141-1 [37], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [37]. + +For BC3 BS testing, NR carriers shall be configured according to NR-FR1-TM1.1\_BC3CS16/17 defined in Annex E of TS 37.141 [16]. + +For the test of certain RF requirements clause 5 refers to the test configurations as defined in the single-RAT specifications. In this case, the transmitter test signals and test models as defined within the referred test specification for the RF requirement shall be used. + +## 4.13 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 clause 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. Required manufacturer declarations may be included here. + +#### X.2 Minimum requirement + +This clause contains the reference to the clause to the 3GPP reference (or core) specification which defines the minimum requirement. For each requirement, there are separate references for MSR and single RAT, where applicable in the core requirement. If the requirement does not apply to a particular RAT, this is explicitly stated here (rather than through a reference). + +#### X.3 Test purpose + +This clause defines the purpose of the test. + +#### X.4 Method of test + +##### X.4.1 General + +In some cases there are alternative test procedures or initial conditions. In such cases, guidance for which initial conditions and test procedures can be applied are stated here. In the case only one test procedure is applicable, that is stated here. Guidance to which TAB connectors are subject to the test is also given here. + +#### X.4.2y First test method + +##### X.4.2y.1 Initial conditions + +This clause defines the initial conditions for each test, including the test environment, the RF channels to be tested and the basic measurement set-up. The test system is assumed to be correctly calibrated as part of the initial conditions. Calibration is not explicitly mentioned. + +##### X.4.2y.2 Procedure + +This clause describes the steps necessary to perform the test and provides further details of the test definition like point of access (e.g. test port), domain (e.g. frequency-span), range, weighting (e.g. bandwidth), and algorithms (e.g. averaging). The procedure may comprise data processing of the measurement result before comparison with the test requirement (e.g. average result from several measurement positions). + +#### X.4.3y Alternative test method (if any) + +If there are alternative test methods, each is described with its initial conditions and procedures. + +### X.5 Test requirement + +This clause defines the pass/fail criteria for the equipment under test, see clause 4.1.3 Interpretation of measurement results. Test requirements for every minimum requirement referred in clause X.2 are listed here. Cases where minimum requirements do not apply need not be mentioned. + +The test requirements may be different depending on the test method applied. A test requirement for each test method applicable to the respective MSR/Single RAT requirement is given in separate clauses where applicable. + +--- + +## 5 Applicability of Requirements + +### 5.1 General + +The present clause defines for each conducted test requirement the set of mandatory test configurations which shall be used for demonstrating conformance for each *TAB connector*. + +Test configurations for *TAB connectors* supporting multiple RAT in the tested operating band are specified in clause 5.2. + +Test configurations for *TAB connectors* declared to support single RAT requirements (see table 4.10-1, D6.13) by either MSR requirements for UTRA only or E-UTRA only or with a single-RAT UTRA requirements or single RAT E-UTRA requirements are specified in clause 5.3. + +Test configurations for *Multi-band TAB connectors* are specified in clause 5.4. + +Requirements apply to *TAB connectors* according to the declared RAT Capability Set (see table 4.10-1, D6.12) within each supported operating band and capability set of the *TAB connector* and the Band Category of the declared operating band (see table 4.10-1, D6.1), as listed in the heading of each table. Some RF requirements listed in the tables may not be mandatory or they may apply only regionally. This is further specified for each requirement in clauses 6 and 7, and in table 4.4-1. + +For a declared RAT Capability Set (see table 4.10-1, D6.12) in tables 5.2-1, 5.3.2-1, 5.3.3-1, 5.3.4-1, 5.4.1-1 or 5.4.2.1 only the requirements listed in the column for that Capability Set apply. Requirements listed under CSA other than the declared CSA(s) need not be tested. In case the BS is declared to support more than one CS, the tests that are common between different supported CSs are not repeated. + +For a *TAB connector* declared to support MSR and to be capable of contiguous spectrum operation only, the test configuration(s) in tables 5.2-1 and 5.3.2-1 denoted by a "C" and entries that refer to single-RAT specifications shall be used for testing. + +For a *TAB connector* that is declared: to support MSR and to be capable of contiguous and non-contiguous spectrum operation (see table 4.10-1, D6.14), where the parameters according to clause 4.10 are identical for contiguous and non-contiguous operation (see table 4.10-1, D6.15), shall use for each declared operating band the test configuration(s) in tables 5.2-1 and 5.3.2-1 denoted by "CNC" and entries that refer to single-RAT specifications shall be used. + +For a *TAB connector* that is declared: to support MSR and to be capable of contiguous and non-contiguous spectrum operation (see table 4.10-1, D6.14), where the parameters according to clause 4.10 are not identical for contiguous and non-contiguous operation (see table 4.10-1, D6.15), shall use for each declared operating band the test configuration(s) in tables 5.2-1 and 5.3.2-1 denoted by "C/NC" and entries that refer to single-RAT specifications shall be used. + +For a MSR capable *multi-band TAB connector* the applicability of the requirement for each operating band is determined by the RAT configuration within that operating band as identified in tables 5.2-1 and 5.3.2-1, unless otherwise stated. The testing of MSR capable *multi-band TAB connectors* shall be according to table 5.4.1-1 as follows: + +- For requirements test denoted by SBT (Single Band Test), the test configuration(s) in tables 5.2-1 and 5.3.2-1 shall be used for each operating band depending on the RAT configuration within that band. +- For requirements test denoted by MBT (Multi-Band Test), the test configuration(s) in table 5.4.1-1 shall be used depending on the Band Category of the declared operating band combination. + +For a single-RAT UTRA only *TAB connector* for each declared operating band clause 5.3.3 defines for each conducted test requirement the set of mandatory test configurations which shall be used for demonstrating conformance. The applicable test configurations are specified in table 5.3.3-1 for each supported RF configuration, which shall be declared according to clause 4.10. The generation and power allocation for each test configuration is defined in clause 4.11.2. + +For a single-RAT E-UTRA only *TAB connector* for each declared operating band clause 5.3.4 defines for each conducted test requirement the set of mandatory test configurations which shall be used for demonstrating conformance. The applicable test configurations are specified in table 5.3.4-1 for each supported RF configuration, which shall be declared according to clause 4.10. The generation and power allocation for each test configuration is defined in clause 4.11.2. + +For a *TAB connector* declared to be capable of single carrier operation only in an operating band (see table 4.10-1, D6.23), a single carrier (SC) shall be used for testing. + +## 5.2 Test configurations for TAB connectors for operating bands where MSR is supported + +**Table 5.2-1: Test configuration applicability to requirements and capability sets for *TAB connectors* supporting MSR operation** + +| TAB connector test case | UTRA + E-UTRA (CSA3) | | | E-UTRA + NR (CSA3A) | | | UTRA + E-UTRA + NR (CSA3B)
BC1, BC2 | +|----------------------------------------------------|----------------------------------------------|----------------------------------------------|--------------|-------------------------------------------|-------------------------------------------|-------------------------------------------|--------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | | +| 6.2 Base Station output power | - | - | - | - | - | - | - | +| 6.2.2 Base Station maximum output power | C: ATC3a
CNC: ATC3a
C/NC: ATC3a, ANTC3 | C: ATC3a
CNC: ATC3a
C/NC: ATC3a, ANTC3 | C: ATC3b | C: ATC6
CNC: ATC6
C/NC: ATC6, ANTC6 | C: ATC6
CNC: ATC6
C/NC: ATC6, ANTC6 | C: ATC6
CNC: ATC6
C/NC: ATC6, ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| Additional regional requirement (only for band 34) | N/A | N/A | (Note 1) | N/A | N/A | (Note 1) | N/A | +| 6.2.3 UTRA FDD primary CPICH power | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Clause 5.3.3 | +| 6.2.3A UTRA FDD secondary CPICH power | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Clause 5.3.3 | +| 6.2.4 UTRA TDD primary CCPCH power | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| 6.2.6 E-UTRA DL RS power | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | + +| TAB connector test case | UTRA + E-UTRA (CSA3) | | | E-UTRA + NR (CSA3A) | | | UTRA + E-UTRA + NR (CSA3B) | +|------------------------------------|-------------------------------------------------|-------------------------------------------------|---------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| | .3.4 | 3.4 | .3.4 | .3.4 | 3.4 | 3.4 | | +| 6.3 Output power dynamics | - | - | - | - | - | - | - | +| E-UTRA | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Clause 5.3.3 | +| UTRA TDD | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| NR | N/A | N/A | N/A | SC | SC | SC | SC | +| 6.4 Transmit ON/OFF power | - | - | - | - | - | - | - | +| 6.4.1 Transmitter OFF power | N/A | N/A | C: ATC3b | N/A | N/A | C: ATC6
CNC: ATC6
C/NC: ATC6,
ANTC6 | N/A | +| 6.4.2 Transmitter transient period | N/A | N/A | C: ATC3b | N/A | N/A | C: ATC6
CNC: ATC6
C/NC: ATC6,
ANTC6 | N/A | +| 6.5 Transmitted signal quality | - | - | - | - | - | - | - | +| 6.5.2 Frequency error | - | - | - | - | - | - | - | +| E-UTRA | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | Same TC as used in subclause 6.5.4 | +| UTRA FDD | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | N/A | N/A | N/A | N/A | Same TC as used in subclause 6.5.4 | +| UTRA TDD | N/A | N/A | Same TC as used in clause 6.5.4 | N/A | N/A | N/A | N/A | +| NR | N/A | N/A | N/A | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | Same TC as used in subclause 6.5.4 | +| 6.5.3 Time alignment error | - | - | - | - | - | - | - | +| E-UTRA | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Clause 5.3.3 | +| UTRA TDD | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| NR | N/A | N/A | N/A | ATC7 | ATC7 | ATC7,
ANTC7 | ATC7 | +| 6.5.4 Modulation quality - EVM | - | - | - | - | - | - | - | +| E-UTRA | C: ATC3a
CNC: ATC3a
C/NC: ATC3a,
ANTC3 | C: ATC3a
CNC: ATC3a
C/NC: ATC3a,
ANTC3 | C: ATC3b | C: ATC6
CNC: ATC6
C/NC: ATC6,
ANTC6 | C: ATC6
CNC: ATC6
C/NC: ATC6,
ANTC6 | C: ATC6
CNC: ATC6
C/NC: ATC6,
ANTC6 | C: ATC8
CNC: ATC8
C/NC: ATC8,
ANTC8 | + +| TAB connector test case | UTRA + E-UTRA (CSA3) | | | E-UTRA + NR (CSA3A) | | | UTRA + E-UTRA + NR (CSA3B) | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------|-------------------------------------------------------|----------------------------------------------------------|-----------------------------------------------------------------------------------------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| | ANTC3 | | | | | | | +| UTRA FDD | C:
ATC3a
CNC:
ATC3a
C/NC:
ATC3a,
ANTC3 | C: ATC3a
CNC:
ATC3a
C/NC:
ATC3a,
ANTC3 | N/A | N/A | N/A | N/A | C:
CNC: ATC8
C/NC: ANTC8,
ATC8 | +| UTRA TDD | N/A | N/A | C:
ATC3b | N/A | N/A | N/A | N/A | +| NR | N/A | N/A | N/A | C: ATC6
CNC:
ATC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ATC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ATC6
C/NC:
ATC6,
ANTC6 | C: ANTC8
CNC:
C/NC: ANTC8,
ANTC8 | +| 6.5.5 Transmit pulse shape filter | Not tested | Not tested | Not tested | Not tested | Not tested | Not tested | Not tested | +| 6.6 Unwanted Emissions | - | - | - | - | - | - | - | +| 6.6.2 Occupied bandwidth | - | - | - | - | - | - | - | +| Minimum requirement | Clause 5
.3.3
Clause 5
.3.4 | Clause 5
.3.3
Clause 5
.3.4 | Clause 5
.3.3
Clause 5
.3.4 | SC
Clause 5
.3.4 | SC
Clause 5
.3.4 | SC
Clause 5
.3.4 | SC
Clause 5.3.3
Clause 5.3.4 | +| 6.6.3 Adjacent Channel Leakage power Ratio | - | - | - | - | - | - | - | +| E-UTRA | C:
ATC2a
CNC:
ANTC2
C/NC:AT
C2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:ATC
2a,
ANTC2 | C:
ATC2a
CNC:
ANTC2
C/NC:A
TC2a,
ANTC2 | C:
ATC2a
CNC:
ANTC2
C/NC:A
TC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:ATC
2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:ATC
2a,
ANTC2 | C: ATC8
CNC: ANTC8
C/NC: ANTC8,
ATC6a | +| UTRA FDD | Clause 5
.3.3 | Clause 5
.3.3 | N/A | N/A | N/A | N/A | C: ATC6a
CNC: ANTC8
C/NC: ANTC8,
ATC6a | +| UTRA TDD | N/A | N/A | Clause 5
.3.3 | N/A | N/A | N/A | N/A | +| NR | N/A | N/A | N/A | C: ATC7
CNC:
ANTC7
C/NC:
ATC7,
ANTC7 | C: ATC7
CNC:
ANTC7
C/NC:
ATC7,
ANTC7 | C: ATC7
CNC:
ANTC7
C/NC:
ATC7,
ANTC7 | C: ATC6a
CNC: ANTC8
C/NC: ANTC8,
ANTC8 | +| Cumulative ACLR | CNC:
ANTC3
C/NC:AN
TC3 | CNC:
ANTC3
C/NC:ANT
C3 | | CNC:
ANTC6
C/NC:A
NTC6 | CNC:
ANTC6
C/NC:ANT
C6 | CNC:
ANTC6
C/NC:ANT
C6 | CNC: ANTC8
C/NC: ANTC8 | +| 6.6.5 Operating band unwanted emission | - | - | - | - | - | - | - | +| General requirement for Band Categories 1 and 3 | Clause 5
.3.3
Clause 5
.3.4 C:
ATC3a
CNC:
ATC3a,
ANTC3
C/NC:
ATC3a,
ANTC3 | N/A | Clause 5
.3.3
Clause 5
.3.4 C:
ATC3b | Clause 5
.3.4
C: ATC6
CNC:
ATC6,
ANTC6
C/NC:
ATC6,
ANTC6
SC:
(Note 2) | N/A | Clause 5
.3.4
C: ATC6
CNC:
ATC6,
ANTC6
C/NC:
ATC6,
ANTC6
SC: (Note 2) | C: ATC8
CNC: ATC8,
ANTC8
C/NC: ,
ANTC8, ATC8
SC: (Note 2) | +| General requirement for Band Category 2 | N/A | Clause 5
.3.3 | N/A | N/A | Clause 5
.3.4 | N/A | C: ATC8
CNC: ANTC8 | + +| TAB connector test case | UTRA + E-UTRA (CSA3) | | | E-UTRA + NR (CSA3A) | | | UTRA + E-UTRA + NR (CSA3B) | +|------------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------|----------------------------------------------------------|------------------------------------------------------------------------------|-----------------------------------------------------|--------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| | | Clause 5.
3.4
C: ATC3a
CNC:
ATC3a,
ANTC3
C/NC:
ATC3a,
ANTC3 | | | C: ATC6
CNC:
ATC6,
ANTC6
C/NC:
ATC6,
ANTC6
SC: (Note 2) | | C/NC, :
ANTC8, ATC8

SC: (Note 2) | +| Additional requirements | (Note 1) | (Note 1) | (Note 1) | (Note 1) | (Note 1) | (Note 1) | (Note 1) | +| 6.6.6 Spurious emission | - | - | - | - | - | - | - | +| (Category A) | C:
ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C: ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C:
ATC3b | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| (Category B) | C:
ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C: ATC3a
CNC:
ANTC3C/
NC:
ATC3a,
ANTC3 | C:
ATC3b | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| Additional requirement for BC2 (Category B) | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| Protection of the BS receiver of own or different BS | C:
ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C: ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C:
ATC3b | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| Additional spurious emissions requirements | C:
ATC3a,
CNC:
ANTC3,
C/NC:
ATC3a,
ANTC3a | C: ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C:
ATC3b | C:
ATC6,
CNC:
ANTC6,
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| Co-location with other Base Stations | C:
ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C: ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C:
ATC3b | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| 6.7 Transmitter intermodulation | - | - | - | - | - | - | - | +| General requirement | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in 6.6 | +| Additional requirement (BC1 and BC2) | CNC:
ANTC3
C/NC:AN
TC3 | Same TC as used in clause 6.6 | N/A | CNC:
ANTC6
C/NC:A
NTC6 | Same TC as used in clause 6.6 | N/A | CNC: ANTC8
C/NC: ANTC8 | +| Additional requirement (BC3) | N/A | N/A | Same TC as used in clause 6 | N/A | N/A | N/A | N/A | + +| TAB connector test case | UTRA + E-UTRA (CSA3) | | | E-UTRA + NR (CSA3A) | | | UTRA + E-UTRA + NR (CSA3B) | +|----------------------------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| 7.2 Reference sensitivity level | - | - | .6 | - | - | - | - | +| E-UTRA requirement | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| UTRA FDD requirement | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Clause 5.3.3 | +| UTRA TDD requirement | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| NR | N/A | N/A | N/A | SC | SC | SC | SC | +| 7.3 Dynamic range | - | - | - | - | - | - | - | +| E-UTRA | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Clause 5.3.3 | +| UTRA TDD | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| NR | N/A | N/A | N/A | SC | SC | SC | SC | +| 7.4 Adjacent channel selectivity and narrowband blocking | - | - | - | - | - | - | - | +| General blocking requirement | C: ATC3a
CNC: ANTC3
C/NC: ATC3a, ANTC3 | C: ATC3a
CNC: ANTC3
C/NC: ATC3a, ANTC3 | C: ATC3b | C: ATC6
CNC: ANTC6
C/NC: ATC6, ANTC6 | C: ATC6
CNC: ANTC6
C/NC: ATC6, ANTC6 | C: ATC6
CNC: ANTC6
C/NC: ATC6, ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| General narrowband blocking requirement | C: ATC3a, ATC4b
CNC: ANTC3, ATC4b
C/NC: ATC3a, ANTC3, ATC4b | C: ATC3a, ATC4b
CNC: ANTC3, ATC4b
C/NC: ATC3a, ANTC3, ATC4b | C: ATC3b, ATC4b | C: ATC6, ATC4b, ATC4d
CNC: ANTC6, ATC4b, ATC4d
C/NC: ATC6, ANTC6, ATC4b, ATC4d | C: ATC6, ATC4b, ATC4d
CNC: ANTC6, ATC4b, ATC4d
C/NC: ATC6, ANTC6, ATC4b, ATC4d | C: ATC6, ATC4b, ATC4d
CNC: ANTC6, ATC4b, ATC4d
C/NC: ATC6, ANTC6, ATC4b, ATC4d | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| Additional BC3 blocking minimum requirement | N/A | N/A | C: ATC3b | N/A | N/A | N/A | N/A | +| 7.5 Blocking | - | - | - | - | - | - | - | +| General requirement | C: ATC3a
CNC: ANTC3
C/NC: ATC3a, ANTC3 | C: ATC3a
CNC: ANTC3
C/NC: ATC3a, ANTC3 | C: ATC3b | C: ATC6
CNC: ANTC6
C/NC: ATC6, ANTC6 | C: ATC6
CNC: ANTC6
C/NC: ATC6, ANTC6 | C: ATC6
CNC: ANTC6
C/NC: ATC6, ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| Co-location requirement | C: ATC3a
CNC: ANTC3
C/NC: ATC3a, ANTC3 | C: ATC3a
CNC: ANTC3
C/NC: ATC3a, ANTC3 | C: ATC3b | C: ATC6
CNC: ANTC6
C/NC: ATC6, ANTC6 | C: ATC6
CNC: ANTC6
C/NC: ATC6, ANTC6 | C: ATC6
CNC: ANTC6
C/NC: ATC6, ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, ATC8 | +| 7.6 Receiver spurious emissions | - | - | - | - | - | - | - | +| General requirement | C: ATC3a
CNC: ANTC3 | C: ATC3a
CNC: ANTC3 | C: ATC3b | C: ATC6
CNC: ANTC6 | C: ATC6
CNC: ANTC6 | C: ATC6
CNC: ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8, | + +| TAB connector test case | UTRA + E-UTRA (CSA3) | | | E-UTRA + NR (CSA3A) | | | UTRA + E-UTRA + NR (CSA3B) | +|------------------------------------------------|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| | ANTC3
C/NC:
ATC3a,
ANTC3 | C/NC:
ATC3a,
ANTC3 | | C/NC:
ATC6,
ANTC6 | C/NC:
ATC6,
ANTC6 | C/NC:
ATC6,
ANTC6 | ATC8 | +| Additional requirement for BC2 (Category B) | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| 7.7 Receiver intermodulation | - | - | - | - | - | - | - | +| General intermodulation requirement | C:
ATC3a
CNC:
ANTC3
C/NC:
ATC3a,
ANTC3 | C: ATC3a
CNC
ANTC3
C/NC:
ATC3a,
ANTC3 | C:
ATC3b | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC6
CNC:
ANTC6
C/NC:
ATC6,
ANTC6 | C: ATC8
CNC: ANTC8
C/NC: ANTC8,
ATC8 | +| General narrowband intermodulation requirement | C:
ATC3a,
ATC4b
CNC:ANT
TC3,
ATC4b
C/NC:
ATC3a,
ANTC3,
ATC4b | C: ATC3a
ATC4b
CNC:ANT
C3,ATC4b
C/NC:
ATC3a,
ANTC3;
ATC4b | C:
ATC3b,
ATC4b | C:
ATC6,
ATC4b,
ATC4d
CNC:AN
TC6,
ATC4b,
ATC4d
C/NC:
ATC6,
ANTC6,
ATC4b,
ATC4d | C: ATC6
ATC4b,
ATC4d
CNC:ANT
C6,ATC4b
, ATC4d
C/NC:
ATC6,
ANTC6;
ATC4b,
ATC4d | C: ATC6,
ATC4b,
ATC4d
CNC:
ANTC6,
ATC4b,
ATC4d
C/NC:
ATC6,
ANTC6,
ATC4b,
ATC4d | C: ATC8
CNC: ANTC8
C/NC: ANTC8,
ATC8 | +| 7.8 In-channel selectivity | Clause 5
.3.4 | Clause 5.
3.4 | Clause 5
.3.4 | - | - | - | - | +| E-UTRA requirement | Clause 5
.3.4 | Clause 5.
3.4 | Clause 5
.3.4 | Clause 5
.3.4 | Clause 5.
3.4 | Clause 5.
3.4 | Clause 5.3.4 | +| NR requirement | N/A | N/A | N/A | SC | SC | SC | SC | + +NOTE 1: Compliance stated by manufacturer declaration. + +NOTE 2: For Operating band unwanted emissions, NR shall also be tested with SC with widest supported channel bandwidth and highest supported sub-carrier spacing. + +## 5.3 Test configurations for multi-carrier capable TAB connector(s) in operating bands where one RAT capability sets are supported + +### 5.3.1 General + +A *TAB connector* may support only one RAT operation in an operating band by fulfilling different sets of requirements. Both UTRA and E-UTRA have two complete sets of requirements that may be fulfilled depending on whether the TAB connector is declared to be MSR or single RAT in the operating band. MSR and single RAT requirements are addressed separately by separate test requirements (and corresponding core requirements). They are also identified by different capability sets as described in clauses 4.11 and 5.2. + +### 5.3.2 TAB connector supporting one RAT only MSR in the operating band + +This clause contains test configuration applicability to requirements and capability sets for *TAB connectors* supporting one RAT only MSR operation operating with multiple carriers (MC). + +**Table 5.3.2-1: Test configuration applicability to requirements and capability sets for TAB connectors supporting one RAT only MSR operation** + +| Capability Set | | UTRA (MC) capable BS (CSA1) | | | E-UTRA (MC) capable BS (CSA2) | | | +|-------------------------|----------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------|---------------------------------|-------------------------------------------------------|-------------------------------------------------------|-------------------------------------------------------| +| TAB connector test case | | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| 6.2 | Base Station output power | - | - | - | - | - | - | +| 6.2.2 | Base Station maximum output power | C: ATC1a
CNC:
ATC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ATC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a
CNC:
ATC2a
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ATC2a
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ATC2a
C/NC:
ATC2a,
ANTC2 | +| | Additional regional requirement (only for band 34) | N/A | N/A | N/A | N/A | N/A | NOTE1 | +| 6.2.3 | UTRA FDD primary CPICH power | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| 6.2.3A | UTRA FDD secondary CPICH power | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| 6.2.4 | UTRA TDD primary CCPCH power | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | +| 6.2.5 | UTRA FDD additional CPICH power for MIMO mode | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| 6.2.6 | E-UTRA DL RS power | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| 6.3 | Output power dynamics | - | - | - | - | - | - | +| 6.3.2 | UTRA Inner loop power control in the downlink | Clause 5.3.3 | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | +| 6.3.3 | Power control dynamic range | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| 6.3.4 | Total power dynamic range | Clause 5.3.3 | Clause 5.3.3 | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| 6.3.5 | IPDL time mask | Clause 5.3.3 | Clause 5.3.3 | N/A | | | | +| 6.4 | Transmit ON/OFF power | - | - | - | - | - | - | +| 6.4.1 | Transmitter OFF power | N/A | N/A | C: ATC1b | N/A | N/A | C: ATC2a
CNC:
ATC2a
C/NC:
ATC2a,
ANTC2 | +| 6.4.2 | Transmitter transient period | N/A | N/A | C: ATC1b | N/A | N/A | C: ATC2a
CNC:
ATC2a
C/NC:
ATC2a,
ANTC2 | +| 6.5 | Transmitted signal quality | - | - | - | - | - | - | +| 6.5.2 | Frequency error | - | - | - | - | - | - | +| | E-UTRA | N/A | N/A | N/A | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | +| | UTRA FDD | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | N/A | N/A | N/A | N/A | +| | UTRA TDD | N/A | N/A | Same TC as used in clause 6.5.1 | N/A | N/A | N/A | +| 6.5.3 | Time alignment error | - | - | - | - | - | - | +| | E-UTRA | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| | UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| | UTRA TDD | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | + +| Capability Set | | UTRA (MC) capable BS (CSA1) | | | E-UTRA (MC) capable BS (CSA2) | | | +|-------------------------|-------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| TAB connector test case | | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| 6.5.4 | Modulation quality - EVM | - | - | - | - | - | - | +| | E-UTRA | N/A | N/A | N/A | C: ATC2a
CNC:
ATC2a
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ATC2a
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ATC2aC/N
C: ATC2a,
ANTC2 | +| | UTRA FDD | C: ATC1a
CNC:
ATC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ATC1a
C/NC:
ATC1a,
ANTC1a | N/A | N/A | N/A | N/A | +| | UTRA TDD | N/A | N/A | C: ATC1b | N/A | N/A | N/A | +| 6.5.5 | Transmit pulse shape filter | Not tested | Not tested | Not tested | Not tested | Not tested | Not tested | +| 6.6 | Unwanted Emissions | - | - | - | - | - | - | +| 6.6.2 | Occupied bandwidth | - | - | - | - | - | - | +| | Minimum requirement | Clause 5.3.3 | Clause 5.3.3 | Clause 5.3.3 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| 6.6.3 | Adjacent Channel Leakage power Ratio | - | - | - | - | - | - | +| | E-UTRA | N/A | N/A | N/A | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| | UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| | UTRA TDD | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | +| | Cumulative ACLR | CNC:
ANTC1a
C/NC:
ANTC1a | CNC:
ANTC1a
C/NC:
ANTC1a | - | CNC:
ANTC2
C/NC:
ANTC2 | CNC:
ANTC2
C/NC:
ANTC2 | CNC:
ANTC2
C/NC:
ANTC2 | +| 6.6.4 | Spectrum emission mask | | | | | | | +| 6.6.5 | Operating band unwanted emission | - | - | - | - | - | - | +| | General requirement for Band Categories 1 and 3 | Clause 5.3.3
C: ATC1a
CNC:
ATC1a,
ANTC1a
C/NC:
ATC1a,
ANTC1a | N/A | Clause 5.3.3
C: ATC1b | Clause 5.3.4
C: ATC2a
CNC:
ATC2a,
ANTC2
C/NC:
ATC2a,
ANTC2 | N/A | Clause 5.3.4
C: ATC2a
CNC:
ATC2a,
ANTC2
C/NC:
ATC2a,
ANTC2 | +| | General requirement for Band Category 2 | N/A | Clause 5.3.3
C: ATC1a
CNC:
ATC1a,
ANTC1a
C/NC:
ATC1a,
ANTC1a | N/A | N/A | Clause 5.3.4
C: ATC2a
CNC:
ATC2a,
ANTC2
C/NC:
ATC2a,
ANTC2 | N/A | +| | Additional requirements | (note) | (note) | (note) | (note) | (note) | (note) | +| 6.6.6 | Spurious emission | - | - | - | - | - | - | +| | (Category A) | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| | (Category B) | C: ATC1a
CNC: | C: ATC1a
CNC: | C: ATC1b | C: ATC2a
CNC: | C: ATC2a
CNC: | C: ATC2a
CNC: | + +| Capability Set | | UTRA (MC) capable BS (CSA1) | | | E-UTRA (MC) capable BS (CSA2) | | | +|-------------------------|------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-------------------------------|------------------------------------------------------------------------|----------------------------------------------------------------------------|----------------------------------------------------------------------------| +| TAB connector test case | | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| | | ANTC1a
C/NC:
ATC1a,
ANTC1a | ANTC1a
C/NC:
ATC1a,
ANTC1a | | ANTC2
C/NC:
ATC2a,
ANTC2 | ANTC2
C/NC:
ATC2a,
ANTC2 | ANTC2
C/NC:
ATC2a,
ANTC2 | +| | Additional requirement for BC2 (Category B) | N/A | N/A | N/A | N/A | N/A | N/A | +| | Protection of the BS receiver of own or different BS | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| | Additional spurious emissions requirements | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| | Co-location with other Base Stations | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2C/N
C: ATC2a,
ANTC2 | +| 6.7 | Transmitter intermodulation | - | - | - | - | - | - | +| | General requirement | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | +| | Additional requirement (BC1 and BC2) | CNC:
ANTC1a
C/NC:ANT
C1a | Same TC as used in 6.6 | N/A | CNC:
ANTC2
C/NC:
ANTC2 | Same TC as used in 6.6 | N/A | +| | Additional requirement (BC3) | N/A | N/A | Same TC as used in clause 6.6 | N/A | N/A | Same TC as used in 6.6 | +| 7.2 | Reference sensitivity level | - | - | - | - | - | - | +| | E-UTRA requirement | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| | UTRA FDD requirement | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| | UTRA TDD requirement | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | +| 7.3 | Dynamic range | - | - | - | - | - | - | +| | E-UTRA | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| | UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| | UTRA TDD | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | +| 7.4 | Adjacent channel selectivity and narrowband blocking | - | - | - | - | - | - | +| | General blocking requirement | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a,
ATC4aCN
C: ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b
ATC4c | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| | General narrowband blocking requirement | C: ATC1a,
ATC4a
CNC:
ANTC1a,
ATC4a
C/NC:
ATC1a,
ANTC1a, | C: ATC1a,
ATC4a
CNC:ANTC
1a, ATC4a
C/NC:
ATC1a,
ANTC1a,
ATC4a | C: ATC1b
ATC4c | C: ATC2a,
ATC4b
CNC:ANTC
2, ATC4b
C/NC:
ATC2a,
ANTC2 | C: ATC2a,
ATC4b
CNC:
ANTC2,
ATC4b
C/NC:
ATC2a,
ANTC2, | C: ATC2a,
ATC4b
CNC:
ANTC2,
ATC4b
C/NC:
ATC2a,
ANTC2, | + +| Capability Set | UTRA (MC) capable BS (CSA1) | | | E-UTRA (MC) capable BS (CSA2) | | | +|------------------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|--------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| TAB connector test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| | ATC4a | | | | ATC4b | ATC4b | +| Additional BC3 blocking minimum requirement | N/A | N/A | C: ATC1b | N/A | N/A | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| 7.5 Blocking | - | - | - | - | - | - | +| General requirement | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| Co-location requirement | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| 7.6 Receiver spurious emissions | - | - | - | - | - | - | +| General requirement | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| Additional requirement for BC2 (Category B) | N/A | N/A | N/A | N/A | N/A | N/A | +| 7.7 Receiver intermodulation | - | - | - | - | - | - | +| General intermodulation requirement | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1a
CNC:
ANTC1a
C/NC:
ATC1a,
ANTC1a | C: ATC1b | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | C: ATC2a
CNC:
ANTC2
C/NC:
ATC2a,
ANTC2 | +| General narrowband intermodulation requirement | C: ATC1a,
ATC4a
CNC:ANTC
1a, ATC4a
C/NC:
ATC1a,
ANTC1a,
ATC4a | C: ATC1a,
ATC4a
CNC:ANTC
1a, ATC4a
C/NC:
ATC1a,
ANTC1a,
ATC4a | C: ATC1b,
ATC4c | C: ATC2a,
ATC4b
CNC:
ANTC2,
ATC4b
C/NC:
ATC2a,
ANTC2,
ATC4b | C: ATC2a,
ATC4b
CNC:
ANTC2,
ATC4b
C/NC:
ATC2a,
ANTC2,
ATC4b | C: ATC2a,
ATC4b
CNC:
ANTC2,
ATC4b
C/NC:
ATC2a,
ANTC2,
ATC4b | +| 7.8 In-channel selectivity | - | - | - | - | - | - | +| E-UTRA requirement | N/A | N/A | N/A | Clause 5.3.
4 | Clause 5.3.
4 | Clause 5.3.
4 | + +NOTE: Compliance stated by manufacturer. + +### 5.3.3 TAB connector supporting Single-RAT UTRA in the operating band + +This clause contains the test configurations for TAB connectors supporting single-RAT UTRA in the operating band. The test configurations apply to *TAB connectors* operating with multiple carriers (MC). + +For a *TAB connector* declared to support multi-carrier operation in contiguous spectrum operation in single band only, the test configurations in the second column of table 5.3.3-1 for FDD, and in the fifth column of table 5.3.3-1 for TDD, shall be used for testing. + +NOTE: The applicability of test configurations for TDD in this clause is only applicable to UTRA TDD 1,28 Mcps option. + +For FDD a *TAB connector* declared to support multi-carrier operation in contiguous and non-contiguous spectrum in single band and where the parameters in the manufacturer's declaration according to clause 4.10 are identical for contiguous (C) and non-contiguous (NC) spectrum operation, the test configurations in the third column of table 5.3.3-1 shall be used for testing. + +For FDD a *TAB connector* declared to support multi-carrier operation in contiguous and non-contiguous spectrum in single band and where the parameters in the manufacturer's declaration according to clause 4.10 are not identical for contiguous and non-contiguous spectrum operation, the test configurations in the fourth column of table 5.3.3-1 shall be used for testing. + +**Table 5.3.3-1: Test configurations for a *TAB connector* supporting single-RAT UTRA operation** + +| TAB connector test case | | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C capable only | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC capable TAB connector (CSA4) C capable only | +|-------------------------|------------------------------------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| 6.2 | Base Station output power | - | - | - | - | +| 6.2.2 | Base Station maximum output power | ATC1a | ATC1a | ATC1a, ANTC1 | ATC1b | +| 6.2.3 | UTRA FDD primary CPICH power | SC | SC | SC | N/A | +| 6.2.3A | UTRA FDD secondary CPICH power | SC | SC | SC | N/A | +| 6.2.4 | UTRA TDD primary CCPCH power | N/A | N/A | N/A | SC | +| 6.3 | Output power dynamics | - | - | - | - | +| 6.3.2 | UTRA Inner loop power control in the downlink | SC | SC | SC | SC | +| 6.3.3 | Power control dynamic range | SC | SC | SC | SC | +| 6.3.4 | Total power dynamic range | SC or ATC1a | SC or ATC1a | SC or ATC1a | N/A | +| 6.3.5 | IPDL time mask | SC | SC | SC | N/A | +| 6.4 | Transmit ON/OFF power | N/A | N/A | N/A | ATC1b | +| 6.5 | Transmitted signal quality | - | - | - | - | +| 6.5.2 | Frequency error | ATC1a | ATC1a | ATC1a, ANTC1 | ATC1b | +| 6.5.3 | Time alignment error | ATC1a | ATC1a | ATC1a, ANTC1 | ATC1b | +| 6.5.4 | Modulation quality - EVM | ATC1a | ATC1a | ATC1a, ANTC1 | ATC1b | +| 6.5.4 | Modulation quality - PCDE | ATC1a | ATC1a | ATC1a, ANTC1 | ATC1b | +| 6.5.4 | Modulation quality - RCDE | ATC1a | ATC1a | ATC1a | ATC1b | +| 6.5.5 | Transmit pulse shape filter | Not tested | Not tested | Not tested | Not tested | +| 6.6 | Unwanted Emissions | - | - | - | - | +| 6.6.2 | Occupied bandwidth | SC | SC | SC | SC | +| 6.6.3 | Adjacent Channel Leakage power Ratio | ATC1a | ANTC1 | ATC1a, ANTC1 | ATC1b | +| | Cumulative ACLR | - | ANTC1 | ANTC1 | N/A | +| 6.6.4 | Spectrum emission mask | ATC1a | ATC1a, ANTC1 | ATC1a, ANTC1 | ATC1b | +| 6.6.6 | Spurious emission | ATC1a | ANTC1 | ATC1a, ANTC1 | ATC1b | +| 6.7 | Transmitter intermodulation | ATC1a | ATC1a, ANTC1 | ATC1a, ANTC1 | ATC1b | +| 7.2 | Reference sensitivity level | SC | SC | SC | SC | +| 7.3 | Dynamic range | SC | SC | SC | SC | +| 7.4 | Adjacent channel selectivity and narrowband blocking | ATC1a | ANTC1 | ATC1a, ANTC1 | ATC1b | +| 7.5 | Blocking | ATC1a | ANTC1 | ATC1a, ANTC1 | ATC1b | +| 7.6 | Receiver spurious emissions | ATC1a | ANTC1 | ATC1a, ANTC1 | ATC1b | +| 7.7 | Receiver intermodulation | ATC1a | ANTC1 | ATC1a, ANTC1 | ATC1b | + +### 5.3.4 TAB connector supporting Single-RAT E-UTRA in the operating band + +This clause contains the test configurations for TAB connectors supporting single-RAT E-UTRA in the operating band. The test configurations apply to *TAB connectors* operating with multiple carriers (MC). + +For a *TAB connector* declared to support multi-carrier and/or CA operation in contiguous spectrum operation in single band only, the test configurations in the second column of table 5.3.4-1 shall be used for testing. + +For a *TAB connector* declared to support multi-carrier and/or CA operation in contiguous and non-contiguous spectrum in single band and where the parameters in the manufacture's declaration according to clause 4.10 are identical for contiguous (C) and non-contiguous (NC) spectrum operation, the test configurations in the third column of table 5.3.4-1 shall be used for testing. + +For a *TAB connector* declared to support multi-carrier and/or CA in contiguous and non-contiguous spectrum in single band and where the parameters in the manufacture's declaration according to clause 4.10 are not identical for contiguous and non-contiguous spectrum operation, the test configurations in the fourth column of table 5.3.4-1 shall be used for testing. + +**Table 5.3.4-1: Test configurations for a *TAB connector* supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band** + +| TAB connector test case | | Single-RAT E-UTRA MC capable TAB connector (CSA5) C capable only | Single-RAT E-UTRA MC capable TAB connector (CSA5) C and NC capable BS with identical parameters (CNC) | Single-RAT E-UTRA MC capable TAB connector (CSA5) C and NC capable BS with different parameters (CNC) | +|--------------------------------|------------------------------------------------------|-------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| 6.2 | Base Station output power | - | - | - | +| 6.2.2 | Base Station maximum output power | ATC2a | ATC2a | ATC2a, ANTC2 | +| 6.2.6 | E-UTRA DL RS power | SC | SC | SC | +| 6.3 | Output power dynamics | - | - | - | +| 6.3.4 | Total power dynamic range | SC | SC | SC | +| 6.3.6 | RE Power control dynamic range | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| 6.4 | Transmit ON/OFF power | ATC2a | ATC2a | ATC2a, ANTC2 | +| 6.5 | Transmitted signal quality | - | - | - | +| 6.5.2 | Frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| 6.5.3 | Time alignment error | ATC2a | ATC2a | ATC2a, ANTC2 | +| 6.5.4 | Modulation quality - EVM | ATC2a | ATC2a | ATC2a, ANTC2 | +| 6.5.5 | Transmit pulse shape filter | Not Tested | Not Tested | Not Tested | +| 6.6 | Unwanted Emissions | - | - | - | +| 6.6.2 | Occupied bandwidth | SC, ATC2b (Note) | SC, ATC2b (Note) | SC, ATC2b (Note) | +| 6.6.3 | Adjacent Channel Leakage power Ratio | ATC2a | ANTC2 | ATC2a, ANTC2 | +| 6.6.3 | Cumulative ACLR | - | ANTC2 | ANTC2 | +| 6.6.5 | Operating band unwanted emission | ATC2a | ATC2a, ANTC2 | ATC2a, ANTC2 | +| 6.6.6 | Spurious emission | ATC2a | ANTC2 | ATC2a, ANTC2 | +| 6.7 | Transmitter intermodulation | ATC2a | Same TC as used in 6.6 | Same TC as used in 6.6 | +| 7.2 | Reference sensitivity level | SC | SC | SC | +| 7.3 | Dynamic range | SC | SC | SC | +| 7.4 | Adjacent channel selectivity and narrowband blocking | ATC2a | ANTC2 | ATC2a, ANTC2 | +| 7.5 | Blocking | ATC2a | ANTC2 | ATC2a, ANTC2 | +| 7.6 | Receiver spurious emissions | ATC2a | ANTC2 | ATC2a, ANTC2 | +| 7.7 | Receiver intermodulation | ATC2a | ANTC2 | ATC2a, ANTC2 | +| 7.8 | In-channel selectivity | SC | SC | SC | + +NOTE: ATC2b is only applicable when contiguous CA is supported. + +## 5.4 Test configurations for *Multi-band TAB connectors* + +### 5.4.1 Multi-band TAB connector supporting MSR operation + +Table 5.4.1-1: Test configuration for *multi-band TAB connectors* supporting MSR operation + +| TAB connector test case | | Test for Multi-Band TAB connector
CSA1, CSA2, CSA3,
CSA3A | Test configuration for MBT | | +|-------------------------|----------------------------------------------------|------------------------------------------------------------------------|----------------------------|-------| +| | | | BC1/BC2 | BC3 | +| 6.2 | Base Station output power | - | - | - | +| 6.2.2 | Base Station maximum output power | SBT, MBT | ATC5a | ATC5a | +| | Additional regional requirement (only for band 34) | Compliance by declaration | N/A | - | +| 6.2.3 | UTRA FDD primary CPICH power | SBT | - | - | +| 6.2.3A | UTRA FDD secondary CPICH power | | | | +| 6.2.4 | UTRA TDD primary CCPCH power | SBT | - | - | +| 6.2.5 | UTRA FDD additional CPICH power for MIMO mode | | | | +| 6.2.6 | E-UTRA DL RS power | E-UTRA for DL RS power | SBT | - | +| 6.3 | Output power dynamics | - | - | - | +| 6.3.2 | UTRA Inner loop power control in the downlink | SBT | - | - | +| 6.3.3 | Power control dynamic range | SBT | - | - | +| 6.3.4 | Total power dynamic range | SBT | - | N/A | +| 6.3.5 | IPDL time mask | SBT | - | N/A | +| 6.3.6 | RE Power control dynamic range | SBT | - | N/A | +| 6.4 | Transmit ON/OFF power | - | - | - | +| 6.4.1 | Transmitter OFF power | MBT, SBT (note 3) | N/A | ATC5a | +| 6.4.2 | Transmitter transient period | MBT, SBT (note 3) | N/A | ATC5a | +| 6.5 | Transmitted signal quality | - | - | - | +| 6.5.2 | Frequency error | - | - | - | +| | E-UTRA | SBT, MBT | ATC5a | ATC5a | +| | UTRA FDD | SBT, MBT | ATC5a | N/A | +| | UTRA TDD | SBT, MBT | N/A | ATC5a | +| | NR | SBT, MBT | ATC5a | ATC5a | +| 6.5.3 | Time alignment error | - | - | - | +| | E-UTRA | SBT, MBT (note 1) | ATC5b | ATC5b | +| | UTRA FDD | SBT, MBT (note 1) | ATC5b | N/A | +| | UTRA TDD | SBT | N/A | - | +| | NR | SBT, MBT (note 1) | ATC5b | ATC5b | +| 6.5.4 | Modulation quality - EVM | - | - | - | +| | E-UTRA | SBT, MBT | ATC5a | ATC5a | +| | UTRA FDD | SBT, MBT | ATC5a | N/A | +| | UTRA TDD | SBT, MBT | N/A | ATC5a | +| | NR | SBT, MBT | ATC5a | ATC5a | +| 6.5.5 | Transmit pulse shape filter | Not tested | - | - | +| 6.6 | Unwanted Emissions | - | - | - | +| 6.6.2 | Occupied bandwidth | - | - | - | +| | Minimum requirement | SBT | - | - | +| 6.6.3 | Adjacent Channel Leakage power Ratio | - | - | - | +| | E-UTRA | SBT, MBT (note 2) | ATC5b | ATC5b | +| | UTRA FDD | SBT, MBT (note 2) | ATC5b | N/A | +| | UTRA TDD | SBT, MBT (note 2) | N/A | ATC5b | +| | Cumulative ACLR | SBT, MBT (note 2) | ATC5b | ATC5b | +| | NR | SBT, MBT (note 2) | ATC5b | ATC5b | +| 6.6.4 | Spectrum emission mask | - | - | - | +| 6.6.5 | Operating band unwanted emission | - | - | - | +| | General requirement for Band Categories 1 and 3 | SBT, MBT | ATC5b | ATC5b | +| | General requirement for Band Category 2 | SBT, MBT | ATC5b | N/A | +| | Additional requirements | SBT, MBT | - | - | +| 6.6.6 | Spurious emission | - | - | - | +| | (Category A) | SBT, MBT | ATC5b | ATC5b | +| | (Category B) | SBT, MBT | ATC5b | ATC5b | +| | Additional requirement for BC2 (Category B) | SBT, MBT | ATC5b | ATC5b | +| | Protection of the BS receiver of own or different | SBT, MBT | ATC5b | ATC5b | + +| TAB connector test case | Test for Multi-Band TAB connector
CSA1, CSA2, CSA3, CSA3A | Test configuration for MBT | | +|----------------------------------------------------------|---------------------------------------------------------------------|----------------------------|-------| +| | | BC1/BC2 | BC3 | +| BS | | | | +| Additional spurious emissions requirements | SBT, MBT | ATC5b | ATC5b | +| Co-location with other Base Stations | - | - | - | +| 6.7 Transmitter intermodulation | - | - | - | +| General requirement | SBT | - | - | +| Additional requirement (BC1 and BC2) | SBT | - | N/A | +| Additional requirement (BC3) | SBT | N/A | - | +| 7.2 Reference sensitivity level | - | - | - | +| E-UTRA requirement | SBT | - | - | +| UTRA FDD requirement | SBT | - | - | +| UTRA TDD requirement | SBT | - | - | +| NR | SBT | - | - | +| 7.3 Dynamic range | - | - | - | +| E-UTRA | SBT | - | - | +| UTRA FDD | SBT | - | - | +| UTRA TDD | SBT | - | - | +| NR | SBT | - | - | +| 7.4 Adjacent channel selectivity and narrowband blocking | - | - | - | +| General blocking requirement | MBT, SBT (note 3) | ATC5b | ATC5b | +| General narrowband blocking requirement | MBT, SBT (note 3) | ATC5b | ATC5b | +| Additional BC3 blocking minimum requirement | MBT, SBT (note 3) | N/A | ATC5b | +| 7.5 Blocking | - | - | - | +| General requirement | MBT, SBT (note 3) | ATC5b | ATC5b | +| Co-location requirement | MBT, SBT (note 3) | ATC5b | ATC5b | +| 7.6 Receiver spurious emissions | - | - | - | +| General requirement | SBT, MBT | ATC5b | ATC5b | +| Additional requirement for BC2 (Category B) | - | - | - | +| 7.7 Receiver intermodulation | - | - | - | +| General intermodulation requirement | MBT, SBT (note 3) | ATC5b | ATC5b | +| General narrowband intermodulation requirement | MBT, SBT (note 3) | ATC5b | ATC5b | +| 7.8 In-channel selectivity | - | - | - | +| E-UTRA requirement | SBT | - | - | +| NR requirement | SBT | - | - | + +NOTE 1: MBT is only applicable when DB-DC-HSDPA/inter-band CA is supported. +NOTE 2: For ACLR, MBT shall be applied for the Inter RF bandwidth gap only. +NOTE 3: SBT is only applicable if different Capability Sets are declared for single-band and multi-band operation. + +## 5.4.2 Multi-band TAB connector supporting Single-RAT only + +For a *multi-band TAB connector* supporting single-RAT only in the operational band, the test configurations in table 5.4.2-1, shall be used for testing. + +**Table 5.4.2-1: Test configuration for *multi-band TAB connectors* supporting Single-RAT only** + +| TAB connector test case | UTRA FDD CSA4 | UTRA TDD CSA4 | E-UTRA Test CSA5 | +|-----------------------------------------------------|----------------------------|-----------------------|-----------------------------| +| 6.2 Base Station output power | - | - | - | +| 6.2.2 Base Station maximum output power | ATC1a/ANTC1 (note 1) ATC5a | ATC1b (note 3), ATC5a | ATC2a/ANTC2 (note 5), ATC5a | +| 6.2.3 UTRA FDD primary CPICH power | SC | N/A | N/A | +| 6.2.3A UTRA FDD secondary CPICH power | SC | N/A | N/A | +| 6.2.4 UTRA TDD primary CCPCH power | N/A | SC | N/A | +| 6.2.5 UTRA FDD additional CPICH power for MIMO mode | SC | N/A | N/A | +| 6.2.6 E-UTRA DL RS power | N/A | N/A | SC | +| 6.3 Output power dynamics | - | - | - | +| 6.3.2 UTRA Inner loop power control in the downlink | SC | SC | N/A | +| 6.3.3 Power control dynamic range | SC | SC | SC | +| 6.3.4 Total power dynamic range | SC or ATC1a | N/A | SC | +| 6.3.5 IPDL time mask | SC | N/A | N/A | + +| TAB connector test case | UTRA FDD CSA4 | UTRA TDD CSA4 | E-UTRA Test CSA5 | +|----------------------------------------------------------|-------------------------------------|--------------------------------|----------------------------------------| +| 6.3.6 RE Power control dynamic range | N/A | N/A | Tested with Error Vector Magnitude | +| 6.4 Transmit ON/OFF power | - | - | - | +| 6.4.1 Transmitter OFF power | N/A | ATC5a | ATC5a (only applied for E-UTRA TDD BS) | +| 6.4.2 Transmitter transient period | N/A | SC | SC | +| 6.5 Transmitted signal quality | - | - | - | +| 6.5.2 Frequency error | Tested with EVM | ATC1b (note 3), ATC5a | Tested with Error Vector Magnitude | +| 6.5.3 Time alignment error | ATC1a/ANTC1 (note 1) ATC5b | ATC1b (note 3) | ATC2a/ANTC2 (note 5), ATC5b (note 6) | +| 6.5.4 Modulation quality - EVM | ATC1a/ANTC1 (note 1), ATC5a | ATC1b (note 3), ATC5a | ATC2a/ANTC2 (note 5), ATC5a | +| 6.5.4 Modulation quality - PCDE | ATC1a/ANTC1 (note 1) | ATC1b (note 3), ATC5a | N/A | +| 6.5.4 Modulation quality - RCDE | AUTC1 | ATC1b (note 3), ATC5a | N/A | +| 6.5.5 Transmit pulse shape filter | not tested | not tested | not tested | +| 6.6 Unwanted Emissions | - | - | - | +| 6.6.2 Occupied bandwidth | SC | SC | SC, ATC2b (note 7) | +| 6.6.3 Adjacent Channel Leakage power Ratio | ATC1a/ANTC1 (note 1) ATC5b (note 2) | ATC1b (note 3), ATC5a (note 4) | ATC2a/ANTC2 (note 5), ATC5b (note 8) | +| 6.6.4 Spectrum emission mask | ATC1a/ANTC1 (note 1) ATC5b | ATC1b (note 3), ATC5a | N/A | +| 6.6.5 Operating band unwanted emission | N/A | N/A | ATC2a/ANTC2 (note 5), ATC5b | +| 6.6.6 Spurious emission | ATC1a/ANTC1 (note 1) ATC5b | ATC1b (note 3), ATC5a | ATC2a/ANTC2 (note 5), ATC5b | +| 6.7 Transmitter intermodulation | ATC1a/ANTC1 (note 1) | ATC1b (note 3) | ATC2a/ANTC2 (note 5) | +| 7.2 Reference sensitivity level | SC | SC | SC | +| 7.3 Dynamic range | SC | SC | SC | +| 7.4 Adjacent channel selectivity and narrowband blocking | ATC5b | ATC5a | ATC5b | +| 7.5 Blocking | ATC5b | ATC5a | ATC5b | +| 7.6 Receiver spurious emissions | ATC1a/ANTC1 (note 1) ATC5b | ATC1b (note 3), ATC5a | ATC2a/ANTC2 (note 5), ATC5b | +| 7.7 Receiver intermodulation | ATC5b | ATC5a | ATC5b | +| 7.8 In-channel selectivity | N/A | N/A | SC | + +NOTE 1: ATC1a and/or ANTC1 shall be applied in each supported operating band according to table 5.3.3-1. + +NOTE 2: ATC5b may be applied for *Inter RF Bandwidth gap* only. + +NOTE 3: ATC1b shall be applied in each supported operating band according to table 5.3.3-1. + +NOTE 4: ATC5a may be applied for *Inter RF bandwidth gap* only. + +NOTE 5: ATC2 and/or ANTC2 shall be applied in each supported operating band according to table 5.3.4-1. + +NOTE 6: ATC5b is only applicable when inter-band CA is supported. + +NOTE 7: ATC2b is only applicable when contiguous CA is supported. + +NOTE 8: ATC5b may be applied for *Inter RF bandwidth gap* only. + +## 6 Conducted transmitter characteristics + +### 6.1 General + +General test conditions for transmitter tests are given in clause 4, including interpretation of measurement results and configurations for testing. BS configurations for the tests are defined in clause 4.8. + +If a number of *TAB connectors* have been declared equivalent (see table 4.10-1, D6.70), only a representative one is necessary to be tested to demonstrate conformance. + +In clause 6.6.3.1, if representative *TAB connectors* are used then per connector criteria (i.e. option 2) shall be applied. + +The manufacturer shall declare the minimum number of supported geographical cells (i.e. geographical areas). The minimum number of supported geographical cells ( $N_{\text{cells}}$ ) relates to the AAS BS setting with the minimum amount of cell splitting supported with transmission on all *TAB connectors* supporting the operating band. The manufacturer shall also declare *TAB connector TX min cell groups*. Every *TAB connector* supporting transmission in an operating band shall map to one *TAB connector TX min cell group* supporting the same operating band. The mapping of *TAB connectors* to cells is implementation dependent. + +The number of *active transmitter units* that are considered when calculating the emissions limit ( $N_{\text{TXU, counted}}$ ) for an AAS BS is calculated as follows: + +$N_{\text{TXU, counted}} = \min(N_{\text{TXU, active}}, 8 \cdot N_{\text{cells}})$ for E-UTRA single RAT AAS BS and MSR AAS BS (except UTRA only MSR AAS BS); and + +$N_{\text{TXU, counted}} = \min(N_{\text{TXU, active}}, 4 \cdot N_{\text{cells}})$ for UTRA single RAT AAS BS and UTRA only MSR AAS BS + +Further: + +$$N_{\text{TXU, counted per cell}} = N_{\text{TXU, counted}} / N_{\text{cells}}$$ + +$N_{\text{TXU, counted per cell}}$ is used for scaling the *basic limits* as described in clause 6.6. + +NOTE: $N_{\text{TXU, active}}$ depends on the actual number of *active transmitter units* and is independent to the declaration of $N_{\text{cells}}$ . + +Any transmitter test requirement specified for Band 46 operation in TS 36.104 [4] for E-UTRA, or in TS 37.104 [5] for E-UTRA in MSR operation, and referred in clause 6, is not applicable for AAS BS. + +Any transmitter test requirement specified for NB-IoT in-band, NB-IoT guard band, or standalone NB-IoT operation in TS 36.141 [14] for E-UTRA with NB-IoT (in-band or guard band) or for standalone NB-IoT, or in TS 37.141 [13] for E-UTRA with NB-IoT or standalone NB-IoT in *MSR operation*, and referred in clause 6, is not applicable for AAS BS. + +### 6.2 Base station output power + +#### 6.2.1 General + +The configured carrier power is the target maximum power for a specific carrier for the operating mode set in the BS within the limits given by the manufacturer's declaration. + +#### 6.2.2 Maximum output power + +##### 6.2.2.1 Definition and applicability + +The rated carrier output power of the *AAS BS* shall be as specified in table 6.2.2.1-1. + +**Table 6.2.2.1-1: AAS Base Station rated output power limits for BS classes** + +| AAS BS class | P Rated,c,sys | P Rated,c,TABC | +|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|---------------------------| +| Wide Area BS | (note) | (note) | +| Medium Range BS | ≤ 38 dBm +10log(N TXU,counted ) | ≤ 38 dBm | +| Local Area BS | ≤ 24 dBm +10log(N TXU,counted ) | ≤ 24 dBm | +| NOTE: There is no upper limit for the P Rated,c,sys or P Rated,c,TABC of the Wide Area Base Station. | | | + +The output power limit for the respective BS classes in table 6.2.2.1-1 shall be compared to the rated output power and the declared BS class. It is not subject to testing. + +The requirement in clause 6.2.2.2 applies per *TAB connector*. + +## 6.2.2.2 Minimum Requirement + +The minimum requirement is in TS 37.105 [8], clause 6.2.2.2. + +## 6.2.2.3 Test Purpose + +The test purpose is to verify the accuracy of the *maximum carrier output power per TAB connector* (Pmax,c,TABC) across the frequency range and under normal and extreme conditions for all *TAB connectors* in the AAS BS. + +## 6.2.2.4 Method of test + +### 6.2.2.4.1 Initial conditions + +Test environment: + +- normal; see clause B.2. +- extreme; see clauses B.3 and B.5. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1 + +*Base Station RF Bandwidth* positions to be tested: + +- BRFBW, MRFBW and TRFBW for *single band TAB connector(s)*, see clause 4.12.1; BRFBW\_TRFBW and B'RFBW\_TRFBW for *multi-band TAB connector(s)*, see clause 4.12.1. + +Under extreme test environment, it is sufficient to test on one RF channel or one *Base Station RF bandwidth* position, and with one applicable test configuration defined in clauses 4.11 and 5. Testing shall be performed under extreme power supply conditions, as defined in Annex B.5. + +NOTE: Tests under extreme power supply conditions also test extreme temperatures. + +### 6.2.2.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect the power measuring equipment to the *TAB connector(s)* as shown in annex clause D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) Set each *TAB connector* to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. For single carrier set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* (PRated,c,TABC). +- 3) Measure the mean power for each carrier at each *TAB connector*. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 6.2.2.5 Test Requirements + +In normal conditions, the measurement result in step 3 of clause 6.2.2.4.3 shall be: + +- within +2.7 dB and -2.7 dB of the manufacturer's *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ) for carrier frequency $f \leq 3.0$ GHz. +- within +3.0 dB and -3.0 dB of the manufacturer's *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ) for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +In extreme conditions, measurement result in step 3 of clause 6.2.2.4.3 shall be: + +- within +3.2 dB and -3.2 dB of the manufacturer's *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ) for carrier frequency $f \leq 3.0$ GHz. +- within +3.5 dB and -3.5 dB of the manufacturer's *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ) for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +## 6.2.3 UTRA FDD primary CPICH power + +### 6.2.3.1 Definition and applicability + +This requirement applies to the *TAB connector* group(s) transmitting primary CPICH. + +Primary CPICH (P-CPICH) power is the code domain power of the Primary Common Pilot Channel summed over the *TAB connectors* transmitting the P-CPICH for a cell. P-CPICH power is indicated on the BCH. + +NOTE 1: A *TAB connector* group may comprise all *TAB connectors*. + +NOTE 2: A *TAB connector* may be mapped to several groups. + +NOTE 3: The manufacturer declares the *TAB connector* mapping to the P-CPICH transmission group(s) as specified in clause 4.10. + +### 6.2.3.2 Minimum requirement + +The minimum requirement for UTRA FDD operation is in TS 37.105 [8], clause 6.2.3. + +There is no P-CPICH power requirement for UTRA TDD 1,28 Mcps option operation. + +There is no P-CPICH power requirement for E-UTRA operation. + +There is no P-CPICH power requirement for NR operation. + +### 6.2.3.3 Test purpose + +The test purpose is to verify that the UTRA FDD primary CPICH power is within the limits specified by the minimum requirement. + +### 6.2.3.4 Method of test + +#### 6.2.3.4.1 Initial conditions + +Test environment: + +- normal; see annex B. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1. + +Disable inner loop power control. + +Set the TAB connectors in the P-CPICH transmission group (see table 4.10-1, D6.45) to output a signal in accordance to TM2, in TS 25.141 [18], clause 6.1.1.2. + +#### 6.2.3.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors* in the *TAB connector* group(s) transmitting primary CPICH. *TAB connectors* may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to code domain analyser as shown in annex clause D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) Set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). Measure the P-CPICH power in one timeslot on each of the *TAB connector(s)* transmitting the P-CPICH according to annex E in TS 25.141 [18]. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.2.3.5 Test requirements + +For UTRA FDD the test requirement for CPICH power is: + +Either: + +The sum of the measured P-CPICH code domain power on each of the *TAB connectors* transmitting the P-CPICH shall be: + +Within $\pm 2.9$ dB of the configured absolute value for carrier frequency $f \leq 3.0$ GHz. + +Within $\pm 3.2$ dB of the configured absolute value for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +Or + +The measured P-CPICH code domain power on each of the *TAB connectors* transmitting the P-CPICH shall be: + +Within $\pm 2.9$ dB of the configured absolute value for carrier frequency $f \leq 3.0$ GHz. + +Within $\pm 3.2$ dB of the configured absolute value for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.2.4 UTRA TDD primary CCPCH power + +#### 6.2.4.1 Definition and applicability + +This requirement applies to the *TAB connector* group(s) transmitting primary CCPCH. It comprises primary CCPCH (PCCPCH) absolute power accuracy, and differential accuracy. + +Primary CCPCH power is the *code domain power* of the primary common control physical channel averaged over the transmit timeslot and summed over the *TAB connectors* transmitting the PCCPCH for a cell. Primary CCPCH power is signalled over the BCH. + +The differential accuracy of the Primary CCPCH power is the relative transmitted power accuracy of PCCPCH in consecutive frames when the nominal PCCPCH power is not changed. + +NOTE 1: A *TAB connector* group may comprise all *TAB connectors*. + +NOTE 2: A *TAB connector* may be mapped to several groups. + +NOTE 3: The manufacturer declares the *TAB connector* mapping to the PCCPCH transmission group(s). See clause 4.10. + +#### 6.2.4.2 Minimum requirement + +The minimum requirement for UTRA TDD 1,28 Mcps option operation is in TS 37.105 [8], clause 6.2.4. + +There is no PCCPCH power requirement for UTRA FDD operation. + +There is no PCCPCH power requirement for E-UTRA operation. + +There is no PCCPCH power requirement for NR operation. + +#### 6.2.4.3 Test purpose + +The test purpose is to verify that the UTRA TDD primary CCPCH power is within the limits specified by the minimum requirement. + +#### 6.2.4.4 Method of test + +##### 6.2.4.4.1 Initial conditions + +Test environment: + +- normal; see annex B. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1 + +Set the *TAB connectors* in the PCCPCH transmission group (see table 4.10-1, D6.47) to output a signal in accordance to table 6.2.4.4.1-1. + +**Table 6.2.4.4.1-1: Parameters of the BS transmitted signal for Primary CCPCH power testing 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 carrying PCCPCH | TS 0 | +| Relative power of PCCPCH | 1/2 of BS output power | +| Data content of DPCH | real life (sufficient irregular) | + +##### 6.2.4.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors* in the *TAB connector* group(s) transmitting primary CCPCH. *TAB connectors* may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +The requirement has both an absolute accuracy requirement and a differential accuracy requirement which are measured at the same time. + +- 1) Connect *TAB connector* to code domain analyser as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. + +- 2) Set the TAB connector to transmit at manufacturers declared rated carrier output power per TAB connector ( $P_{\text{Rated,c,TABC}}$ ). +- 3) Measure the CCPCH power in one timeslot on each of the TAB connector(s) transmitting the PCCPCH according to annex E in TS 25.142 [20]. +- 4) Measure the PCCPCH code domain power in TS 0 of consecutive frames by applying the global in-channel Tx test method described in annex E in TS 25.142 [20]. +- 5) Calculate the differential accuracy of the Primary CCPCH power by taking the difference between the PCCPCH power measurement results of consecutive frames. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For multi-band TAB connectors and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.2.4.5 Test requirements + +For UTRA TDD 1,28 Mcps option the test requirement for PCCPCH power is: + +Either: + +The sum of the measured PCCPCH code domain power on each of the *TAB connectors* transmitting the PCCPCH shall be within the limits defined in table 6.2.4.5-1. + +Or + +The measured PCCPCH code domain power on each of the *TAB connectors* transmitting the PCCPCH shall be within the tolerance indicated in table 6.2.4.5-1. + +**Table 6.2.4.5-1: Test Requirements for errors between Primary CCPCH power and the broadcast value** + +| Output power in slot, dB | PCCPCH power tolerance | +|---------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| $P_{\text{Rated,t.group}} - 3 < P_{\text{out}} \leq P_{\text{Rated,t.group}} + 2$ | $\pm 3.3$ dB | +| $P_{\text{Rated,t.group}} - 6 < P_{\text{out}} \leq P_{\text{Rated,t.group}} - 3$ | $\pm 4.3$ dB | +| $P_{\text{Rated,t.group}} - 13 < P_{\text{out}} \leq P_{\text{Rated,t.group}} - 6$ | $\pm 5.8$ dB | +| NOTE: $P_{\text{Rated,t.group}}$ is the power sum of $P_{\text{Rated,t,TABC}}$ of all the TAB connectors in the group transmitting PCCPCH. | | + +The differential accuracy of the Primary CCPCH power, shall be within $\pm 0.6$ dB. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.2.5 UTRA FDD additional CPICH power for MIMO mode + +##### 6.2.5.1 Definition and applicability + +This clause includes requirements on secondary CPICH power level, for two and four *TAB connector* groups, as well as Demodulation CPICH requirements. The requirements apply to all *TAB connector* groups associated with UTRA FDD MIMO transmission as "antenna 2", "antenna 3" or "antenna 4" in the *AAS BS*. + +The concept of "antenna 2", "antenna 3" and "antenna 4" is described in TS 25.104 [2]. The group(s) of *TAB connectors* mapped to P-CPICH transmission (see table 4.10-1 D6.45) represents "antenna 1". + +NOTE 1: The manufacturer declares the mapping of *TAB connectors* to "antenna 1", "antenna 2", "antenna 3" and "antenna 4" (as defined in TS 25.331 [16]) where applicable for AAS BS capable of UTRA FDD operation. The required declarations are specified clause 4.10. + +For UTRA FDD *AAS BS* operating only "antenna 1" and "antenna 2", the secondary CPICH (S-CPICH) power is the *code domain power* of the Secondary Common Pilot Channel. S-CPICH power is equal to the (dB) sum of the P-CPICH power and the power offset, which are signalled to the UE. The power offset is signalled in the IE "Power Offset for S-CPICH for MIMO", for MIMO mode as defined in clause 10.3.6.41b in TS 25.331 [16]. + +When the UE supports MIMO mode with four BS transmit antennas, the power offset of S-CPICH on antenna 2 is signalled in the IE "Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna2" as defined in clause 10.3.6.143 in TS 25.331 [16]. The power offset of S-CPICH on antenna 3 and 4 is signalled in the IE "Common Power Offset for S-CPICH for MIMO mode with four transmit antennas on antenna 3 and 4", as defined in clause 10.3.6.143 in TS 25.331 [16]. + +Demodulation CPICH (D-CPICH) power is the *code domain power* of the Demodulation Common Pilot Channel. D-CPICH power is equal to the (dB) sum of the P-CPICH power and the power offset, which are signalled to the UE. The power offset of D-CPICH on antenna 3 and 4 is signalled in the IE "Common Power Offset for D-CPICH for MIMO mode with four transmit antennas on antenna 3 and 4", as defined in clause 10.3.6.143 in TS 25.331 [16]. + +NOTE 2: The accuracy level of the power offset for S-CPICH may affect both MIMO HS-DSCH demodulation and CQI reporting performance. + +NOTE 3: The accuracy level of the power offset for D-CPICH transmitted on antennas 3 and 4 may affect both MIMO HS-DSCH demodulation and CQI reporting performance. + +NOTE 4: At high geometry level PDSCH performance may be affected if D-CPICH is not scheduled. + +NOTE 5: A *TAB connector* group may comprise all *TAB connectors*. + +NOTE 6: A *TAB connector* may be mapped to several groups. + +## 6.2.5.2 Minimum requirement + +The minimum requirement for UTRA FDD operation is in TS 37.105 [8], clause 6.2.5.3. + +There is no CPICH power requirement for UTRA TDD 1,28 Mcps option operation. + +There is no CPICH power requirement for E-UTRA operation. + +There is no CPICH power requirement for NR operation. + +## 6.2.5.3 Test purpose + +The test purpose is to verify that the UTRA FDD CPICH power for MIMO mode is within the limits specified by the minimum requirement. + +## 6.2.5.4 Method of test + +### 6.2.5.4.1 Initial conditions + +Test environment: + +- normal; see annex B. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1. + +Disable inner loop power control. + +Set the *TAB connectors* in the P-CPICH transmission group (see table 4.10-1, D6.45) and the *TAB connectors* in the S-CPICH transmission groups (see table 4.10-1, D6.49), to output a signal in accordance to TM2, in TS 25.141 [18], clause 6.1.1.2. + +NOTE: Although the S-CPICH transmission groups are referred to as S-CPICH as the same TM2 is used for the test, the signal being measured on the S-CPICH transmission groups is actually a P-CPICH signal. + +#### 6.2.5.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors* in the P-CPICH transmission group transmitting primary CPICH and the *TAB connectors* in the S-CPICH transmission groups. *TAB connectors* may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to code domain analyser as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) Set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). +- 3) Measure the P-CPICH power in one timeslot on each of the *TAB connector(s)* in the P-CPICH transmission groups according to annex E in TS 25.141 [18]. +- 4) Measure the P-CPICH power in the same timeslot as step 2 on each of the *TAB connector(s)* in each of the S-CPICH transmission groups according to annex E in TS 25.141 [18]. Depending on the MIMO support (see table 4.10-1, D6.49), for MIMO mode there is a single S-CPICH transmission group representing "antenna 2" and for MIMO with 4 transmit antennas there are three S-CPICH transmission groups representing "antenna 2", "antenna 3" and "antenna 4". + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.2.5.5 Test requirements + +For UTRA FDD the test requirement for CPICH power for MIMO mode is: + +Either: + +The difference between the sums of the measured P-CPICH code domain power on each of the *TAB connectors* in the P-CPICH transmission group or the S-CPICH transmission groups shall be: + +Within $\pm 2.7$ dB for carrier frequency $f \leq 3.0$ GHz. + +Within $\pm 3.0$ dB for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +Or + +The difference between the measured P-CPICH code domain power on any 2 *TAB connectors* in either the P-CPICH transmission group or the S-CPICH transmission group(s) with corresponding beamforming weights shall be: + +Within $\pm 2.7$ dB for carrier frequency $f \leq 3.0$ GHz. + +Within $\pm 3.0$ dB for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.2.6 E-UTRA DL RS power + +#### 6.2.6.1 Definition and applicability + +This requirement applies to the *TAB connector* group(s) transmitting primary DL RS. + +The DL RS power is the resource element power of the Downlink Reference Symbol summed over the group of *TAB connectors* transmitting the DL RS for a cell. + +The absolute DL RS power is indicated on the DL-SCH. The absolute accuracy is defined as the maximum deviation between the DL RS power indicated on the DL-SCH and the DL RS power of each E-UTRA carrier. + +NOTE 1: A *TAB connector* group may comprise all *TAB connectors*. + +NOTE 2: A *TAB connector* may be mapped to several groups. + +NOTE 3: The manufacturer declares the *TAB connector* mapping to the DL RS transmission group(s). + +#### 6.2.6.2 Minimum requirement + +The minimum requirement for E-UTRA operation is in TS 37.105 [8], clause 6.2.6. + +There is no DL RS power requirement for UTRA FDD operation. + +There is no DL RS power requirement for UTRA TDD 1,28 Mcps option operation. + +There is no DL RS power requirement for NR operation. + +#### 6.2.6.3 Test purpose + +The test purpose is to verify that the E-UTRA FDD DL RS power is within the limits specified by the minimum requirement. + +#### 6.2.6.4 Method of test + +##### 6.2.6.4.1 Initial conditions + +Test environment: + +- normal; see annex B. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1. + +Set the *TAB connectors* in the DL RS transmission group (see table 4.10-1, D6.54) to output a signal in accordance to E-TM 1.1, in TS 36.141 [17] clause 6.1.1.1. + +##### 6.2.6.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors* in the *TAB connector* group(s) transmitting primary CPICH. *TAB connectors* may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to code domain analyser as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) Set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). +- 3) Measure the DL RS power on each of the *TAB connector(s)* transmitting the DL RS according to annex F in TS 36.141 [17]. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.2.6.5 Test requirements + +The DL RS power of each E-UTRA carrier shall be: + +within $\pm 2.9$ dB of the DL RS power indicated on the DL-SCH for carrier frequency $f \leq 3.0$ GHz. + +within $\pm 3.2$ dB of the DL RS power indicated on the DL-SCH for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +Alternatively, the DL RS power measured at each *TAB connector* shall be within $\pm 2.9$ dB for $f \leq 3.0$ GHz and within $\pm 3.2$ dB for $3.0$ GHz $< f \leq 4.2$ GHz of the DL RS power level indicated on the DL-SCH multiplied by a *TAB connector* specific beamforming weight. Beamforming weights on P-CPICH are set by the AAS BS to achieve an intended radiated pattern. + +## 6.3 Output power dynamics + +### 6.3.1 General + +The requirements in clause 6.3 apply during the *transmitter ON period*. Transmit signal quality (as specified in clause 6.5) shall be maintained for the output power dynamics requirements. + +### 6.3.2 UTRA Inner loop power control in the downlink + +#### 6.3.2.1 Definition and applicability + +Inner loop power control in the downlink is the ability of the AAS BS to adjust the transmitted output power of a code channel in accordance with the corresponding TPC commands received in the uplink. + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +#### 6.3.2.2 Minimum requirement + +The minimum requirement for UTRA FDD operation is in TS 37.105 [8], clause 6.3.2. + +The minimum requirement for UTRA TDD 1,28 Mcps option operation is in TS 25.105 [10], clause 6.4.2.1. + +There is no Inner loop power control requirement for E-UTRA or NR operation. + +#### 6.3.2.3 Test purpose + +The test purpose is to verify that the Inner loop power control in the downlink is within the limits specified by the minimum requirement. + +#### 6.3.2.4 Method of test + +##### 6.3.2.4.1 Initial conditions + +###### 6.3.2.4.1.1 General test conditions + +Test environment: + +- normal; see annex B. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1. + +Disable closed loop power control. + +###### 6.3.2.4.1.2 UTRA FDD + +Set each *TAB connector* to output a signal in accordance to TM2, in TS 25.141 [18], clause 6.1.1.2. + +The DPCH intended for power control is on channel 120 starting at -3 dB. + +Establish downlink power control with parameters as specified in table 6.3.2.4.1.2-1. + +**Table 6.3.2.4.1.2-1: DL power control parameters** + +| Parameter | Level/status | Unit | +|----------------------|--------------------------------------|------| +| UL signal mean power | $P_{\text{REFSENS}} + 10 \text{ dB}$ | dBm | +| Data sequence | PN9 | | + +#### 6.3.2.4.1.3 UTRA TDD + +Set the initial parameters of the *TAB connector* transmitted signal according to table 6.3.2.4.1.3-1. + +Operate the *TAB connector* in such a mode that it is able to interpret received TPC commands. + +NOTE: The BS tester used for this test must have the ability: + +- to analyze the output signal of the *TAB connector* under test with respect to code domain power, by applying the global in-channel Tx test method described in annex E of TS 25.142 [20]; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.3.2.4.1.3-1: Initial parameters of the *TAB connector* signal for power control steps 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 | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.3.2.4.2 Procedure + +##### 6.3.2.4.2.1 General procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) Set the *TAB connector* to transmit at manufacturers *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). + +##### 6.3.2.4.2.2 UTRA FDD + +- 1) Set and send alternating TPC bits from the UE simulator or UL signal generator. +- 2) Measure mean power level of the code under the test each time TPC command is transmitted. All steps within power control dynamic range declared by manufacturer (see table 4.10-1, D6.57) shall be measured. Use the code domain power measurement method defined in annex E in TS 25.141 [18]. +- 3) Measure the 10 highest and the 10 lowest power step levels within the power control dynamic range declared by manufacturer by sending 10 consecutive equal commands as described in TS 37.105 [8], clause 6.3.2. Table 6.3.2.3-2 + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 1) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.3.2.4.2.3 UTRA TDD + +- 1) Configure the *TAB connector* to enable power control steps of size 1 dB. +- 2) Set the BS tester to produce a sequence of TPC commands related to the active DPCH. This sequence shall be transmitted to the AAS BS within receive time slots TS i of the AAS BS and shall consist of a series of TPC commands with content "Decrease Tx power", followed by a series of TPC commands with content "Increase Tx power". Each of these series should be sufficiently long so that the code domain power of the active DPCH is controlled to reach its minimum and its maximum, respectively. +- 3) Measure the code domain power of the active DPCH over the 848 active chips of each transmit time slot AAS TS i of the AAS BS (this excludes the guard period) by applying the global in-channel Tx test method described in annex E in TS 25.142 [20]. +- 4) Based on the measurement made in step (5), calculate the power control step sizes and the average rate of change per 10 steps. +- 5) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (4) to (6). + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.3.2.5 Test requirements + +#### 6.3.2.5.1 UTRA FDD + +For UTRA FDD the test requirement Inner loop power control is: + +- a) *TAB connector* shall fulfil step size requirement shown in table 6.3.2.5.1-1 for all power control steps declared by manufacture in clause 4.10. +- b) For all measured Up/Down cycles, the difference of code domain power between before and after 10 equal commands (Up and Down), derived in step (3), shall not exceed the prescribed tolerance in table 6.3.2.5.1-2. + +**Table 6.3.2.5.1-1: UTRA FDD TAB connector power control step tolerance** + +| Power control commands in the downlink | Transmitter power control step tolerance | | | | | | | | +|----------------------------------------|------------------------------------------|---------|------------------|----------|----------------|---------|------------------|----------| +| | 2 dB step size | | 1.5 dB step size | | 1 dB step size | | 0.5 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | Lower | Upper | +| Up(TPC command "1") | +0.9 dB | +3.1 dB | +0.65 dB | +2.35 dB | +0.4 dB | +1.6 dB | +0.15 dB | +0.85 dB | +| Down(TPC command "0") | -0.9 dB | -3.1 dB | -0.65 dB | -2.35 dB | -0.4 dB | -1.6 dB | -0.15 dB | -0.85 dB | + +**Table 6.3.2.5.1-2: UTRA FDD TAB connector aggregated power control step range** + +| Power control commands in the downlink | Transmitter aggregated power control step range after 10 consecutive equal commands (up or down) | | | | | | | | +|----------------------------------------|--------------------------------------------------------------------------------------------------|----------|------------------|----------|----------------|----------|------------------|---------| +| | 2 dB step size | | 1.5 dB step size | | 1 dB step size | | 0.5 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | Lower | Upper | +| Up(TPC command "1") | +15.9 dB | +24.1 dB | +11.9 dB | +18.1 dB | +7.9 dB | +12.1 dB | +3.9 dB | +6.1 dB | +| Down(TPC command "0") | -15.9 dB | -24.1 dB | -11.9 dB | -18.1 dB | -7.9 dB | -12.1 dB | -3.9 dB | -6.1 dB | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.3.2.5.2 UTRA TDD + +For UTRA TDD 1,28 Mcps option the test requirement Inner loop power control is: + +For all measurements, the tolerance of the power control step sizes and the average rate of change per 10 steps shall be within the limits given in table 6.3.2.5.2-1. + +**Table 6.3.2.5.2-1: Test Requirements for power control step size tolerance** + +| Step size | Single step tolerance | Range of average rate of change in code domain power per 10 steps | | +|-----------|-----------------------|-------------------------------------------------------------------|----------| +| | | Minimum | maximum | +| 1 dB | ±0,6 dB | ±7,7 dB | ±12,3 dB | +| 2 dB | ±0,85 dB | ±15,7 dB | ±24,3 dB | +| 3 dB | ±1,1 dB | ±23,7 dB | ±36,3 dB | + +In case, the power control step size is set to 3 dB, the number of power control steps feasible within the power control dynamic range of the TAB connector under test may be less than 10. In this case, the evaluation of the average rate of change in code domain power shall be based on the number of power control steps actually feasible, and the permitted range of average rate of change shall be reduced compared to the values given in table 6.3.2.5.2-1 in proportion to the ratio (number of power control steps actually feasible /10). + +EXAMPLE: If the number of power control steps actually feasible is 9, the minimum and maximum value of the range of average rate of change in code domain power are given by 21,6 dB and 32,4 dB, respectively. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6. 3.3 Power control dynamic range + +### 6.3.3.1 Definition and applicability + +The power control dynamic range is the difference between the maximum and the minimum *code domain power* of a code channel for a specified reference condition. + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +### 6.3.3.2 Minimum requirement + +The minimum requirement for UTRA FDD operation are defined in TS 25.104 [9], clause 6.4.2.1. + +The minimum requirement for UTRA TDD 1,28 Mcps option operation is in TS 25.105 [10], clause 6.4.3.1 + +There is no power control dynamic range requirement for E-UTRA or NR operation. + +### 6.3.3.3 Test purpose + +The test purpose is to verify that the power control dynamic range is within the limits specified by the minimum requirement. + +### 6.3.3.4 Method of test + +#### 6.3.3.4.1 Initial conditions + +##### 6.3.3.4.1.1 General test conditions + +Test environment: + +- normal; see annex B. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1. + +#### 6.3.3.4.1.2 UTRA FDD + +Set each *TAB connector* to output a signal in accordance to TM2, in TS 25.141 [18], clause 6.1.1.2. + +#### 6.3.3.4.1.3 UTRA TDD + +Set the initial parameters of the *TAB connector* transmitted signal according to table 6.3.3.4.1.3-1. + +Operate the *TAB connector* in such a mode that it is able to interpret received TPC commands. + +NOTE: The BS tester used for this test must have the ability: + +- to analyze the output signal of the *TAB connector* under test with respect to code domain power, by applying the global in-channel Tx test method described in annex E of TS 25.142 [20]; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.3.3.4.1.3-1: Parameters of the BS transmitted signal for power control dynamic range 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 | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.3.3.4.2 Procedure + +##### 6.3.3.4.2.1 General procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) Set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ) + +##### 6.3.3.4.2.1 UTRA FDD + +- 1) Using TM2, set the code domain power of the DPCH under test to $P_{\text{max,c,TABC}} - 3$ dB. Power levels for other code channels may be adjusted if necessary. +- 2) Measure the code domain power of the code channel under test. Use the code domain power measurement method defined in annex E in TS 25.141 [18]. +- 3) Set the code domain power of the DPCH under test to $P_{\text{max,c,TABC}} - 28$ dB by means determined by the manufacturer. The power levels for the other code channels used in step 2 shall remain unchanged (the overall output power will drop by approximately 3 dB). +- 4) Measure the code domain power of the code channel under test. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.3.3.4.2.2 UTRA TDD + +- 1) Configure the *TAB connector* transmitter unit to enable power control steps of size 1 dB. +- 2) Set the BS tester to produce a sequence of TPC commands related to the active DPCH, with content "Decrease Tx power". This sequence shall be sufficiently long so that the code domain power of the active DPCH is controlled to reach its minimum, and shall be transmitted to the AAS BS within the receive time slots TS i of the BS. +- 3) Measure the code domain power of the active DPCH over the 848 active chips of a transmit time slot TS i of the AAS BS (this excludes the guard period) by applying the global in-channel Tx test method described in annex E of TS 25.142 [20]. +- 4) Set the BS tester to produce a sequence of TPC commands related to the active DPCH, with content "Increase Tx power". This sequence shall be sufficiently long so that the code domain power of the active DPCH is controlled to reach its maximum, and shall be transmitted to the AAS BS within the receive time slots TS i of the AAS BS. +- 5) Measure the code domain power of the active DPCH over the 848 active chips of a transmit time slot TS i of the AAS BS (this excludes the guard period) by applying the global in-channel Tx test method described in annex E in TS 25.142 [20]. +- 6) Determine the power control dynamic range by calculating the difference between the maximum code domain power measured in step (5) and the minimum code domain power measured in step (7). +- 7) Configure the *TAB connector* transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (4) to (8). + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 8) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.3.3.5 Test requirements + +##### 6.3.3.5.1 UTRA FDD + +For UTRA FDD the test requirement Inner loop power control is: + +Downlink (DL) power control dynamic range: + +- maximum code domain power: *TAB connector* maximum output power ( $P_{\max,c,TABC}$ ) -4.1 dB or greater; +- minimum code domain power: *TAB connector* maximum output power ( $P_{\max,c,TABC}$ ) -26.9 dB or less. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +##### 6.3.3.5.2 UTRA TDD + +For UTRA TDD 1,28 Mcps option the power control dynamic range derived according to clause 6.3.2.4 shall be greater than or equal to 29,7dB. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.3.4 Total power dynamic range + +##### 6.3.4.1 Definition and applicability + +The total power dynamic range is the difference between the maximum and the minimum output power for a specified reference condition. + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +NOTE 1: The upper limit of the dynamic range is the *TAB connector* maximum output power ( $P_{\text{Rated,c,TABC}}$ ). The lower limit of the dynamic range is the lowest minimum power from the *TAB connector* when no traffic channels are activated. + +Particularly for E-UTRA, the total power dynamic range is the difference between the maximum and the minimum transmit power of an OFDM symbol for a specified reference condition. + +NOTE 2: The upper limit of the dynamic range at a *TAB connector* is the OFDM symbol power at maximum output power ( $P_{\text{Rated,c,TABC}}$ ) when transmitting on all RBs. The lower limit of the dynamic range at a *TAB connector* is the OFDM symbol power when one resource block is transmitted. The OFDM symbol carries PDSCH or sPDSCH (for sTTI) and not contain RS, PBCH or synchronization signals. + +#### 6.3.4.2 Minimum requirement + +The minimum requirement for UTRA FDD operation are defined in TS 25.104 [9], clause 6.4.3.1. + +There is no total power dynamic range requirement for UTRA TDD 1,28 Mcps option operation. + +The minimum requirement for E-UTRA operation is in TS 36.104 [11], clause 6.3.2.1. + +The minimum requirement for NR operation is in TS 38.104 [36], clause 6.3.3.2. + +#### 6.3.4.3 Test purpose + +The test purpose is to verify that the total power dynamic range is within the limits specified by the minimum requirement. + +#### 6.3.4.4 Method of test + +##### 6.3.4.4.1 Initial conditions + +###### 6.3.4.4.1.1 General test conditions + +Test environment: normal; see annex B. + +RF channels to be tested: M; see clause 4.12.1. + +###### 6.3.4.4.1.2 UTRA FDD + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single band operation; see clause 4.12.1. + +Set each *TAB connector* to output a signal in accordance to TM2, in TS 25.141 [18], clause 6.1.1.2. + +###### 6.3.4.4.1.3 E-UTRA + +Set the Channel set-up of the *TAB connector* transmitted signal according to: + +- E-TM3.1, or +- sE-TM3.1-1 for subslot TTI, or +- sE-TM3.1-2 for slot TTI. + +###### 6.3.4.4.1.4 NR + +Set the Channel set-up of the *TAB connector* transmitted signal according to procedure described in TS 38.141-1 [37] in clause 6.3.3.4.2. + +#### 6.3.4.4.2 Procedure + +##### 6.3.4.4.2.1 General procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in annex D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) Set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). + +##### 6.3.4.4.2.2 UTRA FDD + +The downlink total dynamic range is computed as the difference of the maximum carrier output power, measured as defined in step 3 in clause 6.2.2.4.3 and the carrier power measured at step 3 of the Error Vector Magnitude test, as described in clause 6.5.4.4.2.1. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 1) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +##### 6.3.4.4.2.3 E-UTRA + +- 1) Measure the average OFDM symbol power as defined in annex F of TS 36.141 [17]. +- 2) Set the *TAB connector* to transmit a signal according to the same selection as in subclause 6.3.4.4.1.3: + - E-TM2, or + - sE-TM2-1 for subslot TTI, or + - sE-TM2-2 for slot TTI. +- 3) Measure the average OFDM symbol power as defined in annex F of TS 36.141 [17]. The measured OFDM symbols shall not contain RS, PBCH or synchronisation signals. +- 4) If BS supports 256QAM, set the channel set-up of the *TAB connector* transmitted signal according to E-TM3.1a (or sE-TM3.1a-1 for subslot TTI, or sE-TM3.1a-2 for slot TTI) and repeat step 1. Set the *TAB connector* to transmit a signal according to E-TM2a (or sE-TM2a-1 for subslot TTI, or sE-TM2a-2 for slot TTI) and repeat step 3. +- 5) If BS supports 1024QAM, set the channel set-up of the *TAB connector* transmitted signal according to E-TM3.1b and repeat step 1. Set the *TAB connector* to transmit a signal according to E-TM2b and repeat step 3. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +##### 6.3.4.4.2.4 NR + +- 1) Measure the average OFDM symbol power as defined in annex D in TS 38.141-1 [37]. +- 2) Set the BS to transmit a signal according to procedure described in TS 38.141-1 [37] in clause 6.3.3.4.2. +- 3) Measure the average OFDM symbol power as defined in annex D in TS 38.141-1 [37]. + +The measured OFDM symbols shall not contain RS or SSB. + +In addition, for *multi-band connectors*, the following steps shall apply: + +- 4) For a multi-band connectors and single band tests, repeat the steps above per involved operating band where single band test configurations and test models shall apply with no carrier activated in the other operating band. + +### 6.3.4.5 Test requirements + +#### 6.3.4.5.1 UTRA FDD + +For UTRA FDD the downlink total power dynamic range shall be 17.7 dB or greater. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.3.4.5.2 E-UTRA + +The downlink (DL) total power dynamic range for each E-UTRA carrier shall be larger than or equal to the level in table 6.3.4.5.1-1. + +**Table 6.3.4.5.2-1 E-UTRA TAB connector total power dynamic range, paired spectrum** + +| E-UTRA channel bandwidth (MHz) | Total power dynamic range (dB) | +|--------------------------------|--------------------------------| +| 1.4 | 7.3 | +| 3 | 11.3 | +| 5 | 13.5 | +| 10 | 16.5 | +| 15 | 18.3 | +| 20 | 19.6 | + +NOTE 1: 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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +NOTE 2: Additional test requirements for the Error Vector Magnitude (EVM) at the lower limit of the dynamic range are defined in clause 6.5.4. + +#### 6.3.4.5.3 NR + +The downlink (DL) total power dynamic range for each NR carrier shall be larger than or equal to the level in table 6.3.4.5.3-1. + +**Table 6.3.4.5.3-1: NR TAB connector total power dynamic range** + +| NR channel bandwidth (MHz) | Total power dynamic range (dB) | | | +|----------------------------|--------------------------------|------------|------------| +| | 15 kHz SCS | 30 kHz SCS | 60 kHz SCS | +| 5 | 13.5 | 10 | N/A | +| 10 | 16.7 | 13.4 | 10 | +| 15 | 18.5 | 15.3 | 12.1 | +| 20 | 19.8 | 16.6 | 13.4 | +| 25 | 20.8 | 17.7 | 14.5 | +| 30 | 21.6 | 18.5 | 15.3 | +| 35 | 22.7 | 19.6 | 16.4 | +| 40 | 22.9 | 19.8 | 16.6 | +| 45 | 23.8 | 20.7 | 17.6 | +| 50 | 23.9 | 20.8 | 17.7 | +| 60 | N/A | 21.6 | 18.5 | +| 70 | N/A | 22.3 | 19.2 | +| 80 | N/A | 22.9 | 19.8 | +| 90 | N/A | 23.4 | 20.4 | +| 100 | N/A | 23.9 | 20.9 | + +NOTE 1: 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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +NOTE 2: Additional test requirements for the Error Vector Magnitude (EVM) at the lower limit of the dynamic range are defined in clause 6.5.4. + +## 6.3.5 IPDL time mask + +### 6.3.5.1 Definition and applicability + +To support IPDL location method in UTRA FDD operation, the AAS BS shall interrupt all transmitted signals in the downlink (i.e. common and dedicated channels). The IPDL time mask specifies the limits of the *TAB connector* output power during these idle periods. + +This requirement applies only to AAS BS supporting IPDL. The requirement applies at each *TAB connector* supporting transmission in the operating band. + +### 6.3.5.2 Minimum requirement + +The minimum requirement for UTRA FDD operation are defined in TS 25.104 [9], clause 6.4.5.1. + +There is no IPDL requirement for UTRA TDD 1,28 Mcps option operation. + +There is no IPDL requirement for E-UTRA or NR operation. + +### 6.3.5.3 Test purpose + +The test purpose is to verify the ability of the AAS BS to temporarily reduce its output power on each *TAB connector* below a specified value to improve time difference measurements made by UE for location services. + +### 6.3.5.4 Method of test + +#### 6.3.5.4.1 Initial conditions + +Test environment: + +- normal; see annex B. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1. + +Set each *TAB connector* to output a signal in accordance to TM1, in clause 4.12.2. + +Configure the *TAB connector* to produce idle periods in continuous mode. The IPDL parameters as defined in TS 25.214 [23] shall have the following values: + +- IP\_Spacing = 5 +- IP\_Length = 10 CPICH symbols +- Seed = 0 + +#### 6.3.5.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. + +- 2) Set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). +- 3) Measure the mean power at the *TAB connector* over a period starting 27 chips after the beginning of the IPDL period and ending 27 chips before the expiration of the IPDL period. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.3.5.5 Test requirements + +The mean power measured according to step (3) in clause 6.3.5.4.2 shall be equal to or less than + +$$\text{TAB connector maximum output power } (P_{\text{max,c,TABC}}) - 34.3 \text{ dB.}$$ + +See also figure 6.3.5.5-1. + +![Figure 6.3.5.5-1: IPDL Time Mask. The diagram shows a power level line labeled 'BS maximum output power'. A vertical double-headed arrow indicates a power difference of '34.3 dB' from this line down to a dashed horizontal line. A central grey rectangular block represents the IPDL period. Horizontal double-headed arrows labeled '27 chips' are positioned on both sides of the grey block, between the start and end of the IPDL period. A horizontal double-headed arrow labeled 'IP_Length' spans the entire duration of the IPDL period, from the start of the first '27 chips' interval to the end of the second.](f43d225d8fed2845b8d7e5afecbfe636_img.jpg) + +Figure 6.3.5.5-1: IPDL Time Mask. The diagram shows a power level line labeled 'BS maximum output power'. A vertical double-headed arrow indicates a power difference of '34.3 dB' from this line down to a dashed horizontal line. A central grey rectangular block represents the IPDL period. Horizontal double-headed arrows labeled '27 chips' are positioned on both sides of the grey block, between the start and end of the IPDL period. A horizontal double-headed arrow labeled 'IP\_Length' spans the entire duration of the IPDL period, from the start of the first '27 chips' interval to the end of the second. + +Figure 6.3.5.5-1: IPDL Time Mask + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.3.6 RE Power control dynamic range + +### 6.3.6.1 Definition and applicability + +The RE power control dynamic range is the difference between the power of an RE and the average RE power for a *TAB connector* at maximum output power ( $P_{\text{Rated,c,TABC}}$ ) for a specified reference condition. + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +### 6.3.6.2 Minimum requirement + +There is no RE Power control dynamic range requirement for UTRA FDD operation. + +There is no RE Power control dynamic range requirement for UTRA TDD 1,28 Mcps option operation. + +The minimum requirement for E-UTRA operation are defined in TS 36.104 [11], clause 6.3.1.1. + +The minimum requirement for NR operation are defined in TS 38.104 [36], clause 6.3.2.2. + +### 6.3.6.3 Method of test + +No specific test or test requirements are defined for RE Power control dynamic range. The Error Vector Magnitude test, as described in clause 6.5.4 provides sufficient test coverage for this requirement. + +## 6.4 Transmit ON/OFF power + +### 6.4.1 General + +Transmitter ON/OFF power requirements apply only to TDD operation of UTRA and E-UTRA. + +### 6.4.2 Transmitter OFF power + +#### 6.4.2.1 Definition and applicability + +Transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth(s) of the BS centred on the central frequency of the RF bandwidth(s) during the *transmitter OFF period*. N is equal to 1 for UTRA and E-UTRA SCS/15 for NR, where SCS is Sub Carrier Spacing in kHz. + +The requirement applies at each *TAB connector* supporting transmission in the operating band. + +For *multi-band TAB connectors* and for *single band TAB connectors* supporting transmission in multiple operating bands, the requirement is only applicable during the *transmitter OFF period* in all supported operating bands. + +For AAS BS supporting intra-band contiguous CA, the transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *Aggregated BS Channel Bandwidth* $BW_{\text{Channel\_CA}}$ centred on $(F_{\text{edge,high}} + F_{\text{edge,low}})/2$ during the *transmitter OFF period*. N is equal to 1 if there are any UTRA or E-UTRA carriers, or for NR $N = \text{SCS}/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *Aggregated BS Channel Bandwidth*. + +#### 6.4.2.2 Minimum requirement + +There is no transmitter off power requirement for UTRA FDD operation. + +The minimum requirement for UTRA TDD 1,28 Mcps option operation are defined in TS 37.105 [8], clause 6.4.2.3. + +The minimum requirement for E-UTRA operation are defined in TS 37.105 [8], clause 6.4.2.4. + +The minimum requirement for MSR and NR operation are defined in TS 37.105 [8], clause 6.4.2.2. + +#### 6.4.2.3 Test purpose + +The purpose of this test is to verify the *TAB connector* transmitter OFF power is within the limits of the minimum requirements. + +#### 6.4.2.4 Method of test + +##### 6.4.2.4.1 Initial conditions + +Test environment: + +- normal; see annex B. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested: + +- $M_{\text{RFBW}}$ in single band operation, see clause 4.12.1; $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation; see clause 4.12.1. + +#### 6.4.2.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) Set each *TAB connector* to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. For single carrier set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). +- 3) For UTRA and E-UTRA, measure the mean power spectral density measured over 70 $\mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth of the *TAB connector* centred on the central frequency of the RF bandwidth. 70 $\mu\text{s}$ average window centre is set from 35 $\mu\text{s}$ after end of one transmitter ON period + 17 $\mu\text{s}$ to 35 $\mu\text{s}$ before start of next transmitter ON period - 6.25 $\mu\text{s}$ . + +For NR, measure the mean power spectral density over 70/N $\mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth of the *TAB connector* centred on the central frequency of the RF bandwidth. 70/N $\mu\text{s}$ average window centre is set from 35/N $\mu\text{s}$ after end of one transmitter ON period + 10 $\mu\text{s}$ to 35/N $\mu\text{s}$ before start of next transmitter ON period – 10 $\mu\text{s}$ . N = SCS/15, where SCS is Sub Carrier Spacing in kHz. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.4.2.5 Test requirements + +The measured mean power spectral density according to clause 6.4.2.4.2 shall be less than -83 dBm/MHz for carrier frequency $f \leq 3.0$ GHz. + +The measured mean power spectral density according to clause 6.4.2.4.2 shall be less than -82.5 dBm/MHz for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +For *multi-band TAB connector*, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.4.3 Transmitter transient period + +#### 6.4.3.1 Definition and applicability + +The *transmitter transient period* is the time period during which the transmitter unit is changing from the OFF period to the ON period or vice versa. The *transmitter transient period* is illustrated in figure 6.4.3.1-1. + +![Figure 6.4.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two levels: 'ON power level (Informative)' and 'OFF power level'. The x-axis is divided into three main segments: 'UL Timeslots', 'Transmitter ON period (DL Timeslots and DwPTS)', and 'GP and UpPTS'. The 'Transmitter ON period' is the duration where the power is at the ON level. The 'Transmitter OFF period' is the duration where the power is at the OFF level. The 'Transmitter transient period' is the duration of the power transition between the ON and OFF levels, indicated by arrows pointing to the rising and falling edges of the power curve.](be2d9105109f6a87907ab68cb88548d9_img.jpg) + +Figure 6.4.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two levels: 'ON power level (Informative)' and 'OFF power level'. The x-axis is divided into three main segments: 'UL Timeslots', 'Transmitter ON period (DL Timeslots and DwPTS)', and 'GP and UpPTS'. The 'Transmitter ON period' is the duration where the power is at the ON level. The 'Transmitter OFF period' is the duration where the power is at the OFF level. The 'Transmitter transient period' is the duration of the power transition between the ON and OFF levels, indicated by arrows pointing to the rising and falling edges of the power curve. + +**Figure 6.4.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period** + +This requirement applies at each *TAB connector* supporting transmission in the operating band. + +#### 6.4.3.2 Minimum requirement + +The minimum requirement for MSR operation is in TS 37.104 [12], clause 6.4.2.1. + +There is no Transmitter transient period requirement for UTRA FDD operation. + +The minimum requirement for single RAT UTRA TDD 1,28 Mcps option operation are defined in TS 25.105 [10], clause 6.5.2.1.2. + +The minimum requirement for single RAT E-UTRA operation are defined in TS 36.104 [11], clause 6.4.2.1. + +#### 6.4.3.3 Test purpose + +The purpose of this test is to verify the *TAB connector* transmitter transient periods are within the limits of the minimum requirements. + +#### 6.4.3.4 Method of test + +##### 6.4.3.4.1 Initial conditions + +###### 6.4.3.4.1.1 MSR operation + +For MSR operation the test for transmitter off power in clause 6.4.2 demonstrates compliance. + +###### 6.4.3.4.1.2 UTRA TDD operation + +Test environment: + +- normal; see clause B.2. + +RF channels to be tested for single carrier (SC): + +- M; see clause 4.12.1. + +RF bandwidth positions to be tested: + +- $M_{\text{RFBW}}$ in single band operation; see clause 4.12.1; $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ in multi-band operation, see clause 4.12.1. + +**Table 6.4.3.4.1.2-1: Parameters of the transmitted signal for transmit ON/OFF time mask test for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS $i$ ; $i = 0, 1, 2, 3, 4, 5, 6$ :
transmit, if $i$ is 0,4,5,6;
receive, if $i$ is UpPCH,1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 8 | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.4.3.4.1.3 E-UTRA operation + +Test environment: + +- normal; see clause B.2. + +RF channels to be tested for single carrier: + +- $M$ ; see clause 4.12.1. + +RF bandwidth positions to be tested for multi-carrier and/or CA: + +- $M_{\text{RFBW}}$ in single-band operation, see clause 4.12.1; $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ in multi-band operation, see clause 4.12.1. + +#### 6.4.3.4.2 Procedure + +##### 6.4.3.4.2.1 MSR operation + +For MSR operation the test for transmitter off power in clause 6.4.2 demonstrates compliance. + +##### 6.4.3.4.2.2 UTRA TDD operation + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) Set each *TAB connector* to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. For single carrier set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). +- 3) Measure the RRC filtered mean power of the *TAB connector* output signal chipwise (i.e. averaged over time intervals of one chip duration) over the transmit off power period starting 11 chips before the start of the receive time slot $TS\ i = \text{UpPCH}$ , and ending 8 chips before the next transmit time slot $TS\ i=4$ starts. + +##### 6.4.3.4.2.3 E-UTRA operation + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. + +As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity, efficiency and avoiding e.g. carrier leakage, + +the resolution bandwidth may 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. + +- 2) For a Set each *TAB connector* to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. For single carrier set the *TAB connector* to transmit at manufacturers declared *rated carrier output power per TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). +- 3) Measure the mean power spectral density over 70 $\mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth of the *TAB connector* centred on the central frequency of the RF bandwidth. 70 $\mu\text{s}$ average window centre is set from 35 $\mu\text{s}$ after end of one transmitter ON period + 17 $\mu\text{s}$ to 35 $\mu\text{s}$ before start of next transmitter ON period - 17 $\mu\text{s}$ . +- 4) For a *TAB connector* supporting contiguous CA, measure the mean power spectral density over 70 $\mu\text{s}$ filtered with a square filter of bandwidth equal to the Aggregated Channel Bandwidth $BW_{\text{Channel\_CA}}$ centred on $(F_{\text{edge\_high}} + F_{\text{edge\_low}})/2$ . 70 $\mu\text{s}$ average window centre is set from 35 $\mu\text{s}$ after end of one transmitter ON period + 17 $\mu\text{s}$ to 35 $\mu\text{s}$ before start of next transmitter ON period - 17 $\mu\text{s}$ . + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.4.3.5 Test requirements + +#### 6.4.3.5.1 MSR operation + +For MSR operation the test for transmitter off power in clause 6.4.2 demonstrates compliance. + +#### 6.4.3.5.1 UTRA TDD operation + +Each value of the power measured according to clause 6.4.3.4.2.2 shall be below -41,3 dBm in the period from 85 chips to 88 chips after the burst and below -80 dBm in the period where the Tx OFF power specification is applicable. + +For *multi-band TAB connector*, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +#### 6.4.3.5.1 E-UTRA operation + +The measured mean power spectral density according to clause 6.3.5.4.3 shall be less than -83 dBm/MHz for carrier frequency $f \leq 3.0$ GHz. + +The measured mean power spectral density according to clause 6.3.5.4.3 shall be less than -82.5 dBm/MHz for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +For *multi-band TAB connector*, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.5 Transmitted signal quality + +### 6.5.1 General + +The requirements apply per TAB connector unless otherwise stated differently. + +The requirement applies during the transmitter ON period. + +## 6.5.2 Frequency error + +### 6.5.2.1 Definition and applicability + +Frequency error is the measure of the difference between the actual AAS BS transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation. + +It is not possible to verify by testing that the data clock is derived from the same frequency source as used for RF generation. This may be confirmed by the manufacturer's declaration. + +### 6.5.2.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 6.5.2.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 6.5.2.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 6.5.2.4. + +### 6.5.2.3 Test purpose + +The test purpose is to verify that frequency error is within the limit specified by the minimum requirement. + +### 6.5.2.4 Method of test + +Requirement is tested together with modulation quality test, as described in clause 6.5.4. + +### 6.5.2.5 Test Requirements + +#### 6.5.2.5.1 UTRA FDD test requirement + +The frequency error for every measured slot shall be between the minimum and maximum value specified in table 6.5.2.5.1-1. + +**Table 6.5.2.5.1-1: Frequency error test requirement** + +| BS class | Accuracy | +|-----------------|-----------------------------------------| +| Wide Area BS | $\pm(0.05 \text{ ppm} + 12 \text{ Hz})$ | +| Medium Range BS | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | +| Local Area BS | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.5.2.5.2 UTRA TDD test requirement + +The frequency error for every measured slot shall be between the minimum and maximum value specified in table 6.5.2.5.2-1. + +**Table 6.5.2.5.2-1: Frequency error test requirement** + +| BS class | Accuracy | +|-----------------|-----------------------------------------| +| Wide Area BS | $\pm(0.05 \text{ ppm} + 12 \text{ Hz})$ | +| Medium Range BS | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | + +### 6.5.2.5.3 E-UTRA and NR test requirement + +The modulated carrier frequency of each E-UTRA or NR carrier configured by the AAS BS shall be accurate to within the accuracy range given in table 6.5.2.5.3-1 observed over a period of one subframe (1 ms). + +**Table 6.5.2.5.3-1: Frequency error test requirement** + +| BS class | Accuracy | +|-----------------|-----------------------------------------| +| Wide Area BS | $\pm(0.05 \text{ ppm} + 12 \text{ Hz})$ | +| Medium Range BS | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | +| Local Area BS | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.5.3 Time alignment error + +### 6.5.3.1 Definition and applicability + +This requirement applies to frame timing in: + +- UTRA single/multi-carrier transmissions and their combinations with MIMO or TX diversity. +- E-UTRA single/multi-carrier transmissions and their combinations with MIMO or TX diversity. +- E-UTRA *carrier aggregation*, with or without MIMO or TX diversity. +- NR single/multi-carrier transmissions, and their combinations with MIMO. +- NR *carrier aggregation*, with or without MIMO. + +Frames of the UTRA/E-UTRA/NR signals present at the *TAB connectors* are not perfectly aligned in time. In relation to each other, the RF signals present at the *transceiver array boundary* may experience certain timing differences. + +For a specific set of signals/transmitter configuration/transmission mode, the Time Alignment Error (TAE) is defined as the largest timing difference between any two different E-UTRA signals or any two different UTRA signals or any two different NR signals belonging to different *TAB Connectors* belonging to different transmitter groups at the *transceiver array boundary*, where transmitter groups are associated with the *TAB connectors* in the transceiver unit array corresponding to TX diversity (except NR), MIMO transmission, *carrier aggregation*, etc. + +### 6.5.3.2 Minimum requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 6.5.3.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 6.5.3.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 6.5.3.4. + +### 6.5.3.3 Test purpose + +To verify that the time alignment error is within the limit specified by the minimum requirement. + +### 6.5.3.4 Method of test + +#### 6.5.3.4.1 Initial conditions + +##### 6.5.3.4.1.1 General test conditions + +Test environment: normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.12.1. + +#### 6.5.3.4.1.2 UTRA FDD + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ ; $B_{\text{RFBW\_T}}'_{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}_{\text{RFBW}}$ in multi-band operation; see clause 4.12.1. + +Refer to clause D.1.3 for a functional block diagram of the test set-up. + +#### 6.5.3.4.1.3 UTRA TDD + +RF bandwidth positions to be tested for multi-carrier: $M_{\text{RFBW}}$ in single band operation, see clause 4.12.1. + +- For a *TAB connectors* declared to be capable of single carrier operation only, set the base station to transmit according to table 6.5.3.4.1.3-1 on one cell using MIMO. +- For a *multi-carrier TAB connectors*, set to transmit according to table 6.5.3.4.1.3-1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 5.3. + +**Table 6.5.3.4.1.3-1: Parameters of the BS transmitted signal 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 | TS0 and DwPTS | +| Spreading factor | 16 | + +#### 6.5.3.4.1.4 E-UTRA and NR + +RF bandwidth positions to be tested for multi-carrier and/or CA: + +- $M_{\text{RFBW}}$ in single-band operation, see clause 4.12.1; +- $B_{\text{RFBW\_T}}'_{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}_{\text{RFBW}}$ in multi-band operation, see clause 4.7. + +#### 6.5.3.4.2 Procedure + +##### 6.5.3.4.2.1 General procedure + +*TAB connectors* to be tested are identified from the declared sets of *TAB connector beam forming groups* (see clause 4.10 D.6.58). + +Connect two representative *TAB connectors* one from each of the declared groups to the measurement equipment according to annex D.1.3. Terminate any unused *TAB connector(s)*. + +Compliance is to be demonstrated between all pairs of *TAB connectors beam forming groups*, however it is not required to exhaustively measure the time alignment error between every combination of pairs of representative *TAB connectors*. Compliance can be demonstrated by comparison of a reduced set of representative measurement results. + +##### 6.5.3.4.2.2 UTRA FDD procedure + +- 1) If the AAS BS supports TX diversity or MIMO, set the *TAB connectors* to transmit TM1, clause 4.12.2, at manufacturer's declared rated output power, $P_{\text{Rated,c,TABC}}$ on one cell using TX diversity or MIMO. +- 2) Measure the time alignment error between the signals using the P-CPICH on one of the representative *TAB connector* from the main signal conveyed via a *TAB connectors beam forming group* and the CPICH on the *TAB connector* from the diversity signal conveyed via another *TAB connectors beam forming group*. +- 3) If the AAS BS supports DC-HSDPA, 4C-HSDPA, NC-4C-HSDPA or 8C-HSDPA set the *TAB connectors* to transmit according to TM1, without using TX diversity or MIMO, on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +- 4) Measure the time alignment error between the signals using the P-CPICH on one of the representative *TAB connector* and CPICH signals on representative *TAB connector* from another group. +- 5) If the AAS BS supports DB-DC-HSDPA or any of the multi-band 4C-HSDPA or 8C-HSDPA configurations set the *TAB connectors* to transmit TM1 on two carriers belonging to different frequency bands, without using TX diversity or MIMO on any of the carriers. +- 6) Measure the time alignment error between the signals using the P-CPICH and CPICH signals on the *TAB connectors*. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 7) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.5.3.4.2.3 UTRA TDD procedure + +- 1) Start the *TAB connector beam forming groups* transmission at the manufacturer's specified rated output power, $P_{\text{Rated,c,TABC}}$ at the *TAB connector*. +- 2) Measure the time alignment error between the P-CCPCH and DwPTS on the representative *TAB connectors* under test. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.5.3.4.2.4 E-UTRA and NR procedure + +- 1) Set the AAS BS to transmit E-TM1.1 or NR-FR1-TM 1.1 or any DL signal using TX diversity (except NR), MIMO transmission or carrier aggregation. + +NOTE: For TX diversity (except NR) and MIMO transmission, different ports may be configured in E-TM (using CRS ports $p = 0$ and $1$ with FDM) or NR-FR1-TM (using DMRS ports $p = 1000$ and $1001$ with CDM). + +For an AAS BS declared to be capable of single carrier operation only, set the representative *TAB connectors* to transmit according to manufacturer's declared rated output power, $P_{\text{Rated,c,TABC}}$ . + +If the AAS BS supports intra band contiguous or non-contiguous Carrier Aggregation set the representative *TAB connectors* to transmit using the applicable test configuration and corresponding power setting specified in clauses 4.10 and 4.11. + +If the AAS BS supports inter band carrier aggregation set the representative *TAB connectors* to transmit, for each band, a single carrier or all carriers, using the applicable test configuration and corresponding power setting specified in clauses 4.10 and 4.11. + +- 2) Measure the time alignment error between the reference symbols on the carrier(s) from the representative *TAB connector(s)*. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.5.3.5 Test requirement + +#### 6.5.3.5.1 UTRA FDD test requirement + +For Tx diversity and MIMO transmission, in the tested cell, TAE shall not exceed $0.35 T_c$ . + +For transmission of multiple cells within a frequency band TAE shall not exceed $0.6 T_c$ . + +For transmission of multiple cells in different frequency bands TAE shall not exceed $5.1 T_c$ . + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.5.3.5.2 UTRA TDD test requirement + +The time alignment error shall be less than 65 + 78 ns. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.5.3.5.3 E-UTRA test requirement + +For MIMO or TX diversity transmissions, at each carrier frequency, TAE shall not exceed 90 ns. + +For intra-band carrier aggregation, with or without MIMO or TX diversity, TAE shall not exceed 155 ns. + +For intra-band non-contiguous carrier aggregation, with or without MIMO or TX diversity, TAE shall not exceed 285 ns. + +For inter-band carrier aggregation, with or without MIMO or TX diversity, TAE shall not exceed 285 ns. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.5.3.5.4 NR test requirement + +For MIMO transmissions, at each carrier frequency, TAE shall not exceed 90 ns. + +For intra-band contiguous CA, with or without MIMO, TAE shall not exceed 285 ns. + +For intra-band non-contiguous CA, with or without MIMO, TAE shall not exceed 3.025 µs. + +For inter-band CA, with or without MIMO, TAE shall not exceed 3.025 µs. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.5.4 Modulation quality + +#### 6.5.4.1 Definition and applicability + +Modulation quality is defined by the difference between the measured carrier signal and a reference signal. Modulation quality can be expressed e.g. as Peak Code domain Error (PCDE) or Relative Code domain Error (RCDE) or Error Vector Magnitude (EVM) for UTRA and Error Vector Magnitude (EVM) for E-UTRA and NR. + +#### 6.5.4.2 Minimum Requirement + +The minimum requirement for UTRA operation are defined in TS 37.105 [8], clause 6.5.4.3. + +The minimum requirement for E-UTRA operation are defined in TS 37.105 [8], clause 6.5.4.4. + +The minimum requirement for NR operation are defined in TS 37.105 [8], clause 6.5.4.2. + +#### 6.5.4.3 Test purpose + +The test purpose is to verify that modulation quality is within the limit specified by the minimum requirement. + +#### 6.5.4.4 UTRA FDD method of test + +##### 6.5.4.4.1 Initial conditions + +Test environment: normal; see annex B.2. + +RF channels to be tested for single carrier: B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* position to be tested: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ single-band operation, see clause 4.12.1 single-band operation. + +##### 6.5.4.4.2 Procedure + +###### 6.5.4.4.2.1 EVM procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) For a *TAB connector* declared to be capable of single carrier operation only, set the *TAB connector* to transmit a signal according to TM1 according to clause 4.12.2 at manufacturer's declared rated output power, $P_{\text{Rated,c,TABC}}$ . +For a *TAB connector* declared to be capable of multi-carrier operation, set the *TAB connector* to transmit according to clause 4.12.2 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. +- 2) For each carrier, measure the Error Vector Magnitude and frequency error as defined in annex D.1.1 and the mean power of the signal. The measurement shall be performed on all 15 slots of the frame defined by the Test Model. +- 3) Using the same setting as in step 1), set the *TAB connector* to transmit a signal according to TM4, clause 4.12.2, with X value equal to 18, and repeat step 2). If the requirement in clause 6.5.4.5 is not fulfilled, decrease the total output power by setting the base station to transmit a signal according to TM4 with X greater than 18, and repeat step 2). + +The following test shall be additionally performed if the base station supports HS-PDSCH transmission using 16QAM: + +- 4) Using the same setting as in step 1), set the base station to transmit according to TM5, clause 4.12.2. +- 5) Repeat step 2). + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +###### 6.5.4.4.2.2 PCDE procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) For a *TAB connector* declared to be capable of single carrier operation only, set the *TAB connector* to transmit a signal according to TM3, clause 4.12.2, at manufacturer's declared rated output power, $P_{\text{Rated,c,TABC}}$ . +For a *TAB connector* declared to be capable of multi-carrier operation, set the *TAB connector* to transmit according to TM3 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. +- 2) Measure Peak code domain error according to annex D.1.1. The measurement shall be performed on all 15 slots of the frame defined by TM3. For a *TAB connector* declared to be capable of multi-carrier operation the measurement is performed on one of the carriers under test. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.5.4.4.2.3 RCDE procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) For a *TAB connector* declared to be capable of single carrier operation only, set the *TAB connector* to transmit a signal according to TM6, clause 4.12.2, at manufacturer's declared rated output power, $P_{\text{Rated,c,TABC}}$ + +For a *TAB connector* declared to be capable of multi-carrier operation, set the *TAB connector* to transmit according to TM6, clause 4.12.2, on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +- 2) Measure average Relative code domain error according to annex E. The measurement shall be performed over one frame defined by TM6 and averaged as specified in clause 4.12.2. For a *TAB connector* declared to be capable of multi-carrier operation the measurement is performed on one of the carriers under test. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.5.4.5 UTRA TDD method of test + +##### 6.5.4.5.1 Initial conditions + +Test environment: normal; see annex B.2. + +RF channels to be tested for single carrier: B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* position to be tested: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ single-band operation, see clause 4.12.1 single-band operation. + +**Table 6.5.4.5.1-1: Parameters of the *TAB connector* transmitted signal for modulation accuracy testing at maximum *TAB connector* output power for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-------------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS $i$ ; $i = 0, 1, 2, \dots, 6$ :
Transmit, if $i$ is 0,4,5,6;
receive, if $i$ is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 10 | +| Power of each DPCH | 1/10 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +In addition the following test set up only applies for 16QAM capable BS. + +**Table 6.5.4.5.1-2: Parameters of the *TAB connector* transmitted signal for modulation accuracy testing at maximum *TAB connector* output power setting for 1,28 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS $i$ ; $i = 0, 1, 2, 3, 4, 5, 6$ :
transmit, if $i$ is 0,4,5,6;
receive, if $i$ is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 10 | +| Power of each HS-PDSCH | 1/10 of Base Station output power | +| Data content of HS-PDSCH | Real life (sufficient irregular) | +| Spreading factor | 16 | + +## 6.5.4.5.2 Procedure + +### 6.5.4.5.2.1 EVM procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) For a *TAB connector* declared to be capable of single carrier operation only, set the parameters of the *TAB connector* transmitted signal according to table 6.5.4.5.1-1 at manufacturer's declared output power, $P_{\text{Rated,c,TABC}}$ . + +For a *TAB connector* declared to be capable of multi-carrier operation, set the *TAB connector* to transmit according to table 6.5.4.5.1-1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 5.3. + +- 2) Measure the error vector magnitude (EVM) for each carrier by applying the global in-channel Tx test method described in annex E with the *TAB connector* transmitted signal set as described in table 6.5.4.5.1-1. +- 3) Measure the error vector magnitude (EVM) for each carrier by applying the global in-channel Tx test method described in annex C with the *TAB connector* transmitted signal on each carrier set as described in table 6.5.4.5.2.1-1. +- 4) For *TAB connector* declared to be capable of 16QAM repeat steps 2 and 3 using transmitted signal set as described in tables 6.5.4.5.1-2 and 6.5.4.5.2.1-2. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +**Table 6.5.4.5.2.1-1: Parameters of the *TAB connector* transmitted signal for modulation accuracy testing at minimum *TAB connector* output power for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-------------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS $i$ ; $i = 0, 1, 2, \dots, 6$ :
Transmit, if $i$ is 0,4,5,6;
receive, if $i$ is 1,2,3. | +| Time slot under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| BS output power setting on each carrier | Maximum output power - 30 dB | +| Data content of DPCH | Real life
(sufficient irregular) | + +**Table 6.5.4.5.2.1-2: Parameters of the *TAB connector* transmitted signal for modulation accuracy testing at minimum *TAB connector* output power setting for 1,28 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| HS-PDSCH modulation | 16QAM | +| Time slots under test | TS4, TS5 and TS6 | +| Number of HS-PDSCH in each time slot under test | 1 | +| BS output power setting on each carrier | Maximum output power - 30 dB | +| Data content of HS-PDSCH | Real life
(sufficient irregular) | +| Spreading factor | 16 | + +#### 6.5.4.5.2.2 PCDE procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) For a *TAB connector* declared to be capable of single carrier operation only, set the parameters of the *TAB connector* transmitted signal according to table 6.5.4.5.2.1-1 at manufacturer's declared output power, $P_{\text{Rated,c,TABC}}$ . + +For a *TAB connector* declared to be capable of multi-carrier operation, set the *TAB connector* to transmit according to table 6.5.4.5.2.1-1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 5.3. + +- 2) Measure the Peak code domain error by applying the global in-channel Tx test method described in annex E. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.5.4.5.2.3 RCDE procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) For a *TAB connector* declared to be capable of single carrier operation only, set the parameters of the *TAB connector* transmitted signal according to table 6.5.4.5.2.1-1 at manufacturer's declared output power, $P_{\text{Rated,c,TABC}}$ . + +For a *TAB connector* declared to be capable of multi-carrier operation, set the *TAB connector* to transmit according to table 6.5.4.5.2.1-1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 5.3. + +- 2) Measure the Relative code domain error by applying the global in-channel Tx test method described in annex E. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.5.4.6 E-UTRA and NR method of test + +#### 6.5.4.6.1 Initial conditions + +Test environment: normal; see annex B.2. + +RF channels to be tested for single carrier: B, M and T; see clause 4.12.1. + +RF bandwidth positions to be tested for multi-carrier and/or CA: + +- $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single-band operation, see clause 4.12.1; +- $B_{\text{RFBW\_T}'_{\text{RFBW}}}$ and $B'_{\text{RFBW\_T}'_{\text{RFBW}}}$ in multi-band operation, see clause 4.12.1. + +#### 6.5.4.6.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) For a *TAB connector* declared to be capable of single carrier operation only, set the *TAB connector* to transmit a signal according to E-TM 3.1 for E-UTRA (or sE-TM3.1-1 for subslot TTI, or sE-TM3.1-2 for slot TTI). For NR, procedure described in TS 38.141-1 [37] in clause 6.5.3.4.2 shall be used. + +For a *TAB connector* declared to be capable of multi-carrier and/or CA operation, set the *TAB connector* to transmit according to E-TM3.1 for E-UTRA (or sE-TM3.1-1 for subslot TTI, or sE-TM3.1-2 for slot TTI) on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.10 and 4.11. For NR, procedure described in TS 38.141-1 [37] in clause 6.5.3.4.2 shall be used. + +- 2) Measure the EVM and frequency error as defined in annex F. +- 3) Repeat steps 1 and 2 for the following test models: + - For E-UTRA: repeat steps 1 and 2 for E-TM 3.2, E-TM 3.3 and E-TM 2, + - For E-UTRA with subslot TTI: repeat steps 1 and 2 for sE-TM3.2-1, sE-TM3.3-1 and sE-TM2-1, + - For E-UTRA with slot TTI: repeat steps 1 and 2 for sE-TM3.2-2, sE-TM3.3-2 and sE-TM2-2. + +If 256QAM is supported by BS: + +- For E-UTRA: repeat steps 1 and 2 for E-TM3.1a and E-TM2a, +- For E-UTRA with subslot TTI: repeat steps 1 and 2 for sE-TM3.1a-1 and sE-TM2a-1, +- For E-UTRA with slot TTI: repeat steps 1 and 2 for sE-TM3.1a-2 and sE-TM2a-2. + +For E-UTRA test model E-TM2 and E-TM2a the OFDM symbol power shall be at the lower limit of the dynamic range according to the test procedure in clause 6.3.4.4.2 and test requirements in clause 6.3.4.5.2. + +For subslot TTI test model sE-TM2-1 and sE-TM2a-1 (or for sE-TM2-2 and sE-TM2a-2 for slot TTI) the OFDM symbol power shall be at the lower limit of the dynamic range according to the test procedure in clause 6.3.4.4.2 and test requirements in clause 6.3.4.5.2. + +If 1024QAM is supported by BS: + +- For E-UTRA: repeat steps 1 and 2 for E-TM3.1b and E-TM2b. +- For NR: repeat steps 1 and 2 for NR-FR1-TM3.1b and NR-FR1-TM2b. + +For 1024QAM test model E-TM2b and NR-FR1-TM2b the OFDM symbol power shall be at the lower limit of the dynamic range according to the test procedure in clause 6.3.4.4.2.3 and test requirements in clause 6.3.4.5.2. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 6.5.4.7 Test Requirements + +### 6.5.4.7.1 UTRA FDD test requirement + +The Error Vector Magnitude for each UTRA carrier and every measured slot shall be less than 17.5 % when the *TAB connector* is transmitting a composite signal using only QPSK modulation and shall be less than 12.5 % when the *TAB connector* is transmitting a composite signal that includes 16QAM modulation. + +The peak code domain error for every measured slot shall not exceed -32 dB at spreading factor 256. + +The average Relative Code Domain Error for 64QAM modulated codes shall not exceed -20 dB at spreading factor 16. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.5.4.7.2 UTRA TDD test requirement + +The error vector magnitude (EVM) for each carrier measured according to clause 6.5.4.5.2.1 shall not exceed 12.5 %. + +The peak code domain error measured according to clause 6.5.4.5.2.2 shall not exceed -27 dB. + +The Relative code domain error measured according to clause 6.5.4.5.2.3 shall not exceed -20.9 dB. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.5.4.7.3 E-UTRA and NR test requirement + +The EVM of each E-UTRA carrier for different modulation schemes on PDSCH or sPDSCH shall be less than the limits in table 6.5.4.7.3-1. + +The EVM of each NR carrier for different modulation schemes on PDSCH shall be less than the limits in table 6.5.4.7.3-1a. + +**Table 6.5.4.7.3-1 EVM requirements for E-UTRA** + +| Modulation scheme for PDSCH | Required EVM (%) | +|-----------------------------|------------------| +| QPSK | 18.5 | +| 16QAM | 13.5 | +| 64QAM | 9 | +| 256QAM | 4.5 | +| 1024QAM | 3.5 | + +**Table 6.5.4.7.3-1a EVM: requirements for NR** + +| Modulation scheme for PDSCH | Required EVM (%) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| QPSK | 18.5 | +| 16QAM | 13.5 | +| 64QAM | 9 | +| 256QAM | 4.5 | +| 1024QAM | 3.5 % 1
3.8 % 2 | +| NOTE 1: This requirement is applicable for frequencies equal to or below 4.2 GHz.
NOTE 2: This requirement is applicable for frequencies above 4.2 GHz. | | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +The EVM requirement shall be applicable within a time period around the centre of the CP therefore the EVM requirement is tested against the maximum of the RMS average of 10 subframes at the two window W extremities. + +For E-UTRA, the EVM window length (W) for normal CP and extended CP is specified in TS 36.104 [4], annex E.5.1. + +**Table 6.5.4.7.3-2 Void** + +For NR, the EVM window length (W) for normal CP and extended CP is specified in TS 38.104 [36], annex B.5.2. + +## 6.6 Unwanted Emissions + +### 6.6.1 General + +Unwanted emissions consist of so-called out-of-band emissions and spurious emissions according to ITU definitions [14]. In ITU terminology, 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. 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. + +For AAS BS in *single RAT E-UTRA operation* and *MSR operation*, the out-of-band emissions requirement for the AAS BS transmitter is specified in terms of an operating band unwanted emissions requirement that defines limits for emissions in each supported *downlink operating band* plus the frequency ranges $\Delta f_{\text{OBUE}}$ above and $\Delta f_{\text{OBUE}}$ below each band, where $\Delta f_{\text{OBUE}}$ is the maximum offset of the operating band unwanted emission mask from the operating band edge. Emissions outside of this frequency range are limited by a spurious emissions requirement. For UTRA FDD single RAT AAS BS, the out of band emission requirement for AAS BS transmitter is specified in terms of spectrum emission mask requirement. + +The values of $\Delta f_{\text{OBUE}}$ are defined for *hybrid AAS BS* for E-UTRA and UTRA operating bands in Table 6.6.1-1. + +**Table 6.6.1-1: Maximum offset of OBUE outside the downlink operating band** + +| BS type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ [MHz] | +|----------------------|--------------------------------------------------------------------------------------|--------------------------------| +| Hybrid AAS BS | $F_{\text{DL\_high}} - F_{\text{DL\_low}} < 100 \text{ MHz}$ | 10 | +| | $100 \text{ MHz} \leq F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 900 \text{ MHz}$ | 40 | + +The unwanted emission level limit of a *TAB connector TX min cell group* is in general defined by the unwanted emission *basic limit* which is the same as the corresponding applicable *Non-AAS BS* per transmitter requirement specified in [2], [3], [4] or [5], and its scaling by $N_{\text{TXU, counted per cell}}$ . The unwanted emission requirements are applied per the *TAB connector TX min cell groups* for all the configurations supported by the AAS BS. The *basic limits* and corresponding scaling are defined in each relevant clause. + +There are in addition a requirement for occupied bandwidth and an ACLR requirement. + +### 6.6.2 Occupied bandwidth + +#### 6.6.2.1 Definition and applicability + +The occupied bandwidth is the width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage $\beta/2$ of the total mean transmitted power. See also Recommendation ITU-R SM.328 [17]. + +The value of $\beta/2$ shall be taken as 0.5%. + +The occupied bandwidth requirement applies during the *transmitter ON period* for a single transmitted carrier. The minimum requirement below may be applied regionally. There may also be regional requirements to declare the occupied bandwidth according to the definition in the present clause. + +### 6.6.2.2 Minimum requirement + +For MSR AAS BS, the minimum requirement for occupied bandwidth is the same as that stated in TS 37.104 [12], clause 6.6.3. + +For single RAT UTRA FDD AAS BS, the minimum requirement for occupied bandwidth is the same as that stated in TS 25.104 [9], clause 6.6.1. + +For single RAT UTRA TDD, 1,28Mcps option AAS BS, the minimum requirement for occupied bandwidth is the same as that stated in TS 25.105 [10], clause 6.6.1. + +For single RAT E-UTRA AAS BS, the minimum requirement for occupied bandwidth is the same as that stated in TS 36.104 [11], clause 6.6.1. + +### 6.6.2.3 Test purpose + +The test purpose is to verify that the emission of the *TAB connector* does not occupy an excessive bandwidth for the service to be provided and is, therefore, not likely to create interference to other users of the spectrum beyond undue limits. + +### 6.6.2.4 Method of test + +#### 6.6.2.4.1 Initial conditions + +##### 6.6.2.4.1.1 General test conditions + +Test environment: + +- normal; see clause B.2. + +RF channels to be tested: + +- M; see clause 4.12.1. + +##### 6.6.2.4.1.2 UTRA FDD + +Set the *TAB connector* to transmit a signal in accordance to TM1, clause 4.12.2. + +##### 6.6.2.4.1.3 UTRA TDD + +Set the parameters of the BS transmitted signal according to table 6.6.2.4.1.3-1. + +**Table 6.6.2.4.1.3-1: Parameters of the *TAB connector* transmitted signal for occupied bandwidth testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| 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) | + +##### 6.6.2.4.1.4 E-UTRA and NR + +Aggregated Channel Bandwidth positions to be tested for contiguous carrier aggregation: + +- BBW Channel CA, MBW Channel CA and TBW Channel CA; see clause 4.12.1. + +For a AAS BS declared to be capable of single carrier operation, start transmission according to E- TM1.1 for E-UTRA or [NR-FR1-TM 1.1] for NR, clause 4.12.2. + +#### 6.6.2.4.2 Procedure + +##### 6.6.2.4.2.1 General Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. +- 2) For UTRA and E-UTRA and NR declared capable of single carrier operation set the *TAB connector* to transmit at manufacturers declared rated carrier output power per *TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). + +For E-UTRA and NR declared capable of contiguous carrier aggregation operation set the *TAB connector* to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 5. + +##### 6.6.2.4.2.2 UTRA FDD + +- 1) Measure the spectrum of the transmitted signal across a span of 10 MHz, based on an occupied bandwidth requirement of 5 MHz. The selected resolution bandwidth (RBW) filter of the analyser shall be 30 kHz or less. The spectrum shall be measured at 400 or more points across the measurement span. + +NOTE: The detection mode of the spectrum analyzer will not have any effect on the result if the statistical properties of the out-of-OBW power are the same as those of the inside-OBW power. Both are expected to have the Rayleigh distribution of the amplitude of Gaussian noise. In any case where the statistics are not the same, though, the detection mode is power responding. There are at least two ways to be power responding. The spectrum analyser can be set to "sample" detection, with its video bandwidth setting at least three times its RBW setting. Or the analyser may be set to respond to the average of the power (root-mean-square of the voltage) across the measurement cell. + +- 2) Compute the total of the power, $P_0$ , (in power units, not decibel units) of all the measurement cells in the measurement span. Compute $P_1$ , the power outside the occupied bandwidth on each side. $P_1$ is half of the total power outside the bandwidth. $P_1$ is half of $(100 \% - (\text{occupied percentage}))$ of $P_0$ . For the occupied percentage of 99 %, $P_1$ is 0.005 times $P_0$ . +- 3) Determine the lowest frequency, $f_1$ , for which the sum of all power in the measurement cells from the beginning of the span to $f_1$ exceeds $P_1$ . +- 4) Determine the highest frequency, $f_2$ , for which the sum of all power in the measurement cells from the end of the span to $f_2$ exceeds $P_1$ . +- 5) Compute the occupied bandwidth as $f_2 - f_1$ . + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +##### 6.6.2.4.2.3 UTRA TDD + +- 1) Measure the power of the transmitted signal with a measurement filter of bandwidth 30 kHz. The characteristic of the filter shall be approximately Gaussian (typical spectrum analyser filter). The centre frequency of the filter shall be stepped in contiguous 30 kHz steps from a minimum frequency, which shall be $(2,4 - 0,015)$ MHz below the assigned channel frequency of the transmitted signal, up to a maximum frequency, which shall be $(2,4 - 0,015)$ MHz above the assigned channel frequency of the transmitted signal. The time duration of each step shall be sufficiently long to capture one active time slot. The measured power shall be recorded for each step. +- 2) Determine the total output power by accumulating the recorded power measurement results of all steps. + +- 3) Sum up the recorded power measurement results, starting from the step at the minimum frequency defined in (3) up to the step at a lower limit frequency by which this sum is equal to or greater than 0,5 % of the total output power determined in (4). This limit frequency is recorded as "Lower Frequency". +- 4) Sum up the recorded power measurement results, starting from the step at the maximum frequency defined in (3) down to the step at an upper limit frequency by which this sum is equal to or greater than 0,5 % of the total output power determined in (4). This limit frequency is recorded as "Upper Frequency". +- 5) Calculate the occupied bandwidth as the difference between the "Upper Frequency" obtained in (5) and the "Lower Frequency" obtained in (6). + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.6.2.4.2.4 E-UTRA and NR + +- 1) Measure the spectrum emission of the transmitted signal using at least the number of measurement points, and across a span, as listed in table 6.6.2.4.2.4-1 for E-UTRA and 6.6.2.4.2.4-2 for NR. The selected resolution bandwidth (RBW) filter of the analyser shall be 30 kHz or less. + +**Table 6.6.2.4.2.4-1: Span and number of measurement points for OBW measurements** + +| Bandwidth | E-UTRA channel bandwidth
$BW_{Channel}$ (MHz) | | | | | | Aggregated channel
bandwidth $BW_{Channel\_CA}$
(MHz) | +|--------------------------------------|--------------------------------------------------|-----|-----|-----|-----|-----|-------------------------------------------------------------| +| | 1.4 | 3 | 5 | 10 | 15 | 20 | > 20 | +| Span (MHz) | 10 | 10 | 10 | 20 | 30 | 40 | $2 \times BW_{Channel\_CA}$ | +| Minimum number of measurement points | 1429 | 667 | 400 | 400 | 400 | 400 | $\frac{2 \times BW_{Channel\_CA}}{100kHz}$ | + +**Table 6.6.2.4.2.4-2: Span and number of measurement points for OBW measurements for NR** + +| Bandwidth | BS channel bandwidth
$BW_{Channel}$ (MHz) | | | | | Aggregated BS channel
bandwidth $BW_{Channel\_CA}$ (MHz) | +|--------------------------------------|----------------------------------------------|-----|-----|-----|-----------------------------------|-------------------------------------------------------------| +| | 5 | 10 | 15 | 20 | > 20 | > 20 | +| Span (MHz) | 10 | 20 | 30 | 40 | $2 \times BW_{Channel}$ | $2 \times BW_{Channel\_CA}$ | +| Minimum number of measurement points | 400 | 400 | 400 | 400 | $\frac{2 \times BW_{Channel}}{T}$ | $\frac{2 \times BW_{Channel\_CA}}{T}$ | + +[NOTE 1: T = 200 kHz, when the BS channel bandwidth of outermost carriers are both larger than 50 MHz; Otherwise, T = 100 kHz.] + +NOTE: The detection mode of the spectrum analyzer will not have any effect on the result if the statistical properties of the out-of-OBW power are the same as those of the inside-OBW power. Both are expected to have the Rayleigh distribution of the amplitude of Gaussian noise. In any case where the statistics are not the same, though, the detection mode is power responding. The analyser may be set to respond to the average of the power (root-mean-square of the voltage) across the measurement cell. + +- 2) Compute the total of the power, P0, (in power units, not decibel units) of all the measurement cells in the measurement span. Compute P1, the power outside the occupied bandwidth on each side. P1 is half of the total power outside the bandwidth. P1 is half of (100 % - (occupied percentage)) of P0. For the occupied percentage of 99 %, P1 is 0.005 times P0. +- 3) Determine the lowest frequency, f1, for which the sum of all power in the measurement cells from the beginning of the span to f1 exceeds P1. + +- 4) Determine the highest frequency, $f_2$ , for which the sum of all power in the measurement cells from $f_2$ to the end of the span exceeds $P_1$ . +- 5) Compute the occupied bandwidth as $f_2 - f_1$ . + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 6.6.2.5 Test requirements + +### 6.6.2.5.1 MSR + +The occupied bandwidth of a single carrier shall be less than the values listed in table 6.6.2.5.1-1. In addition, for E-UTRA and NR intra-band contiguous carrier aggregation, test requirement in clause 6.6.1.5 of TS 36.141 [17] or clause 6.6.2.5 of TS 38.141-1 [37] applies for the E-UTRA or NR component carriers that are aggregated. + +**Table 6.6.2.5.1-1: Occupied bandwidth** + +| RAT | Occupied bandwidth limit | +|--------------------|--------------------------| +| E-UTRA and NR | $BW_{\text{Channel}}$ | +| UTRA FDD | 5 MHz | +| 1.28 Mcps UTRA TDD | 1.6 MHz | + +### 6.6.2.5.2 UTRA FDD + +The occupied bandwidth shall be less than 5 MHz based on a chip rate of 3,84 Mcps. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.6.2.5.3 UTRA TDD + +The occupied bandwidth shall be less than 1,6 MHz. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.6.2.5.4 E-UTRA + +The occupied bandwidth for each E-UTRA carrier shall be less than the channel bandwidth. For contiguous CA, the occupied bandwidth shall be less than or equal to the Aggregated Channel Bandwidth as defined in TS 36.141 [17] clause 5.6. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.6.3 Adjacent Channel Leakage power Ratio + +### 6.6.3.1 Definition and applicability + +Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. + +NOTE: Conformance to the AAS ACLR requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The ratio of the sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the assigned channel frequency to the sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the adjacent channel frequency shall be greater than or equal to the AAS ACLR limit. This applies for each *TAB connector TX min cell group*. + +Or + +- 2) The ratio of the filtered mean power at the *TAB connector* centred on the assigned channel frequency to the filtered mean power at each *TAB connector* centred on the adjacent channel frequency shall be greater than or equal to the AAS limit for every *TAB connector* in the *TAB connector TX min cell group*, for each *TAB connector TX min cell group*. + +### 6.6.3.2 Minimum requirement + +For MSR operation the AAS BS minimum requirements are the same as those specified in TS 37.105 [8], clause 6.6.3.2. + +For single RAT UTRA FDD operation, the AAS BS minimum requirements are the same as those specified in TS 25.104 [9], clauses 6.6.2.2.1 and 6.6.2.2.2. + +For single RAT UTRA TDD 1,28 Mcps option operation, the AAS BS minimum requirements are the same as those specified in TS 25.105 [10], clause 6.6.2.2. + +For *single RAT E-UTRA operation*, the AAS BS minimum requirements are the same as those specified in TS 36.104 [11], clauses 6.6.2.1 and 6.6.2.2. + +### 6.6.3.3 Test purpose + +To verify that the adjacent channel leakage power ratio requirement shall be met as specified by the minimum requirement. + +### 6.6.3.4 Method of test + +#### 6.6.3.4.1 Initial conditions + +##### 6.6.3.4.1.1 General test conditions + +Test environment: + +- normal; see clause B.2. + +RF channels to be tested for single carrier: + +- B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single-band operation; see clause 4.12.1; $B'_{RFBW}$ , $T'_{RFBW}$ and $B'_{RFBW}$ , $T'_{RFBW}$ in multi-band operation, see clause 4.12.1. + +#### 6.6.3.4.1.2 MSR + +For E-UTRA and NR ACLR requirement outside the *Base Station RF Bandwidth edges* and the ACLR requirement applied inside sub-block gap, in addition, for non-contiguous spectrum operation or *Inter RF Bandwidth gap* for multi-band operation using, the test configurations defined in clause 4.8, the method of test described in clauses 6.6.4.4.1 and 6.6.4.4.2 applies. + +#### 6.6.3.4.1.3 UTRA FDD + +Set the base station to transmit a signal modulated in accordance to TM1, in clause 4.12.2. + +For a *TAB connector* declared to be capable of multi-carrier operation, set the base station to transmit according to TM1 on all carriers configured + +#### 6.6.3.4.1.4 UTRA TDD + +For a *TAB connector* declared to be capable of single carrier operation only, set the parameters of the transmitted signal according to table 6.6.3.4.1.4-1. + +For a *TAB connector* declared to be capable of multi-carrier operation set the parameters of the transmitted signal according to table 6.6.3.4.1.4-1 on all carriers. + +**Table 6.6.3.4.1.4-1: Parameters of the transmitted signal for ACLR testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| 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) | + +For a *TAB connector* declared capable of supporting 16QAM capable. + +For a *TAB connector* declared to be capable of single carrier operation only, set the parameters of the transmitted signal according to table 6.6.3.4.1.4-2. + +For a *TAB connector* declared to be capable of multi-carrier operation, set the parameters of the transmitted signal according to table 6.6.3.4.1.4-2 on all carriers. + +**Table 6.6.3.4.1.4-2: Parameters of the transmitted signal for ACLR testing for 1,28 Mcps TDD- 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 8 | +| Power of each HS-PDSCH | 1/8 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.6.3.4.1.3 E-UTRA + +For a *TAB connector* declared to be capable of single carrier operation only set to transmit a signal according to E-TM1.1. in clause 4.12.2. + +For a *TAB connector* declared to be capable of multi-carrier and/or CA operation, set to transmit according to E-TM1.1 on all carriers configured. + +#### 6.6.3.4.2 Procedure + +##### 6.6.3.4.2.1 General procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. + +The measurement device characteristics shall be: + +- measurement filter bandwidth: defined in clause 6.6.3.5; +- detection mode: true RMS voltage or true average power. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 2) For single carrier operation set the *TAB connector* to transmit at manufacturers declared rated carrier output power per *TAB connector* ( $P_{\text{Rated,c,TABC}}$ ). + +For a *TAB connector* declared to be capable of multi-carrier and/or CA operation set the *TAB connector* to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 5 using the corresponding test models or set of physical channels in clause 4.12. + +##### 6.6.3.4.2.2 MSR + +- 1) For E-UTRA and NR, measure ACLR: + - outside the Base Station RF Bandwidth edges; + - inside sub-block gap for non-contiguous spectrum operation as specified in clause 6.6.4.5.1; + - inside Inter RF Bandwidth gap for multi-band operation. +- 2) For UTRA FDD, measure ACLR inside sub-block gap or Inter RF Bandwidth gap as specified in clause 6.6.4.5.2. +- 3) Measure Cumulative Adjacent Channel Leakage power Ratio (CACLR) inside sub-block gap or the *Inter RF Bandwidth gap* as specified in clause 6.6.4.5.4. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +##### 6.6.3.4.2.3 UTRA FDD + +- 1) Measure Adjacent channel leakage power ratio for 5 MHz and 10 MHz offsets both side of channel frequency. In multiple carrier case only offset frequencies below the lowest and above the highest carrier frequency used shall be measured. +- 2) For the ACLR requirement applied inside sub-block gap for non-contiguous spectrum operation or inside *Inter RF Bandwidth gap* for multi-band operation: + - a) Measure ACLR inside sub-block gap or *Inter RF Bandwidth gap* as specified in clause 6.6.3.5.4.1, if applicable. + - b) Measure Cumulative Adjacent Channel Leakage power Ratio (CACLR) inside sub-block gap or *Inter RF Bandwidth gap* as specified in clause 6.6.3.5.4.2, if applicable. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.6.3.4.2.4 UTRA TDD 1,28Mcps option + +- 1) Measure the RRC filtered mean power centred on the lowest assigned channel frequency of a operating band over the 848 active chips of the transmit time slots TS i (this excludes the guard period). +- 2) Average over at least one time slot. +- 3) Measure the RRC filtered mean power at the first lower adjacent RF channel (centre frequency 1,6 MHz below the lowest assigned channel frequency of the transmitted signal) over the useful part of the burst within the transmit time slots TS i (this excludes the guard period). +- 4) Average over at least one time slot. +- 5) Calculate the ACLR by the ratio: + +$$\text{ACLR} = \text{average power acc. to (4)} / \text{average interference power acc. to (6)}.$$ + +- 6) Repeat steps (5), (6) and (7) for the second lower adjacent RF channel (centre frequency 3,2 MHz below the lowest assigned channel frequency of the transmitted signal) and also for the first and second upper adjacent RF channel (centre frequency 1,6 MHz and 3,2 MHz above the assigned channel frequency of the transmitted signal, respectively). +- 7) In case of a *multi-carrier TAB connector*, repeat steps (3) and (4) for the highest assigned channel frequency. Otherwise, use the result obtained in step (4) above for further calculation in step (12). +- 8) Measure the RRC filtered mean power at the first higher adjacent RF channel (centre frequency 1,6 MHz above the highest assigned channel frequency of the transmitted signal) over the useful part of the burst within the transmit time slots TS i (this excludes the guard period). +- 9) Average over at least one time slot. +- 10) Calculate the ACLR by the ratio + +$$\text{ACLR} = \text{average power acc. to (9)} / \text{average interference power acc. to (11)}.$$ + +- 11) Repeat steps (10) to (12) for the second upper adjacent RF channel (centre frequency 3,2 MHz above the highest assigned channel frequency of the transmitted signal). + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 12) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +In addition for a 16QAM capable TAB connector + +The same procedure applies to 1,28 Mcps TDD option supporting 16QAM. + +#### 6.6.3.4.2.5 E-UTRA + +- 1) Measure Adjacent channel leakage power ratio for the frequency offsets both side of channel frequency as specified in table 6.6.3.5.6.1-1 (Paired spectrum case) or Table 6.6.3.5.6.1-2 (Unpaired spectrum case) respectively. In multiple carrier case only offset frequencies below the lowest and above the highest carrier frequency used shall be measured. +- 2) For the ACLR requirement applied inside sub-block gap for non-contiguous spectrum operation: or inside *Inter RF Bandwidth gap* for multi-band operation: + - a) Measure ACLR inside sub-block gap or *Inter RF Bandwidth gap* as specified in clause 6.6.3.5.6.1, if applicable. + - b) Measure CACLR inside sub-block gap or *Inter RF Bandwidth gap* as specified in clause 6.6.3.5.6.2, if applicable. + +- 3) Repeat the test with the channel set-up according to E- TM1.2 in clause 4.12.2. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.6.3.5 Test requirements + +#### 6.6.3.5.1 General Requirements + +For the ACLR requirement either the ACLR/CACLR limits in clauses 6.6.3.5.3, 6.6.3.5.4, 6.6.3.5.5 and 6.6.3.5.6, or the absolute limit in clause 6.6.3.5.2 shall apply, whichever is less stringent. + +Conformance to the relative ACLR/CACLR requirement may be shown to either the measure and sum test requirement or the per *TAB connector* test requirement. + +- 1) The relative ACLR/CACLR test requirements for an AAS BS when using the measure and sum alternative are that for each *TAB connector TX cell group* and each applicable limit, the ratio of the power summation of wanted signal at the *TAB connectors* of the *TAB connector TX cell group* to the power sum of the emissions at the *TAB connectors* of the *TAB connector TX cell group* shall not exceed the limit. +- 2) The relative ACLR/CACLR test requirements for an AAS BS when using the per *TAB connector* alternative are that for each *TAB connector TX cell group* and each applicable limit, ratio of the wanted signal to the emissions at each of the *TAB connectors* of the *TAB connector TX cell group* shall not exceed the limit. + +#### 6.6.3.5.2 Absolute Limits + +The absolute limits apply for ACLR and CACLR. + +Conformance may be shown to either the measure and sum test requirement or the per *TAB connector* test requirement. + +- 1) The ACLR/CACLR test requirements for an AAS BS when using the measure and sum alternative are that for each *TAB connector TX cell group* and each applicable absolute *basic limit* as specified in this clause, the power summation of emissions at the *TAB connectors* of the *TAB connector TX cell group* shall not exceed the specified absolute *basic limit* + $10\log_{10}(N_{\text{TXU, countedpercell}})$ . +- 2) The ACLR/CACLR test requirements for an AAS BS when using the per *TAB connector* alternative are that for each *TAB connector TX cell group* and each applicable absolute *basic limit* as specified in this clause, the emissions at each of the *TAB connectors* of the *TAB connector TX cell group* shall not exceed the specified absolute *basic limit* + $10\log_{10}(N_{\text{TXU, countedpercell}}) - 10\log_{10}(n)$ where $n$ is the number of *TAB connectors* in the *TAB connector TX cell group*. + +The basic limit for the ACLR/CACLR absolute value is specified in table 6.6.3.5.2-1. + +**Table 6.6.3.5.2-1: Base station ACLR/CACLR absolute basic limit** + +| BS category / BS class | ACLR/CACLR absolute basic limit | +|-------------------------|---------------------------------| +| Category A Wide Area BS | -13 dBm/MHz | +| Category B Wide Area BS | -15 dBm/MHz | +| Medium Range BS | -25 dBm/MHz | +| Local Area BS | -32 dBm/MHz | + +#### 6.6.3.5.3 MSR + +##### 6.6.3.5.3.1 MSR E-UTRA test requirement + +For E-UTRA, the test requirement is specified in tables 6.6.3.5.3.1-1 and 6.6.3.5.3.1-2, and applies outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. + +For a *TAB connector* operating in non-contiguous spectrum, the ACLR also applies for the first adjacent channel inside any sub-blockgap with a gap size $W_{\text{gap}} \geq 15$ MHz. The ACLR requirement for the second adjacent channel applies + +inside any sub-block gap with a gap size $W_{\text{gap}} \geq 20$ MHz. The CACLR test requirement in clause 6.6.3.5.6.2 applies in sub block gaps for the frequency ranges defined in table 6.6.3.5.6.2-1. + +For a *multi-band TAB connector*, the ACLR also applies for the first adjacent channel inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 15$ MHz. The ACLR requirement for the second adjacent channel applies inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 20$ MHz. The CACLR requirement in clause 6.6.3.5.6.2 applies in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.5.6.2-1. + +The requirement applies during the transmitter on period. + +The ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal ( $BW_{\text{Config}}$ ) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +For operation in paired spectrum, the ACLR shall be higher than the value specified in table 6.6.3.5.3.1-1. + +**Table 6.6.3.5.3.1-1: Base Station ACLR in paired spectrum** + +| Channel bandwidth of E-UTRA Lowest/Highest Carrier transmitted $BW_{\text{Channel}}$ (MHz) | adjacent channel centre frequency offset below the lower or above the upper Base Station RF Bandwidth edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|--------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| 1.4, 3.0, 5, 10, 15, 20 | $0.5 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | $1.5 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | + +NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{Config}}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +For operation in unpaired spectrum, the ACLR shall be higher than the value specified in table 6.6.3.5.3.1-2. + +**Table 6.6.3.5.3.1-2: Base Station ACLR in unpaired spectrum with synchronized operation** + +| Channel bandwidth of E-UTRA Lowest/Highest Carrier transmitted $BW_{\text{Channel}}$ (MHz) | adjacent channel centre frequency offset below the lower or above the upper Base Station RF Bandwidth edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|--------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| 1.4, 3 | $0.5 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | $1.5 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | 0.8 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| | 2.4 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| 5, 10, 15, 20 | $0.5 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | $1.5 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | 0.8 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| | 2.4 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| | 5 MHz | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 44.2 dB | +| | 15 MHz | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 44.2 dB | + +NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{Config}}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.105 [3], with a chip rate as defined in this table. + +For operation in non-contiguous paired spectrum, the ACLR shall be higher than the value specified in table 6.6.3.5.3.1-3. + +**Table 6.6.3.5.3.1-3: Base Station ACLR in non-contiguous paired spectrum** + +| Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies | adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| $W_{\text{gap}} \geq 15$ MHz | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| $W_{\text{gap}} \geq 20$ MHz | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| NOTE: | The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | | | + +For operation in non-contiguous unpaired spectrum, the ACLR shall be higher than the value specified in table 6.6.3.5.3.1-4. + +**Table 6.6.3.5.3.1-4: Base Station ACLR in non-contiguous unpaired spectrum** + +| Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| $W_{\text{gap}} \geq 15$ MHz | 2.5 MHz | 5 MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| $W_{\text{gap}} \geq 20$ MHz | 7.5 MHz | 5 MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | + +#### 6.6.3.5.3.1A NR test requirement + +For NR, the test requirement is specified in tables 6.6.3.5.3.1A-1 and applies outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. + +For a *TAB connector* operating in non-contiguous spectrum, the ACLR also applies for the first adjacent channel inside any sub-block gap with a gap size as indicated in table 6.6.3.5.3.1A-2. The ACLR requirement for the second adjacent channel applies inside any sub-block gap with a gap size as indicated in table 6.6.3.5.3.1A-2. The CACLR test requirement in clause 6.6.3.5.3.4 applies in sub block gaps for the frequency ranges defined in table 6.6.3.5.3.4-2. + +For a *multi-band TAB connector*, the ACLR also applies for the first adjacent channel inside any *Inter RF Bandwidth gap* with a gap size as indicated in table 6.6.3.5.3.1A-2. The ACLR requirement for the second adjacent channel applies inside any *Inter RF Bandwidth gap* with a gap size as indicated in table 6.6.3.5.3.1A-2. The CACLR test requirement in clause 6.6.3.5.3.4 applies in sub block gaps for the frequency ranges defined in table 6.6.3.5.3.4-2. + +The requirement applies during the transmitter on period. + +The ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal ( $BW_{\text{Config}}$ ) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +For operation in paired or unpaired spectrum, the ACLR shall be higher than the value specified in table 6.6.3.5.3.1A-1. + +**Table 6.6.3.5.3.1A-1: Base Station ACLR limit** + +| BS channel bandwidth of lowest/highest NR carrier transmitted BW_{Channel} [MHz] | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 5, 10, 15, 20 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | +| | $2 \times BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | +| | $BW_{Channel}/2 + 2.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 44.2 dB (NOTE 3) | +| | $BW_{Channel}/2 + 7.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 44.2 dB (NOTE 3) | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 43.8 dB | +| | $2 \times BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 43.8 dB | +| | $BW_{Channel}/2 + 2.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 43.8 dB (NOTE 3) | +| | $BW_{Channel}/2 + 7.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 43.8 dB (NOTE 3) | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the BS channel bandwidth and transmission bandwidth configuration of the lowest/highest NR carrier transmitted on the assigned channel frequency. +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). +NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. + +For operation in non-contiguous paired or unpaired spectrum, the ACLR shall be higher than the value specified in table 6.6.3.5.3.1A-2. + +**Table 6.6.3.5.3.1A-2: Base Station ACLR limit in non-contiguous spectrum or multiple bands** + +| BS channel bandwidth of lowest/highest NR carrier transmitted BW_{Channel} [MHz] | Sub-block or Inter RF Bandwidth gap size (W_{gap}) where the limit applies [MHz] | BS adjacent channel centre frequency offset below or above the sub-block or Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 5, 10, 15, 20 | $W_{gap} \geq 15$ (Note 3)
$W_{gap} \geq 45$ (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | +| | $W_{gap} \geq 20$ (Note 3)
$W_{gap} \geq 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $W_{gap} \geq 60$ (Note 4)
$W_{gap} \geq 30$ (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 43.8 dB | +| | $W_{gap} \geq 80$ (Note 4)
$W_{gap} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | | | + +NOTE 1: $BW_{Config}$ is the transmission bandwidth configuration of the assumed adjacent channel carrier. +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). +NOTE 3: Applicable in case the BS channel bandwidth of the carrier transmitted at the other edge of the gap is 5, 10, 15, 20 MHz. +NOTE 4: Applicable in case the BS channel bandwidth of the NR carrier transmitted at the other edge of the gap is 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 MHz. + +## 6.6.3.5.3.2 + +## MSR UTRA FDD test requirement + +For UTRA FDD, the test requirement is specified in TS 25.141 [18], clause 6.5.2.2.5, and applies outside the Base Station RF Bandwidth or Maximum Radio Bandwidth. + +For a *TAB connector* operating in non-contiguous spectrum, ACLR requirement also applies for the first adjacent channel, inside any sub-block gap with a gap size $W_{\text{gap}} \geq 15$ MHz. The ACLR requirement for the second adjacent channel applies inside any sub-block gap with a gap size $W_{\text{gap}} \geq 20$ MHz. The CACLR test requirement in clause 6.6.3.5.6.2 applies in sub block gaps for the frequency ranges defined in table 6.6.3.5.6.2-1. + +For a *multi-band TAB connector* ACLR requirement also applies for the first adjacent channel, inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 15$ MHz. The ACLR requirement for the second adjacent channel applies inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 20$ MHz. The CACLR requirement in clause 6.6.3.5.6.2 applies in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.5.6.2-1. + +#### 6.6.3.5.3.3 MSR UTRA TDD test requirement + +For UTRA TDD, the test requirement is specified in clause 6.6.3.5.5, and applies outside the *Base Station RF Bandwidth* or Maximum Radio Bandwidth. + +#### 6.6.3.5.3.4 Cumulative ACLR requirement in non-contiguous spectrum + +The following test requirement applies for sub-block or *Inter RF Bandwidth gap* sizes listed in table 6.6.3.5.3.4-1 for UTRA FDD, UTRA TDD or E-UTRA operation or table 6.6.3.5.3.4-1A for NR operation: + +- Inside a sub-block gap within an operating band for a BS operating in non-contiguous spectrum. +- Inside an *Inter RF Bandwidth gap* for a BS operating in multiple bands, where multiple bands are mapped on the same antenna connector. + +The Cumulative Adjacent Channel Leakage power Ratio (CACLR) in a sub-block gap or the *Inter RF Bandwidth gap* is the ratio of: + +- a) the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the sub-block gap or the *Inter RF Bandwidth gap*; and +- b) the filtered mean power centred on a frequency channel adjacent to one of the respective sub-block edges or *Base Station RF Bandwidth edges*. + +The requirement applies to adjacent channels of E-UTRA or UTRA or NR carriers allocated adjacent to each side of the sub-block gap or the *Inter RF Bandwidth gap*. In case of mixed UTRA and E-UTRA (but not NR) carriers on either side of the gap, table 6.6.3.5.3.4-1 is applicable. In case of mixed NR and E-UTRA or UTRA or NR only carriers on either side of the gap, table 6.6.3.5.3.4-1A is applicable. The assumed filter for the adjacent channel frequency is defined in tables 6.6.3.5.3.4-1 and 6.6.3.5.3.4-1A and the filters on the assigned channels are defined in table 6.6.3.5.3.4-2. + +NOTE: If the RAT on the assigned channel frequencies is different, the filters used are also different. + +The CACLR for E-UTRA and UTRA carriers located on either side of the sub-block gap or the *Inter RF Bandwidth gap* shall be higher than the value specified in table 6.6.3.5.3.4-1. + +**Table 6.6.3.5.3.4-1: CACLR in non-contiguous spectrum or multiple bands for UTRA and E-UTRA only** + +| Band Category | Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|---------------|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------| +| BC1, BC2 | $5 \text{ MHz} \leq W_{\text{gap}} < 15 \text{ MHz}$ | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| BC1, BC2 | $10 \text{ MHz} \leq W_{\text{gap}} < 20 \text{ MHz}$ | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| BC3 | $5 \text{ MHz} \leq W_{\text{gap}} < 15 \text{ MHz}$ | 2.5 MHz | 5 MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| BC3 | $10 \text{ MHz} < W_{\text{gap}} < 20 \text{ MHz}$ | 7.5 MHz | 5 MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | + +NOTE: For BC1 and BC2 the RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +**Table 6.6.3.5.3.4-1A: CACLR in non-contiguous spectrum or multiple bands for E-UTRA and NR combinations** + +| BS channel bandwidth of NR carrier transmitted adjacent to sub-block gap or inter RF Bandwidth gap BW_{Channel} [MHz] | Sub-block or Inter RF Bandwidth gap size (W_{gap}) where the limit applies [MHz] | BS adjacent channel centre frequency offset below or above the sub-block or Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|--------------------| +| 5, 10, 15, 20 | $5 \leq W_{gap} < 15$ (Note 3)
$5 \leq W_{gap} < 45$ (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB | +| | $10 < W_{gap} < 20$ (Note 3)
$10 \leq W_{gap} < 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $20 \leq W_{gap} < 60$ (Note 4)
$20 \leq W_{gap} < 30$ (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 43.8 dB | +| | $40 < W_{gap} < 80$ (Note 4)
$40 \leq W_{gap} < 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | | | + +NOTE 1: $BW_{Config}$ is the transmission bandwidth configuration of the assumed adjacent channel carrier. +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). +NOTE 3: Applicable in case the *BS channel bandwidth* of the UTRA, E-UTRA or NR carrier transmitted at the other edge of the gap is 5, 10, 15, 20 MHz. +NOTE 4: Applicable in case the *BS channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 MHz + +**Table 6.6.3.5.3.4-2: Filter parameters for the assigned channel for UTRA, E-UTRA only combinations** + +| RAT of the carrier adjacent to the sub-block or Inter RF Bandwidth gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| E-UTRA | E-UTRA of same BW | +| UTRA FDD | RRC (3.84 Mcps) | + +NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +## 6.6.3.5.4 UTRA FDD + +### 6.6.3.5.4.1 ACLR + +The measurement result shall not be less than the ACLR limit specified in tables 6.6.3.5.4.1-1. + +**Table 6.6.3.5.4.1-1: BS ACLR** + +| BS channel offset below the first or above the last carrier frequency used | ACLR limit | +|----------------------------------------------------------------------------|------------| +| 5 MHz | 44.2 dB | +| 10 MHz | 49.2 dB | + +NOTE 1: In certain regions, the adjacent channel power (the RRC filtered mean power centred on an adjacent channel frequency) shall be less than or equal to -7.2 dBm/3.84 MHz (for Band I, III, IX, XI and XXI) or +2.8 dBm/3.84 MHz (for Band VI, VIII and XIX) or as specified by the ACLR limit, whichever is the higher. This note is not applicable for Home BS. + +NOTE 2: For Home BS, the adjacent channel power (the RRC filtered mean power centred on an adjacent channel frequency) shall be less than or equal to -42.7 dBm/3.84 MHz $f \leq 3.0$ GHz and -42.4 dBm/3.84 MHz for $3.0$ GHz $< f \leq 4.2$ GHz or as specified by the ACLR limit, whichever is the higher. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +The measurement result in shall not be less than the ACLR limit specified in table 6.6.3.5.4.1-2. + +**Table 6.6.3.5.4.1-2: ACLR in non-contiguous spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| $W_{\text{gap}} \geq 15$ MHz | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| $W_{\text{gap}} \geq 20$ MHz | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | + +NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +#### 6.6.3.5.4.2 Cumulative ACLR test requirement in non-contiguous spectrum or multiple-bands + +The following test requirement applies for a *TAB connector* operating in non-contiguous spectrum or multiple bands. + +The following requirement applies for the gap sizes listed in table 6.6.3.5.4.2-1: + +- inside a sub-block gap within an operating band for a *TAB connector* operating in non-contiguous spectrum; +- inside an *Inter RF Bandwidth gap* for a *multi-band TAB connector*. + +The Cumulative Adjacent Channel Leakage power Ratio (CACLR) in a sub-block gap or *Inter RF Bandwidth gap* is the ratio of: + +- a) the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the sub-block gap or *Inter RF Bandwidth gap*; and +- b) the filtered mean power centred on a frequency channel adjacent to one of the respective sub-block edges or *Base Station RF Bandwidth edges*. + +The assumed filter for the adjacent channel frequency is defined in table 6.6.3.5.4.2-1 and the filters on the assigned channels are defined in table 6.6.3.5.4.2-2. + +The CACLR for UTRA carriers located on either side of the sub-block gap or *Inter RF Bandwidth gap* shall be higher than the value specified in table 6.6.3.5.4.2-1. + +**Table 6.6.3.5.4.2-1: Base Station CACLR in non-contiguous spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------| +| $5 \text{ MHz} \leq W_{\text{gap}} < 15 \text{ MHz}$ | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| $10 \text{ MHz} < W_{\text{gap}} < 20 \text{ MHz}$ | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | + +NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +**Table 6.6.3.5.4.2-2: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the sub-block or Inter RF Bandwidth gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| UTRA FDD | RRC (3.84 Mcps) | +| NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | + +### 6.6.3.5.5 UTRA TDD, 1,28Mcps option + +The ACLR shall be equal or greater than the limits given in table 6.6.3.5.5-1. In case the equipment is tested against the requirements defined for operation in the same geographic area or co-sited with unsynchronised TDD or FDD on adjacent channels, the adjacent channel leakage power measured shall not exceed the maximum levels specified in tables 6.27B, 6.27C, 6.27D, 6.28B, 6.28C or 6.28D, respectively. + +**Table 6.6.3.5.5-1: BS ACLR Test Requirements (1,28 Mcps option)** + +| BS adjacent channel offset below the first or above the last carrier frequency used | ACLR limit | +|-------------------------------------------------------------------------------------|------------| +| 1,6 MHz | 39.2 dB | +| 3,2 MHz | 44.2 dB | + +The requirements shall apply outside the *Base Station RF bandwidth* or *maximum radio bandwidth* edges whatever the type of transmitter considered (single carrier, multi-carrier). It applies for all transmission modes foreseen by the manufacturer's specification. + +For a *multi-band TAB connector* the ACLR requirement also applies for the first adjacent channel inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 4.8 \text{ MHz}$ . The ACLR requirement for the second adjacent channel applies inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 6.4 \text{ MHz}$ . + +The same test requirements apply to 1,28 Mcps TDD option BS supporting 16QAM. + +### 6.6.3.5.6 E-UTRA + +#### 6.6.3.5.6.1 ACLR + +The ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal ( $BW_{\text{Config}}$ ) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +For operation in paired spectrum, the ACLR shall be higher than the value specified in table 6.6.3.5.6.1-1. + +**Table 6.6.3.5.6.1-1: ACLR in paired spectrum** + +| Channel bandwidth of E-UTRA lowest/highest carrier transmitted $BW_{\text{Channel}}$ (MHz) | adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|--------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| 1.4, 3.0, 5, 10, 15, 20 | $BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | $2 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 2.5 \text{ MHz}$ | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 7.5 \text{ MHz}$ | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | + +NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{Config}}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA lowest/highest carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.014 [3] with a chip rate as defined in this table. + +For operation in unpaired spectrum, the ACLR shall be higher than the value specified in table 6.6.3.5.6.1-2. + +**Table 6.6.3.5.6.1-2: ACLR in unpaired spectrum with synchronized operation** + +| Channel bandwidth of E-UTRA lowest/highest carrier transmitted $BW_{\text{Channel}}$ (MHz) | adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|--------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| 1.4, 3.0 | $BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | $2 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 0.8 \text{ MHz}$ | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 2.4 \text{ MHz}$ | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| 5, 10, 15, 20 | $BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | $2 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 0.8 \text{ MHz}$ | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 2.4 \text{ MHz}$ | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 2.5 \text{ MHz}$ | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 7.5 \text{ MHz}$ | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 5 \text{ MHz}$ | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 44.2 dB | +| | $BW_{\text{Channel}}/2 + 15 \text{ MHz}$ | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 44.2 dB | + +NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{Config}}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA lowest/highest carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.014 [3] with a chip rate as defined in this table. + +For operation in non-contiguous paired spectrum or multiple bands, the ACLR shall be higher than the value specified in table 6.6.3.5.6.1-3. + +**Table 6.6.3.5.6.1-3: Base Station ACLR in non-contiguous paired spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| $W_{\text{gap}} \geq 15 \text{ MHz}$ | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| $W_{\text{gap}} \geq 20 \text{ MHz}$ | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | + +NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +For operation in non-contiguous unpaired spectrum or multiple bands, the ACLR shall be higher than the value specified in table 6.6.3.5.6.1-4. + +**Table 6.6.3.5.6.1-4: ACLR in non-contiguous unpaired spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| $W_{\text{gap}} \geq 15$ MHz | 2.5 MHz | 5 MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| $W_{\text{gap}} \geq 20$ MHz | 7.5 MHz | 5 MHz E-UTRA | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | + +#### 6.6.3.5.6.2 Cumulative ACLR test requirement in non-contiguous spectrum + +The following test requirement applies for the sub-block or *Inter RF Bandwidth gap* sizes listed in table 6.6.3.5.6.2-1, + +- Inside a sub-block gap within an operating band for a BS operating in non-contiguous spectrum. +- Inside an *Inter RF Bandwidth gap* for a *multi-band TAB connector*. + +The Cumulative Adjacent Channel Leakage power Ratio (CACLR) in a sub-block gap or *Inter RF Bandwidth gap* is the ratio of: + +- a) the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the sub-block gap or *Inter RF Bandwidth gap*; and +- b) the filtered mean power centred on a frequency channel adjacent to one of the respective sub-block edges or *Base Station RF Bandwidth edges*. + +The assumed filter for the adjacent channel frequency is defined in tables 6.6.3.5.6.2-1 and 6.6.3.5.6.2-2. Filters on the assigned channels are defined in table 6.6.3.5.6.2-3. + +For operation in non-contiguous spectrum or multiple bands, the CACLR for E-UTRA carriers located on either side of the sub-block gap or *Inter RF Bandwidth gap* shall be higher than the value specified in tables 6.6.3.5.6.2-1 and 6.6.3.5.6.2-2. + +**Table 6.6.3.5.6.2-1: Base Station CACLR in non-contiguous paired spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|--------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------| +| $5 \text{ MHz} \leq W_{\text{gap}} < 15 \text{ MHz}$ | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| $10 \text{ MHz} < W_{\text{gap}} < 20 \text{ MHz}$ | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44.2 dB | +| NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | | | | + +**Table 6.6.3.5.6.2-2: Base Station CACLR in non-contiguous unpaired spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------| +| $5 \text{ MHz} \leq W_{\text{gap}} < 15 \text{ MHz}$ | 2.5 MHz | 5 MHz E-UTRA carrier | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | +| $10 \text{ MHz} < W_{\text{gap}} < 20 \text{ MHz}$ | 7.5 MHz | 5 MHz E-UTRA carrier | Square ( $BW_{\text{Config}}$ ) | 44.2 dB | + +**Table 6.6.3.5.6.2-3: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the sub-block or Inter RF Bandwidth gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| E-UTRA | E-UTRA of same BW | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.6.4 Spectrum emission mask + +### 6.6.4.1 Definition and applicability + +This requirement is applicable for single RAT UTRA AAS BS operation only. + +### 6.6.4.2 Minimum requirement + +The minimum requirement for UTRA operation are defined in TS 37.105 [8], clause 6.6.4.3. + +### 6.6.4.3 Test purpose + +This test measures the emissions of the *TAB connector*, close to the assigned channel bandwidth of the wanted signal, while the transmitter unit associated with the *TAB connector* under test is in operation. + +### 6.6.4.4 Method of test + +#### 6.6.4.4.1 Initial conditions + +##### 6.6.4.4.1.1 General test conditions + +Test environment: + +- normal; see clause B.2. + +RF channels to be tested for single carrier: + +- B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single-band operation; see clause 4.12.1; $B'_{\text{RFBW}}$ , $T'_{\text{RFBW}}$ and $B'_{\text{RFBW}}$ , $T'_{\text{RFBW}}$ in multi-band operation, see clause 4.12.1. + +#### 6.6.4.4.1.2 UTRA FDD + +For a *TAB connector* declared to be capable of single carrier operation only, set to transmit a signal according to TM1, in clause 4.12.2. + +For a *multi-carrier TAB connector*, set to transmit according to TM1 on all carriers configured using the applicable test configuration. + +#### 6.6.4.4.1.3 UTRA TDD + +For a *TAB connector* declared to be capable of single carrier operation only, set the parameters of the transmitted signal according to table 6.6.4.4.1.3-1. + +For a *multi-carrier TAB connector* set to transmit according to table 6.6.4.4.1.3-1 on all carriers configured using the applicable test configuration. + +**Table 6.6.4.4.1.3-1: Parameters of the transmitted signal for spectrum emission mask testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| 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) | + +In addition for a *TAB connector* declared capable of 16QAM. + +For a *TAB connector* declared to be capable of single carrier operation only, set the parameters of the transmitted signal according to table 6.6.4.4.1.3-2. + +For a *multi-carrier TAB connector* set to transmit according to table 6.6.4.4.1.3-2 on all carriers configured using the applicable test configuration. + +**Table 6.6.4.4.1.3-2: Parameters of the transmitted signal for spectrum emission mask testing for 1,28 Mcps TDD - 16QAM capable *TAB connector*** + +| Parameter | Value/description | +|-------------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 8 | +| Power of each HS-PDSCH | 1/8 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.6.4.4.2 Procedure + +##### 6.6.4.4.2.1 General procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. + +As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity, efficiency and avoiding e.g. carrier leakage, the resolution bandwidth may 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. + +The measurement device characteristics shall be: + +- Measurements with an offset from the carrier centre frequency between 2,515 MHz and 4.0 MHz shall use a 30 kHz measurement bandwidth. +- Measurements with an offset from the carrier centre frequency between 4.0 MHz and ( $f_{\text{offsetmax}} - 500$ kHz).shall use a 1 MHz measurement bandwidth. +- Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- b) For single carrier operation set the *TAB connector* to transmit at manufacturers declared rated carrier output power per *TAB connector* ( $P_{\text{Rated,c,TABC}}$ ) + +For a *TAB connector* declared to be capable of multi-carrier and/or CA operation set the *TAB connector* to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 5 using the corresponding test models or set of physical channels in clause 4.12. + +#### 6.6.4.4.2.1 UTRA FDD + +- 1) Step the centre frequency of the measurement filter in contiguous steps and measure the emission within the specified frequency ranges with the specified measurement bandwidth. For *multi-band TAB connector* or *TAB connector* operating in non-contiguous spectrum, the emission within the Inter RF Bandwidth or sub-block gap shall be measured using the specified measurement bandwidth from the closest *Base Station RF Bandwidth* or sub block edge. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 2) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.6.4.4.2.2 UTRA TDD + +- 1) Measure the power of the *TAB connector* spectrum emissions by applying measurement filters with bandwidths as specified in the relevant table in clause 6.6.4.5.2.2. The characteristic of the filters shall be approximately Gaussian (typical spectrum analyzer filters). The centre frequency of the filter shall be stepped in contiguous steps over the ranges of frequency offsets $f_{\text{offset}}$ as given in the tables. The step width shall be equal to the respective measurement bandwidth. The time duration of each step shall be sufficiently long to capture one active time slot. +- 2) The measurement shall be performed by applying filters with measurement bandwidth of 50 kHz or less and integrating the measured results over the nominal measurement bandwidth 1 MHz specified in the tables in clause 6.6.4.5.2.2 when the measurement bandwidth is 1 MHz. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +The same procedure applies to *TAB connectors* declared to support 16QAM. + +## 6.6.4.5 Test requirements + +### 6.6.4.5.1 General + +Conformance may be shown to either the measure and sum test requirement or the per *TAB connector* test requirement. + +- 1) The spurious emission test requirements for an AAS BS when using the measure and sum alternative are that for each *TAB connector TX cell group* and each applicable *basic limit* as specified in this clause, the power summation of emissions at the *TAB connectors* of the *TAB connector TX cell group* shall not exceed a limit specified as the *basic limit* + $10\log_{10}(N_{\text{TXU,countedpercell}})$ . +- 2) The spurious emission test requirements for an AAS BS when using the per *TAB connector* alternative are that for each *TAB connector TX cell group* and each applicable *basic limit* as specified in this clause, the emissions at each of the *TAB connectors* of the *TAB connector TX cell group* shall not exceed a limit specified as the *basic limit* + $10\log_{10}(N_{\text{TXU,countedpercell}}) - 10\log(n)$ where $n$ is the number of *TAB connectors* in the *TAB connector TX cell group*. + +The appropriate table for the basic limit is based on the same power level ( $P_{\text{Rated,c,sys}}$ ) as used for the AAS BS rated power limits for BS classes in table 6.2.2.1-1 the same method of scaling the power level using $N_{\text{TXU,counted}}$ is used. + +### 6.6.4.5.2 Basic Limits + +#### 6.6.4.5.2.1 UTRA FDD + +The *basic limit* is specified in tables 6.6.4.5.2.1-1 to 6.6.4.5.2.1-11 for the appropriate $P_{\text{Rated,c,sys}}$ , where: + +- $\Delta f$ is the separation between the carrier frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the carrier frequency and the centre of the measurement filter; +- $f_{\text{offset,max}}$ is either 12.5 MHz or the offset to the UMTS Tx band edge as defined in clause 3.4.1, whichever is the greater. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset,max}}$ minus half of the bandwidth of the measuring filter. + +Inside any *Inter RF Bandwidth gap* $s$ with $W_{\text{gap}} < 2 \times \Delta f_{\text{OBUE}}$ MHz for BS operating in multiple bands, emissions shall not exceed the cumulative sum of the test requirements specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *basic limit* for *Base Station RF Bandwidth edge* is specified in tables 6.6.4.5.2.1-1 to 6.6.4.5.2.1-11 below, where in this case: + +- $\Delta f$ is equal to 2.5 MHz plus the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the *Base Station RF Bandwidth edge*. +- $f_{\text{offset}}$ is equal to 2.5 MHz plus the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f_{\text{offset,max}}$ is either 12.5 MHz or the offset to the UMTS Tx band edge as defined in clause 5.2, whichever is the greater. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset,max}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector*, the operating band unwanted emission limits apply also in a supported operating band without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported operating band. In this case, no cumulative limit is applied in the *inter-band gap* between a supported downlink operating band with carrier(s) transmitted and a supported downlink operating band without any carrier transmitted and + +- In case the *inter-band gap* between a downlink band with carrier(s) transmitted and a downlink band without any carrier transmitted is less than $2 \times \Delta f_{\text{OBUE}}$ MHz, $f_{\text{offset,max}}$ shall be the offset to the frequency 10 MHz outside the outermost edges of the two downlink operating bands and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both downlink bands. + +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{max}$ ), shall apply from $\Delta f_{OBUE}$ MHz below the lowest frequency, up to $\Delta f_{OBUE}$ MHz above the highest frequency of the downlink operating band without any carrier transmitted. + +Inside any sub-block gap for a *TAB connector* operating in non-contiguous spectrum, the measurement results shall not exceed the cumulative sum of the test requirements specified for the adjacent sub blocks on each side of the sub block gap. The *basic limit* for each sub block is specified in tables 6.6.4.5.2.1-1 to 6.6.4.5.2.1-11 below, where in this case: + +- $\Delta f$ is equal to 2.5 MHz plus the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f\_offset$ is equal to 2.5 MHz plus the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the sub block gap bandwidth minus half of the bandwidth of the measuring filter plus 2.5 MHz. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +**Table 6.6.4.5.2.1-1: Spectrum emission mask values, $P_{rated,c,cell} - 10 \cdot \log_{10}(N_{TXU,countedpercell}) \geq 43$ dBm for UTRA FDD bands $\leq 3$ GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -12.5 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -24.5 dBm | 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 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -11.5 dBm | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation the *basic limit* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *basic limits* in clauses 6.6.6.5.2.2 and 6.6.6.5.5.3 shall be met. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE}$ MHz the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.6.4.5.2.1-2: Spectrum emission mask values, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \geq 43 \text{ dBm}$ UTRA FDD bands > 3 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -12.2 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -24.2 dBm | 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.2 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -11.2 dBm | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation the *basic limit* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *basic limits* in clause 6.6.6.5.2.2 and 6.6.6.5.3 shall be met. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.6.4.5.2.1-3: Spectrum emission mask values, + $39 \text{ dBm} \leq P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 43 \text{ dBm}$ for UTRA FDD bands $\leq 3 \text{ GHz}$** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -12.5 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -24.5 dBm | 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 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 54.5 \text{ dB}$ | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation the *basic limit* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *basic limits* in clauses 6.6.6.5.2.2 and 6.6.6.5.3 shall be met. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ MHz the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.6.4.5.2.1-4: Spectrum emission mask values, + $39 \text{ dBm} \leq P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 43 \text{ dBm}$ for UTRA FDD bands $> 3 \text{ GHz}$** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -12.2 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -24.2 dBm | 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.2 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{max,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 54.2 \text{ dB}$ | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation the *basic limit* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *basic limits* in clause 6.6.6.5.2.2 and 6.6.6.5.5.3 shall be met. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.6.4.5.2.1-5: Spectrum emission mask values, $31 \text{ dBm} \leq P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 39 \text{ dBm}$ for UTRA FDD bands $\leq 3 \text{ GHz}$** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 51.5 \text{ dB}$ | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 63.5 \text{ dB}$ | 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_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 50.5 \text{ dB}$ | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 54.5 \text{ dB}$ | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation the *basic limit* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *basic limits* in clauses 6.6.6.5.2.2 and 6.6.6.5.5.3 shall be met. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.6.4.5.2.1-6: Spectrum emission mask values, + $31 \text{ dBm} \leq P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 39 \text{ dBm}$ for UTRA FDD bands > 3 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 51.2 \text{ dB}$ | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 63.2 \text{ dB}$ | 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_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 50.2 \text{ dB}$ | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 54.2 \text{ dB}$ | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation the *basic limit* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *basic limits* in clauses 6.6.6.5.2.2 and 6.6.6.5.5.3 shall be met. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.6.4.5.2.1-7: Spectrum emission mask values, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}}) < 31 \text{ dBm}$ for UTRA FDD bands $\leq 3 \text{ GHz}$** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -20.5 dBm | 30 kHz | +| $2.7 \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -32.5 dBm | 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 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -23.5 dBm | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation the *basic limit* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *basic limits* in clauses 6.6.6.5.2.2 and 6.6.6.5.5.3 shall be met. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.6.4.5.2.1-8: Spectrum emission mask values, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, countedpercell}}) < 31$ dBm for UTRA FDD bands > 3 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -20.2 dBm | 30 kHz | +| $2.7 \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -32.2 dBm | 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.2 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -23.2 dBm | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation the *basic limit* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *basic limits* in clauses 6.6.6.5.2.2 and 6.6.6.5.5.3 shall be met. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +For operation in band II, IV, V, X, XII, XIII, XIV, XXV and XXVI, the applicable additional requirement in tables 6.6.4.5.2.1-9 to 6.6.4.5.2.1-11 apply in addition to the minimum requirements in tables 6.6.4.5.2.1-1 to 6.6.4.5.2.1-8. + +**Table 6.6.4.5.2.1-9: Additional spectrum emission limits 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 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | -15 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $4.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -13 dBm | 1 MHz | + +NOTE 5: 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. + +**Table 6.6.4.5.2.1-10: Additional spectrum emission limits for Bands V, XXVI** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | -15 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $3.55 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -13 dBm | 100 kHz | + +NOTE 5: 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. + +**Table 6.6.4.5.2.1-11: Additional spectrum emission limits 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 5) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.6 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.615 \text{ MHz}$ | -13 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 dBm | 100 kHz | + +NOTE 5: 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. + +In certain regions the following requirement may apply for protection of DTT. For a *TAB connector* 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 6.21F, shall not exceed the maximum emission level $P_{EM,N}$ declared by the manufacturer. + +**Table 6.6.4.5.2.1-12: Declared emissions levels for protection of DTT** + +| Filter centre frequency, $F_{filter}$ | Measurement bandwidth | Declared emission level (dBm) | +|-----------------------------------------------------------------------|-----------------------|-------------------------------| +| $F_{filter} = 8 \cdot N + 306 \text{ (MHz)}$ ;
$21 \leq N \leq 60$ | 8 MHz | $P_{EM,N}$ | + +NOTE 1: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the basestation needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in annex D of [1]. + +In certain regions, the following requirements may apply to a *TAB connector* operating in Band XXXII within 1452-1492 MHz. The level of unwanted emissions, measured on centre frequencies $f\_offset$ with filter bandwidth, according to table 6.6.4.5.2.1-13, shall neither exceed the maximum emission level $P_{EM,B32,a}$ , $P_{EM,B32,b}$ nor $P_{EM,B32,c}$ declared by the manufacturer. + +**Table 6.6.4.5.2.1-13: Declared frequency band XXXII unwanted emission within 1452-1492 MHz** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Declared emission level (dBm) | Measurement bandwidth | +|----------------------------------------------------------------------|-------------------------------|-----------------------| +| 5 MHz | $P_{EM,B32,a}$ | 5 MHz | +| 10 MHz | $P_{EM,B32,b}$ | 5 MHz | +| $15 \text{ MHz} \leq f\_offset \leq f\_offset_{max, B32}$ | $P_{EM,B32,c}$ | 5 MHz | + +NOTE: $f\_offset_{max, B32}$ denotes the frequency difference between the lower channel carrier frequency and 1454.5 MHz, and the frequency difference between the upper channel carrier frequency and 1489.5 MHz for the set channel position. + +NOTE 2: The regional requirement, included in [17], is defined in terms of EIRP per antenna, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in annex H of TS 36.104 [11]. + +In certain regions, the following requirement may apply to *TAB connector* operating in Band XXXII within 1452-1492MHz for the protection of services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{filter}$ with filter bandwidth according to table 6.6.4.5.2.1-14, shall neither exceed the maximum emission level $P_{EM,B32,d}$ nor $P_{EM,B32,e}$ declared by the manufacturer. This requirement applies in the frequency range 1429-1518MHz even though part of the range falls in the spurious domain. + +**Table 6.6.4.5.2.1-14: Frequency band XXXII declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission level (dBm) | Measurement bandwidth | +|---------------------------------------------------------------------|-------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{\text{filter}} \leq 1448.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | +| $F_{\text{filter}} = 1450.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $F_{\text{filter}} = 1493.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{\text{filter}} \leq 1517.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | + +NOTE 3: The regional requirement, included in [17], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in annex H of TS 36.104 [11]. + +#### 6.6.4.5.2.2 UTRA TDD + +The *basic limit* is specified in tables 6.6.4.5.2.2-1 to 6.6.4.5.2.2-3 for the appropriate $P_{\text{Rated,c,sys}}$ , where: + +**Table 6.6.4.5.2.2-1: basic limits for spectrum emission mask values, + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \geq 34 \text{ dBm}$ for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | basic limit | Measurement bandwidth | +|------------------------------------------------------------------------------|--------------------|-----------------------| +| $0.815 \text{ MHz} \leq f_{\text{offset}} < 1.015 \text{ MHz}$ | -18.5 dBm | 30 kHz | +| $1.015 \text{ MHz} \leq f_{\text{offset}} < 1.815 \text{ MHz}$ | | 30 kHz | +| $1.815 \text{ MHz} \leq f_{\text{offset}} < 2.3 \text{ MHz}$ | -26.5 dBm | 30 kHz | +| $2.3 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offset,max}}$ | -11.5 dBm | 1 MHz | + +NOTE: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* less than 8MHz, the *basic limit* within the *Inter RF Bandwidth gap* is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end *RF Bandwidth*. + +**Table 6.6.4.5.2.2-2: basic limits for spectrum emission mask values, + $26 \text{ dBm} \leq P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 34 \text{ dBm}$ for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | basic limit | Measurement bandwidth | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------| +| $0.815 \text{ MHz} \leq f_{\text{offset}} < 1.015 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 52.5 \text{ dB}$ | 30 kHz | +| $1.015 \text{ MHz} \leq f_{\text{offset}} < 1.815 \text{ MHz}$ | | 30 kHz | +| $1.815 \text{ MHz} \leq f_{\text{offset}} < 2.3 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60.5 \text{ dB}$ | 30 kHz | +| $2.3 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offset,max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 45.5 \text{ dB}$ | 1 MHz | + +NOTE: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* less than 8MHz, the *basic limit* within the *Inter RF Bandwidth gap* is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end *RF Bandwidth*. + +**Table 6.6.4.5.2.2-3: basic limits for spectrum emission mask values, + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) < 26 \text{ dBm}$ for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | -26.5 dBm | 30 kHz | +| $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$ | | 30 kHz | +| $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | -34.5 dBm | 30 kHz | +| $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -19.5 dBm | 1 MHz | + +NOTE: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* less than 8MHz, the *basic limit* within the *Inter RF Bandwidth gap* is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end *RF Bandwidth*. + +The basic limits for a TAB connector declared capable of 16QAM are the same as those defined in the clause. + +## 6.6.5 Operating band unwanted emission + +### 6.6.5.1 Definition and applicability + +Unless otherwise stated, for E-UTRA single band and MSR the operating band unwanted emission limits are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported *downlink operating band* to the lower *Base Station RF Bandwidth edge* located at $F_{\text{BW,RF,low}}$ and from the upper *Base Station RF Bandwidth edge* located at $F_{\text{BW,RF,high}}$ up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported *downlink operating band*. The values of $\Delta f_{\text{OBUE}}$ are defined in table 6.6.1-1. + +For AAS BS capable of operation in multiple operating bands, using *single band TAB connectors*, the single-band requirements apply to those connectors and the cumulative evaluation of the emission limit in the *inter RF bandwidth gap* is not applicable. + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. + +For BS operating in bands n50, n51, n74, n75 and n76 additional emission limits that might be applicable outside OBUE frequency domain are specified in clause 6.6.5.5.4.6. + +### 6.6.5.2 Minimum requirement + +The minimum requirement for MSR operation are defined in TS 37.105 [8], clause 6.6.5.2. + +There is no Operating band unwanted emission requirement for UTRA operation. + +The minimum requirement for E-UTRA operation is in TS 37.105 [8], clause 6.6.5.4. + +### 6.6.5.3 Test purpose + +This test measures the emissions of the *TAB connector*, close to the assigned channel bandwidth of the wanted signal, while the transmitter is in operation. + +### 6.6.5.4 Method of test + +#### 6.6.5.4.1 Initial conditions + +##### 6.6.5.4.1.1 General test conditions + +Test environment: + +- normal; see clause B.2. + +RF channels to be tested for single carrier: + +- B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- BRFBW, MRFBW and TRFBW in single-band operation; see clause 4.12.1; BRFBW' TRFBW' and BRFBW' TRFBW' in multi-band operation, see clause 4.12.1. + +#### 6.6.5.4.1.2 UTRA FDD + +#### 6.6.5.4.1.3 E-UTRA and NR + +#### 6.6.5.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.1. All *TAB connectors* not under test shall be terminated. + +As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity, efficiency and avoiding e.g. carrier leakage, the resolution bandwidth may 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. + +The measurement device characteristics shall be: + +- Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 2) Set the set the *TAB connector* to transmit: + +a) For MSR: + +- Set the *TAB connector* to transmit maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12. + +b) For E-UTRA: + +- *TAB connector* declared to be capable of single carrier operation only, set the *TAB connector* to transmit a signal according to E-TM1.1 (clause 4.12.2) at manufacturer's declared rated output power $P_{\text{rated,c,TABC..}}$ +- For a *TAB connector* declared to be capable of multi-carrier and/or CA operation, set the set the *TAB connector* to transmit according to E-TM1.1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +- 3) Step the centre frequency of the measurement filter in contiguous steps and measure the emission within the specified frequency ranges with the specified measurement bandwidth. + +- 4) Repeat the test for the remaining test cases: + +a) For MSR with channel set-up according to clause 5 and clause 4.12.2. + +b) For E-UTRA with the channel set-up according to E-TM 1.2 + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 6.6.5.5 Test requirements + +### 6.6.5.5.1 General + +Conformance may be shown to either the measure and sum test requirement or the per *TAB connector* test requirement. + +- 1) The spurious emission test requirements for an AAS BS when using the measure and sum alternative are that for each *TAB connector TX cell group* and each applicable *basic limit* as specified in this clause, the power summation of emissions at the *TAB connectors* of the *TAB connector TX cell group* shall not exceed a limit specified as the *basic limit* + $10\log_{10}(N_{\text{TXU, counted per cell}})$ . +- 2) The spurious emission test requirements for an AAS BS when using the per *TAB connector* alternative are that for each *TAB connector TX cell group* and each applicable *basic limit* as specified in this clause, the emissions at each of the *TAB connectors* of the *TAB connector TX cell group* shall not exceed a limit specified as the *basic limit* + $10\log_{10}(N_{\text{TXU, counted per cell}}) - 10\log(n)$ where $n$ is the number of *TAB connectors* in the *TAB connector TX cell group*. + +The appropriate table for the basic limit is based on the same power level ( $P_{\text{Rated, c, sys}}$ ) as used for the AAS BS rated power limits for BS classes in table 6.2.2.1-1 the same method of scaling the power level using $N_{\text{TXU, counted}}$ is used. + +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. + +### 6.6.5.5.2 Basic Limits for MSR Band Categories 1 and 3 + +For an AAS BS of Wide Area BS class operating in Band Category 1 or Band Category 3, the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for a Wide Area BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for an AAS BS of Wide Area BS class operating in multiple bands, it applies inside any *Inter RF Bandwidth gap*. + +For an AAS BS of Medium Range BS class operating in Band Category 1 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for a Medium Range BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for an AAS BS of Medium Range BS class operating in multiple bands, it applies inside any *Inter RF Bandwidth gap*. + +For an AAS BS of Local Area BS class operating in Band Category 1 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for a Local Area BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for an AAS BS of Local Area BS class operating in multiple bands, it applies inside any *Inter RF Bandwidth gap*. + +Outside the *Base Station RF Bandwidth edges*, emissions *basic limits* are specified in tables 6.6.2.5.1-1 to 6.6.2.5.1-4 below, where: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f_{\text{offset,max}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink operating band. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset,max}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector*, inside any *Inter RF Bandwidth gaps* with $W_{\text{gap}} < 2 * \Delta f_{\text{OBUE}}$ , a combined *basic limit* shall be applied which is the cumulative sum of the test requirements specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *basic limit* for *Base Station RF Bandwidth edge* is specified in tables 6.6.5.5.2-1 to 6.6.5.5.2-8, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. + +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *Inter RF Bandwidth gap* divided by two. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector*, the operating band unwanted emission limits apply also in a supported operating band without any carriers transmitted, in the case where there are carriers transmitted in another operating band. In this case where there is no carrier transmitted in an operating band, no cumulative *basic limits* are applied in the *inter-band gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted and + +- In case the *Inter RF Bandwidth gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted is less than $2 * \Delta f_{OBUE}$ MHz, $f\_offset_{max}$ shall be the offset to the frequency $\Delta f_{OBUE}$ outside the outermost edges of the two supported downlink operating bands and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both supported downlink bands. +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{max}$ ), shall apply from $\Delta f_{OBUE}$ below the lowest frequency, up to $\Delta f_{OBUE}$ above the highest frequency of the supported downlink operating band without any carrier transmitted. + +Inside any sub-block gap for a *TAB connector* operating in non-contiguous spectrum, a combined *basic limit* shall be applied which is the cumulative sum of the test requirements specified for the adjacent sub blocks on each side of the sub block gap. The *basic limit* for each sub block is specified in tables 6.6.5.5.2-1 to 6.6.5.5.2-8, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge frequency. +- $f\_offset$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the sub block gap bandwidth divided by two. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +Applicability of Wide Area operating band unwanted emission requirements in tables 6.6.5.5.2-1/2, 6.6.5.5.2-2a and 6.5.5.2-2b is specified in table 6.6.5.5.2-0. + +Note: Option 1 and Option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [4] and TS 38.104 [36]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [2]. + +**Table 6.6.5.5.2-0: Applicability of operating band unwanted emission requirements for BC1 and BC3 Wide Area BS** + +| NR band operation | UTRA supported (NOTE 1) | Applicable requirement table | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------| +| None | Y/N | 6.6.5.5.2-1/2 (option 2) | +| In certain regions (NOTE 2), band 1, 7, 38, 65 | N | 6.6.5.5.2-1/2 (option 2) | +| Any | Y | 6.6.5.5.2-1/2 (option 2) | +| Any below 1 GHz | N | 6.6.5.5.2-2a (option 1) | +| Any above 1 GHz except for certain regions (NOTE 2), band 1, 65 | N | 6.5.5.2-2b/2c (option 1) | +| NOTE 1: Void | | | +| NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [35] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [4] and TS 38.104 [36] are applied. | | | + +**Table 6.6.5.5.2-1: WA BS OBUE in BC1 and BC3 bands $\leq 3$ GHz – option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-12.5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$
(Note 6) | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.5 dBm (Note 6) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -11.5 dBm (Note 6) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 5, 6) | 1 MHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/MHz (for MSR *multi-band TAB connector* supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ ). + +NOTE 2: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +NOTE 6: For MSR *multi-band TAB connector* supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ . + +**Table 6.6.5.5.2-2: WA BS OBUE in BC1 and BC3 bands $> 3$ GHz - option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.2 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.2 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -11.2 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 5) | 1 MHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/MHz. + +NOTE 2: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-2a: WA BS OBUE in BC1 and BC3 bands $\leq 1$ GHz - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | -12.5 dBm | | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -16 dBm (Note 3) | | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band*, the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be -16 dBm/100 kHz. + +NOTE 2: For a *multi-band connector* with Inter RF Bandwidth gap $< 2 * \Delta f_{OBUE}$ the emission limits within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: The requirement is not applicable when $\Delta f_{max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-2b: WA BS OBUE in BC1 and BC3 bands $> 1$ GHz and $\leq 3$ GHz - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | -12.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm (Note 3) | 1MHz | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band*, the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with Inter RF Bandwidth gap $< 2 * \Delta f_{OBUE}$ the emission limits within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: The requirement is not applicable when $\Delta f_{max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-2c: WA BS OBUE in BC1 and BC3 bands $> 3$ GHz - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.2 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | -12.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm (Note 3) | 1MHz | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band*, the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with Inter RF Bandwidth gap $< 2 * \Delta f_{OBUE}$ the emission limits within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: The requirement is not applicable when $\Delta f_{max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-3: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm and not supporting NR; or BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 63.5 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.1 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 50.5 \text{ dB}$ | 1 MHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.1 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 50.5 \text{ dB}, -13.5 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\text{max}}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\text{max}}, 10.5 \text{ MHz})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 54.5 \text{ dB}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB}$
(Note 5) | 1 MHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be $(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB})/\text{MHz}$ . + +NOTE 2: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-3a: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 51.5 \text{ dB} - 7/5(f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 58.5 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})$
(Note 3) | 100 kHz | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band* the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm}) / 100 \text{ kHz}$ . + +NOTE 2: For a *multi-band connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-4: MR BS OBUE in BC1 bands > 3 GHz applicable for: BS with maximum output power 31 < $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38 \text{ dBm}$ and not supporting NR; or BS with maximum output power 31 < $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38 \text{ dBm}$ supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 63.2 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.1 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 50.2 \text{ dB}$ | 1 MHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.1 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 50.2 \text{ dB}, -13.2 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\text{max}}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\text{max}}, 10.5 \text{ MHz})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 54.2 \text{ dB}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB}$
(Note 5) | 1 MHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be $(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB})/\text{MHz}$ . + +NOTE 2: For MSR multi-band *TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-4a: MR BS OBUE in BC1 bands > 3 GHz applicable for: BS with maximum output power 31 < $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38 \text{ dBm}$ , supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 51.2 \text{ dB} - 7/5(f\_offset - 0.05)$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 58.2 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(P_{\text{rated,c,cell}} - 60 \text{ dB}, -25 \text{ dBm})$
$\text{Min}(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})$
(Note 3) | 100 kHz | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band* the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be $\text{Min}(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm}) / 100 \text{ kHz}$ . + +NOTE 2: For a *multi-band connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-5: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm and not supporting NR; or BS with maximum output power $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-25.5 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-20.5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -32.5 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -19.5 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\text{max}}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\text{max}}, 10.5 \text{ MHz})$ | -23.5 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm (Note 5) | 1 MHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -25 dBm/MHz. + +NOTE 2: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-5a: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -27.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm (Note 3) | 100 kHz | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band* the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be -29dBm/100kHz. + +NOTE 2: For a *multi-band connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-6: MR BS OBUE in BC1 bands > 3 GHz applicable for: BS with maximum output power $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm and not supporting NR; or BS with maximum output power $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-25.2 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-20.2 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -32.2 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -19.2 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\text{max}}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\text{max}}, 10.5 \text{ MHz})$ | -23.2 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm (Note 5) | 1 MHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -25 dBm/MHz. + +NOTE 2: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-6a: MR BS OBUE in BC1 bands > 3 GHz applicable for: BS with maximum output power $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -27.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm (Note 3) | 100 kHz | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band* the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be -29dBm/100kHz. + +NOTE 2: For a *multi-band connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-7: LA BS OBUE in BC1 bands $\leq 3$ GHz** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -35.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 5) | 100 kHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -37 dBm/100 kHz. + +NOTE 2: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 * \Delta f_{\text{OBUE}} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: Void. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.2-8: LA BS OBUE in BC1 bands $> 3$ GHz** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Note 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -35.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 5) | 100 kHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -37 dBm/100 kHz. + +NOTE 2: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 * \Delta f_{\text{OBUE}} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: Void. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +### 6.6.5.5.3 Basic Limits for MSR Band Category 2 + +For a *TAB connector* operating in Band Category 2 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for a *TAB connector* operating in non-contiguous spectrum, it applies inside any sub-block gap. + +Outside the *Base Station RF Bandwidth edges*, *basic limits* are specified in tables 6.6.5.5.3-1 to 6.6.5.5.3-8, where: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{\max}$ is the offset to the frequency $\Delta f_{\text{OBUE}} \text{ MHz}$ outside the downlink operating band. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector*, inside any *Inter RF Bandwidth gaps* with $W_{\text{gap}} < 2 * \Delta f_{\text{OBUE}} \text{ MHz}$ , a combined *basic limit* shall be applied which is the cumulative sum of the test requirements specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *basic limit* for *Base Station RF Bandwidth edge* is specified in tables 6.6.5.5.3-1 to 6.6.5.5.3-8, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. + +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *Inter RF Bandwidth gap* divided by two. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector* and where there is no carrier transmitted in an operating band, no cumulative *basic limits* are applied in the *inter-band gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted and + +- In case the *inter-band gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted less than is $2 \times \Delta f_{OBUE}$ MHz, $f\_offset_{max}$ shall be the offset to the frequency $\Delta f_{OBUE}$ MHz outside the outermost edges of the two supported downlink operating bands and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both supported downlink bands. +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{max}$ ), shall apply from $\Delta f_{OBUE}$ MHz below the lowest frequency, up to $\Delta f_{OBUE}$ MHz above the highest frequency of the supported downlink operating band without any carrier transmitted. + +Inside any sub-block gap for a *TAB connector* operating in non-contiguous spectrum, a combined *basic* limit shall be applied which is the cumulative sum of the test requirement specified for the adjacent sub blocks on each side of the sub block gap. The *basic limit* for each sub block is specified in tables 6.6.5.5.3-1 to 6.6.5.5.3-8, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f\_offset$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the sub block gap bandwidth divided by two. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +Applicability of Wide Area operating band unwanted emission requirements in tables 6.6.5.5.3-1, 6.6.5.5.3-1a and 6.6.5.5.3-1b is specified in table 6.6.5.5.3-0. + +Note: Option 1 and option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [4] and TS 38.104 [36]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [2]. + +**Table 6.6.5.5.3-0: Applicability of operating band unwanted emission requirements for BC2 Wide Area BS** + +| NR band operation | UTRA supported | Applicable requirement table | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|------------------------------| +| None | Y/N | 6.6.5.5.3-1 (option 2) | +| In certain regions (NOTE 2), band 3, 8 | N | 6.6.5.5.3-1 (option 2) | +| Any | Y | 6.6.5.5.3-1 (option 2) | +| Any below 1 GHz except for, in certain regions (NOTE 2), band 8 | N | 6.6.5.5.3-1a (option 1) | +| Any above 1 GHz except for certain regions (NOTE 2), band 3 | N | 6.6.5.5.3-1b (option 1) | +| NOTE 1: Void | | | +| NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [35] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [4] and TS 38.104 [36] are applied. | | | + +**Table 6.6.5.5.3-1: WA BS OBUE in BC2 bands– option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 2 and 3) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-12.5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ (Note 11) | 30 kHz | +| (Note 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.5 dBm (Note 11) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -11.5 dBm (Note 11) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 10, 11) | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.5.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/MHz (for MSR *multi-band TAB connector*, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands <1GHz). + +NOTE 3: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz operation the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 8: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 10: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +NOTE 11: For MSR *multi-band TAB connector*, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands < 1 GHz. + +**Table 6.6.5.5.3-1a: WA BS OBUE in BC2 bands $\leq 1 \text{ GHz}$ – option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.5 - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -12.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 11) | 100 kHz | + +NOTE 1: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band, the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -16dBm/100kHz. + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.2.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.5.5.3-1b: WA BS OBUE in BC2 bands > 1 GHz – option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.5 - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -12.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 11) | 1MHz | + +NOTE 1: For MSR *TAB connectors* supporting non-contiguous spectrum operation within any operating band, the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within sub-block gaps shall be -15dBm/1MHz. + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.5.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.5.5.3-2: WA BS OBUE in BC2 bands applicable for: BS operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Note 2, 3 and 4) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 2: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 4: Void. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ + +**Table 6.6.5.5.3-3: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm and not supporting NR; or BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm supporting NR, and supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 2 and 3) | Measurement bandwidth | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$
(Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$
(Note 8) | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 63.5 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 50.5 \text{ dB}$ | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.3 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 50.5 \text{ dB}, -13.5 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\text{max}}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\text{max}}, 10.5 \text{ MHz})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 54.5 \text{ dB}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB}$
(Note 10) | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be $(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 56 \text{ dB})/\text{MHz}$ . + +NOTE 3: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 8: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 10: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ + +**Table 6.6.5.5.3-3a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 51.5 \text{ dB} - (7/5) \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 61.5 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})$
(Note 11) | 100 kHz | + +NOTE 1: For MSR *TAB connectors* supporting non-contiguous spectrum operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within sub-block gaps shall be $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm}) / 100 \text{ kHz}$ . + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.5.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.5.5.3-4: MR BS OBUE in BC2 bands applicable for: BS with maximum output power** + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ and not supporting NR; or BS with maximum output power + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ supporting NR, and supporting UTRA + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 2 and 3) | Measurement bandwidth | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-20.5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz | +| (Note 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -32.5 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -19.5 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\text{max}}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\text{max}}, 10.5 \text{ MHz})$ | -23.5 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm (Note 10) | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.5.3-6 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -25 dBm/MHz. + +NOTE 3: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 8: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 10: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ + +**Table 6.6.5.5.3-4a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power** + $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ , supporting NR, and not supporting UTRA + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth (Note 10) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------|---------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-20.5 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -27.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm (Note 11) | 100 kHz | + +NOTE 1: For MSR *TAB connectors* supporting non-contiguous spectrum operation within any operating band the *basic limit* within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the *sub block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the *sub-block gap*, where the *basic limit* within sub-block gaps shall be -29dBm/100kHz. + +NOTE 2: For MSR *multi band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.5.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +**Table 6.6.5.5.3-5: MR BS OBUE applicable for: BS with maximum output power $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm and operating E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 2 and 3) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 2: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ + +**Table 6.6.5.5.3-6: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm and operating E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 2, 3 and 4) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 2: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 4: Void. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ + +**Table 6.6.5.5.3-7: LA BS OBUE in BC2 bands** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 2 and 3) | Measurement bandwidth | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ (Note 1) | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -35.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -37 dBm (Note 7) | 100 kHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.5.3-8 apply for $0 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ . + +NOTE 2: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -37 dBm/100 kHz. + +NOTE 3: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ + +**Table 6.6.5.5.3-8: LA BS OBUE in BC2 bands applicable for: BS operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 2, 3 and 4) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.175 \text{ MHz}$ | | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 2: For MSR *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 4: Void. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ + +#### 6.6.5.5.4 Basic Limits for MSR Additional requirements + +##### 6.6.5.5.4.1 Limits in FCC Title 47 + +In addition to the requirements in clauses 6.6.5.5.2 and 6.6.5.5.3, the *TAB connector* may have to comply with the applicable *basic limits* established by FCC Title 47 [24], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +##### 6.6.5.5.4.2 Unsynchronized operation for BC3 + +In certain regions, the following requirements may apply to a TDD *TAB connector* operating in BC3 in the same geographic area and in the same operating band as another TDD system without synchronisation. For this case the emissions *basic limit* is -52 dBm/MHz in each supported downlink operating band except in: + +- The frequency range from 10 MHz below the lower *Base Station RF Bandwidth edge* to the frequency 10 MHz above the upper *Base Station RF Bandwidth edge* of each supported band. + +NOTE 1: Local or regional regulations may specify another excluded frequency range, which may include frequencies where synchronised TDD systems operate. + +NOTE 2: TDD Base Stations that are synchronized and operating in BC3 can transmit without these additional co-existence requirements. + +##### 6.6.5.5.4.3 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For a *TAB connector* operating in Band 20/n20, the level of emissions in the band 470-790 MHz, measured in an 8 MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to table 6.6.5.5.4.3-1, a *basic limit* $P_{\text{EM,N}}$ is declared by the manufacturer. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 6.6.5.5.4.3-1: Declared emissions *basic limit* for protection of DTT** + +| Filter centre frequency, $F_{\text{filter}}$ | Measurement bandwidth | Declared emission basic limit (dBm) | +|------------------------------------------------------------------------------|-----------------------|--------------------------------------------| +| $F_{\text{filter}} = 8 \cdot N + 306 \text{ (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 BS emissions at the *TAB connector* and radiated in the far field. The requirement defined above provides the characteristics of the AAS BS needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in annex G of TS 36.104 [11]. + +6.6.5.5.4.4 Void + +**Table 6.6.5.5.4.4-1: Void** + +6.6.5.5.4.5 Void + +**Table 6.6.5.5.4.5-1: Void** + +6.6.5.5.4.6 Additional band 32, 50, 51, 74, 75 and 76 unwanted emissions + +In certain regions, the following requirements may apply to a *TAB connector* operating in Band 32 within 1452-1492 MHz. The maximum level of operating band unwanted emissions, measured on centre frequencies $f\_offset$ with filter bandwidth, according to table 6.6.5.5.4.6-1, shall be defined according to the *basic limits* $P_{EM,B32,a}$ , $P_{EM,B32,b}$ and $P_{EM,B32,c}$ declared by the manufacturer. + +**Table 6.6.5.5.4.6-1: Declared operating band 32 unwanted emission within 1452-1492 MHz** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Declared emission basic limit (dBm) | Measurement bandwidth | +|----------------------------------------------------------------------|--------------------------------------------|-----------------------| +| 2.5 MHz | $P_{EM,B32,a}$ | 5 MHz | +| 7.5 MHz | $P_{EM,B32,b}$ | 5 MHz | +| $12.5 \text{ MHz} \leq f\_offset \leq f\_offset_{max, B32}$ | $P_{EM,B32,c}$ | 5 MHz | + +NOTE: $f\_offset_{max, B32}$ denotes the frequency difference between the lower *Base Station RF Bandwidth* edge and 1454.5 MHz, and the frequency difference between the upper *Base Station RF Bandwidth* edge and 1489.5 MHz for the set channel position. + +NOTE: The regional requirement, included in [25], is defined in terms of EIRP per antenna, which is dependent on both the BS emissions at the *TAB connector* and radiated in the far field. The requirement defined above provides the characteristics of the AAS BS needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in annex H of TS 36.104 [11]. + +In certain regions, the following requirement may apply to a *TAB connector* operating in Band 32 within 1452-1492 MHz for the protection of services in spectrum adjacent to the frequency range 1452-1492 MHz. The maximum level of emissions, measured on centre frequencies $F_{filter}$ with filter bandwidth according to table 6.6.5.5.4.6-2, shall be defined according to the *basic limits* $P_{EM,B32,d}$ and $P_{EM,B32,e}$ declared by the manufacturer. This requirement applies in the frequency range 1429-1518 MHz even though part of the range falls in the spurious domain. + +**Table 6.6.5.5.4.6-2: Operating band 32 declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{filter}$ | Declared emission basic limit (dBm) | Measurement bandwidth | +|--------------------------------------------------------------|--------------------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{filter} \leq 1448.5 \text{ MHz}$ | $P_{EM,B32,d}$ | 1 MHz | +| $F_{filter} = 1450.5 \text{ MHz}$ | $P_{EM,B32,e}$ | 3 MHz | +| $F_{filter} = 1493.5 \text{ MHz}$ | $P_{EM,B32,e}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{filter} \leq 1517.5 \text{ MHz}$ | $P_{EM,B32,d}$ | 1 MHz | + +NOTE: The regional requirement, included in [23], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and radiated in the far field. The requirement defined above provides the characteristics of the AAS BS needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in annex H of TS 36.104 [11]. + +In certain regions, the following requirement may apply to NR BS operating in Band 50 and 75 within the 1432 – 1452 MHz, and in Band 51 and Band 76. The *basic limit* is specified in Table 6.6.5.5.4.6-3. + +**Table 6.6.5.5.4.6-3: Additional emission *basic limit* for BS operating in Band 50 and 75 within 1432 – 1452 MHz, and in Band 51 and 76** + +| Filter centre frequency, $F_{\text{filter}}$ | Basic limit | Measurement Bandwidth | +|----------------------------------------------|--------------------|------------------------------| +| $F_{\text{filter}} = 1413.5 \text{ MHz}$ | -42 dBm | 27 MHz | + +In certain regions, the following requirement may apply to BS operating in Band 50 and 75 within 1492-1517 MHz and in Band 74 within 1492-1518 MHz. The maximum level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to Table 6.6.5.5.4.6-4, shall be defined according to the *basic limits* $P_{\text{EM,n50/n75,a}}$ nor $P_{\text{EM,n50/n75,b}}$ declared by the manufacturer. + +**Table 6.6.5.5.4.6-4: Operating band 50, 74 and 75 declared emission above 1518 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared basic limits (dBm) | Measurement bandwidth | +|---------------------------------------------------------------------|------------------------------------|------------------------------| +| $1518.5 \text{ MHz} \leq F_{\text{filter}} \leq 1519.5 \text{ MHz}$ | $P_{\text{EM,n50/n75,a}}$ | 1 MHz | +| $1520.5 \text{ MHz} \leq F_{\text{filter}} \leq 1558.5 \text{ MHz}$ | $P_{\text{EM,n50/n75,b}}$ | 1 MHz | + +NOTE: The regional requirement, included in ECC/DEC/(17)06 [42], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in TS 37.105 [6], Annex B.1. + +#### 6.6.5.5.4.7 Additional requirements for Band 48 + +The following requirement may apply to AAS BS operating in Band 48 in certain regions. Emissions shall not exceed the maximum levels specified in Table 6.6.2.5.4.7-1. + +**Table 6.6.2.5.4.7-1: Additional operating band unwanted emission limits for Band 48** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| All | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -13 dBm | 1 MHz | + +#### 6.6.5.5.5 Basic Limits for E-UTRA + +##### 6.6.5.5.5.1 General + +The measurement results in clause 6.6.5.4 shall not exceed the maximum levels based on the *basic limits* in the tables below, where: + +- $\Delta f$ is the separation between the channel edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the channel edge frequency and the centre of the measuring filter. +- $f\_offset_{\text{max}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ MHz outside the downlink operating band. +- $\Delta f_{\text{max}}$ is equal to $f\_offset_{\text{max}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band TAB connector*, inside any *Inter RF Bandwidth gaps* with $W_{\text{gap}} < 2 \times \Delta f_{\text{OBUE}}$ MHz, a combined *basic limit* shall be applied which is the cumulative sum of the test requirements specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *basic limit* for *Base Station RF Bandwidth edge* is specified in tables 6.6.5.5.2-1 to 6.6.5.5.2-9, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the *Base Station RF Bandwidth edge*. +- $f_{\text{offset}}$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f_{\text{offset}_{\text{max}}}$ is equal to the *Inter RF Bandwidth gap* minus half of the bandwidth of the measuring filter. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset}_{\text{max}}}$ minus half of the bandwidth of the measuring filter. + +For *multi-band TAB connector*, the operating band unwanted emission limits apply also in a supported operating band without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported operating band. In this case, no cumulative *basic limit* is applied in the *inter-band gap* between a supported downlink operating band with carrier(s) transmitted and a supported downlink operating band without any carrier transmitted and: + +- In case the *inter-band gap* between a supported downlink operating band with carrier(s) transmitted and a supported downlink operating band without any carrier transmitted is less than $2 \times \Delta f_{\text{OBUE}}$ MHz, $f_{\text{offset}_{\text{max}}}$ shall be the offset to the frequency $\Delta f_{\text{OBUE}}$ MHz outside the outermost edges of the two supported downlink operating bands and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both downlink bands. +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{\text{max}}$ ), shall apply from $\Delta f_{\text{OBUE}}$ MHz below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ MHz above the highest frequency of the supported downlink operating band without any carrier transmitted. + +For a multicarrier E-UTRA TAB connector or a *TAB connector* configured for intra-band contiguous or non-contiguous carrier aggregation the definitions above apply to the lower edge of the carrier transmitted at the lowest carrier frequency and the upper edge of the carrier transmitted at the highest carrier frequency within a specified frequency band. + +In addition inside any sub-block gap for a *TAB connector* operating in non-contiguous spectrum, measurement results shall not exceed a level based on a combined *basic limit* shall be applied which is the cumulative sum specified for the adjacent sub blocks on each side of the sub block gap. The *basic limit* for each sub block is specified in tables 6.6.5.5.2-1 to 6.6.5.5.2-9, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f_{\text{offset}}$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f_{\text{offset}_{\text{max}}}$ is equal to the sub block gap bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset}_{\text{max}}}$ minus half of the bandwidth of the measuring filter. + +#### 6.6.5.5.5.2 Basic Limits for Wide Area BS (Category A) + +For E-UTRA *TAB connector* operating in Bands 5, 6, 8, 12, 13, 14, 17, 18, 19, 26, 27, 28, 29, 31, 44, 68, 71, 72, 73, 106 *basic limits* are specified in tables 6.6.5.5.5.2-1 to 6.6.5.5.5.2-3. + +**Table 6.6.5.5.5.2-1: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -9.5 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -13 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.2-2: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -13.5 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -13 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.2-3: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -12.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -13 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For E-UTRA *TAB connector* operating in Bands 1, 2, 3, 4, 7, 9, 10, 11, 21, 23, 24, 25, 30, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 45, 48, 54, 65, 66, 69, 70, *basic limits* are specified in tables 6.6.5.5.5.2-4, 6.6.5.5.5.2-6 and 6.6.5.5.5.2-8. + +For E-UTRA *TAB connector* operating in Bands 22, 42, 43, 52 *basic limits* are specified in tables 6.6.5.5.5.2-5, 6.6.5.5.5.2-7 and 6.6.5.5.5.2-9. + +**Table 6.6.5.5.5.2-4: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (1GHz < E-UTRA bands ≤ 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -9.5 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -13 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.2-5: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -9.2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -13 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.2-6: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (1GHz < E-UTRA bands ≤ 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -13.5 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -13 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.2-7: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -13.2 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -13 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.2-8: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (1GHz < E-UTRA bands ≤ 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -12.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -13 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.2-9: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -12.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -13 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +#### 6.6.5.5.5.3 + +#### Basic limits for Wide Area BS Category B (Option1) + +For Category B Operating band unwanted emissions, there are two options for the limits that may be applied regionally, option 1 is as follows. For E-UTRA *TAB connector* operating in Bands 5, 8, 12, 13, 14, 17, 20, 26, 27, 28, 29, 31, 44, 67, 68, 71, 72, 73 *basic limits* are specified in tables 6.6.5.5.5.3-1 to 6.6.5.5.5.3-3. + +**Table 6.6.5.5.5.3-1: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -9.5 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -16 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.3-2: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -13.5 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -16 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.6.5.5.5.3-3: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -12.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -16 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For E-UTRA *TAB connector* operating in Bands 1, 2, 3, 4, 7, 10, 25, 30, 33, 34, 35, 36, 37, 38, 39, 40, 41, 45, 48, 65, 66, 69, 70, *basic limits* are specified in tables 6.6.5.5.5.3-4, 6.6.5.5.5.3-6 and 6.6.5.5.5.3-8. + +For E-UTRA *TAB connector* operating in Bands 22, 42, 43, 52 *basic limits* are specified in tables 6.6.5.5.5.3-5, 6.6.5.5.5.3-7 and 6.6.5.5.5.3-9. + +**Table 6.6.5.5.5.3-4: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (1GHz < E-UTRA bands $\leq$ 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -9.5 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.3-5: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -9.2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.3-6: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (1GHz < E-UTRA bands $\leq$ 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -13.5 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.3-7: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -13.2 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.3-8: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (1GHz < E-UTRA bands ≤ 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -12.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.3-9: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -12.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +#### 6.6.5.5.5.4 Basic limits for Wide Area BS Category B (Option 2) + +For Category B Operating band unwanted emissions, there are two options for the limits that may be applied regionally, option 2 is as follows. + +The limits in this clause are intended for Europe and may be applied regionally for a *TAB connector* operating in band 1, 3, 8, 32, 33, 34 or 65. + +For a *TAB connector* operating in band 1, 3, 8, 32, 33, 34 or 65, *basic limits* are specified in table 6.6.5.5.5.4-1 below for 5, 10, 15 and 20 MHz channel bandwidth. + +**Table 6.6.5.5.5.4-1: Regional Wide Area BS operating band unwanted emission limits in band 1, 3, 8, 32, 33, 34 or 65 for 5, 10, 15 and 20 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 7) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.5 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $1.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -11.5 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 7: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For a *TAB connector* operating in band 3, 8 or 65, *basic limits* are specified in table 6.6.5.5.5.4-2 for 3 MHz channel bandwidth. + +**Table 6.6.5.5.5.4-2: Regional Wide Area BS operating band unwanted emission limits in band 3, 8 or 65 for 3 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | +| $0.15 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.165 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 7) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.5 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$ | -11.5 dBm | 1 MHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 7: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For a BS operating in band 3, 8 or 65, *basic limits* are specified in table 6.6.5.5.5.4-3 for 1.4 MHz channel bandwidth. + +**Table 6.6.5.5.5.4-3: Regional Wide Area BS operating band unwanted emission limits in band 3, 8 or 65 for 1.4 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | +| $0.15 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.165 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.5 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 7) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.5 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | -11.5 dBm | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $3.3 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 dBm (Note 8) | 1 MHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 7: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 8: The requirement is not applicable when $\Delta f_{max} < 10 \text{ MHz}$ . + +#### 6.6.5.5.5 Basic limits for Local Area BS (Category A and B) + +For an AAS BS of Local Area BS class in E-UTRA bands $\leq 3 \text{ GHz}$ , *basic limits* are specified in tables 6.6.5.5.5.5-1, 6.6.5.5.5.5-3 and 6.6.5.5.5.5-5. + +For an AAS BS of Local Area BS class in E-UTRA bands $> 3 \text{ GHz}$ , *basic limits* are specified in tables 6.6.5.5.5.5-2, 6.6.5.5.5.5-4 and 6.6.5.5.5.5-6. + +**Table 6.6.5.5.5.5-1: Local Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-19.5 \text{ dBm} - \frac{10}{1.4} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -29.5 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -31 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -31 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.5-2: Local Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -29.2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -31 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -31 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.5-3: Local Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-23.5 \text{ dBm} - \frac{10}{3} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -33.5 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -35 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -35 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.5-4: Local Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -33.2 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -35 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -35 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.5-5: Local Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands $\leq 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-28.5 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -35.5 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -37 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.5-6: Local Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands $> 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -35.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -37 dBm/100 kHz. + +NOTE 2: For BS a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +#### 6.6.5.5.5.6 Basic limits for Medium Range BS (Category A and B) + +For an AAS BS of Medium Range BS class in E-UTRA bands $\leq 3$ GHz, *basic limits* are specified in tables 6.6.5.5.5.6-1, 6.6.5.5.5.6-3, 6.6.5.5.5.6-5, 6.6.5.5.5.6-7, 6.6.5.5.5.6-9 and 6.6.5.5.5.6-11. + +For an AAS BS of Medium Range BS class in E-UTRA bands $> 3$ GHz, *basic limits* are specified in tables 6.6.5.5.5.6-2, 6.6.5.5.5.6-4, 6.6.5.5.5.6-6, 6.6.5.5.5.6-8, 6.6.5.5.5.6-10 and 6.6.5.5.5.6-12. + +**Table 6.6.5.5.6-1: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38 \text{ dBm}$ (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 53.5 \text{ dB}$ | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -25 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.6-2: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38 \text{ dBm}$ (E-UTRA bands $> 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 53.2 \text{ dB}$ | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -25 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.6-3: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-12.5 \text{ dBm} - \frac{10}{1.4} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -22.5 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -25 dBm/100 kHz. + +NOTE 2: For BS a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.6-4: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-12.2 \text{ dBm} - \frac{10}{1.4} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -22.2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $2.85 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -25 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -25 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.6-5: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38 \text{ dBm}$ (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 57.5 \text{ dB}$ | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 59 \text{ dB}, -25 \text{ dBm})$ (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be $\text{Min}(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 59 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.6-6: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38 \text{ dBm}$ (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 57.2 \text{ dB}$ | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 59 \text{ dB}, -25 \text{ dBm})$ (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be $\text{Min}(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 59 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.6-7: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-16.5 \text{ dBm} - \frac{10}{3} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -26.5 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -28 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -28 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.6-8: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31 \text{ dBm}$ (E-UTRA bands $> 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-16.2 \text{ dBm} - \frac{10}{3} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -26.2 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -28 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be -28 dBm/100 kHz. + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.6-9: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38 \text{ dBm}$ (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 58.5 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})$ (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.6-10: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $31 < P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 38$ dBm (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 58.2 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})$ (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be $\min(P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.6-11: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-20.5 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $-27.5 \text{ dBm}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-29 \text{ dBm}$ (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be $-29 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.5.5.5.6-12: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU,countedpercell}}) \leq 31$ dBm (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-20.2 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $-27.2 \text{ dBm}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-29 \text{ dBm}$ (Note 8) | 100 kHz | + +NOTE 1: For a *TAB connector* supporting non-contiguous spectrum operation within any operating band the *basic limit* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *basic limit* within sub-block gaps shall be $-29 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band TAB connector* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *basic limit* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +#### 6.6.5.5.5.7 Basic limits for Additional requirements + +In certain regions the following requirement may apply. For E-UTRA *TAB connector* operating in Bands 5, 26, 27 or 28, *basic limits* are specified in table 6.6.5.5.5.7-1. + +**Table 6.6.5.5.5.7-1: Additional operating band unwanted emission limits for E-UTRA bands < 1 GHz** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| 1.4 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.005 \text{ MHz} \leq f\_offset < 0.995 \text{ MHz}$ | -14 dBm | 10 kHz | +| 3 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -13 dBm | 30 kHz | +| 5 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -15 dBm | 30 kHz | +| 10 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -13 dBm | 100 kHz | +| 15 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -13 dBm | 100 kHz | +| 20 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -13 dBm | 100 kHz | +| All | $1 \text{ MHz} \leq \Delta f < \Delta f_{\max}$ | $1.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm
(Note 8) | 100 kHz | + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +In certain regions the following requirement may apply. For E-UTRA a *TAB connector* operating in Bands 2, 4, 10, 23, 25, 30, 35, 36, 41, 66, 70 *basic limits* are specified in table 6.6.5.5.5.7-2. + +**Table 6.6.5.5.5.7-2: Additional operating band unwanted emission limits for E-UTRA bands > 1GHz** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| 1.4 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.005 \text{ MHz} \leq f\_offset < 0.995 \text{ MHz}$ | -14 dBm | 10 kHz | +| 3 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -13 dBm | 30 kHz | +| 5 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -15 dBm | 30 kHz | +| 10 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -13 dBm | 100 kHz | +| 15 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -15 dBm | 100 kHz | +| 20 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -16 dBm | 100 kHz | +| All | $1 \text{ MHz} \leq \Delta f < \Delta f_{\max}$ | $1.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm
(Note 8) | 1 MHz | + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +In certain regions the following requirement may apply. For E-UTRA a *TAB connector* operating in Bands 12, 13, 14, 17, 29, 71 *basic limits* are specified in table 6.6.5.5.5.7-3. + +**Table 6.6.5.5.5.7-3: Additional operating band unwanted emission limits for E-UTRA (bands 12, 13, 14, 17, 29, 71)** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limit | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| All | $0 \text{ MHz} \leq \Delta f < 100 \text{ kHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.085 \text{ MHz}$ | -13 dBm | 30 kHz | +| All | $100 \text{ kHz} \leq \Delta f < \Delta f_{\max}$ | $150 \text{ kHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm
(Note 8) | 100 kHz | + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +In certain regions, the following requirements may apply to an E-UTRA TDD *TAB connector* operating in the same geographic area and in the same operating band as another E-UTRA TDD system without synchronisation. For this case the basic limit shall be -52 dBm/MHz in each supported downlink operating band, except in: + +- The frequency range from 10 MHz below the lower channel edge to the frequency 10 MHz above the upper channel edge of each supported band. + +In certain regions the following requirement may apply for protection of DTT. For E-UTRA a *TAB connector* operating in Band 20, the maximum level of emissions in the band 470-790 MHz, measured in an 8MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to table 6.6.5.5.7-4, be based upon a declared *basic limit* $P_{\text{EM}}$ $P_{\text{EM,N}}$ declared by the manufacturer. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 6.6.5.5.7-4: Declared emissions *basic limit* for protection of DTT** + +| Filter centre frequency, $F_{\text{filter}}$ | Measurement bandwidth | Declared emission basic limit (dBm) | +|---------------------------------------------------------------------|-----------------------|--------------------------------------------| +| $F_{\text{filter}} = 8 \cdot N + 306$ (MHz);
$21 \leq N \leq 60$ | 8 MHz | $P_{\text{EM,N}}$ | + +NOTE 1: The regional requirement is defined in terms of EIRP, which is dependent on both the BS emissions at the *TAB connector* and the RND and antenna array. The EIRP level is calculated using: $P_{\text{EIRP}} = P_{\text{E}} + G_{\text{ant}}$ where $P_{\text{E}}$ denotes the *TAB connector* unwanted emission level at the *TAB connector*, $G_{\text{ant}}$ equals the RDN and antenna array gain. The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in annex G of TS 36.104 [11]. + +**Table 6.6.5.5.7-5: Void** + +In regions where FCC regulation applies, requirements for protection of GPS according to FCC Order DA 20-48 applies for operation in Band 24. The following normative requirement covers the base station, to be used together with other information about the site installation to verify compliance with the requirement in FCC Order DA 20-48. The requirement applies to a *TAB connector* operating in Band 24 to ensure that appropriate interference protection is provided to the GPS. This requirement applies to the frequency range 1541-1650 MHz, even though part of this range falls within the spurious domain. + +The maximum level of emissions in the 1541 - 1650 MHz band, measured in measurement bandwidth according to table 6.6.5.5.7-6 shall be based upon declared *basic limits* $P_{\text{EM\_B24,a}}$ , $P_{\text{EM\_B24,b}}$ , $P_{\text{EM\_B24,c}}$ , $P_{\text{EM\_B24,d}}$ , $P_{\text{EM\_B24,e}}$ and $P_{\text{EM\_B24,f}}$ declared by the manufacturer. + +**Table 6.6.5.5.7-6: Declared emissions *basic limits* for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range (MHz) | Declared emission level (dBW)
(Measurement bandwidth = 1 MHz) | Declared emission basic limit (dBW) of discrete emissions of less than 700 Hz bandwidth
(Measurement bandwidth = 1 kHz) | Declared emission basic limit (dBW) of discrete emissions of less than 2 kHz bandwidth
(Measurement bandwidth = 1 kHz) | +|----------------|-----------------------|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| 24 | 1541 - 1559 | $P_{\text{EM\_B24,a}}$ | | $P_{\text{EM\_B24,f}}$ | +| | 1559 - 1610 | $P_{\text{EM\_B24,b}}$ | $P_{\text{EM\_B24,d}}$ | | +| | 1610 - 1650 | $P_{\text{EM\_B24,c}}$ | $P_{\text{EM\_B24,e}}$ | | + +NOTE 2: The regional requirements in FCC Order DA 20-48 are defined in terms of EIRP, which is dependent on both the BS emissions at the *TAB connector* and the RND and antenna array. The EIRP level is calculated using: $P_{\text{EIRP}} = P_{\text{E}} + G_{\text{ant}}$ where $P_{\text{E}}$ denotes the *TAB connector* unwanted emission level at the *TAB connector*, $G_{\text{ant}}$ equals the RDN and antenna array gain. The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in annex G of TS 36.104 [11]. + +**Table 6.6.5.5.7-7: Void** + +**Table 6.6.5.5.7-8: void** + +**Table 6.6.5.5.7-9: void** + +For BS operating in bands 32, 50, 51, 74, 75 and 76 additional emission limits that might be applicable in the OBUE frequency domain are specified in clause 6.6.5.5.4.6. + +In certain regions the following requirement may apply to an E-UTRA *TAB connector* operating in Band 45. *Basic limits* are specified in table 6.6.5.5.7-10. + +**Table 6.6.5.5.7-10: Emissions *basic limits* for protection of adjacent band services** + +| Operating Band | Filter centre frequency, $F_{\text{filter}}$ | Basic limit (dBm) | Measurement Bandwidth | +|----------------|---------------------------------------------------------------------|--------------------------|-----------------------| +| 45 | $F_{\text{filter}} = 1467.5$ | -20 | 1 MHz | +| | $F_{\text{filter}} = 1468.5$ | -23 | 1 MHz | +| | $F_{\text{filter}} = 1469.5$ | -26 | 1 MHz | +| | $F_{\text{filter}} = 1470.5$ | -33 | 1 MHz | +| | $F_{\text{filter}} = 1471.5$ | -40 | 1 MHz | +| | $1472.5 \text{ MHz} \leq F_{\text{filter}} \leq 1491.5 \text{ MHz}$ | -47 | 1 MHz | + +The following requirement may apply to E-UTRA BS operating in Band 48 in certain regions. Emissions shall not exceed the maximum levels specified in Table 6.6.5.5.7-11. + +**Table 6.6.5.5.7-11: Additional operating band unwanted emission limits for Band 48** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 3) | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|--------------------------------| +| All | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -13 dBm | 1 MHz | + +## 6.6.6 Spurious emission + +### 6.6.6.1 Definition and applicability + +The conducted transmitter spurious emission limits apply from 9 kHz to 12.75 GHz, excluding the following RAT-specific frequency ranges: + +- UTRA TDD BS, 1.28 Mcps option as specified in TS 25.105 [3]: from 4 MHz below the lowest frequency of each operating band to 4 MHz above the highest frequency of each operating band. +- UTRA FDD BS as specified in TS 25.104 [2]: from 12.5MHz below the lowest carrier frequency used up to 12.5MHz above the highest carrier frequency used. +- E-UTRA BS as specified in TS 36.104 [4]: from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band*, where $\Delta f_{\text{OBUE}}$ is defined clause 6.6.1. +- MSR BS as specified in TS 37.104 [5]: from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band*, where $\Delta f_{\text{OBUE}}$ is defined clause 6.6.1. + +For some operating bands the upper frequency limit is higher than 12.75 GHz in order to comply with the 5th harmonic limit of the *downlink operating band*, as specified in ITU-R recommendation SM.329 [14]. In some exceptional cases, requirements apply also closer than $\Delta f_{\text{OBUE}}$ MHz from the *downlink operating band*; these cases are highlighted in the requirement tables in respective referenced UTRA, E-UTRA or MSR specifications. For operating bands supported by *multi-band TAB connectors* exclusion bands apply to each supported band. + +The requirements applies for both single band and multiband *TAB connectors* (except for frequencies at which exclusion bands or other multi-band provisions apply) and for all transmission modes foreseen by the manufacturer's specification. Unless otherwise stated, all requirements are measured as mean power. + +For operation in region 2, where the FCC guidance for MIMO systems in [38] is applicable, $N_{\text{TXU, counted per cell}}$ shall be equal to 1 for the purposes of calculating the spurious emissions limits in clauses 6.6.6. For all other unwanted + +emissions requirements, $N_{TXU, countedpercell}$ shall be the value calculated according to clause 6.1, unless stated differently in regional regulation. + +The AAS BS test requirements for co-location spurious emissions limits which are specified for Band 46 in TS 37.104 [5], are applicable for AAS BS. + +For BS operating in bands n50, n51, n74, n75 and n76 additional emission limits that might be applicable in the spurious emissions frequency domain are specified in clause 6.6.5.5.4.6. + +#### 6.6.6.2 Minimum requirement + +The minimum requirement for MSR operation are defined in TS 37.105 [8], clause 6.6.6.2. + +The minimum requirement for UTRA operation are defined in TS 37.105 [8], clause 6.6.6.3. + +The minimum requirement for E-UTRA operation are defined in TS 37.105 [8], clause 6.6.6.4. + +#### 6.6.2.3 Test purpose + +This test measures conducted spurious emission from the AAS BS transmit *TAB connector(s)*, while the transmitter unit associated with the *TAB connector* under test is in operation. + +#### 6.6.6.4 Method of test + +##### 6.6.6.4.1 Initial conditions + +Test environment: + +- normal; see clause B.2. + +RF channels to be tested for single carrier: + +- B when testing the spurious frequencies below $F_{DL\_low} - \Delta f_{OBUE}$ , +- T when testing the spurious frequencies above $F_{DL\_high} + \Delta f_{OBUE}$ ; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $B_{RFBW}$ when testing the spurious frequencies below $F_{DL\_low} - \Delta f_{OBUE}$ , +- $T_{RFBW}$ when testing the spurious frequencies above $F_{DL\_high} + \Delta f_{OBUE}$ in single-band operation; see clause 4.12.1; +- $B_{RFBW\_T'_{RFBW}}$ when testing the spurious frequencies below $F_{DL\_low} - \Delta f_{OBUE}$ of the lowest operating band; + $B_{RFBW\_T'_{RFBW}}$ when testing the spurious frequencies below $F_{DL\_low} - \Delta f_{OBUE}$ of the lowest operating band in multi-band operation, see clause 4.12.1. + +##### 6.6.6.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.3. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.1.3. All *TAB connectors* not under test shall be terminated. +- 2) Measurements shall use a measurement bandwidth in accordance to the conditions in clause 6.6.6.5. +- 3) The measurement device characteristics shall be: + - Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +4) Set the *TAB connector* to transmit: + +a) For MSR: + +- Set the *TAB connector* to transmit maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.11. + +b) For UTRA: + +- For a *TAB connector* declared to be capable of single carrier operation only, set the *TAB connector* to transmit a signal according to TM1, clause 4.12.2, at the manufacturer's declared rated output power, $P_{\text{rated,c,TABC}}$ . +- For a *TAB connector* declared to be capable of multi-carrier operation, set the *TAB connector* to transmit according to TM1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +c) For E-UTRA: + +- *TAB connector* declared to be capable of single carrier operation only, set the *TAB connector* to transmit a signal according to E-TM1.1 in clause 4.12.2, at manufacturer's declared rated output power $P_{\text{rated,c,TABC}}$ . +- For a *TAB connector* declared to be capable of multi-carrier and/or CA operation, set the *TAB connector* to transmit according to E-TM1.1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +5) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the test requirement in clause 6.6.6.5. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 6.6.6.5 Test requirements + +### 6.6.6.5.1 General + +Conformance may be shown to either the measure and sum test requirement or the per *TAB connector* test requirement: + +- 1) The spurious emission test requirements for an AAS BS when using the measure and sum alternative are that for each *TAB connector TX cell group* and each applicable *basic limit* as specified in this clause, the power summation of emissions at the *TAB connectors* of the *TAB connector TX cell group* shall not exceed a limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{\text{TXU,countedpercell}})$ , unless stated differently in regional regulation. +- 2) The spurious emission test requirements for an AAS BS when using the per *TAB connector* alternative are that for each *TAB connector TX cell group* and each applicable *basic limit* as specified in this clause, the emissions at each of the *TAB connectors* of the *TAB connector TX cell group* shall not exceed a limit specified as the *basic limit* + X - $10\log(n)$ where n is the number of *TAB connectors* in the *TAB connector TX cell group* and $X = 10\log_{10}(N_{\text{TXU,countedpercell}})$ , unless stated differently in regional regulation. + +The appropriate table for the basic limit is based on the same power level ( $P_{\text{Rated,c,sys}}$ ) as used for the AAS BS rated power limits for BS classes in table 6.2.2.1-1 the same method of scaling the power level using $N_{\text{TXU,counted}}$ is used. + +### 6.6.6.5.2 Basic limits + +#### 6.6.6.5.2.1 General + +The basic limits specified in tables 6.6.6.5.2.2-1 to table 6.6.6.5.2.6-3 are applicable for the *TAB connector* under test. + +The test requirements of either clause 6.6.6.5.2.2 (Category A limits) or clause 6.6.6.5.2.3 (Category B limits) shall apply. In addition for a *TAB connector* operating in Band Category 2, the test requirements of 6.6.6.5.2.4 shall apply in case of Category B limits. + +#### 6.6.6.5.2.2 Spurious emissions (Category A) + +The basic limit of any spurious emission shall not exceed the limits in table 6.6.6.5.2.2 -1 + +**Table 6.6.6.5.2.2 -1: Spurious emission limits, Category A** + +| Frequency range | Basic limit | Measurement Bandwidth | Notes | +|--------------------------------------------------------------------------------------------------|-------------|-----------------------|----------------| +| 9kHz - 150 kHz | -13 dBm | 1 kHz | Note 1 | +| 150 kHz - 30 MHz | | 10 kHz | Note 1 | +| 30 MHz - 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 operating band in GHz | | 1 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in Recommendation ITU-R SM.329 [13], s4.1 +NOTE 2: Bandwidth as in Recommendation ITU-R SM.329 [13], s4.1. Upper frequency as in Recommendation ITU-R SM.329 [13], s2.5 table 1 +NOTE 3: For E-UTRA applies only for Bands 22, 42, 43 and 48. +NOTE 4: For UTRA applies only for Band XXII. + +#### 6.6.6.5.2.3 Spurious emissions (Category B) + +For MSR and E-UTRA the basic limits of is in table 6.6.6.5.2.3-1. + +For UTRA FDD the basic limits of is in tables 6.6.6.5.2.3-2 and 6.6.6.5.2.3-3. + +For UTRA TDD the basic limits of is in table 6.6.6.5.2.3-2. + +**Table 6.6.6.5.2.3-1: Spurious emissions limits, Category B** + +| Frequency range | Basic limit | Measurement Bandwidth | Notes | +|--------------------------------------------------------------------------------------------------|-------------|-----------------------|----------------| +| 9 kHz ↔ 150 kHz | -36 dBm | 1 kHz | Note 1 | +| 150 kHz ↔ 30 MHz | | 10 kHz | Note 1 | +| 30 MHz ↔ 1 GHz | | 100 kHz | Note 1 | +| 1 GHz ↔ 12.75 GHz | | 1 MHz | Note 2 | +| 12.75 GHz ↔ 5 th harmonic of the upper frequency edge of the DL operating band in GHz | | 1 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in Recommendation ITU-R SM.329 [13], s4.1. +NOTE 2: Bandwidth as in Recommendation ITU-R SM.329 [13], s4.1. Upper frequency as in Recommendation ITU-R SM.329 [13], s2.5 table 1. +NOTE 3: Applies only for Bands 22, 42, 43 and 48. + +**Table 6.6.6.5.2.3-2: Mandatory spurious emissions basic limits, UTRA FDD in operating band I, II, III, IV, VII, X, XXV, XXXII (Category B) and UTRA TDD** + +| Band | Basic limit | Measurement Bandwidth | Notes | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|----------------| +| 9 kHz $\leftrightarrow$ 150 kHz | -36 dBm | 1 kHz | Note 1 | +| 150 kHz $\leftrightarrow$ 30 MHz | -36 dBm | 10 kHz | Note 1 | +| 30 MHz $\leftrightarrow$ 1 GHz | -36 dBm | 100 kHz | Note 1 | +| 1 GHz $\leftrightarrow$ $F_{\text{low}}$ - 10 MHz | -30 dBm | 1 MHz | Note 1 | +| $F_{\text{low}}$ - 10 MHz $\leftrightarrow$ $F_{\text{high}}$ + 10 MHz | -15 dBm | 1 MHz | Note 2 | +| $F_{\text{high}}$ + 10 MHz $\leftrightarrow$ 12.75 GHz | -30 dBm | 1 MHz | Note 3 | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the DL operating band in GHz | -30 dBm | 1 MHz | Note 3, Note 4 | +| NOTE 1: Bandwidth as in Recommendation ITU-R SM.329 [35], s4.1. | | | | +| NOTE 2: Limit based on Recommendation ITU-R SM.329 [35], s4.3 and Annex 7. | | | | +| NOTE 3: Bandwidth as in Recommendation ITU-R SM.329 [35], s4.1. Upper frequency as in ITU-R SM.329 [35], s2.5 table 1. | | | | +| NOTE 4: UTRA FDD applies only for Band XXII. | | | | +| Key:
$F_{\text{low}}$ : The lowest downlink frequency of the operating band as defined in clause 4.5.
$F_{\text{high}}$ : The highest downlink frequency of the operating band as defined in clause 4.5. | | | | + +**Table 6.6.6.5.2.3-3: Mandatory spurious emissions basic limits, UTRA in operating band V, VIII, XII, XIII, XIV, XX, XXVI (Category B)** + +| Band | Basic limit | Measurement Bandwidth | Notes | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|--------| +| 9 kHz $\leftrightarrow$ 150 kHz | -36 dBm | 1 kHz | Note 1 | +| 150 kHz $\leftrightarrow$ 30 MHz | -36 dBm | 10 kHz | Note 1 | +| 30 MHz $\leftrightarrow$ $F_{\text{low}}$ - 10 MHz | -36 dBm | 100 kHz | Note 1 | +| $F_{\text{low}}$ - 10 MHz $\leftrightarrow$ $F_{\text{high}}$ + 10 MHz | -16 dBm | 100 kHz | Note 2 | +| $F_{\text{high}}$ + 10 MHz $\leftrightarrow$ 1 GHz | -36 dBm | 100 kHz | Note 1 | +| 1GHz $\leftrightarrow$ 12.75GHz | -30 dBm | 1 MHz | Note 3 | +| NOTE 1: Bandwidth as in Recommendation ITU-R SM.329 [35], s4.1. | | | | +| NOTE 2: Limit based on Recommendation ITU-R SM.329 [35], s4.3 and Annex 7. | | | | +| NOTE 3: Bandwidth as in Recommendation ITU-R SM.329 [35], s4.1. Upper frequency as in ITU-R SM.329 [35], s2.5 table 1. | | | | +| Key:
$F_{\text{low}}$ : The lowest downlink frequency of the operating band as defined in clause 4.5.
$F_{\text{high}}$ : The highest downlink frequency of the operating band as defined in clause 4.5. | | | | + +#### 6.6.6.5.2.4 Protection of the BS receiver of own or different BS + +This requirement shall be applied for FDD operation in order to prevent the receivers of Base Stations being desensitised by emissions from the transmitter *TAB connector*. It is measured at the transmit *TAB connector* for any type of *TAB connector* which has common or separate Tx/Rx antenna ports. + +The basic limit of any spurious emission shall not exceed the limits in table 6.6.6.5.2.4 -1, depending on the declared Base Station class and Band Category. + +**Table 6.6.6.5.2.4-1: Spurious emissions basic limits for protection of the BS receiver** + +| | Frequency range | UTRA basic limit | E-UTRA basic limit | Measurement bandwidth | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------------|-----------------------| +| Wide Area BS | $F_{\text{UL\_low}}$ - $F_{\text{UL\_high}}$ | -96 dBm | -96 dBm | 100 kHz | +| Medium Range BS | $F_{\text{UL\_low}}$ - $F_{\text{UL\_high}}$ | -86 dBm | -91 dBm | 100 kHz | +| Local Area BS | $F_{\text{UL\_low}}$ - $F_{\text{UL\_high}}$ | -82 dBm | -88 dBm | 100 kHz | +| Note: | For E-UTRA Band 28 BS operating in regions where Band 28 is only partially allocated for E-UTRA operations, this requirement only applies in the UL frequency range of the partial allocation. | | | | + +#### 6.6.6.5.2.5 Co-existence with other systems in the same geographical area + +These requirements may be applied for the protection of system operating in frequency ranges other than the *TAB connector* downlink operating band. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the AAS BS, or they may be set by local or regional regulation as a mandatory requirement for an operating band. It is in some cases not stated in the present document whether a requirement is mandatory or under what exact circumstances that a limit applies, since this is set by local or regional regulation. An overview of regional requirements in the present document is given in clause 4.4. + +Some requirements may apply for the protection of specific equipment (UE, MS and/or BS) or equipment operating in specific systems (GSM/EDGE, CDMA, UTRA, E-UTRA, NR, etc.) as listed below. The basic limit any spurious emission are in table 6.6.6.5.2.5-1 for *TAB connector(s)* where requirements for co-existence with the system listed in the first column apply. For *multi-band TAB connector(s)*, the exclusions and conditions in the Note column of table 6.6.6.5.2.5-1 apply for each supported operating band. + +**Table 6.6.6.5.2.5-1: Spurious emissions basic limits for co-existence with systems operating in other frequency bands** + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-----------------------------------------------------|-----------------------------------|-------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | -57 dBm | 100 kHz | This requirement does not apply to UTRA FDD operating in band VIII.
This requirement does not apply to E-UTRA BS operating in band 8 or NR BS operating in band n8 | +| | 876 - 915 MHz | -61 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to UTRA FDD operating in band VIII, since it is already covered by the requirement in clause 6.6.6.5.2.4.
For the frequency range 880-915 MHz, this requirement does not apply to E-UTRA BS operating in band 8 or NR BS operating in band n8, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| DCS1800 | 1805 - 1880 MHz | -47 dBm | 100 kHz | This requirement does not apply to UTRA FDD operating in band III.
This requirement does not apply to UTRA TDD operating in Band b and c. For UTRA TDD BS operating in Band f, it applies for 1805 - 1850 MHz
This requirement does not apply to E-UTRA BS operating in band 3 or NR BS operating in band n3. | +| | 1710 - 1785 MHz | -61 dBm | 100 kHz | This requirement does not apply to UTRA FDD operating in band III, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD operating in Band b and c. For UTRA TDD BS operating in Band f, it applies for 1710 - 1755 MHz
This requirement does not apply to E-UTRA BS operating in band 3 or NR BS operating in band n3, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| PCS1900 | 1930 - 1990 MHz | -47 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band II or band XXV.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in frequency band 2, band 25 or band 36 or NR BS operating in band n2 or n25. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-----------------------------------------------------|-----------------------------------|-----------------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 1850 - 1910 MHz | -61 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band II or band XXV, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in frequency band 2 or 25 or NR BS operating in band n2 or n25, since it is already covered by the requirement in clause 6.6.6.5.2.4. This requirement does not apply to E-UTRA BS operating in frequency band 35. | +| GSM850 or CDMA850 | 869 - 894 MHz | -57 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band V or XXVI.
This requirement does not apply to E-UTRA BS operating in frequency band 5 or 26 or NR BS operating in band n5 or n26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -61 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band V or XXVI, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to E-UTRA BS operating in frequency band 5 or 26 or NR BS operating in band n5 or n26, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band I,
This requirement does not apply to E-UTRA BS operating in band 1 or 65 or NR BS operating in band n1 or n65. | +| | 1920 - 1980 MHz | -49 dBm
(UTRA TDD -43 dBm for WA BS -40 dBm for LA BS) | 1 MHz
(UTRA TDD 3.84 MHz) | This requirement does not apply to UTRA FDD BS operating in band I, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to E-UTRA BS operating in band 1 or 65 or NR BS operating in band n1 or n65, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band II or band XXV4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 2 or 25 or NR BS operating in band n2 or n25. | +| | 1850 - 1910 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band II or band XXV, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 2 or 25 or NR BS operating in band n2, since it is already covered by the requirement in clause 6.6.6.5.2.4 | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III or band IX
For UTRA TDD BS operating in Band f, it applies for 1805- 1850 MHz
This requirement does not apply to E-UTRA BS operating in band 3 or NR BS operating in band n3. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|--------------------------------------------------------------------|-----------------------------------|---------------------------------------------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 1710 - 1785 MHz | -49 dBm

(UTRA TDD -43 dBm for WA BS -40 dBm for LA BS) | 1 MHz

(UTRA TDD 3.84 MHz) | This requirement does not apply to UTRA FDD BS operating in band III, since it is already covered by the requirement in clause 6.6.6.5.2.4.
For UTRA BS operating in band IX, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in clause 6.6.6.5.2.4.
This requirement does not apply to E-UTRA BS operating in band 3 or 9 or NR BS operating in band n3, since it is already covered by the requirement in clause 6.6.6.5.2.4.
For UTRA TDD BS operating in Band f, it applies for 1710- 1755 MHz
For E-UTRA BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in clause 6.6.6.5.2.4. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band IV or band X
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 4, 10 or 66 | +| | 1710 - 1755 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band IV or band X, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 4, 10 or 66, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or XXVI
This requirement does not apply to E-UTRA BS operating in band 5 or 26 or NR BS operating in band n5 or n26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -49 dBm

(UTRA TDD -43 dBm for WA BS -40 dBm for LA BS) | 1 MHz

(UTRA TDD 3.84 MHz) | This requirement does not apply to UTRA FDD BS operating in band V or XXVI, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to E-UTRA BS operating in band 5 or 26 or NR BS operating in band n5 or n26, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| UTRA FDD Band VI or XIX, or E-UTRA Band 6, 18 or 19 or NR band n18 | 860 - 890 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VI or XIX
For UTRA TDD applicable in Japan
This requirement does not apply to E-UTRA BS operating in band 6, 18, 19.
This requirement does not apply to NR BS operating in band n18. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-----------------------------------------------------|-----------------------------------|--------------------------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 815 - 845 MHz | -49 dBm
(UTRA TDD -43 dBm) | 1 MHz
(UTRA TDD 3.84 MHz) | This requirement does not apply to UTRA FDD BS operating in band VI or XIX, since it is already covered by the requirement in clause 6.6.6.5.2.4.
For UTRA TDD applicable in Japan
This requirement does not apply to E-UTRA BS operating in band 18 between 815-830 MHz, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to E-UTRA BS operating in band 6, 19 between 830-845 MHz, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to NR BS operating in band n18 between 815-830 MHz, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 - 2690 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VII,
This requirement does not apply to E-UTRA BS operating in band 7 or NR BS operating in band n7.
This requirement does not apply to E-UTRA BS operating in band 7 or NR BS operating in band n7, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| | 2500 - 2570 MHz | -49 dBm
(UTRA TDD -43 dBm for WA BS
-40 dBm for LA BS) | 1 MHz
(UTRA TDD 3.84 MHz) | This requirement does not apply to UTRA FDD BS operating in band VII or E-UTRA BS operation in band 7 or NR BS operating in band n7, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VIII.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 8 or NR BS operating in band n8. | +| | 880 - 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VIII, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 8 or NR BS operating in band n8, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | -52 dBm
(UTRA TDD -43 dBm) | 1 MHz
(UTRA TDD 3.84 MHz) | This requirement does not apply to UTRA FDD BS operating in band III or band IX
For UTRA TDD applicable in Japan
This requirement does not apply to E-UTRA BS operating in band 3 or 9 or NR BS operating in band n3. | +| | 1749.9 - 1784.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III or band IX, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to E-UTRA BS operating in band 3 or 9 or NR BS operating in band n3, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band IV or band X
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 4, 10 or 66 | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-----------------------------------------------------|-----------------------------------|-------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 1710 - 1770 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band X, since it is already covered by the requirement in clause 6.6.6.5.2.4. For UTRA FDD BS operating in Band IV, it applies for 1755 MHz to 1770 MHz, while the rest is covered in clause 6.6.6.5.2.4. This requirement does not apply to UTRA TDD. This requirement does not apply to E-UTRA BS operating in band 10 or 66 or NR BS operating in band n66, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 4, it applies for 1755 MHz to 1770 MHz, while the rest is covered in clause 6.6.6.5.2.4. | +| 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 BS operating in band XI, XXI, or XXXII. For UTRA TDD applicable in Japan. This requirement does not apply to E-UTRA BS operating in band 11, 21 or 32. This requirement does not apply to NR BS operating in n92 or n94. | +| | 1427.9 - 1447.9 MHz | -49 dBm
(UTRA TDD -43 dBm) | 1 MHz
(UTRA TDD 3.84 MHz) | This requirement does not apply to UTRA FDD BS operating in band XI, since it is already covered by the requirement in clause 6.6.6.5.2.4. For UTRA BS operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. For UTRA TDD applicable in Japan. This requirement does not apply to E-UTRA BS operating in band 11, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in band 32, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. This requirement does not apply to NR BS operating in n91, n92, n93 or n94. | +| | 1447.9 - 1462.9 MHz | -49 dBm
(UTRA TDD -43 dBm) | 1 MHz
(UTRA TDD 3.84 MHz) | This requirement does not apply to UTRA FDD BS operating in band XXI, since it is already covered by the requirement in clause 6.6.6.5.2.4. For UTRA BS operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. For UTRA TDD applicable in Japan up to 1462.9MHz. This requirement does not apply to E-UTRA BS operating in band 21, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in band 32, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. This requirement does not apply to NR BS operating in n92 or n94. | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII. This requirement does not apply to UTRA TDD. This requirement does not apply to E-UTRA BS operating in band 12 or 85, nor NR BS operating in band n12. | +| | 699 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII, since it is already covered by the requirement in clause 6.6.6.5.2.4. This requirement does not apply to UTRA TDD. This requirement does not apply to E-UTRA BS operating in band 12 or 85, nor NR BS operating in band n12, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 29 or NR BS operating in Band n29, it applies 1 MHz below the Band 29 downlink operating band (Note 6) | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-----------------------------------------------------|-----------------------------------|-------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIII
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 13, nor NR BS operating in band n13. | +| | 777 - 787 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIII, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 13, nor NR BS operating in band n13, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 - 768 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIV
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 14. | +| | 788 - 798 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIV, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 14, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| E-UTRA Band 17 | 734 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 17. | +| | 704 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 17, since it is already covered by the requirement in clause 6.6.4.5.3. For E-UTRA BS operating in Band 29 or NR BS operating in Band n29, it applies 1 MHz below the Band 29 downlink operating band (Note 6) | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 791 - 821 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XX
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 20 or 28 or NR BS operating in band n20. | +| | 832 - 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XX, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 20 or NR BS operating in band n20, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 -3590 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXII
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 22, 42 or 48. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-----------------------------------------------------|-----------------------------------|-------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 3410 -3490 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXII, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 22, since it is already covered by the requirement in clause 6.6.4.5.3. This requirement does not apply to E-UTRA BS operating in Band 42 | +| E-UTRA Band 24 or NR band n24 | 1525 - 1559 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 24.
This requirement does not apply to UTRA TDD | +| | 1626.5 - 1660.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 24, since it is already covered by the requirement in clause 6.6.6.5.2.4. This requirement does not apply to UTRA TDD | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 - 1995 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band II or band XXV
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 2 or 25 or NR BS operating in band n2 or n25. | +| | 1850 - 1915 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXV, since it is already covered by the requirement in clause 6.6.6.5.2.4. For UTRA FDD BS operating in Band II, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 25, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 2 or NR BS operating in band n2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.6.6.5.2.4. | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859-894 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or band XXVI
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 5 or 26 or NR BS operating in band n5 or n26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 814-849 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXVI, since it is already covered by the requirements in clause 6.6.6.5.2.4. For UTRA FDD BS operating in band V, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.6.3.2
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 26 or NR BS operating in band n26, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 5 or NR BS operating in band n5, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| E-UTRA Band 27 | 852 - 869 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in Band V or XXVI.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in Band 5, 26 or 27 or NR BS operating in band n5. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|------------------------------------------------------|-----------------------------------|-------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 807 - 824 MHz | -49 dBm | 1 MHz | For UTRA BS operating in Band XXVI, it applies for 807 MHz to 814 MHz, while the rest is covered in clause 6.6.6.5.2.4.
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in Band 27, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 26, it applies for 807 MHz to 814 MHz, while the rest is covered in clause 6.6.6.5.2.4.
This requirement also applies to E-UTRA BS operating in Band 28, starting 4 MHz above the Band 28 downlink operating band (Note 5). | +| E-UTRA Band 28 or NR band n28 | 758 - 803 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 20, 28, 44, 67 or 68.
This requirement does not apply to UTRA TDD | +| | 703 - 748 MHz | -49 MHz | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 28, since it is already covered by the requirement in clause 6.6.6.5.2.4. This requirement does not apply to E-UTRA BS operating in Band 44.
This requirement does not apply to UTRA TDD
For E-UTRA BS operating in Band 67, it applies for 703 MHz to 736 MHz. For E-UTRA BS operating in Band 68, it applies for 728MHz to 733 MHz. | +| E-UTRA Band 29 or NR Band n29 | 717 - 728 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA TDD.
This requirement does not apply to E-UTRA BS operating in Band 29 or 85 | +| E-UTRA Band 30 or NR band n30 | 2350 - 2360 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA TDD.
This requirement does not apply to E-UTRA BS operating in band 30 or 40 or NR BS operating in band n40. | +| | 2305 - 2315 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA TDD.
This requirement does not apply to E-UTRA BS operating in band 30, since it is already covered by the requirement in clause 6.6.6.5.2.4. This requirement does not apply to E-UTRA BS operating in Band 40 or NR BS operating in band n40. | +| E-UTRA Band 31 or NR Band n31 | 462.5 -467.5 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA TDD.
This requirement does not apply to E-UTRA BS operating in band 31, 72, 73. | +| | 452.5 -457.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA TDD.
This requirement does not apply to E-UTRA BS operating in band 31, since it is already covered by the requirement in clause 6.6.6.5.2.4. This requirement does not apply to E-UTRA BS operating in band 72 or 73. | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in Band XI, XXI, or XXXII
This requirement does not apply to UTRA TDD
This requirement does not apply to E-UTRA BS operating in band 11, 21 or 32.
This requirement does not apply to NR BS operating in n92 or n94. | +| UTRA TDD in Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 33. | +| UTRA TDD in Band a) or E-UTRA Band 34 or NR band n34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 34 or NR BS operating in band n34. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|------------------------------------------------------|-----------------------------------|-------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 - 1910 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS. This requirement does not apply to E-UTRA BS operating in Band 35. | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS. This requirement does not apply to E-UTRA BS operating in Band 2 and 36 or NR BS operating in band n2. | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS. This is not applicable to E-UTRA BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD in Band d) or E-UTRA Band 38 or NR band n38 | 2570 - 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 38 or 69 or NR BS operating in band n38. | +| UTRA TDD in Band f) or E-UTRA Band 39 or NR band n39 | 1880 - 1920 MHz | -52 dBm | 1 MHz | Applicable in China for UTRA FDD. This is not applicable to E-UTRA BS operating in Band 39. | +| UTRA TDD in Band e) or E-UTRA Band 40 or NR band n40 | 2300 - 2400 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 30 or 40 or NR BS operating in band n40. | +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 41 or 53 or NR BS operating in band n41 or n53. | +| E-UTRA Band 42 | 3400 - 3600 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 22, 42, 43, 48, 52. | +| E-UTRA Band 43 | 3600 - 3800 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA TDD. This is not applicable to E-UTRA BS operating in Band 42, 43 or 48. | +| E-UTRA Band 44 | 703 - 803 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 - 1467 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS. This is not applicable to E-UTRA BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 22, 42, 43 or 48. | +| E-UTRA Band 49 | 3550 – 3700 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 22, 42, 43, 48. | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76, n91, n92, n93 or n94. | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76, n91, n92, n93 or n94. | +| E-UTRA Band 52 | 3300 – 3400 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 42 or 52. | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 41 or 53 or NR BS operating in band n41 or n53. | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 54. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-----------------------------------------------------|-----------------------------------|-------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 65 or NR band n65 | 2110 - 2200 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS. This requirement does not apply to E-UTRA BS operating in band 1 or 65 or NR BS operating in band n1 or n65. | +| | 1920 - 2010 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA BS. This requirement does not apply to E-UTRA BS operating in band 65 or NR BS operating in band n65, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 1 or NR BS operating in band n1, it applies for 1980 MHz to 2010 MHz, while the rest is covered in clause 6.6.6.5.2.4. | +| E-UTRA Band 66 or NR band n66 | 2110 - 2200 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS. This requirement does not apply to E-UTRA BS operating in band 4, 10, 23 or 66. | +| | 1710 - 1780 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA BS. This requirement does not apply to E-UTRA BS operating in band 66, since it is already covered by the requirement in clause 6.6.4.5.3. For E-UTRA BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in clause 6.6.6.5.2.4. | +| E-UTRA Band 67 or NR band n67 | 738 - 758 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS. This requirement does not apply to E-UTRA BS operating in Band 28 or 67. | +| E-UTRA Band 68 | 753 - 783 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA BS. This requirement does not apply to E-UTRA BS operating in band 28, or 68. | +| | 698-728 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA BS. This requirement does not apply to E-UTRA BS operating in band 68, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 28, it applies between 698 MHz and 703 MHz, while the rest is covered in clause 6.6.6.5.2.4. | +| E-UTRA Band 69 | 2570 - 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 38 or 69. | +| E-UTRA Band 70 or NR band n70 | 1995 - 2020 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 2, 25 or 70 or NR BS operating in band n2 or n25. | +| | 1695 – 1710 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 70, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| E-UTRA Band 71 or NR Band n71 | 617 – 652 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band n71 or n105 | +| | 663 – 698 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n71 or n105, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| E-UTRA Band 72 or NR Band n72 | 461 – 466 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 31, 72 and or 73. | +| | 451 – 456 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 72, since it is already covered by the requirement in clause 6.6.6.5.2.4. This requirement does not apply to E-UTRA BS operating in band 73. | +| E-UTRA Band 73 | 460 - 465 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 31, 72 or 73. | +| | 450 - 455 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 73, since it is already covered by the requirement in clause 6.6.6.5.2.4. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-----------------------------------------------------|-----------------------------------|------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 74 or NR Band n74 | 1475 – 1518 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band n50, n74, n75, n92 or n94. | +| | 1427 – 1470 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n50, n51, n74, n75, n76, n91, n92, n93 or n94. | +| E-UTRA Band 75 or NR Band n75 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76, n91, n92, n93 or n94. | +| E-UTRA Band 76 or NR Band n76 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76, n91, n92, n93 or n94. | +| NR Band n77 | 3.3 – 4.2 GHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 22, 42, 43, 48, 52, n77 and n78 | +| NR Band n78 | 3.3 – 3.8 GHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 22, 42, 43, 48, 52, n77 and n78 | +| NR Band n79 | 4.4 – 5.0 GHz | -52 dBm | 1 MHz | | +| NR Band n80 | 1710 – 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n3, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| NR Band n81 | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n8, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| NR Band n82 | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n20, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| NR Band n83 | 703 – 748 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n28, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| NR Band n84 | 1920 – 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n1, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| E-UTRA Band 85 or NR band n85 | 728 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 12/n12, 29 or 85. | +| | 698 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 12/n12 or 85, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 29 or NR BS operating in Band n29, it applies 1 MHz below the Band 29 downlink operating band (Note 6). | +| NR Band n86 | 1710 – 1780 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n66, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| E-UTRA Band 87 | 420 - 425 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 87 or 88. | +| | 410 – 415 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 87, since it is already covered by the requirement in clause 6.6.4.2 | +| E-UTRA Band 88 | 422 - 427 MHz | -52 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 87 or 88. | +| | 412 – 417 MHz | -49 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 88, since it is already covered by the requirement in clause 6.6.4.2. This requirement does not apply to E-UTRA BS operating in band 87. | +| NR Band n89 | 824 - 849 MHz | -49 dBm

(UTRA TDD -43 dBm for WA BS
-40 dBm for LA BS) | 1 MHz

(UTRA TDD 3.84 MHz) | This requirement does not apply to NR BS operating in band n5, since it is already covered by the requirement in clause 6.6.6.5.2.4. For E-UTRA BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-----------------------------------------------------|-----------------------------------|-------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n91 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76, n91, n92, n93 or n94. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n20, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| NR Band n92 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76, n91, n92, n93 or n94. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n20, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| NR Band n93 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76, n91, n92, n93 or n94. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n8, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| NR Band n94 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76, n91, n92, n93 or n94. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n8, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| NR Band n95 | 2010 - 2025 MHz | -52 dBm | 1 MHz | | +| NR band n96 | 5925 – 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n97 | 2300 - 2400 MHz | -52 dBm | 1 MHz | | +| NR Band n98 | 1880 - 1920 MHz | -52 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n24, since it is already covered by the requirement in clause 6.6.6.5.2.4. | +| E-UTRA Band 103 | 757 – 758 MHz | -52 dBm | 1 MHz | | +| | 787 – 788 MHz | -49 dBm | 1 MHz | | +| NR Band n104 | 6425 – 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n105 | 612 – 652 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n71 or n105 | +| | 663 – 703 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in n105, since it is already covered by the requirement in clause 6.6.5.2.2. | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 106. | +| | 896 – 901 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 106, since it is already covered by the requirement in clause 6.6.6.5.2.4.
This requirement does not apply to BS operating in band 5 or 26. | +| NR band n109 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74/n74, 75/n75 or 76/n76. | +| | 703 – 733 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band 28/n28, since it is already covered by the requirement in clause 6.6.6.5.2.4. This requirement does not apply to E-UTRA BS operating in Band 44. For E-UTRA BS operating in Band 68, it applies for 728MHz to 733 MHz. | + +| System type operating in the same geographical area | Band for co-existence requirement | Basic limit | Measurement Bandwidth | Notes | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------|-----------------------|-------| +| NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the downlink operating band (see clause 4.5.). 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. | | | | | + +- NOTE 1: As defined in the scope for spurious emissions in this clause, except for the cases where the noted requirements apply to a BS operating in Band 25/n25, Band 27, Band 28/n28 or Band 29, the co-existence requirements in Table 6.6.6.5.2.5-1 do not apply for the 10 MHz frequency range immediately outside the downlink operating band (see Tables 4.5-1 and 4.5-2). Emission limits for this excluded frequency range may be covered by local or regional requirements. +- NOTE 2: Table 6.6.6.5.2.5-1 assumes that two operating bands, where the frequency ranges in table 4.4-1 or table 4.4-2 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 3: For the protection of DCS1800, UTRA Band III, E-UTRA Band 3 or NR Band n3 in China, the frequency ranges of the downlink and uplink protection requirements are 1805 – 1850 MHz and 1710 – 1755 MHz respectively. +- NOTE 4: TDD base stations deployed in the same geographical area, that are synchronized and use the same or adjacent operating bands can transmit without additional co-existence requirements. For unsynchronized base stations, special co-existence requirements may apply that are not covered by the 3GPP specifications. +- NOTE 5: For Band 28/n28 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with Band 27 UL operating band. +- NOTE 6: For Band 29 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with UTRA Band XII, E-UTRA Band 12 or NR Band n12 UL operating band, E-UTRA Band 17 UL operating band or E-UTRA Band 85 UL operating band. + +The following requirement may be applied for the protection of PHS. This requirement is also applicable at specified frequencies falling between $\Delta f_{OBUE}$ below the lowest BS transmitter frequency of the downlink operating band and $\Delta f_{OBUE}$ above the highest BS transmitter frequency of the downlink operating band. + +The basic limit for any spurious emission is: + +**Table 6.6.6.5.2.5-2: Spurious emissions *basic limits* for co-existence with PHS** + +| Frequency range | Basic limit | Measurement Bandwidth | Notes | +|---------------------------------------------------|-------------|-----------------------|---------------------------------------------------------------------------| +| 1884.5 - 1915.7 MHz | -41 dBm | 300 kHz | Applicable for co-existence with PHS system operating in 1884.5-1915.7MHz | +| NOTE: The requirement is not applicable in China. | | | | + +**Table 6.6.6.5.2.5-3: Void** + +The following requirement shall be applied to *TAB connectors* operating in Bands 13 and 14 to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the BS transmitter operating band up to 10 MHz above the highest frequency of the BS transmitter operating band. The basic limit for any spurious emission is: + +**Table 6.6.6.5.2.5-4: Spurious emissions *basic limits* for protection of 700 MHz public safety operations** + +| Operating Band | Band | Basic limit | Measurement Bandwidth | +|----------------|---------------|--------------------|-----------------------| +| 13 | 763 - 775 MHz | -46 dBm | 6.25 kHz | +| 13 | 793 - 805 MHz | -46 dBm | 6.25 kHz | +| 14 | 769 - 775 MHz | -46 dBm | 6.25 kHz | +| 14 | 799 - 805 MHz | -46 dBm | 6.25 kHz | + +The following requirement shall be applied to *TAB connectors* operating in Band 26 to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the BS downlink operating band up to 10 MHz above the highest frequency of the BS downlink operating band. + +The basic limit for any spurious emission is: + +**Table 6.6.6.5.2.5-5: BS Spurious emissions *basic limits* for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Basic limit | Measurement Bandwidth | Notes | +|----------------|-----------------|-------------|-----------------------|---------------------------------------------------------| +| 26 | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5 kHz from the channel edge | + +**Table 6.6.6.5.2.5-6: Void** + +In addition to the requirements in clauses 6.6.6.5.2.1 to 6.6.6.5.2.5 and above in the present clause, the *TAB connector* may have to comply with the applicable emission limits established by FCC Title 47 [24], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +The following requirement may apply to a *TAB connector* operating in Band 30 in certain regions. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the BS downlink operating band up to 10 MHz above the highest frequency of the BS downlink operating band. + +The basic limit for any spurious emission is: + +**Table 6.6.6.5.2.5-7: Additional Spurious emissions *basic limits* for Band 30** + +| Frequency range | Basic limit | Measurement Bandwidth | | +|-----------------------|--------------------|-----------------------|--| +| 2200 MHz - 2345 MHz | -45 dBm | 1 MHz | | +| 2362.5 MHz - 2365 MHz | -25 dBm | 1 MHz | | +| 2365 MHz - 2367.5 MHz | -40 dBm | 1 MHz | | +| 2367.5 MHz - 2370 MHz | -42 dBm | 1 MHz | | +| 2370 MHz - 2395 MHz | -45 dBm | 1 MHz | | + +The following requirement may apply to E-UTRA BS operating in Band 48 in certain regions. The power of any spurious emission shall not exceed: + +**Table 6.6.6.5.2.5-8: Additional E-UTRA BS Spurious emissions limits for Band 48** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|----------------------------------------|---------------|-----------------------|-------------------------------------------------| +| 3530MHz – 3720MHz | -25dBm | 1 MHz | Applicable 10MHz from the assigned channel edge | +| 3100MHz – 3530MHz
3720MHz – 4200MHz | -40dBm | 1 MHz | | + +The following requirement may also apply to BS operating in Band 54 in certain regions. The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to Table 6.6.6.5.2.5-9 shall not exceed the maximum emission levels $P_{EM,B54,a}$ , $P_{EM,B54,b}$ , $P_{EM,B54,c}$ , $P_{EM,B54,d}$ , $P_{EM,B54,e}$ and $P_{EM,B54,f}$ declared by the manufacturer. + +**Table 6.6.6.5.2.5-9: Declared Band 54 emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range | Declared emission level (dBW)
(Measurement bandwidth = 1 MHz) | Declared emission level (dBW) of discrete emissions of less than 700 Hz bandwidth
(Measurement bandwidth = 1 kHz) | Declared emission level (dBW) of discrete emissions of less than 2 kHz bandwidth
(Measurement bandwidth = 1 kHz) | +|----------------|-----------------|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| 54 | 1541 - 1559 MHz | $P_{EM,B54,a}$ | | $P_{EM,B54,f}$ | +| | 1559 - 1610 MHz | $P_{EM,B54,b}$ | $P_{EM,B54,d}$ | | +| | 1610 - 1650 MHz | $P_{EM,B54,c}$ | $P_{EM,B54,e}$ | | + +Note: The regional requirements specified in attachment to the FCC reference document, 0007135419, are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The EIRP level is calculated using: $P_{EIRP} = P_E + G_{ant}$ where $P_E$ denotes the BS unwanted emission level at the antenna connector, $G_{ant}$ equals the BS antenna gain minus feeder loss. The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. + +#### 6.6.6.5.2.6 Co-location with other Base Stations + +These requirements may be applied for the protection of other BS receiver units when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA and/or NR BS are co-located with a BS. + +The requirements assume a 30 dB coupling loss between transmitter and receiver and are based on co-location with base stations of the same class. + +The basic limit for any spurious emission are in table 6.6.6.5.2.6-1 for a MSR, E-UTRA or UTRA FDD *TAB connector* or tables 6.6.6.5.2.6-2 and 6.6.6.5.2.6-3 for UTRA TDD, where requirements for co-location with a BS type listed in the first column apply, depending on the declared Base Station class. For a *multi-band TAB connector*, the exclusions and conditions in the Notes column of table 6.6.6.5.2.6-1 apply for each supported operating band. + +**Table 6.6.6.5.2.6-1: Spurious emissions basic limits for MSR, E-UTRA or UTRA (FDD) or NR BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Basic limit (WA BS) | Basic limit (MR BS) | Basic limit (LA BS) | Measurement Bandwidth | Notes | +|-----------------------|---------------------------------------------|---------------------|---------------------------|--------------------------------------|-----------------------|-------| +| GSM900 | 876 - 915 MHz | -98 dBm | -91 dBm | MSR -88 dBm,
UTRA, E-UTRA -70 dBm | 100 kHz | | +| DCS1800 | 1710 - 1785 MHz | -98 dBm | -91 dBm
(UTRA -96 dBm) | MSR -88 dBm,
UTRA, E-UTRA -80 dBm | 100 kHz | | +| PCS1900 | 1850 - 1910 MHz | -98 dBm | -91 dBm
(UTRA -96 dBm) | MSR -88 dBm,
UTRA, E-UTRA -80 dBm | 100 kHz | | + +| Type of co-located BS | Frequency range for co-location requirement | Basic limit (WA BS) | Basic limit (MR BS) | Basic limit (LA BS) | Measurement Bandwidth | Notes | +|-----------------------------------------------------|---------------------------------------------|---------------------|---------------------|-------------------------------------|-----------------------|---------------------------------------------------------------------| +| GSM850 or CDMA850 | 824 - 849 MHz | -98 dBm | -91 dBm | MSR -88 dBm
UTRA, E-UTRA -70 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 1920 - 1980 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1850 - 1910 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1710 - 1785 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 824 - 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 - 845 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2500 - 2570 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 880 - 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1447.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n91, n92, n93 or n94 | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 699 - 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 777 - 787 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 788 - 798 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 - 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 18 or NR band n18 | 815 - 830 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 832 - 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 - 1462.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n92 or n94 | + +| Type of co-located BS | Frequency range for co-location requirement | Basic limit (WA BS) | Basic limit (MR BS) | Basic limit (LA BS) | Measurement Bandwidth | Notes | +|-----------------------------------------------------|---------------------------------------------|---------------------------|---------------------|---------------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 - 3490 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 42 | +| E-UTRA Band 24 or NR band n24 | 1626.5 - 1660.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1850 - 1915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 814 - 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 27 | 807 - 824 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 28 or NR band n28 | 703 - 748 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | +| E-UTRA Band 30 or NR band n30 | 2305 - 2315 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 40 or n40 | +| E-UTRA Band 31 or NR Band n31 | 452.5 - 457.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -96 dBm
(UTRA -86 dBm) | -91 dBm
Note 4 | -88 dBm
(UTRA -78 dBm) | 100 kHz
(UTRA 1 MHz) | This is not applicable to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 - 2025 MHz | -96 dBm
(UTRA -86 dBm) | -91 dBm
Note 4 | -88 dBm
(UTRA -78 dBm) | 100 kHz
(UTRA 1 MHz) | This is not applicable to BS operating in Band 34 or n34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 - 1910 MHz | -96 dBm
(UTRA -86 dBm) | -91 dBm
Note 4 | -88 dBm
(UTRA -78 dBm) | 100 kHz
(UTRA 1 MHz) | This is not applicable to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -96 dBm
(UTRA -86 dBm) | -91 dBm
Note 4 | -88 dBm
(UTRA -78 dBm) | 100 kHz
(UTRA 1 MHz) | This is not applicable to BS operating in Band 2, n2 and 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -96 dBm
(UTRA -86 dBm) | -91 dBm
Note 4 | -88 dBm
(UTRA -78 dBm) | 100 kHz
(UTRA 1 MHz) | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 - 2620 MHz | -96 dBm
(UTRA -86 dBm) | -91 dBm
Note 4 | -88 dBm
(UTRA -78 dBm) | 100 kHz
(UTRA 1 MHz) | This is not applicable to BS operating in Band 38 or n38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 - 1920 MHz | -96 dBm
(UTRA -86 dBm) | -91 dBm
Note 4 | -88 dBm
(UTRA -78 dBm) | 100 kHz
(UTRA 1 MHz) | This is not applicable to BS operating in Band 33 and 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 - 2400 MHz | -96 dBm
(UTRA -86 dBm) | -91 dBm
Note 4 | -88 dBm
(UTRA -78 dBm) | 100 kHz
(UTRA 1 MHz) | This is not applicable to BS operating in Band 30 or 40 or n40 | + +| Type of co-located BS | Frequency range for co-location requirement | Basic limit (WA BS) | Basic limit (MR BS) | Basic limit (LA BS) | Measurement Bandwidth | Notes | +|-------------------------------|---------------------------------------------|-------------------------------|-----------------------|-------------------------------|-----------------------------|-----------------------------------------------------------------------------------------| +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 MHz | -96 dBm

(UTRA -86 dBm) | -91 dBm

Note 4 | -88 dBm

(UTRA -78 dBm) | 100 kHz

(UTRA 1 MHz) | This is not applicable to BS operating in Band 41 or 53 or n41 or n53 | +| E-UTRA Band 42 | 3400 - 3600 MHz | -96 dBm

(UTRA -86 dBm) | -91 dBm

Note 4 | -88 dBm

(UTRA -78 dBm) | 100 kHz

(UTRA 1 MHz) | This is not applicable to BS operating in Band 22, 42, 43, 48, 52 | +| E-UTRA Band 43 | 3600 - 3800 MHz | -96 dBm

(UTRA -86 dBm) | -91 dBm

Note 4 | -88 dBm

(UTRA -78 dBm) | 100 kHz

(UTRA 1 MHz) | This is not applicable to BS operating in Band 42 or 43, or 48 | +| E-UTRA Band 44 | 703 - 803 MHz | -96 dBm

(UTRA -86 dBm) | -91 dBm

Note 4 | -88 dBm

(UTRA -78 dBm) | 100 kHz

(UTRA 1 MHz) | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -96 dBm

(UTRA -86 dBm) | -91 dBm

Note 4 | -88 dBm

(UTRA -78 dBm) | 100 kHz

(UTRA 1 MHz) | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -96 dBm

(UTRA -86 dBm) | -91 dBm

Note 4 | -88 dBm

(UTRA -78 dBm) | 100 kHz

(UTRA 1 MHz) | This is not applicable to E-UTRA BS operating in Band 42, 43 or 48 | +| E-UTRA Band 49 | 3550 - 3700 MHz | N/A | N/A | (UTRA -78 dBm) | (UTRA 1 MHz) | | +| E-UTRA Band 50 or NR Band n50 | 1432 – 1517 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n51, n74, n75, n91, n92, n93 or n94 | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n50, n74, n75, n76, n91, n92, n93 or n94 | +| E-UTRA Band 52 | 3300 – 3400 MHz | -96 dBm
(UTRA -86 dBm) | -91 dBm | -88 dBm
(UTRA -78 dBm) | 100 kHz
(UTRA 1 MHz) | This is not applicable to E-UTRA BS operating in Band 42 or 52 | +| E-UTRA Band 53 or NR band n53 | 2483.5 - 2495 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 or n41 or n53 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 65 or NR band n65 | 1920 - 2010 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to AAS BS operating in Band 65 or n65 | + +| Type of co-located BS | Frequency range for co-location requirement | Basic limit (WA BS) | Basic limit (MR BS) | Basic limit (LA BS) | Measurement Bandwidth | Notes | +|---------------------------------|---------------------------------------------|---------------------|---------------------|---------------------|-----------------------|-------------------------------------------------------------------------------| +| E-UTRA Band 66 or NR band n66 | 1710 - 1780 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 66 or n66 | +| E-UTRA Band 68 | 698 - 728 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 68 | +| E-UTRA Band 70 or NR band n70 | 1695 – 1710 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 71 or NR Band n71 | 663 – 698 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 72 or NR Band n72 | 451 – 456 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 73 | 450 - 455 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 74 or NR Band n74 | 1427 – 1470 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n50, n51, n91, n92, n93 or n94 | +| NR Band n77 | 3.3 – 4.2 GHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52 | +| NR Band n78 | 3.3 – 3.8 GHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52 | +| NR Band n79 | 4.4 – 5.0 GHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n80 | 1710 – 1785 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n81 | 880 – 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n82 | 832 – 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n83 | 703 – 748 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n84 | 1920 – 1980 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 85 or NR band n85 | 698 - 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n86 | 1710 – 1780 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 87 | 410 - 415 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 88 | 412 - 417 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n89 | 824 - 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n91 | 832 – 862 MHz | N/A | N/A | -88 dBm | 100 kHz | | +| NR Band n92 | 832 – 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n93 | 880 – 915 MHz | N/A | N/A | -88 dBm | 100 kHz | | +| NR Band n94 | 880 – 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR band n95 | 2010 - 2025 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n96 | 5925 - 7125 MHz | N/A | -90 dBm | -87 dBm | 100 kHz | | +| NR band n97 | 2300 - 2400 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR band n98 | 1880 - 1920 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR band n99 | 1626.5 – 1660.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 103 | 787 – 788 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n104 | 6425 – 7125 MHz | -95 dBm | -90 dBm | -87 dBm | 100 kHz | | +| NR Band n105 | 663 – 703 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 106 or NR Band n106 | 896 – 901 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| NR Band n109 | 703 – 733 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | + +NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in table 6.6.6.5.2.6-1 do not apply for the $\Delta f_{\text{OBUE}}$ frequency range immediately outside the *TAB connector* transmit frequency range of a downlink operating band (clause 4.5). 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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [21]. + +NOTE 2: Table 6.6.6.5.2.6-1 assumes that two operating bands, where the corresponding *TAB connector* transmit and receive frequency ranges in clause 4.5 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 3: Co-located TDD Base Stations that are synchronized and using the same or adjacent operating band can transmit without special co-locations requirements. For unsynchronized Base Stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +NOTE 4: For UTRA MR BS the measurement bandwidth is the same as for E-UTRA (100 kHz). + +**Table 6.6.6.5.2.6-2: Spurious emissions basic limits for UTRA TDD Wide Area BS co-located with another BS** + +| System type operating in the same geographical area | Band | Basic limit | Measurement bandwidth | Notes | +|-----------------------------------------------------|-----------------|-------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| Macro GSM900 | 876 - 915 MHz | -98 dBm | 100 kHz | | +| Macro DCS1800 | 1710 - 1785 MHz | -98 dBm | 100 kHz | This requirement does not apply to UTRA TDD operating in Band b and c. For UTRA TDD BS operating in Band f, it applies for 1710 - 1755 MHz | +| GSM850 or CDMA850 | 824 - 849 MHz | -98 dBm | 100 kHz | | +| WA BS UTRA FDD Band I or E-UTRA Band 1 | 1920 - 1980 MHz | -80 dBm (Note 1) | 3.84 MHz | | +| WA BS UTRA FDD Band III or E-UTRA Band 3 | 1710 - 1785 MHz | -80 dBm | 3.84 MHz | For UTRA TDD BS operating in Band f, it applies for 1710 - 1755 MHz. | +| WA BS UTRA FDD Band V or E-UTRA Band 5 | 824 - 849 MHz | -80 dBm (Note 1) | 3.84 MHz | | +| WA BS UTRA FDD Band VII or E-UTRA Band 7 | 2500 - 2570 MHz | - 80 dBm (Note 2) | 3.84 MHz | | + +NOTE 1: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the BS transmit frequency range of the operating band (see clause 4.5). 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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [21]. + +NOTE 2: The requirements in table 6.17 are based on a minimum coupling loss of 30 dB between base stations. The co-location of different base station classes is not considered. + +NOTE 3: 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 UTRA TDD in geographic areas where 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission in case of co-location shall not exceed the maximum level given in table 6.6.6.5.2.6-3. + +For *multi-band TAB connector*, the exclusions and conditions in the Notes of table 6.6.6.5.2.6-3 for each supported operating band. + +**Table 6.6.6.5.2.6-3: Spurious emissions basic limits for co-location with unsynchronised 1,28 Mcps UTRA TDD and/or E-UTRA TDD** + +| System type operating in the same geographic area | Frequency range | Basic limit | Measurement Bandwidth | +|---------------------------------------------------|-----------------|-------------|-----------------------| +| WA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -96 dBm | 100 kHz | +| WA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -96 dBm | 100 kHz | +| WA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -96 dBm | 100 kHz | +| WA UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400 MHz | -96 dBm | 100 kHz | +| WA UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920 MHz | -96 dBm | 100 kHz | +| WA E-UTRA Band 41 | 2496 - 2690 MHz | -96 dBm | 100 kHz | +| WA E-UTRA Band 42 | 3400 - 3600 MHz | -96 dBm | 100 kHz | +| WA E-UTRA Band 44 | 703 - 803 MHz | -96 dBm | 100 kHz | +| LA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -88 dBm | 100 kHz | +| LA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -88 dBm | 100 kHz | +| LA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -88 dBm | 100 kHz | +| LA UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400 MHz | -88 dBm | 100 kHz | +| LA UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920 MHz | -88 dBm | 100 kHz | +| LA E-UTRA Band 41 | 2496 - 2690 MHz | -88 dBm | 100 kHz | +| LA E-UTRA Band 42 | 3400 - 3600 MHz | -88 dBm | 100 kHz | +| LA E-UTRA Band 44 | 703 - 803 MHz | -88 dBm | 100 kHz | + +NOTE 1: The requirement applies for frequencies more than 10 MHz below or above the supported frequency range declared by the vendor. 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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [21]. + +NOTE 2: The requirements in this table are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations. The scenarios leading to these requirements are addressed in TR 25.942 [21]. + +NOTE 3: 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. + +## 6.7 Transmitter intermodulation + +### 6.7.1 Definition and applicability + +#### 6.7.1.1 General + +The transmitter intermodulation requirement is a measure of the capability of the transmitter unit to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter unit via the RDN and antenna array. The requirement applies during the *transmitter ON period* and the *transmitter transient period*. + +The requirement applies at each *TAB connector* supporting transmission in the operating band. + +The transmitter intermodulation level is the power of the intermodulation products when an interfering signal is injected into the *TAB connector*. + +For AAS BS there are two types of transmitter intermodulation cases captured by the transmitter intermodulation requirement: + +- 1) Co-location transmitter intermodulation in which the interfering signal is from a co-located base station. +- 2) Intra-system transmitter intermodulation in which the interfering signal is from other transmitter units within the AAS BS. + +For AAS BS, the co-location transmitter intermodulation requirement is considered sufficient if the interfering signal for the co-location requirement is higher than the declared interfering signal for intra-system transmitter intermodulation requirement. + +For *TAB connectors* capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply regardless of the interfering signals position relative to the *Inter RF Bandwidth gap*. + +## 6.7.2 Minimum requirement + +The minimum requirement for MSR operation are defined in TS 37.105 [8], clause 6.7.2. + +The minimum requirement for UTRA operation are defined in TS 37.105 [8], clause 6.7.3. + +The minimum requirement for UTRA operation are defined in TS 37.105 [8], clause 6.7.4. + +## 6.7.3 Test purpose + +The test purpose is to verify the ability of the transmitter units associated with the *TAB connector* under test to restrict the generation of intermodulation products in its nonlinear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna to below specified levels. + +## 6.7.4 Method of test + +### 6.7.4.1 Initial conditions + +Test environment: + +- normal; see clause B.2. + +RF channels to be tested for single carrier: + +- M; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $M_{\text{RFBW}}$ in single-band operation; see clause 4.12.1; $B'_{\text{RFBW}}\_T'_{\text{RFBW}}$ and $B'_{\text{RFBW}}\_T_{\text{RFBW}}$ in multi-band operation, see clause 4.12.1. + +### 6.7.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in clause D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in annex D.1.2. All *TAB connectors* not under test shall be terminated. +- 2) The measurement device characteristics shall be: + - Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 3) Set the set the *TAB connector* to transmit: + +## a) For MSR: + +- Set the *TAB connector* to transmit maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.11. + +## b) For UTRA FDD: + +- For a *TAB connector* declared to be capable of single carrier operation only, set the *TAB connector* to transmit a signal according to TM1, clause 4.12.2, at the manufacturer's declared rated output power, $P_{\text{rated,c,TABC}}$ . +- For a *TAB connector* declared to be capable of multi-carrier operation, set the *TAB connector* to transmit according to TM1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +## c) For UTRA TDD: + +- For a *TAB connector* declared to be capable of single carrier operation only, set the parameters of the transmitted signal according to table 6.7.4.2-1. +- For a *TAB connector* declared to be capable of multi-carrier operation, set to transmit according to table 6.7.4.2-1 on all carriers. + +**Table 6.7.4.2-1: Parameters of the transmitted signal for transmit intermodulation testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| 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) | + +## d) For E-UTRA: + +- *TAB connector* declared to be capable of single carrier operation only, set the *TAB connector* to transmit a signal according to E- TM1.1 in clause 4.12.2, at manufacturer's declared rated output power $P_{\text{rated,c,TABC}}$ . +- For a *TAB connector* declared to be capable of multi-carrier and/or CA operation, set the *TAB connector* to transmit according to E-TM1.1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +## 4) Generate the interfering signal: + +## a) For MSR: + +- using E-TM1.1 as defined in clause 4.12.2, with 5 MHz channel bandwidth, at a centre frequency offset according to the conditions in table 6.7.2.1-1 in TS 37.105 [8], but exclude interfering frequencies that are outside of the allocated downlink operating band or interfering frequencies that are not completely within the sub-block gap or within the *Inter RF Bandwidth gap*. + +## b) For UTRA FDD: + +- in accordance to TM1, clause 4.12.2 with a frequency offset of according to the conditions of table 6.7.3.1-1 in TS 37.105 [8], but exclude interfering signal frequencies that are outside of the allocated downlink operating band or interfering signal frequencies that are not completely within the sub-block gap or within the *Inter RF Bandwidth gap*. + +## c) For UTRA TDD: + +- The signal shall be like-modulated as the transmit signal and the active time slots of both signals shall be synchronized, with a frequency offset of according to the conditions of table 6.7.3.2-1 in TS 37.105 [8], + +but exclude interfering signal frequencies that are outside of the allocated downlink operating band or interfering signal frequencies that are not completely within the sub-block gap or within the *Inter RF Bandwidth gap*. + +d) For E-UTRA: + +- according to E-TM1.1, as defined in clause 4.12.2, with 5 MHz channel bandwidth and a centre frequency offset according to the conditions of table 6.7.4.1-1 in TS 37.105 [8], but exclude interfering frequencies that are outside of the allocated downlink operating band or interfering frequencies that are not completely within the sub-block gap or within the *Inter RF Bandwidth gap*. + +5) Adjust ATT1 so that level of the interfering signal is as defined in: + +a) For MSR: + +- i. General co-location table 6.7.2.1-1 in TS 37.105 [8]. +- ii. Additional co-location (BC1 and BC2) table 6.7.2.2-1 in TS 37.105 [8]. +- iii. Additional co-location (BC3) table 6.7.2.3-1 in TS 37.105 [8]. +- iv. Intra-system table 6.7.2.5-1 in TS 37.105 [8]. + +b) For UTRA FDD: + +- i. General co-location table 6.7.3.1-1 in TS 37.105 [8]. +- ii. Intra-system table 6.7.3.3-1 in TS 37.105 [8]. + +c) For UTRA TDD: + +- i. General co-location for 1,28 Mcps TDD UTRA table 6.7.3.2-1 in TS 37.105 [8]. +- ii. Intra-system table 6.7.3.3-1 in TS 37.105 [8]. + +d) For E-UTRA: + +- i. General co-location table 6.7.4.1-1 in TS 37.105 [8]. +- ii. Void +- iii. Intra-system table 6.7.4.131 in TS 37.105 [8]. + +6) If the test signal is applicable according to clause 5, perform the unwanted emission tests specified in clauses 6.6.3, 6.6.4 and 6.6.5, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clauses 6.6.3, 6.6.4 and 6.6.5. The width of the intermodulation products shall be taken into account. + +7) If the test signal is applicable according to clause 5, perform the Transmitter spurious emissions test as specified in clause 6.6.6, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clause 6.6.6. The width of the intermodulation products shall be taken into account. + +8) Verify that the emission level does not exceed the required level in clause 6.7.5 with the exception of interfering signal frequencies. + +9) Repeat the test for the remaining interfering signal centre frequency offsets according to the conditions of: + +a) For MSR: + +- i. General co-location table 6.7.2.1-1 in TS 37.105 [8]. +- ii. Additional co-location (BC1 and BC2) table 6.7.2.2-1 in TS 37.105 [8]. +- iii. Additional co-location (BC3) table 6.7.2.3-1 in TS 37.105 [8]. +- iv. Intra-system table 6.7.2.5-1 in TS 37.105 [8]. + +b) For UTRA FDD: + +- i. General co-location table 6.7.3.1-1 in TS 37.105 [8]. +- ii. Intra-system table 6.7.3.3-1 in TS 37.105 [8]. +- c) For UTRA TDD: + - i. General co-location for 1,28 Mcps TDD UTRA table 6.7.3.2-1 in TS 37.105 [8]. + - ii. Intra-system table 6.7.3.3-1 in TS 37.105 [8]. +- d) For E-UTRA: + - i. General co-location table 6.7.4.1-1 in TS 37.105 [8]. + - ii. Void + - iii. Intra-system table 6.7.4.131 in TS 37.105 [8]. + +10) Repeat the test for the remaining test signals defined in clause 5 for requirements 6.6.1, 6.6.2 and 6.6.4. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +11) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +NOTE: The third order intermodulation products are centred at $2F1 \pm F2$ and $2F2 \pm F1$ . The fifth order intermodulation products are centred at $3F1 \pm 2F2$ , $3F2 \pm 2F1$ , $4F1 \pm F2$ , and $4F2 \pm F1$ where F1 represents the test signal centre frequency or centre frequency of each sub-block and F2 represents the interfering signal centre frequency. The widths of intermodulation products are: + +- $(n * BW_{F1} + m * BW_{F2})$ for the $nF1 \pm mF2$ products; +- $(n * BW_{F2} + m * BW_{F1})$ for the $nF2 \pm mF1$ products; + +where $BW_{F1}$ represents the test signal RF bandwidth or channel bandwidth in case of single carrier, or sub-block bandwidth, and $BW_{F2}$ represents interfering signal bandwidth. + +## 6.7.5 Test requirements + +### 6.7.5.1 MSR test requirements + +#### 6.7.5.1.1 General test requirement + +In the frequency range relevant for this test the transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in clause 6.6.6, operating band unwanted emission in clause 6.6.5 and ACLR in clause 6.6.3 in the presence of a wanted signal and an interfering signal according to clause 6.7.4. for a *TAB connector* operating in BC1, BC2 and BC3. + +The requirement is applicable outside the edges of the *Base Station RF Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *radio bandwidth edges*. For *TAB connectors* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block edges*. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement applies relative to the *Base Station RF Bandwidth edges* of each operating band. In case the inter *Base Station RF Bandwidth* gap is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth* gap. + +#### 6.7.5.1.2 Additional test requirement (BC1 and BC2) + +In the frequency range relevant for this test the transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in clause 6.6.6, operating band unwanted emission in + +clause 6.6.5 and ACLR in clause 6.6.3 in the presence of a wanted signal and an interfering signal according clause 6.7.4. for a *TAB connector* operating in BC2. + +The requirement is applicable outside the edges of the *Base Station RF Bandwidth* for BC2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges*. + +For *TAB connectors* supporting operation in *non-contiguous spectrum* in BC1 or BC2, the requirement is also applicable inside a *sub-block gap* with a gap size larger than or equal to two times the interfering signal centre frequency offset. For *TAB connectors* supporting operation in *non-contiguous spectrum* in BC1, the requirement is not applicable inside a *sub-block gap* with a gap size equal to or larger than 5 MHz. The interfering signal offset is defined relative to the *sub-block edges*. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement applies relative to the *Base Station RF Bandwidth edges* of a BC2 operating band. The requirement is also applicable for BC1 and BC2 inside an inter *Base Station RF Bandwidth* gap equal to or larger than two times the interfering signal centre frequency offset. For *TAB connectors* supporting operation in multiple operating bands, the requirement is not applicable for BC1 band inside an inter *Base Station RF Bandwidth* gap with a gap size equal to or larger than 5 MHz. + +#### 6.7.5.1.3 Additional test requirement (BC3) + +This additional requirement shall only apply for BS co-located with an UTRA TDD BS. + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in clause 6.6.6, operating band unwanted emission in clause 6.6.5 and ACLR in clause 6.6.3 in the presence of a wanted signal and an interfering signal according clause 6.7.4. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement applies relative to the *Base Station RF Bandwidth edges* of each operating band. In case the *Inter RF Bandwidth gap* is less than 3.2 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth* gap. + +#### 6.7.5.1.4 Intra-system test requirement + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits specified for operating band unwanted emission in clause 6.6.5 and ACLR in clause 6.6.3 in the presence of a wanted signal and an interfering signal according clause 6.7.4 for a *TAB connector* operating in BC1, BC2 and BC3. + +### 6.7.5.2 Single RAT UTRA operation + +#### 6.7.5.2.1 General test requirement for UTRA FDD + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the out of band emission or the spurious emission requirements of clause 6.6.5 and clause 6.6.6 in the presence of interfering signal according to according clause 6.7.4. + +For *TAB connectors* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block edges*. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement is also applicable inside an *Inter RF Bandwidth gap* for interfering signal offsets where the interfering signal falls completely within the *Base Station RF Bandwidth* gap. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.7.5.2.2 General test requirement for UTRA TDD + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the out of band emission or the spurious emission requirements of clause 6.6.5 and clause 6.6.6 in the presence of interfering signal according to according clause 6.7.4. + +For *TAB connectors* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block* edges. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement is also applicable inside an *Inter RF Bandwidth gap* for interfering signal offsets where the interfering signal falls completely within the *Inter RF Bandwidth gap*. + +#### 6.7.5.2.3 Intra-system test requirement + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits specified for operating band unwanted emission in clause 6.6.5 and ACLR in clause 6.6.3 in the presence of a wanted signal and an interfering signal according to according clause 6.7.4. + +### 6.7.5.4 Single RAT E-UTRA operation + +#### 6.7.5.4.1 General test requirement + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 6.6.6, 6.6.5 and 6.6.3 in the presence of an E-UTRA interfering signal according to according clause 6.7.4. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *radio bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *radio bandwidth edges*. + +For *TAB connectors* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block* edges. + +For *TAB connectors* supporting operation in multiple operating bands, the requirement applies relative to the *Base Station RF Bandwidth edges* of each supported operating band. In case the *Inter RF Bandwidth gap* is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the *inter Base Station RF Bandwidth gap*. + +#### 6.7.5.4.2 Void + +#### 6.7.5.4.3 Intra-system test requirement + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits specified for operating band unwanted emission in clause 6.6.5 and ACLR in clause 6.6.3 in the presence of a wanted signal and an interfering signal according to according clause 6.7.4. + +## 7 Conducted receiver characteristics + +### 7.1 General + +Unless otherwise stated, the receiver characteristics are specified at the AAS BS *TAB connector* with full complement of transceivers for the configuration in normal operating condition. + +The manufacturer shall declare the minimum number of supported geographical cells (i.e. geographical areas) in clause 4.10. The minimum number of supported geographical cells ( $N_{\text{cells}}$ ) relates to the AAS BS setting with minimum amount of cell splitting. The manufacturer shall also declare *TAB connector RX min cell groups* for this minimum number of cells configuration. Every *TAB connector* supporting reception in an operating band shall map to one *TAB connector RX min cell group* supporting the same. The mapping of *TAB connectors* to cells is implementation dependent. + +The number of active receiver units that are considered when calculating the emission limit ( $N_{\text{RXU,counted}}$ ) for an AAS base station is calculated as follows: + +- $N_{\text{RXU,counted}} = \min(N_{\text{RXU,active}}, 8 \cdot N_{\text{cells}})$ for E-UTRA single RAT AAS BS and MSR AAS BS (excluding UTRA only MSR AAS BS). + +And + +- $N_{\text{RXU,counted}} = \min(N_{\text{RXU,active}}, 4 \cdot N_{\text{cells}})$ for UTRA single RAT AAS BS and UTRA only MSR AAS BS. + +Further: + +- $N_{\text{RXU,countedpercell}} = N_{\text{RXU,counted}}/N_{\text{cells}}$ + +$N_{\text{RXU,countedpercell}}$ is used for scaling the *basic limits* as described in clause 7.6. + +NOTE: $N_{\text{RXU,active}}$ is the number of actually active receiver units and is independent to the declaration of $N_{\text{cells}}$ . + +If a number of *TAB connectors* have been declared equivalent (see table 4.10-1, D6.70), only a representative one is necessary to demonstrate conformance. + +In clause 7.6.5.1, if representative *TAB connectors* are used then per connector criteria (option 2) shall be applied. + +Any receiver test requirement specified for Band 46 operation in TS 36.104 [4] for E-UTRA, or in TS 37.104 [5] for E-UTRA in *MSR operation*, and referred in clause 6, is not applicable for AAS BS. The requirements for co-location blocking for Band 46 are applicable for AAS BS. + +Any receiver requirement specified for NB-IoT in-band, NB-IoT guard band, or standalone NB-IoT operation in TS 36.104 [4] for E-UTRA with NB-IoT (in-band or guard band) or for standalone NB-IoT, or in TS 37.104 [5] for E-UTRA with NB-IoT or standalone NB-IoT in *MSR operation*, and referred in clause 7, is not applicable for AAS BS. + +## 7.2 Reference sensitivity level + +### 7.2.1 Definition and applicability + +The reference sensitivity power level $P_{\text{REFSENS}}$ is the minimum mean power received at the *TAB connector* at which a reference performance requirement shall be met for a specified reference measurement channel. + +### 7.2.2 Minimum Requirement + +The single RAT UTRA FDD AAS BS of Wide Area BS class shall fulfil minimum requirements for reference sensitivity specified in TS 25.104 [9], clause 7.2.1. + +The single RAT UTRA FDD AAS BS of Medium Range BS class shall fulfil minimum requirements for reference sensitivity specified in TS 25.104 [9], clause 7.2.1. + +The single RAT UTRA FDD AAS BS of Local Area BS class shall fulfil minimum requirements for reference sensitivity specified in TS 25.104 [9], clause 7.2.1. + +The single RAT UTRA TDD AAS BS of Wide Area BS class shall fulfil minimum requirements for reference sensitivity specified in TS 25.105 [10], clause 7.2.1.1. + +The single RAT UTRA TDD AAS BS of Local Area BS class shall fulfil minimum requirements for reference sensitivity specified in TS 25.105 [10], clause 7.2.1.1. + +The single RAT E-UTRA AAS BS of Wide Area BS class shall fulfil minimum requirements for reference sensitivity specified in TS 36.104 [11], clause 7.2.1. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for reference sensitivity specified in TS 36.104 [11], clause 7.2.1. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for reference sensitivity specified in TS 36.104 [11], clause 7.2.1. + +The MSR NR AAS BS of Wide Area BS class shall fulfil minimum requirements for reference sensitivity specified in TS 38.104 [36], clause 7.2.1. + +The MSR NR AAS BS of Medium Range BS class shall fulfil minimum requirements for reference sensitivity specified in TS 38.104 [36], clause 7.2.1. + +The MSR NR AAS BS of Local Area BS class shall fulfil minimum requirements for reference sensitivity specified in TS 38.104 [36], clause 7.2.1. + +## 7.2.3 Test Purpose + +To verify that at each *TAB connector* the reference sensitivity level the performance requirements shall be met for a specified reference measurement channel. + +## 7.2.4 Method of test + +### 7.2.4.1 Initial conditions + +Test environment: + +- normal; see clause B.2. +- extreme; see clauses B.3 and B.5. + +RF channels to be tested for single carrier: + +- B, M and T; see clause 4.12.1. + +Under extreme test environment, the test shall be performed on each of B, M and T under extreme power supply as defined in annex B.5. + +NOTE: Tests under extreme supply conditions also test extreme temperature. + +### 7.2.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect *TAB connector* to measurement equipment as shown in clause D.2.1. All *TAB connectors* not under test shall be terminated. +- 2) Set all *TAB connectors* declared in the same RAT and operating band to transmit a signal according to clause 4.12.2 at manufacturers declared rated output power $P_{\text{Rated,c,TABC}}$ . + +- 3) Start the signal generator for the wanted signal to transmit: + - 12,2kbps DPCH with reference measurement channel defined in annex A in TS 25.141 [18] (PN-9 data sequence or longer) for UTRA FDD, + - UL reference measurement channel (12.2 kbps) defined in clause A.2.1 in TS 25.142 [20] for UTRA TDD 1,28Mcps operation + - The test signal mean power as specified in clause 7.2.5.3 for E-UTRA to the *TAB connector*. + - The test signal mean power as specified in clause 7.2.5.4 for NR to the *TAB connector*. +- 4) For UTRA FDD disable the TPC function. +- 5) Set the signal generator for the wanted signal power as specified in clause 7.2.5. +- 6) Measure: + - BER according to annex C in TS 25.141 [18] for FDD UTRA. + - BER according to annex F in TS 25.142 [20] for TDD UTRA. + - Throughput according to annex E in TS 36.141 [17] for E-UTRA and NR. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 7) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 7.2.5 Test Requirements + +### 7.2.5.1 UTRA FDD operation + +The BER measurement result in step 6 of 7.2.4.2 shall not be greater than the limit specified in table 7.2.5.1-1. + +**Table 7.2.5.1-1: Reference sensitivity levels** + +| BS class | Reference measurement channel data rate | reference sensitivity level (dBm) | | BER | +|-----------------|-----------------------------------------|-----------------------------------|------------------------------|----------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | +| Wide Area BS | 12.2 kbps | -120.3 | -120.0 | BER shall not exceed 0.001 | +| Medium Range BS | 12.2 kbps | -110.3 | -110.0 | BER shall not exceed 0.001 | +| Local Area BS | 12.2 kbps | -106.3 | -106.0 | BER shall not exceed 0.001 | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.2.5.2 UTRA TDD 1,28 Mcps option operation + +The BER measurement result in step 4 of 7.2.4.2.2 shall not be greater than the limit specified in table 7.2.5.2-1. + +**Table 7.2.5.2-1: Test Requirement for BS reference sensitivity level for 1,28 Mcps option** + +| BS class | Reference measurement channel data rate | reference sensitivity level | BER | +|---------------|-----------------------------------------|-----------------------------|----------------------------| +| Wide Area BS | 12.2 kbps | -109.3 dBm | BER shall not exceed 0.001 | +| Local Area BS | 12.2 kbps | -95.3 dBm | BER shall not exceed 0.001 | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.2.5.3 E-UTRA operation + +For each measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel as specified in clause A.1 in TS 36.141 [17] with parameters specified in table 7.2.5.3-1 for Wide Area BS, in table 7.2.5.3-2 for Local Area BS and in table 7.2.5.3-3 for Medium Range BS. + +**Table 7.2.5.3-1: Wide Area BS class reference sensitivity levels** + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel (Note 2) | Reference sensitivity power level, $P_{\text{REFSENS}}$ (dBm) | | +|--------------------------------|----------------------------------------|---------------------------------------------------------------|------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | +| 1.4 | FRC A1-1 | -106.1 | -105.8 | +| 3 | FRC A1-2 | -102.3 | -102.0 | +| 5 | FRC A1-3 | -100.8 | -100.5 | +| 10 | FRC A1-3 (Note 1) | -100.8 | -100.5 | +| 15 | FRC A1-3 (Note 1) | -100.8 | -100.5 | +| 20 | FRC A1-3 (Note 1) | -100.8 | -100.5 | + +NOTE 1: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 in TS 36.141 [17] mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +NOTE 2: FRC reference measurement channels as defined in annex A.1 in TS 36.141 [17]. + +**Table 7.2.5.3-2: Local Area BS class, reference sensitivity levels** + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel (Note 2) | Reference sensitivity power level, $P_{\text{REFSENS}}$ (dBm) | | +|--------------------------------|----------------------------------------|---------------------------------------------------------------|------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | +| 1.4 | FRC A1-1 | -98.1 | -97.8 | +| 3 | FRC A1-2 | -94.3 | -94.0 | +| 5 | FRC A1-3 | -92.8 | -92.5 | +| 10 | FRC A1-3 (Note 1) | -92.8 | -92.5 | +| 15 | FRC A1-3 (Note 1) | -92.8 | -92.5 | +| 20 | FRC A1-3 (Note 1) | -92.8 | -92.5 | + +NOTE 1: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 in TS 36.141 [17] mapped to disjoint frequency ranges with a width of 25 resource blocks each. This reference measurement channel is not applied for Band 46 nor Band 49. + +NOTE 2: FRC reference measurement channels as defined in annex A.1 in TS 36.141 [17]. + +**Table 7.2.5.3-3: Medium Range BS class, reference sensitivity levels** + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel (Note 2) | Reference sensitivity power level, $P_{\text{REFSENS}}$ (dBm) | | +|--------------------------------|----------------------------------------|---------------------------------------------------------------|------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | +| 1.4 | FRC A1-1 | -101.1 | -100.8 | +| 3 | FRC A1-2 | -97.3 | -97.0 | +| 5 | FRC A1-3 | -95.8 | -95.5 | +| 10 | FRC A1-3 (Note 1) | -95.8 | -95.5 | +| 15 | FRC A1-3 (Note 1) | -95.8 | -95.5 | +| 20 | FRC A1-3 (Note 1) | -95.8 | -95.5 | + +NOTE 1: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 in TS 36.141 [17] mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +NOTE 2: FRC reference measurement channels as defined in annex A.1 in TS 36.141 [17]. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.2.5.4 NR operation + +For NR, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in Annex A in TS 38.104 [36] with parameters specified in table 7.2.5.4-1 for Wide Area BS, in table 7.2.5.4-2 for Medium Range BS and in table 7.2.5.4-3 for Local Area BS. + +**Table 7.2.5.4-1: NR Wide Area BS reference sensitivity levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, $P_{\text{REFSENS}}$ (dBm) | | | +|-------------------------------------------------|---------------------------|-------------------------------|---------------------------------------------------------------|------------------------------|------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | -101 | -100.7 | -100.2 | +| 10, 15 | 30 | G-FR1-A1-2 | -101.1 | -100.8 | -100.3 | +| 10, 15 | 60 | G-FR1-A1-3 | -98.2 | -97.9 | -97.4 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -94.6 | -94.3 | -93.8 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -94.9 | -94.6 | -94.1 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -95 | -94.7 | -94.2 | + +NOTE: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.2.5.4-2: NR Medium Area BS reference sensitivity levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, $P_{\text{REFSENS}}$ (dBm) | | | +|-------------------------------------------------|---------------------------|-------------------------------|---------------------------------------------------------------|------------------------------|------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | -96 | -95.7 | -95.2 | +| 10, 15 | 30 | G-FR1-A1-2 | -96.1 | -95.8 | -95.3 | +| 10, 15 | 60 | G-FR1-A1-3 | -93.2 | -92.9 | -92.4 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -89.6 | -89.3 | -88.8 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -89.9 | -89.6 | -89.1 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -90 | -89.7 | -89.2 | + +NOTE: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.2.5.4-3: NR Local Area BS reference sensitivity levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, P_{\text{REFSENS}} (dBm) | | | +|-------------------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------| +| | | | f \leq 3.0 GHz | 3.0 GHz < f \leq 4.2 GHz | 4.2 GHz < f \leq 6.0 GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | -93 | -92.7 | -92.2 | +| 10, 15 | 30 | G-FR1-A1-2 | -93.1 | -92.8 | -92.3 | +| 10, 15 | 60 | G-FR1-A1-3 | -90.2 | -89.9 | -89.4 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -86.6 | -86.3 | -85.8 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -86.9 | -86.6 | -86.1 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -87 | -86.7 | -86.2 | + +NOTE: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The relationship between Minimum Requirements and Test Requirements is defined in clause 4.1 and the explanation of how the Minimum Requirement has been adjusted by the Test Tolerance is given in Annex C. + +## 7.3 Dynamic range + +### 7.3.1 Definition and applicability + +The dynamic range is a measure of the capability of the receiver unit to receive a wanted signal in the presence of an interfering signal at the *TAB connector* inside the received *channel bandwidth* or the capability of receiving high level of wanted signal. + +### 7.3.2 Minimum requirement + +The single RAT UTRA FDD AAS BS of Wide Area BS class shall fulfil minimum requirements for dynamic range specified in TS 25.104 [9], clause 7.3.1. + +The single RAT UTRA FDD AAS BS of Medium Range BS class shall fulfil minimum requirements for dynamic range specified in TS 25.104 [9], clause 7.3.1. + +The single RAT UTRA FDD AAS BS of Local Area BS class shall fulfil minimum requirements for dynamic range specified in TS 25.104 [9], clause 7.3.1. + +The single RAT UTRA TDD AAS BS of Wide Area BS class shall fulfil minimum requirements for dynamic range specified in TS 25.105 [10], clause 7.3.1.1. + +The single RAT UTRA TDD AAS BS of Local Area BS class shall fulfil minimum requirements for dynamic range specified in TS 25.105 [10], clause 7.3.1.1. + +The single RAT E-UTRA AAS BS of A Wide Area BS class shall fulfil minimum requirements for dynamic range specified in TS 36.104 [11], clause 7.3.1. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for dynamic range specified in TS 36.104 [11], clause 7.3.1. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for dynamic range specified in TS 36.104 [11], clause 7.3.1. + +The MSR NR AAS BS of A Wide Area BS class shall fulfil minimum requirements for dynamic range specified in TS 38.104 [36], clause 7.3.1. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for dynamic range specified in TS 38.104 [36], clause 7.3.1. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for dynamic range specified in TS 38.104 [36], clause 7.3.1. + +### 7.3.3 Test purpose + +To verify that at the dynamic range of the receiver unit associated with each *TAB connector* shall fulfil the specified limit. + +### 7.3.4 Method of test + +#### 7.3.4.1 Initial conditions + +Test environment: + +- normal; see clause B.2. + +RF channels to be tested for single carrier: + +- M; see clause 4.12.1. + +#### 7.3.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect *TAB connector* to measurement equipment as shown in annex D.2.1. All *TAB connectors* not under test shall be terminated. +- 2) Set the signal generator for the wanted signal to transmit: + - as specified in table 7.3.5.1-1 for UTRA. + - as specified in table 7.3.5.2-1 for UTRA TDD 1,28Mcps operation. + - as specified in table 7.3.5.3-1 to table 7.3.5.3-3 for E-UTRA. + - as specified in table 7.3.5.4-1 to table 7.3.5.4-3 for NR. +- 3) Set the Signal generator for the AWGN interfering signal at the same frequency as the wanted signal to transmit: + - as specified in table 7.3.5.1-1 for UTRA. + - as specified in table 7.3.5.2-1 for UTRA TDD 1,28Mcps operation. + - as specified in table 7.3.5.3-1 to table 7.3.5.3-3 for E-UTRA. + - as specified in table 7.3.5.1-1 to table 7.3.5.1-3 for NR. +- 4) Measure: + - BER according to annex C in TS 25.141 [18] for FDD UTRA. + - BER according to annex F in TS 25.142 [20] for TDD UTRA. + - Throughput according to annex E in TS 36.141 [17] for E-UTRA. + - Throughput according TS 38.141-1 [37] for NR. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 7.3.5 Test requirements + +#### 7.3.5.1 UTRA FDD operation + +The BER shall not exceed 0,001 for the parameters specified in table 7.3.5.1-1. + +**Table 7.3.5.1-1: Dynamic range** + +| Parameter | Level
Wide Area BS | Level
Medium Range BS | Level
Local Area BS | Unit | +|-----------------------------------------|-----------------------|--------------------------|------------------------|--------------| +| Reference measurement channel data rate | 12,2 | 12.2 | 12.2 | Kbps | +| Wanted signal mean power | -89.8 | -79.8 | -75.8 | dBm | +| Interfering AWGN signal | -73 | -63 | -59 | dBm/3.84 MHz | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 7.3.5.2 UTRA TDD 1,28 Mcps option operation + +The BER shall not exceed 0,001 for the parameters specified in table 7.3.5.2-1. + +**Table 7.3.5.2-1: Test Requirements for Dynamic Range for 1,28 Mcps TDD option** + +| Parameter | Level | Unit | +|-----------------------------------------|---------------|--------| +| Reference measurement channel data rate | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -78,8 | +| | Local Area BS | -64,8 | +| Interfering AWGN signal | Wide Area BS | -76 | +| | Local Area BS | -62 | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 7.3.5.3 E-UTRA operation + +For each measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel as specified in annex A in TS 36.141 [17] with parameters specified in table 7.3.5.3-1 for an AAS BS of Wide Area BS class, in Table 7.3.5.3-2 for an AAS BS of Local Area BS class and in table 7.3.5.3-3 for AAS BS of Medium Range BS class. + +**Table 7.3.5.3-1: AAS BS of Wide Area BS class dynamic range** + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BW Config | Type of interfering signal | +|--------------------------------|-------------------------------|--------------------------------|------------------------------------------------------------|----------------------------| +| 1.4 | FRC A2-1 in annex A.2 | -76.0 | -88.7 | AWGN | +| 3 | FRC A2-2 in annex A.2 | -72.1 | -84.7 | AWGN | +| 5 | FRC A2-3 in annex A.2 | -69.9 | -82.5 | AWGN | +| 10 | FRC A2-3 in annex A.2 (Note) | -69.9 | -79.5 | AWGN | +| 15 | FRC A2-3 in annex A.2 (Note) | -69.9 | -77.7 | AWGN | +| 20 | FRC A2-3 in annex A.2 (Note) | -69.9 | -76.4 | AWGN | + +NOTE: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A2-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +**Table 7.3.5.3-2: AAS BS of Local Area BS class dynamic range** + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BW Config | Type of interfering signal | +|--------------------------------|-------------------------------|--------------------------------|------------------------------------------------------------|----------------------------| +| 1.4 | FRC A2-1 in annex A.2 | -68.0 | -80.7 | AWGN | +| 3 | FRC A2-2 in annex A.2 | -64.1 | -76.7 | AWGN | +| 5 | FRC A2-3 in annex A.2 | -61.9 | -74.5 | AWGN | +| 10 | FRC A2-3 in annex A.2 (Note) | -61.9 | -71.5 | AWGN | +| 15 | FRC A2-3 in annex A.2 (Note) | -61.9 | -69.7 | AWGN | +| 20 | FRC A2-3 in annex A.2 (Note) | -61.9 | -68.4 | AWGN | + +NOTE: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A2-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. This reference measurement channel is not applied for Band 46 nor Band 49. + +**Table 7.3.5.3-3: AAS BS of Medium Range BS class dynamic range** + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BW Config | Type of interfering signal | +|--------------------------------|-------------------------------|--------------------------------|------------------------------------------------------------|----------------------------| +| 1.4 | FRC A2-1 in annex A.2 | -71.0 | -83.7 | AWGN | +| 3 | FRC A2-2 in annex A.2 | -67.1 | -79.7 | AWGN | +| 5 | FRC A2-3 in annex A.2 | -64.9 | -77.5 | AWGN | +| 10 | FRC A2-3 in annex A.2 (Note) | -64.9 | -74.5 | AWGN | +| 15 | FRC A2-3 in annex A.2 (Note) | -64.9 | -72.7 | AWGN | +| 20 | FRC A2-3 in annex A.2 (Note) | -64.9 | -71.4 | AWGN | + +NOTE: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A2-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 7.3.5.4 NR operation + +For NR, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in Annex A in TS 38.104 [36] with parameters specified in table 7.3.5.4-1 for Wide Area BS, in table 7.3.5.4-2 for Medium Range BS and in table 7.3.5.4-3 for Local Area BS. + +**Table 7.3.5.4-1: Wide Area BS dynamic range** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | 15 | G-FR1-A2-1 | -70.4 | -82.5 | AWGN | +| | 30 | G-FR1-A2-2 | -71.1 | | | +| 10 | 15 | G-FR1-A2-1 | -70.4 | -79.3 | AWGN | +| | 30 | G-FR1-A2-2 | -71.1 | | | +| | 60 | G-FR1-A2-3 | -68.1 | | | +| 15 | 15 | G-FR1-A2-1 | -70.4 | -77.5 | AWGN | +| | 30 | G-FR1-A2-2 | -71.1 | | | +| | 60 | G-FR1-A2-3 | -68.1 | | | +| 20 | 15 | G-FR1-A2-4 | -64.2 | -76.2 | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 | | | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 25 | 15 | G-FR1-A2-4 | -64.2 | -75.2 | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 | | | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 30 | 15 | G-FR1-A2-4 | -64.2 | -74.4 | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 | | | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 35 | 15 | G-FR1-A2-4 | -64.2 | -73.7 | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 | | | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 40 | 15 | G-FR1-A2-4 | -64.2 | -73.1 | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 | | | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 45 | 15 | G-FR1-A2-4 | -64.2 | -72.6 | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 | | | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 50 | 15 | G-FR1-A2-4 | -64.2 | -72.1 | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 | | | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 60 | 30 | G-FR1-A2-5 | -64.2 | -71.3 | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 70 | 30 | G-FR1-A2-5 | -64.2 | -70.7 | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 80 | 30 | G-FR1-A2-5 | -64.2 | -70.1 | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 90 | 30 | G-FR1-A2-5 | -64.2 | -69.5 | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 | | | +| 100 | 30 | G-FR1-A2-5 | -64.2 | -69.1 | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.3.5.4-2: Medium Range BS dynamic range** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | 15 | G-FR1-A2-1 | -65.4 | -77.5 | AWGN | +| | 30 | G-FR1-A2-2 | -66.1 | | | +| 10 | 15 | G-FR1-A2-1 | -65.4 | -74.3 | AWGN | +| | 30 | G-FR1-A2-2 | -66.1 | | | +| | 60 | G-FR1-A2-3 | -63.1 | | | +| 15 | 15 | G-FR1-A2-1 | -65.4 | -72.5 | AWGN | +| | 30 | G-FR1-A2-2 | -66.1 | | | +| | 60 | G-FR1-A2-3 | -63.1 | | | +| 20 | 15 | G-FR1-A2-4 | -59.2 | -71.2 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 25 | 15 | G-FR1-A2-4 | -59.2 | -70.2 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 30 | 15 | G-FR1-A2-4 | -59.2 | -69.4 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 35 | 15 | G-FR1-A2-4 | -59.2 | -68.7 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 40 | 15 | G-FR1-A2-4 | -59.2 | -68.1 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 45 | 15 | G-FR1-A2-4 | -59.2 | -67.6 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 50 | 15 | G-FR1-A2-4 | -59.2 | -67.1 | AWGN | +| | 30 | G-FR1-A2-5 | 59.8 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 60 | 30 | G-FR1-A2-5 | -59.2 | -66.3 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 70 | 30 | G-FR1-A2-5 | -59.2 | -65.7 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 80 | 30 | G-FR1-A2-5 | -59.2 | -65.1 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 90 | 30 | G-FR1-A2-5 | -59.2 | -64.5 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 100 | 30 | G-FR1-A2-5 | -59.2 | -64.1 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.3.5.4-3: Local Area BS dynamic range** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | 15 | G-FR1-A2-1 | -62.4 | -74.5 | AWGN | +| | 30 | G-FR1-A2-2 | -63.1 | | | +| 10 | 15 | G-FR1-A2-1 | -62.4 | -71.3 | AWGN | +| | 30 | G-FR1-A2-2 | -63.1 | | | +| | 60 | G-FR1-A2-3 | -60.1 | | | +| 15 | 15 | G-FR1-A2-1 | -62.4 | -69.5 | AWGN | +| | 30 | G-FR1-A2-2 | -63.1 | | | +| | 60 | G-FR1-A2-3 | -60.1 | | | +| 20 | 15 | G-FR1-A2-4 | -56.2 | -68.2 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 25 | 15 | G-FR1-A2-4 | -56.2 | -67.2 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 30 | 15 | G-FR1-A2-4 | -56.2 | -66.4 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 35 | 15 | G-FR1-A2-4 | -56.2 | -65.7 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 40 | 15 | G-FR1-A2-4 | -56.2 | -65.1 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 45 | 15 | G-FR1-A2-4 | -56.2 | -64.6 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 50 | 15 | G-FR1-A2-4 | -56.2 | -64.1 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 60 | 30 | G-FR1-A2-5 | -56.2 | -63.3 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 70 | 30 | G-FR1-A2-5 | -56.2 | -62.7 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 80 | 30 | G-FR1-A2-5 | -56.2 | -62.1 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 90 | 30 | G-FR1-A2-5 | -56.2 | -61.5 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 100 | 30 | G-FR1-A2-5 | -56.2 | -61.1 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The relationship between Minimum Requirements and Test Requirements is defined in clause 4.1 and the explanation of how the Minimum Requirement has been adjusted by the Test Tolerance is given in Annex C. + +## 7.4 Adjacent channel selectivity and narrowband blocking + +### 7.4.1 Definition and applicability + +The adjacent channel selectivity, general blocking and narrowband blocking characteristics are measures of the receiver unit ability to receive a wanted signal at its assigned channel at the *TAB connector* in the presence of an unwanted interferer inside the operating band. + +NOTE For Single RAT requirements, the in-band selectivity characteristics is referred to as "adjacent channel selectivity", whereas for the MSR requirements, the corresponding property is referred to as "general blocking" since the adjacent frequency range may not carry a channel addressable from the interfered carrier. + +The in-band blocking requirement applies from $F_{UL\_low} - \Delta f_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ , excluding the downlink frequency range of the *operating band*. The values of $\Delta f_{OOB}$ are defined in table 7.4.1-1. + +**Table 7.4.1-1: $\Delta f_{OOB}$ offset for operating bands** + +| Operating band characteristics | \Delta f_{OOB} [MHz] | +|----------------------------------------------------------|------------------------------------------| +| $F_{UL\_high} - F_{UL\_low} < 100$ MHz | 20 | +| $100$ MHz $\leq F_{UL\_high} - F_{UL\_low} \leq 900$ MHz | 60 | + +### 7.4.2 Minimum requirement + +The minimum requirement for MSR operation is in TS 37.105 [8], clause 7.4.2. + +The single RAT UTRA FDD AAS BS of Wide Area BS class shall fulfil minimum requirements for adjacent channel selectivity and narrow-band blocking specified in TS 25.104 [9], clause 7.4. + +The single RAT UTRA FDD AAS BS of Medium Range BS class shall fulfil minimum requirements for adjacent channel selectivity and narrow-band blocking specified in TS 25.104 [9], clause 7.4. + +The single RAT UTRA FDD Local Area BS class shall fulfil minimum requirements for adjacent channel selectivity and narrow-band blocking specified in TS 25.104 [9], clause 7.4. + +The single RAT UTRA TDD AAS BS of Wide Area BS class shall fulfil minimum requirements for adjacent channel selectivity and narrow-band blocking specified in TS 25.105 [10], clause 7.4. + +The single RAT UTRA TDD AAS BS of Local Area BS class shall fulfil minimum requirements for adjacent channel selectivity and narrow-band blocking specified in TS 25.105 [10], clause 7.4. + +The single RAT E-UTRA AAS BS of Wide Area BS class shall fulfil minimum requirements for adjacent channel selectivity and narrow-band blocking specified in TS 36.104 [11], clause 7.5. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for adjacent channel selectivity and narrow-band blocking specified in TS 36.104 [11], clause 7.5. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for adjacent channel selectivity and narrow-band blocking specified in TS 36.104 [11], clause 7.5. + +### 7.4.3 Test purpose + +The test stresses the receiver unit ability to withstand high-level interference from unwanted signals at specified frequency offsets at the *TAB connector* without undue degradation of its sensitivity. + +### 7.4.4 Method of test + +#### 7.4.4.1 Initial conditions + +Test environment: + +- Normal; see clause B.2. + +RF channels to be tested for single carrier (SC): + +- M; see clause 4.12.1 + +*Base Station RF Bandwidth* positions to be tested for multi-carrier (MC): + +- $M_{\text{RFBW}}$ for *single-band TAB connector(s)*, see clause 4.12.1, $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ for *multi-band TAB connector(s)*, see clause 4.12.1. + +## 7.4.4.2 Procedure + +### 7.4.4.2.1 General procedure + +The general procedure steps apply to the procedures for all the RATs. + +The minimum requirement is applied to all *TAB connectors*, the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect *TAB connector* to measurement equipment as shown in annex D.2.3. All *TAB connectors* not under test shall be terminated. +- 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the *TAB connector* under test as follows: + - For E-UTRA see clause A.1 in TS 36.141 [17]. + - For UTRA FDD see clause A.2 in TS 25.141 [18]. + - For UTRA TDD see clause A.2.1 in TS 25.142 [20]. + - For NR, see clause [4.11]. +- 3) Set the transmitter unit associated with the *TAB connector* under test to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +### 7.4.4.2.2 MSR operation + +#### 7.4.4.2.2.1 Procedure for general blocking + +- 1) Adjust the signal generators to the type of interfering signal, levels and the frequency offsets as specified in table 7.4.5.1.1-1. +- 2) The interfering signal shall be swept with a step size of 1 MHz starting from the minimum offset to the channel edges of the wanted signals as specified in table 7.4.5.1.1-1. +- 3) Measure the performance of the wanted signal at the receiver unit associated with the *TAB connector* under test, as defined in clause 7.4.5.1, for the relevant carriers specified by the test configuration in clause 4.11. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.4.4.2.2.2 Procedure for narrowband blocking + +- 1) Adjust the signal generators to the type of interfering signal, levels and the frequency offsets as specified in table 7.4.5.1.2-1. +- 2) Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.4.5.1.2-1. + +- 3) Measure the performance of the wanted signal at the receiver unit associated with the *TAB connector* under test, as defined in clause 7.4.5.1, for the relevant carriers specified by the test configuration in clause 4.11. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.4.4.2.2.3 Procedure for additional BC3 blocking requirement + +- 1) Adjust the signal generators to the type of interfering signal, levels and the frequency offsets as specified in table 7.4.5.5-1. +- 2) Measure the performance of the wanted signal at the receiver unit associated with the *TAB connector* under test, as defined in clause 7.4.5, for the relevant carriers specified by the test configuration in clause 4.8. + +#### 7.4.4.2.3 Single RAT UTRA FDD operation + +- 1) Generate the wanted signal and adjust the ATT1 to set the input level to the base station under test to the level specified in table 7.4.5.2-1 For a *TAB connector* supporting multi-carrier operation, generate the wanted signal according to the applicable test configuration (see clause 4.11) using applicable reference measurement channel to the *TAB connector* under test. Power settings are specified in table 7.4.5.2-1. +- 2) Set-up the interfering signal at the adjacent channel frequency and adjust the ATT2 to obtain the specified level of interfering signal at the base station input defined in table 7.4.5.2-1. Note that the interfering signal shall have an ACLR of at least 63 dB in order to eliminate the impact of interfering signal adjacent channel leakage power on the ACS measurement. +- 3) Measure the BER of the wanted signal at the receiver unit associated with the *TAB connector* under test. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.4.4.2.4 Single RAT UTRA TDD 1,28Mcps option operation + +- 1) Generate the wanted signal according to the test configurations in clause 4.11 and adjust the input level to the *TAB connector* under test according to table 7.4.5.3-1. The UL reference measurement channel (12,2 kbps) defined in clause A.2.1 in TS 25.142 [20] shall be used for each wanted carrier. +- 2) Set-up the interfering signal at the adjacent channel frequency and adjust the interfering signal level at the *TAB connector* according to table 7.4.5.3-1. The interfering signal is equivalent to a continuous 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$ . +- 3) Measure the BER of the wanted signal at the receiver unit associated with the *TAB connector* under test. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.4.4.2.5 Single RAT E-UTRA operation + +##### 7.4.4.2.5.1 Procedure for adjacent channel selectivity + +- 1) Generate the wanted signal using the applicable test configuration specified in clause 5.3.4 and adjust the input level to the *TAB connector* under test to the level specified in table 7.4.5.4-1 for the appropriate BS class. +- 2) Set-up the interfering signal at the adjacent channel frequency and adjust the interfering signal level at the *TAB connector* under test to the level defined in table 7.4.5.4-1 for the appropriate BS class. + +- 3) Measure the throughput, for multi-carrier and/or CA operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clause 5.3.4. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.4.4.2.5.2 Procedure for narrow-band blocking + +- 1) For *TAB connector* operating E-UTRA FDD declared to be capable of single carrier operation only in the operating band, set the transmitter unit associated with the *TAB connector* under test to transmit according to clause 4.12.2 at manufacturers declared rated output power $P_{\text{Rated,c,TABC}}$ . + +For a *TAB connector* operating E-UTRA FDD declared to be capable of multi-carrier and/or CA operation in the operating band, set the transmitter unit associated with the *TAB connector* under test to transmit according to clause 4.12.2 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 5.3.4. + +- 2) Generate the wanted signal using the applicable test configuration specified in clause 5.3.4 and adjust the input level to the *TAB connector* under test to the level specified in table 7.4.5.4-1. +- 3) Adjust the interfering signal level at the *TAB connector* input to the level defined in table 7.4.5.4-1. Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.4.5.4-2. +- 4) Measure the throughput, for multi-carrier and/or CA operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clause 5.3.4. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 7.4.5 Test requirements + +#### 7.4.5.1 MSR operation + +##### 7.4.5.1.1 General blocking test requirement + +For the general blocking requirement, the interfering signal shall be a UTRA FDD signal as specified in clause A.1 in TS 25.141 [18] for a UTRA, E-UTRA or NR ( $\leq 20$ MHz) wanted signal. The interfering signal shall be a 20 MHz E-UTRA signal for NR wanted signal channel bandwidth greater than 20 MHz. + +For *TAB connector* operating in non-contiguous spectrum, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 15 MHz. The interfering signal offset is defined relative to the sub-block edges inside the *sub-block gap*. + +For *multi-band TAB connector* the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least 15 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal coupled to the *TAB connector*, using the parameters in tables 7.4.5.1.1-1 and 7.4.5.1.1-2, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.3. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.1. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.2. + +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [17], clause 7.2. + +For a *multi-band TAB connector*, the requirement applies according to table 7.4.5.1-1 for the in-band blocking frequency ranges of each supported operating band. + +**Table 7.4.5.1.1-1: General blocking requirement** + +| Base Station class | Mean power of interfering signal (dBm) | Wanted Signal mean power (dBm) (Note 1) | Centre Frequency of Interfering Signal | Interfering signal centre frequency minimum frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap (MHz) | +|--------------------|----------------------------------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | -40 +y (Note 7) | $P_{\text{REFSENS}} + x$ dB (Note 2, 5) | $F_{\text{UL\_low}} - \Delta f_{\text{OOB}}$ to $F_{\text{UL\_high}} + \Delta f_{\text{OOB}}$ (Note 8) | $\pm(7.5+z)$ (Note 9) | +| Medium Range BS | -35 +y (Note 7) | $P_{\text{REFSENS}} + x$ dB (Note 3, 5) | | | +| Local Area BS | -30 +y (Note 7) | $P_{\text{REFSENS}} + x$ dB (Note 4, 5) | | | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth, see clause 7.2. +NOTE 2: For WA BS supporting UTRA, "x" is equal to 6 in case of NR or E-UTRA or UTRA wanted signals. +NOTE 3: For MR BS supporting UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA wanted signal. +NOTE 4: For LA BS supporting UTRA, "x" is equal to 11 in case of NR or E-UTRA wanted signal, 6 in case of UTRA wanted signal. +NOTE 5: For a BS not supporting UTRA, x is equal to 6 for all BS classes if NR is supported, otherwise "x" is equal to 6 for WA BS or 9 for MR BS or 11 for LA BS if NR is not supported. +NOTE 6: For a BS capable of multi-band operation, "x" in Note 2, 3, 4, 5 applies in case of interfering signals that are in the in-band blocking frequency range of the operating band where the wanted signal is present or in the in-band blocking frequency range of an adjacent or overlapping operating band. For other in-band blocking frequency ranges of the interfering signal for the supported operating bands, "x" is equal to 1.4 dB. +NOTE 7: For a BS supporting NR and not supporting UTRA, "y" is equal to -3 for the WA and MR BS class and -5 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. +NOTE 8: The downlink frequency range of an FDD operating band is excluded from the general blocking requirement. +NOTE 9: For NR wanted signal channel bandwidth greater than 20 MHz, z = 22.5 MHz. For all other cases, z = 0 MHz. + +**Table 7.4.5.1.1-2: Void** + +NOTE: The requirement in tables 7.4.5.1.1-1 assumes that two operating bands, where the *downlink operating band* (see table 4.4-1 and table 4.4-2 in TS 37.141 [16].) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +#### 7.4.5.1.2 General narrowband blocking test requirement + +For the narrowband blocking requirement, the interfering signal shall be an E-UTRA 1RB signal as specified in clause A.3 in TS 37.141 [16]. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For a *TAB connector* operating in non-contiguous spectrum, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 3 MHz. The interfering signal offset is defined relative to the sub-block edges inside the *sub-block gap*. + +For a *multi-band TAB connector*, the requirement applies in addition inside any *Inter RF Bandwidth gap* in case the gap size is at least 3 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal coupled to the *TAB connector*, using the parameters in table 7.4.5.1.2-1 the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.3. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.1. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [17], clause 7.2.5.3. + +**Table 7.4.5.1.2-1: Narrowband blocking requirement** + +| Base Station Class | RAT of the carrier | Wanted signal mean power (dBm) (Note 1, 2, 6) | Interfering signal mean power (dBm) | Interfering RB (Note 3) centre frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap (kHz) | +|--------------------|---------------------|-----------------------------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | NR, E-UTRA and UTRA | $P_{\text{REFSENS}} + x \text{ dB}$ | -49 | $\pm(240 + m \cdot 180)$ ,
$m=0, 1, 2, 3, 4, 9, 14$
(Note 4) | +| Medium Range BS | | | -44 | | +| Local Area BS | | | -41 | $\pm(550 + m \cdot 180)$ ,
$m=0, 1, 2, 3, 4, 29, 54, 79, 99$ (Note 5) | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth, see clause 7.2 in TS 37.104 [12]. +NOTE 2: "x" is equal to 6 in case of E-UTRA, NR or UTRA wanted signals. +NOTE 3: Interfering signal (E-UTRA 3 MHz) consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the *Base Station RF Bandwidth edge*. +NOTE 4: Applicable for *channel bandwidths* equal to or below 20 MHz. +NOTE 5: Applicable for *channel bandwidths* above 20 MHz. +NOTE 6: 7.5 kHz shift is not applied to the wanted signal of NR. +NOTE 7: Void + +#### 7.4.5.1.3 Additional BC3 blocking test requirement + +This additional requirement only applies for BS operating in the same geographical area as UTRA TDD. + +The interfering signal is a 1,28Mcps UTRA TDD modulated signal as specified in clause A.2 in TS 37.141 [16]. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For a *multi-band TAB connector*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least 4.8 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal coupled to the *TAB connector*, using the parameters in table 7.4.5.1.3-1, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.3. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.2. + +**Table 7.4.5.1.3-1: Additional blocking requirement for Band Category 3** + +| Operating Band | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power (dBm) | Wanted Signal mean power (dBm) | Interfering signal centre frequency minimum frequency offset from the Base Station RF Bandwidth edge (MHz) | +|---------------------------------------------------------------------------------------------|-----------------------------------------------------------|-------------------------------------|------------------------------------|------------------------------------------------------------------------------------------------------------| +| 33 - 40 | (F UL_low - 20) to (F UL_high + 20) | -40, | P REFSENS + 6 dB (Note) | ±2.4 | +| NOTE: P REFSENS depends on the RAT and on the channel bandwidth, see clause 7.2. | | | | | + +### 7.4.5.2 Single RAT UTRA FDD operation + +For each measured carrier, the BER shall not exceed 0,001 for the parameters specified in table 7.4.5.2-1. + +For *multi-carrier TAB connector* the ACS requirement is applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the lower/upper *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For a *TAB connector* operating in non-contiguous spectrum within any operating band, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 5 MHz. The interfering signal offset is defined relative to the lower/upper sub-block edge inside the *sub-block gap* and is equal to -2.5 MHz/+2.5 MHz, respectively. + +For a *multi-band TAB connector*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least 5 MHz. The interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -2.5 MHz/+2.5 MHz, respectively. + +**Table 7.4.5.2-1: Adjacent channel selectivity** + +| Parameter | Level Wide Area BS | Level Medium Range BS | Level Local Area BS | Unit | +|-----------------------------------------|--------------------|-----------------------|---------------------|------| +| Reference measurement channel data rate | 12.2 | 12.2 | 12.2 | kbps | +| Wanted signal mean power | -115 | -105 | -101 | dBm | +| Interfering signal mean power | -52 | -42 | -38 | dBm | +| F uw (Modulated) | ±5 | ±5 | ±5 | MHz | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.4.5.3 Single RAT UTRA TDD 1,28 Mcps option operation + +The BER, measured on the wanted signal in the presence of an interfering signal, shall not exceed 0,001 for the parameters specified in table 7.4.5.3-1. + +The ACS 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 *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For *multi-band TAB connector*, the requirement applies in addition inside any *Inter RF Bandwidth gap* as long as the *Inter RF Bandwidth gap* size is at least 1.6MHz. The interfering signal offset is defined relative to the lower / upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -0.8MHz/+0.8MHz, respectively. + +**Table 7.4.5.3-1: Parameters of the wanted signal and the interfering signal for ACS testing for 1,28 Mcps TDD** + +| Parameter | | Level | Unit | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------|--------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -104 | dBm | +| | Local Area BS | -90 | dBm | +| Interfering signal mean power | Wide Area BS | -55 | dBm | +| | Local Area BS | -41 | dBm | +| Fuw (modulated) | | ±1,6 | MHz | +| NOTE: | Fuw is the frequency offset of the unwanted interfering signal from the assigned channel frequency of the wanted signal. | | | + +#### 7.4.5.4 Single RAT E-UTRA operation + +For each measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel. + +For AAS BS of wide area BS class the wanted and the interfering signal coupled to the *TAB connector* are specified in table 7.4.5.4-1 and 7.4.5.4-2 for narrowband blocking and 7.4.5.4-3 for ACS. The reference measurement channel for the wanted signal is specified in table 7.2.5.3-1 for each channel bandwidth and further specified in annex A in TS 36.141 [17]. + +For AAS BS of Medium Range BS class, the wanted and the interfering signal coupled to the *TAB connector* are specified in tables 7.4.5.4-1 and 7.4.5.4-2 for narrowband blocking and in table 7.4.5.4-5 for ACS. The reference measurement channel for the wanted signal is specified in table 7.2.5.3-3 for each channel bandwidth and further specified in annex A in TS 36.141 [17]. + +For AAS BS of Local Area BS class, the wanted and the interfering signal coupled to the *TAB connector* are specified in tables 7.4.5.4-1 and 7.4.5.4-2 for narrowband blocking and 7.4.5.4-4 for ACS. The reference measurement channel for the wanted signal is specified in table 7.2.5.3-2 for each channel bandwidth and further specified in annex A in TS 36.141 [17]. + +The ACS and narrowband blocking requirement is always applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the *Base station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For a *TAB connector* operating in non-contiguous spectrum within any operating band, the ACS requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least as wide as the E-UTRA interfering signal in tables 7.4.5.4-3, 7.4.5.4-4 and 7.4.5.4-5. The interfering signal offset is defined relative to the sub-block edges inside the *sub-block gap*. + +For a *multi-band TAB connector*, the ACS requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least as wide as the E-UTRA interfering signal in tables 7.4.5.4-3, 7.4.5.4-4 and 7.4.5.4-5. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For a *TAB connector* operating in non-contiguous spectrum within any operating band, the narrowband blocking requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least as wide as the channel bandwidth of the E-UTRA interfering signal in table 7.4.5.4-2. The interfering signal offset is defined relative to the sub-block edges inside the *sub-block gap*. + +For a *multi-band TAB connector*, the narrowband blocking requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least as wide as the E-UTRA interfering signal in table 7.4.5.4-2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 7.4.5.4-1: Narrowband blocking requirement** + +| | Wanted signal mean power (dBm) (Note) | Interfering signal mean power (dBm) | Type of interfering signal | +|----------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------|----------------------------| +| Wide Area BS | $P_{REFSENS} + 6$ dB | -49 | See table 7.4.5.4-2 | +| Medium Range BS | $P_{REFSENS} + 6$ dB | -44 | See table 7.4.5.4-2 | +| Local Area BS | $P_{REFSENS} + 6$ dB | -41 | See table 7.4.5.4-2 | +| NOTE: $P_{REFSENS}$ depends on the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1. | | | | + +**Table 7.4.5.4-2: Interfering signal for Narrowband blocking requirement** + +| E-UTRA channel BW of the lowest/highest carrier received (MHz) | Interfering RB centre frequency offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (kHz) | Type of interfering signal (Note) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| 1.4 | $\pm(252.5+m*180)$ ,
m=0, 1, 2, 3, 4, 5 | 1.4 MHz E-UTRA signal, 1 RB | +| 3 | $\pm(247.5+m*180)$ ,
m=0, 1, 2, 3, 4, 7, 10, 13 | 3 MHz E-UTRA signal, 1 RB | +| 5 | $\pm(342.5+m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz E-UTRA signal, 1 RB | +| 10 | $\pm(347.5+m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz E-UTRA signal, 1 RB | +| 15 | $\pm(352.5+m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz E-UTRA signal, 1 RB | +| 20 | $\pm(342.5+m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz E-UTRA signal, 1 RB | +| NOTE: Interfering signal consisting of one resource block is positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the lower/upper Base Station RF Bandwidth edge . | | | + +**Table 7.4.5.4-3: Adjacent channel selectivity for Wide Area BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) (Note) | Interfering signal mean power (dBm) | Interfering signal centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|----------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1.4 | $P_{REFSENS} + 11$ dB | -52 | $\pm 0.7025$ | 1.4 MHz E-UTRA signal | +| 3 | $P_{REFSENS} + 8$ dB | -52 | $\pm 1.5075$ | 3 MHz E-UTRA signal | +| 5 | $P_{REFSENS} + 6$ dB | -52 | $\pm 2.5025$ | 5 MHz E-UTRA signal | +| 10 | $P_{REFSENS} + 6$ dB | -52 | $\pm 2.5075$ | 5 MHz E-UTRA signal | +| 15 | $P_{REFSENS} + 6$ dB | -52 | $\pm 2.5125$ | 5 MHz E-UTRA signal | +| 20 | $P_{REFSENS} + 6$ dB | -52 | $\pm 2.5025$ | 5 MHz E-UTRA signal | +| NOTE: $P_{REFSENS}$ depends on the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1. | | | | | + +**Table 7.4.5.4-4: Adjacent channel selectivity for Local Area BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) (Note) | Interfering signal mean power (dBm) | Interfering signal centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|-----------------------------------------------------------------------|---------------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1.4 | $P_{\text{REFSENS}} + 11$ dB | -44 | $\pm 0.7025$ | 1.4 MHz E-UTRA signal | +| 3 | $P_{\text{REFSENS}} + 8$ dB | -44 | $\pm 1.5075$ | 3 MHz E-UTRA signal | +| 5 | $P_{\text{REFSENS}} + 6$ dB | -44 | $\pm 2.5025$ | 5 MHz E-UTRA signal | +| 10 | $P_{\text{REFSENS}} + 6$ dB | -44 | $\pm 2.5075$ | 5 MHz E-UTRA signal | +| 15 | $P_{\text{REFSENS}} + 6$ dB | -44 | $\pm 2.5125$ | 5 MHz E-UTRA signal | +| 20 | $P_{\text{REFSENS}} + 6$ dB | -44 | $\pm 2.5025$ | 5 MHz E-UTRA signal | + +NOTE: $P_{\text{REFSENS}}$ depends on the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1. + +**Table 7.4.5.4-5: Adjacent channel selectivity for Medium Range BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Interfering signal centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|-----------------------------------------------------------------------|--------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1.4 | $P_{\text{REFSENS}} + 11$ dB | -47 | $\pm 0.7025$ | 1.4 MHz E-UTRA signal | +| 3 | $P_{\text{REFSENS}} + 8$ dB | -47 | $\pm 1.5075$ | 3 MHz E-UTRA signal | +| 5 | $P_{\text{REFSENS}} + 6$ dB | -47 | $\pm 2.5025$ | 5 MHz E-UTRA signal | +| 10 | $P_{\text{REFSENS}} + 6$ dB | -47 | $\pm 2.5075$ | 5 MHz E-UTRA signal | +| 15 | $P_{\text{REFSENS}} + 6$ dB | -47 | $\pm 2.5125$ | 5 MHz E-UTRA signal | +| 20 | $P_{\text{REFSENS}} + 6$ dB | -47 | $\pm 2.5025$ | 5 MHz E-UTRA signal | + +NOTE: $P_{\text{REFSENS}}$ depends on the channel bandwidth as specified in TS 36.104 [11], clause 7.2.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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 7.5 Blocking + +### 7.5.1 Definition and applicability + +The out-of-band blocking characteristic is a measure of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer outside the *uplink operating band*. + +### 7.5.2 Minimum requirement + +The minimum requirement for MSR operation is in TS 37.105 [8], clause 7.5.2. + +The minimum requirement for single RAT UTRA operation is in TS 37.105 [8], clause 7.5.3. + +The minimum requirement for single RAT E-UTRA operation is in TS 37.105 [8], clause 7.5.4. + +The minimum requirement for NR operation is in TS 38.104 [36], clause 7.5.2. + +### 7.5.3 Test purpose + +The test stresses the ability of the receiver unit associated with the *TAB connector* under test to withstand high-level interference from unwanted signals at specified frequency bands, without undue degradation of its sensitivity. + +### 7.5.4 Method of test + +#### 7.5.4.1 Initial conditions + +Test environment: + +- Normal; see clause B.2. + +RF channels to be tested for single carrier (SC): + +- M; see clause 4.12.1 + +*Base Station RF Bandwidth* positions to be tested for multi-carrier (MC): + +- $M_{\text{RFBW}}$ for *single-band TAB connector(s)*, see clause 4.12.1, $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ for *multi-band TAB connector(s)*, see clause 4.12.1. + +In addition, for *multi-band TAB connectors*: + +- For $B_{\text{RFBW\_T'RFBW}}$ , out-of-band blocking testing above the highest operating band may be omitted. +- For $B'_{\text{RFBW\_T'RFBW}}$ , out-of-band blocking testing below the lowest operating band may be omitted. + +#### 7.5.4.2 Procedure + +##### 7.5.4.2.1 General Procedure + +The general procedure steps apply to the procedures for all the RATs. + +The minimum requirement is applied to all *TAB connectors*, the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1: + +- 1) Connect *TAB connector* to measurement equipment as shown in annex D.2.3. All *TAB connectors* not under test shall be terminated. + +##### 7.5.4.2.2 MSR operation + +- 1) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the *TAB connector* under test as follows: + +- For E-UTRA see clause A.1 in TS 36.141 [17]. +- For UTRA FDD see clause A.2 in TS 25.141 [18]. +- For UTRA TDD see clause A.2.1 in TS 25.142 [20]. +- For NR, see clause [4.11] + +- 2) Set the transmitter unit associated with the *TAB connector* under test to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +The transmitter unit associated with the *TAB connector* under test may be turned off for the out-of-band blocker tests when the frequency of the blocker is such that no IM2 or IM3 products fall inside the bandwidth of the wanted signal. + +- 3) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified for general test requirements in table 7.5.5.1.1-1 and, when applicable, for co-location test requirements in table 7.5.5.1.2-1. + +- 4) The CW interfering signal shall be swept with a step size of 1 MHz within the specified range. +- 5) Measure the performance of the wanted signal at the receiver unit associated with the *TAB connector*, as defined in the clause 7.5.5, for the relevant carriers specified by the test configuration in clause 4.11. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.5.4.2.3 Single RAT UTRA FDD operation + +- 1) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the *TAB connector* under test as shown in clause A.2.1 in TS 25.141 [18]. +- 2) Set the transmitter unit associated with the *TAB connector* under test to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +The transmitter unit associated with the *TAB connector* under test may be turned off for the out-of-band blocker tests when the frequency of the blocker is such that no IM2 or IM3 products fall inside the bandwidth of the wanted signal. + +- 3) Adjust the signal generators to the type of interfering signals and the frequency offsets as specified in tables 7.5.5.2-1 to 7.5.5.2-9. Note that the GMSK modulated interfering signal shall have an ACLR of at least 72 dB in order to eliminate the impact of interfering signal adjacent channel leakage power on the blocking characteristics measurement. For the tests defined in tables 7.5.5.2-1 to 7.5.5.2-9, the interfering signal shall be at a frequency offset $F_{uw}$ from the assigned channel frequency of the wanted signal which is given by: + +$$F_{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 centre frequency of the interfering signal covers the range from 1 MHz to 12,75 GHz. + +- 4) Measure the BER of the wanted signal at the receiver unit associated with the *TAB connector* under test. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.5.4.2.4 Single RAT UTRA TDD 1,28 Mcps option operation + +- 1) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the *TAB connector* under test as shown in clause A.2.1 in TS 25.142 [20]. +- 2) Set the transmitter unit associated with the *TAB connector* under test to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +The transmitter unit associated with the *TAB connector* under test may be turned off for the out-of-band blocker tests when the frequency of the blocker is such that no IM2 or IM3 products fall inside the bandwidth of the wanted signal. + +- 3) Set the signal generator to produce an interfering signal at a frequency offset $F_{uw}$ from the assigned channel frequency of the wanted signal which is given by + +$$F_{uw} = \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 centre frequency of the interfering signal covers the range from 1 MHz to 12,75 GHz. The interfering signal level measured at the *TAB connector* shall be set in dependency of its centre frequency, as specified in tables 7.5.5.3.1-1 to 7.5.5.3.1-9 and 7.5.5.3.2-1. The type of the interfering signal is either equivalent to a continuous wideband CDMA signal with one code of chip frequency 1,28 Mcps, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ , or a CW signal; see tables 7.5.5.3.1-1 to 7.5.5.3.1-9 and 7.5.5.3.2-1. + +- 4) Measure the BER of the wanted signal at the receiver unit associated with the *TAB connector* under test. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.5.4.2.5 Single RAT E-UTRA operation + +- 1) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the *TAB connector* under test as shown in clause A.1 in TS 36.141 [17]. +- 2) Set the transmitter unit associated with the *TAB connector* under test to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +The transmitter unit associated with the *TAB connector* under test may be turned off for the out-of-band blocker tests when the frequency of the blocker is such that no IM2 or IM3 products fall inside the bandwidth of the wanted signal. + +- 3) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified for general test requirements in tables 7.5.5.4.1-1 and 7.5.5.4.2-1 for AAS BS of wide area BS class, tables 7.5.5.4.1-2 and 7.5.5.4.2-1 for AAS BS of local area BS class and tables 7.5.5.4.1-3 and 7.5.5.4.2-1 for AAS BS of medium range BS class. +- 4) The CW interfering signal shall be swept with a step size of 1 MHz within the specified range. +- 5) Measure the performance of the wanted signal at the receiver unit associated with the *TAB connector*, as defined in the clause 7.5.5, for the relevant carriers specified by the test configuration in clause 4.11. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 7.5.5 Test requirements + +#### 7.5.5.1 MSR operation + +##### 7.5.5.1.1 General out-of-band blocking test requirements + +For a wanted and an interfering signal coupled to a *TAB connector* using the parameters in table 7.5.5.1.1-1, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.3. +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.4. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.1. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.2. + +The out-of-band blocking requirement applies from 1 MHz to $F_{UL\_low} - \Delta f_{OOB}$ and from $F_{UL\_high} + \Delta f_{OOB}$ up to 12750 MHz, including the downlink frequency range of the FDD *operating band* for BS supporting FDD. The $\Delta f_{OOB}$ is defined in table 7.4.1-1. + +The in-band blocking frequency ranges of all supported operating bands shall be excluded from the requirement. + +**Table 7.5.5.1.1-1: Blocking performance requirement** + +| Wanted Signal mean power [dBm] | Interfering Signal mean power [dBm] | Type of Interfering Signal | +|----------------------------------------------------------------------------------------------------------------|-------------------------------------|----------------------------| +| $P_{\text{REFSENS}} + 6$ dB (Note) | -15 | CW carrier | +| NOTE: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and the channel bandwidth ; see clause 7.2. | | | + +### 7.5.5.1.2 Co-location test requirements + +This additional blocking requirement may be applied for the protection of receiver units associated with *TAB connectors* when a E-UTRA, UTRA, CDMA or GSM/EDGE BS operating in a different frequency band are co-located with the AAS BS. + +The requirements in this clause assume a 30 dB coupling loss between the interfering transmitter and the *TAB connector* and are based on co-location with base stations of the same class. + +For a wanted and an interfering signal coupled to *TAB connector* using the parameters in table 7.5.5.1.2-1, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.3. +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.4. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.1. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.2. + +**Table 7.5.5.1.2-1: Blocking requirement for co-location with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| GSM900 | 921 - 960 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| DCS1800 | 1805 - 1880 (Note 4) | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| PCS1900 | 1930 - 1990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 (Note 4) | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 - 885 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 - 2690 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 - 1495.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 - 768 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 17 | 734 - 746 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 18 or NR band n18 | 860 - 875 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 - 890 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XX or E-UTRA | 791 - 821 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| Band 20 or NR band n20 | | | | | | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 - 1510.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3590 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1525 - 1559 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 - 1995 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 859 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 27 | 852 - 869 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 28 or NR band n28 | 758 - 803 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717 - 728 | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6$ dB | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2350 - 2360 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6$ dB | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 (Note 5) | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6$ dB | CW carrier | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900-1920 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010-2025 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850-1910 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930-1990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910-1930 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570-2620 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880-1920 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300-2400 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 42 | 3400 - 3600 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 43 | 3600 - 3800 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 44 | 703 - 803 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | +| E-UTRA Band 46 | 5150 - 5925 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x$ dB | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|----------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| or NR Band n46 | | | | | | | +| E-UTRA Band 48 or NR Band n48 | 3550 - 3700 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 49 | 3550 - 3700 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 50 or NR band n50 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 51 or NR band n51 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 52 | 3300 - 3400 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 - 1675 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 - 2200 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 66 or NR band n66 | 2110 - 2200 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 69 | 2570 - 2620 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 70 or NR band n70 | 1995 - 2020 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 71 or or NR band n71 | 617 - 652 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 75 or or NR band n75 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 76 or or NR band n76 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n77 | 3300 - 4200 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n78 | 3300 - 3800 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n79 | 4400 - 5000 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 85 or or NR band n85 | 728 - 746 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 87 | 420 - 425 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 88 | 422 - 427 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n91 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n92 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n93 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n94 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n96 | 5925 - 7125 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n100 | 919.4 - 925 | +16 | N/A | N/A | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n101 | 1900 - 1910 | +16 | N/A | N/A | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 103 | 757 - 758 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR Band n104 | 6425 - 7125 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR Band n105 | 612 - 652 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 106 or NR Band n106 | 935 - 940 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR Band n109 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and the channel bandwidth, see clause 7.2. +"x" is equal to 6 in case of UTRA or E-UTRA or NR wanted signals. + +NOTE 2: Except for a *TAB connector* operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported *uplink operating band* or in the $\Delta f_{\text{OOB}}$ immediately outside any of the supported *uplink operating band*. +For a *TAB connector* operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768-797MHz. + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| NOTE 3: 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 or E-UTRA TDD or NR TDD with E-UTRA FDD on adjacent frequencies for 30 dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [21]. | | | | | | | +| NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805-1850 MHz. | | | | | | | +| NOTE 5: For a TAB connector operating in band 11 or 21, this requirement applies for interfering signal within the frequency range 1475.9-1495.9 MHz. | | | | | | | +| NOTE 6: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can receive without special co-location requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. | | | | | | | + +### 7.5.5.2 Single RAT UTRA FDD operation + +For each measured carrier, the BER shall not exceed 0.001 for the parameters specified in tables 7.5.5.2-1 to 7.5.5.2-9 if applicable for the *TAB connector* under test. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the lower/upper *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For a *TAB connector* operating in non-contiguous spectrum within any operating band, the blocking requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 15 MHz. The interfering signal offset is defined relative to the lower/upper sub-block edge inside the *sub-block gap* and is equal to -7.5 MHz/+7.5 MHz, respectively. + +For a *TAB connector* operating in non-contiguous spectrum within any operating band, the narrowband blocking requirements in tables 7.5.5.2-7 to 7.5.5.2-9 apply in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 400 kHz or 600 kHz, depending on the operating band. The interfering signal offset is defined relative to the lower/upper sub-block edge inside the *sub-block gap* and is equal to -200 kHz/+200 kHz or -300 kHz/+300 kHz, respectively. + +For a *multi-band TAB connector*, the requirement in the in-band blocking frequency range applies for each supported operating band. The requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least 15 MHz. The interfering signal offset is defined relative to lower/upper *Base Station RF bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -7.5 MHz/+7.5 MHz, respectively. + +For a *multi-band TAB connector*, the requirement in the out-of-band blocking frequency ranges apply for each operating band, with the exception that the in-band blocking frequency ranges of all supported operating bands according to tables 7.5.5.2-1 to 7.5.5.2-3 shall be excluded from the out-of-band blocking requirement. + +For a *multi-band TAB connector*, the narrowband blocking requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least 400 kHz or 600 kHz, depending on the operating band. The interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -200 kHz/+200 kHz or -300 kHz/+300 kHz, respectively. + +**Table 7.5.5.2-1: Blocking characteristics for Wide Area BS** + +| Operating Band | Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| I | 1920 - 1980 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1900 - 1920 MHz
1980 - 2000 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1900 MHz
2000 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| II | 1850 - 1910 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1830 - 1850 MHz
1910 - 1930 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1830 MHz
1930 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| III | 1710 - 1785 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1690 - 1710 MHz
1785 - 1805 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1690 MHz
1805 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| IV | 1710 - 1755 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1690 - 1710 MHz
1755 - 1775 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1690 MHz
1775 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| V | 824-849 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 804-824 MHz
849-869 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 804 MHz
869 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| VI | 810 - 830 MHz
840 - 860 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 810 MHz
860 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| VII | 2500 - 2570 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 2480 - 2500 MHz
2570 - 2590 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 2480 MHz
2590 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| VIII | 880 - 915 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 860 - 880 MHz
915 - 925 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 860 MHz
925 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| IX | 1749.9 - 1784.9 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1729.9 - 1749.9 MHz
1784.9 - 1804.9 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1729.9 MHz
1804.9 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| X | 1710 - 1770 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1690 - 1710 MHz
1770 - 1790 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1690 MHz
1790 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XI | 1427.9 - 1447.9 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1407.9 - 1427.9 MHz
1447.9 - 1467.9 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | + +| Operating Band | Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| | 1 MHz - 1407.9 MHz
1467.9 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XII | 699 - 716 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 679 - 699 MHz
716 - 729 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 679 MHz
729 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XIII | 777 - 787 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 757 - 777 MHz
787 - 807 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 - 757 MHz
807 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XIV | 788 - 798 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 768 - 788 MHz
798 - 818 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 - 768 MHz
818 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XIX | 830 - 845 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 810 - 830 MHz
845 - 865 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 810 MHz
865 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XX | 832 - 862 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 821 - 832 MHz
862 - 882 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 821 MHz
882 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XXI | 1447.9 - 1462.9 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1427.9 - 1447.9 MHz
1462.9 - 1482.9 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1427.9 MHz
1482.9 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XXII | 3410 - 3490 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 3390 - 3410 MHz
3490 - 3510 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 3390 MHz
3510 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XXV | 1850 - 1915 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1830 - 1850 MHz
1915 - 1930 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1830 MHz
1930 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | +| XXVI | 814-849 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 794-814 MHz
849-859 MHz | -40 dBm | -115 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 794 MHz
859 MHz - 12750 MHz | -15 dBm | -115 dBm | – | CW carrier | + +NOTE 1: The characteristics of the W-CDMA interfering signal are specified in annex I of TS 25.141 [18]. + +NOTE 2: For a *multi-band TAB connector*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, or in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to -119.6 dBm. + +NOTE: Table 7.5.5.2-1 assumes that two operating bands, where the downlink frequencies (see TS 25.141 [18] table 3.0) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.5.5.2-2: Blocking characteristics for Medium Range BS** + +| Operating Band | Centre Frequency of Interfering Signal | Interfering Signal Level | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------------|--------------------------|--------------------------|--------------------------------------|----------------------------| +| I | 1920 - 1980 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1900 - 1920 MHz
1980 - 2000 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1900 MHz
2000 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| II | 1850 - 1910 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1830 - 1850 MHz
1910 - 1930 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1830 MHz
1930 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| III | 1710 - 1785 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1690 - 1710 MHz
1785 - 1805 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1690 MHz
1805 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| IV | 1710 - 1755 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1690 - 1710 MHz
1755 - 1775 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1690 MHz
1775 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| V | 824-849 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 804-824 MHz
849-869 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 804 MHz
869 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| VI | 810 - 830 MHz
840 - 860 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 810 MHz
860 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| VII | 2500 - 2570 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 2480 - 2500 MHz
2570 - 2590 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 2480 MHz
2590 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| VIII | 880 - 915 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 860 - 880 MHz
915 - 925 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 860 MHz
925 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| IX | 1749.9 - 1784.9 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1729.9 - 1749.9 MHz
1784.9 - 1804.9 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1729.9 MHz
1804.9 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| X | 1710 - 1770 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1690 - 1710 MHz
1770 - 1790 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1690 MHz
1790 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XI | 1427.9 - 1447.9 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1407.9 - 1427.9 MHz
1447.9 - 1467.9 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | + +| Operating Band | Centre Frequency of Interfering Signal | Interfering Signal Level | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------------|--------------------------|--------------------------|--------------------------------------|----------------------------| +| | 1 MHz - 1407.9 MHz
1467.9 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XII | 699 - 716 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 679 - 699 MHz
716 - 729 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 679 MHz
729 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XIII | 777 - 787 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 757 - 777 MHz
787 - 807 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 - 757 MHz
807 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XIV | 788 - 798 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 768 - 788 MHz
798 - 818 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 - 768 MHz
818 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XIX | 830 - 845 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 810 - 830 MHz
845 - 865 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 810 MHz
865 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XX | 832 - 862 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 821 - 832 MHz
862 - 882 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 821 MHz
882 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XXI | 1447.9 - 1462.9 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1427.9 - 1447.9 MHz
1462.9 - 1482.9 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1427.9 MHz
1482.9 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XXII | 3410 - 3490 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 3390 - 3410 MHz
3490 - 3510 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 3390 MHz
3510 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XXV | 1850 - 1915 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1830 - 1850 MHz
1915 - 1930 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1830 MHz
1930 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | +| XXVI | 814-849 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 794-814 MHz
849-859 MHz | -35 dBm | -105 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 794 MHz
859 MHz - 12750 MHz | -15 dBm | -105 dBm | – | CW carrier | + +NOTE 1: The characteristics of the WCDMA interfering signal are specified in annex I of TS 25.141 [18]. + +NOTE 2: For a *multi-band TAB connector*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, or in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to -109.6 dBm. + +NOTE: Table 7.5.5.2-2 assumes that two operating bands, where the downlink frequencies (see TS 25.141 [18] Table 3.0) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.5.5.2-3: Blocking characteristics for Local Area** + +| Operating Band | Centre Frequency of Interfering Signal | Interfering Signal Level | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------------|--------------------------|--------------------------|--------------------------------------|----------------------------| +| I | 1920 - 1980 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1900 - 1920 MHz
1980 - 2000 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1900 MHz
2000 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| II | 1850 - 1910 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1830 - 1850 MHz
1910 - 1930 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1830 MHz
1930 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| III | 1710 - 1785 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1690 - 1710 MHz
1785 - 1805 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1690 MHz
1805 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| IV | 1710 - 1755 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1690 - 1710 MHz
1755 - 1775 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1690 MHz
1775 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| V | 824-849 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 804-824 MHz
849-869 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 804 MHz
869 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| VI | 810 - 830 MHz
840 - 860 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 810 MHz
860 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| VII | 2500 - 2570 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 2480 - 2500 MHz
2570 - 2590 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 2480 MHz
2590 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| VIII | 880 - 915 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 860 - 880 MHz
915 - 925 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 860 MHz
925 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| IX | 1749.9 - 1784.9 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1729.9 - 1749.9 MHz
1784.9 - 1804.9 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1729.9 MHz
1804.9 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| X | 1710 - 1770 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1690 - 1710 MHz
1770 - 1790 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1690 MHz
1790 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XI | 1427.9 - 1447.9 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1407.9 - 1427.9 MHz
1447.9 - 1467.9 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | + +| Operating Band | Centre Frequency of Interfering Signal | Interfering Signal Level | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------------|--------------------------|--------------------------|--------------------------------------|----------------------------| +| | 1 MHz - 1407.9 MHz
1467.9 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XII | 699 - 716 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 679 - 699 MHz
716 - 729 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 679 MHz
729 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XIII | 777 - 787 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 757 - 777 MHz
787 - 807 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 - 757 MHz
807 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XIV | 788 - 798 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 768 - 788 MHz
798 - 818 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 - 768 MHz
818 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XIX | 830 - 845 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 810 - 830 MHz
845 - 865 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 810 MHz
865 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XX | 832 - 862 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 821 - 832 MHz
862 - 882 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 821 MHz
882 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XXI | 1447.9 - 1462.9 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1427.9 - 1447.9 MHz
1462.9 - 1482.9 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1427.9 MHz
1482.9 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XXII | 3410 - 3490 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 3390 - 3410 MHz
3490 - 3510 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 3390 MHz
3510 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XXV | 1850 - 1915 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1830 - 1850 MHz
1915 - 1930 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 1830 MHz
1930 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | +| XXVI | 814-849 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 794-814 MHz
849-859 MHz | -30 dBm | -101 dBm | ±10 MHz | WCDMA signal (Note 1) | +| | 1 MHz - 794 MHz
859 MHz - 12750 MHz | -15 dBm | -101 dBm | – | CW carrier | + +NOTE 1: The characteristics of the WCDMA interfering signal are specified in annex I of TS 25.141 [18]. + +NOTE 2: For a *multi-band TAB connector*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, or in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to -105.6 dBm. + +NOTE: Table 7.5.5.2-3 assumes that two operating bands, where the downlink frequencies (see TS 25.141 [18] table 3.0) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.5.5.2-4: Blocking performance requirement when co-located with BS in other bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 - 894 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| GSM900 | 921 - 960 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| DCS1800 | 1805 - 1880 (Note 4) | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| PCS1900 | 1930 - 1990 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 (Note 4) | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 - 885 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 - 1495.9 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 - 768 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| E-UTRA Band 17 | 734 - 746 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| E-UTRA Band 18 or NR band n18 | 860 - 875 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 - 890 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR | 791 - 821 | +16 | +8 | -6 | $P_{REFSENS} + x$ dB | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| band n20 | | | | | | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 - 1510.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3590 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1525 - 1559 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 - 1995 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 859 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 27 | 852 - 869 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 28 or NR band n28 | 758 - 803 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717 - 728 | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6 \text{ dB}$ | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2350 - 2360 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6 \text{ dB}$ | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 (Note 5) | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6 \text{ dB}$ | CW carrier | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900-1920 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010-2025 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850-1910 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930-1990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910-1930 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570-2620 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880-1920 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300-2400 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 42 | 3400 - 3600 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 43 | 3600 - 3800 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 44 | 703 - 803 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|----------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| E-UTRA Band 48 or NR Band n48 | 3550 - 3700 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 49 | 3550 - 3700 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 51 or NR band n51 | 1427– 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 53 or NR band n53 | 2483.5 – 2495 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 - 2200 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 66 or NR band n66 | 2110 - 2200 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 69 | 2570 - 2620 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 70 or NR band n70 | 1995 - 2020 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 71 or or NR band n71 | 617 - 652 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 75 or or NR band n75 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 76 or or NR band n76 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n77 | 3300 - 4200 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n78 | 3300 - 3800 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n79 | 4400 - 5000 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 – 746 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 87 | 420 - 425 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 88 | 422 - 427 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n91 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n92 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n93 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n94 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n96 | 5925 - 7125 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 103 | 757 – 758 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR Band n104 | 6425 – 7125 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR Band n105 | 612 – 652 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 106 | 935 – 940 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n109 | 1432 – 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | + +NOTE 1: $P_{\text{REFSENS}}$ depends on, the BS class and the channel bandwidth, see clause 7.2. +"x" is equal to 6 in case of UTRA wanted signals. + +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 or E-UTRA TDD with E-UTRA FDD on adjacent frequencies for 30 dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [21]. + +NOTE 3: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805-1850 MHz. + +NOTE 4: For a *TAB connector* operating in band XI or XXI, this requirement applies for interfering signal within the frequency range 1475.9-1495.9 MHz. + +Table 7.5.5.2-5: Void + +Table 7.5.5.2-6: Void + +Table 7.5.5.2-7: Blocking performance requirement (narrowband) for Wide Area BS + +| Operating Band | Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal (Note) | +|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|-----------------------------------| +| II | 1850 - 1910 MHz | - 47 dBm | -115 dBm | ±2.7 MHz | GMSK modulated | +| III | 1710 - 1785 MHz | - 47 dBm | -115 dBm | ±2.8 MHz | GMSK modulated | +| IV | 1710 - 1755 MHz | - 47 dBm | -115 dBm | ±2.7 MHz | GMSK modulated | +| V | 824 - 849 MHz | - 47 dBm | -115 dBm | ±2.7 MHz | GMSK modulated | +| VIII | 880 - 915 MHz | - 47 dBm | -115 dBm | ±2.8 MHz | GMSK modulated | +| X | 1710 - 1770 MHz | - 47 dBm | -115 dBm | ±2.7 MHz | GMSK modulated | +| XII | 699 - 716 MHz | - 47 dBm | -115 dBm | ±2.7 MHz | GMSK modulated | +| XIII | 777 - 787 MHz | - 47 dBm | -115 dBm | ±2.7 MHz | GMSK modulated | +| XIV | 788 - 798 MHz | - 47 dBm | -115 dBm | ±2.7 MHz | GMSK modulated | +| XXV | 1850 - 1915 MHz | - 47 dBm | -115 dBm | ±2.7 MHz | GMSK modulated | +| XXVI | 814-849 MHz | -47 dBm | -115 dBm | ±2.7 MHz | GMSK modulated | + +NOTE: GMSK modulation as defined in TS 45.004 [22]. + +Table 7.5.5.2-8: Blocking performance requirement (narrowband) for Medium range BS + +| Operating Band | Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| II | 1850 - 1910 MHz | - 42 dBm | -105 dBm | ±2.7 MHz | GMSK modulated | +| III | 1710 - 1785 MHz | - 42 dBm | -105 dBm | ±2.8 MHz | GMSK modulated | +| IV | 1710 - 1755 MHz | - 42 dBm | -105 dBm | ±2.7 MHz | GMSK modulated | +| V | 824 - 849 MHz | - 42 dBm | -105 dBm | ±2.7 MHz | GMSK modulated | +| VIII | 880 - 915 MHz | - 42 dBm | -105 dBm | ±2.8 MHz | GMSK modulated | +| X | 1710 - 1770 MHz | - 42 dBm | -105 dBm | ±2.7 MHz | GMSK modulated | +| XII | 699 - 716 MHz | - 42 dBm | -105 dBm | ±2.7 MHz | GMSK modulated | +| XIII | 777 - 787 MHz | - 42 dBm | -105 dBm | ±2.7 MHz | GMSK modulated | +| XIV | 788 - 798 MHz | - 42 dBm | -105 dBm | ±2.7 MHz | GMSK modulated | +| XXV | 1850 - 1915 MHz | - 42 dBm | -105 dBm | ±2.7 MHz | GMSK modulated | +| XXVI | 814-849 MHz | - 42 dBm | -105 dBm | ±2.7 MHz | GMSK modulated | + +NOTE: GMSK modulation as defined in TS 45.004 [22]. + +Table 7.5.5.2-9: Blocking performance requirement (narrowband) for Local Area + +| Operating Band | Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| II | 1850 - 1910 MHz | - 37 dBm | -101 dBm | ±2.7 MHz | GMSK modulated | +| III | 1710 - 1785 MHz | - 37 dBm | -101 dBm | ±2.8 MHz | GMSK modulated | +| IV | 1710 - 1755 MHz | - 37 dBm | -101 dBm | ±2.7 MHz | GMSK modulated | +| V | 824 - 849 MHz | - 37 dBm | -101 dBm | ±2.7 MHz | GMSK modulated | +| VIII | 880 - 915 MHz | - 37 dBm | -101 dBm | ±2.8 MHz | GMSK modulated | +| X | 1710 - 1770 MHz | - 37 dBm | -101 dBm | ±2.7 MHz | GMSK modulated | +| XII | 699 - 716 MHz | - 37 dBm | -101 dBm | ±2.7 MHz | GMSK modulated | +| XIII | 777 - 787 MHz | - 37 dBm | -101 dBm | ±2.7 MHz | GMSK modulated | +| XIV | 788 - 798 MHz | - 37 dBm | -101 dBm | ±2.7 MHz | GMSK modulated | +| XXV | 1850 - 1915 MHz | - 37 dBm | -101 dBm | ±2.7 MHz | GMSK modulated | +| XXVI | 814-849 MHz | - 37 dBm | -101 dBm | ±2.7 MHz | GMSK modulated | + +NOTE: GMSK modulation as defined in TS 45.004 [22]. + +NOTE 1: 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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +NOTE 2: Annex C of TS 25.141 [18] 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.5.5.3 Single RAT UTRA TDD 1,28 Mcps option operation + +#### 7.5.5.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 *TAB connector* using the parameters specified in table 7.5.5.3.1-1 to table 7.5.5.3.1-12, respectively. + +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 *Base Station RF Bandwidth* edges or *Maximum Radio Bandwidth* edges. + +For *multi-band TAB connector*, the requirement in the in-band blocking frequency range applies for each supported operating band. The requirements applies in addition inside any *Inter RF Bandwidth gap* as long as the Inter RF Bandwidth gap size is at least 4.8MHz. The interfering signal offset is defined relative to the lower / upper *Base Station RF Bandwidth* edges inside the Inter RF Bandwidth gap and is equal to -2.4 MHz/+2.4 MHz, respectively. + +For *multi-band TAB connector*, the requirement in the out-of-band blocking frequency ranges apply for each supported operating band, with the exception that the in-band blocking frequency ranges of all supported operating bands shall be excluded from the out-of-band blocking requirement. + +**Table 7.5.5.3.1-1: Blocking requirements for Wide Area BS in operating bands defined in clause 4.5 a) for 1,28 Mcps TDD** + +| 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 | -104 dBm | $\pm 3.2$ MHz | 1,28 Mcps TDD signal with one code | +| 1880 - 1900 MHz,
1990 - 2010 MHz,
2025 - 2045 MHz | -40 dBm | -104 dBm | $\pm 3.2$ MHz | 1,28 Mcps TDD signal with one code | +| 1920 - 1980 MHz | -40 dBm | -104 dBm | $\pm 3.2$ MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1880 MHz,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | -104 dBm | — | CW carrier | + +NOTE: For *multi-band TAB connector*, 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 -108.6 dBm. + +**Table 7.5.5.3.1-2: Blocking requirements for Wide Area BS +in operating bands defined in clause 4.5 b) for 1,28 Mcps TDD** + +| 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 | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1830 - 1850 MHz,
1990 - 2010 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | -104 dBm | – | CW carrier | + +NOTE: For *multi-band TAB connector*, 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 -108.6 dBm. + +**Table 7.5.5.3.1-3: Blocking requirements for Wide Area BS +in operating bands defined in clause 4.5 c) for 1,28 Mcps TDD** + +| 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 | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1890 - 1910 MHz,
1930 - 1950 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | -104 dBm | – | CW carrier | + +NOTE: For *multi-band TAB connector*, 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 -108.6 dBm. + +**Table 7.5.5.3.1-4: Blocking requirements for Wide Area BS +in operating bands defined in clause 4.5 d) for 1,28 Mcps TDD** + +| 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 | -104 dBm | ±3.2MHz | 1,28 Mcps TDD signal with one code | +| 2500 - 2570 MHz,
2620 - 2690 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 2500 MHz,
2690 - 12750 MHz | -15 dBm | -104 dBm | – | CW carrier | + +NOTE: For *multi-band TAB connector*, 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 -108.6 dBm. + +**Table 7.5.5.3.1-5: Blocking requirements for Wide Area BS +in operating bands defined in clause 4.5 e) for 1,28 Mcps TDD** + +| Centre Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|------------------------------------| +| 2300 - 2400 MHz | -40 dBm | -104 dBm | ±3.2MHz | 1,28 Mcps TDD signal with one code | +| 2280 - 2300 MHz,
2400 - 2420 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 2280 MHz,
2420 - 12750 MHz | -15 dBm | -104 dBm | – | CW carrier | + +NOTE: For *multi-band TAB connector*, 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 -108.6 dBm. + +**Table 7.5.5.3.1-6: Blocking requirements for Wide Area BS +in operating bands defined in clause 4.5 f) for 1,28Mcps TDD** + +| Centre Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|---------------------------------------| +| 1880 - 1920 MHz | -40 dBm | -104 dBm | ±3.2 MHz | Narrow band CDMA signal with one code | +| 1860 - 1880 MHz,
1920 - 1940 MHz | -40 dBm | -104 dBm | ±3.2 MHz | Narrow band CDMA signal with one code | +| 1 - 1860 MHz,
1940 - 12750 MHz | -15 dBm | -104 dBm | — | CW carrier | + +NOTE: For *multi-band TAB connector*, 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 -108.6 dBm. + +**Table 7.5.5.3.1-7: Blocking requirements for Local Area BS +in operating bands defined in clause 4.5 a) for 1,28 Mcps TDD** + +| Centre 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 | $P_{\text{REFSENS}} + 6$ dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1880 - 1900 MHz,
1990 - 2010 MHz,
2025 - 2045 MHz | -30 dBm | $P_{\text{REFSENS}} + 6$ dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1920 - 1980 MHz | -30 dBm | $P_{\text{REFSENS}} + 6$ dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1880 MHz,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | $P_{\text{REFSENS}} + 6$ dB | — | CW carrier | + +NOTE: For *multi-band TAB connector*, 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.6 dBm for Local Area BS. + +**Table 7.5.5.3.1-8: Blocking requirements for Local Area BS +in operating bands defined in clause 4.5 b) for 1,28 Mcps TDD** + +| Centre frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|--------------------------|-----------------------------|--------------------------------------|------------------------------------| +| 1850 - 1990 MHz | -30 dBm | $P_{\text{REFSENS}} + 6$ dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1830 - 1850 MHz,
1990 - 2010 MHz | -30 dBm | $P_{\text{REFSENS}} + 6$ dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | $P_{\text{REFSENS}} + 6$ dB | — | CW carrier | + +NOTE: For *multi-band TAB connector*, 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.6 dBm for Local Area BS. + +**Table 7.5.5.3.1-9: Blocking requirements for Local Area BS +in operating bands defined in clause 4.5 c) for 1,28 Mcps TDD** + +| Centre frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|--------------------------|-----------------------------|--------------------------------------|------------------------------------| +| 1910 - 1930 MHz | -30 dBm | $P_{\text{REFSENS}} + 6$ dB | $\pm 3,2$ MHz | 1,28 Mcps TDD signal with one code | +| 1890 - 1910 MHz,
1930 - 1950 MHz | -30 dBm | $P_{\text{REFSENS}} + 6$ dB | $\pm 3,2$ MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | $P_{\text{REFSENS}} + 6$ dB | — | CW carrier | + +NOTE: For *multi-band TAB connector*, 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.6 dBm for Local Area BS. + +**Table 7.5.5.3.1-10: Blocking requirements for Local Area BS +in operating bands defined in clause 4.5 d) for 1,28 Mcps TDD** + +| 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 | $P_{\text{REFSENS}} + 6$ dB | $\pm 3.2$ MHz | 1,28 Mcps TDD signal with one code | +| 2500 - 2570 MHz,
2620 - 2690 MHz | -30 dBm | $P_{\text{REFSENS}} + 6$ dB | $\pm 3.2$ MHz | 1,28 Mcps TDD signal with one code | +| 1 - 2500 MHz,
2690 - 12750 MHz | -15 dBm | $P_{\text{REFSENS}} + 6$ dB | — | CW carrier | + +NOTE: For *multi-band TAB connector*, 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.6 dBm for Local Area BS. + +**Table 7.5.5.3.1-11: Blocking requirements for Local Area BS +in operating bands defined in clause 4.5 e) for 1,28 Mcps TDD** + +| Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|-----------------------------|--------------------------------------|------------------------------------| +| 2300 - 2400 MHz | -30 dBm | $P_{\text{REFSENS}} + 6$ dB | $\pm 3.2$ MHz | 1,28 Mcps TDD signal with one code | +| 2280 - 2300 MHz,
2400 - 2420 MHz | -30 dBm | $P_{\text{REFSENS}} + 6$ dB | $\pm 3.2$ MHz | 1,28 Mcps TDD signal with one code | +| 1 - 2280 MHz,
2420 - 12750 MHz | -15 dBm | $P_{\text{REFSENS}} + 6$ dB | — | CW carrier | + +NOTE: For *multi-band TAB connector*, 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.6 dBm for Local Area BS. + +**Table 7.5.5.3.1-12: Blocking requirements for Local Area BS +in operating bands defined in clause 4.5 f) for 1,28 Mcps TDD** + +| Centre 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 | $\pm 3.2$ MHz | Narrow band CDMA signal with one code | +| 1860 - 1880 MHz,
1920 - 1940 MHz | -30 dBm | -90 dBm | $\pm 3.2$ MHz | Narrow band CDMA signal with one code | +| 1 - 1860 MHz,
1940 - 12750 MHz | -15 dBm | -90 dBm | — | CW carrier | + +NOTE: For *multi-band TAB connector*, 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.6 dBm for Local Area BS. + +### 7.5.5.3.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 receiver units associated with *TAB connectors* with TDD operation 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 1 MHz 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.5.5.3.2-1: 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 | Notes | +|---------------------------------------------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|-------------------------------------------------------------------------------------| +| Macro GSM900 | 921 - 960 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| Macro DCS1800 | 1805 - 1880 MHz | +16 dBm | -104 dBm | – | CW carrier | For TAB connector operating UTRA TDD 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 | (NOTE 3) | +| 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 | | +| WA E-UTRA Band 54 | 1670 – 1675 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 | | + +| 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 | Notes | +|---------------------------------------------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|----------| +| 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 | (NOTE 3) | +| 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 | | +| LA E-UTRA Band 54 | 1670 – 1675 MHz | +16 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 30 dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [21]. + +NOTE 3: For *TAB connector operating* UTRA TDD in Band 5.2(f), the requirement is not covered by the present release of this specification. For the source of this requirement, refer to co-location requirements in TS 25.142 [19]. + +## 7.5.5.4 Single RAT E-UTRA operation + +### 7.5.5.4.1 General test requirement + +For each measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel, with a wanted and an interfering signal coupled to BS antenna input using the parameters in tables 7.5.5.4.1-1, 7.5.5.4.1-2, 7.5.5.4.1-3 and 7.5.5.4.1-4. The reference measurement channel for the wanted signal is specified in tables 7.2.5.3-1, 7.2.5.3-2 and 7.2.5.3-3 for each channel bandwidth and further specified in TS 36.141 [17], Annex A. + +The blocking requirement is always applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For a *TAB connector* operating in non-contiguous spectrum within any operating band, the blocking requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least as wide as twice the interfering signal minimum offset in table 7.6-2. The interfering signal offset is defined relative to the sub-block edges inside the *sub-block gap*. + +For a *multi-band TAB connector*, the requirement in the in-band blocking frequency ranges applies for each supported operating band. The requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least as wide as twice the interfering signal minimum offset in table 7.6-2. + +For a *multi-band TAB connector*, the requirement in the out-of-band blocking frequency ranges apply for each operating band, with the exception that the in-band blocking frequency ranges of all supported operating bands according to tables 7.5.5.4.1-1, 7.5.5.4.1-2 and 7.5.5.4.1-3 shall be excluded from the out-of-band blocking requirement. + +**Table 7.5.5.4.1-1: Blocking performance requirement for Wide Area BS** + +| Operating Band | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power (dBm) | Wanted Signal mean power (dBm) (Note 1) | Interfering signal centre frequency minimum frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of Interfering Signal | +|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1-7, 9-11, 13, 14, 18, 19, 21-23, 24, 27, 30, 33-45, 48, 50, 52, 54, 65, 66, 68, 70, 106 | (F UL_low -20) to (F UL_high +20) | -43 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +20) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 8, 26, 28 | (F UL_low -20) to (F UL_high +10) | -43 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +10) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 12 | (F UL_low -20) to (F UL_high +13) | -43 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +13) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 17 | (F UL_low -20) to (F UL_high +18) | -43 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +18) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 20, 71 | (F UL_low -11) to (F UL_high +20) | -43 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -11)
(F UL_high +20) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 25 | (F UL_low -20) to (F UL_high +15) | -43 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +15) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 31, 72, 73, 74 | (F UL_low -20) to (F UL_high +5) | -43 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +5) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 85 | (F UL_low -20) to (F UL_high +12) | -43 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +12) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | + +NOTE 1: PREFSENS depends on the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1.NOTE 2: For a *multi-band TAB connector*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, or in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to PREFSENS + 1.4 dB.NOTE 1: Table 7.5.5.4.1-1 assumes that two operating bands, where the *downlink operating band* see clause 4.5 of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.5.5.4.1-2: Blocking performance requirement for Local Area BS** + +| Operating Band | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power (dBm) | Wanted Signal mean power (dBm) (Note 1) | Interfering signal centre frequency minimum frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of Interfering Signal | +|-------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1-7, 9-11, 13-14, 18,19,21-23, 24, 27, 30, 33-45, 48, 50, 51, 52, 54, 65, 66, 68, 70, 106 | (F UL_low -20) to (F UL_high +20) | -35 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +20) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 8, 26, 28 | (F UL_low -20) to (F UL_high +10) | -35 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +10) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 12 | (F UL_low -20) to (F UL_high +13) | -35 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +13) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 17 | (F UL_low -20) to (F UL_high +18) | -35 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +18) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 20, 71 | (F UL_low -11) to (F UL_high +20) | -35 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -11)
(F UL_high +20) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 25 | (F UL_low -20) to (F UL_high +15) | -35 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +15) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 31, 72, 73, 74 | (F UL_low -20) to (F UL_high +5) | -35 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +5) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 85 | (F UL_low -20) to (F UL_high +12) | -35 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +12) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | + +NOTE 1: PREFSENS depends on the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1. + +NOTE 2: For a *multi-band TAB connector*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, or in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to PREFSENS + 1.4 dB. + +NOTE 2: Table 7.5.5.4.1-2 assumes that two operating bands, where the *downlink operating band* see clause 4.5 of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.5.5.4.1-3: Blocking performance requirement for Medium Range BS** + +| Operating Band | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power (dBm) | Wanted Signal mean power (dBm) (Note 1) | Interfering signal centre frequency minimum frequency offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of Interfering Signal | +|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1-7, 9-11, 13, 14, 18, 19, 21-23, 24, 27, 30, 33-45, 48, 50, 52, 54, 65, 66, 68, 70, 106 | (F UL_low -20) to (F UL_high +20) | -38 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +20) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 8, 26, 28 | (F UL_low -20) to (F UL_high +10) | -38 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +10) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 12 | (F UL_low -20) to (F UL_high +13) | -38 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +13) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 17 | (F UL_low -20) to (F UL_high +18) | -38 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +18) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 20, 71 | (F UL_low -11) to (F UL_high +20) | -38 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -11)
(F UL_high +20) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 25 | (F UL_low -20) to (F UL_high +15) | -38 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +15) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 31, 72, 73, 74 | (F UL_low -20) to (F UL_high +5) | -38 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +5) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | +| 85 | (F UL_low -20) to (F UL_high +12) | -38 | P REFSENS +6 dB (Note 2) | See table 7.5.5.4.1-4 | See table 7.5.5.4.1-4 | +| | 1 to (F UL_low -20)
(F UL_high +12) to 12750 | -15 | P REFSENS +6 dB | – | CW carrier | + +NOTE 1: PREFSENS depends on the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1.NOTE 2: For a *multi-band TAB connector*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, or in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to PREFSENS + 1.4 dB.NOTE 3: Table 7.5.5.4.1-3 assumes that two operating bands, where the *downlink operating band* see clause 4.5 of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.5.5.4.1-4: Interfering signals for blocking performance requirement** + +| E-UTRA channel BW of the lowest/highest carrier received (MHz) | Interfering signal centre frequency minimum offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1.4 | ±2.1 | 1.4 MHz E-UTRA signal | +| 3 | ±4.5 | 3 MHz E-UTRA signal | +| 5 | ±7.5 | 5 MHz E-UTRA signal | +| 10 | ±7.5 | 5 MHz E-UTRA signal | +| 15 | ±7.5 | 5 MHz E-UTRA signal | +| 20 | ±7.5 | 5 MHz E-UTRA signal | + +NOTE 4: 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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 7.5.5.4.2 Co-location with other base stations + +This additional blocking requirement may be applied for the protection of E-UTRA receiver units associated with the *TAB connectors* under test when GSM, CMDA, UTRA or E-UTRA BS operating in a different frequency band are co-located with an E-UTRA BS. The requirement is applicable to all channel bandwidths supported by the E-UTRA BS. + +The requirements in this clause assume a 30 dB coupling loss between interfering transmitter and E-UTRA BS receiver and are based on co-location with base stations of the same class. + +For each measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel, with a wanted and an interfering signal coupled to the *TAB connector* using the parameters in table 7.5.5.4.2-1 for AAS BS of Wide Area BS class, in table 7.5.5.4.2-2 for AAS BS of Local Area BS class and in table 7.5.5.4.2-3 for AAS BS of Medium Range BS class. The reference measurement channel for the wanted signal is specified in tables 7.2.5.3-1, 7.2.5.3-2 and 7.2.5.3-4 for each channel bandwidth and further specified in annex A of TS 36.141 [17]. + +**Table 7.5.5.4.2-1: Blocking performance requirement for E-UTRA when co-located with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| GSM900 | 921 - 960 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| DCS1800 | 1805 - 1880 (Note 4) | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| PCS1900 | 1930 - 1990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 (Note 4) | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 - 885 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 - 1495.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 - 768 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 17 | 734 - 746 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 18 or NR band n18 | 860 - 875 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 - 890 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR | 791 - 821 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| band n20 | | | | | | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 - 1510.9 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3590 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1525 - 1559 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 - 1995 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR band n26 | 859 - 894 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 27 | 852 - 869 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 28 or NR band n28 | 758 - 803 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717 - 728 | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6 \text{ dB}$ | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2350 - 2360 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6 \text{ dB}$ | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 (Note 5) | +16 | +8 | -6 | $P_{\text{REFSENS}} + 6 \text{ dB}$ | CW carrier | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900-1920 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010-2025 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850-1910 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930-1990 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910-1930 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570-2620 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880-1920 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300-2400 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 42 | 3400 - 3600 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 43 | 3600 - 3800 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 44 | 703 - 803 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|---------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| E-UTRA Band 48 or NR Band n48 | 3550 - 3700 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 51 or NR band n51 | 1427– 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 52 | 3300 - 3400 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 - 2200 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 66 or NR band n66 | 2110 - 2200 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}^*$ | CW carrier | +| E-UTRA Band 69 | 2570 - 2620 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 70 or NR band n70 | 1995 - 2020 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 71 or NR band n71 | 617 - 652 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 75 or NR band n75 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 76 or NR band n76 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n77 | 3300 - 4200 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n78 | 3300 - 3800 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n79 | 4400 - 5000 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 - 746 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 87 | 420 - 425 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 88 | 422 - 427 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n91 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n92 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n93 | 1427 - 1432 | N/A | N/A | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n94 | 1432 - 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n96 | 5925 - 7125 | N/A | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n100 | 919.4- 925 | +16 | N/A | N/A | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR band n101 | 1900 - 1910 | +16 | N/A | N/A | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 103 | 757 – 758 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR Band n104 | 6425 – 7125 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR Band n105 | 612 – 652 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| E-UTRA Band 106 or NR Band n106 | 935– 940 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | +| NR Band n109 | 1432 – 1517 | +16 | +8 | -6 | $P_{\text{REFSENS}} + x \text{ dB}$ | CW carrier | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the BS class and the channel bandwidth, see clause 7.2. + +"x" is equal to 6 in case of E-UTRA wanted signals. + +NOTE 2: Except for a *TAB connector* operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported *uplink operating band* or in the 10 MHz immediately outside any of the supported *uplink operating band*. + +For a *TAB connector* operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768-797MHz. + +NOTE 3: 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 or E-UTRA + +| Type of co-located BS | Centre Frequency of Interfering Signal (MHz) | Interfering Signal mean power for WA BS (dBm) | Interfering Signal mean power for MR BS (dBm) | Interfering Signal mean power for LA BS (dBm) | Wanted Signal mean power (dBm) (Note 1) | Type of Interfering Signal | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +|

TDD with E-UTRA FDD on adjacent frequencies for 30 dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [21].

NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805-1850 MHz.

NOTE 5: For a TAB connector operating in band 11 or 21, this requirement applies for interfering signal within the frequency range 1475.9-1495.9 MHz.

NOTE 6: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can receive without special co-location requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications.

| | | | | | | + +Table 7.5.5.4.2-2: Void + +Table 7.5.5.4.2-3: Void + +## 7.6 Receiver spurious emissions + +### 7.6.1 Definition and applicability + +The receiver spurious emissions power is the power of emissions generated or amplified in a receiver unit that appear at the *TAB connector*. The requirements apply to all AAS BS with separate RX and TX *TAB connectors*. + +NOTE: In this case for FDD AAS BS the test is performed when both TX and RX are on, with the TX *TAB connector* terminated. + +For a *TAB connector* supporting both RX and TX in TDD, the requirements apply during the *transmitter OFF period*. For a *TAB connector* supporting both RX and TX in FDD, the receiver spurious requirements are superseded by the TX spurious requirements in TS 37.105 [8], clause 6.6.6. + +For RX only *multi-band TAB connector(s)*, the RX spurious emissions requirements are subject to exclusion zones in each supported operating band. For *multi-band TAB connector(s)* that both transmit and receive in operating bands supporting TDD, RX spurious emissions requirements are applicable during the TX OFF period, and are subject to exclusion zones in each supported operating band. The unwanted emission level limit of a *TAB connector RX min cell group* is in general defined by the unwanted emission *basic limit* which is the same as the corresponding applicable *Non-AAS BS* per transmitter requirement specified in [3], [4], or [5], and its scaling by $N_{RXU, countedpercell}$ . The *basic limits* and corresponding scaling are defined in each relevant clause. The receiver spurious emission requirements are applied per the *TAB connector RX min cell groups* for all the configurations supported by the AAS BS. + +### 7.6.2 Minimum Requirement + +The minimum requirement for MSR operation is in TS 37.105 [8], clause 7.6.2. + +The minimum requirement for single RAT UTRA operation is defined in TS 37.105 [8], clause 7.6.3. + +The minimum requirement for single RAT E-UTRA operation is defined in TS 37.105 [8], clause 7.6.4. + +### 7.6.3 Test Purpose + +The test purpose is to verify the ability of the AAS BS to limit the interference caused by receiver spurious emissions to other systems. + +## 7.6.4 Method of test + +### 7.6.4.1 Initial conditions + +Test environment: + +- normal; see clause B.2 + +RF channels to be tested for single carrier: + +- M; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $M_{\text{RFBW}}$ in single-band operation, see clause 4.12.1, $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.12.1. + +### 7.6.4.2 Procedure + +#### 7.6.4.2.1 General procedure + +The general procedure steps apply to the procedures for all the RATs. + +The minimum requirement is applied to all *TAB connectors* described in clause 7.6.1, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.2.4. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect *TAB connector* to measurement equipment as shown in annex D.2.4. All *TAB connectors* not under test shall be terminated. + +For TDD connectors capable of transmit and receive ensure the transmitter is OFF. + +#### 7.6.4.2.2 MSR operation + +- 1) Set the measurement equipment parameters as specified in table 7.6.5.2.1-1. +- 2) Set the transmitter unit associated with the *TAB connector* under test to transmit with the carrier set-up and power allocation according to the applicable test configuration(s), see clause 5. +- 3) Measure the spurious emissions over each frequency range described in clause 7.6.5.2.1. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.6.4.2.3 Single RAT UTRA FDD operation + +- 1) For *TAB connector(s)* capable of single carrier operation only, set each *TAB connector* declared in the same RAT and operating band to transmit a signal according to TM1, (clause 4.12.2), at the manufacturer's declared rated output power, $P_{\text{Rated,e,TABC}}$ . + +For *TAB connector(s)* declared to be capable of multi-carrier operation, set each *TAB connector* declared in the same RAT and operating band to transmit a signal according to TM1 on all carriers configured, using the applicable test configuration and corresponding power setting for receiver tests, as specified in clause 4.11. + +- 2) Set measurement equipment parameters as specified in table 7.6.4.2.3-1. +- 3) Measure the spurious emissions over each frequency range described in clause 7.6.5.2.2 + +**Table 7.6.4.2.3-1: Measurement equipment parameters** + +| | | +|------------------------|-------------------------------------------------------------| +| Measurement Band width | 3.84 MHz (Root raised cosine, 0.22) / 100 kHz/ 1 MHz (note) | +| Sweep frequency range | 30 MHz to 12.75GHz | +| Detection | True RMS | +| NOTE: | As defined in clause 7.6.2. | + +- The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.3-1. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.6.4.2.4 Single RAT UTRA TDD 1,28Mcps option operation + +- 1) For *TAB connector(s)* capable of single carrier operation only, set each *TAB connector* declared in the same RAT and operating band to transmit a signal according to table 7.6.4.2.4-1, at the manufacturer's declared rated output power, $P_{\text{Rated,c,TABC}}$ . + +For *TAB connector(s)* declared to be capable of multi-carrier operation, set each *TAB connector* declared in the same RAT and operating band to transmit a signal according to table 7.6.4.2.4-1 on all carriers configured, using the applicable test configuration and corresponding power setting for receiver tests, as specified in clause 4.11. + +**Table 7.6.4.2.4-1: 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 | +| 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) | + +- 2) Measure the power of the spurious emissions by applying the measuring equipment with the settings as specified in table 7.6.4.2.4-2. 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 centre frequency of the filters shall be stepped in contiguous steps over the frequency bands as specified in table 7.6.4.2.4-2. The time duration of each step shall be sufficiently long to capture one even (transmit) time slot. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +**Table 7.6.4.2.4-2: Measurement equipment settings** + +| Stepped frequency range | Measurement bandwidth | Step width | Note | Detection mode | | +|-------------------------|-----------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------|--| +| 30 MHz - 1 GHz | 100 kHz | 100 kHz | | true RMS | | +| 1 GHz - 1,880 GHz | 1 MHz | 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 | | | +| 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,620 GHz | 1,28 MHz | 200 kHz | | | | +| 2,620 GHz - 12,75 GHz | 1 MHz | 1 MHz | | | | + +- The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.3-1. + +#### 7.6.4.2.5 Single RAT E-UTRA operation + +- 1) Set the measurement equipment parameters as specified in table 7.6.5.2.5-1. +- 2) Set the *TAB connector(s)* to transmit with the carrier set-up and power allocation according to the applicable test configuration(s), see clause 5. +- 3) Measure the spurious emissions over each frequency range described in clause 7.6.5.2.4. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 4) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 7.6.5 Test Requirements + +#### 7.6.5.1 General + +Conformance may be shown to either the measure and sum test requirement or the per *TAB connector* test requirement. + +- 1) The spurious emission test requirements for an AAS BS when using the measure and sum alternative are that for each *TAB connector RX cell group* and each applicable *basic limit* as specified in clause 7.6.5.2, the power summation of emissions at the *TAB connectors* of the *TAB connector RX cell group* shall not exceed a limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{\text{RXU, countedpercell}})$ , unless stated differently in regional regulation. +- 2) The spurious emission test requirements for an AAS BS when using the per *TAB connector* alternative are that for each *TAB connector RX cell group* and each applicable *basic limit* as specified in clause 7.6.5.2, the emissions at each of the *TAB connectors* of the *TAB connector RX cell group* shall not exceed a limit specified as the *basic limit* + X - $10\log(n)$ where n is the number of *TAB connectors* in the *TAB connector RX cell group* and $X = 10\log_{10}(N_{\text{RXU, countedpercell}})$ , unless stated differently in regional regulation. + +## 7.6.5.2 Basic limits + +### 7.6.5.2.1 MSR operation + +The basic limit for MSR operation is given below: + +**Table 7.6.5.2.1-1: General spurious emission test requirement basic limit** + +| Frequency range | Basic limit | Measurement Bandwidth | Notes | +|--------------------------------------------------------------------------------------------------|-------------|-----------------------|-------------------------------------------| +| 30 MHz - 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz - 12.75 GHz | -47 dBm | 1 MHz | | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -47 dBm | 1 MHz | Applies only for Bands 22, 42, 43 and 48. | + +NOTE: The frequency range from $F_{BW\_RF\_DL\_low} - \Delta f_{OBUE}$ to $F_{BW\_RF\_DL\_high} + \Delta f_{OBUE}$ may be excluded from the requirement. 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. + +In addition to the *basic limits* in table 7.6.5.2.1-1, Additional spurious emissions requirements in clause 6.6.6.5.2.5 form *basic limits* for additional receiver spurious emission requirements. + +In case of FDD BS (for BC1 and BC2), the levels specified for Protection of the BS receivers of own or different BS in clause 6.6.6.5.2.4, form basic levels for additional receiver spurious emission requirements. + +In addition, the requirements for co-location with other base stations specified in clause 6.6.6.5.2.6, may also form basic levels for co-location spurious emission requirements. + +### 7.6.5.2.2 Single RAT UTRA FDD operation + +The basic limit for UTRA FDD operation is given below: + +For *multi-band TAB connectors*, the exclusions and conditions in the Notes column of table 7.6.5.2.1-1 apply for each supported operating band. 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.6.5.2.2-1: Spurious emission test requirement basic limit** + +| Band | Basic limit | Measurement Bandwidth | Notes | +|--------------------------------------------------------------------------------------------------|-------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 30 MHz - 1 GHz | -57 dBm | 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 transmitted used by the BS. | +| 1 GHz - 12.75 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 12.5 MHz below the first carrier frequency and 12.5 MHz above the last carrier frequency transmitted used by the BS. | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -47 dBm | 1 MHz | NOTE: Applies only for Band XXII | + +In addition to the requirements in table 7.6.5.2.2-1, the power of any spurious emission shall not exceed the levels specified for Protection of the BS receiver of own or different BS in clause 6.6.6.5.2.4 and for Co-existence with other systems in the same geographical area in clause 6.6.6.5.2.5. In addition, the co-existence requirements for co-located base stations specified in clause 6.6.5.2.6 may also be applied. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.6.5.2.3 Single RAT UTRA TDD 1,28Mcps option operation + +The basic limits for UTRA TDD operation are given below: + +**Table 7.6.5.2.3-1: General receiver spurious emission test requirement basic limit** + +| Band | Basic limit | Measurement Bandwidth | Note | +|-------------------|-------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| 30 MHz - 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. | + +In addition to the requirements in table 7.6.5.2.3-1, the power of any spurious emission shall not exceed the levels specified for Co-existence with other systems in the same geographical area in clause 6.6.6.5.2.4. In addition, the co-existence requirements for co-located base stations specified in clause 6.6.6.5.2.5 and 6.6.6.5.2.6 may also be applied. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.6.5.2.4 Single RAT E-UTRA operation + +The basic limit for E-UTRA operation is given below: + +**Table 7.6.5.2.4-1: General spurious emission test requirement basic limit** + +| Frequency range | Basic limit | Measurement Bandwidth | Note | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|-------------------------------------------| +| 30 MHz - 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz - 12.75 GHz | -47 dBm | 1 MHz | | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -47 dBm | 1 MHz | Applies only for Bands 22, 42, 43 and 48. | +| NOTE: The frequency range from $F_{BW\_RF\_DL\_low} - \Delta f_{OBUE}$ to $F_{BW\_RF\_DL\_high} + \Delta f_{OBUE}$ may be excluded from the requirement. For a multi-band TAB connector , the exclusion applies for all supported operating bands. | | | | + +In addition to the requirements in table 7.6.5.2.4-1, the power of any spurious emission shall not exceed the additional spurious emissions requirements in clause 6.6.6.5.2.5 and in case of a *TAB connector* operating FDD (for BC1 and BC2) emission shall not exceed the levels specified for protection of the BS receivers of own or different BS in clause 6.6.6.5.2.4. In addition, the requirements for co-location with other Base Stations specified in clause 6.6.6.5.2.6 may also be applied. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 7.7 Receiver intermodulation + +### 7.7.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 receiver unit to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. The requirement applies per *TAB connector*. + +### 7.7.2 Minimum requirement + +The minimum requirement for MSR operation is defined in TS 37.105 [8], clause 7.7.2. + +The single RAT UTRA FDD AAS BS of Wide Area BS class shall fulfil minimum requirements for receiver intermodulation specified in TS 25.104 [9], clause 7.6.1. + +The single RAT UTRA FDD AAS BS of Medium Range BS class shall fulfil minimum requirements for receiver intermodulation specified in TS 25.104 [9], clause 7.6.1. + +The single RAT UTRA FDD AAS BS of Local Area BS class shall fulfil minimum requirements for receiver intermodulation specified in TS 25.104 [9], clause 7.6.1. + +The single RAT UTRA TDD AAS BS of Wide Area BS class shall fulfil minimum requirements for receiver intermodulation specified in TS 25.105 [10], clause 7.6.1.2. + +The single RAT UTRA TDD AAS BS of Local Area BS class shall fulfil minimum requirements for receiver intermodulation specified in TS 25.105 [10], clause 7.6.1.2. + +The single RAT E-UTRA AAS BS of Wide Area BS class shall fulfil minimum requirements for receiver intermodulation specified in TS 36.104 [11], clause 7.8. + +The single RAT E-UTRA AAS BS of Medium Range BS class shall fulfil minimum requirements for receiver intermodulation specified in TS 36.104 [11], clause 7.8. + +The single RAT E-UTRA AAS BS of Local Area BS class shall fulfil minimum requirements for receiver intermodulation specified in TS 36.104 [11], clause 7.8. + +### 7.7.3 Test purpose + +The test purpose is to verify the ability of the receiver unit associated with the *TAB connector* under test 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.7.4 Method of test + +#### 7.7.4.1 Initial conditions + +Test environment: + +- Normal; see clause B.2. + +RF channels to be tested for single carrier (SC): + +- M; see clause 4.12.1 + +*Base Station RF Bandwidth* positions to be tested: + +- For *single-band TAB connector(s)*: $M_{RFBW}$ if ATC4 is applicable; $B_{RFBW}$ and $T_{RFBW}$ for other ATC, see clause 4.12.1. For *multi-band TAB connector(s)*: $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ , see clause 4.12.1. + +## 7.7.4.2 Procedure + +### 7.7.4.2.1 General procedure + +The general procedure steps apply to the procedures for all the RATs. + +The minimum requirement is applied to all *TAB connectors*, the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect *TAB connector* to measurement equipment as shown in annex D.2.6. All *TAB connectors* not under test shall be terminated. +- 2) Generate the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the *TAB connector* under test as follows: + - For E-UTRA see clause A.1 in TS 36.141 [17]. + - For UTRA FDD see clause A.2 in TS 25.141 [18]. + - For UTRA TDD see clause A.2.1 in TS 25.142 [20]. + - For NR, see clause [4.11] +- 3) Set the transmitter unit associated with the *TAB connector* under test to transmit with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +### 7.7.4.2.2 MSR operation + +#### 7.7.4.4.2.1 Procedure for general and narrowband intermodulation + +- 1) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified in table 7.7.5.1.1-1 and Table 7.7.5.1.1-2 for general intermodulation requirement, and Table 7.7.5.2.1-1 and Table 7.7.5.2.1-2 for narrowband intermodulation requirement. +- 2) Measure the performance of the wanted signal at the receiver unit associated with the *TAB connector* under test, as defined in clause 7.7.5.1.1 and 7.7.5.1.2, for the relevant carriers specified by the test configuration in clause 5. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 3) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 7.7.4.2.3 Single RAT UTRA FDD operation + +- 1) Generate the wanted signal (reference signal) and adjust ATT1 to set the signal level to the *TAB connector* under test to the level specified in table 7.7.5.2-1. For a *TAB connector* supporting multi-carrier operation, generate the wanted signal according to the applicable test configuration (see clause 4.11) using applicable reference measurement channel to the *TAB connector* under test. Power settings are specified in table 7.7.5.2-1. +- 2) Adjust the signal generators to the type of interfering signals and the frequency offsets as specified in tables 7.7.5.2-1 and 7.7.5.2-2. Note that the GMSK modulated interfering signal shall have an ACLR of at least 72 dB in order to eliminate the impact of interfering signal adjacent channel leakage power on the intermodulation characteristics measurement. +- 3) Adjust the ATT2 and ATT3 to obtain the specified level of interfering signal at the *TAB connector*. +- 4) Measure the BER of the wanted signal. For a *TAB connector* supporting multi-carrier operation the BER shall be measured for all relevant carriers specified by the test configuration. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.7.4.2.4 Single RAT UTRA TDD 1,28Mcps option operation + +- 1) Start transmission from the BS tester to the *TAB connector* using the UL reference measurement channel (12,2 kbps) defined in clause A.2.1 of TS 25.142 [20]. For a *TAB connector* supporting multi-carrier operation, generate the wanted signal using the applicable test configuration specified in clause 4.11, and the UL reference measurement channel in clause A.2.1 of TS 25.142 [20] shall be used on all carriers for the *TAB connector* under test. The level of the UE simulator signal measured at the *TAB connector* shall be set to 6 dB above the reference sensitivity level specified in clause 7.2.2. +- 2) Set the first signal generator to produce a CW signal with a level measured at the *TAB connector* as specified in table 7.7.5.3-1. +- 3) 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 *TAB connector* shall be set as specified in table 7.7.5.3-1. +- 4) Measure the BER of the wanted signal. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.7.4.2.5 Single RAT E-UTRA operation + +- 1) Generate the wanted signal using the applicable test configuration specified in clause 5 and adjust the signal level to the *TAB connector* under test to the level specified in table 7.7.5.4-1. +- 2) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified in table 7.7.5.4-2 for intermodulation requirement and Table 7.7.5.4-3, Table 7.7.5.4-4 and Table 7.7.5.4-5 for narrowband intermodulation requirement. +- 3) Adjust the signal generators to obtain the specified level of interfering signal at the *TAB connector*. +- 4) Measure the throughput, for multi-carrier and/or CA operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clause 5. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 5) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 7.7.5 Test requirements + +#### 7.7.5.1 MSR operation + +##### 7.7.5.1.1 General intermodulation test requirement + +Interfering signals shall be a CW signal and an E-UTRA or UTRA signal, as specified in annex A of TS 37.141 [16]. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For *multi-band TAB connector*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least twice as wide as the UTRA/E-UTRA interfering signal centre frequency offset from the RF bandwidth edge. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted signal at the assigned channel frequency and two interfering signals coupled to the *TAB connector*, using the parameters in table 7.7.5.1.1-1 and 7.7.5.1.1-2, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.3. + +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.1. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [36], clause 7.2. + +**Table 7.7.5.1.1-1: General intermodulation requirement** + +| Base Station Type | Mean power of interfering signals (dBm) | Wanted Signal mean power (dBm) | Type of interfering signal | +|-------------------|-----------------------------------------|----------------------------------------|----------------------------| +| Wide Area BS | -48 +y (Note 6) | $P_{\text{REFSENS}} +x$ dB (Note 2, 5) | See Table 7.7.5.1.1-2 | +| Medium Range BS | -44 +y (Note 6) | $P_{\text{REFSENS}} +x$ dB (Note 3, 5) | | +| Local Area BS | -38 +y (Note 6) | $P_{\text{REFSENS}} +x$ dB (Note 4, 5) | | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth, see clause 7.2. + +NOTE 2: For WA BS supporting UTRA, "x" is equal to 6 + +NOTE 3: For MR BS supporting UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of NR or E-UTRA wanted signals. + +NOTE 4: For LA BS supporting UTRA, "x" is equal to 12 in case of NR or E-UTRA wanted signals, 6 in case of UTRA wanted signals. + +NOTE 5: For a BS not supporting UTRA, x is equal to 6 for all BS classes if NR is supported, otherwise x is equal to 6 for WA BS or 9 for MR or 12 for LA BS if NR is not supported. + +NOTE 6: For a BS supporting NR and not supporting UTRA; "y" is equal to -4 for the WA BS class, -3 for the MR BS class and -6 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. + +**Table 7.7.5.1.1-2: Interfering signals for intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge | Interfering signal centre frequency offset from the Base Station RF Bandwidth edge [MHz] | Type of interfering signal | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------------------| +| E-UTRA 1.4 MHz | ±2.0 (BC1 and BC3) / ±2.1 (BC2) | CW | +| | ±4.9 | 1.4MHz E-UTRA signal | +| E-UTRA 3 MHz | ±4.4 (BC1 and BC3) / ±4.5 (BC2) | CW | +| | ±10.5 | 3MHz E-UTRA signal | +| UTRA FDD and E-UTRA 5 MHz | ±7.5 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| E-UTRA 10 MHz | ±7.375 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| E-UTRA 15 MHz | ±7.25 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| E-UTRA 20 MHz | ±7.125 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| 1.28 Mcps UTRA TDD | ±2.3 (BC3) | CW | +| | ±5.6 (BC3) | 1.28Mcps UTRA TDD signal | +| NR 5 MHz | ±7.5 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 10 MHz | ±7.465 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 15 MHz | ±7.43 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 20 MHz | ±7.395 | CW | +| | ±17.5 | 5MHz E-UTRA signal | +| NR 25 MHz | ±7.465 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 30 MHz | ±7.43 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 35 MHz | ±7.44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 40 MHz | ±7.45 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 45 MHz | ±7.37 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 50 MHz | ±7.35 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 60 MHz | ±7.49 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 70 MHz | ±7.42 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 80 MHz | ±7.44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 90 MHz | ±7.46 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 100 MHz | ±7.48 | CW | +| | ±25 | 20MHz E-UTRA signal | + +### 7.7.5.1.2 General narrowband intermodulation test requirement + +Interfering signals shall be a CW signal and an E-UTRA 1RB signal, as specified in annex A of TS 37.141 [16]. + +The requirement is applicable outside the *Base Station RF Bandwidth* or maximum *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF bandwidth edges* or maximum *Radio Bandwidth edges*. + +For a *TAB connector* operating in non-contiguous spectrum within each supported operating band, the requirement applies in addition inside any *sub-block gap* in case the *sub-block gap* is at least as wide as the channel bandwidth of the E-UTRA interfering signal in table 7.7.5.1.2-2. The interfering signal offset is defined relative to the sub-block edges inside the gap. + +For a *multi-band TAB connector*, the requirement applies in addition inside any *Inter RF Bandwidth gap* in case the gap size is at least as wide as the E-UTRA interfering signal in table 7.7.5.1.2-2. The interfering signal offset is defined relative to the RF bandwidth edges inside the *Inter RF Bandwidth gap*. + +For the wanted signal at the assigned channel frequency and two interfering signals coupled to the Base Station antenna input, using the parameters in table 7.7.5.2-1 and 7.7.5.2-2, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.3. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in TS 38.104 [36], clause 7.2.5.4. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.1. +- For any measured UTRA TDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.2. + +**Table 7.7.5.1.2-1: General narrowband intermodulation requirement** + +| Base Station Type | Mean power of interfering signals (dBm) | Wanted Signal mean power (dBm) | Type of interfering signal | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------|----------------------------| +| Wide Area BS | -52 | $P_{\text{REFSENS}} + x$ dB (Note) | See Table 7.7.5.1.2-2 | +| Medium Range BS | -47 | | | +| Local Area BS | -44 | | | +| NOTE: $P_{\text{REFSENS}}$ depends on the RAT, the BS class and on the channel bandwidth, see clause 7.2 in TS 37.104 [12].
"x" is equal to 6 in case of NR, E-UTRA or UTRA wanted signals. | | | | + +**Table 7.7.5.1.2-2: Interfering signals for narrowband intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge or sub-block edge | CW or 1RB interfering signal centre frequency offset from the Base Station RF Bandwidth edge or sub-block edge inside a gap [kHz] | Type of interfering signal | +|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| E-UTRA 1.4 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±970 (BC1 and BC3) / ±790 (BC2) | 1.4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA or E-UTRA 3 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±960 (BC1 and BC3) / ±780 (BC2) | 3.0 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 5 MHz | ±360 | CW | +| | ±1060 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 10 MHz
(NOTE 2) | ±325 | CW | +| | ±1240 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 15 MHz
(NOTE 2) | ±380 | CW | +| | ±1600 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 20 MHz
(NOTE 2) | ±345 | CW | +| | ±1780 | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| UTRA FDD | ±345 (BC1 and BC2) | CW | +| | ±1780 (BC1 and BC2) | 5MHz E-UTRA signal, 1 RB (NOTE 1) | +| 1.28Mcps UTRA TDD | ±190 (BC3) | CW | +| | ±970 (BC3) | 1.4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| NR 5 MHz | ±360 | CW | +| | ±1420 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 10 MHz | ±370 | CW | +| | ±1960 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 15 MHz
(NOTE 2) | ±380 | CW | +| | ±1960 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 20 MHz
(NOTE 2) | ±390 | CW | +| | ±2320 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 25 MHz
(NOTE 2) | ±325 | CW | +| | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------| +| NR 30 MHz | ±335 | CW | +| (NOTE 2) | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 35 MHz | ±345 | CW | +| (NOTE 2) | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 40 MHz | ±355 | CW | +| (NOTE 2) | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 45 MHz | ±365 | CW | +| (NOTE 2) | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 50 MHz | ±375 | CW | +| (NOTE 2) | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 60 MHz | ±395 | CW | +| (NOTE 2) | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 70 MHz | ±415 | CW | +| (NOTE 2) | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 80 MHz | ±435 | CW | +| (NOTE 2) | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 90 MHz | ±365 | CW | +| (NOTE 2) | ±2530 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 100 MHz | ±385 | CW | +| (NOTE 2) | ±2530 | E-UTRA signal, 1 RB (NOTE 1) | +| NOTE 1: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the Base Station RF Bandwidth edge. | | | +| NOTE 2: This requirement shall apply only for an E-UTRA FRC A1-3 or NR G-FRC mapped to the frequency range at the channel edge adjacent to the interfering signals. | | | + +### 7.7.5.2 Single RAT UTRA FDD operation + +For each measured carrier, the BER shall not exceed 0,001 for the parameters specified in tables 7.7.5.2-1 and 7.7.5.2-2. + +The intermodulation performance shall be met when the following signals are applied to the receiver. + +For a *TAB connector* operating in non-contiguous spectrum within any operating band, the narrowband intermodulation requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 6.8MHz. The CW interfering signal offset is defined relative to the lower/upper sub-block edge inside the *sub-block gap* and is equal to -1 MHz/+1 MHz, respectively. The GMSK modulated interfering signal offset is defined relative to the lower/upper sub-block edge inside the *sub-block gap* and is equal to -3.4 MHz/+3.4 MHz, respectively. The requirement applies separately for both sub-blocks. + +For a *multi-band TAB connector*, the narrowband intermodulation requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least 6.8MHz. The CW interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -1 MHz/+1 MHz, respectively. The GMSK modulated interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -3.4 MHz/+3.4 MHz, respectively. + +**Table 7.7.5.2-1: Intermodulation performance requirement** + +| Operating Band | Type of Signal | Offset | Signal mean power | | | +|----------------|---------------------|---------|-------------------|-----------------|------------| +| | | | Wide Area BS | Medium Range BS | Local Area | +| All bands | Wanted signal | - | -115 dBm | -105 dBm | -101 dBm | +| | CW signal | ±10 MHz | -48 dBm | -44 dBm | -38 dBm | +| | WCDMA signal (Note) | ±20 MHz | -48 dBm | -44 dBm | -38 dBm | + +NOTE: The characteristics of the W-CDMA interfering signal are specified in annex I of TS 25.141 [18] + +**Table 7.7.5.2-2: Narrowband intermodulation performance requirement** + +| Operating band | Type of Signal | Offset | Signal mean power | | | +|----------------------------------------------------|-----------------------|----------|-------------------|-----------------|------------| +| | | | Wide Area BS | Medium Range BS | Local Area | +| II, III, IV, V, VIII, X, XII, XIII, XIV, XXV, XXVI | Wanted signal | - | -115 dBm | -105 dBm | -101 dBm | +| | CW signal | ±3.5 MHz | - 47 dBm | - 43 dBm | -37 dBm | +| | GMSK modulated (Note) | ±5.9 MHz | - 47 dBm | - 43 dBm | -37 dBm | + +NOTE: GMSK as defined in TS 45.004 [22]. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.7.5.3 Single RAT UTRA TDD 1,28Mcps option operation + +The BER measured shall not exceed 0,001. + +The static reference performance as specified in clause 7.2.5.2 should be met when the following signals are coupled to the *TAB connector*. + +- 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.7.5.3-1. + +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 a *multi-band TAB connector*, 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 *Base Station RF bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -2.4 MHz/+2.4 MHz, respectively. The modulated interfering signal offset is defined relative to lower/upper *Base Station RF bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -5.6MHz/+5.6MHz, respectively. + +**Table 7.7.5.3-1: 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 | | | +| - 48 dBm | - 38 dBm | ±3,2 MHz | CW signal | +| - 48 dBm | - 38 dBm | ±6,4 MHz | 1,28 Mcps TDD signal with one code | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 7.7.5.4 Single RAT E-UTRA operation + +For each measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel, with a wanted signal at the assigned channel frequency and two interfering signals with the conditions specified in tables 7.7.5.4-1 and 7.7.5.4-2 for intermodulation performance and in tables 7.7.5.4-3, 7.7.5.4-4 and 7.7.5.4-5 for narrowband intermodulation performance. The reference measurement channel for the wanted signal is specified in tables 7.2.5.3-1, 7.2.5.3-2 and 7.2.5.3-3 for each channel bandwidth and further specified in annex A of TS 36.141 [17]. + +The receiver intermodulation 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 a *TAB connector* operating in non-contiguous spectrum within any operating band, the narrowband intermodulation requirement applies in addition inside any *sub-block gap* in case the *sub-block gap* is at least as wide as the channel bandwidth of the E-UTRA interfering signal in table 7.7.5.4-3. The interfering signal offset is defined relative to the sub-block edges inside the *sub-block gap*. The requirement applies separately for both sub-blocks. + +For a *multi-band TAB connector*, the intermodulation requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least twice as wide as the E-UTRA interfering signal centre frequency offset from the *Base Station RF bandwidth edge*. + +For a *multi-band TAB connector*, the narrowband intermodulation requirement applies in addition inside any *Inter RF Bandwidth gap* in case the gap size is at least as wide as the E-UTRA interfering signal in tables 7.7.5.4-3, 7.7.5.4-4 and 7.7.5.4-5. The interfering signal offset is defined relative to the *Base Station RF bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 7.7.5.4-1: Intermodulation performance requirement** + +| BS type | Wanted signal mean power (dBm) (Note) | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------|----------------------------| +| Wide Area BS | $P_{\text{REFSENS}} + 6$ dB | -52 | See Table 7.7.5.4-2 | +| Medium Range BS | $P_{\text{REFSENS}} + 6$ dB | -47 | | +| Local Area BS | $P_{\text{REFSENS}} + 6$ dB | -44 | | +| NOTE: $P_{\text{REFSENS}}$ depends on the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1. For E-UTRA channel bandwidths 10, 15 and 20 MHz this requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals. | | | | + +**Table 7.7.5.4-2: Interfering signal for Intermodulation performance requirement** + +| E-UTRA channel bandwidth of the lowest (highest) carrier received (MHz) | Interfering signal centre frequency offset from the lower (upper) edge (MHz) | Type of interfering signal | +|-------------------------------------------------------------------------|------------------------------------------------------------------------------|----------------------------| +| 1.4 | $\pm 2.1$ | CW | +| | $\pm 4.9$ | 1.4 MHz E-UTRA signal | +| 3 | $\pm 4.5$ | CW | +| | $\pm 10.5$ | 3 MHz E-UTRA signal | +| 5 | $\pm 7.5$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | +| 10 | $\pm 7.375$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | +| 15 | $\pm 7.25$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | +| 20 | $\pm 7.125$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | + +**Table 7.7.5.4-3: Narrowband intermodulation performance requirement for Wide Area BS** + +| E-UTRA channel bandwidth of the lowest (highest) carrier received (MHz) | Wanted signal mean power (dBm) (Note 1) | Interfering signal mean power (dBm) | Interfering RB centre frequency offset from the lower (upper) edge or sub-block edge inside a sub-block gap (kHz) | Type of interfering signal | +|-------------------------------------------------------------------------|-----------------------------------------|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| 1.4 | $P_{\text{REFSENS}} + 6$ dB | -52 | $\pm 270$ | CW | +| | | -52 | $\pm 790$ | 1.4 MHz E-UTRA signal, 1 RB (Note 2) | +| 3 | $P_{\text{REFSENS}} + 6$ | -52 | $\pm 270$ | CW | +| | | -52 | $\pm 780$ | 3.0 MHz E-UTRA signal, 1 RB (Note 2) | +| 5 | $P_{\text{REFSENS}} + 6$ dB | -52 | $\pm 360$ | CW | +| | | -52 | $\pm 1060$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | +| 10 | $P_{\text{REFSENS}} + 6$ dB
(Note 3) | -52 | $\pm 325$ | CW | +| | | -52 | $\pm 1240$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | +| 15 | $P_{\text{REFSENS}} + 6$ dB
(Note 3) | -52 | $\pm 380$ | CW | +| | | -52 | $\pm 1600$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | +| 20 | $P_{\text{REFSENS}} + 6$ dB
(Note 3) | -52 | $\pm 345$ | CW | +| | | -52 | $\pm 1780$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | + +NOTE 1: $P_{\text{REFSENS}}$ is related to the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1. + +NOTE 2: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the lower (upper) edge. + +NOTE 3: This requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals + +**Table 7.7.5.4-4: Narrowband intermodulation performance requirement for Local Area BS** + +| E-UTRA channel bandwidth of the lowest (highest) carrier received (MHz) | Wanted signal mean power (dBm) (Note 1) | Interfering signal mean power (dBm) | Interfering RB centre frequency offset from the lower (upper) edge or sub-block edge inside a sub-block (kHz) | Type of interfering signal | +|-------------------------------------------------------------------------|-----------------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------|--------------------------------------| +| 1.4 | $P_{\text{REFSENS}} + 6$ dB | -44 | $\pm 270$ | CW | +| | | -44 | $\pm 790$ | 1.4 MHz E-UTRA signal, 1 RB (Note 2) | +| 3 | $P_{\text{REFSENS}} + 6$ | -44 | $\pm 275$ | CW | +| | | -44 | $\pm 790$ | 3.0 MHz E-UTRA signal, 1 RB (Note 2) | +| 5 | $P_{\text{REFSENS}} + 6$ dB | -44 | $\pm 360$ | CW | +| | | -44 | $\pm 1060$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | +| 10 | $P_{\text{REFSENS}} + 6$ dB
(Note 3) | -44 | $\pm 415$ | CW | +| | | -44 | $\pm 1420$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | +| 15 | $P_{\text{REFSENS}} + 6$ dB
(Note 3) | -44 | $\pm 380$ | CW | +| | | -44 | $\pm 1600$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | +| 20 | $P_{\text{REFSENS}} + 6$ dB
(Note 3) | -44 | $\pm 345$ | CW | +| | | -44 | $\pm 1780$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | + +NOTE 1: $P_{\text{REFSENS}}$ is related to the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1. + +NOTE 2: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the lower (upper) edge. + +NOTE 3: This requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals. + +**Table 7.7.5.4-5: Narrowband intermodulation performance requirement for Medium Range BS** + +| E-UTRA channel bandwidth of the lowest (highest) carrier received (MHz) | Wanted signal mean power (dBm) (Note 1) | Interfering signal mean power (dBm) | Interfering RB centre frequency offset to the lower (higher) edge or sub-block edge inside a sub-block gap (kHz) | Type of interfering signal | +|-------------------------------------------------------------------------|-----------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| 1.4 | $P_{\text{REFSENS}} + 6$ dB | -47 | $\pm 270$ | CW | +| | | -47 | $\pm 790$ | 1.4 MHz E-UTRA signal, 1 RB (Note 2) | +| 3 | $P_{\text{REFSENS}} + 6$ | -47 | $\pm 270$ | CW | +| | | -47 | $\pm 780$ | 3.0 MHz E-UTRA signal, 1 RB (Note 2) | +| 5 | $P_{\text{REFSENS}} + 6$ dB | -47 | $\pm 360$ | CW | +| | | -47 | $\pm 1060$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | +| 10 | $P_{\text{REFSENS}} + 6$ dB (Note 3) | -47 | $\pm 325$ | CW | +| | | -47 | $\pm 1240$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | +| 15 | $P_{\text{REFSENS}} + 6$ dB (Note 3) | -47 | $\pm 380$ | CW | +| | | -47 | $\pm 1600$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | +| 20 | $P_{\text{REFSENS}} + 6$ dB (Note 3) | -47 | $\pm 345$ | CW | +| | | -47 | $\pm 1780$ | 5 MHz E-UTRA signal, 1 RB (Note 2) | + +NOTE 1: $P_{\text{REFSENS}}$ is related to the channel bandwidth as specified in TS 36.104 [11], clause 7.2.1. +NOTE 2: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the lower (higher) edge. +NOTE 3: This requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 7.8 In-channel selectivity + +### 7.8.1 Definition and applicability + +In-channel selectivity (ICS) is a measure of the receiver unit ability to receive a wanted signal at its assigned resource block locations in the presence of an interfering signal received at a larger power spectral density. In this condition a throughput requirement shall be met for a specified reference measurement channel. The requirement applies per *TAB connector*. + +### 7.8.2 Minimum requirement + +The minimum requirement for E-UTRA operation is defined in TS 37.105 [8], clause 7.8.4. + +The minimum requirement for MSR operation is defined in TS 37.105 [8], clause 7.8.2. + +### 7.8.3 Test purpose + +The purpose of this test is to verify the ability of the receiver unit associated with the *TAB connector* under test to suppress the IQ leakage. + +## 7.8.4 Method of test + +### 7.8.4.1 Initial conditions + +Test environment: + +- normal; see clause B.2 + +RF channels to be tested for single carrier: + +- M; see clause 4.12.1. + +### 7.8.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect *TAB connector* to measurement equipment as shown in annex D.2.5. All *TAB connectors* not under test shall be terminated. + +For each supported E-UTRA channel BW: + +- 2) Adjust the signal generator for the wanted signal as specified in table 7.8.5-1 for AAS BS of Wide Area BS class, in table 7.8.5-2 for AAS BS of Local Area BS class and in table 7.8.5-3 for AAS BS of Medium Range BS class on one side of the $F_C$ . +- 3) Adjust the signal generator for the interfering signal as specified in table 7.8.5-1 for AAS BS of Wide Area BS class, in table 7.8.5-2 for AAS BS of Local Area BS class and in table 7.8.5-3 for AAS BS of Medium Range BS class at opposite side of the $F_C$ and adjacent to the wanted signal. +- 4) Measure throughput. +- 5) Repeat the measurement with the wanted signal on the other side of the $F_C$ , and the interfering signal at opposite side of the $F_C$ and adjacent to the wanted signal. + +In addition, for *multi-band TAB connector(s)*, the following steps shall apply: + +- 6) For *multi-band TAB connectors* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 7.8.5 Test requirements + +For each measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel as specified in [Annex A] with parameters specified in table 7.8.5-1 for AAS BS of Wide Area BS, class in Table 7.8.5-2 for AAS BS of Local Area BS class and in table 7.8.5-3 for AAS BS of Medium Range BS class. + +**Table 7.8.5-1: Wide Area BS in-channel selectivity for E-UTRA channels** + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) | Type of interfering signal | +|--------------------------------|-------------------------------|--------------------------------|------------------------------|-------------------------------------|-------------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 1.4 | A1-4 in clause A.1 | -105.5 | -105.1 | -87 | 1.4 MHz E-UTRA signal, 3 RBs | +| 3 | A1-5 in clause A.1 | -100.7 | -100.3 | -84 | 3 MHz E-UTRA signal, 6 RBs | +| 5 | A1-2 in clause A.1 | -98.6 | -98.2 | -81 | 5 MHz E-UTRA signal, 10 RBs | +| 10 | A1-3 in clause A.1 | -97.1 | -96.7 | -77 | 10 MHz E-UTRA signal, 25 RBs | +| 15 | A1-3 in clause A.1 (Note) | -97.1 | -96.7 | -77 | 15 MHz E-UTRA signal, 25 RBs (Note) | +| 20 | A1-3 in clause A.1 (Note) | -97.1 | -96.7 | -77 | 20 MHz E-UTRA signal, 25 RBs (Note) | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ . + +**Table 7.8.5-2: Local Area BS in-channel selectivity for E-UTRA channels** + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) | Type of interfering signal | +|--------------------------------|-------------------------------|--------------------------------|------------------------------|-------------------------------------|-------------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 1.4 | A1-4 in clause A.1 | -97.5 | -97.1 | -79 | 1.4 MHz E-UTRA signal, 3 RBs | +| 3 | A1-5 in clause A.1 | -92.7 | -92.3 | -76 | 3 MHz E-UTRA signal, 6 RBs | +| 5 | A1-2 in clause A.1 | -90.6 | -90.2 | -73 | 5 MHz E-UTRA signal, 10 RBs | +| 10 | A1-3 in clause A.1 | -89.1 | -88.7 | -69 | 10 MHz E-UTRA signal, 25 RBs | +| 15 | A1-3 in clause A.1 (Note) | -89.1 | -88.7 | -69 | 15 MHz E-UTRA signal, 25 RBs (Note) | +| 20 | A1-3 in clause A.1 (Note) | -89.1 | -88.7 | -69 | 20 MHz E-UTRA signal, 25 RBs (Note) | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , this reference measurement channel and interfering signal are not applied for Band 46 and Band 49. + +**Table 7.8.5-3: Medium Range BS in-channel selectivity for E-UTRA channels** + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) | Type of interfering signal | +|--------------------------------|-------------------------------|--------------------------------|------------------------------|-------------------------------------|-------------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 1.4 | A1-4 in clause A.1 | -100.5 | -100.1 | -82 | 1.4 MHz E-UTRA signal, 3 RBs | +| 3 | A1-5 in clause A.1 | -95.7 | -95.3 | -79 | 3 MHz E-UTRA signal, 6 RBs | +| 5 | A1-2 in clause A.1 | -93.6 | -93.2 | -76 | 5 MHz E-UTRA signal, 10 RBs | +| 10 | A1-3 in clause A.1 | -92.1 | -91.7 | -72 | 10 MHz E-UTRA signal, 25 RBs | +| 15 | A1-3 in clause A.1 (Note) | -92.1 | -91.7 | -72 | 15 MHz E-UTRA signal, 25 RBs (Note) | +| 20 | A1-3 in clause A.1 (Note) | -92.1 | -91.7 | -72 | 20 MHz E-UTRA signal, 25 RBs (Note) | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , this reference measurement channel and interfering signal are not applied for Band 46. + +For NR channels, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A of TS 38.104 [36] with parameters specified in Table 7.8.5-4 for Wide Area BS, in Table 7.8.5-5 for Medium Range BS and in Table 7.8.5-6 for Local Area BS. The characteristics of the interfering signal is further specified in annex A of TS 38.104 [36]. + +**Table 7.8.5-4: Wide Area BS in-channel selectivity for NR channels** + +| NR channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | | | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------|--------------------------|-------------------------------|--------------------------------|------------------------------|------------------------------|-------------------------------------|--------------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | | | +| 5 | 15 | G-FR1-A1-7 | -99.2 | -98.8 | -98.1 | -81.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 PRBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -97.3 | -96.9 | -96.2 | -77.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 PRBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -90.9 | -90.5 | -89.8 | -71.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 PRBs | +| 5 | 30 | G-FR1-A1-8 | -99.9 | -99.5 | -98.8 | -81.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 PRBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -97.4 | -97 | -96.3 | -78.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 PRBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -91.2 | -90.8 | -90.1 | -71.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 PRBs | +| 10, 15, 20, 25, 30 | 60 | G-FR1-A1-9 | -96.8 | -96.4 | -95.7 | -78.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 PRBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -91.3 | -90.9 | -90.2 | -71.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 PRBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for BS channel bandwidth of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [41]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.8.5-5: Medium Range BS in-channel selectivity for NR channels** + +| NR channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | | | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------------------|--------------------------------|----------------------------------------|----------------------------------------|-------------------------------------|--------------------------------------------| +| | | | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | | | +| 5 | 15 | G-FR1-A1-7 | -94.2 | -93.8 | -93.1 | -76.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 PRBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -92.3 | -91.9 | -91.2 | -72.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 PRBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -85.9 | -85.5 | -84.8 | -66.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 PRBs | +| 5 | 30 | G-FR1-A1-8 | -94.9 | -94.5 | -93.8 | -76.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 PRBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -92.4 | -92 | -91.3 | -73.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -86.2 | -85.8 | -85.1 | -66.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 PRBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -91.8 | -91.4 | -90.7 | -73.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -86.3 | -85.9 | -85.2 | -66.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 PRBs | +| NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for BS channel bandwidth of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [41]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. | | | | | | | | + +**Table 7.8.5-6: Local area BS in-channel selectivity for NR channels** + +| NR channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | | | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------------------|--------------------------|-------------------------------|--------------------------------|----------------------------------------|----------------------------------------|-------------------------------------|--------------------------------------------| +| | | | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | | | +| 5 | 15 | G-FR1-A1-7 | -91.2 | -90.8 | -90.1 | -73.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 PRBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -89.3 | -88.9 | -88.2 | -69.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 PRBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -82.9 | -82.5 | -81.8 | -63.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 PRBs | +| 5 | 30 | G-FR1-A1-8 | -91.9 | -91.5 | -90.8 | -73.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 PRBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -89.4 | -89 | -88.3 | -70.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -83.2 | -82.8 | -82.1 | -63.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 PRBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -88.8 | -88.4 | -87.7 | -70.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -83.3 | -82.9 | -82.2 | -63.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 PRBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for BS channel bandwidth of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [41]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 8 Performance requirements + +### 8.1 General + +Performance requirements specify the ability of the AAS BS to correctly demodulate signals in various conditions and configurations. + +The demodulation requirements for an AAS BS are the same as non-AAS BS demodulation requirements specified for: + +- *Single RAT UTRA operation* in TS 25.104 [9] clause 8 for FDD operation, and in TS 25.105 [10] clause 8 for TDD operation, +- *Single RAT E-UTRA operation* in TS 36.104 [11], clauses 8.2 – 8.4 (for PUSCH, PUCCH and PRACH) and 8.6 – 8.7 (for subslot-PUSCH and SPUCCH). +- NR operation in TS 38.104 [36], clauses 8.2-8.5. + +The test requirements for the AAS BS performance requirements have hence been referenced from: + +- TS 25.141 [18] clause 8 for UTRA FDD, + +- TS 25.142 [20] clause 8 for UTRA TDD, +- TS 36.141 [17] clauses 8.2 – 8.4 (for PUSCH, PUCCH and PRACH) and 8.6 – 8.7 (for subslot-PUSCH and SPUCCH) for E-UTRA, and +- TS 38.104 [36] clauses 8.2 - 8.5 for NR. + +Necessary amendments for the AAS BS architecture are made in this clause. + +## 8.2 Performance requirements for MSR + +For *single RAT UTRA operation* in FDD, the minimum performance requirements are specified in clause 8.3. + +For *single RAT UTRA operation* in TDD 1,28Mcps option, the minimum performance requirements are specified in clause 8.4. + +For *single RAT E-UTRA operation*, the minimum performance requirements are specified in clause 8.5. + +For *NR operation*, the minimum performance requirements are specified in clause 8.6. + +## 8.3 Performance requirements for UTRA FDD + +### 8.3.1 Definition and applicability + +Performance requirements for *single RAT UTRA operation* in FDD are specified for the measurement channels defined in TS 25.104 [2]. The requirements only apply to those measurement channels that are supported by AAS BS. For FRC8 in TS 25.104 [2] the non E-DPCCH boosting and E-DPCCH boosting requirement only apply for the option supported by the AAS BS. The performance requirements for the high speed train scenarios defined in TS 25.104 [2] and TS 25.105 [3] are optional. + +Unless stated otherwise, performance requirements apply for a single cell only. Performance requirements for an AAS BS supporting DC-HSUPA or DB-DC-HSUPA are defined in terms of single carrier requirements. The requirements in clause 8 shall be met with the transmitter unit(s) associated with the *TAB connector(s)* in the operating band ON. + +NOTE: In normal operating conditions the *TAB connector(s)* are configured to transmit and receive at the same time. The transmitter unit(s) associated with the *TAB connector(s)* may be OFF for some of the tests. + +In the referred UTRA specifications and in this clause, the term BS with RX diversity refers to performance requirements for two *demodulation branches*, and BS without RX diversity refers to performance requirements for one *demodulation branch*. + +For AAS BS with RX diversity, only the BS performance requirements with RX diversity apply, the required $E_b/N_0$ shall be applied separately for each *demodulation branch*. + +For AAS BS without RX diversity, only the BS performance requirements without RX diversity apply. The required $E_b/N_0$ shall be applied for each AAS BS *demodulation branch*. + +The $E_b/N_0$ used is defined as: + +Where: + +- is the received total energy of DPDCH, DPCCH, S-DPCCH, HS-DPCCH, E-DPDCH, S-E-DPDCH, E-DPCCH and S-E-DPCCH per PN chip per *demodulation branch* from all branches +- is the total one-sided noise power spectral density due to all noise sources +- is the number of chips per frame +- is the number of information bits in DTCH excluding CRC bits per frame + +**Table 8.3.1-1: Summary of AAS BS performance targets for *single RAT UTRA operation* in FDD** + +| Physical channel | Measurement channel | Static | Multi-path Case 1 | Multi-path Case 2 | Multi-path Case 3 | Moving | Birth / Death | High Speed Train (Note) | +|------------------|---------------------|-------------------------------------------|-------------------------------------------|-------------------------------------------|---------------------------------------------------------------|--------------------------------------------|--------------------------------------------|-------------------------| +| | | Performance metric | | | | | | | +| DCH | 12.2 kbps | BLER<10 -2 | BLER<10 -2 | 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 | 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. + +In the referenced test requirements from TS 25.141 [15] the method to test describes connection to one or a number of BS antenna connectors. When applying these methods to the AAS BS connection shall be made to the declared *TAB connectors* (see table 4.10-1, D8.1) which represent the *demodulation branches*. + +## 8.3.2 Minimum Requirement + +The minimum requirements for the *single RAT UTRA operation* in FDD for each of the tests specified in clauses 8.2 to 8.13 of TS 25.141 [18] are the demodulation performance requirements specified in clauses 8.2 to 8.12 of TS 25.104 [9]. + +## 8.3.3 Test purpose + +The test shall verify the receiver's ability to achieve the specified performance metrics under the measurement channels and conditions for a given $E_c/N_0$ or $E_b/N_0$ for each of the demodulation performance requirements specified in clauses 8.2 to 8.12 of TS 25.104 [9]. + +## 8.3.4 Method of test + +### 8.3.4.1 Initial Conditions + +The initial conditions for each of the tests as specified in clauses 8.2 to 8.13 of TS 25.141 [18], shall be the same as those specified in clauses 8.2 to 8.13 of TS 25.141 [18]. + +With the exception that instead of connecting to BS antenna connectors as stated in TS 25.141 [18], clause 8 connection shall be made to the declared *TAB connectors* which represent the *demodulation branches* (see table 4.10-1, D6.74). + +All unused *TAB connectors* shall be terminated. Receiver units associated with unused *TAB connectors* may be turned OFF. + +### 8.3.4.2 Procedure + +The initial conditions shall be the same as those specified in clauses 8.2 to 8.13 of TS 25.141 [18]. + +## 8.3.5 Test Requirement + +The test requirements for each of the tests, as specified in clauses 8.2 to 8.13 of TS 25.141 [18], shall be the same as those in clauses 8.2 to 8.13 of TS 25.141 [18]. + +In the referenced test requirements in this clause, the term "BS with RX diversity" should be replaced with performance requirements for two *demodulation branches*, and the term "BS without RX diversity" should be replaced with performance requirements for one *demodulation branch*. + +## 8.4 Performance requirements for UTRA TDD + +### 8.4.1 Definition and applicability + +Performance requirements for *single RAT UTRA operation* in TDD are specified for the measurement channels defined in TS 25.105 [3]. The requirements only apply to those measurement channels that are supported by AAS BS. The performance requirements for the high speed train conditions defined in TS 25.105 [3] are optional. All Bit Error Ratio (BER) and Block Error Rate (BLER) measurements shall be carried out according to the general rules for statistical testing defined in recommendation ITU-T O.153 [34] and annex F of TS 25.142 [20]. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for a AAS 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 TS 25.105 [10], clause 5.18. + +In the referred UTRA specifications and in this clause, the term BS with dual RX diversity refers to performance requirements for two *demodulation branches*, and BS without RX diversity refers to performance requirements for one *demodulation branch*. + +For AAS BS with RX diversity, only the BS performance requirements with dual RX diversity apply, the required $\hat{I}_{or}/I_{oc}$ shall be applied separately for each *demodulation branch*. + +For AAS BS without RX diversity, only the BS performance requirements without dual RX diversity apply. The required $\hat{I}_{or}/I_{oc}$ shall be applied for each AAS BS *demodulation branch*. + +**Table 8.4.1-1: Summary of AAS BS performance targets for *single RAT UTRA operation* in TDD** + +| Physical channel | Measurement channel | Static | Multi-path Case 1 | Multi-path Case 2 (Note) | Multi-path Case 3 (Note) | High speed train (Note) | +|------------------|---------------------|------------------------------|------------------------------|------------------------------|------------------------------------------|------------------------------| +| | | 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. + +In the referenced test requirements from TS 25.142 [19] the method to test describes connection to one or a number of BS antenna connectors. When applying these methods to the AAS BS connection shall be made to the declared *TAB connectors* (see table 4.10-1, D8.1) which represent the *demodulation branches*. + +### 8.4.2 Minimum Requirement + +The minimum requirements for the *single RAT UTRA operation* in TDD for each of the tests specified in clauses 8.2 to 8.5 of TS 25.142 [20] are the demodulation performance requirements specified in clauses 8.2 to 8.5 of TS 25.105 [10]. + +### 8.4.3 Test purpose + +The test shall verify the receiver's ability to achieve the specified performance metrics under the measurement channels and conditions for a given $\hat{I}_{or}/I_{oc}$ for each of the demodulation performance requirements specified in clauses 8.2 to 8.5 of TS 25.105 [10]. + +## 8.4.4 Method of test + +### 8.4.4.1 Initial Conditions + +The initial conditions for each of the tests as specified in clauses 8.2 to 8.5 of TS 25.142 [20], shall be the same as those specified in clauses 8.2 to 8.5 of TS 25.142 [20]. + +With the exception that instead of connecting to BS antenna connectors as stated in clauses 8.2 to 8.5 of TS 25.142 [20] connection shall be made to the declared *TAB connectors* which represent the *demodulation branches* (see table 4.10-1, D6.74). + +All unused *TAB connectors* shall be terminated. Receiver units associated with unused *TAB connectors* may be turned OFF. + +### 8.4.4.2 Procedure + +The initial conditions shall be the same as those specified in clauses 8.2 to 8.5 of TS 25.142 [20]. + +## 8.4.5 Test Requirement + +The test requirements for each of the tests, as specified in clauses 8.2 to 8.5 of TS 25.142 [20], shall be the same as those in clauses 8.2 to 8.5 of TS 25.142 [20]. + +In the referenced test requirements in this clause, the term "BS with RX diversity" should be replaced with performance requirements for two *demodulation branches*, and the term "BS without RX diversity" should be replaced with performance requirements for one *demodulation branch*. + +# 8.5 Performance requirements for E-UTRA + +## 8.5.1 Definition and applicability + +Performance requirements for *single RAT E-UTRA operation* are specified for the fixed reference channels (FRC) and propagation conditions defined in TS 36.104 [8] annex A and annex B, respectively. The requirements only apply to those FRCs that are supported by the AAS BS. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for a *single RAT E-UTRA operation* supporting carrier aggregation are defined in terms of single carrier requirements. For FDD operation the requirements shall be met with the transmitter unit(s) associated with the *TAB connectors(s)* in the operating band ON. + +NOTE: In normal operating conditions the *TAB connector(s)* in FDD operation are configured to transmit and receive at the same time. The transmitter unit(s) associated with the *TAB connectors* may be OFF for some of the tests. + +In the referred E-UTRA specification, the term "RX antennas" refers to *demodulation branches* (i.e. not physical antennas). + +The SNR used in this clause is specified based on a single carrier and defined as: + +$$\text{SNR} = S / N$$ + +Where: + +S is the total signal energy in the subframe on a single *TAB connector*. + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the duration of a subframe. + +For enhanced performance requirements type A in TS 36.104 [4], the SINR used in this clause is specified based on a single carrier and defined as: + +$$\text{SINR} = S / N'$$ + +Where: + +$S$ is the total signal energy in the subframe on a single *TAB connector*. + +$N'$ is the summation of the received energy of the strongest interferers explicitly defined in a test procedure plus the white noise energy $N$ , in a bandwidth corresponding to the transmission bandwidth over the duration of a subframe on a single *TAB connector*. The respective energy of each interferer relative to $N'$ is defined by its associated DIP value. + +In the referenced test requirements from TS 36.141 [14] the method to test describes connection to one or a number of BS antenna connectors. When applying these methods to the AAS BS connection shall be made to the declared *TAB connectors* (see table 4.10-1, D8.1) which represent the *demodulation branches*. + +## 8.5.2 Minimum Requirement + +The minimum requirements for *single RATE-UTRA operation* for each of the tests specified in clauses 8.2 – 8.4 (for PUSCH, PUCCH and PRACH) and 8.6 – 8.7 (for subslot-PUSCH and SPUCCH) of TS 36.141 [17] are the demodulation performance requirements specified in clauses 8.2 – 8.4 and 8.6 – 8.7 of TS 36.104 [11]. + +## 8.5.3 Test purpose + +The test shall verify the receiver's ability to achieve the specified performance metrics under the measurement channels and conditions for a given SNR or SINR for each of the demodulation performance requirements specified in clauses 8.2 – 8.4 and 8.6 – 8.7 of TS 36.104 [11]. + +## 8.5.4 Method of test + +### 8.5.4.1 Initial Conditions + +The initial conditions for each of the tests as specified in clauses 8.2 – 8.4 and 8.6 – 8.7 of TS 36.141 [17], shall be the same as those specified in clauses 8.2 – 8.4 and 8.6 – 8.7 of TS 36.141 [17]. + +With the exception that instead of connecting to BS antenna connectors as stated in TS 36.141 [17] clause 8 connection shall be made to the declared *TAB connectors* which represent the *demodulation branches* (see table 4.10-1, D6.74). + +All unused *TAB connectors* shall be terminated. Receiver units associated with unused *TAB connectors* may be turned OFF. + +### 8.5.4.2 Procedure + +The procedure shall be the same as those specified in clauses 8.2 – 8.4 and 8.6 – 8.7 of TS 36.141 [17]. + +## 8.5.5 Test Requirement + +The test requirements for each of the tests, as specified in clauses 8.2 – 8.4 and 8.6 – 8.7 of TS 36.141 [17], shall be the same as those in clauses 8.2 – 8.4 and 8.6 – 8.7 of TS 36.141 [17]. + +In the referenced test requirements in this clause, the term "number of RX antennas" should be replaced by the number of *demodulation branches*. + +# 8.6 Performance requirements for NR + +## 8.6.1 Definition and applicability + +Conducted performance requirements specify the ability of the *BS type 1-H* to correctly demodulate signals in various conditions and configurations. Conducted performance requirements are specified at the *TAB connector(s)*. + +Performance requirements for NR operation are specified for the fixed reference channels (FRC) and propagation conditions defined in TS 38.104 [36] annex A and annex G, respectively. The requirements only apply to those FRCs that are supported by the NR BS. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for a NR operation supporting carrier aggregation are defined in terms of single carrier requirements. + +For FDD operation the requirements in clause 8 shall be met with the transmitter units associated with *TAB connectors* in the *operating band* turned ON. + +NOTE: In normal operating conditions, transceivers in FDD operation are configured to transmit and receive at the same time. The associated transmitter unit(s) may be OFF for some of the tests as specified in TS 38.141-1 [37]. + +In the referred NR specification, the term "RX antennas" refers to *demodulation branches* (i.e. not physical antennas). + +The SNR used in this clause is specified based on a single carrier and defined as: + +$$\text{SNR} = S / N$$ + +Where: + +S is the total signal energy in the slot on a single *TAB connector*. + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the duration of a slot on a single *TAB connector*. + +## 8.6.2 Minimum Requirement + +The minimum requirements for NR operation for each of the tests specified in clauses 8.2 – 8.4 (for PUSCH, PUCCH and PRACH) of TS 38.141-1 [37] are the demodulation performance requirements specified in clauses 8.2 – 8.4 of TS 38.104 [36]. + +## 8.6.3 Test purpose + +The test shall verify the receiver's ability to achieve the specified performance metrics under the measurement channels and conditions for a given SNR for each of the demodulation performance requirements specified in clauses 8.2 – 8.4 of TS 38.104 [36]. + +## 8.6.4 Method of test + +### 8.6.4.1 Initial conditions + +The initial conditions for each of the or each of the PUSCH, PUCCH or PRACH requirements shall be the same as those specified in related clauses 8.2 – 8.4 of TS 38.141-1 [37]. + +Connection shall be made to the declared *TAB connectors* which represent the *demodulation branches* (see table 4.10-1, D6.74). + +All unused *TAB connectors* shall be terminated. Receiver units associated with unused *TAB connectors* may be turned OFF. + +### 8.6.4.2 Procedure + +The procedure shall be the same as those specified in clauses 8.2 – 8.4 of TS 38.141-1 [37]. + +## 8.6.5 Test Requirement + +The test requirements for each of the PUSCH, PUCCH or PRACH requirements shall be the same as those in related clauses 8.2 – 8.4 of TS 38.141-1 [37]. + +In the referenced test requirements, the term "number of RX antennas" should be replaced by the number of *demodulation branches*. + +--- + +## Annex A (normative): Characteristics of interfering signals + +--- + +## Annex B (normative): Environmental requirements for the BS equipment + +### B.1 General + +For each test in the present document, the environmental conditions under which the AAS BS is to be tested are defined. The environmental conditions and class shall be from the relevant IEC specifications or the corresponding ETSI specifications. + +--- + +### B.2 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 B.2-1. + +**Table B.2-1: 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. + +--- + +### B.3 Extreme test environment + +#### B.3.1 General + +The manufacturer shall declare one of the following: + +- 1) the equipment class for the equipment under test, as defined in the IEC 60721-3-3 [27] or ETSI EN 300 019-1-3 [29] ("Stationary use at weather protected locations"); +- 2) the equipment class for the equipment under test, as defined in the IEC 60721-3-4 [28] or ETSI EN 300 019-1-4 [30] ("Stationary use at non weather protected locations"); +- 3) the equipment that does not comply to the mentioned classes, the relevant classes from IEC 60721 [26] documentation for Temperature, Humidity and Vibration shall be declared. + +NOTE: Reduced functionality for conditions that fall outside of the standard operational conditions are not tested in the present document. These may be stated and tested separately. + +#### B.3.2 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 60068-2-1 [31]. + +**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 60068-2-2 [32]. + +NOTE: It is recommended that the equipment is made fully operational prior to the equipment being taken to its lower operating temperature. + +--- + +## B.4 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 into the equipment, conforming to the test procedure of IEC 60068-2-6 [33]. Other environmental conditions shall be within the ranges specified in annex B.2. + +NOTE: The higher levels of vibration may induce undue physical stress into equipment after a prolonged series of tests. The testing body should only vibrate the equipment during the RF measurement process. + +--- + +## B.5 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 60068-2-1 [31] Test Ab/Ad and IEC 60068-2-2 [32] 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 60068-2-1 [31] Test Ab/Ad and IEC 60068-2-2 [32] Test Bb/Bd: Dry Heat. + +--- + +## B.6 Measurement of test environments + +The measurement accuracy of the BS test environments shall be: + +| | | +|----------------------|------------------| +| Pressure: | $\pm 5$ kPa. | +| Temperature: | $\pm 2$ degrees. | +| Relative Humidity: | $\pm 5$ %. | +| DC Voltage: | $\pm 1,0$ %. | +| AC Voltage: | $\pm 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. + +--- + +## Annex C (informative): Test tolerances and derivation of test requirements + +Test requirements which are included by reference to TS 25.141 [15], TS 25.142 [19], TS 36.141 [14] or TS 37.141 [13] have been calculated within the referred test specification using the Test Tolerances defined therein. + +## Annex D (informative): Measurement system set-up + +### D.1 Transmitter + +#### D.1.1 AAS BS output power, transmitter ON/OFF power, modulation quality, frequency error and operating band unwanted emissions + +*TAB connectors* may be connected to the measurement equipment singularly and tested one at a time (figure D.1.1-1), or may be tested simultaneously in groups (figure D.1.1-2) where the group size may range from two to all the *TAB connectors* which are subject to particular transmitter test in this test setup. + +In all cases the measurement is per *TAB connector* but the measurement may be done in parallel. + +![Diagram of the measuring system set-up for a single TAB connector.](e38e591c444bf8a9b0f37d3cdfacec96_img.jpg) + +The diagram illustrates the measurement setup for a single TAB connector. On the left, a dashed rectangle represents the 'Transceiver unit array'. A vertical dashed line to its right marks the 'Transceiver array boundary'. Several horizontal lines, representing TAB connectors, pass through this boundary. The top connector is labeled '#1' and is connected to a box labeled 'Measurement equipment'. The next connector is labeled '#2' and is connected to a box labeled 'Load'. Vertical ellipsis dots indicate additional connectors. The bottom connector is labeled '#K' and is also connected to a box labeled 'Load'. An arrow points to the connector labeled '#K' with the text 'Transceiver array boundary connector TAB(n)'. + +Diagram of the measuring system set-up for a single TAB connector. + +**Figure D.1.1-1: Measuring system set-up for AAS BS output power, transmitter ON/OFF power, modulation quality, frequency error and operating band unwanted emissions for a single TAB connector** + +![Diagram of measuring system set-up for AAS BS output power. A dashed box on the left is labeled 'transceiver unit array'. A vertical dashed line to its right is labeled 'transceiver array boundary'. Multiple horizontal lines, labeled #1, #2, ..., #K, cross this boundary from left to right. Each line has a small square connector at the boundary, labeled 'Transceiver array boundary connector TAB(n)'. All lines terminate in a box on the right labeled 'Measurement Equipment'.](35ddc8b19bd31dedba7ba2d696f43bd0_img.jpg) + +Diagram of measuring system set-up for AAS BS output power. A dashed box on the left is labeled 'transceiver unit array'. A vertical dashed line to its right is labeled 'transceiver array boundary'. Multiple horizontal lines, labeled #1, #2, ..., #K, cross this boundary from left to right. Each line has a small square connector at the boundary, labeled 'Transceiver array boundary connector TAB(n)'. All lines terminate in a box on the right labeled 'Measurement Equipment'. + +Figure D.1.1-2: Measuring system set-up for AAS BS output power, transmitter ON/OFF power, modulation quality, frequency error and operating band unwanted emissions for multiple TAB connectors + +### D.1.2 Transmitter intermodulation + +![Diagram of measuring system set-up for transmitter intermodulation. A dashed box on the left represents the transceiver. A vertical dashed line is labeled 'Transceiver Array Boundary (TAB)'. Inside the box, multiple horizontal lines are labeled #1, #n, ..., #N_TABC. Lines #1 and #N_TABC terminate in 'Load' boxes. Line #n is labeled 'TAB connector under test' and connects to a circulator. A 'Wanted signal' is input to the circulator from the right. An 'Interferring signal' is also input to the circulator from the right, passing through an 'Att' (attenuator) and a 'Test signal' box. The circulator's output is connected to a 'Spectrum analyser'.](945312942dd5a2526ccbf77dbdf676ab_img.jpg) + +Diagram of measuring system set-up for transmitter intermodulation. A dashed box on the left represents the transceiver. A vertical dashed line is labeled 'Transceiver Array Boundary (TAB)'. Inside the box, multiple horizontal lines are labeled #1, #n, ..., #N\_TABC. Lines #1 and #N\_TABC terminate in 'Load' boxes. Line #n is labeled 'TAB connector under test' and connects to a circulator. A 'Wanted signal' is input to the circulator from the right. An 'Interferring signal' is also input to the circulator from the right, passing through an 'Att' (attenuator) and a 'Test signal' box. The circulator's output is connected to a 'Spectrum analyser'. + +Figure D.1.2-1: Measuring system set-up for transmitter intermodulation + +### D.1.3 Transmitter spurious emissions + +*TAB connectors* may be connected to the measurement equipment singularly and tested one at a time (figure D.1.3-1), or may be tested simultaneously in groups (figure D.1.3-2) where the group size may range from two to all the *TAB connectors* which are subject to transmitter spurious emissions test. + +In all cases the measurement is per *TAB connector* but the measurement may be done in parallel. + +![Diagram of measuring system set-up for transmitter spurious emissions for a single TAB connector. It shows a 'Transceiver unit array' on the left, separated by a 'Transceiver array boundary' from the test equipment. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'TX notch' which is then connected to 'Measurement equipment'. Connectors #2 and #K are each connected to a 'Load'. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'.](bd0102d6e3d91c70d57762f2c33904bf_img.jpg) + +Transceiver array boundary + +#1 + +#2 + +⋮ + +#K + +Load + +TX notch + +Measurement equipment + +Transceiver unit array + +Transceiver array boundary connector TAB(n) + +Diagram of measuring system set-up for transmitter spurious emissions for a single TAB connector. It shows a 'Transceiver unit array' on the left, separated by a 'Transceiver array boundary' from the test equipment. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'TX notch' which is then connected to 'Measurement equipment'. Connectors #2 and #K are each connected to a 'Load'. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'. + +**Figure D.1.3-1: Measuring system set-up for transmitter spurious emissions for a single *TAB connector*** + +![Diagram of measuring system set-up for transmitter spurious emissions for multiple TAB connectors in parallel test. It shows a 'Transceiver unit array' on the left, separated by a 'Transceiver array boundary' from the test equipment. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Each of these connectors is connected to its own 'TX notch', and all 'TX notch' blocks are connected to a single 'Measurement equipment' block. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'.](2220640608c0f0fbe74cc30accdcf03a_img.jpg) + +Transceiver array boundary + +#1 + +#2 + +⋮ + +#K + +TX notch + +TX notch + +TX notch + +Measurement equipment + +Transceiver unit array + +Transceiver array boundary connector TAB(n) + +Diagram of measuring system set-up for transmitter spurious emissions for multiple TAB connectors in parallel test. It shows a 'Transceiver unit array' on the left, separated by a 'Transceiver array boundary' from the test equipment. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Each of these connectors is connected to its own 'TX notch', and all 'TX notch' blocks are connected to a single 'Measurement equipment' block. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'. + +**Figure D.1.3-2: Measuring system set-up for transmitter spurious emissions for multiple *TAB connectors in parallel test*** + +## D.2 Receiver + +### D.2.1 Reference sensitivity level + +![Diagram of measuring system set-up for Reference sensitivity level Test. It shows a transceiver unit array (dashed box) connected to a transceiver array boundary (dotted line). At the boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Signal generator for the wanted signal'. Connectors #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'.](3d78972deac525eec7f3e871083ede74_img.jpg) + +transceiver array boundary + +#1 + +#2 + +⋮ + +#K + +Signal generator for the wanted signal + +Load + +Load + +transceiver unit array + +Transceiver array boundary connector TAB(n) + +Diagram of measuring system set-up for Reference sensitivity level Test. It shows a transceiver unit array (dashed box) connected to a transceiver array boundary (dotted line). At the boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Signal generator for the wanted signal'. Connectors #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'. + +Figure D.2.1-1: Measuring system Set-up for Reference sensitivity level Test + +### D.2.2 Receiver Dynamic Range + +![Diagram of measuring system set-up for Dynamic Range Test. It shows a transceiver unit array (dashed box) connected to a transceiver array boundary (dotted line). At the boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Hybrid' block. Connector #2 and #K are connected to 'Load' blocks. The 'Hybrid' block is connected to two signal generators: 'Signal generator for the wanted signal' and 'Signal generator for the AWGN interfering signal'. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'.](4f1d9d4c58def49634d2896db1134b83_img.jpg) + +transceiver array boundary + +#1 + +#2 + +⋮ + +#K + +Hybrid + +Signal generator for the wanted signal + +Signal generator for the AWGN interfering signal + +Load + +Load + +transceiver unit array + +Transceiver array boundary connector TAB(n) + +Diagram of measuring system set-up for Dynamic Range Test. It shows a transceiver unit array (dashed box) connected to a transceiver array boundary (dotted line). At the boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Hybrid' block. Connector #2 and #K are connected to 'Load' blocks. The 'Hybrid' block is connected to two signal generators: 'Signal generator for the wanted signal' and 'Signal generator for the AWGN interfering signal'. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'. + +Figure D.2.2-1: Measuring system Set-up for Dynamic Range Test + +## D.2.3 Receiver Adjacent channel selectivity and narrowband blocking + +![Diagram of measuring system set-up for Adjacent channel selectivity and narrowband blocking Test. It shows a transceiver unit array with multiple ports (#1, #2, ..., #K) connected to a transceiver array boundary. Port #1 is connected to a Hybrid, which is then connected to two signal generators via attenuators ATT1 and ATT2. Port #2 is connected to a Load. Port #K is also connected to a Load. The signal generators are labeled 'Signal generator for the wanted signal' and 'Signal generator for the interfering signal'. The boundary is labeled 'transceiver array boundary' and the connector is 'Transceiver array boundary connector TAB(n)'.](15be56665b11258de01ed9f11b85ac3b_img.jpg) + +The diagram illustrates the test setup for receiver adjacent channel selectivity and narrowband blocking. A dashed box on the left represents the 'transceiver unit array'. A vertical dashed line marks the 'transceiver array boundary'. At this boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Hybrid' component. The Hybrid has two outputs: one connected to 'ATT1' (Attenuator 1) which leads to a 'Signal generator for the wanted signal', and another connected to 'ATT2' (Attenuator 2) which leads to a 'Signal generator for the interfering signal'. Connector #2 is connected to a 'Load'. Connector #K is also connected to a 'Load'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Diagram of measuring system set-up for Adjacent channel selectivity and narrowband blocking Test. It shows a transceiver unit array with multiple ports (#1, #2, ..., #K) connected to a transceiver array boundary. Port #1 is connected to a Hybrid, which is then connected to two signal generators via attenuators ATT1 and ATT2. Port #2 is connected to a Load. Port #K is also connected to a Load. The signal generators are labeled 'Signal generator for the wanted signal' and 'Signal generator for the interfering signal'. The boundary is labeled 'transceiver array boundary' and the connector is 'Transceiver array boundary connector TAB(n)'. + +Figure D.2.3-1: Measuring system Set-up for Adjacent channel selectivity and narrowband blocking Test + +## D.2.4 Receiver spurious emissions + +*TAB connector(s)* may be connected to the measurement equipment singularly and tested one at a time (figure D.2.2-1), or may be tested simultaneously in groups (figure D.2.2-2) where the group size may range from 2 to all the *TAB connectors*. + +In all cases the measurement is per *TAB connector* but the measurement may be done in parallel. + +![Diagram of measuring system set-up for receiver spurious emissions for a single TAB connector. It shows a transceiver unit array with multiple ports (#1, #2, ..., #K) connected to a transceiver array boundary. Port #1 is connected to a TX notch, which is then connected to a Measurement receiver. Port #2 is connected to a Load. Port #K is also connected to a Load. The boundary is labeled 'transceiver array boundary' and the connector is 'Transceiver array boundary connector TAB(n)'.](1dd1fd872b949e838fdb2d5c42b4761b_img.jpg) + +The diagram illustrates the test setup for receiver spurious emissions for a single *TAB connector*. A dashed box on the left represents the 'transceiver unit array'. A vertical dashed line marks the 'transceiver array boundary'. At this boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'TX notch' component, which is then connected to a 'Measurement receiver'. Connector #2 is connected to a 'Load'. Connector #K is also connected to a 'Load'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Diagram of measuring system set-up for receiver spurious emissions for a single TAB connector. It shows a transceiver unit array with multiple ports (#1, #2, ..., #K) connected to a transceiver array boundary. Port #1 is connected to a TX notch, which is then connected to a Measurement receiver. Port #2 is connected to a Load. Port #K is also connected to a Load. The boundary is labeled 'transceiver array boundary' and the connector is 'Transceiver array boundary connector TAB(n)'. + +Figure D.2.4-1: Measuring system set-up for receiver spurious emissions for a single *TAB connector* + +![Diagram of measuring system set-up for receiver spurious emissions for multiple TAB connectors.](2f428a156e5b9a3416517ee20ce7e4e6_img.jpg) + +This diagram illustrates the measuring system set-up for receiver spurious emissions. On the left, a dashed box labeled 'transceiver unit array' contains multiple transceivers. A vertical dashed line labeled 'transceiver array boundary' separates this array from the external test equipment. At this boundary, there are multiple connectors labeled #1, #2, ..., #K. An arrow points to one of these connectors with the label 'Transceiver array boundary connector TAB(n)'. Each connector is linked to a 'TX' (transmitter) block. All 'TX' blocks are connected to a single large block on the right labeled 'Measurement receiver(s)'. + +Diagram of measuring system set-up for receiver spurious emissions for multiple TAB connectors. + +**Figure D.2.4-2: Measuring system set-up for receiver spurious emissions for multiple *TAB* connectors** + +## D.2.5 Receiver In-channel selectivity + +![Diagram of measuring system set-up for In-channel selectivity Test.](2939c0a0faaa25343a1205d5044ee48d_img.jpg) + +This diagram illustrates the measuring system set-up for an In-channel selectivity test. On the left, a dashed box labeled 'transceiver unit array' contains multiple transceivers. A vertical dashed line labeled 'transceiver array boundary' separates this array from the external test equipment. At this boundary, there are multiple connectors labeled #1, #2, ..., #K. An arrow points to one of these connectors with the label 'Transceiver array boundary connector TAB(n)'. Connector #1 is connected to a 'Hybrid' block. Connectors #2, ..., #K are each connected to a 'Load' block. The 'Hybrid' block is connected to a 'Signal generator for the wanted signal and E-UTRA interfering signal' block. + +Diagram of measuring system set-up for In-channel selectivity Test. + +**Figure D.2.5-1: Measuring system Set-up for In-channel selectivity Test** + +## D.2.6 Receiver Intermodulation + +![Block diagram of the measuring system set-up for receiver intermodulation test. It shows a transceiver unit array connected via a transceiver array boundary to various signal generators through attenuators (ATT1, ATT2, ATT3) and hybrid components.](c908c2c17b0800f07e33a113389b554b_img.jpg) + +The diagram illustrates the test setup for receiver intermodulation. On the left, a dashed box labeled 'transceiver unit array' contains multiple units. A vertical dashed line labeled 'transceiver array boundary' separates this array from the external test equipment. At this boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Hybrid' block. Connector #2 is connected to a 'Load' block. Connector #K is also connected to a 'Load' block. An arrow labeled 'Transceiver array boundary connector TAB(n)' points to the boundary line. The 'Hybrid' block connected to #1 has two outputs: one goes to an attenuator labeled 'ATT1' which is connected to a 'Signal generator for the wanted signal'; the other goes to a second 'Hybrid' block. This second 'Hybrid' block has two outputs: one goes to an attenuator labeled 'ATT2' which is connected to a 'Signal generator for the CW interfering signal'; the other goes to an attenuator labeled 'ATT3' which is connected to a 'Signal generator for the WCDMA or E-UTRA interfering signal'. + +Block diagram of the measuring system set-up for receiver intermodulation test. It shows a transceiver unit array connected via a transceiver array boundary to various signal generators through attenuators (ATT1, ATT2, ATT3) and hybrid components. + +Figure D.2.6-1: Measuring system Set-up for receiver intermodulation Test + +--- + +## Annex E (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-02 | RAN4#78 | R4-161117 | | | | Specification structure | 0.1.0 | +| 2016-04 | RAN4#79 | R4-164273 | | | | Approved text proposals in the following documents were implemented:
R4-162956 - TP to TS 37.145 (part 1) - Sections 1-5
R4-162957 - TP to TS 37.145 (part 1) - Sections 6.1, 6.2, 6.3, 6.4
R4-162958 - TP to TS 37.145 (part 1) - Section 6.5
R4-162961 - TP to TS 37.145 (part 1) - Section 7
R4-162962 - TP to TS 37.145 (part 1) - Section 8
R4-162532 - TP to TS 37.145 (part 1) - Annex B | 0.2.0 | +| 2016-05 | RAN4#79 | R4-164926 | | | | R4-164711 - TP to TS 37.145 (part 1)
R4-164715 - TP to TS 37.145 (part 1) - Sections 6.5.3 (TAE)
R4-164712 - TP to TS 37.145 (part 1) 6.6 and 6.7 | 0.3.0 | +| 2016-08 | RAN4#80 | R4-167178 | | | | R4-166423 - TP to TS37.145-1 - reference corrections
R4-166217 - TP for TS 37.145-1: Editorial correction on table numbers
R4-166935 TP for TS 37.145-1: AAS BS Performance Target
R4-166936 TP to TS 37.145-1: Annex C (Test tolerances and derivation of test requirements)
R4-166937 TP to TS 37.145-1 - clean-up | 0.4.0 | +| 2016-09 | RANP#73 | RP-161449 | | | | Editorial corrections after review by ETSI editHelp | 1.0.0 | +| 2016-09 | RP#73 | | | | | TS Approved by RAN plenary | 13.0.0 | +| 2016-12 | RP-74 | RP-162422 | 0001 | - | D | TS 37.145 part 1: Editorial corrections | 13.1.0 | +| 2016-12 | RP-74 | RP-162422 | 0002 | - | F | TS 37.145 part 1: Corrections related to band 65 | 13.1.0 | +| 2016-12 | RP-74 | RP-162422 | 0003 | 1 | F | MB MSR related corrections on receiver blocking | 13.1.0 | +| 2016-12 | RP-74 | RP-162422 | 0005 | - | F | Correction of Manufacturer declaration description list in TS 37.145-1 | 13.1.0 | +| 2016-12 | RP-74 | RP-162422 | 0006 | 1 | F | TS 37.145 part 1: Corrections | 13.1.0 | +| 2016-12 | RP-74 | RP-162422 | 0007 | 1 | D | CR to TS 37.145-1: Frequency error corrections | 13.1.0 | +| 2017-03 | RP-75 | RP-170586 | 0008 | - | F | RF channels for blocking test | 13.2.0 | +| 2017-03 | RP-75 | RP-170586 | 0009 | - | F | Corrections of the power range for SEM and OBUE requirement. | 13.2.0 | +| 2017-03 | RP-75 | RP-170586 | 0010 | 1 | F | TS 37.145-1: Corrections on test procedure related to support for 256QAM | 13.2.0 | +| 2017-03 | RP-75 | RP-170586 | 0011 | - | F | CR to TS 37.145-1: Removal of FFS and TBD's | 13.2.0 | +| 2017-03 | RP-75 | RP-170586 | 0012 | 1 | D | CR to TS 37.145-1: Implementation comments from MCC and drafting rules implementation | 13.2.0 | +| 2017-03 | RP-75 | - | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2017-06 | RP-76 | RP-171306 | 0058 | | A | CR to TS 37.145-1: Isolation of Band 46 from the AAS BS specification | 14.1.0 | +| 2017-06 | RP-76 | RP-171306 | 0059 | | A | CR to TS 37.145-1: Isolation of the NB-IoT from the AAS BS specification | 14.1.0 | +| 2017-06 | RP-76 | RP-171306 | 0060 | | A | CR to TS 37.145-1: BS demodulation requirements update | 14.1.0 | +| 2017-06 | RP-76 | RP-171306 | 0061 | | A | CR to TS 37.145-1: Correction of the 256QAM test requirement for EVM | 14.1.0 | +| 2017-06 | RP-76 | RP-171306 | 0062 | | A | CR to TS 37.145-1: Update of Rel-13 references to the UTRA, EUTRA and MSR specifications | 14.1.0 | +| 2017-06 | RP-76 | RP-171306 | 0063 | | A | CR to TS 37.145-1: Introduction of Rel-13 bands: 45, 65, 66 and 68 | 14.1.0 | +| 2017-06 | RP-76 | RP-171306 | 0064 | | A | CR to TS 37.145-1: Correction of the test setup for the Tx spurious emissions requirement | 14.1.0 | +| 2017-06 | RP-76 | RP-171306 | 0065 | | A | CR to TS 37.145-1: MB-MSR update | 14.1.0 | +| 2017-09 | RP-77 | RP-171968 | 0067 | | A | CR to TS 37.145-1: Editorial corrections, Rel-14 | 14.2.0 | +| 2017-09 | RP-77 | RP-171968 | 0068 | 1 | B | CR to TS 37.145-1: introduction of bands 47, 48, 69, 70 | 14.2.0 | +| 2017-09 | RP-77 | RP-171968 | 0069 | | F | CR to TS 37.145-1: versioned references updates to Rel-14 non-AAS specifications | 14.2.0 | +| 2018-06 | RAN#80 | RP-181109 | 0071 | | A | CR to TS 37.145-1: corrections to the existing manufacturers declarations (4.10), Rel-14 | 14.3.0 | +| 2018-06 | RAN#80 | RP-181109 | 0073 | | A | CR to TS 37.145-1: correction of the performance metrics for BS demod, Rel-14 | 14.3.0 | +| 2018-06 | RAN#80 | RP-181109 | 0075 | | F | CR to TS 37.145-1: Correction of regional requirements - removal of co-location and co-existance (4.4), Rel-14 | 14.3.0 | +| 2018-06 | RAN#80 | RP-181109 | 0077 | | | Correction of test scope for ACLR tests | 14.3.0 | +| 2018-06 | SA#80 | | | | | Update to Rel-15 version (MCC) | 15.0.0 | +| 2018-09 | RAN#81 | RP-181910 | 0088 | | A | CR to TS 37.145-1: Clarification on manufacturers declarations | 15.1.0 | +| 2018-09 | RAN#81 | RP-181910 | 0096 | 1 | A | CR to TS 37.145-1: Correction of Occupied BS test applicability for CA, Rel-15 | 15.1.0 | +| 2018-09 | RAN#81 | RP-181910 | 0099 | 1 | A | CR to TS 37.145-1: E-UTRA DL RS power test requirement correction, Rel-15 | 15.1.0 | +| 2018-12 | RAN#82 | RP-182380 | 0102 | | A | CR to TS37.145-1_Adding RF channel for CA OBW (section 4.12.1) Rel.15 | 15.2.0 | +| 2018-12 | RAN#82 | RP-182380 | 0119 | 1 | A | Cleanup to conducted requirements text | 15.2.0 | +| 2018-12 | RAN#82 | RP-182380 | 0122 | | A | Clarification to ACLR test requirements | 15.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------|--------| +| 2018-12 | RAN#82 | RP-182362 | 0123 | 1 | B | Introduction of NR to 37.145-1 | 15.2.0 | +| 2018-12 | RAN#82 | RP-182380 | 0124 | | A | Correction of hybrid BS demodulation declarations | 15.2.0 | +| 2019-03 | RAN#83 | RP-190419 | 0126 | 1 | F | Correction to TDD OFF power requirement | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0128 | | F | CR to TS 37.145-1: Corrections on blocking requirements | 15.3.0 | +| 2019-03 | RAN#83 | RP-190412 | 0131 | | A | CR to TS 37.145-1: Intermodulation product bandwidth in Tx IMD test (Rel-15) | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0133 | 1 | F | CR to TS 37.145-1: editorial corrections and improving clarity to ACLR test requirements | 15.3.0 | +| 2019-03 | RAN#83 | RP-190412 | 0135 | 1 | A | TS 37.145-1: Editorial corrections | 15.3.0 | +| 2019-03 | RAN#83 | RP-190412 | 0138 | | A | CR to TS 37.145-1 on Correction of unwanted emissions scaling | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0139 | 1 | F | CR to TS 37.145-1: Implementation of 1024QAM for E-UTRA, Rel-15 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0140 | | F | CR to TS 37.145-1: Implementation of sTTI for E-UTRA, Rel-15 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190412 | 0143 | | A | CR to TS 37.145-1: BS Spurious emissions limits for protection of the BS receiver for B28 in Europe, Rel-15 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0144 | 1 | F | CR to TS 37.145-1: new Rel-15 bands and isolation of band 49, Tx, Rel-15 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0145 | | F | CR to TS 37.145-1: new Rel-15 bands and isolation of band 49, Rx, Rel-15 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190412 | 0147 | | A | CR to TS 37.145-1: Band 48 colocation correction, Rel-15 | 15.3.0 | +| 2019-06 | RAN#84 | RP-191263 | 0148 | 1 | F | CR to TS 37.145-1: Corrections on out-of-band blocking requirement | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0149 | 1 | F | CR to TS 37.145-1: clarification on CSA and RCSA relations for hybrid AAS BS, Rel-15 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191258 | 0152 | | F | CR to TS 37.145-1: correction of the throughput calculation in test procedures, Rel-15 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191237 | 0156 | | F | CR to TS 37.145-1: updates to Tx spur and co-location blocking | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0158 | | F | Correction on $\Delta$ fOOB for 37.145-1 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0159 | 2 | F | Addition of power backoff for 256QAM and 1024QAM | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0160 | 1 | F | Blocking requirement for MSR/NR operation | 15.4.0 | +| 2019-06 | RAN#84 | RP-191237 | 0163 | 2 | F | CR to TS 37.145-01: TAE requirement (section 6.5.3) | 15.4.0 | +| 2019-06 | RAN#84 | RP-191258 | 0166 | | A | CR to TS 37.145-1: mirror of operating band and frequency range declaration from NR, Rel-15 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0167 | 1 | B | CR to TS 37.145-1: BS demodulation requirements for NR | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0168 | | F | Non-AAS CRs mirroring to the AAS specification | 15.4.0 | +| 2019-06 | RAN#84 | RP-191250 | 0161 | 1 | B | n65 introduction to 37.145-1 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191257 | 0169 | | B | CR to 37.145-1: Introduction of Band 87 and 88 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191249 | 0170 | | B | CR to 37.145-1: Introduction of n48 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191245 | 0171 | | B | Introduce Band n18 to 37.145-1 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191243 | 0172 | 1 | B | Introduction of Band n14 in TS 37.145-1 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191247 | 0173 | | B | Introduction of Band n30 in TS 37.145-1 | 16.0.0 | +| 2019-09 | RAN#85 | RP-192053 | 0175 | | A | Correction to RX spurious emissions applicability range for SR E-UTRA BS | 16.1.0 | +| 2019-09 | RAN#85 | RP-192053 | 0177 | | A | CR for TS37.145-1: definition of synchronization operation | 16.1.0 | +| 2019-09 | RAN#85 | RP-192021 | 0179 | | A | CR to TS 37.145-1: Correction on SEM and operation band unwanted emission | 16.1.0 | +| 2019-09 | RAN#85 | RP-192021 | 0181 | | A | CR to TS 37.145-1: Correction on multi-band test configurations | 16.1.0 | +| 2019-09 | RAN#85 | RP-192021 | 0183 | | A | CR to TS37.145-1: Corrections on ICS requirement (Section 7.8.5) | 16.1.0 | +| 2019-09 | RAN#85 | RP-192021 | 0185 | | A | CR to TS37.145-1 Corrections on NBB requirement (section 7.4.5.1.2) | 16.1.0 | +| 2019-09 | RAN#85 | RP-192030 | 0186 | | F | CR on Protection of SUL band n89 to TS 37.145-1 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192021 | 0188 | | A | CR to TS 37.145-1 with addition of reference to data content for test models | 16.1.0 | +| 2019-09 | RAN#85 | RP-192021 | 0190 | | A | CR to TS 37.145-1 with editorial corrections | 16.1.0 | +| 2019-09 | RAN#85 | RP-192034 | 0191 | 1 | B | n29 introduction to 37.145-1 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192050 | 0195 | | A | CR to 37.145-1: correction of equivalent TAB connectors testing, Rel-16 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192021 | 0197 | | A | CR to TS37.145-1 editorial corrections on G-FRC (section 7.2.7.3) | 16.1.0 | +| 2019-12 | RAN#86 | RP-193014 | 0200 | | B | Introduction of 2010-2025MHz SUL band into Rel-16 TS 37.145-1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192991 | 0202 | | A | CR to 37.145-1 on Receiver Intermodulation signal offset correction | 16.2.0 | +| 2019-12 | RAN#86 | RP-192991 | 0204 | | A | CR to TS37.145-1 Corrections on NBB requirement (section 7.4.5.1.2) | 16.2.0 | +| 2019-12 | RAN#86 | RP-192991 | 0206 | | A | CR Modulation fallback for total power dynamic range in 37.145-1 clause 6.3.4.4.1.4 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192848 | 0207 | | B | CR to 37.145-1 on variable duplex FDD bands | 16.2.0 | +| 2020-03 | RAN#87 | RP-200381 | 0208 | | B | Introduction of n26 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200382 | 0209 | | B | Introduction of n53 | 16.3.0 | +| 2020-06 | RAN#88 | RP-200984 | 0210 | | F | TS 37.145-1: Corrections related to Foffset | 16.4.0 | +| 2020-06 | RAN#88 | RP-200984 | 0212 | | F | CR to 37.145-1: Correction on interference level of receiver dynamic range requirement | 16.4.0 | +| 2020-12 | RAN#90 | RP-202513 | 0224 | | A | CR to TS 37.145-1: correction of manufacturer | 16.5.0 | +| 2020-12 | RAN#90 | RP-202510 | 0227 | | A | CR to TS 37.145-1: Corrections to conformance requirements, Rel-16 | 16.5.0 | +| 2020-12 | RAN#90 | RP-202489 | 0229 | | A | CR to 37.145-1: Correction to applicability of additional BC3 | 16.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | requirement (Rel-16) | | +| 2020-12 | RAN#90 | RP-202510 | 0231 | | A | CR to 37.145-1 on Removal of additional limit for Band 1 | 16.5.0 | +| 2020-12 | RAN#90 | RP-202510 | 0233 | | A | CR to TS 37.145-1: addition of the OBUE applicability table, Rel-16 | 16.5.0 | +| 2020-12 | RAN#90 | RP-202451 | 0217 | - | B | Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.145-1 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202452 | 0218 | - | B | Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.145-1 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202448 | 0220 | - | B | CR to TS 37.145-1: introduction of NR band n13 | 17.0.0 | +| 2021-03 | RAN#91 | RP-210097 | 0234 | | B | CR for TS 37.145-1 introduction of NR band n24 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210096 | 0236 | 1 | B | CR to 37.145-1 on introducing new SUL band n99 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210111 | 0241 | | A | CR for 37.145-1: Corrections related to Band 24 regulatory updates | 17.1.0 | +| 2021-03 | RAN#91 | RP-210118 | 0247 | | A | CR to TS 37.145-1: Introduction of new BS capability set for NR+EUTRA+UTRA, Rel-17 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210121 | 0250 | | A | CR to 37.145-1 on Removal of additional limit for Band 7 | 17.1.0 | +| 2021-06 | RAN#92 | RP-211076 | 0256 | | A | CR to TS 37.145-1: Regional requirements for band 41 in Japan, Rel-17 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211082 | 0259 | 1 | A | CR to 37.145-1 to modify statement in Co-existence with other systems in the same geographical area in R17 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0260 | | B | CR to TS 37.145-1: Introduction of band n67 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0261 | 1 | B | CR to TS 37.145-1: Introduction of band n85 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211094 | 0263 | | A | CR to CR TS 37.145-1: Introduction of NR-U | 17.2.0 | +| 2021-06 | RAN#92 | RP-211090 | 0267 | | A | CR to 37.145-1: In-band blocking for multi-band Base Stations | 17.2.0 | +| 2021-06 | RAN#92 | RP-211091 | 0270 | | A | CR to 37.145-1: Correction to ACLR limit in non-contiguous spectrum (Rel-17) | 17.2.0 | +| 2021-09 | RAN#93 | RP-211909 | 0271 | | B | CR to TS 37.145-1: introduction of 35MHz and 45MHz | 17.3.0 | +| 2021-09 | RAN#93 | RP-211926 | 0274 | | A | Big CR for TS 37.145-1 Maintenance (Rel-17, CAT A) | 17.3.0 | +| 2021-12 | RAN#94 | RP-212856 | 0278 | | A | Big CR for TS 37.145-1 Maintenance (Rel-17, CAT A) | 17.4.0 | +| 2022-03 | RAN#95 | RP-220349 | 0279 | | B | CR for 37.145-1 on BS RF conformance testing for 1024QAM for NR FR1 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220347 | 0280 | 1 | B | CR to TS 37.145-1: implementation of LTE_upper_700MHz_A band 103 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220338 | 0284 | | A | Big CR for TS 37.145-1 Maintenance (Rel-17, CAT A) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220376 | 0285 | | B | CR to TS 37.145-1: RMR 1900MHz band n101 introduction | 17.5.0 | +| 2022-06 | RAN#96 | RP-221673 | 0286 | | B | CR on introduction of 6GHz licensed band for 37.145-1 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221675 | 0287 | | F | CR to 37.145-1: BS RF conformance requirements for 1024QAM in FR1 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221684 | 0288 | | B | CR to TS 37.145-1: introduction of n100 co-existence requirements, Rel-17 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221657 | 0291 | | A | Big CR for TS 37.145-1 Maintenance (Rel-17, CAT A) | 17.6.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | RP-223315 | 0292 | | B | CR to TS 37.145-1: Introduction of LTE TDD band 54 | 18.0.0 | +| 2022-12 | RAN#98-e | RP-223319 | 0294 | | B | CR to TS37.145-1 the introduction of APT600MHz | 18.0.0 | +| 2023-03 | RAN#99 | RP-230505 | 0297 | | A | CR to TS 37.145-1 with modulation quality and TPDR tests for NR updates | 18.1.0 | +| 2023-03 | RAN#99 | RP-230500 | 0300 | | A | CR to TS 37.145-1: The aplicability of additional BC3 requirements | 18.1.0 | +| 2023-03 | RAN#99 | RP-230500 | 0303 | | A | CR to 37.145-1: Operating band unwanted emission requirements | 18.1.0 | +| 2023-03 | RAN#99 | RP-230535 | 0305 | | B | CR to TS 37.145-1: Introduction of NR band n54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230527 | 0307 | 1 | F | CR to TS 37.145-1: LTE TDD band 54 additional spurious clarification | 18.1.0 | +| 2023-06 | RAN#100 | RP-231352 | 0312 | | A | CR to 37.145-1: Clarification on the OBUE limites when narrow carrier adjacent to the sub block edge | 18.2.0 | +| 2023-06 | RAN#100 | RP-231354 | 0315 | | A | CR to 37.145-1: Receiver spurious emissions | 18.2.0 | +| 2023-06 | RAN#100 | RP-231362 | 0316 | | B | CR to TS37.145-1: the introduction of 900 MHz LTE new band | 18.2.0 | +| 2023-09 | RAN#101 | RP-232486 | 0319 | | A | [AAS_BS_LTE_UTRA-Perf] CR to TS 37.145-1 with corrections to TCs for AAS BS conformance testing | 18.3.0 | +| 2023-09 | RAN#101 | RP-232486 | 0322 | | A | [AAS_BS_LTE_UTRA-Perf] CR to TS 37.145-1 with test signal configuration changes for AAS BS | 18.3.0 | +| 2023-09 | RAN#101 | RP-232504 | 0327 | | A | CR to 37.145-1: Correction to ACLR and CACLR requirement | 18.3.0 | +| 2023-12 | RAN#102 | RP-233339 | 0330 | | A | [NR_n18-Perf] CR to TS 37.145-1 on correction of transmitter spurious emissions for protection of Band n18 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0331 | | B | CR to TS37.145-1: introduction of NR bands n31 and n72 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0332 | 1 | B | CR to TS 37.145-1 - Introduction of band n109 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233337 | 0335 | | A | [MSR_GSM_UTRA_LTE_NR-Perf] CR to 37.145-1: Power allocation for NC operation | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0336 | | B | CR to 37.145-1 on introduction of Band 106 | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37145-2/raw.md b/marked/Rel-18/37_series/37145-2/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..821796a866a0a530c0d401b0899d814df73ee569 --- /dev/null +++ b/marked/Rel-18/37_series/37145-2/raw.md @@ -0,0 +1,12153 @@ + + +# 3GPP TS 37.145-2 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: radiated conformance testing (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green wave-like graphic above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------|----| +| Foreword..... | 22 | +| 1 Scope..... | 24 | +| 2 References..... | 24 | +| 3 Definitions, symbols and abbreviations..... | 26 | +| 3.1 Definitions..... | 26 | +| 3.2 Symbols..... | 30 | +| 3.3 Abbreviations..... | 32 | +| 4 General test conditions and declarations..... | 33 | +| 4.1 Measurement uncertainties and test requirements..... | 33 | +| 4.1.1 General..... | 33 | +| 4.1.2 Acceptable uncertainty of Test System..... | 35 | +| 4.1.2.1 General..... | 35 | +| 4.1.2.2 Measurement of transmitter..... | 36 | +| 4.1.2.3 Measurement of receiver..... | 39 | +| 4.1.2.4 Measurement of performance requirement..... | 40 | +| 4.1.3 Interpretation of measurement results..... | 40 | +| 4.2 Conducted and radiated requirement reference points..... | 40 | +| 4.3 Base station classes for AAS BS..... | 41 | +| 4.4 Regional requirements..... | 41 | +| 4.5 Operating bands and band categories..... | 43 | +| 4.6 Channel arrangements..... | 43 | +| 4.7 Requirements for AAS BS capable of multi-band operation..... | 43 | +| 4.8 AAS BS configurations..... | 44 | +| 4.8.1 Transmit configurations..... | 44 | +| 4.8.2 Receive configurations..... | 45 | +| 4.8.3 Power supply options..... | 46 | +| 4.8.4 BS with integrated Iuant BS modem..... | 46 | +| 4.9 Capability sets..... | 46 | +| 4.10 Manufacturer declarations..... | 47 | +| 4.11 Test signal configurations for testing..... | 54 | +| 4.11.1 General..... | 54 | +| 4.11.1A NR Test signal used to build Test Configurations..... | 55 | +| 4.11.2 Test signal configurations..... | 55 | +| 4.11.2.1 ATCR1: UTRA multicarrier operation..... | 55 | +| 4.11.2.1.1 General..... | 55 | +| 4.11.2.1.2 ATCR1a generation..... | 55 | +| 4.11.2.1.3 ATCR1b generation..... | 55 | +| 4.11.2.1.4 ATCR1 power allocation..... | 55 | +| 4.11.2.2 ANTCR1: UTRA FDD multicarrier non-contiguous operation..... | 56 | +| 4.11.2.2.1 General..... | 56 | +| 4.11.2.2.2 ANTCR1 generation..... | 56 | +| 4.11.2.2.3 ANTCR1 power allocation..... | 56 | +| 4.11.2.3 ATCR2: E-UTRA multicarrier operation..... | 56 | +| 4.11.2.3.1 General..... | 56 | +| 4.11.2.3.2 ATCR2a generation..... | 56 | +| 4.11.2.3.3 ATCR2b generation..... | 57 | +| 4.11.2.3.4 ATCR2 power allocation..... | 57 | +| 4.11.2.4 ANTCR2: E-UTRA multicarrier non-contiguous operation..... | 58 | +| 4.11.2.4.1 General..... | 58 | +| 4.11.2.4.2 ANTCR2 generation..... | 58 | +| 4.11.2.4.3 ANTCR2 power allocation..... | 58 | +| 4.11.2.5 ATCR3: UTRA and E-UTRA multi-RAT operation..... | 58 | +| 4.11.2.5.1 General..... | 58 | +| 4.11.2.5.2 ATCR3a generation..... | 59 | +| 4.11.2.5.3 ATCR3b generation..... | 59 | + +| | | | +|-------------|--------------------------------------------------------------------------------------------------------------------------|----| +| 4.11.2.5.4 | ATCR3 power allocation..... | 59 | +| 4.11.2.6 | ANTCR3: UTRA and E-UTRA multi-RAT non-contiguous operation..... | 59 | +| 4.11.2.6.1 | General..... | 59 | +| 4.11.2.6.2 | ANTCR3 generation..... | 59 | +| 4.11.2.6.3 | ANTCR3 power allocation..... | 60 | +| 4.11.2.7 | ATCR4: Single carrier for receiver tests..... | 60 | +| 4.11.2.7.1 | ATCR4a generation..... | 60 | +| 4.11.2.7.2 | ATCR4b generation..... | 60 | +| 4.11.2.7.3 | ATCR4c generation..... | 60 | +| 4.11.2.7.3A | ATCR4d generation..... | 61 | +| 4.11.2.7.4 | ATCR4 power allocation..... | 61 | +| 4.11.2.8 | ATCR5: MB-MSR operation..... | 61 | +| 4.11.2.8.1 | ATCR5a: MB-MSR test configuration for full carrier allocation..... | 61 | +| 4.11.2.8.2 | ATCR5b: MB-MSR test configuration with high PSD per carrier..... | 62 | +| 4.11.2.9 | ATCR6: Single carrier for transmitter tests..... | 63 | +| 4.11.2.9.1 | ATCR6a generation..... | 63 | +| 4.11.2.9.2 | ATCR6b generation..... | 63 | +| 4.11.2.9.3 | Void..... | 63 | +| 4.11.2.9.3A | ATCR6d generation..... | 63 | +| 4.11.2.9.4 | ATCR6 power allocation..... | 63 | +| 4.11.2.10 | ATCR7: E-UTRA and NR multi RAT operation..... | 64 | +| 4.11.2.10.1 | General..... | 64 | +| 4.11.2.10.2 | ATCR7 generation..... | 64 | +| 4.11.2.10.3 | ATCR7 power allocation..... | 64 | +| 4.11.2.11 | ANTCR7: E-UTRA and NR multi RAT non-contiguous operation..... | 65 | +| 4.11.2.11.1 | General..... | 65 | +| 4.11.2.11.2 | ANTCR7 generation..... | 65 | +| 4.11.2.11.3 | ANTCR7 power allocation..... | 65 | +| 4.11.2.12 | ATCR8: NR multicarrier operation..... | 65 | +| 4.11.2.12.1 | General..... | 65 | +| 4.11.2.12.2 | ATCR8a generation..... | 66 | +| 4.11.2.12.3 | ATCR8b generation..... | 66 | +| 4.11.2.12.4 | ATCR8 power allocation..... | 66 | +| 4.11.2.13 | ANTCR8: NR multicarrier non-contiguous operation..... | 67 | +| 4.11.2.13.1 | General..... | 67 | +| 4.11.2.13.2 | ANTCR8 generation..... | 67 | +| 4.11.2.13.3 | ANTCR8 power allocation..... | 67 | +| 4.11.2.14 | ATCR9: UTRA, E-UTRA and NR multi-RAT operation..... | 67 | +| 4.11.2.14.1 | General..... | 67 | +| 4.11.2.14.2 | ATCR9 generation..... | 67 | +| 4.11.2.14.3 | ATCR9 power allocation..... | 68 | +| 4.11.2.15 | ANTCR9: UTRA, E-UTRA and NR multi-RAT non-contiguous operation..... | 68 | +| 4.11.2.15.1 | ANTCR9 generation..... | 68 | +| 4.11.2.15.2 | ANTCR9 power allocation..... | 69 | +| 4.12 | RF channels and test models..... | 69 | +| 4.12.1 | RF channels..... | 69 | +| 4.12.2 | Test models..... | 70 | +| 4.13 | Format and interpretation of tests..... | 71 | +| 4.14 | Reference coordinate system..... | 72 | +| 4.15 | Co-location requirements..... | 73 | +| 4.15.1 | General..... | 73 | +| 4.15.2 | Co-location test antenna..... | 74 | +| 4.15.2.1 | General..... | 74 | +| 4.15.2.2 | Co-location test antenna characteristics..... | 74 | +| 4.15.2.3 | Co-location test antenna alignment..... | 74 | +| 5 | Applicability of Requirements..... | 75 | +| 5.1 | General..... | 75 | +| 5.2 | Test configurations for AAS BS for operating bands where MSR with more than 1 RAT is supported..... | 78 | +| 5.3 | Test configurations for multi-carrier capable AAS BS in operating bands where one RAT capability sets are supported..... | 84 | +| 5.3.1 | General..... | 84 | + +| | | | +|-----------|-------------------------------------------------------------------------------------|-----| +| 5.3.2 | AAS BS supporting one RAT only MSR in the operating band..... | 84 | +| 5.3.3 | AAS BS supporting Single-RAT UTRA in the operating band..... | 90 | +| 5.3.4 | AAS BS supporting Single-RAT E-UTRA in the operating band..... | 92 | +| 5.4 | Test configurations for AAS BS operating bands with multi-band dependencies..... | 95 | +| 5.4.1 | AAS BS operating bands with multi-band dependencies supporting MSR operation..... | 95 | +| 5.4.2 | AAS BS operating bands with multi-band dependencies supporting Single-RAT only..... | 97 | +| 6 | Radiated transmitter characteristics..... | 100 | +| 6.1 | General..... | 100 | +| 6.2 | Radiated Transmit Power..... | 100 | +| 6.2.1 | Definition and applicability..... | 100 | +| 6.2.2 | Minimum Requirement..... | 101 | +| 6.2.3 | Test purpose..... | 101 | +| 6.2.4 | Method of test..... | 101 | +| 6.2.4.1 | Initial conditions..... | 101 | +| 6.2.4.2 | Procedure..... | 102 | +| 6.2.5 | Test Requirement..... | 102 | +| 6.3 | OTA Base Station output power..... | 103 | +| 6.3.1 | General..... | 103 | +| 6.3.2 | OTA Maximum output power..... | 103 | +| 6.3.2.1 | Definition and applicability..... | 103 | +| 6.3.2.2 | Minimum Requirement..... | 103 | +| 6.3.2.3 | Test purpose..... | 103 | +| 6.3.2.4 | Method of test..... | 103 | +| 6.3.2.4.1 | Initial conditions..... | 103 | +| 6.3.2.4.2 | Procedure..... | 104 | +| 6.3.2.5 | Test Requirement..... | 104 | +| 6.3.3 | OTA E-UTRA DL RS power..... | 104 | +| 6.3.3.1 | Definition and applicability..... | 104 | +| 6.3.3.2 | Minimum Requirement..... | 104 | +| 6.3.3.3 | Test purpose..... | 105 | +| 6.3.3.4 | Method of test..... | 105 | +| 6.3.3.4.1 | Initial conditions..... | 105 | +| 6.3.3.4.2 | Procedure..... | 105 | +| 6.3.3.5 | Test Requirement..... | 105 | +| 6.4 | OTA Output power dynamics..... | 105 | +| 6.4.1 | General..... | 105 | +| 6.4.2 | OTA UTRA Inner loop power control in the downlink..... | 106 | +| 6.4.2.1 | Definition and applicability..... | 106 | +| 6.4.2.2 | Minimum requirement..... | 106 | +| 6.4.2.3 | Test purpose..... | 106 | +| 6.4.2.4 | Method of test..... | 106 | +| 6.4.2.4.1 | Initial conditions..... | 106 | +| 6.4.2.4.2 | Procedure..... | 106 | +| 6.4.2.5 | Test Requirement..... | 107 | +| 6.4.3 | OTA Power control dynamic range..... | 107 | +| 6.4.3.1 | Definition and applicability..... | 107 | +| 6.4.3.2 | Minimum Requirement..... | 108 | +| 6.4.3.3 | Test purpose..... | 108 | +| 6.4.3.4 | Method of test..... | 108 | +| 6.4.3.4.1 | Initial conditions..... | 108 | +| 6.4.3.4.2 | Procedure..... | 108 | +| 6.4.3.5 | Test Requirement..... | 109 | +| 6.4.4 | OTA total power dynamic range..... | 109 | +| 6.4.4.1 | Definition and applicability..... | 109 | +| 6.4.4.2 | Minimum Requirement..... | 109 | +| 6.4.4.3 | Test purpose..... | 109 | +| 6.4.4.4 | Method of test..... | 110 | +| 6.4.4.4.1 | Initial conditions..... | 110 | +| 6.4.4.4.2 | Procedure..... | 110 | +| 6.4.4.5 | Test Requirement..... | 112 | +| 6.4.4.5.1 | UTRA FDD..... | 112 | + +| | | | +|-----------|-----------------------------------------|-----| +| 6.4.4.5.2 | E-UTRA..... | 112 | +| 6.4.4.5.3 | NR..... | 112 | +| 6.4.5 | OTA IPDL time mask..... | 113 | +| 6.4.5.1 | Definition and applicability..... | 113 | +| 6.4.5.2 | Minimum Requirement..... | 113 | +| 6.4.5.3 | Test purpose..... | 113 | +| 6.4.5.4 | Method of test..... | 113 | +| 6.4.5.4.1 | Initial conditions..... | 113 | +| 6.4.5.4.2 | Procedure..... | 113 | +| 6.4.5.5 | Test Requirement..... | 114 | +| 6.4.6 | OTA RE Power control dynamic range..... | 114 | +| 6.4.6.1 | Definition and applicability..... | 114 | +| 6.4.6.2 | Minimum Requirement..... | 114 | +| 6.4.6.3 | Method of test..... | 115 | +| 6.5 | OTA Transmit ON/OFF power..... | 115 | +| 6.5.1 | General..... | 115 | +| 6.5.2 | OTA Transmitter OFF power..... | 115 | +| 6.5.2.1 | Definition and applicability..... | 115 | +| 6.5.2.2 | Minimum Requirement..... | 115 | +| 6.5.2.3 | Test purpose..... | 115 | +| 6.5.2.4 | Method of test..... | 115 | +| 6.5.2.4.1 | Initial conditions..... | 115 | +| 6.5.2.4.2 | Procedure..... | 116 | +| 6.5.2.5 | Test Requirement..... | 116 | +| 6.5.3 | OTA Transmitter transient period..... | 116 | +| 6.5.3.1 | Definition and applicability..... | 116 | +| 6.5.3.2 | Minimum Requirement..... | 117 | +| 6.5.3.3 | Test purpose..... | 117 | +| 6.5.3.4 | Method of test..... | 117 | +| 6.5.3.4.1 | Initial conditions..... | 117 | +| 6.5.3.4.2 | Procedure..... | 117 | +| 6.5.3.5 | Test Requirement..... | 118 | +| 6.6 | OTA Transmitted signal quality..... | 118 | +| 6.6.1 | General..... | 118 | +| 6.6.2 | OTA Frequency Error..... | 118 | +| 6.6.2.1 | Definition and applicability..... | 118 | +| 6.6.2.2 | Minimum Requirement..... | 119 | +| 6.6.2.3 | Test purpose..... | 119 | +| 6.6.2.4 | Method of test..... | 119 | +| 6.6.2.5 | Test Requirement..... | 119 | +| 6.6.2.5.1 | UTRA FDD test requirement..... | 119 | +| 6.6.2.5.2 | E-UTRA and NR test requirement..... | 119 | +| 6.6.3 | OTA Time alignment error..... | 119 | +| 6.6.3.1 | Definition and applicability..... | 119 | +| 6.6.3.2 | Minimum Requirement..... | 120 | +| 6.6.3.3 | Test purpose..... | 120 | +| 6.6.3.4 | Method of test..... | 120 | +| 6.6.3.4.1 | Initial conditions..... | 120 | +| 6.6.3.4.2 | Procedure..... | 121 | +| 6.6.3.5 | Test Requirement..... | 122 | +| 6.6.3.5.1 | UTRA FDD test requirement..... | 122 | +| 6.6.3.5.2 | E-UTRA test requirement..... | 122 | +| 6.6.3.5.3 | NR test requirement..... | 122 | +| 6.6.4 | OTA modulation quality..... | 122 | +| 6.6.4.1 | Definition and applicability..... | 122 | +| 6.6.4.2 | Minimum Requirement..... | 122 | +| 6.6.4.3 | Test purpose..... | 123 | +| 6.6.4.4 | Method of test..... | 123 | +| 6.6.4.4.1 | UTRA method of test..... | 123 | +| 6.6.4.4.2 | E-UTRA and NR method of test..... | 124 | +| 6.6.4.5 | Test Requirement..... | 126 | + +| | | | +|-------------|-----------------------------------------------------------|-----| +| 6.6.4.5.1 | UTRA test requirement..... | 126 | +| 6.6.4.5.2 | E-UTRA and NR test requirement..... | 126 | +| 6.7 | OTA Unwanted Emissions..... | 127 | +| 6.7.1 | General..... | 127 | +| 6.7.2 | OTA occupied bandwidth..... | 127 | +| 6.7.2.1 | Definition and applicability..... | 127 | +| 6.7.2.2 | Minimum Requirement..... | 128 | +| 6.7.2.3 | Test purpose..... | 128 | +| 6.7.2.4 | Method of test..... | 128 | +| 6.7.2.4.1 | Initial conditions..... | 128 | +| 6.7.2.4.2 | Procedure..... | 128 | +| 6.7.2.5 | Test Requirement..... | 129 | +| 6.7.2.5.1 | MSR..... | 129 | +| 6.7.2.5.2 | UTRA FDD..... | 130 | +| 6.7.2.5.3 | E-UTRA..... | 130 | +| 6.7.3 | OTA Adjacent Channel Leakage power Ratio..... | 130 | +| 6.7.3.1 | Definition and applicability..... | 130 | +| 6.7.3.2 | Minimum Requirement..... | 130 | +| 6.7.3.3 | Test purpose..... | 130 | +| 6.7.3.4 | Method of test..... | 130 | +| 6.7.3.4.1 | Initial conditions..... | 130 | +| 6.7.3.4.2 | Procedure..... | 131 | +| 6.7.3.4.2.2 | MSR..... | 132 | +| 6.7.3.4.2.3 | UTRA FDD..... | 132 | +| 6.7.3.4.2.4 | E-UTRA..... | 132 | +| 6.7.3.5 | Test Requirement..... | 133 | +| 6.7.3.5.1 | MSR..... | 133 | +| 6.7.3.5.2 | UTRA FDD..... | 139 | +| 6.7.3.5.3 | E-UTRA..... | 141 | +| 6.7.4 | OTA Spectrum emission mask..... | 144 | +| 6.7.4.1 | Definition and applicability..... | 144 | +| 6.7.4.2 | Minimum requirement..... | 144 | +| 6.7.4.3 | Test purpose..... | 144 | +| 6.7.4.4 | Method of test..... | 144 | +| 6.7.4.4.1 | Initial conditions..... | 144 | +| 6.7.4.4.2 | Procedure..... | 145 | +| 6.7.4.5 | Test Requirement..... | 146 | +| 6.7.4.5.1 | UTRA FDD..... | 146 | +| 6.7.5 | OTA Operating band unwanted emission..... | 156 | +| 6.7.5.1 | Definition and applicability..... | 156 | +| 6.7.5.2 | Minimum Requirement..... | 156 | +| 6.7.5.3 | Test purpose..... | 157 | +| 6.7.5.4 | Method of test..... | 157 | +| 6.7.5.4.1 | Initial conditions..... | 157 | +| 6.7.5.4.2 | Procedure..... | 157 | +| 6.7.5.5 | Test Requirement..... | 158 | +| 6.7.5.5.1 | General..... | 158 | +| 6.7.5.5.2 | MSR Band categories 1 and 3..... | 158 | +| 6.7.5.5.3 | MSR Band Category 2..... | 166 | +| 6.7.5.5.4 | MSR Additional requirements..... | 173 | +| 6.7.5.5.5 | E-UTRA..... | 177 | +| 6.7.6 | OTA Spurious emission..... | 199 | +| 6.7.6.1 | General..... | 199 | +| 6.7.6.2 | Mandatory Requirements..... | 200 | +| 6.7.6.2.1 | Definition and applicability..... | 200 | +| 6.7.6.2.2 | Minimum Requirement..... | 200 | +| 6.7.6.2.3 | Test purpose..... | 200 | +| 6.7.6.2.4 | Method of test..... | 200 | +| 6.7.6.2.5 | Test Requirement..... | 201 | +| 6.7.6.3 | Protection of the BS receiver of own or different BS..... | 204 | +| 6.7.6.3.1 | Definition and applicability..... | 204 | + +| | | | +|-----------|-------------------------------------------------|-----| +| 6.7.6.3.2 | Minimum Requirement..... | 204 | +| 6.7.6.3.3 | Test purpose..... | 204 | +| 6.7.6.3.4 | Method of test..... | 204 | +| 6.7.6.3.5 | Test Requirement..... | 206 | +| 6.7.6.4 | Additional spurious emissions requirements..... | 207 | +| 6.7.6.4.1 | Definition and applicability..... | 207 | +| 6.7.6.4.2 | Minimum Requirement..... | 207 | +| 6.7.6.4.3 | Test purpose..... | 207 | +| 6.7.6.4.4 | Method of test..... | 207 | +| 6.7.6.4.5 | Test Requirement..... | 208 | +| 6.7.6.5 | Co-location with other base stations..... | 242 | +| 6.7.6.5.1 | Definition and applicability..... | 242 | +| 6.7.6.5.2 | Minimum Requirement..... | 242 | +| 6.7.6.5.3 | Test purpose..... | 243 | +| 6.7.6.5.4 | Method of test..... | 243 | +| 6.7.6.5.5 | Test Requirement..... | 243 | +| 6.8 | OTA Transmitter intermodulation..... | 264 | +| 6.8.1 | Definition and applicability..... | 264 | +| 6.8.2 | Minimum Requirement..... | 264 | +| 6.8.3 | Test purpose..... | 264 | +| 6.8.4 | Method of test..... | 264 | +| 6.8.4.1 | Initial conditions..... | 264 | +| 6.8.4.2 | Procedure..... | 265 | +| 6.8.5 | Test Requirement..... | 267 | +| 6.8.5.1 | MSR test requirements..... | 267 | +| 6.8.5.1.1 | General test requirement..... | 267 | +| 6.8.5.1.2 | Additional test requirement (BC1 and BC2)..... | 268 | +| 6.8.5.1.3 | Additional test requirement (BC3)..... | 268 | +| 6.8.5.2 | Single RAT UTRA operation..... | 269 | +| 6.8.5.2.1 | General test requirement for UTRA FDD..... | 269 | +| 6.8.5.3 | Single RAT E-UTRA operation..... | 270 | +| 6.8.5.3.1 | General test requirement..... | 270 | +| 6.8.5.3.2 | Void..... | 270 | +| 7 | Radiated receiver characteristics..... | 270 | +| 7.1 | General..... | 270 | +| 7.2 | OTA sensitivity..... | 271 | +| 7.2.1 | Definition and applicability..... | 271 | +| 7.2.2 | Minimum Requirement..... | 272 | +| 7.2.3 | Test Purpose..... | 272 | +| 7.2.4 | Method of test..... | 272 | +| 7.2.4.1 | Initial conditions..... | 272 | +| 7.2.4.2 | Procedure..... | 272 | +| 7.2.5 | Test Requirements..... | 273 | +| 7.2.5.1 | General..... | 273 | +| 7.2.5.2 | UTRA FDD Test Requirements..... | 273 | +| 7.2.5.3 | UTRA TDD 1,28Mcp option Test Requirements..... | 273 | +| 7.2.5.4 | E-UTRA Test Requirements..... | 273 | +| 7.2.5.5 | NR Test Requirements..... | 274 | +| 7.3 | OTA Reference sensitivity level..... | 274 | +| 7.3.1 | Definition and applicability..... | 274 | +| 7.3.2 | Minimum Requirement..... | 275 | +| 7.3.3 | Test purpose..... | 275 | +| 7.3.4 | Method of test..... | 275 | +| 7.3.4.1 | Initial conditions..... | 275 | +| 7.3.4.2 | Procedure..... | 275 | +| 7.3.5 | Test Requirement..... | 276 | +| 7.3.5.1 | General..... | 276 | +| 7.3.5.2 | UTRA FDD Test Requirements..... | 276 | +| 7.3.5.3 | E-UTRA Test Requirements..... | 276 | +| 7.3.5.4 | NR Test Requirements..... | 277 | +| 7.4 | OTA Dynamic range..... | 279 | + +| | | | +|-----------|----------------------------------------------------------------------------------|-----| +| 7.4.1 | Definition and applicability..... | 279 | +| 7.4.2 | Minimum Requirement..... | 279 | +| 7.4.3 | Test purpose..... | 279 | +| 7.4.4 | Method of test..... | 279 | +| 7.4.4.1 | Initial conditions..... | 279 | +| 7.4.4.2 | Procedure..... | 280 | +| 7.4.5 | Test Requirement..... | 280 | +| 7.4.5.1 | UTRA FDD operation..... | 280 | +| 7.4.5.2 | E-UTRA operation..... | 281 | +| 7.4.5.3 | NR operation..... | 283 | +| 7.5 | OTA Adjacent channel selectivity, general blocking, and narrowband blocking..... | 292 | +| 7.5.1 | Definition and applicability..... | 292 | +| 7.5.2 | Minimum Requirement..... | 292 | +| 7.5.3 | Test purpose..... | 292 | +| 7.5.4 | Method of test..... | 292 | +| 7.5.4.1 | Initial conditions..... | 292 | +| 7.5.4.2 | Procedure..... | 293 | +| 7.5.4.2.1 | General procedure..... | 293 | +| 7.5.4.2.2 | MSR operation..... | 293 | +| 7.5.4.2.3 | Single RAT UTRA FDD operation..... | 294 | +| 7.5.4.2.4 | Single RAT E-UTRA operation..... | 294 | +| 7.5.5 | Test Requirement..... | 295 | +| 7.5.5.1 | MSR operation..... | 295 | +| 7.5.5.1.1 | General blocking test requirement..... | 295 | +| 7.5.5.1.2 | General narrowband blocking test requirement..... | 296 | +| 7.5.5.1.3 | Additional BC3 blocking test requirement..... | 297 | +| 7.5.5.2 | Single RAT UTRA FDD operation..... | 298 | +| 7.5.5.3 | Single RAT E-UTRA operation..... | 299 | +| 7.6 | OTA Blocking..... | 302 | +| 7.6.1 | General..... | 302 | +| 7.6.2 | General Requirement..... | 302 | +| 7.6.2.1 | Definition and applicability..... | 302 | +| 7.6.2.2 | Minimum Requirement..... | 302 | +| 7.6.2.3 | Test purpose..... | 302 | +| 7.6.2.4 | Method of test..... | 302 | +| 7.6.2.4.1 | Initial conditions..... | 302 | +| 7.6.2.4.2 | Procedure..... | 303 | +| 7.6.2.5 | Test Requirement..... | 304 | +| 7.6.2.5.1 | MSR operation..... | 304 | +| 7.6.2.5.2 | Single RAT UTRA FDD operation..... | 305 | +| 7.6.2.5.3 | Single RAT E-UTRA operation..... | 306 | +| 7.6.3 | Co-location Requirement..... | 308 | +| 7.6.3.1 | Definition and applicability..... | 308 | +| 7.6.3.2 | Minimum Requirement..... | 308 | +| 7.6.3.3 | Test purpose..... | 308 | +| 7.6.3.4 | Method of test..... | 308 | +| 7.6.3.4.1 | Initial conditions..... | 308 | +| 7.6.3.4.2 | Procedure..... | 308 | +| 7.6.3.5 | Test Requirement..... | 309 | +| 7.6.3.5.1 | MSR operation..... | 309 | +| 7.6.3.5.2 | Single RAT UTRA FDD operation..... | 314 | +| 7.6.3.5.3 | Single RAT E-UTRA operation..... | 319 | +| 7.7 | OTA Receiver spurious emissions..... | 324 | +| 7.7.1 | Definition and applicability..... | 324 | +| 7.7.2 | Minimum Requirement..... | 324 | +| 7.7.3 | Test purpose..... | 325 | +| 7.7.4 | Method of test..... | 325 | +| 7.7.4.1 | Initial conditions..... | 325 | +| 7.7.4.2 | Procedure..... | 325 | +| 7.7.5 | Test Requirement..... | 326 | +| 7.8 | OTA Receiver intermodulation..... | 326 | + +| | | | +|-----------|----------------------------------------------------------|-----| +| 7.8.1 | Definition and applicability..... | 326 | +| 7.8.2 | Minimum Requirement..... | 326 | +| 7.8.3 | Test purpose..... | 327 | +| 7.8.4 | Method of test..... | 327 | +| 7.8.4.1 | Initial conditions..... | 327 | +| 7.8.4.2 | Procedure..... | 327 | +| 7.8.4.2.1 | General procedure..... | 327 | +| 7.8.4.2.2 | MSR operation..... | 327 | +| 7.8.4.2.3 | Single RAT UTRA FDD operation..... | 328 | +| 7.8.4.2.4 | Single RAT E-UTRA operation..... | 328 | +| 7.8.5 | Test Requirement..... | 328 | +| 7.8.5.1 | MSR operation..... | 328 | +| 7.8.5.1.1 | General intermodulation test requirement..... | 328 | +| 7.8.5.1.2 | General narrowband intermodulation test requirement..... | 330 | +| 7.8.5.2 | Single RAT UTRA operation..... | 334 | +| 7.8.5.3 | Single RAT E- UTRA operation..... | 336 | +| 7.9 | OTA In-channel selectivity..... | 340 | +| 7.9.1 | Definition and applicability..... | 340 | +| 7.9.2 | Minimum Requirement..... | 340 | +| 7.9.3 | Test purpose..... | 341 | +| 7.9.4 | Method of test..... | 341 | +| 7.9.4.1 | Initial conditions..... | 341 | +| 7.9.4.2 | Procedure..... | 341 | +| 7.9.5 | Test Requirement..... | 342 | +| 7.9.5.1 | E-UTRA test requirement..... | 342 | +| 7.9.5.2 | NR test requirement..... | 343 | +| 8 | Radiated performance requirements..... | 346 | +| 8.1 | General..... | 346 | +| 8.1.1 | OTA demodulation branches..... | 347 | +| 8.2 | Radiated performance requirements for MSR..... | 347 | +| 8.3 | Radiated performance requirements for UTRA FDD..... | 347 | +| 8.3.1 | General..... | 347 | +| 8.3.2 | Definitions and applicability..... | 348 | +| 8.3.3 | Minimum requirements..... | 349 | +| 8.3.4 | Test purposes..... | 349 | +| 8.3.5 | Method of test..... | 349 | +| 8.3.5.1 | Initial conditions..... | 349 | +| 8.3.5.2 | Procedure..... | 349 | +| 8.3.6 | Test requirements..... | 350 | +| 8.4 | Radiated performance requirements for E-UTRA..... | 351 | +| 8.4.1 | General..... | 351 | +| 8.4.2 | Definitions and applicability..... | 352 | +| 8.4.3 | Minimum requirements..... | 352 | +| 8.4.4 | Test purposes..... | 352 | +| 8.4.5 | Method of test..... | 353 | +| 8.4.5.1 | Initial conditions..... | 353 | +| 8.4.5.2 | Procedure..... | 353 | +| 8.4.6 | Test requirements..... | 354 | +| 8.5 | Radiated performance requirements for NR..... | 354 | +| 8.5.1 | General..... | 354 | +| 8.5.2 | Definitions and applicability..... | 355 | +| 8.5.3 | Minimum requirements..... | 355 | +| 8.5.4 | Test purposes..... | 356 | +| 8.5.5 | Method of test..... | 356 | +| 8.5.5.1 | Initial conditions..... | 356 | +| 8.5.5.2 | Procedure..... | 356 | +| 8.5.6 | Test requirements..... | 357 | + +| | | +|--------------------------------------------------------------------------------------------------------------------|------------| +| Annex A (normative): Test system characterization..... | 358 | +| Annex B (normative): Calibration..... | 359 | +| Annex C (informative): Test tolerances and derivation of test requirements..... | 360 | +| C.1 General..... | 360 | +| C.2 Measurement of transmitter (OTA)..... | 361 | +| C.3 Measurement of receiver (OTA)..... | 363 | +| Annex D (informative): Test system set-up..... | 364 | +| D.1 Transmitter..... | 364 | +| D.1.1 Radiated Transmit Power, OTA E-UTRA DL RS power, output power dynamics and Transmitter signal quality..... | 364 | +| D.1.2 OTA Base Station output power, ACLR, OTA spectrum emissions mask, OTA operating band unwanted emissions..... | 365 | +| D.1.3 OTA spurious emissions..... | 365 | +| D.1.4 OTA Co-location emissions, TX OFF power..... | 366 | +| D.1.5 OTA Transmitter Intermodulation..... | 366 | +| D.2 Receiver..... | 367 | +| D.2.1 OTA sensitivity and OTA Reference sensitivity..... | 367 | +| D.2.2 OTA Dynamic range..... | 367 | +| D.2.3 OTA Adjacent channel selectivity, general blocking, and narrowband blocking..... | 368 | +| D.2.4 OTA Blocking..... | 369 | +| D.2.5 OTA Receiver spurious emissions..... | 370 | +| D.2.6 OTA Receiver intermodulation..... | 370 | +| D.2.7 OTA In-channel selectivity..... | 371 | +| D.3 Performance requirements..... | 372 | +| Annex E (normative): Estimation of Measurement Uncertainty..... | 373 | +| E.1 General..... | 373 | +| E.2 Measurement methodology descriptions..... | 373 | +| E.3 Measurement uncertainty budget format..... | 373 | +| E.4 Measurement uncertainty budgets..... | 373 | +| E.5 Measurement error contribution descriptions..... | 373 | +| Annex F (normative): TRP measurement grids..... | 374 | +| F.1 General..... | 374 | +| F.2 Spherical equal angle grid..... | 374 | +| F.2.1 General..... | 374 | +| F.2.2 Reference angular step criteria..... | 374 | +| F.3 Spherical equal area grid..... | 376 | +| F.4 Spherical Fibonacci grid..... | 377 | +| F.5 Orthogonal cut grid..... | 377 | +| F.5.1 General..... | 377 | +| F.5.2 Operating band unwanted emissions..... | 378 | +| F.5.3 Spurious unwanted emissions..... | 378 | + +| | | | +|----------------------------------------------------------------------------------|----------------------------------------------------|------------| +| F.6 | Wave vector space grid..... | 379 | +| F.7 | Orthogonal 2 cuts with pattern multiplication..... | 379 | +| F.8 | Void..... | 379 | +| F.9 | Full sphere with sparse sampling..... | 379 | +| F.10 | Beam-based directions..... | 380 | +| F.11 | Peak method..... | 380 | +| F.12 | Equal sector with peak average..... | 380 | +| F.13 | Pre-scan..... | 381 | +| Annex G (normative): Environmental requirements for the BS equipment..... | | 382 | +| G.1 | General..... | 382 | +| G.2 | Normal test environment..... | 382 | +| G.3 | Extreme test environment..... | 382 | +| G.3.1 | General..... | 382 | +| G.3.2 | Extreme temperature..... | 383 | +| G.4 | Vibration..... | 383 | +| G.5 | Power supply..... | 383 | +| G.6 | Measurement of test environments..... | 383 | +| G.7 | OTA extreme test methods..... | 384 | +| G.7.1 | Direct far field method..... | 384 | +| G.7.2 | Relative method..... | 384 | +| Annex H (informative): Measuring noise close to noise-floor..... | | 386 | +| Annex I (informative): Change history..... | | 387 | + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document specifies radiated test methods and conformance requirements for 2 types of AAS BS; *hybrid requirements set* which specify requirements for a *hybrid AAS BS* with both a conducted and a radiated interface and *OTA requirements set* which specify requirements for an *OTA AAS BS* which has a radiated interface only. + +The *hybrid AAS BS* requirements are specified for E-UTRA AAS Base Station (BS), the FDD mode of UTRA AAS Base Station (BS), the 1,28 Mcps TDD mode of UTRA AAS Base Station (BS) in single RAT and any MSR AAS Base Station (BS) implementation of these RATs including NR operation. + +The *OTA AAS BS* requirements are specified for E-UTRA AAS Base Station (BS), the FDD mode of UTRA AAS Base Station (BS), in single RAT and any MSR AAS Base Station (BS) implementation of these RATs and/or NR. + +The requirements have been derived from, and are consistent with non-AAS BS specifications in TS 25.104 [2], TS 25.105 [3], TS 36.104 [4] or TS 37.104 [5] and where applicable with the NR specification TS 38.104 [33]. The technical specification TS 37.145 is in 2 parts, part TS 37.145-1 [9] covers conducted requirements and part TS 37.145-2 (the present document) covers radiated requirements. + +The present document does not establish radiated test methods and conformance requirements for Band 46 operation as it is not supported by AAS BS. Conducted Band 46 test requirements are still applicable for AAS BS for protection of and against Band 46 operation, as specified in TS 37.145-1 [9]. + +The present document does not establish minimum RF characteristics or minimum performance requirements for Narrow-Band Internet of Things (NB-IoT) in band, NB-IoT guard band, or standalone NB-IoT operation, for AAS BS in *single RAT E-UTRA operation* or in *MSR operation* using E-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 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)". +- [3] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD)". +- [4] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". +- [5] 3GPP TS 37.104: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception". +- [6] 3GPP TS 37.105: "Active Antenna System (AAS) Base Station (BS) transmission and reception". +- [7] Void +- [8] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [9] 3GPP TS 37.145-1: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 1: Conducted conformance testing". +- [10] 3GPP TS 25.141: "Base Station (BS) conformance testing (FDD)". + +- [11] 3GPP TS 25.142: "Base Station (BS) conformance testing (TDD)". +- [12] 3GPP TS 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing". +- [13] 3GPP TS 37.141: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing". +- [14] Recommendation ITU-R M.328: "Spectra and bandwidth of emissions". +- [15] 3GPP TS 25.331 (V14.3.0): "Radio Resource Control (RRC); Protocol specification (Release 14)". +- [16] Recommendation ITU-R SM.329-10: "Unwanted emissions in the spurious domain". +- [17] FCC publication number 662911: "Emissions Testing of Transmitters with Multiple Outputs in the Same Band" +- [18] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission +- [19] CEPT ECC Decision (13)03, "The harmonised use of the frequency band 1452-1492 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL)". +- [20] IEC 60721: "Classification of environmental conditions" +- [21] IEC 60721-3-3: "Classification of environmental conditions - Part 3-3: Classification of groups of environmental parameters and their severities - Stationary use at weather protected locations" +- [22] IEC 60721-3-4: "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations" +- [23] ETSI EN 300 019-1-3: "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-3: Classification of environmental conditions; Stationary use at weatherprotected locations" +- [24] ETSI EN 300 019-1-4: "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1-4: Classification of environmental conditions; Stationary use at non-weatherprotected locations" +- [25] IEC 60068-2-1 (2007): "Environmental testing - Part 2: Tests. Tests A: Cold" +- [26] IEC 60068-2-2 (2007): "Environmental testing - Part 2: Tests. Tests B: Dry heat" +- [27] IEC 60068-2-6 (2007): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)" +- [28] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation" +- [29] Void +- [30] Recommendation ITU-T O.153: "Basic parameters for the measurement of error performance at bit rates below the primary rate" +- [31] 3GPP TR 25.942: "Radio Frequency (RF) system scenarios". +- [32] 3GPP TS 45.004: "Digital cellular telecommunications system (Phase 2+); Modulation". +- [33] 3GPP TS 38.104: "NR Base Station (BS) radio transmission and reception". +- [34] 3GPP TS 38.141-2: "Base Station (BS) conformance testing Part 2: Radiated conformance testing". +- [35] 3GPP TS 38.141-1: "NR;Base Station (BS) conformance testing; Part 1: Conducted conformance testing". +- [36] 3GPP TS 38.211: "NR; Physical channels and modulation". + +- [37] 3GPP TS 38.104 (V15.6.0): "NR Base Station (BS) radio transmission and reception (Release 15)". +- [38] 3GPP TR 37.941: "Radio Frequency (RF) conformance testing background for radiated Base Station (BS) requirements". + +--- + +## 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]. + +**AAS BS receiver:** composite receiver function of an AAS BS receiving in an operating band + +**active antenna system base station:** base station system which combines an Antenna Array with an Active transceiver unit array and a *Radio Distribution Network* + +**band category:** group of operating bands for which the same MSR scenarios apply + +**Base Station RF Bandwidth:** bandwidth in which a base station transmits and/or receives single or multiple carrier(s) and/or RATs simultaneously within a supported operating band + +NOTE 1: In single carrier operation, the *Base Station RF Bandwidth* is equal to the channel bandwidth. + +**Base Station RF Bandwidth edge:** frequency of one of the edges of the *Base Station RF Bandwidth* + +**beam:** main lobe of a radiation pattern from an AAS BS + +NOTE 2: For certain AAS antenna array, there may be more than one beam. + +**beam centre direction:** direction equal to the geometric centre of the -3 dB EIRP contour of the beam + +**beam direction pair:** data set consisting of the *beam centre direction* and the related *beam peak direction* + +**beam peak direction:** direction where the maximum EIRP is supposed to be found + +**beamwidth:** angles describing the major and minor axes of an ellipsoid closest fit to an essentially elliptic half-power contour of a beam + +**carrier:** modulated waveform conveying the physical channels + +**carrier aggregation:** aggregation of two or more NR or E-UTRA component carriers in order to support wider *transmission bandwidths* + +**channel bandwidth:** RF bandwidth supporting a single RF carrier with the *transmission bandwidth* configured in the uplink or downlink of a cell + +NOTE 3: The *channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE 4: For UTRA FDD, the *channel bandwidth* is the nominal channel spacing specified in TS 25.104 [2]. For UTRA TDD 1,28 Mcps, the *channel bandwidth* is the nominal channel spacing specified in TS 25.105 [3]. + +NOTE 5: For E-UTRA, the *channel bandwidths* are specified in TS 36.104 [4]. + +NOTE 6: In TS 38.104 [33] for NR, *channel bandwidths* are referred to as BS channel bandwidths, since for NR BS and UE channel bandwidths may differ. + +**channel edge:** lowest or highest frequency of the NR carrier, separated by the *BS channel bandwidth* + +**contiguous spectrum:** spectrum consisting of a contiguous block of spectrum with no *sub-block gap(s)* + +**demodulation branch:** single input of the *AAS BS receiver* to the demodulation algorithms + +NOTE 7: For UTRA FDD, *non-AAS BS* a *demodulation branch* is referred to as a receive diversity branch or an UL MIMO branch. For E-UTRA *non-AAS BS* a *demodulation branch* is referred to as an RX antenna in the performance requirement tables. + +NOTE 8: The term "RX antenna" in clause 8 (i.e. Performance requirements) of the E-UTRA specification TS 36.104 [4] does not refer to physical receiver antennas. + +**co-location reference antenna:** a passive antenna used as reference for base station to base station co-location requirements + +**contiguous spectrum:** spectrum consisting of a contiguous block of spectrum with no *sub-block gap(s)* + +**downlink operating band:** part of the (FDD) operating band designated for downlink + +**equivalent isotropic radiated power:** equivalent power radiated from an isotropic directivity device producing the same field intensity at a point of observation as the field intensity radiated in the direction of the same point of observation by the discussed device + +NOTE 9: Isotropic directivity is equal in all directions (0 dBi). + +**equivalent isotropic sensitivity:** sensitivity for an isotropic directivity device equivalent to the sensitivity of the discussed device exposed to an incoming wave from a defined AoA + +NOTE 10: The sensitivity is the minimum received power level at which a RAT specific requirement is met. + +NOTE 11: Isotropic directivity is equal in all directions (0 dBi). + +**fractional bandwidth:** fractional bandwidth FBW is defined as + +**highest carrier:** the carrier with the highest carrier frequency transmitted/received in a specified frequency band + +**hybrid AAS BS:** AAS BS which has both a conducted RF interface and a radiated RF interface in the far field and conforms to a *hybrid requirements set* + +NOTE 12: For NR operation, a *hybrid AAS BS* corresponds to NR *type 1-H* in [34]. + +**hybrid requirements set:** complete set of requirements applied to a *hybrid AAS BS* with both conducted and radiated requirements + +**inter-band carrier aggregation:** carrier aggregation of component carriers in different operating bands + +NOTE 13: Carriers aggregated in each band can be contiguous or non-contiguous. + +**intra-band contiguous carrier aggregation:** *contiguous carriers* aggregated in the same operating band + +**intra-band non-contiguous carrier aggregation:** non-contiguous carriers aggregated in the same operating band + +**Inter RF Bandwidth gap:** frequency gap between two consecutive *Base Station RF Bandwidths* that are placed within two supported operating bands + +**maximum carrier TRP:** mean power level measured per RIB during the *transmitter ON period* for a specific carrier in a specified reference condition and corresponding to the declared *rated carrier TRP* ( $P_{\text{rated,c,TRP}}$ ) + +**maximum transmitter TRP:** mean power level measured per RIB during the *transmitter ON period* in a specified reference condition and corresponding to the declared *rated transmitter TRP* ( $P_{\text{rated,t,TRP}}$ ) + +**minSENS:** the lowest declared EIS value for the OSDD's declared for OTA sensitivity requirement. + +**minSENS RoAoA:** the *reference RoAoA* associated with the OSDD with the lowest declared EIS value. + +**MSR operation:** operation of AAS BS declared to be MSR in particular *operating band(s)* + +**multi-band RIB:** *operating band* specific RIB which is paired with one or more additional *operating band* specific RIBs where the multiple bands are supported through common active electronic component(s) + +**non-AAS BS:** BS conforming to one of the RF requirement specifications TS 25.104 [2], TS 25.105 [3], TS 36.104 [4] or TS 37.104 [5] + +**non-contiguous spectrum:** spectrum consisting of two or more *sub-blocks* separated by *sub-block gap(s)* + +**operating band:** frequency range in which the AAS BS operates (paired or unpaired), that is defined with a specific set of technical requirements + +**OTA AAS BS:** AAS BS which has $\geq 8$ *transceiver units* for E-UTRA or MSR and $\geq 4$ *transceiver units* for UTRA per cell and has a radiated RF interface only and conforms to the *OTA requirements set*. + +NOTE 14: For NR operation, an *OTA AAS BS* corresponds to an NR *type I-O BS* in [34]. + +**OTA coverage range:** a common range of directions within which TX OTA requirements that are neither specified in the *OTA peak directions sets* nor as *TRP requirement* are intended to be met + +**OTA coverage range:** a common range of directions within which TX OTA requirements that are neither specified in the *OTA peak directions sets* nor as *TRP requirement* are intended to be met + +**OTA peak directions set:** set(s) of *beam peak directions* within which certain TX OTA requirements are intended to be met, where all *OTA peak directions set(s)* are subsets of the *OTA coverage range* + +NOTE 15: The *beam peak directions* are related to a corresponding contiguous range or discrete list of *beam centre directions* by the *beam direction pairs* included in the set. + +NOTE 16: *OTA peak directions set* definition (applicable to multiple *directional requirements*) is replacing the Rel-13/14 *EIRP accuracy directions set* definition (which was applicable to EIRP requirement only). + +**OTA REFSSENS RoAoA:** Is the RoAoA determined by the contour defined by the points at which the achieved EIS is 3dB higher than the achieved EIS in the reference direction assuming that for any AoA, the receiver gain is optimized for that AoA. + +NOTE 17: This contour will be related to the average element/sub-array radiation pattern 3dB beam width. + +**OTA requirements set:** complete set of OTA requirements applied to an *OTA AAS BS*. + +**OTA sensitivity directions declaration:** set of manufacturer declarations comprising one or more EIS values (with related RAT and *channel bandwidth*), and the directions where it (they) applies + +NOTE 18: All the directions apply to all the EIS values in an OSDD. + +**polarization match:** condition that exists when a plane wave, incident upon an antenna from a given direction, has a polarization that is the same as the receiving polarization of the antenna in that direction + +**radiated interface boundary:** *operating band* specific radiated requirements reference where the radiated requirements apply. + +NOTE 19: For requirements based on EIRP/EIS, the radiated interface boundary is associated to the far-field region. + +**Radio Bandwidth:** frequency difference between the upper edge of the highest used carrier and the lower edge of the lowest used carrier. + +**radio distribution network:** passive network which distributes radio signals generated by the transceiver unit array to the antenna array, and/or distributes the radio signals collected by the antenna array to the transceiver unit array + +NOTE 20: In the case when the active transceiver units are physically integrated with the array elements of the antenna array, the radio distribution network is a one-to-one mapping. + +**rated beam EIRP:** EIRP that is declared as being achieved in the *beam peak direction* associated with a particular *beam direction pair* + +**rated carrier TRP:** mean power level declared by the manufacturer per carrier, for BS operating in single carrier, multi-carrier, or carrier aggregation configurations that the manufacturer has declared to be available at the RIB during the *transmitter ON period* + +**rated transmitter TRP:** mean power level declared by the manufacturer to be available at the RIB during the *transmitter ON period* + +**receiver target:** angles of arrival in which reception is performed + +**receiver target redirection range:** union of all the *sensitivity RoAoA* achievable through redirecting the *receiver target* related to the OSDD + +**receiver target reference direction:** direction inside the *receiver target redirection range* declared by the manufacturer for conformance testing. + +NOTE 21 For an OSDD without *receiver target redirection range*, this is a direction inside the *sensitivity RoAoA*. + +**reference beam direction:** declared *beam direction pair*, including reference *beam centre direction* and reference *beam peak direction* where the reference *beam peak direction* is the direction for the intended maximum EIRP within the EIRP accuracy compliance directions set + +**reference beam direction pair:** declared *beam direction pair*, including reference *beam centre direction* and reference *beam peak direction* where the reference *beam peak direction* is the direction for the intended maximum EIRP within the *OTA peak directions set* + +**reference RoAoA:** the *sensitivity RoAoA* associated with the *receiver target reference direction* for each OSDD. + +**sensitivity RoAoA:** RoAoA within which the declared EIS(s) of an OSDD is intended to be achieved at any instance of time for a specific AAS BS direction setting + +**single-band RIB:** *operating band* specific RIB without any common active electronic component(s) shared with other *operating bands* + +**single RAT E-UTRA operation:** operation of AAS BS declared to be single RAT E-UTRA in the *operating band* + +NOTE 22: *Single RAT E-UTRA operation* does not cover in-band NB-IoT, nor guardband NB-IoT operation. + +**single RAT UTRA operation:** operation of AAS BS declared to be single RAT UTRA in the *operating band* + +**sTTI:** A transmission time interval (TTI) of either one slot or one subslot as defined in TS 36.211 [38] on either uplink or downlink. + +**sub-block:** one contiguous allocated block of spectrum for use by the same Base Station + +NOTE 23 There may be multiple instances of *sub-blocks* within a *Base Station RF Bandwidth*. + +**sub-block gap:** frequency gap between two consecutive *sub-blocks* within an *Base Station RF Bandwidth*, where the RF requirements in the gap are based on co-existence for un-coordinated operation + +**Synchronized operation:** Operation of TDD in two different systems, where no simultaneous uplink and downlink occur. + +**TAB connector:** transceiver array boundary connector + +**throughput:** number of payload bits successfully received per second for a reference measurement channel in a specified reference condition + +**total radiated power:** is the total power radiated by the antenna. + +NOTE 24: The *total radiated power* is the power radiating in all direction for two orthogonal polarizations. + +NOTE 25: *total radiated power* is defined in both the near-field region and the far-field region. + +**total RF bandwidth:** maximum sum of Base Station RF Bandwidths in all supported *operating bands* + +**transceiver array boundary:** conducted interface between the transceiver unit array and the composite antenna + +**transmission bandwidth:** bandwidth of an instantaneous E-UTRA transmission from a UE or BS, measured in Resource Block units + +**Unsynchronized operation:** Operation of TDD in two different systems, where the conditions for synchronized operation are not met. + +**uplink operating band:** part of the (FDD) operating band designated for uplink + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\beta$ | Percentage of the mean transmitted power emitted outside the occupied bandwidth on the assigned channel | +| $BeW_{\theta}$ | The Beam width in $\theta$ | +| $BeW_{\phi}$ | The Beam width in $\phi$ | +| $BeW_{\theta,REFSENS}$ | The beamwidth equivalent to the OTA REFSENS RoAoA in the $\theta$ -axis in degrees. | +| $BeW_{\phi,REFSENS}$ | The beamwidth equivalent to the OTA REFSENS RoAoA in the $\phi$ -axis in degrees. | +| $BW_{Channel}$ | Channel bandwidth (for E-UTRA or NR) | +| $BW_{Channel\_CA}$ | Aggregated channel bandwidth, expressed in MHz. $BW_{Channel\_CA} = F_{edge\_high} - F_{edge\_low}$ . | +| $BW_{Config}$ | Transmission bandwidth configuration (for E-UTRA), expressed in MHz, where $BW_{Config} = N_{RB} \times 180$ kHz in the uplink and $BW_{Config} = 15$ kHz + $N_{RB} \times 180$ kHz in the downlink. | +| $BW_{tot}$ | Total RF bandwidth | +| $DwPTS$ | Downlink part of the special subframe (for E-UTRA TDD) operation | +| $E_b$ | Average energy per information bit (for UTRA) | +| $f$ | Frequency | +| $\Delta f$ | Separation between the Base Station RF bandwidth edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency | +| $\Delta f_{max}$ | The largest value of $\Delta f$ used for defining the requirement | +| $\Delta f_{OBUE}$ | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| $\Delta f_{OOB}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $\Delta_{minSENS}$ | Difference between conducted reference sensitivity and EIS minSENS | +| $\Delta_{OTAREFSENS}$ | Difference between conducted reference sensitivity and OTA REFSENS | +| $\Delta_{sample}$ | The difference between the nominal and extreme power measurements dueing extreme EIRP testing, $P_{max,sample,nom} - P_{max,sample,ex}$ | +| $EIS_{minSENS}$ | The EIS declared for the minSENS RoAoA | +| $F_C$ | Carrier centre frequency | +| $F_{filter}$ | Filter centre frequency | +| $f\_offset$ | Separation between the Base Station RF bandwidth edge frequency and the centre of the measuring filter | +| $f\_offset_{max}$ | The maximum value of $f\_offset$ used for defining the requirement | +| $F_{BW\_RF,high}$ | Upper RF bandwidth edge, where $F_{BW\_RF,high} = F_{C,high} + F_{offset, RAT}$ | +| $F_{BW\_RF,low}$ | Lower RF bandwidth edge, where $F_{BW\_RF,low} = F_{C,low} - F_{offset, RAT}$ | +| $F_C$ | RF reference frequency on the channel raster | +| $F_{C,high}$ | Centre frequency of the highest transmitted/received carrier. | +| $F_{C,low}$ | Centre frequency of the lowest transmitted/received carrier. | +| $F_{DL\_low}$ | The lowest frequency of the downlink operating band | +| $F_{DL\_high}$ | The highest frequency of the downlink operating band | +| $F_{edge\_low}$ | The lower edge of aggregated channel bandwidth, expressed in MHz. $F_{edge\_low} = F_{C,low} - F_{offset, RAT}$ . | +| $F_{edge\_high}$ | The upper edge of aggregated channel bandwidth, expressed in MHz. $F_{edge\_high} = F_{C,high} + F_{offset, RAT}$ . | +| $F_{offset, RAT}$ | Frequency offset from the centre frequency of the highest transmitted/received carrier to the upper RF bandwidth edge, sub-block edge or inter-RF bandwidth edge, or from the centre frequency of the lowest transmitted/received carrier to the lower RF bandwidth edge, sub-block edge or inter-RF bandwidth edge for a specific RAT. | +| $F_{FBWhigh}$ | Highest supported frequency within supported operating band, for which fractional bandwidth support was declared | +| $F_{FBWlow}$ | Lowest supported frequency within supported operating band, for which fractional bandwidth support was declared | +| $F_{UL\_low}$ | The lowest frequency of the uplink operating band | +| $F_{UL\_high}$ | The highest frequency of the uplink operating band | +| $F_{uw}$ | Frequency offset of unwanted signal | + +| | | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $N_{\text{cells}}$ | The declared number corresponding to the minimum number of cells that can be transmitted by an AAS BS in a particular band with transmission on all transceiver units supporting the operating band | +| $N_0$ | Total one-sided noise power spectral density due to all noise sources (for UTRA) | +| $N_{\text{RXU,active}}$ | The number of active receiver units. The same as the number of demodulation branches to which compliance is declared for chapter 8 performance requirements | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in units of resource blocks (for E-UTRA) | +| $P_{\text{max,c,EIRP}}$ | The maximum carrier EIRP when the AAS BS is configured at the rated carrier TRP ( $P_{\text{rated,c,TRP}}$ ) | +| $P_{\text{max,c,EIRP, extreme}}$ | The maximum carrier EIRP when the AAS BS is configured at the rated carrier TRP ( $P_{\text{rated,c,TRP}}$ ) under extreme conditions, either measured directly or calculated. | +| $P_{\text{max,c,TRP}}$ | The maximum carrier TRP per cell | +| $P_{\text{max,sample,nom}}$ | The measured sample power in extreme conditionals chamber when the AAS BS is configured at the rated carrier TRP ( $P_{\text{rated,c,TRP}}$ ), under nominal conditions. | +| $P_{\text{max,sample,ext}}$ | The measured sample power in extreme conditionals chamber when the AAS BS is configured at the rated carrier TRP ( $P_{\text{rated,c,TRP}}$ ), under extreme conditions. $P_{\text{max,t,TRP}}$ , the maximum total output power per cell | +| $P_{\text{rated,c,EIRP}}$ | The rated carrier EIRP when the AAS BS is configured at the rated carrier TRP ( $P_{\text{rated,c,TRP}}$ ) | +| $P_{\text{rated,c,FBIhigh}}$ | The rated carrier EIRP for the higher supported frequency range within supported operating band , for which fractional bandwidth support was declared | +| $P_{\text{rated,c,FBIlow}}$ | The rated carrier EIRP for the lower supported frequency range within supported operating band , for which fractional bandwidth support was declared | +| $P_{\text{rated,c,TRP}}$ | The rated carrier TRP | +| $P_{\text{rated,t,TRP}}$ | Rated transmitter TRP declared per RIB | +| $W_{\text{gap}}$ | Sub-block gap size or Inter RF Bandwidth gap size | +| $\theta$ | The angle in the reference coordinate system between the projection of the x/y plane and the radiation vector defined between $-90^\circ$ and $90^\circ$ . $0^\circ$ represents the direction perpendicular to the y/z plane. The angle is aligned with the down-tilt angle. | +| $\phi$ | The angle in the reference coordinate system between the x-axis and the projection of the radiation vector onto the x/y plane defined between $-180^\circ$ and $180^\circ$ . | +| $P_{\text{REFSENS}}$ | Conducted reference Sensitivity power level | +| $\text{TRP}_{\text{Estimate}}$ | Numerically approximated TRP | + +![Figure 3.2-1: Illustration of RF bandwidth related symbols and definitions for Multi-standard Radio. The diagram shows a frequency axis with two main regions: RAT_low (orange) and RAT_high (green), separated by 'Multiple carriers / RATs' (blue). The total RF bandwidth is labeled BW_RF. The lower bound of the RF bandwidth is F_BW_RF_low, and the upper bound is F_BW_RF_high. The center frequency of the RAT_low region is F_C_low, and the center frequency of the RAT_high region is F_C_high. The offset from the center frequency to the lower bound is F_offset_RAT_low, and the offset from the center frequency to the upper bound is F_offset_RAT_high.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +The diagram illustrates the RF bandwidth configuration for a Multi-standard Radio (MSR). It shows a horizontal frequency axis with two primary operating regions: **RAT\_low** (orange) and **RAT\_high** (green). Between these two regions are **Multiple carriers / RATs** (blue). The total RF bandwidth is indicated by a bracket at the bottom as **BWRF**. The lower edge of the RF bandwidth is marked as **FBW RF,low**, and the upper edge as **FBW RF,high**. Vertical dashed lines indicate the center frequencies **FC,low** and **FC,high** for the low and high RAT regions, respectively. Horizontal double-headed arrows show the offsets **Foffset, RAT, low** and **Foffset, RAT, high** from these center frequencies to the respective RF bandwidth edges. + +Figure 3.2-1: Illustration of RF bandwidth related symbols and definitions for Multi-standard Radio. The diagram shows a frequency axis with two main regions: RAT\_low (orange) and RAT\_high (green), separated by 'Multiple carriers / RATs' (blue). The total RF bandwidth is labeled BW\_RF. The lower bound of the RF bandwidth is F\_BW\_RF\_low, and the upper bound is F\_BW\_RF\_high. The center frequency of the RAT\_low region is F\_C\_low, and the center frequency of the RAT\_high region is F\_C\_high. The offset from the center frequency to the lower bound is F\_offset\_RAT\_low, and the offset from the center frequency to the upper bound is F\_offset\_RAT\_high. + +Figure 3.2-1: Illustration of RF bandwidth related symbols and definitions for Multi-standard Radio + +![Figure 3.2-2: Illustration of RF bandwidth related symbols and definitions for non-contiguous Multi-standard Radio. The diagram shows two sub-blocks, Sub block 1 and Sub block n, separated by a gap. Each sub-block contains multiple carriers/RATs. The frequency range of Sub block 1 is from F_BW RF, low to F_BW RF, high. The frequency range of Sub block n is also from F_BW RF, low to F_BW RF, high. The frequency range of the carriers within each sub-block is from F_C block 1, low to F_C block 1, high for Sub block 1, and from F_C block n, low to F_C block n, high for Sub block n. The frequency offset between the carrier and the sub-block edge is F_offset, RAT.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates the RF bandwidth for non-contiguous Multi-standard Radio. It shows two sub-blocks, Sub block 1 and Sub block n, separated by a gap. Each sub-block contains multiple carriers/RATs. The frequency range of Sub block 1 is from $F_{BW\ RF,\ low}$ to $F_{BW\ RF,\ high}$ . The frequency range of Sub block n is also from $F_{BW\ RF,\ low}$ to $F_{BW\ RF,\ high}$ . The frequency range of the carriers within each sub-block is from $F_{C\ block\ 1,\ low}$ to $F_{C\ block\ 1,\ high}$ for Sub block 1, and from $F_{C\ block\ n,\ low}$ to $F_{C\ block\ n,\ high}$ for Sub block n. The frequency offset between the carrier and the sub-block edge is $F_{offset,\ RAT}$ . + +Figure 3.2-2: Illustration of RF bandwidth related symbols and definitions for non-contiguous Multi-standard Radio. The diagram shows two sub-blocks, Sub block 1 and Sub block n, separated by a gap. Each sub-block contains multiple carriers/RATs. The frequency range of Sub block 1 is from F\_BW RF, low to F\_BW RF, high. The frequency range of Sub block n is also from F\_BW RF, low to F\_BW RF, high. The frequency range of the carriers within each sub-block is from F\_C block 1, low to F\_C block 1, high for Sub block 1, and from F\_C block n, low to F\_C block n, high for Sub block n. The frequency offset between the carrier and the sub-block edge is F\_offset, RAT. + +**Figure 3.2-2: Illustration of RF bandwidth related symbols and definitions for non-contiguous Multi-standard Radio** + +![Figure 3.2-3: Illustration of maximum radio bandwidth and Total RF bandwidth for Multi-band Multi-standard Radio. The diagram shows two bands, Band X and Band Y, separated by an Inter RF bandwidth gap. The frequency range of Band X is from F_C band X, low to F_C band X, high. The frequency range of Band Y is from F_C band Y, low to F_C band Y, high. The frequency offset between the carrier and the band edge is F_offset, RAT. The total RF bandwidth is the sum of the RF bandwidth of Band X and the RF bandwidth of Band Y. The maximum radio bandwidth is the total RF bandwidth plus the Inter RF bandwidth gap.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +The diagram illustrates the maximum radio bandwidth and Total RF bandwidth for Multi-band Multi-standard Radio. It shows two bands, Band X and Band Y, separated by an Inter RF bandwidth gap. The frequency range of Band X is from $F_{C\ band\ X,\ low}$ to $F_{C\ band\ X,\ high}$ . The frequency range of Band Y is from $F_{C\ band\ Y,\ low}$ to $F_{C\ band\ Y,\ high}$ . The frequency offset between the carrier and the band edge is $F_{offset,\ RAT}$ . The total RF bandwidth is the sum of the RF bandwidth of Band X and the RF bandwidth of Band Y. The maximum radio bandwidth is the total RF bandwidth plus the Inter RF bandwidth gap. + +Figure 3.2-3: Illustration of maximum radio bandwidth and Total RF bandwidth for Multi-band Multi-standard Radio. The diagram shows two bands, Band X and Band Y, separated by an Inter RF bandwidth gap. The frequency range of Band X is from F\_C band X, low to F\_C band X, high. The frequency range of Band Y is from F\_C band Y, low to F\_C band Y, high. The frequency offset between the carrier and the band edge is F\_offset, RAT. The total RF bandwidth is the sum of the RF bandwidth of Band X and the RF bandwidth of Band Y. The maximum radio bandwidth is the total RF bandwidth plus the Inter RF bandwidth gap. + +**Figure 3.2-3: Illustration of maximum radio bandwidth and Total RF bandwidth for Multi-band Multi-standard Radio** + +### 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|------------------------------------| +| AAS BS | Active Antenna System Base Station | +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| AoA | Angle of Arrival | +| BC | Band Category | +| BER | Bit Error Rate | + +| | | +|---------|--------------------------------------------| +| BLER | Block Error Rate | +| CA | Carrier Aggregation | +| CACLR | Cumulative ACLR | +| CLTA | Co-Location Test Antenna | +| DTT | Digital Terrestrial Television | +| DUT | Device Under Test | +| DIP | Dominant Interferer Proportion | +| EIRP | Equivalent Isotropic Radiated Power | +| EIS | Equivalent Isotropic Sensitivity | +| FBW | Fractional Bandwidth | +| FDD | Frequency Division Duplex | +| FRC | Fixed Reference Channel | +| ICS | In-Channel Selectivity | +| ITU | International Telecommunication Union | +| ITU-R | Radio communication Sector of the ITU | +| MB-MSR | Multi-Band Multi-Standard Radio | +| MBT | Multi-Band Testing | +| MC | Multi-Carrier in a Single RAT | +| NR | New Radio | +| OBW | Occupied Band Width | +| OBUE | Operating Band Unwanted Emission | +| OSDD | OTA Sensitivity Directions Declaration | +| OTA | Over The Air | +| RAT | Radio Access Technology | +| RB | Resource Block (for E-UTRA) | +| RDN | Radio Distribution Network | +| REFSENS | Reference Sensitivity | +| RIB | Radiated Interface Boundary | +| RF | Radio Frequency | +| RoAoA | Range of Angles of Arrival | +| SBT | Single Band Testing | +| SC | Single-Carrier | +| sPDsch | shortened Physical Downlink Shared Channel | +| TAB | Transceiver Array Boundary | +| TAE | Time Alignment Error | +| TDD | Time Division Duplex | +| TRP | Total Radiated Power | +| TT | Test Tolerance | +| UE | User Equipment | + +--- + +## 4 General test conditions and declarations + +### 4.1 Measurement uncertainties and test requirements + +#### 4.1.1 General + +The requirements of this clause apply to all applicable tests in part 2 of this specification, i.e. to all AAS BS radiated tests. + +The minimum requirements for AAS BS radiated requirements are given in TS 37.105 [14] clause 9 and 10 for the radiated transmitter and radiated receiver characteristics, respectively. Test Tolerances for the radiated test requirements explicitly stated in part 2 of the present specification are given in annex C of this specification. + +Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the minimum requirements to create test requirements. + +When a test requirement differs from the corresponding minimum requirement, then the Test Tolerance applied for the test is non-zero. The Test Tolerance for the test and the explanation of how the minimum requirement has been relaxed by the Test Tolerance are given in annex C. + +**Table 4.1.1-1: Overview of radiated Tx requirements** + +| AAS BS requirement | | OTA requirement type | Coverage range | Notes | +|--------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-----------------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Base station output power | Output power accuracy for EIRP | Directional | OTA peak directions set | Output power accuracy for EIRP requirement is already included as a core requirement in TS 37.105 []. | +| | Output power accuracy for TRP | TRP | N/A | | +| E-UTRA DL RS power | | Directional | OTA peak directions set | Conformance testing is carried out in the reference direction | +| Output power dynamics | | Directional | OTA peak directions set | Conformance testing is carried out in the reference direction. | +| Transmitter OFF power | | Co-location | N/A | | +| Frequency Error | | Directional | OTA coverage range | Conformance testing is carried out in the reference direction. | +| Time Alignment Error | | Directional | OTA coverage range | Conformance testing is carried out in the reference direction. | +| Modulation Quality (EVM) | | Directional | OTA coverage range | Conformance testing is carried out in the reference direction and the maximum directions of the OTA coverage range on each axis. | +| Unwanted emissions | Occupied Bandwidth | Directional | OTA coverage range | Conformance testing is carried out in the reference direction. | +| | Adjacent Channel Leakage Ratio (ACLR) | TRP | N/A | | +| | Spectrum emission mask | TRP | N/A | | +| Spurious emissions | Mandatory Requirements | TRP | N/A | | +| | Protection of the BS receiver of own or different BS | Co-location | N/A | | +| | Additional spurious emissions requirements | TRP | N/A | Includes co-existence in same geographical area | +| | Co-location with other base stations | Co-location | N/A | | +| Transmitter intermodulation | | Co-location | N/A | The interferer is applied as a co-location requirements, the radiated emissions requirements are specified in the appropriated referenced clause, generally TRP | +| NOTE: Directional does not imply one compliance direction only. The requirement applies to a single direction at a time. | | | | | + +**Table 4.1.1-2: Overview of radiated Rx requirements** + +| AAS BS requirement | | OTA requirement type | Applicability levels | Coverage range | Number of conformance directions | +|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------|----------------------|---------------------------------------------|----------------------------------------------------------------------------------|----------------------------------| +| OTA sensitivity | | Directional | N/A | Receiver target redirection range (D10.8) | 5 | +| OTA reference sensitivity | | Directional | OTA REFSSENS | OTA REFSSENS RoAoA | 5 | +| Dynamic range | | Directional | OTA REFSSENS | OTA REFSSENS RoAoA | 1 | +| In-band selectivity and blocking | | Directional | OTA REFSSENS and minSENS | OTA REFSSENS RoAoA and minSENS RoAoA | 5 | +| ACS and narrowband blocking | | Directional | OTA REFSSENS (NB blocking only) and minSENS | OTA REFSSENS RoAoA (NB blocking only) minSENS RoAoA (NB blocking and ACS) | 5 (blocking)
1 (ACS) | +| Out-of-band blocking | Mandatory | Directional | minSENS | minSENS RoAoA | 1 | +| | Co-location with other base stations | Co-location | N/A | N/A | | +| Receiver spurious emissions | | TRP | N/A | N/A | - | +| Receiver intermodulation | | Directional | OTA REFSSENS and minSENS | OTA REFSSENS RoAoA and minSENS RoAoA | 1 | +| In-channel selectivity | | Directional | minSENS | minSENS RoAoA | 1 | +| NOTE: Directional does not imply one compliance direction only. The requirement applies to a single direction at a time. | | | | | | + +## 4.1.2 Acceptable uncertainty of Test System + +### 4.1.2.1 General + +The maximum acceptable uncertainty of the Test System is specified below for each test defined explicitly in the present specification, 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 details on measurement uncertainty budget calculation, OTA measurement methodology description (including calibration and measurement stage for each test range), MU budget format and its contributions, refer to TR 37.941 [38]. + +#### 4.1.2.2 Measurement of transmitter + +**Table 4.1.2.2-1: Maximum Test System uncertainty for transmitter tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|---------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2 Radiated transmit power (normal conditions) | ±1.1 dB, $f \leq 3.0$ GHz
±1.3 dB, $3.0$ GHz $< f \leq 4.2$ GHz | For the derivation of test system measurement uncertainty, uncertainty budget contributors as well as uncertainty budget assessment, refer to TR 37.941 [38]. | +| 6.2 Radiated transmit power (extreme conditions) | ±2.5 dB, $f \leq 3.0$ GHz
±2.6 dB, $3.0$ GHz $< f \leq 4.2$ | | +| 6.3.2 OTA maximum output power | ±1.4 dB, $f \leq 3.0$ GHz
±1.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.3.3 OTA E-UTRA DL RS power | 1.3 dB, $f \leq 3.0$ GHz
1.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.4.2 OTA UTRA inner loop power control in the downlink | 0.1 dB | | +| 6.4.3 OTA power control dynamic range | 1.1 dB | | +| 6.4.4 OTA total power dynamic range | 0.3 dB UTRA
0.4 dB E-UTRA & NR | | +| 6.4.5 OTA IPDL time mask | 0.7 dB | | +| 6.5 OTA transmit ON/OFF power | ±3.4 dB, $f \leq 3.0$ GHz
±3.6 dB, $3.0$ GHz $< f \leq 4.2$ GHz
(NOTE 1) | | +| 6.6.2 OTA frequency error | 12 Hz | | +| 6.6.3 OTA TAE | 25 ns | | +| 6.6.4 OTA modulation Quality | 1 % | | +| 6.7.2 OTA occupied bandwidth | 30 kHz: $BW_{\text{Channel}}$ 1.4 MHz, 3 MHz
100 kHz: $BW_{\text{Channel}}$ 5 MHz, 10 MHz
300 kHz: $BW_{\text{Channel}}$ 15 MHz, 20 MHz
25 MHz, 30 MHz, 40 MHz, 50 MHz
600 kHz: $BW_{\text{Channel}}$ 60 MHz, 70 MHz, 80 MHz, 90 MHz, 100 MHz | | +| 6.7.3 OTA ACLR/CACL | ±1.0 dB, $f \leq 3.0$ GHz
±1.2 dB, $3.0$ GHz $< f \leq 4.2$
Absolute limit
±2.2 dB, $f \leq 3.0$ GHz
±2.7 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.7.4 OTA spectrum emission mask | ±1.8 dB, $f \leq 3.0$ GHz
±2.0 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.7.5 OTA operating band unwanted emissions | ±1.8 dB, $f \leq 3.0$ GHz
±2.0 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.7.6.2 OTA transmitter spurious emissions, mandatory requirements | ±2.3 dB, $30$ MHz $< f \leq 6$ GHz
±4.2 dB, $6$ GHz $< f \leq 19$ GHz | | +| 6.7.6.3 OTA transmitter spurious emissions, protection of BS receiver | ±3.1 dB, $f \leq 3.0$ GHz
±3.3 dB, $3.0$ GHz $< f \leq 4.2$ GHz
(NOTE 1) | | +| 6.7.6.4 OTA transmitter spurious emissions, additional spurious emission requirements | ±2.6 dB, $f \leq 3.0$ GHz
±3.0 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 6.7.6.5 OTA transmitter spurious emissions, co-location | ±3.1 dB, $f \leq 3.0$ GHz
±3.3 dB, $3.0$ GHz $< f \leq 4.2$ GHz
(NOTE 1) | | +| 6.8 OTA transmitter intermodulation (interferer requirements) (NOTE 2) | The value below applies only to the interfering signal and is unrelated to the measurement uncertainty of the tests (6.6.1, 6.6.2 and 6.6.4) which have to be carried out in the presence of the interferer.

±3.2 dB, $f \leq 3.0$ GHz
±3.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz
(NOTE 1) | | + +- | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

NOTE 1: Fulfilling the criteria for CLTA selection and placement in clause 4.15 is deemed sufficient for the test purposes. When these criteria are met, the measurement uncertainty related to the selection of the co-location test antenna and its alignment as specified in the appropriate measurement uncertainty budget in TR 37.941 [38], shall be used for evaluating the test system uncertainty.

NOTE 2: This tolerance applies to the stimulus and not the measurements defined in clause 6.8.

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 4.1.2.3 Measurement of receiver + +**Table 4.1.2.3-1: Maximum Test System Uncertainty for receiver tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.2 OTA sensitivity | ±1.3 dB, $f \leq 3.0$ GHz
±1.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz | For the derivation of test system measurement uncertainty, uncertainty budget contributors as well as uncertainty budget assessment, refer to TR 37.941 [38]. | +| 7.3 OTA reference sensitivity | ±1.3 dB, $f \leq 3.0$ GHz
±1.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 7.4 OTA dynamic range | ±0.3 dB | | +| 7.5 OTA adjacent channel selectivity, general blocking, and narrowband blocking | ±1.7 dB, $f \leq 3.0$ GHz
±2.1 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 7.5 OTA in-band general blocking | ±1.9 dB, $f \leq 3.0$ GHz
±2.2 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 7.6.2 OTA blocking | $f_{\text{wanted}} \leq 3$ GHz
$1$ MHz $< f_{\text{interferer}} \leq 3$ GHz: ±2.0 dB
$3$ GHz $< f_{\text{interferer}} \leq 6$ GHz: ±2.1 dB
$6$ GHz $< f_{\text{interferer}} \leq 12.75$ GHz: ±3.5 dB

$3$ GHz $< f_{\text{wanted}} \leq 4.2$ GHz:
$1$ MHz $< f_{\text{interferer}} \leq 3$ GHz: ±2.0 dB
$3$ GHz $< f_{\text{interferer}} \leq 6$ GHz: ±2.1 dB
$6$ GHz $< f_{\text{interferer}} \leq 12.75$ GHz: ±3.6 dB | | +| 7.6.3 OTA co-location blocking | $f_{\text{wanted}} \leq 3.0$ GHz:
±3.4 dB, $f_{\text{interferer}} \leq 3.0$ GHz
±3.5 dB, $3.0$ GHz $< f_{\text{interferer}} \leq 4.2$ GHz

$3$ GHz $< f_{\text{wanted}} \leq 4.2$ GHz:
±3.5 dB, $f_{\text{interferer}} \leq 3.0$ GHz
±3.6 dB, $3.0$ GHz $< f_{\text{interferer}} \leq 4.2$ GHz
(NOTE 2) | | +| 7.7 OTA receiver spurious emissions | ±2.5 dB, $30$ MHz $< f \leq 6$ GHz:
dB
±4.2 dB, $6$ GHz $< f \leq 19$ GHz | | +| 7.8 OTA receiver intermodulation (general requirements) | ±2.0 dB, $f \leq 3.0$ GHz
±2.6 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 7.8 OTA receiver intermodulation (Narrowband requirements) | ±2.0 dB, $f \leq 3.0$ GHz
±2.6 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | +| 7.9 OTA in-channel selectivity | ±1.7 dB, $f \leq 3.0$ GHz
±2.1 dB, $3.0$ GHz $< f \leq 4.2$ GHz | | + +NOTE 1: Unless otherwise noted, only the Test System stimulus error is considered here. The effect of errors in the throughput measurements or the BER/FER due to finite test duration is not considered. + +NOTE 2: Fulfilling the criteria for CLTA selection and placement in clause 4.15 is deemed sufficient for the test purposes. When these criteria are met, the measurement uncertainty related to the selection of the co-location test antenna and its alignment as specified in the appropriate measurement uncertainty budget in TR 37.941 [38], shall be used for evaluating the test system uncertainty. + +#### 4.1.2.4 Measurement of performance requirement + +The measurement uncertainties for the performance requirements are the same as those quoted in TS 36.141 [12] clause 4.2.1.3 and TS 25.141 [10] clause 4.1.4. + +#### 4.1.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 Shared Risk principle. + +The Shared Risk principle is defined in Recommendation ITU-R M.1545 [8]. + +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 clause 4.1.2 of the present document. + +If the Test System for a test is known to have a measurement uncertainty greater than that specified in clause 4.1.2, 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 clause 4.1.2 shall be used to tighten the test requirement, making the test harder to pass. (For some tests e.g. receiver tests, this may require modification of stimulus signals). This procedure (defined in annex C) will ensure that a Test System not compliant with clause 4.1.2 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 clause 4.1.2 had been used. + +### 4.2 Conducted and radiated requirement reference points + +AAS BS requirements are defined for two points of reference, signified by radiated requirements (RIB) and conducted requirements (TAB). + +![Diagram of radiated and conducted points of reference of hybrid AAS BS. The diagram shows a 'Transceiver unit array' on the left and a 'Composite antenna' on the right. The 'Composite antenna' contains a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A vertical dashed line labeled 'Transceiver array boundary' separates the two. Another vertical dashed line labeled 'Radiated interface boundary' is to the right of the composite antenna. Horizontal lines connect the transceiver unit array to the RDN at points labeled #1, #2, and #K. Small squares at these connection points represent 'Transceiver array boundary connector TAB(n)'.](b81d1613e285a9353171cdc5ef97a1f0_img.jpg) + +Diagram of radiated and conducted points of reference of hybrid AAS BS. The diagram shows a 'Transceiver unit array' on the left and a 'Composite antenna' on the right. The 'Composite antenna' contains a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A vertical dashed line labeled 'Transceiver array boundary' separates the two. Another vertical dashed line labeled 'Radiated interface boundary' is to the right of the composite antenna. Horizontal lines connect the transceiver unit array to the RDN at points labeled #1, #2, and #K. Small squares at these connection points represent 'Transceiver array boundary connector TAB(n)'. + +**Figure 4.2-1: Radiated and conducted points of reference of hybrid AAS BS** + +![Diagram of Radiated points of reference of OTA AAS BS. The diagram shows a 'Transceiver unit array (TRXUA) 1 to M' on the left, connected via a horizontal line to a 'Composite antenna' on the right. The 'Composite antenna' is a dashed box containing two sub-components: 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'. A vertical dashed line to the right of the 'Antenna Array (AA)' is labeled 'Radiated interface boundary'.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Diagram of Radiated points of reference of OTA AAS BS. The diagram shows a 'Transceiver unit array (TRXUA) 1 to M' on the left, connected via a horizontal line to a 'Composite antenna' on the right. The 'Composite antenna' is a dashed box containing two sub-components: 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'. A vertical dashed line to the right of the 'Antenna Array (AA)' is labeled 'Radiated interface boundary'. + +**Figure 4.3-2: Radiated points of reference of OTA AAS BS** + +Radiated characteristics are defined over the air (OTA) at the *radiated interface boundary* (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) directions in which the OTA requirements apply are detailed for each requirement. + +Some OTA requirements are specified as co-location requirements where the requirements are specified at the conducted interface of the *co-location reference antenna*, co-location requirements are further defined in clause 4.15 + +Conducted characteristics are defined at individual or groups of *TAB connectors* at the *transceiver array boundary*, which is the conducted interface between the transceiver unit array and the composite antenna. + +The transceiver unit array is part of the composite transceiver functionality generating modulated transmit signal structures and performing receiver combining and demodulation. + +The transceiver unit array contains an implementation specific number of transmitter units and an implementation specific number of receiver units. Transmitter units and receiver units may be combined into transceiver units. The transmitter/receiver units have the ability to receive/send parallel independent modulated symbol streams. + +The composite antenna contains a *radio distribution network* (RDN) and an antenna array. The RDN is a linear passive network that distributes the RF power between the *transceiver array boundary* and the antenna array, in an implementation specific way. + +How a conducted requirement is applied to the *transceiver array boundary* is detailed in the respective requirement clause. + +The present document details the test requirements of the radiated requirements only and hence only requires the radiated reference points. + +## 4.3 Base station classes for AAS BS + +The requirements in this specification apply to AAS BS of Wide Area BS, Medium Range BS and Local Area BS classes unless otherwise stated. + +The base station classes are defined in TS 37.105 [6]. + +## 4.4 Regional requirements + +Some requirements in the present document may only apply in certain regions either as optional requirements, or set by local and regional regulation as mandatory requirements. It is normally not stated in the 3GPP specifications under what exact circumstances that the requirements apply, since this is defined by local or regional regulation. + +Table 4.4-1 lists all requirements in the present specification that may be applied differently in different regions. Non-AAS requirements are applicable as defined in the present document. In many cases, such requirements include regional + +requirements that are implicitly referenced from the present specification, and listed in the specification for the specifications concerned [2] [5]. + +**Table 4.4-1: List of regional requirements** + +| Clause number | Requirement | Comments | +|---------------|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.6 | Operating bands and Band Categories | Some bands may be applied regionally. | +| 6.7.2 | OTA Occupied bandwidth | The requirement may be applied regionally. There may also be regional requirements to declare the Occupied bandwidth according to the definition. | +| 6.7.4 | OTA Spectrum emission mask | The mask specified may be mandatory in certain regions. In other regions this mask may not be applied. Additional spectrum protection requirements may apply regionally. | +| 6.7.5 | OTA Operating band unwanted emissions | The BS may have to comply with the applicable emission limits established by FCC Title 47 [18], when deployed in regions where those limits are applied and under the conditions declared by the manufacturer. | +| 6.7.5 | OTA Operating band unwanted emissions | The requirements for unsynchronized TDD co-existence may apply regionally. | +| 6.7.5 | OTA Operating band unwanted emissions | The requirements for protection of DTT may apply regionally. | +| 6.7.5 | OTA Operating band unwanted emissions | Regional requirement as defined in TS 37.104, clause 6.6.2.4.4 [5] may be applied for the protection of systems operating in frequency bands adjacent to band 1 as defined in TS 37.104, clause 4.5, [5] in geographic areas in which both an adjacent band service and UTRA and/or E-UTRA are deployed. | +| 6.7.5 | OTA Operating band unwanted emissions | Additional requirements defined for Band 24 in 3GPP TS 37.104, subclause 6.6.2.4.5 may apply in regions where FCC regulation applies. | +| 6.7.5 | OTA Operating band unwanted emissions | Additional band 32 unwanted emissions requirements may apply in certain regions | +| 6.7.6 | OTA Spurious emissions | Category A limits are mandatory for regions where Category A limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [16] apply. Category B limits are mandatory for regions where Category B limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [16] apply. | +| 6.7.6 | OTA Spurious emissions | Additional spurious emissions requirements may be applied for the protection of system operating in frequency ranges other than the AAS BS operating band as described in TS 37.104 [5] clause 6.6.1.3 (NOTE). | +| 6.7.6 | OTA Spurious emissions | In addition to 3GPP requirements, the BS may have to comply with the applicable emission limits established by FCC Title 47 [18], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. | +| 6.7.6 | OTA Spurious emissions | Co-location spurious emissions requirements may be applied for the protection of other BS receivers when an MSR BS operating in another frequency band is co-located with an AAS BS. | +| 6.7.6 | OTA Spurious emissions | The emission limits specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | +| 6.7.6 | OTA Spurious emissions | Additional requirements defined for Band 54 in 3GPP TS 37.104, subclause 6.6.1.3.1 may apply in regions where FCC regulation applies. | +| 6.8 | OTA Transmitter intermodulation | Additional requirements may apply in certain regions. | +| 7.5 | Additional BC3 blocking requirement | This requirement may be applied for the protection of the BS receiver when an MSR BS is operating in the same geographical area as UTRA TDD. | +| 7.6 | OTA Blocking | Co-location blocking requirements may be applied for the protection of the BS receiver when a BS operating in another frequency band is co-located with an AAS BS. | +| 7.6 | OTA Blocking | For the Public Safety LTE BS in Korea from 718 to 728 MHz in Band 28, regional blocking requirement is specified in TS 36.104 [4], clause 7.6.3. | +| 7.7 | OTA Rx spurious emissions | The emission limits specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | + +NOTE: AAS BS does not support Band 46 operation, but additional spurious emissions requirements for Band 46 as described in TS 37.104 [5] clause 6.6.1.3, are still applicable for AAS BS for protection of Band 46 operation. + +## 4.5 Operating bands and band categories + +The operating bands and band categories for AAS BS are the same as for *non-AAS BS*, as described in TS 37.104 [6]. In addition, band category aspects described in TS 37.141, clauses 4.4.1, 4.4.2 and 4.4.3, shall apply. + +NOTE 1: *AAS BS* does not support GSM, but BC2 is still applicable for protection of/against GSM operation in BC2 operating bands. + +NOTE 2: AAS BS does not support Band 46 (and all its sub-bands defined in TS 36.104 [4]) operation. Conducted Band 46 test requirements are still applicable for AAS BS for protection of and against Band 46 operation, as specified in TS 37.145-1 [9]. + +## 4.6 Channel arrangements + +The channel arrangements for AAS BS are the same as those for UTRA *non-AAS BS* and E-UTRA *non-AAS BS* as described in TS 37.104 [5]. + +## 4.7 Requirements for AAS BS capable of multi-band operation + +For AAS BS capable of operation in multiple operating bands, the RF requirements in clause 6 and 7 apply separately to each supported operating band unless otherwise stated. + +A *hybrid AAS BS* may be capable of supporting operation in multiple operating bands with one of the following implementations of *TAB connectors* in the *transceiver array boundary*: + +- All *TAB connectors* are *single band TAB connectors*. + - Different sets of *single band TAB connectors* support different operating bands, but each *TAB connector* supports only operation in one single operating band. + - Sets of *single band TAB connectors* support operation in multiple operating bands with some *single band TAB connectors* supporting more than one operating band. +- All *TAB connectors* are *multiband TAB connectors*. +- A combination of single band sets and multi-band sets of *TAB connectors* provides support of the *hybrid AAS BS* capability of operation in multiple operating bands. + +Unless otherwise stated all requirements specified for an operating band apply only to the set of *TAB connectors* supporting that operating band. + +In certain requirements it is explicitly stated that specific additions or exclusions to the requirement apply at *multi-band TAB connectors* as detailed in the requirement subclause. When referencing the NR specification 3GPP TS 38.104 [33] for a BS type 1-H the multi-band connector term is equivalent to a *multi-band TAB connector* in this specification. + +In the case of an operating band being supported only by *single band TAB connectors* in a *TAB connector TX min cell group* or a *TAB connector RX min cell group*, *single band requirements* apply to that set of *TAB connectors*. + +NOTE: Each supported operating band needs to be operated separately during conformance testing on *single band TAB connectors*. + +For a band supported by a *TAB connector* where the transmitted carriers are not processed in active RF components together with carriers in any other band, *TX single band requirements* shall apply. For a band supported by a *TAB connector* where the received carriers are not processed in active RF components together with carriers in any other band, *RX single band requirements* shall apply. + +In the case of an operating band being supported only by *multi-band TAB connectors* supporting the same operating band combination in a *TAB connector TX min cell group* or a *TAB connector RX min cell group*, *multi-band requirements* apply to that set of *TAB connectors*. + +The case of an operating band being supported by both *multi-band TAB connectors* and *single band TAB connectors* in a *TAB connector TX min cell group* or a *TAB connector RX min cell group* is not covered by the present release of this specification. + +The case of an operating band being supported by *multi-band TAB connectors* which are not all supporting the same operating band combination in a *TAB connector TX min cell group* or a *TAB connector RX min cell group* is not covered by the present release of this specification. + +An *OTA AAS BS* may be capable of supporting operation in multiple operating bands with one of the following implementations at the *radiated interface boundary*: + +- All RIBs are *single band RIBs*. +- All RIBs are *multiband RIBs*. +- A combination of *single band RIBs* and *multi-band RIBs* provides support of the *OTA AAS BS* capability of operation in multiple operating bands. + +In certain requirements it is explicitly stated that specific additions or exclusions to the requirement apply at *multi-band RIBs* as detailed in the requirement subclause. + +NOTE: Each supported operating band needs to be operated separately during conformance testing for single RIBs. + +For *multi-band TAB connectors* and *multi-band RIBs* supporting the bands for TDD, the RF requirements in the present specification assume no simultaneous uplink and downlink occur between the bands. + +The RF requirements for *multi-band TAB connectors* and *multi-band RIBs* supporting bands for both FDD and TDD are not covered by the present release of this specification. + +A RIB may operate multi-RAT where the individual RATs are operated in different RAT specific bands that partially or fully overlap; $\Delta f_{\text{OBUE}}$ and $\Delta f_{\text{FOOB}}$ are according to the combined frequency range occupied by the overlapping bands. + +## 4.8 AAS BS configurations + +### 4.8.1 Transmit configurations + +Unless otherwise stated, the radiated transmitter characteristics in clause 6 are specified at the *radiated interface boundary* (RIB). The AAS BS shall have a full complement of transceiver units for the configuration in normal operating conditions. + +![Diagram of transmitter test interfaces for an AAS BS. The diagram shows the internal structure of an AAS BS, including the Transceiver unit array, Transceiver Array Boundary, RDN, Antenna array, and Composite antenna. An arrow points from the AAS BS to a Test antenna connected to Measurement equipment.](eb450c92214e8409c1e0f0846e30d876_img.jpg) + +The diagram illustrates the transmitter test interfaces for an AAS BS. On the left, a dashed box labeled 'AAS BS' contains several components: a 'Transceiver unit array' on the left, a 'Transceiver Array Boundary' (dashed line) in the center, and a 'Composite antenna' on the right. The 'Composite antenna' is further divided into 'RDN' and 'Antenna array'. Inside the 'Transceiver unit array', there are multiple transceivers labeled #1, #2, ..., #K. An arrow points from the 'AAS BS' to a 'Test antenna' on the right, which is connected to 'Measurement equipment'. + +Diagram of transmitter test interfaces for an AAS BS. The diagram shows the internal structure of an AAS BS, including the Transceiver unit array, Transceiver Array Boundary, RDN, Antenna array, and Composite antenna. An arrow points from the AAS BS to a Test antenna connected to Measurement equipment. + +Figure 4.8.1-1: Transmitter test interfaces + +![Diagram of transmitter test interfaces for co-location concept. It shows an AAS BS containing a Transceiver unit array and a Composite antenna (RDN and AA). A Co-location reference antenna is connected to Measurement equipment. A Test antenna is also connected to Measurement equipment. Arrows indicate the flow from the BS to the test equipment.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +Top view + +The diagram illustrates the transmitter test interfaces for the co-location concept. At the top, a 'Co-location reference antenna' (dashed box) is connected to 'Measurement equipment'. Below it, an 'AAS BS' (dashed box) contains a 'Transceiver unit array' and a 'Composite antenna' (which includes 'Radio Distribution Network RDN' and 'Antenna Array AA'). A large upward arrow points from the AAS BS to the Co-location reference antenna. To the right, a 'Test antenna' is connected to 'Measurement equipment', with a large rightward arrow pointing from the AAS BS to it. + +Diagram of transmitter test interfaces for co-location concept. It shows an AAS BS containing a Transceiver unit array and a Composite antenna (RDN and AA). A Co-location reference antenna is connected to Measurement equipment. A Test antenna is also connected to Measurement equipment. Arrows indicate the flow from the BS to the test equipment. + +Figure 4.8.1-2: Transmitter test interfaces for co-location concept + +## 4.8.2 Receive configurations + +Unless otherwise stated, the radiated receiver characteristics in clause 7 are specified at the *radiated interface boundary* (RIB). The AAS BS shall have a full complement of transceiver units for the configuration in normal operating conditions. + +![Diagram of receiver test interfaces. It shows an AAS BS containing a Transceiver unit array and a Composite antenna (RDN and AA). The Transceiver unit array is divided into multiple units labeled #1, #2, ..., #K. A Test antenna is connected to Measurement equipment. An arrow points from the test equipment to the BS.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +The diagram illustrates the receiver test interfaces. On the right, a 'Test antenna' is connected to 'Measurement equipment'. A large leftward arrow points from the test equipment towards an 'AAS BS' (dashed box). The AAS BS contains a 'Transceiver unit array' and a 'Composite antenna' (which includes 'RDN' and 'Antenna array'). The 'Transceiver unit array' is divided into multiple units, labeled '#1', '#2', '...', and '#K'. A dashed line labeled 'Transceiver Array Boundary' encloses the transceiver units. + +Diagram of receiver test interfaces. It shows an AAS BS containing a Transceiver unit array and a Composite antenna (RDN and AA). The Transceiver unit array is divided into multiple units labeled #1, #2, ..., #K. A Test antenna is connected to Measurement equipment. An arrow points from the test equipment to the BS. + +Figure 4.8.2-1: Receiver test interfaces + +![Diagram illustrating the receiver test interfaces for the co-location concept. It shows a 'Co-location reference antenna' connected to 'Measurement equipment', which is connected to the 'AAS BS'. The 'AAS BS' is shown in a top view, containing a 'Transceiver unit array', a 'Radio Distribution Network (RDN)', and an 'Antenna Array (AA)'. The 'RDN' and 'AA' are grouped as a 'Composite antenna'. A 'Test antenna' is also connected to 'Measurement equipment', with an arrow pointing from the test antenna towards the 'AAS BS'.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Top view + +The diagram illustrates the receiver test interfaces for the co-location concept. At the top, a 'Co-location reference antenna' (represented by a dashed rectangle) is connected to 'Measurement equipment' (a solid rectangle). A large downward-pointing arrow leads to a top view of the 'AAS BS' (Active Antenna System Base Station). The 'AAS BS' is enclosed in a dashed rectangle and contains three main components: a 'Transceiver unit array' (left), a 'Radio Distribution Network (RDN)' (middle), and an 'Antenna Array (AA)' (right). The 'RDN' and 'AA' are grouped together as a 'Composite antenna'. To the right of the 'AAS BS', a 'Test antenna' (represented by a symbol) is connected to 'Measurement equipment' (a solid rectangle). A large rightward-pointing arrow indicates the signal flow from the test antenna towards the 'AAS BS'. + +Diagram illustrating the receiver test interfaces for the co-location concept. It shows a 'Co-location reference antenna' connected to 'Measurement equipment', which is connected to the 'AAS BS'. The 'AAS BS' is shown in a top view, containing a 'Transceiver unit array', a 'Radio Distribution Network (RDN)', and an 'Antenna Array (AA)'. The 'RDN' and 'AA' are grouped as a 'Composite antenna'. A 'Test antenna' is also connected to 'Measurement equipment', with an arrow pointing from the test antenna towards the 'AAS BS'. + +**Figure 4.8.2-2: Receiver test interfaces for co-location concept** + +### 4.8.3 Power supply options + +If the AAS BS 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. + +### 4.8.4 BS with integrated Iuant BS modem + +Unless otherwise stated, for the tests in the present document, the integrated Iuant BS modem shall be switched OFF. + +## 4.9 Capability sets + +A radiated capability set is defined as the AAS BS capability to support certain RAT combinations in an operating band. + +The manufacturer shall declare (D9.25) the supported radiated capability set(s) according to table 4.9-1 for each supported operating band. + +**Table 4.9-1 Radiated capability sets** + +| Radiated capability Set supported by the AAS BS | RCSA1 | RCSA2 | RCSA3 | RCSA3A | RCSA3B | RCSA4 | RCSA5 | +|--------------------------------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|------------------------------------------------------| +| Supported RATs | AAS BS supports MSR operation of UTRA only in the band | AAS BS supports MSR operation of E-UTRA only in the band | AAS BS supports MSR E-UTRA and UTRA in the band | AAS BS supports NR and E-UTRA MSR in the band | AAS BS supports MSR NR, E-UTRA and UTRA in the band | AAS BS supports single-RAT UTRA in the band | AAS BS supports single-RAT E-UTRA in the band | +| Supported configurations | SR UTRA (SC, MC) | SR E-UTRA (SC, MC, CA) | MR UTRA + E-UTRA
SR UTRA (SC, MC)
SR E-UTRA (SC, MC, CA) | MR E-UTRA + NR
SR NR (SC, MC, CA)
SR E-UTRA (SC, MC, CA) | SR UTRA (SC, MC)
SR E-UTRA (SC, MC, CA)
SR NR (SC, MC, CA)
MR UTRA + E-UTRA
MR UTRA + NR
MR E-UTRA + NR
MR UTRA + E-UTRA + NR | SR UTRA (SC, MC) | SR E-UTRA (SC, MC, CA) | +| Applicable BC | BC1, BC2 or BC3 | BC1, BC2 or BC3 | BC1, BC2 or BC3 | BC1, BC2 or BC3 | BC1, BC2 | BC1, BC2 or BC3 | BC1, BC2 or BC3 | + +The applicable test configurations for each RF requirement are defined in clause 5.1, 5.2 and 5.3 for the declared radiated capability set(s). For beams with multi-band beam dependencies the applicable test configurations for each RF requirement are defined in clause 5.4 for the declared radiated capability set(s). + +NOTE: Not every supported configuration within a capability set is tested, but the tables in clauses 5.2, 5.3 and 5.4 provide a judicious choice among the supported configurations and test configurations to ensure proper test coverage. + +## 4.10 Manufacturer declarations + +The AAS BS declarations categories D9.x and D10.x listed in table 4.10-1 are required to be provided by the manufacturer for the radiated requirements testing of the *hybrid AAS BS* or the OTA AAS BS. + +For the *hybrid AAS BS* declarations required for the conducted requirements testing, refer to TS 37.145-1 [9], clause 4.10. + +NOTE 1: D9.x declarations are related to the radiated Tx requirements, while D10.x declarations are related to the radiated Rx requirements. + +NOTE 2: From Rel-15 onwards, additional D11.x declarations are introduced in table 4.10-2 for OTA AAS BS, in order to easily distinguish from the Rel-13/14 OTA declarations which are also applicable for *hybrid AAS BS*. Declarations in table 4.10-2 are applicable to OTA AAS BS only. + +**Table 4.10-1: Hybrid AAS BS and OTA AAS BS manufacturer declarations for radiated test requirements** + +| Declaration identifier | Declaration | Description | +|------------------------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D9.1 | Coordinate system reference point | Location of coordinated system reference point in reference to an identifiable physical feature of the AAS BS enclosure. | +| D9.2 | Coordinate system orientation | Orientation of the coordinate system in reference to an identifiable physical feature of the AAS BS enclosure. | +| D9.3 | Beam identifier |

A unique title to identify a beam, e.g. a, b, c or 1, 2, 3. The vendor may declare any number of beams with unique identifiers. The minimum set to declare, for conformance, correspond to the beams at the reference beam direction, with the highest intended EIRP, and covering the properties listed below:

  1. 1) A beam with the narrowest intended BeW_\phi, and narrowest intended BeW_\theta possible when narrowest intended BeW_\phi is used.
  2. 2) A beam with the narrowest intended BeW_\phi and narrowest intended BeW_\theta possible when narrowest intended BeW_\phi is used.
  3. 3) A beam with the widest intended BeW_\phi and widest intended BeW_\theta possible when widest intended BeW_\phi is used.
  4. 4) A beam with the widest intended BeW_\phi and widest intended BeW_\theta possible when widest intended BeW_\phi is used.
  5. 5) A beam which provides the highest intended EIRP of all possible beams.

NOTE 1: Depending on the capability of the system some of these beams may be the same. For those same beams, testing is not repeated.

When selecting the above five beam widths for declaration, all beams that the AAS BS is intended to produce shall be considered, including beams that during operation may be identified by any kind of cell or UE specific reference signals, with the exception of any type of beam that is created from a group of transmitters that are not all phase synchronised.

| +| D9.4 | Operating bands and frequency ranges |

List of UTRA or E-UTRA operating band(s) supported by BS and if applicable, frequency range(s) within the operating band(s) that the BS can operate in.

Supported bands declared for every beam (D9.3).

NOTE 2: These operating bands are related to their respective single-band RIBs.

NOTE 3: This declaration in-directly provides information on the RAT's supported by the AAS BS.

| +| D9.5 | Beam RAT support | RAT(s) supported by each beam for each supported operating band, declared for every beam identified in D9.3. | +| D9.6 | E-UTRA channel band width support | E-UTRA channel bandwidth supported. Declared for each beam (D9.3) and each E-UTRA operating band (D9.4). | +| D9.7 | Reference beam direction pair | The beam direction pair, describing the reference beam peak direction and the reference beam centre direction. Declared for every beam | +| D9.8 | OTA peak directions set |

The OTA peak directions set for each beam. Declared for every beam identified in D9.3.

NOTE 4: In Rel-13/14 version of this specification, this declaration was called EIRP accuracy directions set.

| + +| Declaration identifier | Declaration | Description | +|------------------------|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D9.9 | Maximum steering direction(s) |

The beam direction pair(s) corresponding to the following points:

  1. 1) The beam peak direction corresponding to the maximum steering from the reference beam centre direction in the positive \Phi direction, while the \theta value being the closest possible to the reference beam centre direction.
  2. 2) The beam peak direction corresponding to the maximum steering from the reference beam centre direction in the negative \Phi direction, while the \theta value being the closest possible to the reference beam centre direction.
  3. 3) The beam peak direction corresponding to the maximum steering from the reference beam centre direction in the positive \theta direction, while the \Phi value being the closest possible to the reference beam centre direction.
  4. 4) The beam peak direction corresponding to the maximum steering from the reference beam centre direction in the negative \theta direction, while the \Phi value being the closest possible to the reference beam centre direction.

The maximum steering direction(s) may coincide with the reference beam centre direction.
Declared for every beam identified in D9.3.

| +| D9.10 | Rated beam EIRP |

The rated EIRP level per carrier (P_{\text{rated,c,EIRP}}) at the beam peak direction associated with a particular beam direction pair for each of the declared maximum steering directions (D9.9), as well as the reference beam direction pair (D9.7). Declared for every beam identified in D9.3. (Note 1, Note 2)

| +| D9.11 | Beamwidth |

The beamwidth for the reference beam direction pair and the four maximum steering directions. Declared for every beam identified in D9.3.

| +| D9.12 | Equivalent beams |

List of beams which are declared to be equivalent. Equivalent beams imply that the beams are expected to have identical OTA peak directions sets and intended to have identical spatial properties at all steering directions within the OTA peak directions set when presented with identical signals. All declarations (D9.4-D9.11) made for the beams are identical and the transmitter unit, RDN and antenna array responsible for generating the beam are of identical design.

| +| D9.13 | Parallel beams |

List of beams which have been declared equivalent (D9.12) and can be generated in parallel using independent RF power resources. Independent power resources mean that the beams are transmitted from mutually exclusive transmitter units.

| +| D9.14 | Number of carriers at maximum TRP |

The number of carriers per operating band the AAS BS is capable of generating at maximum TRP declared each RAT (and multi-RAT) for every beam identified in D9.3.

| +| D9.15 | Multi-band transceiver units |

Declared if an operating band is generated using transceiver units supporting operation in multiple operating bands through common active RF components.

| +| D9.16 | Operating bands with multi-band dependencies |

List operating bands which are generated by multi-band transceiver units. Declared for each operating band for which multi-band transceiver units (D9.15) have been declared,

| +| D9.15 | Maximum radiated Base Station RF Bandwidth |

Maximum Base Station RF Bandwidth in the operating band, declared for each supported operating band identified in D9.4.

| +| D9.18 | Maximum radiated Base Station RF Bandwidth for contiguous operation. |

Largest Base Station RF Bandwidth for contiguous spectrum operation, declared for each supported operating band (D9.4).

| +| D9.19 | Maximum radiated Base Station RF Bandwidth for non-contiguous operation. |

Maximum Base Station RF Bandwidth for non-contiguous spectrum operation, declared for each supported operating band (D9.4).

| +| D9.20 | Inter-band CA bands |

Declared inter-band CA bands supported per operating band (D9.4).

| +| D9.21 | CA only operation |

Declared per operating band identified in D9.4.

| +| D9.22 | Multi-carrier HSPA only operation |

Declared per each supported UTRA operating band (D9.4).

| +| D9.23 | Reduced number of supported carriers at maximum TRP in multi-RAT operations |

Declared for each supported operating (D9.4).

| +| D9.24 | Reduced maximum TRP at the total number of supported carriers in multi-RAT operations |

Declared for each supported operating band (D9.4). (Note 1, Note 2)

| + +| Declaration identifier | Declaration | Description | +|------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D9.25 | Radiated capability set (RCSA) | The manufacturer shall declare the supported radiated capability set(s) according to table 4.9-1 for each supported operating band (D9.4).
NOTE: in case of hybrid AAS BS , set of operating band specific RCSA declarations shall be aligned with the set of CSA's declared by D6.12 in TS 37.145-1 [9] for the conducted testing for the operating band in question. | +| D9.26 | Maximum Radio Bandwidth of the operating band with multi-band dependencies | Largest Radio Bandwidth that can be supported by the operating bands with multi-band dependencies.
Declared for each supported operating band which has multi-band dependencies (D9.16) | +| D9.27 | Total number of supported carriers for operating bands with multi-band dependencies | Total number of supported carriers for operating bands declared to have multi-band dependencies (D9.16). | +| D9.28 | Contiguous or non-contiguous spectrum support | Ability of AAS BS to support contiguous or non-contiguous (or both) frequency distribution of carriers when operating multi-carrier in an operating band. | +| D9.29 | Non-contiguous parameters | If non-contiguous operation is supported in operating band () and parameters (e.g. frequency range, maximum Base Station RF Bandwidth, rated transmitter TRP, etc.) differ from the contiguous spectrum operation, then this declaration provided parameters for the non-contiguous operation. Otherwise, parameters for contiguous or non-contiguous spectrum operation in the operating band are assumed to be the same. | +| D9.30 | DL RS EIRP for conformance test | The DL RS EIRP transmitted during the DL RS power conformance test derived from the power broadcast on the DL-SCH and the AAS BS directivity in the direction to be tested. | +| D9.31 | NR BS channel band width and SCS support | NR BS channel bandwidth and SCS supported. Declared for each beam () and each operating band (). | +| D9.32 | Total RF bandwidth ( $BW_{tot}$ ) | Total RF bandwidth $BW_{tot}$ of transmitter and receiver, declared per the band combinations (). | +| D9.33 | Inter-band CA bands | Declared inter-band CA bands supported by the beam. Declared per beam (D.3). | +| D9.34 | CA only operation | Declared of CA-only but not multiple carriers operation, declared per operating band (D.4) and per beam (D.3). | +| D10.1 | OSDD identifier | A unique identifier for the OSDD. | +| D10.2 | OSDD operating band support | Operating band supported by the OSDD, declared for every OSDD identified in D10.1.
NOTE 2: As each identified OSDD has a declared minimum EIS value (D10.6), multiple operating band can be only be declared if they have the same minimum EIS declaration. | +| D10.3 | OSDD RAT support | RAT(s) supported by the OSDD for each supported operating band, declared for every OSDD identified in D10.1.
NOTE 3: If the OSDD supports multiple RAT's with different minimum EIS value (D10.6) if all other parameters are the same then different EIS values for different RATS and signal BW's may be declared for an OSDD. | +| D10.4 | OTA sensitivity E-UTRA supported channel bandwidths | The E-UTRA channel bandwidths supported by each OSDD. | +| D10.5 | Redirection of receiver target support | Ability to redirect the receiver target related to the OSDD | +| D10.6 | Minimum EIS | The minimum EIS requirement (i.e. maximum allowable EIS value) applicable to all sensitivity RoAoA per OSDD.
Declared for per RAT and E-UTRA supported channel BW for the OSDD (10.4).
The lowest EIS value for all the declared OSDD's is called minSENS , while its related range of angles of arrival is called minSENS RoAoA .
NOTE 4: If the AAS BS is not capable of redirecting the receiver target related to the OSDD then there is only one RoAoA applicable to the OSDD. | +| D10.7 | Receiver target reference direction Sensitivity Range of Angle of Arrival | The sensitivity RoAoA associated with the receiver target reference direction (D10.9) for each OSDD. | + +| Declaration identifier | Declaration | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D10.8 | Receiver target redirection range | For each OSDD the associated union of all the sensitivity RoAoA achievable through redirecting the receiver target related to the OSDD | +| D10.9 | Receiver target reference direction | For each OSDD an associated direction inside the receiver target redirection range (D10.8).
NOTE 5: For an OSDD without receiver target redirection range, this is a direction inside the sensitivity RoAoA. | +| D10.10 | Conformance test directions sensitivity RoAoA | For each OSDD that includes a receiver target redirection range, four sensitivity RoAoA comprising the conformance test directions (D10.11). | +| D10.11 | Conformance test directions | For each OSDD four conformance test directions.
If the OSDD includes a receiver target redirection range the following four directions shall be declared:
  1. 1) The direction determined by the maximum \phi value achievable inside the receiver target redirection range, while \theta value being the closest possible to the receiver target reference direction.
  2. 2) The direction determined by the minimum \phi value achievable inside the receiver target redirection range, while \theta value being the closest possible to the receiver target reference direction.
  3. 3) The direction determined by the maximum \theta value achievable inside the receiver target redirection range, while \phi value being the closest possible to the receiver target reference direction.
  4. 4) The direction determined by the minimum \theta value achievable inside the receiver target redirection range, while \phi value being the closest possible to the receiver target reference direction.
If an OSDD does not include a receiver target redirection range the following 4 directions shall be declared:
  1. 1) The direction determined by the maximum \phi value achievable inside the sensitivity RoAoA, while \theta value being the closest possible to the receiver target reference direction.
  2. 2) The direction determined by the minimum \phi value achievable inside the sensitivity RoAoA, while \theta value being the closest possible to the receiver target reference direction.
  3. 3) The direction determined by the maximum \theta value achievable inside the sensitivity RoAoA, while \phi value being the closest possible to the receiver target reference direction.
  4. 4) The direction determined by the minimum \theta value achievable inside the sensitivity RoAoA, while \phi value being the closest possible to the receiver target reference direction.
| +| D10.12 | OTA sensitivity supported NR BS channel bandwidth and SCS | The NR BS channel bandwidths and SCS supported by each OSDD. | +| NOTE 1: If a BS is capable of 256QAM DL operation but not 1024QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. | | | +| NOTE 2: If a BS is capable of 1024QAM DL operation then up to three rated output power declarations may be made. One declaration is applicable when configured for 1024QAM transmissions, a different declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when configured neither for 256 QAM nor 1024QAM transmissions. | | | + +**Table 4.10-2: OTA AAS BS manufacturers declarations for radiated test requirements** + +| Declaration identifier | Declaration | Description | +|------------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D11.1 | AAS BS requirements set | Declaration of either hybrid AAS BS architecture conforming to the hybrid requirement set , or OTA AAS BS architecture conforming to the OTA requirement set . | +| D11.2 | BS class | BS Class of the AAS BS, declared as Wide Area BS, Medium Range BS, or Local Area BS. | + +| Declaration identifier | Declaration | Description | +|------------------------|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D11.3 | OTA coverage range | Declared as a single range within which selected TX OTA requirements are intended to be met.

NOTE 1: OTA coverage range is used for conformance testing of such TX OTA requirements as occupied bandwidth, frequency error, TAE or EVM. | +| D11.4 | OTA coverage range reference direction | The direction describing the reference direction of the OTA coverage range (D11.2).
NOTE 2: The OTA coverage reference direction may be the same as the Reference beam direction pair (D9.7) but does not have to be. | +| D11.5 | OTA coverage range maximum directions | The directions corresponding to the following points:
1) The direction determined by the maximum $\phi$ value achievable inside the OTA coverage range , while $\theta$ value being the closest possible to the OTA coverage range reference direction.
2) The direction determined by the minimum $\phi$ value achievable inside the OTA coverage range , while $\theta$ value being the closest possible to the OTA coverage range reference direction.
3) The direction determined by the maximum $\theta$ value achievable inside the OTA coverage range , while $\phi$ value being the closest possible to the OTA coverage range reference direction.
4) The direction determined by the minimum $\theta$ value achievable inside the OTA coverage range , while $\phi$ value being the closest possible to the OTA coverage range reference direction. | +| D11.6 | The rated carrier OTA BS power, $P_{\text{rated,c,TRP}}$ | $P_{\text{rated,c,TRP}}$ is declared as TRP OTA power per carrier, declared per supported operating band, per supported RAT. (Note 1, Note 2) | +| D11.7 | Worst-case side of the AAS BS on which the co-location test antenna is placed | Declare the worst-case side of the AAS BS on which the co-location test antenna is placed and test will be done only on the declared side. | +| D11.8 | Spurious emission category | Declare the OTA AAS BS spurious emission category as either category A or B with respect to the limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [16]. | +| D11.9 | Geographic area support | The manufacturer shall declare the regions the OTA AAS BS may operate in. e.g. CEPT. | +| D11.10 | Band 20 or Band XX support, operating in geographical areas allocated to broadcasting (DTT) | If the OTA AAS BS supports Band 20/XX or Band 32/XXXII, the manufacturer shall declare if the OTA AAS BS may operate in geographical areas allocated to broadcasting (DTT). | +| D11.11 | Band 20 or Band XX support, emission level for channel N ( $P_{\text{EM,N}}$ ) | If the OTA AAS BS supports Band 20 or Band XX and has been declared to operate in geographical areas allocated to broadcasting (DTT; declaration D11.7), the emission level for channel N (as defined in annex G of TS 36.104 [4]) shall be declared. | +| D11.12 | Band 20 or Band XX support, Maximum output power in 10 MHz ( $P_{10\text{ MHz}}$ ) | If the OTA AAS BS supports Band 20 or Band XX and has been declared to operate in geographical areas allocated to broadcasting (DTT; declaration D11.7), the maximum output power in 10 MHz (annex G of TS 36.104 [4]) shall be declared. | +| D11.13 | Band 32 or Band XXXII support, Declared emission level in Band 32/XXXII ( $P_{\text{EM,B32,ind}}$ ) | If the OTA AAS BS supports Band 32 or Band XXXII and has been declared to operate in geographical areas allocated to broadcasting (DTT; declaration D11.7), the emission level in Band 32/XXXII ( $P_{\text{EM,B32,ind}}$ , ind = a, b, c, d, e) shall be declared. | +| D11.14 | Co-existence with other systems | The manufacturer shall declare whether the OTA AAS BS under test is intended to operate in geographic areas where one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD, E-UTRA and/or PHS operating in another operating band are deployed. | + +| Declaration identifier | Declaration | Description | +|------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D11.15 | Co-location with other base stations | The manufacturer shall declare whether the OTA AAS BS under test is intended to operate co-located with Base Stations of one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD and/or E-UTRA operating in another operating band. | +| D11.16 | Single-band RIB or multi-band RIB | List of single-band RIB and/or multi-band RIB resulting from the supported operating bands (D9.4), and operating bands with multi-band dependencies (D9.16). | +| D11.17 | Single or multiple carrier | OTA AAS BS capability to operate with a single carrier (only) or multiple carriers. Declared per supported operating band, per RAT, per RIB. | +| D11.18 | Maximum number of supported carriers per band | Maximum number of supported carriers. Declared per supported operating band, per RAT, per RIB. | +| D11.19 | Total maximum number of supported carriers | Maximum number of supported carriers for all supported operating bands. Declared per RIB. | +| D11.20 | Other band combination multi-band restrictions | Declare any other limitation under simultaneous operation in the declared band combinations (D9.16), which have any impact on the test configuration generation. | +| D11.21 | $N_{\text{cells}}$ | Number corresponding to the minimum number of cells that can be transmitted by an OTA AAS BS in a particular operating band. Declared per RIB (D11.13). | +| D11.22 | Maximum supported power difference between carriers | Maximum supported TRP difference between carriers in each supported operating band. Declared per RIB. | +| D11.23 | Maximum supported power difference between carriers is different operating bands | Maximum supported power difference between any two carriers in any two different supported operating bands. Declared per operating bands combination (D9.16, D11.16). | +| D11.24 | UTRA FDD MIMO support | Number of 'antennas' supported by the UTRA FDD MIMO mode (i.e. 2 or 4). Declared per supported UTRA FDD operating band (D9.4).

NOTE 3: The concept of "antenna 2", "antenna 3" and "antenna 4" is described in TS 25.104 [2]. | +| D11.25 | UTRA Inner loop power control dynamic range | Power control dynamic range for UTRA inner loop power control. Declared per supported UTRA FDD operating band, per RIB. | +| D11.26 | Inter-band CA or inter-band HSDPA | Declaration of operating band combinations supporting inter-band CA or multi-band HSDPA. Declared per operating band combination (D9.16, D11.16). | +| D11.27 | Intra-band contiguous CA or intra-band contiguous HSDPA | Declaration of operating band(s) supporting intra-band contiguous CA, or intra-band contiguous HSDPA. Declared per operating band with CA support. | +| D11.28 | Intra-band non-contiguous CA or intra-band contiguous HSDPA | Declaration of operating band(s) supporting intra-band non-contiguous CA, or intra-band non-contiguous HSDPA. Declared per operating band with CA support. | +| D11.29 | OTA REFSSENS RoAoA | The REFSSENS RoAoA associated with the receiver target reference direction (D11.30). | +| D11.30 | OTA REFSSENS receiver target reference direction | An associated direction inside the OTA REFSSENS RoAoA (D11.29). | + +| Declaration identifier | Declaration | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D11.31 | OTA REFSENS conformance test directions | Four conformance test directions for the OTA REFSENS:
1) The direction determined by the maximum $\phi$ value achievable inside the OTA REFSENS RoAoA, while $\theta$ value being the closest possible to the receiver target reference direction.
2) The direction determined by the minimum $\phi$ value achievable inside the OTA REFSENS RoAoA, while $\theta$ value being the closest possible to the receiver target reference direction.
3) The direction determined by the maximum $\theta$ value achievable inside the OTA REFSENS RoAoA, while $\phi$ value being the closest possible to the receiver target reference direction.
4) The direction determined by the minimum $\theta$ value achievable inside the OTA REFSENS RoAoA, while $\phi$ value being the closest possible to the receiver target reference direction. | +| D11.32 | Supported frequency range of the NR operating band | List of supported frequency ranges representing fractional bandwidths (FBW) of operating bands with FBW larger than 6%. | +| D11.33 | Rated beam EIRP at lower frequency range of the fractional bandwidth ( $P_{\text{rated,c,FBWLow}}$ ) | The rated EIRP level per carrier at lower frequency range of the fractional bandwidth ( $P_{\text{rated,c,FBWLow}}$ ), at the beam peak direction associated with a particular beam direction pair for each of the declared maximum steering directions (D9.9), as well as the reference beam direction pair (D9.7). (Note 1, Note 2)
Declared per beam for all supported frequency ranges (D11.32).
NOTE 13: if D11.33 is declared for certain frequency range (D11.32), there shall be no "Rated beam EIRP" declaration (D9.10) for the operating band containing that particular frequency range. | +| D11.34 | Rated beam EIRP at higher frequency range of the fractional bandwidth ( $P_{\text{rated,c,FBWHigh}}$ ) | The rated EIRP level per carrier at higher frequency range of the fractional bandwidth ( $P_{\text{rated,c,FBWHigh}}$ ), at the beam peak direction associated with a particular beam direction pair for each of the declared maximum steering directions (D9.9), as well as the reference beam direction pair (D9.7). (Note 1, Note 2)
Declared per beam for all supported frequency ranges in (D11.32).
NOTE 14: if D11.34 is declared for certain frequency range (D11.32), there shall be no "Rated beam EIRP" declaration (D9.10) for the operating band containing that particular frequency range. | +| D11.35 | Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ | $P_{\text{rated,t,TRP}}$ is declared as TRP OTA power per RIB, declared per supported operating band, per supported RAT. (Note 1, Note 2) | +| NOTE 1: If a BS is capable of 256QAM DL operation but not 1024QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. | | | +| NOTE 2: If a BS is capable of 1024QAM DL operation then up to three rated output power declarations may be made. One declaration is applicable when configured for 1024QAM transmissions, a different declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when configured neither for 256 QAM nor 1024QAM transmissions. | | | + +## 4.11 Test signal configurations for testing + +### 4.11.1 General + +The test configurations shall be constructed using the methods defined below subject to the parameters declared by the manufacturer as listed in clause 4.10. + +For test contiguous spectrum operation configurations used in receiver tests only the carriers in the outermost frequency positions in the *Base Station RF Bandwidth* need to be generated by the test equipment. For non-contiguous spectrum operation test configurations used in receiver tests, outermost carriers for each sub-block need to be generated by the test equipment. + +The applicable test models for generation of the carrier transmit test signal are defined in clause 4.12.2. + +NOTE: If required, carriers are shifted to align with the channel raster. + +## 4.11.1A NR Test signal used to build Test Configurations + +The signal's Channel Bandwidth and Subcarrier spacing used to build NR Test Configurations shall be selected according to table 4.11.1A-1. + +**Table 4.11.1A-1: Signal to be used to build NR TCs** + +| Operating Band characteristics | | $F_{DL\_high} - F_{DL\_low} < 100$ MHz | $F_{DL\_high} - F_{DL\_low} \geq 100$ MHz | +|--------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------|-------------------------------------------| +| TC signal characteristics | BW channel | 5 MHz (Note 1) | 20 MHz (Note 1) | +| | Subcarrier spacing | Smallest supported subcarrier spacing | | +| NOTE 1: If this channel bandwidth is not supported, the narrowest supported channel bandwidth shall be used. | | | | + +## 4.11.2 Test signal configurations + +### 4.11.2.1 ATCR1: UTRA multicarrier operation + +#### 4.11.2.1.1 General + +The purpose of ATCR1 is to test UTRA OTA multi-carrier aspects. + +#### 4.11.2.1.2 ATCR1a generation + +ATCR1a should be constructed using the following method: + +- The *Base Station RF Bandwidth* shall be the declared maximum radiated *Base Station RF Bandwidth* for contiguous operation (see table 4.10-1, D9.18). +- Place one UTRA FDD carrier adjacent to the upper *Base Station RF Bandwidth edge* and one UTRA FDD carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{offset, RAT}$ shall apply. +- For transmitter tests, alternately place a UTRA FDD carrier adjacent to the already placed carriers at the low and high *Base Station RF Bandwidth edges* until there is no more space to fit a carrier or the beam does not support more carriers. The nominal carrier spacing defined in clause 4.6 shall apply. +- The carrier(s) may be shifted maximum 100 kHz towards lower frequencies for $B_{RFBW}$ and $M_{RFBW}$ and towards higher frequencies for $T_{RFBW}$ to align with the channel raster. + +#### 4.11.2.1.3 ATCR1b generation + +ATCR1b is constructed using the following method: + +- The *Base Station RF Bandwidth* shall be the declared maximum radiated *Base Station RF Bandwidth* for contiguous operation (see table 4.10-1, D6.20). +- Place one UTRA TDD carrier adjacent to the upper *Base Station RF Bandwidth edge* and one UTRA TDD carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{offset, RAT}$ shall apply. +- For transmitter tests, alternately place a UTRA TDD carrier adjacent to the already placed carriers at the low and high *Base Station RF Bandwidth edges* until there is no more space to fit a carrier or the beam does not support more carriers. The nominal carrier spacing defined in clause 4.6 shall apply. + +#### 4.11.2.1.4 ATCR1 power allocation + +Set the number of carriers to the number of carriers at maximum TRP (see table 4.10-1, D9.14). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +#### 4.11.2.2 ANTcR1: UTRA FDD multicarrier non-contiguous operation + +##### 4.11.2.2.1 General + +The purpose of ANTcR1 is to test UTRA FDD multicarrier non-contiguous aspects. + +##### 4.11.2.2.2 ANTcR1 generation + +ANTcR1 is constructed as NTC1a in TS 37.141 [13], clause 4.8.1a.1. + +ANTcR1 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* for non-contiguous operation (see table 4.10-1, D6.21). The *Base Station RF Bandwidth* consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum *Base Station RF Bandwidth* for non-contiguous operation. +- For transmitter tests, place one UTRA carrier adjacent to the upper *Base Station RF Bandwidth edge* and one UTRA carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For receiver tests, place one UTRA carrier adjacent to the upper *Base Station RF Bandwidth edge* and one UTRA carrier adjacent to the lower *Base Station RF Bandwidth edge*. For single-band operation, if the maximum *Base Station RF Bandwidth* for non-contiguous operation is at least 35 MHz and the beam supports at least 4 UTRA FDD carriers, place a UTRA FDD carrier adjacent to each already placed carrier for each sub-block. The nominal carrier spacing defined in clause 4.6 shall apply. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{offset, RAT}}$ for the carrier adjacent to the sub-block gap. +- The UTRA FDD carrier in the lower sub-block may be shifted maximum 100 kHz towards lower frequencies and the UTRA FDD carrier in the upper sub-block may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. + +##### 4.11.2.2.3 ANTcR1 power allocation + +Set the number of carriers to the number of carriers at maximum TRP (see table 4.10-1, D9.14). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +#### 4.11.2.3 ATcR2: E-UTRA multicarrier operation + +##### 4.11.2.3.1 General + +The purpose of ATcR2a is to test E-UTRA multi-carrier aspects excluding CA occupied bandwidth. + +The purpose of ATcR2b is to test E-UTRA contiguous CA occupied bandwidth. + +##### 4.11.2.3.2 ATcR2a generation + +ATcR2a is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* for contiguous operation (see table 4.10-1, D9.18). + +- Select the narrowest supported E-UTRA carrier and place it adjacent to the low *Base Station RF Bandwidth edge*. Place a 5 MHz E-UTRA carrier adjacent to the high *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, select as many 5 MHz E-UTRA carriers that the beam supports and that fit in the rest of the *Base Station RF Bandwidth*. Place the carriers adjacent to each other starting from the high *Base Station RF Bandwidth edge*. The nominal carrier spacing defined in clause 4.6 shall apply. The specified $F_{\text{offset, RAT}}$ shall apply. +- If 5 MHz E-UTRA carriers are not supported by the beam the narrowest supported *channel bandwidth* (see table 4.10-1, D9.6) shall be selected instead. + +The test configuration should be constructed on a per band basis for all component carriers of the inter-band CA bands declared to be supported by the beam (see table 4.10-1, D9.20). All configured component carriers are transmitted simultaneously in the tests where the transmitter should be on. + +#### 4.11.2.3.3 ATCR2b generation + +ATCR2b is constructed on a per band basis using the following method: + +- Of all component carrier combinations supported by the beam, those which have smallest or largest sum of *channel bandwidth* of component carrier, shall be tested. Of all component carrier combinations which have smallest or largest sum of channel bandwidth of component carriers supported by the BS, only one combination having largest sum and one combination having smallest sum shall be tested irrespective of the number of component carriers. +- Of all component carrier combinations which have same sum of *channel bandwidth* of component carrier, select those with the narrowest carrier at the lower *Base Station RF Bandwidth edge*. +- Of the combinations selected in the previous step, select one with the narrowest carrier at the upper *Base Station RF Bandwidth edge*. +- If there are multiple combinations fulfilling previous steps, select the one with the smallest number of component carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier being adjacent to the lowest carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier being adjacent to the highest carrier +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier being adjacent to the carrier which has been selected in the previous step. +- If there are multiple combinations fulfilling previous steps, repeat the previous step until there is only one combination left. +- The nominal carrier spacing defined in clause 4.6 shall apply. + +#### 4.11.2.3.4 ATCR2 power allocation + +Set the number of carriers to the number of carriers at maximum TRP (see table 4.10-1, D9.14). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +For a beam declared to support only CA operation (see table 4.10-1, D6.23), set the power spectral density of each carrier to the same level so that the sum of the carrier power equals the same value as above. + +#### 4.11.2.4 ANTCR2: E-UTRA multicarrier non-contiguous operation + +##### 4.11.2.4.1 General + +The purpose of ANTCR2 is to test E-UTRA multicarrier non-contiguous aspects. + +##### 4.11.2.4.2 ANTCR2 generation + +ANTCR2 is constructed as NTC2 in TS 37.141 [13], clause 4.8.2a.1 + +ANTCR2 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* for non-contiguous operation (see table 4.10-1, D9.19). The *Base Station RF Bandwidth* consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum radiated *Base Station RF Bandwidth* (see table 4.10-1, D9.17). +- For transmitter tests, place a 5 MHz E-UTRA carrier adjacent to the upper *Base Station RF Bandwidth edge* and a 5 MHz E-UTRA carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. If 5 MHz E-UTRA carriers are not supported by the beam, the narrowest supported *channel bandwidth* shall be selected instead. +- For receiver tests, place a 5 MHz E-UTRA carrier adjacent to the upper *Base Station RF Bandwidth edge* and a 5 MHz E-UTRA carrier adjacent to the lower *Base Station RF Bandwidth edge*. If 5 MHz E-UTRA carriers are not supported by the beam, the narrowest supported *channel bandwidth* shall be selected instead. +- For single-band operation receiver tests, if the remaining gap is at least 15 MHz plus two times the *channel bandwidth* used in the previous step and the beam supports at least 4 E-UTRA carriers, place an E-UTRA carrier of this *channel bandwidth* adjacent to each already placed carrier for each sub-block. The nominal carrier spacing defined in clause 4.5 shall apply. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{offset, RAT}}$ for the carrier adjacent to the sub-block gap. + +##### 4.11.2.4.3 ANTCR2 power allocation + +Set the number of carriers to the number of carriers at maximum EIRP (see table 4.10-1, D9.14). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +#### 4.11.2.5 ATCR3: UTRA and E-UTRA multi-RAT operation + +##### 4.11.2.5.1 General + +The purpose of ATCR3 is to test UTRA and E-UTRA multi-RAT aspects. + +If the maximum EIRP and total number of supported carriers at maximum EIRP are not simultaneously supported in multi-RAT operations, two instances of ATCR3 shall be generated using the following values for rated transmitter TRP and the total number of supported carriers: + +- 1) The maximum EIRP and the reduced number of supported carriers at the maximum EIRP in multi-RAT operations. +- 2) The reduced maximum EIRP at the total number of supported carriers in multi-RAT operations and the total number of supported carriers. + +Tests that use ATCR3 shall be performed using both instances 1) and 2) of ATCR3. + +#### 4.11.2.5.2 ATCR3a generation + +ATCR3a is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* (see table 4.10-1 D9.17). +- Select an FDD UTRA carrier to be placed at the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- Place a 5 MHz E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. If that is not possible use the narrowest E-UTRA carrier supported by the beam. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, alternately add FDD UTRA carriers at the low end and 5 MHz E-UTRA carriers at the high end adjacent to the already placed carriers until the *Base Station RF Bandwidth* is filled or the total number of supported carriers (see table 4.10-1, D9.14) is reached. The nominal carrier spacing defined in clause 4.6 shall apply. + +#### 4.11.2.5.3 ATCR3b generation + +ATCR3b is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* (see table 4.10-1 D9.17). +- Select a UTRA TDD carrier to be placed at the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- Place a 5 MHz E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. If that is not possible use the narrowest E-UTRA carrier supported by the beam. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, alternately add UTRA TDD carriers at the low end and 5 MHz E-UTRA carriers at the high end adjacent to the already placed carriers until the *Base Station RF Bandwidth* is filled or the total number of supported carriers is reached. The nominal carrier spacing defined in clause 4.6 shall apply. + +#### 4.11.2.5.4 ATCR3 power allocation + +For ATCR3a set the number of carriers to the reduced number of carriers at maximum TRP in multi-RAT operations (see table 4.10-1, D9.23) and set each carrier to maximum EIRP (see table 4.10-1, D9.11). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +#### 4.11.2.6 ANTCR3: UTRA and E-UTRA multi-RAT non-contiguous operation + +##### 4.11.2.6.1 General + +The purpose of ANTCR3 is to test UTRA and E-UTRA multi-RAT non-contiguous aspects. + +##### 4.11.2.6.2 ANTCR3 generation + +ANTCR3 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* for non-contiguous operation (see table 4.10-1, D6.21). The *Base Station RF Bandwidth* consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum *Base Station RF Bandwidth* for non-contiguous operation. + +- For transmitter tests, place an UTRA carrier at the lower *Base Station RF Bandwidth edge* and a 5 MHz E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. If 5 MHz E-UTRA carriers are not supported by the beam, the narrowest supported *channel bandwidth* shall be selected instead. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. In case rated transmitter TRP per RIB is not reached, the narrowest E-UTRA channel BW which supports the rated carrier OTA BS power shall be selected. If still there is some output power room, alternately place an E-UTRA carrier of this BW adjacent to the carrier at the lower *Base Station RF Bandwidth edge* and UTRA carrier adjacent to the carrier at the upper *Base Station RF Bandwidth edge* until the rated transmitter TRP per RIB or the total number of supported carriers is reached. +- For receiver tests, place an UTRA carrier at the lower *Base Station RF Bandwidth edge* and a 5 MHz E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. If 5 MHz E-UTRA carriers are not supported by the beam, the narrowest supported *channel bandwidth* shall be selected instead. The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- For single-band operation receiver tests, if the remaining gap is at least 20 MHz plus the *channel bandwidth* of the E-UTRA carrier used in the previous step and the beam supports at least 2 UTRA and 2 E-UTRA carriers, place a E-UTRA carrier of this *channel bandwidth* adjacent to the carrier at the lower *Base Station RF Bandwidth edge* and UTRA carrier adjacent to the carrier at the upper *Base Station RF Bandwidth edge*. The nominal carrier spacing defined in clause 4.6 shall apply. The UTRA FDD may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{offset, RAT}}$ for the carrier adjacent to the sub-block gap. + +#### 4.11.2.6.3 ANTCR3 power allocation + +For case (1) in clause 4.11.2.6.1 set the number of carriers to the reduced number of carriers at maximum TRP in multi-RAT operations (see table 4.10-1, D9.23). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level unless the rated carrier output power for RATs are different so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +For case (2) in clause 4.11.2.6.1 set the number of carriers to the reduced number of carriers at maximum TRP (see table 4.10-1, D9.14) and set each carrier to the reduced maximum TRP at the total number of supported carriers in multi-RAT operations (see table 4.10-1, D9.24) for the tested *beam direction pair*. + +#### 4.11.2.7 ATCR4: Single carrier for receiver tests + +##### 4.11.2.7.1 ATCR4a generation + +ATCR4a is constructed using the following method: + +- Place a single (UTRA FDD) carrier in the middle of the maximum radiated *Base Station RF Bandwidth*. The carrier may be shifted maximum 100 kHz towards lower frequencies for $B_{\text{RFBW}}$ and $M_{\text{RFBW}}$ and towards higher frequencies for $T_{\text{RFBW}}$ to align with the channel raster. + +##### 4.11.2.7.2 ATCR4b generation + +ATCR4b is constructed using the following method: + +- Place the narrowest supported E-UTRA carrier in the middle of the maximum radiated *Base Station RF Bandwidth*. + +##### 4.11.2.7.3 ATCR4c generation + +ATCR4c is constructed using the following method: + +- Place a single UTRA TDD carrier in the middle of the maximum radiated *Base Station RF Bandwidth*. + +#### 4.11.2.7.3A ATCR4d generation + +ATCR4d is constructed using the following method: + +- Place a single NR carrier as specified in clause 4.11.1A in the middle of the maximum radiated *Base Station RF Bandwidth*. + +#### 11.2.7.4 ATCR4 power allocation + +Set the beam EIRP on the carrier such that it's EIRP level is equal to the sum of *rated beam EIRPs* (see table 4.10-1, D9.12) when transmitting the maximum supported carriers at the *beam peak direction* (see table 4.10-1, D9.16). + +#### 4.11.2.8 ATCR5: MB-MSR operation + +##### 4.11.2.8.1 ATCR5a: MB-MSR test configuration for full carrier allocation + +###### 4.11.2.8.1.1 General + +The purpose of ATCR5a is to test beams which have been generated using transceiver units supporting operation in multiple operating bands through common active electronic components(s), considering maximum supported number of carriers. + +###### 4.11.2.8.1.2 ATCR5a generation + +ATCR5a is based on re-using the existing test configurations applicable per band on beams generated using multi-band transceiver units and hence have declared multi-band dependencies (see table 4.10-1, D9.16). ATCR5a is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* (see table 4.10-1, D9.17). +- The number of carriers of each supported operating band shall be the declared maximum number of supported carriers by the multi-band dependencies in each band (see table 4.10-1, D9.16). Carriers shall first be placed at the outermost edges of the declared maximum radiated *Radio Bandwidth* (see table 4.10-1, D9.17). Additional carriers shall next be placed at the edges of the *Base Station RF Bandwidths*, if possible. +- The allocated *Base Station RF Bandwidth* of the outermost bands shall be located at the outermost edges of the declared maximum radiated *Radio Bandwidth* (see table 4.10-1, D9.17). +- Each concerned band shall be considered as an independent band and the corresponding test configuration shall be generated in each band. The mirror image of the single band test configuration shall be used in the highest band being tested for the beam. +- Band category and declared per band capability set (see table 4.10-1, D9.25) shall be used to generate per band RAT/carrier allocation according to table 4.11.2.8.1.2-1 for each band category and radiated capability set. If an operating band with multi-band dependencies supports three carriers only, two carriers shall be placed in one band according to the relevant test configuration while the remaining carrier shall be placed at the edge of the maximum *Radio Bandwidth* (see table 4.10-1, D9.17) in the other band. +- If the sum of the maximum *Base Station RF bandwidths* of each of the supported operating bands is greater than the declared *Total RF Bandwidth* BWtot (D9.32) of transmitter and receiver for the declared band combinations of the BS, then repeat the steps above for test configurations where the *Base Station RF Bandwidth* of one of the operating band shall be reduced so that the declared *Total RF Bandwidth* is not exceeded and vice versa. +- If the sum of the maximum number of supported carrier of each supported operating bands with multi-band dependencies (see table 4.10-1, D9.16) is larger than the declared t Total number of supported carriers for operating bands with multi-band dependencies (see table 4.10-1, D9.27), repeat the steps above for test configurations where in each test configuration the number of carriers of one of the operating band shall be reduced so that the total number of supported carriers is not exceeded and vice versa. + +**Table 4.11.2.8.1.2-1: The applicability of test configuration in each band** + +| BC | RCSA1 | RCSA2 | RCSA3 | RCSA3A | RCSA3B | RCSA4 | RCSA5 | +|-----|--------|--------|--------|--------|--------|--------|--------| +| BC1 | ATCR1a | ATCR2a | ATCR3a | ATCR7 | ATCR9 | ATCR1a | ATCR2a | +| BC2 | ATCR1a | ATCR2a | ATCR3a | ATCR7 | ATCR9 | ATCR1a | ATCR2a | +| BC3 | ATCR1b | ATCR2a | ATCR3b | ATCR7 | N/A | ATCR1b | ATCR2a | + +#### 4.11.2.8.1.3 ATCR5a power allocation + +Set the number of carriers to the total number of supported carriers for the declared multi-band dependencies (see table 4.10-1, D9.27). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +If the allocated number of carriers in an operating band exceeds the declared number of carriers at maximum TRP in an operating band (see table 4.10-1, D9.14) the carriers should if possible be allocated to a different operating band. + +#### 4.11.2.8.2 ATCR5b: MB-MSR test configuration with high PSD per carrier + +##### 4.11.2.8.2.1 General + +The purpose of ATCR5b is to test multi-band operation aspects considering higher PSD cases with reduced number of carriers and non-contiguous operation (if supported) in multi-band mode. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth and the narrowest supported E-UTRA channel bandwidth for each operating band shall be used in the test configuration. + +##### 4.11.2.8.2.2 ATCR5b generation + +ATCR5b is based on re-using the existing test configurations applicable for operating bands using multi-band transceiver units and hence have declared multi-band dependencies (see table 4.10-1, D9.16). ATCR5b is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* (see table 4.10-1, D9.17). +- The allocated *Radio Bandwidth* of the outermost bands shall be located at the outermost edges of the declared maximum *Radio Bandwidth* of the operating band with multi-band dependencies (see table 4.10-1, D9.26). +- The maximum number of carriers is limited to two per band. Carriers shall be placed at the outermost edges of the declared maximum *Radio Bandwidth* of the operating band with multi-band dependencies (see table 4.10-1, D9.26). +- Each concerned band shall be considered as an independent band and the corresponding test configuration for non-contiguous operation shall be generated in each band according to table 4.11.2.8.2.2-1. The mirror image of the single band test configuration shall be used in the highest band being tested. +- For AAS BS supporting RCSA4 in the band and supports three carriers only, two carriers shall be placed in one band according to ATC2 while the remaining carrier shall be placed at the edge of the maximum *Base Station RF Bandwidth* in the other band. +- If the sum of the maximum *Base Station RF bandwidths* of each of the supported operating bands is greater than the declared *Total RF Bandwidth* $BW_{\text{tot}}$ (D9.32) of transmitter and receiver for the declared band combinations of the BS, then repeat the steps above for test configurations where the *Base Station RF Bandwidth* of one of the operating band shall be reduced so that the declared *Total RF Bandwidth* of the operating band with multi-band dependencies (see table 4.10-1, D9.26) is not exceeded and vice versa. + +**Table 4.11.2.8.2.2-1: The applicability of test configuration in each band** + +| BC | RCSA1 | RCSA2 | RCSA3 | RCSA3A | RCSA3B | RCSA4 | RCSA5 | +|-----------|--------------|--------------|--------------|---------------|---------------|--------------|--------------| +| BC1 | ANTCR1a | ANTCR2 | ANTCR3 | ANTCR7 | ANTCR8 | ANTCR1 | ANTCR2 | +| BC2 | ANTCR1a | ANTCR2 | ANTCR3 | ANTCR7 | ANTCR8 | ANTCR1 | ANTCR2 | +| BC3 | ATCR1b | ANTCR2 | ANTCR3 | ANTCR7 | N/A | N/A | ANTCR2 | + +#### 4.11.2.8.2.3 ATCR5b power allocation + +Set the number of carriers to the total number of supported carriers for the declared multi-band dependencies (see table 4.10-1, D9.27). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +If the sum of the TRP for all carriers in an operating band(s) exceeds the sum of the maximum TRP per carrier (see table 4.10-1, D9.14) for the number of carriers transmitted in multi-band operation, the exceeded part shall, if possible, be reallocated into the other band(s). If the TRP allocated for a carrier exceeds the declared maximum TRP, the exceeded power shall, if possible, be reallocated into the other carriers. + +#### 4.11.2.9 ATCR6: Single carrier for transmitter tests + +##### 4.11.2.9.1 ATCR6a generation + +ATCR6a is constructed using the following method: + +- Place a single UTRA carrier at the RF channel to be tested. + +##### 4.11.2.9.2 ATCR6b generation + +ATCR6b is constructed using the following method: + +- Place a 5 MHz E-UTRA carrier i at the RF channel to be tested. If 5 MHz carriers are not supported by the beam the narrowest supported channel BW shall be selected instead. + +##### 4.11.2.9.3 Void + +##### 4.11.2.9.3A ATCR6d generation + +ATCR6d is constructed using the following method: + +- Place a single NR carrier as specified in clause 4.11.1A at the RF channel to be tested. + +##### 4.11.2.9.4 ATCR6 power allocation + +Set the number of carriers to 1. Set the beam parameters to those appropriate for the beam identifier of the beam under test and to the direction to be tested from the beam declarations (see table 4.10-1, D9.3 - D9.13). + +## 4.11.2.10 ATCR7: E-UTRA and NR multi RAT operation + +### 4.11.2.10.1 General + +The purpose of ATCR7 is to test E-UTRA and NR multi-RAT aspects. + +If the maximum EIRP and total number of supported carriers at maximum EIRP are not simultaneously supported in Multi-RAT operations, two instances of ATCR7 shall be generated using the following values for rated transmitter TRP and the total number of supported carriers: + +- 1) The maximum EIRP and the reduced number of supported carriers at the maximum EIRP in Multi-RAT operations. +- 2) The reduced maximum EIRP at the total number of supported carriers in Multi-RAT operations and the total number of supported carriers. + +Tests that use ATCR7 shall be performed using both instances 1) and 2) of ATCR7. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth for the operating band shall be used in the test configuration. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5 MHz unless the BS does not support 5 MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth for the operating band. + +### 4.11.2.10.2 ATCR7 generation + +ATCR7 is only applicable for a BS that supports E-UTRA and NR. ATCR7 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* (see table 4.10-1 D9.17). +- Select a NR carrier as specified in subclause 4.11.1A to be placed at the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- Place an E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, alternately add NR carriers as specified in subclause 4.11.1A at the low end and E-UTRA carriers at the high end adjacent to the already placed carriers until the *Base Station RF Bandwidth* is filled or the total number of supported carriers (see table 4.10-1, D9.14) is reached. The nominal carrier spacing defined in subclause 4.6 shall apply. + +### 4.11.2.10.3 ATCR7 power allocation + +- a) Unless otherwise stated, set each carrier to the same power so that the sum of the carrier powers equals the rated total output power as appropriate for the test configuration according to manufacturer's declarations in subclause 4.10. +- b) In case that ATCR7 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in subclause 4.10, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacturer's declaration the power in the other RAT(s) does not need to be increased. + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level. + +## 4.11.2.11 ANTTCR7: E-UTRA and NR multi RAT non-contiguous operation + +## 4.11.2.11 ANTCT7: E-UTRA and NR multi RAT non-contiguous operation + +### 4.11.2.11.1 General + +The purpose of ANTCT7 is to test E-UTRA and NR multi RAT non-contiguous aspects. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth shall be used in the test configuration. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5 MHz unless the BS does not support 5 MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth. + +### 4.11.2.11.2 ANTCT7 generation + +ANTCT7 is only applicable for a BS that supports E-UTRA and NR. ANTCT7 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* for non-contiguous operation (see table 4.10-1, D6.21). The *Base Station RF Bandwidth* consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum *Base Station RF Bandwidth* for non-contiguous operation. +- For transmitter tests, place an NR carrier as specified in subclause 4.11.1A at the lower *Base Station RF Bandwidth edge* and an E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. In case rated transmitter TRP per RIB is not reached, the narrowest E-UTRA and/or NR channel BW which supports the rated carrier OTA BS power shall be selected. If still there is some output power room, alternately place an E-UTRA carrier of this BW adjacent to the carrier at the lower *Base Station RF Bandwidth edge* and NR carrier adjacent to the carrier at the upper *Base Station RF Bandwidth edge* until the rated transmitter TRP per RIB or the total number of supported carriers is reached. +- For receiver tests, place a NR carrier as specified in subclause 4.11.1A at the lower *Base Station RF Bandwidth edge* and an E-UTRA carrier at the upper *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{offset, RAT}}$ for the carrier adjacent to the sub-block gap. + +### 4.11.2.11.3 ANTCT7 power allocation + +- a) Unless otherwise stated, set each carrier to the same power so that the sum of the carrier powers equals the rated total output power appropriate for the test configuration according to manufacturer's declarations in subclause 4.10. +- b) In case that ANTCT7 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in subclause 4.10, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacturer's declaration the power in the other RAT(s) does not need to be increased. + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level unless the rated carrier output power for RATs are different so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +## 4.11.2.12 ATCT8: NR multicarrier operation + +### 4.11.2.12.1 General + +The purpose of ATCT8a is to test NR multi-carrier aspects excluding CA occupied bandwidth. + +The purpose of ATCR8b is to test NR Contiguous CA occupied bandwidth. + +#### 4.11.2.12.2 ATCR8a generation + +ATCR8 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared radiated *Base Station RF Bandwidth* for contiguous operation (see table 4.10-1, D9.18). +- Select the NR carrier as specified in clause 4.11.1A and place it adjacent to the low *Base Station RF Bandwidth edge*. Place a similar NR carrier adjacent to the high *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For transmitter tests, select as many similar NR carriers that the beam supports and that fit in the rest of the *Base Station RF Bandwidth*. Place the carriers adjacent to each other starting from the high Base Station RF Bandwidth edge. The nominal carrier spacing defined in clause 4.6 shall apply. The specified $F_{\text{offset, RAT}}$ shall apply. + +The test configuration should be constructed on a per band basis for all component carriers of the inter-band CA bands declared to be supported by the beam (see table 4.10-1, D9.20). All configured component carriers are transmitted simultaneously in the tests where the transmitter should be on. + +#### 4.11.2.12.3 ATCR8b generation + +ATCR8b is constructed on a per band basis using the following method: + +- All component carrier combinations supported by the beam, which have different sum of *channel bandwidth* of component carrier, shall be tested. For all component carrier combinations which have the same sum of *channel bandwidth* of component carriers, only one of the component carrier combinations shall be tested. +- Of all component carrier combinations which have same sum of *channel bandwidth* of component carrier, select those with the narrowest carrier at the lower *Base Station RF Bandwidth edge*. +- Of the combinations selected in the previous step, select one with the narrowest carrier at the upper *Base Station RF Bandwidth edge*. +- If there are multiple combinations fulfilling previous steps, select the one with the smallest number of component carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier being adjacent to the lowest carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier being adjacent to the highest carrier +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier being adjacent to the carrier which has been selected in the previous step. +- If there are multiple combinations fulfilling previous steps, repeat the previous step until there is only one combination left. +- The nominal carrier spacing defined in clause 4.6 shall apply. + +#### 4.11.2.12.4 ATCR8 power allocation + +Set the number of carriers to the number of carriers at maximum TRP (see table 4.10-1, D9.14). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +For a beam declared to support only CA operation (see table 4.10-1, D6.23), set the power spectral density of each carrier to the same level so that the sum of the carrier power equals the same value as above. + +#### 4.11.2.13 ANTcR8: NR multicarrier non-contiguous operation + +##### 4.11.2.13.1 General + +The purpose of ANTcR8 is to test NR multicarrier non-contiguous aspects. + +##### 4.11.2.13.2 ANTcR8 generation + +ANTcR8 is constructed using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* for non-contiguous operation (see table 4.10-1, D9.19). The *Base Station RF Bandwidth* consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum radiated *Base Station RF Bandwidth* (see table 4.10-1, D9.17). +- For transmitter tests, place a NR carrier as specified in clause 4.11.1A adjacent to the upper *Base Station RF Bandwidth edge* and a similar NR carrier adjacent to the lower *Base Station RF Bandwidth edge*. The specified $F_{\text{offset, RAT}}$ shall apply. +- For receiver tests, place a NR carrier as specified in clause 4.11.1A adjacent to the upper *Base Station RF Bandwidth edge* and a similar NR carrier adjacent to the lower *Base Station RF Bandwidth edge*. - The sub-block edges adjacent to the *sub-block gap* shall be determined using the specified $F_{\text{offset, RAT}}$ for the carrier adjacent to the *sub-block gap*. + +##### 4.11.2.13.3 ANTcR8 power allocation + +Set the number of carriers to the number of carriers at maximum EIRP (see table 4.10-1, D9.14). + +For EIRP accuracy requirements set each beam to maximum EIRP (see table 4.10-1, D9.10) for the tested *beam direction pair*. + +For all other requirements set the power of each carrier to the same level so that the sum of the carrier powers equals to Rated transmitter TRP per RIB, $P_{\text{rated,t,TRP}}$ (see table 4.10-2, D11.35). + +#### 4.11.2.14 ATcR9: UTRA, E-UTRA and NR multi-RAT operation + +##### 4.11.2.14.1 General + +The purpose of ATcR9 is to test UTRA, E-UTRA and NR multi-RAT aspects. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth for the operating band shall be used in the test configuration. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5 MHz unless the BS does not support 5 MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth for the operating band. + +##### 4.11.2.14.2 ATcR9 generation + +ATcR9 is only applicable for a BS that supports UTRA, E-UTRA and NR. ATcR9 is constructed using the following method: + +For transmitter tests, if the rated total output power and total number of supported carriers are not simultaneously supported in Multi-RAT operations, two instances of ATcR9 shall be generated using the following values for rated total output power and the total number of supported carriers: + +- 1) The rated total output power and the reduced number of supported carriers at the rated total output power in multi-RAT operations + +- 2) The reduced rated total output power at the total number of supported carriers in multi-RAT operations and the total number of supported carriers. + +If the rated total output power and total number of supported carriers are not simultaneously supported in multi-RAT operations, tests that use ATCR9 shall be performed using both instances 1) and 2) of ATCR9. + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth.- Adjacent to the lower Base Station RF Bandwidth edge: Place an NR carrier. The specified FOffset-RAT shall apply. +- Adjacent to the upper Base Station RF Bandwidth edge: Place a E-UTRA carrier. The specified FOffset-RAT shall apply. +- Place UTRA carrier adjacent to the already placed E-UTRA carrier. +- The UTRA FDD may be shifted maximum 100 kHz towards lower frequencies to align with the channel raster. +- For transmitter tests, alternately add NR carriers at the low end and E-UTRA carriers at the high end adjacent to the already placed carriers until the Base Station RF Bandwidth is filled or the total number of supported carriers is reached. The nominal carrier spacing defined in subclause 4.6 shall apply. + +#### 4.11.2.14.3 ATCR9 power allocation + +- a) Unless otherwise stated, set each carrier to the same power so that the sum of the carrier powers equals the rated total output power as appropriate for the test configuration according to manufacturer's declarations in subclause 4.10. +- b) In case that ATCR9 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in subclause 4.10, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacture's declaration the power in the other RAT(s) does not need to be increased. + +#### 4.11.2.15 ANTCCR9: UTRA, E-UTRA and NR multi-RAT non-contiguous operation + +The purpose of ANTCCR9 is to test UTRA, E-UTRA and NR multi RAT non-contiguous aspects. + +Unless otherwise stated, for all test configurations in this section, the narrowest supported NR channel bandwidth and lowest SCS for that bandwidth shall be used in the test configuration. + +Unless otherwise stated, the E-UTRA bandwidth shall be 5 MHz unless the BS does not support 5 MHz E-UTRA, in which case the E-UTRA bandwidth shall be the lowest supported bandwidth. + +#### 4.11.2.15.1 ANTCCR9 generation + +ANTCCR9 is only applicable for a BS that supports UTRA, E-UTRA and NR. ANTCCR9 is constructed using the following method: + +- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth for non-contiguous operation. The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum Base Station RF Bandwidth. +- Adjacent to the lower Base Station RF Bandwidth edge: + - Place an NR carrier. The specified FOffset-RAT shall apply. +- Adjacent to the upper Base Station RF Bandwidth edge: + +- Place an E-UTRA carrier. The specified $F_{\text{Offset-RAT}}$ shall apply. +- Place a UTRA carrier adjacent to the lower sub-block edge of the upper sub-block. +- For transmitter tests, place one UTRA adjacent to the upper sub-block edge of the lower sub-block. The nominal carrier spacing defined in subclause 4.6 shall apply. In case transmitter TRP per RIB is not reached, for the NR carrier adjacent to the lower Base Station RF Bandwidth edge, the narrowest NR channel BW which supports rated carrier output power shall be selected. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{Offset-RAT}}$ for the carrier adjacent to the sub-block gap. The carrier(s) may be shifted maximum 100 kHz towards higher frequencies to align with the channel raster. + +#### 4.11.2.15.2 ANTCR9 power allocation + +- Unless otherwise stated, set each carrier to the same power unless the rated carrier output power for RATs are different so that the sum of the carrier powers equals the rated total output power appropriate for the test configuration according to manufacturer's declarations in subclause 4.10. +- In case that ANTCR9 is configured for testing modulation quality, the power allocated per carrier for the RAT on which modulation quality is measured shall be the highest possible for the given modulation configuration according to the manufacturer's declarations in subclause 4.10, unless that power is higher than the level defined by case a). The power of the remaining carriers from other RAT(s) shall be set to the same level as in case a). + +If in the case of b) the power of one RAT needs to be reduced in order to meet the manufacture's declaration the power in the other RAT(s) does not need to be increased. + +## 4.12 RF channels and test models + +### 4.12.1 RF channels + +For single carrier tests unless otherwise stated the tests shall be performed with a single carrier at each of the RF channels B, M and T. + +Many tests in this TS are performed with the maximum radiated *Base Station RF Bandwidth* located at the bottom, middle and top of the supported frequency range in the operating band. These are denoted as $B_{\text{RFBW}}$ (bottom), $M_{\text{RFBW}}$ (middle) and $T_{\text{RFBW}}$ (top). + +- Unless otherwise stated, the test shall be performed at $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ defined as following: +- $B_{\text{RFBW}}$ : maximum *Base Station RF Bandwidth* located at the bottom of the supported frequency range in the operating band. +- $M_{\text{RFBW}}$ : maximum *Base Station RF Bandwidth* located in the middle of the supported frequency range in the operating band. $M_{\text{RFBW}}$ may be shifted maximum 100 kHz towards lower frequencies to align carriers with the channel raster. +- $T_{\text{RFBW}}$ : maximum *Base Station RF Bandwidth* located at the top of the supported frequency range in the operating band. + +For the test of certain RF requirements the present specification refers to test procedures defined in the single-RAT specifications [2], [3], [4], [5]. In this case, the interpretation of the RF channels to be tested shall be according to the definitions in the corresponding single-RAT specifications [2], [3], [4], [5]. + +For an operating band which has multi-band beam dependencies capable of dual-band operation, unless otherwise stated, the test shall be performed at $B'_{\text{RFBW\_T'_{\text{RFBW}}}}$ and $B'_{\text{RFBW\_T'_{\text{RFBW}}}}$ defined as following: + +- $B'_{\text{RFBW\_T'_{\text{RFBW}}}}$ : the *Base Station RF Bandwidths* located at the bottom of the supported frequency range in the lower operating band and at the highest possible simultaneous frequency position, within the maximum *Radio Bandwidth*, in the upper operating band. + +- $B'_{\text{RFBW\_T\_RFBW}}$ : the *Base Station RF Bandwidths* located at the top of the supported frequency range in the upper operating band and at the lowest possible simultaneous frequency position, within the maximum *Radio Bandwidth*, in the lower operating band. + +NOTE: $B_{\text{RFBW\_T\_RFBW}} = B'_{\text{RFBW\_T\_RFBW}} = B_{\text{RFBW\_T\_RFBW}}$ when the declared maximum radiated *Radio Bandwidth* (see table 4.10-1, D9.17) spans both operating bands. $B_{\text{RFBW\_T\_RFBW}}$ means the *Base Station RF Bandwidths* are located at the bottom of the supported frequency range in the lower operating band and at the top of the supported frequency range in the upper operating band. + +When a test is performed by a test laboratory, the position of $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in each supported operating band, the position of $B_{\text{RFBW\_T\_RFBW}}$ and $B'_{\text{RFBW\_T\_RFBW}}$ in the supported operating band combinations shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies. + +## 4.12.2 Test models + +a) Unless otherwise stated, carriers used for transmitter tests shall be configured as follows: + +- UTRA FDD carriers shall be configured according to TM1 as defined in TS 25.141 [10], clause 6.1.1.1. +- UTRA TDD carriers shall be configured according to table 6.1A as defined in TS 25.142 [11], clause 6.2.4.1.2. +- E-UTRA carriers shall be configured according to E-TM1.1 as defined in clause 6.1.1.1 of TS 36.141 [12], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [12]. + +For BC3 CS3 BS testing, E-UTRA carriers shall be configured according to E-TM1\_BC3CS3 defined in annex E of TS 37.141 [13]. + +- NR carriers shall be configured according to NR-FR1-TM1.1 as defined in clause 4.9.2.2 of TS 38.141-1 [35], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [35]. + +For BC3 BS testing, NR carriers shall be configured according to NR-FR1-TM1.1\_BC3CS16/17 defined in Annex E of TS 37.141 [13]. + +b) The configuration of the carriers in test configurations used for testing modulation quality and frequency error shall be as follows: + +- For the case that modulation accuracy is measured for UTRA FDD, the UTRA FDD carriers shall be configured according to the supported TM1 and TM4, as defined in TS 25.141 [10], clause 6.1.1, whilst any remaining carriers from other RAT(s) shall be configured according to bullet a) above. + +If HS-PDSCH transmission using 16QAM is supported, the UTRA FDD carriers shall be configured according to TM4 and TM5, as defined in TS 25.141 [10], clause 6.1.1. + +- For the case that modulation accuracy is measured for E-UTRA, the E-UTRA carriers shall be configured according to the supported E-TM3.1, E-TM3.2, E-TM3.3 and E-TM2 as defined in clause 6.1.1 of TS 36.141 [12], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [12], whilst any remaining carriers from other RAT(s) shall be configured according to bullet a) above. +- If transmission using 256QAM is supported, the E-UTRA carriers shall be configured according to E-TM2a and E-TM3.1a as defined in clause 6.1.1 of TS 36.141 [12], and data content of physical channels and signals as defined in clause 6.1.2. +- If transmission using 1024QAM is supported, the E-UTRA carriers shall be configured according to E-TM2b and E-TM3.1b as defined in clause 6.1.1 of TS 36.141 [12], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [12]. + +For BC3 CS3 BS testing, E-UTRA carriers shall be configured according to E-TM3.1\_BC3CS3, E-TM3.2\_BC3CS3, E-TM3.3\_BC3CS3 and E-TM2\_BC3CS3 defined in Annex E of TS 37.141 [13]. + +- For the case that modulation accuracy is measured for NR, the NR carriers shall be configured according to the supported NR-FR1-TM3.1, NR-FR1-TM3.2, NR-FR1-TM3.3 and NR-FR1-TM2 as defined in clause 4.9.2.2 of TS 38.141-1 [35], and data content of physical channels and signals as defined in + +clause 4.9.2.3 of TS 38.141-1 [35], whilst any remaining carriers from other RAT(s) shall be configured according to bullet a) above. + +- If transmission using 256QAM is supported, the NR carriers shall be configured according to NR-FR1-TM2a and NR-FR1-TM3.1a as defined in clause 4.9.2.2 of TS 38.141-1 [35], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [35]. +- If transmission using 1024QAM is supported, the NR carriers shall be configured according to NR-FR1-TM2b and NR-FR1-TM3.1b as defined in clause 4.9.2.2 of TS 38.141-1 [35], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [35]. + +For BC3 BS testing, NR carriers shall be configured according to NR-FR1-TM3.1\_BC3CS16/17, NR-FR1-TM3.1a\_BC3CS16/17, NR-FR1-TM3.1b\_BC3CS16/17, NR-FR1-TM3.2\_BC3CS16/17, NR-FR1-TM3.3\_BC3CS16/17, NR-FR1-TM2\_BC3CS16/17, NR-FR1-TM2a\_BC3CS16/17 and NR-FR1-TM2b\_BC3CS16/17 defined in Annex E of TS 37.141 [13]. + +c) Unless otherwise stated, transmitter carriers used for receiver tests shall be configured as follows: + +- UTRA FDD carriers shall be configured according to TM1 as defined in TS 25.141 [10], clause 6.1.1.1. +- UTRA TDD carriers shall be configured according to table 6.1A as defined in TS 25.142 [11], clause 6.2.4.1.2. +- E-UTRA carriers shall be configured according to E-TM1.1 as defined in clause 6.1.1.1 of TS 36.141 [12], and data content of physical channels and signals as defined in clause 6.1.2 of TS 36.141 [12]. For BC3 CS3 BS testing, E-UTRA carriers shall be configured according to E-TM1\_BC3CS3 defined in annex E of TS 37.141 [13]. +- NR carriers shall be configured according to NR-FR1-TM1.1 as defined in clause 4.9.2.2 of TS 38.141-1 [35], and data content of physical channels and signals as defined in clause 4.9.2.3 of TS 38.141-1 [35]. For BC3 BS testing, NR carriers shall be configured according to NR-FR1-TM1\_CS3 defined in annex E of TS 37.141 [16]. + +For the test of certain RF requirements clause 5 refers to the test configurations as defined in the single-RAT specifications. In this case, the transmitter test signals and test models as defined within the referred test specification for the RF requirement shall be used. + +## 4.13 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 clause 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. Required manufacturer declarations may be included here. + +#### **X.2 Minimum requirement** + +This clause contains the reference to the clause to the 3GPP reference (or core) specification which defines the minimum requirement. For each requirement, there are separate references for MSR and single RAT, where applicable in the core requirement. If the requirement does not apply to a particular RAT, this is explicitly stated here (rather than through a reference). + +#### **X.3 Test purpose** + +This clause defines the purpose of the test. + +#### **X.4 Method of test** + +##### **X.4.1 General** + +In some cases there are alternative test procedures or initial conditions. In such cases, guidance for which initial conditions and test procedures can be applied are stated here. In the case only one test procedure is applicable, that is stated here. + +#### **X.4.2y First test method** + +##### **X.4.2y.1 Initial conditions** + +This clause defines the initial conditions for each test, including the test environment, the RF channels to be tested and the basic measurement set-up. The test system is assumed to be correctly calibrated as part of the initial conditions. Calibration is not explicitly mentioned. + +##### **X.4.2y.2 Procedure** + +This clause describes the steps necessary to perform the test and provides further details of the test definition like point of access (e.g. test port), domain (e.g. frequency-span), range, weighting (e.g. bandwidth), and algorithms (e.g. averaging). The procedure may comprise data processing of the measurement result before comparison with the test requirement (e.g. average result from several measurement positions). + +##### **X.4.3y Alternative test method (if any)** + +If there are alternative test methods, each is described with its initial conditions and procedures. + +#### **X.5 Test requirement** + +This clause defines the pass/fail criteria for the equipment under test, see clause 4.1.3 Interpretation of measurement results. Test requirements for every minimum requirement referred in clause X.2 are listed here. Cases where minimum requirements do not apply need not be mentioned. + +The test requirements may be different depending on the test method applied. A test requirement for each test method applicable to the respective MSR/Single RAT requirement is given in separate clauses where applicable. + +## **4.14 Reference coordinate system** + +Radiated requirements are stated in terms of electromagnetic characteristics (e.g. EIRP and EIS) at certain angles with respect to the base station. To be able to declare radiated characteristics part of radiated requirements a reference coordinate system is required. The reference coordinate system is should be associated to an identifiable physical feature on the base station enclosure.. The location of the origin and the orientation of the reference coordinate system are for the base station manufacturer to declare. + +The reference coordinate system is created of a Cartesian coordinate system with rectangular axis (x, y, z) and spherical angles ( $\theta$ , $\phi$ ) as showed in figure 4.14-1. + +![Figure 4.14-1: Reference coordinate system. A 3D coordinate system with x, y, and z axes. A vector originates from the origin. The angle between the x-axis and the projection of the vector onto the x/y plane is labeled phi (φ). The angle between the projection of the vector in the x/y plane and the radiating vector is labeled theta (θ).](e9baf350bd23410e8a6df8dc5c68c16b_img.jpg) + +Figure 4.14-1: Reference coordinate system. A 3D coordinate system with x, y, and z axes. A vector originates from the origin. The angle between the x-axis and the projection of the vector onto the x/y plane is labeled phi (φ). The angle between the projection of the vector in the x/y plane and the radiating vector is labeled theta (θ). + +**Figure 4.14-1: Reference coordinate system** + +$\phi$ is the angle in the x/y plane, between the x-axis and the projection of the radiating vector onto the x/y plane and is defined between $-180^\circ$ and $+180^\circ$ , inclusive. $\theta$ is the angle between the projection of the vector in the x/y plane and the radiating vector and is defined between $-90^\circ$ and $+90^\circ$ , inclusive. Note that $\theta$ is defined as positive along the down-tilt angle. + +## 4.15 Co-location requirements + +### 4.15.1 General + +Co-location requirements are requirements which are based on assuming the AAS BS is co-located with another BS of the same base station class. They ensure that both co-located systems can operate with minimal degradation to each other. + +The co-location requirements in Table 4.15-1-1 rely on a *co-location reference antenna* used to mimic a base station to base station co-location scenario. + +**Table 4.15-1-1: Co-location requirements** + +| Clause number | Requirement | Co-location reference antenna operation | Type | +|--------------------|---------------------------------|-----------------------------------------|-------------------------------| +| 6.5 | OTA Transmit ON/OFF power | Measure emission | Mandatory | +| 6.7.6.3
6.7.6.5 | OTA Spurious emission | Measure emission | Optional based on declaration | +| 6.8 | OTA Transmitter intermodulation | Inject the interferer signal | Mandatory | +| 7.6.3 | OTA Blocking | Inject the interferer signal | Optional based on declaration | + +The OTA Transmit ON/OFF power requirement and OTA Transmitter intermodulation requirement are mandatory requirements where the test requirement is derived using the *co-location reference antenna*, which represents the worst-case scenario. + +The *co-location reference antenna* is defined in TS 37.105[6]. + +## 4.15.2 Co-location test antenna + +### 4.15.2.1 General + +Co-location requirements are specified as power levels into or out of the conducted interface of the *co-location reference antenna*. For conformance testing the requirements are translated to the input or output of a *co-location test antenna* (CLTA). + +A CLTA is a practical antenna which can be used to test conformance to the co-location requirements. + +### 4.15.2.2 Co-location test antenna characteristics + +A co-location test antenna is a practical passive antenna that is used for conformance testing of the co-location requirements and is based on the definition of the *co-location reference antenna*. A CLTA shall comply to the requirements specified in Table 4.15.2.2-1. Translation of the requirements to other test antennas is not precluded but suitable translations between the *co-location reference antenna* and test antennas must be provided to demonstrate that the method is within the specified MU. + +The currently defined CLTAs are suitable for testing AAS BSs implemented with a planar antenna array. The method for testing AAS BS with other antenna array implementations is FFS. + +**Table 4.15.2.2-1: CLTA characteristics** + +| Parameter | in-band CLTA | out-of-band CLTAs | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| Vertical radiating dimension (h) | Test object vertical radiating length $\pm 30\%$ | Test object vertical radiating length $\pm 30\%$
(Note 2) | +| Horizontal beam width | $65^\circ \pm 10^\circ$ | $65^\circ \pm 10^\circ$ | +| Vertical beam width | N/A | The half-power vertical beam width of the CLTA equals the narrowest declared vertical beamwidth $\pm 3^\circ$
(Note 2) | +| Polarization (Note 3) | Match (Note 4) | Match to in-band (Note 4) | +| Conducted interface return loss | $> 10\text{dB}$ | $> 10\text{dB}$ | +| NOTE 1: If a multi-column or multi-band antenna is used the column closest to the AAS BS shall be selected while other columns are terminated during testing. | | | +| NOTE 2: The vertical radiating dimension definition shall be used instead of the vertical beam width definition when the test chamber dimensions limit the use of vertical beam width definition. Otherwise the vertical beam width definition shall be used. | | | +| NOTE 3: For BS type 1-O with dual polarization the CLTA has two conducted interfaces each representing one polarization | | | +| NOTE 4: Matched to the polarization of EUT antenna | | | + +### 4.15.2.3 Co-location test antenna alignment + +The alignment between the AAS BS under test and the *co-location test antenna* is specified in Table 4.15.2.3-1 and Figure 4.15.2.3-1. + +**Table 4.15.2.3-1: CLTA alignment tolerances** + +| Parameter | in-band | out-of-band | +|------------------------------------------------------------|----------------------------------|----------------------------------| +| Edge-to-edge separation between the AAS BS and the CLTA, d | $0.1\text{ m} \pm 0.01\text{ m}$ | $0.1\text{ m} \pm 0.01\text{ m}$ | +| Vertical alignment | Centre $\pm 0.01\text{ m}$ | Centre $\pm 0.01\text{ m}$ | +| Front alignment | Radome front $\pm 0.01\text{ m}$ | Radome front $\pm 0.01\text{ m}$ | + +![Figure 4.15.2.3-1 Alignment of AAS BS and CLTA. The diagram shows three views: Horizontal View, Vertical View, and Side View. In the Horizontal View, the AAS BS is a large rectangle with an 'X' inside, and the CLTA is a smaller rectangle with an 'X' inside. A horizontal dashed line connects their centers. A vertical dashed line connects the bottom of the AAS BS to the bottom of the CLTA. A horizontal double-headed arrow labeled 'd' indicates the distance between the centers of the AAS BS and CLTA. In the Vertical View, the AAS BS is a rectangle, and the CLTA is a smaller rectangle. A vertical dashed line connects the bottom of the AAS BS to the bottom of the CLTA. Arrows point down from the bottom of each rectangle to the text 'Mechanical bore-sight direction'. In the Side View, the AAS BS is shown as a dashed rectangle, and the CLTA is shown as a solid rectangle. The text 'Back side' is to the left of the dashed rectangle, and 'Front side' is to the right of the solid rectangle.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +Figure 4.15.2.3-1 Alignment of AAS BS and CLTA. The diagram shows three views: Horizontal View, Vertical View, and Side View. In the Horizontal View, the AAS BS is a large rectangle with an 'X' inside, and the CLTA is a smaller rectangle with an 'X' inside. A horizontal dashed line connects their centers. A vertical dashed line connects the bottom of the AAS BS to the bottom of the CLTA. A horizontal double-headed arrow labeled 'd' indicates the distance between the centers of the AAS BS and CLTA. In the Vertical View, the AAS BS is a rectangle, and the CLTA is a smaller rectangle. A vertical dashed line connects the bottom of the AAS BS to the bottom of the CLTA. Arrows point down from the bottom of each rectangle to the text 'Mechanical bore-sight direction'. In the Side View, the AAS BS is shown as a dashed rectangle, and the CLTA is shown as a solid rectangle. The text 'Back side' is to the left of the dashed rectangle, and 'Front side' is to the right of the solid rectangle. + +**Figure 4.15.2.3-1 Alignment of AAS BS and CLTA** + +## 5 Applicability of Requirements + +### 5.1 General + +The present clause defines for each radiated test requirement the set of mandatory test configurations which shall be used for demonstrating conformance for radiated requirement. + +Test configurations for beams supporting multiple RAT in the tested operating band are specified in clause 5.1. + +Test configurations for radiated requirements where the operating band has been declared to support single RAT requirements (see table 4.10-1, D9.5) by either MSR requirements for UTRA only or E-UTRA only or with a single-RAT UTRA requirements or single RAT E-UTRA requirements are specified in subclause 5.2. + +Test configurations for an AAS BS with operating bands which have multi-band dependencies are specified in subclause 5.3. + +Requirements apply to AAS BS according to the declared RAT radiated Capability Set (see table 4.10-1, D9.25) within each supported operating band the Band Category of the declared operating band (see table 4.10-1, D9.4), as listed in the heading of each table. Some RF requirements listed in the tables may not be mandatory or they may apply only regionally. This is further specified for each requirement in clauses 6 and 7, and in table 4.4-1. + +For a declared RAT radiated Capability Set (see table 4.10-1, D9.25) in tables 5.2-1, 5.3.2-1, 5.3.3-1, 5.3.4-1, 5.4.1-1 or 5.4.2-1 only the requirements listed in the column for that radiated Capability Set apply. Requirements listed under RCSA other than the declared RCSA(s) need not be tested. In case the BS is declared to support more than one CS, the tests that are common between different supported CSs are not repeated. + +An AAS BS where the operating band is declared: to support multiple RATs (MSR) and to be capable of contiguous spectrum operation only, the test configuration(s) in tables 5.2-1 and 5.3.2-1 denoted by a "C" and entries that refer to single-RAT specifications shall be used for testing. + +An AAS BS where the operating band is declared: to support multiple RATs (MSR), to be capable of contiguous and non-contiguous spectrum operation (see table 4.10-1, D9.28), where the parameters according to clause 4.10 are identical for contiguous and non-contiguous operation (see table 4.10-1, D9.29). Shall use for each declared operating band the test configuration(s) in tables 5.2-1 and 5.3.2-1 denoted by "CNC" and entries that refer to single-RAT specifications shall be used. + +An AAS BS where the operating band is declared: to support multiple RATs (MSR), to be capable of contiguous and non-contiguous spectrum operation (see table 4.10-1, D9.28), where the parameters according to clause 4.10 are not identical for contiguous and non-contiguous operation (see table 4.10-1, D9.29). Shall use for each declared operating band the test configuration(s) in tables 5.2-1 and 5.3.2-1 denoted by "C/NC" and entries that refer to single-RAT specifications shall be used. + +For an AAS BS operating bands which have multi-band dependencies which is MSR capable the applicability of the requirement for each operating band is determined by the RAT configuration within that operating band as identified in tables 5.2-1 and 5.3.2-1, unless otherwise stated. The testing of an AAS BS in operating bands with multi-band dependencies which are MSR capable shall be according to table 5.4.1-1 as follows: + +- For requirements test denoted by SBT (Single Band Test), the test configuration (s) in tables 5.2-1 and 5.3.2-1 shall be used for each operating band depending on the RAT configuration within that band. +- For requirements test denoted by MBT (Multi-Band Test), the test configuration (s) in table 5.4.1-1 shall be used depending on the Band Category of the declared operating band combination. + +For a single-RAT UTRA only operating bands clause 5.3.3 defines for each radiated test requirement the set of mandatory test configurations which shall be used for demonstrating conformance. The applicable test configurations are specified in table 5.3.3-1 for each supported RF configuration, which shall be declared according to clause 4.10. The generation and EIRP allocation for each test configuration is defined in clause 4.11.2. + +For a single-RAT E-UTRA only operating bands clause 5.3.4 defines for each radiated test requirement the set of mandatory test configurations which shall be used for demonstrating conformance. The applicable test configurations are specified in table 5.3.4-1 for each supported RF configuration, which shall be declared according to clause 4.10. The generation and EIRP allocation for each test configuration is defined in clause 4.11.3. + +For an AAS BS operating band declared to be capable of single carrier operation only (see table 4.10-1, D9.4), a single carrier (SC) shall be used for testing. + +In Table 5.1-1, the requirement applicability for each requirement set is defined. For each requirement, the applicable requirement clause in the specification is identified. Requirements not included in a requirement set is marked not applicable (NA). + +**Table 5.1-1: Requirement set applicability** + +| Requirement | Requirement set | | +|--------------------------------------|-------------------------|----------------------| +| | Hybrid requirements set | OTA requirements set | +| Radiated transmit power | 6.2 | 6.2 | +| OTA Base Station output power | NA | 6.3 | +| OTA Output power dynamics | | 6.4 | +| OTA Transmit ON/OFF power | | 6.5 | +| OTA Transmitted signal quality | | 6.6 | +| OTA occupied bandwidth | | 6.7.2 | +| OTA ACLR | | 6.7.3 | +| OTA Spectrum emission mask | | 6.7.4 | +| OTA Operating band unwanted emission | | 6.7.5 | +| OTA transmitter spurious emission | | 6.7.6 | +| OTA transmitter intermodulation | | 6.8 | +| OTA sensitivity | 7.2 | 7.2 | +| OTA reference sensitivity level | NA | 7.3 | +| OTA dynamic range | | 7.4 | +| OTA in-band selectivity and blocking | | 7.5 | +| OTA out-of-band blocking | | 7.6 | +| OTA receiver spurious emission | | 7.7 | +| OTA receiver intermodulation | | 7.8 | +| OTA in-channel selectivity | | 7.9 | +| Radiated performance requirements | | 8 | + +## 5.2 Test configurations for AAS BS for operating bands where MSR with more than 1 RAT is supported + +**Table 5.2-1: Test configuration applicability to requirements and capability sets for AAS BS supporting MSR operation** + +| Test case | UTRA + E-UTRA (RCSA 3) | | | E-UTRA + NR (RCSA 3A) | | | UTRA + E-UTRA
+ NR (RCSA 3B) | +|----------------------------------------|--------------------------------------------------------------|-----------------------------------------------------------|---------------------------------|-----------------------------------------------------------|-----------------------------------------------------------|-----------------------------------------------------------|--------------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| 6.2 Radiated transmit power | C:
ATCR3a
CNC:
ATCR3a
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ATCR3a
C/NC:
ATCR3a,
ANTCR3 | C:
ATCR3b | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ATCR9
C/NC: ATCR9,
ANTCR9 | +| 6.3 OTA Base Station output power | - | - | - | - | - | - | - | +| 6.3.2 OTA Maximum output power | C:
ATCR3a
CNC:
ATCR3a
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ATCR3a
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ATCR9
C/NC: ATCR9,
ANTCR9 | +| 6.3.3 OTA E-UTRA DL RS power | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Subclause 5.3.4 | +| 6.4 OTA Output power dynamics | - | - | - | - | - | - | - | +| E-UTRA | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Subclause 5.3.4 | +| UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Subclause 5.3.3 | +| NR – RE power control dynamic range | N/A | N/A | N/A | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| NR – total power dynamic range | N/A | N/A | N/A | SC | SC | SC | SC | +| 6.5 OTA Transmit ON/OFF power | - | - | - | - | - | - | - | +| 6.5.1 OTA Transmitter OFF power | N/A | N/A | N/A | N/A | N/A | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | N/A | +| 6.5.2 OTA Transmitter transient period | N/A | N/A | N/A | N/A | N/A | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | N/A | +| 6.6 Transmitted signal quality | - | - | - | - | - | - | - | +| 6.6.2 OTA Frequency error | - | - | - | - | - | - | - | +| E-UTRA | Same TC as used in clause 6.6.4 | Same TC as used in clause 6.6.4 | Same TC as used in clause 6.6.4 | Same TC as used in clause 6.6.4 | Same TC as used in clause 6.6.4 | Same TC as used in clause 6.6.4 | Same TC as used in subclause 6.6.4 | +| UTRA FDD | Same TC as used in clause 6.6.4 | Same TC as used in clause 6.6.4 | N/A | N/A | N/A | N/A | Same TC as used in subclause 6.6.4 | +| NR | N/A | N/A | | Same TC as used in clause 6.6.4 | Same TC as used in clause 6.6.4 | Same TC as used in clause 6.6.4 | Same TC as used in subclause 6.6.4 | + +| Test case | UTRA + E-UTRA (RCSA 3) | | | E-UTRA + NR (RCSA 3A) | | | UTRA + E-UTRA
+ NR (RCSA 3B) | +|------------------------------------------------|--------------------------------------------------------------|-----------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| 6.6.3 OTA Time alignment error | - | - | - | - | - | - | - | +| E-UTRA | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Subclause 5.3.4 | +| UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Subclause 5.3.3 | +| NR | N/A | N/A | N/A | C:
ATCR8
CNC:
ATCR8
C/NC:
ATCR8,
ANTCR8 | C:
ATCR8
CNC:
ATCR8
C/NC:
ATCR8,
ANTCR8 | C:
ATCR8
CNC:
ATCR8
C/NC:
ATCR8,
ANTCR8 | C: ATCR9
CNC: ATCR9
C/NC: ATCR9,
ANTCR9 | +| 6.6.4 OTA Modulation quality - EVM | - | - | - | - | - | - | - | +| E-UTRA | C:
ATCR3a
CNC:
ATCR3a
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ATCR3a
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ATCR9
C/NC: ATCR9,
ANTCR9 | +| UTRA FDD | C:
ATCR3a
CNC:
ATCR3a
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ATCR3a
C/NC:
ATCR3a,
ANTCR3 | N/A | N/A | N/A | N/A | C: ATCR9
CNC: ATCR9
C/NC: ATCR9,
ANTCR9 | +| NR | N/A | N/A | N/A | N/A | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ATCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ATCR9
C/NC: ATCR9,
ANTCR9 | +| 6.7 OTA Unwanted Emissions | - | - | - | - | - | - | - | +| 6.7.2 OTA Occupied bandwidth | - | - | - | - | - | - | - | +| Minimum requirement | Clause 5.3.3
Clause 5.3.4 | Clause 5.3.3
Clause 5.3.4 | Clause 5.3.3
Clause 5.3.4 | Clause 5.3.4
SC,
ATCR8b
(Note) | Clause 5.3.4
SC,
ATCR8b
(Note) | Clause 5.3.4
SC,
ATCR8b
(Note) | Subclause 5.3.3
Subclause 5.3.4
SC | +| 6.7.3 OTA Adjacent Channel Leakage power Ratio | - | - | - | - | - | - | - | +| E-UTRA | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C: ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C: ATCR9
CNC: ATCR9
C/NC: ATCR9,
ANTCR9 | +| UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Subclause 5.3.3 | +| NR | N/A | N/A | N/A | C:
ATCR8a
CNC:
ANTCR8
C/NC:
ATCR8a,
ANTCR8 | C:
ATCR8a
CNC:
ANTCR8
C/NC:
ATCR8a,
ANTCR8 | C:
ATCR8a
CNC:
ANTCR8
C/NC:
ATCR8a,
ANTCR8 | C: ATCR9
CNC: ATCR9
C/NC: ATCR9,
ANTCR9 | + +| Test case | UTRA + E-UTRA (RCSA 3) | | | E-UTRA + NR (RCSA 3A) | | | UTRA + E-UTRA
+ NR (RCSA 3B) | +|------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------|--------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| Cumulative ACLR | CNC:
ANTCR3
C/NC:AN
TCR3 | CNC:
ANTCR3
C/NC:ANT
CR3 | | CNC:
ANTCR7
C/NC:AN
TCR7 | CNC:
ANTCR7
C/NC:AN
TCR7 | CNC:
ANTCR7
C/NC:AN
TCR7 | CNC: ANTCR9
C/NC: ANTCR9 | +| 6.6.5 OTA Operating band unwanted emission | - | - | - | - | - | - | - | +| General requirement for Band Categories 1 and 3 | Clause 5.3.3
Clause 5.3.4 C:
ATCR3a
CNC:
ATCR3a,
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | Clause 5.3.3
Clause 5.3.4 | Clause 5.3.4
C:
ATCR7
CNC:
ATCR7,
ANTCR7
C/NC:
ATCR7,
ANTCR7 | N/A | Clause 5.3.4
C:
ATCR7
CNC:
ATCR7,
ANTCR7
C/NC:
ATCR7,
ANTCR7 | Subclause 5.3.3
Subclause 5.3.4 | +| General requirement for Band Category 2 | N/A | Clause 5.3.3
Clause 5.3.4
C: ATCR3a
CNC:
ATCR3a,
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | N/A | Clause 5.3.4
C:
ATCR7
CNC:
ATCR7,
ANTCR7
C/NC:
ATCR7,
ANTCR7 | N/A | BC1: N/A
BC2:
Subclause 5.3.3
Subclause 5.3.4
C: ATCR9
CNC: ATCR9,
ANTCR9
C/NC: ATCR9,
ANTCR9 | +| Additional requirements | (note) | (note) | (note) | (note) | (note) | (note) | (note 1) | +| 6.7.6 OTA Spurious emission | - | - | - | - | - | - | - | +| (Category A) | C:
ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | +| (Category B) | C:
ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | +| Protection of the BS receiver of own or different BS | C:
ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3C/
NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | +| Additional spurious emissions requirements | C:
ATCR3a,
CNC:
ANTCR3,
C/NC:
ATCR3a,
ANTCR3a | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7,
CNC:
ANTCR7,
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7,
CNC:
ANTCR7,
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7,
CNC:
ANTCR7,
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | + +| Test case | UTRA + E-UTRA (RCSA 3) | | | E-UTRA + NR (RCSA 3A) | | | UTRA + E-UTRA
+ NR (RCSA 3B) | +|--------------------------------------------------------------|--------------------------------------------------------------|-----------------------------------------------------------|-------------------------------|------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| Co-location with other Base Stations | C:
ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | +| 6.8 OTA Transmitter intermodulation | - | - | - | - | - | - | - | +| General requirement | Same TC as used in clause 6.7 | Same TC as used in clause 6.7 | Same TC as used in clause 6.7 | Same TC as used in clause 6.7 | Same TC as used in clause 6.7 | Same TC as used in clause 6.7 | Same TC as used in subclause 6.7 | +| Additional requirement (BC1 and BC2) | CNC:
ANTCR3
C/NC:AN
TCR3 | Same TC as used in clause 6.7 | N/A | CNC:
ANTCR7
C/NC:AN
TCR7a | Same TC as used in clause 6.7 | N/A | BC1:
CNC: ANTCR9
C/NC:ANTCR9
BC2:
Same TC as used in subclause 6.7 | +| Additional requirement (BC3) | N/A | N/A | Same TC as used in clause 6.7 | N/A | N/A | N/A | N/A | +| 7.2 OTA sensitivity | - | - | - | - | - | - | - | +| E-UTRA requirement | clause 5.3.4 | clause 5.3.4 | clause 5.3.4 | clause 5.3.4 | clause 5.3.4 | clause 5.3.4 | subclause 5.3.4 | +| UTRA FDD requirement | clause 5.3.3 | clause 5.3.3 | N/A | N/A | N/A | N/A | subclause 5.3.3 | +| UTRA TDD requirement | N/A | N/A | clause 5.3.3 | N/A | N/A | N/A | N/A | +| NR requirement | N/A | N/A | N/A | ATCR4d | ATRC4d | ATCR4d | ATCR4d | +| 7.3 OTA reference sensitivity level | - | - | - | - | - | - | - | +| E-UTRA requirement | clause 5.3.4 | clause 5.3.4 | clause 5.3.4 | clause 5.3.4 | clause 5.3.4 | clause 5.3.4 | subclause 5.3.4 | +| UTRA FDD requirement | clause 5.3.3 | clause 5.3.3 | N/A | N/A | N/A | N/A | subclause 5.3.3 | +| NR requirement | N/A | N/A | N/A | ATRC4d | ATCR4d | ATCR4d | ATCR4d | +| 7.4 OTA Dynamic range | - | - | - | - | - | - | - | +| E-UTRA | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Subclause 5.3.4 | +| UTRA FDD | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | Subclause 5.3.3 | +| NR | N/A | N/A | N/A | ATCR4d | ATCR4d | ATCR4d | ATCR4d | +| 7.5 OTA Adjacent channel selectivity and narrowband blocking | - | - | - | - | - | - | - | +| General blocking requirement | C:
ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | + +| Test case | UTRA + E-UTRA (RCSA 3) | | | E-UTRA + NR (RCSA 3A) | | | UTRA + E-UTRA
+ NR (RCSA 3B) | +|------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| General narrowband blocking requirement | C:
ATCR3a,
ATCR4b
CNC:ANT
CR3,
ATCR4b
C/NC:
ATCR3a,
ANTCR3,
ATCR4b | C:
ATCR3a,
ATCR4b
CNC:ANTC
R3,
ATCR4b
C/NC:
ATCR3a,
ANTCR3,A
TCR4b | C:
ATCR4b | C:
ATCR7,
ATCR4b,
ATCR4d
CNC:AN
TCR7,
ATCR4b,
ATCR4d
C/NC:
ATCR7,
ANTCR7,
ATCR4b,
ATCR4d | C:
ATCR7,
ATCR4b,
ATCR4d
CNC:AN
TCR7,
ATCR4b,
ATCR4d
C/NC:
ATCR7,
ANTCR7,
ATCR4b,
ATCR4d | C:
ATCR7,
ATCR4b,
ATCR4d
CNC:
ANTCR7,
ATCR4b,
ATCR4d
C/NC:
ATCR7,
ANTCR7,
ATCR4b,
ATCR4d | C:
ATCR9, ATCR4a,
ATCR4b, ATCR4d
CNC:
ANTCR9,
ATCR4a,
ATCR4b, ATCR4d
C/NC:
ATCR9,
ANTCR9,
ATCR4a,
ATCR4b, ATCR4d | +| Additional BC3 blocking minimum requirement | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| 7.6 OTA Blocking | - | - | - | - | - | - | - | +| General requirement | C:
ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | +| Co-location requirement | C:
ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | +| 7.7 OTA Receiver spurious emissions | - | - | - | - | - | - | - | +| General requirement | C:
ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | +| Additional requirement for BC2 (Category B) | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| 7.8 OTA Receiver intermodulation | - | - | - | - | - | - | - | +| General intermodulation requirement | C:
ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | C: ATCR3a
CNC:
ANTCR3
C/NC:
ATCR3a,
ANTCR3 | N/A | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C:
ATCR7
CNC:
ANTCR7
C/NC:
ATCR7,
ANTCR7 | C: ATCR9
CNC: ANTCR9
C/NC: ATCR9,
ANTCR9 | +| General narrowband intermodulation requirement | C:
ATCR3a,
ATCR4b
CNC:ANT
CR3,
ATCR4b
C/NC:
ATCR3a,
ANTCR3,
ATCR4b | C: ATCR3a
ATCR4b
CNC:ANTC
R3,ATCR4
b C/NC:
ATCR3a,
ANTCR3;
ATCR4b | C:
ATCR4b | C:
ATCR7,
ATCR4b,
ATCR4d
CNC:AN
TCR7,
ATCR4b,
ATCR4d
C/NC:
ATCR7,
ANTCR7,
ATCR4b,
ATCR4d | C:
ATCR7,
ATCR4b,
ATCR4d
CNC:AN
TCR7,AT
CR4b,
ATCR4d
C/NC:
ATCR7,
ANTCR7,
ATCR4b,
ATCR4d | C:
ATCR7,
ATCR4b,
ATCR4d
CNC:
ANTCR7,
ATCR4b,
ATCR4d
C/NC:
ATCR7,
ANTCR7,
ATCR4b,
ATCR4d | C:
ATCR9, ATCR4a,
ATCR4b, ATCR4d
CNC:
ANTCR9,
ATCR4a,
ATCR4b, ATCR4d
C/NC:
ATCR9,
ANTCR9,
ATCR4a,
ATCR4b, ATCR4d | + +| Test case | UTRA + E-UTRA (RCSA 3) | | | E-UTRA + NR (RCSA 3A) | | | UTRA + E-UTRA
+ NR (RCSA 3B) | +|--------------------------------|------------------------|--------------|--------------|-----------------------|--------------|--------------|---------------------------------| +| | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | BC1, BC2 | +| 7.9 OTA In-channel selectivity | - | - | - | - | - | - | - | +| E-UTRA requirement | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | Subclause 5.3.4 | +| NR requirement | N/A | N/A | N/A | ATCR4d | ATCR4d | ATCR4d | ANTCR9 | + +NOTE 1: ATCR8b is only applicable when contiguous CA is supported + +NOTE 2: For Operating band unwanted emissions, NR shall also be tested with SC with widest supported channel bandwidth and highest supported sub-carrier spacing. + +## 5.3 Test configurations for multi-carrier capable AAS BS in operating bands where one RAT capability sets are supported + +### 5.3.1 General + +An AAS BS may support only one RAT operation in an operating band by fulfilling different sets of requirements. Both UTRA and E-UTRA have two complete sets of requirements that may be fulfilled depending on whether the beam is declared to be MSR or single RAT in the operating band. MSR and single RAT requirements are addressed separately by separate test requirements (and corresponding core requirements). They are also identified by different capability sets as described in clauses 4.11 and 5.2. + +### 5.3.2 AAS BS supporting one RAT only MSR in the operating band + +This clause contains test configuration applicability to requirements and capability sets for AAS BS supporting one RAT only MSR operation operating with multiple carriers (MC). + +**Table 5.3.2-1: Test configuration applicability to requirements +and capability sets for operating bands supporting one RAT only MSR operation** + +| Capability Set | | UTRA (MC) capable BS (RCSA1) | | | E-UTRA (MC) capable BS (RCSA2) | | | +|-----------------------|---------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------|--------------|--------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------| +| Test case | | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| 6.2 | Radiated transmit power | C:
ATCR1a
CNC:
ATCR1a
C/NC:
ATCR1a,
ANTCR1a | C:
ATCR1a
CNC:
ATCR1a
C/NC:
ATCR1a,
ANTCR1a | C:
ATCR1b | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | +| 6.3 | OTA Base Station output power | - | - | - | - | - | - | +| 6.3.2 | OTA maximum output power | C:
ATCR1a
CNC:
ATCR1a
C/NC:
ATCR1a,
ANTCR1a | C:
ATCR1a
CNC:
ATCR1a
C/NC:
ATCR1a,
ANTCR1a | N/A | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | +| 6.3.3 | OTA E-UTRA DL RS power | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| 6.4 | OTA Output power dynamics | - | - | - | - | - | - | +| 6.4.2 | OTA UTRA Inner loop power control in the downlink | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| 6.4.3 | OTA Power control dynamic range | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| 6.4.4 | OTA Total power dynamic range | N/A | N/A | Clause 5.3.3 | N/A | N/A | N/A | +| 6.4.5 | OTA IPDL time mask | Clause 5.3.3 | Clause 5.3.3 | N/A | | | | +| 6.4.6 | OTA RE Power control dynamic range | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| 6.5 | OTA Transmit ON/OFF power | - | - | - | - | - | - | +| 6.5.1 | OTA Transmitter OFF power | N/A | N/A | N/A | N/A | N/A | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | +| 6.5.2 | OTA Transmitter transient period | N/A | N/A | N/A | N/A | N/A | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | +| 6.6 | OTA signal quality | - | - | - | - | - | - | +| 6.6.2 | OTA Frequency error | - | - | - | - | - | - | +| | E-UTRA | N/A | N/A | N/A | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | +| | UTRA FDD | Same TC as used in clause 6.5.4 | Same TC as used in clause 6.5.4 | N/A | N/A | N/A | N/A | +| 6.6.3 | OTA Time alignment error | - | - | - | - | - | - | + +| Capability Set | | UTRA (MC) capable BS (RCSA1) | | | E-UTRA (MC) capable BS (RCSA2) | | | +|-------------------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| Test case | | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| E-UTRA | | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| UTRA FDD | | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| 6.6.4 | OTA Modulation quality - EVM | - | - | - | - | - | - | +| E-UTRA | | N/A | N/A | N/A | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ATCR2a
C/NC:
ATCR2a,
ANTCR2 | +| UTRA FDD | | C:
ATCR1a
CNC:
ATCR1a
C/NC:
ATCR1a,
ANTCR1a | C:
ATCR1a
CNC:
ATCR1a
C/NC:
ATCR1a,
ANTCR1a | N/A | N/A | N/A | N/A | +| 6.7 | OTA Unwanted Emissions | - | - | - | - | - | - | +| 6.7.2 | OTA Occupied bandwidth | - | - | - | - | - | - | +| Minimum requirement | | Clause 5.3.3 | Clause 5.3.3 | Clause 5.3.3 | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| 6.7.3 | OTA Adjacent Channel Leakage power Ratio | | - | - | - | - | - | +| E-UTRA | | N/A | N/A | N/A | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | +| UTRA FDD | | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| Cumulative ACLR | | CNC:
ANTCR1a
C/NC:
ANTCR1a | CNC:
ANTCR1a
C/NC:
ANTCR1a | - | CNC:
ANTCR2
C/NC:
ANTCR2 | CNC:
ANTCR2
C/NC:
ANTCR2 | CNC:
ANTCR2
C/NC:
ANTCR2 | +| 6.7.4 | OTA Spectrum emission mask | | | | | | | +| 6.7.5 | OTA Operating band unwanted emission | - | - | - | - | - | - | +| General requirement for Band Categories 1 and 3 | | Clause 5.3.3
C:
ATCR1a
CNC:
ATCR1a,
ANTCR1a
C/NC:
ATCR1a,
ANTCR1a | N/A | Clause 5.3.3 | Clause 5.3.4
C:
ATCR2a
CNC:
ATCR2a,
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | N/A | Clause 5.3.4
C:
ATCR2a
CNC:
ATCR2a,
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | + +| Capability Set | UTRA (MC) capable BS (RCSA1) | | | E-UTRA (MC) capable BS (RCSA2) | | | +|------------------------------------------------------|----------------------------------------------------|----------------------------------------------------------------------------|-------------------------------|----------------------------------------------------|----------------------------------------------------------------------------|----------------------------------------------------| +| Test case | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| General requirement for Band Category 2 | N/A | Clause 5.3.3
C: ATCR1a
CNC: ATCR1a, ANTCR1a
C/NC: ATCR1a, ANTCR1a | N/A | N/A | Clause 5.3.4
C: ATCR2a
CNC: ATCR2a, ANTCR2a
C/NC: ATCR2a, ANTCR2a | N/A | +| Additional requirements | (note) | (note) | (note) | (note) | (note) | (note) | +| 6.7.6 OTA Spurious emission | - | - | - | - | - | - | +| (Category A) | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | N/A | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | +| (Category B) | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | N/A | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | +| Protection of the BS receiver of own or different BS | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | N/A | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | +| Additional spurious emissions requirements | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | N/A | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | +| Co-location with other Base Stations | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | C: ATCR1a
CNC: ANTCR1a
C/NC: ATCR1a, ANTCR1a | N/A | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | C: ATCR2a
CNC: ANTCR2a
C/NC: ATCR2a, ANTCR2a | +| 6.8 OTA Transmitter intermodulation | - | - | - | - | - | - | +| General requirement | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | Same TC as used in clause 6.6 | + +| Capability Set | | UTRA (MC) capable BS (RCSA1) | | | E-UTRA (MC) capable BS (RCSA2) | | | +|---------------------------------------------|----------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------|------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| Test case | | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| Additional requirement (BC1 and BC2) | | CNC:
ANTCR1a
C/NC:ANT
CR1a | Same TC as used in 6.6 | N/A | CNC:
ANTCR2
C/NC:
ANTCR2 | Same TC as used in 6.6 | N/A | +| Additional requirement (BC3) | | N/A | N/A | Same TC as used in clause 6.6 | N/A | N/A | Same TC as used in 6.6 | +| 7.2 | OTA sensitivity | - | - | - | - | - | - | +| E-UTRA requirement | | N/A | N/A | N/A | clause 5.3.4 | clause 5.3.4 | clause 5.3.4 | +| UTRA FDD requirement | | clause 5.3.3 | clause 5.3.3 | N/A | N/A | N/A | N/A | +| UTRA TDD requirement | | N/A | N/A | clause 5.3.3 | N/A | N/A | N/A | +| 7.3 | OTA Reference sensitivity level | - | - | - | - | - | - | +| E-UTRA requirement | | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| UTRA FDD requirement | | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| 7.4 | OTA Dynamic range | - | - | - | - | - | - | +| E-UTRA | | N/A | N/A | N/A | Clause 5.3.4 | Clause 5.3.4 | Clause 5.3.4 | +| UTRA FDD | | Clause 5.3.3 | Clause 5.3.3 | N/A | N/A | N/A | N/A | +| 7.5 | OTA Adjacent channel selectivity and narrowband blocking | - | - | - | - | - | - | +| General blocking requirement | | C:
ATCR1a
CNC:
ANTCR1a
C/NC:
ATCR1a ,
ANTCR1a | C:
ATCR1a,
NC:
ANTCR1a
C/NC:
ATCR1a ,
ANTCR1a | N/A | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | +| General narrowband blocking requirement | | C:
ATCR1a,
ATCR4a
CNC:
ANTCR1a,
ATCR4a
C/NC:
ATCR1a,
ANTCR1a,
ATCR4a | C:
ATCR1a,
ATCR4a
CNC:ANT
CR1a,
ATCR4a
C/NC:
ATCR1a,
ANTCR1a,
ATCR4a | N/A | C:
ATCR2a,
ATCR4b
CNC:ANT
CR2,
ATCR4b
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a,
ATCR4b
CNC:
ANTCR2,
ATCR4b
C/NC:
ATCR2a,
ANTCR2,
ATCR4b | C:
ATCR2a,
ATCR4b
CNC:
ANTCR2,
ATCR4b
C/NC:
ATCR2a,
ANTCR2,
ATCR4b | +| Additional BC3 blocking minimum requirement | | N/A | N/A | N/A | N/A | N/A | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | +| 7.6 | OTA Blocking | - | - | - | - | - | - | + +| Capability Set | | UTRA (MC) capable BS (RCSA1) | | | E-UTRA (MC) capable BS (RCSA2) | | | +|----------------|------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|-----|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| Test case | | BC1 | BC2 | BC3 | BC1 | BC2 | BC3 | +| | General requirement | C:
ATCR1a
CNC:
ANTCR1a
C/NC:
ATCR1a,
ANTCR1a | C:
ATCR1a
CNC:
ANTCR1
a C/NC:
ATCR1a,
ANTCR1
a | N/A | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | +| | Co-location requirement | C:
ATCR1a
CNC:
ANTCR1a
C/NC:
ATCR1a,
ANTCR1a | C:
ATCR1a
CNC:
ANTCR1
a C/NC:
ATCR1a,
ANTCR1
a | N/A | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | +| 7.7 | OTA Receiver spurious emissions | - | - | - | - | - | - | +| | General requirement | C:
ATCR1a
CNC:
ANTCR1a
C/NC:
ATCR1a,
ANTCR1a | C:
ATCR1a
CNC:
ANTCR1
a C/NC:
ATCR1a,
ANTCR1
a | N/A | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | +| 7.8 | OTA Receiver intermodulation | - | - | - | - | - | - | +| | General intermodulation requirement | C:
ATCR1a
CNC:
ANTCR1a
C/NC:
ATCR1a ,
ANTCR1a | C:
ATCR1a
CNC:
ANTCR1
a C/NC:
ATCR1a
,
ANTCR1
a | N/A | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | C:
ATCR2a
CNC:
ANTCR2
C/NC:
ATCR2a,
ANTCR2 | +| | General narrowband intermodulation requirement | C:
ATCR1a,
ATCR4a
CNC:ANT
CR1a,
ATCR4a
C/NC:
ATCR1a,
ANTCR1a,
ATCR4a | C:
ATCR1a,
ATCR4a
CNC:AN
TCR1a,
ATCR4a
C/NC:
ATCR1a,
ANTCR1
a,
ATCR4a | N/A | C:
ATCR2a,
ATCR4b
CNC:
ANTCR2,
ATCR4b
C/NC:
ATCR2a,
ANTCR2,
ATCR4b | C:
ATCR2a,
ATCR4b
CNC:
ANTCR2,
ATCR4b
C/NC:
ATCR2a,
ANTCR2,
ATCR4b | C:
ATCR2a,
ATCR4b
CNC:
ANTCR2,
ATCR4b
C/NC:
ATCR2a,
ANTCR2,
ATCR4b | +| 7.9 | OTA In-channel selectivity | - | - | - | - | - | - | +| | E-UTRA requirement | N/A | N/A | N/A | Clause 5.
3.4 | Clause 5.
3.4 | Clause 5.
3.4 | + +### 5.3.3 AAS BS supporting Single-RAT UTRA in the operating band + +This clause contains the test configurations for AAS BS supporting single-RAT UTRA in the operating band. The test configurations apply to beams operating with multiple carriers (MC). + +For an AAS BS declared to support multi-carrier operation in contiguous spectrum operation in single band only, the test configurations in the second column of table 5.3.3-1 for FDD, and in the fifth column of table 5.3.3-1 for TDD, shall be used for testing. + +NOTE: The applicability of test configurations for TDD in this clause is only applicable to UTRA TDD 1,28 Mcps option. + +For FDD an AAS BS declared to support multi-carrier operation in contiguous and non-contiguous spectrum in single band and where the parameters in the manufacture's declaration according to clause 4.10 are identical for contiguous (C) and non-contiguous (NC) spectrum operation, the test configurations in the third column of table 5.3.3-1 shall be used for testing. + +For FDD an AAS BS declared to support multi-carrier operation in contiguous and non-contiguous spectrum in single band and where the parameters in the manufacture's declaration according to clause 4.10 are not identical for contiguous and non-contiguous spectrum operation, the test configurations in the fourth column of table 5.3.3-1 shall be used for testing. + +**Table 5.3.3-1: Test configurations for a AAS BS supporting single-RAT UTRA operation** + +| test case | | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C capable only | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC AAS BS operating band (RCSA4) C capable only | +|------------------|----------------------------------------------------------|------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| +| 6.2 | Radiated Transmit Power | ATCR1a | ATCR1a | ATCR1a, ANT1 | ATCR1b | +| 6.3 | OTA Base Station output power | - | - | - | N/A | +| 6.3.2 | Base Station maximum output power | ATC1a | ATC1a | ATC1a, ANT1 | N/A | +| 6.4 | OTA Output power dynamics | - | - | - | N/A | +| 6.4.2 | OTA UTRA Inner loop power control in the downlink | SC | SC | SC | N/A | +| 6.4.3 | OTA Power control dynamic range | SC | SC | SC | N/A | +| 6.4.4 | OTA Total power dynamic range | SC or ATC1a | SC or ATC1a | SC or ATC1a | N/A | +| 6.4.5 | OTA IPDL time mask | SC | SC | SC | N/A | +| 6.6 | OTA Transmitted signal quality | - | - | - | N/A | +| 6.6.2 | OTA Frequency error | ATC1a | ATC1a | ATC1a, ANT1 | N/A | +| 6.6.3 | OTA Time alignment error | ATC1a | ATC1a | ATC1a, ANT1 | N/A | +| 6.6.4 | OTA Modulation quality - EVM | ATC1a | ATC1a | ATC1a, ANT1 | N/A | +| 6.6.4 | OTA Modulation quality - PCDE | ATC1a | ATC1a | ATC1a, ANT1 | N/A | +| 6.6.4 | OTA Modulation quality - RCDE | ATC1a | ATC1a | ATC1a | N/A | +| 6.7 | OTA Unwanted Emissions | - | - | - | N/A | +| 6.7.2 | OTA Occupied bandwidth | SC | SC | SC | N/A | +| 6.7.3 | OTA Adjacent Channel Leakage power Ratio | ATC1a | ANT1 | ATC1a, ANT1 | N/A | +| | Cumulative ACLR | - | ANT1 | ANT1 | N/A | +| 6.7.4 | OTA Spectrum emission mask | ATC1a | ATC1a, ANT1 | ATC1a, ANT1 | N/A | +| 6.7.6 | OTA Spurious emission | ATC1a | ANT1 | ATC1a, ANT1 | N/A | +| 6.8 | OTA Transmitter intermodulation | ATC1a | ATC1a, ANT1 | ATC1a, ANT1 | N/A | +| 7.2 | OTA sensitivity | ATCR4a | ATCR4a | ATCR4a | ATCR4c | +| 7.3 | OTA Reference sensitivity level | ATCR4a | ATCR4a | ATCR4a | N/A | +| 7.4 | OTA Dynamic range | ATCR4a | ATCR4a | ATCR4a | N/A | +| 7.5 | OTA Adjacent channel selectivity and narrowband blocking | ATCR1a | ANTCR1 | ATCR1a, ANTCR1 | N/A | +| 7.6 | OTA Blocking | ATCR1a | ANTCR1 | ATCR1a, ANTCR1 | N/A | +| 7.7 | OTA Receiver spurious emissions | ATCR1a | ANTCR1 | ATCR1a, ANTCR1 | N/A | +| 7.8 | OTA Receiver intermodulation | ATCR1a | ANTCR1 | ATCR1a, ANTCR1 | N/A | + +### 5.3.4 AAS BS supporting Single-RAT E-UTRA in the operating band + +This clause contains the test configurations for AAS BS supporting single-RAT E-UTRA in the operating band. The test configurations apply to AAS BS operating bands operating with multiple carriers (MC). + +For an AAS BS declared to support multi-carrier and/or CA operation in contiguous spectrum operation in single band only, the test configurations in the second column of table 5.3.4-1 shall be used for testing. + +For an AAS BS declared to support multi-carrier and/or CA operation in contiguous and non-contiguous spectrum in single band and where the parameters in the manufacture's declaration according to clause 4.10 are identical for contiguous (C) and non-contiguous (NC) spectrum operation, the test configurations in the third column of table 5.3.4-1 shall be used for testing. + +For an AAS BS declared to support multi-carrier and/or CA in contiguous and non-contiguous spectrum in single band and where the parameters in the manufacture's declaration according to clause 4.10 are not identical for contiguous and non-contiguous spectrum operation, the test configurations in the fourth column of table 5.3.4-1 shall be used for testing. + +**Table 5.3.4-1: Test configurations for a AAS BS supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band** + +| test case | | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5) C capable only | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5) C and NC capable BS with identical parameters | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5) C and NC capable BS with different parameters | +|------------------------------------------------------------------|----------------------------------------------------------|---------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| 6.2 | Radiated Transmit Power | ATCR2a | ATCR2a | ATCR2a, ANTCCR2 | +| 6.3 | OTA Base Station output power | - | - | - | +| 6.3.2 | OTA Base Station maximum output power | ATCR2a | ATCR2a | ATCR2a, ANTCCR2 | +| 6.3.3 | OTA E-UTRA DL RS power | SC | SC | SC | +| 6.4 | OTA Output power dynamics | - | - | - | +| 6.4.4 | OTA Total power dynamic range | SC | SC | SC | +| 6.4.6 | OTA RE Power control dynamic range | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| 6.5 | OTA Transmit ON/OFF power | ATCR2a | ATCR2a | ATCR2a, ANTCCR2 | +| 6.6 | OTA Transmitted signal quality | - | - | - | +| 6.6.2 | OTA Frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| 6.6.3 | OTA Time alignment error | ATCR2a | ATCR2a | ATCR2a, ANTCCR2 | +| 6.6.4 | OTA Modulation quality - EVM | ATCR2a | ATCR2a | ATCR2a, ANTCCR2 | +| 6.7 | OTA Unwanted Emissions | - | - | - | +| 6.7.2 | OTA Occupied bandwidth | SC, ATCR2b (Note) | SC, ATCR2b (Note) | SC, ATCR2b (Note) | +| 6.7.3 | OTA Adjacent Channel Leakage power Ratio | ATCR2a | ATCR2a, ANTCCR2 | ATCR2a, ANTCCR2 | +| 6.7.3 | OTA Cumulative ACLR | - | ANTCCR2 | ANTCCR2 | +| 6.7.5 | OTA Operating band unwanted emission | ATCR2a | ATCR2a, ANTCCR2 | ATCR2a, ANTCCR2 | +| 6.7.6 | OTA Spurious emission | ATCR2a | ANTCCR2 | ATCR2a, ANTCCR2 | +| 6.8 | OTA Transmitter intermodulation | ATCR2a | Same TC as used in 6.6 | Same TC as used in 6.6 | +| 7.2 | OTA sensitivity | ATCR4b | ATCR4b | ATCR4b | +| 7.3 | OTA Reference sensitivity level | ATCR4b | ATCR4b | ATCR4b | +| 7.4 | OTA Dynamic range | ATCR4b | ATCR4b | ATCR4b | +| 7.5 | OTA Adjacent channel selectivity and narrowband blocking | ATCR2a | ANTCCR2 | ATCR1, ANTCCR2 | +| 7.6 | OTA Blocking | ATCR2a | ANTCCR2 | ATCR2a, ANTCCR2 | +| 7.7 | OTA Receiver spurious emissions | ATCR2a | ANTCCR2 | ATCR2a, ANTCCR2 | +| 7.8 | OTA Receiver intermodulation | ATCR2a | ANTCCR2 | ATCR2a, ANTCCR2 | +| 7.9 | OTA In-channel selectivity | ATCR4b | ATCR4b | ATCR4b | +| NOTE: ATCR2b is only applicable when contiguous CA is supported. | | | | | + +## 5.4 Test configurations for AAS BS operating bands with multi-band dependencies + +### 5.4.1 AAS BS operating bands with multi-band dependencies supporting MSR operation + +**Table 5.4.1-1: Test configuration for AAS BS operating bands containing beams with multi-band dependencies supporting MSR operation** + +| test case | Test for AAS BS operating bands with multi-band dependencies
RCSA1,RCSA2, RCSA3, RCSA3A | Test configuration for MBT | | +|---------------------------------------------------------|--------------------------------------------------------------------------------------------|----------------------------|--------| +| | | BC1/BC2 | BC3 | +| 6. Radiated Transmit Power | SBT, MBT | ATCR5a | ATCR5a | +| 6.2 | | | | +| 6.3 OTA Base Station output power | - | - | - | +| 6.3.2 OTA Base Station maximum output power | SBT, MBT | ATCR5a | ATCR5a | +| 6.3.3 OTA E-UTRA DL RS power | E-UTRA for DL RS power | SBT | - | +| 6.4 OTA Output power dynamics | - | - | - | +| 6.4.2 OTA UTRA Inner loop power control in the downlink | SBT | - | - | +| 6.4.3 OTA Power control dynamic range | SBT | - | - | +| 6.4.4 OTA Total power dynamic range | SBT | - | N/A | +| 6.4.5 OTA IPDL time mask | SBT | - | N/A | +| 6.4.6 OTA RE Power control dynamic range | SBT | - | N/A | +| 6.5 OTA Transmit ON/OFF power | - | - | - | +| 6.5.1 OTA Transmitter OFF power | MBT, SBT (note 3) | N/A | ATCR5a | +| 6.5.2 OTA Transmitter transient period | MBT, SBT (note 3) | N/A | ATCR5a | +| 6.6 OTA Transmitted signal quality | - | - | - | +| 6.6.2 OTA Frequency error | - | - | - | +| E-UTRA | SBT, MBT | ATCR5a | ATCR5a | +| UTRA FDD | SBT, MBT | ATCR5a | N/A | +| NR | SBT, MBT | ATCR5a | ATCR5a | +| 6.6.3 OTA Time alignment error | - | - | - | +| E-UTRA | SBT, MBT (note 1) | ATCR5b | ATCR5b | +| UTRA FDD | SBT, MBT (note 1) | ATCR5b | N/A | +| NR | SBT, MBT (note 1) | ATCR5b | ATCR5b | +| 6.6.4 OTA Modulation quality - EVM | - | - | - | +| E-UTRA | SBT, MBT | ATCR5a | ATCR5a | +| UTRA FDD | SBT, MBT | ATCR5a | N/A | +| NR | SBT, MBT | ATCR5a | ATCR5a | +| 6.7 OTA Unwanted Emissions | - | - | - | +| 6.6.2 OTA Occupied bandwidth | - | - | - | +| Minimum requirement | SBT | - | - | +| 6.7.3 OTA Adjacent Channel Leakage power Ratio | - | - | - | +| E-UTRA | SBT, MBT (note 2) | ATCR5b | ATCR5b | +| UTRA FDD | SBT, MBT (note 2) | ATCR5b | N/A | +| NR | SBT, MBT (note 2) | ATCR5b | ATCR5b | +| Cumulative ACLR | SBT, MBT (note 2) | ATCR5b | ATCR5b | +| 6.7.4 OTA Spectrum emission mask | - | - | - | +| 6.7.5 OTA Operating band unwanted emission | - | - | - | +| General requirement for Band Categories 1 and 3 | SBT, MBT | ATCR5b | ATCR5b | +| General requirement for Band Category 2 | SBT, MBT | ATCR5b | N/A | +| Additional requirements | SBT, MBT | - | - | +| 6.7.6 OTA Spurious emission | - | - | - | +| (Category A) | SBT, MBT | ATCR5b | ATCR5b | +| (Category B) | SBT, MBT | ATCR5b | ATCR5b | +| Protection of the BS receiver of own or different BS | SBT, MBT | ATCR5b | ATCR5b | +| Additional spurious emissions requirements | SBT, MBT | ATCR5b | ATCR5b | +| Co-location with other Base Stations | - | - | - | +| 6.8 OTA Transmitter intermodulation | - | - | - | +| General requirement | SBT | - | - | +| Additional requirement (BC1 and BC2) | SBT | - | N/A | +| Additional requirement (BC3) | SBT | N/A | - | +| 7.2 OTA sensitivity | SBT | ATCR4a,A
TCR4b | None | +| 7.3 OTA Reference sensitivity level | - | - | - | +| E-UTRA requirement | SBT | - | - | +| UTRA FDD requirement | SBT | - | - | +| NR requirement | SBT | - | - | +| 7.4 OTA Dynamic range | - | - | - | +| E-UTRA | SBT | - | - | +| UTRA FDD | SBT | - | - | + +| test case | | Test for AAS BS operating bands with multi-band dependencies
RCSA1,RCSA2, RCSA3,
RCSA3A | Test configuration for MBT | | +|-----------|----------------------------------------------------------|-----------------------------------------------------------------------------------------------|----------------------------|--------| +| | | | BC1/BC2 | BC3 | +| | NR | SBT | - | - | +| 7.5 | OTA Adjacent channel selectivity and narrowband blocking | - | - | - | +| | General blocking requirement | MBT, SBT (note 3) | ATCR5b | ATCR5b | +| | General narrowband blocking requirement | MBT, SBT (note 3) | ATCR5b | ATCR5b | +| 7.6 | OTA Blocking | - | - | - | +| | General requirement | MBT, SBT(note 3) | ATCR5b | ATCR5b | +| | Co-location requirement | MBT, SBT(note 3) | ATCR5b | ATCR5b | +| 7.7 | OTA Receiver spurious emissions | - | - | - | +| | General requirement | SBT, MBT | ATCR5b | ATCR5b | +| 7.8 | OTA Receiver intermodulation | - | - | - | +| | General intermodulation requirement | MBT, SBT(note 3) | ATCR5b | ATCR5b | +| | General narrowband intermodulation requirement | MBT, SBT(note 3) | ATCR5b | ATCR5b | +| 7.9 | OTA In-channel selectivity | - | - | - | +| | E-UTRA requirement | SBT | - | - | +| | NR requirement | SBT | - | - | + +NOTE 1: MBT is only applicable when DB-DC-HSDPA or inter-band CA is supported. + +NOTE 2: For ACLR, MBT shall be applied for the Inter RF bandwidth gap only. + +NOTE 3: SBT is only applicable if different Capability Sets are declared for single-band and multi-band operation. + +## 5.4.2 AAS BS operating bands with multi-band dependencies supporting Single-RAT only + +For an AAS BS operating bands with multi-band dependencies supporting single-RAT only in the operational band, the test configurations in table 5.4.2-1, shall be used for testing. + +**Table 5.4.2-1: Test configuration for AAS BS operating bands with multi-band dependencies supporting Single-RAT only** + +| test case | | UTRA FDD
RCSA4 | UTRA TDD
RCSA4 | E-UTRA Test
RCSA5 | +|------------------|----------------------------------------------------------|-----------------------------------------------|-------------------------------|---------------------------------------------------| +| 6.2 | Radiated Transmit Power | ATCR1a/
ANTCR1 (Note 1)
ATCR5a | ATCR1b
(Note 3),
ATCR5a | ATCR2a/
ANTCR2
(Note 5),
ATCR5a | +| 6.3 | OTA Base Station output power | - | - | - | +| 6.3.2 | OTA Base Station maximum output power | ATCR1a/
ANTCR1 (note 1)
ATCR5a | N/A | ATCR2a/
ANTCR2 (note
6), ATCR5a | +| 6.3.3 | OTA E-UTRA DL RS power | N/A | N/A | SC | +| 6.4 | OTA Output power dynamics | - | - | - | +| 6.4.2 | OTA UTRA Inner loop power control in the downlink | SC | N/A | N/A | +| 6.4.3 | OTA Power control dynamic range | SC | N/A | SC | +| 6.4.4 | OTA Total power dynamic range | SC or ATCR1a | N/A | SC | +| 6.4.5 | OTA IPDL time mask | SC | N/A | N/A | +| 6.4.6 | OTA RE Power control dynamic range | N/A | N/A | Tested with
Error Vector
Magnitude | +| 6.5 | OTA Transmit ON/OFF power | - | - | - | +| 6.5.1 | OTA Transmitter OFF power | N/A | N/A | ATCR5a (only
applied for
E-UTRA TDD
BS) | +| 6.5.2 | OTA Transmitter transient period | N/A | N/A | SC | +| 6.6 | OTA Transmitted signal quality | - | - | - | +| 6.6.2 | OTA Frequency error | Tested with EVM | N/A | Tested with
Error Vector
Magnitude | +| 6.6.3 | OTA Time alignment error | ATCR1a/
ANTCR1 (note 1)
ATCR5b | N/A | ATCR2a/
ANTCR2 (note
6), ATCR5b
(note 7) | +| 6.6.4 | OTA Modulation quality - EVM | ATCR1a/
ANTCR1 (note 1),
ATCR5a | N/A | ATCR2a/
ANTCR2 (note
6), ATCR5a | +| 6.6.4 | OTA Modulation quality - PCDE | ATCR1a/
ANTCR1 (note 1) | N/A | N/A | +| 6.6.4 | OTA Modulation quality - RCDE | ATCR1 | N/A | N/A | +| 6.7 | OTA Unwanted Emissions | - | - | - | +| 6.7.2 | OTA Occupied bandwidth | SC | N/A | SC, ATCR2b
(note 8) | +| 6.7.3 | OTA Adjacent Channel Leakage power Ratio | ATCR1a/
ANTCR1 (note 1)
ATCR5b (note 2) | N/A | ATCR2a/
ANTCR2 (note
6), ATCR5b
(note 9) | +| 6.7.4 | OTA Spectrum emission mask | ATCR1a/
ANTCR1 (note 1)
ATCR5b | N/A | N/A | +| 6.7.5 | OTA Operating band unwanted emission | N/A | N/A | ATCR2a/
ANTCR2 (note
6), ATCR5b | +| 6.7.6 | OTA Spurious emission | ATCR1a/
ANTCR1 (note 1)
ATCR5b | N/A | ATCR2a/
ANTCR2 (note
6), ATCR5b | +| 6.8 | OTA Transmitter intermodulation | ATCR1a/
ANTCR1 (note 1) | N/A | ATCR2a/
ANTCR2 (note
6) | +| 7.2 | Reference sensitivity level | ATCR4a | ATCR4c | ATCR4b | +| 7.3 | OTA Reference sensitivity level | ATCR4a | N/A | ATCR4a | +| 7.4 | OTA Dynamic range | ATCR4a | N/A | ATCR4a | +| 7.5 | OTA Adjacent channel selectivity and narrowband blocking | ATCR5b | N/A | ATCR5b | +| 7.6 | OTA Blocking | ATCR5b | N/A | ATCR5b | + +| test case | | UTRA FDD
RCSA4 | UTRA TDD
RCSA4 | E-UTRA Test
RCSA5 | +|-----------|---------------------------------|---------------------------------|-------------------|--------------------------------------| +| 7.7 | OTA Receiver spurious emissions | ATCR1a/ANTC1
(note 1) ATCR5b | N/A | ATCR2a/
ANTC2 (note
6), ATCR5b | +| 7.8 | OTA Receiver intermodulation | ATCR5b | N/A | ATCR5b | +| 7.9 | OTA In-channel selectivity | N/A | N/A | ATCR4a | + +NOTE 1: ATCR1a and/or ANTCR1 shall be applied in each supported operating band according to table 5.3.3-1. +NOTE 2: ATCR5b may be applied for Inter RF Bandwidth gap only. +NOTE 3: ATCR1b shall be applied in each supported operating band according to table 5.3.3-1. +NOTE 4: Void +NOTE 5: ATCR5a may be applied for Inter RF bandwidth gap only. +NOTE 6: ATCR2 and/or ANTCR2 shall be applied in each supported operating band according to table 5.3.4-1. +NOTE 7: ATCR5b is only applicable when inter-band CA is supported. +NOTE 8: ATCR2b is only applicable when contiguous CA is supported. +NOTE 9: ATCR5b may be applied for Inter RF bandwidth gap only. + +## 6 Radiated transmitter characteristics + +### 6.1 General + +General test conditions for transmitter tests are given in clause 4, including interpretation of measurement results and configuration for testing. AAS BS configurations for the tests are defined in clause 4.8. + +If beams have been declared equivalent and parallel (see table 4.10-1, D9.12, D9.13), only a representative beam is necessary to be tested to demonstrate conformance. The manufacturer shall declare the minimum number of supported geographical cells (i.e. geographical areas). The minimum number of supported geographical cells ( $N_{\text{cells}}$ ) relates to the AAS BS setting with the minimum amount of cell splitting supported. + +OTA AAS BS transmitter requirements apply per geographical cell. + +Any radiated transmitter test requirement specified in TS 37.105 [6] is not applicable for AAS BS operation in Band 46. + +For OTA base station output power (clause 6.3), OTA transmit ON/OFF power (clause 6.5), OTA unwanted emissions requirements (clause 6.7) and OTA receiver spurious emissions (clause 7.7), TRP is defined in spherical coordinates as: + +, where $P_D(r, \theta, \phi)$ is the power density in $\text{W/m}^2$ of two orthogonal polarizations at a distance $r$ (meters). + +NOTE: General TRP expression that is obtained by integrating the Poynting vector over a spherical surface. + +### 6.2 Radiated Transmit Power + +#### 6.2.1 Definition and applicability + +This is an output power accuracy requirement defined at the RIB during the *transmitter ON period*. + +An AAS BS is declared to support one or more beams. Radiated transmit power is defined as the EIRP level for a declared beam at a specific *beam peak direction*. + +For each beam, the requirement is based on declarations (see table 4.10-1) of a beam identifier (D9.3), *reference beam direction pair* (D9.7), *rated beam EIRP* (D9.10) at the *reference beam direction pair*, *OTA peak directions set* (D9.8), the *beam direction pairs* at the maximum steering directions (D9.9) and their associated *rated beam EIRP* and *beamwidth(s)* (D9.11) for *reference beam direction pair* and maximum steering directions. + +For a declared beam identifier and *beam direction pair*, the *rated beam EIRP* level is the maximum power that the base station is declared to radiate at the associated *beam peak direction* during the *transmitter ON period*. + +For each *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a specific *rated beam EIRP* level may be claimed. Any claimed value shall be met within the accuracy requirement as described below. *Rated beam EIRP* is only required to be declared for the *beam direction pairs* subject to conformance testing as detailed in clause 6.2.4.1. + +NOTE 1: The *OTA peak directions set* for a beam is the complete continuous or discrete set of all *beam direction* for which the EIRP accuracy is intended to be achieved for the beam. + +NOTE 2: A *beam direction pair* consists of a *beam centre direction* and an associated *beam peak direction*. + +NOTE 3: A declared EIRP value is a value provided by the manufacturer for verification according to the conformance specification declaration requirements, whereas a claimed EIRP value is provided by the manufacturer to the equipment user for normal operation of the equipment and is not subject to formal conformance testing. + +For *operating bands* where the supported *fractional bandwidth* (FBW) is larger than 6%, two rated carrier EIRP may be declared by manufacturer: + +- $P_{\text{rated,c,FBWlow}}$ for lower supported frequency range, and +- $P_{\text{rated,c,FBWhigh}}$ for higher supported frequency range. + +For frequencies in between $F_{\text{FBWlow}}$ and $F_{\text{FBWhigh}}$ the rated carrier EIRP is: + +- $P_{\text{rated,c,FBWlow}}$ , for the carrier whose carrier frequency is within frequency range $F_{\text{FBWlow}} \leq f < (F_{\text{FBWlow}} + F_{\text{FBWhigh}}) / 2$ , +- $P_{\text{rated,c,FBWhigh}}$ , for the carrier whose carrier frequency is within frequency range $(F_{\text{FBWlow}} + F_{\text{FBWhigh}}) / 2 \leq f \leq F_{\text{FBWhigh}}$ . + +## 6.2.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.2.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.2.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.2.4. + +## 6.2.3 Test purpose + +The test purpose is to verify the ability to accurately generate and direct radiated power per beam, across the frequency range and under normal conditions, for all declared beams of the AAS BS. + +## 6.2.4 Method of test + +### 6.2.4.1 Initial conditions + +Test environment: + +- Normal; see annex G.2. +- Extreme (applies only to OTA AAS BS), see annexes G.3 and G.5. + +RF bandwidth positions to be tested: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single-band operation, see clause 4.12.1. + +$B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.12.1. + +Directions to be tested: + +- The *reference beam direction pair* (D9.7) +- The maximum steering directions (D9.9). + +Beams to be tested: + +- the beam with the highest rated beam EIRP (D9.10); or + +- the beams with highest rated beam EIRP, $P_{\text{rated,c,FBWlow}}$ (D11.33) and $P_{\text{rated,c,FBWhigh}}$ (D11.34), if these are provided. + +Under extreme test environment, for OTA AAS BS only, it is sufficient to test on one RF channel or one *Base Station RF Bandwidth* position, and with one applicable test configuration defined in clauses 4.11 and 5. The direction to be tested is only at *reference beam direction pair* (D9.7). Testing shall be performed under extreme power supply conditions, as defined in annex G.5. + +NOTE: Tests under extreme power supply conditions also test extreme temperatures. + +#### 6.2.4.2 Procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the AAS BS according to the declared beam direction pair. +- 5) Set the base station to transmit according to the applicable test configuration in clause 5 using the corresponding test model(s) in clause 4.12.2. + +In addition, for an AAS BS declared to be capable of multi-carrier and/or CA operation use the applicable test signal configuration and corresponding power setting specified in clause 4.11. + +- 6) Measure EIRP for any two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $\text{EIRP} = \text{EIRP}_{p1} + \text{EIRP}_{p2}$ . +- 7) Test steps 3 to 6 are repeated for all declared beams (see table 4.10-1, D9.3) and their reference beam direction pairs and *maximum steering directions* (see table 4.10-1, D9.7 and D9.11). + +For multi-band capable AAS BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carriers activated in the other band. + +- 8) For extreme conditions tests the methods in annex B.7 may be used where a representative power measurement is taken at both nominal conditions ( $P_{\text{max,sample,nom}}$ ) and extreme conditions ( $P_{\text{max,sample,ext}}$ ) and the delta ( $\Delta_{\text{sample}}$ ) is added to the nominal measurement from step 6 such that $P_{\text{max,c,EIRP, extreme}} = P_{\text{max,c,EIRP}} + \Delta_{\text{sample}}$ . + +#### 6.2.5 Test Requirement + +For each declared conformance beam direction pair, in normal conditions, the EIRP measurement result in step 6 of clause 6.2.4.2 shall for UTRA, E-UTRA and NR remain: + +- within +3.3 dB and -3.3 dB of the manufacturer's declared rated beam EIRP value for carrier frequency $f \leq 3.0$ GHz; +- within +3.5 dB and -3.5 dB of the manufacturer's declared rated beam EIRP value for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +For a OTA AAS BS in extreme conditions, the result in step 8 ( $P_{\text{max,c,EIRP, extreme}}$ ) of clause 6.2.4.2 shall be: + +- within +5.2 dB and -5.2 dB of the manufacturer's declared rated beam EIRP value for carrier frequency $f \leq 3.0$ GHz; +- within +5.3 dB and -5.3 dB of the manufacturer's declared rated beam EIRP value for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +## 6.3 OTA Base Station output power + +### 6.3.1 General + +The *OTA AAS BS* base station output power is declared as TRP. + +### 6.3.2 OTA Maximum output power + +#### 6.3.2.1 Definition and applicability + +The rated carrier TRP shall be as specified for UTRA in table 6.3.2.1-1, and for E-UTRA and NR in table 6.3.2.1-2 + +**Table 6.3.2.1-1: UTRA OTA AAS Base Station rated output power limits for BS classes** + +| OTA AAS BS class | P rated,c,TRP | +|-----------------------------------------------------------------------------------------------|--------------------------| +| Wide Area BS | (NOTE) | +| Medium Range BS | ≤ 44 dBm | +| Local Area BS | ≤ 30 dBm | +| NOTE: There is no upper limit for the P rated,c,TRP of the Wide Area Base Station. | | + +**Table 6.3.2.1-2: E-UTRA and NR OTA AAS Base Station rated output power limits for BS classes** + +| OTA AAS BS class | P rated,c,TRP | +|-----------------------------------------------------------------------------------------------|--------------------------| +| Wide Area BS | (NOTE) | +| Medium Range BS | ≤ 47 dBm | +| Local Area BS | ≤ 33 dBm | +| NOTE: There is no upper limit for the P rated,c,TRP of the Wide Area Base Station. | | + +#### 6.3.2.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.3.2.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.3.2.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.3.2.4. + +#### 6.3.2.3 Test purpose + +The test purpose is to verify the accuracy of the *maximum carrier TRP* (Pmax,c,TRP) across the frequency range for all *RIBs* in the AAS BS. + +#### 6.3.2.4 Method of test + +##### 6.3.2.4.1 Initial conditions + +Test environment: Normal; see annex G.2. + +RF bandwidth positions to be tested: BRFBW, MRFBW and TRFBW in single-band operation, see clause 4.12.1. + +BRFBW\_TRFBW and B'RFBW\_TRFBW in multi-band operation, see clause 4.12.1. + +As the requirement is TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see annex F). + +#### 6.3.2.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in in Annex F. An alternative method to measure TRP is to use a characterized and calibrated reverberation chamber. If so follow steps 1, 4, 5, and 7. When calibrated and operated within the guidance of 3GPP TR 37.941 [38] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the AAS BS at the positioner. + - 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. + - 3) Configure the AAS BS such that the beam peak direction(s) applied during the power measurement step 6 are consistent with the grid and measurement approach for the TRP test. + - 4) Set the AAS BS to transmit according to the applicable test configuration in clause 5 using the corresponding test model(s) in clause 4.12.2. +- In addition, for an AAS BS declared to be capable of multi-carrier and/or CA operation use the applicable test signal configuration and corresponding power setting specified in clause 4.11. +- 5) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex F). + - 6) Measure the radiated power for any two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular beam direction pair as $EIRP = EIRP_{p1} + EIRP_{p2}$ . + +If the test chamber is a reverberation chamber measure TRP directly. + +- 7) Measure EIRP for any two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . +- 8) Calculate TRP using the power measurements. + +For multi-band capable AAS BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carriers activated in the other band. + +#### 6.3.2.5 Test Requirement + +The TRP measurement result in step 9 of clause 6.3.2.4.2 shall for UTRA, E-UTRA and NR remain: + +- within +3.4 dB and -3.4dB of the manufacturer's declared rated TRP value for carrier frequency $f \leq 3.0$ GHz; +- within +3.5 dB and -3.5 dB of the manufacturer's declared rated TRP value for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +### 6.3.3 OTA E-UTRA DL RS power + +#### 6.3.3.1 Definition and applicability + +This requirement applies to the RIB(s) transmitting primary DL RS. + +The DL RS power is the resource element power of the Downlink Reference Symbol at the RIB transmitting the DL RS for a cell. + +The absolute DL RS power is indicated on the DL-SCH. The absolute accuracy is defined as the maximum deviation between the DL RS power indicated on the DL-SCH and the DL RS power of each E-UTRA carrier. + +#### 6.3.3.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.3.3.2. + +There is no DL RS power requirement for *single RAT UTRA operation*. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.3.3.4. + +### 6.3.3.3 Test purpose + +The test purpose is to verify that the E-UTRA FDD DL RS power is within the limits specified by the minimum requirement. + +### 6.3.3.4 Method of test + +#### 6.3.3.4.1 Initial conditions + +Test environment: normal: see annex G.2. + +RF channels to be tested: B, M and T; see clause 4.12.1. + +Beams to be tested: The narrowest declared beam (see table 4.10-1, D9.3, D9.11). + +Directions to be tested: The *reference beam direction pair* (see table 4.10-1, D9.7). + +#### 6.3.3.4.2 Procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the AAS BS according to the declared beam direction pair +- 5) Set the AAS BS to transmit using E-TM 1.1, in 36.141 [12]TS 36.141 [12] clause 6.1.1.1 at manufacturers declared *rated carrier EIRP* ( $P_{\text{rated,c,EIRP}}$ ). +- 6) Measure the average OFDM symbol power as defined in annex F by measuring the EIRP for any two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $\text{EIRP} = \text{EIRP}_{\text{p1}} + \text{EIRP}_{\text{p2}}$ . + +The DL RS power is measured according to annex F in 36.141 [12]TS 36.141 [12]. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 7) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.3.3.5 Test Requirement + +The DL RS EIRP of each E-UTRA carrier shall be: + +within $\pm 3,4$ dB of the declared DL RS EIRP (see table 4.10-1, D9.30) for carrier frequency $f \leq 3.0$ GHz. + +within $\pm 3,6$ dB of the declared DL RS EIRP (see table 4.10-1, D9.30) for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +## 6.4 OTA Output power dynamics + +### 6.4.1 General + +The requirements in TS 37.105 [6] clause 9.4 apply during the *transmitter ON period*. Transmit signal quality (as specified in clause 9.6 of the TS 37.105 [6]) shall be maintained for the output power dynamics requirements. Power control is used to limit the interference level. The TA output power requirements are *directional requirements* and apply to the *beam peak directions* associated with the *beam direction pairs* over the *OTA peak directions set*. + +## 6.4.2 OTA UTRA Inner loop power control in the downlink + +### 6.4.2.1 Definition and applicability + +Inner loop power control in the downlink is the ability of the AAS BS transmitter to adjust the transmitter output power of a code channel in accordance with the corresponding TPC symbols received in the uplink. + +### 6.4.2.2 Minimum requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.2.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.2.3. + +This requirement does not apply to single RAT E-UTRA or NR operation. + +### 6.4.2.3 Test purpose + +The test purpose is to verify that the Inner loop power control in the downlink is within the limits specified by the minimum requirement. + +### 6.4.2.4 Method of test + +#### 6.4.2.4.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested: M; see clause 4.12.1. + +Beams to be tested: The narrowest declared beam (see table 4.10-1, D9.3, D9.11). + +Directions to be tested: The *reference beam direction pair* (see table 4.10-1, D9.7). + +Disable closed loop power control. + +The DPCH intended for power control is on channel 120 starting at -3 dB. + +Establish downlink power control with parameters as specified in table 6.4.2.4.1-1. + +**Table 6.4.2.4.1-1: DL power control parameters** + +| Parameter | Level/status | Unit | +|----------------------|--------------------------------------|------| +| UL signal mean power | $P_{\text{REFSENS}} + 10 \text{ dB}$ | dBm | +| Data sequence | PN9 | | + +#### 6.4.2.4.2 Procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the AAS BS according to the declared beam direction pair +- 5) Set the AAS BS to transmit using TM2, in TS 25.141 [10], clause 6.1.1.2 at the manufacturers declared *rated carrier EIRP* ( $P_{\text{rated,c,EIRP}}$ ). +- 6) Set and send alternating TPC bits from the UE simulator or UL signal generator. + +- 7) Measure mean power level of the code under the test each time TPC command is transmitted by measuring the EIRP for any two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . + +All steps within power control dynamic range declared by manufacturer (see table 4.10-1, D6.57) shall be measured. Use the code domain power measurement method defined in annex E in TS 25.141 [10]. + +- 8) Measure the 10 highest and the 10 lowest power step levels within the power control dynamic range declared by measuring the EIRP for any two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . + +Measure by sending 10 consecutive equal commands as described in TS 37.105 [6], clause 6.3.2. Table 6.3.2.3-2 + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 9) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 6.4.2.5 Test Requirement + +For UTRA FDD the test requirement Inner loop power control is: + +- a) AAS BS shall fulfil step size requirement shown in table 6.4.2.5-1 for all power control steps declared by manufacture in clause 4.10. +- b) For all measured Up/Down cycles, the difference of code domain power between before and after 10 equal commands (Up and Down), derived in step (3), shall not exceed the prescribed tolerance in table 6.4.2.5.1-2. + +**Table 6.4.2.5-1: UTRA FDD power control step tolerance** + +| Power control commands in the down link | Transmitter power control step tolerance | | | | | | | | +|-----------------------------------------|------------------------------------------|---------|------------------|----------|----------------|---------|------------------|----------| +| | 2 dB step size | | 1,5 dB step size | | 1 dB step size | | 0,5 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | Lower | Upper | +| Up (TPC command "1") | +0.9 dB | +3.1 dB | +0.65 dB | +2.35 dB | +0.4 dB | +1.6 dB | +0.15 dB | +0.85 dB | +| Down (TPC command "0") | -0.9 dB | -3.1 dB | -0.65 dB | -2.35 dB | -0.4 dB | -1.6 dB | -0.15 dB | -0.85 dB | + +**Table 6.4.2.5-2: UTRA FDD aggregated power control step range** + +| Power control commands in the down link | Transmitter aggregated power control step change after 10 consecutive equal commands (up or down) | | | | | | | | +|-----------------------------------------|---------------------------------------------------------------------------------------------------|----------|------------------|----------|----------------|----------|------------------|---------| +| | 2 dB step size | | 1,5 dB step size | | 1 dB step size | | 0,5 dB step size | | +| | Lower | Upper | Lower | Upper | Lower | Upper | Lower | Upper | +| Up (TPC command "1") | +15.9 dB | +24.1 dB | +11.9 dB | +18.1 dB | +7.9 dB | +12.1 dB | +3.9 dB | +6.1 dB | +| Down (TPC command "0") | -15.9 dB | -24.1 dB | -11.9 dB | -18.1 dB | -7.9 dB | -12.1 dB | -3.9 dB | -6.1 dB | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.4.3 OTA Power control dynamic range + +### 6.4.3.1 Definition and applicability + +The power control dynamic range is the difference between the maximum and the minimum *code domain power* of a code channel for a specified reference condition. + +This requirement applies at each RIB supporting transmission in the operating band. + +This requirement applies to UTRA operation only. + +#### 6.4.3.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.3.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.3.3. + +This requirement does not apply to single RAT E-UTRA or NR operation. + +#### 6.4.3.3 Test purpose + +The test purpose is to verify that the power control dynamic range is within the limits specified by the minimum requirement. + +#### 6.4.3.4 Method of test + +##### 6.4.3.4.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested: B, M and T; see clause 4.12.1. + +Beams to be tested: The narrowest declared beam (see table 4.10-1, D9.3, D9.11). + +Directions to be tested: The *reference beam direction pair* (see table 4.10-1, D9.7). + +##### 6.4.3.4.2 Procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the AAS BS according to the declared beam direction pair. +- 5) Set the AAS BS to transmit using TM2, in TS 25.141 [10], clause 6.1.1.2 at the manufacturers declared *rated carrier EIRP* ( $P_{\text{rated,c,EIRP}}$ ). +- 6) Using TM2, set the code domain EIRP of the DPCH under test to $P_{\text{max,c,EIRP}} - 3$ dB. Power levels for other code channels may be adjusted if necessary. +- 7) Measure the code domain EIRP of the code channel under test by either a) or b) below: + - a) If the test facility only supports single polarization, then measure EIRP with the test facility's test antenna/probe polarization matched to the AAS BS. Sum the EIRP measured on both polarizations. + - b) If the test facility supports dual polarization then measure total EIRP for two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $\text{EIRP} = \text{EIRP}_{\text{p1}} + \text{EIRP}_{\text{p2}}$ . + +Use the code domain power measurement method defined in annex E in TS 25.141 [10]. + +- 8) Set the code domain EIRP of the DPCH under test to $P_{\text{max,c,EIRP}} - 28$ dB by means determined by the manufacturer. The power levels for the other code channels used in step 2 shall remain unchanged (the overall output power will drop by approximately 3 dB). +- 9) Measure the code domain EIRP of the code channel under test by either a) or b) below: + +- a) If the test facility only supports single polarization, then measure EIRP with the test facility's test antenna/probe polarization matched to the AAS BS. Sum the EIRP measured on both polarizations. +- b) If the test facility supports dual polarization then measure total EIRP for two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 10) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.4.3.5 Test Requirement + +For UTRA FDD the test requirement Inner loop power control is: + +Downlink (DL) power control dynamic range: + +- maximum code domain power: maximum EIRP ( $P_{max,c,EIRP}$ ) –4.1 dB or greater; +- minimum code domain power: maximum EIRP ( $P_{max,c,EIRP}$ ) –26.9 dB or less. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.4.4 OTA total power dynamic range + +### 6.4.4.1 Definition and applicability + +The total power dynamic range is the difference between the maximum and the minimum output power for a specified reference condition. + +This requirement applies at each RIB supporting transmission in the operating band. + +NOTE 1: The upper limit of the dynamic range is the BS maximum carrier EIRP ( $P_{max,c,EIRP}$ ). The lower limit of the dynamic range is the lowest minimum power from the AAS BS when no traffic channels are activated in the same direction using the same beam. + +Particularly for E-UTRA, the total power dynamic range is the difference between the maximum and the minimum transmit power of an OFDM symbol for a specified reference condition. + +NOTE 2: The upper limit of the dynamic range at a RIB is the OFDM symbol power at maximum carrier EIRP ( $P_{max,c,EIRP}$ ) when transmitting on all RBs. The lower limit of the dynamic range at a RIB is the OFDM symbol power when one resource block is transmitted. The OFDM symbol carries PDSCH or sPDSCH (for sTTI) and not contain RS, PBCH or synchronization signals in the same direction using the same beam. + +### 6.4.4.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.4.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.4.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.4.4. + +The minimum requirement for NR operation is in TS 38.104 [33], clause 6.3.3.2. + +### 6.4.4.3 Test purpose + +The test purpose is to verify that the total power dynamic range is within the limits specified by the minimum requirement. + +#### 6.4.4.4 Method of test + +##### 6.4.4.4.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested: B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single band operation; see clause 4.12.1. + +Beams to be tested: The narrowest declared beam (see table 4.10-1, D9.3, D9.11). + +Directions to be tested: The *reference beam direction pair* (see table 4.10-1, D9.7). + +##### 6.4.4.4.2 Procedure + +###### 6.4.4.4.2.1 General procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the AAS BS according to the declared beam direction pair. + +###### 6.4.4.4.2.2 UTRA FDD + +- 5) Set the AAS BS to transmit using TM2, in TS 25.141 [10], clause 6.1.1.2 at the manufacturers declared *rated carrier EIRP* ( $P_{\text{rated,c,EIRP}}$ ). + +The downlink total dynamic range is computed as the difference of the maximum EIRP, measured as defined in step 6 in clause 6.2.4.2 and the EIRP measured at step 3 of the Error Vector Magnitude test, as described in clause 6.6.4.4.2.1. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 6) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +###### 6.4.4.4.2.3 E-UTRA + +- 5) Set the AAS BS to transmit using E-TM 3.1 (or sE-TM3.1-1 for subslot TTI, or sE-TM3.1-2 for slot TTI), as defined in TS 36.141 [12] clause 6.1.1 at the manufacturers declared *rated carrier EIRP* ( $P_{\text{rated,c,EIRP}}$ ). +- 6) Measure the average OFDM symbol EIRP as defined in annex F in TS 36.141 [12] by either a) or b) below: + - a) If the test facility only supports single polarization, then measure EIRP with the test facility's test antenna/probe polarization matched to the AAS BS. Sum the EIRP measured on both polarizations. + - b) If the test facility supports dual polarization then measure total EIRP for two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular beam direction pair as $\text{EIRP} = \text{EIRP}_{\text{p1}} + \text{EIRP}_{\text{p2}}$ . +- 7) Set the AAS BS to transmit using E-TM2 (or sE-TM2-1 for subslot TTI, or sE-TM2-2 for slot TTI), with the same selection as in step 5), as defined in TS 36.141 [12] clause 6.1.1. +- 8) Measure the average OFDM symbol power as defined in annex F of TS 36.141 [12] by either a) or b) below: + - a) If the test facility only supports single polarization, then measure EIRP with the test facility's test antenna/probe polarization matched to the AAS BS. Sum the EIRP measured on both polarizations. + +- b) If the test facility supports dual polarization then measure total EIRP for two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . + +The measured OFDM symbols shall not contain RS, PBCH or synchronisation signals. + +- 9) If BS supports 256QAM, set the channel set-up of the transmitted signal according to E-TM3.1a (or sE-TM3.1a-1 for subslot TTI, or sE-TM3.1a-2 for slot TTI) and repeat step 6. Set to transmit a signal according to E-TM 2a (or sE-TM2a-1 for subslot TTI, or sE-TM2a-2 for slot TTI) and repeat step 8. +- 10) If BS supports 1024QAM, set the channel set-up of the *TAB connector* transmitted signal according to E-TM3.1b and repeat step 6. Set the *TAB connector* to transmit a signal according to E-TM2b and repeat step 8. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 11) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.4.4.4.2.4 NR + +- 5) Set the BS to transmit a signal according to: + - NR-FR1-TM3.1b as defined in TS 38.141-1 [35] clause 4.9.2.2.6a if 1024QAM is supported by BS without power back off, or + - NR-FR1-TM3.1a as defined in TS 38.141-1 [35] clause 4.9.2.2.6 if 1024QAM is not supported by BS without power back off and 256QAM is supported by BS without power back off, or + - NR-FR1-TM3.1 as defined in TS 38.141-1 [35] clause 4.9.2.2.5 if 1024QAM and 256QAM are both not supported by BS without power back off. +- 6) Measure the average OFDM symbol power as defined by either a) or b) below: + - a) If the test facility only supports single polarization, then measure EIRP with the test facility's test antenna/probe polarization matched to the BS. Sum the EIRP measured on both polarizations. + - b) If the test facility supports dual polarization then measure total EIRP for two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . +- 7) Set the BS to transmit a signal according to: + - NR-FR1-TM2b as defined in TS 38.141-1 [35] clause 4.9.2.2.4a if 1024QAM is supported by BS, or + - NR-FR1-TM2a as defined in TS 38.141-1 [35] clause 4.9.2.2.4 if 1024QAM is not supported by BS but 256QAM is supported by BS, or + - NR-FR1-TM2 as defined in TS 38.141-1 [35] clause 4.9.2.2.3 if 1024QAM and 256QAM are not supported by BS. +- 8) Measure the average OFDM symbol power as defined by either a) or b) below: + - a) If the test facility only supports single polarization, then measure EIRP with the test facility's test antenna/probe polarization matched to the BS. Sum the EIRP measured on both polarizations. + - b) If the test facility supports dual polarization then measure total EIRP for two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . + +The measured OFDM symbols shall not contain RS or SSB. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 9) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 6.4.4.5 Test Requirement + +### 6.4.4.5.1 UTRA FDD + +For UTRA FDD the downlink total power dynamic range shall be 17.7 dB or greater. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.4.4.5.2 E-UTRA + +The downlink (DL) total power dynamic range for each E-UTRA carrier shall be larger than or equal to the level in table 6.4.4.5.1-1. + +**Table 6.4.4.5.2-1 E-UTRA total power dynamic range, paired spectrum** + +| E-UTRA channel bandwidth (MHz) | Total power dynamic range (dB) | +|--------------------------------|--------------------------------| +| 1.4 | 7.3 | +| 3 | 11.3 | +| 5 | 13.5 | +| 10 | 16.5 | +| 15 | 18.3 | +| 20 | 19.6 | + +NOTE 1: 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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +NOTE 2: Additional test requirements for the Error Vector Magnitude (EVM) at the lower limit of the dynamic range are defined in clause 6.6.4.5. + +### 6.4.4.5.3 NR + +The downlink (DL) total power dynamic range for each NR carrier shall be larger than or equal to the level in table 6.4.4.5.3-1. + +**Table 6.4.4.5.3-1: Total power dynamic range** + +| BS channel bandwidth (MHz) | Total power dynamic range (dB) | | | +|----------------------------|--------------------------------|------------|------------| +| | 15 kHz SCS | 30 kHz SCS | 60 kHz SCS | +| 5 | 13.5 | 10 | N/A | +| 10 | 16.7 | 13.4 | 10 | +| 15 | 18.5 | 15.3 | 12.1 | +| 20 | 19.8 | 16.6 | 13.4 | +| 25 | 20.8 | 17.7 | 14.5 | +| 30 | 21.6 | 18.5 | 15.3 | +| 35 | 22.7 | 19.6 | 16.4 | +| 40 | 22.9 | 19.8 | 16.6 | +| 45 | 23.8 | 20.7 | 17.6 | +| 50 | 23.9 | 20.8 | 17.7 | +| 60 | N/A | 21.6 | 18.5 | +| 70 | N/A | 22.3 | 19.2 | +| 80 | N/A | 22.9 | 19.8 | +| 90 | N/A | 23.4 | 20.4 | +| 100 | N/A | 23.9 | 20.9 | + +NOTE 1: 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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +NOTE 2: Additional test requirements for the Error Vector Magnitude (EVM) at the lower limit of the dynamic range are defined in clause 6.6.4.5. + +## 6.4.5 OTA IPDL time mask + +### 6.4.5.1 Definition and applicability + +To support IPDL location method in UTRA FDD operation, the AAS BS shall interrupt all transmitted signals in the downlink (i.e. common and dedicated channels). The IPDL time mask specifies the limits at the RIB output power during these idle periods. + +This requirement applies only to AAS BS supporting IPDL. The requirement applies at each RIB supporting transmission in the operating band. + +### 6.4.5.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.5.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.5.3. + +This requirement does not apply to single RAT E-UTRA or MSR E-UTRA/NR operation. + +### 6.4.5.3 Test purpose + +The test purpose is to verify the ability of the AAS BS to temporarily reduce its output power below a specified value to improve time difference measurements made by UE for location services. + +### 6.4.5.4 Method of test + +#### 6.4.5.4.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested: B, M and T; see clause 4.12.1. + +Beams to be tested: The narrowest declared beam (see table 4.10-1, D9.3, D9.11). + +Directions to be tested: The *reference beam direction pair* (see table 4.10-1, D9.7). + +Configure the AAS BS to produce idle periods in continuous mode. The IPDL parameters as defined in TS 25.214 [23] shall have the following values: + +- IP\_Spacing = 5 +- IP\_Length = 10 CPICH symbols +- Seed = 0 + +#### 6.4.5.4.2 Procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the AAS BS according to the declared beam direction pair. + +- 5) Set the AAS BS to transmit using TM1, in TS 25.141 [10], clause 6.1.1.2 at the manufacturers declared *rated carrier EIRP*( $P_{\text{rated,c,EIRP}}$ ). +- 6) Measure the mean EIRP over a period starting 27 chips after the beginning of the IPDL period and ending 27 chips before the expiration of the IPDL period by either a) or b) below: + - a) If the test facility only supports single polarization, then measure EIRP with the test facility's test antenna/probe polarization matched to the AAS BS. Sum the EIRP measured on both polarizations. + - b) If the test facility supports dual polarization then measure total EIRP for two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $\text{EIRP} = \text{EIRP}_{\text{p1}} + \text{EIRP}_{\text{p2}}$ . + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 7) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.4.5.5 Test Requirement + +The mean EIRP measured according to step (3) in clause 6.4.5.4.2 shall be equal to or less than + +$$\text{maximum EIRP } (P_{\text{max,c,EIRP}}) - 34.3 \text{ dB.}$$ + +See also figure 6.4.5.5-1. + +![Figure 6.4.5.5-1: IPDL Time Mask. The diagram shows a power level represented by a horizontal line labeled 'BS maximum output power'. A dashed horizontal line below it represents a lower power level, with a vertical double-headed arrow between them labeled '34.3 dB'. A central grey rectangular block represents the IPDL period. To the left of this block, a horizontal double-headed arrow labeled '27 chips' indicates the start of the measurement period. To the right of the block, another horizontal double-headed arrow labeled '27 chips' indicates the end of the measurement period. A long horizontal double-headed arrow at the bottom, spanning from the start of the first '27 chips' interval to the end of the second, is labeled 'IP_Length'.](07b81106e8525814c458f262000c54a9_img.jpg) + +Figure 6.4.5.5-1: IPDL Time Mask. The diagram shows a power level represented by a horizontal line labeled 'BS maximum output power'. A dashed horizontal line below it represents a lower power level, with a vertical double-headed arrow between them labeled '34.3 dB'. A central grey rectangular block represents the IPDL period. To the left of this block, a horizontal double-headed arrow labeled '27 chips' indicates the start of the measurement period. To the right of the block, another horizontal double-headed arrow labeled '27 chips' indicates the end of the measurement period. A long horizontal double-headed arrow at the bottom, spanning from the start of the first '27 chips' interval to the end of the second, is labeled 'IP\_Length'. + +**Figure 6.4.5.5-1: IPDL Time Mask** + +**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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.4.6 OTA RE Power control dynamic range + +##### 6.4.6.1 Definition and applicability + +The RE power control dynamic range is the difference between the power of an RE and the average RE power for an AAS BS at maximum output power ( $P_{\text{rated,c,TRP}}$ ) for a specified reference condition. + +This requirement applies at each RIB supporting transmission in the operating band. + +##### 6.4.6.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.6.2. + +This requirement does not apply to *single RAT UTRA operation*. + +For AAS BS *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.4.6.4. + +#### 6.4.6.3 Method of test + +No specific test or test requirements are defined for RE Power control dynamic range. The Error Vector Magnitude test, as described in clause 6.6.4 provides sufficient test coverage for this requirement. + +### 6.5 OTA Transmit ON/OFF power + +#### 6.5.1 General + +OTA transmitter ON/OFF power requirements apply only to TDD operation of E-UTRA and NR. + +The OTA Transmit ON/OFF power requirements are co-location requirements and specified as the power sum of the supported polarization(s) at the *co-location reference* antenna conducted output(s), see clause 4.15. + +#### 6.5.2 OTA Transmitter OFF power + +##### 6.5.2.1 Definition and applicability + +OTA transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *Base Station RF Bandwidth(s)* centred on the central frequency of the *Base Station RF Bandwidth (s)* during the *transmitter OFF period*. For UTRA and E-UTRA, $N=1$ . For NR, $N = \text{SCS}/15$ , where SCS is Sub Carrier Spacing in kHz. + +For *multi-band RIBs and single band RIBs supporting transmission in multiple bands*, the requirement is only applicable during the *transmitter OFF period* in all supported operating bands. + +For AAS BS supporting intra-band contiguous CA, the transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *Aggregated BS Channel Bandwidth* $\text{BW}_{\text{Channel\_CA}}$ centred on $(F_{\text{edge,high}} + F_{\text{edge,low}})/2$ during the *transmitter OFF period*. N is equal to 1 if there are any UTRA or E-UTRA carriers, or for NR $N = \text{SCS}/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *Aggregated BS Channel Bandwidth*. + +##### 6.5.2.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.5.2.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.5.2.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.5.2.4. + +##### 6.5.2.3 Test purpose + +The purpose of this test is to verify the OTA transmitter OFF power is within the limits of the minimum requirements. + +#### 6.5.2.4 Method of test + +##### 6.5.2.4.1 Initial conditions + +Test environment: + +- normal; see annex G.2. + +RF channels to be tested: + +- M; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested: + +- $M_{\text{RFBW}}$ in single band operation, see clause 4.12.1; $B'_{\text{RFBW\_T\_RFBW}}$ and $B'_{\text{RFBW\_T\_RFBW}}$ in multi-band operation; see clause 4.12.1. + +#### 6.5.2.4.2 Procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Set the AAS BS in the direction of the declared beam peak direction of the beam direction pair, for the beam to be tested. +- 4) Place the *co-location test antenna* as specified in clause 4.15. +- 5) Configure the beam peak direction of the AAS BS according to the declared beam direction pair. +- 6) Set the AAS BS to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. For single carrier set the AAS BS to transmit at manufacturers declared *rated carrier TRP* ( $P_{\text{rated,c,TRP}}$ ). +- 7) For E-UTRA and UTRA, measure the mean power spectral density at the output(s) of co-location test antennas power sum over all supported polarizations over 70 $\mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth of the AAS BS centred on the central frequency of the RF bandwidth. 70 $\mu\text{s}$ average window centre is set from 35 $\mu\text{s}$ after end of one transmitter ON period + 17 $\mu\text{s}$ to 35 $\mu\text{s}$ before start of next transmitter ON period - 17 $\mu\text{s}$ . + +For NR, measure the mean power spectral density over 70/N $\mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth of the *TAB connector* centred on the central frequency of the RF bandwidth. 70/N $\mu\text{s}$ average window centre is set from 35/N $\mu\text{s}$ after end of one transmitter ON period + 10 $\mu\text{s}$ to 35/N $\mu\text{s}$ before start of next transmitter ON period – 10 $\mu\text{s}$ . N = SCS/15, where SCS is Sub Carrier Spacing in kHz. + +- 8) For an AAS BS supporting contiguous CA, measure the mean power spectral density at the output(s) of co-location test antenna as power sum over all supported polarizations over 70 $\mu\text{s}$ filtered with a square filter of bandwidth equal to the Aggregated Channel Bandwidth $BW_{\text{Channel\_CA}}$ centred on $(F_{\text{edge\_high}} + F_{\text{edge\_low}})/2$ . 70 $\mu\text{s}$ average window centre is set from 35 $\mu\text{s}$ after end of one transmitter ON period + 17 $\mu\text{s}$ to 35 $\mu\text{s}$ before start of next transmitter ON period - 17 $\mu\text{s}$ . + +In addition, for a multi-band RIB, the following steps shall apply: + +- 9) For a multi-band RIB and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.5.2.5 Test Requirement + +The mean power spectral density measured according to clause 6.5.2.4.2 shall be less than -102.6 dBm/MHz for carrier frequency $f \leq 3.0$ GHz. + +The mean power spectral density measured according to clause 6.5.2.4.2 shall be less than -102.4 dBm/MHz for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +For a multi-band RIB, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance given in annex C. + +### 6.5.3 OTA Transmitter transient period + +#### 6.5.3.1 Definition and applicability + +The OTA *transmitter transient period* is the time period during which the transmitter unit is changing from the OFF period to the ON period or vice versa. The OTA *transmitter transient period* is illustrated in figure 6.5.3.1-1. + +![Figure 6.5.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows the power level at a co-location reference antenna conducted output over time. The y-axis has 'ON power level (Informative)' and 'OFF power level'. The x-axis is 'Time'. The graph shows a curve representing the power level. It starts at the OFF power level, rises sharply during a 'Transmitter transient period', reaches the ON power level, and then falls sharply during another 'Transmitter transient period' back to the OFF power level. The 'Transmitter ON period (DL Timeslots and DwPTS)' is the duration where the power level is at the ON level. The 'UL Timeslots' are indicated above the ON power level. The 'GP and UpPTS' are indicated above the OFF power level. The 'Transmitter OFF period' is the duration where the power level is at the OFF level, before and after the ON period.](2303c01c42eb5b45539e6b0324701ee1_img.jpg) + +Figure 6.5.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows the power level at a co-location reference antenna conducted output over time. The y-axis has 'ON power level (Informative)' and 'OFF power level'. The x-axis is 'Time'. The graph shows a curve representing the power level. It starts at the OFF power level, rises sharply during a 'Transmitter transient period', reaches the ON power level, and then falls sharply during another 'Transmitter transient period' back to the OFF power level. The 'Transmitter ON period (DL Timeslots and DwPTS)' is the duration where the power level is at the ON level. The 'UL Timeslots' are indicated above the ON power level. The 'GP and UpPTS' are indicated above the OFF power level. The 'Transmitter OFF period' is the duration where the power level is at the OFF level, before and after the ON period. + +**Figure 6.5.3.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period** + +This requirement applies at *RIB* supporting reception in the operating band and is measured at the *co-location reference antenna conducted outputs*. + +### 6.5.3.2 Minimum Requirement + +This requirement does not apply to *single RAT UTRA operation*. + +For AAS BS in *single RAT E-UTRA* and NR operation, the minimum requirement is defined in TS 37.105 [6], clause 9.5.3.2. + +### 6.5.3.3 Test purpose + +The purpose of this test is to verify that the OTA transmitter transient periods are within the limits of the minimum requirements. + +### 6.5.3.4 Method of test + +#### 6.5.3.4.1 Initial conditions + +Test environment: + +- normal; see annex G.2. + +RF channels to be tested for single carrier: + +- M; see clause 4.12.1. + +RF bandwidth positions to be tested for multi-carrier and/or CA: + +- $M_{\text{RFBW}}$ in single-band operation, see clause 4.12.1; $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.12.1. + +#### 6.5.3.4.2 Procedure + +- 1) Place the AAS BS at the positioner. + +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Set the AAS BS in the direction of the declared *beam peak direction* of the *beam direction pair*, for the beam to be tested. +- 4) Place the *co-location test antenna* as specified in clause 4.15. +- 5) Configure the beam peak direction of the AAS BS according to the declared beam direction pair. +- 6) Set the AAS BS to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. For single carrier set the AAS BS to transmit at manufacturers declared *rated carrier TRP* ( $P_{\text{rated,c,TRP}}$ ). +- 7) Measure the mean power spectral density at the output(s) of co-location test antenna as power sum over all supported polarizations over 70 $\mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth of the AAS BS centred on the central frequency of the RF bandwidth. 70 $\mu\text{s}$ average window centre is set from 35 $\mu\text{s}$ after end of one transmitter ON period + 17 $\mu\text{s}$ to 35 $\mu\text{s}$ before start of next transmitter ON period - 17 $\mu\text{s}$ . +- 8) For an AAS BS supporting contiguous CA, measure the mean power spectral density at the output(s) of co-location test antenna as power sum over all supported polarizations over 70 $\mu\text{s}$ filtered with a square filter of bandwidth equal to the Aggregated Channel Bandwidth $BW_{\text{Channel\_CA}}$ centred on $(F_{\text{edge\_high}}+F_{\text{edge\_low}})/2$ . 70 $\mu\text{s}$ average window centre is set from 35 $\mu\text{s}$ after end of one transmitter ON period + 17 $\mu\text{s}$ to 35 $\mu\text{s}$ before start of next transmitter ON period - 17 $\mu\text{s}$ . + +In addition, for a multi-band RIB, the following steps shall apply: + +- 9) For a multi-band RIB and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.5.3.5 Test Requirement + +The mean power spectral density measured according to clause 6.5.3.4.2 shall be less than -102.6 dBm/MHz for carrier frequency $f \leq 3.0$ GHz. + +The mean power spectral density measured according to clause 6.5.3.4.2 shall be less than -102.4 dBm/MHz for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. + +For a multi-band RIB, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.6 OTA Transmitted signal quality + +### 6.6.1 General + +Unless otherwise stated, the requirements in clause 6.6 apply during the *transmitter ON period*. + +### 6.6.2 OTA Frequency Error + +#### 6.6.2.1 Definition and applicability + +OTA frequency error is the measure of the difference between the actual AAS BS transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation. + +The OTA frequency error requirement is defined as a directional requirement at the RIB and shall be met within the *OTA coverage range*. + +### 6.6.2.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.6.2.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.6.2.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.6.2.4. + +### 6.6.2.3 Test purpose + +The test purpose is to verify that OTA frequency error is within the limit specified by the minimum requirement. + +### 6.6.2.4 Method of test + +Requirement is tested together with OTA modulation quality test, as described in clause 6.6.4. + +NOTE: Measurement only in the OTA coverage range reference direction (see table 4.10-1, D11.4) is enough for OTA frequency error measurement. + +### 6.6.2.5 Test Requirement + +#### 6.6.2.5.1 UTRA FDD test requirement + +The OTA frequency error for every measured slot shall be between the minimum and maximum value specified in table 6.6.2.5.1-1. + +**Table 6.6.2.5.1-1: OTA frequency error test requirement** + +| BS class | Accuracy | +|-----------------|-----------------------------------------| +| Wide Area BS | $\pm(0.05 \text{ ppm} + 12 \text{ Hz})$ | +| Medium Range BS | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | +| Local Area BS | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.6.2.5.2 E-UTRA and NR test requirement + +The modulated carrier frequency of each E-UTRA and NR carrier configured by the AAS BS shall be accurate to within the accuracy range given in table 6.6.2.5.2-1 observed over a period of one subframe (1 ms). + +**Table 6.6.2.5.2-1: OTA frequency error test requirement** + +| BS class | Accuracy | +|-----------------|-----------------------------------------| +| Wide Area BS | $\pm(0.05 \text{ ppm} + 12 \text{ Hz})$ | +| Medium Range BS | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | +| Local Area BS | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.6.3 OTA Time alignment error + +### 6.6.3.1 Definition and applicability + +This requirement applies to frame timing in: + +- UTRA single/multi-carrier transmissions and their combinations with MIMO or TX diversity. +- E-UTRA and/or NR single/multi-carrier transmissions and their combinations with MIMO or TX diversity. +- E-UTRA and /or NR *carrier aggregation*, with or without MIMO or TX diversity (except NR). + +Frames of the UTRA/E-UTRA/NR signals present in the radiated domain are not perfectly aligned in time. In relation to each other, the RF signals present in the radiated domain may experience certain timing differences. + +For a specific set of signals/transmitter configuration/transmission mode, the OTA Time Alignment Error (OTA TAE) is defined as the largest timing difference between any two different E-UTRA signals or any two different UTRA or any two different NR signals belonging to different *reference symbols* (e.g. CRS0 or CRS1 for E-UTRA, DMRS ports 1000 and 1001 for NR) in the radiated domain. The OTA time alignment error requirement is defined as a *directional requirement* at the RIB and shall be met within the *OTA coverage range*. + +### 6.6.3.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.6.3.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.6.3.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.6.3.4. + +### 6.6.3.3 Test purpose + +The test purpose is to verify that the OTA time alignment error is within the limit specified by the minimum requirement. + +### 6.6.3.4 Method of test + +#### 6.6.3.4.1 Initial conditions + +##### 6.6.3.4.1.1 General test conditions + +Test environment: + +- normal; see annex G.2. + +RF channels to be tested for single carrier: + +- M; see clause 4.12.1. + +Directions to be tested: The OTA coverage range reference direction (see table 4.10-1, D11.4). + +For dual polarized systems the requirement shall be tested and met considering both polarisations. If the measurement antenna does not support dual polarization, time alignment error shall be measured under the condition that measurement antenna is aligned between the AAS BS polarisations such that it receives half the power from each polarisation. + +##### 6.6.3.4.1.2 UTRA FDD + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single-band operation; $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ in multi-band operation, see clause 4.12.1. + +Refer to clause D.1.3 for a functional block diagram of the test set-up. + +##### 6.6.3.4.1.3 E-UTRA and NR + +*Base Station RF Bandwidth* positions to be tested for multi-carrier and/or CA: + +- $M_{\text{RFBW}}$ in single-band operation, see clause 4.12.1; $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}^{\text{RFBW}}$ in multi-band operation, see clause 4.12.1. + +#### 6.6.3.4.2 Procedure + +##### 6.6.3.4.2.1 General Procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the AAS BS according to the direction to be tested. + +##### 6.6.3.4.2.2 UTRA FDD Procedure + +- 5) If the AAS BS supports TX diversity or MIMO, set the AAS BS to transmit TM1, clause 4.12.2, at manufacturer's declared rated carrier TRP, $P_{\text{rated,c,TRP}}$ using TX diversity or MIMO. +- 6) Measure the time alignment error between the signals using different P-CPICH and CPICH signals on different beams. +- 7) If the AAS BS supports DC-HSDPA, 4C-HSDPA, NC-4C-HSDPA or 8C-HSDPA set the AAS BS to transmit according to TM1, without using TX diversity or MIMO, on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. +- 8) Measure the time alignment error between the signals using the P-CPICH and CPICH signals on another beam. +- 9) If the AAS BS supports DB-DC-HSDPA or any of the multi-band 4C-HSDPA or 8C-HSDPA configurations set the AAS BS to transmit TM1 on two carriers belonging to different frequency bands, without using TX diversity or MIMO on any of the carriers. +- 10) Measure the time alignment error between the signals using different P-CPICH and CPICH signals on different beams. + +In addition, for a multi-band RIB, the following steps shall apply: + +- 11) For a multi-band RIB and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +##### 6.6.3.4.2.3 E-UTRA and NR Procedure + +- 5) Set the AAS BS to transmit E-TM1.1 or NR-FR1-TM1.1 or any DL signal using TX diversity (except NR), MIMO transmission or carrier aggregation, using the configuration with the minimum number of cells and reference signals. + +NOTE 1: For TX diversity and MIMO transmissions, different ports may be configured in E-TM (using $p = 0$ and 1). + +NOTE 2: For MIMO transmission, different ports may be configured in NR-FR1-TM (using ports 1000 and 1001). + +For an AAS BS declared to be capable of single carrier operation only, set the AAS BS to transmit according to manufacturer's declared rated carrier TRP, $P_{\text{rated,c,TRP}}$ . + +If the AAS BS supports intra band contiguous or non-contiguous Carrier Aggregation set the AAS BS to transmit using the applicable test configuration and corresponding power setting specified in clause 4.11. + +If the AAS BS supports inter band carrier aggregation set the AAS BS to transmit, for each band, a single carrier or all carriers, using the applicable test configuration and corresponding power setting specified in clause 4.11. + +- 6) Measure the time alignment error between the different reference symbols on different beams on the carrier(s). + +In addition, for a multi-band RIB, the following steps shall apply: + +- 7) For a multi-band RIB and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.6.3.5 Test Requirement + +#### 6.6.3.5.1 UTRA FDD test requirement + +For Tx diversity and MIMO transmission, in the tested cell, TAE shall not exceed 0.35 $T_c$ . + +For transmission of multiple cells within a frequency band TAE shall not exceed 0.6 $T_c$ . + +For transmission of multiple cells in different frequency bands TAE shall not exceed 5.1 $T_c$ . + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.6.3.5.2 E-UTRA test requirement + +For MIMO or TX diversity transmissions, at each carrier frequency, TAE shall not exceed 90 ns. + +For intra-band carrier aggregation, with or without MIMO or TX diversity, TAE shall not exceed 155 ns. + +For intra-band non-contiguous carrier aggregation, with or without MIMO or TX diversity, TAE shall not exceed 285 ns. + +For inter-band carrier aggregation, with or without MIMO or TX diversity, TAE shall not exceed 285 ns. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 6.6.3.5.3 NR test requirement + +For MIMO transmission, at each carrier frequency, OTA TAE shall not exceed 90 ns. + +For intra-band contiguous carrier aggregation, with or without MIMO, OTA TAE shall not exceed 285 ns. + +For intra-band non-contiguous carrier aggregation, with or without MIMO, OTA TAE shall not exceed 3.025 $\mu$ s. + +For inter-band carrier aggregation, with or without MIMO, OTA TAE shall not exceed 3.025 $\mu$ s. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.6.4 OTA modulation quality + +#### 6.6.4.1 Definition and applicability + +OTA modulation quality is defined by the difference between the measured carrier signal and a reference signal. Modulation quality can be expressed e.g. as Peak Code Domain Error (PCDE) or Relative Code Domain Error (RCDE) or Error Vector Magnitude (EVM) for UTRA and Error Vector Magnitude (EVM) for E-UTRA. + +The OTA modulation quality requirement is defined as a *directional requirement* at the RIB and shall be met within the *OTA coverage range*. + +#### 6.6.4.2 Minimum Requirement + +For AAS BS the in *MSR operation* minimum requirement is defined in TS 37.105 [6], clause 9.6.4.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.6.4.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.6.4.4. + +#### 6.6.4.3 Test purpose + +The test purpose is to verify that OTA modulation quality is within the limit specified by the minimum requirement. + +#### 6.6.4.4 Method of test + +##### 6.6.4.4.1 UTRA method of test + +###### 6.6.4.4.1.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested for single carrier: B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* position to be tested: + +- $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single-band operation, see clause 4.12.1; +- $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ in multi-band operation, see clause 4.12.1. + +Directions to be tested: + +- The OTA coverage range reference direction (see table 4.10-2, D11.4) and the OTA coverage range maximum directions (see table 4.10-2, D11.5). +- The EVM test is performed once using the narrowest beamwidth supported by the AAS BS + +For dual polarised systems the requirement shall be tested and met for each of the supported polarisations. + +##### 6.6.4.4.1.2 Procedure + +###### 6.6.4.4.1.2.1 General procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Move the AAS BS on the positioner in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the AAS BS according to the direction to be tested. + +###### 6.6.4.4.1.2.2 EVM procedure + +- 5) Set the AAS BS to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. For single carrier set the AAS BS to transmit at manufacturers declared rated carrier EIRP ( $P_{\text{rated,c,EIRP}}$ ). +- 6) For each carrier, measure the Error Vector Magnitude and frequency error as defined in annex D.1.1 and the mean EIRP (in the conformance direction) of the signal. The measurement shall be performed on all 15 slots of the frame defined by the Test Model. +- 7) Using the same setting as in step 5), set the AAS BS to transmit a signal according to TM4, clause 4.12.2, with X value equal to 18, and repeat step 6). If the requirement in clause 6.6.4.5 is not fulfilled, decrease the total output power by setting the base station to transmit a signal according to TM4 with X greater than 18, and repeat step 6). + +The following test shall be additionally performed if the base station supports HS-PDSCH transmission using 16QAM: + +- 8) Using the same setting as in step 5), set the base station to transmit according to TM5, clause 4.12.2. +- 9) Repeat step 6). + +In addition, for a multi-band RIB, the following steps shall apply: + +- 10) For multi-band RIB and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.6.4.4.1.2.3 PCDE procedure + +- 5) Set the AAS BS to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. For single carrier set the AAS BS to transmit at manufacturers declared rated carrier EIRP ( $P_{\text{rated,c,EIRP}}$ ). +- 6) Measure Peak code domain error according to annex D.1.1. The measurement shall be performed on all 15 slots of the frame defined by TM3. For an AAS BS declared to be capable of multi-carrier operation the measurement is performed on one of the carriers under test. + +In addition, for a multi-band RIB, the following steps shall apply: + +- 7) For multi-band RIB and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.6.4.4.1.2.4 RCDE procedure + +- 5) Set the AAS BS to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. For single carrier set the AAS BS to transmit at manufacturers declared rated carrier EIRP ( $P_{\text{rated,c,EIRP}}$ ). +- 6) Measure average Relative code domain error according to annex E. The measurement shall be performed over one frame defined by TM6 and averaged as specified in TS 25.141 [10] clause 6.7.4.4.2. For an AAS BS declared to be capable of multi-carrier operation the measurement is performed on one of the carriers under test. + +In addition, for a multi-band RIB, the following steps shall apply: + +- 7) For multi-band RIB and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.6.4.4.2 E-UTRA and NR method of test + +##### 6.6.4.4.2.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested for single carrier: B and T; see clause 4.12.1. + +RF bandwidth positions to be tested for multi-carrier and/or CA: + +- $B_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single-band operation, see clause 4.12.1; +- $B'_{\text{RFBW}}$ , $T'_{\text{RFBW}}$ and $B'_{\text{RFBW}}$ , $T'_{\text{RFBW}}$ in multi-band operation, see clause 4.12.1. + +Directions to be tested: + +- OTA coverage range reference direction (see table 4.10-2, D11.4) +- OTA coverage range maximum directions (see table 4.10-2, D11.5). + +Polarization to be tested: For dual polarized systems the requirement shall be tested and met for both polarizations. + +##### 6.6.4.4.2.2 Procedure + +- 1) Place the AAS BS at the positioner. + +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the AAS BS according to the direction to be tested. +- 5) Set the AAS BS to output according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12.2. + +For single carrier operation only, set the AAS BS to transmit signal according to E-TM3.1 for E-UTRA (or sE-TM3.1-1 for subslot TTI, or sE-TM3.1-2 for slot TTI), at manufacturers declared rated carrier EIRP ( $P_{\text{rated,c,EIRP}}$ ). + +For NR operation, set the AAS BS to transmit signal according following procedure for *BS type 1-O*: + +For *BS type 1-O* declared to be capable of single carrier operation only, set the BS to transmit a signal according to: + +- NR-FR1-TM3.1b if 1024QAM is supported by BS without power back off +- or NR-FR1-TM 3.1b at manufacturer's declared rated output power if 1024QAM is supported by BS with power back off, and NR-FR1-TM 3.1a if 256QAM is supported by BS without power back off +- or NR-FR1-TM 3.1b at manufacturer's declared rated output power if 1024QAM is supported by BS with power back off and NR-FR1-TM 3.1a at manufacturer's declared rated output power if 256QAM is supported by BS with power back off, and NR-FR1-TM3.1 at maximum power +- or NR-FR1-TM 3.1a if 1024QAM is not supported by BS and 256QAM is supported by BS without power back off +- or NR-FR1-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by BS with power back off and 1024QAM is not supported, and NR-FR1-TM3.1 at maximum power +- or NR-FR1-TM3.1 if highest modulation order supported by BS is 64QAM +- or NR-FR1-TM3.2 if highest modulation order supported by BS is 16QAM +- or NR-FR1-TM3.3 if highest modulation order supported by BS is QPSK. + +- 6) Measure the EVM and frequency error as defined in annex D. + +- 7) Repeat steps 5 and 6 for the following test models: + +- For E-UTRA: repeat steps 5 and 6 for E-TM 3.2, E-TM 3.3 and E-TM2, +- For E-UTRA with subslot TTI: repeat steps 5 and 6 for sE-TM3.2-1, sE-TM3.3-1 and sE-TM2-1, +- For E-UTRA with slot TTI: repeat steps 5 and 6 for sE-TM3.2-2, sE-TM3.3-2 and sE-TM2-2. + +If 256QAM is supported by BS for E-UTRA: + +- For E-UTRA: repeat steps 5 and 6 for E-TM3.1a and E-TM2a, +- For E-UTRA with subslot TTI: repeat steps 5 and 6 for sE-TM3.1a-1 and sE-TM2a-1, +- For E-UTRA with slot TTI: repeat steps 5 and 6 for sE-TM3.1a-2 and sE-TM2a-2. + +For E-UTRA test model E-TM2 and E-TM2a the OFDM symbol power shall be at the lower limit of the OTA dynamic range according to the test procedure in clause 6.4.4.4.2 and test requirements in clause 6.4.4.5.2. + +For subslot TTI test model sE-TM2-1 and sE-TM2a-1 (or for sE-TM2-2 and sE-TM2a-2 for slot TTI) the OFDM symbol power shall be at the lower limit of the OTA dynamic range according to the test procedure in clause 6.4.4.4.2 and test requirements in clause 6.4.4.5.2. + +For NR: repeat steps 5 and 6 for NR-FR1-TM2 if 256QAM is not supported by *BS type 1-O* or for NR-FR1-TM2a if 256QAM is supported by *BS type 1-O* but 1024QAM is not supported by *BS type 1-O* or for NR-FR1-TM2b if 1024QAM is supported by *BS type 1-O*. For NR-FR1-TM2, NR-FR1-TM2a and NR-FR1-TM2b the + +OFDM symbol power (in the conformance direction) shall be at the lower limit of the dynamic range according to the test procedure in clause 6.4.4.4.2.4 and test requirements in clause 6.4.4.5.3. + +In addition, for multi-band RIB, the following steps shall apply: + +- 8) For multi-band RIB and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 6.6.4.5 Test Requirement + +### 6.6.4.5.1 UTRA test requirement + +The Error Vector Magnitude for each UTRA carrier and every measured slot shall be less than 18.5 % when the AAS BS is transmitting a composite signal using only QPSK modulation and shall be less than 13.5 % when the AAS BS is transmitting a composite signal that includes 16QAM modulation. + +The peak code domain error for every measured slot shall not exceed 32 dB at spreading factor 256. + +The average Relative Code Domain Error for 64QAM modulated codes shall not exceed 20 dB at spreading factor 16. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.6.4.5.2 E-UTRA and NR test requirement + +The EVM of each E-UTRA carrier for different modulation schemes on PDSCH or sPDSCH shall be less than the limits in table 6.6.4.5.2-1. + +The EVM of each NR carrier for different modulation schemes on PDSCH shall be less than the limits in table 6.6.4.5.2-1a. + +**Table 6.6.4.5.2-1: EVM requirements for E-UTRA** + +| Modulation scheme for PDSCH or sPDSCH | Required EVM (%) | +|---------------------------------------|------------------| +| QPSK | 18.5 | +| 16QAM | 13.5 | +| 64QAM | 9 | +| 256QAM | 4.5 | +| 1024QAM | 3.5 | + +**Table 6.6.4.5.2-1a: EVM requirements for NR** + +| Modulation scheme for PDSCH | Required EVM (%) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| QPSK | 18.5 | +| 16QAM | 13.5 | +| 64QAM | 9 | +| 256QAM | 4.5 | +| 1024QAM | 3.5 % 1
3.8 % 2 | +| NOTE 1: This requirement is applicable for frequencies equal to or below 4.2 GHz.
NOTE 2: This requirement is applicable for frequencies above 4.2 GHz. | | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +The EVM requirement shall be applicable within a time period around the centre of the CP therefore the EVM requirement is tested against the maximum of the RMS average of 10 subframes at the two window W extremities. + +For E-UTRA, the EVM window length (W) for normal CP and extended CP is specified in TS 36.104 [4], annex E.5.1. + +**Table 6.6.4.5.2-2: Void** + +For NR, the EVM window length (W) for normal CP and extended CP is specified in TS 38.104 [36], annex B.5.2. + +## 6.7 OTA Unwanted Emissions + +### 6.7.1 General + +Unwanted emissions consist of so-called out-of-band emissions and spurious emissions according to ITU definitions TS 25.331 [15]. In ITU terminology, 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. 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. + +OTA unwanted emissions for *OTA AAS BS* in *single RAT E-UTRA operation* and *MSR operation* using E-UTRA consist of an OTA operating band unwanted emissions requirement and OTA spurious emissions requirement. OTA operating band unwanted emissions requirement defines limits for emissions in each supported *downlink operating band* plus the frequency ranges $\Delta f_{\text{OBUE}}$ above and $\Delta f_{\text{OBUE}}$ below each band, where $\Delta f_{\text{OBUE}}$ is the maximum offset of the operating band unwanted emission mask from the operating band edge. Emissions outside of this frequency range are limited by OTA spurious emissions requirement. + +The values of $\Delta f_{\text{OBUE}}$ are defined for OTA AAS BS for E-UTRA, NR and UTRA FDD operating bands in Table 6.7.1-1. + +**Table 6.7.1-1: Maximum offset of OBUE outside the downlink operating band** + +| BS type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ [MHz] | +|------------|--------------------------------------------------------------------------------------|--------------------------------| +| OTA AAS BS | $F_{\text{DL\_high}} - F_{\text{DL\_low}} < 100 \text{ MHz}$ | 10 | +| | $100 \text{ MHz} \leq F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 900 \text{ MHz}$ | 40 | + +OTA unwanted emissions for *OTA AAS BS* in *single UTRA operation* and *MSR operation* using UTRA consist of OTA spectrum emission mask requirement and OTA spurious emissions requirement. + +NOTE: For definitions of conducted unwanted emissions requirements refer to clause 6.6 in TS 37.145-1 [9]. + +The unwanted emission requirements are applied per cell for all the configurations supported by *OTA AAS BS*. Requirements for OTA unwanted emissions are captured using TRP, *directional requirements* or co-location requirements as described per requirement. + +There is in addition a requirement for occupied bandwidth and an ACLR requirement. + +## 6.7.2 OTA occupied bandwidth + +### 6.7.2.1 Definition and applicability + +The OTA occupied bandwidth is the width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage $\beta/2$ of the total mean transmitted power. See also recommendation ITU-R SM.328 [14]. + +The value of $\beta/2$ shall be taken as 0.5%. + +The OTA occupied bandwidth requirement applies during the *transmitter ON period* for a single transmitted carrier. The minimum requirement below may be applied regionally. There may also be regional requirements to declare the OTA occupied bandwidth according to the definition in the present clause. + +The OTA occupied bandwidth is defined as a *directional requirement* and shall be met in the manufacturer's declared *OTA coverage range* at the RIB. + +### 6.7.2.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.2.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.2.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.2.4. + +### 6.7.2.3 Test purpose + +The test purpose is to verify that the emission at the *RIB* does not occupy an excessive bandwidth for the service to be provided and is, therefore, not likely to create interference to other users of the spectrum beyond undue limits. + +### 6.7.2.4 Method of test + +#### 6.7.2.4.1 Initial conditions + +##### 6.7.2.4.1.1 General test conditions + +Test environment: + +- normal; see annex G.2. + +RF channels to be tested: + +- M; see clause 4.12.1. + +Aggregated Channel Bandwidth positions to be tested for contiguous carrier aggregation: $M_{\text{BW Channel CA}}$ + +Directions to be tested: + +- The *reference beam direction pair* (see table 4.10-1, D9.7). + +##### 6.7.2.4.1.2 UTRA FDD + +- Set the AAS BS to transmit a signal in accordance to TM1 in clause 4.12.2 at manufacturers declared *rated carrier EIRP* ( $P_{\text{rated,c,EIRP}}$ ). + +##### 6.7.2.4.1.3 E-UTRA and NR + +- Aggregated Channel Bandwidth positions to be tested for contiguous carrier aggregation: +- $B_{\text{BW Channel CA}}$ , $M_{\text{BW Channel CA}}$ and $T_{\text{BW Channel CA}}$ . +- For a AAS BS declared to be capable of single carrier operation, start transmission according to E- TM1.1 or N- TM1.1, clause 4.12.2 at manufacturers declared *rated carrier EIRP* ( $P_{\text{rated,c,EIRP}}$ ). +- For a AAS BS declared to be capable of contiguous carrier aggregation operation, set the base station to transmit according to E- TM1.1 or N- TM1.1, on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 5 +- For an AAS BS declared to be capable of multi-carrier and/or CA operation use the applicable test signal configuration and corresponding power setting specified in clause 4.11. + +#### 6.7.2.4.2 Procedure + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. + +- 4) Configure the beam peak direction of the AAS BS according to the declared beam direction pair. +- 5) Set the AAS BS to transmit signal. +- 6) For UTRA FDD, measure the spectrum of the transmitted signal across a span of 10 MHz, based on an occupied bandwidth requirement of 5 MHz. The selected resolution bandwidth (RBW) filter of the analyser shall be 30 kHz or less. The spectrum shall be measured at 400 or more points across the measurement span. + +For E-UTRA and NR measure the spectrum emission of the transmitted signal using at least the number of measurement points, and across a span, as listed in table 6.7.2.4.2-1. The selected resolution bandwidth (RBW) filter of the analyser shall be 30 kHz or less. + +NOTE: The detection mode of the spectrum analyzer will not have any effect on the result if the statistical properties of the out-of-OBW power are the same as those of the inside-OBW power. Both are expected to have the Rayleigh distribution of the amplitude of Gaussian noise. In any case where the statistics are not the same, though, the detection mode is power responding. There are at least two ways to be power responding. The spectrum analyser can be set to "sample" detection, with its video bandwidth setting at least three times its RBW setting. Or the analyser may be set to respond to the average of the power (root-mean-square of the voltage) across the measurement cell. + +**Table 6.7.2.4.2-1: Span and number of measurement points for OBW measurements for FR1** + +| Bandwidth | BS channel bandwidth
BW Channel (MHz) | | | | | Aggregated BS
channel bandwidth
BW Channel_CA (MHz) | +|--------------------------------------|-----------------------------------------------------|-----|-----|-----|------|----------------------------------------------------------------------| +| | 5 | 10 | 15 | 20 | > 20 | > 20 | +| Span (MHz) | 10 | 20 | 30 | 40 | | $2 \times BW_{Channel\_CA}$ | +| Minimum number of measurement points | 400 | 400 | 400 | 400 | | $\left[ \frac{2 \times BW_{Channel\_CA}}{100kHz} \right]$ | + +- 7) Compute the total of the EIRP, P0, (in power units, not decibel units) of all the measurement cells in the measurement span. Compute P1, the EIRP outside the occupied bandwidth on each side. P1 is half of the total EIRP outside the bandwidth. P1 is half of (100 % - (occupied percentage)) of P0. For the occupied percentage of 99 %, P1 is 0.005 times P0. Measure the EIRP for any two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . +- 8) Determine the lowest frequency, f1, for which the sum of all EIRP in the measurement cells from the beginning of the span to f1 exceeds P1. +- 9) Determine the highest frequency, f2, for which the sum of all EIRP in the measurement cells from the end of the span to f2 exceeds P1. +- 10) Compute the OTA occupied bandwidth as f2 - f1. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 11) For *multi-band RIBs* and single band tests, repeat the steps 6) - 10) above per involved band where single band test configurations and test models shall apply with no carriers activated in the other band. + +## 6.7.2.5 Test Requirement + +### 6.7.2.5.1 MSR + +The OTA occupied bandwidth of a single carrier shall be less than the values listed in table 6.7.2.5.1-1. In addition, for E-UTRA/NR intra-band contiguous carrier aggregation, test requirement in clause 6.6.1.5 of TS 36.141 [12] applies for the E-UTRA/NR component carriers that are aggregated. + +**Table 6.7.2.5.1-1: OTA Occupied bandwidth** + +| RAT | OTA Occupied bandwidth limit | +|------------|-------------------------------------| +| E-UTRA/NR | BW Channel | +| UTRA FDD | 5 MHz | + +### 6.7.2.5.2 UTRA FDD + +The OTA occupied bandwidth shall be less than 5 MHz based on a chip rate of 3,84 Mcps. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 6.7.2.5.3 E-UTRA + +The OTA occupied bandwidth for each E-UTRA carrier shall be less than the channel bandwidth. For contiguous CA, the occupied bandwidth shall be less than or equal to the Aggregated Channel Bandwidth as defined in TS 36.141 [12] clause 5.6. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 6.7.3 OTA Adjacent Channel Leakage power Ratio + +### 6.7.3.1 Definition and applicability + +OTA Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. The measured power is TRP. + +### 6.7.3.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.3.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.3.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.3.4. + +### 6.7.3.3 Test purpose + +To verify that the adjacent channel leakage power ratio requirement shall be met as specified by the minimum requirement. + +### 6.7.3.4 Method of test + +#### 6.7.3.4.1 Initial conditions + +##### 6.7.3.4.1.1 General test conditions + +Test environment: + +- normal; see annex G.2. + +RF channels to be tested for single carrier: + +- B and T; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $B_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single-band operation; see clause 4.12.1; $B'_{\text{RFBW}}$ , $T'_{\text{RFBW}}$ and $B'_{\text{RFBW}}$ , $T_{\text{RFBW}}$ in multi-band operation, see clause 4.12.1. + +#### 6.7.3.4.1.2 MSR + +For E-UTRA ACLR requirement outside the *Base Station RF Bandwidth edges* and the ACLR requirement applied inside sub-block gap, in addition, for non-contiguous spectrum operation or *Inter RF Bandwidth gap* for multi-band operation using, the test configurations defined in clause 4.8, the method of test described in clause 6.7.3.4.2 applies. + +#### 6.7.3.4.1.3 UTRA FDD + +Set the AAS BS to transmit a signal modulated in accordance to TM1, in clause 4.12.2. + +For an AAS BS declared to be capable of multi-carrier operation, set the base station to transmit according to TM1 on all carriers configured. + +#### 6.7.3.4.1.4 E-UTRA + +For an AAS BS declared to be capable of single carrier operation only set to transmit a signal according to E-TM1.1 in clause 4.12.2. + +For an AAS BS declared to be capable of multi-carrier and/or CA operation, set to transmit according to E-TM1.1 on all carriers configured. + +#### 6.7.3.4.1.5 NR + +For an AAS BS declared to be capable of single carrier operation only set to transmit a signal according to NR-FR1-TM1.1 in clause 4.12.2. + +For an AAS BS declared to be capable of multi-carrier and/or CA operation, set to transmit according to NR-FR1-TM1.1 on all carriers configured. + +#### 6.7.3.4.2 Procedure + +##### 6.7.3.4.2.1 General Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in in Annex F. An alternative method to measure TRP is to use a characterized and calibrated reverberation chamber. If so, follow steps 1, 3, 4, 6 and 9. When calibrated and operated within the guidance of 3GPP TR 37.941 [38] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) The measurement devices characteristics shall be: + - measurement filter bandwidth: defined in clause 6.7.3.5. + - detection mode: true RMS voltage or true power averaging. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 4) For single carrier operation, set the AAS BS to transmit according to the applicable test configuration in clause 5 using the corresponding test model(s) in clause 4.12.2 at manufacturers declared *rated carrier TRP* ( $P_{\text{rated,c,TRP}}$ ). + +For an AAS BS declared to be capable of multi-carrier and/or CA operation use the applicable test signal configuration and corresponding power setting specified in clause 4.11. + +- 5) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex F). + +- 6) Measure the absolute total power of the assigned channel frequency and the (adjacent channel frequency) +- 7) Repeat step 6-7 for all directions in the appropriated TRP measurement grid needed for TRPEstimate for each of the assigned channel frequency and the adjacent channel frequency (see Annex F). +- 8) Calculate TRPEstimate for the absolute total radiated power of the wanted channel and the adjacent channel and the ACLR estimate using the measurements made in Step 7. +- 9) Calculate relative ACLR estimate. + +NOTE 1: ACLR is calculated by the ratio of the absolute TRP of the assigned channel frequency and the absolute TRP of the adjacent frequency channel. + +NOTE 2: For FR1 the measurement uncertainty of the reverberation chamber for the relative ACLR is higher than the measurement uncertainty in clause 4.1.2 the test requirements in Table 6.7.3.5.1-1 shall be tightened following the procedure in clause 4.1.3. + +#### 6.7.3.4.2.2 MSR + +- 1) For E-UTRA and NR, measure OTA ACLR: + - outside the Base Station RF Bandwidth edges; + - inside sub-block gap for non-contiguous spectrum operation as specified in clause 6.7.3.5.1.1; + - inside Inter RF Bandwidth gap for multi-band operation. +- 2) For UTRA FDD, measure ACLR inside sub-block gap or Inter RF Bandwidth gap as specified in clause 6.7.3.5.1.2. +- 3) Measure Cumulative Adjacent Channel Leakage power Ratio (CACLR) inside sub-block gap or the *Inter RF Bandwidth gap* as specified in clause 6.7.3.5.1.3. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 4) For *multi-band RIB* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.7.3.4.2.3 UTRA FDD + +- 1) Measure OTA ACLR for 5 MHz and 10 MHz offsets both side of channel frequency. In multiple carrier case only offset frequencies below the lowest and above the highest carrier frequency used shall be measured. +- 2) For the OTA ACLR requirement applied inside sub-block gap for non-contiguous spectrum operation or inside *Inter RF Bandwidth gap* for multi-band operation: + - a) Measure OTA ACLR inside sub-block gap or *Inter RF Bandwidth gap* as specified in clause 6.7.3.5.2.1, if applicable. + - b) Measure OTA CACLR inside sub-block gap or *Inter RF Bandwidth gap* as specified in clause 6.7.3.5.2.2, if applicable. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 3) For *multi-band RIB* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.7.3.4.2.4 E-UTRA + +- 1) Measure OTA ACLR for the frequency offsets both side of channel frequency as specified in table 6.7.3.5.3.1-1 (Paired spectrum case) or Table 6.7.3.5.3.1-2 (Unpaired spectrum case) respectively. In multiple carrier case only offset frequencies below the lowest and above the highest carrier frequency used shall be measured. +- 2) For the OTA ACLR requirement applied inside sub-block gap for non-contiguous spectrum operation: or inside *Inter RF Bandwidth gap* for multi-band operation: + +- a) Measure OTA ACLR inside sub-block gap or *Inter RF Bandwidth gap* as specified in clause 6.7.3.5.3.1, if applicable. + - b) Measure OTA CACLR inside sub-block gap or *Inter RF Bandwidth gap* as specified in clause 6.7.3.5.3.2, if applicable. +- 3) Repeat the test with the channel set-up according to E- TM1.2 in clause 4.12.2. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 4) For *multi-band RIB* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.7.3.5 Test Requirement + +#### 6.7.3.5.1 MSR + +##### 6.7.3.5.1.1 MSR E-UTRA test requirement + +For E-UTRA, the test requirement is specified in tables 6.7.3.5.1.1-1 and 6.7.3.5.1.1-2, and applies outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. + +For an AAS BS operating in non-contiguous spectrum, the OTA ACLR also applies for the first adjacent channel inside any sub-block gap with a gap size $W_{\text{gap}} \geq 15$ MHz. The OTA ACLR requirement for the second adjacent channel applies inside any sub-block gap with a gap size $W_{\text{gap}} \geq 20$ MHz. The CACLR test requirement in clause 6.6.3.5.6.2 applies in sub-block gaps for the frequency ranges defined in table 6.6.3.5.6.2-1. + +For a *multi-band RIB*, the ACLR also applies for the first adjacent channel inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 15$ MHz. The ACLR requirement for the second adjacent channel applies inside any *Inter RF Bandwidth gap* with a gap size $W_{\text{gap}} \geq 20$ MHz. The OTA CACLR requirement in clause 6.7.3.5.3.2 applies in *Inter RF Bandwidth gaps* for the frequency ranges defined in Table 6.7.3.5.3.2-1. + +The requirement applies during the transmitter on period. + +The OTA ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal ( $BW_{\text{Config}}$ ) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +For operation in paired spectrum, the measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.1.1-1. + +**Table 6.7.3.5.1.1-1: OTA ACLR in paired spectrum** + +| Channel bandwidth of E-UTRA Lowest/Highest Carrier transmitted $BW_{\text{Channel}}$ (MHz) | BS adjacent channel centre frequency offset below the lower or above the upper Base Station RF Bandwidth edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| +| 1.4, 3.0, 5, 10, 15, 20 | $0.5 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8dB | +| | $1.5 \times BW_{\text{Channel}}$ | E-UTRA of same BW | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8dB | +| | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | + +NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{Config}}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +For operation in unpaired spectrum, the measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.1.1-2. + +**Table 6.7.3.5.1.1-2: OTA ACLR in unpaired spectrum with synchronized operation** + +| Channel bandwidth of E-UTRA Lowest/Highest Carrier transmitted BW Channel (MHz) | BS adjacent channel centre frequency offset below the lower or above the upper Base Station RF Bandwidth edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|--------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| +| 1.4, 3 | 0.5 x BW Channel | E-UTRA of same BW | Square (BW Config ) | 44 dB | 43.8dB | +| | 1.5 x BW Channel | E-UTRA of same BW | Square (BW Config ) | 44 dB | 43.8dB | +| | 0.8 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44 dB | 43.8dB | +| | 2.4 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44 dB | 43.8dB | +| 5, 10, 15, 20 | 0.5 x BW Channel | E-UTRA of same BW | Square (BW Config ) | 44 dB | 43.8dB | +| | 1.5 x BW Channel | E-UTRA of same BW | Square (BW Config ) | 44 dB | 43.8dB | +| | 0.8 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44 dB | 43.8dB | +| | 2.4 MHz | 1.28 Mcps UTRA | RRC (1.28 Mcps) | 44 dB | 43.8dB | +| | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| | 5 MHz | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 44 dB | 43.8dB | +| | 15 MHz | 7.68 Mcps UTRA | RRC (7.68 Mcps) | 44 dB | 43.8dB | + +NOTE 1: BWChannel and BWConfig are the channel bandwidth and transmission bandwidth configuration of the E-UTRA Lowest/Highest Carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.105 [3], with a chip rate as defined in this table. + +For operation in non-contiguous paired spectrum, the measurement results shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.1.1-3. + +**Table 6.7.3.5.1.1-3: OTA ACLR in non-contiguous paired spectrum** + +| Sub-block gap size (W gap ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|----------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| +| W gap ≥ 15 MHz | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| W gap ≥ 20 MHz | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | + +NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +For operation in non-contiguous unpaired spectrum, the measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.1.1-4. + +**Table 6.7.3.5.1.1-4: OTA ACLR in non-contiguous unpaired spectrum** + +| Sub-block gap size (W gap ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|----------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| +| W gap ≥ 15 MHz | 2.5 MHz | 5 MHz E-UTRA | Square (BW Config ) | 44 dB | 43.8dB | +| W gap ≥ 20 MHz | 7.5 MHz | 5 MHz E-UTRA | Square (BW Config ) | 44 dB | 43.8dB | + +For Category A, an E-UTRA AAS BS of Wide Area BS class, either the OTA ACLR limits in Tables 6.7.3.5.1.1-1/2/3/4 or OTA ACLR absolute limit of -4 dBm/MHz shall apply, whichever is less stringent. + +For Category B, an E-UTRA AAS BS of Wide Area BS class, either the OTA ACLR limits in Tables 6.7.3.5.1.1-1/2/3/4 or OTA ACLR absolute limit of -6 dBm/MHz shall apply, whichever is less stringent. + +For an E-UTRA AAS BS of Medium Range BS class, either the OTA ACLR limits in Tables 6.7.3.5.1.1-1/2/3/4 or OTA ACLR absolute limit of -16 dBm/MHz shall apply, whichever is less stringent. + +For an E-UTRA AAS BS of Local Area BS class, either the OTA ACLR limits in Tables 6.7.3.5.1.1-1/2/3/4 or OTA ACLR absolute limit of -23 dBm/MHz shall apply, whichever is less stringent. + +#### 6.7.3.5.1.2 MSR UTRA FDD test requirement + +For UTRA FDD, the test requirement is specified in Tables 6.7.3.5.1.2-1 and 6.7.3.5.1.2-2, and applies outside the *Base Station RF Bandwidth* or Maximum Radio Bandwidth. + +The measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.1.2-1. + +**Table 6.7.3.5.1.2-1: OTA ACLR** + +| BS channel offset below the first or above the last carrier frequency used | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| 5 MHz | 44 dB | 43.8dB | +| 10 MHz | 44 dB | 43.8dB | +| Note 1: | In certain regions, the adjacent channel power (the RRC filtered mean power centered on an adjacent channel frequency) shall be less than or equal to -7.2 dBm/3.84 MHz (for Band I, III, IX, XI and XXI) or +2.8 dBm/3.84 MHz (for Band VI, VIII and XIX) or as specified by the ACLR limit, whichever is the higher. This note is not applicable for Home BS. | | +| Note 2: | For Home BS, the adjacent channel power (the RRC filtered mean power centered on an adjacent channel frequency) shall be less than or equal to -42.7 dBm/3.84 MHz $f \leq 3.0$ GHz and -42.4 dBm/3.84 MHz for $3.0$ GHz $< f \leq 4.2$ GHz or as specified by the ACLR limit, whichever is the higher. | | + +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 clause 4.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex F. + +The measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.1.2-2. + +**Table 6.7.3.5.1.2-2: OTA ACLR in non-contiguous spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{gap}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|--------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| +| $W_{gap} \geq 15$ MHz | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| $W_{gap} \geq 20$ MHz | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| NOTE: | The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104, with a chip rate as defined in this table. | | | | | + +For an AAS BS operating in non-contiguous spectrum, OTA ACLR requirement also applies for the first adjacent channel, inside any sub-block gap with a gap size $W_{gap} \geq 15$ MHz. The OTA ACLR requirement for the second adjacent channel applies inside any sub-block gap with a gap size $W_{gap} \geq 20$ MHz. The OTA CACLR test requirement in clause 6.7.3.5.3.2 applies in sub block gaps for the frequency ranges defined in Table 6.7.3.5.3.2-1. + +For a multi-band capable AAS BS OTA ACLR requirement also applies for the first adjacent channel, inside any *Inter RF Bandwidth gap* with a gap size $W_{gap} \geq 15$ MHz. The OTA ACLR requirement for the second adjacent channel applies inside any *Inter RF Bandwidth gap* with a gap size $W_{gap} \geq 20$ MHz. The OTA CACLR requirement in clause 6.7.3.5.3.2 applies in *Inter RF Bandwidth gaps* for the frequency ranges defined in Table 6.7.3.5.3.2-1. + +For Category A, a UTRA AAS BS of Wide Area BS class, either the OTA ACLR limits in the Tables 6.7.3.5.1.2-1/2 or the absolute limit of -7 dBm/MHz shall apply, whichever is less stringent. + +For Category B, a UTRA AAS BS of Wide Area BS class, either the OTA ACLR limits in the Tables 6.7.3.5.1.2-1/2 or the absolute limit of -9 dBm/MHz shall apply, whichever is less stringent. + +For a UTRA AAS BS of Medium Range BS class, either the OTA ACLR limits in the Tables 6.7.3.5.1.2-1/2 or the absolute limit of -19 dBm/MHz shall apply, whichever is less stringent. + +For a UTRA AAS BS of Local Area BS class, either the OTA ACLR limits in the Tables 6.7.3.5.1.2-1/2 or the absolute limit of -26 dBm/MHz shall apply, whichever is less stringent. + +#### 6.7.3.5.1.3 OTA Cumulative ACLR test requirement in non-contiguous spectrum + +The following test requirement applies for sub-block or *Inter RF Bandwidth gap* sizes listed in Table 6.7.3.5.1.3-1: + +- Inside a sub-block gap within an operating band for a BS operating in non-contiguous spectrum. +- Inside an *Inter RF Bandwidth gap* for a BS operating in multiple bands, where multiple bands are mapped on the same antenna connector. + +The Cumulative Adjacent Channel Leakage power Ratio (CACLR) in a sub-block gap or the *Inter RF Bandwidth gap* is the ratio of: + +- a) the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the sub-block gap or the *Inter RF Bandwidth gap*; and +- b) the filtered mean power centred on a frequency channel adjacent to one of the respective sub-block edges or *Base Station RF Bandwidth edges*. + +The requirement applies to adjacent channels of E-UTRA or UTRA carriers allocated adjacent to each side of the sub-block gap or the *Inter RF Bandwidth gap*. The assumed filter for the adjacent channel frequency is defined in Table 6.7.3.5.1.3-1 and the filters on the assigned channels are defined in Table 6.7.3.5.1.3-2. + +NOTE: If the RAT on the assigned channel frequencies is different, the filters used are also different. + +The CACLR for E-UTRA and UTRA carriers located on either side of the sub-block gap or the *Inter RF Bandwidth gap* shall not be less than the value specified in Table 6.7.3.5.1.3-1. + +**Table 6.7.3.5.1.3-1: OTA CACLR in non-contiguous spectrum or multiple bands** + +| Band Category | Sub-block or Inter RF Bandwidth gap size (W gap ) where the limit applies [MHz] | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA CACLR limit for bands below 3GHz | OTA CACLR limit for bands between 3 and 4.2GHz | +|---------------|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------|------------------------------------------------| +| BC1, BC2 | 5 ≤ W gap < 15 (Note 3) | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| BC1, BC2 | 10 < W gap < 20 (Note 3) | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| BC3 | 5 ≤ W gap < 15 (Note 3) | 2.5 MHz | 5 MHz E-UTRA | Square (BW Config ) | 44 dB | 43.8dB | +| BC3 | 10 < W gap < 20 (Note 3) | 7.5 MHz | 5 MHz E-UTRA | Square (BW Config ) | 44 dB | 43.8dB | +| BC1, BC2, BC3 | 5 ≤ W gap < 45 (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8dB | +| BC1, BC2, BC3 | 10 ≤ W gap < 50 (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8dB | +| BC1, BC2, BC3 | 20 ≤ W gap < 30 (Note 3, 5) | 10 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8dB | +| BC1, BC2, BC3 | 20 ≤ W gap < 60 (Note 4) | 10 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 45 dB | 43.8dB | +| BC1, BC2, BC3 | 40 ≤ W gap < 50 (Note 3, 5) | 30 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8dB | +| BC1, BC2, BC3 | 40 ≤ W gap < 80 (Note 4) | 30 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8dB | + +NOTE 1: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. + +NOTE 2: With SCS that provides largest transmission bandwidth configuration (BWConfig). + +NOTE 3: Applicable in case the *channel bandwidth* of the carrier transmitted at the other edge of the gap is 5, 10, 15, 20 MHz. + +NOTE 4: Applicable in case the *channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 25, 30, 40, 50, 60, 70, 80, 90, 100 MHz. + +NOTE 5: Applicable in case the *channel bandwidth* of the NR carrier transmitted adjacent to sub-block gap or inter RF Bandwidth gap is 25, 30, 40, 50, 60, 70, 80, 90, 100 MHz. + +**Table 6.7.3.5.1.3-2: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the sub-block or Inter RF Bandwidth gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| E-UTRA | E-UTRA of same BW | +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | +| UTRA FDD | RRC (3.84 Mcps) | +| NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | + +For Category A, an E-UTRA or NR AAS BS of Wide Area BS class, either the OTA CACLR limits in Table 6.7.3.5.1.3-1 or OTA ACLR absolute limit of -4 dBm/MHz shall apply, whichever is less stringent. + +For Category B, an E-UTRA or NR AAS BS of Wide Area BS class, either the OTA CACLR limits in Table 6.7.3.5.1.3-1 or OTA ACLR absolute limit of -6 dBm/MHz shall apply, whichever is less stringent. + +For an E-UTRA or NR AAS BS of Medium Range BS class, either the OTA CACLR limits in Table 6.7.3.5.1.3-1 or OTA ACLR absolute limit of -16 dBm/MHz shall apply, whichever is less stringent. + +For an E-UTRA or NR AAS BS of Local Area BS class, either the OTA CACLR limits in Table 6.7.3.5.1.3-1 or OTA ACLR absolute limit of -23 dBm/MHz shall apply, whichever is less stringent. + +For Category A, a UTRA AAS BS of Wide Area BS class, either the OTA CACLR limits in Table 6.7.3.5.1.3-1 or OTA ACLR absolute limit of -7 dBm/MHz shall apply, whichever is less stringent. + +For Category B, a UTRA AAS BS of Wide Area BS class, either the OTA CACLR limits in Table 6.7.3.5.1.3-1 or OTA ACLR absolute limit of -9 dBm/MHz shall apply, whichever is less stringent. + +For a UTRA AAS BS of Medium Range BS class, either the OTA CACLR limits in Table 6.7.3.5.1.3-1 or OTA ACLR absolute limit of -19 dBm/MHz shall apply, whichever is less stringent. + +For a UTRA AAS BS of Local Area BS class, either the OTA CACLR limits in Table 6.7.3.5.1.3-1 or OTA ACLR absolute limit of -26 dBm/MHz shall apply, whichever is less stringent. + +#### 6.7.3.5.1.4 NR test requirement + +For the NR OTA ACLR requirement either the OTA ACLR limits in tables 6.7.3.5.1.4-1/2a or the OTA ACLR absolute limits in tables 6.7.3.5.1.4-2 shall apply, whichever is less stringent. The OTA CACLR limits in clause 6.7.3.5.1.3 shall also apply. + +For a RIB operating in non-contiguous spectrum, the OTA ACLR requirement applies inside sub block gaps for the frequency ranges defined in table 6.7.3.5.1.4-2a, while the CACLR requirement applies inside sub block gaps for the frequency ranges defined in table 6.7.3.5.1.3-1. + +For a *multi-band RIB*, the OTA ACLR test requirement applies inside Inter RF Bandwidth gaps for the frequency ranges defined in table 6.7.3.5.1.4-2a, while the OTA CACLR requirement applies inside Inter RF Bandwidth gaps for the frequency ranges defined in table 6.7.3.5.1.3-1. + +For operation in paired and unpaired spectrum, the OTA ACLR measurement result shall not be less than the OTA ACLR limit specified in table 6.7.3.5.1.4-1. + +**Table 6.7.3.5.1.4-1: NR ACLR limit** + +| BS channel bandwidth of lowest/highest NR carrier transmitted BW_{\text{Channel}} [MHz] | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit (0 – 3 GHz) | OTA ACLR limit (3 – 6 GHz) | +|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------|-----------------------------------| +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8 dB | +| | $2 \times BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8 dB | +| | $BW_{\text{Channel}}/2 + 2.5 \text{ MHz}$ | 5 MHz E-UTRA | Square (4.5 MHz) | 44 dB (Note 3) | 43.8 dB (Note 3) | +| | $BW_{\text{Channel}}/2 + 7.5 \text{ MHz}$ | 5 MHz E-UTRA | Square (4.5 MHz) | 44 dB (Note 3) | 43.8 dB (Note 3) | + +NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{Config}}$ are the BS channel bandwidth and transmission bandwidth configuration of the lowest/highest NR carrier transmitted on the assigned channel frequency. +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{\text{Config}}$ ). +NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. + +The absolute total power measurement shall not exceed the OTA ACLR absolute limit specified in table 6.7.3.5.1.4-2. + +**Table 6.7.3.5.1.4-2: NR ACLR absolute limit** + +| BS category / BS class | OTA ACLR absolute limit | +|-------------------------------|--------------------------------| +| Category A Wide Area BS | -4 dBm/MHz | +| Category B Wide Area BS | -6 dBm/MHz | +| Medium Range BS | -16 dBm/MHz | +| Local Area BS | -23 dBm/MHz | + +For operation in non-contiguous spectrum or multiple bands, the OTA ACLR measurement result shall not be less than the OTA ACLR limit specified in table 6.7.3.5.1.4-2a. + +**Table 6.7.3.5.1.4-2a: NR ACLR limit in non-contiguous spectrum or multiple bands** + +| BS channel bandwidth of NR carrier transmitted adjacent to sub-block gap or inter RF Bandwidth gap BW_{\text{Channel}} [MHz] | Sub-block or Inter RF Bandwidth gap size (W_{\text{gap}}) where the limit applies [MHz] | BS adjacent channel centre frequency offset below or above the sub-block or Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit (0-3GHz) | OTA ACLR limit (3-6GHz) | +|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|--------------------------------|--------------------------------| +| 5, 10, 15, 20 | $W_{\text{gap}} \geq 15$ (Note 3) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8 dB | +| | $W_{\text{gap}} \geq 45$ (Note 4) | | | | | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $W_{\text{gap}} \geq 20$ (Note 3)
$W_{\text{gap}} \geq 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8 dB | +| | $W_{\text{gap}} \geq 60$ (Note 4)
$W_{\text{gap}} \geq 30$ (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8 dB | +| | $W_{\text{gap}} \geq 80$ (Note 4)
$W_{\text{gap}} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8 dB | + +NOTE 1: $BW_{\text{Config}}$ is the transmission bandwidth configuration of the assumed adjacent channel carrier. +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{\text{Config}}$ ). +NOTE 3: Applicable in case the *BS channel bandwidth* of the carrier transmitted at the other edge of the gap is 5, 10, 15, 20 MHz. +NOTE 4: Applicable in case the *BS channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 25, 30, 40, 50, 60, 70, 80, 90, 100 MHz. + +The OTA CACLR measurement result shall not less than the OTA CACLR limit specified in table 6.7.3.5.1.4-1. + +## 6.7.3.5.2 UTRA FDD + +### 6.7.3.5.2.1 OTA ACLR + +The measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.2.1-1. + +**Table 6.7.3.5.2.1-1: OTA BS ACLR** + +| BS channel offset below the first or above the last carrier frequency used | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|-----------------------------------------------------------------------------------|--------------------------------------------|------------------------------------------------------| +| 5 MHz | 44 dB | 43.8dB | +| 10 MHz | 44 dB | 43.8dB | + +NOTE 1: In certain regions, the adjacent channel power (the RRC filtered mean power centred on an adjacent channel frequency) shall be less than or equal to -7.2 dBm/3.84 MHz (for Band I, III, IX, XI and XXI) or +2.8 dBm/3.84 MHz (for Band VI, VIII and XIX) or as specified by the ACLR limit, whichever is the higher. This note is not applicable for Home BS. +NOTE 2: For Home BS, the adjacent channel power (the RRC filtered mean power centred on an adjacent channel frequency) shall be less than or equal to -42.7 dBm/3.84 MHz $f \leq 3.0$ GHz and -42.4 dBm/3.84 MHz for $3.0$ GHz $< f \leq 4.2$ GHz or as specified by the ACLR limit, whichever is the higher. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +The measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.2.1-2. + +**Table 6.7.3.5.2.1-2: OTA ACLR in non-contiguous spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| +| $W_{\text{gap}} \geq 15$ MHz | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| $W_{\text{gap}} \geq 20$ MHz | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| NOTE: | The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | | | | + +For Category A, a UTRA AAS BS of Wide Area BS class, either the OTA ACLR limits in Tables 6.7.3.5.2.1-1/2 or OTA ACLR absolute limit of -7 dBm/MHz shall apply, whichever is less stringent. + +For Category B, a UTRA AAS BS of Wide Area BS class, either the OTA ACLR limits in Tables 6.7.3.5.2.1-1/2 or OTA ACLR absolute limit of -9 dBm/MHz shall apply, whichever is less stringent. + +For a UTRA AAS BS of Medium Range BS class, either the OTA ACLR limits in Tables 6.7.3.5.2.1-1/2 or OTA ACLR absolute limit of -19 dBm/MHz shall apply, whichever is less stringent. + +For a UTRA AAS BS of Local Area BS class, either the OTA ACLR limits in Tables 6.7.3.5.2.1-1/2 or OTA ACLR absolute limit of -26 dBm/MHz shall apply, whichever is less stringent. + +#### 6.7.3.5.2.2 OTA Cumulative ACLR test requirement in non-contiguous spectrum or multiple bands + +The following test requirement applies for an AAS BS operating in non-contiguous spectrum or multiple bands. + +The following requirement applies for the gap sizes listed in Table 6.7.3.5.2.2-1: + +- inside a sub-block gap within an operating band for an AAS BS operating in non-contiguous spectrum; +- inside an *Inter RF Bandwidth gap* for a multi-band capable AAS BS. + +The Cumulative Adjacent Channel Leakage power Ratio (CACLR) in a sub-block gap or *Inter RF Bandwidth gap* is the ratio of: + +- a) the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the sub-block gap or *Inter RF Bandwidth gap*; and +- b) the filtered mean power centred on a frequency channel adjacent to one of the respective sub-block edges or *Base Station RF Bandwidth edges*. + +The assumed filter for the adjacent channel frequency is defined in Table 6.7.3.5.2.2-1 and the filters on the assigned channels are defined in Table 6.7.3.5.2.2-2. + +The CACLR for UTRA carriers located on either side of the sub-block gap or *Inter RF Bandwidth gap* shall not be less than the value specified in Table 6.7.3.5.2.2-1. + +**Table 6.7.3.5.2.2-1: OTA CACLR in non-contiguous spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA CACLR limit for bands below 3GHz | OTA CACLR limit for bands between 3 and 4.2GHz | +|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------|------------------------------------------------| +| $5$ MHz $\leq W_{\text{gap}} < 15$ MHz | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| $10$ MHz $< W_{\text{gap}} < 20$ MHz | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| NOTE: | The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | | | | + +**Table 6.7.3.5.2.2-2: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the sub-block or Inter RF Bandwidth gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| UTRA FDD | RRC (3.84 Mcps) | +| NOTE: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | + +For Category A, a UTRA AAS BS of Wide Area BS class, either the OTA CACLR limits in Table 6.7.3.5.2.2-1 or OTA ACLR absolute limit of -7 dBm/MHz shall apply, whichever is less stringent. + +For Category B, a UTRA AAS BS of Wide Area BS class, either the OTA CACLR limits in Table 6.7.3.5.2.2-1 or OTA ACLR absolute limit of -9 dBm/MHz shall apply, whichever is less stringent. + +For a UTRA AAS BS of Medium Range BS class, either the OTA CACLR limits in Table 6.7.3.5.2.2-1 or OTA ACLR absolute limit of -19 dBm/MHz shall apply, whichever is less stringent. + +For a UTRA AAS BS of Local Area BS class, either the OTA CACLR limits in Table 6.7.3.5.2.2-1 or OTA ACLR absolute limit of -26 dBm/MHz shall apply, whichever is less stringent. + +### 6.7.3.5.3 E-UTRA + +#### 6.7.3.5.3.1 OTA ACLR + +For operation in paired spectrum, the OTA ACLR shall be higher than the value specified in Table 6.7.3.5.3.1-1. + +**Table 6.7.3.5.3.1-1: OTA ACLR in paired spectrum** + +| Channel bandwidth of E-UTRA lowest/highest carrier transmitted BW_{Channel} (MHz) | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------------------|------------------------------------------------------| +| 1.4, 3.0, 5, 10, 15, 20 | $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44 dB | 43.8dB | +| | $2 \times BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 2.5$ MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 7.5$ MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA lowest/highest carrier transmitted on the assigned channel frequency. | | | | | | +| NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.014 [3] with a chip rate as defined in this table. | | | | | | + +For operation in unpaired spectrum, the measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.3.1-2. + +**Table 6.7.3.5.3.1-2: OTA ACLR in unpaired spectrum with synchronized operation** + +| Channel bandwidth of E-UTRA lowest/highest carrier transmitted $BW_{Channel}$ (MHz) | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| +| 1.4, 3.0 | $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44 dB | 43.8dB | +| | $2 \times BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 0.8$ MHz | 1.28 Mcps UTRA | RRc (1.28 Mcps) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 2.4$ MHz | 1.28 Mcps UTRA | RRc (1.28 Mcps) | 44 dB | 43.8dB | +| 5, 10, 15, 20 | $BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44 dB | 43.8dB | +| | $2 \times BW_{Channel}$ | E-UTRA of same BW | Square ( $BW_{Config}$ ) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 0.8$ MHz | 1.28 Mcps UTRA | RRc (1.28 Mcps) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 2.4$ MHz | 1.28 Mcps UTRA | RRc (1.28 Mcps) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 2.5$ MHz | 3.84 Mcps UTRA | RRc (3.84 Mcps) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 7.5$ MHz | 3.84 Mcps UTRA | RRc (3.84 Mcps) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 5$ MHz | 7.68 Mcps UTRA | RRc (7.68 Mcps) | 44 dB | 43.8dB | +| | $BW_{Channel}/2 + 15$ MHz | 7.68 Mcps UTRA | RRc (7.68 Mcps) | 44 dB | 43.8dB | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the channel bandwidth and transmission bandwidth configuration of the E-UTRA lowest/highest carrier transmitted on the assigned channel frequency. + +NOTE 2: The RRc filter shall be equivalent to the transmit pulse shape filter defined in TS 25.014 [3] with a chip rate as defined in this table. + +For operation in non-contiguous paired spectrum or multiple bands, the measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.3.1-3. + +**Table 6.7.3.5.3.1-3: OTA ACLR in non-contiguous paired spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{gap}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| +| $W_{gap} \geq 15$ MHz | 2.5 MHz | 3.84 Mcps UTRA | RRc (3.84 Mcps) | 44 dB | 43.8dB | +| $W_{gap} \geq 20$ MHz | 7.5 MHz | 3.84 Mcps UTRA | RRc (3.84 Mcps) | 44 dB | 43.8dB | +| NOTE: | The RRc filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | | | | + +For operation in non-contiguous unpaired spectrum or multiple bands, the measurement result shall not be less than the OTA ACLR limit specified in Table 6.7.3.5.3.1-4. + +**Table 6.7.3.5.3.1-4: OTA ACLR in non-contiguous unpaired spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{gap}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit for bands below 3GHz | OTA ACLR limit for bands between 3 and 4.2GHz | +|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| +| $W_{gap} \geq 15$ MHz | 2.5 MHz | 5 MHz E-UTRA | Square ( $BW_{Config}$ ) | 44 dB | 43.8dB | +| $W_{gap} \geq 20$ MHz | 7.5 MHz | 5 MHz E-UTRA | Square ( $BW_{Config}$ ) | 44 dB | 43.8dB | + +For Category A, an E-UTRA AAS BS of Wide Area BS class, either the OTA ACLR limits in Tables 6.7.3.5.3.1-1/2/3/4 or OTA ACLR absolute limit of -4 dBm/MHz shall apply, whichever is less stringent. + +For Category B, an E-UTRA AAS BS of Wide Area BS class, either the OTA ACLR limits in Tables 6.7.3.5.3.1-1/2/3/4 or OTA ACLR absolute limit of -6 dBm/MHz shall apply, whichever is less stringent. + +For an E-UTRA AAS BS of Medium Range BS class, either the OTA ACLR limits in Tables 6.7.3.5.3.1-1/2/3/4 or OTA ACLR absolute limit of -16 dBm/MHz shall apply, whichever is less stringent. + +For an E-UTRA AAS BS of Local Area BS class, either the OTA ACLR limits in Tables 6.7.3.5.3.1-1/2/3/4 or OTA ACLR absolute limit of -23 dBm/MHz shall apply, whichever is less stringent. + +#### 6.7.3.5.3.2 OTA Cumulative ACLR test requirement in non-contiguous spectrum + +The following test requirement applies for the sub-block or *Inter RF Bandwidth gap* sizes listed in Table 6.7.3.5.3.2-1, + +- Inside a sub-block gap within an operating band for a BS operating in non-contiguous spectrum. +- Inside an *Inter RF Bandwidth gap* for a multi-band capable AAS BS. + +The Cumulative Adjacent Channel Leakage power Ratio (CACLR) in a sub-block gap or *Inter RF Bandwidth gap* is the ratio of: + +- a) the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the sub-block gap or *Inter RF Bandwidth gap*; and +- b) the filtered mean power centred on a frequency channel adjacent to one of the respective sub-block edges or *Base Station RF Bandwidth edges*. + +The assumed filter for the adjacent channel frequency is defined in Tables 6.7.3.5.3.2-1 and 6.7.3.5.3.2-2. Filters on the assigned channels are defined in Table 6.7.3.5.3.2-3. + +For operation in non-contiguous spectrum or multiple bands, the CACLR for E-UTRA carriers located on either side of the sub-block gap or *Inter RF Bandwidth gap* shall not be less than the value specified in Tables 6.7.3.5.3.2-1 and 6.7.3.5.3.2-2. + +**Table 6.7.3.5.3.2-1: OTA CACLR in non-contiguous paired spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA CACLR limit for bands below 3GHz | OTA CACLR limit for bands between 3 and 4.2GHz | +|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------|------------------------------------------------| +| $5 \text{ MHz} \leq W_{\text{gap}} < 15 \text{ MHz}$ | 2.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| $10 \text{ MHz} < W_{\text{gap}} < 20 \text{ MHz}$ | 7.5 MHz | 3.84 Mcps UTRA | RRC (3.84 Mcps) | 44 dB | 43.8dB | +| NOTE: | The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [2], with a chip rate as defined in this table. | | | | | + +**Table 6.7.3.5.3.2-2: OTA CACLR in non-contiguous unpaired spectrum or multiple bands** + +| Sub-block or Inter RF Bandwidth gap size ( $W_{\text{gap}}$ ) where the limit applies | BS adjacent channel centre frequency offset below or above the sub-block edge or the Base Station RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA CACLR limit for bands below 3GHz | OTA CACLR limit for bands between 3 and 4.2GHz | +|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------|------------------------------------------------| +| $5 \text{ MHz} \leq W_{\text{gap}} < 15 \text{ MHz}$ | 2.5 MHz | 5 MHz E-UTRA carrier | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8dB | +| $10 \text{ MHz} < W_{\text{gap}} < 20 \text{ MHz}$ | 7.5 MHz | 5 MHz E-UTRA carrier | Square ( $BW_{\text{Config}}$ ) | 44 dB | 43.8dB | + +**Table 6.7.3.5.3.2-3: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the sub-block or Inter RF Bandwidth gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| E-UTRA | E-UTRA of same BW | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +For Category A, an E-UTRA AAS BS of Wide Area BS class, either the OTA CACLR limits in Tables 6.7.3.5.3.2-1/2 or OTA ACLR absolute limit of -4 dBm/MHz shall apply, whichever is less stringent. + +For Category B, an E-UTRA AAS BS of Wide Area BS class, either the OTA CACLR limits in Tables 6.7.3.5.3.2-1/2 or OTA ACLR absolute limit of -6 dBm/MHz shall apply, whichever is less stringent. + +For an E-UTRA AAS BS of Medium Range BS class, either the OTA CACLR limits in Tables 6.7.3.5.3.2-1/2 or OTA ACLR absolute limit of -16 dBm/MHz shall apply, whichever is less stringent. + +For an E-UTRA AAS BS of Local Area BS class, either the OTA CACLR limits in Tables 6.7.3.5.3.2-1/2 or OTA ACLR absolute limit of -23 dBm/MHz shall apply, whichever is less stringent. + +## 6.7.4 OTA Spectrum emission mask + +### 6.7.4.1 Definition and applicability + +This requirement is applicable for AAS BS in *single RAT UTRA operation* only. + +The spectrum emission mask minimum requirements are quoted as TRP unless otherwise stated. + +### 6.7.4.2 Minimum requirement + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.4.3. + +This requirement does not apply to *single RAT E-UTRA operation* or *MSR operation*. + +### 6.7.4.3 Test purpose + +This test measures the emissions of the AAS BS, close to the assigned channel bandwidth of the wanted signal, while the AAS BS is in operation. + +### 6.7.4.4 Method of test + +#### 6.7.4.4.1 Initial conditions + +##### 6.7.4.4.1.1 General test conditions + +Test environment: + +- normal; see annex G.2. + +RF channels to be tested for single carrier: + +- B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single-band operation; see clause 4.12.1; $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ in multi-band operation, see clause 4.12.1. + +#### 6.7.4.4.1.2 UTRA FDD + +For an AAS BS declared to be capable of single carrier operation only, set to transmit a signal according to TM1, in clause 4.12.2. + +For a multi-carrier capable AAS BS, set to transmit according to TM1 on all carriers configured using the applicable test configuration. + +#### 6.7.4.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in Annex F. An alternative method to measure TRP is to use a characterized and calibrated reverberation chamber. If so, follow steps 1, 3, 4, 5, 7 and 10. When calibrated and operated within the guidance of 3GPP TR 37.941 [38] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) The measurement devices characteristics shall be: + - a 30 kHz measurement bandwidth. + - Measurements with an offset from the carrier centre frequency between 2,515 MHz and 4.0 MHz shall use Measurements with an offset from the carrier centre frequency between 4.0 MHz and ( $f\_offset_{max} - 500$ kHz) shall use a 1 MHz measurement bandwidth. + - detection mode: true RMS voltage or true power averaging. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity, efficiency and avoiding e.g. carrier leakage, the resolution bandwidth may 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. + +- 4) For single carrier operation, set the AAS BS to transmit according to the applicable test configuration in clause 5 using the corresponding test model(s) in clause 4.12.2 at manufacturers declared *rated carrier TRP* ( $P_{rated,c,TRP}$ ). + +For an AAS BS declared to be capable of multi-carrier and/or CA operation use the applicable test signal configuration and corresponding power setting specified in clause 4.11. + +- 5) For UTRA FDD *multi-band RIB* or *RIB* operating in non-contiguous spectrum, the emission within the Inter RF Bandwidth or sub-block gap shall be measured using the specified measurement bandwidth from the closest *Base Station RF Bandwidth* or sub block edge. +- 6) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex F). +- 7) Sweep the centre frequency of the measurement filter in contiguous steps and measure emission power within the specified frequency ranges with the specified measurement bandwidth. +- 8) Repeat step 6-7 for all directions in the appropriated TRP measurement grid needed for $TRP_{Estimate}$ (see Annex F). +- 9) Calculate $TRP_{Estimate}$ using the measurements made in Step 7. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 10) For *multi-band RIB* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 6.7.4.5 Test Requirement + +### 6.7.4.5.1 UTRA FDD + +The measurement result shall not exceed the test requirements specified in Tables 6.7.4.5.1-1 to 6.7.4.5.1-11 for the appropriate $P_{\text{rated,c,TRP}}$ , where + +- $\Delta f$ is the separation between the carrier frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the carrier frequency and the centre of the measurement filter; +- $f_{\text{offsetmax}}$ is either 12.5 MHz or the offset to the UMTS Tx band edge as defined in clause 3.4.1 of TS 25.141 [10], whichever is the greater. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +Inside any *Inter RF Bandwidth gaps* with $W_{\text{gap}} < 2 \times \Delta f_{\text{OBUE}}$ for a *multi-band RIB*, emissions shall not exceed the cumulative sum of the *minimum requirements* specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *minimum requirements* for *Base Station RF Bandwidth edge* is specified in the tables below, where in this case: + +- $\Delta f$ is equal to 2.5 MHz plus the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the *Base Station RF Bandwidth edge*. +- $f_{\text{offset}}$ is equal to 2.5 MHz plus the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is either 12.5 MHz or the offset to the UMTS Tx band edge, whichever is the greater. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band RIB*, the operating band unwanted emission minimum requirements apply also in a supported operating band without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported operating band. In this case, no cumulative limit is applied in the *inter-band gap* between a supported *downlink operating band* with carrier(s) transmitted and a supported *downlink operating band* without any carrier transmitted and + +- In case the *inter-band gap* between a downlink band with carrier(s) transmitted and a downlink band without any carrier transmitted is less than $2 \times \Delta f_{\text{OBUE}}$ , $f_{\text{offsetmax}}$ shall be the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the outermost edges of the two *downlink operating bands* and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both downlink bands. +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{\text{max}}$ ), shall apply from $\Delta f_{\text{OBUE}}$ below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band* without any carrier transmitted. + +Inside any *sub-block gap* for a RIB operating in *non-contiguous spectrum*, emissions shall not exceed the cumulative sum of the *minimum requirements* specified for the adjacent sub blocks on each side of the *sub-block gap*. The *minimum requirement* for each sub block is specified in the tables below, where in this case: + +- $\Delta f$ is equal to 2.5 MHz plus the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f_{\text{offset}}$ is equal to 2.5 MHz plus the separation between the sub block edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter plus 2.5 MHz. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +**Table 6.7.4.5.1-1: Spectrum emission mask values, $P_{\text{rated,c,TRP}} \geq 49$ dBm for UTRA FDD bands $\leq 3$ GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -6.2 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | $-6.2 + 15 \cdot (f\_offset/\text{MHz} - 2.715) \text{ dBm}$ | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -18.2 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f < 7.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f\_offset < 8.0 \text{ MHz}$ | -5.2 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -5.2 dBm | 1 MHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation the test requirement within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission test requirement in clauses 6.7.6 shall be met. + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.7.4.5.1-2: Spectrum emission mask values, $P_{\text{rated,c,TRP}} \geq 49$ dBm for UTRA FDD bands > 3 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Test requirement (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|------------------------------------------------------------------------------|--------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f_{\text{offset}} < 2.715 \text{ MHz}$ | -6 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f_{\text{offset}} < 3.515 \text{ MHz}$ | $-6 + 15 \cdot (f_{\text{offset}}/\text{MHz} - 2.715) \text{ dBm}$ | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f_{\text{offset}} < 4.0 \text{ MHz}$ | -18 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f < 7.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f_{\text{offset}} < 8.0 \text{ MHz}$ | -5 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offsetmax}}$ | -5 dBm | 1 MHz | + +NOTE 1: For a *RIB* supporting non-contiguous spectrum operation the test requirement within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *test requirement* in clause 6.7.6 shall be met. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f_{\text{offset}}$ is continuous. + +NOTE 5: 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. + +**Table 6.7.4.5.1-3: Spectrum emission mask values, $45 \text{ dBm} \leq P_{\text{rated,c,TRP}} < 49 \text{ dBm}$ for UTRA FDD bands $\leq 3 \text{ GHz}$** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -6.2 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | $-6.2 + 15(f\_offset/\text{MHz} - 2.715) \text{ dBm}$ | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -18.2 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f < 7.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f\_offset < 8.0 \text{ MHz}$ | -5.2 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,TRP}} - 54.2 \text{ dB}$ | 1 MHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation the *test requirement* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *test requirement* in clauses 6.7.6 shall be met. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.7.4.5.1-4: Spectrum emission mask values, $45 \text{ dBm} \leq P_{\text{rated,c,TRP}} < 49 \text{ dBm}$ for UTRA FDD bands > 3 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -6 dBm | 30 kHz | +| $2.7 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | $-6 + 15(f\_offset/\text{MHz}-2.715)\text{dBm}$ | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -18 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f < 7.5 \text{ MHz}$ | $4.0 \text{ MHz} \leq f\_offset < 8.0 \text{ MHz}$ | -5 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,TRP}} - 54 \text{ dB}$ | 1 MHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation the *test requirement* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *test requirement* in clause 6.7.6 shall be met. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.7.4.5.1-5: Spectrum emission mask values, $37 \text{ dBm} \leq P_{\text{rated,c,TRP}} < 45 \text{ dBm}$ for UTRA FDD bands $\leq 3 \text{ GHz}$** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51.2 \text{ dB}$ | 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_{\text{rated,c,TRP}} - 51.2 - 15(f\_offset/\text{MHz} - 2.715) \text{ dB}$ | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 63.2 \text{ dB}$ | 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_{\text{rated,c,TRP}} - 50.2 \text{ dB}$ | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,TRP}} - 54.2 \text{ dB}$ | 1 MHz | + +NOTE 1: For a *R/B* supporting non-contiguous spectrum operation the *test requirement* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *test requirement* in clauses 6.7.6 shall be met. + +NOTE 2: For a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.7.4.5.1-6: Spectrum emission mask values, $37 \text{ dBm} \leq P_{\text{rated,c,TRP}} < 45 \text{ dBm}$ for UTRA FDD bands $> 3 \text{ GHz}$** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51 \text{ dB}$ | 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_{\text{rated,c,TRP}} - 51 - 15(f\_offset/\text{MHz} - 2.715) \text{ dB}$ | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 63 \text{ dB}$ | 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_{\text{rated,c,TRP}} - 50 \text{ dB}$ | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,TRP}} - 54 \text{ dB}$ | 1 MHz | + +NOTE 1: For a *R/B* supporting non-contiguous spectrum operation the *test requirement* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *test requirement* in clauses 6.7.6 shall be met. + +NOTE 2: For a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.7.4.5.1-7: Spectrum emission mask values, $P_{\text{rated,c,TRP}} < 37$ dBm for UTRA FDD bands $\leq 3$ GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -14.2 dBm | 30 kHz | +| $2.7 \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | $-14.2 \text{ dBm} - 15(f\_offset/\text{MHz} - 2.715) \text{ dB}$ | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -26.2 dBm | 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.2 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -17.2 dBm | 1 MHz | + +NOTE 1: For RIB supporting non-contiguous spectrum operation the *test requirement* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *test requirement* in clauses 6.7.6 shall be met. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +**Table 6.7.4.5.1-8: Spectrum emission mask values, $P_{\text{rated,c,TRP}} < 37$ dBm for UTRA FDD bands $> 3$ GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (notes 1 and 2) | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.7 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.715 \text{ MHz}$ | -14 dBm | 30 kHz | +| $2.7 \leq \Delta f < 3.5 \text{ MHz}$ | $2.715 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | $-14 \text{ dBm} - 15(f\_offset/\text{MHz} - 2.715) \text{ dB}$ | 30 kHz | +| (Note 4) | $3.515 \text{ MHz} \leq f\_offset < 4.0 \text{ MHz}$ | -26 dBm | 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 dBm | 1 MHz | +| $7.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $8.0 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -17 dBm | 1 MHz | + +NOTE 1: For a *RIB* supporting non-contiguous spectrum operation the *test requirement* within sub-block gaps within any operating band is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 12.5 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the spurious emission *test requirement* in clauses 6.7.6 shall be met. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: 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. + +For operation in band II, IV, V, X, XII, XIII, XIV, XXV and XXVI, the applicable additional requirement in tables 6.7.4.5.1-9 to 6.7.4.5.1-11 apply in addition to the test requirements in tables 6.7.4.5.1-1 to 6.7.4.5.1-8. + +**Table 6.7.4.5.1-9: Additional spectrum emission limits 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 5) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | -7.2 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $4.0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -5.2 dBm | 1 MHz | +| NOTE 5: 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. | | | | + +**Table 6.7.4.5.1-10: Additional spectrum emission limits for Bands V, XXVI** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 5) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 3.5 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 3.515 \text{ MHz}$ | -7.2 dBm | 30 kHz | +| $3.5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3.55 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -5.2 dBm | 100 kHz | +| NOTE 5: 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. | | | | + +**Table 6.7.4.5.1-11: Additional spectrum emission limits 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 5) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2.5 \text{ MHz} \leq \Delta f < 2.6 \text{ MHz}$ | $2.515 \text{ MHz} \leq f\_offset < 2.615 \text{ MHz}$ | -5.2 dBm | 30 kHz | +| $2.6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.65 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -5.2 dBm | 100 kHz | +| NOTE 5: 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. | | | | + +In certain regions the following test requirement may apply for protection of DTT. For a *RIB* operating in Band XX, the level of emissions in the band 470-790 MHz, measured in an 8 MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to Table 6.7.4.5.1-12, shall not exceed the maximum emission level TRP in Table 6.7.4.5.1-12. + +**Table 6.7.4.5.1-12: Emissions levels for protection of DTT** + +| Case | Measurement filter centre frequency | Condition on BS maximum aggregate EIRP / 10 MHz, $P_{\text{EIRP\_10MHz}}$ (NOTE) | Maximum Level $P_{\text{EIRP,N,MAX}}$ | Measurement Bandwidth | +|---------------------------------------------------------------------------------------------|--------------------------------------|----------------------------------------------------------------------------------|---------------------------------------|-----------------------| +| A: for DTT frequencies where broadcasting is protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{EIRP\_10 MHz}} \geq 59$ dBm | 1.8 dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{EIRP\_10 MHz}} < 59$ dBm | $P_{\text{EIRP\_10 MHz}} - 57.2$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{EIRP\_10 MHz}} < 36$ dBm | -21.2 dBm | 8 MHz | +| B: for DTT frequencies where broadcasting is subject to an intermediate level of protection | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{EIRP\_10 MHz}} \geq 59$ dBm | 11.8 dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{EIRP\_10 MHz}} < 59$ dBm | $P_{\text{EIRP\_10 MHz}} - 47.2$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{EIRP\_10 MHz}} < 36$ dBm | -11.2 dBm | 8 MHz | +| C: for DTT frequencies where broadcasting is not protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | N.A. | 23.8 dBm | 8 MHz | + +NOTE: $P_{\text{EIRP\_10 MHz}}$ (dBm) is defined by the expression $P_{\text{EIRP\_10 MHz}} = P_{10 \text{ MHz}} + G_{\text{ant}} + 6\text{dB}$ for UTRA and $P_{\text{EIRP\_10 MHz}} = P_{10 \text{ MHz}} + G_{\text{ant}} + 9\text{dB}$ for E-UTRA, where $G_{\text{ant}}$ is [17] dBi + +NOTE 1: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B1, TS 37.105 [6] indicates how the limit in Table 6.7.4.5.1-12 demonstrates compliance to the regional requirement + +In certain regions, the following test requirements may apply to a *RIB* operating in Band XXXII within 1452-1492 MHz. The level of unwanted emissions, measured on centre frequencies $f_{\text{offset}}$ with filter bandwidth, according to Table 6.7.4.5.1-13, shall not exceed the maximum TRP limits indicated in the table. + +**Table 6.7.4.5.1-13: Declared frequency band XXXII unwanted emission within 1452-1492 MHz** + +| Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Maximum level (dBm) | Measurement bandwidth | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------------------| +| 5 MHz | $P_{\text{EIRP}} - 17$ dBi + 7.8 dB | 5 MHz | +| 10 MHz | $P_{\text{EIRP}} - 17$ dBi + 7.8 dB | 5 MHz | +| $15 \text{ MHz} \leq f_{\text{offset}} \leq f_{\text{offset,max,B32}}$ | $P_{\text{EIRP}} - 17$ dBi + 7.8 dB | 5 MHz | +| NOTE: $f_{\text{offset,max,B32}}$ denotes the frequency difference between the lower channel carrier frequency and 1454.5 MHz, and the frequency difference between the upper channel carrier frequency and 1489.5 MHz for the set channel position. | | | + +NOTE 2: The regional requirement, included in CEPT ECC Decision (13)03 [xx], is defined in terms of EIRP per antenna, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B, TS 37.105 [6] indicates how the limit in Table 6.7.4.5.1-13 demonstrates compliance to the regional requirement. + +In certain regions, the following test requirement may apply to *RIB* operating in Band XXXII within 1452-1492 MHz for the protection of services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to Table 6.7.4.5.1-14, shall not exceed the maximum emission TRP limits in the table. This requirement applies in the frequency range 1429-1518 MHz even though part of the range falls in the spurious domain. + +**Table 6.7.4.5.1-14: Frequency band XXXII declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission level (dBm) | Measurement bandwidth | +|---------------------------------------------------------------------|-----------------------------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{\text{filter}} \leq 1448.5 \text{ MHz}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 7.8 \text{ dB}$ | 1 MHz | +| $F_{\text{filter}} = 1450.5 \text{ MHz}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 7.8 \text{ dB}$ | 3 MHz | +| $F_{\text{filter}} = 1493.5 \text{ MHz}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 7.8 \text{ dB}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{\text{filter}} \leq 1517.5 \text{ MHz}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 7.8 \text{ dB}$ | 1 MHz | + +NOTE 3: The regional requirement, included in CEPT ECC Decision (13)03 [19], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in annex B, TS 37.105 indicates how the limit in Table 6.7.4.5.1-14 demonstrates compliance to the regional requirement. + +## 6.7.5 OTA Operating band unwanted emission + +### 6.7.5.1 Definition and applicability + +Unless otherwise stated, for E-UTRA single band and MSR the operating band unwanted emission limits are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported *downlink operating band* to the lower *Base Station RF Bandwidth edge* located at $F_{\text{BW RF,low}}$ and from the upper *Base Station RF Bandwidth edge* located at $F_{\text{BW RF,high}}$ up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported *downlink operating band*. + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. + +For BS operating in bands n50, n51, n74, n75 and n76 additional emission limits that might be applicable outside OBUE frequency domain are specified in clause 6.7.5.5.4.6. + +### 6.7.5.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.5.2 + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.5.4. + +This requirement does not apply to *single RAT UTRA operation*. + +### 6.7.5.3 Test purpose + +This test measures the emissions of the AAS BS, close to the assigned channel bandwidth of the wanted signal, while the AAS BS is in operation. + +### 6.7.5.4 Method of test + +#### 6.7.5.4.1 Initial conditions + +Test environment: + +- normal; annex G.2. + +RF channels to be tested for single carrier: + +- B, M and T; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single-band operation; see clause 4.12.1; $B'_{\text{RFBW}}$ , $T'_{\text{RFBW}}$ and $B'_{\text{RFBW}}$ , $T'_{\text{RFBW}}$ in multi-band operation, see clause 4.12.1 + +#### 6.7.5.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in Annex F. An alternative method to measure TRP is to use a characterized and calibrated reverberation chamber. If so, follow steps 1, 3, 4, 6, 9 and 10. When calibrated and operated within the guidance of 3GPP TR 37.941 [38] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) The measurement devices characteristics shall be: + - detection mode: true RMS voltage or true power averaging. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 4) Set the AAS BS to transmit: + - a) For MSR: + - Set the AAS BS to transmit maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.12. + - b) For E-UTRA: + - AAS BS declared to be capable of single carrier operation only, set the AAS BS to transmit a signal according to E-TM1.1 (clause 4.12.2) at manufacturer's declared *rated carrier TRP* ( $P_{\text{rated,c,TRP}}$ ). + - For an AAS BS declared to be capable of multi-carrier and/or CA operation, set the set the AAS BS to transmit according to E-TM1.1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. +- 5) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex F). +- 6) Sweep the centre frequency of the measurement filter in contiguous steps and measure emission power within the specified frequency ranges with the specified measurement bandwidth. +- 7) Repeat step 6-7 for all directions in the appropriated TRP measurement grid needed for $\text{TRP}_{\text{Estimate}}$ (see annex F). +- 8) Calculate $\text{TRP}_{\text{Estimate}}$ using the measurements made in Step 7. +- 9) Repeat the test for the remaining test cases: + - a) For MSR with channel set-up according to clause 5 and clause 4.12.2. + - b) For E-UTRA with the channel set-up according to E-TM 1.2 + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 10) For *multi-band RIB* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.7.5.5 Test Requirement + +##### 6.7.5.5.1 General + +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. + +#### 6.7.5.5.2 MSR Band categories 1 and 3 + +For an AAS BS of Wide Area BS class operating in Band Category 1 or Band Category 3, the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for a Wide Area BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for an AAS BS of Wide Area BS class operating in multiple bands, it applies inside any *Inter RF Bandwidth gap*. + +For an AAS BS of Medium Range BS class operating in Band Category 1 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for a Medium Range BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for an AAS BS of Medium Range BS class operating in multiple bands, it applies inside any *Inter RF Bandwidth gap*. + +For an AAS BS of Local Area BS class operating in Band Category 1 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for a Local Area BS operating in non-contiguous spectrum, it applies inside any sub-block gap. In addition, for an AAS BS of Local Area BS class operating in multiple bands, it applies inside any *Inter RF Bandwidth gap*. + +Outside the *Base Station RF Bandwidth edges*, emissions shall not exceed the maximum levels specified in Tables 6.7.5.5.2-1 to 6.7.5.5.2-8 below, where: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is the offset to the frequency $\Delta f_{OBUE}$ MHz outside the downlink operating band. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band RIB*, inside any *Inter RF Bandwidth gaps* with $W_{gap} < 2 \times \Delta f_{OBUE}$ MHz, emissions shall not exceed the cumulative sum of the test requirements specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The minimum requirement for *Base Station RF Bandwidth edge* is specified in Tables 6.7.5.5.2-1 to 6.7.5.5.2-8, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *Inter RF Bandwidth gap* divided by two. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band RIB*, the operating band unwanted emission limits apply also in a supported operating band without any carriers transmitted, in the case where there are carriers transmitted in another operating band. In this case where there is no carrier transmitted in an operating band, no cumulative limits are applied in the *inter-band gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted and + +- In case the *Inter RF Bandwidth gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted is less than $2 \times \Delta f_{OBUE}$ MHz, $f\_offset_{max}$ shall be the offset to the frequency $\Delta f_{OBUE}$ MHz outside the outermost edges of the two supported downlink operating bands and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both supported downlink bands. +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{max}$ ), shall apply from $\Delta f_{OBUE}$ MHz below the lowest frequency, up to $\Delta f_{OBUE}$ MHz above the highest frequency of the supported downlink operating band without any carrier transmitted. + +Inside any sub-block gap for a *RIB* operating in non-contiguous spectrum, emissions shall not exceed the cumulative sum of the test requirements specified for the adjacent sub blocks on each side of the sub block gap. The minimum requirement for each sub block is specified in Tables 6.7.5.5.2-1 to 6.7.5.5.2-8, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge frequency. +- $f\_offset$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the sub block gap bandwidth divided by two. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +Applicability of Wide Area operating band unwanted emission requirements in tables 6.7.5.5.2-1/2, 6.7.5.5.2-2a and 6.7.5.5.2-2b is specified in table 6.7.5.5.2-0. + +Note: Option 1 and Option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [4] and TS 38.104 [36]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [2]. + +**Table 6.7.5.5.2-0: Applicability of operating band unwanted emission requirements for BC1 and BC3 Wide Area BS** + +| NR band operation | UTRA supported | Applicable requirement table | +|------------------------------------------------------------------------|----------------|------------------------------| +| None | Y/N | 6.7.5.5.2-1/2 (option 2) | +| In certain regions (NOTE 2), band 1, 7, 38, 65 | N | 6.7.5.5.2-1/2 (option 2) | +| Any | Y | 6.7.5.5.2-1/2 (option 2) | +| Any below 1 GHz | N | 6.7.5.5.2-2a (option 1) | +| Any above 1 GHz except for certain regions (NOTE 2), band 1, 7, 38, 65 | N | 6.7.5.5.2-2b/2c (option 1) | + +NOTE 1: Void +NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [16] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [4] and TS 38.104 [33] are applied. + +**Table 6.7.5.5.2-1: WA BS OBUE in BC1 and BC3 bands $\leq 3$ GHz - option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|----------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -3.2 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-3.2 - 15(f\_offset/\text{MHz} - 0.215) \text{ dBm}$ (Note 6) | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -15.2 dBm (Note 6) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{max}, 10.5 \text{ MHz})$ | -2.2 dBm (Note 6) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -6 dBm (NOTE 5, 6) | 1 MHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -6 dBm/MHz (for MSR *multi-band TAB connector* supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ ). + +NOTE 2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{OBUE} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{max} < 10 \text{ MHz}$ . + +NOTE 6: For MSR *multi-band TAB connector* supporting multi-band operation, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands $< 1 \text{ GHz}$ . + +Table 6.7.5.5.2-2: WA BS OBUE in BC1 and BC3 bands > 3 GHz - option 2 + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -3 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-3-15(f\_offset/\text{MHz}-0.215)\text{dBm}$ | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -15 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -2 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (NOTE 5) | 1 MHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be -6 dBm/MHz. + +NOTE 2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +Table 6.7.5.5.2-2a: WA BS OBUE in BC1 and BC3 bands ≤ 1 GHz - option 1 + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $3.8 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05)\text{dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm (Note 5) | 100 kHz | + +NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -7dBm/100 kHz. + +NOTE 2: For AAS BS supporting multi-band operation with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.7.5.5.2-2b: WA BS OBUE in BC1 and BC3 bands > 3 GHz - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $4 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05)\text{dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (Note 5) | 1 MHz | +| NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -6dBm/1 MHz. | | | | +| NOTE 2: For AAS BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. | | | | + +**Table 6.7.5.5.2-2c: WA BS OBUE in BC1 and BC3 bands > 1GHz and $\leq 3 \text{ GHz}$ - option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $3.8 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05)\text{dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (Note 5) | 1 MHz | +| NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -6dBm/1 MHz. | | | | +| NOTE 2: For AAS BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. | | | | + +**Table 6.7.5.5.2-3: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm and not supporting NR; or BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm supporting NR and UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 56.2 \text{ dB} - (5/3) \cdot (f\_offset - 0,015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51.2 \text{ dB} - 15 \cdot (f\_offset - 0,015) \text{ dB}$ | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 63.2 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.1 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 50.2 \text{ dB}$ | 1 MHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.1 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{rated,c,TRP}} - 50.2 \text{ dB}, -4.2 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\text{max}}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\text{max}}, 10.5 \text{ MHz})$ | $P_{\text{rated,c,TRP}} - 54.2 \text{ dB}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $P_{\text{rated,c,TRP}} - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be $(P_{\text{rated,c,TRP}} - 56 \text{ dB})/\text{MHz}$ . + +NOTE 2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.2-3a: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm BS, supporting NR and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51.2 \text{ dB} - (7/5) \cdot (f\_offset - 0,05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,TRP}} - 58.2 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$ (Note 5) | 100 kHz | + +NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For AAS BS supporting multi-band operation with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.7.5.5.2-4: Medium Range BS operating band unwanted emission mask (UEM) in BC1 bands > 3 GHz applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm and not supporting NR; or BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm supporting NR and UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 56 \text{ dB} - (5/3) \cdot (f\_offset - 0,015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51 \text{ dB} - 15 \cdot (f\_offset - 0,015) \text{ dB}$ | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 63 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.1 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 50 \text{ dB}$ | 1 MHz | +| $2.6 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.1 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{rated,c,TRP}} - 50 \text{ dB}, -4 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | $P_{\text{rated,c,TRP}} - 54 \text{ dB}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P_{\text{rated,c,TRP}} - 56 \text{ dB}$ | 1 MHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be $(P_{\text{rated,c,TRP}} - 56 \text{ dB})/\text{MHz}$ . + +NOTE 2: For MSR multi-band RIB with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.2-4a: MR BS OBUE in BC1 bands > 3 GHz applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm BS, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51 \text{ dB} - 7/5 \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,c,TRP}} - 58 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$ (Note 5) | 100 kHz | + +NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For AAS BS supporting multi-band operation with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.7.5.5.2-5: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm and not supporting NR; or BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm supporting NR and UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-16.2 - 5/3(f\_offset/\text{MHz} - 0.015) \text{ dBm}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-11.2 - 15(f\_offset/\text{MHz} - 0.015) \text{ dBm}$ | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -23.2 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -10.2 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -14.2 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16dBm (Note 5) | 1 MHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be -16 dBm/MHz. + +NOTE 2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.2-5a: MR BS OBUE in BC1 bands $\leq 3$ GHz applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-11.2 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -18.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -20 dBm (Note 8) | 100 kHz | + +NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -20dBm/100 kHz. + +NOTE 2: For AAS BS supporting multi-band operation with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.7.5.5.2-6: MR BS OBUE in BC1 bands > 3 GHz applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm and not supporting NR; or BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm supporting NR and UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-16 - 5/3(f\_offset/\text{MHz} - 0.015) \text{ dBm}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-11 - 15(f\_offset/\text{MHz} - 0.015) \text{ dBm}$ | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -23 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -10 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -14 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16dBm (Note 5) | 1 MHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be -16 dBm/MHz. + +NOTE 2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 3: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.2-6a: MR BS OBUE in BC1 bands > 3 GHz applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-11 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -18 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -20 dBm (Note 5) | 100 kHz | + +NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -20dBm/100 kHz. + +NOTE 2: For AAS BS supporting multi-band operation with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +**Table 6.7.5.5.2-7: LA BS OBUE in BC1 bands $\leq 3 \text{ GHz}$** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-19.2 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -26.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm (Note 5) | 100 kHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be -28 dBm/100 kHz. + +NOTE 2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: Void. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.2-8: LA BS OBUE in BC1 bands > 3 GHz** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-19 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -26 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm (Note 5) | 100 kHz | + +NOTE 1: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be -28 dBm/100 kHz. + +NOTE 2: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: Void. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +### 6.7.5.5.3 MSR Band Category 2 + +For a *RIB* operating in Band Category 2 the requirement applies outside the *Base Station RF Bandwidth edges*. In addition, for a *RIB* operating in non-contiguous spectrum, it applies inside any sub-block gap. + +Outside the *Base Station RF Bandwidth edges*, emissions shall not exceed the maximum levels specified in Tables 6.7.5.5.3-1 to 6.7.5.5.3-8, where: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{\max}$ is the offset to the frequency $\Delta f_{\text{OBUE}} \text{ MHz}$ outside the downlink operating band. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band RIB*, inside any *Inter RF Bandwidth gaps* with $W_{\text{gap}} < 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ , emissions shall not exceed the cumulative sum of the test requirements specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *minimum requirement* for *Base Station RF Bandwidth edge* is specified in Tables 6.7.5.5.3-1 to 6.7.5.5.3-8, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{\max}$ is equal to the *Inter RF Bandwidth gap* divided by two. +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band RIB* and where there is no carrier transmitted in an operating band, no cumulative limits are applied in the *inter-band gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted and + +- In case the *inter-band gap* between a supported downlink band with carrier(s) transmitted and a supported downlink band without any carrier transmitted less than is $2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ , $f\_offset_{\max}$ shall be the offset to the frequency $\Delta f_{\text{OBUE}} \text{ MHz}$ outside the outermost edges of the two supported downlink operating bands and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both supported downlink bands. + +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{max}$ ), shall apply from $\Delta f_{OBUE}$ MHz below the lowest frequency, up to $\Delta f_{OBUE}$ MHz above the highest frequency of the supported downlink operating band without any carrier transmitted. + +Inside any sub-block gap for a *RIB* operating in non-contiguous spectrum, emissions shall not exceed the cumulative sum of the test requirement specified for the adjacent sub blocks on each side of the sub block gap. The *minimum requirement* for each sub block is specified in Tables 6.7.5.5.3-1 to 6.7.5.5.3-8, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f\_offset$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the sub block gap bandwidth divided by two. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +Applicability of Wide Area operating band unwanted emission requirements in tables 6.7.5.5.3-1, 6.7.5.5.3-2a and 6.7.5.5.3-2b is specified in table 6.7.5.5.3-0. + +Note: Option 1 and Option 2 correspond to the Category B option 1/2 operating band unwanted emissions defined in the E-UTRA and NR specifications TS 36.104 [4] and TS 38.104 [36]. Option 2 also corresponds to the UTRA spectrum emission mask as defined in TS 25.104 [2]. + +**Table 6.7.5.5.3-0: Applicability of operating band unwanted emission requirements for BC2 Wide Area BS** + +| NR band operation | UTRA supported | Applicable requirement table | +|-----------------------------------------------------------------|----------------|------------------------------| +| None | Y/N | 6.7.5.5.3-1 (option 2) | +| In certain regions (NOTE 2), band 3, 8 | N | 6.7.5.5.3-1 (option 2) | +| Any | Y | 6.7.5.5.3-1 (option 2) | +| Any below 1 GHz except for, in certain regions (NOTE 2), band 8 | N | 6.7.5.5.3-2a (option 1) | +| Any above 1 GHz except for certain regions (NOTE 2), band 3 | N | 6.7.5.5.3-2b (option 1) | + +NOTE 1: Void +NOTE 2: Applicable only for operation in regions where Category B limits as defined in ITU-R Recommendation SM.329 [16] are used for which category B option 2 operating band unwanted emissions requirements as defined in TS 36.104 [4] and TS 38.104 [33] are applied. + +**Table 6.7.5.5.3-1: WA BS OBUE in BC2 bands - option 2** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 2 and 3) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -3.2 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-3.2 - 15(f\_offset/\text{MHz} - 0.215) \text{ dBm}$ (Note 11) | 30 kHz | +| (Note 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -15.2 dBm (Note 11) | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $1.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -2.2 dBm (Note 11) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (Note 10, 11) | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.7.5.5.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *minimum requirement* within sub-block gaps shall be -6 dBm/MHz (for MSR *multi-band TAB connector*, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands <1GHz). + +NOTE 3: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz operation the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 8: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 10: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +NOTE 11: For MSR *multi-band TAB connector*, either this limit or -16dBm/100kHz with correspondingly adjusted $f\_offset$ shall apply for this frequency offset range for operating bands < 1 GHz. + +**Table 6.7.5.5.3-2: WA BS OBUE in BC2 bands applicable for: BS operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 2, 3 and 4) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $\text{Max}(15.8 \text{ dBm} - 60(f\_offset/\text{MHz} - 0.015), -3.2 \text{ dBm})$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $\text{Max}(12.8 \text{ dBm} - 160(f\_offset/\text{MHz} - 0.065), -3.2 \text{ dBm})$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 2: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 4: Void. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ + +**Table 6.7.5.5.3-2a: WA BS OBUE in BC2 bands $\leq 1$ GHz – option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $3.8 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05)\text{dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm (Note 10) | 100 kHz | + +NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -7dBm/100 kHz. + +NOTE 2: For AAS BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.7.5.5.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 4: Void. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.3-2b: WA BS OBUE in BC2 bands $> 1$ GHz – option 1** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $3.8 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05)\text{dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm (Note 5) | 1 MHz | + +NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band, the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -6dBm/1 MHz. + +NOTE 2: For AAS BS supporting multi-band operation with Inter RF Bandwidth gap $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the Inter RF Bandwidth gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or RF Bandwidth on each side of the Inter RF Bandwidth gap, where the contribution from the far-end sub-block or RF Bandwidth shall be scaled according to the measurement bandwidth of the near-end sub-block or RF Bandwidth. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the Base Station RF Bandwidth edge or the sub-block edge, the limits in Table 6.7.5.5.3-2 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 4: Void. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.3-3: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm and not supporting NR; or BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm supporting NR with UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 2 and 3) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 56.2 \text{ dB} - (5/3) \cdot (f\_offset - 0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51.2 \text{ dB} - 15 \cdot (f\_offset - 0.215) \text{ dB}$ | 30 kHz | +| (Note 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 63.2 \text{ dB}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 50.2 \text{ dB}$ | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $3.3 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | $\min(P_{\text{rated,c,TRP}} - 50.2 \text{ dB}, -4.2 \text{ dBm})$ | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | $P_{\text{rated,c,TRP}} - 54.2 \text{ dB}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P_{\text{rated,c,TRP}} - 56 \text{ dB}$ (Note 10) | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in Table 6.7.5.5.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be $(P_{\text{rated,c,TRP}} - 56 \text{ dB})/\text{MHz}$ . + +NOTE 3: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 8: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 10: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ + +**Table 6.7.5.5.3-3a: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51.2 \text{ dB} - 7.5 \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,c,TRP}} - 58.2 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$ (Note 5) | 100 kHz | + +NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For AAS BS supporting multi-band operation with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in Table 6.7.5.5.3-5 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 4: Void. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.3-4: Medium Range BS operating band unwanted emission mask (UEM) in BC2 bands applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm and not supporting NR; or BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm supporting NR with UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 2 and 3) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.6 \text{ MHz}$ (Note 1) | $0.015 \text{ MHz} \leq f\_offset < 0.615 \text{ MHz}$ | $-16.2 \text{ dBm} - 5/3(f\_offset/\text{MHz} - 0.015) \text{ dB}$ | 30 kHz | +| $0.6 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.615 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-11.2 \text{ dBm} - 15(f\_offset/\text{MHz} - 0.215) \text{ dB}$ | 30 kHz | +| (Note 8) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -23.2 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 5 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 5.5 \text{ MHz}$ | -10.2 dBm | 1 MHz | +| $5 \text{ MHz} \leq \Delta f \leq \min(\Delta f_{\max}, 10 \text{ MHz})$ | $5.5 \text{ MHz} \leq f\_offset < \min(f\_offset_{\max}, 10.5 \text{ MHz})$ | -14.2 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 10) | 1 MHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.7.5.5.3-6 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 2: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be -16 dBm/MHz. + +NOTE 3: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *RF Bandwidth*. + +NOTE 8: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 10: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ + +**Table 6.7.5.5.3-4a: MR BS OBUE in BC2 bands applicable for: BS maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm, supporting NR, and not supporting UTRA** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 1, 2) | Measurement bandwidth (Note 7) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-11.2 \text{ dBm} - 7/5(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -18.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -20 dBm (Note 5) | 100 kHz | + +NOTE 1: For AAS BS supporting non-contiguous spectrum operation within any operating band the minimum requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -20dBm/100 kHz. + +NOTE 2: For AAS BS supporting multi-band operation with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ the minimum requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in Table 6.7.5.5.3-6 apply for $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ . + +NOTE 4: Void. + +NOTE 5: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.3-5: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm and operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 2 and 3) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 36.2 - 60(f\_offset - 0.015)$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 39.2 - 160(f\_offset - 0.065)$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 2: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ + +**Table 6.7.5.5.3-6: MR BS OBUE in BC2 bands applicable for: BS with maximum output power $P_{\text{rated,c,TRP}} \leq 40$ dBm and operating E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 2, 3 and 4) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $\text{Max}(3.8 - 60(f\_offset/\text{MHz} - 0.015), -16.2) \text{ dBm}$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $\text{Max}(0.8 - 160(f\_offset/\text{MHz} - 0.065), -16.2) \text{ dBm}$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 2: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 4: Void. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ + +**Table 6.7.5.5.3-7: LA BS OBUE in BC2 bands** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 2 and 3) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ (Note 1) | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-19.2-7/5(f\_offset/\text{MHz}-0.05) \text{ dBm}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -26.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm (Note 10) | 100 kHz | + +NOTE 1: For operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge, the limits in table 6.6.5.5.3-8 apply for $0 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ . + +NOTE 2: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the *test requirement* within sub-block gaps shall be -28 dBm/100 kHz. + +NOTE 3: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ + +**Table 6.7.5.5.3-8: LA BS OBUE for operation in BC2 bands applicable for: BS operating with E-UTRA 1.4 or 3 MHz carriers adjacent to the Base Station RF Bandwidth edge or the sub-block edge** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 2, 3 and 4) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $\text{Max}(-3.2 \text{ dBm} - 60(f\_offset/\text{MHz} - 0.015) \text{ dB}, -24.2 \text{ dBm})$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.16 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.175 \text{ MHz}$ | $\text{max}(-6.2 \text{ dBm} - 160(f\_offset/\text{MHz} - 0.065) \text{ dB}, -24.2 \text{ dBm})$ | 30 kHz | + +NOTE 1: The limits in this table only apply for operation with an E-UTRA 1.4 or 3 MHz carrier adjacent to the *Base Station RF Bandwidth edge* or the sub-block edge. + +NOTE 2: For MSR RIB supporting non-contiguous spectrum operation within any operating band the *test requirement* within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. + +NOTE 3: For MSR *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the *test requirement* within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the *Inter RF Bandwidth gap*. + +NOTE 4: Void. + +NOTE 8: Void. + +NOTE 10: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ + +NOTE 9: As a general rule for the requirements in the present clause, 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 may 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. + +#### 6.7.5.5.4 MSR Additional requirements + +##### 6.7.5.5.4.1 Limits in FCC Title 47 + +In addition to the requirements in clauses 6.7.5.5.2 and 6.7.5.5.3, the AAS BSW may have to comply with the applicable emission limits established by FCC Title 47 [18], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +#### 6.7.5.5.4.2 Unsynchronized operation for BC3 + +In certain regions, the following requirements may apply to a TDD AAS BS operating in BC3 in the same geographic area and in the same operating band as another TDD system without synchronisation. For this case the emissions shall not exceed -52 dBm/MHz in each supported downlink operating band except in: + +- The frequency range from 10 MHz below the lower *Base Station RF Bandwidth edge* to the frequency 10 MHz above the upper *Base Station RF Bandwidth edge* of each supported band. + +NOTE 1: Local or regional regulations may specify another excluded frequency range, which may include frequencies where synchronised TDD systems operate. + +NOTE 2: TDD Base Stations that are synchronized and operating in BC3 can transmit without these additional co-existence requirements. + +#### 6.7.5.5.4.3 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For an AAS BS operating in Band 20/n20, the level of emissions in the band 470-790 MHz, measured in an 8 MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to table 6.7.5.5.4.3-1, shall not exceed the maximum emission level TRP level shown in the table. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 6.7.5.5.4.3-1: Declared emissions levels for protection of DTT** + +| Case | Measurement filter centre frequency | Condition on BS maximum aggregate TRP / 10 MHz, $P_{\text{TRP\_10MHz}}$ (NOTE) | Maximum Level $P_{\text{TRP,N,MAX}}$ | Measurement Bandwidth | +|---------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------------------------------------|--------------------------------------|-----------------------| +| A: for DTT frequencies where broadcasting is protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10 MHz}} \geq 59$ dBm | 1.8dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{TRP\_10 MHz}} < 59$ dBm | $P_{\text{TRP\_10 MHz}} - 57.2$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10 MHz}} < 36$ dBm | -21.2dBm | 8 MHz | +| B: for DTT frequencies where broadcasting is subject to an intermediate level of protection | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10 MHz}} \geq 59$ dBm | 11.8 dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{TRP\_10 MHz}} < 59$ dBm | $P_{\text{TRP\_10 MHz}} - 47.2$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10 MHz}} < 36$ dBm | -11.2dBm | 8 MHz | +| C: for DTT frequencies where broadcasting is not protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | N.A. | 23.8 dBm | 8 MHz | + +NOTE: $P_{\text{TRP\_10 MHz}}$ (dBm) is defined by the expression $P_{\text{TRP\_10 MHz}} = P_{10 \text{ MHz}} + G_{\text{ant}} + 6\text{dB}$ for UTRA and $P_{\text{TRP\_10 MHz}} = P_{10 \text{ MHz}} + G_{\text{ant}} + 9\text{dB}$ for E-UTRA, where $G_{\text{ant}}$ is 17 dBi + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions and the deployment (including antenna gain and feeder loss). The method outlined in annex B1, TS 37.105 [6] indicates how the limit in Table 6.7.5.5.4.3-1 demonstrates compliance to the regional requirement. + +#### 6.7.5.5.4.4 Co-existence with RNSS/GPS services in North America + +In regions where FCC regulation applies, requirements for protection of GPS according to FCC Order DA 20-48 applies for operation in Band 24. The following normative requirement covers the base station, to be used together with other information about the site installation to verify compliance with the requirement in FCC Order DA 20-48. The + +requirement applies to BS operating in Band 24 to ensure that appropriate interference protection is provided to the GPS. This requirement applies in the frequency range 1541-1650 MHz even though part of the range falls in the spurious domain. + +The level of emissions in the 1541 - 1650 MHz band, measured in measurement bandwidth according to table 6.7.5.5.4.4-1 shall not exceed the maximum TRP limits indicated in the table. + +**Table 6.7.5.5.4.4-1: Emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range (MHz) | Emission level (dBW)
(Measurement bandwidth = 1 MHz) | Emission level (dBW) of discrete emissions of less than 700 Hz bandwidth
(Measurement bandwidth = 1 kHz) | Emission level (dBW) of discrete emissions of less than 2 kHz bandwidth
(Measurement bandwidth = 1 kHz) | +|----------------|-----------------------|---------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------| +| 24 | 1541 - 1559 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | +| | 1559 - 1610 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | +| | 1610 - 1650 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | + +NOTE: The regional requirements, included in FCC Order DA 20-48 are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in TS 37.105 [6] annex B1 indicates how the limit in table 6.7.5.5.4.4-1 demonstrates compliance to the regional requirement in DA 20-48. $P_{\text{EIRP}}$ values in table 6.7.5.5.4.4-1 are the effective isotropic power (or radiated power spectral density) set in the FCC Order DA 20-48 for the specified frequency ranges and bandwidths. + +#### 6.7.5.5.4.5 Void + +**Table 6.7.5.5.4.5-1: Void** + +#### 6.7.5.5.4.6 Additional band 32, 50, 51, 74, 75 and 76 unwanted emissions + +In certain regions, the following requirements may apply to BS operating in Band 32 within 1452-1492 MHz, in Band 75 within 1432-1517 MHz and in Band 76 within 1427-1432 MHz. The maximum level of unwanted emissions, measured as EIRP, on centre frequencies $f_{\text{offset}}$ with filter bandwidth, according to table 6.7.5.5.4.6-1, shall not exceed the EIRP limits indicated in the table. + +For Band 32, this requirement applies in the frequency range 1452-1492 MHz when non-Mobile/Fixed Communications Network (MFCN) services are deployed in adjacent frequency ranges, while it applies also within 1427-1452 MHz and/or 1492-1517 MHz when MFCN services are deployed in such frequency ranges, even though part of the ranges falls in the spurious domain. For Band 75, this requirement applies in the frequency range 1427-1517 MHz. For Band 76, this requirement applies in the frequency range 1432-1517 MHz even though part of the range falls in the spurious domain. + +**Table 6.7.5.5.4.6-1: Unwanted emission limits within 1427-1517 MHz** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | EIRP limit [dBm] | Measurement bandwidth | +|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| 2.5 MHz | 16.3 | 5 MHz | +| 7.5 MHz | 11 | 5 MHz | +| $12.5 \text{ MHz} \leq f\_offset \leq f\_offset_{max}$ | 9 | 5 MHz | +| NOTE: | For Band 32, when non-MFCN services are deployed in the adjacent bands, $f\_offset_{max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1454.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1489.5 MHz for the set channel position. For Band 32, when MFCN services are deployed in the adjacent frequencies, Band 75 and Band 76, $f\_offset_{max}$ denotes the frequency difference between the lower Base Station RF Bandwidth edge and 1429.5 MHz, and the frequency difference between the upper Base Station RF Bandwidth edge and 1514.5 MHz for the set channel position. | | + +In certain regions, the following requirement may apply to BS operating in Band 32 within 1452-1492 MHz for the protection of non-MFCN services in spectrum adjacent to the frequency range 1452-1492 MHz. The maximum level of emissions, measured as EIRP, on centre frequencies $F_{filter}$ with filter bandwidth according to Table 6.7.5.5.4.6-2, shall not exceed the EIRP limits indicated in the table. This requirement applies in the frequency range 1429-1518 MHz even though part of the range falls in the spurious domain. + +**Table 6.7.5.5.4.6-2: Unwanted emission emission limits outside 1452-1492 MHz** + +| Filter centre frequency, $F_{filter}$ | EIRP limit [dBm] | Measurement bandwidth | +|--------------------------------------------------------------|------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{filter} \leq 1448.5 \text{ MHz}$ | -20 | 1 MHz | +| $F_{filter} = 1450.5 \text{ MHz}$ | 14 | 3 MHz | +| $F_{filter} = 1493.5 \text{ MHz}$ | 14 | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{filter} \leq 1517.5 \text{ MHz}$ | -20 | 1 MHz | + +In certain regions, the following requirement may apply to BS operating in Band 50 and Band 75 within 1492-1517 MHz and in Band 74 within 1492-1518 MHz. The maximum level of emissions, measured as EIRP, on centre frequencies $F_{filter}$ with filter bandwidth according to table 6.7.5.5.4.6-3, shall not exceed the EIRP limits indicated in the table. + +**Table 6.7.5.5.4.6-3: Operating band 50, 74 and 75 emission test limits above 1518 MHz** + +| Filter centre frequency, $F_{filter}$ | EIRP limit [dBm] | Measurement bandwidth | +|--------------------------------------------------------------|------------------|-----------------------| +| $1518.5 \text{ MHz} \leq F_{filter} \leq 1519.5 \text{ MHz}$ | -0.8 | 1 MHz | +| $1520.5 \text{ MHz} \leq F_{filter} \leq 1558.5 \text{ MHz}$ | -30 | 1 MHz | + +In certain regions, the following requirement may apply to E-UTRA BS operating in Band 50 and Band 75 within 1432-1452 MHz, and in Band 51 and Band 76. Emissions shall not exceed the test level specified in table 6.7.5.5.4.6-4. + +**Table 6.7.5.5.4.6-4: Additional unwanted emission limits for BS operating in Band 50 and 75 within 1432-1452 MHz, and in Band 51 and 76** + +| Filter centre frequency, $F_{filter}$ | Maximum Level [dBm] | Measurement Bandwidth | +|---------------------------------------|---------------------|-----------------------| +| $F_{filter} = 1413.5 \text{ MHz}$ | -42 | 27 MHz | + +#### 6.7.5.5.4.7 Additional requirements for band 45 + +In certain regions the following requirement may apply to E-UTRA BS operating in Band 45. Emissions shall not exceed the maximum levels specified in table 6.7.5.5.4.7-1. + +**Table 6.7.5.5.4.7-1: Emissions limits for protection of adjacent band services** + +| Operating Band | Filter centre frequency, $F_{\text{filter}}$ | Maximum Level [dBm] | Measurement Bandwidth | +|----------------|---------------------------------------------------------------------|---------------------|-----------------------| +| 45 | $F_{\text{filter}} = 1467.5$ | -11 | 1 MHz | +| | $F_{\text{filter}} = 1468.5$ | -14 | 1 MHz | +| | $F_{\text{filter}} = 1469.5$ | -17 | 1 MHz | +| | $F_{\text{filter}} = 1470.5$ | -24 | 1 MHz | +| | $F_{\text{filter}} = 1471.5$ | -31 | 1 MHz | +| | $1472.5 \text{ MHz} \leq F_{\text{filter}} \leq 1491.5 \text{ MHz}$ | -38 | 1 MHz | + +#### 6.7.5.5.4.8 Additional requirements for band 48 + +The following requirement may apply to BS operating in Band 48 in certain regions. Emissions shall not exceed the maximum levels specified in table 6.7.5.5.4.8-1. + +**Table 6.7.5.5.4.8-1: Additional operating band unwanted emission limits for Band 48** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|----------------------------------------------------------------------|------------------|-----------------------| +| All | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -4 dBm | 1 MHz | + +#### 6.7.5.5.5 E-UTRA + +##### 6.7.5.5.5.1 General + +The measurement results in clause 6.7.5.4 shall not exceed the maximum levels specified in the tables below, where: + +- $\Delta f$ is the separation between the channel edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the channel edge frequency and the centre of the measuring filter. +- $f\_offset_{\text{max}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ MHz outside the downlink operating band. +- $\Delta f_{\text{max}}$ is equal to $f\_offset_{\text{max}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band RIB*, inside any *Inter RF Bandwidth gaps* with $W_{\text{gap}} < 2 \times \Delta f_{\text{OBUE}}$ MHz, emissions shall not exceed the cumulative sum of the test requirements specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The test requirement for *Base Station RF Bandwidth edge* is specified in Tables 6.7.5.5.5.2-1 to 6.7.5.5.5.2-9, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the *Base Station RF Bandwidth edge*. +- $f\_offset$ is the separation between the *Base Station RF Bandwidth edge* frequency and the centre of the measuring filter. +- $f\_offset_{\text{max}}$ is equal to the *Inter RF Bandwidth gap* minus half of the bandwidth of the measuring filter. +- $\Delta f_{\text{max}}$ is equal to $f\_offset_{\text{max}}$ minus half of the bandwidth of the measuring filter. + +For *multi-band RIB*, the operating band unwanted emission limits apply also in a supported operating band without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported operating band. In this case, no cumulative limit is applied in the *inter-band gap* between a supported downlink operating band with carrier(s) transmitted and a supported downlink operating band without any carrier transmitted and: + +- In case the *inter-band gap* between a supported downlink operating band with carrier(s) transmitted and a supported downlink operating band without any carrier transmitted is less than $2 \times \Delta f_{\text{OBUE}}$ MHz, $f\_offset_{\text{max}}$ shall be the offset to the frequency $\Delta f_{\text{OBUE}}$ MHz outside the outermost edges of the two supported downlink operating + +bands and the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both downlink bands. + +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{\max}$ ), shall apply from $\Delta f_{\text{OBUE}}$ MHz below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ MHz above the highest frequency of the supported downlink operating band without any carrier transmitted. + +For a multicarrier E-UTRA TAB connector or a RIB configured for intra-band contiguous or non-contiguous carrier aggregation the definitions above apply to the lower edge of the carrier transmitted at the lowest carrier frequency and the upper edge of the carrier transmitted at the highest carrier frequency within a specified frequency band. + +In addition inside any sub-block gap for a *RIB* operating in non-contiguous spectrum, measurement results shall not exceed the cumulative sum of the test requirements specified for the adjacent sub blocks on each side of the sub block gap. The minimum requirement for each sub block is specified in Tables 6.7.5.5.2-1 to 6.7.5.5.2-9, where in this case: + +- $\Delta f$ is the separation between the sub block edge frequency and the nominal -3 dB point of the measuring filter closest to the sub block edge. +- $f_{\text{offset}}$ is the separation between the sub block edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is equal to the sub block gap bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{\max}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +#### 6.7.5.5.2 Wide Area BS (Category A) + +For E-UTRA *RIB* operating in Bands 5, 6, 8, 12, 13, 14, 17, 18, 19, 26, 27, 28, 29, 31, 44, 68, 71, 72, 73, 85, 106 emissions shall not exceed the maximum levels specified in Tables 6.7.5.5.2-1 to 6.7.5.5.2-3. + +**Table 6.7.5.5.2-1: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f_{\text{offset}} < 1.45 \text{ MHz}$ | $9.8 \text{ dBm} - 10/1.4(f_{\text{offset}}/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f_{\text{offset}} < 2.85 \text{ MHz}$ | -0.2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $2.85 \text{ MHz} \leq f_{\text{offset}} < \min(10.05 \text{ MHz}, f_{\text{offsetmax}})$ | -2.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offsetmax}}$ | -4 dBm (Note 8) | 100 kHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -4 dBm/100 kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.2-2: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $5.8 \text{ dBm} - 10/3(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -4.2 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -2.2 dBm (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (Note 8) | 100 kHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -4 dBm/100 kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.2-3: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $3.8 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (NOTE 8) | 100 kHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -4 dBm/100 kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For E-UTRA RIB operating in Bands 1, 2, 3, 4, 7, 9, 10, 11, 21, 23, 24, 25, 30, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 45, 48, 54, 65, 66, 69, 70, emissions shall not exceed the maximum levels specified in tables 6.6.5.5.5.2-4, 6.6.5.5.5.2-6 and 6.6.5.5.5.2-8. + +For E-UTRA RIB operating in Bands 22, 42, 43, 52 emissions shall not exceed the maximum levels specified in tables 6.6.5.5.5.2-5, 6.6.5.5.5.2-7 and 6.6.5.5.5.2-9. + +**Table 6.7.5.5.5.2-4: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (1GHz < E-UTRA bands $\leq$ 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $9.8 \text{ dBm} - 10/1.4(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -0.2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $3.3 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -2.2 (Note 8) dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (NOTE 8) | 1 MHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -4 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.2-5: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands $> 3 \text{ GHz}$ ) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $10 \text{ dBm} - 10/1.4(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | 0 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $3.3 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -2 (Note 8) dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (NOTE 8) | 1 MHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -4 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.2-6: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (1GHz < E-UTRA bands ≤ 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $5.8 \text{ dBm} - 10/3(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -4.2 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -2.2 dBm (Note 8) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (Note 8) | 1 MHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -4 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.2-7: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $6 \text{ dBm} - 10/3(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -4.0 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -2.0 dBm (Note 8) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (Note 8) | 1 MHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -4 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.2-8: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (1GHz < E-UTRA bands ≤ 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $3.8 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (NOTE 8) | 1 MHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -4 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.2-9: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $4 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -4 dBm (NOTE 8) | 1 MHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -4 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +## 6.7.5.5.5.3 Wide Area BS Category B (Option1) + +For Category B Operating band unwanted emissions, there are two options for the limits that may be applied regionally, option 1 is as follows. For E-UTRA AAS BS operating in Bands 5, 8, 12, 13, 14, 17, 20, 26, 27, 28, 29, 31, 44, 67, 68, 71, 72, 73, 85 emissions shall not exceed the maximum levels specified in Tables 6.7.5.5.5.3-1 to 6.7.5.5.5.3-3. + +**Table 6.7.5.5.5.3-1: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|----------------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $9.8 \text{ dBm} - 10/1.4(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -0.2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $2.85 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -5.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm (Note 8) | 100 kHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -7 dBm/100 kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.3-2: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $5.8 \text{ dBm} - 10/3(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -4.2 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -5.2 dBm (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm (Note 8) | 100 kHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -7 dBm/100 kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.3-3: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands < 1 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $3.8 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -7 dBm (NOTE 8) | 100 kHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -7 dBm/100 kHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For E-UTRA *RIB* operating in Bands 1, 2, 3, 4, 7, 10, 25, 30, 33, 34, 35, 36, 37, 38, 39, 40, 41, 45, 48, 65, 66, 69, 70, emissions shall not exceed the maximum levels specified in tables 6.6.5.5.5.3-4, 6.6.5.5.5.3-6 and 6.6.5.5.5.3-8. + +For E-UTRA *RIB* operating in Bands 22, 42, 43, 52 emissions shall not exceed the maximum levels specified in tables 6.6.5.5.5.3-5, 6.6.5.5.5.3-7 and 6.6.5.5.5.3-9. + +**Table 6.7.5.5.5.3-4: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (1GHz < E-UTRA bands $\leq 3 \text{ GHz}$ ) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $9.8 \text{ dBm} - 10/1.4(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -0.2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $3.3 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -4.2 dBm (Note 8) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (Note 8) | 1 MHz | + +NOTE 1: For a RIB supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -6 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.3-5: Wide Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $10\text{dBm} - 10/1.4(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | 0 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $3.3 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -4 dBm (Note 8) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (Note 8) | 1 MHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -6 dBm/1 MHz. + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.3-6: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (1GHz < E-UTRA bands $\leq 3 \text{ GHz}$ ) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $5.8 \text{ dBm} - 10/3(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -4.2 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -4.2 dBm (Note 8) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (Note 8) | 1 MHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -6 dBm/1 MHz. + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.3-7: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $6 \text{ dBm} - 10/3(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -4 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -4 dBm (Note 8) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (Note 8) | 1 MHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -6 dBm/1 MHz. + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.3-8: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (1GHz < E-UTRA bands $\leq$ 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $3.8 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (NOTE 8) | 1 MHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -6 dBm/1 MHz. + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.3-9: Wide Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands > 3 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $4 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -3 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (NOTE 8) | 1 MHz | + +NOTE 1: For a *RIB* supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -6 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +#### 6.7.5.5.5.4 Wide Area BS Category B (Option 2) + +For Category B Operating band unwanted emissions, there are two options for the limits that may be applied regionally, option 2 is as follows. + +The limits in this clause are intended for Europe and may be applied regionally for a *RIB* operating in band 1, 3, 8, 32, 33, 34 or 65. + +For a *RIB* operating in band 1, 3, 8, 32, 33, 34 or 65, emissions shall not exceed the maximum levels specified in table 6.6.5.5.5.4-1 below for 5, 10, 15 and 20 MHz channel bandwidth. + +**Table 6.7.5.5.5.4-1: Regional Wide Area BS operating band unwanted emission limits in band 1, 3, 8, 32, 33, 34 or 65 for 5, 10, 15 and 20 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -3.2 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-3.2 \text{ dBm} - 15(f\_offset/\text{MHz}-0.215) \text{ dB}$ | 30 kHz | +| (Note 7) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -15.2 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $1.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -2.2 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -6 dBm (NOTE 8) | 1 MHz | + +NOTE 1: For a *RIB* supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -6 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 7: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For a *RIB* operating in band 3, 8 or 65, emissions shall not exceed the maximum levels specified in table 6.7.5.5.5.4-2 for 3 MHz channel bandwidth. + +**Table 6.7.5.5.5.4-2: Regional Wide Area BS operating band unwanted emission limits in band 3, 8 or 65 for 3 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $15.8 \text{ dBm} - 60(f\_offset\_MHz - 0.015) \text{ dB}$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $12.8 \text{ dBm} - 160(f\_offset\_MHz - 0.065) \text{ dB}$ | 30 kHz | +| $0.15 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.165 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | $-3.2 \text{ dBm}$ | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-3.2 \text{ dBm} - 15(f\_offset\_MHz - 0.215) \text{ dB}$ | 30 kHz | +| (Note 7) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $-15.2 \text{ dBm}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$ , | $-2.2 \text{ dBm}$ | 1 MHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | $-4.2 \text{ dBm}$ | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-6 \text{ dBm}$ (Note 8) | | + +NOTE 1: For a *RIB* supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $-6 \text{ dBm}/1 \text{ MHz}$ . + +NOTE 2: For a *multi-band RIB* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 7: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For a BS operating in band 3, 8 or 65, emissions shall not exceed the maximum levels specified in table 6.7.5.5.5.4-3 for 1.4 MHz channel bandwidth. + +**Table 6.7.5.5.5.4-3: Regional Wide Area BS operating band unwanted emission limits in band 3, 8 or 65 for 1.4 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | $15.8 \text{ dBm} - 60(f\_offset/\text{MHz}-0.015) \text{ dB}$ | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | $12.8 \text{ dBm} - 160(f\_offset/\text{MHz}-0.065) \text{ dB}$ | 30 kHz | +| $0.15 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.165 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | $-3.2 \text{ dBm}$ | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $-3.2-15(f\_offset/\text{MHz}-0.215) \text{ dB}$ | 30 kHz | +| (Note 7) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | $-15.2 \text{ dBm}$ | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 2.8 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 3.3 \text{ MHz}$ | $-2.2 \text{ dBm}$ | 1 MHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $3.3 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | $-4.2 \text{ dBm}$ (Note 8) | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-6 \text{ dBm}$ (Note 8) | 1 MHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $-6 \text{ dBm}/1 \text{ MHz}$ . + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*, where the contribution from the far-end sub-block or *Base Station RF Bandwidth* shall be scaled according to the measurement bandwidth of the near-end sub-block or *Base Station RF Bandwidth*. + +NOTE 7: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +#### 6.7.5.5.5.5 Local Area BS (Category A and B) + +For an AAS BS of Local Area BS class in E-UTRA bands $\leq 3 \text{ GHz}$ , emissions shall not exceed the maximum levels specified in Tables 6.7.5.5.5.5-1, 6.7.5.5.5.5-3 and 6.7.5.5.5.5-5. + +For an AAS BS of Local Area BS class in E-UTRA bands $> 3 \text{ GHz}$ , emissions shall not exceed the maximum levels specified in tables 6.7.5.5.5.5-2, 6.7.5.5.5.5-4 and 6.7.5.5.5.5-6. + +**Table 6.7.5.5.5.5-1: Local Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-10.2 \text{ dBm} - 10/1.4(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | $-20.2 \text{ dBm}$ | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $2.85 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $-20.2 \text{ dBm}$ (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-22 \text{ dBm}$ (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $-22 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.5-2: Local Area BS operating band unwanted emission limits for 1.4 MHz channel bandwidth (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-10 \text{ dBm} - 10/1.4(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -20 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $2.85 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -20 dBm (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -22 dBm (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -22 dBm/100 kHz. + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.5-3: Local Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-14.2 \text{ dBm} - 10/3(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -24.2 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -24.2 dBm (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -26 dBm (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -26 dBm/100 kHz. + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.5-4: Local Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-14 \text{ dBm} - 10/3(f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -24 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -24 dBm (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -26 dBm (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -26 dBm/100 kHz. + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.5-5: Local Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands $\leq 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-19.2 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -26.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm (NOTE 8) | 100 kHz | + +NOTE 1: For a *R/B* supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -28 dBm/100 kHz. + +NOTE 2: For a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.5-6: Local Area BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth (E-UTRA bands $> 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-19 \text{ dBm} - 7/5(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -26 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm (NOTE 8) | 100 kHz | + +NOTE 1: For a *R/B* supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -28 dBm/100 kHz. + +NOTE 2: For BS a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}} \text{ MHz}$ the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +#### 6.7.5.5.5.6 Medium Range BS (Category A and B) + +For an AAS BS of Medium Range BS class in E-UTRA bands $\leq 3 \text{ GHz}$ , emissions shall not exceed the maximum levels specified in Tables 6.7.5.5.5.6-1, 6.7.5.5.5.6-3, 6.7.5.5.5.6-5, 6.7.5.5.5.6-7, 6.7.5.5.5.6-9 and 6.7.5.5.5.6-11. + +For an AAS BS of Medium Range BS class in E-UTRA bands $> 3 \text{ GHz}$ , emissions shall not exceed the maximum levels specified in Tables 6.7.5.5.5.6-2, 6.7.5.5.5.6-4, 6.7.5.5.5.6-6, 6.7.5.5.5.6-8, 6.7.5.5.5.6-10 and 6.7.5.5.5.6-12. + +**Table 6.7.5.5.6-1: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm (E-UTRA bands $\leq 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 43.2 \text{ dB} - (10/1.4) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 53.2 \text{ dB}$ | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $2.85 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -14.2 dBm (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -16 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *R/B* supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -16 dBm/100 kHz. + +NOTE 2: For a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-2: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm (E-UTRA bands $> 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 43 \text{ dB} - (10/1.4) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 53 \text{ dB}$ | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $2.85 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -14 dBm (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -16 dBm (Note 8) | 100 kHz | + +NOTE 1: For a *R/B* supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -25 dBm/100 kHz. + +NOTE 2: For a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-3: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $P_{\text{rated,c,TRP}} \leq 40$ dBm (E-UTRA bands $\leq 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-3.2 \text{ dBm} - 10/1.4(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -13.2 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $2.85 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14.2dBm (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -16 dBm/100 kHz. + +NOTE 2: For BS a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-4: Medium Range BS operating band unwanted emission limits for 1.4 MHz channel bandwidth, $P_{\text{rated,c,TRP}} \leq 40$ dBm (E-UTRA bands $> 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1.4 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.45 \text{ MHz}$ | $-3 \text{ dBm} - 10/1.4(f\_offset/\text{MHz}-0.05) \text{ dB}$ | 100 kHz | +| $1.4 \text{ MHz} \leq \Delta f < 2.8 \text{ MHz}$ | $1.45 \text{ MHz} \leq f\_offset < 2.85 \text{ MHz}$ | -13 dBm | 100 kHz | +| $2.8 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $2.85 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14dBm (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -16 dBm/100 kHz. + +NOTE 2: For a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-5: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm (E-UTRA bands $\leq 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 47.2 \text{ dB} - (10/3) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 57.2 \text{ dB}$ | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $\text{Min}(P_{\text{rated,c,TRP}} - 57.2 \text{ dB}, -14.2 \text{ dBm})$ (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\text{Min}(P_{\text{rated,c,TRP}} - 59 \text{ dB}, -16 \text{ dBm})$ (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $\text{Min}(P_{\text{rated,c,TRP}} - 59 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-6: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 47 \text{ dB} - (10/3) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 57 \text{ dB}$ | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $\min(P_{\text{rated,c,TRP}} - 57 \text{ dB}, -14 \text{ dBm})$ (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,TRP}} - 59 \text{ dB}, -16 \text{ dBm})$ (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $\min(P_{\text{rated,c,TRP}} - 59 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-7: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $P_{\text{rated,c,TRP}} \leq 40$ dBm (E-UTRA bands $\leq 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-7.2 \text{ dBm} - 10/3 \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | $-17.2 \text{ dBm}$ | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $-17.2 \text{ dBm}$ (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-19 \text{ dBm}$ (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $-19 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-8: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $P_{\text{rated,c,TRP}} \leq 40$ dBm (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-7 \text{ dBm} - 10/3 \cdot (f\_offset/\text{MHz} - 0.05) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | $-17 \text{ dBm}$ | 100 kHz | +| $6 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $6.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $-17 \text{ dBm}$ (Note 8) | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-19 \text{ dBm}$ (Note 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $-19 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-9: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm (E-UTRA bands $\leq 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51.2 \text{ dB} - (7/5) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,c,TRP}} - 58.2 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$ (NOTE 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-10: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm (E-UTRA bands $> 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 51 \text{ dB} - (7/5) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,c,TRP}} - 58 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$ (NOTE 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.6-11: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $P_{\text{rated,c,TRP}} \leq 40$ dBm (E-UTRA bands $\leq 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 11.2 \text{ dB} - (7/5) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $-18.2 \text{ dBm}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-20 \text{ dBm}$ (NOTE 8) | 100 kHz | + +NOTE 1: For a R/B supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be $-20 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For a multi-band R/B with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.7.5.5.5.6-12: Medium Range BS operating band unwanted emission limits for 5, 10, 15 and 20 MHz channel bandwidth, $P_{\text{rated,c,TRP}} \leq 40$ dBm (E-UTRA bands > 3 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Notes 1 and 2) | Measurement bandwidth | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $P_{\text{rated,c,TRP}} - 11 \text{ dB} - (7/5) \cdot (f\_offset - 0.05) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -18 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -20 dBm (NOTE 8) | 100 kHz | + +NOTE 1: For a *R/B* supporting non-contiguous spectrum operation within any operating band the test requirement within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the test requirement within sub-block gaps shall be -20 dBm/100 kHz. + +NOTE 2: For a *multi-band R/B* with *Inter RF Bandwidth gap* $< 2 \times \Delta f_{\text{OBUE}}$ MHz the test requirement within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent sub-blocks or *Base Station RF Bandwidth* on each side of the *Inter RF Bandwidth gap*. + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +#### 6.7.5.5.5.7 Additional requirements + +In certain regions the following test requirement may apply. For E-UTRA *R/B* operating in Bands 5, 26, 27 or 28, emissions shall not exceed the maximum levels specified in Table 6.7.5.5.5.7-1. + +**Table 6.7.5.5.5.7-1: Additional operating band unwanted emission limits for E-UTRA bands < 1 GHz** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement | Measurement bandwidth | +|-------------------|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------|-----------------------| +| 1.4 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.005 \text{ MHz} \leq f\_offset < 0.995 \text{ MHz}$ | -12.2 dBm | 10 kHz | +| 3 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -11.2 dBm | 30 kHz | +| 5 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -13.2 dBm | 30 kHz | +| 10 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -11.2 dBm | 100 kHz | +| 15 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -11.2 dBm | 100 kHz | +| 20 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -11.2 dBm | 100 kHz | +| All | $1 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\text{max}})$ | $1.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | -11.2 dBm (Note 8) | 100 kHz | +| All | $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -13 dBm (Note 8) | 100 kHz | + +NOTE 8: The requirement is not applicable when $\Delta f_{\text{max}} < 10 \text{ MHz}$ . + +In certain regions the following test requirement may apply. For E-UTRA a *RIB* operating in Bands 2, 4, 10, 23, 25, 30, 35, 36, 41, 66, emissions shall not exceed the maximum levels specified in Table 6.7.5.5.7-2. + +**Table 6.7.5.5.7-2: Additional operating band unwanted emission limits for E-UTRA bands > 1GHz** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement | Measurement bandwidth | +|-------------------|-----------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------|-----------------------| +| 1.4 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.005 \text{ MHz} \leq f\_offset < 0.995 \text{ MHz}$ | -12.2 dBm | 10 kHz | +| 3 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -11.2 dBm | 30 kHz | +| 5 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.985 \text{ MHz}$ | -13.2 dBm | 30 kHz | +| 10 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -11.2 dBm | 100 kHz | +| 15 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -13.2 dBm | 100 kHz | +| 20 MHz | $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.95 \text{ MHz}$ | -14.2 dBm | 100 kHz | +| All | $1 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $1.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -11.2 dBm (Note 8) | 1 MHz | +| All | $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 1 MHz | + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +In certain regions the following test requirement may apply. For E-UTRA a *RIB* operating in Bands 12, 13, 14, 17, 29, 85 emissions shall not exceed the maximum levels specified in Table 6.7.5.5.7-3. + +**Table 6.7.5.5.7-3: Additional operating band unwanted emission limits for E-UTRA (bands 12, 13, 14, 17, 29, 85)** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement | Measurement bandwidth | +|-------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------|--------------------|-----------------------| +| All | $0 \text{ MHz} \leq \Delta f < 100 \text{ kHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.085 \text{ MHz}$ | -11.2 dBm | 30 kHz | +| All | $100 \text{ kHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $150 \text{ kHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -11.2 dBm (Note 8) | 100 kHz | +| All | $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 8) | 100 kHz | + +NOTE 8: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +In certain regions, the following test requirements may apply to an E-UTRA TDD *RIB* operating in the same geographic area and in the same operating band as another E-UTRA TDD system without synchronisation. For this case the emissions shall not exceed -52 dBm/MHz in each supported downlink operating band, except in: + +- The frequency range from $\Delta f_{\text{OBUE}}$ MHz below the lower channel edge to the frequency $\Delta f_{\text{OBUE}}$ MHz above the upper channel edge of each supported band. + +In certain regions the following test requirement may apply for protection of DTT. For E-UTRA a *RIB* operating in Band 20, the level of emissions in the band 470-790 MHz, measured in an 8 MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to Table 6.7.5.5.7-4, shall not exceed the maximum emission TRP level shown in the table. This test requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 6.7.5.5.5.7-4: Declared emissions levels for protection of DTT** + +| Case | Measurement filter centre frequency | Condition on BS maximum aggregate EIRP / 10 MHz, $P_{\text{EIRP\_10MHz}}$ (NOTE) | Maximum Level $P_{\text{EIRP,N,MAX}}$ | Measurement Bandwidth | +|---------------------------------------------------------------------------------------------|--------------------------------------|----------------------------------------------------------------------------------|---------------------------------------|-----------------------| +| A: for DTT frequencies where broadcasting is protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{EIRP\_10 MHz}} \geq 59$ dBm | 1.8dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{EIRP\_10 MHz}} < 59$ dBm | $P_{\text{EIRP\_10 MHz}} - 57.2$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{EIRP\_10 MHz}} < 36$ dBm | -21.2dBm | 8 MHz | +| B: for DTT frequencies where broadcasting is subject to an intermediate level of protection | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{EIRP\_10 MHz}} \geq 59$ dBm | 11.8dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{EIRP\_10 MHz}} < 59$ dBm | $P_{\text{EIRP\_10 MHz}} - 47.2$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{EIRP\_10 MHz}} < 36$ dBm | -11,2dBm | 8 MHz | +| C: for DTT frequencies where broadcasting is not protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | N.A. | 23.8dBm | 8 MHz | + +NOTE: $P_{\text{EIRP\_10 MHz}}$ (dBm) is defined by the expression $P_{\text{EIRP\_10 MHz}} = P_{10 \text{ MHz}} + G_{\text{ant}} + 6\text{dB}$ for UTRA and $P_{\text{EIRP\_10 MHz}} = P_{10 \text{ MHz}} + G_{\text{ant}} + 9\text{dB}$ for E-UTRA, where $G_{\text{ant}}$ is 17 dBi + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions and the deployment (including antenna gain and feeder loss). The method outlined in annex B1, TS 37.105 [6] indicates how the limit in Table 6.7.5.5.5.7-4 demonstrates compliance to the regional requirement. + +In regions where FCC regulation applies, requirements for protection of GPS according to FCC Order DA 20-48 applies for operation in Band 24. The following normative requirement covers the base station, to be used together with other information about the site installation to verify compliance with the requirement in FCC Order DA 20-48. The requirement applies to BS operating in Band 24 to ensure that appropriate interference protection is provided to the GPS. This requirement applies in the frequency range 1541-1650 MHz even though part of the range falls in the spurious domain. + +The level of emissions in the 1541 - 1650 MHz band, measured in measurement bandwidth according to table 6.7.5.5.5.7-5 shall not exceed the maximum TRP limits indicated in the table. + +**Table 6.7.5.5.5.7-5: Emissions test requirements for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range (MHz) | Emission level (dBW) (Measurement bandwidth = 1 MHz) | Emission level (dBW) of discrete emissions of less than 700 Hz bandwidth (Measurement bandwidth = 1 kHz) | Emission level (dBW) of discrete emissions of less than 2 kHz bandwidth (Measurement bandwidth = 1 kHz) | +|----------------|-----------------------|------------------------------------------------------|----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| 24 | 1541 - 1559 | $P_{\text{EIRP}} - 17$ dBi + 9 dB | | $P_{\text{EIRP}} - 17$ dBi + 9 dB | +| | 1559 - 1610 | $P_{\text{EIRP}} - 17$ dBi + 9 dB | $P_{\text{EIRP}} - 17$ dBi + 9 dB | | +| | 1610 - 1650 | $P_{\text{EIRP}} - 17$ dBi + 9 dB | $P_{\text{EIRP}} - 17$ dBi + 9 dB | | + +NOTE: The regional requirements, included in FCC Order DA 20-48 are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in TS 37.105 [6], Annex B1 indicates how the limit in table 6.7.5.5.5.7-5 demonstrates compliance to the regional requirement in DA 20-48. $P_{\text{EIRP}}$ values in table 6.7.5.5.5.7-5 are the effective isotropic power (or radiated power spectral density) set in the FCC Order DA 20-48 for the specified frequency ranges and bandwidths. + +**Table 6.7.5.5.5.7-6: Void** + +For BS operating in bands n50, n51, n74, n75 and n76 additional emission limits are specified in clauses 6.7.5.5.4.6. + +**Table 6.7.5.5.5.7-7: void** + +**Table 6.7.5.5.5.7-8: void** + +**Table 6.7.5.5.5.7-8a: void** + +**Table 6.7.5.5.5.7-8b: void** + +In certain regions the following requirement may apply to E-UTRA BS operating in Band 45. Emissions shall not exceed the maximum levels specified in table 6.7.5.5.5.7-9. + +**Table 6.7.5.5.5.7-9: Emissions limits for protection of adjacent band services** + +| Operating Band | Filter centre frequency, $F_{\text{filter}}$ | Maximum Level [dBm] | Measurement Bandwidth | +|----------------|---------------------------------------------------------------------|---------------------|-----------------------| +| 45 | $F_{\text{filter}} = 1467.5$ | -11 | 1 MHz | +| | $F_{\text{filter}} = 1468.5$ | -14 | 1 MHz | +| | $F_{\text{filter}} = 1469.5$ | -17 | 1 MHz | +| | $F_{\text{filter}} = 1470.5$ | -24 | 1 MHz | +| | $F_{\text{filter}} = 1471.5$ | -31 | 1 MHz | +| | $1472.5 \text{ MHz} \leq F_{\text{filter}} \leq 1491.5 \text{ MHz}$ | -38 | 1 MHz | + +The following requirement may apply to BS operating in Band 48 in certain regions. Emissions shall not exceed the maximum levels specified in table 6.7.5.5.5.7-10. + +**Table 6.7.5.5.5.7-10: Additional operating band unwanted emission limits for Band 48** + +| Channel bandwidth | Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Test requirement | Measurement bandwidth | +|-------------------|---------------------------------------------------------------|------------------------------------------------------------------------------|------------------|-----------------------| +| All | $0 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $0.5 \text{ MHz} \leq f_{\text{offset}} < 9.5 \text{ MHz}$ | -4 dBm | 1 MHz | + +## 6.7.6 OTA Spurious emission + +### 6.7.6.1 General + +The OTA spurious emissions limits are specified as TRP per cell unless otherwise specified. + +The OTA transmitter spurious emission limits apply from 30 MHz to 12.75 GHz, excluding the following RAT-specific frequency ranges: + +- UTRA FDD BS as specified in TS 25.104 [2]: from 12.5 MHz below the lowest carrier frequency used up to 12.5 MHz above the highest carrier frequency used. + +- E-UTRA BS as specified in TS 36.104 [4]: from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band*, where $\Delta f_{\text{OBUE}}$ is defined in clause 6.7.1. +- MSR BS as specified in TS 37.104 [5]: from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the *downlink operating band*, where $\Delta f_{\text{OBUE}}$ is defined in clause 6.7.1. For some operating bands the upper frequency limit is higher than 12.75 GHz in order to comply with the 5th harmonic limit of the *downlink operating band*, as specified in ITU-R recommendation SM.329 [16]. In some exceptional cases, requirements apply also closer than 10 MHz from the *downlink operating band*; these cases are highlighted in the requirement tables in respective referenced UTRA, E-UTRA, NR or MSR specifications. For operating bands supported by *multi-band RIB* each supported band including the $\Delta f_{\text{OBUE}}$ around the band are excluded from the spurious emissions requirements. + +The requirements apply for both *single band RIBs* and *multi-band RIBs* (except for frequencies at which exclusion bands or other multi-band provisions apply) and for all transmission modes foreseen by the manufacturer's specification. Unless otherwise stated, all requirements are measured as mean power. + +For operation in Region 2, where the FCC guidance for MIMO systems in [17] is applicable, the emissions limits are the same regardless of the number of transceiver units so the limits are equivalent to those for a single transceiver unit as specified in the as the corresponding applicable *non-AAS BS* per transmitter requirement specified in TS 25.104 [2], TS 25.105 [3], TS 36.104 [4], TS 37.104 [5] or TS 38.104 [33]. For E-UTRA and NR the limits will be 9dB lower and for UTRA FDD the limits will be 6dB lower, unless stated differently in regional regulation. + +The AAS BS requirements for spurious emissions limits which are specified for Band 46 in TS 37.104 [5], are applicable for AAS BS. + +For BS operating in bands n50, n51, n74, n75 and n76 additional emission limits that might be applicable in the spurious emissions frequency domain are specified in clause 6.7.5.5.4.6. + +## 6.7.6.2 Mandatory Requirements + +### 6.7.6.2.1 Definition and applicability + +The OTA spurious emissions mandatory requirements include the CAT A, CAT B and additional minimum requirements for BC2, limits are specified as TRP per cell unless otherwise specified. + +### 6.7.6.2.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.6.2.1. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.6.3.1. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.6.4.1. + +### 6.7.6.2.3 Test purpose + +The test purpose is to verify the radiated spurious emissions from the AAS BS at the RIB are within the specified minimum requirements. + +### 6.7.6.2.4 Method of test + +#### 6.7.6.2.4.1 Initial conditions + +Test environment: normal, see annex G.2. + +RF channels to be tested for single carrier: + +B when testing from $30 \text{ MHz}$ to $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ + +T when testing from $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ to $12.75 \text{ GHz}$ (or to 5th harmonic) + +RF bandwidth positions to be tested: in single-band operation, see clause 4.12.1. + +$B_{\text{RFBW}}$ when testing from 30 MHz to $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ + +$T_{\text{RFBW}}$ when testing from $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ to 12.75 GHz (or 5th harmonic) + +RF bandwidth positions to be tested in multi-band operation, see clause 4.12.1. + +$B_{\text{RFBW\_T}}'_{\text{RFBW}}$ when testing from 30 MHz to $F_{\text{DL\_Blow\_low}} - \Delta f_{\text{OBUE}}$ + +$B'_{\text{RFBW\_T}}'_{\text{RFBW}}$ when testing from $F_{\text{DL\_Bhigh\_high}} + \Delta f_{\text{OBUE}}$ to 12.75 GHz (or to 5th harmonic) + +$B_{\text{RFBW\_T}}'_{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}'_{\text{RFBW}}$ when testing from $F_{\text{DL\_Blow\_high}} + \Delta f_{\text{OBUE}}$ to $F_{\text{DL\_Bhigh\_low}} - \Delta f_{\text{OBUE}}$ + +Directions to be tested + +As the requirement is TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see annex F). + +#### 6.7.6.2.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in in Annex F. An alternative method to measure TRP is to use a characterized and calibrated reverberation chamber. If so, follow steps 1, 3, 4, 5, 7 and 10. When calibrated and operated within the guidance of 3GPP TR 37.941 [38] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Measurements shall use a measurement bandwidth in accordance to the conditions in clause 6.7.6.2.5. +- 4) The measurement device characteristics shall be: + - Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 5) Set the AAS BS to transmit + - a) For MSR: + - Set the RIB to transmit maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.11. + - b) For UTRA: + - For a RIB declared to be capable of single carrier operation only, set the RIB to transmit a signal according to TM1, clause 4.12.2, at the manufacturer's declared rated carrier TRP, $P_{\text{rated,c,TRP}}$ . + - For a RIB declared to be capable of multi-carrier operation, set the set the RIB to transmit according to TM1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + - c) For E-UTRA: + - RIB declared to be capable of single carrier operation only, set the RIB to transmit a signal according to E-TM1.1 in clause 4.12.2, at manufacturer's declared rated carrier TRP, $P_{\text{rated,c,TRP}}$ . + - For a RIB declared to be capable of multi-carrier and/or CA operation, set the set the RIB to transmit according to E-TM1.1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. +- 6) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex F). + +- 7) Measure the emission at the specified frequencies with specified measurement bandwidth +- 8) Repeat step 6-7 for all directions in the appropriated TRP measurement grid needed for full TRP estimation (see annex F). + +NOTE 1: The TRP measurement grid may not be the same for all measurement frequencies. + +NOTE 2: The frequency sweep or the TRP measurement grid sweep may be done in any order + +- 9) Calculate TRP at each specified frequency using the directional measurements. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 10) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.7.6.2.5 Test Requirement + +##### 6.7.6.2.5.1 MSR operation + +###### Category A requirements + +For an AAS BS meeting category A the TRP of any spurious emission shall not exceed the limits in table 6.7.6.2.5.1-1 + +**Table 6.7.6.2.5.1-1: AAS BS OTA Spurious emission limits, Category A** + +| Frequency range | Maximum level | Measurement Bandwidth | NOTE | +|--------------------------------------------------------------------------------------------------|---------------|-----------------------|----------------| +| 30 MHz - 1 GHz | | 100 kHz | NOTE 1 | +| 1 GHz - 12.75 GHz | -13 + X dBm | 1 MHz | NOTE 2 | +| 12.75 GHz – 5 th harmonic of the upper frequency edge of the DL operating band in GHz | NOTE 4, | 1 MHz | NOTE 2, NOTE 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [16], s4.1 +NOTE 2: Bandwidth as in ITU-R SM.329 [16], s4.1. Upper frequency as in ITU-R SM.329 [16] , s2.5 table 1 +NOTE 3: Applies only for Bands 22, 42, 43, 48. +NOTE 4: X = 9 dB for E-UTRA, X = 6 dB for UTRA, unless stated differently in regional regulation. + +###### Category B requirements + +For UTRA, the minimum requirement is specified in clause 6.7.6.2.5.2 + +For E-UTRA and NR, the minimum requirement is specified in clause 6.7.6.2.5.3 + +###### Additional requirements for BC2 (category B) + +For AAS BS operating in Band Category 2 when GSM/EDGE is configured, the power of any spurious emission shall not exceed the limits in table 6.7.6.2.5.1-2. + +For *multi-band RIBs* the limits in table 6.7.6.2.5.1-2 are only applicable when all supported operating bands belong to BC2 and GSM/EDGE is configured in all bands. + +**Table 6.7.6.2.5.1-2: Additional AAS BS OTA Spurious emissions limits for BC2, Category B** + +| Frequency range | Frequency offset from downlink operating band edge (NOTE) | Maximum Level | Measurement Bandwidth | +|-----------------------------------|------------------------------------------------------------------|---------------|-----------------------| +| 500 MHz $\leftrightarrow$ 1 GHz | 10 – 20 MHz | -25 dBm | 300 kHz | +| | 20 – 30 MHz | -25 dBm | 1 MHz | +| | $\geq 30$ MHz | -25 dBm | 3 MHz | +| 1 GHz $\leftrightarrow$ 12.75 GHz | $\geq 30$ MHz | -22 dBm | 3 MHz | + +NOTE: For *multi-band RIBs*, the frequency offset is relative to the closest operating band. + +#### 6.7.6.2.5.2 Single RAT UTRA operation + +##### Category A requirements + +For an AAS BS meeting category A the TRP of any spurious emission shall not exceed the limits in table 6.7.6.2.5.1-1 + +##### Category B requirements + +The following limits shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [16], are applied. + +The TRP of any spurious emission shall not exceed the limits in tables 6.7.6.2.5.2-1 and 6.7.6.2.5.2-2 + +**Table 6.7.6.2.5.2-1: OTA AAS BS Mandatory spurious emissions limits, operating band I, II, III, IV, VII, X, XXII, XXV, XXXII (Category B)** + +| Band | Maximum Level (Note 5) | Measurement Bandwidth | Notes | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------|----------------| +| 30 MHz $\leftrightarrow$ 1 GHz | $-36 + X$ dBm | 100 kHz | NOTE 1 | +| 1 GHz $\leftrightarrow F_{\text{low}} - 10$ MHz | $-30 + X$ dBm | 1 MHz | NOTE 1 | +| $F_{\text{low}} - 10$ MHz $\leftrightarrow F_{\text{high}} + 10$ MHz | $-15 + X$ dBm | 1 MHz | NOTE 2 | +| $F_{\text{high}} + 10$ MHz $\leftrightarrow 12.75$ GHz | $-30 + X$ dBm | 1 MHz | NOTE 3 | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the DL operating band in GHz | $-30 + X$ dBm | 1 MHz | NOTE 3, NOTE 4 | +| NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [16], s4.1 | | | | +| NOTE 2: Limit based on ITU-R Recommendation SM.329 [16], s4.3 and Annex 7 | | | | +| NOTE 3: Bandwidth as in ITU-R Recommendation SM.329 [16], s4.1. Upper frequency as in ITU-R SM.329 [16], s2.5 table 1 | | | | +| NOTE 4: Applies only for Band XXII | | | | +| NOTE 5: $X = 6$ dB, unless stated differently in regional regulation. | | | | +| Key:
$F_{\text{low}}$ : The lowest downlink frequency of the operating band as defined in clause 4.7
$F_{\text{high}}$ : The highest downlink frequency of the operating band as defined in clause 4.7 | | | | + +**Table 6.7.6.2.5.2-2: BS Mandatory spurious emissions limits, operating band V, VIII, XII, XIII, XIV, XX, XXVI (Category B)** + +| Band | Maximum Level (Note 4) | Measurement Bandwidth | Notes | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------|--------| +| 30 MHz $\leftrightarrow$ $F_{\text{low}} - 10$ MHz | $-36 + X$ dBm | 100 kHz | NOTE 1 | +| $F_{\text{low}} - 10$ MHz $\leftrightarrow$ $F_{\text{high}} + 10$ MHz | $-16 + X$ dBm | 100 kHz | NOTE 2 | +| $F_{\text{high}} + 10$ MHz $\leftrightarrow$ 1 GHz | $-36 + X$ dBm | 100 kHz | NOTE 1 | +| 1 GHz $\leftrightarrow$ 12.75 GHz | $-30 + X$ dBm | 1 MHz | NOTE 3 | +| NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [16], s4.1 | | | | +| NOTE 2: Limit based on ITU-R Recommendation SM.329 [16], s4.3 and Annex 7 | | | | +| NOTE 3: Bandwidth as in ITU-R Recommendation SM.329 [16], s4.1. Upper frequency as in ITU-R SM.329 [16], s2.5 table 1 | | | | +| NOTE 4: $X = 6$ dB, unless stated differently in regional regulation. | | | | +| Key:
$F_{\text{low}}$ : The lowest downlink frequency of the operating band as defined in clause 4.7
$F_{\text{high}}$ : The highest downlink frequency of the operating band as defined in clause 4.7 | | | | + +#### 6.7.6.2.5.3 Single RAT E-UTRA operation + +##### Category A requirements + +For an AAS BS meeting category A the TRP of any spurious emission shall not exceed the limits in table 6.7.6.2.5.1-1 + +##### Category B requirements + +The TRP of any spurious emission shall not exceed the limits in table 6.7.6.2.5.3-1 + +**Table 6.7.6.2.5.3-1: AAS BS OTA Spurious emissions limits, Category B** + +| Frequency range | Maximum Level (Note 4) | Measurement Bandwidth | Notes | +|------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------|----------------| +| 30 MHz $\leftrightarrow$ 1 GHz | $-36 + X$ dBm | 100 kHz | NOTE 1 | +| 1 GHz $\leftrightarrow$ 12.75 GHz | $-30 + X$ dBm | 1 MHz | NOTE 2 | +| 12.75 GHz $\leftrightarrow$ 5 th harmonic of the upper frequency edge of the DL operating band in GHz | $-36 + X$ dBm | 1 MHz | NOTE 2, NOTE 3 | +| NOTE 1: Bandwidth as in ITU-R SM.329 [16], s4.1 | | | | +| NOTE 2: Bandwidth as in ITU-R SM.329 [16], s4.1. Upper frequency as in ITU-R SM.329 [16], s2.5 table 1 | | | | +| NOTE 3: Applies only for Bands 22, 42, 43, 48. | | | | +| NOTE 4: $X = 9$ dB, unless stated differently in regional regulation. | | | | + +#### 6.7.6.3 Protection of the BS receiver of own or different BS + +##### 6.7.6.3.1 Definition and applicability + +This requirement shall be applied for FDD operation in order to prevent the receivers of own or a different BS of the same band being desensitised by emissions from a *OTA AAS BS*. + +The requirement is a co-location requirement, the power levels specified at the CLTA output(s). + +##### 6.7.6.3.2 Minimum Requirement + +The minimum requirement for AAS BS in *MSR operation* is defined in TS 37.105 [6], clause 9.7.6.2. + +The minimum requirement for AAS BS in *single RAT UTRA operation* is defined in TS 37.105 [6], clause 9.7.6.3. + +The minimum requirement for AAS BS in *single RAT E-UTRA operation* is defined in TS 37.105 [6], clause 9.7.6.4. + +### 6.7.6.3.3 Test purpose + +The test purpose of OTA spurious emission is to verify the radiated spurious emissions from the AAS BS at the *RIB* are within specified requirements. + +For OTA co-locate spurious emission, the test purpose is to verify that the emission is within the specified requirement limits at the CLTA conducted output(s). + +### 6.7.6.3.4 Method of test + +#### 6.7.6.3.4.1 Initial conditions + +Test environment: + +- normal; see annex G.2. + +RF channels to be tested for single carrier (SC): + +- M; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier (MC): + +- $M_{\text{RFBW}}$ for *single-band RIB*, see clause 4.12.1; $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ for *multi-band RIB*, see clause 4.12.1. + +In addition, for *multi-band RIB*: + +- For $B_{\text{RFBW\_T}}$ , co-location spurious emission testing above the highest operating band may be omitted. +- For $B'_{\text{RFBW\_T}}$ , co-location spurious emission testing below the lowest operating band may be omitted. + +Directions to be tested: + +- The requirement is specified as co-location requirement. For general description of co-location requirements, refer to clause 4.12. + +The co-location spurious emission is measured at the CLTA conducted output(s). + +#### 6.7.6.3.4.2 Procedure + +- 1) Select a CLTA according to parameters given in Table 4.15.2.2-1 and place the CLTA according to parameters given in Table 4.15.2.3-1. +- 2) Several CLTAs are required to cover the whole co-location spurious emission frequency ranges. +- 3) The test antenna shall be dual (or single) polarized with the same frequency range as the *AAS BS* for co-location spurious emission test case. +- 4) Connect test antenna and CLTA to the measurement equipment as depicted in Annex D1.4. +- 5) OTA co-location spurious emission is measured at the CLTA conducted output(s). +- 6) The measurement device (signal analyzer) characteristics shall be: + +- Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 7) Set the *AAS BS* to transmit: + +a) For MSR: + +- Set the *AAS BS* to transmit maximum power, according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.11. + +## b) For UTRA FDD: + +- For a *AAS BS* declared to be capable of single carrier operation only, set the *AAS BS* to transmit full maximum power according to TM1, clause 4.12.2, at the manufacturer's declared rated carrier TRP, $P_{\text{rated,c,TRP}}$ . +- For a *AAS BS* declared to be capable of multi-carrier operation, set the *AAS BS* to transmit maximum power according to TM1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +## c) For E-UTRA: + +- For *AAS BS* declared to be capable of single carrier operation only, set the *AAS BS* to transmit maximum power according to E-TM1.1 in clause 4.12.2, at manufacturer's declared rated carrier TRP, $P_{\text{rated,c,TRP}}$ . +- For a *AAS BS* declared to be capable of multi-carrier and/or CA operation, set the *AAS BS* to transmit maximum power according to E-TM1.1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +- 8) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the test requirement in clause 6.7.6.5. + +NOTE: An alternative measurement method to be used for measuring the OTA emission is described in Annex H. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 9) For *multi-band RIB* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 6.7.6.3.5 Test Requirement + +#### 6.7.6.3.5.1 MSR operation + +The total power from both polarizations of the CLTA connector output(s) of any spurious emission shall not exceed the limits in table 6.7.6.3.5.1-1 depending on the declared Base Station class and Band Category. + +**Table 6.7.6.3.5.1-1: BS Spurious emissions limits for protection of the BS receiver** + +| BS-class | Band category | Frequency range | Maximum Level for bands below 3GHz | Maximum Level for bands between 3 and 4.2GHz | Measurement bandwidth | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------------------------------------------|------------------------------------|----------------------------------------------|-----------------------| +| Wide Area BS | BC1 | $F_{\text{UL\_low}} - F_{\text{UL\_high}}$ | -113.9 dBm | -113.7 dBm | 100 kHz | +| Wide Area BS | BC2 | $F_{\text{UL\_low}} - F_{\text{UL\_high}}$ | -115.9 dBm | -115.7 dBm | 100 kHz | +| Medium Range BS | BC1,BC2 | $F_{\text{UL\_low}} - F_{\text{UL\_high}}$ | -108.9 dBm | -108.7 dBm | 100 kHz | +| Local Area BS | BC1,BC2 | $F_{\text{UL\_low}} - F_{\text{UL\_high}}$ | -105.9 dBm | -105.7 dBm | 100 kHz | +| NOTE: For E-UTRA Band 28 BS operating in regions where Band 28 is only partially allocated for E-UTRA operations, this requirement only applies in the UL frequency range of the partial allocation. | | | | | | + +#### 6.7.6.3.5.2 Single RAT UTRA operation + +The total power of any spurious emission from both polarizations of the CLTA connector output(s) shall not exceed the limits in table 6.7.6.3.5.2-1. + +**Table 6.7.6.3.5.2-1: BS Spurious emissions limits for protection of the BS receiver** + +| | Frequency range | Maximum Level for bands below 3GHz | Maximum Level for bands between 3 and 4.2GHz | Measurement Bandwidth | Notes | +|-----------------|------------------------------|------------------------------------|----------------------------------------------|-----------------------|-------| +| Wide Area BS | $F_{UL\_low} - F_{UL\_high}$ | - 116.9 dBm | - 116.7 dBm | 100 kHz | | +| Medium Range BS | $F_{UL\_low} - F_{UL\_high}$ | - 106.9 dBm | - 106.7 dBm | 100 kHz | | +| Local Area BS | $F_{UL\_low} - F_{UL\_high}$ | - 102.9 dBm | - 102.7 dBm | 100 kHz | | + +#### 6.7.6.3.5.3 Single RAT E-UTRA operation + +The total power of any spurious emission from both polarizations of the CLTA connector output(s) shall not exceed the limits in table 6.7.6.3.5.3-1. + +**Table 6.7.6.3.5.3-1: BS Spurious emissions limits for protection of the BS receiver** + +| | Frequency range | Maximum Level for bands below 3GHz | Maximum Level for bands between 3 and 4.2GHz | Measurement bandwidth | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------------------------|-----------------------| +| Wide Area BS | $F_{UL\_low} - F_{UL\_high}$ | -113.9 dBm | -113.7 dBm | 100 kHz | +| Medium Range BS | $F_{UL\_low} - F_{UL\_high}$ | -108.9 dBm | -108.7 dBm | 100 kHz | +| Local Area BS | $F_{UL\_low} - F_{UL\_high}$ | -105.9 dBm | -105.7 dBm | 100 kHz | +| NOTE: | For E-UTRA Band 28 BS operating in regions where Band 28 is only partially allocated for E-UTRA operations, this requirement only applies in the UL frequency range of the partial allocation. | | | | + +### 6.7.6.4 Additional spurious emissions requirements + +#### 6.7.6.4.1 Definition and applicability + +These requirements may be applied for the protection of system operating in frequency ranges other than the BS *downlink operating band*. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the BS, or they may be set by local or regional regulation as a mandatory requirement for an operating band. It is in some cases not stated in the present document whether a requirement is mandatory or under what exact circumstances that a limit applies, since this is set by local or regional regulation. An overview of regional requirements in the present document is given in clause 4.5. + +Some requirements may apply for the protection of specific equipment (UE, MS and/or BS) or equipment operating in specific systems (GSM/EDGE, CDMA, UTRA, E-UTRA, NR etc.) as listed below. + +All additional spurious requirements are TRP unless otherwise stated. + +#### 6.7.6.4.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.6.2.3. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.6.3.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 9.7.6.4.3. + +#### 6.7.6.4.3 Test purpose + +The test purpose is to verify the radiated spurious emissions from the AAS BS at the RIB are within the specified additional spurious emissions requirements. + +#### 6.7.6.4.4 Method of test + +##### 6.7.6.4.4.1 Initial conditions + +Test environment: normal, see annex G.2. + +RF channels to be tested for single carrier: + +B when testing from $F_{DL\_low} - \Delta f_{OBUE}$ + +T when testing from $F_{DL\_high} + \Delta f_{OBUE}$ to 12.75 GHz (or to 5th harmonic) + +RF bandwidth positions to be tested: in single-band operation, see clause 4.12.1. + +$B_{RFBW}$ when testing from $F_{DL\_low} - \Delta f_{OBUE}$ + +$T_{RFBW}$ when testing from $F_{DL\_high} + \Delta f_{OBUE}$ to 12.75 GHz (or to 5th harmonic) + +RF bandwidth positions to be tested in multi-band operation, see clause 4.12.1. + +$B_{RFBW\_T'_{RFBW}}$ when testing from $F_{DL\_Blow\_low} - \Delta f_{OBUE}$ + +$B'_{RFBW\_T_{RFBW}}$ when testing from $F_{DL\_Bhigh\_high} + \Delta f_{OBUE}$ to 12.75 GHz (or to 5th harmonic) + +$B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ when testing from $F_{DL\_Blow\_high} + \Delta f_{OBUE}$ to $F_{DL\_Bhigh\_low} - \Delta f_{OBUE}$ + +Directions to be tested: + +As the requirement is TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see annex F). + +##### 6.7.6.4.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in Annex F. An alternative method to measure TRP is to use a characterized and calibrated reverberation chamber. If so, follow steps 1, 3, 4, 5, 7 and 10. When calibrated and operated within the guidance of 3GPP TR 37.941 [38] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Measurements shall use a measurement bandwidth in accordance to the conditions in TS 37.104 [5] clause 6.6.1. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 4) The measurement device characteristics shall be: + +- Detection mode: True RMS. + +- 5) Set the AAS BS to transmit + +- a) For MSR: + +- Set the RIB to transmit maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.11. + +- b) For UTRA: + +- For a RIB declared to be capable of single carrier operation only, set the RIB to transmit a signal according to TM1, clause 4.12.2, at the manufacturer's declared rated carrier TRP, $P_{\text{rated,c,TRP}}$ . +- For a RIB declared to be capable of multi-carrier operation, set the set the RIB to transmit according to TM1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +c) For E-UTRA: + +- RIB declared to be capable of single carrier operation only, set the RIB to transmit a signal according to E-TM1.1 in clause 4.12.2, at manufacturer's declared rated carrier TRP $P_{\text{rated,c,TRP}}$ . +- For a RIB declared to be capable of multi-carrier and/or CA operation, set the set the RIB to transmit according to E-TM1.1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +- 6) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex F). +- 7) Measure the emission at the specified frequencies with specified measurement bandwidth +- 8) Repeat step 6-7 for all directions in the appropriated TRP measurement grid needed for full TRP estimation (see annex F). + +Note 1: the TRP measurement grid may not be the same for all measurement frequencies. + +Note 2: the frequency sweep or the TRP measurement grid sweep may be done in any order + +- 9) Calculate TRP at each specified frequency using the directional measurements. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 10) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 6.7.6.4.5 Test Requirement + +##### 6.7.6.4.5.1 MSR operation + +For UTRA, the minimum requirement is specified in clause 6.7.6.4.5.2 + +For E-UTRA, the minimum requirement is specified in clause 6.7.6.4.5.3. + +###### 6.7.6.4.5.1.1 E-UTRA and NR MSR operation + +The TRP of any spurious emission shall not exceed the limits of table 6.7.6.4.5.1.1-1 for an AAS BS where requirements for co-existence with the system listed in the first column apply. For a *multi-band RIB*, the exclusions and conditions in the notes column of table 6.7.6.4.5.1.1-1 apply for each supported operating band. + +**Table 6.7.6.4.5.1.1-1: AAS BS OTA Spurious emissions limits for co-existence with systems operating in other frequency bands** + +| System type to co-exist with | Frequency range for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|-----------------------------------------------------------|----------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | -45.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 8/n8 | +| | 876 - 915 MHz | -49.4 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to BS operating in band 8/n8, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| DCS1800 (Note 3) | 1805 - 1880 MHz | -35.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 3/n3. | +| | 1710 - 1785 MHz | -49.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 3/n3, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| PCS1900 | 1930 - 1990 MHz | -35.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 2/n2, 25/n25, band 36 or band 70/n70. | +| | 1850 - 1910 MHz | -49.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 2/n2 or 25/n25, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in band 35. | +| GSM850 or CDMA850 | 869 - 894 MHz | -45.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 5/n5 or 26/n26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -49.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 5/n5 or 26/n26, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 2110 - 2170 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 1/n1 or 65/n65. | +| | 1920 - 1980 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 1/n1 or 65/n65, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1930 - 1990 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 2/n2, 25/n25 or 70/n70. | +| | 1850 - 1910 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 2/n2 or 25/n25, since it is already covered by the requirement in clause 6.6.6.5.2.4 | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 (Note 3) | 1805 - 1880 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3/n3 or 9. | +| | 1710 - 1785 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3/n3, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in clause 6.7.6.3.5.1 | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66. | +| | 1710 - 1755 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 869 - 894 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 5/n5 or 26/n26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 5/n5 or 26/n26, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | + +| | | | | | +|---------------------------------------------------------------|---------------------|-----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 18, 19 or NR Band n18 | 860 - 890 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 18, 19 | +| | 815 - 830 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 18 since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| | 830 - 845 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 19, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2620 - 2690 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 7/n7. | +| | 2500 - 2570 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 7/n7, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 - 960 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8/n8. | +| | 880 - 915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8/n8, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3/n3 or 9. | +| | 1749.9 - 1784.9 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3/n3 or 9, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66/n66. | +| | 1710 - 1770 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 10 or 66/n66, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in band 4, it applies for 1755 MHz to 1770 MHz, while the rest is covered in clause 6.7.6.3.5.1 | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 - 1510.9 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50/n50, 74 or 75/n75. This requirement does not apply to BS operating in band n92 or n94. | +| | 1427.9 - 1447.9 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 11 or 74, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in band 32, 50/n50, 51/n51, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| | 1447.9 - 1462.9 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 21 or 74, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in band 32, 50/n50 or 75/n75. This requirement does not apply to BS operating in band n92 or n94. | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 729 - 746 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 12/n12 or 85. | +| | 699 - 716 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 12/n12 or 85, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7). | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 746 - 756 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 13. | +| | 777 - 787 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 13/n13, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| UTRA FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 14. | +| | 788 - 798 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 14, since it is already covered by the requirement in clause 6.7.6.3.5.1 | + +| | | | | | +|-----------------------------------------------------|---------------------|-----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 17 | 734 - 746 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 17. | +| | 704 - 716 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 17, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7). | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 791 - 821 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20/n20 or 28/n28. | +| | 832 - 862 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20/n20, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -40.0 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, 42, 48/n48, n77 or n78. | +| | 3410 – 3490 MHz | -37.0 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to Band 42, n77 or n78. | +| E-UTRA Band 24 or NR band n24 | 1525 – 1559 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 24. | +| | 1626.5 – 1660.5 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 24, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR Band n25 | 1930 - 1995 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 2/n2, 25/n25 or 70/n70. | +| | 1850 - 1915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 25/n25, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in band 2/n2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.7.6.3.5.1 | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 - 894 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 5/n5 or 26/n26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 814 - 849 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 26/n26, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in band 5/n5, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.7.6.3.5.1 For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| E-UTRA Band 27 | 852 – 869 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 5/n5, 26 or 27. | +| | 807 – 824 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 27, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 26, it applies for 807 MHz to 814 MHz, while the rest is covered in clause 6.7.6.3.5.1 This requirement also applies to BS operating in Band 28/n28, starting 4 MHz above the Band 28/n28 downlink operating band (Note 6). | +| E-UTRA Band 28 or NR Band n28 | 758 - 803 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20/n20, 28/n28, 44 or 67. | +| | 703 - 748 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 28/n28, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in Band 44. For BS operating in Band 67, it applies for 703-736 MHz. For E-UTRA BS operating in Band 68, it applies for 728 MHz to 733 MHz. | + +| | | | | | +|---------------------------------------------------|-------------------|-----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 29 or 85. | +| E-UTRA Band 30 | 2350 - 2360 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 30 or 40/n40. | +| | 2305 - 2315 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 30, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in Band 40. | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 452.5 – 457.5 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in band 72 or 73. | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50/n50, 74 or 75/n75. This requirement does not apply to BS operating in band n92 or n94. | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR Band n34 | 2010 - 2025 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 34/n34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 2/n2, 25/n25 or 36 | +| UTRA TDD in Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570 – 2620 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 38/n38 or 69. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR Band n39 | 1880 – 1920 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 39/n39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 30 or 40/n40 | +| E-UTRA Band 41 or NR Band n41 | 2496 – 2690 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 41/n41 or 53/n53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48/n48, 52, n77 or n78. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 42, 43, 48/n48, n77 or n78. | +| E-UTRA Band 44 | 703 - 803 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 28/n28 or 44 | +| E-UTRA Band 45 | 1447 - 1467 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 45 | + +| | | | | | +|-------------------------------|-------------------|-----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 MHz | -39.5 dBm | 1 MHz | | +| E-UTRA Band 47 | 5855 - 5925 MHz | -39.5 dBm | 1 MHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48/n48, n77 or n78 | +| E-UTRA Band 49 | 3550 – 3700 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48/n48, n77 or n78 | +| E-UTRA Band 50 or NR Band n50 | 1432 - 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50/n50, 51/n51, 74, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| E-UTRA Band 51 or NR Band n51 | 1427 - 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50/n50, 51/n51, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| E-UTRA Band 52 | 3300 – 3400 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 42 or 52. | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 41/n41 or 53/n53 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 54. | +| E-UTRA Band 65 or NR band n65 | 2110 - 2200 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 1/n1 or 65/n65. | +| | 1920 - 2010 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 65/n65, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 1, it applies for 1980 MHz to 2010 MHz, while the rest is covered in clause 6.7.6.3.5.1 | +| E-UTRA Band 66 or NR Band n66 | 2110 - 2200 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10, 23 or 66/n66. | +| | 1710 - 1780 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 66/n66, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.3.5.1 For BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.3.5.1 | +| E-UTRA Band 67 or NR band n67 | 738 – 758 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 28/n28 or 67. | +| E-UTRA Band 68 | 753 -783 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 28/n28 or 68. | +| | 698-728 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 68, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 28/n28, it applies between 698 MHz and 703 MHz, while the rest is covered in clause 6.7.6.3.5.1 | +| E-UTRA Band 69 | 2570 - 2620 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 38 or 69. | +| E-UTRA Band 70 or NR Band n70 | 1995 - 2020 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 2/n2, 25/n25 or 70/n70 | +| | 1695 – 1710 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 70/n70, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| E-UTRA Band 71 or NR Band n71 | 617 - 652 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 71/n71 or n105. | + +| | | | | | +|-------------------------------|-----------------|-----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 663 – 698 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 71/n71 or n105, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 451 - 456 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 72, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in band 73. | +| E-UTRA Band 73 | 460 - 465 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 450 - 455 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 73, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| E-UTRA Band 74 or NR band n74 | 1475 – 1518 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50/n50, 74 or 75/n75. This requirement does not apply to BS operating in band n92 or n94. | +| | 1427 – 1470 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 74, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in band 32, 45, 50/n50, 51/n51, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| E-UTRA Band 75 or NR Band n75 | 1432 - 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50/n50, 51/n51, 74, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| E-UTRA Band 76 or NR Band n76 | 1427 - 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50/n50, 51/n51, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| NR Band n77 | 3300 – 4200 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48/n48, 52, n77 or n78 | +| NR Band n78 | 3300 – 3800 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48/n48, 52, n77 or n78 | +| NR Band n79 | 4400 – 5000 MHz | -39.5 dBm | 1 MHz | | +| NR Band n80 | 1710 - 1785 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3/n3, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in clause 6.7.6.3.5.1 | +| NR Band n81 | 880 - 915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8/n8, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| NR Band n82 | 832 - 862 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20/n20, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| NR Band n83 | 703 - 748 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 28/n28, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in Band 44. For BS operating in Band 67, it applies for 703-736 MHz. For BS operating in Band 68, it applies for 728 MHz to 733 MHz. | +| NR Band n84 | 1920 - 1980 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 1/n1 or 65, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| E-UTRA Band 85 or NR band n85 | 728 - 746 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 12/n12, 29 or 85. | + +| | | | | | +|----------------|--------------------|-----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 698 - 716 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 12/n12 or 85, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7). | +| NR Band n86 | 1710 - 1780 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 66/n66, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.3.5.1 For BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.3.5.1 | +| E-UTRA Band 87 | 420 - 425 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 87 or 88. | +| | 410 – 415 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 87, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| E-UTRA Band 88 | 422 - 427 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 87 or 88. | +| | 412 - 417 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 88, since it is already covered by the requirement in clause 6.7.6.3.5.1. This requirement does not apply to BS operating in band 87. | +| NR Band n89 | 824 - 849 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 5/n5 or 26, since it is already covered by the requirement in clause 6.7.6.3.5.1 For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band. | +| NR Band n91 | 1427 - 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50/n50, 51/n51, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| | 832 - 862 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20/n20, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| NR Band n92 | 1432 - 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50/n50, 51/n51, 74, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| | 832 - 862 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20/n20, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| NR Band n93 | 1427 - 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50/n50, 51/n51, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| | 880 - 915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8/n8, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| NR Band n94 | 1432 - 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50/n50, 51/n51, 74, 75/n75 or 76/n76. This requirement does not apply to BS operating in band n91, n92, n93 or n94. | +| | 880 - 915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8/n8, since it is already covered by the requirement in clause 6.7.6.3.5.1 | +| NR Band n95 | 2010 - 2025 MHz | -40.4 dBm | 1 MHz | | +| NR Band n96 | 5925 - 7125 MHz | -39.5 dBm | 1 MHz | | +| NR Band n97 | 2300 - 2400 MHz | -40.4 dBm | 1 MHz | | +| NR Band n98 | 1880 - 1920 MHz | -40.4 dBm | 1 MHz | | +| NR Band n99 | 1626.5- 1660.5 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 24, since it is already covered by the requirement in clause 6.7.6.3.5.1 | + +| | | | | | +|---------------------------------|-----------------|-----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n102 | 5925 - 6425 MHz | -39.5 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -40.4 dBm | 1 MHz | | +| | 787 – 788 MHz | -37.4 dBm | 1 MHz | | +| NR Band n104 | 6425 - 7125 MHz | -39.5 dBm | 1 MHz | | +| NR Band n105 | 612 – 652 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 71/n71 or n105 | +| | 663 – 703 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n105 | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 106/n106. | +| | 896 – 901 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 106/n106, since it is already covered by the requirement in clause 6.7.6.3.5.1.
This requirement does not apply to BS operating in band 5 or 26. | +| NR band n109 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74/n74, 75/n75 or 76/n76. | +| | 703 – 733 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 28/n28, since it is already covered by the requirement in clause 6.7.6.3.5.1 This requirement does not apply to BS operating in Band 44. For E-UTRA BS operating in Band 68, it applies for 728 MHz to 733 MHz. | + +NOTE 1: As defined in the scope for spurious emissions in this clause, except for the cases where the noted requirements apply to a BS operating in Band 25/n25, Band 27, Band 28/n28 or Band 29, the co-existence requirements in table 6.7.6.4.5.1.1-1 do not apply for the $\Delta f_{OBUE}$ frequency range immediately outside the *downlink operating band* (see clause 6.7.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. + +NOTE 2: Table 6.7.6.4.5.1.1-1 assumes that two operating bands, where the frequency ranges in clause 4.7 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 3: For the protection of DCS1800, UTRA Band III or E-UTRA Band 3 or NR band n3 in China, the frequency ranges of the downlink and uplink protection requirements are 1805 – 1850 MHz and 1710 – 1755 MHz respectively. + +NOTE 4: TDD base stations deployed in the same geographical area, that are synchronized and use the same or adjacent operating bands can transmit without additional co-existence requirements. For unsynchronized base stations (except in Band 46), special co-existence requirements may apply that are not covered by the 3GPP specifications. + +NOTE 6: For Band 28/n28 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with Band 27 UL operating band. + +NOTE 7: For Band 29 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with UTRA Band XII, E-UTRA Band 12 or NR Band n12 UL operating band, E-UTRA Band 17 UL operating band or E-UTRA Band 85 UL operating band. + +The following requirement may be applied for the protection of PHS. This requirement is also applicable at specified frequencies falling between $\Delta f_{OBUE}$ below the lowest BS transmitter frequency of the *downlink operating band* and $\Delta f_{OBUE}$ above the highest BS transmitter frequency of the *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.1.1-2: AAS BS OTA Spurious emissions limits for BS for co-existence with PHS** + +| Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|---------------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------| +| 1884.5 - 1915.7 MHz | -32 dBm | 300 kHz | Applicable for co-existence with PHS system operating in 1884.5-1915.7 MHz | +| NOTE: The requirement is not applicable in China. | | | | + +The following requirement shall be applied to AAS BS operating in Bands 13 and 14 to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.1.1-3: AAS BS OTA Spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|-------| +| 13 | 763 - 775 MHz | -37 dBm | 6.25 kHz | | +| 13 | 793 - 805 MHz | -37 dBm | 6.25 kHz | | +| 14 | 769 - 775 MHz | -37 dBm | 6.25 kHz | | +| 14 | 799 - 805 MHz | -37 dBm | 6.25 kHz | | + +The following requirement shall be applied to AAS BS operating in Band 26 to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.1.1-4: AAS BS OTA Spurious emissions limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|---------------------------------------------------------| +| 26 | 851 - 859 MHz | -4 dBm | 100 kHz | Applicable for offsets > 37.5 kHz from the channel edge | + +**Table 6.7.6.4.5.1.1-5: Void** + +The following requirement may apply to AAS BS operating in Band 30 in certain regions. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.1.1-6: Additional AAS BS OTA Spurious emissions limits for Band 30** + +| Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|-----------------------|---------------|-----------------------|-------| +| 2200 MHz – 2345 MHz | -33.4 dBm | 1 MHz | | +| 2362.5 MHz – 2365 MHz | -13.4 dBm | 1 MHz | | +| 2365 MHz – 2367.5 MHz | -28.4 dBm | 1 MHz | | +| 2367.5 MHz – 2370 MHz | -30.4 dBm | 1 MHz | | +| 2370 MHz – 2395 MHz | -33.4 dBm | 1 MHz | | + +The following requirement may apply to AAS BS operating in Band 48 in certain regions. The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.1.1-7: Additional AAS BS OTA Spurious emissions limits for Band 48** + +| Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|--------------------------------------------|---------------|-----------------------|--------------------------------------------------| +| 3530 MHz – 3720 MHz | -13 dBm | 1 MHz | Applicable 10 MHz from the assigned channel edge | +| 3100 MHz – 3530 MHz
3720 MHz – 4200 MHz | -28.0 dBm | 1 MHz | | + +In addition to the requirements in clauses in the present clause, the AAS BS may have to comply with the applicable emission limits established by FCC Title 47 [18], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +The following requirement shall be applied to AAS BS operating in Bands 13 and 14 to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the BS *downlink operating band* up to 10 MHz above the highest frequency of the BS *downlink operating band*. + +**Table 6.7.6.4.5.1.1-8: AAS BS OTA Spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|-------| +| 13 | 763 - 775 MHz | -37 dBm | 6.25 kHz | | +| 13 | 793 - 805 MHz | -37 dBm | 6.25 kHz | | +| 14 | 769 - 775 MHz | -37 dBm | 6.25 kHz | | +| 14 | 799 - 805 MHz | -37 dBm | 6.25 kHz | | + +The following requirement shall be applied to AAS BS operating in Band 26 to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.1.1-9: AAS BS OTA Spurious emissions limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|---------------------------------------------------------| +| 26 | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5 kHz from the channel edge | + +The following requirement may apply to BS operating in Band 54 in certain regions, to be used together with other information about the site installation to verify the compliance. + +The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to table 6.7.6.4.5.1.1-10 shall not exceed the maximum TRP limits indicated in the table. + +**Table 6.7.6.4.5.1.1-10: Emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range | Declared emission level (dBW)
(Measurement bandwidth = 1 MHz) | Declared emission level (dBW) of discrete emissions of less than 700 Hz bandwidth
(Measurement bandwidth = 1 kHz) | Declared emission level (dBW) of discrete emissions of less than 2 kHz bandwidth
(Measurement bandwidth = 1 kHz) | +|----------------|-----------------|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| 54 | 1541 - 1559 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | +| | 1559 - 1610 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | +| | 1610 - 1650 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | + +Note: The regional requirements specified in attachment to the FCC reference document, 0007135419, are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in TS 37.105 [6], Annex B1 indicates how the limit in table 6.7.6.4.5.1.1-10 demonstrates compliance to the regional requirement. + +#### 6.7.6.4.5.2 Single RAT UTRA operation + +The TRP of any spurious emission shall not exceed the limits of table 6.7.6.4.5.2-1 for a AAS BS where requirements for co-existence with the system listed in the first column apply. For a *multi-band RIB*, the exclusions and conditions in the notes column of table 6.7.6.4.5.2-1 apply for each supported operating band. + +**Table 6.7.6.4.5.2-1: OTA AAS BS Spurious emissions limits for UTRA FDD BS 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 | Notes | +|-----------------------------------------------------------------|-----------------------------------|---------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | -48.4 dBm | 100 kHz | This requirement does not apply to UTRA FDD operating in band VIII | +| | 876 - 915 MHz | -52.4 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to UTRA FDD operating in band VIII, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| DCS1800 | 1805 - 1880 MHz | -38.4 dBm | 100 kHz | This requirement does not apply to UTRA FDD operating in band III | +| | 1710 - 1785 MHz | -52.4 dBm | 100 kHz | This requirement does not apply to UTRA FDD operating in band III, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| PCS1900 | 1930 - 1990 MHz | -38.4 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band II or band XXV | +| | 1850 - 1910 MHz | -52.4 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band II or band XXV, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| GSM850 or CDMA850 | 869 - 894 MHz | -48.4 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band V or XXVI | +| | 824 - 849 MHz | -52.4 dBm | 100 kHz | This requirement does not apply to UTRA FDD BS operating in frequency band V or XXVI, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band I, | +| | 1920 - 1980 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band I, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band II or band XXV | +| | 1850 - 1910 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band II or band XXV, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III or band IX | +| | 1710 - 1785 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III, since it is already covered by the requirement in clause 6.7.6.5.1.4.
For UTRA BS operating in band IX, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in clause 6.7.6.5.1.4. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band IV or band X | +| | 1710 - 1755 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band IV or band X, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or XXVI | +| | 824 - 849 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or XXVI, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band VI or XIX, E-UTRA Band 6, 18 or 19 or NR Band n18 | 860 - 890 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VI or XIX | +| | 815 - 845 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VI or XIX, since it is already covered by the requirement in clause 6.7.6.5.1.4. | + +| | | | | | +|-----------------------------------------------------|---------------------|-----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 - 2690 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VII, | +| | 2500 - 2570 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VII, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VIII. | +| | 880 - 915 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band VIII, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III or band IX | +| | 1749.9 - 1784.9 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band III or band IX, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band IV or band X. | +| | 1710 - 1770 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band X, since it is already covered by the requirement in clause 6.7.6.5.1.4. For UTRA FDD BS operating in Band IV, it applies for 1755 MHz to 1770 MHz, while the rest is covered in clause 6.7.6.5.1.4. | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 - 1510.9 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI , XXI or XXXII. | +| | 1427.9 - 1447.9 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI, since it is already covered by the requirement in clause 6.7.6.5.1.4. For UTRA BS operating in band XXXII, this requirement applies for carriers allocated within 1475.9 MHz and 1495.9 MHz. | +| | 1447.9 - 1462.9 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXI, since it is already covered by the requirement in clause 6.7.6.5.1.4. For UTRA BS operating in band XXXII, this requirement applies for carriers allocated within 1475.9 MHz and 1495.9 MHz. | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII | +| | 699 - 716 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIII | +| | 777 - 787 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIII, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIV | +| | 788 - 798 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XIV, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| E-UTRA Band 17 | 734 - 746 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII | +| | 704 - 716 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XII, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 791 - 821 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XX | +| | 832 - 862 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XX, since it is already covered by the requirement in clause 6.7.6.5.1.4. | + +| | | | | | +|-----------------------------------------------------|---------------------|-----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 -3590 MHz | -43.0 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXII. | +| | 3410 -3490 MHz | -40.0 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXII, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| | 2010 – 2020 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 24 or NR band n24 | 1525 – 1559 MHz | -43.4 dBm | 1 MHz | | +| | 1626.5 – 1660.5 MHz | -40.4 dBm | 1 MHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 - 1995 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band II or band XXV | +| | 1850 - 1915 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXV, since it is already covered by the requirement in clause 6.7.6.5.1.4. For UTRA FDD BS operating in Band II, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.7.6.5.1.4. | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859-894 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or band XXVI | +| | 814-849 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XXVI, since it is already covered by the requirements in clause 6.7.6.5.1.4 For UTRA FDD BS operating in band V, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.7.6.5.1.4 | +| E-UTRA Band 27 | 852 – 869 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in Band V or XXVI. | +| | 807 – 824 MHz | -40.4 dBm | 1 MHz | For UTRA BS operating in Band XXVI, it applies for 807 MHz to 814 MHz, while the rest is covered in clause 6.7.6.5.1.4. | +| E-UTRA Band 28 or NR band n28 | 758 – 803 MHz | -43.4 dBm | 1 MHz | | +| | 703 – 748 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -43.4 dBm | 1 MHz | | +| E-UTRA Band 30 | 2350 - 2360 MHz | -43.4 dBm | 1 MHz | | +| | 2305 - 2315 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 31 or NR Band n31 | 462.5 -467.5 MHz | -43.4 dBm | 1 MHz | | +| | 452.5 -457.5 MHz | -40.4 dBm | 1 MHz | | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 – 1496 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in Band XI, XXI, or XXXII | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -43.4 dBm | 1 MHz | | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 – 2025 MHz | -43.4 dBm | 1 MHz | | + +| | | | | | +|------------------------------------------------------|-------------------|-----------|-------|-----------------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -43.4 dBm | 1 MHz | | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -43.4 dBm | 1 MHz | | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -43.4 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 MHz | -43.4 dBm | 1 MHz | | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920 MHz | -43.4 dBm | 1 MHz | Applicable in China | +| UTRA TDD in Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400 MHz | -43.4 dBm | 1 MHz | | +| E-UTRA Band 41 or NR band n41 | 2496 - 2690 MHz | -43.4 dBm | 1 MHz | | +| E-UTRA Band 42 | 3400 – 3600 MHz | -43.0 dBm | 1 MHz | | +| E-UTRA Band 43 | 3600 – 3800 MHz | -43.0 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 - 803 MHz | -43.4 dBm | 1 MHz | | +| E-UTRA Band 45 | 1447 - 1467 MHz | -43.4 dBm | 1 MHz | | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 MHz | -42.5 dBm | 1 MHz | | +| E-UTRA Band 47 | 5855 - 5925 MHz | -42.5 dBm | 1 MHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -43.0 dBm | 1 MHz | | +| E-UTRA Band 49 | 3550 – 3700 MHz | -43.0 dBm | 1 MHz | | +| E-UTRA Band 50 or NR Band n50 | 1432 - 1517 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in Band XI | +| E-UTRA Band 51 or NR Band n51 | 1427 - 1432 MHz | -43.4 dBm | 1 MHz | | +| E-UTRA Band 52 | 3300 – 3400 MHz | -43.0 dBm | 1 MHz | | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | -43.0 dBm | 1 MHz | | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -43.4 dBm | 1 MHz | | +| E-UTRA Band 65 or NR band n65 | 2110 - 2200 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in band I. | +| | 1920 - 2010 MHz | -40.4 dBm | 1 MHz | For UTRA BS operating in Band I, it applies for 1980 MHz to 2010 MHz, while the rest is covered in clause 6.7.6.5.1.4 | + +| | | | | | +|-------------------------------|-----------------|-----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 66 or NR band n66 | 2110 - 2200 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in band IV or X. | +| | 1710 - 1780 MHz | -40.4 dBm | 1 MHz | For UTRA BS operating in Band IV, this requirement applies for 1755 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.5.1.4. For UTRA BS operating in Band X, this requirement applies for 1770 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.5.1.4. | +| E-UTRA Band 67 | 738 - 758 MHz | -43.4 dBm | 1 MHz | | +| E-UTRA Band 68 | 753 - 783 MHz | -43.4 dBm | 1 MHz | | +| | 698-728 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 69 | 2570 - 2620 MHz | -43.4 dBm | 1 MHz | | +| E-UTRA Band 70 or NR band n70 | 1995 – 2020 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA BS operating in band II or XXV. | +| | 1695 – 1710 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 71 or NR Band n71 | 617 - 652 MHz | -40.4 dBm | 1 MHz | | +| | 663 – 698 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 MHz | -40.4 dBm | 1 MHz | | +| | 451 - 456 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 73 | 460 - 465 MHz | -40.4 dBm | 1 MHz | | +| | 450 - 455 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 74 or NR band n74 | 1475 – 1518 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI. | +| | 1427 – 1470 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 75 or NR Band n75 | 1432 - 1517 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI. | +| E-UTRA Band 76 or NR Band n76 | 1427 - 1432 MHz | -43.4 dBm | 1 MHz | | +| NR Band n77 | 3300 – 4200 MHz | -43.0 dBm | 1 MHz | | +| NR Band n78 | 3300 – 3800 MHz | -43.0 dBm | 1 MHz | | +| NR Band n79 | 4400 – 5000 MHz | -42.5 dBm | 1 MHz | | +| NR Band n80 | 1710 - 1785 MHz | -40.4 dBm | 1 MHz | For BS operating in band IX. | +| NR Band n81 | 880 - 915 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band VIII | +| NR Band n82 | 832 - 862 MHz | -40.4 dBm | 1 MHz | | +| NR Band n83 | 703 - 748 MHz | -40.4 dBm | 1 MHz | | +| NR Band n84 | 1920 - 1980 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band I | +| E-UTRA Band 85 | 728 - 746 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to BS operating in band XII | +| | 698 - 716 MHz | -40.4 dBm | 1 MHz | | + +| | | | | | +|---------------------------------|---------------------|-----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n86 | 1710 - 1780 MHz | -40.4 dBm | 1 MHz | For BS operating in Band IV, it applies for 1755 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.5.1.4 For BS operating in Band X, it applies for 1770 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.5.1.4 | +| E-UTRA Band 87 | 420 - 425 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 87 or 88. | +| | 410 – 415 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 87, since it is already covered by the requirement in clause 6.7.6.5.1.4 | +| E-UTRA Band 88 | 422 - 427 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 87 or 88. | +| | 412 - 417 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 88, since it is already covered by the requirement in clause 6.7.6.5.1.4. This requirement does not apply to BS operating in band 87. | +| NR Band n89 | 824 - 849 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band V or XXVI, since it is already covered by the requirement in clause 6.7.6.5.1.4. | +| NR Band n91 | 1427 - 1432 MHz | -43.4 dBm | 1 MHz | | +| | 832 - 862 MHz | -40.4 dBm | 1 MHz | | +| NR Band n92 | 1432 - 1517 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI. | +| | 832 - 862 MHz | -40.4 dBm | 1 MHz | | +| NR Band n93 | 1427 - 1432 MHz | -43.4 dBm | 1 MHz | | +| | 880 - 915 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band VIII | +| NR Band n94 | 1432 - 1517 MHz | -43.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI. | +| | 880 - 915 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band VIII | +| NR Band n95 | 2010 – 2025 MHz | -43.4 dBm | 1 MHz | | +| NR band n96 | 5925 – 7125 MHz | -42.5 dBm | 1 MHz | | +| NR Band n97 | 2300 - 2400 MHz | -43.4 dBm | 1 MHz | | +| NR Band n98 | 1880 - 1920 MHz | -43.4 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -40.4 dBm | 1 MHz | | +| NR band n102 | 5925 – 6425 MHz | -42.5 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -43.4 dBm | 1 MHz | | +| | 787 – 788 MHz | -40.4 dBm | 1 MHz | | +| NR Band n104 | 6425 - 7125 MHz | -42.5 dBm | 1 MHz | | +| NR Band n105 | 612 – 652 MHz | -40.4 dBm | 1 MHz | | +| | 663 – 703 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 MHz | -40.4 dBm | 1 MHz | | +| | 896 – 901 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band V or XXVI. | +| NR band n109 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to UTRA FDD BS operating in band XI. | +| | 703 – 733 MHz | -37.4 dBm | 1 MHz | | + +- NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the *downlink operating band* (see clause 6.7.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. + +The following requirement may be applied for the protection of PHS in geographic areas in which both PHS and UTRA FDD are deployed. 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. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.2-2: AAS BS OTA Spurious emissions limits for BS in geographic coverage area of PHS** + +| Band | Maximum Level | Measurement Bandwidth | Notes | +|---------------------|---------------|-----------------------|-------| +| 1884.5 - 1915.7 MHz | -35 dBm | 300 kHz | | + +**Table 6.7.6.4.5.2-3: Void** + +NOTE: This requirement for the frequency range 2610-2615 MHz may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD are deployed. + +The following requirement shall be applied to AAS BS 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. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.2-4: AAS BS OTA Spurious emissions limits** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Notes | +|----------------|---------------|---------------|-----------------------|-------| +| XIII | 763 - 775 MHz | -37.4 dBm | 6.25 kHz | | +| XIII | 793 - 805 MHz | -37.4 dBm | 6.25 kHz | | +| XIV | 769 - 775 MHz | -37.4 dBm | 6.25 kHz | | +| XIV | 799 - 805 MHz | -37.4 dBm | 6.25 kHz | | + +The following requirement shall be applied to AAS BS operating in Bands XXVI to ensure that appropriate interference protection is provided to 800 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. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.2-5: AAS BS OTA Spurious emissions limits** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Notes | +|----------------|---------------|---------------|-----------------------|---------------------------------------------------------| +| XXVI | 851 - 859 MHz | -4.4 dBm | 100 kHz | Applicable for offsets > 37.5 kHz from the channel edge | + +#### 6.7.6.4.5.3 + +#### Single RAT E-UTRA operation + +The TRP of any spurious emission shall not exceed the limits of table 6.7.6.4.5.3-1 for an AAS BS where requirements for co-existence with the system listed in the first column apply. For a *multi-band RIB*, the exclusions and conditions in the notes column of table 6.7.6.4.5.3-1 apply for each supported operating band. + +**Table 6.7.6.4.5.3-1: AAS BS OTA Spurious emissions limits for co-existence with systems operating in other frequency bands** + +| System type to co-exist with | Frequency range for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|-----------------------------------------------------------|----------------------------------------------|---------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | -45.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 8 | +| | 876 - 915 MHz | -49.4 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to BS operating in band 8, since it is already covered by the requirement in clause 6.7.6.5.3.3 | +| DCS1800 (NOTE 3) | 1805 - 1880 MHz | -35.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 3. | +| | 1710 - 1785 MHz | -49.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| PCS1900 | 1930 - 1990 MHz | -35.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 2, 25, band 36 or band 70. | +| | 1850 - 1910 MHz | -49.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 2 or 25, since it is already covered by the requirement in clause 6.7.6.5.3.3. This requirement does not apply to BS operating in band 35. | +| GSM850 or CDMA850 | 869 - 894 MHz | -45.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | +| | 824 - 849 MHz | -49.4 dBm | 100 kHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band . | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 - 2170 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, | +| | 1920 - 1980 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 - 1990 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25 or 70. | +| | 1850 - 1910 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 2 or 25, since it is already covered by the requirement in clause 6.7.6.5.3.3 | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 (NOTE 3) | 1805 - 1880 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9. | +| | 1710 - 1785 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in clause 6.7.6.5.3.3.
For BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in clause 6.7.6.5.3.3. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 - 2155 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66 | +| | 1710 - 1755 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 - 894 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | + +| | | | | | +|---------------------------------------------------------------|---------------------|-----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 824 - 849 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band . | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 18, 19 or NR Band n18 | 860 - 890 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 18, 19 | +| | 815 - 830 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 18 since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| | 830 - 845 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 6, 19, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 - 2690 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 7. | +| | 2500 - 2570 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 7, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 - 960 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8. | +| | 880 - 915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9. | +| | 1749.9 - 1784.9 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3 or 9, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 - 2170 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10 or 66 | +| | 1710 - 1770 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 10 or 66, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 4, it applies for 1755 MHz to 1770 MHz, while the rest is covered in clause 6.7.6.5.3.3. | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 - 1510.9 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21 or 32 | +| | 1427.9 - 1447.9 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 32, this requirement applies for carriers allocated within 1475.9 MHz and 1495.9 MHz. | +| | 1447.9 – 1462.9 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 21, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 32, this requirement applies for carriers allocated within 1475.9 MHz and 1495.9 MHz. | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 - 746 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 12 or 85. | +| | 699 - 716 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 12 or 85, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (NOTE 7) | + +| | | | | | +|-----------------------------------------------------|---------------------|-----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 - 756 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 13. | +| | 777 - 787 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 13, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| UTRA FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 14. | +| | 788 - 798 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 14, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| E-UTRA Band 17 | 734 - 746 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 17. | +| | 704 - 716 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 17, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (NOTE 7) | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 791 - 821 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20 or 28. | +| | 832 - 862 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -40.0 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, 42, 48, n77 or n78.. | +| | 3410 – 3490 MHz | -37.0 dBm | 1 MHz | This requirement does not apply to BS operating in band 22, since it is already covered by the requirement in clause 9.7.3.3. This requirement does not apply to Band 42, 77 or 78. | +| E-UTRA Band 24 or NR band n24 | 1525 – 1559 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 24. | +| | 1626.5 – 1660.5 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 24, since it is already covered by the requirement in clause 6.7.6.5.3.3. | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 - 1995 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 2, 25 or 70. | +| | 1850 - 1915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 25, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.7.6.5.3.3. | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 - 894 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | + +| | | | | | +|---------------------------------------------------|-------------------|-----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 814 - 849 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 26, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 5, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.7.6.5.3.3. For BS operating in Band 27, it applies 3 MHz below the Band 27 downlink operating band . | +| E-UTRA Band 27 | 852 – 869 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in bands 5, 26 or 27. | +| | 807 – 824 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 27, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 26, it applies for 807 MHz to 814 MHz, while the rest is covered in clause 6.7.6.5.3.3. This requirement also applies to BS operating in Band 28, starting 4 MHz above the Band 28 downlink operating band (NOTE 6). | +| E-UTRA Band 28 or NR band n28 | 758 - 803 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, 28, 44, 67 or 68. | +| | 703 - 748 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in clause 6.7.6.5.3.3. This requirement does not apply to BS operating in Band 44. For BS operating in Band 67, it applies for 703-736 MHz. For E-UTRA BS operating in Band 68, it applies for 728 MHz to 733 MHz. | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 29 or 85 | +| E-UTRA Band 30 | 2350 - 2360 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 30 or 40. | +| | 2305 - 2315 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 30, since it is already covered by the requirement in clause 6.7.6.5.3.3. This requirement does not apply to BS operating in Band 40. | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72, 73. | +| | 452.5 – 457.5 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, since it is already covered by the requirement in clause 6.7.6.5.3.3. This requirement does not apply to E-UTRA BS operating in band 72 or 73. | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21 or 32. | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 - 2025 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 35 | + +| | | | | | +|---------------------------------------------------|-------------------|-----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 2, 25 or 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 38 or 69. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or NR band n41 | 2496 – 2690 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 42, 43, 48 | +| E-UTRA Band 44 | 703 - 803 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 - 1467 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 MHz | -39.5 dBm | 1 MHz | | +| E-UTRA Band 47 | 5855 - 5925 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48 | +| E-UTRA Band 49 | 3550 – 3700 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band 22, 42, 43, 48 | +| E-UTRA Band 50 or NR Band n50 | 1432 - 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76 | +| E-UTRA Band 51 or NR Band n51 | 1427 - 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 50, 51, 75 or 76. | +| E-UTRA Band 52 | 3300 – 3400 MHz | -52 dBm | 1 MHz | This is not applicable to E-UTRA BS operating in Band 42 or 52. | +| E-UTRA Band 53 or NR band n53 | 2483.5 – 2495 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 54. | +| E-UTRA Band 65 or NR band n65 | 2110 - 2200 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, | +| | 1920 - 2010 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 65, since it is already covered by the requirement in clause 6.7.6.5.3.3.
For BS operating in Band 1, it applies for 1980 MHz to 2010 MHz, while the rest is covered in clause 6.7.6.5.3.3. | +| E-UTRA Band 66 or NR Band n66 | 2110 - 2200 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 4, 10, 23 or 66. | + +| | | | | | +|-------------------------------|-----------------|-----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 1710 - 1780 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 66, since it is already covered by the requirement in clause 6.7.6.5.3.3. For BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.5.3.3. For BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.5.3.3. | +| E-UTRA Band 67 | 738 – 758 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 28 or 67. | +| E-UTRA Band 68 | 753 - 783 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 28, or 68. | +| | 698 - 728 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 68, since it is already covered by the requirement in clause 9.7.3.3. For E-UTRA BS operating in Band 28, it applies between 698 MHz and 703 MHz, while the rest is covered in clause 9.7.3.3. | +| E-UTRA Band 69 | 2570 - 2620 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in Band 38 or 69. | +| E-UTRA Band 70 or NR Band n70 | 1995 - 2020 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 2, 25 or 70 | +| | 1695 – 1710 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to E-UTRA BS operating in band 70, since it is already covered by the requirement in clause 6.7.6.5.3.3 | +| E-UTRA Band 71 or NR Band n71 | 617 - 652 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 71 or n105. | +| | 663 – 698 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 71/n71 or n105, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 451 - 456 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 72, since it is already covered by the requirement in clause 6.7.6.3.5.3. This requirement does not apply to BS operating in band 73. | +| E-UTRA Band 73 | 460 - 465 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 31, 72 or 73. | +| | 450 - 455 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 73, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| E-UTRA Band 74 or NR band n74 | 1475 – 1518 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 11, 21, 32, 50 74 or 75. | +| | 1427 – 1470 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 74, since it is already covered by the requirement in clause 6.7.6.3.5.3. This requirement does not apply to BS operating in band 32, 45, 50, 51, 75 or 76. | +| E-UTRA Band 75 or NR Band n75 | 1432 - 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76. | +| E-UTRA Band 76 or NR Band n76 | 1427 - 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75 or 76. | +| NR Band n77 | 3300 – 4200 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 42, 43, 48 | + +| | | | | | +|----------------|-----------------|-----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n78 | 3300 – 3800 MHz | -40.0 dBm | 1 MHz | This is not applicable to BS operating in Band 42, 43, 48 | +| NR Band n79 | 4400 – 5000 MHz | -39.5 dBm | 1 MHz | | +| NR Band n80 | 1710 - 1785 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 3, since it is already covered by the requirement in clause 6.7.6.3.5.3.
For BS operating in band 9, it applies for 1710 MHz to 1749.9 MHz and 1784.9 MHz to 1785 MHz, while the rest is covered in clause 6.7.6.3.5.3. | +| NR Band n81 | 880 - 915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| NR Band n82 | 832 - 862 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| NR Band n83 | 703 - 748 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in clause 6.7.6.3.5.3. This requirement does not apply to BS operating in Band 44. For BS operating in Band 67, it applies for 703-736 MHz. For BS operating in Band 68, it applies for 728 MHz to 733 MHz. | +| NR Band n84 | 1920 - 1980 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 1 or 65, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| E-UTRA Band 85 | 728 - 746 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 12, 29 or 85. | +| | 698 - 716 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 85, since it is already covered by the requirement in clause 6.7.6.3.5.3. For BS operating in Band 29, it applies 1 MHz below the Band 29 downlink operating band (Note 7). | +| NR Band n86 | 1710 - 1780 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 66/n66, since it is already covered by the requirement in clause 6.7.6.3.5.3. For BS operating in Band 4, it applies for 1755 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.3.5.3. For BS operating in Band 10, it applies for 1770 MHz to 1780 MHz, while the rest is covered in clause 6.7.6.3.5.3. | +| E-UTRA Band 87 | 420 - 425 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 87 or 88. | +| | 410 – 415 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 87, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| E-UTRA Band 88 | 422 - 427 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 87 or 88. | +| | 412 - 417 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 88, since it is already covered by the requirement in clause 6.7.6.3.5.3. This requirement does not apply to BS operating in band 87. | +| NR Band n89 | 869 - 894 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 5 or 26. This requirement applies to E-UTRA BS operating in Band 27 for the frequency range 879-894 MHz. | + +| | | | | | +|---------------------------------|---------------------|-----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n91 | 1427 - 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75 or 76. | +| | 832 - 862 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| NR Band n92 | 1432 - 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76. | +| | 832 - 862 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 20, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| NR Band n93 | 1427 - 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 50, 51, 75 or 76. | +| | 880 - 915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| NR Band n94 | 1432 - 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76. | +| | 880 - 915 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 8, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| NR Band n95 | 2010 - 2025 MHz | -40.4 dBm | 1 MHz | | +| NR Band n96 | 5925 - 7125 MHz | -39.5 dBm | 1 MHz | | +| NR Band n97 | 2300 - 2400 MHz | -40.4 dBm | 1 MHz | | +| NR Band n98 | 1880 - 1920 MHz | -40.4 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 24, since it is already covered by the requirement in clause 6.7.6.3.5.3. | +| NR Band n102 | 5925 - 6425 MHz | -39.5 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -40.4 dBm | 1 MHz | | +| | 787 – 788 MHz | -37.4 dBm | 1 MHz | | +| NR Band n104 | 6425 - 7125 MHz | -39.5 dBm | 1 MHz | | +| NR Band n105 | 612 – 652 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n71 or n105 | +| | 663 – 703 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in n105, since it is already covered by the requirement in clause 6.6.5.2. | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 106. | +| | 896 – 901 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 106, since it is already covered by the requirement in clause 6.7.6.3.5.3.
This requirement does not apply to BS operating in band 5 or 26. | +| NR band n109 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band 11, 21, 32, 45, 50, 51, 74, 75 or 76. | +| | 703 – 733 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band 28, since it is already covered by the requirement in clause 6.7.6.5.3.3. This requirement does not apply to BS operating in Band 44. For E-UTRA BS operating in Band 68, it applies for 728 MHz to 733 MHz. | + +- NOTE 1: As defined in the scope for spurious emissions in this clause, except for the cases where the noted requirements apply to a BS operating in Band 25, Band 27, Band 28 or Band 29, the co-existence requirements in table 6.7.6.4.5.3-1 do not apply for the $\Delta f_{\text{OBUE}}$ frequency range immediately outside the *downlink operating band* (see clause 6.7.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. +- NOTE 2: Table 6.7.6.4.5.3-1 assumes that two operating bands, where the frequency ranges in clause 4.7 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 3: For the protection of DCS1800, UTRA Band III or E-UTRA Band 3 in China, the frequency ranges of the downlink and uplink protection requirements are 1805 – 1850 MHz and 1710 – 1755 MHz respectively. +- NOTE 4: TDD base stations deployed in the same geographical area, that are synchronized and use the same or adjacent operating bands can transmit without additional co-existence requirements. For unsynchronized base stations (except in Band 46), special co-existence requirements may apply that are not covered by the 3GPP specifications. +- NOTE 6: For Band 28 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with Band 27 UL operating band. +- NOTE 7: For Band 29 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with UTRA Band XII or E-UTRA Band 12 UL operating band, E-UTRA Band 17 UL operating band or E-UTRA Band 85 UL operating band. + +The following requirement may be applied for the protection of PHS. This requirement is also applicable at specified frequencies falling between $\Delta f_{\text{OBUE}}$ below the lowest BS transmitter frequency of the *downlink operating band* and $\Delta f_{\text{OBUE}}$ above the highest BS transmitter frequency of the *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.3-2: AAS BS OTA Spurious emissions limits for BS for co-existence with PHS** + +| Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|---------------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------| +| 1884.5 - 1915.7 MHz | -32 dBm | 300 kHz | Applicable for co-existence with PHS system operating in 1884.5-1915.7 MHz | +| NOTE: The requirement is not applicable in China. | | | | + +The following requirement shall be applied to AAS BS operating in Bands 13 and 14 to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.3-3: AAS BS OTA Spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|-------| +| 13 | 763 - 775 MHz | -37 dBm | 6.25 kHz | | +| 13 | 793 - 805 MHz | -37 dBm | 6.25 kHz | | +| 14 | 769 - 775 MHz | -37 dBm | 6.25 kHz | | +| 14 | 799 - 805 MHz | -37 dBm | 6.25 kHz | | + +The following requirement shall be applied to AAS BS operating in Band 26 to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.3-4: AAS BS OTA Spurious emissions limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|---------------------------------------------------------| +| 26 | 851 - 859 MHz | -4 dBm | 100 kHz | Applicable for offsets > 37.5 kHz from the channel edge | + +**Table 6.7.6.4.5.3-5: Void** + +The following requirement may apply to AAS BS operating in Band 30 in certain regions. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.3-6: Additional AAS BS OTA Spurious emissions limits for Band 30** + +| Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|-----------------------|---------------|-----------------------|-------| +| 2200 MHz – 2345 MHz | -33.4 dBm | 1 MHz | | +| 2362.5 MHz – 2365 MHz | -13.4 dBm | 1 MHz | | +| 2365 MHz – 2367.5 MHz | -28.4 dBm | 1 MHz | | +| 2367.5 MHz – 2370 MHz | -30.4 dBm | 1 MHz | | +| 2370 MHz – 2395 MHz | -33.4 dBm | 1 MHz | | + +The following requirement may apply to AAS BS operating in Band 48 in certain regions. The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.3-7: Additional AAS BS OTA Spurious emissions limits for Band 48** + +| Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|--------------------------------------------|---------------|-----------------------|--------------------------------------------------| +| 3530 MHz – 3720 MHz | -13 dBm | 1 MHz | Applicable 10 MHz from the assigned channel edge | +| 3100 MHz – 3530 MHz
3720 MHz – 4200 MHz | -28.0 dBm | 1 MHz | | + +In addition to the requirements in clauses 6.7.6.5.3.1, 6.7.6.5.3.2, 6.7.6.5.3.3 and above in the present clause, the AAS BS may have to comply with the applicable emission limits established by FCC Title 47 [18], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +**Table 6.7.6.4.5.3-8: Void** + +The following requirement shall be applied to AAS BS operating in Bands 13 and 14 to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the BS *downlink operating band* up to 10 MHz above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.3-9: AAS BS OTA Spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|-------| +| 13 | 763 - 775 MHz | -37 dBm | 6.25 kHz | | +| 13 | 793 - 805 MHz | -37 dBm | 6.25 kHz | | +| 14 | 769 - 775 MHz | -37 dBm | 6.25 kHz | | +| 14 | 799 - 805 MHz | -37 dBm | 6.25 kHz | | + +The following requirement shall be applied to AAS BS operating in Band 26 to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS *downlink operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS *downlink operating band*. + +The TRP of any spurious emission shall not exceed: + +**Table 6.7.6.4.5.3-10: AAS BS OTA Spurious emissions limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Notes | +|----------------|-----------------|---------------|-----------------------|---------------------------------------------------------| +| 26 | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5 kHz from the channel edge | + +The following requirement may apply to BS operating in Band 54 in certain regions, to be used together with other information about the site installation to verify the compliance. + +The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to table 6.7.6.4.5.3-11 shall not exceed the maximum TRP limits indicated in the table. + +**Table 6.7.6.4.5.3-11: Emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range | Declared emission level (dBW) (Measurement bandwidth = 1 MHz) | Declared emission level (dBW) of discrete emissions of less than 700 Hz bandwidth (Measurement bandwidth = 1 kHz) | Declared emission level (dBW) of discrete emissions of less than 2 kHz bandwidth (Measurement bandwidth = 1 kHz) | +|----------------|-----------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| 54 | 1541 - 1559 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | +| | 1559 - 1610 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | +| | 1610 - 1650 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | + +Note: The regional requirements specified in attachment to the FCC reference document, 0007135419, are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The method outlined in TS 37.105 [6], Annex B1 indicates how the limit in table 6.7.6.4.5.3-11 demonstrates compliance to the regional requirement. + +## 6.7.6.5 Co-location with other base stations + +### 6.7.6.5.1 Definition and applicability + +### 6.7.6.5.2 Minimum Requirement + +The minimum requirement for AAS BS in *MSR operation* is defined in TS 37.105 [6], clause 9.7.6.2. + +The minimum requirement for AAS BS in *single RAT UTRA operation* is defined in TS 37.105 [6], clause 9.7.6.3. + +The minimum requirement for AAS BS in *single RAT E-UTRA operation* is defined in TS 37.105 [6], clause 9.7.6.4. + +#### 6.7.6.5.3 Test purpose + +The test purpose of OTA spurious emission is to verify the radiated spurious emissions from the AAS BS at the *RIB* are within specified requirements. + +For OTA co-location spurious emission, the test purpose is to verify that the emission is within the specified requirement limits at the CLTA conducted output(s). + +#### 6.7.6.5.4 Method of test + +##### 6.7.6.5.4.1 Initial conditions + +See clause 6.7.6.3.4.1. + +##### 6.7.6.5.4.2 Procedure + +See clause 6.7.6.3.4.2. + +#### 6.7.6.5.5 Test Requirement + +##### 6.7.6.5.5.1 MSR operation + +These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA and/or NR BS are co-located with a BS. + +The requirements assume with base stations of the same class. + +NOTE: For co-location with UTRA, the requirements are based on co-location with UTRA FDD or TDD base stations. + +The requirements are co-location emission requirements are specified as the power sum of the supported polarization(s) at the CLTA conducted output(s). + +The output of the CLTA of any spurious emission shall not exceed the limits of table 6.7.6.5.5.1-1 for a AAS BS where requirements for co-location with a BS type listed in the first column apply, depending on the declared Base Station class. For a *multi-band RIB*, the exclusions and conditions in the notes column of table 6.7.6.5.5.1-1 apply for each supported operating band. + +**Table 6.7.6.5.5.1-1: AAS BS OTA Spurious emissions E-UTRA limits for AAS BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Bandwidth | Note | +|-----------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|-----------------------|---------------------------------------------------------------------------------------------------| +| GSM900 | 876-915 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| DCS1800 | 1710 - 1785 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| PCS1900 | 1850 - 1910 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 - 849 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 1920 - 1980 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1850 - 1910 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 | 1710 - 1785 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 824 - 849 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 - 845 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2500 - 2570 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 880 - 915 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1447.9 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 50/n50, 51/n51, 75/n75, 76/n76, n91, n92, n93, n94 | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 699 - 716 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 777 - 787 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | + +| | | | | | | | +|-----------------------------------------------------|---------------------|------------|------------|------------|---------|-----------------------------------------------------------------------------| +| UTRA FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 - 716 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 18 or NR Band n18 | 815 - 830 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 832 - 862 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 32, 50/n50, 75/n75, n92, n94 | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 – 3490 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42, n77 or n78 | +| E-UTRA Band 24 or NR band n24 | 1626.5 – 1660.5 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR Band n25 | 1850 - 1915 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 814 - 849 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 27 | 807 - 824 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 28 or NR Band n28 | 703 – 748 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | +| E-UTRA Band 30 | 2305 - 2315 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 40/n40 | +| E-UTRA Band 31 or NR Band n31 | 452.5 – 457.5 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR Band n34 | 2010 - 2025 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 34/n34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 2, n2 and 36 | + +| | | | | | | | +|---------------------------------------------------|-----------------|------------|------------|------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570 – 2620 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 38/n38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR Band n39 | 1880 – 1920 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 33 and 39/n39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 30 or 40/n40 | +| E-UTRA Band 41 or NR Band n41 | 2496 – 2690 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 41/n41 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48/n48, 52, n77 or n78 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48/n48, n77 or n78 | +| E-UTRA Band 44 | 703 – 803 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 28/n28 or 44 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -108.6 dBm | -105.6 dBm | 100 kHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48/n48, n77 or n78 | +| E-UTRA Band 49 | 3550 – 3700 MHz | N/A | N/A | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48/n48, n77 or n78 | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 11, 21, 32, 51, n51, 74, 75/n75, 76/n76, n91, n92, n93, n94 | + +| | | | | | | | +|----------------------------------------------|---------------------|------------|------------|------------|---------|-------------------------------------------------------------------------------------------| +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 50/n50, 75/n75, 76/n76, n91, n92, n93, n94 | +| E-UTRA Band 52 | 3300 – 3400 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42 or 52 | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | N/A | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 41/n41 or 53/n53 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 65 or NR band n65 | 1920 - 2010 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 66 or NR Band n66 | 1710 – 1780 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 68 | 698 – 728 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 70 or NR Band n70 or NR band n70 | 1695 – 1710 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 71 or NR Band n71 | 663 – 698 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 72 or NR Band n72 | 451 – 456 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 73 | 450 – 455 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 74 or NR band n74 | 1427 – 1470 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 50/n50, 51/n51, n91, n92, n93, n94 | +| NR Band n77 | 3300 MHz – 4200 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48/n48, 52, n77 or n78 | +| NR Band n78 | 3300 MHz – 3800 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48/n48, 52, n77 or n78 | +| NR band n79 | 4400 MHz – 5000 MHz | -113.6 dBm | -108.6 dBm | -105.6 dBm | 100 kHz | | +| NR band n80 | 1710 MHz – 1785 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n81 | 880 MHz – 915 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n82 | 832 MHz – 862 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n83 | 703 MHz – 748 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n84 | 1920 MHz – 1980 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | + +| | | | | | | | +|---------------------------------|---------------------|------------|------------|------------|---------|---------------------------------------------------| +| E-UTRA Band 85 or NR band n85 | 698 - 716 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n86 | 1710 MHz – 1780 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 87 | 420 – 425 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 88 | 422 – 427 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n89 | 824 - 849 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n91 | 832 MHz – 862 MHz | N/A | N/A | -105.9 dBm | 100 kHz | | +| NR band n92 | 832 MHz – 862 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n93 | 880 MHz – 915 MHz | N/A | N/A | -105.9 dBm | 100 kHz | | +| NR band n94 | 880 MHz – 915 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n95 | 2010 - 2025 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n96 | 5925 - 7125 MHz | N/A | -107.6 dBm | -104.6 dBm | 100 kHz | | +| NR band n97 | 2300 - 2400 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n98 | 1880 - 1920 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n99 | 1626.5 – 1660.5 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n102 | 5925 - 6425 MHz | N/A | -107.6 dBm | -104.6 dBm | 100 kHz | | +| E-UTRA Band 103 | 787 – 788 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n104 | 6425 - 7125 MHz | -112.6 dBm | -107.6 dBm | -104.6 dBm | 100 kHz | | +| NR Band n105 | 663 – 703 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 106 or NR Band n106 | 896 – 901 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n109 | 703 – 733 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | + +NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in table 6.7.6.5.3.5-1 do not apply for the $\Delta f_{\text{OBUE}}$ frequency range immediately outside the BS transmit frequency range of a *downlink operating band* (see clause 6.7.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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [31]. + +NOTE 2: Table 6.7.6.5.3.5-1 assumes that two operating bands, where the corresponding BS transmit and receive frequency ranges in clause 4.6 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 3: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can transmit without special co-locations requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +#### 6.7.6.5.5.2 Single RAT UTRA operation + +These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD and/or E-UTRA BS are co-located with a BS. + +The requirements assume with base stations of the same class. + +NOTE: For co-location with UTRA, the requirements are based on co-location with UTRA FDD or TDD base stations. + +The requirements are co-location emission requirements and specified as the power sum of the supported polarization(s) at the CLTA conducted output(s). + +The power sum of any spurious emission is specified over all supported polarizations at the conducted output(s) of the CLTA and shall not exceed the limits of table 6.7.6.5.5.2-1 for a AAS BS where requirements for co-location with a BS type listed in the first column apply, depending on the declared Base Station class. For a *multi-band RIB*, the exclusions and conditions in the Notes column of table 6.7.6.5.5.2-1 apply for each supported operating band. + +**Table 6.7.6.5.5.2-1: UTRA AAS BS OTA Spurious emissions limits for AAS BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|---------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|-------| +| GSM900 | 876-915 MHz | -118.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| DCS1800 | 1710 - 1785 MHz | -118.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| PCS1900 | 1850 - 1910 MHz | -118.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 - 849 MHz | -118.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 1920 - 1980 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1850 - 1910 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1710 - 1785 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 824 - 849 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 - 845 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2500 - 2570 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 880 - 915 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1447.9 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | + +| | | | | | | | +|-----------------------------------------------------|---------------------|------------|------------|------------|---------|---------------------------------------------------| +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 699 - 716 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 777 - 787 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 - 716 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 18 or NR Band n18 | 815 - 830 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 832 - 862 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 – 3490 MHz | -116.7 dBm | -111.7 dBm | -108.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42 | +| E-UTRA Band 24 or NR band n24 | 1626.5 – 1660.5 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1850 - 1915 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 814 - 849 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 27 | 807 - 824 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 28 or NR band n28 | 703 – 748 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | +| E-UTRA Band 30 | 2305 - 2315 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 40 | +| E-UTRA Band 31 or NR Band n31 | 452.5 – 457.5 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 33 | + +| | | | | | | | +|---------------------------------------------------|-----------------|------------|------------|------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 - 2025 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 2 and 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 33 and 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or NR band n41 | 2496 – 2690 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -116.7 dBm | -111.7 dBm | -108.7 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42 or 43 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -116.7 dBm | -111.7 dBm | -108.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42 or 43 | +| E-UTRA Band 44 | 703 – 803 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 45 | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -111.6 dBm | -108.6 dBm | 100 kHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | | +| E-UTRA Band 49 | 3550 – 3700 MHz | N/A | N/A | -105.7 dBm | 100 kHz | | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band XI | + +| | | | | | | | +|-------------------------------|---------------------|------------|------------|------------|---------|---------------------------------------------------------| +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -105.9 dBm | 100 kHz | | +| E-UTRA Band 52 | 3300 – 3400 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 53 or NR band n53 | 2483.5 – 2495 MHz | N/A | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 65 or NR band n65 | 1920 - 2010 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 66 or NR band n66 | 1710 – 1780 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 68 | 698 – 728 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 70 or NR band n70 | 1695 – 1710 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 71 or NR Band n71 | 663 – 698 MHz | -116.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 72 or NR Band n72 | 451 – 456 MHz | -116.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 73 | 450 – 455 MHz | -116.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 74 or NR band n74 | 1427 – 1470 MHz | -116.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n77 | 3300 MHz – 4200 MHz | -116.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | | +| NR Band n78 | 3300 MHz – 3800 MHz | -116.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | | +| NR band n79 | 4400 MHz – 5000 MHz | -116.6 dBm | -108.6 dBm | -105.6 dBm | 100 kHz | | +| NR band n80 | 1710 – 1785 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n81 | 880 – 915 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n82 | 832 – 862 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n83 | 703 – 748 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n84 | 1920 – 1980 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 85 or NR band n85 | 698 – 716 MHz | -116.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n86 | 1710 -1780 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | + +| | | | | | | | +|---------------------------------|---------------------|------------|------------|------------|---------|---------------------------------------------------| +| E-UTRA Band 87 | 410 – 415 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| E-UTRA Band 88 | 412 – 417 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n89 | 824 – 849 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n91 | 832 – 862 MHz | N/A | N/A | -108.9 dBm | 100 kHz | | +| NR band n92 | 832 – 862 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n93 | 880 – 915 MHz | N/A | N/A | -108.9 dBm | 100 kHz | | +| NR band n94 | 880 – 915 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n95 | 2010 – 2025 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR Band n96 | 5925 – 7125 MHz | N/A | -110.6 dBm | -107.6 dBm | 100 kHz | | +| NR band n97 | 2300 – 2400 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n98 | 1880 – 1920 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR band n99 | 1626.5 – 1660.5 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR Band n102 | 5925 – 6425 MHz | N/A | -110.6 dBm | -107.6 dBm | 100 kHz | | +| E-UTRA Band 103 | 787 – 788 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR Band n104 | 6425 – 7125 MHz | -115.6 dBm | -110.6 dBm | -107.6 dBm | 100 kHz | | +| NR Band n105 | 663 – 703 MHz | -116.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 106 or NR Band n106 | 896 – 901 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | | +| NR Band n109 | 703 – 733 MHz | -116.9 dBm | -111.9 dBm | -108.9 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | + +NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in table 6.7.6.5.2.5-1 do not apply for the 10 MHz frequency range immediately outside the BS transmit frequency range of a *downlink operating band* (see clause 6.7.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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [31]. + +NOTE 2: Table 6.7.6.5.2.5-1 assumes that two operating bands, where the corresponding BS transmit and receive frequency ranges in clause 4.6 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 3: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can transmit without special co-locations requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +#### 6.7.6.5.5.3 Single RAT E-UTRA operation + +These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD and/or E-UTRA BS are co-located with a BS. + +The requirements assume co-location with base stations of the same class. + +NOTE: For co-location with UTRA, the requirements are based on co-location with UTRA FDD or TDD base stations. + +The requirements are co-location emission requirements and specified as the power sum of the supported polarization(s) at the CLTA conducted output(s). + +The power sum of any spurious emission is specified over all supported polarizations at the conducted output(s) of the CLTA and shall not exceed the limits of table 6.7.6.5.5.3-1 for a AAS BS where requirements for co-location with a BS type listed in the first column apply, depending on the declared Base Station class. For a *multi-band RIB*, the exclusions and conditions in the notes column of table 6.7.6.5.5.3-1 apply for each supported operating band. + +**Table 6.7.6.5.5.3-1: AAS BS OTA Spurious emissions E-UTRA limits for AAS BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|---------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|-------| +| GSM900 | 876-915 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| DCS1800 | 1710 - 1785 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| PCS1900 | 1850 - 1910 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 - 849 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 1920 - 1980 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1850 - 1910 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1710 - 1785 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 - 1755 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 824 - 849 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 - 845 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2500 - 2570 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 880 - 915 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 - 1784.9 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 - 1770 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 - 1447.9 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|-----------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|---------------------------------------------------| +| GSM900 | 876-915 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 699 - 716 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 777 - 787 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 - 716 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 18 or NR Band n18 | 815 - 830 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 832 - 862 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 – 3490 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42 | +| E-UTRA Band 24 or NR band n24 | 1626.5 – 1660.5 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1850 - 1915 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 814 - 849 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 27 | 807 - 824 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 28 or NR band n28 | 703 – 748 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | +| E-UTRA Band 30 | 2305 - 2315 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 40 | + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|---------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 876-915 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 31 or NR Band n31 | 452.5 – 457.5 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 33 | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 - 2025 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 35 | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 - 1990 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 2 and 36 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 - 1930 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 37. This unpaired band is defined in ITU-R M.1036, but is pending any future deployment. | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 33 and 39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 30 or 40 | +| E-UTRA Band 41 or NR band n41 | 2496 – 2690 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42 or 43 | +| E-UTRA Band 44 | 703 – 803 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 28 or 44 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 45 | + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|-------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|------------------------------------------------------------------------| +| GSM900 | 876-915 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -108.6 dBm | -105.6 dBm | 100 kHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48 | +| E-UTRA Band 49 | 3550 – 3700 MHz | N/A | N/A | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42, 43, 48 | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 11, 21, 32, 51, n51, 74 | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 50 | +| E-UTRA Band 52 | 3300 – 3400 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 42 or 52 | +| E-UTRA Band 53 or NR band n53 | 2483.5 – 2495 MHz | N/A | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 41 or 53 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 65 or NR band n65 | 1920 - 2010 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 66 | 1710 – 1780 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 68 | 698 – 728 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 70 | 1695 – 1710 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 71 or NR Band n71 | 663 – 698 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 72 or NR Band n72 | 451 – 456 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 73 | 450 – 455 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 74 or NR band n74 | 1427 – 1470 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 50, 51 | +| NR Band n77 | 3300 MHz – 4200 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52 | +| NR Band n78 | 3300 MHz – 3800 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band 22, 42, 43, 48, 52 | + +| Type of co-located BS | Frequency range for co-location requirement | Maximum Level (WA-BS) | Maximum Level (MR-BS) | Maximum Level (LA-BS) | Measurement Band width | Notes | +|---------------------------------|---------------------------------------------|-----------------------|-----------------------|-----------------------|------------------------|---------------------------------------------------| +| GSM900 | 876-915 MHz | -115.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n79 | 4400 – 5000 MHz | -113.6 dBm | -108.6 dBm | -105.6 dBm | 100 kHz | | +| NR band n80 | 1710 – 1785 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n81 | 880 – 915 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n82 | 832 – 862 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n83 | 703 – 748 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n84 | 1920 – 1980 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 85 or NR band n85 | 698 - 716 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n86 | 1710 - 1780 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 87 | 410 – 415 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 88 | 412 – 417 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n89 | 824 - 849 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n91 | 832 – 862 MHz | N/A | N/A | -105.9 dBm | 100 kHz | | +| NR band n92 | 832 – 862 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n93 | 880 – 915 MHz | N/A | N/A | -105.9 dBm | 100 kHz | | +| NR band n94 | 880 – 915 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n95 | 2010 - 2025 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n96 | 5925 - 7125 MHz | N/A | -107.6 dBm | -104.6 dBm | 100 kHz | | +| NR band n97 | 2300 - 2400 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n98 | 1880 - 1920 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n99 | 1626.5 – 1660.5 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n102 | 5925 - 6425 MHz | N/A | -107.6 dBm | -104.6 dBm | 100 kHz | | +| E-UTRA Band 103 | 787 – 788 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n104 | 6425 - 7125 MHz | -112.6 dBm | -107.6 dBm | -104.6 dBm | 100 kHz | | +| NR Band n105 | 663 – 703 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 106 or NR Band n106 | 896 – 901 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n109 | 703 – 733 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band 44 | + +- NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in table 6.7.6.5.3.5-1 do not apply for the $\Delta f_{\text{OBUE}}$ frequency range immediately outside the BS transmit frequency range of a *downlink operating band* (see clause 6.7.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 BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [31]. +- NOTE 2: Table 6.7.6.5.3.5-1 assumes that two operating bands, where the corresponding BS transmit and receive frequency ranges in clause 4.6 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 3: Co-located TDD base stations that are synchronized and using the same or adjacent operating band can transmit without special co-locations requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +## 6.8 OTA Transmitter intermodulation + +### 6.8.1 Definition and applicability + +The OTA transmitter intermodulation requirement is a measure of the capability of the transmitter unit to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter unit via the RDN and antenna array from a co-located base station. The requirement applies during the *transmitter ON period* and the *transmitter transient period*. + +The requirement applies at each RIB supporting transmission in the operating band. + +The transmitter intermodulation level is the *total radiated power* of the intermodulation products when an interfering signal is injected into the CLTA. + +For *OTA AAS BS*, the transmitter intermodulation requirement is captured by the co-location transmitter intermodulation scenario case, in which the interfering signal is injected into the CLTA. + +### 6.8.2 Minimum Requirement + +The minimum requirement for AAS BS in *MSR operation* is defined in TS 37.105 [6], clause 9.8.2. + +The minimum requirement for AAS BS in *single RAT UTRA operation* is defined in TS 37.105 [6], clause 9.8.3. + +The minimum requirement for AAS BS in *single RAT E-UTRA operation* is defined in TS 37.105 [6], clause 9.8.4. + +### 6.8.3 Test purpose + +The test purpose is to verify the ability of the transmitter units associated with the *RIB* under test to restrict the generation of intermodulation products in its nonlinear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter unit via the RDN and antenna array from a co-located base station to below specified levels. + +### 6.8.4 Method of test + +#### 6.8.4.1 Initial conditions + +Test environment: + +- normal; see annex G.2. + +RF channels to be tested for single carrier: + +- M; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $M_{\text{RFBW}}$ in *single-band RIB*, see clause 4.12.1; $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in *multi-band RIB*, see clause 4.12.1. + +In addition, for *multi-band RIB*: + +- For $B_{\text{RFBW\_T}}$ , emission testing above the highest operating band may be omitted. +- For $B'_{\text{RFBW\_T}}$ , emission testing below the lowest operating band may be omitted. +- FFS + +Directions to be tested for: + +As the requirement is based on TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see annex F). + +## 6.8.4.2 Procedure + +- 1) Select a CLTA according to parameters given in Table 4.15.2.2-1. +- 2) Place the CLTA according to parameters given in Table 4.15.2.3-1. +- 3) The test antenna(s) shall be dual (or single) polarized covering the same frequency range as the *AAS BS* and the emission frequencies. +- 4) Several test antennas are required to cover both the *AAS BS* and the whole emission frequency range. +- 5) Connect the test antenna and CLTA to the measurement equipment as shown in Annex D1.5, Figures D.1.5-1. +- 6) During the OTA emission measurements at the test antenna conducted output(s), both *AAS BS* and CLTA are rotated around same axis. +- 7) The OTA unwanted emissions measurement method shall be TRP, according to the procedure described in Annex F. +- 8) The measurement device (signal analyzer) characteristics shall be: + - Detection mode: True RMS. + - The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. +- 9) Set the *AAS BS* to transmit: + - a) For MSR: + - Set the *AAS BS* to transmit maximum power according to the applicable test configuration in clause 5 using the corresponding test models or set of physical channels in clause 4.11. + - b) For UTRA FDD: + - For a *AAS BS* declared to be capable of single carrier operation only, set the *AAS BS* to transmit maximum power according to TM1, clause 4.12.2, at the manufacturer's declared rated carrier TRP, $P_{\text{rated,c,TRP}}$ . + - For a *AAS BS* declared to be capable of multi-carrier operation, set the *AAS BS* to transmit maximum power according to TM1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + - c) For E-UTRA: + - For *AAS BS* declared to be capable of single carrier operation only, set the *AAS BS* to transmit maximum power according to E-TM1.1 in clause 4.12.2, at manufacturer's declared rated carrier TRP, $P_{\text{rated,c,TRP}}$ . + +- For a *AAS BS* declared to be capable of multi-carrier and/or CA operation, set the *AAS BS* to transmit maximum power according to E-TM1.1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.11. + +10) Generate the interfering signal: + +a) For MSR: + +- using E-TM1.1 as defined in clause 4.12.2, with 5 MHz channel bandwidth, at a centre frequency offset according to the conditions in table 6.8.5.1.1-1, but exclude interfering frequencies that are outside of the allocated downlink operating band or interfering frequencies that are not completely within the sub-block gap or within the *Inter RF Bandwidth gap*. + +b) For UTRA FDD: + +- in accordance to TM1, clause 4.12.2 with a frequency offset according to the conditions of table 6.8.5.2.1-1, but exclude interfering signal frequencies that are outside of the allocated downlink operating band or interfering signal frequencies that are not completely within the sub-block gap or within the *Inter RF Bandwidth gap*. + +c) For E-UTRA: + +- according to E-TM1.1, as defined in clause 4.12.2, with 5 MHz channel bandwidth and a centre frequency offset according to the conditions of table 6.8.5.3.1-1, but exclude interfering frequencies that are outside of the allocated downlink operating band or interfering frequencies that are not completely within the sub-block gap or within the *Inter RF Bandwidth gap*. + +11) Connect the interfering signal to the CLTA input interfaces, equally dividing the power among supported polarizations. Adjust the interfering signal level at the CLTA conducted input(s) as defined in: + +a) For MSR: + +- i. General co-location table 6.8.5.1.1-1. +- ii. Additional co-location (BC1 and BC2) table 6.8.5.1.2-1. +- iii. Additional co-location (BC3) table 6.8.5.1.3-1. + +b) For UTRA FDD: + +- i. General co-location table 6.8.5.2.1-1 . + +c) For E-UTRA: + +- i. General co-location table 6.8.5.3.1-1. +- ii. Void + +12) If the interfering signal is applicable according to clause 5, perform the unwanted emission tests specified in clauses 6.7.3 (OTA ACLR), 6.7.4 (OTA spectrum mask) and 6.7.5 (OTA OBUE), for all third and fifth order intermodulation products which appear in the frequency ranges defined in clauses 6.7.3, 6.7.4 and 6.7.5 (NOTE 2). The width of the intermodulation products shall be taken into account. + +13) If the interfering signal is applicable according to clause 5, perform the transmitter spurious emissions test as specified in clause 6.7.6 (OTA spurious emission), except OTA co-location spurious emission, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clause 6.7.6 (NOTE 2). The width of the intermodulation products shall be taken into account. + +14) Verify that the emission level does not exceed the required level in clause 6.8.5 (Test requirements) with the exception of interfering signal frequencies. + +15) Repeat the test for the remaining interfering signal centre frequency offsets according to the conditions of: + +a) For MSR: + +- i. General co-location table 6.8.5.1.1-1. + +- ii. Additional co-location (BC1 and BC2) table 6.8.5.1.2-1. + - iii. Additional co-location (BC3) table 6.8.5.1.3-1. +- b) For UTRA FDD: +- i. General co-location table 6.8.5.2.1-1 . +- c) For E-UTRA: +- i. General co-location table 6.8.5.3.1-1. + - ii. Void +- 16) Repeat the test for the remaining interfering signals defined in clause 5 for requirements 6.7.3 (OTA ACLR), 6.7.4 (OTA spectrum mask), 6.7.5 (OTA OBUE) and 6.7.6 (OTA spurious emission), except OTA co-location spurious emission. + +In addition, for *multi-band AAS BS*, the following steps shall apply: + +- 17) For *multi-band AAS BS* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +NOTE 1: The third order intermodulation products are centred at $2F1 \pm F2$ and $2F2 \pm F1$ . The fifth order intermodulation products are centred at $3F1 \pm 2F2$ , $3F2 \pm 2F1$ , $4F1 \pm F2$ , and $4F2 \pm F1$ where F1 represents the test signal centre frequency or centre frequency of each sub-block and F2 represents the interfering signal centre frequency. The widths of intermodulation products are: + +- $(n * BW_{F1} + m * BW_{F2})$ for the $nF1 \pm mF2$ products; +- $(n * BW_{F2} + m * BW_{F1})$ for the $nF2 \pm mF1$ products; + +where $BW_{F1}$ represents the test signal RF bandwidth or channel bandwidth in case of single carrier, or sub-block bandwidth, and $BW_{F2}$ represents the interfering signal bandwidth. + +NOTE 2: During the conformance test the interfering signal can be applied on one side of the wanted signal, while the transmitter intermodulation emission is measured only on the opposite side of the wanted signal. This applies for intermodulation products which are within the operating band or OBUE region. + +## 6.8.5 Test Requirement + +### 6.8.5.1 MSR test requirements + +#### 6.8.5.1.1 General test requirement + +In the frequency range relevant for this test the transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in clause 6.7.6 (except co-location spurious emission), operating band unwanted emission in clause 6.7.5 and ACLR in clause 6.7.3 in the presence of a wanted signal and an interfering signal according to table 6.8.5.1.1-1 for an *OTA AAS BS* operating in BC1, BC2 and BC3. + +The requirement is applicable outside the edges of the *Base Station RF Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *radio bandwidth edges*. + +For *RIB* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block edges*. + +For *multi-band RIBs*, the requirement applies relative to the *Base Station RF Bandwidth edges* of each operating band. In case the inter *Base Station RF Bandwidth* gap is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth* gap. + +**Table 6.8.5.1.1-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA or NR signal | +| Interfering signal type | E-UTRA signal of channel bandwidth 5 MHz | +| Interfering signal power level applied to the CLTA | min(46 dBm, $P_{\text{rated,t,TRP}}$ ) | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or edge of sub-block inside a gap | ±2.5 MHz
±7.5 MHz
±12.5 MHz | +| NOTE 1: | Interfering signal positions that are partially or completely outside of any downlink operating band of the RIB is excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band , TS 37.141 provides further guidance regarding appropriate test requirements. | +| NOTE 2: | In certain regions, NOTE 1 is not applied in Band 1, 3, 8, 9, 11, 18, 19, 21, 28, 32 operating within 1 475.9 MHz to 1 495.9 MHz, 34. | +| NOTE 3: | For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the CLTA. | + +#### 6.8.5.1.2 Additional test requirement (BC1 and BC2) + +In the frequency range relevant for this test the transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in clause 6.7.6 (except co-location spurious emission), operating band unwanted emission in clause 6.7.5 and ACLR in clause 6.7.3 in the presence of a wanted signal and an interfering signal according to table 6.8.5.1.2-1 for an *OTA AAS BS* operating in BC2. + +The requirement is applicable outside the edges of the *Base Station RF Bandwidth* for BC2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth* edges. + +For *RIBs* supporting operation in *non-contiguous spectrum* in BC1 or BC2, the requirement is also applicable inside a *sub-block gap* with a gap size larger than or equal to two times the interfering signal centre frequency offset. For *RIBs* supporting operation in *non-contiguous spectrum* in BC1, the requirement is not applicable inside a *sub-block gap* with a gap size equal to or larger than 5 MHz. The interfering signal offset is defined relative to the *sub-block* edges. + +For *multi-band RIBs*, the requirement applies relative to the *Base Station RF Bandwidth* edges of a BC2 operating band. The requirement is also applicable for BC1 and BC2 inside an inter *Base Station RF Bandwidth* gap equal to or larger than two times the interfering signal centre frequency offset. For *RIBs* supporting operation in multiple operating bands, the requirement is not applicable for BC1 band inside an inter *Base Station RF Bandwidth* gap with a gap size equal to or larger than 5 MHz. + +**Table 6.8.5.1.2-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA and/or NR UTRA signal | +| Interfering signal type | CW | +| Interfering signal power level applied to the CLTA | min(46 dBm, $P_{\text{rated,t,TRP}}$ ) | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or edge of sub-block inside a gap | > abs(800) kHz for CW interfering signal | +| NOTE 1: | Interfering signal positions that are partially or completely outside of any downlink operating band of the RIB are excluded from the requirement. | +| NOTE 2: | For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the CLTA. | + +#### 6.8.5.1.3 Additional test requirement (BC3) + +This additional requirement shall only apply for BS co-located with an UTRA TDD BS. + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits specified for transmitter spurious emission in clause 6.7.6 (except co-location spurious emission), operating band unwanted emission in clause 6.7.5 and ACLR in clause 6.7.3 in the presence of a wanted signal and an interfering signal according to table 6.8.5.1.3-1 an *OTA AAS BS* operating in BC3. + +For *multi-band RIBs*, the requirement applies relative to the *Base Station RF Bandwidth edges* of each operating band. In case the *Inter RF Bandwidth gap* is less than 3.2 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter *Base Station RF Bandwidth gap*. + +**Table 6.8.5.1.3-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement (BC3)** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | E-UTRA and/or UTRA and/or NR signal | +| Interfering signal type | 1,28 Mcps UTRA TDD signal of channel bandwidth 1,6 MHz | +| Interfering signal power level applied to the CLTA | min(46 dBm, $P_{\text{rated,t,TRP}}$ ) | +| Interfering signal centre frequency offset from Base Station RF Bandwidth edge or edge of sub-block inside a gap | ±0,8 MHz
±1,6 MHz
±2,4 MHz | +| NOTE 1: | Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are excluded from the requirement. | +| NOTE 2: | For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the CLTA. | + +## 6.8.5.2 Single RAT UTRA operation + +### 6.8.5.2.1 General test requirement for UTRA FDD + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the out of band emission or the spurious emission requirements of clause 6.7.4 (OTA spectrum mask) and clause 6.7.6 (OTA spurious emission, except co-location spurious emission), in the presence of interfering signal according to table 6.8.5.2.1-1. + +For *RIBs* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block edges*. + +For *multi-band RIBs*, the requirement is also applicable inside an *Inter RF Bandwidth gap* for interfering signal offsets where the interfering signal falls completely within the *Base Station RF Bandwidth gap*. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +**Table 6.8.5.2.1-1: Interfering and wanted signal frequency offset for OTA transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | UTRA | +| Interfering signal type | UTRA | +| Interfering signal power level applied to the CLTA | min(46 dBm, $P_{\text{rated,t,TRP}}$ ) | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal or edge of sub-block inside a gap | -2,5 MHz
-7,5 MHz
-12,5 MHz
+2,5 MHz
+7,5 MHz
+12,5 MHz | +| NOTE 1: | Interference frequencies that are outside of any allocated frequency band for UTRA-FDD downlink specified in clause 4.6 are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. | +| NOTE 2: | NOTE 1 is not applied in Band I, III, VI, VIII, IX, XI, XIX, XXI, and XXXII operating within 1 475.9 MHz to 1 495.9 MHz, in certain regions. | +| NOTE 3: | For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the CLTA. | + +### 6.8.5.3 Single RAT E-UTRA operation + +#### 6.8.5.3.1 General test requirement + +In the frequency range relevant for this test, the transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 6.7.6 (OTA spurious emission, except co-location spurious emission), 6.7.5 (OTA OBUE) and 6.7.3 (OTA ACLR) in the presence of an E-UTRA interfering signal according to table 6.8.5.3.1-1. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *radio bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *radio bandwidth edges*. + +For *RIBs* supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block edges*. + +For *multi-band RIBs*, the requirement applies relative to the *Base Station RF Bandwidth edges* of each supported operating band. In case the *Inter RF Bandwidth gap* is less than 15 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the *inter Base Station RF Bandwidth gap*. + +**Table 6.8.5.3.1-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement** + +| Parameter | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal | E-UTRA single carrier, or multi-carrier, or multiple intra-band contiguously or non-contiguously aggregated carriers | +| Interfering signal type | E-UTRA signal of channel bandwidth 5 MHz | +| Interfering signal power level applied to the CLTA | $\min(46 \text{ dBm}, P_{\text{rated,t,TRP}})$ | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal or edge of sub-block inside a sub-block gap | $\pm 2,5 \text{ MHz}$
$\pm 7,5 \text{ MHz}$
$\pm 12,5 \text{ MHz}$ | +| NOTE 1: | Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band , TS 36.141 provides further guidance regarding appropriate test requirements. | +| NOTE 2: | In certain regions, NOTE 1 is not applied in Band 1, 3, 8, 9, 11, 18, 19, 21, 28, 32 operating within 1 475.9 MHz to 1 495.9 MHz, 34. | +| NOTE 3: | For OTA AAS BS with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the CLTA. | + +#### 6.8.5.3.2 Void + +**Table 6.8.5.3.2-1: Void** + +## 7 Radiated receiver characteristics + +### 7.1 General + +OTA receiver characteristics requirements apply to the *AAS BS* including all its functional components active unless otherwise stated in each requirement. + +Unless otherwise stated the requirements in clause 7 apply during the AAS BS *receive period*. + +The requirements in clause 7 shall be met for any transmitter setting. + +The (E-UTRA) throughput requirements defined for the receiver characteristics in this clause do not assume HARQ retransmissions. + +When the AAS BS is configured to receive multiple carriers, all the throughput requirements are applicable for each received carrier. + +Any radiated receiver test requirement specified in TS 37.105 [6] is not applicable for AAS BS operation in Band 46. + +Each requirement shall be met over the RoAoA specified. + +For requirements which are to be met over the *OTA REFSENS RoAoA* absolute requirement values are offset by the following term: + +$$\Delta_{\text{OTAREFSENS}} = 44.1 - 10 \cdot \log_{10}(\text{BeW}_{\theta, \text{REFSENS}} \cdot \text{BeW}_{\phi, \text{REFSENS}}) \text{ (dB) for the reference direction.}$$ + +And + +$$\Delta_{\text{OTAREFSENS}} = 41.1 - 10 \cdot \log_{10}(\text{BeW}_{\theta, \text{REFSENS}} \cdot \text{BeW}_{\phi, \text{REFSENS}}) \text{ (dB) for all other directions.}$$ + +For requirements which are to be met over the *minSENS RoAoA* absolute requirement values are offset by the following term: + +$$\Delta_{\text{minSENS}} = P_{\text{REFSENS}} - \text{EIS}_{\text{minSENS}} \text{ (dB)}$$ + +## 7.2 OTA sensitivity + +### 7.2.1 Definition and applicability + +The OTA sensitivity requirement is based upon the declaration of one or more *OTA sensitivity direction declarations* (OSDD), related to an *AAS BS receiver*. + +The *AAS BS receiver* may optionally be capable of redirecting/changing the *receiver target* by means of adjusting BS settings resulting in multiple *sensitivity RoAoA*. The *sensitivity RoAoA* resulting from the current AAS BS settings is the active *sensitivity RoAoA*. + +If the AAS BS is capable of redirecting the *receiver target* related to the OSDD then the OSDD shall include: + +- The set(s) of RAT, *Channel bandwidth* and declared minimum EIS level applicable to any active *sensitivity RoAoA* inside the *receiver target redirection range* in the OSDD. +- A declared *receiver target redirection range*, describing all the angles of arrival that can be addressed for the OSDD through alternative settings in the *AAS BS*. +- Five declared *sensitivity RoAoA* comprising the conformance testing directions as detailed in [7]. +- The *receiver target reference direction*. + +NOTE 1: Some of the declared *sensitivity RoAoA* may coincide depending on the redirection capability. + +NOTE 2: In addition to the declared *sensitivity RoAoA*, several *sensitivity RoAoA* may be implicitly defined by the *receiver target redirection range* without being explicitly declared in the OSDD. + +NOTE 3: (Void) + +If the *AAS BS* is not capable of redirecting the *receiver target* related to the OSDD, then the OSDD includes only: + +- The set(s) of RAT, *Channel bandwidth* and declared minimum EIS level applicable to the *sensitivity RoAoA* in the OSDD. +- One declared active *sensitivity RoAoA*. +- The *receiver target reference direction*. + +NOTE 4: For *AAS BS* without target redirection capability, the declared (fixed) *sensitivity RoAoA* is always the active *sensitivity RoAoA*. + +The OTA sensitivity EIS level declaration shall apply to each supported polarization, under the assumption of *polarization match*. + +## 7.2.2 Minimum Requirement + +The minimum requirement for MSR & NR operation is in TS 37.105 [6], clause 10.2.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.2.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.2.4. + +## 7.2.3 Test Purpose + +The test purpose is to verify that the AAS BS can meet the BER or throughput requirement for a specified measurement channel at the EIS level and the range of angles of arrival declared in the OSDD. + +## 7.2.4 Method of test + +### 7.2.4.1 Initial conditions + +Test environment: + +- normal: see annex G.2. + +RF channels to be tested: + +- M; see clause 4.12.1. + +Directions to be tested: + +- *receiver target reference direction* (see table 4.10-1, D10.9), +- conformance test directions (see table 4.10-1, D10.10). + +### 7.2.4.2 Procedure + +- 1) Place the AAS BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D1.1. +- 2) Align the manufacturer declared coordinate system orientation of the AAS BS with the test system. +- 3) Align the BS with the test antenna in the declared direction to be tested. +- 4) Ensure the polarization is accounted for such that all the power from the test antenna is captured by the AAS BS under test. +- 5) Configure the beam peak direction of the AAS BS according to declared *reference beam direction pair* for the appropriate beam identifier. +- 6) Set the AAS BS to transmit the beam(s) of the same operational band and RAT as the OSDD being tested according to the appropriate test configuration in clause 5. +- 7) Start the signal generator for the wanted signal to transmit: + - 12.2 kbps DPCH with reference measurement channel defined in annex A in TS 25.141 [10] (PN-9 data sequence or longer) for UTRA FDD. + - UL reference measurement channel (12.2 kbps) defined in annex A.2.1 in TS 25.142 [11] for UTRA TDD 1.28Mcps operation. + +- The test signal as specified in clause 7.2.5.4 for E-UTRA. + - The test signal as specified in clause 7.2.5.5 for NR. +- 8) Set the test signal mean power so the calibrated radiated power at the AAS BS Antenna Array coordinate system reference point is as specified in clause 7.2.5. +- 9) Measure: +- BER according to annex C in TS 25.141 [10] for FDD UTRA. + - BER according to annex F in TS 25.142 [11] for TDD UTRA. + - Throughput according to annex E in TS 36.141 [12] for E-UTRA. + - Throughput according to annex A in TS 38.141-2 [34] for NR. +- 10) Repeat steps 3 to 9 for all OSDD(s) declared for the AAS BS (see table 4.10-1, D10.1), and supported polarizations. + +For multi-band capable AAS BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carriers activated in the other band. + +## 7.2.5 Test Requirements + +### 7.2.5.1 General + +The minimum EIS level is a declared figure for each OSDD (see table 4.10-1, D10.6). The test requirement is calculated from the declared value offset by the EIS Test Tolerance specified in clause 4.1.2.3. + +### 7.2.5.2 UTRA FDD Test Requirements + +The BER measurement result in step 9 of clause 7.2.4.2 shall not be greater than the limit specified in table 7.2.5.2-1. + +**Table 7.2.5.2-1: EIS levels** + +| Reference measurement channel | Reference measurement channel data rate | OTA sensitivity ( dBm) | | BER | +|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------|---------------------------------------|----------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | +| 12.2kbps DPCH with reference measurement channel defined in annex A in TS 25.141 [10] (PN-9 data sequence or longer) | 12.2 kbps | Declared minimum EIS (D10.6) + 1.3 dB | Declared minimum EIS (D10.6) + 1.4 dB | BER shall not exceed 0.001 | + +### 7.2.5.3 UTRA TDD 1,28Mcp option Test Requirements + +The BER measurement result in step 9 of clause 7.2.4.2 shall not be greater than the limit specified in table 7.2.5.3-1. + +**Table 7.2.5.3-1: EIS levels** + +| Reference measurement channel | Reference measurement channel data rate | OTA sensitivity ( dBm) | | BER | +|---------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------|---------------------------------------|----------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | +| UL reference measurement channel (12.2 kbps) defined in annex A.2.1 in TS 25.142 [11] | 12.2 kbps | Declared minimum EIS (D10.6) + 1.3 dB | Declared minimum EIS (D10.6) + 1.4 dB | BER shall not exceed 0.001 | + +### 7.2.5.4 E-UTRA Test Requirements + +For each measured E-UTRA carrier, the throughput measured in step 9 of clause 7.2.4.2 shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in TS 36.141 [12] annex A.1 with parameters specified in table 7.2.5.4-1. + +**Table 7.2.5.4-1: EIS levels** + +| E-UTRA channel
bandwidth (MHz) | Reference measurement
channel | OTA sensitivity (dBm) | | | | +|-----------------------------------|--------------------------------------|------------------------------------------|------------------------------------------|--|--| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 1.4 | FRC A1-1 in annex A.1 [12] | Declared minimum EIS
(D10.6) + 1.3 dB | Declared minimum EIS
(D10.6) + 1.4 dB | | | +| 3 | FRC A1-2 in annex A.1 [12] | | | | | +| 5 | FRC A1-3 in annex A.1 [12] | | | | | +| 10 | FRC A1-3 in annex A.1 [12]
(Note) | | | | | +| 15 | | | | | | +| 20 | | | | | | + +NOTE: EIS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 in [11] mapped to disjoint frequency ranges with a width of 25 Resource Blocks each. This reference measurement channel is not applied for Band 46 nor Band 49. + +### 7.2.5.5 NR Test Requirements + +For each measured carrier, the throughput measured in step 9 of clause 7.2.4.2 shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in TS 38.104 [33] annex A.1 with parameters specified in table 7.2.5.5-1. + +**Table 7.2.5.5-1: EIS levels** + +| BS channel
bandwidth [MHz] | Sub-carrier
spacing [kHz] | Reference
measurement
channel | EIS level [dBm] | | +|-------------------------------------------------|------------------------------|-------------------------------------|----------------------------|------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 in clause A.1 in [33] | Declared minimum EIS + 1.3 | Declared minimum EIS + 1.4 | +| 10, 15 | 30 | G-FR1-A1-2 in clause A.1 in [33] | Declared minimum EIS + 1.3 | Declared minimum EIS + 1.4 | +| 10, 15 | 60 | G-FR1-A1-3 in clause A.1 in [33] | Declared minimum EIS + 1.3 | Declared minimum EIS + 1.4 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 in clause A.1 in [33] | Declared minimum EIS + 1.3 | Declared minimum EIS + 1.4 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 in clause A.1 in [33] | Declared minimum EIS + 1.3 | Declared minimum EIS + 1.4 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 in clause A.1 in [33] | Declared minimum EIS + 1.3 | Declared minimum EIS + 1.4 | + +## 7.3 OTA Reference sensitivity level + +### 7.3.1 Definition and applicability + +The OTA REFSENS requirement is intended to ensure the OTA reference sensitivity level for a declared *OTA REFSENS RoAoA*. + +The OTA reference sensitivity power level $EIS_{REFSENS}$ is the mean power received at the RIB at which a reference performance requirement shall be met for a specified reference measurement channel. + +The OTA REFSENS requirement shall apply to each supported polarization, under the assumption of *polarization match*. + +### 7.3.2 Minimum Requirement + +The minimum requirement for MSR & NR operation is in TS 37.105 [6], clause 10.3.2. + +The minimum requirement for AAS BS in *single RAT UTRA operation* is defined in TS 37.105 [6], clause 10.3.3. + +The minimum requirement for AAS BS in *single RAT E-UTRA operation* is defined in TS 37.105 [6], clause 10.3.4. + +### 7.3.3 Test purpose + +The test purpose is to verify that the AAS BS can meet the BER or throughput requirement for a specified measurement channel at the $EIS_{REFSENS}$ level and the range of angles of arrival within the OTA REFSENS RoAoA. + +### 7.3.4 Method of test + +#### 7.3.4.1 Initial conditions + +Test environment: + +- normal: see annex G.2. + +RF channels to be tested: + +- B, M and T; see clause 4.12.1. + +Directions to be tested: + +- OTA REFSENS *receiver target reference direction* (see table 4.10-2, D11.30), +- OTA REFSENS conformance test directions (see table 4.10-2, D11.31). + +#### 7.3.4.2 Procedure + +- 1) Place the AAS BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D1.1. +- 2) Align the manufacturer declared coordinate system orientation of the AAS BS with the test system. +- 3) Align the BS with the test antenna in the declared direction to be tested. +- 4) Ensure the polarization is accounted for such that all the power from the test antenna is captured by the AAS BS under test. +- 5) Configure the beam peak direction of the AAS BS according to declared reference beam direction pair for the appropriate beam identifier. +- 6) Set the AAS BS to transmit the beam(s) of the same operational band and RAT as the OTA REFSENS RoAoA being tested according to the appropriate test configuration in clause 5. +- 7) Start the signal generator for the wanted signal to transmit: + - 12.2 kbps DPCH with reference measurement channel defined in annex A in TS 25.141 [10] (PN-9 data sequence or longer) for UTRA FDD. + - The test signal as specified in clause 7.3.5.3 for E-UTRA. + - The test signal as specified in clause 7.3.5.4 for NR. + +- 8) Set the test signal mean power so the calibrated radiated power at the AAS BS Antenna Array coordinate system reference point is as specified in clause 7.3.5. +- 9) Measure: + - BER according to annex C in TS 25.141 [10] for FDD UTRA. + - Throughput according to annex E in TS 36.141 [12] for E-UTRA. + - Throughput according to annex A in TS 38.141-2 [34] for NR. +- 10) Repeat steps 3 to 9 for all directions to be tested, and supported polarizations. + +For multi-band capable AAS BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carriers activated in the other band. + +## 7.3.5 Test Requirement + +### 7.3.5.1 General + +The $EIS_{REFSENS}$ level is the conducted REFSENS requirement value offset by $\Delta_{OTAREFSENS}$ . The test requirement is calculated from the $EIS_{REFSENS}$ level offset by the $EIS_{REFSENS}$ Test Tolerance specified in clause 4.1.2.3. + +### 7.3.5.2 UTRA FDD Test Requirements + +The BER measurement result in step 9 of clause 7.3.4.2 shall not be greater than the limit specified in table 7.3.5.2-1. + +**Table 7.3.5.2-1: $EIS_{REFSENS}$ levels** + +| BS Class | Reference measurement channel | Reference measurement channel data rate | $EIS_{REFSENS}$ (dBm) | | BER | +|-----------------|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------------------------------|--------------------------------|----------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | +| Wide Area BS | 12.2kbps DPCH with reference measurement channel defined in annex A in TS 25.141 [10] (PN-9 data sequence or longer) | 12.2 kbps | -119.7 - $\Delta_{OTAREFSENS}$ | -119.6 - $\Delta_{OTAREFSENS}$ | BER shall not exceed 0.001 | +| Medium Range BS | 12.2kbps DPCH with reference measurement channel defined in annex A in TS 25.141 [10] (PN-9 data sequence or longer) | 12.2 kbps | -109.7 - $\Delta_{OTAREFSENS}$ | -109.6 - $\Delta_{OTAREFSENS}$ | BER shall not exceed 0.001 | +| Local Area BS | 12.2kbps DPCH with reference measurement channel defined in annex A in TS 25.141 [10] (PN-9 data sequence or longer) | 12.2 kbps | -105.7 - $\Delta_{OTAREFSENS}$ | -105.6 - $\Delta_{OTAREFSENS}$ | BER shall not exceed 0.001 | + +### 7.3.5.3 E-UTRA Test Requirements + +For each measured E-UTRA carrier, the throughput measured in step 9 of clause 7.3.4.2 shall be $\geq 95$ % of the maximum throughput of the reference measurement channel as specified in TS 36.141 [12] annex A.1 with parameters specified in table 7.3.5.3-1. + +Table 7.3.5.3-1: E-UTRA Wide area AAS BS EISREFSENS levels + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel | EIS REFSENS (dBm) | | +|--------------------------------|--------------------------------------|--------------------------------|--------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | +| 1.4 | FRC A1-1 in annex A.1 [12] | $-105.5 - \Delta_{OTAREFSENS}$ | $-105.4 - \Delta_{OTAREFSENS}$ | +| 3 | FRC A1-2 in annex A.1 [12] | $-101.7 - \Delta_{OTAREFSENS}$ | $-101.6 - \Delta_{OTAREFSENS}$ | +| 5 | FRC A1-3 in annex A.1 [12] | $-100.2 - \Delta_{OTAREFSENS}$ | $-100.1 - \Delta_{OTAREFSENS}$ | +| 10 | FRC A1-3 in annex A.1 [12]
(Note) | $-100.2 - \Delta_{OTAREFSENS}$ | $-100.1 - \Delta_{OTAREFSENS}$ | +| 15 | | | | +| 20 | | | | + +NOTE: EISREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 in [11] mapped to disjoint frequency ranges with a width of 25 Resource Blocks each. + +Table 7.3.5.3-2: E-UTRA Local area AAS BS EISREFSENS levels + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel | EIS REFSENS (dBm) | | +|--------------------------------|--------------------------------------|-------------------------------|-------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | +| 1.4 | FRC A1-1 in annex A.1 [12] | $-97.5 - \Delta_{OTAREFSENS}$ | $-97.4 - \Delta_{OTAREFSENS}$ | +| 3 | FRC A1-2 in annex A.1 [12] | $-93.7 - \Delta_{OTAREFSENS}$ | $-93.6 - \Delta_{OTAREFSENS}$ | +| 5 | FRC A1-3 in annex A.1 [12] | $-92.2 - \Delta_{OTAREFSENS}$ | $-92.1 - \Delta_{OTAREFSENS}$ | +| 10 | FRC A1-3 in annex A.1 [12]
(Note) | $-92.2 - \Delta_{OTAREFSENS}$ | $-92.1 - \Delta_{OTAREFSENS}$ | +| 15 | | | | +| 20 | | | | + +NOTE: EISREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 in [11] mapped to disjoint frequency ranges with a width of 25 Resource Blocks each. + +Table 7.3.5.3-3: E-UTRA Medium range AAS BS EISREFSENS levels + +| E-UTRA channel bandwidth (MHz) | Reference measurement channel | EIS REFSENS (dBm) | | +|--------------------------------|----------------------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | +| 1.4 | FRC A1-1 in annex A.1 [12] | $-100.5 - \Delta_{OTAREFSENS}$ | $-100.4 - \Delta_{OTAREFSENS}$ | +| 3 | FRC A1-2 in annex A.1 [12] | $-96.7 - \Delta_{OTAREFSENS}$ | $-96.6 - \Delta_{OTAREFSENS}$ | +| 5 | FRC A1-3 in annex A.1 [12] | $-95.2 - \Delta_{OTAREFSENS}$ | $-95.1 - \Delta_{OTAREFSENS}$ | +| 10 | FRC A1-3 in annex A.1 [12] (NOTE 1)
FRC A1-8 in Annex A.1 [12] (NOTE 2) | $-95.2 - \Delta_{OTAREFSENS}$
$-97.9 - \Delta_{OTAREFSENS}$ | $-95.1 - \Delta_{OTAREFSENS}$
$-97.8 - \Delta_{OTAREFSENS}$ | +| 15 | FRC A1-3 in annex A.1 [12] (Note) | $-95.2 - \Delta_{OTAREFSENS}$ | $-95.1 - \Delta_{OTAREFSENS}$ | +| 20 | FRC A1-3 in annex A.1 [12] (NOTE 1)
FRC A1-8 in Annex A.1 [12] (NOTE 2) | $-95.2 - \Delta_{OTAREFSENS}$
$-97.9 - \Delta_{OTAREFSENS}$ | $-95.2 - \Delta_{OTAREFSENS}$
$-97.9 - \Delta_{OTAREFSENS}$ | + +NOTE 1: EISREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A1-3 in [11] mapped to disjoint frequency ranges with a width of 25 Resource Blocks each. This reference measurement channel is not applied for Band 46. + +NOTE 2: EISREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each single interlace of FRC A1-8 and A1-9. This reference measurement channel is only applied for Band 46. + +### 7.3.5.4 NR Test Requirements + +For each measured carrier, the throughput measured in step 9 of clause 7.3.4.2 shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex TS 38.104 [33] A.1 with parameters specified in tables 7.3.5.4-1 to 7.3.5.4-3. + +**Table 7.3.5.4-1: Wide Area BS EISREFSENS levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | EIS REFSENS (dBm) | | +|-------------------------------------------------|---------------------------|-------------------------------|------------------------------------------|------------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | -100.4 –
$\Delta_{\text{OTAREFSENS}}$ | -100.3 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 30 | G-FR1-A1-2 | -100.5 –
$\Delta_{\text{OTAREFSENS}}$ | -100.4 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 60 | G-FR1-A1-3 | -97.6 –
$\Delta_{\text{OTAREFSENS}}$ | -97.5 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -94 –
$\Delta_{\text{OTAREFSENS}}$ | -93.9 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -94.3 –
$\Delta_{\text{OTAREFSENS}}$ | -94.2 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -94.4 –
$\Delta_{\text{OTAREFSENS}}$ | -94.3 –
$\Delta_{\text{OTAREFSENS}}$ | + +NOTE: PREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.3.5.4-2: Medium Range BS EISREFSENS levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | EIS REFSENS (dBm) | | +|-------------------------------------------------|---------------------------|-------------------------------|-----------------------------------------|-----------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | -95.4 –
$\Delta_{\text{OTAREFSENS}}$ | -95.3 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 30 | G-FR1-A1-2 | -95.5 –
$\Delta_{\text{OTAREFSENS}}$ | -95.4 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 60 | G-FR1-A1-3 | -92.6 –
$\Delta_{\text{OTAREFSENS}}$ | -92.5 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -89 –
$\Delta_{\text{OTAREFSENS}}$ | -88.9 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -89.3 –
$\Delta_{\text{OTAREFSENS}}$ | -89.2 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -89.4 –
$\Delta_{\text{OTAREFSENS}}$ | -89.3 –
$\Delta_{\text{OTAREFSENS}}$ | + +NOTE: PREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.3.5.4-3: Local Area BS EISREFSENS levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | EIS REFSENS (dBm) | | +|-------------------------------------------------|---------------------------|-------------------------------|------------------------------------|------------------------------------| +| | | | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | -92.4 –
Δ OTAREFSENS | -92.3 –
Δ OTAREFSENS | +| 10, 15 | 30 | G-FR1-A1-2 | -92.5 –
Δ OTAREFSENS | -92.4 –
Δ OTAREFSENS | +| 10, 15 | 60 | G-FR1-A1-3 | -89.6 –
Δ OTAREFSENS | -89.5 –
Δ OTAREFSENS | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -86 –
Δ OTAREFSENS | -85.9 –
Δ OTAREFSENS | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -86.3 –
Δ OTAREFSENS | -86.2 –
Δ OTAREFSENS | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -86.4 –
Δ OTAREFSENS | -86.3 –
Δ OTAREFSENS | + +NOTE: PREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +## 7.4 OTA Dynamic range + +### 7.4.1 Definition and applicability + +The OTA dynamic range is a measure of the capability of the receiver unit to receive a wanted signal in the presence of an interfering signal inside the received *channel bandwidth* or the capability of receiving high level of wanted signal. + +The requirement applies at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction and are within the OTA REFSENS *RoAoA*. + +The wanted and interfering signals apply to each supported polarization, under the assumption of *polarization match*. + +### 7.4.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 10.4.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.4.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.4.4. + +### 7.4.3 Test purpose + +To verify that at the dynamic range of the receiver shall fulfil the specified limit. + +### 7.4.4 Method of test + +#### 7.4.4.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested for single carrier: M; see clause 4.12.1. + +Directions to be tested: OTA REFSENS receiver target reference direction (see table 4.10-2, D11.30). + +#### 7.4.4.2 Procedure + +- 1) Place the AAS BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in Annex D2.2 +- 2) Align the manufacturer declared coordinate system orientation of the AAS BS with the test system. +- 3) Align the BS with the test antenna in the declared direction to be tested. +- 4) Align the NR BS to that the wanted signal and interferer signal is *polarization matched* with the test antenna(s).. +- 5) Set the test signal mean power so the calibrated radiated power at the AAS BS Antenna Array coordinate system reference point is as specified as follows: + - a) Set the signal generator for the wanted signal to transmit: + - as specified in table 7.4.5.1-1 for UTRA. + - as specified in table 7.4.5.2-3 to table 7.4.5.2-5 for E-UTRA. + - as specified in table 7.4.5.3-3 to table 7.4.5.2-5 for NR. + - b) Set the Signal generator for the AWGN interfering signal at the same frequency as the wanted signal to transmit: + - as specified in table 7.4.5.1-1 for UTRA. + - as specified in table 7.4.5.2-3 to table 7.4.5.2-5 for E-UTRA. + - as specified in table 7.4.5.3-3 to table 7.4.5.23-5 for NR. +- 6) Measure: + - BER according to annex C in TS 25.141 [10] for FDD UTRA. + - Throughput according to annex E in TS 36.141 [12] for E-UTRA. + - Throughput according to TS 38.141-2 [34] for NR. +- 7) Repeat for all supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 8) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.4.5 Test Requirement + +##### 7.4.5.1 UTRA FDD operation + +The BER shall not exceed 0,001 for the parameters specified in table 7.3.5.1-1. + +**Table 7.4.5.1-1: Dynamic range** + +| Parameter | Level Wide Area BS | Level Medium Range BS | Level Local Area BS | Unit | +|-----------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------| +| Reference measurement channel data rate | 12.2 | 12.2 | 12.2 | kbps | +| Wanted signal mean power | $-90.7 - \Delta_{\text{OTAREFSENS}}$ | $-80.7 - \Delta_{\text{OTAREFSENS}}$ | $-76.7 - \Delta_{\text{OTAREFSENS}}$ | dBm | +| Interfering AWGN signal | $-73 - \Delta_{\text{OTAREFSENS}}$ | $-63 - \Delta_{\text{OTAREFSENS}}$ | $-59 - \Delta_{\text{OTAREFSENS}}$ | dBm/3.84 MHz | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.4.5.2 E-UTRA operation + +For each measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel as specified in annex A in 36.141 [12]TS 36.141 [12] with parameters specified in table 7.3.5.3-1 for an AAS BS of Wide Area BS class, in Table 7.3.5.3-2 for an AAS BS of Local Area BS class and in table 7.3.5.3-3 for AAS BS of Medium Range BS class. + +**Table 7.4.5.2-1: AAS BS of Wide Area BS class dynamic range** + +| E-UTRA channel bandwidth [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] / BW Config | Type of interfering signal | +|--------------------------------|---------------------------------------------|--------------------------------------|------------------------------------------------------------|----------------------------| +| 1.4 | FRC A2-1 in TS 36.104 [4], annex A.2 | $-76.0 - \Delta_{\text{OTAREFSENS}}$ | $-88.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 3 | FRC A2-2 in TS 36.104 [4], annex A.2 | $-72.1 - \Delta_{\text{OTAREFSENS}}$ | $-84.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 5 | FRC A2-3 in TS 36.104 [4], annex A.2 | $-69.9 - \Delta_{\text{OTAREFSENS}}$ | $-82.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 10 | FRC A2-3 in TS 36.104 [4], annex A.2 (NOTE) | $-69.9 - \Delta_{\text{OTAREFSENS}}$ | $-79.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 15 | FRC A2-3 in TS 36.104 [4], annex A.2 (NOTE) | $-69.9 - \Delta_{\text{OTAREFSENS}}$ | $-77.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| 20 | FRC A2-3 in TS 36.104 [4], annex A.2 (NOTE) | $-69.9 - \Delta_{\text{OTAREFSENS}}$ | $-76.4 - \Delta_{\text{OTAREFSENS}}$ | AWGN | + +NOTE: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A2-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +**Table 7.3.5.3-2: AAS BS of Local Area BS class dynamic range** + +| E-UTRA channel bandwidth h [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] / BW_{Config} | Type of interfering signal | +|------------------------------------------------------|-----------------------------------------------|---------------------------------------|-----------------------------------------------------------------------|-----------------------------------| +| 1.4 | FRC A2-1 in TS 36.104 [4], annex A.2 | $-68.0 - \Delta_{OTAREFSENS}$ | $-80.7 - \Delta_{OTAREFSENS}$ | AWGN | +| 3 | FRC A2-2 in TS 36.104 [4], annex A.2 | $-64.1 - \Delta_{OTAREFSENS}$ | $-76.7 - \Delta_{OTAREFSENS}$ | AWGN | +| 5 | FRC A2-3 in TS 36.104 [4], annex A.2 | $-61.9 - \Delta_{OTAREFSENS}$ | $-74.5 - \Delta_{OTAREFSENS}$ | AWGN | +| 10 | FRC A2-3 in TS 36.104 [4], annex A.2 (NOTE 1) | $-61.9 - \Delta_{OTAREFSENS}$ | $-71.5 - \Delta_{OTAREFSENS}$ | AWGN | +| 15 | FRC A2-3 in TS 36.104 [4], annex A.2 (NOTE 1) | $-61.9 - \Delta_{OTAREFSENS}$ | $-69.7 - \Delta_{OTAREFSENS}$ | AWGN | +| 20 | FRC A2-3 in TS 36.104 [4], annex A.2 (NOTE 1) | $-61.9 - \Delta_{OTAREFSENS}$ | $-68.4 - \Delta_{OTAREFSENS}$ | AWGN | + +NOTE 1: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A2-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. This reference measurement channel is not applied for Band 46 nor Band 49. + +NOTE 2: Void + +**Table 7.3.5.3-3: AAS BS of Medium Range BS class dynamic range** + +| E-UTRA channel bandwidth h [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] / BW_{Config} | Type of interfering signal | +|------------------------------------------------------|-----------------------------------------------|---------------------------------------|-----------------------------------------------------------------------|-----------------------------------| +| 1.4 | FRC A2-1 in TS 36.104 [4], annex A.2 | $-71.0 - \Delta_{OTAREFSENS}$ | $-83.7 - \Delta_{OTAREFSENS}$ | AWGN | +| 3 | FRC A2-2 in TS 36.104 [4], annex A.2 | $-67.1 - \Delta_{OTAREFSENS}$ | $-79.7 - \Delta_{OTAREFSENS}$ | AWGN | +| 5 | FRC A2-3 in TS 36.104 [4], annex A.2 | $-64.9 - \Delta_{OTAREFSENS}$ | $-77.5 - \Delta_{OTAREFSENS}$ | AWGN | +| 10 | FRC A2-3 in TS 36.104 [4], annex A.2 (NOTE 1) | $-64.9 - \Delta_{OTAREFSENS}$ | $-74.5 - \Delta_{OTAREFSENS}$ | AWGN | +| 15 | FRC A2-3 in TS 36.104 [4], Annex A.2 (NOTE 1) | $-64.9 - \Delta_{OTAREFSENS}$ | $-72.7 - \Delta_{OTAREFSENS}$ | AWGN | +| 20 | FRC A2-3 in TS 36.104 [4], annex A.2 (NOTE 1) | $-64.9 - \Delta_{OTAREFSENS}$ | $-71.4 - \Delta_{OTAREFSENS}$ | AWGN | + +NOTE 1: The wanted signal mean power is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of FRC A2-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each. This reference measurement channel is not applied for Band 46. + +NOTE 2: Void. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.4.5.3 NR operation + +For each measured carrier, the throughput measured in step 6 of clause 7.4.4.2 shall be $\geq 95$ % of the maximum throughput of the reference measurement channel as specified in TS 38.104 [33] annex A.2 with parameters specified in tables 7.4.5.3-1 to 7.4.5.3-3. + +**Table 7.4.5.3-1: Wide Area BS dynamic range** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) / BW Config | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|--------------------------------------|--------------------------------------|------------------------------------------------------------|----------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 5 | 15 | G-FR1-A2-1 | $-70.4 - \Delta_{\text{OTAREFSENS}}$ | $-70.4 - \Delta_{\text{OTAREFSENS}}$ | $-82.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-71.1 - \Delta_{\text{OTAREFSENS}}$ | $-71.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 10 | 15 | G-FR1-A2-1 | $-70.4 - \Delta_{\text{OTAREFSENS}}$ | $-70.4 - \Delta_{\text{OTAREFSENS}}$ | $-79.3 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-71.1 - \Delta_{\text{OTAREFSENS}}$ | $-71.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | $-68.1 - \Delta_{\text{OTAREFSENS}}$ | $-68.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 15 | 15 | G-FR1-A2-1 | $-70.4 - \Delta_{\text{OTAREFSENS}}$ | $-70.4 - \Delta_{\text{OTAREFSENS}}$ | $-77.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-71.1 - \Delta_{\text{OTAREFSENS}}$ | $-71.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | $-68.1 - \Delta_{\text{OTAREFSENS}}$ | $-68.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 20 | 15 | G-FR1-A2-4 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-76.2 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 25 | 15 | G-FR1-A2-4 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-75.2 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-74.4 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 35 | 15 | G-FR1-A2-4 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-73.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-73.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 45 | 15 | G-FR1-A2-4 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-72.6 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-72.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-71.3 - \Delta_{\text{OTAREFSENS}}$ | AWGN | + +| | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------|--------------------------------------|--------------------------------------|--------------------------------------|------| +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-70.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-70.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-69.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.2 - \Delta_{\text{OTAREFSENS}}$ | $-69.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth . | | | | | | | + +**Table 7.4.5.3-2: Medium Range BS dynamic range** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) / BW Config | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|---------------------------------------|---------------------------------------|------------------------------------------------------------|----------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 5 | 15 | G-FR1-A2-1 | $-65.4 - \Delta_{\text{OTAREFSENS}}$ | $-65.4 - \Delta_{\text{OTAREFSENS}}$ | $-77.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-66.1 - \Delta_{\text{OTAREFSENS}}$ | $-66.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 10 | 15 | G-FR1-A2-1 | $-65.4 - \Delta_{\text{OTAREFSENS}}$ | $-65.4 - \Delta_{\text{OTAREFSENS}}$ | $-74.3 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-66.1 - \Delta_{\text{OTAREFSENS}}$ | $-66.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 15 | 15 | G-FR1-A2-1 | $-65.4 - \Delta_{\text{OTAREFSENS}}$ | $-65.4 - \Delta_{\text{OTAREFSENS}}$ | $-72.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-66.1 - \Delta_{\text{OTAREFSENS}}$ | $-66.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 20 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-71.2 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 25 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-70.2 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-69.4 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 35 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-68.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-68.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 45 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-67.6 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-67.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $--59.2 - \Delta_{\text{OTAREFSENS}}$ | $--59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-66.3 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-65.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-65.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +Table 7.4.5.3-3: Local Area BS dynamic range + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) / BW Config | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|--------------------------------------|--------------------------------------|------------------------------------------------------------|----------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 5 | 15 | G-FR1-A2-1 | $-62.4 - \Delta_{\text{OTAREFSENS}}$ | $-62.4 - \Delta_{\text{OTAREFSENS}}$ | $-74.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 10 | 15 | G-FR1-A2-1 | $-62.4 - \Delta_{\text{OTAREFSENS}}$ | $-62.4 - \Delta_{\text{OTAREFSENS}}$ | $-71.3 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | $-60.1 - \Delta_{\text{OTAREFSENS}}$ | $-60.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 15 | 15 | G-FR1-A2-1 | $-62.4 - \Delta_{\text{OTAREFSENS}}$ | $-62.4 - \Delta_{\text{OTAREFSENS}}$ | $-69.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | $-60.1 - \Delta_{\text{OTAREFSENS}}$ | $-60.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 20 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-68.2 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 25 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-67.2 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-66.4 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 35 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.6 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-65.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 45 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.6 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-63.3 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-62.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-62.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-61.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-56.2 - \Delta_{\text{OTAREFSENS}}$ | $-61.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | $-56.5 - \Delta_{\text{OTAREFSENS}}$ | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +## 7.5 OTA Adjacent channel selectivity, general blocking, and narrowband blocking + +### 7.5.1 Definition and applicability + +The adjacent channel selectivity (ACS), general blocking and narrowband blocking characteristics are measures of the receiver unit ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer inside the operating band. + +The requirement applies at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction, and: + +- when the wanted signal is based on $EIS_{REFSENS}$ : the AoA of the incident wave of a received signal and the interfering signal are within the OTA $REFSENS\ RoAoA$ . +- when the wanted signal is based on $EIS_{minSENS}$ : the AoA of the incident wave of a received signal and the interfering signal are within the $minSENS\ RoAoA$ . + +The wanted and interfering signals apply to each supported polarization, under the assumption of *polarization match*. + +NOTE: For Single RAT requirements, the in-band selectivity characteristics is referred to as "adjacent channel selectivity", whereas for the MSR requirements, the corresponding property is referred to as "general blocking" since the adjacent frequency range may not carry a channel addressable from the interfered carrier. The in-band blocking requirement applies from $F_{UL\_low} - \Delta f_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ , excluding the downlink frequency range of the *operating band*. The $\Delta f_{OOB}$ is defined in table 7.5-1. + +**Table 7.5-1: $\Delta f_{OOB}$ offset for operating bands** + +| Operating band characteristics | \Delta f_{OOB} [MHz] | +|----------------------------------------------------------|------------------------------------------| +| $F_{UL\_high} - F_{UL\_low} < 100\ MHz$ | 20 | +| $100\ MHz \leq F_{UL\_high} - F_{UL\_low} \leq 900\ MHz$ | 60 | + +### 7.5.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 10.5.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.5.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.5.4. + +### 7.5.3 Test purpose + +The test stresses the receiver unit ability to withstand high-level interference from unwanted signals at specified frequency offsets without undue degradation of its sensitivity. + +### 7.5.4 Method of test + +#### 7.5.4.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested for single carrier: M; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier (MC): - $M_{RFBW}$ for *single-band RIB(s)*, see clause 4.12.1, $B_{RFBW\_T_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ for *multi-band RIB(s)*, see clause 4.12.1. + +Directions to be tested: + +OTA minSENS receiver target reference direction (see table 4.10-2, D107). + +OTA REFSENS conformance test directions (see table 4.10-2, D11.31).). + +## 7.5.4.2 Procedure + +### 7.5.4.2.1 General procedure + +The general procedure steps apply to the procedures for all the RATs. + +- 1) Place the AAS BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in Annex D1.1. +- 2) Align the manufacturer declared coordinate system orientation of the AAS BS with the test system. +- 3) Align the BS with the test antenna in the declared direction to be tested. +- 4) Align the NR BS to that the wanted signal and interferer signal is *polarization matched* with the test antenna(s). +- 5) Set the test signal mean power so the calibrated radiated power at the AAS BS Antenna Array coordinate system reference point is as specified as follows: + - a) Set the signal generator for the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to transmit: + - For E-UTRA see clause A.1 in TS 36.141 [12]. + - For UTRA FDD see clause A.2 in TS 25.141 [10]. + - For NR see clause A.1 in TS 38.141-2 [34]. + +### 7.5.4.2.2 MSR operation + +#### 7.5.4.2.2.1 Procedure for general blocking + +- 1) Adjust the signal generators to the type of interfering signal, levels and the frequency offsets as specified in table 7.5.5.1.1-1. +- 2) The interfering signal shall be swept with a step size of 1 MHz starting from the minimum offset to the channel edges of the wanted signals as specified in table 7.5.5.1.1-1. +- 3) Measure the performance of the wanted signal as defined in clause 7.5.5.1, for the relevant carriers specified by the test configuration in clause 4.11. +- 4) Repeat for all the specified measurement directions. +- 5) Repeat for all supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 6) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.5.4.2.2.2 Procedure for narrowband blocking + +- 1) Adjust the signal generators to the type of interfering signal, levels and the frequency offsets as specified in table 7.5.5.1.2-1. +- 2) Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.5.5.1.2-1. +- 3) Measure the performance of the wanted signal at the receiver under test, as defined in clause 7.5.5.1, for the relevant carriers specified by the test configuration in clause 4.11. + +- 4) Repeat for all the specified measurement directions. +- 5) Repeat for all supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 6) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.5.4.2.2.3 Procedure for additional BC3 blocking requirement + +- 1) Adjust the signal generators to the type of interfering signal, levels and the frequency offsets as specified in table 7.5.5.1.3-1. +- 2) Measure the performance of the wanted signal at the receiver under test, as defined in clause 7.5.5, for the relevant carriers specified by the test configuration in clause 4.11. +- 3) Repeat for all the specified measurement directions and all supported polarizations. + +#### 7.5.4.2.3 Single RAT UTRA FDD operation + +- 1) Generate the wanted signal and adjust the ATT1 to set the input level to the level specified in table 7.5.5.2-1 For a RIB supporting multi-carrier operation, generate the wanted signal according to the applicable test configuration (see clause 4.11) using applicable reference measurement channel to the RIB under test. Power settings are specified in table 7.5.5.2-1. +- 2) Set-up the interfering signal at the adjacent channel frequency and adjust the ATT2 to obtain the specified level of interfering signal at the AAS BS input defined in table 7.5.5.2-1. Note that the interfering signal shall have an ACLR of at least 63 dB in order to eliminate the impact of interfering signal adjacent channel leakage power on the ACS measurement. +- 3) Measure the BER of the wanted signal at the receiver under test. +- 4) Repeat for all the specified measurement directions and all supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 5) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.5.4.2.4 Single RAT E-UTRA operation + +##### 7.4.4.2.4.1 Procedure for adjacent channel selectivity + +- 1) Generate the wanted signal using the applicable test configuration specified in clause 5.3.4 and adjust the input level to the level specified in table 7.5.5.3-1 for the appropriate BS class. +- 2) Set-up the interfering signal at the adjacent channel frequency and adjust the interfering signal level to the level defined in table 7.5.5.3-1 for the appropriate BS class. +- 3) Measure the throughput according to annex E in 36.141 [12]TS 36.141 [12], for multi-carrier and/or CA operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clause 5.3.4. +- 4) Repeat for all the specified measurement directions and all supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 5) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.5.4.2.4.2 Procedure for narrow-band blocking + +- 1) Configure the beam peak direction of the AAS BS according to declared *reference beam direction pair* for the appropriate beam identifier. +- 2) For RIB operating E-UTRA FDD declared to be capable of single carrier operation only in the operating band, set the AAS BS to transmit according to clause 4.12.2 at manufacturers declared rated carrier TRP $P_{\text{rated,c,TABC}}$ . + +For a RIB operating E-UTRA FDD declared to be capable of multi-carrier and/or CA operation in the operating band, set the ASA BS to transmit according to clause 4.12.2 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 5.3.4. + +- 3) Generate the wanted signal using the applicable test configuration specified in clause 5.3.4 and adjust the input level to the level specified in table 7.5.5.3-1. +- 4) Adjust the interfering signal level to the level defined in table 7.5.5.3-1. Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.5.5.3-2. +- 5) Measure the throughput according to annex E in 36.141 [12]TS 36.141 [12], for multi-carrier and/or CA operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clause 5.3.4. +- 6) Repeat for all the specified measurement directions and all supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 7) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 7.5.5 Test Requirement + +#### 7.5.5.1 MSR operation + +##### 7.5.5.1.1 General blocking test requirement + +For the general blocking requirement, the interfering signal shall be a UTRA FDD signal as specified in clause A.1 in TS 25.141 [10] for a UTRA, E-UTRA or NR ( $\leq 20$ MHz) wanted signal. The interfering signal shall be a 20 MHz E-UTRA signal for NR wanted signal channel bandwidth greater than 20 MHz. + +For RIBs supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 15 MHz. The interfering signal offset is defined relative to the sub-block edges inside the *sub-block gap*. + +For *multi-band RIBs* the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least 15 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal coupled to the *RIB*, using the parameters in tables 7.5.5.1.1-1 and 7.5.5.1.1-2, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.4. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.2. +- For any measured NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined in clause 7.2 of TS 38.104 [33]. + +For *multi-band RIBs*, the requirement applies according to table 7.5.5.1.1-1 for the in-band blocking frequency ranges of each supported operating band. + +**Table 7.5.5.1.1-1: General blocking requirement** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] (NOTE 1) | Centre Frequency of Interfering Signal | Interfering signal centre frequency minimum frequency offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap [MHz] | +|-------------------|----------------------------------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | $-40 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 7, 9) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 2, 5, 9) | $F_{\text{UL\_low}} - \Delta f_{\text{OOB}}$ to $F_{\text{UL\_high}} + \Delta f_{\text{OOB}}$ | $(\pm 7.5 + z)$ (Note 11) | +| | $-40 + y - \Delta_{\text{minSENS}}$ (NOTE 7, 10) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 2, 5, 10) | | | +| Medium Range BS | $-35 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 7, 9) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 3, 5, 9) | $F_{\text{UL\_low}} - \Delta f_{\text{OOB}}$ to $F_{\text{UL\_high}} + \Delta f_{\text{OOB}}$ | $(\pm 7.5 + z)$ (Note 11) | +| | $-35 + y - \Delta_{\text{minSENS}}$ (NOTE 7, 10) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 3, 5, 10) | | | +| Local Area BS | $-30 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 7, 9) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 4, 5, 9) | $F_{\text{UL\_low}} - \Delta f_{\text{OOB}}$ to $F_{\text{UL\_high}} + \Delta f_{\text{OOB}}$ | $(\pm 7.5 + z)$ (Note 11) | +| | $-30 + y - \Delta_{\text{minSENS}}$ (NOTE 7, 10) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 4, 5, 10) | | | + +NOTE 1: $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{minSENS}}$ depend on the RAT, the BS class and on the *channel bandwidth*, see clauses 7.3 and 7.2. + +NOTE 2: For WA BS that does not support NR, "x" is equal to 6 in case of E-UTRA or UTRA wanted signals and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 3: For MR BS that does not support NR, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of E-UTRA wanted signal and 3 in case of GSM/EDGE wanted signal. + +NOTE 4: For LA BS that does not support NR, "x" is equal to 11 in case of E-UTRA wanted signal, 6 in case of UTRA wanted signal and equal to 3 in case of GSM/EDGE wanted signal. + +NOTE 5: For a BS that supports NR but does not support UTRA, x is equal to 6. + +NOTE 6: For a BS capable of multi-band operation, "x" in Note 2, 3, 4, 5 applies in case of interfering signals that are in the in-band blocking frequency range of the operating band where the wanted signal is present or in the in-band blocking frequency range of an adjacent or overlapping operating band. For other in-band blocking frequency ranges of the interfering signal for the supported operating bands, "x" is equal to 1.4 dB. + +NOTE 7: For a BS that not supporting NR, "y" is equal to zero for all BS classes. For a BS that supports NR but does not support UTRA, "y" is equal to -3 for the WA and MR BS class and -5 for the LA BS class. + +NOTE 8: The downlink frequency range of an FDD operating band is excluded from the general blocking requirement. + +NOTE 9: This test requirement is only applied in the OTA REFSENS conformance test directions. + +NOTE 10: This test requirement is only applied in the OTA minSENS receiver target reference direction. + +NOTE 11: For NR wanted signal channel bandwidth greater than 20 MHz, $z = 22.5 \text{ MHz}$ . For all other cases, $z = 0 \text{ MHz}$ . + +**Table 7.5.5.1.1-2: Void** + +NOTE: The requirement in tables 7.5.5.1.1-1 and 7.5.5.1.1-2 assumes that two operating bands, where the *downlink operating band* (see table 4.4-1 and table 4.4-2 in TS 37.141 [13].) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +### 7.5.5.1.2 General narrowband blocking test requirement + +For the narrowband blocking requirement, the interfering signal shall be an E-UTRA 1RB signal as specified in clause A.3 in TS 37.141 [13]. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For RIBs supporting operation in non-contiguous spectrum, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 3 MHz. The interfering signal offset is defined relative to the sub-block edges inside the *sub-block gap*. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap* in case the gap size is at least 3 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal coupled to the RIB, using the parameters in table 7.5.5.1.2-1 the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5.4. +- For any measured UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in clause 7.2.5.2. +- For any NR carrier, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel defined for *BS type 1-O* in TS 38.104 [33], clause 10.3.2 + +**Table 7.5.5.1.2-1: Narrowband blocking requirement** + +| Base Station Type | RAT of the carrier | Wanted signal mean power [dBm] (NOTE 1, 2, 8) | Interfering signal mean power [dBm] | Interfering RB (NOTE 3) centre frequency offset from the AAS Base Station RF Bandwidth edge or edge of sub-block inside a gap [kHz] | +|-------------------|--------------------|-----------------------------------------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | E-UTRA, NR, UTRA | $EIS_{REFSENS} + x$ dB (NOTE 6) | $-49 - \Delta_{OTAREFSENS}$ (NOTE 6) | $\pm(240 + m \cdot 180)$ ,
$m=0, 1, 2, 3, 4, 9, 14$ (Note 4) | +| | | $EIS_{minSENS} + x$ dB (NOTE 7) | $-49 - \Delta_{minSENS}$ (NOTE 7) | | +| Medium Range BS | | $EIS_{REFSENS} + x$ dB (NOTE 6) | $-44 - \Delta_{OTAREFSENS}$ (NOTE 6) | | +| | | $EIS_{minSENS} + x$ dB (NOTE 7) | $-44 - \Delta_{minSENS}$ (NOTE 7) | | +| Local Area BS | | $EIS_{REFSENS} + x$ dB (NOTE 6) | $-41 - \Delta_{OTAREFSENS}$ (NOTE 6) | | +| | | $EIS_{minSENS} + x$ dB (NOTE 7) | $-41 - \Delta_{minSENS}$ (NOTE 7) | | + +NOTE 1: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depend on the RAT, the BS class and on the *channel bandwidth*, see clauses 7.3 and 7.2. + +NOTE 2: "x" is equal to 6 dB in case of E-UTRA or UTRA wanted signals. + +NOTE 3: Interfering signal (E-UTRA 3 MHz) consisting of one resource block positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the AAS Base Station RF Bandwidth edge. + +NOTE 4: Applicable for *channel bandwidths* equal to or below 20 MHz. + +NOTE 5: Applicable for *channel bandwidths* above 20 MHz. + +NOTE 6: This test requirement is only applied in the OTA REFSENS conformance test directions. + +NOTE 7: This test requirement is only applied in the OTA minSENS receiver target reference direction. + +NOTE 8: 7.5 kHz shift is not applied to the wanted signal of NR. + +NOTE 9: Void + +### 7.5.5.1.3 Additional BC3 blocking test requirement + +This additional requirement only applies for BS operating in the same geographical area as UTRA TDD. + +The interfering signal is a 1,28Mcps UTRA TDD modulated signal as specified in clause A.2 in TS 37.141 [13]. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least 4.8 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal coupled to the RIB, using the parameters in table 7.5.5.1.3-1, the following requirements shall be met: + +- For any measured E-UTRA carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in clause 7.2.5. + +**Table 7.5.5.1.3-1: Additional blocking requirement for Band Category 3** + +| Operating Band | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] (NOTE) | Interfering signal centre frequency minimum frequency offset from the Base Station RF Bandwidth edge [MHz] | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------------------------------------------------| +| 33 - 40 | $(F_{UL\_low} - 20)$ to $(F_{UL\_high} + 20)$ | $-40 - \Delta_{OTAREFSENS}$ (NOTE 2) | $EIS_{REFSENS} + 6$ dB (NOTE 2) | $\pm 2,4$ | +| | | $-40 - \Delta_{minSENS}$ (NOTE 3) | $EIS_{minSENS} + 6$ dB (NOTE 3) | | +| NOTE 1: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depend on the RAT, the BS class and on the channel bandwidth , see clauses 7.3 and 7.2.
NOTE 2: This test requirement is only applied in the OTA REFSENS conformance test directions.
NOTE 3: This test requirement is only applied in the OTA minSENS receiver target reference direction. | | | | | + +## 7.5.5.2 Single RAT UTRA FDD operation + +For each measured carrier, the BER shall not exceed 0,001 for the parameters specified in table 7.5.5.2-1. + +For *multi-carrier RIB* the ACS requirement is applicable outside the *Base Station RF Bandwidth* or *Maximum Radio Bandwidth*. The interfering signal offset is defined relative to the lower/upper *Base Station RF Bandwidth edges* or *Maximum Radio Bandwidth edges*. + +For RIBs supporting operation in *non-contiguous spectrum* within any operating band, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 5 MHz. The interfering signal offset is defined relative to the lower/upper sub-block edge inside the *sub-block gap* and is equal to -2.5 MHz/+2.5 MHz, respectively. + +For a *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least 5 MHz. The interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -2.5 MHz/+2.5 MHz, respectively. + +**Table 7.5.5.2-1: Adjacent channel selectivity** + +| Parameter | Level Wide Area BS | Level Medium Range BS | Level Local Area / Home BS | Unit | +|-------------------------------|---------------------------|---------------------------|----------------------------|------| +| Data rate | 12.2 | 12.2 | 12.2 | kbps | +| Wanted signal mean power | $-115 - \Delta_{minSENS}$ | $-105 - \Delta_{minSENS}$ | $-101 - \Delta_{minSENS}$ | dBm | +| Interfering signal mean power | $-52 - \Delta_{minSENS}$ | $-42 - \Delta_{minSENS}$ | $-38 - \Delta_{minSENS}$ | dBm | +| $F_{uw}$ offset (Modulated) | $\pm 5$ | $\pm 5$ | $\pm 5$ | MHz | + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +### 7.5.5.3 Single RAT E-UTRA operation + +The throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel. + +For E-UTRA Wide Area BS, the wanted and the interfering signal coupled to the BS antenna input are specified in tables 7.5.5.3-1 and 7.5.5.3-2 for narrowband blocking and 7.5.5.3-3 for ACS. The reference measurement channel for the wanted signal is identified in table 7.3.5.3-1 for each *channel bandwidth* and further specified in TS 36.104 [4] Annex A. + +For E-UTRA Medium Range BS, the wanted and the interfering signal coupled to the BS antenna input are specified in tables 7.5.5.3-1 and 7.5.5.3-2 for narrowband blocking and in table 7.5.5.3-5 for ACS. Narrowband blocking requirements are not applied for Band 46. The reference measurement channel for the wanted signal is identified in table 7.3.5.3-3 for each *channel bandwidth* and further specified in TS 36.104 [4] Annex A. + +For E-UTRA Local Area BS, the wanted and the interfering signal coupled to the BS antenna input are specified in tables 7.5.5.3-1 and 7.5.5.3-2 for narrowband blocking and 7.5.5.3-4 for ACS. Narrowband blocking requirements are not applied for Band 46. The reference measurement channel for the wanted signal is identified in table 7.3.5.3-2 for each *channel bandwidth* and further specified in TS 36.104 [4] Annex A. + +For narrowband blocking the OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +For ACS the OTA levels are applied referenced to $\Delta_{\text{minSENS}}$ . + +The ACS and narrowband blocking requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIBs supporting operation in *non-contiguous spectrum* within any operating band, the ACS requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least as wide as the E-UTRA interfering signal in tables 7.5.5.3-3, 7.5.5.3-4 and 7.5.5.3-5. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the ACS requirement applies in addition inside any *Inter RF Bandwidth gap* at the RIB, in case the gap size is at least as wide as the E-UTRA interfering signal in tables 7.5.5.3-3, 7.5.5.3-4 and 7.5.5.3-5. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For a RIBs operating in *non-contiguous spectrum* within any operating band, the narrowband blocking requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least as wide as the *channel bandwidth* of the E-UTRA interfering signal in table 7.5.5.3-2. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the narrowband blocking requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least as wide as the E-UTRA interfering signal in table 7.5.5.3-2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 7.5.5.3-1: Narrowband blocking requirement** + +| | Wanted signal mean power [dBm] (NOTE) | Interfering signal mean power [dBm] | Type of interfering signal | +|-----------------|----------------------------------------|----------------------------------------|----------------------------| +| Wide Area BS | EIS REFSENS + 6 dB (NOTE 2) | -49 – Δ OTAREFSENS (NOTE 2) | See table 10.5.4.2-2 | +| | EIS minSENS + 6 dB (NOTE 3) | -49 – Δ minSENS (NOTE 3) | | +| Medium Range BS | EIS REFSENS + 6 dB (NOTE 2) | -44 – Δ OTAREFSENS (NOTE 2) | See table 10.5.4.2-2 | +| | EIS minSENS + 6 dB (NOTE 3) | -44 – Δ minSENS (NOTE 3) | | +| Local Area BS | EIS REFSENS + 6 dB (NOTE 2) | -41 – Δ OTAREFSENS (NOTE 2) | See table 10.5.4.2-2 | +| | EIS minSENS + 6 dB (NOTE 3) | -41 – Δ minSENS (NOTE 3) | | + +NOTE 1: EISREFSENS and EISminSENS depend on the RAT, the BS class and on the *channel bandwidth*, see clauses 7.3 and 7.2. +NOTE 2: This test requirement is only applied in the OTA REFSENS conformance test directions. +NOTE 3: This test requirement is only applied in the OTA minSENS receiver target reference direction. + +**Table 7.5.5.3-2: Interfering signal for Narrowband blocking requirement** + +| E-UTRA channel BW of the lowest/highest carrier received [MHz] | Interfering RB centre frequency offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [kHz] | Type of interfering signal | +|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| 1.4 | ±(252.5+m*180), m=0, 1, 2, 3, 4, 5 | 1.4 MHz E-UTRA signal, 1 RB (NOTE) | +| 3 | ±(247.5+m*180), m=0, 1, 2, 3, 4, 7, 10, 13 | 3 MHz E-UTRA signal, 1 RB (NOTE) | +| 5 | ±(342.5+m*180), m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz E-UTRA signal, 1 RB (NOTE) | +| 10 | ±(347.5+m*180), m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz E-UTRA signal, 1 RB (NOTE) | +| 15 | ±(352.5+m*180), m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz E-UTRA signal, 1 RB (NOTE) | +| 20 | ±(342.5+m*180), m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz E-UTRA signal, 1 RB (NOTE) | + +NOTE: Interfering signal consisting of one resource block is positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the lower/upper Base Station RF Bandwidth edge. + +**Table 7.5.5.3-3: Adjacent channel selectivity for Wide Area BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE) | Interfering signal mean power [dBm] | Interfering signal centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of interfering signal | +|-----------------------------------------------------------------------|---------------------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1.4 | EIS minSENS + 11 dB | -52 – Δ minSENS | ±0.7025 | 1.4 MHz E-UTRA signal | +| 3 | EIS minSENS + 8 dB | -52 – Δ minSENS | ±1.5075 | 3 MHz E-UTRA signal | +| 5 | EIS minSENS + 6 dB | -52 – Δ minSENS | ±2.5025 | 5 MHz E-UTRA signal | +| 10 | EIS minSENS + 6 dB | -52 – Δ minSENS | ±2.5075 | 5 MHz E-UTRA signal | +| 15 | EIS minSENS + 6 dB | -52 – Δ minSENS | ±2.5125 | 5 MHz E-UTRA signal | +| 20 | EIS minSENS + 6 dB | -52 – Δ minSENS | ±2.5025 | 5 MHz E-UTRA signal | + +NOTE: EISminSENS depends on the *channel bandwidth* as specified see clause 7.2. + +**Table 7.5.5.3-4: Adjacent channel selectivity for Local Area BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering signal centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| 1.4 | EIS minSENS + 11 dB | -44 – Δ minSENS | ±0.7025 | 1.4 MHz E-UTRA signal | +| 3 | EIS minSENS + 8 dB | -44 – Δ minSENS | ±1.5075 | 3 MHz E-UTRA signal | +| 5 | EIS minSENS + 6 dB | -44 – Δ minSENS | ±2.5025 | 5 MHz E-UTRA signal | +| 10 | EIS minSENS + 6 dB | -44 – Δ minSENS | ±2.5075
±10.0175 | 5 MHz E-UTRA signal (NOTE 2)
20 MHz E-UTRA signal (NOTE 3) | +| 15 | EIS minSENS + 6 dB | -44 – Δ minSENS | ±2.5125 | 5 MHz E-UTRA signal | +| 20 | EIS minSENS + 6 dB | -44 – Δ minSENS | ±2.5025
±10.0175 | 5 MHz E-UTRA signal (NOTE 2)
20 MHz E-UTRA signal (NOTE 3) | + +NOTE 1: EISminSENS depends on the *channel bandwidth* as specified see clause 7.2. + +NOTE 2: This type of interfering signal is not applied for Band 46. + +NOTE 3: This type of interfering signal is only applied for Band 46. + +**Table 7.5.5.3-5: Adjacent channel selectivity for Medium Range BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering signal centre frequency offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| 1.4 | EIS minSENS + 11 dB | -47 – Δ minSENS | ±0.7025 | 1.4 MHz E-UTRA signal | +| 3 | EIS minSENS + 8 dB | -47 – Δ minSENS | ±1.5075 | 3 MHz E-UTRA signal | +| 5 | EIS minSENS + 6 dB | -47 – Δ minSENS | ±2.5025 | 5 MHz E-UTRA signal | +| 10 | EIS minSENS + 6 dB | -47 – Δ minSENS | ±2.5075
±10.0175 | 5 MHz E-UTRA signal (NOTE 2)
20 MHz E-UTRA signal (NOTE 3) | +| 15 | EIS minSENS + 6 dB | -47 – Δ minSENS | ±2.5125 | 5 MHz E-UTRA signal | +| 20 | EIS minSENS + 6 dB | -47 – Δ minSENS | ±2.5025
±10.0175 | 5 MHz E-UTRA signal (NOTE 2)
20 MHz E-UTRA signal (NOTE 3) | + +NOTE 1: EISminSENS depends on the *channel bandwidth* as specified see clause 7.2. + +NOTE 2: This type of interfering signal is not applied for Band 46. + +NOTE 3: This type of interfering signal is only applied for Band 46. + +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 clause 4.1.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 7.6 OTA Blocking + +### 7.6.1 General + +The blocking characteristics are a measure of the receiver unit ability to receive a wanted signal at the RIB at its assigned channel in the presence of an unwanted interferer. + +The requirement applies at the *RIB* when the AoA of the incident wave of the received signal and the interfering signal are the same direction and are within the *minSENS RoAoA* + +The wanted signal applies to each supported polarization, under the assumption of *polarization match*. The interferer shall be polarization matched for in-band frequencies and the polarization maintained for out-of-band frequencies. + +## 7.6.2 General Requirement + +### 7.6.2.1 Definition and applicability + +### 7.6.2.2 Minimum Requirement + +The minimum requirement for AAS BS in *MSR operation* is defined in TS 37.105 [6], clause 10.6.2. + +The minimum requirement for AAS BS in *single RAT UTRA operation* is defined in TS 37.105 [6], clause 10.6.3. + +The minimum requirement for AAS BS in *single RAT E-UTRA operation* is defined in TS 37.105 [6], clause 10.6.4. + +### 7.6.2.3 Test purpose + +The test stresses the ability of the receiver unit associated with the RIB under test to withstand high-level interference from unwanted signals at specified frequency bands, without undue degradation of its sensitivity. + +### 7.6.2.4 Method of test + +#### 7.6.2.4.1 Initial conditions + +Test environment: + +- normal; see annex G.2. + +RF channels to be tested for single carrier (SC): + +- M; see clause 4.12.1 + +*Base Station RF Bandwidth* positions to be tested for multi-carrier (MC): + +- $M_{\text{RFBW}}$ for *single-band RIB*, see clause 4.12.1, $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}^{\text{RFBW}}$ for *multi-band RIB*, see clause 4.12.1. + +In addition, for *multi-band RIB*: + +- For $B_{\text{RFBW\_T}}^{\text{RFBW}}$ , blocking testing above the highest operating band may be omitted. +- For $B'_{\text{RFBW\_T}}^{\text{RFBW}}$ , blocking testing below the lowest operating band may be omitted. + +Directions to be tested: + +- OTA REFSENS receiver target reference direction (see table 4.10-2, D11.30). + +#### 7.6.2.4.2 Procedure + +##### 7.6.2.4.2.1 General procedure + +- 1) Place *AAS BS* and the test antenna(s) according to Annex D.2.4. +- 2) Place test antenna(s) in reference direction (see table 4.10-1, D10.9) at far-field distance, aligned in all supported polarizations with the *AAS BS* as depicted in Annex D.2.4. +- 3) Connect test antenna(s) to the measurement equipment as shown in Annex D.2.4. +- 4) The test antenna(s) shall be dual (or single) polarized covering the same frequency ranges as the *AAS BS* and the blocking frequencies. If the test antenna does not cover both the wanted and interfering signal frequencies, separate test antennas for the wanted and interfering signal are required. + +- 5) The OTA blocking interferer is injected into the test antenna, with the blocking interferer producing specified interferer field strength level for each supported polarization. The interferer shall be *polarization matched* in-band and the polarization maintained for out-of-band frequencies. +- 6) The *AAS BS* receives the wanted signal and the interferer signal for supported polarization(s), in the reference direction (see table 4.10-1, D10.9) from the test antenna(s). + +#### 7.6.2.4.2.2 MSR operation + +- 1) Generate the wanted signal from the test antenna, according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the *RIB* under test as follows: + - For E-UTRA see clause A.1 in TS 36.141 [12]. + - For UTRA FDD see clause A.2 in TS 25.141 [10]. + - For NR see clause A.1 in TS 38.141-2 [34]. +- 2) Set the transmitter unit(s) associated with the *RIB* under test to transmit in reference direction (see table 4.10-1, D10.9) with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +The transmitter unit(s) associated with the *RIB* under test may be turned off for the out-of-band blocker tests when the frequency of the blocker is such that no IM2 or IM3 products fall inside the bandwidth of the wanted signal. + +- 3) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified for general test requirements in table 7.6.2.5.1-1 and, when applicable, for co-location test requirements in table 7.6.3.5.1-1. + +The distance between the test object and test antenna injecting the interferer signal is adjusted when necessary to ensure specified interferer signal level to be received. + +- 4) The CW interfering signal shall be swept with a step size of 1 MHz within the specified range. +- 5) Measure the performance of the wanted signal at the receiver unit associated with the *RIB*, as defined in the clause 7.6.5, for the relevant carriers specified by the test configuration in clause 4.11. +- 6) Repeat for all supported polarizations. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 7) For *multi-band RIB* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.6.2.4.2.3 Single RAT UTRA FDD operation + +- 1) Generate the wanted signal, from the test antenna, according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the *RIB* under test as shown in clause A.2.1 in TS 25.141 [10]. +- 2) Set the transmitter unit(s) associated with the *RIB* under test to transmit in reference direction (see table 4.10-1, D10.9) with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +The transmitter unit(s) associated with the *RIB* under test may be turned off for the out-of-band blocker tests when the frequency of the blocker is such that no IM2 or IM3 products fall inside the bandwidth of the wanted signal. + +- 3) Adjust the signal generators to the type of interfering signals and the frequency offsets as specified in tables 7.6.2.5.2-1 to 7.6.2.5.2-2 (in-band and narrowband blocking test requirements) and 7.6.3.5.2-1 (co-location test requirements). Note that the GMSK modulated interfering signal shall have an ACLR of at least 72 dB in order to eliminate the impact of interfering signal adjacent channel leakage power on the blocking characteristics measurement. For the tests defined in tables 7.6.2.5.2-1 to 7.6.2.5.2-2, the interfering signal shall be at a frequency offset $F_{uw}$ from the assigned channel frequency of the wanted signal which is given by: + +$$F_{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 centre frequency of the interfering signal covers the range from 1 MHz to 12.75 GHz. + +- 4) Measure the BER of the wanted signal at the receiver unit associated with the *RIB* under test. +- 5) Repeat for all supported polarizations. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 6) For *multi-band RIB* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.6.2.4.2.4 Single RAT E-UTRA operation + +- 1) Generate the wanted signal from the test antenna, according to the applicable test configuration (see clause 5) using applicable reference measurement channel to the *RIB* under test as shown in clause A.1 in TS 36.141 [6]. +- 2) Set the transmitter unit(s) associated with the *RIB* under test to transmit in reference direction (see table 4.10-1, D10.9) with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 5). + +The transmitter unit(s) associated with the *RIB* under test may be turned off for the out-of-band blocker tests when the frequency of the blocker is such that no IM2 or IM3 products fall inside the bandwidth of the wanted signal. + +- 3) Adjust the signal generators to the type of interfering signals and the frequency offsets as specified in tables 7.6.2.5.3-1 to 7.6.2.5.3-2 (in-band blocking test requirements), 7.6.3.5.3-1 (co-location test requirements). +- 4) The CW interfering signal shall be swept with a step size of 1 MHz within the specified range. +- 5) Measure the performance of the wanted signal at the receiver unit associated with the *RIB*, as defined in the clause 7.6.5, for the relevant carriers specified by the test configuration in clause 4.11. +- 6) Repeat for all supported polarizations. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 7) For *multi-band RIB* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.6.2.5 Test Requirement + +##### 7.6.2.5.1 MSR operation + +The OTA interfering signal RMS field-strength shall be set to 0.36 V/m at the base station *RIB* per polarization. + +NOTE: The RMS field-strength level in V/m is related to the interferer EIRP level at a distance described as + +$$E = \frac{\sqrt{30 \text{ EIRP}}}{r}, \text{ where EIRP is in W and } r \text{ is in m; for example, 0.36 V/m is equivalent to 36 dBm at fixed distance of 30 m.}$$ + +For a wanted and an interfering signal specified at the *RIB* using the parameters in table 7.6.2.5.1-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95 \%$ of the *maximum throughput* of the reference measurement channel defined in TS 36.104 [9], clause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], clause 7.2.1. + +- For any NR carrier, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel defined in TS 38.104 [33], clause 7.2.1. + +For *multi-band RIB*, the requirement applies for each supported operating band. The in-band blocking frequency ranges of all supported operating bands according to table 7.6.2.5.1-1 shall be excluded from the requirement. + +The OTA blocking requirement applies from $30\text{ MHz}$ to $F_{UL\_low} - \Delta f_{OOB}$ and from $F_{UL\_high} + \Delta f_{OOB}$ up to $12750\text{ MHz}$ , including the downlink frequency range of the FDD *operating band* for BS supporting FDD. $\Delta f_{OOB}$ is defined in clause 7.5.1. + +**Table 7.6.2.5.1-1: Blocking performance requirement** + +| Wanted signal mean power (dBm) | Interfering signal RMS field-strength (V/m) | Type of interfering signal | +|-----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|----------------------------| +| EIS minSENS + 6 dB
(Note 1) | 0.36 V/m | CW carrier | +| NOTE 1: EIS minSENS depends on the RAT, the BS class and the channel bandwidth , see TS 37.105 [6] clause 10.2. | | | +| NOTE 2: Void | | | + +### 7.6.2.5.2 Single RAT UTRA FDD operation + +In addition to the following in-band and narrowband requirements, the general minimum requirements relating to out of band blocking defined for MSR in clause 7.6.2.5.1-1 shall also be applied for single RAT UTRA operation. + +The minimum requirement for in-band blocking and narrowband blocking UTRA operation is defined below: + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges* applicable to each *RIB*. + +For *RIB* supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 15 MHz. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap* and is equal to -7.5 MHz/+7.5 MHz, respectively. + +For a *RIB* supporting operation in *non-contiguous spectrum* the narrowband blocking requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 400 kHz or 600 kHz, depending on the operating band. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap* and is equal to -200 kHz/+200 kHz or -300 kHz/+300 kHz, respectively. + +For *multi-band RIBs* the requirement in the in-band blocking frequency range applies for each supported operating band. The requirement applies in addition inside any *Inter RF Bandwidth gap*, in case *Inter RF Bandwidth gap* size is at least 15 MHz. The interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -7.5 MHz/+7.5 MHz, respectively. + +For *multi-band RIBs* the narrowband blocking requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least 400 kHz or 600 kHz, depending on the operating band. The interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -200 kHz/+200 kHz or -300 kHz/+300 kHz, respectively. + +For the wanted and interfering signal at the *RIB*, using the parameters in tables 7.6.2.5.2-1 and 7.6.2.5.2-2, the following requirements shall be met: + +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], clause 7.2.1. + +The OTA levels are applied referenced to two antenna gain offsets $\Delta_{OTAREFSENS}$ and $\Delta_{minSENS}$ . + +**Table 7.6.2.5.2-1: In-band blocking requirement for single RAT UTRA AAS BS** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|-------------------|----------------------------------------|----------------------------------------------|--------------------------------------|----------------------------| +| Wide Area BS | $-40 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | $\pm 10 \text{ MHz}$ | WCDMA signal (NOTE 1) | +| | $-40 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Medium Range BS | $-35 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-35 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Local Area BS | $-30 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-30 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | + +NOTE 1: The characteristics of the W-CDMA interference signal are specified in Annex C of TS 25.104 [2]. +NOTE 2: For *multi-band RIBs*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, and not in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to $-119.6 - \Delta_{\text{OTAREFSENS}}$ dBm or $-119.6 - \Delta_{\text{minSENS}}$ dBm as appropriate. + +NOTE: Table 7.6.2.5.2-1 assumes that two operating bands, where the downlink frequencies (see clause 4.6) of one band would be within the in-band blocking region of the other band, are not deployed in the same geographical area. + +**Table 7.6.2.5.2-2: Blocking performance requirement (narrowband) for single RAT UTRA AAS BS** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|-------------------|----------------------------------------|----------------------------------------------|------------------------------------------------------------------|----------------------------| +| Wide Area BS | $-47 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | $\pm 2.7 \text{ MHz}$ (NOTE 2)
$\pm 2.8 \text{ MHz}$ (NOTE 3) | GMSK modulated (NOTE 1) | +| | $-47 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Medium Range BS | $-42 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-42 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | +| Local Area BS | $-37 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | | | +| | $-37 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6 \text{ dB}$ | | | + +NOTE 1: GMSK modulation as defined in TS 45.004 [32]. +NOTE 2: applies for bands II, IV, V, VIII, X, XII, XIV, XXV, XXVI +NOTE 3: applies for bands III, VIII + +### 7.6.2.5.3 Single RAT E-UTRA operation + +In addition to the following in-band and narrowband requirements, the general minimum requirements relating to out of band blocking defined for MSR in clause 7.6.2.5.1-1 shall also be applied for single RAT E-UTRA operation. + +The minimum requirement for in-band blocking E-UTRA operation is defined below: + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges* applicable to each *RIB*. + +For *RIB* supporting operation in *non-contiguous spectrum*, the requirement applies in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least 15 MHz. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least 15 MHz. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted and interfering signal at the *RIB*, using the parameters in tables 7.6.2.5.3-1 and 7.6.2.5.3-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95 \%$ of the *maximum throughput* of the reference measurement channel defined in TS 36.104 [4], clause 7.2.1. + +The OTA levels are applied referenced to two antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +For *multi-band RIBs*, the requirement applies according to table 7.6.2.5.3-1 for the in-band blocking frequency ranges of each supported operating band. + +**Table 7.6.2.5.3-1: In-band blocking requirement for single RAT E-UTRA** + +| Base Station Type | Mean power of interfering signal [dBm] | Wanted Signal mean power [dBm] (NOTE 1,2) | Type of Interfering Signal | Interfering signal centre frequency minimum frequency offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap [MHz] | +|-------------------|----------------------------------------|-------------------------------------------|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Wide Area BS | $-43 - \Delta_{OTAREFSENS}$ | $EIS_{REFSENS} + 6$ dB | See
table 7.6.2.5.3-2 | See
table 7.6.2.5.3-2 | +| | $-43 - \Delta_{minSENS}$ | $EIS_{minSENS} + 6$ dB | | | +| Medium Range BS | $-38 - \Delta_{OTAREFSENS}$ | $EIS_{REFSENS} + 6$ dB | | | +| | $-38 - \Delta_{minSENS}$ | $EIS_{minSENS} + 6$ dB | | | +| Local Area BS | $-35 - \Delta_{OTAREFSENS}$ | $EIS_{REFSENS} + 6$ dB | | | +| | $-35 - \Delta_{minSENS}$ | $EIS_{minSENS} + 6$ dB | | | + +NOTE 1: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depend on the RAT, the BS class and on the *channel bandwidth*, see clauses 10.3 and 10.2 in TS 37.105 [6]. + +NOTE 2: For *multi-band RIBs*, in case of interfering signal that is not in the in-band blocking frequency range of the operating band where the wanted signal is present, and not in the in-band blocking frequency range of an adjacent or overlapping operating band, the wanted signal mean power is equal to $EIS_{REFSENS} + 1.4$ dB or $EIS_{minSENS} + 1.4$ dB as appropriate. + +**Table 7.6.2.5.3-2: Interfering signals for single RAT E-UTRA in-band blocking performance requirement** + +| E-UTRA channel BW of the lowest/highest carrier received [MHz] | Interfering signal centre frequency minimum offset to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [MHz] | Type of interfering signal | +|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 1.4 | $\pm 2.1$ | 1.4 MHz E-UTRA signal | +| 3 | $\pm 4.5$ | 3 MHz E-UTRA signal | +| 5 | $\pm 7.5$ | 5 MHz E-UTRA signal | +| 10 | $\pm 7.5$ | 5 MHz E-UTRA signal | +| 15 | $\pm 7.5$ | 5 MHz E-UTRA signal | +| 20 | $\pm 7.5$ | 5 MHz E-UTRA signal | +| 20 | $\pm 30$ | 20 MHz E-UTRA signal | + +## 7.6.3 Co-location Requirement + +### 7.6.3.1 Definition and applicability + +This additional blocking requirement may be applied for the protection of *AAS BS receivers* when E-UTRA BS, UTRA BS, NR BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with an AAS BS. + +The requirement is a co-location requirement. The interferer power levels are specified at the CLTA conducted input(s). + +Interfering signal shall be applied to the CLTA. The interfering power is specified per polarization. + +### 7.6.3.2 Minimum Requirement + +The minimum requirement for AAS BS in *MSR operation* is defined in TS 37.105 [6], clause 10.6.2. + +The minimum requirement for AAS BS in *single RAT UTRA operation* is defined in TS 37.105 [6], clause 10.6.3. + +The minimum requirement for AAS BS in *single RAT E-UTRA operation* is defined in TS 37.105 [6], clause 10.6.4. + +### 7.6.3.3 Test purpose + +The test stresses the ability of the receiver unit associated with the *RIB* under test to withstand high-level interference from unwanted signals at specified frequency bands, without undue degradation of its sensitivity. + +### 7.6.3.4 Method of test + +#### 7.6.3.4.1 Initial conditions + +Initial conditions according to clause 7.6.2.4.1. + +#### 7.6.3.4.2 Procedure + +- 1) Place *AAS BS* and CLTA as specified in clause 4.15, at the distance $d=0.1\text{m}$ . +- 2) Several CLTAs are required to cover the whole co-location blocking frequency ranges. +- 3) Place test antenna in reference direction (see table 4.10-1, D10.9) at far-field distance, aligned in all supported polarizations (single or dual) with the *AAS BS* as depicted in Annex D.2.4. +- 4) The test antenna shall be dual (or single) polarized, with the same frequency range as the *AAS BS*, for the co-location blocking test case. +- 5) Connect test antenna and CLTA to the measurement equipment as depicted in Annex D.2.4. +- 6) The *AAS BS* receives the wanted signal in all supported polarizations (single or dual), in the reference direction (see table 4.10-1, D10.9) from the test antenna. +- 7) The OTA co-location blocking interferer is injected into the CLTA. The CLTA is fed with the co-location blocking interferer. + +##### 7.6.3.4.2.1 MSR operation + +See clause 7.6.2.4.2.2. + +##### 7.6.3.4.2.2 Single RAT UTRA FDD operation + +See clause 7.6.2.4.2.3. + +##### 7.6.3.4.2.3 Single RAT E-UTRA operation + +See clause 7.6.2.4.2.4. + +### 7.6.3.5 Test Requirement + +#### 7.6.3.5.1 MSR operation + +This additional blocking requirement may be applied for the protection of *AAS BS receivers* when E-UTRA BS, UTRA BS, NR BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with an AAS BS. + +The requirement is a co-location requirement, the interferer power levels specified at the CLTA conducted input(s). + +The requirement is valid over *minSENS RoAoA*. + +Interfering signal shall be applied to the CLTA. The interfering power is specified per polarization. + +When the wanted and an interfering signal using the parameters in table 7.6.3.5.1-1, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in TS 36.104 [9], clause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], clause 7.2.1. +- For any NR carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in TS 38.104 [33], clause 7.2.1. + +**Table 7.6.3.5.1-1: Blocking requirement for co-location with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 – 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| GSM900 | 921 – 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| DCS1800 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| PCS1900 | 1930 – 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 – 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 – 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 – 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 – 885 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 – 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 – 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 - 1495.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 – 756 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 – 768 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 17 | 734 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 18 or NR Band n18 | 860 – 875 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 – 890 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 791 – 821 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 - 1510.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3 590 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1525 – 1559 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 – 1995 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 – 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 27 | 852 – 869 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 28 or NR band n28 | 758 – 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2350 – 2360 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 (NOTE-5) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 33 | 1900 – 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 34 or NR band n34 | 2010 – 2025 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 35 | 1850 – 1910 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 36 | 1930 – 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band c) or E-UTRA TDD Band 37 | 1910 – 1930 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2496 – 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 42 | 3400 – 3600 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 43 | 3600 – 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 44 | 703 – 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|----------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 49 | 3550 – 3700 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 51 or or NR band n51 | 1427– 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 52 | 3300 - 3400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 66 or or NR band n66 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 69 | 2570-2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 70 or or NR band n70 | 1995 - 2020 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 71 or or NR band n71 | 617 - 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 75 or or NR band n75 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 76 or or NR band n76 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n77 | 3300 - 4200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n78 | 3300 - 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n79 | 4400 - 5000 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 - 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 87 | 420 – 425 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 88 | 422 – 427 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n91 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n92 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n93 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n94 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|---------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| NR band n96 | 5925 - 7125 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n100 | 919.4- 925 | +46 | N/A | N/A | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n101 | 1900 - 1910 | +46 | N/A | N/A | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n102 | 5925 - 6425 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 103 | 757 – 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n104 | 6425 - 7125 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n105 | 612 – 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR Band n109 | 703 – 733 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +NOTE 1: $EIS_{minSENS}$ depends on the RAT, the BS class and on the *channel bandwidth*, see clauses 10.3 and 10.2 in TS 37.105; "x" is equal to 6 dB in case of E-UTRA or UTRA wanted signals. + +NOTE 2: Except for a BS operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported *uplink operating band* or in the $\Delta f_{OOB}$ immediately outside any of the supported *uplink operating band*. +For a BS operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768 - 797 MHz. + +NOTE 3: 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 or E-UTRA TDD or NR TDD with 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 [31]. + +NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805 - 1850 MHz. + +NOTE 5: For an AAS BS operating in band 11 or 21, this requirement applies for interfering signal within the frequency range 1475.9 - 1495.9 MHz. + +### 7.6.3.5.2 Single RAT UTRA FDD operation + +This additional blocking requirement may be applied for the protection of *AAS BS receivers* when E-UTRA BS, UTRA BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with an AAS BS. + +The requirement is a co-location requirement, the interferer power levels specified at the CLTA conducted input(s). + +The requirement is valid over *minSENS RoAoA*. + +Interfering signal shall be applied to the CLTA. The interfering power is specified per polarization. + +When the wanted and an interfering signal using the parameters in table 7.6.3.5.1-1 for co-location with UTRA or E-UTRA systems and table 7.6.3.5.2-1 for co-location with GSM systems, the following requirements shall be met: + +- For any UTRA FDD carrier, the BER shall not exceed 0.001 for the reference measurement channel defined in TS 25.104 [2], clause 7.2.1. + +**Table 7.6.3.5.2-1: UTRA additional OTA blocking requirement for co-location with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 – 894 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| GSM900 | 921 – 960 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| DCS1800 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| PCS1900 | 1930 – 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 – 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 – 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 – 894 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 – 885 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 – 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 – 960 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 - 1495.9 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 – 756 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 – 768 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 17 | 734 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| E-UTRA Band 18 or NR Band n18 | 860 – 875 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 – 890 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 791 – 821 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 - 1510.9 | +46 | +38 | +24 | $EIS_{minSENS} + x \text{ dB}$ (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3 590 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1525 – 1559 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 – 1995 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 – 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 27 | 852 – 869 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 28 or NR band n28 | 758 – 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 29 or NR band n29 | 717 – 728 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2350 – 2360 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 (NOTE-5) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 33 | 1900 – 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 34 or NR band n34 | 2010 – 2025 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 35 | 1850 – 1910 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 36 | 1930 – 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band c) or E-UTRA TDD Band 37 | 1910 – 1930 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2496 – 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 42 | 3400 – 3600 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 43 | 3600 – 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 44 | 703 – 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|----------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 49 | 3550 – 3700 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 51 or or NR band n51 | 1427– 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 52 | 3300 - 3400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 66 or or NR band n66 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 69 | 2570-2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 70 or or NR band n70 | 1995 - 2020 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 71 or or NR band n71 | 617 - 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 75 or or NR band n75 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 76 or or NR band n76 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n77 | 3300 - 4200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n78 | 3300 - 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n79 | 4400 - 5000 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 87 | 420 – 425 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 88 | 422 – 427 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n91 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n92 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n93 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n94 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|---------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| NR band n96 | 5925 - 7125 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n100 | 919.4- 925 | +46 | N/A | N/A | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n101 | 1900 - 1910 | +46 | N/A | N/A | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n102 | 5925 - 6425 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 103 | 757 – 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n104 | 6425 - 7125 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n105 | 612 – 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR Band n109 | 703 – 733 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +NOTE 1: $EIS_{minSENS}$ depends on the BS class and on the *channel bandwidth*, see clauses 10.2 in TS 37.105; "x" is equal to 6 dB in case of UTRA wanted signals. + +NOTE 2: Except for a BS operating in Band XIII, these requirements do not apply when the interfering signal falls within any of the supported *uplink operating band* or in the 10 MHz immediately outside any of the supported *uplink operating band*. +For a BS operating in band XIII the requirements do not apply when the interfering signal falls within the frequency range 768 - 797 MHz. + +NOTE 3: 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 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 [31]. + +NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805 - 1850 MHz. + +NOTE 5: For an AAS BS operating in band XI, this requirement applies for interfering signal within the frequency range 1475.9 - 1495.9 MHz. + +### 7.6.3.5.3 Single RAT E-UTRA operation + +This additional blocking requirement may be applied for the protection of *AAS BS receivers* when E-UTRA BS, UTRA BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with an AAS BS. + +The requirement is a co-location requirement, the interferer power levels specified at the CLTA conducted input(s). + +The requirement is valid over *minSENS RoAoA*. + +Interfering signal shall be applied to the CLTA. The interfering power is specified per polarization. + +When the wanted and an interfering signal using the parameters in table 7.6.3.5.1-1 for co-location with UTRA or E-UTRA systems and table 7.6.3.5.3-1 for co-location with GSM systems, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in TS 36.104 [9], clause 7.2.1. + +**Table 7.6.3.5.3-1: E-UTRA additional OTA blocking requirement for co-location with BS in other frequency bands** + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-----------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| GSM850 or CDMA850 | 869 – 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| GSM900 | 921 – 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| DCS1800 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| PCS1900 | 1930 – 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band I or E-UTRA Band 1 or NR band n1 | 2110 – 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band II or E-UTRA Band 2 or NR band n2 | 1930 – 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band III or E-UTRA Band 3 or NR band n3 | 1805 - 1880 (NOTE 4) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band V or E-UTRA Band 5 or NR band n5 | 869 – 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VI or E-UTRA Band 6 | 875 – 885 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VII or E-UTRA Band 7 or NR band n7 | 2620 – 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR band n8 | 925 – 960 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 - 1879.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XI or E-UTRA Band 11 | 1475.9 - 1495.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XII or E-UTRA Band 12 or NR band n12 | 729 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR band n13 | 746 – 756 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 – 768 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 17 | 734 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 18 or NR Band n18 | 860 – 875 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XIX or E-UTRA Band 19 | 875 – 890 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XX or E-UTRA Band 20 or NR band n20 | 791 – 821 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1495.9 - 1510.9 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-------------------------------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3 590 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 24 or NR band n24 | 1525 – 1559 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 – 1995 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 – 894 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 27 | 852 – 869 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 28 or NR band n28 | 758 – 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 29 or NR band n29 | 717 – 728 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 30 or NR band n30 | 2350 – 2360 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 31 or NR Band n31 | 462.5 - 467.5 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 (NOTE-5) | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 33 | 1900 – 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band a) or E-UTRA TDD Band 34 or NR band n34 | 2010 – 2025 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 35 | 1850 – 1910 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band b) or E-UTRA TDD Band 36 | 1930 – 1990 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band c) or E-UTRA TDD Band 37 | 1910 – 1930 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band d) or E-UTRA Band 38 or NR band n38 | 2570 – 2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| UTRA TDD Band e) or E-UTRA Band 40 or NR band n40 | 2300 – 2400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 41 or NR band n41 | 2496 – 2690 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 42 | 3400 – 3600 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 43 | 3600 – 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 44 | 703 – 803 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 45 | 1447 - 1467 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|-------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| E-UTRA Band 46 or NR Band n46 | 5150 - 5925 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 49 | 3550 – 3700 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 51 or NR band n51 | 1427– 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 52 | 3300 – 3400 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 65 or NR band n65 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 66 or NR band n66 | 2110 – 2200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 67 or NR band n67 | 738 - 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 68 | 753 - 783 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 69 | 2570-2620 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 70 or NR band n70 | 1995 - 2020 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 71 or NR band n71 | 617 - 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 72 or NR Band n72 | 461 - 466 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 73 | 460 - 465 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 74 or NR band n74 | 1475 - 1518 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 75 or NR band n75 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 76 or NR band n76 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n77 | 3300 - 4200 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n78 | 3300 - 3800 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n79 | 4400 - 5000 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 85 or NR band n85 | 728 – 746 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 87 | 420 – 425 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 88 | 422 – 427 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n91 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n92 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n93 | 1427 - 1432 | N/A | N/A | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n94 | 1432 - 1517 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +| Type of co-located BS | Centre Frequency of Interfering Signal [MHz] | Interfering Signal mean power for WA BS [dBm] | Interfering Signal mean power for MR BS [dBm] | Interfering Signal mean power for LA BS [dBm] | Wanted Signal mean power [dBm] | Type of Interfering Signal | +|---------------------------------|----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|---------------------------------|----------------------------| +| NR band n96 | 5925 - 7125 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n100 | 919.4- 925 | +46 | N/A | N/A | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n101 | 1900 - 1910 | +46 | N/A | N/A | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n102 | 5925 - 6425 | N/A | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 103 | 757 – 758 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n104 | 6425 - 7125 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR band n105 | 612 – 652 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | +| NR Band n109 | 703 – 733 | +46 | +38 | +24 | $EIS_{minSENS} + x$ dB (NOTE 1) | CW carrier | + +NOTE 1: $EIS_{minSENS}$ depends on the BS class and on the *channel bandwidth*, see clauses 10.2 in TS 37.105; "x" is equal to 6 dB in case of E-UTRA wanted signals. + +NOTE 2: Except for a BS operating in Band 13, these requirements do not apply when the interfering signal falls within any of the supported *uplink operating band* or in the 10 MHz immediately outside any of the supported *uplink operating band*. +For a BS operating in band 13 the requirements do not apply when the interfering signal falls within the frequency range 768 - 797 MHz. + +NOTE 3: 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 E-UTRA TDD with 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 [31]. + +NOTE 4: In China, the blocking requirement for co-location with DCS1800 and Band III BS is only applicable in the frequency range 1805 - 1850 MHz. + +NOTE 5: For an AAS BS operating in band 11 or 21, this requirement applies for interfering signal within the frequency range 1475.9 - 1495.9 MHz. + +## 7.7 OTA Receiver spurious emissions + +### 7.7.1 Definition and applicability + +The receiver spurious emission requirement is the power of the emissions radiated from the antenna array from a receiver unit. For an *OTA AAS BS* operating in FDD, OTA RX spurious emissions requirement do not apply as they are superseded by the OTA TX spurious emissions requirement. This is due to the fact that TX and RX spurious emissions cannot be distinguished in OTA domain. + +NOTE: The OTA receiver spurious emission requirement applicability for the AAS BS with the RX-only capabilities is FFS. + +For an *OTA AAS BS* operating in TDD, the OTA receiver spurious emissions requirement applies during the *transmitter OFF period* only. + +For RX only *multi-band RIB*, the RX spurious emissions requirements are subject to exclusion zones in each supported operating band. + +### 7.7.2 Minimum Requirement + +For an MSR AAS BS the minimum requirement is in TS 37.105 [6], clause 10.7.2 + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.7.4 + +For single RAT UTRA AAS BS the minimum requirement is in TS 37.105 [6], clause 10.7.3 + +### 7.7.3 Test purpose + +The test purpose is to verify the receiver radiated spurious emissions from the AAS BS at the RIB are within the specified requirements. + +### 7.7.4 Method of test + +#### 7.7.4.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested for single carrier: M; see clause 4.12.1. + +RF bandwidth positions to be tested in single-band operation: - $M_{RFBW}$ , see clause 4.12.1, + +RF bandwidth positions to be tested in multi-band operation, see clause 4.12.1. + +- $B_{RFBW\_T'_{RFBW}}$ when testing from $F_{DL\_Blow\_low} - \Delta f_{OBUE}$ +- $B'_{RFBW\_T_{RFBW}}$ when testing from $F_{DL\_Bhigh\_high} + \Delta f_{OBUE}$ to 12.75 GHz (or to 5th harmonic) +- $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ when testing from $F_{DL\_Blow\_high} + \Delta f_{OBUE}$ to $F_{DL\_Bhigh\_low} - \Delta f_{OBUE}$ + +Directions to be tested: Not applicable as Rx only TRP measurement. + +#### 7.7.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in Annex F. An alternative method to measure TRP is to use a characterized and calibrated reverberation chamber. If so, follow steps 1, 3, 4, 5, 7 and 10. When calibrated and operated within the guidance of 3GPP TR 37.941 [38] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the AAS BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (see table 4.10-1, D9.2) of the AAS BS with the test system. +- 3) Measurements shall use a measurement bandwidth in accordance to the conditions in TS 37.104 [5] clause 6.6.1. +- 4) The measurement device characteristics shall be: + - Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.3-1. + +- 5) Set the TDD AAS BS to receive only +- 6) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex F). +- 7) Measure the emission at the specified frequencies with specified measurement bandwidth +- 8) Repeat step 6-9 for all directions in the appropriated TRP measurement grid needed for full TRP estimation (see annex F). + +NOTE 1: The TRP measurement grid may not be the same for all measurement frequencies. + +NOTE 2: The frequency sweep or the TRP measurement grid sweep may be done in any order. + +- 9) Calculate TRP at each specified frequency using the directional measurements. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 10) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 7.7.5 Test Requirement + +The TRP of any spurious emission shall not exceed the limits in table 7.7.5-1: + +**Table 7.7.5-1: Receiver spurious emission test requirement** + +| Frequency range | Maximum level
(Note 2, Note 3) | Measurement
bandwidth | NOTE | +|--------------------------------------------------------------------------------------------------|-----------------------------------|--------------------------|----------------------------------------| +| 30 MHz - 1 GHz | -36 + X dBm | 100 kHz | | +| 1 GHz - 12.75 GHz | -30 + X dBm | 1 MHz | | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -30 + X dBm | 1 MHz | Applies only for Bands 22, 42, 43, 48. | + +NOTE 1: The frequency range between $2.5 \cdot \text{channel bandwidth}$ below the first carrier frequency and $2.5 \cdot \text{channel bandwidth}$ above the last carrier frequency transmitted by the AAS BS may be excluded from the requirement. However, frequencies that are more than $\Delta_{\text{ROBUE}}$ below the lowest frequency of any of the AAS BS supported *downlink operating band* or more than $\Delta_{\text{ROBUE}}$ above the highest frequency of any of the AAS BS supported *downlink operating band* shall not be excluded from the requirement. For a *multiband RIB*, the exclusion applies for all supported operating bands. + +NOTE 2: X = 9 dB, unless stated differently in regional regulation. + +NOTE 3: Additional limits may apply regionally. + +In addition to the requirements in table 7.7.5-1, the power of any spurious emission shall not exceed the levels specified for Protection of the E-UTRA FDD BS receiver of own or different BS in clause 6.7.6.3 and for Co-existence with other systems in the same geographical area in clause 6.7.6.4. In addition, the co-existence requirements for co-located base stations specified in clause 6.7.6.5 may also be applied. + +## 7.8 OTA Receiver intermodulation + +### 7.8.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 receiver unit to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. + +The requirement applies at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction, and: + +- when the wanted signal is based on $\text{EIS}_{\text{REFSENS}}$ : the AoA of the incident wave of a received signal and the interfering signal are within the OTA REFSENS *RoAoA*. +- when the wanted signal is based on $\text{EIS}_{\text{minSENS}}$ : the AoA of the incident wave of a received signal and the interfering signal are within the *minSENS RoAoA*. + +The wanted and interfering signals apply to each supported polarization, under the assumption of *polarization match*. + +### 7.8.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 10.8.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.8.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.8.4. + +## 7.8.3 Test purpose + +The test purpose is to verify the ability of the 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.8.4 Method of test + +### 7.8.4.1 Initial conditions + +Test environment: normal; see annex G.2. + +RF channels to be tested for single carrier: M; see clause 4.12.1. + +*Base Station RF Bandwidth* positions to be tested: For *single-band RIB(s)*: $M_{\text{RFBW}}$ if ATC4 is applicable; $B_{\text{RFBW}}$ and $T_{\text{RFBW}}$ for other ATC, see clause 4.12.1. For *multi-band RIB(s)*: $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ , see clause 4.12.1. + +Directions to be tested: OTA REFSENS receiver target reference direction (see table 4.10-20 D11.30). + +### 7.8.4.2 Procedure + +#### 7.8.4.2.1 General procedure + +The general procedure steps apply to the procedures for all the RATs. + +- 1) Place the AAS BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in Annex D2.6. +- 2) Align the manufacturer declared coordinate system orientation of the AAS BS with the test system. +- 3) Align the BS with the test antenna in the declared direction to be tested. +- 4) Align the NR BS to that the wanted signal and interferer signal is *polarization matched* with the test antenna(s). +- 5) Configure the beam peak direction of the AAS BS according to declared *reference beam direction pair* for the appropriate beam identifier. +- 6) Set the AAS BS to transmit the beam(s) of the same operational band and RAT as the OSDD being tested according to the appropriate test configuration in clause 5. +- 7) Set the test signal mean power so the calibrated radiated power at the AAS BS Antenna Array coordinate system reference point is as specified as follows: + +Set the signal generator for the wanted signal according to the applicable test configuration (see clause 5) using applicable reference measurement channel to transmit: + +- For E-UTRA see clause A.1 in TS 36.141 [12]. +- For UTRA FDD see clause A.2 in TS 25.141 [10]. +- For NR see clause A.1 in TS 38.141-2 [34]. + +#### 7.8.4.2.2 MSR operation + +##### 7.8.4.2.2.1 Procedure for general and narrowband intermodulation + +- 1) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified in table 7.8.5.1.1-1 and Table 7.7.5.1.1-2 for general intermodulation requirement, and Table 7.8.5.1.2-1 and Table 7.8.5.1.2-2 for narrowband intermodulation requirement. +- 2) Measure the performance of the wanted signal at the receiver under test, as defined in clause 7.8.5.1.1 and 7.8.5.1.2, for the relevant carriers specified by the test configuration in clause 5. + +- 3) Repeat for all supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 4) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.8.4.2.3 Single RAT UTRA FDD operation + +- 1) Generate the wanted signal (reference signal) and adjust ATT1 to set the signal level to the level specified in table 7.8.5.2-1. For a RIB supporting multi-carrier operation, generate the wanted signal according to the applicable test configuration (see clause 4.11) using applicable reference measurement channel. Power settings are specified in table 7.8.5.2-1. +- 2) Adjust the signal generators to the type of interfering signals and the frequency offsets as specified in tables 7.8.5.2-1 and 7.8.5.2-2. Note that the GMSK modulated interfering signal shall have an ACLR of at least 72 dB in order to eliminate the impact of interfering signal adjacent channel leakage power on the intermodulation characteristics measurement. +- 3) Adjust the ATT2 and ATT3 to obtain the specified level of interfering signal at the RIB. +- 4) Measure the BER of the wanted signal. For a RIB supporting multi-carrier operation the BER shall be measured for all relevant carriers specified by the test configuration. +- 5) Repeat for all supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 6) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +#### 7.8.4.2.4 Single RAT E-UTRA operation + +- 1) Generate the wanted signal using the applicable test configuration specified in clause 5 and adjust the signal level to the level specified in table 7.8.5.3-1. +- 2) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified in table 7.8.5.3-2 for intermodulation requirement and Table 7.8.5.3-3, Table 7.8.5.3-4 and Table 7.8.5.3-5 for narrowband intermodulation requirement. +- 3) Adjust the signal generators to obtain the specified level of interfering signal. +- 4) Measure the throughput according to annex E of 36.141 [12]TS 36.141 [12], for multi-carrier and/or CA operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clause 5. +- 5) Repeat for all supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 6) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +### 7.8.5 Test Requirement + +#### 7.8.5.1 MSR operation + +##### 7.8.5.1.1 General intermodulation test requirement + +Interfering signals shall be a CW signal and an E-UTRA, NR or UTRA signal as specified in TS 37.104 [5], annex A. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap* at those connectors, in case the gap size is at least twice as wide as the UTRA/E-UTRA interfering signal centre frequency offset from the *Base Station RF Bandwidth edge*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted signal at the assigned channel frequency and two interfering signals at the RIB, using the parameters in tables 7.8.5.1.1-1 and 7.8.5.1.1-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in TS 36.104 [4], clause 7.2.1. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in TS 25.104 [2], clause 7.2.1. +- For any NR carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in TS 38.104 [33], clause 7.2.2. + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +**Table 7.8.5.1.1-1: General intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE 1) | Type of interfering signal | +|-------------------|-------------------------------------------------|----------------------------------------------------------|----------------------------| +| Wide Area BS | $-48 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 6) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 2, 5) | See table 7.8.5.1.1-2 | +| | $-48 + y - \Delta_{\text{minSENS}}$ (NOTE 6) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 2, 5) | | +| Medium Range BS | $-44 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 6) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 3, 5) | | +| | $-44 + y - \Delta_{\text{minSENS}}$ (NOTE 6) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 3, 5) | | +| Local Area BS | $-38 + y - \Delta_{\text{OTAREFSENS}}$ (NOTE 6) | $\text{EIS}_{\text{REFSENS}} + x \text{ dB}$ (NOTE 4, 5) | | +| | $-38 + y - \Delta_{\text{minSENS}}$ (NOTE 6) | $\text{EIS}_{\text{minSENS}} + x \text{ dB}$ (NOTE 4, 5) | | + +NOTE 1: $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{minSENS}}$ depend on the RAT, the BS class and on the *channel bandwidth*, see clauses 7.3 and 7.2. + +NOTE 2: For WA BS supporting UTRA, "x" is equal to 6. + +NOTE 3: For MR BS supporting UTRA, "x" is equal to 6 in case of UTRA wanted signals, 9 in case of E-UTRA. + +NOTE 4: For LA BS supporting UTRA, "x" is equal to 12 in case of NR or E-UTRA wanted signals, 6 in case of UTRA wanted signal. + +NOTE 5: For a BS not supporting UTRA, x is equal to 6 for all BS classes if NR is supported, otherwise x is equal to 6 for WA BS or 9 for MR or 12 for LA BS if NR is not supported. + +NOTE 6: For a BS that supports NR but not UTRA; "y" is equal to -4 for the WA BS class, -3 for the MR BS class and -6 for the LA BS class. For all other cases, "y" is equal to zero for all BS classes. + +**Table 7.8.5.1.1-2: Interfering signals for intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge | Interfering signal centre frequency offset from the Base Station RF Bandwidth edge [MHz] | Type of interfering signal | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------------------| +| E-UTRA 1.4 MHz | ±2,0 (BC1 and BC3) / ±2,1 (BC2) | CW | +| | ±4,9 | 1,4 MHz E-UTRA signal | +| E-UTRA 3 MHz | ±4,4 (BC1 and BC3) / ±4,5 (BC2) | CW | +| | ±10,5 | 3 MHz E-UTRA signal | +| UTRA FDD and E-UTRA 5 MHz | ±7,5 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| E-UTRA 10 MHz | ±7,375 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| E-UTRA 15 MHz | ±7,25 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| E-UTRA 20 MHz | ±7,125 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| GSM/EDGE | ±7,575 | CW | +| | ±17,5 | 5 MHz E-UTRA signal | +| 1,28 Mcps UTRA TDD | ±2,3 (BC3) | CW | +| | ±5,6 (BC3) | 1,28 Mcps UTRA TDD signal | +| NR 5 MHz | ±7.5 | CW | +| | ±17.5 | 5 MHz E-UTRA signal | +| NR 10 MHz | ±7.465 | CW | +| | ±17.5 | 5 MHz E-UTRA signal | +| NR 15 MHz | ±7.43 | CW | +| | ±17.5 | 5 MHz E-UTRA signal | +| NR 20 MHz | ±7.395 | CW | +| | ±17.5 | 5 MHz E-UTRA signal | +| NR 25 MHz | ±7.465 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 30 MHz | ±7.43 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 35 MHz | ±7.44 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 40 MHz | ±7.45 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 45 MHz | ±7.37 | CW | +| | ±25 | 20MHz E-UTRA signal | +| NR 50 MHz | ±7.35 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 60 MHz | ±7.49 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 70 MHz | ±7.42 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 80 MHz | ±7.44 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 90 MHz | ±7.46 | CW | +| | ±25 | 20 MHz E-UTRA signal | +| NR 100 MHz | ±7.48 | CW | +| | ±25 | 20 MHz E-UTRA signal | + +### 7.8.5.1.2 General narrowband intermodulation test requirement + +Interfering signals shall be a CW signal and an E-UTRA 1RB signal as specified in TS 37.104 [5], annex A. + +The requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIB supporting operation in *non-contiguous spectrum* within each supported operating band, the requirement applies in addition inside any *sub-block gap* in case the *sub-block gap* is at least as wide as the *channel bandwidth* of the E-UTRA interfering signal in table 7.8.5.1.2-2. The interfering signal offset is defined relative to the *sub-block* edges inside the gap. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least as wide as the E-UTRA interfering signal in table 7.8.5.1.2-2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +For the wanted signal at the assigned channel frequency and two interfering signals at the RIB, using the parameters in tables 7.8.5.1.2-1 and 7.8.5.1.2-2, the following requirements shall be met: + +- For any E-UTRA carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in TS 36.104 [4], clause 7.2.5.3. +- For any UTRA FDD carrier, the BER shall not exceed 0,001 for the reference measurement channel defined in TS 25.104 [2], clause 7.2.5.1. +- For any NR carrier, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel defined in TS 38.104 [33], clause 7.2.5.3. + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +**Table 7.8.5.1.2-1: General narrowband intermodulation requirement** + +| Base Station Type | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Type of interfering signal | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------|----------------------------| +| Wide Area BS | $-52 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6$ dB | See table 7.8.5.1.2-2 | +| | $-52 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6$ dB | | +| Medium Range BS | $-47 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6$ dB | | +| | $-47 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6$ dB | | +| Local Area BS | $-44 - \Delta_{\text{OTAREFSENS}}$ | $\text{EIS}_{\text{REFSENS}} + 6$ dB | | +| | $-44 - \Delta_{\text{minSENS}}$ | $\text{EIS}_{\text{minSENS}} + 6$ dB | | +| NOTE $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{minSENS}}$ depend on the RAT, the BS class and on the channel bandwidth , see clauses 10.3 and 10.2. | | | | + +**Table 7.8.5.1.2-2: Interfering signals for narrowband intermodulation requirement** + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge or edge of the sub-block | CW or 1RB interfering signal centre frequency offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap [kHz] | Type of interfering signal | +|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| E-UTRA 1.4 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±970 (BC1 and BC3) / ±790 (BC2) | 1,4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 3 MHz | ±260 (BC1 and BC3) / ±270 (BC2) | CW | +| | ±960 (BC1 and BC3) / ±780 (BC2) | 3,0 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 5 MHz | ±360 | CW | +| | ±1 060 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 10 MHz (NOTE 2) | ±325 | CW | +| | ±1 240 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 15 MHz (NOTE 2) | ±380 | CW | +| | ±1 600 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| E-UTRA 20 MHz (NOTE 2) | ±345 | CW | +| | ±1 780 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| UTRA FDD | ±345 (BC1 and BC2) | CW | +| | ±1 780 (BC1 and BC2) | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| GSM/EDGE | ±340 | CW | +| | ±880 | 5 MHz E-UTRA signal, 1 RB (NOTE 1) | +| 1,28 Mcps UTRA TDD | ±190 (BC3) | CW | +| | ±970 (BC3) | 1,4 MHz E-UTRA signal, 1 RB (NOTE 1) | +| NR 5 MHz | ±360 | CW | +| | ±1420 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 10 MHz | ±370 | CW | +| | ±1960 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 15 MHz (Note 2) | ±380 | CW | +| | ±1960 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 20 MHz (Note 2) | ±390 | CW | +| | ±2320 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 25 MHz (Note 2) | ±325 | CW | +| | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 30 MHz (Note 2) | ±335 | CW | +| | ±2350 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 35 MHz (Note 2) | ±345 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 40 MHz (Note 2) | ±355 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 45 MHz (Note 2) | ±365 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 50 MHz (Note 2) | ±375 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 60 MHz (Note 2) | ±395 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 70 MHz (Note 2) | ±415 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 80 MHz (Note 2) | ±435 | CW | +| | ±2710 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 90 MHz | ±365 | CW | + +| RAT of the carrier adjacent to the upper/lower Base Station RF Bandwidth edge or edge of the sub-block | CW or 1RB interfering signal centre frequency offset from the Base Station RF Bandwidth edge or edge of sub-block inside a gap [kHz] | Type of interfering signal | +|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| (Note 2) | ±2530 | E-UTRA signal, 1 RB (NOTE 1) | +| NR 100 MHz
(Note 2) | ±385 | CW | +| | ±2530 | E-UTRA signal, 1 RB (NOTE 1) | + +NOTE 1: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the Base Station RF Bandwidth edge. + +NOTE 2: This requirement shall apply only for an E-UTRA FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals. + +### 7.8.5.2 Single RAT UTRA operation + +The static reference performance as specified in clause 10.3 and 10.2 shall be met for a Wide Area BS when the signals in table 7.8.5.2-1 and table 7.8.5.2-2 are at the RIB. + +The static reference performance as specified in clause 10.3 and 10.2 shall be met for a Medium range BS when the signals in table 7.8.5.2-3 and table 7.8.5.2-4 are at the RIB. + +The static reference performance as specified in clause 10.3 and 10.2 shall be met for a Local Area BS when the signals in table 7.8.5.2-5 and table 7.8.5.2-6 are at the RIB. + +For RIB supporting operation in *non-contiguous spectrum* within each supported operating band, the requirement applies in addition inside any *sub-block gap* in case the *sub-block gap* is at least 6.8 MHz. The CW interfering signal offset is defined relative to the lower/upper *sub-block* edge inside the *sub-block gap* and is equal to -1 MHz/+1 MHz, respectively. The GMSK modulated interfering signal offset is defined relative to the lower/upper *sub-block* edge inside the *sub-block gap* and is equal to -3.4 MHz/+3.4 MHz, respectively. + +For *multi-band RIBs*, the requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least 6.8 MHz. The CW interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -1 MHz/+1 MHz, respectively. The GMSK modulated interfering signal offset is defined relative to lower/upper *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap* and is equal to -3.4 MHz/+3.4 MHz, respectively. + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +**Table 7.8.5.2-1: Intermodulation performance requirement (Wide Area BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signal | +|----------------|-----------------------------------------|---------------------------------------|---------|----------------------------| +| All bands | $-48 - \Delta_{\text{OTAREFSENS}}$ | $-115 - \Delta_{\text{OTAREFSENS}}$ | ±10 MHz | CW signal | +| | $-48 - \Delta_{\text{minSENS}}$ | $-115 - \Delta_{\text{minSENS}}$ | | | +| | $-48 - \Delta_{\text{OTAREFSENS}}$ | $-115 - \Delta_{\text{OTAREFSENS}}$ | ±20 MHz | WCDMA signal (NOTE) | +| | $-48 - \Delta_{\text{minSENS}}$ | $-115 - \Delta_{\text{minSENS}}$ | | | + +NOTE: The characteristics of the WCDMA interference signal are specified in TS 25.104 [2] Annex C. + +**Table 7.8.5.2-2: Narrowband intermodulation performance requirement (Wide Area BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signal | +|----------------------------------------------------|-----------------------------------------|---------------------------------------|---------------|----------------------------| +| II, III, IV, V, VIII, X, XII, XIII, XIV, XXV, XXVI | - 47 - $\Delta_{\text{OTAREFSENS}}$ | - 115 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 3.5$ MHz | CW signal | +| | -47 - $\Delta_{\text{minSENS}}$ | -115 - $\Delta_{\text{minSENS}}$ | | | +| | - 47 - $\Delta_{\text{OTAREFSENS}}$ | - 115 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 5.9$ MHz | GMSK modulated (NOTE) | +| | -47 - $\Delta_{\text{minSENS}}$ | -115 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: GMSK as defined in TS45.004 [32] | | | | | + +**Table 7.8.5.2-3: Intermodulation performance requirement (Medium Range BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signal | +|----------------------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------|--------------|----------------------------| +| All bands | - 44 - $\Delta_{\text{OTAREFSENS}}$ | - 105 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 10$ MHz | CW signal | +| | -44 - $\Delta_{\text{minSENS}}$ | -105 - $\Delta_{\text{minSENS}}$ | | | +| | - 44 - $\Delta_{\text{OTAREFSENS}}$ | - 105 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 20$ MHz | WCDMA signal (NOTE) | +| | -44 - $\Delta_{\text{minSENS}}$ | -105 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: The characteristics of the WCDMA interference signal are specified in TS 25.104 [2] Annex C. | | | | | + +**Table 7.8.5.2-4: Narrowband intermodulation performance requirement (Medium Range BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signal | +|----------------------------------------------------|-----------------------------------------|---------------------------------------|---------------|----------------------------| +| II, III, IV, V, VIII, X, XII, XIII, XIV, XXV, XXVI | - 43 - $\Delta_{\text{OTAREFSENS}}$ | - 105 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 3.5$ MHz | CW signal | +| | -43 - $\Delta_{\text{minSENS}}$ | -105 - $\Delta_{\text{minSENS}}$ | | | +| | - 43 - $\Delta_{\text{OTAREFSENS}}$ | - 105 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 5.9$ MHz | GMSK modulated (NOTE) | +| | -43 - $\Delta_{\text{minSENS}}$ | -105 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: GMSK as defined in TS45.004 [32] | | | | | + +**Table 7.8.5.2-5: Intermodulation performance requirement (Local Area BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signal | +|----------------------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------|--------------|----------------------------| +| All bands | - 38 - $\Delta_{\text{OTAREFSENS}}$ | - 101 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 10$ MHz | CW signal | +| | -38 - $\Delta_{\text{minSENS}}$ | -101 - $\Delta_{\text{minSENS}}$ | | | +| | - 38 - $\Delta_{\text{OTAREFSENS}}$ | - 101 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 20$ MHz | WCDMA signal (NOTE) | +| | -38 - $\Delta_{\text{minSENS}}$ | -101 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: The characteristics of the WCDMA interference signal are specified in TS 25.104 [2] Annex C. | | | | | + +**Table 7.8.5.2-6: Narrowband intermodulation performance requirement (Local Area BS)** + +| Operating band | Mean power of interfering signals [dBm] | Wanted Signal mean power [dBm] (NOTE) | Offset | Type of Interfering Signal | +|----------------------------------------------------|-----------------------------------------|---------------------------------------|---------------|----------------------------| +| II, III, IV, V, VIII, X, XII, XIII, XIV, XXV, XXVI | - 38 - $\Delta_{\text{OTAREFSENS}}$ | - 101 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 3.5$ MHz | CW signal | +| | -38 - $\Delta_{\text{minSENS}}$ | -101 - $\Delta_{\text{minSENS}}$ | | | +| | - 38 - $\Delta_{\text{OTAREFSENS}}$ | - 101 - $\Delta_{\text{OTAREFSENS}}$ | $\pm 5.9$ MHz | GMSK modulated (NOTE) | +| | -38 - $\Delta_{\text{minSENS}}$ | -101 - $\Delta_{\text{minSENS}}$ | | | +| NOTE: GMSK as defined in TS45.004 [32] | | | | | + +### 7.8.5.3 Single RAT E- UTRA operation + +For E-UTRA, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel, with a wanted signal at the assigned channel frequency and two interfering signals at the RIB, with the conditions specified in tables 7.8.5.3-1 and 7.8.5.3-2 for intermodulation performance and in tables 7.8.5.3-3, 7.8.5.3-4, and 7.8.5.3-5 for narrowband intermodulation performance. Narrowband intermodulation requirements are not applied for Band 46. The reference measurement channel for the wanted signal is identified in table 10.8.4-1 to 6 for each *channel bandwidth* and further specified in TS 36.104 [4] Annex A. + +The receiver intermodulation requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth edges*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIB supporting operation in *non-contiguous spectrum* within each supported operating band, the requirement applies in addition inside any *sub-block gap* in case the *sub-block gap* is at least as wide as the *channel bandwidth* of the E-UTRA interfering signal in table 7.8.5.3-3. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the intermodulation requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least as wide as the E-UTRA interfering signal centre frequency offset from the *Base Station RF Bandwidth edge*. + +For *multi-band RIBs*, the narrowband intermodulation requirement applies in addition inside any *Inter RF Bandwidth gap*, in case the gap size is at least as wide as the E-UTRA interfering signal in tables 7.8.5.3-3, 7.8.5.3-4 and 7.8.5.3-5. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +The OTA levels are applied referenced to 2 antenna gain offsets $\Delta_{\text{OTAREFSENS}}$ and $\Delta_{\text{minSENS}}$ . + +**Table 7.8.5.3-1: Intermodulation performance requirement** + +| BS type | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] (NOTE) | Type of interfering signal | +|-----------------|---------------------------------------------|--------------------------------------------|----------------------------| +| Wide Area BS | $\text{EIS}_{\text{REFSENS}} + 6\text{dB}$ | $-52 - \Delta_{\text{OTAREFSENS}}$ | See table 7.8.5.3-2 | +| | $\text{EIS}_{\text{minSENS}} + 6\text{ dB}$ | $-52 - \Delta_{\text{minSENS}}$ | | +| Medium Range BS | $\text{EIS}_{\text{REFSENS}} + 6\text{dB}$ | $-47 - \Delta_{\text{OTAREFSENS}}$ | | +| | $\text{EIS}_{\text{minSENS}} + 6\text{ dB}$ | $-47 - \Delta_{\text{minSENS}}$ | | +| Local Area BS | $\text{EIS}_{\text{REFSENS}} + 6\text{dB}$ | $-44 - \Delta_{\text{OTAREFSENS}}$ | | +| | $\text{EIS}_{\text{minSENS}} + 6\text{ dB}$ | $-44 - \Delta_{\text{minSENS}}$ | | + +NOTE: $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{minSENS}}$ depend on the RAT, the BS class and on the *channel bandwidth*, see clauses 7.3 and 7.2. + +**Table 7.8.5.3-2: Interfering signal for Intermodulation performance requirement** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Interfering signal centre frequency offset from the lower/upper Base Station RF Bandwidth edge [MHz] | Type of interfering signal | +|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-------------------------------| +| 3 | $\pm 4.5$ | CW | +| | $\pm 10.5$ | 3 MHz E-UTRA signal (NOTE 3) | +| 5 | $\pm 7.5$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | +| 10 | $\pm 7.375$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | +| 15 | $\pm 7.25$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal | +| 20 | $\pm 7.125$ | CW | +| | $\pm 17.5$ | 5 MHz E-UTRA signal (NOTE 1) | +| 20 | $\pm 7.125$ | CW | +| | $\pm 24$ | 20 MHz E-UTRA signal (NOTE 2) | + +NOTE 1: This type of interfering signal is not applied for Band 46. +NOTE 2: This type of interfering signal is only applied for Band 46. +NOTE 3: 3 MHz *channel bandwidth* is not applicable to guard band operation. + +**Table 7.8.5.3-3: Narrowband intermodulation performance requirement for Wide Area BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [kHz] | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| 1.4 | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±790 | 1.4 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 3 | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±780 | 3.0 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 5 | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±360 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±1060 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 10 (NOTE 3) | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±325 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±1240 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 15 (NOTE 3) | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±380 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±1600 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| 20 (NOTE 3) | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±345 | CW | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -52 - Δ TAREFSENS | ±1780 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -52 - Δ minSENS | | | + +NOTE 1: EISREFSENS and EISminSENS depend on the RAT, the BS class and on the channel bandwidth, see clauses 7.3 and 7.2. + +NOTE 2: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the lower/upper Base Station RF Bandwidth edge. + +NOTE 3: This requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals + +**Table 7.8.5.3-4: Narrowband intermodulation performance requirement for Local Area BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [kHz] | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| 1.4 | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±790 | 1.4 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 3 | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±780 | 3.0 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 5 | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±360 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±1060 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 10 (NOTE 3) | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±325 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±1240 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 15 (NOTE 3) | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±380 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±1600 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| 20 (NOTE 3) | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±345 | CW | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -44 - Δ OTAREFSENS | ±1780 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -44 - Δ minSENS | | | + +NOTE 1: EISREFSENS and EISminSENS depend on the RAT, the BS class and on the *channel bandwidth*, see clauses 7.3 and 7.2. + +NOTE 2: Interfering signal consisting of one resource block positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the lower/upper *Base Station RF Bandwidth edge*. + +NOTE 3: This requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals + +**Table 7.8.5.3-5: Narrowband intermodulation performance requirement for Medium Range BS** + +| E-UTRA channel bandwidth of the lowest/highest carrier received [MHz] | Wanted signal mean power [dBm] (NOTE 1) | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap [kHz] | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| 1.4 | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±790 | 1.4 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 3 | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±270 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±780 | 3.0 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 5 | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±360 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±1060 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 10 (NOTE 3) | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±325 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±1240 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 15 (NOTE 3) | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±380 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±1600 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| 20 (NOTE 3) | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±345 | CW | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | +| | EIS REFSENS + 6dB | -47 - Δ TAREFSENS | ±1780 | 5 MHz E-UTRA signal, 1 RB (NOTE 2) | +| | EIS minSENS + 6 dB | -47 - Δ minSENS | | | + +NOTE 1: EISREFSENS and EISminSENS depend on the RAT, the BS class and on the channel bandwidth, see clauses 7.3 and 7.2. + +NOTE 2: Interfering signal consisting of one resource block positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the lower/upper Base Station RF Bandwidth edge. + +NOTE 3: This requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals + +## 7.9 OTA In-channel selectivity + +### 7.9.1 Definition and applicability + +In-channel selectivity (ICS) is a measure of the receiver unit ability to receive a wanted signal at its assigned resource block locations in the presence of an interfering signal received at a larger power spectral density. In this condition a throughput requirement shall be met for a specified reference measurement channel. + +The requirement applies at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction and are within the *minSENS RoAoA*. + +The wanted and interfering signals apply to each supported polarization, under the assumption of *polarization match*. + +### 7.9.2 Minimum Requirement + +For AAS BS in *MSR operation* the minimum requirement is defined in TS 37.105 [6], clause 10.9.2. + +For AAS BS in *single RAT UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.9.3. + +For AAS BS in *single RAT E-UTRA operation* the minimum requirement is defined in TS 37.105 [6], clause 10.9.4. + +### 7.9.3 Test purpose + +The purpose of this test is to verify the ability of the receiver to suppress the IQ leakage. + +### 7.9.4 Method of test + +#### 7.9.4.1 Initial conditions + +Test environment: normal; see annex G.2 + +RF channels to be tested for single carrier: M; see clause 4.12.1. + +Directions to be tested: OTA REFSENS receiver target reference direction (see table 4.10-2, D11.30). + +#### 7.9.4.2 Procedure + +- 1) Place the AAS BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in Annex D1.1. +- 2) Align the manufacturer declared coordinate system orientation of the AAS BS with the test system. +- 3) Align the BS with the test antenna in the declared direction to be tested. +- 4) Align the NR BS to that the wanted signal and interferer signal is *polarization matched* with the test antenna(s) + +For each supported E-UTRA channel BW: + +- 5) Adjust the signal generator for the wanted signal as specified in table 7.9.5.1-1 for AAS BS of Wide Area BS class, in table 7.9.5.1-2 for AAS BS of Local Area BS class and in table 7.9.5.1-3 for AAS BS of Medium Range BS class on one side of the $F_c$ . +- 6) Adjust the signal generator for the interfering signal as specified in table 7.9.5.1-1 for AAS BS of Wide Area BS class, in table 7.9.5.1-2 for AAS BS of Local Area BS class and in table 7.9.5.1-3 for AAS BS of Medium Range BS class at opposite side of the $F_c$ and adjacent to the wanted signal. +- 7) Measure throughput according to annex E in TS 36.141 [12]. +- 8) Repeat the measurement with the wanted signal on the other side of the $F_c$ , and the interfering signal at opposite side of the $F_c$ and adjacent to the wanted signal. +- 9) Repeat for all supported polarizations. 10 + +For each supported NR channel BW: + +- 2) Adjust the signal generator for the wanted signal as specified in table 7.9.5.2-1 for AAS BS of Wide Area BS class, in table 7.9.5.2-2 for AAS BS of Local Area BS class and in table 7.9.5.2-3 for AAS BS of Medium Range BS class on one side of the $F_c$ . +- 3) Adjust the signal generator for the interfering signal as specified in table 7.9.5.2-1 for AAS BS of Wide Area BS class, in table 7.9.5.2-2 for AAS BS of Local Area BS class and in table 7.9.5.2-3 for AAS BS of Medium Range BS class at opposite side of the $F_c$ and adjacent to the wanted signal. +- 4) Measure throughput according to annex A in TS 38.141-2 [34]. +- 5) Repeat the measurement with the wanted signal on the other side of the $F_c$ , and the interfering signal at opposite side of the $F_c$ and adjacent to the wanted signal. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 10) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 7.9.5 Test Requirement + +### 7.9.5.1 E-UTRA test requirement + +For E-UTRA, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel as specified in 3GPP 36.104 [4] Annex A with parameters specified in table 7.9.5.1-1 for Wide Area BS, in table 7.9.5.1-2 for Local Area BS and in table 7.9.5.1-3 for Medium Range BS. + +The OTA levels are applied referenced to $\Delta_{\min\text{SENS}}$ . + +**Table 7.9.5.1-1 Wide Area BS in-channel selectivity for E-UTRA** + +| E-UTRA channel bandwidth $h$ [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | | Interfering signal mean power [dBm] | Type of interfering signal | +|------------------------------------|------------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 1.4 | A1-4 in 3GPP 36.104 [4] Annex A.1 | $-105.2 - \Delta_{\min\text{SENS}}$ | $-104.8 - \Delta_{\min\text{SENS}}$ | $-87 - \Delta_{\min\text{SENS}}$ | 1.4 MHz E-UTRA signal, 3 RBs | +| 3 | A1-5 in 3GPP 36.104 [4] Annex A.1 | $-100.4 - \Delta_{\min\text{SENS}}$ | $-100.0 - \Delta_{\min\text{SENS}}$ | $-84 - \Delta_{\min\text{SENS}}$ | 3 MHz E-UTRA signal, 6 RBs | +| 5 | A1-2 in 3GPP 36.104 [4] Annex A.1 | $-98.3 - \Delta_{\min\text{SENS}}$ | $-97.9 - \Delta_{\min\text{SENS}}$ | $-81 - \Delta_{\min\text{SENS}}$ | 5 MHz E-UTRA signal, 10 RBs | +| 10 | A1-3 in 3GPP 36.104 [4] Annex A.1 | $-96.8 - \Delta_{\min\text{SENS}}$ | $-96.4 - \Delta_{\min\text{SENS}}$ | $-77 - \Delta_{\min\text{SENS}}$ | 10 MHz E-UTRA signal, 25 RBs | +| 15 | A1-3 in 3GPP 36.104 [4] Annex A.1 (NOTE) | $-96.8 - \Delta_{\min\text{SENS}}$ | $-96.4 - \Delta_{\min\text{SENS}}$ | $-77 - \Delta_{\min\text{SENS}}$ | 15 MHz E-UTRA signal, 25 RBs (NOTE) | +| 20 | A1-3 in 3GPP 36.104 [4] Annex A.1 (NOTE) | $-96.8 - \Delta_{\min\text{SENS}}$ | $-96.4 - \Delta_{\min\text{SENS}}$ | $-77 - \Delta_{\min\text{SENS}}$ | 20 MHz E-UTRA signal, 25 RBs (NOTE) | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ . + +**Table 7.9.5.1-2 Local Area BS in-channel selectivity for E-UTRA** + +| E-UTRA channel bandwidth $h$ [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | | Interfering signal mean power [dBm] | Type of interfering signal | +|------------------------------------|--------------------------------------------|------------------------------------|------------------------------------|-------------------------------------|---------------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 1.4 | A1-4 in 3GPP 36.104 [4] Annex A.1 | $-97.2 - \Delta_{\min\text{SENS}}$ | $-96.8 - \Delta_{\min\text{SENS}}$ | $-79 - \Delta_{\min\text{SENS}}$ | 1.4 MHz E-UTRA signal, 3 RBs | +| 3 | A1-5 in 3GPP 36.104 [4] Annex A.1 | $-92.4 - \Delta_{\min\text{SENS}}$ | $-92.0 - \Delta_{\min\text{SENS}}$ | $-76 - \Delta_{\min\text{SENS}}$ | 3 MHz E-UTRA signal, 6 RBs | +| 5 | A1-2 in 3GPP 36.104 [4] Annex A.1 | $-90.3 - \Delta_{\min\text{SENS}}$ | $-89.9 - \Delta_{\min\text{SENS}}$ | $-73 - \Delta_{\min\text{SENS}}$ | 5 MHz E-UTRA signal, 10 RBs | +| 10 | A1-3 in 3GPP 36.104 [4] Annex A.1 (NOTE 3) | $-88.8 - \Delta_{\min\text{SENS}}$ | $-88.4 - \Delta_{\min\text{SENS}}$ | $-69 - \Delta_{\min\text{SENS}}$ | 10 MHz E-UTRA signal, 25 RBs (NOTE 3) | +| 15 | A1-3 in 3GPP 36.104 [4] Annex A.1 (NOTE 1) | $-88.8 - \Delta_{\min\text{SENS}}$ | $-88.4 - \Delta_{\min\text{SENS}}$ | $-69 - \Delta_{\min\text{SENS}}$ | 15 MHz E-UTRA signal, 25 RBs (NOTE 1) | +| 20 | A1-3 in 3GPP 36.104 [4] Annex A.1 (NOTE 1) | $-88.8 - \Delta_{\min\text{SENS}}$ | $-88.4 - \Delta_{\min\text{SENS}}$ | $-69 - \Delta_{\min\text{SENS}}$ | 20 MHz E-UTRA signal, 25 RBs (NOTE 1) | + +NOTE 1: Wanted and interfering signal are placed adjacently around $F_c$ , this reference measurement channel and interfering signal are not applied for Band 46 nor Band 49. + +NOTE 2: Void + +NOTE 3: This reference measurement channel and interfering signal are not applied for Band 46 nor Band 49. + +**Table 7.9.5.1-3 Medium Range BS in-channel selectivity for E-UTRA** + +| E-UTRA channel bandwidth $h$ [MHz] | Reference measurement channel | Wanted signal mean power [dBm] | | Interfering signal mean power [dBm] | Type of interfering signal | +|------------------------------------|--------------------------------------------|-------------------------------------|------------------------------------|-------------------------------------|---------------------------------------| +| | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 1.4 | A1-4 in 3GPP 36.104 [4] Annex A.1 | $-100.2 - \Delta_{\min\text{SENS}}$ | $-99.8 - \Delta_{\min\text{SENS}}$ | $-82 - \Delta_{\min\text{SENS}}$ | 1.4 MHz E-UTRA signal, 3 RBs | +| 3 | A1-5 in 3GPP 36.104 [4] Annex A.1 | $-95.4 - \Delta_{\min\text{SENS}}$ | $-95.0 - \Delta_{\min\text{SENS}}$ | $-79 - \Delta_{\min\text{SENS}}$ | 3 MHz E-UTRA signal, 6 RBs | +| 5 | A1-2 in 3GPP 36.104 [4] Annex A.1 | $-93.3 - \Delta_{\min\text{SENS}}$ | $-92.9 - \Delta_{\min\text{SENS}}$ | $-76 - \Delta_{\min\text{SENS}}$ | 5 MHz E-UTRA signal, 10 RBs | +| 10 | A1-3 in 3GPP 36.104 [4] Annex A.1 (NOTE 3) | $-91.8 - \Delta_{\min\text{SENS}}$ | $-91.4 - \Delta_{\min\text{SENS}}$ | $-72 - \Delta_{\min\text{SENS}}$ | 10 MHz E-UTRA signal, 25 RBs (NOTE 3) | +| 15 | A1-3 in 3GPP 36.104 [4] Annex A.1 (NOTE 1) | $-91.8 - \Delta_{\min\text{SENS}}$ | $-91.4 - \Delta_{\min\text{SENS}}$ | $-72 - \Delta_{\min\text{SENS}}$ | 15 MHz E-UTRA signal, 25 RBs (NOTE 1) | +| 20 | A1-3 in 3GPP 36.104 [4] Annex A.1 (NOTE 1) | $-91.8 - \Delta_{\min\text{SENS}}$ | $-91.4 - \Delta_{\min\text{SENS}}$ | $-72 - \Delta_{\min\text{SENS}}$ | 20 MHz E-UTRA signal, 25 RBs (NOTE 1) | + +NOTE 1: Wanted and interfering signal are placed adjacently around $F_c$ , this reference measurement channel and interfering signal are not applied for Band 46. + +NOTE 2: Void + +NOTE 3: This reference measurement channel and interfering signal are not applied for Band 46. + +## 7.9.5.2 NR test requirement + +The requirement shall apply at the RIB when the AoA of the incident wave of the received signal and the interfering signal are the same direction and are within the *minSENS RoAoA* + +The wanted and interfering signals applies to all supported polarizations, under the assumption of *polarization matching*. + +Details of the reference measurement channels can be found in TS 38.141-2 [34] annex A. + +**Table 7.9.5.2-1: Wide Area BS in-channel selectivity** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------------------|--------------------------|-------------------------------|------------------------------------|--------------------------------------------|-------------------------------------|--------------------------------------------| +| | | | $f \leq 3.0 \text{ GHz}$ | $3.0 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | | | +| 5 | 15 | G-FR1-A1-7 | $-98.9 - \Delta_{\min\text{SENS}}$ | $-98.5 - \Delta_{\min\text{SENS}}$ | $-81.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 PRBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | $-97 - \Delta_{\min\text{SENS}}$ | $-96.6 - \Delta_{\min\text{SENS}}$ | $-77.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 PRBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | $-90.6 - \Delta_{\min\text{SENS}}$ | $-90.2 - \Delta_{\min\text{SENS}}$ | $-71.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 PRBs | +| 5 | 30 | G-FR1-A1-8 | $-99.6 - \Delta_{\min\text{SENS}}$ | $-99.2 - \Delta_{\min\text{SENS}}$ | $-81.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 PRBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | $-97.1 - \Delta_{\min\text{SENS}}$ | $-96.7 - \Delta_{\min\text{SENS}}$ | $-78.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | $-90.9 - \Delta_{\min\text{SENS}}$ | $-90.5 - \Delta_{\min\text{SENS}}$ | $-71.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 PRBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | $-96.5 - \Delta_{\min\text{SENS}}$ | $-96.1 - \Delta_{\min\text{SENS}}$ | $-78.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | $-91 - \Delta_{\min\text{SENS}}$ | $-90.6 - \Delta_{\min\text{SENS}}$ | $-71.6 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 24 PRBs | + +NOTE: Wanted and interfering signal are placed adjacently around Fc, where the Fc is defined for *BS channel bandwidth* of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [37]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.9.5.2-2: Medium Range BS in-channel selectivity** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------------------|--------------------------|-------------------------------|------------------------------------|------------------------------------|-------------------------------------|--------------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 5 | 15 | G-FR1-A1-7 | $-93.9 - \Delta_{\min\text{SENS}}$ | $-93.5 - \Delta_{\min\text{SENS}}$ | $-76.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 PRBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | $-92 - \Delta_{\min\text{SENS}}$ | $-91.6 - \Delta_{\min\text{SENS}}$ | $-72.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 PRBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | $-85.6 - \Delta_{\min\text{SENS}}$ | $-85.2 - \Delta_{\min\text{SENS}}$ | $-66.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 PRBs | +| 5 | 30 | G-FR1-A1-8 | $-94.6 - \Delta_{\min\text{SENS}}$ | $-94.2 - \Delta_{\min\text{SENS}}$ | $-76.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 PRBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | $-92.1 - \Delta_{\min\text{SENS}}$ | $-91.7 - \Delta_{\min\text{SENS}}$ | $-73.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | $-85.9 - \Delta_{\min\text{SENS}}$ | $-85.5 - \Delta_{\min\text{SENS}}$ | $-66.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 PRBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | $-91.5 - \Delta_{\min\text{SENS}}$ | $-91.1 - \Delta_{\min\text{SENS}}$ | $-73.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | $-86 - \Delta_{\min\text{SENS}}$ | $-85.6 - \Delta_{\min\text{SENS}}$ | $-66.6 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 24 PRBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for BS channel bandwidth of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [37]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.9.5.2-3: Local area BS in-channel selectivity** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------------------|--------------------------|-------------------------------|------------------------------------|------------------------------------|-------------------------------------|--------------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | | | +| 5 | 15 | G-FR1-A1-7 | $-90.9 - \Delta_{\min\text{SENS}}$ | $-90.5 - \Delta_{\min\text{SENS}}$ | $-73.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 PRBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | $-89 - \Delta_{\min\text{SENS}}$ | $-88.6 - \Delta_{\min\text{SENS}}$ | $-69.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 PRBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | $-82.6 - \Delta_{\min\text{SENS}}$ | $-82.2 - \Delta_{\min\text{SENS}}$ | $-63.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 PRBs | +| 5 | 30 | G-FR1-A1-8 | $-91.6 - \Delta_{\min\text{SENS}}$ | $-91.2 - \Delta_{\min\text{SENS}}$ | $-73.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 PRBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | $-89.1 - \Delta_{\min\text{SENS}}$ | $-88.7 - \Delta_{\min\text{SENS}}$ | $-70.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | $-82.9 - \Delta_{\min\text{SENS}}$ | $-82.5 - \Delta_{\min\text{SENS}}$ | $-63.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 PRBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | $-88.5 - \Delta_{\min\text{SENS}}$ | $-88.1 - \Delta_{\min\text{SENS}}$ | $-70.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 PRBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | $-83 - \Delta_{\min\text{SENS}}$ | $-82.6 - \Delta_{\min\text{SENS}}$ | $-63.6 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 24 PRBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for BS channel bandwidth of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [37]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +## 8 Radiated performance requirements + +### 8.1 General + +Radiated performance requirements specify the ability of the OTA AAS BS to correctly demodulate radiated signals in various propagation conditions and configurations. + +The demodulation requirements for an OTA AAS BS are limited to two OTA *demodulations branches* as described in clause 8.1.1, and are the same as non-AAS BS demodulation requirements specified for: + +- *Single RAT UTRA operation* in TS 25.104 [2] clause 8 for FDD operation, +- *Single RAT E-UTRA operation* in TS 36.104 [4], clauses 8.2 – 8.4 (for PUSCH, PUCCH and PRACH) and 8.6 – 8.7 (for subslot-PUSCH and SPUCCH), + +- *MSR operation* in TS 37.105 [6], based on references to the single RAT requirements in TS 25.104 [2] and TS 36.104 [4]. + +### 8.1.1 OTA demodulation branches + +OTA performance requirements are only specified for up to 2 *demodulation branches*. + +If the OTA AAS BS uses polarization diversity and has the ability to maintain isolation between the signals for each of the *demodulation branches*, then OTA performance requirements can be tested for up to two *demodulation branches* (i.e. 1TX-1RX or 1TX-2RX test setup). When tested for two *demodulation branches*, each demodulation branch maps to one polarization. + +If the OTA AAS BS does not use polarization diversity then OTA performance requirements can only be tested for a single *demodulation branch* (i.e. 1TX-1RX test setup). + +## 8.2 Radiated performance requirements for MSR + +For OTA AAS BS in *single RAT UTRA operation*, minimum requirements for radiated demodulation performance are specified in clause 8.3. + +For OTA AAS BS in *single RAT E-UTRA operation*, minimum requirements for radiated demodulation performance are specified in clause 8.4. + +For OTA AAS BS in NR operation, minimum requirements for radiated demodulation performance are specified in clause 8.5. + +NOTE: Radiated performance requirements for MSR BS are applicable to the multi-RAT of single RAT operation, but tested only in single RAT configuration. + +## 8.3 Radiated performance requirements for UTRA FDD + +### 8.3.1 General + +Radiated performance requirements for *single RAT UTRA operation* in FDD are specified for the fixed reference channels (FRC) and propagation conditions defined in TS 25.104 [2] annex A and annex B, respectively. The requirements only apply to those FRCs that are supported by the OTA AAS BS. + +Unless stated otherwise, radiated performance requirements apply for a single carrier only. Performance requirements for a BS supporting DC-HSUPA or DB-DC-HSUPA are defined in terms of single carrier requirements. The requirements in clause 8.3 shall be met with the transmitter(s) ON. + +NOTE: In normal operating conditions the *transceiver units* are configured to transmit and receive at the same time. The transmitter unit(s) associated with the RIB may be OFF for some of the tests in clause 8. + +In the referenced conducted test requirements from TS 25.141 [10] the method to test describes connection to one or a number of BS antenna connectors. When applying these methods to the OTA AAS BS, connection shall be made to the RIB, based on one or two OTA *demodulation branches*. + +In the referred UTRA specifications and in this clause, the term "BS with RX diversity" refers to performance requirements for two *demodulation branches*, and the term "BS without RX diversity" refers to performance requirements for one *demodulation branch*. For "BS with RX diversity", only the BS performance requirements with Rx diversity apply, otherwise only the BS performance requirements without Rx diversity apply. + +For testing purposes, there is one *demodulation branch* per active polarization assumed. In tests performed with signal generators a synchronization signal may be provided, from the BS to the signal generator, to enable correct timing of the wanted signal. + +The $E_b/N_0$ used is defined as: + +Where: + +is the received total energy of DPDCH, DPCCH, S-DPCCH, HS-DPCCH, E-DPDCH, S-E-DPDCH, E-DPCCH and S-E-DPCCH per PN chip per *demodulation branch* from all branches + +is the total one-sided noise power spectral density due to all noise sources + +is the number of chips per frame + +is the number of information bits in DTCH excluding CRC bits per frame + +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 [30] and TS 25.141 [10], annex C. + +If external BLER measurement is not used then the internal BLER calculation shall be used instead. When internal BLER calculation is used, the requirements of the verification test according to TS 25.141 [10] clause 8.6 shall be met in advance. + +**Table 8.3.1-1: Summary of AAS BS performance targets for *single RAT UTRA operation* in FDD** + +| Physical channel | Measurement channel | Static | Multi-path Case 1 | Multi-path Case 2 | Multi-path Case 3 | Moving | Birth / Death | High Speed Train (Note) | +|------------------|---------------------|------------------------------------------|------------------------------------------|------------------------------------------|-------------------------------------------------------------|------------------------------------------|------------------------------------------|-------------------------| +| | | Performance metric | | | | | | | +| DCH | 12.2 kbps | BLER<10 -2 | BLER<10 -2 | 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 | 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. + +## 8.3.2 Definitions and applicability + +Definitions of radiated performance requirements in *single RAT UTRA operation* in FDD and their applicability are the same as defined in TS 25.141 [10], in requirement's specific "Definition and applicability" clauses within 8.2 - 8.13 clauses. + +The following limitation apply for the radiated performance requirements in *single RAT UTRA operation* in FDD: + +- All the radiated performance requirements referred from TS 25.141 [10] are subject to 2Rx limitation in the OTA test setup, as captured in clause 8.1.1. +- If the OTA AAS BS does not use polarisation diversity then performance requirements only apply to a single *demodulation branch* (i.e. 1TX-1RX test setup). +- If the OTA AAS BS uses polarisation diversity and has the ability to maintain isolation between the performance requirements signals for each of the *demodulation branches*, then performance requirements can be applied to up to two *demodulation branches* (i.e. 1TX-2RX test setups). + +NOTE: for the list of BS demodulation requirements which were found to be feasible in OTA test setup with the above 2Rx limitation, refer to TR 37.941 [38]. + +- For FRC8 in TS 25.104 [2] the non E-DPCCH boosting and E-DPCCH boosting requirement only apply for the option supported by the OTA AAS BS. +- Performance of signalling detection for 4C-HSDPA HS-DPCCH test shall be performed only for the BS supporting 4C-HSDPA. +- Performance of signalling detection for 8C-HSDPA HS-DPCCH test shall be performed only for the BS supporting 8C-HSDPA. +- The performance requirements for the high speed train scenarios defined in TS 25.104 [2] are optional. + +### 8.3.3 Minimum requirements + +Minimum requirements for radiated performance requirements in *single RAT UTRA operation* in FDD are the same as defined in TS 25.104 [2], in requirement's specific "Minimum requirement" clauses within 8.2 - 8.12 clauses, subject to limitations listed in clause 8.3.2. + +### 8.3.4 Test purposes + +Test purposes for the radiated performance requirements in *single RAT UTRA operation* in FDD are the same as defined in TS 25.141 [10], in requirement's specific "Test purpose" clauses within clauses 8.2 - 8.13. + +The radiated test shall verify the OTA AAS BS receiver's ability to achieve requirement's specific performance metric under defined propagation conditions emulated in OTA test chamber, for a given $E_b/N_0$ (or $E_c/N_0$ ). + +### 8.3.5 Method of test + +#### 8.3.5.1 Initial conditions + +Initial conditions of radiated performance requirements in *single RAT UTRA operation* in FDD are the same as defined in TS 25.141 [10], in requirement's specific "Initial conditions" clauses within 8.2 - 8.13 clauses, with the exception, that instead of connecting the BS tester(s) directly to antenna connector(s), either a single or two polarizations should be transmitted via test antenna(s) in the OTA chamber, where each polarization represents a *demodulation branch*. + +The initial conditions for the radiated performance requirements in *single RAT UTRA operation* in FDD are generalized as follows: + +Test environment: normal, see annex G.2. + +RF channels to be tested: B, M and T; see TS 25.141 [10], clause 4.8. + +Direction to be tested: OTA REFSENS receiver target reference direction (see table 4.10-1, D11.30). + +#### 8.3.5.2 Procedure + +- 1) Place the OTA AAS BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.3. +- 2) Align the manufacturer declared coordinate system orientation of the OTA AAS BS with the test system. +- 3) Set the OTA AAS BS in the declared direction to be tested. +- 4) Connect the BS tester generating the wanted signal, multipath fading simulators and/or AWGN generators (depending on the required OTA test procedure) to a test antenna via a combining network in OTA test setup, as shown in annex D.3. +- 5) Apply the conducted performance test procedure appropriate to the requirement as described in clause 8 of TS 25.141 [10]. Instead of connection via an antenna connector, one of the RX antenna signals should be transmitted on each polarization of the test antenna(s). +- 6) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A in TS 25.141 [10], and according to additional test parameters listed in respective conducted performance test procedure in TS 25.141 [10]. + - a. For RACH requirements: configure test signal generator to sends a preamble according to the test signal pattern defined for RACH in TS 25.141 [10]. +- 7) The multipath fading emulators shall be configured according to the corresponding channel model defined in TS 25.141 [10], annex D. +- 8) Adjust the test signal mean power so the calibrated radiated signal level at the BS receiver is as specified in requirement's specific clause 8 of TS 25.141 [10]. + +- a. For DCH requirements: Adjust the test signal mean power so the calibrated radiated $E_b/N_0$ value at the BS receiver is as specified in requirement's specific clause 8 of TS 25.141 [10]. To achieve the specified $E_b/N_0$ , the ratio of the wanted signal level relative to the AWGN signal should be adjusted to: $10 * \log_{10}(R_b / 3.84 * 10^6) + E_b/N_0$ [dB]. +- b. For RACH requirements: Adjust the test signal mean power so the calibrated radiated $E_b/N_0$ (or $E_c/N_0$ ) value at the BS receiver is as specified in requirement's specific clause 8 of TS 25.141 [10]. + - i. For RACH preamble detection in static propagation, multipath fading case 3, or in high speed train conditions: To achieve the specified $E_c/N_0$ , the ratio of the wanted signal level (of the preamble part) relative to the AWGN signal at the BS receiver should be adjusted to: $E_c/N_0$ [dB]. + - ii. For Demodulation of RACH message in static propagation conditions, multipath fading case 3, or in high speed train conditions: To achieve the specified $E_c/N_0$ , the ratio of the wanted signal level (of the message part) relative to the AWGN signal at the BS receiver should be adjusted to: $10 * \log_{10}(TB / (TTI * 3.84 * 10^6)) + E_b/N_0$ [dB]. +- c. For HS-DPCCH: Adjust the test signal mean power so the calibrated radiated $E_c/N_0$ value at the BS receiver is as specified in requirement's specific clause 8 of TS 25.141 [10]. To achieve the specified $E_c/N_0$ , the ratio of the wanted signal level relative to the AWGN signal at the BS input should be adjusted to: $E_c/N_0$ [dB]. + +The power level for the transmission may be set such that the AWGN level at the RIB is equal to the AWGN level quoted in the test procedure of TS 25.141 [10] minus $\Delta_{\text{OTAREFSENS}}$ . Example of the AWGN levels for the UTRA FDD requirements, with the $\Delta_{\text{OTAREFSENS}}$ correction are presented in table 8.4.5.2-1. + +**Table 8.3.5.2-1: AWGN power level at the BS input for UTRA FDD requirements** + +| BS class | AWGN power level | +|--------------|-----------------------------------------------------| +| Wide Area | $-84 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 3.84 MHz | +| Medium Range | $-74 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 3.84 MHz | +| Local Area | $-70 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 3.84 MHz | + +While signal power adjustment, reassure that the $E_b/N_0$ (or $E_c/N_0$ ) at the BS receiver is not impacted by the noise floor. + +- 9) If RX diversity is not supported, ensure the *polarisation match* is achieved among test antenna(s) and the OTA AAS BS under test, in order to maximize the power at the BS receiver. +- 10) For reference channels applicable to the BS, measure the appropriate performance metric for the requirement as described in clause 8 of TS 25.141 [10]. + +### 8.3.6 Test requirements + +Test requirements of radiated performance requirements in *single RAT UTRA operation* in FDD are the same as defined in TS 25.141 [10], in requirement's specific "Test requirement" clauses within 8.2 - 8.13 clauses, with the exception that shall be derived based on the OTA test procedure, as in clause 8.3.5.2. + +Applicability of radiated test requirements is subject to limitations listed in clause 8.3.2. + +In the referenced test requirements in this clause, the term "number of RX antennas" should be replaced by one if a single polarization is transmitted or by two if two polarizations are transmitted. + +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 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +## 8.4 Radiated performance requirements for E-UTRA + +### 8.4.1 General + +Radiated performance requirements for *single RAT E-UTRA operation* are specified for the fixed reference channels (FRC) and propagation conditions defined in TS 36.104 [4] annex A and annex B, respectively. The requirements only apply to those FRCs that are supported by the OTA AAS BS. + +Unless stated otherwise, radiated performance requirements apply for a single carrier only. Radiated performance requirements for an OTA AAS BS in E-UTRA operation supporting *carrier aggregation* are defined in terms of single carrier requirements. + +In the referred E-UTRA specification TS 36.104 [4], the term "RX antennas" refers to *demodulation branches* (and not physical antennas). + +Conformance requirements can only be tested for 1 or 2 *demodulation branches* depending on the number of polarizations supported by the BS, with the required SNR /SINR (in case of E-UTRA demodulation requirements), or required $E_b/N_0$ (in case of UTRA FDD demodulation requirements) applied separately per polarization. + +Only 2RX BS performance requirements apply when OTA AAS BS supports and is tested with dual polarizations, except where requirements are defined with 1RX only (e.g. HST) where the requirements shall be tested with single polarization. + +NOTE: OTA AAS BS can support more than 2 *demodulation branches*, however OTA conformance testing can only be performed for 1 or 2 *demodulation branches*. + +For tests in clause 8.4 the transmitters may be OFF. + +The performance requirements for High Speed Train conditions are optional. + +The performance requirements for UL timing adjustment scenario 2 are optional. + +In tests performed with signal generators a synchronization signal may be provided, from the BS to the signal generator, to enable correct timing of the wanted signal. + +For E-UTRA performance requirements the SNR used in this clause is specified based on a single carrier and defined as: + +$$\text{SNR} = S / N$$ + +Where: + +S is the total signal energy in the subframe. + +N is the noise energy in a bandwidth corresponding to the *transmission bandwidth* over the duration of a subframe. + +For enhanced E-UTRA performance requirements type A, the SINR used in this clause is specified based on a single carrier and defined as: + +$$\text{SINR} = S / N'$$ + +Where: + +S is the total signal energy in the subframe. + +N' is the summation of the received energy of the strongest interferers explicitly defined in a test procedure plus the white noise energy N, in a bandwidth corresponding to the *transmission bandwidth* over the duration of a subframe. The respective energy of each interferer relative to N' is defined by its associated DIP value. + +In the referenced conducted test requirements from TS 36.141 [12] the method to test describes connection to one or a number of BS antenna connectors. When applying these methods to the OTA AAS BS, connection shall be made to the RIB, based on one or two OTA *demodulation branches*. + +## 8.4.2 Definitions and applicability + +Definitions of radiated performance requirements in *single RAT E-UTRA operation* and their applicability are the same as defined in TS 36.141 [12], in requirement's specific "Definition and applicability" clauses within 8.2 - 8.4 clauses. + +The following limitation apply for the radiated performance requirements in *single RAT E-UTRA operation*: + +- All the radiated performance requirements referred from TS 36.141 [12] are subject to 2Rx limitation in the OTA test setup, as captured in clause 8.1.1. +- If the OTA AAS BS does not use polarisation diversity then performance requirements only apply to a single *demodulation branch* (i.e. 1TX-1RX test setup). +- If the OTA AAS BS uses polarisation diversity and has the ability to maintain isolation between the performance requirements signals for each of the *demodulation branches*, then performance requirements can be applied to up to two *demodulation branches* (i.e. 1TX-2RX test setups). + +NOTE: for the list of BS demodulation requirements which were found to be feasible in OTA test setup with the above 2Rx limitation, refer to TR 37.941 [38]. + +- A test for a specific channel bandwidth is only applicable if the BS supports it. For a BS supporting multiple channel bandwidths only the tests for the lowest and the highest channel bandwidths supported by the BS are applicable. +- The performance requirements for High Speed Train conditions are optional. +- The performance requirements for UL timing adjustment scenario 2 are optional. +- Performance requirements for coverage enhancements are applicable only to the AAS BS supporting coverage enhancement configured with CEModeA. This applies to the following requirements: + - Requirements for PUSCH supporting coverage enhancement + - Requirements for PUSCH supporting Cat-M1 UEs + - PUCCH performance requirements for supporting Cat-M1 UEs + - PRACH missed detection, Cat-M1 mode +- The enhanced performance requirements apply to AAS BS supporting the enhanced performance requirements type A and/or type B. +- Performance requirements for NB-IoT are not applicable to AAS BS. + +For PUSCH performance requirements, the FRCs for the throughput performance metric derivation are listed in TS 36.141 [12], annex A. + +## 8.4.3 Minimum requirements + +Minimum requirements for radiated performance requirements in *single RAT E-UTRA operation* are the same as defined in TS 36.104 [4], in requirement's specific "Minimum requirement" clauses within 8.2 - 8.4 (for PUSCH, PUCCH and PRACH) and 8.6 – 8.7 (for subslot-PUSCH and SPUCCH), subject to limitations listed in clause 8.4.2. + +## 8.4.4 Test purposes + +Test purposes for the radiated performance requirements in *single RAT E-UTRA operation* are the same as defined in TS 36.141 [12], in requirement's specific "Test purpose" clauses within clauses 8.2 - 8.4 (for PUSCH, PUCCH and PRACH) and 8.6 – 8.7 (for subslot-PUSCH and SPUCCH). + +The radiated test shall verify the OTA AAS BS receiver's ability to achieve requirement's specific performance metric under defined propagation conditions emulated in OTA test chamber, for a given SNR (or SINR). + +## 8.4.5 Method of test + +### 8.4.5.1 Initial conditions + +Initial conditions of radiated performance requirements in *single RAT E-UTRA operation* are the same as defined in TS 36.141 [12], in requirement's specific "Initial conditions" clauses within 8.2 - 8.4 and 8.6 - 8.7, with the exception, that instead of connecting the BS tester(s) directly to antenna connector(s), either a single or two polarizations should be transmitted via test antenna(s) in the OTA chamber, where each polarization represents a *demodulation branch*. + +The initial conditions for the radiated performance requirements in *single RAT E-UTRA operation* are generalized as follows: + +Test environment: normal, annex G.2. + +RF channels to be tested: M; see TS 36.141 [12], clause 4.7. + +Direction to be tested: OTA REFSSENS receiver target reference direction (see table 4.10-1, D11.30). + +### 8.4.5.2 Procedure + +- 1) Place the OTA AAS BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.3. +- 2) Align the manufacturer declared coordinate system orientation of the OTA AAS BS with the test system. +- 3) Set the OTA AAS BS in the declared direction to be tested. +- 4) Connect the BS tester generating the wanted signal, interference signal(s), multipath fading simulators and/or AWGN generators (depending on the required OTA test procedure) to a test antenna via a combining network in OTA test setup, as shown in annex D.3. + - a. For enhanced performance requirements and for ACK missed detection for multi user PUCCH format 1a: Interconnect attenuators for relative power setting purposes for all transmitting branches (wanted signal and all interferers, separately). +- 5) Apply the conducted performance test procedure appropriate to the requirement as described in clause 8 of TS 36.141 [12]. Instead of connection via an antenna connector, one of the RX antenna signals should be transmitted on each polarization of the test antenna(s). +- 6) The characteristics of the wanted/interfering signal shall be configured according to the corresponding UL reference measurement channel defined in annex A in TS 36.141 [12], and according to additional test parameters listed in respective conducted performance test procedure in TS 36.141 [12]. In case of PUCCH requirements, the characteristics of the wanted signal shall be configured according to TS 36.211 [28]. +- 7) The multipath fading emulators shall be configured according to the corresponding channel model defined in TS 36.141 [12], annex B. +- 8) Adjust the test signal mean power so the calibrated radiated SNR (or SINR) value at the BS receiver is as specified in requirement's specific clause 8 of TS 36.141 [12], and that the SNR (or SINR) at the BS receiver is not impacted by the noise floor. + +The power level for the transmission may be set such that the AWGN level at the RIB is equal to the AWGN level quoted in the test procedure of TS 36.141 [12] minus $\Delta_{\text{OTAREFSSENS}}$ . Examples of the AWGN levels for the E-UTRA PUSCH as well as for the PUCCH and PRACH requirements, with the $\Delta_{\text{OTAREFSSENS}}$ correction are presented in table 8.4.5.2-1 and table 8.4.5.2-2, respectively. + +**Table 8.4.5.2-1: AWGN power level at the BS input for PUSCH requirements** + +| Channel bandwidth [MHz] | AWGN power level | +|-------------------------|-------------------------------------------------------| +| 1.4 | $-92.7 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 1.08 MHz | +| 3 | $-88.7 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 2.7 MHz | +| 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 4.5 MHz | +| 10 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 9 MHz | +| 15 | $-81.7 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 13.5 MHz | +| 20 | $-80.4 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 18 MHz | + +**Table 8.4.5.2-2: AWGN power level at the BS input for PUCCH and PRACH requirements** + +| Channel bandwidth [MHz] | AWGN power level | +|-------------------------|-------------------------------------------------------| +| 1.4 | $-89.7 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 1.08 MHz | +| 3 | $-85.7 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 2.7 MHz | +| 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 4.5 MHz | +| 10 | $-80.5 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 9 MHz | +| 15 | $-78.7 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 13.5 MHz | +| 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ [dBm] / 18 MHz | + +- 9) If RX diversity is not supported, ensure the *polarisation match* is achieved among test antenna(s) and the OTA AAS BS under test, in order to maximize the power at the BS receiver. +- 10) For reference channels applicable to the BS, measure the appropriate performance metric for the requirement as described in clause 8 of TS 36.141 [12]. + +## 8.4.6 Test requirements + +Test requirements of radiated performance requirements in *single RAT E-UTRA operation* are the same as defined in TS 36.141 [12], in requirement's specific "Test requirement" clauses within 8.2 - 8.4 and 8.6 – 8.7, with the exception that shall be derived based on the OTA test procedure, as in clause 8.4.5.2. + +Applicability of radiated test requirements is subject to limitations listed in clause 8.4.2. + +In the referenced test requirements in this clause, the term "number of RX antennas" should be replaced by one if a single polarization is transmitted or by two if two polarizations are transmitted. + +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 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +# 8.5 Radiated performance requirements for NR + +## 8.5.1 General + +Radiated performance requirements specify the ability of the *OTA AAS BS* to correctly demodulate radiated signals in various conditions and configurations. Radiated performance requirements are specified at the RIB. + +Radiated performance requirements for NR operation are specified for the fixed reference channels (FRC) and propagation conditions defined in TS 38.104 [36] annex A and annex G, respectively. The requirements only apply to those FRCs that are supported by the *OTA AAS BS*. + +The radiated performance requirements for *OTA AAS BS* are limited to two OTA *demodulation branches* as described in clause 8.1.1. Conformance requirements can only be tested for 1 or 2 *demodulation branches* depending on the number of polarizations supported by the BS, with the required SNR applied separately per polarization. + +NOTE 1: The BS can support more than 2 *demodulation branches*, however OTA conformance testing can only be performed for 1 or 2 *demodulation branches*. + +Unless stated otherwise, radiated performance requirements apply for a single carrier only. Radiated performance requirements for NR operation supporting *carrier aggregation* are defined in terms of single carrier requirements. + +For *OTA AAS BS* in FDD operation the requirements in clause 8 shall be met with the transmitter units associated with the RIB in the *operating band* turned ON. + +NOTE 2: In normal operating conditions, transceivers in FDD operation are configured to transmit and receive at the same time. The associated transmitter unit(s) may be OFF for some of the tests as specified in TS 38.141-2 [34]. + +In tests performed with signal generators a synchronization signal may be provided, from the BS to the signal generator, to enable correct timing of the wanted signal. + +Conformance requirements can only be tested for 1 or 2 *demodulation branches* depending on the number of polarizations supported by the BS, with the required SNR applied separately per polarization. + +Only 2RX BS performance requirements apply when *OTA AAS BS* supports and is tested with dual polarizations. + +NOTE 3: *OTA AAS BS* can support more than 2 *demodulation branches*, however OTA conformance testing can only be performed for 1 or 2 *demodulation branches*. + +The SNR used in this clause is specified based on a single carrier and defined as: + +$$\text{SNR} = S / N$$ + +Where: + +S is the total signal energy in a slot on a RIB. + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the duration of a slot on a RIB. + +## 8.5.2 Definitions and applicability + +Definitions of radiated performance requirements in NR operation and their applicability are the same as defined in TS 38.141-2 [34], in requirement's specific "Definition and applicability" clauses within 8.2 - 8.4. + +The following limitation apply for the radiated performance requirements in NR operation: + +- All the radiated performance requirements referred from TS 38.141-2 [34] are subject to 2RX limitation in the OTA test setup, as captured in clause 8.1.1. +- If the *OTA AAS BS* does not use polarisation diversity then performance requirements only apply to a single *demodulation branch* (i.e. 1TX-1RX test setup). +- If the *OTA AAS BS* uses polarisation diversity and has the ability to maintain isolation between the performance requirements signals for each of the *demodulation branches*, then performance requirements can be applied to up to two *demodulation branches* (i.e. 1TX-2RX test setups). +- A test for a specific channel bandwidth is only applicable if the BS supports it. For a BS supporting multiple channel bandwidths only the tests for the lowest and the highest channel bandwidths supported by the BS are applicable. + +For PUSCH performance requirements, the FRCs for the throughput performance metric derivation are listed in TS 38.141-2 [34], annex A. + +## 8.5.3 Minimum requirements + +Minimum requirements for radiated performance requirements in NR operation are the same as defined in TS 38.104 [36], in requirement's specific "Minimum requirement" clauses within 8.2 - 8.4, subject to limitations listed in clause 8.5.2. + +## 8.5.4 Test purposes + +Test purposes for the radiated performance requirements in NR operation are the same as defined in TS 38.141-2 [34], in requirement's specific "Test purpose" clauses within 8.2 - 8.4. + +The radiated test shall verify the OTA AAS BS receiver's ability to achieve requirement's specific performance metric under defined propagation conditions emulated in OTA test chamber, for a given SNR. + +## 8.5.5 Method of test + +### 8.5.5.1 Initial conditions + +Initial conditions of radiated performance requirements in NR operation are the same as defined in TS 38.141-2 [34], in requirement's specific "Initial conditions" clauses within 8.2 - 8.4. + +A single or two polarizations should be transmitted via test antenna(s) in the OTA chamber, where each polarization represents a *demodulation branch*. + +The initial conditions for the radiated performance requirements in NR operation are generalized as follows: + +Test environment: normal, annex G.2. + +RF channels to be tested: M; see TS 38.141-2 [34], clause 4.9. + +Direction to be tested: OTA REFSENS receiver target reference direction (see table 4.10-1, D11.30). + +### 8.5.5.2 Procedure + +- 1) Place the OTA AAS BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.3. +- 2) Align the manufacturer declared coordinate system orientation of the OTA AAS BS with the test system. +- 3) Set the OTA AAS BS in the declared direction to be tested. +- 4) Connect the BS tester generating the wanted signal, interference signal(s), multipath fading simulators and/or AWGN generators (depending on the required OTA test procedure) to a test antenna via a combining network in OTA test setup, as shown in annex D.3. +- 5) Apply the performance test procedure appropriate to the requirement as described in clause 8 of TS 38.141-2 [34]. One of the RX antenna signals should be transmitted on each polarization of the test antenna(s). +- 6) The characteristics of the wanted/interfering signal shall be configured according to the corresponding UL reference measurement channel defined in annex A in TS 38.141-2 [34], and according to additional test parameters listed in respective performance test procedures. In case of PUCCH requirements, the characteristics of the wanted signal shall be configured according to TS 38.211 [36]. +- 7) The multipath fading emulators shall be configured according to the corresponding channel model defined in TS 38.141-2 [34], annex J. +- 8) Adjust the test signal mean power so the calibrated radiated SNR value at the BS receiver is as specified in requirement's specific clause 8 of TS 38.141-2 [34], and that the SNR at the BS receiver is not impacted by the noise floor. + +The power level for the transmission may be set such that the AWGN level at the RIB is set according to the respective PUSCH, PUCCH, or PRACH test procedures of TS 38.141-2 [34]. + +**Table 8.2.1.4.2-2: Void** + +- 9) If RX diversity is not supported, ensure the *polarisation match* is achieved among test antenna(s) and the OTA AAS BS under test, in order to maximize the power at the BS receiver. +- 10) For reference channels applicable to the BS, measure the appropriate performance metric for the requirement as described in clause 8 of TS 38.141-2 [34]. + +## 8.5.6 Test requirements + +Test requirements of radiated performance requirements in NR operation are the same as defined in TS 38.141-2 [34], in requirement's specific "Test requirement" clauses within 8.2 - 8.4. + +Applicability of radiated test requirements is subject to limitations listed in clause 8.5.2. + +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 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +--- + +## Annex A (normative): Test system characterization + +The radiated measurement methods for AAS BS conformance testing were described in TR 37.941 [38], including descriptions of their limitations and testing applicability. + +--- + +## Annex B (normative): Calibration + +The radiated measurement methods for AAS BS conformance testing were described in TR 37.941 [38]. Calibration stage description was covered for each of the identified Test Systems in the measurement's procedure description, which covered two distinct stages: calibration stage and measurement stage. This has been separately covered for transmitter and for receiver requirements. + +--- + +## Annex C (informative): Test tolerances and derivation of test requirements + +### C.1 General + +The test requirements explicitly defined in this specification have been calculated by relaxing the minimum requirements of the core specification using the Test Tolerances defined here. 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 the following tables. + +The Test Tolerances are derived from Test System uncertainties. + +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.). + +Note that a formula for applying Test Tolerances is provided for all tests. + +NOTE: OTA test requirements for AAS BS are specified for Normal conditions, only. + +--- + +## C.2 Measurement of transmitter (OTA) + +**Table C.2-1: Derivation of Test Requirements (OTA transmitter tests)** + +| Test | Minimum Requirement in TS 37.105 [6] | Test Tolerance (TT) | Test Requirement in the present document | +|-----------------------------------------------------------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| 6.2 Radiated transmit power | See TS 37.105 [6], clause 9.2 | 1.1 dB, $f \leq 3.0$ GHz
1.3 dB, $3.0$ GHz $< f \leq 4.2$ GHz | Formula:
Upper limit + TT, Lower limit – TT | +| 6.2 Radiated transmit power (extreme conditions) | See TS 37.105 [6], clause 9.2 | 2.5 dB, $f \leq 3.0$ GHz
2.6 dB, $3.0$ GHz $< f \leq 4.2$ GHz | Formula:
Upper limit + TT, Lower limit – TT | +| 6.3.2 OTA Maximum output power | See TS 37.105 [6], clause 9.3.2 | 1.4 dB, $f \leq 3.0$ GHz
1.5 dB, $3.0$ GHz $< f \leq 4.2$ | Formula:
Upper limit + TT, Lower limit – TT | +| 6.3.3 OTA E-UTRA DL RS power | See TS 37.105 [6], clause 9.3.3 | 1.3 dB, $f \leq 3.0$ GHz
1.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz | Formula:
Upper limit + TT, Lower limit – TT | +| 6.4.2 OTA UTRA Inner loop power control in the downlink | See TS 37.105 [6], clause 9.4.2 | 0.1 dB | Formula:
Upper limit + TT, Lower limit – TT | +| 6.4.3 OTA Power control dynamic range | See TS 37.105 [6], clause 9.4.3 | 1.1 dB | Formula:
Upper limit - TT, Lower limit + TT | +| 6.4.4 OTA Total power dynamic range | See TS 37.105 [6], clause 9.4.4 | 0.3 dB UTRA
0.4 dB E-UTRA & NR | Formula:
limit - TT | +| 6.4.5 OTA IPDL time mask | See TS 37.105 [6], clause 9.4.5 | 0.7 dB | Formula:
limit - TT | +| 6.5 OTA Transmit ON/OFF power | See TS 37.105 [6], clause 9.5 | 3.4 dB, $f \leq 3.0$ GHz
3.6 dB, $3.0$ GHz $< f \leq 4.2$ GHz | Formula:
limit - TT | +| 6.6.2 OTA Frequency Error | See TS 37.105 [6], clause 9.6.2 | 12 Hz | Limit + TT | +| 6.6.3 OTA Time alignment error | See TS 37.105 [6], clause 9.6.3 | 25 ns | Limit + TT | +| 6.6.4 OTA Modulation quality | See TS 37.105 [6], clause 9.6.3 | 1 % | Limit + TT | +| 6.7.2 OTA occupied bandwidth | See TS 37.105 [6], clause 9.7.2 | 0 Hz | Limit | +| 6.7.3 OTA Adjacent Channel Leakage power Ratio | See TS 37.105 [6], clause 9.7.3 | ACLR / CACLR
1.0 dB, $f \leq 3.0$ GHz
1.2 dB, $3.0$ GHz $< f \leq 4.2$
Absolute limit
0 dB | Limit + TT | +| 6.7.4 OTA Spectrum emission mask | See TS 37.105 [6], clause 9.6.3 | 1.8 dB, $f \leq 3.0$ GHz
2.0 dB, $3.0$ GHz $< f \leq 4.2$ GHz
FFS | Limit + TT | +| 6.7.5 OTA Operating band unwanted emission | See TS 37.105 [6], clause 9.6.3 | close to carrier ( $<10$ MHz)
1.8 dB, $f \leq 3.0$ GHz
2.0 dB, $3.0$ GHz $< f \leq 4.2$ GHz
far from carrier ( $\geq 10$ MHz)
0dB
Additional limits for bands n50, n51, n74, n75, n76: 0 dB | Limit + TT | +| 6.7.6.2 OTA Transmitter spurious emissions, Mandatory Requirements | See TS 37.105 [6], clause 9.7.6.2.1, 9.7.6.3.1 and 9.7.6.4.1 | 0dB | FFS | +| 6.7.6.3 Transmitter spurious emissions, Protection of BS receiver | See TS 37.105 [6], clause 9.7.6.2.2, 9.7.6.3.2 and 9.7.6.4.2 | 3.1 dB, $f \leq 3.0$ GHz
3.3 dB, $3.0$ GHz $< f \leq 4.2$ GHz | Limit + TT | +| 6.7.6.4 Transmitter spurious emissions, Additional spurious emission requirements | See TS 37.105 [6], clause 9.7.6.2.3, 9.7.6.3.3 and 9.7.6.4.3 | 2.6 dB, $f \leq 3.0$ GHz
3.0 dB, $3.0$ GHz $< f \leq 4.2$ GHz
3.5 dB, $4.2$ GHz $< f \leq 6.0$ GHz

For co-existence with PHS and public safety bands.
0 dB

Additional limits for bands n50, n51, n74, n75, n76: 0 dB | Limit + TT | + +| | | | | +|-----------------------------------------------------|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|------------| +| 6.7.6.5 Transmitter spurious emissions, Co-location | See TS 37.105 [6], clause 9.7.6.2.4, 9.7.6.3.4 and 9.7.6.4.4 | 3.1 dB, $f \leq 3.0$ GHz
3.3 dB, $3.0$ GHz $< f \leq 4.2$ GHz
3.4 dB, $4.2$ GHz $< f \leq 6.0$ GHz | Limit + TT | +| 6.8 OTA Transmitter intermodulation | See TS 37.105 [6] | 0dB | | + +## C.3 Measurement of receiver (OTA) + +**Table C.2-1: Derivation of Test Requirements (OTA receiver tests)** + +| Test | Minimum Requirement in TS 37.105 [6] | Test Tolerance | Test Requirement in the present document | +|---------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------------------| +| 7.2 OTA sensitivity | See TS 37.105 [6], clause 10.2 | 1.3 dB, $f \leq 3.0$ GHz
1.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz | Formula:
Declared Minimum EIS + TT | +| 7.3 OTA Reference Sensitivity | See TS 37.105 [6], clause 10.3 | 1.3 dB, $f \leq 3.0$ GHz
1.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz | Formula:
EISREFSENS + TT | +| 7.4 OTA Dynamic range | See TS 37.105 [6], clause 10.4 | 0.3 dB | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | +| 7.5 OTA Adjacent channel selectivity, general blocking, and narrowband blocking | See TS 37.105 [6], clause 10.5 | 0 dB | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | +| 7.6 OTA Blocking - in-band | See TS 37.105 [6], clause 10.6 | 0 dB | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | +| 7.6 OTA Blocking - out of band | See TS 37.105 [6], clause 10.6 | 0 dB | | +| 7.6 OTA blocking – co-location | See TS 37.105 [6], clause 10.6 | 0 dB | Formula: Wanted signal power unchanged

Interferer signal power - TT. | +| 7.7 Receiver spurious emissions | See TS 37.105 [6], clause 10.7 | 0 dB | Formula: Wanted signal power + TT. | +| 7.8 OTA Receiver intermodulation | See TS 37.105 [6], clause 10.8 | 0 dB | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | +| 7.9 OTA In-channel selectivity | See TS 37.105 [6], clause 10.9 | 1.7 dB, $f \leq 3.0$ GHz
2.1 dB, $3.0$ GHz $< f \leq 4.2$ GHz | Formula: Wanted signal power + TT.

Interferer signal power unchanged. | + +## Annex D (informative): Test system set-up + +### D.1 Transmitter + +#### D.1.1 Radiated Transmit Power, OTA E-UTRA DL RS power, output power dynamics and Transmitter signal quality + +![Diagram of the measurement setup for Radiated Transmit Power, OTA E-UTRA DL RS power, output power dynamics, and Transmitter signal quality. The setup is inside a 'Test system enclosure' lined with waveguides. On the left, an 'AAS BS' (Active Antenna System Base Station) is shown with a 'Test system Calibrated point' marked by a dot. A coordinate system is defined with a vertical dashed line as the reference. The angle theta (θ) is measured from the vertical, and the angle phi (φ) is measured from the horizontal. An arrow points from the 'AAS declared coordinate reference point and orientation' label to the origin. On the right, a 'Test antenna' is positioned to receive the signal. An arrow points from the test antenna to a 'Measurement receiver' box outside the enclosure.](ef0ac4e673da0e46509a5c1eccc68c34_img.jpg) + +Diagram of the measurement setup for Radiated Transmit Power, OTA E-UTRA DL RS power, output power dynamics, and Transmitter signal quality. The setup is inside a 'Test system enclosure' lined with waveguides. On the left, an 'AAS BS' (Active Antenna System Base Station) is shown with a 'Test system Calibrated point' marked by a dot. A coordinate system is defined with a vertical dashed line as the reference. The angle theta (θ) is measured from the vertical, and the angle phi (φ) is measured from the horizontal. An arrow points from the 'AAS declared coordinate reference point and orientation' label to the origin. On the right, a 'Test antenna' is positioned to receive the signal. An arrow points from the test antenna to a 'Measurement receiver' box outside the enclosure. + +**Figure D.1.1-1: Measurement set up for Radiated Transmit Power, OTA E-UTRA DL RS power, output power dynamics, Transmitter signal quality** + +The OTA chamber shown in figure D.1.1-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, Near field chamber, etc.). + +## D.1.2 OTA Base Station output power, ACLR, OTA spectrum emissions mask, OTA operating band unwanted emissions + +![Measurement setup diagram for OTA Base Station output power, ACLR, OTA spectrum emissions mask, OTA operating band unwanted emissions. The diagram shows an AAS BS mounted on a positioner inside a test system enclosure. A calibrated point is marked on the BS, and the AAS declared coordinate reference point and orientation are indicated. A test antenna is positioned to receive signals from the BS, and the signal is sent to a measurement receiver.](4141e32339a99ae82b6360896250e1fc_img.jpg) + +The diagram illustrates the measurement setup for OTA Base Station output power, ACLR, OTA spectrum emissions mask, and OTA operating band unwanted emissions. It features a 'Test system enclosure' with a jagged border. Inside, an 'AAS BS' is mounted on a 'Positioner'. A 'Test system Calibrated point' is marked on the BS. The 'AAS declared coordinate reference point and orientation' are indicated by a dashed line and angles $\theta$ and $\varphi$ . A 'Test antenna' is positioned to the right of the BS, connected to a 'Measurement receiver'. + +Measurement setup diagram for OTA Base Station output power, ACLR, OTA spectrum emissions mask, OTA operating band unwanted emissions. The diagram shows an AAS BS mounted on a positioner inside a test system enclosure. A calibrated point is marked on the BS, and the AAS declared coordinate reference point and orientation are indicated. A test antenna is positioned to receive signals from the BS, and the signal is sent to a measurement receiver. + +Figure D.1.2-1: Measurement set up for OTA Base Station output power, ACLR, OTA spectrum emissions mask, OTA operating band unwanted emissions + +## D.1.3 OTA spurious emissions + +![Measurement setup diagram for OTA spurious emissions. The diagram shows an AAS BS mounted on a positioner inside a test system enclosure. A calibrated point is marked on the BS, and the AAS declared coordinate reference point and orientation are indicated. A test antenna is positioned to receive signals from the BS, and the signal is sent to a measurement receiver.](dc5554f3d97c390f2e7467a86598b98e_img.jpg) + +The diagram illustrates the measurement setup for OTA spurious emissions. It is identical to the setup in Figure D.1.2-1, showing an 'AAS BS' on a 'Positioner' inside a 'Test system enclosure'. It includes the 'Test system Calibrated point', 'AAS declared coordinate reference point and orientation' (angles $\theta$ and $\varphi$ ), a 'Test antenna', and a 'Measurement receiver'. + +Measurement setup diagram for OTA spurious emissions. The diagram shows an AAS BS mounted on a positioner inside a test system enclosure. A calibrated point is marked on the BS, and the AAS declared coordinate reference point and orientation are indicated. A test antenna is positioned to receive signals from the BS, and the signal is sent to a measurement receiver. + +Figure D.1.3-1: Measurement set up for OTA spurious emissions + +### D.1.4 OTA Co-location emissions, TX OFF power + +![Diagram of measurement setup for OTA Co-location emissions, TX OFF power. It shows a test system enclosure with a positioner, AAS BS, calibrated point, coordinate reference, co-location test antenna, test antenna, measurement receiver, switch/limiter/filter, and measurement device.](d2c36d67ed6755e11257cc7ed7a32edb_img.jpg) + +The diagram illustrates the measurement setup for OTA Co-location emissions with TX OFF power. It features a large rectangular 'Test system enclosure' with a jagged border. Inside, a 'Positioner' holds an 'AAS BS' (Antenna Under Test). A 'Test system Calibrated point' is marked on the AAS BS, and an 'AAS declared coordinate reference point and orientation' is indicated. A 'Co-Location Test Antenna' is positioned near the AAS BS. A 'Test antenna' is located to the right, connected to a 'Measurement receiver'. A red line connects the Co-Location Test Antenna to a 'Switch, limiter or filter', which is then connected to a 'Measurement Device'. + +Diagram of measurement setup for OTA Co-location emissions, TX OFF power. It shows a test system enclosure with a positioner, AAS BS, calibrated point, coordinate reference, co-location test antenna, test antenna, measurement receiver, switch/limiter/filter, and measurement device. + +Figure D.1.4-1: Measurement set up for OTA Co-location emissions, TX OFF power + +### D.1.5 OTA Transmitter Intermodulation + +![Diagram of measurement setup for OTA Transmitter intermodulation. It is similar to the previous diagram but includes a 'Signal Generator for the interfering signal' connected to the Co-Location Test Antenna via a switch/limiter/filter.](b664da64b7121b86310de02c98642405_img.jpg) + +This diagram shows the measurement setup for OTA Transmitter intermodulation. It is identical to the setup in Figure D.1.4-1, but instead of a 'Measurement Device', a 'Signal Generator for the interfering signal' is connected to the 'Switch, limiter or filter' which is connected to the Co-Location Test Antenna. + +Diagram of measurement setup for OTA Transmitter intermodulation. It is similar to the previous diagram but includes a 'Signal Generator for the interfering signal' connected to the Co-Location Test Antenna via a switch/limiter/filter. + +Figure D.1.5-1: Measurement set up for OTA Transmitter intermodulation + +## D.2 Receiver + +### D.2.1 OTA sensitivity and OTA Reference sensitivity + +![Figure D.2.1-1: Measurement set up for OTA sensitivity and OTA reference sensitivity](c0e1c8d37f9cd96595cb6370b1b5a8c7_img.jpg) + +The diagram illustrates the measurement setup for OTA sensitivity and OTA reference sensitivity. It shows a test system enclosure with a jagged border. Inside, on the left, a 'Test antenna' is positioned. A 'Signal generator for the wanted signal' is connected to this antenna. A label 'Test antenna polarisation can be adjusted' points to the antenna. On the right, an 'AAS BS' (Active Antenna System Base Station) is shown. A 'Test system Calibrated point' is marked above it. A coordinate system is centered on the AAS BS with a vertical dashed line, an angle $\theta$ from the vertical, an angle $\phi$ from the horizontal, and a reference point '0'. A label 'AAS declared coordinate reference point and orientation' points to this origin. The entire setup is enclosed in a 'Test system enclosure'. + +Figure D.2.1-1: Measurement set up for OTA sensitivity and OTA reference sensitivity + +Figure D.2.1-1: Measurement set up for OTA sensitivity and OTA reference sensitivity + +The OTA chamber shown in figure D.2.1-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +### D.2.2 OTA Dynamic range + +![Figure D.2.2-1: Measurement set up for OTA Dynamic range](acb90ab4b1096f13fbf453251ca3ffd2_img.jpg) + +The diagram illustrates the measurement setup for OTA dynamic range. It shows a test system enclosure with a jagged border. Inside, on the left, a 'Test antenna' is positioned. A 'Signal Generator for the wanted signal' is connected to 'ATT1', which is then connected to a 'Hybrid'. A 'Signal Generator for the AWGN interfering signal' is connected to 'ATT2', which is also connected to the 'Hybrid'. The output of the 'Hybrid' is connected to the 'Test antenna'. A label 'Test antenna polarisation can be adjusted' points to the antenna. On the right, an 'AAS BS' (Active Antenna System Base Station) is shown. A 'Test system Calibrated point' is marked above it. A coordinate system is centered on the AAS BS with a vertical dashed line, an angle $\theta$ from the vertical, an angle $\phi$ from the horizontal, and a reference point '0'. A label 'AAS declared coordinate reference point and orientation' points to this origin. The entire setup is enclosed in a 'Test system enclosure'. + +Figure D.2.2-1: Measurement set up for OTA Dynamic range + +Figure D.2.2-1: Measurement set up for OTA Dynamic range + +The OTA chamber shown in figure D.2.2-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +### D.2.3 OTA Adjacent channel selectivity, general blocking, and narrowband blocking + +![Figure D.2.3-1: Measurement set up for OTA ACS and narrowband blocking. The diagram illustrates a signal generation chain on the left consisting of two signal generators (one for the wanted signal, one for the interfering signal) connected to attenuators ATT1 and ATT2. These feed into a Hybrid coupler. The output of the hybrid is connected to a Test antenna inside an anechoic chamber (indicated by absorber patterns). The test antenna's polarisation can be adjusted. Inside the chamber, the antenna faces an AAS BS (Active Antenna System Base Station). A calibrated point is marked on the AAS BS with a coordinate system showing angles theta (θ) and phi (φ). A dashed line indicates the AAS declared coordinate reference point and orientation. The entire chamber is labeled as a Test system enclosure.](36cc7cc6626dc09bfcc888a4f8e2e9e4_img.jpg) + +Figure D.2.3-1: Measurement set up for OTA ACS and narrowband blocking. The diagram illustrates a signal generation chain on the left consisting of two signal generators (one for the wanted signal, one for the interfering signal) connected to attenuators ATT1 and ATT2. These feed into a Hybrid coupler. The output of the hybrid is connected to a Test antenna inside an anechoic chamber (indicated by absorber patterns). The test antenna's polarisation can be adjusted. Inside the chamber, the antenna faces an AAS BS (Active Antenna System Base Station). A calibrated point is marked on the AAS BS with a coordinate system showing angles theta (θ) and phi (φ). A dashed line indicates the AAS declared coordinate reference point and orientation. The entire chamber is labeled as a Test system enclosure. + +**Figure D.2.3-1: Measurement set up for OTA ACS and narrowband blocking** + +## Test + +The OTA chamber shown in figure D.2.3-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +![Figure D.2.3-2: Measurement set up for OTA general blocking. This diagram is similar to Figure D.2.3-1 but includes a circulator component between the Hybrid coupler and the Test antenna. One port of the circulator is connected to a Termination. The rest of the setup, including the signal generators, attenuators, test antenna, and AAS BS inside the test system enclosure, remains the same as in the previous figure.](0512d726ae1370e8b8329956690b1a0d_img.jpg) + +Figure D.2.3-2: Measurement set up for OTA general blocking. This diagram is similar to Figure D.2.3-1 but includes a circulator component between the Hybrid coupler and the Test antenna. One port of the circulator is connected to a Termination. The rest of the setup, including the signal generators, attenuators, test antenna, and AAS BS inside the test system enclosure, remains the same as in the previous figure. + +**Figure D.2.3-2: Measurement set up for OTA general blocking** + +The OTA chamber shown in figure D.2.3-2 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +## D.2.4 OTA Blocking + +![Diagram of measurement setup for OTA Blocking](febfdd6a7182116484c126105b53fdaf_img.jpg) + +This diagram illustrates the measurement setup for OTA Blocking. It shows a rectangular test system enclosure with jagged edges representing anechoic chamber walls. Inside, on the left, are two test antennas: one labeled 'Test antenna (in band)' and the other 'Test antenna (out of band)'. Each antenna is connected to a signal generator, labeled 'Signal Generator for the wanted signal' and 'Signal Generator for the interfering signal' respectively. A note indicates that 'Test antenna polarisation can be adjusted'. On the right, a box labeled 'AAS BS' (Active Antenna System Base Station) is positioned. A dashed vertical line passes through the center of the AAS BS, labeled 'Test system Calibrated point'. The 'AAS declared coordinate reference point and orientation' is marked at the center of the AAS BS. A coordinate system is shown with the origin at the center, a vertical axis labeled $\theta$ , and a horizontal axis labeled $\varphi$ . + +Diagram of measurement setup for OTA Blocking + +Figure D.2.4-1: Measurement set up for OTA Blocking + +The OTA chamber shown in figure D.2.4-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +![Diagram of measurement setup for OTA co-location blocking](8b6f7b51bc160aa80e286e818baa7998_img.jpg) + +This diagram illustrates the measurement setup for OTA co-location blocking. It shows a rectangular test system enclosure with jagged edges. Inside, on the left, is a test antenna labeled 'Test antenna (in band)', connected to a 'Signal Generator for the wanted signal'. A note indicates that 'Test antenna polarisation can be adjusted'. On the right, a box labeled 'AAS BS' is positioned. A dashed vertical line passes through the center of the AAS BS, labeled 'Test system Calibrated point'. The 'AAS declared coordinate reference point and orientation' is marked at the center of the AAS BS. A coordinate system is shown with the origin at the center, a vertical axis labeled $\theta$ , and a horizontal axis labeled $\varphi$ . A 'Co-Location Test Antenna' is shown as a small red rectangle at the bottom of the AAS BS. A red dashed line connects this antenna to a 'Signal Generator for the interfering signal' located outside the enclosure at the bottom. + +Diagram of measurement setup for OTA co-location blocking + +Figure D.2.4-2: Measurement set up for OTA co-location blocking + +## D.2.5 OTA Receiver spurious emissions + +![Diagram of measurement setup for OTA receiver spurious emissions. It shows a test system enclosure with a positioner holding an AAS BS at a calibrated point. A test antenna is positioned outside the enclosure, connected to a measurement receiver. Coordinate reference points and orientation angles theta and phi are indicated.](87661c01f79c13b3ea49e7d3e9782c48_img.jpg) + +The diagram illustrates the measurement setup for OTA receiver spurious emissions. It features a 'Test system enclosure' represented by a rectangular box with jagged edges. Inside the enclosure, on the left, is an 'AAS BS' (Active Antenna System Base Station) mounted on a 'Positioner'. A dashed vertical line passes through the AAS BS, labeled 'Test system Calibrated point'. To the right of this line is the 'AAS declared coordinate reference point and orientation'. A circular coordinate system is centered on the AAS BS, with angles $\theta$ and $\phi$ indicated. Outside the enclosure on the right is a 'Test antenna' connected to a 'Measurement receiver'. + +Diagram of measurement setup for OTA receiver spurious emissions. It shows a test system enclosure with a positioner holding an AAS BS at a calibrated point. A test antenna is positioned outside the enclosure, connected to a measurement receiver. Coordinate reference points and orientation angles theta and phi are indicated. + +Figure D.2.5-1: Measurement set up for OTA receiver spurious emissions + +## D.2.6 OTA Receiver intermodulation + +![Diagram of measurement setup for OTA receiver intermodulation. It shows three signal generators (wanted, CW interfering, and modulated interfering) connected through attenuators (ATT1, ATT2, ATT3) and hybrids. The signals are combined and fed into a test antenna inside a test system enclosure. The test antenna's polarization can be adjusted. The test system enclosure contains an AAS BS at a calibrated point with coordinate reference points and orientation angles theta and phi.](8be5d9cba2614c3e06e06525a14c5a3b_img.jpg) + +The diagram illustrates the measurement setup for OTA receiver intermodulation. On the left, three signal generators are shown: 'Signal Generator for the wanted signal', 'Signal Generator for the CW interfering signal', and 'Signal Generator for the modulated interfering signal'. Each is connected to an attenuator labeled 'ATT1', 'ATT2', and 'ATT3' respectively. The outputs of ATT1 and ATT2 are combined in a 'Hybrid' block. The output of ATT3 is also combined in another 'Hybrid' block. The outputs of these two hybrid blocks are then combined in a third 'Hybrid' block, which feeds into a 'Test antenna'. A label 'Test antenna polarisation can be adjusted' points to this antenna. The test antenna is positioned inside a 'Test system enclosure' (a rectangular box with jagged edges). Inside the enclosure, on the right, is an 'AAS BS' mounted at a 'Test system Calibrated point'. A dashed vertical line passes through the AAS BS, labeled 'AAS declared coordinate reference point and orientation'. A circular coordinate system is centered on the AAS BS, with angles $\theta$ and $\phi$ indicated. + +Diagram of measurement setup for OTA receiver intermodulation. It shows three signal generators (wanted, CW interfering, and modulated interfering) connected through attenuators (ATT1, ATT2, ATT3) and hybrids. The signals are combined and fed into a test antenna inside a test system enclosure. The test antenna's polarization can be adjusted. The test system enclosure contains an AAS BS at a calibrated point with coordinate reference points and orientation angles theta and phi. + +Figure D.2.6-1: Measurement set up for OTA receiver intermodulation + +The OTA chamber shown in figure D.2.6-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +## D.2.7 OTA In-channel selectivity + +![Diagram of the measurement setup for OTA In-channel selectivity.](e7511e4fa0a0df6c02eb793c62524690_img.jpg) + +The diagram illustrates the measurement setup for OTA In-channel selectivity. It features a rectangular test system enclosure with jagged, sawtooth-like walls representing anechoic chamber lining. Inside the enclosure, on the left, is a 'Test antenna' mounted on a stand. A label 'Test antenna polarisation can be adjusted' points to this antenna. To the right of the test antenna is an 'AAS BS' (Active Antenna System Base Station) unit. A label 'Test system Calibrated point' points to a specific location on the AAS BS. A coordinate system is shown at the center of the AAS BS, with a vertical dashed line labeled '0', an angle $\theta$ measured from the vertical, and an angle $\phi$ measured from the horizontal. A label 'AAS declared coordinate reference point and orientation' points to the center of the AAS BS. Outside the enclosure on the left, a 'Signal Generator for the wanted signal and the E-UTRA interfering signal' is connected to a 'Hybrid' box. The output of the Hybrid box is connected to the Test antenna. + +Diagram of the measurement setup for OTA In-channel selectivity. + +**Figure D.2.7-1: Measurement set up for OTA In-channel selectivity** + +The OTA chamber shown in figure D.2.7-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +## D.3 Performance requirements + +![Figure D.3-1: Measurement set up for single TX, single demodulation branch radiated performance requirements. The diagram shows a signal generator for the AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator 1 and then ATT2. Both ATT1 and ATT2 feed into a Hybrid, which is connected to a PA. The PA is connected to a Test antenna inside a Test system enclosure. The Test system enclosure contains an AAS BS with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'.](888ca03f14a7d40e9cf34ed55778a679_img.jpg) + +Figure D.3-1: Measurement set up for single TX, single demodulation branch radiated performance requirements. The diagram shows a signal generator for the AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator 1 and then ATT2. Both ATT1 and ATT2 feed into a Hybrid, which is connected to a PA. The PA is connected to a Test antenna inside a Test system enclosure. The Test system enclosure contains an AAS BS with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'. + +**Figure D.3-1: Measurement set up for single TX, single demodulation branch radiated performance requirements** + +![Figure D.3-2: Measurement set up for single TX, dual polarization radiated performance requirements. The diagram shows a signal generator for the first AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator #1 and then ATT2. Both ATT1 and ATT2 feed into Hybrid 1, which is connected to PA 1. PA 1 is connected to a Test antenna polarization A inside a Test system enclosure. The signal generator for the wanted signal is also connected to Fading channel emulator #2 and then ATT3. ATT3 feeds into Hybrid 2, which is connected to PA 2. PA 2 is connected to a Test antenna polarization B inside the Test system enclosure. The Test system enclosure contains an AAS BS with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'.](4b11ea1901434ce484d71c4050c656b4_img.jpg) + +Figure D.3-2: Measurement set up for single TX, dual polarization radiated performance requirements. The diagram shows a signal generator for the first AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator #1 and then ATT2. Both ATT1 and ATT2 feed into Hybrid 1, which is connected to PA 1. PA 1 is connected to a Test antenna polarization A inside a Test system enclosure. The signal generator for the wanted signal is also connected to Fading channel emulator #2 and then ATT3. ATT3 feeds into Hybrid 2, which is connected to PA 2. PA 2 is connected to a Test antenna polarization B inside the Test system enclosure. The Test system enclosure contains an AAS BS with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'. + +**Figure D.3-2: Measurement set up for single TX, dual polarization radiated performance requirements** + +![Figure D.3-3: Measurement set up for dual TX, dual polarization radiated performance requirements. The diagram shows two signal generators for the wanted signal, TX1 and TX2. TX1 is connected to Fading channel emulator #1 and Fading channel emulator #2. TX2 is connected to Fading channel emulator #3 and Fading channel emulator #4. Fading channel emulator #1 and Fading channel emulator #2 feed into Hybrid 1. Fading channel emulator #3 and Fading channel emulator #4 feed into Hybrid 2. Hybrid 1 is connected to ATT2, which feeds into Hybrid 3. Hybrid 3 is connected to PA 1. PA 1 is connected to a Test antenna polarization A inside a Test system enclosure. Hybrid 2 is connected to ATT3, which feeds into Hybrid 4. Hybrid 4 is connected to PA 2. PA 2 is connected to a Test antenna polarization B inside the Test system enclosure. The signal generator for the first AWGN signal is connected to ATT1, which feeds into Hybrid 3. The signal generator for the second AWGN signal is connected to ATT4, which feeds into Hybrid 4. The Test system enclosure contains an AAS BS with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'.](71440aab73c3d21521dba3a413e3a7ca_img.jpg) + +Figure D.3-3: Measurement set up for dual TX, dual polarization radiated performance requirements. The diagram shows two signal generators for the wanted signal, TX1 and TX2. TX1 is connected to Fading channel emulator #1 and Fading channel emulator #2. TX2 is connected to Fading channel emulator #3 and Fading channel emulator #4. Fading channel emulator #1 and Fading channel emulator #2 feed into Hybrid 1. Fading channel emulator #3 and Fading channel emulator #4 feed into Hybrid 2. Hybrid 1 is connected to ATT2, which feeds into Hybrid 3. Hybrid 3 is connected to PA 1. PA 1 is connected to a Test antenna polarization A inside a Test system enclosure. Hybrid 2 is connected to ATT3, which feeds into Hybrid 4. Hybrid 4 is connected to PA 2. PA 2 is connected to a Test antenna polarization B inside the Test system enclosure. The signal generator for the first AWGN signal is connected to ATT1, which feeds into Hybrid 3. The signal generator for the second AWGN signal is connected to ATT4, which feeds into Hybrid 4. The Test system enclosure contains an AAS BS with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'. + +**Figure D.3-3: Measurement set up for dual TX, dual polarization radiated performance requirements** + +The OTA chambers shown in figures D.3-1, D.3-2 and D.3-3 are intended to be generic and can be replaced with any suitable OTA chamber (e.g. far field anechoic chamber, CATR, etc.). The PA depicted in figures D.3-1, D.3-2 and D.3-3 is optional. Fading channel emulators are included when needed according to the requirement description. + +--- + +## Annex E (normative): Estimation of Measurement Uncertainty + +### E.1 General + +Common measurement uncertainty budget calculation principle, was described in TR 37.941 [38]. + +--- + +### E.2 Measurement methodology descriptions + +The AAS BS radiated measurement method descriptions, including description of the calibration stage, and the measurement stage, are described separately for each of the OTA tests, i.e. for radiated transmit power and for OTA sensitivity test in TR 37.941 [38]. + +--- + +### E.3 Measurement uncertainty budget format + +Each test methodology is characterized by different uncertainty contributors. Moreover, within single test methodology, certain uncertainty contributors will need to be modified, depending on the transmitter, or receiver test. Therefore, separate uncertainty budget format were collected for all considered Test Systems in TR 37.941 [38], specifying uncertainty contributors for calibration stage, as well as measurement stage. + +--- + +### E.4 Measurement uncertainty budgets + +Descriptions of uncertainty assessment for radiated transmit power and for OTA sensitivity test were described separately for each of the considered Tests Systems as in TR 37.941 [38]. + +--- + +### E.5 Measurement error contribution descriptions + +Detailed descriptions of the uncertainty contributors for the radiated transmit power and OTA sensitivity test were described separately for each of the considered Tests Systems as in TR 37.941 [38]. + +--- + +## Annex F (normative): TRP measurement grids + +### F.1 General + +The annex describes various procedures for BS OTA TRP measurements. These procedures can provide either an accurate or an over-estimate of TRP values. The procedures for an accurate estimate can be applied to all TRP requirements. However, if a TRP requirement does not need accurate TRP estimate then the procedures for over-estimate of TRP may be used in order to have a reasonable OTA test time. Pre-scan does not provide an accurate TRP estimate or over-estimate of TRP. Pre-scan is a fast but coarse method that is used to identify the spurious emission frequencies with emission power as described in annex F.13. A sequential measurement is then made at the emission frequencies, to assess the TRP as described in annex F.2 to annex F.9. + +When making TRP measurements the alignment between EUT and measurement antenna is important to achieve expected measurement uncertainty; + +1. The measurement antenna needs to be aligned tangential to the measurement surface forming a sphere around the EUT, in order to measure the TRP properly. +2. Test methods described in clauses F.5.1, F.5.2, F.10, F.11 and F.12 require angular alignment between the selected measurement grid and EUT radiation pattern in order to measure peak values in the main beams. Angular misalignment can lead to differences in the actual and measured angular positions of the intended maximum EIRP. +3. Test methods described in clause F.5.3, F.6 and F.9 are designed to be independent of rotations of the angular grid, and hence angular alignment between the measurement grid and EUT is not needed. + +--- + +### F.2 Spherical equal angle grid + +#### F.2.1 General + +$TRP_{\text{Estimate}}$ is defined as: + +when EIRP measurements is used or as: + +when power density measurements are used, and $d$ is the test distance. $N$ and $M$ are the number of samples in the $\theta$ and $\phi$ angles. Each $(\theta_i, \phi_j)$ is a sampling point. The sampling angular intervals for $\theta$ and $\phi$ angles are $\Delta\theta$ and $\Delta\phi$ . The sampling intervals and are described in F.2.2. + +#### F.2.2 Reference angular step criteria + +The reference angular steps $\Delta\theta$ and $\Delta\phi$ , in degrees, are defined as: + +The upper limit for these reference angular steps of $\Delta\theta$ ensures a low Summation Error (SE) when $d$ is large compared to the DUT dimensions. + +$D_{\text{cyl}}$ and $D$ are calculated as: + +The definition of $d$ , $w$ and $h$ is shown in Figure F.2.2-1. The radiation source can be EUT antenna array or the whole of EUT. + +![Figure F.2.2-1: Dimensions of a radiation source: depth (d), width (w) and height (h). The diagram shows a 3D coordinate system with x, y, and z axes. A rectangular prism representing the radiation source is positioned at the origin. Its dimensions are labeled: 'd' for depth along the x-axis, 'w' for width along the y-axis, and 'h' for height along the z-axis. A red vector labeled 'P' originates from the center of the prism, pointing towards a point in space. The angle between the z-axis and the vector P is labeled 'θ'. The angle between the y-axis and the projection of the vector P onto the xy-plane is labeled 'φ'. Dashed lines indicate the projection of the vector P onto the xy-plane and the z-axis.](854a7aa42ede8d319880a076c262338e_img.jpg) + +Figure F.2.2-1: Dimensions of a radiation source: depth (d), width (w) and height (h). The diagram shows a 3D coordinate system with x, y, and z axes. A rectangular prism representing the radiation source is positioned at the origin. Its dimensions are labeled: 'd' for depth along the x-axis, 'w' for width along the y-axis, and 'h' for height along the z-axis. A red vector labeled 'P' originates from the center of the prism, pointing towards a point in space. The angle between the z-axis and the vector P is labeled 'θ'. The angle between the y-axis and the projection of the vector P onto the xy-plane is labeled 'φ'. Dashed lines indicate the projection of the vector P onto the xy-plane and the z-axis. + +**Figure F.2.2-1: Dimensions of a radiation source: depth (d), width (w) and height (h)** + +Optionally, in the case of a Uniform Linear Array (ULA), when $d$ is negligible ( $d \approx 0$ ) and when the EUT is mounted along the yz plane as shown in figure F.2.2-2, the reference angular step, in degrees, can be determined by + +Where $D_y$ is the length of radiating parts of EUT along y-axis, $D_z$ is the length of radiating parts of EUT along the z-axis and $\lambda$ is wavelength for the measured frequency. + +![Figure F.2.2-2: Spherical coordinate system for OTA conformance testing of EUT. The diagram shows a sphere with a coordinate system centered at the origin. The x-axis points towards the bottom-left, the y-axis points to the right, and the z-axis points upwards. A point on the sphere is defined by its spherical coordinates: the polar angle theta (θ) measured from the positive z-axis, and the azimuthal angle phi (φ) measured in the xy-plane from the positive y-axis. The projection of the point onto the yz-plane is labeled Kz, and its projection onto the xy-plane is labeled Ky.](51923f79574a4c945d05c5ad3ff8dda5_img.jpg) + +Figure F.2.2-2: Spherical coordinate system for OTA conformance testing of EUT. The diagram shows a sphere with a coordinate system centered at the origin. The x-axis points towards the bottom-left, the y-axis points to the right, and the z-axis points upwards. A point on the sphere is defined by its spherical coordinates: the polar angle theta (θ) measured from the positive z-axis, and the azimuthal angle phi (φ) measured in the xy-plane from the positive y-axis. The projection of the point onto the yz-plane is labeled Kz, and its projection onto the xy-plane is labeled Ky. + +**Figure F.2.2-2: Spherical coordinate for OTA conformance testing of EUT** + +Where due to practical reasons such as time constraints or turn-table precision, measurement with the reference steps is not practical, sparser grids can be used. Use of sparse grids can lead to errors in TRP assessment. In order to characterize these errors, the SF (sparsity factor) of the grid is defined as: + +Where $\Delta\phi$ and $\Delta\theta$ are the actual angular steps used in the measurement. + +Alternatively, when the EUT radiating dimensions are not known. For each frequency within the *downlink operating band* including $\Delta f_{\text{OBUE}}$ , the reference angular steps can be specified in terms of the *beamwidth* of the wanted signal as + +where $\lambda_0$ is the wavelength of the wanted signal, and $\text{BeW}_\phi$ and $\text{BeW}_\theta$ are the *beamwidth* of the wanted signal in the $\phi$ -axis and $\theta$ -axis, respectively. + +$\text{BeW}_\phi$ and $\text{BeW}_\theta$ may be set to *beamwidth* declared for the *OTA AAS BS* radiated transmit power requirement provided the same *beam* is applied to test in-band TRP requirements. + +NOTE: *Beamwidth* is approximately equal to half the first-null beam width. + +## F.3 Spherical equal area grid + +$\text{TRP}_{\text{Estimate}}$ is defined as: + +N is the total number of samples and specified as: + +The sampling intervals $\Delta\phi$ and $\Delta\theta$ are described in F.2.2. Each $(\phi, \theta)$ is a sampling point. + +## F.4 Spherical Fibonacci grid + +$TRP_{Estimate}$ is defined as: + +$N$ is the total number of samples and specified as: + +The sampling intervals $\Delta\theta$ and $\Delta\phi$ are described in F.2.2. Each $(\theta, \phi)$ is a sampling point, where $\theta$ and $\phi$ , in degrees, are defined as: + +## F.5 Orthogonal cut grid + +### F.5.1 General + +Here, at least two cuts (default) shall be used, an optional third cut can be used. The alignment of the cuts must be along the symmetry planes of the antenna array. No alignment is required for spurious emissions. + +When alignment is required: + +1. The first mandatory cut is a horizontal cut passing through the peak direction of the main beam. +2. The second mandatory is a vertical cut passing through the peak direction of the main beam. Using the data from these two mandatory cuts, a conditional pattern multiplication can be used. +3. The third optional cut is a vertical cut orthogonal to the first and the second cut. + +When alignment is not required, the cuts can be aligned arbitrarily. + +Once the number and the orientation of the cuts are decided, the total EIRP is measured on the orthogonal cuts and the TRP is then calculated as follows: First the contributions from each cut is calculated as: + +where $P$ is the number of sampling points in the cut. The final contribution for all cuts is calculated as: + +where $N$ is the number of cuts. Note that when orthogonal cuts are measured, the intersection points are measured multiple times and the repeated values can be removed from the samples before averaging. + +When two cuts measurements are used, a conditional pattern multiplication can be applied. The following are the conditions for applying pattern multiplication: + +- i. The vertical cut (and the main beam) is in the $\phi$ -plane +- ii. The frequency of the emission is within the downlink operating band. +- iii. The bandwidth of the emission is the same as the bandwidth of the in-band modulated signal +- iv. The emission appears/disappears when the Tx power is turned on/off. +- v. The antenna arrays of the EUT + 1. Have rectangular grids of antenna element positions + 2. Have symmetry planes that are vertical and horizontal. + +### 3. Have parallel antenna planes + +The antenna array is here assumed to be placed in the $yz$ -plane. The pattern multiplication is performed in $uv$ -coordinates and the data in the two cuts are denoted $\phi = 0^\circ$ and a vertical cut with data $\phi = 180^\circ$ . The data is split in two parts corresponding to the forward and backward hemispheres. The $uv$ -coordinates are the projections of the angular directions onto the antenna plane, here the $yz$ -plane. Using the spherical coordinates as depicted in figure F.2.2.-1 the $u$ and $v$ coordinates are defined as: + +Note that only the data on the cuts are measured. + +Calculate power density/EIRP values outside the two cardinal cuts as + +The pattern multiplication is applied separately for the forward (fwd) and backward (bwd) hemisphere. The TRP is then calculated as: + +NOTE: The numerical singularity at $\phi = 0^\circ$ must be treated with care, e.g. by change of variables. + +## F.5.2 Operating band unwanted emissions + +The procedure is as follows: + +- 1) Follow steps described in annex I.5.1 for the first two mandatory cuts and calculate the $TRP_{Estimate}$ . +- 2) Compare the $TRP_{Estimate}$ to the limit. +- 3) If the $TRP_{Estimate}$ is above the limit, perform the measurement on an additional third cut and repeat steps 1 to 2. + +## F.5.3 Spurious unwanted emissions + +The procedure is as follows: + +- 1) Follow steps described in annex F.5.1 for two cuts and calculate the preliminary $TRP_{Estimate}$ . +- 2) Add the appropriate correction factor $\Delta TRP$ according to table F.5.3-1 to ensure overestimation with 95% confidence. +- 3) Compare the corrected $TRP_{Estimate}$ (including $\Delta TRP$ ) to the limit. +- 4) If the corrected $TRP_{Estimate}$ is above the limit, perform the measurement on an additional third cut and repeat steps 1 to 3. + +**Table F.5.3-1: The correction factor for two or three cuts dense sampling** + +| | Three cuts | Two cuts | +|-------------------------------------|------------|----------| +| Correction factor $\Delta TRP$ (dB) | 2.0 | 2.5 | + +## F.6 Wave vector space grid + +If EUT is mounted along the $yz$ plane as shown in figure F.2.2-1, the reference step in wave vector space can be determined by: + +where $D_y$ is the length of radiating parts of EUT along y-axis, $D_z$ is the length of radiating parts of EUT along the z-axis. + +According to the relationship between the normalized wave vector and spherical coordinate, the wave vector can be represented as following: + +The total radiated power (TRP) in the wave vector space is determined by: + +Where due to practical reasons such as time constraints or turn-table precision, measurement with the reference steps is not practical, sparser grids can be used. Use of sparse grids can lead to errors in TRP assessment. In order to characterize these errors, the SF (sparsity factor) of the grid is defined as: + +Where $\Delta\theta$ and $\Delta\phi$ are the actual steps used in the wave vector space in the measurement and the upper bound of their value is 15 degrees. + +## F.7 Orthogonal 2 cuts with pattern multiplication + +This method can be used when the antenna symmetries are compatible with pattern multiplication, see Clause F.1.2.4. The procedure is as follows: + +1. Calculate the reference angular steps as described in Clause F.1.2. +2. Align the EUT to allow for proper pattern multiplication. See Clause F.5. Measure EIRP on two orthogonal cuts with steps smaller or equal to the reference steps according to step 1. +3. Apply pattern multiplication according to Clause F.5 to extrapolate the two cuts data to full-sphere. +4. Apply numerical integration to obtain the TRP estimate as described in Clause F.5. + +## F.8 Void + +## F.9 Full sphere with sparse sampling + +The procedure is as follows: + +1. Set the angular grid: + - a. Non-harmonic frequencies: choose the angular steps $\Delta\theta$ and $\Delta\phi$ smaller than or equal to 15 degrees. Calculate the sparsity factor (SF) as + +and the correction factor as: + +where $\Delta\theta_{ref}$ corresponds to 15 degrees angular step. If the sparsity factor is smaller than 1, the correction factor $\Delta\text{TRP}$ is 0 dB. + +- b. Harmonic frequencies with fixed beam test signal: choose the angular steps smaller than or equal to the reference angular steps $\Delta\theta_{ref}$ and $\Delta\phi_{ref}$ . Correction factor $\Delta\text{TRP}$ is 0 dB. + +- c. Harmonic frequencies with beam sweeping test signal: set the angular steps to 15 degrees. Correction factor is $\Delta\text{TRP}$ 0 dB. +2. Apply a suitable numerical integration to calculate the TRP estimate. +3. Add the appropriate correction factor $\Delta\text{TRP}$ according to step 1 to ensure an overestimation with 95% confidence. +4. Compare the (TRP estimate + $\Delta\text{TRP}$ ) with the limit. If the (TRP estimate + $\Delta\text{TRP}$ ) is above the limit, choose a smaller angular step and repeat steps 2-4. If the sparsity factor is less than one, no significant improvement of accuracy is expected. + +--- + +## F.10 Beam-based directions + +Beam-based direction can be used in the base station operating band only if the directivity of the radiation pattern of the emissions being measured is known. *band*. $\text{TRP}_{\text{Estimate}}$ is defined as: + +where $\text{EIRP}_{\text{max}}$ is the maximum EIRP in the *beam peak direction* within a particular *beam direction pair* and $D$ is directivity of the EUT antenna. + +--- + +## F.11 Peak method + +The peak method can be used when frequencies with unwanted peak emissions are identified during pre-scan. The method does not provide an estimate of TRP. + +For each peak emission frequency identified during pre-scan, measure peak EIRP or power density as follows: + +1. Move EUT and test antenna to the same position where the peak emission is recorded during the pre-scan. +2. Move the EUT around the position and test antenna orientation to find the final peak EIRP or power density. +3. The measured peak power density or EIRP shall be used to demonstrate conformance. + +NOTE: Peak EIRP is the linear sum of two orthogonal polarised components. + +--- + +## F.12 Equal sector with peak average + +Equal sector with peak average can be performed on frequencies with unwanted peak emission, which are considered by the peak method for further measurements. + +The spherical angle $\Omega$ is divided into $K$ equal sectors. If the largest dimension of EUT is less than 60 cm, then each sector is a half quadrant of $45^\circ$ . + +For each peak emission frequency, measure peak EIRP of beams belonging to different sectors of the sphere as follows: + +1. Move EUT and test antenna to the same position where the emission peak is recorded during the pre-scan. +2. Move EUT around the position and test antenna orientation to find the final peak EIRP. +3. Repeat Steps 1 to 2 until all sectors are covered. +4. Calculate $\text{TRP}_{\text{Estimate}}$ as: + +where $\text{EIRP}_k$ is the peak EIRP in the $k$ th sector. + +NOTE: Peak EIRP is the linear sum of two orthogonal polarised components. + +--- + +## F.13 Pre-scan + +Pre-scan is used to identify frequencies with unwanted emission power levels above a certain threshold. The pre-scan does not provide an estimate of TRP. An emission frequency identified by a pre-scan may be further investigated by any of the TRP measurement methods in this annex. + +The procedure for pre-scan is as follows: + +1. Scan the entire surface around EUT. +2. Rotate test antenna to cover all possible polarisations of emissions to detect maximum emissions. +3. Record the list of frequencies and corresponding unwanted emission power levels, EUT spatial positions, and test antenna polarization for which the maximum emission levels occur. +4. Emissions which are 20 dB or more below the specified limit shall not require further measurements. + +## Annex G (normative): Environmental requirements for the BS equipment + +### G.1 General + +For each test in the present document, the environmental conditions under which the AAS BS is to be tested are defined. The environmental conditions and class shall be from the relevant IEC specifications or the corresponding ETSI specifications. + +For OTA requirements where it is not possible to environmentally control the entire calibrated OTA chamber either localised control of the AAS BS hardware or alternative OTA measurements which are then related to the original specification are acceptable. + +### G.2 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 G.2-1. + +**Table G.2-1: 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. + +### G.3 Extreme test environment + +#### G.3.1 General + +The manufacturer shall declare one of the following: + +- 1) the equipment class for the equipment under test, as defined in the IEC 60721-3-3 [21] or ETSI EN 300 019-1-3 [23] ("Stationary use at weather protected locations"); +- 2) the equipment class for the equipment under test, as defined in the IEC 60721-3-4 [22] or ETSI EN 300 019-1-4 [24] ("Stationary use at non weather protected locations"); +- 3) the equipment that does not comply to the mentioned classes, the relevant classes from IEC 60721 [20] documentation for Temperature, Humidity and Vibration shall be declared. + +NOTE: Reduced functionality for conditions that fall outside of the standard operational conditions are not tested in the present document. These may be stated and tested separately. + +## G.3.2 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 60068-2-1 [25]. + +### 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 60068-2-2 [26]. + +NOTE: It is recommended that the equipment is made fully operational prior to the equipment being taken to its lower operating temperature. + +--- + +## G.4 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 60068-2-6 [27]. Other environmental conditions shall be within the ranges specified in annex G.2. + +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. + +--- + +## G.5 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 60068-2-1 [25] Test Ab/Ad and IEC 60068-2-2 [26] 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 60068-2-1 [25] Test Ab/Ad and IEC 60068-2-2 [26] Test Bb/Bd: Dry Heat. + +--- + +## G.6 Measurement of test environments + +The measurement accuracy of the BS 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. + +## G.7 OTA extreme test methods + +### G.7.1 Direct far field method + +The AAS BS under test is placed inside a sealed RF transparent environmental enclosure, as showed in Figure G.7.1-1. This is connected to an environment control system which regulates the temperature inside the enclosure. The remaining equipment inside the OTA chamber (any suitable antenna test range chamber type is acceptable) is outside the environmental control and is at nominal temperature. Positioners, test antennas and all other OTA test equipment do not need to be specified over the extreme temperature range. + +![Figure G.7.1-1: Measurement set up for Extreme conditions for EIRP accuracy using direct far field method. The diagram shows a cross-section of a test setup. A large rectangular 'Test system enclosure' with jagged edges contains a smaller 'Radome like enclosure'. Inside the radome is the 'AAS BS' (Antenna Under Test) mounted on a 'Test system Calibrated point'. A coordinate system is shown with the origin at the AAS BS, with axes labeled theta (θ) and phi (φ). A 'Temperature control system' is connected to the radome. To the right of the radome, a 'Test antenna' is positioned, with a line of sight to the AAS BS. The test antenna is connected to 'Measurement equipment' outside the enclosure. A label 'AAS declared coordinate reference point and orientation' points to the AAS BS.](8bffff22941e018add90bd8d04b6798c_img.jpg) + +Figure G.7.1-1: Measurement set up for Extreme conditions for EIRP accuracy using direct far field method. The diagram shows a cross-section of a test setup. A large rectangular 'Test system enclosure' with jagged edges contains a smaller 'Radome like enclosure'. Inside the radome is the 'AAS BS' (Antenna Under Test) mounted on a 'Test system Calibrated point'. A coordinate system is shown with the origin at the AAS BS, with axes labeled theta (θ) and phi (φ). A 'Temperature control system' is connected to the radome. To the right of the radome, a 'Test antenna' is positioned, with a line of sight to the AAS BS. The test antenna is connected to 'Measurement equipment' outside the enclosure. A label 'AAS declared coordinate reference point and orientation' points to the AAS BS. + +**Figure G.7.1-1: Measurement set up for Extreme conditions for EIRP accuracy using direct far field method** + +The presence of the environmental chamber inside the OTA chamber may affect the measurement accuracy due to additional reflections and refractions, also the loss through the environmental enclosure may not be consistent with direction as the path through the radome may vary with angle. Hence the system should be calibrated in all tested directions. + +NOTE. Currently only a single direction is specified for extreme testing so a single calibration direction is sufficient. + +Conformance may be demonstrated by measuring the difference between the nominal measurement and the extreme measurement ( $\Delta_{\text{sample}}$ ) or by measuring $P_{\text{max,c,EIRP, extreme}}$ directly. + +Measure EIRP for any two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular beam direction pair as $\text{EIRP} = \text{EIRP}_{\text{p1}} + \text{EIRP}_{\text{p2}}$ . + +### G.7.2 Relative method + +The AAS BS under test is placed inside a small (compared to a far field chamber) anechoic chamber which is both RF a screened and suitable for environmental conditioning. The RF conditionals inside the chamber are absorptive and capable of dissipating the power the AAS BS when radiating. A sample antenna or RF probe are placed in a location which gives a sample of the main beam EIRP but does not have to accurately measure the EIRP directly, instead the + +near-field response is measured. For this method test components are exposed to the full temperature range for example the test antenna/probe, cables, absorbers etc. may change as a function of temperature. + +Using the relative method it is also necessary to measure the EIRP under nominal conditions using an appropriately calibrated far field (or near field) test range to obtain $P_{\max,c,EIRP}$ . + +![Diagram of the measurement setup for extreme conditions for EIRP accuracy using the difference method. A central square labeled 'AAS BS' is surrounded by a thick border representing a 'Small shield anechoic and environmental chamber'. To the left, a box labeled 'Temperature control system' is connected to the chamber. To the right, a 'Test antenna/Probe' is positioned inside the chamber, pointing towards the 'AAS BS'. An arrow from the probe points to a box labeled 'Measurement equipment'.](3c8ed97dd81b363f7919bb50f8410baa_img.jpg) + +Diagram of the measurement setup for extreme conditions for EIRP accuracy using the difference method. A central square labeled 'AAS BS' is surrounded by a thick border representing a 'Small shield anechoic and environmental chamber'. To the left, a box labeled 'Temperature control system' is connected to the chamber. To the right, a 'Test antenna/Probe' is positioned inside the chamber, pointing towards the 'AAS BS'. An arrow from the probe points to a box labeled 'Measurement equipment'. + +**Figure F.7.2-1: Measurement set up for Extreme conditions for EIRP accuracy using difference method** + +Measurements from the test antenna/ probe are taken under nominal conditions and extreme conditions to calculate ( $\Delta_{\text{sample}}$ ). The difference between the nominal and extreme conditions ( $\Delta_{\text{sample}}$ ) is then used along with the nominal EIRP measurement ( $P_{\max,c,EIRP}$ ) made in the appropriate far field or near field chamber and compared against the extreme requirement. As follows: + +$$P_{\max,c,EIRP, \text{ extreme}} = P_{\max,c,EIRP} + \Delta_{\text{sample}}.$$ + +Measure EIRP for any two orthogonal polarizations (denoted p1 and p2) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . + +## Annex H (informative): Measuring noise close to noise-floor + +As the emission level seen by the measurement receiver ( $P_{UEM}$ ) for co-location requirements are very low, it is suggested to measure relative noise change instead of absolute noise level. The relations between measured noise change $\delta_1$ , noise floor $N_0$ and the relation to $P_{UEM}$ with respect to the noise floor denoted $\delta_2$ is visualized in Figure H-1. + +![Figure H-1: Relative noise measurement. The figure consists of two parts. On the left, a diagram shows three horizontal lines representing power levels: N_tot (top), N_0 (middle), and P_UEM (bottom). An upward arrow between N_0 and N_tot is labeled delta_1 = N_tot/N_0. A downward arrow between N_0 and P_UEM is labeled delta_2 = N_0/P_UEM. On the right, a graph titled 'UEM level relative to noisefloor' plots delta_2 [dB] on the y-axis (0 to 30) against delta_1 [dB] on the x-axis (0 to 3). A blue curve starts at approximately (0, 27) and decreases monotonically, approaching zero as delta_1 increases.](04c2b0e015697b9fd54da23916a850d6_img.jpg) + +Figure H-1: Relative noise measurement. The figure consists of two parts. On the left, a diagram shows three horizontal lines representing power levels: N\_tot (top), N\_0 (middle), and P\_UEM (bottom). An upward arrow between N\_0 and N\_tot is labeled delta\_1 = N\_tot/N\_0. A downward arrow between N\_0 and P\_UEM is labeled delta\_2 = N\_0/P\_UEM. On the right, a graph titled 'UEM level relative to noisefloor' plots delta\_2 [dB] on the y-axis (0 to 30) against delta\_1 [dB] on the x-axis (0 to 3). A blue curve starts at approximately (0, 27) and decreases monotonically, approaching zero as delta\_1 increases. + +**Figure H-1: Relative noise measurement** + +The absolute emission level in decibel scale is calculated as: + +$P_{UEM} = N_0 - \delta_2$ , where $N_0$ is the noise floor of the measurement receiver and $\delta_2$ is plotted as function of $\delta_1$ in Figure H-1. The absolute noise floor of the measurement receiver, including probe antenna, cables, filter and LNA is determined by a calibration procedure. The calibration will determine the absolute emission level ( $N_0$ ) accuracy of measuring out-of-band unwanted emission close to the thermal noise floor. + +## Annex I (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2016-02 | RAN4#78 | R4-161118 | | | | Specification structure | 0.1.0 | | +| 2016-04 | RAN4#78 bis | R4-162524 | | | | R4-161370 - TP for TS 37.145-2: Adding Annex for relations between core and conformance requirements | 0.2.0 | | +| 2016-05 | RAN4#79 | R4-164927 | | | | R4-164717 - TP to TS 37.145 (part 2) sections 1-5
R4-164718 - TP for TS 37.145-2: Addition of radiated transmit power conformance test requirement in clause 6
R4-164719 - TP to TS 37.145 (part 2) section 7 - Radiated receiver characteristics | 0.3.0 | | +| 2016-08 | RAN4#80 | R4-167179 | | | | R4-166422 - TP to 3GPP TS 37.145-2 - clean up
R4-166218 - TP for TS 37.145-2: Editorial correction on table numbers
R4-166567 - TP to TS 37.145-2: Manufacturer declarations consistency improvements
R4-166938 - TP for TS 37.145-2: Improvements of text in clause 4.8
R4-166940 TP for TS 37.145-2: Improvements on text relating to the reference coordinate system
R4-166939 TP to TR 37.145-2: Test Requirements derivation: Annexes A, B, C, E
R4-166929 TP to TS 37.145-2: Measurement uncertainties and TT values
R4-166931 TP for TS 37.145-2 - On OTA RX sensitivity requirements for AAS
R4-167191 TP to TR 37.145-2: definition and test procedure clarifications for EIRP and EIS | 0.4.0 | | +| 2016-09 | RP-73 | RP-161450 | | | | Editorial corrections after review by ETSI editHelp | 1.0.0 | | +| 2016-09 | RP-73 | | | | | TS was approved by RAN plenary | 13.0.0 | | +| 2016-12 | RP-74 | RP-162422 | 0003 | - | A | Correction of Manufacturer declaration description list in TS 37.145-2 | 13.1.0 | | +| 2017-03 | RP-75 | RP-170586 | 0005 | 1 | F | TS 37.145-2: Clarification of test procedure for radiated transmit power | 13.2.0 | | +| 2017-03 | RP-75 | RP-170586 | 0006 | 1 | F | TS 37.145-2: Corrections | 13.2.0 | | +| 2017-03 | RP-75 | - | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | | +| 2017-06 | RP-76 | RP-171306 | 0011 | | A | CR to TS 37.145-2: Isolation of Band 46 from the AAS BS specification | 14.1.0 | | +| 2017-09 | RP-77 | RP-171968 | 0013 | | A | CR to TS 37.145-2: Editorial corrections, Rel-14 | 14.2.0 | | +| 2017-12 | RAN#78 | RP-172608 | 0015 | 1 | A | Correction of maximum steering directions declarations | 14.3.0 | | +| 2018-03 | RAN#79 | RP-180280 | 0017 | | A | CR to TS 37.145-2: corrections to the EIS test requirements (7.2) Rel-14 | 14.4.0 | | +| 2018-06 | RAN#80 | RP-181109 | 0019 | | A | CR to TR 37.145-2: Clarifications on OTA sensitivity requirement (7.2.1) | 14.5.0 | | +| 2018-06 | SA#80 | | | | | Update to Rel-15 version (MCC) | 15.0.0 | | +| 2018-09 | RAN#81 | RP-181907 | 0034 | | B | CR to TS 37.145-2 | 15.1.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0035 | 1 | F | CR to TS 37.145-2 Correction on OTA test requirements | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0040 | 1 | F | CR to TS 37.145-2: CLTA definition | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0041 | 1 | F | CR to TS 37.145-2: Clarification on CLTA related MU | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0042 | 2 | F | CR to TS 37.145-2: Corrections on OTA Transmit ON/OFF power | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182380 | 0046 | | A | CR to TS 37.145-2: corrections of declarations for the Radiated Transmit Power, Rel-15 | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0047 | | F | CR to TS 37.145-2: correction of the "EIRP accuracy directions set" into "OTA peak directions set" | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0052 | | F | CR to TS 37.145-2: terminology corrections for "Minimum requirements", Rel-15 | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0054 | 1 | F | CR to TS 37.145-2: Clarification on demodulation requirements (8.1) | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0055 | 1 | F | CR to TS 37.145-2: OTA Adjacent Channel Leakage Ratio (6.7.3) and OTA Operating band unwanted emissions (6.7.5) - corrections to text and tables | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0056 | 1 | F | CR to TS 37.145-2: adding TRP measurement procedures in Annex F. | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0060 | 1 | F | CR to 37.145-2: MU clarifications | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0061 | 1 | F | CR to 37.145-2: Corrections to co-location requirements | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0063 | | F | CR to TS 37.145-2: UTRA TDD removal | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0064 | 1 | F | CR to TS 37.145-2: fix for the EUTRA demodulation requirements | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0065 | 1 | F | Cleanup to OTA requirements text | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182387 | 0066 | 1 | F | Correction to RX receiver test directions | 15.2.0 | | +| 2018-12 | RAN#82 | RP-182362 | 0067 | 1 | B | Introduction of NR to 37.145-2 | 15.2.0 | | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------|--------| +| 2018-12 | RAN#82 | RP-182387 | 0068 | 2 | F | CR to TS 37.145-2 - polarisation wording improvements for OTA reference sensitivity | 15.2.0 | +| 2018-12 | RAN#82 | RP-182387 | 0070 | | F | CR to TS 37.145-2 Removal of referencing error for in-band blocking | 15.2.0 | +| 2019-03 | RAN#83 | RP-190419 | 0071 | 2 | F | CR to TS37.145-2 Correction on OTA test requirements | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0073 | 1 | F | Correction to definition of OTA reference sensitivity | 15.3.0 | +| 2019-03 | RAN#83 | RP-190419 | 0074 | 1 | F | Addition of measurement system setup for radiated performance requirements | 15.3.0 | +| 2019-03 | RAN#83 | RP-190419 | 0075 | 1 | F | Correction to TDD OFF power requirement | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0076 | | F | CR to TS 37.145-2: Corrections on blocking requirements | 15.3.0 | +| 2019-03 | RAN#83 | RP-190419 | 0077 | 1 | F | CR to TS 37.145-2: Intermodulation product bandwidth in Tx IMD test (Rel-15) | 15.3.0 | +| 2019-03 | RAN#83 | RP-190419 | 0078 | 1 | F | CR to TS 37.145-2: Corrections to acceptable uncertainty of test system (4.1.2) | 15.3.0 | +| 2019-03 | RAN#83 | RP-190419 | 0080 | 3 | D | TS 37.145-2: Editorial corrections | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0082 | | F | CR to TS 37.145-2: additional reference angular step criteria in Annex F.2.2 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190419 | 0083 | 1 | F | CR to TS 37.145-2 on Correction of unwanted emissions scaling | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0084 | 1 | F | CR to TS 37.145-2: Implementation of 1024QAM for E-UTRA, Rel-15 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0085 | | F | CR to TS 37.145-2: Implementation of sTTI for E-UTRA, Rel-15 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190418 | 0086 | | F | CR to TS 37.145-2: BS Spurious emissions limits for protection of the BS receiver for B28 in Europe, Rel-15 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190419 | 0087 | 2 | F | CR to TS 37.145-2: new Rel-15 bands and isolation of band 49, Tx, Rel-15 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190419 | 0088 | 3 | F | CR to TS 37.145-2: new Rel-15 bands and isolation of band 49, Rx, Rel-15 | 15.3.0 | +| 2019-06 | RAN#84 | RP-191263 | 0090 | 1 | F | CR to TS 37.145-2: Corrections on out-of-band blocking requirement | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0091 | 1 | F | CR to TS 37.145-2: clarification on CSA and RCSA relations for hybrid AAS BS, Rel-15 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191236 | 0093 | 1 | F | CR to TS 37.145-2: updates to Tx spur and Tx co-location | 15.4.0 | +| 2019-06 | RAN#84 | RP-191236 | 0094 | 1 | F | CR to TS 37.145-2: Corrections related to TRP measurements in Annex F | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0095 | 1 | F | CR to TS37.145-2 Correction on OTA test requirements for spurious emissions | 15.4.0 | +| 2019-06 | RAN#84 | RP-191236 | 0096 | | D | CR to TS 37.145-2: Adding reference in clause 6.4.1 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0097 | 1 | F | Clarification on polarisations to be tested | 15.4.0 | +| 2019-06 | RAN#84 | RP-191236 | 0104 | 1 | F | CR to TS 37.145-2: Corrections related to TRP measurements in Annex F | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0105 | | F | Corrections to operation in Band 46 and 49 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0107 | 1 | F | Correction on $\Delta$ FOOB for 37.145-2 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0108 | 1 | F | Addition of power backoff for 256QAM and 1024QAM | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0109 | 1 | F | Blocking requirement for MSR/NR operation | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0110 | 1 | F | Correction of applicable RATs for OOB blocking requirement | 15.4.0 | +| 2019-06 | RAN#84 | RP-191236 | 0111 | | F | CR to TS 37.145-2: Correction on multi-band test configurations | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0112 | | F | CR to TS 37.145-2: Addition of RC test method for spurious emissions in clause 6.7.6 and 7.7.4 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0114 | 2 | F | CR to TS 37.145-2: Clarification om beam identifier declaration in clause 4.10 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0115 | 2 | F | CR to TS 37.145-2: Clarification of TRP methods applicability in Annex F | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0118 | 1 | D | CR to TS 37.145-2: Correction to reference to Annex | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0123 | 1 | F | CR to TS 37.145-2: Correction to Total Radiated Power definition and Single-band RIB | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0124 | 1 | F | CR to TS 37.145-2: Correction on usage of terms TRP and EIRP | 15.4.0 | +| 2019-06 | RAN#84 | RP-191262 | 0125 | | F | CR to TS 37.145-2: Correction of Radiated Interface Boundary (RIB) definition | 15.4.0 | +| 2019-06 | RAN#84 | RP-191236 | 0127 | 1 | F | CR to TR 37.145-2 removal of Tx Diversity for TAE testing | 15.4.0 | +| 2019-06 | RAN#84 | RP-191236 | 0130 | | F | CR to TS 37.145-2: adding further details to spherical Fibonacci grids (F.4) | 15.4.0 | +| 2019-06 | RAN#84 | RP-191258 | 0133 | | F | CR to TS 37.145-2: mirror of operating band and frequency range declaration from NR, Rel-15 | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0134 | 1 | B | CR to TS37.145-2: BS demodulation requirements for NR | 15.4.0 | +| 2019-06 | RAN#84 | RP-191263 | 0135 | | F | Non-AAS CRs mirroring to the AAS specification | 15.4.0 | +| 2019-06 | RAN#84 | RP-191250 | 0116 | 1 | B | n65 introduction to 37.145-2 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191257 | 0136 | | B | CR to 37.145-2: Introduction of Band 87 and 88 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191249 | 0137 | | B | CR to 37.145-2: Introduction of n48 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191245 | 0138 | | B | Introduce Band n18 to 37.145-2 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191243 | 0139 | | B | Introduction of Band n14 in TS 37.145-2 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191247 | 0140 | | B | Introduction of Band n30 in TS 37.145-2 | 16.0.0 | +| 2019-09 | RAN#85 | RP-192054 | 0146 | | A | Correction to RX spurious emissions applicability range for SR E-UTRA BS | 16.1.0 | +| 2019-09 | RAN#85 | RP-192054 | 0148 | | A | CR for TS37.145-2: definition of synchronization operation | 16.1.0 | +| 2019-09 | RAN#85 | RP-192054 | 0150 | | A | CR to TS 37.145-2: Clarification on application of OTA receiver | 16.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------|--------| +| | | | | | | requirements for BS supporting polarization | | +| 2019-09 | RAN#85 | RP-192019 | 0152 | | A | CR to TS 37.145-2: Removal of BS type 2-O in radiated performance requirements for NR | 16.1.0 | +| 2019-09 | RAN#85 | RP-192019 | 0156 | | A | CR to TS 37.145-2: Correction on SEM and operation band unwanted emission | 16.1.0 | +| 2019-09 | RAN#85 | RP-192019 | 0158 | | A | CR to TS37.145-2: Corrections on ICS requirement (Section 7.9.5) | 16.1.0 | +| 2019-09 | RAN#85 | RP-192019 | 0160 | | A | CR to TS37.145-2 Corrections on NBB requirement (section 7.5.5.1.2) | 16.1.0 | +| 2019-09 | RAN#85 | RP-192030 | 0167 | | F | CR on Protection of SUL band n89 to TS 37.145-2 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192019 | 0169 | | A | CR to TS 37.145-2 with addition of reference to data content for test models | 16.1.0 | +| 2019-09 | RAN#85 | RP-192034 | 0172 | 1 | B | n29 introduction to 37.145-2 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192050 | 0176 | | A | CR to 37.145-2: correction of equivalent beams testing, Rel-16 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192019 | 0178 | | A | CR to TS37.145-2 editorial corrections on G-FRC (section 7.2,7.3,7.4) | 16.1.0 | +| 2019-09 | RAN#85 | RP-192054 | 0180 | | A | CR to TS 37.145-2 – clarify measurement directions test procedures | 16.1.0 | +| 2019-09 | RAN#85 | RP-192054 | 0182 | | A | CR to TS 37.145-2 – Improvements to Annex F | 16.1.0 | +| 2019-09 | RAN#85 | RP-192054 | 0184 | | A | CR to TS 37.145-2 – clean up reverberation chamber spurious emissions procedure | 16.1.0 | +| 2019-09 | RAN#85 | RP-192054 | 0186 | | A | CR to TS 37.145-2 - reverberation chamber in-band TRP procedures | 16.1.0 | +| 2019-09 | RAN#85 | RP-192054 | 0188 | | A | CR to TS 37.145-2 – single polarisation measurement procedure | 16.1.0 | +| 2019-12 | RAN#86 | RP-193014 | 0190 | | B | Introduction of 2010-2025 MHz SUL band into Rel-16 TS 37.145-2 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192991 | 0192 | 1 | A | CR to 37.145-2 on Receiver spurious emission requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-192991 | 0194 | | A | CR to 37.145-2 on Receiver Intermodulation signal offset correction | 16.2.0 | +| 2019-12 | RAN#86 | RP-193045 | 0198 | | A | CR to TS 37.145-2: Clarification of conformance testing for same beams | 16.2.0 | +| 2019-12 | RAN#86 | RP-192991 | 0200 | | A | CR to 37.145-2: OTA ACLR R16 (6.7.3) | 16.2.0 | +| 2019-12 | RAN#86 | RP-192991 | 0202 | | A | CR to TS37.145-2 Corrections on NBB requirement (section 7.5.5.1.2) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193048 | 0204 | | A | CR to TS 37.145-2: Requirement set applicability | 16.2.0 | +| 2019-12 | RAN#86 | RP-193048 | 0208 | | A | Correction to co-existence and co-location spurious emissions applicability range | 16.2.0 | +| 2019-12 | RAN#86 | RP-192991 | 0210 | | A | CR Modulation fallback for total power dynamic range in 37.145-2 clause 6.4.4.4.2.4 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193048 | 0212 | | A | CR to TS 37.145-2 - reverberation chamber in-band TRP procedures | 16.2.0 | +| 2019-12 | RAN#86 | RP-193048 | 0214 | | A | CR to TS 37.145-2: correction of the direction to be tested for the BS demodulation requirements, Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193151 | 0216 | 1 | B | CR to 37.145-2 on variable duplex FDD bands | 16.2.0 | +| 2020-03 | RAN#87 | RP-200381 | 0217 | | B | Introduction of n26 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200382 | 0218 | | B | Introduction of n53 | 16.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88 | RP-200984 | 0220 | | A | CR to TS 37.145-2: Corrections on generation of test configurations | 16.4.0 | +| 2020-06 | RAN#88 | RP-200984 | 0222 | | A | TS 37.145-2: Corrections related to Foffset | 16.4.0 | +| 2020-06 | RAN#88 | RP-200984 | 0224 | | A | CR to TS 37.145-2: Additional information about alignment needed for TRP measurements in Annex F.1 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200984 | 0226 | | A | CR to 37.145-2: Correction on interference level of receiver dynamic range requirement | 16.4.0 | +| 2020-06 | RAN#88 | RP-201005 | 0228 | | A | CR to TS 37.145-2: internal TR references corrections (wrt. TR 37.941 for OTA BS testing), Rel-16 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200984 | 0230 | | A | CR to 37.145-2 Corrections to OTA modulation quality test Rel-16 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200984 | 0232 | | A | CR to TS 37.145-2: Correcting the reference angular step equations (Annex F.2.2) | 16.4.0 | +| 2020-09 | RAN#89 | RP-201512 | 0236 | | A | CR to TS 37.145-2: Correction on procedure for spurious unwanted emissions measurement using orthogonal cut grid | 16.5.0 | +| 2020-09 | RAN#89 | RP-201501 | 0238 | | A | CR to TS 37.145-2: internal TR references corrections (wrt. TR 37.941 for OTA BS testing), Rel-16 | 16.5.0 | +| 2020-12 | RAN#90 | RP-202513 | 0249 | | A | CR to TS 37.145-2: correction of manufacturer | 16.6.0 | +| 2020-12 | RAN#90 | RP-202510 | 0254 | | A | CR to TS 37.145-2: Corrections to conformance requirements including UEM additional requirements, Rel-16 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202510 | 0255 | | F | CR to TS 37.145-2: Corrections to single RAT E-UTRA additional requirements for band 89, Rel-16 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202489 | 0257 | | A | CR to 37.145-2: Correction on NR REFSSENS | 16.6.0 | +| 2020-12 | RAN#90 | RP-202489 | 0259 | | A | CR to 37.145-2: Correction to applicability of additional BC3 requirement (Rel-16) | 16.6.0 | +| 2020-12 | RAN#90 | RP-202510 | 0263 | | A | CR to 37.145-2 on Removal of additional limit for Band 1 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202510 | 0266 | | A | TS 37.145-2: Corrections OTA SEM, OTA Rx intermod and OTA ACS | 16.6.0 | +| 2020-12 | RAN#90 | RP-202510 | 0267 | | A | CR to TS 37.145-2: addition of the OBUE applicability table, Rel-16 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202451 | 0242 | - | B | Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.145-2 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202452 | 0243 | - | B | Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.145-2 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202448 | 0245 | - | B | CR to TS 37.145-2: introduction of NR band n13 | 17.0.0 | +| 2021-03 | RAN#91 | RP-210097 | 0268 | | B | CR for TS 37.145-2 introduction of NR band n24 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210096 | 0270 | 1 | B | CR to 37.145-2 on introducing new SUL band n99 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210111 | 0275 | | A | CR for 37.145-2: Corrections related to Band 24 regulatory updates | 17.1.0 | +| 2021-03 | RAN#91 | RP-210121 | 0282 | | F | CR to TS 37.145-2: Corrections to conformance requirements, Rel-17 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210121 | 0285 | | A | CR to TS 37.145-2 Update CLTA definition, Rel-17 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210118 | 0287 | | A | CR to TS 37.145-2: Introduction of new BS capability set for NR+EUTRA+UTRA, Rel-17 | 17.1.0 | +| 2021-06 | RAN#92 | RP-211076 | 0299 | | A | CR to TS 37.145-2: Regional requirements for band 41 in Japan, Rel-17 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211082 | 0302 | 1 | A | CR to 37.145-2 to modify AAS BS OTA Spurious emissions limits for co-existence with systems operating in other frequency bands in R17 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0303 | | B | CR to TS 37.145-2: Introduction of band n67 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0304 | | B | CR to TS 37.145-2: Introduction of band n85 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211094 | 0307 | | A | TS 37.145-2: Introduction of NR-U co-existence requirements | 17.2.0 | +| 2021-06 | RAN#92 | RP-211090 | 0310 | | A | CR to 37.145-2: In-band blocking for multi-band Base Stations | 17.2.0 | +| 2021-06 | RAN#92 | RP-211091 | 0313 | | A | CR to 37.145-2: Correction to ACLR limit in non-contiguous spectrum (Rel-17) | 17.2.0 | +| 2021-09 | RAN#93 | RP-211909 | 0314 | | B | CR for TS 37.145-2: introduction of channel bandwidths 35MHz and 45MHz | 17.3.0 | +| 2021-09 | RAN#93 | RP-211926 | 0317 | | A | Big CR for TS 37.145-2 Maintenance (Rel-17, CAT A) | 17.3.0 | +| 2021-12 | RAN#94 | RP-212856 | 0320 | | A | Big CR for TS 37.145-2 Maintenance (Rel-17, CAT A) | 17.4.0 | +| 2022-03 | RAN#95 | RP-220349 | 0321 | | B | CR to TS 37.145-2 with 1024QAM introduction | 17.5.0 | +| 2022-03 | RAN#95 | RP-220347 | 0322 | 1 | B | CR to TS 37.145-2: implementation of LTE_upper_700MHz_A band 103 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220357 | 0323 | | B | CR to 37.145-2 - adding band n102 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220338 | 0326 | | A | Big CR for TS 37.145-2 Maintenance (Rel-17, CAT A) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220376 | 0327 | | B | CR to TS 37.145-2: RMR 1900MHz band n101 introduction | 17.5.0 | +| 2022-06 | RAN#96 | RP-221673 | 0328 | | B | CR on introduction of 6GHz licensed band for 37.145-2 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221675 | 0329 | | F | CR to 37.145-2: BS RF conformance requirements for 1024QAM in FR1 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221684 | 0330 | | B | CR to TS 37.145-2: introduction of n100 co-existence requirements, Rel-17 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221652 | 0333 | | A | Big CR for TS 37.145-2 Maintenance (Rel-17, CAT A) | 17.6.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | RP-223315 | 0334 | | B | CR to TS 37.145-2: Introduction of LTE TDD band 54 | 18.0.0 | +| 2022-12 | RAN#98-e | RP-223319 | 0336 | | B | CR to TS37.145-2 the introduction of APT600MHz | 18.0.0 | +| 2023-03 | RAN#99 | RP-230500 | 0339 | | A | CR to TS 37.145-2: The applicability of additional BC3 requirements | 18.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------|--------| +| 2023-03 | RAN#99 | RP-230500 | 0342 | | A | CR to 37.145-2: Operating band unwanted emission requirements | 18.1.0 | +| 2023-03 | RAN#99 | RP-230535 | 0344 | | B | CR to TS 37.145-2: Introduction of NR band n54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230527 | 0347 | 1 | F | CR to TS 37.145-2: LTE TDD band 54 additional spurious clarification | 18.1.0 | +| 2023-06 | RAN#100 | RP-231352 | 0352 | | A | CR to 37.145-2: Clarification on the OBUE limites when narrow carrier adjacent to the sub block edge | 18.2.0 | +| 2023-06 | RAN#100 | RP-231362 | 0353 | | B | CR to TS37.145-2: the introduction of 900 MHz LTE new band | 18.2.0 | +| 2023-09 | RAN#101 | RP-232486 | 0357 | | A | [AASenh_BS_LTE_UTRA-Perf] CR to TR 37.145-2: Corrections on tables for E-UTRA in-channel selectivity test requirement | 18.3.0 | +| 2023-09 | RAN#101 | RP-232504 | 0362 | | A | CR to 37.145-2: Correction to ACLR and CACLR requirement | 18.3.0 | +| 2023-09 | RAN#101 | RP-232505 | 0366 | | A | TS 37.145-2: Corrections | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0367 | | B | CR to TS37.145-2: introduction of NR bands n31 and n72 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0368 | 1 | B | CR to TS 37.145-2 - Introduction of band n109 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233337 | 0371 | | A | [MSR_GSM_UTRA_LTE_NR-Perf] CR to 37.145-2: Power allocation for NC operation | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0372 | | B | CR to 37.145-2 on introduction of Band 106 | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37171/raw.md b/marked/Rel-18/37_series/37171/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7f2082c89cb9be5124dccee0ad05b0b87b7fd176 --- /dev/null +++ b/marked/Rel-18/37_series/37171/raw.md @@ -0,0 +1,1183 @@ + + +# 3GPP TS 37.171 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) performance requirements for Radio Access Technology (RAT) Independent Positioning Enhancements (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association +Bluetooth® is a Trade Mark of the Bluetooth SIG registered for the benefit of its members + + + +# Contents + +| | | +|--------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, abbreviations and test tolerances..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 3.3 Test tolerances..... | 8 | +| 4 General..... | 8 | +| 4.1 Introduction ..... | 8 | +| 4.2 MBS Measurements..... | 8 | +| 4.2.1 General ..... | 8 | +| 4.2.2 MBS measurement parameters..... | 9 | +| 4.2.3 MBS Measurement time..... | 9 | +| 4.2.4 RRC states for MBS measurements ..... | 10 | +| 4.2.5 MBS Measurement Error Definitions ..... | 10 | +| 4.3.2 WLAN Access Point Measurements..... | 10 | +| 4.3.2.1 E-UTRAN FDD-WLAN Access Point Measurements ..... | 10 | +| 4.3.2.1.1 Introduction ..... | 10 | +| 4.3.2.1.2 Measurement Requirements..... | 11 | +| 4.3.2.1.3 Measurement Reporting Delay..... | 11 | +| 4.3.2.2 E-UTRAN TDD-WLAN Access Point Measurements..... | 11 | +| 4.3.2.2.1 Introduction ..... | 11 | +| 4.3.2.2.2 Measurement Requirements..... | 11 | +| 4.3.2.2.3 Measurement Reporting Delay..... | 12 | +| 4.3.2.3 NR WLAN Access Point Measurements..... | 12 | +| 4.3.2.3.1 Introduction ..... | 12 | +| 4.3.2.3.2 Measurement Requirements..... | 12 | +| 4.3.2.3.3 Measurement Reporting Delay..... | 12 | +| 4.4 Bluetooth Measurements..... | 12 | +| 4.4.1 General ..... | 12 | +| 4.4.2.1 Introduction..... | 12 | +| 4.4.2.2 Measurement Requirements ..... | 12 | +| 4.4.2.3 Measurement Reporting Delay ..... | 13 | +| 4.4.2.4 NR Measurement Requirements..... | 13 | +| 4.4.2.5 NR Measurement Reporting Delay..... | 13 | +| 5 MBS minimum performance requirements..... | 13 | +| 5.1 General ..... | 13 | +| 5.2 Sensitivity..... | 13 | +| 5.3 Nominal Accuracy..... | 13 | +| 5.4 Dynamic Range..... | 14 | +| 5.5 Multipath..... | 14 | +| 6 Bluetooth performance requirements..... | 15 | +| 6.1 Introduction ..... | 15 | +| 6.1.1 Bluetooth RSSI Measurement ..... | 15 | +| 6.1.1.1 Measurement Accuracy ..... | 15 | +| 7 WLAN Access Point Identification minimum performance requirements..... | 15 | +| 7.1 General ..... | 15 | +| 7.2 WLAN Access Point Identification under Sensitivity conditions..... | 15 | +| 7.3 WLAN Access Point Identification under Nominal conditions..... | 15 | +| 7.4 WLAN Access Point Identification under Dynamic Range conditions..... | 16 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------|-----------| +| Annex A (normative): | Test Case Requirements ..... | 17 | +| A.1 | Purpose of annex ..... | 17 | +| A.2 | Requirement classification for statistical testing ..... | 17 | +| A.3 | UE Measurement Procedures ..... | 17 | +| A.3.1 | MBS Measurement reporting delay test case ..... | 17 | +| A.3.1.1 | Test Purpose and Environment ..... | 17 | +| A.3.1.2 | Test Requirements ..... | 18 | +| A.3.2 | WLAN Access Point Identification and Reporting Delay ..... | 18 | +| A.3.2.1 | Void ..... | 19 | +| A.3.2.2 | LTE-FDD: WLAN AP Identification and reporting delay under nominal conditions test ..... | 19 | +| A.3.2.2.1 | Test purpose and Environment ..... | 19 | +| A.3.2.2.2 | Test Requirements ..... | 20 | +| A.3.2.3 | LTE-TDD: WLAN AP Identification and reporting delay under nominal conditions test ..... | 21 | +| A.3.2.3.1 | Test purpose and Environment ..... | 21 | +| A.3.2.3.2 | Test Requirements ..... | 22 | +| A.3.2.4 | LTE-FDD: WLAN AP Identification and reporting delay under dynamic range conditions test ..... | 23 | +| A.3.2.4.1 | Test purpose and Environment ..... | 23 | +| A.3.2.4.2 | Test Requirements ..... | 25 | +| A.3.2.5 | LTE-TDD: WLAN AP Identification and reporting delay under dynamic range conditions test ..... | 25 | +| A.3.2.5.1 | Test purpose and Environment ..... | 25 | +| A.3.2.5.2 | Test Requirements ..... | 27 | +| A.3.3 | Bluetooth Measurement Requirements ..... | 27 | +| A.3.3.1 | E-UTRAN FDD Bluetooth identification ..... | 27 | +| A.3.3.1.1 | Test Purpose and Environment ..... | 27 | +| A.3.3.1.2 | Test Requirements ..... | 28 | +| A.3.3.2 | E-UTRAN TDD Bluetooth identification ..... | 29 | +| A.3.3.2.1 | Test Purpose and Environment ..... | 29 | +| A.3.3.2.2 | Test Requirements ..... | 30 | +| A.4 | Measurement Performance Requirements ..... | 31 | +| A.4.1 | General ..... | 31 | +| A.4.2 | MBS Code Phase Measurement Accuracy Requirements in AWGN ..... | 31 | +| A.4.2.1 | Test Purpose and Environment ..... | 31 | +| A.4.2.2 | Test Requirements ..... | 32 | +| A.4.3 | MBS Code Phase Measurement Accuracy Requirements in Multipath ..... | 32 | +| A.4.3.1 | Test Purpose and Environment ..... | 32 | +| A.4.3.2 | Test Requirements ..... | 33 | +| Annex B (normative): | Assistance data required for testing (Release 14 and beyond) ..... | 34 | +| B.1 | Introduction ..... | 34 | +| B.2 | MBS Assistance Data ..... | 34 | +| Annex C (informative): | Change history ..... | 35 | + +# Foreword + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document +- might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document establishes the minimum performance requirements for RAT-Independent Positioning Enhancements for FDD and TDD mode of UTRA, FDD and TDD mode of E-UTRA, and NR for the User Equipment (UE). + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 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". +- [3] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)". +- [4] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Special conformance testing functions for User Equipment (UE)". +- [5] 3GPP TS 36.942: Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Frequency (RF) system scenarios". +- [6] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification". +- [7] ATIS-0500027: "Recommendations for Establishing Wide Scale Indoor Location Performance", May 2015. +- [8] 3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions ". +- [9] 3GPP TS 37.571-1: " User Equipment (UE) conformance specification for UE positioning; Part 1: Conformance test specification ". +- [10] 3GPP TS 36.521-1: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Conformance testing". +- [11] Void. +- [12] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)". +- [13] Bluetooth Special Interest Group: "Bluetooth Core Specification version 4.2", December 2014. +- [14] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification". +- [15] IEEE Standard 802.11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. + +[16] 3GPP TS 38.509: "5GS; Special conformance testing functions for User Equipment (UE)". + +# --- 3 Definitions, abbreviations and test tolerances + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|---------------------------------------| +| AWGN | Additive White Gaussian Noise | +| EPA | Extended Pedestrian A | +| E-UTRA | Evolved UMTS Terrestrial Radio Access | +| FDD | Frequency Division Duplex | +| LMF | Location Management Function | +| LPP | LTE Positioning Protocol | +| MBS | Metropolitan Beacon System | +| NR | New Radio Access | +| RRC | Radio Resource Control | +| RSSI | Received Signal Strength Indicator | +| SS | System Simulator | +| TDD | Time Division Duplex | +| UE | User Equipment | +| UTRA | UMTS Terrestrial Radio Access | +| WLAN | Wireless Local Area Network | + +## 3.3 Test tolerances + +The requirements given in the present document make no allowance for measurement uncertainty. The test specification 3GPP TS 37.571 -1 [9] will define 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 ETSI TR 102 273-1-2 [2], subclause 6.5. + +# --- 4 General + +## 4.1 Introduction + +The present document defines the minimum performance requirements for UEs that support RAT Independent positioning technologies. + +## 4.2 MBS Measurements + +### 4.2.1 General + +Clause 4.2 describes the measurements performed by the UE for MBS positioning. + +### 4.2.2 MBS measurement parameters + +The measurement parameters are the MBS code phase measurements contained in the *TBS-MeasurementInformation* IE provided in the LPP message of type PROVIDE LOCATION INFORMATION [3] by NR UE, the *TBS-MeasurementInformation* IE provided in LPP message of type PROVIDE LOCATION INFORMATION [3] by LTE UE, and the *UE Positioning AddPos measured results* IE in the MEASUREMENT REPORT message by UTRA UE [6]. + +### 4.2.3 MBS Measurement time + +For NR, MBS measurement time is defined as the time starting from the moment that the UE has received the LPP [3] message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. For tests that involve sending MBS assistance data to the UE, the assistance data is sent prior to the REQUEST LOCATION INFORMATION message. The response times specified for all test cases are based on new measurements unless otherwise stated, i.e. the UE shall not reuse any information on measurements 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 38.509 [16] clause 5.6 for the purpose of deleting this information. + +For LTE, MBS measurement time is defined as the time starting from the moment that the UE has received the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. For tests that involve sending MBS assistance data to the UE, the assistance data is sent prior to the REQUEST LOCATION INFORMATION message. The response times specified for all test cases are based on new measurements unless otherwise stated, i.e. the UE shall not reuse any information on measurements 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 36.509 [4] clause 6.9 for the purpose of deleting this information. + +For UTRA, MBS measurement 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 MBS measured results, and ending when the UE starts sending the measurement report containing the measured result on the Uu interface. The response times specified for all test cases are based on new measurements unless otherwise stated, i.e. the UE shall not reuse any information on measurements 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 [8] clause 5.4 for the purpose of deleting this information. + +The measurements for n MBS beacons, enabled across the slots of an MBS transmission period [7], shall be available at the UE by $T_{\text{MBS\_meas}}$ , where $T_{\text{MBS\_meas}}$ can be expressed as: + +$$T_{\text{MBS\_meas}} = \tau + 10 \times \text{ceil}(n/10) \times T_{\text{MBS\_TP}} + T_{\text{Proc}} \quad \text{ms}$$ + +where + +$T_{\text{MBS\_meas}}$ is the total time for detecting and measuring n beacons + +$\tau$ is the elapsed time from the trigger of the measurement to the start of the first MBS transmission period + +$T_{\text{MBS\_TP}}$ is the MBS transmission period (1 second) + +$T_{\text{Proc}}$ is the processing time, an upper-bound for which can be given as $10 \times \text{ceil}(n/10) \times T_{\text{MBS\_slot}}$ where $T_{\text{MBS\_slot}}$ is the duration of a MBS slot (100 ms) with continuous MBS transmissions + +![Figure 4.2.3-1: MBS Measurement Time. A timeline diagram showing the sequence of events for MBS measurement. It starts with 'The last location request received by higher layers' (blue bar) and 'The last location request received by MBS physical layer' (red bar). A time interval τ is shown between these two events. The timeline then shows a '1 sec boundary' followed by 'Slot 1' containing 'Beacon 1' and 'Slot 2' containing 'Beacon 2'. Each slot has a duration of 100 ms. The interval between the start of Slot 1 and Slot 2 is labeled T_MBS_TP (1 sec). The interval between the start of Slot 1 and the start of Slot n is labeled n * T_MBS_TP. The total duration of the measurement period is labeled T_MBS_meas. A processing time T_Proc is indicated at the end of the timeline.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 4.2.3-1: MBS Measurement Time. A timeline diagram showing the sequence of events for MBS measurement. It starts with 'The last location request received by higher layers' (blue bar) and 'The last location request received by MBS physical layer' (red bar). A time interval τ is shown between these two events. The timeline then shows a '1 sec boundary' followed by 'Slot 1' containing 'Beacon 1' and 'Slot 2' containing 'Beacon 2'. Each slot has a duration of 100 ms. The interval between the start of Slot 1 and Slot 2 is labeled T\_MBS\_TP (1 sec). The interval between the start of Slot 1 and the start of Slot n is labeled n \* T\_MBS\_TP. The total duration of the measurement period is labeled T\_MBS\_meas. A processing time T\_Proc is indicated at the end of the timeline. + +Figure 4.2.3-1: MBS Measurement Time + +For this requirement, the assumption is that there is zero frequency offset for the beacons and the UEs have a minimum of 13 parallel correlators. + +The test case for MBS Measurement time requirements are specified in clause A.3.1. + +### 4.2.4 RRC states for MBS measurements + +For NR, the minimum MBS performance requirements specified in clause 5 apply for RRC\_CONNECTED state. + +For LTE, the minimum MBS performance requirements specified in clause 5 apply for RRC\_CONNECTED state. + +For UTRA, the minimum MBS performance requirements specified in clause 5 apply for different RRC states that include Cell\_DCH and Cell\_FACH. + +### 4.2.5 MBS Measurement Error Definitions + +The code phase measurement error is defined as the difference between the actual code phase for a given MBS beacon, and the estimated code phase for that beacon, as reported in the *TBS-MeasurementInformation* IE provided in the LPP message of type PROVIDE LOCATION INFORMATION by NR UE [3], the *TBS-MeasurementInformation* IE provided in the LPP message of type PROVIDE LOCATION INFORMATION by LTE UE [3], and the *UE Positioning AddPos measured results* IE in the MEASUREMENT REPORT message by UTRA UE [6]. This difference has to then be adjusted for the measurement bias introduced by the UE clock to provide the final code phase measurement error. + +## 4.3 WLAN Measurements + +### 4.3.1 General + +Clause 4.3 defines the measurement requirements for the measurements performed by the UE for WLAN based positioning. + +### 4.3.2 WLAN Access Point Measurements + +Editor's note: In the WLAN requirements for NR, the NR clauses are separate from LTE, but it is FFS whether separate clauses are needed for SA NR and non-SA NR. + +#### 4.3.2.1 E-UTRAN FDD-WLAN Access Point Measurements + +##### 4.3.2.1.1 Introduction + +The requirements defined in section 4.3.2.1 shall apply provided the E-UTRA FDD UE has received *WLAN-RequestLocationInformation* message from E-SMLC via LPP requesting the UE to report WLAN measurement for one or more WLAN Access Points [12]. + +##### 4.3.2.1.2 Measurement Requirements + +The measurement delay reporting requirements for WLAN are defined in section 4.3.2.1.3. The WLAN Access Point identification minimum performance requirements are defined in clause 7. + +##### 4.3.2.1.3 Measurement Reporting Delay + +For LTE, WLAN measurement time is defined as the time starting from the moment that the UE has received the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. The response times specified for all test cases are based on new measurements unless otherwise stated, i.e. the UE shall not re use any information on measurements 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 36.509 [4] clause 6.9 for the purpose of deleting this information. No WLAN assistance data is provided to the UE. + +The signals from the WLAN APs shall be available at the UE for the duration of the measurement time. Each WLAN AP transmits a beacon signal with a beacon interval smaller or equal to 102.4 ms. The beacon frames from different access points shall be transmitted in different time slots or non-overlapping frequency channels. The beacon frames have variable time duration of ~1ms. + +The WLAN Measurement Reporting Delay is given as: + +$$T_{\text{WLAN\_meas}} = \tau + 20 \text{ sec}$$ + +where + +$T_{\text{WLAN\_meas}}$ is the total time for detecting and measuring the WLAN Access Points + +$\tau$ is the elapsed time from the trigger of the measurement to the start of the first WLAN transmission period and is shown in Figure 4.3.2.1.3-1. + +![Figure 4.3.2.1.3-1: WLAN Measurement Time diagram. The diagram shows a timeline starting with two triggers: 'The last location request received by higher layers' (blue bar) and 'The last location request received by WLAN physical layer' (red bar). The time interval from the red bar to the start of 'Time Slot 1' is labeled as tau. 'Time Slot 1' contains 'Beacon 1, Chan.A' and 'Beacon 1, Chan.B'. 'Time Slot 2' contains 'Beacon 2, Chan.A' and 'Beacon 2, Chan.B'. A horizontal double-headed arrow between the start of Time Slot 1 and the start of Time Slot 2 is labeled '20 s'. A long horizontal double-headed arrow at the bottom, spanning from the start of Time Slot 1 to the end of the shown period, is labeled 'T_WLAN_meas'.](0019f09403376d6444ee323591fa2e98_img.jpg) + +Figure 4.3.2.1.3-1: WLAN Measurement Time diagram. The diagram shows a timeline starting with two triggers: 'The last location request received by higher layers' (blue bar) and 'The last location request received by WLAN physical layer' (red bar). The time interval from the red bar to the start of 'Time Slot 1' is labeled as tau. 'Time Slot 1' contains 'Beacon 1, Chan.A' and 'Beacon 1, Chan.B'. 'Time Slot 2' contains 'Beacon 2, Chan.A' and 'Beacon 2, Chan.B'. A horizontal double-headed arrow between the start of Time Slot 1 and the start of Time Slot 2 is labeled '20 s'. A long horizontal double-headed arrow at the bottom, spanning from the start of Time Slot 1 to the end of the shown period, is labeled 'T\_WLAN\_meas'. + +Figure 4.3.2.1.3-1: WLAN Measurement Time + +#### 4.3.2.2 E-UTRAN TDD-WLAN Access Point Measurements + +##### 4.3.2.2.1 Introduction + +The requirements defined in section 4.3.2.2 shall apply provided the E-UTRA TDD UE has received *WLAN-RequestLocationInformation* message from E-SMLC via LPP requesting the UE to report WLAN measurement for one or more WLAN Access Points [12]. + +##### 4.3.2.2.2 Measurement Requirements + +The measurement reporting delay requirements for WLAN are defined in section 4.3.2.2.3. The WLAN Access Point identification minimum performance requirements are defined in clause 7. + +##### 4.3.2.2.3 Measurement Reporting Delay + +Same as 4.3.2.1.3. + +#### 4.3.2.3 NR WLAN Access Point Measurements + +##### 4.3.2.3.1 Introduction + +The requirements defined in section 4.3.2.3 shall apply provided the NR UE has received *WLAN-RequestLocationInformation* message from LMF via LPP requesting the UE to report WLAN measurement for one or more WLAN Access Points [12]. + +##### 4.3.2.3.2 Measurement Requirements + +The measurement reporting delay requirements for WLAN are defined in section 4.3.2.3.3. The WLAN Access Point identification minimum performance requirements are defined in clause 7. + +##### 4.3.2.3.3 Measurement Reporting Delay + +Same as 4.3.2.1.3. + +## 4.4 Bluetooth Measurements + +### 4.4.1 General + +Clause 4.4 defines the measurement requirements for the measurements performed by the UE for Bluetooth based positioning. + +### 4.4.2 Bluetooth Access Point Measurements + +#### 4.4.2.1 Introduction + +The requirements defined in sections 4.4.2 for E-UTRA shall apply provided the UE has received *BT-RequestLocationInformation* message from E-SMLC via LPP requesting the UE to report Bluetooth measurements for one or more Bluetooth Access Points [12]. + +The requirements defined in sections 4.4.2 for NR shall apply provided the UE has received *BT-RequestLocationInformation* message from LMF via LPP requesting the UE to report Bluetooth measurements for one or more Bluetooth Access Points [12]. + +Editor's note: In the Bluetooth access point measurement requirements for NR, the NR clauses are separate from LTE, but it is FFS whether separate clauses are needed for SA NR and non-SA NR. + +#### 4.4.2.2 Measurement Requirements + +For E-UTRA, in the RRC\_CONNECTED state the measurement period for Bluetooth Access Point identification shall be $T_{\text{BT\_meas}}$ . The value of $T_{\text{BT\_meas}}$ is 10.24 s, and can be extended to 40.96 s if extended inquiry is allowed, provided that the following conditions are met [13]: + +- At least one Bluetooth beacon signal is transmitted on one of the Bluetooth advertising channels with a broadcast interval of 100 ms. + +$T_{\text{BT\_meas}}$ defined in this section shall apply when no DRX cycle is configured or when any DRX cycle defined in [14] is configured. + +The UE physical layer shall be capable of reporting Bluetooth Access Point(s) measurements to higher layers within the measurement period of $T_{\text{BT\_meas}}$ . + +The Bluetooth RSSI measurement accuracy for all measured access points shall be fulfilled according to the accuracy as specified in the clause 6. + +#### 4.4.2.3 Measurement Reporting Delay + +For E-UTRA, this requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is: $2 \times \text{TTI}_{\text{DCCH}}$ . This measurement reporting delay excludes any delay caused by no UL resources for UE to send the measurement report. + +#### 4.4.2.4 NR Measurement Requirements + +Same as 4.4.2.2. + +#### 4.4.2.5 NR Measurement Reporting Delay + +Same as 4.4.2.3. + +# 5 MBS minimum performance requirements + +## 5.1 General + +The minimum performance requirements specified in clause 5 apply for UEs that support MBS. This section applies to requirements for NR, UTRA, and E-UTRA. + +The code phase accuracy requirements in this clause are statistical in nature and pertain to the 90th percentile of the distribution. + +The measurement time for each requirement shall be $T_{\text{MBS\_meas}}$ as described in clause 4.2.3. This clause does not include nor consider delays occurring in the various signalling interfaces of the network. + +## 5.2 Sensitivity + +A Sensitivity requirement is essential for verifying the performance of MBS receiver in weak signal conditions. In order to test the most stringent signal levels for the beacons the Sensitivity test case is performed in AWGN channel. This test case verifies the UE MBS performance at the lowest expected signal levels. + +In MBS deployments, target sensitivity levels of -130 dBm (at the UE antenna connector, across the signal bandwidth) are used. + +The minimum requirements for Sensitivity are shown in Table 5.2-1. + +**Table 5.2-1: Requirements for Sensitivity** + +| MBS Configuration | Signal Strength (dBm) | Code phase measurement accuracy (ms) | +|-------------------|-----------------------|--------------------------------------------| +| TB1 (2 MHz) [7] | -130 | $1.66 \times 10^{-4}$ | +| TB1 (5 MHz) [7] | -130 | $6.64 \times 10^{-5}$ (Release 14 onwards) | + +The test case requirements for Sensitivity measurement accuracy can be found in clause A.4.2. + +## 5.3 Nominal Accuracy + +The Nominal Accuracy requirement verifies the UE MBS performance under ideal conditions. The primary aim of the test is to ensure good accuracy when the MBS signal conditions allow it. + +In this requirement AWGN channel model is used and the signal level is above the noise floor. + +The minimum requirements for Nominal are shown in Table 5.3-1. + +**Table 5.3-1: Requirements for Nominal Accuracy** + +| MBS Configuration | Signal Strength (dBm) | Code phase measurement accuracy (ms) | +|-------------------|-----------------------|-------------------------------------------| +| TB1 (2 MHz) [7] | -30 | $5.0 \times 10^{-5}$ | +| TB2 (5 MHz) [7] | -30 | $2.0 \times 10^{-5}$ (Release 14 onwards) | + +The test case requirements for Nominal measurement accuracy can be found in clause A.4.2. + +## 5.4 Dynamic Range + +The Dynamic Range requirement is targeted at testing the performance of the MBS receiver under time varying signal conditions. This test case is important for a system such as MBS where the time slotting of beacons is used. + +The maximum signal level of a MBS beacon is expected to be -30 dBm (at the UE antenna connector). This can be shown theoretically by assuming a TX power of +40 dBm and a minimum coupling loss between the transmitter and the UE of 70 dB [5]. + +For this requirement, the power level of the MBS beacons shall be alternated between the strongest and the weakest expected levels across consecutive slots in the MBS transmission period. + +The minimum requirements for Dynamic Range are shown in Table 5.4-1. + +**Table 5.4-1: Requirements for Dynamic Range** + +| MBS Configuration | Signal Strength (dBm) | Code phase measurement accuracy (ms) | +|-------------------|-----------------------|--------------------------------------------| +| TB1 (2 MHz) [7] | -30 | $5.0 \times 10^{-5}$ | +| | -130 | $1.66 \times 10^{-4}$ | +| TB2 (5 MHz) [7] | -30 | $2.0 \times 10^{-5}$ (Release 14 onwards) | +| | -130 | $6.64 \times 10^{-5}$ (Release 14 onwards) | + +The test case requirements for Dynamic Range measurement accuracy can be found in clause A.4.2. + +## 5.5 Multipath + +The purpose of the test case is to verify the receiver's tolerance to multipath. + +The pedestrian channel model used in TS 37.571-1 [9], captured in Annex B of TS 36.521-1 [10] is used for assessing the MBS performance under the multipath scenario, specifically the Extended Pedestrian A (EPA) with a maximum Doppler frequency of 5 Hz (EPA 5Hz). + +The minimum requirements for the Multipath scenario are shown in Table 5.5-1. + +**Table 5.5-1: Requirements for Multipath scenario** + +| MBS Configuration | Direct Path Signal Strength (dBm) | Code phase measurement accuracy (ms) | +|-------------------|-----------------------------------|--------------------------------------| +| TB1 (2 MHz) [7] | -30 | $1.66 \times 10^{-4}$ | + +The test case requirements for Multipath measurement accuracy can be found in clause A.4.3. + +# 6 Bluetooth performance requirements + +## 6.1 Introduction + +The requirements in this clause are valid for terminals capable of Bluetooth. + +### 6.1.1 Bluetooth RSSI Measurement + +#### 6.1.1.1 Measurement Accuracy + +The Bluetooth RSSI metric is an absolute receiver signal strength value in dBm. The measured Bluetooth RSSI shall be accurate within $\pm 6$ dB as defined in [13]. + +The reporting range of Bluetooth RSSI is defined in section 6.5.7.2 [12]. + +# 7 WLAN Access Point Identification minimum performance requirements + +## 7.1 General + +The minimum performance requirements specified in clause 7 apply for UEs that support WLAN positioning. This section applies to requirements for E-UTRA and NR. + +The measurement requirements in this clause are statistical in nature and pertain to the 90th percentile of the distribution. + +The measurement time for each requirement shall be $T_{\text{WLAN\_meas}}$ as described in clause 4.3.2.1.2 for E-UTRA FDD, clause 4.3.2.2.3 for E-UTRA TDD, and TBD for NR. These requirements do not include nor consider delays occurring in the various signalling interfaces of the network. + +## 7.2 WLAN Access Point Identification under Sensitivity conditions + +The sensitivity conditions for a WLAN receiver are defined by IEEE in [15]. + +The UE shall be able to identify at least 6 WLAN Access Points if the WLAN beacons are received at the sensitivity power level. In order to test the most stringent signal levels for the beacons the Sensitivity test case is performed in AWGN channel. This test case verifies the UE capability to identify and report WLAN AP at the lowest expected signal levels but it does not evaluate measurement accuracy. + +**Table 7.2-1: Requirements for WLAN Access Point Identification under Sensitivity conditions** + +| Number of WLAN APs | Signal Strength (dBm) | % of reported Access Points | +|--------------------|-----------------------|-----------------------------| +| 6 | See [15] | 90 | + +## 7.3 WLAN Access Point Identification under Nominal conditions + +The WLAN Access Point identification under nominal conditions verifies the UE capability to identify and report WLAN APs when the WLAN signal conditions are ideal. + +In this requirement AWGN channel model is used and the signal level is above the noise floor. + +The minimum requirements for Nominal are shown in Table 7.3-1. + +**Table 7.3-1: Requirements for WLAN Access Point Identification under Nominal conditions** + +| Number of WLAN APs | Signal Strength (dBm) | % of reported Access Points | +|--------------------|-----------------------|-----------------------------| +| 6 | -60 | 90 | + +## 7.4 WLAN Access Point Identification under Dynamic Range conditions + +The WLAN Access Point identification under dynamic range conditions verifies the UE capability to identify and report WLAN APs when the received power difference between WLAN APs is large. The power difference between APs follows the adjacent channel rejection criteria defined by IEEE in [15]. + +The UE shall be able to identify at least 3 WLAN AP located in 3 adjacent channels where the separation between channels is $\geq 20$ MHz and the middle channel is received with high power and the side channels are received with low power. + +**Table 7.4-1: Requirements for WLAN Access Point Identification under Dynamic Range conditions** + +| Number of WLAN APs | Signal Strength (dBm) | % of reported Access Points | +|--------------------|-----------------------|-----------------------------| +| 3 | See [15] | 100 | + +# --- Annex A (normative): Test Case Requirements --- + +## A.1 Purpose of annex + +This Annex specifies test specific parameters for some of the functional requirements in clause 5. The tests provide additional information to how the requirements should be interpreted for the purpose of conformance testing. The tests in this Annex are described such that one functional requirement may be tested in one or several tests and one test may verify several requirements. Some requirements may lack a test. + +The conformance tests are specified in clauses A.3 and A.4. Statistical interpretation of the requirements is described in clause A.2. + +Editor's Note: Based on the E-UTRA test cases specified in A.3.2 and A.3.3, additional WLAN and Bluetooth test parameters for EN-DC and NR SA operations shall be defined separately. The LTE and NR cell specific parameters for EN-DC and NR SA tests are FFS and shall be aligned with the NR requirements. + +## --- 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 A outlines the tests in more detail and lists the test parameters needed. The test will result in an outcome of a test variable value for the device under test (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. + +The statistical nature depends on the type of requirement. Some have large statistical variations, while others are not statistical in nature at all. When testing a parameter with a statistical nature, a confidence level is set. This establishes the probability that a DUT passing the test actually meets the requirements and determines how many times a test has to be repeated and what the pass and fail criteria are. Those aspects are not covered by TS 37.171. The details of the tests on how many times to run it and how to establish confidence in the tests are described in TS 37.571-1 [9]. This Annex establishes the variable to be used in the test and whether it can be viewed as statistical in nature or not. + +## --- A.3 UE Measurement Procedures + +### A.3.1 MBS Measurement reporting delay test case + +#### A.3.1.1 Test Purpose and Environment + +The purpose of the test is to verify that the MBS measurements meet the measurement time requirements specified in clause 4.2.3 in an environment with fading propagation conditions (EPA 5 Hz). This test can be used for NR, UTRA, and E-UTRA testing. + +In this test case there is one beacon transmitted in one beacon slots in the MBS beacon transmission period (see Figure 4.2.3-1). The position of the beacon in the beacon transmission period is static for the duration of the test. In other slots there are no simulated beacons. The beacon has centre frequency of 925.977 MHz or set using the network assistance data in Release 14. The beacon has transmitted signal strength of -30 dBm. The beacon is transmitted with code phase (delay) of $1.6678 \times 10^{-4}$ ms, corresponding to 50 m. + +The UE shall perform and report the MBS measurements for the beacon within 12000 ms, starting from the receipt of the location request. + +NOTE: The MBS measurement time in the test is derived from the following expression: + +$$T_{\text{MBS\_meas}} = \tau + 10 \times \text{ceil}(n/10) \times T_{\text{MBS\_TP}} + T_{\text{Proc}} \text{ ms, where } n=1, \tau \text{ is one second, } T_{\text{MBS\_TP}} \text{ is one second and } T_{\text{Proc}} \text{ is one second.}$$ + +The beacon is of type TB1 (2 MHz) specified in clause 9 of the MBS ICD [7] and the data transmitted is in Type 2 packets specified in clause 9.6.3 of the MBS ICD [7] with the following data fields: The MBS Transmitter ID and the Slot Index shall be set to the MBS slot number; All other beacon payload data shall be populated with zeros [7]. + +The beacon shall use a PN code chosen from the PN code list for TB1 [7]. + +If the UE supports MBS assistance data, the UE will receive the MBS assistance data for each beacon via LPP, according to Annex A. + +**Table A.3.1.1-1: General test parameters for measurement reporting delay** + +| Parameter | Unit | Value | Comment | +|---------------------------------------|---------|--------------------------------------|------------------------------------------------------------------------| +| Centre Frequency | MHz | 925.977 | | +| RF Channel | N/A | EPA 5 Hz | | +| MBS Beacon Configuration | N/A | TB1 (2 MHz) | | +| MBS Data Packet Type | N/A | Type 2 | | +| Beacon PN Code | Integer | Chosen from the PN code list for TB1 | | +| Beacon transmitted Code Phase (delay) | ms | $1.6678 \times 10^{-4}$ | Corresponds to 50 m. Constant per beacon for the duration of the test. | +| Beacon Signal Strength | dBm | -30 | | + +**Table A.3.1.1-2: MBS Beacon Payload fields for measurement reporting delay** + +| Parameter | Unit | Value | Comment | +|------------------|---------|----------------------|---------| +| TxID | Integer | Equal to Slot number | | +| Slot Index | Integer | Equal to Slot number | | +| All other fields | N/A | 0 | | + +#### A.3.1.2 Test Requirements + +The MBS measurement reporting delay shall fulfil the requirements in clause 4.2.3. + +### A.3.2 WLAN Access Point Identification and Reporting Delay + +Editor's Note: Based on the E-UTRA test cases specified in this section, additional WLAN test parameters for EN-DC and NR SA operations shall be defined separately. The LTE and NR cell specific parameters for EN-DC and NR SA tests are FFS and shall be aligned with the NR requirements. + +#### A.3.2.1 Void + +#### A.3.2.2 LTE-FDD: WLAN AP Identification and reporting delay under nominal conditions test + +##### A.3.2.2.1 Test purpose and Environment + +The purpose of this test is to verify the requirements in Clause 7.3 for WLAN AP measurements. The UE shall send *wlan-MeasurementInformation* IE including WLAN measurements for each AP indicating at least *wlan-AP-Identifier* (BSSID) and *rssi* (if reporting of RSSI is supported by the UE as indicated by the UE in the LPP PROVIDE CAPABILITIES message). + +In this test, there are cell1 (E-UTRAN FDD) and 6 WLAN APs transmitting beacon signals at least every 102.4 ms. There is an active LTE connection between the SS and the UE and the measurements are performed in RRC\_CONNECTED state. The beacon signals from different APs shall be received at different time slots or in non-overlapping frequency channels. Non-overlapping frequency channels shall be at least 25 MHz apart in the WLAN 2.4 GHz band and at least 20 MHz apart in the WLAN 5 GHz band. The APs are transmitting in 3 non-overlapping frequency channels in the same WLAN Frequency Band. There are 2 APs in every channel. The test consists of two successive time periods, with duration of T1 and T2, respectively. *WLAN-RequestLocationInformation* message shall be provided to the UE during T1. WLAN Access Points only transmit signal during T2. + +**Table A.3.2.2.1-1: General WLAN AP test parameters +for WLAN AP Identification and reporting delay under nominal conditions test** + +| Parameter | Unit | Value | Comment | +|-------------------------|------|-------|---------------------------------------------------------| +| Number of Access Points | N/A | 6 | AP1-AP6 | +| Time Slot 1 | ms | 1 | AP1, AP2 | +| Time Slot 2 | ms | 1 | AP3, AP4 | +| Time Slot 3 | ms | 1 | AP5 | +| Time Slot 4 | ms | 1 | AP6 | +| T1 | s | 5 | During this time the WLAN signal is not transmitted | +| T2 | s | 25 | UE shall report WLAN measurement information within 20s | + +**Table A.3.2.2.1-2: E-UTRAN TDD Cell specific and WLAN AP specific test parameters for WLAN AP Identification and reporting delay under nominal conditions test** + +| Parameter | Unit | Cell 1 | | AP 1, 4 | | AP 2, 5 | | AP 3, 6 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------|------|------------------------------------------------------|-----|------------------------------------------------------|-----|------------------------------------------------------|-----| +| | | T1 | T2 | T1 | T2 | T1 | T2 | T1 | T2 | +| E-UTRA RF Channel Number | | 1 | | N/A | | N/A | | N/A | | +| WLAN Channel Number | | N/A | | 1 | | 2 | | 3 | | +| BW channel | | 10MHz | | N/A | | N/A | | N/A | | +| WLAN Channel spacing | | N/A | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | +| PDSCH parameters:
DL Reference Measurement Channel | | R.0 FDD | | N/A | | N/A | | N/A | | +| PCFICH/PDCCH/PHICH parameters:
DL Reference Measurement Channel | | R.6 FDD | | N/A | | N/A | | N/A | | +| OCNG Patterns | | OP.1 FDD | | N/A | | N/A | | N/A | | +| PBCH_RA | dB | 0 | | N/A | | N/A | | N/A | | +| PBCH_RB | dB | | | | | | | | | +| PSS_RA | dB | | | | | | | | | +| SSS_RA | dB | | | | | | | | | +| PCFICH_RB | dB | | | | | | | | | +| PHICH_RA | dB | | | | | | | | | +| PHICH_RB | dB | | | | | | | | | +| PDCCH_RA | dB | | | | | | | | | +| PDCCH_RB | dB | | | | | | | | | +| PDSCH_RA | dB | | | | | | | | | +| PDSCH_RB | dB | | | | | | | | | +| OCNG_RA Note 1 | dB | | | | | | | | | +| OCNG_RB Note 1 | dB | | | | | | | | | +| N oc1 Note 2 | dBm/15 KHz | -98 | | N/A | | N/A | | N/A | | +| N oc2 Note 3 | dBm/20 MHz | N/A | | -75 | | -75 | | -75 | | +| $\hat{E}_s/N_{oc1}$ | dB | 3 | 3 | N/A | | N/A | | N/A | | +| $\hat{E}_s/I_{ot}$ Note 4 | dB | 3 | 3 | | | | | | | +| RSRP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | | +| SCH_RP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | | +| I o Note 3 | dBm/Ch BW | - | - | | | | | | | +| | | 65.5 | 65.5 | | | | | | | +| WLAN Received Power Level | dBm | N/A | N/A | - inf | -60 | - inf | -60 | - inf | -60 | +| WLAN SNR Note 4 | dB | N/A | | 15 | | 15 | | 15 | | +| Propagation Condition | | AWGN | | | | | | | | +| Antenna Configuration | | 1x2 | | - | | - | | - | | +| Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | +| Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc1 to be fulfilled. | | | | | | | | | | +| Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N oc2 to be fulfilled. | | | | | | | | | | +| Note 4: E s /I ot , RSRP, SCH_RP, I o and WLAN SNR have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | | | +| Note 5: The resources for uplink transmission are assigned to the UE prior to the start of time period T2. | | | | | | | | | | + +##### A.3.2.2.2 Test Requirements + +The WLAN Response Time shall fulfil the requirements in section 4.3 and the WLAN AP report shall fulfil the requirements in section 7.3. This test is, as stated in Clause 7, statistical in nature and the UE shall meet the corresponding requirement for at least 90% of the reported cases. + +#### A.3.2.3 LTE-TDD: WLAN AP Identification and reporting delay under nominal conditions test + +##### A.3.2.3.1 Test purpose and Environment + +The purpose of this test is to verify the requirements in Clause 7.3 for WLAN AP measurements. The UE shall send *wlan-MeasurementInformation* IE including WLAN measurements for each AP indicating at least *wlan-AP-Identifier* (BSSID) and *rssi* (if reporting of RSSI is supported by the UE as indicated by the UE in the LPP PROVIDE CAPABILITIES message). + +In this test, there are cell1 (E-UTRAN TDD) and 6 WLAN APs transmitting beacon signals at least every 102.4 ms. There is an active LTE connection between the SS and the UE and the measurements are performed in RRC\_CONNECTED state. The beacon signals from different APs shall be received at different time slots or in non-overlapping frequency channels. Non-overlapping frequency channels shall be at least 25 MHz apart in the WLAN 2.4 GHz band and at least 20 MHz apart in the WLAN 5 GHz band. The APs are transmitting in 3 non-overlapping frequency channels in the same WLAN Frequency Band. There are 2 APs in every channel. The test consists of two successive time periods, with duration of T1 and T2, respectively. *WLAN-RequestLocationInformation* message shall be provided to the UE during T1. WLAN Access Points only transmit signal during T2. + +**Table A.3.2.3.1-1: General WLAN AP test parameters +for WLAN AP Identification and reporting delay under nominal conditions test** + +| Parameter | Unit | Value | Comment | +|-------------------------|------|-------|---------------------------------------------------------| +| Number of Access Points | N/A | 6 | AP1-AP6 | +| Time Slot 1 | ms | 1 | AP1, AP2 | +| Time Slot 2 | ms | 1 | AP3, AP4 | +| Time Slot 3 | ms | 1 | AP5 | +| Time Slot 4 | ms | 1 | AP6 | +| T1 | s | 5 | During this time the WLAN signal is not transmitted | +| T2 | s | 25 | UE shall report WLAN measurement information within 20s | + +**Table A.3.2.3.1-2: E-UTRAN TDD Cell specific and WLAN AP specific test parameters for WLAN AP Identification and reporting delay under nominal conditions test** + +| Parameter | Unit | Cell 1 | | AP 1, 4 | | AP 2, 5 | | AP 3, 6 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------|------|------------------------------------------------------|-----|------------------------------------------------------|-----|------------------------------------------------------|-----| +| | | T1 | T2 | T1 | T2 | T1 | T2 | T1 | T2 | +| E-UTRA RF Channel Number | | 1 | | N/A | | N/A | | N/A | | +| WLAN Channel Number | | N/A | | 1 | | 2 | | 3 | | +| BW channel | | 10MHz | | N/A | | N/A | | N/A | | +| WLAN Channel spacing | | N/A | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | +| PDSCH parameters:
DL Reference Measurement Channel | | R.0 TDD | | N/A | | N/A | | N/A | | +| PCFICH/PDCCH/PHICH parameters:
DL Reference Measurement Channel | | R.6 TDD | | N/A | | N/A | | N/A | | +| OCNG Patterns | | OP.1 TDD | | N/A | | N/A | | N/A | | +| PBCH_RA | dB | 0 | | N/A | | N/A | | N/A | | +| PBCH_RB | dB | | | | | | | | | +| PSS_RA | dB | | | | | | | | | +| SSS_RA | dB | | | | | | | | | +| PCFICH_RB | dB | | | | | | | | | +| PHICH_RA | dB | | | | | | | | | +| PHICH_RB | dB | | | | | | | | | +| PDCCH_RA | dB | | | | | | | | | +| PDCCH_RB | dB | | | | | | | | | +| PDSCH_RA | dB | | | | | | | | | +| PDSCH_RB | dB | | | | | | | | | +| OCNG_RA Note 1 | dB | | | | | | | | | +| OCNG_RB Note 1 | dB | | | | | | | | | +| N oc1 Note 2 | dBm/15 KHz | -98 | | N/A | | N/A | | N/A | | +| N oc2 Note 3 | dBm/20 MHz | N/A | | -75 | | -75 | | -75 | | +| $\hat{E}_s/N_{oc1}$ | dB | 3 | 3 | N/A | | N/A | | N/A | | +| $\hat{E}_s/I_{ot}$ Note 4 | dB | 3 | 3 | | | | | | | +| RSRP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | | +| SCH_RP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | | +| I o Note 3 | dBm/Ch BW | - | - | | | | | | | +| | | 65.5 | 65.5 | | | | | | | +| WLAN Received Power Level | dBm | N/A | N/A | - inf | -60 | - inf | -60 | - inf | -60 | +| WLAN SNR Note 4 | dB | N/A | | 15 | | 15 | | 15 | | +| Propagation Condition | | AWGN | | | | | | | | +| Antenna Configuration | | 1x2 | | - | | - | | - | | +| Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | +| Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc1 to be fulfilled. | | | | | | | | | | +| Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N oc2 to be fulfilled. | | | | | | | | | | +| Note 4: E s /I ot , RSRP, SCH_RP, I o and WLAN SNR have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | | | +| Note 5: The resources for uplink transmission are assigned to the UE prior to the start of time period T2. | | | | | | | | | | + +##### A.3.2.3.2 Test Requirements + +The WLAN Response Time shall fulfil the requirements in section 4.3 and the WLAN AP report shall fulfil the requirements in section 7.3. This test is, as stated in Clause 7, statistical in nature and the UE shall meet the corresponding requirement for at least 90% of the reported cases. + +#### A.3.2.4 LTE-FDD: WLAN AP Identification and reporting delay under dynamic range conditions test + +##### A.3.2.4.1 Test purpose and Environment + +The purpose of this test is to verify the requirements in Clause 7.4 for WLAN AP measurements. The UE shall send *wlan-MeasurementInformation* IE including WLAN measurements for each AP indicating at least *wlan-AP-Identifier* (BSSID) and *rssi* (if reporting of RSSI is supported by the UE as indicated by the UE in the LPP PROVIDE CAPABILITIES message). + +In this test, there are cell1 (E-UTRAN FDD) and 3 WLAN APs transmitting beacon signals at least every 102.4 ms. There is an active LTE connection between the SS and the UE and the measurements are performed in RRC\_CONNECTED state. The beacon signals from different APs shall be received at different time slots or in non-overlapping frequency channels. Non-overlapping frequency channels shall be at least 25 MHz apart in the WLAN 2.4 GHz band and at least 20 MHz apart in the WLAN 5 GHz band. The APs are transmitting in 3 non-overlapping frequency channels in the same WLAN Frequency Band. There is 1 AP in every channel. The test consists of two successive time periods, with duration of T1 and T2, respectively. *WLAN-RequestLocationInformation* message shall be provided to the UE during T1. WLAN Access Points only transmit signal during T2. + +**Table A.3.2.4.1-1: General test parameters for WLAN AP Identification and reporting delay under dynamic range conditions test** + +| Parameter | Unit | Value | Comment | +|-------------------------|------|-------|---------------------------------------------------------| +| Number of Access Points | N/A | 3 | AP1-AP3 | +| Time Slot 1 | ms | 1 | AP1, AP2, AP3 | +| T1 | s | 5 | During this time the WLAN signal is not transmitted | +| T2 | s | 25 | UE shall report WLAN measurement information within 20s | + +**Table A.3.2.4.1-2: E-UTRAN FDD Cell specific test parameters for WLAN AP Identification and reporting delay under dynamic range conditions test** + +| Parameter | Unit | Cell 1 | | AP 1 | | AP 2 | | AP 3 | | +|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-----|------------------------------------------------------|------------------------------------------------|------------------------------------------------------|------------------------------------------------|------------------------------------------------------|------------------------------------------------| +| | | T1 | T2 | T1 | T2 | T1 | T2 | T1 | T2 | +| E-UTRA RF Channel Number | | 1 | | N/A | | N/A | | N/A | | +| WLAN Channel Number | | N/A | | 1 | | 2 | | 3 | | +| BW channel | | 10MHz | | N/A | | N/A | | N/A | | +| WLAN Channel spacing | | N/A | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | +| PDSCH parameters:
DL Reference Measurement Channel | | R.0 FDD | | N/A | | N/A | | N/A | | +| PCFICH/PDCCH/PHICH parameters: DL Reference Measurement Channel | | R.6 FDD | | N/A | | N/A | | N/A | | +| OCNG Patterns | | OP.1 FDD | | N/A | | N/A | | N/A | | +| PBCH_RA | dB | 0 | | N/A | | N/A | | N/A | | +| PBCH_RB | dB | | | | | | | | | +| PSS_RA | dB | | | | | | | | | +| SSS_RA | dB | | | | | | | | | +| PCFICH_RB | dB | | | | | | | | | +| PHICH_RA | dB | | | | | | | | | +| PHICH_RB | dB | | | | | | | | | +| PDCCH_RA | dB | | | | | | | | | +| PDCCH_RB | dB | | | | | | | | | +| PDSCH_RA | dB | | | | | | | | | +| PDSCH_RB | dB | | | | | | | | | +| OCNG_RA Note 1 | dB | | | | | | | | | +| OCNG_RB Note 1 | dB | | | | | | | | | +| N oc1 Note 2 | dBm/15 KHz | -98 | | N/A | | N/A | | N/A | | +| N oc2 Note 3 | dBm/20 MHz | N/A | | -85 | | -85 | | -85 | | +| $\hat{E}_s/N_{oc1}$ | dB | 3 | 3 | N/A | | N/A | | N/A | | +| $\hat{E}_s/I_{ot}$ Note 4 | dB | 3 | 3 | | | | | | | +| RSRP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | | +| SCH_RP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | | +| I o Note 3 | dBm/Ch BW | - | - | | | | | | | +| WLAN Received Power Level | dBm | N/A | N/A | -inf | WLAN 2.4 GHz band: -74
WLAN 5 GHz band: -79 | -inf | WLAN 2.4 GHz band: -39
WLAN 5 GHz band: -63 | -inf | WLAN 2.4 GHz band: -74
WLAN 5 GHz band: -79 | +| WLAN SNR Note 4 | dB | N/A | | WLAN 2.4 GHz band: 11
WLAN 5 GHz band: 6 | | WLAN 2.4 GHz band: 46
WLAN 5 GHz band: 22 | | WLAN 2.4 GHz band: 11
WLAN 5 GHz band: 6 | | +| Propagation Condition | | AWGN | | | | | | | | +| Antenna Configuration | | 1x2 | | - | | - | | - | | +| Note 1: | OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc1 to be fulfilled. | | | | | | | | | +| Note 3: | Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N oc2 to be fulfilled. | | | | | | | | | +| Note 4: | E s /I ot , RSRP, SCH_RP, I o and WLAN SNR have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | | +| Note 5: | The resources for uplink transmission are assigned to the UE prior to the start of time period T2. | | | | | | | | | + +##### A.3.2.4.2 Test Requirements + +The WLAN Response Time shall fulfil the requirements in section 4.3 and the WLAN AP report shall fulfil the requirements in section 7.4. This test is, as stated in Clause 7, statistical in nature and the UE shall meet the corresponding requirement for at least 90% of the reported cases. + +#### A.3.2.5 LTE-TDD: WLAN AP Identification and reporting delay under dynamic range conditions test + +##### A.3.2.5.1 Test purpose and Environment + +The purpose of this test is to verify the requirements in Clause 7.4 for WLAN AP measurements. The UE shall send *wlan-MeasurementInformation* IE including WLAN measurements for each AP indicating at least *wlan-AP-Identifier* (BSSID) and *rssi* (if reporting of RSSI is supported by the UE as indicated by the UE in the LPP PROVIDE CAPABILITIES message). + +In this test, there are cell1 (E-UTRAN TDD) and 3 WLAN APs transmitting beacon signals at least every 102.4 ms. There is an active LTE connection between the SS and the UE and the measurements are performed in RRC\_CONNECTED state. The beacon signals from different APs shall be received at different time slots or in non-overlapping frequency channels. Non-overlapping frequency channels shall be at least 25 MHz apart in the WLAN 2.4 GHz band and at least 20 MHz apart in the WLAN 5 GHz band. The APs are transmitting in 3 non-overlapping frequency channels in the same WLAN Frequency Band. There is 1 AP in every channel. The test consists of two successive time periods, with duration of T1 and T2, respectively. *WLAN-RequestLocationInformation* message shall be provided to the UE during T1. WLAN Access Points only transmit signal during T2. + +**Table A.3.2.5.1-1: General test parameters for WLAN AP Identification and reporting delay under dynamic range conditions test** + +| Parameter | Unit | Value | Comment | +|-------------------------|------|-------|---------------------------------------------------------| +| Number of Access Points | N/A | 3 | AP1-AP3 | +| Time Slot 1 | ms | 1 | AP1, AP2, AP3 | +| T1 | s | 5 | During this time the WLAN signal is not transmitted | +| T2 | s | 25 | UE shall report WLAN measurement information within 20s | + +**Table A.3.2.5.1-2: E-UTRAN TDD Cell specific test parameters for WLAN AP Identification and reporting delay under dynamic range conditions test** + +| Parameter | Unit | Cell 1 | | AP 1 | | AP 2 | | AP 3 | | +|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------|------------------------------------------------------|------------------------------------------------|------------------------------------------------------|------------------------------------------------|------------------------------------------------------|------------------------------------------------| +| | | T1 | T2 | T1 | T2 | T1 | T2 | T1 | T2 | +| E-UTRA RF Channel Number | | 1 | | N/A | | N/A | | N/A | | +| WLAN Channel Number | | N/A | | 1 | | 2 | | 3 | | +| BW channel | | 10MHz | | N/A | | N/A | | N/A | | +| WLAN Channel spacing | | N/A | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | WLAN 2.4 GHz band: 25 MHz
WLAN 5 GHz band: 20 MHz | | +| PDSCH parameters:
DL Reference Measurement Channel | | R.0 TDD | | N/A | | N/A | | N/A | | +| PCFICH/PDCCH/PHICH parameters: DL Reference Measurement Channel | | R.6 TDD | | N/A | | N/A | | N/A | | +| OCNG Patterns | | OP.1 TDD | | N/A | | N/A | | N/A | | +| PBCH_RA | dB | 0 | | N/A | | N/A | | N/A | | +| PBCH_RB | dB | | | | | | | | | +| PSS_RA | dB | | | | | | | | | +| SSS_RA | dB | | | | | | | | | +| PCFICH_RB | dB | | | | | | | | | +| PHICH_RA | dB | | | | | | | | | +| PHICH_RB | dB | | | | | | | | | +| PDCCH_RA | dB | | | | | | | | | +| PDCCH_RB | dB | | | | | | | | | +| PDSCH_RA | dB | | | | | | | | | +| PDSCH_RB | dB | | | | | | | | | +| OCNG_RA Note 1 | dB | | | | | | | | | +| OCNG_RB Note 1 | dB | | | | | | | | | +| N oc1 Note 2 | dBm/15 KHz | -98 | | N/A | | N/A | | N/A | | +| N oc2 Note 3 | dBm/20 MHz | N/A | | -85 | | -85 | | -85 | | +| $\hat{E}_s/N_{oc1}$ | dB | 3 | 3 | N/A | | N/A | | N/A | | +| $\hat{E}_s/I_{ot}$ Note 4 | dB | 3 | 3 | | | | | | | +| RSRP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | | +| SCH_RP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | | +| I o Note 3 | dBm/Ch BW | -65.5 | -65.5 | | | | | | | +| | | | | | | | | | | +| WLAN Received Power Level | dBm | N/A | N/A | -inf | WLAN 2.4 GHz band: -74
WLAN 5 GHz band: -79 | -inf | WLAN 2.4 GHz band: -39
WLAN 5 GHz band: -63 | -inf | WLAN 2.4 GHz band: -74
WLAN 5 GHz band: -79 | +| WLAN SNR Note 4 | dB | N/A | | WLAN 2.4 GHz band: 11
WLAN 5 GHz band: 6 | | WLAN 2.4 GHz band: 46
WLAN 5 GHz band: 22 | | WLAN 2.4 GHz band: 11
WLAN 5 GHz band: 6 | | +| Propagation Condition | | AWGN | | | | | | | | +| Antenna Configuration | | 1x2 | | - | | - | | - | | +| Note 1: | OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc1 to be fulfilled. | | | | | | | | | +| Note 3: | Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N oc2 to be fulfilled. | | | | | | | | | +| Note 4: | E s /I ot , RSRP, SCH_RP, I o and WLAN SNR have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | | +| Note 5: | The resources for uplink transmission are assigned to the UE prior to the start of time period T2. | | | | | | | | | + +##### A.3.2.5.2 Test Requirements + +The WLAN Response Time shall fulfil the requirements in section 4.3 and the WLAN AP report shall fulfil the requirements in section 7.4. This test is, as stated in Clause 7, statistical in nature and the UE shall meet the corresponding requirement for at least 90% of the reported cases. + +### A.3.3 Bluetooth Measurement Requirements + +Editor's Note: Based on the E-UTRA test cases specified in section, additional Bluetooth test parameters for EN-DC and NR SA operations shall be defined separately. The LTE and NR cell specific parameters for EN-DC and NR SA tests are FFS and shall be aligned with the NR requirements. + +#### A.3.3.1 E-UTRAN FDD Bluetooth identification + +##### A.3.3.1.1 Test Purpose and Environment + +The purpose of this test is to verify that the UE correctly identify and report Bluetooth Low Energy devices within the requirements stated in clause 4.4. + +The test parameters are given in Tables A.3.3.1.1-1 and A.3.3.1.1-2 below. In the tests there are cell1 (E-UTRAN FDD) and 6 Bluetooth low energy (BLE) devices. The test consists of two successive time periods, with duration of T1 and T2, respectively. *BT-RequestLocationInformation* message shall be provided to the UE during T1. BLE devices only transmit signal during T2. + +**Table A.3.3.1.1-1: General test parameters for E-UTRAN FDD Bluetooth measurement under AWGN in non-DRX** + +| Parameter | Unit | Value | Comment | +|--------------------------------------------|------|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Active cell | | Cell 1 | Cell 1 is on E-UTRA RF channel number 1. | +| Bluetooth Low Energy (BLE) Devices | | BLE 1, BLE 2, BLE3, BLE4, BLE5 and BLE6 | BLE 1 and BLE2 are on Bluetooth Advertising Channel 1 (2402 MHz).
BLE 3 and BLE4 are on Bluetooth Advertising Channel 2 (2426 MHz).
BLE 5 and BLE6 are on Bluetooth Advertising Channel 3 (2480 MHz). | +| CP length | | Normal | Applicable to cell 1 | +| E-UTRA RF Channel Number | | 1 | One E-UTRA FDD carrier frequency is used. | +| Bluetooth Advertising Channel Number | | Channel 1:2402 MHz, Channel 2:2426 MHz, Channel 3:2480 MHz | Bluetooth advertising channels (2402, 2426, 2480 MHz) | +| Bluetooth beacon signal broadcast interval | ms | 100 ms | | +| DRX | | OFF | | +| T1 | s | 5 | During this time the cell1 shall be known to the UE; but cell2 shall be unknown to the UE. | +| T2 | s | 15 | UE should report Bluetooth measurement information within 10.24s. | + +**Table A.3.3.1.1-2: Cell specific test parameters for E-UTRAN FDD-WLAN event triggered reporting under AWGN in non-DRX** + +| Parameter | Unit | Cell 1 | | BLE1, BLE2 | | BLE3, BLE4 | | BLE5, BLE6 | | +|-----------|------|--------|----|------------|----|------------|----|------------|----| +| | | T1 | T2 | T1 | T2 | T1 | T2 | T1 | T2 | + +| | | | | | | | | | +|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------|-------|-----------|------|-----------|------| +| E-UTRA RF Channel Number | | 1 | | N/A | N/A | | N/A | | +| Bluetooth Advertising Channel Number | | N/A | | 1 | 2 | | 3 | | +| BW channel | | 10MHz | | 2 MHz | 2 MHz | | 2 MHz | | +| PDSCH parameters:
DL Reference Measurement Channel | | R.0 FDD | | N/A | N/A | | N/A | | +| PCFICH/PDCCH/PHICH parameters:
DL Reference Measurement Channel | | R.6 FDD | | N/A | N/A | | N/A | | +| OCNG Patterns | | OP.1 FDD | | N/A | N/A | | N/A | | +| PBCH_RA | dB | 0 | | N/A | N/A | | N/A | | +| PBCH_RB | dB | | | | | | | | +| PSS_RA | dB | | | | | | | | +| SSS_RA | dB | | | | | | | | +| PCFICH_RB | dB | | | | | | | | +| PHICH_RA | dB | | | | | | | | +| PHICH_RB | dB | | | | | | | | +| PDCCH_RA | dB | | | | | | | | +| PDCCH_RB | dB | | | | | | | | +| PDSCH_RA | dB | | | | | | | | +| PDSCH_RB | dB | | | | | | | | +| OCNG_RA Note 1 | dB | | | | | | | | +| OCNG_RB Note 1 | dB | | | | | | | | +| N oc1 Note 2 | dBm/15 KHz | -98 | | N/A | N/A | | N/A | | +| N oc2 Note 3 | dBm/2MHz | N/A | | -84 | -84 | | -84 | | +| Ê s /N oc1 | dB | 3 | 3 | N/A | | | | | +| Ê s /I ot Note 4 | dB | 3 | 3 | | | | | | +| RSRP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | +| SCH_RP Note 4 | dBm/15 kHz | -95 | -95 | | | | | | +| I o Note 3 | dBm/Ch BW | -65.5 | -65.5 | | | | | | +| Bluetooth RSSI Note 4 | dBm/2 MHz | N/A | | N/A | -infinity | -60 | -infinity | -60 | +| SINR Note 4 | dB | N/A | | N/A | infinity | 63.2 | infinity | 63.2 | +| Propagation Condition | | AWGN | | | | | | | +| Antenna Configuration | | 1x2 | | - | - | | - | | +| Note 1: | OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc1 to be fulfilled. | | | | | | | | +| Note 3: | Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N oc2 to be fulfilled. | | | | | | | | +| Note 4: | Ê s /I ot , RSRP, SCH_RP, I o and Bluetooth RSSI have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | +| Note 5: | The resources for uplink transmission are assigned to the UE prior to the start of time period T2. | | | | | | | | + +##### A.3.3.1.2 Test Requirements + +The UE shall send *BT-ProvideLocationInformation*, with a measurement reporting delay less than 10.24s from the beginning of time period T2. + +The rate of correct events observed during repeated tests shall be at least 90% for each of the events. + +NOTE: The actual overall delays measured in the tests may be up to $2 \times \text{TTI}_{\text{DCCH}}$ higher than the measurement reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH. + +#### A.3.3.2 E-UTRAN TDD Bluetooth identification + +##### A.3.3.2.1 Test Purpose and Environment + +The purpose of this test is to verify that the UE correctly identify and report Bluetooth Low Energy devices within the requirements stated in clause 4.4. + +The test parameters are given in Tables A.3.3.2.1-1 and A.3.3.2.1-2 below. In the tests there are cell1 (E-UTRAN FDD) and 6 Bluetooth low energy (BLE) devices. The test consists of two successive time periods, with duration of T1 and T2, respectively. BT-RequestLocationInformation message shall be provided to the UE during T1. BLE devices only transmit signal during T2. + +**Table A.3.3.2.1-1: General test parameters for E-UTRAN TDD Bluetooth measurement under AWGN in non-DRX** + +| Parameter | Unit | Value | Comment | +|--------------------------------------------|------|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Active cell | | Cell 1 | Cell 1 is on E-UTRA RF channel number 1. | +| Bluetooth Low Energy (BLE) Devices | | BLE 1, BLE 2, BLE3, BLE4, BLE5 and BLE6 | BLE 1 and BLE2 are on Bluetooth Advertising Channel 1 (2402 MHz).
BLE 3 and BLE4 are on Bluetooth Advertising Channel 2 (2426 MHz).
BLE 5 and BLE6 are on Bluetooth Advertising Channel 3 (2480 MHz). | +| CP length | | Normal | Applicable to cell 1 | +| E-UTRA RF Channel Number | | 1 | One E-UTRA FDD carrier frequency is used. | +| Bluetooth Advertising Channel Number | | Channel 1:2402 MHz, Channel 2:2426 MHz, Channel 3:2480 MHz | Bluetooth advertising channels (2402, 2426, 2480 MHz) | +| Bluetooth beacon signal broadcast interval | ms | 100 ms | | +| DRX | | OFF | | +| Special subframe configuration | | 6 | As specified in table 4.2-1 in TS 36.211 [16].
The same configuration applies to all cells. | +| Uplink-downlink configuration | | 1 | As specified in table 4.2-2 in TS 36.211 [16].
The same configuration applies to all cells | +| T1 | s | 5 | During this time the cell1 shall be known to the UE; but cell2 shall be unknown to the UE. | +| T2 | s | 15 | UE should report Bluetooth measurement information within 10.24s. | + +**Table A.3.3.2.1-2: Cell specific test parameters for E-UTRAN TDD-WLAN event triggered reporting under AWGN in non-DRX** + +| Parameter | Unit | Cell 1 | | BLE1, BLE2 | | BLE3, BLE4 | | BLE5, BLE6 | | +|-----------|------|--------|----|------------|----|------------|----|------------|----| +| | | T1 | T2 | T1 | T1 | T1 | T2 | T1 | T2 | + +| | | | | | | | | | +|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------|-----------|---------------|-----------|---------------|-----------| +| E-UTRA RF Channel Number | | 1 | N/A | N/A | N/A | | | | +| Bluetooth Advertising Channel Number | | N/A | 1 | 2 | 3 | | | | +| BW channel | | 10MHz | 2 MHz | 2 MHz | 2 MHz | | | | +| PDSCH parameters:
DL Reference Measurement Channel | | R.0 TDD | N/A | N/A | N/A | | | | +| PCFICH/PDCCH/PHICH parameters:
DL Reference Measurement Channel | | R.6 TDD | N/A | N/A | N/A | | | | +| OCNG Patterns | | OP.1 TDD | N/A | N/A | N/A | | | | +| PBCH_RA | dB | 0 | N/A | N/A | N/A | | | | +| PBCH_RB | dB | | | | | | | | +| PSS_RA | dB | | | | | | | | +| SSS_RA | dB | | | | | | | | +| PCFICH_RB | dB | | | | | | | | +| PHICH_RA | dB | | | | | | | | +| PHICH_RB | dB | | | | | | | | +| PDCCH_RA | dB | | | | | | | | +| PDCCH_RB | dB | | | | | | | | +| PDSCH_RA | dB | | | | | | | | +| PDSCH_RB | dB | | | | | | | | +| OCNG_RA Note 1 | dB | | | | | | | | +| OCNG_RB Note 1 | dB | | | | | | | | +| N oc1 Note 2 | dBm/15 KHz | -98 | N/A | N/A | N/A | | | | +| N oc2 Note 3 | dBm/2 MHz | N/A | -84 | -84 | -84 | | | | +| Ê s /N oc1 | dB | 3     3 | N/A | N/A | N/A | | | | +| Ê s /I ot Note 4 | dB | 3     3 | | | | | | | +| RSRP Note 4 | dBm/15 kHz | -95   -95 | | | | | | | +| SCH_RP Note 4 | dBm/15 kHz | -95   -95 | | | | | | | +| I o Note 3 | dBm/Ch BW | -     -
65.5   65.5 | | | | | | | +| Bluetooth RSSI Note 4 | dBm/2 MHz | N/A | -
infinity | -60
- | -
infinity | -60
- | -
infinity | -60
- | +| SINR Note 4 | dB | N/A | -
infinity | -
63.2 | -
infinity | -
63.2 | -
infinity | -
63.2 | +| Propagation Condition | | AWGN | | | | | | | +| Antenna Configuration | | 1x2 | - | - | - | | | | +| Note 1: | OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N oc1 to be fulfilled. | | | | | | | | +| Note 3: | Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N oc2 to be fulfilled. | | | | | | | | +| Note 4: | Ê s /I ot , RSRP, SCH_RP, I o and WLAN RSSI have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | +| Note 5: | The resources for uplink transmission are assigned to the UE prior to the start of time period T2. | | | | | | | | + +##### A.3.3.2.2 Test Requirements + +The UE shall send *BT-ProvideLocationInformation*, with a measurement reporting delay less than 10.24s from the beginning of time period T2. + +The rate of correct events observed during repeated tests shall be at least 90% for each of the events. + +NOTE: The actual overall delays measured in the tests may be up to $2 imes ext{TTI}_{ ext{DCCH}}$ higher than the measurement reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH. + +## A.4 Measurement Performance Requirements + +### A.4.1 General + +Unless explicitly stated otherwise: + +- Reported measurements shall be within defined range of accuracy limits defined in clause 5 for at least 90 % of the reported cases. If multiple measurement performance requirements are verified in the same test, the reported measurements for each requirement shall be within defined range of accuracy limits of the corresponding requirement defined in clause 5 for at least 90% of the reported cases. +- Measurements are performed in RRC\_CONNECTED state. + +### A.4.2 MBS Code Phase Measurement Accuracy Requirements in AWGN + +#### A.4.2.1 Test Purpose and Environment + +The purpose of this test is to verify that the MBS Code Phase measurement accuracy is within the specified limits. This single test will verify the requirements in clauses 5.2, 5.3 and 5.4 for MBS measurements. The channel type for this test is AWGN, as specified in the appropriate sub-clause of clause 5. This test can be used for NR, UTRA and E-UTRA testing. + +In each test, there is one beacon transmitted in each of four consecutive beacon slots. The position of first of the four consecutive beacons in the beacon transmission period can be any slot, but it is static for the duration of the test. In other slots there are no simulated beacons. All beacons are in the same time slotted RF channel, with centre frequency of 925.977 MHz or set using the network assistance data. All beacons are of type TB1 (2 MHz) [7], or set using the network assistance data in Release 14, and the data transmitted is in Type 2 packets with the following data fields: The MBS Transmitter ID and the Slot Index shall be set to the MBS slot number; All other beacon payload data shall be populated with zeros. + +In the four slots containing beacon transmissions, every other slot shall contain a beacon with the higher signal strength beacon, and the other slots shall contain a beacon with the lower signal strength. + +The higher power beacons (-30 dBm) shall have code phase delay of $1.6678 \times 10^{-4}$ ms (corresponding to 50 m) and the lower power beacons (-130 dBm) shall have code phase delay of $5.00346 \times 10^{-3}$ ms (corresponding to 1500 m). + +Each of the beacons shall use a unique PN code chosen from the PN code list for TB1 [7]. + +If the UE supports MBS assistance data, the UE will receive the MBS assistance data for each beacon via LPP, according to Annex A. + +**Table A.4.2.1-1: General test parameters for Code Phase measurement Accuracy** + +| Parameter | Unit | Value | Comment | +|------------------------------------------------|---------|--------------------------------------|--------------------------------------------------------------------------| +| Centre Frequency | MHz | 925.977 | | +| RF Channel | N/A | AWGN | | +| MBS Beacon Configuration | N/A | TB1 (2 MHz) | | +| MBS Packet Type | N/A | Type 2 | | +| Beacon PN Code | Integer | Chosen from the PN code list for TB1 | | +| -30 dBm beacon transmitted Code Phase (delay) | ms | $1.6678 \times 10^{-4}$ | Corresponds to 50 m. Constant per beacon for the duration of the test. | +| -130 dBm beacon transmitted Code Phase (delay) | ms | $5.00346 \times 10^{-3}$ | Corresponds to 1500 m. Constant per beacon for the duration of the test. | +| $T_{\text{MBS\_meas}}$ | ms | 12000 | | + +**Table A.4.2.1-2: MBS Beacon Payload fields for Code Phase measurement Accuracy** + +| Parameter | Unit | Value | Comment | +|------------------|---------|----------------------|---------| +| TxID | Integer | Equal to Slot number | | +| Slot Index | Integer | Equal to Slot number | | +| All other fields | N/A | 0 | | + +#### A.4.2.2 Test Requirements + +The MBS Code Phase measurement accuracy shall fulfil the requirements in clauses 5.2, 5.3 and 5.4. + +### A.4.3 MBS Code Phase Measurement Accuracy Requirements in Multipath + +#### A.4.3.1 Test Purpose and Environment + +The purpose of this test is to verify that the MBS Code Phase measurement accuracy is within the specified limits. This test will verify the requirements in clause 5.5 for MBS measurements. The channel type for the test is specified in clause 5.5. This test can be used for NR, UTRA and E-UTRA testing. + +In this test, there is one beacon transmitted in each of two chosen slots. The position of the beacons in the beacon transmission period is static for the duration of the test. In other slots there are no simulated beacons. Both beacons are in the same time slotted RF channel, with centre frequency of 925.977 MHz or set using the network assistance data. All beacons are of type TB1 (2 MHz) [7], or set using the network assistance data in Release 14, and the data transmitted is in Type 2 packets with the following data fields: The MBS Transmitter ID and the Slot Index shall be set to the MBS slot number; All other beacon payload data shall be populated with zeros. + +Both beacon slots shall contain a beacon with the signal strength listed in clause 5.5. + +The beacons shall have code phase delay of $1.6678 \times 10^{-4}$ ms (corresponding to 50 m). + +Each of the beacons shall use a unique PN code chosen from the PN code list for TB1 [7]. + +If the UE supports MBS assistance data, the UE will receive the MBS assistance data for each beacon via LPP, according to Annex A. + +**Table A.4.3.1-1: General test parameters for Code Phase measurement Accuracy in Multipath** + +| Parameter | Unit | Value | Comment | +|-----------------------------------------------|---------|--------------------------------------|------------------------------------------------------------------------| +| Centre Frequency | MHz | 925.977 | | +| RF Channel | N/A | EPA 5 Hz | | +| MBS Beacon Configuration | N/A | TB1 (2 MHz) | | +| MBS Packet Type | N/A | Type 2 | | +| Beacon PN Code | Integer | Chosen from the PN code list for TB1 | | +| -30 dBm beacon transmitted Code Phase (delay) | ms | $1.6678 \times 10^{-4}$ | Corresponds to 50 m. Constant per beacon for the duration of the test. | +| $T_{\text{MBS\_meas}}$ | ms | 12000 | | + +**Table A.4.3.1-2: MBS Beacon Payload fields for Code Phase measurement Accuracy** + +| Parameter | Unit | Value | Comment | +|------------------|---------|----------------------|---------| +| TxID | Integer | Equal to Slot number | | +| Slot Index | Integer | Equal to Slot number | | +| All other fields | N/A | 0 | | + +#### A.4.3.2 Test Requirements + +The MBS Code Phase measurement accuracy shall fulfil the requirements in clause 5.5. + +# --- Annex B (normative): Assistance data required for testing (Release 14 and beyond) --- + +## B.1 Introduction + +This annex defines the assistance data IEs available at the SS in all test cases where the UE supports MBS acquisition assistance data. Almanac assistance data will not be provided since there are only performance requirements for UE-Assisted mode. The acquisition assistance data shall be provided for all beacons. + +The information elements are given with reference to 3GPP TS 36.355 [3], where the details are defined. + +## --- B.2 MBS Assistance Data + +Table B.2-1 defines the acquisition assistance data elements which shall be provided to the UE. Assistance data IEs supported by the UE but not listed in Table B.2-1 shall not be sent. + +**Table B.2-1: Assistance Data to be provided to the UE for each beacon** + +| MBS Acquisition Assistance Data IE | Measurement reporting delay test case | MBS Code Phase Measurement accuracy test cases | +|------------------------------------|---------------------------------------|------------------------------------------------| +| transmitterID-r14 | Yes | Yes | +| mbsConfiguration-r14 | Yes | Yes | +| pnCodeIndex-r14 | Yes | Yes | +| freq-r14 | Yes | Yes | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37213/raw.md b/marked/Rel-18/37_series/37213/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..72d2255668f206aa0a5b20cb0e1dc0880af18c5c --- /dev/null +++ b/marked/Rel-18/37_series/37213/raw.md @@ -0,0 +1,1477 @@ + + +# 3GPP TS 37.213 V18.1.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical layer procedures for shared spectrum channel access (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo. + +3GPP logo + +## --- **Keywords** + +--- + +Radio layer 1 + +## **3GPP** + +## --- **Postal address** + +### --- **3GPP support office address** + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + +--- + + + +## --- **Copyright Notification** + +--- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|--------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 7 | +| 4 Channel access procedure ..... | 7 | +| 4.0 General ..... | 7 | +| 4.1 Downlink channel access procedures..... | 8 | +| 4.1.1 Type 1 DL channel access procedures ..... | 8 | +| 4.1.1.1 Regional limitations on channel occupancy time ..... | 9 | +| 4.1.2 Type 2 DL channel access procedures ..... | 9 | +| 4.1.2.1 Type 2A DL channel access procedures..... | 10 | +| 4.1.2.2 Type 2B DL channel access procedures ..... | 10 | +| 4.1.2.3 Type 2C DL channel access procedures ..... | 10 | +| 4.1.3 DL channel access procedures in a shared channel occupancy..... | 10 | +| 4.1.4 Contention window adjustment procedures ..... | 11 | +| 4.1.4.1 Contention window adjustment procedures for transmissions by eNB..... | 11 | +| 4.1.4.2 Contention window adjustment procedures for DL transmissions by gNB ..... | 12 | +| 4.1.4.3 Common procedures for CWS adjustments for DL transmissions..... | 13 | +| 4.1.5 Energy detection threshold adaptation procedures..... | 13 | +| 4.1.6 Channel access procedures for transmission(s) on multiple channels..... | 14 | +| 4.1.6.1 Type A multi-channel access procedures ..... | 14 | +| 4.1.6.1.1 Type A1 multi-channel access procedures..... | 14 | +| 4.1.6.1.2 Type A2 multi-channel access procedures..... | 14 | +| 4.1.6.2 Type B multi-channel access procedure ..... | 14 | +| 4.1.6.2.1 Type B1 multi-channel access procedure..... | 15 | +| 4.1.6.2.2 Type B2 multi-channel access procedure..... | 15 | +| 4.2 Uplink channel access procedures..... | 15 | +| 4.2.1 Channel access procedures for uplink transmission(s)..... | 16 | +| 4.2.1.0 Channel access procedures and UL related signaling..... | 17 | +| 4.2.1.0.0 Channel access procedures upon detection of a common DCI..... | 17 | +| 4.2.1.0.1 Channel access procedures for consecutive UL transmission(s) ..... | 18 | +| 4.2.1.0.2 Conditions for maintaining Type 1 UL channel access procedures..... | 19 | +| 4.2.1.0.3 Conditions for indicating Type 2 channel access procedures ..... | 20 | +| 4.2.1.0.4 Channel access procedures for UL multi-channel transmission(s)..... | 20 | +| 4.2.1.1 Type 1 UL channel access procedure ..... | 21 | +| 4.2.1.2 Type 2 UL channel access procedure ..... | 22 | +| 4.2.1.2.1 Type 2A UL channel access procedure..... | 22 | +| 4.2.1.2.2 Type 2B UL channel access procedure..... | 22 | +| 4.2.1.2.3 Type 2C UL channel access procedure..... | 22 | +| 4.2.2 Contention window adjustment procedures ..... | 22 | +| 4.2.2.1 Contention window adjustment procedures for UL transmissions scheduled/configured by eNB ..... | 22 | +| 4.2.2.2 Contention window adjustment procedures for UL transmissions scheduled/configured by gNB..... | 24 | +| 4.2.2.3 Common procedures for CWS adjustments for UL transmissions..... | 25 | +| 4.2.3 Energy detection threshold adaptation procedure ..... | 25 | +| 4.2.3.1 Default maximum energy detection threshold computation procedure ..... | 26 | +| 4.3 Channel access procedures for semi-static channel occupancy ..... | 26 | +| 4.3.1 Channel access procedures to initiate a channel occupancy..... | 27 | +| 4.3.1.1 Channel occupancy initiated only by gNB ..... | 27 | +| 4.3.1.2 Channel occupancy initiated by gNB or UE..... | 27 | +| 4.3.1.2.1 Channel occupancy initiated by gNB and sensing procedures ..... | 27 | +| 4.3.1.2.2 Channel occupancy initiated by UE and sensing procedures..... | 28 | +| 4.3.1.2.3 Association with initiated channel occupancy for configured UL transmissions ..... | 29 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------|-----------| +| 4.3.1.2.4 | Association with initiated channel occupancy for scheduled UL transmissions ..... | 30 | +| 4.3.1.2.4.1 | Intra-period scheduled UL transmissions ..... | 30 | +| 4.3.1.2.4.2 | Cross-period scheduled UL transmissions ..... | 31 | +| 4.3.2 | Channel access related procedures for UL transmissions ..... | 32 | +| 4.3.3 | Channel access procedures for transmission(s) on multiple channels..... | 32 | +| 4.4 | Channel access procedures for frequency range 2-2 ..... | 33 | +| 4.4.1 | Type 1 channel access procedures..... | 34 | +| 4.4.2 | Type 2 channel access procedures..... | 35 | +| 4.4.3 | Type 3 channel access procedures..... | 35 | +| 4.4.4 | Channel access procedures in an initiated channel occupancy..... | 35 | +| 4.4.5 | Exempted transmissions from sensing ..... | 36 | +| 4.4.6 | Channel access procedures for transmission(s) on multiple channels or beams ..... | 36 | +| 4.4.7 | Energy detection threshold adaptation procedures..... | 37 | +| 4.5 | Sidelink Channel access procedures ..... | 37 | +| 4.5.1 | Type 1 SL channel access procedure..... | 38 | +| 4.5.2 | Type 2 SL channel access procedure..... | 39 | +| 4.5.2.1 | Type 2A SL channel access procedure ..... | 39 | +| 4.5.2.2 | Type 2B SL channel access procedure ..... | 39 | +| 4.5.2.3 | Type 2C SL channel access procedure ..... | 40 | +| 4.5.3 | SL channel access procedures in a shared channel occupancy ..... | 40 | +| 4.5.4 | Contention window adjustment procedures for SL transmissions ..... | 41 | +| 4.5.5 | Energy detection threshold adaptation procedure ..... | 42 | +| 4.5.5.1 | Default maximum energy detection threshold computation procedure..... | 43 | +| 4.5.6 | Channel access procedures for transmission(s) on multiple channels..... | 43 | +| 4.5.6.1 | Type A multi-channel access procedures for PSFCH transmissions..... | 44 | +| 4.5.6.1.1 | Type A1 multi-channel access procedures..... | 44 | +| 4.5.6.1.2 | Type A2 multi-channel access procedures..... | 44 | +| 4.5.6.2 | Type B multi-channel access procedures for PSFCH or S-SSB transmissions..... | 44 | +| 4.5.6.2.1 | Type B1 multi-channel access procedure..... | 45 | +| 4.5.6.2.2 | Type B2 multi-channel access procedure..... | 45 | +| 4.5.6.3 | Multi-channel access procedures for SL transmissions ..... | 45 | +| Annex X (informative): | Change history..... | 47 | + +# --- 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 and establishes the characteristics of the physical layer procedures for shared spectrum channel. + +# --- 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 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". +- [3] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [4] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures". +- [5] 3GPP TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding". +- [6] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [7] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [8] 3GPP TS 38.214: "NR; Physical layer procedures for data". +- [9] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". +- [10] 3GPP TS 38.212: "NR; Multiplexing and channel coding". +- [11] 3GPP TS 38.211: "NR; Physical channels and Modulations". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +$CW_p$ Contention window for a given priority class + +| | | +|--------------------------|------------------------------------------------------------------| +| $CW_{\max,p}$ | Maximum contention window for a given priority class | +| $CW_{\min,p}$ | Minimum contention window for a given priority class | +| $T_{mcot,p}$ | Maximum channel occupancy time for a given priority class | +| $T_{ulmcot,p}$ | Maximum Uplink channel occupancy time for a given priority class | +| $X_{\text{Thresh}}$ | Energy detection threshold | +| $X_{\text{Thresh\_max}}$ | Maximum energy detection threshold | + +## 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]. + +| | | +|---------|--------------------------------------------| +| AUL-DFI | Autonomous UL Downlink Feedback Indication | +| CAPC | Channel Access Priority Class | +| COT | Channel Occupancy Time | +| LAA | Licensed Assisted Access | +| MCOT | Maximum Channel Occupancy Time | +| SL | Sidelink | + +# --- 4 Channel access procedure + +## 4.0 General + +Unless otherwise noted, the definitions below are applicable for the following terminologies used in this specification: + +- A channel refers to a carrier or a part of a carrier consisting of a contiguous set of resource blocks (RBs) on which a channel access procedure is performed in shared spectrum. +- A channel access procedure is a procedure based on sensing that evaluates the availability of a channel for performing transmissions. The basic unit for sensing is a sensing slot with a duration $T_{sl} = 9\mu\text{s}$ . The sensing slot duration $T_{sl}$ is considered to be idle if an eNB/gNB or a UE senses the channel during the sensing slot duration, and determines that the detected power for at least $4\mu\text{s}$ within the sensing slot duration is less than energy detection threshold $X_{\text{Thresh}}$ . Otherwise, the sensing slot duration $T_{sl}$ is considered to be busy. +- A *channel occupancy* refers to transmission(s) on channel(s) by eNB/gNB/UE(s) after performing the corresponding channel access procedures in this clause. +- A *Channel Occupancy Time* refers to the total time for which eNB/gNB/UE and any eNB/gNB/UE(s) sharing the channel occupancy perform transmission(s) on a channel after an eNB/gNB/UE performs the corresponding channel access procedures described in this clause. For determining a *Channel Occupancy Time*, if a transmission gap is less than or equal to $25\mu\text{s}$ , the gap duration is counted in the channel occupancy time. A channel occupancy time can be shared for transmission between an eNB/gNB and the corresponding UE(s). +- A *DL transmission burst* is defined as a set of transmissions from an eNB/gNB without any gaps greater than $16\mu\text{s}$ . Transmissions from an eNB/gNB separated by a gap of more than $16\mu\text{s}$ are considered as separate DL transmission bursts. An eNB/gNB can transmit transmission(s) after a gap within a *DL transmission burst* without sensing the corresponding channel(s) for availability. +- A *UL transmission burst* is defined as a set of transmissions from a UE without any gaps greater than $16\mu\text{s}$ . Transmissions from a UE separated by a gap of more than $16\mu\text{s}$ are considered as separate UL transmission bursts. A UE can transmit transmission(s) after a gap within a *UL transmission burst* without sensing the corresponding channel(s) for availability. + +- A *SL transmission burst* is defined as a set of SL transmissions from a UE without any gaps greater than $16\mu\text{s}$ . The SL transmissions from a UE separated by a gap of more than $16\mu\text{s}$ , are considered as separate SL transmission bursts. A UE can transmit SL transmission(s) after a gap within a *SL transmission burst* without sensing the corresponding channel(s) for availability. +- A *discovery burst* refers to a DL transmission burst including a set of signal(s) and/or channel(s) confined within a window and associated with a duty cycle. The *discovery burst* can be any of the following: + - Transmission(s) initiated by an eNB that includes a primary synchronization signal (PSS), secondary synchronization signal (SSS) and cell-specific reference signal(s)(CRS) and may include non-zero power CSI reference signals (CSI-RS). + - Transmission(s) initiated by a gNB that includes at least an SS/PBCH block consisting of a primary synchronization signal (PSS), secondary synchronization signal (SSS), physical broadcast channel (PBCH) with associated demodulation reference signal (DM-RS) and may also include CORESET for PDCCH scheduling PDSCH with SIB1, and PDSCH carrying SIB1 and/or non-zero power CSI reference signals (CSI-RS). + +## 4.1 Downlink channel access procedures + +An eNB operating LAA Scell(s) on channel(s) and a gNB performing transmission(s) on channel(s) shall perform the channel access procedures described in this clause for accessing the channel(s) on which the transmission(s) are performed. + +In this clause, $X_{Thresh}$ for sensing is adjusted as described in clause 4.1.5 when applicable. + +A gNB performs channel access procedures in this clause unless the higher layer parameter *channelAccessMode-r16* is provided and *channelAccessMode-r16* = 'semiStatic'. + +### 4.1.1 Type 1 DL channel access procedures + +This clause describes channel access procedures to be performed by an eNB/gNB where the time duration spanned by the sensing slots that are sensed to be idle before a downlink transmission(s) is random. The clause is applicable to the following transmissions: + +- Transmission(s) initiated by an eNB including PDSCH/PDCCH/EPDCCH, or +- Any transmission(s) initiated by a gNB. + +The eNB/gNB may transmit a transmission after first sensing the channel to be idle during the sensing slot durations of a defer duration $T_d$ and after the counter $N$ is zero in step 4. The counter $N$ is adjusted by sensing the channel for additional sensing slot duration(s) according to the steps below: + +- 1) set $N = N_{init}$ , where $N_{init}$ is a random number uniformly distributed between 0 and $CW_p$ , and go to step 4; +- 2) if $N > 0$ and the eNB/gNB chooses to decrement the counter, set $N = N - 1$ ; +- 3) sense the channel for an additional sensing slot duration, and if the additional sensing slot duration is idle, go to step 4; else, go to step 5; +- 4) if $N = 0$ , stop; else, go to step 2. +- 5) sense the channel until either a busy sensing slot is detected within an additional defer duration $T_d$ or all the sensing slots of the additional defer duration $T_d$ are detected to be idle; +- 6) if the channel is sensed to be idle during all the sensing slot durations of the additional defer duration $T_d$ , go to step 4; else, go to step 5; + +If an eNB/gNB has not transmitted a transmission after step 4 in the procedure above, the eNB/gNB may transmit a transmission on the channel, if the channel is sensed to be idle at least in a sensing slot duration $T_{sl}$ when the eNB/gNB is ready to transmit and if the channel has been sensed to be idle during all the sensing slot durations of a defer duration $T_d$ immediately before this transmission. If the channel has not been sensed to be idle in a sensing slot duration $T_{sl}$ when the eNB/gNB first senses the channel after it is ready to transmit or if the channel has been sensed to be not idle + +during any of the sensing slot durations of a defer duration $T_d$ immediately before this intended transmission, the eNB/gNB proceeds to step 1 after sensing the channel to be idle during the sensing slot durations of a defer duration $T_d$ . + +The defer duration $T_d$ consists of duration $T_f = 16\mu s$ immediately followed by $m_p$ consecutive sensing slot durations $T_{sl}$ , and $T_f$ includes an idle sensing slot duration $T_{sl}$ at start of $T_f$ . + +$CW_{min,p} \leq CW_p \leq CW_{max,p}$ is the contention window. $CW_p$ adjustment is described in clause 4.1.4. + +$CW_{min,p}$ and $CW_{max,p}$ are chosen before step 1 of the procedure above. + +$m_p$ , $CW_{min,p}$ , and $CW_{max,p}$ are based on a channel access priority class $p$ associated with the eNB/gNB transmission, as shown in Table 4.1.1-1. + +An eNB/gNB shall not transmit on a channel for a *Channel Occupancy Time* that exceeds $T_{m cot,p}$ where the channel access procedures are performed based on a channel access priority class $p$ associated with the eNB/gNB transmissions, as given in Table 4.1.1-1. + +If an eNB/gNB transmits discovery burst(s) as described in clause 4.1.2 when $N > 0$ in the procedure above, the eNB/gNB shall not decrement $N$ during the sensing slot duration(s) overlapping with discovery burst(s). + +A gNB may use any channel access priority class for performing the procedures above to transmit transmission(s) including discovery burst(s) satisfying the conditions described in this clause. + +A gNB shall use a channel access priority class applicable to the unicast user plane data multiplexed in PDSCH for performing the procedures above to transmit transmission(s) including unicast PDSCH with user plane data. + +For $p = 3$ and $p = 4$ , if the absence of any other technology sharing the channel can be guaranteed on a long term basis (e.g. by level of regulation), $T_{m cot,p} = 10ms$ , otherwise, $T_{m cot,p} = 8ms$ . + +**Table 4.1.1-1: Channel Access Priority Class (CAPC)** + +| Channel Access Priority Class ( $p$ ) | $m_p$ | $CW_{min,p}$ | $CW_{max,p}$ | $T_{m cot,p}$ | allowed $CW_p$ sizes | +|---------------------------------------|-------|--------------|--------------|---------------|-----------------------------| +| 1 | 1 | 3 | 7 | 2 ms | {3,7} | +| 2 | 1 | 7 | 15 | 3 ms | {7,15} | +| 3 | 3 | 15 | 63 | 8 or 10 ms | {15,31,63} | +| 4 | 7 | 15 | 1023 | 8 or 10 ms | {15,31,63,127,255,511,1023} | + +#### 4.1.1.1 Regional limitations on channel occupancy time + +In Japan, if an eNB/gNB has transmitted a transmission after $N = 0$ in step 4 of the procedure above, the eNB/gNB may transmit the next continuous transmission, for duration of maximum $T_j = 4ms$ , immediately after sensing the channel to be idle for at least a sensing interval of $T_{js} = 34\mu s$ and if the total sensing and transmission time is not more than $1000 \cdot T_{m cot} + \left\lceil \frac{T_{m cot}}{T_j} - 1 \right\rceil \cdot T_{js} \mu s$ . The sensing interval $T_{js}$ consists of duration $T_f = 16\mu s$ immediately followed by two sensing slots and $T_f$ includes an idle sensing slot at start of $T_f$ . The channel is considered to be idle for $T_{js}$ if it is sensed to be idle during the sensing slot durations of $T_{js}$ . + +### 4.1.2 Type 2 DL channel access procedures + +This clause describes channel access procedures to be performed by an eNB/gNB where the time duration spanned by sensing slots that are sensed to be idle before a downlink transmission(s) is deterministic. + +If an eNB performs Type 2 DL channel access procedures, it follows the procedures described in clause 4.1.2.1. + +Type 2A channel access procedures as described in clause 4.1.2.1 are only applicable to the following transmission(s) performed by an eNB/gNB: + +- Transmission(s) initiated by an eNB including discovery burst and not including PDSCH where the transmission(s) duration is at most 1ms, or +- Transmission(s) initiated by a gNB with only discovery burst or with discovery burst multiplexed with non-unicast information, where the transmission(s) duration is at most 1ms, and the discovery burst duty cycle is at most 1/20, or +- Transmission(s) by an eNB/ gNB following transmission(s) by a UE after a gap of 25 $\mu$ s in a shared channel occupancy as described in clause 4.1.3. + +Type 2B or Type 2C DL channel access procedures as described in clause 4.1.2.2 and 4.1.2.3, respectively, are applicable to the transmission(s) performed by a gNB following transmission(s) by a UE after a gap of 16 $\mu$ s or up to 16 $\mu$ s, respectively, in a shared channel occupancy as described in clause 4.1.3. + +#### 4.1.2.1 Type 2A DL channel access procedures + +An eNB/gNB may transmit a DL transmission immediately after sensing the channel to be idle for at least a sensing interval $T_{short\_dl} = 25\mu$ s. $T_{short\_dl}$ consists of a duration $T_f = 16\mu$ s immediately followed by one sensing slot and $T_f$ includes a sensing slot at start of $T_f$ . The channel is considered to be idle for $T_{short\_dl}$ if both sensing slots of $T_{short\_dl}$ are sensed to be idle. + +#### 4.1.2.2 Type 2B DL channel access procedures + +A gNB may transmit a DL transmission immediately after sensing the channel to be idle within a duration of $T_f = 16\mu$ s. $T_f$ includes a sensing slot that occurs within the last 9 $\mu$ s of $T_f$ . The channel is considered to be idle within the duration $T_f$ if the channel is sensed to be idle for a total of at least 5 $\mu$ s with at least 4 $\mu$ s of sensing occurring in the sensing slot. + +#### 4.1.2.3 Type 2C DL channel access procedures + +When a gNB follows the procedures in this clause for transmission of a DL transmission, the gNB does not sense the channel before transmission of the DL transmission. The duration of the corresponding DL transmission is at most 584 $\mu$ s. + +### 4.1.3 DL channel access procedures in a shared channel occupancy + +For the case where an eNB shares a channel occupancy initiated by a UE, the eNB may transmit a transmission that follows an autonomous PUSCH transmission by the UE as follows: + +- If 'COT sharing indication' in AUL-UCI in subframe $n$ indicates '1', an eNB may transmit a transmission in subframe $n + X$ , where $X$ is subframeOffsetCOT-Sharing, including PDCCH but not including PDSCH on the same channel immediately after performing Type 2A DL channel access procedures in clause 4.1.2.1, if the duration of the PDCCH is less than or equal to duration of two OFDM symbols and it shall contain at least AUL-DFI or UL grant to the UE from which the PUSCH transmission indicating COT sharing was received. + +If a gNB shares a channel occupancy initiated by a UE using the channel access procedures described in clause 4.2.1.1 on a channel, the gNB may transmit a transmission that follows a UL transmission on scheduled resources or a PUSCH transmission on configured resources by the UE after a gap as follows: + +- The transmission shall contain transmission to the UE that initiated the channel occupancy and can include non-unicast and/or unicast transmissions where any unicast transmission that includes user plane data is only transmitted to the UE that initiated the channel occupancy. +- If the higher layer parameters *ul-toDL-COT-SharingED-Threshold-r16* is not provided, the transmission shall not include any unicast transmissions with user plane data and the transmission duration is not more than the duration of 2, 4 and 8 symbols for subcarrier spacing of 15, 30 and 60 kHz of the corresponding channel, respectively. +- If the gap is up to 16 $\mu$ s, the gNB can transmit the transmission on the channel after performing Type 2C DL channel access as described in clause 4.1.2.3. + +- If the gap is $25\mu\text{s}$ or $16\mu\text{s}$ , the gNB can transmit the transmission on the channel after performing Type 2A or Type 2B DL channel access procedures as described in clause 4.1.2.1 and 4.1.2.2, respectively. + +For the case where a gNB shares a channel occupancy initiated by a UE with configured grant PUSCH transmission, the gNB may transmit a transmission that follows the configured grant PUSCH transmission by the UE as follows: + +- If the higher layer parameter *ul-toDL-COT-SharingED-Threshold-r16* is provided, the UE is configured by *cg-COT-SharingList-r16* where *cg-COT-SharingList-r16* provides a table configured by higher layer. Each row of the table provides a channel occupancy sharing information given by higher layer parameter *CG-COT-Sharing-r16*. One row of the table is configured for indicating that the channel occupancy sharing is not available. +- If the 'COT sharing information' in CG-UCI detected in slot $n$ indicates a row index that corresponds to a *CG-COT-Sharing-r16* that provides channel occupancy sharing information, the gNB can share the UE channel occupancy assuming a channel access priority class $p = \text{channelAccessPriority-r16}$ , starting from slot $n+O$ , where $O = \text{offset-r16}$ slots, for a duration of $D = \text{duration-r16}$ slots where *duration-r16*, *offset-r16*, and *channelAccessPriority-r16* are higher layer parameters provided by *CG-COT-Sharing-r16*. +- If the higher layer parameter *ul-toDL-COT-SharingED-Threshold-r16* is not provided, and if 'COT sharing information' in CG-UCI indicates '1', the gNB can share the UE channel occupancy and start the DL transmission $X = \text{cg-COT-SharingOffset-r16} * 14$ symbols from the end of the slot where CG-UCI is detected, where *cg-COT-SharingOffset-r16* is provided by higher layer. The transmission shall not include any unicast transmissions with user plane data and the transmission duration is not more than the duration of 2, 4 and 8 symbols for subcarrier spacing of 15, 30 and 60 kHz of the corresponding channel, respectively. + +For the case where a gNB uses channel access procedures as described in clause 4.1.1 to initiate a transmission and shares the corresponding channel occupancy with a UE that transmits a transmission as described in clause 4.2.1.2, the gNB may transmit a transmission within its channel occupancy that follows the UE's transmission if any gap between any two transmissions in the gNB channel occupancy is at most $25\mu\text{s}$ . In this case the following applies: + +- If the gap is $25\mu\text{s}$ or $16\mu\text{s}$ , the gNB can transmit the transmission on the channel after performing Type 2A or 2B DL channel access procedures as described in clause 4.1.2.1 and 4.1.2.2, respectively. +- If the gap is up to $16\mu\text{s}$ , the gNB can transmit the transmission on the channel after performing Type 2C DL channel access as described in clause 4.1.2.3. + +### 4.1.4 Contention window adjustment procedures + +If an eNB/gNB transmits transmissions including PDSCH that are associated with channel access priority class $p$ on a channel, the eNB/gNB maintains the contention window value $CW_p$ and adjusts $CW_p$ before step 1 of the procedure described in clause 4.1.1 for those transmissions as described in this clause. + +#### 4.1.4.1 Contention window adjustment procedures for transmissions by eNB + +If an eNB transmits transmissions including PDSCH that are associated with channel access priority class $p$ on a channel, the eNB maintains the contention window value $CW_p$ and adjusts $CW_p$ before step 1 of the procedure described in clause 4.1.1 for those transmissions using the following steps: + +- 1) for every priority class $p \in \{1,2,3,4\}$ set $CW_p = CW_{min,p}$ +- 2) if at least $Z = 80\%$ of HARQ-ACK values corresponding to PDSCH transmission(s) in reference subframe $k$ are determined as NACK, increase $CW_p$ for every priority class $p \in \{1,2,3,4\}$ to the next higher allowed value and remain in step 2; otherwise, go to step 1. + +Reference subframe $k$ is the starting subframe of the most recent transmission on the channel made by the eNB, for which at least some HARQ-ACK feedback is expected to be available. + +The eNB shall adjust the value of $CW_p$ for every priority class $p \in \{1,2,3,4\}$ based on a given reference subframe $k$ only once. + +For determining $Z$ , + +- if the eNB transmission(s) for which HARQ-ACK feedback is available start in the second slot of subframe $k$ , HARQ-ACK values corresponding to PDSCH transmission(s) in subframe $k + 1$ are also used in addition to the HARQ-ACK values corresponding to PDSCH transmission(s) in subframe $k$ . +- if the HARQ-ACK values correspond to PDSCH transmission(s) on an LAA SCell that are assigned by (E)PDCCH transmitted on the same LAA SCell, + - if no HARQ-ACK feedback is detected for a PDSCH transmission by the eNB, or if the eNB detects 'DTX', 'NACK/DTX' or 'any' state, it is counted as NACK. +- if the HARQ-ACK values correspond to PDSCH transmission(s) on an LAA SCell that are assigned by (E)PDCCH transmitted on another serving cell, + - if the HARQ-ACK feedback for a PDSCH transmission is detected by the eNB, 'NACK/DTX' or 'any' state is counted as NACK, and 'DTX' state is ignored. + - if no HARQ-ACK feedback is detected for a PDSCH transmission by the eNB + - if PUCCH format 1b with channel selection is expected to be used by the UE, 'NACK/DTX' state corresponding to 'no transmission' as described in Clauses 10.1.2.2.1, 10.1.3.1 and 10.1.3.2.1 is counted as NACK, and 'DTX' state corresponding to 'no transmission' is ignored in [4]. + - Otherwise, the HARQ-ACK for the PDSCH transmission is ignored. +- if a PDSCH transmission has two codewords, the HARQ-ACK value of each codeword is considered separately +- bundled HARQ-ACK across $M$ subframes is considered as $M$ HARQ-ACK responses. + +If the eNB transmits transmissions including PDCCH/EPDCCH with DCI format 0A/0B/4A/4B and not including PDSCH that are associated with channel access priority class $p$ on a channel starting from time $t_0$ , the eNB maintains the contention window value $CW_p$ and adjusts $CW_p$ before step 1 of the procedure described in clause 4.1.1 for those transmissions using the following steps: + +- 1) for every priority class $p \in \{1,2,3,4\}$ set $CW_p = CW_{min,p}$ +- 2) if less than 10% of the UL transport blocks scheduled by the eNB using Type 2 channel access procedure (described in clause 4.2.1.2) in the time interval between $t_0$ and $t_0 + T_{co}$ have been received successfully, increase $CW_p$ for every priority class $p \in \{1,2,3,4\}$ to the next higher allowed value and remain in step 2; otherwise, go to step 1. + +$T_{co}$ is computed as described in clause 4.2.1.0.3. + +#### 4.1.4.2 Contention window adjustment procedures for DL transmissions by gNB + +If a gNB transmits transmissions including PDSCH that are associated with channel access priority class $p$ on a channel, the gNB maintains the contention window value $CW_p$ and adjusts $CW_p$ before step 1 of the procedure described in clause 4.1.1 for those transmissions using the following steps: + +- 1) For every priority class $p \in \{1,2,3,4\}$ , set $CW_p = CW_{min,p}$ . +- 2) If HARQ-ACK feedback is available after the last update of $CW_p$ , go to step 3. Otherwise, if the gNB transmission after procedure described in clause 4.1.1 does not include a retransmission or would be transmitted within a duration $T_w$ from the end of the *reference duration* corresponding to the earliest DL channel occupancy after the last update of $CW_p$ , go to step 5; otherwise go to step 4. +- 3) The HARQ-ACK feedback(s) corresponding to PDSCH(s) in the reference duration for the latest DL channel occupancy for which HARQ-ACK feedback is available is used as follows: + - a. If at least one HARQ-ACK feedback is 'ACK' for PDSCH(s) with transport block based feedback or at least 10% of HARQ-ACK feedbacks is 'ACK' for PDSCH CBGs transmitted at least partially on the channel with code block group based feedback, go to step 1; otherwise go to step 4. +- 4) Increase $CW_p$ for every priority class $p \in \{1,2,3,4\}$ to the next higher allowed value. + +- 5) For every priority class $p \in \{1,2,3,4\}$ , maintain $CW_p$ as it is; go to step 2. + +The *reference duration* and duration $T_w$ in the procedure above are defined as follows: + +- The *reference duration* corresponding to a channel occupancy initiated by the gNB including transmission of PDSCH(s) is defined in this clause as a duration starting from the beginning of the channel occupancy until the end of the first slot where at least one unicast PDSCH is transmitted over all the resources allocated for the PDSCH, or until the end of the first transmission burst by the gNB that contains unicast PDSCH(s) transmitted over all the resources allocated for the PDSCH, whichever occurs earlier. If the channel occupancy includes a unicast PDSCH, but it does not include any unicast PDSCH transmitted over all the resources allocated for that PDSCH, then, the duration of the first transmission burst by the gNB within the channel occupancy that contains unicast PDSCH(s) is the *reference duration* for CWS adjustment. +- $T_w = \max(T_A, T_B + 1ms)$ where $T_B$ is the duration of the transmission burst from start of the *reference duration* in $ms$ and $T_A = 5ms$ if the absence of any other technology sharing the channel cannot be guaranteed on a long-term basis (e.g. by level of regulation), and $T_A = 10ms$ otherwise. + +If a gNB transmits transmissions using Type 1 channel access procedures associated with the channel access priority class $p$ on a channel and the transmissions are not associated with explicit HARQ-ACK feedbacks by the corresponding UE(s), the gNB adjusts $CW_p$ before step 1 in the procedures described in clause 4.1.1, using the latest $CW_p$ used for any DL transmissions on the channel using Type 1 channel access procedures associated with the channel access priority class $p$ . If the corresponding channel access priority class $p$ has not been used for any DL transmissions on the channel, $CW_p = CW_{min,p}$ is used. + +#### 4.1.4.3 Common procedures for CWS adjustments for DL transmissions + +The following applies to the procedures described in clauses 4.1.4.1 and 4.1.4.2: + +- If $CW_p = CW_{max,p}$ , the next higher allowed value for adjusting $CW_p$ is $CW_{max,p}$ . +- If the $CW_p = CW_{max,p}$ is consecutively used $K$ times for generation of $N_{init}$ , $CW_p$ is reset to $CW_{min,p}$ only for that priority class $p$ for which $CW_p = CW_{max,p}$ is consecutively used $K$ times for generation of $N_{init}$ . $K$ is selected by eNB/gNB from the set of values $\{1, 2, \dots, 8\}$ for each priority class $p \in \{1,2,3,4\}$ . + +### 4.1.5 Energy detection threshold adaptation procedures + +An eNB/gNB accessing a channel on which transmission(s) are performed, shall set the energy detection threshold ( $X_{Thresh}$ ) to be less than or equal to the maximum energy detection threshold $X_{Thresh\_max}$ . + +$X_{Thresh\_max}$ is determined as follows: + +- If the absence of any other technology sharing the channel can be guaranteed on a long-term basis (e.g. by level of regulation) then: + - $$X_{Thresh\_max} = \min \left\{ \begin{matrix} T_{max} + 10dB, \\ X_r \end{matrix} \right\}$$ + - $X_r$ is maximum energy detection threshold defined by regulatory requirements in dBm when such requirements are defined, otherwise $X_r = T_{max} + 10dB$ ; + - otherwise, + - $$X_{Thresh\_max} = \max \left\{ \begin{matrix} X_{reg} \\ \min \left\{ \begin{matrix} T_{max}, \\ T_{max} - T_A + (P_H + 10 \cdot \log 10(BW MHz / 20 MHz) - P_{TX}) \end{matrix} \right\} \end{matrix} \right\}$$ + +where: + +In regulatory regions and bands where it is allowed, + +- $X_{reg} = -67 + 10 \cdot \log 10(BW MHz / 20 MHz)$ dBm; +- $T_A = 5dB$ for all transmissions; + +- $P_H = 23\text{dBm}$ ; + +Otherwise, + +- $X_{reg} = -72 + 10 \cdot \log_{10}(BW\text{MHz} / 20\text{MHz})\text{dBm}$ ; +- $T_A = 5\text{dB}$ for transmissions including discovery burst(s) as described in clause 4.1.2, and $T_A = 10\text{dB}$ otherwise; +- $P_H = 23\text{dBm}$ or in regions and bands where regulations allow, $24\text{dBm}$ ; +- $P_{TX}$ is set to the maximum eNB/gNB output power in dBm for the channel; +- eNB/gNB uses the set maximum transmission power over a single channel irrespective of whether single channel or multi-channel transmission is employed +- $T_{\max}(\text{dBm}) = 10 \cdot \log_{10}(3.16228 \cdot 10^{-8}(\text{mW/MHz}) \cdot BW\text{MHz} (\text{MHz}))$ ; +- $BW\text{MHz}$ is the single channel bandwidth in MHz. + +### 4.1.6 Channel access procedures for transmission(s) on multiple channels + +An eNB/gNB can access multiple channels on which transmission(s) are performed, according to one of the Type A or Type B procedures described in this Clause. + +#### 4.1.6.1 Type A multi-channel access procedures + +An eNB/gNB shall perform channel access on each channel $c_i \in C$ , according to the procedures described in clause 4.1.1, where $C$ is a set of channels on which the eNB/gNB intends to transmit, and $i = 0, 1, \dots, q-1$ , and $q$ is the number of channels on which the eNB/gNB intends to transmit. + +The counter $N$ described in clause 4.1.1 is determined for each channel $c_i$ and is denoted as $N_{c_i}$ . $N_{c_i}$ is maintained according to clause 4.1.6.1.1 or 4.1.6.1.2. + +If a gNB configures a carrier without intra-cell guard bands as described in clause 7 in [8], the gNB may not transmit on channel $c_i \in C$ within the bandwidth of the carrier, if the gNB fails to access any of the channels of the carrier bandwidth. + +##### 4.1.6.1.1 Type A1 multi-channel access procedures + +Counter $N$ as described in clause 4.1.1 is independently determined for each channel $c_i$ and is denoted as $N_{c_i}$ . + +If the absence of any other technology sharing the channel cannot be guaranteed on a long term basis (e.g. by level of regulation), when the eNB/gNB ceases transmission on any one channel $c_j \in C$ , for each channel $c_i \neq c_j$ , the eNB/gNB can resume decrementing $N_{c_i}$ when idle sensing slots are detected either after waiting for a duration of $4 \cdot T_{sl}$ , or after reinitializing $N_{c_i}$ . + +For determining $CW_p$ for channel $c_i$ , any PDSCH that fully or partially overlaps with channel $c_i$ , is used in the procedures described in clause 4.1.4.2. + +##### 4.1.6.1.2 Type A2 multi-channel access procedures + +Counter $N$ is determined as described in clause 4.1.1 for channel $c_j \in C$ , and is denoted as $N_{c_j}$ , where $c_j$ is the channel that has the largest $CW_p$ value. For each channel $c_i$ , $N_{c_i} = N_{c_j}$ . + +When the eNB/gNB ceases transmission on any one channel for which $N_{c_i}$ is determined, the eNB/gNB shall reinitialize $N_{c_i}$ for all channels. + +For determining $CW_p$ for channel $c_i$ , any PDSCH that fully or partially overlaps with channel $c_i$ , is used in the procedures described in clause 4.1.4.2. + +#### 4.1.6.2 Type B multi-channel access procedure + +A channel $c_j \in C$ is selected by the eNB/gNB as follows: + +- the eNB/gNB selects $c_j$ by uniformly randomly choosing $c_j$ from $C$ before each transmission on multiple channels $c_i \in C$ , or +- the eNB/gNB selects $c_j$ no more frequently than once every 1 second, + +where $C$ is a set of channels on which the eNB/gNB intends to transmit, $i = 0, 1, \dots, q-1$ , and $q$ is the number of channels on which the eNB intends to transmit. + +To transmit on channel $c_j$ + +- the eNB/gNB shall perform channel access on channel $c_j$ according to the procedures described in clause 4.1.1 with the modifications described in clause 4.1.6.2.1 or 4.1.6.2.2. + +To transmit on channel $c_i \neq c_j$ , $c_i \in C$ + +- for each channel $c_i$ , the eNB/gNB shall sense the channel $c_i$ for at least a sensing interval $T_{mc} = 25\mu s$ immediately before transmitting on channel $c_j$ , and the eNB/gNB may transmit on channel $c_i$ immediately after sensing the channel $c_i$ to be idle for at least the sensing interval $T_{mc}$ . The channel $c_i$ is considered to be idle for $T_{mc}$ if the channel is sensed to be idle during all the time durations in which such idle sensing is performed on the channel $c_j$ in given interval $T_{mc}$ . + +The eNB/gNB shall not transmit a transmission on a channel $c_i \neq c_j$ , $c_i \in C$ , for a period exceeding $T_{mcot,p}$ as given in Table 4.1.1-1, where the value of $T_{mcot,p}$ is determined using the channel access parameters used for channel $c_j$ . + +For the procedures in this clause, the channel frequencies of the set of channels $C$ selected by gNB, is a subset of one of the sets of channel frequencies defined in [6]. + +If a gNB configures a carrier without intra-cell guard band(s) as described in clause 7 in [8], the gNB may not transmit on channel $c_i \in C$ within the bandwidth of the carrier, if the gNB fails to access any of the channels of the carrier bandwidth. + +##### 4.1.6.2.1 Type B1 multi-channel access procedure + +A single $CW_p$ value is maintained for the set of channels $C$ . + +For determining $CW_p$ for channel access on channel $c_j$ , step 2 of the procedure described in clause 4.1.4.1 is modified as follows + +- if at least $Z = 80\%$ of HARQ-ACK values corresponding to PDSCH transmission(s) in reference subframe $k$ of all channels $c_i \in C$ are determined as NACK, increase $CW_p$ for each priority class $p \in \{1, 2, 3, 4\}$ to the next higher allowed value; otherwise, go to step 1. + +For determining $CW_p$ for a set of channels $C$ , any PDSCH that fully or partially overlaps with any channel $c_i \in C$ , is used in the procedure described in clause 4.1.4.2. + +##### 4.1.6.2.2 Type B2 multi-channel access procedure + +A $CW_p$ value is maintained independently for each channel $c_i \in C$ using the procedure described in clause 4.1.4. + +For determining $CW_p$ for channel $c_i$ , any PDSCH that fully or partially overlaps with channel $c_i$ , is used in the procedure described in clause 4.1.4.2. + +For determining $N_{init}$ for channel $c_j$ , $CW_p$ value of channel $c_{j1} \in C$ is used, where $c_{j1}$ is the channel with largest $CW_p$ among all channels in set $C$ . + +## 4.2 Uplink channel access procedures + +A UE performing transmission(s) on LAA Scell(s), an eNB scheduling or configuring UL transmission(s) for a UE performing transmission(s) on LAA Scell(s), and a UE performing transmission(s) on channel(s) and a gNB scheduling or configuring UL transmission(s) for a UE performing transmissions on channel(s) shall perform the procedures described in this clause for the UE to access the channel(s) on which the transmission(s) are performed. + +In this clause, transmissions from a UE are considered as separate UL transmissions, irrespective of having a gap between transmissions or not, and $X_{\text{Thresh}}$ for sensing is adjusted as described in clause 4.2.3 when applicable. + +A UE performs channel access procedures in this clause unless the higher layer parameter *channelAccessMode-r16* is provided and *channelAccessMode-r16* = 'semiStatic'. + +If a UE fails to access the channel(s) prior to an intended UL transmission to a gNB, Layer 1 notifies higher layers about the channel access failure. + +### 4.2.1 Channel access procedures for uplink transmission(s) + +A UE can access a channel on which UL transmission(s) are performed according to one of Type 1 or Type 2 UL channel access procedures. Type 1 channel access procedure is described in clause 4.2.1.1. Type 2 channel access procedure is described in clause 4.2.1.2. + +If a UL grant scheduling a PUSCH transmission indicates Type 1 channel access procedures, the UE shall use Type 1 channel access procedures for transmitting transmissions including the PUSCH transmission unless stated otherwise in this clause. + +A UE shall use Type 1 channel access procedures for transmitting transmissions including the autonomous or configured grant PUSCH transmission on configured UL resources unless stated otherwise in this clause. + +If a UL grant scheduling a PUSCH transmission indicates Type 2 channel access procedures, the UE shall use Type 2 channel access procedures for transmitting transmissions including the PUSCH transmission unless stated otherwise in this clause. + +A UE shall use Type 1 channel access procedures for transmitting SRS transmissions not including a PUSCH transmission. UL channel access priority class $p = 1$ in Table 4.2.1-1 is used for SRS transmissions not including a PUSCH. + +If a DL assignment triggering SRS but not scheduling a PUCCH transmission indicates Type 2 channel access procedures, the UE shall use Type 2 channel access procedures. + +If a UE is scheduled by an eNB/gNB to transmit PUSCH and SRS in contiguous transmissions without any gaps in between, and if the UE cannot access the channel for PUSCH transmission, the UE shall attempt to make SRS transmission according to uplink channel access procedures specified for SRS transmission. + +If a UE is scheduled by a gNB to transmit PUSCH and one or more SRSs by a single UL grant in non-contiguous transmissions, or a UE is scheduled by a gNB to transmit PUCCH and/or SRSs by a single DL assignment in non-contiguous transmissions, the UE shall use the channel access procedure indicated by the scheduling DCI for the first UL transmission scheduled by the scheduling DCI. If the channel is sensed by the UE to be continuously idle after the UE has stopped transmitting the first transmission, the UE may transmit further UL transmissions scheduled by the scheduling DCI using Type 2 channel access procedures or Type 2A UL channel access procedures without applying a CP extension if the further UL transmissions are within the gNB Channel Occupancy Time. Otherwise, if the channel sensed by the UE is not continuously idle after the UE has stopped transmitting the first UL transmission or the further UL transmissions are outside the gNB Channel Occupancy Time, the UE may transmit the further UL transmissions using Type 1 channel access procedure, without applying a CP extension. + +A UE shall use Type 1 channel access procedures for PUCCH transmissions unless stated otherwise in this clause. If a DL grant determined according to Clause 9.2.3 in [7, TS38.213] or a random access response (RAR) message for successRAR scheduling a PUCCH transmission indicates Type 2 channel access procedures, the UE shall use Type 2 channel access procedures. + +When a UE uses Type 1 channel access procedures for PUCCH transmissions or PUSCH only transmissions without UL-SCH, the UE shall use UL channel access priority class $p = 1$ in Table 4.2.1-1. + +A UE shall use Type 1 channel access procedure for PRACH transmissions and PUSCH transmissions without user plane data related to random access procedure that initiate a channel occupancy. In this case, UL channel access priority class $p = 1$ in Table 4.2.1-1 is used for PRACH transmissions, and UL channel access priority class used for PUSCH transmissions is determined according to Clause 5.6.2 in [9]. + +When a UE uses Type 1 channel access procedures for PUSCH transmissions on configured resource, the UE determines the corresponding UL channel access priority $p$ in Table 4.2.1-1 following the procedures described in Clause 5.6.2 in [9]. + +When a UE uses Type 1 channel access procedures for PUSCH transmissions with user plane data indicated by a UL grant or related to random access procedure where the corresponding UL channel access priority $p$ is not indicated, the UE determines $p$ in Table 4.2.1-1 following the same procedures as for PUSCH transmission on configured resources using Type 1 channel access procedures. + +When a UE uses Type 2A, Type 2B, or Type 2C UL channel access procedures for PUSCH transmissions indicated by a UL grant or related to random access procedures, where the corresponding UL channel access priority $p$ is not indicated, the UE assumes that the channel access priority class $p = 4$ is used by the gNB for the *Channel Occupancy Time*. + +A UE shall not transmit on a channel for a *Channel Occupancy Time* that exceeds $T_{ulm\ cot,p}$ where the channel access procedure is performed based on the channel access priority class $p$ associated with the UE transmissions, as given in Table 4.2.1-1. + +The total *Channel Occupancy Time* of autonomous uplink transmission(s) obtained by the channel access procedure in this clause, including the following DL transmission if the UE sets 'COT sharing indication' in AUL-UCI to '1' in a subframe within the autonomous uplink transmission(s) as described in Clause 4.1.3, shall not exceed $T_{ulm\ cot,p}$ , where $T_{ulm\ cot,p}$ is given in Table 4.2.1-1. + +**Table 4.2.1-1: Channel Access Priority Class (CAPC) for UL** + +| Channel Access Priority Class ( $p$ ) | $m_p$ | $CW_{min,p}$ | $CW_{max,p}$ | $T_{ulm\ cot,p}$ | allowed $CW_p$ sizes | +|---------------------------------------|-------|--------------|--------------|------------------|-----------------------------| +| 1 | 2 | 3 | 7 | 2 ms | {3,7} | +| 2 | 2 | 7 | 15 | 4 ms | {7,15} | +| 3 | 3 | 15 | 1023 | 6ms or 10 ms | {15,31,63,127,255,511,1023} | +| 4 | 7 | 15 | 1023 | 6ms or 10 ms | {15,31,63,127,255,511,1023} | + +NOTE1: For $p = 3,4$ , $T_{ulm\ cot,p} = 10ms$ if the higher layer parameter *absenceOfAnyOtherTechnology-r14* or *absenceOfAnyOtherTechnology-r16* is provided , otherwise, $T_{ulm\ cot,p} = 6ms$ . +NOTE 2: When $T_{ulm\ cot,p} = 6ms$ it may be increased to $8ms$ by inserting one or more gaps. The minimum duration of a gap shall be $100\mu s$ . The maximum duration before including any such gap shall be $6ms$ . + +#### 4.2.1.0 Channel access procedures and UL related signaling + +#### 4.2.1.0.0 Channel access procedures upon detection of a common DCI + +If a UE detects 'UL duration and offset' field in DCI Format 1C as described in clause 5.3.3.1.4 of [5], the following are applicable: + +- If the 'UL duration and offset' field indicates an 'UL offset' $l$ and an 'UL duration' $d$ for subframe $n$ , then the scheduled UE may use channel access procedures Type 2 for transmissions in subframes $n + l + i$ where $i = 0, 1, \dots, d - 1$ , irrespective of the channel access Type signalled in the UL grant for those subframes, if the end of UE transmission occurs in or before subframe $n + l + d - 1$ . +- If the 'UL duration and offset' field indicates an 'UL offset' $l$ and an 'UL duration' $d$ for subframe $n$ and the 'COT sharing indication for AUL' field is set to '1', then a UE configured with autonomous UL may use channel access procedures Type 2 for autonomous UL transmissions assuming any priority class in subframes $n + l + i$ where $i = 0, 1, \dots, d - 1$ , if the end of UE autonomous UL transmission occurs in or before subframe $n + l + d - 1$ and the autonomous UL transmission between $n + l$ and $n + l + d - 1$ shall be contiguous. + +- If the 'UL duration and offset' field indicates an 'UL offset' $l$ and an 'UL duration' $d$ for subframe $n$ and the 'COT sharing indication for AUL' field is set to '0', then a UE configured with autonomous UL shall not transmit autonomous UL in subframes $n + l + i$ where $i = 0, 1, \dots, d - 1$ . + +If a UE determines the duration in time domain and the location in frequency domain of a remaining channel occupancy initiated by the gNB from a DCI format 2\_0 as described in clause 11.1.1 of [7], the following is applicable: + +- The UE may switch from Type 1 channel access procedures as described in clause 4.2.1.1 to Type 2A channel access procedures as described in clause 4.2.1.2.1 for its corresponding UL transmissions within the determined duration in time and location in frequency domain of the remaining channel occupancy. In this case, if the UL transmissions are PUSCH transmissions on configured resources, the UE may assume any priority class for the channel occupancy shared with the gNB. + +##### 4.2.1.0.1 Channel access procedures for consecutive UL transmission(s) + +For contiguous UL transmission(s), the following are applicable: + +- If a UE is scheduled to transmit a set of UL transmissions using one or more UL grant(s) or DL assignment(s), and + - if the UE cannot access the channel for a transmission in the set prior to the last transmission according to one of Type 1, Type 2, or Type 2A UL channel access procedures, the UE shall attempt to transmit the next transmission according to the channel access type indicated in the corresponding UL grant or DL assignment. + - if the UE cannot access the channel for a transmission in the set prior to the last transmission according to Type 2B UL channel access procedure, the UE shall attempt to transmit the next transmission according to Type 2A UL channel access procedure. +- If a UE is scheduled by a gNB to transmit a set of UL transmissions including PUSCH or SRS symbol(s) using a UL grant, the UE shall not apply a CP extension for the remaining UL transmissions in the set after the first UL transmission after accessing the channel. +- If a UE is scheduled to transmit a set of consecutive UL transmissions without gaps including PUSCH using one or more UL grant(s), PUCCH using one or more DL grant(s), or SRS with one or more DL grant(s) or UL grant(s) and the UE transmits one of the scheduled UL transmissions in the set after accessing the channel according to one of Type 1, Type 2, Type 2A, Type 2B or Type 2C UL channel access procedures, the UE may continue transmission of the remaining UL transmissions in the set, if any. +- If a UE is configured to transmit a set of consecutive PUSCH or SRS transmissions on resources configured by the gNB, the time domain resource configuration defines multiple transmission occasions, and if the UE cannot access the channel according to Type 1 UL channel access procedure for transmitting in a transmission occasion prior to the last transmission occasion, the UE shall attempt to transmit in the next transmission occasion according to Type 1 UL channel access procedure. If the UE transmits in one of the multiple transmission occasions after accessing the channel according to Type 1 UL channel access procedure, the UE may continue transmission in the remaining transmission occasions in the set, wherein each transmission occasion starts at the starting symbol of a configured grant PUSCH within the duration of the COT. +- If a UE is configured by the gNB to transmit a set of consecutive UL transmissions without gaps including PUSCH, periodic PUCCH, or periodic SRS and the UE transmits one of the configured UL transmissions in the set after accessing the channel according to Type 1 UL channel access procedures, the UE may continue transmission of the remaining UL transmissions in the set, if any. +- A UE is not expected to be indicated with different channel access types for any consecutive UL transmissions without gaps in between the transmissions, except if Type 2B or Type 2C UL channel access procedures are identified for the first of the consecutive UL transmissions. + +For UL transmission(s) with multiple starting positions scheduled by eNB, the following are applicable: + +- If a UE is scheduled by an eNB to transmit transmissions including PUSCH Mode 1 using the Type 1 channel access procedure indicated in DCI, and if the UE cannot access the channel for a transmission according to the PUSCH starting position indicated in the DCI, the UE shall attempt to make a transmission at symbol 7 in the same subframe according to Type 1 channel access procedure. There is no limit on the number of attempts the UE can make using Type 1 channel access procedure. + +- If a UE is scheduled by an eNB to transmit transmissions including PUSCH Mode 1 using the Type 2 channel access procedure indicated in DCI, and if the UE cannot access the channel for a transmission according to the PUSCH starting position indicated in the DCI, the UE may attempt to make a transmission at symbol 7 in the same subframe and according to Type 2 channel access procedure. The number of attempts the UE should make within the consecutively scheduled subframes including the transmission is limited to $w + 1$ , where $w$ is the number of consecutively scheduled subframes using Type 2 channel access procedure. + +For contiguous UL transmissions(s) including a transmission pause, the following are applicable: + +- If a UE is scheduled to transmit a set of consecutive UL transmissions without gaps using one or more UL grant(s), and if the UE has stopped transmitting during or before one of these UL transmissions in the set and prior to the last UL transmission in the set, and if the channel is sensed by the UE to be continuously idle after the UE has stopped transmitting, the UE may transmit a later UL transmission in the set using Type 2 channel access procedures or Type 2A UL channel access procedures without applying a CP extension. +- If a channel sensed by a UE is not continuously idle after the UE has stopped transmitting, the UE may transmit a later UL transmission in the set using Type 1 channel access procedure with the UL channel access priority class indicated in the DCI corresponding to the UL transmission. + +For UL transmission(s) following autonomous UL transmission(s), the following are applicable: + +- If a UE is scheduled by an eNB to transmit on channel $c_i$ by a UL grant received on channel $c_j$ , $i \neq j$ , and if the UE is transmitting using autonomous UL on channel $c_i$ , the UE shall terminate the ongoing PUSCH transmissions using the autonomous UL at least one subframe before the UL transmission according to the received UL grant. +- If a UE is scheduled by a UL grant received from an eNB on a channel to transmit a PUSCH transmission(s) starting from subframe $n$ on the same channel using Type 1 channel access procedure and if at least for the first scheduled subframe occupies $N_{RB}^{UL}$ resource blocks and the indicated PUSCH starting position is OFDM symbol zero, and if the UE starts autonomous UL transmissions before subframe $n$ using Type 1 channel access procedure on the same channel, the UE may transmit UL transmission(s) according to the received UL grant from subframe $n$ without a gap, if the priority class value of the performed channel access procedure is larger than or equal to priority class value indicated in the UL grant, and the autonomous UL transmission in the subframe preceding subframe $n$ shall end at the last OFDM symbol of the subframe regardless of the higher layer parameter *endingSymbolAUL*. The sum of the lengths of the autonomous UL transmission(s) and the scheduled UL transmission(s) shall not exceed the maximum channel occupancy time corresponding to the priority class value used to perform the autonomous uplink channel access procedure. Otherwise, the UE shall terminate the ongoing autonomous UL transmission at least one subframe before the start of the UL transmission according to the received UL grant on the same channel. + +For UL transmission(s) following configured grant UL transmission(s), the following are applicable: + +- If a UE is scheduled to transmit UL transmission(s) starting from symbol $i$ in slot $n$ using Type 1 channel access procedures without CP extension with a corresponding CAPC, and if the UE starts configured grant UL transmissions before symbol $i$ in slot $n$ using Type 1 channel access procedures with a corresponding CAPC, and the scheduled UL transmission(s) occupies all the RBs of the same channels occupied by the configured grant UL transmission(s) or all the RBs of a subset thereof, the UE may directly continue to transmit the scheduled UL transmission(s) to the corresponding CAPC from symbol $i$ in slot $n$ without a gap, if the CAPC value of the performed channel access procedure is larger than or equal to the CAPC value corresponding to the scheduled UL transmission(s). The sum of the transmission durations of the configured grant UL transmission(s) and the scheduled UL transmission(s) shall not exceed the MCOT duration corresponding to the CAPC value used to transmit the configured grant UL transmission(s). Otherwise, the UE shall terminate the configured grant UL transmission(s) by dropping the transmission on the symbols of at least the last configured grant UL transmission before symbol $i$ in slot $n$ and attempt to transmit the scheduled UL transmission(s) according to the corresponding CAPC. The symbols of the PUSCH transmission with a configured grant in a slot is dropped according to the mechanism in Clause 11.1 of [7, TS 38.213] relative to a last symbol of a CORESET where the UE detected the scheduling DCI. In this case, if the UE cannot terminate the configured grant UL transmission(s), the UE ignores the scheduling DCI. + +##### 4.2.1.0.2 Conditions for maintaining Type 1 UL channel access procedures + +If a UE receives a DCI indicating a UL grant scheduling a PUSCH transmission using Type 1 channel access procedures or indicating a DL assignment scheduling a PUCCH transmission using Type 1 channel access procedures, + +and if the UE has an ongoing Type 1 channel access procedures before the PUSCH or PUCCH transmission starting time: + +- If the UL channel access priority class value $p_1$ used for the ongoing Type 1 channel access procedures is same or larger than the UL channel access priority class value $p_2$ indicated in the DCI, the UE may transmit the PUSCH transmission in response to the UL grant by accessing the channel by using the ongoing Type 1 channel access procedure. +- If the UL channel access priority class value $p_1$ used for the ongoing Type 1 channel access procedure is smaller than the UL channel access priority class value $p_2$ indicated in the DCI, the UE shall terminate the ongoing channel access procedure. +- The UE may transmit the PUCCH transmission in response to the DL grant by accessing the channel by using the ongoing Type 1 channel access procedures. + +##### 4.2.1.0.3 Conditions for indicating Type 2 channel access procedures + +An eNB/gNB may indicate Type 2 channel access procedures in the DCI of a UL grant or DL assignment scheduling transmission(s) including PUSCH on one or more channels or PUCCH on a channel, respectively, as follows: + +If the UL transmissions occur within the time interval starting at $t_0$ and ending at $t_0 + T_{CO}$ , where + +- $T_{CO} = T_{m,cot,p} + T_g$ , +- $t_0$ is the time instant when the eNB/gNB has started transmission on the carrier according to the channel access procedure described in clause 4.1.1, +- $T_{m,cot,p}$ value is determined by the eNB/gNB as described in clause 4.1.1, +- $T_g$ is the total duration of all gaps of duration greater than $25\mu s$ that occur between the DL transmissions of the eNB/gNB and UL transmissions scheduled by the eNB/gNB, and between any two UL transmissions scheduled by the eNB/gNB starting from $t_0$ , + +then, + +- the eNB/gNB may indicate Type 2 channel access procedures in the DCI if the eNB/gNB has transmitted on the channel(s) according to the channel access procedures described in clause 4.1.1 or the multi-channel access procedures in clause 4.1.6, or +- the eNB may indicate using the 'UL duration and offset' field that the UE may perform a Type 2 channel access procedure for transmissions(s) including PUSCH on a channel in a subframe $n$ when the eNB has transmitted on the channel according to the channel access procedure described in clause 4.1.1, or +- the eNB may indicate using the 'UL duration and offset' field and 'COT sharing indication for AUL' field that a UE configured with autonomous UL may perform a Type 2 channel access procedure for autonomous UL transmissions(s) including PUSCH on a channel in subframe $n$ when the eNB has transmitted on the channel according to the channel access procedure described in clause 4.1.1 and acquired the channel using the largest priority class value and the eNB transmission includes PDSCH, or +- the eNB/gNB may schedule UL transmissions on a channel, that follow a transmission by the eNB/gNB on that channel with Type 2A channel access procedures for the UL transmissions as described in clause 4.2.1.2.1 after a duration of $25\mu s$ . + +The eNB/gNB shall schedule UL transmissions between $t_0$ and $t_0 + T_{CO}$ without gaps between consecutive UL transmissions if they can be scheduled contiguously. For a UL transmission on a channel that follows a transmission by the eNB/gNB on that channel using Type 2A channel access procedures as described in clause 4.2.1.2.1, the UE may use Type 2A channel access procedure for the UL transmission. + +If the eNB/gNB indicates Type 2 channel access procedure for the UE in the DCI, the eNB/gNB indicates the channel access priority class used to obtain access to the channel in the DCI. + +For indicating a Type 2 channel access procedure, if the gap is at least $25\mu s$ , or equal to $16\mu s$ , or up to $16\mu s$ , the gNB may indicate Type 2A, or Type 2B, or Type 2C UL channel procedures, respectively, as described in clauses 4.2.1.2. + +##### 4.2.1.0.4 Channel access procedures for UL multi-channel transmission(s) + +If a UE + +- is scheduled to transmit on a set of channels $\mathcal{C}$ , and if the UL transmissions are scheduled to start transmissions at the same time on all channels in the set of channels $\mathcal{C}$ , or +- intends to perform an uplink transmission on configured resources on the set of channels $\mathcal{C}$ , and if UL transmissions are configured to start transmissions at the same time on all channels in the set of channels $\mathcal{C}$ , + +the following is applicable: + +- if Type 1 channel access procedure is indicated or intended for the scheduled or configured UL transmissions, respectively, to be transmitted on the set of channels $\mathcal{C}$ , +- the UE may transmit on channel $c_i \in \mathcal{C}$ using Type 2A channel access procedure as described in clause 4.2.1.2.1, + - if the channel frequencies of the set of channels $\mathcal{C}$ is a subset of the sets of channel frequencies defined in clause 5.7.4 in [2], and + - if Type 2A channel access procedure is performed on channel $c_i$ immediately before the UE transmission on channel $c_j \in \mathcal{C}$ , $i \neq j$ , and + - if the UE has accessed channel $c_j$ using Type 1 channel access procedure as described in clause 4.2.1.1, + - where channel $c_j$ is selected by the UE uniformly randomly from the set of channels $\mathcal{C}$ before performing Type 1 channel access procedure on any channel in the set of channels $\mathcal{C}$ . +- the UE may transmit on channel $c_i \in \mathcal{C}$ using Type 1 channel access procedure as described in clause 4.2.1.1 +- the UE may not transmit on channel $c_i \in \mathcal{C}$ within the bandwidth of a carrier, if the UE fails to access any of the channels, of the carrier bandwidth, on which the UE is scheduled or configured with UL resources. +- the UE may not transmit on a channel within the bandwidth of a carrier if the UE is configured without intra-cell guard band(s) on an UL bandwidth part as described in clause 7 of [8], and the UE fails to access any of the channels of the UL bandwidth part. + +#### 4.2.1.1 Type 1 UL channel access procedure + +This clause describes channel access procedures by a UE where the time duration spanned by the sensing slots that are sensed to be idle before a UL transmission(s) is random. The clause is applicable to the following transmissions: + +- PUSCH/SRS transmission(s) scheduled or configured by eNB/gNB, or +- PUCCH transmission(s) scheduled or configured by gNB, or +- Transmission(s) related to random access procedure. + +A UE may transmit the transmission using Type 1 channel access procedure after first sensing the channel to be idle during the sensing slot durations of a defer duration $T_d$ , and after the counter $N$ is zero in step 4. The counter $N$ is adjusted by sensing the channel for additional sensing slot duration(s) according to the steps described below. + +- 1) set $N = N_{init}$ , where $N_{init}$ is a random number uniformly distributed between 0 and $CW_p$ , and go to step 4; +- 2) if $N > 0$ and the UE chooses to decrement the counter, set $N = N - 1$ ; +- 3) sense the channel for an additional sensing slot duration, and if the additional sensing slot duration is idle, go to step 4; else, go to step 5; +- 4) if $N = 0$ , stop; else, go to step 2. +- 5) sense the channel until either a busy sensing slot is detected within an additional defer duration $T_d$ or all the sensing slots of the additional defer duration $T_d$ are detected to be idle; + +- 6) if the channel is sensed to be idle during all the sensing slot durations of the additional defer duration $T_d$ , go to step 4; else, go to step 5; + +If a UE has not transmitted a UL transmission on a channel on which UL transmission(s) are performed after step 4 in the procedure above, the UE may transmit a transmission on the channel, if the channel is sensed to be idle at least in a sensing slot duration $T_{sl}$ when the UE is ready to transmit the transmission and if the channel has been sensed to be idle during all the sensing slot durations of a defer duration $T_d$ immediately before the transmission. If the channel has not been sensed to be idle in a sensing slot duration $T_{sl}$ when the UE first senses the channel after it is ready to transmit, or if the channel has not been sensed to be idle during any of the sensing slot durations of a defer duration $T_d$ immediately before the intended transmission, the UE proceeds to step 1 after sensing the channel to be idle during the sensing slot durations of a defer duration $T_d$ . + +The defer duration $T_d$ consists of duration $T_f = 16\mu s$ immediately followed by $m_p$ consecutive sensing slot durations where each sensing slot duration is $T_{sl} = 9\mu s$ , and $T_f$ includes an idle sensing slot duration $T_{sl}$ at start of $T_f$ . + +$CW_{min,p} \leq CW_p \leq CW_{max,p}$ is the contention window. $CW_p$ adjustment is described in clause 4.2.2. + +$CW_{min,p}$ and $CW_{max,p}$ are chosen before step 1 of the procedure above. + +$m_p$ , $CW_{min,p}$ , and $CW_{max,p}$ are based on a channel access priority class $p$ as shown in Table 4.2.1-1, that is signalled to the UE. + +#### 4.2.1.2 Type 2 UL channel access procedure + +This clause describes channel access procedures by UE where the time duration spanned by the sensing slots that are sensed to be idle before a UL transmission(s) is deterministic. + +If a UE is indicated by an eNB to perform Type 2 UL channel access procedures, the UE follows the procedures described in clause 4.2.1.2.1. + +##### 4.2.1.2.1 Type 2A UL channel access procedure + +If a UE is indicated to perform Type 2A UL channel access procedures, the UE uses Type 2A UL channel access procedures for a UL transmission. The UE may transmit the transmission immediately after sensing the channel to be idle for at least a sensing interval $T_{short\_ul} = 25\mu s$ . $T_{short\_ul}$ consists of a duration $T_f = 16\mu s$ immediately followed by one sensing slot and $T_f$ includes a sensing slot at start of $T_f$ . The channel is considered to be idle for $T_{short\_ul}$ if both sensing slots of $T_{short\_ul}$ are sensed to be idle. + +##### 4.2.1.2.2 Type 2B UL channel access procedure + +If a UE is indicated to perform Type 2B UL channel access procedures, the UE uses Type 2B UL channel access procedure for a UL transmission. The UE may transmit the transmission immediately after sensing the channel to be idle within a duration of $T_f = 16\mu s$ . $T_f$ includes a sensing slot that occurs within the last $9\mu s$ of $T_f$ . The channel is considered to be idle within the duration $T_f$ if the channel is sensed to be idle for total of at least $5\mu s$ with at least $4\mu s$ of sensing occurring in the sensing slot. + +##### 4.2.1.2.3 Type 2C UL channel access procedure + +If a UE is indicated to perform Type 2C UL channel access procedures for a UL transmission, the UE does not sense the channel before the transmission. The duration of the corresponding UL transmission is at most $584\mu s$ . + +### 4.2.2 Contention window adjustment procedures + +If a UE transmits transmissions using Type 1 channel access procedures that are associated with channel access priority class $p$ on a channel, the UE maintains the contention window value $CW_p$ and adjusts $CW_p$ for those transmissions before step 1 of the procedure described in clause 4.2.1.1, as described in this clause. + +#### 4.2.2.1 Contention window adjustment procedures for UL transmissions scheduled/configured by eNB + +If a UE transmits transmissions using Type 1 channel access procedures that are associated with channel access priority class $p$ on a channel, the UE maintains the contention window value $CW_p$ and adjusts $CW_p$ for those transmissions before step 1 of the procedure described in clause 4.2.1.1, using the following procedure: + +- If the UE receives an UL grant or an AUL-DFI, the contention window size for all the priority classes is adjusted as following: + - If the NDI value for at least one HARQ process associated with HARQ\_ID\_ref is toggled, or if the HARQ-ACK value(s) for at least one of the HARQ processes associated with HARQ\_ID\_ref received in the earliest AUL-DFI after $n_{ref}+3$ indicates ACK, + - for every priority class $p \in \{1,2,3,4\}$ , set $CW_p = CW_{min,p}$ ; + - Otherwise, increase $CW_p$ for every priority class $p \in \{1,2,3,4\}$ to the next higher allowed value; +- If there exists one or more previous transmissions $\{T_0, \dots, T_n\}$ using Type 1 channel access procedure, from the start subframe(s) of the previous transmission(s) of which, N or more subframes have elapsed and neither UL grant nor AUL-DFI was received, where $N = \max(\text{contentionWindowSizeTimer}, T_i \text{ burst length}+1)$ if $\text{contentionWindowSizeTimer} > 0$ and $N = 0$ otherwise, for each transmission $T_i$ , $CW_p$ is adjusted as following: + - increase $CW_p$ for every priority class $p \in \{1,2,3,4\}$ to the next higher allowed value; + - The $CW_p$ is adjusted once +- Else if the UE transmits transmissions using Type 1 channel access procedure before N subframes have elapsed from the start of previous UL transmission burst using Type 1 channel access procedure and neither UL grant nor AUL-DFI is received, + - the $CW_p$ is unchanged. +- If the UE receives an UL grant or an AUL-DFI indicates feedback for one or more previous transmissions $\{T_0, \dots, T_n\}$ using Type 1 channel access procedure, from the start subframe(s) of the previous transmission(s) of which, N or more subframes have elapsed and neither UL grant nor AUL-DFI was received, where $N = \max(\text{contentionWindowSizeTimer}, T_i \text{ burst length}+1)$ if $\text{contentionWindowSizeTimer} > 0$ and $N = 0$ otherwise, the UE may recompute $CW_p$ as follows: + - The UE reverts $CW_p$ to the value used to transmit at $n_{T0}$ using Type 1 channel access procedure. + - The UE updates $CW_p$ sequentially in the order of the transmission $\{T_0, \dots, T_n\}$ + - If the NDI value for at least one HARQ process associated with HARQ\_ID\_ref is toggled, or if the HARQ-ACK value(s) for at least one of the HARQ processes associated with HARQ\_ID\_ref received in the earliest AUL-DFI after $n_{Ti}+3$ indicates ACK, + - for every priority class $p \in \{1,2,3,4\}$ set $CW_p = CW_{min,p}$ . + - Otherwise, increase $CW_p$ for every priority class $p \in \{1,2,3,4\}$ to the next higher allowed value. +- If the UE transmits transmissions using Type 1 channel access procedure before N subframes have elapsed from the start of previous UL transmission burst using Type 1 channel access procedure and neither UL grant nor AUL-DFI is received, + - $CW_p$ is unchanged. + +HARQ\_ID\_ref is the HARQ process ID of UL-SCH in reference subframe $n_{ref}$ . The reference subframe $n_{ref}$ is determined as follows + +- If the UE receives an UL grant or an AUL-DFI in subframe $n_g$ , subframe $n_w$ is the most recent subframe before subframe $n_g - 3$ in which the UE has transmitted UL-SCH using Type 1 channel access procedure. + +- If the UE transmits transmissions including UL-SCH without gaps starting with subframe $n_0$ and in subframes $n_0, n_1, \dots, n_w$ and the UL-SCH in subframe $n_0$ is not PUSCH Mode 1 that starts in the second slot of the subframe, reference subframe $n_{ref}$ is subframe $n_0$ . +- If the UE transmits transmissions including PUSCH Mode 1 without gaps starting with second slot of subframe $n_0$ and in subframes $n_0, n_1, \dots, n_w$ and the, reference subframe $n_{ref}$ is subframe $n_0$ and $n_1$ , +- otherwise, reference subframe $n_{ref}$ is subframe $n_w$ . + +HARQ\_ID\_ref is the HARQ process ID of UL-SCH in reference subframe $n_{Ti}$ . The reference subframe $n_{Ti}$ is determined as the start subframe of a transmission $T_i$ using Type 1 channel access procedure and of which, N subframes have elapsed and neither UL grant nor AUL-DFI was received. + +If the AUL-DFI with DCI format 0A is indicated to a UE that is activated with AUL transmission and transmission mode 2 is configured for the UE for grant-based uplink transmissions, the spatial HARQ-ACK bundling shall be performed by logical OR operation across multiple codewords for the HARQ process not configured for autonomous UL transmission. + +If $CW_p$ changes during an ongoing channel access procedure, the UE shall draw a counter $N_{init}$ and applies it to the ongoing channel access procedure. + +The UE may keep the value of $CW_p$ unchanged for every priority class $p \in \{1,2,3,4\}$ , if the UE scheduled to transmit transmissions without gaps including PUSCH in a set subframes $n_0, n_1, \dots, n_{w-1}$ using Type 1 channel access procedure, and if the UE is not able to transmit any transmission including PUSCH in the set of subframes. + +The UE may keep the value of $CW_p$ for every priority class $p \in \{1,2,3,4\}$ the same as that for the last scheduled transmission including PUSCH using Type 1 channel access procedure, if the reference subframe for the last scheduled transmission is also $n_{ref}$ . + +#### 4.2.2.2 Contention window adjustment procedures for UL transmissions scheduled/configured by gNB + +If a UE transmits transmissions using Type 1 channel access procedures that are associated with channel access priority class $p$ on a channel, the UE maintains the contention window value $CW_p$ and adjusts $CW_p$ for those transmissions before step 1 of the procedure described in clause 4.2.1.1, using the following steps: + +- 1) For every priority class $p \in \{1,2,3,4\}$ , set $CW_p = CW_{min,p}$ ; +- 2) If HARQ-ACK feedback is available after the last update of $CW_p$ , go to step 3. Otherwise, if the UE transmission after procedure described in clause 4.2.1.1 does not include a retransmission or would be transmitted within a duration $T_w$ from the end of the *reference duration* corresponding to the earliest UL channel occupancy after the last update of $CW_p$ , go to step 5; otherwise go to step 4. +- 3) The HARQ-ACK feedback(s) corresponding to PUSCH(s) in the *reference duration* for the latest UL channel occupancy for which HARQ-ACK feedback is available is used as follows: + - a. If at least one HARQ-ACK feedback is 'ACK' for PUSCH(s) with transport block (TB) based feedback or at least 10% of HARQ-ACK feedbacks are 'ACK' for PUSCH CBGs transmitted at least partially on the channel with code block group (CBG) based feedback, go to step 1; otherwise go to step 4. +- 4) Increase $CW_p$ for every priority class $p \in \{1,2,3,4\}$ to the next higher allowed value; +- 5) For every priority class $p \in \{1,2,3,4\}$ , maintain $CW_p$ as it is; go to step 2. + +The HARQ-ACK feedback, *reference duration* and duration $T_w$ in the procedure above are defined as the following: + +- For the purpose of contention window adjustment in this clause, HARQ-ACK feedback for PUSCH(s) transmissions are expected to be provided to UE(s) explicitly or implicitly where explicit HARQ-ACK is determined based on the valid HARQ-ACK feedback in a corresponding CG-DFI as described in clause 10.5 in [7], and implicit HARQ-ACK feedback is determined based on the indication for a new transmission or retransmission in the DCI scheduling PUSCH(s) as follows: + +- If a new transmission is indicated, 'ACK' is assumed for the transport blocks or code block groups in the corresponding PUSCH(s) for the TB-based and CBG-based transmission, respectively. +- If a retransmission is indicated for TB-based transmissions, 'NACK' is assumed for the transport blocks in the corresponding PUSCH(s). +- If a retransmission is indicated for CBG-based transmissions, if a bit value in the code block group transmission information (CBGTI) field is '0' or '1' as described in clause 5.1.7.2 in [8], 'ACK' or 'NACK' is assumed for the corresponding CBG in the corresponding PUSCH(s), respectively. +- The *reference duration* corresponding to a channel occupancy initiated by the UE including transmission of PUSCH(s) is defined in this clause as a duration starting from the beginning of the channel occupancy until the end of the first slot where at least one PUSCH is transmitted over all the resources allocated for the PUSCH, or until the end of the first transmission burst by the UE that contains PUSCH(s) transmitted over all the resources allocated for the PUSCH, whichever occurs earlier. If the channel occupancy includes a PUSCH, but it does not include any PUSCH transmitted over all the resources allocated for that PUSCH, then, the duration of the first transmission burst by the UE within the channel occupancy that contains PUSCH(s) is the *reference duration* for CWS adjustment. +- $T_w = \max(T_A, T_B + 1ms)$ where $T_B$ is the duration of the transmission burst from start of the *reference duration* in *ms* and $T_A = 5ms$ if the absence of any other technology sharing the channel cannot be guaranteed on a long-term basis (e.g. by level of regulation), and $T_A = 10ms$ otherwise. + +If a UE transmits transmissions using Type 1 channel access procedures associated with the channel access priority class $p$ on a channel and the transmissions are not associated with explicit or implicit HARQ-ACK feedbacks as described above in this clause, the UE adjusts $CW_p$ before step 1 in the procedures described in clause 4.2.1.1, using the latest $CW_p$ used for any UL transmissions on the channel using Type 1 channel access procedures associated with the channel access priority class $p$ . If the corresponding channel access priority class $p$ has not been used for any UL transmission on the channel, $CW_p = CW_{min,p}$ is used. + +#### 4.2.2.3 Common procedures for CWS adjustments for UL transmissions + +The following applies to the procedures described in clauses 4.2.2.1 and 4.2.2.2: + +- If $CW_p = CW_{max,p}$ , the next higher allowed value for adjusting $CW_p$ is $CW_{max,p}$ . +- If the $CW_p = CW_{max,p}$ is consecutively used $K$ times for generation of $N_{init}$ , $CW_p$ is reset to $CW_{min,p}$ only for that priority class $p$ for which $CW_p = CW_{max,p}$ is consecutively used $K$ times for generation of $N_{init}$ . $K$ is selected by UE from the set of values $\{1, 2, \dots, 8\}$ for each priority class $p \in \{1, 2, 3, 4\}$ . + +### 4.2.3 Energy detection threshold adaptation procedure + +A UE accessing a channel on which UL transmission(s) are performed, shall set the energy detection threshold ( $X_{Thresh}$ ) to be less than or equal to the maximum energy detection threshold $X_{Thresh\_max}$ . + +$X_{Thresh\_max}$ is determined as follows: + +- If the UE is configured with higher layer parameter *maxEnergyDetectionThreshold-r14* or *maxEnergyDetectionThreshold-r16*, + - $X_{Thresh\_max}$ is set equal to the value signalled by the higher layer parameter; +- otherwise + - the UE shall determine $X'_{Thresh\_max}$ according to the procedure described in clause 4.2.3.1; + - if the UE is configured with higher layer parameter *energyDetectionThresholdOffset-r14* or *energyDetectionThresholdOffset-r16* + - $X_{Thresh\_max}$ is set by adjusting $X'_{Thresh\_max}$ according to the offset value signalled by the higher layer parameter; + - otherwise + +- the UE shall set $X_{\text{Thresh\_max}} = X'_{\text{Thresh\_max}}$ . + +The UE is not expected to be configured with *ul-toDL-COT-SharingED-Threshold-r16* when the UE is provided with *ChannelAccessMode-r16 = 'semiStatic'*, + +If the higher layer parameter *absenceOfAnyOtherTechnology-r16* is not configured to a UE, and the higher layer parameter *ul-toDL-COT-SharingED-Threshold-r16* is configured to the UE, the gNB should use the gNB's transmit power in determining the resulting energy detection threshold *ul-toDL-COT-SharingED-Threshold-r16*. + +For the case where a UE performs channel access procedures as described in clause 4.2.1.1 for a UL transmission and CG-UCI is absent in the UL transmission or CG-UCI is present in the UL transmission and indicates COT-sharing information other than 'COT sharing not available', $X_{\text{Thresh\_max}}$ is set equal to the value provided by the higher layer parameter *ul-toDL-COT-SharingED-Threshold-r16*, if provided. + +#### 4.2.3.1 Default maximum energy detection threshold computation procedure + +If the higher layer parameter *absenceOfAnyOtherTechnology-r14* or *absenceOfAnyOtherTechnology-r16* is provided + +- $X'_{\text{Thresh\_max}} = \min \left\{ \begin{matrix} T_{\max} + 10\text{dB} \\ X_r \end{matrix} \right\}$ where + - $X_r$ is Maximum energy detection threshold defined by regulatory requirements in dBm when such requirements are defined, otherwise $X_r = T_{\max} + 10\text{dB}$ + Otherwise + +$$- X'_{\text{Thresh\_max}} = \max \left\{ \begin{matrix} X_{\text{reg}} \\ \min \left\{ \begin{matrix} T_{\max}, \\ T_{\max} - T_A + (P_H + 10 \cdot \log 10(BW\text{MHz} / 20\text{MHz}) - P_{TX}) \end{matrix} \right\} \end{matrix} \right\}$$ + +where + +- In regulatory regions and bands where it is allowed, + - $X_{\text{reg}} = -67 + 10 \cdot \log 10(BW\text{MHz} / 20\text{MHz}) \text{ dBm}$ ; + - $T_A = 5\text{dB}$ ; + - $P_H = 23\text{dBm}$ ; + +Otherwise, + +- $X_{\text{reg}} = -72 + 10 \cdot \log 10(BW\text{MHz} / 20\text{MHz}) \text{ dBm}$ ; +- $T_A = 10\text{dB}$ ; +- $P_H = 23\text{dBm}$ or in regions and bands where regulations allow, $24\text{dBm}$ ; +- $P_{TX}$ is set to the value of $P_{\text{CMAX\_H,c}}$ as defined in [3]; +- $T_{\max}(\text{dBm}) = 10 \cdot \log 10 (3.16228 \cdot 10^{-8}(\text{mW/MHz}) \cdot BW\text{MHz} (\text{MHz}))$ ; +- $BW\text{MHz}$ is the single channel bandwidth in MHz. + +## 4.3 Channel access procedures for semi-static channel occupancy + +Channel access procedures based on semi-static channel occupancy as described in this Clause, are intended for environments where the absence of other technologies is guaranteed e.g., by level of regulations, private premises policies, etc. + +If a gNB provides UE(s) with higher layer parameters *ChannelAccessMode-r16 = 'semiStatic'* by SIB1 or dedicated configuration for a serving cell, a periodic channel occupancy can be initiated by the gNB on a channel(s) within the + +bandwidth of the serving cell every $T_x$ within every two consecutive radio frames, starting from the even indexed radio frame at $i \cdot T_x$ with a maximum channel occupancy time $T_y = 0.95T_x$ , where $T_x = \text{period}$ in ms, is a higher layer parameter provided in *SemiStaticChannelAccessConfig* and $i \in \{0, 1, \dots, \frac{20}{T_x} - 1\}$ . A duration of $T_z = \max(0.05T_x, 100\mu\text{s})$ at the end of a period is referred to as the *idle duration* of that period. + +If the gNB additionally configures a UE with higher layer parameter *semiStaticChannelAccessConfigUE* consisting of *periodUE* and *offsetUE*, the UE can initiate a channel occupancy on a channel(s) within the bandwidth of the serving cell every $T_u = \text{periodUE}$ in ms with corresponding maximum channel occupancy time $T_v = 0.95T_u$ . The offset of the periodic channel occupancy is determined by $T_o = \text{offsetUE}$ as the number of symbols from the beginning of an even indexed radio frame to the start of the first period in that radio frame in which the UE can initiate a channel occupancy. A duration of $T_w = \max(0.05T_u, 100\mu\text{s})$ at the end of a period is referred to as the *idle duration* of that period. + +For determining a *Channel Occupancy Time* based on semi-static channel access procedures, duration of any transmission gap within a period excluding the corresponding idle duration is counted in the channel occupancy time. In the following procedures in this clause, when a gNB or UE performs sensing for evaluating a channel availability, the sensing is performed at least during a sensing slot duration $T_{sl} = 9\mu\text{s}$ , unless longer sensing duration is required (e.g. by level of regulation), in which case sensing is performed within a duration of $T_{sl} = 16\mu\text{s}$ . When sensing is performed within a duration of $T_{sl} = 16\mu\text{s}$ , the channel is considered to be idle if the channel is sensed to be idle for total of at least $5\mu\text{s}$ with at least $4\mu\text{s}$ of sensing occurring in the last $9\mu\text{s}$ time interval in the sensing duration. The corresponding $X_{\text{Thresh}}$ adjustment for performing sensing by a gNB or a UE is described in clauses 4.1.5 and 4.2.3, respectively. + +### 4.3.1 Channel access procedures to initiate a channel occupancy + +For semi-static channel occupancy, the procedures in Clause 4.3.1.1 are followed if *semiStaticChannelAccessConfigUE* is absent. Otherwise, the procedures in Clause 4.3.1.2 are applicable. + +If a UE fails to access the channel(s) prior to an intended UL transmission to a gNB, Layer 1 notifies higher layers about the channel access failure. + +#### 4.3.1.1 Channel occupancy initiated only by gNB + +A channel occupancy that is initiated by a gNB and is shared with UE(s), satisfies the following: + +- The gNB shall transmit a DL transmission burst starting at the beginning of a period of duration $T_x$ in which the channel occupancy is initiated immediately after sensing the channel to be idle for at least a sensing slot duration $T_{sl}$ . If the channel is sensed to be busy, the gNB shall not perform any transmission during the current period. +- The gNB may transmit a DL transmission burst(s) within the channel occupancy time immediately after sensing the channel to be idle for at least a sensing slot duration $T_{sl}$ if the gap between the DL transmission burst(s) and any previous transmission burst is more than $16\mu\text{s}$ . +- The gNB may transmit DL transmission burst(s) after UL transmission burst(s) within the channel occupancy time without sensing the channel if the gap between the DL and UL transmission bursts is at most $16\mu\text{s}$ . +- A UE may transmit UL transmission burst(s) after detection of a DL transmission burst(s) within the channel occupancy time as follows: + - If the gap between the UL and DL transmission bursts is at most $16\mu\text{s}$ , the UE may transmit UL transmission burst(s) after a DL transmission burst(s) within the channel occupancy time without sensing the channel. + - If the gap between the UL and DL transmission bursts is more than $16\mu\text{s}$ , the UE may transmit UL transmission burst(s) after a DL transmission burst(s) within the channel occupancy time after sensing the channel to be idle for at least a sensing slot duration $T_{sl}$ within a $25\mu\text{s}$ interval ending immediately before transmission. +- A UE may be indicated by the gNB to transmit UL transmission burst(s) within the channel occupancy time without sensing the channel or after sensing the channel to be idle for at least a sensing slot duration $T_{sl}$ within a $25\mu\text{s}$ interval ending immediately before transmission. +- The gNB and UEs shall not transmit any transmissions in a set of consecutive symbols for a duration of at least $T_z = \max(0.05T_x, 100\mu\text{s})$ before the start of the next period. + +#### 4.3.1.2 Channel occupancy initiated by gNB or UE + +##### 4.3.1.2.1 Channel occupancy initiated by gNB and sensing procedures + +The gNB initiates a channel occupancy in a period of duration $T_x$ if the gNB transmits a DL transmission burst starting at the beginning of the period immediately after sensing the channel to be idle for at least a sensing slot duration $T_{sl}$ and ends the transmission of the DL transmission burst before the start of the idle duration of that period. When the gNB initiates a channel occupancy in that period, the gNB shall not transmit any transmission(s) within the idle duration of that period. A UE determines that the gNB has initiated the channel occupancy in that period by detection of a DL transmission burst(s) in that period or an indication by a DCI as described in Clause 4.3.1.2.4. + +When a UL or DL transmission burst(s) is associated with the channel occupancy that is initiated in that period by the gNB, the following are applicable: + +- The UL or DL transmission burst(s) is confined within that period and ends before the start of the idle duration of that period. +- If the gap between the DL transmission burst(s) and any previous transmission burst in that period is more than $16\mu s$ , the DL transmission burst(s) may be transmitted if the channel is sensed to be idle for at least a sensing slot duration $T_{sl}$ immediately before the DL transmission. +- If the gap between the DL transmission burst(s) and any previous UL transmission burst in that period is at most $16\mu s$ , the DL transmission burst(s) may be transmitted without sensing. +- If the gap between the UL transmission burst(s) and any previous DL transmission burst in that period is more than $16\mu s$ , the UL transmission burst(s) may be transmitted if the channel is sensed to be idle for at least a sensing slot duration $T_{sl}$ within a $25\mu s$ interval ending immediately before the UL transmission burst(s). +- If the gap between the UL transmission burst(s) and any previous DL transmission burst in that period is at most $16\mu s$ , the UL transmission burst(s) may be transmitted without sensing. + +##### 4.3.1.2.2 Channel occupancy initiated by UE and sensing procedures + +A UE initiates a channel occupancy in a period of duration $T_u$ if the UE transmits a UL transmission burst starting at the beginning of the period immediately after sensing the channel to be idle for at least a sensing slot duration $T_{sl}$ and ends the transmission of the UL transmission burst before the start of the idle duration of that period. When the UE initiates a channel occupancy in that period, the UE shall not transmit any transmission(s) within the idle duration of that period. + +When a UL or DL transmission burst(s) is associated with the channel occupancy that is initiated in that period by the UE, the following are applicable: + +- The UL or DL transmission burst(s) is confined within that period and ends before the start of the idle duration of that period. +- If the gap between the UL transmission burst(s) and any previous transmission burst in that period is more than $16\mu s$ , the UL transmission burst(s) may be transmitted if the channel is sensed to be idle for at least a sensing slot duration $T_{sl}$ immediately before the UL transmission burst(s). +- If the gap between the UL transmission burst(s) and any previous DL transmission burst in that period is at most $16\mu s$ , the UL transmission burst(s) may be transmitted without sensing. +- If the gap between the DL transmission burst(s) and any previous UL transmission burst in that period is more than $16\mu s$ , the DL transmission burst(s) may be transmitted if the channel is sensed to be idle for at least a sensing slot duration $T_{sl}$ within a $25\mu s$ interval ending immediately before the DL transmission. +- If the gap between the DL transmission burst(s) and any previous UL transmission burst in that period is at most $16\mu s$ , the DL transmission burst(s) may be transmitted without sensing. + +When a DL transmission burst(s) is associated with a channel occupancy that is initiated in a period of duration $T_u$ by a UE, the DL transmission burst(s) shall include unicast user plane data or control information intended for the UE that has initiated the channel occupancy in that period. The gNB may include in the DL transmission burst(s) an additional transmission(s) intended to other UEs than the UE that has initiated the channel occupancy in that period or broadcast transmission(s), only if the gNB satisfies the condition that the detection of the additional DL transmission(s) at any UE + +will not be associated with a channel occupancy that is initiated by gNB following the procedures described in Clause 4.3.1.2.3 and 4.3.1.2.4. + +When a UE is configured with a configured grant for which *cg-RetransmissionTimer-r16* is provided and if the UE is provided *cg-COT-SharingList-r16* by higher layers, the UE is configured with a table wherein each row is given by higher layer parameter *CG-COT-Sharing-r16*. One row of the table is configured for indicating that the channel occupancy sharing is not available and other rows of the table each provides a channel occupancy sharing information. In this case, each configured grant PUSCH transmission includes 'COT sharing information' in CG-UCI as described in [10] that indicates a row index to the table, which is chosen by the UE independently of the CAPC information that the row may carry. If the gNB shares a channel occupancy initiated by the UE and detects a CG-UCI in slot $n$ that includes 'COT sharing information', the gNB may transmit a transmission that follows the configured grant PUSCH transmission starting from slot $n + O$ , where $O = \text{offset-r16}$ slots, for a duration of $D = \text{duration-r16}$ slots where *duration-r16* and *offset-r16* are higher layer parameters provided by *CG-COT-Sharing-r16*. + +##### 4.3.1.2.3 Association with initiated channel occupancy for configured UL transmissions + +When a UE is configured with a UL transmission, the UE follows the following procedures to determine if the configured UL transmission is associated with a channel occupancy that is initiated by the gNB or the UE. + +- If the configured UL transmission would occur at the beginning of a period of duration $T_u$ and would end before the idle duration corresponding to that period, the following is applied: + - If the configured UL transmission would occur within a period of duration $T_x$ and would end before the idle duration corresponding to that period and if the UE has already determined that the gNB has initiated a channel occupancy in that period as described in Clause 4.3.1.2.1, the UE assumes that the configured UL transmission is associated with the channel occupancy that is initiated by the gNB. + - Otherwise, the UE assumes that the configured UL transmission is associated with a channel occupancy to be initiated by the UE. +- If the configured UL transmission would occur at the beginning of a period of duration $T_u$ and would overlap with the idle duration corresponding to that period, the following is applied: + - If the configured UL transmission would occur within a period of duration $T_x$ and would end before the idle duration corresponding to that period, and if the UE has already determined that the gNB has initiated a channel occupancy in that period as described in Clause 4.3.1.2.1, the UE assumes that the configured UL transmission is associated with the channel occupancy that is initiated by the gNB. + - Otherwise, the UE drops the configured UL transmission. +- If the configured UL transmission would occur after the beginning of a period of duration $T_u$ and would end before the idle duration corresponding to that period, the following is applied: + - If the UE has already initiated a channel occupancy in that period as described in Clause 4.3.1.2.2, the UE assumes that the configured UL transmission is associated with the channel occupancy that is initiated by the UE. + - If the UE has not already initiated a channel occupancy in that period as described in Clause 4.3.1.2.2, then if the configured UL transmission would occur within a period of duration $T_x$ and would end before the idle duration corresponding to that period and if the UE has already determined that the gNB has initiated a channel occupancy in that period as described in Clause 4.3.1.2.1, the UE assumes that the configured UL transmission is associated with the channel occupancy that is initiated by the gNB; otherwise, the UE drops the configured UL transmission(s). +- If the configured UL transmission would occur after the beginning of a period of duration $T_u$ and would overlap with the idle duration corresponding to that period, the following is applied: + - If the UE has not already initiated a channel occupancy in that period as described in Clause 4.3.1.2.2: + - If the configured UL transmission would occur within a period of duration $T_x$ and would end before the idle duration corresponding to that period and the UE has already determined that the gNB has initiated a channel occupancy in that period as described in Clause 4.3.1.2.1, the UE assumes that the configured UL transmission is associated with the channel occupancy that is initiated by the gNB. + +- Otherwise, the UE drops the configured UL transmission. +- Otherwise, the UE drops the configured UL transmission. + +If the configured UL transmission is a PUSCH with PUSCH repetition type B that does not overlap with an idle duration corresponding to a period of duration $T_u$ or a period of duration $T_x$ , the above procedures are applicable to its corresponding nominal repetition as described in [8]. Otherwise, the following procedures are applicable to its corresponding nominal repetition. + +- If the configured UL transmission would occur at the beginning of a period of duration $T_u$ and within a period of duration $T_x$ the following is applied: + - If the UE has already determined that the gNB has initiated channel occupancy in that period as described in Clause 4.3.1.2.1, the UE assumes that the configured UL transmission is associated with the channel occupancy that is initiated by the gNB. + - Otherwise, the UE assumes that the configured UL transmission is associated with a channel occupancy to be initiated by the UE. +- If the configured UL transmission would occur after the beginning of a period of duration $T_u$ and within a period of duration $T_x$ the following is applied: + - If the UE has already initiated a channel occupancy in the period of duration $T_u$ as described in Clause 4.3.1.2.2, the UE assumes that the configured UL transmission is associated with the channel occupancy that is initiated by the UE. + - Otherwise, + - if the UE has already determined that the gNB has initiated a channel occupancy in the period of duration $T_x$ as described in Clause 4.3.1.2.1, the UE assumes that the configured UL transmission is associated with the channel occupancy that is initiated by the gNB. + - Otherwise, the UE drops the configured UL transmission. + +##### 4.3.1.2.4 Association with initiated channel occupancy for scheduled UL transmissions + +When a UL transmission(s) is scheduled by a DCI or a RAR message, the scheduling DCI or the RAR message indicates the channel access parameters for the UL transmission(s) as described in [10]. Based on the DCI or the RAR message, the UE determines if the scheduled UL transmission(s) is associated with a channel occupancy that is initiated by the gNB or the UE, and whether sensing and CP extension are applicable. + +###### 4.3.1.2.4.1 Intra-period scheduled UL transmissions + +The procedures in this clause are applicable when a scheduled UL transmission and the corresponding scheduling DCI or the corresponding RAR transmission are confined within the same period of duration $T_x$ corresponding to the carrier within which the UL transmission is scheduled and regardless of whether they are transmitted on the same carrier or different carriers. + +If the UE is indicated that the scheduled UL transmission is associated with a channel occupancy that is initiated by the gNB, and the UE is indicated to perform the UL transmission without sensing, the UE applies CP extension if applicable following the procedures described in [11] and is expected to transmit the scheduled UL transmission without sensing as described in Clause 4.3.1.2.1. + +If the UE is indicated that the scheduled UL transmission is associated with a channel occupancy that is initiated by the gNB and the UE is indicated to perform the UL transmission after sensing, the following are applied: + +- If the UE determines that the UL transmission follows a previous transmission after a gap of at most 16us, the UE is expected to transmit the UL transmission without sensing. Otherwise, the UE senses the channel for at least a sensing slot duration $T_{sl}$ within a 25us interval immediately before the scheduled UL transmission as described in Clause 4.3.1.2.1. If the channel is sensed to be idle, the UE is expected to transmit the scheduled UL transmission, and drop otherwise. + +If the UE is indicated that the scheduled UL transmission is associated with a channel occupancy that is initiated by the UE, the following are applied: + +- If the UL transmission would occur at the beginning of a period of duration $T_u$ , the UE is expected to sense the channel for at least a sensing slot duration $T_{sl}$ immediately before the UL transmission as described in Clause 4.3.1.2.2. If the channel is sensed to be idle, the UE is expected to transmit the UL transmission, and drop otherwise. +- If the UL transmission would occur after the beginning of a period of duration $T_u$ + - if the UE has not initiated a channel occupancy in that period as described in Clause 4.3.1.2.2, the UE is expected to drop the transmission; + - otherwise, if the UE has already initiated a channel occupancy in that period as described in Clause 4.3.1.2.2: + - if the UE determines that the UL transmission would follow a previous transmission after a gap of at most 16us, the UE is expected to transmit the UL transmission without sensing; + - otherwise, if the UE determines that the UL transmission would follow a previous transmission, if any, after a gap of more than 16us, the UE is expected to sense the channel for at least a sensing slot duration $T_{sl}$ immediately before the UL transmission as described in Clause 4.3.1.2.2 where the UE is expected to transmit the UL transmission if the channel is sensed to be idle, and drop the UL transmission otherwise. + +###### 4.3.1.2.4.2 Cross-period scheduled UL transmissions + +The procedures in this clause are applicable when a scheduled UL transmission and the corresponding scheduling DCI or the corresponding RAR transmission are confined within different periods of duration $T_x$ corresponding to the carrier within which the UL transmission is scheduled and regardless of whether they are transmitted on the same carrier or different carriers. + +If the UE is indicated that the scheduled UL transmission is associated with a channel occupancy that is initiated by the gNB and the UE is indicated to perform the UL transmission without sensing, the following are applied: + +- If the scheduled UL transmission starts after the beginning of a period of duration $T_x$ corresponding to the carrier within which the UL transmission is scheduled and ends before the start of the idle duration corresponding to that period and if the UE has determined that a channel occupancy corresponding to that period is initiated by the gNB as described in Clause 4.3.1.2.1, the UE applies CP extension if applicable and is expected to transmit the scheduled UL transmission without sensing as described in Clause 4.3.1.2.1. +- Otherwise, the UE drops the scheduled UL transmission. + +If the UE is indicated that the scheduled UL transmission is associated with a channel occupancy that is initiated by the gNB and the UE is indicated to perform the UL transmission after sensing, the following are applied: + +- If the scheduled UL transmission starts after the beginning of a period of duration $T_x$ corresponding to the carrier within which the UL transmission is scheduled and ends before the start of the idle duration corresponding to that period and if the UE has determined that a channel occupancy corresponding to the period is initiated by the gNB as described in Clause 4.3.1.2.1, + - if the UE determines that the UL transmission follows a previous transmission after a gap of at most 16us, the UE is expected to transmit the UL transmission without sensing. Otherwise, the UE senses the channel for at least a sensing slot duration $T_{sl}$ within a 25 $\mu$ s interval immediately before the scheduled UL transmission as described in Clause 4.3.1.2.1 where the UE is expected to transmit the scheduled UL transmission if the channel is sensed to be idle and drop the scheduled UL transmission otherwise. +- Otherwise, the UE drops the scheduled UL transmission. + +If the UE is indicated that the scheduled UL transmission is associated with a channel occupancy that is initiated by the UE the following are applied: + +- If the UL transmission would start at the beginning of a period of duration $T_u$ and would end before the start of the idle duration corresponding to that period, the UE is expected to sense the channel for at least a sensing slot duration $T_{sl}$ immediately before the UL transmission as described in Clause 4.3.1.2.2 where the UE is expected to transmit the UL transmission if the channel is sensed to be idle, and drop the UL transmission otherwise. + +- If the UL transmission would start after the beginning of a period of duration $T_u$ and would end before the start of the idle duration corresponding to that period, +- if the UE has already initiated a channel occupancy in that period as described in Clause 4.3.1.2.2 the following is applied: + - If the UE determines that the UL transmission follows a previous transmission after a gap of more than 16us, the UE is expected to sense the channel for at least a sensing slot duration $T_{sl}$ immediately before the UL transmission as described in Clause 4.3.1.2.2 where the UE is expected to transmit the UL transmission if the channel is sensed to be idle, and drop otherwise. + - If the UE determines that the UL transmission follows a previous transmission after a gap of at most 16us, the UE is expected to transmit the UL transmission without sensing. +- Otherwise, the UE drops the transmission. + +### 4.3.2 Channel access related procedures for UL transmissions + +For semi-static channel occupancy, the following channel access procedures for consecutive scheduled UL transmissions are applicable: + +- If a UE is scheduled by a gNB to transmit a set of UL transmissions including PUSCH or SRS symbol(s) using a UL grant, the UE shall not apply a CP extension for the remaining UL transmissions in the set after the first UL transmission after accessing the channel. +- If a UE is scheduled to transmit a set of consecutive UL transmissions without gaps including PUSCH using one or more UL grant(s), PUCCH using one or more DL grant(s), or SRS with one or more DL grant(s) or UL grant(s) and the UE transmits one of the scheduled UL transmissions in the set after accessing the channel, the UE may continue transmission of the remaining UL transmissions in the set, if any. + +For semi-static channel occupancy, when a UE is provided with higher layer parameter *semiStaticChannelAccessConfigUE* the following are applicable: + +- The UE may assume that any scheduled or configured UL transmission(s) within a UL transmission burst is associated with the same channel occupancy that is initiated either by the gNB or by the UE. +- If the UE is scheduled by a DCI to transmit multiple UL transmissions, the UE assumes that the indicated initiator of the associated channel occupancy in the DCI is applied for all the UL transmissions scheduled by the DCI. +- If the UE would transmit a nominal repetition of a PUSCH transmission with repetition type B as described in [8] and the UE has already determined based on the procedures in Clause 4.3.1.2.4 or based on the procedures in Clause 4.3.1.2.3 and/or the above rules in this clause, that the nominal repetition is associated with a channel occupancy that is initiated either by the gNB or by the UE, the followings are applicable: + - If the UE has already initiated a channel occupancy in a period of duration $T_u$ as described in Clause 4.3.1.2.2 and the nominal repetition would overlap with the idle duration corresponding to that period and if the UE has already determined that the nominal repetition is associated with a channel occupancy that is initiated by the gNB corresponding to a period of duration $T_x$ and if the nominal repetition would overlap with the idle duration corresponding to that period of duration $T_x$ , the UE drops the nominal repetition of the PUSCH transmission. + - If the UE has already determined that the nominal repetition is associated with a channel occupancy that is initiated by the gNB corresponding to a period of duration $T_x$ and if the nominal repetition overlaps with an idle duration corresponding to that period, all the symbols during the idle duration are considered as invalid symbols as described in [8] and the corresponding actual repetition after the idle period, if any, is dropped. + - If the UE has already determined that the nominal repetition is associated with a channel occupancy that is initiated by the UE corresponding to a period of duration $T_u$ and if the nominal repetition overlaps with an idle duration corresponding to that period, all the symbols during the idle duration are considered as invalid symbols as described in [8]. +- The UE is not expected to transmit a UL transmission(s) that is associated with a channel occupancy initiated by the UE corresponding to a period of duration $T_u$ during the contention-based random access procedures. + +### 4.3.3 Channel access procedures for transmission(s) on multiple channels + +For semi-static channel occupancy, if a gNB/UE intends to transmit on a set of channels $\mathcal{C}$ a transmission that starts at the same time on the set of channels $\mathcal{C}$ , the gNB/UE shall perform channel access on each channel $c_i \in \mathcal{C}$ , according to the procedures described in clause 4.3.1.1 to 4.3.1.2 when applicable. The following are applicable for the transmission on a channel within the bandwidth of a carrier: + +- If the transmission is a UL transmission, the UE may not transmit on channel $c_i \in \mathcal{C}$ within the bandwidth of the carrier, if the UE fails to access any of the channels, of the carrier bandwidth, on which the UE is scheduled or configured by UL resources for the UL transmission. +- If the transmission is a UL transmission, the UE may not transmit on a channel within the bandwidth of the carrier if the UE is configured without intra-cell guard band(s) on a UL bandwidth part as described in clause 7 in [8] and if the UE fails to access any of the channels of the UL bandwidth part. +- If the transmission is a nominal repetition of a configured PUSCH transmission with repetition type B as described in [8], the transmission is dropped if the UE determines that the nominal repetition is not associated with a same channel occupancy for all of the channels and the nominal repetition would overlap with an idle duration corresponding to a period of duration $T_u$ and/or a period of duration $T_x$ . +- If the transmission is a DL transmission, the gNB may not transmit on a channel within the bandwidth of the carrier if the gNB configures the carrier without intra-cell guard band(s) on a DL bandwidth part as described in clause 7 in [8] and if the gNB fails to access any of the channels of the DL bandwidth part. + +## 4.4 Channel access procedures for frequency range 2-2 + +When a gNB is required by regulations to sense a channel(s) for availability for performing transmission(s) on the channel(s) or when a gNB provides UE(s) with higher layer parameters *channelAccessMode2-r17* by SIB1 or dedicated configuration indicating that the channel access procedures would be performed by UE before transmission(s) on a channel(s), the channel access procedures described in this clause for accessing the channel(s) on which the transmission(s) are performed by the gNB/UE(s), are applied. + +When a gNB/UE senses a channel for availability to perform DL/UL transmission(s), the channel for sensing includes at least the corresponding active DL/UL bandwidth part(s) for the DL/UL transmission(s). + +In this clause, when sensing is applicable, the basic unit to perform sensing is a sensing slot with a duration $T_{sl} = 5\mu\text{s}$ . The channel is considered to be idle for the sensing slot duration $T_{sl}$ if a gNB or a UE senses the channel during the sensing slot duration and determines that the detected energy after the antenna assembly within the sensing slot duration is less than energy detection threshold $X_{Thresh}$ as described in Clause 4.4.7. Otherwise, the channel is considered busy for the sensing slot duration $T_{sl}$ . + +In this clause, a maximum gap among a set of DL or UL transmissions in a DL or UL transmission burst, respectively, is $8\mu\text{s}$ . For determining a *Channel Occupancy Time*, if a transmission gap is less than or equal to $8\mu\text{s}$ , the gap duration is counted in the channel occupancy time. + +The spatial domain filter for sensing beam(s) during the sensing slot duration at the gNB, or at a UE when the UE does not indicate a capability for beam correspondence without the uplink beam sweeping, or at a UE when the UE uses a different beam for sensing than the beam used for transmission, covers the transmission beam(s) of the intended transmission(s) within the channel occupancy. + +If a UE indicates a capability for beam correspondence without the uplink beam sweeping and if the UE selects the same sensing beam(s) as the transmission beam(s), the spatial domain filter for sensing beam is determined as described in Clause 5.1.5 of [8]. + +If a channel occupancy includes transmission(s) in different beams that are multiplexed in spatial domain, one of the followings is applicable for the corresponding sensing to perform the transmission(s) within the channel occupancy: + +- Type 1 channel access procedure as described in Clause 4.4.1 is applied before the start of the channel occupancy using a single sensing beam where the single beam covers all the transmission beams within the channel occupancy. When the channel is accessed, the transmission(s) within the channel occupancy across different beams can occur. + +- Type 1 channel access procedure as described in Clause 4.4.1 is applied before the start of the channel occupancy simultaneously per sensing beam where each sensing beam covers a transmission beam within the channel occupancy. When the channel is accessed, the transmission(s) within the channel occupancy across different beams can occur. + +If a channel occupancy includes transmissions in different beams that are multiplexed in time domain, one of the followings is applicable for the corresponding sensing to perform the transmissions within the channel occupancy: + +- Type 1 channel access procedure as described in Clause 4.4.1 is applied before the start of the channel occupancy using a single sensing beam where the single beam covers all the transmissions beams within the channel occupancy. When the channel is accessed, the transmissions within the channel occupancy across different beams can occur following the procedures described in Clause 4.4.3. +- When the gNB/UE can perform simultaneous sensing in different beams, Type 1 channel access procedure as described in Clause 4.4.1 is applied before the start of the channel occupancy per sensing beam where each sensing beam covers a transmission beam within the channel occupancy. When the channel is accessed, the transmission within the channel occupancy across different beams can occur following the procedures described in Clause 4.4.3. +- When the gNB/UE can perform simultaneous sensing in different beams, Type 1 channel access procedure as described in Clause 4.4.1 is applied before the start of the channel occupancy per sensing beam where each sensing beam covers a transmission beam within the channel occupancy. When the channel is accessed, the transmission within the channel occupancy can occur following the procedures in Clause 4.4.2 before switching to a different beam within the channel occupancy. + +When the gNB intends to transmit a DL transmission(s) across multiple transmission beams, if the gNB performs sensing on the corresponding sensing beam(s) independently, the DL transmission(s) can occur on a transmission beam(s) among the multiple transmission beams if the channel access procedures on the corresponding sensing beam(s) have succeeded, and the channel occupancy would start at the same time across the multiple transmission beams. + +When a UE is scheduled by a DCI to transmit a UL transmission(s), the scheduling DCI may indicate the corresponding channel access procedures for the UL transmission(s) as described in [10]. The UE determines based on the DCI if Type 1, or Type 2, or Type 3 channel access procedures described in Clause 4.4.1, Clause 4.4.2 and Clause 4.4.3, respectively, is applicable. + +When a UE is scheduled with a set of consecutive UL transmissions, the following are applicable: + +- The UE is not expected to be indicated with different channel access types for any consecutive UL transmissions without gaps in between the transmissions. +- If the UE cannot access the channel for a transmission in the set prior to the last transmission according to one of Type 1 or Type 2 channel access procedures, the UE shall attempt to transmit the next transmission according to the channel access type indicated in the corresponding UL grant or DL assignment. +- If a UE is scheduled to transmit a set of consecutive UL transmissions without gaps including PUSCH using one or more UL grant(s), PUCCH using one or more DL grant(s), or SRS with one or more DL grant(s) or UL grant(s) and the UE transmits one of the scheduled UL transmissions in the set after accessing the channel according to one of Type 1, Type 2, or Type 3 channel access procedures, the UE may continue transmission of the remaining UL transmissions in the set, if any. + +### 4.4.1 Type 1 channel access procedures + +This clause describes channel access procedures to be performed by a gNB/UE where the time duration spanned by the sensing slots that are sensed to be idle before a transmission(s) is random based on a fixed contention window size. The clause is applicable to any transmission initiating a channel occupancy by the gNB/UE. + +The gNB/UE may transmit a transmission after first sensing the channel to be idle during the sensing slot duration of a defer duration $T_d$ and after the counter $N$ is zero in step 4. The counter $N$ is adjusted by sensing the channel for additional sensing slot duration(s) according to the steps below: + +- 1) set $N = N_{init}$ , where $N_{init}$ is a random number uniformly distributed between 0 and $CW$ , and go to step 4; +- 2) if $N > 0$ and the gNB/UE chooses to decrement the counter, set $N = N - 1$ ; + +- 3) sense the channel for an additional sensing slot duration, and if the channel is idle for the additional sensing slot duration, go to step 4; else, go to step 5; +- 4) if $N = 0$ , stop; else, go to step 2. +- 5) sense the channel until either it is detected busy within an additional defer duration $T_d$ or it is detected to be idle for the sensing slot of the additional defer duration $T_d$ ; +- 6) if the channel is sensed to be idle during the sensing slot duration of the additional defer duration $T_d$ , go to step 4; else, go to step 5; + +If the gNB/UE has not transmitted a transmission after step 4 in the procedure above, the gNB/UE may transmit a transmission on the channel if the channel is sensed to be idle at least in a sensing slot duration $T_{sl}$ immediately before this transmission. If the channel has not been sensed to be idle in a sensing slot duration $T_{sl}$ immediately before this intended transmission, the gNB/UE proceeds to step 1 after sensing the channel to be idle during the sensing slot durations of a defer duration $T_d$ . + +In the above procedures, $CW$ is the contention window and $CW = 3$ . + +The defer duration is $T_d = 8\mu s$ that ends with a sensing slot of a duration $T_{sl} = 5\mu s$ for performing at least a single measurement to determine whether the channel is idle. + +A gNB/UE shall not transmit on a channel for a *Channel Occupancy Time* that exceeds 5ms. + +A UE may be scheduled to apply Type 1 channel access procedures for a UL transmission(s) before indicating the corresponding capability. The UE discards the UL transmission(s) if it is not capable of performing Type 1 channel access procedures. + +### 4.4.2 Type 2 channel access procedures + +This clause describes channel access procedures to be performed by a gNB/UE where the time duration spanned by sensing slots that are sensed to be idle before a DL/UL transmission(s) is deterministic. + +A gNB/UE may transmit a transmission(s) on a channel immediately after $T_d$ that ends with a sensing slot of a duration $T_{sl} = 5\mu s$ for performing at least a single measurement to determine the channel is sensed to be idle. + +A UE is not expected to be scheduled to apply Type 2 channel access procedures for a UL transmission(s) before indicating the corresponding capability. + +### 4.4.3 Type 3 channel access procedures + +A gNB/UE may transmit a transmission on a channel without sensing the channel. + +### 4.4.4 Channel access procedures in an initiated channel occupancy + +If a gNB/UE initiates a channel occupancy using the channel access procedures described in clause 4.4.1 on a channel, the gNB/UE may transmit a DL/UL transmission(s) that is followed by a UL/DL transmission(s) within the maximum *Channel Occupancy Time* described in Clause 4.4.1. The followings are applicable to the UL/DL transmission(s): + +- The transmission bandwidth(s) corresponding to the UL/DL transmission(s) shall be within the DL/UL bandwidth part(s) where in the channel occupancy is initiated; +- Regardless of the duration of the gap between the UL/DL transmission(s) and previous DL/UL transmission(s) on the channel, the UL/DL transmission(s) occurs following the procedures described in Clause 4.4.3; or +- if the gap between the UL/DL transmission(s) and previous DL/UL transmission(s) on the channel is more than a threshold that is determined by the gNB and is at least $8\mu s$ , the UL/DL transmission(s) occurs following the procedures described in Clause 4.4.2. Otherwise, the UL/DL transmission(s) occurs following the procedures described in Clause 4.4.3. + +If a gNB initiates a channel occupancy using the channel access procedures described in clause 4.4.1 on a channel, the gNB may transmit a DL transmission(s) on the channel within the maximum *Channel Occupancy Time* described in + +Clause 4.4.1 on the channel after the DL transmission(s) initiating the channel occupancy. The followings are applicable to the DL transmission(s): + +- Regardless of the duration of the gap between the DL transmission(s) and any previous transmission(s) corresponding to the channel occupancy initiated by the gNB, the DL transmission(s) occurs following the procedures described in Clause 4.4.3; or +- if the gap between the DL transmission(s) and any previous transmission(s) corresponding to the channel occupancy initiated by the gNB is more than a threshold that is determined by the gNB and is at least $8\mu\text{s}$ , the DL transmission(s) occurs following the procedures described in Clause 4.4.2. + +If a gNB shares a channel occupancy initiated by a UE using the channel access procedures described in clause 4.4.1 on a channel, the gNB may transmit a transmission on the channel that follows a scheduled UL transmission or a configured PUSCH transmission by the UE if the following conditions are satisfied: + +- The DL transmission shall contain transmission to the UE that initiated the channel occupancy and can include non-unicast and/or unicast transmissions where any unicast transmission that includes user plane data is only transmitted to the UE that initiated the channel occupancy. + +When a UE is provided *cg-COT-SharingList-r17* by higher layers, the UE is configured with a table wherein each row is given by higher layer parameter *CG-COT-Sharing-r17*. One row of the table is configured for indicating that the channel occupancy sharing is not available and other rows of the table each provides a channel occupancy sharing information. In this case, each configured grant PUSCH transmission includes 'COT sharing information' in CG-UCI as described in [10] that indicates a row index to the table. + +If a gNB shares a channel occupancy initiated by a UE using configured grant PUSCH transmission and the UE is configured by *cg-COT-SharingList-r17*, the gNB may transmit a transmission that follows the configured grant PUSCH transmission by the UE if the following conditions are satisfied: + +- If the gNB determines that the 'COT sharing information' in CG-UCI in slot $n$ indicates a row index that corresponds to a *CG-COT-Sharing-r17* that provides channel occupancy sharing information, the gNB can share the UE channel occupancy starting from slot $n + O$ , where $O = \text{offset-r17}$ slots, for a duration of $D = \text{duration-r17}$ slots where *duration-r17*, and *offset-r17* are higher layer parameters provided by *CG-COT-Sharing-r17*. + +### 4.4.5 Exempted transmissions from sensing + +In regions where channel sensing is required to access a channel for transmission and short control signalling exemption is allowed by regulation, a gNB/UE may transmit the following transmission(s) on a channel without sensing the channel: + +- Transmission(s) of the discovery burst by the gNB +- If the higher layer parameter *ra-ChannelAccess-r17* is not configured, transmission(s) of the first message in a random access procedure by the UE + +When the gNB/UE transmits the above transmission(s) without sensing on a channel by utilizing the exemption above, the total duration of such transmission(s) by the gNB/UE shall not occupy the corresponding channel more than $10\text{ms}$ over any $100\text{ms}$ interval. + +### 4.4.6 Channel access procedures for transmission(s) on multiple channels or beams + +When a gNB/UE intends to transmit a transmission(s) that starts at the same time on a set of channels $\mathcal{C}$ , the gNB/UE performs the channel access procedures described in Clause 4.4.1 on each channel $c_i \in \mathcal{C}$ independently. When the channel access procedures in Clause 4.4.1 are applied on any channel $c_i \in \mathcal{C}$ , the corresponding counter $N$ in step 1 shall be initialized independently and the corresponding sensing on the channel $c_i$ shall be performed after the end of any previous transmission(s) by the gNB/UE occupying any channel $c_j \in \mathcal{C}$ . + +When a gNB/UE intends to transmit a transmission(s) that starts at the same time across multiple transmission beams, if the gNB/UE performs sensing on the corresponding sensing beam(s) independently, the gNB/UE performs the channel access procedures described in Clause 4.4.1 on each sensing beam independently. When the channel access procedures in Clause 4.4.1 are applied on any sensing beam, the corresponding counter $N$ in step 1 shall be initialized + +independently and the corresponding sensing on the sensing beam shall be performed after the end of any previous transmission(s) by the gNB/UE occupying any beam. + +### 4.4.7 Energy detection threshold adaptation procedures + +A gNB/UE accessing a channel on which transmission(s) on beam(s) are performed within a channel occupancy, shall set the energy detection threshold $X_{\text{Thresh}}$ to be less than or equal to the maximum energy detection threshold $X_{\text{Thresh\_max}}$ that is determined as follows: + +$$X_{\text{Thresh\_max}} = -80\text{dBm} + P_{\text{max}} - P_{\text{out}} + 10 \cdot \log 10(BW)$$ + +where: + +- $P_{\text{max}}$ is the RF output power limit in $\text{dBm}$ . +- $P_{\text{out}}$ is the maximum EIRP of the intended transmission(s) by the gNB/UE to acquire a channel occupancy in $\text{dBm}$ where $P_{\text{out}} \leq P_{\text{max}}$ . The maximum EIRP used for the transmission(s) by the initiating gNB/UE during the channel occupancy is limited to $P_{\text{out}}$ . +- $BW$ is the channel bandwidth in MHz. + +## 4.5 Sidelink Channel access procedures + +A UE operating in sidelink resource allocation mode 1 or mode 2 and performing SL transmission(s) on channel(s) shall perform the procedures described in this clause for the UE to access the channel(s) on which the transmission(s) are performed. + +In this clause, transmissions from a UE are considered as separate SL transmissions, irrespective of having a gap between transmissions or not, and $X_{\text{Thresh}}$ for sensing is adjusted as described in clause 4.5.5 when applicable. + +A UE can access a channel on which SL transmission(s) are performed according to one of Type 1 or Type 2 SL channel access procedures as described in clauses 4.5.1 and 4.5.2, respectively. + +When a UE applies Type 1 channel access procedures to transmit SL transmission(s), the applicable channel access priority class (CAPC) is defined in Table 4.5-1. + +When a UE applies Type 1 channel access procedures to transmit SL transmission(s) including PSSCH with user plane data and associated PSCCH, the UE determines the corresponding SL channel access priority class $p$ in Table 4.5-1 following the procedures described in Clause 16.9.x.2 in [9]. + +When a UE applies Type 1 channel access procedures to transmit SL transmission(s) including only PSFCH or only S-SSB transmission(s), the UE shall use the channel access priority class $p = 1$ in Table 4.5-1. + +A UE shall not transmit on a channel for a *Channel Occupancy Time* that exceeds $T_{\text{slm cot}, p}$ where the channel access procedure is performed based on the channel access priority class $p$ associated with the UE transmissions, as given in Table 4.5-1. + +When a UE applies Type 1 channel access procedure to initiate a channel occupancy for multiple SL transmissions over one slot or multiple consecutive slots, the highest CAPC value among the associated CAPC values with the multiple SL transmissions is used for performing the Type 1 channel access procedure. + +If a UE fails to access the channel(s) prior to an intended SL transmission(s), Layer 1 notifies higher layers about the channel access failure and the channel(s) that the UE fails to access. + +**Table 4.5-1: Channel Access Priority Class (CAPC) for SL** + +| Channel Access Priority Class ( $p$ ) | $m_p$ | $CW_{min,p}$ | $CW_{max,p}$ | $T_{slm\ cot,p}$ | allowed $CW_p$ sizes | +|---------------------------------------|-------|--------------|--------------|------------------|-----------------------------| +| 1 | 2 | 3 | 7 | 2 ms | {3,7} | +| 2 | 2 | 7 | 15 | 4 ms | {7,15} | +| 3 | 3 | 15 | 1023 | 6ms or 10 ms | {15,31,63,127,255,511,1023} | +| 4 | 7 | 15 | 1023 | 6ms or 10 ms | {15,31,63,127,255,511,1023} | + +NOTE1: For $p = 3,4$ , $T_{slm\ cot,p} = 10\text{ms}$ if the higher layer parameter *sl-absenceOfAnyOtherTechnology-r18* is provided, otherwise, $T_{slm\ cot,p} = 6\text{ms}$ . +NOTE 2: When $T_{slm\ cot,p} = 6\text{ms}$ it may be increased to $8\text{ms}$ by inserting one or more gaps. The minimum duration of a gap shall be $100\mu\text{s}$ . The maximum duration before including any such gap shall be $6\text{ms}$ . + +For contiguous SL transmission(s), the following are applicable: + +- If a UE is scheduled or autonomous selected to transmit a set of SL transmissions using one or more selected SL grant(s), and +- if the UE cannot access the channel for a transmission in the set prior to the last transmission according to Type 1 or Type 2 SL channel access procedures, the UE shall attempt to transmit the next transmission according to Type 1 or Type 2 SL channel access procedures. +- if the UE cannot access the channel for a transmission in the set prior to the last transmission according to Type 2B SL channel access procedure, the UE shall attempt to transmit the next transmission according to Type 2A SL channel access procedure. + +For SL transmission(s) with multiple starting positions in a slot, the following are applicable: + +- If a UE intends to transmit PSCCH/PSSCH in sidelink resource allocation mode 1 or mode 2 using a Type 1 channel access procedure, and if the UE cannot access the channel for the transmission from the 1st starting symbol of a slot, the UE shall attempt to transmit PSCCH/PSSCH from the 2nd starting symbol in the same slot according to Type 1 channel access procedure. There is no limit on the number of attempts the UE can make using Type 1 channel access procedure. +- If a UE intends to transmit PSCCH/PSSCH in sidelink resource allocation mode 1 or mode 2 using a Type 2 channel access procedure, and if the UE cannot access the channel for the transmission from the 1st starting symbol of a slot, the UE may attempt to transmit PSCCH/PSSCH from the 2nd starting symbol in the same slot and according to Type 2 channel access procedure. + +### 4.5.1 Type 1 SL channel access procedure + +This clause describes channel access procedures by a UE where the time duration spanned by the sensing slots that are sensed to be idle before a SL transmission(s) is random. The clause is applicable to the SL transmission(s) including at least any of PSSCH/PSCCH or PSFCH or S-SSB. + +A UE may transmit the transmission using Type 1 channel access procedure after first sensing the channel to be idle during the sensing slot durations of a defer duration $T_d$ , and after the counter $N$ is zero in step 4. The counter $N$ is adjusted by sensing the channel for additional sensing slot duration(s) according to the steps described below. + +- 1) set $N = N_{init}$ , where $N_{init}$ is a random number uniformly distributed between 0 and $CW_p$ , and go to step 4; +- 2) if $N > 0$ and the UE chooses to decrement the counter, set $N = N - 1$ ; +- 3) sense the channel for an additional sensing slot duration, and if the additional sensing slot duration is idle, go to step 4; else, go to step 5; +- 4) if $N = 0$ , stop; else, go to step 2. +- 5) sense the channel until either a busy sensing slot is detected within an additional defer duration $T_d$ or all the sensing slots of the additional defer duration $T_d$ are detected to be idle; + +- 6) if the channel is sensed to be idle during all the sensing slot durations of the additional defer duration $T_d$ , go to step 4; else, go to step 5; + +If a UE has not transmitted a SL transmission on a channel on which SL transmission(s) are performed after step 4 in the procedure above, the UE may transmit a transmission on the channel, if the channel is sensed to be idle at least in a sensing slot duration $T_{sl}$ when the UE is ready to transmit the transmission and if the channel has been sensed to be idle during all the sensing slot durations of a defer duration $T_d$ immediately before the transmission. If the channel has not been sensed to be idle in a sensing slot duration $T_{sl}$ when the UE first senses the channel after it is ready to transmit, or if the channel has not been sensed to be idle during any of the sensing slot durations of a defer duration $T_d$ immediately before the intended transmission, the UE proceeds to step 1 after sensing the channel to be idle during the sensing slot durations of a defer duration $T_d$ . + +The defer duration $T_d$ consists of duration $T_f = 16\mu s$ immediately followed by $m_p$ consecutive sensing slot durations where each sensing slot duration is $T_{sl} = 9\mu s$ , and $T_f$ includes an idle sensing slot duration $T_{sl}$ at start of $T_f$ . + +$CW_{min,p} \leq CW_p \leq CW_{max,p}$ is the contention window. $CW_p$ adjustment is described in clause 4.5.4. + +$CW_{min,p}$ and $CW_{max,p}$ are chosen before step 1 of the procedure above. + +$m_p$ , $CW_{min,p}$ , and $CW_{max,p}$ are based on a channel access priority class $p$ as shown in Table 4.5-1. + +### 4.5.2 Type 2 SL channel access procedure + +This clause describes channel access procedures by UE where the time duration spanned by the sensing slots that are sensed to be idle before a SL transmission(s) is deterministic. + +Type 2A SL channel access procedure as described in clause 4.5.2.1 is applicable to the following transmission(s) performed by a UE: + +- If a UE intends to transmit a SL transmission at least $25\mu s$ after a SL transmission by another UE in a shared channel occupancy as described in clause 4.5.3, the UE uses Type 2A SL channel access procedures for the SL transmission. +- If a UE intends to transmit only S-SSB in transmission(s) where the time duration of S-SSB transmission(s) is at most $1ms$ with a duty cycle of at most $1/20$ , the UE uses Type 2A SL channel access procedures for the SL transmission(s). + +When a UE initiates a channel occupancy on a channel to transmit SL transmission(s) within the channel occupancy, if the UE stops transmitting on the channel, the UE can resume SL transmission(s) within the channel occupancy on the channel after performing Type 2A SL channel access procedures as described in clause 4.5.2.1 if the UE continuously senses the channel to be idle before resuming transmission. + +Type 2B or Type 2C SL channel access procedures as described in clauses 4.5.2.2 and 4.5.2.3, respectively, are applicable to the transmission(s) performed by a UE following transmission(s) by a UE after a gap of $16\mu s$ or up to $16\mu s$ , respectively, in a shared channel occupancy as described in clause 4.5.3. + +#### 4.5.2.1 Type 2A SL channel access procedure + +When a UE uses Type 2A SL channel access procedures for a transmission, the UE may transmit the transmission immediately after sensing the channel to be idle for at least a sensing interval $T_{short\_sl} = 25\mu s$ . The interval $T_{short\_sl}$ consists of a duration $T_f = 16\mu s$ immediately followed by one sensing slot and $T_f$ includes a sensing slot at start of $T_f$ . The channel is considered to be idle for $T_{short\_sl}$ if both sensing slots of $T_{short\_sl}$ are sensed to be idle. + +#### 4.5.2.2 Type 2B SL channel access procedure + +When a UE uses Type 2B SL channel access procedures for a transmission, the UE may transmit the transmission immediately after sensing the channel to be idle within a duration of $T_f = 16\mu s$ . $T_f$ includes a sensing slot that occurs within the last $9\mu s$ of $T_f$ . The channel is considered to be idle within the duration $T_f$ if the channel is sensed to be idle for total of at least $5\mu s$ with at least $4\mu s$ of sensing occurring in the sensing slot. + +#### 4.5.2.3 Type 2C SL channel access procedure + +When a UE uses Type 2C SL channel access procedures for a transmission, the UE does not sense the channel before the transmission. The duration of the corresponding SL transmission is at most $584\mu\text{s}$ . + +### 4.5.3 SL channel access procedures in a shared channel occupancy + +When a UE initiates a channel occupancy using the channel access procedures described in clause 4.5.1 or clause 4.5.6.3 on a channel(s) to transmit SL transmission(s) including PSCCH/PSSCH(s), the UE can provide a channel occupancy sharing information in SL control information that includes at least the Layer 1 source and destination IDs, the corresponding channel access priority class, the remaining channel occupancy duration, and the frequency domain information for the applicable RB set(s) of the channel occupancy. The channel occupancy sharing information can also include additional IDs and associated cast type. The additional IDs includes one pair of Layer 1 source and destination IDs for all cast types, where the source ID is set to the source ID of the UE initiating channel occupancy for unicast and to the reserved bits for groupcast and broadcast. The channel occupancy sharing information transmitted in slot $n$ indicates the remaining channel occupancy duration in a number of slot(s) $K$ . If $K = 0$ , the initiated channel occupancy by the UE shall not be shared for SL transmission(s) by other UE(s). Otherwise, the initiated channel occupancy by the UE can be shared for SL transmission(s) by other UE(s) within a duration starting from the end of slot $n$ and ending at slot $n + K$ . + +For the case when a UE transmits SL transmission(s) in a shared channel occupancy initiated by another UE, the channel access priority class value corresponding to the SL transmission(s) is at most equal to the channel access priority class value provided by the channel access priority class in the channel occupancy sharing information. + +When a UE initiates a channel occupancy to transmit SL transmission(s) within a RB set(s) and provides channel occupancy sharing information with a unicast PSCCH/PSSCH transmission within the RB set(s), another UE may transmit unicast PSCCH/PSSCH transmission(s) sharing the initiated channel occupancy within the RB set(s), if the destination and source IDs in the corresponding SL control information match the source and destination IDs, respectively, in the unicast PSCCH/PSSCH transmission carrying the channel occupancy information or match a pair of additional source and destination IDs and associated cast type if provided by the channel occupancy sharing information and the corresponding COT sharing cast type indicates '10' value for unicast cast type. Another UE may transmit groupcast or broadcast PSCCH/PSSCH transmissions sharing the initiated channel occupancy within the RB set(s), if the destination ID in the corresponding SL control information matches an additional destination ID and associated cast type if provided by the channel occupancy sharing information and the corresponding COT sharing cast type indicates '00' or '01' value for groupcast or broadcast cast type, respectively. + +When a UE initiates a channel occupancy to transmit SL transmission(s) within a RB set(s) and provides channel occupancy sharing information with a groupcast or broadcast PSCCH/PSSCH transmission within the RB set(s), another UE may transmit a groupcast or broadcast PSCCH/PSSCH transmission(s) sharing the initiated channel occupancy within the RB set(s), if the destination ID in the corresponding SL control information matches the destination ID in the groupcast or broadcast PSCCH/PSSCH transmission carrying the channel occupancy sharing information or matches an additional destination ID and associated cast type if provided by the channel occupancy sharing information and the corresponding COT sharing cast type indicates '00' or '01' value for groupcast or broadcast cast type, respectively. Another UE may transmit unicast PSCCH/PSSCH transmissions sharing the initiated channel occupancy within the RB set(s), if the destination and source IDs in the corresponding SL control information match a pair of additional source and destination IDs and associated cast type if provided by the channel occupancy sharing information and the corresponding COT sharing cast type indicates '10' value for unicast cast type. + +When a UE initiates a channel occupancy to transmit SL transmission(s) within a RB set(s) and provides channel occupancy sharing information with a PSSCH/PSCCH transmission within the RB set(s), another UE may transmit a S-SSB transmission(s) sharing the initiated channel occupancy within the RB set(s). + +When a UE initiates a channel occupancy to transmit SL transmission(s) within a RB set(s) and provides channel occupancy sharing information with a unicast PSCCH/PSSCH transmission within the RB set(s), for a given PSFCH transmission occasion, another UE may transmit PSFCH(s) within the RB set(s) sharing the initiated channel occupancy using the channel access procedures described in clause 4.5.2, if for at least one PSFCH in the given transmission occasion, the source and destination IDs in the corresponding unicast PSCCH/PSSCH's SL control information match the source and destination IDs, respectively, in the unicast PSCCH/PSSCH transmission carrying the channel occupancy information or match a pair of additional source and destination IDs and associated cast type if provided by the channel occupancy sharing information and the corresponding COT sharing cast type indicates '10' value for unicast cast type. + +When a UE initiates a channel occupancy to transmit SL transmission(s) within a RB set(s) and provides channel occupancy sharing information with a groupcast PSCCH/PSSCH transmission within the RB set(s), for a given PSFCH transmission occasion, another UE may transmit PSFCH(s) within the RB set(s) sharing the initiated channel occupancy using the channel access procedures described in clause 4.5.2, if for at least one PSFCH in the given transmission occasion, the source and destination ID in the corresponding groupcast PSCCH/PSSCH's SL control information matches the source and destination ID in the groupcast PSCCH/PSSCH transmission carrying the channel occupancy sharing information. For a given PSFCH transmission occasion, another UE may transmit PSFCH(s) within the RB set(s) sharing the initiated channel occupancy using the channel access procedures described in clause 4.5.2, if for at least one PSFCH in the given transmission occasion, the source and destination IDs in the corresponding unicast PSCCH/PSSCH's SL control information match a pair of additional source and destination IDs and associated cast type if provided by the channel occupancy sharing information and the corresponding COT sharing cast type indicates '10' value for unicast cast type. + +If a UE shares a channel occupancy initiated by another UE using the channel access procedures described in clause 4.5.1 on a channel to transmit SL transmission(s), the UE may transmit a SL transmission that follows the SL transmission by the UE that has initiated the channel occupancy after a transmission gap as follows: + +- If the transmission gap is at least $25\mu\text{s}$ , the UE can transmit the SL transmission on the channel after performing Type 2A channel access procedures as described in clause 4.5.2.1. +- If the transmission gap is $16\mu\text{s}$ , the UE can transmit the SL transmission on the channel after performing Type 2B channel access procedures as described in clause 4.5.2.2. +- If the transmission gap is up to $16\mu\text{s}$ , the UE can transmit the SL transmission on the channel after performing Type 2C channel access as described in clause 4.5.2.3. + +When a UE uses channel access procedures to initiate a channel occupancy to transmit SL transmission(s) and shares the corresponding channel occupancy with another UE that transmits a SL transmission(s), the UE that has initiated the channel occupancy may transmit a SL transmission(s) within its channel occupancy that follows the SL transmission(s) from the other UE, as the following. + +- If the UE determines a transmission gap from the other UE's SL transmission(s), the followings are applicable: + - If the transmission gap is at least $25\mu\text{s}$ , the UE can transmit the SL transmission on the channel after performing Type 2A channel access procedures as described in clause 4.5.2.1. + - If the transmission gap is $16\mu\text{s}$ , the UE can transmit the SL transmission on the channel after performing Type 2B channel access procedures as described in clause 4.5.2.2. + - If the transmission gap is up to $16\mu\text{s}$ , the UE can transmit the SL transmission on the channel after performing Type 2C channel access as described in clause 4.5.2.3. +- Otherwise, the UE can transmit the SL transmission on the channel after performing Type 2A channel access procedures as described in clause 4.5.2.1. + +When a UE initiates a channel occupancy using the channel access procedures described in clause 4.5.6.3 to transmit SL transmission(s) on a set of RB sets, the channel occupancy can be shared with other UEs when the initiating UE transmits PSCCH/PSSCH in the SL transmission(s), and the channel occupancy time of each channel(s) is the same. + +### 4.5.4 Contention window adjustment procedures for SL transmissions + +If a UE transmits a SL transmission(s) including at least one PSSCH using Type 1 channel access procedures associated with the channel access priority class $p$ on a channel, the UE maintains the contention window value $CW_p$ and adjusts $CW_p$ before step 1 of the procedure described in clause 4.5.1 for the SL transmission(s) applying the following procedures: + +- 1) For every priority class $p \in \{1,2,3,4\}$ , set $CW_p = CW_{min,p}$ . +- 2) If a HARQ-ACK feedback corresponding to the PSSCH(s) for unicast SL transmission(s) in the reference duration for the latest channel occupancy initiated by the UE, is available: + - If the HARQ-ACK feedback includes only 'ACK', go to step 1; otherwise go to step 5. + +- 3) If a HARQ-ACK feedback corresponding to the PSSCH(s) for groupcast SL transmission(s) in the *reference duration* for the latest channel occupancy initiated by the UE, is available: + - If HARQ-ACKFeedbackRatioforContentionWindowAdjustment-GC-Option2 is provided by higher layers: + - The UE calculates the ratio between the number of received 'ACK' in the HARQ-ACK feedback and the number of UE(s) from which the corresponding 'ACK'/'NACK' in the HARQ-ACK feedback is expected. If the calculated ratio is equal to or larger than *HARQ-ACKFeedbackRatioforContentionWindowAdjustment-GC-Option2*, go to step 1; otherwise go to step 5. + - Otherwise: + - If the HARQ-ACK feedback includes at least an 'ACK', go to step 1; otherwise go to step 5. +- 4) If a HARQ-ACK feedback corresponding to the PSSCH(s) in the reference duration for the latest channel occupancy initiated by the UE is not available, go to step 6. +- 5) Increase $CW_p$ for every priority class $p \in \{1,2,3,4\}$ to the next higher allowed value. +- 6) For every priority class $p \in \{1,2,3,4\}$ , maintain $CW_p$ as it is; go to step 2. + +The *reference duration* in the procedure above is defined as follows: + +- The *reference duration* corresponding to a channel occupancy initiated by the UE including SL transmission(s) of PSSCH(s) is defined in this clause as a duration starting from the beginning of the channel occupancy initiated by the UE including SL transmission(s) of PSSCH(s) until the end of the first slot where at least one PSSCH with HARQ-ACK feedback(s) including 'ACK'/'NACK' is transmitted. + +If a UE transmits a SL transmission(s) using Type 1 channel access procedures associated with the channel access priority class $p$ on a channel and the SL transmission(s) is not associated with explicit HARQ-ACK feedback(s) by the corresponding UE(s), the UE adjusts $CW_p$ before step 1 in the procedures described in clause 4.5.1, using the latest $CW_p$ used for any SL transmissions on the channel using Type 1 channel access procedures associated with the channel access priority class $p$ . If the corresponding channel access priority class $p$ has not been used for any SL transmissions on the channel, $CW_p = CW_{min,p}$ is used. If the latest $CW_p \neq CW_{max,p}$ value is consecutively used for X times provided by higher layers parameter [*sl-CWSforPsschWithoutHarqAck*] for generation of $N_{init}$ as described in clause 4.5.1 for PSSCH transmission(s) without associated explicit HARQ-ACK feedback(s), the $CW_p$ is increased for every priority class $p \in \{1,2,3,4\}$ to the next higher allowed value. + +The following applies to the procedures described in this clause for contention window adjustment: + +- If $CW_p = CW_{max,p}$ , the next higher allowed value for adjusting $CW_p$ is $CW_{max,p}$ . +- If the $CW_p = CW_{max,p}$ is consecutively used $K$ times for generation of $N_{init}$ , $CW_p$ is reset to $CW_{min,p}$ only for that priority class $p$ for which $CW_p = CW_{max,p}$ is consecutively used $K$ times for generation of $N_{init}$ . $K$ is selected by UE from the set of values $\{1, 2, \dots, 8\}$ for each priority class $p \in \{1,2,3,4\}$ . + +### 4.5.5 Energy detection threshold adaptation procedure + +A UE accessing a channel on which SL transmission(s) are performed, shall set the energy detection threshold ( $X_{Thresh}$ ) to be less than or equal to the maximum energy detection threshold $X_{Thresh\_max}$ . + +$X_{Thresh\_max}$ is determined as follows: + +- If the UE is configured with higher layer parameter *sl-maxEnergyDetectionThreshold-r18*, + - $X_{Thresh\_max}$ is set equal to the value signalled by the higher layer parameter; +- otherwise + - the UE shall determine $X'_{Thresh\_max}$ according to the procedure described in clause 4.5.5.1; + - if the UE is configured with higher layer parameter *sl-energyDetectionThresholdOffset-r18* + +- $X_{\text{Thresh\_max}}$ is set by adjusting $X'_{\text{Thresh\_max}}$ according to the offset value signalled by the higher layer parameter; +- otherwise +- the UE shall set $X_{\text{Thresh\_max}} = X'_{\text{Thresh\_max}}$ . + +If the higher layer parameter *sl-absenceOfAnyOtherTechnology-r18* is not configured to a UE, the UE that performs channel access procedures to initiate a channel occupancy to be shared to other UE(s), and another UE that shares the initiated channel occupancy as described in clause 4.5.3 shall use the (pre-)configured *ue-toUE-COT-SharingED-Threshold* for accessing the channel(s). + +For the case where a UE performs channel access procedures as described in clause 4.5.1 for SL transmission(s) and indicates channel occupancy sharing information, $X_{\text{Thresh\_max}}$ is set equal to the value provided by the higher layer parameter *ue-toUE-COT-SharingED-Threshold*. + +#### 4.5.5.1 Default maximum energy detection threshold computation procedure + +If the higher layer parameter *sl-absenceOfAnyOtherTechnology-r18* is provided + +- $X'_{\text{Thresh\_max}} = \min \left\{ \begin{matrix} T_{\max} + 10\text{dB} \\ X_r \end{matrix} \right\}$ where +- $X_r$ is Maximum energy detection threshold defined by regulatory requirements in dBm when such requirements are defined, otherwise $X_r = T_{\max} + 10\text{dB}$ + +otherwise + +- $$X'_{\text{Thresh\_max}} = \max \left\{ \begin{matrix} -72 + 10 \cdot \log 10 (BW\text{MHz} / 20\text{MHz}) \text{ dBm}, \\ \min \left\{ \begin{matrix} T_{\max}, \\ T_{\max} - T_A + (P_H + 10 \cdot \log 10 (BW\text{MHz} / 20\text{MHz}) - P_{TX}) \end{matrix} \right\} \end{matrix} \right\}$$ + +where + +- $T_A = 5\text{dB}$ if Type 2A SL channel access procedures is performed for a SL transmission(s) that initiates a channel occupancy and includes only S-SSB as described in clause 4.5.2; otherwise $T_A = 10\text{dB}$ ; +- $P_H = 23\text{dBm}$ ; +- $P_{TX}$ is set to the value of $P_{\text{CMAX\_H,c}}$ as defined in [3]; +- $T_{\max}(\text{dBm}) = 10 \cdot \log 10 (3.16228 \cdot 10^{-8} (\text{mW/MHz}) \cdot BW\text{MHz} (\text{MHz}))$ ; +- $BW\text{MHz}$ is the single channel bandwidth in MHz. + +The higher layer parameter *sl-absenceOfAnyOtherTechnology-r18* is not expected to be provided if the channel(s) where UE performing SL transmission(s) is overlapped with either an LAA Scell(s) on channel(s) or channel(s) where gNB/UE performing DL/UL transmission(s). + +### 4.5.6 Channel access procedures for transmission(s) on multiple channels + +If a UE + +- is scheduled to transmit on a set of channels $C$ , and if the SL transmissions are scheduled to start transmissions at the same time on all channels in the set of channels $C$ , or +- intends to perform sidelink transmissions on configured resources on the set of channels $C$ , and if the SL transmissions are configured to start transmissions at the same time on all channels in the set of channels $C$ , or +- intends to perform sidelink transmissions on selected resources on the set of channel $C$ , and if SL transmissions are to start at the same time on all channels in the set of channels $C$ + +the followings are applicable: + +- Type A or Type B procedures described in clause 4.5.6.1 and 4.5.6.2 can be used for accessing multiple channels only for PSFCH or S-SSB transmissions. +- A UE can access multiple channels on which SL transmissions are performed, according to the procedures described in clause 4.5.6.3. + +When a UE performs Type A or Type B channel access procedures to transmit PSFCH transmissions on multiple RB sets after performing associated prioritization for the PSFCH, if the channel access procedures fail on part of the RB set(s) but succeed on other part of the RB set(s), the UE may transmit the PSFCH transmission(s) on the part of the RB set(s) where the corresponding channel access was successful. + +#### 4.5.6.1 Type A multi-channel access procedures for PSFCH transmissions + +The procedures described in this clause are applicable for PSFCH/S-SSB transmissions. + +A UE shall perform channel access on each channel $c_i \in C$ , according to the procedures described in clause 4.5.1, where $C$ is a set of channels on which the UE intends to transmit, and $i = 0, 1, \dots, q-1$ , and $q$ is the number of channels on which the UE intends to transmit. + +The counter $N$ described in clause 4.5.1 is determined for each channel $c_i$ and is denoted as $N_{c_i}$ . $N_{c_i}$ is maintained according to clause 4.5.6.1.1 or 4.5.6.1.2. + +##### 4.5.6.1.1 Type A1 multi-channel access procedures + +Counter $N$ as described in clause 4.5.1 is independently determined for each channel $c_i$ and is denoted as $N_{c_i}$ . + +If the absence of any other technology sharing the channel cannot be guaranteed on a long term basis (e.g. by level of regulation), when the UE ceases transmission on any one channel $c_j \in C$ , for each channel $c_i \neq c_j$ , the UE can resume decrementing $N_{c_i}$ when idle sensing slots are detected either after waiting for a duration of $4 \cdot T_{sl}$ , or after reinitializing $N_{c_i}$ , for performing channel access procedures, respectively. + +##### 4.5.6.1.2 Type A2 multi-channel access procedures + +Counter $N$ is determined as described in clause 4.5.1 for channel $c_j \in C$ , and is denoted as $N_{c_j}$ , where $c_j$ is the channel that has the largest $CW_p$ value. For each channel $c_i$ , $N_{c_i} = N_{c_j}$ . + +When the UE ceases the PSFCH transmissions, on any one channel for which $N_{c_i}$ is determined, the UE shall reinitialize $N_{c_i}$ for all channels, respectively. + +#### 4.5.6.2 Type B multi-channel access procedures for PSFCH or S-SSB transmissions + +The procedures described in this clause are applicable for PSFCH/S-SSB transmissions. + +A channel $c_j \in C$ is selected by the UE as follows: + +- the UE selects $c_j$ by uniformly randomly choosing $c_j$ from $C$ before each transmission on multiple channels $c_i \in C$ , or +- the UE selects $c_j$ no more frequently than once every 1 second, + +where $C$ is a set of channels on which the UE intends to transmit, $i = 0, 1, \dots, q-1$ , and $q$ is the number of channels on which the UE intends to transmit PSFCH transmissions. + +To transmit on channel $c_j$ + +- the UE shall perform channel access on channel $c_j$ according to the procedures described in clause 4.5.1 with the modifications described in clause 4.5.6.2.1 or 4.5.6.2.2, for accessing the channel to perform PSFCH transmissions. + +To transmit on channel $c_i \neq c_j$ , $c_i \in C$ + +- for each channel $c_i$ , the UE shall sense the channel $c_i$ for at least a sensing interval $T_{mc} = 25\mu s$ immediately before transmitting on channel $c_j$ , and the UE may transmit on channel $c_i$ immediately after sensing the channel $c_i$ to be idle for at least the sensing interval $T_{mc}$ , for accessing the channel to perform PSFCH transmissions. The channel $c_i$ is considered to be idle for $T_{mc}$ if the channel is sensed to be idle during all the time durations in which such idle sensing is performed on the channel $c_j$ in given interval $T_{mc}$ . + +The UE shall not transmit a transmission on a channel $c_i \neq c_j$ , $c_i \in C$ , for a period exceeding $T_{mcot,p}$ as given in Table 4.5-1, where the value of $T_{mcot,p}$ is determined using the channel access parameters used for channel $c_j$ , for accessing the channel to perform PSFCH transmissions. + +For the procedures in this clause, the channels of the set of channels $C$ selected by the UE for PSFCH transmissions, is a subset of the RB sets in the (pre-)configured sidelink resource pool. + +##### 4.5.6.2.1 Type B1 multi-channel access procedure + +A single $CW_p$ value is maintained for the set of channels $C$ . + +##### 4.5.6.2.2 Type B2 multi-channel access procedure + +A $CW_p$ value is maintained independently for each channel $c_i \in C$ using the procedure described in clause 4.5.4. + +For determining $N_{init}$ for channel $c_j$ , $CW_p$ value of channel $c_{j1} \in C$ is used, where $c_{j1}$ is the channel with largest $CW_p$ among all channels in set $C$ . + +#### 4.5.6.3 Multi-channel access procedures for SL transmissions + +The procedures described in this clause are applied for PSCCH/PSSCH/S-SSB transmission(s) and may be applied for PSFCH transmission. + +A UE can access multiple channels on which SL transmissions are performed, according to the procedures described in this clause. + +If a UE intends to transmit SL transmissions on a set of channels $C$ , the following is applicable: + +- if Type 1 channel access procedure is used for SL transmissions on the set of channels $C$ , +- the UE may transmit on channel $c_i \in C$ using Type 2A channel access procedure as described in clause 4.5.2.1, +- if the channel frequencies of the set of channels $C$ is a subset of the sets of channel frequencies defined in clause X.X in [2X], and +- if Type 2A channel access procedure is performed on channel $c_i$ immediately before the UE transmission on channel $c_j \in C$ , $i \neq j$ , and +- if the UE has accessed channel $c_j$ using Type 1 channel access procedure as described in clause 4.5.1, +- where channel $c_j$ is selected by the UE uniformly randomly from the set of channels $C$ before performing Type 1 channel access procedure on any channel in the set of channels $C$ . +- the UE may transmit on channel $c_i \in C$ using Type 1 channel access procedure as described in clause 4.5.1 +- the UE may not transmit on channel $c_i \in C$ within the bandwidth of a carrier, if the UE fails to access any of the channels, of the carrier bandwidth, on which the UE is scheduled or configured with or selects SL resources. +- [the UE may not transmit on a channel within the bandwidth of a carrier if the UE is configured without intra-cell guard band(s) on an SL bandwidth part as described in clause X of [8], and the UE fails to access any of the channels of the SL bandwidth part.] + +A $CW_p$ value is maintained independently for each channel $c_i \in C$ using the procedure described in clause 4.5.4. For determining $CW_p$ for channel $c_i$ , any PSSCH transmission that fully or partially overlaps with any channel $c_i \in C$ is used in the procedures described in clause 4.5.4. + +After a UE successfully performs a multi-channel access procedure for a set of RB sets, a channel occupancy is initiated for the set of RB sets and the UE can use the initiated channel occupancy for own subsequent transmissions (including any of S-SSB, PSFCH or PSCCH/PSSCH). + +# --- Annex X (Informative): Change history + +| Change history | | | | | | | | +|----------------|------------|------------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-04 | RAN1#92bis | R1-1804453 | | | | First version | 0.0.1 | +| 2018-04 | RAN1#92bis | R1-1805351 | | | | Removal of FeLAA agreements | 0.0.2 | +| 2018-04 | RAN1#92bis | R1-1805352 | | | | Addition of FeLAA agreements | 0.0.3 | +| 2018-04 | RAN1#92bis | R1-1805416 | | | | First endorsed version | 0.1.0 | +| 2018-05 | RAN1#92bis | R1-1805788 | | | | Correction to FeLAA agreements and alignment with other specifications | 0.1.1 | +| 2018-05 | RAN1#92bis | R1-1805790 | | | | Second endorsed version | 0.2.0 | +| 2018-05 | RAN1#93 | R1-1807911 | | | | Update based on agreements at RAN1 #93 | 0.2.1 | +| 2018-06 | RAN1#93 | R1-1807932 | | | | Endorsed version | 1.0.0 | +| 2018-06 | RAN#80 | | | | | Spec under change control further to RAN approval decision | 15.0.0 | +| 2018-09 | RAN#81 | RP-181795 | 0001 | 1 | F | Correction on RRC parameters for FeLAA in 37.213 | 15.1.0 | +| 2018-09 | RAN#81 | RP-181795 | 0002 | - | F | Correction on starting position of Partial PUSCH Mode 1 for FeLAA in 37.213 | 15.1.0 | +| 2018-09 | RAN#81 | RP-181795 | 0003 | - | F | Correction on COT length for AUL transmission | 15.1.0 | +| 2019-03 | RAN#83 | RP-190444 | 0004 | - | F | Corrections on channel access procedures in 37.213 | 15.2.0 | +| 2019-12 | RAN#86 | RP-192636 | 0005 | - | B | Introduction of channel access procedures to unlicensed spectrum for NR-based access | 16.0.0 | +| 2020-03 | RAN#87-e | RP-200185 | 0007 | - | F | Corrections to NR-based access to unlicensed spectrum | 16.1.0 | +| 2020-06 | RAN#88-e | RP-200687 | 0008 | - | F | Corrections to NR-based access to unlicensed spectrum | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200687 | 0009 | - | F | Additional corrections to NR-based access to unlicensed spectrum | 16.2.0 | +| 2020-09 | RAN#89-e | RP-201805 | 0010 | - | F | Corrections to NR-based access to unlicensed spectrum | 16.3.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0011 | - | F | CR to 37.213 to correct CP extension and LBT type for SRS | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0012 | - | F | CR to 37.213 CR to correct CAPC for RACH | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0013 | - | F | CR to 37.213 to correct channel access for SRS | 16.4.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0014 | - | F | Correction on LBT for consecutive UL transmission triggered by DL assignments | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0015 | - | F | Correction on LBT Type and CP Extension Indication for Semi-Static Channel Occupancy | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0016 | - | F | Correction on Channel Occupancy Time for Semi-Static Channel Access | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0017 | - | F | Correction on Channel Access for Multi-Channel transmission | 16.5.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0018 | - | F | Correction on the conditions for DL channel access procedure | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0019 | - | F | Clarifying the conditions for indicating Type 2 LBT for wideband scheduled PUSCH | 16.6.0 | +| 2021-12 | RAN#94-e | RP-212961 | 0020 | - | F | UL transmissions in wideband operation | 16.7.0 | +| 2021-12 | RAN#94-e | RP-212961 | 0021 | - | F | Changes of channel access procedure in TS 37.213 according to MIIT regulation | 16.7.0 | +| 2021-12 | RAN#94-e | RP-212961 | 0024 | - | F | Alignment CR for TS 37.213 | 16.7.0 | +| 2021-12 | RAN#94-e | RP-212967 | 0022 | - | B | Introduction of features to extend current NR operation to 71 GHz | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212968 | 0023 | - | B | Introduction of UE initiating a channel occupancy in semi-static channel access mode for enhanced IIoT and URLLC operation on shared spectrum for NR | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220247 | 0026 | - | A | Correction on channel access procedures for consecutive UL transmissions | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220251 | 0027 | - | F | Corrections of the features extending NR operation to 71 GHz | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220252 | 0028 | - | F | Corrections of the semi-static channel access mode with UE initiating channel occupancy | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220247 | 0030 | - | A | Rel-16 editorial corrections for TS 37.213 mirrored to Rel-17 | 17.1.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|----------------------------------------------------------------------------------------|--------| +| 2022-06 | RAN#96 | RP-221601 | 0031 | - | F | Corrections of the features extending NR operation to 71 GHz | 17.2.0 | +| 2022-06 | RAN#96 | RP-221602 | 0032 | - | F | Correction to semi-static channel access procedures for PUSCH scheduled via RAR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221599 | 0034 | - | A | Rel-16 editorial corrections for TS 37.213 (mirrored to Rel-17) | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0035 | 1 | F | Corrections to the conditions for channel sensing in FR2-2 in TS37.213 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222422 | 0036 | - | F | RRC parameter corrections for TS 37.213 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222399 | 0037 | - | A | Rel-16 editorial corrections for TS 37.213 (mirrored to Rel-17) | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222871 | 0040 | - | A | Rel-16 Corrections for sensing slot in channel access procedures (mirrored to Rel-17) | 17.4.0 | +| 2023-03 | RAN#99 | RP-230454 | 0043 | - | A | Corrections to type 2 channel access for UL multi channel access | 17.5.0 | +| 2023-06 | RAN#100 | RP-231220 | 0044 | - | F | Correction on the indication of short control signal | 17.6.0 | +| 2023-06 | RAN#100 | RP-231232 | 0045 | 1 | F | Correction on contention window adjustments | 17.6.0 | +| 2023-09 | RAN#101 | RP-232469 | 0046 | - | B | Introduction of NR Sidelink operation on shared spectrum | 18.0.0 | +| 2023-12 | RAN#102 | RP-233703 | 0049 | - | A | CR on energy detection threshold formula for shared spectrum channel access for Rel-18 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233706 | 0050 | - | F | Maintenance of NR Sidelink operation on shared spectrum | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37320/raw.md b/marked/Rel-18/37_series/37320/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b64eee6b2fbefda202d7c0538822c659f0f5ecc9 --- /dev/null +++ b/marked/Rel-18/37_series/37320/raw.md @@ -0,0 +1,1221 @@ + + +# 3GPP TS 37.320 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2 (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is the tagline "A GLOBAL INITIATIVE" in a smaller, all-caps, sans-serif font. To the right of the "3GPP" text is a small "TM" symbol. + +3GPP logo + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Main concept and requirements ..... | 9 | +| 4.1 General ..... | 9 | +| 5 Functions and procedures..... | 10 | +| 5.1 General procedures..... | 10 | +| 5.1.1 Logged MDT procedures ..... | 10 | +| 5.1.1.1 Measurement configuration ..... | 10 | +| 5.1.1.1.1 Configuration parameters..... | 11 | +| 5.1.1.1.2 Configuration effectiveness..... | 13 | +| 5.1.1.2 Measurement collection..... | 14 | +| 5.1.1.3 Measurement reporting..... | 14 | +| 5.1.1.3.1 Availability Indicator ..... | 14 | +| 5.1.1.3.2 Report retrieval..... | 15 | +| 5.1.1.3.3 Reporting parameters ..... | 16 | +| 5.1.1.4 MDT context handling..... | 18 | +| 5.1.2 Immediate MDT procedures..... | 18 | +| 5.1.2.1 Measurement configuration..... | 18 | +| 5.1.2.2 Measurement reporting..... | 18 | +| 5.1.2.3 MDT context handling during handover and UE context retrieval ..... | 18 | +| 5.1.3 MDT Initiation..... | 19 | +| 5.1.4 UE capabilities..... | 19 | +| 5.1.5 Void..... | 21 | +| 5.1.6 Accessibility measurements ..... | 21 | +| 5.2 E-UTRAN solutions..... | 22 | +| 5.2.1 RRC_CONNECTED..... | 22 | +| 5.2.1.1 Measurements and reporting triggers for Immediate MDT ..... | 22 | +| 5.2.1.2 Enhancement to Radio Link Failure report..... | 23 | +| 5.2.1.3 Detailed Location Information..... | 24 | +| 5.2.2 RRC_IDLE ..... | 24 | +| 5.3 UTRAN solutions..... | 24 | +| 5.3.1 UTRA RRC Connected ..... | 24 | +| 5.3.1.1 Measurements and reporting events for Immediate MDT ..... | 25 | +| 5.3.1.2 Detailed Location Information..... | 26 | +| 5.3.2 UTRA Idle ..... | 26 | +| 5.4 NR solutions..... | 26 | +| 5.4.0 General ..... | 26 | +| 5.4.1 RRC_CONNECTED..... | 26 | +| 5.4.1.1 Measurements and reporting triggers for Immediate MDT ..... | 26 | +| 5.4.1.2 Radio Link Failure report ..... | 27 | +| 5.4.1.3 Immediate MDT for MR-DC..... | 29 | +| 5.4.2 RRC_IDLE & RRC_INACTIVE..... | 29 | +| 5.4.2.1 General..... | 29 | +| 5.4.2.2 Logging of on-demand SI request related information..... | 30 | +| 5.4.3 Support of NPN ..... | 30 | + +**Annex A (informative): Coverage use cases ..... 31** + +**Annex B (informative): QoS verification use cases ..... 32** + +**Annex C (informative): Measurements..... 33** + +**Annex D (informative): MBSFN use cases..... 34** + +**Annex E (informative): Change history ..... 35** + +# --- 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 provides an overview and overall description of the minimization of drive tests functionality. + +The document describes functions and procedures to support collection of UE-specific measurements for MDT using Control Plane architecture, for UTRAN, E-UTRAN and NR. + +Details of the signalling procedures for single-RAT operation are specified in the appropriate radio interface protocol specification. Network operation and overall control of MDT is described in OAM specifications. + +NOTE: The focus is on conventional macro cellular network deployments. In the current release no specific support is provided for H(e)NB deployments. + +# 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.133: "Requirements for support of radio resource management (FDD)". +- [3] 3GPP TS 36.133: "Requirements for support of radio resource management (FDD)". +- [4] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification". +- [5] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [6] 3GPP TS 32.422: "Subscriber and equipment trace; Trace control and configuration management". +- [7] 3GPP TS 25.215: "Physical Layer; Measurements (FDD)". +- [8] 3GPP TS 25.225: "Physical Layer; Measurements (TDD)". +- [9] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer; Measurements". +- [10] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC); Protocol Specification". +- [11] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures". +- [12] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2". +- [13] 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 – Measurements". +- [14] 3GPP TS 25.321: "Medium Access Control (MAC) Protocol Specification". +- [15] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". + +- [16] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [17] 3GPP TS 28.552: "Technical Specification Group Services and System Aspects; Management and orchestration; 5G performance measurements". +- [18] 3GPP TS 38.314: "NR; Layer 2 Measurements". +- [19] 3GPP TS 38.215: " NR; Physical layer measurements". +- [20] 3GPP TS 38.213: " NR; Physical layer procedures for control". +- [21] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [22] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2". + +# --- 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] apply. + +**Immediate MDT:** MDT functionality involving measurements performed by the UE in CONNECTED state and reporting of the measurements to RAN available at the time of reporting condition as well as measurements by the network for MDT purposes. + +**Logged MDT:** MDT functionality involving measurement logging by UE in IDLE mode, INACTIVE state, CELL\_PCH, URA\_PCH states and CELL\_FACH state when second DRX cycle is used (when UE is in UTRA) for reporting to eNB/RNC/gNB at a later point in time, and logging of MBSFN measurements by E-UTRA UE in IDLE and CONNECTED modes. + +**Management Based MDT PLMN List:** MDT PLMN List applicable to management based MDT. + +**MDT measurements:** Measurements determined for MDT. + +**MDT PLMN List:** A list of PLMNs where MDT is allowed for a user. It is a subset of the EPLMN list and RPLMN at the time when MDT is initiated. + +**Signalling Based MDT PLMN List:** MDT PLMN List applicable to signalling based MDT. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +| | | +|----------|---------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 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]. + +| | | +|-------|-------------------------------| +| ACK | Acknowledgement | +| AICH | Acquisition Indicator CHannel | +| BLER | Block Error Rate | +| BSSID | Basic Service Set Identifier | +| CA | Carrier Aggregation | +| CDMA | Code Division Multiple Access | +| CHO | Conditional Handover | +| CN | Core Network | +| CPICH | Common Pilot CHannel | + +| | | +|---------|----------------------------------------------------------| +| DAPS | Dual Active Protocol Stack | +| DCH | Dedicated CHannel | +| DL | Downlink | +| DRX | Discontinuous Reception | +| ECGI | E-UTRAN Cell Global Identifier | +| E-CID | Enhanced Cell-ID (positioning method) | +| E-DCH | Enhanced Uplink DCH | +| EDGE | Enhanced Data rates for GSM Evolution | +| E-RUCCH | E-DCH Random Access Uplink Control CHannel | +| eNB | Evolved NodeB | +| EPLMN | Equivalent PLMN | +| E-UTRA | Evolved UTRA | +| E-UTRAN | Evolved UTRAN | +| FACH | Forward Access CHannel | +| FDD | Frequency Division Duplex | +| FIFO | First Input First Output | +| FPACH | Fast Physical Access CHannel | +| GERAN | GSM EDGE Radio Access Network | +| gNB | Next Generation Node B | +| GNSS | Global Navigation Satellite System | +| HESSID | Homogenous Extended Service Set Identifier | +| HOF | Handover Failure | +| IMEI-SV | International Mobile Equipment Identity Software Version | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | +| ISCP | Interference on Signal Code Power | +| LA | Location Area | +| LTE | Long Term Evolution | +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast Multicast Service | +| MBSFN | MBMS Single Frequency Network | +| MDT | Minimization of Drive-Tests | +| NG-RAN | Next Generation RAN | +| NPN | Non-Public Network | +| NR | New Radio | +| OAM | Operation and Maintenance | +| P-CCPCH | Primary Physical Common Control CHannel | +| PCH | Paging CHannel | +| PCI | Physical Cell Id | +| PDCP | Packet Data Convergence Protocol | +| PH | Power Headroom | +| PLMN | Public Land Mobile Network | +| PNI-NPN | Public Network Integrated Non-Public Network | +| PS | Packet Switched | +| QCI | QoS Class Identifier | +| QoS | Quality of Service | +| RA | Routing Area | +| RAB | Radio Access Bearer | +| RAT | Radio Access Technology | +| RB | Radio Bearer | +| RF | Radio Frequency | +| RLC | Radio Link Control | +| RLF | Radio Link Failure | +| RNC | Radio Network Controller | +| RPLMN | Registered PLMN | +| RRC | Radio Resource Control | +| RRM | Radio Resource Management | +| RSCP | Received Signal Code Power | +| RSRP | Reference Signal Received Power | +| RSRQ | Reference Signal Received Quality | +| RSSI | Received Signal Strength Indicator | +| RTT | Round Trip Time | + +| | | +|-------|--------------------------------------------| +| RTWP | Received Total Wideband Power | +| SCell | Secondary Cell | +| SIR | Signal to Interference Ratio | +| SINR | Signal to Noise plus Interference Ratio | +| SNPN | Stand-alone Non-Public Network | +| SNR | Signal to Noise Ratio | +| SON | Self Organizing/Optimizing Network | +| SRB | Signalling Radio Bearer | +| SRNC | Serving RNC | +| SSB | Synchronization Signal Block | +| SSID | Service Set Identifier | +| TA | Tracking Area | +| TCE | Trace Collection Entity | +| TDD | Time Division Duplex | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunication System | +| UPH | Uplink PH | +| URA | UTRAN Registration Area | +| UTRA | Universal Terrestrial Radio Access | +| UTRAN | Universal Terrestrial Radio Access Network | + +# --- 4 Main concept and requirements + +## 4.1 General + +The general principles and requirements guiding the definition of functions for Minimization of drive tests are the following: + +### 1. MDT mode + +There are two modes for the MDT measurements: Logged MDT and Immediate MDT. There are also cases of measurement collection not specified as either immediate or logged MDT, such as Accessibility measurements. + +### 2. UE measurement configuration + +It is possible to configure MDT measurements for the UE logging purpose independently from the network configurations for normal RRM purposes. However, in most cases, the availability of measurement results is conditionally dependent on the UE RRM configuration. + +### 3. UE measurement collection and reporting + +UE MDT measurement logs consist of multiple events and measurements taken over time. The time interval for measurement collection and reporting is decoupled in order to limit the impact on the UE battery consumption and network signalling load. + +### 4. Geographical scope of measurement logging + +It is possible to configure the geographical area where the defined set of measurements shall be collected. + +### 5. Location information + +The measurements shall be linked to available location information and/or other information or measurements that can be used to derive location information. + +### 6. Time information + +The measurements in measurement logs shall be linked to a time stamp. + +### 7. Sensor information + +The measurements can be linked to available sensor information that can be used to derive UE orientation in a global coordinate system, the uncompensated barometric pressure and the UE speed. + +### 8. UE capability information + +The network may use UE capabilities to select terminals for MDT measurements. + +### 9. Dependency on SON + +The solutions for MDT are able to work independently from SON support in the network. Relation between measurements/solution for MDT and UE side SON functions shall be established in a way that re-use of functions is achieved where possible. + +### 10. Dependency on TRACE + +The subscriber/cell trace functionality is reused and extended to support MDT. If the MDT is initiated towards a specific UE (e.g. based on IMSI, IMEI-SV, etc.), the signalling based trace procedure is used, otherwise the management based trace procedure (or cell traffic trace procedure) is used. Network signalling and overall control of MDT is described in TS 32.422 [6]. + +The solutions for MDT shall take into account the following constraints: + +### 1. UE measurements + +The UE measurement logging mechanism is an optional feature. In order to limit the impact on UE power consumption and processing, the UE measurement logging should as much as possible rely on the measurements that are available in the UE according to radio resource management enforced by the access network. + +### 2. Location information + +The availability of location information is subject to UE capability and/or UE implementation. Solutions requiring location information shall take into account power consumption of the UE due to the need to run its positioning components. + +# --- 5 Functions and procedures + +## 5.1 General procedures + +### 5.1.1 Logged MDT procedures + +Support of Logged MDT complies with the principles for IDLE and INACTIVE state measurements in the UE specified in TS 25.133[2], TS 36.133 [3] and TS 38.133 [16] and principles for IDLE and CONNECTED mode MBSFN measurements in the UE specified in TS 36.133 [3]. + +NOTE: It should be noted the established principles may result in different logged information in different UEs. + +Furthermore, measurement logging is differentiated based on UE states in idle mode i.e. camped normally, any cell selection or camped on any cell. The UE shall perform measurement logging in "camped normally" state and "any cell selection" state. In "camped on any cell" state the UE is not required to perform MDT measurement logging (including time and location information). + +For Logged MDT, the configuration will always be done in cells of the same RAT type. However, measurements included in the logged MDT report comprises of measurements from the same RAT type (serving cell measurements, intra-frequency and inter-frequency neighbor cell measurements) and different RAT types (inter-RAT neighbor cell measurements). + +Logging of MBSFN measurements is only applicable to E-UTRA. + +#### 5.1.1.1 Measurement configuration + +Logged MDT measurements are configured with a MDT Measurement Configuration procedure, as shown in Figure 5.1.1.1-1. + +![Sequence diagram showing the MDT measurement configuration for Logged MDT. A box labeled '(E-)UTRAN or NR' sends a message labeled 'LoggedMeasurementConfiguration' to a box labeled 'UE'.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network as (E-)UTRAN or NR + Note right of Network: LoggedMeasurementConfiguration + Network->>UE: LoggedMeasurementConfiguration + +``` + +Sequence diagram showing the MDT measurement configuration for Logged MDT. A box labeled '(E-)UTRAN or NR' sends a message labeled 'LoggedMeasurementConfiguration' to a box labeled 'UE'. + +**Figure 5.1.1.1-1: MDT measurement configuration for Logged MDT** + +Network initiates the procedure to UE in RRC Connected by sending *LoggedMeasurementConfiguration* message, which is used to transfer configuration parameters for Logged MDT. This is a unidirectional RRC signalling procedure. + +A release operation for logged measurement configuration in the UE is realized only by configuration replacement when the configuration is overwritten or by configuration clearance in case a duration timer stopping or expiration condition is met. + +##### 5.1.1.1.1 Configuration parameters + +The logged measurement configuration consists of: + +- configuration of downlink pilot strength measurements logging for (E-)UTRA and NR. +- configuration of MBSFN measurement logging for E-UTRA. +- configuration of the triggering of logging events: + - for (E-)UTRAN: + - periodic measurement trigger is supported, for which the logging interval is configurable. The parameter specifies the periodicity for storing MDT measurement results. It should be configured in seconds in multiples of the applied IDLE mode DRX, i.e. multiples of 1.28s which is either a factor or multiple of the IDLE mode DRX. The UE behaviour is unspecified when the UE is configured with a DRX cycle larger than the logging interval. + - for NR: + - periodic measurement trigger is supported, for which the logging interval is configurable. The parameter specifies the periodicity for storing MDT measurement results. + - for E-UTRAN and NR: + - event-based trigger is supported, for which the logging interval is configurable, which determines periodical logging of available data (e.g. time stamp, location information), and the following two types of events are supported: + - measurement quantity-based event L1, for which the event threshold, hysteresis, and time to trigger are configurable. If the configured time to trigger is not a multiple of the DRX cycle, then the UE uses the next multiple of DRX cycle duration that is larger than the time to trigger for evaluating the event L1; + - out-of-coverage detection trigger. + +NOTE: The logging configuration for event-based and periodical DL pilot strength logged measurements can be configured independently. Only one type of event can be configured to the UE. + +- configuration of the logging duration. This configuration parameter defines a timer activated at the moment of configuration, that continues independent of state changes, RAT or RPLMN change. When the timer expires the logging is stopped and the configuration is cleared (except for the parameters that are required for further reporting e.g. network absolute time stamp, trace reference, trace recording session reference and TCE Id). +- network absolute time stamp to be used as a time reference to UE. +- Trace Reference parameter as indicated by the OAM configuration as specified in TS 32.422 [6]. +- Trace Recording Session Reference as indicated by the OAM configuration as specified in TS 32.422 [6]. +- TCE Id as indicated by the OAM configuration as specified in TS 32.422 [6]. +- (optionally) MDT PLMN List, indicating the PLMNs where measurement collection and log reporting is allowed. It is either the Management Based MDT PLMN List or the Signalling Based MDT PLMN List, depending on how the Logged MDT task was initiated (see 5.1.3). +- (optionally) configuration of a logging area. A UE will log measurements as long as it is within the configured logging area. The scope of the logging area may consist of one of: + - a list of up to 32 global cell identities for PLMN, and, for NR, additionally a list of up to 256 PNI-NPNs. If one or both of these lists are configured, the UE will only log measurements when camping in any of the cells belonging to the list of global cell identities, or in any of the cells belonging to the listed PNI-NPNs. + - a list of up to 8 TAs or 8 LAs or 8 RAs for PLMN, and, for NR, a list of up to 256 PNI-NPNs. If one or both of these lists are configured, the UE will only log measurements when camping in any cell belonging to the preconfigured TA/LA/RAs. + - for NR, a list of inter-frequency neighbouring cells per frequency. + - for NR, a list of up to 256 PNI-NPNs. + - for NR, a list of up to 16 SNPNS. + - for NR, a list of up to 32 global cell identities for SNPN. If this list is configured, the UE will only log measurements when camping in any of these cells. + - for NR, a list of up to 8 TAs for SNPN. If this list is configured, the UE will only log measurements when camping in any cell belonging to the configured TAs. +- The configured logging area can span one of: + - PLMNs in the MDT PLMN List. If no area is configured, the UE will log measurements throughout the PLMNs of the MDT PLMN list. + - Any configured SNPN area. +- (optionally) for NR, configuration of a list of neighbouring frequencies and/or cells, indicating the UE to include neighbouring cell's measurements as indicated in the list in the logged MDT report. +- (optionally) for E-UTRA, configuration of target MBSFN area(s) for MBSFN measurement logging. If target MBSFN area(s) is configured, UE applies it in addition to other restrictions such as the logging area. The UE will log measurements as long as it receives MBMS service from an indicated target MBSFN area and is within the configured logging area. The target MBSFN area(s) is defined by a list of up to 8 entries, where each entry indicates a carrier frequency and optionally indicates a specific MBSFN area on a carrier frequency. +- (optionally) configuration of the WLAN access point names, indicating the UE to attempt to obtain WLAN measurements associated to these access points. +- (optionally) configuration of the Bluetooth beacon names, indicating the UE to attempt to obtain Bluetooth measurements associated to these beacons. +- (optionally) for NR, configuration of the sensor names, indicating the UE to attempt to obtain sensor measurements. + +- (optionally) for E-UTRA, configuration indicating the UE to attempt to obtain uncompensated barometric pressure measurements. +- (optionally) for NR, the network can use a flag to indicate if an early measurement/idle mode configuration has relevance for logged measurement purposes, indicating the UE is allowed to log the measurement results related to early measurement frequencies in the logged MDT report. +- (optionally) for NR, logged MDT type flag, indicating the logged measurement configuration is the signalling based MDT (see 5.4.0). + +##### 5.1.1.1.2 Configuration effectiveness + +The logged measurement configuration is provided in a cell by dedicated control while UE is in CONNECTED and implies: + +- logged measurement configuration for downlink pilot strength measurements (or events) logging is active + - in IDLE UE state in E-UTRAN, or + - in IDLE mode, CELL\_PCH and URA\_PCH states in UTRAN, or + - in CELL\_FACH state when second DRX cycle is used in UTRAN, or + - in IDLE and INACTIVE states in NR + - until logging duration timer expires or stops +- logged measurement configuration for MBSFN measurement logging is active + - in IDLE and CONNECTED UE states in E-UTRAN + - until logging duration timer expires or stops +- logged measurement configuration and logs are maintained when the UE is in any state as described above, despite multiple periods interrupted by UE state transitions, e.g. for downlink pilot strength measurements when the UE is in CONNECTED state for E-UTRAN and NR and CELL\_DCH, CELL\_FACH state when second DRX cycle is not used in UTRAN +- logged measurement configuration and logs are maintained when the UE is in any state as described above in that RAT, despite multiple periods interrupted by UE presence in another RAT + +There is only one RAT-specific logged measurement configuration for Logged MDT in the UE. When the network provides a configuration, any previously configured logged measurement configuration will be entirely replaced by the new one. Moreover, logged measurements corresponding to the previous configuration will be cleared at the same time. It is left up to the network to retrieve any relevant data before providing a new configuration. + +NOTE: The network may have to do inter-RAT coordination. + +When a logging area is configured, logged MDT measurements are performed as long as the UE is within this logging area. For NR, when determining whether a cell is part of the logging area, only the first entry of the *plmn-IdentityList* in the first entry of the *PLMN-IdentityInfoList* (in SIB1), and cellIdentity and TAC corresponding to the first entry of the *PLMN-IdentityInfoList* are considered. If no logging area is configured, logged MDT measurements are performed as long as the RPLMN is part of the MDT PLMN list. When the UE is not in the logging area or RPLMN is not part of the MDT PLMN list, the logging is suspended, i.e. the logged measurement configuration and the log are kept but measurement results are not logged. In addition, for MBSFN logged measurements, logged MDT measurements are performed in logging intervals when the UE receives MBMS service from a MBSFN area according to the target MBSFN area(s) configuration. When the UE is not in the logging area or does not receive MBMS service from a MBSFN area that matches the target MBSFN area(s) configuration in the logging interval the logged measurement configuration and the log are kept but measurement results are not logged. + +NOTE: The logging duration timer continues. + +In case the new PLMN that does not belong to the MDT PLMN list provides a logged measurement configuration any previously configured logged measurement configuration and corresponding log are cleared and overwritten without being retrieved. + +#### 5.1.1.2 Measurement collection + +In "camped normally" state, a UE shall perform logging as per the logged measurement configuration. This state includes a period between cell selection criteria not being met and UE entering "any cell selection" state, i.e. 10 s for E-UTRA (See TS 36.133 [3]) or 12 s for UTRA (See TS 25.133 [2]) or 10s for NR (See TS 38.133 [16]). + +In "any cell selection" state, a UE shall perform logging of available information (i.e. at least indicator 'anyCellSelectionDetected', time stamp, and the available location information). In "camped on any cell" state, the periodic logging stops. However, it should be noted that the duration timer is kept running. When the UE re-enters "camped normally" state and the duration timer has not expired, the periodic logging is restarted based on new DRX and logging resumes automatically (with a leap in time stamp). + +When an E-UTRA or NR UE detects an in-device coexistence problem that may affect the logged measurement results, the UE shall stop measurement logging, indicate in the log that an in-device coexistence problem has occurred, and keep the duration timer running. When the in-device coexistence problem is no longer present, and the duration timer has not expired, the logging resumes, with a leap in time stamp. + +For E-UTRA MBSFN measurement logging, the UE shall perform MBSFN measurements only when receiving MBMS service, and measurement logging is performed only for logging intervals for which MBSFN measurements are available. The UE shall perform MBSFN measurements and MBSFN measurement logging in both IDLE and CONNECTED modes. + +NOTE: the UE is only required to perform MBSFN measurements when receiving MBMS service of the MBSFN area(s) targeted for logging. + +For WLAN measurement logging and Bluetooth measurement logging, the UE shall perform WLAN and Bluetooth measurements, respectively, only when indicated in the corresponding configuration. The measurement logging is performed only for logging intervals for which WLAN and Bluetooth measurements are available, respectively. + +The measurement quantities for downlink pilot strength measurement logging are fixed and consist of both RSRP and RSRQ for EUTRA, both RSCP and Ec/No for UTRA FDD, P-CCPCH RSCP for UTRA 1.28 Mcps TDD, Rxlev for GERAN, and Pilot Pn Phase and Pilot Strength for CDMA2000 if the serving cell is EUTRAN cell, and both RSRP and RSRQ for NR. + +For NR, in addition to the logged measurement quantities of the camped cell, the best beam index (SSB Index) as along with the best beam RSRP/RSRQ are logged as well as the 'number of good beams' (the number of SSBs that are above the configured threshold i.e., *absThreshSS-BlocksConsolidation*, if configured by the network) associated to the cells within the R value range (which is configured by network for cell reselection) of the highest ranked cell as part of the beam level measurements. Sensor measurements are logged if available. + +For E-UTRA, uncompensated barometric pressure measurements are logged if available. + +The measurement quantities for E-UTRA MBSFN measurement logging are fixed and consist of MBSFN RSRP, MBSFN RSRQ, BLER for signalling and BLER for data per MCH, in addition to the measurement quantities for downlink pilot strength measurements. + +The measurement quantities for WLAN measurement logging are fixed and consist of BSSID, SSID, HESSID of WLAN APs. If configured by the network, optionally available RSSI and RTT can be included. + +The measurement quantity for Bluetooth measurement logging is fixed and consists of MAC address of Bluetooth beacons. If configured by the network, optionally available RSSI can be included. + +UE collects MDT measurements and continues logging according to the logged measurement configuration until UE memory reserved for MDT is full. In this case the UE stops logging, stops the log duration timer and starts the 48 hour timer. + +#### 5.1.1.3 Measurement reporting + +##### 5.1.1.3.1 Availability Indicator + +A UE configured to perform Logged MDT downlink pilot strength measurements indicates the availability of Logged MDT measurements, by means of a one bit, in RRCConnectionSetupComplete or RRCSetupComplete or RRCConnectionResumeComplete or RRCResumeComplete message during connection establishment. Furthermore, the indicator (possibly updated) shall be provided within: + +- E-UTRAN handover and re-establishment; +- UTRAN procedures involving the change of SRNC (SRNC relocation), CELL UPDATE, URA UPDATE messages as well as MEASUREMENT REPORT message in case of state transition to CELL\_FACH without CELL UPDATE; +- NR re-establishment, reconfiguration. + +The UE includes the indication in one of these messages at every transition to RRC Connected mode even though the logging period has not ended, upon connection to RAT which configured the UE to perform Logged MDT measurements and RPLMN which is equal to a PLMN in the MDT PLMN list. + +A E-UTRA UE configured to perform Logged MDT MBSFN measurements indicates the availability of Logged MDT MBSFN measurements, by means of an indicator, in RRCConnectionSetupComplete message during connection establishment. The indicator (possibly updated) shall be provided within E-UTRAN also at handover and re-establishment, except when the logged measurement configuration is active in CONNECTED mode, i.e. except when the logging campaign is still ongoing. + +A E-UTRA UE configured to perform Logged MDT WLAN measurements indicates the availability of Logged MDT WLAN measurements, by means of an indicator, in RRCConnectionSetupComplete message or RRCConnectionResumeComplete message during connection establishment. Furthermore, the indicator can be included in some uplink RRC messages, i.e., RRCConnectionReconfigurationComplete message, RRCConnectionReestablishmentComplete message, or UEInformationResponse message, at every transition to RRC Connected mode even though the logging period has not ended. + +A E-UTRA UE configured to perform Logged MDT Bluetooth measurements indicates the availability of Logged MDT Bluetooth measurements, by means of an indicator, in RRCConnectionSetupComplete message or RRCConnectionResumeComplete message during connection establishment. Furthermore, the indicator can be included in some uplink RRC messages, i.e., RRCConnectionReconfigurationComplete message, RRCConnectionReestablishmentComplete message, or UEInformationResponse message, at every transition to RRC Connected mode even though the logging period has not ended. + +A NR UE configured to perform Logged MDT WLAN measurements indicates the availability of Logged MDT WLAN measurements, by means of an indicator, in RRCSetupComplete message or RRCResumeComplete message during connection establishment. Furthermore, the indicator can be included in some uplink RRC messages, i.e., RRCReconfigurationComplete message, RRCReestablishmentComplete message, or UEInformationResponse message, at every transition to RRC Connected mode even though the logging period has not ended. + +A NR UE configured to perform Logged MDT Bluetooth measurements indicates the availability of Logged MDT Bluetooth measurements, by means of an indicator, in RRCSetupComplete message or RRCResumeComplete message during connection establishment. Furthermore, the indicator can be included in some uplink RRC messages, i.e., RRCReconfigurationComplete message, RRCReestablishmentComplete message, or UEInformationResponse message, at every transition to RRC Connected mode even though the logging period has not ended. + +An indicator shall be also provided in UEInformationResponse message during MDT report retrieval in case the UE has not transferred the total log in one RRC message in order to indicate the remaining data availability. + +The UE will not indicate the availability of MDT measurements in another RAT or in a PLMN that is not in the MDT PLMN list. + +The network may decide to retrieve the logged measurements based on this indication. In case Logged MDT measurements are retrieved before the completion of the pre-defined logging duration, the reported measurement results are deleted, but MDT measurement logging will continue according to ongoing logged measurement configuration. + +In case the network does not retrieve Logged MDT measurements, UE should store non-retrieved measurements for 48 hours from the moment the duration timer for logging expired. There is no requirement to store non-retrieved data beyond 48 hours. In addition, all logged measurement configuration and the log shall be removed by the UE at switch off or detach. + +##### 5.1.1.3.2 Report retrieval + +For Logged MDT the measurement reporting is triggered by an on-demand mechanism, i.e. the UE is asked by the network to send the collected measurement logs via RRC signalling. UE Information procedure defined in TS 25.331 + +[4] and TS 36.331 [5] and TS 38.331 [15] is used to request UE to send the collected measurement logs. The reporting may occur in different cells than which the logged measurement configuration is signalled. + +Transport of Logged MDT reports in multiple RRC messages is supported. With every request, the network may receive a part of the total UE log. To indicate the reported data is a segment, the UE shall include data availability indicator in UEInformationResponse message to convey the information that further measurement information is available, as specified in 5.1.1.3.1. In multiple RRC transmissions for segmented Logged MDT reporting, FIFO order is followed, i.e. the UE should provide oldest available measurement entries in earliest message. There is no requirement specified on the size of particular reporting parts. However, each reported part should be "self-decodable", i.e. interpretable even in case all the other parts are not available. + +The UE shall send an empty report when retrieval is attempted and the RPLMN is not in the MDT PLMN list. + +##### 5.1.1.3.3 Reporting parameters + +For downlink pilot strength measurements, the logged measurement report consists of measurement results for the serving cell (the measurement quantity), available UE measurements performed in idle or inactive for intra-frequency/inter-frequency/inter-RAT, time stamp and location information. + +For E-UTRA MBSFN measurements logging, the logged measurement report consists of MBSFN measurement results from target MBSFN area(s), if configured, and available downlink pilot strength measurement results. Inter-RAT downlink pilot strength measurements are not required to be logged. + +For WLAN and Bluetooth measurement logging, the logged measurement reports consist of WLAN and Bluetooth measurement results, respectively. + +The number of neighbouring cells to be logged is limited by a fixed upper limit per frequency for each category below. The UE should log the measurement results for the neighbouring cells, if available, up to: + +- 6 for intra-frequency neighbouring cells; +- 3 for inter-frequency neighbouring cells per frequency; +- 3 for GERAN neighbouring cells per frequency; +- 3 for UTRAN (if non-serving) neighbouring cells per frequency; +- 3 for E-UTRAN (if non-serving) neighbouring cells per frequency; +- 3 for NR (if non-serving) neighbouring cells per frequency; +- 3 for CDMA2000 (if serving is E-UTRA) neighbouring cells per frequency; +- 32 for WLAN APs; +- 32 for Bluetooth Beacons. + +NOTE: UE in NR IDLE or INACTIVE state will not log measurements from UMTS or GSM. + +The measurement reports for neighbour cells consist of: + +- Physical cell identity of the logged cell; +- Carrier frequency; +- RSRP and RSRQ for EUTRA and NR; +- RSCP and Ec/No for UTRA FDD, +- P-CCPCH RSCP for UTRA 1.28 Mcps TDD; +- Rxlev for GERAN; +- Pilot Pn Phase and Pilot Strength for CDMA2000; +- RSSI and RTT for WLAN APs; + +- RSSI for Bluetooth Beacons. + +For any logged cell (serving or neighbour), latest available measurement result made for cell reselection purposes is included in the log only if it has not already been reported. + +While logging neighbour cells measurements, the UE shall determine a fixed number of best cells based on the measurement quantity used for ranking during cell reselection per frequency or RAT. + +The MBSFN measurement results consist of, per MBSFN area where MBMS service is received: + +- MBSFN area identity; +- Carrier frequency; +- MBSFN RSRP; +- MBSFN RSRQ; +- MCH BLER for signalling; +- MCH BLER for data, and related MCH index. + +The WLAN measurement results consist of, per wireless network served by the WLAN AP: + +- BSSID, SSID and HESSID; +- RSSI for WLAN; +- RTT. + +The Bluetooth measurement results consist of, per wireless network served by the Bluetooth beacon: + +- MAC address; +- RSSI for Bluetooth. + +Measurements are performed in accordance with requirements defined in TS 25.133 [2] and TS 36.133 [3] and TS 38.133 [16]. + +The measurement report is self contained, i.e. the RAN node is able to interpret the Logged MDT reporting results even if it does not have access to the logged measurement configuration. Each measurement report also contains the necessary parameters for the network to be able to route the reports to the correct TCE and for OAM to identify what is reported. The parameters are sent to the UE in the logged configuration message, see clause 5.1.1.1.1. + +For each MDT measurement the UE includes a relative time stamp. The base unit for time information in the Logged MDT reports is the second. In the log associated to periodical logging configuration, the time stamp indicates the point in time when periodic logging timer expires. The time stamp is counted in seconds from the moment the logged measurement configuration is received at the UE, relative to the absolute time stamp received within the configuration. The absolute time stamp is the current network time at the point when Logged MDT is configured to the UE. The UE echoes back this absolute reference time. The time format for Logged MDT report is: *YY-MM-DD HH:MM:SS*. + +Location information is based on available location information in the UE. Thus, the Logged MDT measurements are tagged by the UE with location data in the following manner: + +- ECGI, Cell-Id or NCGI in TS 38.300 [22] of the serving cell when the measurement was taken is always included in E-UTRAN, UTRAN or NR respectively; +- Detailed location information (e.g. GNSS location information) is included if available in the UE when the measurement was taken. If detailed location information is available, the reporting shall consist of latitude and longitude. Depending on availability, altitude, uncertainty and confidence may be also additionally included. UE tags available detailed location information only once with upcoming measurement sample, and then the detailed location information is discarded, i.e. the validity of detailed location information is implicitly assumed to be one logging interval; +- Sensor information (i.e. uncompensated barometric pressure measurement (for NR and E-UTRA), UE speed and UE orientation (only in NR)) can be included, if available in the UE when the measurement was taken. + +NOTE: The neighbour cell measurement information that is provided by the UE may be used to determine the UE location (RF fingerprint). + +Depending on location information availability, measurement log/report consists of: + +- time information, RF measurements, RF fingerprints; or +- time information, RF measurements, detailed location information (e.g. GNSS location information); +time information, RF measurements, detailed location information, sensor information. + +#### 5.1.1.4 MDT context handling + +For Logged MDT in IDLE, CELL\_PCH, URA\_PCH states and CELL\_FACH state when second DRX cycle is used and INACTIVE, no need is identified to transfer an MDT context (any related configuration information about measurement and reporting) between (e/g)NBs/RNCs if corresponding MDT configuration has already been configured to UE. In addition, MDT context is assumed to be released in the RAN nodes when the UE is in IDLE and INACTIVE if corresponding MDT configuration has already been configured to UE. + +For UE in INACTIVE, the MDT context handling during cell reselection as described in 5.4.2 apply. + +### 5.1.2 Immediate MDT procedures + +#### 5.1.2.1 Measurement configuration + +For Immediate MDT, RAN measurements and UE measurements can be configured. The configuration for UE measurements is based on the existing RRC measurement procedures for configuration and reporting with some extensions for location information. + +NOTE: No extensions related to time stamp are expected for Immediate MDT i.e. time stamp is expected to be provided by eNB/RNC/gNB. + +If area scope is included in the MDT configuration provided to the RAN, the UE is configured with respective measurement when the UE is connected to a cell that is part of the configured area scope. + +#### 5.1.2.2 Measurement reporting + +For Immediate MDT, the UE provides detailed location information (e.g. GNSS location information) if available. The UE also provides available neighbour cell measurement information that may be used to determine the UE location (RF fingerprint). ECGI, Cell-Id, or CellIdentity of the serving cell when the measurement was taken is always assumed known in E-UTRAN, UTRAN or NR respectively. + +The location information which comes with UE radio measurements for MDT can be correlated with other MDT measurements, e.g. RAN measurements. For MDT measurements where UE location information is provided separately, it is assumed that the correlation of location information and MDT measurements should be done in the TCE based on time-stamps. + +When the gNB becomes aware of an in-device coexistence interference problem for NR reported by the UE, this information should be forwarded to the TCE which may correlate impacted measurements (e.g. RAN measurements M4, M5, M6, M7) with the in-device coexistence interference problem. + +#### 5.1.2.3 MDT context handling during handover and UE context retrieval + +The measurements configured in the UE for Immediate MDT should fully comply with the transferring and reconfiguration principles for the current measurements configured in the UE for RRM purpose during handover (including conformance with Rel-8 and Rel-9). + +The target node releases the measurements configured in the UE for immediate MDT which are no longer needed based on any MDT trace configuration it receives or does not receive. + +In addition, MDT configuration handling during handover and UE context retrieval depends on MDT initiation from OAM defined in clause 5.1.3: + +- The MDT configuration configured by management based trace function will not propagate during handover. +- For LTE, the MDT configuration received by signalling based trace messages for a specific UE will propagate during intra-PLMN handover, and may propagate during inter-PLMN handover if the Signalling Based MDT PLMN List is available and includes the target PLMN. This behaviour applies also for MDT configuration that includes area scope, regardless of whether the source or target cell is part of the configured area scope. This behaviour applies also for Xn inter-RAT handover. +- For UMTS, the MDT configuration received by signalling based trace messages for a specific UE will continue during intra-PLMN handover, and may continue during inter-PLMN handover if the Signalling Based MDT PLMN List is available and includes the target PLMN, except for the case of SRNS relocation. +- For NR, the MDT configuration received by signalling based trace messages for a specific UE will propagate during intra-PLMN handover, intra-PLMN UE context retrieval, and may propagate during inter-PLMN handover or inter-PLMN UE context retrieval if the Signalling Based MDT PLMN List is available and includes the target PLMN. This behaviour applies also for MDT configuration that includes area scope, regardless of whether the source or target cell is part of the configured area scope. This behaviour applies also for Xn inter-RAT handover. + +NOTE: In the case of SRNS relocation, MDT may be reactivated by the Core Network following a successful relocation. + +### 5.1.3 MDT Initiation + +There are two cases that RAN should initiate a MDT measurements collection task. One is that the MDT task is initiated without targeting a specific UE by the cell traffic trace, i.e. management based trace function from OAM. The other is that the MDT task is initiated towards a specific UE by the signalling trace activation messages from CN nodes, i.e. the Initial Context Setup message, the Trace Start message or the Handover request message in E-UTRAN or NR, the CN Invoke Trace message in UTRAN. The detailed procedures to transfer the MDT configurations to RAN are specified in TS 32.422 [6]. + +For signalling based MDT within a PLMN, the CN shall not initiate MDT towards a particular user unless it is allowed. + +For management based MDT within a PLMN, the CN indicates to the RAN whether MDT is allowed to be configured by the RAN for this user considering e.g. user consent and roaming status (see TS 32.422 [6]), by providing management based MDT allowed information. For E-UTRAN/UTRAN, the MDT allowed information consists of the Management Based MDT Allowed indication and optionally the Management Based MDT PLMN List. For NR, the MDT allowed information only consists of the Management Based MDT PLMN List. The management based MDT allowed information propagates during inter-PLMN handover or inter-PLMN UE context retrieval if the Management Based MDT PLMN List is available and includes the target PLMN. + +A UE is configured with an MDT PLMN List only if user consent is valid for the RPLMN. + +User consent does not apply if the UE is served by an SNPN. + +### 5.1.4 UE capabilities + +MDT relevant UE capabilities are component of radio access UE capabilities. Thus, the procedures used for handling UE radio capabilities over (E-)UTRAN and NR apply. + +For (E-)UTRAN: + +- The UE indicates one capability bit for support for Logged MDT, which indicates that the UE supports logging of downlink pilot strength measurements. The UE may also indicate capability for stand-alone GNSS positioning. +- The E-UTRA UE may indicate capability bits for support of event triggered Logged MDT. +- The E-UTRA UE may indicate a capability for RX-TX time difference measurement for E-CID positioning for MDT. +- The E-UTRA UE may indicate a capability for support of logging of MBSFN measurements. + +- The E-UTRA UE may indicate a capability for support of UL PDCP delay measurement when the UE is not configured with MR-DC. +- The E-UTRA UE may indicate a capability for support of UL PDCP Packet Average Delay measurement when the UE is configured with EN-DC. +- The E-UTRA UE may indicate a capability for support of Bluetooth measurements in RRC idle mode. +- The E-UTRA UE may indicate a capability for support of WLAN measurements in RRC idle mode. +- The E-UTRA UE may indicate a capability for support of Bluetooth measurements in RRC connected mode. +- The E-UTRA UE may indicate a capability for support of WLAN measurements in RRC connected mode. +- The E-UTRA UE may indicate a capability for support of barometer measurements in RRC idle mode. +- The E-UTRA UE may indicate a capability for support of barometer measurements in RRC connected mode. +- For UMTS support of the Accessibility measurements is an optional UE feature. + +For NR: + +- The UE indicates one capability bit for support for Logged MDT in RRC idle and inactive mode, to indicate that the UE supports logging of downlink pilot strength measurements, periodical logging and event-triggered logging. + +NOTE: Logged MDT suspension due to in-device coexistence detection is conditionally mandatory feature, i.e., it is mandatory supported if the UE supports Logged MDT in RRC idle and inactive mode. + +- The NR UE may indicate a capability bit for support of signalling based Logged MDT overriding protection. +- The UE may indicate capability for stand-alone GNSS positioning. +- The NR UE may indicate a capability for support of UL PDCP packet average delay measurement. +- The NR UE may indicate a capability for support of multiple reports on accessibility measurements. +- The NR UE may indicate a capability for support of Bluetooth measurements in RRC idle and inactive mode. +- The NR UE may indicate a capability for support of WLAN measurements in RRC idle and inactive mode. +- The NR UE may indicate a capability for support of Bluetooth measurements in RRC connected state. +- The NR UE may indicate a capability for support of WLAN measurements in RRC connected state. +- The NR UE may indicate a capability for support of barometer measurements. +- The NR UE may indicate a capability for support of orientation measurements. +- The NR UE may indicate a capability for support of speed measurements. +- The NR UE may indicate a capability for support of UL PDCP excess packet delay. +- The NR UE may indicate a capability for logging and reporting on-Demand SI request information support. +- The NR UE may indicate a capability for storing and reporting PSCell Mobility History Information. +- The NR UE may indicate a capability for support of RLF report for CHO. +- The NR UE may indicate a capability for support of RLF report for DAPS. +- The NR UE may indicate a capability for support of storage and delivery of 2-step RACH related information. + +### 5.1.5 Void + +### 5.1.6 Accessibility measurements + +The UE logs failed RRC connection establishments for LTE, UMTS and NR, i.e. a log is created when the RRC connection establishment procedure fails. For NR, UE logs any failed connection establishment attempt, i.e. a log is created when the RRC setup or resume procedure fails. The UE logs failed RRC connection establishments without the need for prior configuration by the network. + +The UE stores the Selected PLMN on the RRC connection establishment failure or RRC resume procedure failure. Only if that PLMN is the same as the RPLMN, the UE may report the log. + +NOTE: There is no expected performance degradation for networks using EPLMNs. + +The trigger for creating a log related to a failed RRC connection establishment is for NR when timer T300 expires, for LTE when timer T300 expires and for UMTS when V300 is greater than N300. The trigger for creating log related to a failed RRC resume procedure is for NR when timer T319 expires. + +The UE can store the following information related to the failed RRC connection establishment or failed RRC resume procedure: + +- Time stamp, which is the elapsed time between logging and reporting the log. +- The global cell identity of the serving cell when the RRC connection establishment or resume fails, i.e. the cell which the UE attempted to access. +- The latest available radio measurements for any frequency or RAT +- The latest detailed location information, if available. +- For LTE: + - Number of Random Access Preambles transmitted; + - Indication whether the maximum transmission power was used; + - Contention detected; + - The latest WLAN measurement results, if available; + - The latest Bluetooth measurement results, if available. +- For UMTS FDD: + - Number of RRC Connection Request attempts (e.g. T300 expiry after receiving ACK and AICH) +- For UMTS 1.28 Mcps TDD: + - Number of RRC Connection Request attempts. + - Whether the FPACH is received or whether the maximum number Mmax of synchronisation attempts is reached. + - Failure indication of the E-RUCCH transmission. It is only applied when common E-DCH is supported by UE and network. +- For NR: + - SSB index of the downlink beams of serving cell; + - The latest number of consecutive connection failures in the last failed cell the UE has experienced independent of RRC state transitions; + - RACH failure report: + +- Tried SSB index and number of Random Access Preambles transmitted for each tried SSB in chronological order of attempts; +- Contention detected as per RACH attempt; +- Indication whether the selected SSB is above or below the rsrp-ThresholdSSB threshold, as per RACH attempt; +- TAC of the cell in which the UE performs the RA procedure; +- For 2-step RACH, the following information can be additionally included: + - Indication that fallback from 2-step RA to 4-step RA was performed by the UE, as per RACH attempt. +- The latest WLAN measurement results, if available; +- The latest Bluetooth measurement results, if available; +- The latest sensor information, if available. + +In addition, the CEF report may include additional information required for RACH Optimization solutions, as specified in TS 38.300 [22]. + +For NR, the UE can store multiple CEF (up to 4) reports to solve the problem about UL/DL coverage imbalance. For the failures happening consecutively in different cells, the UE stores multiple CEF report entries in the CEF report list, as specified in TS 38.331 [15]. For the failures happening consecutively in the same cell, the UE stores only one CEF report entry in the CEF report list, and replaces the last information related to the failed RRC connection establishment or failed RRC resume procedure with the new one, while the number of consecutive connection failures is increased. All the entries in the multiple CEF report list correspond to one PLMN. Prior to logging connection setup or resume failure information for a cell belonging to a different RPLMN, the UE clears stored CEF report entries. + +## 5.2 E-UTRAN solutions + +### 5.2.1 RRC\_CONNECTED + +UE in RRC Connected does not support Logged MDT in this release of the specification, except for the case of logged MDT for MBSFN measurements as described in clause 5.1.1. In order to support Immediate MDT where MDT measurements are executed in the UE, the existing RRC measurement configuration and reporting procedures apply. Some extensions are used to carry location information. + +#### 5.2.1.1 Measurements and reporting triggers for Immediate MDT + +Measurements to be performed for Immediate MDT purposes involve reporting triggers and criteria utilized for RRM. An MDT specific UE-based measurement for UL PDCP delay is applied for QoS verification purpose. In addition, there are measurements performed in eNB. + +In particular, the following measurements shall be supported for Immediate MDT performance: + +Measurements: + +- M1: RSRP, RSRQ and SINR measurement by UE, see TS 36.214 [9]. +- M2: Power Headroom measurement by UE, see TS 36.213 [11]. +- M3: Received Interference Power measurement by eNB, see TS 36.214 [9]. This is a cell measurement. One sample is logged each measurement collection period, where one sample corresponds to a measurement period as specified in TS 36.133 [3]. +- M4: Data Volume measurement separately for DL and UL, per QCI per UE, by eNB, see TS 36.314 [13]. +- M5: Scheduled IP Throughput for MDT measurement separately for DL and UL, per RAB per UE and per UE for the DL, per UE for the UL, by eNB, see TS 36.314 [13]. QCI values of the RABs that have contributed to a measurement value are logged with the measurement values. + +- M6: Packet Delay measurement, separately for DL and UL, per QCI per UE, see UL PDCP Delay, by the UE, and Packet Delay in the DL per QCI, by the eNB, TS 36.314 [13]. + +NOTE 1: If the UE does not detect any UL PDCP delay based on the delay threshold and delay report interval configured by the network, the UE does not report any UL PDCP delay measurement within that period. + +NOTE 2: A UE in EN-DC mode of operation can be configured with UL PDCP Packet Average Delay (*ul-DelayValueConfig*), if UE is capable of performing the UL average PDCP queueing delay. + +- M7: Packet Loss rate measurement, separately for DL and UL per QCI per UE, by the eNB, see Packet Loss rate in the UL and Packet Uu Loss rate in the DL TS 36.314 [13]. +- M8: RSSI measurement by UE, see TS 36.331 [5]. +- M9: RTT measurement by UE, see TS 36.331 [5]. + +Measurement collection triggers: + +- For M1: + - Event-triggered measurement reports according to existing RRM configuration for events A1, A2, A3, A4, A5 A6, B1 or B2 + - Periodic, A2 event-triggered, or A2 event triggered periodic measurement report according to MDT specific measurement configuration. +- For M2: + - Reception of Power Headroom Report (PHR) according to existing RRM configuration. + +NOTE 3: PHR is carried by MAC signalling. Thus, the existing mechanism of PHR transmission applies, see TS 36.321 [10]. + +- For M3: + - End of measurement collection period +- For M4: + - End of measurement collection period. +- For M5: + - End of measurement collection period. +- For M6: + - End of measurement collection period. +- For M7: + - End of measurement collection period. +- For M8: + - Associated to M1 and/or M6 related measurement reporting triggers. +- For M9: + - Associated to M1 and/or M6 related measurement reporting triggers. + +#### 5.2.1.2 Enhancement to Radio Link Failure report + +The Radio Link Failure report contains information related to the latest connection failure experienced by the UE. The connection failure can be Radio Link Failure (RLF) or Handover Failure (HOF). The contents of the RLF report and the procedure for retrieving it by an eNB are described in TS 36.300 [12] or by an NG-RAN are described in TS 38.300 [22]. + +RLF reports can be collected by OAM. Upon RLF/HOF detection in the UE, *RLFReport* defined in TS 36.331 [5] also includes available location information on where RLF occurred, i.e. if detailed location information (e.g. GNSS location information) is available the reported location information in *RLFReport* consists of: + +- Latitude, longitude (mandatory) +- Altitude (conditional on availability) +- Velocity (conditional on availability) +- Uncertainty (conditional on availability) +- Confidence (conditional on availability) +- Direction (conditional on availability). + +As an indication of impact to MMTEL calls the UE indicates in the radio link failure report whether a radio bearer with QCI 1 was established when radio link failure was detected. + +RLF reports may also include available WLAN measurement results and/or Bluetooth measurement results for calculating UE location. + +If available, the UE can indicate NR neighbor cell measurements in measurements results. + +#### 5.2.1.3 Detailed Location Information + +The M1 measurements are tagged by the UE with location data in the following manner: + +- Detailed location information (e.g. GNSS location information) is included if available in the UE when the measurement was taken. If detailed location information is available, the reporting shall consist of latitude and longitude. Depending on availability, altitude, uncertainty and confidence may be also additionally included. The UE should include the available detailed location information only once. If the detailed location information is obtained by GNSS positioning method, GNSS time information shall be included. For both event based and periodic reporting (see 5.2.1.1), the detailed location information is included if the report is transmitted within the validity time after the detailed location information was obtained. The validity evaluation of detailed location information is left to UE implementation. +- To support UE location information in SCG failure, the location information (i.e. commonLocationInfo, see TS 38.331 [15] and WLAN and BT information, if available) is included in *SCGFailureInformation* message, see TS 36.331 [5]. + +For immediate MDT, the eNB can request the UE to attempt to make GNSS location information available. Standalone GNSS is used as the default baseline. It is desired that the UE provides fresh location information with each immediate MDT measurement report. The details how this is achieved is up to UE implementation. + +The eNB may use an Enhanced Cell ID mechanism for location. The eNB forwards the raw E-CID specific measurements to the TCE. When E-CID positioning is requested, the eNB may choose to not use E-CID positioning for collected measurement for which the UE provides detailed location information. + +### 5.2.2 RRC\_IDLE + +For UE in RRC\_IDLE state Logged MDT procedures as described in 5.1.1 apply. + +Logged MDT measurements are sent on Signalling Radio Bearer SRB2 in RRC\_CONNECTED state. + +## 5.3 UTRAN solutions + +### 5.3.1 UTRA RRC Connected + +In CELL\_PCH, URA\_PCH states and CELL\_FACH state when second DRX cycle is used, UE supports Logged MDT as described in 5.1.1. In CELL\_DCH state UE supports Immediate MDT as described in 5.1.2. In CELL\_FACH state when second DRX cycle is not used, MDT is not supported in the current release. + +#### 5.3.1.1 Measurements and reporting events for Immediate MDT + +The solutions for Immediate MDT in UTRAN are only applicable for UEs in CELL\_DCH state. Measurements to be performed for Immediate MDT purposes involve normal UTRAN reporting triggers and criteria utilized for controlling the RRC connection. In addition, there are measurements defined that are performed in UTRAN. In particular, the following measurements shall be supported for Immediate MDT: + +Measurements: + +- M1: CPICH RSCP and CPICH Ec/No measurement (FDD) by UE, see TS 25.215 [7]. +- M2: P-CCPCH RSCP and Timeslot ISCP for UTRA 1.28 Mcps TDD by UE, see TS 25.225 [8]. +- M3: SIR and SIR error (FDD) by NodeB, see TS 25.215 [7] and TS 25.225 [8]. +- M4: UE power headroom (UPH) by the UE, applicable for E-DCH transport channels, see TS 25.215 [7] and TS 25.225 [8]. +- M5: Received total wideband power (RTWP) by Node B, see TS 25.215 [7] TS 25.225 [8], and TS 25.133 [2]. This is a cell measurement. +- M6: Data Volume measurement, separately for DL and UL, per QoS class per UE, by RNC. +- M7: Throughput measurement, separately for DL and UL, per RAB per UE and per UE, by RNC. Traffic class and Traffic Handling Priority for interactive RABs for the RABs that have contributed to a measurement value are logged with the measurement values. + +Measurement collection triggers: + +- For M1: + - Event triggered measurement reports according to existing RRM configuration, for measurement types intra-frequency measurement, inter-frequency measurement and inter-RAT measurement. + - Periodic, or 1F event-triggered measurement report, primary CPICH becomes worse than an absolute threshold, according to MDT specific measurement configuration. +- For M2: + - Event triggered measurement reports according to existing RRM configuration, for measurement types intra-frequency measurement, inter-frequency measurement and inter-RAT measurement. + - Periodic, or 1I event-triggered measurement report, timeslot ISCP above a certain threshold (TDD), according to MDT specific measurement configuration. +- For M3: + - When available +- For M4: + - Reception of UPH according to existing RRM configuration + - Provided by the UE according to RRM configuration. + - UPH samples may be collected and logged: + - always + - periodic, one sample per period. + - periodic, one sample per period, when measurement value < threshold. +- For M5: + - When available. + +- End of measurement collection period. +- For M6: + - End of measurement collection period. +- For M7: + - End of measurement collection period. + +#### 5.3.1.2 Detailed Location Information + +For Immediate MDT, existing procedures for UE Location information are used to obtain detailed location information. + +### 5.3.2 UTRA Idle + +For UEs in UTRA Idle mode Logged MDT procedures as described in 5.1.1 apply. + +Logged MDT measurements are sent on Signalling Radio Bearer SRB4 in RRC Connected mode. + +## 5.4 NR solutions + +### 5.4.0 General + +The management-based MDT configuration should not overwrite signalling based MDT configuration. + +To assist the network in preventing management based logged MDT overwriting signaling based logged MDT, if the UE is configured with logged MDT type, the UE provides an assistance information during connection establishment, re-establishment, resume and intra-NR handover. The information indicates the signaling based logged MDT configuration or unretreived signaling based logged MDT measurement report presence in the UE. + +### 5.4.1 RRC\_CONNECTED + +In RRC\_CONNECTED state UE supports Immediate MDT as described in 5.1.2. In order to support Immediate MDT, the existing RRC measurement configuration and reporting procedures apply. Some extensions are used to carry location information. + +#### 5.4.1.1 Measurements and reporting triggers for Immediate MDT + +Measurements to be performed for Immediate MDT purposes involve reporting triggers and criteria utilized for RRM. In addition, there are associated network performance measurements performed in the gNB. + +In particular, the following measurements shall be supported for Immediate MDT performance: + +Measurements: + +- M1: DL signal quantities measurement results for the serving cell and for intra-frequency/Inter-frequency/inter-RAT neighbour cells, including cell/beam level measurement for NR cells only, TS 38.215 [19]. +- M2: Power Headroom measurement by UE, TS 38.213 [20]. +- M3: Void. +- M4: PDCP SDU Data Volume measurement separately for DL and UL, per DRB per UE, see TS 28.552 [17]. +- M5: Average UE throughput measurement separately for DL and UL, per DRB per UE and per UE for the DL, per DRB per UE and per UE for the UL, by gNB, see TS 28.552 [17]. +- M6: Packet Delay measurement separately for DL and UL, per DRB per UE, TS 28.552 [17] and TS 38.314 [18]. + +NOTE 0: UL PDCP Excess Packet Delay measurement can be configured with a threshold as specified in TS 38.331 [15]. + +- M7: Packet loss rate measurement separately for DL and UL, per DRB per UE, TS 28.552 [17] and TS 38.314 [18]. +- M8: RSSI measurement by UE (for WLAN/Bluetooth measurement) see TS 38.331 [15]. +- M9: RTT Measurement by UE (for WLAN measurement) see TS 38.331 [15]. + +NOTE 1: Void + +NOTE 1a: M5 ~ M7 can apply to MR-DC and EN-DC SN terminated MCG/split bearers and MN terminated SCG/split bearers. + +Measurement collection triggers: + +- For M1: + - Event-triggered measurement reports according to existing RRM configuration for events A1, A2, A3, A4, A5, A6, B1 or B2. + - Periodic, A2 event-triggered, or A2 event triggered periodic measurement report according to MDT specific measurement configuration. +- For M2: + - Reception of Power Headroom Report (PHR) according to existing RRM configuration. + +NOTE 2: PHR is carried by MAC signalling. Thus, the existing mechanism of PHR transmission applies, see TS 38.321 [21]. + +- For M3: + - Void. +- For M4: + - End of measurement collection period. +- For M5: + - End of measurement collection period. + +NOTE 3: If transmission of a data burst is ongoing at the boundary of the measurement collection period, T1 and T2 in throughput evaluations are set to the end and the start of the measurement period, respectively. + +- For M6: + - End of measurement collection period. +- For M7: + - End of measurement collection period. +- For M8: + - Associated to M1 and/or M6 related measurement reporting triggers. +- For M9: + - Associated to M1 and/or M6 related UE measurement reporting triggers. + +#### 5.4.1.2 Radio Link Failure report + +The Radio Link Failure report contains information related to the latest connection failure experienced by the UE. The connection failure can be Radio Link Failure (RLF), or Handover Failure (HOF). The contents of the RLF report and + +the procedure for retrieving it by a gNB are specified in TS 38.331 [15], including failure information related to CHO, or DAPS Handover Failure (DAPS HOF). In case of consecutive connection failures associated to CHO or DAPS, the UE stores and reports both failure related information in the RLF report. + +RLF report can contain latest two consecutive failures, in case one of the failures is related to CHO. In case of consecutive failures, the UE stores and reports both failure related information in the RLF report. The consecutive failure scenarios concern the following sequence of events: + +- a. A UE that has CHO configuration (as specified in TS 36.331 [5]) detects RLF in the source cell. The UE selects a configured candidate CHO target cell for connection re-establishment. The UE fails to re-establish to the selected CHO candidate cell. +- b. A UE that has CHO configuration, executes the CHO towards the target cell upon fulfilling the configured condition and experiences a HO failure. The UE selects a configured candidate CHO target cell for connection re-establishment. The UE fails to re-establish to the selected CHO candidate cell. +- c. A UE that has CHO configuration executes the normal HO towards the target cell and experiences a HO failure. The UE selects for connection re-establishment a configured candidate CHO target cell. The UE fails to re-establish to the selected CHO candidate cell using CHO procedure. + +For DAPS, two consecutive failure information concern the following scenarios: + +- a. A UE detects a connection failure at the source (RLF) while performing access to DAPS target cell and fails to access the target (HOF). +- b. A UE detects a connection failure at the target cell (HOF) and fails to perform fallback (RLF at source). + +NR RLF report content required for MDT includes: + +- Latest radio measurement results of the serving and neighbouring cells, including SSB/CSI-RS index and associated measurements in the serving and neighbouring cells; + +NOTE: The measure quantities are sorted through the same RS type depending on the availability, according to the following priority: RSRP, RSRQ, SINR. + +- For CHO, UE includes the latest radio measurement results of the candidate target cells; +- WLAN and Bluetooth measurement results, if were configured prior RLF and are available for reporting; +- "No suitable cell is found" flag when T311 expires; +- Indication per SSB/CSI-RS beams reporting whether it is configured to RLM purpose; +- Available sensor information; +- Available detailed location information; +- RACH failure report (in case, the cause for RLF is random access problem or Beam Failure Recovery failure): + - Tried SSB/CSI-RS index and number of Random Access Preambles transmitted for each tried SSB/CSI-RS in chronological order of attempts; + - Contention detected as per RACH attempt; + - Indication whether the selected SSB is above or below the rsrp-ThresholdSSB threshold, as per RACH attempt; + - TAC of the cell in which the UE performs the RA procedure; + - Frequency location related information of the RA resources used by the UE as specified in TS 38.331 [15]; + - For 2-step RA, the following information can be additionally included: + - The measured RSRP of DL pathloss reference obtained just before performing RACH procedure (per RA procedure); + - Indication that fallback from 2-step RA to 4-step RA was performed by the UE, as per RACH attempt; + +- Indication of RA switching point (as defined by the field *msgA-TransMax* in TS 38.331 [15]); +- The payload size available in the UE buffer at the time of initiating the 2-step RA procedure, without considering the padding (per RA procedure); +- MSGA PUSCH resources for 2-step RACH as specified in TS 38.331 [15] can be included in case the UE uses random access resources configured with CFRA. + +If detailed location information (e.g. GNSS location information) is available the reported location information in *rlf-Report* consists of: + +- Latitude, longitude (mandatory); +- Altitude (conditional on availability); +- Velocity (conditional on availability); +- Uncertainty (conditional on availability); +- Confidence (conditional on availability); +- Direction (conditional on availability). + +If sensor information is available, the sensor information may convey uncompensated barometric pressure, UE speed, and UE orientation. + +In addition, the RLF report may include additional information required for MRO solutions, as specified in TS 38.300 [22]. + +#### 5.4.1.3 Immediate MDT for MR-DC + +Immediate MDT is supported for (NG)EN-DC, NE-DC and NR-DC scenario. + +In signalling based immediate MDT, MME provides MDT configuration for both MN and SN towards MN including multi RAT SN configuration, specifically E-UTRA and NR MDT configuration. MN then forwards the NR MDT configuration towards SN (EN-DC scenario, SN is always NR). + +In management-based immediate MDT, OAM provides the MDT configuration to both MN and SN independently. For both MN and SN, Management based MDT should not overwrite signalling based MDT. + +For immediate MDT configuration, MN and SN can independently configure and receive measurement from the UE. + +For MN terminated SCG bearer and SN terminated MCG bearer, the terminated node, e.g., MN in case of MN terminated SCG bearer, configures the configuration to UE. + +For configuring UL PDCP packet average delay (as specified in clause 4.3.1.1 in TS 38.314 [18]) in case of split bearer: only the terminated node of the split bearer can configure the measurement to UE, and the UE reports the measurement result to corresponding node where the configuration was received from. + +### 5.4.2 RRC\_IDLE & RRC\_INACTIVE + +#### 5.4.2.1 General + +For UE in RRC\_IDLE and RRC\_INACTIVE states Logged MDT procedures as described in 5.1.1 apply. + +For Logged MDT measurement collection for RRC\_INACTIVE UEs, the actual process of logging within the UE, takes place in RRC\_INACTIVE state and may be continued in RRC\_IDLE state; or vice versa. + +The logged measurement stored in UE during RRC\_INACTIVE and RRC\_IDLE state are kept for a given common period before they are deleted as in LTE MDT. + +If the signalling based logged or immediate MDT configuration received by the NG-RAN when UE is in RRC\_INACTIVE: + +- The NG-RAN stores the MDT configuration in the UE context; + +- When the UE resumes the RRC connection in the last serving NG-RAN, the NG-RAN can configure the MDT configuration for the UE; +- When the UE resumes the RRC connection in one new NG-RAN, the new NG-RAN can configure the MDT configuration for the UE, only if the signalling based logged MDT was received by the new NG-RAN from the previous NG-RAN or AMF. + +If the management based MDT configuration is received by the NG-RAN when UE is in RRC\_INACTIVE, + +- No requirement for the NG-RAN to store the MDT configuration in the UE context; +- When the UE resumes the RRC connection in the last serving NG-RAN, the NG-RAN can configure the MDT configuration for the UE; +- When the UE resumes the RRC connection in another NG-RAN, the source NG-RAN will not propagate the management based MDT configuration. The source NG-RAN should inform the target NG-RAN of UE consents. + +Logged MDT measurements are sent on Signalling Radio Bearer SRB2 in RRC\_CONNECTED state. + +#### 5.4.2.2 Logging of on-demand SI request related information + +For NR, following on-demand SI request related information are logged for both Msg1-based and Msg3-based SI request: + +- The SIB(s) that UE actually intends to request; +- The beam identifiers used to acquire the on-demand SI; +- One specific raPurpose for MSG3 based on demand SI request; +- An indication whether on-demand SI acquisition was successful or not. + +### 5.4.3 Support of NPN + +MDT is supported in PNI-NPN and SNPN. + +# --- Annex A (informative): Coverage use cases + +The MDT data reported from UEs and the RAN may be used to monitor and detect coverage problems in the network. Some examples of use cases of coverage problem monitoring and detection are described in the following: + +- **Coverage hole:** A coverage hole is an area where the signal level SNR (or SINR) of both serving and allowed neighbor cells is below the level needed to maintain basic service (SRB & DL common channels), i.e. coverage of PDCCH. Coverage holes are usually caused by physical obstructions such as new buildings, hills, or by unsuitable antenna parameters, or just inadequate RF planning. UE in coverage hole will suffer from call drop and radio link failure. Multi-band and/or Multi-RAT UEs may go to other network layer instead. +- **Weak coverage:** Weak coverage occurs when the signal level SNR (or SINR) of serving cell is below the level needed to maintain a planned performance requirement (e.g. cell edge bit-rate). +- **Pilot Pollution:** In areas where coverage of different cells overlap a lot, interference levels are high, power levels are high, energy consumption is high and cell performance may be low. This problem phenomenon has been called "pilot pollution", and the problem can be addressed by reducing coverage of cells. Typically in this situation UEs may experience high SNR to more than one cell and high interference levels. +- **Overshoot coverage:** Overshoot occurs when coverage of a cell reaches far beyond what is planned. It can occur as an "island" of coverage in the interior of another cell, which may not be a direct neighbor. Reasons for overshoot may be reflections in buildings or across open water, lakes etc. UEs in this area may suffer call drops or high interference. Possible actions to improve the situation include changing the coverage of certain cells and mobility by exclude-listing of certain cells. +- **Coverage mapping:** There should be knowledge about the signal levels in the cell areas in order to get a complete view for the coverage and be able to assess the signal levels that can be provided in the network. This means that there should be measurements collected in all parts of the network, and not just in the areas where there are potential coverage issues. +- **UL coverage:** Poor UL coverage might impact user experience in terms of call setup failure / call drop / poor UL voice quality. Therefore, coverage should be balanced between uplink and downlink connections. Possible UL coverage optimization comprises adapting the cellular coverage by changing the site configuration (antennas) but also about adjusting the UL related parameters in the way that they allow optimized usage of UL powers in different environments. +- **Cell boundary mapping:** There should be knowledge about the location of (intra/inter RAT) cell boundaries in order to compare to the expected/planned network setting. Poor handover performance may be caused by changed cell boundaries due to changes in the physical condition of the surrounding area, e.g., construction of new buildings, bridge or tunnel near the handover area. +- **Coverage mapping for pico cell in CA scenario:** As a realization of CA scenario 4 in TS 36.300 [12], pico cell may be deployed in area where high traffic occurs. The location where a pico cell is available to be added as an SCell may show whether the deployment of pico cell is according to the needs of capacity increase. + +# --- Annex B (informative): QoS verification use cases + +The MDT data reported from UEs and the RAN may be used to verify Quality of Service, assess user experience from RAN perspective, and to assist network capacity extension. Use cases are described in the following: + +- **Traffic Location:** MDT functionality to obtain information of where data traffic is transferred within a cell. +- **User QoS Experience:** MDT functionality to assess the QoS experience for a specific UE together with location information. + - Data Throughput measurements can be collected, aiming to reflect QoS for bandwidth limited traffic. + - For E-UTRA, Data Loss and Latency measurements can be collected, aiming to reflect QoS for conversational traffic. + +# --- Annex C (informative): Measurements + +This annex provides information on measurements that are used for MDT and are not specified elsewhere. + +**Throughput measurement for UMTS.** The throughput is measured on PDCP or RLC level. A measurement value for a UE and each RAB of the UE is provided each measurement period, except if the value is zero. The measurement is performed separately for UL and DL, and is performed for PS RABs. Idle periods shall not be taken into account, when there is no data buffered or no data being transmitted. + +**Data Volume measurement for UMTS.** Data Volume is measured on PDCP or RLC (without Layer 2 overhead). A measurement value for a QoS class for a UE is provided each measurement period, except if the value is zero, where the QoS class is one of conversational, interactive, streaming or background. The measurement is performed separately for UL and DL, and is performed for PS RABs. + +# --- Annex D (informative): MBSFN use cases + +The MDT data reported from UEs may be used to verify signal strength, signal quality and block error rates for MBSFN reception, to support network verification, re-planning of MBSFN areas, and optimization of MBSFN operation parameters. + +# --- Annex E (informative): Change history + +| Change history | | | | | | +|----------------|----------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | WG # | WG Doc. | Subject/Comment | Old | New | +| 2010/01 | R2#68bis | R2-100845 | Skeleton TS endorsed | 0.0.0 | 0.1.0 | +| 2010/01 | R2#68bis | R2-100846 | Initial content provided | 0.1.0 | 0.2.0 | +| 2010/02 | R2#69 | R2-101800 | Logged and Immediate MDT definitions added
Requirements introduced
Measurement Configuration/Reporting principles clarified | 0.2.0 | 0.2.1 | +| 2010/02 | R2#69 | R2-101891 | RAN2 approved TS v0.3.0 | 0.2.1 | 0.3.0 | +| 2010/04 | R2#69bis | R2-102623 | - General principles for support of Logged MDT included
- Location Information principles for Logged MDT introduced
- MDT Context handling for Logged MDT introduced
- Report availability indicator added to 5.1.3
- Annex A | 0.3.0 | 0.3.1 | +| 2010/04 | R2#69bis | R2-102656 | - Editorial changes | 0.3.1 | 0.3.2 | +| 2010/04 | R2#69bis | R2-102667 | RAN2 approved TS v0.4.0 | 0.3.2 | 0.4.0 | +| 2010/05 | R2#70 | R2-103400 | Logged MDT configuration and reporting principles added
Periodical measurement configuration rules for Logged MDT added
SRB for Logged MDT identified
Measurements and triggers for Immediate MDT identified | 0.4.0 | 0.4.1 | +| 2010/05 | R2#70 | R2-103456 | RAN2 approved TS v0.5.0 | 0.4.1 | 0.5.0 | +| 2010/06 | R2#70bis | R2-103991 | Editorial changes:
- New text organization in 5.1: split in two clauses for Logged MDT and Immediate MDT
- MDT Reporting mode in 4.1 update to clarify the requirement on feature support
- FFS on extension across RAT aligned to RAN#69 agreement
- Retrieved data removal requirement aligned to RAN2#70 agreement | 0.5.0 | 0.5.1 | +| 2010/06 | R2#70bis | R2-104073 | RAN2 approved TS v0.6.0 | 0.5.1 | 0.6.0 | +| 2010/06 | R2#70bis | R2-104074 | - Logged MDT configuration message sequence added in 5.1.1.1
- Measurement area scope identified
- Time stamping principles added
- MDT configuration/log handling at PLMN change introduced
- Validity timer for non-retrieved data defined
- GNSS location information details defined
- RLF enhancements on location information defined
- MDT applicability for UTRA states added | 0.6.0 | 0.6.1 | +| 2010/06 | R2#70bis | R2-104206 | Clarification on sending availability indicator in another RAT added | 0.6.1 | 0.6.2 | +| 2010/06 | R2#70bis | R2-104212 | RAN2 approved TS v0.7.0 | 0.6.2 | 0.7.0 | +| 2010/08 | R2#71 | R2-104950 | Agreed text proposal in R2-104303 on clarification on logged MDT data retrieval added
MDT applicability for particular UE states clarified in corresponding clauses
Time stamp details included in 5.1.1.3.3
MDT handling during handover added in 5.1.2.3
Agreed text proposal in R2-104678 to address SA5 progress added in 5.1.3
Assumptions on memory size limit capability added in 5.1.4
Further RLF enhancements listed as FFS in 5.2.1.2 | 0.7.0 | 0.7.1 | +| 2010/08 | R2#71 | R2-105238 | Clarification on idle logging applicability to "camped normally" state in 5.1.1.2. added
FFS on logged data clearance in shared network scenarios added
Submitted to TSG RAN for information | 0.7.1 | 1.0.0 | +| 2010/10 | R2#71b | R2-105787 | Editorial and formatting changes | 1.0.0 | 1.0.1 | +| 2010/10 | R2#71b | R2-105877 | Logged MDT reports details on neighbours details added
Accurate location information validity clarified
UE memory size reserved for Logged MDT added
Transport of MDT logs using multiple RRC messages defined
Logging handling at PLMN change clarified | 1.0.1 | 1.0.2 | +| 2010/10 | R2#71b | R2-106018 | RAN2 approved TS v1.1.0 | 1.0.2 | 1.1.0 | + +| | | | | | | +|---------|-------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| 2010/11 | R2#72 | R2-106682 | Requirement on Dependency on Trace added
Validity time for accurate location information in Immediate MDT added
Introduction of UTRA 1.28 TDD metrics | 1.1.0 | 1.1.1 | +| 2010/11 | R2#72 | R2-106936 | RAN2 approved TS v2.0.0 | 1.1.1 | 2.0.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|----------|-----|-----|----------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 2010-12 | RP-50 | RP-101162 | - | - | | TS 37.320 approved b RAN #50 | 10.0.0 | +| 2011-03 | RP-51 | RP-110282 | 000
1 | - | | Clarifications on MDT initiation | 10.1.0 | +| | RP-51 | RP-110282 | 000
2 | - | | Clear MDT configuration and logs when the UE is not registered | 10.1.0 | +| | RP-51 | RP-110282 | 000
3 | 1 | | MDT stage 2 clarifications | 10.1.0 | +| | RP-51 | RP-110282 | 000
4 | - | | On memory size limitation for Logged MDT | 10.1.0 | +| | RP-51 | RP-110282 | 000
5 | - | | UE Capabilities for MDT | 10.1.0 | +| | RP-51 | RP-110282 | 000
6 | - | | Validity time for location information in Immediate MDT | 10.1.0 | +| | RP-51 | RP-110282 | 000
8 | - | | Correction to include CDMA2000 reporting for neighbouring cells | 10.1.0 | +| | RP-51 | RP-110282 | 001
2 | - | | Small Clarifications and Corrections to 37.320 | 10.1.0 | +| | RP-51 | RP-110282 | 001
3 | - | | Trace parameters for MDT configuration | 10.1.0 | +| 2011-06 | RP-52 | RP-110843 | 001
4 | - | | Clarification for logged MDT measurement configuration effectiveness | 10.2.0 | +| | RP-52 | RP-110843 | 001
5 | - | | Correction of log availability reporting | 10.2.0 | +| | RP-52 | RP-110843 | 001
6 | - | | Immediate MDT context handling during inter-PLMN handover | 10.2.0 | +| | RP-52 | RP-110843 | 001
7 | 1 | | MDT UL network measurements | 10.2.0 | +| | RP-52 | RP-110843 | 001
8 | - | | Signalling based Immediate MDT initiation with area scope configuration | 10.2.0 | +| | RP-52 | RP-110843 | 001
9 | - | | TCE ID parameter for logged MDT | 10.2.0 | +| | RP-52 | RP-110843 | 002
0 | - | | Miscellaneous corrections to 37.320 | 10.2.0 | +| | RP-52 | RP-110843 | 002
5 | 1 | | MDT Stage-2 Cleanup | 10.2.0 | +| | RP-52 | RP-110843 | 002
6 | 1 | | Introduction of the User consent | 10.2.0 | +| | RP-52 | RP-110843 | 002
7 | - | | CR to 37.320 to clean up description of RLF Reporting | 10.2.0 | +| 2011-09 | RP-53 | RP-111285 | 003
3 | - | | Immediate MDT context handling during inter-PLMN handover | 10.3.0 | +| | RP-53 | RP-111285 | 003
4 | - | | Miscellaneous corrections to 37.320 | 10.3.0 | +| | RP-53 | RP-111285 | 003
7 | - | | Editorial corrections | 10.3.0 | +| 2011-12 | RP-54 | RP-111714 | 003
8 | - | | CR to 37.320 on Immediate MDT handling at handover | 10.4.0 | +| | RP-54 | RP-111714 | 003
9 | - | | Small Corrections to 37.320 | 10.4.0 | +| 2012-06 | RP-56 | RP-120819 | 004
5 | 1 | | Introduction of MDT enhancements | 11.0.0 | +| 2012-09 | RP-57 | RP-121370 | 004
6 | 1 | | Updates for MDT enhancements | 11.1.0 | +| 2012-12 | RP-58 | RP-121946 | 005
1 | - | | MDT Open Issues Resolutions | 11.2.0 | +| | RP-58 | RP-121946 | 005
2 | - | | Removing the IE Contention Detected in Accessibility Measurement(option 3) | 11.2.0 | +| | RP-58 | RP-121946 | 005
4 | - | | Stage-2 update for MDT enhancements | 11.2.0 | +| | RP-58 | RP-121730 | 005
5 | - | | Multi-PLMN MDT | 11.2.0 | +| 2013-03 | RP-59 | RP-130240 | 005
6 | - | | Miscellaneous MDT corrections | 11.3.0 | + +| | | | | | | | | +|---------|--------|-----------|----------|---|---|-----------------------------------------------------------------------------|--------| +| | RP-59 | RP-130240 | 005
7 | - | | Correction to E-CID positioning for MDT | 11.3.0 | +| | RP-59 | RP-130240 | 005
8 | - | | Corrections for multi-PLMN MDT | 11.3.0 | +| 2014-03 | RP-63 | RP-140347 | 006
1 | - | | Introduction of Cell_FACH with Second DRX to 3G Logged MDT | 12.0.0 | +| 2014-06 | RP-64 | RP-140889 | 006
2 | 1 | | Introduction of MBMS operations Support for E-UTRA | 12.1.0 | +| 2014-09 | RP-65 | RP-141507 | 006
6 | - | | Minor corrections to MDT Stage-2 | 12.2.0 | +| | RP-65 | RP-141496 | 006
4 | 1 | | Reporting and measurement collection triggers for immediate MDT | 12.2.0 | +| 2015-12 | RP-70 | RP-152082 | 006
7 | 1 | | Further Enhancements of MDT for E-UTRA | 13.0.0 | +| 2016-03 | RP-71 | RP-160470 | 006
9 | - | | Reporting of UL PDCP delay measurements for FeMDT | 13.1.0 | +| 2017-03 | RP-75 | | | | | Upgrade to Rel-14, no technical change | 14.0.0 | +| 2018-06 | RP-80 | RP-181227 | 007
1 | 2 | B | 37.320 CR to introduce BT and WLAN in MDT | 15.0.0 | +| | RP-80 | RP-181228 | 007
2 | - | B | Support for logging of 'Any cell selection' state | 15.0.0 | +| 2020-03 | RP-87 | RP-200354 | 007
7 | 2 | B | CR to Introduce NR MDT | 16.0.0 | +| 2020-07 | RP-88 | RP-201184 | 008
5 | 2 | F | CR to 37.320 to support NR MDT | 16.1.0 | +| 2020-09 | RP-89 | RP-201931 | 009
0 | - | F | Corrections to TS37.320 | 16.2.0 | +| 2020-12 | RP-90 | RP-202776 | 009
8 | 1 | F | Merged Corrections for TS37.320 | 16.3.0 | +| 2021-03 | RP-91 | RP-210693 | 010
3 | - | F | Merged Corrections to TS 37.320 | 16.4.0 | +| 2021-06 | RP-92 | RP-211471 | 010
7 | 2 | F | Merged Corrections to TS 37.320 | 16.5.0 | +| 2021-09 | RP-93 | RP-212443 | 011
0 | 1 | F | On UL delay configuration in LTE | 16.6.0 | +| 2021-12 | RP-94 | RP-213344 | 011
2 | - | F | TS37.320 title update | 16.7.0 | +| 2022-03 | RP-95 | RP-220835 | 011
6 | - | F | Immediate MDT configurations for UE in inactive | 16.8.0 | +| 2022-03 | RP-95 | RP-220506 | 010
4 | 2 | D | Inclusive Language Review for TS 37.320 | 17.0.0 | +| | RP-95 | RP-220837 | 011
3 | - | B | Introduction of event-based trigger for LTE MDT logging [LTE-Event-MDT] | 17.0.0 | +| | RP-95 | RP-220837 | 011
4 | 1 | B | On introducing height information reporting in MDT reports [LTE-Height-MDT] | 17.0.0 | +| | RP-95 | RP-220846 | 011
5 | 2 | B | Introduction of Rel-17 MDT enhancements | 17.0.0 | +| 2022-06 | RP-96 | RP-221733 | 011
9 | - | F | Corrections on TS37.320 | 17.1.0 | +| 2022-12 | RP-98 | RP-223410 | 012
1 | - | F | Correction to Logged MDT type handling | 17.2.0 | +| 2023-03 | RP-99 | RP-230689 | 012
3 | - | F | Miscellaneous corrections on TS 37.320 for MDT | 17.3.0 | +| 2023-06 | RP-100 | RP-231413 | 012
4 | 1 | F | Correction to NR M3 measurement | 17.4.0 | +| | RP-100 | RP-231413 | 012
6 | - | F | Stage-2 correction on the UL PDCP packet average delay | 17.4.0 | +| 2023-09 | RP-101 | RP-232568 | 012
7 | 1 | F | CR to 37320 on RLF report and CEF report | 17.5.0 | +| 2023-12 | RP-102 | RP-233909 | 012
8 | - | B | Introduction of MDT enhancements to support Non-Public Networks | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37324/raw.md b/marked/Rel-18/37_series/37324/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..137f178c0e74bec7ebe731ecb1a16ce9f2c6370a --- /dev/null +++ b/marked/Rel-18/37_series/37324/raw.md @@ -0,0 +1,609 @@ + + +# 3GPP TS 37.324 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. Below the "3GPP" text is a red graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General..... | 7 | +| 4.1 Introduction ..... | 7 | +| 4.2 SDAP architecture..... | 7 | +| 4.2.1 SDAP structure ..... | 7 | +| 4.2.2 SDAP entities ..... | 8 | +| 4.3 Services ..... | 9 | +| 4.3.1 Services provided to upper layers..... | 9 | +| 4.3.2 Services expected from lower layers..... | 9 | +| 4.4 Functions ..... | 9 | +| 5 SDAP procedures..... | 9 | +| 5.1 SDAP entity handling..... | 9 | +| 5.1.1 SDAP entity establishment..... | 9 | +| 5.1.2 SDAP entity release..... | 9 | +| 5.2 Data transfer ..... | 10 | +| 5.2.1 Uplink..... | 10 | +| 5.2.2 Downlink..... | 10 | +| 5.2.3 SL transmission ..... | 10 | +| 5.2.4 SL reception..... | 11 | +| 5.3 QoS flow to DRB mapping ..... | 11 | +| 5.3.1 Configuration..... | 11 | +| 5.3.2 Reflective mapping..... | 12 | +| 5.3.3 DRB release..... | 12 | +| 5.4 RQI handling..... | 12 | +| 5.5 PC5 QoS flow to SL-DRB mapping ..... | 12 | +| 5.5.1 Configuration..... | 12 | +| 5.5.2 SL-DRB release..... | 13 | +| 6 Protocol data units, formats, and parameters ..... | 13 | +| 6.1 Protocol data units..... | 13 | +| 6.1.1 Data PDU..... | 13 | +| 6.1.2 Control PDU ..... | 13 | +| 6.2 Formats..... | 13 | +| 6.2.1 General ..... | 13 | +| 6.2.2 Data PDU..... | 13 | +| 6.2.2.1 Data PDU without SDAP header..... | 13 | +| 6.2.2.2 DL Data PDU with SDAP header..... | 14 | +| 6.2.2.3 UL Data PDU with SDAP header..... | 14 | +| 6.2.2.4 SL Data PDU with SDAP header for unicast of NR sidelink communication..... | 14 | +| 6.2.3 End-Marker Control PDU ..... | 15 | +| 6.3 Parameters ..... | 15 | +| 6.3.1 General ..... | 15 | +| 6.3.2 Data..... | 15 | +| 6.3.3 D/C ..... | 15 | +| 6.3.4 QFI..... | 15 | +| 6.3.5 R ..... | 16 | +| 6.3.6 RQI..... | 16 | +| 6.3.7 RDI..... | 16 | +| 6.3.8 PQFI ..... | 16 | + +**Annex A (informative): Change history................................................................................................................ 17** + +# --- 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 Service Data Adaptation Protocol (SDAP) for a UE with connection to the 5G-CN or for a UE in NR sidelink communication. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.300: "NG Radio Access Network; Overall description". +- [3] 3GPP TS 38.331: "NR Radio Resource Control (RRC); Protocol Specification". +- [4] 3GPP TS 23.501: "System Architecture for the 5G System". +- [5] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [6] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3". + +# 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]. + +**PC5 QoS flow to SL-DRB mapping rule:** a mapping rule determining on which SL-DRB packets of a PC5 QoS flow shall be carried. + +**QoS flow to DRB mapping rule:** a mapping rule determining on which DRB packets of a QoS flow shall be carried. + +**Reflective QoS flow to DRB mapping:** a QoS flow to DRB mapping scheme where a UE monitors the QoS flow to DRB mapping rule in the DL, and applies it to in the UL. + +**NR sidelink communication:** AS functionality enabling at least V2X communication as defined in TS 23.287 [5], between two or more nearby UEs, using NR technology but not traversing any network node. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------|-----------------| +| PQFI | PC5 QoS Flow ID | +|------|-----------------| + +| | | +|--------|-----------------------------------------------| +| QFI | QoS Flow ID | +| RDI | Reflective QoS flow to DRB mapping Indication | +| RQI | Reflective QoS Indication | +| SDAP | Service Data Adaptation Protocol | +| SL | Sidelink | +| SL-DRB | Sidelink Data Radio Bearer | + +# 4 General + +## 4.1 Introduction + +The objective is to describe the SDAP architecture and the SDAP entity from a functional point of view. The specified functionality only applies to UE with connection to the 5G-CN and UE in NR sidelink communication. + +## 4.2 SDAP architecture + +### 4.2.1 SDAP structure + +Figure 4.2.1-1 illustrates one possible structure for the SDAP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2]. + +![Diagram of SDAP sublayer structure showing QoS Flows, SDAP entities, Radio Bearers, and PDCP entities.](e2c1c672349c10dccb2563eff6d8260e_img.jpg) + +The diagram illustrates the SDAP sublayer structure. At the top, multiple 'QoS Flows' are shown, each connected to an 'SDAP-SAP' (Service Access Point). These SAPs are part of the 'SDAP sublayer', which contains two 'SDAP entity' blocks. Below the SDAP sublayer, there are 'Radio Bearers', also connected to 'SDAP-SAP' points. Between the SDAP sublayer and the 'PDCP sublayer' are two boxes labeled 'SDAP - PDU' and 'PDCP - SDU'. The 'PDCP sublayer' contains four 'PDCP entity' blocks. Vertical double-headed arrows connect the 'SDAP-SAP' points in the SDAP sublayer to the 'PDCP-SAP' points in the PDCP sublayer, indicating data flow through the Radio Bearers. + +Diagram of SDAP sublayer structure showing QoS Flows, SDAP entities, Radio Bearers, and PDCP entities. + +Figure 4.2.1-1: SDAP sublayer, structure view + +The SDAP sublayer is configured for DRBs by RRC (TS 38.331 [3]). The SDAP sublayer maps QoS flows to DRBs. One or more QoS flows may be mapped onto one DRB. One QoS flow is mapped onto only one DRB at a time in the UL. + +The SDAP sublayer is configured for MRBs by RRC (TS 38.331 [3]). The SDAP sublayer maps MBS QoS flows to MRBs. One or more MBS QoS flows may be mapped onto one MRB. + +In NR sidelink communication, the SDAP sublayer maps PC5 QoS flows to SL-DRBs. One or more PC5 QoS flows may be mapped onto one SL-DRB. One PC5 QoS flow is mapped onto only one SL-DRB at a time in the NR sidelink for transmission. + +### 4.2.2 SDAP entities + +The SDAP entities are located in the SDAP sublayer. Several SDAP entities may be defined for a UE. There is an SDAP entity configured for each individual PDU session or MBS session for NR Uu. For NR sidelink, SDAP entity is configured per Destination Layer-2 ID and cast type in the UE. + +An SDAP entity receives/delivers SDAP SDUs from/to upper layers and submits/receives SDAP data PDUs to/from its peer SDAP entity via lower layers. + +- At the transmitting side, when an SDAP entity receives an SDAP SDU from upper layers, it constructs the corresponding SDAP data PDU and submits it to lower layers; +- At the receiving side, when an SDAP entity receives an SDAP data PDU from lower layers, it retrieves the corresponding SDAP SDU and delivers it to upper layers. + +Figure 4.2.2-1 illustrates the functional view of the SDAP entity for the SDAP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2]. + +![Figure 4.2.2-1: SDAP layer, functional view. The diagram shows the functional flow of data through the SDAP layer on both the transmitting (UE/NG-RAN/UEA) and receiving (NG-RAN/UE/UEB) sides, connected by a Radio Interface (Uu/PC5).](731f533b0599c8e42a063f06e4332045_img.jpg) + +The diagram illustrates the functional view of the SDAP layer across two entities: UE/NG-RAN/UEA (left) and NG-RAN/UE/UEB (right), connected by a Radio Interface (Uu/PC5). + +**Transmitting Side (UE/NG-RAN/UEA):** + +- A **QoS flow** enters the **Transmitting SDAP entity**. +- The flow goes to **Mapping of QoS flow to a DRB/MRB/SL DRB**. +- From this mapping, two paths emerge: + - If the **SDAP header is configured**, it goes to **Adding SDAP header** and then down to the Radio Interface. + - If the **SDAP header is not configured**, it goes directly down to the Radio Interface. + +**Receiving Side (NG-RAN/UE/UEB):** + +- Data from the Radio Interface enters the **Receiving SDAP entity**. +- Two paths emerge from the interface: + - If the **SDAP header is configured**, it goes to **Removing SDAP header** and then up to the **QoS flow** output. + - If the **SDAP header is not configured**, it goes to a dashed box labeled **Reflective QoS flow to DRB mapping**, then up to **Removing SDAP header**, and finally up to the **QoS flow** output. + +Figure 4.2.2-1: SDAP layer, functional view. The diagram shows the functional flow of data through the SDAP layer on both the transmitting (UE/NG-RAN/UEA) and receiving (NG-RAN/UE/UEB) sides, connected by a Radio Interface (Uu/PC5). + +**Figure 4.2.2-1: SDAP layer, functional view** + +Reflective QoS flow to DRB mapping is performed at UE, as specified in the clause 5.3.2, if DL SDAP header is configured. + +Reflective QoS flow to MRB mapping is not supported. There is no SDAP header for MRB. + +For NR sidelink communication, reflective PC5 QoS flow to SL-DRB mapping is not supported. + +## 4.3 Services + +### 4.3.1 Services provided to upper layers + +The SDAP sublayer provides its service to the user plane upper layers. The following services are provided by SDAP to upper layers: + +- transfer of user plane data. + +### 4.3.2 Services expected from lower layers + +An SDAP entity expects the following services from lower layers: + +- user plane data transfer service; +- in-order delivery except when out of order delivery is configured by RRC (TS 38.331 [3]). + +## 4.4 Functions + +The SDAP sublayer supports the following functions: + +- transfer of user plane data; +- mapping between a QoS flow and a DRB for both DL and UL; +- mapping between an MBS QoS flow and an MRB for DL; +- mapping between a PC5 QoS flow and a SL-DRB for NR sidelink communication; +- marking QoS flow ID in both DL and UL packets; +- marking PC5 QoS flow ID in unicast of NR sidelink communication packets; +- reflective QoS flow to DRB mapping for the UL SDAP data PDUs. + +# --- 5 SDAP procedures + +## 5.1 SDAP entity handling + +### 5.1.1 SDAP entity establishment + +When RRC (TS 38.331 [3]) requests an SDAP entity establishment, the UE shall: + +- establish an SDAP entity; +- follow the procedures in clause 5.2.1 and 5.2.2. + +When RRC (TS 38.331 [3]) requests establishment of an SDAP entity for unicast, groupcast or broadcast of NR sidelink communication, the UE shall: + +- establish an SDAP entity; +- follow the procedures in clauses 5.2.3 and 5.2.4. + +### 5.1.2 SDAP entity release + +When RRC (TS 38.331 [3]) requests an SDAP entity release, the UE shall: + +- release the SDAP entity. + +When RRC (TS 38.331 [3]) requests release of an SDAP entity for unicast, groupcast or broadcast of NR sidelink communication, the UE shall: + +- release the SDAP entity. + +## 5.2 Data transfer + +### 5.2.1 Uplink + +At the reception of an SDAP SDU from upper layer for a QoS flow, the transmitting SDAP entity shall: + +- if there is no stored QoS flow to DRB mapping rule for the QoS flow as specified in the clause 5.3: + - map the SDAP SDU to the default DRB; +- else: + - map the SDAP SDU to the DRB according to the stored QoS flow to DRB mapping rule; +- if the DRB to which the SDAP SDU is mapped is configured by RRC (TS 38.331 [3]) with the presence of SDAP header, + - construct the UL SDAP data PDU as specified in the clause 6.2.2.3; +- else: + - construct the UL SDAP data PDU as specified in the clause 6.2.2.1; +- submit the constructed UL SDAP data PDU to the lower layers. + +NOTE 1: UE behaviour is not defined if there is neither a default DRB nor a stored QoS flow to DRB mapping rule for the QoS flow. + +NOTE 2: Default DRB is always configured with UL SDAP header (TS 38.331 [3]). + +### 5.2.2 Downlink + +At the reception of an SDAP data PDU from lower layers for a QoS flow, the receiving SDAP entity shall: + +- if this SDAP data PDU is received from an MRB: + - retrieve the SDAP SDU from the DL SDAP data PDU as specified in the clause 6.2.2.1. +- if the DRB from which this SDAP data PDU is received is configured by RRC (TS 38.331 [3]) with the presence of SDAP header: + - perform reflective QoS flow to DRB mapping as specified in the clause 5.3.2; + - perform RQI handling as specified in the clause 5.4; + - retrieve the SDAP SDU from the DL SDAP data PDU as specified in the clause 6.2.2.2. +- else: + - retrieve the SDAP SDU from the DL SDAP data PDU as specified in the clause 6.2.2.1; +- deliver the retrieved SDAP SDU to the upper layer. + +### 5.2.3 SL transmission + +At the reception of an SDAP SDU from upper layer for a PC5 QoS flow, the transmitting SDAP entity shall: + +- if there is no stored PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow as specified in the clause 5.5: + - map the SDAP SDU to the default SL-DRB; +- else: + - map the SDAP SDU to the SL-DRB according to the stored PC5 QoS flow to SL-DRB mapping rule; +- if the SL-DRB to which the SDAP SDU is mapped is configured by RRC (TS 38.331 [3]) with the presence of SDAP header: + - construct the SL SDAP data PDU as specified in the clause 6.2.2.4; +- else: + - construct the SL SDAP data PDU as specified in the clause 6.2.2.1; +- submit the constructed SL SDAP data PDU to the lower layers. + +### 5.2.4 SL reception + +At the reception of an SDAP data PDU from lower layers for a PC5 QoS flow, the receiving SDAP entity shall: + +- if the SL-DRB from which this SDAP data PDU is received is configured by RRC (TS 38.331 [3]) with the presence of SDAP header: + - retrieve the SDAP SDU from the SL SDAP data PDU as specified in the clause 6.2.2.4; +- else: + - retrieve the SDAP SDU from the SL SDAP data PDU as specified in the clause 6.2.2.1; +- deliver the retrieved SDAP SDU to the upper layer. + +## 5.3 QoS flow to DRB mapping + +### 5.3.1 Configuration + +When RRC (TS 38.331 [3]) configures an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall: + +- if the SDAP entity has already been established and there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured: + - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow; + - map the end-marker control PDU to the default DRB; + - submit the end-marker control PDU to the lower layers. +- if the stored UL QoS flow to DRB mapping rule is different from the configured QoS flow to DRB mapping rule for the QoS flow and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of UL SDAP header: + - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow; + - map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule; + - submit the end-marker control PDU to the lower layers. +- store the configured UL QoS flow to DRB mapping rule for the QoS flow. + +When RRC (TS 38.331 [3]) releases an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall: + +- remove the UL QoS flow to DRB mapping rule for the QoS flow. + +### 5.3.2 Reflective mapping + +For each received DL SDAP data PDU with RDI set to 1, the SDAP entity shall: + +- process the QFI field in the SDAP header and determine the QoS flow; +- if there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured: + - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow; + - map the end-marker control PDU to the default DRB; + - submit the end-marker control PDU to the lower layers; +- if the stored QoS flow to DRB mapping rule for the QoS flow is different from the QoS flow to DRB mapping of the DL SDAP data PDU and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of UL SDAP header: + - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow; + - map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule; + - submit the end-marker control PDU to the lower layers; +- store the QoS flow to DRB mapping of the DL SDAP data PDU as the QoS flow to DRB mapping rule for the UL. + +### 5.3.3 DRB release + +When RRC (TS 38.331 [3]) indicates that a DRB is released, the SDAP entity shall: + +- remove all QoS flow to DRB mappings associated with the released DRB based on the clauses 5.3.1 and 5.3.2. + +## 5.4 RQI handling + +For each received DL SDAP data PDU with RQI set to 1, the SDAP entity shall: + +- inform the NAS layer of the RQI and QFI. + +## 5.5 PC5 QoS flow to SL-DRB mapping + +### 5.5.1 Configuration + +When RRC (TS 38.331 [3]) configures a PC5 QoS flow to SL-DRB mapping rule for a PC5 QoS flow, the SDAP entity shall: + +- for unicast of NR sidelink communication, if the SDAP entity has already been established and there is no stored SL-DRB mapping rule for the PC5 QoS flow and a default SL-DRB is configured: + - construct an end-marker control PDU, as specified in the clause 6.2.3, for the PC5 QoS flow; + - map the end-marker control PDU to the default SL-DRB; + - submit the end-marker control PDU to the lower layers; +- for unicast of NR sidelink communication, if the stored PC5 QoS flow to SL-DRB mapping rule is different from the configured PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow and the SL-DRB according + +to the stored PC5 QoS flow to SL-DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of SL SDAP header: + +- construct an end-marker control PDU, as specified in the clause 6.2.3, for the PC5 QoS flow; +- map the end-marker control PDU to the SL-DRB according to the stored PC5 QoS flow to SL-DRB mapping rule; +- submit the end-marker control PDU to the lower layers; +- store the configured PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow. + +When RRC (TS 38.331 [3]) releases a PC5 QoS flow to SL-DRB mapping rule for a PC5 QoS flow, the SDAP entity shall: + +- remove the PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow. + +### 5.5.2 SL-DRB release + +When RRC (TS 38.331 [3]) indicates that an SL-DRB is released, the SDAP entity shall: + +- remove all PC5 QoS flow to SL-DRB mappings associated with the released SL-DRB based on the clause 5.5.1. + +# --- 6 Protocol data units, formats, and parameters + +## 6.1 Protocol data units + +### 6.1.1 Data PDU + +The SDAP Data PDU is used to convey one or more of followings: + +- SDAP header; +- user plane data. + +### 6.1.2 Control PDU + +#### a) End-Marker Control PDU + +End-Marker control PDU is used by the SDAP entity at UE to indicate that it stops the mapping of the SDAP SDU of the QoS flow indicated by the QFI/PQFI to the DRB/SL-DRB on which the End-Marker control PDU is transmitted. + +## 6.2 Formats + +### 6.2.1 General + +A SDAP PDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. In the figures in clause 6.2, bit strings are represented by tables in which the first and most significant bit is the left most bit of the first line of the table, the last and least significant bit is the rightmost bit of 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. + +SDAP SDUs are bit strings that are byte aligned (i.e. multiple of 8 bits) in length. An SDAP SDU is included into a SDAP PDU from the first bit onward. + +For groupcast and broadcast of NR sidelink communication, only SDAP data PDU without SDAP header is supported. + +### 6.2.2 Data PDU + +#### 6.2.2.1 Data PDU without SDAP header + +An SDAP PDU consists only of a data field and does not consist of any SDAP header, as described in Figure 6.2.2.1-1. + +![Diagram of SDAP Data PDU format without SDAP header. It shows a vertical stack of data blocks. The top block is labeled 'Data' and 'Oct 1'. Below it is an ellipsis '....'. The bottom block is labeled 'Oct N'.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +| | | | | | | | | | +|------|--|--|--|--|--|--|--|-------| +| | | | | | | | | | +| Data | | | | | | | | Oct 1 | +| .... | | | | | | | | | +| | | | | | | | | Oct N | + +Diagram of SDAP Data PDU format without SDAP header. It shows a vertical stack of data blocks. The top block is labeled 'Data' and 'Oct 1'. Below it is an ellipsis '....'. The bottom block is labeled 'Oct N'. + +Figure 6.2.2.1-1: SDAP Data PDU format without SDAP header + +#### 6.2.2.2 DL Data PDU with SDAP header + +Figure 6.2.2.2 – 1 shows the format of SDAP Data PDU of DL with SDAP header being configured. + +![Diagram of DL SDAP Data PDU format with SDAP header. The first octet is split into RDI and RQI. The next octet is QFI. Subsequent octets are Data blocks labeled Oct 2, ..., Oct N.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +| | | | | | | | | | +|------|-----|-----|--|--|--|--|--|-------| +| | | | | | | | | | +| RDI | RQI | QFI | | | | | | Oct 1 | +| Data | | | | | | | | Oct 2 | +| ... | | | | | | | | | +| Data | | | | | | | | Oct N | + +Diagram of DL SDAP Data PDU format with SDAP header. The first octet is split into RDI and RQI. The next octet is QFI. Subsequent octets are Data blocks labeled Oct 2, ..., Oct N. + +Figure 6.2.2.2-1: DL SDAP Data PDU format with SDAP header + +#### 6.2.2.3 UL Data PDU with SDAP header + +Figure 6.2.2.3 – 1 shows the format of SDAP Data PDU of UL with SDAP header being configured. + +![Diagram of UL SDAP Data PDU format with SDAP header. The first octet is split into D/C and R. The next octet is QFI. Subsequent octets are Data blocks labeled Oct 2, ..., Oct N.](2bc39576969969ffe6d3f3d5264bba75_img.jpg) + +| | | | | | | | | | +|------|---|-----|--|--|--|--|--|-------| +| | | | | | | | | | +| D/C | R | QFI | | | | | | Oct 1 | +| Data | | | | | | | | Oct 2 | +| ... | | | | | | | | | +| Data | | | | | | | | Oct N | + +Diagram of UL SDAP Data PDU format with SDAP header. The first octet is split into D/C and R. The next octet is QFI. Subsequent octets are Data blocks labeled Oct 2, ..., Oct N. + +Figure 6.2.2.3-1: UL SDAP Data PDU format with SDAP header + +#### 6.2.2.4 SL Data PDU with SDAP header for unicast of NR sidelink communication + +Figure 6.2.2.4–1 shows the format of SDAP Data PDU for unicast of NR sidelink communication with SDAP header being configured. + +![Figure 6.2.2.4-1: SL SDAP Data PDU format with SDAP header for unicast of NR sidelink communication. The diagram shows a sequence of octets. The first octet (Oct 1) is divided into three fields: D/C (1 bit), R (1 bit), and PQFI (6 bits). Subsequent octets (Oct 2 to Oct N) contain Data. An ellipsis indicates intermediate octets.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 6.2.2.4-1: SL SDAP Data PDU format with SDAP header for unicast of NR sidelink communication. The diagram shows a sequence of octets. The first octet (Oct 1) is divided into three fields: D/C (1 bit), R (1 bit), and PQFI (6 bits). Subsequent octets (Oct 2 to Oct N) contain Data. An ellipsis indicates intermediate octets. + +Figure 6.2.2.4-1: SL SDAP Data PDU format with SDAP header for unicast of NR sidelink communication + +### 6.2.3 End-Marker Control PDU + +Figure 6.2.3-1 shows the format of End-Marker Control PDU. + +![Figure 6.2.3-1: End-Marker Control PDU. The diagram shows a single octet (Oct 1) divided into three fields: D/C (1 bit), R (1 bit), and QFI/PQFI (6 bits).](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +Figure 6.2.3-1: End-Marker Control PDU. The diagram shows a single octet (Oct 1) divided into three fields: D/C (1 bit), R (1 bit), and QFI/PQFI (6 bits). + +Figure 6.2.3-1: End-Marker Control PDU + +## 6.3 Parameters + +### 6.3.1 General + +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 is the first and most significant bit 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. + +### 6.3.2 Data + +Length: Variable + +This field includes the SDAP SDU. + +### 6.3.3 D/C + +Length: 1 bit, + +The D/C bit indicates whether the SDAP PDU is an SDAP Data PDU or an SDAP Control PDU. + +Table 6.3.3-1: D/C field + +| Bit | Description | +|-----|-------------| +| 0 | Control PDU | +| 1 | Data PDU | + +### 6.3.4 QFI + +Length: 6 bits + +The QFI field indicates the ID of the QoS flow (TS 23.501 [4]) to which the SDAP PDU belongs. + +### 6.3.5 R + +Length: 1 bit + +Reserved. In this version of the specification reserved bits shall be set to 0. Reserved bits shall be ignored by the receiver. + +### 6.3.6 RQI + +Length: 1 bit, + +The RQI bit indicates whether NAS should be informed of the updated of SDF to QoS flow mapping rules (TS 23.501 [4]). + +**Table 6.3.6-1: RQI field** + +| Bit | Description | +|-----|-----------------------------------------| +| 0 | No action | +| 1 | To inform NAS that RQI bit is set to 1. | + +### 6.3.7 RDI + +Length: 1 bit, + +The RDI bit indicates whether QoS flow to DRB mapping rule should be updated. + +**Table 6.3.7-1: RDI field** + +| Bit | Description | +|-----|----------------------------------------| +| 0 | No action | +| 1 | To store QoS flow to DRB mapping rule. | + +### 6.3.8 PQFI + +Length: 6 bits + +The PQFI field indicates the ID of the PC5 QoS flow (as specified in TS 24.587[6]) to which the SDAP PDU belongs. \ No newline at end of file diff --git a/marked/Rel-18/37_series/37340/raw.md b/marked/Rel-18/37_series/37340/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9020d6f85e63069cf0f90c755a3fe0500a531423 --- /dev/null +++ b/marked/Rel-18/37_series/37340/raw.md @@ -0,0 +1,5522 @@ + + +# 3GPP TS 37.340 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 18)** --- + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is a small red signal icon. Below the icon, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 9 | +| 4 Multi-Radio Dual Connectivity ..... | 10 | +| 4.1 General ..... | 10 | +| 4.1.1 Common MR-DC principles ..... | 10 | +| 4.1.2 MR-DC with the EPC..... | 10 | +| 4.1.3 MR-DC with the 5GC ..... | 11 | +| 4.1.3.1 E-UTRA-NR Dual Connectivity ..... | 11 | +| 4.1.3.2 NR-E-UTRA Dual Connectivity ..... | 11 | +| 4.1.3.3 NR-NR Dual Connectivity..... | 11 | +| 4.2 Radio Protocol Architecture..... | 11 | +| 4.2.1 Control Plane ..... | 11 | +| 4.2.2 User Plane..... | 12 | +| 4.3 Network interfaces ..... | 14 | +| 4.3.1 Control Plane ..... | 14 | +| 4.3.1.1 Common MR-DC principles..... | 14 | +| 4.3.1.2 MR-DC with EPC..... | 15 | +| 4.3.1.3 MR-DC with 5GC..... | 15 | +| 4.3.2 User Plane..... | 15 | +| 4.3.2.1 Common MR-DC principles..... | 15 | +| 4.3.2.2 MR-DC with EPC..... | 16 | +| 4.3.2.3 MR-DC with 5GC..... | 16 | +| 5 Layer 1 related aspects..... | 16 | +| 6 Layer 2 related aspects..... | 17 | +| 6.1 MAC Sublayer..... | 17 | +| 6.2 RLC Sublayer..... | 17 | +| 6.3 PDCP Sublayer..... | 17 | +| 6.4 SDAP Sublayer ..... | 18 | +| 6.5 BAP Sublayer..... | 18 | +| 7 RRC related aspects ..... | 18 | +| 7.1 System information handling ..... | 18 | +| 7.2 Measurements..... | 18 | +| 7.3 UE capability coordination..... | 20 | +| 7.4 Handling of combined MN/SN RRC messages ..... | 21 | +| 7.5 SRB3 ..... | 21 | +| 7.6 Split SRB..... | 22 | +| 7.7 SCG/MCG failure handling ..... | 22 | +| 7.8 UE identities..... | 23 | +| 7.9 Inter-node Resource Coordination ..... | 23 | +| 7.10 UE assistance information..... | 23 | +| 7.11 F1-C transfer over E-UTRA..... | 24 | +| 7.14 RLM/BFD relaxation ..... | 25 | +| 8 Bearer handling aspects ..... | 25 | +| 8.1 QoS aspects ..... | 25 | +| 8.2 Bearer type selection..... | 27 | +| 8.3 Bearer type change..... | 28 | +| 8.4 User data forwarding..... | 28 | + +| | | | +|---------|------------------------------------------------------------------------------------------------|-----| +| 9 | Security related aspects ..... | 29 | +| 10 | Multi-Connectivity operation related aspects ..... | 30 | +| 10.1 | General ..... | 30 | +| 10.2 | Secondary Node Addition ..... | 30 | +| 10.2.1 | EN-DC ..... | 30 | +| 10.2.2 | MR-DC with 5GC ..... | 34 | +| 10.2.3 | Conditional PSCell Addition ..... | 39 | +| 10.3 | Secondary Node Modification (MN/SN initiated) ..... | 39 | +| 10.3.1 | EN-DC ..... | 39 | +| 10.3.2 | MR-DC with 5GC ..... | 46 | +| 10.4 | Secondary Node Release (MN/SN initiated) ..... | 54 | +| 10.4.1 | EN-DC ..... | 54 | +| 10.4.2 | MR-DC with 5GC ..... | 56 | +| 10.5 | Secondary Node Change (MN/SN initiated) ..... | 59 | +| 10.5.1 | EN-DC ..... | 59 | +| 10.5.2 | MR-DC with 5GC ..... | 66 | +| 10.6 | PSCell change ..... | 74 | +| 10.7 | Inter-Master Node handover with/without Secondary Node change ..... | 75 | +| 10.7.1 | EN-DC ..... | 75 | +| 10.7.2 | MR-DC with 5GC ..... | 77 | +| 10.8 | Master Node to eNB/gNB Change ..... | 79 | +| 10.8.1 | EN-DC ..... | 79 | +| 10.8.2 | MR-DC with 5GC ..... | 81 | +| 10.9 | eNB/gNB to Master Node change ..... | 83 | +| 10.9.1 | EN-DC ..... | 83 | +| 10.9.2 | MR-DC with 5GC ..... | 84 | +| 10.10 | RRC Transfer ..... | 85 | +| 10.10.1 | EN-DC ..... | 85 | +| 10.10.2 | MR-DC with 5GC ..... | 87 | +| 10.11 | Secondary RAT data volume reporting ..... | 90 | +| 10.11.1 | EN-DC ..... | 90 | +| 10.11.2 | MR-DC with 5GC ..... | 91 | +| 10.12 | Activity Notification ..... | 92 | +| 10.12.1 | EN-DC ..... | 92 | +| 10.12.2 | MR-DC with 5GC ..... | 95 | +| 10.13 | Notification Control Indication ..... | 98 | +| 10.13.1 | EN-DC ..... | 98 | +| 10.13.2 | MR-DC with 5GC ..... | 98 | +| 10.14 | PDU Session Split at UPF ..... | 98 | +| 10.14.1 | PDU Session Split at UPF during PDU session resource setup ..... | 98 | +| 10.14.2 | PDU Session Split at UPF during PDU session resource modify (5GC initiated) ..... | 99 | +| 10.14.3 | PDU Session Split at UPF (RAN initiated QoS flows offloading from MN to SN) ..... | 99 | +| 10.15 | F1-C Traffic Transfer ..... | 102 | +| 10.16 | Support of inter-system handover involving EN-DC or MR-DC with 5GC ..... | 103 | +| 10.16.1 | General ..... | 103 | +| 10.16.2 | Inter-system handover from EPS to 5GS with the Secondary Node used as target ..... | 103 | +| 10.16.3 | Inter-system handover from 5GS to EPS with the Source Node used as target Secondary Node ..... | 104 | +| 10.17 | Inter-Master Node RRC Resume without Secondary Node change ..... | 105 | +| 10.17.1 | MR-DC with 5GC ..... | 105 | +| 10.18 | Self-optimisation for PSCell change ..... | 107 | +| 10.18.1 | General ..... | 107 | +| 10.18.2 | PSCell change failure ..... | 107 | +| 10.18.3 | Conditional PSCell addition or change failure ..... | 108 | +| 10.18.4 | Successful PSCell Change Report ..... | 108 | +| 10.18.5 | RA Report retrieval ..... | 109 | +| 10.19 | Conditional Handover with Secondary Node ..... | 109 | +| 10.19.1 | EN-DC ..... | 109 | +| 10.19.2 | MR-DC with 5GC ..... | 112 | +| 10.19.3 | CHO with candidate SCG(s) ..... | 116 | +| 10.20 | Subsequent Conditional PSCell Addition or Change ..... | 116 | + +| | | | +|----------------------------------------------------------------------------|--------------------------------------------------------------------|------------| +| 11 | Service related aspects ..... | 125 | +| 11.1 | Roaming and Access Restrictions ..... | 125 | +| 11.2 | Support of Network Sharing ..... | 125 | +| 11.3 | ARPI/SPID Handling from MN..... | 125 | +| 12 | X2/Xn Interface related aspects ..... | 125 | +| 13 | Other aspects..... | 125 | +| 13.1 | Interference avoidance for in-device coexistence..... | 125 | +| 13.2 | Sidelink..... | 125 | +| 13.3 | SCG UE history information..... | 126 | +| 13.4 | Application Layer Measurement Collection ..... | 126 | +| 13.4.1 | Overview ..... | 126 | +| 13.4.2 | SRB5..... | 126 | +| 13.4.3 | QoE Measurement Configuration..... | 126 | +| 13.4.3.1 | QoE Measurement Collection Activation and Reporting in NR-DC ..... | 126 | +| 13.4.3.2 | RAN Overload Handling ..... | 128 | +| 13.4.4 | QoE Measurement Continuity for Mobility ..... | 128 | +| Annex A (informative): Layer 2 handling for bearer type change..... | | 129 | +| Annex B (informative): Supported MR-DC Handover Scenarios..... | | 131 | +| Annex C (informative): Change history..... | | 132 | + +# --- 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 provides an overview of the multi-connectivity operation using E-UTRA and NR radio access technologies. Details of the network and radio interface protocols are specified in companion specifications of the 36 and 38 series. + +# --- 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 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [3] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage 2". +- [4] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification". +- [5] 3GPP TS 38.423: "NG-RAN; Xn application protocol (XnAP)". +- [6] 3GPP TS 38.425: "NG-RAN; NR user plane protocol". +- [7] 3GPP TS 38.401: "NG-RAN; Architecture description". +- [8] 3GPP TS 38.133: "NG-RAN; Requirements for support of radio resource management". +- [9] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)". +- [10] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [11] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [12] 3GPP TS 38.101-1: "User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [13] 3GPP TS 38.101-2: "User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [14] 3GPP TS 38.101-3: "User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios". +- [15] 3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification". +- [16] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification". +- [17] 3GPP TS 38.340: "Backhaul Adaptation Protocol (BAP) specification". + +- [18] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ". +- [19] 3GPP TS 23.285: "Architecture enhancements for V2X services". +- [20] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [21] 3GPP TS 38.213: "NR; Physical layer procedures". +- [22] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [23] 3GPP TS 38.473: "F1 application protocol (F1AP)". +- [24] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [25] 3GPP TS 23.586: "Technical Specification Group Services and System Aspects; Architectural Enhancements to support Ranging based services and Sidelink Positioning". + +# --- 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] and TS 36.300 [2]. + +**Child node:** IAB-DU's or IAB-donor-DU's next hop neighbour IAB-node. + +**Conditional PSCell Addition:** a PSCell addition procedure that is executed only when PSCell addition execution condition is met. + +**Conditional PSCell Change:** a PSCell change procedure that is executed only when PSCell change execution condition is met. + +**En-gNB:** node providing NR user plane and control plane protocol terminations towards the UE, and acting as Secondary Node in EN-DC. + +**Fast MCG link recovery:** in MR-DC, an RRC procedure where the UE sends an MCG Failure Information message to the MN via the SCG upon the detection of a radio link failure on the MCG. + +**IAB-donor:** gNB that provides network access to UEs via a network of backhaul and access links. + +**IAB-MT:** IAB-node function that terminates the Uu interface to the parent node using the procedures and behaviours specified for UEs unless stated otherwise. + +**IAB-node:** RAN node that supports NR access links to UEs and NR backhaul links to parent nodes and child nodes. The IAB-node does not support backhauling via E-UTRA. + +**Master Cell Group:** in MR-DC, a group of serving cells associated with the Master Node, comprising of the SpCell (PCell) and optionally one or more SCells. + +**Master node:** in MR-DC, the radio access node that provides the control plane connection to the core network. It may be a Master eNB (in EN-DC), a Master ng-eNB (in NGEN-DC) or a Master gNB (in NR-DC and NE-DC). + +**MCG bearer:** in MR-DC, a radio bearer with an RLC bearer (or two RLC bearers, in case of CA packet duplication in an E-UTRAN cell group, or up to four RLC bearers in case of CA packet duplication in a NR cell group) only in the MCG. + +**MN terminated bearer:** in MR-DC, a radio bearer for which PDCP is located in the MN. + +**MCG SRB:** in MR-DC, a direct SRB between the MN and the UE. + +**Multi-Radio Dual Connectivity:** Dual Connectivity between E-UTRA and NR nodes, or between two NR nodes. + +**Ng-eNB:** as defined in TS 38.300 [3]. + +**NR sidelink communication:** AS functionality enabling at least V2X Communication as defined in TS 23.287 [18] and ProSe Communication (including ProSe UE-to-Network Relay and non-Relay communication) as defined in TS 23.304 [24], between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink discovery:** AS functionality enabling ProSe non-Relay Discovery and ProSe UE-to-Network Relay discovery for Proximity based Services as defined in TS 23.304 [24] between two or more nearby UEs, using NR technology but not traversing any network node. + +**Parent node:** IAB-MT's next hop neighbour node; the parent node can be IAB-node or IAB-donor-DU. + +**PCell:** SpCell of a master cell group. + +**PSCell:** SpCell of a secondary cell group. + +**Ranging/Sidelink Positioning:** AS functionality enabling ranging-based services and sidelink positioning as defined in TS 23.586 [25]. + +**RLC bearer:** RLC and MAC logical channel configuration of a radio bearer in one cell group. + +**Secondary Cell Group:** in MR-DC, a group of serving cells associated with the Secondary Node, comprising of the SpCell (PSCell) and optionally one or more SCells. + +**Secondary node:** in MR-DC, the radio access node, with no control plane connection to the core network, providing additional resources to the UE. It may be an en-gNB (in EN-DC), a Secondary ng-eNB (in NE-DC) or a Secondary gNB (in NR-DC and NGEN-DC). + +**SCG bearer:** in MR-DC, a radio bearer with an RLC bearer (or two RLC bearers, in case of CA packet duplication in an E-UTRAN cell group, or up to four RLC bearers in case of CA packet duplication in a NR cell group) only in the SCG. + +**SN terminated bearer:** in MR-DC, a radio bearer for which PDCP is located in the SN. + +**SpCell:** primary cell of a master or secondary cell group. + +**SRB3:** in EN-DC, NGEN-DC and NR-DC, a direct SRB between the SN and the UE. + +**SRB5:** in NR-DC, a direct SRB between the SN and the UE dedicated for sending application layer measurement report information. + +**Split bearer:** in MR-DC, a radio bearer with RLC bearers both in MCG and SCG. + +**Split PDU Session (or PDU Session split):** a PDU Session whose QoS Flows are served by more than one SDAP entities in the NG-RAN. + +**Split SRB:** in MR-DC, a SRB between the MN and the UE with RLC bearers both in MCG and SCG. + +**Subsequent Conditional PSCell Addition or Change (subsequent CPAC):** a conditional PSCell addition or change procedure that is executed after a PSCell addition, a PSCell change, a PCell change or an SCG release based on pre-configured subsequent CPAC configuration of candidate PSCell(s) without reconfiguration and re-initiation of CPC/CPA. + +**User plane resource configuration:** in MR-DC with 5GC, encompasses radio network resources and radio access resources related to either one or more PDU sessions, one or more QoS flows, one or more DRBs, or any combination thereof. + +**V2X sidelink communication:** AS functionality enabling V2X Communication as defined in TS 23.285 [19], between nearby UEs, using E-UTRA technology but not traversing any network node. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1], TS 36.300 [2] and TS 38.300 [3]. + +| | | +|---------|------------------------------------------------| +| BFD | Beam Failure Detection | +| CHO | Conditional Handover | +| CLI | Cross Link Interference | +| CPA | Conditional PSCell Addition | +| CPAC | Conditional PSCell Addition or Change | +| CPC | Conditional PSCell Change | +| DAPS | Dual Active Protocol Stack | +| DC | Intra-E-UTRA Dual Connectivity | +| DCP | DCI with CRC scrambled by PS-RNTI | +| EN-DC | E-UTRA-NR Dual Connectivity | +| IAB | Integrated Access and Backhaul | +| IDC | In-Device Coexistence | +| LTM | L1/L2 Triggered Mobility | +| MCG | Master Cell Group | +| MN | Master Node | +| MR-DC | Multi-Radio Dual Connectivity | +| MUSIM | Multi-Universal Subscriber Identity Module | +| NE-DC | NR-E-UTRA Dual Connectivity | +| NGEN-DC | NG-RAN E-UTRA-NR Dual Connectivity | +| NR-DC | NR-NR Dual Connectivity | +| QMC | QoE Measurement Collection | +| QoE | Quality of Experience | +| RLM | Radio Link Monitoring | +| SCG | Secondary Cell Group | +| SMTC | SS/PBCH block Measurement Timing Configuration | +| SN | Secondary Node | +| SPR | Successful PSCell change Report | +| V2X | Vehicle-to-Everything | + +# --- 4 Multi-Radio Dual Connectivity + +## 4.1 General + +### 4.1.1 Common MR-DC principles + +Multi-Radio Dual Connectivity (MR-DC) is a generalization of the Intra-E-UTRA Dual Connectivity (DC) described in TS 36.300 [2], where a multiple Rx/Tx capable UE may be configured to utilise resources provided by two different nodes connected via non-ideal backhaul, one providing NR access and the other one providing either E-UTRA or NR access. One node acts as the MN and the other as the SN. The MN and SN are connected via a network interface and at least the MN is connected to the core network. + +The MN and/or the SN can be operated with shared spectrum channel access. + +All functions specified for a UE may be used for an IAB-MT unless otherwise stated. Similar as specified for UE, the IAB-MT can access the network using either one network node or using two different nodes with EN-DC and NR-DC architectures. In EN-DC, the backhauling traffic over the E-UTRA radio interface is not supported. + +NOTE 1: MR-DC is designed based on the assumption of non-ideal backhaul between the different nodes but can also be used in case of ideal backhaul. + +NOTE 2: All MR-DC normative text and procedures in this version of the specification show the aggregated node case. The details about non-aggregated node for MR-DC operation are described in TS 38.401 [7]. + +### 4.1.2 MR-DC with the EPC + +E-UTRAN supports MR-DC via E-UTRA-NR Dual Connectivity (EN-DC), in which a UE is connected to one eNB that acts as a MN and one en-gNB that acts as a SN. The eNB is connected to the EPC via the S1 interface and to the en-gNB via the X2 interface. The en-gNB might also be connected to the EPC via the S1-U interface and other en-gNBs via the X2-U interface. + +The EN-DC architecture is illustrated in Figure 4.1.2-1 below. + +![Figure 4.1.2-1: EN-DC Overall Architecture. The diagram shows the network architecture for EN-DC. At the top, two MME/S-GW units are shown, collectively labeled as the EPC. Below them, the E-UTRAN layer contains four radio nodes: two en-gNBs and two eNBs. The left en-gNB is connected to the left MME/S-GW via an S1 interface and to the left eNB via an X2 interface. The right en-gNB is connected to the right MME/S-GW via an S1 interface and to the right eNB via an X2 interface. Both en-gNBs are also connected to both MME/S-GW units via S1-U interfaces. The two eNBs are connected to each other via an X2 interface. The right eNB is also connected to the left MME/S-GW via an S1 interface. The left eNB is connected to the right MME/S-GW via an S1-U interface. The right eNB is also connected to the left MME/S-GW via an X2-U interface.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +Figure 4.1.2-1: EN-DC Overall Architecture. The diagram shows the network architecture for EN-DC. At the top, two MME/S-GW units are shown, collectively labeled as the EPC. Below them, the E-UTRAN layer contains four radio nodes: two en-gNBs and two eNBs. The left en-gNB is connected to the left MME/S-GW via an S1 interface and to the left eNB via an X2 interface. The right en-gNB is connected to the right MME/S-GW via an S1 interface and to the right eNB via an X2 interface. Both en-gNBs are also connected to both MME/S-GW units via S1-U interfaces. The two eNBs are connected to each other via an X2 interface. The right eNB is also connected to the left MME/S-GW via an S1 interface. The left eNB is connected to the right MME/S-GW via an S1-U interface. The right eNB is also connected to the left MME/S-GW via an X2-U interface. + +Figure 4.1.2-1: EN-DC Overall Architecture + +### 4.1.3 MR-DC with the 5GC + +#### 4.1.3.1 E-UTRA-NR Dual Connectivity + +NG-RAN supports NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), in which a UE is connected to one ng-eNB that acts as a MN and one gNB that acts as a SN. + +#### 4.1.3.2 NR-E-UTRA Dual Connectivity + +NG-RAN supports NR-E-UTRA Dual Connectivity (NE-DC), in which a UE is connected to one gNB that acts as a MN and one ng-eNB that acts as a SN. + +#### 4.1.3.3 NR-NR Dual Connectivity + +NG-RAN supports NR-NR Dual Connectivity (NR-DC), in which a UE is connected to one gNB that acts as a MN and another gNB that acts as a SN. In addition, NR-DC can also be used when a UE is connected to a single gNB, acting both as a MN and as a SN, and configuring both MCG and SCG. + +## 4.2 Radio Protocol Architecture + +### 4.2.1 Control Plane + +In MR-DC, the UE has a single RRC state, based on the MN RRC and a single C-plane connection towards the Core Network. Figure 4.2.1-1 illustrates the Control plane architecture for MR-DC. Each radio node has its own RRC entity (E-UTRA version if the node is an eNB or NR version if the node is a gNB) which can generate RRC PDUs to be sent to the UE. + +RRC PDUs generated by the SN can be transported via the MN to the UE. The MN always sends the initial SN RRC configuration via MCG SRB (SRB1), but subsequent reconfigurations may be transported via MN or SN. When transporting RRC PDU from the SN, the MN does not modify the UE configuration provided by the SN. + +In E-UTRA connected to EPC, at initial connection establishment SRB1 uses E-UTRA PDCP. If the UE supports EN-DC, regardless whether EN-DC is configured or not, after initial connection establishment, MCG SRBs (SRB1 and SRB2) can be configured by the network to use either E-UTRA PDCP or NR PDCP (either SRB1 and SRB2 are both configured with E-UTRA PDCP, or they are both configured with NR PDCP). Change from E-UTRA PDCP to NR PDCP (or vice-versa) is supported via a handover procedure (reconfiguration with mobility) or, for the initial change of SRB1 from E-UTRA PDCP to NR PDCP, with a reconfiguration without mobility before the initial security activation. + +If the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC), the UE can be configured to establish a SRB with the SN (SRB3) to enable RRC PDUs for the SN to be sent directly between the UE and the SN. RRC PDUs for the SN can only be transported directly to the UE for SN RRC reconfiguration not requiring any coordination with the MN. Measurement reporting for mobility within the SN can be done directly from the UE to the SN if SRB3 is configured. + +In NR-DC, the UE can be configured to establish a SRB with the SN (SRB5) to enable RRC messages which include application layer measurement report information to be sent directly between the UE and the SN. The application measurement report can be sent directly from the UE to the SN if SRB5 is configured and indicated by the network for the application measurement reporting. + +Split SRB is supported for all MR-DC options, allowing duplication of RRC PDUs generated by the MN, via the direct path and via the SN. Split SRB uses NR PDCP. This version of the specification does not support the duplication of RRC PDUs generated by the SN via the MN and SN paths. + +In EN-DC, the SCG configuration is kept in the UE during suspension. During connection resumption, if the UE supports resuming with EN-DC, the UE can be configured to release, restore, or reconfigure the SCG configuration. Otherwise, the UE releases the SCG configuration (but not the radio bearer configuration) during resumption initiation. + +In MR-DC with 5GC, the UE stores the PDCP/SDAP configuration and the SCG configuration when moving to RRC Inactive. During connection resumption, if the UE supports resuming with MR-DC, the UE can be configured to release, restore, or reconfigure the SCG configuration. Otherwise, it releases the SCG configuration. + +![Figure 4.2.1-1: Control plane architecture for EN-DC (left) and MR-DC with 5GC (right).](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +The diagram illustrates two control plane architectures. The left side shows EN-DC architecture where a MeNB (Master node) is connected to an S1 interface and a UE. The MeNB contains an RRC component. The UE contains an RRC component in MeNB state. A secondary node (SgNB) is connected to the MeNB via an X2-C interface and to the UE via a Uu interface. The SgNB contains an NR RRC component. The right side shows MR-DC with 5GC architecture where a Master node is connected to an NG-C interface and a UE. The Master node contains an RRC component. The UE contains an RRC component in Master node state. A Secondary node is connected to the Master node via an Xn-C interface and to the UE via a Uu interface. The Secondary node contains an RRC component. + +Figure 4.2.1-1: Control plane architecture for EN-DC (left) and MR-DC with 5GC (right). + +Figure 4.2.1-1: Control plane architecture for EN-DC (left) and MR-DC with 5GC (right). + +### 4.2.2 User Plane + +In MR-DC, from a UE perspective, three bearer types exist: MCG bearer, SCG bearer and split bearer. These three bearer types are depicted in Figure 4.2.2-1 for MR-DC with EPC (EN-DC) and in Figure 4.2.2-2 for MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). + +In E-UTRA connected to EPC, if the UE supports EN-DC, regardless whether EN-DC is configured or not, the network can configure either E-UTRA PDCP or NR PDCP for MN terminated MCG bearers while NR PDCP is always used for all other bearers. Change from E-UTRA to NR PDCP or vice-versa can be performed via a reconfiguration procedure (with or without handover), either using release and add of the DRBs or using the full configuration option. + +In MR-DC with 5GC, NR PDCP is always used for all bearer types. In NGEN-DC, E-UTRA RLC/MAC is used in the MN while NR RLC/MAC is used in the SN. In NE-DC, NR RLC/MAC is used in the MN while E-UTRA RLC/MAC is used in the SN. In NR-DC, NR RLC/MAC is used in both MN and SN. + +![Figure 4.2.2-1: Radio Protocol Architecture for MCG, SCG and split bearers from a UE perspective in MR-DC with EPC (EN-DC).](cab0834804fb031b43865554cc8d06ab_img.jpg) + +This diagram illustrates the radio protocol architecture for MR-DC with EPC (EN-DC) from a UE perspective. It shows three bearer types: MCG Bearer, Split Bearer, and SCG Bearer. The MCG Bearer consists of E-UTRA/NR PDCP, E-UTRA RLC, and E-UTRA MAC. The Split Bearer consists of NR PDCP, E-UTRA RLC, and NR MAC. The SCG Bearer consists of NR PDCP, NR RLC, and NR MAC. All bearers are shown within a UE box, with arrows pointing from the bearer labels to their respective protocol stacks. + +Figure 4.2.2-1: Radio Protocol Architecture for MCG, SCG and split bearers from a UE perspective in MR-DC with EPC (EN-DC). + +**Figure 4.2.2-1: Radio Protocol Architecture for MCG, SCG and split bearers from a UE perspective in MR-DC with EPC (EN-DC)** + +![Figure 4.2.2-2: Radio Protocol Architecture for MCG, SCG and split bearers from a UE perspective in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC).](ddc7460821484f1ae2835c67955c554c_img.jpg) + +This diagram illustrates the radio protocol architecture for MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC) from a UE perspective. It shows three bearer types: MCG Bearer, Split Bearer, and SCG Bearer. All bearers start with SDAP at the top, followed by NR PDCP. The MCG Bearer then uses MN RLC and MN MAC. The Split Bearer uses SN RLC and SN MAC. The SCG Bearer uses SN RLC and SN MAC. All bearers are shown within a UE box, with arrows pointing from the bearer labels to their respective protocol stacks. + +Figure 4.2.2-2: Radio Protocol Architecture for MCG, SCG and split bearers from a UE perspective in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). + +**Figure 4.2.2-2: Radio Protocol Architecture for MCG, SCG and split bearers from a UE perspective in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC).** + +From a network perspective, each bearer (MCG, SCG and split bearer) can be terminated either in MN or in SN. Network side protocol termination options are shown in Figure 4.2.2-3 for MR-DC with EPC (EN-DC) and in Figure 4.2.2-4 for MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). + +NOTE 1: Even if only SCG bearers are configured for a UE, for SRB1 and SRB2 the logical channels are always configured at least in the MCG, i.e. this is still an MR-DC configuration and a PCell always exists. + +NOTE 2: If only MCG bearers are configured for a UE, i.e. there is no SCG, this is still considered an MR-DC configuration, as long as at least one of the bearers is terminated in the SN. + +![Figure 4.2.2-3: Network side protocol termination options for MCG, SCG and split bearers in MR-DC with EPC (EN-DC).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +This diagram illustrates the network side protocol termination options for MCG, SCG, and split bearers in MR-DC with EPC (EN-DC). It shows two main components: the Master Node (MN) and the Secondary Node (SN), connected by an X2 interface. + +- MN (Master Node):** Contains an E-UTRA MAC layer. Above it are two E-UTRA RLC layers. The top layer consists of three PDCP entities: E-UTRA/NR PDCP (for MCG Bearer), NR PDCP (for SCG Bearer), and another NR PDCP (for Split Bearer). The E-UTRA/NR PDCP connects to the first E-UTRA RLC. The SCG Bearer's NR PDCP connects to the second E-UTRA RLC. The Split Bearer's NR PDCP connects to both the second and third E-UTRA RLC layers. +- SN (Secondary Node):** Contains an NR MAC layer. Above it are four NR RLC layers. The top layer consists of three PDCP entities: NR PDCP (for Split Bearer), NR PDCP (for MCG Bearer), and NR PDCP (for SCG Bearer). The Split Bearer's NR PDCP connects to the first and second NR RLC layers. The MCG Bearer's NR PDCP connects to the third NR RLC layer. The SCG Bearer's NR PDCP connects to the fourth NR RLC layer. +- Interfaces:** The X2 interface connects the MN and SN. Arrows indicate the flow of data from the bearers down through the PDCP, RLC, and MAC layers. + +Figure 4.2.2-3: Network side protocol termination options for MCG, SCG and split bearers in MR-DC with EPC (EN-DC). + +Figure 4.2.2-3: Network side protocol termination options for MCG, SCG and split bearers in MR-DC with EPC (EN-DC). + +![Figure 4.2.2-4: Network side protocol termination options for MCG, SCG and split bearers in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC).](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +This diagram illustrates the network side protocol termination options for MCG, SCG, and split bearers in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). It shows two main components: the Master Node (MN) and the Secondary Node (SN), connected by an Xn interface. + +- MN (Master Node):** Contains an MN MAC layer. Above it are four MN RLC layers. The top layer consists of three NR PDCP entities: NR PDCP (for MCG Bearer), NR PDCP (for SCG Bearer), and NR PDCP (for Split Bearer). All three NR PDCP entities connect to the SDAP layer, which receives QoS Flows. The MCG Bearer's NR PDCP connects to the first MN RLC. The SCG Bearer's NR PDCP connects to the second MN RLC. The Split Bearer's NR PDCP connects to both the third and fourth MN RLC layers. +- SN (Secondary Node):** Contains an SN MAC layer. Above it are four SN RLC layers. The top layer consists of three NR PDCP entities: NR PDCP (for Split Bearer), NR PDCP (for MCG Bearer), and NR PDCP (for SCG Bearer). All three NR PDCP entities connect to the SDAP layer, which receives QoS Flows. The Split Bearer's NR PDCP connects to the first and second SN RLC layers. The MCG Bearer's NR PDCP connects to the third SN RLC layer. The SCG Bearer's NR PDCP connects to the fourth SN RLC layer. +- Interfaces:** The Xn interface connects the MN and SN. Arrows indicate the flow of data from the QoS Flows down through the SDAP, NR PDCP, RLC, and MAC layers. + +Figure 4.2.2-4: Network side protocol termination options for MCG, SCG and split bearers in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). + +Figure 4.2.2-4: Network side protocol termination options for MCG, SCG and split bearers in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). + +## 4.3 Network interfaces + +### 4.3.1 Control Plane + +#### 4.3.1.1 Common MR-DC principles + +In MR-DC, there is an interface between the MN and the SN for control plane signalling and coordination. For each MR-DC UE, there is also one control plane connection between the MN and a corresponding CN entity. The MN and + +the SN involved in MR-DC for a certain UE control their radio resources and are primarily responsible for allocating radio resources of their cells. + +Figure 4.3.1.1-1 shows C-plane connectivity of MN and SN involved in MR-DC for a certain UE. + +![Figure 4.3.1.1-1: C-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right).](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +The diagram illustrates two network architectures for C-plane connectivity. On the left, representing EN-DC, an MME (Mobility Management Entity) is connected to a MeNB (Master eNodeB) via an S1-MME interface (green dashed line). The MeNB is connected to an en-gNB (secondary node) via an X2-C interface (red dashed line). On the right, representing MR-DC with 5GC, an AMF (Access and Management Function) is connected to an MN (Master Node) via an NG-C interface (green dashed line). The MN is connected to an SN (Secondary Node) via an Xn-C interface (red dashed line). Both architectures show the core network entity (MME or AMF) connected to the Master Node, which in turn is connected to the Secondary Node. + +Figure 4.3.1.1-1: C-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right). + +**Figure 4.3.1.1-1: C-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right).** + +#### 4.3.1.2 MR-DC with EPC + +In MR-DC with EPC (EN-DC), the involved core network entity is the MME. S1-MME is terminated in MN and the MN and the SN are interconnected via X2-C. + +#### 4.3.1.3 MR-DC with 5GC + +In MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC), the involved core network entity is the AMF. NG-C is terminated in the MN and the MN and the SN are interconnected via Xn-C. + +### 4.3.2 User Plane + +#### 4.3.2.1 Common MR-DC principles + +There are different U-plane connectivity options of the MN and SN involved in MR-DC for a certain UE, as shown in Figure 4.3.2.1-1. The U-plane connectivity depends on the bearer option configured: + +- For *MN terminated bearers*, the user plane connection to the CN entity is terminated in the MN; +- For *SN terminated bearers*, the user plane connection to the CN entity is terminated in the SN; +- The transport of user plane data over the Uu either involves MCG or SCG radio resources or both: + - For *MCG bearers*, only MCG radio resources are involved; + - For *SCG bearers*, only SCG radio resources are involved; + - For *split bearers*, both MCG and SCG radio resources are involved. +- For split bearers, *MN terminated SCG bearers* and *SN terminated MCG bearers*, PDCP data is transferred between the MN and the SN via the MN-SN user plane interface. + +![Figure 4.3.2.1-1: U-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right).](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates two network architectures for U-plane connectivity. On the left, for EN-DC, an S-GW is connected to a MeNB via an S1-U interface (blue line). The MeNB is connected to an en-gNB via an X2-U interface (red line). The S-GW is also connected to the en-gNB via an S1-U interface (blue line). On the right, for MR-DC with 5GC, a UPF is connected to an MN via an NG-U interface (blue line). The MN is connected to an SN via an Xn-U interface (red line). The UPF is also connected to the SN via an NG-U interface (blue line). + +Figure 4.3.2.1-1: U-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right). + +**Figure 4.3.2.1-1: U-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right).** + +#### 4.3.2.2 MR-DC with EPC + +For MR-DC with EPC (EN-DC), X2-U interface is the user plane interface between MN and SN, and S1-U is the user plane interface between the MN, the SN or both and the S-GW. + +#### 4.3.2.3 MR-DC with 5GC + +For MR-DC with 5GC (NGEN-DC, NE-DC and inter-gNB NR-DC), Xn-U interface is the user plane interface between MN and SN, and NG-U is the user plane interface between the MN, the SN or both and the UPF. + +# 5 Layer 1 related aspects + +In MR-DC, two or more Component Carriers (CCs) may be aggregated over two cell groups. A UE may simultaneously receive or transmit on multiple CCs depending on its capabilities. The maximum number of configured CCs for a UE is 32 for DL and UL. Depending on UE's capabilities, up to 31 CCs can be configured for an E-UTRA cell group when the NR cell group is configured. For the NR cell group, the maximum number of configured CCs for a UE is 16 for DL and 16 for UL. + +A gNB may configure the same Physical Cell ID (PCI) to more than one NR cell it serves. To avoid PCI confusion for MR-DC, NR PCIs should be allocated in a way that an NR cell is uniquely identifiable by a PCell identifier. This PCell is in the coverage area of an NR cell included in the MR-DC operation. In addition, NR PCIs should only be re-used in NR cells on the same SSB frequency sufficiently distant from each other. X2-C/Xn-C signalling supports disambiguation of NR PCIs by including the CGI of the PCell in respective X2AP/XnAP messages (e.g. SGNB ADDITION REQUEST/S-NODE ADDITION REQUEST) and by providing neighbour cell relationship via non-UE associated signaling (e.g. via the Xn Setup procedure or the NG-RAN node Configuration Update procedure). + +NR-DC supports the case of no synchronization between PCell and PSCell. However, some UEs may support NR-DC only if slot-level synchronization between PCell and PSCell is ensured. + +In MR-DC, power sharing can be performed within a frequency range with either semi-static or dynamic power sharing. With semi-static power sharing, the maximum UE transmission power is semi-statically split between MCG and SCG by RRC configuration. With dynamic power sharing: + +- when determining the UL transmission power of an SCG transmission in (NG)EN-DC or in NR-DC, the UE takes into account transmission(s) on MCG overlapping with any part of the SCG transmission; +- when determining the UL transmission power of an MCG transmission in NE-DC, the UE takes into account transmission(s) on SCG overlapping with any part of the MCG transmission. + +Details are specified in TS38.213[21]. + +In EN-DC, a UE configured with uplink Tx switching can have Tx dynamically switched between E-UTRA uplink carrier and NR uplink carrier for enabling 2Tx UL transmission on NR carrier. + +# 6 Layer 2 related aspects + +## 6.1 MAC Sublayer + +In MR-DC, the UE is configured with two MAC entities: one MAC entity for the MCG and one MAC entity for the SCG. The serving cells other than the PCell can be activated/deactivated by RRC or MAC Control Element. For activation/deactivation by MAC Control Element, the serving cells of the MCG other than the PCell can only be activated/deactivated by the MAC Control Element received on MCG, and the serving cells of the SCG other than PSCell can only be activated/ deactivated by the MAC Control Element received on SCG. The MAC entity applies the bitmap for the associated cells of either MCG or SCG. When the SCG is not deactivated, the PSCell is always activated like the PCell (i.e. deactivation timer is not applied to PSCell). With the exception of PUCCH SCell, one deactivation timer is configured per SCell by RRC. + +In MR-DC, semi-persistent scheduling (SPS) resources and configured grant (CG) resources can be configured on serving cells in both MCG and SCG. + +In MR-DC, for 4-step RA type, contention based random access (CBRA) procedure is supported on both PCell and PSCell while contention free random access (CFRA) procedure is supported on all serving cells in both MCG and SCG. For 2-step RA type, CBRA can be supported on the PCell, if the MN is a gNB (i.e. for NE-DC and NR-DC) and on the PSCell, if the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC) while CFRA is only supported on the PCell, if the MN is a gNB (i.e. for NE-DC and NR-DC). + +In (NG)EN-DC and NR-DC, when SCG is deactivated as described in clause 7.13, the TA timer associated with SCG continues running, the UE considers the TA is valid as long as TA timer is running. In case of SCG activation, the UE can be instructed by the network to perform random access towards PSCell even if the TA timer associated with PSCell is running and RLF and beam failure are not declared. Besides, the UE can be instructed by the network to perform SCG activation without performing random access, if the TA timer associated with PSCell is running and RLM and beam failure detection are configured but RLF or beam failure is not declared. In case of network-initiated SCG activation, both CBRA and CFRA on PSCell are supported. For CFRA, the dedicated RACH resources can be provided in the RRC message used to activate SCG. + +In MR-DC, the BSR configuration, triggering and reporting are independently performed per cell group. For split bearers, the PDCP data is considered in BSR in the cell group(s) configured by RRC. + +In MR-DC, separate DRX configurations are provided for MCG and SCG. A secondary DRX group can be configured in MR-DC for a cell group that includes cells in different Frequency Ranges as specified in TS 38.331 [4]. + +In MR-DC, PHR is independently configured per cell group. Events in one cell group can trigger power headroom reporting in both MCG and SCG. Power headroom information for one cell group is also included in a PHR transmitted in the other cell group. While the SCG is deactivated, PHR for SCG is not reported. + +In MR-DC, consistent LBT failure recovery procedure as described in clause 5.6.1 in TS 38.300 [3] can be configured for both MAC entities of MCG and/or SCG when operating with shared spectrum channel access. + +In MR-DC, for power saving purpose, the UE can be configured with DCP to be monitored on the PCell, if the MN is a gNB (i.e. for NE-DC and NR-DC) and/or with DCP to be monitored on the PSCell, if the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC). + +In MR-DC, the UE may be configured with enhanced intra-UE overlapping resources prioritization on MN, if the MN is a gNB (i.e. for NE-DC and NR-DC) and on SN, if the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC). + +## 6.2 RLC Sublayer + +Both RLC AM and UM can be configured for MR-DC, for all bearer types (MCG, SCG and split bearers). + +## 6.3 PDCP Sublayer + +In EN-DC, CA duplication (see [3]) can be applied in the MN and in the SN, but MCG bearer CA duplication can be configured only in combination with E-UTRAN PDCP and MCG bearer CA duplication can be configured only if DC duplication is not configured for any split bearer. + +In NGEN-DC, CA duplication can only be configured for SCG bearer. In NE-DC, CA duplication can only be configured for MCG bearer. In NR-DC, CA duplication can be configured for both MCG and SCG bearers, and can be configured together with DC duplication. + +In MR-DC, RoHC and EHC (as described in TS 36.323 [15] and TS 38.323 [16]) can be configured for all the bearer types. In MR-DC with 5GC, UDC (as described in TS 38.323 [16]) can be configured for all the bearer types. + +## 6.4 SDAP Sublayer + +In MR-DC with 5GC, the network may host up to two SDAP protocol entities for each individual PDU session, one for MN and another one for SN (see clause 8.1). The UE is configured with one SDAP protocol entity per PDU session. + +## 6.5 BAP Sublayer + +In EN-DC and NR-DC, IAB-node and IAB-donor-DU can be configured with BAP sublayer for backhaul traffic (as described in TS 38.300 [3] and TS 38.340 [17]). In EN-DC, the BAP sublayer routes the backhaul traffic via only the NR interface. In NR-DC, the BAP sublayer can route the backhaul traffic via the two NR interfaces to the same IAB-donor. + +# --- 7 RRC related aspects + +## 7.1 System information handling + +In MR-DC, the SN is not required to broadcast system information other than for radio frame timing and SFN. System information for initial configuration is provided to the UE by dedicated RRC signalling via the MN. The UE acquires, at least, radio frame timing and SFN of SCG from the PSS/SSS and MIB (if the SN is an eNB) / NR-PSS/SSS and PBCH (if the SN is a gNB) of the PSCell. In EN-DC, SN may broadcast system information to allow only IAB-MT to access the SN. + +NOTE: The option that the SN does not broadcast system information other than radio frame timing and SFN relies on proper OAM configuration. + +Additionally, upon change of the relevant system information of a configured SCell, the network releases and subsequently adds the concerned SCell (with updated system information), via one or more *RRC reconfiguration* messages sent on SRB1 or SRB3, if configured. + +## 7.2 Measurements + +If the measurement is configured to the UE in preparation for the Secondary Node Addition procedure described in clause 10.2, the Master node should configure the measurement to the UE. + +In case of the intra-secondary node mobility described in clause 10.3, the SN should configure the measurement to the UE in coordination with the MN, if required. + +The Secondary Node Change procedure described in clause 10.5 can be triggered by both the MN (only for inter-frequency secondary node change) and the SN. For secondary node changes triggered by the SN, the RRM measurement configuration is maintained by the SN which also processes the measurement reporting, without providing the measurement results to the MN. + +Measurements can be configured independently by the MN and by the SN (intra-RAT measurements on serving and non-serving frequencies). The MN indicates the maximum number of frequency layers and measurement identities of intra-frequency and inter-frequency measurement that can be used in the SN to ensure that UE capabilities are not exceeded. In MR-DC, to assist MN to identify the measurement type, the SN indicates to the MN the list of SCG serving frequencies. In NR-DC, to assist SN to identify the measurement type, the MN indicates also to SN the list of MCG serving frequencies. The SN can also request the MN for new maximum values of the number of measurement identities that it can configure, and it is up to the MN whether to accommodate the SN request, based on the capability coordination principles as described in 7.3. If the SN receives from the MN a new value for the maximum number of + +measurement identities, is SN responsibility to ensure that its configured measurement identities to comply with the new limit. + +If MN and SN both configure measurements on the same carrier frequency then the configurations need to be consistent (if the network wants to ensure these are considered as a single measurement layer). Each node (MN and SN) can configure independently a threshold for the SpCell quality. In (NG)EN-DC scenario, when the PCell quality is above the threshold configured by the MN, the UE is still required to perform inter-RAT measurements configured by the MN on the SN RAT (while it's not required to perform intra-RAT measurements); when the PSCell quality is above the threshold configured by the SN, the UE is not required to perform measurements configured by the SN. In NR-DC or NE-DC scenario, when the PCell quality is above the threshold configured by the MN, the UE is not required to perform measurements configured by the MN; when the PSCell quality is above the threshold configured by the SN, the UE is not required to perform measurements configured by the SN. + +NOTE: The SN cannot renegotiate the number of frequency layers allocated by the MN in this version of the protocol. + +In MR-DC, both the MN and the SN can configure CGI reporting. The MN can configure CGI reporting for intra-RAT and inter-RAT cells but the SN can only configure CGI reporting of intra-RAT cells. At any point in time, the UE can be configured with at most one CGI reporting configuration. For CGI reporting coordination, the SN sends the CGI measurement request and the embedded CGI reporting configuration to the MN. Optionally, the SN sends the unknown cell information to the MN. If there is no ongoing CGI reporting measurement on UE side, the MN forwards the SN CGI measurement configuration to UE. Otherwise the MN rejects the request by sending X2/Xn reject message. In case the SN indicates the unknown cell information, and the CGI information of the requested cell is already available in the MN, the MN can also reject the request, and sends the CGI information of the requested cell to the SN. The SN cannot configure the CGI measurement using the SRB3. + +Both MN-configured and SN-configured RRM measurements are supported while the SCG is deactivated. The PSCell measurement cycle when in deactivated SCG state is configured by RRC. + +When SRB3 is not configured or the SCG is deactivated, reports for measurements configured by the SN are sent on SRB1. When SRB3 is configured and SCG transmission of radio bearers is not suspended and the SCG is not deactivated, reports for measurements configured by the SN are sent on SRB3. + +Measurement results related to the target SN can be provided by MN to target SN at MN initiated SN change procedure. Measurement results of target SN can be forwarded from source SN to target SN via MN at SN initiated SN change procedure. Measurement results related to the target SN can be provided by source MN to target MN at Inter-MN handover with/without SN change procedure. + +Measurement results according to measurement configuration from the MN are encoded according to SN RRC when they are provided by MN to SN in *SgNB Addition Request* message / *SN Addition Request* message. During SN initiated SN change procedure, measurement results according to measurement configuration from SN are encoded according to SN RRC when they are provided by MN to SN in *SgNB Addition Request* message / *SN Addition Request* message. + +Per-UE or per-FR measurement gaps can be configured, depending on UE capability to support independent FR measurement and network preference. Per-UE gap applies to both FR1 (E-UTRA, UTRA-FDD and NR) and FR2 (NR) frequencies. For per-FR gap, two independent gap patterns (i.e. FR1 gap and FR2 gap) are configured for FR1 and FR2 respectively. The UE may also be configured with a per-UE gap sharing configuration (applying to per-UE gap) or with two separate gap sharing configurations (applying to FR1 and FR2 measurement gaps respectively) [8]. + +A measurement gap configuration is always provided: + +- In EN-DC, NGEN-DC and NE-DC, for UEs configured with E-UTRA inter-frequency measurements as described in table 9.1.2-2 in TS 38.133 [8]; +- In EN-DC and NGEN-DC, for UEs configured with UTRAN and GERAN measurements as described in table 9.1.2-2 in TS 38.133 [8]; +- In NR-DC, for UEs configured with E-UTRAN measurements as described in table 9.1.2-3 in TS 38.133 [8]; +- In NR-DC, NE-DC, for UEs configured with UTRAN measurements as described in table 9.4.6.3-1 and 9.4.6.3-2 in TS 38.133 [8]; +- In MR-DC, for UEs that support either per-UE or per-FR gaps, when the conditions to measure SSB based inter-frequency measurement or SSB based intra-frequency measurement as described in clause 9.2.4 in TS 38.300 [3] are met; + +If per-UE gap is used, the MN decides the gap pattern and the related gap sharing configuration. If per-FR gap is used, in EN-DC and NGEN-DC, the MN decides the FR1 gap pattern and the related gap sharing configuration for FR1, while the SN decides the FR2 gap pattern and the related gap sharing configuration for FR2; in NE-DC and NR-DC, the MN decides both the FR1 and FR2 gap patterns and the related gap sharing configurations. + +In EN-DC and NGEN-DC, the measurement gap configuration from the MN to the UE indicates if the configuration from the MN is a per-UE gap or an FR1 gap configuration. The MN also indicates the configured per-UE or FR1 measurement gap pattern and the gap purpose (per-UE or per-FR1) to the SN. Measurement gap configuration assistance information can be exchanged between the MN and the SN. For the case of per-UE gap, the SN indicates to the MN the list of SN configured frequencies in FR1 and FR2 measured by the UE. For the per-FR gap case, the SN indicates to the MN the list of SN configured frequencies in FR1 measured by the UE and the MN indicates to the SN the list of MN configured frequencies in FR2 measured by the UE. + +In NE-DC, the MN indicates the configured per-UE or FR1 measurement gap pattern to the SN. The SN can provide a gap request to the MN, without indicating any list of frequencies. + +In NR-DC, the MN indicates the configured per-UE, FR1 or FR2 measurement gap pattern and the gap purpose to the SN. The SN can indicate to the MN the list of SN configured frequencies in FR1 and FR2 measured by the UE. + +In (NG)EN-DC and NR-DC, SMTC can be used for PSCell addition/PSCell change to assist the UE in finding the SSB in the target PSCell. In case the SMTC of the target PSCell is provided by both MN and SN it is up to UE implementation which one to use. + +CLI measurements can be configured for NR cells in all MR-DC options. In EN-DC and NGEN-DC, only the SN can configure CLI measurements. In NE-DC, only the MN can configure CLI measurements. In NR-DC, both the MN and the SN can configure CLI measurements, and the MN informs the SN about the maximum number of CLI measurement resources that can be configured by the SN to ensure that the total number of CLI measurement resources does not exceed the UE capabilities. + +For MUSIM operation, when the UE is configured to operate in NR-DC in Network A (as described in TS 38.300 [3]), the MN indicates the per-UE MUSIM gap configuration to the SN. + +## 7.3 UE capability coordination + +In (NG)EN-DC and NE-DC, the capabilities of a UE supporting MR-DC are carried by different capability containers. Some MR-DC related capabilities are in the MR-DC container e.g. MR-DC band combinations, while other MR-DC related capabilities are contained in the E-UTRA and NR capability containers e.g. feature sets as described in TS 38.300 [3]. The MR-DC capabilities in the MR-DC container need to be visible to both MN and SN, while the capabilities in the E-UTRA and NR containers only need to be visible to the node of the concerned RAT. + +In NR-DC, all NR-DC related capabilities are in the NR capability container and are visible to both MN and SN. + +When retrieving MR-DC related capabilities, the MN shall provide an MR-DC filter that affects the MR-DC related capabilities in MR-DC, E-UTRA and NR capability containers. When using different *UE capability enquiry* messages to retrieve the different containers, the MN shall employ the same MR-DC filter in all enquiry messages. In the E-UTRA RRC UE capability enquiry, the MR-DC filter is also used for retrieval of NR capabilities i.e. there is in fact one MR-DC/NR filter (while there is a separate filter for E-UTRA capabilities). Furthermore, the MN stores the retrieved capabilities and the corresponding filter, used to retrieve those capabilities, in the core network for later use. + +For the UE capabilities requiring coordination between E-UTRA and NR (i.e. band combinations, feature sets and the maximum power for FR1 the UE can use in SCG) or between NR MN and NR SN (i.e. band combinations, feature sets and the maximum power for FR1 and FR2), it is up to the MN to decide on how to resolve the dependency between MN and SN configurations. The MN then provides the resulting UE capabilities usable for SCG configuration to the SN, including the list of allowed MR-DC band combinations and feature sets, and the SN indicates the selected band combination and feature set to the MN. When subsequently reconfiguring the SCG, the SN should inform the MN whenever the band combination and/or feature set is selected for the SCG changes (i.e. even if the selection concerns a band combination and feature set that is allowed). As part of an SN initiated SN modification, the SN may also indicate the desired UE capabilities usable for SCG configuration (e.g. a band combination and a feature set) outside those allowed by the MN (i.e. it may re-negotiate the UE capabilities for SCG configuration), and it is up to the MN to make the final decision whether to accept or reject the request. If the MN accepts the request, the MN may provide the resulting UE capabilities e.g. by indicating the allowed band combinations and feature sets. If MN accepts but does not provide resulting UE capabilities, SN assumes the UE capabilities usable for SCG configuration are updated in accordance with the modification it requested. Otherwise, the MN rejects the request by sending X2/Xn refuse message. + +In EN-DC and MR-DC with 5GC, the MN may provide the UE radio capability ID to the SN. For EN-DC, the SN may retrieve the UE Radio Capability information associated to a UE radio capability ID from the MN. For MR-DC with 5GC, the SN may retrieve the UE radio capability information associated to a UE radio capability ID from the 5GC. + +For MUSIM operation, when the UE is configured to operate in NR-DC in Network A (as described in TS 38.300 [3]), the MN may indicate the temporary capability restriction to the SN based on the temporary capability restrictions indicated by the UE. + +## 7.4 Handling of combined MN/SN RRC messages + +When both MCG and SCG reconfiguration is required due to the need for coordination with the MN, the *SN RRC reconfiguration* message is encapsulated in an MN RRC message that also carries the corresponding MCG reconfiguration that ensures that the combined configuration can be jointly processed by the UE. If the MN terminates a bearer using NR PDCP, the NR PDCP configuration is generated by the MN itself. If the SN terminates the bearer, the SN generates the NR PDCP configuration and sends it to the MN as a separate container. + +The UE uses a joint success/failure procedure for messages in an encapsulating MN RRC message. A failure of the MN RRC messages, including one encapsulated SN RRC message with or without any MCG reconfiguration fields, triggers a re-establishment procedure. Each *SN RRC reconfiguration* message should have its own RRC response message even when the SN RRC message is encapsulated in an MN RRC message. The SN RRC response message is forwarded over X2/Xn to the SN. If a *SN RRC reconfiguration* message is contained in a MN RRC message, the UE sends a MN RRC response message that encapsulates the SN RRC response message. + +NOTE: If the MN RRC message does not encapsulate an *SN RRC reconfiguration* message (i.e. an SCG configuration) but only information elements generated by the SN (e.g. the PDCP configuration for an SN terminated bearer), the UE will not send an SN RRC response message. + +## 7.5 SRB3 + +SRB3 is supported in EN-DC, NGEN-DC and NR-DC, but not in NE-DC. + +The decision to establish SRB3 is taken by the SN, which provides the SRB3 configuration using an SN RRC message. SRB3 establishment and release can be done at Secondary Node Addition and Secondary Node Change. SRB3 reconfiguration can be done at Secondary Node Modification procedure. + +SRB3 may be used to send *SN RRC Reconfiguration*, *SN RRC Reconfiguration Complete*, *SN Measurement Report*, *SN Failure Information* (i.e., in case of failure for an SCG RLC bearer), *SN UE Assistance Information* message and *SN IABOtherInformation*, only in procedures where the MN is not involved. *SN RRC Reconfiguration Complete* messages are mapped to the same SRB as the message initiating the procedure. *SN Measurement Report* messages are mapped to SRB3, if configured, regardless of whether the configuration is received directly from the SN or via the MN. No MN RRC messages are mapped to SRB3. + +If split SRB1 is not configured, SRB3 may be used by the UE to transmit to the MN an encapsulated *MCG Failure Information* message in the *ULInformationTransferMRDC* message and receive in response an encapsulated *RRC reconfiguration* message, *MobilityFromNRCommand* message, *MobilityFromEUTRACommand* message or *RRC release* message in the *DLInformationTransferMRDC* message. + +SRB3 is modelled as one of the SRBs defined in TS 38.331 [4] and uses the NR-DCCH logical channel type. RRC PDUs on SRB3 are ciphered and integrity protected using NR PDCP, with security keys derived from $S-K_{gNB}$ . The SN selects ciphering and integrity protection algorithms for the SRB3 and provides them to the MN within the SCG Configuration for transmission to the UE. + +NOTE: A NR SCG RRC message sent via E-UTRA MCG SRB is protected by E-UTRA MCG SRB security (NR security is not used in this case). + +SRB3 is of higher scheduling priority than all DRBs. The default scheduling priorities of split SRB1 and SRB3 are the same. + +There is no requirement on the UE to perform any reordering of RRC messages between SRB1 and SRB3. + +When SCG is released, SRB3 is released. + +## 7.6 Split SRB + +Split SRB is supported for both SRB1 and SRB2 (split SRB is not supported for SRB0, SRB3, SRB4 and SRB5) in all MR-DC cases. RRC PDUs on split SRB are ciphered and integrity protected using NR PDCP. + +Split SRB can be configured by the MN in Secondary Node Addition and/or Modification procedure, with SN configuration part provided by the SN. A UE can be configured with both split SRB and SRB3 simultaneously. SRB3 and the SCG leg of split SRB can be independently configured. + +For the split SRB, the selection of transmission path in downlink depends on network implementation. For uplink, the UE is configured via MN RRC signalling whether to use MCG path or duplicate the transmission on both MCG and SCG. + +## 7.7 SCG/MCG failure handling + +RLF is declared separately for the MCG and for the SCG. + +If radio link failure is detected for MCG, fast MCG link recovery is configured and the SCG is not deactivated, the UE triggers fast MCG link recovery. Otherwise, the UE initiates the RRC connection re-establishment procedure. During the execution of PSCell addition or PSCell change, if radio link failure is detected for MCG, the UE initiates the RRC connection re-establishment procedure. + +During fast MCG link recovery, the UE suspends MCG transmissions for all radio bearers, except SRB0, and, if any, BH RLC channels and reports the failure with *MCGFailureInformation* message to the MN via the SCG, using the SCG leg of split SRB1 or SRB3. + +The UE includes in the *MCGFailureInformation* message the measurement results available according to current measurement configuration of both the MN and the SN. Once the fast MCG link recovery is triggered, the UE maintains the current measurement configurations from both the MN and the SN, and continues measurements based on configuration from the MN and the SN, if possible. The UE initiates the RRC connection re-establishment procedure if it does not receive an *RRCConnectionReconfiguration* message, *RRCReconfiguration* message, *MobilityFromNRCommand* message, *MobilityFromEUTRACommand* message, *RRCConnectionRelease* message or *RRCRelease* message within a certain time after fast MCG link recovery was initiated. + +Upon reception of the *MCGFailureInformation* message, the MN can send *RRCConnectionReconfiguration* message, *RRCReconfiguration* message, *MobilityFromNRCommand* message, *MobilityFromEUTRACommand* message, *RRCConnectionRelease* message or *RRCRelease* message to the UE, using the SCG leg of split SRB1 or SRB3. Upon receiving an *RRCConnectionReconfiguration* message, *RRCReconfiguration* message, *MobilityFromNRCommand* message or *MobilityFromEUTRACommand* message, the UE resumes MCG transmissions for all radio bearers. Upon receiving an *RRCConnectionRelease* message or *RRCRelease* message, the UE releases all the radio bearers and configurations. + +NOTE 1: It is up to network implementation to guarantee that the RRC-related messages are delivered to the UE by the SN before the release of its control plane resources. + +The following SCG failure cases are supported: + +- SCG RLF; +- SCG beam failure while the SCG is deactivated; +- SN addition/change failure; +- For EN-DC, NGEN-DC and NR-DC, SCG configuration failure or CPC configuration failure (only for messages on SRB3); +- For EN-DC, NGEN-DC and NR-DC, SCG RRC integrity check failure (on SRB3); +- For EN-DC, NGEN-DC and NR-DC, consistent UL LBT failure on PSCell; +- For IAB-MT, reception of a BH RLF indication from SCG; +- CPA/CPC or subsequent CPAC execution failure; + +- SCG LTM cell switch failure. + +Upon SCG failure, if MCG transmissions of radio bearers are not suspended, the UE suspends SCG transmissions for all radio bearers and, if any, BH RLC channels, if the SCG failure is not triggered by SCG beam failure, and reports the *SCGFailureInformation* to the MN, instead of triggering re-establishment. If SCG failure is detected while MCG transmissions for all radio bearers are suspended, the UE initiates the RRC connection re-establishment procedure. + +SCG/MCG failure handling by UE also applies to IAB MT. + +In all SCG failure cases, the UE maintains the current measurement configurations from both the MN and the SN and the UE continues measurements based on configuration from the MN and the SN if possible. The SN measurements configured to be routed via the MN will continue to be reported after the SCG failure. + +NOTE 2: UE may not continue measurements based on configuration from the SN after SCG failure in certain cases (e.g. UE cannot maintain the timing of PSCell). + +The UE includes in the *SCGFailureInformation* message the measurement results available according to current measurement configuration of both the MN and the SN. The MN handles the *SCGFailureInformation* message and may decide to keep, change, or release the SN/SCG. In all the cases, the measurement results according to the SN configuration and the SCG failure type may be forwarded to the old SN and/or to the new SN. + +In case of CPA/CPC, upon transmission of the *SCGFailureInformation* message to the MN, the UE stops evaluating the CPA/CPC execution condition. In case of subsequent CPAC, upon transmission of the *SCGFailureInformation* message to the MN or upon transmission of the *MCGFailureInformation* message to the SN, the UE stops evaluating the subsequent CPAC execution condition. The UE is not required to continue measurements for candidate PSCell(s) for execution condition upon transmission of the *SCGFailureInformation* message to the MN. + +## 7.8 UE identities + +In MR-DC, two C-RNTIs are independently allocated to the UE: one for MCG, and one for SCG. + +## 7.9 Inter-node Resource Coordination + +For MR-DC operations, MN and SN may coordinate their UL and DL radio resources in semi-static manner via UE associated signalling. The MN may coordinate its sidelink radio resources with the SN using the same UE associated signalling. + +In EN-DC, CSI-RS based SgNB change between neighbour en-gNBs is supported by enabling that neighbour en-gNBs can exchange their own CSI-RS configurations and on/off status via the MeNB. + +In NGEN-DC and NR-DC, CSI-RS based SN change between neighbour gNBs is supported by enabling that neighbour gNBs can exchange their own CSI-RS configurations and on/off status via the MN. + +## 7.10 UE assistance information + +In MR-DC, the UE can be configured to report MCG specific UE assistance information if the MN is a gNB and/or SCG specific UE assistance information if the SN is a gNB, if it prefers an adjustment on the connected mode DRX parameters, the maximum aggregated bandwidth, the maximum number of secondary component carriers, the maximum number of MIMO layers, whether the UE prefers the SCG to be deactivated, the minimum scheduling offset for cross-slot scheduling cycle length, whether the UE is applying RLM/BFD measurements relaxation for power saving, and/or whether the UE is experiencing IDC problems as described in TS 36.300 [2] and TS 38.300 [3]. In these cases, it is up to the network whether to accommodate the preference or how to use the relaxation status indications or how to solve the IDC problems. SCG specific UE assistance information for power saving or IDC can be configured by the network via SRB1 or SRB3. SCG specific UE assistance information for power saving or IDC is directly transmitted to the SN via SRB3, if SRB3 is configured and the SCG is activated, otherwise UE transmits SCG specific UE assistance information for power saving or IDC in a transparent container to the MN. When network simultaneously configures the UE to perform radio link monitoring on the SCG and beam failure detection on the SCG while the SCG is deactivated, UE assistance information for the relaxation state report of RLM/BFD measurements for SCG is reported over MCG. UE can implicitly indicate a preference for NR SCG release by indicating zero number of carriers and zero aggregated maximum bandwidth in both FR1 and FR2. + +## 7.11 F1-C transfer over E-UTRA + +In EN-DC, the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet can be transferred between IAB-donor and IAB-node via E-UTRA, if configured by IAB-donor, as specified in TS 38.331 [4]. When both E-UTRA and NR are configured to transfer the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet, it is up to the IAB implementation when to select the E-UTRA. SRB2 is used for transporting the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet between IAB-MT and MN [10], and the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet is transferred as a container via X2-AP between MN and SN, see TS 36.423 [9]. + +## 7.12 F1-C transfer in NR-DC + +In NR-DC, the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet can be transferred via BAP sublayer or via SRB between the IAB-node and F1-terminating IAB-donor (as specified in TS 38.401 [7]), as specified in TS 38.331 [4]. When both MCG and SCG are configured to transfer the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet, it is up to the IAB-node implementation for path selection. Two scenarios are supported, as shown in Figure 7.12-1. + +![Figure 7.12-1: F1-C transfer in NR-DC. The diagram shows two scenarios for F1-C transfer. Scenario 1 (a) shows an M-NG-RAN node connected to an IAB-donor via an Xn interface. The IAB-donor is connected to an IAB-node via a backhaul (BH) RLC channel. The IAB-node is connected to another IAB-node via another BH RLC channel. The F1-C traffic is shown as a blue line from the IAB-node to the IAB-donor, and the F1-U traffic is shown as a red line from the IAB-donor to the IAB-node. Scenario 2 (b) shows an S-NG-RAN node connected to an IAB-donor via an Xn interface. The IAB-donor is connected to an IAB-node via a backhaul (BH) RLC channel. The IAB-node is connected to another IAB-node via another BH RLC channel. The F1-C traffic is shown as a blue line from the IAB-node to the IAB-donor, and the F1-U traffic is shown as a red line from the IAB-donor to the IAB-node.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +Figure 7.12-1: F1-C transfer in NR-DC. The diagram shows two scenarios for F1-C transfer. Scenario 1 (a) shows an M-NG-RAN node connected to an IAB-donor via an Xn interface. The IAB-donor is connected to an IAB-node via a backhaul (BH) RLC channel. The IAB-node is connected to another IAB-node via another BH RLC channel. The F1-C traffic is shown as a blue line from the IAB-node to the IAB-donor, and the F1-U traffic is shown as a red line from the IAB-donor to the IAB-node. Scenario 2 (b) shows an S-NG-RAN node connected to an IAB-donor via an Xn interface. The IAB-donor is connected to an IAB-node via a backhaul (BH) RLC channel. The IAB-node is connected to another IAB-node via another BH RLC channel. The F1-C traffic is shown as a blue line from the IAB-node to the IAB-donor, and the F1-U traffic is shown as a red line from the IAB-donor to the IAB-node. + +Figure 7.12-1: F1-C transfer in NR-DC; a) Scenario 1; b) Scenario 2 + +**Scenario 1:** IAB-node exchanges F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet with the SN (F1-terminating IAB-donor as specified in TS 38.401 [7]) using NR access link via MN (non-F1-terminating IAB-donor), and exchanges F1-U traffic using backhaul link(s) with SN. SRB2 is used for transporting the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet between IAB-MT and MN (see TS 38.331 [4]), and the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet is transferred in a container via XnAP between MN and SN, see TS 38.423 [5]. + +**Scenario 2:** IAB-node exchanges F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet with the MN (F1-terminating IAB-donor) using NR access link via SN (non-F1-terminating IAB-donor), and exchanges F1-U traffic using backhaul link(s) with MN. Split SRB2 is used for transporting the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet between IAB-MT and SN (see TS 38.331 [4]), and the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet is transferred in a container via XnAP between SN and MN, see TS 38.423 [5]. + +The F1-AP message encapsulated in SCTP/IP or the F1-C related (SCTP/IP) packet can be transferred either over BAP sublayer or over SRB, but the two mechanisms cannot be supported simultaneously on the same parent link. The F1-AP message encapsulated in SCTP/IP or the F1-C related (SCTP/IP) packet is transferred over BAP sublayer, if the BH RLC channel used for transferring the F1-C traffic is configured on the cell group indicated for F1-C traffic transfer according to TS 38.331 [4]. + +## 7.13 Activation and Deactivation of SCG + +To enable reasonable UE battery consumption while having fast usage of SCG when (NG)EN-DC or NR-DC is configured, an activation/deactivation mechanism of SCG is supported. While the SCG is deactivated, there is no + +transmission via SCG RLC bearers. Only the NR SCG can be deactivated, and all SCG SCell(s) are in deactivated state while the SCG is deactivated. + +Upon SCG deactivation and while the SCG is deactivated, the network ensures that there is no uplink control PDU transmission to the deactivated SCG (e.g. the network releases statusReportRequired from PDCP entities of SCG bearers if configured, the network does not perform QoS flow remapping from a DRB associated to the deactivated SCG to another DRB). The network ensures the SCG is activated while PDCP duplication is activated for SCG RLC entities associated with a PDCP entity. + +NOTE: Upon SCG (de)activation, it is up to the network to ensure there is no pending SDUs or PDUs in SCG RLC entity (e.g. instructs the UE to perform PDCP data recovery and RLC re-establishment/release, if needed). + +While the SCG is deactivated, the UE will not transmit PUSCH, SRS and CSI report on SCG, and the UE is not required to monitor PDCCH or receive DL-SCH on SCG. If configured by the network, the UE performs radio link monitoring on the SCG and beam failure detection on the SCG while SCG is deactivated. In case of SCG activation without performing random access, the network can indicate TCI states to UE for PDCCH/PDSCH reception on PSCell, if not provided, the UE uses the previously activated TCI states. + +The MN can configure the SCG as activated or deactivated upon e.g. PSCell addition, PSCell change, RRC Resume or handover. In case the SCG is configured as deactivated, the UE does not perform random access towards the PSCell. The network can trigger SCG RRC reconfiguration (e.g. PSCell change, configuration update) when deactivating the SCG and while the SCG is in deactivated state. + +SCG activation can be requested by the MN, by the SN and by the UE. SCG deactivation can be requested by the MN and by the SN. For UL data arrival on SCG bearer(s) while the SCG is deactivated, the UE indicates to the MN that it has UL data to transmit over SCG bearer. During handover procedure, the target MN can indicate the SCG state in the RRC reconfiguration message sent to the UE by the source MN. + +Network can configure whether the UE is allowed to indicate a preference for SCG deactivation to the MN. + +## 7.14 RLM/BFD relaxation + +For RLM and BFD relaxation, network may configure low mobility criterion in the NR PCell for the case of NE-DC/NR-DC, and in the NR PSCell for the case of EN-DC and NGEN-DC. MN informs SN when low mobility criterion has been configured in the NR PCell for NR-DC. + +For RLM relaxation, network may configure good serving cell criterion in the NR PCell for the case of NE-DC/NR-DC, and in the NR PSCell for the case of EN-DC, NGEN-DC and NR-DC. + +For BFD relaxation, network may configure good serving cell criterion in the NR PCell and/or SCell(s) for the case of NE-DC/NR-DC, and in the NR PSCell and/or SCell(s) for the case of EN-DC, NGEN-DC and NR-DC. + +For RLM/BFD relaxation, network may simultaneously configure the UE to perform radio link monitoring on the SCG and beam failure detection on the SCG while SCG is deactivated. In such case, UE initiates UE assistance information for the relaxation state report of RLM/BFD measurements for SCG. + +For RLM/BFD relaxation, network may simultaneously configure the UE not to perform radio link monitoring on the SCG and beam failure detection on the SCG while SCG is deactivated. In such case, UE assistance information for the relaxation state report of RLM/BFD measurements for SCG will not be initiated. + +# --- 8 Bearer handling aspects + +## 8.1 QoS aspects + +In EN-DC, the E-UTRAN QoS framework defined in TS 36.300 [2] applies: + +- An S1-U bearer is established between the EPC and the SN for SN terminated bearers; + +- An X2-U bearer is established between the MN and the SN for split bearers, MN terminated SCG bearers and SN terminated MCG bearers; +- MN terminated and SN terminated bearers may have either MCG or SCG radio resources or both, MCG and SCG radio resources, established; + +In MR-DC with 5GC: + +- The NG-RAN QoS framework defined in TS 38.300 [3] applies; +- QoS flows belonging to the same PDU session may be mapped to different bearer types (see clause 4.2.2) and as a result there may be two different SDAP entities for the same PDU session: one at the MN and another one at the SN, in which case the MN decides which QoS flows are assigned to the SDAP entity in the SN. If the SN decides that its SDAP entity cannot host a given QoS flow any longer, the SN informs the MN and the MN cannot reject the request. If the MN decides that its SDAP entity can host a given QoS flow which has already been relocated to SN, the MN informs the SN; +- The MN or SN node that hosts the SDAP entity for a given QoS flow decides how to map the QoS flow to DRBs; +- If the SDAP entity for a given QoS flow is hosted by the MN and the MN decides that SCG resources are to be configured it provides to the SN + - DRB QoS flow level QoS parameters, which the SN may reject, and + - QoS flow to DRB mapping information and the respective per QoS flow information; +- If the SDAP entity for a given QoS flow is hosted by the SN and the SN configures MCG resources, based on offered MCG resource information from the MN, the SN provides to the MN + - DRB QoS flow level QoS parameters, which the MN may reject, and + - QoS flow to DRB mapping information and the respective per QoS flow information. +- If the SDAP entity for a given QoS flow is hosted by the SN, the MN provides sufficient QoS related information to enable the SN to configure appropriate SCG resources and to request the configuration of appropriate MCG resources. The MN may offer MCG resources to the SN and may indicate for GBR QoS flows the amount offered to the SN on a per QoS flow level. Otherwise, the SN can only use SCG resources for the concerned QoS flow. The SN may request the MN to release QoS flows from the SDAP entity hosted by the SN that the MN cannot reject. The MN may also offer MCG resources per PDU Session for all DRBs to which non-GBR QoS flows contained in the PDU Session are mapped. +- MN decides the DL PDU session AMBR and UL PDU session AMBR limits to be assigned to the SN, and indicates these to the SN: + - The PDCP entity at the SN applies the received DL PDU session AMBR limit to the set of all bearers for which the SN hosts PDCP for the UE; + - The MAC entity at the SN applies the received UL PDU session AMBR limit to the scheduled uplink radio traffic at the SN for the UE. +- The MN can decide to reallocate one or more QoS flows from the MN to the SN. In such case, the SN decides which DRBs the offloaded QoS flows are mapped to. It is possible to avoid/ minimise loss and ensure in-order delivery when reallocating all QoS flows mapped to a given DRB in the MN by keeping the QoS flows mapped to the same DRB in the SN. To achieve this, the SN should behave similar to what is specified for the target NG-RAN node upon handover, see TS 38.300 clause 9.2.3.2.2 [3]. The corresponding behaviour applies when QoS flows are re-allocated from the SN to the MN. +- The MN decides the DL UE Slice MBR and UL UE Slice MBR limits to be assigned to the SN, and indicates these to the SN: + - The PDCP entity at the SN applies the received DL UE Slice MBR limit to the set of all bearers for which the SN hosts PDCP for the concerned Slice, as defined in TS 23.501 [11]; + - The MAC entity at the SN applies the received UL UE Slice MBR limit to the scheduled uplink radio traffic at the SN for the concerned Slice, as defined in TS 23.501 [11]. + +In all MR-DC cases: + +- The MN decides the DL UE AMBR and UL UE AMBR limits to be assigned to the SN, and indicates these to the SN: +- The PDCP entity at the SN applies the received DL UE AMBR limit to the set of all bearers for which the SN hosts PDCP for the UE; +- The MAC entity at the SN applies the received UL UE AMBR limit to the scheduled uplink radio traffic at the SN for the UE. + +To support PDU sessions mapped to different bearer types, MR-DC with 5GC provides the possibility for the MN to request the 5GC: + +- For some PDU sessions of a UE: Direct the User Plane traffic of the whole PDU session either to the MN or to the SN. In that case, there is a single NG-U tunnel termination at the NG-RAN for such PDU session. +- The MN may request to change this assignment during the life time of the PDU session. +- For some other PDU sessions of a UE: Direct the User Plane traffic of a subset of the QoS flows of the PDU session to the SN (respectively MN) while the rest of the QoS flows of the PDU session is directed to the MN (respectively SN). In that case, there are two NG-U tunnel terminations at the NG-RAN for such PDU session. +- The MN may request to change this assignment during the life time of the PDU session. + +To support notification control indication for GBR QoS flows along the QoS framework specified in 38.300 [3] for MR-DC with 5GC, SN and MN may mutually indicate whenever QoS requirements for GBR QoS flows cannot be fulfilled anymore or can be fulfilled again. When indicating that GBR QoS flows cannot be fulfilled anymore, SN or MN may additionally indicate the reference to the QoS Parameter Set which it can currently fulfil. + +## 8.2 Bearer type selection + +In EN-DC, for each radio bearer the MN decides the location of the PDCP entity and in which cell group(s) radio resources are to be configured. Once an SN terminated split bearer is established, e.g. by means of the Secondary Node Addition procedure or MN initiated Secondary Node Modification procedure, the SN may remove SCG resources for the respective E-RAB, as long as the QoS for the respective E-RAB is guaranteed. In case an SN terminated bearer is released or reconfigured to an MN terminated bearer, only the MN generates the corresponding configuration and the SN does not generate the release configuration. + +In MR-DC with 5GC, the following principles apply: + +- The MN decides per PDU session the location of the SDAP entity, i.e. whether it shall be hosted by the MN or the SN or by both (split PDU session); +- If the MN decides to host an SDAP entity it may decide some of the related QoS flows to be realized as MCG bearer, some as SCG bearer, and others to be realized as split bearer; +- If the MN decides that an SDAP entity shall be hosted in the SN, some of the related QoS flows may be realized as SCG bearer, some as MCG bearer, while others may be realized as split bearer. In this case, the SN decides how to realise the QoS flow, but if the MN does not offer MCG resources, the SN can only realize the QoS flow as SCG bearer. The SN may remove or add SCG resources for the respective QoS flows, as long as the QoS for the respective QoS flow is guaranteed +- If the MN decides that an SDAP entity shall be hosted in the SN, coordination of DRB IDs between the MN and the SN is needed to ensure unique allocation of DRBs for a UE. The SN is responsible to assign the DRB IDs for the DRBs it terminates, based on the DRB IDs indicated by the MN. +- For each PDU session, including split PDU sessions, at most one default DRB may be configured (see [3]). The MN decides whether the SN is allowed to setup the default DRB or not; +- In case an SN terminated bearer is released or reconfigured to an MN terminated bearer, the MN generates the corresponding configuration and the SN does not generate the release configuration. The only exceptional case where SN generates the release configuration is for the DRB release due to QoS flow to DRB remapping within SN. + +## 8.3 Bearer type change + +In MR-DC, all the possible bearer type change options are supported: + +- MCG bearer to/from split bearer; +- MCG bearer to/from SCG bearer; +- SCG bearer to/from split bearer. + +Bearer termination point change is supported for all bearer types, and can be performed with or without bearer type change: + +- MN terminated bearer to/from SN terminated bearer. + +For MR-DC: + +- when the security key is changed for a bearer due to a termination point change, the associated PDCP and RLC entities are re-established, while MAC behavior might depend on the solution selected by the network, e.g. MAC reset, change of LCID, etc. (see Annex A); +- for MCG bearer, split bearer and SCG bearer, during MN security key change the MCG/SCG PDCP and RLC are re-established and MCG/SCG MAC is reset; +- if a bearer type change happens together with MN security key change then for MCG bearer, split bearer and SCG bearer, the MCG/SCG PDCP and RLC are re-established and MCG/SCG MAC is reset; +- if a bearer type change happens through SN change procedure, then SN terminated PDCP and SCG RLC are re-established and SCG MAC is reset. MCG RLC/MAC behavior depends on the solution selected by the network, see Annex A; +- one step (direct) bearer type change between MN terminated bearer types without using the handover procedure is supported; +- one step (direct) bearer type change between SN terminated bearer types without using the handover or SN change procedure is supported; +- one step (direct) bearer type change from/to MN terminated bearer to/from SN terminated bearer without using the handover procedure is supported; +- PDCP SN length change for an AM DRB or RLC mode change for DRB is performed using a release and add of the DRBs (in a single message) or full configuration; +- One step (direct) bearer type change with PDCP version change (only applicable for EN-DC) is supported. + +For MR-DC with 5GC: + +- in a bearer termination point change of a DRB from a source NG-RAN node to a target NG-RAN node, for each DRB for which the source NG-RAN node provides QoS flow to DRB mapping information to the target NG-RAN node, the source NG-RAN node also offers the indicated DRB ID for usage at the target NG-RAN node. The target NG-RAN node informs the source NG-RAN node if it accepts the DRB offloading and takes the DRB ID into use. + +NOTE 1: In this clause the term "handover" refers to an E-UTRA handover or to an NR synchronous reconfiguration not necessarily implying a P(S)Cell change with or without security key change. + +NOTE 2: L2 handling for bearer type change in MR-DC is also summarized in Annex A (the table does not consider the cases that PDCP SN length is changed and avoiding reuse of COUNT). + +## 8.4 User data forwarding + +Upon EN-DC specific activities, user data forwarding may be performed for E-RABs for which the bearer type change from/to MN terminated bearer to/from SN terminated bearer is performed. The behaviour of the node from which data + +is forwarded is the same as specified for the "source eNB" for handover, the behaviour of the node to which data is forwarded is the same as specified for the "target eNB" for handover. + +For MR-DC with 5GC, user data forwarding may be performed between NG-RAN nodes whenever the logical node hosting the PDCP entity changes. The behaviour of the node from which data is forwarded is the same as specified for the "source NG-RAN node" for handover, the behaviour of the node to which data is forwarded is the same as specified for the "target NG-RAN node" for handover. + +For SN change involving full configuration, the source SN behaviour is the same as the description as specified in intra-system data forwarding in TS 36.300 [2] for the source eNB or TS 38.300 [3] for the source NG-RAN node, respectively. In case that a DRB DL forwarding tunnel was established, the target SN may identify the PDCP SDUs for which delivery was attempted by the source SN, by the presence of the PDCP SN in the forwarded GTP-U packet and may discard them. + +For mobility scenarios which involve more than two RAN nodes, either direct or indirect data forwarding may be applied. Two transport layer addresses of different versions may be provided to enable that the source RAN node can select either IPv4 or IPv6. + +Direct data forwarding from source SN to target NG-RAN node and from source NG-RAN node to target SN for mobility scenario is supported. Direct data forwarding from source SN to target SN for SN change scenario is also supported. + +In case of NR-DC to NR-DC handover, direct data forwarding from source SN to target MN, from source SN to target SN and from source MN to target SN is supported. + +Direct data forwarding for inter-system handover is specified in TS 38.300 [3]. If a gNB and an en-gNB are involved in direct data forwarding and realised within the same network entity, inter-system handover to and from EN-DC allows direct data forwarding being performed in a node-internal way, in which case the source RAN node provides a UE context reference to the target side as described in clause 10.16. If the gNB and en-gNB are not realised within the same network entity, direct data forwarding for inter-system handover to and from en-gNB/gNB could be supported if there is direct connectivity between the two nodes. + +For MR-DC with 5GC, offloading of QoS flows within one PDU session may be performed between NG-RAN nodes. The handling of End Marker packets in case of NG-RAN initiated PDU session split is described in clause 10.14.3 and 10.14.4. + +# --- 9 Security related aspects + +MR-DC can only be configured after security activation in the MN. + +In EN-DC and NGEN-DC, for bearers terminated in the MN the network configures the UE with $K_{eNB}$ ; for bearers terminated in the SN the network configures the UE with $S-K_{gNB}$ . In NE-DC, for bearers terminated in the MN the network configures the UE with $K_{gNB}$ ; for bearers terminated in the SN the network configures the UE with $S-K_{eNB}$ . In NR-DC, for bearers terminated in the MN the network configures the UE with $K_{gNB}$ ; for bearers terminated in the SN the network configures the UE with $S-K_{gNB}$ . + +In NE-DC and NR-DC, a PCell change without $K_{gNB}$ change does not require a $S-K_{eNB}$ change (NE-DC case) or a $S-K_{gNB}$ change (NR-DC case). + +In EN-DC, NGEN-DC and NR-DC, for a PSCell change that does not require a $K_{eNB}$ change (i.e. no simultaneous PCell handover in EN-DC and NGEN-DC) or a $K_{gNB}$ change (in NR-DC), $S-K_{gNB}$ key refresh is not required if the PDCP termination point of the SN is not changed. In NE-DC, a PSCell change always requires a $S-K_{eNB}$ change. + +In EN-DC, the UE supports the NR security algorithms corresponding to the E-UTRA security algorithms signalled at NAS level and the UE NR AS Security capability is not signalled to the MN over RRC. Mapping from E-UTRA security algorithms to the corresponding NR security algorithms, where necessary, is performed at the MN. The MN sends the complete UE security capabilities including all security capability bits previously received (after mapping, where necessary) to the SN. + +An EN-DC capable UE supporting user plane integrity protection when connected to E-UTRA/EPC (see TS 24.301 [22]) shall support integrity protection for all DRBs (MN and SN terminated) at any data rate, up to and including the + +highest data rate supported by the UE for both UL and DL. MN and/or SN terminated DRBs can have UP integrity protection activation either on or off, on a per radio bearer basis. + +For MR-DC with 5GC, UP integrity protection can be configured on a per radio bearer basis. All DRBs which belong to the same PDU session always have the same UP integrity protection activation, i.e., either on or off: + +- For NR-DC: MN and/or SN terminated DRBs of a PDU session can have UP integrity protection activation either on or off. A UE configured to operate in NR-DC shall support integrity protection for all DRBs (MN and SN terminated) at any data rate, up to and including the highest data rate supported by the UE for both UL and DL (see TS 38.300 [3]). +- For NE-DC: MN terminated DRBs of a PDU session can have UP integrity protection activation on; however, in this case, the MN will not at any point offload any DRB of such PDU session to the SN. A UE configured to operate in NE-DC shall support integrity protection for all MN terminated DRBs at any data rate, up to and including the highest data rate supported by the UE's radio access capabilities for both UL and DL (see TS 38.300 [3]). SN terminated DRBs of a PDU session always have UP integrity protection activation off. +- For NGEN-DC: Both MN terminated and SN terminated DRBs of a PDU session always have UP integrity protection activation off. + +In MR-DC with 5GC, the MN sends the complete UE security capabilities to the SN including all NR and E-UTRA security capability bits previously received by the MN from the Core Network or from another NG-RAN node as specified in TS 38.300 [3]. + +In (NG)EN-DC and NR-DC, if the SCG is deactivated as described in clause 7.13, whether to perform security key update upon SCG activation is up to network implementation. + +# --- 10 Multi-Connectivity operation related aspects + +## 10.1 General + +Similar procedures as defined under clause 10.1.2.8 (Dual Connectivity operation) in TS 36.300 [2] apply for MR-DC. + +Similar CHO principles as defined in TS 36.300 [2] and TS 38.300 [3] apply for the Conditional PSCell Change and Conditional PSCell Addition in MR-DC. + +Similar LTM principles as defined in TS 38.300 [3] apply for MCG LTM and SCG LTM in NR-DC. MCG LTM with SCG release and MCG LTM without SCG change are supported. LTM for simultaneous PCell and PSCell change is not supported. + +Conditional PSCell Change and conditional PSCell addition are not supported for the MR-DC options NE-DC and NGEN-DC. + +Subsequent CPAC is only supported for NR-DC. + +Configuration of a deactivated SCG in a conditional configuration, configuration of CPC (or subsequent CPAC) while the SCG is deactivated and SCG deactivation while CPC (or subsequent CPAC) is configured are not supported. + +In MR-DC, CHO is supported in Master Node to eNB/gNB Change procedure and Conditional Handover with Secondary Node procedure. + +## 10.2 Secondary Node Addition + +### 10.2.1 EN-DC + +The Secondary Node Addition procedure is initiated by the MN and is used to establish a UE context at the SN to provide resources from the SN to the UE. For bearers requiring SCG radio resources, this procedure is used to add at least the first cell of the SCG. This procedure can also be used to configure an SN terminated MCG bearer (where no SCG configuration is needed). In case of CPA, the Conditional Secondary Node Addition procedure can be used for CPA configuration and CPA execution. + +#### Secondary Node Addition + +Figure 10.2.1-1 shows the Secondary Node Addition procedure. + +![Sequence diagram of the Secondary Node Addition procedure. The diagram shows interactions between UE, MN, SN, S-GW, and MME. The process starts with the MN sending an SgNB Addition Request to the SN. The SN responds with an SgNB Addition Request Acknowledge. The MN then sends an RRCConnectionReconfiguration to the UE, which responds with RRCConnectionReconfigurationComplete. The MN sends an SgNB Reconfiguration Complete to the SN. The SN initiates a Random Access Procedure with the UE. The SN sends an SN Status Transfer to the MN. The MN initiates a Path Update procedure with the S-GW, which involves an E-RAB Modification Indication to the MME, a Bearer Modification from the MME, and an E-RAB Modification Confirm back to the S-GW. The MN also performs Data Forwarding and sends an End Marker Packet to the SN.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + + Note right of SN: Path Update procedure + MN->>SN: 1. SgNB Addition Request + SN-->>MN: 2. SgNB Addition Request Acknowledge + MN->>UE: 3. RRCConnectionReconfiguration + UE-->>MN: 4. RRCConnectionReconfigurationComplete + MN->>SN: 5. SgNB Reconfiguration Complete + SN->>UE: 6. Random Access Procedure + SN->>MN: 7. SN Status Transfer + Note right of SN: Data Forwarding + MN->>SN: 8. Data Forwarding + Note right of SN: End Marker Packet + MN->>SN: 11. End Marker Packet + Note right of SN: Path Update procedure + MN->>S-GW: 9. E-RAB Modification Indication + S-GW->>MME: 10. Bearer Modification + MME-->>S-GW: 12. E-RAB Modification Confirm + +``` + +Sequence diagram of the Secondary Node Addition procedure. The diagram shows interactions between UE, MN, SN, S-GW, and MME. The process starts with the MN sending an SgNB Addition Request to the SN. The SN responds with an SgNB Addition Request Acknowledge. The MN then sends an RRCConnectionReconfiguration to the UE, which responds with RRCConnectionReconfigurationComplete. The MN sends an SgNB Reconfiguration Complete to the SN. The SN initiates a Random Access Procedure with the UE. The SN sends an SN Status Transfer to the MN. The MN initiates a Path Update procedure with the S-GW, which involves an E-RAB Modification Indication to the MME, a Bearer Modification from the MME, and an E-RAB Modification Confirm back to the S-GW. The MN also performs Data Forwarding and sends an End Marker Packet to the SN. + +**Figure 10.2.1-1: Secondary Node Addition procedure** + +- The MN decides to request the SN to allocate resources for a specific E-RAB, indicating E-RAB characteristics (E-RAB parameters, TNL address information corresponding to bearer type). In addition, for bearers requiring SCG radio resources, MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the latest measurement results for SN to choose and configure the SCG cell(s). The MN may request the SN to allocate radio resources for split SRB operation. The MN always provides all the needed security information to the SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. In case of bearer options that require X2-U resources between the MN and the SN, the MN provides X2-U TNL address information for the respective E-RAB, X2-U DL TNL address information for SN terminated bearers, X2-U UL TNL address information for MN terminated bearers. In case of SN terminated split bearers the MN provides the maximum QoS level that it can support. The MN may request the SCG to be activated or deactivated. The SN may reject the addition request. + +NOTE 1: For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MNs decision is reflected in step 1 by the E-RAB parameters signalled to the SN, which may differ from E-RAB parameters received over S1. + +NOTE 2: For a specific E-RAB, the MN may request the direct establishment of an SCG or a split bearer, i.e., without first having to establish an MCG bearer. It is also allowed that all E-RABs can be configured as SN terminated bearers, i.e. there is no E-RAB established as an MN terminated bearer. + +- If the RRM entity in the SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer option, respective transport network resources. For bearers requiring SCG radio resources, the SN triggers Random Access so that synchronisation of the SN radio resource configuration can be performed. The SN decides the PSCell and other SCG SCells and provides the new SCG radio resource configuration to the MN in a *NR RRC configuration* message contained in the *SgNB Addition Request Acknowledge* message. In case of bearer options that require X2-U resources between the MN and the SN, the SN provides X2-U TNL address information for the respective E-RAB, X2-U UL TNL address information for SN terminated bearers, X2-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the SN provides the S1-U DL TNL address information for the respective E-RAB and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided. If the MN requested the SCG to be deactivated, the SN may keep the SCG activated. If the MN requests the SCG to be activated, the SN shall keep the SCG activated. + +- NOTE 3: For the SN terminated split bearer option, the SN may either decide to request resources from the MN of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MN and the SN together, or even more. The SNs decision is reflected in step 2 by the E-RAB parameters signalled to the MN, which may differ from E-RAB parameters received in step 1. The QoS level requested from the MN shall not exceed the level that the MN offered when setting up the split bearer in step 1. +- NOTE 4: In case of MN terminated bearers, transmission of user plane data may take place after step 2. +- NOTE 5: In case of SN terminated bearers, data forwarding and the SN Status Transfer may take place after step 2. +3. The MN sends to the UE the *RRCConnectionReconfiguration* message including the NR RRC configuration message, without modifying it. Within the MN *RRCConnectionReconfiguration* message, the MN can indicate the SCG is deactivated. + 4. The UE applies the new configuration and replies to MN with *RRCConnectionReconfigurationComplete* message, including a NR RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the *RRCConnectionReconfiguration* message, it performs the reconfiguration failure procedure. + 5. The MN informs the SN that the UE has completed the reconfiguration procedure successfully via *SgNB ReconfigurationComplete* message, including the encoded NR RRC response message, if received from the UE. + 6. If configured with bearers requiring SCG radio resources and the SCG is not deactivated, the UE performs synchronisation towards the PSCell of the SN. The order the UE sends the *RRCConnectionReconfigurationComplete* message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure. + 7. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the *SN Status Transfer* message. + 8. For SN terminated bearers moved from the MN, dependent on the bearer characteristics of the respective E-RAB, the MN may take actions to minimise service interruption due to activation of EN-DC (Data forwarding). + - 9-12. If applicable, the update of the UP path towards the EPC is performed. + +#### Conditional Secondary Node Addition + +Figure 10.2.1-2 shows the Conditional Secondary Node Addition procedure. + +![Sequence diagram of the Conditional Secondary Node Addition procedure. Lifelines: UE, MN, SN, Other potential SN, S-GW, MME. The procedure involves SgNB Addition Requests from MN to SN and Other potential SN, followed by acknowledgments. The MN then sends an RRCConnectionReconfiguration to the UE. The UE responds with RRCConnectionReconfigurationComplete. The MN then sends an SgNB Reconfiguration Complete to the SN, followed by an SgNB Release Request to the Other potential SN, which receives an acknowledgment. The UE performs a Random Access Procedure with the SN. The MN sends an SN Status Transfer to the SN, followed by Data Forwarding. A Path Update procedure is initiated between the MN and the MME, involving an E-RAB Modification Indication from the MN to the MME, a Bearer Modification from the MME to the S-GW, and an E-RAB Modification Confirm from the S-GW to the MN.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant Other potential SN + participant S-GW + participant MME + + Note left of UE: 1. MN decides to configure CPA for the UE and requests the candidate SN(s) to allocate resources for a specific E-RAB... + MN->>SN: 1. SgNB Addition Request + MN->>Other potential SN: 1. SgNB Addition Request + SN-->>MN: 2. SgNB Addition Request Acknowledge + Other potential SN-->>MN: 2. SgNB Addition Request Acknowledge + Note left of UE: 3. RRCConnectionReconfiguration (containing MN RRCConnectionReconfiguration* containing SN RRCReconfiguration***) + MN->>UE: 3. RRCConnectionReconfiguration (containing MN RRCConnectionReconfiguration* containing SN RRCReconfiguration***) + Note left of UE: 4. RRCConnectionReconfigurationComplete + UE->>MN: 4. RRCConnectionReconfigurationComplete + Note left of UE: 4a. RRCConnectionReconfigurationComplete* (containing SN RRCReconfigurationComplete***) + UE->>MN: 4a. RRCConnectionReconfigurationComplete* (containing SN RRCReconfigurationComplete***) + Note left of MN: 5a. SgNB Reconfiguration Complete + MN->>SN: 5a. SgNB Reconfiguration Complete + Note left of MN: 5b. SgNB Release Request + MN->>Other potential SN: 5b. SgNB Release Request + Other potential SN-->>MN: 5c. SgNB Release Request Acknowledge + Note left of UE: 6. Random Access Procedure + UE->>SN: 6. Random Access Procedure + Note left of MN: 7. SN Status Transfer + MN->>SN: 7. SN Status Transfer + Note left of MN: 8. Data Forwarding + MN->>SN: 8. Data Forwarding + Note left of MN: Path Update procedure + MN->>MME: 9. E-RAB Modification Indication + MME->>S-GW: 10. Bearer Modification + S-GW->>MN: 12. E-RAB Modification Confirm + Note left of MN: 11. End Marker Packet + MN->>SN: 11. End Marker Packet + +``` + +Sequence diagram of the Conditional Secondary Node Addition procedure. Lifelines: UE, MN, SN, Other potential SN, S-GW, MME. The procedure involves SgNB Addition Requests from MN to SN and Other potential SN, followed by acknowledgments. The MN then sends an RRCConnectionReconfiguration to the UE. The UE responds with RRCConnectionReconfigurationComplete. The MN then sends an SgNB Reconfiguration Complete to the SN, followed by an SgNB Release Request to the Other potential SN, which receives an acknowledgment. The UE performs a Random Access Procedure with the SN. The MN sends an SN Status Transfer to the SN, followed by Data Forwarding. A Path Update procedure is initiated between the MN and the MME, involving an E-RAB Modification Indication from the MN to the MME, a Bearer Modification from the MME to the S-GW, and an E-RAB Modification Confirm from the S-GW to the MN. + +**Figure 10.2.1-2: Conditional Secondary Node Addition procedure** + +- The MN decides to configure CPA for the UE and requests the candidate SN(s) to allocate resources for a specific E-RAB, indicating E-RAB characteristics (E-RAB parameters, TNL address information corresponding to bearer type), indicating that the request is for CPAC and providing the upper limit for the number of PSCells that can be prepared by the candidate SN. In addition, for the bearers requiring SCG radio resources, the MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN to choose from and configure the SCG cell(s). The MN may request the candidate SN to allocate radio resources for split SRB operation. The MN always provides all the needed security information to the candidate SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. In case of bearer options that require X2-U resources between the MN and the candidate SN, the MN provides X2-U TNL address information for the respective E-RAB, X2-U DL TNL address information for SN terminated bearers, X2-U UL TNL address information for MN terminated bearers. In case of SN terminated split bearers the MN provides the maximum QoS level that it can support. The candidate SN may reject the addition request. + +NOTE 6: For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MN decision is reflected in step 1 by the E-RAB parameters signalled to the candidate SN, which may differ from E-RAB parameters received over S1. + +NOTE 7: For a specific E-RAB, the MN may request the direct establishment of an SCG or a split bearer, i.e., without first having to establish an MCG bearer. It is also allowed that all E-RABs can be configured as SN terminated bearers, i.e. there is no E-RAB established as an MN terminated bearer. + +- If the RRM entity in the candidate SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer option, respective transport network resources, and provides the prepared PSCell ID(s) to the MN. For bearers requiring SCG radio resources, the candidate SN configures Random Access so that synchronisation of the SN radio resource configuration can be performed at the CPA execution. From the list of cells indicated within the measurement results provided by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides SCG SCells and provides the corresponding SCG radio resource configuration to the MN + +in an NR *RRConnectionReconfiguration\*\** message contained in the *SgNB Addition Request Acknowledge* message. The candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. In case of bearer options that require X2-U resources between the MN and the candidate SN, the candidate SN provides X2-U TNL address information for the respective E-RAB, X2-U UL TNL address information for SN terminated bearers, X2-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the candidate SN provides the S1-U DL TNL address information for the respective E-RAB and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided. + +- NOTE 8: For the SN terminated split bearer option, the candidate SN may either decide to request resources from the MN of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MN and the candidate SN together, or even more. The candidate SN decision is reflected in step 2 by the E-RAB parameters signalled to the MN, which may differ from E-RAB parameters received in step 1. The QoS level requested from the MN shall not exceed the level that the MN offered when setting up the split bearer in step 1. +- NOTE 9: In case of SN terminated bearers, early data forwarding may take place after step 2. For the early data forwarding of SN terminated bearers, the MN forwards the PDCP SDU to the candidate SN and also sends the *Early Status Transfer* message. For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN. +3. The MN sends to the UE an *RRConnectionReconfiguration* message including the CPA configuration, i.e. a list of *RRConnectionReconfiguration\** messages and associated execution conditions. Each *RRConnectionReconfiguration\** message contains the SCG configuration in the *RRReconfiguration\*\** message received from the candidate SN in step 2 and possibly an MCG configuration. Besides, the *RRConnectionReconfiguration* message can also include an updated MCG configuration, e.g., to configure the required conditional measurements. + 4. The UE applies the *RRConnectionReconfiguration* message received in step 3, stores the CPA configuration and replies to the MN with an *RRConnectionReconfigurationComplete* message. In case the UE is unable to comply with (part of) the configuration included in the *RRConnectionReconfiguration* message, it performs the reconfiguration failure procedure. + - 4a. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies *RRConnectionReconfiguration\** message corresponding to the selected candidate PSCell, and sends an *RRConnectionReconfigurationComplete\** message, including an NR *RRReconfigurationComplete\*\** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. + - 5a-5c. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via *SgNB Reconfiguration Complete* message, including the *RRReconfigurationComplete\*\** message. The MN sends the *SgNB Release Request* message(s) to cancel CPA in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. + 6. The UE performs synchronisation towards the PSCell indicated in the *RRConnectionReconfiguration\** message applied in step 4a. The order the UE sends the *RRConnectionReconfigurationComplete\** message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure. + 7. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the *SN Status Transfer* message. + 8. For SN terminated bearers moved from the MN, dependent on the bearer characteristics of the respective E-RAB, the MN may take actions to minimise service interruption due to activation of EN-DC (Data forwarding). + - 9-12. If applicable, the update of the UP path towards the EPC is performed. + +### 10.2.2 MR-DC with 5GC + +The Secondary Node (SN) Addition procedure is initiated by the MN and is used to establish a UE context at the SN in order to provide resources from the SN to the UE. For bearers requiring SCG radio resources, this procedure is used to add at least the initial SCG serving cell of the SCG. This procedure can also be used to configure an SN terminated MCG bearer (where no SCG configuration is needed). In case of CPA, the Conditional Secondary Node Addition + +procedure can be used for CPA configuration and CPA execution. This procedure can also be used to support coordination between the MN and the SN for managing the configuration and reporting of QoE measurements and/or RAN visible QoE measurements in NR-DC. + +#### Secondary Node Addition + +Figure 10.2.2-1 shows the SN Addition procedure. + +![Sequence diagram of the SN Addition procedure showing interactions between UE, MN, SN, UPF, and AMF.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + + Note right of MN: Path Update procedure (dashed box) + MN->>SN: 1. SN Addition Request + SN-->>MN: 2. SN Addition Request Acknowledge + SN-->>MN: 2a. Xn-U Address Indication + MN->>UE: 3. RRC reconfiguration message + UE-->>MN: 4. RRC reconfiguration complete message + MN->>SN: 5. SN Reconfiguration Complete + UE->>SN: 6. Random Access Procedure + MN->>SN: 7. SN Status Transfer + MN-->>UPF: 8. Data Forwarding + MN->>AMF: 9. PDU Session Resource Modify Indication + AMF->>UPF: 10. Bearer Modification + MN-->>UPF: 11. End Marker Packet + AMF-->>MN: 12. PDU Session Resource Modify Confirm + +``` + +Sequence diagram of the SN Addition procedure showing interactions between UE, MN, SN, UPF, and AMF. + +Figure 10.2.2-1: SN Addition procedure + +1. The MN decides to request the target SN to allocate resources for one or more specific PDU Sessions/QoS Flows, indicating QoS Flows characteristics (QoS Flow Level QoS parameters, PDU session level TNL address information, and PDU session level Network Slice info). In addition, for bearers requiring SCG radio resources, MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the latest measurement results for SN to choose and configure the SCG cell(s). The MN may request the SN to allocate radio resources for split SRB operation. In NGEN-DC and NR-DC, the MN always provides all the needed security information to the SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. The MN may request the SCG to be activated or deactivated. + +For MN terminated bearer options that require Xn-U resources between the MN and the SN, the MN provides Xn-U UL TNL address information. For SN terminated bearers, the MN provides a list of available DRB IDs. The S-NG-RAN node shall store this information and use it when establishing SN terminated bearers. The SN may reject the request. + +For SN terminated bearer options that require Xn-U resources between the MN and the SN, the MN provides in step 1 a list of QoS flows per PDU Sessions for which SCG resources are requested to be setup upon which the SN decides how to map QoS flows to DRB. + +In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the *SN Addition Request* message may contain the *QMC Coordination Request* IE. + +NOTE 1: For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective QoS Flow is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MN decision is reflected in step 1 by the QoS Flow parameters signalled to the SN, which may differ from QoS Flow parameters received over NG. + +NOTE 2: For a specific QoS flow, the MN may request the direct establishment of SCG and/or split bearers, i.e. without first having to establish MCG bearers. It is also allowed that all QoS flows can be mapped to SN terminated bearers, i.e. there is no QoS flow mapped to an MN terminated bearer. + +2. If the RRM entity in the SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer type options, respective transport network resources. For bearers requiring SCG radio resources the SN triggers UE Random Access so that synchronisation of the SN radio resource configuration can be performed. The SN decides for the PSCell and other SCG SCells and provides the new SCG radio resource configuration to the MN within an SN RRC configuration message contained in the *SN Addition Request Acknowledge* message. If the MN requested the SCG to be deactivated, the SN may keep the SCG activated. If the MN requests the SCG to be activated, the SN shall keep the SCG activated. In case of bearer options that require Xn-U resources between the MN and the SN, the SN provides Xn-U TNL address information for the respective DRB, Xn-U UL TNL address information for SN terminated bearers, Xn-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the SN provides the NG-U DL TNL address information for the respective PDU Session and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided. + +In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the *SN Addition Request Acknowledge* message may contain the *QMC Coordination Response* IE. + +NOTE 3: In case of MN terminated bearers, transmission of user plane data may take place after step 2. + +NOTE 4: In case of SN terminated bearers, data forwarding and the SN Status Transfer may take place after step 2. + +NOTE 5: For MN terminated bearers for which PDCP duplication with CA is configured in NR SCG side, the MN allocates up to 4 separate Xn-U bearers and the SN provides a logical channel ID for primary or split secondary path to the MN. + +For SN terminated bearers for which PDCP duplication with CA is configured in NR MCG side, the SN allocates up to 4 separate Xn-U bearers and the MN provides a logical channel ID for primary or split secondary path to the SN via an additional MN-initiated SN modification procedure. + +- 2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message. +3. The MN sends the MN RRC reconfiguration message to the UE including the SN RRC configuration message, without modifying it. Within the MN RRC reconfiguration message, the MN can indicate the SCG is deactivated. +4. The UE applies the new configuration and replies to MN with MN RRC reconfiguration complete message, including an SN RRC response message for SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. +5. The MN informs the SN that the UE has completed the reconfiguration procedure successfully via *SN Reconfiguration Complete* message, including the SN RRC response message, if received from the UE. +6. If configured with bearers requiring SCG radio resources and the SCG is not deactivated, the UE performs synchronisation towards the PSCell configured by the SN. The order the UE sends the MN RRC reconfiguration complete message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure. +7. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the *SN Status Transfer* message. +8. For SN terminated bearers or QoS flows moved from the MN, dependent on the characteristics of the respective bearer or QoS flow, the MN may take actions to minimise service interruption due to activation of MR-DC (Data forwarding). +- 9-12. If applicable, the update of the UP path towards the 5GC is performed via a PDU Session Path Update procedure. + +#### Conditional Secondary Node Addition + +Figure 10.2.2-2 shows the Conditional SN Addition procedure. + +![Sequence diagram of the Conditional Secondary Node Addition procedure. Lifelines: UE, MN, SN, Other potential SN, UPF, AMF. The procedure involves SN Addition Requests, Acknowledges, RRC Reconfiguration, SN Reconfiguration Complete, SN Release Request/Acknowledge, Random Access Procedure, SN Status Transfer, Data Forwarding, Path Update procedure (PDU Session Resource Modify Indication, Bearer Modification, End Marker Packet), and PDU Session Resource Modify Confirm.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant Other potential SN + participant UPF + participant AMF + + Note right of MN: 1. SN Addition Request + MN->>SN: 1. SN Addition Request + MN->>Other potential SN: 1. SN Addition Request + Note right of SN: 2. SN Addition Request Acknowledge + SN-->>MN: 2. SN Addition Request Acknowledge + Other potential SN-->>MN: 2. SN Addition Request Acknowledge + Note right of MN: 2a. Xn-U Address Indication + MN-->>SN: 2a. Xn-U Address Indication + MN-->>Other potential SN: 2a. Xn-U Address Indication + Note right of MN: 3. RRCReconfiguration (containing MN RRCReconfiguration* and SN RRCReconfiguration**) + MN->>UE: 3. RRCReconfiguration (containing MN RRCReconfiguration* and SN RRCReconfiguration**) + Note right of UE: 4. RRCReconfigurationComplete + UE->>MN: 4. RRCReconfigurationComplete + Note right of MN: 4a. RRCReconfigurationComplete* (containing SN RRCReconfigurationComplete**) + MN->>SN: 4a. RRCReconfigurationComplete* (containing SN RRCReconfigurationComplete**) + Note right of SN: 5a. SN Reconfiguration Complete + SN-->>MN: 5a. SN Reconfiguration Complete + Note right of MN: 5b. SN Release Request + MN->>Other potential SN: 5b. SN Release Request + Note right of Other potential SN: 5c. SN Release Request Acknowledge + Other potential SN-->>MN: 5c. SN Release Request Acknowledge + Note right of MN: 6. Random Access Procedure + MN->>UE: 6. Random Access Procedure + Note right of MN: 7. SN Status Transfer + MN->>SN: 7. SN Status Transfer + Note right of MN: 8. Data Forwarding + MN->>SN: 8. Data Forwarding + Note right of MN: Path Update procedure + Note right of MN: 9. PDU Session Resource Modify Indication + MN->>AMF: 9. PDU Session Resource Modify Indication + Note right of AMF: 10. Bearer Modification + AMF->>UPF: 10. Bearer Modification + Note right of MN: 11. End Marker Packet + MN->>SN: 11. End Marker Packet + Note right of AMF: 12. PDU Session Resource Modify Confirm + AMF-->>MN: 12. PDU Session Resource Modify Confirm + +``` + +Sequence diagram of the Conditional Secondary Node Addition procedure. Lifelines: UE, MN, SN, Other potential SN, UPF, AMF. The procedure involves SN Addition Requests, Acknowledges, RRC Reconfiguration, SN Reconfiguration Complete, SN Release Request/Acknowledge, Random Access Procedure, SN Status Transfer, Data Forwarding, Path Update procedure (PDU Session Resource Modify Indication, Bearer Modification, End Marker Packet), and PDU Session Resource Modify Confirm. + +Figure 10.2.2-2: Conditional Secondary Node Addition procedure + +- The MN decides to configure CPA for the UE. The MN requests the candidate SN(s) to allocate resources for one or more specific PDU Sessions/QoS Flows, indicating QoS Flows characteristics (QoS Flow Level QoS parameters, PDU session level TNL address information, and PDU session level Network Slice info), indicating that the request is for CPA and providing the upper limit for the number of PSCells that can be prepared by the candidate SN. In addition, for bearers requiring SCG radio resources, the MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN to choose and configure the SCG cell(s). The MN may request the candidate SN to allocate radio resources for split SRB operation. In NR-DC, the MN always provides all the needed security information to the candidate SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. + +For MN terminated bearer options that require Xn-U resources between the MN and the candidate SN, the MN provides Xn-U UL TNL address information. For SN terminated bearers, the MN provides a list of available DRB IDs. The candidate SN shall store this information and use it when establishing SN terminated bearers. The candidate SN may reject the addition request. + +For SN terminated bearer options that require Xn-U resources between the MN and the candidate SN, the MN provides in step 1 a list of QoS flows per PDU Sessions for which SCG resources are requested to be setup upon which the candidate SN decides how to map QoS flows to DRB. + +NOTE 6: For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective QoS Flow is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MN decision is reflected in step 1 by the QoS Flow parameters signalled to the candidate SN, which may differ from QoS Flow parameters received over NG. + +NOTE 7: For a specific QoS flow, the MN may request the direct establishment of SCG and/or split bearers, i.e. without first having to establish MCG bearers. It is also allowed that all QoS flows can be mapped to SN terminated bearers, i.e. there is no QoS flow mapped to an MN terminated bearer. + +2. If the RRM entity in the candidate SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer type options, respective transport network resources, and provides the prepared PSCell ID(s) to the MN. For bearers requiring SCG radio resources the candidate SN configures Random Access so that synchronisation of the SN radio resource configuration can be performed at the CPA execution. From the list of cells indicated within the measurement results provided by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR *RRCREconfiguration\*\** message, contained in the *SN Addition Request Acknowledge* message. The candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. In case of bearer options that require Xn-U resources between the MN and the candidate SN, the candidate SN provides Xn-U TNL address information for the respective DRB, Xn-U UL TNL address information for SN terminated bearers, Xn-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the candidate SN provides the NG-U DL TNL address information for the respective PDU Session and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided. + +NOTE 8: For MN terminated bearers for which PDCP duplication with CA is configured in NR SCG side, the MN allocates up to 4 separate Xn-U bearers and the candidate SN provides a logical channel ID for primary or split secondary path to the MN. + +For SN terminated bearers for which PDCP duplication with CA is configured in NR MCG side, the candidate SN allocates up to 4 separate Xn-U bearers and the MN provides a logical channel ID for primary or split secondary path to the candidate SN via an additional MN-initiated SN modification procedure. + +NOTE 9: In case of SN terminated bearers, early data forwarding may take place after step 2. For the early data forwarding of SN terminated bearers, the MN forwards the PDCP SDU to the candidate SN. For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN. + +- 2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message. In case of early data forwarding in CPA, the MN sends the *Early Status Transfer* message to the candidate SN. +3. The MN sends to the UE an *RRCREconfiguration* message including the CPA configuration, i.e. a list of *RRCREconfiguration\** messages and associated execution conditions. Each *RRCREconfiguration\** message contains the SCG configuration in the *RRCREconfiguration\*\** received from the candidate SN in step 2 and possibly an MCG configuration. Besides, the *RRCREconfiguration* message can also include an updated MCG configuration. e.g. to configure the required conditional measurements. +4. The UE applies the *RRCREconfiguration* message received in step 3, stores the CPA configuration and replies to the MN with an *RRCREconfigurationComplete* message. In case the UE is unable to comply with (part of) the configuration included in the *RRCREconfiguration* message, it performs the reconfiguration failure procedure. +- 4a. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies *RRCREconfiguration\** message corresponding to the selected candidate PSCell, and sends an MN *RRCREconfigurationComplete\** message, including an *RRCREconfigurationComplete\*\** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. +- 5a-5c. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via *SN Reconfiguration Complete* message, including the *RRCREconfigurationComplete\*\** message. The MN sends the *SN Release Request* message(s) to cancel CPA in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. +6. The UE performs synchronisation towards the PSCell indicated in the *RRCREconfiguration\** message applied in step 4a. The order the UE sends the MN *RRCREconfigurationComplete\** message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure. +7. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the *SN Status Transfer* message. + +8. For SN terminated bearers or QoS flows moved from the MN, dependent on the characteristics of the respective bearer or QoS flow, the MN may take actions to minimise service interruption due to activation of MR-DC (Data forwarding). +- 9-12. If applicable, the update of the UP path towards the 5GC is performed via a PDU Session Path Update procedure. + +### 10.2.3 Conditional PSCell Addition + +A Conditional PSCell Addition (CPA) is defined as a PSCell addition that is executed by the UE when execution condition(s) is met. The UE starts evaluating the execution condition(s) upon receiving the CPA configuration, and stops evaluating the execution condition(s) once PSCell addition or PCell change is triggered. + +The following principles apply to CPA: + +- The CPA configuration contains the configuration of CPA candidate PSCell(s), execution condition(s) and may contain the MCG configuration, to be applied when CPA execution is triggered. +- An execution condition may consist of one or two trigger condition(s) (see *CondEvent*, as defined in TS 38.331 [4] or TS 36.331 [10]). Only a single RS type and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be used for the evaluation of CPA execution condition of a single candidate PSCell. +- Before any CPA execution condition is satisfied, upon reception of PSCell addition command or PCell change command, the UE executes the PSCell addition procedure as described in clause 10.2.1 or 10.2.2, or the PCell change procedure as described in clause 9.2.3.2 in TS 38.300[3] or clause 10.1.2.1 in TS 36.300 [2], regardless of any previously received CPA configuration. Upon the successful completion of PSCell addition procedure or PCell change procedure, the UE releases the stored CPA configuration. +- While executing CPA, the UE is not required to continue evaluating the execution condition of other candidate PSCell(s) or PCell(s). +- Once the CPA procedure is executed successfully, the UE releases all stored conditional reconfigurations (i.e. for CPA and for CHO, as specified in TS 38.300 [3] or TS 36.300 [2]). + +CPA configuration in HO command, in PSCell addition command, or within any conditional reconfiguration (i.e., CPA, CPC or CHO configuration) is not supported. + +## 10.3 Secondary Node Modification (MN/SN initiated) + +### 10.3.1 EN-DC + +The Secondary Node Modification procedure may be initiated either by the MN or by the SN and be used to modify, establish or release bearer contexts, to transfer bearer contexts to and from the SN or to modify other properties of the UE context within the same SN. It may also be used to transfer an NR RRC message from the SN to the UE via the MN and the response from the UE via MN to the SN (e.g. when SRB3 is not used). In case of CPA or inter-SN CPC, this procedure is used to modify CPA or inter-SN CPC configuration within the same candidate SN. In case of CPA or inter-SN CPC, this procedure may also be triggered by the candidate SN to add some prepared PSCells from the suggested list or cancel part of the prepared PSCells. In case of intra-SN CPC, this procedure is used to configure, modify or release intra-SN CPC configuration. This procedure may be initiated by the MN or SN to request the SN or MN to deactivate or activate the SCG. + +The Secondary Node modification procedure does not necessarily need to involve signalling towards the UE. + +#### **MN initiated SN Modification** + +![Sequence diagram of SN Modification procedure - MN initiated. Lifelines: UE, MN, SN, S-GW, MME. The procedure involves 11 steps: 1. MN sends SgNB Modification Request to SN; 2. SN responds with SgNB Modification Request Acknowledge; 3. MN sends RRCConnectionReconfiguration to UE; 4. UE performs Random access procedure to MN; 5. UE sends RRCConnectionReconfigurationComplete to MN; 6. MN sends SgNB Reconfiguration Complete to SN; 7. UE performs Random access procedure to SN; 8. MN sends SN Status Transfer to SN; 9. MN sends Data Forwarding to S-GW (dashed green line); 10. SN sends Secondary RAT Data Usage Report to MN; 11. MN initiates Path Update procedure with S-GW and MME (highlighted in a blue box).](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Sequence diagram of SN Modification procedure - MN initiated. Lifelines: UE, MN, SN, S-GW, MME. The procedure involves 11 steps: 1. MN sends SgNB Modification Request to SN; 2. SN responds with SgNB Modification Request Acknowledge; 3. MN sends RRCConnectionReconfiguration to UE; 4. UE performs Random access procedure to MN; 5. UE sends RRCConnectionReconfigurationComplete to MN; 6. MN sends SgNB Reconfiguration Complete to SN; 7. UE performs Random access procedure to SN; 8. MN sends SN Status Transfer to SN; 9. MN sends Data Forwarding to S-GW (dashed green line); 10. SN sends Secondary RAT Data Usage Report to MN; 11. MN initiates Path Update procedure with S-GW and MME (highlighted in a blue box). + +**Figure 10.3.1-1: SN Modification procedure - MN initiated** + +The MN uses the procedure to initiate configuration changes of the SCG within the same SN, e.g. the addition, modification or release of SCG bearer(s) and the SCG RLC bearer of split bearer(s), as well as configuration changes for SN terminated MCG bearers. Bearer termination point change is realized by adding the new bearer configuration and releasing the old bearer configuration within a single MN initiated SN Modification procedure for the respective E-RAB. The MN uses this procedure to perform handover within the same MN while keeping the SN. The MN also uses the procedure to query the current SCG configuration, e.g. when delta configuration is applied in an MN initiated SN change. The MN also uses the procedure to provide the S-RLF related information to the SN. The MN also uses this procedure to activate or deactivate the SCG. The MN may not use the procedure to initiate the addition, modification or release of SCG SCells. The SN may reject the request, except if it concerns the release of SN terminated bearer(s) or the SCG RLC bearer of MN terminated bearer(s), or if it is used to perform handover within the same MN while keeping the SN. Figure 10.3.1-1 shows an example signalling flow for an MN initiated SN Modification procedure. + +1. The MN sends the *SgNB Modification Request* message, which may contain bearer context related or other UE context related information, data forwarding address information (if applicable) and the requested SCG configuration information, including the UE capability coordination result to be used as basis for the reconfiguration by the SN. The MN may request the SCG to be activated or deactivated. In case a security key update in the SN is required, a new *SgNB Security Key* is included. In case of SCG RLC re-establishment for E-RABs configured with an MN terminated bearer with an SCG RLC bearer for which no bearer type change is performed, the MN provides a new UL GTP tunnel endpoint to the SN. The SN shall continue sending UL PDCP PDUs to the MN with the previous UL GTP tunnel endpoint until it re-establishes the RLC and use the new UL GTP tunnel endpoint after re-establishment. In case of PDCP re-establishment for E-RABs configured with an SN terminated bearer with an MCG RLC bearer for which no bearer type change is performed, the MN provides a new DL GTP tunnel endpoint to the SN. The SN shall continue sending DL PDCP PDUs to the MN with the previous DL GTP tunnel endpoint until it performs PDCP re-establishment and use the new DL GTP tunnel endpoint starting with the PDCP re-establishment. +2. The SN responds with the *SgNB Modification Request Acknowledge* message, which may contain SCG radio resource configuration information within a NR RRC configuration message and data forwarding address information (if applicable). If the MN requested the SCG to be activated or deactivated, the SN indicates whether the SCG is activated or deactivated. In case of a security key update (with or without PSCell change), for E-RABs configured with the MN terminated bearer option that require X2-U resources between the MN and the SN, for which no bearer type change is performed, the SN provides a new DL GTP tunnel endpoint to the MN. The MN shall continue sending DL PDCP PDUs to the SN with the previous DL GTP tunnel endpoint until it performs PDCP re-establishment or PDCP data recovery, and use the new DL GTP tunnel endpoint starting with the PDCP re-establishment or data recovery. In case of a security key update (with or without PSCell change), for E-RABs configured with the SN terminated bearer option that require X2-U resources between the MN and the SN, for which no bearer type change is performed, the SN provides a new UL GTP tunnel endpoint to the + +MN. The MN shall continue sending UL PDCP PDUs to the SN with the previous UL GTP tunnel endpoint until it re-establishes the RLC and use the new UL GTP tunnel endpoint after re-establishment. + +NOTE 00: In case SN includes the indication of full RRC configuration in *SgNB Modification Request Acknowledge* message to MN e.g. comprehension failure upon intra-CU inter-DU change, MN performs release and add of the NR SCG part of the configuration but does not release SN terminated radio bearers towards the UE. + +3-5. The MN initiates the RRC connection reconfiguration procedure, including the NR RRC configuration message. The UE applies the new configuration, synchronizes to the MN (if instructed, in case of intra-MN handover) and replies with *RRCConnectionReconfigurationComplete*, including a NR RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the *RRCConnectionReconfiguration* message, it performs the reconfiguration failure procedure. + +6. Upon successful completion of the reconfiguration, the success of the procedure is indicated in the *SgNB Reconfiguration Complete* message. + +7. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SgNB addition procedure. Otherwise, the UE may perform UL transmission after having applied the new configuration. + +8. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN Status Transfer takes place between the MN and the SN (Figure 10.3.1-1 depicts the case where a bearer context is transferred from the MN to the SN). + +NOTE 0: The SN may not be aware that a SN terminated bearer requested to be released is reconfigured to a MN terminated bearer. The SN Status for the released SN terminated bearers with RLC AM may also be transferred to the MN. + +9. If applicable, data forwarding between MN and the SN takes place (Figure 10.3.1-1 depicts the case where a bearer context is transferred from the MN to the SN). + +10. The SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the E-RABs to be released and for the E-RABs for which the S1 UL GTP Tunnel endpoint was requested to be modified. + +NOTE 1: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. + +11. If applicable, a path update is performed. + +#### **SN initiated SN Modification with MN involvement** + +![Sequence diagram of SN Modification procedure - SN initiated with MN involvement. The diagram shows interactions between UE, MN, SN, S-GW, and MME. The SN initiates the procedure with the MN via '1. SgNB Modification Required'. A dashed box labeled 'For providing of Forwarding addresses, SgNB Security Key' contains steps 2 and 3: '2. SgNB Modification Request' and '3. SgNB Modification Request Acknowledge'. The MN then sends '4. RRCConnectionReconfiguration' to the UE, which responds with '5. RRCConnectionReconfigurationComplete'. The MN sends '6. SgNB Modification Confirm' to the SN. The UE performs '7. Random Access Procedure' with the SN. The SN sends '8. SN Status Transfer' to the MN, '9. Data Forwarding' to the S-GW, and '10. Secondary RAT Data Usage Report' to the MN. Finally, a dashed box labeled 'Path Update procedure' shows the MN interacting with the S-GW and MME.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + + Note right of MN: For providing of Forwarding addresses, SgNB Security Key + SN->>MN: 1. SgNB Modification Required + MN->>SN: 2. SgNB Modification Request + SN-->>MN: 3. SgNB Modification Request Acknowledge + MN->>UE: 4. RRCConnectionReconfiguration + UE-->>MN: 5. RRCConnectionReconfigurationComplete + MN->>SN: 6. SgNB Modification Confirm + UE->>SN: 7. Random Access Procedure + SN->>MN: 8. SN Status Transfer + SN->>S-GW: 9. Data Forwarding + SN->>MN: 10. Secondary RAT Data Usage Report + Note right of MN: Path Update procedure + MN->>S-GW + S-GW-->>MME + +``` + +Sequence diagram of SN Modification procedure - SN initiated with MN involvement. The diagram shows interactions between UE, MN, SN, S-GW, and MME. The SN initiates the procedure with the MN via '1. SgNB Modification Required'. A dashed box labeled 'For providing of Forwarding addresses, SgNB Security Key' contains steps 2 and 3: '2. SgNB Modification Request' and '3. SgNB Modification Request Acknowledge'. The MN then sends '4. RRCConnectionReconfiguration' to the UE, which responds with '5. RRCConnectionReconfigurationComplete'. The MN sends '6. SgNB Modification Confirm' to the SN. The UE performs '7. Random Access Procedure' with the SN. The SN sends '8. SN Status Transfer' to the MN, '9. Data Forwarding' to the S-GW, and '10. Secondary RAT Data Usage Report' to the MN. Finally, a dashed box labeled 'Path Update procedure' shows the MN interacting with the S-GW and MME. + +**Figure 10.3.1-2: SN Modification procedure - SN initiated with MN involvement** + +The SN uses the procedure to perform configuration changes of the SCG within the same SN, e.g. to trigger the release of SCG bearer(s) and the SCG RLC bearer of split bearer(s) (upon which the MN may release the bearer or maintain current bearer type or reconfigure it to an MCG bearer, either MN terminated or SN terminated), to trigger the release of SCG resources (e.g., release SCG lower layer resources but keep SN), and to trigger PSCell change (e.g. when a new security key is required or when the MN needs to perform PDCP data recovery). The MN cannot reject the release request of SCG bearer and the SCG RLC bearer of a split bearer and the release request of SCG resources. The SN also uses this procedure to activate or deactivate the SCG. The MN shall either accept modification of all of the requested SCG bearer(s) and the SCG RLC bearer of split bearer(s) and the request of activation or deactivation of the SCG, or fail the procedure. Figure 10.3.1-2 shows an example signalling flow for an SN initiated SgNB Modification procedure, with MN involvement. + +1. The SN sends the *SgNB Modification Required* message including a NR RRC configuration message, which may contain bearer context related, other UE context related information and the new SCG radio resource configuration. The SN may request the SCG to be activated or deactivated. For bearer release or modification, a corresponding E-RAB list is included in the *SgNB Modification Required* message. In case of change of security key, the *PDCP Change Indication* indicates that a $S-K_{\text{gNB}}$ update is required. In case the MN needs to perform PDCP data recovery, the *PDCP Change Indication* indicates that PDCP data recovery is required. In case SN decides to trigger SCG release, the E-RABs to be modified list includes all the E-RABs of the UE with SCG resource indicated as not present for each E-RAB. + +The SN can decide whether the change of security key is required. + +NOTE 1a: In case SN includes the indication of full RRC configuration in *SgNB Modification Required* message to MN e.g. comprehension failure upon intra-CU inter-DU change, MN performs release and add of the NR SCG part of the configuration but does not release SN terminated radio bearers towards the UE. + +NOTE 1b: In case that a MN initiated conditional reconfiguration (e.g. CHO or MN initiated inter-SN CPC) is prepared, and if any execution of a prepared SN initiated intra-SN CPC procedure or reconfiguration of the SCG, the SN notifies to the MN via the *SgNB Modification Required* message. In this case, the steps 2 and 3 are skipped. + +NOTE 1c: In case of SN initiated inter-SN CPC and in case that a candidate SN triggered the SN Initiated SN Modification procedure to include some more prepared PSCells (within the candidate cells suggested by the source SN in SN initiated inter-SN CPC) or to remove some prepared PSCells, the MN may decide to trigger the step 2 towards the source SN. + +2/3. The MN initiated SN Modification procedure may be triggered by the *SN Modification Required* message (e.g. to provide information such as data forwarding addresses, new SN security key, measurement gap, etc...) + +NOTE 2: If only SN security key is provided in step 2, the MN does not need to wait for the reception of step 3 to initiate the RRC connection reconfiguration procedure. + +4. The MN sends the *RRConnectionReconfiguration* message including a NR RRC configuration message to the UE including the new SCG radio resource configuration. + +5. The UE applies the new configuration and sends the *RRConnectionReconfigurationComplete* message, including an encoded NR RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the *RRConnectionReconfiguration* message, it performs the reconfiguration failure procedure. + +6. Upon successful completion of the reconfiguration, the success of the procedure is indicated in the *SgNB Modification Confirm* message containing the encoded NR RRC response message, if received from the UE. + +7. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SN addition procedure. Otherwise, the UE may perform UL transmission after having applied the new configuration. + +8. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN Status Transfer takes place between the MN and the SN (Figure 10.3.1-2 depicts the case where a bearer context is transferred from the SN to the MN). + +NOTE 2a: The SN may not be aware that a SN terminated bearer requesting to release is reconfigured to a MN terminated bearer. The SN Status for the released SN terminated bearers with RLC AM may also be transferred to the MN. + +9. If applicable, data forwarding between MN and the SN takes place (Figure 10.3.1-2 depicts the case where a bearer context is transferred from the SN to the MN). + +10. The SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the E-RABs to be released. + +NOTE 3: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. + +11. If applicable, a path update is performed. + +#### SN initiated SN Modification without MN involvement + +![Sequence diagram for SN initiated SN Modification without MN involvement. The diagram shows three participants: UE, SN, and MN. The sequence of messages is: 1. NR RRCReconfiguration (SN to UE), 2. Random access procedure (UE to SN), 3. NR RRCReconfigurationComplete (UE to SN).](ad91a8c592581096c346cdd7a2bdf9f1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SN + participant MN + Note left of UE: + SN->>UE: 1. NR RRCReconfiguration + UE->>SN: 2. Random access procedure + UE->>SN: 3. NR RRCReconfigurationComplete + +``` + +Sequence diagram for SN initiated SN Modification without MN involvement. The diagram shows three participants: UE, SN, and MN. The sequence of messages is: 1. NR RRCReconfiguration (SN to UE), 2. Random access procedure (UE to SN), 3. NR RRCReconfigurationComplete (UE to SN). + +Figure 10.3.1-3: SN modification - SN initiated without MN involvement + +The SN initiated modification without MN involved procedure is used to modify the configuration within SN in case no coordination with MN is required, including the addition/modification/release of SCG SCell and PSCell change (e.g. + +when the security key does not need to be changed and the MN does not need to be involved in PDCP recovery). The SN may initiate the procedure to configure, modify or release intra-SN CPC configuration within the same SN. Figure 10.3.1-3 shows an example signalling flow for SN initiated SN modification procedure, without MN involvement. The SN can decide whether the Random Access procedure is required. + +1. The SN sends the *RRCReconfiguration* message to the UE through SRB3. The UE applies the new configuration. In case the UE is unable to comply with (part of) the configuration included in the *RRCReconfiguration* message, it performs the reconfiguration failure procedure. +2. If instructed, the UE performs synchronisation towards the PSCell of the SN. +3. The UE replies with the *RRCReconfigurationComplete* message. + +#### **SN initiated Conditional SN Modification without MN involvement (SRB3 is used)** + +![Sequence diagram for SN initiated Conditional SN Modification without MN involvement (SRB3 is used). The diagram shows three entities: UE, SN, and MN. The interaction is as follows: 1. SN sends 'NR RRCReconfiguration (containing CPC configuration)' to UE. 2. UE responds with 'NR RRCReconfigurationComplete (CPC configuration)' to SN. 3. SN initiates a 'Random access procedure' with UE. 4. UE completes the procedure and sends 'NR RRCReconfigurationComplete (CPC execution)' to SN. The MN entity is shown but has no active participation in this sequence.](a5184899f915014fa38608754efcc9c7_img.jpg) + +Sequence diagram for SN initiated Conditional SN Modification without MN involvement (SRB3 is used). The diagram shows three entities: UE, SN, and MN. The interaction is as follows: 1. SN sends 'NR RRCReconfiguration (containing CPC configuration)' to UE. 2. UE responds with 'NR RRCReconfigurationComplete (CPC configuration)' to SN. 3. SN initiates a 'Random access procedure' with UE. 4. UE completes the procedure and sends 'NR RRCReconfigurationComplete (CPC execution)' to SN. The MN entity is shown but has no active participation in this sequence. + +**Figure 10.3.1-3a: SN Modification - SN-initiated without MN involvement and SRB3 is used to configure intra-SN CPC.** + +The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is used to configure intra-SN CPC. + +1. The SN sends the *RRCReconfiguration* message including CPC configuration to the UE through SRB3. +2. The UE applies the new configuration. In case the UE is unable to comply with (part of) the configuration included in the *RRCReconfiguration* message, it performs the reconfiguration failure procedure. The UE starts evaluating the CPC execution conditions for the candidate PSCell(s). The UE maintains connection with the source PSCell and replies with the *RRCReconfigurationComplete* message to the SN via SRB3. +3. If at least one CPC candidate PSCell satisfies the corresponding CPC execution condition, the UE detaches from the source PSCell, applies the stored configuration corresponding to the selected candidate PSCell and synchronises to the candidate PSCell. +4. The UE completes the CPC execution procedure by sending an *RRCReconfigurationComplete* message to the new PSCell. + +##### **Transfer of an NR RRC message to/from the UE (when SRB3 is not used)** + +![Sequence diagram for Transfer of an NR RRC message to/from the UE (when SRB3 is not used). The diagram shows five entities: UE, MN, SN, S-GW, and MME. The interaction is as follows: 1. SN sends 'SgNB Modification Required' to MN. 2. MN sends 'RRConnectionReconfiguration' to UE. 3. UE responds with 'RRConnectionReconfigurationComplete' to MN. 4. MN sends 'SgNB Modification Confirm' to SN. 5. MN initiates a 'Random Access Procedure' with UE.](c79b9212cfc136d4191e637cd9437ffb_img.jpg) + +Sequence diagram for Transfer of an NR RRC message to/from the UE (when SRB3 is not used). The diagram shows five entities: UE, MN, SN, S-GW, and MME. The interaction is as follows: 1. SN sends 'SgNB Modification Required' to MN. 2. MN sends 'RRConnectionReconfiguration' to UE. 3. UE responds with 'RRConnectionReconfigurationComplete' to MN. 4. MN sends 'SgNB Modification Confirm' to SN. 5. MN initiates a 'Random Access Procedure' with UE. + +**Figure 10.3.1-4: Transfer of an NR RRC message to/from the UE** + +The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used. + +1. The SN initiates the procedure by sending the *SgNB Modification Required* to the MN. +2. The MN forwards the NR RRC message to the UE in the *RRConnectionReconfiguration* message. +3. The UE applies the new configuration and replies with the *RRConnectionReconfigurationComplete* message. In case the UE is unable to comply with (part of) the configuration included in the NR RRC message, it performs the reconfiguration failure procedure. +4. The MN forwards the NR RRC response message, if received from the UE, to the SN in the *SgNB Modification Confirm* message. +5. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SgNB Addition procedure. Otherwise the UE may perform UL transmission after having applied the new configuration. + +#### **SN initiated Conditional SN Modification without MN involvement (SRB3 is not used)** + +![Sequence diagram for SN-initiated Conditional SN Modification without MN involvement. The diagram shows interactions between UE, MN, SN, S-GW, and MME. The SN sends an SgNB Modification Required to the MN. The MN sends an RRConnectionReconfiguration (containing CPC configuration) to the UE. The UE replies with an RRConnectionReconfigurationComplete (CPC configuration) to the MN. The MN forwards this to the SN in an SgNB Modification Confirm. The UE then performs UL InformationTransferMRDC (CPC execution) to the MN. The MN sends an RRC Transfer to the SN. Finally, the UE performs a Random Access Procedure with the SN.](1e8c50ad4fca7f315a407347dd5091cc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + Note left of UE: SN initiated Conditional SN Modification without MN involvement (SRB3 is not used) + SN->>MN: 1. SgNB Modification Required + MN->>UE: 2. RRConnectionReconfiguration (containing CPC configuration) + UE->>MN: 3. RRConnectionReconfigurationComplete (CPC configuration) + MN->>SN: 4. SgNB Modification Confirm + UE->>MN: 5. UL InformationTransferMRDC (CPC execution) + MN->>SN: 6. RRC Transfer + UE->>SN: 7. Random Access Procedure + +``` + +Sequence diagram for SN-initiated Conditional SN Modification without MN involvement. The diagram shows interactions between UE, MN, SN, S-GW, and MME. The SN sends an SgNB Modification Required to the MN. The MN sends an RRConnectionReconfiguration (containing CPC configuration) to the UE. The UE replies with an RRConnectionReconfigurationComplete (CPC configuration) to the MN. The MN forwards this to the SN in an SgNB Modification Confirm. The UE then performs UL InformationTransferMRDC (CPC execution) to the MN. The MN sends an RRC Transfer to the SN. Finally, the UE performs a Random Access Procedure with the SN. + +**Figure 10.3.1-5: SN Modification - SN-initiated without MN involvement and SRB3 is not used to configure intra-SN CPC** + +The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used to configure intra-SN CPC. + +1. The SN initiates the procedure by sending the *SgNB Modification Required* to the MN including the SN RRC reconfiguration message with CPC configuration. +2. The MN forwards the SN RRC reconfiguration message to the UE including it in the *RRConnectionReconfiguration* message. +3. The UE replies with the *RRConnectionReconfigurationComplete* message by including the SN RRC reconfiguration complete message. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. The UE maintains connection with source PSCell after receiving CPC configuration, and starts evaluating the CPC execution conditions for the candidate PSCell(s). +4. The MN forwards the SN RRC response message, if received from the UE, to the SN by including it in the *SgNB Modification Confirm* message. +5. If at least one CPC candidate PSCell satisfies the corresponding CPC execution condition, the UE completes the CPC execution procedure by an *ULInformationTransferMRDC* message to the MN which includes an embedded *RRReconfigurationComplete* message to the selected target PSCell. +6. The *RRReconfigurationComplete* message is forwarded to the SN embedded in *RRC Transfer* message. + +- The UE detaches from the source PSCell, applies the stored corresponding configuration and synchronises to the selected candidate PSCell. + +### 10.3.2 MR-DC with 5GC + +The SN Modification procedure may be initiated either by the MN or by the SN and be used to modify the current user plane resource configuration (e.g. related to PDU session, QoS flow or DRB) or to modify other properties of the UE context within the same SN. It may also be used to transfer an RRC message from the SN to the UE via the MN and the response from the UE via MN to the SN (e.g. when SRB3 is not used). In NGEN-DC and NR-DC, the RRC message is an NR message (i.e., *RRRReconfiguration*) whereas in NE-DC it is an E-UTRA message (i.e., *RRRConnectionReconfiguration*). In case of CPA, inter-SN CPC or inter-SN subsequent CPAC, this procedure is used to modify CPA, inter-SN CPC or inter-SN subsequent CPAC configuration within the same candidate SN. In case of CPA, inter-SN CPC or inter-SN subsequent CPAC, this procedure may also be triggered by the candidate SN to add some prepared PSCells from the suggested list or cancel part of the prepared PSCells. In case of intra-SN CPC or intra-SN subsequent CPAC, this procedure is used to configure, modify or release intra-SN CPC or intra-SN subsequent CPAC configuration. In case of intra-SN SCG LTM, this procedure is used to configure, modify or release intra-SN SCG LTM configuration. This procedure may be initiated by the MN or SN to request the SN or MN to activate or deactivate the SCG. This procedure can also be used to support coordination between the MN and the SN for managing the configuration and reporting of QoE measurements and/or RAN visible QoE measurements in NR-DC. + +**Editor's note:** FFS. It's up to RAN3 on how to configure intra-SN subsequent CPAC in MN format and which procedure is to be used, e.g. MN initiated SN modification procedure, SN initiated SN modification with MN involvement procedure, or SN initiated SN change procedure. + +The SN modification procedure does not necessarily need to involve signalling towards the UE. + +#### MN initiated SN Modification + +![Sequence diagram of the SN Modification procedure initiated by the MN. The diagram shows interactions between UE, MN, SN, UPF, and AMF. The MN sends an SN Modification Request to the SN. The SN responds with an SN Modification Request Acknowledge and Xn-U Address information. The MN then sends an RRC reconfiguration message to the UE. The UE performs a Random Access Procedure and sends an RRC reconfiguration complete message. The MN sends an SN Reconfiguration Complete message to the SN. The SN performs a Random Access Procedure and sends an SN Status Transfer to the MN. The MN then initiates Data Forwarding from the SN to the UPF. The SN sends a Secondary RAT Data Usage Report to the MN. Finally, the MN initiates a PDU Session Path Update procedure with the AMF.](9dc9f41d7d76c1add4b190d348cb1533_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + + Note right of MN: MN initiated SN Modification + MN->>SN: 1. SN Modification Request + SN-->>MN: 2. SN Modification Request Acknowledge + SN-->>MN: 2a. Xn-U Address information + MN-->>UE: 3. RRC reconfiguration message + UE-->>MN: 3a. Random Access Procedure + UE-->>MN: 4. RRC reconfiguration complete message + MN-->>SN: 5. SN Reconfiguration Complete + SN-->>UE: 6. Random Access Procedure + SN-->>MN: 7. SN Status Transfer + Note right of SN: 8. Data Forwarding + SN-->>UPF: 8. Data Forwarding + SN-->>MN: 9. Secondary RAT Data Usage Report + Note right of MN: 10. PDU Session Path Update procedure + MN-->>AMF: 10. PDU Session Path Update procedure + +``` + +Sequence diagram of the SN Modification procedure initiated by the MN. The diagram shows interactions between UE, MN, SN, UPF, and AMF. The MN sends an SN Modification Request to the SN. The SN responds with an SN Modification Request Acknowledge and Xn-U Address information. The MN then sends an RRC reconfiguration message to the UE. The UE performs a Random Access Procedure and sends an RRC reconfiguration complete message. The MN sends an SN Reconfiguration Complete message to the SN. The SN performs a Random Access Procedure and sends an SN Status Transfer to the MN. The MN then initiates Data Forwarding from the SN to the UPF. The SN sends a Secondary RAT Data Usage Report to the MN. Finally, the MN initiates a PDU Session Path Update procedure with the AMF. + +**Figure 10.3.2-1: SN Modification procedure - MN initiated** + +The MN uses the procedure to initiate configuration changes of the SCG within the same SN, including addition, modification or release of the user plane resource configuration. The MN uses this procedure to perform handover within the same MN while keeping the SN, when the SN needs to be involved (i.e. in NGEN-DC). The MN also uses the procedure to query the current SCG configuration, e.g. when delta configuration is applied in an MN initiated SN change. The MN also uses the procedure to provide the S-RLF related information to the SN or to provide additional available DRB IDs to be used for SN terminated bearers. The MN also uses this procedure to activate or deactivate the SCG. The MN may not use the procedure to initiate the addition, modification or release of SCG SCells. The SN may + +reject the request, except if it concerns the release of the user plane resource configuration, or if it is used to perform handover within the same MN while keeping the SN. Figure 10.3.2-1 shows an example signalling flow for an MN initiated SN Modification procedure. + +1. The MN sends the *SN Modification Request* message, which may contain user plane resource configuration related or other UE context related information, PDU session level Network Slice info and the requested SCG configuration information, including the UE capabilities coordination result to be used as basis for the reconfiguration by the SN. In case a security key update in the SN is required, a new *SN Security Key* is included. In case the PDCP data recovery in the SN is required, the *PDCP Change Indication* is included which indicates that PDCP data recovery is required in SN. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the *SN Modification Request* message may contain the *QMC Coordination Request IE*. +2. The SN responds with the *SN Modification Request Acknowledge* message, which may contain new SCG radio configuration information within an SN RRC reconfiguration message, and data forwarding address information (if applicable). If the MN requested the SCG to be activated or deactivated, the SN indicates whether the SCG is activated or deactivated. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the *SN Modification Request Acknowledge* message may contain the *QMC Coordination Response IE*. + +NOTE 1: For MN terminated bearers to be setup for which PDCP duplication with CA is configured in NR SCG side, the MN allocates up to 4 separate Xn-U bearers and the SN provides a logical channel ID for primary or split secondary path to the MN. + +For SN terminated bearers to be setup for which PDCP duplication with CA is configured in NR MCG side, the SN allocates up to 4 separate Xn-U bearers and the MN provides a logical channel ID for primary or split secondary path to the SN via an additional MN-initiated SN modification procedure. + +- 2a. When applicable, the MN provides data forwarding address information to the SN. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message. + - 3/4. The MN initiates the RRC reconfiguration procedure, including an SN RRC reconfiguration message. The UE applies the new configuration, synchronizes to the MN (if instructed, in case of intra-MN handover) and replies with MN RRC reconfiguration complete message, including an SN RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. + 5. Upon successful completion of the reconfiguration, the success of the procedure is indicated in the *SN Reconfiguration Complete* message. + 6. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SN addition procedure. Otherwise, the UE may perform UL transmission after having applied the new configuration. + 7. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN Status Transfer takes place between the MN and the SN (Figure 10.3.2-1 depicts the case where a bearer context is transferred from the MN to the SN). + 8. If applicable, data forwarding between MN and the SN takes place (Figure 10.3.2-1 depicts the case where a user plane resource configuration related context is transferred from the MN to the SN). + 9. The SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. +- NOTE 2: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. +10. If applicable, a PDU Session path update procedure is performed. + +#### SN initiated SN Modification with MN involvement + +![Sequence diagram of SN Modification procedure - SN initiated with MN involvement. The diagram shows interactions between UE, MN, SN, UPF, and AMF. The SN sends an SN Modification Required message to the MN. The MN then initiates an SN Modification procedure (steps 2/3). The MN sends an RRC reconfiguration message to the UE. The UE responds with an RRC reconfiguration complete message. The MN sends an SN Modification Confirm message to the SN. The SN performs a Random Access Procedure with the UE. The SN sends an SN Status Transfer message to the MN. The MN performs Data Forwarding with the UPF. The MN sends a Secondary RAT Data Usage Report to the SN. Finally, the MN initiates a PDU Session Path Update procedure with the AMF.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + + Note right of SN: 1. SN Modification Required + SN->>MN: 1. SN Modification Required + Note right of MN: 2/3. MN initiated SN Modification procedure in some cases + MN->>UE: 4. RRC reconfiguration (Carry SN RRC reconfiguration message) + UE-->>MN: 5. RRC reconfiguration complete (Carry SN RRC reconfiguration complete) + MN->>SN: 6. SN Modification Confirm (Carry SN RRC reconfiguration complete) + SN->>UE: 7. Random Access Procedure + SN-->>MN: 8. SN Status Transfer + Note right of MN: 9. Data Forwarding + MN->>UPF: 9. Data Forwarding + MN-->>SN: 10. Secondary RAT Data Usage Report + Note right of MN: 11. PDU Session Path Update procedure + MN->>AMF: 11. PDU Session Path Update procedure + +``` + +Sequence diagram of SN Modification procedure - SN initiated with MN involvement. The diagram shows interactions between UE, MN, SN, UPF, and AMF. The SN sends an SN Modification Required message to the MN. The MN then initiates an SN Modification procedure (steps 2/3). The MN sends an RRC reconfiguration message to the UE. The UE responds with an RRC reconfiguration complete message. The MN sends an SN Modification Confirm message to the SN. The SN performs a Random Access Procedure with the UE. The SN sends an SN Status Transfer message to the MN. The MN performs Data Forwarding with the UPF. The MN sends a Secondary RAT Data Usage Report to the SN. Finally, the MN initiates a PDU Session Path Update procedure with the AMF. + +**Figure 10.3.2-2: SN Modification procedure - SN initiated with MN involvement** + +The SN uses the procedure to perform configuration changes of the SCG within the same SN, e.g. to trigger the modification/release of the user plane resource configuration, to trigger the release of SCG resources (e.g., release SCG lower layer resources but keep SN), and to trigger PSCell changes (e.g. when a new security key is required or when the MN needs to perform PDCP data recovery). The MN cannot reject the release request of PDU session/QoS flows and the release request of SCG resources. The SN also uses the procedure to request the MN to provide more DRB IDs to be used for SN terminated bearers or to return DRB IDs used for SN terminated bearers that are not needed any longer. The SN also uses this procedure to activate or deactivate the SCG. Figure 10.3.2-2 shows an example signalling flow for SN initiated SN Modification procedure. + +1. The SN sends the *SN Modification Required* message including an SN RRC reconfiguration message, which may contain user plane resource configuration related context, other UE context related information and the new radio resource configuration of SCG. The SN may request the SCG to be activated or deactivated. In case of change of security key, the *PDCP Change Indication* indicates that an SN security key update is required. In case the MN needs to perform PDCP data recovery, the *PDCP Change Indication* indicates that PDCP data recovery is required. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the *SN Modification Required* message may contain the *QMC Coordination Request* IE. + +The SN can decide whether the change of security key is required. + +NOTE 3a: In case that a MN initiated conditional reconfiguration (e.g. CHO, MN initiated inter-SN CPC or MN initiated inter-SN subsequent CPAC) is prepared, and if any execution of a prepared SN initiated intra-SN CPC or SN initiated intra-SN subsequent CPAC without MN involvement procedure or reconfiguration of the SCG, the SN notifies to the MN via the *SN Modification Required* message. In this case, the steps 2 and 3 are skipped. + +NOTE 3b: In case of SN initiated inter-SN CPC or SN initiated inter-SN subsequent CPAC and in case that a candidate SN triggered the SN Initiated SN Modification procedure to include some prepared PSCells (within the candidate cells suggested by the source SN in SN initiated inter-SN CPC or SN initiated inter-SN subsequent CPAC) or to remove some prepared PSCells, the MN may decide to trigger the step 2 towards the source SN. + +- 2/3. The MN initiated SN Modification procedure may be triggered by *SN Modification Required* message, e.g. when an SN security key change needs to be applied. + +NOTE 3: For SN terminated bearers to be setup for which PDCP duplication with CA is configured in NR MCG side, the SN allocates up to 4 separate Xn-U bearers and the MN provides a logical channel ID for primary or split secondary path to the SN via the nested MN-initiated SN modification procedure. + +4. The MN sends the MN RRC reconfiguration message to the UE including the SN RRC reconfiguration message with the new SCG radio resource configuration. + 5. The UE applies the new configuration and sends the MN RRC reconfiguration complete message, including an SN RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. + 6. Upon successful completion of the reconfiguration, the success of the procedure is indicated in the *SN Modification Confirm* message including the SN RRC response message, if received from the UE. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the *SN Modification Confirm* message may contain the *QMC Coordination Response* IE. + 7. If instructed, the UE performs synchronisation towards the PSCell configured by the SN as described in SN Addition procedure. Otherwise, the UE may perform UL transmission directly after having applied the new configuration. + 8. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN Status Transfer takes place between the MN and the SN (Figure 10.3.2-2 depicts the case where a bearer context is transferred from the SN to the MN). + 9. If applicable, data forwarding between MN and the SN takes place (Figure 10.3.2-2 depicts the case where a user plane resource configuration related context is transferred from the SN to the MN). + 10. The SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. +- NOTE 4: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. +11. If applicable, a PDU Session path update procedure is performed. + +#### SN initiated SN Modification without MN involvement + +This procedure is not supported for NE-DC. + +![Sequence diagram for SN initiated SN modification without MN involvement. The diagram shows three entities: UE, SN, and MN. The interaction is as follows: 1. SN sends an 'SN RRC reconfiguration message' to the UE. 2. UE sends an 'SN RRC reconfiguration complete message' to the SN. 3. A 'Random access procedure' is performed between the UE and the SN, indicated by a dashed double-headed arrow.](a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SN + participant MN + Note left of UE: SN initiated SN modification without MN involvement + SN->>UE: 1. SN RRC reconfiguration message + UE->>SN: 2. SN RRC reconfiguration complete message + UE-->>SN: 3. Random access procedure + +``` + +Sequence diagram for SN initiated SN modification without MN involvement. The diagram shows three entities: UE, SN, and MN. The interaction is as follows: 1. SN sends an 'SN RRC reconfiguration message' to the UE. 2. UE sends an 'SN RRC reconfiguration complete message' to the SN. 3. A 'Random access procedure' is performed between the UE and the SN, indicated by a dashed double-headed arrow. + +Figure 10.3.2-3: SN Modification – SN initiated without MN involvement + +The SN initiated SN modification procedure without MN involvement is used to modify the configuration within SN in case no coordination with MN is required, including the addition/modification/release of SCG SCell and PSCell change (e.g. when the security key does not need to be changed and the MN does not need to be involved in PDCP recovery). The SN may initiate the procedure to configure, modify or release intra-SN CPC or intra-SN subsequent CPAC configuration within the same SN. The SN may initiate the procedure to configure, modify or release intra-SN SCG LTM configuration within the same SN. Figure 10.3.2-3 shows an example signalling flow for SN initiated SN + +modification procedure without MN involvement. The SN can decide whether the Random Access procedure is required. + +1. The SN sends the SN RRC reconfiguration message to the UE through SRB3. +2. The UE applies the new configuration and replies with the SN RRC reconfiguration complete message. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. +3. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SN Addition procedure. Otherwise the UE may perform UL transmission after having applied the new configuration. + +#### **SN initiated Conditional SN Modification without MN involvement (SRB3 is used)** + +This procedure is not supported for NE-DC and NGEN-DC. + +![Sequence diagram for SN-initiated Conditional SN Modification without MN involvement. The diagram shows four steps between the UE and the SN: 1. RRC Reconfiguration message (containing CPC configuration or subsequent CPAC configuration) from SN to UE; 2. RRC Reconfiguration Complete message (CPC configuration or subsequent CPAC configuration) from UE to SN; 3. Random access procedure from UE to SN; 4. RRC Reconfiguration Complete message (CPC execution) from UE to SN. The MN is shown but not involved in the message exchange.](fd76efce549d3713543bb5ed9b023c2e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SN + participant MN + Note left of UE: + SN->>UE: 1. RRC Reconfiguration message (containing CPC configuration or subsequent CPAC configuration) + UE-->>SN: 2. RRC Reconfiguration Complete message (CPC configuration or subsequent CPAC configuration) + Note left of UE: + UE->>SN: 3. Random access procedure + UE-->>SN: 4. RRC Reconfiguration Complete message (CPC execution) + Note right of UE: + +``` + +Sequence diagram for SN-initiated Conditional SN Modification without MN involvement. The diagram shows four steps between the UE and the SN: 1. RRC Reconfiguration message (containing CPC configuration or subsequent CPAC configuration) from SN to UE; 2. RRC Reconfiguration Complete message (CPC configuration or subsequent CPAC configuration) from UE to SN; 3. Random access procedure from UE to SN; 4. RRC Reconfiguration Complete message (CPC execution) from UE to SN. The MN is shown but not involved in the message exchange. + +**Figure 10.3.2-3a: SN Modification – SN-initiated without MN involvement and SRB3 is used to configure intra-SN CPC or intra-SN subsequent CPAC.** + +The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is used to configure intra-SN CPC or intra-SN subsequent CPAC. + +1. The SN sends the SN RRC reconfiguration including CPC configuration or subsequent CPAC configuration to the UE through SRB3. +2. The UE applies the new configuration. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. The UE starts evaluating the execution conditions for the candidate PSCell(s). The UE maintains connection with the source PSCell and replies with the *RRReconfigurationComplete* message to the SN via SRB3. +3. If at least one candidate PSCell satisfies the corresponding execution condition, the UE detaches from the source PSCell, applies the stored configuration corresponding to the selected candidate PSCell and synchronises to the candidate PSCell. In subsequent CPAC, the UE keeps the configured subsequent CPAC configuration and evaluates the execution conditions of other candidate PSCells after completion of the subsequent CPAC execution. +4. The UE completes the CPC execution procedure by sending an *RRReconfigurationComplete* message to the new PSCell. + +NOTE 5: For a subsequent CPAC configuration, after a PSCell change, if the execution condition of one candidate PSCell is satisfied, the UE executes steps 3-4, e.g. based on the configuration provided in step 1. + +#### **SN initiated SCG LTM without MN involvement (SRB3 is used)** + +This procedure is not supported for NE-DC and NGEN-DC. + +![Sequence diagram for SN Modification – SN-initiated without MN involvement and SRB3 is used to configure intra-SN SCG LTM. The diagram shows interactions between UE, SN, and MN. The SN sends an RRC Reconfiguration message to the UE. The UE responds with an RRC Reconfiguration Complete message. The SN then indicates DL and UL synchronization with candidate cells. The UE sends an L1 measurement report. The SN sends a Cell switch command (MAC CE). The UE performs a RACH procedure. Finally, the UE sends an RRC Reconfiguration Complete message (SCG LTM execution) to the SN.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SN + participant MN + Note right of SN: 1. RRC Reconfiguration message (containing SCG LTM configuration) + SN->>UE: 1. RRC Reconfiguration message (containing SCG LTM configuration) + Note left of UE: 2. RRC Reconfiguration Complete message + UE->>SN: 2. RRC Reconfiguration Complete message + Note right of SN: 3a. DL synchronization with candidate cells + Note right of SN: 3b. UL synchronization with candidate cells + Note left of UE: 4. L1 measurement report + UE->>SN: 4. L1 measurement report + Note right of SN: 5. Cell switch command (MAC CE) + SN->>UE: 5. Cell switch command (MAC CE) + Note right of SN: 6. RACH procedure + Note left of UE: 7. RRC Reconfiguration Complete message (SCG LTM execution) + UE->>SN: 7. RRC Reconfiguration Complete message (SCG LTM execution) + +``` + +Sequence diagram for SN Modification – SN-initiated without MN involvement and SRB3 is used to configure intra-SN SCG LTM. The diagram shows interactions between UE, SN, and MN. The SN sends an RRC Reconfiguration message to the UE. The UE responds with an RRC Reconfiguration Complete message. The SN then indicates DL and UL synchronization with candidate cells. The UE sends an L1 measurement report. The SN sends a Cell switch command (MAC CE). The UE performs a RACH procedure. Finally, the UE sends an RRC Reconfiguration Complete message (SCG LTM execution) to the SN. + +**Figure 10.3.2-3b: SN Modification – SN-initiated without MN involvement and SRB3 is used to configure intra-SN SCG LTM** + +The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is used to configure intra-SN SCG LTM. + +1. The SN sends the SN *RRReconfiguration* including SCG LTM configuration to the UE through SRB3. +2. The UE stores the SCG LTM candidate cell configurations and transmits an *RRReconfigurationComplete* message to the SN. +- 3a. If indicated by the SN, the UE performs DL synchronization with candidate cell(s) before receiving the cell switch command. +- 3b. If indicated by the SN, the UE performs early TA acquisition with candidate cell(s) before receiving the cell switch command as specified in clause in 9.2.3.5.2 in TS 38.300 [3]. +4. The UE performs L1 measurements on the configured candidate cell(s) and transmits L1 measurement reports to the SN, according to the L1 measurement configuration in *RRReconfiguration* received in step 1. The UE starts to perform L1 measurements once the L1 measurement configuration is applicable. +5. The SN decides to execute cell switch to a target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by candidate configuration index. +6. The UE performs the random access procedure towards the target cell, if the UE does not have valid TA of the target cell. +7. The UE completes the SCG LTM cell switch procedure by sending *RRReconfigurationComplete* message to target cell. If the UE has performed a RA procedure in step 6 the UE considers that LTM execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM execution is successfully completed when the UE determines that the target cell has successfully received its first UL data, as specified in clause in 9.2.3.5.2 in TS 38.300 [3]. + +NOTE 6: The steps 3-7 can be performed multiple times for subsequent SCG LTM using the SCG LTM candidate configuration(s) provided in step 1. + +##### **Transfer of an NR RRC message to/from the UE (when SRB3 is not used)** + +This procedure is supported for all the MR-DC options. + +![Sequence diagram for Figure 10.3.2-4: Transfer of an NR RRC message to/from the UE. The diagram shows five steps: 1. SN to MN: SN Modification Required; 2. MN to UE: RRC reconfiguration message; 3. UE to MN: RRC reconfiguration complete message; 4. MN to SN: SN Modification Confirm; 5. UE to SN: Random Access Procedure (dashed line).](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant SN + participant MN + participant UE + Note left of SN: 1. SN Modification Required + SN->>MN: 1. SN Modification Required + Note left of MN: 2. RRC reconfiguration message + MN->>UE: 2. RRC reconfiguration message + Note left of UE: 3. RRC reconfiguration complete message + UE->>MN: 3. RRC reconfiguration complete message + Note left of MN: 4. SN Modification Confirm + MN->>SN: 4. SN Modification Confirm + Note left of UE: 5. Random Access Procedure + UE-->>SN: 5. Random Access Procedure + +``` + +Sequence diagram for Figure 10.3.2-4: Transfer of an NR RRC message to/from the UE. The diagram shows five steps: 1. SN to MN: SN Modification Required; 2. MN to UE: RRC reconfiguration message; 3. UE to MN: RRC reconfiguration complete message; 4. MN to SN: SN Modification Confirm; 5. UE to SN: Random Access Procedure (dashed line). + +**Figure 10.3.2-4: Transfer of an NR RRC message to/from the UE** + +The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used. + +1. The SN initiates the procedure by sending the *SN Modification Required* to the MN including the SN RRC reconfiguration message. +2. The MN forwards the SN RRC reconfiguration message to the UE including it in the RRC reconfiguration message. +3. The UE applies the new configuration and replies with the RRC reconfiguration complete message by including the SN RRC reconfiguration complete message. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. +4. The MN forwards the SN RRC response message, if received from the UE, to the SN by including it in the *SN Modification Confirm* message. +5. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SN Addition procedure. Otherwise the UE may perform UL transmission after having applied the new configuration. + +#### **SN initiated Conditional SN Modification without MN involvement (SRB3 is not used)** + +This procedure is not supported for NE-DC and NGEN-DC. + +![Sequence diagram for Figure 10.3.2-5: SN Modification – SN-initiated without MN involvement and SRB3 is not used to configure intra-SN CPC or intra-SN subsequent CPAC. The diagram shows seven steps: 1. SN to MN: SN Modification Required; 2. MN to UE: RRC reconfiguration message; 3. UE to MN: RRC reconfiguration complete message; 4. MN to SN: SN Modification Confirm; 5. UE to SN: UL InformationTransferMRDC (CPC execution); 6. MN to SN: RRC Transfer; 7. UE to SN: Random Access Procedure (dashed line).](9e9104f9ba7eec1259a7893c6380ca1b_img.jpg) + +``` + +sequenceDiagram + participant SN + participant MN + participant UE + Note left of SN: 1. SN Modification Required + SN->>MN: 1. SN Modification Required + Note left of MN: 2. RRC reconfiguration message + MN->>UE: 2. RRC reconfiguration message + Note left of UE: 3. RRC reconfiguration complete message + UE->>MN: 3. RRC reconfiguration complete message + Note left of MN: 4. SN Modification Confirm + MN->>SN: 4. SN Modification Confirm + Note left of UE: 5. UL InformationTransferMRDC (CPC execution) + UE->>SN: 5. UL InformationTransferMRDC (CPC execution) + Note left of MN: 6. RRC Transfer + MN->>SN: 6. RRC Transfer + Note left of UE: 7. Random Access Procedure + UE-->>SN: 7. Random Access Procedure + +``` + +Sequence diagram for Figure 10.3.2-5: SN Modification – SN-initiated without MN involvement and SRB3 is not used to configure intra-SN CPC or intra-SN subsequent CPAC. The diagram shows seven steps: 1. SN to MN: SN Modification Required; 2. MN to UE: RRC reconfiguration message; 3. UE to MN: RRC reconfiguration complete message; 4. MN to SN: SN Modification Confirm; 5. UE to SN: UL InformationTransferMRDC (CPC execution); 6. MN to SN: RRC Transfer; 7. UE to SN: Random Access Procedure (dashed line). + +**Figure 10.3.2-5: SN Modification – SN-initiated without MN involvement and SRB3 is not used to configure intra-SN CPC or intra-SN subsequent CPAC** + +The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used to configure intra-SN CPC or intra-SN subsequent CPAC. + +1. The SN initiates the procedure by sending the *SN Modification Required* to the MN including the SN RRC reconfiguration message with CPC configuration or subsequent CPAC configuration. + +2. The MN forwards the SN RRC reconfiguration message to the UE including it in the *RRCReconfiguration* message. +3. The UE replies with the *RRCReconfigurationComplete* message by including the SN RRC reconfiguration complete message. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. The UE maintains connection with source PSCell after receiving CPC configuration or subsequent CPAC configuration, and starts evaluating the execution conditions for the candidate PSCell(s). +4. The MN forwards the SN RRC response message, if received from the UE, to the SN by including it in the *SN Modification Confirm* message. +5. If at least one candidate PSCell satisfies the corresponding execution condition, the UE completes the CPC execution procedure by an *ULInformationTransferMRDC* message to the MN which includes an embedded *RRCReconfigurationComplete* message to the selected target PSCell. In subsequent CPAC, the UE keeps the configured subsequent CPAC configuration and evaluates the execution conditions of other candidate PSCells after completion of the subsequent CPAC execution. +6. The *RRCReconfigurationComplete* message is forwarded to the SN embedded in *RRC Transfer* message. +7. The UE detaches from the source PSCell, applies the stored corresponding configuration and synchronises to the selected candidate PSCell. + +NOTE 7: For a subsequent CPAC configuration, after a PSCell change, if the execution condition of one candidate PSCell is satisfied, the UE executes steps 5-7, e.g. based on the configuration provided in step 2. + +#### SN initiated SCG LTM without MN involvement (SRB3 is not used) + +This procedure is not supported for NE-DC and NGEN-DC. + +![Sequence diagram for SN-initiated SCG LTM without MN involvement. The diagram shows interactions between UE, MN, SN, UPF, and AMF. The SN initiates the procedure by sending an SN Modification Required message to the MN. The MN then sends an RRC reconfiguration message (containing SCG LTM configuration) to the UE. The UE responds with an RRC reconfiguration complete message. The MN then sends an SN Modification Confirm message to the SN. The UE then performs DL and UL synchronization with candidate cells, followed by an L1 measurement report. The SN then sends a cell switch command (MAC CE) to the UE. The UE completes the SCG LTM execution with an UL InformationTransferMRDC message. The MN then sends an RRC Transfer message to the SN. The UE then performs a RACH procedure and finally completes the SCG LTM.](458fdbcb4015a4ee90bd84809afc4aac_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + + Note right of SN: 1. SN Modification Required + SN->>MN: 1. SN Modification Required + Note right of MN: 2. RRC reconfiguration message (containing SCG LTM configuration) + MN->>UE: 2. RRC reconfiguration message (containing SCG LTM configuration) + Note right of UE: 3. RRC reconfiguration complete message + UE->>MN: 3. RRC reconfiguration complete message + Note right of MN: 4. SN Modification Confirm + MN->>SN: 4. SN Modification Confirm + + Note right of UE: 5a. DL synchronization with candidate cells + Note right of UE: 5b. UL synchronization with candidate cells + Note right of UE: 6. L1 measurement report + UE->>SN: 6. L1 measurement report + Note right of SN: 7. Cell switch command (MAC CE) + SN->>UE: 7. Cell switch command (MAC CE) + Note right of UE: 8. UL InformationTransferMRDC (SCG LTM execution) + UE->>MN: 8. UL InformationTransferMRDC (SCG LTM execution) + Note right of MN: 9. RRC Transfer + MN->>SN: 9. RRC Transfer + + Note right of UE: 10. RACH procedure + Note right of UE: 11. SCG LTM completion + +``` + +Sequence diagram for SN-initiated SCG LTM without MN involvement. The diagram shows interactions between UE, MN, SN, UPF, and AMF. The SN initiates the procedure by sending an SN Modification Required message to the MN. The MN then sends an RRC reconfiguration message (containing SCG LTM configuration) to the UE. The UE responds with an RRC reconfiguration complete message. The MN then sends an SN Modification Confirm message to the SN. The UE then performs DL and UL synchronization with candidate cells, followed by an L1 measurement report. The SN then sends a cell switch command (MAC CE) to the UE. The UE completes the SCG LTM execution with an UL InformationTransferMRDC message. The MN then sends an RRC Transfer message to the SN. The UE then performs a RACH procedure and finally completes the SCG LTM. + +**Figure 10.3.2-6: SN Modification – SN-initiated without MN involvement and SRB3 is not used to configure intra-SN SCG LTM** + +The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used to configure intra-SN SCG LTM. + +1. The SN initiates the procedure by sending the *SN Modification Required* to the MN including the SN *RRCReconfiguration* message with SCG LTM configuration. + +2. The MN forwards the SN *RRCREconfiguration* message to the UE including it in the *RRCREconfiguration* message. +3. The UE replies with the *RRCREconfigurationComplete* message by including the SN *RRCREconfigurationComplete* message. +4. The MN forwards the SN RRC response message, if received from the UE, to the SN by including it in the *SN Modification Confirm* message. +- 5a. If indicated by the SN, the UE performs DL synchronization with candidate cell(s) before receiving the cell switch command. +- 5b. If indicated by the SN, the UE performs early TA acquisition with candidate cell(s) before receiving the cell switch command as specified in clause 9.2.3.5.2 in TS 38.300 [3]. +6. The UE performs L1 measurements on the configured candidate cell(s) and transmits L1 measurement reports to the SN, according to the L1 measurement configuration in *RRCREconfiguration* received in step 2. The UE starts to perform L1 measurements once the L1 measurement configuration is applicable. +7. The SN decides to execute cell switch to a target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by candidate configuration index. +8. The UE sends an *ULInformationTransferMRDC* message to the MN which includes an embedded *RRCREconfigurationComplete* message to the target cell. +9. The *RRCREconfigurationComplete* message is forwarded to the SN embedded in *RRCTransfer* message. +10. The UE performs the random access procedure towards the target cell, if the UE does not have valid TA of the target cell. +11. The UE completes the SCG LTM cell switch procedure by sending an UL transmission to target cell. If the UE has performed a RA procedure in step 10 the UE considers that LTM execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM execution is successfully completed when the UE determines that the SN has successfully received its first UL transmission, as specified in clause 9.2.3.5.2 in TS 38.300 [3]. + +NOTE 8: The steps 5-11 can be performed multiple times for subsequent SCG LTM using the SCG LTM candidate configuration(s) provided in step 2. + +## 10.4 Secondary Node Release (MN/SN initiated) + +### 10.4.1 EN-DC + +The Secondary Node Release procedure may be initiated either by the MN or by the SN and is used to initiate the release of the UE context at the SN. The recipient node of this request can reject it, e.g., if a SN change procedure is triggered by the SN. + +In case of CPA or inter-SN CPC, this procedure may be initiated either by the MN or the candidate SN, and it is used to cancel all the prepared PSCells at the candidate SN and initiate the release of related UE context at the candidate SN. + +It does not necessarily need to involve signalling towards the UE, e.g., in case of the RRC connection re-establishment due to Radio Link Failure in MN. + +#### MN initiated SN Release + +![Sequence diagram of SN Release procedure – MN initiated. The diagram shows five lifelines: UE, MN, SN, S-GW, and MME. The procedure starts with the MN sending a '1. SgNB Release Request' to the SN. The SN responds with '2. SgNB Release Request Acknowledge'. The MN then sends '3. RRCConnectionReconfiguration' to the UE, which replies with '4. RRCConnectionReconfigurationComplete'. The SN sends '5. SN Status Transfer' to the MN. A dashed green line labeled '6. Data Forwarding' shows data being forwarded from the SN to the S-GW. The SN sends '7. Secondary RAT Data Usage Report' to the MN. A blue box labeled '8. Path Update procedure' spans across the MN, SN, S-GW, and MME lifelines. Finally, the MN sends '9. UE Context Release' to the SN.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + + Note right of MN: 1. SgNB Release Request + MN->>SN: 1. SgNB Release Request + Note right of SN: 2. SgNB Release Request Acknowledge + SN-->>MN: 2. SgNB Release Request Acknowledge + Note right of MN: 3. RRCConnectionReconfiguration + MN-->>UE: 3. RRCConnectionReconfiguration + Note right of UE: 4. RRCConnectionReconfigurationComplete + UE-->>MN: 4. RRCConnectionReconfigurationComplete + Note right of SN: 5. SN Status Transfer + SN-->>MN: 5. SN Status Transfer + Note right of SN: 6. Data Forwarding + SN-->>S-GW: 6. Data Forwarding + Note right of SN: 7. Secondary RAT Data Usage Report + SN-->>MN: 7. Secondary RAT Data Usage Report + Note right of MN: 8. Path Update procedure + MN->>SN: 9. UE Context Release + +``` + +Sequence diagram of SN Release procedure – MN initiated. The diagram shows five lifelines: UE, MN, SN, S-GW, and MME. The procedure starts with the MN sending a '1. SgNB Release Request' to the SN. The SN responds with '2. SgNB Release Request Acknowledge'. The MN then sends '3. RRCConnectionReconfiguration' to the UE, which replies with '4. RRCConnectionReconfigurationComplete'. The SN sends '5. SN Status Transfer' to the MN. A dashed green line labeled '6. Data Forwarding' shows data being forwarded from the SN to the S-GW. The SN sends '7. Secondary RAT Data Usage Report' to the MN. A blue box labeled '8. Path Update procedure' spans across the MN, SN, S-GW, and MME lifelines. Finally, the MN sends '9. UE Context Release' to the SN. + +**Figure 10.4.1-1: SN Release procedure – MN initiated** + +Figure 10.4.1-1 shows an example signalling flow for the MN initiated Secondary Node Release procedure when SN Release is confirmed by SN. + +1. The MN initiates the procedure by sending the *SgNB Release Request* message. If applicable, the MN provides data forwarding addresses to the SN. +2. The SN confirms SN Release by sending the *SgNB Release Request Acknowledge* message. If appropriate, the SN may reject SN Release, e.g. if the SN change procedure is triggered by the SN. + +NOTE 0: If CPA or inter-SN CPC is configured, upon reception of the *SgNB Release Request Acknowledge* message the MN cancels all CPAC with the target candidate SN(s). + +- 3/4. If required, the MN indicates in the *RRCConnectionReconfiguration* message towards the UE that the UE shall release the entire SCG configuration. In case the UE is unable to comply with (part of) the configuration included in the *RRCConnectionReconfiguration* message, it performs the reconfiguration failure procedure. + +NOTE 1: If data forwarding is applied, timely coordination between steps 1 and 2 may minimize gaps in service provision, this is however regarded to be an implementation matter. + +5. For bearers using RLC AM, the SN sends the *SN Status Transfer* message. +6. Data forwarding from the SN to the MN may start. +7. The SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. + +NOTE 2: If data forwarding is applied, the order the SN sends the *Secondary RAT Data Usage Report* message and starts data forwarding with MN is not defined i.e., step 7 can take place before step 6. The SN does not need to wait for the end of data forwarding to send the *Secondary RAT Data Usage Report* message. + +8. If applicable, the path update procedure is initiated. +9. Upon reception of the *UE Context Release* message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +#### SN initiated SN Release + +![Sequence diagram of the SN Release procedure – SN initiated. The diagram shows five lifelines: UE, MN, SN, S-GW, and MME. The procedure starts with the SN sending an SgNB Release Required message to the MN. The MN responds with an SgNB Release Confirm. The MN then sends an RRCConnectionReconfiguration message to the UE, which the UE completes with RRCConnectionReconfigurationComplete. The SN sends an SN Status Transfer to the MN. Data forwarding begins from the SN to the MN. The SN sends a Secondary RAT Data Usage report to the MN. A Path Update procedure is initiated between the MN and the MME. Finally, the MN sends a UE Context Release message to the SN.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + + Note right of SN: 1. SgNB Release Required + SN->>MN: 1. SgNB Release Required + Note right of MN: 2. SgNB Release Confirm + MN->>SN: 2. SgNB Release Confirm + Note right of MN: 3. RRCConnectionReconfiguration + MN->>UE: 3. RRCConnectionReconfiguration + Note right of UE: 4. RRCConnectionReconfigurationComplete + UE-->>MN: 4. RRCConnectionReconfigurationComplete + Note right of SN: 5. SN Status Transfer + SN->>MN: 5. SN Status Transfer + Note right of SN: 6. Data Forwarding + SN-->>MN: 6. Data Forwarding + Note right of SN: 7. Secondary RAT Data Usage report + SN->>MN: 7. Secondary RAT Data Usage report + Note right of MN: 8. Path Update procedure + MN->>MME: 8. Path Update procedure + Note right of MN: 9. UE Context Release + MN->>SN: 9. UE Context Release + +``` + +Sequence diagram of the SN Release procedure – SN initiated. The diagram shows five lifelines: UE, MN, SN, S-GW, and MME. The procedure starts with the SN sending an SgNB Release Required message to the MN. The MN responds with an SgNB Release Confirm. The MN then sends an RRCConnectionReconfiguration message to the UE, which the UE completes with RRCConnectionReconfigurationComplete. The SN sends an SN Status Transfer to the MN. Data forwarding begins from the SN to the MN. The SN sends a Secondary RAT Data Usage report to the MN. A Path Update procedure is initiated between the MN and the MME. Finally, the MN sends a UE Context Release message to the SN. + +**Figure 10.4.1-2: SN Release procedure – SN initiated** + +Figure 10.4.1-2 shows an example signalling flow for the SN initiated Secondary Node Release procedure. + +1. The SN initiates the procedure by sending the *SgNB Release Required* message which may contain inter-node message to support delta configuration. +2. If applicable, the MN provides data forwarding addresses to the SN in the *SgNB Release Confirm* message. The SN may start data forwarding and stop providing user data to the UE as early as it receives the *SgNB Release Confirm* message. + +NOTE 2a: If CPA or inter-SN CPC is configured, upon reception of the *SgNB Release Required* message the MN cancels all CPAC with the target candidate SN(s). + +- 3/4. If required, the MN indicates in the *RRCConnectionReconfiguration* message towards the UE that the UE shall release the entire SCG configuration. In case the UE is unable to comply with (part of) the configuration included in the *RRCConnectionReconfiguration* message, it performs the reconfiguration failure procedure. + +NOTE 3: If data forwarding is applied, timely coordination between steps 2 and 3 may minimize gaps in service provision. This is however regarded to be an implementation matter. + +5. For bearers using RLC AM, the SN sends the *SN Status Transfer* message. + +6. Data forwarding from the SN to the MN may start. + +7. The SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. + +NOTE 4: If data forwarding is applied, the order the SN sends the *Secondary RAT Data Usage Report* message and starts data forwarding with MN is not defined i.e., step 7 can take place before step 6. The SN does not need to wait for the end of data forwarding to send the *Secondary RAT Data Usage Report* message. + +8. If applicable, the path update procedure is initiated. + +9. Upon reception of the *UE Context Release* message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +### 10.4.2 MR-DC with 5GC + +The SN Release procedure may be initiated either by the MN or by the SN and is used to initiate the release of the UE context and relevant resources at the SN. The recipient node of this request can reject it, e.g., if an SN change procedure is triggered by the SN. + +In case of CPA, inter-SN CPC or inter-SN subsequent CPAC, this procedure may be initiated either by the MN or the candidate SN, and it is used to cancel all the prepared PSCells at the candidate SN and initiate the release of related UE context at the candidate SN. + +#### MN initiated SN Release + +![Sequence diagram of the SN release procedure initiated by the MN. The diagram shows interactions between UE, MN, SN, UPF, and AMF. The MN sends an SN Release Request to the SN. The SN responds with an SN Release Request Acknowledge and an Xn-U Address Indication. The MN then sends an RRC reconfiguration to the UE, which completes it. The MN sends an SN Status Transfer to the SN. The SN starts data forwarding to the MN and sends a Secondary RAT Data Usage Report. A dashed box indicates the PDU Session Path Update procedure between the MN, UPF, and AMF. Finally, the MN sends a UE Context Release to the SN.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + + Note left of UE: 3. RRC reconfiguration + Note left of UE: 4. RRC reconfiguration complete + + MN->>SN: 1. SN Release Request + SN-->>MN: 2. SN Release Request Acknowledge + MN->>SN: 2a. Xn-U Address Indication + MN-->>UE: 3. RRC reconfiguration + UE-->>MN: 4. RRC reconfiguration complete + MN->>SN: 5. SN Status Transfer + Note right of SN: 6. Data Forwarding + SN-->>MN: 7. Secondary RAT Data Usage Report + Note right of MN: 8. PDU Session Path Update procedure + MN->>SN: 9. UE Context Release + +``` + +Sequence diagram of the SN release procedure initiated by the MN. The diagram shows interactions between UE, MN, SN, UPF, and AMF. The MN sends an SN Release Request to the SN. The SN responds with an SN Release Request Acknowledge and an Xn-U Address Indication. The MN then sends an RRC reconfiguration to the UE, which completes it. The MN sends an SN Status Transfer to the SN. The SN starts data forwarding to the MN and sends a Secondary RAT Data Usage Report. A dashed box indicates the PDU Session Path Update procedure between the MN, UPF, and AMF. Finally, the MN sends a UE Context Release to the SN. + +**Figure 10.4.2-1: SN release procedure - MN initiated** + +Figure 10.4.2-1 shows an example signalling flow for the MN initiated SN Release procedure. + +1. The MN initiates the procedure by sending the *SN Release Request* message. +2. The SN confirms SN Release by sending the *SN Release Request Acknowledge* message. If appropriate, the SN may reject SN Release, e.g., if the SN change procedure is triggered by the SN. + +NOTE 00: If CPA or inter-SN CPC is configured, upon reception of the *SN Release Request Acknowledge* message the MN cancels all CPAC with the target candidate SN(s). + +NOTE 00a: If subsequent CPAC is configured, upon reception of the *SN Release Acknowledge* message from the source SN, the MN may retain the subsequent CPAC configuration or cancel the subsequent CPAC configuration. If the MN maintains the subsequent CPAC configuration, it should provide suitable execution conditions for the evaluation of the subsequent CPAC. + +- 2a. When applicable, the MN provides forwarding address information to the SN. + +NOTE 0: The MN may send the *Xn-U Address Indication* message to provide forwarding address information before step 2. + +- 3/4. If required, the MN indicates in the MN RRC reconfiguration message towards the UE that the UE shall release the entire SCG configuration. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. + +NOTE 1: If data forwarding is applied, timely coordination between steps 1 and 2 may minimize gaps in service provision, this is however regarded to be an implementation matter. + +5. If PDCP termination point is changed to the MN for bearers using RLC AM, the SN sends the *SN Status Transfer* message. + +6. Data forwarding from the SN to the MN may start. + +7. The SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. + +NOTE 1a: If data forwarding is applied, the order the SN sends the *Secondary RAT Data Usage Report* message and starts data forwarding with MN is not defined i.e., step 7 can take place before step 6. The SN does not need to wait for the end of data forwarding to send the *Secondary RAT Data Usage Report* message. + +8. If applicable, the PDU Session path update procedure is initiated. + +9. Upon reception of the *UE Context Release* message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +#### SN initiated SN Release + +![Sequence diagram of the SN initiated SN release procedure. The diagram shows five entities: UE, MN, SN, UPF, and AMF. The sequence of messages is: 1. SN to MN: SN Release Required; 2. MN to SN: SN Release Confirm; 3. MN to UE: RRC reconfiguration; 4. UE to MN: RRC reconfiguration complete; 5. SN to MN: SN Status Transfer; 6. SN to UPF: Data Forwarding (dashed green line); 7. SN to MN: Secondary RAT Data Usage report; 8. MN to AMF: PDU Session Path Update procedure (dashed blue line); 9. MN to SN: UE Context Release.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant SN + participant MN + participant UE + participant UPF + participant AMF + Note left of SN: SN initiated SN release procedure + SN->>MN: 1. SN Release Required + MN-->>SN: 2. SN Release Confirm + MN->>UE: 3. RRC reconfiguration + UE-->>MN: 4. RRC reconfiguration complete + SN-->>MN: 5. SN Status Transfer + Note right of SN: Data Forwarding + SN-->>UPF: 6. Data Forwarding + SN->>MN: 7. Secondary RAT Data Usage report + Note right of MN: PDU Session Path Update procedure + MN-->>AMF: 8. PDU Session Path Update procedure + MN->>SN: 9. UE Context Release + +``` + +Sequence diagram of the SN initiated SN release procedure. The diagram shows five entities: UE, MN, SN, UPF, and AMF. The sequence of messages is: 1. SN to MN: SN Release Required; 2. MN to SN: SN Release Confirm; 3. MN to UE: RRC reconfiguration; 4. UE to MN: RRC reconfiguration complete; 5. SN to MN: SN Status Transfer; 6. SN to UPF: Data Forwarding (dashed green line); 7. SN to MN: Secondary RAT Data Usage report; 8. MN to AMF: PDU Session Path Update procedure (dashed blue line); 9. MN to SN: UE Context Release. + +**Figure 10.4.2-2: SN release procedure - SN initiated** + +Figure 10.4.2-2 shows an example signalling flow for the SN initiated SN Release procedure. + +1. The SN initiates the procedure by sending the *SN Release Required* message which may contain inter-node message to support delta configuration. +2. If data forwarding is requested, the MN provides data forwarding addresses to the SN in the *SN Release Confirm* message. The SN may start data forwarding and stop providing user data to the UE as early as it receives the *SN Release Confirm* message. + +NOTE 1b: If CPA or inter-SN CPC is configured, upon reception of the *SN Release Required* message the MN cancels all CPAC with the target candidate SN(s). + +NOTE 1c: If subsequent CPAC is configured, upon reception of the *SN Release Required* message from the source SN, the MN may retain the subsequent CPAC configuration or cancel the subsequent CPAC configuration. If the MN maintains the subsequent CPAC configuration, it should provide suitable execution conditions for the evaluation of the subsequent CPAC. + +- 3/4. If required, the MN indicates in the MN RRC reconfiguration message towards the UE that the UE shall release the entire SCG configuration. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. + +NOTE 2: If data forwarding is applied, timely coordination between steps 2 and 3 may minimize gaps in service provision. This is however regarded to be an implementation matter. + +5. If PDCP termination point is changed to the MN for bearers using RLC AM, the SN sends the *SN Status Transfer* message. + +6. Data forwarding from the SN to the MN may start. + +7. The SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. + +NOTE 3: If data forwarding is applied, the order the SN sends the *Secondary RAT Data Usage Report* message and starts data forwarding with MN is not defined i.e., step 7 can take place before step 6. The SN does not need to wait for the end of data forwarding to send the *Secondary RAT Data Usage Report* message. + +8. If applicable, the PDU Session path update procedure is initiated. + +9. Upon reception of the *UE Context Release* message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +## 10.5 Secondary Node Change (MN/SN initiated) + +### 10.5.1 EN-DC + +The Secondary Node Change procedure is initiated either by MN or SN and used to transfer a UE context from a source SN to a target SN and to change the SCG configuration in UE from one SN to another. In case of inter-SN CPC, the Conditional Secondary Node Change procedure initiated either by the MN or SN is also used for inter-SN CPC configuration and inter-SN CPC execution. + +NOTE 1: Inter-RAT SN change procedure with single RRC reconfiguration is not supported in this version of the protocol (i.e. no transition from EN-DC to DC). + +The Secondary Node Change procedure always involves signalling over MCG SRB towards the UE. + +#### MN initiated SN Change + +![Sequence diagram for MN initiated SN Change procedure. The diagram shows the interaction between UE, MN, S-SN, T-SN, S-GW, and MME. The procedure starts with the MN sending an SgNB Addition Request to the T-SN. The T-SN responds with an SgNB Addition Request Acknowledge. The MN then sends an SgNB Release Request to the S-SN, which responds with an SgNB Release Request Acknowledge. The MN sends an RRCConnectionReconfiguration to the UE, which responds with an RRCConnectionReconfigurationComplete. The MN then initiates a Random Access Procedure with the UE. The S-SN sends an SN Status Transfer to the T-SN, which responds with an SN Status Transfer. The S-SN then sends a Data Forwarding message to the T-SN. The MN sends a Secondary RAT Data Usage Report to the S-SN. The S-SN sends an E-RAB Modification Indication to the MME, which responds with a Bearer Modification. The S-SN then sends an End Marker Packet to the T-SN. The T-SN sends a New Path message to the S-GW. The S-GW sends an E-RAB Modification Confirm to the MME. Finally, the MN sends a UE Context Release to the S-SN.](30fe9e9487585118063341332e802e98_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant S-SN + participant T-SN + participant S-GW + participant MME + + Note left of MN: 1/2. The MN initiates the SN change by requesting the target SN to allocate resources for the UE by means of the SgNB Addition procedure. The MN may include measurement results related to the target SN. If forwarding is needed, the target SN provides forwarding addresses to the MN. The target SN includes the indication of the full or delta RRC configuration. + + MN->>T-SN: 1. SgNB Addition Request + T-SN-->>MN: 2. SgNB Addition Request Acknowledge + MN->>S-SN: 3a. SgNB Release Request + S-SN-->>MN: 3b. SgNB Release Request Acknowledge + MN->>UE: 4. RRCConnectionReconfiguration + UE-->>MN: 5. RRCConnectionReconfigurationComplete + MN->>UE: 7. Random Access Procedure + S-SN->>T-SN: 8a. SN Status Transfer + T-SN-->>S-SN: 8b. SN Status Transfer + S-SN-->>T-SN: 9. Data Forwarding + MN->>S-SN: 10. Secondary RAT Data Usage Report + S-SN->>MME: 11. E-RAB Modification Indication + MME-->>S-GW: 12. Bearer Modification + S-SN-->>T-SN: 13. End Marker Packet + T-SN-->>S-GW: 14. New Path + S-GW-->>MME: 15. E-RAB Modification Confirm + MN->>S-SN: 16. UE Context Release + +``` + +Sequence diagram for MN initiated SN Change procedure. The diagram shows the interaction between UE, MN, S-SN, T-SN, S-GW, and MME. The procedure starts with the MN sending an SgNB Addition Request to the T-SN. The T-SN responds with an SgNB Addition Request Acknowledge. The MN then sends an SgNB Release Request to the S-SN, which responds with an SgNB Release Request Acknowledge. The MN sends an RRCConnectionReconfiguration to the UE, which responds with an RRCConnectionReconfigurationComplete. The MN then initiates a Random Access Procedure with the UE. The S-SN sends an SN Status Transfer to the T-SN, which responds with an SN Status Transfer. The S-SN then sends a Data Forwarding message to the T-SN. The MN sends a Secondary RAT Data Usage Report to the S-SN. The S-SN sends an E-RAB Modification Indication to the MME, which responds with a Bearer Modification. The S-SN then sends an End Marker Packet to the T-SN. The T-SN sends a New Path message to the S-GW. The S-GW sends an E-RAB Modification Confirm to the MME. Finally, the MN sends a UE Context Release to the S-SN. + +Figure 10.5.1-1: SN Change – MN initiated + +Figure 10.5.1-1 shows an example signalling flow for the MN initiated Secondary Node Change: + +- 1/2. The MN initiates the SN change by requesting the target SN to allocate resources for the UE by means of the SgNB Addition procedure. The MN may include measurement results related to the target SN. If forwarding is needed, the target SN provides forwarding addresses to the MN. The target SN includes the indication of the full or delta RRC configuration. + +NOTE 2: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration before step 1. + +NOTE 2a: In case the target SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. + +3. If the allocation of target SN resources was successful, the MN initiates the release of the source SN resources including a Cause indicating SCG mobility. The Source SN may reject the release. If data forwarding is needed the MN provides data forwarding addresses to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides data forwarding addresses as received from the target SN to source SN. Reception of the *SgNB Release Request* message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. + +- 4/5. The MN triggers the UE to apply the new configuration. The MN indicates to the UE the new configuration in the *RRCConnectionReconfiguration* message including the NR RRC configuration message generated by the target SN. The UE applies the new configuration and sends the *RRCConnectionReconfigurationComplete* message, including the encoded NR RRC response message for the target SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the *RRCConnectionReconfiguration* message, it performs the reconfiguration failure procedure. +6. If the RRC connection reconfiguration procedure was successful, the MN informs the target SN via *SgNBReconfigurationComplete* message with the encoded NR RRC response message for the target SN, if received from the UE. +7. If configured with bearers requiring SCG radio resources, the UE synchronizes to the target SN. +8. For SN terminated bearers using RLC AM, the source SN sends the *SN Status Transfer* message, which the MN sends then to the target SN, if needed. +9. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the *SgNB Release Request* message from the MN. +10. The source SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. +- NOTE 3: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. +- 11-15. If applicable, a path update is triggered by the MN. +16. Upon reception of the *UE Context Release* message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +#### SN initiated SN Change + +![Sequence diagram for SN initiated SN Change. Lifelines: UE, MN, S-SN, T-SN, S-GW, MME. The sequence starts with S-SN sending '1. SgNB Change Required' to MN. MN sends '2. SgNB Addition Request' to T-SN, which responds with '3. SgNB Addition Request Acknowledge'. MN then sends '4. RRCConnectionReconfiguration' to UE, which responds with '5. RRCConnectionReconfigurationComplete'. MN sends '6. SgNB Change Confirm' to S-SN and '7. SgNB Reconfiguration Complete' to T-SN. UE performs '8. Random Access Procedure' with T-SN. MN sends '9a. SN Status Transfer' and '9b. SN Status Transfer' to T-SN. S-SN sends '10. Data Forwarding' (dashed green line) to T-SN and '11. Secondary RAT Data Usage Report' to MN. MN sends '12. E-RAB Modification Indication' to S-GW, which responds with '13. Bearer Modification'. S-SN sends '14. End Marker Packet' (dashed green line) to T-SN. T-SN sends '15. New Path' (dashed green line) to S-GW. MN sends '16. E-RAB Modification Confirm' to S-GW and '17. UE Context Release' to S-SN.](848073118eebfdbfdb9a60e3923fe0b3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant S-SN + participant T-SN + participant S-GW + participant MME + + Note left of UE: 4/5. The MN triggers the UE to apply the new configuration. The MN indicates to the UE the new configuration in the RRCConnectionReconfiguration message including the NR RRC configuration message generated by the target SN. The UE applies the new configuration and sends the RRCConnectionReconfigurationComplete message, including the encoded NR RRC response message for the target SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. + + S-SN->>MN: 1. SgNB Change Required + MN->>T-SN: 2. SgNB Addition Request + T-SN-->>MN: 3. SgNB Addition Request Acknowledge + MN->>UE: 4. RRCConnectionReconfiguration + UE-->>MN: 5. RRCConnectionReconfigurationComplete + MN->>S-SN: 6. SgNB Change Confirm + MN->>T-SN: 7. SgNB Reconfiguration Complete + UE->>T-SN: 8. Random Access Procedure + MN->>T-SN: 9a. SN Status Transfer + MN->>T-SN: 9b. SN Status Transfer + S-SN-->>T-SN: 10. Data Forwarding + S-SN->>MN: 11. Secondary RAT Data Usage Report + MN->>S-GW: 12. E-RAB Modification Indication + S-GW-->>MME: 13. Bearer Modification + S-SN-->>T-SN: 14. End Marker Packet + T-SN-->>S-GW: 15. New Path + MN->>S-GW: 16. E-RAB Modification Confirm + MN->>S-SN: 17. UE Context Release + +``` + +Sequence diagram for SN initiated SN Change. Lifelines: UE, MN, S-SN, T-SN, S-GW, MME. The sequence starts with S-SN sending '1. SgNB Change Required' to MN. MN sends '2. SgNB Addition Request' to T-SN, which responds with '3. SgNB Addition Request Acknowledge'. MN then sends '4. RRCConnectionReconfiguration' to UE, which responds with '5. RRCConnectionReconfigurationComplete'. MN sends '6. SgNB Change Confirm' to S-SN and '7. SgNB Reconfiguration Complete' to T-SN. UE performs '8. Random Access Procedure' with T-SN. MN sends '9a. SN Status Transfer' and '9b. SN Status Transfer' to T-SN. S-SN sends '10. Data Forwarding' (dashed green line) to T-SN and '11. Secondary RAT Data Usage Report' to MN. MN sends '12. E-RAB Modification Indication' to S-GW, which responds with '13. Bearer Modification'. S-SN sends '14. End Marker Packet' (dashed green line) to T-SN. T-SN sends '15. New Path' (dashed green line) to S-GW. MN sends '16. E-RAB Modification Confirm' to S-GW and '17. UE Context Release' to S-SN. + +Figure 10.5.1-2: SN Change – SN initiated + +Figure 10.5.1-2 shows an example signalling flow for the Secondary Node Change initiated by the SN: + +1. The source SN initiates the SN change procedure by sending *SgNB Change Required* message which contains target SN ID information and may include the SCG configuration (to support delta configuration) and measurement results related to the target SN. + +- 2/3. The MN requests the target SN to allocate resources for the UE by means of the SgNB Addition procedure, including the measurement results related to the target SN received from the source SN. If forwarding is needed, the target SN provides forwarding addresses to the MN. The target SN includes the indication of the full or delta RRC configuration. + +NOTE 3a: In case the target SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. + +- 4/5. The MN triggers the UE to apply the new configuration. The MN indicates the new configuration to the UE in the *RRCConnectionReconfiguration* message including the NR RRC configuration message generated by the target SN. The UE applies the new configuration and sends the *RRCConnectionReconfigurationComplete* message, including the encoded NR RRC response message for the target SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the *RRCConnectionReconfiguration* message, it performs the reconfiguration failure procedure. + 6. If the allocation of target SN resources was successful, the MN confirms the release of the source SN resources. If data forwarding is needed the MN provides data forwarding addresses to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides data forwarding addresses as received from the target SN to source SN. Reception of the *SgNB Change Confirm* message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. + 7. If the RRC connection reconfiguration procedure was successful, the MN informs the target SN via *SgNB Reconfiguration Complete* message with the encoded NR RRC response message for the target SN, if received from the UE. + 8. The UE synchronizes to the target SN. + 9. For SN terminated bearers using RLC AM, the source SN sends the *SN Status Transfer* message, which the MN sends then to the target SN, if needed. + 10. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the *SgNB Change Confirm* message from the MN. + 11. The source SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. +- NOTE 4: The order the source SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN/target SN is not defined. The SgNB may send the report when the transmission of the related bearer is stopped. +- 12-16. If applicable, a path update is triggered by the MN. + 17. Upon reception of the *UE Context Release* message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +#### MN initiated conditional SN Change + +The MN initiated conditional inter-SN change procedure is used for inter-SN CPC configuration and inter-SN CPC execution. + +![Sequence diagram for Conditional SN Change – MN initiated. Lifelines: UE, MN, S-SN, T-SN, Other potential T-SN, S-GW, MME. The process involves SgNB Addition Request, RRC Connection Reconfiguration, SgNB Release Request, Random Access Procedure, SN Status Transfer, Data Forwarding, and UE Context Release.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant S-SN + participant T-SN + participant Other potential T-SN + participant S-GW + participant MME + + Note right of MN: 1. SgNB Addition Request + MN->>T-SN: 1. SgNB Addition Request + Note right of MN: 1. SgNB Addition Request + MN->>Other potential T-SN: 1. SgNB Addition Request + Note right of T-SN: 2. SgNB Addition Request Acknowledge + T-SN->>MN: 2. SgNB Addition Request Acknowledge + Note right of Other potential T-SN: 2. SgNB Addition Request Acknowledge + Other potential T-SN->>MN: 2. SgNB Addition Request Acknowledge + Note right of MN: 3. RRCConnectionReconfiguration (containing MN RRCConnectionReconfiguration* containing SN RRCReconfiguration***) + MN->>UE: 3. RRCConnectionReconfiguration (containing MN RRCConnectionReconfiguration* containing SN RRCReconfiguration***) + Note right of UE: 4. RRCConnectionReconfigurationComplete + UE->>MN: 4. RRCConnectionReconfigurationComplete + Note right of MN: 4a. Data Forwarding Address Indication + MN->>S-SN: 4a. Data Forwarding Address Indication + Note right of MN: 5. RRCConnectionReconfigurationComplete* (containing SN RRCReconfigurationComplete***) + MN->>UE: 5. RRCConnectionReconfigurationComplete* (containing SN RRCReconfigurationComplete***) + Note right of UE: 6a. SgNB Release Request + UE->>MN: 6a. SgNB Release Request + Note right of MN: 6b. SgNB Release Request Acknowledge + MN->>UE: 6b. SgNB Release Request Acknowledge + Note right of MN: 7a. SgNB Reconfiguration Complete + MN->>T-SN: 7a. SgNB Reconfiguration Complete + Note right of MN: 7b. SgNB Release Request + MN->>Other potential T-SN: 7b. SgNB Release Request + Note right of Other potential T-SN: 7c. SgNB Release Request Acknowledge + Other potential T-SN->>MN: 7c. SgNB Release Request Acknowledge + Note right of MN: 8. Random Access Procedure + MN->>UE: 8. Random Access Procedure + Note right of MN: 9a. SN Status Transfer + MN->>S-SN: 9a. SN Status Transfer + Note right of MN: 9b. SN Status Transfer + MN->>T-SN: 9b. SN Status Transfer + Note right of S-SN: 10. Data Forwarding + S-SN->>T-SN: 10. Data Forwarding + Note right of MN: 11. Secondary RAT Data Usage Report + MN->>S-SN: 11. Secondary RAT Data Usage Report + Note right of S-SN: 12. E-RAB Modification Indication + S-SN->>MME: 12. E-RAB Modification Indication + Note right of MME: 13. Bearer Modification + MME->>S-GW: 13. Bearer Modification + Note right of S-GW: 14. End Marker Packet + S-GW->>T-SN: 14. End Marker Packet + Note right of T-SN: 15. New Path + T-SN->>S-GW: 15. New Path + Note right of S-GW: 16. E-RAB Modification Confirm + S-GW->>MME: 16. E-RAB Modification Confirm + Note right of MME: 17. UE Context Release + MME->>S-SN: 17. UE Context Release + +``` + +Sequence diagram for Conditional SN Change – MN initiated. Lifelines: UE, MN, S-SN, T-SN, Other potential T-SN, S-GW, MME. The process involves SgNB Addition Request, RRC Connection Reconfiguration, SgNB Release Request, Random Access Procedure, SN Status Transfer, Data Forwarding, and UE Context Release. + +**Figure 10.5.1-3: Conditional SN Change – MN initiated** + +Figure 10.5.1-3 shows an example signalling flow for the MN initiated Conditional Secondary Node Change: + +- 1/2. The MN initiates the conditional SN change by requesting the candidate SN(s) to allocate resources for the UE by means of the SgNB Addition procedure, indicating that the request is for CPAC. The MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN(s) to choose and configure the SCG cell(s), and provides the upper limit for the number of PSCells that can be prepared by the candidate SN. From the measurement results indicated by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR *RRCReconfiguration\*\** message contained in the *SgNB Addition Request Acknowledge* message with the prepared PSCell ID(s). If forwarding is needed, the candidate SN provides forwarding addresses to the MN. The candidate SN includes the indication of the full or delta RRC configuration. The candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. + +NOTE 5: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration before step 1. + +NOTE 5a: In case the candidate SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE in the conditional configuration. + +3. The MN sends to the UE an *RRCConnectionReconfiguration* message including the CPC configuration, i.e. a list of *RRCConnectionReconfiguration\** messages and associated execution conditions, in which each *RRCConnectionReconfiguration\** message contains the SCG configuration in the *RRCReconfiguration\*\** message received from the candidate SN in step 2 and possibly an MCG configuration. Besides, the *RRCConnectionReconfiguration* message can also include an updated MCG configuration, e.g., to configure the required conditional measurements. +4. The UE applies the *RRCConnectionReconfiguration* message received in step 3, stores the CPC configuration and replies to the MN with an *RRCConnectionReconfigurationComplete* message. In case the UE is unable to + +comply with (part of) the configuration included in the *RRConnectionReconfiguration* message, it performs the reconfiguration failure procedure. + +- 4a. Upon receiving the *RRConnectionReconfigurationComplete* message from the UE, the MN triggers the Data Forwarding Address Indication procedure to the source SN to inform that the CPC has been configured, the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. + +NOTE 5b: Separate Data Forwarding Address Indication procedures may be invoked to provide different forwarding addresses of the prepared candidate target SNs. In this case, it is up to the MN and the source SN implementations to make sure that the EARLY STATUS TRANSFER message(s) from the source SN, if any, is forwarded to the right target destination. The Data Forwarding Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some SN-terminated bearers if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional SN change procedures. + +NOTE 5c: For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN(s). + +5. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies *RRConnectionReconfiguration\** message corresponding to the selected candidate PSCell, and sends an *RRConnectionReconfigurationComplete\** message, including an NR *RRReconfigurationComplete\*\** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. + - 6a-6b. The MN triggers the MeNB initiated SgNB Release procedure to inform the source SN to stop providing user data to the UE, and, if applicable, the address of the SN of the selected candidate PSCell to start data forwarding. + - 7a-7c. If the RRC connection reconfiguration procedure was successful, the MN informs the SN of the selected candidate PSCell via *SgNB Reconfiguration Complete* message, including the SN *RRReconfigurationComplete\*\** message. The MN sends the *SgNB Release Request* message(s) to cancel CPC in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. + 8. The UE synchronizes to the PSCell indicated in the *RRConnectionReconfiguration\** message applied in step 5. + - 9a-9b. For SN terminated bearers using RLC AM, the source SN sends the *SN Status Transfer* message, which the MN sends to the SN of the selected candidate PSCell, if needed. + 10. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the early data forwarding address in step 4a. + 11. The source SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. +- NOTE 6: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. +- 12-16. If applicable, a path update is triggered by the MN. + 17. Upon reception of the *UE Context Release* message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +#### SN initiated conditional SN Change + +The SN initiated conditional SN change procedure is used for inter-SN CPC configuration and inter-SN CPC execution. + +The SN initiated conditional SN change procedure may also be initiated by the source SN, to modify the existing SN initiated inter-SN CPC configuration, or to trigger the release of the candidate SN by cancellation of all the prepared PSCells at the candidate SN and releasing the CPC related UE context at the candidate SN. + +NOTE 6a0: To modify or release an existing intra-SN CPC configuration, the source SN triggers an SN initiated Conditional SN Modification (with or without SRB3) without MN involvement, as specified in 10.3. + +![Sequence diagram for Conditional SN Change – SN initiated. Lifelines: UE, MN, S-SN, T-SN, Other potential T-SN, S-GW, MME. The diagram shows the signaling flow between these entities for a conditional secondary node change initiated by the source node (SN).](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant S-SN + participant T-SN + participant Other potential T-SN + participant S-GW + participant MME + + Note left of MN: 1. SgNB Change Required + MN->>S-SN: 2. SgNB Addition Request + Note right of S-SN: 2. SgNB Addition Request + S-SN->>Other potential T-SN: 2. SgNB Addition Request + Note right of Other potential T-SN: 3. SgNB Addition Request Acknowledge + Other potential T-SN->>S-SN: 3. SgNB Addition Request Acknowledge + Note right of S-SN: 3. SgNB Addition Request Acknowledge + S-SN->>MN: 4. SgNB Modification Request + Note right of MN: 5. SgNB Modification Request Acknowledge + MN->>UE: 6. RRCConnectionReconfiguration (containing MN RRCConnectionReconfiguration* containing T-SN RRCReconfiguration**, and may contain S-SN RRCReconfiguration***) + Note right of UE: 7. RRCConnectionReconfigurationComplete (may contain S-SN RRCReconfigurationComplete***) + UE->>MN: 8. SgNB Change Confirm + Note right of MN: 9a. SgNB Modification Required + MN->>UE: 9b. RRCConnectionReconfiguration (containing MN RRCConnectionReconfiguration* containing T-SN RRCReconfiguration**, and may contain S-SN RRCReconfiguration***) + Note right of UE: 9c. RRCConnectionReconfigurationComplete (may contain S-SN RRCReconfigurationComplete***) + UE->>MN: 9d. SgNB Modification Confirm + Note right of MN: 10. RRCConnectionReconfigurationComplete* (containing T-SN RRCReconfigurationComplete**) + MN->>S-SN: 11a. SgNB Release Request + Note right of S-SN: 11b. SgNB Release Request Ack + S-SN->>MN: 12a. SgNB Reconfiguration Complete + Note right of MN: 12b. SgNB Release Request + MN->>Other potential T-SN: 12c. SgNB Release Request Acknowledge + Note right of Other potential T-SN: 13. Random Access Procedure + Other potential T-SN->>T-SN: 14a. SN Status Transfer + Note right of T-SN: 14b. SN Status Transfer + T-SN->>S-SN: 15. Data Forwarding + Note right of S-SN: 16. Secondary RAT Data Usage Report + S-SN->>MME: 17. E-RAB Modification Indication + Note right of MME: 18. Bearer Modification + MME->>S-GW: 18. Bearer Modification + S-GW->>S-SN: 19. End Marker Packet + Note right of S-SN: 20. New Path + S-SN->>T-SN: 21. E-RAB Modification Confirm + Note right of T-SN: 22. UE Context Release + T-SN->>S-SN: 22. UE Context Release + +``` + +Sequence diagram for Conditional SN Change – SN initiated. Lifelines: UE, MN, S-SN, T-SN, Other potential T-SN, S-GW, MME. The diagram shows the signaling flow between these entities for a conditional secondary node change initiated by the source node (SN). + +**Figure 10.5.1-4: Conditional SN Change – SN initiated** + +Figure 10.5.1-4 shows an example signalling flow for the Conditional Secondary Node Change initiated by the SN: + +1. The source SN initiates the conditional SN change procedure by sending *SgNB Change Required* message which contains a CPC initiation indication. The message also contains candidate SN ID(s) information and may include the SCG configuration (to support delta configuration), and contains the measurement results related to the candidate SN(s). The message also includes a list of proposed PSCell candidates recommended by the source SN, including execution conditions, the upper limit for the number of PSCells that can be prepared by each candidate SN, and may also include the SCG measurement configurations for CPC (e.g. measurement ID(s) to be used for CPC). +- 2/3. The MN requests each candidate SN to allocate resources for the UE by means of the *SgNB Addition* procedure(s), indicating the request is for CPAC, and the measurements results related to the candidate SN and indicating a list of proposed PSCell candidates received from the source SN, but not including execution conditions. Within the list of PSCells suggested by the source SN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an *NR RRCReconfiguration\*\** message contained in the *SgNB Addition Request Acknowledge* message. If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN includes the indication of full or delta RRC configuration, and the list of prepared PSCell IDs to the MN. The candidate SN can either accept or reject each of the candidate cells suggested by the source SN, i.e. it cannot configure any alternative candidates. + +NOTE 6a: In case the candidate SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE in the conditional configuration. + +- 4/5. The MN may indicate the candidate PSCells accepted by each candidate SN to the source SN via *SgNB Modification Request* message before it configures the UE e.g., when not all candidate PSCells were accepted by the candidate SN(s). If the MN does not send such indication, step 4 and 5 are skipped. If requested, the source SN sends an *SgNB Modification Request Acknowledge* message and if needed, provides an updated measurement configurations and/or the execution conditions for CPC to the MN. +6. The MN sends to the UE an *RRConnectionReconfiguration* message including the CPC configuration, i.e. a list of *RRConnectionReconfiguration\** messages and associated execution conditions, in which each *RRConnectionReconfiguration\** message contains the SCG configuration in the *RRReconfiguration\*\** message received from the candidate SN in step 3 and possibly an MCG configuration. Besides, the *RRConnectionReconfiguration* message can also include an updated MCG configuration, as well as the NR *RRReconfiguration\*\*\** message generated by the source SN, e.g., to configure the required conditional measurements. +7. The UE applies the *RRConnectionReconfiguration* message received in step 6, stores the CPC configuration and replies to the MN with an *RRConnectionReconfigurationComplete* message, which can include an NR *RRReconfigurationComplete\*\*\** message. In case the UE is unable to comply with (part of) the configuration included in the *RRConnectionReconfiguration* message, it performs the reconfiguration failure procedure. +8. If an NR RRC response message is included, the MN informs the source SN with the NR *RRReconfigurationComplete\*\*\** message via *SgNB Change Confirm* message. If step 4 and 5 are skipped, the MN will indicate the candidate PSCells accepted by each candidate SN to the source SN in the *SgNB Change Confirm* message. + +The MN sends the *SgNB Change Confirm* message towards the source SN to indicate that CPC is prepared, and in such case the source SN continues providing user data to the UE. If early data forwarding is applied, the MN informs the source SN the data forwarding addresses as received from the candidate SN(s), the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. In case multiple candidate SNs are prepared, the MN includes a list of Target SgNB ID and list of data forwarding addresses to the source SN. + +NOTE 6b: The Data Forwarding Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some PDCP SDUs if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional PSCell change. + +NOTE 6c: For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN(s). + +9a-9d. The source SN may send the *SgNB Modification Required* message to trigger an update of CPC execution condition and/or corresponding SCG measurement configuration for CPC. In such case in step 9b, the MN reconfigures the UE and in step 9c the UE responds with *RRConnectionReconfigurationComplete*, similarly as in steps 6 and 7. + +10. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies the *RRConnectionReconfiguration\** message corresponding to the selected candidate PSCell, and sends an *RRConnectionReconfigurationComplete\** message, including the NR *RRReconfigurationComplete\*\** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. + +11a-11b. The MN triggers the MeNB initiated SgNB Release procedure to inform source SN to stop providing user data to the UE, and if applicable, provides the address of the SN of the selected candidate PSCell to start late data forwarding. + +12a-12c. If the RRC connection reconfiguration procedure was successful, the MN informs the SN of the selected candidate PSCell via *SgNB Reconfiguration Complete* message, including the SN *RRReconfigurationComplete\*\** message. The MN sends the *SgNB Release Request* message(s) to cancel CPC in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. + +13. The UE synchronizes to the PSCell indicated in the *RRConnectionReconfiguration\** message applied in step 10. + +14a-14b. For SN terminated bearers using RLC AM, the source SN sends the *SN Status Transfer* message, which the MN sends then to the SN of the selected candidate PSCell, if needed. + +15. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the early data forwarding message from the MN. + +16. The source SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. + +NOTE 7: The order the source SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN/target SN is not defined. The SgNB may send the report when the transmission of the related bearer is stopped. + +17-21. If applicable, a path update is triggered by the MN. + +22. Upon reception of the *UE Context Release* message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +### 10.5.2 MR-DC with 5GC + +#### MN initiated SN Change + +The MN initiated SN change procedure is used to transfer a UE context from the source SN to a target SN and to change the SCG configuration in UE from one SN to another. + +The Secondary Node Change procedure always involves signalling over MCG SRB towards the UE. + +![Sequence diagram of the SN change procedure - MN initiated. The diagram shows the interaction between UE, MN, S-SN, T-SN, UPF, and AMF. The MN initiates the change by sending an SN Addition Request to the T-SN. The T-SN responds with an SN Addition Request Acknowledge. The MN then sends an Xn-U Address Indication to the S-SN. The S-SN responds with an SN Release Request Acknowledge. The MN then sends an RRC reconfiguration to the UE. The UE responds with an RRC reconfiguration complete. The MN then sends an SN Reconfiguration Complete to the T-SN. The T-SN initiates a Random Access Procedure with the UE. The MN sends an SN Status Transfer to the T-SN. The S-SN performs data forwarding to the T-SN. The S-SN sends a Secondary RAT Data Usage Report to the MN. The MN sends a PDU Session Resource Modify Indication to the AMF. The AMF sends a Bearer Modification to the UPF. The S-SN sends an End Marker Packet to the T-SN. The T-SN establishes a new path to the UPF. The MN sends a PDU Session Resource Modify Confirm to the AMF. Finally, the MN sends a UE Context Release to the S-SN.](503e868b4dc4a68f02e22d83251f2b0f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant S-SN + participant T-SN + participant UPF + participant AMF + + MN->>T-SN: 1. SN Addition Request + T-SN-->>MN: 2. SN Addition Request Acknowledge + MN->>S-SN: 2a. Xn-U Address Indication + S-SN-->>MN: 3a. SN Release Request + MN-->>S-SN: 3b. SN Release Request Acknowledge + S-SN-->>MN: 3c. Xn-U Address Indication + MN-->>UE: 4. RRC reconfiguration + UE-->>MN: 5. RRC reconfiguration complete + MN->>T-SN: 6. SN Reconfiguration Complete + T-SN-->>UE: 7. Random Access Procedure + MN-->>T-SN: 8a. SN Status Transfer + T-SN-->>MN: 8b. SN Status Transfer + S-SN-->>T-SN: 9. Data Forwarding + S-SN-->>MN: 10. Secondary RAT Data Usage Report + MN->>AMF: 11. PDU Session Resource Modify Indication + AMF-->>UPF: 12. Bearer Modification + S-SN-->>T-SN: 13. End Marker Packet + T-SN-->>UPF: 14. New Path + MN-->>AMF: 15. PDU Session Resource Modify Confirm + MN-->>S-SN: 16. UE Context Release + +``` + +Sequence diagram of the SN change procedure - MN initiated. The diagram shows the interaction between UE, MN, S-SN, T-SN, UPF, and AMF. The MN initiates the change by sending an SN Addition Request to the T-SN. The T-SN responds with an SN Addition Request Acknowledge. The MN then sends an Xn-U Address Indication to the S-SN. The S-SN responds with an SN Release Request Acknowledge. The MN then sends an RRC reconfiguration to the UE. The UE responds with an RRC reconfiguration complete. The MN then sends an SN Reconfiguration Complete to the T-SN. The T-SN initiates a Random Access Procedure with the UE. The MN sends an SN Status Transfer to the T-SN. The S-SN performs data forwarding to the T-SN. The S-SN sends a Secondary RAT Data Usage Report to the MN. The MN sends a PDU Session Resource Modify Indication to the AMF. The AMF sends a Bearer Modification to the UPF. The S-SN sends an End Marker Packet to the T-SN. The T-SN establishes a new path to the UPF. The MN sends a PDU Session Resource Modify Confirm to the AMF. Finally, the MN sends a UE Context Release to the S-SN. + +Figure 10.5.2-1: SN change procedure - MN initiated + +Figure 10.5.2-1 shows an example signalling flow for the SN Change initiated by the MN: + +1/2. The MN initiates the SN change by requesting the target SN to allocate resources for the UE by means of the SN Addition procedure. The MN may include measurement results related to the target SN. If data forwarding is needed, the target SN provides data forwarding addresses to the MN. The target SN includes the indication of the full or delta RRC configuration. + +NOTE 1: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration and SN-associated QMC configuration information, and to allow provision of data forwarding related information before step 1. + +- 2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message. + 3. If the allocation of target SN resources was successful, the MN initiates the release of the source SN resources including a Cause indicating SCG mobility. The Source SN may reject the release. If data forwarding is needed the MN provides data forwarding addresses to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides data forwarding addresses as received from the target SN to source SN. Reception of the *SN Release Request* message triggers the source SN to stop providing user data to the UE. + - 4/5. The MN triggers the UE to apply the new configuration. The MN indicates the new configuration to the UE in the MN RRC reconfiguration message including the target SN RRC reconfiguration message. The UE applies the new configuration and sends the MN RRC reconfiguration complete message, including the SN RRC response message for the target SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. + 6. If the RRC connection reconfiguration procedure was successful, the MN informs the target SN via *SN Reconfiguration Complete* message with the included SN RRC response message for the target SN, if received from the UE. + 7. If configured with bearers requiring SCG radio resources the UE synchronizes to the target SN. + 8. If PDCP termination point is changed for bearers using RLC AM, the source SN sends the *SN Status Transfer* message, which the MN sends then to the target SN, if needed. + 9. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the *SN Release Request* message from the MN. + 10. The source SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. +- NOTE 2: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. +- 11-15. If applicable, a PDU Session path update procedure is triggered by the MN. + 16. Upon reception of the *UE Context Release* message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue + +#### SN initiated SN Change + +The SN initiated SN change procedure is used to transfer a UE context from the source SN to a target SN and to change the SCG configuration in UE from one SN to another. + +![Sequence diagram of SN change procedure - SN initiated. Lifelines: UE, MN, S-SN, T-SN, UPF, AMF. The procedure involves SN Change Required, SN Addition Request, RRC reconfiguration, SN Change Confirm, SN Reconfiguration Complete, Random Access Procedure, SN Status Transfer, Data Forwarding, Secondary RAT Data Usage Report, PDU Session Resource Modify Indication, Bearer Modification, End Marker Packet, New Path, PDU Session Resource Modify Confirm, and UE Context Release.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant S-SN + participant T-SN + participant UPF + participant AMF + + Note left of MN: 1. SN Change Required + MN->>S-SN: 1. SN Change Required + Note left of MN: 2. SN Addition Request + MN->>T-SN: 2. SN Addition Request + Note left of T-SN: 3. SN Addition Request Acknowledge + T-SN->>MN: 3. SN Addition Request Acknowledge + Note left of MN: 3a. Xn-U Address Indication + MN->>T-SN: 3a. Xn-U Address Indication + Note left of MN: 4. RRC reconfiguration + MN->>UE: 4. RRC reconfiguration + Note left of UE: 5. RRC reconfiguration complete + UE->>MN: 5. RRC reconfiguration complete + Note left of MN: 6. SN Change Confirm + MN->>S-SN: 6. SN Change Confirm + Note left of MN: 7. SN Reconfiguration Complete + MN->>T-SN: 7. SN Reconfiguration Complete + Note left of UE: 8. Random Access Procedure + UE->>T-SN: 8. Random Access Procedure + Note left of MN: 9a. SN Status Transfer + MN->>S-SN: 9a. SN Status Transfer + Note left of T-SN: 9b. SN Status Transfer + T-SN->>MN: 9b. SN Status Transfer + Note left of S-SN: 10. Data Forwarding + S-SN-->>T-SN: 10. Data Forwarding + Note left of MN: 11. Secondary RAT Data Usage Report + MN->>S-SN: 11. Secondary RAT Data Usage Report + Note left of S-SN: 12. PDU Session Resource Modify Indication + S-SN-->>AMF: 12. PDU Session Resource Modify Indication + Note left of AMF: 13. Bearer Modification + AMF->>UPF: 13. Bearer Modification + Note left of S-SN: 14. End Marker Packet + S-SN-->>T-SN: 14. End Marker Packet + Note left of T-SN: 15. New Path + T-SN-->>UPF: 15. New Path + Note left of T-SN: 16. PDU Session Resource Modify Confirm + T-SN-->>S-SN: 16. PDU Session Resource Modify Confirm + Note left of MN: 17. UE Context Release + MN->>S-SN: 17. UE Context Release + +``` + +Sequence diagram of SN change procedure - SN initiated. Lifelines: UE, MN, S-SN, T-SN, UPF, AMF. The procedure involves SN Change Required, SN Addition Request, RRC reconfiguration, SN Change Confirm, SN Reconfiguration Complete, Random Access Procedure, SN Status Transfer, Data Forwarding, Secondary RAT Data Usage Report, PDU Session Resource Modify Indication, Bearer Modification, End Marker Packet, New Path, PDU Session Resource Modify Confirm, and UE Context Release. + +**Figure 10.5.2-2: SN change procedure - SN initiated** + +Figure 10.5.2-2 shows an example signalling flow for the SN Change initiated by the SN: + +1. The source SN initiates the SN change procedure by sending the *SN Change Required* message, which contains a candidate target node ID and may include the SCG configuration (to support delta configuration) and measurement results related to the target SN. For supporting QMC continuity during mobility, the *SN Change Required* message may contain the information about the QMC configurations at the source SN. +- 2/3. The MN requests the target SN to allocate resources for the UE by means of the SN Addition procedure, including the measurement results related to the target SN received from the source SN. If data forwarding is needed, the target SN provides data forwarding addresses to the MN. The target SN includes the indication of the full or delta RRC configuration. +- 3a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message. +- 4/5. The MN triggers the UE to apply the new configuration. The MN indicates the new configuration to the UE in the MN RRC reconfiguration message including the SN RRC reconfiguration message generated by the target SN. The UE applies the new configuration and sends the MN RRC reconfiguration complete message, including the SN RRC response message for the target SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. +6. If the allocation of target SN resources was successful, the MN confirms the change of the source SN. If data forwarding is needed the MN provides data forwarding addresses to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides data forwarding addresses as received from the target SN to source SN. Reception of the *SN Change Confirm* message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. +7. If the RRC connection reconfiguration procedure was successful, the MN informs the target SN via *SN Reconfiguration Complete* message with the included SN RRC response message for the target SN, if received from the UE. + +8. The UE synchronizes to the target SN. + 9. If PDCP termination point is changed for bearers using RLC AM, the source SN sends the *SN Status Transfer* message, which the MN sends then to the target SN, if needed. + 10. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the *SN Change Confirm* message from the MN. + 11. The source SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. +- NOTE 3: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN/target SN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. +- 12-16. If applicable, a PDU Session path update procedure is triggered by the MN. +17. Upon reception of the *UE Context Release* message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +#### MN initiated conditional SN Change + +The Conditional Secondary Node Change procedure is initiated by the MN for inter-SN CPC configuration and inter-SN CPC execution. + +![Sequence diagram of the Conditional SN change procedure - MN initiated. The diagram shows interactions between UE, MN, S-SN, T-SN, Other potential T-SN, UPF, and AMF. The MN initiates the process by sending SN Addition Requests to T-SN and Other potential T-SN. The T-SN responds with SN Addition Request Acknowledge. The MN then sends Xn-U Address Indications to both. The MN sends an RRCReconfiguration to the UE. The UE responds with RRCReconfigurationComplete. The MN then sends SN Release Requests to the S-SN and Other potential T-SN. The S-SN responds with SN Release Request Acknowledge. The MN sends Xn-U Address Indications to the S-SN and T-SN. The MN sends SN Reconfiguration Complete to the T-SN. The MN sends SN Release Request to the Other potential T-SN. The Other potential T-SN responds with SN Release Request Acknowledge. The UE performs a Random Access Procedure with the T-SN. The MN sends SN Status Transfer to the T-SN. The S-SN performs Data Forwarding to the T-SN. The S-SN sends Secondary RAT Data Usage Report to the MN. The MN sends PDU Session Resource Modify Indication to the AMF. The AMF sends Bearer Modification to the UPF. The UPF sends End Marker Packet to the S-SN. The S-SN sends New Path to the T-SN. The MN sends PDU Session Resource Modify Confirm to the AMF. The MN sends UE Context Release to the S-SN.](4260aa4a7ece77c411597094c9d197bd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant S-SN + participant T-SN + participant Other potential T-SN + participant UPF + participant AMF + + Note right of MN: 1. SN Addition Request + MN->>T-SN: 1. SN Addition Request + MN->>Other potential T-SN: 1. SN Addition Request + Note right of T-SN: 2. SN Addition Request Acknowledge + T-SN-->>MN: 2. SN Addition Request Acknowledge + Note right of Other potential T-SN: 2. SN Addition Request Acknowledge + Other potential T-SN-->>MN: 2. SN Addition Request Acknowledge + Note right of MN: 2a. Xn-U Address Indication + MN->>T-SN: 2a. Xn-U Address Indication + MN->>Other potential T-SN: 2a. Xn-U Address Indication + Note right of MN: 3. RRCReconfiguration (containing SN RRCReconfiguration**) + MN->>UE: 3. RRCReconfiguration (containing SN RRCReconfiguration**) + Note right of UE: 4. RRCReconfigurationComplete + UE-->>MN: 4. RRCReconfigurationComplete + Note right of MN: 4a. Xn-U Address Indication + MN->>S-SN: 4a. Xn-U Address Indication + Note right of UE: 5. RRCReconfigurationComplete* (containing SN RRCReconfiguration***) + UE-->>MN: 5. RRCReconfigurationComplete* (containing SN RRCReconfiguration***) + Note right of MN: 6a. SN Release Request + MN->>S-SN: 6a. SN Release Request + Note right of S-SN: 6b. SN Release Request Acknowledge + S-SN-->>MN: 6b. SN Release Request Acknowledge + Note right of MN: 6c. Xn-U Address Indication + MN->>S-SN: 6c. Xn-U Address Indication + Note right of MN: 7a. SN Reconfiguration Complete + MN->>T-SN: 7a. SN Reconfiguration Complete + Note right of MN: 7b. SN Release Request + MN->>Other potential T-SN: 7b. SN Release Request + Note right of Other potential T-SN: 7c. SN Release Request Acknowledge + Other potential T-SN-->>MN: 7c. SN Release Request Acknowledge + Note right of UE: 8. Random Access Procedure + UE->>T-SN: 8. Random Access Procedure + Note right of MN: 9a. SN Status Transfer + MN->>T-SN: 9a. SN Status Transfer + Note right of MN: 9b. SN Status Transfer + MN->>T-SN: 9b. SN Status Transfer + Note right of S-SN: 10. Data Forwarding + S-SN->>T-SN: 10. Data Forwarding + Note right of S-SN: 11. Secondary RAT Data Usage Report + S-SN->>MN: 11. Secondary RAT Data Usage Report + Note right of MN: 12. PDU Session Resource Modify Indication + MN->>AMF: 12. PDU Session Resource Modify Indication + Note right of AMF: 13. Bearer Modification + AMF->>UPF: 13. Bearer Modification + Note right of UPF: 14. End Marker Packet + UPF->>S-SN: 14. End Marker Packet + Note right of S-SN: 15. New Path + S-SN->>T-SN: 15. New Path + Note right of MN: 16. PDU Session Resource Modify Confirm + MN->>AMF: 16. PDU Session Resource Modify Confirm + Note right of MN: 17. UE Context Release + MN->>S-SN: 17. UE Context Release + +``` + +Sequence diagram of the Conditional SN change procedure - MN initiated. The diagram shows interactions between UE, MN, S-SN, T-SN, Other potential T-SN, UPF, and AMF. The MN initiates the process by sending SN Addition Requests to T-SN and Other potential T-SN. The T-SN responds with SN Addition Request Acknowledge. The MN then sends Xn-U Address Indications to both. The MN sends an RRCReconfiguration to the UE. The UE responds with RRCReconfigurationComplete. The MN then sends SN Release Requests to the S-SN and Other potential T-SN. The S-SN responds with SN Release Request Acknowledge. The MN sends Xn-U Address Indications to the S-SN and T-SN. The MN sends SN Reconfiguration Complete to the T-SN. The MN sends SN Release Request to the Other potential T-SN. The Other potential T-SN responds with SN Release Request Acknowledge. The UE performs a Random Access Procedure with the T-SN. The MN sends SN Status Transfer to the T-SN. The S-SN performs Data Forwarding to the T-SN. The S-SN sends Secondary RAT Data Usage Report to the MN. The MN sends PDU Session Resource Modify Indication to the AMF. The AMF sends Bearer Modification to the UPF. The UPF sends End Marker Packet to the S-SN. The S-SN sends New Path to the T-SN. The MN sends PDU Session Resource Modify Confirm to the AMF. The MN sends UE Context Release to the S-SN. + +Figure 10.5.2-3: Conditional SN change procedure - MN initiated + +Figure 10.5.2-3 shows an example signalling flow for the conditional SN Change initiated by the MN: + +- 1/2. The MN initiates the conditional SN change by requesting the candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure, indicating that the request is for CPAC. The MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN(s) to choose and + +configure the SCG cell(s), provides the upper limit for the number of PSCells that can be prepared by the candidate SN. Within the list of cells as indicated within the measurement results indicated by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR *RRCREconfiguration\*\** message contained in the *SN Addition Request Acknowledge* message with the prepared PSCell ID(s). If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN includes the indication of the full or delta RRC configuration. The candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. + +NOTE 4: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration and to allow provision of data forwarding related information before step 1. + +- 2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message to the candidate SN(s). +3. The MN sends to the UE an *RRCREconfiguration* message including the CPC configuration, i.e. a list of *RRCREconfiguration\** messages and associated execution conditions, in which each *RRCREconfiguration\** message contains the SCG configuration in the *RRCREconfiguration\*\** message received from the candidate SN in step 2 and possibly an MCG configuration. Besides, the *RRCREconfiguration* message can also include an updated MCG configuration, e.g., to configure the required conditional measurements. +4. The UE applies the *RRCREconfiguration* message received in step 3, stores the CPC configuration and replies to the MN with an *RRCREconfigurationComplete* message. In case the UE is unable to comply with (part of) the configuration included in the *RRCREconfiguration* message, it performs the reconfiguration failure procedure. +- 4a. Upon receiving the MN *RRCREconfigurationComplete* message from the UE, the MN informs the source SN that the CPC has been configured via Xn-U Address Indication procedure, the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. + +NOTE 4a: Separate Xn-U Address Indication procedures may be invoked to provide different forwarding addresses of the prepared candidate target SNs. In this case, it is up to the MN and the source SN implementations to make sure that the EARLY STATUS TRANSFER message(s) from the source SN, if any, is forwarded to the right target destination. The Xn-U Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some SN-terminated bearers if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional SN change procedures. + +NOTE 4b: For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN(s). + +5. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies *RRCREconfiguration\** message corresponding to the selected candidate PSCell, and sends an MN *RRCREconfigurationComplete\** message, including an NR *RRCREconfigurationComplete\*\** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. +- 6a-6c. The MN triggers the MN initiated SN Release procedure to inform the source SN to stop providing user data to the UE, and if applicable, triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell, to start late data forwarding. +- 7a-7c. If the RRC connection reconfiguration procedure was successful, the MN informs the SN of the selected candidate PSCell via *SN Reconfiguration Complete* message, including the SN *RRCREconfigurationComplete\*\** message. The MN sends the *SN Release Request* message(s) to cancel CPC in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. +8. The UE synchronizes to the PSCell indicated in the *RRCREconfiguration\** message applied in step 5. +- 9a-9b. If PDCP termination point is changed for bearers using RLC AM, the source SN sends the message, which the MN sends then to the SN of the selected candidate PSCell, if needed. +10. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the early data forwarding address in step 4a. + +11. The source SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. + +NOTE 5: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. + +12-16. If applicable, a PDU Session path update procedure is triggered by the MN. + +17. Upon reception of the *UE Context Release* message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +#### **SN initiated conditional SN Change** + +The SN initiated conditional SN change procedure is used for inter-SN CPC configuration and inter-SN CPC execution. + +The SN initiated conditional SN change procedure may also be initiated by the source SN, to modify the existing SN initiated inter-SN CPC configuration, or to trigger the release of the candidate SN by cancellation of all the prepared PSCells at the candidate SN and releasing the CPC related UE context at the candidate SN. + +NOTE 5a0: To modify or release an existing intra-SN CPC configuration, the source SN triggers an SN initiated Conditional SN Modification (with or without SRB3) without MN involvement, as specified in 10.3. + +![Sequence diagram for Conditional SN change procedure - SN initiated. Lifelines: UE, MN, S-SN, T-SN, Other potential T-SN, UPF, AMF. The procedure involves SN Change Required, SN Addition Request, SN Modification Request, RRC Reconfiguration, SN Release Request, SN Status Transfer, Data Forwarding, and UE Context Release.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant S-SN + participant T-SN + participant Other potential T-SN + participant UPF + participant AMF + + Note left of MN: 1. SN Change Required + MN->>S-SN: 2. SN Addition Request + Note right of S-SN: 2. SN Addition Request + S-SN->>Other potential T-SN: 2. SN Addition Request + Note right of Other potential T-SN: 3. SN Addition Request Acknowledge + Other potential T-SN->>S-SN: 3. SN Addition Request Acknowledge + Note right of S-SN: 3. SN Addition Request Acknowledge + S-SN->>MN: 3. SN Addition Request Acknowledge + Note left of MN: 3a. Xn-U Address Indication + MN->>T-SN: 3a. Xn-U Address Indication + Note right of T-SN: 3a. Xn-U Address Indication + T-SN->>Other potential T-SN: 3a. Xn-U Address Indication + Note right of Other potential T-SN: 4. SN Modification Request + Other potential T-SN->>S-SN: 4. SN Modification Request + Note right of S-SN: 5. SN Modification Request Acknowledge + S-SN->>MN: 5. SN Modification Request Acknowledge + Note left of MN: 6. RRCReconfiguration (containing MN RRCReconfiguration* containing T-SN RRCReconfiguration**, and may contain S-SN RRCReconfiguration***) + MN->>UE: 6. RRCReconfiguration (containing MN RRCReconfiguration* containing T-SN RRCReconfiguration**, and may contain S-SN RRCReconfiguration***) + Note left of UE: 7. RRCReconfigurationComplete (may contain S-SN RRCReconfigurationComplete***) + UE->>MN: 7. RRCReconfigurationComplete (may contain S-SN RRCReconfigurationComplete***) + Note left of MN: 8. SN Change Confirm + MN->>S-SN: 8. SN Change Confirm + Note left of MN: 9a. SN Modification Required + MN->>S-SN: 9a. SN Modification Required + Note left of S-SN: 9b. RRCReconfiguration (containing MN RRCReconfiguration* containing T-SN RRCReconfiguration**, and may contain S-SN RRCReconfiguration***) + S-SN->>UE: 9b. RRCReconfiguration (containing MN RRCReconfiguration* containing T-SN RRCReconfiguration**, and may contain S-SN RRCReconfiguration***) + Note left of UE: 9c. RRCReconfigurationComplete (may contain S-SN RRCReconfigurationComplete***) + UE->>S-SN: 9c. RRCReconfigurationComplete (may contain S-SN RRCReconfigurationComplete***) + Note left of S-SN: 9d. SN Modification Confirm + S-SN->>MN: 9d. SN Modification Confirm + Note left of MN: 10. RRCReconfigurationComplete* (containing T-SN RRCReconfigurationComplete**) + MN->>UE: 10. RRCReconfigurationComplete* (containing T-SN RRCReconfigurationComplete**) + Note left of UE: 11a. SN Release Request + UE->>MN: 11a. SN Release Request + Note left of MN: 11b. SN Release Request Ack + MN->>S-SN: 11b. SN Release Request Ack + Note left of S-SN: 11c. Xn-U Address Indication + S-SN->>MN: 11c. Xn-U Address Indication + Note left of MN: 12a. SN Reconfiguration Complete + MN->>T-SN: 12a. SN Reconfiguration Complete + Note left of T-SN: 12b. SN Release Request + T-SN->>Other potential T-SN: 12b. SN Release Request + Note right of Other potential T-SN: 12c. SN Release Request Acknowledge + Other potential T-SN->>T-SN: 12c. SN Release Request Acknowledge + Note right of T-SN: 13. Random Access Procedure + T-SN->>UE: 13. Random Access Procedure + Note left of UE: 14a. SN Status Transfer + UE->>MN: 14a. SN Status Transfer + Note left of MN: 14b. SN Status Transfer + MN->>T-SN: 14b. SN Status Transfer + Note left of T-SN: 15. Data Forwarding + T-SN->>UPF: 15. Data Forwarding + Note left of UPF: 16. Secondary RAT Data Usage Report + UPF->>MN: 16. Secondary RAT Data Usage Report + Note left of MN: 17. PDU Session Resource Modify Indication + MN->>AMF: 17. PDU Session Resource Modify Indication + Note left of AMF: 18. Bearer Modification + AMF->>UPF: 18. Bearer Modification + Note left of UPF: 19. End Marker Packet + UPF->>T-SN: 19. End Marker Packet + Note left of T-SN: 20. New Path + T-SN->>UPF: 20. New Path + Note left of UPF: 21. PDU Session Resource Modify Confirm + UPF->>AMF: 21. PDU Session Resource Modify Confirm + Note left of AMF: 22. UE Context Release + AMF->>S-SN: 22. UE Context Release + +``` + +Sequence diagram for Conditional SN change procedure - SN initiated. Lifelines: UE, MN, S-SN, T-SN, Other potential T-SN, UPF, AMF. The procedure involves SN Change Required, SN Addition Request, SN Modification Request, RRC Reconfiguration, SN Release Request, SN Status Transfer, Data Forwarding, and UE Context Release. + +**Figure 10.5.2-4: Conditional SN change procedure - SN initiated** + +Figure 10.5.2-4 shows an example signalling flow for the conditional SN Change initiated by the SN: + +1. The source SN initiates the conditional SN change procedure by sending the *SN Change Required* message, which contains a CPC initiation indication. The message also contains candidate node ID(s) and may include the SCG configuration (to support delta configuration), and contains the measurements results which may include cells that are not CPC candidates. The message also includes a list of proposed PSCell candidates recommended by the source SN, including execution conditions, the upper limit for the number of PSCells that can be prepared by each candidate SN, and may also include the SCG measurement configurations for CPC (e.g. measurement ID(s) to be used for CPC). +- 2/3. The MN requests each candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure(s), indicating the request is for CPAC, and the measurements results which may include cells that are not CPC candidates received from the source SN to the candidate SN, and indicating a list of proposed PSCell candidates received from the source SN, but not including execution conditions. Within the list of PSCells suggested by the source SN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an *NR RRCReconfiguration\*\** message contained in the *SgNB Addition Request Acknowledge* message. If data forwarding is needed, the candidate SN + +provides data forwarding addresses to the MN. The candidate SN includes the indication of full or delta RRC configuration, and the list of prepared PSCell IDs to the MN. The candidate SN can either accept or reject each of the candidate cells suggested by the source SN, i.e., it cannot configure any alternative candidates. + +- 3a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message to the candidate SN(s). +- 4/5. The MN may indicate the candidate PSCells accepted by each candidate SN to the source SN via *SN Modification Request* message before it configures the UE, e.g., when not all candidate PSCells were accepted by the candidate SN(s). If the MN does not send such indication, step 4 and 5 are skipped. If requested, the source SN sends an *SN Modification Request Acknowledge* message and if needed, provides an updated measurement configurations and/or the execution conditions to the MN. +6. The MN sends to the UE an *RRCREconfiguration* message including the CPC configuration, i.e. a list of *RRCREconfiguration\** messages and associated execution conditions, in which each *RRCREconfiguration\** message contains the SCG configuration in the *RRCREconfiguration\*\** message received from the candidate SN in step 3 and possibly an MCG configuration. Besides, the *RRCREconfiguration* message can also include an updated MCG configuration, as well as the NR *RRCREconfiguration\*\*\** message generated by the source SN, e.g., to configure the required conditional measurements. +7. The UE applies the *RRCREconfiguration* message received in step 6, stores the CPC configuration and replies to the MN with an *RRCREconfigurationComplete* message, which can include an NR *RRCREconfigurationComplete\*\*\** message. In case the UE is unable to comply with (part of) the configuration included in the *RRCREconfiguration* message, it performs the reconfiguration failure procedure. +8. If an SN RRC response message is included, the MN informs the source SN with the SN *RRCREconfigurationComplete\*\*\** message via *SN Change Confirm* message. If step 4 and 5 are skipped, the MN will indicate the candidate PSCells accepted by each candidate SN to the source SN in the *SN Change Confirm* message. + +The MN sends the *SN Change Confirm* message towards the source SN to indicate that CPC is prepared, and in such case the source SN continues providing user data to the UE. If early data forwarding is applied, the MN informs the source SN the data forwarding addresses as received from the candidate SN(s), the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. In case multiple candidate SNs are prepared, the MN includes a list of Target SN ID and list of data forwarding addresses to the source SN. + +NOTE 5a: The Xn-U Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some PDCP SDUs if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional PSCell change. + +NOTE 5b: For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN(s). + +9a-9d. The source SN may send the *SN Modification Required* message to trigger an update of CPC execution condition and/or corresponding SCG measurement configuration for CPC. In such case in step 9b, the MN reconfigures the UE and in step 9c the UE responds with *RRCREconfigurationComplete*, similarly as in steps 6 and 7. + +10. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies *RRCREconfiguration\** message corresponding to the selected candidate PSCell, and sends an *RRCREconfigurationComplete\** message, including an *RRCREconfigurationComplete\*\** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. + +11a-11c. The MN triggers the MN initiated SN Release procedure to inform the source SN to stop providing user data to the UE, and if applicable, triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell to start late data forwarding. + +- 12a-12c. If the RRC connection reconfiguration procedure was successful, the MN informs the SN of the selected candidate PSCell via *SN Reconfiguration Complete* message, including the SN *RRCREconfigurationComplete\*\** message. The MN sends the *SN Release Request* message(s) to cancel CPC in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. + +13. The UE synchronizes to the PSCell indicated in the *RRReconfiguration\** message applied in step 10. + 14. If PDCP termination point is changed for bearers using RLC AM, the source SN sends the *SN Status Transfer* message, which the MN sends then to the SN of the selected candidate PSCell, if needed. + 15. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the data forwarding address related information from the MN. + 16. The source SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. +- NOTE 6: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN/target SN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. +- 17-21. If applicable, a PDU Session path update procedure is triggered by the MN. + 22. Upon reception of the *UE Context Release* message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +## 10.6 PSCell change + +In MR-DC, a PSCell change does not always require a security key change. + +If a security key change is required, this is performed through a synchronous SCG reconfiguration procedure towards the UE involving random access on PSCell and a security key change, during which the MAC entity configured for SCG is reset and RLC configured for SCG is re-established regardless of the bearer type(s) established on SCG. For SN terminated bearers, PDCP is re-established. In all MR-DC options, to perform this procedure within the same SN, the SN Modification procedure as described in clause 10.3 is used, setting the *PDCP Change Indication* to indicate that a $S-K_{\text{gNB}}$ (for EN-DC, NGEN-DC and NR-DC) or $S-K_{\text{eNB}}$ (for NE-DC) update is required when the procedure is initiated by the SN or including the *SgNB Security Key / SN Security Key* when the procedure is initiated by the MN. In all MR-DC options, to perform a PSCell change between different SN nodes, the SN Change procedure as described in clause 10.5 is used. + +If a security key change is not required (only possible in EN-DC, NGEN-DC and NR-DC), this is performed through a synchronous SCG reconfiguration procedure without security key change towards the UE involving random access on PSCell, during which the MAC entity configured for SCG is reset and RLC configured for SCG is re-established regardless of the bearer type(s) established on SCG. For DRBs using RLC AM mode PDCP data recovery applies, and for DRBs using RLC UM no action is performed in PDCP. For SRB3 PDCP may discard all stored SDUs and PDUs. Unless MN terminated SCG or split bearers are configured, this does not require MN involvement. In this case, if location information was requested for the UE, the SN informs the MN about the PSCell change (as part of location information) using the SN initiated SN modification procedure independently from the reconfiguration of the UE. In case of MN terminated SCG or split bearers, the SN initiated SN Modification procedure as described in clause 10.3 is used, setting the *PDCP Change Indication* to indicate that a PDCP data recovery is required. If the MN subscribes to PSCell changes to retrieve the SCG UE history information, the SN informs the MN about the SCG UE history information using the SN initiated SN modification procedure when the SCG UE history information changes. + +A Conditional PSCell Change (CPC) is defined as a PSCell change that is executed by the UE when execution condition(s) is met. The UE starts evaluating the execution condition(s) upon receiving the CPC configuration, and stops evaluating the execution condition(s) once PSCell change or PCell change is triggered. Intra-SN CPC without MN involvement, inter-SN CPC initiated either by MN or SN are supported. + +The following principles apply to CPC: + +- The CPC configuration contains the configuration of CPC candidate PSCell(s) and execution condition(s) and may contain the MCG configuration for inter-SN CPC, to be applied when CPC execution is triggered. +- An execution condition may consist of one or two trigger condition(s) (see *CondEvent*, as defined in TS 38.331 [4] or TS 36.331 [10]). Only single RS type and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be used for the evaluation of CPC execution condition of a single candidate PSCell. +- Before any CPC execution condition is satisfied, upon reception of PSCell change command or PCell change command, the UE executes the PSCell change procedure as described in clause 10.3 and 10.5 or the PCell change procedure as described in clause 9.2.3.2 in TS 38.300[3] or clause 10.1.2.1 in TS 36.300 [2], regardless + +of any previously received CPC configuration. Upon the successful completion of PSCell change procedure or PCell change procedure, the UE releases all stored CPC configurations. + +- While executing CPC, the UE is not required to continue evaluating the execution condition of other candidate PSCell(s) or PCell(s). +- Once the CPC procedure is executed successfully, the UE releases all stored conditional reconfigurations (i.e. for CPC and for CHO, as specified in TS 38.300 [3] or TS 36.300 [2]). +- Upon the release of SCG, the UE releases the stored CPC configurations. +- MN can inform SN of the maximum number of conditional reconfigurations the SN is allowed to configure for SN initiated CPC including both intra-SN and inter-SN CPC. + +CPC configuration in HO command, in PSCell addition/change command or within any conditional reconfiguration (i.e CPA, CPC or CHO configuration) is not supported. + +An SCG LTM is defined as a PSCell cell switch procedure that the network triggers via MAC CE based on L1 measurements. Only intra-SN SCG LTM without MN involvement is supported. + +## 10.7 Inter-Master Node handover with/without Secondary Node change + +### 10.7.1 EN-DC + +Inter-Master Node handover with/without MN initiated Secondary Node change is used to transfer context data from a source MN to a target MN while the context at the SN is kept or moved to another SN. During an Inter-Master Node handover, the target MN decides whether to keep or change the SN (or release the SN, as described in clause 10.8). + +NOTE 1: Void. + +![Sequence diagram for Inter-MN handover with/without MN initiated SN change. Lifelines: UE, source MN, (source) SN, (target) SN, target MN, S-GW, MME. The diagram shows the signaling flow for a handover between two Master Nodes (MN), with or without a change in the Secondary Node (SN).](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant source MN + participant source SN as (source) SN + participant target SN as (target) SN + participant target MN + participant S-GW + participant MME + + Note left of source MN: 1. Handover Request + source MN->>target MN: 1. Handover Request + Note right of target MN: 2. SgNB Addition Request + target MN->>target SN: 2. SgNB Addition Request + Note right of target SN: 3. SgNB Addition Request Ack + target SN->>target MN: 3. SgNB Addition Request Ack + Note left of source MN: 4. Handover Request Acknowledge + target MN->>source MN: 4. Handover Request Acknowledge + Note left of source MN: 5a. SgNB Release Request + source MN->>source SN: 5a. SgNB Release Request + Note left of source SN: 5b. SgNB Release Request Acknowledge + source SN->>source MN: 5b. SgNB Release Request Acknowledge + Note left of UE: 6. RRCConnectionReconfiguration + source MN->>UE: 6. RRCConnectionReconfiguration + Note left of UE: 7. Random Access Procedure + UE->>target MN: 7. Random Access Procedure + Note left of target MN: 8. RRCConnectionReconfigurationComplete + target MN->>UE: 8. RRCConnectionReconfigurationComplete + Note left of UE: 9. Random Access Procedure + UE->>target SN: 9. Random Access Procedure + Note right of target SN: 10. SgNB Reconfiguration Complete + target SN->>target MN: 10. SgNB Reconfiguration Complete + Note left of source MN: 11a. Secondary RAT Data Usage Report + source MN->>source SN: 11a. Secondary RAT Data Usage Report + Note left of source SN: 11b. Secondary RAT Data Usage Report + source SN->>source MN: 11b. Secondary RAT Data Usage Report + Note left of source MN: 12a. SN Status Transfer + source MN->>target MN: 12a. SN Status Transfer + Note left of target MN: 12b. SN Status Transfer + target MN->>target SN: 12b. SN Status Transfer + Note right of target SN: 12c. SN Status Transfer + target SN->>target MN: 12c. SN Status Transfer + Note left of source MN: 13. Data Forwarding + source MN-->>target MN: 13. Data Forwarding + Note left of target MN: 14. Path Switch Request + target MN->>MME: 14. Path Switch Request + Note left of MME: 15. Bearer Modification + MME->>S-GW: 15. Bearer Modification + Note left of S-GW: 16a. New Path (MN terminated bearer) + S-GW-->>target MN: 16a. New Path (MN terminated bearer) + Note left of target MN: 16b. New Path (SN terminated bearer) + target MN-->>target SN: 16b. New Path (SN terminated bearer) + Note left of target MN: 17. Path Switch Request Acknowledge + target MN->>MME: 17. Path Switch Request Acknowledge + Note left of target MN: 18. UE Context Release + target MN->>source MN: 18. UE Context Release + Note left of source MN: 19. UE Context Release + source MN->>source SN: 19. UE Context Release + +``` + +Sequence diagram for Inter-MN handover with/without MN initiated SN change. Lifelines: UE, source MN, (source) SN, (target) SN, target MN, S-GW, MME. The diagram shows the signaling flow for a handover between two Master Nodes (MN), with or without a change in the Secondary Node (SN). + +**Figure 10.7.1-1: Inter-MN handover with/without MN initiated SN change** + +Figure 10.7.1-1 shows an example signaling flow for inter-Master Node handover with or without MN initiated Secondary Node change: + +NOTE 2: For an inter-Master Node handover without Secondary Node change, the source SN and the target SN shown in Figure 10.7.1-1 are the same node. + +1. The source MN starts the handover procedure by initiating the X2 Handover Preparation procedure including both MCG and SCG configuration. The source MN includes the (source) SN UE X2AP ID, SN ID and the UE context in the (source) SN in the *Handover Request* message. + +NOTE 3: The source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration before step 1. + +2. If the target MN decides to keep the UE context in SN, the target MN sends *SgNB Addition Request* to the SN including the SN UE X2AP ID as a reference to the UE context in the SN that was established by the source MN. If the target MN decides to change the SN allowing delta configuration, the target MN sends the *SgNB Addition Request* to the target SN including the UE context in the source SN that was established by the source MN. Otherwise, the target MN may send the *SgNB Addition Request* to the target SN including neither the SN UE X2AP ID nor the UE context in the source SN that was established by the source MN. +3. The (target) SN replies with *SgNB Addition Request Acknowledge*. The (target) SN may include the indication of the full or delta RRC configuration. + +NOTE 3a: In case the target SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. + +NOTE 3b: Void. + +4. The target MN includes within the *Handover Request Acknowledge* message a transparent container to be sent to the UE as an RRC message to perform the handover, and may also provide forwarding addresses to the source + +MN. The target MN indicates to the source MN that the UE context in the SN is kept if the target MN and the SN decided to keep the UE context in the SN in step 2 and step 3. + +5. The source MN sends *SgNB Release Request* to the (source) SN including a Cause indicating MCG mobility. The (source) SN acknowledges the release request. The source MN indicates to the (source) SN that the UE context in SN is kept, if it receives the indication from the target MN. If the indication as the UE context kept in SN is included, the SN keeps the UE context. + +6. The source MN triggers the UE to apply the new configuration. + +- 7/8. The UE synchronizes to the target MN and replies with *RRCConnectionReconfigurationComplete* message. + +9. If configured with bearers requiring SCG radio resources, the UE synchronizes to the (target) SN. + +NOTE 3b1: The order the UE performs Random Access towards the MN (step 7) and performs the Random Access procedure towards the SN (step 9) is not defined. + +10. If the RRC connection reconfiguration procedure was successful, the target MN informs the (target) SN via *SgNB Reconfiguration Complete* message. + +- 11a. The SN sends the *Secondary RAT Data Usage Report* message to the source MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. + +NOTE 4: The order the source SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN/target SN is not defined. The SgNB may send the report when the transmission of the related bearer is stopped. + +- 11b. The source MN sends the *Secondary RAT Report* message to MME to provide information on the used NR resource. + +12. For bearers using RLC AM, the source MN sends the *SN Status Transfer* message, including, if needed, SN Status received from the source SN to the target MN. The target forwards the SN Status to the target SN, if needed. + +13. If applicable, data forwarding takes place from the source side. If the SN is kept, data forwarding may be omitted for SN-terminated bearers kept in the SN. + +- 14-17. The target MN initiates the S1 Path Switch procedure. + +NOTE 5: If new UL TEIDs of the S-GW are included, the target MN performs the MN initiated SN Modification procedure to provide them to the SN. + +18. The target MN initiates the UE Context Release procedure towards the source MN. + +19. Upon reception of the *UE Context Release* message, the (source) SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE context kept indication was included in the *SgNB Release Request* message in step 5. + +### 10.7.2 MR-DC with 5GC + +Inter-MN handover with/without MN initiated SN change is used to transfer UE context data from a source MN to a target MN while the UE context at the SN is kept or moved to another SN. During an Inter-Master Node handover, the target MN decides whether to keep or change the SN (or release the SN, as described in clause 10.8). Only intra-RAT Inter-Master node handover with/without SN change is supported (e.g. no transition from NGEN-DC to NR-DC). + +![Sequence diagram for Inter-MN handover with/without MN initiated SN change procedure. Lifelines: UE, source MN, (source) SN, (target) SN, (target) MN, UPF, AMF. The diagram shows 19 numbered steps of signaling between these entities. Steps 13, 14, 15, 16a, 16b, and 17 are highlighted with green dashed arrows, indicating data forwarding and path switching. Step 11b is a dashed arrow to the AMF. Step 12c is a dashed arrow from (target) SN to (target) MN.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` + +sequenceDiagram + participant UE + participant source MN + participant source SN as (source) SN + participant target SN as (target) SN + participant target MN as (target) MN + participant UPF + participant AMF + + Note right of source MN: 1. Handover Request + source MN->>target MN: 1. Handover Request + Note right of target MN: 2. SN Addition Request + target MN->>target SN: 2. SN Addition Request + Note right of target SN: 3. SN Addition Request Acknowledge + target SN->>target MN: 3. SN Addition Request Acknowledge + Note right of target MN: 3a. Xn-U Address Indication + target MN->>target SN: 3a. Xn-U Address Indication + Note right of source MN: 4. Handover Request Acknowledge + target MN->>source MN: 4. Handover Request Acknowledge + Note right of source MN: 5a. SN Release Request + source MN->>source SN: 5a. SN Release Request + Note right of source SN: 5b. SN Release Request Acknowledge + source SN->>source MN: 5b. SN Release Request Acknowledge + Note right of source MN: 5c. Xn-U Address Indication + source MN->>source SN: 5c. Xn-U Address Indication + Note right of source MN: 6. RRC reconfiguration + source MN->>UE: 6. RRC reconfiguration + Note right of UE: 7. Random Access Procedure + UE->>target MN: 7. Random Access Procedure + Note right of target MN: 8. RRC reconfiguration complete + target MN->>UE: 8. RRC reconfiguration complete + Note right of UE: 9. Random Access Procedure + UE->>target SN: 9. Random Access Procedure + Note right of target SN: 10. SN Reconfiguration Complete + target SN->>target MN: 10. SN Reconfiguration Complete + Note right of target MN: 11a. Secondary RAT Data Usage report + target MN->>source MN: 11a. Secondary RAT Data Usage report + Note right of source MN: 11b. Secondary RAT Data Usage Report + source MN-->>AMF: 11b. Secondary RAT Data Usage Report + Note right of source MN: 12a. SN Status Transfer + source MN->>source SN: 12a. SN Status Transfer + Note right of source SN: 12b. SN Status Transfer + source SN->>source MN: 12b. SN Status Transfer + Note right of target SN: 12c. SN Status Transfer + target SN-->>target MN: 12c. SN Status Transfer + Note right of source MN: 13. Data Forwarding + source MN-->>target MN: 13. Data Forwarding + Note right of target MN: 14. Path Switch Request + target MN->>AMF: 14. Path Switch Request + Note right of AMF: 15. Bearer Modification + AMF->>target MN: 15. Bearer Modification + Note right of target MN: 16a. New Path (MN terminated bearer) + target MN-->>UPF: 16a. New Path (MN terminated bearer) + Note right of target SN: 16b. New Path (SN terminated bearer) + target SN-->>UPF: 16b. New Path (SN terminated bearer) + Note right of target MN: 17. Path Switch Request Acknowledge + target MN->>AMF: 17. Path Switch Request Acknowledge + Note right of source MN: 18. UE Context Release + target MN->>source MN: 18. UE Context Release + Note right of source MN: 19. UE Context Release + source MN->>source SN: 19. UE Context Release + +``` + +Sequence diagram for Inter-MN handover with/without MN initiated SN change procedure. Lifelines: UE, source MN, (source) SN, (target) SN, (target) MN, UPF, AMF. The diagram shows 19 numbered steps of signaling between these entities. Steps 13, 14, 15, 16a, 16b, and 17 are highlighted with green dashed arrows, indicating data forwarding and path switching. Step 11b is a dashed arrow to the AMF. Step 12c is a dashed arrow from (target) SN to (target) MN. + +**Figure 10.7.2-1: Inter-MN handover with/without MN initiated SN change procedure** + +Figure 10.7.2-1 shows an example signalling flow for inter-MN handover with or without MN initiated SN change: + +NOTE 1: For an Inter-Master Node handover without Secondary Node change, the source SN and the target SN shown in Figure 10.7.2-1 are the same node. + +1. The source MN starts the handover procedure by initiating the Xn Handover Preparation procedure including both MCG and SCG configuration. The source MN includes the source SN UE XnAP ID, SN ID and the UE context in the source SN in the *Handover Request* message. + +NOTE 2: The source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration and SN-associated QMC configuration information and to allow provision of data forwarding related information before step 1. + +2. If the target MN decides to keep the UE context in source SN, the target MN sends *SN Addition Request* to the SN including the SN UE XnAP ID as a reference to the UE context in the SN that was established by the source MN. If the target MN decides to change the SN allowing delta configuration, the target MN sends the *SN Addition Request* to the target SN including the UE context in the source SN that was established by the source MN. Otherwise, the target MN may send the *SN Addition Request* to the target SN including neither the SN UE XnAP ID nor the UE context in the source SN that was established by the source MN. + +3. The (target) SN replies with *SN Addition Request Acknowledge*. The (target) SN may include the indication of the full or delta RRC configuration. + +NOTE 2a0: Void. + +- 3a. For SN terminated bearers using MCG resources, the target MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message. + +4. The target MN includes within the *Handover Request Acknowledge* message the MN RRC reconfiguration message to be sent to the UE in order to perform the handover, and may also provide forwarding addresses to the + +source MN. If PDU session split is performed in the target side during handover procedure, more than one data forwarding addresses corresponding to each node are included in the *Handover Request Acknowledge* message. The target MN indicates to the source MN that the UE context in the SN is kept if the target MN and the SN decided to keep the UE context in the SN in step 2 and step 3. + +5a/5b. The source MN sends *SN Release Request* message to the (source) SN including a Cause indicating MCG mobility. The (source) SN acknowledges the release request. The source MN indicates to the (source) SN that the UE context in SN is kept, if it receives the indication from the target MN. If the indication as the UE context kept in SN is included, the SN keeps the UE context. + +5c. The source MN sends XN-U Address Indication message to the (source) SN to transfer data forwarding information. More than one data forwarding addresses may be provided if the PDU session is split in the target side. + +6. The source MN triggers the UE to perform handover and apply the new configuration. + +7/8. The UE synchronizes to the target MN and replies with MN RRC reconfiguration *complete* message. + +9. If configured with bearers requiring SCG radio resources, the UE synchronizes to the (target) SN. + +NOTE 2a1: The order the UE performs Random Access towards the MN (step 7) and performs the Random Access procedure towards the SN (step 9) is not defined. + +10. If the RRC connection reconfiguration procedure was successful, the target MN informs the (target) SN via *SN Reconfiguration Complete* message. + +11a. The source SN sends the *Secondary RAT Data Usage Report* message to the source MN and includes the data volumes delivered to and received from the UE over the NR/E-UTRA radio as described in clause 10.11.2. + +NOTE 2a2: The order the source SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN/target SN is not defined. The SN may send the report when the transmission of the related QoS is stopped. + +11b. The source MN sends the *Secondary RAT Report* message to AMF to provide information on the used NR/E-UTRA resource. + +12. For bearers using RLC AM, the source MN sends the *SN Status Transfer* message to the target MN, including, if needed, SN Status received from the source SN. The target forwards the SN Status to the target SN, if needed. + +13. If applicable, data forwarding takes place from the source side. If the SN is kept, data forwarding may be omitted for SN terminated bearers or QoS flows kept in the SN. + +14-17. The target MN initiates the Path Switch procedure. If the target MN includes multiple DL TEIDs for one PDU session in the *Path Switch Request* message, multiple UL TEID of the UPF for the PDU session should be included in the *Path Switch Ack* message in case there is TEID update in UPF. + +NOTE 3: If new UL TEIDs of the UPF for SN are included, the target MN performs MN initiated SN Modification procedure to provide them to the SN. + +18. The target MN initiates the UE Context Release procedure towards the source MN. + +19. Upon reception of the *UE Context Release* message from source MN, the (source) SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE context kept indication was included in the *SN Release Request* message in step 5. + +## 10.8 Master Node to eNB/gNB Change + +### 10.8.1 EN-DC + +The Master Node to eNB Change procedure is used to transfer context data from a source MN/SN to a target eNB. + +![Sequence diagram for Master Node to eNB Change procedure. Lifelines: UE, S-MN, S-SN, T-eNB, S-GW, MME. The procedure involves 16 steps: 1. Handover Request (S-MN to T-eNB), 2. Handover Request Acknowledge (T-eNB to S-MN), 3a. SgNB Release Request (S-MN to S-SN), 3b. SgNB Release Request Acknowledge (S-SN to S-MN), 4. RRCConnectionReconfiguration (S-MN to UE), 5. Random Access Procedure (UE to T-eNB), 6. RRCConnectionReconfigurationComplete (UE to S-MN), 7a. SN Status Transfer (S-MN to S-SN), 7b. SN Status Transfer (S-SN to T-eNB), 8. Data Forwarding (S-SN to T-eNB), 9a. Secondary RAT Data Usage report (S-MN to S-SN), 9b. Secondary RAT Data Usage Report (S-SN to T-eNB), 10. Path Switch Request (T-eNB to MME), 11. Bearer Modification (MME to S-GW), 12. End Marker Packet (S-SN to T-eNB), 13. New Path (S-GW to T-eNB), 14. Path Switch Request Acknowledge (MME to T-eNB), 15. UE Context Release (T-eNB to S-MN), 16. UE Context Release (S-MN to S-SN).](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +Sequence diagram for Master Node to eNB Change procedure. Lifelines: UE, S-MN, S-SN, T-eNB, S-GW, MME. The procedure involves 16 steps: 1. Handover Request (S-MN to T-eNB), 2. Handover Request Acknowledge (T-eNB to S-MN), 3a. SgNB Release Request (S-MN to S-SN), 3b. SgNB Release Request Acknowledge (S-SN to S-MN), 4. RRCConnectionReconfiguration (S-MN to UE), 5. Random Access Procedure (UE to T-eNB), 6. RRCConnectionReconfigurationComplete (UE to S-MN), 7a. SN Status Transfer (S-MN to S-SN), 7b. SN Status Transfer (S-SN to T-eNB), 8. Data Forwarding (S-SN to T-eNB), 9a. Secondary RAT Data Usage report (S-MN to S-SN), 9b. Secondary RAT Data Usage Report (S-SN to T-eNB), 10. Path Switch Request (T-eNB to MME), 11. Bearer Modification (MME to S-GW), 12. End Marker Packet (S-SN to T-eNB), 13. New Path (S-GW to T-eNB), 14. Path Switch Request Acknowledge (MME to T-eNB), 15. UE Context Release (T-eNB to S-MN), 16. UE Context Release (S-MN to S-SN). + +**Figure 10.8.1-1: Master Node to eNB Change procedure** + +Figure 10.8.1-1 shows an example signalling flow for the Master Node to eNB Change procedure: + +1. The source MN starts the MN to eNB Change procedure by initiating the X2 Handover Preparation procedure, including both MCG and SCG configuration. + +NOTE 1: The source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration before step 1. + +2. The target eNB includes the field in HO command which releases SCG configuration, and may also provide forwarding addresses to the source MN. +3. If the allocation of target eNB resources was successful, the MN initiates the release of the source SN resources towards the source SN including a Cause indicating MCG mobility. The SN acknowledges the release request. If data forwarding is needed, the MN provides data forwarding addresses to the source SN. Reception of the *SgNB Release Request* message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. + +NOTE 1a: In case the handover is a conditional handover, step 3a and step 3b are performed after the source MN receives an indication that the UE has successfully accessed one of the potential target eNB(s) as described in step 11a in Figure 10.1.2.1a-1n TS 36.300 [2], i.e., after step 6 in Figure 10.8.1-1. + +NOTE 1b: In case the handover is a conditional handover, the Data Forwarding Address Indication procedure is executed right after step 2. This Data Forwarding Address Indication procedure notifies conditional handover to the source SN, for which it may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an *EARLY STATUS TRANSFER* message to the source MN. Separate Data Forwarding Address Indication procedures may be invoked to provide different forwarding addresses of the prepared conditional handovers. In this case, it is up to the source MN and SN implementations to make sure that the *EARLY STATUS TRANSFER* message(s) from the source SN, if any, is forwarded to the right target destination. The Data Forwarding Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some SN-terminated bearers if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional handovers. If applicable, the normal data forwarding and *SN STATUS TRANSFER* message would follow from the source SN once it receives the *SgNB Release Request* message of the step 3a that is performed after step 6. + +4. The MN triggers the UE to apply the new configuration. Upon receiving the new configuration, the UE releases the entire SCG configuration. + +- 5/6. The UE synchronizes to the target eNB. + +7. For SN terminated bearers using RLC AM, the SN sends the *SN Status Transfer* message, which the source MN sends then to the target eNB. + +8. If applicable, data forwarding takes place from the source side. + +9a. The source SN sends the *Secondary RAT Data Usage Report* message to the source MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. + +NOTE 2: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. + +9b. The source MN sends the *Secondary RAT Report* message to MME to provide information on the used NR resource. + +10-14. The target eNB initiates the S1 Path Switch procedure. + +15. The target eNB initiates the UE Context Release procedure towards the source MN. + +16. Upon reception of the *UE Context Release* message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +NOTE 3: Inter-system HO from E-UTRA with EN-DC configuration to NR or to E-UTRA connected to 5GC is also supported. + +### 10.8.2 MR-DC with 5GC + +The MN to ng-eNB/gNB Change procedure is used to transfer UE context data from a source MN/SN to a target ng-eNB/gNB. Both the cases where the source MN and the target node belong to the same RAT (i.e. they are both ng-eNBs or both gNBs) and the cases where the source MN and the target node belong to different RATs are supported. + +NOTE 0: Inter-system HO from ng-eNB/gNB MN to eNB is also supported. + +![Sequence diagram of the MN to ng-eNB/gNB Change procedure. The diagram shows the interaction between UE, S-MN, S-SN, T-Ng-eNB/gNB, UPF, and AMF. The procedure starts with a Handover Request from S-MN to T-Ng-eNB/gNB, followed by a Handover Request Acknowledge. Then, S-MN sends SN Release Request, SN Release Request Acknowledge, and Xn-U Address Indication to S-SN. S-MN sends RRC reconfiguration to UE, which performs Random Access Procedure and RRC reconfiguration complete. S-MN sends SN Status Transfer to T-Ng-eNB/gNB. S-SN sends Data Forwarding and Secondary RAT Data Usage Report to S-MN. S-MN sends Secondary RAT Report to AMF. T-Ng-eNB/gNB sends Path Switch Request to AMF, which sends Bearer Modification to UPF. S-MN sends End Marker Packet to S-SN. S-SN sends New Path to T-Ng-eNB/gNB. T-Ng-eNB/gNB sends Path Switch Request Acknowledge to AMF. T-Ng-eNB/gNB sends UE Context Release to S-MN, which sends UE Context Release to S-SN.](db730b8d3402ded94362bb3037b985ed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant S-MN + participant S-SN + participant T-Ng-eNB/gNB + participant UPF + participant AMF + + S-MN->>T-Ng-eNB/gNB: 1. Handover Request + T-Ng-eNB/gNB-->>S-MN: 2. Handover Request Acknowledge + S-MN->>S-SN: 3a. SN Release Request + S-SN-->>S-MN: 3b. SN Release Request Acknowledge + S-MN->>S-SN: 3c. Xn-U Address Indication + S-MN->>UE: 4. RRC reconfiguration + UE->>S-MN: 5. Random Access Procedure + S-MN->>T-Ng-eNB/gNB: 6. RRC reconfiguration complete + S-MN->>T-Ng-eNB/gNB: 7a. SN Status Transfer + T-Ng-eNB/gNB-->>S-MN: 7b. SN Status Transfer + S-SN-->>S-MN: 8. Data Forwarding + S-SN-->>T-Ng-eNB/gNB: 8. Data Forwarding + S-SN->>S-MN: 9a. Secondary RAT Data Usage report + S-MN-->>AMF: 9b. Secondary RAT Data Usage Report + T-Ng-eNB/gNB->>AMF: 10. Path Switch Request + AMF->>UPF: 11. Bearer Modification + S-MN-->>S-SN: 12. End Marker Packet + S-SN-->>T-Ng-eNB/gNB: 13. New Path + T-Ng-eNB/gNB->>AMF: 14. Path Switch Request Acknowledge + T-Ng-eNB/gNB->>S-MN: 15. UE Context Release + S-MN->>S-SN: 16. UE Context Release + +``` + +Sequence diagram of the MN to ng-eNB/gNB Change procedure. The diagram shows the interaction between UE, S-MN, S-SN, T-Ng-eNB/gNB, UPF, and AMF. The procedure starts with a Handover Request from S-MN to T-Ng-eNB/gNB, followed by a Handover Request Acknowledge. Then, S-MN sends SN Release Request, SN Release Request Acknowledge, and Xn-U Address Indication to S-SN. S-MN sends RRC reconfiguration to UE, which performs Random Access Procedure and RRC reconfiguration complete. S-MN sends SN Status Transfer to T-Ng-eNB/gNB. S-SN sends Data Forwarding and Secondary RAT Data Usage Report to S-MN. S-MN sends Secondary RAT Report to AMF. T-Ng-eNB/gNB sends Path Switch Request to AMF, which sends Bearer Modification to UPF. S-MN sends End Marker Packet to S-SN. S-SN sends New Path to T-Ng-eNB/gNB. T-Ng-eNB/gNB sends Path Switch Request Acknowledge to AMF. T-Ng-eNB/gNB sends UE Context Release to S-MN, which sends UE Context Release to S-SN. + +Figure 10.8.2-1: MN to ng-eNB/gNB Change procedure + +Figure 10.8.2-1 shows an example signalling flow for the MN to ng-eNB/gNB Change procedure: + +1. The source MN starts the MN to ng-eNB/gNB Change procedure by initiating the Xn Handover Preparation procedure, including both MCG and SCG configuration. + +NOTE 1: The source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration and to allow provision of data forwarding related information before step 1. + +2. The target ng-eNB/gNB includes the field in HO command which releases the SCG configuration, and may also provide forwarding addresses to the source MN. +3. If the resource allocation of target ng-eNB/gNB was successful, the MN initiates the release of the source SN resources towards the source SN including a Cause indicating MCG mobility. The SN acknowledges the release request. If data forwarding is needed, the MN provides data forwarding addresses to the source SN. Reception of the *SN Release Request* message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. + +NOTE 1a: In case the handover is a conditional handover, step 3a and step 3b are performed after the source MN receives an indication that the UE has successfully accessed one of the potential target gNB(s) as described in step 8a in Figure 9.2.3.4.2-1 in TS 38.300 [3], i.e., after step 6 in Figure 10.8.2-1. + +NOTE 1b: In case the handover is a conditional handover, the step 3c is executed right after step 2. The *Xn-U Address Indication* message notifies conditional handover to the source SN, for which it may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an *EARLY STATUS TRANSFER* message to the source MN. Separate Xn-U Address Indication procedures may be invoked to provide different forwarding addresses of the prepared conditional handovers. In this case, it is up to the source MN and SN implementations to make sure that the EARLY STATUS TRANSFER message(s) from the source SN, if any, is forwarded to the right target destination. The Xn-U Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some SN-terminated bearers if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional handovers. If applicable, the normal data forwarding and *SN STATUS TRANSFER* message would follow from the source SN once it receives the *SN Release Request* message of the step 3a that is performed after step 6. In case the step 3c Xn-U Address Indication procedure corresponding to the conditional handover that the UE successfully accessed was rejected by the source SN, the source MN re-sends it after the step 3b that is performed after step 6. + +4. The MN triggers the UE to perform HO and apply the new configuration. Upon receiving the new configuration, the UE releases the entire SCG configuration. + +5/6. The UE synchronizes to the target ng-eNB/gNB. + +7. If PDCP termination point is changed for bearers using RLC AM, the SN sends the *SN Status Transfer* message, which the source MN sends then to the target ng-eNB/gNB. + +8. If applicable, data forwarding takes place from the source side. + +- 9a. The source SN sends the *Secondary RAT Data Usage Report* message to the source MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. + +NOTE 2: The order the SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. + +- 9b. The source MN sends the *Secondary RAT Report* message to AMF to provide information on the used NR/E-UTRA resource. + +- 10-14. The target ng-eNB/gNB initiates the Path Switch procedure. + +15. The target ng-eNB/gNB initiates the UE Context Release procedure towards the source MN. + +16. Upon reception of the *UE Context Release* message from the MN, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +## 10.9 eNB/gNB to Master Node change + +### 10.9.1 EN-DC + +The eNB to Master Node change procedure is used to transfer context data from a source eNB to a target MN that adds an SN during the handover. + +![Sequence diagram for eNB to Master Node change procedure. Lifelines: UE, S-eNB, T-SN, T-MN, S-GW, MME. The sequence shows the preparation, execution, and completion of the handover, including RRC reconfiguration, random access, and data forwarding.](c2f36c545b190860d04e1d84e58d22cc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant S-eNB + participant T-SN + participant T-MN + participant S-GW + participant MME + + Note right of S-eNB: 1. Handover Request + S-eNB->>T-MN: 1. Handover Request + Note right of T-MN: 2. SgNB Addition Request + T-MN->>T-SN: 2. SgNB Addition Request + Note right of T-SN: 3. SgNB Addition Request Ack + T-SN->>T-MN: 3. SgNB Addition Request Ack + Note right of T-MN: 4. Handover Request Acknowledge + T-MN->>S-eNB: 4. Handover Request Acknowledge + Note right of S-eNB: 5. RRCConnectionReconfiguration + S-eNB->>UE: 5. RRCConnectionReconfiguration + Note right of UE: 6. Random Access Procedure + UE->>T-MN: 6. Random Access Procedure + Note right of T-MN: 7. RRCConnectionReconfigurationComplete + T-MN->>UE: 7. RRCConnectionReconfigurationComplete + Note right of UE: 8. Random Access Procedure + UE->>T-SN: 8. Random Access Procedure + Note right of T-SN: 9. SgNB Reconfiguration Complete + T-SN->>T-MN: 9. SgNB Reconfiguration Complete + Note right of S-eNB: 10. SN Status Transfer + S-eNB->>T-MN: 10. SN Status Transfer + Note right of T-MN: 10a. SN Status Transfer + T-MN->>T-SN: 10a. SN Status Transfer + Note right of S-eNB: 11. Data Forwarding + S-eNB-->>T-MN: 11. Data Forwarding + Note right of T-MN: 12. Path Switch Request + T-MN->>MME: 12. Path Switch Request + Note right of MME: 13. Bearer Modification + MME->>T-MN: 13. Bearer Modification + Note right of T-MN: 14a. New Path (MN terminated bearer) + T-MN-->>S-GW: 14a. New Path (MN terminated bearer) + Note right of T-MN: 14b. New Path (SN terminated bearer) + T-MN-->>T-SN: 14b. New Path (SN terminated bearer) + Note right of T-MN: 15. Path Switch Request Acknowledge + T-MN->>MME: 15. Path Switch Request Acknowledge + Note right of S-eNB: 16. UE Context Release + S-eNB->>T-MN: 16. UE Context Release + +``` + +Sequence diagram for eNB to Master Node change procedure. Lifelines: UE, S-eNB, T-SN, T-MN, S-GW, MME. The sequence shows the preparation, execution, and completion of the handover, including RRC reconfiguration, random access, and data forwarding. + +Figure 10.9.1-1: eNB to Master Node change + +Figure 10.9.1-1 shows an example signaling flow for eNB to Master Node change: + +1. The source eNB starts the handover procedure by initiating the X2 Handover Preparation procedure. +2. The target MN sends *SgNB Addition Request* to the target SN. +3. The target SN replies with *SgNB Addition Request Acknowledge*. If data forwarding is needed, the target SN provides forwarding addresses to the target MN. + +NOTE 0: Void. + +4. The target MN includes within the *Handover Request Acknowledge* message a transparent container to be sent to the UE as an E-UTRA RRC message, including a NR RRC configuration message which also includes the SCG configuration, to perform the handover, and may also provide forwarding addresses to the source eNB. + +5. The source eNB triggers the UE to apply the new configuration. + +- 6/7. The UE synchronizes to the target MN and replies with *RRCConnectionReconfigurationComplete* message. + +8. If configured with bearers requiring SCG radio resources, the UE synchronizes to the target SN. + +NOTE 0: The order the UE performs Random Access towards the target MN (step 6) and performs the Random Access procedure towards the target SN (step 8) is not defined. + +9. If the RRC connection reconfiguration procedure was successful, the target MN informs the target SN. + +10. For bearers using RLC AM, the source eNB sends the *SN Status Transfer* message, which the target MN forwards then to the target SN, if needed. + +11. Data forwarding from the source eNB takes place. + +12-15. The target MN initiates the S1 Path Switch procedure. + +NOTE 1: If new UL TEIDs of the S-GW are included, the target MN performs MN initiated SN Modification procedure to provide them to the target SN. + +16. The target MN initiates the *UE Context Release* procedure towards the source eNB. + +NOTE 2: Void. + +NOTE 3: Void. + +### 10.9.2 MR-DC with 5GC + +The ng-eNB/gNB to MN change procedure is used to transfer UE context data from a source ng-eNB/gNB to a target MN that adds an SN during the handover. Only the cases where the source node and the target MN belong to the same RAT (i.e. they are both ng-eNBs or both gNBs) are supported. + +![Sequence diagram of the ng-eNB/gNB to MN change procedure. Lifelines: UE, S-ng-eNB/gNB, T-SN, T-MN, UPF, AMF. The sequence shows the preparation, execution, and completion of the handover, including Xn messages, RRC signaling, and the Path Switch procedure with the UPF and AMF.](747516f5861a0ddf31e3851da8e34b95_img.jpg) + +``` + +sequenceDiagram + participant UE + participant S-ng-eNB/gNB + participant T-SN + participant T-MN + participant UPF + participant AMF + + S-ng-eNB/gNB->>T-MN: 1. Handover Request + T-MN->>T-SN: 2. SN Addition Request + T-SN->>T-MN: 3. SN Addition Request Ack + T-MN-->>T-SN: 3a. Xn-U Address Indication + T-MN->>S-ng-eNB/gNB: 4. Handover Request Acknowledge + S-ng-eNB/gNB->>UE: 5. RRC reconfiguration message + UE->>S-ng-eNB/gNB: 6. Random Access Procedure + S-ng-eNB/gNB->>T-MN: 7. RRC reconfiguration complete message + UE->>T-SN: 8. Random Access Procedure + T-SN->>T-MN: 9. SN Reconfiguration Complete + T-MN->>S-ng-eNB/gNB: 10. SN Status Transfer + S-ng-eNB/gNB-->>T-MN: 10a. SN Status Transfer + S-ng-eNB/gNB-->>UPF: 11. Data Forwarding + T-MN->>AMF: 12. Path Switch Request + AMF->>UPF: 13. Bearer Modification + UPF-->>T-MN: 14a. New Path (MN terminated bearer) + UPF-->>T-SN: 14b. New Path (SN terminated bearer) + T-MN->>AMF: 15. Path Switch Request Acknowledge + T-MN->>S-ng-eNB/gNB: 16. UE Context Release + +``` + +Sequence diagram of the ng-eNB/gNB to MN change procedure. Lifelines: UE, S-ng-eNB/gNB, T-SN, T-MN, UPF, AMF. The sequence shows the preparation, execution, and completion of the handover, including Xn messages, RRC signaling, and the Path Switch procedure with the UPF and AMF. + +Figure 10.9.2-1: ng-eNB/gNB to MN change procedure + +Figure 10.9.2-1 shows an example signalling flow for ng-eNB/gNB to MN change: + +1. The source ng-eNB/gNB starts the handover procedure by initiating the Xn Handover Preparation procedure. +2. The target MN sends *SN Addition Request* to the target SN. +3. The target SN replies with *SN Addition Request Acknowledge*. If data forwarding is needed, the target SN provides forwarding addresses to the target MN. + +NOTE 0: Void. + +- 3a. For SN terminated bearers using MCG resources, the target MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message. +4. The target MN includes within the *Handover Request Acknowledge* message the SN RRC reconfiguration message to be sent to the UE that includes the SCG configuration to perform the handover, and may also provide forwarding addresses to the source ng-eNB/gNB. +5. The source ng-eNB/gNB triggers the UE to perform handover and apply the new configuration. + +6/7. The UE synchronizes to the target MN and replies with MN RRC reconfiguration complete message including the SN RRC reconfiguration complete message. + +8. If configured with bearers requiring SCG radio resources, the UE synchronizes to the target SN. + +NOTE 1: The order the UE performs Random Access towards the target MN (step 6) and performs the Random Access procedure towards the target SN (step 8) is not defined. + +9. If the RRC connection reconfiguration procedure was successful, the target MN informs the target SN via *SN Reconfiguration Complete* message. + +10. For bearers using RLC AM, the source ng-eNB/gNB sends the *SN Status Transfer* message, which the target MN forwards then to the target SN, if needed. + +11. Data forwarding from the source ng-eNB/gNB takes place. + +12-15. The target MN initiates the PDU Session Path Switch procedure. + +NOTE 2: If new UL TEIDs of the UPF are included, the target MN performs MN initiated SN Modification procedure to provide them to the target SN. + +16. The target MN initiates the *UE Context Release* procedure towards the source ng-eNB/gNB. + +## 10.10 RRC Transfer + +### 10.10.1 EN-DC + +The RRC Transfer procedure is used to deliver an RRC message, encapsulated in a PDCP PDU between the MN and the SN (and vice versa) so that it may be forwarded to/from the UE using split SRB. The RRC transfer procedure is also used for: + +- providing an NR measurement report, NR failure information, NR UE assistance information or intra-SN CPC execution completion from the UE to the SN via the MN. If UE is IAB-MT, providing NR IAB other information from the IAB-MT to the SN via the MN; +- providing MCG failure information from the UE to the MN via the SN and an RRC reconfiguration, or release, or an inter-RAT handover command from the MN to the UE via the SN. + +Additional details of the RRC transfer procedure are defined in TS 36.423 [9]. + +#### Split SRB: + +![Sequence diagram illustrating the RRC Transfer procedure for the split SRB (DL operation). The diagram shows five entities: UE, MN, SN, S-GW, and MME. The sequence of messages is: 1. RRC Transfer from MN to SN (solid line); 2. RLC SDU from SN to UE (solid line); 3. RRC Transfer from SN to MN (dashed line).](0bc2dbdde1fd164bcb295b4f6ddbacc8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + Note left of UE: + MN->>SN: 1. RRC Transfer + SN->>UE: 2. RLC SDU + SN-->>MN: 3. RRC Transfer + +``` + +Sequence diagram illustrating the RRC Transfer procedure for the split SRB (DL operation). The diagram shows five entities: UE, MN, SN, S-GW, and MME. The sequence of messages is: 1. RRC Transfer from MN to SN (solid line); 2. RLC SDU from SN to UE (solid line); 3. RRC Transfer from SN to MN (dashed line). + +**Figure 10.10.1-1: RRC Transfer procedure for the split SRB (DL operation)** + +Figure 10.10.1-1 shows an example signaling flow for the DL RRC Transfer in case of the split SRB: + +1. The MN, when it decides to use the split SRBs, starts the procedure by initiating the RRC Transfer procedure. The MN encapsulates the RRC message in a PDCP-C PDU and ciphers with own keys. + +NOTE: The usage of the split SRBs shall be indicated in the Secondary Node Addition procedure or Modification procedure. + +2. The SN forwards the RRC message to the UE. +3. The SN may send PDCP delivery acknowledgement of the RRC message forwarded in step 2. + +![Sequence diagram for RRC Transfer procedure for the split SRB (UL operation).](64323b705244afc70bf77babdacb6ce5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + Note left of UE: 1. RLC SDU + UE->>SN: 1. RLC SDU + Note right of SN: 2. RRC Transfer + SN->>MN: 2. RRC Transfer + +``` + +The diagram shows a sequence of messages between five entities: UE, MN, SN, S-GW, and MME. The first message, labeled '1. RLC SDU', is sent from the UE to the SN. The second message, labeled '2. RRC Transfer', is sent from the SN to the MN. The S-GW and MME are shown but do not participate in this specific sequence. + +Sequence diagram for RRC Transfer procedure for the split SRB (UL operation). + +**Figure 10.10.1-2: RRC Transfer procedure for the split SRB (UL operation)** + +Figure 10.10.1-2 shows an example signaling flow for the UL RRC Transfer in case of the split SRB: + +1. When the UE provides response to the RRC message, it sends it to the SN. +2. The SN initiates the RRC Transfer procedure, in which it transfers the received PDCP-C PDU with encapsulated RRC message. + +**NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion:** + +![Sequence diagram for RRC Transfer procedure for NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion.](7b18671bc31881a5c474883bf6a300fd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + Note left of UE: 1. ULInformationTransferMRDC + UE->>MN: 1. ULInformationTransferMRDC + Note right of MN: 2. RRC Transfer + MN->>SN: 2. RRC Transfer + +``` + +The diagram shows a sequence of messages between five entities: UE, MN, SN, S-GW, and MME. The first message, labeled '1. ULInformationTransferMRDC', is sent from the UE to the MN. The second message, labeled '2. RRC Transfer', is sent from the MN to the SN. The S-GW and MME are shown but do not participate in this specific sequence. + +Sequence diagram for RRC Transfer procedure for NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion. + +**Figure 10.10.1-3: RRC Transfer procedure for NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion** + +Figure 10.10.1-3 shows an example signaling flow for RRC Transfer in case of the forwarding of the NR measurement report, NR failure information, NR IAB other information from the UE, NR UE assistance information or intra-SN CPC execution completion: + +1. When the UE sends a measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion, it sends it to the MN in a container within *ULInformationTransferMRDC* message as specified in TS 36.331 [10]. +2. The MN initiates the RRC Transfer procedure, in which it transfers the received NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion as an octet string. + +**MCG failure information and RRC Reconfiguration / RRC Release / inter-RAT handover command over SRB3:** + +![Sequence diagram showing the RRC Transfer procedure for MCG failure information. The diagram involves five entities: UE, MN, SN, S-GW, and MME. The sequence of messages is: 1. UE sends ULInformationTransferMRDC (EUTRA MCGFailureInformation) to SN; 2. SN sends RRC Transfer to MN; 3. MN sends RRC Transfer to SN; 4. SN sends DLInformationTransferMRDC (EUTRA RRC message) to UE.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + Note left of UE: + UE->>SN: 1. ULInformationTransferMRDC (EUTRA MCGFailureInformation) + SN->>MN: 2. RRC Transfer + MN-->>SN: 3. RRC Transfer + SN-->>UE: 4. DLInformationTransferMRDC (EUTRA RRC message) + +``` + +Sequence diagram showing the RRC Transfer procedure for MCG failure information. The diagram involves five entities: UE, MN, SN, S-GW, and MME. The sequence of messages is: 1. UE sends ULInformationTransferMRDC (EUTRA MCGFailureInformation) to SN; 2. SN sends RRC Transfer to MN; 3. MN sends RRC Transfer to SN; 4. SN sends DLInformationTransferMRDC (EUTRA RRC message) to UE. + +**Figure 10.10.1-4: RRC Transfer procedure for MCG failure information** + +Figure 10.10.1-4 shows an example signaling flow for RRC Transfer in case of the forwarding of the MCG failure information from the UE: + +1. When the UE sends EUTRA *MCGFailureInformation* message over SRB3, it sends it to the SN in a container within *ULInformationTransferMRDC* message as specified in TS 38.331 [4]. +2. The SN initiates the RRC Transfer procedure, in which it transfers the received EUTRA *MCGFailureInformation* message as an octet string. +3. The MN initiates the RRC Transfer procedure, in which it transfers the EUTRA *RRCConnectionReconfiguration* message, or EUTRA *RRCConnectionRelease* message, or *MobilityFromEUTRACommand* message as an octet string. +4. The SN sends the received EUTRA RRC message to the UE over SRB3 in a container within *DLInformationTransferMRDC*, message as specified in TS 38.331 [4]. + +### 10.10.2 MR-DC with 5GC + +The RRC Transfer procedure is used to deliver an RRC message, encapsulated in a PDCP PDU between the MN and the SN (and vice versa) so that it may be forwarded to/from the UE using split SRB. The RRC transfer procedure is also used for: + +- providing a SN measurement report, failure information report, SN UE assistance information or intra-SN CPC execution completion from the UE to the SN. If UE is IAB-MT, providing NR IAB other information from the IAB-MT to the SN when the IAB-donor is the SN; +- providing MCG failure information from the UE to the MN via the SN and an RRC reconfiguration, or release, or an inter-RAT handover command from the MN to the UE via the SN; +- providing F1-C traffic from an IAB-node to the MN via the SN, or F1-C traffic from the MN to an IAB-node via the SN. + +Additional details of the RRC transfer procedure are defined in TS 38.423 [5]. + +#### Split SRB: + +![Sequence diagram for RRC Transfer procedure for split SRB (DL operation).](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +A sequence diagram showing the interaction between five entities: UE, MN, SN, UPF, and AMF. The sequence of messages is as follows: 1. MN sends an 'RRC Transfer' message to SN. 2. SN sends an 'RLC SDU' message to UE. 3. SN sends an 'RRC Transfer' message to MN. The arrows indicate the direction of the messages between the entities. + +Sequence diagram for RRC Transfer procedure for split SRB (DL operation). + +**Figure 10.10.2-1: RRC Transfer procedure for split SRB (DL operation)** + +Figure 10.10.2-1 shows an example signaling flow for DL RRC Transfer in case of the split SRB: + +1. The MN, when it decides to use the split SRBs, starts the procedure by initiating the RRC Transfer procedure. The MN encapsulates the RRC message in a PDCP PDU and ciphers with own keys. + +NOTE: The usage of the split SRBs shall be indicated in the Secondary Node Addition procedure or Modification procedure. + +2. The SN forwards the RRC message to the UE. +3. The SN may send PDCP delivery acknowledgement of the RRC message forwarded in step 2. + +![Sequence diagram for RRC Transfer procedure for split SRB (UL operation).](c6e0b9030f9fb81435eaf9cb71532614_img.jpg) + +A sequence diagram showing the interaction between five entities: UE, MN, SN, UPF, and AMF. The sequence of messages is as follows: 1. UE sends an 'RLC SDU' message to SN. 2. SN sends an 'RRC Transfer' message to MN. The arrows indicate the direction of the messages between the entities. + +Sequence diagram for RRC Transfer procedure for split SRB (UL operation). + +**Figure 10.10.2-2: RRC Transfer procedure for split SRB (UL operation)** + +Figure 10.10.2-2 shows an example signaling flow for UL RRC Transfer in case of the split SRB: + +1. When the UE provides response to the RRC message, it sends it to the SN. +2. The SN initiates the RRC Transfer procedure, in which it transfers the received PDCP PDU with encapsulated RRC message. + +**SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information:** + +![Sequence diagram for RRC Transfer procedure for SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information. The diagram shows five lifelines: UE, MN, SN, UPF, and AMF. Step 1: UE sends ULInformationTransferMRDC to MN. Step 2: MN sends RRC Transfer to SN.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + Note left of UE: + UE->>MN: 1. ULInformationTransferMRDC + MN->>SN: 2. RRC Transfer + +``` + +Sequence diagram for RRC Transfer procedure for SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information. The diagram shows five lifelines: UE, MN, SN, UPF, and AMF. Step 1: UE sends ULInformationTransferMRDC to MN. Step 2: MN sends RRC Transfer to SN. + +**Figure 10.10.2-3: RRC Transfer procedure for SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information** + +Figure 10.10.2-3 shows an example signaling flow for RRC Transfer in case of the forwarding of the SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information from the UE: + +1. When the UE sends an SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information it sends it to the MN in a container called *ULInformationTransferMRDC* message as specified in TS 38.331 [4]. +2. The MN initiates the RRC Transfer procedure, in which it transfers the received SN measurement report, failure information, SN UE assistance information, intra-SN CPC execution completion or IAB other information as an octet string. + +#### **MCG failure information and RRC Reconfiguration / RRC Release / inter-RAT handover command over SRB3:** + +![Sequence diagram for RRC Transfer procedure for MCG failure information. The diagram shows five lifelines: UE, MN, SN, UPF, and AMF. Step 1: UE sends ULInformationTransferMRDC (MCGFailureInformation) to SN. Step 2: SN sends RRC Transfer to MN. Step 3: MN sends RRC Transfer to SN. Step 4: SN sends DLInformationTransferMRDC (RRC message) to UE.](8a0a9aa5fac5d73eefb772afd44649f6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + Note left of UE: + UE->>SN: 1. ULInformationTransferMRDC (MCGFailureInformation) + SN->>MN: 2. RRC Transfer + MN->>SN: 3. RRC Transfer + SN-->>UE: 4. DLInformationTransferMRDC (RRC message) + +``` + +Sequence diagram for RRC Transfer procedure for MCG failure information. The diagram shows five lifelines: UE, MN, SN, UPF, and AMF. Step 1: UE sends ULInformationTransferMRDC (MCGFailureInformation) to SN. Step 2: SN sends RRC Transfer to MN. Step 3: MN sends RRC Transfer to SN. Step 4: SN sends DLInformationTransferMRDC (RRC message) to UE. + +**Figure 10.10.2-4: RRC Transfer procedure for MCG failure information** + +Figure 10.10.2-4 shows an example signaling flow for RRC Transfer in case of the forwarding of the MCG failure information from the UE: + +1. When the UE sends *MCGFailureInformation* message over SRB3, it sends it to the SN in a container called *ULInformationTransferMRDC* message as specified in TS 38.331 [4]. +2. The SN initiates the RRC Transfer procedure, in which it transfers the received *MCGFailureInformation* message as an octet string. +3. The MN initiates the RRC Transfer procedure, in which it transfers the *RRConnectionReconfiguration* message, or *RRReconfiguration* message, or *RRConnectionRelease* message, or *RRRelease* message, or *MobilityFromNRCommand* message, or *MobilityFromEUTRACommand* message as an octet string. +4. The SN sends the received RRC message to the UE in a container called *DLInformationTransferMRDC* message, as specified in TS 38.331 [4]. + +#### **F1-C traffic transfer:** + +![Sequence diagram showing F1-C traffic transfer procedure between IAB-MT and MN (F1-terminating node) in NR-DC. The diagram shows four steps: 1. RLC SDU (ULInformationTransfer) from IAB-MT to SN; 2. RRC Transfer from SN to MN; 3. RRC Transfer from MN to SN; 4. RLC SDU (DLInformationTransfer) from SN to IAB-MT. UPF and AMF are shown but not involved in this specific procedure.](145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg) + +``` + +sequenceDiagram + participant IAB-MT + participant MN + participant SN + participant UPF + participant AMF + Note left of IAB-MT: 1. RLC SDU (ULInformationTransfer) + IAB-MT->>SN: 1. RLC SDU (ULInformationTransfer) + Note right of SN: 2. RRC Transfer + SN->>MN: 2. RRC Transfer + Note right of MN: 3. RRC Transfer + MN->>SN: 3. RRC Transfer + Note left of SN: 4. RLC SDU (DLInformationTransfer) + SN->>IAB-MT: 4. RLC SDU (DLInformationTransfer) + +``` + +Sequence diagram showing F1-C traffic transfer procedure between IAB-MT and MN (F1-terminating node) in NR-DC. The diagram shows four steps: 1. RLC SDU (ULInformationTransfer) from IAB-MT to SN; 2. RRC Transfer from SN to MN; 3. RRC Transfer from MN to SN; 4. RLC SDU (DLInformationTransfer) from SN to IAB-MT. UPF and AMF are shown but not involved in this specific procedure. + +**Figure 10.10.2-5: Scenario 2: F1-C Traffic Transfer procedure between IAB-MT and MN (F1-terminating node) in NR-DC** + +1. The IAB-MT sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet to the SN (non-F1-terminating IAB-donor) via split SRB2 in a container within *ULInformationTransfer* message encapsulated in a PDCP PDU as specified in TS 38.331 [4]. +2. The SN initiates the RRC Transfer procedure, in which it transfers the received PDCP PDU (*ULInformationTransfer* message) including F1-AP message. +3. When the MN (F1-terminating IAB-donor) sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet, it starts the procedure by initiating the RRC Transfer procedure, if split SRB2 is determined to be used and usage of SCG path is determined. The MN sends the F1-AP message to the SN in a container within *DLInformationTransfer* message encapsulated in a PDCP PDU specified in TS 38.331 [4]. +4. The SN forwards the encapsulated *DLInformationTransfer* message in a PDCP PDU as specified in TS 38.331 [4] to IAB-MT. + +## 10.11 Secondary RAT data volume reporting + +### 10.11.1 EN-DC + +The secondary RAT data volume reporting function is used to report the data volume of secondary RAT to CN. In EN-DC, if configured, the MN reports the uplink and downlink data volumes of used NR resources to the EPC on a per EPS bearer basis as specified in TS 36.300 [2]. Periodic reporting is performed by periodically sending the *Secondary RAT Data Usage Report* messages to the MME. + +The data volume is counted by the node hosting PDCP. Downlink data volume is counted in bytes of PDCP SDUs successfully delivered to the UE over NR (for RLC AM) or transmitted to the UE over NR (for RLC UM). Uplink data volume is counted in bytes of PDCP SDUs received by the node hosting PDCP over NR. Forwarded packets shall not be counted when PDCP entity is relocated. When PDCP duplication is activated, packets shall be counted only once. + +![Sequence diagram for EN-DC secondary RAT data volume periodic reporting. Lifelines: UE, MN, SN, S-GW, MME. Step 1: SN sends 'Secondary RAT Data Usage Report' to MN (dashed arrow). Step 2: MN sends 'Secondary RAT Data Usage Report' to MME (solid arrow).](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + Note right of SN: 1. Secondary RAT Data Usage Report + SN-->>MN: 1. Secondary RAT Data Usage Report + Note right of MN: 2. Secondary RAT Data Usage Report + MN->>MME: 2. Secondary RAT Data Usage Report + +``` + +Sequence diagram for EN-DC secondary RAT data volume periodic reporting. Lifelines: UE, MN, SN, S-GW, MME. Step 1: SN sends 'Secondary RAT Data Usage Report' to MN (dashed arrow). Step 2: MN sends 'Secondary RAT Data Usage Report' to MME (solid arrow). + +**Figure 10.11.1-1: Secondary RAT data volume periodic reporting - EN-DC** + +Figure 10.11.1-1 shows an example signalling flow for secondary RAT data volume periodic reporting: + +1. If the periodic reporting is configured, then the SN periodically sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes of used NR radio resources for the related SN-terminated E-RABs. +2. The MN sends the *Secondary RAT Data Usage Report* message to MME to provide information on the used NR resource. + +NOTE: The *Secondary RAT Data Usage Report* message sent by the MN may also include secondary RAT report information of MN-terminated bearers. + +### 10.11.2 MR-DC with 5GC + +The secondary RAT data volume reporting function is used to report the data volume of secondary RAT to the 5GC. In MR-DC with 5GC, if configured, the MN reports the uplink and downlink data volumes of used secondary RAT resources to the 5GC as specified in TS 23.501 [11]. Configuration for reporting of secondary RAT data volume may happen separately for NR and E-UTRA. Secondary RAT data volume reporting indicates the secondary RAT type. For each PDU session, it contains data volumes consumed for the whole PDU Session, or for selected QoS flow, or both. Periodic reporting is performed by periodically sending the *Secondary RAT Data Usage Report* messages to the 5GC. + +The data volume is counted by the node hosting PDCP. Downlink data volume is counted in bytes of SDAP SDUs successfully delivered to the UE (for RLC AM) or transmitted to the UE (for RLC UM). Uplink data volume is counted in bytes of SDAP SDUs received by the node hosting PDCP. Forwarded packets shall not be counted when PDCP entity is relocated. When PDCP duplication is activated, packets shall be counted only once. + +![Sequence diagram for MR-DC with 5GC secondary RAT data volume periodic reporting. Lifelines: UE, MN, SN, UPF, AMF. Step 1: SN sends 'Secondary RAT Data Usage Report' to MN (dashed arrow). Step 2: MN sends 'Secondary RAT Data Usage Report' to AMF (solid arrow).](bbd36eba6bb7c4ba87608874c8c714ff_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + Note right of SN: 1. Secondary RAT Data Usage Report + SN-->>MN: 1. Secondary RAT Data Usage Report + Note right of MN: 2. Secondary RAT Data Usage Report + MN->>AMF: 2. Secondary RAT Data Usage Report + +``` + +Sequence diagram for MR-DC with 5GC secondary RAT data volume periodic reporting. Lifelines: UE, MN, SN, UPF, AMF. Step 1: SN sends 'Secondary RAT Data Usage Report' to MN (dashed arrow). Step 2: MN sends 'Secondary RAT Data Usage Report' to AMF (solid arrow). + +**Figure 10.11.2-1: Secondary RAT data volume periodic reporting - MR-DC with 5GC** + +Figure 10.11.2-1 shows an example signalling flow for secondary RAT data volume periodic reporting: + +1. For SN terminated bearers, the SN sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes of used secondary RAT resources for PDU Sessions or selected QoS flows or both + +mapped to SN-terminated bearers. If periodic reporting is configured, then the SN periodically sends the *Secondary RAT Data Usage Report* message to the MN and includes the data volumes of used radio resources. + +2. The MN sends the *Secondary RAT Data Usage Report* message to the 5GC to provide information on the used radio resources. + +NOTE: The *Secondary RAT Data Usage Report* message sent by the MN may also include secondary RAT data volumes of used secondary RAT resources for MN terminated bearers. + +## 10.12 Activity Notification + +### 10.12.1 EN-DC + +The Activity Notification function is used to report user plane activity within SN resources. It can either report inactivity or resumption of activity after inactivity was reported. In EN-DC the Activity Reporting is provided from the SN only. The MN may take further actions. + +#### EN-DC Activity Notification + +![Sequence diagram showing EN-DC Activity Notification between SN and MN.](7c57192c514175021e4560a1a46126c1_img.jpg) + +``` +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + Note right of MN: 2. MN decides to keep SN resources + SN->>MN: 1. Activity Notification (inactive) + MN->>SN: 3. Activity Notification (re-activated) +``` + +The diagram illustrates the interaction between the SN and MN for Activity Notification in EN-DC. It shows three steps: 1. The SN sends an 'Activity Notification (inactive)' message to the MN. 2. The MN decides to keep SN resources (indicated by a box). 3. The SN sends an 'Activity Notification (re-activated)' message to the MN. The UE, S-GW, and MME are shown as participants but do not have active messages in this sequence. + +Sequence diagram showing EN-DC Activity Notification between SN and MN. + +**Figure 10.12.1-1: Support of Activity Notification in EN-DC** + +Support of Activity Notification in EN-DC is used to keep the MN informed about user traffic activity in resources owned by the SN. The MN may take appropriate action upon receiving such notification. + +1. The SN informs the MN about user data inactivity of resources owned by the SN. +2. The MN decides to keep SN resources. +3. After a while the SN reports resumption of user plane activity. + +#### EN-DC with suspended RRC connection – SCG configuration released in SN + +The Activity Notification function may be used to enable EN-DC with suspended RRC connected operation. The MN node may decide, after inactivity is reported from the SN and also MN resources show no activity, to send the UE to suspended RRC connection. Resumption to RRC\_CONNECTED may take place after activity is reported from the SN for SN terminated bearers. + +![Sequence diagram showing the support of Activity Notification in EN-DC with suspended RRC connection – SCG configuration released in SN. The diagram illustrates the interaction between UE, MN, SN, S-GW, and MME. The process starts with an Activity Notification (Inactive) from SN to MN. The MN decides to send the UE to a suspended RRC connection. The MN triggers an SgNB Modification Request (release lower layers) to the SN. The SN responds with an SgNB Modification Request Acknowledge. The MN sends an RRCConnectionRelease (suspended RRC connection) to the UE. A period of suspended RRC connection occurs. Upon activity notification (Re-activated) from the SN, the MN triggers a transition from suspended RRC connection to RRC_CONNECTED. The MN decides whether to reactivate the SN terminated bearers or not. The MN triggers an SgNB Modification Request (re-establish lower layers) to the SN. The SN responds with an SgNB Modification Request Acknowledge (carry SN RRC reconfiguration message). The MN sends an RRCConnectionReconfiguration to the UE. The UE responds with an RRCConnectionReconfigurationComplete (carry SN RRC reconfiguration complete). The MN sends an SgNB Reconfiguration Complete (carry SN RRC reconfiguration complete) to the SN. Finally, a Random Access Procedure is initiated between the UE and the SN.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + + Note right of MN: 2.MN decides to send UE to suspended RRC connection + Note right of MN: 8bis. MN decides whether to reactivate the SN terminated bearers or not + + SN->>MN: 1.Activity Notification (Inactive) + MN->>SN: 3.SgNB Modification Request(release lower layers) + SN->>MN: 4.SgNB Modification Request Acknowledge + MN->>UE: 5.RRCConnectionRelease(suspended RRC connection) + Note over UE, MN: 6.Period of suspended RRC connection + SN->>MN: 7. Activity Notification (Re-activated) + Note over UE, MN: 8. Suspended RRC connection to RRC_CONNECTED transition + MN->>SN: 9.SgNB Modification Request(re-establish lower layers) + SN->>MN: 10.SgNB Modification Request Acknowledge (carry SN RRC reconfiguration message) + MN->>UE: 11.RRCConnectionReconfiguration + UE->>MN: 12.RRCConnectionReconfigurationComplete (carry SN RRC reconfiguration complete) + MN->>SN: 13.SgNB Reconfiguration Complete (carry SN RRC reconfiguration complete) + UE->>SN: 14.Random Access Procedure + +``` + +Sequence diagram showing the support of Activity Notification in EN-DC with suspended RRC connection – SCG configuration released in SN. The diagram illustrates the interaction between UE, MN, SN, S-GW, and MME. The process starts with an Activity Notification (Inactive) from SN to MN. The MN decides to send the UE to a suspended RRC connection. The MN triggers an SgNB Modification Request (release lower layers) to the SN. The SN responds with an SgNB Modification Request Acknowledge. The MN sends an RRCConnectionRelease (suspended RRC connection) to the UE. A period of suspended RRC connection occurs. Upon activity notification (Re-activated) from the SN, the MN triggers a transition from suspended RRC connection to RRC\_CONNECTED. The MN decides whether to reactivate the SN terminated bearers or not. The MN triggers an SgNB Modification Request (re-establish lower layers) to the SN. The SN responds with an SgNB Modification Request Acknowledge (carry SN RRC reconfiguration message). The MN sends an RRCConnectionReconfiguration to the UE. The UE responds with an RRCConnectionReconfigurationComplete (carry SN RRC reconfiguration complete). The MN sends an SgNB Reconfiguration Complete (carry SN RRC reconfiguration complete) to the SN. Finally, a Random Access Procedure is initiated between the UE and the SN. + +**Figure 10.12.1-2: Support of Activity Notification in EN-DC with suspended RRC connection – SCG configuration released in SN** + +Figure 10.12.1-2 shows how Activity Notification function interacts with E-UTRAN functions for suspended RRC connection and SgNB Modification procedures in order to keep the higher layer EN-DC E-UTRAN resources established for UEs in suspended RRC connection, including S1 and X2 interface C-plane, U-plane and bearer contexts established while lower layer MCG and SCG resources are released. E-UTRAN memorises the cell group configuration for MCG in order to apply delta signalling at resume, as specified in TS 36.331 [4]. After the UE has transitioned successfully back to RRC\_CONNECTED, lower layer SCG resources are established afterwards by means of RRC Connection Reconfiguration. + +1. The SN notifies the MN about user data inactivity for SN terminated bearers. +2. The MN decides to send the UE to suspended RRC connection. +- 3/4. The MN triggers the MN initiated SgNB Modification procedure, requesting the SN to release lower layers. +5. The UE is sent to suspended RRC connection. +- 6-8. After a period of suspended RRC connection, upon activity notification from the SN, the UE returns to RRC\_CONNECTED. +- 8bis. MN decides whether to reactivate the SN terminated bearers. If (e.g. due to UE mobility), MN decides not to reactivate the SN terminated bearers, it initiates the MN initiated SN release procedure and the procedure ends. +- 9/10. The MN triggers the MN initiated SgNB Modification procedure to re-establish lower layers. The SN provides configuration data within an SN RRC configuration message. +- 11-14. The RRC Connection Reconfiguration procedure commences. + +#### EN-DC with suspended RRC connection - SCG configuration suspended in SN + +The Activity Notification function may be used to enable EN-DC with suspended RRC connection operation. The MN node may decide, after inactivity is reported from the SN and also MN resources show no activity, to send the UE to suspended RRC connection, while keeping the SCG configuration. Resumption to RRC\_CONNECTED may take place after activity is reported from the SN for SN terminated bearers. + +![Sequence diagram illustrating the support of Activity Notification in EN-DC with suspended RRC connection - SCG configuration suspended in SN. The diagram shows interactions between UE, MN, SN, S-GW, and MME. The process starts with an Activity Notification (inactive) from SN to MN. The MN decides to suspend the UE's RRC connection. The MN sends an SgNB Modification Request (suspend lower layers) to the SN, which responds with an SgNB Modification Request Acknowledge. The MN then sends an RRCConnectionRelease (suspendConfig) to the UE. A 'Period of suspended RRC connection' occurs. After this, an Activity Notification (active) is received by the MN from the SN. The MN decides whether to reactivate the SN terminated bearers. If reactivation is decided, the MN sends an SgNB Modification Request (resume lower layers) to the SN, which responds with an SgNB Modification Request Acknowledge (carrying an SN RRC reconfiguration message). The MN then sends an RRCConnectionResume (restore SCG) (carrying an SN RRC reconfiguration message) to the UE. The UE responds with an RRCConnectionResumeComplete (carrying an SN RRC reconfiguration complete message). The MN then sends an SgNB Reconfiguration Complete (carrying an SN RRC reconfiguration complete) to the SN. Finally, the UE performs a Random Access Procedure towards the SN.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant S-GW + participant MME + + Note right of MN: 1. Activity Notification (inactive) + Note right of MN: 2. MN decides to send UE to suspended RRC connection + MN->>SN: 3. SgNB Modification Request(suspend lower layers) + SN-->>MN: 4. SgNB Modification Request Acknowledge + MN-->>UE: 5. RRCConnectionRelease (suspendConfig) + Note over UE, MN, SN, S-GW, MME: 6. Period of suspended RRC connection + Note right of SN: 7. Activity Notification (active) + Note right of MN: 8. MN decides whether to reactivate the SN terminated bearers or not + MN->>SN: 9. SgNB Modification Request(resume lower layers) + SN-->>MN: 10. SgNB Modification Request Acknowledge (carry SN RRC reconfiguration message) + MN-->>UE: 11. RRCConnectionResume (restore SCG) (carry SN RRC reconfiguration message) + UE-->>MN: 12. RRCConnectionResumeComplete (carry SN RRC reconfiguration complete message) + MN-->>SN: 13. SgNB Reconfiguration Complete (carry SN RRC reconfiguration complete) + UE-->>SN: 14. Random Access Procedure + +``` + +Sequence diagram illustrating the support of Activity Notification in EN-DC with suspended RRC connection - SCG configuration suspended in SN. The diagram shows interactions between UE, MN, SN, S-GW, and MME. The process starts with an Activity Notification (inactive) from SN to MN. The MN decides to suspend the UE's RRC connection. The MN sends an SgNB Modification Request (suspend lower layers) to the SN, which responds with an SgNB Modification Request Acknowledge. The MN then sends an RRCConnectionRelease (suspendConfig) to the UE. A 'Period of suspended RRC connection' occurs. After this, an Activity Notification (active) is received by the MN from the SN. The MN decides whether to reactivate the SN terminated bearers. If reactivation is decided, the MN sends an SgNB Modification Request (resume lower layers) to the SN, which responds with an SgNB Modification Request Acknowledge (carrying an SN RRC reconfiguration message). The MN then sends an RRCConnectionResume (restore SCG) (carrying an SN RRC reconfiguration message) to the UE. The UE responds with an RRCConnectionResumeComplete (carrying an SN RRC reconfiguration complete message). The MN then sends an SgNB Reconfiguration Complete (carrying an SN RRC reconfiguration complete) to the SN. Finally, the UE performs a Random Access Procedure towards the SN. + +**Figure 10.12.1-3: Support of Activity Notification in EN-DC with suspended RRC connection - SCG configuration suspended in SN** + +Figure 10.12.1-3 shows how Activity Notification function interacts with functions for suspended RRC connection and SgNB Modification procedures in order to keep the full EN-DC resources established for UEs in suspended RRC connection. When the UE transits successfully back to RRC\_CONNECTED, lower layer MCG and SCG configurations are restored or reconfigured by means of RRC Connection Resume. + +1. The SN notifies the MN about user data inactivity for SN terminated bearers. +2. The MN decides to send the UE to suspended RRC connection. +- 3/4. The MN triggers the MN initiated SN Modification procedure, requesting the SN to suspend lower layers. +5. The UE is sent to suspended RRC connection. +- 6-7. After a period of suspended RRC connection, the MN receives activity notification from the SN. +8. The MN decides whether to reactivate the SN terminated bearers. If (e.g. due to UE mobility), the MN decides not to reactivate the SN terminated bearers, it initiates the MN initiated SN release procedure, rather than the MN initiated SN modification procedure in steps 9/10. If the MN decides to return the UE to RRC\_CONNECTED, the network triggered state transition from suspended RRC connection to RRC\_CONNECTED commences. +- 9/10. The MN triggers the MN initiated SN Modification procedure to resume the SCG lower layers. If the SCG configuration needs to be updated, the SN provides the configuration data within an SN RRC configuration message. +- 11/12. The UE is instructed to resume both the MCG and the SCG. If the SCG configuration is to be updated, the new configuration is provided in the *RRCConnectionResume* message. +13. The MN informs the SN that the UE has completed the reconfiguration procedure successfully, via the *SgNB Reconfiguration Complete* message, including the SN RRC response message, if received from the UE. +14. The UE performs synchronisation towards the PSCell of the SN. + +### 10.12.2 MR-DC with 5GC + +The Activity Notification function is used to report user plane activity within SN resources or to report a RAN Paging Failure event to the SN. It can either report inactivity or resumption of activity after inactivity was reported. In MR-DC with 5GC the Activity Reporting is provided from the SN only. The MN may take further actions. RAN Paging Failure Reporting is provided from the MN only. + +#### MR-DC with 5GC Activity Notification + +![Sequence diagram showing Activity Notification in MR-DC with 5GC. The diagram involves five entities: UE, MN, SN, UPF, and AMF. The sequence of messages is: 1. SN sends an 'Activity Notification (inactive)' to MN. 2. MN performs an internal decision 'MN decides to keep SN resources'. 3. SN sends an 'Activity Notification (re-activated)' to MN.](1adc4b0458c277ba8c0e8d6f5ad15511_img.jpg) + +``` +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + Note right of MN: 2. MN decides to keep SN resources + SN->>MN: 1. Activity Notification (inactive) + SN->>MN: 3. Activity Notification (re-activated) +``` + +Sequence diagram showing Activity Notification in MR-DC with 5GC. The diagram involves five entities: UE, MN, SN, UPF, and AMF. The sequence of messages is: 1. SN sends an 'Activity Notification (inactive)' to MN. 2. MN performs an internal decision 'MN decides to keep SN resources'. 3. SN sends an 'Activity Notification (re-activated)' to MN. + +Figure 10.12.2-1: Support of Activity Notification in MR-DC with 5GC + +1. The SN notifies the MN about user data inactivity. +2. The MN decides further actions that impact SN resources (e.g. send UE to RRC\_INACTIVE, bearer reconfiguration). In the case shown, MN takes no action. +3. The SN notifies the MN that the (UE or PDU Session or QoS flow) is no longer inactive. + +#### MR-DC with 5GC with RRC\_INACTIVE – SCG configuration released in SN + +The Activity Notification function may be used to enable MR-DC with 5GC with RRC\_INACTIVE operation. The MN node may decide, after inactivity is reported from the SN and also MN resources show no activity, to send the UE to RRC\_INACTIVE. Resumption to RRC\_CONNECTED may take place after activity is reported from the SN for SN terminated bearers. + +![Sequence diagram showing the support of Activity Notification in MR-DC with 5GC with RRC_Inactive – SCG configuration released in SN. The diagram illustrates the interaction between UE, MN, SN, UPF, and AMF. The process starts with an Activity Notification (Inactive) from SN to MN. MN decides to send UE to RRC_INACTIVE and triggers an SN Modification Request (release lower layers) to SN. SN acknowledges, and MN sends an RRC release (INACTIVE) to UE. After a period of inactivity, an Activity Notification (Re-activated) is sent from SN to MN. MN triggers an RRC_INACTIVE to RRC_CONNECTED transition. MN then decides whether to reactivate the SN terminated bearers. If reactivation is needed, an SN Modification Request (re-establish lower layers) is sent to SN, which acknowledges with an SN RRC reconfiguration message. MN then sends an RRC reconfiguration to UE, which completes it. MN sends an SN Reconfiguration Complete to SN, and finally, a Random Access Procedure is initiated by UE.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + + Note right of MN: 1. Activity Notification (Inactive) + MN->>MN: 2. MN decides to send UE to RRC_INACTIVE + MN->>SN: 3. SN Modification Request(release lower layers) + SN->>MN: 4. SN Modification Request Acknowledge + MN->>UE: 5. RRC release(INACTIVE) + Note over UE, AMF: 6. Period of Inactivity + Note right of SN: 7. Activity Notification (Re-activated) + Note over UE, AMF: 8. RRC_INACTIVE to RRC_CONNECTED transition + Note right of MN: 8bis. MN decides whether to reactivate the SN terminated bearers or not + MN->>SN: 9. SN Modification Request(re-establish lower layers) + SN->>MN: 10. SN Modification Request Acknowledge (carry SN RRC reconfiguration message) + MN->>UE: 11. RRC reconfiguration + UE->>MN: 12. RRC reconfiguration complete (carry SN RRC reconfiguration complete) + MN->>SN: 13. SN Reconfiguration Complete (carry SN RRC reconfiguration complete) + UE->>SN: 14. Random Access Procedure + +``` + +Sequence diagram showing the support of Activity Notification in MR-DC with 5GC with RRC\_Inactive – SCG configuration released in SN. The diagram illustrates the interaction between UE, MN, SN, UPF, and AMF. The process starts with an Activity Notification (Inactive) from SN to MN. MN decides to send UE to RRC\_INACTIVE and triggers an SN Modification Request (release lower layers) to SN. SN acknowledges, and MN sends an RRC release (INACTIVE) to UE. After a period of inactivity, an Activity Notification (Re-activated) is sent from SN to MN. MN triggers an RRC\_INACTIVE to RRC\_CONNECTED transition. MN then decides whether to reactivate the SN terminated bearers. If reactivation is needed, an SN Modification Request (re-establish lower layers) is sent to SN, which acknowledges with an SN RRC reconfiguration message. MN then sends an RRC reconfiguration to UE, which completes it. MN sends an SN Reconfiguration Complete to SN, and finally, a Random Access Procedure is initiated by UE. + +**Figure 10.12.2-2: Support of Activity Notification in MR-DC with 5GC with RRC\_Inactive – SCG configuration released in SN** + +Figure 10.12.2-2 shows how Activity Notification function interacts with NG-RAN functions for RRC\_INACTIVE and SN Modification procedures in order to keep the higher layer MR-DC NG-RAN resources established for UEs in RRC\_INACTIVE, including NG and Xn interface C-plane, U-plane and bearer contexts established while lower layer MCG and SCG resources are released. NG-RAN memorises the cell group configuration for MCG in order to apply delta signalling at resume, as specified in TS 38.331 [4]. After the UE has transited successfully back to RRC\_CONNECTED, lower layer SCG resources are established afterwards by means of RRC Connection Reconfiguration. + +1. The SN notifies the MN about user data inactivity for SN terminated bearers. +2. The MN decides to send the UE to RRC\_INACTIVE. +- 3/4. The MN triggers the MN initiated SN Modification procedure, requesting the SN to release lower layers. +5. The UE is sent to RRC\_INACTIVE. +- 6-8. After a period of inactivity, upon activity notification from the SN, the UE returns to RRC\_CONNECTED. +- 8bis. MN decides whether to reactivate the SN terminated bearers. If (e.g. due to UE mobility), MN decides not to reactivate the SN terminated bearers, it initiates the MN initiated SN release procedure and the procedure ends. +- 9/10. The MN triggers the MN initiated SN Modification procedure to re-establish lower layers. The SN provides configuration data within an SN RRC reconfiguration message. +- 11-14. The RRC Connection Reconfiguration procedure commences. + +#### MR-DC with 5GC with RRC\_INACTIVE - SCG configuration suspended in SN + +The Activity Notification function may be used to enable MR-DC with 5GC with RRC\_INACTIVE operation. The MN node may decide, after inactivity is reported from the SN and also MN resources show no activity, to send the UE to RRC\_INACTIVE, while keeping the SCG configuration. Resumption to RRC\_CONNECTED may take place after activity is reported from the SN for SN terminated bearers. + +![Sequence diagram showing the support of Activity Notification in MR-DC with 5GC with RRC_Inactive - SCG configuration suspended in SN. The diagram involves five entities: UE, MN, SN, UPF, and AMF. The process is divided into two main parts: suspension and resumption, separated by a 'Period of Inactivity'.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + + Note right of MN: 1. Activity Notification (inactive) + Note right of MN: 2. MN decides to send UE to RRC_INACTIVE + MN->>SN: 3. SN Modification Request(suspend lower layers) + SN-->>MN: 4. SN Modification Request Acknowledge + MN->>UE: 5. RRC(Connection)Release (suspendConfig) + Note over UE, MN, SN, UPF, AMF: 6. Period of Inactivity + Note right of SN: 7. Activity Notification (active) + Note right of MN: 8. MN decides whether to reactivate the SN terminated bearers or not + MN->>SN: 9. SN Modification Request(resume lower layers) + SN-->>MN: 10. SN Modification Request Acknowledge (carry SN RRC reconfiguration message) + MN->>UE: 11. RRC(Connection)Resume (restore SCG) (carry SN RRC reconfiguration message) + UE-->>MN: 12. RRC(Connection)ResumeComplete (carry SN RRC reconfiguration complete message) + MN->>SN: 13. SN Reconfiguration Complete (carry SN RRC reconfiguration complete) + UE->>SN: 14. Random Access Procedure + +``` + +Sequence diagram showing the support of Activity Notification in MR-DC with 5GC with RRC\_Inactive - SCG configuration suspended in SN. The diagram involves five entities: UE, MN, SN, UPF, and AMF. The process is divided into two main parts: suspension and resumption, separated by a 'Period of Inactivity'. + +**Figure 10.12.2-3: Support of Activity Notification in MR-DC with 5GC with RRC\_Inactive - SCG configuration suspended in SN** + +Figure 10.12.2-3 shows how Activity Notification function interacts with NG-RAN functions for RRC\_INACTIVE and SN Modification procedures in order to keep the full MR-DC NG-RAN resources established for UEs in RRC\_INACTIVE. When the UE transits successfully back to RRC\_CONNECTED, lower layer MCG and SCG configurations are restored or reconfigured by means of RRC (Connection) Resume. + +1. The SN notifies the MN about user data inactivity for SN terminated bearers. +2. The MN decides to send the UE to RRC\_INACTIVE. +- 3/4. The MN triggers the MN initiated SN Modification procedure, requesting the SN to suspend lower layers. +5. The UE is sent to RRC\_INACTIVE. +- 6-7. After a period of inactivity, the MN receives activity notification from the SN. +8. The MN decides whether to reactivate the SN terminated bearers. If (e.g. due to UE mobility), the MN decides not to reactivate the SN terminated bearers, it initiates the MN initiated SN release procedure, rather than the MN initiated SN modification procedure in steps 9/10. If the MN decides to return the UE to RRC\_CONNECTED, the network triggered state transition from RRC\_INACTIVE to RRC\_CONNECTED commences as described in clause 9.2.2.4.2 in TS 38.300 [3]. +- 9/10. The MN triggers the MN initiated SN Modification procedure to resume the SCG lower layers. If the SCG configuration needs to be updated, the SN provides the configuration data within an SN RRC reconfiguration message. +- 11/12. The UE is instructed to resume both the MCG and the SCG. If the SCG configuration is to be updated, the new configuration is provided in the RRC(Connection)Resume message. +13. The MN informs the SN that the UE has completed the reconfiguration procedure successfully, via the *SN Reconfiguration Complete* message, including the SN RRC response message, if received from the UE. +14. The UE performs synchronisation towards the PSCell of the SN. + +## 10.13 Notification Control Indication + +### 10.13.1 EN-DC + +Notification Control Indication procedure is not supported in EN-DC. + +### 10.13.2 MR-DC with 5GC + +The Notification Control Indication procedure may be initiated either by the MN or by the SN and is used to indicate that GFBR for one or several QoS flows cannot be fulfilled any more or can be fulfilled again by the reporting node. + +![Sequence diagram for Notification Control Indication procedure. Lifelines: UE, MN, SN, UPF, AMF. Step 1: MN to SN (Notification Control Indication (MN initiated)). Step 2: SN to MN (Notification Control Indication (SN initiated)). Step 3: MN to AMF (PDU Session Resource Notify).](986e77e2df3c318680a569774888f4aa_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + Note right of MN: 1. Notification Control Indication (MN initiated) + MN->>SN: 1. Notification Control Indication (MN initiated) + Note right of SN: 2. Notification Control Indication (SN initiated) + SN->>MN: 2. Notification Control Indication (SN initiated) + Note right of MN: 3. PDU Session Resource Notify + MN->>AMF: 3. PDU Session Resource Notify + +``` + +Sequence diagram for Notification Control Indication procedure. Lifelines: UE, MN, SN, UPF, AMF. Step 1: MN to SN (Notification Control Indication (MN initiated)). Step 2: SN to MN (Notification Control Indication (SN initiated)). Step 3: MN to AMF (PDU Session Resource Notify). + +Figure 10.13.2-1: Notification Control Indication procedure + +Figure 10.13.2-1 shows an example signalling flow for the Notification Control Indication procedure. + +1. The MN may, for an SN terminated bearer, indicate, that the GFBR requested from the MN cannot be fulfilled anymore. +In case the SN terminated bearer is configured as a split bearer, the SN may decide to increase the share provided by the SN or it may decide to notify the MN that resources requested for the SN terminated bearer cannot fulfill the GFBR any more. +2. Continuing the example message flow from step 1, the SN informs the MN that the GFBR for an SN terminated bearer cannot be fulfilled any more. +3. The MN decides to inform the 5GC that NG-RAN cannot fulfill the GFBR for a GBR QoS flow any more. + +## 10.14 PDU Session Split at UPF + +### 10.14.1 PDU Session Split at UPF during PDU session resource setup + +When a new PDU session needs to be established, the 5GC may provide two UL TEID addresses during PDU Session Resource Setup in order to allow for PDU session split. The MN may perform the SN Addition or the MN-initiated SN Modification procedure. If the MN decides to split the PDU session, the MN provides two DL TEID addresses and also the QoS flows associated with each tunnel. + +![Sequence diagram for PDU Session Split at UPF during PDU session resource setup. Lifelines: UE, MN, SN, UPF, AMF. Step 1: AMF to MN (PDU Session Resource Setup Request (UL TNL, additional UL TNL)). Step 2: MN internal decision (MN decides to setup two tunnels. Secondary Node Addition procedure or Secondary Node Modification (MN-initiated) procedure). Step 3: MN to AMF (PDU Session Resource Setup Response (DL TNL, QoS flows associated; additional DL TNL, QoS flows associated)).](047dcd17568e167181141afe7c0ee396_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant UPF + participant AMF + Note right of AMF: 1. PDU Session Resource Setup Request (UL TNL, additional UL TNL) + AMF->>MN: 1. PDU Session Resource Setup Request (UL TNL, additional UL TNL) + Note right of MN: 2. MN decides to setup two tunnels. Secondary Node Addition procedure or Secondary Node Modification (MN-initiated) procedure. + MN->>AMF: 3. PDU Session Resource Setup Response (DL TNL, QoS flows associated; additional DL TNL, QoS flows associated) + +``` + +Sequence diagram for PDU Session Split at UPF during PDU session resource setup. Lifelines: UE, MN, SN, UPF, AMF. Step 1: AMF to MN (PDU Session Resource Setup Request (UL TNL, additional UL TNL)). Step 2: MN internal decision (MN decides to setup two tunnels. Secondary Node Addition procedure or Secondary Node Modification (MN-initiated) procedure). Step 3: MN to AMF (PDU Session Resource Setup Response (DL TNL, QoS flows associated; additional DL TNL, QoS flows associated)). + +Figure 10.14.1-1: PDU Session Split at UPF during PDU session resource setup + +1. The 5GC provides two UL TEID addresses during PDU Session Resource Setup, to be applied as the first UL tunnel on the NG-U interface and the additional NG-U tunnel in case the MN decides to split the PDU session. +2. The MN decides to setup two tunnels. The MN uses the SN Addition procedure (as described in 10.2.2) or the MN-initiated SN Modification procedure (as described in 10.3.2) up to step 6. +3. The MN provides a DL TEID address to be applied as the first and an additional DL tunnel address on the NG-U interface. The MN also provides which QoS flows are associated with which tunnel. + +### 10.14.2 PDU Session Split at UPF during PDU session resource modify (5GC initiated) + +The 5GC may provide an additional UL TEID address during PDU Session Resource Modify in order to allow the MN to split the PDU session. The MN may perform the SN Addition or the MN-initiated SN Modification procedure. If the MN decides to split the PDU session, the MN provides a DL TEID address to be applied as the additional DL tunnel address and the QoS flows associated with that tunnel. + +![Sequence diagram for PDU Session Split at UPF during PDU session resource modify (5GC initiated).](26d0c0482ad7f4f026a58ecc0b468980_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UPF + participant SN + participant MN + participant UE + + Note right of MN: 1. PDU Session Resource Modify Request (additional UL TNL) + AMF->>MN: 1. PDU Session Resource Modify Request (additional UL TNL) + Note left of UPF: 2. MN decides to setup two tunnels. Secondary Node Addition procedure or Secondary Node modification (MN initiated) procedure + MN->>UPF: 2. MN decides to setup two tunnels. Secondary Node Addition procedure or Secondary Node modification (MN initiated) procedure + Note right of MN: 3. PDU Session Resource Modify Response(DL TNL, QoS flows associated; additional DL TNL, QoS flows associated) + MN->>AMF: 3. PDU Session Resource Modify Response(DL TNL, QoS flows associated; additional DL TNL, QoS flows associated) + +``` + +Sequence diagram for PDU Session Split at UPF during PDU session resource modify (5GC initiated). + +**Figure 10.14.2-1: PDU Session Split at UPF during PDU session resource modify** + +1. The 5GC provides an additional UL TEID address during PDU Session Resource Modify, to be applied as the additional NG-U tunnel in case the MN decides to split the PDU session. +2. The MN decides to setup two tunnels. If the new tunnel is to be setup at the SN, the MN uses the SN Addition procedure (as described in 10.2.2) or the MN-initiated SN Modification procedure (as described in 10.3.2) up to step 6, or up to step 8 if a QoS flow is moved to the SN and data forwarding applies. +3. The MN provides a DL TEID address to be applied as the additional DL tunnel address on the NG-U interface and the QoS flows associated with that tunnel. + +### 10.14.3 PDU Session Split at UPF (RAN initiated QoS flows offloading from MN to SN) + +When some QoS flows are offloaded from the MN to the SN, the MN may decide to split the PDU session served by the MN into more than one NG-U tunnels. The MN sends the *SN Addition/Modification Request* message including UPF UL TEID address used at the MN. Later on, if the MN receives a new UL TEID in the *PDU Session Resource Modify Confirm* message, the MN may provide the new UL TEID to the SN. + +![Sequence diagram illustrating the PDU Session Split at UPF during RAN initiated PDU session resource modify (QoS flows offloading from MN to SN).](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant 5GC + + Note right of SN: If in-order delivery is required for a QoS flow, the SN buffers those QoS flow packets received from the UE until it receives an indication that the MN has delivered all the UL packets to UPF for that QoS flow + + MN->>SN: 1. SN Addition/Modification Request (UPF UL TNL address @MN) + SN-->>MN: 2. SN Addition/Modification Request Acknowledge (additional DL TNL address @SN) + MN->>UE: 3. RRC reconfiguration + UE-->>MN: 4. RRC reconfiguration complete + MN->>SN: 5. SN Reconfiguration Complete + UE->>SN: 6. Random Access Procedure + Note left of SN: 6a. UL data transmission + Note left of SN: 6b. UL SDAP End Marker + UE-->>MN: 6c. GTP-U End Marker Packet + Note right of SN: 6c. UL packet delivery + MN->>5GC: 7. PDU Session Resource Modify Indication (DL TNL, QoS flows associated; additional DL TNL, QoS flows associated) + Note left of 5GC: 7a. GTP-U End Marker Packet + Note left of 5GC: 7b. GTP-U End Marker Packet + 5GC-->>MN: 8. PDU Session Resource Modify Confirm (UL TNL, additional UL TNL) + MN->>SN: 9. SN Modification Request (UL TNL) + SN-->>MN: 10. SN Modification Request Acknowledge + +``` + +Sequence diagram illustrating the PDU Session Split at UPF during RAN initiated PDU session resource modify (QoS flows offloading from MN to SN). + +**Figure 10.14.3-1: PDU Session Split at UPF during RAN initiated PDU session resource modify (QoS flows offloading from MN to SN)** + +1-2. If the MN decides to split a PDU session, it uses the SN Addition procedure or the MN-initiated SN Modification procedure, including current UPF UL NG-U tunnel used at the MN. If in-order delivery is required for some QoS flows, an UL forwarding tunnel may be setup for the PDU session at this stage. + +NOTE 1: In case the MN offloads some QoS flows to the SN within a PDU session already split between the MN and the SN, the MN initiated SN Modification procedure is used. + +3-6d. If in-order delivery is required, the SN buffers the first packets received from the UE for a certain QoS flow until it receives an GTP-U end marker packet over the UL forwarding tunnel indicating that the MN has delivered all UL packets from the source side to UPF for that QoS flow. Then the SN starts delivering UL packets to UPF for that QoS flow using the UPF UL TEID address used at the MN received at step 1. + +7-8. The MN uses the *PDU Session Resource Modify Indication* message to inform 5GC that the PDU session is split into two tunnels and indicate which QoS flows are associated with which DL tunnel. The 5GC triggers the sending of DL End Marker packets without QFI tag at step 7a and confirms with the *PDU Session Resource Modify Confirm* message and allocates corresponding uplink tunnels. + +After receiving the End Marker packet(s) from UPF at step 7a, the MN determines that the End Marker packets only work on the offloaded QoS flows, and may stop delivering and discard DL packets of the offloaded QoS flows, and the MN shall continue transmitting DL packets for the not offloaded QoS flows, if any. + +7a./7b. After receiving the DL end marker from 5GC at step 7a, the MN may generate at step 7b DL End Marker packets without QFI tag towards the SN. + +9-10. If the MN receives a new UL TEID in the *PDU Session Resource Modify Confirm* message for itself, the MN will use it to deliver UL packets to UPF. If the MN receives a new UL TEID for the SN, then the MN-initiated + +SN Modification procedure (i.e., step 9 and step 10) is used to provide the new UL TEID to the SN and then the SN switches to use the new UL TEID to deliver UL packets. + +### 10.14.4 PDU Session Split at UPF (RAN initiates QoS flows offloading from SN to MN) + +When some QoS flows are offloaded from the SN to the MN, the MN may decide to split the PDU session served by the SN into more than one NG-U tunnels. If the MN requests to offload, the MN sends the *SN Modification Request* message to the SN. In case the SN requests to offload, the SN sends the *SN Modification Required* message to the MN. + +![Sequence diagram illustrating the PDU Session Split at UPF during RAN initiated PDU session resource modify (QoS flows offloading from SN to MN).](691626a7032a642bb74793336c37e274_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN + participant 5GC + + Note right of MN: 1a. SN Modification Request + MN->>SN: 1a. SN Modification Request + Note right of SN: 1b. SN Request Acknowledge + SN->>MN: 1b. SN Request Acknowledge + Note right of MN: 1c. Xn-U Address Indication + MN->>SN: 1c. Xn-U Address Indication + + Note right of SN: 2a. SN Modification Required + SN->>MN: 2a. SN Modification Required + Note right of MN: 2b. SN Modification Confirm + MN->>SN: 2b. SN Modification Confirm + + Note right of MN: 3. RRC reconfiguration + MN->>UE: 3. RRC reconfiguration + Note right of UE: 4. RRC reconfiguration complete + UE->>MN: 4. RRC reconfiguration complete + Note right of MN: 5. SN Reconfiguration Complete + MN->>SN: 5. SN Reconfiguration Complete + + Note right of UE: 6. Random Access Procedure + UE->>SN: 6. Random Access Procedure + + Note right of UE: 6a. UL data transmission + UE->>MN: 6a. UL data transmission + Note right of UE: 6b. UL SDAP End Marker + UE->>SN: 6b. UL SDAP End Marker + Note right of SN: 6c. GTP-U End Marker Packet + SN->>MN: 6c. GTP-U End Marker Packet + + Note right of MN: If in-order delivery is required for a QoS flow, the MN buffers those QoS flow packets received from the UE until it receives an indication that the SN has delivered all the UL packets to UPF for that QoS flow + Note right of MN: 6d. UL packet delivery + MN->>5GC: 6d. UL packet delivery + + Note right of MN: 7. PDU Session Resource Modify Indication (DL TNL, QoS flows associated; additional DL TNL, QoS flows associated) + MN->>5GC: 7. PDU Session Resource Modify Indication (DL TNL, QoS flows associated; additional DL TNL, QoS flows associated) + Note right of SN: 7a. GTP-U End Marker Packet + SN->>5GC: 7a. GTP-U End Marker Packet + Note right of MN: 7b. GTP-U End Marker Packet + MN->>5GC: 7b. GTP-U End Marker Packet + + Note right of MN: 8. PDU Session Resource Modify Confirm (UL TNL, additional UL TNL) + 5GC->>MN: 8. PDU Session Resource Modify Confirm (UL TNL, additional UL TNL) + + Note right of MN: 9. SN Modification Request (UL TNL) + MN->>SN: 9. SN Modification Request (UL TNL) + Note right of SN: 10. SN Modification Request Acknowledge + SN->>MN: 10. SN Modification Request Acknowledge + +``` + +Sequence diagram illustrating the PDU Session Split at UPF during RAN initiated PDU session resource modify (QoS flows offloading from SN to MN). + +**Figure 10.14.4-1: PDU Session Split at UPF during RAN initiated PDU session resource modify (QoS flows offloading from SN to MN)** + +1a-1c. When the MN requests to offload some QoS flows from the SN to the MN for a PDU session, it sends the *SN Modification Request* message. If in-order delivery is required for some of the QoS flows, an UL forwarding tunnel may be setup for the PDU session at this stage and the MN provides the UL forwarding tunnel address information in the *Xn-U Address Indication* message. + +2a-2b. When the SN requests to offload some QoS flows to the MN for a PDU session, the SN sends the *SN Modification Required* message. If in-order delivery is required for some of the QoS flows, an UL forwarding tunnel may be setup for the PDU session at this stage and the MN provides the UL forwarding tunnel address information in the *SN Modification Confirm* message. + +3-6d. If in-order delivery is required, the MN buffers the first packets received from the UE for a certain QoS flow until it receives an GTP-U end marker packet over the UL forwarding tunnel indicating that the SN has delivered all UL packets from the source side to UPF for that QoS flow. + +7-8. The MN uses the *PDU Session Resource Modify Indication* message to inform 5GC that the PDU session is split into two tunnels and indicate which QoS flows are associated with which DL tunnel. The 5GC triggers the sending of DL End Marker packets without QFI tag at step 7a and confirms with the *PDU Session Resource Modify Confirm* message and allocates corresponding uplink tunnels. + +After receiving the End Marker packet(s) from UPF at step 7a, the SN determines that the End Marker packets only work on the offloaded QoS flows, and may stop delivering and discard DL packets of the offloaded QoS flows, and the SN shall continue transmitting DL packets for the not offloaded QoS flows, if any. + +7a./7b. After receiving the DL end marker from 5GC at step 7a, the SN may generate at step 7b DL End Marker packets without QFI tag towards the MN. + +9-10. If the MN receives a new UL TEID in the *PDU Session Resource Modify Confirm* message for itself, the MN will use it to deliver UL packets to UPF. If the MN receives a new UL TEID for the SN, then the MN-initiated SN Modification procedure (i.e., the step 9 and step 10) is used to provide the new UL TEID to the SN and then the SN switches to use the new UL TEID to deliver UL packets. + +## 10.15 F1-C Traffic Transfer + +In EN-DC/NR-DC, the F1-C Traffic Transfer message is sent by the MN to the SN or by the SN to MN to transfer the F1-C traffic to and from an IAB-node. + +![Sequence diagram illustrating the F1-C transfer procedure in EN-DC. The diagram shows five entities: IAB-MT, MN, SN, S-GW, and MME. The sequence of messages is: 1. ULInformationTransfer from IAB-MT to MN; 2. F1-C Traffic Transfer from MN to SN; 3. F1-C Traffic Transfer from SN to MN; 4. DLInformationTransfer from MN to IAB-MT.](c59200e0fd141cba63a0b0739c59c3d7_img.jpg) + +``` + +sequenceDiagram + participant IAB-MT + participant MN + participant SN + participant S-GW + participant MME + Note left of IAB-MT: 1. ULInformationTransfer + IAB-MT->>MN: 1. ULInformationTransfer + Note right of MN: 2. F1-C Traffic Transfer + MN->>SN: 2. F1-C Traffic Transfer + Note right of SN: 3. F1-C Traffic Transfer + SN->>MN: 3. F1-C Traffic Transfer + Note left of MN: 4. DLInformationTransfer + MN->>IAB-MT: 4. DLInformationTransfer + +``` + +Sequence diagram illustrating the F1-C transfer procedure in EN-DC. The diagram shows five entities: IAB-MT, MN, SN, S-GW, and MME. The sequence of messages is: 1. ULInformationTransfer from IAB-MT to MN; 2. F1-C Traffic Transfer from MN to SN; 3. F1-C Traffic Transfer from SN to MN; 4. DLInformationTransfer from MN to IAB-MT. + +Figure 10.15-1: F1-C transfer procedure in EN-DC + +1. When the IAB-MT sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet, it sends it to the MN in a container within *ULInformationTransfer* message as specified in TS 36.331 [10]. +2. The MN initiates the F1-C Traffic Transfer procedure, in which it transfers the received F1-AP message encapsulated in (SCTP/IP or F1-C related (SCTP/IP) packet as an octet string. +3. When the SN sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet, it sends it to the MN as an octet string through the F1-C Traffic Transfer procedure. +4. The MN sends the received F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet to the IAB-MT in a container within *DLInformationTransfer* message as specified in TS 36.331 [10]. + +![Sequence diagram showing F1-C transfer between IAB-MT and SN in NR-DC. The diagram involves five nodes: IAB-MT, MN, SN, UPF, and AMF. The sequence of messages is: 1. ULInformationTransfer from IAB-MT to MN; 2. F1-C Traffic Transfer from MN to SN; 3. F1-C Traffic Transfer from SN to MN; 4. DLInformationTransfer from MN to IAB-MT.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +``` + +sequenceDiagram + participant IAB-MT + participant MN + participant SN + participant UPF + participant AMF + Note left of IAB-MT: 1. ULInformationTransfer + IAB-MT->>MN: 1. ULInformationTransfer + Note right of MN: 2. F1-C Traffic Transfer + MN->>SN: 2. F1-C Traffic Transfer + Note right of SN: 3. F1-C Traffic Transfer + SN->>MN: 3. F1-C Traffic Transfer + Note left of MN: 4. DLInformationTransfer + MN->>IAB-MT: 4. DLInformationTransfer + +``` + +Sequence diagram showing F1-C transfer between IAB-MT and SN in NR-DC. The diagram involves five nodes: IAB-MT, MN, SN, UPF, and AMF. The sequence of messages is: 1. ULInformationTransfer from IAB-MT to MN; 2. F1-C Traffic Transfer from MN to SN; 3. F1-C Traffic Transfer from SN to MN; 4. DLInformationTransfer from MN to IAB-MT. + +**Figure 10.15-2: Scenario 1: F1-C transfer between IAB-MT and SN (F1-terminating node) in NR-DC** + +1. The IAB-MT sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet to the MN (non-F1-terminating node) via SRB2 in a container within *ULInformationTransfer* message as specified in TS 38.331 [4]. +2. The MN initiates the F1-C Traffic Transfer procedure, in which it transfers the received F1-AP message encapsulated in (SCTP/IP) or F1-C related (SCTP/IP) packet as an octet string. +3. The SN (F1-terminating node) sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet to the MN as an octet string through the F1-C Traffic Transfer procedure. +4. The MN sends the received F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/IP) packet to the IAB-MT via SRB2 in a container within *DLInformationTransfer* message as specified in TS 38.331 [4]. + +## 10.16 Support of inter-system handover involving EN-DC or MR-DC with 5GC + +### 10.16.1 General + +Inter-system handover is specified in TS 23.501 [11] and TS 23.502 [20]. Data forwarding for inter-system handover is specified in TS 38.300 [3] and clause 8.4. + +Inter-system Inter-Master node handover with/without SN change is not supported in this version of the protocol (e.g. no transition from EN-DC to NGEN-DC or NR-DC). + +Inter-system HO from NR to E-UTRA with EN-DC configuration is supported in this version of the specification. N26 based inter-system HO will be executed between source RAN and gNB. + +Inter-system HO from E-UTRA connected to 5GC to E-UTRA with EN-DC configuration is not supported. Inter-system HO from E-UTRA with EPC to MR-DC with 5GC is not supported. + +Inter-system handover with source gNB and the target en-gNB or the source en-gNB and the target gNB being realised within the same network entity is supported in this version of the specification as described in clause 10.16.2 and clause 10.16.3. + +### 10.16.2 Inter-system handover from EPS to 5GS with the Secondary Node used as target + +Inter-system handover from EPS to 5GS with the Secondary Node used as target refers to a deployment scenario where the source en-gNB and the target gNB are realised within the same network entity. + +![Sequence diagram for inter-system handover from EPS to 5GS with the Secondary Node used as target. The diagram shows the interaction between UE, eNB, gNB, en-gNB, MME, AMF/SMF, SGW, and UPF. The process involves S1AP and NGAP signaling, data forwarding from SGW to gNB, and RRC reconfiguration of the UE.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +The sequence diagram illustrates the inter-system handover from EPS to 5GS with the Secondary Node (SN) used as target. The entities involved are UE, eNB, gNB, en-gNB, MME, AMF/SMF, SGW, and UPF. The gNB and en-gNB are grouped together in a dashed box labeled 'Data'. + +The sequence of messages is as follows: + +- The eNB sends an **1. S1AP Handover Required (SgNB UE X2AP ID)** to the MME. +- The MME sends an **2. NGAP Handover Request (SgNB UE X2AP ID)** to the gNB. +- The gNB sends an **2. NGAP Handover Request Acknowledge** to the MME. +- The MME sends an **S1AP Handover Command** to the eNB. +- The eNB sends a **MobilityFromEUTRACommand (carry RRCReconfiguration)** to the UE. +- The UE sends a **3. RRCReconfigurationComplete** to the eNB. +- The eNB sends a **3. NGAP Handover Notify** to the AMF/SMF. +- The AMF/SMF sends an **EPC/5GC Session Modification** to the SGW. +- The SGW sends a **4. End Marker Packet** to the gNB. + +Data flow is indicated by dashed green arrows: + +- Data Over E-RAB**: From the UE to the eNB. +- Data**: From the SGW to the gNB (labeled '3. internal forwarding and buffering'). +- 3. Data Over DRB**: From the gNB to the UE. +- 4. Data Over DRB**: From the gNB to the UE. + +Sequence diagram for inter-system handover from EPS to 5GS with the Secondary Node used as target. The diagram shows the interaction between UE, eNB, gNB, en-gNB, MME, AMF/SMF, SGW, and UPF. The process involves S1AP and NGAP signaling, data forwarding from SGW to gNB, and RRC reconfiguration of the UE. + +**Figure 10.16.2-1: Inter-system handover from EPS to 5GS with the Secondary Node used as target** + +- Step 1: The (source) eNB, performing EN-DC with the (source) en-gNB triggers handover preparation including the SgNB UE X2AP ID within the Source NG-RAN to Target NG-RAN Transparent Container. +- Step 2: The target gNB infers from the received SgNB UE X2AP ID in the *Handover Request* message that direct data forwarding can be performed in a node-internal way. +- Step 3: DL UP data is forwarded in a node-internal way for the SN terminated bearers. +- Step 4: After the end marker has arrived from the SGW, the (target) gNB processes UP data from the UPF. + +### 10.16.3 Inter-system handover from 5GS to EPS with the Source Node used as target Secondary Node + +Inter-system handover from 5GS to EPS with the Source Node used as target Secondary Node refers to a deployment scenario where the source gNB and the target en-gNB are realised within the same network entity. + +![Sequence diagram for inter-system handover from 5GS to EPS with the source node used as target secondary node. The diagram shows the interaction between UE, gNB, en-gNB, eNB, AMF/SMF, MME, SGW, and UPF. The process involves NGAP Handover Required, S1AP Handover Request, SgNB Addition Request, SgNB Addition Request Acknowledge, S1AP Handover Request Acknowledge, Modify Bearer, NGAP Handover Command, MobilityFromNRCommand, internal Forwarding and buffering, RRCConnectionReconfigurationComplete, Handover Notify, and Data Restart Over DRB.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant en-gNB + participant eNB + participant AMF/SMF + participant MME + participant SGW + participant UPF + + Note right of AMF/SMF: Data + UE->>gNB: Data Over DRB + gNB->>AMF/SMF: 1. NGAP Handover Required (Source NG-RAN node ID, RAN UE NGAP ID) + AMF/SMF->>MME: 2. S1AP Handover Request (Source NG-RAN node ID, RAN UE NGAP ID) + MME->>eNB: 3. SgNB Addition Request (RAN UE NGAP ID) + eNB->>MME: 4. SgNB Addition Request Acknowledge + MME->>AMF/SMF: 5. S1AP Handover Request Acknowledge + AMF/SMF->>SGW: 6. Modify Bearer + AMF/SMF->>gNB: 7. NGAP Handover Command + gNB->>UE: 8. MobilityFromNRCommand (carry RRCConnectionReconfiguration) + Note right of gNB: 9. internal Forwarding and buffering + Note right of AMF/SMF: Data + UE->>gNB: 10. RRCConnectionReconfigurationComplete + gNB->>MME: 11. Handover Notify + Note right of MME: EPC/5GC Session Modification (details not shown) + UE->>gNB: 12. Data Restart Over DRB + Note right of AMF/SMF: Data + UE->>gNB: 12. Data Over DRB + +``` + +Sequence diagram for inter-system handover from 5GS to EPS with the source node used as target secondary node. The diagram shows the interaction between UE, gNB, en-gNB, eNB, AMF/SMF, MME, SGW, and UPF. The process involves NGAP Handover Required, S1AP Handover Request, SgNB Addition Request, SgNB Addition Request Acknowledge, S1AP Handover Request Acknowledge, Modify Bearer, NGAP Handover Command, MobilityFromNRCommand, internal Forwarding and buffering, RRCConnectionReconfigurationComplete, Handover Notify, and Data Restart Over DRB. + +**Figure 10.16.3-1: Inter-system handover from 5GS to EPS with the Source Node used as target Secondary Node** + +1. The (source) gNB triggers handover preparation phase including in the Source eNB to Target eNB Transparent Container the Source NG-RAN node ID and the RAN UE NGAP ID. +2. The target eNB receives the Source NG-RAN node ID and the RAN UE NGAP ID in the Source eNB to Target eNB Transparent Container. +- 3.-4. The X2AP SgNB Addition procedure is performed towards the (target) en-gNB indicated in the Source NG-RAN node ID received in step 2. The eNB includes the RAN UE NGAP ID received in step 2 in the X2 SgNB Addition Request message. +- 5.-8. Handover proceeds. +9. DL UP data is forwarded in a node-internal way for the SN terminated bearers. + +## 10.17 Inter-Master Node RRC Resume without Secondary Node change + +### 10.17.1 MR-DC with 5GC + +Inter-MN RRC Resume without MN initiated SN change is used to transfer UE context data from a source MN to a target MN while the UE context at the SN is kept. During the procedure, the target MN may decide not to keep the SN. + +![Sequence diagram for Inter-MN RRC Resume without MN initiated SN change procedure. The diagram shows the interaction between UE, source MN, SN, target MN, UPF, and AMF. The process starts with the UE sending an RRCResumeRequest to the target MN. The target MN then requests the UE context from the source MN. The source MN responds with the context, which includes the SN UE XnAP ID, SN ID, and the UE context in the SN. The target MN then sends an SN Addition Request to the SN, which includes the SN UE XnAP ID as a reference to the UE context in the SN. The SN responds with an SN Addition Request Acknowledge. The target MN also sends an Xn-U Address Indication to the SN. The target MN then resumes the RRC connection with the UE. The UE completes the RRC connection and performs a Random Access Procedure towards the SN. The target MN then sends an SN Reconfiguration Complete message to the SN. The source MN then sends a Retrieve UE Context Confirm to the target MN. The target MN then sends an Xn-U Address Indication to the source MN. The source MN then sends an SN Release Request to the SN. The SN responds with an SN Release Request Acknowledge. The source MN also sends an Xn-U Address Indication to the SN. The source MN then starts data forwarding to the target MN. The target MN then sends a Path Switch Request to the AMF. The AMF responds with a Bearer Modification. The target MN then sends a New Path (MN terminated bearer) to the UPF. The UPF responds with a New Path (SN terminated bearer) to the target MN. The target MN then sends a Path Switch Request Acknowledge to the AMF. The target MN then sends a UE Context Release to the source MN. The source MN then sends a UE Context Release to the SN.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +``` + +sequenceDiagram + participant UE + participant source MN + participant SN + participant target MN + participant UPF + participant AMF + + Note left of UE: 1. RRCResumeRequest + UE->>target MN: 1. RRCResumeRequest + Note right of target MN: 2. Retrieve UE Context Request + target MN->>source MN: 2. Retrieve UE Context Request + Note right of source MN: 3. Retrieve UE Context Response + source MN->>target MN: 3. Retrieve UE Context Response + Note right of target MN: 4a. SN Addition Request + target MN->>SN: 4a. SN Addition Request + Note right of SN: 4b. SN Addition Request Acknowledge + SN->>target MN: 4b. SN Addition Request Acknowledge + Note right of target MN: 4c. Xn-U Address Indication + target MN->>SN: 4c. Xn-U Address Indication + Note left of UE: 5. RRCResume + target MN->>UE: 5. RRCResume + Note left of UE: 6. RRCResumeComplete + UE->>target MN: 6. RRCResumeComplete + Note left of UE: 7. Random Access Procedure + UE->>SN: 7. Random Access Procedure + Note right of SN: 8. SN Reconfiguration Complete + SN->>target MN: 8. SN Reconfiguration Complete + Note right of target MN: 9. Retrieve UE Context Confirm + target MN->>source MN: 9. Retrieve UE Context Confirm + Note right of source MN: 10. Xn-U Address Indication + source MN->>target MN: 10. Xn-U Address Indication + Note right of source MN: 11a. SN Release Request + source MN->>SN: 11a. SN Release Request + Note right of SN: 11b. SN Release Request Acknowledge + SN->>source MN: 11b. SN Release Request Acknowledge + Note right of source MN: 11c. Xn-U Address Indication + source MN->>SN: 11c. Xn-U Address Indication + Note right of source MN: 12. Data Forwarding + source MN-->>target MN: 12. Data Forwarding + Note right of target MN: 13. Path Switch Request + target MN->>AMF: 13. Path Switch Request + Note right of AMF: 14. Bearer Modification + AMF->>target MN: 14. Bearer Modification + Note right of target MN: 15a. New Path (MN terminated bearer) + target MN-->>UPF: 15a. New Path (MN terminated bearer) + Note right of UPF: 15b. New Path (SN terminated bearer) + UPF-->>target MN: 15b. New Path (SN terminated bearer) + Note right of target MN: 16. Path Switch Request Acknowledge + target MN->>AMF: 16. Path Switch Request Acknowledge + Note right of target MN: 17. UE Context Release + target MN->>source MN: 17. UE Context Release + Note right of source MN: 18. UE Context Release + source MN->>SN: 18. UE Context Release + +``` + +Sequence diagram for Inter-MN RRC Resume without MN initiated SN change procedure. The diagram shows the interaction between UE, source MN, SN, target MN, UPF, and AMF. The process starts with the UE sending an RRCResumeRequest to the target MN. The target MN then requests the UE context from the source MN. The source MN responds with the context, which includes the SN UE XnAP ID, SN ID, and the UE context in the SN. The target MN then sends an SN Addition Request to the SN, which includes the SN UE XnAP ID as a reference to the UE context in the SN. The SN responds with an SN Addition Request Acknowledge. The target MN also sends an Xn-U Address Indication to the SN. The target MN then resumes the RRC connection with the UE. The UE completes the RRC connection and performs a Random Access Procedure towards the SN. The target MN then sends an SN Reconfiguration Complete message to the SN. The source MN then sends a Retrieve UE Context Confirm to the target MN. The target MN then sends an Xn-U Address Indication to the source MN. The source MN then sends an SN Release Request to the SN. The SN responds with an SN Release Request Acknowledge. The source MN also sends an Xn-U Address Indication to the SN. The source MN then starts data forwarding to the target MN. The target MN then sends a Path Switch Request to the AMF. The AMF responds with a Bearer Modification. The target MN then sends a New Path (MN terminated bearer) to the UPF. The UPF responds with a New Path (SN terminated bearer) to the target MN. The target MN then sends a Path Switch Request Acknowledge to the AMF. The target MN then sends a UE Context Release to the source MN. The source MN then sends a UE Context Release to the SN. + +**Figure 10.17.1-1: Inter-MN RRC Resume without MN initiated SN change procedure** + +Figure 10.17.1-1 shows an example signalling flow for inter-MN RRC Resume without MN initiated SN change: + +1. The UE resumes from RRC\_INACTIVE, providing the I-RNTI, allocated by the source MN, i.e., the last serving NG-RAN node. +2. The target MN, if able to resolve the NG-RAN node identity contained in the I-RNTI, requests the source MN to provide UE Context by initiating the Xn Retrieve UE Context procedure. +3. If the verification is successful, the source MN provides UE context data. The source MN includes the SN UE XnAP ID, SN ID and the UE context in the SN in the *Retrieve UE Context Response* message. + +NOTE 1: The source MN may trigger the MN-initiated SN Modification procedure (to the SN) to retrieve the current SCG configuration and to allow provision of data forwarding related information before step 3.4a. If the target MN decides to keep the SN, the target MN sends *SN Addition Request* to the SN including the SN UE XnAP ID as a reference to the UE context in the SN that was established by the source MN. + +4b. The SN replies with *SN Addition Request Acknowledge* message. + +4c. For SN terminated bearers using MCG resources, the target MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message. + +5/6. The target MN and UE complete the resumption of the RRC connection. + +7. If configured with bearers requiring SCG radio resources, the UE synchronizes to the SN. + +NOTE 2: The order the UE sends the *RRCResumeComplete* message towards the target MN (step 6) and performs the Random Access procedure towards the SN (step 7) is not defined. + +8. If the RRC connection reconfiguration procedure was successful, the target MN informs the SN via *SN Reconfiguration Complete* message. + +9. If the RRC connection reconfiguration procedure was successful, the target MN initiates the Xn Retrieve UE Context Confirm procedure and indicates to the source MN whether the UE context in the SN is kept or not. + 10. The Xn-U Address Indication procedure may be invoked by the target MN to provide forwarding address information if loss of DL user data buffered in the source side needs to be avoided. + - 11a/11b. The source MN sends *SN Release Request* message to the SN including a Cause indicating MCG mobility. The SN acknowledges the release request. The source MN indicates to the SN that the UE context in the SN is kept, if it receives the indication from the target MN. If the indication as the UE context kept in the SN is included, the SN keeps the UE context. + - 11c. If received in step 10, the source MN sends the *Xn-U Address Indication* message to the SN to transfer data forwarding information. More than one data forwarding addresses may be provided if the PDU session is split in the target side. + 12. If applicable, data forwarding takes place from the source side. If the SN is kept, data forwarding may be omitted for SN terminated bearers or QoS flows kept in the SN. + - 13-16. The target MN initiates the Path Switch procedure. If the target MN includes multiple DL TEIDs for one PDU session in the *Path Switch Request* message, multiple UL TEID of the UPF for the PDU session should be included in the *Path Switch Ack* message in case there is TEID update in UPF. +- NOTE 3: If new UL TEIDs of the UPF for SN terminated bearers are included, the target MN performs MN initiated SN Modification procedure to provide them to the SN. +17. The target MN initiates the UE Context Release procedure towards the source MN. + 18. Upon reception of the *UE Context Release* message from source MN, the SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE context kept indication was included in the *SN Release Request* message in step 11. + +## 10.18 Self-optimisation for PSCell change + +### 10.18.1 General + +For analysis of PSCell change failure, the UE makes the SCG Failure Information available to the MN. + +### 10.18.2 PSCell change failure + +One of the functions of self-optimization for PSCell change is to detect PSCell change failures that occur due to Too late PSCell change or Too early PSCell change, or Triggering PSCell change to wrong PSCell. These problems are defined as follows: + +- Too late PSCell change: an SCG failure occurs after the UE has stayed for a long period of time in the PSCell; a suitable different PSCell is found based on the measurements reported from the UE. +- Too early PSCell change: an SCG failure occurs shortly after a successful PSCell change from a source PSCell to a target PSCell or a PSCell change failure occurs during the PSCell change procedure; source PSCell is still the suitable PSCell based on the measurements reported from the UE. +- Triggering PSCell change to wrong PSCell: an SCG failure occurs shortly after a successful PSCell change from a source PSCell to a target PSCell or a PSCell change failure occurs during the PSCell change procedure; a suitable PSCell different with source PSCell or target PSCell is found based on the measurements reported from the UE. + +In the definition above, the "successful PSCell change" refers to the UE state, namely the successful completion of the RA procedure. + +MN performs initial analysis to identify the node that caused the failure. The MN may use the SCG Failure Information Report procedure to verify whether intra-SN PSCell change has been triggered in the last serving SN and stores the SCG Failure Information for the time needed to receive possible response from the last serving SN. If the failure is + +caused by a source SN, the MN forwards then the SCG Failure Information to the source SN. The node responsible for the last PSCell change (the source SN, the last serving SN or the MN) performs the final root cause analysis. + +### 10.18.3 Conditional PSCell addition or change failure + +One of the functions of self-optimization for CPAC is to detect CPAC failures that occur due to Too late CPC execution or Too early CPC/CPA execution, or CPC/CPA execution to wrong PSCell. These problems are defined as follows: + +- Too Late CPC Execution: UE receives CPC configuration, while a SCG failure occurs before CPC execution condition is satisfied; a suitable PSCell different from source PSCell is found based on the measurements reported from the UE. +- Too Early CPC/CPA Execution: CPC/CPA execution is not successful or an SCG failure occurs shortly after a successful CPC/CPA execution; in case of CPC, the source PSCell is still the suitable PSCell based on the measurements reported from the UE; in case of CPA, no suitable PSCell is found based on the measurements reported from the UE. +- CPC/CPA Execution to wrong PSCell: CPC/CPA execution is not successful or an SCG failure occurs shortly after a successful CPC/CPA execution; a suitable PSCell different from the source PSCell or the target PSCell is found based on the measurements reported from the UE. There are two sub-cases: + - if the suitable PSCell is one of the candidate target PSCells provided by the node initiating the CPC or by the MN initiating the CPA, but not one of the candidate PSCells selected by the candidate or target SN, it is wrong target PSCell selection at the candidate or target SN; + - else, it is wrong candidate PSCell list selection at the node initiating the CPC or at the MN initiating the CPA. + +In the definition above, the "successful CPC/CPA execution" refers to the UE state, namely the successful completion of the RA procedure. + +The MN performs the initial analysis when *SCGFailureInformation* is received from the UE. In the first step, MN verifies whether intra-SN PSCell change has been triggered in the last serving SN. In case the intra-SN PSCell change has been triggered in the last serving SN, the MN forwards the SCG Failure Information Report message to this last serving SN, which performs the final root cause analysis. In case of no intra-SN PSCell change, the MN determines the type of PSCell addition/change, e.g., whether it is CPA or CPC in case of conditional mobility, if CPC whether it is MN initiated or SN initiated. + +For CPA or MN initiated CPC, if the suitable PSCell is one of the candidate PSCells provided by the MN at CPAC preparation, but not one of the candidate PSCells selected by the candidate or target SN, MN sends the SCG Failure Information Report message to the candidate or target SN, which perform the final MRO related optimisation. Otherwise, the MN performs the final MRO related optimisation. + +For SN initiated CPC, the MN sends the SCG Failure Information Report message to source SN, and source SN performs root cause analysis. If the suitable PSCell is one of the candidate PSCells provided by the source SN, but not one of the candidate PSCells selected by the candidate or target SN, the source SN indicates to MN that the root cause of the SCG failure may have occurred in the other nodes. MN then sends the SCG Failure Information Report message to the candidate or target SN. Otherwise, the source SN performs the final MRO related optimisation. + +### 10.18.4 Successful PSCell Change Report + +The objective of Successful PSCell change Report (SPR) is to detect sub-optimal successful PSCell change/CPC or successful PSCell addition/CPA. + +For analysis of such sub-optimal successful PSCell change/CPC and successful PSCell addition/CPA, the UE may collect SPR based on the triggers configured by the network, if received, and makes the SPR available to the network as specified in TS 38.331 [4]. + +For PSCell addition/CPA and PSCell change/CPC (MN or SN initiated), the target SN always decides the T304 trigger for SPR and performs root cause analysis. + +For SN-initiated PSCell change/CPC, the source SN decides the T310/T312 triggers for SPR and is responsible for SPR related optimizations e.g., to optimize PSCell change/CPC configuration or associated mobility thresholds or adjust T310/T312 timer values. + +For MN-initiated PSCell change/CPC, the MN decides the T310/T312 triggers for SPR. MN may optimize PSCell change/CPC configuration or associated mobility thresholds or both. Source SN may optimize lower layer issues e.g., adjust T310/T312 timer values. + +The SPR can be fetched from the UE by the MN only while the UE is still connected to the MN, or by a node different from the MN that sent the SPR configuration to the UE if the UE is not connected to the MN anymore. In case the SPR is retrieved in a node different from the MN that sent the SPR configuration to the UE, the SPR is first forwarded to that MN, which then forwards it to the respective SN(s) which should perform the SPR optimization. + +### 10.18.5 RA Report retrieval + +In MR-DC, when a UE performs successful random access attempts which are only known by the SN (e.g., beam failure recovery, UL synchronization issue, scheduling request failure, no PUCCH resource available), the SN may inform the MN about the occurrences of successful random access procedures in the SN via a RACH indication. The MN may then retrieve the RA Report from the UE(s) based on the RACH indication received from the SN. + +A UE while being in EN-DC and NGEN-DC can collect E-UTRA RA Reports and NR RA Reports upon performing RACH in MN and SN respectively. When a E-UTRAN node retrieves the E-UTRA RA Report, it can also request UE to include the NR RA Report. If available, the UE then includes the NR RA Report in a container along with a list of PSCells associated to the NR RA Report within the E-UTRA RA Report. The retrieving E-UTRAN node may then forward it to the corresponding SNs serving the PSCells indicated within the E-UTRA RA Report. + +In case of NGEN-DC, in case there is no Xn connectivity between the ng-eNB retrieving the NR RA Report from the UE and the gNB serving the PSCells indicated by UE in the NR RA Report, the ng-eNB may forward the NR RA Report via Xn to an ng-eNB connected to a gNB serving the PSCells indicated in the RA Report. + +In case of EN-DC, in case there is no X2 connectivity between the eNB retrieving the NR RA Report from the UE and the en-gNB serving the PSCells indicated by UE in the NR RA Report, the eNB may forward the NR RA Report via X2 to an eNB connected to an en-gNB serving the PSCells indicated in the RA Report. + +## 10.19 Conditional Handover with Secondary Node + +### 10.19.1 EN-DC + +The Conditional Handover with Secondary Node procedure is used for configuration and execution of CHO with SN. This procedure includes the cases where the SN is kept, changed or added. If the SN is kept, the UE context at the SN is kept. If the SN is changed, the UE context at the source SN is moved to the target SN. + +![Sequence diagram for Conditional Handover with Secondary Node procedure. Lifelines: UE, source MN, (source) SN, (target) SN, target MN, Other potential target MN, Other potential target SN, S-GW, MME. The diagram shows 21 numbered steps of signaling between these entities, with dashed boxes for 'Early Data Forwarding' and 'Data Forwarding'.](a5404b7275b06497eecf9b5883604753_img.jpg) + +``` + +sequenceDiagram + participant UE + participant source MN + participant source SN as (source) SN + participant target SN as (target) SN + participant target MN + participant Other potential target MN + participant Other potential target SN + participant S-GW + participant MME + + Note left of source MN: 1. Handover Request + source MN->>target MN: 1. Handover Request + Note left of source MN: 1. Handover Request + source MN->>Other potential target MN: 1. Handover Request + Note left of target MN: 2. SgNB Addition Request + target MN->>target SN: 2. SgNB Addition Request + Note left of target SN: 3. SgNB Addition Request Ack + target SN->>target MN: 3. SgNB Addition Request Ack + Note left of target MN: 2. SgNB Addition Request + target MN->>Other potential target SN: 2. SgNB Addition Request + Note left of Other potential target SN: 3. SgNB Addition Request Ack + Other potential target SN->>target MN: 3. SgNB Addition Request Ack + Note left of target MN: 4. Handover Request Acknowledge + target MN->>source MN: 4. Handover Request Acknowledge + Note left of source MN: 4. Handover Request Acknowledge + source MN->>target MN: 4. Handover Request Acknowledge + Note left of source MN: 4a. Data Forwarding Address Indication + source MN->>target MN: 4a. Data Forwarding Address Indication + Note left of source MN: 5. RRCConnectionReconfiguration (containing MN RRCConnectionReconfiguration* and may contain SN RRCReconfiguration**) + source MN->>UE: 5. RRCConnectionReconfiguration (containing MN RRCConnectionReconfiguration* and may contain SN RRCReconfiguration**) + Note left of source MN: 6. RRCConnectionReconfigurationComplete + source MN->>UE: 6. RRCConnectionReconfigurationComplete + Note left of source MN: Early Data Forwarding + Note left of target MN: Early Data Forwarding + Note left of source MN: 7. Random Access Procedure + source MN->>UE: 7. Random Access Procedure + Note left of target MN: 8. RRCConnectionReconfigurationComplete* (may contain SN RRCReconfigurationComplete**) + target MN->>UE: 8. RRCConnectionReconfigurationComplete* (may contain SN RRCReconfigurationComplete**) + Note left of source MN: 9. Random Access Procedure + source MN->>UE: 9. Random Access Procedure + Note left of target SN: 10. SgNB Reconfiguration Complete + target SN->>target MN: 10. SgNB Reconfiguration Complete + Note left of target MN: 11. Handover Success + target MN->>source MN: 11. Handover Success + Note left of source MN: 12a. SgNB Release Request + source MN->>target MN: 12a. SgNB Release Request + Note left of target MN: 12b. SgNB Release Request Acknowledge + target MN->>source MN: 12b. SgNB Release Request Acknowledge + Note left of source MN: 12c. Handover Cancel + source MN->>target MN: 12c. Handover Cancel + Note left of target MN: 12d. SgNB Release Request + target MN->>Other potential target SN: 12d. SgNB Release Request + Note left of Other potential target SN: 12e. SgNB Release Request Acknowledge + Other potential target SN->>target MN: 12e. SgNB Release Request Acknowledge + Note left of source MN: 13a. Secondary RAT Data Usage Report + source MN->>target MN: 13a. Secondary RAT Data Usage Report + Note left of source MN: 13b. Secondary RAT Data Usage Report + source MN->>MME: 13b. Secondary RAT Data Usage Report + Note left of source MN: 14a. SN Status Transfer + source MN->>target MN: 14a. SN Status Transfer + Note left of source MN: 14b. SN Status Transfer + source MN->>target SN: 14b. SN Status Transfer + Note left of target SN: 14c. SN Status Transfer + target SN->>target MN: 14c. SN Status Transfer + Note left of source MN: 15. Data Forwarding + Note left of target MN: 15. Data Forwarding + Note left of target MN: 16. Path Switch Request + target MN->>S-GW: 16. Path Switch Request + Note left of S-GW: 17. Bearer Modification + S-GW->>MME: 17. Bearer Modification + Note left of target MN: 18a. New Path (MN terminated bearer) + target MN->>S-GW: 18a. New Path (MN terminated bearer) + Note left of target SN: 18b. New Path (SN terminated bearer) + target SN->>S-GW: 18b. New Path (SN terminated bearer) + Note left of target MN: 19. Path Switch Request Acknowledge + target MN->>S-GW: 19. Path Switch Request Acknowledge + Note left of source MN: 20. UE Context Release + source MN->>target MN: 20. UE Context Release + Note left of source MN: 21. UE Context Release + source MN->>source SN: 21. UE Context Release + +``` + +Sequence diagram for Conditional Handover with Secondary Node procedure. Lifelines: UE, source MN, (source) SN, (target) SN, target MN, Other potential target MN, Other potential target SN, S-GW, MME. The diagram shows 21 numbered steps of signaling between these entities, with dashed boxes for 'Early Data Forwarding' and 'Data Forwarding'. + +**Figure 10.19.1-1: Conditional Handover with Secondary Node procedure** + +Figure 10.19.1-1 shows an example signaling flow for Conditional Handover with Secondary Node. + +NOTE 1: For a CHO without SN change, the source SN and the target SN shown in Figure 10.19.1-1 are the same node. + +NOTE 2: For a CHO with SN addition, the source SN and steps involving the source SN in Figure 10.19.1-1 are ignored. + +- The source MN starts the conditional handover procedure by initiating the X2 Handover Preparation procedure including MCG configuration and, if the UE is configured with an SCG, SCG configuration. The source MN may include the (source) SN UE X2AP ID, SN ID, the UE context in the (source) SN and the Conditional Handover Information Request IE in the *Handover Request* message. + +NOTE 3: In case of the CHO with/without SN change, the source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration, if configured, before step 1. + +- If the candidate MN decides to keep the UE context in the SN, the candidate MN sends the *SgNB Addition Request* message to the SN including the SN UE X2AP ID as a reference to the UE context in the SN that was established by the source MN. If the candidate MN decides to change the SN allowing delta configuration, the candidate MN sends the *SgNB Addition Request* message to the candidate SN including the UE context in the source SN that was established by the source MN. Otherwise, the candidate MN may send the *SgNB Addition Request* message to the candidate SN including neither the SN UE X2AP ID nor the UE context in the source SN + +that was established by the source MN. Within the *SgNB Addition Request* message, the candidate MN also includes the CHO related information, i.e., the source MN ID and the MN UE X2AP ID in the source MN, in order to indicate that the SgNB Addition Preparation procedure is triggered in relation to a CHO and to enable the SN to identify requests related to the same UE. + +NOTE 3a: The target MN and other potential target MNs may trigger the SgNB Addition Preparation procedure to the same (target) SN. + +NOTE 3b: The source MN may initiate additional X2 Handover Preparation procedures towards the same or other target MNs. Based on each X2 Handover Preparation procedure, each target MN may decide to trigger SgNB Addition Preparation procedure. + +3. The (candidate) SN replies with the *SgNB Addition Request Acknowledge* message. The (candidate) SN may include the indication of full or delta RRC configuration. + +NOTE 4: In CHO with SCG configuration, it is up to the candidate MN implementation to make sure that the CG-Config provided from the (candidate) SN can be used in all CHO preparations. + +4. The candidate MN includes within the *Handover Request Acknowledge* message a transparent container to be sent to the UE as an RRC message to perform the conditional handover, and may also provide forwarding addresses to the source MN. The candidate MN indicates to the source MN that the UE context in the SN is kept if the candidate MN and the SN decided to keep the UE context in the SN in step 2 and step 3. + +NOTE 4a0: Steps 1-4 may be produced in several instances, each instance initiated with a separate Handover Preparation procedure (step 1). The order of messages belonging to separate instances is not defined. + +4a. The source MN sends the *Data Forwarding Address Indication* message to the (source) SN. This *Data Forwarding Address Indication* message notifies conditional handover to the (source) SN, which may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an *Early Status Transfer* message to the source MN. + +NOTE 4a: Separate Data Forwarding Address Indication procedures may be initiated to provide different forwarding addresses of the prepared conditional handovers. In this case, it is up to the source MN and SN implementations to make sure that the *Early Status Transfer* message(s) from the source SN, if any, is forwarded to the right target MN. The Data Forwarding Address Indication procedure may further be initiated to indicate to the (source) SN to stop already initiated early data forwarding for some SN-terminated bearers, if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional handovers. + +5. The source MN sends an *RRConnectionReconfiguration* message to the UE, including the CHO configuration, i.e. a list of *RRConnectionReconfiguration\** messages and associated execution conditions, in which each *RRConnectionReconfiguration\** message contains an MCG configuration and possibly an SCG configuration in the *RRReconfiguration\*\** message received from the candidate SN in step 3. + +6. The UE applies the *RRConnectionReconfiguration* message received in step 5, stores the CHO configuration and replies to the MN with an *RRConnectionReconfigurationComplete* message. + +7/8. The UE maintains connection with the source MN and, if the UE is configured with a PSCell, with the source PSCell, after receiving CHO configuration, and starts evaluating the CHO execution condition for the candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source MN, applies the stored corresponding configuration for that selected candidate cell, synchronises to that candidate cell and completes the RRC handover procedure by sending *RRConnectionReconfigurationComplete\** message to the target MN. If the stored configuration for the selected candidate cell includes an SCG configuration, the UE includes an embedded SN *RRReconfigurationComplete\*\** message for the target SN. The UE releases stored CHO configurations after successful completion of RRC handover procedure. + +NOTE 5: In case the target SN includes the indication of full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. + +9. If configured with bearers requiring SCG radio resources, the UE synchronizes to the (target) SN. + +NOTE 6: The order the UE performs Random Access towards the MN (step 7) and performs the Random Access procedure towards the (target) SN (step 9) is not defined. + +10. If the RRC connection reconfiguration procedure was successful, the target MN informs the (target) SN via *SgNB Reconfiguration Complete* message. + 11. The target MN sends the *Handover Success* message to the source MN to inform that the UE has successfully accessed the target cell. + - 12a/b. The source MN sends *SgNB Release Request* message to the (source) SN including a Cause indicating MCG mobility and, if applicable, data forwarding information. The source MN indicates to the (source) SN that the UE context in SN is kept, if it receives the indication from the target MN. The (source) SN acknowledges the release request. + - 12c. The source MN sends the *Handover Cancel* message toward the other signalling connections or other candidate MNs, if any, to cancel CHO for the UE. + - 12d/e. If the target MN is configured with other candidate PCell(s) associated with other candidate SN(s) than the target SN, the target MN sends the *SgNB Release Request* message(s) to the corresponding candidate SN(s). Other candidate MN(s) send(s) the *SgNB Release Request* message(s) to other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. + - 13a. The (source) SN sends the *Secondary RAT Data Usage Report* message to the source MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. +- NOTE 7: The order the source SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN/target SN is not defined. The SgNB may send the report when the transmission of the related bearer is stopped. +- 13b. The source MN sends the *Secondary RAT Data Usage Report* message to MME to provide information on the used NR resource. + 14. For bearers using RLC AM, the source MN sends the *SN Status Transfer* message, including, if needed, SN Status received from the source SN to the target MN. The target MN forwards the SN Status to the target SN, if needed. + 15. If applicable, data forwarding takes place from the source side (i.e. source MN or source SN). If the SN is kept, data forwarding may be omitted for SN-terminated bearers kept in the SN. + - 16-19. The target MN initiates the S1 Path Switch procedure. +- NOTE 8: If new UL TEIDs of the S-GW are included, the target MN performs the MN initiated SN Modification procedure to provide them to the SN. +20. The target MN initiates the UE Context Release procedure towards the source MN. + 21. Upon reception of the *UE Context Release* message, the (source) SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE context kept indication was included in the *SgNB Release Request* message in step 12a. + +### 10.19.2 MR-DC with 5GC + +The Conditional Handover with Secondary Node procedure is used for configuration and execution of CHO with SN or CHO with candidate SCG(s). This procedure includes the cases where the SN is kept, changed or added. If the SN is kept, the UE context at the SN is kept. If the SN is changed, the UE context at the source SN is moved to the target SN. + +CHO with candidate SCG(s) is not supported for NE-DC and NGEN-DC. + +![Sequence diagram for Conditional Handover with Secondary Node procedure. Lifelines: UE, source MN, (source) SN, (target) SN, target MN, Other potential target MN, Other potential target SN, UPF, AMF. The diagram shows the signaling flow for a conditional handover involving a secondary node, including messages like Handover Request, SN Addition Request, RRC reconfiguration, and Data Forwarding.](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +``` + +sequenceDiagram + participant UE + participant source MN + participant source SN as (source) SN + participant target SN as (target) SN + participant target MN + participant other potential target MN as Other potential target MN + participant other potential target SN as Other potential target SN + participant UPF + participant AMF + + Note left of source MN: 1. Handover Request + source MN->>target MN: 1. Handover Request + Note left of source MN: 1. Handover Request + source MN->>other potential target MN: 1. Handover Request + Note left of target MN: 2. SN Addition Request + target MN->>target SN: 2. SN Addition Request + Note left of target SN: 3. SN Addition Request Ack + target SN->>target MN: 3. SN Addition Request Ack + Note left of target MN: 3a. Xn-U Address Indication + target MN-->>other potential target SN: 3a. Xn-U Address Indication + Note left of other potential target SN: 2. SN Addition Request + other potential target SN->>other potential target MN: 2. SN Addition Request + Note left of other potential target MN: 3. SN Addition Request Ack + other potential target MN->>other potential target SN: 3. SN Addition Request Ack + Note left of other potential target MN: 3a. Xn-U Address Indication + other potential target MN-->>other potential target SN: 3a. Xn-U Address Indication + Note left of source MN: 4. Handover Request Acknowledge + source MN->>target MN: 4. Handover Request Acknowledge + Note left of source MN: 4. Handover Request Acknowledge + source MN->>other potential target MN: 4. Handover Request Acknowledge + Note left of source MN: 4a. Xn-U Address Indication + source MN-->>source SN: 4a. Xn-U Address Indication + Note left of UE: 5. RRC reconfiguration (containing MN RRC reconfiguration* and may contain SN RRC reconfiguration**) + UE->>source MN: 5. RRC reconfiguration + Note left of source MN: 6. RRC reconfiguration complete + source MN->>UE: 6. RRC reconfiguration complete + Note left of source MN: Early Data Forwarding + source MN-->>target MN: Early Data Forwarding + Note left of UE: 7. Random Access Procedure + UE->>target MN: 7. Random Access Procedure + Note left of target MN: 8. RRC reconfiguration complete* (may contain SN RRC reconfiguration complete**) + target MN->>UE: 8. RRC reconfiguration complete + Note left of UE: 9. Random Access Procedure + UE->>target SN: 9. Random Access Procedure + Note left of target SN: 10. SN Reconfiguration Complete + target SN->>target MN: 10. SN Reconfiguration Complete + Note left of target MN: 11. Handover Success + target MN->>source MN: 11. Handover Success + Note left of source MN: 12a. SN Release Request + source MN->>target SN: 12a. SN Release Request + Note left of target SN: 12b. SN Release Request Acknowledge + target SN->>source MN: 12b. SN Release Request Acknowledge + Note left of source MN: 12c. Xn-U Address Indication + source MN-->>target SN: 12c. Xn-U Address Indication + Note left of source MN: 12d. Handover Cancel + source MN->>target MN: 12d. Handover Cancel + Note left of target MN: 12e. SN Release Request + target MN->>other potential target MN: 12e. SN Release Request + Note left of other potential target MN: 12f. SN Release Request Acknowledge + other potential target MN->>target MN: 12f. SN Release Request Acknowledge + Note left of source MN: 13a. Secondary RAT Data Usage Report + source MN-->>target MN: 13a. Secondary RAT Data Usage Report + Note left of source MN: 13b. Secondary RAT Data Usage Report + source MN-->>AMF: 13b. Secondary RAT Data Usage Report + Note left of source MN: 14a. SN Status Transfer + source MN-->>target MN: 14a. SN Status Transfer + Note left of source MN: 14b. SN Status Transfer + source MN-->>AMF: 14b. SN Status Transfer + Note left of target SN: 14c. SN Status Transfer + target SN->>target MN: 14c. SN Status Transfer + Note left of source MN: 15. Data Forwarding + source MN-->>target MN: 15. Data Forwarding + Note left of target MN: 16. Path Switch Request + target MN->>AMF: 16. Path Switch Request + Note left of AMF: 17. Bearer Modification + AMF->>target MN: 17. Bearer Modification + Note left of target MN: 18a. New Path (MN terminated bearer) + target MN-->>UPF: 18a. New Path (MN terminated bearer) + Note left of target SN: 18b. New Path (SN terminated bearer) + target SN-->>UPF: 18b. New Path (SN terminated bearer) + Note left of target MN: 19. Path Switch Request Acknowledge + target MN->>AMF: 19. Path Switch Request Acknowledge + Note left of source MN: 20. UE Context Release + source MN->>target MN: 20. UE Context Release + Note left of source MN: 21. UE Context Release + source MN->>source SN: 21. UE Context Release + +``` + +Sequence diagram for Conditional Handover with Secondary Node procedure. Lifelines: UE, source MN, (source) SN, (target) SN, target MN, Other potential target MN, Other potential target SN, UPF, AMF. The diagram shows the signaling flow for a conditional handover involving a secondary node, including messages like Handover Request, SN Addition Request, RRC reconfiguration, and Data Forwarding. + +**Figure 10.19.2-1: Conditional Handover with Secondary Node procedure** + +Figure 10.19.2-1 shows an example signaling flow for Conditional Handover with Secondary Node. + +NOTE 1: For a CHO without SN change, the source SN and the target SN shown in Figure 10.19.2-1 are the same node. + +NOTE 2: For a CHO with SN addition, the source SN and steps involving the source SN in Figure 10.19.2-1 are ignored. + +1. The source MN starts the conditional handover procedure by initiating the Xn Handover Preparation procedure including MCG configuration and, if the UE is configured with an SCG, SCG configuration. The source MN includes the (source) SN UE XnAP ID, SN ID, the UE context in the (source) SN and the Conditional Handover Information Request IE in the *Handover Request* message. In case of CHO with candidate SCG(s), the source MN also provides the maximum number of conditional reconfigurations that the candidate MN can prepare for the UE in the *Handover Request* message. + +NOTE 3: In case of the CHO with/without SN change or CHO with candidate SCG(s), the source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration, if configured, before step 1. + +2. If the candidate MN decides to keep the UE context in the SN, the candidate MN sends the *SN Addition Request* message to the SN including the SN UE XnAP ID as a reference to the UE context in the SN that was established by the source MN. If the candidate MN decides to change the SN allowing delta configuration, the candidate MN sends the *SN Addition Request* message to the candidate SN including the UE context in the source SN that was established by the source MN. Otherwise, the candidate MN may send the *SN Addition Request* message to the candidate SN including neither the SN UE XnAP ID nor the UE context in the source SN that was established by the source MN. Within the *SN Addition Request* message, the candidate MN also includes the CHO related information, i.e., the source MN ID and the MN UE XnAP ID in the source MN, in order to indicate that the SN Addition Preparation procedure is triggered in relation to a CHO and to enable the SN to identify requests related to the same UE. In case of CHO with candidate SCG(s), the candidate MN also provides the candidate PSCells recommended by the candidate MN via the latest measurement results for the candidate SN(s) to choose and configure the candidate SCG cell(s), and provides the maximum number of PSCells that the candidate SN can prepare for the UE in the *SN Addition Request* message. + +NOTE 3a: The target MN and other potential target MNs may trigger the SN Addition Preparation procedure to the same (target) SN. + +NOTE 3b: The source MN may initiate additional Xn Handover Preparation procedures towards the same or other target MNs. Based on each Xn Handover Preparation procedure, each target MN may decide to trigger SN Addition Preparation procedure. + +3. The (candidate) SN replies with the *SN Addition Request Acknowledge* message. The (candidate) SN may include the indication of the full or delta RRC configuration. In case of CHO with candidate SCG(s), within the list of cells as indicated within the measurement results indicated by the candidate MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the candidate MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the candidate MN in an NR RRC reconfiguration\*\* message contained in the *SN Addition Request Acknowledge* message with the prepared PSCell ID(s). + +NOTE 4: In CHO with SCG configuration, it is up to the candidate MN implementation to make sure that the CG-Config provided from the (candidate) SN can be used in all CHO preparations. + +NOTE 4A1: In case of CHO with candidate SCG(s), the (candidate) SN assigns the same data forwarding addresses for multiple data forwarding requests from different candidate MNs and the (candidate) SN indicates to the candidate MN direct data forwarding path availability with the source SN and/or source MN, if applicable. + +- 3a. For the SN terminated bearers using MCG resources, the candidate MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message. + +4. The candidate MN includes within the *Handover Request Acknowledge* message the MN RRC reconfiguration message to be sent to the UE in order to perform the conditional handover, and may also provide forwarding addresses to the source MN. If PDU session split is performed in the target side during handover procedure, more than one data forwarding addresses corresponding to each node are included in the *Handover Request Acknowledge* message. The candidate MN indicates to the source MN that the UE context in the SN is kept if the candidate MN and the SN decided to keep the UE context in the SN in step 2 and step 3. In case of CHO with candidate SCG(s), the candidate MN includes a list of one or more (candidate) SNs in *Handover Request Acknowledge* message with the PDU Session admission results, data forwarding addresses and list of prepared PSCells for each prepared (candidate) SN. The candidate MN also indicates to the source MN the parameters of the execution condition of each prepared candidate PSCell. + +NOTE 4A2: In case of CHO with candidate SCG(s), the candidate MN indicates direct data forwarding path availability between the target node and the source SN in per PDU session granularity in the *Handover Request Acknowledge* message, if applicable. + +NOTE 4a0: Steps 1-4 may be produced in several instances, each instance initiated with a separate Handover Preparation procedure (step 1). The order of messages belonging to separate instances is not defined. + +- 4a. The source MN sends the *Xn-U Address Indication* message to the (source) SN. This *Xn-U Address Indication* message notifies conditional handover to the (source) SN, which may decide to perform, if applicable, early data + +forwarding for SN-terminated bearers, together with the sending of an *Early Status Transfer* message to the source MN. + +NOTE 4a: Separate Xn-U Address Indication procedures may be initiated to provide different forwarding addresses of the prepared conditional handovers. In this case, it is up to the source MN and SN implementations to make sure that the *Early Status Transfer* message(s) from the source SN, if any, is forwarded to the right target MN. The Xn-U Address Indication procedure may further be initiated to indicate to the (source) SN to stop already initiated early data forwarding for some SN-terminated bearers, if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional handovers. + +5. The source MN sends an RRC reconfiguration message to the UE, including the CHO configuration, i.e. a list of RRC reconfiguration\* messages and associated execution conditions, in which each RRC reconfiguration\* message contains an MCG configuration and possibly an SCG configuration in the RRC reconfiguration\*\* message received from the candidate SN in step 3. For each configuration of CHO with candidate SCG(s), the source MN provides an execution condition for the candidate PCell and an execution condition for the candidate PSCell. Besides, each RRC reconfiguration\* message contains an MCG configuration and an SCG configuration in the RRC reconfiguration\*\* message received from the candidate SN in step 3. + +NOTE 4b: In case of CHO with candidate SCG(s), the source MN can provide multiple CHO configurations for the same candidate PCell (i.e. without the SCG configuration or with the SCG configuration of different candidate PSCell). + +6. The UE applies the RRC reconfiguration message received in step 5, stores the CHO configuration and replies to the MN with an RRC reconfiguration complete message. + +7/8. The UE maintains connection with the source MN and, if the UE is configured with a PSCell, with the source PSCell, after receiving CHO configuration, and starts evaluating the execution condition for the candidate PCell(s) and if any, the execution condition for the candidate PSCell(s): + +- If at least one candidate PCell satisfies the corresponding execution condition and the associated candidate PSCell satisfies the corresponding execution condition, the UE detaches from the source MN, applies the stored corresponding configuration for that selected candidate PCell and the associated candidate PSCell, synchronises to that candidate PCell, and completes the RRC handover procedure by sending RRC reconfiguration complete\* message to the target MN. The UE includes an embedded SN RRCReconfigurationComplete\*\* message for the target SN, and information enabling the target MN to identify the target SN of the selected candidate PSCell. +- Else if at least one candidate PCell satisfies the corresponding execution condition and there is no associated execution condition for a candidate PSCell, the UE detaches from the source MN, applies the stored corresponding configuration for that selected candidate PCell and, if included, the associated PSCell, synchronises to that candidate PCell and completes the RRC handover procedure by sending RRC reconfiguration complete\* message to the target MN. If the stored configuration for the selected candidate PCell includes an SCG configuration, the UE includes an embedded SN RRCReconfigurationComplete\*\* message for the target SN. +- The UE releases the stored CHO configurations after successful completion of the RRC handover procedure. + +NOTE 5: In case the target SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. + +9. If configured with bearers requiring SCG radio resources, the UE synchronizes to the (target) SN. + +NOTE 6: The order the UE performs Random Access towards the MN (step 7) and performs the Random Access procedure towards the (target) SN (step 9) is not defined. + +10. If the RRC connection reconfiguration procedure was successful, the target MN informs the (target) SN via *SN Reconfiguration Complete* message. + +11. The target MN sends the *Handover Success* message to the source MN to inform that the UE has successfully accessed the target cell. In case of CHO with candidate SCG(s), the target PSCell ID may also be included in the *Handover Success* message. + +- 12a/b. The source MN sends *SN Release Request* message to the (source) SN including a Cause indicating MCG mobility. The source MN indicates to the (source) SN that the UE context in SN is kept, if it receives the indication from the target MN. The (source) SN acknowledges the release request. + +- 12c. The source MN sends *XN-U Address Indication* message to the (source) SN to transfer data forwarding information. More than one data forwarding addresses may be provided if the PDU session is split in the target side. + - 12d. The source MN sends the *Handover Cancel* message toward the other signalling connections or other candidate MNs, if any, to cancel CHO for the UE. + - 12e/f. If the target MN is configured with other candidate PCell(s) associated with other candidate SN(s) than the target SN, the target MN sends the *SN Release Request* message(s) to the corresponding candidate SN(s). Other candidate MN(s) send(s) the *SN Release Request* message(s) to other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. + - 13a. The (source) SN sends the *Secondary RAT Data Usage Report* message to the source MN and includes the data volumes delivered to and received from the UE over the NR/E-UTRA radio as described in clause 10.11.2. +- NOTE 7: The order the source SN sends the *Secondary RAT Data Usage Report* message and performs data forwarding with MN/target SN is not defined. The SN may send the report when the transmission of the related QoS is stopped. +- 13b. The source MN sends the *Secondary RAT Data Usage Report* message to AMF to provide information on the used NR/E-UTRA resource. + - 14. For bearers using RLC AM, the source MN sends the *SN Status Transfer* message to the target MN, including, if needed, SN Status received from the source SN. The target MN forwards the SN Status to the target SN, if needed. + - 15. If applicable, data forwarding takes place from the source side (i.e. source MN or source SN). If the SN is kept, data forwarding may be omitted for the SN terminated bearers or QoS flows kept in the SN. + - 16-19. The target MN initiates the Path Switch procedure. If the target MN includes multiple DL TEIDs for one PDU session in the *Path Switch Request* message, multiple UL TEID of the UPF for the PDU session should be included in the *Path Switch Ack* message in case there is TEID update in UPF. +- NOTE 8: If new UL TEIDs of the UPF for SN are included, the target MN performs MN initiated SN Modification procedure to provide them to the SN. +- 20. The target MN initiates the UE Context Release procedure towards the source MN. + - 21. Upon reception of the *UE Context Release* message from source MN, the (source) SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE context kept indication was included in the *SN Release Request* message in step 12a. + +### 10.19.3 CHO with candidate SCG(s) + +A CHO with candidate SCG(s) is defined as a PCell change with PSCell addition/change that is executed by the UE when the execution conditions for both candidate PCell and the associated candidate PSCell are met. The UE starts evaluating the execution conditions for candidate PCell(s) and candidate PSCell(s) simultaneously upon receiving the CHO with candidate SCG(s) configuration, and stops evaluating the execution conditions once a PCell change or a PSCell change is triggered. The UE does not execute CHO with candidate SCG(s) until the execution conditions for both the candidate PCell and the associated candidate PSCell are met. + +## 10.20 Subsequent Conditional PSCell Addition or Change + +A Subsequent Conditional PSCell Addition or Change (subsequent CPAC) is defined as a conditional PSCell addition or change procedure that is executed after a PSCell addition, a PSCell change, a PCell change or an SCG release based on pre-configured subsequent CPAC configuration of candidate PSCell(s) without reconfiguration and re-initiation of CPC/CPA. The UE keeps the configured subsequent CPAC configuration (unless the network indicates to release it) and evaluates the execution conditions of candidate PSCells after completion of a PSCell addition, a PSCell change, a PCell change or an SCG release. Intra-SN subsequent CPAC initiated by the SN, inter-SN subsequent CPAC initiated by either MN or SN are supported. + +The following principles apply to subsequent CPAC: + +- For MN initiated subsequent CPAC, the MN initially triggers the candidate cell preparation of subsequent CPAC procedure and generates the execution conditions for the initial execution of subsequent CPAC (e.g. CPA or CPC). +- For SN initiated subsequent CPAC, the source SN initially triggers the candidate cell preparation of subsequent CPAC procedure and generates the execution conditions for the initial execution of subsequent CPAC. +- For both MN and SN initiated inter-SN subsequent CPAC, the candidate SN generates the execution conditions for the following execution of subsequent CPAC when the candidate SN prepares the candidate SCG configuration(s) for candidate PSCell(s). For SN initiated intra-SN subsequent CPAC, the source SN generates the execution conditions for the following execution of subsequent CPAC when the source SN prepares the candidate SCG configuration(s) for candidate PSCell(s). +- The subsequent CPAC configuration contains candidate SCG configuration(s) of candidate PSCell(s), execution conditions, and may contain the MCG configuration (to be applied when subsequent CPAC execution is triggered), the reference configuration and the security update configuration. +- The subsequent CPAC configuration for CPA or inter-SN CPC candidate PSCell(s) is provided in MN format. The subsequent CPAC configuration for intra-SN CPC candidate PSCell(s) is provided in MN format or SN format. It's up to the source SN to decide which format to be used for intra-SN subsequent CPAC. +- For one UE, the subsequent CPAC configuration for all candidate PSCells (including inter-SN and/or intra-SN) is provided in the same format, i.e., either MN format, or SN format. If the configured candidate PSCell(s) includes at least one inter-SN CPC candidate PSCell, the subsequent CPAC configuration can only be provided in MN format. If only intra-SN CPC candidate PSCell(s) is configured, the subsequent CPAC configuration can be provided in either MN format or SN format. +- Each candidate PSCell configuration is provided as a delta configuration on top of a reference configuration or a complete configuration. Only one reference configuration is supported. +- The MN generates the MCG part of the reference configuration (if any), while the SN generates the SCG part of the reference configuration. The MN can request an SCG reference configuration from any one of the involved SNs. +- The network explicitly configures a subsequent CPAC configuration for the current serving PSCell if the network wants to use that PSCell as a candidate PSCell for subsequent CPAC. +- The network always explicitly releases the subsequent CPAC configuration for candidate PSCells after an inter-MN PCell change. +- Upon the release of SCG, the UE releases the stored subsequent CPAC configuration in SN format. Upon the release of SCG, the UE releases or maintains the stored subsequent CPAC configuration in MN format according to the network indication. +- The same candidate PSCell configuration can be used for CPA execution and CPC execution, but with different execution conditions of the candidate PSCell. +- The subsequent CPAC configuration with CPA execution condition(s) maintained after SCG release can be used for the subsequent CPA execution. +- Upon inter-SN subsequent CPAC execution, the UE uses the first unused sk-Counter value for S-KgNB generation, based on the per-SN pre-configured sk-Counter value list. +- Upon PCell change, PSCell change or SCG release, if the subsequent CPAC configuration is maintained, the UE also maintains the unused sk-Counter values. + +### **MN initiated subsequent CPAC** + +The subsequent CPAC procedure is initiated by the MN for inter-SN subsequent CPAC configuration and inter-SN subsequent CPAC execution. + +![](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +Sequence diagram illustrating the interaction between UE, MN, SN-1, SN-2, and SN-3 during a multi-SN addition and modification procedure. + +The diagram is divided into three phases: + +- Preparation phase** +- Initial evaluation & execution phase** +- Subsequent evaluation & execution phase** + +**Preparation phase:** + +- MN sends **1: SN ADDITION REQUEST** to SN-1. +- SN-1 sends **2: SN ADDITION REQUEST ACKNOWLEDGE** to MN. +- MN sends **3: SN ADDITION REQUEST** to SN-2. +- SN-2 sends **4: SN ADDITION REQUEST ACKNOWLEDGE** to MN. +- MN sends **5: Xn-U ADDRESS INDICATION** to SN-1, SN-2, and SN-3 (dashed lines). +- MN sends **6: SN MODIFICATION REQUEST** to SN-1, SN-2, and SN-3 (dashed lines). +- SN-1 sends **7: SN MODIFICATION REQUEST ACKNOWLEDGE** to MN (dashed lines). +- MN sends **8: RRCReconfiguration** to UE. +- UE sends **9: RRCReconfigurationComplete** to MN. +- MN sends **10: Early Data Forwarding** to SN-1, SN-2, and SN-3 (dashed blue lines). + +**Initial evaluation & execution phase:** + +- UE sends **11: RRCReconfigurationComplete** to MN. +- MN sends **12: SN RECONFIGURATION COMPLETE** to SN-1. +- SN-1 initiates **13: Random Access Procedure** with UE. +- MN sends **14: SN STATUS TRANSFER** to SN-1. +- MN sends **15: Data Forwarding** to SN-1 (dashed green line). +- MN sends **16: Xn-U ADDRESS INDICATION** to SN-1. +- SN-1 sends **17: Early Data Forwarding** to SN-2 and SN-3 (dashed blue lines). + +**Subsequent evaluation & execution phase:** + +- UE sends **18: RRCReconfigurationComplete** to MN. +- MN sends **19: SN RECONFIGURATION COMPLETE** to SN-2. +- SN-2 initiates **20: Random Access Procedure** with UE. +- MN sends **21: SN MODIFICATION REQUEST** to SN-1. +- SN-1 sends **22: SN MODIFICATION REQUEST ACKNOWLEDGE** to MN. +- MN sends **23: Xn-U ADDRESS INDICATION** to SN-1. +- MN sends **24: SN STATUS TRANSFER** to SN-1. +- MN sends **25: SN STATUS TRANSFER** to SN-2 (dashed line). +- MN sends **26: Data Forwarding** to SN-2 (dashed green line). +- MN sends **27: Xn-U ADDRESS INDICATION** to SN-2. +- SN-2 sends **28: Early Data Forwarding** to SN-3 (dashed blue line). + +**Figure 10.20-1: Inter-SN subsequent CPAC - MN initiated** + +Figure 10.20-1 shows an example signalling flow for the inter-SN subsequent CPAC initiated by the MN: + +1/2/3/4. The MN initiates the inter-SN subsequent CPAC by requesting the candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure, indicating that the request is for subsequent CPAC. The MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN(s) to choose and configure the SCG cell(s), provides the upper limit for the number of PSCells that can be prepared by each candidate SN, and provides a list of $K_{SN}$ and associated sk-Counter values for each candidate SN. In the SN Addition procedure, the MN also includes information of other candidate SN(s), and for each candidate SN, a list of cells recommended by the MN via the latest measurement results for the candidate SN to select the PSCell(s) for the following execution of subsequent CPAC. Within the list of cells as indicated within the measurement results indicated by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR *RRCReconfiguration\*\** message contained in the *SN Addition Request Acknowledge* message with the prepared PSCell ID(s). For each prepared PSCell, the candidate SN also decides the list of PSCell(s) and associated execution conditions proposed for the following execution of subsequent CPAC. If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN may also propose data forwarding to the MN or other candidate SN(s) for subsequent CPAC. The candidate SN includes the indication of the complete or delta RRC configuration with respect to the SCG reference configuration. For the prepared PSCell(s) and the proposed PSCell(s) for the following execution of subsequent CPAC, the candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. + +The MN may select one of the candidate SN(s) and requests providing the SCG reference configuration as part of the SN Addition procedure. Once obtained, the MN provides the SCG reference configuration to other candidate SN(s). + +NOTE 1: If the UE was configured with SN-1 in Dual Connectivity operation (i.e. SN-1 is the source SN), then the MN starts the subsequent CPAC operation with SN-1 via the MN-initiated SN Modification procedure instead of the SN Addition procedure. + +NOTE 2: If the UE was configured with SN-1 in Dual Connectivity operation (i.e. SN-1 is the source SN), then the MN may trigger the MN-initiated SN Modification procedure to SN-1 to retrieve the current SCG configuration or request a SCG reference configuration for the subsequent CPAC, and to allow provision of data forwarding related information before step 1. + +NOTE 3: If applicable, the MN stores the data forwarding addresses and data forwarding proposals provided from all the candidate SN(s). + +5. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message to the candidate SN(s). + +6/7. If the lists of prepared PSCells received from the candidate SN(s) in steps 2 and 4 are different than the lists of proposed PSCells, e.g., when not all proposed PSCells were accepted by the candidate SN(s), the MN may initiate the SN Modification procedures towards all the candidate SN(s) to inform them about the updated lists of prepared PSCells in other candidate SN(s). If requested, the candidate SN(s) sends an SN Modification Request Acknowledge message and if needed, provides the updated candidate SCG configurations and/or the execution conditions for the following execution of subsequent CPAC to the MN. + +8. The MN sends to the UE an *RRCReconfiguration* message including the subsequent CPAC configuration, i.e. a list of *RRCReconfiguration\** messages and associated execution conditions for the subsequent CPAC, in which each *RRCReconfiguration\** message contains the SCG configuration in the *RRCReconfiguration\*\** message received from one of the candidate SN(s) in steps 2 and 4, and possibly an MCG configuration. Besides, the *RRCReconfiguration* message can also include an updated source MCG configuration, e.g., to configure the required conditional measurements. The *RRCReconfiguration* message also includes a security update configuration and may also include a reference configuration. + +9. The UE applies the *RRCReconfiguration* message received in step 8, stores the subsequent CPAC configuration and replies to the MN with an *RRCReconfigurationComplete* message. In case the UE is unable to comply with (part of) the configuration included in the *RRCReconfiguration* message, it performs the reconfiguration failure procedure. + +11. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies *RRCREconfiguration\** message corresponding to the selected candidate PSCell, and sends an MN *RRCREconfigurationComplete\** message, including an *RRCREconfigurationComplete\*\** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. The *RRCREconfigurationComplete\** message may also include the sk-Counter value associated with the selected candidate PSCell if a new sk-Counter value is selected. +12. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via *SN Reconfiguration Complete* message, including the *RRCREconfigurationComplete\*\** message. If the sk-Counter value is received by the *RRCREconfigurationComplete\** message, the MN also indicates the received sk-Counter value to the SN. +13. The UE performs synchronisation towards the PSCell indicated in the *RRCREconfiguration\** message applied in step 11. The order the UE sends the MN *RRCREconfigurationComplete\** message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Reconfiguration procedure. +14. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the *SN Status Transfer* message. +15. For SN terminated bearers or QoS flows moved from the MN, dependent on the characteristics of the respective bearer or QoS flow, the MN may take actions to minimise service interruption due to activation of MR-DC (Data forwarding). +16. If data forwarding is needed, the MN may send the *Xn-U Address Indication* message to the selected candidate SN. The SN may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an *Early Status Transfer* message to the source MN. + +NOTE 4: Separate Xn-U Address Indication procedures may be initiated to provide different forwarding addresses of the prepared subsequent CPAC. In this case, it is up to the MN and the candidate SN implementations to make sure that the *Early Status Transfer* message(s) from the selected SN, if any, is forwarded to the right other candidate SN. + +18. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies *RRCREconfiguration\** message corresponding to the selected candidate PSCell, and sends an MN *RRCREconfigurationComplete\** message, including an *RRCREconfigurationComplete\*\** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. The *RRCREconfigurationComplete\** message may also include a sk-Counter value associated with the selected candidate PSCell if a new sk-Counter value is selected. +19. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via *SN Reconfiguration Complete* message, including the *RRCREconfigurationComplete\*\** message. If the sk-Counter value is received by the *RRCREconfigurationComplete\** message, the MN also indicates the received sk-Counter value to the SN. +20. The UE performs synchronisation towards the PSCell indicated in the *RRCREconfiguration\** message applied in step 18. The order the UE sends the MN *RRCREconfigurationComplete\** message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Reconfiguration procedure. +- 21/22/23. The MN triggers the MN initiated SN Modification procedure to inform the last serving SN to stop providing user data to the UE, to switch to the prepared state, and if applicable, to allow provisioning of new data forwarding addresses. If applicable, the MN triggers the Xn-U Address Indication procedure to inform the last serving SN the address of the SN of the selected candidate PSCell, to start late data forwarding. +- 24/25. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN sends the *SN Status Transfer* message to MN, which the MN sends then to the SN of the selected candidate PSCell, if needed. +26. If applicable, data forwarding from the last serving SN takes place. It may be initiated as early as the the last serving SN receives the early data forwarding address in step 17. + +27. If data forwarding is needed, the MN may send the *Xn-U Address Indication* message to the selected candidate SN. The SN may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an *Early Status Transfer* message to the source MN. + +NOTE 5: Separate Xn-U Address Indication procedures may be initiated to provide different forwarding addresses of the prepared subsequent CPAC. In this case, it is up to the MN and candidate SN implementations to make sure that the *Early Status Transfer* message(s) from the selected SN, if any, is forwarded to the right other candidate SN. + +### **SN initiated subsequent CPAC** + +The subsequent CPAC procedure is initiated by the SN for inter-SN subsequent CPAC configuration and inter-SN subsequent CPAC execution. + +![Sequence diagram for Inter-SN subsequent CPAC - SN initiated. The diagram shows signaling between UE, MN, SN-1, SN-2, and SN-3 across three phases: Preparation, Initial evaluation & execution, and Subsequent evaluation & execution.](c21bad844b5cb6026c067a1f43ce67c3_img.jpg) + +The sequence diagram illustrates the signaling flow for an inter-SN subsequent CPAC procedure initiated by the source SN (SN-1). The participants involved are the User Equipment (UE), Master Node (MN), Source SN (SN-1), Target SN-2 (SN-2), and Target SN-3 (SN-3). The procedure is divided into three main phases: + +- Preparation phase:** + - The MN sends a **1: SN CHANGE REQUIRED** message to SN-1. + - SN-1 sends a **2: SN ADDITION REQUEST** to SN-2. + - SN-1 sends a **3: SN ADDITION REQUEST** to SN-3. + - SN-2 sends a **4: SN ADDITION REQUEST ACKNOWLEDGE** to SN-1. + - SN-3 sends a **5: SN ADDITION REQUEST ACKNOWLEDGE** to SN-1. + - SN-1 sends a **6: Xn-U ADDRESS INDICATION** to SN-2 (dashed line). + - SN-1 sends a **6: Xn-U ADDRESS INDICATION** to SN-3 (dashed line). + - SN-1 sends a **7: SN MODIFICATION REQUEST** to SN-2 (dashed line). + - SN-1 sends a **7: SN MODIFICATION REQUEST** to SN-3 (dashed line). + - SN-2 sends a **8: SN MODIFICATION REQUEST ACKNOWLEDGE** to SN-1 (dashed line). + - SN-3 sends a **8: SN MODIFICATION REQUEST ACKNOWLEDGE** to SN-1 (dashed line). + - The MN sends a **9: RRCReconfiguration** message to the UE. + - The UE sends a **10: RRCReconfigurationComplete** message to the MN. + - The MN sends a **11: SN CHANGE CONFIRM** message to SN-1. + - SN-1 sends a **12: Early Data Forwarding** message to SN-2 (dashed blue line). + - SN-1 sends a **12: Early Data Forwarding** message to SN-3 (dashed blue line). +- Initial evaluation & execution phase:** + - The UE sends a **13: RRCReconfigurationComplete** message to the MN. + - The MN sends a **14: SN RECONFIGURATION COMPLETE** message to SN-2. + - The MN initiates a **15: Random Access Procedure** with the UE. + - The MN sends a **16: SN MODIFICATION REQUEST** message to SN-1. + - SN-1 sends a **17: SN MODIFICATION REQUEST ACKNOWLEDGE** message to the MN (dashed line). + - The MN sends a **18: Xn-U ADDRESS INDICATION** message to SN-1. + - The MN sends a **19: SN STATUS TRANSFER** message to SN-1. + - SN-1 sends a **20: SN STATUS TRANSFER** message to SN-2 (dashed line). + - SN-1 sends a **21: Data Forwarding** message to the UE (dashed green line). + - SN-1 sends a **21: Data Forwarding** message to SN-2 (dashed green line). + - The MN sends a **22: Xn-U ADDRESS INDICATION** message to SN-2. + - SN-2 sends a **23: Early Data Forwarding** message to SN-3 (dashed blue line). + - SN-3 sends a **23: Early Data Forwarding** message back to SN-2 (dashed blue line). +- Subsequent evaluation & execution phase:** + - The MN initiates the **24: Subsequent evaluation & execution phase**. + +Sequence diagram for Inter-SN subsequent CPAC - SN initiated. The diagram shows signaling between UE, MN, SN-1, SN-2, and SN-3 across three phases: Preparation, Initial evaluation & execution, and Subsequent evaluation & execution. + +**Figure 10.20-2: Inter-SN subsequent CPAC - SN initiated** + +Figure 10.20-2 shows an example signalling flow for the inter-SN subsequent CPAC initiated by the source SN: + +1. The source SN (i.e. SN-1) initiates the inter-SN subsequent CPAC procedure by sending the *SN Change Required* message, which contains a subsequent CPAC initiation indication. The message also contains candidate node ID(s) and may include an SCG reference configuration (to support delta configuration), and contains the measurements results which may include cells that are not subsequent CPAC candidates. The message also includes a list of proposed PSCell candidates recommended by the source SN, including execution + +conditions for the initial evaluation, the upper limit for the number of PSCells that can be prepared by each candidate SN, and may also include the SCG measurement configurations for subsequent CPAC (e.g. measurement ID(s) to be used for subsequent CPAC). + +2/3/4/5. The MN requests each candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure(s), indicating the request is for subsequent CPAC, and the measurements results which may include cells that are not subsequent CPAC candidates received from the source SN to the candidate SN, and indicating a list of proposed PSCell candidates to the candidate SN(s) received from the source SN, but not including execution conditions. The MN also includes information of other candidate SN(s), and for each candidate SN, a list of proposed PSCell candidates recommended by the source SN for the candidate SN to select the PSCell(s) for the following execution of subsequent CPAC. The MN also provides the upper limit for the number of PSCells that can be prepared by each candidate SN and provides a list of $K_{SN}$ and associated $sk$ -Counter values for each candidate SN. Within the list of PSCells suggested by the source SN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR *RRCREconfiguration\*\** message contained in the *SN Addition Request Acknowledge* message with the prepared PSCell ID(s). For each prepared PSCell, the candidate SN also decides the list of PSCell(s) and associated execution conditions proposed for the following execution of subsequent CPAC. If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN may also propose data forwarding to the MN or other candidate SN(s) for subsequent CPAC. The candidate SN includes the indication of the complete or delta RRC configuration with respect to the SCG reference configuration. For the prepared PSCell(s) and the proposed PSCell(s) for the following execution of subsequent CPAC, the candidate SN can either accept or reject each of the candidate cells suggested by the source SN, i.e. it cannot configure any alternative candidates. + +The MN may select one of the candidate SN(s) and requests providing the reference SCG configuration as part of the SN Addition procedure. Once obtained, the MN provides the reference configuration to other candidate SN(s). + +NOTE 6: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to request a reference configuration for the subsequent CPAC before step 2. + +NOTE 7: If applicable, the MN stores the data forwarding addresses and data forwarding proposals provided from all the candidate SN(s) and the source SN. + +6. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the *Xn-U Address Indication* message to the candidate SN(s). + +7/8. If the lists of prepared PSCells received from the candidate SN(s) in steps 3 and 5 are different than the lists of proposed PSCells, e.g., when not all proposed PSCells were accepted by the candidate SN(s), the MN may initiate the SN Modification procedures towards the source SN and all the candidate SN(s) to inform them about the updated lists of prepared PSCells in other candidate SN(s). If requested, the source SN or the candidate SN(s) sends an SN Modification Request Acknowledge message and if needed, provides the updated candidate SCG configurations and/or the execution conditions for the following execution of subsequent CPAC for the prepared PSCell to the MN. + +9. The MN sends to the UE an *RRCREconfiguration* message including the subsequent CPAC configuration, i.e. a list of *RRCREconfiguration\** messages and associated execution conditions for the subsequent CPAC, in which each *RRCREconfiguration\** message contains the SCG configuration in the *RRCREconfiguration\*\** message received from one of the candidate SN(s) in steps 3 and 5, and possibly an MCG configuration. Besides, the *RRCREconfiguration* message can also include an updated MCG configuration, as well as the NR *RRCREconfiguration\*\*\** message generated by the source SN, e.g., to configure the required conditional measurements. The *RRCREconfiguration* message also includes a security update configuration and may also include a reference configuration. + +10. The UE applies the *RRCREconfiguration* message received in step 9, stores the subsequent CPAC configuration and replies to the MN with an *RRCREconfigurationComplete* message, which can include an NR *RRCREconfigurationComplete\*\*\** message. In case the UE is unable to comply with (part of) the configuration included in the *RRCREconfiguration* message, it performs the reconfiguration failure procedure. + +11/12. If an SN RRC response message is included, the MN informs the source SN with the SN *RRCREconfigurationComplete\*\*\** message via *SN Change Confirm* message. If step 7 and 8 towards the source SN are skipped, the MN will indicate the candidate PSCells accepted by each candidate SN to the source SN in the *SN Change Confirm* message. + +The MN sends the *SN Change Confirm* message towards the source SN to indicate that subsequent CPAC is prepared, and in such case the source SN continues providing user data to the UE. If early data forwarding is applied, the MN informs the source SN the data forwarding addresses as received from the candidate SN(s), the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. In case multiple candidate SNs are prepared, the MN includes a list of Target SN ID and list of data forwarding addresses to the source SN. + +NOTE 8: The Xn-U Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some PDCP SDUs if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional PSCell change. + +NOTE 9: For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN(s). + +13. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies *RRReconfiguration\** message corresponding to the selected candidate PSCell, and sends an MN *RRReconfigurationComplete\** message, including an *RRReconfigurationComplete\*\** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. The *RRReconfigurationComplete\** message may also include the sk-Counter value associated with the selected candidate PSCell if a new sk-Counter value is selected. + 14. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via *SN Reconfiguration Complete* message, including the *RRReconfigurationComplete\*\** message. If the sk-Counter value is received by the *RRReconfigurationComplete\** message, the MN also indicates the received sk-Counter value to the SN. + 15. The UE performs synchronisation towards the PSCell indicated in the *RRReconfiguration\** message applied in step 13. The order the UE sends the MN *RRReconfigurationComplete\** message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Reconfiguration procedure. + - 16/17/18. If the source SN is configured as a candidate SN, the MN triggers the MN initiated SN Modification procedure to inform the source SN to stop providing user data to the UE, to switch to the prepared state, and if applicable, to allow provisioning of new data forwarding addresses. If applicable, the MN triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell, to start late data forwarding. If the source SN is not configured as a candidate SN, the MN triggers the MN initiated SN Release procedure to inform the source SN to stop providing user data to the UE, and triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell and if applicable, starts late data forwarding. + - 19/20. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN sends the *SN Status Transfer* message to MN, which the MN sends then to the SN of the selected candidate PSCell, if needed. + 21. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the the source SN receives the early data forwarding address in step 12. + 22. If data forwarding is needed, the MN may send the *Xn-U Address Indication* message to the selected candidate SN. The SN may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an *Early Status Transfer* message to the source MN. +- NOTE 10: Separate Xn-U Address Indication procedures may be initiated to provide different forwarding addresses of the prepared subsequent CPAC. In this case, it is up to the MN and the candidate SN implementations to make sure that the *Early Status Transfer* message(s) from the selected SN, if any, is forwarded to the right other candidate SN. +24. In subsequent evaluation and execution phase, i.e., for the following execution of subsequent CPAC, the similar steps as steps 13~23 are performed. + +# --- 11 Service related aspects + +## 11.1 Roaming and Access Restrictions + +The principles for conveying roaming and access restriction info for EN-DC are described in TS 36.300 [2]. + +For MR-DC with 5GC, SCG (re)selection at the SN is based on roaming and access restriction information in SN. If roaming and access restriction information is not available at the SN, the SN shall consider that there is no restriction for SCG (re)selection. Therefore, the MN needs to convey the latest roaming and access restriction information as received from the Core Network or another NG-RAN node to the SN via XnAP messages. + +## 11.2 Support of Network Sharing + +E-UTRAN and NG-RAN aspects of network sharing are specified in TS 36.300 [2] and TS 38.300 [3]. + +## 11.3 ARPI/SPID Handling from MN + +Usage of the Subscriber Profile ID for RAT/Frequency Priority (SPID) and the Additional RRM Policy Index (ARPI) in E-UTRAN is specified in TS 36.300 [2] and applies to EN-DC. Therefore, the MN needs to convey the up-to-date ARPI/SPID information to the SN via X2AP messages. + +# --- 12 X2/Xn Interface related aspects + +Stage 2 specification for X2-C procedures for EN-DC is contained in TS 36.300 [2]. + +Xn-C procedures for MR-DC with 5GC are specified in TS 38.423 [5]. + +X2-U procedures for EN-DC and Xn-U procedures for MR-DC with 5GC are specified in TS 38.425 [6]. + +# --- 13 Other aspects + +## 13.1 Interference avoidance for in-device coexistence + +IDC solution as described in TS 36.300 [2] and TS 38.300 [3] is extended to address EN-DC/NR-DC operation. For the FDM solution, the list of NR carriers or NR frequency ranges suffering from IDC problems is signalled in IDC report. For the TDM solution, a periodic pattern can be signalled per-CG in IDC report. In EN-DC, the MN can configure the UE to report FDM assistance information with affected carriers. In NR-DC, the MN can configure the UE to report FDM assistance information with affected frequency ranges and/or TDM assistance information. For both EN-DC and NR-DC, the SN can configure the UE to report FDM assistance information with affected frequency ranges and/or TDM assistance information to the SN via SRB1 or SRB3, if SRB3 is configured and the SCG is activated. The network can also configure autonomous denial per-CG for the UE to solve IDC problems. The requirement on RRM/RLM/CSI measurements in different phases of IDC interference defined in TS 36.300 [2] is applicable except that for NR serving cell, the requirements in TS 38.133 [8] and TS 38.101-1 [12], TS 38.101-2 [13], TS 38.101-3 [14] apply. + +## 13.2 Sidelink + +NR Sidelink Communication, V2X Sidelink Communication, NR Sidelink Discovery and Ranging/Sidelink Positioning cannot be configured in MR-DC in this release. + +## 13.3 SCG UE history information + +The MN stores and correlates the UE History Information from MN and SN(s) as long as the UE stays in MR-DC, forwards UE History Information and optional UE History Information from the UE to its connected SNs. The resulting information is then used by SN for dual-connectivity operation. The SN is in charge of collecting SCG UE history information and providing the collected information to the MN. + +If the UE stays in a PSCell for a duration exceeding the maximum value of the Time Stay parameter, the SN may store the PSCell information with consecutive entries using the same PSCell identity. The total stay time in this PSCell is the sum of stay time for all consecutive PSCell with the same identity. + +The SN shall provide the collected SCG UE history information, if available, to the MN in the following procedures: + +- the SN Release, and SN initiated SN Change procedures +- the MN initiated SN Modification procedure if requested by the MN in this procedure +- the SN initiated SN modification procedure upon PSCell change if subscribed in the SN Addition procedure + +When the target NG-RAN node receives the SCG UHI from the source NG-RAN node via Handover Request message for CHO, the target NG-RAN node updates the time UE stayed in cell of the latest PSCell entry (i.e. the source PSCell) when the UE successfully accesses to a candidate cell of the target NG-RAN node. The updated value of the time UE stayed in the source PSCell is equal to the value received from the source NG-RAN node during the Handover Preparation plus the time from receiving Handover Request message from the source NG-RAN node to receiving RRC Reconfiguration Complete message from the UE. + +When the target SN receives the SCG UHI from the MN via SN Addition Request message for CPC, the target SN updates the time UE stayed in the cell of the latest PSCell entry (i.e. the source PSCell) when the UE successfully accesses to a candidate cell of the target SN. The updated value of the time UE stayed in the latest PSCell is equal to the value received from the MN via the SN Addition Request message plus the time from receiving SN Addition Request message from the MN to receiving SN Reconfiguration Complete from the MN. + +## 13.4 Application Layer Measurement Collection + +### 13.4.1 Overview + +The QoE Measurement Collection function as described in TS 38.300 [3] is extended to address the NR-DC operation. The requirements on the gNB provided in TS 38.300 [3] apply to the MN, together with additional requirements on the MN and the SN provided in following sub-clauses. + +### 13.4.2 SRB5 + +SRB5 is supported in NR-DC, but not in EN-DC, NGEN-DC and NE-DC. + +The decision to establish SRB5 is taken by the SN, which provides the SRB5 configuration using an SN RRC message. SRB5 establishment and release can be done at Secondary Node Addition and Secondary Node Change. SRB5 reconfiguration can be done at Secondary Node Modification procedure. + +SRB5 is used to send RRC messages (i.e., *MeasurementReportAppLayer* message) including application layer measurement report information directly to the SN. + +SRB5 is modelled as one of the SRBs defined in TS 38.331 [4] and uses the NR-DCCH logical channel type. + +When the SCG is released, SRB5 is released. + +### 13.4.3 QoE Measurement Configuration + +#### 13.4.3.1 QoE Measurement Collection Activation and Reporting in NR-DC + +For a UE in NR-DC, either the MN or the SN can generate QoE configuration(s) and transmit the configuration to the UE. If both the MN and the SN send QoE configurations to the UE, the MN and the SN do not use the same set of + +application layer measurement configuration identities, which means there is a unique ID for QoE configurations across MN and SN. + +For a UE in NR-DC, the MN and the SN may coordinate QoE measurement collection activation and reporting as follows: + +For management-based QoE activation, the MN: + +- Allocates the application layer measurement configuration ID, and indicates it to the SN if needed; +- Determines whether the MN or the SN sends the QoE configuration to the UE, in case the SN inquires the MN. + +For management-based QoE measurement configurations received directly by the SN from OAM, the SN may perform UE selection. For a selected UE, the SN indicates to the MN the QoE reference of the management-based QoE session and, separately for the QoE reports and RAN visible QoE reports, the SN indicates whether it is going to receive the corresponding reports via the MN (using SRB4) or using SRB5. Upon receiving the request, the MN can decide and notify the SN whether the MN sends the QoE and RAN Visible QoE configuration to the UE, or whether the SN should send the configuration(s) to the UE. The SN can send a QoE and a RAN Visible QoE measurement configuration directly to the UE via SRB3, or in a transparent container to the MN, which then sends the configuration to the UE via SRB1. + +For management-based QoE configurations received from OAM and for signalling-based QoE configurations, the MN can only send the configuration to the UE via SRB1, and the UE can send the QoE reports via SRB4 or SRB5. + +For a UE in NR-DC, both SRB4 and SRB5 can be configured simultaneously for QoE reporting. The network explicitly indicates to the UE whether to send QoE reports via SRB4 or SRB5, per QoE reference, separately for QoE reports and RAN visible QoE reports. The SRB for QoE reporting can be changed during the application session. The command for changing the SRB used for reporting may be sent to the UE by the node that configured that specific QoE configuration. The node that currently receives the QoE reports via the Uu interface can request from the peer node that the QoE reporting leg is switched to the peer node per QoE Reference. The leg switch for QoE reporting needs to be approved by both nodes serving the UE. RAN visible QoE reports can be sent via the same SRB as the QoE reports pertaining to the same QoE reference, or via a different SRB. + +RAN visible QoE reports can be sent to the SN directly via SRB5, or via the MN using SRB4. + +If encapsulated QoE reports cannot be sent because the SRB configured for the encapsulated QoE reporting is not available, the UE continues to store the reports until the SRB is available or the QoE configuration is released. If RAN visible QoE reports cannot be sent because the SRB configured for RAN visible QoE measurement reporting is not available, the UE discards the RAN visible QoE report. + +The MN should inform the SN that a UE is configured with a management-based QoE/RAN visible QoE measurement configuration. + +If the MN has configured the UE with QoE measurements, and if the UE is configured to send the QoE reports to the SN, then, if the MN decides that the SN forwards the reports directly to the MCE, the MN should indicate to the SN the QoE reference, the MCE IP address and the application layer measurement configuration ID. + +If the SN has configured the UE with QoE measurements, and if the UE is configured to send the QoE reports to the MN, then, if the SN decides that the MN forwards the reports directly to the MCE, the SN should indicate to the MN the QoE reference and the MCE IP address. + +If the SN has released a QoE configuration towards a UE, the SN should inform the MN. + +When SCG is deactivated, for QoE configurations configured to use SRB5 for QoE reporting, it is up to network implementation to reconfigure the reporting leg to SRB4, release the QoE configuration or pause the QoE reporting. For UL data arrival on SRB5 while the SCG is deactivated, the UE does not indicate to the MN that it has QoE report to transmit over SRB5 for the purpose of SCG activation. + +When the SCG is released, the UE releases all the QoE measurements configured by the SCG and discards the unsent QoE reports configured to be reported via SRB5. + +In order to allow the transmission of application layer measurement reports which exceed the maximum PDCP SDU size, the network can inform the UE whether the MN allows RRC segmentation of *MeasurementReportAppLayer* message via SRB4 and whether the SN allows RRC segmentation of *MeasurementReportAppLayer* message via SRB5. + +#### 13.4.3.2 RAN Overload Handling + +In NR-DC, when RAN overload happens in the node which receives the QoE reports from the UE, the node may coordinate with its peer node to reconfigure the QoE reporting path, by sending the QoE Reporting Path Request in the *QMC Coordination Request* IE, via the SN modification procedure. + +When neither the MN nor the SN is able to receive the QoE reports due to RAN overload, the network can indicate to the UE to pause QoE reporting, as specified in TS 38.300 [3]. + +### 13.4.4 QoE Measurement Continuity for Mobility + +For ongoing sessions, QoE measurement continuity is ensured during mobility in NR-DC, e.g., during inter-MN handover (with/without SN change) and SN change scenarios. + +To ensure QoE measurement continuity during SN change, the SN-initiated SN modification procedure and/or the MN-initiated SN modification procedure can be used to provide the information about the SN-associated QMC configurations to the MN. The MN can then transfer this information to the new SN during the SN Addition procedure. + +To ensure QoE measurement continuity during inter-MN handover with SN change, the source SN should provide the information about the SN-associated QMC configurations to the source MN. During the handover procedure, the target MN is provided with all the information that the source MN has about the SN-associated QMC configuration. + +If the MN configured the UE with QoE measurements, every subsequent MN serving the UE can configure and release the RAN visible QoE measurements. + +# Annex A (informative): Layer 2 handling for bearer type change + +This clause provides for information an overview on L2 handling for bearer type change in MR-DC, with and without a security key change due to a change of the termination point. + +**Table A-1: L2 handling for bearer type change with and without a security key change due to a change of the termination point.** + +| Bearer type change from row to col | MCG | | Split | | SCG | | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| | no change of termination point (no key change) | change of termination point (key change) | no change of termination point (no key change) | change of termination point (key change) | no change of termination point (no key change) | change of termination point (key change) | +| MCG | N/A | PDCP:
Re-establish
MCG RLC:
See Note 1
MCG MAC:
See Note 1
SCG RLC:
No action
SCG MAC:
No action | PDCP:
Reconfigure
MCG RLC:
No action
MCG MAC:
No action
SCG RLC:
Establish
SCG MAC:
Reconfigure | PDCP:
Re-establish
MCG RLC:
See Note 1
MCG MAC:
See Note 1
SCG RLC:
Establish
SCG MAC:
Reconfigure | PDCP:
Recovery
MCG RLC:
See Note 3
MCG MAC:
Reconfigure
SCG RLC:
Establish
SCG MAC:
Reconfigure | PDCP:
Re-establish
MCG RLC:
See Note 3
MCG MAC:
Reconfigure
SCG RLC:
Establish
SCG MAC:
Reconfigure | +| Split | PDCP:
Recovery
MCG RLC:
No action
MCG MAC:
No action
SCG RLC:
See Note 4
SCG MAC:
Reconfigure | PDCP:
Re-establish
MCG RLC:
See Note 1
MCG MAC:
See Note 1
SCG RLC:
See Note 4
SCG MAC:
Reconfigure | N/A | PDCP:
Re-establish
MCG RLC:
See Note 1
MCG MAC:
See Note 1
SCG RLC:
See Note 1
SCG MAC:
See Note 1 | PDCP:
Recovery
MCG RLC:
See Note 3
MCG MAC:
Reconfigure
SCG RLC:
No action
SCG MAC:
No action | PDCP:
Re-establish
MCG RLC:
See Note 3
MCG MAC:
Reconfigure
SCG RLC:
See Note 1
SCG MAC:
See Note 1 | +| SCG | PDCP:
Recovery
MCG RLC:
Establish
MCG MAC:
Reconfigure
SCG RLC:
See Note 4
SCG MAC:
Reconfigure | PDCP:
Re-establish
MCG RLC:
Establish
MCG MAC:
Reconfigure
SCG RLC:
See Note 4
SCG MAC:
Reconfigure | PDCP:
Reconfigure
MCG RLC:
Establish
MCG MAC:
Reconfigure
SCG RLC:
No action
SCG MAC:
No action | PDCP:
Re-establish
MCG RLC:
Establish
MCG MAC:
Reconfigure
SCG RLC:
See Note 1
SCG MAC:
See Note 1 | N/A | PDCP:
Re-establish
MCG RLC:
No action
MCG MAC:
No action
SCG RLC:
See Note 1
SCG MAC:
See Note 1 | + +NOTE 1: For EN-DC and NGEN-DC MCG, NE-DC SCG: the MAC/RLC behaviour depends on the solution selected by the network. It can be PCell handover (for EN-DC and NGEN-DC) or PSCell change (for NE-DC), which triggers MAC reset and RLC re-establishment. Alternatively, the logical channel identity can be changed, either via RLC bearer release and add for the same DRB (including RLC re-establishment), or via reconfiguration of the RLC bearer with RLC-re-establishment. + +For EN-DC and NGEN-DC SCG, NE-DC MCG, NR-DC MCG and SCG: the MAC/RLC behaviour depends on the solution selected by the network. It can be reconfiguration with sync, with MAC reset and RLC re-establishment. Alternatively, the logical channel identity can be changed via RLC bearer release and add. + +NOTE 2: Void + +NOTE 3: For EN-DC and NGEN-DC: Re-establishment and release. For NE-DC and NR-DC: Release. + +NOTE 4: For NE-DC: Re-establishment and release. For EN-DC, NGEN-DC and NR-DC: Release. + +# Annex B (informative): Handover Scenarios + +## Supported MR-DC + +Table B-1 summarizes the supported handover scenarios involving MR-DC configurations. + +**Table B-1: Supported MR-DC handover scenarios.** + +| To (column)
HO from (row) | E-UTRA with EPC | E-UTRA with 5GC | NR | GERAN or UTRAN | EN-DC | NGEN-DC | NE-DC | NR-DC | +|------------------------------|-----------------|-----------------|-----|----------------|-------|---------|-------|-------| +| E-UTRA with EPC | YES | YES | YES | YES | YES | NO | NO | NO | +| E-UTRA with 5GC | YES | YES | YES | NO | NO | YES | NO | NO | +| NR | YES | YES | YES | NOTE 1 | YES | NO | YES | YES | +| GERAN or UTRAN | YES | NO | NO | YES | NO | NO | NO | NO | +| EN-DC | YES | YES | YES | YES | YES | NO | NO | NO | +| NGEN-DC | YES | YES | YES | NO | NO | YES | NO | NO | +| NE-DC | YES | YES | YES | NOTE 1 | NO | NO | YES | NO | +| NR-DC | YES | YES | YES | NOTE 1 | NO | NO | NO | YES | + +NOTE 1: Only SRVCC handover of IMS voice bearer to UTRAN is supported. + +NOTE 2: All handover scenarios according to Table B-1 that have a DC option in the column "from" are supported during fast MCG failure recovery. + +NOTE 3: Only intra-RAT conditional handover is supported except for E-UTRA with 5GC scenario. + +NOTE 4: DAPS handover is only supported from E-UTRA with EPC to E-UTRA with EPC and from NR to NR. + +# Annex C (informative): Change history + +| Change history | | | | | | | | | +|----------------|----------------------|------------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | Tdoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2017.04 | RAN2#9
7bis | R2-1703828 | - | - | - | Draft Skeleton | | 0.0.1 | +| 2017.04 | RAN2#9
7bis | R2-1703923 | - | - | - | Endorsed Skeleton | | 0.0.2 | +| 2017.05 | RAN2#9
8 | R2-1704898 | - | - | - | Initial version, including:
Agreements from TR38.912
Agreements from RAN2#97bis on:
- System information handling
- Measurements
- UE capability coordination
- Handling of combined MN/SN RRC messages
- SCG SRB
- MCG split SRB
- SN/MN Failure handling
- QoS aspects
- Bearer type configuration
- Security aspects | | 0.1.0 | +| 2017.06 | RAN2
NR
AdHoc2 | R2-1706418 | - | - | - | Agreements from RAN3#96 on:
- Network interfaces
- Initial EN-DC operation related aspects
- UP related aspects
Agreements from RAN2#98 on:
- Measurement coordination
- UE capability coordination
- SCG SRB
Further RAN2 agreements on EN-DC operation related aspects | | 0.1.1 | +| 2017.06 | RAN2
NR
AdHoc2 | R2-1707467 | - | - | - | Endorsed version at RAN2 NR AH2, also including:
Initial description of procedures for MR-DC with 5GC
Correction to SN initiated SN change procedure for EN-DC | | 0.2.0 | +| 2017.08 | RAN2#9
9 | R2-1708080 | - | - | - | Agreements from RAN3 NR AH2 on:
- Data forwarding for SCG split bearer
- Path Update procedure
Agreements from RAN2 NR AH2 on:
- Bearer type harmonization / bearer type change
- UE capability coordination
- SRB3 (SCG SRB)
- MCG Split SRB
- SN failure handling
- Security handling
- SN Addition procedure
- MN initiated SN Modification/Release procedures
Miscellaneous corrections | | 0.2.1 | +| 2017.08 | RAN2#9
9 | R2-1709831 | - | - | - | Endorsed version at RAN2#99 | | 0.3.0 | +| 2017.08 | RAN2#9
9 | R2-1709939 | - | - | - | Agreements from RAN2#99 on:
- Bearer type harmonization / bearer type change
- SN failure handling
- Measurement result exchange
- Security aspects
- Embedded RRC transport
- Other MR-DC procedures related aspects
RAN3 endorsed TPs on miscellaneous corrections to MR-DC procedures (in R3-173187, R3-173380, R3-173381, R3-173384, R3-173386, R3-173388 and R3-173390), | | 0.4.0 | +| 2017.09 | RAN#77 | RP-171872 | - | - | - | Provided for information to RAN | | 1.0.0 | +| 2017.09 | RAN#77 | RP-172036 | - | - | - | Correction of some auto-formatting issues | | 1.0.1 | +| 2017.09 | RAN2#9
9bis | R2-1711526 | - | - | - | Alignment to the agreed terminology for the different nodes:
- introduction of the en-gNB term
- replacement of MeNB and SgNB with MN and SN
Clarification on UE capabilities coordination
Clarification in Figure 4.2.2-2 that there is one SDAP entity per cell group | | 1.0.2 | +| 2017.10 | RAN2#9
9bis | R2-1711937 | - | - | - | Endorsed version at RAN2#99bis | | 1.1.0 | +| 2017.10 | RAN2#9 | R2-1712072 | - | - | - | Agreements from RAN2#99bis on: | | 1.1.1 | + +| | | | | | | | | +|---------|----------|------------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | 9bis | | | | | - Bearer type harmonization / bearer type change
- SCG change and Pscell change
- MN/SN measurement coordination
- UE capabilities coordination
- MR-DC procedures related aspects
- Security aspects
Agreed Text Proposals in:
- R2-1711929 TP on SN modification without MN involvement
- R2-1711942 TP on inter-MN HO with SN change
Agreements from RAN3#97bis in R3-174254, collecting changes from:
- R3-174214 Text Proposal for QoS Handling in 5GC DC
- R3-174132 Completion of the RRC tunnelling in MR-DC
- R3-174136 Stage 2 TP on bearer type change without MAC reset
- R3-174221 TP for Supporting MN Initiate SN Change
- R3-174194 UE-AMBR enforcement
- R3-174234 Secondary RAT data volume reporting
- R3-174160 MN and SN role for QoS flow to DRB mapping
- R3-174101 Clean-up of 37.340 RAN3 Related Part | | +| 2017.11 | RAN2#100 | R2-1712301 | - | - | - | Clean version | 1.2.0 | +| 2017.11 | RAN2#100 | R2-1712302 | - | - | - | MR-DC related agreements moved from TS 38.300:
- on two C-RNTIs independently allocated at the UE
- on RLF declared separately for the MCG and for the SCG
- on roaming and access restrictions for MR-DC with 5GC
- on SPS and BSR configuration, triggering and reporting
Addition of a note on support of ideal backhaul.
Clarification on use of SRB3.
Clarification on security key handling.
Editorial corrections in various Figures
Removal of FFSs for MR-DC with 5GC (moved to a separate list) | 1.2.1 | +| 2017.12 | RAN2#100 | R2-1714080 | - | - | - | Agreed Text Proposals in:
- R2-1713141 TP on 37.340
- R2-1713838 Bearer type change with PDPC version change
- R2-1714176 PSCell change clarification and SCG Change removal
- R2-1714183 Stage 2 TP to update bearer type description
- R2-1714237 Clarification for the MR-DC QoS framework
- R3-174308 Cleanup of reference/definitions for 37.340
- R3-174565 TP for SCG Change related to Bearer Type Change
- R3-174661 TP for querying SCGconfig for MN to eNB/gNB Change
- R3-174763 TP for a unified 5G User Plane protocol
- R3-174876 Further Clean-up of TS37.340 RAN3 Related Part
- R3-174913 Clarifications on Inter-MN handover with SN change
- R3-174916 Clarification on the interface between gNB for Option 3
- R3-174917 Tunnel ID switching in case of reconfiguration
- R3-174921 Introducing bearer harmonization – RAN3 parts
- R3-174923 On security related IE in MN initiated SN modification
- R3-174928 TP on UE-AMBR for EN-DC
- R3-174930 Stage 2 for secondary RAT data volume reporting
- R3-175009 Removing data forwarding from corresponding node
- R3-175048 Stage 2 TP for bearer type change
- R3-174975 Race conditions in case of SN release Other miscellaneous agreements from RAN2#100 | 1.2.2 | +| 2017.12 | RAN2#100 | R2-1714251 | - | - | - | RAN2 agreed version | 1.3.0 | +| 2017.12 | RP-78 | RP-172464 | - | - | - | Provided for approval to RAN | 2.0.0 | +| 2017/12 | RP-78 | | | | | Upgraded to Rel-15 | 15.0.0 | +| 2018/03 | RP-79 | RP-180440 | 0004 | 1 | F | Miscellaneous corrections | 15.1.0 | +| | RP-79 | RP-180440 | 0008 | 1 | F | Baseline CR for TS 37.340 (RAN3 part) covering agreements of RAN3 #NR adhoc 1801 and RAN3 #99 | 15.1.0 | +| 2018/06 | RP-80 | RP-181214 | 0012 | 2 | F | Further miscellaneous corrections | 15.2.0 | +| | RP-80 | RP-181214 | 0014 | 1 | F | CR on EN-DC bearer type changes in TS 37.340 | 15.2.0 | +| | RP-80 | RP-181214 | 0015 | 1 | F | CR on EN-DC reconfiguration procedure via SRB3 in TS 37.340 | 15.2.0 | +| | RP-80 | RP-181214 | 0017 | - | F | Radio Protocol Architecture figure clarification with SDAP | 15.2.0 | +| | RP-80 | RP-181215 | 0018 | 1 | F | Stage 2 CR on combined bearer type and termination point change | 15.2.0 | +| | RP-80 | RP-181215 | 0021 | 1 | F | Correction to TS 37.340 on PDCP version for SRB | 15.2.0 | +| | RP-80 | RP-181215 | 0024 | 1 | F | L2 handling for bearer type change when PDCP SN length changed | 15.2.0 | +| | RP-80 | RP-181215 | 0025 | 1 | F | Correction on SN configured NR measurements after SCG failure | 15.2.0 | +| | RP-80 | RP-181215 | 0026 | 1 | F | Clarification of the usage of SN Status Transfer | 15.2.0 | +| | RP-80 | RP-181215 | 0027 | - | F | Addition of the full config indicator in SN Change | 15.2.0 | +| | RP-80 | RP-181216 | 0028 | 2 | F | Coordination of Inactivity for EN-DC | 15.2.0 | +| | RP-80 | RP-181216 | 0029 | - | F | CR on maintaining the bearer type on wrap-around for TS37.340 | 15.2.0 | +| | RP-80 | RP-181216 | 0030 | 2 | F | Enabling re-use of NR PCIs in cells served by the same SN in EN-DC | 15.2.0 | +| 2018/09 | RP-81 | RP-181939 | 0037 | 2 | F | Clarification on number of CC for NR CA | 15.3.0 | +| | RP-81 | RP-181942 | 0039 | 2 | F | CR for 37.340 for CA duplication of LTE bearer | 15.3.0 | +| | RP-81 | RP-181942 | 0042 | - | F | Capturing the agreement related to Count wrap around handling for | 15.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------|--------| +| | | | | | | split bearer type | | +| | RP-81 | RP-181941 | 0043 | 1 | F | Miscellaneous clarifications | 15.3.0 | +| | RP-81 | RP-181941 | 0044 | 1 | F | Inclusion of measurement gap related agreements | 15.3.0 | +| | RP-81 | RP-181942 | 0046 | 2 | F | Small correction about bear type change | 15.3.0 | +| | RP-81 | RP-181942 | 0047 | 3 | F | CR to 37.340 on the Layer 2 handling for bearer type change | 15.3.0 | +| | RP-81 | RP-181939 | 0048 | - | F | CR on the support of RLC mode reconfiguration | 15.3.0 | +| | RP-81 | RP-181939 | 0051 | - | F | Corrections on 37.340 for bearer type change support | 15.3.0 | +| | RP-81 | RP-181941 | 0054 | 1 | F | NR Corrections (37.340 Baseline CR covering RAN3-101 agreements) | 15.3.0 | +| 2018/12 | RP-82 | RP-182650 | 0067 | 1 | F | Split SRB UL configuration | 15.4.0 | +| | RP-82 | RP-182656 | 0071 | 1 | F | Miscellaneous clarifications | 15.4.0 | +| | RP-82 | RP-182669 | 0073 | 4 | B | Agreements for MR-DC | 15.4.0 | +| | RP-82 | RP-182651 | 0079 | - | F | Correction for SN terminated MCG bearer | 15.4.0 | +| | RP-82 | RP-182667 | 0082 | 3 | F | Updates to UE capability coordination for MR-DC | 15.4.0 | +| | RP-82 | RP-182664 | 0084 | 2 | F | Corrections on RRC transfer procedure in EN-DC | 15.4.0 | +| | RP-82 | RP-182666 | 0085 | 3 | F | Correction of SN Initiated SN Modification procedure for Measurement Gap | 15.4.0 | +| | RP-82 | RP-182660 | 0086 | 1 | F | Stage 2 CR on Measurement gap configuration scenarios | 15.4.0 | +| | RP-82 | RP-182669 | 0092 | 1 | B | Baseline CR for TS37.340 | 15.4.0 | +| 2019/03 | RP-83 | RP-190543 | 0090 | 3 | F | Corrections for MR-DC procedures | 15.5.0 | +| | RP-83 | RP-190543 | 0096 | 2 | F | QoS flow offloading for MR-DC | 15.5.0 | +| | RP-83 | RP-190540 | 0098 | 1 | F | Introduction of IDC mechanism for EN-DC operation | 15.5.0 | +| | RP-83 | RP-190543 | 0104 | 1 | F | Correction on UP integrity protection in late drop | 15.5.0 | +| | RP-83 | RP-190543 | 0106 | 1 | F | Corrections to SN Modification Request in MR-DC | 15.5.0 | +| | RP-83 | RP-190553 | 0107 | - | F | PSCell information for LI purposes | 15.5.0 | +| | RP-83 | RP-190544 | 0108 | - | F | Correction of EN DC data volume reporting and relocation | 15.5.0 | +| | RP-83 | RP-190544 | 0110 | - | F | Data volume reporting for MR-DC with 5GC | 15.5.0 | +| | RP-83 | RP-190544 | 0111 | - | F | Correction of RAN triggered PDU session split | 15.5.0 | +| | RP-83 | RP-190544 | 0112 | - | F | Correction of PDU session split at handover | 15.5.0 | +| | RP-83 | RP-190544 | 0113 | - | F | TEID change in case of key change | 15.5.0 | +| | RP-83 | RP-190545 | 0114 | 1 | F | Support of PDU session split during inter-MN handover for MR-DC with 5GC | 15.5.0 | +| 2019/06 | RP-84 | RP-191375 | 0116 | 1 | F | MN-SN coordination for ANR in MR-DC | 15.6.0 | +| | RP-84 | RP-191378 | 0118 | 3 | F | CR on 37.340 for s-Measure in NR-DC and NE-DC | 15.6.0 | +| | RP-84 | RP-191374 | 0120 | - | F | Clarification on RLC bearer release and add | 15.6.0 | +| | RP-84 | RP-191374 | 0122 | - | F | Activation/deactivation of SCells in MR-DC | 15.6.0 | +| | RP-84 | RP-191374 | 0123 | - | F | Corrections on MN and SN inter-node resource coordination | 15.6.0 | +| | RP-84 | RP-191376 | 0124 | 1 | F | Measurement gap coordination in MR-DC | 15.6.0 | +| | RP-84 | RP-191379 | 0125 | 2 | F | Inter-RAT HO support | 15.6.0 | +| | RP-84 | RP-191376 | 0126 | 1 | F | Editorial clean-up | 15.6.0 | +| | RP-84 | RP-191379 | 0133 | - | F | Various Clean-ups for TS37.340 | 15.6.0 | +| | RP-84 | RP-191380 | 0134 | - | F | Correction of RAN triggered PDU session split | 15.6.0 | +| | RP-84 | RP-191381 | 0135 | 1 | F | Allow MN to retrieve forwarding proposal from the source SN | 15.6.0 | +| | RP-84 | RP-191380 | 0136 | - | F | RAN paging failure handling in SN | 15.6.0 | +| | RP-84 | RP-191380 | 0137 | - | F | Rapporteur Clean-ups of Secondary RAT Data Volume Report | 15.6.0 | +| | RP-84 | RP-191380 | 0138 | - | F | Correction of the references to the GTP tunnel endpoint information | 15.6.0 | +| | RP-84 | RP-191380 | 0139 | - | F | In-order delivery when QoS flows offloaded from SN | 15.6.0 | +| | RP-84 | RP-191380 | 0140 | - | F | RAN sharing with multiple Cell ID broadcast | 15.6.0 | +| 2019/09 | RP-85 | RP-192191 | 0141 | 1 | F | PDCP configuration generation | 15.7.0 | +| | RP-85 | RP-192190 | 0142 | 1 | F | Clarification on selectedBandCombination | 15.7.0 | +| | RP-85 | RP-192194 | 0143 | 3 | F | Clarification about PSCell change between different SN nodes | 15.7.0 | +| | RP-85 | RP-192193 | 0144 | 2 | F | Clarification of handover terminology | 15.7.0 | +| | RP-85 | RP-192191 | 0145 | 1 | F | Default DRB handling | 15.7.0 | +| | RP-85 | RP-192192 | 0148 | 1 | F | Capability report and coordination in NR-DC | 15.7.0 | +| | RP-85 | RP-192191 | 0151 | 1 | F | LTE to NR-DC Inter-RAT HO support | 15.7.0 | +| | RP-85 | RP-192190 | 0153 | - | F | Correction of E-RAB Modification Indication | 15.7.0 | +| | RP-85 | RP-192191 | 0154 | 1 | F | TS37.340 Rapporteur Cleanups | 15.7.0 | +| 2019/12 | RP-86 | RP-192934 | 0155 | 2 | F | PDCP version in EN-DC | 15.8.0 | +| | RP-86 | RP-192936 | 0157 | 3 | F | SMTC setting for NR PSCell change in MR-DC | 15.8.0 | +| | RP-86 | RP-192937 | 0158 | 3 | F | PDCP configuration generation (email discussion of 107#25) | 15.8.0 | +| | RP-86 | RP-192936 | 0159 | 3 | F | Correction on sending Failure Information via SRB3 | 15.8.0 | +| | RP-86 | RP-192938 | 0160 | 2 | F | Clarification of NR-DC synchronization | 15.8.0 | +| | RP-86 | RP-192938 | 0163 | 2 | F | Clarification on security key change and bearer termination point change | 15.8.0 | +| | RP-86 | RP-192936 | 0168 | 1 | F | Clarification regarding QoS handling in MRDC with 5G CN | 15.8.0 | +| | RP-86 | RP-192936 | 0169 | 1 | F | Missing RACH aspect for DC | 15.8.0 | +| | RP-86 | RP-192937 | 0170 | - | F | IP version on X2-U | 15.8.0 | +| | RP-86 | RP-192937 | 0171 | - | F | Correction to MR-DC with 5GC with RRC_INACTIVE | 15.8.0 | +| | RP-86 | RP-192938 | 0172 | - | F | Correction of SN Status Transfer during HO with DC | 15.8.0 | +| | RP-86 | RP-192938 | 0174 | 1 | F | DRB ID co-ordination between MN and SN | 15.8.0 | +| | RP-86 | RP-192938 | 0175 | - | F | Correcting misbehaviors and clean-ups on 37.340 related to PDU session split | 15.8.0 | +| | RP-86 | RP-192938 | 0177 | - | F | Stage2 Clarifications for RRC_Inactive with MR-DC@5GC | 15.8.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------|--------| +| | RP-86 | RP-192938 | 0178 | - | F | Correction of NG connection in MR DC | 15.8.0 | +| | RP-86 | RP-192938 | 0179 | - | F | Correcting misbehaviors and clean-ups on 37.340 related to data forwarding and SN status transfer | 15.8.0 | +| | RP-86 | RP-192945 | 0173 | 1 | B | Stage2 Introduction of ARPI&SPID for EN-DC | 16.0.0 | +| | RP-86 | RP-192943 | 0176 | 1 | B | Resuming SCG in RRC Resume | 16.0.0 | +| | RP-86 | RP-192943 | 0180 | 1 | F | Clarification on the offered non-GBR resources | 16.0.0 | +| 2020/03 | RP-87 | RP-200350 | 0165 | 3 | B | Introduction of SRVCC from 5G to 3G | 16.1.0 | +| | RP-87 | RP-200340 | 0182 | 1 | B | Introduction of cross link interference management | 16.1.0 | +| | RP-87 | RP-200341 | 0183 | 2 | B | Introduction of NR-U to 37.340 | 16.1.0 | +| | RP-87 | RP-200344 | 0184 | 2 | B | CR for supporting UE Power Saving in TS 37.340 | 16.1.0 | +| | RP-87 | RP-200357 | 0185 | - | B | Stage 2 CR for Inter-RAT HO between NR to EN-DC in Rel-16 | 16.1.0 | +| | RP-87 | RP-200349 | 0186 | 2 | B | Correction of TS 37.340 on the support of MR-DC for IAB | 16.1.0 | +| | RP-87 | RP-200346 | 0187 | - | B | Introduction of 5G V2X with NR Sidelink | 16.1.0 | +| | RP-87 | RP-200348 | 0188 | - | B | Introduction of CA/DC enhancements to 37.340 | 16.1.0 | +| 2020/07 | RP-88 | RP-201174 | 0189 | 4 | F | SRB3 for reporting UAI for power saving | 16.2.0 | +| | RP-88 | RP-201179 | 0192 | 3 | F | Miscellaneous correction to 37.340 for IAB | 16.2.0 | +| | RP-88 | RP-201160 | 0194 | 2 | A | Correction on MN-SN measurements coordination in INM | 16.2.0 | +| | RP-88 | RP-201181 | 0195 | 3 | B | Introduction of IIOT features to TS 37.340 | 16.2.0 | +| | RP-88 | RP-201166 | 0198 | 2 | F | Clarification on PDCP version change | 16.2.0 | +| | RP-88 | RP-201162 | 0205 | 1 | A | Corrections to MAC description | 16.2.0 | +| | RP-88 | RP-201191 | 0208 | 1 | F | Correction on MN-SN measurements coordination in INM | 16.2.0 | +| | RP-88 | RP-201178 | 0209 | - | F | DCCA corrections | 16.2.0 | +| | RP-88 | RP-201177 | 0210 | - | B | Introduction of Conditional PSCell Change for intra-SN without MN involvement | 16.2.0 | +| | RP-88 | RP-201178 | 0211 | - | B | Support of inter-RAT handover in response to MCGFailureInformation | 16.2.0 | +| | RP-88 | RP-201177 | 0212 | 1 | B | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | 16.2.0 | +| | RP-88 | RP-201180 | 0213 | - | B | Supporting of RACS for EN-DC and MR-DC | 16.2.0 | +| | RP-88 | RP-201212 | 0214 | - | C | Introduction of Inter-gNB CSI-RS Based Mobility | 16.2.0 | +| | RP-88 | RP-201296 | 0216 | 1 | A | Support of SN not broadcasting system information | 16.2.0 | +| 2020/09 | RP-89 | RP-201930 | 0218 | - | F | Minor Correction for CPC Configuration Related Procedure | 16.3.0 | +| | RP-89 | RP-201932 | 0222 | 1 | F | Mandatory support of full rate user plane integrity protection in MR-DC | 16.3.0 | +| | RP-89 | RP-201930 | 0223 | 1 | F | Correction of signalling flow for CPC | 16.3.0 | +| | RP-89 | RP-201924 | 0225 | 1 | F | Miscellaneous correction for TS 37.340 for IAB | 16.3.0 | +| | RP-89 | RP-201922 | 0227 | - | F | Miscellaneous corrections for DCCA | 16.3.0 | +| | RP-89 | RP-201933 | 0228 | - | F | Inter-system direct forwarding with shared en-gNB/gNB | 16.3.0 | +| | RP-89 | RP-201938 | 0230 | 1 | F | Further correction for CA-based PDCP duplication for Industrial IoT | 16.3.0 | +| | RP-89 | RP-201931 | 0231 | 1 | F | Introducing UE Radio Capability Mapping procedure for EN-DC | 16.3.0 | +| 2020-12 | RP-90 | RP-202774 | 0220 | 2 | F | Corrections to CPC with and without SRB3 involved | 16.4.0 | +| | RP-90 | RP-202790 | 0233 | 1 | A | UE Capabilities description | 16.4.0 | +| | RP-90 | RP-202772 | 0234 | - | F | CR to 37.340 on SRB3 description | 16.4.0 | +| | RP-90 | RP-202770 | 0235 | 1 | B | CR for 37.340 on power control for NR_DC | 16.4.0 | +| | RP-90 | RP-202774 | 0236 | 1 | F | Miscellaneous corrections for Mobility Enhancements | 16.4.0 | +| | RP-90 | RP-202777 | 0238 | - | F | Clarification for secondary DRX | 16.4.0 | +| | RP-90 | RP-202777 | 0239 | - | F | Full rate UP IP correction | 16.4.0 | +| | RP-90 | RP-202790 | 0241 | 1 | A | End marker handling in case of MR-DC NG-RAN initiated QoS Flow offloading | 16.4.0 | +| | RP-90 | RP-202769 | 0242 | - | F | Corrections on AQP for notification control | 16.4.0 | +| 2021-03 | RP-91 | RP-210701 | 0244 | - | A | Correction on the PDCP Change Indication for 37.340 | 16.5.0 | +| | RP-91 | RP-210689 | 0245 | 1 | F | CR on co-configuration of sidelink and MR-DC | 16.5.0 | +| | RP-91 | RP-210690 | 0246 | 1 | F | CR on support of NR-DC within the same gNB-DU | 16.5.0 | +| | RP-91 | RP-210703 | 0248 | 1 | F | Corrections on UL power sharing | 16.5.0 | +| | RP-91 | RP-210702 | 0249 | 1 | A | Correction on user plane handling for full configuration in SN Change | 16.5.0 | +| | RP-91 | RP-210698 | 0251 | - | F | Non-support of CHO/CPC with LTE/5GC | 16.5.0 | +| | RP-91 | RP-210701 | 0254 | - | A | Correction of DL End Markers and QoS Flow Mobility | 16.5.0 | +| 2021-06 | RP-92 | RP-211483 | 0256 | 1 | A | CR on MN and SN configuration restriction coordination | 16.6.0 | +| | RP-92 | RP-211471 | 0257 | 2 | F | CR on SCG suspend in EN-DC | 16.6.0 | +| | RP-92 | RP-211472 | 0258 | 1 | F | Clarification on IP packet type in DedicatedInfoF1c | 16.6.0 | +| | RP-92 | RP-211471 | 0261 | 3 | F | Miscellaneous corrections on DCCA, 2-step RACH, IIOT | 16.6.0 | +| | RP-92 | RP-211473 | 0262 | 2 | F | Miscellaneous corrections to 37.340 on mobility enhancement | 16.6.0 | +| | RP-92 | RP-211482 | 0264 | 1 | A | CR on SCG release in EN-DC | 16.6.0 | +| | RP-92 | RP-211485 | 0272 | - | A | Correction on PSCell change without security key change and data forwarding upon SN change with full configuration | 16.6.0 | +| | RP-92 | RP-211486 | 0274 | - | A | Clarification on RRC full config for PSCell change | 16.6.0 | +| | RP-92 | RP-211473 | 0275 | - | F | 37.340 correction for CHO early data forwarding in MN to eNB/gNB Change scenario | 16.6.0 | +| | RP-92 | RP-211480 | 0276 | - | F | Addition of sidelink MR-DC resource coordination | 16.6.0 | +| | RP-92 | RP-211484 | 0278 | - | A | No partial success in the SN initiated SN Modification procedure for EN-DC | 16.6.0 | +| | RP-92 | RP-211484 | 0280 | - | A | R16CR37.340 for SCG release | 16.6.0 | +| 2021-09 | RP-93 | RP-212438 | 0266 | 2 | A | Clarification on RACH procedure for HO with PSCell | 16.7.0 | +| | RP-93 | RP-212438 | 0285 | - | A | Clean-up on Xn-U Address Indication procedure | 16.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------|--------| +| 2021-12 | RP-94 | RP-213341 | 0288 | - | F | Corrections on SCG/MCG failure handling | 16.8.0 | +| | RP-94 | RP-213341 | 0291 | - | A | Clarification for SgNB trigger SCG release in Rel-16 in TS 37.340 | 16.8.0 | +| | RP-94 | RP-213341 | 0292 | - | F | Correction on SN-initiated SN Release | 16.8.0 | +| 2022-03 | RP-95 | RP-220472 | 0300 | 1 | A | Clarification on inter-MN handover without SN change | 16.9.0 | +| | RP-95 | RP-220835 | 0303 | 1 | F | CR on data forwarding between EN-DC/MR-DC and SA handover | 16.9.0 | +| 2022-03 | RP-95 | RP-220495 | 0294 | 1 | B | Introducing support of UP IP for EPC connected architectures using NR PDC | 17.0.0 | +| | RP-95 | RP-220486 | 0296 | 1 | B | Introduction of CP-UP separation support in NR eIAB | 17.0.0 | +| | RP-95 | RP-220489 | 0298 | - | B | Introduction of the support for UDC in NR | 17.0.0 | +| | RP-95 | RP-220510 | 0301 | - | B | Inter-MN RRC Resume without SN change [InterMNResume] | 17.0.0 | +| | RP-95 | RP-220510 | 0302 | 1 | C | On UE security capability to address SA3 request [UE_Sec_Caps] | 17.0.0 | +| | RP-95 | RP-220510 | 0304 | - | F | Support of CHO with SCG configuration[CHOWithDCkept] | 17.0.0 | +| | RP-95 | RP-220490 | 0306 | - | B | Enhancement of RAN Slicing | 17.0.0 | +| | RP-95 | RP-220839 | 0308 | - | B | Addition of SON features enhancement | 17.0.0 | +| | RP-95 | RP-220485 | 0309 | - | B | Introduction of further multi-RAT dual-connectivity enhancements | 17.0.0 | +| 2022-06 | RP-96 | RP-221728 | 0310 | 3 | F | Corrections on TS 37.340 for DCCA enhancement | 17.1.0 | +| | RP-96 | RP-221718 | 0313 | 2 | F | Miscellaneous Corrections to 37.340 | 17.1.0 | +| | RP-96 | RP-221712 | 0324 | 1 | A | Correction for SCell activation | 17.1.0 | +| | RP-96 | RP-221714 | 0326 | 2 | F | Rapporteur Clean-up | 17.1.0 | +| | RP-96 | RP-221713 | 0328 | 1 | A | Support of 1Tx-2Tx UL Tx switching for EN-DC | 17.1.0 | +| | RP-96 | RP-221736 | 0329 | - | C | Support of CHO with SCG configuration - 37340 [CHOWithDCkept] | 17.1.0 | +| | RP-96 | RP-221733 | 0330 | - | F | Correction on MRO for SN Change Failure | 17.1.0 | +| | RP-96 | RP-221728 | 0331 | 2 | F | Stage-2 aspects for CPAC | 17.1.0 | +| | RP-96 | RP-221733 | 0332 | - | F | Corrections to UE History Information in MR-DC | 17.1.0 | +| | RP-96 | RP-221727 | 0333 | 1 | F | Introduction of UE power saving enhancements In 37.340 | 17.1.0 | +| 2022-09 | RP-97 | RP-222522 | 0340 | 2 | F | Corrections for DCCA enhancement | 17.2.0 | +| | RP-97 | RP-222521 | 0342 | 1 | A | Rapporteur Clean-up | 17.2.0 | +| | RP-97 | RP-222523 | 0343 | 1 | F | Miscellaneous Corrections to 37.340 | 17.2.0 | +| | RP-97 | RP-222522 | 0346 | - | F | Clarification on direct data forwarding for MN initiated CPC to TS37340 | 17.2.0 | +| | RP-97 | RP-222522 | 0347 | - | F | Coordination of CHO and intra-SN SCG reconfiguration | 17.2.0 | +| 2022-12 | RP-98 | RP-223414 | 0350 | 4 | F | Corrections for DCCA enhancement | 17.3.0 | +| | RP-98 | RP-223412 | 0351 | 1 | F | Correction on Sidelink based U2N Relay | 17.3.0 | +| | RP-98 | RP-223413 | 0353 | 1 | F | Miscellaneous corrections on TS 37.340 for ePowSav | 17.3.0 | +| | RP-98 | RP-223410 | 0356 | - | F | Failure handling for SCG MRO | 17.3.0 | +| | RP-98 | RP-223410 | 0357 | - | F | Correction for TS 37.340 on UHI in MR-DC | 17.3.0 | +| | RP-98 | RP-223409 | 0358 | 1 | F | Interaction between CPC Cancel and SN Release | 17.3.0 | +| | RP-98 | RP-223409 | 0359 | - | F | Clarification on direct data forwarding for SN initiated CPC to TS37.340 | 17.3.0 | +| 2023-03 | RP-99 | RP-230688 | 0361 | 1 | F | Corrections for DCCA enhancement | 17.4.0 | +| | RP-99 | RP-230688 | 0362 | - | F | Xn-U Address Information delivery in CPAC | 17.4.0 | +| | RP-99 | RP-230688 | 0363 | - | F | PDCP PDU early transmission in CPAC | 17.4.0 | +| | RP-99 | RP-230687 | 0364 | 2 | F | Correction to the description of the CHO | 17.4.0 | +| | RP-99 | RP-230688 | 0365 | 1 | F | Clarifications on prepared PSCell addition by candidate SN in CPC-A | 17.4.0 | +| | RP-99 | RP-230688 | 0366 | - | F | Correction on SCG reconfiguration when MN initiated conditional reconfiguration is prepared | 17.4.0 | +| 2023-06 | RP-100 | RP-231412 | 0368 | - | F | Modify the figures for MN/SN initiated CPC and CHO with SCG | 17.5.0 | +| 2023-09 | RP-101 | RP-232565 | 0370 | - | A | Correction on mobility restriction list for MR-DC with 5GC | 17.6.0 | +| 2023-12 | RP-102 | RP-233887 | 0376 | - | F | Correction of CPAC to clarify optional late data forwarding | 17.7.0 | +| 2023-12 | RP-102 | RP-233905 | 0367 | 2 | B | Introduction of In-Device Co-existence (IDC) Enhancements for NR | 18.0.0 | +| | RP-102 | RP-233901 | 0371 | 1 | B | Introduction of R18 positioning to MR-DC | 18.0.0 | +| | RP-102 | RP-233910 | 0372 | 2 | B | Introduction of QoE enhancement for NR-DC | 18.0.0 | +| | RP-102 | RP-233903 | 0373 | 3 | B | Introduction of DualTxRx MUSIM | 18.0.0 | +| | RP-102 | RP-233930 | 0375 | - | B | Introduction of NR further mobility enhancements in TS 37.340 | 18.0.0 | +| | RP-102 | RP-233909 | 0377 | - | B | Addition of SON Rel.18 features | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37355/raw.md b/marked/Rel-18/37_series/37355/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..88e23ff15b828e4ca62afa50cc2258deda4c65c8 --- /dev/null +++ b/marked/Rel-18/37_series/37355/raw.md @@ -0,0 +1,20514 @@ + + +# 3GPP TS 37.355 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; LTE Positioning Protocol (LPP) (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. The "3" is stylized with a red signal wave icon at its base. A small "TM" trademark symbol is located to the upper right of the "P". + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. + +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices + +--- + +# **3GPP** + +Postal address + +3GPP support office address +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + +# Contents + +| | | +|---------------------------------------------------------------------|----| +| Foreword..... | 13 | +| 1 Scope..... | 14 | +| 2 References..... | 14 | +| 3 Definitions and Abbreviations..... | 16 | +| 3.1 Definitions..... | 16 | +| 3.2 Abbreviations..... | 17 | +| 4 Functionality of Protocol..... | 20 | +| 4.1 General..... | 20 | +| 4.1.1 LPP Configuration..... | 20 | +| 4.1.2 LPP Sessions and Transactions..... | 20 | +| 4.1.3 LPP Position Methods..... | 21 | +| 4.1.4 LPP Messages..... | 21 | +| 4.2 Common LPP Session Procedure..... | 21 | +| 4.3 LPP Transport..... | 22 | +| 4.3.1 Transport Layer Requirements..... | 22 | +| 4.3.2 LPP Duplicate Detection..... | 22 | +| 4.3.3 LPP Acknowledgement..... | 23 | +| 4.3.3.1 General..... | 23 | +| 4.3.3.2 Procedure related to Acknowledgement..... | 23 | +| 4.3.4 LPP Retransmission..... | 24 | +| 4.3.4.1 General..... | 24 | +| 4.3.4.2 Procedure related to Retransmission..... | 24 | +| 4.3.5 LPP Message Segmentation..... | 25 | +| 5 LPP Procedures..... | 26 | +| 5.1 Procedures related to capability transfer..... | 26 | +| 5.1.1 Capability Transfer procedure..... | 26 | +| 5.1.2 Capability Indication procedure..... | 26 | +| 5.1.3 Reception of LPP Request Capabilities..... | 27 | +| 5.1.4 Transmission of LPP Provide Capabilities..... | 27 | +| 5.2 Procedures related to Assistance Data Transfer..... | 27 | +| 5.2.1 Assistance Data Transfer procedure..... | 27 | +| 5.2.1a Periodic Assistance Data Transfer procedure..... | 28 | +| 5.2.1b Periodic Assistance Data Transfer with Update procedure..... | 30 | +| 5.2.2 Assistance Data Delivery procedure..... | 30 | +| 5.2.2a Periodic Assistance Data Delivery procedure..... | 31 | +| 5.2.3 Transmission of LPP Request Assistance Data..... | 33 | +| 5.2.4 Reception of LPP Provide Assistance Data..... | 33 | +| 5.3 Procedures related to Location Information Transfer..... | 33 | +| 5.3.1 Location Information Transfer procedure..... | 33 | +| 5.3.2 Location Information Delivery procedure..... | 34 | +| 5.3.3 Reception of Request Location Information..... | 34 | + +# Copyright Notification + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association +Bluetooth® is a Trade Mark of the Bluetooth SIG registered for the benefit of its members + +| | | | +|-------|----------------------------------------------------------------------------|----| +| 5.3.4 | Transmission of Provide Location Information..... | 35 | +| 5.4 | Error Handling Procedures..... | 35 | +| 5.4.1 | General..... | 35 | +| 5.4.2 | Procedures related to Error Indication..... | 35 | +| 5.4.3 | LPP Error Detection..... | 35 | +| 5.4.4 | Reception of an LPP Error Message..... | 36 | +| 5.5 | Abort Procedure..... | 37 | +| 5.5.1 | General..... | 37 | +| 5.5.2 | Procedures related to Abort..... | 37 | +| 5.5.3 | Reception of an LPP Abort Message..... | 37 | +| 6 | Information Element Abstract Syntax Definition..... | 37 | +| 6.1 | General..... | 37 | +| 6.2 | LPP PDU Structure..... | 38 | +| – | LPP-PDU-Definitions ..... | 38 | +| – | LPP-Message ..... | 38 | +| – | LPP-MessageBody ..... | 39 | +| – | LPP-TransactionID ..... | 39 | +| 6.3 | Message Body IEs..... | 40 | +| – | RequestCapabilities ..... | 40 | +| – | ProvideCapabilities ..... | 40 | +| – | RequestAssistanceData ..... | 41 | +| – | ProvideAssistanceData ..... | 41 | +| – | RequestLocationInformation ..... | 42 | +| – | ProvideLocationInformation ..... | 43 | +| – | Abort ..... | 43 | +| – | Error ..... | 44 | +| 6.4 | Common IEs..... | 44 | +| 6.4.1 | Common Lower-Level IEs..... | 44 | +| – | AccessTypes ..... | 44 | +| – | ARFCN-ValueEUTRA ..... | 45 | +| – | ARFCN-ValueNR ..... | 45 | +| – | ARFCN-ValueUTRA ..... | 45 | +| – | CarrierFreq-NB ..... | 45 | +| – | CellGlobalIdEUTRA-AndUTRA ..... | 46 | +| – | CellGlobalIdGERAN ..... | 46 | +| – | ECGI ..... | 47 | +| – | Ellipsoid-Point ..... | 47 | +| – | Ellipsoid-PointWithUncertaintyCircle ..... | 47 | +| – | EllipsoidPointWithUncertaintyEllipse ..... | 47 | +| – | EllipsoidPointWithAltitude ..... | 48 | +| – | EllipsoidPointWithAltitudeAndUncertaintyEllipsoid ..... | 48 | +| – | EllipsoidArc ..... | 48 | +| – | EPDU-Sequence ..... | 48 | +| – | FreqBandIndicatorNR ..... | 49 | +| – | HA-EllipsoidPointWithAltitudeAndScalableUncertaintyEllipsoid ..... | 49 | +| – | HA-EllipsoidPointWithScalableUncertaintyEllipse ..... | 50 | +| – | HighAccuracyEllipsoidPointWithUncertaintyEllipse ..... | 50 | +| – | HighAccuracyEllipsoidPointWithAltitudeAndUncertaintyEllipsoid ..... | 50 | +| – | HorizontalVelocity ..... | 51 | +| – | HorizontalWithVerticalVelocity ..... | 51 | +| – | HorizontalVelocityWithUncertainty ..... | 51 | +| – | HorizontalWithVerticalVelocityAndUncertainty ..... | 51 | +| – | Local2dPointWithUncertaintyEllipse ..... | 51 | +| – | Local3dPointWithUncertaintyEllipsoid ..... | 52 | +| – | LocationCoordinateTypes ..... | 53 | +| – | NCGL ..... | 53 | +| – | NR-PhysCellId ..... | 54 | +| – | PeriodicAssistanceDataControlParameters ..... | 54 | +| – | Polygon ..... | 54 | +| – | PositioningModes ..... | 55 | +| – | ScheduledLocationTimeSupport ..... | 55 | + +| | | | +|-------|--------------------------------------------------------------------|-----| +| – | ScheduledLocationTimeSupportPerMode ..... | 55 | +| – | SegmentationInfo ..... | 55 | +| – | VelocityTypes ..... | 56 | +| 6.4.2 | Common Positioning..... | 56 | +| – | CommonIEsRequestCapabilities ..... | 56 | +| – | CommonIEsProvideCapabilities ..... | 57 | +| – | CommonIEsRequestAssistanceData ..... | 57 | +| – | CommonIEsProvideAssistanceData ..... | 58 | +| – | CommonIEsRequestLocationInformation ..... | 58 | +| – | CommonIEsProvideLocationInformation ..... | 63 | +| – | CommonIEsAbort ..... | 65 | +| – | CommonIEsError ..... | 66 | +| 6.4.3 | Common NR Positioning Information Elements..... | 66 | +| – | AreaID-CellList ..... | 66 | +| – | CoordinateID ..... | 67 | +| – | DL-PRS-ID-Info ..... | 67 | +| – | LCS-GCS-TranslationParameter ..... | 67 | +| – | LOS-NLOS-Indicator ..... | 68 | +| – | LOS-NLOS-IndicatorGranularity1 ..... | 68 | +| – | LOS-NLOS-IndicatorGranularity2 ..... | 69 | +| – | LOS-NLOS-IndicatorType1 ..... | 69 | +| – | LOS-NLOS-IndicatorType2 ..... | 69 | +| – | NR-AdditionalPathList ..... | 69 | +| – | NR-AggregatedDL-PRS-ResourceSetID-Element ..... | 70 | +| – | NR-DL-PRS-AssistanceData ..... | 70 | +| – | NR-DL-PRS-BeamInfo ..... | 73 | +| – | NR-DL-PRS-ExpectedLOS-NLOS-Assistance ..... | 76 | +| – | NR-DL-PRS-Info ..... | 77 | +| – | NR-DL-PRS-MeasurementTimeWindowsConfig ..... | 80 | +| – | NR-DL-PRS-ProcessingCapability ..... | 81 | +| – | NR-DL-PRS-QCL-ProcessingCapability ..... | 90 | +| – | NR-DL-PRS-ResourceID ..... | 90 | +| – | NR-DL-PRS-ResourcesCapability ..... | 91 | +| – | NR-DL-PRS-ResourceSetID ..... | 92 | +| – | NR-DL-PRS-TRP-TEG-Info ..... | 92 | +| – | NR-IntegrityRiskParameters ..... | 93 | +| – | NR-IntegrityServiceAlert ..... | 93 | +| – | NR-IntegrityServiceParameters ..... | 94 | +| – | NR-On-Demand-DL-PRS-Configurations ..... | 94 | +| – | NR-On-Demand-DL-PRS-Information ..... | 95 | +| – | NR-On-Demand-DL-PRS-Request ..... | 96 | +| – | NR-On-Demand-DL-PRS-Configurations-Selected-IndexList ..... | 97 | +| – | NR-On-Demand-DL-PRS-Support ..... | 98 | +| – | NR-PeriodicAssistData ..... | 98 | +| – | NR-PeriodicAssistDataReq ..... | 98 | +| – | NR-PeriodicControlParam ..... | 99 | +| – | NR-PositionCalculationAssistance ..... | 99 | +| – | NR-PRU-DL-Info ..... | 101 | +| – | NR-RTD-Info ..... | 102 | +| – | NR-SelectedDL-PRS-IndexList ..... | 104 | +| – | NR-SSB-Config ..... | 105 | +| – | NR-Timestamp ..... | 106 | +| – | NR-TimingQuality ..... | 107 | +| – | NR-TRP-BeamAntennaInfo ..... | 107 | +| – | NR-TRP-LocationInfo ..... | 110 | +| – | NR-UE-TEG-Capability ..... | 113 | +| – | NR-UL-SRS-Capability ..... | 113 | +| – | NR-PhaseQuality ..... | 118 | +| – | ReferencePoint ..... | 119 | +| – | RelativeCartesianLocation ..... | 119 | +| – | RelativeLocation ..... | 120 | + +| | | | +|---------|----------------------------------------------------|-----| +| – | TEG-TimingErrorMargin ..... | 122 | +| – | RxTxTEG-TimingErrorMargin ..... | 122 | +| 6.5 | Positioning Method IEs..... | 122 | +| 6.5.1 | OTDOA Positioning..... | 122 | +| 6.5.1.1 | OTDOA Assistance Data..... | 122 | +| – | OTDOA-ProvideAssistanceData ..... | 122 | +| 6.5.1.2 | OTDOA Assistance Data Elements..... | 123 | +| – | OTDOA-ReferenceCellInfo ..... | 123 | +| – | PRS-Info ..... | 125 | +| – | TDD-Config ..... | 126 | +| – | OTDOA-NeighbourCellInfoList ..... | 127 | +| – | OTDOA-ReferenceCellInfoNB ..... | 130 | +| – | PRS-Info-NB ..... | 132 | +| – | OTDOA-NeighbourCellInfoListNB ..... | 135 | +| 6.5.1.3 | OTDOA Assistance Data Request..... | 138 | +| – | OTDOA-RequestAssistanceData ..... | 138 | +| 6.5.1.4 | OTDOA Location Information..... | 138 | +| – | OTDOA-ProvideLocationInformation ..... | 138 | +| 6.5.1.5 | OTDOA Location Information Elements..... | 139 | +| – | OTDOA-SignalMeasurementInformation ..... | 139 | +| – | OTDOA-SignalMeasurementInformation-NB ..... | 142 | +| – | OTDOA-MeasQuality ..... | 144 | +| – | AdditionalPath ..... | 145 | +| 6.5.1.6 | OTDOA Location Information Request..... | 145 | +| – | OTDOA-RequestLocationInformation ..... | 145 | +| 6.5.1.7 | OTDOA Capability Information..... | 146 | +| – | OTDOA-ProvideCapabilities ..... | 146 | +| 6.5.1.8 | OTDOA Capability Information Request..... | 149 | +| – | OTDOA-RequestCapabilities ..... | 149 | +| 6.5.1.9 | OTDOA Error Elements..... | 149 | +| – | OTDOA-Error ..... | 149 | +| – | OTDOA-LocationServerErrorCauses ..... | 149 | +| – | OTDOA-TargetDeviceErrorCauses ..... | 150 | +| 6.5.2 | A-GNSS Positioning..... | 150 | +| 6.5.2.1 | GNSS Assistance Data..... | 150 | +| – | A-GNSS-ProvideAssistanceData ..... | 150 | +| – | GNSS-CommonAssistData ..... | 150 | +| – | GNSS-GenericAssistData ..... | 151 | +| – | GNSS-PeriodicAssistData ..... | 152 | +| 6.5.2.2 | GNSS Assistance Data Elements..... | 153 | +| – | GNSS-ReferenceTime ..... | 153 | +| – | GNSS-SystemTime ..... | 154 | +| – | GPS-TOW-Assist ..... | 155 | +| – | NetworkTime ..... | 155 | +| – | GNSS-ReferenceLocation ..... | 158 | +| – | GNSS-IonosphericModel ..... | 158 | +| – | KlobucharModelParameter ..... | 158 | +| – | KlobucharModel2Parameter ..... | 159 | +| – | NeQuickModelParameter ..... | 160 | +| – | GNSS-EarthOrientationParameters ..... | 160 | +| – | GNSS-RTK-ReferenceStationInfo ..... | 161 | +| – | GNSS-RTK-CommonObservationInfo ..... | 163 | +| – | GNSS-RTK-AuxiliaryStationData ..... | 164 | +| – | GNSS-SSR-CorrectionPoints ..... | 166 | +| – | GNSS-Integrity-ServiceParameters ..... | 167 | +| – | GNSS-Integrity-ServiceAlert ..... | 167 | +| – | GNSS-LOS-NLOS-GridPoints ..... | 168 | +| – | GNSS-SSR-IOD-Update ..... | 169 | +| – | GNSS-TimeModelList ..... | 170 | +| – | GNSS-DifferentialCorrections ..... | 171 | +| – | GNSS-NavigationModel ..... | 174 | + +| | | | +|---------|-------------------------------------------------|-----| +| – | StandardClockModelList ..... | 176 | +| – | NAV-ClockModel ..... | 177 | +| – | CNAV-ClockModel ..... | 177 | +| – | GLONASS-ClockModel ..... | 178 | +| – | SBAS-ClockModel ..... | 179 | +| – | BDS-ClockModel ..... | 179 | +| – | BDS-ClockModel2 ..... | 180 | +| – | NavIC-ClockModel ..... | 181 | +| – | NavModelKeplerianSet ..... | 181 | +| – | NavModelNAV-KeplerianSet ..... | 183 | +| – | NavModelCNAV-KeplerianSet ..... | 184 | +| – | NavModel-GLONASS-ECEF ..... | 185 | +| – | NavModel-SBAS-ECEF ..... | 186 | +| – | NavModel-BDS-KeplerianSet ..... | 187 | +| – | NavModel-BDS-KeplerianSet2 ..... | 189 | +| – | NavModel-NavIC-KeplerianSet ..... | 191 | +| – | GNSS-RealTimeIntegrity ..... | 192 | +| – | GNSS-DataBitAssistance ..... | 193 | +| – | GNSS-AcquisitionAssistance ..... | 194 | +| – | GNSS-Almanac ..... | 197 | +| – | AlmanacKeplerianSet ..... | 198 | +| – | AlmanacNAV-KeplerianSet ..... | 199 | +| – | AlmanacReducedKeplerianSet ..... | 200 | +| – | AlmanacMidiAlmanacSet ..... | 201 | +| – | AlmanacGLONASS-AlmanacSet ..... | 202 | +| – | AlmanacECEF-SBAS-AlmanacSet ..... | 203 | +| – | AlmanacBDS-AlmanacSet ..... | 204 | +| – | AlmanacNavIC-AlmanacSet ..... | 205 | +| – | GNSS-UTC-Model ..... | 206 | +| – | UTC-ModelSet1 ..... | 206 | +| – | UTC-ModelSet2 ..... | 207 | +| – | UTC-ModelSet3 ..... | 208 | +| – | UTC-ModelSet4 ..... | 208 | +| – | UTC-ModelSet5 ..... | 209 | +| – | GNSS-AuxiliaryInformation ..... | 210 | +| – | BDS-DifferentialCorrections ..... | 211 | +| – | BDS-GridModelParameter ..... | 212 | +| – | GNSS-RTK-Observations ..... | 212 | +| – | GLO-RTK-BiasInformation ..... | 215 | +| – | GNSS-RTK-MAC-CorrectionDifferences ..... | 216 | +| – | GNSS-RTK-Residuals ..... | 218 | +| – | GNSS-RTK-FKP-Gradients ..... | 219 | +| – | GNSS-SSR-OrbitCorrections ..... | 221 | +| – | GNSS-SSR-ClockCorrections ..... | 224 | +| – | GNSS-SSR-CodeBias ..... | 226 | +| – | GNSS-SSR-URA ..... | 227 | +| – | GNSS-SSR-PhaseBias ..... | 228 | +| – | GNSS-SSR-STECCorrection ..... | 230 | +| – | GNSS-SSR-GriddedCorrection ..... | 234 | +| – | NavIC-DifferentialCorrections ..... | 239 | +| – | NavIC-GridModelParameter ..... | 240 | +| – | GNSS-SSR-OrbitCorrectionsSet2 ..... | 241 | +| – | GNSS-SSR-ClockCorrectionsSet2 ..... | 242 | +| – | GNSS-SSR-URA-Set2 ..... | 242 | +| – | GNSS-LOS-NLOS-GriddedIndications ..... | 243 | +| – | GNSS-SSR-SatellitePCVResiduals ..... | 243 | +| 6.5.2.3 | GNSS Assistance Data Request ..... | 244 | +| – | A-GNSS-RequestAssistanceData ..... | 244 | +| – | GNSS-CommonAssistDataReq ..... | 245 | +| – | GNSS-GenericAssistDataReq ..... | 246 | +| – | GNSS-PeriodicAssistDataReq ..... | 248 | + +| | | | +|----------|-------------------------------------------------|-----| +| 6.5.2.4 | GNSS Assistance Data Request Elements..... | 249 | +| – | GNSS-ReferenceTimeReq..... | 249 | +| – | GNSS-ReferenceLocationReq..... | 250 | +| – | GNSS-IonosphericModelReq..... | 250 | +| – | GNSS-EarthOrientationParametersReq..... | 250 | +| – | GNSS-RTK-ReferenceStationInfoReq..... | 251 | +| – | GNSS-RTK-AuxiliaryStationDataReq..... | 251 | +| – | GNSS-SSR-CorrectionPointsReq..... | 251 | +| – | GNSS-Integrity-ServiceParametersReq..... | 252 | +| – | GNSS-Integrity-ServiceAlertReq..... | 252 | +| – | GNSS-SSR-IOD-UpdateReq..... | 252 | +| – | GNSS-TimeModelListReq..... | 252 | +| – | GNSS-DifferentialCorrectionsReq..... | 253 | +| – | GNSS-NavigationModelReq..... | 253 | +| – | GNSS-RealTimeIntegrityReq..... | 255 | +| – | GNSS-DataBitAssistanceReq..... | 255 | +| – | GNSS-AcquisitionAssistanceReq..... | 256 | +| – | GNSS-AlmanacReq..... | 256 | +| – | GNSS-UTC-ModelReq..... | 257 | +| – | GNSS-AuxiliaryInformationReq..... | 257 | +| – | BDS-DifferentialCorrectionsReq..... | 257 | +| – | BDS-GridModelReq..... | 258 | +| – | GNSS-RTK-ObservationsReq..... | 258 | +| – | GLO-RTK-BiasInformationReq..... | 258 | +| – | GNSS-RTK-MAC-CorrectionDifferencesReq..... | 259 | +| – | GNSS-RTK-ResidualsReq..... | 259 | +| – | GNSS-RTK-FKP-GradientsReq..... | 260 | +| – | GNSS-SSR-OrbitCorrectionsReq..... | 260 | +| – | GNSS-SSR-ClockCorrectionsReq..... | 261 | +| – | GNSS-SSR-CodeBiasReq..... | 261 | +| – | GNSS-SSR-URA-Req..... | 261 | +| – | GNSS-SSR-PhaseBiasReq..... | 262 | +| – | GNSS-SSR-STECCorrectionReq..... | 262 | +| – | GNSS-SSR-GriddedCorrectionReq..... | 262 | +| – | NavIC-DifferentialCorrectionsReq..... | 263 | +| – | NavIC-GridModelReq..... | 263 | +| – | GNSS-SSR-OrbitCorrectionsSet2Req..... | 263 | +| – | GNSS-SSR-ClockCorrectionsSet2Req..... | 264 | +| – | GNSS-SSR-URA-Set2Req..... | 264 | +| – | GNSS-LOS-NLOS-GriddedIndicationsReq..... | 264 | +| – | GNSS-SSR-SatellitePCVResidualsReq..... | 265 | +| 6.5.2.5 | GNSS Location Information..... | 265 | +| – | A-GNSS-ProvideLocationInformation..... | 265 | +| 6.5.2.6 | GNSS Location Information Elements..... | 265 | +| – | GNSS-SignalMeasurementInformation..... | 265 | +| – | MeasurementReferenceTime..... | 266 | +| – | GNSS-MeasurementList..... | 268 | +| – | GNSS-LocationInformation..... | 272 | +| – | HA-GNSS-Metrics..... | 272 | +| 6.5.2.7 | GNSS Location Information Request..... | 273 | +| – | A-GNSS-RequestLocationInformation..... | 273 | +| 6.5.2.8 | GNSS Location Information Request Elements..... | 273 | +| – | GNSS-PositioningInstructions..... | 273 | +| 6.5.2.9 | GNSS Capability Information..... | 274 | +| – | A-GNSS-ProvideCapabilities..... | 274 | +| 6.5.2.10 | GNSS Capability Information Elements..... | 276 | +| – | GNSS-CommonAssistanceDataSupport..... | 276 | +| – | GNSS-ReferenceTimeSupport..... | 277 | +| – | GNSS-ReferenceLocationSupport..... | 278 | +| – | GNSS-IonosphericModelSupport..... | 278 | +| – | GNSS-EarthOrientationParametersSupport..... | 278 | + +| | | | +|----------|--------------------------------------------------------|-----| +| – | GNSS-RTK-ReferenceStationInfoSupport ..... | 278 | +| – | GNSS-RTK-AuxiliaryStationDataSupport ..... | 278 | +| – | GNSS-Integrity-ServiceParametersSupport ..... | 278 | +| – | GNSS-Integrity-ServiceAlertSupport ..... | 279 | +| – | GNSS-SSR-IOD-UpdateSupport ..... | 279 | +| – | GNSS-GenericAssistanceDataSupport ..... | 279 | +| – | GNSS-TimeModelListSupport ..... | 281 | +| – | GNSS-DifferentialCorrectionSupport ..... | 281 | +| – | GNSS-NavigationModelSupport ..... | 282 | +| – | GNSS-RealTimeIntegritySupport ..... | 283 | +| – | GNSS-DataBitAssistanceSupport ..... | 283 | +| – | GNSS-AcquisitionAssistanceSupport ..... | 283 | +| – | GNSS-AlmanacSupport ..... | 284 | +| – | GNSS-UTC-ModelSupport ..... | 284 | +| – | GNSS-AuxiliaryInformationSupport ..... | 285 | +| – | BDS-DifferentialCorrectionsSupport ..... | 285 | +| – | BDS-GridModelSupport ..... | 285 | +| – | GNSS-RTK-ObservationsSupport ..... | 285 | +| – | GLO-RTK-BiasInformationSupport ..... | 285 | +| – | GNSS-RTK-MAC-CorrectionDifferencesSupport ..... | 286 | +| – | GNSS-RTK-ResidualsSupport ..... | 286 | +| – | GNSS-RTK-FKP-GradientsSupport ..... | 286 | +| – | GNSS-SSR-OrbitCorrectionsSupport ..... | 286 | +| – | GNSS-SSR-ClockCorrectionsSupport ..... | 287 | +| – | GNSS-SSR-URA-Support ..... | 287 | +| – | GNSS-SSR-STECCorrectionSupport ..... | 288 | +| – | GNSS-SSR-GriddedCorrectionSupport ..... | 288 | +| – | NavIC-DifferentialCorrectionsSupport ..... | 288 | +| – | NavIC-GridModelSupport ..... | 289 | +| – | GNSS-SSR-OrbitCorrectionsSet2Support ..... | 289 | +| – | GNSS-SSR-ClockCorrectionsSet2Support ..... | 289 | +| – | GNSS-SSR-URA-Set2Support ..... | 289 | +| – | GNSS-LOS-NLOS-GriddedIndicationsSupport ..... | 289 | +| 6.5.2.11 | GNSS Capability Information Request..... | 290 | +| – | A-GNSS-RequestCapabilities ..... | 290 | +| 6.5.2.12 | GNSS Error Elements..... | 290 | +| – | A-GNSS-Error ..... | 290 | +| – | GNSS-LocationServerErrorCauses ..... | 290 | +| – | GNSS-TargetDeviceErrorCauses ..... | 291 | +| 6.5.2.13 | Common GNSS Information Elements..... | 291 | +| – | GNSS-FrequencyID ..... | 291 | +| – | GNSS-ID ..... | 292 | +| – | GNSS-ID-Bitmap ..... | 293 | +| – | GNSS-Link-CombinationsList ..... | 293 | +| – | GNSS-NavListInfo ..... | 293 | +| – | GNSS-NetworkID ..... | 293 | +| – | GNSS-PeriodicControlParam ..... | 294 | +| – | GNSS-ReferenceStationID ..... | 294 | +| – | GNSS-SignalID ..... | 294 | +| – | GNSS-SignalIDs ..... | 296 | +| – | GNSS-SubNetworkID ..... | 297 | +| – | SBAS-ID ..... | 298 | +| – | SBAS-IDs ..... | 298 | +| – | SV-ID ..... | 298 | +| 6.5.3 | Enhanced Cell ID Positioning..... | 299 | +| 6.5.3.1 | E-CID Location Information..... | 299 | +| – | ECID-ProvideLocationInformation ..... | 299 | +| 6.5.3.2 | E-CID Location Information Elements..... | 299 | +| – | ECID-SignalMeasurementInformation ..... | 299 | +| 6.5.3.3 | E-CID Location Information Request..... | 301 | +| – | ECID-RequestLocationInformation ..... | 301 | + +| | | | +|---------|------------------------------------------------|-----| +| 6.5.3.4 | E-CID Capability Information..... | 301 | +| – | ECID-ProvideCapabilities ..... | 301 | +| 6.5.3.5 | E-CID Capability Information Request..... | 302 | +| – | ECID-RequestCapabilities ..... | 302 | +| 6.5.3.6 | E-CID Error Elements..... | 302 | +| – | ECID-Error ..... | 302 | +| – | ECID-LocationServerErrorCauses ..... | 303 | +| – | ECID-TargetDeviceErrorCauses ..... | 303 | +| 6.5.4 | Terrestrial Beacon System Positioning..... | 303 | +| 6.5.4.1 | TBS Location Information..... | 303 | +| – | TBS-ProvideLocationInformation ..... | 303 | +| 6.5.4.2 | TBS Location Information Elements..... | 304 | +| – | TBS-MeasurementInformation ..... | 304 | +| – | MBS-BeaconMeasList ..... | 304 | +| 6.5.4.3 | TBS Location Information Request..... | 305 | +| – | TBS-RequestLocationInformation ..... | 305 | +| 6.5.4.4 | TBS Capability Information..... | 305 | +| – | TBS-ProvideCapabilities ..... | 305 | +| – | MBS-AssistanceDataSupportList ..... | 306 | +| 6.5.4.5 | TBS Capability Information Request..... | 307 | +| – | TBS-RequestCapabilities ..... | 307 | +| 6.5.4.6 | TBS Error Elements..... | 307 | +| – | TBS-Error ..... | 307 | +| – | TBS-LocationServerErrorCauses ..... | 307 | +| – | TBS-TargetDeviceErrorCauses ..... | 307 | +| 6.5.4.7 | TBS Assistance Data..... | 308 | +| – | TBS-ProvideAssistanceData ..... | 308 | +| 6.5.4.8 | TBS Assistance Data Elements..... | 308 | +| – | TBS-AssistanceDataList ..... | 308 | +| – | MBS-AlmanacAssistance ..... | 308 | +| – | MBS-AcquisitionAssistance ..... | 309 | +| 6.5.4.9 | TBS Assistance Data Request..... | 309 | +| – | TBS-RequestAssistanceData ..... | 309 | +| 6.5.5 | Sensor based Positioning..... | 310 | +| 6.5.5.0 | Introduction..... | 310 | +| 6.5.5.1 | Sensor Location Information..... | 310 | +| – | Sensor-ProvideLocationInformation ..... | 310 | +| 6.5.5.2 | Sensor Location Information Elements..... | 310 | +| – | Sensor-MeasurementInformation ..... | 310 | +| – | Sensor-MotionInformation ..... | 311 | +| 6.5.5.3 | Sensor Location Information Request..... | 312 | +| – | Sensor-RequestLocationInformation ..... | 312 | +| 6.5.5.4 | Sensor Capability Information..... | 313 | +| – | Sensor-ProvideCapabilities ..... | 313 | +| 6.5.5.5 | Sensor Capability Information Request..... | 314 | +| – | Sensor-RequestCapabilities ..... | 314 | +| 6.5.5.6 | Sensor Error Elements..... | 314 | +| – | Sensor-Error ..... | 314 | +| – | Sensor-LocationServerErrorCauses ..... | 314 | +| – | Sensor-TargetDeviceErrorCauses ..... | 315 | +| 6.5.5.7 | Sensor Assistance Data..... | 315 | +| – | Sensor-ProvideAssistanceData ..... | 315 | +| 6.5.5.8 | Sensor Assistance Data Elements..... | 315 | +| – | Sensor-AssistanceDataList ..... | 315 | +| 6.5.5.9 | Sensor Assistance Data Request..... | 316 | +| – | Sensor-RequestAssistanceData ..... | 316 | +| 6.5.6 | WLAN-based Positioning..... | 317 | +| 6.5.6.1 | WLAN Location Information..... | 317 | +| – | WLAN-ProvideLocationInformation ..... | 317 | +| 6.5.6.2 | WLAN Location Information Elements..... | 317 | +| – | WLAN-MeasurementInformation ..... | 317 | + +| | | | +|----------|---------------------------------------------------|-----| +| 6.5.6.3 | WLAN Location Information Request..... | 318 | +| – | WLAN-RequestLocationInformation ..... | 318 | +| 6.5.6.4 | WLAN Capability Information..... | 319 | +| – | WLAN-ProvideCapabilities ..... | 319 | +| 6.5.6.5 | WLAN Capability Information Request..... | 320 | +| – | WLAN-RequestCapabilities ..... | 320 | +| 6.5.6.6 | WLAN Error Elements..... | 320 | +| – | WLAN-Error ..... | 320 | +| – | WLAN-LocationServerErrorCauses ..... | 320 | +| – | WLAN-TargetDeviceErrorCauses ..... | 321 | +| 6.5.7 | Bluetooth-based Positioning..... | 324 | +| 6.5.7.1 | Bluetooth Location Information..... | 324 | +| – | BT-ProvideLocationInformation ..... | 324 | +| 6.5.7.2 | Bluetooth Location Information Elements..... | 325 | +| – | BT-MeasurementInformation ..... | 325 | +| 6.5.7.3 | Bluetooth Location Information Request..... | 326 | +| – | BT-RequestLocationInformation ..... | 326 | +| 6.5.7.4 | Bluetooth Capability Information..... | 327 | +| – | BT-ProvideCapabilities ..... | 327 | +| 6.5.7.5 | Bluetooth Capability Information Request..... | 328 | +| – | BT-RequestCapabilities ..... | 328 | +| 6.5.7.6 | BT Error Elements..... | 328 | +| – | BT-Error ..... | 328 | +| – | BT-LocationServerErrorCauses ..... | 328 | +| – | BT-TargetDeviceErrorCauses ..... | 329 | +| 6.5.7.7 | Bluetooth Assistance Data..... | 329 | +| – | BT-ProvideAssistanceData ..... | 329 | +| 6.5.7.8 | Bluetooth Assistance Data Elements..... | 330 | +| – | BT-BeaconInfo ..... | 330 | +| – | BT-UniformLinearArray ..... | 332 | +| – | BT-UniformRectangularArray ..... | 332 | +| – | BT-UniformCircularArray ..... | 333 | +| – | BT-GenericArray ..... | 333 | +| 6.5.7.9 | Bluetooth Assistance Data Request..... | 334 | +| – | BT-RequestAssistanceData ..... | 334 | +| 6.5.8 | NR UL Positioning..... | 334 | +| 6.5.8.1 | NR UL Capability Information..... | 334 | +| – | NR-UL-ProvideCapabilities ..... | 334 | +| 6.5.8.2 | NR UL Capability Information Request..... | 335 | +| – | NR-UL-RequestCapabilities ..... | 335 | +| 6.5.9 | NR E-CID Positioning..... | 335 | +| 6.5.9.1 | NR E-CID Location Information..... | 335 | +| – | NR-ECID-ProvideLocationInformation ..... | 335 | +| 6.5.9.2 | NR E-CID Location Information Elements..... | 335 | +| – | NR-ECID-SignalMeasurementInformation ..... | 335 | +| 6.5.9.3 | NR E-CID Location Information Request..... | 336 | +| – | NR-ECID-RequestLocationInformation ..... | 336 | +| 6.5.9.4 | NR E-CID Capability Information..... | 337 | +| – | NR-ECID-ProvideCapabilities ..... | 337 | +| 6.5.9.5 | NR E-CID Capability Information Request..... | 337 | +| – | NR-ECID-RequestCapabilities ..... | 337 | +| 6.5.9.6 | NR E-CID Error Elements..... | 338 | +| – | NR-ECID-Error ..... | 338 | +| – | NR-ECID-LocationServerErrorCauses ..... | 338 | +| – | NR-ECID-TargetDeviceErrorCauses ..... | 338 | +| 6.5.10 | NR DL-TDOA Positioning..... | 339 | +| 6.5.10.1 | NR DL-TDOA Assistance Data..... | 339 | +| – | NR-DL-TDOA-ProvideAssistanceData ..... | 339 | +| 6.5.10.2 | NR DL-TDOA Assistance Data Request..... | 340 | +| – | NR-DL-TDOA-RequestAssistanceData ..... | 340 | +| 6.5.10.3 | NR DL-TDOA Location Information..... | 341 | + +| | | | +|-----------|-----------------------------------------------------------|-----| +| – | NR-DL-TDOA-ProvideLocationInformation ..... | 341 | +| 6.5.10.4 | NR DL-TDOA Location Information Elements..... | 342 | +| – | NR-DL-TDOA-SignalMeasurementInformation ..... | 342 | +| – | NR-DL-TDOA-LocationInformation ..... | 345 | +| 6.5.10.5 | NR DL-TDOA Location Information Request..... | 346 | +| – | NR-DL-TDOA-RequestLocationInformation ..... | 346 | +| 6.5.10.6 | NR DL-TDOA Capability Information..... | 348 | +| – | NR-DL-TDOA-ProvideCapabilities ..... | 348 | +| 6.5.10.6a | NR DL-TDOA Capability Information Elements..... | 350 | +| – | NR-DL-TDOA-MeasurementCapability ..... | 350 | +| 6.5.10.7 | NR DL-TDOA Capability Information Request..... | 352 | +| – | NR-DL-TDOA-RequestCapabilities ..... | 352 | +| 6.5.10.8 | NR DL-TDOA Error Elements..... | 352 | +| – | NR-DL-TDOA-Error ..... | 352 | +| – | NR-DL-TDOA-LocationServerErrorCauses ..... | 352 | +| – | NR-DL-TDOA-TargetDeviceErrorCauses ..... | 352 | +| 6.5.11 | NR DL-AoD Positioning..... | 353 | +| 6.5.11.1 | NR DL-AoD Assistance Data..... | 353 | +| – | NR-DL-AoD-ProvideAssistanceData ..... | 353 | +| 6.5.11.2 | NR DL-AoD Assistance Data Request..... | 354 | +| – | NR-DL-AoD-RequestAssistanceData ..... | 354 | +| 6.5.11.3 | NR DL-AoD Location Information..... | 355 | +| – | NR-DL-AoD-ProvideLocationInformation ..... | 355 | +| 6.5.11.4 | NR DL-AoD Location Information Elements..... | 356 | +| – | NR-DL-AoD-SignalMeasurementInformation ..... | 356 | +| – | NR-DL-AoD-LocationInformation ..... | 357 | +| 6.5.11.5 | NR DL-AoD Location Information Request..... | 358 | +| – | NR-DL-AoD-RequestLocationInformation ..... | 358 | +| 6.5.11.6 | NR DL-AoD Capability Information..... | 359 | +| – | NR-DL-AoD-ProvideCapabilities ..... | 359 | +| 6.5.11.6a | NR DL-AoD Capability Information Elements..... | 362 | +| – | NR-DL-AoD-MeasurementCapability ..... | 362 | +| 6.5.11.7 | NR DL-AoD Capability Information Request..... | 363 | +| – | NR-DL-AoD-RequestCapabilities ..... | 363 | +| 6.5.11.8 | NR DL-AoD Error Elements..... | 363 | +| – | NR-DL-AoD-Error ..... | 363 | +| – | NR-DL-AoD-LocationServerErrorCauses ..... | 363 | +| – | NR-DL-AoD-TargetDeviceErrorCauses ..... | 364 | +| 6.5.12 | NR Multi-RTT Positioning..... | 364 | +| 6.5.12.1 | NR Multi-RTT Assistance Data..... | 364 | +| – | NR-Multi-RTT-ProvideAssistanceData ..... | 364 | +| 6.5.12.2 | NR Multi-RTT Assistance Data Request..... | 365 | +| – | NR-Multi-RTT-RequestAssistanceData ..... | 365 | +| 6.5.12.3 | NR Multi-RTT Location Information..... | 366 | +| – | NR-Multi-RTT-ProvideLocationInformation ..... | 366 | +| 6.5.12.4 | NR Multi-RTT Location Information Elements..... | 366 | +| – | NR-Multi-RTT-SignalMeasurementInformation ..... | 366 | +| 6.5.12.5 | NR Multi-RTT Location Information Request..... | 371 | +| – | NR-Multi-RTT-RequestLocationInformation ..... | 371 | +| 6.5.12.6 | NR Multi-RTT Capability Information..... | 374 | +| – | NR-Multi-RTT-ProvideCapabilities ..... | 374 | +| 6.5.12.6a | NR Multi-RTT Capability Information Elements..... | 375 | +| – | NR-Multi-RTT-MeasurementCapability ..... | 375 | +| 6.5.12.7 | NR Multi-RTT Capability Information Request..... | 377 | +| – | NR-Multi-RTT-RequestCapabilities ..... | 377 | +| 6.5.12.8 | NR Multi-RTT Error Elements..... | 377 | +| – | NR-Multi-RTT-Error ..... | 377 | +| – | NR-Multi-RTT-LocationServerErrorCauses ..... | 377 | +| – | NR-Multi-RTT-TargetDeviceErrorCauses ..... | 378 | +| 6.6 | Multiplicity and type constraint values..... | 378 | +| – | Multiplicity and type constraint definitions ..... | 378 | + +| | | | +|-------------------------------|--------------------------------------------------------------|------------| +| – | End of LPP-PDU-Definitions ..... | 379 | +| 7 | Broadcast of assistance data..... | 379 | +| 7.1 | General..... | 379 | +| 7.2 | Mapping of posSibType to assistance data element..... | 379 | +| 7.3 | Procedures related to broadcast information elements..... | 381 | +| 7.4 | Broadcast information elements..... | 383 | +| 7.4.1 | Basic production..... | 383 | +| – | LPP-Broadcast-Definitions ..... | 383 | +| 7.4.2 | Element definitions..... | 383 | +| – | AssistanceDataSIBelement ..... | 383 | +| – | OTDOA-UE-Assisted ..... | 384 | +| – | NR-UEB-TRP-LocationData ..... | 384 | +| – | NR-UEB-TRP-RTD-Info ..... | 385 | +| – | NR-IntegrityParameters ..... | 385 | +| – | End of LPP-Broadcast-Definitions ..... | 386 | +| 7.5 | Broadcast ciphering (informative)..... | 386 | +| Annex A (informative): | Change History..... | 388 | + +--- + +## 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 contains the definition of the LTE Positioning Protocol (LPP) for the radio access technologies E-UTRA/LTE and NR. + +--- + +# 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 36.305: "Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN". +- [3] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)". +- [4] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006. +- [5] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005. +- [6] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, September 4, 2008. +- [7] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.1, July 31, 2009. +- [8] Galileo OS Signal in Space ICD (OS SIS ICD), Issue 1.2, February 2014, European Union. +- [9] Global Navigation Satellite System GLONASS Interface Control Document, Version 5.1, 2008. +- [10] Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001. +- [11] RTCM-SC104, RTCM Recommended Standards for Differential GNSS Service (v.2.3), August 20, 2001. +- [12] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [13] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification". +- [14] 3GPP TS 44.031: "Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP)". +- [15] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [16] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation". +- [17] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer – Measurements". + +- [18] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management". +- [19] 3GPP TS 23.003: "Numbering, addressing and identification". +- [20] OMA-TS-LPPE-V1\_0, LPP Extensions Specification, Open Mobile Alliance. +- [21] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [22] ITU-T Recommendation X.691 (07/2002) "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)" (Same as the ISO/IEC International Standard 8825-2). +- [23] BDS-SIS-ICD-B1I-3.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B1I (Version 3.0)", February, 2019. +- [24] ATIS-0500027: "Recommendations for Establishing Wide Scale Indoor Location Performance", May 2015. +- [25] Bluetooth Special Interest Group: "Bluetooth Core Specification v4.2", December 2014. +- [26] IEEE 802.11, Part 11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". +- [27] IETF RFC 6225, "Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information", July 2011. +- [28] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures". +- [29] "Earth Gravitational Model 96 (EGM96)", National Geospatial-Intelligence Agency, NASA. +- [30] RTCM Standard 10403.3: "Differential GNSS (Global Navigation Satellite Systems) Services" – Version 3, October 7, 2016. +- [31] IGS ANTEx: "The Antenna Exchanged Format" – version 1.4, September 15, 2010. +- [32] Federal Information Processing Standards Publication 197, "Specification for the ADVANCED ENCRYPTION STANDARD (AES)", November 26, 2001. +- [33] NIST Special Publication 800-38A, "Recommendation for Block Cipher Modes of Operation Methods and Techniques", 2001. +- [34] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [35] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [36] 3GPP TS 38.215: "NR; Physical layer measurements". +- [37] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [38] IRNSS Signal-In-Space (SPS) Interface Control Document (ICD) for standard positioning service version 1.1, Aug 2017. +- [39] BDS-SIS-ICD-B1C-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B1C (Version 1.0)", December, 2017. +- [40] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". +- [41] 3GPP TS 38.211: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation". +- [42] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". + +- [43] IS-QZSS-L6-001, Quasi-Zenith Satellite System Interface Specification – Centimetre Level Augmentation Service, Cabinet Office, November 5, 2018. +- [44] 3GPP TR 38.901: "Technical Specification Group Radio Access Network; Study on channel model for frequencies from 0.5 to 100 GHz". +- [45] 3GPP TS 38.214: "NR; Physical layer procedures for data". +- [46] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [47] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". +- [48] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [49] BDS-SIS-ICD-B2a-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B2a (Version 1.0)", December, 2017. +- [50] BDS-SIS-ICD-B3I-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B3I (Version 1.0)", February, 2018. +- [51] NMEA standard 0183, Version 4.11, November 2018. +- [52] BDS-SIS-ICD-PPP-B2b-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Precise Point Positioning Service Signal PPP-B2b (Version 1.0)", July, 2020. +- [53] Bluetooth Special Interest Group: "Bluetooth Core Specification v5.4", February 2023. +- [54] 3GPP TS 38.101-5: "User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements". + +## 3 Definitions and Abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 36.305 [2], TS 23.271 [3], 38.305 [40] and TS 23.273 [42] apply. Other definitions are provided below. + +**Anchor carrier:** In NB-IoT, a carrier where the UE assumes that NPSS/NSSS/NPBCH/SIB-NB for FDD or NPSS/NSSS/NPBCH for TDD are transmitted. + +**Location Server:** a physical or logical entity (e.g., E-SMLC, SUPL SLP, or LMF) that manages positioning for a target device by obtaining measurements and other location information from one or more positioning units and providing assistance data to positioning units to help determine this. A Location Server may also compute or verify the final location estimate. + +**NB-IoT:** NB-IoT allows access to network services via E-UTRA with a channel bandwidth limited to 200 kHz. + +**Observed Time Difference Of Arrival (OTDOA):** The time interval that is observed by a target device between the reception of downlink signals from two different TPs. If a signal from TP 1 is received at the moment $t_1$ , and a signal from TP 2 is received at the moment $t_2$ , the OTDOA is $t_2 - t_1$ . + +**Positioning frequency layer:** A positioning frequency layer is defined as a collection of DL PRS resource sets where each DL PRS resource set is in turn a collection of DL PRS resources. All DL PRS resources from all DL PRS resource sets from the same positioning frequency layer have some common/same PRS parameters viz. PRS subcarrier spacing, PRS resource bandwidth, PRS start PRB, PRS Point A, PRS Comb size and PRS cyclic prefix. + +**PRS-only TP:** A TP which only transmits PRS signals or DL-PRS for PRS-based TBS positioning and is not associated with a cell. + +**Reference Source:** a physical entity or part of a physical entity that provides signals (e.g., RF, acoustic, infra-red) that can be measured (e.g., by a Target Device) in order to obtain the location of a Target Device. + +**Relative Time Difference (RTD):** The relative time difference between a TRP $i$ and a TRP $j$ , is defined as $t_j - t_i$ , where $t_i$ and $t_j$ are defined as the time when TRP $i$ and $j$ transmit the start of one subframe respectively. + +**Rx Time Delay:** From a signal reception perspective, there will be a time delay from the time when the RF signal arrives at the Rx antenna to the time when the signal is digitized and time-stamped at the baseband. + +**Rx Timing Error:** Result of Rx Time Delay involved in the reception of a signal before reporting measurements that are obtained from the signal. It is the uncalibrated Rx Time Delay, or the remaining delay after the UE/TRP internal calibration/compensation of the Rx Time Delay, involved in the reception of the DL-PRS/UL SRS signals. The calibration/compensation may also include the calibration/compensation of the relative time delay between different RF chains in the same UE/TRP and may also possibly consider the offset of the Rx antenna phase centre to the physical antenna centre. + +**Target Device:** the device that is being positioned (e.g., UE or SUPL SET). + +**Transmission Point (TP):** A set of geographically co-located transmit antennas (e.g. antenna array (with one or more antenna elements)) for one cell, part of one cell or one PRS-only TP. Transmission Points can include base station (eNodeB) antennas, remote radio heads, a remote antenna of a base station, an antenna of a PRS-only TP, etc. One cell can be formed by one or multiple transmission points. For a homogeneous deployment, each transmission point may correspond to one cell. + +**Transmission-Reception Point (TRP):** A set of geographically co-located antennas (e.g. antenna array (with one or more antenna elements)) supporting TP and/or RP functionality. + +**TRP Tx Timing Error Group (TRP Tx TEG):** Tx Timing Errors, associated with TRP transmissions on one or more DL-PRS Resources, that are within a certain margin. + +**Tx Time Delay:** From a signal transmission perspective, the time delay from the time when the digital signal is generated at baseband to the time when the RF signal is transmitted from the Tx antenna. + +**Tx Timing Error:** Result of Tx Time Delay involved in the transmission of a signal. It is the uncalibrated Tx Time Delay, or the remaining delay after the TRP/UE internal calibration/compensation of the Tx Time Delay, involved in the transmission of the DL-PRS/UL SRS signals. The calibration/compensation may also include the calibration/compensation of the relative time delay between different RF chains in the same TRP/UE and may also possibly consider the offset of the Tx antenna phase centre to the physical antenna centre. + +**UE Rx Timing Error Group (UE Rx TEG):** Rx Timing Errors, associated with UE reporting of one or more DL measurements, that are within a certain margin. + +**UE RxTx Timing Error Group (UE RxTx TEG):** Rx Timing Errors and Tx Timing Errors, associated with UE reporting of one or more UE Rx-Tx time difference measurements, which have the 'Rx Timing Errors + Tx Timing Errors' differences within a certain margin. + +**UE Tx Timing Error Group (UE Tx TEG):** Tx Timing Errors, associated with UE transmissions on one or more UL SRS resources for positioning purpose, that are within a certain margin. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply. + +| | | +|--------|------------------------------------------------------------------------------------------| +| ADR | Accumulated Delta-Range | +| A-GNSS | Assisted-GNSS | +| AoA | Angle-of-Arrival | +| AoD | Angle-of-Departure | +| AP | Access Point | +| ARFCN | Absolute Radio Frequency Channel Number | +| ARP | Antenna Reference Point | +| BDS | BeiDou Navigation Satellite System | +| BIPM | Bureau International des Poids et Mesures (International Bureau of Weights and Measures) | +| BSSID | Basic Service Set Identifier | +| BTS | Base Transceiver Station (GERAN) | +| CID | Cell-ID (positioning method) | +| CNAV | Civil Navigation | + +| | | +|-----------|----------------------------------------------------------------------------------------------| +| CRS | Cell-specific Reference Signals | +| DL-AoD | Downlink Angle-of-Departure | +| DL-TDOA | Downlink Time Difference Of Arrival | +| ECEF | Earth-Centered, Earth-Fixed | +| ECGI | Evolved Cell Global Identifier | +| ECI | Earth-Centered-Inertial | +| E-CID | Enhanced Cell-ID (positioning method) | +| EGNOS | European Geostationary Navigation Overlay Service | +| E-SMLC | Enhanced Serving Mobile Location Centre | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| EOP | Earth Orientation Parameters | +| EPDU | External Protocol Data Unit | +| FDMA | Frequency Division Multiple Access | +| FEC | Forward Error Correction | +| FKP | (German) Flächen-Korrektur-Parameter (area correction parameter) | +| FTA | Fine Time Assistance | +| GAGAN | GPS Aided Geo Augmented Navigation | +| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| HA GNSS | High-Accuracy GNSS (RTK, PPP) | +| HPL | Horizontal Protection Level | +| ICD | Interface Control Document | +| IGS | International GNSS Service | +| IOD | Issue of Data | +| IRNSS | Indian Regional Navigation Satellite System | +| IS | Interface Specification | +| LLA | Latitude Longitude Altitude | +| LMF | Location Management Function | +| LOS | Line-of-Sight | +| LPP | LTE Positioning Protocol | +| LPPa | LTE Positioning Protocol Annex | +| LSB | Least Significant Bit | +| MAC | Master Auxiliary Concept | +| MBS | Metropolitan Beacon System | +| MG | Measurement Gap | +| MO-LR | Mobile Originated Location Request | +| MSAS | Multi-functional Satellite Augmentation System | +| MSB | Most Significant Bit | +| msd | mean solar day | +| MT-LR | Mobile Terminated Location Request | +| Multi-RTT | Multiple-Round Trip Time | +| NAV | Navigation | +| NavIC | NAVigation with Indian Constellation | +| NB-IoT | NarrowBand Internet of Things | +| NCGI | NR Cell Global Identifier | +| NICT | National Institute of Information and Communications Technology | +| NI-LR | Network Induced Location Request | +| NLOS | Non-Line-of-Sight | +| NPRS | Narrowband Positioning Reference Signals | +| NR | NR Radio Access | +| NRSRP | Narrowband Reference Signal Received Power | +| NRSRQ | Narrowband Reference Signal Received Quality | +| NTN | Non-Terrestrial Network | +| NTSC | National Time Service Center of Chinese Academy of Sciences | +| OSR | Observation Space Representation | +| OTDOA | Observed Time Difference Of Arrival | +| PBCH | Physical Broadcast Channel | +| PDU | Protocol Data Unit | +| PL | Protection Level | + +| | | +|--------|---------------------------------------------------------------| +| PPP | Precise Point Positioning | +| PPW | PRS Processing Window | +| PRB | Physical Resource Block | +| PRC | Pseudo-Range Correction | +| PRS | Positioning Reference Signals | +| posSIB | Positioning System Information Block | +| PZ-90 | Parametry Zemli 1990 Goda – Parameters of the Earth Year 1990 | +| QZS | Quasi Zenith Satellite | +| QZSS | Quasi-Zenith Satellite System | +| QZST | Quasi-Zenith System Time | +| RF | Radio Frequency | +| RP | Reception Point | +| RRC | Range-Rate Correction
Radio Resource Control | +| RSCP | Reference Signal Carrier Phase | +| RSCPD | Reference Signal Carrier Phase Difference | +| RSRP | Reference Signal Received Power | +| RSRPP | Reference Signal Received Path Power | +| RSRQ | Reference Signal Received Quality | +| RSTD | Reference Signal Time Difference | +| RTK | Real-Time Kinematic | +| RTT | Round Trip Time | +| RU | Russia | +| SBAS | Space Based Augmentation System | +| SET | SUPL Enabled Terminal | +| SFN | System Frame Number | +| SLP | SUPL Location Platform | +| SRS | Sounding Reference Signal | +| SS | Synchronization Signal | +| SSB | Synchronization Signal Block, SS/PBCH Block | +| SSID | Service Set Identifier | +| SSR | State Space Representation | +| STEC | Slant TEC | +| SUPL | Secure User Plane Location | +| SV | Space Vehicle | +| TB | Terrestrial Beacon | +| TBS | Terrestrial Beacon System | +| TEC | Total Electron Content | +| TECU | TEC Units | +| TEG | Timing Error Group | +| TIR | Target Integrity Risk | +| TLM | Telemetry | +| TOA | Time Of Arrival | +| TOD | Time Of Day | +| TOW | Time Of Week | +| TP | Transmission Point | +| TRP | Transmission-Reception Point | +| UDRE | User Differential Range Error | +| ULP | User Plane Location Protocol | +| URA | User Range Accuracy | +| USNO | US Naval Observatory | +| UT1 | Universal Time No.1 | +| UTC | Coordinated Universal Time | +| VPL | Vertical Protection Level | +| WAAS | Wide Area Augmentation System | +| WGS-84 | World Geodetic System 1984 | +| WLAN | Wireless Local Area Network | + +## 4 Functionality of Protocol + +### 4.1 General + +#### 4.1.1 LPP Configuration + +LPP is used point-to-point between a location server (E-SMLC, LMF or SLP) and a target device (UE or SET) in order to position the target device using position-related measurements obtained by one or more reference sources. Figure 4.1.1-1 shows the configuration as applied to the control- and user-plane location solutions for E-UTRAN and NG-RAN (as defined in TS 36.305 [2], TS 38.305 [40], TS 23.273 [42] and TS 23.271 [3]). + +NB-IoT is a non-backward compatible variant of E-UTRAN supporting a reduced set of functionalities. In this specification, procedures and messages specified for the UE equally apply to the UE in NB-IoT. + +![Diagram of LPP Configuration for Control- and User-Plane Positioning in E-UTRAN or NG-RAN. The diagram shows a Target Device (UE/SET) connected to a Location Server (E-SMLC/LMF/SLP) via an LPP interface. The Target Device receives GNSS signals (B) from a Reference Source and LTE/NR radio signals (A) from an eNodeB/NG-RAN. The Target Device sends Measurements (A, B or A+B) or Location to the Location Server, which responds with Assistance Data.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +The diagram illustrates the LPP configuration for positioning. At the top, a 'Reference Source' (represented by two satellite icons) provides 'GNSS signals (B)' to a 'Target Device' (UE/SET). The Target Device is connected to an 'eNodeB/NG-RAN' (represented by a tower icon), which also provides 'LTE/NR radio signals (A)'. The Target Device sends 'Measurements (A, B or A+B) or Location' to a 'Location Server' (E-SMLC/LMF/SLP) via an 'LPP' interface. The Location Server responds with 'Assistance Data' to the Target Device. + +Diagram of LPP Configuration for Control- and User-Plane Positioning in E-UTRAN or NG-RAN. The diagram shows a Target Device (UE/SET) connected to a Location Server (E-SMLC/LMF/SLP) via an LPP interface. The Target Device receives GNSS signals (B) from a Reference Source and LTE/NR radio signals (A) from an eNodeB/NG-RAN. The Target Device sends Measurements (A, B or A+B) or Location to the Location Server, which responds with Assistance Data. + +Figure 4.1.1-1: LPP Configuration for Control- and User-Plane Positioning in E-UTRAN or NG-RAN + +#### 4.1.2 LPP Sessions and Transactions + +An LPP session is used between a Location Server and the target device in order to obtain location related measurements or a location estimate or to transfer assistance data. A single LPP session is used to support a single location request (e.g., for a single MT-LR, MO-LR or NI-LR). Multiple LPP sessions can be used between the same endpoints to support multiple different location requests (as required by TS 23.271 [3]). Each LPP session comprises one or more LPP transactions, with each LPP transaction performing a single operation (capability exchange, assistance data transfer, or location information transfer). In E-UTRAN and NG-RAN, the LPP transactions are realized as LPP procedures. The instigator of an LPP session will always instigate the first LPP transaction, but subsequent transactions may be instigated by either end. LPP transactions within a session may occur serially or in parallel. LPP transactions are indicated at the LPP protocol level with a transaction ID in order to associate messages with one another (e.g., request and response). + +Messages within a transaction are linked by a common transaction identifier. + +### 4.1.3 LPP Position Methods + +Internal LPP positioning methods and associated signalling content are defined in this specification. + +This version of the specification defines OTDOA (based on LTE signals), A-GNSS, E-CID (based on LTE signals), Sensor, TBS, WLAN, Bluetooth, NR E-CID, NR DL-TDOA, NR DL-AoD and NR Multi-RTT positioning methods. + +### 4.1.4 LPP Messages + +Each LPP transaction involves the exchange of one or more LPP messages between the location server and the target device. The general format of an LPP message consists of a set of common fields followed by a body. The body (which may be empty) contains information specific to a particular message type. Each message type contains information specific to one or more positioning methods and/or information common to all positioning methods. + +The common fields are as follows: + +| Field | Role | +|----------------------|-------------------------------------------------------------------------------| +| Transaction ID | Identify messages belonging to the same transaction | +| Transaction End Flag | Indicate when a transaction (e.g. one with periodic responses) has ended | +| Sequence Number | Enable detection of a duplicate LPP message at a receiver | +| Acknowledgement | Enable an acknowledgement to be requested and/or returned for any LPP message | + +NOTE: Use of the Transaction ID and Transaction End fields conform to the procedures in clause 5 and are independent of the means used to transport LPP messages (e.g., whether using a NAS MO-LR Request, NAS Generic Transport or user-plane solution). + +The following message types are defined: + +- Request Capabilities; +- Provide Capabilities; +- Request Assistance Data; +- Provide Assistance Data; +- Request Location Information; +- Provide Location Information; +- Abort; +- Error. + +## 4.2 Common LPP Session Procedure + +The purpose of this procedure is to support an LPP session comprising a sequence of LPP transactions. The procedure is described in Figure 4.2-1. + +![Sequence diagram of the LPP Session Procedure between Endpoint A and Endpoint B. The diagram shows four steps: 1. Endpoint A sends an LPP Message (Transaction ID = j, Body) to Endpoint B. 2. Endpoint A and B exchange Additional LPP Messages (Transaction ID = j, Body) via dashed arrows. 3. Endpoint A and B exchange LPP Messages (Transaction ID = k, Body) via dashed arrows. 4. Endpoint A sends a final LPP Message (Transaction ID = N, Body) to Endpoint B.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant A as Endpoint A + participant B as Endpoint B + Note right of A: 1. LPP Message (Transaction ID = j, Body) + A->>B: 1. LPP Message (Transaction ID = j, Body) + Note right of B: 2. Additional LPP Messages (Transaction ID = j, Body) + B-->>A: 2. Additional LPP Messages (Transaction ID = j, Body) + Note right of A: 3. LPP Messages (Transaction ID = k, Body) + A-->>B: 3. LPP Messages (Transaction ID = k, Body) + Note right of B: 4. LPP Message (Transaction ID = N, Body) + B-->>A: 4. LPP Message (Transaction ID = N, Body) + +``` + +Sequence diagram of the LPP Session Procedure between Endpoint A and Endpoint B. The diagram shows four steps: 1. Endpoint A sends an LPP Message (Transaction ID = j, Body) to Endpoint B. 2. Endpoint A and B exchange Additional LPP Messages (Transaction ID = j, Body) via dashed arrows. 3. Endpoint A and B exchange LPP Messages (Transaction ID = k, Body) via dashed arrows. 4. Endpoint A sends a final LPP Message (Transaction ID = N, Body) to Endpoint B. + +**Figure 4.2-1 LPP Session Procedure** + +1. Endpoint A, which may be either the target or the server, initiates an LPP session by sending an LPP message for an initial LPP transaction $j$ to the other endpoint B (which has an opposite role to A). +2. Endpoints A and B may exchange further messages to continue the transaction started in step 1. +3. Either endpoint may instigate further transactions by sending additional LPP messages. +4. A session is terminated by a final transaction $N$ in which LPP messages will be exchanged between the two endpoints. + +Within each transaction, all constituent messages shall contain the same transaction identifier. The last message sent in each transaction shall have the IE *endTransaction* set to TRUE. Transactions that occur in parallel shall use different transaction IDs; transaction IDs for completed transactions may be reused at any time after the final message of the previous transaction with the same ID is known to have been received. + +## 4.3 LPP Transport + +### 4.3.1 Transport Layer Requirements + +LPP requires reliable, in-sequence delivery of LPP messages from the underlying transport layers. This clause describes the transport capabilities that are available within LPP. A UE implementing LPP for the control-plane solution shall support LPP reliable transport (including all three of duplicate detection, acknowledgement, and retransmission). + +LPP reliable transport functionality is not used in the user-plane solution. + +The following requirements in clauses 4.3.2, 4.3.3, and 4.3.4 for LPP reliable transport apply only when the capability is supported. + +### 4.3.2 LPP Duplicate Detection + +A sender shall include a sequence number in all LPP messages sent for a particular location session. The sequence number shall be distinct for different LPP messages sent in the same direction in the same location session (e.g., may start at zero in the first LPP message and increase monotonically in each succeeding LPP message). Sequence numbers used in the uplink and downlink are independent (e.g., can be the same). + +A receiver shall record the most recent received sequence number for each location session. If a message is received carrying the same sequence number as that last received for the associated location session, it shall be discarded. Otherwise (i.e., if the sequence number is different or if no sequence number was previously received or if no sequence number is included), the message shall be processed. + +Sending and receiving sequence numbers shall be deleted in a server when the associated location session is terminated and shall be deleted in a target device when there has been no activity for a particular location session for 10 minutes. + +NOTE: For LPP control-plane use, a target device can be aware of a location session from information provided at the NAS level for downlink transport of an LPP message. + +### 4.3.3 LPP Acknowledgement + +#### 4.3.3.1 General + +Each LPP message may carry an acknowledgement request and/or an acknowledgement indicator. A LPP message including an acknowledgement request (i.e., that include the IE *ackRequested* set to TRUE) shall also include a sequence number. Upon reception of an LPP message which includes the IE *ackRequested* set to TRUE, a receiver returns an LPP message with an acknowledgement response (i.e., that includes the *ackIndicator* IE set to the same sequence number of the message being acknowledged). An acknowledgement response may contain no LPP message body (in which case only the sequence number being acknowledged is significant); alternatively, the acknowledgement may be sent in an LPP message along with an LPP message body. An acknowledgement is returned for each received LPP message that requested an acknowledgement including any duplicate(s). Once a sender receives an acknowledgement for an LPP message, and provided any included sequence number is matching, it is permitted to send the next LPP message. No message reordering is needed at the receiver since this stop-and-wait method of sending ensures that messages normally arrive in the correct order. + +When an LPP message is transported via a NAS MO-LR request, the message does not request an acknowledgement. + +#### 4.3.3.2 Procedure related to Acknowledgement + +Figure 4.3.3.2-1 shows the procedure related to acknowledgement. + +![Sequence diagram illustrating the LPP Acknowledgement procedure between two endpoints, A and B. The diagram shows a horizontal timeline for each endpoint. Endpoint A sends a message to Endpoint B, and Endpoint B responds with an acknowledgement. The diagram is partially obscured by a black rectangle at the top.](a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg) + +The diagram illustrates the LPP Acknowledgement procedure between two endpoints, A and B. It is a sequence diagram with two vertical lifelines. Endpoint A (left) sends a message to Endpoint B (right). Endpoint B receives the message and sends a response back to Endpoint A. The diagram is partially obscured by a black rectangle at the top, but the basic flow of message exchange is visible. + +Sequence diagram illustrating the LPP Acknowledgement procedure between two endpoints, A and B. The diagram shows a horizontal timeline for each endpoint. Endpoint A sends a message to Endpoint B, and Endpoint B responds with an acknowledgement. The diagram is partially obscured by a black rectangle at the top. + +Figure 4.3.3.2-1: LPP Acknowledgement procedure + +1. Endpoint A sends an LPP message *N* to Endpoint B which includes the IE *ackRequested* set to TRUE and a sequence number. +2. If LPP message *N* is received and Endpoint B is able to decode the *ackRequested* value and sequence number, Endpoint B shall return an acknowledgement for message *N*. The acknowledgement shall contain the IE *ackIndicator* set to the same sequence number as that in message *N*. +3. When the acknowledgement for LPP message *N* is received and provided the included *ackIndicator* IE matches the sequence number sent in message *N*, Endpoint A sends the next LPP message *N+1* to Endpoint B when this message is available. + +### 4.3.4 LPP Retransmission + +#### 4.3.4.1 General + +This capability builds on the acknowledgement and duplicate detection capabilities. When an LPP message which requires acknowledgement is sent and not acknowledged, it is resent by the sender following a timeout period up to three times. If still unacknowledged after that, the sender aborts all LPP activity for the associated session. The timeout period is determined by the sender implementation but shall not be less than a minimum value of 250 ms. + +In addition, for NB-IoT the timeout period may be determined by the sender implementation based on e.g., the coverage level of the UE. + +#### 4.3.4.2 Procedure related to Retransmission + +Figure 4.3.4.2-1 shows the procedure related to retransmission when combined with acknowledgement and duplicate detection. + +![Sequence diagram illustrating the LPP Retransmission procedure between Endpoint A and Endpoint B.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +The diagram shows a sequence of interactions between two endpoints, A and B, represented by vertical lines. A horizontal arrow points from Endpoint A to Endpoint B, representing the initial LPP message. Above the diagram is a large black rectangular area. Below the diagram, a horizontal line with an arrow pointing to the right indicates the sequence of steps described in the text. + +Sequence diagram illustrating the LPP Retransmission procedure between Endpoint A and Endpoint B. + +**Figure 4.3.4.2-1: LPP Retransmission procedure** + +1. Endpoint A sends an LPP message $N$ to Endpoint B for a particular location session and includes a request for acknowledgement along with a sequence number. +2. If LPP message $N$ is received and Endpoint B is able to decode the *ackRequested* value and sequence number (regardless of whether the message body can be correctly decoded), Endpoint B shall return an acknowledgement for message $N$ . If the acknowledgement is received by Endpoint A (such that the acknowledged message can be identified and sequence numbers are matching), Endpoint A skips steps 3 and 4. +3. If the acknowledgement in step 2 is not received after a timeout period, Endpoint A shall retransmit LPP message $N$ and shall include the same sequence number as in step 1. +4. If LPP message $N$ in step 3 is received and Endpoint B is able to decode the *ackRequested* value and sequence number (regardless of whether the message body can be correctly decoded and whether or not the message is considered a duplicate), Endpoint B shall return an acknowledgement. Steps 3 may be repeated one or more times if the acknowledgement in step 4 is not received after a timeout period by Endpoint A. If the acknowledgement in step 4 is still not received after sending three retransmissions, Endpoint A shall abort all procedures and activity associated with LPP support for the particular location session. +5. Once an acknowledgement in step 2 or step 4 is received, Endpoint A sends the next LPP message $N+1$ for the location session to Endpoint B when this message is available. + +### 4.3.5 LPP Message Segmentation + +An LPP message body may be sent in several shorter LPP messages instead of one long LPP message to deliver a large amount of information (e.g., in case the LPP message size exceeds the maximum message size supported by lower layers). When a sender employs LPP message segmentation, the sender shall include the IE *SegmentationInfo* in each LPP message segment. The sender shall indicate in all but the final message segment that more messages are on the way. + +When a receiver receives an LPP message indicating that more messages are on the way, the receiver may store the LPP message. If the receiver receives a subsequent LPP message for the same session and transaction ID, the receiver shall assume that the new LPP message continues the segmentation of the earlier message and may store the new message if the new message indicates that more messages are on the way. If the new message indicates that no more messages are on the way, the receiver shall assume that message segmentation is complete and shall process the new message and any stored message segments for the same session and transaction ID. + +The reliable transport rules specified in clause 4.3.2, 4.3.3, and 4.3.4 apply to each individual LPP message segment, independently of the value of the IE *SegmentationInfo*. + +The rules for setting the common fields of the LPP message specified in clause 4.1.4 (Transaction ID, Transaction End Flag, Sequence Number, Acknowledgment) apply to each individual LPP message segment, independently of the value of the IE *SegmentationInfo*. + +![Diagram illustrating the LPP Message Segmentation procedure. It shows two vertical timelines representing Endpoint A (left) and Endpoint B (right). A horizontal arrow points from Endpoint A to Endpoint B, representing the transmission of an LPP message segment. The arrow is positioned such that it spans across the gap between the two timelines, indicating the flow of data from A to B.](9b686adccf125267a013fa25721231a3_img.jpg) + +The diagram shows two vertical lines representing the timelines of Endpoint A (left) and Endpoint B (right). A horizontal arrow points from Endpoint A to Endpoint B, representing the transmission of an LPP message segment. The arrow is positioned such that it spans across the gap between the two timelines, indicating the flow of data from A to B. Above the timelines, there are two black rectangular blocks, one on each side, which likely represent the application or protocol layers involved in the segmentation process. + +Diagram illustrating the LPP Message Segmentation procedure. It shows two vertical timelines representing Endpoint A (left) and Endpoint B (right). A horizontal arrow points from Endpoint A to Endpoint B, representing the transmission of an LPP message segment. The arrow is positioned such that it spans across the gap between the two timelines, indicating the flow of data from A to B. + +**Figure 4.3.5-1: LPP Message Segmentation procedure** + +1. Endpoint A sends an LPP message to Endpoint B for a particular location session and includes the IE *SegmentationInfo* set to *moreMessagesOnTheWay* to indicate that this is one of many LPP message segments used to deliver the entire LPP message body. +2. Endpoint A may send one or more additional LPP messages to Endpoint B with the IE *SegmentationInfo* set to *moreMessagesOnTheWay* to continue delivering the segmented LPP message. +3. Endpoint A sends the final LPP message segment to Endpoint B and includes the IE *SegmentationInfo* set to *noMoreMessages* to indicate that this is the final LPP message segment. Endpoint B assumes that the complete LPP message body has been received. + +## 5 LPP Procedures + +### 5.1 Procedures related to capability transfer + +The purpose of the procedures that are grouped together in this clause is to enable the transfer of capabilities from the target device to the server. Capabilities in this context refer to positioning and protocol capabilities related to LPP and the positioning methods supported by LPP. + +These procedures instantiate the Capability Transfer transaction from TS 36.305 [2] and TS 38.305 [40]. + +#### 5.1.1 Capability Transfer procedure + +The Capability Transfer procedure is shown in Figure 5.1.1-1. + +![Sequence diagram for LPP Capability Transfer procedure](15e4a144a88176b71ea3eff2722253b0_img.jpg) + +A sequence diagram illustrating the LPP Capability Transfer procedure. It features two vertical lifelines representing the server (left) and the target (right). The interaction consists of two messages: 1. A message arrow points from the server's lifeline to the target's lifeline. 2. A message arrow points from the target's lifeline back to the server's lifeline. + +Sequence diagram for LPP Capability Transfer procedure + +Figure 5.1.1-1: LPP Capability Transfer procedure + +1. The server sends a *RequestCapabilities* message to the target. The server may indicate the types of capability needed. +2. The target responds with a *ProvideCapabilities* message to the server. The capabilities shall correspond to any capability types specified in step 1. This message shall include the *endTransaction* IE set to TRUE. + +#### 5.1.2 Capability Indication procedure + +The Capability Indication procedure allows the target to provide unsolicited capabilities to the server and is shown in Figure 5.1.2-1. + +![Sequence diagram for LPP Capability Indication procedure](bdcc4eb452fcc6ba091949b77546a6d4_img.jpg) + +A sequence diagram illustrating the LPP Capability Indication procedure. It features two vertical lifelines representing the server (left) and the target (right). The interaction consists of a single message: 1. A message arrow points from the target's lifeline to the server's lifeline. + +Sequence diagram for LPP Capability Indication procedure + +Figure 5.1.2-1: LPP Capability Indication procedure + +1. The target sends a *ProvideCapabilities* message to the server. This message shall include the *endTransaction* IE set to TRUE. + +### 5.1.3 Reception of LPP Request Capabilities + +Upon receiving a *RequestCapabilities* message, the target device shall generate a *ProvideCapabilities* message as a response. + +The target device shall: + +- 1> for each positioning method for which a request for capabilities is included in the message: + - 2> if the target device supports this positioning method: + - 3> include the capabilities of the device for that supported positioning method in the response message; +- 1> set the IE *LPP-TransactionID* in the response message to the same value as the IE *LPP-TransactionID* in the received message; +- 1> deliver the response message to lower layers for transmission. + +### 5.1.4 Transmission of LPP Provide Capabilities + +When triggered to transmit a *ProvideCapabilities* message, the target device shall: + +- 1> for each positioning method whose capabilities are to be indicated: + - 2> set the corresponding IE to include the device's capabilities; + - 2> if OTDOA capabilities are to be indicated: + - 3> include the IE *supportedBandListEUTRA*; +- 1> deliver the response to lower layers for transmission. + +## 5.2 Procedures related to Assistance Data Transfer + +The purpose of the procedures in this clause is to enable the target to request assistance data from the server to assist in positioning, and to enable the server to transfer assistance data to the target in the absence of a request. + +These procedures instantiate the Assistance Data Transfer transaction from TS 36.305 [2] and TS 38.305 [40]. + +### 5.2.1 Assistance Data Transfer procedure + +The Assistance Data Transfer procedure is shown in Figure 5.2.1-1. + +![Sequence diagram illustrating the LPP Assistance data transfer procedure between a target device and a server.](d5918cee231b536f20789a18d861fae3_img.jpg) + +The diagram shows a sequence of messages between two entities, represented by rectangular boxes at the top. The left entity (Target) sends a solid horizontal arrow labeled 'RequestAssistanceData' to the right entity (Server). The Server responds with a solid horizontal arrow labeled 'ProvideAssistanceData' back to the Target. Below these, a dashed horizontal arrow points from the Server to the Target, representing a subsequent message or response. + +Sequence diagram illustrating the LPP Assistance data transfer procedure between a target device and a server. + +**Figure 5.2.1-1: LPP Assistance data transfer procedure** + +1. The target sends a *RequestAssistanceData* message to the server. +2. The server responds with a *ProvideAssistanceData* message to the target containing assistance data. The transferred assistance data should match or be a subset of the assistance data requested in step 1. The server may + +also provide any not requested information that it considers useful to the target. If step 3 does not occur, this message shall set the *endTransaction* IE to TRUE. + +3. The server may transmit one or more additional *ProvideAssistanceData* messages to the target containing further assistance data. The transferred assistance data should match or be a subset of the assistance data requested in step 1. The server may also provide any not requested information that it considers useful to the target. The last message shall include the *endTransaction* IE set to TRUE. + +### 5.2.1a Periodic Assistance Data Transfer procedure + +The Periodic Assistance Data Transfer procedure is shown in Figure 5.2.1a-1. This procedure enables a target to request a server to send assistance data periodically. + +NOTE 1: In this version of the specification, periodic assistance data transfer is supported for HA GNSS (e.g., RTK) and NR DL-TDOA positioning only. + +![A large black rectangular redaction box covering the entire area where Figure 5.2.1a-1 would normally be displayed. Below the box, there are two short vertical lines and a small horizontal line segment, likely artifacts from the redaction process.](f2ea0f64a770b22b902820457d262265_img.jpg) + +A large black rectangular redaction box covering the entire area where Figure 5.2.1a-1 would normally be displayed. Below the box, there are two short vertical lines and a small horizontal line segment, likely artifacts from the redaction process. + +**Figure 5.2.1a-1: LPP Periodic Assistance data transfer procedure** + +1. The target sends a *RequestAssistanceData* message to the server using some available *transactionID* T1. The message contains a *periodicSessionID* S (different to any other *periodicSessionID* currently in use between the target and server) in the IE *CommonIEsRequestAssistanceData*. The message also includes a positioning method specific assistance data request element (e.g., IE *A-GNSS-RequestAssistanceData*) identifying the type of assistance data being requested together with desired periodicity conditions for sending it and a duration for ending the assistance data transfer (e.g., in IE *GNSS-PeriodicAssistDataReq*). +2. The server responds with a *ProvideAssistanceData* message to the target. The message uses the *transactionID* T1 in step 1 and indicates the end of this transaction. The message contains the *periodicSessionID* S in IE *CommonIEsProvideAssistanceData*. If the request can be supported, the message contains the control parameters in the positioning method specific assistance data (e.g., IE *A-GNSS-ProvideAssistanceData*) which may confirm or redefine the type of assistance data or periodicity parameters requested at step 1 (e.g., in IE *GNSS-PeriodicAssistData*). If the target requested non-periodic assistance data in addition to the periodic assistance data in step 1, the *ProvideAssistanceData* message may also include the non-periodic assistance data in this step 2 (but not any periodic assistance data). +If the request cannot be supported (fully or partly), an error reason is provided in the positioning method specific IE (e.g., IE *A-GNSS-Error*). If the request cannot even partly be supported remaining steps are then not performed. + +NOTE 2: The target device infers from an absence of the *periodicSessionID* that the location server does not support periodic assistance data delivery. In that case, the target device does not expect the Data Transaction (Steps 3-7). + +3. When the first periodic message is available, the server sends an unsolicited *ProvideAssistanceData* message to the target containing the *periodicSessionID* S and the periodic assistance data confirmed in step 2. The message uses some available *transactionID* T2 that may be different to T1. + +NOTE 3: The positioning method specific control parameters (e.g., IE *GNSS-PeriodicAssistData*) are not included in the data transaction. + +4. The server may continue to send further *ProvideAssistanceData* messages to the target containing the periodic assistance data confirmed or redefined in step 2 when each additional periodicity condition occurs. + +NOTE 4: The target device expects a *ProvideAssistanceData* messages at the in Step 2 confirmed interval(s). If some or all of the assistance data is not available at each periodic interval, an error indication is provided in the positioning method specific IE (e.g., IE *A-GNSS-Error*). + +5. If the target requires the session to end, the target sends an *Abort* message to the server for transaction T2 that may optionally include an *abortCause*. Remaining steps are then omitted. +6. If the server requires the session to end, the server sends an *Abort* message to the target for transaction T2 that may optionally include an *abortCause*. Remaining steps are then omitted. +7. When the duration or other conditions for ending the periodic assistance data transfer occur, the last *ProvideAssistanceData* message transferred indicates the end of transaction T2. + +### 5.2.1b Periodic Assistance Data Transfer with Update procedure + +![Sequence diagram for LPP Periodic Assistance data transfer with update procedure. It shows two lifelines. The left lifeline sends a message to the right lifeline. The right lifeline has a self-call (indicated by a bracket) and then sends a response message back to the left lifeline.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` +sequenceDiagram + participant Target + participant Server + Note left of Target: + Target->>Server: RequestAssistanceData + Note right of Server: + Server-->>Target: ProvideAssistanceData +``` + +Sequence diagram for LPP Periodic Assistance data transfer with update procedure. It shows two lifelines. The left lifeline sends a message to the right lifeline. The right lifeline has a self-call (indicated by a bracket) and then sends a response message back to the left lifeline. + +**Figure 5.2.1b-1: LPP Periodic Assistance data transfer with update procedure** + +1. Steps 1-2 and optionally steps 3-4 are performed for the Periodic Assistance Data Transfer procedure in clause 5.2.1a with the following exceptions: + - The *RequestAssistanceData* message in step 1 indicates the update capabilities of the target device. + - The *ProvideAssistanceData* message in step 2 indicates the update capabilities of the target device which are supported by the server. +2. If the target device changes its primary cell and if the update capabilities of the target device supported by the server in step 1 include update of a primary cell ID, the target device sends a *RequestAssistanceData* message to the server using some available *transactionID* T3, which is different from T2 (previously used in step 2). The message contains the *periodicSessionID* S (previously used in step 1) and the new primary cell ID in the IE *CommonIEsRequestAssistanceData*. +3. The server responds with a *ProvideAssistanceData* message to the target. The message uses the *transactionID* T3 in step 2 and indicates the end of this transaction. The message contains the *periodicSessionID* S in IE *CommonIEsProvideAssistanceData*. Steps 2-3 are repeated each time the target device changes its primary cell. +4. Steps 4-7 are performed for the Periodic Assistance Data Transfer procedure in clause 5.2.1a. + +### 5.2.2 Assistance Data Delivery procedure + +The Assistance Data Delivery procedure allows the server to provide unsolicited assistance data to the target and is shown in Figure 5.2.2-1. + +![Sequence diagram showing LPP Assistance data transfer procedure between two entities. Two vertical lifelines are shown. Two arrows point from the right lifeline to the left lifeline: a solid arrow on top and a dashed arrow below it.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant Target + participant Server + Server->>Target: ProvideAssistanceData + Server-->>Target: ProvideAssistanceData (optional) + +``` + +Sequence diagram showing LPP Assistance data transfer procedure between two entities. Two vertical lifelines are shown. Two arrows point from the right lifeline to the left lifeline: a solid arrow on top and a dashed arrow below it. + +**Figure 5.2.2-1: LPP Assistance data transfer procedure** + +1. The server sends a *ProvideAssistanceData* message to the target containing assistance data. If step 2 does not occur, this message shall set the *endTransaction* IE to TRUE. +2. The server may transmit one or more additional *ProvideAssistanceData* messages to the target containing additional assistance data. The last message shall include the *endTransaction* IE set to TRUE. + +### 5.2.2a Periodic Assistance Data Delivery procedure + +The Periodic Assistance Data Delivery procedure allows the server to provide unsolicited periodic assistance data to the target and is shown in Figure 5.2.2a-1. + +NOTE 1: In this version of the specification, periodic assistance data delivery is supported for HA GNSS (e.g., RTK) and NR DL-TDOA positioning only. + +![A large black rectangular area representing a redacted diagram. Below the rectangle, there are two vertical lines and a small horizontal line segment, which are likely remnants of the original diagram's structure.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +A large black rectangular area representing a redacted diagram. Below the rectangle, there are two vertical lines and a small horizontal line segment, which are likely remnants of the original diagram's structure. + +**Figure 5.2.2a-1: LPP Periodic Assistance data delivery procedure** + +1. The server sends a *ProvideAssistanceData* message to the target using some available *transactionID* T1 and indicates the end of this transaction. The message contains a *periodicSessionID* S (different to any other *periodicSessionID* currently in use between the server and target) in the IE *CommonEsProvideAssistanceData*. The message includes positioning method specific assistance data control parameters (e.g., in IE *A-GNSS-ProvideAssistanceData*) identifying the type of periodic assistance data being delivered together with periodicity conditions for sending it and a duration for ending the assistance data delivery (e.g., in IE *GNSS-PeriodicAssistData*). The *ProvideAssistanceData* message may also include non-periodic assistance data (but not any periodic assistance data). +2. When the first periodic message is available, the server sends an unsolicited *ProvideAssistanceData* message to the target containing the *periodicSessionID* S and the periodic assistance data announced in step 1. The message uses some available *transactionID* T2 that may be different to T1. + +NOTE 2: The positioning method specific control parameters (e.g., IE *GNSS-PeriodicAssistData*) are not included in the data transaction. + +3. The server may continue to send further *ProvideAssistanceData* messages to the target containing the periodic assistance data announced in step 2 when each additional periodicity condition occurs. + +NOTE3: The target device expects a *ProvideAssistanceData* messages at the in Step 2 announced interval(s). If some or all of the assistance data is not available at each periodic interval, an error indication is provided in the positioning method specific IE (e.g., IE *A-GNSS-Error*). + +4. If the target requires the session to end, the target sends an *Abort* message to the server for transaction T2 that may optionally include an *abortCause*. Remaining steps are then omitted. +5. If the server requires the session to end, the server sends an *Abort* message to the target for transaction T2 that may optionally include an *abortCause*. Remaining steps are then omitted. +6. When the duration or other conditions for ending the periodic assistance data transfer occur, the last *ProvideAssistanceData* message transferred indicates the end of transaction T2. + +### 5.2.3 Transmission of LPP Request Assistance Data + +When triggered to transmit a *RequestAssistanceData* message, the target device shall: + +- 1> set the IEs for the positioning-method-specific request for assistance data to request the data indicated by upper layers. + +### 5.2.4 Reception of LPP Provide Assistance Data + +Upon receiving a *ProvideAssistanceData* message, the target device shall: + +- 1> for each positioning method contained in the message: +- 2> deliver the related assistance data to upper layers. + +## 5.3 Procedures related to Location Information Transfer + +The purpose of the procedures in this clause is to enable the server to request location measurement data and/or a location estimate from the target, and to enable the target to transfer location measurement data and/or a location estimate to a server in the absence of a request. + +These procedures instantiate the Location Information Transfer transaction in TS 36.305 [2] and TS 38.305 [40]. + +NOTE: The service layer (e.g. NAS or OMA SUPL ULP) would be used to transfer information associated with a location request from a target to a server (MO-LR). + +### 5.3.1 Location Information Transfer procedure + +The Location Information Transfer procedure is shown in Figure 5.3.1-1. + +![Sequence diagram illustrating the LPP Location Information Transfer procedure. It shows two vertical lifelines representing a server and a target. The server sends a 'RequestLocationInformation' message (solid line with arrow) to the target. The target responds with 'LocationInformation' (solid line with arrow) and 'AssistanceData' (dashed line with arrow) back to the server.](6f90e8489d3449ddab9b5773db240a16_img.jpg) + +``` +sequenceDiagram + participant Server + participant Target + Note left of Server: Server sends RequestLocationInformation + Server->>Target: RequestLocationInformation + Note right of Target: Target responds with LocationInformation and AssistanceData + Target-->>Server: LocationInformation + Target-->>Server: AssistanceData +``` + +Sequence diagram illustrating the LPP Location Information Transfer procedure. It shows two vertical lifelines representing a server and a target. The server sends a 'RequestLocationInformation' message (solid line with arrow) to the target. The target responds with 'LocationInformation' (solid line with arrow) and 'AssistanceData' (dashed line with arrow) back to the server. + +**Figure 5.3.1-1: LPP Location Information transfer procedure** + +1. The server sends a *RequestLocationInformation* message to the target to request location information, indicating the type of location information needed and potentially the associated QoS. + +2. The target sends a *ProvideLocationInformation* message to the server to transfer location information. The location information transferred should match or be a subset of the location information requested in step 1 unless the server explicitly allows additional location information. If step 3 does not occur, this message shall set the *endTransaction* IE to TRUE. +3. If requested in step 1, the target sends additional *ProvideLocationInformation* messages to the server to transfer location information. The location information transferred should match or be a subset of the location information requested in step 1 unless the server explicitly allows additional location information. The last message shall include the *endTransaction* IE set to TRUE. + +### 5.3.2 Location Information Delivery procedure + +The Location Information Delivery allows the target to provide unsolicited location information to the server. The procedure is shown in Figure 5.3.2-1. + +![Sequence diagram illustrating the LPP Location Information Delivery procedure. Two vertical lifelines represent the Target (left) and the Server (right). The Target sends a solid horizontal arrow message to the Server. Below this, a dashed horizontal arrow message is shown from the Target to the Server, representing additional ProvideLocationInformation messages. The Server's lifeline has a solid vertical line and a dashed vertical line, indicating processing or response phases.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +Sequence diagram illustrating the LPP Location Information Delivery procedure. Two vertical lifelines represent the Target (left) and the Server (right). The Target sends a solid horizontal arrow message to the Server. Below this, a dashed horizontal arrow message is shown from the Target to the Server, representing additional ProvideLocationInformation messages. The Server's lifeline has a solid vertical line and a dashed vertical line, indicating processing or response phases. + +**Figure 5.3.2-1: LPP Location Information Delivery procedure** + +1. The target sends a *ProvideLocationInformation* message to the server to transfer location information. If step 2 does not occur, this message shall set the *endTransaction* IE to TRUE. +2. The target may send one or more additional *ProvideLocationInformation* messages to the server containing additional location information data. The last message shall include the *endTransaction* IE set to TRUE. + +### 5.3.3 Reception of Request Location Information + +Upon receiving a *RequestLocationInformation* message, the target device shall: + +- 1> if the requested information is compatible with the target device capabilities and configuration: + - 2> include the requested information in a *ProvideLocationInformation* message; + - 2> set the IE *LPP-TransactionID* in the response to the same value as the IE *LPP-TransactionID* in the received message; + - 2> deliver the *ProvideLocationInformation* message to lower layers for transmission. +- 1> otherwise: + - 2> if one or more positioning methods are included that the target device does not support: + - 3> continue to process the message as if it contained only information for the supported positioning methods; + - 3> handle the signaling content of the unsupported positioning methods by LPP error detection as in 5.4.3. + +### 5.3.4 Transmission of Provide Location Information + +When triggered to transmit *ProvideLocationInformation* message, the target device shall: + +- 1> for each positioning method contained in the message: + - 2> set the corresponding IE to include the available location information; +- 1> deliver the response to lower layers for transmission. + +## 5.4 Error Handling Procedures + +### 5.4.1 General + +This clause describes how a receiving entity (target device or location server) behaves in cases when it receives erroneous or unexpected data or detects that certain data are missing. + +### 5.4.2 Procedures related to Error Indication + +Figure 5.4.2-1 shows the Error indication procedure. + +![Sequence diagram illustrating the LPP Error Indication procedure. It shows two lifelines, Endpoint A and Endpoint B. A solid arrow points from Endpoint A to Endpoint B, representing the initial LPP message. A dashed arrow points from Endpoint B back to Endpoint A, representing the Error message response.](f1cbfa3fc27f58581615654fec4335d8_img.jpg) + +``` + +sequenceDiagram + participant A as Endpoint A + participant B as Endpoint B + Note right of A: [Black Box] + A->>B: LPP message + Note right of B: [White Box] + B-->>A: Error message + +``` + +Sequence diagram illustrating the LPP Error Indication procedure. It shows two lifelines, Endpoint A and Endpoint B. A solid arrow points from Endpoint A to Endpoint B, representing the initial LPP message. A dashed arrow points from Endpoint B back to Endpoint A, representing the Error message response. + +Figure 5.4.2-1: LPP Error Indication procedure + +1. Endpoint A sends an LPP message to Endpoint B. +2. Endpoint B determines that the LPP message in step 1 contains an error. Endpoint B returns an *Error* message to Endpoint A indicating the error or errors and discards the message in step 1. If Endpoint B is able to determine that the erroneous LPP message in step 1 is an LPP *Error* or *Abort* Message, Endpoint B discards the message in step 1 without returning an *Error* message to Endpoint A. + +### 5.4.3 LPP Error Detection + +Upon receiving any LPP message, the receiving entity shall attempt to decode the message and verify the presence of any errors and: + +- 1> if decoding errors are encountered: + - 2> if the receiver can not determine that the received message is an LPP *Error* or *Abort* message: + - 3> return an LPP *Error* message to the sender and include the received *LPP-TransactionID*, if this was decoded, and type of error; + - 3> if the receiver can determine the session and the *LPP-TransactionID* and the received message includes the IE *SegmentationInfo* and the receiver has previously stored message segments for this session and *LPP-TransactionID*: + - 4> discard all stored LPP message segments for this session and *LPP-TransactionID*; + - 3> discard the received message and stop the error detection procedure; + +- 1> if the message is a duplicate of a previously received message: + - 2> discard the message and stop the error detection procedure; +- 1> if the *LPP-TransactionID* matches the *LPP-TransactionID* for a procedure that is still ongoing for the same session and the message type is invalid for the current state of the procedure: + - 2> abort the ongoing procedure; + - 2> return an LPP *Error* message to the sender and include the received transaction ID and type of error; + - 2> if the message includes the IE *SegmentationInfo* and the receiver has previously stored message segments for this session and *LPP-TransactionID*: + - 3> discard all stored LPP message segments for this session and *LPP-TransactionID*; + - 2> discard the message and stop the error detection procedure; +- 1> if the message includes the IE *SegmentationInfo*: + - 2> if the receiver has previously stored LPP message segments for this session and *LPP-TransactionID*: + - 3> if the received message type is different to the stored message type: + - 4> return an LPP *Error* message to the sender and include the received transaction ID and type of error; + - 4> discard the message and all stored LPP message segments for this session and *LPP-TransactionID* and stop the error detection procedure; + - 2> if the IE *SegmentationInfo* has the value *moreMessagesOnTheWay*: + - 3> store the received message; + - NOTE: As an implementation option, the receiver of an LPP Provide Assistance Data or LPP Provide Location Information message may process the received message segment instead of storing the message. + - 2> if the IE *SegmentationInfo* has the value *noMoreMessages*: + - 3> continue error detection for the received message and any stored LPP message segments for this session and *LPP-TransactionID*; + - 1> if the message type is an LPP *RequestCapabilities* and some of the requested information is not supported: + - 2> return any information that can be provided in a normal response. + - 1> if the message type is an LPP *RequestAssistanceData* or *RequestLocationInformation* and some or all of the requested information is not supported: + - 2> return any information that can be provided in a normal response, which includes indications on other information that is not supported. + +#### 5.4.4 Reception of an LPP Error Message + +Upon receiving an *Error* message, a device shall: + +- 1> abort any ongoing procedure associated with the *LPP-TransactionID* if included in the received message. + +The device may: + +- 1> restart the aborted procedure taking into consideration the returned error information. + +## 5.5 Abort Procedure + +### 5.5.1 General + +The purpose of the abort procedure is to allow the target device or location server to abort an ongoing procedure due to some unexpected event (e.g., cancellation of a location request by an LCS client). It can also be used to stop an ongoing procedure (e.g., periodic location reporting from the target device). + +### 5.5.2 Procedures related to Abort + +Figure 5.5.2-1 shows the Abort procedure. + +![Sequence diagram illustrating the LPP Abort procedure between two endpoints, A and B. Endpoint A (left) sends an Abort message to Endpoint B (right).](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +The diagram is a sequence diagram showing the interaction between two endpoints, A and B, for an LPP Abort procedure. Endpoint A is represented by a box on the left with a black top bar, and Endpoint B is represented by a box on the right with a black top bar. A horizontal line (lifeline) extends downwards from each box. A message arrow points from the lifeline of Endpoint A to the lifeline of Endpoint B. A return message arrow points from the lifeline of Endpoint B back to the lifeline of Endpoint A. A large, light-grey rectangular box is positioned in the center, overlapping the lifelines, representing the ongoing procedure P. + +Sequence diagram illustrating the LPP Abort procedure between two endpoints, A and B. Endpoint A (left) sends an Abort message to Endpoint B (right). + +Figure 5.5.2-1: LPP Abort procedure + +1. A procedure P is ongoing between endpoints A and B. +2. Endpoint A determines that the procedure must be aborted and sends an *Abort* message to Endpoint B carrying the transaction ID for procedure P. Endpoint B aborts procedure P. + +### 5.5.3 Reception of an LPP Abort Message + +Upon receiving an *Abort* message, a device shall: + +- 1) abort any ongoing procedure associated with the transaction ID indicated in the message. + +--- + +## 6 Information Element Abstract Syntax Definition + +### 6.1 General + +The contents of each LPP message is specified in clause 6.2 using ASN.1 to specify the message syntax and using tables when needed to provide further detailed information about the fields specified in the message syntax. + +The ASN.1 in this clause uses the same format and coding conventions as described in Annex A of TS 36.331 [12]. + +Transfer syntax for LPP messages is derived from their ASN.1 definitions by use of Basic Packed Encoding Rules (BASIC-PER), Unaligned Variant, as specified in ITU-T Rec. X.691 [22]. The encoded LPP message always contains a multiple of 8 bits. + +Transfer syntax for LPP IEs is derived from their ASN.1 definitions by use of Basic Packed Encoding Rules (BASIC-PER), Unaligned Variant, as specified in ITU-T Rec. X.691 [22]. The encoded LPP IE always contains a multiple of 8 bits. This applies when a single LPP IE is encoded as the basic production, i.e. for other purposes than encoding the LPP IE within an LPP message. + +The need for fields to be present in a message or an abstract type, i.e., the ASN.1 fields that are specified as OPTIONAL in the abstract notation (ASN.1), is specified by means of comment text tags attached to the OPTIONAL statement in the abstract syntax. The meaning of each tag is specified in table 6.1-1. The use of these tags in the uplink (target to server) direction does not impose any requirements on the server. + +**Table 6.1-1: Meaning of abbreviations used to specify the need for fields to be present** + +| Abbreviation | Meaning | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cond conditionTag | Conditionally present
A field for which the need is specified by means of conditions. For each conditionTag , the need is specified in a tabular form following the ASN.1 segment. In case, according to the conditions, a field is not present, the target takes no action and where applicable shall continue to use the existing value (and/or the associated functionality) unless explicitly stated otherwise in the description of the field itself. | +| Need OP | Optionally present
A field that is optional to signal. For downlink messages, the target is not required to take any special action on absence of the field beyond what is specified in the procedural text or the field description table following the ASN.1 segment. The target behaviour on absence should be captured either in the procedural text or in the field description. | +| Need ON | Optionally present, No action
A field that is optional to signal. If the message is received by the target, and in case the field is absent, the target takes no action and where applicable shall continue to use the existing value (and/or the associated functionality). | +| Need OR | Optionally present, Release
A field that is optional to signal. If the message is received by the target, and in case the field is absent, the target shall discontinue/ stop using/ delete any existing value (and/ or the associated functionality). | + +When specifying information elements which are to be represented by BIT STRINGs, if not otherwise specifically stated in the field 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). + +## 6.2 LPP PDU Structure + +### – *LPP-PDU-Definitions* + +This ASN.1 segment is the start of the LPP PDU definitions. + +``` +-- ASN1START + +LPP-PDU-Definitions +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ASN1STOP +``` + +### – *LPP-Message* + +The *LPP-Message* provides the complete set of information for an invocation or response pertaining to an LPP transaction. + +``` +-- ASN1START + +LPP-Message ::= SEQUENCE { + transactionID LPP-TransactionID OPTIONAL, -- Need ON + endTransaction BOOLEAN, + sequenceNumber SequenceNumber OPTIONAL, -- Need ON + acknowledgement Acknowledgement OPTIONAL, -- Need ON + lpp-MessageBody LPP-MessageBody OPTIONAL -- Need ON +} +``` + +``` + +} + +SequenceNumber ::= INTEGER (0..255) + +Acknowledgement ::= SEQUENCE { + ackRequested BOOLEAN, + ackIndicator SequenceNumber OPTIONAL +} + +-- ASN1STOP + +``` + +| LPP-Message field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| transactionID
This field is omitted if an lpp-MessageBody is not present (i.e. in an LPP message sent only to acknowledge a previously received message) or if it is not available to the transmitting entity (e.g., in an LPP-Error message triggered by a message that could not be parsed). If present, this field shall be ignored at a receiver in an LPP message for which the lpp-MessageBody is not present. | +| endTransaction
This field indicates whether an LPP message is the last message carrying an lpp-MessageBody in a transaction (TRUE) or not last (FALSE). When LPP message segmentation is used, only the final LPP message segment may indicate the end of the transaction. | +| sequenceNumber
This field may be included when LPP operates over the control plane and an lpp-MessageBody is included but shall be omitted otherwise. | +| acknowledgement
This field is included in an LPP acknowledgement and in any LPP message requesting an acknowledgement when LPP operates over the control plane and is omitted otherwise. | +| ackRequested
This field indicates whether an LPP acknowledgement is requested (TRUE) or not (FALSE). A value of TRUE may only be included when an lpp-MessageBody is included. | +| ackIndicator
This field indicates the sequence number of the message being acknowledged. | +| lpp-MessageBody
This field may be omitted in the case the message is sent only to acknowledge a previously received message. | + +## — *LPP-MessageBody* + +The *LPP-MessageBody* identifies the type of an LPP message and contains all LPP information specifically associated with that type. + +``` + +-- ASN1START + +LPP-MessageBody ::= CHOICE { + c1 CHOICE { + requestCapabilities RequestCapabilities, + provideCapabilities ProvideCapabilities, + requestAssistanceData RequestAssistanceData, + provideAssistanceData ProvideAssistanceData, + requestLocationInformation RequestLocationInformation, + provideLocationInformation ProvideLocationInformation, + abort Abort, + error Error, + spare7 NULL, spare6 NULL, spare5 NULL, spare4 NULL, + spare3 NULL, spare2 NULL, spare1 NULL, spare0 NULL + }, + messageClassExtension SEQUENCE {} +} + +-- ASN1STOP + +``` + +## — *LPP-TransactionID* + +The *LPP-TransactionID* identifies a particular LPP transaction and the initiator of the transaction. + +``` + +-- ASN1START + +LPP-TransactionID ::= SEQUENCE { + initiator Initiator, +} + +``` + +``` + +transactionNumber TransactionNumber, +... +} + +Initiator ::= ENUMERATED { + locationServer, + targetDevice, + ... +} + +TransactionNumber ::= INTEGER (0..255) + +-- ASN1STOP + +``` + +## 6.3 Message Body IEs + +### – *RequestCapabilities* + +The *RequestCapabilities* message body in a LPP message is used by the location server to request the target device capability information for LPP and the supported individual positioning methods. + +``` + +-- ASN1START + +RequestCapabilities ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + requestCapabilities-r9 RequestCapabilities-r9-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +RequestCapabilities-r9-IEs ::= SEQUENCE { + commonIEsRequestCapabilities CommonIEsRequestCapabilities OPTIONAL, -- Need ON + a-gnss-RequestCapabilities A-GNSS-RequestCapabilities OPTIONAL, -- Need ON + otdoa-RequestCapabilities OTDOA-RequestCapabilities OPTIONAL, -- Need ON + ecid-RequestCapabilities ECID-RequestCapabilities OPTIONAL, -- Need ON + epdu-RequestCapabilities EPDU-Sequence OPTIONAL, -- Need ON + ..., + [[ sensor-RequestCapabilities-r13 Sensor-RequestCapabilities-r13 OPTIONAL, -- Need ON + tbs-RequestCapabilities-r13 TBS-RequestCapabilities-r13 OPTIONAL, -- Need ON + wlan-RequestCapabilities-r13 WLAN-RequestCapabilities-r13 OPTIONAL, -- Need ON + bt-RequestCapabilities-r13 BT-RequestCapabilities-r13 OPTIONAL -- Need ON + ]], + [[ nr-ECID-RequestCapabilities-r16 NR-ECID-RequestCapabilities-r16 OPTIONAL, -- Need ON + nr-Multi-RTT-RequestCapabilities-r16 + NR-Multi-RTT-RequestCapabilities-r16 + OPTIONAL, -- Need ON + nr-DL-AoD-RequestCapabilities-r16 + NR-DL-AoD-RequestCapabilities-r16 OPTIONAL, -- Need ON + nr-DL-TDOA-RequestCapabilities-r16 + NR-DL-TDOA-RequestCapabilities-r16 OPTIONAL, -- Need ON + nr-UL-RequestCapabilities-r16 NR-UL-RequestCapabilities-r16 OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP + +``` + +### – *ProvideCapabilities* + +The *ProvideCapabilities* message body in a LPP message indicates the LPP capabilities of the target device to the location server. + +``` + +-- ASN1START + +ProvideCapabilities ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + provideCapabilities-r9 ProvideCapabilities-r9-IEs, + +``` + +``` + + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} +} + +ProvideCapabilities-r9-IEs ::= SEQUENCE { + commonIEsProvideCapabilities CommonIEsProvideCapabilities OPTIONAL, + a-gnss-ProvideCapabilities A-GNSS-ProvideCapabilities OPTIONAL, + otdoa-ProvideCapabilities OTDOA-ProvideCapabilities OPTIONAL, + ecid-ProvideCapabilities ECID-ProvideCapabilities OPTIONAL, + epdu-ProvideCapabilities EPDU-Sequence OPTIONAL, + ..., + [[ sensor-ProvideCapabilities-r13 Sensor-ProvideCapabilities-r13 OPTIONAL, + tbs-ProvideCapabilities-r13 TBS-ProvideCapabilities-r13 OPTIONAL, + wlan-ProvideCapabilities-r13 WLAN-ProvideCapabilities-r13 OPTIONAL, + bt-ProvideCapabilities-r13 BT-ProvideCapabilities-r13 OPTIONAL + ]], + [[ nr-ECID-ProvideCapabilities-r16 NR-ECID-ProvideCapabilities-r16 OPTIONAL, + nr-Multi-RTT-ProvideCapabilities-r16 + NR-Multi-RTT-ProvideCapabilities-r16 OPTIONAL, + nr-DL-AoD-ProvideCapabilities-r16 + NR-DL-AoD-ProvideCapabilities-r16 OPTIONAL, + nr-DL-TDOA-ProvideCapabilities-r16 + NR-DL-TDOA-ProvideCapabilities-r16 OPTIONAL, + nr-UL-ProvideCapabilities-r16 NR-UL-ProvideCapabilities-r16 OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +## — *RequestAssistanceData* + +The *RequestAssistanceData* message body in a LPP message is used by the target device to request assistance data from the location server. + +``` + +-- ASN1START + +RequestAssistanceData ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + requestAssistanceData-r9 RequestAssistanceData-r9-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +RequestAssistanceData-r9-IEs ::= SEQUENCE { + commonIEsRequestAssistanceData CommonIEsRequestAssistanceData OPTIONAL, + a-gnss-RequestAssistanceData A-GNSS-RequestAssistanceData OPTIONAL, + otdoa-RequestAssistanceData OTDOA-RequestAssistanceData OPTIONAL, + epdu-RequestAssistanceData EPDU-Sequence OPTIONAL, + ..., + [[ sensor-RequestAssistanceData-r14 + Sensor-RequestAssistanceData-r14 OPTIONAL, + tbs-RequestAssistanceData-r14 TBS-RequestAssistanceData-r14 OPTIONAL, + wlan-RequestAssistanceData-r14 WLAN-RequestAssistanceData-r14 OPTIONAL + ]], + [[ nr-Multi-RTT-RequestAssistanceData-r16 NR-Multi-RTT-RequestAssistanceData-r16 OPTIONAL, + nr-DL-AoD-RequestAssistanceData-r16 NR-DL-AoD-RequestAssistanceData-r16 OPTIONAL, + nr-DL-TDOA-RequestAssistanceData-r16 NR-DL-TDOA-RequestAssistanceData-r16 OPTIONAL + ]], + [[ + bt-RequestAssistanceData-r18 BT-RequestAssistanceData-r18 OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +## ProvideAssistanceData + +The *ProvideAssistanceData* message body in a LPP message is used by the location server to provide assistance data to the target device either in response to a request from the target device or in an unsolicited manner. + +``` +-- ASN1START + +ProvideAssistanceData ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + provideAssistanceData-r9 ProvideAssistanceData-r9-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +ProvideAssistanceData-r9-IEs ::= SEQUENCE { + commonIEsProvideAssistanceData CommonIEsProvideAssistanceData OPTIONAL, -- Need ON + a-gnss-ProvideAssistanceData A-GNSS-ProvideAssistanceData OPTIONAL, -- Need ON + otdoa-ProvideAssistanceData OTDOA-ProvideAssistanceData OPTIONAL, -- Need ON + epdu-ProvideAssistanceData EPDU-Sequence OPTIONAL, -- Need ON + ..., + [[ + sensor-ProvideAssistanceData-r14 Sensor-ProvideAssistanceData-r14 OPTIONAL, -- Need ON + tbs-ProvideAssistanceData-r14 TBS-ProvideAssistanceData-r14 OPTIONAL, -- Need ON + wlan-ProvideAssistanceData-r14 WLAN-ProvideAssistanceData-r14 OPTIONAL, -- Need ON + ]], + [[ + nr-Multi-RTT-ProvideAssistanceData-r16 + NR-Multi-RTT-ProvideAssistanceData-r16 + OPTIONAL, -- Need ON + nr-DL-AoD-ProvideAssistanceData-r16 + NR-DL-AoD-ProvideAssistanceData-r16 OPTIONAL, -- Need ON + nr-DL-TDOA-ProvideAssistanceData-r16 + NR-DL-TDOA-ProvideAssistanceData-r16 + OPTIONAL, -- Need ON + ]], + [[ + bt-ProvideAssistanceData-r18 BT-ProvideAssistanceData-r18 OPTIONAL, -- Need ON + ]] +} + +-- ASN1STOP +``` + +## RequestLocationInformation + +The *RequestLocationInformation* message body in a LPP message is used by the location server to request positioning measurements or a position estimate from the target device. + +``` +-- ASN1START + +RequestLocationInformation ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + requestLocationInformation-r9 RequestLocationInformation-r9-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +RequestLocationInformation-r9-IEs ::= SEQUENCE { + commonIEsRequestLocationInformation + CommonIEsRequestLocationInformation OPTIONAL, -- Need ON + a-gnss-RequestLocationInformation A-GNSS-RequestLocationInformation OPTIONAL, -- Need ON + otdoa-RequestLocationInformation OTDOA-RequestLocationInformation OPTIONAL, -- Need ON + ecid-RequestLocationInformation ECID-RequestLocationInformation OPTIONAL, -- Need ON + epdu-RequestLocationInformation EPDU-Sequence OPTIONAL, -- Need ON + ..., + [[ + sensor-RequestLocationInformation-r13 + Sensor-RequestLocationInformation-r13 + OPTIONAL, -- Need ON + tbs-RequestLocationInformation-r13 TBS-RequestLocationInformation-r13 OPTIONAL, -- Need ON + ]]] +``` + +``` + +wlan-RequestLocationInformation-r13 WLAN-RequestLocationInformation-r13 OPTIONAL, -- Need ON +bt-RequestLocationInformation-r13 BT-RequestLocationInformation-r13 OPTIONAL -- Need ON +]], +[[ nr-ECID-RequestLocationInformation-r16 + NR-ECID-RequestLocationInformation-r16 + OPTIONAL, -- Need ON + nr-Multi-RTT-RequestLocationInformation-r16 + NR-Multi-RTT-RequestLocationInformation-r16 + OPTIONAL, -- Need ON + nr-DL-AoD-RequestLocationInformation-r16 + NR-DL-AoD-RequestLocationInformation-r16 + OPTIONAL, -- Need ON + nr-DL-TDOA-RequestLocationInformation-r16 + NR-DL-TDOA-RequestLocationInformation-r16 + OPTIONAL -- Need ON +]] +} + +-- ASN1STOP + +``` + +#### RequestLocationInformation field descriptions + +##### commonEsRequestLocationInformation + +This field specifies the location information type requested by the location server and optionally other configuration information associated with the requested location information. This field should always be included in this version of the protocol. + +### ProvideLocationInformation + +The *ProvideLocationInformation* message body in a LPP message is used by the target device to provide positioning measurements or position estimates to the location server. + +``` + +-- ASN1START + +ProvideLocationInformation ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + provideLocationInformation-r9 ProvideLocationInformation-r9-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +ProvideLocationInformation-r9-IEs ::= SEQUENCE { + commonIEsProvideLocationInformation CommonIEsProvideLocationInformation OPTIONAL, + a-gnss-ProvideLocationInformation A-GNSS-ProvideLocationInformation OPTIONAL, + otdoa-ProvideLocationInformation OTDOA-ProvideLocationInformation OPTIONAL, + ecid-ProvideLocationInformation ECID-ProvideLocationInformation OPTIONAL, + epdu-ProvideLocationInformation EPDU-Sequence OPTIONAL, + ... + [[ + sensor-ProvideLocationInformation-r13 + Sensor-ProvideLocationInformation-r13 + OPTIONAL, + tbs-ProvideLocationInformation-r13 TBS-ProvideLocationInformation-r13 OPTIONAL, + wlan-ProvideLocationInformation-r13 WLAN-ProvideLocationInformation-r13 OPTIONAL, + bt-ProvideLocationInformation-r13 BT-ProvideLocationInformation-r13 OPTIONAL + ]], + [[ nr-ECID-ProvideLocationInformation-r16 + NR-ECID-ProvideLocationInformation-r16 OPTIONAL, + nr-Multi-RTT-ProvideLocationInformation-r16 + NR-Multi-RTT-ProvideLocationInformation-r16 OPTIONAL, + nr-DL-AoD-ProvideLocationInformation-r16 + NR-DL-AoD-ProvideLocationInformation-r16 OPTIONAL, + nr-DL-TDOA-ProvideLocationInformation-r16 + NR-DL-TDOA-ProvideLocationInformation-r16 OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +## – *Abort* + +The *Abort* message body in a LPP message carries a request to abort an ongoing LPP procedure. + +``` +-- ASN1START + +Abort ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + abort-r9 Abort-r9-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +Abort-r9-IEs ::= SEQUENCE { + commonIEsAbort CommonIEsAbort OPTIONAL, -- Need ON + ..., + epdu-Abort EPDU-Sequence OPTIONAL -- Need ON +} + +-- ASN1STOP +``` + +## – *Error* + +The *Error* message body in a LPP message carries information concerning a LPP message that was received with errors. + +``` +-- ASN1START + +Error ::= CHOICE { + error-r9 Error-r9-IEs, + criticalExtensionsFuture SEQUENCE {} +} + +Error-r9-IEs ::= SEQUENCE { + commonIEsError CommonIEsError OPTIONAL, -- Need ON + ..., + epdu-Error EPDU-Sequence OPTIONAL -- Need ON +} + +-- ASN1STOP +``` + +## 6.4 Common IEs + +Common IEs comprise IEs that are applicable to more than one LPP positioning method. + +### 6.4.1 Common Lower-Level IEs + +#### – *AccessTypes* + +The IE *AccessTypes* is used to indicate several cellular access types using a bit map. + +``` +-- ASN1START + +AccessTypes ::= SEQUENCE { + accessTypes BIT STRING { + eutra (0), + utra (1), + gsm (2), + nb-iot (3), + nr-v1510 (4) } (SIZE (1..8)), + ... +} + +-- ASN1STOP +``` + +**AccessTypes field descriptions****accessTypes** + +This field specifies the cellular access type(s). This is represented by a bit string, with a one-value at the bit position means the particular access type is addressed; a zero-value means not addressed. + +### — ARFCN-ValueEUTRA + +The IEs *ARFCN-ValueEUTRA* and *ARFCN-ValueEUTRA-v9a0* are used to indicate the ARFCN of the E-UTRA carrier frequency, as defined in TS 36.331 [12]. + +``` +-- ASN1START +ARFCN-ValueEUTRA ::= INTEGER (0..maxEARFCN) +ARFCN-ValueEUTRA-v9a0 ::= INTEGER (maxEARFCN-Plus1..maxEARFCN2) +ARFCN-ValueEUTRA-r14 ::= INTEGER (0..maxEARFCN2) +-- ASN1STOP +``` + +NOTE 1: For fields using the original value range, as defined by IE *ARFCN-ValueEUTRA* i.e. without suffix, value *maxEARFCN* indicates that the E-UTRA carrier frequency is indicated by means of an extension. + +### — ARFCN-ValueNR + +The IE *ARFCN-ValueNR* is used to indicate the ARFCN applicable for a downlink, uplink or bi-directional (TDD) NR global frequency raster, as defined in TS 38.101-2 [34] and TS 38.101-1 [37]. + +``` +-- ASN1START +ARFCN-ValueNR-r15 ::= INTEGER (0..3279165) +-- ASN1STOP +``` + +### — ARFCN-ValueUTRA + +The IE *ARFCN-ValueUTRA* is used to indicate the ARFCN of the UTRA carrier frequency, as defined in TS 25.331 [13]. + +``` +-- ASN1START +ARFCN-ValueUTRA ::= INTEGER (0..16383) +-- ASN1STOP +``` + +### — CarrierFreq-NB + +The IE *CarrierFreq-NB* is used to provide the NB-IoT carrier frequency, as defined in TS 36.101 [21]. + +``` +-- ASN1START +CarrierFreq-NB-r14 ::= SEQUENCE { + carrierFreq-r14 ARFCN-ValueEUTRA-r14, + carrierFreqOffset-r14 CarrierFreqOffsetNB-r14 OPTIONAL, + ... +} +-- ASN1STOP +``` + +| CarrierFreq-NB field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------| +| carrierFreq
This field specifies the ARFCN applicable for the NB-IoT carrier frequency as defined in TS 36.101 [21, Table 5.7.3-1]. | +| carrierFreqOffset
This field specifies the offset of the NB-IoT channel number to EARFCN as defined in TS 36.101 [21]. | + +### — **CarrierFreqOffsetNB** + +The IE *CarrierFreqOffsetNB* is used to provide the offset of the NB-IoT channel number to EARFCN of a NB-IoT carrier. + +``` +-- ASN1START +CarrierFreqOffsetNB-r14 ::= ENUMERATED { + v-10, v-9, v-8, v-7, v-6, v-5, v-4, v-3, v-2, v-1, v-0dot5, + v0, v1, v2, v3, v4, v5, v6, v7, v8, v9 + } +-- ASN1STOP +``` + +| CarrierFreqOffsetNB field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CarrierFreqOffsetNB
This field specifies the offset of the NB-IoT channel number to EARFCN as defined in TS 36.101 [21]. Value v-10 means -10, v-9 means -9, and so on. | + +### — **CellGlobalIdEUTRA-AndUTRA** + +The IE *CellGlobalIdEUTRA-AndUTRA* specifies the global Cell Identifier for E-UTRA or UTRA, the globally unique identity of a cell in E-UTRA or UTRA. + +``` +-- ASN1START +CellGlobalIdEUTRA-AndUTRA ::= SEQUENCE { + plmn-Identity SEQUENCE { + mcc SEQUENCE (SIZE (3)) OF INTEGER (0..9), + mnc SEQUENCE (SIZE (2..3)) OF INTEGER (0..9) + }, + cellIdentity CHOICE { + eutra BIT STRING (SIZE (28)), + utra BIT STRING (SIZE (32)) + }, + ... +} +-- ASN1STOP +``` + +| CellGlobalIdEUTRA-AndUTRA field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| plmn-Identity
This field identifies the PLMN of the cell as defined in TS 36.331 [12]. | +| cellIdentity
This field defines the identity of the cell within the context of the PLMN as defined in TS 36.331 [12] and TS 25.331 [13]. The size of the bit string allows for the 32-bit extended UTRAN cell ID; in the case the cell ID is shorter, the first bits of the string are set to 0. | + +### — **CellGlobalIdGERAN** + +The IE *CellGlobalIdGERAN* specifies the global Cell Identifier for GERAN, the globally unique identity of a cell in GERAN. + +``` +-- ASN1START +CellGlobalIdGERAN ::= SEQUENCE { + plmn-Identity SEQUENCE { + mcc SEQUENCE (SIZE (3)) OF INTEGER (0..9), + mnc SEQUENCE (SIZE (2..3)) OF INTEGER (0..9) + } +} +``` + +``` + + }, + locationAreaCode BIT STRING (SIZE (16)), + cellIdentity BIT STRING (SIZE (16)), + ... + } + +-- ASN1STOP + +``` + +#### CellGlobalIdGERAN field descriptions + +##### **plmn-Identity** + +This field identifies the PLMN of the cell. + +##### **locationAreaCode** + +This field is a fixed length code identifying the location area within a PLMN. + +##### **cellIdentity** + +This field specifies the cell Identifier which is unique within the context of the GERAN location area. + +### — **ECGI** + +The IE *ECGI* specifies the Evolved Cell Global Identifier (ECGI), the globally unique identity of a cell in E-UTRA (TS 36.331 [12]). + +NOTE 2: The IE *ECGI* is also used for NB-IoT access. + +``` + +-- ASN1START + +ECGI ::= SEQUENCE { + mcc SEQUENCE (SIZE (3)) OF INTEGER (0..9), + mnc SEQUENCE (SIZE (2..3)) OF INTEGER (0..9), + cellidentity BIT STRING (SIZE (28)) +} + +-- ASN1STOP + +``` + +### — ***Ellipsoid-Point*** + +The IE *Ellipsoid-Point* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` + +-- ASN1START + +Ellipsoid-Point ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607) -- 24 bit field +} + +-- ASN1STOP + +``` + +### — ***Ellipsoid-PointWithUncertaintyCircle*** + +The IE *Ellipsoid-PointWithUncertaintyCircle* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` + +-- ASN1START + +Ellipsoid-PointWithUncertaintyCircle ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + uncertainty INTEGER (0..127) +} + +-- ASN1STOP + +``` + +### – *EllipsoidPointWithUncertaintyEllipse* + +The IE *EllipsoidPointWithUncertaintyEllipse* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` +-- ASN1START + +EllipsoidPointWithUncertaintyEllipse ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + uncertaintySemiMajor INTEGER (0..127), + uncertaintySemiMinor INTEGER (0..127), + orientationMajorAxis INTEGER (0..179), + confidence INTEGER (0..100) +} + +-- ASN1STOP +``` + +### – *EllipsoidPointWithAltitude* + +The IE *EllipsoidPointWithAltitude* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` +-- ASN1START + +EllipsoidPointWithAltitude ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + altitudeDirection ENUMERATED {height, depth}, + altitude INTEGER (0..32767), -- 15 bit field +} + +-- ASN1STOP +``` + +### – *EllipsoidPointWithAltitudeAndUncertaintyEllipsoid* + +The IE *EllipsoidPointWithAltitudeAndUncertaintyEllipsoid* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` +-- ASN1START + +EllipsoidPointWithAltitudeAndUncertaintyEllipsoid ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + altitudeDirection ENUMERATED {height, depth}, + altitude INTEGER (0..32767), -- 15 bit field + uncertaintySemiMajor INTEGER (0..127), + uncertaintySemiMinor INTEGER (0..127), + orientationMajorAxis INTEGER (0..179), + uncertaintyAltitude INTEGER (0..127), + confidence INTEGER (0..100) +} + +-- ASN1STOP +``` + +### – *EllipsoidArc* + +The IE *EllipsoidArc* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` +-- ASN1START + +EllipsoidArc ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + innerRadius INTEGER (0..65535), -- 16 bit field, + uncertaintyRadius INTEGER (0..127), + offsetAngle INTEGER (0..179), +} +``` + +``` + + includedAngle INTEGER (0..179), + confidence INTEGER (0..100) +} + +-- ASN1STOP + +``` + +## – *EPDU-Sequence* + +The *EPDU-Sequence* contains IEs that are defined externally to LPP by other organizations. + +``` + +-- ASN1START + +EPDU-Sequence ::= SEQUENCE (SIZE (1..maxEPDU)) OF EPDU + +maxEPDU INTEGER ::= 16 + +EPDU ::= SEQUENCE { + ePDU-Identifier EPDU-Identifier, + ePDU-Body EPDU-Body +} + +EPDU-Identifier ::= SEQUENCE { + ePDU-ID EPDU-ID, + ePDU-Name EPDU-Name OPTIONAL, + ... +} + +EPDU-ID ::= INTEGER (1..256) + +EPDU-Name ::= VisibleString (SIZE (1..32)) + +EPDU-Body ::= OCTET STRING + +-- ASN1STOP + +``` + +### *EPDU-Sequence* field descriptions + +#### ***EPDU-ID*** + +This field provides a unique integer ID for the externally defined positioning method. Its value is assigned to the external entity that defines the EPDU. See table External PDU Identifier Definition for a list of external PDU identifiers defined in this version of the specification. + +#### ***EPDU-Name*** + +This field provides an optional character encoding which can be used to provide a quasi-unique name for an external PDU – e.g., by containing the name of the defining organization and/or the name of the associated public or proprietary standard for the EPDU. + +#### ***EPDU-Body*** + +The content and encoding of this field are defined externally to LPP. + +### External PDU Identifier Definition + +| EPDU-ID | EPDU Defining entity | Method name | Reference | +|----------------|-----------------------------|---------------------------|-----------------------| +| 1 | OMA LOC | OMA LPP extensions (LPPE) | OMA-TS-LPPE-V1_0 [20] | + +## – *FreqBandIndicatorNR* + +The IE *FreqBandIndicatorNR* specifies the NR band indicator (TS 38.331 [35]). + +``` + +-- ASN1START + +FreqBandIndicatorNR-r16 ::= INTEGER (1..1024) + +-- ASN1STOP + +``` + +### – *HA-EllipsoidPointWithAltitudeAndScalableUncertaintyEllipsoid* + +The IE *HA-EllipsoidPointWithAltitudeAndScalableUncertaintyEllipsoid* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` +-- ASN1START +HA-EllipsoidPointWithAltitudeAndScalableUncertaintyEllipsoid-r16 ::= SEQUENCE { + degreesLatitude-r16 INTEGER(-2147483648..2147483647), + degreesLongitude-r16 INTEGER(-2147483648..2147483647), + altitude-r16 INTEGER(-64000..1280000), + uncertaintySemiMajor-r16 INTEGER (0..255), + uncertaintySemiMinor-r16 INTEGER (0..255), + orientationMajorAxis-r16 INTEGER (0..179), + horizontalConfidence-r16 INTEGER (0..100), + uncertaintyAltitude-r16 INTEGER (0..255), + verticalConfidence-r16 INTEGER (0..100), + ha-HorizontalExtendedRangeUsed-r16 BOOLEAN, + ha-VerticalExtendedRangeUsed-r16 BOOLEAN +} + +-- ASN1STOP +``` + +### – *HA-EllipsoidPointWithScalableUncertaintyEllipse* + +The IE *HA-EllipsoidPointWithScalableUncertaintyEllipse* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` +-- ASN1START +HA-EllipsoidPointWithScalableUncertaintyEllipse-r16 ::= SEQUENCE { + degreesLatitude-r16 INTEGER(-2147483648..2147483647), + degreesLongitude-r16 INTEGER(-2147483648..2147483647), + uncertaintySemiMajor-r16 INTEGER (0..255), + uncertaintySemiMinor-r16 INTEGER (0..255), + orientationMajorAxis-r16 INTEGER (0..179), + confidence-r16 INTEGER (0..100), + ha-ExtendedUncertaintyRangeUsed-r16 BOOLEAN +} + +-- ASN1STOP +``` + +### – *HighAccuracyEllipsoidPointWithUncertaintyEllipse* + +The IE *HighAccuracyEllipsoidPointWithUncertaintyEllipse* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` +-- ASN1START +HighAccuracyEllipsoidPointWithUncertaintyEllipse-r15 ::= SEQUENCE { + degreesLatitude-r15 INTEGER(-2147483648..2147483647), + degreesLongitude-r15 INTEGER(-2147483648..2147483647), + uncertaintySemiMajor-r15 INTEGER (0..255), + uncertaintySemiMinor-r15 INTEGER (0..255), + orientationMajorAxis-r15 INTEGER (0..179), + confidence-r15 INTEGER (0..100) +} + +-- ASN1STOP +``` + +### – *HighAccuracyEllipsoidPointWithAltitudeAndUncertaintyEllipsoid* + +The IE *HighAccuracyEllipsoidPointWithAltitudeAndUncertaintyEllipsoid* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` +-- ASN1START +HighAccuracyEllipsoidPointWithAltitudeAndUncertaintyEllipsoid-r15 ::= SEQUENCE { +``` + +``` + +degreesLatitude-r15 INTEGER(-2147483648..2147483647), +degreesLongitude-r15 INTEGER(-2147483648..2147483647), +altitude-r15 INTEGER(-64000..1280000), +uncertaintySemiMajor-r15 INTEGER (0..255), +uncertaintySemiMinor-r15 INTEGER (0..255), +orientationMajorAxis-r15 INTEGER (0..179), +horizontalConfidence-r15 INTEGER (0..100), +uncertaintyAltitude-r15 INTEGER (0..255), +verticalConfidence-r15 INTEGER (0..100) +} + +-- ASN1STOP + +``` + +### – *HorizontalVelocity* + +The IE *HorizontalVelocity* is used to describe a velocity shape as defined in TS 23.032 [15]. + +``` + +-- ASN1START + +HorizontalVelocity ::= SEQUENCE { + bearing INTEGER(0..359), + horizontalSpeed INTEGER(0..2047) +} + +-- ASN1STOP + +``` + +### – *HorizontalWithVerticalVelocity* + +The IE *HorizontalWithVerticalVelocity* is used to describe a velocity shape as defined in TS 23.032 [15]. + +``` + +-- ASN1START + +HorizontalWithVerticalVelocity ::= SEQUENCE { + bearing INTEGER(0..359), + horizontalSpeed INTEGER(0..2047), + verticalDirection ENUMERATED{upward, downward}, + verticalSpeed INTEGER(0..255) +} + +-- ASN1STOP + +``` + +### – *HorizontalVelocityWithUncertainty* + +The IE *HorizontalVelocityWithUncertainty* is used to describe a velocity shape as defined in TS 23.032 [15]. + +``` + +-- ASN1START + +HorizontalVelocityWithUncertainty ::= SEQUENCE { + bearing INTEGER(0..359), + horizontalSpeed INTEGER(0..2047), + uncertaintySpeed INTEGER(0..255) +} + +-- ASN1STOP + +``` + +### – *HorizontalWithVerticalVelocityAndUncertainty* + +The IE *HorizontalWithVerticalVelocityAndUncertainty* is used to describe a velocity shape as defined in TS 23.032 [15]. + +``` + +-- ASN1START + +HorizontalWithVerticalVelocityAndUncertainty ::= SEQUENCE { + bearing INTEGER(0..359), + horizontalSpeed INTEGER(0..2047), + verticalDirection ENUMERATED{upward, downward}, + verticalSpeed INTEGER(0..255), +} + +``` + +``` + + horizontalUncertaintySpeed INTEGER(0..255), + verticalUncertaintySpeed INTEGER(0..255) +} + +-- ASN1STOP + +``` + +### – *Local2dPointWithUncertaintyEllipse* + +The IE *Local2dPointWithUncertaintyEllipse* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` + +-- ASN1START + +Local2dPointWithUncertaintyEllipse-r18 ::= SEQUENCE { + localOrigin-r18 ReferencePoint-r16, + cartesianCoordinatesUnits-r18 ENUMERATED { mm, cm, dm, m, ... }, + x-value-r18 X-Value-r18, + y-value-r18 Y-Value-r18, + uncertaintySemiMajor-r18 INTEGER (0..127), + uncertaintySemiMinor-r18 INTEGER (0..127), + orientationMajorAxis-r18 INTEGER (0..179), + confidence-r18 INTEGER (0..100) +} + +-- ASN1STOP + +``` + +| Local2dPointWithUncertaintyEllipse field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| localOrigin
This field identifies the reference point of the local Cartesian coordinate system. | +| cartesianCoordinatesUnits
This field provides the unit and scale factor for the x-value and y-value fields. Enumerated values mm, cm, dm, and m, correspond to $10^{-3}$ metre, $10^{-2}$ metre, $10^{-1}$ metre and 1 metres, respectively. | +| x-value
This field provides the x-value of the location in the Cartesian coordinate system. Positive value represents easting from reference point (origin) [15]. See IE RelativeCartesianLocation . | +| y-value
This field provides the y-value of the location in the Cartesian coordinate system. Positive value represents northing from reference point (origin) [15]. See IE RelativeCartesianLocation . | +| uncertaintySemiMajor
This field indicates the semi-major axis of the uncertainty ellipse [15]. | +| uncertaintySemiMinor
This field indicates the semi-minor axis of the uncertainty ellipse [15]. | +| orientationMajorAxis
This field indicates the orientation angle of the major axis [15]. | +| confidence
This field indicates the confidence value [15]. | + +### – *Local3dPointWithUncertaintyEllipsoid* + +The IE *Local3dPointWithUncertaintyEllipsoid* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` + +-- ASN1START + +Local3dPointWithUncertaintyEllipsoid-r18 ::= SEQUENCE { + localOrigin-r18 ReferencePoint-r16, + cartesianCoordinatesUnits-r18 ENUMERATED { mm, cm, dm, m, ... }, + x-value-r18 X-Value-r18, + y-value-r18 Y-Value-r18, + z-value-r18 Z-Value-r18, + uncertaintySemiMajor-r18 INTEGER (0..127), + uncertaintySemiMinor-r18 INTEGER (0..127), + orientationMajorAxis-r18 INTEGER (0..179), + uncertaintyAltitude-r18 INTEGER (0..127), + confidence-r18 INTEGER (0..100) +} + +-- ASN1STOP + +``` + +| Local3dPointWithUncertaintyEllipsoid field descriptions | | +|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| localOrigin | This field identifies the reference point of the local Cartesian coordinate system. | +| cartesianCoordinatesUnits | This field provides the unit and scale factor for the x-value , y-value and z-value fields. Enumerated values mm, cm, dm, and m, correspond to $10^{-3}$ metre, $10^{-2}$ metre, $10^{-1}$ metre and 1 metres, respectively. | +| x-value | This field provides the x-value of the location in the Cartesian coordinate system. Positive value represents easting from reference point (origin) [15]. See IE RelativeCartesianLocation . | +| y-value | This field provides the y-value of the location in the Cartesian coordinate system. Positive value represents northing from reference point (origin) [15]. See IE RelativeCartesianLocation . | +| z-value | This field provides the z-value of the location in the Cartesian coordinate system. Positive value represents height above reference point (origin) [15]. See IE RelativeCartesianLocation . | +| uncertaintySemiMajor | This field indicates the semi-major axis of the uncertainty ellipsoid [15]. | +| uncertaintySemiMinor | This field indicates the semi-minor axis of the uncertainty ellipsoid [15]. | +| orientationMajorAxis | This field indicates the orientation angle of the major axis [15]. | +| uncertaintyAltitude | This field indicates the vertical axis of the uncertainty ellipsoid [15]. | +| confidence | This field indicates the confidence value [15]. | + +## LocationCoordinateTypes + +The IE *LocationCoordinateTypes* defines a list of possible geographic shapes as defined in TS 23.032 [15]. + +``` +-- ASN1START +LocationCoordinateTypes ::= SEQUENCE { + ellipsoidPoint BOOLEAN, + ellipsoidPointWithUncertaintyCircle BOOLEAN, + ellipsoidPointWithUncertaintyEllipse BOOLEAN, + polygon BOOLEAN, + ellipsoidPointWithAltitude BOOLEAN, + ellipsoidPointWithAltitudeAndUncertaintyEllipsoid BOOLEAN, + ellipsoidArc BOOLEAN, + ... + [[ + highAccuracyEllipsoidPointWithUncertaintyEllipse-r15 + BOOLEAN OPTIONAL, -- Need ON + highAccuracyEllipsoidPointWithAltitudeAndUncertaintyEllipsoid-r15 + BOOLEAN OPTIONAL -- Need ON + ]], + [[ + ha-EllipsoidPointWithScalableUncertaintyEllipse-r16 + BOOLEAN OPTIONAL, -- Need ON + ha-EllipsoidPointWithAltitudeAndScalableUncertaintyEllipsoid-r16 + BOOLEAN OPTIONAL -- Need ON + ]], + [[ + local2dPointWithUncertaintyEllipse-r18 BOOLEAN OPTIONAL, -- Need ON + local3dPointWithUncertaintyEllipsoid-r18 BOOLEAN OPTIONAL -- Need ON + ]] +} +-- ASN1STOP +``` + +NOTE 3: In this version of the specification, the GAD shapes *local2dPointWithUncertaintyEllipse* and *local3dPointWithUncertaintyEllipsoid* are supported for DL-TDOA and DL-AoD only. + +## NCGI + +The IE *NCGI* specifies the NR Cell Global Identifier (NCGI) which is used to identify NR cells globally (TS 38.331 [35]). + +``` + +-- ASN1START + +NCGI-r15 ::= SEQUENCE { + mcc-r15 SEQUENCE (SIZE (3)) OF INTEGER (0..9), + mnc-r15 SEQUENCE (SIZE (2..3)) OF INTEGER (0..9), + nr-cellidentity-r15 BIT STRING (SIZE (36)) +} + +-- ASN1STOP + +``` + +### – **NR-PhysCellId** + +The IE *NR-PhysCellId* specifies the NR physical cell identifier (TS 38.331 [35]). + +``` + +-- ASN1START + +NR-PhysCellID-r16 ::= INTEGER (0..1007) + +-- ASN1STOP + +``` + +### – **PeriodicAssistanceDataControlParameters** + +The IE *PeriodicAssistanceDataControlParameters* is used in a periodic assistance data delivery procedure as described in clauses 5.2.1a and 5.2.2a. + +``` + +-- ASN1START + +PeriodicAssistanceDataControlParameters-r15 ::= SEQUENCE { + periodicSessionID-r15 PeriodicSessionID-r15, + ... + [[ + updateCapabilities-r15 UpdateCapabilities-r15 OPTIONAL -- Need ON + ]] +} + +PeriodicSessionID-r15 ::= SEQUENCE { + periodicSessionInitiator-r15 ENUMERATED { locationServer, targetDevice, ... }, + periodicSessionNumber-r15 INTEGER (0..255), + ... +} + +UpdateCapabilities-r15 ::= BIT STRING {primaryCellID-r15 (0)} (SIZE(1..8)) + +-- ASN1STOP + +``` + +#### **PeriodicAssistanceDataControlParameters field descriptions** + +##### ***periodicSessionID*** + +This field identifies a particular periodic assistance data delivery session and the initiator of the session. + +##### ***updateCapabilities*** + +This field identifies the capabilities of the sending entity to support an update of periodic assistance data. A bit value set to one indicates a capability is supported and a bit value set to zero indicates a capability is not supported. + +### – **Polygon** + +The IE *Polygon* is used to describe a geographic shape as defined in TS 23.032 [15]. + +``` + +-- ASN1START + +Polygon ::= SEQUENCE (SIZE (3..15)) OF PolygonPoints + +PolygonPoints ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607) -- 24 bit field +} + +-- ASN1STOP + +``` + +## – *PositioningModes* + +The IE *PositioningModes* is used to indicate several positioning modes using a bit map. + +``` +-- ASN1START + +PositioningModes ::= SEQUENCE { + posModes BIT STRING { standalone (0), + ue-based (1), + ue-assisted (2) + } (SIZE (1..8)), + ... +} + +-- ASN1STOP +``` + +### *PositioningModes* field descriptions + +#### ***posModes*** + +This field specifies the positioning mode(s). This is represented by a bit string, with a one-value at the bit position means the particular positioning mode is addressed; a zero-value means not addressed. + +## – *ScheduledLocationTimeSupport* + +The IE *ScheduledLocationTimeSupport* is used by the target device to indicate the time bases supported for scheduled location requests. + +``` +-- ASN1START + +ScheduledLocationTimeSupport-r17 ::= SEQUENCE { + utcTime-r17 ENUMERATED { supported } OPTIONAL, + gnssTime-r17 GNSS-ID-Bitmap OPTIONAL, + e-utraTime-r17 ENUMERATED { supported } OPTIONAL, + nrTime-r17 ENUMERATED { supported } OPTIONAL, + relativeTime-r17 ENUMERATED { supported } OPTIONAL, + ... +} + +-- ASN1STOP +``` + +## – *ScheduledLocationTimeSupportPerMode* + +The IE *ScheduledLocationTimeSupportPerMode* is used by the target device to indicate the time bases supported for scheduled location requests for each positioning mode indicated by *PositioningModes*. + +``` +-- ASN1START + +ScheduledLocationTimeSupportPerMode-r17 ::= SEQUENCE { + utcTime-r17 PositioningModes OPTIONAL, + gnssTime-r17 SEQUENCE { + posModes-r17 PositioningModes, + gnss-TimeIDs-r17 GNSS-ID-Bitmap + } OPTIONAL, + e-utraTime-r17 PositioningModes OPTIONAL, + nrTime-r17 PositioningModes OPTIONAL, + relativeTime-r17 PositioningModes OPTIONAL, + ... +} + +-- ASN1STOP +``` + +## – *SegmentationInfo* + +The IE *SegmentationInfo* is used by a sender to indicate that LPP message segmentation is used, as specified in clause 4.3.5. + +``` +-- ASN1START + +SegmentationInfo-r14 ::= ENUMERATED { noMoreMessages, moreMessagesOnTheWay } + +-- ASN1STOP +``` + +| SegmentationInfo field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

SegmentationInfo
noMoreMessages indicates that this is the only or last LPP message segment used to deliver the entire message body.
moreMessagesOnTheWay indicates that this is one of multiple LPP message segments used to deliver the entire message body.

| + +## VelocityTypes + +The IE *VelocityTypes* defines a list of possible velocity shapes as defined in TS 23.032 [15]. + +``` +-- ASN1START + +VelocityTypes ::= SEQUENCE { + horizontalVelocity BOOLEAN, + horizontalWithVerticalVelocity BOOLEAN, + horizontalVelocityWithUncertainty BOOLEAN, + horizontalWithVerticalVelocityAndUncertainty BOOLEAN, + ... +} + +-- ASN1STOP +``` + +## 6.4.2 Common Positioning + +### CommonIEsRequestCapabilities + +The *CommonIEsRequestCapabilities* carries common IEs for a Request Capabilities LPP message Type. + +``` +-- ASN1START + +CommonIEsRequestCapabilities ::= SEQUENCE { + ..., + [[ + lpp-message-segmentation-req-r14 BIT STRING { serverToTarget (0), + targetToServer (1) } OPTIONAL -- Need ON + ]], + [[ + remoteUE-IndicationReq-r18 ENUMERATED { true } OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP +``` + +| CommonIEsRequestCapabilities field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

lpp-message-segmentation-req
This field, if present, indicates that the target device is requested to provide its LPP message segmentation capabilities.
If bit 0 is set to value 1, it indicates that the server is able to send segmented LPP messages to the target device; if bit 0 is set to value 0 it indicates that the server is not able to send segmented LPP messages to the target device.
If bit 1 is set to value 1, it indicates that the server is able to receive segmented LPP messages from the target device; if bit 1 is set to value 0 it indicates that the server is not able to receive segmented LPP messages from the target device.

| +|

remoteUE-IndicationReq
This field, if present, indicates that the target device is requested to indicate if it operates as a L2 U2N Remote UE.

| + +## CommonIEsProvideCapabilities + +The *CommonIEsProvideCapabilities* carries common IEs for a Provide Capabilities LPP message Type. + +``` +-- ASN1START + +CommonIEsProvideCapabilities ::= SEQUENCE { + ... + [[ + segmentationInfo-r14 SegmentationInfo-r14 OPTIONAL, -- Cond Segmentation + lpp-message-segmentation-r14 BIT STRING { serverToTarget (0), + targetToServer (1) } OPTIONAL + ]], + [[ + remoteUE-Indication-r18 BOOLEAN OPTIONAL, -- Cond NR + locationEstimateAndMeasurementReporting-r18 ENUMERATED { supported } OPTIONAL + ]] +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Segmentation | This field is optionally present, need OP, if lpp-message-segmentation-req has been received from the location server with bit 1 ( targetToServer ) set to value 1. The field shall be omitted if lpp-message-segmentation-req has not been received in this location session, or has been received with bit 1 ( targetToServer ) set to value 0. | +| NR | This field is optionally present, need OR, for NR access if remoteUE-IndicationReq has been received from the location server in this location session. Otherwise it is not present. | + +| CommonIEsProvideCapabilities field descriptions | | +|-------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| segmentationInfo | This field indicates whether this ProvideCapabilities message is one of many segments, as specified in clause 4.3.5. | +| lpp-message-segmentation | This field, if present, indicates the target device's LPP message segmentation capabilities.
If bit 0 is set to value 1, it indicates that the target device supports receiving segmented LPP messages; if bit 0 is set to value 0 it indicates that the target device does not support receiving segmented LPP messages.
If bit 1 is set to value 1, it indicates that the target device supports sending segmented LPP messages; if bit 1 is set to value 0 it indicates that the target device does not support sending segmented LPP messages. | +| remoteUE-Indication | This field indicates whether the target device in NR access is configured as a L2 U2N Remote UE. The target device in NR access may transmit a ProvideCapabilities message with an appropriate value of this field when it starts or stops operation as a U2N Remote UE. | +| locationEstimateAndMeasurementReporting | This field, if present, indicates that the target device supports locationEstimateAndMeasurementsRequired in LocationInformationType . | + +## CommonIEsRequestAssistanceData + +The *CommonIEsRequestAssistanceData* carries common IEs for a Request Assistance Data LPP message Type. + +``` +-- ASN1START + +CommonIEsRequestAssistanceData ::= SEQUENCE { + primaryCellID ECGI OPTIONAL, -- Cond EUTRA + ... + [[ + segmentationInfo-r14 SegmentationInfo-r14 OPTIONAL -- Cond Segmentation + ]], + [[ + periodicAssistanceDataReq-r15 + PeriodicAssistanceDataControlParameters-r15 + OPTIONAL, -- Cond PerADreq + primaryCellID-r15 NCGI-r15 OPTIONAL -- Cond NR + ]] +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EUTRA | The field is mandatory present for E-UTRA or NB-IoT access. The field shall be omitted for non-EUTRA and non-NB-IoT user plane support. | +| Segmentation | This field is optionally present, need OP, if lpp-message-segmentation-req has been received from the location server with bit 1 ( targetToServer ) set to value 1. The field shall be omitted if lpp-message-segmentation-req has not been received in this location session, or has been received with bit 1 ( targetToServer ) set to value 0. | +| PerADreq | The field is mandatory present if the target device requests periodic assistance data delivery. Otherwise it is not present. | +| NR | The field is mandatory present for NR access. The field shall be omitted for non-NR user plane support. | + +| CommonIEsRequestAssistanceData field descriptions | | +|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| primaryCellID | This parameter identifies the current primary cell for the target device. | +| segmentationInfo | This field indicates whether this RequestAssistanceData message is one of many segments, as specified in clause 4.3.5. | +| periodicAssistanceDataReq | This field indicates a request for periodic assistance data delivery, as specified in clause 5.2.1a. | + +## – CommonIEsProvideAssistanceData + +The *CommonIEsProvideAssistanceData* carries common IEs for a Provide Assistance Data LPP message Type. + +``` +-- ASN1START +CommonIEsProvideAssistanceData ::= SEQUENCE { + ... + [[ + segmentationInfo-r14 SegmentationInfo-r14 OPTIONAL -- Need ON + ]], + [[ + periodicAssistanceData-r15 PeriodicAssistanceDataControlParameters-r15 + OPTIONAL -- Cond PerAD + ]] +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------| +| PerAD | The field is mandatory present in a periodic assistance data delivery session. Otherwise it is not present. | + +| CommonIEsProvideAssistanceData field descriptions | | +|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| segmentationInfo | This field indicates whether this ProvideAssistanceData message is one of many segments, as specified in clause 4.3.5. | +| periodicAssistanceData | This field indicates a periodic assistance data delivery, as specified in clauses 5.2.1a and 5.2.2a. | + +## – CommonIEsRequestLocationInformation + +The *CommonIEsRequestLocationInformation* carries common IEs for a Request Location Information LPP message Type. + +``` +-- ASN1START +CommonIEsRequestLocationInformation ::= SEQUENCE { + locationInformationType LocationInformationType, + triggeredReporting TriggeredReportingCriteria OPTIONAL, -- Cond ECID + periodicalReporting PeriodicalReportingCriteria OPTIONAL, -- Need ON + additionalInformation AdditionalInformation OPTIONAL, -- Need ON + qos QoS OPTIONAL, -- Need ON +} +``` + +``` + +environment Environment OPTIONAL, -- Need ON +locationCoordinateTypes LocationCoordinateTypes OPTIONAL, -- Need ON +velocityTypes VelocityTypes OPTIONAL, -- Need ON +..., +[[ + messageSizeLimitNB-r14 MessageSizeLimitNB-r14 OPTIONAL -- Need ON +]], +[[ + segmentationInfo-r14 SegmentationInfo-r14 OPTIONAL -- Need ON +]], +[[ + scheduledLocationTime-r17 + ScheduledLocationTime-r17 OPTIONAL, -- Need ON + targetIntegrityRisk-r17 + TargetIntegrityRisk-r17 OPTIONAL -- Need ON +]] +} + +LocationInformationType ::= ENUMERATED { + locationEstimateRequired, + locationMeasurementsRequired, + locationEstimatePreferred, + locationMeasurementsPreferred, + ..., + locationEstimateAndMeasurementsRequired-r18 +} + +PeriodicalReportingCriteria ::= SEQUENCE { + reportingAmount ENUMERATED { + ra1, ra2, ra4, ra8, ra16, ra32, + ra64, ra-Infinity + } DEFAULT ra-Infinity, + reportingInterval ENUMERATED { + noPeriodicalReporting, ri0-25, + ri0-5, ri1, ri2, ri4, ri8, ri16, ri32, ri64 + } +} + +TriggeredReportingCriteria ::= SEQUENCE { + cellChange BOOLEAN, + reportingDuration ReportingDuration, + ... +} + +ReportingDuration ::= INTEGER (0..255) + +AdditionalInformation ::= ENUMERATED { + onlyReturnInformationRequested, + mayReturnAdditionalInformation, + ... +} + +QoS ::= SEQUENCE { + horizontalAccuracy HorizontalAccuracy OPTIONAL, -- Need ON + verticalCoordinateRequest BOOLEAN, + verticalAccuracy VerticalAccuracy OPTIONAL, -- Need ON + responseTime ResponseTime OPTIONAL, -- Need ON + velocityRequest BOOLEAN, + ..., + [[ + responseTimeNB-r14 ResponseTimeNB-r14 OPTIONAL -- Need ON + ]], + [[ + horizontalAccuracyExt-r15 HorizontalAccuracyExt-r15 OPTIONAL, -- Need ON + verticalAccuracyExt-r15 VerticalAccuracyExt-r15 OPTIONAL -- Need ON + ]] +} + +HorizontalAccuracy ::= SEQUENCE { + accuracy INTEGER(0..127), + confidence INTEGER(0..100), + ... +} + +VerticalAccuracy ::= SEQUENCE { + accuracy INTEGER(0..127), + confidence INTEGER(0..100), + ... +} + +``` + +``` + +HorizontalAccuracyExt-r15 ::= SEQUENCE { + accuracyExt-r15 INTEGER(0..255), + confidence-r15 INTEGER(0..100), + ... +} + +VerticalAccuracyExt-r15 ::= SEQUENCE { + accuracyExt-r15 INTEGER(0..255), + confidence-r15 INTEGER(0..100), + ... +} + +ResponseTime ::= SEQUENCE { + time INTEGER (1..128), + ..., + [[ responseTimeEarlyFix-r12 INTEGER (1..128) OPTIONAL -- Need ON + ]], + [[ unit-r15 ENUMERATED { ten-seconds, ... , ten-milli-seconds-v1700 } + OPTIONAL -- Need ON + ]] +} + +ResponseTimeNB-r14 ::= SEQUENCE { + timeNB-r14 INTEGER (1..512), + responseTimeEarlyFixNB-r14 INTEGER (1..512) OPTIONAL, -- Need ON + ..., + [[ unitNB-r15 ENUMERATED { ten-seconds, ... } OPTIONAL -- Need ON + ]] +} + +Environment ::= ENUMERATED { + badArea, + notBadArea, + mixedArea, + ... +} + +MessageSizeLimitNB-r14 ::= SEQUENCE { + measurementLimit-r14 INTEGER (1..512) OPTIONAL, -- Need ON + ... +} + +ScheduledLocationTime-r17 ::= SEQUENCE { + utcTime-r17 UTCTime OPTIONAL, -- Need ON + gnssTime-r17 SEQUENCE { + gnss-TOD-msec-r17 INTEGER (0..3599999), + gnss-TimeID-r17 GNSS-ID + } OPTIONAL, -- Need ON + networkTime-r17 CHOICE { + e-utraTime-r17 SEQUENCE { + lte-PhysCellId-r17 INTEGER (0..503), + lte-ArfcnEUTRA-r17 ARFCN-ValueEUTRA, + lte-CellGlobalId-r17 CellGlobalIdEUTRA-AndUTRA + OPTIONAL, -- Need ON + lte-SystemFrameNumber-r17 INTEGER (0..1023) + }, + nrTime-r17 SEQUENCE { + nr-PhysCellID-r17 NR-PhysCellID-r16, + nr-ARFCN-r17 ARFCN-ValueNR-r15, + nr-CellGlobalID-r17 NCGI-r15 OPTIONAL, -- Need ON + nr-SFN-r17 INTEGER (0..1023), + nr-Slot-r17 CHOICE { + scs15-r17 INTEGER (0..9), + scs30-r17 INTEGER (0..19), + scs60-r17 INTEGER (0..39), + scs120-r17 INTEGER (0..79) + } OPTIONAL -- Need ON + }, + ... + } OPTIONAL, -- Need ON + relativeTime-r17 INTEGER (1..1024) OPTIONAL -- Need ON +} + +TargetIntegrityRisk-r17 ::= INTEGER (10..90) + +-- ASN1STOP + +``` + +Editor Notes: FFS exact IE structure of the request for location+measurements in the agreement of RAN2#123bis. + +| Conditional presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------| +| ECID | The field is optionally present, need ON, if E-CID or NR E-CID is requested. Otherwise it is not present. | + +| CommonEsRequestLocationInformation field descriptions | | +|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| locationInformationType |

This IE indicates whether the server requires a location estimate or measurements. For 'locationEstimateRequired', the target device shall return a location estimate if possible, or indicate a location error if not possible. For 'locationMeasurementsRequired', the target device shall return measurements if possible, or indicate a location error if not possible. For 'locationEstimatePreferred', the target device shall return a location estimate if possible, but may also or instead return measurements for any requested position methods for which a location estimate is not possible. For 'locationMeasurementsPreferred', the target device shall return location measurements if possible, but may also or instead return a location estimate for any requested position methods for which return of location measurements is not possible. For 'locationEstimateAndMeasurementsRequired', the PRU shall return both location estimate and measurements if possible, or indicate a location error if not possible.

NOTE: If the PRU is requested to return both location estimate and measurements, the location information is determined independently of the reported measurements.

| +| triggeredReporting |

This IE indicates that triggered reporting is requested and comprises the following subfields:

  • - cellChange: If this field is set to TRUE, the target device provides requested location information each time the primary cell has changed.
  • - reportingDuration: Maximum duration of triggered reporting in seconds. A value of zero is interpreted to mean an unlimited (i.e. "infinite") duration. The target device should continue triggered reporting for the reportingDuration or until an LPP Abort or LPP Error message is received.

The triggeredReporting field should not be included by the location server and shall be ignored by the target device if the periodicalReporting IE or responseTime IE or responseTimeNB IE is included in CommonEsRequestLocationInformation.

| +| periodicalReporting |

This IE indicates that periodic reporting is requested and comprises the following subfields:

  • - reportingAmount indicates the number of periodic location information reports requested. Enumerated values correspond to 1, 2, 4, 8, 16, 32, 64, or infinite/indefinite number of reports. If the reportingAmount is 'infinite/indefinite', the target device shall continue periodic reporting until an LPP Abort message is received. The value 'ra1' shall not be used by a sender.
  • - reportingInterval indicates the interval between location information reports and the response time requirement for the first location information report. Enumerated values ri0-25, ri0-5, ri1, ri2, ri4, ri8, ri16, ri32, ri64 correspond to reporting intervals of 1, 2, 4, 8, 10, 16, 20, 32, and 64 seconds, respectively. Measurement reports containing no measurements or no location estimate are required when a reportingInterval expires before a target device is able to obtain new measurements or obtain a new location estimate. The value 'noPeriodicalReporting' shall not be used by a sender.
| +| additionalInformation |

This IE indicates whether a target device is allowed to return additional information to that requested. If this IE indicates 'onlyReturnInformationRequested' then the target device shall not return any additional information to that requested by the server. If this IE indicates 'mayReturnAdditionalInformation' then the target device may return additional information to that requested by the server. If a location estimate is returned, any additional information is restricted to that associated with a location estimate (e.g. might include velocity if velocity was not requested but cannot include measurements). If measurements are returned, any additional information is restricted to additional measurements (e.g. might include E-CID measurements if A-GNSS measurements were requested but not E-CID measurements).

| +| gos |

This IE indicates the quality of service and comprises a number of sub-fields. In the case of measurements, some of the sub-fields apply to the location estimate that could be obtained by the server from the measurements provided by the target device assuming that the measurements are the only sources of error. Fields are as follows:

  • - horizontalAccuracy indicates the maximum horizontal error in the location estimate at an indicated confidence level. The 'accuracy' corresponds to the encoded uncertainty as defined in TS 23.032 [15] and 'confidence' corresponds to confidence as defined in TS 23.032 [15].
  • - verticalCoordinateRequest indicates whether a vertical coordinate is required (TRUE) or not (FALSE)
  • - verticalAccuracy indicates the maximum vertical error in the location estimate at an indicated confidence level and is only applicable when a vertical coordinate is requested. The 'accuracy' corresponds to the encoded uncertainty altitude as defined in TS 23.032 [15] and 'confidence' corresponds to confidence as defined in TS 23.032 [15].
  • - responseTime
    • - time indicates the maximum response time as measured between receipt of the
| + +### **CommonEsRequestLocationInformation field descriptions** + +*RequestLocationInformation* and transmission of a *ProvideLocationInformation*. If the *unit* field is absent, this is given as an integer number of seconds between 1 and 128. If the *unit* field is present with enumerated value '*ten-seconds*', the maximum response time is given in units of 10-seconds, between 10 and 1280 seconds. If the *unit* field is present with enumerated value '*ten-milli-seconds*', the maximum response time is given in units of 10-milli-seconds, between 0.01 and 1.28 seconds. If the *periodicalReporting* IE is included in *CommonEsRequestLocationInformation*, this field should not be included by the location server and shall be ignored by the target device (if included). + +- **responseTimeEarlyFix** indicates the maximum response time as measured between receipt of the *RequestLocationInformation* and transmission of a *ProvideLocationInformation* containing early location measurements or an early location estimate. If the *unit* field is absent, this is given as an integer number of seconds between 1 and 128. If the *unit* field is present with enumerated value '*ten-seconds*', the maximum response time is given in units of 10-seconds, between 10 and 1280 seconds. If the *unit* field is present with enumerated value '*ten-milli-seconds*', the maximum response time is given in units of 10-milli-seconds, between 0.01 and 1.28 seconds. When this IE is included, a target should send a *ProvideLocationInformation* (or more than one *ProvideLocationInformation* if location information will not fit into a single message) containing early location information according to the *responseTimeEarlyFix* IE and a subsequent *ProvideLocationInformation* (or more than one *ProvideLocationInformation* if location information will not fit into a single message) containing final location information according to the *time* IE. A target shall omit sending a *ProvideLocationInformation* if the early location information is not available at the expiration of the time value in the *responseTimeEarlyFix* IE. A server should set the *responseTimeEarlyFix* IE to a value less than that for the *time* IE. A target shall ignore the *responseTimeEarlyFix* IE if its value is not less than that for the *time* IE. +- **unit** indicates the unit of the *time* and *responseTimeEarlyFix* fields. Enumerated value '*ten-seconds*' corresponds to a resolution of 10 seconds. Enumerated value '*ten-milli-seconds*' corresponds to a resolution of 0.01 seconds. If this field is absent, the unit/resolution is 1 second. Enumerated value '*ten-milli-seconds*' is only applicable for NR E-CID Positioning, NR DL-TDOA Positioning, NR DL-AoD Positioning, and NR Multi-RTT Positioning. If the enumerated value '*ten-milli-seconds*' is included for methods other than NR E-CID Positioning, NR DL-TDOA Positioning, NR DL-AoD Positioning, and NR Multi-RTT Positioning the target device shall ignore the *unit* field. +- **velocityRequest** indicates whether velocity (or measurements related to velocity) is requested (TRUE) or not (FALSE). +- **responseTimeNB** +If the *periodicalReporting* IE or *responseTime* IE is included in *CommonEsRequestLocationInformation*, this field should not be included by the location server and shall be ignored by the target device (if included). +- **timeNB** indicates the maximum response time as measured between receipt of the *RequestLocationInformation* and transmission of a *ProvideLocationInformation*. If the *unitNB* field is absent, this is given as an integer number of seconds between 1 and 512. If the *unitNB* field is present, the maximum response time is given in units of 10-seconds, between 10 and 5120 seconds. +- **responseTimeEarlyFixNB** indicates the maximum response time as measured between receipt of the *RequestLocationInformation* and transmission of a *ProvideLocationInformation* containing early location measurements or an early location estimate. If the *unitNB* field is absent, this is given as an integer number of seconds between 1 and 512. If the *unitNB* field is present, the maximum response time is given in units of 10-seconds, between 10 and 5120 seconds. When this IE is included, a target should send a *ProvideLocationInformation* (or more than one *ProvideLocationInformation* if location information will not fit into a single message) containing early location information according to the *responseTimeEarlyFixNB* IE and a subsequent *ProvideLocationInformation* (or more than one *ProvideLocationInformation* if location information will not fit into a single message) containing final location information according to the *timeNB* IE. A target shall omit sending a *ProvideLocationInformation* if the early location information is not available at the expiration of the time value in the *responseTimeEarlyFixNB* IE. A server should set the *responseTimeEarlyFixNB* IE to a value less than that for the *timeNB* IE. A target shall ignore the *responseTimeEarlyFixNB* IE if its value is not less than that for the *timeNB* IE. +- **unitNB** indicates the unit of the *timeNB* and *responseTimeEarlyFixNB* fields. Enumerated value '*ten-second*' corresponds to a resolution of 10 seconds. If this field is absent, the unit/resolution is 1 second. +- **horizontalAccuracyExt** indicates the maximum horizontal error in the location estimate at an indicated confidence level. The '*accuracyExt*' corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and '*confidence*' corresponds to confidence as defined in TS 23.032 [15]. This field should not be included by the location server and shall be ignored by the target device if the *horizontalAccuracy* field is included in QoS. +- **verticalAccuracyExt** indicates the maximum vertical error in the location estimate at an indicated confidence level and is only applicable when a vertical coordinate is requested. The '*accuracyExt*' corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and '*confidence*' corresponds to confidence as defined in TS 23.032 [15]. This field should not be included by the location server and shall be ignored by the target device if the *verticalAccuracy* field is included in QoS. + +All QoS requirements shall be obtained by the target device to the degree possible but it is permitted to return a response that does not fulfill all QoS requirements if some were not attainable. The single exception is *time* and *timeNB* which shall always be fulfilled – even if that means not fulfilling other QoS requirements. + +A target device supporting NB-IoT access shall support the *responseTimeNB* IE. + +| CommonIEsRequestLocationInformation field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

A target device supporting HA GNSS shall support the HorizontalAccuracyExt, VerticalAccuracyEx, and unit fields with enumerated value 'ten-seconds'.
A target device supporting NB-IoT access and HA GNSS shall support the unitNB field.

| +|

environment
This field provides the target device with information about expected multipath and non line of sight (NLOS) in the current area. The following values are defined:

  • - badArea: possibly heavy multipath and NLOS conditions (e.g. bad urban or urban).
  • - notBadArea: no or light multipath and usually LOS conditions (e.g. suburban or rural).
  • - mixedArea: environment that is mixed or not defined.

If this field is absent, a default value of 'mixedArea' applies.

| +|

locationCoordinateTypes
This field provides a list of the types of location estimate that the target device may return when a location estimate is obtained by the target.

| +|

velocityTypes
This field provides a list of the types of velocity estimate that the target device may return when a velocity estimate is obtained by the target.

| +|

messageSizeLimitNB
This field provides an octet limit on the amount of location information a target device can return.

  • - measurementLimit indicates the maximum amount of location information the target device should return in response to the RequestLocationInformation message received from the location server. The limit applies to the overall size of the LPP message at LPP level (LPP Provide Location Information), and is specified in steps of 100 octets. The message size limit is then given by the value provided in measurementLimit times 100 octets.
| +|

segmentationInfo
This field indicates whether this RequestLocationInformation message is one of many segments, as specified in clause 4.3.5

| +|

scheduledLocationTime
This field indicates that the target device is requested to obtain location measurements or location estimate valid at the scheduledLocationTime T and comprises the following subfields:

  • - utcTime provides T in UTC in the form of YYMMDDhhmmssZ.
  • - gnssTime provides T in GNSS system time of the GNSS indicated by gnss-TimeID.
    • - gnss-TOD-msec specifies the GNSS TOD in 1-milli-second resolution rounded down to the nearest millisecond unit.
  • - networkTime provides T in E-UTRA or NR network time.
    • - lte-PhysCellId, lte-ArfcnEUTRA, lte-CellGlobalId identifies the reference cell (E-UTRA) that is used for the network time.
    • - lte-systemFrameNumber specifies the system frame number in E-UTRA.
    • - nr-PhysCellID, nr-ARFCN, nr-CellGlobalID identifies the reference cell (NR) that is used for the network time.
    • - nr-SFN specifies the system frame number in NR.
    • - nr-Slot specifies the slot number in NR for the indicated subcarrier spacing (SCS). The total NR network time is given by nr-SFN + nr-Slot.
  • - relativeTime provides T in seconds from current time, where current time is defined as the time the CommonIEsRequestLocationInformation was received.

NOTE 1: A location estimate returned to an LCS Client, AF or UE for a scheduled location time can be treated by the LCS Client, AF or UE as an estimate of the location of the UE at the scheduled location time (see TS 23.273 [42]).

NOTE 2: If this field is present, at least one of utcTime, gnssTime, networkTime, or relativeTime shall be present.

| +|

targetIntegrityRisk
This field indicates the TIR for which the PL is requested. The TIR is calculated by P=10^{-0.1n} [hour-1] where n is the value of targetIntegrityRisk and the range is 10^{-1} to 10^{-9} per hour.

| + +## — CommonIEsProvideLocationInformation + +The *CommonIEsProvideLocationInformation* carries common IEs for a Provide Location Information LPP message Type. + +``` +-- ASN1START +CommonIEsProvideLocationInformation ::= SEQUENCE { + locationEstimate LocationCoordinates OPTIONAL, + velocityEstimate Velocity OPTIONAL, + locationError LocationError OPTIONAL, + ... + [[ earlyFixReport-r12 EarlyFixReport-r12 OPTIONAL + ]], +} +``` + +``` + +[[ locationSource-r13 LocationSource-r13 OPTIONAL, + locationTimestamp-r13 UTCTime OPTIONAL +]], +[[ + segmentationInfo-r14 SegmentationInfo-r14 OPTIONAL -- Cond Segmentation +]], +[[ + integrityInfo-r17 IntegrityInfo-r17 OPTIONAL +]] +} + +LocationCoordinates ::= CHOICE { + ellipsoidPoint Ellipsoid-Point, + ellipsoidPointWithUncertaintyCircle Ellipsoid-PointWithUncertaintyCircle, + ellipsoidPointWithUncertaintyEllipse Ellipsoid-PointWithUncertaintyEllipse, + polygon Polygon, + ellipsoidPointWithAltitude Ellipsoid-PointWithAltitude, + ellipsoidPointWithAltitudeAndUncertaintyEllipsoid + Ellipsoid-PointWithAltitudeAndUncertaintyEllipsoid, + ellipsoidArc EllipsoidArc, + ..., + highAccuracyEllipsoidPointWithUncertaintyEllipse-v1510 + HighAccuracyEllipsoid-PointWithUncertaintyEllipse-r15, + highAccuracyEllipsoidPointWithAltitudeAndUncertaintyEllipsoid-v1510 + HighAccuracyEllipsoid-PointWithAltitudeAndUncertaintyEllipsoid-r15, + ha-EllipsoidPointWithScalableUncertaintyEllipse-v1680 + HA-Ellipsoid-PointWithScalableUncertaintyEllipse-r16, + ha-EllipsoidPointWithAltitudeAndScalableUncertaintyEllipsoid-v1680 + HA-Ellipsoid-PointWithAltitudeAndScalableUncertaintyEllipsoid-r16, + local2dPointWithUncertaintyEllipse-v1800 Local2dPointWithUncertaintyEllipse-r18, + local3dPointWithUncertaintyEllipsoid-v1800 Local3dPointWithUncertaintyEllipsoid-r18 +} + +Velocity ::= CHOICE { + horizontalVelocity HorizontalVelocity, + horizontalWithVerticalVelocity HorizontalWithVerticalVelocity, + horizontalVelocityWithUncertainty HorizontalVelocityWithUncertainty, + horizontalWithVerticalVelocityAndUncertainty + HorizontalWithVerticalVelocityAndUncertainty, + ... +} + +LocationError ::= SEQUENCE { + locationFailureCause LocationFailureCause, + ... +} + +LocationFailureCause ::= ENUMERATED { + undefined, + requestedMethodNotSupported, + positionMethodFailure, + periodicLocationMeasurementsNotAvailable, + ... +} + +EarlyFixReport-r12 ::= ENUMERATED { + noMoreMessages, + moreMessagesOnTheWay +} + +LocationSource-r13 ::= BIT STRING { a-gnss (0), + wlan (1), + bt (2), + tbs (3), + sensor (4), + ha-gnss-v1510 (5), + motion-sensor-v1550 (6), + dl-tdoa-r16 (7), + dl-aod-r16 (8) } (SIZE(1..16)) + +IntegrityInfo-r17 ::= SEQUENCE { + horizontalProtectionLevel-r17 INTEGER (0..50000), + verticalProtectionLevel-r17 INTEGER (0..50000) OPTIONAL, + achievableTargetIntegrityRisk-r17 INTEGER (10..90) OPTIONAL, + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Segmentation | This field is optionally present, need OP, if lpp-message-segmentation-req has been received from the location server with bit 1 ( targetToServer ) set to value 1. The field shall be omitted if lpp-message-segmentation-req has not been received in this location session, or has been received with bit 1 ( targetToServer ) set to value 0. | + +| CommonIEsProvideLocationInformation field descriptions | | +|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| locationEstimate | This field provides a location estimate using one of the geographic shapes defined in TS 23.032 [15]. Coding of the values of the various fields internal to each geographic shape follow the rules in TS 23.032 [15]. The conditions for including this field are defined for the locationInformationType field in a Request Location Information message. | +| velocityEstimate | This field provides a velocity estimate using one of the velocity shapes defined in TS 23.032 [15]. Coding of the values of the various fields internal to each velocity shape follow the rules in TS 23.032 [15]. | +| locationError | This field shall be included if and only if a location estimate and measurements are not included in the LPP PDU. The field includes information concerning the reason for the lack of location information. The LocationFailureCause 'periodicLocationMeasurementsNotAvailable' shall be used by the target device if periodic location reporting was requested, but no measurements or location estimate are available when the reportingInterval expired. | +| earlyFixReport | This field shall be included if and only if the ProvideLocationInformation message contains early location measurements or an early location estimate. The target device shall set the values of this field as follows:
  • - noMoreMessages: This is the only or last ProvideLocationInformation message used to deliver the entire set of early location information.
  • - moreMessagesOnTheWay: This is one of multiple ProvideLocationInformation messages used to deliver the entire set of early location information (if early location information will not fit into a single message).
If this field is included, the IE SegmentationInfo shall not be included. | +| locationSource | This field provides the source positioning technology for the location estimate.
NOTE 1: In this version of the specification, the entry 'tbs' is used only for TBS positioning based on MBS signals.
NOTE 2: The entry 'sensor' is used only for positioning technology that uses barometric pressure sensor. The entry 'motion-sensor' is used for positioning technology that uses sensor(s) to detect displacement and movement, e.g. accelerometers, gyros, magnetometers. | +| locationTimestamp | This field provides the UTC time when the location estimate is valid and should take the form of YYMMDDhhmmssZ. | +| segmentationInfo | This field indicates whether this ProvideLocationInformation message is one of many segments, as specified in clause 4.3.5 | +| integrityInfo | This field provides the integrity result for the locationEstimate .
  • - horizontalProtectionLevel provides the HPL for the locationEstimate along the semi-major axis of the error ellipse. Scale factor 0.01 metre; range 0 – 500 metres.
  • - verticalProtectionLevel provides the VPL for the locationEstimate. Scale factor 0.01 metre; range 0 – 500 metres.
  • - achievableTargetIntegrityRisk indicates the achievable TIR for which the HPL and VPL are provided. The achievable TIR is given by P=10^{-0.1n} [hour-1] where n is the value of achievableTargetIntegrityRisk and the range is 10^{-1} to 10^{-9} per hour. If this field is absent, the achievable TIR is the same as the targetIntegrityRisk in CommonIEsRequestLocationInformation.
| + +NOTE: Void. + +## CommonIEsAbort + +The *CommonIEsAbort* carries common IEs for an Abort LPP message Type. + +``` +-- ASN1START + +CommonIEsAbort ::= SEQUENCE { + abortCause ENUMERATED { + undefined, + stopPeriodicReporting, + targetDeviceAbort, +``` + +``` + + networkAbort, + ... + stopPeriodicAssistanceDataDelivery-v1510 + } +} + +-- ASN1STOP + +``` + +#### CommonEsAbort field descriptions + +##### **abortCause** + +This IE defines the request to abort an ongoing procedure. The abort cause '*stopPeriodicReporting*' should be used by the location server to stop any ongoing location reporting configured as *periodicalReporting* or *triggeredReporting* in the *CommonEsRequestLocationInformation*. + +The abort cause '*stopPeriodicAssistanceDataDelivery*' should be used by the location server or target device to stop any ongoing periodic assistance data delivery, as specified in clauses 5.2.1a and 5.2.2a. + +### CommonEsError + +The *CommonEsError* carries common IEs for an Error LPP message Type. + +``` + +-- ASN1START + +CommonEsError ::= SEQUENCE { + errorCause ENUMERATED { + undefined, + lppMessageHeaderError, + lppMessageBodyError, + epduError, + incorrectDataValue, + ... + lppSegmentationError-v1450 + } +} + +-- ASN1STOP + +``` + +#### CommonEsError field descriptions + +##### **errorCause** + +This IE defines the cause for an error. '*lppMessageHeaderError*', '*lppMessageBodyError*' and '*epduError*' is used if a receiver is able to detect a coding error in the LPP header (i.e., in the common fields), LPP message body or in an EPDU, respectively. '*incorrectDataValue*' is used if a receiver receives an incorrect data value. '*lppSegmentationError*' is used if a receiver detects an error in LPP message segmentation. + +## 6.4.3 Common NR Positioning Information Elements + +### AreaID-CellList + +The IE *AreaID-CellList* provides the NR Cell-IDs of the TRPs belonging to a particular network area where the associated assistance data are valid. Each cell is included in only one area. + +``` + +-- ASN1START + +AreaID-CellList-r17 ::= SEQUENCE (SIZE(1..maxCellIDsPerArea-r17)) OF NR-Cell-IDs-r17 + +NR-Cell-IDs-r17 ::= SEQUENCE { + nr-CellGlobalID-r17 NCGI-r15 OPTIONAL, -- Need ON + nr-PhysCellID-r17 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-ARFCN-r17 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP + +``` + +| AreaID-CellList field descriptions | | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-CellGlobalID | This field specifies the NR Cell Global ID of the TRP belonging to a particular network area where the associated assistance data are applicable. | +| nr-PhysCellID | This field specifies the physical cell identity of the TRP belonging to a particular network area where the associated assistance data are applicable. | +| nr-ARFCN | This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID . | + +### — *CoordinateID* + +The IE *CoordinateID* is used to indicate a reference point that defines the origin of a local Cartesian Coordinate System as defined in TS 23.032 [15]. + +``` +-- ASN1START +CoordinateID-r18 ::= VisibleString (SIZE (1..256)) +-- ASN1STOP +``` + +### — *DL-PRS-ID-Info* + +The IE *DL-PRS-ID-Info* provides the IDs of the reference TRPs' DL-PRS Resources. + +``` +-- ASN1START +DL-PRS-ID-Info-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + nr-DL-PRS-ResourceID-List-r16 SEQUENCE (SIZE (1..nrMaxResourceIDs-r16)) OF + NR-DL-PRS-ResourceID-r16 + OPTIONAL, -- Need ON + nr-DL-PRS-ResourceSetID-r16 NR-DL-PRS-ResourceSetID-r16 + OPTIONAL -- Need ON +} +-- ASN1STOP +``` + +| DL-PRS-ID-Info field descriptions | | +|------------------------------------------|---------------------------------------------------------------------------------------| +| nr-DL-PRS-ResourceID-List | This field provides a list of DL-PRS Resource IDs under the same DL-PRS Resource Set. | + +### — *LCS-GCS-TranslationParameter* + +The IE *LCS-GCS-TranslationParameter* provides the angles $\alpha$ (bearing angle), $\beta$ (downtilt angle) and $\gamma$ (slant angle) for the translation of a Local Coordinate System (LCS) to a Global Coordinate System (GCS) as defined in TR 38.901 [44]. + +``` +-- ASN1START +LCS-GCS-TranslationParameter-r16 ::= SEQUENCE { + alpha-r16 INTEGER (0..359), + alpha-fine-r16 INTEGER (0..9) OPTIONAL, -- Cond AzElFine + beta-r16 INTEGER (0..359), + beta-fine-r16 INTEGER (0..9) OPTIONAL, -- Cond AzElFine + gamma-r16 INTEGER (0..359), + gamma-fine-r16 INTEGER (0..9) OPTIONAL, -- Cond AzElFine + ... +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| AzElFine | The field is mandatory present if the angles where this IE is used are provided with 0.1 degrees resolution; otherwise it is not present. | + +| LCS-GCS-TranslationParameter field descriptions | | +|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alpha | This field specifies the bearing angle $\alpha$ for the translation of the LCS to a GCS as defined in TR 38.901 [44].
Scale factor 1 degree; range 0 to 359 degrees. | +| alpha-fine | This field provides finer granularity for the alpha .
The total bearing angle $\alpha$ is given by alpha + alpha-fine .
Scale factor 0.1 degrees; range 0 to 0.9 degrees. | +| beta | This field specifies the downtilt angle $\beta$ for the translation of the LCS to a GCS as defined in TR 38.901 [44].
Scale factor 1 degree; range 0 to 359 degrees. | +| beta-fine | This field provides finer granularity for the beta .
The total downtilt angle $\beta$ is given by beta + beta-fine .
Scale factor 0.1 degrees; range 0 to 0.9 degrees. | +| gamma | This field specifies the slant angle $\gamma$ for the translation of the LCS to a GCS as defined in TR 38.901 [44].
Scale factor 1 degree; range 0 to 359 degrees. | +| gamma-fine | This field provides finer granularity for the gamma .
The total slant angle $\gamma$ is given by gamma + gamma-fine .
Scale factor 0.1 degrees; range 0 to 0.9 degrees. | + +## — LOS-NLOS-Indicator + +The IE *LOS-NLOS-Indicator* provides information on the likelihood of a Line-of-Sight (LOS) propagation path from the source to the receiver. + +``` +-- ASN1START +LOS-NLOS-Indicator-r17 ::= SEQUENCE { + indicator-r17 CHOICE { + soft-r17 INTEGER (0..10), + hard-r17 BOOLEAN + }, + ... +} +-- ASN1STOP +``` + +| LOS-NLOS-Indicator field descriptions | | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| indicator | This field provides information on the likelihood of a Line-of-Sight propagation path from the source to the receiver with a value of 1 corresponding to LoS and a value of 0 corresponding to NLoS.
  • - soft: Integer value '0' indicates likelihood 0, integer value '10' indicates likelihood 1.
    Scale factor 0.1; range 0 to 1.
  • - hard: FALSE indicates likelihood '0', TRUE indicates likelihood '1'.
| + +## — LOS-NLOS-IndicatorGranularity1 + +The IE *LOS-NLOS-IndicatorGranularity1* provides information on the *LOS-NLOS-Indicator* granularity. + +``` +-- ASN1START +LOS-NLOS-IndicatorGranularity1-r17 ::= ENUMERATED { trpspecific, resourcespecific } +-- ASN1STOP +``` + +### — LOS-NLOS-IndicatorGranularity2 + +The IE *LOS-NLOS-IndicatorGranularity2* provides information on the *LOS-NLOS-Indicator* granularity. + +``` +-- ASN1START +LOS-NLOS-IndicatorGranularity2-r17 ::= ENUMERATED { trpspecific, resourcespecific, both } +-- ASN1STOP +``` + +### — LOS-NLOS-IndicatorType1 + +The IE *LOS-NLOS-IndicatorType1* provides information on the *LOS-NLOS-Indicator* type that is requested by the location server. + +``` +-- ASN1START +LOS-NLOS-IndicatorType1-r17 ::= ENUMERATED { hardvalue, softvalue } +-- ASN1STOP +``` + +### — LOS-NLOS-IndicatorType2 + +The IE *LOS-NLOS-IndicatorType2* provides information on the *LOS-NLOS-Indicator* type that is supported by the target device. + +``` +-- ASN1START +LOS-NLOS-IndicatorType2-r17 ::= ENUMERATED { hardvalue, hardAndsoftvalue } +-- ASN1STOP +``` + +### — NR-AdditionalPathList + +The IE *NR-AdditionalPathList* is used by the target device to provide information about additional paths in association to the TOA measurements associated to NR positioning in the form of a relative time difference and a quality value. The additional path *nr-RelativeTimeDifference* is the detected path timing relative to the detected path timing used for the TOA value, and each additional path can be associated with a quality value *nr-PathQuality*. + +``` +-- ASN1START +NR-AdditionalPathList-r16 ::= SEQUENCE (SIZE(1..2)) OF NR-AdditionalPath-r16 +NR-AdditionalPathListExt-r17 ::= SEQUENCE (SIZE(1..8)) OF NR-AdditionalPath-r16 +NR-AdditionalPath-r16 ::= SEQUENCE { + nr-RelativeTimeDifference-r16 CHOICE { + k0-r16 INTEGER(0..16351), + k1-r16 INTEGER(0..8176), + k2-r16 INTEGER(0..4088), + k3-r16 INTEGER(0..2044), + k4-r16 INTEGER(0..1022), + k5-r16 INTEGER(0..511), + ..., + kMinus1-r18 INTEGER(0..32701), + kMinus2-r18 INTEGER(0..65401) + }, + nr-PathQuality-r16 NR-TimingQuality-r16 OPTIONAL, + ..., + [[ + nr-DL-PRS-RSRP-r17 INTEGER (0..126) OPTIONAL + ]] +} +-- ASN1STOP +``` + +| NR-AdditionalPathList field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-RelativeTimeDifference
This field specifies the additional detected path timing relative to the detected path timing of the reference resource. The mapping of reported values and measured quantity value is defined in TS 38.133 [46] clause 10.1.23.3.3 and 10.1.25.3.3. A positive value indicates that the particular path is later in time than the detected path of the reference; a negative value indicates that the particular path is earlier in time than the detected path of the reference. | +| nr-PathQuality
This field specifies the target device's best estimate of the quality of the detected timing of the additional path. | +| nr-DL-PRS-RSRPP
This field specifies the DL PRS reference signal received path power (DL PRS-RSRPP) of the NR-AdditionalPath reported, as defined in TS 38.215 [36]. The mapping of the quantity is defined as in TS 38.133 [46]. | + +## – NR-AggregatedDL-PRS-ResourceSetID-Element + +The IE *NR-AggregatedDL-PRS-ResourceSetID-Element* is used by the target device to indicate each of the aggregated PRS resource set and the PRS resource to UE. + +``` +-- ASN1START +NR-AggregatedDL-PRS-ResourceSetID-Element-r18 ::= SEQUENCE { + dl-PRS-ID-r18 INTEGER (0..255), + nr-DL-PRS-ResourceID-r18 NR-DL-PRS-ResourceID-r16 +} + +-- ASN1STOP +``` + +## – NR-DL-PRS-AssistanceData + +The IE *NR-DL-PRS-AssistanceData* is used by the location server to provide DL-PRS assistance data. + +NOTE 1: The location server should include at least one TRP for which the SFN can be obtained by the target device, e.g. the serving TRP. + +NOTE 2: The *nr-DL-PRS-ReferenceInfo* defines the "assistance data reference" TRP whose DL-PRS configuration is included in *nr-DL-PRS-AssistanceDataList*. The *nr-DL-PRS-SFN0-Offset's* and *nr-DL-PRS-expectedRSTD's* in *nr-DL-PRS-AssistanceDataList* are provided relative to the "assistance data reference" TRP. + +NOTE 3: The network signals a value of zero for the *nr-DL-PRS-SFN0-Offset*, *nr-DL-PRS-expectedRSTD*, and *nr-DL-PRS-expectedRSTD-uncertainty* of the "assistance data reference" TRP in *nr-DL-PRS-AssistanceDataList*. + +NOTE 4: For NR DL-TDOA positioning (see clause 6.5.10) the *nr-DL-PRS-ReferenceInfo* defines also the requested "RSTD reference". + +For DL-PRS processing, the LPP layer may inform lower layers to start performing DL-PRS measurements and provide to lower layers the information about the location of DL-PRS, e.g. DL-PRS-PointA, DL-PRS Positioning occasion information. + +``` +-- ASN1START +NR-DL-PRS-AssistanceData-r16 ::= SEQUENCE { + nr-DL-PRS-ReferenceInfo-r16 DL-PRS-ID-Info-r16, + nr-DL-PRS-AssistanceDataList-r16 SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF + NR-DL-PRS-AssistanceDataPerFreq-r16, + nr-SSB-Config-r16 SEQUENCE (SIZE (1..nrMaxTRPs-r16)) OF + NR-SSB-Config-r16 OPTIONAL, -- Need ON + ..., + [[ + nr-DL-PRS-AggregationInfo-r18 NR-DL-PRS-AggregationInfo-r18 OPTIONAL -- Need ON + ]] +} + +NR-DL-PRS-AssistanceDataPerFreq-r16 ::= SEQUENCE { + nr-DL-PRS-PositioningFrequencyLayer-r16 + NR-DL-PRS-PositioningFrequencyLayer-r16, + nr-DL-PRS-AssistanceDataPerFreq-r16 SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF +``` + +``` + +NR-DL-PRS-AssistanceDataPerTRP-r16, +... +} + +NR-DL-PRS-AssistanceDataPerTRP-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r16 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r16 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + nr-DL-PRS-SFN0-Offset-r16 NR-DL-PRS-SFN0-Offset-r16, + nr-DL-PRS-ExpectedRSTD-r16 INTEGER (-3841..3841), + nr-DL-PRS-ExpectedRSTD-Uncertainty-r16 INTEGER (0..246), + nr-DL-PRS-Info-r16 NR-DL-PRS-Info-r16, + ... + [[ + prs-OnlyTP-r16 ENUMERATED { true } OPTIONAL -- Need ON + ]], + [[ + nr-DL-PRS-ExpectedAoD-or-AoA-r17 + NR-DL-PRS-ExpectedAoD-or-AoA-r17 OPTIONAL -- Need ON + ]] +} + +NR-DL-PRS-PositioningFrequencyLayer-r16 ::= SEQUENCE { + dl-PRS-SubcarrierSpacing-r16 ENUMERATED {kHz15, kHz30, kHz60, kHz120, ...}, + dl-PRS-ResourceBandwidth-r16 INTEGER (1..63), + dl-PRS-StartPRB-r16 INTEGER (0..2176), + dl-PRS-PointA-r16 ARFCN-ValueNR-r15, + dl-PRS-CombSizeN-r16 ENUMERATED {n2, n4, n6, n12, ...}, + dl-PRS-CyclicPrefix-r16 ENUMERATED {normal, extended, ...}, + ... +} + +NR-DL-PRS-SFN0-Offset-r16 ::= SEQUENCE { + sfn-Offset-r16 INTEGER (0..1023), + integerSubframeOffset-r16 INTEGER (0..9), + ... +} + +NR-DL-PRS-ExpectedAoD-or-AoA-r17 ::= CHOICE { + expectedAoD-r17 SEQUENCE { + expectedDL-AzimuthAoD-r17 INTEGER (0..359), + expectedDL-AzimuthAoD-Unc-r17 INTEGER (0..60) OPTIONAL, -- Need OP + expectedDL-ZenithAoD-r17 INTEGER (0..180), + expectedDL-ZenithAoD-Unc-r17 INTEGER (0..30) OPTIONAL -- Need OP + }, + expectedAoA-r17 SEQUENCE { + expectedDL-AzimuthAoA-r17 INTEGER (0..359), + expectedDL-AzimuthAoA-Unc-r17 INTEGER (0..60) OPTIONAL, -- Need OP + expectedDL-ZenithAoA-r17 INTEGER (0..180), + expectedDL-ZenithAoA-Unc-r17 INTEGER (0..30) OPTIONAL -- Need OP + } +} + +NR-DL-PRS-AggregationInfo-r18 ::= SEQUENCE (SIZE (1..nrMaxNumPRS-BandWidthAggregation-r18)) OF + NR-linkedDL-PRS-ResourceSetID-ListPRS-Aggregation-r18 + +NR-linkedDL-PRS-ResourceSetID-ListPRS-Aggregation-r18 ::= SEQUENCE (SIZE (2..3)) OF + NR-DL-PRS-AggregationElement-r18 + +NR-DL-PRS-AggregationElement-r18 ::= SEQUENCE { + nr-DL-PRS-FrequencyLayerIndex-r18 INTEGER (0..nrMaxFreqLayers-1-r16), + nr-DL-PRS-TRP-Index-r18 INTEGER (0..nrMaxTRPsPerFreq-1-r16), + nr-DL-PRS-ResourceSetIndex-r18 INTEGER (0..nrMaxSetsPerTrpPerFreqLayer-1-r16) +} + +-- ASN1STOP + +``` + +#### NR-DL-PRS-AssistanceData field descriptions + +##### **nr-DL-PRS-ReferenceInfo** + +This field specifies the IDs of the assistance data reference TRP. + +##### **nr-DL-PRS-AssistanceDataList** + +This field specifies the DL-PRS resources for each frequency layer. + +##### **nr-SSB-Config** + +This field specifies the SSB configuration of the TRPs. + +**nr-DL-PRS-AggregationInfo** + +This field specifies the DL-PRS Resource Sets across DL-PRS Positioning Frequency Layers available for DL-PRS bandwidth aggregation. The 2 or 3 DL-PRS Resource Sets indicated by IE *NR-linkedDL-PRS-ResourceSetID-ListPRS-Aggregation* is linked for bandwidth aggregation. + +- **nr-DL-PRS-FrequencyLayerIndex**: This field indicates the frequency layer provided in *nr-DL-PRS-AssistanceDataList*. Value 0 corresponds to the first frequency layer provided in *nr-DL-PRS-AssistanceDataList*, value 1 to the second frequency layer in *nr-DL-PRS-AssistanceDataList*, and so on. +- **nr-DL-PRS-TRP-Index**: This field indicates the TRP/DL-PRS ID provided in *nr-DL-PRS-AssistanceDataPerFreq*. Value 0 corresponds to the first TRP/DL-PRS ID provided in *nr-DL-PRS-AssistanceDataPerFreq*, value 1 to the second TRP/DL-PRS ID in *nr-DL-PRS-AssistanceDataPerFreq*, and so on. +- **nr-DL-PRS-ResourceSetIndex**: This field indicates the DL-PRS Resource Set in *nr-DL-PRS-ResourceSetList* in IE *NR-DL-PRS-Info*. Value 0 corresponds to the first DL-PRS Resource Set provided in *nr-DL-PRS-ResourceSetList*, value 1 to the second DL-PRS Resource Set in *nr-DL-PRS-ResourceSetList*. + +NOTE: The linked DL-PRS Resource Sets from two or three Positioning Frequency Layers in a *NR-linkedDL-PRS-ResourceSetID-ListPRS-Aggregation* are from the same TRP. + +**nr-DL-PRS-PositioningFrequencyLayer** + +This field specifies the Positioning Frequency Layer for the *nr-DL-PRS-AssistanceDataPerFreq* field. + +**nr-DL-PRS-AssistanceDataPerFreq** + +This field specifies the DL-PRS Resources for the TRPs within the Positioning Frequency Layer. + +**dl-PRS-ID** + +This field is used along with a DL-PRS Resource Set ID and a DL-PRS Resource ID to uniquely identify a DL-PRS Resource, and is associated with a single TRP. + +**nr-PhysCellID** + +This field specifies the physical cell identity of the TRP. When the field *prs-OnlyTP* is included, this field is not included. + +**nr-CellGlobalID** + +This field specifies the NCGI, the globally unique identity of a cell in NR, as defined in TS 38.331 [35]. When the field *prs-OnlyTP* is included, this field is not included. + +**nr-ARFCN** + +This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to *nr-PhysCellID*. When the field *prs-OnlyTP* is included, this field is not included. + +**nr-DL-PRS-SFN0-Offset** + +This field specifies the time offset of the SFN#0 slot#0 for the given TRP with respect to SFN#0 slot#0 of the assistance data reference TRP and comprises the following subfields: + +- **sfN-Offset** specifies the SFN offset at the TRP antenna location between the assistance data reference TRP and this neighbour TRP. +The offset corresponds to the number of full radio frames counted from the beginning of a radio frame #0 of the assistance data reference TRP to the beginning of the closest subsequent radio frame #0 of this neighbour TRP. +- **integerSubframeOffset** specifies the frame boundary offset at the TRP antenna location between the assistance data reference TRP and this neighbour TRP counted in full subframes. +The offset corresponds to the number of full subframes counted from the beginning of a subframe #0 of the assistance data reference TRP to the beginning of the closest subsequent subframe #0 of this neighbour TRP. + +NOTE: The location server sets the value in accordance with the defined search window for the target device using *nr-DL-PRS-ExpectedRSTD* and *nr-DL-PRS-ExpectedRSTD-Uncertainty*. + +**nr-DL-PRS-ExpectedRSTD** + +This field indicates the RSTD value that the target device is expected to measure between this TRP and the assistance data reference TRP. The *nr-DL-PRS-ExpectedRSTD* field takes into account the expected propagation time difference as well as transmit time difference of PRS positioning occasions between the two TRPs. The resolution is $4 \times T_s$ , with $T_s = 1/(15000 \times 2048)$ seconds. + +**nr-DL-PRS-ExpectedRSTD-Uncertainty** + +This field indicates the uncertainty in *nr-DL-PRS-ExpectedRSTD* value. The uncertainty is related to the location server's a-priori estimate of the target device location. The *nr-DL-PRS-ExpectedRSTD* and *nr-DL-PRS-ExpectedRSTD-Uncertainty* together define the search window for the target device. + +The resolution R is + +- $T_s$ if all PRS resources are in frequency range 2, +- $4 \times T_s$ otherwise, + +with $T_s = 1/(15000 \times 2048)$ seconds. + +The target device may assume that the beginning of the subframe for the PRS of this TRP is received within the search window of size + +- $[-nr-DL-PRS-ExpectedRSTD-Uncertainty \times R; nr-DL-PRS-ExpectedRSTD-Uncertainty \times R]$ centred at $T_{REF} + 1$ millisecond $\times N + nr-DL-PRS-ExpectedRSTD \times 4 \times T_s$ , + +where $T_{REF}$ is the reception time of the beginning of the subframe for the PRS of the assistance data reference TRP at the target device antenna connector, and N can be calculated based on + +- *nr-DL-PRS-SFN0-Offset* +- *dl-PRS-Periodicity-and-ResourceSetSlotOffset* +- *dl-PRS-ResourceSlotOffset*. + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-DL-PRS-Info
This field specifies the PRS configuration of the TRP. | +| dl-PRS-SubcarrierSpacing
This field specifies the subcarrier spacing of the DL-PRS Resource. 15, 30, 60 kHz for FR1; 60, 120 kHz for FR2. All DL-PRS Resources and DL-PRS Resource Sets in the same Positioning Frequency layer have the same value of dl-PRS-SubcarrierSpacing . | +| dl-PRS-ResourceBandwidth
This field specifies the number of PRBs allocated for the DL-PRS Resource (allocated DL-PRS bandwidth) in multiples of 4 PRBs. All DL-PRS Resources of the DL-PRS Resource Set have the same bandwidth. All DL-PRS Resource Sets belonging to the same Positioning Frequency Layer have the same value of DL-PRS Bandwidth and Start PRB.
Integer value 1 corresponds to 24 PRBs, value 2 corresponds to 28 PRBs, value 3 corresponds to 32 PRBs and so on. | +| dl-PRS-StartPRB
This field specifies the start PRB index defined as offset with respect to reference DL-PRS Point A for the Positioning Frequency Layer. All DL-PRS Resources Sets belonging to the same Positioning Frequency Layer have the same value of dl-PRS-StartPRB . | +| dl-PRS-PointA
This field specifies the absolute frequency of the reference resource block for the DL-PRS. Its lowest subcarrier is also known as DL-PRS Point A. A single DL-PRS Point A for DL-PRS Resource allocation is provided per Positioning Frequency Layer. All DL-PRS Resources belonging to the same DL-PRS Resource Set have the same DL-PRS Point A. | +| dl-PRS-CombSizeN
This field specifies the Resource Element spacing in each symbol of the DL-PRS Resource. All DL-PRS Resource Sets belonging to the same Positioning Frequency Layer have the same value of comb size N. | +| dl-PRS-CyclicPrefix
This field specifies the Cyclic Prefix length of the DL-PRS Resource. All DL-PRS Resources Sets belonging to the same Positioning Frequency Layer have the same value of dl-PRS-CyclicPrefix . | +| prs-OnlyTP
This field, if present, indicates that the NR-DL-PRS-AssistanceData is provided for a PRS-only TP. Whether the field is present or absent should be the same for all the NR-DL-PRS-AssistanceData of all the PRS transmitted under the same TP.
The target device shall not assume that any other signals or physical channels are present for the TRP other than DL-PRS. | +| nr-DL-PRS-ExpectedAoD-or-AoA
This field specifies the expected AoD or AoA in the Global Coordinate System (GCS) at the target device location together with uncertainty.
  • - expectedDL-AzimuthAoD: This field specifies the expected azimuth angle of departure.
    Scale factor 1 degree; range 0 to 359 degrees.
  • - expectedDL-AzimuthAoD-Unc: This field specifies the (single-sided) uncertainty of the expected azimuth angle of departure. If this field is absent, it indicates maximum uncertainty (60 degrees).
    Scale factor 1 degree; range 0 to 60 degrees.
  • - expectedDL-ZenithAoD: This field specifies the expected elevation angle of departure.
    Scale factor 1 degree; range 0 to 180 degrees.
  • - expectedDL-ZenithAoD-Unc: This field specifies the (single-sided) uncertainty of the expected elevation angle of departure. If this field is absent, it indicates maximum uncertainty (30 degrees).
    Scale factor 1 degree; range 0 to 30 degrees.
  • - expectedDL-AzimuthAoA: This field specifies the expected azimuth angle of arrival.
    Scale factor 1 degree; range 0 to 359 degrees.
  • - expectedDL-AzimuthAoA-Unc: This field specifies the (single-sided) uncertainty of the expected azimuth angle of arrival. If this field is absent, it indicates maximum uncertainty (60 degrees).
    Scale factor 1 degree; range 0 to 60 degrees.
  • - expectedDL-ZenithAoA: This field specifies the expected elevation angle of arrival.
    Scale factor 1 degree; range 0 to 180 degrees.
  • - expectedDL-ZenithAoA-Unc: This field specifies the (single-sided) uncertainty of the expected elevation angle of arrival. If this field is absent, it indicates maximum uncertainty (30 degrees).
    Scale factor 1 degree; range 0 to 30 degrees.
| + +## NR-DL-PRS-BeamInfo + +The IE *NR-DL-PRS-BeamInfo* is used by the location server to provide spatial direction information of the DL-PRS Resources together with integrity information. + +-- ASN1START + +NR-DL-PRS-BeamInfo-r16 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF + +``` + +NR-DL-PRS-BeamInfoPerFreqLayer-r16 +NR-DL-PRS-BeamInfoPerFreqLayer-r16 ::= SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF + NR-DL-PRS-BeamInfoPerTRP-r16 +NR-DL-PRS-BeamInfoPerTRP-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r16 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r16 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + associated-DL-PRS-ID-r16 INTEGER (0..255) OPTIONAL, -- Need OP + lcs-GCS-TranslationParameter-r16 + LCS-GCS-TranslationParameter-r16 + OPTIONAL, -- Need OP + dl-PRS-BeamInfoSet-r16 DL-PRS-BeamInfoSet-r16 OPTIONAL, -- Need OP + ... +} +DL-PRS-BeamInfoSet-r16 ::= SEQUENCE (SIZE (1..nrMaxSetsPerTrpPerFreqLayer-r16)) OF + DL-PRS-BeamInfoResourceSet-r16 +DL-PRS-BeamInfoResourceSet-r16 ::= SEQUENCE (SIZE (1..nrMaxResourcesPerSet-r16)) OF + DL-PRS-BeamInfoElement-r16 +DL-PRS-BeamInfoElement-r16 ::= SEQUENCE { + dl-PRS-Azimuth-r16 INTEGER (0..359), + dl-PRS-Azimuth-fine-r16 INTEGER (0..9) OPTIONAL, -- Need ON + dl-PRS-Elevation-r16 INTEGER (0..180) OPTIONAL, -- Need ON + dl-PRS-Elevation-fine-r16 INTEGER (0..9) OPTIONAL, -- Need ON + ... + [ + integrityBeamInfoBounds-r18 + IntegrityBeamInfoBounds-r18 + OPTIONAL -- Need OP + ] +} +IntegrityBeamInfoBounds-r18 ::= SEQUENCE { + meanAzimuth-r18 INTEGER (0..128), + stdDevAzimuth-r18 INTEGER (0..255), + meanElevation-r18 INTEGER (0..128), + stdDevElevation-r18 INTEGER (0..255), + ... +} +-- ASN1STOP + +``` + +#### NR-DL-PRS-BeamInfo field descriptions + +##### **dl-PRS-ID** + +This field is used along with a DL-PRS Resource Set ID and a DL-PRS Resources ID to uniquely identify a DL-PRS Resource. This ID can be associated with multiple DL-PRS Resource Sets associated with a single TRP. Each TRP should only be associated with one such ID. + +##### **nr-PhysCellID** + +This field specifies the physical cell identity of the associated TRP, as defined in TS 38.331 [35]. + +##### **nr-CellGlobalID** + +This field specifies the NCGI, the globally unique identity of a cell in NR, of the associated TRP, as defined in TS 38.331 [35]. The server should include this field if it considers that it is needed to resolve ambiguity in the TRP indicated by *nr-PhysCellID*. + +##### **nr-ARFCN** + +This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to *nr-PhysCellID*. + +##### **associated-DL-PRS-ID** + +This field specifies the *dl-PRS-ID* of the associated TRP from which the beam information is obtained. See the field descriptions of *dl-PRS-BeamInfoSet* and *lcs-GCS-TranslationParameter*. + +##### **lcs-GCS-TranslationParameter** + +This field provides the angles $\alpha$ (bearing angle), $\beta$ (downtilt angle) and $\gamma$ (slant angle) for the translation of a Local Coordinate System (LCS) to a Global Coordinate System (GCS) as defined in TR 38.901 [44]. If this field and the field *associated-DL-PRS-ID* are absent, the *dl-PRS-Azimuth* and *dl-PRS-Elevation* are provided in a GCS. If this field is absent and the *associated-DL-PRS-ID* field is present, then the *lcs-GCS-TranslationParameter* for this TRP is obtained from the *lcs-GCS-TranslationParameter* of the associated TRP. + +##### **dl-PRS-BeamInfoSet** + +This field provides the DL-PRS beam information for each DL-PRS Resource of the DL-PRS Resource Set associated with this TRP. If this field is absent and the field *associated-DL-PRS-ID* is present, the *dl-PRS-BeamInfoSet* for this TRP are obtained from the *dl-PRS-BeamInfoSet* of the associated TRP. + +**dl-PRS-Azimuth** + +This field specifies the azimuth angle of the boresight direction in which the DL-PRS Resources associated with this DL-PRS Resource ID in the DL-PRS Resource Set are transmitted. + +For a Global Coordinate System (GCS), the azimuth angle is measured counter-clockwise from geographical North. + +For a Local Coordinate System (LCS), the azimuth angle is measured counter-clockwise from the x-axis of the LCS. + +Scale factor 1 degree; range 0 to 359 degrees. + +**dl-PRS-Azimuth-fine** + +This field provides finer granularity for the *dl-PRS-Azimuth*. + +The total azimuth angle of the boresight direction is given by *dl-PRS-Azimuth* + *dl-PRS-Azimuth-fine*. + +Scale factor 0.1 degrees; range 0 to 0.9 degrees. + +**dl-PRS-Elevation** + +This field specifies the elevation angle of the boresight direction in which the DL-PRS Resources associated with this DL-PRS Resource ID in the DL-PRS Resource Set are transmitted. + +For a Global Coordinate System (GCS), the elevation angle is measured relative to zenith and positive to the horizontal direction (elevation 0 deg. points to zenith, 90 deg to the horizon). + +For a Local Coordinate System (LCS), the elevation angle is measured relative to the z-axis of the LCS (elevation 0 deg. points to the z-axis, 90 deg to the x-y plane). + +Scale factor 1 degree; range 0 to 180 degrees. + +**dl-PRS-Elevation-fine** + +This field provides finer granularity for the *dl-PRS-Elevation*. + +The total elevation angle of the boresight direction is given by *dl-PRS-Elevation* + *dl-PRS-Elevation-fine*. + +Scale factor 0.1 degrees; range 0 to 0.9 degrees. + +**integrityBeamInfoBounds** + +This field provides an overbounding model that bounds the spatial direction information of the DL-PRS Resources. If this field is absent, the *integrityBeamInfoBounds* for this instance of the *DL-PRS-BeamInfoElement* is the same as the *integrityBeamInfoBounds* of the previous instance of the *DL-PRS-BeamInfoElement* in *DL-PRS-BeamInfoResourceSet*. If integrity bounds are provided, this field shall be present at least in the first instance of the *DL-PRS-BeamInfoResourceSet*. + +**meanAzimuth** + +This field specifies the Mean Azimuth Error bound which is the mean value for an overbounding model that bounds the azimuth angle error of the boresight direction in which the DL-PRS Resources associated with this DL-PRS Resource ID in the DL-PRS Resource Set are transmitted. + +The bound is *meanAzimuth* + $K \cdot \text{stdDevAzimuth}$ and shall be so that the probability of it to be exceeded shall be lower than $\text{IR}_{\text{allocation}}$ for *ir-Minimum* < $\text{IR}_{\text{allocation}}$ < *ir-Maximum*, where $K = \text{normInv}(\text{IR}_{\text{allocation}} / 2)$ and *ir-Minimum*, *ir-Maximum* as provided in IE *NR-Integrity-ServiceParameters*. + +This $\text{IR}_{\text{allocation}}$ is a fraction of the Target Integrity Risk that represents the integrity risk budget available. + +Scale factor 0.1 degrees; range 0-12.8 degrees. + +**stdDevAzimuth** + +This field specifies the Standard Deviation Azimuth Error bound which is the standard deviation for an overbounding model that bounds the Azimuth error of the boresight direction in which the DL-PRS Resources associated with this DL-PRS Resource ID in the DL-PRS Resource Set are transmitted. + +Scale factor 0.1 degrees; range 0-25.5 degrees. + +**meanElevation** + +This field specifies the Mean Elevation Error bound which is the mean value for an overbounding model that bounds the elevation angle error of the boresight direction in which the DL-PRS Resources associated with this DL-PRS Resource ID in the DL-PRS Resource Set are transmitted. + +The bound is *meanElevation* + $K \cdot \text{stdDevElevation}$ and shall be so that the probability of it to be exceeded shall be lower than $\text{IR}_{\text{allocation}}$ for *ir-Minimum* < $\text{IR}_{\text{allocation}}$ < *ir-Maximum*, where $K = \text{normInv}(\text{IR}_{\text{allocation}} / 2)$ and *ir-Minimum*, *ir-Maximum* as provided in IE *NR-Integrity-ServiceParameters*. + +This $\text{IR}_{\text{allocation}}$ is a fraction of the Target Integrity Risk that represents the integrity risk budget available. + +Scale factor 0.1 degrees; range 0-12.8 degrees. + +**stdDevElevation** + +This field specifies the Standard Deviation Elevation Error bound which is the standard deviation for an overbounding model that bounds the Elevation error of the boresight direction in which the DL-PRS Resources associated with this DL-PRS Resource ID in the DL-PRS Resource Set are transmitted. + +Scale factor 0.1 degrees; range 0-25.5 degrees. + +## NR-DL-PRS-ExpectedLOS-NLOS-Assistance + +The IE *NR-DL-PRS-ExpectedLOS-NLOS-Assistance* is used by the location server to provide the expected likelihood of a LOS propagation path from a TRP to the target device, or for all DL-PRS Resources of the TRP to the target device. + +-- ASN1START + +``` +NR-DL-PRS-ExpectedLOS-NLOS-Assistance-r17 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF + NR-DL-PRS-ExpectedLOS-NLOS-AssistancePerFreqLayer-r17 +``` + +``` + +NR-DL-PRS-ExpectedLOS-NLOS-AssistancePerFreqLayer-r17 ::= + SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF + NR-DL-PRS-ExpectedLOS-NLOS-AssistancePerTRP-r17 + +NR-DL-PRS-ExpectedLOS-NLOS-AssistancePerTRP-r17 ::= SEQUENCE { + dl-PRS-ID-r17 INTEGER (0..255), + nr-PhysCellID-r17 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r17 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r17 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + nr-los-nlos-indicator-r17 CHOICE { + perTrp-r17 LOS-NLOS-Indicator-r17, + perResource-r17 SEQUENCE (SIZE (1..nrMaxSetsPerTrpPerFreqLayer-r16)) OF + NR-DL-PRS-ExpectedLOS-NLOS-AssistancePerResource-r17 + }, + ... +} + +NR-DL-PRS-ExpectedLOS-NLOS-AssistancePerResource-r17 ::= + SEQUENCE (SIZE (1..nrMaxResourcesPerSet-r16)) OF + LOS-NLOS-Indicator-r17 + +-- ASN1STOP + +``` + +#### ***NR-DL-PRS-ExpectedLOS-NLOS-Assistance* field descriptions** + +| | | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PRS-ID | This field specifies the DL-PRS ID of the TRP for which the LOS/NLOS Information is provided. | +| nr-PhysCellID | This field specifies the physical Cell-ID of the TRP for which the LOS/NLOS Information is provided, as defined in TS 38.331 [35]. | +| nr-CellGlobalID | This field specifies the NCGI, the globally unique identity of a cell in NR, of the TRP for which the LOS/NLOS Information is provided, as defined in TS 38.331 [35]. | +| nr-ARFCN | This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID . | +| nr-los-nlos-indicator | This field provides the expected likelihood of a LOS propagation path from a TRP to the target device (choice perTrp ) or for all DL-PRS Resources of the TRP (choice perResource ). | + +## NR-DL-PRS-Info + +The IE *NR-DL-PRS-Info* defines downlink PRS configuration. + +``` + +-- ASN1START + +NR-DL-PRS-Info-r16 ::= SEQUENCE { + nr-DL-PRS-ResourceSetList-r16 SEQUENCE (SIZE (1..nrMaxSetsPerTrpPerFreqLayer-r16)) OF + NR-DL-PRS-ResourceSet-r16, + ... +} + +NR-DL-PRS-ResourceSet-r16 ::= SEQUENCE { + nr-DL-PRS-ResourceSetID-r16 NR-DL-PRS-ResourceSetID-r16, + dl-PRS-Periodicity-and-ResourceSetSlotOffset-r16 + NR-DL-PRS-Periodicity-and-ResourceSetSlotOffset-r16, + dl-PRS-ResourceRepetitionFactor-r16 ENUMERATED {n2, n4, n6, n8, n16, n32, ...} + OPTIONAL, -- Need OP + dl-PRS-ResourceTimeGap-r16 ENUMERATED {s1, s2, s4, s8, s16, s32, ...} + OPTIONAL, -- Cond Rep + dl-PRS-NumSymbols-r16 ENUMERATED {n2, n4, n6, n12, ..., n1-v1800 }, + dl-PRS-MutingOption1-r16 DL-PRS-MutingOption1-r16 OPTIONAL, -- Need OP + dl-PRS-MutingOption2-r16 DL-PRS-MutingOption2-r16 OPTIONAL, -- Need OP + dl-PRS-ResourcePower-r16 INTEGER (-60..50), + dl-PRS-ResourceList-r16 SEQUENCE (SIZE (1..nrMaxResourcesPerSet-r16)) OF + NR-DL-PRS-Resource-r16, + ... +} + +DL-PRS-MutingOption1-r16 ::= SEQUENCE { + dl-prs-MutingBitRepetitionFactor-r16 + ENUMERATED { n1, n2, n4, n8, ... } OPTIONAL, -- Need OP +} + +``` + +``` + + nr-option1-muting-r16 NR-MutingPattern-r16, + ... +} + +DL-PRS-MutingOption2-r16 ::= SEQUENCE { + nr-option2-muting-r16 NR-MutingPattern-r16, + ... +} + +NR-MutingPattern-r16 ::= CHOICE { + po2-r16 BIT STRING (SIZE(2)), + po4-r16 BIT STRING (SIZE(4)), + po6-r16 BIT STRING (SIZE(6)), + po8-r16 BIT STRING (SIZE(8)), + po16-r16 BIT STRING (SIZE(16)), + po32-r16 BIT STRING (SIZE(32)), + ... +} + +NR-DL-PRS-Resource-r16 ::= SEQUENCE { + nr-DL-PRS-ResourceID-r16 NR-DL-PRS-ResourceID-r16, + dl-PRS-SequenceID-r16 INTEGER (0.. 4095), + dl-PRS-CombSizeN-AndReOffset-r16 CHOICE { + n2-r16 INTEGER (0..1), + n4-r16 INTEGER (0..3), + n6-r16 INTEGER (0..5), + n12-r16 INTEGER (0..11), + ... + }, + dl-PRS-ResourceSlotOffset-r16 INTEGER (0..nrMaxResourceOffsetValue-1-r16), + dl-PRS-ResourceSymbolOffset-r16 INTEGER (0..12), + dl-PRS-QCL-Info-r16 DL-PRS-QCL-Info-r16 OPTIONAL, --Need ON + ..., + [[ + dl-PRS-ResourcePrioritySubset-r17 DL-PRS-ResourcePrioritySubset-r17 OPTIONAL -- Need ON + ]], + [[ + dl-PRS-ResourceSymbolOffset-v1800 INTEGER (13) OPTIONAL -- Need OR + ]] +} + +DL-PRS-QCL-Info-r16 ::= CHOICE { + ssb-r16 SEQUENCE { + pci-r16 NR-PhysCellID-r16, + ssb-Index-r16 INTEGER (0..63), + rs-Type-r16 ENUMERATED {typeC, typeD, typeC-plus-typeD} + }, + dl-PRS-r16 SEQUENCE { + qcl-DL-PRS-ResourceID-r16 NR-DL-PRS-ResourceID-r16, + qcl-DL-PRS-ResourceSetID-r16 NR-DL-PRS-ResourceSetID-r16 + } +} + +NR-DL-PRS-Periodicity-and-ResourceSetSlotOffset-r16 ::= CHOICE { + scs15-r16 CHOICE { + n4-r16 INTEGER (0..3), + n5-r16 INTEGER (0..4), + n8-r16 INTEGER (0..7), + n10-r16 INTEGER (0..9), + n16-r16 INTEGER (0..15), + n20-r16 INTEGER (0..19), + n32-r16 INTEGER (0..31), + n40-r16 INTEGER (0..39), + n64-r16 INTEGER (0..63), + n80-r16 INTEGER (0..79), + n160-r16 INTEGER (0..159), + n320-r16 INTEGER (0..319), + n640-r16 INTEGER (0..639), + n1280-r16 INTEGER (0..1279), + n2560-r16 INTEGER (0..2559), + n5120-r16 INTEGER (0..5119), + n10240-r16 INTEGER (0..10239), + ... + }, + scs30-r16 CHOICE { + n8-r16 INTEGER (0..7), + n10-r16 INTEGER (0..9), + n16-r16 INTEGER (0..15), + } +} + +``` + +``` + + n20-r16 INTEGER (0..19), + n32-r16 INTEGER (0..31), + n40-r16 INTEGER (0..39), + n64-r16 INTEGER (0..63), + n80-r16 INTEGER (0..79), + n128-r16 INTEGER (0..127), + n160-r16 INTEGER (0..159), + n320-r16 INTEGER (0..319), + n640-r16 INTEGER (0..639), + n1280-r16 INTEGER (0..1279), + n2560-r16 INTEGER (0..2559), + n5120-r16 INTEGER (0..5119), + n10240-r16 INTEGER (0..10239), + n20480-r16 INTEGER (0..20479), + ... + }, + scs60-r16 CHOICE { + n16-r16 INTEGER (0..15), + n20-r16 INTEGER (0..19), + n32-r16 INTEGER (0..31), + n40-r16 INTEGER (0..39), + n64-r16 INTEGER (0..63), + n80-r16 INTEGER (0..79), + n128-r16 INTEGER (0..127), + n160-r16 INTEGER (0..159), + n256-r16 INTEGER (0..255), + n320-r16 INTEGER (0..319), + n640-r16 INTEGER (0..639), + n1280-r16 INTEGER (0..1279), + n2560-r16 INTEGER (0..2559), + n5120-r16 INTEGER (0..5119), + n10240-r16 INTEGER (0..10239), + n20480-r16 INTEGER (0..20479), + n40960-r16 INTEGER (0..40959), + ... + }, + scs120-r16 CHOICE { + n32-r16 INTEGER (0..31), + n40-r16 INTEGER (0..39), + n64-r16 INTEGER (0..63), + n80-r16 INTEGER (0..79), + n128-r16 INTEGER (0..127), + n160-r16 INTEGER (0..159), + n256-r16 INTEGER (0..255), + n320-r16 INTEGER (0..319), + n512-r16 INTEGER (0..511), + n640-r16 INTEGER (0..639), + n1280-r16 INTEGER (0..1279), + n2560-r16 INTEGER (0..2559), + n5120-r16 INTEGER (0..5119), + n10240-r16 INTEGER (0..10239), + n20480-r16 INTEGER (0..20479), + n40960-r16 INTEGER (0..40959), + n81920-r16 INTEGER (0..81919), + ... + }, + ... +} + +DL-PRS-ResourcePrioritySubset-r17 ::= SEQUENCE (SIZE (1..maxNumPrioResources-r17)) OF + NR-DL-PRSResourcePriorityItem-r17 + +NR-DL-PRSResourcePriorityItem-r17 ::= SEQUENCE { + nr-DL-PRS-PrioResourceSetID-r17 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, -- Cond NotSame + nr-DL-PRS-PrioResourceID-r17 NR-DL-PRS-ResourceID-r16, + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Rep | The field is mandatory present, if dl-PRS-ResourceRepetitionFactor is present. Otherwise it is not present. | +| NotSame | The field is optionally present, need OP. If the field is absent, the indicated nr-DL-PRS-PrioResourceID belongs to the same DL-PRS Resource Set as the nr-DL-PRS-ResourceID . | + +| NR-DL-PRS-Info field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

nr-DL-PRS-ResourceSetID
This field specifies the DL-PRS Resource Set ID, which is used to identify the DL-PRS Resource Set of the TRP across all the frequency layers.

| +|

dl-PRS-Periodicity-and-ResourceSetSlotOffset
This field specifies the periodicity of DL-PRS allocation in slots configured per DL-PRS Resource Set and the slot offset with respect to SFN #0 slot #0 for a TRP where the DL-PRS Resource Set is configured (i.e. slot where the first DL-PRS Resource of DL-PRS Resource Set occurs).

| +|

dl-PRS-ResourceRepetitionFactor
This field specifies how many times each DL-PRS Resource is repeated for a single instance of the DL-PRS Resource Set. It is applied to all resources of the DL-PRS Resource Set. Enumerated values n2, n4, n6, n8, n16, n32 correspond to 2, 4, 6, 8, 16, 32 resource repetitions, respectively. If this field is absent, the value for dl-PRS-ResourceRepetitionFactor is 1 (i.e., no resource repetition).

| +|

dl-PRS-ResourceTimeGap
This field specifies the offset in units of slots between two repeated instances of a DL-PRS Resource corresponding to the same DL-PRS Resource ID within a single instance of the DL-PRS Resource Set. The time duration spanned by one DL-PRS Resource Set containing repeated DL-PRS Resources should not exceed DL-PRS-Periodicity.

| +|

dl-PRS-NumSymbols
This field specifies the number of symbols per DL-PRS Resource within a slot.

| +|

dl-PRS-MutingOption1
This field specifies the DL-PRS muting configuration of the TRP for the Option-1 muting, as specified in TS 38.214 [45], and comprises the following sub-fields:

  • - dl-prs-MutingBitRepetitionFactor indicates the number of consecutive instances of the DL-PRS Resource Set corresponding to a single bit of the nr-option1-muting bit map. Enumerated values n1, n2, n4, n8 correspond to 1, 2, 4, 8 consecutive instances, respectively. If this sub-field is absent, the value for dl-prs-MutingBitRepetitionFactor is n1.
  • - nr-option1-muting defines a bitmap of the time locations where the DL-PRS Resource is transmitted (value '1') or not (value '0') for a DL-PRS Resource Set, as specified in TS 38.214 [45].

If this field is absent, Option-1 muting is not in use for the TRP.

| +|

dl-PRS-MutingOption2
This field specifies the DL-PRS muting configuration of the TRP for the Option-2 muting, as specified in TS 38.214 [45], and comprises the following sub-fields:

  • - nr-option2-muting defines a bitmap of the time locations where the DL-PRS Resource is transmitted (value '1') or not (value '0'). Each bit of the bitmap corresponds to a single repetition of the DL-PRS Resource within an instance of a DL-PRS Resource Set, as specified in TS 38.214 [45]. The size of this bitmap should be the same as the value for dl-PRS-ResourceRepetitionFactor.

If this field is absent, Option-2 muting is not in use for the TRP.

| +|

dl-PRS-ResourcePower
This field specifies the average EPRE of the resources elements that carry the PRS in dBm that is used for PRS transmission. The UE assumes constant EPRE is used for all REs of a given DL-PRS resource.

| +|

dl-PRS-SequenceID
This field specifies the sequence Id used to initialize cinit value used in pseudo random generator TS 38.211 [41], clause 5.2.1 for generation of DL-PRS sequence for transmission on a given DL-PRS Resource.

| +|

dl-PRS-CombSizeN-AndReOffset
This field specifies the Resource Element spacing in each symbol of the DL-PRS Resource and the Resource Element (RE) offset in the frequency domain for the first symbol in a DL-PRS Resource. All DL-PRS Resource Sets belonging to the same Positioning Frequency Layer have the same value of comb size. The relative RE offsets of following symbols are defined relative to the RE Offset in the frequency domain of the first symbol in the DL-PRS Resource according to TS 38.211 [41]. The comb size configuration should be aligned with the comb size configuration for the frequency layer.

| +|

dl-PRS-ResourceSlotOffset
This field specifies the starting slot of the DL-PRS Resource with respect to the corresponding DL-PRS-Resource Set Slot Offset.

| +|

dl-PRS-ResourceSymbolOffset
This field specifies the starting symbol of the DL-PRS Resource within a slot determined by dl-PRS-ResourceSlotOffset. If dl-PRS-ResourceSymbolOffset-v1800 is present, the target device shall ignore dl-PRS-ResourceSymbolOffset-r16.

| + +**dl-PRS-QCL-Info** + +This field specifies the QCL indication with other DL reference signals for serving and neighbouring cells and comprises the following subfields: + +- **ssb** indicates the SSB information for QCL source and comprises the following sub-fields: + - **pci** specifies the physical cell ID of the cell with the SSB that is configured as the source reference signal for the DL-PRS. The UE obtains the SSB configuration for the SSB configured as source reference signal for the DL-PRS by indexing to the field *nr-SSB-Config* with this physical cell identity. + - **ssb-Index** indicates the index for the SSB configured as the source reference signal for the DL-PRS. + - **rs-Type** indicates the QCL type. +- **dl-PRS** indicates the PRS information for QCL source reference signal and comprises the followings sub-fields: + - **qcl-DL-PRS-ResourceID** specifies DL-PRS Resource ID of the DL-PRS resource used as the source reference signal. + - **qcl-DL-PRS-ResourceSetID** indicates the DL-PRS Resource Set ID of the DL-PRS Resource Set used as the source reference signal. + +**dl-PRS-ResourcePrioritySubset** + +This field provides a subset of DL-PRS Resources, which is associated with *nr-DL-PRS-ResourceID* for the purpose of prioritization of DL-AoD reporting, as specified in TS 38.214 [45]. + +NOTE: This field is only applicable to DL-AoD positioning method and should be ignored for DL-TDOA and Multi-RTT positioning. + +## NR-DL-PRS-MeasurementTimeWindowsConfig + +The IE *NR-DL-PRS-MeasurementTimeWindowsConfig* provides a set of indicated time window(s) which is configured from server to target UE or PRU to perform measurements on indicated DL PRS resource set(s) occurring within indicated time window(s) for DL CPP, DL-TDOA, Multi-RTT and DL-AoD. + +``` +-- ASN1START + +NR-DL-PRS-MeasurementTimeWindowsConfig-r18 ::= + SEQUENCE (SIZE(1..2)) OF + NR-DL-PRS-MeasurementTimeWindowsConfigElement-r18 + +NR-DL-PRS-MeasurementTimeWindowsConfigElement-r18 ::= SEQUENCE { + nr-StartSFN-TimeWindow-r18 INTEGER (0..1023), + nr-PeriodicityAndSlotOffsetTimeWindow-r18 + NR-DL-PRS-Periodicity-and-ResourceSetSlotOffset-r16 + OPTIONAL, -- Need ON + nr-SymbolOffsetTimeWindow-r18 INTEGER (0..13) + OPTIONAL, -- Need ON + nr-DurationTimeWindow-r18 ENUMERATED { n1, n2, n4, n6, n8, n12, n16, ... }, + nr-SelectedDL-PRS-FrequencyLayerIndex-r18 INTEGER (0..nrMaxFreqLayers-1-r16), + nr-SelectedDL-PRS-IndexListPerFreq-r18 + SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF + NR-SelectedDL-PRS-IndexPerTRP-r18 OPTIONAL, --Need OP + ... +} + +NR-SelectedDL-PRS-IndexPerTRP-r18 ::= SEQUENCE { + nr-SelectedTRP-Index-r18 INTEGER (0..nrMaxTRPsPerFreq-1-r16), + dl-SelectedPRS-ResourceSetIndexList-r18 SEQUENCE (SIZE (1..nrMaxSetsPerTrpPerFreqLayer-r16)) OF + INTEGER (0..nrMaxSetsPerTrpPerFreqLayer-1-r16) OPTIONAL, --Need OP + ... +} + +-- ASN1STOP +``` + +| NR-DL-PRS-MeasurementTimeWindowsConfig field descriptions | | +|------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-StartSFN-TimeWindow | This field specifies the start of the time window in system frame number. | +| nr-PeriodicityAndSlotOffsetTimeWindow | This field specifies the periodicity of the time window in slots configured per DL-PRS Resource Set and the slot offset with respect to the SFN in IE nr-StartSFN-TimeWindow slot #0 for the TRP where the DL-PRS Resource Set is configured. | +| nr-SymbolOffsetTimeWindow | This field specifies the symbol offset with respect to the slot offset in nr-PeriodicityAndSlotOffsetTimeWindow . | +| nr-DurationTimeWindow | This field specifies the desired duration of a time window for the indicated DL-PRS resource set in unit of slots. Enumerated value 'n1' corresponds to 1 slot, n2 to 2 slots, n4 to 4 slots and so on. | +| nr-SelectedDL-PRS-FrequencyLayerIndex | This field indicates the frequency layer provided in IE NR-DL-PRS-AssistanceData . Value 0 corresponds to the first frequency layer provided in nr-DL-PRS-AssistanceDataList in IE NR-DL-PRS-AssistanceData , value 1 to the second frequency layer in nr-DL-PRS-AssistanceDataList , and so on. | +| nr-SelectedDL-PRS-IndexListPerFreq | This field provides the list of addressed TRPs of the selected frequency layer. If this field is absent, all DL-PRS Resources of all TRPs of the indicated frequency layer are addressed. | +| nr-SelectedTRP-Index | This field indicates the addressed TRP of the selected frequency layer. Value 0 corresponds to the first entry in nr-DL-PRS-AssistanceDataPerFreq provided in IE NR-DL-PRS-AssistanceData , value 1 corresponds to the second entry in nr-DL-PRS-AssistanceDataPerFreq , and so on. | +| dl-SelectedPRS-ResourceSetIndexList | This field provides the list of addressed DL-PRS Resource Sets of the selected TRPs of the selected frequency layer. If this field is absent, all DL-PRS Resource Sets and Resources of the indicated TRP are addressed. | + +## NR-DL-PRS-ProcessingCapability + +The IE *NR-DL-PRS-ProcessingCapability* defines the common DL-PRS Processing capability. In the case of capabilities for multiple NR positioning methods are provided, the IE *NR-DL-PRS-ProcessingCapability* applies across the NR positioning methods and the target device shall indicate the same values for the capabilities in IEs *NR-DL-TDOA-ProvideCapabilities*, *NR-DL-AoD-ProvideCapabilities*, and *NR-Multi-RTT-ProvideCapabilities*. + +The *PRS-ProcessingCapabilityPerBand* is defined for a single positioning frequency layer on a certain band (i.e., a target device supporting multiple positioning frequency layers is expected to process one frequency layer at a time). + +``` +-- ASN1START + +NR-DL-PRS-ProcessingCapability-r16 ::= SEQUENCE { + prs-ProcessingCapabilityBandList-r16 SEQUENCE (SIZE (1..nrMaxBands-r16)) OF + PRS-ProcessingCapabilityPerBand-r16, + maxSupportedFreqLayers-r16 INTEGER (1..4), + simulLTE-NR-PRS-r16 ENUMERATED { supported } OPTIONAL, + ... + [[ + dummy ENUMERATED { m1, m2, ... } OPTIONAL + ]] +} + +PRS-ProcessingCapabilityPerBand-r16 ::= SEQUENCE { + freqBandIndicatorNR-r16 FreqBandIndicatorNR-r16, + supportedBandwidthPRS-r16 CHOICE { + fr1 ENUMERATED { mhz5, mhz10, mhz20, mhz40, + mhz50, mhz80, mhz100}, + fr2 ENUMERATED { mhz50, mhz100, mhz200, mhz400}, + ... + }, + dl-PRS-BufferType-r16 ENUMERATED { type1, type2, ...}, + durationOfPRS-Processing-r16 SEQUENCE { + durationOfPRS-ProcessingSymbols-r16 ENUMERATED { nDot125, nDot25, nDot5, n1, + n2, n4, n6, n8, n12, n16, n20, n25, + n30, n32, n35, n40, n45, n50}, + durationOfPRS-ProcessingSymbolsInEveryTms-r16 + ENUMERATED { n8, n16, n20, n30, n40, n80, + n160, n320, n640, n1280}, + ... + }, + maxNumOfDL-PRS-ResProcessedPerSlot-r16 SEQUENCE { + scs15-r16 ENUMERATED { n1, n2, n4, n8, n16, n24, n32, + n48, n64, n80, n96, n112, n128, n144, n160, n176, n192, n208, n224, n240, n256, n272, n288, n304, n320, n336, n352, n368, n384, n400, n416, n432, n448, n464, n480, n496, n512, n528, n544, n560, n576, n592, n608, n624, n640, n656, n672, n688, n704, n720, n736, n752, n768, n784, n800, n816, n832, n848, n864, n880, n896, n912, n928, n944, n960, n976, n992, n1008, n1024, n1040, n1056, n1072, n1088, n1104, n1120, n1136, n1152, n1168, n1184, n1200, n1216, n1232, n1248, n1264, n1280, n1296, n1312, n1328, n1344, n1360, n1376, n1392, n1408, n1424, n1440, n1456, n1472, n1488, n1504, n1520, n1536, n1552, n1568, n1584, n1600, n1616, n1632, n1648, n1664, n1680, n1696, n1712, n1728, n1744, n1760, n1776, n1792, n1808, n1824, n1840, n1856, n1872, n1888, n1904, n1920, n1936, n1952, n1968, n1984, n2000, n2016, n2032, n2048, n2064, n2080, n2096, n2112, n2128, n2144, n2160, n2176, n2192, n2208, n2224, n2240, n2256, n2272, n2288, n2304, n2320, n2336, n2352, n2368, n2384, n2400, n2416, n2432, n2448, n2464, n2480, n2496, n2512, n2528, n2544, n2560, n2576, n2592, n2608, n2624, n2640, n2656, n2672, n2688, n2704, n2720, n2736, n2752, n2768, n2784, n2800, n2816, n2832, n2848, n2864, n2880, n2896, n2912, n2928, n2944, n2960, n2976, n2992, n3008, n3024, n3040, n3056, n3072, n3088, n3104, n3120, n3136, n3152, n3168, n3184, n3200, n3216, n3232, n3248, n3264, n3280, n3296, n3312, n3328, n3344, n3360, n3376, n3392, n3408, n3424, n3440, n3456, n3472, n3488, n3504, n3520, n3536, n3552, n3568, n3584, n3600, n3616, n3632, n3648, n3664, n3680, n3696, n3712, n3728, n3744, n3760, n3776, n3792, n3808, n3824, n3840, n3856, n3872, n3888, n3904, n3920, n3936, n3952, n3968, n3984, n4000, n4016, n4032, n4048, n4064, n4080, n4096, n4112, n4128, n4144, n4160, n4176, n4192, n4208, n4224, n4240, n4256, n4272, n4288, n4304, n4320, n4336, n4352, n4368, n4384, n4400, n4416, n4432, n4448, n4464, n4480, n4496, n4512, n4528, n4544, n4560, n4576, n4592, n4608, n4624, n4640, n4656, n4672, n4688, n4704, n4720, n4736, n4752, n4768, n4784, n4800, n4816, n4832, n4848, n4864, n4880, n4896, n4912, n4928, n4944, n4960, n4976, n4992, n5008, n5024, n5040, n5056, n5072, n5088, n5104, n5120, n5136, n5152, n5168, n5184, n5200, n5216, n5232, n5248, n5264, n5280, n5296, n5312, n5328, n5344, n5360, n5376, n5392, n5408, n5424, n5440, n5456, n5472, n5488, n5504, n5520, n5536, n5552, n5568, n5584, n5600, n5616, n5632, n5648, n5664, n5680, n5696, n5712, n5728, n5744, n5760, n5776, n5792, n5808, n5824, n5840, n5856, n5872, n5888, n5904, n5920, n5936, n5952, n5968, n5984, n6000, n6016, n6032, n6048, n6064, n6080, n6096, n6112, n6128, n6144, n6160, n6176, n6192, n6208, n6224, n6240, n6256, n6272, n6288, n6304, n6320, n6336, n6352, n6368, n6384, n6400, n6416, n6432, n6448, n6464, n6480, n6496, n6512, n6528, n6544, n6560, n6576, n6592, n6608, n6624, n6640, n6656, n6672, n6688, n6704, n6720, n6736, n6752, n6768, n6784, n6800, n6816, n6832, n6848, n6864, n6880, n6896, n6912, n6928, n6944, n6960, n6976, n6992, n7008, n7024, n7040, n7056, n7072, n7088, n7104, n7120, n7136, n7152, n7168, n7184, n7200, n7216, n7232, n7248, n7264, n7280, n7296, n7312, n7328, n7344, n7360, n7376, n7392, n7408, n7424, n7440, n7456, n7472, n7488, n7504, n7520, n7536, n7552, n7568, n7584, n7600, n7616, n7632, n7648, n7664, n7680, n7696, n7712, n7728, n7744, n7760, n7776, n7792, n7808, n7824, n7840, n7856, n7872, n7888, n7904, n7920, n7936, n7952, n7968, n7984, n8000, n8016, n8032, n8048, n8064, n8080, n8096, n8112, n8128, n8144, n8160, n8176, n8192, n8208, n8224, n8240, n8256, n8272, n8288, n8304, n8320, n8336, n8352, n8368, n8384, n8400, n8416, n8432, n8448, n8464, n8480, n8496, n8512, n8528, n8544, n8560, n8576, n8592, n8608, n8624, n8640, n8656, n8672, n8688, n8704, n8720, n8736, n8752, n8768, n8784, n8800, n8816, n8832, n8848, n8864, n8880, n8896, n8912, n8928, n8944, n8960, n8976, n8992, n9008, n9024, n9040, n9056, n9072, n9088, n9104, n9120, n9136, n9152, n9168, n9184, n9200, n9216, n9232, n9248, n9264, n9280, n9296, n9312, n9328, n9344, n9360, n9376, n9392, n9408, n9424, n9440, n9456, n9472, n9488, n9504, n9520, n9536, n9552, n9568, n9584, n9600, n9616, n9632, n9648, n9664, n9680, n9696, n9712, n9728, n9744, n9760, n9776, n9792, n9808, n9824, n9840, n9856, n9872, n9888, n9904, n9920, n9936, n9952, n9968, n9984, n10000, n10016, n10032, n10048, n10064, n10080, n10096, n10112, n10128, n10144, n10160, n10176, n10192, n10208, n10224, n10240, n10256, n10272, n10288, n10304, n10320, n10336, n10352, n10368, n10384, n10400, n10416, n10432, n10448, n10464, n10480, n10496, n10512, n10528, n10544, n10560, n10576, n10592, n10608, n10624, n10640, n10656, n10672, n10688, n10704, n10720, n10736, n10752, n10768, n10784, n10800, n10816, n10832, n10848, n10864, n10880, n10896, n10912, n10928, n10944, n10960, n10976, n10992, n11008, n11024, n11040, n11056, n11072, n11088, n11104, n11120, n11136, n11152, n11168, n11184, n11200, n11216, n11232, n11248, n11264, n11280, n11296, n11312, n11328, n11344, n11360, n11376, n11392, n11408, n11424, n11440, n11456, n11472, n11488, n11504, n11520, n11536, n11552, n11568, n11584, n11600, n11616, n11632, n11648, n11664, n11680, n11696, n11712, n11728, n11744, n11760, n11776, n11792, n11808, n11824, n11840, n11856, n11872, n11888, n11904, n11920, n11936, n11952, n11968, n11984, n12000, n12016, n12032, n12048, n12064, n12080, n12096, n12112, n12128, n12144, n12160, n12176, n12192, n12208, n12224, n12240, n12256, n12272, n12288, n12304, n12320, n12336, n12352, n12368, n12384, n12400, n12416, n12432, n12448, n12464, n12480, n12496, n12512, n12528, n12544, n12560, n12576, n12592, n12608, n12624, n12640, n12656, n12672, n12688, n12704, n12720, n12736, n12752, n12768, n12784, n12800, n12816, n12832, n12848, n12864, n12880, n12896, n12912, n12928, n12944, n12960, n12976, n12992, n13008, n13024, n13040, n13056, n13072, n13088, n13104, n13120, n13136, n13152, n13168, n13184, n13200, n13216, n13232, n13248, n13264, n13280, n13296, n13312, n13328, n13344, n13360, n13376, n13392, n13408, n13424, n13440, n13456, n13472, n13488, n13504, n13520, n13536, n13552, n13568, n13584, n13600, n13616, n13632, n13648, n13664, n13680, n13696, n13712, n13728, n13744, n13760, n13776, n13792, n13808, n13824, n13840, n13856, n13872, n13888, n13904, n13920, n13936, n13952, n13968, n13984, n14000, n14016, n14032, n14048, n14064, n14080, n14096, n14112, n14128, n14144, n14160, n14176, n14192, n14208, n14224, n14240, n14256, n14272, n14288, n14304, n14320, n14336, n14352, n14368, n14384, n14400, n14416, n14432, n14448, n14464, n14480, n14496, n14512, n14528, n14544, n14560, n14576, n14592, n14608, n14624, n14640, n14656, n14672, n14688, n14704, n14720, n14736, n14752, n14768, n14784, n14800, n14816, n14832, n14848, n14864, n14880, n14896, n14912, n14928, n14944, n14960, n14976, n14992, n15008, n15024, n15040, n15056, n15072, n15088, n15104, n15120, n15136, n15152, n15168, n15184, n15200, n15216, n15232, n15248, n15264, n15280, n15296, n15312, n15328, n15344, n15360, n15376, n15392, n15408, n15424, n15440, n15456, n15472, n15488, n15504, n15520, n15536, n15552, n15568, n15584, n15600, n15616, n15632, n15648, n15664, n15680, n15696, n15712, n15728, n15744, n15760, n15776, n15792, n15808, n15824, n15840, n15856, n15872, n15888, n15904, n15920, n15936, n15952, n15968, n15984, n16000, n16016, n16032, n16048, n16064, n16080, n16096, n16112, n16128, n16144, n16160, n16176, n16192, n16208, n16224, n16240, n16256, n16272, n16288, n16304, n16320, n16336, n16352, n16368, n16384, n16400, n16416, n16432, n16448, n16464, n16480, n16496, n16512, n16528, n16544, n16560, n16576, n16592, n16608, n16624, n16640, n16656, n16672, n16688, n16704, n16720, n16736, n16752, n16768, n16784, n16800, n16816, n16832, n16848, n16864, n16880, n16896, n16912, n16928, n16944, n16960, n16976, n16992, n17008, n17024, n17040, n17056, n17072, n17088, n17104, n17120, n17136, n17152, n17168, n17184, n17200, n17216, n17232, n17248, n17264, n17280, n17296, n17312, n17328, n17344, n17360, n17376, n17392, n17408, n17424, n17440, n17456, n17472, n17488, n17504, n17520, n17536, n17552, n17568, n17584, n17600, n17616, n17632, n17648, n17664, n17680, n17696, n17712, n17728, n17744, n17760, n17776, n17792, n17808, n17824, n17840, n17856, n17872, n17888, n17904, n17920, n17936, n17952, n17968, n17984, n18000, n18016, n18032, n18048, n18064, n18080, n18096, n18112, n18128, n18144, n18160, n18176, n18192, n18208, n18224, n18240, n18256, n18272, n18288, n18304, n18320, n18336, n18352, n18368, n18384, n18400, n18416, n18432, n18448, n18464, n18480, n18496, n18512, n18528, n18544, n18560, n18576, n18592, n18608, n18624, n18640, n18656, n18672, n18688, n18704, n18720, n18736, n18752, n18768, n18784, n18800, n18816, n18832, n18848, n18864, n18880, n18896, n18912, n18928, n18944, n18960, n18976, n18992, n19008, n19024, n19040, n19056, n19072, n19088, n19104, n19120, n19136, n19152, n19168, n19184, n19200, n19216, n19232, n19248, n19264, n19280, n19296, n19312, n19328, n19344, n19360, n19376, n19392, n19408, n19424, n19440, n19456, n19472, n19488, n19504, n19520, n19536, n19552, n19568, n19584, n19600, n19616, n19632, n19648, n19664, n19680, n19696, n19712, n19728, n19744, n19760, n19776, n19792, n19808, n19824, n19840, n19856, n19872, n19888, n19904, n19920, n19936, n19952, n19968, n19984, n20000, n20016, n20032, n20048, n20064, n20080, n20096, n20112, n20128, n20144, n20160, n20176, n20192, n20208, n20224, n20240, n20256, n20272, n20288, n20304, n20320, n20336, n20352, n20368, n20384, n20400, n20416, n20432, n20448, n20464, n20480, n20496, n20512, n20528, n20544, n20560, n20576, n20592, n20608, n20624, n20640, n20656, n20672, n20688, n20704, n20720, n20736, n20752, n20768, n20784, n20800, n20816, n20832, n20848, n20864, n20880, n20896, n20912, n20928, n20944, n20960, n20976, n20992, n21008, n21024, n21040, n21056, n21072, n21088, n21104, n21120, n21136, n21152, n21168, n21184, n21200, n21216, n21232, n21248, n21264, n21280, n21296, n21312, n21328, n21344, n21360, n21376, n21392, n21408, n21424, n21440, n21456, n21472, n21488, n21504, n21520, n21536, n21552, n21568, n21584, n21600, n21616, n21632, n21648, n21664, n21680, n21696, n21712, n21728, n21744, n21760, n21776, n21792, n21808, n21824, n21840, n21856, n21872, n21888, n21904, n21920, n21936, n21952, n21968, n21984, n22000, n22016, n22032, n22048, n22064, n22080, n22096, n22112, n22128, n22144, n22160, n22176, n22192, n22208, n22224, n22240, n22256, n22272, n22288, n22304, n22320, n22336, n22352, n22368, n22384, n22400, n22416, n22432, n22448, n22464, n22480, n22496, n22512, n22528, n22544, n22560, n22576, n22592, n22608, n22624, n22640, n22656, n22672, n22688, n22704, n22720, n22736, n22752, n22768, n22784, n22800, n22816, n22832, n22848, n22864, n22880, n22896, n22912, n22928, n22944, n22960, n22976, n22992, n23008, n23024, n23040, n23056, n23072, n23088, n23104, n23120, n23136, n23152, n23168, n23184, n23200, n23216, n23232, n23248, n23264, n23280, n23296, n23312, n23328, n23344, n23360, n23376, n23392, n23408, n23424, n23440, n23456, n23472, n23488, n23504, n23520, n23536, n23552, n23568, n23584, n23600, n23616, n23632, n23648, n23664, n23680, n23696, n23712, n23728, n23744, n23760, n23776, n23792, n23808, n23824, n23840, n23856, n23872, n23888, n23904, n23920, n23936, n23952, n23968, n23984, n24000, n24016, n24032, n24048, n24064, n24080, n24096, n24112, n24128, n24144, n24160, n24176, n24192, n24208, n24224, n24240, n24256, n24272, n24288, n24304, n24320, n24336, n24352, n24368, n24384, n24400, n24416, n24432, n24448, n24464, n24480, n24496, n24512, n24528, n24544, n24560, n24576, n24592, n24608, n24624, n24640, n24656, n24672, n24688, n24704, n24720, n24736, n24752, n24768, n24784, n24800, n24816, n24832, n24848, n24864, n24880, n24896, n24912, n24928, n24944, n24960, n24976, n24992, n25008, n25024, n25040, n25056, n25072, n25088, n25104, n25120, n25136, n25152, n25168, n25184, n25200, n25216, n25232, n25248, n25264, n25280, n25296, n25312, n25328, n25344, n25360, n25376, n25392, n25408, n25424, n25440, n25456, n25472, n25488, n25504, n25520, n25536, n25552, n2556 +``` + +``` + + n48, n64} OPTIONAL, +scs30-r16 ENUMERATED {n1, n2, n4, n8, n16, n24, n32, + n48, n64} OPTIONAL, +scs60-r16 ENUMERATED {n1, n2, n4, n8, n16, n24, n32, + n48, n64} OPTIONAL, +scs120-r16 ENUMERATED {n1, n2, n4, n8, n16, n24, n32, + n48, n64} OPTIONAL, + ..., + [[ +scs15-v1690 ENUMERATED {n6, n12} OPTIONAL, +scs30-v1690 ENUMERATED {n6, n12} OPTIONAL, +scs60-v1690 ENUMERATED {n6, n12} OPTIONAL, +scs120-v1690 ENUMERATED {n6, n12} OPTIONAL + ]] +}, +..., +[[ +supportedDL-PRS-ProcessingSamples-RRC-CONNECTED-r17 ENUMERATED { supported } OPTIONAL, +prs-ProcessingWindowType1A-r17 ENUMERATED { option1, option2, option3} OPTIONAL, +prs-ProcessingWindowType1B-r17 ENUMERATED { option1, option2, option3} OPTIONAL, +prs-ProcessingWindowType2-r17 ENUMERATED { option1, option2, option3} OPTIONAL, +prs-ProcessingCapabilityOutsideMGinPPW-r17 + SEQUENCE (SIZE(1..3)) OF + PRS-ProcessingCapabilityOutsideMGinPPWperType-r17 + OPTIONAL, +dl-PRS-BufferType-RRC-Inactive-r17 ENUMERATED { type1, type2, ... } OPTIONAL, +durationOfPRS-Processing-RRC-Inactive-r17 SEQUENCE { + durationOfPRS-ProcessingSymbols-r17 ENUMERATED {nDot125, nDot25, nDot5, n1, + n2, n4, n6, n8, n12, n16, n20, n25, + n30, n32, n35, n40, n45, n50}, + durationOfPRS-ProcessingSymbolsInEveryTms-r17 + ENUMERATED {n8, n16, n20, n30, n40, n80, + n160, n320, n640, n1280}, + ... +} OPTIONAL, +maxNumOfDL-PRS-ResProcessedPerSlot-RRC-Inactive-r17 SEQUENCE { + scs15-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs30-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs60-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs120-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + ... +} OPTIONAL, +supportedLowerRxBeamSweepingFactor-FR2-r17 ENUMERATED { n1, n2, n4, n6 } OPTIONAL +]], +[[ +supportedDL-PRS-ProcessingSamples-RRC-Inactive-r17 ENUMERATED { supported } OPTIONAL +]], +[[ +prs-MeasurementWithoutMG-r17 ENUMERATED {cp, symbolDot25, symbolDot5, + slotDot5} OPTIONAL +]], +[[ +maxNumOfOneSymbolPRS-ResProcessedPerSlot-RRC-Inactive-r18 SEQUENCE { + scs15-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs30-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs60-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs120-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + ... +} OPTIONAL, +maxNumOfOneSymbolPRS-ResProcessedPerSlot-RRC-Connected-r18 SEQUENCE { + scs15-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs30-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs60-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs120-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + ... +} OPTIONAL, +} OPTIONAL, + +``` + +``` + +ppw-maxNumOfOneSymbolPRS-ResProcessedPerSlot-r18 SEQUENCE { + scs15-r18 ENUMERATED { n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs30-r18 ENUMERATED { n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs60-r18 ENUMERATED { n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + scs120-r18 ENUMERATED { n1, n2, n4, n6, n8, n12, n16, n24, + n32, n48, n64} OPTIONAL, + ... +} +prs-BWA-TwoContiguousIntrabandInMG-RRC-Connected-r18 + PRS-BWA-TwoContiguousIntrabandInMG-r18 OPTIONAL, +prs-BWA-ThreeContiguousIntrabandInMG-RRC-Connected-r18 + PRS-BWA-ThreeContiguousIntrabandInMG-r18 OPTIONAL, +prs-BWA-TwoContiguousIntrabandInMG-RRC-IdleAndInactive-r18 + PRS-BWA-TwoContiguousIntrabandInMG-r18 OPTIONAL, +prs-BWA-ThreeContiguousIntrabandInMG-RRC-IdleAndInactive-r18 + PRS-BWA-ThreeContiguousIntrabandInMG-r18 OPTIONAL, +reducedNumOfSampleInMeasurementWithPRS-BWA-RRC-Connected-r18 BOOLEAN OPTIONAL, +reducedNumOfSampleInMeasurementWithPRS-BWA-RRC-IdleAndInactive-r18 BOOLEAN OPTIONAL, +dL-PRS-MeasurementWithRxFH-RRC-Inactive-r18 ENUMERATED { supported } OPTIONAL, +dL-PRS-MeasurementWithRxFH-RRC-Idle-r18 ENUMERATED { supported } OPTIONAL, +reducedNumOfSampleForMeasurementWithFH-RRC-Connected-r18 BOOLEAN OPTIONAL, +reducedNumOfSampleForMeasurementWithFH-RRC-IdleAndInactive-r18 BOOLEAN OPTIONAL, +] ] +} + +PRS-ProcessingCapabilityOutsideMGinPPWperType-r17 ::= SEQUENCE { + prsProcessingType-r17 ENUMERATED { type1A, type1B, type2 }, + ppw-dl-PRS-BufferType-r17 ENUMERATED { type1, type2, ... }, + ppw-durationOfPRS-Processing1-r17 SEQUENCE { + ppw-durationOfPRS-ProcessingSymbolsN-r17 + ENUMERATED { msDot125, msDot25, msDot5, ms1, ms2, ms4, + ms6, ms8, ms12, ms16, ms20, ms25, ms30, ms32, ms35, + ms40, ms45, ms50 }, + ppw-durationOfPRS-ProcessingSymbolsT-r17 + ENUMERATED { ms1, ms2, ms4, ms8, ms16, ms20, ms30, ms40, ms80, + ms160, ms320, ms640, ms1280 } + } + ppw-durationOfPRS-Processing2-r17 SEQUENCE { + ppw-durationOfPRS-ProcessingSymbolsN2-r17 + ENUMERATED { msDot125, msDot25, msDot5, ms1, ms2, ms3, ms4, ms5, + ms6, ms8, ms12 }, + ppw-durationOfPRS-ProcessingSymbolsT2-r17 + ENUMERATED { ms4, ms5, ms6, ms8 } + } + ppw-maxNumOfDL-PRS-ResProcessedPerSlot-r17 SEQUENCE { + scs15-r17 ENUMERATED { n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + scs30-r17 ENUMERATED { n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + scs60-r17 ENUMERATED { n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + scs120-r17 ENUMERATED { n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + ... + }, + ..., + [[ + ppw-maxNumOfDL-Bandwidth-r17 CHOICE { + fr1 ENUMERATED { mhz5, mhz10, mhz20, mhz40, + mhz50, mhz80, mhz100}, + fr2 ENUMERATED { mhz50, mhz100, mhz200, mhz400} + } + ] ] +} + +PRS-BWA-TwoContiguousIntrabandInMG-r18 ::= SEQUENCE { + maximumOfTwoAggregatedDL-PRS-Bandwidth-FR1-r18 ENUMERATED { mhz10, mhz20, mhz40, mhz50, + mhz80, mhz100, mhz160, mhz200} OPTIONAL, + maximumOfTwoAggregatedDL-PRS-Bandwidth-FR2-r18 ENUMERATED { mhz100, mhz200, mhz400, mhz800} OPTIONAL, +} + +``` + +``` + +maximumOfDL-PRS-BandwidthPerPFL-FR1-r18 ENUMERATED {mhz5, mhz10, mhz20, mhz40, + mhz50, mhz80, mhz100} OPTIONAL, +maximumOfDL-PRS-BandwidthPerPFL-FR2-r18 ENUMERATED {mhz50, mhz100, mhz200, mhz400} + OPTIONAL, +dl-PRS-BufferTypeOfBWA-r18 ENUMERATED {type1, type2}, +prs-durationOfTwoPRS-BWA-Processing-r18 SEQUENCE { + prs-durationOfTwoPRS-BWA-ProcessingSymbolsN-r18 + ENUMERATED {msDot125, msDot25, msDot5, ms1, ms2, ms4, ms6, ms8, ms12, + ms16, ms20, ms25, ms30, ms32, ms35, ms40, ms45, ms50}, + prs-durationOfTwoPRS-BWA-ProcessingSymbolsT-r18 + ENUMERATED {ms8, ms16, ms20, ms30, ms40, ms80, ms160, ms320, ms640, ms1280} +} + OPTIONAL, +maxNumOfAggregatedDL-PRS-ResourcePerSlot-FR1-r18 SEQUENCE { + scs15-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + scs30-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + scs60-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL +}, +maxNumOfAggregatedDL-PRS-ResourcePerSlot-FR2-r18 SEQUENCE { + scs60-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + scs120-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL +} +} + +PRS-BWA-ThreeContiguousIntrabandInMG-r18 ::= SEQUENCE { + maximumOfThreeAggregatedDL-PRS-Bandwidth-FR1-r18 + ENUMERATED {mhz15, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100, mhz120, + mhz140, mhz150, mhz180, mhz200, mhz240, mhz300} OPTIONAL, + maximumOfThreeAggregatedDL-PRS-Bandwidth-FR2-r18 + ENUMERATED {mhz150, mhz200, mhz300, mhz400, mhz600, mhz800, mhz1000, + mhz1200} OPTIONAL, + maximumOfDL-PRS-BandwidthPerPFL-FR1-r18 + ENUMERATED {mhz5, mhz10, mhz20, mhz40, mhz50, mhz80, mhz100} OPTIONAL, + maximumOfDL-PRS-BandwidthPerPFL-FR2-r18 + ENUMERATED {mhz50, mhz100, mhz200, mhz400} OPTIONAL, + dl-PRS-BufferTypeOfBWA-r18 ENUMERATED {type1, type2}, + prs-durationOfThreePRS-BWA-Processing-r18 SEQUENCE { + prs-durationOfThreePRS-BWA-ProcessingSymbolsN-r18 + ENUMERATED {msDot125, msDot25, msDot5, ms1, ms2, ms4, ms6, ms8, ms12, + ms16, ms20, ms25, ms30, ms32, ms35, ms40, ms45, ms50}, + prs-durationOfThreePRS-BWA-ProcessingSymbolsT-r18 + ENUMERATED {ms8, ms16, ms20, ms30, ms40, ms80, ms160, + ms320, ms640, ms1280} + } + OPTIONAL, + maxNumOfAggregatedDL-PRS-ResourcePerSlot-FR1-r18 SEQUENCE { + scs15-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + scs30-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + scs60-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL + }, + maxNumOfAggregatedDL-PRS-ResourcePerSlot-FR2-r18 SEQUENCE { + scs60-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL, + scs120-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, + n16, n24, n32, n48, n64 } OPTIONAL + } +} + +-- ASN1STOP + +``` + +#### NR-DL-PRS-ProcessingCapability field descriptions + +| | | +|-------------------------------|-------------------------------------------------------------------------------------------------| +| maxSupportedFreqLayers | Indicates the maximum number of positioning frequency layers supported by UE. | +| simultLTE-NR-PRS | Indicates whether the UE supports parallel processing of LTE PRS and NR PRS. | +| dummy | This field is not used in the specification. If received it shall be ignored by the receiver. | +| supportedBandwidthPRS | Indicates the maximum number of DL-PRS bandwidth in MHz, which is supported and reported by UE. | + +| NR-DL-PRS-ProcessingCapability field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

dl-PRS-BufferType
Indicates DL-PRS buffering capability. Value type1 indicates sub-slot/symbol level buffering and value type2 indicates slot level buffering.

| +|

durationOfPRS-Processing
Indicates the duration N of DL-PRS symbols in units of ms a UE can process every T ms assuming maximum DL-PRS bandwidth provided in supportedBandwidthPRS and comprises the following subfields:

  • - durationOfPRS-ProcessingSymbols: This field specifies the values for N. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50 ms.
  • - durationOfPRS-ProcessingSymbolsInEveryTms: This field specifies the values for T. Enumerated values indicate 8, 16, 20, 30, 40, 80, 160, 320, 640, 1280 ms.

See NOTE 9.

| +|

maxNumOfDL-PRS-ResProcessedPerSlot
Indicates the maximum number of DL-PRS resources that UE can process in a slot. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands.

| +|

supportedDL-PRS-ProcessingSamples-RRc-CONNECTED
Indicates the UE capability for support of measurements based on measuring M=1 or M=2 (instances) of a DL-PRS Resource Set. The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList. Otherwise, the UE does not include this field.

NOTE 1: This feature is supported for both UE-assisted and UE based positioning.

| +|

prs-ProcessingWindowType1A
Indicates the supported DL-PRS processing types subject to the UE determining that DL-PRS to be higher priority for DL-PRS measurement outside MG and in a DL-PRS Processing Window.

Type 1A refers to the determination of prioritization between DL-PRS and other DL signals/channels in all OFDM symbols within the PRS Processing Window. The DL signals/channels from all DL CCs (per UE) are affected across LTE and NR. Enumerated value indicates supported priority handing options of DL-PRS:

  • - option1: Support of "st1" and "st3" defined in clause 5.1.6.5 of TS 38.214 [45].
  • - option2: Support of "st1", "st2", and "st3" defined in clause 5.1.6.5 of TS 38.214 [45].
  • - option3: Support of "st1" only defined in clause 5.1.6.5 of TS 38.214 [45].

The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList. Otherwise, the UE does not include this field.

NOTE 2: Within a PRS processing window, UE measurement is inside the active DL BWP with PRS having the same numerology as the active DL BWP.

NOTE 2a: When the UE determines higher priority for other DL signals/channels over the DL-PRS measurement/processing, the UE is not expected to measure/process DL-PRS.

| +|

prs-ProcessingWindowType1B
Indicates the supported DL-PRS processing types subject to the UE determining that DL-PRS to be higher priority for DL-PRS measurement outside MG and in a DL-PRS Processing Window.

Type 1B refers to the determination of prioritization between DL-PRS and other DL signals/channels in all OFDM symbols within the PRS processing window. The DL signals/channels from a certain band are affected. Enumerated value indicates supported priority handing options of DL-PRS (see prs-ProcessingWindowType1A).

The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList. Otherwise, the UE does not include this field.

NOTE 3: Within a PRS processing window, UE measurement is inside the active DL BWP with PRS having the same numerology as the active DL BWP.

NOTE 3a: When the UE determines higher priority for other DL signals/channels over the DL-PRS measurement/processing, the UE is not expected to measure/process DL-PRS.

| +|

prs-ProcessingWindowType2
Indicates the supported DL-PRS processing types subject to the UE determining that DL-PRS to be higher priority for DL-PRS measurement outside MG and in a DL-PRS Processing Window.

Type 2 refers to the determination of prioritization between DL-PRS and other DL signals/channels only in DL-PRS symbols within the PRS processing window. Enumerated value indicates supported priority handing options of DL-PRS (see prs-ProcessingWindowType1A).

The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList. Otherwise, the UE does not include this field.

NOTE 4: Within a PRS processing window, UE measurement is inside the active DL BWP with PRS having the same numerology as the active DL BWP.

NOTE 4a: When the UE determines higher priority for other DL signals/channels over the DL-PRS measurement/processing, the UE is not expected to measure/process DL-PRS.

| + +| NR-DL-PRS-ProcessingCapability field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

prs-ProcessingCapabilityOutsideMGinPPW
Indicates the DL-PRS Processing Capability outside MG of each of the supported PPW Type in the case the UE supports multiple PPW Types in a band and comprises the following subfields:

  • - prsProcessingType: Indicates the DL-PRS Processing Window Type for which the prs-ProcessingCapabilityOutsideMGinPPW are provided.
  • - ppw-dl-PRS-BufferType: Indicates DL-PRS buffering capability. Value 'type1' indicates sub-slot/symbol level buffering and value 'type2' indicates slot level buffering.
  • - ppw-durationOfPRS-Processing1: Indicates the duration of DL-PRS symbols N in units of ms a UE can process every T ms assuming maximum DL-PRS bandwidth provided in ppw-maxNumOfDL-Bandwidth and comprises the following subfields:
    • - ppw-durationOfPRS-ProcessingSymbolsN: This field specifies the values for N. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50 ms.
    • - ppw-durationOfPRS-ProcessingSymbolsT: This field specifies the values for T. Enumerated values indicate 1, 2, 4, 8, 16, 20, 30, 40, 80, 160, 320, 640, 1280 ms.
  • - ppw-durationOfPRS-Processing2: Indicates the duration of DL-PRS symbols N2 in units of ms a UE can process in T2 ms assuming maximum DL-PRS bandwidth provided in ppw-maxNumOfDL-Bandwidth and comprises the following subfields:
    • - ppw-durationOfPRS-ProcessingSymbolsN2: This field specifies the values for N2. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 3, 4, 5, 6, 8, 12 ms.
    • - ppw-durationOfPRS-ProcessingSymbolsT2: This field specifies the values for T2. Enumerated values indicate 4, 5, 6, 8 ms.
  • - ppw-maxNumOfDL-PRS-ResProcessedPerSlot: Indicates the maximum number of DL-PRS resources that UE can process in a slot. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands.
  • - ppw-maxNumOfDL-Bandwidth: Indicates the maximum number of DL PRS bandwidth in MHz, which is supported and reported by UE for PRS measurement outside MG within the PPW.

The UE can include this field only if the UE supports one of prs-ProcessingWindowType1A, prs-ProcessingWindowType1B and prs-ProcessingWindowType2. Otherwise, the UE does not include this field.

NOTE 5: A UE that supports one of prs-ProcessingWindowType1A, prs-ProcessingWindowType1B or prs-ProcessingWindowType2 shall always include the prs-ProcessingCapabilityOutsideMGinPPW.

NOTE 6: The (N, T) UE capability in ppw-durationOfPRS-Processing1 is interpreted as in NOTE 9, and the UE is expected to receive the DL-PRS within the PRS processing window but the processing of the received DL-PRS may be outside a DL-PRS processing window.

NOTE 7: The (N2, T2) UE capability in ppw-durationOfPRS-Processing2 is interpreted such that the UE is capable of measuring up to N2 ms DL-PRS within a PPW and is capable of completing the DL-PRS processing within the PPW, e.g., if the time duration from the last symbol of the measured DL-PRS resource(s) inside the PPW to the end of PPW is not smaller than T2 ms.

NOTE 8: A UE which supports prs-ProcessingCapabilityOutsideMGinPPW shall support either ppw-durationOfPRS-Processing1 or ppw-durationOfPRS-Processing2, but not both for each supported type in a band.

| +|

dl-PRS-BufferType-RRC-Inactive
Indicates DL-PRS buffering capability in RRC_INACTIVE state. Value 'type1' indicates sub-slot/symbol level buffering and value 'type2' indicates slot level buffering.

| +|

durationOfPRS-Processing-RRC-Inactive
Indicates the duration N of DL-PRS symbols in units of ms a UE can process every T ms in RRC_INACTIVE state assuming maximum DL-PRS bandwidth provided in supportedBandwidthPRS and comprises the following subfields:

  • - durationOfPRS-ProcessingSymbols: This field specifies the values for N. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50 ms.
  • - durationOfPRS-ProcessingSymbolsInEveryTms: This field specifies the values for T. Enumerated values indicate 8, 16, 20, 30, 40, 80, 160, 320, 640, 1280 ms.

See NOTE 9.

| +|

maxNumOfDL-PRS-ResProcessedPerSlot-RRC-Inactive
Indicates the maximum number of DL-PRS resources a UE can process in a slot in RRC_INACTIVE state. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands.

| +|

supportedLowerRxBeamSweepingFactor-FR2
Indicates support of the lower Rx beam sweeping factor than 8 for FR2. Enumerated value indicates the number of Rx beam sweeping factors supported.

| +|

supportedDL-PRS-ProcessingSamples-RRC-Inactive
Indicates the UE capability for support of reduced number of samples for PRS measurement in RRC_INACTIVE state. The UE can include this field only if the UE supports prs-ProcessingRRC-Inactive defined in TS 38.331 [35]. Otherwise, the UE does not include this field.

| + +| NR-DL-PRS-ProcessingCapability field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxNumOfOneSymbolPRS-ResProcessedPerSlot-RRC-Inactive
Indicates the maximum number of single-symbol DL-PRS resources that UE can process in a slot in RRC_INACTIVE. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands. A UE which supports maxNumOfOneSymbolPRS-ResProcessedPerSlot-RRC-Inactive-r18 shall support single-symbol DL-PRS with the comb sizes from {2,4,6,12}.
The UE can include this field only if the UE supports one of dl-PRS-BufferType-RRC-Inactive , durationOfPRS-Processing-RRC-Inactive , and maxNumOfDL-PRS-ResProcessedPerSlot-RRC-Inactive . Otherwise, the UE does not include this field. | +| maxNumOfOneSymbolPRS-ResProcessedPerSlot-RRC-Connected
Indicates the maximum number of single-symbol DL-PRS resources that UE can process in a slot inside a measurement gap in RRC_CONNECTED. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands. A UE which supports maxNumOfOneSymbolPRS-ResProcessedPerSlot-RRC-Connected-r18 shall support single-symbol DL-PRS with the comb sizes from {2,4,6,12}.
The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList . Otherwise, the UE does not include this field. | + +| NR-DL-PRS-ProcessingCapability field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

ppw-maxNumOfOneSymbolPRS-ResProcessedPerSlot
Indicates the maximum number of single-symbol DL-PRS resources that UE can process in a slot outside a measurement gap in RRC_CONNECTED. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands. A UE which supports ppw-maxNumOfOneSymbolPRS-ResProcessedPerSlot-r18 shall support single-symbol DL-PRS with the comb sizes from {2,4,6,12}.
The UE can include this field only if the UE supports prs-ProcessingCapabilityOutsideMGinPPW. Otherwise, the UE does not include this field.

| +|

prs-MeasurementWithoutMG
Indicates the UE capability for support of Rx timing difference between the serving cell and non-serving cell for PRS measurement within a PPW. Value 'cp' indicates one CP length, value 'symbolDot25' indicates 0.25 symbol length, value 'symbolDot5' indicates 0.5 symbol length and value 'slotDot5' indicates 0.5 slot length. The UE can include this field only if the UE supports one of prs-ProcessingWindowType1A, prs-ProcessingWindowType1B and prs-ProcessingWindowType2. Otherwise, the UE does not include this field.

| +|

prs-BWA-TwoContiguousIntrabandInMG-RRC-Connected
Indicates the UE capability for support of DL PRS processing capabilities for aggregated PRS processing of 2 PFLs in intra-band contiguous within a MG for RRC_CONNECTED state and comprises the following subfields:

  • - maximumOfTwoAggregatedDL-PRS-Bandwidth-FR1: Indicates the maximum aggregated DL PRS bandwidth in MHz for FR1, which is supported and reported by UE.
  • - maximumOfTwoAggregatedDL-PRS-Bandwidth-FR2: Indicates the maximum aggregated DL PRS bandwidth in MHz for FR2, which is supported and reported by UE.
  • - maximumOfDL-PRS-BandwidthPerPFL-FR1: Indicates the maximum DL PRS bandwidth in MHz for FR1, per PFL.
  • - maximumOfDL-PRS-BandwidthPerPFL-FR2: Indicates the maximum DL PRS bandwidth in MHz for FR2, per PFL.
  • - dl-PRS-BufferTypeOfBWA: Indicates the DL PRS buffering capability.
  • - prs-durationOfTwoPRS-BWA-Processing: Indicates the duration of DL PRS symbols N in units of ms a UE can process every T ms assuming maximum aggregated DL PRS bandwidth in MHz, which is supported and reported by UE.
  • - prs-durationOfTwoPRS-BWA-ProcessingSymbolsN: This field specifies the values for N. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50 ms.
  • - prs-durationOfTwoPRS-BWA-ProcessingSymbolsT: This field specifies the values for T. Enumerated values indicate 8, 16, 20, 30, 40, 80, 160, 320, 640, 1280, 2560 ms.
  • - maxNumOfAggregatedDL-PRS-ResourcePerSlot-FR1: Indicates the Maximum number of aggregated DL PRS resources across aggregated PFLs that UE can process in a slot for FR1.
  • - maxNumOfAggregatedDL-PRS-ResourcePerSlot-FR2: Indicates the Maximum number of aggregated DL PRS resources across aggregated PFLs that UE can process in a slot for FR2.

The UE can include this field only if the UE supports ProcessingCapabilityPerBand. Otherwise, the UE does not include this field.

NOTE10: dl-PRS-BufferTypeOfBWA follows buffering capability type reported in ProcessingCapabilityPerBand.

NOTE11: The value N should be equal or smaller than the value N reported by ProcessingCapabilityPerBand, or this value T should be equal or larger than the value T reported by ProcessingCapabilityPerBand.

NOTE12: Each two linked PRS resources are counted as 1 resource

NOTE13: maxNumOfAggregatedDL-PRS-ResourcePerSlot should be equal or smaller than the value reported by ProcessingCapabilityPerBand.

NOTE14: The above parameters are reported assuming a configured measurement gap and a maximum ratio of measurement gap length (MGL)/measurement gap repetition period (MGRP) of no more than 30%.

| + +| NR-DL-PRS-ProcessingCapability field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

prs-BWA-ThreeContiguousIntrabandInMG-RRC-Connected

Indicates the UE capability for support of DL PRS processing capabilities for aggregated PRS processing of 3 PFLs in intra-band contiguous within a MG for RRC_CONNECTED state and and comprises the following subfields:

  • - maximumOfThreeAggregatedDL-PRS-Bandwidth-FR1: Indicates the maximum aggregated DL PRS bandwidth in MHz for FR1, which is supported and reported by UE.
  • - maximumOfThreeAggregatedDL-PRS-Bandwidth-FR2: Indicates the maximum aggregated DL PRS bandwidth in MHz for FR2, which is supported and reported by UE.
  • - maximumOfDL-PRS-BandwidthPerPFL-FR1: Indicates the maximum DL PRS bandwidth in MHz for FR1, per PFL
  • - maximumOfDL-PRS-BandwidthPerPFL-FR2: Indicates the maximum DL PRS bandwidth in MHz for FR2, per PFL
  • - dl-PRS-BufferTypeOfBWA: Indicates the DL PRS buffering capability.
  • - prs-durationOfThreePRS-BWA-Processing: Indicates the duration of DL PRS symbols N in units of ms a UE can process every T ms assuming maximum aggregated DL PRS bandwidth in MHz, which is supported and reported by UE.
  • - prs-durationOfThreePRS-BWA-ProcessingSymbolsN: This field specifies the values for N. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50 ms.
  • - prs-durationOfThreePRS-BWA-ProcessingSymbolsT: This field specifies the values for T. Enumerated values indicate 8, 16, 20, 30, 40, 80, 160, 320, 640, 1280, 3840 ms.
  • - maxNumOfAggregatedDL-PRS-ResourcePerSlot-FR1: Indicates the Maximum number of aggregated DL PRS resources across aggregated PFLs that UE can process in a slot for FR1.
  • - maxNumOfAggregatedDL-PRS-ResourcePerSlot-FR2: Indicates the Maximum number of aggregated DL PRS resources across aggregated PFLs that UE can process in a slot for FR2.

The UE can include this field only if the UE supports prs-BWA-TwoContiguousIntrabandInMG-RRC-Connected. Otherwise, the UE does not include this field.

NOTE15: dl-PRS-BufferTypeOfBWA follows buffering capability type reported in ProcessingCapabilityPerBand.

NOTE16: The value N should be equal or smaller than the value N reported by ProcessingCapabilityPerBand, or this value T should be equal or larger than the value T reported by ProcessingCapabilityPerBand.

NOTE17: Each three linked PRS resources are counted as 1 resource

NOTE18: maxNumOfAggregatedDL-PRS-ResourcePerSlot should be equal or smaller than the value reported by ProcessingCapabilityPerBand.

NOTE19: The above parameters are reported assuming a configured measurement gap and a maximum ratio of measurement gap length (MGL)/measurement gap repetition period (MGRP) of no more than 30%.

| +|

prs-BWA-TwoContiguousIntrabandInMG-RRC-IdleAndInactive

Indicates the UE capability for support of DL PRS processing capabilities for aggregated PRS processing of 2 PFLs in intra-band contiguous within a MG for RRC_INACTIVE and RRC_IDLE state.

The UE can include this field only if the UE supports DL PRS processing capabilities in RRC inactive state. Otherwise, the UE does not include this field.

| +|

prs-BWA-ThreeContiguousIntrabandInMG-RRC-IdleAndInactive

Indicates the UE capability for support of DL PRS processing capabilities for aggregated PRS processing of 3 PFLs in intra-band contiguous within a MG for RRC_INACTIVE and RRC_IDLE state. The UE can include this field only if the UE supports prs-BWA-TwoContiguousIntrabandInMG-RRC-IdleAndInactive. Otherwise, the UE does not include this field.

| +|

reducedNumOfSampleInMeasurementWithPRS-BWA-RRC-Connected

Indicates whether UE supports reduced number of samples in positioning measurements with PRS bandwidth aggregation for RRC_CONNECTED. TRUE means supported and FALSE means not supported. The UE can indicate TRUE only if the UE supports prs-BWA-TwoContiguousIntrabandInMG-RRC-Connected. Otherwise, the UE indicates FALSE.

| +|

reducedNumOfSampleInMeasurementWithPRS-BWA-RRC-IdleAndInactive

Indicates whether UE supports reduced number of samples in positioning measurements with PRS bandwidth aggregation for RRC_IDLE and RRC_INACTIVE. TRUE means supported and FALSE means not supported. The UE can indicate TRUE only if the UE supports prs-BWA-TwoContiguousIntrabandInMG-RRC-Connected. Otherwise, the UE indicates FALSE.

| +|

dl-PRS-MeasurementWithRxFH-RRC-Inactive

Indicates the UE capability for support of PRS measurement with Rx frequency hopping in RRC_INACTIVE for RedCap UEs. The UE can include this field only if the UE supports PRS measurement with Rx frequency hopping within a MG and measurement reporting in RRC_CONNECTED for RedCap UEs and prs-ProcessingRRC-Inactive defined in TS 38.331 [35]. Otherwise, the UE does not include this field.

| +|

dl-PRS-MeasurementWithRxFH-RRC-Idle

Indicates the UE capability for support of PRS measurement with Rx frequency hopping in RRC_IDLE for RedCap UEs. The UE can include this field only if the UE supports PRS measurement with Rx frequency hopping within a MG and measurement reporting in RRC_CONNECTED for RedCap UEs. Otherwise, the UE does not include this field.

| +|

reducedNumOfSampleForMeasurementWithFH-RRC-Connected

Indicates whether UE supports reduced number of samples for PRS based positioning measurements frequency hopping for RRC_CONNECTED. TRUE means supported and FALSE means not supported. The UE can indicate TRUE only if the UE supports supportOfRedCap-r17 defined in TS 38.331 [35], and supportedDL-PRS-ProcessingSamples-RRC-CONNECTED-r17. Otherwise, the UE indicates FALSE.

| + +| NR-DL-PRS-ProcessingCapability field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

reducedNumOfSampleForMeasurementWithFH-RRC-IdleAndInactive
Indicates whether UE supports reduced number of samples for PRS based positioning measurements frequency hopping for RRC_IDLE and RRC_INACTIVE. TRUE means supported and FALSE means not supported. The UE can indicate TRUE only if the UE supports supportOfRedCap-r17 defined in TS 38.331 [35], and supportedDL-PRS-ProcessingSamples-RRC-CONNECTED-r17. Otherwise, the UE indicates FALSE.

NOTE 9: When the target device provides the durationOfPRS-Processing capability (N, T) for any time window defined in TS 38.214 [45] clause 5.1.6.5, the target device should be capable of processing all DL-PRS resources within , if

  • - where K is defined in the TS 38.214 [45] clause 5.1.6.5, and
  • - the number of DL-PRS Resources in each slot does not exceed the maxNumOfDL-PRS-ResProcessedPerSlot, and
  • - the configured measurement gap and a maximum ratio of measurement gap length (MGL) / measurement gap repetition period (MGRP) is as specified in TS 38.133 [46].
| + +## – NR-DL-PRS-QCL-ProcessingCapability + +The IE *NR-DL-PRS-QCL-ProcessingCapability* defines the common UE DL-PRS QCL Processing capability. The UE can include this IE only if the UE supports *NR-DL-PRS-ProcessingCapability*. Otherwise, the UE does not include this IE. + +In the case of capabilities for multiple NR positioning methods are provided, the IE *NR-DL-PRS-QCL-ProcessingCapability* applies across the NR positioning methods and the target device shall indicate the same values for the capabilities in IEs *NR-DL-TDOA-ProvideCapabilities*, *NR-DL-AoD-ProvideCapabilities*, and *NR-Multi-RTT-ProvideCapabilities*. + +``` +-- ASN1START + +NR-DL-PRS-QCL-ProcessingCapability-r16 ::= SEQUENCE { + dl-PRS-QCL-ProcessingCapabilityBandList-r16 SEQUENCE (SIZE (1..nrMaxBands-r16)) OF + DL-PRS-QCL-ProcessingCapabilityPerBand-r16, + ... +} + +DL-PRS-QCL-ProcessingCapabilityPerBand-r16 ::= SEQUENCE { + freqBandIndicatorNR-r16 FreqBandIndicatorNR-r16, + ssb-FromNeighCellAsQCL-r16 ENUMERATED { supported } OPTIONAL, + prs-FromServNeighCellAsQCL-r16 ENUMERATED { supported } OPTIONAL, + ... +} + +-- ASN1STOP +``` + +| NR-DL-PRS-QCL-ProcessingCapability field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

ssb-FromNeighCellAsQCL
Indicates the support of SSB from neighbour cell as QCL source of a DL-PRS. UE supporting this feature also support reusing SSB measurement from RRM for receiving PRS.
Note: It refers to Type-C for FR1 and Type-C & Type-D support for FR2.

| +|

prs-FromServNeighCellAsQCL
Indicates the support of DL-PRS from serving/neighbour cell as QCL source of a DL-PRS.
Note 1: It refers to Type-D support for FR2.
Note 2: A PRS from a PRS-only TP is treated as PRS from a non-serving cell.

| + +## – NR-DL-PRS-ResourceID + +The IE *NR-DL-PRS-ResourceID* defines the identity of a DL-PRS Resource of a DL-PRS Resource Set of a TRP. + +``` +-- ASN1START + +NR-DL-PRS-ResourceID-r16 ::= INTEGER (0..nrMaxNumDL-PRS-ResourcesPerSet-1-r16) + +-- ASN1STOP +``` + +## NR-DL-PRS-ResourcesCapability + +The IE *NR-DL-PRS-ResourcesCapability* defines the DL-PRS resources capability for each positioning method. The UE can include this IE only if the UE supports *NR-DL-PRS-ProcessingCapability*. Otherwise, the UE does not include this IE. + +``` +-- ASN1START + +NR-DL-PRS-ResourcesCapability-r16 ::= SEQUENCE { + maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer-r16 + INTEGER (1..2), + maxNrOfTRP-AcrossFreqs-r16 + ENUMERATED { n4, n6, n12, n16, n32, + n64, n128, n256, ..., n24-v1690}, + maxNrOfPosLayer-r16 + INTEGER (1..4), + dl-PRS-ResourcesCapabilityBandList-r16 + SEQUENCE (SIZE (1..nrMaxBands-r16)) OF + DL-PRS-ResourcesCapabilityPerBand-r16, + dl-PRS-ResourcesBandCombinationList-r16 + DL-PRS-ResourcesBandCombinationList-r16, + ... +} + +DL-PRS-ResourcesCapabilityPerBand-r16 ::= SEQUENCE { + freqBandIndicatorNR-r16 + FreqBandIndicatorNR-r16, + maxNrOfDL-PRS-ResourcesPerResourceSet-r16 + ENUMERATED { n1, n2, n4, n8, n16, n32, n64, ...}, + maxNrOfDL-PRS-ResourcesPerPositioningFrequencyLayer-r16 + ENUMERATED { n6, n24, n32, n64, n96, n128, + n256, n512, n1024, ...}, + ... +} + +DL-PRS-ResourcesBandCombinationList-r16 ::= SEQUENCE (SIZE (1..maxBandComb-r16)) OF + DL-PRS-ResourcesBandCombination-r16 + +DL-PRS-ResourcesBandCombination-r16 ::= SEQUENCE { + bandList-r16 + SEQUENCE (SIZE (1..maxSimultaneousBands-r16)) OF + FreqBandIndicatorNR-r16, + maxNrOfDL-PRS-ResourcesAcrossAllFL-TRP-ResourceSet-r16 + CHOICE { + fr1-Only-r16 + ENUMERATED {n6, n24, n64, n128, n192, + n256, n512, n1024, n2048}, + fr2-Only-r16 + ENUMERATED {n24, n64, n96, n128, n192, + n256, n512, n1024, n2048}, + fr1-FR2Mix-r16 + SEQUENCE { + fr1-r16 + ENUMERATED {n6, n24, n64, n96, n128, + n192, n256, n512, n1024, n2048}, + fr2-r16 + ENUMERATED {n24, n64, n96, n128, n192, + n256, n512, n1024, n2048}, + ... + }, + ... + }, + ... +} + +-- ASN1STOP +``` + +### NR-DL-PRS-ResourcesCapability field descriptions + +| | | +|------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer | Indicates the maximum number of DL-PRS Resource Sets per TRP per positioning frequency layer supported by UE. | +| maxNrOfTRP-AcrossFreqs | Indicates the maximum number of TRPs across all positioning frequency layers. | +| maxNrOfPosLayer | Indicates the maximum number of supported positioning frequency layers. | +| dl-PRS-ResourcesBandCombinationList | Provides the capabilities of DL-PRS Resources for the indicated band combination in bandList . This field is provided for all band combinations for which the target device supports DL-PRS. | +| maxNrOfDL-PRS-ResourcesPerResourceSet | Indicates the maximum number of DL-PRS Resources per DL-PRS Resource Set. Value 16, 32, 64 are only applicable to FR2 bands. Value 1 is not applicable for DL-AoD. | +| maxNrOfDL-PRS-ResourcesPerPositioningFrequencyLayer | Indicates the maximum number of DL-PRS resources per positioning frequency layer. Value 6 is only applicable to FR1 bands. | + +| NR-DL-PRS-ResourcesCapability field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer
Indicates the maximum number of DL-PRS Resource Sets per TRP per positioning frequency layer supported by UE. | +| maxNrOfTRP-AcrossFreqs
Indicates the maximum number of TRPs across all positioning frequency layers. | +| maxNrOfDL-PRS-ResourcesAcrossAllFL-TRP-ResourceSet
Indicates the maximum number of DL-PRS Resources supported by UE across all frequency layers, TRPs and DL-PRS Resource Sets.
fr1-Only: This is applicable for FR1 only band combinations;
fr2-Only: This is applicable for FR2 only band combinations;
fr1-FR2Mix: This is applicable for band combinations containing FR1 and FR2 bands. fr1 means for FR1 in FR1/FR2 mixed operation, and fr2 means for FR2 in FR1/FR2 mixed operation. | + +## – NR-DL-PRS-ResourceSetID + +The IE *NR-DL-PRS-ResourceSetID* defines the identity of a DL-PRS Resource Set of a TRP. + +``` +-- ASN1START +NR-DL-PRS-ResourceSetID-r16 ::= INTEGER (0..nrMaxNumDL-PRS-ResourceSetsPerTRP-1-r16) +-- ASN1STOP +``` + +## – NR-DL-PRS-TRP-TEG-Info + +The IE *NR-DL-PRS-TRP-TEG-Info* is used by the location server to provide the association information of DL-PRS Resources with TRP Tx TEGs. + +``` +-- ASN1START +NR-DL-PRS-TRP-TEG-Info-r17 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF + NR-DL-PRS-TRP-TEG-InfoPerFreqLayer-r17 +NR-DL-PRS-TRP-TEG-InfoPerFreqLayer-r17 ::= SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF + NR-DL-PRS-TRP-TEG-InfoPerTRP-r17 +NR-DL-PRS-TRP-TEG-InfoPerTRP-r17 ::= SEQUENCE { + dl-PRS-ID-r17 INTEGER (0..255), + nr-PhysCellID-r17 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r17 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r17 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + dl-PRS-TEG-InfoSet-r17 SEQUENCE (SIZE(1..nrMaxSetsPerTrpPerFreqLayer-r16)) OF + DL-PRS-TEG-InfoPerResourceSet-r17, + ... + [ + nr-TRP-TxTEG-TimingErrorMargin-r17 TEG-TimingErrorMargin-r17 OPTIONAL -- Need ON + ] +} +DL-PRS-TEG-InfoPerResourceSet-r17 ::= SEQUENCE (SIZE(1..nrMaxResourcesPerSet-r16)) OF + DL-PRS-TEG-InfoElement-r17 +DL-PRS-TEG-InfoElement-r17 ::= SEQUENCE { + dl-prs-trp-Tx-TEG-ID-r17 INTEGER (0..maxNumOfTRP-TxTEGs-1-r17), + ... +} +-- ASN1STOP +``` + +| NR-DL-PRS-TRP-TEG-Info field descriptions | +|--------------------------------------------------| +|--------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PRS-ID
This field specifies the DL-PRS ID of the TRP for which the TRP Tx TEG information is provided. | +| nr-PhysCellID
This field specifies the physical Cell-ID of the TRP for which the TRP Tx TEG information is provided, as defined in TS 38.331 [35]. | +| nr-CellGlobalID
This field specifies the NCGI, the globally unique identity of a cell in NR, of the TRP for which the TRP Tx TEG information is provided, as defined in TS 38.331 [35]. | +| nr-ARFCN
This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID . | +| dl-PRS-TEG-InfoSet
This field specifies the TRP Tx TEG ID associated with the transmissions of each DL-PRS Resource of the TRP. The dl-prs-trp-Tx-TEG-ID in dl-PRS-TEG-InfoSet is associated with the nr-DL-PRS-ResourceID of NR-DL-PRS-Info using the same structure and order. | +| nr-TRP-TxTEG-TimingErrorMargin
This field specifies the timing error margin value for all the TRP Tx TEGs contained within one NR-DL-PRS-TRP-TEG-InfoPerTRP . | + +## NR-IntegrityRiskParameters + +The IE *NR-IntegrityRiskParameters* is used by the location server to indicate the residual risks to UE. + +``` +-- ASN1START +NR-IntegrityRiskParameters-r18 ::= SEQUENCE { + nr-ProbOnsetTRP-Fault-r18 INTEGER (0..255), + nr-MeanTRP-FaultDuration-r18 INTEGER (1..3600), + ... +} +-- ASN1STOP +``` + +| NR-IntegrityRiskParameters field descriptions | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| nr-ProbOnsetTRP-Fault
This field specifies the Probability of Onset of TRP Fault per Time Unit which is the probability of occurrence of TRP error to exceed the error bound for more than the Time to Alert (TTA).
This field specifies the onset probability that the error exceeds a bound created using the minimum allowed inflation factor $K_{min}$ , and bounding parameters as $mean + K_{min} * stdDev$ where $K_{min} = normInv(irMaximum / 2)$ , with irMaximum as provided in IE nr-IntegrityServiceParameters .
The probability is calculated by $P=10^{-0.04n}$ [hour -1 ] where n is the value of nr-ProbOnsetTRP-Fault and the range is $10^{-10.2}$ to 1 per hour. | | +| nr-MeanTRP-FaultDuration
This field specifies the Mean TRP Fault Duration which is the mean duration between when a TRP fault occurs, and the user is alerted by IE NR-IntegrityServiceAlert (or the integrity violation is over).
Scale factor 1 s; range 1-3600 s. | | + +## NR-IntegrityServiceAlert + +The IE *NR-IntegrityServiceAlert* is used by the location server to indicate whether the corresponding assistance data can be used for integrity related applications. + +``` +-- ASN1START +NR-IntegrityServiceAlert-r18 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF + NR-TRP-IntegrityServiceAlertPerFreqLayer-r18 +NR-TRP-IntegrityServiceAlertPerFreqLayer-r18 ::= SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) + OF TRP-IntegrityServiceAlertElement-r18 +TRP-IntegrityServiceAlertElement-r18 ::= SEQUENCE { + dl-PRS-ID-r18 INTEGER (0..255), + nr-PhysCellID-r18 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r18 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r18 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + rtd-DoNotUse-r18 BOOLEAN OPTIONAL, -- Need OR +} +``` + +``` + +trp-LocationDoNotUse-r18 BOOLEAN OPTIONAL, -- Need OR +beamInfo-DoNotUse-r18 BOOLEAN OPTIONAL, -- Need OR +beamAntennaInfo-DoNotUse-r18 BOOLEAN OPTIONAL, -- Need OR +... +} + +-- ASN1STOP + +``` + +#### NR-IntegrityServiceAlert field descriptions + +##### **rtd-DoNotUse** + +This field indicates whether the RTD info in IE *NR-RTD-Info* can be used for integrity related applications (FALSE) or not (TRUE). + +##### **trp-LocationDoNotUse** + +This field indicates whether the TRP/ARP location in IE *NR-TRP-LocationInfo* can be used for integrity related applications (FALSE) or not (TRUE). + +##### **beamInfo-DoNotUse** + +This field indicates whether the spatial direction information in IE *NR-DL-PRS-BeamInfo* can be used for integrity related applications (FALSE) or not (TRUE). + +##### **beamAntennaInfo-DoNotUse** + +This field indicates whether the beam antenna information in IE *NR-TRP-BeamAntennaInfo* can be used for integrity related applications (FALSE) or not (TRUE). + +### NR-IntegrityServiceParameters + +The IE *NR-IntegrityServiceParameters* is used by the location server to provide the range of Integrity Risk (IR) for which the integrity assistance data are valid. + +``` + +-- ASN1START + +NR-IntegrityServiceParameters-r18 ::= SEQUENCE { + ir-Minimum-r18 INTEGER (0..255), + ir-Maximum-r18 INTEGER (0..255), + ... +} + +-- ASN1STOP + +``` + +#### NR-IntegrityServiceParameters field descriptions + +##### **ir-Minimum** + +This field specifies the Minimum Integrity Risk (IR) which is the minimum IR for which the error bounds provided in the IEs *IntegrityRTD-InfoBounds*, *IntegrityBeamInfoBounds*, *IntegrityBeamPowerBounds*, and *IntegrityLocationBounds* are valid. + +The IR is calculated by $10^{-n}$ where $n$ is the value of *ir-Minimum* and the range is $10^{-102}$ to 1. + +##### **ir-Maximum** + +This field specifies the Maximum Integrity Risk (IR) which is the maximum IR for which the error bounds provided in the IEs *IntegrityRTD-InfoBounds*, *IntegrityBeamInfoBounds*, *IntegrityBeamPowerBounds*, and *IntegrityLocationBounds* are valid. + +The IR is calculated by $10^{-n}$ where $n$ is the value of *ir-Maximum* and the range is $10^{-102}$ to 1. + +### NR-On-Demand-DL-PRS-Configurations + +The IE *NR-On-Demand-DL-PRS-Configurations* provides a set of possible DL-PRS configurations and/or PRS bandwidth aggregation which can be requested by the target device on-demand. + +``` + +-- ASN1START + +NR-On-Demand-DL-PRS-Configurations-r17 ::= SEQUENCE { + on-demand-dl-prs-configuration-list-r17 SEQUENCE (SIZE (1..maxOD-DL-PRS-Configs-r17)) OF + On-Demand-DL-PRS-Configuration-r17, + ..., + [[ + onDemandDL-PRS-AggregationList-r18 SEQUENCE (SIZE (1..maxOD-DL-PRS-Configs-r17)) OF + OnDemandDL-PRS-AggregationInfo-r18 OPTIONAL-- Need ON + ]] +} + +``` + +``` + +On-Demand-DL-PRS-Configuration-r17 ::= SEQUENCE { + dl-prs-configuration-id-r17 DL-PRS-Configuration-ID-r17, + nr-DL-PRS-PositioningFrequencyLayer-r17 NR-DL-PRS-PositioningFrequencyLayer-r16, + nr-DL-PRS-Info-r17 NR-DL-PRS-Info-r16, + ... +} + +DL-PRS-Configuration-ID-r17 ::= SEQUENCE { + nr-dl-prs-configuration-id-r17 INTEGER (1..maxOD-DL-PRS-Configs-r17), + ... +} + +OnDemandDL-PRS-AggregationInfo-r18 ::= SEQUENCE (SIZE (2..3)) OF DL-PRS-Configuration-ID-r17 + +-- ASN1STOP + +``` + +| NR-On-Demand-DL-PRS-Configurations field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-prs-configuration-id
This field provides an identity for the On-Demand-DL-PRS-Configuration . | +| nr-DL-PRS-PositioningFrequencyLayer
This field, together with nr-DL-PRS-Info , provides the On-demand DL-PRS Configuration information.
Only the following fields in IE NR-DL-PRS-PositioningFrequencyLayer are applicable:
dl-PRS-ResourceBandwidth , dl-PRS-CombSizeN .
The target device shall ignore the remaining fields in IE NR-DL-PRS-PositioningFrequencyLayer . | +| nr-DL-PRS-Info
This field, together with nr-DL-PRS-PositioningFrequencyLayer , provides the On-demand DL-PRS Configuration information. Only the following fields in IE NR-DL-PRS-Info are applicable:
DL-PRS periodicity in dl-PRS-Periodicity-and-ResourceSetSlotOffset , dl-PRS-ResourceRepetitionFactor , dl-PRS-NumSymbols , comb-size in dl-PRS-CombSizeN-AndReOffset , dl-PRS-QCL-Info .
The target device shall ignore the remaining fields in IE NR-DL-PRS-Info . | +| onDemandDL-PRS-Aggregationlist
This field indicates the 2 or 3 DL-PRS-Configuration-ID 's whose corresponding On-Demand-DL-PRS-Configuration 's are available for DL-PRS aggregation. | + +## NR-On-Demand-DL-PRS-Information + +The IE *NR-On-Demand-DL-PRS-Information* defines the requested on-demand DL-PRS. + +``` + +-- ASN1START + +NR-On-Demand-DL-PRS-Information-r17 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF + NR-On-Demand-DL-PRS-PerFreqLayer-r17 + +NR-On-Demand-DL-PRS-PerFreqLayer-r17 ::= SEQUENCE { + dl-prs-FrequencyRangeReq-r17 ENUMERATED { fr1, fr2, ... }, + dl-prs-ResourceSetPeriodicityReq-r17 ENUMERATED { p4, p5, p8, p10, p16, p20, p32, p40, + p64, p80, p160, p320, p640, p1280, p2560, + p5120, p10240, p20480, p40960, p81920, ..., + p128-v1760, p256-v1760, p512-v1760 } + dl-prs-ResourceBandwidthReq-r17 INTEGER (1..63) OPTIONAL, + dl-prs-ResourceRepetitionFactorReq-r17 ENUMERATED { n2, n4, n6, n8, n16, n32, ... } OPTIONAL, + dl-prs-NumSymbolsReq-r17 ENUMERATED { n2, n4, n6, n12, ..., n1-v1800 } OPTIONAL, + dl-prs-CombSizeN-Req-r17 ENUMERATED { n2, n4, n6, n12, ... } OPTIONAL, + dl-prs-QCL-InformationReqTRPList-r17 DL-PRS-QCL-InformationReqTRPList-r17 OPTIONAL, + ... +} + +DL-PRS-QCL-InformationReqTRPList-r17 ::= SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF + DL-PRS-QCL-InformationReqPerTRP-r17 + +DL-PRS-QCL-InformationReqPerTRP-r17 ::= SEQUENCE { + dl-PRS-ID-r17 INTEGER (0..255), + nr-PhysCellID-r17 NR-PhysCellID-r16 OPTIONAL, + nr-CellGlobalID-r17 NCGI-r15 OPTIONAL, + nr-ARFCN-r17 ARFCN-ValueNR-r15 OPTIONAL, + dl-prs-QCL-InformationReqSet-r17 SEQUENCE (SIZE (1..nrMaxSetsPerTrpPerFreqLayer-r16)) OF + DL-PRS-QCL-InfoReq-r17, + ... +} + +``` + +``` + +DL-PRS-QCL-InfoReq-r17 ::= SEQUENCE { + nr-DL-PRS-ResourceSetID-r17 NR-DL-PRS-ResourceSetID-r16, + dl-prs-QCL-InformationReq-r17 CHOICE { + dl-prs-QCL-InfoRecPerResourceSet-r17 DL-PRS-QCL-Info-r16, + dl-prs-QCL-Info-requested-r17 NULL + }, + ... + [[ + dl-prs-QCL-InfoRecPerResource-r17 SEQUENCE (SIZE (1..nrMaxResourcesPerSet-r16)) OF + DL-PRS-QCL-Info-r16 OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +| NR-On-Demand-DL-PRS-Information field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-prs-FrequencyRangeReq
This field specifies the frequency range for which the on-demand DL-PRS is requested. | +| dl-prs-ResourceSetPeriodicityReq
This field specifies the requested periodicity of the DL-PRS Resource Set in slots. The periodicity depends on the subcarrier spacing (SCS) and takes values slots, where for SCS of 15, 30, 60 and 120 kHz respectively. $\mu$ refers to the SCS of SSB of target device's current primary cell. | +| dl-prs-ResourceBandwidthReq
This field specifies the requested number of PRBs allocated for the DL-PRS Resource (allocated DL-PRS bandwidth) in multiples of 4 PRBs. Integer value 1 corresponds to 24 PRBs, value 2 corresponds to 28 PRBs, value 3 corresponds to 32 PRBs and so on. | +| dl-prs-ResourceRepetitionFactorReq
This field specifies the requested DL-PRS Resource repetition. Enumerated values n2, n4, n6, n8, n16, n32 correspond to 2, 4, 6, 8, 16, 32 resource repetitions, respectively. | +| dl-prs-NumSymbolsReq
This field specifies the requested number of symbols per DL-PRS Resource within a slot. | +| dl-prs-CombSizeN-Req
This field specifies the requested Resource Element spacing in each symbol of the DL-PRS Resource. | +| dl-prs-QCL-InformationReqTRPList
This field specifies the recommended or requested QCL indication with other DL reference signals.
  • - dl-PRS-ID indicates the DL-PRS ID of the TRP for which the QCL information is recommended.
  • - nr-PhysCellID indicates the physical Cell-ID of the TRP for which the QCL information is recommended, as defined in TS 38.331 [35].
  • - nr-CellGlobalID indicates the NCGI, the globally unique identity of a cell in NR, of the TRP for which the QCL information is recommended, as defined in TS 38.331 [35].
  • - nr-ARFCN indicates the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID.
  • - dl-prs-QCL-InformationReqSet indicates the recommended QCL information per DL-PRS Resource Set.
    • - nr-DL-PRS-ResourceSetID indicates the DL-PRS Resource Set ID for which the QCL information is recommended.
    • - dl-prs-QCL-InformationReq
      • - dl-prs-QCL-InfoRecPerResourceSet indicates a single recommended QCL source for the DL-PRS Resource Set.
      • - dl-prs-QCL-Info-requested indicates that the UE requests to provide the QCL information in the assistance data.
    • - dl-prs-QCL-InfoRecPerResource indicates a list of recommended QCL sources for the DL-PRS Resource Set. If this field is present, the dl-prs-QCL-InformationReq shall be ignored by the receiver.
| + +## NR-On-Demand-DL-PRS-Request + +The IE **NR-On-Demand-DL-PRS-Request** is used by the target device to request on-demand DL-PRS and/or on-demand PRS bandwidth aggregation from a location server. + +``` + +-- ASN1START + +NR-On-Demand-DL-PRS-Request-r17 ::= SEQUENCE { + dl-prs-StartTime-and-Duration-r17 DL-PRS-StartTime-and-Duration-r17 OPTIONAL, + nr-on-demand-DL-PRS-Information-r17 NR-On-Demand-DL-PRS-Information-r17 OPTIONAL, + dl-prs-configuration-id-PrefList-r17 SEQUENCE (SIZE (1..maxOD-DL-PRS-Configs-r17)) OF + DL-PRS-Configuration-ID-r17 OPTIONAL, + ... + [[ + +``` + +``` + +dl-PRS-AggregationID-PrefList-r18 SEQUENCE (SIZE (1.. maxOD-DL-PRS-Configs-r17)) OF + INTEGER (1.. maxOD-DL-PRS-Configs-r17) + OPTIONAL, +nr-OnDemandDL-PRS-AggregationReqList-r18 SEQUENCE (SIZE (1.. maxOD-DL-PRS-Configs-r17)) OF + NR-OnDemandDL-PRS-AggregationReqElement-r18 + OPTIONAL + ]] +} + +DL-PRS-StartTime-and-Duration-r17 ::= SEQUENCE { + dl-prs-start-time-r17 INTEGER (1..1024) OPTIONAL, + dl-prs-duration-r17 SEQUENCE { + seconds-r17 INTEGER (0..59) OPTIONAL, + minutes-r17 INTEGER (0..59) OPTIONAL, + hours-r17 INTEGER (0..23) OPTIONAL, + ... + } + ... +} + +NR-OnDemandDL-PRS-AggregationReqElement-r18 ::= SEQUENCE (SIZE (2..3)) OF + INTEGER (1..nrMaxFreqLayers-r16) + +-- ASN1STOP + +``` + +#### NR-On-Demand-DL-PRS-Request field descriptions + +##### **dl-prs-StartTime-and-Duration** + +This field specifies the requested start time and duration for the on-demand DL-PRS and comprises the following subfields: + +- **dl-prs-start-time** specifies the desired start time for the requested DL-PRS. It indicates the time in seconds from the time the IE *NR-On-Demand-DL-PRS-Request* was received. +- **dl-prs-duration** specifies the desired duration of the requested DL-PRS. The desired duration is the sum of the *seconds*, *minutes*, *hours* fields. If this field is included, at least one of the *seconds*, *minutes*, *hours* fields shall be present. + +##### **nr-on-demand-DL-PRS-Information** + +This field specifies the on-demand DL-PRS configuration information requested by the target device. + +NOTE: If the network provided predefined on-demand DL-PRS configurations (*NR-On-Demand-DL-PRS-Configurations*), the target device can only request explicit parameters (*nr-on-demand-DL-PRS-Information*) within the scope of those configurations. + +##### **dl-prs-configuration-id-PrefList** + +This field specifies the on-demand DL-PRS configuration associated with *DL-PRS-Configuration-ID* in IE *NR-On-Demand-DL-PRS-Configurations* the target device wishes to obtain in the order of preference. The first *DL-PRS-Configuration-ID* in the list is the most preferred configuration, the second *DL-PRS-Configuration-ID* the second most preferred, etc. + +##### **dl-PRS-AggregationID-PrefList** + +This field specifies the on-demand DL-PRS aggregated configuration associated with *onDemandDL-PRS-AggregationList* in IE *NR-On-Demand-DL-PRS-Configurations* the target device wishes to obtain in the order of preference. The first integer value in the list is the most preferred aggregated configuration; the second integer value in the list is the second most preferred, etc. The integer value corresponds to the entry in the field *onDemandDL-PRS-AggregationList* in IE *NR-On-Demand-DL-PRS-Configurations*. + +##### **nr-OnDemandDL-PRS-AggregationReqList** + +This field specifies the aggregated on-demand DL-PRS configuration information requested by the target device in the order of preference. The first *NR-OnDemandDL-PRS-AggregationReqElement* in the list is the most preferred aggregated configuration; the second element in the list is the second most preferred, etc. The integer value in *NR-OnDemandDL-PRS-AggregationReqElement* corresponds to the entry in the IE *NR-On-Demand-DL-PRS-Information*. + +#### NR-On-Demand-DL-PRS-Configurations-Selected-IndexList + +The IE *NR-On-Demand-DL-PRS-Configurations-Selected-IndexList* is used by the location server to provide the selected available on-demand DL-PRS configurations to the target device. + +In the case of available on-demand DL-PRS configurations for multiple NR positioning methods are provided, the *NR-On-Demand-DL-PRS-Configurations* shall be present in only one of *NR-Multi-RTT-ProvideAssistanceData*, *NR-DL-AoD-ProvideAssistanceData*, or *NR-DL-TDOA-ProvideAssistanceData*. + +``` +-- ASN1START +``` + +``` + +NR-On-Demand-DL-PRS-Configurations-Selected-IndexList-r17 ::= + SEQUENCE (SIZE (1..maxOD-DL-PRS-Configs-r17)) OF + DL-PRS-Configuration-ID-r17 + +-- ASN1STOP + +``` + +## – *NR-On-Demand-DL-PRS-Support* + +The IE *NR-On-Demand-DL-PRS-Support* defines the target device's on-demand DL-PRS capabilities. + +``` + +-- ASN1START + +NR-On-Demand-DL-PRS-Support-r17 ::= SEQUENCE { + nr-on-demand-DL-PRS-InformationSup-r17 ENUMERATED { supported } OPTIONAL, + nr-on-demand-DL-PRS-ConfigurationsSup-r17 ENUMERATED { supported } OPTIONAL, + ... +} + +-- ASN1STOP + +``` + +### **NR-On-Demand-DL-PRS-Support field descriptions** + +#### ***nr-on-demand-DL-PRS-InformationSup*** + +This field, if present, indicates that the target device supports the IE *NR-On-Demand-DL-PRS-Information* in IE *NR-On-Demand-DL-PRS-Request*. + +#### ***nr-on-demand-DL-PRS-ConfigurationsSup*** + +This field, if present, specifies that the target device supports the *dl-prs-configuration-id-PrefList* in IE *NR-On-Demand-DL-PRS-Request*. + +## – *NR-PeriodicAssistData* + +The IE *NR-PeriodicAssistData* is used by the location server to provide control parameters for a periodic assistance data delivery session (e.g., interval and duration) to the target device for UE-based carrier phase positioning. + +NOTE: Omission of a particular assistance data type field in IE *NR-PeriodicAssistData* means that the location server does not provide this assistance data type in a data transaction of a periodic assistance data delivery session, as described in clauses 5.2.1a and 5.2.2a. Inclusion of no assistance data type fields in IE *NR-PeriodicAssistData* means that a periodic assistance data delivery session is terminated. + +``` + +-- ASN1START + +NR-PeriodicAssistData-r18 ::= SEQUENCE { + nr-PRU-DL-Info-r18 NR-PeriodicControlParam-r18 OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP + +``` + +## – *NR-PeriodicAssistDataReq* + +The IE *NR-PeriodicAssistDataReq* is used by the target device to request periodic assistance data delivery from a location server. + +``` + +-- ASN1START + +NR-PeriodicAssistDataReq-r18 ::= SEQUENCE { + nr-PRU-DL-InfoReq-r18 NR-PeriodicControlParam-r18 OPTIONAL, -- Cond pPRU + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------| +| pPRU | The field is mandatory present if the target device requests periodic NR-PRU-DL-Info ; otherwise it is not present. | + +## NR-PeriodicControlParam + +The IE *NR-PeriodicControlParam* is used to specify control parameters for a periodic assistance data delivery. + +``` +-- ASN1START + +NR-PeriodicControlParam-r18 ::= SEQUENCE { + deliveryAmount-r18 INTEGER (1..32), + deliveryInterval-r18 INTEGER (4..81920), + ... +} + +-- ASN1STOP +``` + +### NR-PeriodicControlParam field descriptions + +#### *deliveryAmount* + +This field specifies the number of periodic assistance data deliveries. Integer values $N=1\dots31$ correspond to an amount of $2^N$ . Integer value $N=32$ indicates an 'infinite/indefinite' amount, which means that the assistance data delivery should continue until a LPP *Abort* message is received. + +#### *deliveryInterval* + +This field specifies the interval between assistance data deliveries in milliseconds. + +## NR-PositionCalculationAssistance + +The IE *NR-PositionCalculationAssistance* is used by the location server to provide assistance data to enable UE-based downlink positioning. + +``` +-- ASN1START + +NR-PositionCalculationAssistance-r16 ::= SEQUENCE { + nr-TRP-LocationInfo-r16 NR-TRP-LocationInfo-r16 OPTIONAL, -- Need ON + nr-DL-PRS-BeamInfo-r16 NR-DL-PRS-BeamInfo-r16 OPTIONAL, -- Need ON + nr-RTD-Info-r16 NR-RTD-Info-r16 OPTIONAL, -- Need ON + ..., + [[ + nr-TRP-BeamAntennaInfo-r17 NR-TRP-BeamAntennaInfo-r17 OPTIONAL, -- Need ON + nr-DL-PRS-Expected-LOS-NLOS-Assistance-r17 + NR-DL-PRS-ExpectedLOS-NLOS-Assistance-r17 + OPTIONAL, -- Need ON + nr-DL-PRS-TRP-TEG-Info-r17 NR-DL-PRS-TRP-TEG-Info-r17 OPTIONAL -- Need ON + ]], + [[ + nr-IntegrityServiceParameters-r18 NR-IntegrityServiceParameters-r18 OPTIONAL, -- Need OR + nr-IntegrityServiceAlert-r18 NR-IntegrityServiceAlert-r18 OPTIONAL, -- Need OR + nr-IntegrityRiskParameters-r18 NR-IntegrityRiskParameters-r18 OPTIONAL, -- Need OR + nr-IntegrityParametersTRP-LocationInfo-r18 + NR-IntegrityParametersTRP-LocationInfo-r18 OPTIONAL, -- Cond Integrity1 + nr-IntegrityParametersDL-PRS-BeamInfo-r18 + NR-IntegrityParametersDL-PRS-BeamInfo-r18 OPTIONAL, -- Cond Integrity2 + nr-IntegrityParametersRTD-Info-r18 + NR-IntegrityParametersRTD-Info-r18 OPTIONAL, -- Cond Integrity3 + nr-IntegrityParametersTRP-BeamAntennaInfo-r18 + NR-IntegrityParametersTRP-BeamAntennaInfo-r18 OPTIONAL, -- Cond Integrity4 + nr-PRU-DL-Info-r18 NR-PRU-DL-Info-r18 OPTIONAL -- Need ON + ]] +} + +NR-IntegrityParametersTRP-LocationInfo-r18 ::= SEQUENCE { + trp-ErrorCorrelationTime-r18 INTEGER(0..255), + ... +} + +NR-IntegrityParametersDL-PRS-BeamInfo-r18 ::= SEQUENCE { + dl-PRS-BeamInfoErrorCorrelationTime-r18 INTEGER (0..255), + ... +} + +NR-IntegrityParametersRTD-Info-r18 ::= SEQUENCE { + rtd-ErrorCorrelationTime-r18 INTEGER (0..255), + ... +} +``` + +``` + +NR-IntegrityParametersTRP-BeamAntennaInfo-r18 ::= SEQUENCE { + trp-BeamAntennaInfoErrorCorrelationTime-r18 INTEGER (0..255), + ... +} +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Integrity1 | The field is optionally present, need OR, if NR-TRP-LocationInfo is present and integrityReferencePointLocationBounds , IntegrityLocationBounds is present in IE NR-TRP-LocationInfo ; otherwise it is not present. | +| Integrity2 | The field is optionally present, need OR, if NR-DL-PRS-BeamInfo is present and IntegrityBeamInfoBounds is present in IE NR-DL-PRS-BeamInfo ; otherwise it is not present. | +| Integrity3 | The field is optionally present, need OR, if NR-RTD-Info is present and IntegrityRTD-InfoBounds is present in IE NR-RTD-Info ; otherwise it is not present. | +| Integrity4 | The field is optionally present, need OR, if NR-TRP-BeamAntennaInfo is present and IntegrityBeamPowerBounds is present in IE NR-TRP-BeamAntennaInfo ; otherwise it is not present. | + +| NR-PositionCalculationAssistance field descriptions | | +|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-TRP-LocationInfo | This field provides the location coordinates of the TRPs and location coordinates of antenna reference points for DL-PRS Resource Set(s) and DL-PRS Resources of the TRPs. | +| nr-DL-PRS-BeamInfo | This field provides the spatial directions of DL-PRS Resources for TRPs. | +| nr-RTD-Info | This field provides the time synchronization information between the reference TRP and neighbour TRPs. | +| nr-TRP-BeamAntennaInfo | This field provides the relative DL-PRS Resource power between PRS resources per angle per TRP. | +| nr-DL-PRS-ExpectedLOS-NLOS-Assistance | This field provides the expected likelihood of a LOS propagation path from a TRP to the target device. The information is provided per TRP or per DL-PRS Resource. | +| nr-DL-PRS-TRP-TEG-Info | This field provides the TRP Tx TEG ID associated with the transmission of each DL-PRS Resource of the TRP. | +| nr-IntegrityServiceParameters | This field specifies the range of Integrity Risk (IR) for which the integrity assistance data are valid. | +| nr-IntegrityServiceAlert | This field indicates whether the corresponding assistance data can be used for integrity related applications. | +| trp-ErrorCorrelationTime | This field specifies the TRP Error Correlation Time which is the upper bound of the correlation time of the TRP error. The time is calculated using:

Range is 1-28,200 s. | +| rtd-ErrorCorrelationTime | This field specifies the correlation time of the inter-TRP synchronization error. The correlation time is calculated using:

Where i is the value given by rtdErrorCorrelationTime . Range is 1-28,200 s. | +| dl-PRS-BeamInfoErrorCorrelationTime | This field specifies the Beam Boresight Direction Angle Error Correlation Time which is the upper bound of the correlation time of the DL-PRS Resource angle error. The time is calculated using:

Range is 1-28,200 s. | +| trp-BeamAntennaInfoErrorCorrelationTime | This field specifies the Mean Beam Power Error Correlation Time which is the upper bound of the correlation time of the mean beam power error. The time is calculated using:

Range is 1-28,200 s. | +| nr-PRU-DL-Info | This field provides the measurement reported by a PRU to the target UE. | + +## NR-PRU-DL-Info + +The IE *NR-PRU-DL-Info* is used by the location server to provide the carrier phase measurements together with the associated other measurements reported by a PRU (e.g. RSTD) with additional information of this PRU to a target UE. + +``` +-- ASN1START + +NR-PRU-DL-Info-r18 ::= SEQUENCE { + nr-PRU-LocationInfo-r18 LocationCoordinates OPTIONAL, -- Need ON + nr-PRU-DL-TDOA-MeasInfo-r18 NR-DL-TDOA-SignalMeasurementInformation-r16 + OPTIONAL, -- Need ON + nr-PRU-DL-AoD-MeasInfo-r18 NR-DL-AoD-SignalMeasurementInformation-r16 + OPTIONAL, -- Need ON + nr-PRU-RSCP-MeasInfo-r18 NR-PRU-RSCP-MeasurementInformation-r18 + OPTIONAL, -- Need ON + ... +} + +NR-PRU-RSCP-MeasurementInformation-r18 ::= SEQUENCE (SIZE (1..nrMaxTRPs-r16)) OF + NR-PRU-RSCP-MeasElement-r18 + +NR-PRU-RSCP-MeasElement-r18 ::= SEQUENCE { + dl-PRS-ID-r18 INTEGER (0..255), + nr-PhysCellID-r18 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r18 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r18 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + nr-DL-PRS-ResourceID-r18 NR-DL-PRS-ResourceID-r16 OPTIONAL, -- Need ON + nr-DL-PRS-ResourceSetID-r18 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, -- Need ON + nr-TimeStamp-r18 NR-TimeStamp-r16, + nr-los-nlos-Indicator-r18 CHOICE { + perTRP LOS-NLOS-Indicator-r17, + perResource LOS-NLOS-Indicator-r17 + } + nr-RSCP-r18 INTEGER (0..3600) OPTIONAL, -- Need ON + nr-PhaseQuality-r18 NR-PhaseQuality-r18 OPTIONAL, -- Need ON + nr-PRU-RSCP-AddSampleMeasurements-r18 SEQUENCE (SIZE (1..nrNumOfSamples-1-r18 )) OF + NR-RSCP-AdditionalMeasurements-r18 OPTIONAL, -- Need ON + nr-PRU-RSCP-AdditionalMeasurements-r18 NR-PRU-RSCP-AdditionalMeasurements-r18 OPTIONAL, -- Need ON + ... +} + +NR-PRU-RSCP-AdditionalMeasurements-r18 ::= SEQUENCE (SIZE (1..3)) OF + NR-PRU-RSCP-AdditionalMeasurementElement-r18 + +NR-PRU-RSCP-AdditionalMeasurementElement-r18 ::= SEQUENCE { + nr-DL-PRS-ResourceID-r18 NR-DL-PRS-ResourceID-r16 OPTIONAL, -- Need ON + nr-DL-PRS-ResourceSetID-r18 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, -- Need ON + nr-PRU-RSCP-AdditionalMeasurementsList-r18 SEQUENCE (SIZE (1..nrNumOfSamples-r18 )) OF + NR-RSCP-AdditionalMeasurements-r18 OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP +``` + +### NR-PRU-DL-Info field descriptions + +#### ***nr-PRU-LocationInfo*** + +This field provides the location coordinates of the PRU. + +#### ***nr-PRU-DL-TDOA-MeasInfo*** + +This field specifies the list of carrier phase measurement RSCPD together with the other measurement information in DL-TDOA by the PRU. + +#### ***nr-PRU-DL-AoD-MeasInfo*** + +This field specifies the list of other measurement information in DL-AoD by the PRU. + +#### ***nr-PRU-RSCP-MeasInfo*** + +This field specifies the list of carrier phase measurement RSCP measured by the PRU. + +## NR-RTD-Info + +The IE *NR-RTD-Info* is used by the location server to provide time synchronization information between a reference TRP and a list of neighbour TRPs. + +``` + +-- ASN1START + +NR-RTD-Info-r16 ::= SEQUENCE { + referenceTRP-RTD-Info-r16 ReferenceTRP-RTD-Info-r16, + rtd-InfoList-r16 RTD-InfoList-r16, + ... +} + +ReferenceTRP-RTD-Info-r16 ::= SEQUENCE { + dl-PRS-ID-Ref-r16 INTEGER (0..255), + nr-PhysCellID-Ref-r16 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-Ref-r16 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-Ref-r16 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + refTime-r16 CHOICE { + systemFrameNumber-r16 BIT STRING (SIZE (10)), + utc-r16 UTCTime, + ... + }, + rtd-RefQuality-r16 NR-TimingQuality-r16 OPTIONAL, -- Need ON + ... +} + +RTD-InfoList-r16 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF RTD-InfoListPerFreqLayer-r16 + +RTD-InfoListPerFreqLayer-r16 ::= SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF RTD-InfoElement-r16 + +RTD-InfoElement-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r16 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r16 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + subframeOffset-r16 INTEGER (0..1966079), + rtd-Quality-r16 NR-TimingQuality-r16, + ..., + [[ + integrityRTD-InfoBounds-r18 IntegrityRTD-InfoBounds-r18 OPTIONAL -- Need OR + ]] +} + +IntegrityRTD-InfoBounds-r18 ::= SEQUENCE { + meanRTD-r18 INTEGER (0..255), + stdDevRTD-r18 StdDevRTD-r18, + ... +} + +StdDevRTD-r18 ::= SEQUENCE { + value-r18 INTEGER (0..31), + resolution-r18 ENUMERATED {mdot1, m1, m10, m30, ...} +} + +-- ASN1STOP + +``` + +| NR-RTD-Info field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| referenceTRP-RTD-Info
This field defines the reference TRP for the RTD and comprises the following sub-fields:
  • - dl-PRS-ID-Ref: This field is used along with a DL-PRS Resource Set ID and a DL-PRS Resources ID to uniquely identify a DL-PRS Resource, and is associated to the reference TRP.
  • - nr-PhysCellId-Ref: This field specifies the physical cell identity of the reference TRP.
  • - nr-CellGlobalId-Ref: This field specifies the NCGI, the globally unique identity of a cell in NR, of the reference TRP.
  • - nr-ARFCN-Ref: This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellId.
  • - refTime: This field specifies the reference time at which the rtd-InfoList is valid. The systemFrameNumber choice refers to the SFN of the reference TRP.
  • - rtd-RefQuality: This field specifies the quality of the timing of reference TRP, used to determine the RTD values provided in rtd-InfoList.
| +| dl-PRS-ID
This field is used along with a DL-PRS Resource Set ID and a DL-PRS Resources ID to uniquely identify a DL-PRS Resource. This ID can be associated with multiple DL-PRS Resource Sets associated with a single TRP for which the RTD-InfoElement is applicable. | +| nr-PhysCellID
This field specifies the physical cell identity of the associated TRP for which the RTD-InfoElement is applicable, as defined in TS 38.331 [35]. | +| nr-CellGlobalID
This field specifies the NCGI, the globally unique identity of a cell in NR, of the associated TRP for which the RTD-InfoElement is applicable, as defined in TS 38.331 [35]. The server should include this field if it considers that it is needed to resolve ambiguity in the TRP indicated by nr-PhysCellID . | +| nr-ARFCN
This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID for which the RTD-InfoElement is applicable. | +| subframeOffset
This field specifies the subframe boundary offset at the TRP antenna location between the reference TRP and this neighbour TRP in time units where Hz and (TS 38.211 [41]).
The offset is counted from the beginning of a subframe #0 of the reference TRP to the beginning of the closest subsequent subframe of this neighbour TRP.
Scale factor 1 T c . | +| rtd-Quality
This field specifies the quality of the RTD. | +| integrityRTD-InfoBounds
This field specifies an overbounding model that bounds the inter-TRP synchronization error between reference TRP and this TRP. This field comprises the following sub-fields:
  • - meanRTD: This field specifies the mean value of the inter-TRP synchronization error bound of the overbounding model. The bound is meanRTD + K * stdDevRTD and shall be so that the probability of it to be exceeded shall be lower than IR_{allocation} for ir\text{-Minimum} < IR_{allocation} < ir\text{-Maximum}, where K = \text{normInv}(IR_{allocation} / 2) and ir\text{-Minimum}, ir\text{-Maximum} as provided in IE NR-IntegrityServiceParameters. This IR_{allocation} is a fraction of the Target Integrity Risk that represents the integrity risk budget available. Default value is 0 if absent.
  • - stdDevRTD: This field specifies the standard deviation of the inter-TRP synchronization error bound of the overbounding model. The value field used in the stdDevRTD is provided in units of metres. The resolution is used in the value field of stdDevRTD. The enumerated values m0t1, m1, m10, m30 correspond to 0.1, 1, 10, 30 metres, respectively.
| + +## NR-SelectedDL-PRS-IndexList + +The IE *NR-SelectedDL-PRS-IndexList* is used by the location server to provide the selected DL-PRS Resource of *nr-DL-PRS-AssistanceDataList* to the target device. + +In the case of assistance data for multiple NR positioning methods are provided, the IE *NR-DL-PRS-AssistanceData* shall be present in only one of *NR-Multi-RTT-ProvideAssistanceData*, *NR-DL-AoD-ProvideAssistanceData*, or *NR-DL-TDOA-ProvideAssistanceData*. + +``` +-- ASN1START + +NR-SelectedDL-PRS-IndexList-r16 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF + NR-SelectedDL-PRS-PerFreq-r16 + +NR-SelectedDL-PRS-PerFreq-r16 ::= SEQUENCE { + nr-SelectedDL-PRS-FrequencyLayerIndex-r16 INTEGER (0..nrMaxFreqLayers-1-r16), + nr-SelectedDL-PRS-IndexListPerFreq-r16 SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF +``` + +``` + +NR-SelectedDL-PRS-IndexPerTRP-r16 +OPTIONAL, --Need OP +... +} + +NR-SelectedDL-PRS-IndexPerTRP-r16 ::= SEQUENCE { + nr-SelectedTRP-Index-r16 INTEGER (0..nrMaxTRPsPerFreq-1-r16), + dl-SelectedPRS-ResourceSetIndexList-r16 SEQUENCE (SIZE (1..nrMaxSetsPerTrpPerFreqLayer-r16)) OF + DL-SelectedPRS-ResourceSetIndex-r16 + OPTIONAL, --Need OP + ... +} + +DL-SelectedPRS-ResourceSetIndex-r16 ::= SEQUENCE { + nr-DL-SelectedPRS-ResourceSetIndex-r16 INTEGER (0..nrMaxSetsPerTrpPerFreqLayer-1-r16), + dl-SelectedPRS-ResourceIndexList-r16 SEQUENCE (SIZE (1..nrMaxResourcesPerSet-r16)) OF + DL-SelectedPRS-ResourceIndex-r16 + OPTIONAL --Need OP +} + +DL-SelectedPRS-ResourceIndex-r16 ::= SEQUENCE { + nr-DL-SelectedPRS-ResourceIndex-r16 INTEGER (0..nrMaxNumDL-PRS-ResourcesPerSet-1-r16), + ... +} + +-- ASN1STOP + +``` + +#### **NR-SelectedDL-PRS-IndexList field descriptions** + +##### ***nr-SelectedDL-PRS-FrequencyLayerIndex*** + +This field indicates the frequency layer provided in IE *NR-DL-PRS-AssistanceData*. Value 0 corresponds to the first frequency layer provided in *nr-DL-PRS-AssistanceDataList* in IE *NR-DL-PRS-AssistanceData*, value 1 to the second frequency layer in *nr-DL-PRS-AssistanceDataList*, and so on. + +##### ***nr-SelectedDL-PRS-IndexListPerFreq*** + +This field provides the list of addressed TRPs of the selected frequency layer. If this field is absent, all DL-PRS Resources of all TRPs of the indicated frequency layer are addressed. + +##### ***nr-SelectedTRP-Index*** + +This field indicates the addressed TRP of the selected frequency layer. Value 0 corresponds to the first entry in *nr-DL-PRS-AssistanceDataPerFreq* provided in IE *NR-DL-PRS-AssistanceData*, value 1 corresponds to the second entry in *nr-DL-PRS-AssistanceDataPerFreq*, and so on. + +##### ***dl-SelectedPRS-ResourceSetIndexList*** + +This field provides the list of addressed DL-PRS Resource Sets of the selected TRPs of the selected frequency layer. If this field is absent, all DL-PRS Resource Sets and Resources of the indicated TRP are addressed. + +##### ***nr-DL-SelectedPRS-ResourceSetIndex*** + +This field indicates the addressed DL-PRS Resource Set of the selected TRP of the selected frequency layer. Value 0 corresponds to the first entry in *nr-DL-PRS-ResourceSetList* in IE *NR-DL-PRS-Info* provided in IE *NR-DL-PRS-AssistanceData*. Value 1 corresponds to the second entry in the *nr-DL-PRS-ResourceSetList* in IE *NR-DL-PRS-Info*. + +##### ***dl-SelectedPRS-ResourceIndexList*** + +This field provides the list of addressed DL-PRS Resources of the selected DL-PRS Resource Set of the selected TRP of the selected frequency layer. If this field is absent, all DL-PRS Resources of the indicated DL-PRS Resource Set are addressed. + +##### ***nr-dl-SelectedPRS-ResourceIndex*** + +This field indicates the addressed DL-PRS Resource of the selected DL-PRS Resource Set of the TRP of the selected frequency layer. Value 0 corresponds to the first entry in *dl-PRS-ResourceList* in IE *NR-DL-PRS-Info* provided in IE *NR-DL-PRS-AssistanceData*. Value 1 corresponds to the second entry in the *dl-PRS-ResourceList* in IE *NR-DL-PRS-Info*, and so on. + +## ***NR-SSB-Config*** + +The IE *NR-SSB-Config* defines SSB configuration. + +``` + +-- ASN1START + +NR-SSB-Config-r16 ::= SEQUENCE { + nr-PhysCellID-r16 NR-PhysCellID-r16, + nr-ARFCN-r16 ARFCN-ValueNR-r15, + ss-PBCH-BlockPower-r16 INTEGER (-60..50), + halfFrameIndex-r16 INTEGER (0..1), + ssb-periodicity-r16 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, ...}, + ssb-PositionsInBurst-r16 CHOICE { + shortBitmap-r16 BIT STRING (SIZE (4)), + } +} + +``` + +``` + + mediumBitmap-r16 BIT STRING (SIZE (8)), + longBitmap-r16 BIT STRING (SIZE (64)) + } + ssb-SubcarrierSpacing-r16 ENUMERATED {kHz15, kHz30, kHz60, kHz120, kHz240, ...}, + sfn-SSB-Offset-r16 INTEGER (0..15), + ... +} + +-- ASN1STOP + +``` + +#### NR-SSB-Config field descriptions + +| | | +|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-ARFCN | This field specifies the ARFCN of the first RE of SSB's RB#10. | +| ss-PBCH-BlockPower | Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [48], clause 7. | +| halfFrameIndex | Indicates the 5 msec offset of the SSB within a 10 msec system frame. | +| ssb-periodicity | The SSB periodicity in ms for the rate matching purpose. | +| ssb-PositionsInBurst | Indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [48], clause 4.1. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted. | +| ssb-SubcarrierSpacing | Subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable. | +| sfn-SSB-Offset | Indicates the 10 msec system frame offset of the SSB within the SSB periodicity. Value 0 indicates that the SSB is transmitted in the first system frame; 1 indicates that the SSB is transmitted in the second system frame and so on. This field shall be configured according to the field ssb-Periodicity and the indicated system frame shall not exceed the configured SSB periodicity. | + +#### NR-TimeStamp + +The IE *NR-TimeStamp* defines the UE measurement associated time stamp. + +``` + +-- ASN1START + +NR-TimeStamp-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r16 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r16 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + nr-SFN-r16 INTEGER (0..1023), + nr-Slot-r16 CHOICE { + scs15-r16 INTEGER (0..9), + scs30-r16 INTEGER (0..19), + scs60-r16 INTEGER (0..39), + scs120-r16 INTEGER (0..79) + }, + ..., + [[ + nr-Symbol-r18 INTEGER (0..13) OPTIONAL -- Need OR + ]] +} + +-- ASN1STOP + +``` + +| NR-Timestamp field descriptions | | +|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PRS-ID | This field specifies the DL-PRS ID of the TRP for which the nr-SFN is applicable. | +| nr-PhysCellID | This field specifies the physical cell identity of the associated TRP, as defined in TS 38.331 [35]. | +| nr-CellGlobalID | This field specifies the NCGI, the globally unique identity of a cell in NR, of the associated TRP, as defined in TS 38.331 [35]. | +| nr-ARFCN | This field specifies the ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID associated with the dl-PRS-ID . | +| nr-SFN | This field specifies the NR system frame number for the time stamp. | +| nr-Slot | This field specifies the NR slot number within the NR system frame number indicated by nr-SFN for the time stamp. | +| nr-Symbol | This field specifies the NR symbol index within the NR slot number indicated by nr-Slot for the time stamp for RSCP/RSCPD measurement. | + +## NR-TimingQuality + +The IE *NR-TimingQuality* defines the quality of a timing value (e.g., of a TOA measurement). + +``` +-- ASN1START + +NR-TimingQuality-r16 ::= SEQUENCE { + timingQualityValue-r16 INTEGER (0..31), + timingQualityResolution-r16 ENUMERATED {mdot1, m1, m10, m30, ...}, + ... +} + +-- ASN1STOP +``` + +| NR-TimingQuality field descriptions | | +|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| timingQualityValue | This field provides an estimate of uncertainty of the timing value for which the IE NR-TimingQuality is provided in units of metres. | +| timingQualityResolution | This field provides the resolution used in the timingQualityValue field. Enumerated values mdot1, m1, m10, m30 correspond to 0.1, 1, 10, 30 metres, respectively. | + +## NR-TRP-BeamAntennaInfo + +The IE *NR-TRP-BeamAntennaInfo* is used by the location server to provide beam antenna information of the TRP together with integrity information. + +``` +-- ASN1START + +NR-TRP-BeamAntennaInfo-r17 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF + NR-TRP-BeamAntennaInfoPerFreqLayer-r17 + +NR-TRP-BeamAntennaInfoPerFreqLayer-r17 ::= SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF + NR-TRP-BeamAntennaInfoPerTRP-r17 + +NR-TRP-BeamAntennaInfoPerTRP-r17 ::= SEQUENCE { + dl-PRS-ID-r17 INTEGER (0..255), + nr-PhysCellID-r17 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r17 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r17 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + associated-DL-PRS-ID-r17 INTEGER (0..255) OPTIONAL, -- Need OP + lcs-GCS-TranslationParameter-r17 LCS-GCS-TranslationParameter-r16 OPTIONAL, -- Need OP + nr-TRP-BeamAntennaAngles-r17 NR-TRP-BeamAntennaAngles-r17 OPTIONAL, -- Need OP + ... +} + +NR-TRP-BeamAntennaAngles-r17 ::= SEQUENCE (SIZE (1..3600)) OF + NR-TRP-BeamAntennaInfoAzimuthElevation-r17 +``` + +``` + +NR-TRP-BeamAntennaInfoAzimuthElevation-r17 ::= SEQUENCE { + azimuth-r17 INTEGER (0..359) OPTIONAL, -- Cond Az + azimuth-fine-r17 INTEGER (0..9) OPTIONAL, -- Cond AzOpt + elevationList-r17 SEQUENCE (SIZE(1..1801)) OF ElevationElement-R17, + ... +} + +ElevationElement-R17 ::= SEQUENCE { + elevation-r17 INTEGER (0..180) OPTIONAL, -- Cond El + elevation-fine-r17 INTEGER (0..9) OPTIONAL, -- Cond ElOpt + beamPowerList-r17 SEQUENCE (SIZE (2..maxNumResourcesPerAngle-r17)) OF + BeamPowerElement-r17, + ... +} + +BeamPowerElement-r17 ::= SEQUENCE { + nr-dl-prs-ResourceSetID-r17 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, -- Need OP + nr-dl-prs-ResourceID-r17 NR-DL-PRS-ResourceID-r16, + nr-dl-prs-RelativePower-r17 INTEGER (0..30), + nr-dl-prs-RelativePowerFine-r17 INTEGER (0..9) OPTIONAL, -- Need ON + ..., + [[ + integrityBeamPowerBounds-r18 IntegrityBeamPowerBounds-r18 OPTIONAL -- Need OP + ]] +} + +IntegrityBeamPowerBounds-r18 ::= SEQUENCE { + meanBeamPower-r18 INTEGER (0..128), + stdDevBeamPower-r18 INTEGER (0..128), + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------| +| Az | The field is mandatory present if the field elevation is absent; otherwise it is optionally present, need ON. | +| AzOpt | The field is optionally present, need ON, when azimuth is present; otherwise it is not present. | +| El | The field is mandatory present if the field azimuth is absent; otherwise it is optionally present, need ON. | +| ElOpt | The field is optionally present, need ON, when elevation is present; otherwise it is not present. | + +| NR-TRP-BeamAntennaInfo field descriptions | | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PRS-ID | This field specifies the DL-PRS ID of the TRP for which the Beam Antenna Information is provided. | +| nr-PhysCellID | This field specifies the physical Cell-ID of the TRP for which the Beam Antenna Information is provided, as defined in TS 38.331 [35]. | +| nr-CellGlobalID | This field specifies the NCGI, the globally unique identity of a cell in NR, of the TRP for which the Beam Antenna Information is provided, as defined in TS 38.331 [35]. | +| nr-ARFCN | This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID . | +| associated-DL-PRS-ID | This field specifies the dl-PRS-ID of the associated TRP from which the beam antenna information is obtained. See the field descriptions for nr-TRP-BeamAntennaAngles and Ics-GCS-TranslationParameter . | +| Ics-GCS-TranslationParameter | This field provides the angles $\alpha$ (bearing angle), $\beta$ (downtilt angle) and $\gamma$ (slant angle) for the translation of a Local Coordinate System (LCS) to a Global Coordinate System (GCS) as defined in TR 38.901 [44]. If this field and the associated-DL-PRS-ID field are both absent, the azimuth and elevation are provided in a GCS. If this field is absent and the associated-DL-PRS-ID field is present, then the Ics-GCS-TranslationParameter for this TRP is obtained from the Ics-GCS-TranslationParameter of the associated TRP. | +| nr-TRP-BeamAntennaAngles | This field provides the relative power between DL-PRS Resources per angle per TRP. If this field is absent and the field associated-DL-PRS-ID is present, the nr-TRP-BeamAntennaAngles for this TRP are obtained from the nr-TRP-BeamAntennaAngles of the associated TRP. | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

azimuth
This field specifies the azimuth angle for which the relative power between DL-PRS Resources is provided.
For a Global Coordinate System (GCS), the azimuth angle is measured counter-clockwise from geographical North.
For a Local Coordinate System (LCS), the azimuth angle is measured counter-clockwise from the x-axis of the LCS.
Scale factor 1 degree; range 0 to 359 degrees.

| +|

azimuth-fine
This field provides finer granularity for the azimuth.
The total azimuth angle is given by azimuth + azimuth-fine.
Scale factor 0.1 degrees; range 0 to 0.9 degrees.

| +|

elevation
This field specifies the elevation angle for which the relative power between DL-PRS Resources is provided for the given azimuth.
For a Global Coordinate System (GCS), the elevation angle is measured relative to zenith and positive to the horizontal direction (elevation 0 deg. points to zenith, 90 deg to the horizon).
For a Local Coordinate System (LCS), the elevation angle is measured relative to the z-axis of the LCS (elevation 0 deg. points to the z-axis, 90 deg to the x-y plane).
Scale factor 1 degree; range 0 to 180 degrees.

| +|

elevation-fine
This field provides finer granularity for the elevation.
The total elevation angle is given by elevation + elevation-fine.
Scale factor 0.1 degrees; range 0 to 0.9 degrees.

| +|

beamPowerList
This field provides the relative power between DL-PRS Resources for the angle given by azimuth and elevation.
The first BeamPowerElement in this list provides the peak power for this angle and is defined as 0dB power; i.e., the first value is set to '0' by the location server. All the remaining BeamPowerElement's in this list provide the relative DL-PRS Resource power relative to this first element in the list.

| +|

nr-dl-prs-ResourceSetID
This field specifies the DL-PRS Resource Set ID of the DL-PRS Resource for which the nr-dl-prs-RelativePower is provided. If this field is absent, the DL-PRS Resource Set ID for this instance of the beamPowerList is the same as the DL-PRS Resource Set ID of the previous instance in the beamPowerList. This field shall be included at least in the first instance of the beamPowerList.

| +|

nr-dl-prs-ResourceID
This field specifies the DL-PRS Resource for which the nr-dl-prs-RelativePower is provided.

| +|

nr-dl-prs-RelativePower
Except for the first element in beamPowerList, this field provides the relative power of the DL-PRS Resource, relative to the first element in the beamPowerList.
For the first element in beamPowerList, this field provides the peak power for this angle normalised to 0 dB.
Scale factor 1 dB; range 0..-30 dB.

| +|

nr-dl-prs-RelativePowerFine
This field provides finer granularity for the nr-dl-prs-RelativePower.
The total relative power of the DL-PRS Resource is given by nr-dl-prs-RelativePower + nr-dl-prs-RelativePowerFine.
Scale factor -0.1 dB; range 0 to -0.9 dB.
NOTE: For the first element in beamPowerList, this field is not needed.

| +|

integrityBeamPowerBounds
This field specifies the mean and the Standard Deviation beam power error bound for an overbounding model that bounds the beam power error. If this field is absent, the integrityBeamInfoBounds for this instance of the beamPowerList is the same as integrityBeamInfoBounds of the previous instance in the beamPowerList. If integrity bounds are provided, this field shall be included at least in the first instance of the beamPowerList.

| +|

meanBeamPower
This field specifies the Mean Beam Power Error bound which is the mean value for an overbounding model that bounds the beam power error of the DL-PRS Resources.
The bound is meanBeamPower + K * stdDevBeamPower and shall be so that the probability of it to be exceeded shall be lower than IR_{allocation} for ir-Minimum < IR_{allocation} < ir-Maximum, where K = \text{normInv}(IR_{allocation} / 2) and ir-Minimum, irMaximum as provided in IE NR-Integrity-ServiceParameters.
This IR_{allocation} is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
Scale factor 0.1 dB; range 0-12.8 dB.

| +|

stdDevBeamPower
This field specifies the Standard Deviation Beam Power Error bound which is the standard deviation for an overbounding model that bounds the beam power error of the DL-PRS Resources.
Scale factor 0.1 degrees; range 0-12.8 dB.

| + +## NR-TRP-LocationInfo + +The IE *NR-TRP-LocationInfo* is used by the location server to provide the coordinates of TRPs and coordinates of the antenna reference points for a set of TRPs. For each TRP, the ARP location can be provided for each associated PRS Resource ID per PRS Resource Set. + +``` + +-- ASN1START + +NR-TRP-LocationInfo-r16 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers-r16)) OF + NR-TRP-LocationInfoPerFreqLayer-r16 + +NR-TRP-LocationInfoPerFreqLayer-r16 ::= SEQUENCE { + referencePoint-r16 ReferencePoint-r16 OPTIONAL, -- Cond NotSameAsPrev + trp-LocationInfoList-r16 SEQUENCE (SIZE (1..nrMaxTRPsPerFreq-r16)) OF + TRP-LocationInfoElement-r16, + ... +} + +TRP-LocationInfoElement-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, -- Need ON + nr-CellGlobalID-r16 NCGI-r15 OPTIONAL, -- Need ON + nr-ARFCN-r16 ARFCN-ValueNR-r15 OPTIONAL, -- Need ON + associated-DL-PRS-ID-r16 INTEGER (0..255) OPTIONAL, -- Need OP + trp-Location-r16 RelativeLocation-r16 OPTIONAL, -- Need OP + trp-DL-PRS-ResourceSets-r16 SEQUENCE (SIZE(1..nrMaxSetsPerTrpPerFreqLayer-r16)) OF + DL-PRS-ResourceSets-TRP-Element-r16 OPTIONAL, -- Need OP + ..., + [[ + trp-LocationCartesian-r18 RelativeCartesianLocation-r18 OPTIONAL, -- Need OP + integrityTRP-LocationBounds-r18 IntegrityLocationBounds-r18 OPTIONAL -- Need OR + ]] +} + +DL-PRS-ResourceSets-TRP-Element-r16 ::= SEQUENCE { + dl-PRS-ResourceSetARP-r16 RelativeLocation-r16 OPTIONAL, -- Need OP + dl-PRS-Resource-ARP-List-r16 SEQUENCE (SIZE(1..nrMaxResourcesPerSet-r16)) OF + DL-PRS-Resource-ARP-Element-r16 OPTIONAL, -- Need OP + ..., + [[ + dl-PRS-ResourceSetARP-Cartesian-r18 RelativeCartesianLocation-r18 OPTIONAL, -- Need OP + integrityDL-PRS-ResourceSetARP-LocationBounds-r18 IntegrityLocationBounds-r18 OPTIONAL -- Need OR + ]] +} + +DL-PRS-Resource-ARP-Element-r16 ::= SEQUENCE { + dl-PRS-Resource-ARP-location-r16 RelativeLocation-r16 OPTIONAL, -- Need OP + ..., + [[ + dl-PRS-Resource-ARP-locationCartesian-r18 RelativeCartesianLocation-r18 OPTIONAL, -- Need OP + integrityDL-PRS-ResourceARP-LocationBounds-r18 IntegrityLocationBounds-r18 OPTIONAL -- Need OR + ]] +} + +IntegrityLocationBounds-r18 ::= SEQUENCE { + meanLatitude-r18 INTEGER (0..255), + meanLongitude-r18 INTEGER (0..255), + meanheight-r18 INTEGER (0..255), + stdDevLatitude-r18 INTEGER (0..255), + stdDevLongitude-r18 INTEGER (0..255), + stdDevheight-r18 INTEGER (0..255), + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NotSameAsPrev | The field is mandatory present in the first entry of the NR-TRP-LocationInfoPerFreqLayer in the NR-TRP-LocationInfo list; otherwise it is optionally present, need OP. | + +| NR-TRP-LocationInfo field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

referencePoint
This field specifies the reference point used to define the location of TRPs provided in the trp-LocationInfoList. If this field is absent, the reference point is the same as in the previous entry of the NR-TRP-LocationInfoPerFreqLayer in the NR-TRP-LocationInfo list.

| +|

trp-LocationInfoList
This field provides the antenna reference point locations of the DL-PRS Resources for the TRPs and comprises the following sub-fields:

  • - dl-PRS-ID: This field is used along with a DL-PRS Resource Set ID and a DL-PRS Resource ID to uniquely identify a DL-PRS Resource, and is associated to a single TRP.
  • - nr-PhysCellID: This field specifies the physical cell identity of the associated TRP.
  • - nr-CellGlobalID: This field specifies the NCGI, the globally unique identity of a cell in NR, of the associated TRP.
  • - nr-ARFCN: This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID.
  • - associated-DL-PRS-ID: This field, if present, specifies the dl-PRS-ID of the associated TRP from which the trp-Location or trp-LocationCartesian information is adopted. If the field is present, the field trp-Location and trp-LocationCartesian shall be absent.
  • - trp-Location, trp-LocationCartesian: This field provides the location of the TRP relative to the referencePoint location either in geodetic coordinates (trp-Location) or local Cartesian coordinates (trp-LocationCartesian). If this field is absent the TRP location coincides with the referencePoint location, unless the field associated-dl-PRS-ID is present, in which case the trp-Location or trp-LocationCartesian is adopted from the associated TRP indicated by associated-dl-PRS-ID.
  • - trp-DL-PRS-ResourceSets: This field provides the antenna reference point location(s) of the DL-PRS Resource Set(s) associated with this TRP. If this field is absent, the antenna reference point location(s) of the DL-PRS Resource Set(s) coincides with the trp-Location/trp-LocationCartesian location. This field comprises the following sub-fields:
    • - dl-PRS-ResourceSetARP, dl-PRS-ResourceSetARP-Cartesian: This field provides the antenna reference point location of the DL-PRS Resource Set relative to the trp-Location or trp-LocationCartesian location. If this field is absent, the antenna reference point location of this DL-PRS Resource Set coincides with the trp-Location or trp-LocationCartesian location.
    • - integrityDL-PRS-ResourceSetARP-LocationBounds: This field specifies the mean and the Standard Deviation location error bound for an overbounding model that bounds the antenna reference point location error of the DL-PRS Resource Set.
    • - dl-PRS-Resource-ARP-List: This field provides the antenna reference point location(s) of the DL-PRS Resource(s) associated with this Resource Set of the TRP. If this field is absent, the antenna reference point location(s) of the DL-PRS Resources coincides with the dl-PRS-ResourceSetARP location or dl-PRS-ResourceSetARP-Cartesian. This field comprises the following sub-fields:
      • - dl-PRS-Resource-ARP-location, dl-PRS-Resource-ARP-locationCartesian: This field provides the antenna reference point location of the DL-PRS Resource associated with the DL-PRS Resource Set of the TRP relative to the dl-PRS-ResourceSetARP/dl-PRS-ResourceSetARP-Cartesian location. If this field is absent, the antenna reference point location of this DL-PRS Resource coincides with the dl-PRS-ResourceSetARP location or dl-PRS-Resource-ARP-locationCartesian.
      • - integrityDL-PRS-ResourceARP-LocationBounds: This field specifies the mean and the Standard Deviation location error bound for an overbounding model that bounds the antenna reference point location error of the DL-PRS Resource associated with the DL-PRS Resource Set of the TRP.
      • - integrityTRP-LocationBounds: This field specifies the mean and the Standard Deviation TRP location error bound for an overbounding model that bounds the TRP location error.
| +|

IntegrityLocationBounds
This field specifies the mean and the standard deviation of the location error bound of the overbounding model that bounds the location error, and comprises the following sub-fields:

  • - meanLatitude, meanLongitude, meanheight: This field specifies the location error bound in Latitude, Longitude, height, which are the mean value for an overbounding model that bounds the corresponding Latitude, Longitude, height error of the reference point location. The bound is \text{mean} + K * \text{stdDev} and shall be so that the probability of it to be exceeded shall be lower than \text{IR}_{\text{allocation}} for ir-Minimum < \text{IR}_{\text{allocation}} < ir-Maximum, where K = \text{normInv}(\text{IR}_{\text{allocation}} / 2) and ir-Minimum, ir-Maximum as provided in IE NR-Integrity-ServiceParameters. This \text{IR}_{\text{allocation}} is a fraction of the Target Integrity Risk that represents the integrity risk budget available. Scale factor 0.1 degrees; range 0-25.5 degrees.
  • - stdDevLatitude, stdDevLongitude, stdDevheight: This field specifies the Standard Deviation Location Error bound in Latitude, Longitude, height, which are the standard deviation values for the overbounding model that bounds the location of the reference point error in Latitude, Longitude, height. Scale factor 0.1 degrees; range 0-25.5 degrees.

If integrity bounds are provided, the field shall be present at least in the first entry of the NR-TRP-LocationInfoPerFreqLayer list.

| + +NOTE 5: The locations may be provided in either geodetic coordinates (*RelativeLocation*) or local Cartesian coordinates (*RelativeCartesianLocation*), but not both. + +## NR-UE-TEG-Capability + +The IE *NR-UE-TEG-Capability* defines the TEG capability of the target device. + +``` +-- ASN1START + +NR-UE-TEG-Capability-r17 ::= SEQUENCE { + nr-UE-TEG-ID-CapabilityBandList-r17 SEQUENCE (SIZE (1..nrMaxBands-r16)) OF + NR-UE-TEG-ID-CapabilityPerBand-r17 OPTIONAL, + ... +} + +NR-UE-TEG-ID-CapabilityPerBand-r17 ::= SEQUENCE { + freqBandIndicatorNR-r17 FreqBandIndicatorNR-r16, + nr-UE-RxTEG-ID-MaxSupport-r17 ENUMERATED {n1, n2, n3, n4, n6, n8} OPTIONAL, + nr-UE-TxTEG-ID-MaxSupport-r17 ENUMERATED {n1, n2, n3, n4, n6, n8} OPTIONAL, + nr-UE-RxTxTEG-ID-MaxSupport-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, + n24, n32, n36, n48, n64} OPTIONAL, + measureSameDL-PRS-ResourceWithDifferentRxTEGs-r17 + ENUMERATED {n2, n3, n4, n6, n8} OPTIONAL, + measureSameDL-PRS-ResourceWithDifferentRxTEGsSimul-r17 + ENUMERATED {n1, n2, n3, n4, n6, n8} OPTIONAL, + ... +} + +-- ASN1STOP +``` + +### NR-UE-TEG-Capability field descriptions + +#### *nr-UE-RxTEG-ID-MaxSupport* + +Indicates the maximum number of UE-RxTEGs, which is supported and reported by the UE. This field is applicable for UE assisted DL-TDOA and Multi-RTT positioning. The UE can include this field only if the UE supports *prs-ProcessingCapabilityBandList* and any of *maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer*, *maxNrOfTRP-AcrossFreqs*, *maxNrOfPosLayer*, *maxNrOfDL-PRS-ResourcesPerResourceSet* and *maxNrOfDL-PRS-ResourcesPerPositioningFrequencyLayer*. Otherwise, the UE does not include this field. + +NOTE 1: A single value is reported when both Multi-RTT and DL-TDOA are supported. + +#### *nr-UE-TxTEG-ID-MaxSupport* + +Indicates the maximum number of UE-TxTEGs, which is supported and reported by the UE. This field is applicable for Multi-RTT and UL-TDOA positioning. For UL-TDOA, the UE can include this field only if the UE supports *supportedSRS-PosResources* defined in TS 38.331 [35]. For Multi-RTT, the UE can include this field only if the UE supports *maxNrOfDL-PRS-ResourcesPerResourceSet*, *maxNrOfDL-PRS-ResourcesPerPositioningFrequencyLayer* and *supportedSRS-PosResources* defined in TS 38.331 [35]. Otherwise, the UE does not include this field. + +#### *nr-UE-RxTxTEG-ID-MaxSupport* + +Indicates the maximum number of UE-RxTxTEGs, which is supported and reported by the UE. This field is applicable for Multi-RTT positioning. The UE can include this field only if the UE supports *maxNrOfDL-PRS-ResourcesPerResourceSet*, *maxNrOfDL-PRS-ResourcesPerPositioningFrequencyLayer* and *supportedSRS-PosResources* defined in TS 38.331 [35]. Otherwise, the UE does not include this field. + +#### *measureSameDL-PRS-ResourceWithDifferentRxTEGs* + +Indicates the maximum number of different UE-RxTEGs that a UE can support to measure the same DL-PRS Resource of a TRP. This field is applicable for UE assisted DL-TDOA and Multi-RTT positioning. The UE can include this field only if the UE supports *nr-UE-RxTEG-ID-MaxSupport*. Otherwise, the UE does not include this field. + +NOTE 2: If the UE supports *nr-UE-RxTxTEG-ID-MaxSupport* and *measureSameDL-PRS-* + +*ResourceWithDifferentRxTEGs*, the enumerated value of this field also corresponds to the maximum number of different UE-RxTx TEGs for measuring the same DL PRS Resource of a TRP with the same UE Tx TEG. + +#### *measureSameDL-PRS-ResourceWithDifferentRxTEGsSimul* + +Indicates the maximum number of UE Rx TEGs for measuring the same DL-PRS Resource simultaneously. This field is applicable for UE assisted DL-TDOA and Multi-RTT positioning. The UE can include this field only if the UE supports *measureSameDL-PRS-ResourceWithDifferentRxTEGs*. Otherwise, the UE does not include this field. + +NOTE 3: If the UE supports *nr-UE-RxTxTEG-ID-MaxSupport* and *measureSameDL-PRS-* + +*ResourceWithDifferentRxTEGs* and *measureSameDL-PRS-ResourceWithDifferentRxTEGsSimul*, the enumerated value of this field also corresponds to the maximum number of different UE-RxTx TEGs for measuring the same DL PRS Resource simultaneously with the same UE Tx TEG. + +## NR-UL-SRS-Capability + +The IE *NR-UL-SRS-Capability* defines the UE uplink SRS capability. + +``` +-- ASN1START +``` + +``` + +NR-UL-SRS-Capability-r16 ::= SEQUENCE { + srs-CapabilityBandList-r16 SEQUENCE (SIZE (1..nrMaxBands-r16)) OF + SRS-CapabilityPerBand-r16, + srs-PosResourceConfigCA-BandList-r16 SEQUENCE (SIZE (1..nrMaxConfiguredBands-r16)) OF + SRS-PosResourcesPerBand-r16 OPTIONAL, + maxNumberSRS-PosPathLossEstimateAllServingCells-r16 ENUMERATED {n1, n4, n8, n16} OPTIONAL, + maxNumberSRS-PosSpatialRelationsAllServingCells-r16 ENUMERATED {n0, n1, n2, n4, n8, n16} OPTIONAL, + ... +} + +SRS-CapabilityPerBand-r16 ::= SEQUENCE { + freqBandIndicatorNR-r16 FreqBandIndicatorNR-r16, + olpc-SRS-Pos-r16 OLPC-SRS-Pos-r16 OPTIONAL, + spatialRelationsSRS-Pos-r16 SpatialRelationsSRS-Pos-r16 OPTIONAL, + ..., + [[ + posSRS-RRc-Inactive-InInitialUL-BWP-r17 PosSRS-RRc-Inactive-InInitialUL-BWP-r17 OPTIONAL, + posSRS-RRc-Inactive-OutsideInitialUL-BWP-r17 PosSRS-RRc-Inactive-OutsideInitialUL-BWP-r17 OPTIONAL, + olpc-SRS-PosRRc-Inactive-r17 OLPC-SRS-Pos-r16 OPTIONAL, + spatialRelationsSRS-PosRRc-Inactive-r17 SpatialRelationsSRS-Pos-r16 OPTIONAL + ]], + [[ + posSRS-SP-RRc-Inactive-InInitialUL-BWP-r17 PosSRS-SP-RRc-Inactive-InInitialUL-BWP-r17 OPTIONAL + ]], + [[ + posSRS-RRc-InactiveInitialUL-BWP-r18 ENUMERATED {supported} OPTIONAL, + posSRS-RRc-InactiveOutsideInitialUL-BWP-r18 ENUMERATED {supported} OPTIONAL + ]] +} + +OLPC-SRS-Pos-r16 ::= SEQUENCE { + olpc-SRS-PosBasedOnPRS-Serving-r16 ENUMERATED {supported} OPTIONAL, + olpc-SRS-PosBasedOnSSB-Neigh-r16 ENUMERATED {supported} OPTIONAL, + olpc-SRS-PosBasedOnPRS-Neigh-r16 ENUMERATED {supported} OPTIONAL, + maxNumberPathLossEstimatePerServing-r16 ENUMERATED {n1, n4, n8, n16} OPTIONAL, + ... +} + +SpatialRelationsSRS-Pos-r16 ::= SEQUENCE { + spatialRelation-SRS-PosBasedOnSSB-Serving-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnPRS-Serving-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnSRS-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 ENUMERATED {supported} OPTIONAL, + ... +} + +SRS-PosResourcesPerBand-r16 ::= SEQUENCE { + freqBandIndicatorNR-r16 FreqBandIndicatorNR-r16, + maxNumberSRS-PosResourceSetsPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n12, n16}, + maxNumberSRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumberPeriodicSRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumberAP-SRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, + maxNumberSP-SRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, + ... +} + +PosSRS-RRc-Inactive-InInitialUL-BWP-r17 ::= SEQUENCE { + maxNumOfSRSposResourceSets-r17 ENUMERATED {n1, n2, n4, n8, n12, n16} OPTIONAL, + maxNumOfPeriodicAndSemiPersistentSRSposResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, + maxNumOfPeriodicAndSemiPersistentSRSposResourcesPerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} OPTIONAL, + maxNumOfPeriodicSRSposResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, + maxNumOfPeriodicSRSposResourcesPerSlot-r17 OPTIONAL, +} + +``` + +``` + + ENUMERATED { n1, n2, n3, n4, n5, n6, n8, n10, n12, n14 } + OPTIONAL, +dummy1 ENUMERATED { n1, n2, n4, n8, n16, n32, n64 } OPTIONAL, +dummy2 ENUMERATED { n1, n2, n3, n4, n5, n6, n8, n10, n12, n14 } OPTIONAL, + ... + OPTIONAL, +} + +PosSRS-RRc-Inactive-OutsideInitialUL-BWP-r17 ::= SEQUENCE { + maxSRSpSBandwidthForEachSCS-withinCC-FR1-r17 + ENUMERATED { mhz5, mhz10, mhz15, mhz20, mhz25, mhz30, + mhz35, mhz40, mhz45, mhz50, mhz60, mhz70, + mhz80, mhz90, mhz100 } OPTIONAL, + maxSRSpSBandwidthForEachSCS-withinCC-FR2-r17 + ENUMERATED { mhz50, mhz100, mhz200, mhz400 } OPTIONAL, + maxNumOfSRSpSResourceSets-r17 ENUMERATED { n1, n2, n4, n8, n12, n16 } OPTIONAL, + maxNumOfPeriodicSRSpSResources-r17 ENUMERATED { n1, n2, n4, n8, n16, n32, n64 } OPTIONAL, + maxNumOfPeriodicSRSpSResourcesPerSlot-r17 + ENUMERATED { n1, n2, n3, n4, n5, n6, n8, n10, n12, n14 } OPTIONAL, + differentNumerologyBetweenSRSpSAndInitialBWP-r17 + ENUMERATED { supported } OPTIONAL, + srsPosWithoutRestrictionOnBWP-r17 + ENUMERATED { supported } OPTIONAL, + maxNumOfPeriodicAndSemiPersistentSRSpSResources-r17 + ENUMERATED { n1, n2, n4, n8, n16, n32, n64 } OPTIONAL, + maxNumOfPeriodicAndSemiPersistentSRSpSResourcesPerSlot-r17 + ENUMERATED { n1, n2, n3, n4, n5, n6, n8, n10, + n12, n14 } OPTIONAL, + differentCenterFreqBetweenSRSpSAndInitialBWP-r17 + ENUMERATED { supported } OPTIONAL, + maxNumOfSemiPersistentSRSpSResources-r17 + ENUMERATED { n1, n2, n4, n8, n16, n32, n64 } OPTIONAL, + maxNumOfSemiPersistentSRSpSResourcesPerSlot-r17 + ENUMERATED { n1, n2, n3, n4, n5, n6, n8, n10, + n12, n14 } OPTIONAL, + switchingTimeSRS-TX-OtherTX-r17 ENUMERATED { us100, us140, us200, us300, us500 } OPTIONAL, + ... +} + +PosSRS-SP-RRc-Inactive-InInitialUL-BWP-r17 ::= SEQUENCE { + maxNumOfSemiPersistentSRSpSResources-r17 + ENUMERATED { n1, n2, n4, n8, n16, n32, n64 } OPTIONAL, + maxNumOfSemiPersistentSRSpSResourcesPerSlot-r17 + ENUMERATED { n1, n2, n3, n4, n5, n6, n8, n10, n12, n14 } OPTIONAL, + ... +} + +-- ASN1STOP + +``` + +| | +|------------------------------------------------| +| NR-UL-SRS-Capability field descriptions | +|------------------------------------------------| + +**srs-PosResourceConfigCA-BandList** + +This field indicates the number of SRS for positioning resources supported by the target device. The target device includes this field for each band which belongs to the *srs-CapabilityBandList* for the current configured CA band combination. The capability signalling comprises the following parameters: + +- **freqBandIndicatorNR** indicates the current configured NR band of the target device. +- **maxNumberSRS-PosResourceSetsPerBWP** indicates the maximum number of SRS Resource Sets for positioning supported by the target device per BWP. Enumerated values *n1, n2, n4, n8, n12, n16* correspond to 1, 2, 4, 8, 12, 16 SRS Resource Sets for positioning, respectively. +- **maxNumberSRS-PosResourcesPerBWP** indicates the maximum number of periodic, semi-persistent, and aperiodic SRS Resources for positioning supported by the target device per BWP. Enumerated values *n1, n2, n4, n8, n16, n32, n64* correspond to 1, 2, 4, 8, 16, 32, 64 SRS Resources for positioning, respectively. +- **maxNumberPeriodicSRS-PosResourcesPerBWP** indicates the maximum number of periodic SRS Resources for positioning supported by the target device per BWP. Enumerated values *n1, n2, n4, n8, n16, n32, n64* correspond to 1, 2, 4, 8, 16, 32, 64 periodic SRS Resources for positioning, respectively. +- **maxNumberAP-SRS-PosResourcesPerBWP** indicates the maximum number of aperiodic SRS Resources for positioning supported by the target device per BWP. Enumerated values *n1, n2, n4, n8, n16, n32, n64* correspond to 1, 2, 4, 8, 16, 32, 64 aperiodic SRS Resources for positioning, respectively. +- **maxNumberSP-SRS-PosResourcesPerBWP** indicates the maximum number of semi-persistent SRS Resources for positioning supported by the target device per BWP. Enumerated values *n1, n2, n4, n8, n16, n32, n64* correspond to 1, 2, 4, 8, 16, 32, 64 semi-persistent SRS Resources for positioning, respectively. + +**maxNumberSRS-PosPathLossEstimateAllServingCells** + +Indicates the maximum number of pathloss estimates that the UE can simultaneously maintain for all the SRS resource sets for positioning across all cells in addition to the up to four pathloss estimates that the UE maintains per serving cell for the PUSCH/PUCCH/SRS transmissions. The UE shall include this field if the UE supports any of *olpc-SRS-PosBasedOnPRS-Serving, olpc-SRS-PosBasedOnSSB-Neigh* and *olpc-SRS-PosBasedOnPRS-Neigh*. Otherwise, the UE does not include this field. + +**maxNumberSRS-PosSpatialRelationsAllServingCells** + +indicates the maximum number of maintained spatial relations for all the SRS resource sets for positioning across all serving cells in addition to the spatial relations maintained spatial relations per serving cell for the PUSCH/PUCCH/SRS transmissions. It is only applied for FR2. The UE can include this field only if the UE supports any of *spatialRelation-SRS-PosBasedOnSSB-Serving, spatialRelation-SRS-PosBasedOnCSI-RS-Serving, spatialRelation-SRS-PosBasedOnPRS-Serving, spatialRelation-SRS-PosBasedOnSSB-Neigh* or *spatialRelation-SRS-PosBasedOnPRS-Neigh*. Otherwise, the UE does not include this field. + +**olpc-SRS-Pos** + +Indicates whether the UE supports open-loop power control for SRS for positioning. The capability signalling comprises the following parameters: + +- **olpc-SRS-PosBasedOnPRS-Serving** indicates whether the UE supports OLPC for SRS for positioning based on PRS from the serving cell in the same band. The UE can include this field only if the UE supports *NR-DL-PRS-ProcessingCapability* and *srs-PosResources* TS38.331 [35] Otherwise, the UE does not include this field. +- **olpc-SRS-PosBasedOnSSB-Neigh** indicates whether the UE supports OLPC for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE can include this field only if the UE supports *srs-PosResources* TS 38.331 [35]. Otherwise, the UE does not include this field. +- **olpc-SRS-PosBasedOnPRS-Neigh** indicates whether the UE supports OLPC for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE can include this field only if the UE supports *olpc-SRS-PosBasedOnPRS-Serving*. Otherwise, the UE does not include this field. + +Note: A PRS from a PRS-only TP is treated as PRS from a non-serving cell. + +- **maxNumberPathLossEstimatePerServing** indicates the maximum number of pathloss estimates that the UE can simultaneously maintain for all the SRS resource sets for positioning per serving cell in addition to the up to four pathloss estimates that the UE maintains per serving cell for the PUSCH/PUCCH/SRS transmissions. The UE shall include this field if the UE supports any of *olpc-SRS-PosBasedOnPRS-Serving, olpc-SRS-PosBasedOnSSB-Neigh* and *olpc-SRS-PosBasedOnPRS-Neigh*. Otherwise, the UE does not include this field. + +***spatialRelationsSRS-Pos*** + +Indicates whether the UE supports spatial relations for SRS for positioning. It is only applicable for FR2. The capability signalling comprises the following parameters: + +- ***spatialRelation-SRS-PosBasedOnSSB-Serving*** indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the serving cell in the same band. The UE can include this field only if the UE supports *srs-PosResources* TS 38.331 [35]. Otherwise, the UE does not include this field. +- ***spatialRelation-SRS-PosBasedOnCSI-RS-Serving*** indicates whether the UE supports spatial relation for SRS for positioning based on CSI-RS from the serving cell in the same band. The UE can include this field only if the UE supports *spatialRelation-SRS-PosBasedOnSSB-Serving*. Otherwise, the UE does not include this field. +- ***spatialRelation-SRS-PosBasedOnPRS-Serving*** indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the serving cell in the same band. The UE can include this field only if the UE supports any of DL-PRS Resources for DL-AoD, DL-PRS Resources for DL-TDOA or DL-PRS Resources for Multi-RTT, or *srs-PosResources* TS 38.331 [35]. Otherwise, the UE does not include this field. +- ***spatialRelation-SRS-PosBasedOnSRS*** indicates whether the UE supports spatial relation for SRS for positioning based on SRS in the same band. The UE can include this field only if the UE supports *srs-PosResources* TS 38.331 [35]. Otherwise, the UE does not include this field. +- ***spatialRelation-SRS-PosBasedOnSSB-Neigh*** indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE can include this field only if the UE supports *spatialRelation-SRS-PosBasedOnSSB-Serving*. Otherwise, the UE does not include this field. +- ***spatialRelation-SRS-PosBasedOnPRS-Neigh*** indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE can include this field only if the UE supports *spatialRelation-SRS-PosBasedOnPRS-Serving*. Otherwise, the UE does not include this field. + +Note: A PRS from a PRS-only TP is treated as PRS from a non-serving cell. + +***posSRS-RRC-Inactive-InInitialUL-BWP*** + +Indicates whether the UE supports positioning SRS transmission in RRC\_INACTIVE state for initial UL BWP. The capability signalling comprises the following parameters: + +- ***maxNumOfSRSPosResourceSets*** indicates the maximum number of SRS Resource Sets for positioning supported by the UE. +- ***maxNumOfPeriodicAndSemiPersistentSRSPosResources*** indicates the maximum number of periodic and semi-persistent SRS Resources for positioning supported by the UE. +- ***maxNumOfPeriodicAndSemiPersistentSRSPosResourcesPerSlot*** indicates the maximum number of periodic and semi-persistent SRS Resources for positioning per slot supported by the UE. +- ***maxNumOfPeriodicSRSPosResources*** indicates the maximum number of periodic SRS Resources for positioning supported by the UE. +- ***maxNumOfPeriodicSRSPosResourcesPerSlot*** indicates the maximum number of periodic SRS Resources for positioning per slot supported by the UE. +- ***dummy1***, ***dummy2*** are not used in the specification. If received they shall be ignored by the receiver. + +**posSRS-RRC-Inactive-OutsideInitialUL-BWP** + +Indicates whether the UE supports positioning SRS transmission in RRC\_INACTIVE state outside initial UL BWP. The UE can include this field only if the UE supports *posSRS-RRC-Inactive-InInitialUL-BWP*. Otherwise, the UE does not include this field. The capability signalling comprises the following parameters: + +- **maxSRSPosBandwidthForEachSCS-withinCC-FR1** indicates the maximum SRS bandwidth in MHz supported for each SCS that UE supports within a single CC for FR1. +- **maxSRSPosBandwidthForEachSCS-withinCC-FR2** indicates the maximum SRS bandwidth in MHz supported for each SCS that UE supports within a single CC for FR2. +- **maxNumOfSRSPosResourceSets** indicates the maximum number of SRS Resource Sets for positioning supported by the UE. +- **maxNumOfPeriodicSRSPosResources** indicates the maximum number of periodic SRS Resources for positioning supported by the UE. +- **maxNumOfPeriodicSRSPosResourcesPerSlot** indicates the maximum number of periodic SRS Resources for positioning per slot supported by the UE. +- **differentNumerologyBetweenSRSPosAndInitialBWP** indicates whether different numerology between the SRS and the initial UL BWP is supported by the UE. If the field is absent, the UE only supports same numerology between the SRS and the initial UL BWP. +- **srsPosWithoutRestrictionOnBWP** indicates whether SRS operation without restriction on the BW is supported by the UE; BW of the SRS may not include BW of the CORESET#0 and SSB. If the field is absent, the UE supports only SRS BW that includes the BW of the CORESET #0 and SSB. +- **maxNumOfPeriodicAndSemiPersistentSRSPosResources** indicates the maximum number of periodic and semi-persistent SRS Resources for positioning supported by the UE. +- **maxNumOfPeriodicAndSemiPersistentSRSPosResourcesPerSlot** indicates the maximum number of periodic and semi-persistent SRS Resources for positioning per slot supported by the UE. +- **differentCenterFreqBetweenSRSPosAndInitialBWP** indicates whether different center frequency between the SRS for positioning and the initial UL BWP is supported by the UE. If the field is absent, the UE only supports same center frequency between the SRS for positioning and initial UL BWP. +- **maxNumOfSemiPersistentSRSPosResources** indicates the maximum number of semi-persistent SRS Resources for positioning supported by the UE. The UE can include this field only if the UE supports *posSRS-RRC-Inactive-InInitialUL-BWP*. Otherwise, the UE does not include this field. +- **maxNumOfSemiPersistentSRSPosResourcesPerSlot** indicates the maximum number of semi-persistent SRS Resources for positioning per slot supported by the UE. The UE can include this field only if the UE supports *posSRS-RRC-Inactive-InInitialUL-BWP*. Otherwise, the UE does not include this field. +- **switchingTimeSRS-TX-OtherTX** indicates the switching time between SRS Tx and other Tx in initial UL BWP or Rx in initial DL BWP. + +**olpc-SRS-PosRRC-Inactive** + +Indicates whether the UE supports open-loop power control for SRS for positioning in RRC\_INACTIVE state. The UE can include this field only if the UE supports *posSRS-RRC-Inactive-InInitialUL-BWP*. Otherwise, the UE does not include this field. + +**spatialRelationsSRS-PosRRC-Inactive** + +Indicates whether the UE supports spatial relations for SRS for positioning in RRC\_INACTIVE state on FR2. The UE can include this field only if the UE supports *posSRS-RRC-Inactive-InInitialUL-BWP*. Otherwise, the UE does not include this field. + +**posSRS-SP-RRC-Inactive-InInitialUL-BWP** + +Indicates whether the UE supports positioning SRS transmission in RRC\_INACTIVE state for initial UL BWP with semi-persistent SRS. The UE can include this field only if the UE supports *posSRS-RRC-Inactive-InInitialUL-BWP*. Otherwise, the UE does not include this field. The capability signalling comprises the following parameters: + +- **maxNumOfSemiPersistentSRSPosResources** indicates the maximum number of semi-persistent SRS Resources for positioning supported by the UE. +- **maxNumOfSemiPersistentSRSPosResourcesPerSlot** indicates the maximum number of semi-persistent SRS Resources for positioning per slot supported by the UE. + +**posSRS-RRC-InactiveInitialUL-BWP** + +Indicates whether UE supports of preconfigured SRS with validity area in RRC\_INACTIVE for initial BWP. The UE can include this field only if the UE supports of SRS for positioning configuration in multiple cells for UEs in RRC\_INACTIVE state for initial UL BWP. Otherwise, the UE does not include this field. + +**posSRS-RRC-InactiveOutsideInitialUL-BWP** + +Indicates whether UE supports of preconfigured SRS with validity area in RRC\_INACTIVE outside initial BWP. The UE can include this field only if the UE supports of SRS for positioning configuration in multiple cells for UEs in RRC\_INACTIVE state configured outside initial UL BWP. Otherwise, the UE does not include this field. + +## NR-PhaseQuality + +The IE *NR-PhaseQuality* defines the quality of the RSCP/RSCPD measurement. + +``` +-- ASN1START +``` + +``` +NR-PhaseQuality-r18 ::= SEQUENCE { +``` + +``` + + phaseQualityValue-r18 INTEGER (0..179), + phaseQualityResolution-r18 ENUMERATED {mdot1, m1,...}, + ... +} + +-- ASN1STOP + +``` + +#### NR-PhaseQuality field descriptions + +##### **phaseQualityValue** + +This field provides an estimate of uncertainty of the phase value for which the IE *NR-PhaseQuality* is provided in units of degrees. + +##### **phaseQualityResolution** + +This field provides the resolution used in the *phaseQualityValue* field. Enumerated values *mdot1* and *m1* correspond to 0.1 and 1 degrees respectively. + +### ReferencePoint + +The IE *ReferencePoint* provides a well-defined location relative to which other locations may be defined. + +``` + +-- ASN1START + +ReferencePoint-r16 ::= SEQUENCE { + referencePointGeographicLocation-r16 CHOICE { + location3D-r16 EllipsoidPointWithAltitudeAndUncertaintyEllipsoid, + ha-location3D-r16 HighAccuracyEllipsoidPointWithAltitudeAndUncertaintyEllipsoid-r15, + ..., + localOrigin-v1800 CoordinateID-r18 + }, + ... +} + +-- ASN1STOP + +``` + +#### ReferencePoint field descriptions + +##### **referencePointGeographicLocation** + +This field provides the geodetic or local location of the reference point. + +##### **localOrigin** + +This field provides an identifier for the reference point that defines the origin of a local Cartesian coordinate system [15]. + +### RelativeCartesianLocation + +The IE *RelativeCartesianLocation* provides a Cartesian location relative to some known reference location. + +``` + +-- ASN1START + +RelativeCartesianLocation-r18 ::= SEQUENCE { + cartesianCoordinatesUnits-r18 ENUMERATED { mm, cm, dm, m, ...}, + x-value-r18 X-Value-r18, + y-value-r18 Y-Value-r18, + z-value-r18 Z-Value-r18, + locationUNC-r18 LocationUncertainty-r16 OPTIONAL, -- Need OP + ... +} + +X-Value-r18 ::= SEQUENCE { + delta-x-r18 INTEGER (-1024..1023), + coarse-delta-x-r18 INTEGER (0..4095) OPTIONAL, -- Need OP + ... +} + +Y-Value-r18 ::= SEQUENCE { + delta-y-r18 INTEGER (-1024..1023), + coarse-delta-y-r18 INTEGER (0..4095) OPTIONAL, -- Need OP + ... +} + +Z-Value-r18 ::= SEQUENCE { + +``` + +``` + +delta-z-r18 INTEGER (-1024..1023), +coarse-delta-z-r18 INTEGER (0..4095) OPTIONAL, -- Need OP +... +} + +-- ASN1STOP + +``` + +### RelativeCartesianLocation field descriptions + +#### cartesianCoordinatesUnits + +This field provides the units and scale factor for the *x-value*, *y-value* and *z-value* fields. Enumerated values *mm*, *cm*, *dm*, and *m*, correspond to $10^{-3}$ metre, $10^{-2}$ metre, $10^{-1}$ metre and 1 metres, respectively. + +#### x-value + +This field specifies the x-value of the desired location in a Cartesian coordinate system and comprises the following sub-fields: + +- **delta-x** specifies the delta value on the x-axis of a Cartesian coordinate system in the unit provided in *cartesianCoordinatesUnits* field. +- **coarse-delta-x** specifies the delta value on the x-axis of a Cartesian coordinate system in 1024 times the size of the unit provided in *cartesianCoordinatesUnits* field and with the same sign as in the *delta-x* field. If this field is absent, the value for *coarse-delta-x* is zero. + +I.e., the full *x-value* is given by: + +$$(\text{delta-x} \times \text{cartesianCoordinatesUnits}) \pm (\text{coarse-delta-x} \times 1024 \times \text{cartesianCoordinatesUnits}) \text{ [m]}.$$ + +#### y-value + +This field specifies the y-value of the desired location in a Cartesian coordinate system and comprises the following sub-fields: + +- **delta-y** specifies the delta value on the y-axis of a Cartesian coordinate system in the unit provided in *cartesianCoordinatesUnits* field. +- **coarse-delta-y** specifies the delta value on the y-axis of a Cartesian coordinate system in 1024 times the size of the unit provided in *cartesianCoordinatesUnits* field and with the same sign as in the *delta-y* field. If this field is absent, the value for *coarse-delta-y* is zero. + +I.e., the full *y-value* is given by: + +$$(\text{delta-y} \times \text{cartesianCoordinatesUnits}) \pm (\text{coarse-delta-y} \times 1024 \times \text{cartesianCoordinatesUnits}) \text{ [m]}.$$ + +#### z-value + +This field specifies the z-value of the desired location in a Cartesian coordinate system and comprises the following sub-fields: + +- **delta-z** specifies the delta value on the z-axis of a Cartesian coordinate system in the unit provided in *cartesianCoordinatesUnits* field. +- **coarse-delta-z** specifies the delta value on the z-axis of a Cartesian coordinate system in 1024 times the size of the unit provided in *cartesianCoordinatesUnits* field and with the same sign as in the *delta-z* field. If this field is absent, the value for *coarse-delta-z* is zero. + +I.e., the full *z-value* is given by: + +$$(\text{delta-z} \times \text{cartesianCoordinatesUnits}) \pm (\text{coarse-delta-z} \times 1024 \times \text{cartesianCoordinatesUnits}) \text{ [m]}.$$ + +#### locationUNC + +This field specifies the uncertainty of the location coordinates (see IE *RelativeLocation*). + +If this field is absent, the uncertainty is the same as for the associated reference point location. + +## RelativeLocation + +The IE *RelativeLocation* provides a location relative to some known reference location. + +``` + +-- ASN1START + +RelativeLocation-r16 ::= SEQUENCE { + milli-arc-second-units-r16 ENUMERATED { mas0-03, mas0-3, mas3, mas30, ... }, + height-units-r16 ENUMERATED { mm, cm, m, ... }, + delta-latitude-r16 Delta-Latitude-r16, + delta-longitude-r16 Delta-Longitude-r16, + delta-height-r16 Delta-Height-r16, + locationUNC-r16 LocationUncertainty-r16 OPTIONAL, -- Need OP + ... +} + +Delta-Latitude-r16 ::= SEQUENCE { + delta-Latitude-r16 INTEGER (-1024..1023), + coarse-delta-Latitude-r16 INTEGER (0..4095) OPTIONAL, -- Need OP + ... +} + +Delta-Longitude-r16 ::= SEQUENCE { + +``` + +``` + + delta-Longitude-r16 INTEGER (-1024..1023), + coarse-delta-Longitude-r16 INTEGER (0..4095) OPTIONAL, -- Need OP + ... +} + +Delta-Height-r16 ::= SEQUENCE { + delta-Height-r16 INTEGER (-1024..1023), + coarse-delta-Height-r16 INTEGER (0..4095) OPTIONAL, -- Need OP + ... +} + +LocationUncertainty-r16 ::= SEQUENCE { + horizontalUncertainty-r16 INTEGER (0..255), + horizontalConfidence-r16 INTEGER (0..100), + verticalUncertainty-r16 INTEGER (0..255), + verticalConfidence-r16 INTEGER (0..100) +} + +-- ASN1STOP + +``` + +### **RelativeLocation field descriptions** + +#### ***milli-arc-second-units*** + +This field provides the units and scale factor for the *delta-latitude* and *delta-longitude* fields. Enumerated values *mas0-03*, *mas0-3*, *mas3*, and *mas30*, correspond to 0.03, 0.3, 3, and 30 milliarcseconds, respectively. + +#### ***height-units*** + +This field provides the units and scale factor for the *delta-height* field. Enumerated values *mm*, *cm*, and *m* correspond to $10^{-3}$ metre, $10^{-2}$ metre, and 1 metres, respectively. + +#### ***delta-latitude*** + +This field specifies the delta value in latitude of the desired location, defined as "desired location" minus "reference point location" and comprises the following sub-fields: + +- ***delta-Latitude*** specifies the delta value in latitude in the unit provided in *milli-arc-second-units* field. +- ***coarse-delta-Latitude*** specifies the delta value in latitude in 1024 times the size of the unit provided in *milli-arc-second-units* field and with the same sign as in the *delta-Latitude* field. If this field is absent, the value for *coarse-delta-Latitude* is zero. + +I.e., the full *delta-latitude* is given by: + +$$(\text{delta-Latitude} \times \text{milli-arc-second-units}) \pm (\text{coarse-delta-Latitude} \times 1024 \times \text{milli-arc-second-units}) \text{ [milli-arc-seconds]}$$ + +#### ***delta-longitude*** + +This field specifies the delta value in longitude of the desired location, defined as "desired location" minus "reference point location" and comprises the following sub-fields: + +- ***delta-Longitude*** specifies the delta value in longitude in the unit provided in *milli-arc-second-units* field. +- ***coarse-delta-Longitude*** specifies the delta value in longitude in 1024 times the size of the unit provided in *milli-arc-second-units* field and with the same sign as in the *delta-Longitude* field. If this field is absent, the value for *coarse-delta-Longitude* is zero. + +I.e., the full *delta-longitude* is given by: + +$$(\text{delta-Longitude} \times \text{milli-arc-second-units}) \pm (\text{coarse-delta-Longitude} \times 1024 \times \text{milli-arc-second-units}) \text{ [milli-arc-seconds]}$$ + +#### ***delta-height*** + +This field specifies the delta value in ellipsoidal height of the desired location, defined as "desired location" minus "reference point location" and comprises the following sub-fields: + +- ***delta-Height*** specifies the delta value in ellipsoidal height in the unit provided in *height-units* field. +- ***coarse-delta-Height*** specifies the delta value in ellipsoidal height in 1024 times the size of the unit provided in *height-units* field and with the same sign as in the *delta-Height* field. If this field is absent, the value for *coarse-delta-Height* is zero. + +I.e., the full *delta-height* is given by: + +$$(\text{delta-Height} \times \text{height-units}) \pm (\text{coarse-delta-Height} \times 1024 \times \text{height-units}) \text{ [metres]}$$ + +#### ***locationUNC*** + +This field specifies the uncertainty of the location coordinates and comprises the following sub-fields: + +- ***horizontalUncertainty*** indicates the horizontal uncertainty of the ARP latitude/longitude. The '*horizontalUncertainty*' corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and '*horizontalConfidence*' corresponds to confidence as defined in TS 23.032 [15]. +- ***verticalUncertainty*** indicates the vertical uncertainty of the ARP altitude. The '*verticalUncertainty*' corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and '*verticalConfidence*' corresponds to confidence as defined in TS 23.032 [15]. + +If this field is absent, the uncertainty is the same as for the associated reference point location. + +### – ***TEG-TimingErrorMargin*** + +The IE *TEG-TimingErrorMargin* defines the timing error margin values of the UE Rx TEGs, UE Tx TEGs, or TRP Tx TEGs. Enumerated value '*tc0*' corresponds to 0 Tc, '*tc2*' corresponds to 2 Tc and so on, where Tc is defined in TS 38.211 [41] clause 4.1. + +``` +-- ASN1START +TEG-TimingErrorMargin-r17 ::= ENUMERATED { tc0, tc2, tc4, tc6, tc8, tc12, tc16, tc20, tc24, + tc32, tc40, tc48, tc56, tc64, tc72, tc80 } +-- ASN1STOP +``` + +### – ***RxTxTEG-TimingErrorMargin*** + +The IE *RxTxTEG-TimingErrorMargin* defines the timing error margin values of the UE RxTx TEGs. Enumerated value '*tc0-5*' corresponds to 0.5 Tc, '*tc1*' corresponds to 1 Tc and so on, where Tc is defined in TS 38.211 [41] clause 4.1. + +``` +-- ASN1START +RxTxTEG-TimingErrorMargin-r17 ::= ENUMERATED { tc0-5, tc1, tc2, tc4, tc8, tc12, tc16, tc20, + tc24, tc32, tc40, tc48, tc64, tc80, tc96, tc128 } +-- ASN1STOP +``` + +## 6.5 Positioning Method IEs + +### 6.5.1 OTDOA Positioning + +This clause defines the information elements for downlink OTDOA positioning, which includes TBS positioning based on PRS signals (TS 36.305 [2]). + +#### 6.5.1.1 OTDOA Assistance Data + +##### – ***OTDOA-ProvideAssistanceData*** + +The IE *OTDOA-ProvideAssistanceData* is used by the location server to provide assistance data to enable UE-assisted downlink OTDOA. It may also be used to provide OTDOA positioning specific error reason. + +Throughout clause 6.5.1, "assistance data reference cell" refers to the cell defined by the IE *OTDOA-ReferenceCellInfo* and "NB-IoT assistance data reference cell" refers to the cell defined by the IE *OTDOA-ReferenceCellInfoNB* (see clause 6.5.1.2). "RSTD reference cell" applies only in clause 6.5.1.5. + +If both IEs, *OTDOA-ReferenceCellInfo* and *OTDOA-ReferenceCellInfoNB* are included in *OTDOA-ProvideAssistanceData*, the assistance data reference cell and NB-IoT assistance data reference cell correspond to the same cell, and the target device may assume that PRS and NPRS antenna ports are quasi co-located, as defined in TS 36.211 [16]. + +Throughout clause 6.5.1, the term "cell" refers to "transmission point (TP)", unless distinguished in the field description. + +NOTE 1: The location server should include at least one cell for which the SFN can be obtained by the target device, e.g. the serving cell, in the assistance data, either as the assistance data reference cell or in the neighbour cell list. Otherwise the target device will be unable to perform the OTDOA measurement and the positioning operation will fail. + +NOTE 2: Due to support of cells containing multiple TPs and PRS-only TPs not associated with cells, the term "cell" as used in clause 6.5.1 may not always correspond to a cell for the E-UTRAN. + +NOTE 3: For NB-IoT access, due to support of NPRS on multiple carriers, the term "cell" as used in clause 6.5.1 refers to the anchor carrier, unless otherwise stated. + +``` + +-- ASN1START + +OTDOA-ProvideAssistanceData ::= SEQUENCE { + otdoa-ReferenceCellInfo OTDOA-ReferenceCellInfo OPTIONAL, -- Need ON + otdoa-NeighbourCellInfo OTDOA-NeighbourCellInfoList OPTIONAL, -- Need ON + otdoa-Error OTDOA-Error OPTIONAL, -- Need ON + ..., + [[ + otdoa-ReferenceCellInfoNB-r14 OTDOA-ReferenceCellInfoNB-r14 OPTIONAL, -- Need ON + otdoa-NeighbourCellInfoNB-r14 OTDOA-NeighbourCellInfoListNB-r14 OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP + +``` + +### 6.5.1.2 OTDOA Assistance Data Elements + +#### – *OTDOA-ReferenceCellInfo* + +The IE *OTDOA-ReferenceCellInfo* is used by the location server to provide assistance data reference cell information for OTDOA assistance data. The slot number offsets and expected RSTDs in *OTDOA-NeighbourCellInfoList* are provided relative to the cell defined by this IE. If *earfcnRef* of this assistance data reference cell is different from that of the serving cell, the LPP layer shall inform lower layers to start performing inter-frequency RSTD measurements with this cell and provide to lower layers the information about this assistance data reference cell, e.g. EARFCN and PRS positioning occasion information. + +NOTE: The location server should always include the PRS configuration of the assistance data reference and neighbour cells. Otherwise the UE may not meet the accuracy requirements as defined in TS 36.133 [18]. + +``` + +-- ASN1START + +OTDOA-ReferenceCellInfo ::= SEQUENCE { + physCellId INTEGER (0..503), + cellGlobalId ECGI OPTIONAL, -- Need ON + earfcnRef ARFCN-ValueEUTRA OPTIONAL, -- Cond NotSameAsServ0 + antennaPortConfig ENUMERATED {ports1-or-2, ports4, ... } + OPTIONAL, -- Cond NotSameAsServ1 + cpLength ENUMERATED { normal, extended, ... }, + prsInfo PRS-Info OPTIONAL, -- Cond PRS + ..., + [[ earfcnRef-v9a0 ARFCN-ValueEUTRA-v9a0 OPTIONAL -- Cond NotSameAsServ2 + ]], + [[ tpId-r14 INTEGER (0..4095) OPTIONAL, -- Need ON + cpLengthCRS-r14 ENUMERATED { normal, extended, ... } + OPTIONAL, -- Cond CRS + sameMBSFNconfigRef-r14 BOOLEAN OPTIONAL, -- Need ON + dlBandwidth-r14 ENUMERATED {n6, n15, n25, n50, n75, n100} + OPTIONAL, -- Cond NotSameAsServ3 + addPRSconfigRef-r14 SEQUENCE (SIZE (1..maxAddPRSconfig-r14)) OF PRS-Info + OPTIONAL -- Need ON + ]], + [[ nr-LTE-SFN-Offset-r15 INTEGER (0..1023) OPTIONAL -- Cond NR + ]], + [[ tdd-config-v1520 TDD-Config-v1520 OPTIONAL, -- Need ON + nr-LTE-fineTiming-Offset-r15 INTEGER (0..19) OPTIONAL -- Cond FineOffset + ]] +} + +maxAddPRSconfig-r14 INTEGER ::= 2 + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NotSameAsServ0 | This field is absent if earfcnRef-v9a0 is present. Otherwise, the field is mandatory present if the EARFCN of the OTDOA assistance data reference cell is not the same as the EARFCN of the target devices' current primary cell. | +| NotSameAsServ1 | The field is mandatory present if the antenna port configuration of the OTDOA assistance data reference cell is not the same as the antenna port configuration of the target devices' current primary cell. | +| NotSameAsServ2 | The field is absent if earfcnRef is present. Otherwise, the field is mandatory present if the EARFCN of the OTDOA assistance data reference cell is not the same as the EARFCN of the target devices' current primary cell. | +| PRS | The field is mandatory present if positioning reference signals are available in the assistance data reference cell (TS 36.211 [16]); otherwise it is not present. | +| CRS | The field is optionally present, need ON, if prsInfo is present. Otherwise it is not present. | +| NotSameAsServ3 | The field is mandatory present if the downlink bandwidth configuration of the assistance data reference cell is not the same as the downlink bandwidth configuration of the target devices' current primary cell and if PRS frequency hopping is used in the assistance data reference cell (TS 36.211 [16]); otherwise it is not present. | +| NR | The field is optionally present, need ON, if the target device is served by an NR cell; otherwise it is not present. | +| FineOffset | The field is optionally present, need ON, if nr-LTE-SFN-Offset is present. Otherwise it is not present. | + +| OTDOA-ReferenceCellInfo field descriptions | | +|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| physCellId | This field specifies the physical cell identity of the assistance data reference cell, as defined in TS 36.331 [12]. | +| cellGlobalId | This field specifies the ECGI, the globally unique identity of a cell in E-UTRA, of the assistance data reference cell, as defined in TS 36.331 [12]. The server should include this field if it considers that it is needed to resolve ambiguity in the cell indicated by physCellId . | +| earfcnRef | This field specifies the EARFCN of the assistance data reference cell. | +| antennaPortConfig | This field specifies whether 1 (or 2) antenna port(s) or 4 antenna ports for cell specific reference signals (CRS) are used in the assistance data reference cell. | +| cpLength | This field specifies the cyclic prefix length of the assistance data reference cell PRS if the prsInfo field is present, otherwise this field specifies the cyclic prefix length of the assistance data reference cell CRS. | +| prsInfo | This field specifies the first PRS configuration of the assistance data reference cell. | + +| OTDOA-ReferenceCellInfo field descriptions | | +|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tpId | This field specifies an identity of the transmission point. This field together with the physCellId and/or prsID may be used to identify the transmission point in the case the same physical cell ID is shared by multiple transmission points. | +| cpLengthCRS | This field specifies the cyclic prefix length of the assistance data reference cell CRS. If this field is present, the target device may assume the CRS and PRS antenna ports of the assistance data reference cell are quasi co-located (as defined in TS 36.211 [16]). | +| sameMBSFNconfigRef | This field indicates whether the MBSFN subframe configuration of the assistance data reference cell is the same as the current primary cell of the target device. TRUE means the same, and FALSE means not the same. | +| dlBandwidth | This field specifies the downlink bandwidth configuration of the assistance data reference cell, $N_{RB}$ in downlink, see TS 36.101 [21, table 5.6-1]. Enumerated value n6 corresponds to 6 resource blocks, n15 to 15 resource blocks and so on. | +| addPRSconfigRef | This field specifies the additional (second and possibly third) PRS configuration(s) of the assistance data reference cell. | +| nr-LTE-SFN-Offset | This field specifies the SFN offset between the serving NR cell and the LTE assistance data reference cell. The offset corresponds to the number of full radio frames counted from the beginning of a radio frame #0 of the NR serving cell to the beginning of the closest subsequent radio frame #0 of the assistance data reference cell. | +| tdd-config | This field specifies the TDD specific physical channel configuration of the assistance data reference cell. The field should be present if the assistance data reference cell is a TDD cell and if the TDD UL/DL configuration of the assistance data reference cell is not the same as the target devices' current primary cell or if the target devices' current primary cell is a FDD cell. | +| nr-LTE-fineTiming-Offset | This field specifies the frame boundary offset between the NR serving cell and the LTE assistance data reference cell in units of 0.5 ms. The offset is counted from the beginning of a subframe #0 of the NR serving cell to the beginning of the closest subsequent subframe #0 of the LTE assistance data reference cell, rounded down to multiples of 0.5 ms. Value 0 corresponds to 0 ms, value 1 corresponds to 0.5 ms, 2 to 1 ms and so on. | + +## PRS-Info + +The IE *PRS-Info* provides the information related to the configuration of PRS in a cell. + +``` +-- ASN1START + +PRS-Info ::= SEQUENCE { + prs-Bandwidth ENUMERATED { n6, n15, n25, n50, n75, n100, ... }, + prs-ConfigurationIndex INTEGER (0..4095), + numDL-Frames ENUMERATED {sf-1, sf-2, sf-4, sf-6, ..., sf-add-v1420}, + ..., + prs-MutingInfo-r9 CHOICE { + po2-r9 BIT STRING (SIZE(2)), + po4-r9 BIT STRING (SIZE(4)), + po8-r9 BIT STRING (SIZE(8)), + po16-r9 BIT STRING (SIZE(16)), + ..., + po32-v1420 BIT STRING (SIZE(32)), + po64-v1420 BIT STRING (SIZE(64)), + po128-v1420 BIT STRING (SIZE(128)), + po256-v1420 BIT STRING (SIZE(256)), + po512-v1420 BIT STRING (SIZE(512)), + po1024-v1420 BIT STRING (SIZE(1024)) + } OPTIONAL, -- Need OP + [[ prsID-r14 INTEGER (0..4095) OPTIONAL, -- Need ON + add-numDL-Frames-r14 INTEGER (1..160) OPTIONAL, -- Cond sf-add + prsOccGroupLen-r14 ENUMERATED {g2, g4, g8, g16, g32, g64, g128,... } + OPTIONAL, -- Cond Occ-Grp + prsHoppingInfo-r14 CHOICE { + nb2-r14 INTEGER (0.. maxAvailNarrowBands-Minus1-r14), + nb4-r14 SEQUENCE (SIZE (3)) + OF INTEGER (0.. maxAvailNarrowBands-Minus1-r14) + } OPTIONAL -- Cond PRS-FH + ]] +} + +maxAvailNarrowBands-Minus1-r14 INTEGER ::= 15 -- Maximum number of narrowbands minus 1 + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------| +| sf-add | The field is mandatory present if the numDL-Frames field has the value ' sf-add '; otherwise it is not present. | +| Occ-Grp | The field is mandatory present if a PRS occasion group is configured; otherwise it is not present. | +| PRS-FH | The field is mandatory present if frequency hopping is used for PRS; otherwise it is not present. | + +| PRS-Info field descriptions | | +|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| prs-Bandwidth | This field specifies the bandwidth that is used to configure the positioning reference signals on. Enumerated values are specified in number of resource blocks (n6 corresponds to 6 resource blocks, n15 to 15 resource blocks and so on) and define 1.4, 3, 5, 10, 15 and 20 MHz bandwidth. | +| prs-ConfigurationIndex | This field specifies the positioning reference signals configuration index $I_{PRS}$ as defined in TS 36.211 [16]. | +| numDL-Frames | This field specifies the number of consecutive downlink subframes $N_{PRS}$ with positioning reference signals, as defined in TS 36.211 [16]. Enumerated values define 1, 2, 4, or 6 consecutive downlink subframes. The value sf-add indicates that $N_{PRS}$ is provided in the field add-numDL-Frames . | +| prs-MutingInfo |

This field specifies the PRS muting configuration of the cell. The PRS muting configuration is defined by a periodic PRS muting sequence with periodicity T_{REP} where T_{REP}, counted in the number of PRS occasion groups (TS 36.133 [18]), can be 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024 which is also the length of the selected bit string that represents this PRS muting sequence. If a bit in the PRS muting sequence is set to "0", then the PRS is muted in all the PRS occasions in the corresponding PRS occasion group. A PRS occasion group comprises one or more PRS occasions as indicated by prsOccGroupLen. Each PRS occasion comprises N_{PRS} downlink positioning subframes as defined in TS 36.211 [16]. The first bit of the PRS muting sequence corresponds to the first PRS occasion group that starts after the beginning of the assistance data reference cell SFN=0. The sequence is valid for all subframes after the target device has received the prs-MutingInfo. If this field is not present the target device may assume that the PRS muting is not in use for the cell.

When the SFN of the assistance data reference cell is not known to the UE and prs-MutingInfo is provided for a cell in the OTDOA-NeighbourCellInfoList IE, the UE may assume no PRS is transmitted by that cell.

When the UE receives a T_{REP}-bit muting pattern together with a PRS periodicity T_{PRS} for the same cell which exceeds 10240 subframes (i.e., T_{REP} \times T_{PRS} > 10240 subframes), the UE shall assume an n-bit muting pattern based on the first n-bits, where n = 10240/T_{PRS}.

| +| prsID | This field specifies the PRS-ID as defined in TS 36.211 [16]. | +| add-numDL-Frames | This field specifies the number of consecutive downlink subframes $N_{PRS}$ with positioning reference signals, as defined in TS 36.211 [16]. Integer values define 1, 2, 3, ..., 160 consecutive downlink subframes. | +| prsOccGroupLen | This field specifies the PRS occasion group length, defined as the number of consecutive PRS occasions comprising a PRS occasion group. Each PRS occasion of the PRS occasion group consists of numDL-Frames or add-numDL-Frames consecutive downlink subframes with positioning reference signals. Enumerated values define 2, 4, 8, 16, 32, 64 or 128 consecutive PRS occasions. If omitted, the PRS occasion group length is 1. The product of the PRS periodicity $T_{PRS}$ from the prs-ConfigurationIndex and the PRS occasion group length cannot exceed 1280. | +| prsHoppingInfo | This field specifies the PRS frequency hopping configuration (TS 36.211 [16]). The choice nb2 indicates hopping between 2 narrowbands; the choice nb4 indicates hopping between 4 narrowbands. The first PRS positioning occasion of the first PRS occasion group that starts after the beginning of SFN=0 of the assistance data reference cell is located at the centre of the system bandwidth. The frequency band of each subsequent PRS occasion is indicated by nb2 or nb4 , respectively, which defines the narrowband index as specified in TS 36.211 [16]. If this field is absent, no PRS frequency hopping is used. | + +## – TDD-Config + +The IE *TDD-Config* is used to specify the TDD specific physical channel configuration. + +``` +-- ASN1START +TDD-Config-v1520 ::= SEQUENCE { + subframeAssignment-v1520 ENUMERATED { sa0, sa1, sa2, sa3, sa4, sa5, sa6 }, +``` + +``` + + ... + } + + -- ASN1STOP + +``` + +#### TDD-Config field descriptions + +##### subframeAssignment + +This field specifies the TDD UL/DL subframe configuration where *sa0* points to Configuration 0, *sa1* to Configuration 1 etc. as specified in TS 36.211 [16], table 4.2-2. The target device assumes the same value for all assistance data cells residing on same frequency band. + +### OTDOA-NeighbourCellInfoList + +The IE *OTDOA-NeighbourCellInfoList* is used by the location server to provide neighbour cell information for OTDOA assistance data. If the target device is not capable of supporting additional neighbour cells (as indicated by the absence of the IE *additionalNeighbourCellInfoList* in *OTDOA-ProvideCapabilities*), the set of cells in the *OTDOA-NeighbourCellInfoList* is grouped per frequency layer and in the decreasing order of priority for measurement to be performed by the target device, with the first cell in the list being the highest priority for measurement and with the same *earfcn* not appearing in more than one instance of *OTDOA-NeighbourFreqInfo*. + +If the target device is capable of supporting additional neighbour cells (as indicated by the presence of the IE *additionalNeighbourCellInfoList* in *OTDOA-ProvideCapabilities*), the list may contain all cells (up to 3x24 cells) belonging to the same frequency layer or cells from different frequency layers with the first cell in the list still being the highest priority for measurement. + +The prioritization of the cells in the list is left to server implementation. The target device should provide the available measurements in the same order as provided by the server. + +If inter-frequency neighbour cells are included in *OTDOA-NeighbourCellInfoList*, where an inter-frequency is a E-UTRA frequency which is different from the E-UTRA serving cell frequency, the LPP layer shall inform lower layers to start performing inter-frequency RSTD measurements for these neighbour cells and also provide to lower layers the information about these neighbour cells, e.g. EARFCN and PRS positioning occasion information. + +``` + +-- ASN1START + +OTDOA-NeighbourCellInfoList ::= SEQUENCE (SIZE (1..maxFreqLayers)) OF OTDOA-NeighbourFreqInfo +OTDOA-NeighbourFreqInfo ::= SEQUENCE (SIZE (1..24)) OF OTDOA-NeighbourCellInfoElement + +OTDOA-NeighbourCellInfoElement ::= SEQUENCE { + physCellId INTEGER (0..503), + cellGlobalId ECGI OPTIONAL, -- Need ON + earfcn ARFCN-ValueEUTRA OPTIONAL, -- Cond NotSameAsRef0 + cpLength ENUMERATED {normal, extended, ...} + OPTIONAL, -- Cond NotSameAsRef1 + prsInfo PRS-Info OPTIONAL, -- Cond NotSameAsRef2 + antennaPortConfig ENUMERATED {ports-1-or-2, ports-4, ...} + OPTIONAL, -- Cond NotSameAsRef3 + slotNumberOffset INTEGER (0..19) OPTIONAL, -- Cond NotSameAsRef4 + prs-SubframeOffset INTEGER (0..1279) OPTIONAL, -- Cond InterFreq + expectedRSTD INTEGER (0..16383), + expectedRSTD-Uncertainty INTEGER (0..1023), + ..., + [[ earfcn-v9a0 ARFCN-ValueEUTRA-v9a0 OPTIONAL -- Cond NotSameAsRef5 + ]], + [[ tpId-r14 INTEGER (0..4095) OPTIONAL, -- Need ON + prs-only-tp-r14 ENUMERATED { true } OPTIONAL, -- Cond TBS + cpLengthCRS-r14 ENUMERATED { normal, extended, ... } + OPTIONAL, -- Cond CRS + sameMBSFNconfigNeighbour-r14 BOOLEAN OPTIONAL, -- Need ON + dlBandwidth-r14 ENUMERATED {n6, n15, n25, n50, n75, n100} + OPTIONAL, -- Cond NotSameAsRef6 + addPRSconfigNeighbour-r14 SEQUENCE (SIZE (1..maxAddPRSconfig-r14)) OF + Add-PRSconfigNeighbourElement-r14 + OPTIONAL -- Need ON + ]], + [[ + tdd-config-v1520 TDD-Config-v1520 OPTIONAL -- Need ON + ]] +} + +``` + +``` + +Add-PRSconfigNeighbourElement-r14 ::= SEQUENCE { + add-prsInfo-r14 PRS-Info OPTIONAL, -- Cond NotSameAsRef7 + ... +} + +maxFreqLayers INTEGER ::= 3 + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NotsameAsRef0 | The field is absent if earfcn-v9a0 is present. If earfcn-v9a0 is not present, the field is mandatory present if the EARFCN is not the same as for the assistance data reference cell; otherwise it is not present. | +| NotsameAsRef1 | The field is mandatory present if the cyclic prefix length is not the same as for the assistance data reference cell; otherwise it is not present. | +| NotsameAsRef2 | The field is mandatory present if the first PRS configuration is not the same as for the assistance data reference cell; otherwise it is not present. | +| NotsameAsRef3 | The field is mandatory present if the antenna port configuration is not the same as for the assistance data reference cell; otherwise it is not present. | +| NotsameAsRef4 | The field is mandatory present if the slot timing is not the same as for the assistance data reference cell; otherwise it is not present. | +| NotSameAsRef5 | The field is absent if earfcn is present. If earfcn is not present, the field is mandatory present if the EARFCN is not the same as for the assistance data reference cell; otherwise it is not present. | +| InterFreq | The field is optionally present, need OP, if the EARFCN is not the same as for the assistance data reference cell; otherwise it is not present. | +| TBS | The field is mandatory present if the OTDOA-NeighbourCellInfoElement is provided for a PRS-only TP; otherwise it is not present. | +| CRS | The field is optionally present, need ON, if prsInfo is present. Otherwise it is not present. | +| NotSameAsRef6 | The field is mandatory present if PRS frequency hopping is used on this neighbour cell (TS 36.211 [16]) and if the downlink bandwidth configuration is not the same as for the assistance data reference cell; otherwise it is not present. | +| NotSameAsRef7 | The field is mandatory present if any instance of the additional PRS configurations of addPRSconfigNeighbour is not the same as the corresponding instance of the additional PRS configuration of the addPRSconfigRef for the assistance data reference cell; otherwise it is not present. | + +| OTDOA-NeighbourCellInfoList field descriptions | | +|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| physCellId | This field specifies the physical cell identity of the neighbour cell, as defined in TS 36.331 [12]. | +| cellGlobalId | This field specifies the ECGI, the globally unique identity of a cell in E-UTRA, of the neighbour cell, as defined in TS 36.331 [12]. The server should provide this field if it considers that it is needed to resolve any ambiguity in the cell identified by physCellId . | +| earfcn | This field specifies the EARFCN of the neighbour cell. | +| cpLength | This field specifies the cyclic prefix length of the neighbour cell PRS if PRS are present in this neighbour cell, otherwise this field specifies the cyclic prefix length of CRS in this neighbour cell. | +| prsInfo | This field specifies the first PRS configuration of the neighbour cell.
When the EARFCN of the neighbour cell is the same as for the assistance data reference cell, the target device may assume that each PRS positioning occasion in the neighbour cell at least partially overlaps with a PRS positioning occasion in the assistance data reference cell where the maximum offset between the transmitted PRS positioning occasions may be assumed to not exceed half a subframe.
When the EARFCN of the neighbour cell is the same as for the assistance data reference cell, the target may assume that this cell has the same PRS periodicity ( $T_{PRS}$ ) as the assistance data reference cell. | +| antennaPortConfig | This field specifies whether 1 (or 2) antenna port(s) or 4 antenna ports for cell specific reference signals are used. | +| slotNumberOffset | This field specifies the slot number offset at the transmitter between this cell and the assistance data reference cell. The slotNumberOffset together with the current slot number of the assistance data reference cell may be used to calculate the current slot number of this cell which may further be used to generate the CRS sequence by the target device. The offset corresponds to the number of full slots counted from the beginning of a radio frame of the assistance data reference cell to the beginning of the closest subsequent radio frame of this cell. If this field is absent, the slot timing is the same as for the assistance data reference cell. | + +| OTDOA-NeighbourCellInfoList field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

prs-SubframeOffset

This field specifies the offset between the first PRS subframe of the first PRS occasion group of the first PRS configuration in the assistance data reference cell on the reference carrier frequency layer and the first PRS subframe in the closest subsequent PRS occasion group of the PRS configuration with the longest PRS occasion group periodicity (NOTE 1) of this cell on the other carrier frequency layer. The value is given in number of full sub-frames. If the EARFCN is not the same as for the assistance data reference cell and the field is not present but PRS are available on this cell, the receiver shall consider the PRS subframe offset for this cell to be 0.

| +|

expectedRSTD

If PRS is transmitted:

This field indicates the RSTD value that the target device is expected to measure between this cell and the assistance data reference cell. The expectedRSTD field takes into account the expected propagation time difference as well as transmit time difference of PRS positioning occasions between the two cells. The RSTD value can be negative and is calculated as (expectedRSTD-8192). The resolution is 3 \times T_s, with T_s = 1/(15000 \times 2048) seconds.

If PRS is not transmitted:

This field indicates the RSTD value that the target device is expected to measure between this cell and the assistance data reference cell. The expectedRSTD field takes into account the expected propagation time difference as well as transmit time difference between the two cells. The RSTD value can be negative and is calculated as (expectedRSTD-8192). The resolution is 3 \times T_s, with T_s = 1/(15000 \times 2048) seconds.

| +|

expectedRSTD-Uncertainty

If PRS is transmitted:

This field indicates the uncertainty in expectedRSTD value. The uncertainty is related to the location server's a-priori estimation of the target device location. The expectedRSTD and expectedRSTD-Uncertainty together define the search window for the target device.

The scale factor of the expectedRSTD-Uncertainty field is 3 \times T_s, with T_s = 1/(15000 \times 2048) seconds.

The target device may assume that the beginning of the PRS occasion group of the PRS configuration with the longest PRS occasion group periodicity (NOTE) of the neighbour cell is received within the search window of size [- \text{expectedRSTD-Uncertainty} \times 3 \times T_s, \text{expectedRSTD-Uncertainty} \times 3 \times T_s] centred at T_{REF} + 1 \text{ millisecond} \times N + (\text{expectedRSTD-8192}) \times 3 \times T_s, where T_{REF} is the reception time of the beginning of the first PRS occasion group of the first PRS configuration of the assistance data reference cell at the target device antenna connector, N = 0 when the EARFCN of the neighbour cell is equal to that of the assistance data reference cell, and N = \text{prs-SubframeOffset} otherwise.

If PRS is not transmitted:

This field indicates the uncertainty in expectedRSTD value. The uncertainty is related to the location server's a-priori estimation of the target device location. The expectedRSTD and expectedRSTD-Uncertainty together define the search window for the target device. The scale factor of the expectedRSTD-Uncertainty field is 3 \times T_s, with T_s = 1/(15000 \times 2048) seconds.

If T_x is the reception time of the beginning of the subframe X of the assistance data reference cell at the target device antenna connector, the target device may assume that the beginning of the closest subframe of this neighbour cell to subframe X is received within the search window of size [- \text{expectedRSTD-Uncertainty} \times 3 \times T_s, \text{expectedRSTD-Uncertainty} \times 3 \times T_s] centred at T_x + (\text{expectedRSTD-8192}) \times 3 \times T_s.

| +|

tpId

This field specifies an identity of the transmission point. This field together with the physCellId and/or prsID may be used to identify the transmission point in the case the same physical cell ID is shared by multiple transmission points.

| +|

prs-only-tp

This field, if present, indicates that the OTDOA-NeighbourCellInfoElement is provided for a PRS-only TP.

For the purpose of RSTD measurements from a PRS-only TP, the target device shall not assume any other signals or physical channels are present other than PRS (TS 36.213 [28]).

For the purpose of RSTD measurements from a PRS-only TP, the target device shall use the physCellId only for PRS generation, and only if no PRS-ID is provided for this TP.

| + +| OTDOA-NeighbourCellInfoList field descriptions | | +|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cpLengthCRS | This field specifies the cyclic prefix length of this assistance data neighbour cell CRS. If this field is present, the target device may assume the CRS and PRS antenna ports of this assistance data neighbour cell are quasi co-located (as defined in TS 36.211 [16]). | +| sameMBSFNconfigNeighbour | This field indicates whether the MBSFN subframe configuration of the neighbour cell is the same as the current primary cell of the target device. TRUE means the same, and FALSE means not the same. | +| dlBandwidth | This field specifies the downlink bandwidth configuration of the neighbour cell, $N_{RB}$ in downlink, see TS 36.101 [21, table 5.6-1]. Enumerated value n6 corresponds to 6 resource blocks, n15 to 15 resource blocks and so on. | +| addPRSconfigNeighbour | This field specifies the additional (second and possibly third) PRS configuration(s) of the neighbour cell. When the EARFCN of the neighbour cell is the same as for the assistance data reference cell, the target device may assume that each PRS positioning occasion in each instance of addPRSconfigNeighbour in the neighbour cell at least partially overlaps with a PRS positioning occasion of the same instance of addPRSconfigRef in the assistance data reference cell where the maximum offset between the transmitted PRS positioning occasions may be assumed to not exceed half a subframe.
When the EARFCN of the neighbour cell is the same as for the assistance data reference cell, the target may assume that each instance of addPRSconfigNeighbour of this cell has the same PRS periodicity ( $T_{PRS}$ ) as the corresponding instance of addPRSconfigRef of the assistance data reference cell. | +| tdd-config | This field specifies the TDD specific physical channel configuration of the neighbour cell earfcn . The field should be present if this neighbour cell is a TDD cell and if the TDD UL/DL configuration for assistance data cells on this earfcn has not been provided in any other instance of OTDOA-NeighbourCellInfoElement or in IE OTDOA-ReferenceCellInfo , and is not the same as the target device's current primary cell when this is a TDD cell. NOTE 2. | + +NOTE 1: If this cell has more than one PRS configuration with equal longest PRS occasion group periodicity (i.e., PRS occasion group length times $T_{PRS}$ ), the first such configuration is referenced. In order to avoid ambiguity for frequency hopping, a PRS occasion group should contain at least 2 PRS occasions with hopping between 2 narrowbands and at least 4 PRS occasions with hopping between 4 narrowbands. + +NOTE 2: The target device assumes the same TDD UL/DL configuration for all TDD cells residing on same frequency band specified by *earfcn*. Therefore, the location server should include the field *tdd-config* only once for assistance data cells with the same *earfcn* in IE *OTDOA-ProvideAssistanceData*. The location server does not need to include the field *tdd-config* for any assistance data cell in IE *OTDOA-ProvideAssistanceData* with the same *earfcn* or the same TDD UL/DL configuration as the target devices' current primary cell if this is a TDD cell. + +## – OTDOA-ReferenceCellInfoNB + +The IE *OTDOA-ReferenceCellInfoNB* is used by the location server to provide NB-IoT assistance data reference cell information for OTDOA assistance data. + +``` +-- ASN1START +OTDOA-ReferenceCellInfoNB-r14 ::= SEQUENCE { + physCellIdNB-r14 INTEGER (0..503) OPTIONAL, -- Cond NoPRS-AD1 + cellGlobalIdNB-r14 ECGI OPTIONAL, -- Cond NoPRS-AD2 + carrierFreqRef-r14 CarrierFreq-NB-r14 OPTIONAL, -- Cond NotSameAsServ1 + earfcn-r14 ARFCN-ValueEUTRA-r14 OPTIONAL, -- Cond Inband + eutra-NumCRS-Ports-r14 ENUMERATED {ports1-or-2, ports4} + OPTIONAL, -- Cond NoPRS-AD3 + otdoa-SIB1-NB-repetitions-r14 ENUMERATED { r4, r8, r16 } OPTIONAL, -- Cond NotSameAsServ2 + nprsInfo-r14 PRS-Info-NB-r14 OPTIONAL, -- Cond NPRS-Type1 + ... + [[ + nprsInfo-Type2-v1470 PRS-Info-NB-r14 OPTIONAL -- Cond NPRS-Type2 + ]], + [[ + tdd-config-r15 TDD-Config-v1520 OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NoPRS-AD1 | This field is mandatory present if the OTDOA-ReferenceCellInfo IE is not included in OTDOA-ProvideAssistanceData , or if the OTDOA-ReferenceCellInfo IE is included in OTDOA-ProvideAssistanceData and the narrowband physical layer cell identity is not the same as the physical cell identity provided in OTDOA-ReferenceCellInfo IE. Otherwise it is not present. | +| NoPRS-AD2 | This field is optionally present, need ON, if the OTDOA-ReferenceCellInfo IE is not included in OTDOA-ProvideAssistanceData , or if the OTDOA-ReferenceCellInfo IE is included in OTDOA-ProvideAssistanceData and the global cell identity is not the same as provided in OTDOA-ReferenceCellInfo IE. | +| NotSameAsServ1 | This field is mandatory present if the carrier frequency of the NB-IoT assistance data reference cell is not the same as the carrier frequency of the target devices' current serving NB-IoT cell. Otherwise it is not present. | +| Inband | This field is mandatory present, if the NPRS is configured within the LTE spectrum allocation (inband deployment). Otherwise it is not present. | +| NoPRS-AD3 | This field is mandatory present if the OTDOA-ReferenceCellInfo IE is not included in OTDOA-ProvideAssistanceData and if the NB-IoT assistance data reference cell is deployed within the LTE spectrum allocation (inband deployment). Otherwise it is not present. | +| NotSameAsServ2 | This field is mandatory present, if NPRS configuration Part B only is configured on the NB-IoT assistance data reference cell, and if the repetition number of SIB1-NB of the NB-IoT assistance data reference cell is not the same as the repetition number of SIB1-NB of the target devices' current serving NB-IoT cell. Otherwise it is not present. | +| NPRS-Type1 | The field is mandatory present if Type 1 narrowband positioning reference signals are available in the assistance data reference cell (TS 36.211 [16]); otherwise it is not present. | +| NPRS-Type2 | The field is mandatory present if Type 2 narrowband positioning reference signals are available in the assistance data reference cell (TS 36.211 [16]); otherwise it is not present. | + +| OTDOA-ReferenceCellInfoNB field descriptions | | +|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| physCellIdNB | This field specifies the narrowband physical layer cell identity of the NB-IoT assistance data reference cell, as defined in TS 36.331 [12]. If this field is absent and if the OTDOA-ReferenceCellInfo IE is included in OTDOA-ProvideAssistanceData the narrowband physical layer cell identity is the same as the physCellId provided in OTDOA-ReferenceCellInfo IE. | +| cellGlobalIdNB | This field specifies the global cell identity of the NB-IoT assistance data reference cell, as defined in TS 36.331 [12]. If this field is absent and if the OTDOA-ReferenceCellInfo IE with cellGlobalId is included in OTDOA-ProvideAssistanceData , the global cell identity is the same as provided in OTDOA-ReferenceCellInfo IE. | +| carrierFreqRef | This field specifies the carrier frequency of the NB-IoT assistance data reference cell. | +| earfcn | This field specifies the EARFCN of the E-UTRAN frequency, in which the NB-IoT cell is deployed. | +| eutra-NumCRS-Ports | This field specifies whether 1 (or 2) antenna port(s) or 4 antenna ports for cell specific reference signals (CRS) are used in the NB-IoT assistance data reference cell. If this field is absent and if the OTDOA-ReferenceCellInfo IE is included in OTDOA-ProvideAssistanceData , the number of CRS antenna ports is the same as provided in OTDOA-ReferenceCellInfo IE. | +| otdoa-SIB1-NB-repetitions | This field specifies the repetition number of SIB1-NB of the NB-IoT assistance data reference cell. Enumerated values r4 correspond to 4 repetitions, r8 to 8 repetitions, and r16 to 16 repetitions.
Note, when NPRS configuration Part B only is configured on the NB-IoT assistance data reference cell (i.e., anchor carrier), nprs-NumSF does also count/include subframes containing NPSS, NSSS, NPBCH, or SIB1-NB, but the UE can assume that no NPRS are transmitted in these subframes (TS 36.211 [16]). | + +| OTDOA-ReferenceCellInfoNB field descriptions | | +|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nprsInfo | This field specifies the Type 1 NPRS (TS 36.211 [16]) configuration of the NB-IoT assistance data reference cell.

When the target device receives this field with operationModeInfoNPRS set to value 'standalone', the target device shall assume no NPRS are transmitted on that NB-IoT carrier. | +| nprsInfo-Type2 | This field specifies the Type 2 NPRS (TS 36.211 [16]) configuration of the NB-IoT assistance data reference cell. | +| tdd-config | Indicates the TDD specific physical channel configuration of the NB-IoT assistance data reference cell operating in TDD mode. This field should be present if the DL/UL subframe configuration of the NB-IoT assistance data reference cell is not the same as the DL/UL subframe configuration of the current serving NB-IoT cell of the target device, or if the current serving NB-IoT cell of the target device operates in FDD mode. | + +## PRS-Info-NB + +The IE *PRS-Info-NB* provides the information related to the configuration of NPRS in a cell. If *PRS-Info-NB* includes configurations for multiple NPRS carrier frequencies, the target device may assume the antenna ports for the NPRS carrier are quasi co-located, as defined in TS 36.211 [16]. + +``` +-- ASN1START +PRS-Info-NB-r14 ::= SEQUENCE (SIZE (1..maxCarrier-r14)) OF NPRS-Info-r14 + +NPRS-Info-r14 ::= SEQUENCE { + operationModeInfoNPRS-r14 ENUMERATED { inband, standalone }, + nprs-carrier-r14 CarrierFreq-NB-r14 OPTIONAL, -- Cond Standalone/Guardband + nprsSequenceInfo-r14 INTEGER (0..174) OPTIONAL, -- Cond Inband + nprsID-r14 INTEGER (0..4095) OPTIONAL, -- Cond NPRS-ID + partA-r14 SEQUENCE { + nprsBitmap-r14 CHOICE { + subframePattern10-r14 BIT STRING (SIZE (10)), + subframePattern40-r14 BIT STRING (SIZE (40)) + }, + nprs-MutingInfoA-r14 CHOICE { + po2-r14 BIT STRING (SIZE (2)), + po4-r14 BIT STRING (SIZE (4)), + po8-r14 BIT STRING (SIZE (8)), + po16-r14 BIT STRING (SIZE (16)), + ... + } OPTIONAL, -- Cond MutingA + ... OPTIONAL, -- Cond PartA + } + partB-r14 SEQUENCE { + nprs-Period-r14 ENUMERATED { ms160, ms320, ms640, ms1280, ... , ms2560-v1510}, + nprs-startSF-r14 ENUMERATED { zero, one-eighth, two-eighths, three-eighths, + four-eighths, five-eighths, six-eighths, + seven-eighths, ...}, + nprs-NumSF-r14 ENUMERATED { sf10, sf20, sf40, sf80, sf160, sf320, + sf640, sf1280, ... , sf2560-v1510}, + nprs-MutingInfoB-r14 CHOICE { + po2-r14 BIT STRING (SIZE (2)), + po4-r14 BIT STRING (SIZE (4)), + po8-r14 BIT STRING (SIZE (8)), + po16-r14 BIT STRING (SIZE (16)), + ... + } OPTIONAL, -- Cond MutingB + ... + [[ sib1-SF-TDD-r15 ENUMERATED { sf0, sf4, sf0and5} OPTIONAL -- Cond SIB1-TDD + ]] OPTIONAL, -- Cond PartB + ... + [[ + partA-TDD-r15 SEQUENCE { + nprsBitmap-r15 CHOICE { + subframePattern10-TDD-r15 BIT STRING (SIZE (8)), + subframePattern40-TDD-r15 BIT STRING (SIZE (32)), + ... + }, + nprs-MutingInfoA-r15 CHOICE { + po2-r15 BIT STRING (SIZE (2)), + po4-r15 BIT STRING (SIZE (4)), + po8-r15 BIT STRING (SIZE (8)), + } + } + ]] +``` + +``` + + pol6-r15 BIT STRING (SIZE(16)), + ... + } OPTIONAL, -- Cond MutingA + ... + } OPTIONAL -- Cond PartA-TDD + ]] + } +maxCarrier-r14 INTEGER ::= 5 + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Standalone/Guardband | This field is mandatory present, if the NPRS is configured in standalone or guardband operation mode. Otherwise it is not present. | +| Inband | This field is mandatory present, if the NPRS is configured within the LTE spectrum allocation (inband deployment) and the LTE carrier frequency is not provided in the assistance data. Otherwise it is not present. | +| NPRS-ID | The field is mandatory present, if the NPRS is generated based on the NPRS-ID (TS 36.211 [16]), different from the PCI. Otherwise the field is not present. | +| MutingA | The field is mandatory present, if muting is used for the NPRS Part A or Part A TDD configuration. Otherwise the field is not present. | +| PartA | The field is mandatory present, if NPRS is configured based on a bitmap of subframes which are not NB-IoT DL subframes (i.e., invalid DL subframes) (Part A configuration). Otherwise the field is not present. This field is not applicable for NB-IoT operating in TDD mode. | +| MutingB | The field is mandatory present, if muting is used for the NPRS Part B configuration. Otherwise the field is not present. | +| PartB | The field is mandatory present, if NPRS is configured based on a NPRS period, a NPRS subframe offset, and a number of consecutive NPRS downlink subframes per positioning occasion (Part B configuration). Otherwise the field is not present.
If NPRS configuration Part A and Part B are both configured, then a subframe contains NPRS if both configurations indicate that it contains NPRS. | +| PartA-TDD | The field is mandatory present, if NPRS is configured for NB-IoT operating in TDD mode and if NPRS is configured based on a bitmap of subframes which are not NB-IoT DL subframes (i.e., invalid DL subframes) (Part A TDD configuration). Otherwise the field is not present. | +| SIB1-TDD | The field is mandatory present, if NPRS is configured for NB-IoT operating in TDD mode and if SIB1-NB is transmitted on this carrier frequency. Otherwise the field is not present. | + +| PRS-Info-NB field descriptions | | +|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| operationModeInfoNPRS | This field specifies the operation mode of the NPRS carrier. The value 'standalone' indicates standalone or guardband operation mode. | +| nprs-carrier | This field specifies the NB-IoT carrier frequency for the NPRS. | +| nprsSequenceInfo | This field specifies the index of the PRB containing the NPRS as defined in the table nprsSequenceInfo to E-UTRA PRB index relation below. | +| nprsID | This field specifies the NPRS-ID as defined in TS 36.211 [16]. | +| sib1-SF-TDD | This field indicates the subframe(s) used to transmit SIB1-NB. Values sf0 and sf4 correspond with subframe #0 and #4 respectively. Value sf0and5 corresponds with subframes #0 and #5. | +| subframePattern10, subframePattern40 | This field specifies the NPRS subframe Part A configuration over 10 ms or 40 ms. Subframes not containing NPRS are indicated with value '0' in the bitmap; subframes containing NPRS are indicated with value '1' in the bitmap. The first/leftmost bit corresponds to the subframe #0 of the radio frame satisfying $SFN \bmod x = 0$ , where $x$ is the size of the bit string divided by 10. | + +| PRS-Info-NB field descriptions | | +|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nprs-MutingInfoA |

This field specifies the NPRS muting configuration of the NB-IoT carrier Part A configuration. The NPRS muting configuration is defined by a periodic NPRS muting sequence with periodicity T_{\text{REP}} where T_{\text{REP}}, counted in the number of NPRS positioning occasions, can be 2, 4, 8, or 16 which is also the length of the selected bit string that represents this NPRS muting sequence. If a bit in the NPRS muting sequence is set to '0', then the NPRS is muted in the corresponding NPRS positioning occasion. A NPRS positioning occasion for Part A comprises one radio frame (i.e., 10 subframes). The first/leftmost bit of the NPRS muting sequence corresponds to the first NPRS positioning occasion that starts after the beginning of the NB-IoT assistance data reference cell SFN=0. The sequence is valid for all subframes after the target device has received the nprs-MutingInfoA.

When the SFN of the NB-IoT assistance data reference cell is not known to the target device and nprs-MutingInfoA is provided for a cell in the OTDOA-NeighbourCellInfoListNB IE, the target device may assume no NPRS is transmitted by that cell.

| +| nprs-Period |

This field specifies the NPRS occasion period T_{\text{NPRS}} (TS 36.211 [16]). Enumerated values correspond to 160 ms, 320 ms, 640 ms, 1280 ms, and 2560 ms. The value ms2560 is only applicable to TDD mode.

| +| nprs-startSF |

This field specifies the subframe offset (TS 36.211 [16]). Enumerated values correspond to \alpha of 0, 1/8, 2/8, 3/8, 4/8, 5/8, 6/8, or 7/8.

| +| nprs-NumSF |

This field specifies the number of consecutive downlink subframes N_{\text{NPRS}} in one NPRS positioning occasion (TS 36.211 [16]). Enumerated values correspond to 10, 20, 40, 80, 160, 320, 640, 1280, and 2560 subframes. The values sf10 and sf20 are only applicable to FDD mode. The value sf2560 is only applicable to TDD mode.

When the target device receives a nprs-NumSF which exceeds the nprs-Period (i.e., N_{\text{NPRS}} > T_{\text{NPRS}}), the target device may assume no NPRS is transmitted by that cell.

| +| nprs-MutingInfoB |

This field specifies the NPRS muting configuration of the NB-IoT carrier Part B configuration. The NPRS muting configuration is defined by a periodic NPRS muting sequence with periodicity T_{\text{REP}} where T_{\text{REP}}, counted in the number of NPRS positioning occasions, can be 2, 4, 8, or 16 which is also the length of the selected bit string that represents this NPRS muting sequence. If a bit in the NPRS muting sequence is set to '0', then the NPRS is muted in the corresponding NPRS positioning occasion. A NPRS positioning occasion for Part B comprises N_{\text{NPRS}} consecutive downlink positioning subframes, where N_{\text{NPRS}} is given by the nprs-NumSF field. The first/leftmost bit of the NPRS muting sequence corresponds to the first NPRS positioning occasion that starts after the beginning of the NB-IoT assistance data reference cell SFN=0. The sequence is valid for all subframes after the target device has received the nprs-MutingInfoB.

When the SFN of the NB-IoT assistance data reference cell is not known to the UE and nprs-MutingInfoB is provided for a cell in the OTDOA-NeighbourCellInfoListNB IE, the target device may assume no NPRS is transmitted by that cell.

When the UE receives a T_{\text{REP}}-bit muting pattern together with a NPRS periodicity T_{\text{NPRS}} for the same carrier which exceeds 10240 subframes (i.e., T_{\text{REP}} \times T_{\text{NPRS}} > 10240 subframes), the target device shall assume an n-bit muting pattern based on the first n bits, where n = 10240/T_{\text{NPRS}}.

| +| subframePattern10-TDD, subframePattern40-TDD |

This field specifies the NPRS subframe Part A configuration for TDD over 10 ms or 40 ms. The UE shall assume that subframe number 1 and 2 are not used for NPRS. The MSB of the NPRS bitmap corresponds to subframe 0, the second MSB corresponds to subframe 3, the third MSB corresponds to subframe 4 and so on, as also shown in Figure NPRS bitmap to subframe number mapping below.

| + +***nprsSequenceInfo* to E-UTRA PRB index relation** + +| nprsSequenceInfo | E-UTRA PRB index for odd number of [16] | nprsSequenceInfo | E-UTRA PRB index for even number of [16] | +|--------------------------------|------------------------------------------------|--------------------------------|-------------------------------------------------| +| 0 - 74 | -37, -36, ..., 37 | 75 – 174 | -50, -49, ..., 49 | + +NOTE: Based on the above relation, in inband deployment, the carrier frequency of the NPRS carrier ( $f_{\text{NB-IoT}}$ ) can be calculated as follows: + +where $f_{\text{EUTRA}}$ is derived from *earfcn* according to TS 36.101 [21, 5.7.3]. + +![Diagram showing the mapping of NPRS bitmap to subframe numbers. A 'BIT STRING' of 8 bits (8, 7, 6, 5, 4, 3, 2, 1) is mapped to 'Subframe Numbers' 0 through 9. Arrows show the mapping: bit 8 to subframe 0, bit 7 to subframe 3, bit 6 to subframe 4, bit 5 to subframe 5, bit 4 to subframe 6, bit 3 to subframe 7, bit 2 to subframe 8, and bit 1 to subframe 9.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +| | | | | | | | | | | +|------------------|---|---|---|---|---|---|---|---|---| +| Subframe Numbers | | | | | | | | | | +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | +| BIT STRING | | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | + +Diagram showing the mapping of NPRS bitmap to subframe numbers. A 'BIT STRING' of 8 bits (8, 7, 6, 5, 4, 3, 2, 1) is mapped to 'Subframe Numbers' 0 through 9. Arrows show the mapping: bit 8 to subframe 0, bit 7 to subframe 3, bit 6 to subframe 4, bit 5 to subframe 5, bit 4 to subframe 6, bit 3 to subframe 7, bit 2 to subframe 8, and bit 1 to subframe 9. + +Figure 6.5.1.2-1: NPRS bitmap to subframe number mapping + +### OTDOA-NeighbourCellInfoListNB + +The IE *OTDOA-NeighbourCellInfoListNB* is used by the location server to provide NB-IoT neighbour cell information for OTDOA assistance data. + +``` +-- ASN1START + +OTDOA-NeighbourCellInfoListNB-r14 ::= SEQUENCE (SIZE (1..maxCells-r14)) OF + OTDOA-NeighbourCellInfoNB-r14 + +OTDOA-NeighbourCellInfoNB-r14 ::= SEQUENCE { + physCellIdNB-r14 INTEGER (0..503) OPTIONAL, -- Cond NoPRS-AD1 + cellGlobalIdNB-r14 ECGI OPTIONAL, -- Cond NoPRS-AD2 + carrierFreq-r14 CarrierFreq-NB-r14 OPTIONAL, -- Cond NotSameAsRef1 + earfcn-r14 ARFCN-ValueEUTRA-r14 OPTIONAL, -- Cond Inband + eutra-NumCRS-Ports-r14 ENUMERATED {ports-1-or-2, ports-4, ...} + OPTIONAL, -- Cond NotsameAsRef2 + otdoa-SIB1-NB-repetitions-r14 ENUMERATED { r4, r8, r16 } + nprsInfo-r14 PRS-Info-NB-r14 OPTIONAL, -- Cond NotSameAsRef3 + nprs-slotNumberOffset-r14 INTEGER (0..19) OPTIONAL, -- Cond NotsameAsRef5 + nprs-SFN-Offset-r14 INTEGER (0..63) OPTIONAL, -- Cond NotsameAsRef6 + nprs-SubframeOffset-r14 INTEGER (0..1279) OPTIONAL, -- Need OP + expectedRSTD-r14 INTEGER (0..16383) OPTIONAL, -- Cond NoPRS-AD3 + expectedRSTD-Uncertainty-r14 INTEGER (0..1023) OPTIONAL, -- Cond NoPRS-AD3 + prsNeighbourCellIndex-r14 INTEGER (1..72) OPTIONAL, -- Cond PRS-AD + ..., + [[ + nprsInfo-Type2-v1470 PRS-Info-NB-r14 OPTIONAL -- Cond NotSameAsRef4 + ]], + [[ + tdd-config-r15 TDD-Config-v1520 OPTIONAL -- Need ON + ]] +} + +maxCells-r14 INTEGER ::= 72 + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NoPRS-AD1 | This field is mandatory present if the OTDOA-NeighbourCellInfoList IE is not included in OTDOA-ProvideAssistanceData , or if the OTDOA-NeighbourCellInfoList IE is included in OTDOA-ProvideAssistanceData and the narrowband physical layer cell identity of this cell is not the same as the physical cell identity of the corresponding cell (as indicated by prsNeighbourCellIndex ) in OTDOA-NeighbourCellInfoList IE. | +| NoPRS-AD2 | This field is optionally present, need ON, if the OTDOA-NeighbourCellInfoList IE is not included in OTDOA-ProvideAssistanceData , or if the OTDOA-NeighbourCellInfoList IE is included in OTDOA-ProvideAssistanceData and the global cell identity of this cell is not the same as for the corresponding cell (as indicated by prsNeighbourCellIndex ) in OTDOA-NeighbourCellInfoList IE. | +| Inband | This field is mandatory present, if the NPRS is configured within the LTE spectrum allocation (inband deployment). Otherwise it is not present. | +| NotSameAsRef1 | The field is mandatory present if the carrier frequency is not the same as for the NB-IoT assistance data reference cell; otherwise it is not present. | +| NotSameAsRef2 | The field is mandatory present if this cell is deployed within the LTE spectrum allocation (inband deployment) and if the number of E-UTRA CRS antenna ports is not the same as for the NB-IoT assistance data reference cell; otherwise it is not present. | +| NotSameAsRef3 | This field is mandatory present if NPRS configuration Part B only is configured on this neighbour cell, and if the repetition number of SIB1-NB of this neighbor cell is not the same as the repetition number of SIB1-NB of the NB-IoT assistance data reference cell. Otherwise it is not present. | +| NotSameAsRef4 | The field is mandatory present, if the NPRS configuration is not the same as for the NB-IoT assistance data reference cell; otherwise it is not present. | +| NotSameAsRef5 | The field is mandatory present if the slot timing is not the same as for the NB-IoT assistance data reference cell; otherwise it is not present. | +| NotSameAsRef6 | The field is mandatory present if the frame timing is not the same as for the NB-IoT assistance data reference cell; otherwise it is not present. | +| NoPRS-AD3 | This field is mandatory present if the OTDOA-NeighbourCellInfoList IE is not included in OTDOA-ProvideAssistanceData , or if the OTDOA-NeighbourCellInfoList IE is included in OTDOA-ProvideAssistanceData and prsNeighbourCellIndex is absent for this cell. | +| PRS-AD | This field is optionally present, need ON, if the OTDOA-NeighbourCellInfoList IE is included in OTDOA-ProvideAssistanceData ; otherwise it is not present. | + +| OTDOA-NeighbourCellInfoListNB field descriptions | | +|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| physCellIdNB | This field specifies the narrowband physical cell identity of the NB-IoT neighbour cell, as defined in TS 36.331 [12]. If this field is absent and if the OTDOA-NeighbourCellInfoList IE is included in OTDOA-ProvideAssistanceData the narrowband physical layer cell identity is the same as the physCellId provided for the corresponding cell (as indicated by prsNeighbourCellIndex ) in OTDOA-NeighbourCellInfoList IE. | +| cellGlobalIdNB | This field specifies the global cell ID of the NB-IoT neighbour cell, as defined in TS 36.331 [12]. If this field is absent and if the OTDOA-NeighbourCellInfoList IE with cellGlobalId is included in OTDOA-ProvideAssistanceData , the global cell identity of the NB-IoT neighbour cell is the same as provided for the corresponding cell (as indicated by prsNeighbourCellIndex ) in OTDOA-NeighbourCellInfoList IE. | +| carrierFreq | This field specifies the carrier frequency of the NB-IoT neighbour cell. | +| earfcn | This field specifies the EARFCN of the E-UTRAN frequency, in which the NB-IoT cell is deployed. | +| eutra-NumCRS-Ports | This field specifies whether 1 (or 2) antenna port(s) or 4 antenna ports for cell specific reference signals are used. | +| otdoa-SIB1-NB-repetitions | This field specifies the repetition number of SIB1-NB of the neighbour cell. Enumerated values r4 correspond to 4 repetitions, r8 to 8 repetitions, and r16 to 16 repetitions.
Note, when NPRS configuration Part B only is configured on this NB-IoT neighbour cell (i.e., anchor carrier), nprs-NumSF does also count/include subframes containing NPSS, NSSS, NPBCH, or SIB1-NB, but the UE can assume that no NPRS are transmitted in these subframes (TS 36.211 [16]). | + +| OTDOA-NeighbourCellInfoListNB field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

nprsInfo
This field specifies the Type 1 NPRS (TS 36.211 [16]) configuration of the NB-IoT neighbour cell.

When the carrier frequency of the NB-IoT neighbour cell is the same as for the NB-IoT assistance data reference cell, the target device may assume that each NPRS positioning occasion for each NPRS carrier frequency in the neighbour cell at least partially overlaps with a NPRS positioning occasion for each NPRS carrier frequency in the NB-IoT assistance data reference cell where the maximum offset between the transmitted NPRS positioning occasions may be assumed to not exceed half a subframe.

When the carrier frequency of the neighbour cell is the same as for the NB-IoT assistance data reference cell, and NPRS configuration Part B is configured, the target may assume that this cell has the same NPRS periodicity (T_{\text{NPRS}}) as the assistance data reference cell for each NPRS carrier frequency.

When the target device receives this field with operationModeInfoNPRS set to value 'standalone', the target device shall assume no NPRS are transmitted on that NB-IoT carrier.

| +|

nprs-slotNumberOffset
This field specifies the slot number offset at the transmitter between this cell and the NB-IoT assistance data reference cell. The offset corresponds to the number of full slots counted from the beginning of a radio frame of the NB-IoT assistance data reference cell to the beginning of the closest subsequent radio frame of this cell. If this field is absent, the slot timing is the same as for the NB-IoT assistance data reference cell.

| +|

nprs-SFN-Offset
This field specifies the SFN offset (modulo 64) at the transmitter between this cell and the NB-IoT assistance data reference cell. The offset corresponds to the number of full radio frames counted from the beginning of a radio frame #0 of the NB-IoT assistance data reference cell to the beginning of the closest subsequent radio frame #0 of this cell. The UE may use this field together with the nprs-slotNumberOffset and otdoa-SIB1-NB-repetitions to determine the SIB1-NB subframes of this neighbour cell.

| +|

nprs-SubframeOffset
This field specifies the offset between the first NPRS subframe in the NB-IoT assistance data reference cell (NOTE 1) and the first NPRS subframe in the closest subsequent NPRS positioning occasion of the NPRS carrier with the longest NPRS periodicity of this cell (NOTE 2). The value is given in number of full sub-frames. If this field is not present, the receiver shall consider the NPRS subframe offset to be 0.

| +|

expectedRSTD
This field indicates the RSTD value that the target device is expected to measure between this cell and the NB-IoT assistance data reference cell. The expectedRSTD field takes into account the expected propagation time difference as well as transmit time difference of NPRS positioning occasions between the two cells. The RSTD value can be negative and is calculated as (\text{expectedRSTD}-8192). The resolution is 3 \times T_s, with T_s = 1/(15000 \times 2048) seconds. If this field is absent and if the OTDOA-NeighbourCellInfoList IE is included in OTDOA-ProvideAssistanceData, the expected RSTD is the same as provided in OTDOA-NeighbourCellInfoList IE for the corresponding cell (as indicated by prsNeighbourCellIndex).

| +|

expectedRSTD-Uncertainty
This field indicates the uncertainty in expectedRSTD value. The uncertainty is related to the location server's a-priori estimation of the target device location. The expectedRSTD and expectedRSTD-Uncertainty together define the search window for the target device.

The scale factor of the expectedRSTD-Uncertainty field is 3 \times T_s, with T_s = 1/(15000 \times 2048) seconds.

If this field is absent and if the OTDOA-NeighbourCellInfoList IE is included in OTDOA-ProvideAssistanceData, the expected RSTD uncertainty is the same as provided in OTDOA-NeighbourCellInfoList IE for the corresponding cell (as indicated by prsNeighbourCellIndex).

The target device may assume that the beginning of the NPRS positioning occasion of the NPRS carrier with the longest NPRS periodicity of the neighbour cell (NOTE 2) is received within the search window of size [-\text{expectedRSTD-Uncertainty} \times 3 \times T_s, \text{expectedRSTD-Uncertainty} \times 3 \times T_s] centred at T_{\text{REF}} + 1 \text{ millisecond} \times N + (\text{expectedRSTD}-8192) \times 3 \times T_s, where T_{\text{REF}} is the reception time of the beginning of the NPRS positioning occasion of the NB-IoT assistance data reference cell (NOTE 1) at the target device antenna connector, and N = \text{nprs-SubframeOffset}.

| +|

prsNeighbourCellIndex
This field contains an index of the entry in IE OTDOA-NeighbourCellInfoList. Value 1 corresponds to the first cell in OTDOA-NeighbourCellInfoList, value 2 to the second, and so on. If this field is absent, and if the OTDOA-NeighbourCellInfoList IE is included in OTDOA-ProvideAssistanceData, it means there is no corresponding cell in OTDOA-NeighbourCellInfoList IE for this cell.

The target device may assume the antenna ports of the PRS of the cell indicated by prsNeighbourCellIndex and the NPRS of this cell are quasi co-located, as defined in TS 36.211 [16].

| +|

nprsInfo-Type2
This field specifies the Type 2 NPRS (TS 36.211 [16]) configuration of the NB-IoT neighbour cell.

| +|

tdd-config
Indicates the TDD specific physical channel configuration of the NB-IoT assistance data neighbour cell operating in TDD mode. This field should be present if the DL/UL subframe configuration of the NB-IoT assistance data neighbour cell is not the same as for the NB-IoT assistance data reference cell, or if the current serving NB-IoT cell of the target device operates in FDD mode.

| + +NOTE 1: If the NB-IoT assistance data reference cell (i.e., anchor carrier) has no NPRS configured, the first NPRS carrier in *PRS-Info-NB* is referenced. + +NOTE 2: "Cell" in this context may not necessarily be the anchor carrier. If this "cell" has more than one NPRS carrier with equal longest periodicity, the first such NPRS carrier in *PRS-Info-NB* is referenced. The length of a NPRS positioning occasion for Part A in this context is the length of the *nprsBitmap* bit string. + +### 6.5.1.3 OTDOA Assistance Data Request + +#### – *OTDOA-RequestAssistanceData* + +The IE *OTDOA-RequestAssistanceData* is used by the target device to request assistance data from a location server. + +``` +-- ASN1START +OTDOA-RequestAssistanceData ::= SEQUENCE { + physCellId INTEGER (0..503), + ..., + [[ + adType-r14 BIT STRING { prs (0), nprs (1) } (SIZE (1..8)) OPTIONAL + ]], + [[ + nrPhysCellId-r15 INTEGER (0..1007) OPTIONAL + ]] +} +-- ASN1STOP +``` + +#### *OTDOA-RequestAssistanceData* field descriptions + +##### ***physCellId*** + +This field specifies the E-UTRA physical cell identity of the current primary cell of the target device. + +##### ***adType*** + +This field specifies the assistance data requested. This is represented by a bit string, with a one-value at the bit position means the particular assistance data is requested; a zero-value means not requested. + +Bit 0 indicates that PRS assistance data are requested, bit 1 indicates that NPRS assistance data are requested. + +##### ***nrPhysCellId*** + +This field specifies the NR physical cell identity of the current primary cell of the target device. If this field is present, the target device sets the *physCellId* to an arbitrary value which shall be ignored by the location server. + +### 6.5.1.4 OTDOA Location Information + +#### – *OTDOA-ProvideLocationInformation* + +The IE *OTDOA-ProvideLocationInformation* is used by the target device to provide OTDOA location measurements to the location server. It may also be used to provide OTDOA positioning specific error reason. + +``` +-- ASN1START +OTDOA-ProvideLocationInformation ::= SEQUENCE { + otdoaSignalMeasurementInformation OTDOA-SignalMeasurementInformation OPTIONAL, + otdoa-Error OTDOA-Error OPTIONAL, + ..., + [[ + otdoaSignalMeasurementInformation-NB-r14 OTDOA-SignalMeasurementInformation-NB-r14 + ]], + OPTIONAL +} +-- ASN1STOP +``` + +## 6.5.1.5 OTDOA Location Information Elements + +### – OTDOA-SignalMeasurementInformation + +The IE *OTDOA-SignalMeasurementInformation* is used by the target device to provide RSTD measurements to the location server. The RSTD measurements are provided for a neighbour cell and the RSTD reference cell, both of which are provided in the IE *OTDOA-ProvideAssistanceData*. The RSTD reference cell may or may not be the same as the assistance data reference cell provided in *OTDOA-ReferenceCellInfo* or *OTDOA-ReferenceCellInfoNB*. If the target device stops reporting inter-frequency RSTD measurements, where the inter-frequency RSTD measurement is an OTDOA RSTD measurement with at least one cell on a frequency different from the serving cell frequency, the LPP layer shall inform lower layers that inter-frequency RSTD measurements are stopped. + +NOTE 1: If there are more than 24 *NeighbourMeasurementElement* to be sent, the target device may send them in multiple *ProvideLocationInformation* messages, as described under clause 5.3. + +NOTE 2: If NPRS/PRS antenna ports are quasi co-located, the target device provides a single RSTD measurement for the quasi co-located antenna ports of NPRS/PRS. + +``` +-- ASN1START + +OTDOA-SignalMeasurementInformation ::= SEQUENCE { + systemFrameNumber BIT STRING (SIZE (10)), + physCellIdRef INTEGER (0..503), + cellGlobalIdRef ECGI OPTIONAL, + earfcnRef ARFCN-ValueEUTRA OPTIONAL, -- Cond NotSameAsRef0 + referenceQuality OTDOA-MeasQuality OPTIONAL, + neighbourMeasurementList NeighbourMeasurementList, + ... + [[ earfcnRef-v9a0 ARFCN-ValueEUTRA-v9a0 OPTIONAL -- Cond NotSameAsRef1 + ]], + [[ tpIdRef-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer0 + prsIdRef-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer1 + additionalPathsRef-r14 AdditionalPathList-r14 OPTIONAL, + nprsIdRef-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer2 + carrierFreqOffsetNB-Ref-r14 CarrierFreqOffsetNB-r14 OPTIONAL, -- Cond NB-IoT + hyperSFN-r14 BIT STRING (SIZE (10)) OPTIONAL -- Cond H-SFN + ]], + [[ motionTimeSource-r15 MotionTimeSource-r15 OPTIONAL + ]] +} + +NeighbourMeasurementList ::= SEQUENCE (SIZE(1..24)) OF NeighbourMeasurementElement + +NeighbourMeasurementElement ::= SEQUENCE { + physCellIdNeighbour INTEGER (0..503), + cellGlobalIdNeighbour ECGI OPTIONAL, + earfcnNeighbour ARFCN-ValueEUTRA OPTIONAL, -- Cond NotSameAsRef2 + rstd INTEGER (0..12711), + rstd-Quality OTDOA-MeasQuality, + ... + [[ earfcnNeighbour-v9a0 ARFCN-ValueEUTRA-v9a0 OPTIONAL -- Cond NotSameAsRef3 + ]], + [[ tpIdNeighbour-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer0 + prsIdNeighbour-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer1 + delta-rstd-r14 INTEGER (0..5) OPTIONAL, + additionalPathsNeighbour-r14 AdditionalPathList-r14 OPTIONAL, + nprsIdNeighbour-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer2 + carrierFreqOffsetNB-Neighbour-r14 CarrierFreqOffsetNB-r14 OPTIONAL + -- Cond NB-IoT + ]], + [[ delta-SFN-r15 INTEGER (-8192..8191) OPTIONAL + ]] +} + +AdditionalPathList-r14 ::= SEQUENCE (SIZE(1..maxPaths-r14)) OF AdditionalPath-r14 + +maxPaths-r14 INTEGER ::= 2 + +MotionTimeSource-r15 ::= SEQUENCE { +``` + +``` + +timeSource-r15 ENUMERATED {servingCell, referenceCell, gnss, mixed, +other, none, ...} +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NotSameAsRef0 | The field is absent if the corresponding earfcnRef-v9a0 is present. Otherwise, the target device shall include this field if the EARFCN of the RSTD reference cell is not the same as the EARFCN of the assistance data reference cell provided in the OTDOA assistance data. | +| NotSameAsRef1 | The field is absent if the corresponding earfcnRef is present. Otherwise, the target device shall include this field if the EARFCN of the RSTD reference cell is not the same as the EARFCN of the assistance data reference cell provided in the OTDOA assistance data. | +| NotSameAsRef2 | The field is absent if the corresponding earfcnNeighbour-v9a0 is present. Otherwise, the target device shall include this field if the EARFCN of this neighbour cell is not the same as the earfcnRef for the RSTD reference cell. | +| NotSameAsRef3 | The field is absent if the corresponding earfcnNeighbour is present. Otherwise, the target device shall include this field if the EARFCN of this neighbour cell is not the same as the earfcnRef for the RSTD reference cell. | +| ProvidedByServer0 | The target device shall include this field if a tpId for this transmission point is included in the OTDOA-ProvideAssistanceData . Otherwise the field is absent. | +| ProvidedByServer1 | The target device shall include this field if a prsId for this transmission point is included in the OTDOA-ProvideAssistanceData . Otherwise the field is absent. | +| ProvidedByServer2 | The target device shall include this field if an nprsId for this cell is included in the OTDOA-ProvideAssistanceData and if this cell is a NB-IoT only cell (without associated LTE PRS cell). Otherwise the field is absent. | +| NB-IoT | The target device shall include this field if the cell is a NB-IoT only cell (without associated LTE PRS cell). Otherwise the field is absent. | +| H-SFN | The target device shall include this field if it was able to determine a hyper SFN of the RSTD reference cell. | + +| OTDOA-SignalMeasurementInformation field descriptions | | +|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| systemFrameNumber |

If the delta-SFN and motionTimeSource fields are not present, this field specifies the SFN of the RSTD reference cell containing the starting subframe of the PRS or NPRS positioning occasion if PRS or NPRS are available on the RSTD reference cell, or subframe of the CRS for RSTD measurements if PRS and NPRS are not available on the RSTD reference cell during which the most recent neighbour cell RSTD measurement was performed.

In the case of more than a single PRS configuration on the RSTD reference cell, the first PRS configuration is referenced.

If the delta-SFN and motionTimeSource fields are present, this field specifies the SFN of the RSTD reference cell when the TOA measurement for the RSTD reference cell has been made.

| +| physCellIdRef | This field specifies the physical cell identity of the RSTD reference cell. | +| cellGlobalIdRef | This field specifies the ECGI, the globally unique identity of a cell in E-UTRA, of the RSTD reference cell. The target shall provide this IE if it knows the ECGI of the RSTD reference cell. | +| earfcnRef | This field specifies the EARFCN of the RSTD reference cell. | +| referenceQuality |

This field specifies the target device's best estimate of the quality of the TOA measurement from the RSTD reference cell, T_{\text{SubframeRxRef}}, where T_{\text{SubframeRxRef}} is the time of arrival of the signal from the RSTD reference cell.

When delta-SFN and motionTimeSource are both included, the target device shall not include measurement errors caused by motion of the target device in referenceQuality (e.g. the target device may assume the target device was stationary during OTDOA measurements).

| +| neighbourMeasurementList | This list contains the measured RSTD values for neighbour cells together with the RSTD reference cell, along with quality for each measurement. | +| tpIdRef | This field specifies the transmission point ID of the RSTD reference cell. | +| prsIdRef | This field specifies the PRS-ID of the first PRS configuration of the RSTD reference cell. | +| additionalPathsRef | This field specifies one or more additional detected path timing values for the RSTD reference cell, relative to the path timing used for determining the rstd value. If this field was requested but is not included, it means the UE did not detect any additional path timing values. | + +| OTDOA-SignalMeasurementInformation field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nprslDRef
This field specifies the NPRS-ID of the RSTD reference cell. | +| carrierFreqOffsetNB-Ref
This field specifies the offset of the NB-IoT channel number to EARFCN given by earfcnRef as defined in TS 36.101 [21]. | +| hyperSFN
This field specifies the hyper SFN as defined in TS 36.331 [12] of the RSTD reference cell for the systemFrameNumber . | +| motionTimeSource
This field provides reference information concerning the movement of the target device and comprises the following subfields:
  • - timeSource specifies the external time source to which UE time was locked during the OTDOA measurements. Enumerated value "mixed" indicates that UE time was locked to more than one external time source during OTDOA measurements (e.g. is applicable to a change in serving cell when the serving cell was used as a time source). The value "other" indicates some other external time source. The value "none" indicates that UE time was not locked to an external time source.
If this field is present, the target device shall also provide the IE Sensor-MotionInformation in IE Sensor-ProvideLocationInformation . | +| physCellIdNeighbour
This field specifies the physical cell identity of the neighbour cell for which the RSTDs are provided. | +| cellGlobalIdNeighbour
This field specifies the ECGI, the globally unique identity of a cell in E-UTRA, of the neighbour cell for which the RSTDs are provided. The target device shall provide this IE if it was able to determine the ECGI of the neighbour cell at the time of measurement. | +| earfcnNeighbour
This field specifies the EARFCN of the neighbour cell used for the RSTD measurements. | +| rstd
This field specifies the relative timing difference between this neighbour cell and the RSTD reference cell, as defined in TS 36.214 [17]. Mapping of the measured quantity is defined as in TS 36.133 [18] clause 9.1.10.3. | +| rstd-Quality
This field specifies the target device's best estimate of the quality of the measured rstd .
When delta-SFN and motionTimeSource both included, the target device shall not include measurement errors caused by motion of the target device in rstd-Quality (e.g. the target device may assume the target device was stationary during OTDOA measurements). | +| tpIdNeighbour
This field specifies the transmission point ID for the neighbour cell for which the RSTDs are provided. | +| prsIdNeighbour
This field specifies the PRS-ID of the first PRS configuration of the neighbour cell for which the RSTDs are provided. | +| delta-rstd
This field specifies the higher-resolution RSTD $\Delta_{\text{RSTD}}$ as defined in TS 36.133 [18] clause 9.1.10.4. Mapping of the measured quantity is defined as in TS 36.133 [18] clause 9.1.10.4. | +| additionalPathsNeighbour
This field specifies one or more additional detected path timing values for the neighbour cell, relative to the path timing used for determining the rstd value. If this field was requested but is not included, it means the UE did not detect any additional path timing values. | +| nprslDNeighbour
This field specifies the NPRS-ID of the neighbour cell for which the RSTDs are provided. | +| carrierFreqOffsetNB-Neighbour
This field specifies the offset of the NB-IoT channel number to EARFCN given by earfcnNeighbour as defined in TS 36.101 [21]. | +| delta-SFN
This field provides information concerning the movement of the target device:
Together with systemFrameNumber specifies the measurementSFN of the RSTD reference cell when the TOA measurement for this neighbour cell has been made for determining the rstd . The measurementSFN is given by systemFrameNumber + delta-SFN . (The actual SFN is the measurementSFN modulo 1024.). The measurementSFN is used in IE Sensor-MotionInformation to provide movement information corresponding to the TOA measurement time.
If this field is present, the target device shall also provide the IE Sensor-MotionInformation in IE Sensor-ProvideLocationInformation . | + +## – OTDOA-SignalMeasurementInformation-NB + +The IE *OTDOA-SignalMeasurementInformation-NB* is used by the target device to provide RSTD measurements to the location server. The RSTD measurements are provided for a neighbour cell and the RSTD reference cell, both of which are provided in the IE *OTDOA-ProvideAssistanceData*. The RSTD reference cell may or may not be the same as the assistance data reference cell provided in *OTDOA-ReferenceCellInfo* or *OTDOA-ReferenceCellInfoNB*. If the target device stops reporting inter-frequency RSTD measurements, where the inter-frequency RSTD measurement is an OTDOA RSTD measurement with at least one cell on a frequency different from the serving cell frequency, the LPP layer shall inform lower layers that inter-frequency RSTD measurements are stopped. + +NOTE 1: If there are more than 24 *NeighbourMeasurementElement-NB* to be sent, the target device may send them in multiple *ProvideLocationInformation* messages, as described under clause 5.3. + +NOTE 2: If NPRS/PRS antenna ports are quasi co-located, the target device provides a single RSTD measurement for the quasi co-located antenna ports of NPRS/PRS. + +``` +-- ASN1START + +OTDOA-SignalMeasurementInformation-NB-r14 ::= SEQUENCE { + systemFrameNumber-r14 BIT STRING (SIZE (10)), + physCellIdRef-r14 INTEGER (0..503), + cellGlobalIdRef-r14 ECGI OPTIONAL, + earfcnRef-r14 ARFCN-ValueEUTRA-r14 OPTIONAL, -- Cond NotSameAsRef0 + referenceQuality-r14 OTDOA-MeasQuality OPTIONAL, + neighbourMeasurementList-r14 NeighbourMeasurementList-NB-r14, + tpIdRef-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer0 + prsIdRef-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer1 + additionalPathsRef-r14 AdditionalPathList-r14 OPTIONAL, + nprsIdRef-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer2 + carrierFreqOffsetNB-Ref-r14 CarrierFreqOffsetNB-r14 OPTIONAL, -- Cond NB-IoT + hyperSFN-r14 BIT STRING (SIZE (10)) OPTIONAL, -- Cond H-SFN + ... +} + +NeighbourMeasurementList-NB-r14 ::= SEQUENCE (SIZE(1..24)) OF NeighbourMeasurementElement-NB-r14 + +NeighbourMeasurementElement-NB-r14 ::= SEQUENCE { + physCellIdNeighbour-r14 INTEGER (0..503), + cellGlobalIdNeighbour-r14 ECGI OPTIONAL, + earfcnNeighbour-r14 ARFCN-ValueEUTRA-r14 OPTIONAL, -- Cond NotSameAsRef2 + rstd-r14 INTEGER (0..12711), + rstd-Quality-r14 OTDOA-MeasQuality, + tpIdNeighbour-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer0 + prsIdNeighbour-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer1 + delta-rstd-r14 INTEGER (0..5) OPTIONAL, + additionalPathsNeighbour-r14 + AdditionalPathList-r14 OPTIONAL, + nprsIdNeighbour-r14 INTEGER (0..4095) OPTIONAL, -- Cond ProvidedByServer2 + carrierFreqOffsetNB-Neighbour-r14 + CarrierFreqOffsetNB-r14 OPTIONAL, -- Cond NB-IoT + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NotSameAsRef0 | The target device shall include this field if the EARFCN of the RSTD reference cell is not the same as the EARFCN of the assistance data reference cell provided in the OTDOA assistance data. | +| NotSameAsRef2 | The target device shall include this field if the EARFCN of this neighbour cell is not the same as the earfcnRef for the RSTD reference cell. | +| ProvidedByServer0 | The target device shall include this field if a tpId for this transmission point is included in the OTDOA-ProvideAssistanceData . Otherwise the field is absent. | +| ProvidedByServer1 | The target device shall include this field if a prsId for this transmission point is included in the OTDOA-ProvideAssistanceData . Otherwise the field is absent. | +| ProvidedByServer2 | The target device shall include this field if an nprsId for this cell is included in the OTDOA-ProvideAssistanceData and if this cell is a NB-IoT only cell (without associated LTE PRS cell). Otherwise the field is absent. | +| NB-IoT | The target device shall include this field if the cell is a NB-IoT only cell (without associated LTE PRS cell). Otherwise the field is absent. | +| H-SFN | The target device shall include this field if it was able to determine a hyper SFN of the RSTD reference cell. | + +| OTDOA-SignalMeasurementInformation-NB field descriptions | | +|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| systemFrameNumber | This field specifies the SFN of the RSTD reference cell containing the starting subframe of the PRS or NPRS positioning occasion if PRS or NPRS are available on the RSTD reference cell, or subframe of the CRS for RSTD measurements if PRS and NPRS are not available on the RSTD reference cell during which the most recent neighbour cell RSTD measurement was performed.
In the case of more than a single PRS configuration on the RSTD reference cell, the first PRS configuration is referenced. | +| physCellIdRef | This field specifies the physical cell identity of the RSTD reference cell. | +| cellGlobalIdRef | This field specifies the ECGI, the globally unique identity of a cell in E-UTRA, of the RSTD reference cell. The target shall provide this IE if it knows the ECGI of the RSTD reference cell. | +| earfcnRef | This field specifies the EARFCN of the RSTD reference cell. | +| referenceQuality | This field specifies the target device's best estimate of the quality of the TOA measurement from the RSTD reference cell, $T_{SubframeRxRef}$ , where $T_{SubframeRxRef}$ is the time of arrival of the signal from the RSTD reference cell. | +| neighbourMeasurementList | This list contains the measured RSTD values for neighbour cells together with the RSTD reference cell, along with quality for each measurement. | +| tpIdRef | This field specifies the transmission point ID of the RSTD reference cell. | +| prsIdRef | This field specifies the PRS-ID of the first PRS configuration of the RSTD reference cell. | +| additionalPathsRef | This field specifies one or more additional detected path timing values for the RSTD reference cell, relative to the path timing used for determining the rstd value. If this field was requested but is not included, it means the UE did not detect any additional path timing values. | +| nprsIdRef | This field specifies the NPRS-ID of the RSTD reference cell. | +| carrierFreqOffsetNB-Ref | This field specifies the offset of the NB-IoT channel number to EARFCN given by earfcnRef as defined in TS 36.101 [21]. | +| hyperSFN | This field specifies the hyper SFN as defined in TS 36.331 [12] of the RSTD reference cell for the systemFrameNumber . | +| physCellIdNeighbour | This field specifies the physical cell identity of the neighbour cell for which the RSTDs are provided. | +| cellGlobalIdNeighbour | This field specifies the ECGI, the globally unique identity of a cell in E-UTRA, of the neighbour cell for which the RSTDs are provided. The target device shall provide this IE if it was able to determine the ECGI of the neighbour cell at the time of measurement. | +| earfcnNeighbour | This field specifies the EARFCN of the neighbour cell used for the RSTD measurements. | +| rstd | This field specifies the relative timing difference between this neighbour cell and the RSTD reference cell, as defined in TS 36.214 [17]. Mapping of the measured quantity is defined as in TS 36.133 [18] clause 9.1.10.3. | + +| OTDOA-SignalMeasurementInformation-NB field descriptions | | +|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| rstd-Quality | This field specifies the target device's best estimate of the quality of the measured rstd . | +| tpIdNeighbour | This field specifies the transmission point ID for the neighbour cell for which the RSTDs are provided. | +| prsIdNeighbour | This field specifies the PRS-ID of the first PRS configuration of the neighbour cell for which the RSTDs are provided. | +| delta-rstd | This field specifies the higher-resolution RSTD $\Delta_{\text{RSTD}}$ as defined in TS 36.133 [18] clause 9.1.10.4. Mapping of the measured quantity is defined as in TS 36.133 [18] clause 9.1.10.4. | +| additionalPathsNeighbour | This field specifies one or more additional detected path timing values for the neighbour cell, relative to the path timing used for determining the rstd value. If this field was requested but is not included, it means the UE did not detect any additional path timing values. | +| nprsIdNeighbour | This field specifies the NPRS-ID of the neighbour cell for which the RSTDs are provided. | +| carrierFreqOffsetNB-Neighbour | This field specifies the offset of the NB-IoT channel number to EARFCN given by earfcnNeighbour as defined in TS 36.101 [21]. | + +## – OTDOA-MeasQuality + +``` +-- ASN1START + +OTDOA-MeasQuality ::= SEQUENCE { + error-Resolution BIT STRING (SIZE (2)), + error-Value BIT STRING (SIZE (5)), + error-NumSamples BIT STRING (SIZE (3)) OPTIONAL, + ... +} + +-- ASN1STOP +``` + +| OTDOA-MeasQuality field descriptions | | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| error-Resolution | This field specifies the resolution R used in error-Value field. The encoding on two bits is as follows:
'00' 5 metres
'01' 10 metres
'10' 20 metres
'11' 30 metres | +| error-Value | This field specifies the target device's best estimate of the uncertainty of the OTDOA (or TOA) measurement. The encoding on five bits is as follows:
'00000' 0 to (R*1-1) metres
'00001' R*1 to (R*2-1) metres
'00010' R*2 to (R*3-1) metres
...
'11111' R*31 metres or more;
where R is the resolution defined by error-Resolution field.
E.g., R=20 m corresponds to 0-19 m, 20-39 m, ..., 620+ m. | +| error-NumSamples | If the error-Value field provides the sample uncertainty of the OTDOA (or TOA) measurement, this field specifies how many measurements have been used by the target device to determine this (i.e., sample size). Following 3 bit encoding is used:
'000' Not the baseline metric
'001' 5-9
'010' 10-14
'011' 15-24
'100' 25-34
'101' 35-44
'110' 45-54
'111' 55 or more.
In the case of the value '000', the error-Value field contains the target device's best estimate of the uncertainty of the OTDOA (or TOA) measurement not based on the baseline metric. E.g., other measurements such as signal-to-noise-ratio or signal strength can be utilized to estimate the error-Value .
If this field is absent, the value of this field is '000'. | + +### AdditionalPath + +The IE *AdditionalPath* is used by the target device to provide information about additional paths associated with the RSTD measurements in the form of a relative time difference and a quality value. The additional path *relativeTimeDifference* is the detected path timing relative to the detected path timing used for the *rstd* value (TS 36.214 [17]), and each additional path can be associated with a quality value *path-Quality*. + +``` +-- ASN1START +AdditionalPath-r14 ::= SEQUENCE { + relativeTimeDifference-r14 INTEGER (-256..255), + path-Quality-r14 OTDOA-MeasQuality OPTIONAL, + ... +} + +-- ASN1STOP +``` + +#### AdditionalPath field descriptions + +##### *relativeTimeDifference* + +This field specifies the additional detected path timing relative to the detected path timing used for the *rstd* value in units of 0.5 Ts, with $T_s = 1/(15000 \cdot 2048)$ seconds. A positive value indicates that the particular path is later in time than the detected path used for RSTD; a negative value indicates that the particular path is earlier in time than the detected path used for RSTD. + +##### *path-Quality* + +This field specifies the target device's best estimate of the quality of the detected timing of the additional path. + +### 6.5.1.6 OTDOA Location Information Request + +### OTDOA-RequestLocationInformation + +The IE *OTDOA-RequestLocationInformation* is used by the location server to request OTDOA location measurements from a target device. Details of the required measurements (e.g. details of assistance data reference cell and neighbour cells) are conveyed in the *OTDOA-ProvideAssistanceData* IE in a separate Provide Assistance Data message. + +``` +-- ASN1START +OTDOA-RequestLocationInformation ::= SEQUENCE { + assistanceAvailability BOOLEAN, + ... + [[ + multipathRSTD-r14 ENUMERATED { requested } OPTIONAL, -- Need ON + maxNoOfRSTDmeas-r14 INTEGER (1..32) OPTIONAL, -- Need ON + ]], + [[ + motionMeasurements-r15 ENUMERATED { requested } OPTIONAL, -- Need ON + ]] +} + +-- ASN1STOP +``` + +#### OTDOA-RequestLocationInformation field descriptions + +##### *assistanceAvailability* + +This field indicates whether the target device may request additional OTDOA assistance data from the server. TRUE means allowed and FALSE means not allowed. + +##### *multipathRSTD* + +This field, if present, indicates that the target device is requested to report additional detected path timing information per RSTD reference and neighbour cell. + +##### *maxNoOfRSTDmeas* + +This field, if present, indicates the maximum number of *NeighbourMeasurementElement* fields (i.e., RSTD measurements) the target device can provide in *OTDOA-SignalMeasurementInformation*. + +**OTDOA-RequestLocationInformation field descriptions****motionMeasurements** + +This field, if present, indicates that the target device is requested to report the motion measurements (*delta-SFN* and *motionTimeSource*) in *OTDOA-SignalMeasurementInformation* as well as the IE *Sensor-MotionInformation* in IE *Sensor-ProvideLocationInformation*. + +### 6.5.1.7 OTDOA Capability Information + +#### – OTDOA-ProvideCapabilities + +The IE *OTDOA-ProvideCapabilities* is used by the target device to indicate its capability to support OTDOA and to provide its OTDOA positioning capabilities to the location server. + +``` +-- ASN1START + +OTDOA-ProvideCapabilities ::= SEQUENCE { + otdoa-Mode BIT STRING { + ue-assisted (0), + ue-assisted-NB-r14 (1), + ue-assisted-NB-TDD-r15 (2) } (SIZE (1..8)), + ..., + supportedBandListEUTRA SEQUENCE (SIZE (1..maxBands)) OF SupportedBandEUTRA OPTIONAL, + supportedBandListEUTRA-v9a0 SEQUENCE (SIZE (1..maxBands)) OF SupportedBandEUTRA-v9a0 OPTIONAL, + interFreqRSTDmeasurement-r10 ENUMERATED { supported } OPTIONAL, + additionalNeighbourCellInfoList-r10 ENUMERATED { supported } OPTIONAL, + prs-id-r14 ENUMERATED { supported } OPTIONAL, + tp-separation-via-muting-r14 ENUMERATED { supported } OPTIONAL, + additional-prs-config-r14 ENUMERATED { supported } OPTIONAL, + prs-based-tbs-r14 ENUMERATED { supported } OPTIONAL, + additionalPathsReport-r14 ENUMERATED { supported } OPTIONAL, + densePrsConfig-r14 ENUMERATED { supported } OPTIONAL, + maxSupportedPrsBandwidth-r14 ENUMERATED { n6, n15, n25, n50, n75, n100, ... } OPTIONAL, + prsOccGroup-r14 ENUMERATED { supported } OPTIONAL, + prsFrequencyHopping-r14 ENUMERATED { supported } OPTIONAL, + maxSupportedPrsConfigs-r14 ENUMERATED { c2, c3 } OPTIONAL, + periodicalReporting-r14 ENUMERATED { supported } OPTIONAL, + multiPrbNprs-r14 ENUMERATED { supported } OPTIONAL, + idleStateForMeasurements-r14 ENUMERATED { required } OPTIONAL, + numberOfRXantennas-r14 ENUMERATED { rx1, ... } OPTIONAL, + motionMeasurements-r15 ENUMERATED { supported } OPTIONAL, + interRAT-RSTDmeasurement-r15 ENUMERATED { supported } OPTIONAL, + scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupport-r17 OPTIONAL +} + +maxBands INTEGER ::= 64 + +SupportedBandEUTRA ::= SEQUENCE { + bandEUTRA INTEGER (1..maxFBI) +} + +SupportedBandEUTRA-v9a0 ::= SEQUENCE { + bandEUTRA-v9a0 INTEGER (maxFBI-Plus1..maxFBI2) OPTIONAL +} + +maxFBI INTEGER ::= 64 -- Maximum value of frequency band indicator +maxFBI-Plus1 INTEGER ::= 65 -- lowest value extended FBI range +maxFBI2 INTEGER ::= 256 -- highest value extended FBI range + +-- ASN1STOP +``` + +| OTDOA-ProvideCapabilities field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

otdoa-Mode
This field specifies the OTDOA mode(s) supported by the target device. This is represented by a bit string, with a one value at the bit position means the particular OTDOA mode is supported; a zero value means not supported. A zero-value in all bit positions in the bit string means OTDOA positioning method is not supported by the target device.
ue-assisted: Bit 0 indicates that the target device supports UE-assisted OTDOA and LTE PRS.
ue-assisted-NB: Bit 1 indicates that the target device supports UE-assisted OTDOA and NB-IoT NPRS.
ue-assisted-NB-TDD: Bit 2 indicates that the target device supports UE-assisted OTDOA and NB-IoT NPRS for TDD.

| +|

SupportedBandEUTRA
This field specifies the frequency bands for which the target device supports RSTD measurements. One entry corresponding to each supported E-UTRA band as defined in TS 36.101 [21]. In the case the target device includes bandEUTRA-v9a0, the target device shall set the corresponding entry of bandEUTRA (i.e. without suffix) to maxFBI.

| +|

interFreqRSTDmeasurement
This field, if present, indicates that the target device supports inter-frequency RSTD measurements within and between the frequency bands indicated in SupportedBandEUTRA.

| +|

additionalNeighbourCellInfoList
This field, if present, indicates that the target device supports up to 3×24 OTDOA-NeighbourCellInfoElement in OTDOA-NeighbourCellInfoList in OTDOA-ProvideAssistanceData without any restriction for the earfcn in each OTDOA-NeighbourCellInfoElement as specified in clause 6.5.1.2.

| +|

prs-id
This field, if present, indicates that the target device supports PRS generation based on the PRS-ID as specified in TS 36.211 [16] and support for TP-ID in OTDOA-ReferenceCellInfo and OTDOA-NeighbourCellInfoList.

| +|

tp-separation-via-muting
This field, if present, indicates that the target device supports RSTD measurements for cells which have associated transmission points (e.g., Remote Radio Heads) within the cell coverage and where these associated transmission points have the same physical cell identity as the associated cell, and where these transmission points are identified via a different muting pattern. The field also indicates support for TP-ID in OTDOA-ReferenceCellInfo and OTDOA-NeighbourCellInfoList.

| +|

additional-prs-config
This field, if present, indicates that the target device supports additional PRS configurations. The additional PRS configuration in PRS-Info IE comprise:
- support for prs-ConfigurationIndex > 2399;
- support for NPRS values in addition to 1, 2, 4 and 6 (add-numDL-Frames in PRS-Info);
- support for muting bit string lengths > 16 bits.

| +|

prs-based-tbs
This field, if present, indicates that the target device supports RSTD measurements for PRS-only TPs.

| +|

additionalPathsReport
This field, if present, indicates that the target device supports reporting of timing information for additional detected paths for RSTD reference and each neighbour cell.

| +|

densePrsConfig
This field, if present, indicates that the target device supports a subset of the additional PRS configurations associated with capability additional-prs-config which comprises:
- support for prs-ConfigurationIndex > 2404;
- support for NPRS values of 10, 20, 40, 80 and 160 (in addition to 1, 2, 4 and 6).
In the case additional-prs-config is present, this field is not present.

| +|

maxSupportedPrsBandwidth
This field, if present, indicates the maximum PRS bandwidth supported by the target device. Enumerated value n6 corresponds to 6 resource blocks, n15 to 15 resource blocks and so on. If this field is not present, the target device is assumed to support the PRS bandwidth associated with the target device type, which for LTE devices including Cat-M1/M2 is 100 resource blocks and for NB-IoT devices is 1 resource block.

| +|

prsOccGroup
This field, if present, indicates that the target device supports PRS occasion groups, which implies that each bit of a configured muting pattern applies per PRS occasion group.

| +|

prsFrequencyHopping
This field, if present, indicates that the target device supports PRS occasion frequency hopping, as specified in TS 36.211 [16].

| +|

maxSupportedPrsConfigs
This field, if present, indicates that the target device supports multiple PRS configurations per cell. Enumerated value c2 indicates support for up to 2 configurations; c3 indicates support for up to 3 configurations.

| +|

periodicalReporting
This field, if present, indicates that the target device supports periodicalReporting of RSTD measurements. If this field is absent, the location server may assume that the target device does not support periodicalReporting in CommonEsRequestLocationInformation.

| +|

multiPrbNprs
This field, if present, indicates that the target device supports NPRS configuration in more than one resource block (i.e., maxCarrier in PRS-Info-NB greater than 1).

| +|

idleStateForMeasurements
This field, if present, indicates that the target device requires idle state to perform RSTD measurements.

| + +| OTDOA-ProvideCapabilities field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| numberOfRXantennas
This field is not applicable to NB-IoT devices.
This field, if present, indicates the number of UE downlink receive antennas for RSTD measurements (see TS 36.133 [18]). Enumerated value rx1 indicates a single antenna receiver. If this field is absent, the target device is assumed to support two RX antennas for RSTD measurements. | +| motionMeasurements
This field, if present, indicates that the target device supports reporting of motion measurements ( delta-SFN and motionTimeSource ) in OTDOA-SignalMeasurementInformation . The presence of this field implies presence of sensor-MotionInformationSup in IE Sensor-ProvideCapabilities . | +| interRAT-RSTDmeasurement
This field, if present, indicates that the target device supports inter-RAT RSTD measurements (TS 38.215 [36]); i.e., E-UTRA RSTD measurements when the target device is served by an NR cell. | +| scheduledLocationRequestSupported
This field, if present, indicates that the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonEsRequestLocationInformation – and the time base(s) supported for the scheduled location time. | + +### 6.5.1.8 OTDOA Capability Information Request + +#### – *OTDOA-RequestCapabilities* + +The IE *OTDOA-RequestCapabilities* is used by the location server to request the capability of the target device to support OTDOA and to request OTDOA positioning capabilities from a target device. + +``` +-- ASN1START + +OTDOA-RequestCapabilities ::= SEQUENCE { + ... +} + +-- ASN1STOP +``` + +### 6.5.1.9 OTDOA Error Elements + +#### – *OTDOA-Error* + +The IE *OTDOA-Error* is used by the location server or target device to provide OTDOA error reasons to the target device or location server, respectively. + +``` +-- ASN1START + +OTDOA-Error ::= CHOICE { + locationServerErrorCauses OTDOA-LocationServerErrorCauses, + targetDeviceErrorCauses OTDOA-TargetDeviceErrorCauses, + ... +} + +-- ASN1STOP +``` + +#### – *OTDOA-LocationServerErrorCauses* + +The IE *OTDOA-LocationServerErrorCauses* is used by the location server to provide OTDOA error reasons to the target device. + +``` +-- ASN1START + +OTDOA-LocationServerErrorCauses ::= SEQUENCE { + cause ENUMERATED { undefined, + assistanceDataNotSupportedByServer, + assistanceDataSupportedButCurrentlyNotAvailableByServer, + ... + }, + ... +} +``` + +``` + +} +-- ASN1STOP + +``` + +### – *OTDOA-TargetDeviceErrorCauses* + +The IE *OTDOA-TargetDeviceErrorCauses* is used by the target device to provide OTDOA error reasons to the location server. + +``` + +-- ASN1START + +OTDOA-TargetDeviceErrorCauses ::= SEQUENCE { + cause ENUMERATED { undefined, + assistance-data-missing, + unableToMeasureReferenceCell, + unableToMeasureAnyNeighbourCell, + attemptedButUnableToMeasureSomeNeighbourCells, + ... + }, + ... +} + +-- ASN1STOP + +``` + +## 6.5.2 A-GNSS Positioning + +### 6.5.2.1 GNSS Assistance Data + +#### – *A-GNSS-ProvideAssistanceData* + +The IE *A-GNSS-ProvideAssistanceData* is used by the location server to provide assistance data to enable UE-based and UE-assisted A-GNSS. It may also be used to provide GNSS positioning specific error reasons. + +``` + +-- ASN1START + +A-GNSS-ProvideAssistanceData ::= SEQUENCE { + gnss-CommonAssistData GNSS-CommonAssistData OPTIONAL, -- Need ON + gnss-GenericAssistData GNSS-GenericAssistData OPTIONAL, -- Need ON + gnss-Error A-GNSS-Error OPTIONAL, -- Need ON + ..., + [[ + gnss-PeriodicAssistData-r15 GNSS-PeriodicAssistData-r15 OPTIONAL -- Cond CtrTrans + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CtrTrans | The field is mandatory present in the control transaction of a periodic assistance data delivery session as described in clauses 5.2.1a and 5.2.2a. Otherwise it is not present. | + +#### – *GNSS-CommonAssistData* + +The IE *GNSS-CommonAssistData* is used by the location server to provide assistance data which can be used for any GNSS. + +``` + +-- ASN1START + +GNSS-CommonAssistData ::= SEQUENCE { + gnss-ReferenceTime GNSS-ReferenceTime OPTIONAL, -- Need ON + gnss-ReferenceLocation GNSS-ReferenceLocation OPTIONAL, -- Need ON + gnss-IonosphericModel GNSS-IonosphericModel OPTIONAL, -- Need ON + gnss-EarthOrientationParameters GNSS-EarthOrientationParameters OPTIONAL, -- Need ON + ..., + [[ + +``` + +``` + + gnss-RTK-ReferenceStationInfo-r15 + GNSS-RTK-ReferenceStationInfo-r15 OPTIONAL, -- Need ON + gnss-RTK-CommonObservationInfo-r15 + GNSS-RTK-CommonObservationInfo-r15 OPTIONAL, -- Cond RTK + gnss-RTK-AuxiliaryStationData-r15 + GNSS-RTK-AuxiliaryStationData-r15 OPTIONAL -- Need ON + ]], + [[ + gnss-SSR-CorrectionPoints-r16 + GNSS-SSR-CorrectionPoints-r16 OPTIONAL -- Need ON + ]], + [[ + gnss-Integrity-ServiceParameters-r17 + GNSS-Integrity-ServiceParameters-r17 OPTIONAL, -- Need ON + gnss-Integrity-ServiceAlert-r17 + GNSS-Integrity-ServiceAlert-r17 OPTIONAL -- Need ON + ]], + [[ + gnss-los-nlos-GridPoints-r18 GNSS-LOS-NLOS-GridPoints-r18 OPTIONAL, -- Need ON + gnss-SSR-IOD-Update-r18 GNSS-SSR-IOD-Update-r18 OPTIONAL -- Need OR + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| RTK | The field is mandatory present if the IE GNSS-RTK-Observations is included in IE GNSS-GenericAssistData ; otherwise it is not present. | + +## – *GNSS-GenericAssistData* + +The IE *GNSS-GenericAssistData* is used by the location server to provide assistance data for a specific GNSS. The specific GNSS for which the provided assistance data are applicable is indicated by the IE *GNSS-ID* and (if applicable) by the IE *SBAS-ID*. Assistance for up to 16 GNSSs can be provided. + +``` + +-- ASN1START + +GNSS-GenericAssistData ::= SEQUENCE (SIZE (1..16)) OF GNSS-GenericAssistDataElement + +GNSS-GenericAssistDataElement ::= SEQUENCE { + gnss-ID GNSS-ID, + sbas-ID SBAS-ID OPTIONAL, -- Cond GNSS-ID-SBAS + gnss-TimeModels GNSS-TimeModelList OPTIONAL, -- Need ON + gnss-DifferentialCorrections GNSS-DifferentialCorrections OPTIONAL, -- Need ON + gnss-NavigationModel GNSS-NavigationModel OPTIONAL, -- Need ON + gnss-RealTimeIntegrity GNSS-RealTimeIntegrity OPTIONAL, -- Need ON + gnss-DataBitAssistance GNSS-DataBitAssistance OPTIONAL, -- Need ON + gnss-AcquisitionAssistance GNSS-AcquisitionAssistance OPTIONAL, -- Need ON + gnss-Almanac GNSS-Almanac OPTIONAL, -- Need ON + gnss-UTC-Model GNSS-UTC-Model OPTIONAL, -- Need ON + gnss-AuxiliaryInformation GNSS-AuxiliaryInformation OPTIONAL, -- Need ON + ..., + [[ + bds-DifferentialCorrections-r12 + BDS-DifferentialCorrections-r12 OPTIONAL, -- Cond GNSS-ID-BDS + bds-GridModel-r12 BDS-GridModelParameter-r12 OPTIONAL -- Cond GNSS-ID-BDS + ]], + [[ + gnss-RTK-Observations-r15 GNSS-RTK-Observations-r15 OPTIONAL, -- Need ON + glo-RTK-BiasInformation-r15 GLO-RTK-BiasInformation-r15 OPTIONAL, -- Cond GNSS-ID-GLO + gnss-RTK-MAC-CorrectionDifferences-r15 + GNSS-RTK-MAC-CorrectionDifferences-r15 + OPTIONAL, -- Need ON + gnss-RTK-Residuals-r15 GNSS-RTK-Residuals-r15 OPTIONAL, -- Need ON + gnss-RTK-FKP-Gradients-r15 GNSS-RTK-FKP-Gradients-r15 OPTIONAL, -- Need ON + gnss-SSR-OrbitCorrections-r15 + GNSS-SSR-OrbitCorrections-r15 OPTIONAL, -- Need ON + gnss-SSR-ClockCorrections-r15 + GNSS-SSR-ClockCorrections-r15 OPTIONAL, -- Need ON + gnss-SSR-CodeBias-r15 GNSS-SSR-CodeBias-r15 OPTIONAL -- Need ON + ]], + [[ + gnss-SSR-URA-r16 GNSS-SSR-URA-r16 OPTIONAL -- Need ON + +``` + +``` + +gnss-SSR-PhaseBias-r16 GNSS-SSR-PhaseBias-r16 OPTIONAL, -- Need ON +gnss-SSR-TEC-Correction-r16 GNSS-SSR-TEC-Correction-r16 + OPTIONAL, -- Need ON +gnss-SSR-GriddedCorrection-r16 GNSS-SSR-GriddedCorrection-r16 + OPTIONAL, -- Need ON +navic-DifferentialCorrections-r16 NavIC-DifferentialCorrections-r16 + OPTIONAL, -- Cond GNSS-ID-NavIC +navic-GridModel-r16 NavIC-GridModelParameter-r16 + OPTIONAL -- Cond GNSS-ID-NavIC + ]], + [[ + gnss-SSR-OrbitCorrectionsSet2-r17 GNSS-SSR-OrbitCorrectionsSet2-r17 + OPTIONAL, -- Need ON + gnss-SSR-ClockCorrectionsSet2-r17 GNSS-SSR-ClockCorrectionsSet2-r17 + OPTIONAL, -- Need ON + gnss-SSR-URA-Set2-r17 GNSS-SSR-URA-Set2-r17 + OPTIONAL -- Need ON + ]], + [[ + gnss-LOS-NLOS-GriddedIndications-r18 GNSS-LOS-NLOS-GriddedIndications-r18 + OPTIONAL, -- Need ON + gnss-SSR-SatellitePCVResiduals-r18 GNSS-SSR-SatellitePCVResiduals-r18 + OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------| +| GNSS-ID-SBAS | The field is mandatory present if the GNSS-ID = sbas ; otherwise it is not present. | +| GNSS-ID-BDS | The field may be present if the GNSS-ID = bds ; otherwise it is not present. | +| GNSS-ID-GLO | The field is optionally present, need ON, if the GNSS ID = glonass ; otherwise it is not present. | +| GNSS-ID-NAVIC | The field is optionally present, need ON, if the GNSS-ID = navic ; otherwise it is not present | + +## – GNSS-PeriodicAssistData + +The IE *GNSS-PeriodicAssistData* is used by the location server to provide control parameters for a periodic assistance data delivery session (e.g., interval and duration) to the target device. + +NOTE: Omission of a particular assistance data type field in IE *GNSS-PeriodicAssistData* means that the location server does not provide this assistance data type in a data transaction of a periodic assistance data delivery session, as described in clauses 5.2.1a and 5.2.2a. Inclusion of no assistance data type fields in IE *GNSS-PeriodicAssistData* means that a periodic assistance data delivery session is terminated. + +``` + +-- ASN1START + +GNSS-PeriodicAssistData-r15 ::= SEQUENCE { + gnss-RTK-PeriodicObservations-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + glo-RTK-PeriodicBiasInformation-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + gnss-RTK-MAC-PeriodicCorrectionDifferences-r15 + GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + gnss-RTK-PeriodicResiduals-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + gnss-RTK-FKP-PeriodicGradients-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + gnss-SSR-PeriodicOrbitCorrections-r15 + GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + gnss-SSR-PeriodicClockCorrections-r15 + GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + gnss-SSR-PeriodicCodeBias-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + ... + [[ + gnss-SSR-PeriodicURA-r16 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + gnss-SSR-PeriodicPhaseBias-r16 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + gnss-SSR-PeriodicTEC-Correction-r16 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + gnss-SSR-PeriodicGriddedCorrection-r16 GNSS-PeriodicControlParam-r15 OPTIONAL -- Need ON + ]], + [[ + gnss-Integrity-PeriodicServiceAlert-r17 GNSS-PeriodicControlParam-r15 OPTIONAL -- Need ON + ]], + [[ + gnss-SSR-PeriodicOrbitCorrectionsSet2-r17 + GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + +``` + +``` + +gnss-SSR-PeriodicClockCorrectionsSet2-r17 + gnss-SSR-PeriodicURA-Set2-r17 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Need ON + [[ + gnss-SSR-PeriodicIOD-Update-r18 GNSS-PeriodicControlParam-r15 OPTIONAL -- Need OR + ]] +} + +-- ASN1STOP + +``` + +## 6.5.2.2 GNSS Assistance Data Elements + +### — *GNSS-ReferenceTime* + +The IE *GNSS-ReferenceTime* is used by the location server to provide the GNSS specific system time with uncertainty and the relationship between GNSS system time and network air-interface timing of the eNodeB/NodeB/BTS transmission in the reference cell. + +If the IE *networkTime* is present, the IEs *gnss-SystemTime* and *networkTime* provide a valid relationship between GNSS system time and air-interface network time, as seen at the approximate location of the target device, i.e. the propagation delay from the gNB/ng-eNB/eNodeB/NodeB/BTS to the target device is compensated for by the location server. Depending on implementation, the relation between GNSS system time and air-interface network time may have varying accuracy. The uncertainty of this timing relation is provided in the IE *referenceTimeUnc*. If the propagation delay from the eNodeB/NodeB/BTS to the target device is not accurately known, the location server uses the best available approximation of the propagation delay and take the corresponding delay uncertainty into account in the calculation of the IE *referenceTimeUnc*. + +If the IE *networkTime* is not present, the IE *gnssSystemTime* is an estimate of current GNSS system time at time of reception of the IE *GNSS-ReferenceTime* by the target device. The location server should achieve an accuracy of +/- 3 seconds for this estimate including allowing for the transmission delay between the location server and the target device. Note that the target device should further compensate *gnss-SystemTime* for the time between the reception of *GNSS-ReferenceTime* and the time when the *gnss-SystemTime* is used. + +The location server provides a value for the *gnss-TimeID* only for GNSSs supported by the target device. + +The IE *GNSS-ReferenceTimeForOneCell* can be provided multiple times (up to 16) to provide fine time assistance for several (neighbour) cells. + +``` + +-- ASN1START + +GNSS-ReferenceTime ::= SEQUENCE { + gnss-SystemTime GNSS-SystemTime, + referenceTimeUnc INTEGER (0..127) OPTIONAL, -- Cond noFTA + gnss-ReferenceTimeForCells SEQUENCE (SIZE (1..16)) OF + GNSS-ReferenceTimeForOneCell OPTIONAL, -- Need ON + ... +} + +GNSS-ReferenceTimeForOneCell ::= SEQUENCE { + networkTime NetworkTime, + referenceTimeUnc INTEGER (0..127), + bsAlign ENUMERATED {true} OPTIONAL, + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------| +| noFTA | The field may be present if gnss-ReferenceTimeForCells is absent; otherwise it is not present. | + +| GNSS-ReferenceTime field descriptions | +|-------------------------------------------------------------------------------------| +| gnss-SystemTime
This field provides the specific GNSS system time. | + +| GNSS-ReferenceTime field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| networkTime
This field specifies the cellular network time at the epoch corresponding to gnss-SystemTime . | +| referenceTimeUnc
This field provides the accuracy of the relation between gnssSystemTime and networkTime time if IE networkTime is provided. When IE networkTime is not provided, this field can be included to provide the accuracy of the provided gnssSystemTime .
If GNSS TOD is the given GNSS time, then the true GNSS time, corresponding to the provided network time as observed at the target device location, lies in the interval [GNSS TOD - referenceTimeUnc , GNSS TOD + referenceTimeUnc ].
The uncertainty r , expressed in microseconds, is mapped to a number K , with the following formula:
$r = C * ((1+x)^K - 1)$ with C = 0.5 and x = 0.14. To encode any higher value of uncertainty than that corresponding in the above formula to K =127, the same value, K =127, shall also be used. The uncertainty is then coded on 7 bits, as the binary encoding of K . Example values for the referenceTimeUnc Format: see table K to uncertainty relation below. | +| bsAlign
This flag, if present, indicates that the transmission timings of all cells sharing, depending on the RAT, the same carrier frequency and Tracking Area/Location Area/Routing Area as the cell indicated, are frame aligned. This information allows the target device to derive the GNSS - cellular time relation for any of these cells based on the timing relation information provided in GNSS-ReferenceTime . The flag should be set consistently in all these cells. This flag does not guarantee SFN alignment. | + +### K to uncertainty relation + +| Value of K | Value of uncertainty | +|------------|----------------------| +| 0 | 0 nanoseconds | +| 1 | 70 nanoseconds | +| 2 | 149.8 nanoseconds | +| - | - | +| 50 | 349.62 microseconds | +| - | - | +| 127 | ≥ 8.43 seconds | + +## GNSS-SystemTime + +``` +-- ASN1START +GNSS-SystemTime ::= SEQUENCE { + gnss-TimeID GNSS-ID, + gnss-DayNumber INTEGER (0..32767), + gnss-TimeOfDay INTEGER (0..86399), + gnss-TimeOfDayFrac-msec INTEGER (0..999) OPTIONAL, -- Need ON + notificationOfLeapSecond BIT STRING (SIZE(2)) OPTIONAL, -- Cond gnss-TimeID-glonass + gps-TOW-Assist GPS-TOW-Assist OPTIONAL, -- Cond gnss-TimeID-gps + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------------|-----------------------------------------------------------------------------------------| +| gnss-TimeID-glonass | The field may be present if gnss-TimeID =`glonass'; otherwise it is not present. | +| gnss-TimeID-gps | The field may be present if gnss-TimeID =`gps'; otherwise it is not present. | + +| GNSS-SystemTime field descriptions | +|-------------------------------------------------------------------------------------------------------| +| gnss-TimeID
This field specifies the GNSS for which the GNSS-SystemTime is provided. | + +| GNSS-SystemTime field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-DayNumber
This field specifies the sequential number of days (with day count starting at 0) from the origin of the GNSS System Time as follows:
GPS, QZSS, SBAS – Days from January 6 th 1980 00:00:00 UTC (USNO);
Galileo – Days from Galileo System Time (GST) start epoch, defined as 13 seconds before midnight between 21 st August and 22 nd August 1999; i.e., GST was equal to 13 seconds at August 22 nd 1999 00:00:00 UTC;
GLONASS – Days from December 31 st 1995 21:00:00 UTC (SU), which is local UTC Moscow January 1 st 1996 00:00:00, defined as UTC(SU) + 3 hours in [9];
BDS – Days from January 1 st 2006 00:00:00 UTC (NTSC).
NavIC – Days from NavIC System Time start epoch, defined as 13 seconds before midnight between 21 st August and 22 nd August 1999; i.e., NavIC System Time was equal to 00:00:00 at August 21 st , 1999 23:55:47 UTC (BIPM). | +| gnss-TimeOfDay
This field specifies the integer number of seconds from the GNSS day change. | +| gnss-TimeOfDayFrac-msec
This field specifies the fractional part of the gnssTimeOfDay field in 1-milli-seconds resolution. The total GNSS TOD is gnss-TimeOfDay + gnssTimeOfDayFrac-msec . | +| notificationOfLeapSecond
This field specifies the notification of forthcoming leap second correction, as defined by parameter KP in [9, Table 4.7]. | +| gps-TOW-Assist
This field contains several fields in the Telemetry (TLM) Word and Handover Word (HOW) that are currently being broadcast by the respective GPS satellites. Combining this information with GPS TOW enables the target device to know the entire 1.2-second (60-bit) pattern of TLM and HOW that is transmitted at the start of each six-second NAV subframe by the particular GPS satellite. | + +## GPS-TOW-Assist + +``` +-- ASN1START + +GPS-TOW-Assist ::= SEQUENCE (SIZE(1..64)) OF GPS-TOW-AssistElement + +GPS-TOW-AssistElement ::= SEQUENCE { + satelliteID INTEGER (1..64), + tlmWord INTEGER (0..16383), + antiSpoof INTEGER (0..1), + alert INTEGER (0..1), + tlmRsvdBits INTEGER (0..3), + ... +} + +-- ASN1STOP +``` + +| GPS-TOW-Assist field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| satelliteID
This field identifies the satellite for which the GPS-TOW-Assist is applicable. This field is identical to the GPS PRN Signal No. defined in [4]. | +| tlmWord
This field contains a 14-bit value representing the Telemetry Message (TLM) being broadcast by the GPS satellite identified by the particular satelliteID , with the MSB occurring first in the satellite transmission, as defined in [4]. | +| antiSpoof
This field contains the Anti-Spoof flag that is being broadcast by the GPS satellite identified by satelliteID , as defined in [4]. | +| alert
This field contains the Alert flag that is being broadcast by the GPS satellite identified by satelliteID , as defined in [4]. | +| tlmRsvdBits
This field contains the two reserved bits in the TLM Word being broadcast by the GPS satellite identified by satelliteID , with the MSB occurring first in the satellite transmission, as defined in [4]. | + +## NetworkTime + +``` +-- ASN1START + +NetworkTime ::= SEQUENCE { + secondsFromFrameStructureStart INTEGER (0..12533), + fractionalSecondsFromFrameStructureStart INTEGER (0..3999999), +} +``` + +``` + +frameDrift INTEGER (-64..63) OPTIONAL, -- Cond GNSSsynch +cellID CHOICE { + eUTRA SEQUENCE { + physCellId INTEGER (0..503), + cellGlobalIdEUTRA CellGlobalIdEUTRA-AndUTRA OPTIONAL, -- Need ON + earfcn ARFCN-ValueEUTRA, + ..., + [[ earfcn-v9a0 ARFCN-ValueEUTRA-v9a0 OPTIONAL -- Cond EARFCN-max + ]] + }, + uTRA SEQUENCE { + mode CHOICE { + fdd SEQUENCE { + primary-CPICH-Info INTEGER (0..511), + ..., + }, + tdd SEQUENCE { + cellParameters INTEGER (0..127), + ..., + } + }, + cellGlobalIdUTRA CellGlobalIdEUTRA-AndUTRA OPTIONAL, -- Need ON + uarfcn ARFCN-ValueUTRA, + ..., + }, + gSM SEQUENCE { + bcchCarrier INTEGER (0..1023), + bsic INTEGER (0..63), + cellGlobalIdGERAN CellGlobalIdGERAN OPTIONAL, -- Need ON + ..., + }, + nBIoT-r14 SEQUENCE { + nbPhysCellId-r14 INTEGER (0..503), + nbCellGlobalId-r14 ECGI OPTIONAL, -- Need ON + nbCarrierFreq-r14 CarrierFreq-NB-r14, + ..., + }, + nr-r15 SEQUENCE { + nrPhysCellId-r15 INTEGER (0..1007), + nrCellGlobalID-r15 NCGI-r15 OPTIONAL, -- Need ON + nrARFCN-r15 ARFCN-ValueNR-r15, + ..., + }, + ..., + } + } +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| EARFCN-max | The field is mandatory present if the corresponding earfcn (i.e. without suffix) is set to maxEARFCN . Otherwise the field is not present. | +| GNSSsynch | The field is present and set to 0 if NetworkTime is synchronized to gnss-SystemTime ; otherwise the field is optionally present, need OR. | + +| NetworkTime field descriptions | | +|--------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| secondsFromFrameStructureStart | This field specifies the number of seconds from the beginning of the longest frame structure in the corresponding air interface.
In the case of E-UTRA, the SFN cycle length is 10.24 seconds.
In the case of UTRA, the SFN cycle length is 40.96 seconds.
In the case of GSM, the hyperframe length is 12533.76 seconds.
In the case of NB-IoT, the Hyper-SFN cycle lengths is 10485.76 seconds.
In the case of NR, the SFN cycle length is 10.24 seconds. | +| fractionalSecondsFromFrameStructureStart | This field specifies the fractional part of the secondsFromFrameStructureStart in 250 ns resolution.
The total time since the particular frame structure start is secondsFromFrameStructureStart + fractionalSecondsFromFrameStructureStart | +| frameDrift | This field specifies the drift rate of the GNSS-network time relation with scale factor $2^{-30}$ seconds/second, in the range from -5.9605e-8 to +5.8673e-8 sec/sec. | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellID
This field specifies the cell for which the GNSS-network time relation is provided. | +| physCellId
This field specifies the physical cell identity of the reference cell (E-UTRA), as defined in TS 36.331 [12], for which the GNSS network time relation is provided. | +| cellGlobalIdEUTRA
This field specifies the Evolved Cell Global Identifier (ECGI), the globally unique identity of a cell in E-UTRA, of the reference cell for the GNSS-network time relation, as defined in TS 36.331 [12]. | +| earfcn
This field specifies E-ARFCN of the reference cell for the GNSS-network time relation (E-UTRA). In the case the server includes earfcn-v9a0 , the server shall set the corresponding earfcn (i.e. without suffix) to maxEARFCN . | +| primary-CPICH-Info
This field specifies the physical cell identity of the reference cell (UTRA) for the GNSS-network time relation, as defined in TS 25.331 [13]. | +| cellParameters
This field specifies the physical cell identity of the reference cell (UTRA) for the GNSS-network time relation, as defined in TS 25.331 [13]. | +| cellGlobalIdUTRA
The filed specifies the global UTRAN Cell Identifier, the globally unique identity of a cell in UTRA, of the reference cell for the GNSS-network time relation, as defined in TS 25.331 [13]. | +| uarfcn
This field specifies ARFCN of the reference cell for the GNSS-network time relation (UTRA). | +| bcchCarrier
This field specifies the absolute GSM RF channel number of the BCCH of the reference base station (GERAN) for the GNSS-network time relation, as defined in TS 44.031 [14]. | +| bsic
This field specifies the Base Station Identity Code of the reference base station (GERAN) for the GNSS-network time relation, as defined in TS 44.031 [14]. | +| cellGlobalIdGERAN
This field specifies the Cell Global Identification (CGI), the globally unique identity of a cell in GERAN, of the reference base station for the GNSS-network time relation. | +| nbPhysCellId
This field specifies the narrowband physical layer cell identity of the NB-IoT reference cell, as defined in TS 36.331 [12], for which the GNSS network time relation is provided. | +| nbCellGlobalId
This field specifies the global cell identifier of the NB-IoT reference cell for which the GNSS-network time relation is provided, as defined in TS 36.331 [12]. | +| nbCarrierFreq
This field specifies the carrier frequency of the NB-IoT reference cell for which the GNSS-network time relation is provided. | +| nrPhysCellId
This field specifies the physical cell identity of the reference cell (NR), as defined in TS 38.331 [35], for which the GNSS network time relation is provided. | +| nrCellGlobalID
This field specifies the NR Cell Global Identifier (NCGI) of the reference cell (NR) for the GNSS-network time relation, as defined in TS 38.331 [35]. | +| nrARFCN
This field specifies NR-ARFCN of the reference cell (NR) for the GNSS-network time relation. | + +## – GNSS-ReferenceLocation + +The IE *GNSS-ReferenceLocation* is used by the location server to provide the target device with a-priori knowledge of its location in order to improve GNSS receiver performance. The IE *GNSS-ReferenceLocation* is provided in WGS-84 reference system. + +``` +-- ASN1START +GNSS-ReferenceLocation ::= SEQUENCE { + threeDlocation EllipsoidPointWithAltitudeAndUncertaintyEllipsoid, + ... +} +-- ASN1STOP +``` + +## – *GNSS-IonosphericModel* + +The IE *GNSS-IonosphericModel* is used by the location server to provide parameters to model the propagation delay of the GNSS signals through the ionosphere. Proper use of these fields allows a single-frequency GNSS receiver to remove parts of the ionospheric delay from the pseudorange measurements. Three Ionospheric Models are supported: The Klobuchar model as defined in [4], the NeQuick model as defined in [8], and the klobucharModel2 as defined in [39]. + +``` +-- ASN1START + +GNSS-IonosphericModel ::= SEQUENCE { + klobucharModel KlobucharModelParameter OPTIONAL, -- Need ON + neQuickModel NeQuickModelParameter OPTIONAL, -- Need ON + ..., + [[ klobucharModel2-r16 KlobucharModel2Parameter-r16 OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP +``` + +## – *KlobucharModelParameter* + +``` +-- ASN1START + +KlobucharModelParameter ::= SEQUENCE { + dataID BIT STRING (SIZE (2)), + alfa0 INTEGER (-128..127), + alfa1 INTEGER (-128..127), + alfa2 INTEGER (-128..127), + alfa3 INTEGER (-128..127), + beta0 INTEGER (-128..127), + beta1 INTEGER (-128..127), + beta2 INTEGER (-128..127), + beta3 INTEGER (-128..127), + ... +} + +-- ASN1STOP +``` + +***KlobucharModelParamater field descriptions*** + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dataID | When dataID has the value '11' it indicates that the parameters have been generated by QZSS, and the parameters have been specialized and are applicable within the area defined in [7]. When dataID has the value '01' it indicates that the parameters have been generated by BDS, and UE shall use these parameters according to the description given in 5.2.4.7 in [23], [50]. When the dataID has the value '10', it indicates that the parameters have been generated by NavIC, and UE shall use these parameters according to the description given in [38]. When dataID has the value '00' it indicates the parameters are applicable worldwide [4], [7]. | +| alfa0 | This field specifies the $\alpha_0$ parameter of the Klobuchar model, as specified in [4], [23], [38], [50].
Scale factor $2^{-30}$ seconds. | +| alfa1 | This field specifies the $\alpha_1$ parameter of the Klobuchar model, as specified in [4], [23], [38], [50].
Scale factor $2^{-27}$ seconds/semi-circle. | +| alfa2 | This field specifies the $\alpha_2$ parameter of the Klobuchar model, as specified in [4], [23], [38], [50].
Scale factor $2^{-24}$ seconds/semi-circle 2 . | +| alfa3 | This field specifies the $\alpha_3$ parameter of the Klobuchar model, as specified in [4], [23], [38], [50].
Scale factor $2^{-24}$ seconds/semi-circle 3 . | +| beta0 | This field specifies the $\beta_0$ parameter of the Klobuchar model, as specified in [4], [23], [38], [50].
Scale factor $2^{11}$ seconds. | +| beta1 | This field specifies the $\beta_1$ parameter of the Klobuchar model, as specified in [4], [23], [38], [50].
Scale factor $2^{14}$ seconds/semi-circle. | + +| KlobucharModelParamater field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| beta2
This field specifies the $\beta_2$ parameter of the Klobuchar model, as specified in [4], [23], [38], [50].
Scale factor $2^{16}$ seconds/semi-circle 2 . | +| beta3
This field specifies the $\beta_3$ parameter of the Klobuchar model, as specified in [4], [23], [38], [50].
Scale factor $2^{16}$ seconds/semi-circle 3 . | + +### — KlobucharModel2Parameter + +``` +-- ASN1START + +KlobucharModel2Parameter-r16 ::= SEQUENCE { + alfa1-r16 INTEGER (0..1023), + alfa2-r16 INTEGER (-128..127), + alfa3-r16 INTEGER (0..255), + alfa4-r16 INTEGER (0..255), + alfa5-r16 INTEGER (0..255), + alfa6-r16 INTEGER (-128..127), + alfa7-r16 INTEGER (-128..127), + alfa8-r16 INTEGER (-128..127), + alfa9-r16 INTEGER (-128..127), + ... +} + +-- ASN1STOP +``` + +| KlobucharModel2Parameter field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alfa1
This field specifies the $\alpha_1$ parameter of the Klobuchar model, as specified in 7.8.1 in [39], [49].
Scale factor $2^{-3}$ TECU. | +| alfa2
This field specifies the $\alpha_2$ parameter of the Klobuchar model, as specified in 7.8.1 in [39], [49].
Scale factor $2^{-3}$ TECU. | +| alfa3
This field specifies the $\alpha_3$ parameter of the Klobuchar model, as specified in 7.8.1 in [39], [49].
Scale factor $2^{-3}$ TECU. | +| alfa4
This field specifies the $\alpha_4$ parameter of the Klobuchar model, as specified in 7.8.1 in [39], [49].
Scale factor $2^{-3}$ TECU. | +| alfa5
This field specifies the $\alpha_5$ parameter of the Klobuchar model, as specified in 7.8.1 in [39], [49].
Scale factor $-2^{-3}$ TECU. | +| alfa6
This field specifies the $\alpha_6$ parameter of the Klobuchar model, as specified in 7.8.1 in [39], [49].
Scale factor $2^{-3}$ TECU. | +| alfa7
This field specifies the $\alpha_7$ parameter of the Klobuchar model, as specified in 7.8.1 in [39], [49].
Scale factor $2^{-3}$ TECU. | +| alfa8
This field specifies the $\alpha_8$ parameter of the Klobuchar model, as specified in 7.8.1 in [39], [49].
Scale factor $2^{-3}$ TECU. | +| alfa9
This field specifies the $\alpha_9$ parameter of the Klobuchar model, as specified in 7.8.1 in [39], [49].
Scale factor $2^{-3}$ TECU. | + +### — NeQuickModelParameter + +``` +-- ASN1START + +NeQuickModelParameter ::= SEQUENCE { + ai0 INTEGER (0..2047), + ai1 INTEGER (-1024..1023), + ai2 INTEGER (-8192..8191), + ionoStormFlag1 INTEGER (0..1) OPTIONAL, -- Need OP + ionoStormFlag2 INTEGER (0..1) OPTIONAL, -- Need OP +} +``` + +``` + + ionoStormFlag3 INTEGER (0..1) OPTIONAL, -- Need OP + ionoStormFlag4 INTEGER (0..1) OPTIONAL, -- Need OP + ionoStormFlag5 INTEGER (0..1) OPTIONAL, -- Need OP + ... +} + +-- ASN1STOP + +``` + +| NeQuickModelParameter field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ai0
Effective Ionisation Level 1 st order parameter.
Scale factor 2 -2 Solar Flux Units (SFUs), [8] clause 5.1.6. | +| ai1
Effective Ionisation Level 2 nd order parameter.
Scale factor 2 -8 Solar Flux Units/degree, [8] clause 5.1.6. | +| ai2
Effective Ionisation Level 3 rd order parameter.
Scale factor 2 -15 Solar Flux Units/degree 2 , [8] clause 5.1.6. | +| ionoStormFlag1, ionoStormFlag2, ionoStormFlag3, ionoStormFlag4, ionoStormFlag5
These fields specify the ionosphere disturbance flags (1,...,5) for five different regions as described in [8], clause 5.1.6. If the ionosphere disturbance flag for a region is not present the target device shall treat the ionosphere disturbance condition as unknown. | + +## – GNSS-EarthOrientationParameters + +The IE *GNSS-EarthOrientationParameters* is used by the location server to provide parameters to construct the ECEF and ECI coordinate transformation as defined in [4]. The IE *GNSS-EarthOrientationParameters* indicates the relationship between the Earth's rotational axis and WGS-84 reference system. + +``` + +-- ASN1START + +GNSS-EarthOrientationParameters ::= SEQUENCE { + teop INTEGER (0..65535), + pmX INTEGER (-1048576..1048575), + pmXdot INTEGER (-16384..16383), + pmY INTEGER (-1048576..1048575), + pmYdot INTEGER (-16384..16383), + deltaUT1 INTEGER (-1073741824..1073741823), + deltaUT1dot INTEGER (-262144..262143), + ... +} + +-- ASN1STOP + +``` + +| GNSS-EarthOrientationParameters field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| teop
This field specifies the EOP data reference time in seconds, as specified in [4], [39].
Scale factor 2 4 seconds. | +| pmX
This field specifies the X-axis polar motion value at reference time in arc-seconds, as specified in [4], [39], [49].
Scale factor 2 -20 arc-seconds. | +| pmXdot
This field specifies the X-axis polar motion drift at reference time in arc-seconds/day, as specified in [4], [39], [49].
Scale factor 2 -21 arc-seconds/day. | +| pmY
This field specifies the Y-axis polar motion value at reference time in arc-seconds, as specified in [4], [39], [49].
Scale factor 2 -20 arc-seconds. | +| pmYdot
This field specifies the Y-axis polar motion drift at reference time in arc-seconds/day, as specified in [4], [39], [49].
Scale factor 2 -21 arc-seconds/day. | +| deltaUT1
This field specifies the UT1-UTC difference at reference time in seconds, as specified in [4], [39], [49].
Scale factor 2 -24 seconds. | +| deltaUT1dot
This field specifies the Rate of UT1-UTC difference at reference time in seconds/day, as specified in [4], [39], [49].
Scale factor 2 -25 seconds/day. | + +## GNSS-RTK-ReferenceStationInfo + +The IE *GNSS-RTK-ReferenceStationInfo* is used by the location server to provide the Earth-centered, Earth-fixed (ECEF) coordinates of the antenna reference point (ARP) of the stationary reference station for which the *GNSS-RTK-Observations* assistance data are provided together with reference station antenna description. + +The parameters provided in IE *GNSS-RTK-ReferenceStationInfo* are used as specified for message type 1006, 1033 and 1032 in [30]. + +``` +-- ASN1START + +GNSS-RTK-ReferenceStationInfo-r15 ::= SEQUENCE { + referenceStationID-r15 GNSS-ReferenceStationID-r15, + referenceStationIndicator-r15 ENUMERATED {physical, non-physical}, + antenna-reference-point-ECEF-X-r15 INTEGER (-137438953472..137438953471), + antenna-reference-point-ECEF-Y-r15 INTEGER (-137438953472..137438953471), + antenna-reference-point-ECEF-Z-r15 INTEGER (-137438953472..137438953471), + antennaHeight-r15 INTEGER (0..65535) OPTIONAL, -- Need ON + antennaDescription-r15 AntennaDescription-r15 OPTIONAL, -- Need ON + antenna-reference-point-unc-r15 AntennaReferencePointUnc-r15 OPTIONAL, -- Need ON + physical-reference-station-info-r15 PhysicalReferenceStationInfo-r15 OPTIONAL, -- Cond NP + ... + [[ + equalIntegerAmbiguityLevel-r16 EqualIntegerAmbiguityLevel-r16 OPTIONAL -- Need ON + ]] +} + +AntennaDescription-r15 ::= SEQUENCE { + antennaDescriptor-r15 VisibleString (SIZE (1..256)), + antennaSetUpID-r15 ENUMERATED { non-zero } OPTIONAL, -- Need OP + ... +} + +AntennaReferencePointUnc-r15 ::= SEQUENCE { + uncertainty-X-r15 INTEGER (0..255), + confidence-X-r15 INTEGER (0..100), + uncertainty-Y-r15 INTEGER (0..255), + confidence-Y-r15 INTEGER (0..100), + uncertainty-Z-r15 INTEGER (0..255), + confidence-Z-r15 INTEGER (0..100), + ... +} + +PhysicalReferenceStationInfo-r15 ::= SEQUENCE { + physicalReferenceStationID-r15 GNSS-ReferenceStationID-r15, + physical-ARP-ECEF-X-r15 INTEGER (-137438953472..137438953471), + physical-ARP-ECEF-Y-r15 INTEGER (-137438953472..137438953471), + physical-ARP-ECEF-Z-r15 INTEGER (-137438953472..137438953471), + physical-ARP-unc-r15 AntennaReferencePointUnc-r15 OPTIONAL, -- Need ON + ... +} + +EqualIntegerAmbiguityLevel-r16 ::= CHOICE { + allReferenceStations-r16 NULL, + referenceStationList-r16 ReferenceStationList-r16 +} + +ReferenceStationList-r16 ::= SEQUENCE (SIZE(1..16)) OF GNSS-ReferenceStationID-r15 + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| NP | The field is optionally present, need ON, if the referenceStationIndicator has the value 'non-physical'; otherwise it is not present. | + +| GNSS-RTK-ReferenceStationInfo field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| referenceStationID
The Reference Station ID is determined by the RTK service provider. | +| referenceStationIndicator
This field specifies type of reference station. Enumerated value physical indicates a real, physical reference station; value non-physical indicates a non-physical or computed reference station. | +| antenna-reference-point-ECEF-X
This field specifies the antenna reference point X-coordinate in the World Geodetic System 1984 (WGS 84) datum. Scale factor 0.0001 m; range $\pm 13,743,895.3471$ m. | +| antenna-reference-point-ECEF-Y
This field specifies the antenna reference point Y-coordinate in the World Geodetic System 1984 (WGS 84) datum. Scale factor 0.0001 m; range $\pm 13,743,895.3471$ m. | +| antenna-reference-point-ECEF-Z
This field specifies the antenna reference point Z-coordinate in the World Geodetic System 1984 (WGS 84) datum. Scale factor 0.0001 m; range $\pm 13,743,895.3471$ m. | +| antennaHeight
This field specifies the height of the Antenna Reference Point above the marker used in the survey campaign. Scale factor 0.0001 m; range 0–6.5535 m. | +| antennaDescriptor
This field provides an ASCII descriptor of the reference station antenna using IGS naming convention [31]. The descriptor can be used to look up model specific phase centre corrections of that antenna. | +| antennaSetUpID
This field, if present, indicates that the standard IGS Model is not valid ( $\neq 0$ [30]). If this field is absent the standard IGS Model is valid ('0 = Use standard IGS Model' [30]). | +| antenna-reference-point-unc
This field specifies the uncertainty of the ARP coordinates. uncertainty-X , uncertainty-Y , and uncertainty-Z correspond to the encoded high accuracy uncertainty of the X, Y, and Z-coordinate, respectively, as defined in TS 23.032 [15]. confidence-X , confidence-Y , and confidence-Z corresponds to confidence as defined in TS 23.032 [15]. | +| physical-reference-station-info
This field provides the earth-centred, earth-fixed (ECEF) coordinates of the antenna reference point (ARP) for the real (or "physical") reference station used. This field may be used in the case of the non-physical reference station approach to allow the target device to refer baseline vectors to a physical reference rather than to a non-physical reference without any connection to a physical point. | +| physicalReferenceStationID
This field specifies the station ID of a real reference station, when the referenceStationIndicator has the value ' non-physical '. | +| physical-ARP-ECEF-X
This field specifies the antenna reference point X-coordinate in the World Geodetic System 1984 (WGS 84) datum. Scale factor 0.0001 m; range $\pm 13,743,895.3471$ m. | +| physical-ARP-ECEF-Y
This field specifies the antenna reference point Y-coordinate in the World Geodetic System 1984 (WGS 84) datum. Scale factor 0.0001 m; range $\pm 13,743,895.3471$ m. | +| physical-ARP-ECEF-Z
This field specifies the antenna reference point Z-coordinate in the World Geodetic System 1984 (WGS 84) datum. Scale factor 0.0001 m; range $\pm 13,743,895.3471$ m. | +| physical-ARP-unc
This field specifies the uncertainty of the ARP coordinates. | +| equalIntegerAmbiguityLevel
This field specifies the integer ambiguity level of this reference station in relation to other reference stations. Either, the presence or absence of allReferenceStations indicates whether the integer ambiguity level may be assumed to be aligned between all reference stations or not (interpreted as no alignment is facilitated from the location server), or referenceStationList provides a list of reference stations for which the integer ambiguity level may be assumed to be the same. | + +## — GNSS-RTK-CommonObservationInfo + +The IE *GNSS-RTK-CommonObservationInfo* is used by the location server to provide common information applicable to the IE *GNSS-RTK-Observations*. + +The parameters provided in IE *GNSS-RTK-CommonObservationInfo* are used as specified for message type 1071-1127 in [30]. + +``` +-- ASN1START +GNSS-RTK-CommonObservationInfo-r15 ::= SEQUENCE { + referenceStationID-r15 GNSS-ReferenceStationID-r15, +``` + +``` + + clockSteeringIndicator-r15 INTEGER (0..3), + externalClockIndicator-r15 INTEGER (0..3), + smoothingIndicator-r15 BIT STRING (SIZE(1)), + smoothingInterval-r15 BIT STRING (SIZE(3)), + ... +} + +-- ASN1STOP + +``` + +| GNSS-RTK-CommonObservationInfo field descriptions | | +|----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| referenceStationID | This field specifies the Station ID for which the GNSS-RTK-Observations are provided. | +| clockSteeringIndicator | This field provides the clock steering indicator. The interpretation of the value is as follows:
0 clock steering is not applied
In this case, the receiver clock must be kept in the range of $\pm 1$ ms (approximately $\pm 300$ km)
1 clock steering has been applied
In this case, the receiver clock must be kept in the range of $\pm 1$ microsecond (approximately $\pm 300$ metres).
2 unknown clock steering status
3 reserved | +| externalClockIndicator | This field provides the external clock indicator. The interpretation of the value is as follows:
0 internal clock is used
1 external clock is used, clock status is "locked"
2 external clock is used, clock status is "not locked", which may indicate external clock failure and that the transmitted data may not be reliable.
3 unknown clock is used | +| smoothingIndicator | This field provides the GNSS Divergence-free Smoothing Indicator. The interpretation of the value is as follows:
1 Divergence-free smoothing is used
0 Other type of smoothing is used | +| smoothingInterval | The GNSS Smoothing Interval is the integration period over which the pseudorange code phase measurements are averaged using carrier phase information. Divergence-free smoothing may be continuous over the entire period for which the satellite is visible. A value of zero indicates no smoothing is used.
See table " smoothingInterval value to Smoothing Interval relation" below. | + +**smoothingInterval value to Smoothing Interval relation** + +| smoothingInterval value | Smoothing Interval | +|--------------------------------|------------------------------| +| 000 (0) | No smoothing | +| 001 (1) | < 30 s | +| 010 (2) | 30-60 s | +| 011 (3) | 1-2 min | +| 100 (4) | 2-4 min | +| 101 (5) | 4-8 min | +| 110 (6) | >8 min | +| 111 (7) | Unlimited smoothing interval | + +## GNSS-RTK-AuxiliaryStationData + +The IE *GNSS-RTK-AuxiliaryStationData* is used by the location server to provide the coordinates of the antenna reference point (ARP) of Auxiliary Reference Stations, relative to the coordinates provided in IE *GNSS-RTK-ReferenceStationInfo*. The reference station provided in IE *GNSS-RTK-ReferenceStationInfo* is the Master Reference Station. Therefore, one Master Reference Station with its associated Auxiliary Stations is used in a single Provide Assistance Data message. + +The parameters provided in IE *GNSS-RTK-AuxiliaryStationData* are used as specified for message type 1014 in [30]. + +``` + +-- ASN1START + +GNSS-RTK-AuxiliaryStationData-r15 ::= SEQUENCE { + networkID-r15 GNSS-NetworkID-r15, + subNetworkID-r15 GNSS-SubNetworkID-r15 OPTIONAL, -- Need ON +} + +``` + +``` + + master-referenceStationID-r15 GNSS-ReferenceStationID-r15, + auxiliaryStationList-r15 AuxiliaryStationList-r15, + ... +} + +AuxiliaryStationList-r15 ::= SEQUENCE (SIZE (1..32)) OF AuxiliaryStationElement-r15 + +AuxiliaryStationElement-r15 ::= SEQUENCE { + aux-referenceStationID-r15 GNSS-ReferenceStationID-r15, + aux-master-delta-latitude-r15 INTEGER (-524288..524287), + aux-master-delta-longitude-r15 INTEGER (-1048576..1048575), + aux-master-delta-height-r15 INTEGER (-4194304..4194303), + aux-ARP-unc-r15 Aux-ARP-Unc-r15 OPTIONAL, -- Need ON + ... +} + +Aux-ARP-Unc-r15 ::= SEQUENCE { + horizontalUncertainty-r15 INTEGER (0..255), + horizontalConfidence-r15 INTEGER (0..100), + verticalUncertainty-r15 INTEGER (0..255) OPTIONAL, -- Need ON + verticalConfidence-r15 INTEGER (0..100) OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP + +``` + +### GNSS-RTK-AuxiliaryStationData field descriptions + +#### **networkID** + +This field defines the network and the source of the particular set of reference stations and their observation information. The RTK service provider should ensure that the *networkID* is unique in the region serviced. The *networkID* indicates an area and its reference stations where the service providers will provide a homogenous solution with levelled integer ambiguities between its reference stations. In general, the area indicated by *networkID* will comprise one subnetwork with a unique *subNetworkID*. + +#### **subNetworkID** + +This field identifies the subnetwork of a network identified by *networkID*. In general the area indicated by *networkID* will consist of one subnetwork. The *subNetworkID* indicates the actual solution number of integer ambiguity level. If one network has only one subnetwork, this indicates that an ambiguity level throughout the whole network is established. + +#### **master-referenceStationID** + +This field identifies the Master Reference Station. + +#### **aux-referenceStationID** + +This field identifies the Auxiliary Reference Station. + +#### **aux-master-delta-latitude** + +This field provides the delta value in latitude of Antenna Reference Point of "Auxiliary Reference Station minus Master Reference Station" in geographical coordinates based on GRS80 ellipsoid parameters for the same ECEF system as used in IE *GNSS-RTK-ReferenceStationInfo*. + +Scale factor $25 \times 10^{-6}$ degrees; range $\pm 13.1071$ degrees. + +#### **aux-master-delta-longitude** + +This field provides the delta value in longitude of Antenna Reference Point of "Auxiliary Reference Station minus Master Reference Station" in geographical coordinates based on GRS80 ellipsoid parameters for the same ECEF system as used in IE *GNSS-RTK-ReferenceStationInfo*. + +Scale factor $25 \times 10^{-6}$ degrees; range $\pm 26.2142$ degrees. + +#### **aux-master-delta-height** + +This field provides the delta value in ellipsoidal height of Antenna Reference Point of "Auxiliary Reference Station minus Master Reference Station" in geographical coordinates based on GRS80 ellipsoid parameters for the same ECEF system as used in IE *GNSS-RTK-ReferenceStationInfo*. + +Scale factor 1 millimetre; range $\pm 4194.303$ m. + +#### **aux-ARP-unc** + +This field specifies the uncertainty of the auxiliary station ARP coordinates and comprise the following fields: + +- **horizontalUncertainty** indicates the horizontal uncertainty of the ARP latitude/longitude. The 'horizontalUncertainty' corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and 'horizontalConfidence' corresponds to confidence as defined in TS 23.032 [15]. +- **verticalUncertainty** indicates the vertical uncertainty of the ARP altitude. The 'verticalUncertainty' corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and 'verticalConfidence' corresponds to confidence as defined in TS 23.032 [15]. + +## GNSS-SSR-CorrectionPoints + +The IE *GNSS-SSR-CorrectionPoints* is used by the location server to provide a list of correction point coordinates or an array of correction points ("grid") for which the *GNSS-SSR-GriddedCorrection* are valid. + +``` +-- ASN1START + +GNSS-SSR-CorrectionPoints-r16 ::= SEQUENCE { + correctionPointSetID-r16 INTEGER (0..16383), + correctionPoints-r16 CHOICE { + listOfCorrectionPoints-r16 GNSS-SSR-ListOfCorrectionPoints-r16, + arrayOfCorrectionPoints-r16 GNSS-SSR-ArrayOfCorrectionPoints-r16 + }, + ... +} + +GNSS-SSR-ListOfCorrectionPoints-r16 ::= SEQUENCE { + referencePointLatitude-r16 INTEGER (-16384..16383), + referencePointLongitude-r16 INTEGER (-32768..32767), + relativeLocationsList-r16 SEQUENCE (SIZE (0..63)) OF RelativeLocationElement-r16, + ... +} + +RelativeLocationElement-r16 ::= SEQUENCE { + deltaLatitude-r16 INTEGER (-512..511), + deltaLongitude-r16 INTEGER (-1024..1023), + ... +} + +GNSS-SSR-ArrayOfCorrectionPoints-r16 ::= SEQUENCE { + referencePointLatitude-r16 INTEGER (-16384..16383), + referencePointLongitude-r16 INTEGER (-32768..32767), + numberOfStepsLatitude-r16 INTEGER (0..63), + numberOfStepsLongitude-r16 INTEGER (0..63), + stepOfLatitude-r16 INTEGER (1..511), + stepOfLongitude-r16 INTEGER (1..1023), + bitmaskOfGrids-r16 BIT STRING (SIZE(64)) OPTIONAL, -- Need OP + ... +} + +-- ASN1STOP +``` + +### GNSS-SSR-CorrectionPoints field descriptions + +#### **correctionPointSetID** + +This field provides the ID of the Atmospheric Correction Point set. It is a regionally unique arbitrary number that is used by the UE to ensure that the atmospheric corrections are being applied to the correct set of points. + +#### **referencePointLatitude** + +This field specifies the latitude for the reference point, expressed in the range of -90° , +90°, coded as a number between -214 and 214-1, coded in 2's complement binary on 15 bits. The relation between the latitude X in the range [-90°, 90°] and the coded number N is: + +where $\lfloor x \rfloor$ denotes the greatest integer less than or equal to x (floor operator). + +For the *listOfCorrectionPoints*, the reference point defines the 1st correction point location. + +For the *arrayOfCorrectionPoints*, the reference point defines the northwest corner of the correction point array. + +#### **referencePointLongitude** + +This field specifies the longitude for the reference point, expressed in the range -180°, +180°, coded as a number between -215 and 215-1, coded in 2's complement binary on 16 bits. The relation between the longitude X in the range [-180°, 180°) and the coded number N is: + +For the *listOfCorrectionPoints*, the reference point defines the 1st correction point location. + +For the *arrayOfCorrectionPoints*, the reference point defines the northwest corner of the correction point array. + +| GNSS-SSR-CorrectionPoints field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| relativeLocationsList
This field specifies the 2 nd , 3 rd , ..., 64 th correction point location. | +| deltaLatitude
This field specifies the delta value in latitude of this correction point location relative to the previous point on the list or the reference point in the case of the first additional point, defined as "correction point location" minus "previous correction point location" in units of 0.01 degrees. | +| deltaLongitude
This field specifies the delta value in longitude of this correction point location relative to the previous point on the list or the reference point in the case of the first additional point, defined as "correction point location" minus "previous correction point location" in units of 0.01 degrees. | +| numberOfStepsLatitude, numberOfStepsLongitude
These fields specify the number of steps for latitude and longitude direction respectively. | +| stepOfLatitude, stepOfLongitude
These fields specify the spacing of the correction points for latitude and longitude respectively. The unit and scale factor is 0.01 degrees. | +| bitmaskOfGrids
This field specifies the availability of correction data at the correction points in the array. If a specific bit is enabled (set to '1'), the correction is available. Only the first $(\text{numberOfStepsLatitude} + 1) \times (\text{numberOfStepsLongitude} + 1)$ bits are used, the remainder are set to '0'. Starting with the northwest corner of the array (top left on a north oriented map) the correction points are enumerated with row precedence – first row west to east, second row west to east, until last row west to east – ending with the southeast corner of the array. If the field is omitted all correction points are used and none omitted. | + +## – GNSS-Integrity-ServiceParameters + +The IE *GNSS-Integrity-ServiceParameters* is used by the location server to provide the range of Integrity Risk (IR) for which the GNSS integrity assistance data are valid. + +``` +-- ASN1START + +GNSS-Integrity-ServiceParameters-r17 ::= SEQUENCE { + irMinimum-r17 INTEGER (0..255), + irMaximum-r17 INTEGER (0..255), + ... +} + +-- ASN1STOP +``` + +| GNSS-Integrity-ServiceParameters field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| irMinimum
This field specifies the Minimum Integrity Risk (IR) which is the minimum IR for which the error bounds provided in the IEs SSR-IntegrityOrbitBounds , SSR-IntegrityClockBounds , SSR-IntegrityCodeBiasBounds , SSR-IntegrityPhaseBiasBounds , STEC-IntegrityErrorBounds , and TropoDelayIntegrityErrorBounds are valid. The IR is calculated by where $n$ is the value of irMinimum and the range is $10^{-10.2}$ to 1. | +| irMaximum
This field specifies the Maximum Integrity Risk (IR) which is the maximum IR for which the error bounds provided in the IEs SSR-IntegrityOrbitBounds , SSR-IntegrityClockBounds , SSR-IntegrityCodeBiasBounds , SSR-IntegrityPhaseBiasBounds , STEC-IntegrityErrorBounds , and TropoDelayIntegrityErrorBounds are valid. The IR is calculated by where $n$ is the value of irMaximum and the range is $10^{-10.2}$ to 1. | + +## – GNSS-Integrity-ServiceAlert + +The IE *GNSS-Integrity-ServiceAlert* is used by the location server to indicate whether the corresponding assistance data can be used for integrity related applications. + +``` +-- ASN1START + +GNSS-Integrity-ServiceAlert-r17 ::= SEQUENCE { + ionosphereDoNotUse-r17 BOOLEAN, + troposphereDoNotUse-r17 BOOLEAN, + ... +} + +-- ASN1STOP +``` + +| GNSS-Integrity-ServiceAlert field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ionosphereDoNotUse
This field indicates whether the ionospheric corrections in IE GNSS-SSR-STECCorrection can be used for integrity related applications (FALSE) or not (TRUE). | +| troposphereDoNotUse
This field indicates whether the tropospheric corrections in IE GNSS-SSR-GriddedCorrection can be used for integrity related applications (FALSE) or not (TRUE). | + +## – GNSS-LOS-NLOS-GridPoints + +The IE *GNSS-LOS-NLOS-GridPoints* is used by the location server to provide a list of grid point coordinates or an array of correction points ("grid") for which specific assistance data can be provided. + +``` +-- ASN1START + +GNSS-LOS-NLOS-GridPoints-r18 ::= SEQUENCE { + gridPointsSetID-r18 INTEGER (0..16383), + horizontalGridPoints-r18 ArrayOfGridPoints-r18, + referenceAltitudeFine-r18 INTEGER (0..9) OPTIONAL, -- Need OP + verticalGridPoints-r18 VerticalGridPoints-r18 OPTIONAL, -- Cond 3D + ... +} + +ArrayOfGridPoints-r18 ::= SEQUENCE { + referencePointLatitude-r18 INTEGER (-16777216.. 16777215), + referencePointLongitude-r18 INTEGER (-33554432.. 33554431), + numberOfStepsSouth-r18 INTEGER (0.. 255), + numberOfStepsEast-r18 INTEGER (0.. 255), + stepSouth-r18 SpatialDelta-r18, + stepEast-r18 SpatialDelta-r18, + bitmaskOfGrids-r18 CHOICE { + bog16-r18 BIT STRING (SIZE(16)), + bog64-r18 BIT STRING (SIZE(64)), + bog256-r18 BIT STRING (SIZE(256)), + ... + } OPTIONAL, -- Need OP + ... +} + +VerticalGridPoints-r18 ::= SEQUENCE { + referenceAltitudeCoarse-r18 INTEGER (-50..900), + numberOfStepsDown-r18 INTEGER (1..3), + stepDown-r18 SpatialDelta-r18, + upperValidityDeltaAltitude-r18 SpatialDelta-r18 OPTIONAL, -- Need OP + lowerValidityDeltaAltitude-r18 SpatialDelta-r18 OPTIONAL, -- Need OP + ... +} + +SpatialDelta-r18 ::= ENUMERATED {n1, n2, n3, n4, n5, n10, n20, n50, n100} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|-----------------------------|-----------------------------------------------------------------------------------| +| 3D | This field is mandatory present if a 3D grid is provided; otherwise it is absent. | + +| GNSS-LOS-NLOS-GridPoints field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gridPointsSetID
This field provides the ID of the spatial grid point set. It is a regionally unique arbitrary number that is used by the UE to ensure that provided assistance data associated to a spatial grid point set is being applied to the correct set of points.
The grid point set ID identifies a grid defined by a reference point corresponding to the northwest corner (of the upper layer in case of a 3D grid), where the rest of the grid is defined by a number of steps and step lengths in the south, east (down in case of a 3D grid). The grid is valid within the horizontal perimeter of the grid and between an upper and lower validity altitude, where the upper validity altitude is $(referenceAltitudeFine + 10 * referenceAltitudeCoarse + upperValidityDeltaAltitude)$ , and the lower validity altitude is $(referenceAltitudeFine + 10 * referenceAltitudeCoarse - numberOfStepsDown * stepDown - lowerValidityDeltaAltitude)$ . | +| referencePointLatitude
This field specifies the latitude for the reference point, expressed in the range of $-90^\circ$ , $+90^\circ$ , coded as a number between $-2^{24}$ and $2^{24}-1$ , coded in 2's complement binary on 25 bits. The relation between the latitude X in the range $[-90^\circ, 90^\circ]$ and the coded number N is:

where $\lfloor x \rfloor$ denotes the greatest integer less than or equal to x (floor operator).
The reference point defines the northwest corner of the grid point array. | +| referencePointLongitude
This field specifies the longitude for the reference point, expressed in the range $-180^\circ$ , $+180^\circ$ , coded as a number between $-2^{25}$ and $2^{25}-1$ , coded in 2's complement binary on 26 bits. The relation between the longitude X in the range $[-180^\circ, 180^\circ)$ and the coded number N is:

The reference point defines the northwest corner of the grid point array. | +| numberOfStepsSouth, numberOfStepsEast, numberOfStepsDown
These fields specify the number of steps for south, east and down direction respectively. | +| stepSouth, stepEast, stepDown
These fields specify the spacing of the grid points for south, east and down respectively. | +| bitmaskOfGrids
This field specifies the availability of grid data at the horizontal grid points in the array and applies to all altitude layers of the grid. If a specific bit is enabled (set to '1'), the grid is available. Only the first $(numberOfStepsSouth+1) \times (numberOfStepsEast+1)$ bits are used, the remainder are set to '0'. Starting with the northwest corner of the array (top left on a north oriented map) the grid points are enumerated with row precedence – first row west to east, second row west to east, until last row west to east – ending with the southeast corner of the array. If the field is omitted all grid points are used and none omitted. | +| referenceAltitudeFine
If this field is present and
  • - the field referenceAltitudeCoarse is also present, it provides the fine resolution of the 3D grid altitude of the upmost layer, or
  • - the field referenceAltitudeCoarse is absent, it provides the altitude above ground level of the 2D grid, with a scale factor of 1m.
If the field is absent, the default value is 0m. | +| referenceAltitudeCoarse
This field is present if a 3D grid is provided and specifies the coarse altitude, scale factor 10m, of the upmost layer of the grid relative to the WGS84 ellipsoid. If this field is absent, a 2D grid is provided, valid for ground level. | +| upperValidityDeltaAltitude
This field, if present, specifies the upper validity altitude relative to the grid upper layer altitude. | +| lowerValidityDeltaAltitude
This field, if present, specifies the lower validity altitude relative to the lowest grid layer altitude. | +| SpatialDelta
This field specifies spatial deltas associated to spatial grids. Values n1, n2, n3, n4, n5, n10, n20, n50, n100 encodes 1, 2, 3, 4, 5, 10, 20, 50, 100 meters respectively. | + +## – GNSS-SSR-IOD-Update + +The IE *GNSS-SSR-IOD-Update* is used to indicate the Issue of Data (IOD) values of other IEs that are infrequently updated. The IEs with a matching IOD are linked and valid while the *GNSS-SSR-IOD-Update* is valid, i.e. during the *GNSS-SSR-IOD-Update* and *ssrUpdateInterval* and with respect to the *iod-ssr*. + +``` +-- ASN1START + +GNSS-SSR-IOD-Update-r18 ::= SEQUENCE { + epochTime-r18 GNSS-SystemTime, + ssrUpdateInterval-r18 INTEGER (0..15), + iod-ssr-r18 INTEGER (0..15), + iod-ssr-PCVResiduals-r18 INTEGER (0..64), + ... +} +``` + +``` + +} +-- ASN1STOP + +``` + +#### GNSS-SSR-IOD-Update field descriptions + +| | | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epochTime | This field specifies the epoch time of validity of the information elements referenced via IOD values from this IE. The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| ssrUpdateInterval | This field specifies the SSR Update Interval. The SSR Update Intervals for all SSR parameters start at time 00:00:00 of the GPS time scale. A change of the SSR Update Interval during the transmission of SSR data should ensure consistent data for a target device. See table Value of ssrUpdateInterval to SSR Update Interval relation in IE GNSS-SSR- OrbitCorrections . | +| iod-ssr | This field specifies the Issue of Data number for the SSR data. A change of iod-ssr is used to indicate a change in the SSR generating configuration. | +| iod-ssr-PCVResiduals | This field specifies the Issue of Data for the SSR Satellite PCV Residuals that is valid while the GNSS-SSR-IOD-Update is valid. | + +### GNSS-TimeModelList + +The IE *GNSS-TimeModelList* is used by the location server to provide the GNSS-GNSS system time offset between the GNSS system time indicated by IE *GNSS-ID* in IE *GNSS-GenericAssistDataElement* to the GNSS system time indicated by IE *gnss-TO-ID*. Several *GNSS-TimeModelElement* IEs can be included with different *gnss-TO-ID* fields. The location server should provide a *GNSS-TimeModelList* for the same *GNSS-ID* as the *gnss-TimeID* in IE *GNSS-SystemTime* in *GNSS-ReferenceTime* assistance. If the location server does not provide a *GNSS-TimeModelList* for the same *GNSS-ID* as the *gnss-TimeID* in IE *GNSS-SystemTime* in *GNSS-ReferenceTime* assistance the target device assumes *tA1* and *tA2* are equal to zero. + +``` + +-- ASN1START + +GNSS-TimeModelList ::= SEQUENCE (SIZE (1..15)) OF GNSS-TimeModelElement + +GNSS-TimeModelElement ::= SEQUENCE { + gnss-TimeModelRefTime INTEGER (0..65535), + tA0 INTEGER (-67108864..67108863), + tA1 INTEGER (-4096..4095) OPTIONAL, -- Need ON + tA2 INTEGER (-64..63) OPTIONAL, -- Need ON + gnss-TO-ID INTEGER (1..15), + weekNumber INTEGER (0..8191) OPTIONAL, -- Need ON + deltaT INTEGER (-128..127) OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP + +``` + +#### GNSS-TimeModelElement field descriptions + +| | | +|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-TimeModelRefTime | This field specifies the reference time of week for GNSS-TimeModelElement and it is given in GNSS specific system time.
Scale factor $2^4$ seconds. | +| tA0 | This field specifies the bias coefficient of the GNSS-TimeModelElement .
Scale factor $2^{-35}$ seconds. | +| tA1 | This field specifies the drift coefficient of the GNSS-TimeModelElement .
Scale factor of $2^{-51}$ seconds/second. | +| tA2 | This field specifies the drift rate correction coefficient of the GNSS-TimeModelElement .
Scale factor of $2^{-68}$ seconds/second 2 . | +| gnss-TO-ID | This field specifies the GNSS system time of the GNSS for which the GNSS-TimeModelElement is applicable. GNSS-TimeModelElement contains parameters to convert GNSS system time from the system indicated by GNSS-ID to GNSS system time indicated by gnss-TO-ID . The conversion is defined in [4,5,6]. See table of gnss-TO-ID to Indication relation below. NOTE. | + +| GNSS-TimeModelElement field descriptions | | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| weekNumber | This field specifies the reference week of the GNSS-TimeModelElement given in GNSS specific system time. The location server should include this field, if tA1 or tA2 is included.
Scale factor 1 week. | +| deltaT | This field specifies the integer number of seconds of the GNSS-GNSS time offset provided in the GNSS-TimeModelElement .
Scale factor 1 second. | + +### gnss-TO-ID to Indication relation + +| Value of gnss-TO-ID | Indication | +|---------------------|------------| +| 1 | GPS | +| 2 | Galileo | +| 3 | QZSS | +| 4 | GLONASS | +| 5 | BDS | +| 6 | NavIC | +| 7-15 | reserved | + +NOTE: The time relationship between the system time indicated by *GNSS-ID* and system time indicated by *gnss-TO-ID* is given by the following equation: + +$$t_{\text{GNSS}} = t_E - (A_{0\text{GGTO}} + A_{1\text{GGTO}} (t_E - t_{\text{GGTO}} + 604800 (\text{WN} - \text{WN}_{\text{GGTO}})) + A_{2\text{GGTO}} (t_E - t_{\text{GGTO}} + 604800 (\text{WN} - \text{WN}_{\text{GGTO}}))^2)$$ + +where + +$t_{\text{GNSS}}$ is the system time of week for the GNSS indicated by *gnss-TO-ID*. + $t_E$ is the system time of week for the GNSS indicated by *GNSS-ID*. + $\text{WN}$ is the week number of the GNSS system time indicated by *GNSS-ID* corresponding to the $t_E$ . + $t_{\text{GGTO}}$ is the system time of week for the time model data in the GNSS time indicated by *GNSS-ID* and given by the *gnss-TimeModelRefTime* field. + $\text{WN}_{\text{GGTO}}$ is the week number for the time model data in the GNSS time indicated by *GNSS-ID* corresponding to the $t_{\text{GGTO}}$ and given by the *weekNumber* field. + $A_{0\text{GGTO}}$ is given by the *tA0* field. + $A_{1\text{GGTO}}$ is given by the *tA1* field. + $A_{2\text{GGTO}}$ is given by the *tA2* field. + +If the *tA1* and *tA2* are not included in the *GNSS-TimeModelElement*, the target device assumes $A_{1\text{GGTO}}$ and $A_{2\text{GGTO}}$ are equal to zero. + +The GNSS system times in the IE *GNSS-TimeModelList* and used in the equation above are all given in Time of Week (TOW) and Week Number (WN) in the indicated GNSS specific system time. For conversion between TOW/WN and Day Number/Time of Day (*gnss-DayNumber/gnss-TimeOfDay*) a GNSS week consists of 7 days since the origin of the particular GNSS System time (with the week number count starting at 0), and a day consists of 86400 seconds. + +## GNSS-DifferentialCorrections + +The IE *GNSS-DifferentialCorrections* is used by the location server to provide differential GNSS corrections to the target device for a specific GNSS. Differential corrections can be provided for up to 3 signals per GNSS. + +``` +-- ASN1START + +GNSS-DifferentialCorrections ::= SEQUENCE { + dgnss-RefTime INTEGER (0..3599), + dgnss-SgnTypeList DGNSS-SgnTypeList, + ... +} + +DGNSS-SgnTypeList ::= SEQUENCE (SIZE (1..3)) OF DGNSS-SgnTypeElement +``` + +``` + +DGNSS-SgnTypeElement ::= SEQUENCE { + gnss-SignalID GNSS-SignalID, + gnss-StatusHealth INTEGER (0..7), + dgnss-SatList DGNSS-SatList, + ... +} + +DGNSS-SatList ::= SEQUENCE (SIZE (1..64)) OF DGNSS-CorrectionsElement + +DGNSS-CorrectionsElement ::= SEQUENCE { + svID SV-ID, + iod BIT STRING (SIZE(11)), + udre INTEGER (0..3), + pseudoRangeCor INTEGER (-2047..2047), + rangeRateCor INTEGER (-127..127), + udreGrowthRate INTEGER (0..7) OPTIONAL, -- Need ON + udreValidityTime INTEGER (0..7) OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP + +``` + +### GNSS-DifferentialCorrections field descriptions + +#### ***dgnss-RefTime*** + +This field specifies the time for which the DGNSS corrections are valid, modulo 1 hour. *dgnss-RefTime* is given in GNSS specific system time. + +Scale factor 1-second. + +#### ***dgnss-SgnTypeList*** + +This list includes differential correction data for different GNSS signal types, identified by *GNSS-SignalID*. + +#### ***gnss-StatusHealth*** + +This field specifies the status of the differential corrections. The values of this field and their respective meanings are defined as in table *gnss-StatusHealth Value to Indication relation* below. + +The first six values in this field indicate valid differential corrections. When using the values described below, the "UDRE Scale Factor" value is applied to the UDRE values contained in the element. The purpose is to indicate an estimate in the amount of error in the corrections. + +The value "110" indicates that the source of the differential corrections (e.g., reference station or external DGNSS network) is currently not being monitored. The value "111" indicates that the corrections provided by the source are invalid, as judged by the source. + +#### ***dgnss-SatList*** + +This list includes differential correction data for different GNSS satellites, identified by *SV-ID*. + +#### ***iod*** + +This field specifies the Issue of Data field which contains the identity for the *GNSS-NavigationModel*. + +#### ***udre*** + +This field provides an estimate of the uncertainty ( $1-\sigma$ ) in the corrections for the particular satellite. The value in this field shall be multiplied by the UDRE Scale Factor in the *gnss-StatusHealth* field to determine the final UDRE estimate for the particular satellite. The meanings of the values for this field are shown in the table *udre Value to Indication relation* below. + +#### ***pseudoRangeCor*** + +This field specifies the correction to the pseudorange for the particular satellite at *dgnss-RefTime*, $t_0$ . The value of this field is given in metres and the scale factor is 0.32 metres in the range of $\pm 655.04$ metres. The method of calculating this field is described in [11]. + +If the location server has received a request for GNSS assistance data from a target device which included a request for the GNSS Navigation Model and DGNSS, the location server determines, for each satellite, if the navigation model stored by the target device is still suitable for use with DGNSS corrections and if so and if DGNSS corrections are supported the location server should send DGNSS corrections without including the GNSS Navigation Model. + +The *iod* value sent for a satellite shall always be the IOD value that corresponds to the navigation model for which the pseudo-range corrections are applicable. + +The target device shall only use the *pseudoRangeCor* value when the IOD value received matches its available navigation model. + +Pseudo-range corrections are provided with respect to GNSS specific geodetic datum (e.g., PZ-90.02 if *GNSS-ID* indicates GLONASS). + +Scale factor 0.32 metres. + +| GNSS-DifferentialCorrections field descriptions | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +|

rangeRateCor
This field specifies the rate-of-change of the pseudorange correction for the particular satellite, using the satellite ephemeris and clock corrections identified by the iod field. The value of this field is given in metres per second and the resolution is 0.032 metres/second in the range of \pm 4.064 metres/second. For some time t_1 > t_0, the corrections for iod are estimated by

$\text{PRC}(t_1, \text{IOD}) = \text{PRC}(t_0, \text{IOD}) + \text{RRC}(t_0, \text{IOD}) \cdot (t_1 - t_0),$

and the target device uses this to correct the pseudorange it measures at t_1, \text{PR}_m(t_1, \text{IOD}), by

$\text{PR}(t_1, \text{IOD}) = \text{PR}_m(t_1, \text{IOD}) + \text{PRC}(t_1, \text{IOD}).$

The location server always sends the RRC value that corresponds to the PRC value that it sends. The target device shall only use the RRC value when the iod value received matches its available navigation model. Scale factor 0.032 metres/second.

| | + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +|

udreGrowthRate
This field provides an estimate of the growth rate of uncertainty (1-\alpha) in the corrections for the particular satellite identified by SV-ID. The estimated UDRE at time value specified in the udreValidityTime t_1 is calculated as follows:

$\text{UDRE}(t_0+t_1) = \text{UDRE}(t_0) \times \text{udreGrowthRate},$

where t_0 is the DGNSS Reference Time dgnss-RefTime for which the corrections are valid, t_1 is the udreValidityTime field, \text{UDRE}(t_0) is the value of the udre field, and udreGrowthRate field is the factor as shown in the table Value of udreGrowthRate to Indication relation below.

| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +|

udreValidityTime
This field specifies the time when the udreGrowthRate field applies and is included if udreGrowthRate is included. The meaning of the values for this field is as shown in the table Value of udreValidityTime to Indication relation below.

| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +#### gnss-StatusHealth Value to Indication relation + +| gnss-StatusHealth Value | Indication | +|--------------------------------|----------------------------------------------| +| 000 | UDRE Scale Factor = 1.0 | +| 001 | UDRE Scale Factor = 0.75 | +| 010 | UDRE Scale Factor = 0.5 | +| 011 | UDRE Scale Factor = 0.3 | +| 100 | UDRE Scale Factor = 0.2 | +| 101 | UDRE Scale Factor = 0.1 | +| 110 | Reference Station Transmission Not Monitored | +| 111 | Data is invalid - disregard | + +#### udre Value to Indication relation + +| udre Value | Indication | +|-------------------|--------------------------------------------------| +| 00 | $\text{UDRE} \leq 1.0 \text{ m}$ | +| 01 | $1.0 \text{ m} < \text{UDRE} \leq 4.0 \text{ m}$ | +| 10 | $4.0 \text{ m} < \text{UDRE} \leq 8.0 \text{ m}$ | +| 11 | $8.0 \text{ m} < \text{UDRE}$ | + +#### Value of udreGrowthRate to Indication relation + +| Value of udreGrowthRate | Indication | +|--------------------------------|-------------------| +| 000 | 1.5 | +| 001 | 2 | +| 010 | 4 | +| 011 | 6 | +| 100 | 8 | +| 101 | 10 | +| 110 | 12 | +| 111 | 16 | + +#### Value of udreValidityTime to Indication relation + +| Value of udreValidityTime | Indication [seconds] | +|----------------------------------|-----------------------------| +| 000 | 20 | +| 001 | 40 | + +| | | +|-----|------| +| 010 | 80 | +| 011 | 160 | +| 100 | 320 | +| 101 | 640 | +| 110 | 1280 | +| 111 | 2560 | + +## – GNSS-NavigationModel + +The IE *GNSS-NavigationModel* is used by the location server to provide precise navigation data to the GNSS capable target device. In response to a request from a target device for GNSS Assistance Data, the location server determines whether to send the navigation model for a particular satellite to a target device based upon factors like the T-Toe limit specified by the target device and any request from the target device for DGNSS (see also *GNSS-DifferentialCorrections*). GNSS Orbit Model can be given in Keplerian parameters or as state vector in Earth-Centered Earth-Fixed coordinates, dependent on the *GNSS-ID* and the target device capabilities. The meaning of these parameters is defined in relevant ICDs of the particular GNSS and GNSS specific interpretations apply. For example, GPS and QZSS use the same model parameters but some parameters have a different interpretation [7]. + +``` +-- ASN1START + +GNSS-NavigationModel ::= SEQUENCE { + nonBroadcastIndFlag INTEGER (0..1), + gnss-SatelliteList GNSS-NavModelSatelliteList, + ... +} + +GNSS-NavModelSatelliteList ::= SEQUENCE (SIZE(1..64)) OF GNSS-NavModelSatelliteElement + +GNSS-NavModelSatelliteElement ::= SEQUENCE { + svID SV-ID, + svHealth BIT STRING (SIZE(8)), + iod BIT STRING (SIZE(11)), + gnss-ClockModel GNSS-ClockModel, + gnss-OrbitModel GNSS-OrbitModel, + ... + [[ svHealthExt-v1240 BIT STRING (SIZE(4)) OPTIONAL -- Need ON + ]] +} + +GNSS-ClockModel ::= CHOICE { + standardClockModelList StandardClockModelList, -- Model-1 + nav-ClockModel NAV-ClockModel, -- Model-2 + cnav-ClockModel CNAV-ClockModel, -- Model-3 + glonass-ClockModel GLONASS-ClockModel, -- Model-4 + sbas-ClockModel SBAS-ClockModel, -- Model-5 + ... + bds-ClockModel-r12 BDS-ClockModel-r12, -- Model-6 + bds-ClockModel2-r16 BDS-ClockModel2-r16, -- Model-7 + navic-ClockModel-r16 NavIC-ClockModel-r16 -- Model-8 +} + +GNSS-OrbitModel ::= CHOICE { + keplerianSet NavModelKeplerianSet, -- Model-1 + nav-KeplerianSet NavModelNAV-KeplerianSet, -- Model-2 + cnav-KeplerianSet NavModelCNAV-KeplerianSet, -- Model-3 + glonass-ECEF NavModel-GLONASS-ECEF, -- Model-4 + sbas-ECEF NavModel-SBAS-ECEF, -- Model-5 + ... + bds-KeplerianSet-r12 NavModel-BDS-KeplerianSet-r12, -- Model-6 + bds-KeplerianSet2-r16 NavModel-BDS-KeplerianSet2-r16, -- Model-7 + navic-KeplerianSet-r16 NavModel-NavIC-KeplerianSet-r16 -- Model-8 +} + +-- ASN1STOP +``` + +| GNSS-NavigationModel field descriptions | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--|--|--|--|--| +| nonBroadcastIndFlag
This field indicates if the GNSS-NavigationModel elements are not derived from satellite broadcast data or are given in a format not native to the GNSS. A value of 0 means the GNSS-NavigationModel data elements correspond to GNSS satellite broadcasted data; a value of 1 means the GNSS-NavigationModel data elements are not derived from satellite broadcast. | | | | | | | | | +| gnss-SatelliteList
This list provides ephemeris and clock corrections for GNSS satellites indicated by SV-ID . | | | | | | | | | +| svHealth
This field specifies the satellite's current health. The health values are GNSS system specific. The interpretation of svHealth depends on the GNSS-ID and is as shown in table GNSS to svHealth Bit String(8) relation below. | | | | | | | | | +| iod
This field specifies the Issue of Data and contains the identity for GNSS Navigation Model.
In the case of broadcasted GPS NAV ephemeris, the iod contains the IODC as described in [4].
In the case of broadcasted Modernized GPS ephemeris, the iod contains the 11-bit parameter $t_{oe}$ as defined in [4, Table 30-I] [6, Table 3.5-1].
In the case of broadcasted SBAS ephemeris, the iod contains the 8 bits Issue of Data as defined in [10] Message Type 9.
In the case of broadcasted QZSS QZS-L1 ephemeris, the iod contains the IODC as described in [7].
In the case of broadcasted QZSS QZS-L1C/L2C/L5 ephemeris, the iod contains the 11-bit parameter $t_{oe}$ as defined in [7].
In the case of broadcasted GLONASS ephemeris, the iod contains the parameter $t_b$ as defined in [9].
In the case of broadcasted Galileo ephemeris, the iod contains the IOD index as described in [8].
In the case of broadcasted BDS B1I/B3I ephemeris, the iod contains 11 MSB bits of the $t_{oe}$ as defined in [23], [50].
In the case of broadcasted BDS B1C/B2a ephemeris, the iod contains the IODC as described in [39], [49].
In the case of broadcasted NavIC ephemeris, the iod contains 11 MSB bits of the $t_{oe}$ as defined in [38].
The interpretation of iod depends on the GNSS-ID and is as shown in table GNSS to iod Bit String(11) relation below. | | | | | | | | | +| svHealthExt
This field specifies the satellite's additional current health. The health values are GNSS system specific. The interpretation of svHealthExt depends on the GNSS-ID and is as shown in table GNSS to svHealthExt Bit String(4) relation below. | | | | | | | | | + +### GNSS to *svHealth* Bit String(8) relation + +| GNSS | svHealth Bit String(8) | | | | | | | | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------|--------------------------|-------------------|-------------------|-------------------|-------------------| +| | Bit 1
(MSB) | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8
(LSB) | +| GPS L1/CA (1) | SV Health [4] | | | | | | '0'
(reserved) | '0'
(reserved) | +| Modernized GPS (2) | L1C Health [6] | L1 Health [4,5] | L2 Health [4,5] | L5 Health [4,5] | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | +| SBAS (3) | Ranging
On (0),Off(1) [10] | Corrections
On(0),Off(1) [10] | Integrity
On(0),Off(1)[10] | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | +| QZSS (4)
QZS-L1 | SV Health [7] | | | | | | '0'
(reserved) | '0'
(reserved) | +| QZSS (5)
QZS-L1C/L2C/L5 | L1C Health [7] | L1 Health [7] | L2 Health [7] | L5 Health [7] | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | +| GLONASS | B n (MSB) [9, page 30] | F r [9, Table 4.4] | | | | | '0'
(reserved) | '0'
(reserved) | +| Galileo [8, clause 5.1.9.3] | E5a Data Validity Status | E5b Data Validity Status | E1-B Data Validity Status | E5a Signal Health Status | | | '0'
(reserved) | '0'
(reserved) | +| BDS (6) B1I [23] | B1I Health (SatH1) [23], [50] | B3I Health (SatH1) [23], [50] | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | +| BDS (7) B1C [39]/B2a [49] | Sat Clock Health [39], [49] | B1C Health [39], [49] | B2a Health [39], [49] | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | +| NavIC | L5 health | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | '0'
(reserved) | +| Note 1: | If GNSS-ID indicates 'gps', and GNSS Orbit Model-2 is included, this interpretation of svHealth applies. | | | | | | | | +| Note 2: | If GNSS-ID indicates 'gps', and GNSS Orbit Model-3 is included, this interpretation of svHealth applies.
If a certain signal is not supported on the satellite indicated by SV-ID , the corresponding health bit shall be set to '1' (i.e., signal can not be used). | | | | | | | | +| Note 3: | svHealth , in the case that GNSS-ID indicates 'sbas', includes the 5 LSBs of the Health included in GEO Almanac Message Parameters (Type 17) [10]. | | | | | | | | +| Note 4: | If GNSS-ID indicates 'qzss', and GNSS Orbit Model-2 is included, this interpretation of svHealth applies. | | | | | | | | +| Note 5: | If GNSS-ID indicates 'qzss', and GNSS Orbit Model-3 is included, this interpretation of svHealth applies. | | | | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------| +| Note 6: | If GNSS-ID indicates 'bds', and GNSS Orbit Model-6 is included, this interpretation of svHealth applies. | +| Note 7: | If GNSS-ID indicates 'bds', and GNSS Orbit Model-7 is included, this interpretation of svHealth applies. | + +### GNSS to iod Bit String(11) relation + +| GNSS | iod Bit String(11) | | | | | | | | | | | | | | | | | | | +|---------------------|----------------------------------------------------------------------------------|---------------------------------|-------|--------------------------------------|--------------------------------------|-------|-------|-------|-------|--------|--------------|--|--|--|--|--|--|--|--| +| | Bit 1 (MSB) | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | Bit 9 | Bit 10 | Bit 11 (LSB) | | | | | | | | | +| GPS L1/CA | '0' | Issue of Data, Clock [4] | | | | | | | | | | | | | | | | | | +| Modernized GPS | $t_{oe}$ (seconds, scale factor 300, range 0 – 604500) [4,5,6] | | | | | | | | | | | | | | | | | | | +| SBAS | '0' | '0' | '0' | Issue of Data ([10], Message Type 9) | | | | | | | | | | | | | | | | +| QZSS QZS-L1 | '0' | Issue of Data, Clock [7] | | | | | | | | | | | | | | | | | | +| QZSS QZS-L1C/L2C/L5 | $t_{oe}$ (seconds, scale factor 300, range 0 – 604500) [7] | | | | | | | | | | | | | | | | | | | +| GLONASS | '0' | '0' | '0' | '0' | $t_b$ (minutes, scale factor 15) [9] | | | | | | | | | | | | | | | +| Galileo I/NAV | '0' | IODnav [8] | | | | | | | | | | | | | | | | | | +| BDS B1I/B3I | 11 MSB bits of $t_{oe}$ (seconds, scale factor 512, range 0 – 604672) [23], [50] | | | | | | | | | | | | | | | | | | | +| BDS B1C/B2a | '0' | Issue of Data, Clock [39], [49] | | | | | | | | | | | | | | | | | | +| NavIC | 11 MSB bits of $t_{oe}$ (seconds, scale factor 512) [38] | | | | | | | | | | | | | | | | | | | + +### GNSS to svHealthExt Bit String(4) relation + +| GNSS | svHealthExt Bit String(4) | | | | +|-----------------------------|---------------------------|-------|---------------------------|-------------| +| | Bit 1 (MSB) | Bit 2 | Bit 3 | Bit 4 (LSB) | +| Galileo [8, clause 5.1.9.3] | E5b Signal Health Status | | E1-B Signal Health Status | | + +## — *StandardClockModelList* + +``` +-- ASN1START + +StandardClockModelList ::= SEQUENCE (SIZE(1..2)) OF StandardClockModelElement + +StandardClockModelElement ::= SEQUENCE { + stanClockToc INTEGER (0..16383), + stanClockAF2 INTEGER (-32..31), + stanClockAF1 INTEGER (-1048576..1048575), + stanClockAF0 INTEGER (-1073741824..1073741823), + stanClockTgd INTEGER (-512..511) OPTIONAL, -- Need ON + sisa INTEGER (0..255), + stanModelID INTEGER (0..1) OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP +``` + +### StandardClockModelList field descriptions + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| standardClockModelList | +| gnss-ClockModel Model-1 contains one or two clock model elements. If included, clock Model-1 shall be included once or twice depending on the target device capability.
If the target device is supporting multiple Galileo signals, the location server includes both F/Nav and I/Nav clock models in gnss-ClockModel if the location server assumes the target device to perform location information calculation using multiple signals. | +| stanClockToc
Parameter $t_{oc}$ defined in [8].
Scale factor 60 seconds. | +| stanClockAF2
Parameter $af_2$ defined in [8].
Scale factor $2^{-59}$ seconds/second 2 . | +| stanClockAF1
Parameter $af_1$ defined in [8].
Scale factor $2^{-46}$ seconds/second. | + +| StandardClockModelList field descriptions | | +|--------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| stanClockAf0 | Parameter $af_0$ defined in [8].
Scale factor $2^{-34}$ seconds. | +| stanClockTgd | Parameter $T_{GD}$ , Broadcast Group Delay (BGD), defined in [8].
Scale factor $2^{-32}$ seconds.
This field is required if the target device supports only single frequency Galileo signal. | +| sisa | Signal-In-Space Accuracy (SISA), defined in [8] clause 5.1.11. | +| stanModelID | This field specifies the identity of the clock model according to the table Value of stanModelID to Identity relation below. This field is required if the location server includes both F/Nav and I/Nav Galileo clock models in gnss-ClockModel . | + +### Value of *stanModelID* to Identity relation + +| Value of stanModelID | Identity | +|-----------------------------|----------------| +| 0 | I/Nav (E1,E5b) | +| 1 | F/Nav (E1,E5a) | + +### NAV-ClockModel + +``` +-- ASN1START +NAV-ClockModel ::= SEQUENCE { + navToc INTEGER (0..37799), + navaf2 INTEGER (-128..127), + navaf1 INTEGER (-32768..32767), + navaf0 INTEGER (-2097152..2097151), + navTgd INTEGER (-128..127), + ... +} +-- ASN1STOP +``` + +| NAV-ClockModel field descriptions | | +|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| navToc | Parameter $t_{oc}$ , time of clock (seconds) [4,7]
Scale factor $2^4$ seconds. | +| navaf2 | Parameter $a_{f2}$ , clock correction polynomial coefficient (sec/sec 2 ) [4,7].
Scale factor $2^{-55}$ seconds/second 2 . | +| navaf1 | Parameter $a_{f1}$ , clock correction polynomial coefficient (sec/sec) [4,7].
Scale factor $2^{-43}$ seconds/second. | +| navaf0 | Parameter $a_{f0}$ , clock correction polynomial coefficient (seconds) [4,7].
Scale factor $2^{-31}$ seconds. | +| navTgd | Parameter $T_{GD}$ , group delay (seconds) [4,7].
Scale factor $2^{-31}$ seconds. | + +### CNAV-ClockModel + +``` +-- ASN1START +CNAV-ClockModel ::= SEQUENCE { + cnavToc INTEGER (0..2015), + cnavTop INTEGER (0..2015), + cnavURA0 INTEGER (-16..15), + cnavURA1 INTEGER (0..7), + cnavURA2 INTEGER (0..7), + cnavAf2 INTEGER (-512..511), + ... +} +``` + +``` + + cnavAf1 INTEGER (-524288..524287), + cnavAf0 INTEGER (-33554432..33554431), + cnavTgd INTEGER (-4096..4095), + cnavISC1cp INTEGER (-4096..4095) OPTIONAL, -- Need ON + cnavISC1cd INTEGER (-4096..4095) OPTIONAL, -- Need ON + cnavISC1ca INTEGER (-4096..4095) OPTIONAL, -- Need ON + cnavISC12c INTEGER (-4096..4095) OPTIONAL, -- Need ON + cnavISC15i5 INTEGER (-4096..4095) OPTIONAL, -- Need ON + cnavISC15q5 INTEGER (-4096..4095) OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP + +``` + +### CNAV-ClockModel field descriptions + +#### **cnavToc** + +Parameter $t_{oc}$ , clock data reference time of week (seconds) [4,5,6,7]. + +Scale factor 300 seconds. + +#### **cnavTop** + +Parameter $t_{op}$ , clock data predict time of week (seconds) [4,5,6,7]. + +Scale factor 300 seconds + +#### **cnavURA0** + +Parameter $URA_{oc}$ Index, SV clock accuracy index (dimensionless) [4,5,6,7]. + +#### **cnavURA1** + +Parameter $URA_{oc1}$ Index, SV clock accuracy change index (dimensionless) [4,5,6,7]. + +#### **cnavURA2** + +Parameter $URA_{oc2}$ Index, SV clock accuracy change rate index (dimensionless) [4,5,6,7]. + +#### **cnavAf2** + +Parameter $a_{i2-n}$ , SV clock drift rate correction coefficient (sec/sec2) [4,5,6,7]. + +Scale factor $2^{-60}$ seconds/second2. + +#### **cnavAf1** + +Parameter $a_{i1-n}$ , SV clock drift correction coefficient (sec/sec) [4,5,6,7]. + +Scale factor $2^{-48}$ seconds/second. + +#### **cnavAf0** + +Parameter $a_{i0-n}$ , SV clock bias correction coefficient (seconds) [4,5,6,7]. + +Scale factor $2^{-35}$ seconds. + +#### **cnavTgd** + +Parameter $T_{GD}$ , Group delay correction (seconds) [4,5,6,7]. + +Scale factor $2^{-35}$ seconds. + +#### **cnavISC1cp** + +Parameter $ISC_{L1CP}$ , inter signal group delay correction (seconds) [6,7]. + +Scale factor $2^{-35}$ seconds. + +The location server should include this field if the target device is GPS capable and supports the L1C signal. + +#### **cnavISC1cd** + +Parameter $ISC_{L1CD}$ , inter signal group delay correction (seconds) [6,7]. + +Scale factor $2^{-35}$ seconds. + +The location server should include this field if the target device is GPS capable and supports the L1C signal. + +#### **cnavISC1ca** + +Parameter $ISC_{L1CA}$ , inter signal group delay correction (seconds) [4,5,7]. + +Scale factor $2^{-35}$ seconds. + +The location server should include this field if the target device is GPS capable and supports the L1CA signal. + +#### **cnavISC12c** + +Parameter $ISC_{L2C}$ , inter signal group delay correction (seconds) [4,5,7]. + +Scale factor $2^{-35}$ seconds. + +The location server should include this field if the target device is GPS capable and supports the L2C signal. + +#### **cnavISC15i5** + +Parameter $ISC_{L5i5}$ , inter signal group delay correction (seconds) [5,7]. + +Scale factor $2^{-35}$ seconds. + +The location server should include this field if the target device is GPS capable and supports the L5 signal. + +#### **cnavISC15q5** + +Parameter $ISC_{L5Q5}$ , inter signal group delay correction (seconds) [5,7]. + +Scale factor $2^{-35}$ seconds. + +The location server should include this field if the target device is GPS capable and supports the L5 signal. + +### GLONASS-ClockModel + +``` +-- ASN1START +``` + +``` + +GLONASS-ClockModel ::= SEQUENCE { + gloTau INTEGER (-2097152..2097151), + gloGamma INTEGER (-1024..1023), + gloDeltaTau INTEGER (-16..15) OPTIONAL, -- Need ON + ... +} + +``` + +``` +-- ASN1STOP +``` + +#### GLONASS-ClockModel field descriptions + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gloTau
Parameter $\tau_n(t_b)$ , satellite clock offset (seconds) [9].
Scale factor $2^{-30}$ seconds. | +| gloGamma
Parameter $\gamma_n(t_b)$ , relative frequency offset from nominal value (dimensionless) [9].
Scale factor $2^{-40}$ . | +| gloDeltaTau
Parameter $\Delta\tau_n$ , time difference between transmission in G2 and G1 (seconds) [9].
Scale factor $2^{-30}$ seconds.
The location server should include this parameter if the target device is dual frequency GLONASS receiver capable. | + +#### SBAS-ClockModel + +``` +-- ASN1START +``` + +``` + +SBAS-ClockModel ::= SEQUENCE { + sbasTo INTEGER (0..5399), + sbasAgfo INTEGER (-2048..2047), + sbasAgf1 INTEGER (-128..127), + ... +} + +``` + +``` +-- ASN1STOP +``` + +#### SBAS-ClockModel field descriptions + +| | +|----------------------------------------------------------------------------------------| +| sbasTo
Parameter $t_0$ [10].
Scale factor 16 seconds. | +| sbasAgfo
Parameter $a_{GFO}$ [10].
Scale factor $2^{-31}$ seconds. | +| sbasAgf1
Parameter $a_{GFI}$ [10].
Scale factor $2^{-40}$ seconds/second. | + +#### BDS-ClockModel + +The IE *BDS-ClockModel* is used for BDS B1I defined in [23] and BDS B3I defined in [50]. + +``` +-- ASN1START +``` + +``` + +BDS-ClockModel-r12 ::= SEQUENCE { + bdsAODC-r12 INTEGER (0..31), + bdsToc-r12 INTEGER (0..131071), + bdsA0-r12 INTEGER (-8388608..8388607), + bdsA1-r12 INTEGER (-2097152..2097151), + bdsA2-r12 INTEGER (-1024..1023), + bdsTgd1-r12 INTEGER (-512..511), + ..., + [[ bdsTgd2-r16 INTEGER (-512..511) OPTIONAL -- Need ON + ]] +} + +``` + +``` +-- ASN1STOP +``` + +| BDS-ClockModel field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bdsAODC
Parameter Age of Data, Clock (AODC), see [23], [50], Table 5-6. | +| bdsToc
Parameter $T_{oc}$ , Time of clock (seconds) [23], [50].
Scale factor $2^3$ seconds. | +| bdsA0
Parameter $a_0$ , Clock correction polynomial coefficient (seconds) [23], [50].
Scale factor $2^{-33}$ seconds. | +| bdsA1
Parameter $a_1$ , Clock correction polynomial coefficient (sec/sec) [23], [50].
Scale factor $2^{-50}$ sec/sec. | +| bdsA2
Parameter $a_2$ , Clock correction polynomial coefficient (sec/sec 2 ) [23], [50].
Scale factor $2^{-66}$ sec/sec 2 . | +| bdsTgd1
Parameter Equipment group delay differential $T_{GD1}$ [23], [50].
Scale factor is 0.1 nanosecond. | +| bdsTgd2
Parameter Equipment group delay differential $T_{GD2}$ [23], [50].
Scale factor is 0.1 nanosecond. | + +## — *BDS-ClockModel2* + +The IE *BDS-ClockModel2* is used for BDS B1C defined in [39] and BDS B2a defined in [49]. + +``` +-- ASN1START +BDS-ClockModel2-r16 ::= SEQUENCE { + bdsToc-r16 INTEGER (0..2047), + bdsA0-r16 INTEGER (-16777216..16777215), + bdsA1-r16 INTEGER (-2097152..2097151), + bdsA2-r16 INTEGER (-1024..1023), + bdsTgdB1Cp-r16 INTEGER (-2048..2047), + bdsIscB1Cd-r16 INTEGER (-2048..2047), + ..., + [[ bdsTgdB2ap-r17 INTEGER (-2048..2047) OPTIONAL, -- Need ON + bdsIscB2ad-r17 INTEGER (-2048..2047) OPTIONAL, -- Need ON + ]] +} + +-- ASN1STOP +``` + +| BDS-ClockModel2 field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bdsToc
Parameter $T_{oc}$ , Clock correction parameters reference time (seconds), see [39], 7.5.1 and [49], 7.5.1.
Scale factor 300 seconds. | +| bdsA0
Parameter $a_0$ , Satellite clock time bias correction coefficient (seconds), see [39], 7.5.1 and [49], 7.5.1.
Scale factor $2^{-34}$ seconds. | +| bdsA1
Parameter $a_1$ , Satellite clock time drift correction coefficient (sec/sec), see [39], 7.5.1 and [49], 7.5.1.
Scale factor $2^{-50}$ sec/sec. | +| bdsA2
Parameter $a_2$ , Satellite clock time drift rate correction coefficient (sec/sec 2 ), see [39], 7.5.1 and [49], 7.5.1.
Scale factor $2^{-66}$ sec/sec 2 . | +| bdsTgdB1Cp
Parameter $T_{GDB1Cp}$ Group delay differential of the B1C pilot component (seconds), see [39], 7.6.1 and [49], 7.6.1.
Scale factor is $2^{-34}$ seconds. | +| bdsIscB1Cd
Parameter $ISC_{B1Cd}$ Group delay differential between the B1C data and pilot components (seconds), see [39], 7.6.1.
Scale factor is $2^{-34}$ seconds. | +| bdsTgdB2ap
Parameter $T_{GDB2ap}$ Group delay differential of the B2a pilot component (seconds), see [39], 7.6.1 and [49], 7.6.1.
Scale factor is $2^{-34}$ seconds. | +| bdsIscB2ad
Parameter $ISC_{B2ad}$ Group delay differential between the B2a data and pilot components (seconds), see [49], 7.6.1.
Scale factor is $2^{-34}$ seconds. | + +## NavIC-ClockModel + +``` +-- ASN1START + +NavIC-ClockModel-r16 ::= SEQUENCE { + navic-Toc-r16 INTEGER (0..65535), + navic-af2-r16 INTEGER (-128..127), + navic-af1-r16 INTEGER (-32768..32767), + navic-af0-r16 INTEGER (-2097152..2097151), + navic-Tgd-r16 INTEGER (-128..127), + ... +} + +-- ASN1STOP +``` + +| NavIC-ClockModel field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| navic-Toc
Parameter $t_{oc}$ , time of clock (seconds) [38], Table-11.
Scale factor $2^4$ seconds. | +| navic-af2
Parameter $a_2$ , clock correction polynomial coefficient (sec/sec 2 ) [38].
Scale factor $2^{-55}$ seconds/second 2 . | +| navic-af1
Parameter $a_1$ , clock correction polynomial coefficient (sec/sec) [38].
Scale factor $2^{-43}$ seconds/second. | +| navic-af0
Parameter $a_0$ , clock correction polynomial coefficient (seconds) [38].
Scale factor $2^{-31}$ seconds. | +| navic-Tgd
Parameter $T_{GD}$ , group delay (seconds) [38].
Scale factor $2^{-31}$ seconds. | + +## NavModelKeplerianSet + +``` +-- ASN1START + +NavModelKeplerianSet ::= SEQUENCE { + keplerToe INTEGER (0 .. 16383), + keplerW INTEGER (-2147483648..2147483647), +} +``` + +``` + +keplerDeltaN INTEGER (-32768..32767), +keplerM0 INTEGER (-2147483648..2147483647), +keplerOmegaDot INTEGER (-8388608.. 8388607), +keplerE INTEGER (0..4294967295), +keplerIDot INTEGER (-8192..8191), +keplerAPowerHalf INTEGER (0.. 4294967295), +keplerI0 INTEGER (-2147483648..2147483647), +keplerOmega0 INTEGER (-2147483648..2147483647), +keplerCrs INTEGER (-32768..32767), +keplerCis INTEGER (-32768..32767), +keplerCus INTEGER (-32768..32767), +keplerCrc INTEGER (-32768..32767), +keplerCic INTEGER (-32768..32767), +keplerCuc INTEGER (-32768..32767), +... +} + +-- ASN1STOP + +``` + +**NavModelKeplerianSet field descriptions** + +| | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| keplerToe | Parameter $t_{oe}$ , time-of-ephemeris in seconds [8].
Scale factor 60 seconds. | +| keplerW | Parameter $\omega$ , argument of perigee (semi-circles) [8].
Scale factor $2^{-31}$ semi-circles. | +| keplerDeltaN | Parameter $\Delta n$ , mean motion difference from computed value (semi-circles/sec) [8].
Scale factor $2^{-43}$ semi-circles/second. | +| keplerM0 | Parameter $M_0$ , mean anomaly at reference time (semi-circles) [8].
Scale factor $2^{-31}$ semi-circles. | +| keplerOmegaDot | Parameter OMEGAdot, rate of change of right ascension (semi-circles/sec) [8].
Scale factor $2^{-43}$ semi-circles/second. | +| keplerE | Parameter $e$ , eccentricity [8].
Scale factor $2^{-33}$ . | +| keplerIDot | Parameter Idot, rate of change of inclination angle (semi-circles/sec) [8].
Scale factor $2^{-43}$ semi-circles/second. | +| keplerAPowerHalf | Parameter sqrtA, square root of semi-major Axis in (metres) 1/2 [8].
Scale factor $2^{-19}$ metres 1/2 . | +| keplerI0 | Parameter $i_0$ , inclination angle at reference time (semi-circles) [8].
Scale factor $2^{-31}$ semi-circles. | +| keplerOmega0 | Parameter OMEGA $_0$ , longitude of ascending node of orbit plane at weekly epoch (semi-circles) [8].
Scale factor $2^{-31}$ semi-circles. | +| keplerCrs | Parameter $C_{rs}$ , amplitude of the sine harmonic correction term to the orbit radius (metres) [8].
Scale factor $2^{-5}$ metres. | +| keplerCis | Parameter $C_{is}$ , amplitude of the sine harmonic correction term to the angle of inclination (radians) [8].
Scale factor $2^{-29}$ radians. | +| keplerCus | Parameter $C_{us}$ , amplitude of the sine harmonic correction term to the argument of latitude (radians) [8].
Scale factor $2^{-29}$ radians. | +| keplerCrc | Parameter $C_{rc}$ , amplitude of the cosine harmonic correction term to the orbit radius (metres) [8].
Scale factor $2^{-5}$ metres. | +| keplerCic | Parameter $C_{ic}$ , amplitude of the cosine harmonic correction term to the angle of inclination (radians) [8].
Scale factor $2^{-29}$ radians. | + +| NavModelKeplerianSet field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| keplerCuc
Parameter $C_{uc}$ , amplitude of the cosine harmonic correction term to the argument of latitude (radians) [8].
Scale factor $2^{29}$ radians. | + +## NavModelNAV-KeplerianSet + +``` + +-- ASN1START + +NavModelNAV-KeplerianSet ::= SEQUENCE { + navURA INTEGER (0..15), + navFitFlag INTEGER (0..1), + navToe INTEGER (0..37799), + navOmega INTEGER (-2147483648..2147483647), + navDeltaN INTEGER (-32768..32767), + navM0 INTEGER (-2147483648..2147483647), + navOmegaADot INTEGER (-8388608..8388607), + navE INTEGER (0..4294967295), + navIDot INTEGER (-8192..8191), + navAPowerHalf INTEGER (0..4294967295), + navI0 INTEGER (-2147483648..2147483647), + navOmegaA0 INTEGER (-2147483648..2147483647), + navCrs INTEGER (-32768..32767), + navCis INTEGER (-32768..32767), + navCus INTEGER (-32768..32767), + navCrc INTEGER (-32768..32767), + navCic INTEGER (-32768..32767), + navCuc INTEGER (-32768..32767), + addNAVparam SEQUENCE { + ephemCodeOnL2 INTEGER (0..3), + ephemL2Pflag INTEGER (0..1), + ephemSF1Rsvd SEQUENCE { + reserved1 INTEGER (0..8388607), -- 23-bit field + reserved2 INTEGER (0..16777215), -- 24-bit field + reserved3 INTEGER (0..16777215), -- 24-bit field + reserved4 INTEGER (0..65535) -- 16-bit field + }, + ephemAODA INTEGER (0..31) + } OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP + +``` + +| NavModelNAV-KeplerianSet field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| navURA
Parameter URA Index, SV accuracy (dimensionless) [4,7]. | +| navFitFlag
Parameter Fit Interval Flag, fit interval indication (dimensionless) [4,7] | +| navToe
Parameter $t_{oe}$ , time of ephemeris (seconds) [4,7].
Scale factor $2^4$ seconds. | +| navOmega
Parameter $\omega$ , argument of perigee (semi-circles) [4,7].
Scale factor $2^{31}$ semi-circles. | +| navDeltaN
Parameter $\Delta n$ , mean motion difference from computed value (semi-circles/sec) [4,7].
Scale factor $2^{43}$ semi-circles/second. | +| navM0
Parameter $M_0$ , mean anomaly at reference time (semi-circles) [4,7].
Scale factor $2^{31}$ semi-circles. | +| navOmegaADot
Parameter $\dot{\Omega}$ , rate of right ascension (semi-circles/sec) [4,7].
Scale factor $2^{43}$ semi-circles/second. | +| navE
Parameter $e$ , eccentricity (dimensionless) [4,7].
Scale factor $2^{33}$ . | + +| NavModelNAV-KeplerianSet field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| navIDot
Parameter IDOT, rate of inclination angle (semi-circles/sec) [4,7].
Scale factor $2^{-43}$ semi-circles/second. | +| navAPowerHalf
Parameter $a$ , square root of semi-major axis (metres $^{1/2}$ ) [4,7].
Scale factor $2^{-19}$ metres $^{1/2}$ . | +| navI0
Parameter $i_0$ , inclination angle at reference time (semi-circles) [4,7].
Scale factor $2^{-31}$ semi-circles. | +| navOmegaA0
Parameter $\Omega_0$ , longitude of ascending node of orbit plane at weekly epoch (semi-circles) [4,7].
Scale factor $2^{-31}$ semi-circles. | +| navCrs
Parameter $C_{rs}$ , amplitude of sine harmonic correction term to the orbit radius (metres) [4,7].
Scale factor $2^{-5}$ metres. | +| navCis
Parameter $C_{is}$ , amplitude of sine harmonic correction term to the angle of inclination (radians) [4,7].
Scale factor $2^{-29}$ radians. | +| navCus
Parameter $C_{us}$ , amplitude of sine harmonic correction term to the argument of latitude (radians) [4,7].
Scale factor $2^{-29}$ radians. | +| navCrc
Parameter $C_{rc}$ , amplitude of cosine harmonic correction term to the orbit radius (metres) [4,7].
Scale factor $2^{-5}$ metres. | +| navCic
Parameter $C_{ic}$ , amplitude of cosine harmonic correction term to the angle of inclination (radians) [4,7].
Scale factor $2^{-29}$ radians. | +| navCuc
Parameter $C_{uc}$ , amplitude of cosine harmonic correction term to the argument of latitude (radians) [4,7].
Scale factor $2^{-29}$ radians. | +| addNAVparam
These fields include data and reserved bits in the GPS NAV message [4,14].
These additional navigation parameters, if provided by the location server, allow the target device to perform data wipe-off similar to what is done by the target device with the GNSS-DataBitAssistance . | + +## NavModelCNAV-KeplerianSet + +``` +-- ASN1START +NavModelCNAV-KeplerianSet ::= SEQUENCE { + cnavTop INTEGER (0..2015), + cnavURAindex INTEGER (-16..15), + cnavDeltaA INTEGER (-33554432..33554431), + cnavAdot INTEGER (-16777216..16777215), + cnavDeltaNo INTEGER (-65536..65535), + cnavDeltaNoDot INTEGER (-4194304..4194303), + cnavMo INTEGER (-4294967296..4294967295), + cnavE INTEGER (0..8589934591), + cnavOmega INTEGER (-4294967296..4294967295), + cnavOMEGA0 INTEGER (-4294967296..4294967295), + cnavDeltaOmegaDot INTEGER (-65536..65535), + cnavIo INTEGER (-4294967296..4294967295), + cnavIoDot INTEGER (-16384..16383), + cnavCis INTEGER (-32768..32767), + cnavCic INTEGER (-32768..32767), + cnavCrs INTEGER (-8388608..8388607), + cnavCrc INTEGER (-8388608..8388607), + cnavCus INTEGER (-1048576..1048575), + cnavCuc INTEGER (-1048576..1048575), + ... +} + +-- ASN1STOP +``` + +| NavModelCNAV-KeplerianSet field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cnavTop
Parameter $t_{op}$ , data predict time of week (seconds) [4,5,6,7].
Scale factor 300 seconds. | +| cnavURAindex
Parameter $URA_{oe}$ Index, SV accuracy (dimensionless) [4,5,6,7]. | +| cnavDeltaA
Parameter $\Delta A$ , semi-major axis difference at reference time (metres) [4,5,6,7].
Scale factor $2^{-9}$ metres. | +| cnavAdot
Parameter $\dot{a}$ , change rate in semi-major axis (metres/second) [4,5,6,7].
Scale factor $2^{-21}$ metres/second. | +| cnavDeltaNo
Parameter $\Delta n_0$ , mean motion difference from computed value at reference time (semi-circles/sec) [4,5,6,7].
Scale factor $2^{-44}$ semi-circles/second. | +| cnavDeltaNoDot
Parameter $\dot{\Delta n}$ , rate of mean motion difference from computed value (semi-circles/sec 2 ) [4,5,6,7].
Scale factor $2^{-57}$ semi-circles/second 2 . | +| cnavMo
Parameter $M_{0-n}$ , mean anomaly at reference time (semi-circles) [4,5,6,7].
Scale factor $2^{-32}$ semi-circles. | +| cnavE
Parameter $e_n$ , eccentricity (dimensionless) [4,5,6,7].
Scale factor $2^{-34}$ . | +| cnavOmega
Parameter $\omega_n$ , argument of perigee (semi-circles) [4,5,6,7].
Scale factor $2^{-32}$ semi-circles. | +| cnavOMEGA0
Parameter $\Omega_{0-n}$ , reference right ascension angle (semi-circles) [4,5,6,7].
Scale factor $2^{-32}$ semi-circles. | +| cnavDeltaOmegaDot
Parameter $\dot{\Omega}$ , rate of right ascension difference (semi-circles/sec) [4,5,6,7].
Scale factor $2^{-44}$ semi-circles/second. | +| cnavIo
Parameter $i_{0-n}$ , inclination angle at reference time (semi-circles) [4,5,6,7].
Scale factor $2^{-32}$ semi-circles. | +| cnavIoDot
Parameter $\dot{i}_{0-n}$ DOT, rate of inclination angle (semi-circles/sec) [4,5,6,7].
Scale factor $2^{-44}$ semi-circles/second. | +| cnavCis
Parameter $C_{is-n}$ , amplitude of sine harmonic correction term to the angle of inclination (radians) [4,5,6,7].
Scale factor $2^{-30}$ radians. | +| cnavCic
Parameter $C_{ic-n}$ , amplitude of cosine harmonic correction term to the angle of inclination (radians) [4,5,6,7].
Scale factor $2^{-30}$ radians. | +| cnavCrs
Parameter $C_{rs-n}$ , amplitude of sine harmonic correction term to the orbit radius (metres) [4,5,6,7].
Scale factor $2^{-8}$ metres. | +| cnavCrc
Parameter $C_{rc-n}$ , amplitude of cosine harmonic correction term to the orbit radius (metres) [4,5,6,7].
Scale factor $2^{-8}$ metres. | +| cnavCus
Parameter $C_{us-n}$ , amplitude of the sine harmonic correction term to the argument of latitude (radians) [4,5,6,7].
Scale factor $2^{-30}$ radians. | +| cnavCuc
Parameter $C_{uc-n}$ , amplitude of cosine harmonic correction term to the argument of latitude (radians) [4,5,6,7].
Scale factor $2^{-30}$ radians. | + +## – *NavModel-GLONASS-ECEF* + +``` +-- ASN1START +NavModel-GLONASS-ECEF ::= SEQUENCE { + gloEn INTEGER (0..31), + gloP1 BIT STRING (SIZE(2)), + gloP2 BOOLEAN, + gloM INTEGER (0..3), +``` + +``` + +gloX INTEGER (-67108864..67108863), +gloXdot INTEGER (-8388608..8388607), +gloXdotdot INTEGER (-16..15), +gloY INTEGER (-67108864..67108863), +gloYdot INTEGER (-8388608..8388607), +gloYdotdot INTEGER (-16..15), +gloZ INTEGER (-67108864..67108863), +gloZdot INTEGER (-8388608..8388607), +gloZdotdot INTEGER (-16..15), +... +} + +-- ASN1STOP + +``` + +### NavModel-GLONASS-ECEF field descriptions + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gloEn | Parameter E n , age of data (days) [9].
Scale factor 1 days. | +| gloP1 | Parameter P1, time interval between two adjacent values of t b (minutes) [9]. | +| gloP2 | Parameter P2, change of t b flag (dimensionless) [9]. | +| gloM | Parameter M, type of satellite (dimensionless) [9]. | +| gloX | Parameter , x-coordinate of satellite at time t b (kilometres) [9].
Scale factor 2 -11 kilometres. | +| gloXdot | Parameter , x-coordinate of satellite velocity at time t b (kilometres/second) [9].
Scale factor 2 -20 kilometres/second. | +| gloXdotdot | Parameter , x-coordinate of satellite acceleration at time t b (kilometres/second 2 ) [9].
Scale factor 2 -30 kilometres/second 2 . | +| gloY | Parameter , y-coordinate of satellite at time t b (kilometres) [9].
Scale factor 2 -11 kilometres. | +| gloYdot | Parameter , y-coordinate of satellite velocity at time t b (kilometres/second) [9].
Scale factor 2 -20 kilometres/second. | +| gloYdotdot | Parameter , y-coordinate of satellite acceleration at time t b (kilometres/second 2 ) [9].
Scale factor 2 -30 kilometres/second 2 . | +| gloZ | Parameter , z-coordinate of satellite at time t b (kilometres) [9].
Scale factor 2 -11 kilometres. | +| gloZdot | Parameter , z-coordinate of satellite velocity at time t b (kilometres/second) [9].
Scale factor 2 -20 kilometres/second. | +| gloZdotdot | Parameter , z-coordinate of satellite acceleration at time t b (kilometres/second 2 ) [9].
Scale factor 2 -30 kilometres/second 2 . | + +### NavModel-SBAS-ECEF + +``` + +-- ASN1START + +NavModel-SBAS-ECEF ::= SEQUENCE { + sbasTo INTEGER (0..5399) OPTIONAL, -- Cond ClockModel + sbasAccuracy BIT STRING (SIZE(4)), + sbasXg INTEGER (-536870912..536870911), + sbasYg INTEGER (-536870912..536870911), + sbasZg INTEGER (-16777216..16777215), + sbasXgDot INTEGER (-65536..65535), + sbasYgDot INTEGER (-65536..65535), + sbasZgDot INTEGER (-131072..131071), + sbasXgDotDot INTEGER (-512..511), + sbagYgDotDot INTEGER (-512..511), + sbaszgDotDot INTEGER (-512..511), + ... +} + +``` + +``` +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------| +| ClockModel | This field is mandatory present if gnss-ClockModel Model-5 is not included; otherwise it is not present. | + +| NavModel-SBAS-ECEF field descriptions | | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| sbasTo | Parameter $t_0$ , time of applicability (seconds) [10].
Scale factor 16 seconds. | +| sbasAccuracy | Parameter Accuracy, (dimensionless) [10]. | +| sbasXg | Parameter $X_G$ , (metres) [10].
Scale factor 0.08 metres. | +| sbasYg | Parameter $Y_G$ , (metres) [10].
Scale factor 0.08 metres. | +| sbasZg | Parameter $Z_G$ , (metres) [10].
Scale factor 0.4 metres. | +| sbasXgDot | Parameter $X_G$ , Rate-of-Change, (metres/second) [10].
Scale factor 0.000625 metres/second. | +| sbasYgDot | Parameter $Y_G$ , Rate-of-Change, (metres/second) [10].
Scale factor 0.000625 metres/second. | +| sbasZgDot | Parameter $Z_G$ , Rate-of-Change, (metres/second) [10].
Scale factor 0.004 metres/second. | +| sbasXgDotDot | Parameter $X_G$ , Acceleration, (metres/second 2 ) [10].
Scale factor 0.0000125 metres/second 2 . | +| sbasYgDotDot | Parameter $Y_G$ , Acceleration, (metres/second 2 ) [10].
Scale factor 0.0000125 metres/second 2 . | +| sbasZgDotDot | Parameter $Z_G$ , Acceleration, (metres/second 2 ) [10].
Scale factor 0.0000625 metres/second 2 . | + +## – NavModel-BDS-KeplerianSet + +The IE *NavModel-BDS-KeplerianSet* is used for BDS BII defined in [23], [50]. + +``` +-- ASN1START +NavModel-BDS-KeplerianSet-r12 ::= SEQUENCE { + bdsAODE-r12 INTEGER (0..31), + bdsURAI-r12 INTEGER (0..15), + bdsToe-r12 INTEGER (0..131071), + bdsAPowerHalf-r12 INTEGER (0..4294967295), + bdsE-r12 INTEGER (0..4294967295), + bdsW-r12 INTEGER (-2147483648..2147483647), + bdsDeltaN-r12 INTEGER (-32768..32767), + bdsM0-r12 INTEGER (-2147483648..2147483647), + bdsOmega0-r12 INTEGER (-2147483648..2147483647), + bdsOmegaDot-r12 INTEGER (-8388608..8388607), + bdsI0-r12 INTEGER (-2147483648..2147483647), + bdsIDot-r12 INTEGER (-8192..8191), + bdsCuc-r12 INTEGER (-131072..131071), + bdsCus-r12 INTEGER (-131072..131071), + bdsCrc-r12 INTEGER (-131072..131071), + bdsCrs-r12 INTEGER (-131072..131071), + bdsCic-r12 INTEGER (-131072..131071), + bdsCis-r12 INTEGER (-131072..131071), +} +``` + +``` + + ... +} + +-- ASN1STOP + +``` + +| NavModel-BDS-KeplerianSet field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bdsAODE
Parameter Age of Data, Ephemeris (AODE), see [23], [50], Table 5-8. | +| bdsURA1
Parameter URA Index, URA is used to describe the signal-in-space accuracy in metres as defined in [23], [50]. | +| bdsToe
Parameter $t_{oe}$ , Ephemeris reference time (seconds) [23], [50].
Scale factor $2^3$ seconds. | +| bdsAPowerHalf
Parameter $A^{1/2}$ , Square root of semi-major axis (metres 2 ) [23], [50].
Scale factor $2^{-19}$ metres 2 . | +| bdsE
Parameter $e$ , Eccentricity, dimensionless [23], [50].
Scale factor $2^{-33}$ . | +| bdsW
Parameter $\omega$ , Argument of perigee (semi-circles) [23], [50].
Scale factor $2^{-31}$ semi-circles. | +| bdsDeltaN
Parameter $\Delta n$ , Mean motion difference from computed value (semi-circles/sec) [23], [50].
Scale factor $2^{-43}$ semi-circles/second. | +| bdsM0
Parameter $M_0$ , Mean anomaly at reference time (semi-circles) [23], [50].
Scale factor $2^{-31}$ semi-circles. | +| bdsOmega0
Parameter $\Omega_0$ , Longitude of ascending node of orbital of plane computed according to reference time (semi-circles) [23], [50].
Scale factor $2^{-31}$ semi-circles. | +| bdsOmegaDot
Parameter $\dot{\Omega}$ , Rate of right ascension (semi-circles/sec) [23], [50].
Scale factor $2^{-43}$ semi-circles/second. | +| bdsI0
Parameter $i_0$ , Inclination angle at reference time (semi-circles) [23], [50].
Scale factor $2^{-31}$ semi-circles. | +| bdsIDot
Parameter $\dot{I}$ , Rate of inclination angle (semi-circles/sec) [23], [50].
Scale factor $2^{-43}$ semi-circles/second. | +| bdsCuc
Parameter $C_{uc}$ , Amplitude of cosine harmonic correction term to the argument of latitude (radians) [23], [50].
Scale factor $2^{-31}$ radians. | +| bdsCus
Parameter $C_{us}$ , Amplitude of sine harmonic correction term to the argument of latitude (radians) [23], [50].
Scale factor $2^{-31}$ radians. | +| bdsCrc
Parameter $C_{rc}$ , Amplitude of cosine harmonic correction term to the orbit radius (metres) [23], [50].
Scale factor $2^{-6}$ metres. | +| bdsCrs
Parameter $C_{rs}$ , Amplitude of sine harmonic correction term to the orbit radius (metres) [23], [50].
Scale factor $2^{-6}$ metres. | +| bdsCic
Parameter $C_{ic}$ , Amplitude of cosine harmonic correction term to the angle of inclination (radians) [23], [50].
Scale factor $2^{-31}$ radians. | +| bdsCis
Parameter $C_{is}$ , Amplitude of sine harmonic correction term to the angle of inclination (radians) [23], [50].
Scale factor $2^{-31}$ radians. | + +## — *NavModel-BDS-KeplerianSet2* + +The IE *NavModel-BDS-KeplerianSet2* is used for BDS B1C and BDS B2a defined in [39], [49]. + +``` +-- ASN1START + +NavModel-BDS-KeplerianSet2-r16 ::= SEQUENCE { + bdsIODE-r16 INTEGER (0..255), + bdsToe-r16 INTEGER (0..2047), + bdsDeltaA-r16 INTEGER (-33554432..33554431), + bdsAdot-r16 INTEGER (-16777216..16777216), + bdsDeltaN0-r16 INTEGER (-65536..65535), + bdsDeltaN0dot-r16 INTEGER (-4194304..4194303), + bdsM0-r16 INTEGER (-4294967296..4294967295), + bdsE-r16 INTEGER (0..8589934591), + bdsOmega-r16 INTEGER (-4294967296..4294967295), + bdsOmega0-r16 INTEGER (-4294967296..4294967295), + bdsI0-r16 INTEGER (-4294967296..4294967295), + bdsOmegaDot-r16 INTEGER (-262144..262143), + bdsI0Dot-r16 INTEGER (-16384..16383), + bdsCuc-r16 INTEGER (-1048576..1048575), + bdsCus-r16 INTEGER (-1048576..1048575), + bdsCrc-r16 INTEGER (-8388608..8388607), + bdsCrs-r16 INTEGER (-8388608..8388607), + bdsCic-r16 INTEGER (-32768..32767), + bdsCis-r16 INTEGER (-32768..32767), + ... +} + +-- ASN1STOP +``` + +| NavModel-BDS-KeplerianSet2 field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bdsIODE
Parameter, Issue Of Data, Ephemeris (IODE), see [39], 7.4.1 and [49], 7.4.1. | +| bdsToe
Parameter $t_{oe}$ , Ephemeris reference time (seconds), defined in [39], 7.7.1 and [49], 7.7.1.
Scale factor 300 seconds. | +| bdsDeltaA
Parameter $\Delta A$ , Semi-major axis difference at reference time (metre), defined in [39], 7.7.1 and [49], 7.7.1.
Scale factor $2^{-9}$ metres. | +| bdsAdot
Parameter , Change rate in semi-major axis (metre/second), defined in [39], 7.7.1 and [49], 7.7.1.
Scale factor $2^{-21}$ metre/second.
The value 16777216 is not signalled. | +| bdsDeltaN0
Parameter $\Delta n_0$ , Mean motion difference from computed value at reference time (semi-circles /sec), defined in [39], 7.7.1 and [49], 7.7.1.
Scale factor $2^{-44}$ semi-circles /second. | +| bdsDeltaN0dot
Parameter $\Delta n_{0dot}$ , Rate of mean motion difference from computed value at reference time (semi-circles /sec 2 ), defined in [39], 7.7.1 and [49], 7.7.1.
Scale factor $2^{-57}$ semi-circles /second 2 . | +| bdsM0
Parameter $M_0$ , Mean anomaly at reference time (semi-circles) [39], [49].
Scale factor $2^{-32}$ semi-circles. | +| bdsE
Parameter $e$ , Eccentricity [39], [49].
Scale factor $2^{-34}$ . | +| bdsOmega
Parameter , Argument of perigee (semi-circles) [39], [49].
Scale factor $2^{-32}$ semi-circles. | +| bdsOmega0
Parameter $\Omega_0$ , Longitude of ascending node of orbital plane at weekly epoch (semi-circles) [39], [49].
Scale factor $2^{-32}$ semi-circles. | +| bdsI0
Parameter $i_0$ , Inclination angle at reference time (semi-circles) [39], [49].
Scale factor $2^{-32}$ semi-circles. | +| bdsOmegaDot
Parameter , Rate of right ascension (semi-circles/sec) [39], [49].
Scale factor $2^{-44}$ semi-circles/second. | +| bdsI0Dot
Parameter $i_{0dot}$ , Rate of inclination angle (semi-circles/sec) [39], [49].
Scale factor $2^{-44}$ semi-circles/second. | +| bdsCuc
Parameter $C_{uc}$ , Amplitude of cosine harmonic correction to the argument of latitude (radians) [39], [49].
Scale factor $2^{-30}$ radians. | +| bdsCus
Parameter $C_{us}$ , Amplitude of sine harmonic correction to the argument of latitude (radians) [39], [49].
Scale factor $2^{-30}$ radians. | +| bdsCrc
Parameter $C_{rc}$ , Amplitude of cosine harmonic correction term to the orbit radius (metres) [39], [49].
Scale factor $2^{-8}$ metres. | +| bdsCrs
Parameter $C_{rs}$ , Amplitude of sine harmonic correction term to the orbit radius (metres) [39], [49].
Scale factor $2^{-8}$ metres. | +| bdsCic
Parameter $C_{ic}$ , Amplitude of cosine harmonic correction term to the angle of inclination (radians) [39], [49].
Scale factor $2^{-30}$ radians. | +| bdsCis
Parameter $C_{is}$ , Amplitude of sine harmonic correction term to the angle of inclination (radians) [39], [49].
Scale factor $2^{-30}$ radians. | + +— ***NavModel-NavIC-KeplerianSet*** + +-- ASN1START + +``` + +NavModel-NavIC-KeplerianSet-r16 ::= SEQUENCE { + navic-Toe-r16 INTEGER (0..65536), + navic-URAI-r16 INTEGER (0..15), + navic-W-r16 INTEGER (-2147483648..2147483647), + navic-DeltaN-r16 INTEGER (-2097152..2097151), + navic-M0-r16 INTEGER (-2147483648..2147483647), + navic-OmegaDot-r16 INTEGER (-2147483648..2147483647), + navic-E-r16 INTEGER (0..4294967295), + navic-IDot-r16 INTEGER (-8192..8191), + navic-APowerHalf-r16 INTEGER (0..4294967295), + navic-I0-r16 INTEGER (-2147483648..2147483647), + navic-Omega0-r16 INTEGER (-2147483648..2147483647), + navic-Crs-r16 INTEGER (-32768..32767), + navic-Cis-r16 INTEGER (-32768..32767), + navic-Cus-r16 INTEGER (-32768..32767), + navic-Crc-r16 INTEGER (-32768..32767), + navic-Cic-r16 INTEGER (-32768..32767), + navic-Cuc-r16 INTEGER (-32768..32767), + ... +} + +-- ASN1STOP + +``` + +**NavModel-NavIC-KeplerianSet field descriptions** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| navic-Toe
Parameter $t_{oe}$ , time-of-ephemeris in seconds [38].
Scale factor $2^4$ seconds. | +| navic-URAI
Parameter User Range Accuracy Index (in metres). This is a one-sigma estimate of the user range errors in the navigation data for the transmitting satellite as described under clause 6.2.1.4 in [38] | +| navic-W
Parameter $\omega$ , argument of perigee (semi-circles) [38].
Scale factor $2^{31}$ semi-circles. | +| navic-DeltaN
Parameter $\Delta n$ , mean motion difference from computed value (semi-circles/sec) [38]
Scale factor $2^{41}$ semi-circles/second | +| navic-M0
Parameter $M_0$ , mean anomaly at reference time (semi-circles) [38]
Scale factor $2^{31}$ semi-circles. | +| navic-OmegaDot
Parameter OMEGAAdot, rate of change of right ascension (semi-circles/sec) [38]
Scale factor $2^{41}$ semi-circles/second | +| navic-E
Parameter $e$ , eccentricity [38]
Scale factor $2^{33}$ . | +| navic-IDot
Parameter $\dot{I}$ , rate of change of inclination angle (semi-circles/sec) [38]
Scale factor $2^{43}$ semi-circles/second. | +| navic-APowerHalf
Parameter $\sqrt{A}$ , square root of semi-major Axis in (metres) 1/2 [38]
Scale factor $2^{19}$ metres 1/2 . | +| navic-I0
Parameter $i_0$ , inclination angle at reference time (semi-circles) [38]
Scale factor $2^{31}$ semi-circles. | +| navic-Omega0
Parameter OMEGA 0 , longitude of ascending node of orbit plane at weekly epoch (semi-circles) [38]
Scale factor $2^{31}$ semi-circles. | +| navic-Crs
Parameter $C_{rs}$ , amplitude of the sine harmonic correction term to the orbit radius (metres) [38]
Scale factor $2^4$ metres | +| navic-Cis
Parameter $C_{is}$ , amplitude of the sine harmonic correction term to the angle of inclination (radians) [38]
Scale factor $2^{28}$ radians | +| navic-Cus
Parameter $C_{us}$ , amplitude of the sine harmonic correction term to the argument of latitude (radians) [38]
Scale factor $2^{28}$ radians | + +| NavModel-NavIC-KeplerianSet field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| navic-Crc
Parameter $C_{rc}$ , amplitude of the cosine harmonic correction term to the orbit radius (metres) [38]
Scale factor $2^{-4}$ metres | +| navic-Cic
Parameter $C_{ic}$ , amplitude of the cosine harmonic correction term to the angle of inclination (radians) [38]
Scale factor $2^{-28}$ radians | +| navic-Cuc
Parameter $C_{uc}$ , amplitude of the cosine harmonic correction term to the argument of latitude (radians) [38]
Scale factor $2^{-28}$ radians | + +## – GNSS-RealTimeIntegrity + +The IE *GNSS-RealTimeIntegrity* is used by the location server to provide parameters that describe the real-time status of the GNSS constellations. *GNSS-RealTimeIntegrity* data communicates the health of the GNSS signals to the mobile in real-time. + +The location server always transmits the *GNSS-RealTimeIntegrity* with the current list of unhealthy signals (i.e., not only for signals/SVs currently visible at the reference location), for any GNSS positioning attempt and whenever GNSS assistance data are sent. If the number of bad signals is zero, then the *GNSS-RealTimeIntegrity* IE is omitted. + +NOTE 1: If GNSS integrity assistance data are provided (i.e., any of *GNSS-Integrity-ServiceParameters*, *GNSS-Integrity-ServiceAlert*, *ORBIT-IntegrityParameters*, *SSR-IntegrityOrbitBounds*, *CLOCK-IntegrityParameters*, *SSR-IntegrityClockBounds*, *SSR-IntegrityCodeBiasBounds*, *SSR-IntegrityPhaseBiasBounds*, *STEC-IntegrityParameters*, *STEC-IntegrityErrorBounds*, *SSR-GriddedCorrectionIntegrityParameters*, *TropoDelayIntegrityErrorBounds*) the following interpretation of the IE *GNSS-RealTimeIntegrity* applies: + +- Absence of the IE *GNSS-RealTimeIntegrity* indicates DNU=FALSE according to the Integrity Principle of Operation specified in clause 8.1.1a of TS 38.305 [40] for all GNSS satellites for which integrity assistance data are provided. +- Presence of the IE *GNSS-RealTimeIntegrity* for a GNSS satellite and signal combination indicates DNU=TRUE for this GNSS satellite and signal combination according to the Integrity Principle of Operation specified in clause 8.1.1a of TS 38.305 [40]. + +NOTE 2: The UE assumes that only those satellites for which the GNSS integrity assistance data are provided are monitored by the network and can be used for integrity related applications. + +``` +-- ASN1START + +GNSS-RealTimeIntegrity ::= SEQUENCE { + gnss-BadSignalList GNSS-BadSignalList, + ... +} + +GNSS-BadSignalList ::= SEQUENCE (SIZE(1..64)) OF BadSignalElement + +BadSignalElement ::= SEQUENCE { + badSVID SV-ID, + badSignalID GNSS-SignalIDs OPTIONAL, -- Need OP + ... +} + +-- ASN1STOP +``` + +| GNSS-RealTimeIntegrity field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-BadSignalList
This field specifies a list of satellites with bad signal or signals. | +| badSVID
This field specifies the GNSS SV-ID of the satellite with bad signal or signals. | +| badSignalID
This field identifies the bad signal or signals of a satellite. This is represented by a bit string in GNSS-SignalIDs , with a one-value at a bit position means the particular GNSS signal type of the SV is unhealthy; a zero-value means healthy. Absence of this field means that all signals on the specific SV are bad. | + +## GNSS-DataBitAssistance + +The IE *GNSS-DataBitAssistance* is used by the location server to provide data bit assistance data for specific satellite signals for data wipe-off. The data bits included in the assistance data depends on the GNSS and its signal. + +``` +-- ASN1START + +GNSS-DataBitAssistance ::= SEQUENCE { + gnss-TOD INTEGER (0..3599), + gnss-TODfrac INTEGER (0..999) OPTIONAL, -- Need ON + gnss-DataBitsSatList GNSS-DataBitsSatList, + ... +} + +GNSS-DataBitsSatList ::= SEQUENCE (SIZE(1..64)) OF GNSS-DataBitsSatElement + +GNSS-DataBitsSatElement ::= SEQUENCE { + svID SV-ID, + gnss-DataBitsSgnList GNSS-DataBitsSgnList, + ... +} + +GNSS-DataBitsSgnList ::= SEQUENCE (SIZE(1..8)) OF GNSS-DataBitsSgnElement + +GNSS-DataBitsSgnElement ::= SEQUENCE { + gnss-SignalType GNSS-SignalID, + gnss-DataBits BIT STRING (SIZE (1..1024)), + ... +} + +-- ASN1STOP +``` + +### GNSS-DataBitAssistance field descriptions + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-TOD
This field specifies the reference time of the first bit of the data in GNSS-DataBitAssistance in integer seconds in GNSS specific system time, modulo 1 hour.
Scale factor 1 second. | +| gnss-TODfrac
This field specifies the fractional part of the gnss-TOD in 1-milli-second resolution.
Scale factor 1 millisecond. The total GNSS TOD is gnss-TOD + gnss-TODfrac . | +| gnss-DataBitsSatList
This list specifies the data bits for a particular GNSS satellite SV-ID and signal GNSS-SignalID . | +| svID
This field specifies the GNSS SV-ID of the satellite for which the GNSS-DataBitAssistance is given. | +| gnss-SignalType
This field identifies the GNSS signal type of the GNSS-DataBitAssistance . | + +**GNSS-DataBitAssistance field descriptions****gnss-DataBits** + +Data bits are contained in GNSS system and data type specific format. + +In the case of GPS L1 C/A, it contains the NAV data modulation bits as defined in [4] . + +In the case of Modernized GPS L1C, it contains the encoded and interleaved modulation symbols as defined in [6] clause 3.2.3.1. In the case of Modernized GPS L2C, it contains either the NAV data modulation bits, the FEC encoded NAV data modulation symbols, or the FEC encoded CNAV data modulation symbols, dependent on the current signal configuration of this satellite as defined in [4, Table 3-III]. In the case of Modernized GPS L5, it contains the FEC encoded CNAV data modulation symbols as defined in [5]. + +In the case of SBAS, it contains the FEC encoded data modulation symbols as defined in [10]. + +In the case of QZSS QZS-L1, it contains the NAV data modulation bits as defined in [7] clause 5.2. In the case of QZSS QZS-L1C, it contains the encoded and interleaved modulation symbols as defined in [7] clause 5.3. In the case of QZSS QZS-L2C, it contains the encoded modulation symbols as defined in [7] clause 5.5. In the case of QZSS QZS-L5, it contains the encoded modulation symbols as defined in [7] clause 5.6. + +In the case of GLONASS, it contains the 100 sps differentially Manchester encoded modulation symbols as defined in [9] clause 3.3.2.2. + +In the case of Galileo, it contains the FEC encoded and interleaved modulation symbols. The logical levels 1 and 0 correspond to signal levels -1 and +1, respectively. + +In the case of BDS B1I, it contains the encoded and interleaved modulation symbols as defined in [23], clause 5.1.3. + +In the case of BDS B1C, it contains the encoded and interleaved modulation symbols as defined in [39], clause 6.2.2. + +In the case of BDS B2a, it contains the encoded and interleaved modulation symbols as defined in [49], clause 6.2.2. + +In the case of BDS B3I, it contains the encoded and interleaved modulation symbols as defined in [50], clause 5.1.3. + +In the case of NavIC, it contains the FEC encoded and interleaved Navigation symbols as defined in [38]. + +**GNSS-AcquisitionAssistance** + +The IE *GNSS-AcquisitionAssistance* is used by the location server to provide parameters that enable fast acquisition of the GNSS signals. Essentially, these parameters describe the range and derivatives from respective satellites to the reference location at the reference time *GNSS-SystemTime* provided in IE *GNSS-ReferenceTime*. + +Whenever *GNSS-AcquisitionAssistance* is provided by the location server, the IE *GNSS-ReferenceTime* is provided as well. E.g., even if the target device request for assistance data includes only a request for *GNSS-AcquisitionAssistance*, the location server also provides the corresponding IE *GNSS-ReferenceTime*. + +Figure 6.5.2.2-1 illustrates the relation between some of the fields, using GPS TOW as exemplary reference. + +``` +-- ASN1START + +GNSS-AcquisitionAssistance ::= SEQUENCE { + gnss-SignalID GNSS-SignalID, + gnss-AcquisitionAssistList GNSS-AcquisitionAssistList, + ... + confidence-r10 INTEGER (0..100) OPTIONAL -- Need ON +} + +GNSS-AcquisitionAssistList ::= SEQUENCE (SIZE(1..64)) OF GNSS-AcquisitionAssistElement + +GNSS-AcquisitionAssistElement ::= SEQUENCE { + svID SV-ID, + doppler0 INTEGER (-2048..2047), + doppler1 INTEGER (0..63), + dopplerUncertainty INTEGER (0..4), + codePhase INTEGER (0..1022), + intCodePhase INTEGER (0..127), + codePhaseSearchWindow INTEGER (0..31), + azimuth INTEGER (0..511), + elevation INTEGER (0..127), + ... + codePhase1023 BOOLEAN OPTIONAL, -- Need OP + dopplerUncertaintyExt-r10 ENUMERATED { d60, + d80, + d100, + d120, + noInformation, ... } OPTIONAL -- Need ON +} +``` + +} + +-- ASN1STOP + +| GNSS-AcquisitionAssistance field descriptions | | +|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-SignalID | This field specifies the GNSS signal for which the acquisition assistance are provided. | +| gnss-AcquisitionAssistList | These fields provide a list of acquisition assistance data for each GNSS satellite. | +| confidence | This field specifies the confidence level of the reference location area or volume used to calculate the acquisition assistance parameters (search windows). A high percentage value (e.g., 98% or more) indicates to the target device that the provided search windows are reliable. The location server should include this field to indicate the confidence level of the provided information. | +| svID | This field specifies the GNSS SV-ID of the satellite for which the GNSS-AcquisitionAssistance is given. | +| doppler0 | This field specifies the Doppler (0 th order term) value. A positive value in Doppler defines the increase in satellite signal frequency due to velocity towards the target device. A negative value in Doppler defines the decrease in satellite signal frequency due to velocity away from the target device. Doppler is given in unit of m/s by multiplying the Doppler value in Hz by the nominal wavelength of the assisted signal.
Scale factor 0.5 m/s in the range from -1024 m/s to +1023.5 m/s. | +| doppler1 | This field specifies the Doppler (1 st order term) value. A positive value defines the rate of increase in satellite signal frequency due to acceleration towards the target device. A negative value defines the rate of decrease in satellite signal frequency due to acceleration away from the target device.
Scale factor 1/210 m/s 2 in the range from -0.2 m/s 2 to +0.1 m/s 2 .
Actual value of Doppler (1 st order term) is calculated as $(-42 + \text{doppler1}) \times 1/210 \text{ m/s}^2$ , with doppler1 in the range of 0...63. | +| dopplerUncertainty | This field specifies the Doppler uncertainty value. It is defined such that the Doppler experienced by a stationary target device is in the range [Doppler-Doppler Uncertainty] to [Doppler+Doppler Uncertainty]. Doppler Uncertainty is given in unit of m/s by multiplying the Doppler Uncertainty value in Hz by the nominal wavelength of the assisted signal.
Defined values: 2.5 m/s, 5 m/s, 10 m/s, 20 m/s, 40 m/s as encoded by an integer n in the range 0-4 according to:
$2^{-n}(40) \text{ m/s}; n = 0 - 4.$
If the dopplerUncertaintyExt field is present, the target device that supports the dopplerUncertaintyExt shall ignore this field. | +| codePhase | This field together with the codePhase1023 field specifies the code phase, in units of milli-seconds, in the range from 0 to 1 millisecond scaled by the nominal chipping rate of the GNSS signal, where increasing values of the field signify increasing predicted signal code phases, as seen by a receiver at the reference location at the reference time. The reference location would typically be an a priori estimate of the target device location.
Scale factor $2^{-10}$ ms in the range from 0 to $(1-2^{-10})$ ms.
Note: The value $(1-2^{-10})$ ms is encoded using the codePhase1023 IE. | +| intCodePhase | This field contains integer code phase (expressed modulo 128 ms). The satellite integer milli-seconds code phase currently being transmitted at the reference time, as seen by a receiver at the reference location is calculated as reference time (expressed in milli-seconds) minus $(\text{intCodePhase} + (n \times 128 \text{ ms}))$ , as shown in Figure 6.5.2.2-1, with $n = \dots, -2, -1, 0, 1, 2, \dots$
Scale factor 1 ms in the range from 0 to 127 ms. | +| codePhaseSearchWindow | This field contains the code phase search window. The code phase search window accounts for the uncertainty in the estimated target device location but not any uncertainty in reference time. It is defined such that the expected code phase is in the range [Code Phase-Code Phase Search Window] to [Code Phase+Code Phase Search Window] given in units of milli-seconds.
Range 0-31, mapping according to the table codePhaseSearchWindow Value to Code Phase Search Window [ms] relation shown below. | +| azimuth | This field specifies the azimuth angle. An angle of x degrees means the satellite azimuth a is in the range $(x \leq a < x+0.703125)$ degrees.
Scale factor 0.703125 degrees. | +| elevation | This field specifies the elevation angle. An angle of y degrees means the satellite elevation e is in the range $(y \leq e < y+0.703125)$ degrees.
Scale factor 0.703125 degrees. | + +| GNSS-AcquisitionAssistance field descriptions | | +|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| codePhase1023 | This field if set to TRUE indicates that the code phase has the value $1023 \times 2^{-10} = (1-2^{-10})$ ms. This field may only be set to TRUE if the value provided in the codePhase IE is 1022. If this field is set to FALSE, the code phase is the value provided in the codePhase IE in the range from 0 to $(1 - 2 \times 2^{-10})$ ms. If this field is not present and the codePhase IE has the value 1022, the target device may assume that the code phase is between $(1 - 2 \times 2^{-10})$ and $(1 - 2^{-10})$ ms. | +| dopplerUncertaintyExt | If this field is present, the target device that supports this field shall ignore the dopplerUncertainty field. The location server should include this field only if supported by the target device.
This field specifies the Doppler uncertainty value. It is defined such that the Doppler experienced by a stationary target device is in the range [Doppler-Doppler Uncertainty] to [Doppler+Doppler Uncertainty]. Doppler Uncertainty is given in unit of m/s by multiplying the Doppler Uncertainty value in Hz by the nominal wavelength of the assisted signal.
Enumerated values define 60 m/s, 80 m/s, 100 m/s, 120 m/s, and "No Information". | + +***codePhaseSearchWindow* Value to Code Phase Search Window [ms] relation** + +| codePhaseSearchWindow Value | Code Phase Search Window [ms] | +|-------------------------------------------|--------------------------------------| +| '00000' | No information | +| '00001' | 0,002 | +| '00010' | 0,004 | +| '00011' | 0,008 | +| '00100' | 0,012 | +| '00101' | 0,016 | +| '00110' | 0,024 | +| '00111' | 0,032 | +| '01000' | 0,048 | +| '01001' | 0,064 | +| '01010' | 0,096 | +| '01011' | 0,128 | +| '01100' | 0,164 | +| '01101' | 0,200 | +| '01110' | 0,250 | +| '01111' | 0,300 | +| '10000' | 0,360 | +| '10001' | 0,420 | +| '10010' | 0,480 | +| '10011' | 0,540 | +| '10100' | 0,600 | +| '10101' | 0,660 | +| '10110' | 0,720 | +| '10111' | 0,780 | +| '11000' | 0,850 | +| '11001' | 1,000 | +| '11010' | 1,150 | +| '11011' | 1,300 | +| '11100' | 1,450 | +| '11101' | 1,600 | +| '11110' | 1,800 | +| '11111' | 2,000 | + +![Diagram illustrating the calculation of GNSS Acquisition Assistance fields. It shows five horizontal rows of hexagons. The top two rows are orange, the third is yellow, and the bottom two are green. A vertical line passes through the center of all rows. Above the top row, two horizontal arrows point towards the center line. The hexagons are arranged such that they appear to be shifting or being calculated relative to the central vertical axis.](b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg) + +Diagram illustrating the calculation of GNSS Acquisition Assistance fields. It shows five horizontal rows of hexagons. The top two rows are orange, the third is yellow, and the bottom two are green. A vertical line passes through the center of all rows. Above the top row, two horizontal arrows point towards the center line. The hexagons are arranged such that they appear to be shifting or being calculated relative to the central vertical axis. + +Figure 6.5.2.2-1: Exemplary calculation of some GNSS Acquisition Assistance fields. + +### – *GNSS-Almanac* + +The IE *GNSS-Almanac* is used by the location server to provide the coarse, long-term model of the satellite positions and clocks. The meaning of these parameters is defined in relevant ICDs of the particular GNSS and GNSS specific interpretations apply. For example, GPS and QZSS use the same model parameters but some parameters have a different interpretation [7]. *GNSS-Almanac* is useful for receiver tasks that require coarse accuracy, such as determining satellite visibility. The model is valid for up to a few weeks, typically. Since it is a long-term model, the field should be provided for all satellites available in the GNSS constellation (i.e., not only for SVs visible at the reference location and including SVs flagged as unhealthy in almanac). The *completeAlmanacProvided* field indicates whether or not the location server provided almanacs for the complete GNSS constellation. + +``` +-- ASN1START +GNSS-Almanac ::= SEQUENCE { + weekNumber INTEGER (0..255) OPTIONAL, -- Need ON + toa INTEGER (0..255) OPTIONAL, -- Need ON + ioda INTEGER (0..3) OPTIONAL, -- Need ON + completeAlmanacProvided BOOLEAN, + gnssAlmanacList GNSS-AlmanacList, + .... + [[ toa-ext-v1240 INTEGER (256..1023) OPTIONAL, -- Need ON + ioda-ext-v1240 INTEGER (4..15) OPTIONAL -- Need ON + ]], + [[ + weekNumber-ext-r16 INTEGER (256..8191) OPTIONAL, -- Need ON + toa-ext2-r16 INTEGER (256..65535) OPTIONAL -- Need ON + ]] +} +``` + +``` + +GNSS-AlmanacList ::= SEQUENCE (SIZE(1..64)) OF GNSS-AlmanacElement + +GNSS-AlmanacElement ::= CHOICE { + keplerianAlmanacSet AlmanacKeplerianSet, -- Model-1 + keplerianNAV-Almanac AlmanacNAV-KeplerianSet, -- Model-2 + keplerianReducedAlmanac AlmanacReducedKeplerianSet, -- Model-3 + keplerianMidiAlmanac AlmanacMidiAlmanacSet, -- Model-4 + keplerianGLONASS AlmanacGLONASS-AlmanacSet, -- Model-5 + ecef-SBAS-Almanac AlmanacECEF-SBAS-AlmanacSet, -- Model-6 + ... + keplerianBDS-Almanac-r12 AlmanacBDS-AlmanacSet-r12, -- Model-7 + keplerianNavIC-Almanac-r16 AlmanacNavIC-AlmanacSet-r16 -- Model-8 +} + +-- ASN1STOP + +``` + +#### GNSS-Almanac field descriptions + +##### **weekNumber, weekNumber-ext** + +This field specifies the almanac reference week number in GNSS specific system time to which the almanac reference time *toa* is referenced, modulo 256 weeks. Either *weekNumber* or *weekNumber-ext* is required for non-GLONASS GNSSs. + +In the case of Galileo, the almanac reference week number *WNa* natively contains only the 2 LSB's [8], clause 5.1.10]. + +In the case of BDS B1C and BDS B2a, the almanac reference week number is defined in [39], 7.9.1 and [49], 7.9.1. + +In the case of NavIC, the almanac reference week number is defined in [38]. + +##### **toa, toa-ext, toa-ext2** + +In the cases that *GNSS-ID* does not indicate Galileo or NavIC, this field specifies the almanac reference time given in GNSS specific system time, in units of seconds with a scale factor of $2^{12}$ . *toa* is required for non-GLONASS GNSSs when the *toa-ext2* is not present. + +In the case that *GNSS-ID* indicates Galileo, this field specifies the almanac reference time given in GNSS specific system time, in units of seconds with a scale factor of 600 seconds. Either *toa* or *toa-ext* is required for Galileo GNSS. + +In the case that *GNSS-ID* indicates NavIC, this field specifies the almanac reference time given in GNSS specific system time, in units of seconds with a scale factor of 16 seconds [38]. Either *toa* or *toa-ext2* is required for NavIC GNSS. + +##### **iota, iota-ext** + +This field specifies the issue of data. Either *iota* or *iota-ext* is required for Galileo GNSS. + +##### **completeAlmanacProvided** + +If set to TRUE, the *gnss-AlmanacList* contains almanacs for the complete GNSS constellation indicated by *GNSS-ID*. + +##### **gnss-AlmanacList** + +This list contains the almanac model for each GNSS satellite in the GNSS constellation. + +#### AlmanacKeplerianSet + +``` + +-- ASN1START + +AlmanacKeplerianSet ::= SEQUENCE { + svID SV-ID, + kepAlmanacE INTEGER (0..2047), + kepAlmanacDeltaI INTEGER (-1024..1023), + kepAlmanacOmegaDot INTEGER (-1024..1023), + kepSV-StatusINAV BIT STRING (SIZE (4)), + kepSV-StatusFNAV BIT STRING (SIZE (2)) OPTIONAL, -- Need ON + kepAlmanacAPowerHalf INTEGER (-4096..4095), + kepAlmanacOmega0 INTEGER (-32768..32767), + kepAlmanacW INTEGER (-32768..32767), + kepAlmanacM0 INTEGER (-32768..32767), + kepAlmanacAF0 INTEGER (-32768..32767), + kepAlmanacAF1 INTEGER (-4096..4095), + ... +} + +-- ASN1STOP + +``` + +#### AlmanacKeplerianSet field descriptions + +##### **svID** + +This field identifies the satellite for which the GNSS Almanac Model is given. + +##### **kepAlmanacE** + +Parameter *e*, eccentricity, dimensionless [8]. + +Scale factor $2^{-16}$ . + +| AlmanacKeplerianSet field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| kepAlmanacDeltaI
Parameter $\delta i$ , inclination at reference time relative to $i_0=56^\circ$ ; semi-circles [8].
Scale factor $2^{-14}$ semi-circles. | +| kepAlmanacOmegaDot
Parameter $\dot{\Omega}$ , rate of change of right ascension (semi-circles/sec) [8].
Scale factor $2^{-33}$ semi-circles/seconds. | +| kepSV-StatusINAV
This field contains the I/NAV signal health status [8], clause 5.1.10 , E5b HS and E1-B HS , where E5b HS occupies the 2 MSBs in kepSV-StatusINAV , and E1-B HS the two LSBs. | +| kepSV-StatusFNAV
This field contains the F/NAV signal health status [8], clause 5.1.10 , E5a HS . If the target device is supporting multiple Galileo signals, the location server includes this field. | +| kepAlmanacAPowerHalf
Parameter $\Delta(a^{1/2})$ , difference with respect to the square root of the nominal semi-major axis, (metres) 1/2 [8].
Scale factor $2^{-9}$ metres 1/2 . | +| kepAlmanacOmega0
Parameter $\Omega_{00}$ , longitude of ascending node of orbital plane at weekly epoch (semi-circles) [8].
Scale factor $2^{-15}$ semi-circles. | +| kepAlmanacW
Parameter $\omega$ , argument of perigee (semi-circles) [8].
Scale factor $2^{-15}$ semi-circles. | +| kepAlmanacM0
Parameter $M_0$ , mean anomaly at reference time (semi-circles) [8].
Scale factor $2^{-15}$ semi-circles. | +| kepAlmanacAF0
Parameter $af_0$ , satellite clock correction bias, seconds [8].
Scale factor $2^{-19}$ seconds. | +| kepAlmanacAF1
Parameter $af_1$ , satellite clock correction linear, sec/sec [8].
Scale factor $2^{-38}$ seconds/second. | + +## AlmanacNAV-KeplerianSet + +``` +-- ASN1START +AlmanacNAV-KeplerianSet ::= SEQUENCE { + svID SV-ID, + navAlmE INTEGER (0..65535), + navAlmDeltaI INTEGER (-32768..32767), + navAlmOMEGADOT INTEGER (-32768..32767), + navAlmSVHealth INTEGER (0..255), + navAlmSqrtA INTEGER (0..16777215), + navAlmOMEGAO INTEGER (-8388608..8388607), + navAlmOmega INTEGER (-8388608..8388607), + navAlmMo INTEGER (-8388608..8388607), + navAlmaf0 INTEGER (-1024..1023), + navAlmaf1 INTEGER (-1024..1023), + ... +} + +-- ASN1STOP +``` + +| AlmanacNAV-KeplerianSet field descriptions | | +|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| svID | This field identifies the satellite for which the GNSS Almanac Model is given. | +| navAlmE | Parameter $e$ , eccentricity, dimensionless [4,7].
Scale factor $2^{-21}$ . | +| navAlmDeltaI | Parameter $\delta i$ , correction to inclination, semi-circles [4,7].
Scale factor $2^{-19}$ semi-circles. | +| navAlmOMEGADOT | Parameter $\dot{\Omega}$ , rate of right ascension, semi-circles/sec [4,7].
Scale factor $2^{-38}$ semi-circles/second. | +| navAlmSVHealth | Parameter SV Health, satellite health [4,7]. | +| navAlmSqrtA | Parameter $\sqrt{a}$ , square root of the semi-major axis, metres 1/2 [4,7].
Scale factor $2^{-11}$ metres 1/2 . | +| navAlmOMEGAo | Parameter $\Omega_0$ , longitude of ascending node of orbit plane at weekly epoch, semi-circles [4,7].
Scale factor $2^{-23}$ semi-circles. | +| navAlmOmega | Parameter $\omega$ , argument of perigee semi-circles [4,7].
Scale factor $2^{-23}$ semi-circles. | +| navAlmMo | Parameter $M_0$ , mean anomaly at reference time semi-circles [4,7].
Scale factor $2^{-23}$ semi-circles. | +| navAlmaf0 | Parameter $a_{f0}$ , apparent satellite clock correction seconds [4,7].
Scale factor $2^{-20}$ seconds. | +| navAlmaf1 | Parameter $a_{f1}$ , apparent satellite clock correction sec/sec [4,7].
Scale factor $2^{-38}$ semi-circles seconds/second. | + +### AlmanacReducedKeplerianSet + +``` +-- ASN1START +AlmanacReducedKeplerianSet ::= SEQUENCE { + svID SV-ID, + redAlmDeltaA INTEGER (-128..127), + redAlmOmega0 INTEGER (-64..63), + redAlmPhi0 INTEGER (-64..63), + redAlmL1Health BOOLEAN, + redAlmL2Health BOOLEAN, + redAlmL5Health BOOLEAN, + ... +} + +-- ASN1STOP +``` + +| AlmanacReducedKeplerianSet field descriptions | | +|------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| svID | This field identifies the satellite for which the GNSS Almanac Model is given. | +| redAlmDeltaA | Parameter $\delta_A$ , metres [4], [5], [6], [7], [39], [49].
Scale factor $2^{19}$ metres. | +| redAlmOmega0 | Parameter $\Omega_0$ , semi-circles [4], [5], [6], [7], [39], [49].
Scale factor $2^{-6}$ semi-circles. | +| redAlmPhi0 | Parameter $\Phi_0$ , semi-circles [4], [5], [6], [7], [39], [49].
Scale factor $2^{-6}$ semi-circles. | +| redAlmL1Health | Parameter L1 Health, dimensionless [4], [5], [6], [7].
If GNSS-ID = BDS, this field indicates the Satellite clock health state (the 8th bit) defined in table 7-14 [39] for BDS B1C and in table 7-14 [49] for BDS B2a. | +| redAlmL2Health | Parameter L2 Health, dimensionless [4], [5], [6], [7].
If GNSS-ID = BDS, this field indicates the B1C signal health state (the 7th bit) defined in table 7-14 [39] for BDS B1C and in table 7-14 [49] for BDS B2a. | +| redAlmL5Health | Parameter L5 Health, dimensionless [4], [5], [6], [7].
If GNSS-ID = BDS, this field indicates the B2a signal health state (the 6th bit) defined in table 7-14 [39] for BDS B1C and in table 7-14 [49] for BDS B2a. | + +### AlmanacMidiAlmanacSet + +``` +-- ASN1START +``` + +``` +AlmanacMidiAlmanacSet ::= SEQUENCE { + svID SV-ID, + midiAlmE INTEGER (0..2047), + midiAlmDeltaI INTEGER (-1024..1023), + midiAlmOmegaDot INTEGER (-1024..1023), + midiAlmSqrtA INTEGER (0..131071), + midiAlmOmega0 INTEGER (-32768..32767), + midiAlmOmega INTEGER (-32768..32767), + midiAlmMo INTEGER (-32768..32767), + midiAlmaf0 INTEGER (-1024..1023), + midiAlmaf1 INTEGER (-512..511), + midiAlmL1Health BOOLEAN, + midiAlmL2Health BOOLEAN, + midiAlmL5Health BOOLEAN, + ... +} +``` + +``` +-- ASN1STOP +``` + +| AlmanacMidiAlmanacSet field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| svID
This field identifies the satellite for which the GNSS Almanac Model is given. | +| midiAlmE
Parameter e, dimensionless [4], [5], [6], [7], [39], [49].
Scale factor $2^{-16}$ . | +| midiAlmDeltaI
Parameter $\delta_i$ , semi-circles [4], [5], [6], [7], [39], [49].
Scale factor $2^{-14}$ semi-circles. | +| midiAlmOmegaDot
Parameter $\dot{\Omega}$ , semi-circles/sec [4], [5], [6], [7], [39], [49].
Scale factor $2^{-33}$ semi-circles/second. | +| midiAlmSqrtA
Parameter $\sqrt{A}$ , metres $^{1/2}$ [4], [5], [6], [7], [39], [49].
Scale factor $2^{-4}$ metres $^{1/2}$ . | +| midiAlmOmega0
Parameter $\Omega_0$ , semi-circles [4], [5], [6], [7], [39], [49].
Scale factor $2^{-15}$ semi-circles. | +| midiAlmOmega
Parameter $\omega$ , semi-circles [4], [5], [6], [7], [39], [49].
Scale factor $2^{-15}$ semi-circles. | +| midiAlmMo
Parameter $M_0$ , semi-circles [4], [5], [6], [7], [39], [49].
Scale factor $2^{-15}$ semi-circles. | +| midiAlmaf0
Parameter $a_{f0}$ , seconds [4], [5], [6], [7], [39], [49].
Scale factor $2^{-20}$ seconds. | +| midiAlmaf1
Parameter $a_{f1}$ , sec/sec [4], [5], [6], [7], [39], [49].
Scale factor $2^{-37}$ seconds/second. | +| midiAlmL1Health
Parameter L1 Health, dimensionless [4], [5], [6], [7].
If GNSS-ID = BDS, this field indicates the satellite clock health state (the 8th bit) defined in table 7-14 [39] for BDS B1C and in table 7-14 [49] for BDS B2a. | +| midiAlmL2Health
Parameter L2 Health, dimensionless [4], [5], [6], [7].
If GNSS-ID = BDS, this field indicates the B1C signal health state (the 7th bit) defined in table 7-14 [39] for BDS B1C and in table 7-14 [49] for BDS B2a. | +| midiAlmL5Health
Parameter L5 Health, dimensionless [4], [5], [6], [7].
If GNSS-ID = BDS, this field indicates the B2a signal health state (the 6th bit) defined in table 7-14 [39] for BDS B1C and in table 7-14 [49] for BDS B2a. | + +## AlmanacGLONASS-AlmanacSet + +``` +-- ASN1START + +AlmanacGLONASS-AlmanacSet ::= SEQUENCE { + gloAlm-NA INTEGER (1..1461), + gloAlmnA INTEGER (1..24), + gloAlmHA INTEGER (0..31), + gloAlmLambdaA INTEGER (-1048576..1048575), + gloAlmtLambdaA INTEGER (0..2097151), + gloAlmDeltaIa INTEGER (-131072..131071), + gloAlmDeltaTA INTEGER (-2097152..2097151), + gloAlmDeltaTdotA INTEGER (-64..63), + gloAlmEpsilonA INTEGER (0..32767), + gloAlmOmegaA INTEGER (-32768..32767), + gloAlmTauA INTEGER (-512..511), + gloAlmCA INTEGER (0..1), + gloAlmMA BIT STRING (SIZE(2)) OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP +``` + +| AlmanacGLONASS-AlmanacSet field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gloAlm-NA
Parameter $N^A$ , days [9].
Scale factor 1 days. | +| gloAlmnA
Parameter $n^A$ , dimensionless [9]. | +| gloAlmHA
Parameter $H_n^A$ , dimensionless [9]. | +| gloAlmLambdaA
Parameter $\lambda_n^A$ , semi-circles [9].
Scale factor $2^{-20}$ semi-circles. | +| gloAlmlambdaA
Parameter $t_{i,n}^A$ , seconds [9].
Scale factor $2^{-5}$ seconds. | +| gloAlmDeltaIa
Parameter $\Delta i_n^A$ , semi-circles [9].
Scale factor $2^{-20}$ semi-circles. | +| gloAlmDeltaTA
Parameter $\Delta T_n^A$ , sec/orbit period [9].
Scale factor $2^{-9}$ seconds/orbit period. | +| gloAlmDeltaTdotA
Parameter $\Delta T\_DOT_n^A$ , sec/orbit period 2 [9].
Scale factor $2^{-74}$ seconds/orbit period 2 . | +| gloAlmEpsilonA
Parameter $\epsilon_n^A$ , dimensionless [9].
Scale factor $2^{-20}$ . | +| gloAlmOmegaA
Parameter $\omega_n^A$ , semi-circles [9].
Scale factor $2^{-15}$ semi-circles. | +| gloAlmTauA
Parameter $\tau_n^A$ , seconds [9].
Scale factor $2^{-18}$ seconds. | +| gloAlmCA
Parameter $C_n^A$ , dimensionless [9]. | +| gloAlmMA
Parameter $M_n^A$ , dimensionless [9]. This parameter is present if its value is nonzero; otherwise it is not present. | + +## — AlmanacECEF-SBAS-AlmanacSet + +``` +-- ASN1START +AlmanacECEF-SBAS-AlmanacSet ::= SEQUENCE { + sbasAlmDataID INTEGER (0..3), + svID SV-ID, + sbasAlmHealth BIT STRING (SIZE(8)), + sbasAlmXg INTEGER (-16384..16383), + sbasAlmYg INTEGER (-16384..16383), + sbasAlmZg INTEGER (-256..255), + sbasAlmXgdot INTEGER (-4..3), + sbasAlmYgDot INTEGER (-4..3), + sbasAlmZgDot INTEGER (-8..7), + sbasAlmTo INTEGER (0..2047), + ... +} + +-- ASN1STOP +``` + +| AlmanacECEF-SBAS-AlmanacSet field descriptions | +|-----------------------------------------------------------------------------------------------------------------| +| sbasAlmDataID
Parameter Data ID, dimensionless [10]. | +| svID
This field identifies the satellite for which the GNSS Almanac Model is given. | +| sbasAlmHealth
Parameter Health, dimensionless [10]. | +| sbasAlmXg
Parameter $X_G$ , metres [10].
Scale factor 2600 metres. | +| sbasAlmYg
Parameter $Y_G$ , metres [10].
Scale factor 2600 metres. | +| sbasAlmZg
Parameter $Z_G$ , metres [10].
Scale factor 26000 metres. | +| sbasAlmXgdot
Parameter $X_G$ Rat-of-Change, metres/second [10].
Scale factor 10 metres/second. | +| sbasAlmYgDot
Parameter $Y_G$ Rate-of-Change, metres/second [10].
Scale factor 10 metres/second. | +| sbasAlmZgDot
Parameter $Z_G$ Rate-of-Change, metres/second [10].
Scale factor 40.96 metres/second. | +| sbasAlmTo
Parameter $t_0$ , seconds [10].
Scale factor 64 metres/second. | + +## — *AlmanacBDS-AlmanacSet* + +``` +-- ASN1START +AlmanacBDS-AlmanacSet-r12 ::= SEQUENCE { + svID SV-ID, + bdsAlmToa-r12 INTEGER (0..255) OPTIONAL, -- Cond NotSameForAllSV + bdsAlmSqrtA-r12 INTEGER (0..16777215), + bdsAlmE-r12 INTEGER (0..131071), + bdsAlmW-r12 INTEGER (-8388608..8388607), + bdsAlmM0-r12 INTEGER (-8388608..8388607), + bdsAlmOmega0-r12 INTEGER (-8388608..8388607), + bdsAlmOmegaDot-r12 INTEGER (-65536..65535), + bdsAlmDeltaI-r12 INTEGER (-32768..32767), + bdsAlmA0-r12 INTEGER (-1024..1023), + bdsAlmA1-r12 INTEGER (-1024..1023), + bdsSvHealth-r12 BIT STRING (SIZE(9)) OPTIONAL, -- Cond SV-ID + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| NotSameForAllSV | This field may be present if the $t_{oa}$ is not the same for all SVs; otherwise it is not present and the $t_{oa}$ is provided in GNSS-Almanac . | +| SV-ID | This field is mandatory present if SV-ID is between 0 and 63; otherwise it is not present. | + +| AlmanacBDS-AlmanacSet field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| svID
This field identifies the satellite for which the GNSS Almanac Model is given. | +| bdsAlmToa
Parameter $t_{oa}$ , Almanac reference time (seconds) [23], [50].
Scale factor $2^{12}$ seconds. | +| bdsAlmSqrtA
Parameter $A^{1/2}$ , Square root of semi-major axis (metres $^{1/2}$ ) [23], [50].
Scale factor $2^{11}$ metres $^{1/2}$ . | +| bdsAlmE
Parameter $e$ , Eccentricity, dimensionless [23], [50].
Scale factor $2^{21}$ . | +| bdsAlmW
Parameter $\omega$ , Argument of Perigee (semi-circles) [23], [50].
Scale factor $2^{23}$ semi-circles. | +| bdsAlmM0
Parameter $M_0$ , Mean anomaly at reference time (semi-circles) [23], [50].
Scale factor $2^{23}$ semi-circles. | +| bdsAlmOmega0
Parameter $\Omega_0$ , Longitude of ascending node of orbital plane computed according to reference time (semi-circles) [23], [50].
Scale factor $2^{23}$ semi-circles. | +| bdsAlmOmegaDot
Parameter $\dot{\Omega}$ , Rate of right ascension (semi-circles/second) [23], [50].
Scale factor $2^{38}$ semi-circles/second. | +| bdsAlmDeltaI
Parameter $\delta_i$ , Correction of orbit reference inclination at reference time (semi-circles) [23], [50].
Scale factor $2^{19}$ semi-circles. | +| bdsAlmA0
Parameter $a_0$ , Satellite clock bias (seconds) [23], [50].
Scale factor $2^{20}$ seconds. | +| bdsAlmA1
Parameter $a_1$ , Satellite clock rate (sec/sec) [23], [50].
Scale factor $2^{38}$ seconds/seconds. | +| bdsSvHealth
This field indicates satellites health information as defined in [23], [50] Table 5-16. The left most bit is the MSB. | + +## AlmanacNavIC-AlmanacSet + +``` +-- ASN1START +AlmanacNavIC-AlmanacSet-r16 ::= SEQUENCE { + svID-r16 SV-ID, + navic-AlmToa-r16 INTEGER (0..65535) OPTIONAL, -- Cond NotSameForAllSV + navic-AlmE-r16 INTEGER (0..65535), + navic-AlmOMEGADOT-r16 INTEGER (-32768..32767), + navic-AlmSqrtA-r16 INTEGER (0..16777215), + navic-AlmOMEGAo-r16 INTEGER (-8388608..8388607), + navic-AlmOmega-r16 INTEGER (-8388608..8388607), + navic-AlmMo-r16 INTEGER (-8388608..8388607), + navic-Almaf0-r16 INTEGER (-1024..1023), + navic-Almaf1-r16 INTEGER (-1024..1023), + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NotSameForAllSV | This field is optionally present, need ON, if the $t_{oa}$ is not the same for all SVs; otherwise it is not present and the $t_{oa}$ is provided in GNSS-Almanac . | + +| AlmanacNavIC-AlmanacSet field descriptions | | +|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| svID | This field identifies the satellite for which the Almanac model is given | +| navic-AlmToa | This field provides the time of almanac set
Scale factor 16 seconds. | +| navic-AlmE | Parameter e, eccentricity, dimensionless
Scale factor $2^{-21}$ . | +| navic-AlmOMEGADOT | Parameter , rate of right ascension, semi-circles/sec
Scale factor $2^{-38}$ semi-circles/second | +| navic-AlmSqrtA | Parameter , square root of the semi-major axis, metres $^{1/2}$
Scale factor $2^{-11}$ metres $^{1/2}$ . | +| navic-AlmOMEGAo | Parameter $\Omega_0$ , longitude of ascending node of orbit plane at weekly epoch, semi-circles
Scale factor $2^{-23}$ semi-circles. | +| navic-AlmOmega | Parameter $\omega$ , argument of perigee semi-circles
Scale factor $2^{-23}$ semi-circles. | +| navic-AlmMo | Parameter $M_0$ , mean anomaly at reference time semi-circles
Scale factor $2^{-23}$ semi-circles. | +| navic-Almaf0 | Parameter $a_{f0}$ , apparent satellite clock correction seconds
Scale factor $2^{-20}$ seconds. | +| navic-Almaf1 | Parameter $a_{f1}$ , apparent satellite clock correction sec/sec
Scale factor $2^{-38}$ semi-circles seconds/second. | + +## GNSS-UTC-Model + +The IE *GNSS-UTC-Model* is used by the location server to provide several sets of parameters needed to relate GNSS system time to Universal Time Coordinate (UTC), as defined in [4], [5], [6], [7], [8], [9], [10], [23], [38], [39], [49]. + +The UTC time standard, UTC(k), is GNSS specific. E.g., if *GNSS-ID* indicates GPS, *GNSS-UTC-Model* contains a set of parameters needed to relate GPS system time to UTC(USNO); if *GNSS-ID* indicates QZSS, *GNSS-UTC-Model* contains a set of parameters needed to relate QZST to UTC(NICT); if *GNSS-ID* indicates GLONASS, *GNSS-UTC-Model* contains a set of parameters needed to relate GLONASS system time to UTC(RU); if *GNSS-ID* indicates SBAS, *GNSS-UTC-Model* contains a set of parameters needed to relate SBAS network time for the SBAS indicated by *SBAS-ID* to the UTC standard defined by the UTC Standard ID; if *GNSS-ID* indicates BDS, *GNSS-UTC-Model* contains a set of parameters needed to relate BDS system time to UTC (NTSC), where *UTC-ModelSet2* is used for BDS B1C and BDS B2a, and *UTC-ModelSet5* is used for BDS B1I; if the *GNSS-ID* indicates NavIC, the *GNSS-UTC-Model* contains a set of parameters needed to relate NavIC system time to the UTC (BIPM). + +``` +-- ASN1START +GNSS-UTC-Model ::= CHOICE { + utcModel1 UTC-ModelSet1, -- Model-1 + utcModel2 UTC-ModelSet2, -- Model-2 + utcModel3 UTC-ModelSet3, -- Model-3 + utcModel4 UTC-ModelSet4, -- Model-4 + ..., + utcModel5-r12 UTC-ModelSet5-r12 -- Model-5 +} + +-- ASN1STOP +``` + +## UTC-ModelSet1 + +``` +-- ASN1START +UTC-ModelSet1 ::= SEQUENCE { + gnss-Utc-A1 INTEGER (-8388608..8388607), + gnss-Utc-A0 INTEGER (-2147483648..2147483647), +} +``` + +``` + +gnss-Utc-Tot INTEGER (0..255), +gnss-Utc-WNt INTEGER (0..255), +gnss-Utc-DeltaTls INTEGER (-128..127), +gnss-Utc-WNlsf INTEGER (0..255), +gnss-Utc-DN INTEGER (-128..127), +gnss-Utc-DeltaTlsf INTEGER (-128..127), +... +} + +``` + +``` +-- ASN1STOP +``` + +#### UTC-ModelSet1 field descriptions + +| | | +|---------------------------|----------------------------------------------------------------------------------| +| gnss-Utc-A1 | Parameter A 1 , scale factor 2 -50 seconds/second [4,7,8]. | +| gnss-Utc-A0 | Parameter A 0 , scale factor 2 -30 seconds [4,7,8]. | +| gnss-Utc-Tot | Parameter t ot , scale factor 2 12 seconds [4,7,8]. | +| gnss-Utc-WNt | Parameter WN t , scale factor 1 week [4,7,8]. | +| gnss-Utc-DeltaTls | Parameter Δt ls , scale factor 1 second [4,7,8]. | +| gnss-Utc-WNlsf | Parameter WN lsf , scale factor 1 week [4,7,8]. | +| gnss-Utc-DN | Parameter DN, scale factor 1 day [4,7,8]. | +| gnss-Utc-DeltaTlsf | Parameter Δt lsf , scale factor 1 second [4,7,8]. | + +#### UTC-ModelSet2 + +``` +-- ASN1START +``` + +``` + +UTC-ModelSet2 ::= SEQUENCE { + utcA0 INTEGER (-32768..32767), + utcA1 INTEGER (-4096..4095), + utcA2 INTEGER (-64..63), + utcDeltaTls INTEGER (-128..127), + utcTot INTEGER (0..65535), + utcWNot INTEGER (0..8191), + utcWNlsf INTEGER (0..255), + utcDN BIT STRING (SIZE(4)), + utcDeltaTlsf INTEGER (-128..127), + ... + [[ + utcWNlsf-ext-r16 INTEGER (256..8191) OPTIONAL -- Need ON + ]] +} + +``` + +``` +-- ASN1STOP +``` + +#### UTC-ModelSet2 field descriptions + +| | | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| utcA0 | Parameter A 0-n , bias coefficient of GNSS time scale relative to UTC time scale (seconds) [4], [5], [6], [7], [38], [39], [49]. Scale factor 2 -35 seconds. | +| utcA1 | Parameter A 1-n , drift coefficient of GNSS time scale relative to UTC time scale (sec/sec) [4], [5], [6], [7], [38], [39], [49]. Scale factor 2 -51 seconds/second. | +| utcA2 | Parameter A 2-n , drift rate correction coefficient of GNSS time scale relative to UTC time scale (sec/sec 2 ) [4], [5], [6], [7], [38], [39], [49]. Scale factor 2 -68 seconds/second 2 . | +| utcDeltaTls | Parameter Δt ls , current or past leap second count (seconds) [4], [5], [6], [7], [38], [39], [49]. Scale factor 1 second. | +| utcTot | Parameter t ot , time data reference time of week (seconds) [4], [5], [6], [7], [38], [39], [49]. Scale factor 2 4 seconds. | + +| UTC-ModelSet2 field descriptions | | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| utcWNot | Parameter $WN_{ot}$ , time data reference week number (weeks) [4], [5], [6], [7], [38], [39], [49].
Scale factor 1 week. | +| utcWNIsf, utcWNIsf-ext | Parameter $WN_{LSF}$ , leap second reference week number (weeks) [4], [5], [6], [7], [38], [39], [49].
If the field utcWNIsf-ext is present, the field utcWNIsf shall be ignored by the receiver.
Scale factor 1 week. | +| utcDN | Parameter DN, leap second reference day number (days) [4], [5], [6], [7], [38], [39], [49].
Scale factor 1 day. | +| utcDeltaTIsf | Parameter $\Delta t_{LSF}$ , current or future leap second count (seconds) [4], [5], [6], [7], [38], [39], [49].
Scale factor 1 second. | + +### – UTC-ModelSet3 + +``` +-- ASN1START +UTC-ModelSet3 ::= SEQUENCE { + nA INTEGER (1..1461), + tauC INTEGER (-2147483648..2147483647), + b1 INTEGER (-1024..1023) OPTIONAL, -- Cond GLONASS-M + b2 INTEGER (-512..511) OPTIONAL, -- Cond GLONASS-M + kp BIT STRING (SIZE(2)) OPTIONAL, -- Cond GLONASS-M + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| GLONASS-M | The field is mandatory present if GLONASS-M satellites are present in the current GLONASS constellation; otherwise it is not present. | + +| UTC-ModelSet3 field descriptions | | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| nA | Parameter $N^A$ , calendar day number within four-year period beginning since the leap year (days) [9].
Scale factor 1 day. | +| tauC | Parameter $\tau_c$ , GLONASS time scale correction to UTC(SU) (seconds) [9].
Scale factor $2^{31}$ seconds. | +| b1 | Parameter B1, coefficient to determine $\Delta UT1$ (seconds) [9].
Scale factor $2^{-10}$ seconds. | +| b2 | Parameter B2, coefficient to determine $\Delta UT1$ (seconds/msd) [9].
Scale factor $2^{-16}$ seconds/msd. | +| kp | Parameter KP, notification of expected leap second correction (dimensionless) [9]. | + +### – UTC-ModelSet4 + +``` +-- ASN1START +UTC-ModelSet4 ::= SEQUENCE { + utcAlwnt INTEGER (-8388608..8388607), + utcA0wnt INTEGER (-2147483648..2147483647), + utcTot INTEGER (0..255), + utcWNT INTEGER (0..255), + utcDeltaTls INTEGER (-128..127), + utcWNIsf INTEGER (0..255), + utcDN INTEGER (-128..127), + utcDeltaTlsf INTEGER (-128..127), + utcStandardID INTEGER (0..7), + ... +} +``` + +``` +} +-- ASN1STOP +``` + +**UTC-ModelSet4 field descriptions** + +| | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| utcA1wnt | Parameter $A_{1WNT}$ , sec/sec ([10], Message Type 12).
Scale factor $2^{50}$ seconds/second. | +| utcA0wnt | Parameter $A_{0WNT}$ , seconds ([10], Message Type 12).
Scale factor $2^{30}$ seconds. | +| utcTot | Parameter $t_{ot}$ , seconds ([10], Message Type 12).
Scale factor $2^{12}$ seconds. | +| utcWNt | Parameter $WN_t$ , weeks ([10], Message Type 12).
Scale factor 1 week. | +| utcDeltaTls | Parameter $\Delta t_{LS}$ , seconds ([10], Message Type 12).
Scale factor 1 second. | +| utcWNlsf | Parameter $WN_{LSF}$ , weeks ([10], Message Type 12).
Scale factor 1 week. | +| utcDN | Parameter $DN$ , days ([10], Message Type 12).
Scale factor 1 day. | +| utcDeltaTlsf | Parameter $\Delta t_{LSF}$ , seconds ([10], Message Type 12).
Scale factor 1 second. | +| utcStandardID | If GNSS-ID indicates 'sbas', this field indicates the UTC standard used for the SBAS network time indicated by SBAS-ID to UTC relation as defined in the table Value of UTC Standard ID to UTC Standard relation shown below ([10], Message Type 12). | + +**Value of UTC Standard ID to UTC Standard relation** + +| Value of UTC Standard ID | UTC Standard | +|--------------------------|-------------------------------------------------------------------------------| +| 0 | UTC as operated by the Communications Research Laboratory (CRL), Tokyo, Japan | +| 1 | UTC as operated by the National Institute of Standards and Technology (NIST) | +| 2 | UTC as operated by the U. S. Naval Observatory (USNO) | +| 3 | UTC as operated by the International Bureau of Weights and Measures (BIPM) | +| 4-7 | Reserved for future definition | + +— **UTC-ModelSet5** + +``` +-- ASN1START +UTC-ModelSet5-r12 ::= SEQUENCE { + utcA0-r12 INTEGER (-2147483648..2147483647), + utcA1-r12 INTEGER (-8388608..8388607), + utcDeltaTls-r12 INTEGER (-128..127), + utcWNlsf-r12 INTEGER (0..255), + utcDN-r12 INTEGER (0..255), + utcDeltaTlsf-r12 INTEGER (-128..127), + ... +} +-- ASN1STOP +``` + +**UTC-ModelSet5 field descriptions** + +| | | +|--------------|--------------------------------------------------------------------------------------------------------| +| utcA0 | Parameter $A_{0UTC}$ , BDS clock bias relative to UTC, seconds [23].
Scale factor $2^{30}$ seconds. | +|--------------|--------------------------------------------------------------------------------------------------------| + +| UTC-ModelSet5 field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| utcA1
Parameter $A_{1\text{UTC}}$ , BDS clock rate relative to UTC, sec/sec [23].
Scale factor $2^{-50}$ sec/sec. | +| utcDeltaTIs
Parameter $\Delta t_{\text{LS}}$ , delta time due to leap seconds before the new leap second effective, seconds [23].
Scale factor 1 second. | +| utcWNIsf
Parameter $WN_{\text{LSF}}$ , week number of the new leap second, weeks [23].
Scale factor 1 week. | +| utcDN
Parameter DN, day number of week of the new leap second, days [23].
Scale factor 1 day. | +| utcDeltaTIsf
Parameter $\Delta t_{\text{LSF}}$ , delta time due to leap seconds after the new leap second effective, seconds [23].
Scale factor 1 second. | + +## GNSS-AuxiliaryInformation + +The IE *GNSS-AuxiliaryInformation* is used by the location server to provide additional information dependent on the *GNSS-ID*. If *GNSS-AuxiliaryInformation* is provided together with other satellite dependent GNSS assistance data (i.e., any of *GNSS-DifferentialCorrections*, *GNSS-NavigationModel*, *GNSS-DataBitAssistance*, or *GNSS-AcquisitionAssistance* IEs), the *GNSS-AuxiliaryInformation* should be provided for the same satellites and in the same LPP message as the other satellite dependent GNSS assistance data. + +``` +-- ASN1START + +GNSS-AuxiliaryInformation ::= CHOICE { + gnss-ID-GPS GNSS-ID-GPS, + gnss-ID-GLONASS GNSS-ID-GLONASS, + ... + [[ gnss-ID-BDS-r16 GNSS-ID-BDS-r16 + ]] +} + +GNSS-ID-GPS ::= SEQUENCE (SIZE(1..64)) OF GNSS-ID-GPS-SatElement + +GNSS-ID-GPS-SatElement ::= SEQUENCE { + svID SV-ID, + signalsAvailable GNSS-SignalIDs, + ... +} + +GNSS-ID-GLONASS ::= SEQUENCE (SIZE(1..64)) OF GNSS-ID-GLONASS-SatElement + +GNSS-ID-GLONASS-SatElement ::= SEQUENCE { + svID SV-ID, + signalsAvailable GNSS-SignalIDs, + channelNumber INTEGER (-7..13) OPTIONAL, -- Cond FDMA + ... +} + +GNSS-ID-BDS-r16 ::= SEQUENCE (SIZE(1..64)) OF GNSS-ID-BDS-SatElement-r16 + +GNSS-ID-BDS-SatElement-r16 ::= SEQUENCE { + svID-r16 SV-ID, + satType-r16 INTEGER (0..3), + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------| +| FDMA | The field is mandatory present if the GLONASS SV indicated by svID broadcasts FDMA signals; otherwise it is not present. | + +| GNSS-AuxiliaryInformation field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-ID-GPS
This choice may only be present if GNSS-ID indicates GPS. | +| gnss-ID-GLONASS
This choice may only be present if GNSS-ID indicates GLONASS. | +| gnss-ID-BDS
This choice may only be present if GNSS-ID indicates BDS. | +| svID
This field specifies the GNSS SV for which the GNSS-AuxiliaryInformation is given. | +| signalsAvailable
This field indicates the ranging signals supported by the satellite indicated by svID . This field is given as a bit string as defined in GNSS-SignalIDs for a particular GNSS. If a bit is set to '1' it indicates that the satellite identified by svID transmits ranging signals according to the signal correspondence in GNSS-SignalIDs . If a bit is set to '0' it indicates that the corresponding signal is not supported on the satellite identified by svID . | +| channelNumber
This field indicates the GLONASS carrier frequency number of the satellite identified by svID , as defined in [9]. | +| satType
This field identifies the BDS B1C and BDS B2a Satellite orbit type, defined in [39], [49].
1 indicates the GEO satellite, 2 indicates the IGSO satellite, 3 indicates the MEO satellite, and 0 is reserved. | + +## — **BDS-DifferentialCorrections** + +The IE *BDS-DifferentialCorrections* is used by the location server to provide differential corrections to the target device for BDS B1I and BDS B3I. + +``` +-- ASN1START + +BDS-DifferentialCorrections-r12 ::= SEQUENCE { + dbds-RefTime-r12 INTEGER (0..3599), + bds-SgnTypeList-r12 BDS-SgnTypeList-r12, + ... +} + +BDS-SgnTypeList-r12 ::= SEQUENCE (SIZE (1..3)) OF BDS-SgnTypeElement-r12 + +BDS-SgnTypeElement-r12 ::= SEQUENCE { + gnss-SignalID GNSS-SignalID OPTIONAL, -- Need ON + dbds-CorrectionList-r12 DBDS-CorrectionList-r12, + ... +} + +DBDS-CorrectionList-r12 ::= SEQUENCE (SIZE (1..64)) OF DBDS-CorrectionElement-r12 + +DBDS-CorrectionElement-r12 ::= SEQUENCE { + svID SV-ID, + bds-UDREI-r12 INTEGER (0..15), + bds-RURAI-r12 INTEGER (0..15), + bds-ECC-DeltaT-r12 INTEGER (-4096..4095), + ... +} + +-- ASN1STOP +``` + +| BDS-DifferentialCorrections field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dbds-RefTime
This field specifies the time for which the differential corrections are valid, modulo 1 hour. dbds-RefTime is given in BDS system time.
Scale factor 1-second. | +| bds-UDREI
This field indicates user differential range error information by user differential range error index (UDREI) as defined in [23], [50], clause 5.3.3.8.2. | +| bds-RURA
This field indicates Regional User Range Accuracy (RURA) information by Regional User Range Accuracy Index (UDREI) as defined in [23], [50], clause 5.3.3.7. | +| bds-ECC-DeltaT
This field indicates the BDS differential correction information which is expressed in equivalent clock correction ( $\Delta t$ ). Add the value of $\Delta t$ to the observed pseudo-range to correct the effect caused by the satellite clock offset and ephemeris error. Value -4096 means the $\Delta t$ is not available.
The scale factor is 0.1 metre. | + +## — ***BDS-GridModelParameter*** + +The IE *BDS-GridModelParameter* is used by the location server to provide Ionospheric Grid Information to the target device for BDS B1I and BDS B3I. + +``` +-- ASN1START + +BDS-GridModelParameter-r12 ::= SEQUENCE { + bds-RefTime-r12 INTEGER (0..3599), + gridIonList-r12 GridIonList-r12, + ... +} + +GridIonList-r12 ::= SEQUENCE (SIZE (1..320)) OF GridIonElement-r12 + +GridIonElement-r12 ::= SEQUENCE { + igp-ID-r12 INTEGER (1..320), + dt-r12 INTEGER (0..511), + givei-r12 INTEGER (0..15) , + ... +} + +-- ASN1STOP +``` + +| BDS-GridModelParamater field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bds-RefTime
This field specifies the time for which the grid model parameters are valid, modulo 1 hour. bds-RefTime is given in BDS system time.
Scale factor 1-second. | +| gridIonList
This list provides ionospheric grid point information for each grid point. Up to 16 instances are used in this version of the specification. The values 17 to 320 are reserved for future use. | +| igp-ID
This field indicates the ionospheric grid point (IGP) number as defined in [23], [50], clause 5.3.3.9. | +| dt
This field indicates $d_T$ as defined in [23], [50], clause 5.3.3.9.1, i.e. the vertical delay at the corresponding IGP indicated by igp-ID .
The scale factor is 0.125 metre. | +| givei
This field indicates the Grid Ionospheric Vertical Error Index (GIVEI) which is used to describe the delay correction accuracy at ionospheric grid point indicated by igp-ID , the mapping between GIVEI and GIVE is defined in [23], [50], clause 5.3.3.9.2. | + +## — ***GNSS-RTK-Observations*** + +The IE *GNSS-RTK-Observations* is used by the location server to provide GNSS reference station observables (pseudorange, phaserange, phaserange-rate (Doppler), and carrier-to-noise ratio) of the GNSS signals. Essentially, these + +parameters describe the range and derivatives from respective satellites to the reference station location provided in IE *GNSS-RTK-ReferenceStationInfo*. + +The parameters provided in IE *GNSS-RTK-Observations* are used as specified for message type 1071-1127 in [30]. + +``` +-- ASN1START + +GNSS-RTK-Observations-r15 ::= SEQUENCE { + epochTime-r15 GNSS-SystemTime, + gnss-ObservationList-r15 GNSS-ObservationList-r15, + ... +} + +GNSS-ObservationList-r15 ::= SEQUENCE (SIZE(1..64)) OF GNSS-RTK-SatelliteDataElement-r15 + +GNSS-RTK-SatelliteDataElement-r15 ::= SEQUENCE{ + svID-r15 SV-ID, + integer-ms-r15 INTEGER (0..254) OPTIONAL, -- Need ON + rough-range-r15 INTEGER (0..1023), + rough-phase-range-rate-r15 INTEGER (-8192..8191) OPTIONAL, -- Need ON + gnss-rtk-SatelliteSignalDataList-r15 GNSS-RTK-SatelliteSignalDataList-r15, + ... +} + +GNSS-RTK-SatelliteSignalDataList-r15 ::= SEQUENCE (SIZE(1..24)) OF + GNSS-RTK-SatelliteSignalDataElement-r15 + +GNSS-RTK-SatelliteSignalDataElement-r15 ::= SEQUENCE { + gnss-SignalID-r15 GNSS-SignalID, + fine-PseudoRange-r15 INTEGER (-524288..524287), + fine-PhaseRange-r15 INTEGER (-8388608..8388607), + lockTimeIndicator-r15 INTEGER (0..1023), + halfCycleAmbiguityIndicator-r15 BIT STRING (SIZE (1)), + carrier-to-noise-ratio-r15 INTEGER (0..1023) OPTIONAL, -- Need ON + fine-PhaseRangeRate-r15 INTEGER (-16384..16383) OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP +``` + +| GNSS-RTK-Observations field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

epochTime
This field specifies the epoch time of the observations. The gnss-TimeID in GNSS SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement.

| + +| GNSS-RTK-Observations field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| svID
This field specifies the GNSS SV-ID of the satellite for which the GNSS Observations are provided. | +| integer-ms
This field contains the integer number of milliseconds in the satellite rough range. Rough range can be used to restore complete observables for a given satellite.
Scale factor 1 milli-second in the range from 0 to 254 milli-seconds. | +| rough-range
This field contains the sub-milliseconds in the satellite rough range (modulo 1 millisecond).
Scale factor $2^{-10}$ milli-seconds in the range from 0 to $(1-2^{-10})$ milli-seconds. | +| rough-phase-range-rate
This field contains the GNSS satellite rough phaserange rate.
Scale factor 1 m/s. Range $\pm 8191$ m/s. | +| gnss-SignalID
This field specifies the GNSS signal for which the GNSS observations are provided. | +| fine-PseudoRange
This field contains the GNSS signal fine pseudorange.
Full pseudorange corresponding to the given signal is the sum of this field and the fields integer-ms and rough-range .
NOTE 1.
Scale factor $2^{-29}$ milli-seconds. Range $\pm(2^{-10}-2^{-29})$ milli-seconds. | +| fine-PhaseRange
This field contains the GNSS signal fine phaserange.
Being added to fields integer-ms and rough-range allows getting the full phaserange observable corresponding to given signal. NOTE 2.
Scale factor $2^{-31}$ milli-seconds. Range $\pm(2^{-8}-2^{-31})$ milli-seconds. | +| lockTimeIndicator
This field provides a measure of the amount of time during which the receiver has maintained continuous lock on that satellite signal. If a cycle slip occurs during the previous measurement cycle, the lock time indicator shall be reset to zero.
The mapping of lock-time parameters as defined in [30] is according to the table lockTimeIndicator value to lock-time parameters relation shown below. | +| halfCycleAmbiguityIndicator
Value 0 indicates no half-cycle ambiguity. Value 1 indicates half-cycle ambiguity.
When providing phaserange with unresolved polarity encoding this bit shall be set to 1. A target device that is not capable of handling half-cycle ambiguities shall skip such phaserange observables. If polarity resolution forced phaserange to be corrected by half-a-cycle, then the lockTimeIndicator must be reset to zero, indicating that despite continuous tracking the final phaserange experienced non-continuity. | +| carrier-to-noise-ratio
This field provides the GNSS signal carrier-to-noise-ratio in dB-Hz.
Scale factor $2^{-4}$ dB-Hz in the range from 0.0625 to 63.9375 dB-Hz. | +| fine-PhaseRangeRate
This field contains the GNSS signal fine Phase Range Rate.
Full phaserange rate is the sum of this field and the rough-phase-range-rate field. NOTE 3.
Scale factor 0.0001 m/s. Range $\pm 1.6383$ m/s. | + +NOTE 1: Complete Pseudorange for each signal (i) of given satellite can be restored as follows: + +$$\text{Pseudorange}(i) = c/1000 \times (\text{integer-ms} + \text{rough\_range}/1024 + 2^{-29} \times \text{fine\_Pseudorange}(i)), \text{ metre.}$$ + +NOTE 2: Complete Phaserange for each signal (i) of given satellite can be restored as follows: + +$$\text{Phaserange}(i) = c/1000 \times (\text{integer-ms} + \text{rough\_range}/1024 + 2^{-31} \times \text{fine\_Phaserange}(i)), \text{ metre.}$$ + +NOTE 3: Complete PhaseRangeRate for each signal (i) of given satellite can be restored as follows: + +$$\text{PhaseRangeRate}(i) = \text{rough-phase-range-rate} + 0.0001 * \text{fine-PhaseRangeRate}(i), \text{ metre/second.}$$ + +NOTE 4: The speed of light *c* is 299,792,458 metres per second. + +**lockTimeIndicator value to lock-time parameters relation** + +| lockTimeIndicator value (i) | Supplementary coefficient (k) [30] | Minimum Lock Time (ms) [30] | Range of Indicated Lock Times (t) (ms) [30] | +|------------------------------------|-------------------------------------------|------------------------------------|----------------------------------------------------| +| 0 – 63 | 1 | $i$ | $0 \leq t < 64$ | +| 64 – 95 | 2 | $2 \times i - 64$ | $64 \leq t < 128$ | +| 96 – 127 | 4 | $4 \times i - 256$ | $128 \leq t < 256$ | +| 128 – 159 | 8 | $8 \times i - 768$ | $256 \leq t < 512$ | +| 160 – 191 | 16 | $16 \times i - 2048$ | $512 \leq t < 1024$ | +| 192 – 223 | 32 | $32 \times i - 5120$ | $1024 \leq t < 2048$ | +| 224 – 255 | 64 | $64 \times i - 12288$ | $2048 \leq t < 4096$ | +| 256 – 287 | 128 | $128 \times i - 28672$ | $4096 \leq t < 8192$ | +| 288 – 319 | 256 | $256 \times i - 65536$ | $8192 \leq t < 16384$ | +| 320 – 351 | 512 | $512 \times i - 147456$ | $16384 \leq t < 32768$ | +| 352 – 383 | 1024 | $1024 \times i - 327680$ | $32768 \leq t < 65536$ | +| 384 – 415 | 2048 | $2048 \times i - 720896$ | $65536 \leq t < 131072$ | +| 416 – 447 | 4096 | $4096 \times i - 1572864$ | $131072 \leq t < 262144$ | +| 448 – 479 | 8192 | $8192 \times i - 3407872$ | $262144 \leq t < 524288$ | +| 480 – 511 | 16384 | $16384 \times i - 7340032$ | $524288 \leq t < 1048576$ | +| 512 – 543 | 32768 | $32768 \times i - 15728640$ | $1048576 \leq t < 2097152$ | +| 544 – 575 | 65536 | $65536 \times i - 33554432$ | $2097152 \leq t < 4194304$ | +| 576 – 607 | 131072 | $131072 \times i - 71303168$ | $4194304 \leq t < 8388608$ | +| 608 – 639 | 262144 | $262144 \times i - 150994944$ | $8388608 \leq t < 16777216$ | +| 640 – 671 | 524288 | $524288 \times i - 318767104$ | $16777216 \leq t < 33554432$ | +| 672 – 703 | 1048576 | $1048576 \times i - 671088640$ | $33554432 \leq t < 67108864$ | +| 704 | 2097152 | $2097152 \times i - 1409286144$ | $67108864 \leq t$ | +| 705 – 1023 | | Reserved | | + +**GLO-RTK-BiasInformation** + +The IE *GLO-RTK-BiasInformation* is used by the location server to provide the so-called "GLONASS Code-Phase bias values" (CPB) for up to all FDMA GLONASS observations. + +If IE *GNSS-RTK-Observations* for *gnss-ID = glonass* are provided, but IE *GLO-RTK-BiasInformation* is not provided, the target device assumes that the CPB information has been applied to the GLONASS observation data a priori. + +The parameters provided in IE *GLO-RTK-BiasInformation* are used as specified for message type 1230 in [30]. + +``` +-- ASN1START + +GLO-RTK-BiasInformation-r15 ::= SEQUENCE{ + referenceStationID-r15 GNSS-ReferenceStationID-r15, + cpbIndicator-r15 BIT STRING (SIZE(1)), + l1-ca-cpBias-r15 INTEGER (-32768..32767) OPTIONAL, -- Need ON + l1-p-cpBias-r15 INTEGER (-32768..32767) OPTIONAL, -- Need ON + l2-ca-cpBias-r15 INTEGER (-32768..32767) OPTIONAL, -- Need ON + l2-p-cpBias-r15 INTEGER (-32768..32767) OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP +``` + +**GLO-RTK-BiasInformation field descriptions****referenceStationID** + +This field specifies the Station ID for which the *GLO-RTK-BiasInformation* is provided. + +**cpbIndicator** + +This field specifies the GLONASS Code-Phase Bias Indicator. The interpretation of the value is as follows: + +0 – The GLONASS Pseudorange and Phaserrange observations in IE *GNSS-RTK-Observations* are not aligned to the same measurement epoch. + +1 – The GLONASS Pseudorange and Phaserrange observations in IE *GNSS-RTK-Observations* are aligned to the same measurement epoch. + +| GLO-RTK-BiasInformation field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| l1-ca-cpBias
This field specifies the GLONASS L1 C/A Code-Phase Bias, which represents the offset between the L1 C/A Pseudorange and L1 Phaserrange measurement epochs in metres.
If cpbIndicator is set to 0, the measurement epoch of the GLONASS L1 Phaserrange measurements may be aligned using:
Aligned GLONASS L1 Phaserrange = Full GLONASS L1 Phaserrange + GLONASS L1 C/A Code-Phase Bias.
If cpbIndicator is set to 1, the measurement epoch of the GLONASS L1 Phaserrange measurements may be unaligned using:
Unaligned GLONASS L1 Phaserrange = Full GLONASS L1 Phaserrange – GLONASS L1 C/A Code-Phase Bias.
Scale factor 0.02 m. Range $\pm 655.34$ m. | +| l1-p-cpBias
This field specifies the GLONASS L1 P Code-Phase Bias, which represents the offset between the L1 P Pseudorange and L1 Phaserrange measurement epochs in metres.
If cpbIndicator is set to 0, the measurement epoch of the GLONASS L1 Phaserrange measurements may be aligned using:
Aligned GLONASS L1 Phaserrange = Full GLONASS L1 Phaserrange + GLONASS L1 P Code-Phase Bias.
If cpbIndicator is set to 1, the measurement epoch of the GLONASS L1 Phaserrange measurements may be unaligned using:
Unaligned GLONASS L1 Phaserrange = Full GLONASS L1 Phaserrange – GLONASS L1 P Code-Phase Bias.
Scale factor 0.02 m. Range $\pm 655.34$ m. | +| l2-ca-cpBias
This field specifies the GLONASS L2 C/A Code-Phase Bias, which represents the offset between the L2 C/A Pseudorange and L2 Phaserrange measurement epochs in metres.
If cpbIndicator is set to 0, the measurement epoch of the GLONASS L2 Phaserrange measurements may be aligned using:
Aligned GLONASS L2 Phaserrange = Full GLONASS L2 Phaserrange + GLONASS L2 C/A Code-Phase Bias.
If cpbIndicator is set to 1, the measurement epoch of the GLONASS L2 Phaserrange measurements may be unaligned using:
Unaligned GLONASS L2 Phaserrange = Full GLONASS L2 Phaserrange – GLONASS L2 C/A Code-Phase Bias.
Scale factor 0.02 m. Range $\pm 655.34$ m. | +| l2-p-cpBias
This field specifies the GLONASS L2 P Code-Phase Bias, which represents the offset between the L2 P Pseudorange and L2 Phaserrange measurement epochs in metres.
If cpbIndicator is set to 0, the measurement epoch of the GLONASS L2 Phaserrange measurements may be aligned using:
Aligned GLONASS L2 Phaserrange = Full GLONASS L2 Phaserrange + GLONASS L2 P Code-Phase Bias.
If cpbIndicator is set to 1, the measurement epoch of the GLONASS L2 Phaserrange measurements may be unaligned using:
Unaligned GLONASS L2 Phaserrange = Full GLONASS L2 Phaserrange – GLONASS L2 P Code-Phase Bias.
Scale factor 0.02 m. Range $\pm 655.34$ m. | + +## – GNSS-RTK-MAC-CorrectionDifferences + +The IE *GNSS-RTK-MAC-CorrectionDifferences* is used by the location server to provide dispersive (ionospheric) and non-dispersive (geometric) correction difference components for up to 32 pairs of Auxiliary and Master Reference Stations. The Master Reference Station coordinates are provided in IE *GNSS-RTK-ReferenceStationInfo* and the Auxiliary Station coordinates are provided in IE *GNSS-RTK-AuxiliaryStationData*. + +The parameters provided in IE *GNSS-RTK-MAC-CorrectionDifferences* are used as specified for message type 1017 and 1039 in [30] and apply to all GNSSs. + +``` +-- ASN1START + +GNSS-RTK-MAC-CorrectionDifferences-r15 ::= SEQUENCE { + networkID-r15 GNSS-NetworkID-r15, + subNetworkID-r15 GNSS-SubNetworkID-r15, OPTIONAL, -- Need ON + master-ReferenceStationID-r15 GNSS-ReferenceStationID-r15, + l1-r15 GNSS-FrequencyID-r15, OPTIONAL, -- Need OP + l2-r15 GNSS-FrequencyID-r15, OPTIONAL, -- Need OP + rtkCorrectionDifferencesList-r15 RTK-CorrectionDifferencesList-r15, + ... +} + +RTK-CorrectionDifferencesList-r15 ::= SEQUENCE (SIZE (1..32)) OF + RTK-CorrectionDifferencesElement-r15 + +RTK-CorrectionDifferencesElement-r15 ::= SEQUENCE { +``` + +``` + +epochTime-r15 GNSS-SystemTime, +auxiliary-referenceStationID-r15 GNSS-ReferenceStationID-r15, +geometric-ionospheric-corrections-differences-r15 + Geometric-Ionospheric-Corrections-Differences-r15, + ... +} + +Geometric-Ionospheric-Corrections-Differences-r15 ::= SEQUENCE (SIZE(1..64)) OF + Geometric-Ionospheric-Corrections-Differences-Element-r15 + +Geometric-Ionospheric-Corrections-Differences-Element-r15 ::= SEQUENCE { + svID-r15 SV-ID, + ambiguityStatusFlag-r15 INTEGER (0..3), + non-synch-count-r15 INTEGER (0..7), + geometricCarrierPhaseCorrectionDifference-r15 INTEGER (-65536..65535), + iod-r15 BIT STRING (SIZE(11)), + ionosphericCarrierPhaseCorrectionDifference-r15 INTEGER (-65536..65535), + ... +} + +-- ASN1STOP + +``` + +| GNSS-RTK-MAC-CorrectionDifferences field descriptions | | +|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| networkID | This field provides the network ID. | +| subNetworkID | This field identifies the subnetwork of a network identified by networkID . | +| master-ReferenceStationID | This field specifies the station ID of the Master Reference Station. | +| l1, l2 | These fields specify the dual-frequency combination of L1 and L2 link/frequencies for which the rtkCorrectionDifferencesList is provided. If the fields are absent, the default interpretation in table 'L1/L2 default interpretation' applies. | +| rtkCorrectionDifferencesList | This field provides the correction differences for Auxiliary-Master Reference Station pairs. | +| epochTime | This field specifies the epoch time of observations used to derive the correction differences. The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| auxiliary-referenceStationID | This field specifies the station ID of the Auxiliary Reference Station. | +| svID | This field specifies the satellite for which the data is provided. | +| ambiguityStatusFlag | This field provides the ambiguity status. 'L1' below corresponds to the link indicated by the l1 field; 'L2' below corresponds to the link indicated by the l2 field.
0 - Reserved for future use (artificial observations)
1 - Correct Integer Ambiguity Level for L1 and L2
2 - Correct Integer Ambiguity Level for L1-L2 widelane
3 - Uncertain Integer Ambiguity Level. Only a likely guess is used. | +| non-synch-count | This field provides the count of unrecoverable cycle slips. Whenever an unrecoverable cycle slip occurs this count shall be increased. The counter shall not be increased more than once per minute. Data for satellites with cycle slips more frequent than once per minute should not be provided. | +| geometricCarrierPhaseCorrectionDifference | This field provides the Geometric Carrier Phase Correction Difference (GCPD), which is the Correction Difference for the geometric part (troposphere and orbits) calculated based on integer leveled L1 and L2 correction differences (L1CD and L2CD).

L1CD, L2CD, and ICPD are presented in metres. 'L1' below corresponds to the link indicated by the l1 field; 'L2' below corresponds to the link indicated by the l2 field.
Scale factor 0.5 millimetre; range $\pm 32.767$ metres. | +| iod | This field specifies the IOD value of the broadcast ephemeris used for calculation of Correction Differences (see IE GNSS-NavigationModel ). | + +| GNSS-RTK-MAC-CorrectionDifferences field descriptions | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| ionosphericCarrierPhaseCorrectionDifference
This field provides the Ionospheric Carrier Phase Correction Difference (ICPCD), which is the Correction Difference for the ionospheric part calculated based on integer leveled L1 and L2 correction differences (L1CD and L2CD).

L1CD, L2CD, and ICPCD are presented in metres. 'L1' below corresponds to the link indicated by the l1 field; 'L2' below corresponds to the link indicated by the l2 field.
Scale factor 0.5 millimetre; range $\pm 32.767$ metres. | | + +### L1/L2 default interpretation + +| GNSS | l1 | l2 | +|-------------|------------------|------------------| +| GPS | L1 | L2 | +| SBAS | L1 | L5 | +| QZSS | L1 | L2 | +| Galileo | E1 | E5a | +| GLONASS | G1 | G2 | +| BDS | B1 | B2 | + +## — ***GNSS-RTK-Residuals*** + +The IE *GNSS-RTK-Residuals* is used by the location server to provide Network RTK correction residual error information. + +If the interpolation of the corrections for the target device location is performed at the location server, resulting in a non-physical reference station, the *GNSS-RTK-Residuals* are referenced to the non-physical reference station. + +If the interpolation of the corrections is performed by the target device (e.g., using *GNSS-RTK-MAC-CorrectionDifferences*), the *GNSS-RTK-Residuals* are referenced to the closest master or auxiliary station to the target device. + +The parameters provided in IE *GNSS-RTK-Residuals* are used as specified for message type 1030 and 1031 in [30] and apply to all GNSSs. + +``` +-- ASN1START + +GNSS-RTK-Residuals-r15 ::= SEQUENCE { + epochTime-r15 GNSS-SystemTime, + referenceStationID-r15 GNSS-ReferenceStationID-r15, + n-Refs-r15 INTEGER (0..127), + l1-r15 GNSS-FrequencyID-r15 OPTIONAL, -- Need OP + l2-r15 GNSS-FrequencyID-r15 OPTIONAL, -- Need OP + rtk-residuals-list-r15 RTK-Residuals-List-r15, + ... +} + +RTK-Residuals-List-r15 ::= SEQUENCE (SIZE(1..64)) OF RTK-Residuals-Element-r15 + +RTK-Residuals-Element-r15 ::= SEQUENCE { + svID-r15 SV-ID, + s-oc-r15 INTEGER (0..255), + s-od-r15 INTEGER (0..511), + s-oh-r15 INTEGER (0..63), + s-lc-r15 INTEGER (0..1023), + s-ld-r15 INTEGER (0..1023), + ... +} + +-- ASN1STOP +``` + +| GNSS-RTK-Residuals field descriptions | | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epochTime | This field specifies the epoch time of the Network RTK Residual Error data. The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| referenceStationID | This field specifies the Reference Station ID. The Reference Station may be a physical or non-physical station. | +| n-Refs | This field specifies the number of reference stations used to derive the residual statistics (1 to 127; 127 indicates 127 or more stations). The number of reference stations should never be zero. If zero is encountered the target device should ignore the message. | +| l1, l2 | These fields specify the dual-frequency combination of L1 and L2 link/frequencies for which the rtk residuals-list is provided. If the fields are absent, the default interpretation in table 'L1/L2 default interpretation' in IE GNSS-RTK-MAC-CorrectionDifferences applies. | +| svID | This field specifies the satellite for which the data is provided. | +| s-oc | This field specifies the constant term of standard deviation (1 sigma) for non-dispersive interpolation residuals, $s_{oc}$ . Scale factor 0.5 millimetre; range 0–127 millimetre. NOTE 1. | +| s-od | This field specifies the distance dependent term of standard deviation (1 sigma) for nondispersive interpolation residuals, $s_{od}$ . Scale factor 0.01 ppm; range 0–5.11 ppm. NOTE 1. | +| s-oh | This field specifies the height dependent term of standard deviation (1 sigma) for nondispersive interpolation residuals, $s_{oh}$ . Scale factor 0.1 ppm; range 0–5.1 ppm. NOTE 1. | +| s-lc | This field specifies the constant term of standard deviation (1 sigma) for dispersive interpolation residuals (as affecting L1 frequency), $s_{lc}$ . 'L1' corresponds to the link indicated by the l1 field. Scale factor 0.5 millimetre; range 0–511 millimetre | +| s-ld | This field specifies the distance dependent term of standard deviation (1 sigma) for dispersive interpolation residuals (as affecting L1 frequency), $s_{ld}$ . 'L1' corresponds to the link indicated by the l1 field. NOTE 2. | + +NOTE 1: The complete standard deviation for the expected non-dispersive interpolation residual is computed from $s_{oc}$ , $s_{od}$ and $s_{oh}$ using the formula: + +where $d_{ref}$ is the distance of the target device from the nearest physical reference station in [km] and $|dh_{ref}|$ is the absolute value of the height difference between the nearest physical reference station and the target device in [km]. + +NOTE 2: The complete standard deviation for the expected dispersive interpolation residual is computed from $s_{lc}$ and $s_{ld}$ using the formula: + +where $d_{ref}$ is the distance of the target device from the nearest physical reference station in [km]. +The standard deviation for the L2 frequency is calculated using the formula: +. 'L2' corresponds to the link indicated by the *l2* field; $\lambda_1=c/f_1$ , $\lambda_2=c/f_2$ are the nominal wavelengths of the links indicated by the *l1*, *l2* fields, respectively. + +## – GNSS-RTK-FKP-Gradients + +The IE *GNSS-RTK-FKP-Gradients* is used by the location server to provide the FKP Network RTK gradients of distance-dependent errors like ionosphere, troposphere and orbits. The target device may use the gradients to compute the influence of the distance dependent errors for its own position. + +The parameters provided in IE *GNSS-RTK-FKP-Gradients* are used as specified for message type 1034 and 1035 in [30] and apply to all GNSSs. + +``` +-- ASN1START +GNSS-RTK-FKP-Gradients-r15 ::= SEQUENCE { + referenceStationID-r15 GNSS-ReferenceStationID-r15, + epochTime-r15 GNSS-SystemTime, + l1-r15 GNSS-FrequencyID-r15 OPTIONAL, -- Need OP +``` + +``` + +12-r15 GNSS-FrequencyID-r15 OPTIONAL, -- Need OP + fkp-gradients-list-r15 FKP-Gradients-List-r15, + ... +} + +FKP-Gradients-List-r15 ::= SEQUENCE (SIZE(1..64)) OF FKP-Gradients-Element-r15 + +FKP-Gradients-Element-r15 ::= SEQUENCE { + svID-r15 SV-ID, + iod-r15 BIT STRING (SIZE(11)), + north-geometric-gradient-r15 INTEGER (-2048..2047), + east-geometric-gradient-r15 INTEGER (-2048..2047), + north-ionospheric-gradient-r15 INTEGER (-8192..8191), + east-ionospheric-gradient-r15 INTEGER (-8192..8191), + ... +} + +-- ASN1STOP + +``` + +| GNSS-RTK-FKP-Gradients field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| referenceStationID
This field specifies the Reference Station ID. The Reference Station may be a physical or non-physical station. | +| epochTime
This field specifies the epoch time of the FKP data. The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| l1, l2
These fields specify the dual-frequency combination of L1 and L2 link/frequencies for which the fkp-gradients-list is provided. If the fields are absent, the default interpretation in table 'L1/L2 default interpretation' in IE GNSS-RTK-MAC-CorrectionDifferences applies. NOTE. | +| svID
This field specifies the satellite for which the data is provided. | +| iod
This field specifies the IOD value of the broadcast ephemeris used for calculation of FKP data (see IE GNSS-NavigationModel ). | +| north-geometric-gradient
This field specifies the gradient (FKP) of the geometric (non-dispersive) error components in South-North direction in parts per million of the south-north distance to the reference station.
Scale factor 0.01 ppm; range $\pm 20.47$ ppm. | +| east-geometric-gradient
This field specifies the gradient (FKP) of the geometric (non-dispersive) error components in West-East direction in parts per million of the west-east distance to the reference station.
Scale factor 0.01 ppm; range $\pm 20.47$ ppm. | +| north-ionospheric-gradient
This field specifies the gradient (FKP) of the ionospheric (dispersive) error component in South-North direction.
Scale factor 0.01 ppm; range $\pm 81.91$ ppm. | +| east-ionospheric-gradient
This field specifies the gradient (FKP) of the ionospheric (dispersive) error component in West-East direction.
Scale factor 0.01 ppm; range $\pm 81.91$ ppm. | + +NOTE: As described in [30], the distance dependent error for the geometric part $\delta\rho_0$ and ionospheric part $\delta\rho_1$ is computed from the gradients provided in *FKP-Gradients-Element*. The distance dependent error for a carrier phase measurements $\Phi$ on a signal with frequency $f$ can be computed by: + +where $f_l, f$ is the link/frequency indicated by the *l1, l2* fields, respectively. + +## GNSS-SSR-OrbitCorrections + +The IE *GNSS-SSR-OrbitCorrections* is used by the location server to provide radial, along-track and cross-track orbit corrections together with integrity information. The target device may use the *SSR-OrbitCorrectionList* to compute a satellite position correction to be combined with the satellite position calculated from broadcast ephemeris. + +The parameters provided in IE *GNSS-SSR-OrbitCorrections* – except for *ORBIT-IntegrityParameters* and *SSR-IntegrityOrbitBounds* – are used as specified for SSR Orbit Messages (e.g., message type 1057 and 1063) in [30] and apply to all GNSSs. + +``` + +-- ASN1START + +GNSS-SSR-OrbitCorrections-r15 ::= SEQUENCE { + epochTime-r15 GNSS-SystemTime, + ssrUpdateInterval-r15 INTEGER (0..15), + satelliteReferenceDatum-r15 ENUMERATED { itrf, regional, ... }, + iod-ssr-r15 INTEGER (0..15), + ssr-OrbitCorrectionList-r15 SSR-OrbitCorrectionList-r15, + ... + [[ + orbit-IntegrityParameters-r17 ORBIT-IntegrityParameters-r17 OPTIONAL -- Need OR + ]] +} + +SSR-OrbitCorrectionList-r15 ::= SEQUENCE (SIZE(1..64)) OF SSR-OrbitCorrectionSatelliteElement-r15 + +SSR-OrbitCorrectionSatelliteElement-r15 ::= SEQUENCE { + svID-r15 SV-ID, + iod-r15 BIT STRING (SIZE(11)), + delta-radial-r15 INTEGER (-2097152..2097151), + delta-AlongTrack-r15 INTEGER (-524288..524287), + delta-CrossTrack-r15 INTEGER (-524288..524287), + dot-delta-radial-r15 INTEGER (-1048576..1048575) OPTIONAL, -- Need ON + dot-delta-AlongTrack-r15 INTEGER (-262144..262143) OPTIONAL, -- Need ON + dot-delta-CrossTrack-r15 INTEGER (-262144..262143) OPTIONAL, -- Need ON + ... + [[ + ssr-IntegrityOrbitBounds-r17 SSR-IntegrityOrbitBounds-r17 OPTIONAL -- Cond Integrity1 + ]] +} + +ORBIT-IntegrityParameters-r17 ::= SEQUENCE { + probOnsetConstFault-r17 INTEGER (0..255), + meanConstFaultDuration-r17 INTEGER (1..3600), + probOnsetSatFault-r17 INTEGER (0..255), + meanSatFaultDuration-r17 INTEGER (1..3600), + orbitRangeErrorCorrelationTime-r17 INTEGER (0..255) OPTIONAL, -- Need OR + orbitRangeRateErrorCorrelationTime-r17 INTEGER (0..255) OPTIONAL, -- Cond Integrity2 + ... +} + +SSR-IntegrityOrbitBounds-r17 ::= SEQUENCE { + meanOrbitError-r17 RAC-OrbitalErrorComponents-r17, + stdDevOrbitError-r17 RAC-OrbitalErrorComponents-r17, + meanOrbitRateError-r17 RAC-OrbitalErrorComponents-r17, + stdDevOrbitRateError-r17 RAC-OrbitalErrorComponents-r17, + ... +} + +RAC-OrbitalErrorComponents-r17 ::= SEQUENCE { + radial-r17 INTEGER (0..255), + alongTrack-r17 INTEGER (0..255), + crossTrack-r17 INTEGER (0..255) +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------| +| Integrity1 | The field is mandatory present if ORBIT-IntegrityParameters is present; otherwise it is not present. | +| Integrity2 | The field is mandatory present if orbitRangeErrorCorrelationTime is present; otherwise it is not present. | + +| GNSS-SSR-OrbitCorrections field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epochTime
This field specifies the epoch time of the orbit corrections. The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| ssrUpdateInterval
This field specifies the SSR Update Interval. The SSR Update Intervals for all SSR parameters start at time 00:00:00 of the GPS time scale. A change of the SSR Update Interval during the transmission of SSR data should ensure consistent data for a target device. See table Value of ssrUpdateInterval to SSR Update Interval relation below. NOTE 1. | +| satelliteReferenceDatum
This field specifies the satellite reference datum for the orbit corrections. | +| iod-ssr
This field specifies the Issue of Data number for the SSR data. A change of iod-ssr is used to indicate a change in the SSR generating configuration. | +| svID
This field specifies the satellite for which the orbit corrections are provided. | +| iod
This field specifies the IOD value of the broadcast ephemeris for which the orbit corrections are valid (see IE GNSS-NavigationModel ). NOTE 2, NOTE 4. | +| delta-radial
This field specifies the radial orbit correction for broadcast ephemeris. NOTE 3.
Scale factor 0.1 mm; range $\pm 209.7151$ m. | +| delta-AlongTrack
This field specifies the along-track orbit correction for broadcast ephemeris. NOTE 3.
Scale factor 0.4 mm; range $\pm 209.7148$ m. | +| delta-CrossTrack
This field specifies the cross-track orbit correction for broadcast ephemeris. NOTE 3.
Scale factor 0.4 mm; range $\pm 209.7148$ m. | +| dot-delta-radial
This field specifies the velocity of radial orbit correction for broadcast ephemeris. NOTE 3.
Scale factor 0.001 mm/s; range $\pm 1.048575$ m/s. | +| dot-delta-AlongTrack
This field specifies the velocity of along-track orbit correction for broadcast ephemeris. NOTE 3.
Scale factor 0.004 mm/s; range $\pm 1.048572$ m/s. | +| dot-delta-CrossTrack
This field specifies the velocity of cross-track orbit correction for broadcast ephemeris. NOTE 3.
Scale factor 0.004 mm/s; range $\pm 1.048572$ m/s. | +| probOnsetConstFault
This field specifies the Probability of Onset of Constellation Fault per Time Unit where a constellation fault is at least two satellites being faulty simultaneously due to the same event.
This field specifies the onset probability that the residual range or range rate error exceeds a bound created using the minimum allowed inflation factor $K_{min}$ , and bounding parameters as $mean + K_{min} * stdDev$ where $K_{min} = normInv(irMaximum / 2)$ , with irMaximum as provided in IE GNSS-Integrity-ServiceParameters .
The probability is calculated by $P=10^{-0.04n}$ [hour -1 ] where n is the value of probOnsetConstFault and the range is $10^{-10.2}$ to 1 per hour. | +| meanConstFaultDuration
This field specifies the Mean Constellation Fault Duration which is the mean duration between when a constellation fault occurs, and the user is alerted by IE GNSS-RealTimeIntegrity (or the integrity violation is over).
Scale factor 1 s; range 1-3600 s. | +| probOnsetSatFault
This field specifies the Probability of Onset of Satellite Fault per Time Unit which is the probability of occurrence of satellite error to exceed the residual error bound for more than the Time to Alert (TTA).
This field specifies the onset probability that the residual range or range rate error exceeds a bound created using the minimum allowed inflation factor $K_{min}$ , and bounding parameters as $mean + K_{min} * stdDev$ where $K_{min} = normInv(irMaximum / 2)$ , with irMaximum as provided in IE GNSS-Integrity-ServiceParameters .
The probability is calculated by $P=10^{-0.04n}$ [hour -1 ] where n is the value of probOnsetSatFault and the range is $10^{-10.2}$ to 1 per hour. | +| meanSatFaultDuration
This field specifies the Mean Satellite Fault Duration which is the mean duration between when a satellite fault occurs, and the user is alerted by IE GNSS-RealTimeIntegrity (or the integrity violation is over).
Scale factor 1 s; range 1-3,600 s. | +| orbitRangeErrorCorrelationTime
This field specifies the Orbit Range Error Correlation Time which is the upper bound of the correlation time of the satellite residual range error due to orbit.
The time is calculated using:

Range is 1-28,200 s. | + +| GNSS-SSR-OrbitCorrections field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| orbitRangeRateErrorCorrelationTime
This field specifies the Orbit Range Rate Error Correlation Time which is the upper bound of the correlation time of the satellite residual range rate error due to orbit.
The time is calculated using:
Range is 1-28,200 s. | +| meanOrbitError
This field specifies the Mean Orbit Error bound in satellite radial, along-track and cross-track coordinates, which are the mean values for a set of three overbounding models that bound the residual orbit error in satellite radial, along-track and cross-track directions.
Each mean is calculated using:
Range is 0-17.5 m. | +| stdDevOrbitError
This field specifies the Standard Deviation Orbit Error bound in satellite radial, along-track and cross-track coordinates, which are the standard deviation values for a set of three overbounding models that bound the residual orbit error in satellite radial, along-track and cross-track directions.
Each standard deviation is calculated using:
Range is 0-17.5 m. | +| meanOrbitRateError
This field specifies the Mean Orbit Rate Error in satellite radial, along-track and cross-track coordinates, which are the mean values for a set of three overbounding models that bound the residual satellite orbit rate error in satellite radial, along-track and cross-track directions.
Scale factor 0.001 m/s; range 0-0.255 m/s. | +| stdDevOrbitRateError
This field specifies the Standard Deviation Orbit Rate Error in satellite radial, along-track and cross-track coordinates, which are the standard deviation values for a set of three overbounding models that bound the residual satellite orbit rate error in satellite radial, along-track and cross-track directions.
Scale factor 0.001 m/s; range 0-0.255 m/s. | + +NOTE 1: The update intervals are aligned to the GPS time scale for all GNSSs in order to allow synchronous operation for multiple GNSS services. This means that the update intervals may not be aligned to the beginning of the day for another GNSS. Due to the leap seconds, this is generally the case for GLONASS. + +NOTE 2: In the cases that *gnss-ID* indicates 'gps', 'qzss' or 'bds', the *iod* refers to the NAV broadcast ephemeris (GPS L1 C/A, QZSS QZS-L1 or BDS B1I/B3I, respectively, in table GNSS to iod Bit String(11) relation in IE *GNSS-NavigationModel*). + +NOTE 3: The reference time $t_0$ is $epochTime + \frac{1}{2} \times ssrUpdateInterval$ . The reference time $t_0$ for *ssrUpdateInterval* '0' is *epochTime*. + +NOTE 4: In the cases that the *GNSS-SSR-OrbitCorrection* IE is contained within a *GNSS-SSR-OrbitCorrectionsSet2* IE, then the reference ephemeris is denoted by the *refEph* field within the *GNSS-SSR-OrbitCorrectionsSet2* IE, not the default as per NOTE 2. In the case *gnss-ID* indicates 'bds' and if *refEph* is set to *b1c*, the *iod* refers to the B-CNAV1 broadcast ephemeris (BDS B1C/B2a in table GNSS to iod Bit String (11) relation in IE *GNSS-NavigationModel*). + +### Value of *ssrUpdateInterval* to SSR Update Interval relation + +| Value of ssrUpdateInterval | SSR Update Interval | +|-----------------------------------|---------------------| +| 0 | 1 second | +| 1 | 2 seconds | +| 2 | 5 seconds | +| 3 | 10 seconds | +| 4 | 15 seconds | +| 5 | 30 seconds | +| 6 | 60 seconds | +| 7 | 120 seconds | +| 8 | 240 seconds | +| 9 | 300 seconds | +| 10 | 600 seconds | +| 11 | 900 seconds | +| 12 | 1800 seconds | +| 13 | 3600 seconds | +| 14 | 7200 seconds | +| 15 | 10800 seconds | + +### GNSS-SSR-ClockCorrections + +The IE *GNSS-SSR-ClockCorrections* is used by the location server to provide clock correction parameters together with integrity information. The target device may use the *SSR-ClockCorrectionList* to compute a clock correction to be applied to the broadcast satellite clock parameters, identified by *iod* of corresponding *GNSS-SSR-OrbitCorrections*. + +The parameters provided in IE *GNSS-SSR-ClockCorrections* – except for *CLOCK-IntegrityParameters* and *SSR-IntegrityClockBounds* – are used as specified for SSR Clock Messages (e.g., message type 1058 and 1064) in [30] and apply to all GNSSs. + +``` +-- ASN1START + +GNSS-SSR-ClockCorrections-r15 ::= SEQUENCE { + epochTime-r15 GNSS-SystemTime, + ssrUpdateInterval-r15 INTEGER (0..15), + iod-ssr-r15 INTEGER (0..15), + ssr-ClockCorrectionList-r15 SSR-ClockCorrectionList-r15, + ... + [[ + clock-IntegrityParameters-r17 CLOCK-IntegrityParameters-r17 OPTIONAL -- Need OR + ]] +} + +SSR-ClockCorrectionList-r15 ::= SEQUENCE (SIZE(1..64)) OF SSR-ClockCorrectionSatelliteElement-r15 + +SSR-ClockCorrectionSatelliteElement-r15 ::= SEQUENCE { + svID-r15 SV-ID, + delta-Clock-C0-r15 INTEGER (-2097152..2097151), + delta-Clock-C1-r15 INTEGER (-1048576..1048575) OPTIONAL, -- Need ON + delta-Clock-C2-r15 INTEGER (-67108864..67108863) OPTIONAL, -- Need ON + ... + [[ + ssr-IntegrityClockBounds-r17 SSR-IntegrityClockBounds-r17 OPTIONAL -- Need OR + ]] +} + +CLOCK-IntegrityParameters-r17 ::= SEQUENCE { + clockRangeErrorCorrelationTime-r17 INTEGER (0..255), + clockRangeRateErrorCorrelationTime-r17 INTEGER (0..255), + ... +} + +SSR-IntegrityClockBounds-r17 ::= SEQUENCE { + meanClock-r17 INTEGER (0..255), + stdDevClock-r17 INTEGER (0..255), + meanClockRate-r17 INTEGER (0..255), + stdDevClockRate-r17 INTEGER (0..255), + ... +} +``` + +} + +-- ASN1STOP + +| GNSS-SSR-ClockCorrections field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epochTime
This field specifies the epoch time of the clock corrections. The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| ssrUpdateInterval
This field specifies the SSR Update Interval. The SSR Update Intervals for all SSR parameters start at time 00:00:00 of the GPS time scale. A change of the SSR Update Interval during the transmission of SSR data should ensure consistent data for a target device. See table Value of ssrUpdateInterval to SSR Update Interval relation in IE GNSS-SSR- OrbitCorrections . | +| iod-ssr
This field specifies the Issue of Data number for the SSR data. A change of iod-ssr is used to indicate a change in the SSR generating configuration. | +| svID
This field specifies the satellite for which the clock corrections are provided. | +| delta-Clock-C0
This field specifies the $C_0$ polynomial coefficient for correction of broadcast satellite clock. NOTE 1.
Scale factor 0.1 mm; range $\pm 209.7151$ m. | +| delta-Clock-C1
This field specifies the $C_1$ polynomial coefficient for correction of broadcast satellite clock. NOTE 1.
Scale factor 0.001 mm/s; range $\pm 1.048575$ m/s. | +| delta-Clock-C2
This field specifies the $C_2$ polynomial coefficient for correction of broadcast satellite clock. NOTE 1.
Scale factor 0.00002 mm/s 2 ; range $\pm 1.34217726$ m/s 2 . | +| clockRangeErrorCorrelationTime
This field specifies the Clock Range Error Correlation Time which is the upper bound of the correlation time of the satellite residual range error due to clock.
The time is calculated using:

Range is 1-28,200 s. | +| clockRangeRateErrorCorrelationTime
This field specifies the Clock Range Rate Error Correlation Time which is the upper bound of the correlation time of the satellite residual range rate error due to clock.
The time is calculated using:

Range is 1-28,200 s. | +| meanClock
This field specifies the Mean Clock Error bound which is the mean value for an overbounding model that bounds the residual clock error.
The bound is $meanClock + K * stdDevClock$ and shall be so that the probability of it to be exceeded shall be lower than IRallocation for $irMinimum < IRallocation < irMaximum$ , where $K = \text{normInv}(IRallocation / 2)$ and irMinimum , irMaximum as provided in IE GNSS-Integrity-ServiceParameters .
This IRallocation is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
The mean is calculated using:

Range is 0-17.5 m. | +| stdDevClock
This field specifies the Standard Deviation Clock Error bound which is the standard deviation for an overbounding model that bounds the residual clock error.
The standard deviation is calculated using:

Range is 0-17.5 m. | +| meanClockRate
This field specifies the Mean Clock Rate Error bound which is the mean value for an overbounding model that bounds the residual clock rate error.
The bound is $meanClockRate + K * stdDevClockRate$ and shall be so that the probability of it to be exceeded shall be lower than IRallocation for $irMinimum < IRallocation < irMaximum$ , where $K = \text{normInv}(IRallocation / 2)$ and irMinimum , irMaximum as provided in IE GNSS-Integrity-ServiceParameters .
This IRallocation is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
Scale factor 0.001 m/s; range 0.000-0.255 m/s. | +| stdDevClockRate
This field specifies the Standard Deviation Clock Rate Error bound which is the standard deviation for an overbounding model that bounds the residual clock rate error.
Scale factor 0.001 m/s; range 0.000-0.255 m/s. | + +NOTE 1: The reference time $t_0$ is $epochTime + \frac{1}{2} \times ssrUpdateInterval$ . The reference time $t_0$ for $ssrUpdateInterval$ '0' is $epochTime$ . + +## – GNSS-SSR-CodeBias + +The IE *GNSS-SSR-CodeBias* is used by the location server to provide GNSS signal code bias together with integrity information. The target device may add the code bias to the pseudo-range measurement of the corresponding code signal to get corrected pseudo-ranges. + +NOTE: Any code biases transmitted in the broadcast messages (e.g., the GPS group delay differential $T_{GD}$ [4] (*NAV-ClockModel*)) are not applied at all by the target device. + +The parameters provided in IE *GNSS-SSR-CodeBias* – except for *SSR-IntegrityCodeBiasBounds* – are used as specified for SSR Code Bias Messages (e.g., message type 1059 and 1065) in [30] and apply to all GNSSs. + +``` +-- ASN1START + +GNSS-SSR-CodeBias-r15 ::= SEQUENCE { + epochTime-r15 GNSS-SystemTime, + ssrUpdateInterval-r15 INTEGER (0..15), + iod-ssr-r15 INTEGER (0..15), + ssr-CodeBiasSatList-r15 SSR-CodeBiasSatList-r15, + ... +} + +SSR-CodeBiasSatList-r15 ::= SEQUENCE (SIZE(1..64)) OF SSR-CodeBiasSatElement-r15 + +SSR-CodeBiasSatElement-r15 ::= SEQUENCE { + svID-r15 SV-ID, + ssr-CodeBiasSignalList-r15 SSR-CodeBiasSignalList-r15, + ... +} + +SSR-CodeBiasSignalList-r15 ::= SEQUENCE (SIZE(1..16)) OF SSR-CodeBiasSignalElement-r15 + +SSR-CodeBiasSignalElement-r15 ::= SEQUENCE { + signal-and-tracking-mode-ID-r15 GNSS-SignalID, + codeBias-r15 INTEGER (-8192..8191), + ..., + [[ + ssr-IntegrityCodeBiasBounds-r17 SSR-IntegrityCodeBiasBounds-r17 OPTIONAL -- Need OR + ]] +} + +SSR-IntegrityCodeBiasBounds-r17 ::= SEQUENCE { + meanCodeBias-r17 INTEGER (0..255), + stdDevCodeBias-r17 INTEGER (0..255), + meanCodeBiasRate-r17 INTEGER (0..255), + stdDevCodeBiasRate-r17 INTEGER (0..255), + ... +} + +-- ASN1STOP +``` + +| GNSS-SSR-CodeBias field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epochTime
This field specifies the epoch time of the code bias data. The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| ssrUpdateInterval
This field specifies the SSR Update Interval. The SSR Update Intervals for all SSR parameters start at time 00:00:00 of the GPS time scale. A change of the SSR Update Interval during the transmission of SSR data should ensure consistent data for a target device. See table Value of ssrUpdateInterval to SSR Update Interval relation in IE GNSS-SSR- OrbitCorrections . | +| iod-ssr
This field specifies the Issue of Data number for the SSR data. A change of iod-ssr is used to indicate a change in the SSR generating configuration. | +| svID
This field specifies the GNSS satellite for which the code biases are provided. | +| signal-and-tracking-mode-ID
This field specifies the GNSS signal for which the code biases are provided. | +| codeBias
This field provides the code bias for the GNSS signal indicated by signal-and-tracking-mode-ID .
Scale factor 0.01 m; range $\pm 81.91$ m. | +| meanCodeBias
This field specifies the Mean Code Bias Error bound which is the mean value for an overbounding model that bounds the residual code bias error.
The bound is $\text{meanCodeBias} + K * \text{stdDevCodeBias}$ and shall be so that the probability of it to be exceeded shall be lower than $\text{IR}_{\text{allocation}}$ for $\text{irMinimum} < \text{IR}_{\text{allocation}} < \text{irMaximum}$ , where $K = \text{normInv}(\text{IR}_{\text{allocation}} / 2)$ and $\text{irMinimum}$ , $\text{irMaximum}$ as provided in IE GNSS-Integrity-ServiceParameters .
This $\text{IR}_{\text{allocation}}$ is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
Scale factor 0.005 m; range 0-1.275 m. | +| stdDevCodeBias
This field specifies the Standard Deviation Code Bias Error bound which is the standard deviation for an overbounding model that bounds the residual code bias error.
Scale factor 0.005 m; range 0-1.275 m. | +| meanCodeBiasRate
This field specifies the Mean Code Bias Rate Error bound which is the mean value for an overbounding model that bounds the residual code bias rate error.
The bound is $\text{meanCodeBiasRate} + K * \text{stdDevCodeBiasRate}$ and shall be so that the probability of it to be exceeded shall be lower than $\text{IR}_{\text{allocation}}$ for $\text{irMinimum} < \text{IR}_{\text{allocation}} < \text{irMaximum}$ , where $K = \text{normInv}(\text{IR}_{\text{allocation}} / 2)$ and $\text{irMinimum}$ , $\text{irMaximum}$ as provided in IE GNSS-Integrity-ServiceParameters .
This $\text{IR}_{\text{allocation}}$ is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
Scale factor 0.00005 m/s; range 0-0.01275 m/s. | +| stdDevCodeBiasRate
This field specifies the Standard Deviation Code Bias Rate Error bound which is the standard deviation for an overbounding model that bounds the residual code bias rate error.
Scale factor 0.00005 m/s; range 0-0.01275 m/s. | + +## — GNSS-SSR-URA + +The IE *GNSS-SSR-URA* is used by the location server to provide quality information for the provided SSR assistance data. + +The parameters provided in IE *GNSS-SSR-URA* are used as specified for the SSR URA Messages (e.g., message type 1061 and 1067) in [30] and apply to all GNSSs. + +``` +-- ASN1START + +GNSS-SSR-URA-r16 ::= SEQUENCE { + epochTime-r16 GNSS-SystemTime, + ssrUpdateInterval-r16 INTEGER (0..15), + iod-ssr-r16 INTEGER (0..15), + ssr-URA-SatList-r16 SSR-URA-SatList-r16, + ... +} + +SSR-URA-SatList-r16 ::= SEQUENCE (SIZE(1..64)) OF SSR-URA-SatElement-r16 + +SSR-URA-SatElement-r16 ::= SEQUENCE { + svID-r16 SV-ID, + ssr-URA-r16 BIT STRING (SIZE (6)), + ... +} +``` + +| GNSS-SSR-URA field descriptions | | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epochTime | This field specifies the epoch time of the SSR User Range Accuracy (URA). The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| ssrUpdateInterval | This field specifies the SSR Update Interval. The SSR Update Intervals for all SSR parameters start at time 00:00:00 of the GPS time scale. A change of the SSR Update Interval during the transmission of SSR data should ensure consistent data for a target device. See table Value of ssrUpdateInterval to SSR Update Interval relation in IE GNSS-SSR-OrbitCorrections . | +| iod-ssr | This field specifies the Issue of Data number for the SSR data. A change of iod-ssr is used to indicate a change in the SSR generating configuration. | +| svID | This field specifies the GNSS satellite for which the SSR URA is provided. | +| ssr-URA | This field specifies the User Range Accuracy (URA) (1-sigma) for the range correction provided in the SSR assistance data. The URA is represented by a combination of CLASS and VALUE. The 3 MSB define the CLASS with a range of 0-7 and the 3 LSB define the VALUE with a range of 0-7. The URA is computed by:

See Table 'Relationship between SSR troposphere quality and URA indicator and physical quantity' in IE GNSS-SSR-GriddedCorrection . | + +## GNSS-SSR-PhaseBias + +The IE *GNSS-SSR-PhaseBias* is used by the location server to provide GNSS signal phase bias together with integrity information. The target device may add the phase bias to the phase-range measurement of the corresponding phase signal to get corrected phase-ranges. + +The parameters provided in IE *GNSS-SSR-PhaseBias* – except for *SSR-IntegrityPhaseBiasBounds* – are used as specified for Compact SSR GNSS Satellite Phase Bias Messages (e.g., message type 4073,5) in [43] and apply to all GNSSs. + +``` +-- ASN1START + +GNSS-SSR-PhaseBias-r16 ::= SEQUENCE { + epochTime-r16 GNSS-SystemTime, + ssrUpdateInterval-r16 INTEGER (0..15), + iod-ssr-r16 INTEGER (0..15), + ssr-PhaseBiasSatList-r16 SSR-PhaseBiasSatList-r16, + ... +} + +SSR-PhaseBiasSatList-r16 ::= SEQUENCE (SIZE(1..64)) OF SSR-PhaseBiasSatElement-r16 + +SSR-PhaseBiasSatElement-r16 ::= SEQUENCE { + svID-r16 SV-ID, + ssr-PhaseBiasSignalList-r16 SSR-PhaseBiasSignalList-r16, + ... +} + +SSR-PhaseBiasSignalList-r16 ::= SEQUENCE (SIZE(1..16)) OF SSR-PhaseBiasSignalElement-r16 + +SSR-PhaseBiasSignalElement-r16 ::= SEQUENCE { + signal-and-tracking-mode-ID-r16 GNSS-SignalID, + phaseBias-r16 INTEGER (-16384..16383), + phaseDiscontinuityIndicator-r16 INTEGER (0..3), + phaseBiasIntegerIndicator-r16 INTEGER (0..3) OPTIONAL, -- Need OP + ..., + [[ + ssr-IntegrityPhaseBiasBounds-r17 SSR-IntegrityPhaseBiasBounds-r17 OPTIONAL -- Need OR + ]] +} + +SSR-IntegrityPhaseBiasBounds-r17 ::= SEQUENCE { + meanPhaseBias-r17 INTEGER (0..255), +} +``` + +``` + + stdDevPhaseBias-r17 INTEGER (0..255), + meanPhaseBiasRate-r17 INTEGER (0..255), + stdDevPhaseBiasRate-r17 INTEGER (0..255), + ... +} + +-- ASN1STOP + +``` + +### GNSS-SSR-PhaseBias field descriptions + +#### **epochTime** + +This field specifies the epoch time of the phase bias data. The *gnss-TimeID* in *GNSS-SystemTime* shall be the same as the *GNSS-ID* in IE *GNSS-GenericAssistDataElement*. + +#### **ssrUpdateInterval** + +This field specifies the SSR Update Interval. The SSR Update Intervals for all SSR parameters start at time 00:00:00 of the GPS time scale. A change of the SSR Update Interval during the transmission of SSR data should ensure consistent data for a target device. See table Value of *ssrUpdateInterval* to SSR Update Interval relation in IE *GNSS-SSR- OrbitCorrections*. + +#### **iod-ssr** + +This field specifies the Issue of Data number for the SSR data. A change of *iod-ssr* is used to indicate a change in the SSR generating configuration. + +#### **svID** + +This field specifies the GNSS satellite for which the phase biases are provided. + +#### **signal-and-tracking-mode-ID** + +This field specifies the GNSS signal for which the phase biases are provided. + +#### **phaseBias** + +This field provides the phase bias for the GNSS signal indicated by *signal-and-tracking-mode-ID*. Scale factor 0.001 m; range $\pm 16.383$ m. + +#### **phaseDiscontinuityIndicator** + +This field provides the phase discontinuity counter for the GNSS signal indicated by *signal-and-tracking-mode-ID*. This counter is increased for every discontinuity in phase (roll-over from 3 to 0). + +#### **phaseBiasIntegerIndicator** + +This field informs whether the phase bias is Undifferenced Integer (Value 0), Widelane Integer (Value 1) or Non-Integer (Value 2): + +Value 0: The Undifferenced Integer Phase Bias supports PPP-RTK fixed, widelane or float mode. + +Value 1: The Widelane Integer Phase Bias indicates that after application of the Phase Bias value, this signal can be differenced with any other signal from the same satellite that also has Widelane Integer Phase Bias indicated to form a new combined carrier phase measurement of integer quality, supporting PPP-RTK widelane fixed mode. + +Value 2: The Non-Integer Phase Bias supports PPP-RTK float mode. + +Value 3: Reserved. + +If the *phaseBiasIntegerIndicator* field is not present then it is interpreted as having Value 0 (Undifferenced Integer). + +#### **meanPhaseBias** + +This field specifies the Mean Phase Bias Error bound which is the mean value for an overbounding model that bounds the residual phase bias error. + +The bound is $meanPhaseBias + K * stdDevPhaseBias$ and shall be so that the probability of it to be exceeded shall be lower than $IR_{allocation}$ for $irMinimum < IR_{allocation} < irMaximum$ , where $K = \text{normInv}(IR_{allocation} / 2)$ and $irMinimum$ , $irMaximum$ as provided in IE *GNSS-Integrity-ServiceParameters*. + +This $IR_{allocation}$ is a fraction of the Target Integrity Risk that represents the integrity risk budget available. + +Scale factor 0.005 m; range 0-1.275 m. + +#### **stdDevPhaseBias** + +This field specifies the Standard Deviation Phase Bias Error bound which is the standard deviation for an overbounding model that bounds the residual phase bias error. + +Scale factor 0.005 m; range 0-1.275 m. + +#### **meanPhaseBiasRate** + +This field specifies the Mean Phase Bias Rate Error bound which is the mean value for an overbounding model that bounds the residual phase bias rate error. + +The bound is $meanPhaseBiasRate + K * stdDevPhaseBiasRate$ and shall be so that the probability of it to be exceeded shall be lower than $IR_{allocation}$ for $irMinimum < IR_{allocation} < irMaximum$ , where $K = \text{normInv}(IR_{allocation} / 2)$ and $irMinimum$ , $irMaximum$ as provided in IE *GNSS-Integrity-ServiceParameters*. + +This $IR_{allocation}$ is a fraction of the Target Integrity Risk that represents the integrity risk budget available. + +Scale factor 0.00005 m/s; range 0-0.01275 m/s. + +#### **stdDevPhaseBiasRate** + +This field specifies the Standard Deviation Phase Bias Rate Error bound which is the standard deviation for an overbounding model that bounds the residual phase bias rate error. + +Scale factor 0.00005 m/s; range 0-0.01275 m/s. + +## – GNSS-SSR-STECCorrection + +The IE *GNSS-SSR-STECCorrection* is used by the location server to provide ionosphere slant delay correction together with integrity information. The ionosphere slant delay (STEC) consists of the polynomial part provided in *GNSS-SSR-STECCorrection* and the residual part provided in *GNSS-SSR-GriddedCorrection*. + +The parameters provided in IE *GNSS-SSR-STECCorrection* – except for *STEC-IntegrityParameters* and *STEC-IntegrityErrorBounds* – are used as specified for Compact SSR STEC Correction Messages (e.g., message type 4073,8) in [43] and apply to all GNSSs. + +``` +-- ASN1START + +GNSS-SSR-STECCorrection-r16 ::= SEQUENCE { + epochTime-r16 GNSS-SystemTime, + ssrUpdateInterval-r16 INTEGER (0..15), + iod-ssr-r16 INTEGER (0..15), + correctionPointSetID-r16 INTEGER (0..16383), + stec-SatList-r16 STEC-SatList-r16, + ... + [[ + stec-IntegrityParameters-r17 STEC-IntegrityParameters-r17 OPTIONAL -- Need OR + ]] +} + +STEC-SatList-r16 ::= SEQUENCE (SIZE(1..64)) OF STEC-SatElement-r16 + +STEC-SatElement-r16 ::= SEQUENCE { + svID-r16 SV-ID, + stecQualityIndicator-r16 BIT STRING (SIZE(6)), + stec-C00-r16 INTEGER (-8192..8191), + stec-C01-r16 INTEGER (-2048..2047) OPTIONAL, -- Need ON + stec-C10-r16 INTEGER (-2048..2047) OPTIONAL, -- Need ON + stec-C11-r16 INTEGER (-512..511) OPTIONAL, -- Need ON + ... + [[ + stec-IntegrityErrorBounds-r17 STEC-IntegrityErrorBounds-r17 OPTIONAL -- Cond Integrity1 + ]] +} + +STEC-IntegrityParameters-r17 ::= SEQUENCE { + probOnsetIonoFault-r17 INTEGER (0..255), + meanIonoFaultDuration-r17 INTEGER (1..256), + ionoRangeErrorCorrelationTime-r17 INTEGER (1..255) OPTIONAL, -- Need OR + ionoRangeRateErrorCorrelationTime-r17 INTEGER (1..255) OPTIONAL, -- Cond Integrity2 + ... +} + +STEC-IntegrityErrorBounds-r17 ::= SEQUENCE { + meanIonosphere-r17 INTEGER (0..255), + stdDevIonosphere-r17 INTEGER (0..255), + meanIonosphereRate-r17 INTEGER (0..255), + stdDevIonosphereRate-r17 INTEGER (0..255), + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------| +| Integrity1 | The field is mandatory present if STEC-IntegrityParameters is present; otherwise it is not present. | +| Integrity2 | The field is mandatory present if ionoRangeErrorCorrelationTime is present; otherwise it is not present. | + +| GNSS-SSR-STECCorrection field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epochTime
This field specifies the epoch time of the STEC correction data. The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| ssrUpdateInterval
This field specifies the SSR Update Interval. The SSR Update Intervals for all SSR parameters start at time 00:00:00 of the GPS time scale. A change of the SSR Update Interval during the transmission of SSR data should ensure consistent data for a target device. See table Value of ssrUpdateInterval to SSR Update Interval relation in IE GNSS-SSR-OrbitCorrections . | +| correctionPointSetID
This field provides the ID of the GNSS-SSR-CorrectionPoints set. The reference point used for the STEC calculations (see NOTE below) is the reference point provided in IE GNSS-SSR-CorrectionPoints with the same correctionPointSetID . | +| iod-ssr
This field specifies the Issue of Data number for the SSR data. A change of iod-ssr is used to indicate a change in the SSR generating configuration. | +| svID
This field specifies the GNSS satellite for which the STEC corrections are provided. | +| stecQualityIndicator
This field specifies SSR STEC quality indicator. The STEC quality indicator is represented by a combination of CLASS and VALUE. The 3 MSB define the CLASS with a range of 0-7 and the 3 LSB define the VALUE with a range of 0-7. See Table 'Relationship between SSR STEC quality indicator and physical quantity' below. | +| stec-C00
This field provides the polynomial coefficient $C_{00}$ used to define the STEC. as defined in [43]. NOTE Scale factor 0.05 TECU; range $\pm 409.55$ TECU. | +| stec-C01
This field provides the polynomial coefficient $C_{01}$ used to define the STEC as defined in [43]. NOTE Scale factor 0.02 TECU/deg; range $\pm 40.94$ TECU/deg. | +| stec-C10
This field provides the polynomial coefficient $C_{10}$ used to define the STEC as defined in [43]. NOTE Scale factor 0.02 TECU/deg; range $\pm 40.94$ TECU/deg. | +| stec-C11
This field provides the polynomial coefficient $C_{11}$ used to define the STEC as defined in [43]. NOTE Scale factor 0.02 TECU/deg 2 ; range $\pm 10.22$ TECU/deg 2 . | +| probOnsetIonoFault
This field specifies the Probability of Onset of Ionosphere Fault per Time Unit which is the probability of occurrence of ionosphere error to exceed the residual error bound for more than the Time to Alert (TTA).
This field specifies the onset probability that the residual range or range rate error exceeds a bound created using the minimum allowed inflation factor $K_{min}$ , and bounding parameters as $mean + K_{min} * stdDev$ where $K_{min} = \text{normInv}(\text{irMaximum} / 2)$ , with irMaximum as provided in IE GNSS-Integrity-ServiceParameters .
The probability is calculated by $P=10^{-0.04n}$ [hour -1 ] where $n$ is the value of probOnsetIonoFault and the range is $10^{-10.2}$ to 1 per hour. | +| meanIonoFaultDuration
This field specifies the Mean Ionosphere Fault Duration which is the mean duration between when an ionosphere integrity violation occurs, and the user is alerted through GNSS-Integrity-ServiceAlert (or the integrity violation is over). Scale factor 1 s; range 1-256 s. | +| ionoRangeErrorCorrelationTime
This field specifies the Ionosphere Range Error Correlation Time which is the upper bound of the correlation time of the ionosphere residual range error.
The time is calculated using:

Range is 1-28,200 s. | +| ionoRangeRateErrorCorrelationTime
This field specifies the Ionosphere Range Rate Error Correlation Time which is the upper bound of the correlation time of the ionosphere residual range rate error.
The time is calculated using:

Range is 1-28,200 s. | +| meanIonosphere
This field specifies the Mean Ionosphere Error bound which is the mean value for an overbounding model that bounds the residual ionosphere error.
The bound is $\text{meanIonosphere} + K * \text{stdDevIonosphere}$ and shall be so that the probability of it to be exceeded shall be lower than IRAllocation for $\text{irMinimum} < \text{IRAllocation} < \text{irMaximum}$ , where $K = \text{normInv}(\text{IRAllocation} / 2)$ and irMinimum , irMaximum as provided in IE GNSS-Integrity-ServiceParameters .
This IRAllocation is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
The mean is calculated using:

Range is 0-17.5 m. | + +| GNSS-SSR-STECCorrection field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| stdDevIonosphere
This field specifies the Standard Deviation Ionosphere Error bound which is the standard deviation for an overbounding model that bounds the residual ionosphere error.
The standard deviation is calculated using:
Range is 0-17.5 m. | +| meanIonosphereRate
This field specifies the Mean Ionosphere Rate Error which is the mean value for an overbounding model that bounds the residual ionosphere rate error.
The bound is $meanIonosphereRate + K * stdDevIonosphereRate$ and shall be so that the probability of it to be exceeded shall be lower than $IR_{allocation}$ for $irMinimum < IR_{allocation} < irMaximum$ , where $K = \text{normInv}(IR_{allocation} / 2)$ and $irMinimum, irMaximum$ as provided in IE GNSS-Integrity-ServiceParameters .
This $IR_{allocation}$ is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
Scale factor 0.00005 m/s; range 0-0.01275 m/s. | +| stdDevIonosphereRate
This field specifies the Standard Deviation Ionosphere Rate Error which is the standard deviation for an overbounding model that bounds the residual ionosphere rate error.
Scale factor 0.00005 m/s; range 0-0.01275 m/s. | + +NOTE: The polynomial coefficients $C_{00}, C_{01}, C_{10}, C_{11}$ are used to define the STEC as follows: + +(1) If only $C_{00}$ is included in *STEC-SatElement*: + +$$\delta I_{ai} = C_{00}.$$ + +(2) If only $C_{00}, C_{01}$ and $C_{10}$ are included in *STEC-SatElement*: + +$$\delta I_{ai} = C_{00} + C_{01}(\phi - \phi_0) + C_{10}(\lambda - \lambda_0).$$ + +(3) If all of $C_{00}, C_{01}, C_{10}$ and $C_{11}$ are included in *STEC-SatElement*: + +$$\delta I_{ai} = C_{00} + C_{01}(\phi - \phi_0) + C_{10}(\lambda - \lambda_0) + C_{11}(\phi - \phi_0)(\lambda - \lambda_0).$$ + +Other combinations of $C_{00}, C_{01}, C_{10}, C_{11}$ than (1)-(3) above are undefined in this version of the specification. + +The equations above depend on the latitude $\phi$ and longitude $\lambda$ of an evaluated point and latitude $\phi_0$ and longitude $\lambda_0$ of the reference point which is defined in IE *GNSS-SSR-CorrectionPoints* (*referencePointLatitude* and *referencePointLongitude*). + +## Relationship between SSR STEC quality indicator and physical quantity + +| CLASS | VALUE | Index | SSR STEC Quality Indicator Q [TECU] | +|-------|-------|-------|-------------------------------------| +| 7 | 7 | 63 | 33.6664 < Q | +| 7 | 6 | 62 | 30.2992 < Q ≤ 33.6664 | +| 7 | 5 | 61 | 26.9319 < Q ≤ 30.2992 | +| 7 | 4 | 60 | 23.5647 < Q ≤ 26.9319 | +| 7 | 3 | 59 | 20.1974 < Q ≤ 23.5647 | +| 7 | 2 | 58 | 16.8301 < Q ≤ 20.1974 | +| 7 | 1 | 57 | 13.4629 < Q ≤ 16.8301 | +| 7 | 0 | 56 | 12.3405 < Q ≤ 13.4629 | +| 6 | 7 | 55 | 11.2180 < Q ≤ 12.3405 | +| 6 | 6 | 54 | 10.0956 < Q ≤ 11.2180 | +| 6 | 5 | 53 | 8.9732 < Q ≤ 10.0956 | +| 6 | 4 | 52 | 7.8508 < Q ≤ 8.9732 | +| 6 | 3 | 51 | 6.7284 < Q ≤ 7.8508 | +| 6 | 2 | 50 | 5.6059 < Q ≤ 6.7284 | +| 6 | 1 | 49 | 4.4835 < Q ≤ 5.6059 | +| 6 | 0 | 48 | 4.1094 < Q ≤ 4.4835 | +| 5 | 7 | 47 | 3.7352 < Q ≤ 4.1094 | +| 5 | 6 | 46 | 3.3611 < Q ≤ 3.7352 | +| 5 | 5 | 45 | 2.9870 < Q ≤ 3.3611 | +| 5 | 4 | 44 | 2.6128 < Q ≤ 2.9870 | +| 5 | 3 | 43 | 2.2387 < Q ≤ 2.6128 | +| 5 | 2 | 42 | 1.8645 < Q ≤ 2.2387 | +| 5 | 1 | 41 | 1.4904 < Q ≤ 1.8645 | +| 5 | 0 | 40 | 1.3657 < Q ≤ 1.4904 | +| 4 | 7 | 39 | 1.2410 < Q ≤ 1.3657 | +| 4 | 6 | 38 | 1.1163 < Q ≤ 1.2410 | +| 4 | 5 | 37 | 0.9915 < Q ≤ 1.1163 | +| 4 | 4 | 36 | 0.8668 < Q ≤ 0.9915 | +| 4 | 3 | 35 | 0.7421 < Q ≤ 0.8668 | +| 4 | 2 | 34 | 0.6174 < Q ≤ 0.7421 | +| 4 | 1 | 33 | 0.4927 < Q ≤ 0.6174 | +| 4 | 0 | 32 | 0.4511 < Q ≤ 0.4927 | +| 3 | 7 | 31 | 0.4096 < Q ≤ 0.4511 | +| 3 | 6 | 30 | 0.3680 < Q ≤ 0.4096 | +| 3 | 5 | 29 | 0.3264 < Q ≤ 0.3680 | +| 3 | 4 | 28 | 0.2848 < Q ≤ 0.3264 | +| 3 | 3 | 27 | 0.2433 < Q ≤ 0.2848 | +| 3 | 2 | 26 | 0.2017 < Q ≤ 0.2433 | +| 3 | 1 | 25 | 0.1601 < Q ≤ 0.2017 | +| 3 | 0 | 24 | 0.1463 < Q ≤ 0.1601 | +| 2 | 7 | 23 | 0.1324 < Q ≤ 0.1463 | +| 2 | 6 | 22 | 0.1186 < Q ≤ 0.1324 | +| 2 | 5 | 21 | 0.1047 < Q ≤ 0.1186 | +| 2 | 4 | 20 | 0.0908 < Q ≤ 0.1047 | +| 2 | 3 | 19 | 0.0770 < Q ≤ 0.0908 | +| 2 | 2 | 18 | 0.0631 < Q ≤ 0.0770 | +| 2 | 1 | 17 | 0.0493 < Q ≤ 0.0631 | +| 2 | 0 | 16 | 0.0447 < Q ≤ 0.0493 | +| 1 | 7 | 15 | 0.0400 < Q ≤ 0.0447 | +| 1 | 6 | 14 | 0.0354 < Q ≤ 0.0400 | +| 1 | 5 | 13 | 0.0308 < Q ≤ 0.0354 | +| 1 | 4 | 12 | 0.0262 < Q ≤ 0.0308 | +| 1 | 3 | 11 | 0.0216 < Q ≤ 0.0262 | +| 1 | 2 | 10 | 0.0169 < Q ≤ 0.0216 | +| 1 | 1 | 9 | 0.0123 < Q ≤ 0.0169 | +| 1 | 0 | 8 | 0.0108 < Q ≤ 0.0123 | +| 0 | 7 | 7 | 0.0092 < Q ≤ 0.0108 | +| 0 | 6 | 6 | 0.0077 < Q ≤ 0.0092 | +| 0 | 5 | 5 | 0.0062 < Q ≤ 0.0077 | +| 0 | 4 | 4 | 0.0046 < Q ≤ 0.0062 | +| 0 | 3 | 3 | 0.0031 < Q ≤ 0.0046 | + +| | | | | +|---|---|---|--------------------------| +| 0 | 2 | 2 | $0.0015 < Q \leq 0.0031$ | +| 0 | 1 | 1 | $Q \leq 0.0015$ | +| 0 | 0 | 0 | undefined/unknown | + +## – GNSS-SSR-GriddedCorrection + +The IE *GNSS-SSR-GriddedCorrection* is used by the location server to provide troposphere delay correction, together with the residual part of the STEC corrections and integrity information. + +The parameters provided in IE *GNSS-SSR-GriddedCorrection* – except for *SSR-GriddedCorrectionIntegrityParameters* and *TropoDelayIntegrityErrorBounds* – are used as specified for Compact SSR Gridded Correction Message (e.g., message type 4073,9) in [43] and apply to all GNSSs. + +``` +-- ASN1START + +GNSS-SSR-GriddedCorrection-r16 ::= SEQUENCE { + epochTime-r16 GNSS-SystemTime, + ssrUpdateInterval-r16 INTEGER (0..15), + iod-ssr-r16 INTEGER (0..15), + troposphericDelayQualityIndicator-r16 BIT STRING (SIZE(6)) OPTIONAL, -- Cond Tropo + correctionPointSetID-r16 INTEGER (0..16383), + gridList-r16 GridList-r16, + ... + [[ + ssr-GriddedCorrectionIntegrityParameters-r17 + SSR-GriddedCorrectionIntegrityParameters-r17 + OPTIONAL -- Need OR + ]] +} + +GridList-r16 ::= SEQUENCE (SIZE(1..64)) OF GridElement-r16 + +GridElement-r16 ::= SEQUENCE { + troposphericDelayCorrection-r16 TroposphericDelayCorrection-r16 OPTIONAL, -- Need ON + stec-ResidualSatList-r16 STEC-ResidualSatList-r16 OPTIONAL, -- Need ON + ... +} + +TroposphericDelayCorrection-r16 ::= SEQUENCE { + tropoHydroStaticVerticalDelay-r16 INTEGER (-256..255), + tropoWetVerticalDelay-r16 INTEGER (-128..127), + ... + [[ + tropoDelayIntegrityErrorBounds-r17 TropoDelayIntegrityErrorBounds-r17 + OPTIONAL -- Cond Integrity1 + ]] +} + +STEC-ResidualSatList-r16 ::= SEQUENCE (SIZE(1..64)) OF STEC-ResidualSatElement-r16 + +STEC-ResidualSatElement-r16 ::= SEQUENCE { + svID-r16 SV-ID, + stecResidualCorrection-r16 CHOICE { + b7-r16 INTEGER (-64..63), + b16-r16 INTEGER (-32768..32767) + }, + ... +} + +SSR-GriddedCorrectionIntegrityParameters-r17 ::= SEQUENCE { + probOnsetTroposphereFault-r17 INTEGER (0..255), + meanTroposphereFaultDuration-r17 INTEGER (1..256), + troposphereRangeErrorCorrelationTime-r17 INTEGER (1..255) OPTIONAL, -- Need OR + troposphereRangeRateErrorCorrelationTime-r17 INTEGER (1..255) OPTIONAL, -- Cond Integrity2 + ... +} + +TropoDelayIntegrityErrorBounds-r17 ::= SEQUENCE { + meanTroposphereVerticalHydroStaticDelay-r17 INTEGER (0..255), + stdDevTroposphereVerticalHydroStaticDelay-r17 INTEGER (0..255), + meanTroposphereVerticalWetDelay-r17 INTEGER (0..255), + stdDevTroposphereVerticalWetDelay-r17 INTEGER (0..255), + meanTroposphereVerticalHydroStaticDelayRate-r17 INTEGER (0..255), + stdDevTroposphereVerticalHydroStaticDelayRate-r17 INTEGER (0..255), +} +``` + +``` +meanTroposphereVerticalWetDelayRate-r17 INTEGER (0..255), + stdDevTroposphereVerticalWetDelayRate-r17 INTEGER (0..255), + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Tropo | The field is mandatory present if troposphericDelayCorrection is included in gridList . Otherwise it is not present. | +| Integrity1 | The field is mandatory present if SSR-GriddedCorrectionIntegrityParameters is present; otherwise it is not present. | +| Integrity2 | The field is mandatory present if troposphereRangeErrorCorrelationTime is present; otherwise it is not present. | + +| GNSS-SSR-GriddedCorrection field descriptions | | +|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epochTime | This field specifies the epoch time of the gridded correction data. The gnss-TimeID in GNSS-SystemTime shall be the same as the GNSS-ID in IE GNSS-GenericAssistDataElement . | +| ssrUpdateInterval | This field specifies the SSR Update Interval. The SSR Update Intervals for all SSR parameters start at time 00:00:00 of the GPS time scale. A change of the SSR Update Interval during the transmission of SSR data should ensure consistent data for a target device. See table Value of ssrUpdateInterval to SSR Update Interval relation in IE GNSS-SSR- OrbitCorrections . | +| iod-ssr | This field specifies the Issue of Data number for the SSR data. A change of iod-ssr is used to indicate a change in the SSR generating configuration. | +| troposphericDelayQualityIndicator | This field specifies the quality indicator of the tropospheric delay. The troposphere quality indicator is represented by a combination of CLASS and VALUE. The 3 MSB define the CLASS with a range of 0-7 and the 3 LSB define the VALUE with a range of 0-7. The troposphere quality indicator is computed by:

See Table 'Relationship between SSR troposphere quality and URA indicator and physical quantity' below. | +| correctionPointSetID | This field provides the ID of the GNSS-SSR-CorrectionPoints set. The GNSS-SSR-GriddedCorrection are valid for the correction points provided in IE GNSS-SSR-CorrectionPoints with the same correctionPointSetID . | +| gridList | This field provides the troposphere delay correction together with the residual part of the STEC corrections for up to 64 correction points defined in IE GNSS-SSR-CorrectionPoints .
If the IE GNSS-SSR-CorrectionPoints , which belongs to the correctionPointSetID , includes the listOfCorrectionPoints , the gridList includes the same number of entries, and listed in the same order, as in the listOfCorrectionPoints .
If the IE GNSS-SSR-CorrectionPoints , which belongs to this correctionPointSetID , includes the arrayOfCorrectionPoints the gridList includes the same number of entries, and listed in the same order, as defined by the enabled bits in the bitmaskOfGrids . | +| tropoHydroStaticVerticalDelay | This field specifies the variation in the hydro static troposphere vertical delay relative to nominal value. The target device should add the constant nominal value of 2.3 m to calculate the tropospheric hydro-static vertical delay.
Scale factor 0.004 m; range $\pm 1.02$ m. | +| tropoWetVerticalDelay | This field specifies the variation in the wet troposphere vertical delay relative to nominal value. The target device should add the constant value of 0.252 m to calculate the tropospheric wet (non hydro-static) vertical delay.
Scale factor 0.004 m; range $\pm 0.508$ m. | +| svID | This field specifies the GNSS satellite for which the STEC residual corrections are provided. | +| stecResidualCorrection | This field specifies the STEC residual correction.
Scale factor 0.04 TECU; range $\pm 2.52$ TECU (b7) or $\pm 1310.68$ TECU (b16). | +| probOnsetTroposphereFault | This field specifies the Probability of Onset of Troposphere Fault per Time Unit which is the probability of occurrence of troposphere error to exceed the residual error bound for more than the Time to Alert (TTA) This field specifies the onset probability that the residual range or range rate error exceeds a bound created using the minimum allowed inflation factor $K_{min}$ , and bounding parameters as $mean + K_{min} * stdDev$ where $K_{min} = \text{normInv}(irMaximum / 2)$ and irMaximum as provided in IE GNSS-Integrity-ServiceParameters .
The probability is calculated by $P=10^{-0.04n}$ [hour -1 ] where n is the value of probOnsetTroposphereFault and the range is $10^{-10.2}$ to 1 per hour. | +| meanTroposphereFaultDuration | This field specifies the Mean Troposphere Fault Duration which is the mean duration between when a troposphere integrity violation occurs, and the user is alerted through GNSS-Integrity-ServiceAlert (or the integrity violation is over).
Scale factor 1 s; range 1-256 s. | +| troposphereRangeErrorCorrelationTime | This field specifies the Troposphere Range Error Correlation Time which is the upper bound of the correlation time of the troposphere residual range error.
The time is calculated using:

Range is 1-28,200 s. | +| troposphereRangeRateErrorCorrelationTime | This field specifies the Troposphere Range Rate Error Correlation Time which is the upper bound of the correlation time of the troposphere residual range rate error.
The time is calculated using:

Range is 1-28,200 s. | + +| GNSS-SSR-GriddedCorrection field descriptions | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--| +| meanTroposphereVerticalHydroStaticDelay
This field specifies the Mean Troposphere Vertical Hydro Static Delay Error bound which is the mean value for an overbounding model that bounds the residual troposphere error in the vertical hydro static delay component. The bound is $meanTroposphereVerticalHydroStaticDelay + K * stdDevTroposphereVerticalHydroStaticDelay$ and shall be so that the probability of it to be exceeded shall be lower than IRallocation for $irMinimum < IRallocation < irMaximum$ , where $K = \text{normInv}(IRallocation / 2)$ and $irMinimum, irMaximum$ as provided in IE GNSS-Integrity-ServiceParameters .
This IRallocation is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
Scale factor 0.005 m; range 0-1.275 m. | | | | +| stdDevTroposphereVerticalHydroStaticDelay
This field specifies the Standard Deviation Troposphere Vertical Hydro Static Delay Error bound which is the standard deviation for an overbounding model that bounds the residual troposphere error in the vertical hydro static delay component.
Scale factor 0.005 m; range 0-1.275 m. | | | | +| meanTroposphereVerticalWetDelay
This field specifies the Mean Troposphere Vertical Wet Static Delay Error bound which is the mean value for an overbounding model that bounds the residual troposphere error in the vertical wet delay component. The bound is $meanTroposphereVerticalWetDelay + K * stdDevTroposphereVerticalWetDelay$ and shall be so that the probability of it to be exceeded shall be lower than IRallocation for $irMinimum < IRallocation < irMaximum$ , where $K = \text{normInv}(IRallocation / 2)$ and $irMinimum, irMaximum$ as provided in IE GNSS-Integrity-ServiceParameters .
This IRallocation is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
Scale factor 0.005 m; range 0-1.275 m. | | | | +| stdDevTroposphereVerticalWetDelay
This field specifies the Standard Deviation Troposphere Vertical Wet Static Delay Error bound which is the standard deviation for an overbounding model that bounds the residual troposphere error in the vertical wet delay component.
Scale factor 0.005 m; range 0-1.275 m. | | | | +| meanTroposphereVerticalHydroStaticDelayRate
This field specifies the Mean Troposphere Vertical Hydro Static Delay Rate Error bound which is the mean value for an overbounding model that bounds the residual troposphere rate error in the vertical hydro static delay component. The bound is $meanTroposphereVerticalHydroStaticDelayRate + K * stdDevTroposphereVerticalHydroStaticDelayRate$ and shall be so that the probability of it to be exceeded shall be lower than IRallocation for $irMinimum < IRallocation < irMaximum$ , where $K = \text{normInv}(IRallocation / 2)$ and $irMinimum, irMaximum$ as provided in IE GNSS-Integrity-ServiceParameters .
This IRallocation is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
Scale factor 0.00005 m/s; range 0-0.01275 m/s. | | | | +| stdDevTroposphereVerticalHydroStaticDelayRate
This field specifies the Standard Deviation Troposphere Vertical Hydro Static Delay Rate Error bound which is the standard deviation for an overbounding model that bounds the residual troposphere rate error in the vertical hydro static delay component.
Scale factor 0.00005 m/s; range 0-0.01275 m/s. | | | | +| meanTroposphereVerticalWetDelayRate
This field specifies the Mean Troposphere Vertical Wet Static Delay Rate Error bound which is the mean value for an overbounding model that bounds the residual troposphere rate error in the vertical wet delay component. The bound is $meanTroposphereVerticalWetDelayRate + K * stdDevTroposphereVerticalWetDelayRate$ and shall be so that the probability of it to be exceeded shall be lower than IRallocation for $irMinimum < IRallocation < irMaximum$ , where $K = \text{normInv}(IRallocation / 2)$ and $irMinimum, irMaximum$ as provided in IE GNSS-Integrity-ServiceParameters .
This IRallocation is a fraction of the Target Integrity Risk that represents the integrity risk budget available.
Scale factor 0.00005 m/s; range 0-0.01275 m/s. | | | | +| stdDevTroposphereVerticalWetDelayRate
This field specifies the Standard Deviation Troposphere Vertical Wet Static Delay Rate Error bound which is the standard deviation for an overbounding model that bounds the residual troposphere rate error in the vertical wet delay component.
Scale factor 0.00005 m/s; range 0-0.01275 m/s. | | | | + +### Relationship between SSR troposphere quality and URA indicator and physical quantity + +| CLASS | VALUE | Index | SSR troposphere quality indicator and SSR URA Q [mm] | +|-------|-------|-------|------------------------------------------------------| +| 7 | 7 | 63 | $5466.50 < Q$ | +| 7 | 6 | 62 | $4919.75 < Q \leq 5466.50$ | +| 7 | 5 | 61 | $4373.75 < Q \leq 4919.75$ | +| 7 | 4 | 60 | $3826.25 < Q \leq 4373.00$ | +| 7 | 3 | 59 | $3279.50 < Q \leq 3826.25$ | + +| | | | | | | +|---|---|----|-------------------|-------|---------| +| 7 | 2 | 58 | 2732.75 | < Q ≤ | 3279.50 | +| 7 | 1 | 57 | 2186.00 | < Q ≤ | 2732.75 | +| 7 | 0 | 56 | 2003.75 | < Q ≤ | 2186.00 | +| 6 | 7 | 55 | 1821.50 | < Q ≤ | 2003.75 | +| 6 | 6 | 54 | 1639.25 | < Q ≤ | 1821.50 | +| 6 | 5 | 53 | 1457.00 | < Q ≤ | 1639.25 | +| 6 | 4 | 52 | 1274.75 | < Q ≤ | 1457.00 | +| 6 | 3 | 51 | 1092.50 | < Q ≤ | 1274.75 | +| 6 | 2 | 50 | 910.25 | < Q ≤ | 1092.50 | +| 6 | 1 | 49 | 728.00 | < Q ≤ | 910.25 | +| 6 | 0 | 48 | 667.25 | < Q ≤ | 728.00 | +| 5 | 7 | 47 | 606.50 | < Q ≤ | 667.25 | +| 5 | 6 | 46 | 545.75 | < Q ≤ | 606.50 | +| 5 | 5 | 45 | 485.00 | < Q ≤ | 545.75 | +| 5 | 4 | 44 | 424.25 | < Q ≤ | 485.00 | +| 5 | 3 | 43 | 363.50 | < Q ≤ | 425.25 | +| 5 | 2 | 42 | 302.75 | < Q ≤ | 363.50 | +| 5 | 1 | 41 | 242.00 | < Q ≤ | 302.75 | +| 5 | 0 | 40 | 221.75 | < Q ≤ | 242.00 | +| 4 | 7 | 39 | 201.50 | < Q ≤ | 221.75 | +| 4 | 6 | 38 | 181.25 | < Q ≤ | 201.50 | +| 4 | 5 | 37 | 161.00 | < Q ≤ | 181.25 | +| 4 | 4 | 36 | 140.75 | < Q ≤ | 161.00 | +| 4 | 3 | 35 | 120.50 | < Q ≤ | 140.75 | +| 4 | 2 | 34 | 100.25 | < Q ≤ | 120.50 | +| 4 | 1 | 33 | 80.00 | < Q ≤ | 100.25 | +| 4 | 0 | 32 | 73.25 | < Q ≤ | 80.00 | +| 3 | 7 | 31 | 66.50 | < Q ≤ | 73.25 | +| 3 | 6 | 30 | 59.75 | < Q ≤ | 66.50 | +| 3 | 5 | 29 | 53.00 | < Q ≤ | 59.75 | +| 3 | 4 | 28 | 46.25 | < Q ≤ | 53.00 | +| 3 | 3 | 27 | 39.50 | < Q ≤ | 46.25 | +| 3 | 2 | 26 | 32.75 | < Q ≤ | 39.50 | +| 3 | 1 | 25 | 26.00 | < Q ≤ | 32.75 | +| 3 | 0 | 24 | 23.75 | < Q ≤ | 26.00 | +| 2 | 7 | 23 | 21.50 | < Q ≤ | 23.75 | +| 2 | 6 | 22 | 19.25 | < Q ≤ | 21.50 | +| 2 | 5 | 21 | 17.00 | < Q ≤ | 19.25 | +| 2 | 4 | 20 | 14.75 | < Q ≤ | 17.00 | +| 2 | 3 | 19 | 12.50 | < Q ≤ | 14.75 | +| 2 | 2 | 18 | 10.25 | < Q ≤ | 12.50 | +| 2 | 1 | 17 | 8.00 | < Q ≤ | 10.25 | +| 2 | 0 | 16 | 7.25 | < Q ≤ | 8.00 | +| 1 | 7 | 15 | 6.50 | < Q ≤ | 7.25 | +| 1 | 6 | 14 | 5.75 | < Q ≤ | 6.50 | +| 1 | 5 | 13 | 5.00 | < Q ≤ | 5.75 | +| 1 | 4 | 12 | 4.25 | < Q ≤ | 5.00 | +| 1 | 3 | 11 | 3.50 | < Q ≤ | 4.25 | +| 1 | 2 | 10 | 2.75 | < Q ≤ | 3.50 | +| 1 | 1 | 9 | 2.00 | < Q ≤ | 2.75 | +| 1 | 0 | 8 | 1.75 | < Q ≤ | 2.00 | +| 0 | 7 | 7 | 1.50 | < Q ≤ | 1.75 | +| 0 | 6 | 6 | 1.25 | < Q ≤ | 1.50 | +| 0 | 5 | 5 | 1.00 | < Q ≤ | 1.25 | +| 0 | 4 | 4 | 0.75 | < Q ≤ | 1.00 | +| 0 | 3 | 3 | 0.50 | < Q ≤ | 0.75 | +| 0 | 2 | 2 | 0.25 | < Q ≤ | 0.50 | +| 0 | 1 | 1 | | Q ≤ | 0.25 | +| 0 | 0 | 0 | undefined/unknown | | | + +– **NavIC-DifferentialCorrections** + +The IE *NavIC-DifferentialCorrections* parameters provide users with sets of correction terms that apply to the clock and ephemeris data transmitted by other satellites in the AutoNav mode as defined in [38] under clause 6.2.6. + +``` +-- ASN1START + +NavIC-DifferentialCorrections-r16 ::= SEQUENCE { + navic-ReftOWC-r16 INTEGER (0..50400), + navic-CorrectionListAutoNav-r16 NavIC-CorrectionListAutoNav-r16, + ... +} + +NavIC-CorrectionListAutoNav-r16 ::= SEQUENCE (SIZE (1..64)) OF NavIC-CorrectionElementAutoNav-r16 + +NavIC-CorrectionElementAutoNav-r16 ::= SEQUENCE { + svID SV-ID, + navic-Tod-r16 INTEGER (0..65535), + navic-iodec-r16 INTEGER (0..255), + navic-UDRAI-r16 INTEGER (-16..15), + navic-UDRrateI-r16 INTEGER (-16..15), + navic-EDC-r16 NavIC-EDC-r16, + navic-CDC-r16 NavIC-CDC-r16, + ... +} + +NavIC-EDC-r16 ::= SEQUENCE { + navic-AlphaEDC-r16 INTEGER (-8192..8191), + navic-BetaEDC-r16 INTEGER (-8192..8191), + navic-GammaEDC-r16 INTEGER (-16384..16383), + navic-AoIcorrection-r16 INTEGER (-2048..2047), + navic-AoRAcorrection-r16 INTEGER (-2048..2047), + navic-SemiMajorcorrection-r16 INTEGER (-2048..2047), + ... +} + +NavIC-CDC-r16 ::= SEQUENCE { + navic-ClockBiasCorrection-r16 INTEGER (-4096..4095), + navic-ClockDriftCorrection-r16 INTEGER (-128..127), + ... +} + +-- ASN1STOP +``` + +| NavIC-DifferentialCorrections field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| navic-Reftowc
The transmission timing of the navigation message provided through the Time of Week Count (TOWC) corresponding to the given set of grid ionospheric parameters. It indicates the number of 12 second counts represented in 17 bits. The TOW count value ranges from 1 to 50400 to cover one entire week. The Time of Week (TOW) in seconds is obtained by multiplying TOWC with 12 as defined in [38], clause 5.7. | +| navic-Tod
This field indicates the NavIC Time of Differential Correction in seconds.
Scale factor 16 seconds | +| navic-Iodec
This field indicates Issue of Data Ephemeris and Clock which provides the user with a convenient means of detecting any change in the ephemeris and clock parameters as described under clause 6.2.1.3 in [38] | +| navic-Udrai
This field indicates the index for the User Differential Range Accuracy (in metres) value which enables users to estimate the accuracy obtained after differential corrections are applied as described under clause 6.2.6 in [38] | +| navic-Udraratei
This field indicates the index for the change rate of User Differential Range Accuracy (metres/second) value which enables users to estimate the accuracy obtained after differential corrections are applied as described under clause 6.2.6 in [38] | +| navic-AlphaEDC
This field indicates the Alpha correction to Ephemeris parameter ( $\Delta\alpha$ ), which is one of the six keplerian elements defining the ephemeris differential corrections (EDC) for NavIC as defined under clause 6.1.3.5 in [38].
Scale factor $2^{-34}$ | +| navic-BetaEDC
This field indicates Beta correction to Ephemeris parameter ( $\Delta\beta$ ), which is one of the six keplerian elements defining the ephemeris differential corrections (EDC) for NavIC as defined under clause 6.1.3.5 in [38].
Scale factor $2^{-34}$ | +| navic-GammaEDC
This field indicates the Gamma correction to Ephemeris parameter ( $\Delta\gamma$ ), which is one of the six keplerian elements defining the ephemeris differential corrections (EDC) for NavIC as defined under clause 6.1.3.5 in [38].
Scale factor $2^{-32}$ semi-circles. | +| navic-AoIcorrection
This field indicates the Angle of inclination correction ( $\Delta i$ ), which is one of the six keplerian elements defining the ephemeris differential corrections (EDC) for NavIC as defined under clause 6.1.3.5 in [38].
Scale factor $2^{-32}$ semi-circles. | +| navic-AoRAcorrection
This field indicates the Angle of right ascension correction ( $\Delta\Omega$ ), which is one of the six keplerian elements defining the ephemeris differential corrections (EDC) for NavIC as defined under clause 6.1.3.5 in [38].
Scale factor $2^{-32}$ semi-circles. | +| navic-SemiMajorcorrection
This field indicates the Semi-major correction ( $\Delta A$ ), which is one of the six keplerian elements defining the ephemeris differential corrections (EDC) for NavIC as defined under clause 6.1.3.5 in [38].
Scale factor $2^{-9}$ metres. | +| navic-ClockBiasCorrection
This field indicates correction to the satellite clock bias coefficient ( $\delta af_0$ ), which is one of the two Satellite clock differential corrections (CDC) containing corrections to the NavIC satellite clock polynomial coefficients as defined under clause 6.1.3.5 in [38].
Scale factor $2^{-35}$ seconds. | +| navic-ClockDriftCorrection
This field indicates correction to the satellite clock drift coefficient ( $\delta af_1$ ), which is one of the two Satellite clock differential corrections (CDC) containing corrections to the NavIC satellite clock polynomial coefficients as defined under clause 6.1.3.5 in [38].
Scale factor $2^{-51}$ sec / sec. | + +## — *NavIC-GridModelParameter* + +``` +-- ASN1START + +NavIC-GridModelParameter-r16 ::= SEQUENCE { + navic-Reftowc-r16 INTEGER (0..50400), + regionMasked-r16 INTEGER (0..1023), + regionIgpList-r16 RegionIgpList-r16, + ... +} + +RegionIgpList-r16 ::= SEQUENCE (SIZE (1..16)) OF RegionIgpElement-r16 + +RegionIgpElement-r16 ::= SEQUENCE { +``` + +``` + +regionID-r16 INTEGER (0..15), +givei1-r16 INTEGER (0..15), +givd1-r16 INTEGER (0..511), +givei2-r16 INTEGER (0..15), +givd2-r16 INTEGER (0..511), +givei3-r16 INTEGER (0..15), +givd3-r16 INTEGER (0..511), +givei4-r16 INTEGER (0..15), +givd4-r16 INTEGER (0..511), +givei5-r16 INTEGER (0..15), +givd5-r16 INTEGER (0..511), +givei6-r16 INTEGER (0..15), +givd6-r16 INTEGER (0..511), +givei7-r16 INTEGER (0..15), +givd7-r16 INTEGER (0..511), +givei8-r16 INTEGER (0..15), +givd8-r16 INTEGER (0..511), +givei9-r16 INTEGER (0..15), +givd9-r16 INTEGER (0..511), +givei10-r16 INTEGER (0..15), +givd10-r16 INTEGER (0..511), +givei11-r16 INTEGER (0..15), +givd11-r16 INTEGER (0..511), +givei12-r16 INTEGER (0..15), +givd12-r16 INTEGER (0..511), +givei13-r16 INTEGER (0..15), +givd13-r16 INTEGER (0..511), +givei14-r16 INTEGER (0..15), +givd14-r16 INTEGER (0..511), +givei15-r16 INTEGER (0..15), +givd15-r16 INTEGER (0..511), +... +} + +-- ASN1STOP + +``` + +#### ***NavIC-GridModelParameter field descriptions*** + +##### ***navic-RefTOWC*** + +The transmission timing of the navigation message provided through the Time of Week Count (TOWC) corresponding to the given set of grid ionospheric parameters. It indicates the number of 12 second counts represented in 17 bits. The TOW count value ranges from 1 to 50400 to cover one entire week. The Time of Week (TOW) in seconds is obtained by multiplying TOWC with 12 as defined in [38], clause 5.7. + +##### ***regionMasked*** + +Total 90 Ionospheric Grid Points(IGP) are defined in [38] clause 6.2.3 table 25. 15 IGP points are grouped into a single region. The region masked indicates the total number of regions for which the corrections are provided. For the current service area of the IRNSS, regions masked are 6. + +##### ***regionIgpList*** + +This list provides the set of IGPs corresponding to each region. Up to 6 instances (0 to 5) are used in this version of the specification. The values 6 to 15 are reserved for future use. + +##### ***regionID*** + +regionID along with index of the IGPS point corresponding gives the location of IGPS point as defined in [38], table 25, clause 6.2.3. + +##### ***givei1, givei2, ... , givei15*** + +This field indicates the Grid Ionospheric Vertical Error Index (GIVEI) which is used to describe the delay correction accuracy at ionospheric grid point indicated by the *igp-ID*, the mapping between GIVEI and GIVE is defined in [38], clause 6.2.2 and table 27. + +##### ***givd1, givd2, ... , givd15*** + +This field indicates the Grid Ionospheric Vertical Delay (GIVD) as defined in [38], clause 5.3.3.8.1, i.e. the vertical delay at the corresponding Ionospheric Grid points (IGPs) indicated by *igp-ID*. The scale factor is 0.125 metre. + +## – ***GNSS-SSR-OrbitCorrectionsSet2*** + +The IE *GNSS-SSR-OrbitCorrectionsSet2* is used by the location server to provide SSR orbit correction parameters in the cases where a reference ephemeris is used other than the default ephemeris type used in *GNSS-SSR-OrbitCorrections*. + +``` + +-- ASN1START + +GNSS-SSR-OrbitCorrectionsSet2-r17 ::= SEQUENCE { + refEph-r17 ENUMERATED { blc, ... }, + gnss-SSR-OrbitCorrections-r17 GNSS-SSR-OrbitCorrections-r15, +} + +``` + +``` + + ... + } + + -- ASN1STOP + +``` + +#### GNSS-SSR-OrbitCorrectionsSet2 field descriptions + +##### **refEph** + +This field specifies the reference ephemeris that the SSR orbit corrections refer to. In the case that *gnss-ID* indicates 'bds' and *refEph* indicates b1c, the SSR orbit corrections are referenced to BDS B1C/B2a in table GNSS to iod Bit String (11) relation in IE *GNSS-NavigationModel* (i.e. the B-CNAV1 broadcast ephemeris [52]). + +##### **gnss-SSR-OrbitCorrections** + +This field specifies the orbit correction parameters which refer to the reference ephemeris indicated by *refEph*. + +### — **GNSS-SSR-ClockCorrectionsSet2** + +The IE *GNSS-SSR-ClockCorrectionsSet2* is used by the location server to provide SSR clock correction parameters in the cases where a reference ephemeris is used other than the default ephemeris type used in *GNSS-SSR-ClockCorrections*. + +``` + +-- ASN1START + +GNSS-SSR-ClockCorrectionsSet2-r17 ::= SEQUENCE { + refEph-r17 ENUMERATED { b1c, ... }, + gnss-SSR-ClockCorrections-r17 GNSS-SSR-ClockCorrections-r15, + ... +} + +-- ASN1STOP + +``` + +#### GNSS-SSR-ClockCorrectionsSet2 field descriptions + +##### **refEph** + +This field specifies the reference ephemeris that the SSR clock corrections refer to. In the case that *gnss-ID* indicates 'bds' and *refEph* indicates b1c, the SSR clock corrections are referenced to BDS B1C/B2a in table GNSS to iod Bit String (11) relation in IE *GNSS-NavigationModel* (i.e. the B-CNAV1 broadcast ephemeris [52]). + +##### **gnss-SSR-ClockCorrections** + +This field specifies the clock correction parameters which refer to the reference ephemeris indicated by *refEph*. + +### — **GNSS-SSR-URA-Set2** + +The IE *GNSS-SSR-URA-Set2* is used by the location server to provide quality information for the provided SSR assistance data in the cases where a reference ephemeris is used other than the default ephemeris type used in *GNSS-SSR-URA*. + +``` + +-- ASN1START + +GNSS-SSR-URA-Set2-r17 ::= SEQUENCE { + refEph-r17 ENUMERATED { b1c, ... }, + gnss-SSR-URA-r17 GNSS-SSR-URA-r16, + ... +} + +-- ASN1STOP + +``` + +#### GNSS-SSR-URA-Set2 field descriptions + +##### **refEph** + +This field specifies the reference ephemeris that quality information for the provided SSR assistance data refers to. In the case that *gnss-ID* indicates 'bds' and *refEph* indicates b1c, the SSR User Range Accuracy corrections are referenced to BDS B1C/B2a in table GNSS to iod Bit String (11) relation in IE *GNSS-NavigationModel* (i.e. the B-CNAV1 broadcast ephemeris [52]). + +##### **gnss-SSR-URA** + +This field specifies the quality information which refers to the reference ephemeris indicated by *refEph*. + +## – **GNSS-LOS-NLOS-GriddedIndications** + +The IE *GNSS-LOS-NLOS-GriddedIndications* is used by the location server to provide GNSS LOS-NLOS indication information. The parameters provided in IE *GNSS-LOS-NLOS-GriddedIndications* apply to all GNSSs. + +``` +-- ASN1START + +GNSS-LOS-NLOS-GriddedIndications-r18 ::= SEQUENCE { + gridPointSetID-r18 INTEGER (0..16383), + expirationTime-r18 UTCTime OPTIONAL, + gridList-r18 GridList-r18, + ... +} + +GridList-r18 ::= SEQUENCE (SIZE(1..1024)) OF GridElement-r18 + +GridElement-r18 ::= SEQUENCE { + gnss-LOS-InfoList-r18 GNSS-LOS-InfoList-r18 OPTIONAL, -- Need ON + ... +} + +GNSS-LOS-InfoList-r18 ::= SEQUENCE (SIZE(1..64)) OF GNSS-LOS-InfoElement-r18 + +GNSS-LOS-InfoElement-r18 ::= SEQUENCE { + svID-r18 SV-ID, + los-r18 ENUMERATED{true, false, uncertain}, + ... +} + +-- ASN1STOP +``` + +| GNSS-LOS-NLOS-GriddedIndications field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gridPointsSetID
This field provides the ID of the LOS-NLOS Grid Point set. It is a regionally unique arbitrary number that is used by the UE to ensure that the GNSS LOS-NLOS indications are being applied to the correct set of points. | +| gridList
This field provides the GNSS LOS-NLOS indications for up to 1024 grid points (up to 256 grid points per altitude layer) defined in the field gnss-los-nlos-GridPoints of IE GNSS-CommonAssistData .
The field gnss-los-nlos-GridPoints of IE GNSS-CommonAssistData , which is associated to this gridPointsSetID , includes the same number of entries as in the gridList , and listed in the same order, as defined by the enabled bits in the bitmaskOfGrids . The upmost grid layer is populated first, followed by the lower layer. | +| svID
This field specifies the GNSS satellite for which the LOS-NLOS indications are provided. | +| los
This field represents a LOS indication per svID per GNSS for a specific grid point, and can take the following values:
  • - true – the satellite vehicle is in line of sight
  • - false – the satellite vehicle is not in line of sight
  • - uncertain – satellite vehicle can either be in line of sight or not
| +| expirationTime
This field indicates when the validity of the provided assistance data fields expires. It is specified as UTC time. | + +## – **GNSS-SSR-SatellitePCVResiduals** + +The IE *GNSS-SSR-SatellitePCVResiduals* is used by the location server to provide the nadir-angle-dependent phase center variations. + +``` +-- ASN1START + +GNSS-SSR-SatellitePCVResiduals-r18 ::= SEQUENCE { + iod-ssr-PCVResiduals-r18 INTEGER (0..64), + ssr-SatellitePCV-List-r18 SSR-SatellitePCV-List-r18, + ... +} + +SSR-SatellitePCV-List-r18 ::= SEQUENCE (SIZE(1..64)) OF SSR-SatellitePCV-Element-r18 + +SSR-SatellitePCV-Element-r18 ::= SEQUENCE { + svID-r18 SV-ID, + ssr-SatellitePCV-FrequencyList-r18 SSR-SatellitePCV-FrequencyList-r18, + ... +} +``` + +``` + +} +SSR-SatellitePCV-FrequencyList-r18 ::= SEQUENCE (SIZE(1..8)) OF + SSR-SatellitePCV-FrequencyElement-r18 + +SSR-SatellitePCV-FrequencyElement-r18 ::= SEQUENCE { + frequencyID-r18 GNSS-FrequencyID-r15, + phaseCenterVariations-r18 SSR-PhaseCenterVariationList-r18, + ... +} + +SSR-PhaseCenterVariationList-r18 ::= SEQUENCE (SIZE(1..32)) OF INTEGER(-1024..1023) + +-- ASN1STOP + +``` + +| GNSS-SSR-SatellitePCVResiduals field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| iod-ssr-PCVResiduals
This field specifies the Issue of Data for the SSR Satellite PCV Residuals that is valid while the GNSS-SSR-IOD-Update is valid. | +| svID
This field specifies the satellite for which the Satellite PCV Residual corrections are provided. | +| frequencyID
This field specifies the satellite carrier frequency to which this correction applies. | +| phaseCenterVariations
This field specifies the residual nadir only variations of the phase center that are not already accounted for within the SSR Phase Bias. The nadir angle is defined to be the angle away from the z-axis. The variations are given in increments of 1 degree steps, the first element is the variation at 1 degree.
In units of 1 mm. | + +### 6.5.2.3 GNSS Assistance Data Request + +#### – *A-GNSS-RequestAssistanceData* + +The IE *A-GNSS-RequestAssistanceData* is used by the target device to request GNSS assistance data from a location server. + +``` + +-- ASN1START + +A-GNSS-RequestAssistanceData ::= SEQUENCE { + gnss-CommonAssistDataReq GNSS-CommonAssistDataReq OPTIONAL, -- Cond CommonADReq + gnss-GenericAssistDataReq GNSS-GenericAssistDataReq OPTIONAL, -- Cond GenADReq + ..., + [[ + gnss-PeriodicAssistDataReq-r15 + GNSS-PeriodicAssistDataReq-r15 OPTIONAL -- Cond PerADReq + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CommonADReq | The field is mandatory present if the target device requests GNSS-CommonAssistData ; otherwise it is not present. | +| GenADReq | This field is mandatory present if the target device requests GNSS-GenericAssistData for one or more specific GNSS; otherwise it is not present. | +| PerADReq | This field is mandatory present if the target device requests periodic GNSS assistance data delivery. This field may only be included if any of the fields are included in IE GNSS-GenericAssistDataReq :
  • - GNSS-RTK-ObservationsReq,
  • - GLO-RTK-BiasInformationReq,
  • - GNSS-RTK-MAC-CorrectionDifferencesReq,
  • - GNSS-RTK-ResidualsReq,
  • - GNSS-RTK-FKP-GradientsReq,
  • - GNSS-SSR-OrbitCorrectionsReq,
  • - GNSS-SSR-ClockCorrectionsReq,
  • - GNSS-SSR-CodeBiasReq,
  • - GNSS-SSR-URA-Req,
  • - GNSS-SSR-PhaseBiasReq,
  • - GNSS-SSR-STECCorrectionReq,
  • - GNSS-SSR-GriddedCorrectionReq,
  • - GNSS-Integrity-ServiceAlerReq,
  • - GNSS-SSR-OrbitCorrectionsSet2Req,
  • - GNSS-SSR-ClockCorrectionsSet2Req,
  • - GNSS-SSR-URA-Set2Req, or
  • - GNSS-SSR-IOD-UpdateReq.
| + +## – *GNSS-CommonAssistDataReq* + +The IE *GNSS-CommonAssistDataReq* is used by the target device to request assistance data that are applicable to any GNSS from a location server. + +``` +-- ASN1START + +GNSS-CommonAssistDataReq ::= SEQUENCE { + gnss-ReferenceTimeReq GNSS-ReferenceTimeReq + OPTIONAL, -- Cond RefTimeReq + gnss-ReferenceLocationReq GNSS-ReferenceLocationReq + OPTIONAL, -- Cond RefLocReq + gnss-IonosphericModelReq GNSS-IonosphericModelReq + OPTIONAL, -- Cond IonoModReq + gnss-EarthOrientationParametersReq GNSS-EarthOrientationParametersReq + OPTIONAL, -- Cond EOPReq + ..., + [[ + gnss-RTK-ReferenceStationInfoReq-r15 + GNSS-RTK-ReferenceStationInfoReq-r15 + OPTIONAL, -- Cond ARPReq + gnss-RTK-AuxiliaryStationDataReq-r15 + GNSS-RTK-AuxiliaryStationDataReq-r15 + OPTIONAL -- Cond AuxARPReq + ]], + [[ + gnss-SSR-CorrectionPointsReq-r16 + GNSS-SSR-CorrectionPointsReq-r16 + OPTIONAL -- Cond PointsReq + ]], + [[ + gnss-Integrity-ServiceParametersReq-r17 + GNSS-Integrity-ServiceParametersReq-r17 + OPTIONAL, -- Cond IntServiceReq + gnss-Integrity-ServiceAlertReq-r17 + GNSS-Integrity-ServiceAlertReq-r17 + OPTIONAL -- Cond IntAlertReq + ]], + [[ + gnss-SSR-IOD-UpdateReq-r18 GNSS-SSR-IOD-UpdateReq-r18 + OPTIONAL -- Cond IODUpdateReq + ]] +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| RefTimeReq | The field is mandatory present if the target device requests GNSS-ReferenceTime ; otherwise it is not present. | +| RefLocReq | This field is mandatory present if the target device requests GNSS-ReferenceLocation ; otherwise it is not present. | +| IonoModReq | This field is mandatory present if the target device requests GNSS-IonosphericModel ; otherwise it is not present. | +| EOPReq | This field is mandatory present if the target device requests GNSS-EarthOrientationParameters ; otherwise it is not present. | +| ARPReq | This field is mandatory present if the target device requests GNSS-RTK-ReferenceStationInfo ; otherwise it is not present. | +| AuxARPReq | This field is mandatory present if the target device requests GNSS-RTK-AuxiliaryStationData ; otherwise it is not present. | +| PointsReq | This field is mandatory present if the target device requests GNSS-SSR-CorrectionPoints ; otherwise it is not present. | +| IntServiceReq | This field is mandatory present if the target device requests GNSS-Integrity-ServiceParameters ; otherwise it is not present. | +| IntAlertReq | This field is mandatory present if the target device requests GNSS-Integrity-ServiceAlert ; otherwise it is not present. | +| IODUpdateReq | This field is mandatory present if the target device requests GNSS-SSR-IOD-Update ; otherwise it is not present. | + +## – *GNSS-GenericAssistDataReq* + +The IE *GNSS-GenericAssistDataReq* is used by the target device to request assistance data from a location server for one or more specific GNSSs. The specific GNSS for which the assistance data are requested is indicated by the IE *GNSS-ID* and (if applicable) by the IE *SBAS-ID*. Assistance for up to 16 GNSSs can be requested. + +``` +-- ASN1START + +GNSS-GenericAssistDataReq ::= SEQUENCE (SIZE (1..16)) OF GNSS-GenericAssistDataReqElement + +GNSS-GenericAssistDataReqElement ::= SEQUENCE { + gnss-ID GNSS-ID, + sbas-ID SBAS-ID OPTIONAL, -- Cond GNSS-ID-SBAS + gnss-TimeModelsReq GNSS-TimeModelListReq OPTIONAL, -- Cond TimeModReq + gnss-DifferentialCorrectionsReq GNSS-DifferentialCorrectionsReq OPTIONAL, -- Cond DGNSS-Req + gnss-NavigationModelReq GNSS-NavigationModelReq OPTIONAL, -- Cond NavModReq + gnss-RealTimeIntegrityReq GNSS-RealTimeIntegrityReq OPTIONAL, -- Cond RTIReq + gnss-DataBitAssistanceReq GNSS-DataBitAssistanceReq OPTIONAL, -- Cond DataBitsReq + gnss-AcquisitionAssistanceReq GNSS-AcquisitionAssistanceReq OPTIONAL, -- Cond AcquAssistReq + gnss-AlmanacReq GNSS-AlmanacReq OPTIONAL, -- Cond AlmanacReq + gnss-UTCModelReq GNSS-UTC-ModelReq OPTIONAL, -- Cond UTCModReq + gnss-AuxiliaryInformationReq GNSS-AuxiliaryInformationReq OPTIONAL, -- Cond AuxInfoReq + ... + [[ + bds-DifferentialCorrectionsReq-r12 + BDS-DifferentialCorrectionsReq-r12 + OPTIONAL, -- Cond DBDS-Req + bds-GridModelReq-r12 BDS-GridModelReq-r12 OPTIONAL -- Cond BDS-GridModReq + ]], + [[ + gnss-RTK-ObservationsReq-r15 + GNSS-RTK-ObservationsReq-r15 OPTIONAL, -- Cond RTK-OSR-Req + glo-RTK-BiasInformationReq-r15 + GLO-RTK-BiasInformationReq-r15 OPTIONAL, -- Cond GLO-CPB-Req + gnss-RTK-MAC-CorrectionDifferencesReq-r15 + GNSS-RTK-MAC-CorrectionDifferencesReq-r15 + OPTIONAL, -- Cond MAC-Req + gnss-RTK-ResidualsReq-r15 GNSS-RTK-ResidualsReq-r15 OPTIONAL, -- Cond Res-Req + gnss-RTK-FKP-GradientsReq-r15 + GNSS-RTK-FKP-GradientsReq-r15 OPTIONAL, -- Cond FKP-Req + gnss-SSR-OrbitCorrectionsReq-r15 + GNSS-SSR-OrbitCorrectionsReq-r15 + OPTIONAL, -- Cond OC-Req + gnss-SSR-ClockCorrectionsReq-r15 + GNSS-SSR-ClockCorrectionsReq-r15 + OPTIONAL, -- Cond CC-Req + gnss-SSR-CodeBiasReq-r15 GNSS-SSR-CodeBiasReq-r15 OPTIONAL -- Cond CB-Req + ]]] +``` + +``` + + ]], + [[ + gnss-SSR-URA-Req-r16 GNSS-SSR-URA-Req-r16 OPTIONAL, -- Cond URA-Req + gnss-SSR-PhaseBiasReq-r16 GNSS-SSR-PhaseBiasReq-r16 OPTIONAL, -- Cond PB-Req + gnss-SSR-STECCorrectionReq-r16 + GNSS-SSR-STECCorrectionReq-r16 OPTIONAL, -- Cond STEC-Req + gnss-SSR-GriddedCorrectionReq-r16 GNSS-SSR-GriddedCorrectionReq-r16 + OPTIONAL, -- Cond Grid-Req + navic-DifferentialCorrectionsReq-r16 + NavIC-DifferentialCorrectionsReq-r16 + OPTIONAL, -- Cond DNavIC-Req + navic-GridModelReq-r16 NavIC-GridModelReq-r16 OPTIONAL -- Cond NavIC-GridModReq + ]], + [[ + gnss-SSR-OrbitCorrectionsSet2Req-r17 + GNSS-SSR-OrbitCorrectionsSet2Req-r17 + OPTIONAL, -- Cond OC2-Req + gnss-SSR-ClockCorrectionsSet2Req-r17 + GNSS-SSR-ClockCorrectionsSet2Req-r17 + OPTIONAL, -- Cond CC2-Req + gnss-SSR-URA-Set2Req-r17 GNSS-SSR-URA-Set2Req-r17 OPTIONAL -- Cond URA2-Req + ]], + [[ + gnss-LOS-NLOS-GriddedIndicationsReq-r18 GNSS-LOS-NLOS-GriddedIndicationsReq-r18 + OPTIONAL, -- Cond LOS-GridReq + gnss-SSR-SatellitePCVResidualsReq-r18 + GNSS-SSR-SatellitePCVResidualsReq-r18 + OPTIONAL -- Cond SatPCV-Req + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GNSS-ID-SBAS | The field is mandatory present if the GNSS-ID = sbas ; otherwise it is not present. | +| TimeModReq | The field is mandatory present if the target device requests GNSS-TimeModelList ; otherwise it is not present. | +| DGNSS-Req | The field is mandatory present if the target device requests GNSS-DifferentialCorrections ; otherwise it is not present. | +| NavModReq | The field is mandatory present if the target device requests GNSS-NavigationModel ; otherwise it is not present. | +| RTIReq | The field is mandatory present if the target device requests GNSS-RealTimeIntegrity ; otherwise it is not present. | +| DataBitsReq | The field is mandatory present if the target device requests GNSS-DataBitAssistance ; otherwise it is not present. | +| AcquAssistReq | The field is mandatory present if the target device requests GNSS-AcquisitionAssistance ; otherwise it is not present. | +| AlmanacReq | The field is mandatory present if the target device requests GNSS-Almanac ; otherwise it is not present. | +| UTCModReq | The field is mandatory present if the target device requests GNSS-UTCModel ; otherwise it is not present. | +| AuxInfoReq | The field is mandatory present if the target device requests GNSS-AuxiliaryInformation ; otherwise it is not present. | +| DBDS-Req | The field is mandatory present if the target device requests BDS-DifferentialCorrections ; otherwise it is not present. This field may only be present if gnss-ID indicates 'bds'. | +| BDS-GridModReq | The field is mandatory present if the target device requests BDS-GridModel ; otherwise it is not present. This field may only be present if gnss-ID indicates 'bds'. | +| RTK-OSR-Req | The field is mandatory present if the target device requests GNSS-RTK-Observations ; otherwise it is not present. | +| GLO-CPB-Req | The field is mandatory present if the target device requests GLO-RTK-BiasInformation ; otherwise it is not present. | +| MAC-Req | The field is mandatory present if the target device requests GNSS-RTK-MAC-CorrectionDifferences ; otherwise it is not present. | +| Res-Req | The field is mandatory present if the target device requests GNSS-RTK-Residuals ; otherwise it is not present. | +| FKP-Req | The field is mandatory present if the target device requests GNSS-RTK-FKP-Gradients ; otherwise it is not present. | +| OC-Req | The field is mandatory present if the target device requests GNSS-SSR-OrbitCorrections ; otherwise it is not present. | +| CC-Req | The field is mandatory present if the target device requests GNSS-SSR-ClockCorrections ; otherwise it is not present. | + +| Conditional presence | Explanation | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CB-Req | The field is mandatory present if the target device requests GNSS-SSR-CodeBias ; otherwise it is not present. | +| URA-Req | The field is mandatory present if the target device requests GNSS-SSR-URA ; otherwise it is not present. | +| PB-Req | The field is mandatory present if the target device requests GNSS-SSR-PhaseBias ; otherwise it is not present. | +| STEC-Req | The field is mandatory present if the target device requests GNSS-SSR-STEC-Correction ; otherwise it is not present. | +| Grid-Req | The field is mandatory present if the target device requests GNSS-SSR-GriddedCorrection ; otherwise it is not present. | +| DNavIC-Req | The field is mandatory present if the target device requests NavIC-DifferentialCorrections ; otherwise it is not present. This field may only be present if the gnss-ID indicates 'navic'. | +| NavIC-GridModReq | The field is mandatory present if the target device requests NavIC-GridModel ; otherwise it is not present. This field may only be present if the gnss-ID indicates 'navic'. | +| OC2-Req | The field is mandatory present if the target device requests GNSS-SSR-OrbitCorrectionsSet2 ; otherwise it is not present. | +| CC2-Req | The field is mandatory present if the target device requests GNSS-SSR-ClockCorrectionsSet2 ; otherwise it is not present. | +| URA2-Req | The field is mandatory present if the target device requests GNSS-SSR-URA-Set2 ; otherwise it is not present. | +| LOS-GridReq | The field is mandatory present if the target device requests GNSS-LOS-NLOS-GriddedIndications ; otherwise it is not present. | +| SatPCV-Req | The field is mandatory present if the target device requests GNSS-SSR-SatellitePCVResiduals ; otherwise it is not present. | + +## GNSS-PeriodicAssistDataReq + +The IE *GNSS-PeriodicAssistDataReq* is used by the target device to request periodic assistance data delivery from a location server. + +``` +-- ASN1START +GNSS-PeriodicAssistDataReq-r15 ::= SEQUENCE { + gnss-RTK-PeriodicObservationsReq-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pOSR + glo-RTK-PeriodicBiasInformationReq-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pCPB + gnss-RTK-MAC-PeriodicCorrectionDifferencesReq-r15 + GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pMAC + gnss-RTK-PeriodicResidualsReq-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pRes + gnss-RTK-FKP-PeriodicGradientsReq-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pFKP + gnss-SSR-PeriodicOrbitCorrectionsReq-r15 + GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pOC + gnss-SSR-PeriodicClockCorrectionsReq-r15 + GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pCC + gnss-SSR-PeriodicCodeBiasReq-r15 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pCB + ..., + [[ + gnss-SSR-PeriodicURA-Req-r16 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pURA + gnss-SSR-PeriodicPhaseBiasReq-r16 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pPB + gnss-SSR-PeriodicSTEC-CorrectionReq-r16 GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pSTEC + gnss-SSR-PeriodicGriddedCorrectionReq-r16 + GNSS-PeriodicControlParam-r15 OPTIONAL -- Cond pGrid + ]], + [[ + gnss-Integrity-PeriodicServiceAlertReq-r17 + GNSS-PeriodicControlParam-r15 OPTIONAL -- Cond pDNU + ]], + [[ + gnss-SSR-PeriodicOrbitCorrectionsSet2Req-r17 + GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pOC2 + gnss-SSR-PeriodicClockCorrectionsSet2Req-r17 + GNSS-PeriodicControlParam-r15 OPTIONAL, -- Cond pCC2 + gnss-SSR-PeriodicURA-Set2Req-r17 + GNSS-PeriodicControlParam-r15 OPTIONAL -- Cond pURA2 + ]], + [[ + gnss-SSR-PeriodicIOD-UpdateReq-r18 + GNSS-PeriodicControlParam-r15 OPTIONAL -- Cond pPCV + ]] +} +``` + +-- ASN1STOP + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| pOSR | The field is mandatory present if the target device requests periodic GNSS-RTK-Observations ; otherwise it is not present. | +| pCPB | The field is mandatory present if the target device requests periodic GLO-RTK-BiasInformation ; otherwise it is not present. | +| pMAC | The field is mandatory present if the target device requests periodic GNSS-RTK-MAC-CorrectionDifferences ; otherwise it is not present. | +| pRes | The field is mandatory present if the target device requests periodic GNSS-RTK-Residuals ; otherwise it is not present. | +| pFKP | The field is mandatory present if the target device requests periodic GNSS-RTK-FKP-Gradients ; otherwise it is not present. | +| pOC | The field is mandatory present if the target device requests periodic GNSS-SSR-OrbitCorrections ; otherwise it is not present. | +| pCC | The field is mandatory present if the target device requests periodic GNSS-SSR-ClockCorrections ; otherwise it is not present. | +| pCB | The field is mandatory present if the target device requests periodic GNSS-SSR-CodeBias ; otherwise it is not present. | +| pURA | The field is mandatory present if the target device requests periodic GNSS-SSR-URA ; otherwise it is not present. | +| pPB | The field is mandatory present if the target device requests periodic GNSS-SSR-PhaseBias ; otherwise it is not present. | +| pSTEC | The field is mandatory present if the target device requests periodic GNSS-SSR-STEC-Correction ; otherwise it is not present. | +| pGrid | The field is mandatory present if the target device requests periodic GNSS-SSR-GriddedCorrection ; otherwise it is not present. | +| pDNU | The field is mandatory present if the target device requests periodic GNSS-Integrity-ServiceAlert ; otherwise it is not present. | +| pOC2 | The field is mandatory present if the target device requests periodic GNSS-SSR-OrbitCorrectionsSet2 ; otherwise it is not present. | +| pCC2 | The field is mandatory present if the target device requests periodic GNSS-SSR-ClockCorrectionsSet2 ; otherwise it is not present. | +| pURA2 | The field is mandatory present if the target device requests periodic GNSS-SSR-URA-Set2 ; otherwise it is not present. | +| pPCV | The field is mandatory present if the target device requests periodic GNSS SSR IOD-Update ; otherwise it is not present. | + +## 6.5.2.4 GNSS Assistance Data Request Elements + +### – *GNSS-ReferenceTimeReq* + +The IE *GNSS-ReferenceTimeReq* is used by the target device to request the *GNSS-ReferenceTime* assistance from the location server. + +``` +-- ASN1START +GNSS-ReferenceTimeReq ::= SEQUENCE { + gnss-TimeReqPrefList SEQUENCE (SIZE (1..8)) OF GNSS-ID, + gps-TOW-assistReq BOOLEAN OPTIONAL, -- Cond gps + notOfLeapSecReq BOOLEAN OPTIONAL, -- Cond glonass + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------| +| gps | The field is mandatory present if gnss-TimeReqPrefList includes a GNSS-ID ='gps'; otherwise it is not present. | +| glonass | The field is mandatory present if gnss-TimeReqPrefList includes a GNSS-ID ='glonass'; otherwise it is not present. | + +| GNSS-ReferenceTimeReq field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-TimeReqPrefList
This field is used by the target device to request the system time for a specific GNSS, specified by GNSS-ID in the order of preference. The first GNSS-ID in the list is the most preferred GNSS for reference time, the second GNSS-ID is the second most preferred, etc. | +| gps-TOW-assistReq
This field is used by the target device to request the gps-TOW-Assist field in GNSS-SystemTime . TRUE means requested. | +| notOfLeapSecReq
This field is used by the target device to request the notificationOfLeapSecond field in GNSS-SystemTime . TRUE means requested. | + +### — GNSS-ReferenceLocationReq + +The IE *GNSS-ReferenceLocationReq* is used by the target device to request the *GNSS-ReferenceLocation* assistance from the location server. + +``` +-- ASN1START +GNSS-ReferenceLocationReq ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### — GNSS-IonosphericModelReq + +The IE *GNSS-IonosphericModelReq* is used by the target device to request the *GNSS-IonosphericModel* assistance from the location server. + +``` +-- ASN1START +GNSS-IonosphericModelReq ::= SEQUENCE { + klobucharModelReq BIT STRING (SIZE(2)) OPTIONAL, -- Cond klobuchar + neQuickModelReq NULL OPTIONAL, -- Cond nequick + ..., + [[ klobucharModel2Req-r16 NULL OPTIONAL -- Cond klobuchar2 + ]] +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| klobuchar | The field is mandatory present if the target device requests klobucharModel ; otherwise it is not present. The BIT STRING defines the dataID requested, defined in IE KlobucharModelParameter . | +| nequick | The field is mandatory present if the target device requests neQuickModel ; otherwise it is not present. | +| klobuchar2 | The field is mandatory present if the target device requests klobucharModel2 ; otherwise it is not present. | + +### — GNSS-EarthOrientationParametersReq + +The IE *GNSS-EarthOrientationParametersReq* is used by the target device to request the *GNSS-EarthOrientationParameters* assistance from the location server. + +``` +-- ASN1START +GNSS-EarthOrientationParametersReq ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +## – **GNSS-RTK-ReferenceStationInfoReq** + +The IE *GNSS-RTK-ReferenceStationInfoReq* is used by the target device to request the *GNSS-RTK-ReferenceStationInfo* assistance from the location server. + +``` +-- ASN1START +GNSS-RTK-ReferenceStationInfoReq-r15 ::= SEQUENCE { + antennaDescriptionReq-r15 BOOLEAN, + antennaHeightReq-r15 BOOLEAN, + physicalReferenceStationReq-r15 BOOLEAN, + stationID-r15 GNSS-ReferenceStationID-r15 OPTIONAL, + ... +} +-- ASN1STOP +``` + +### **GNSS-RTK-ReferenceStationInfoReq field descriptions** + +#### ***antennaDescriptionReq*** + +This field specifies whether or not the location server is requested to include the field *AntennaDescription* in the *GNSS-RTK-ReferenceStationInfo* IE. TRUE means requested. + +#### ***antennaHeightReq*** + +This field specifies whether or not the location server is requested to include the field *antennaHeight* in the *GNSS-RTK-ReferenceStationInfo* IE. TRUE means requested. + +#### ***physicalReferenceStationReq*** + +This field specifies whether or not the location server is requested to include the field *physical-reference-station-info* in the *GNSS-RTK-ReferenceStationInfo* IE. TRUE means requested. + +#### ***stationID*** + +This field specifies the Station ID for which the *GNSS-RTK-ReferenceStationInfo* is requested. + +## – **GNSS-RTK-AuxiliaryStationDataReq** + +The IE *GNSS-RTK-AuxiliaryStationDataReq* is used by the target device to request the *GNSS-RTK-AuxiliaryStationData* assistance from the location server. + +``` +-- ASN1START +GNSS-RTK-AuxiliaryStationDataReq-r15 ::= SEQUENCE { + master-referenceStationID-r15 GNSS-ReferenceStationID-r15 OPTIONAL, + ... +} +-- ASN1STOP +``` + +### **GNSS-RTK-AuxiliaryStationDataReq field descriptions** + +#### ***master-referenceStationID*** + +This field specifies the Master Reference Station ID for which the Auxiliary Stations are requested. + +## – **GNSS-SSR-CorrectionPointsReq** + +The IE *GNSS-SSR-CorrectionPointsReq* is used by the target device to request the *GNSS-SSR-CorrectionPoints* assistance from the location server. + +``` +-- ASN1START +GNSS-SSR-CorrectionPointsReq-r16 ::= SEQUENCE { + correctionPointSetID-Req-r16 INTEGER (0..16383) OPTIONAL, + ... +} +-- ASN1STOP +``` + +| | +|--------------------------------------------------------| +| GNSS-SSR-CorrectionPointsReq field descriptions | +|--------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| correctionPointSetID-Req
This field specifies the ID of the Atmospheric Correction Point set for which the GNSS-SSR-CorrectionPoints are requested. | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +— ***GNSS-Integrity-ServiceParametersReq*** + +The IE *GNSS-Integrity-ServiceParametersReq* is used by the target device to request the *GNSS-Integrity-ServiceParameters* assistance from the location server. + +``` +-- ASN1START +GNSS-Integrity-ServiceParametersReq-r17 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +— ***GNSS-Integrity-ServiceAlertReq*** + +The IE *GNSS-Integrity-ServiceAlertReq* is used by the target device to request the *GNSS-Integrity-ServiceAlert* assistance from the location server. + +``` +-- ASN1START +GNSS-Integrity-ServiceAlertReq-r17 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +— ***GNSS-SSR-IOD-UpdateReq*** + +The IE *GNSS-SSR-IOD-UpdateReq* is used by the target device to request the *GNSS-SSR-IOD-Update* assistance from the location server. + +``` +-- ASN1START +GNSS-SSR-IOD-UpdateReq-r18 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +— ***GNSS-TimeModelListReq*** + +The IE *GNSS-TimeModelListReq* is used by the target device to request the *GNSS-TimeModelElement* assistance from the location server. + +``` +-- ASN1START +GNSS-TimeModelListReq ::= SEQUENCE (SIZE(1..15)) OF GNSS-TimeModelElementReq + +GNSS-TimeModelElementReq ::= SEQUENCE { + gnss-TO-IDsReq INTEGER (1..15), + deltaTreq BOOLEAN, + ... +} +-- ASN1STOP +``` + +| GNSS-TimeModelElementReq field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-TO-IDsReq
This field specifies the requested gnss-TO-ID . The meaning and encoding is the same as the gnss-TO-ID field in the GNSS-TimeModelElement IE. | +| deltaTreq
This field specifies whether or not the location server is requested to include the deltaT field in the GNSS-TimeModelElement IE. TRUE means requested. | + +## — *GNSS-DifferentialCorrectionsReq* + +The IE *GNSS-DifferentialCorrectionsReq* is used by the target device to request the *GNSS-DifferentialCorrections* assistance from the location server. + +``` +-- ASN1START + +GNSS-DifferentialCorrectionsReq ::= SEQUENCE { + dgnss-SignalsReq GNSS-SignalIDs, + dgnss-ValidityTimeReq BOOLEAN, + ... +} + +-- ASN1STOP +``` + +| GNSS-DifferentialCorrectionsReq field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dgnss-SignalsReq
This field specifies the GNSS Signal(s) for which the GNSS-DifferentialCorrections are requested. A one-value at a bit position means DGNSS corrections for the specific signal are requested; a zero-value means not requested. The target device shall set a maximum of three bits to value 'one'. | +| dgnss-ValidityTimeReq
This field specifies whether the udreGrowthRate and udreValidityTime in GNSS-DifferentialCorrections are requested or not. TRUE means requested. | + +## — *GNSS-NavigationModelReq* + +The IE *GNSS-NavigationModelReq* is used by the target device to request the *GNSS-NavigationModel* assistance from the location server. + +``` +-- ASN1START + +GNSS-NavigationModelReq ::= CHOICE { + storedNavList StoredNavListInfo, + reqNavList ReqNavListInfo, + ... +} + +StoredNavListInfo ::= SEQUENCE { + gnss-WeekOrDay INTEGER (0..4095), + gnss-Toe INTEGER (0..255), + t-toeLimit INTEGER (0..15), + satListRelatedDataList SatListRelatedDataList OPTIONAL, + ... +} + +SatListRelatedDataList ::= SEQUENCE (SIZE (1..64)) OF SatListRelatedDataElement + +SatListRelatedDataElement ::= SEQUENCE { + svID SV-ID, + iod BIT STRING (SIZE (11)), + clockModelID INTEGER (1..8) OPTIONAL, + orbitModelID INTEGER (1..8) OPTIONAL, + ... +} + +ReqNavListInfo ::= SEQUENCE { + svReqlist BIT STRING (SIZE (64)), + clockModelID-PrefList SEQUENCE (SIZE (1..8)) OF INTEGER (1..8) OPTIONAL, + orbitModelID-PrefList SEQUENCE (SIZE (1..8)) OF INTEGER (1..8) OPTIONAL, + addNavparamReq BOOLEAN OPTIONAL, -- Cond orbitModelID-2 +} +``` + +``` + + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| orbitModelID-2 | The field is mandatory present if orbitModelID-PrefList is absent or includes a Model-ID = '2'; otherwise it is not present. | + +| GNSS-NavigationModelReq field descriptions | | +|-----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| storedNavList | This list provides information to the location server about which GNSS-NavigationModel data the target device has currently stored for the particular GNSS indicated by GNSS-ID . | +| reqNavList | This list provides information to the location server which GNSS-NavigationModel data are requested by the target device. | +| gnss-WeekOrDay | If GNSS-ID does not indicate 'glonass', this field defines the GNSS Week number of the assistance currently held by the target device.
If GNSS-ID is set to 'glonass', this field defines the calendar number of day within the four-year interval starting from 1 st of January in a leap year, as defined by the parameter $N_T$ in [9] of the assistance currently held by the target device. | +| gnss-Toe | If GNSS-ID does not indicate 'glonass', this field defines the GNSS time of ephemeris in hours of the latest ephemeris set contained by the target device.
If GNSS-ID is set to 'glonass', this field defines the time of ephemeris in units of 15 minutes of the latest ephemeris set contained by the target device (range 0 to 95 representing time values between 0 and 1425 minutes). In this case, values 96 to 255 shall not be used by the sender. | +| t-toeLimit | If GNSS-ID does not indicate 'glonass', this IE defines the ephemeris age tolerance of the target device in units of hours.
If GNSS-ID is set to 'glonass', this IE defines the ephemeris age tolerance of the target device in units of 30 minutes. | +| satListRelatedDataList | This list defines the clock and orbit models currently held by the target device for each SV. This field is not included if the target device does not have any stored clock and orbit models for any SV. | +| svID | This field identifies the particular GNSS satellite. | +| iod | This field identifies the issue of data currently held by the target device. | +| clockModelID, orbitModelID | These fields define the clock and orbit model number currently held by the target device. If these fields are absent, the default interpretation of the table GNSS-ID to clockModelID & orbitModelID relation below applies. | +| svReqList | This field defines the SV for which the navigation model assistance is requested. Each bit position in this BIT STRING represents a SV-ID . Bit 0 represents SV-ID=0 and bit 63 represents SV-ID=63 . A one-value at a bit position means the navigation model data for the corresponding SV-ID is requested, a zero-value means not requested. | +| clockModelIDPrefList, orbitModelID-PrefList | These fields define the Model-IDs of the clock and orbit models that the target device wishes to obtain in the order of preference. The first Model-ID in the list is the most preferred model, the second Model-ID the second most preferred, etc. If these fields are absent, the default interpretation of the table GNSS-ID to clockModelID-PrefList & orbitModelID-PrefList relation below applies. | +| addNavparamReq | This field specifies whether the location server is requested to include the addNAVparam fields in GNSS-NavigationModel IE ( NavModel-NAVKeplerianSet field) or not. TRUE means requested. | + +### GNSS-ID to clockModelID & orbitModelID relation + +| GNSS-ID | clockModelID | orbitModelID | +|----------------|---------------------|---------------------| +| gps | 2 | 2 | +| sbas | 5 | 5 | +| qzss | 2 | 2 | +| galileo | 1 | 1 | +| glonass | 4 | 4 | +| bds | 6 | 6 | +| navic | 8 | 8 | + +### GNSS-ID to clockModelID-PrefList & orbitModelID-PrefList relation + +| GNSS-ID | clockModelID-PrefList | orbitModelID-PrefList | +|----------------|------------------------------|------------------------------| +| gps | Model-2 | Model-2 | +| sbas | Model-5 | Model-5 | +| qzss | Model-2 | Model-2 | +| galileo | Model-1 | Model-1 | +| glonass | Model-4 | Model-4 | +| bds | Model-6 | Model-6 | +| navic | Model-8 | Model-8 | + +### — **GNSS-RealTimeIntegrityReq** + +The IE *GNSS-RealTimeIntegrityReq* is used by the target device to request the *GNSS-RealTimeIntegrity* assistance from the location server. + +``` +-- ASN1START +GNSS-RealTimeIntegrityReq ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### — **GNSS-DataBitAssistanceReq** + +The IE *GNSS-DataBitAssistanceReq* is used by the target device to request the *GNSS-DataBitAssistance* assistance from the location server. + +``` +-- ASN1START +GNSS-DataBitAssistanceReq ::= SEQUENCE { + gnss-TOD-Req INTEGER (0..3599), + gnss-TOD-FracReq INTEGER (0..999) OPTIONAL, + dataBitInterval INTEGER (0..15), + gnss-SignalType GNSS-SignalIDs, + gnss-DataBitsReq GNSS-DataBitsReqSatList OPTIONAL, + ... +} + +GNSS-DataBitsReqSatList ::= SEQUENCE (SIZE(1..64)) OF GNSS-DataBitsReqSatElement + +GNSS-DataBitsReqSatElement ::= SEQUENCE { + svID SV-ID, + ... +} + +-- ASN1STOP +``` + +#### **GNSS-DataBitAssistanceReq field descriptions** + +**gnss-TOD-Req** +This field specifies the reference time for the first data bit requested in GNSS specific system time, modulo 1 hour. Scale factor 1 second. + +| GNSS-DataBitAssistanceReq field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-TOD-FracReq
This field specifies the fractional part of gnss-TOD-Req in 1-milli-second resolution.
Scale factor 1 millisecond. | +| dataBitInterval
This field specifies the time length for which the Data Bit Assistance is requested. The GNSS-DataBitAssistance shall be relative to the time interval ( gnss-TOD-Req , gnss-TOD-Req + dataBitInterval ).
The dataBitInterval r , expressed in seconds, is mapped to a binary number K with the following formula:
$r = 0.1 \times 2^K$ Value K =15 means that the time interval is not specified. | +| gnss-SignalType
This field specifies the GNSS Signal(s) for which the GNSS-DataBitAssistance are requested. A one-value at a bit position means GNSS-DataBitAssistance for the specific signal is requested; a zero-value means not requested. | +| gnss-DataBitsReq
This list contains the SV-IDs for which the GNSS-DataBitAssistance is requested. | + +## – GNSS-AcquisitionAssistanceReq + +The IE *GNSS-AcquisitionAssistanceReq* is used by the target device to request the *GNSS-AcquisitionAssistance* assistance from the location server. + +``` +-- ASN1START + +GNSS-AcquisitionAssistanceReq ::= SEQUENCE { + gnss-SignalID-Req GNSS-SignalID, + ... +} + +-- ASN1STOP +``` + +| GNSS-AcquisitionAssistanceReq field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------| +| gnss-SignalID-Req
This field specifies the GNSS signal type for which GNSSAcquisitionAssistance is requested. | + +## – GNSS-AlmanacReq + +The IE *GNSS-AlmanacReq* is used by the target device to request the *GNSS-Almanac* assistance from the location server. + +``` +-- ASN1START + +GNSS-AlmanacReq ::= SEQUENCE { + modelID INTEGER(1..8) OPTIONAL, + ... +} + +-- ASN1STOP +``` + +| GNSS-AlmanacReq field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| modelID
This field specifies the Almanac Model ID requested. If this field is absent, the default interpretation as in the table GNSS-ID to modelID relation below applies. | + +### GNSS-ID to modelID relation + +| GNSS-ID | modelID | +|----------------|----------------| +| gps | 2 | +| sbas | 6 | +| qzss | 2 | +| galileo | 1 | +| glonass | 5 | +| bds | 7 | +| navic | 8 | + +### — **GNSS-UTC-ModelReq** + +The IE *GNSS-UTC-ModelReq* is used by the target device to request the *GNSS-UTC-Model* assistance from the location server. + +``` +-- ASN1START +GNSS-UTC-ModelReq ::= SEQUENCE { + modelID INTEGER(1..8) OPTIONAL, + ... +} +-- ASN1STOP +``` + +#### **GNSS-UTC-ModelReq field descriptions** + +##### ***modelID*** + +This field specifies the *GNSS-UTCModel* set requested. If this field is absent, the default interpretation as in the table GNSS-ID to modelID relation below applies. + +#### **GNSS-ID to modelID relation** + +| GNSS-ID | modelID | +|-----------------------|-----------------------| +| gps | 1 | +| sbas | 4 | +| qzss | 1 | +| galileo | 1 | +| glonass | 3 | +| bds | 5 | +| navic | 2 | + +### — **GNSS-AuxiliaryInformationReq** + +The IE *GNSS-AuxiliaryInformationReq* is used by the target device to request the *GNSS-AuxiliaryInformation* assistance from the location server. + +``` +-- ASN1START +GNSS-AuxiliaryInformationReq ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### — **BDS-DifferentialCorrectionsReq** + +The IE *BDS-DifferentialCorrectionsReq* is used by the target device to request the *BDS-DifferentialCorrections* assistance from the location server. + +``` +-- ASN1START +BDS-DifferentialCorrectionsReq-r12 ::= SEQUENCE { + dgnss-SignalsReq GNSS-SignalIDs, + ... +} +-- ASN1STOP +``` + +| BDS-DifferentialCorrectionsReq field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dgns-SignalsReq
This field specifies the BDS Signal(s) for which the BDS-DifferentialCorrections are requested. A one-value at a bit position means BDS differential corrections for the specific signal are requested; a zero-value means not requested. The target device shall set a maximum of three bits to value 'one'. This only applies for the B1I/B3I signal. | + +### — ***BDS-GridModelReq*** + +The IE *BDS-GridModelReq* is used by the target device to request the *BDS-GridModel* assistance from the location server. + +``` +-- ASN1START +BDS-GridModelReq-r12 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### — ***GNSS-RTK-ObservationsReq*** + +The IE *GNSS-RTK-ObservationsReq* is used by the target device to request the *GNSS-RTK-Observations* assistance from the location server. + +``` +-- ASN1START +GNSS-RTK-ObservationsReq-r15 ::= SEQUENCE { + gnss-RTK-SignalsReq-r15 GNSS-SignalIDs, + gnss-RTK-Integer-ms-Req-r15 BOOLEAN, + gnss-RTK-PhaseRangeRateReq-r15 BOOLEAN, + gnss-RTK-CNR-Req-r15 BOOLEAN, + stationID-r15 GNSS-ReferenceStationID-r15 OPTIONAL, + ... +} +-- ASN1STOP +``` + +| GNSS-RTK-ObservationsReq field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-RTK-SignalsReq
This field specifies the GNSS Signal(s) for which the GNSS-RTK-Observations are requested. A one-value at a bit position means RTK observations for the specific signal are requested; a zero-value means not requested. | +| gnss-RTK-Integer-ms-Req
This field specifies whether the integer-ms is requested or not. TRUE means requested. | +| gnss-RTK-PhaseRangeRateReq
This field specifies whether the rough-phase-range-rate and fine-PhaseRangeRate are requested or not. TRUE means requested. | +| gnss-RTK-CNR-Req
This field specifies whether the carrier-to-noise-ratio is requested or not. TRUE means requested. | +| stationID
This field specifies the Station ID for which the GNSS-RTK-Observations are requested. | + +### — ***GLO-RTK-BiasInformationReq*** + +The IE *GLO-RTK-BiasInformationReq* is used by the target device to request the *GLO-RTK-BiasInformation* assistance from the location server. + +``` +-- ASN1START +GLO-RTK-BiasInformationReq-r15 ::= SEQUENCE { + stationID-r15 GNSS-ReferenceStationID-r15 OPTIONAL, + ... +} +-- ASN1STOP +``` + +| GLO-RTK-BiasInformationReq field descriptions | +|--------------------------------------------------------------------------------------------------------------------| +| stationID
This field specifies the Station ID for which the GLO-RTK-BiasInformation is requested. | + +## – GNSS-RTK-MAC-CorrectionDifferencesReq + +The IE *GNSS-RTK-MAC-CorrectionDifferencesReq* is used by the target device to request the *GNSS-RTK-MAC-CorrectionDifferences* assistance from the location server. + +``` +-- ASN1START +GNSS-RTK-MAC-CorrectionDifferencesReq-r15 ::= SEQUENCE { + master-ReferenceStationID-r15 GNSS-ReferenceStationID-r15 OPTIONAL, + aux-ReferenceStationList-r15 AUX-ReferenceStationList-r15 OPTIONAL, + linkCombinations-PrefList-r15 GNSS-Link-CombinationsList-r15 OPTIONAL, + ... +} + +AUX-ReferenceStationList-r15 ::= SEQUENCE (SIZE (1..32)) OF AUX-ReferenceStationID-Element-r15 + +AUX-ReferenceStationID-Element-r15 ::= SEQUENCE { + aux-stationID-r15 GNSS-ReferenceStationID-r15, + ... +} + +-- ASN1STOP +``` + +| GNSS-RTK-MAC-CorrectionDifferencesReq field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| master-ReferenceStationID, aux-ReferenceStationList
These fields specify the Master and Auxiliary Reference Station IDs for which the GNSS-RTK-MAC-CorrectionDifferences are requested. | +| linkCombinations-PrefList
This field specifies the dual-frequency combination of L1 and L2 link/frequencies for which the target device wishes to obtain the GNSS-RTK-MAC-CorrectionDifferences in the order of preference. The first GNSS-Link-Combinations in GNSS-Link-CombinationsList is the most preferred combination, the second GNSS-Link-Combinations in GNSS-Link-CombinationsList is the second most preferred, etc. | + +## – GNSS-RTK-ResidualsReq + +The IE *GNSS-RTK-ResidualsReq* is used by the target device to request the *GNSS-RTK-Residuals* assistance from the location server. + +``` +-- ASN1START +GNSS-RTK-ResidualsReq-r15 ::= SEQUENCE { + stationID-r15 GNSS-ReferenceStationID-r15 OPTIONAL, + linkCombinations-PrefList-r15 GNSS-Link-CombinationsList-r15 OPTIONAL, + ... +} + +-- ASN1STOP +``` + +| GNSS-RTK-ResidualsReq field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| stationID
This field specifies the Station ID for which the GNSS-RTK-Residuals are requested. | +| linkCombinations-PrefList
This field specifies the dual-frequency combination of L1 and L2 link/frequencies for which the target device wishes to obtain the GNSS-RTK-Residuals in the order of preference. The first GNSS-Link-Combinations in GNSS-Link-CombinationsList is the most preferred combination, the second GNSS-Link-Combinations in GNSS-Link-CombinationsList is the second most preferred, etc. | + +### – **GNSS-RTK-FKP-GradientsReq** + +The IE *GNSS-RTK-FKP-GradientsReq* is used by the target device to request the *GNSS-RTK-FKP-Gradients* assistance from the location server. + +``` +-- ASN1START +GNSS-RTK-FKP-GradientsReq-r15 ::= SEQUENCE { + stationID-r15 GNSS-ReferenceStationID-r15 OPTIONAL, + linkCombinations-PrefList-r15 GNSS-Link-CombinationsList-r15 OPTIONAL, + ... +} + +-- ASN1STOP +``` + +#### **GNSS-RTK-FKP-GradientsReq field descriptions** + +##### ***stationID*** + +This field specifies the Station ID for which the *GNSS-RTK-FKP-Gradients* are requested. + +##### ***linkCombinations-PrefList*** + +This field specifies the dual-frequency combination of L1 and L2 link/frequencies for which the target device wishes to obtain the *GNSS-RTK-FKP-Gradients* in the order of preference. The first *GNSS-Link-Combinations* in *GNSS-Link-CombinationsList* is the most preferred combination, the second *GNSS-Link-Combinations* in *GNSS-Link-CombinationsList* is the second most preferred, etc. + +### – **GNSS-SSR-OrbitCorrectionsReq** + +The IE *GNSS-SSR-OrbitCorrectionsReq* is used by the target device to request the *GNSS-SSR-OrbitCorrections* assistance from the location server. + +``` +-- ASN1START +GNSS-SSR-OrbitCorrectionsReq-r15 ::= SEQUENCE { + storedNavList-r15 GNSS-NavListInfo-r15 OPTIONAL, + ... + [[ + orbit-IntegrityReq-r17 BIT STRING { correlationTimeReq (0) + } (SIZE(1..8)) OPTIONAL + ]] +} + +-- ASN1STOP +``` + +#### **GNSS-SSR-OrbitCorrectionsReq field descriptions** + +##### ***storedNavList*** + +This list provides information to the location server about which NAV data the target device has currently stored for the particular GNSS indicated by *GNSS-ID*. + +##### ***orbit-IntegrityReq*** + +This field, if present, indicates that the target device requests the IEs *ORBIT-IntegrityParameters* and *SSR-IntegrityOrbitBounds*. + +A one-value at the bit position '0' means that the target device requests the fields *orbitRangeErrorCorrelationTime* and *orbitRangeRateErrorCorrelationTime* in IE *ORBIT-IntegrityParameters*. + +### – **GNSS-SSR-ClockCorrectionsReq** + +The IE *GNSS-SSR-ClockCorrectionsReq* is used by the target device to request the *GNSS-SSR-ClockCorrections* assistance from the location server. + +``` +-- ASN1START +GNSS-SSR-ClockCorrectionsReq-r15 ::= SEQUENCE { + storedNavList-r15 GNSS-NavListInfo-r15 OPTIONAL, + ... + [[ + clock-IntegrityParametersReq-r17 ENUMERATED { true } OPTIONAL, + ssr-IntegrityClockBoundsReq-r17 ENUMERATED { true } OPTIONAL + ]] +} +``` + +``` + +} +-- ASN1STOP + +``` + +| GNSS-SSR-ClockCorrectionsReq field descriptions | | +|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| storedNavList | This list provides information to the location server about which NAV data the target device has currently stored for the particular GNSS indicated by GNSS-ID . | +| clock-IntegrityParametersReq | This field, if present, indicates that the target device requests the CLOCK-IntegrityParameters in IE GNSS-SSR-ClockCorrections . | +| ssr-IntegrityClockBoundsReq | This field, if present, indicates that the target device requests the SSR-IntegrityClockBounds in IE GNSS-SSR-ClockCorrections . | + +### — **GNSS-SSR-CodeBiasReq** + +The IE *GNSS-SSR-CodeBiasReq* is used by the target device to request the *GNSS-SSR-CodeBias* assistance from the location server. + +``` + +-- ASN1START +GNSS-SSR-CodeBiasReq-r15 ::= SEQUENCE { + signal-and-tracking-mode-ID-Map-r15 GNSS-SignalIDs, + storedNavList-r15 GNSS-NavListInfo-r15 OPTIONAL, + ... + [[ + ssr-IntegrityCodeBiasBoundsReq-r17 ENUMERATED { requested } OPTIONAL + ]] +} +-- ASN1STOP + +``` + +| GNSS-SSR-CodeBiasReq field descriptions | | +|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| signal-and-tracking-mode-ID-Map | This field specifies the GNSS signal(s) for which the GNSS-SSR-CodeBias is requested. | +| storedNavList | This list provides information to the location server about which NAV data the target device has currently stored for the particular GNSS indicated by GNSS-ID . | +| ssr-IntegrityCodeBiasBoundsReq | This field, if present, indicates that the SSR-IntegrityCodeBiasBounds are requested. | + +### — **GNSS-SSR-URA-Req** + +The IE *GNSS-SSR-URA-Req* is used by the target device to request the *GNSS-SSR-URA* assistance from the location server. + +``` + +-- ASN1START +GNSS-SSR-URA-Req-r16 ::= SEQUENCE { + ... +} +-- ASN1STOP + +``` + +### — **GNSS-SSR-PhaseBiasReq** + +The IE *GNSS-SSR-PhaseBiasReq* is used by the target device to request the *GNSS-SSR-PhaseBias* assistance from the location server. + +``` + +-- ASN1START +GNSS-SSR-PhaseBiasReq-r16 ::= SEQUENCE { + signal-and-tracking-mode-ID-Map-r16 GNSS-SignalIDs, + +``` + +``` + + storedNavList-r16 GNSS-NavListInfo-r15 OPTIONAL, + ... + [[ + ssr-IntegrityPhaseBiasBoundsReq-r17 ENUMERATED { requested } OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +#### GNSS-SSR-PhaseBiasReq field descriptions + +##### **signal-and-tracking-mode-ID-Map** + +This field specifies the GNSS signal(s) for which the *GNSS-SSR-PhaseBias* is requested. + +##### **storedNavList** + +This list provides information to the location server about which NAV data the target device has currently stored for the particular GNSS indicated by *GNSS-ID*. + +##### **ssr-IntegrityPhaseBiasBoundsReq** + +This field, if present, indicates that the *SSR-IntegrityPhaseBiasBounds* are requested. + +### — **GNSS-SSR-STECCorrectionReq** + +The IE *GNSS-SSR-STECCorrectionReq* is used by the target device to request the *GNSS-SSR-STECCorrection* assistance from the location server. + +``` + +-- ASN1START + +GNSS-SSR-STECCorrectionReq-r16 ::= SEQUENCE { + ... + [[ + stec-IntegrityReq-r17 BIT STRING { correlationTimeReq (0) + } (SIZE(1..8)) OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +#### GNSS-SSR-STECCorrectionReq field descriptions + +##### **stec-IntegrityReq** + +This field, if present, indicates that the target device requests the IEs *STECCorrectionIntegrityParameters* and *STECCorrectionErrorBounds*. + +A one-value at the bit position '0' means that the target device requests the fields *ionoRangeErrorCorrelationTime* and *ionoRangeRateErrorCorrelationTime* in IE *STECCorrectionIntegrityParameters*. + +### — **GNSS-SSR-GriddedCorrectionReq** + +The IE *GNSS-SSR-GriddedCorrectionReq* is used by the target device to request the *GNSS-SSR-GriddedCorrection* assistance from the location server. + +``` + +-- ASN1START + +GNSS-SSR-GriddedCorrectionReq-r16 ::= SEQUENCE { + ... + [[ + griddedCorrectionIntegrityReq-r17 ENUMERATED { requested } OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +#### GNSS-SSR-GriddedCorrectionReq field descriptions + +##### **griddedCorrectionIntegrityReq** + +This field, if present, indicates that the target device requests the IEs *SSR-GriddedCorrectionIntegrityParameters* and *TropoDelayIntegrityErrorBounds*. + +### – *NavIC-DifferentialCorrectionsReq* + +The IE *NavIC-DifferentialCorrectionsReq* is used by the target device to request the *NavIC-DifferentialCorrections* assistance from the location server. + +``` +-- ASN1START +NavIC-DifferentialCorrectionsReq-r16 ::= SEQUENCE { + dgnss-SignalsReq-r16 GNSS-SignalIDs, + ... +} +-- ASN1STOP +``` + +#### *NavIC-DifferentialCorrectionsReq* field descriptions + +##### ***dgnss-SignalsReq*** + +This field specifies the NavIC Signal(s) for which the *NavIC-DifferentialCorrections* are requested. A one-value at a bit position means the NavIC differential corrections for the specific signal are requested; a zero-value means not requested. The target device shall set a maximum of three bits to value 'one'. + +### – *NavIC-GridModelReq* + +The IE *NavIC-GridModelReq* is used by the target device to request the *NavIC-GridModel* assistance from the location server. + +``` +-- ASN1START +NavIC-GridModelReq-r16 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### – *GNSS-SSR-OrbitCorrectionsSet2Req* + +The IE *GNSS-SSR-OrbitCorrectionsSet2Req* is used by the target device to request the *GNSS-SSR-OrbitCorrectionsSet2* assistance from the location server. + +``` +-- ASN1START +GNSS-SSR-OrbitCorrectionsSet2Req-r17 ::= SEQUENCE { + refEphReq-r17 ENUMERATED { b1c, ... }, + gnss-SSR-OrbitCorrectionsSet2Req-r17 + GNSS-SSR-OrbitCorrectionsReq-r15 OPTIONAL, -- Cond OC2-Req + ... +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------| +| OC2-Req | The field is mandatory present if the target device requests GNSS-SSR-OrbitCorrectionsSet2 ; otherwise it is not present. | + +#### *GNSS-SSR-OrbitCorrectionsSet2Req* field descriptions + +##### ***refEphReq*** + +This field, if present, indicates that the reference broadcast ephemeris that target device requests the *GNSS-SSR-OrbitCorrectionsSet2* for. + +### – *GNSS-SSR-ClockCorrectionsSet2Req* + +The IE *GNSS-SSR-ClockCorrectionsSet2Req* is used by the target device to request the *GNSS-SSR-ClockCorrectionsSet2* assistance from the location server. + +``` + +-- ASN1START + +GNSS-SSR-ClockCorrectionsSet2Req-r17 ::= SEQUENCE { + refEphReq-r17 ENUMERATED { b1c, ... }, + gnss-SSR-ClockCorrectionsSet2Req-r17 + GNSS-SSR-ClockCorrectionsReq-r15 OPTIONAL, -- Cond CC2-Req + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------| +| CC2-Req | The field is mandatory present if the target device requests GNSS-SSR-ClockCorrectionsSet2 ; otherwise it is not present. | + +| GNSS-SSR-ClockCorrectionsSet2Req field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| refEphReq
This field, if present, indicates that the reference broadcast ephemeris that target device requests the GNSS-SSR-ClockCorrectionsSet2 for. | + +## – GNSS-SSR-URA-Set2Req + +The IE *GNSS-SSR-URA-Set2Req* is used by the target device to request the *GNSS-SSR-URA-Set2* assistance from the location server. + +``` + +-- ASN1START + +GNSS-SSR-URA-Set2Req-r17 ::= SEQUENCE { + refEphReq-r17 ENUMERATED { b1c, ... }, + ... +} + +-- ASN1STOP + +``` + +| GNSS-SSR-URA-Set2Req field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| refEphReq
This field, if present, indicates that the reference broadcast ephemeris that target device requests the GNSS-SSR-URA-Set2 for. | + +## – GNSS-LOS-NLOS-GriddedIndicationsReq + +The IE *GNSS-LOS-NLOS-GriddedIndicationsReq* is used by the target device to request the *GNSS-LOS-NLOS-GriddedIndications* assistance from the location server. + +``` + +-- ASN1START + +GNSS-LOS-NLOS-GriddedIndicationsReq-r18 ::= SEQUENCE { + gridPointsSetID-Req-r18 INTEGER (0..16383) OPTIONAL, + relativeLocationInfo-r18 CHOICE { + inside-r18 ENUMERATED {upper-left, upper-right, lower-left, lower-right, ...}, + outside-r18 ENUMERATED {north, west, south, east, above, below, ...} + } + OPTIONAL, -- Cond Relative + verticalGridType-r18 ENUMERATED {ground-level, threeD}, + referenceAltitudeFine-r18 INTEGER (0..9) OPTIONAL, + referenceAltitudeCoarse-r18 INTEGER (-50..900) OPTIONAL, + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Relative | This field is mandatory present if a relative position is included in the request. It is absent if the field gridPointsSetID-Req is absent. | + +### – **GNSS-SSR-SatellitePCVResidualsReq** + +The IE *GNSS-SSR-SatellitePCVResidualsReq* is used by the target device to request the *GNSS-SSR-SatellitePCVResiduals* assistance from the location server. + +``` +-- ASN1START +GNSS-SSR-SatellitePCVResidualsReq-r18 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +## 6.5.2.5 GNSS Location Information + +### – **A-GNSS-ProvideLocationInformation** + +The IE *A-GNSS-ProvideLocationInformation* is used by the target device to provide location measurements (e.g., pseudo-ranges, location estimate, velocity) to the location server, together with time information. It may also be used to provide GNSS positioning specific error reason. + +``` +-- ASN1START +A-GNSS-ProvideLocationInformation ::= SEQUENCE { + gnss-SignalMeasurementInformation GNSS-SignalMeasurementInformation OPTIONAL, + gnss-LocationInformation GNSS-LocationInformation OPTIONAL, + gnss-Error A-GNSS-Error OPTIONAL, + ... +} +-- ASN1STOP +``` + +## 6.5.2.6 GNSS Location Information Elements + +### – **GNSS-SignalMeasurementInformation** + +The IE *GNSS-SignalMeasurementInformation* is used by the target device to provide GNSS signal measurement information to the location server and GNSS-network time association if requested by the location server. This information includes the measurements of code phase, Doppler, C/N0 and optionally accumulated carrier phase, also called accumulated delta range (ADR), which enable the UE-assisted GNSS method where position is computed in the location server. Figure 6.5.2.6-1 illustrates the relation between some of the fields. + +``` +-- ASN1START +GNSS-SignalMeasurementInformation ::= SEQUENCE { + measurementReferenceTime MeasurementReferenceTime, + gnss-MeasurementList GNSS-MeasurementList, + ... +} +-- ASN1STOP +``` + +| GNSS-SignalMeasurementInformation field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| measurementReferenceTime
This field specifies the GNSS system time for which the information provided in gnss-MeasurementList is valid. It may also include network time, if requested by the location server and supported by the target device. | +| gnss-MeasurementList
This field provides GNSS signal measurement information for up to 16 GNSSs. | + +## – *MeasurementReferenceTime* + +The IE *MeasurementReferenceTime* is used to specify the time when the measurements provided in *A-GNSS-ProvideLocationInformation* are valid. It may also include GNSS-network time association, in which case reported measurements shall be valid for the cellular frame boundary defined in the network time association. + +``` +-- ASN1START +MeasurementReferenceTime ::= SEQUENCE { + gnss-TOD-msec INTEGER (0..3599999), + gnss-TOD-frac INTEGER (0..3999) OPTIONAL, + gnss-TOD-unc INTEGER (0..127) OPTIONAL, + gnss-TimeID GNSS-ID, + networkTime CHOICE { + eUTRA SEQUENCE { + physCellId INTEGER (0..503), + cellGlobalId CellGlobalIdEUTRA-AndUTRA OPTIONAL, + systemFrameNumber BIT STRING (SIZE (10)), + ... + }, + uTRA SEQUENCE { + mode CHOICE { + fdd SEQUENCE { + primary-CPICH-Info INTEGER (0..511), + ... + }, + tdd SEQUENCE { + cellParameters INTEGER (0..127), + ... + } + }, + cellGlobalId CellGlobalIdEUTRA-AndUTRA OPTIONAL, + referenceSystemFrameNumber + INTEGER (0..4095), + ... + }, + gSM SEQUENCE { + bcchCarrier INTEGER (0..1023), + bsic INTEGER (0..63), + cellGlobalId CellGlobalIdGERAN OPTIONAL, + referenceFrame SEQUENCE { + referenceFN INTEGER (0..65535), + referenceFNMSB INTEGER (0..63) OPTIONAL, + ... + }, + deltaGNSS-TOD INTEGER (0 .. 127) OPTIONAL, + ... + }, + ..., + nbIoT-r14 SEQUENCE { + nbPhysCellId-r14 INTEGER (0..503), + nbCellGlobalId-r14 ECGI OPTIONAL, + sfn-r14 BIT STRING (SIZE (10)), + hyperSFN-r14 BIT STRING (SIZE (10)) OPTIONAL, + ... + }, + nr-r15 SEQUENCE { + nrPhysCellId-r15 INTEGER (0..1007), + nrCellGlobalID-r15 NCGI-r15 OPTIONAL, + nr-sfn-r15 BIT STRING (SIZE (10)), + ... + } + } OPTIONAL, + ... +} +-- ASN1STOP +``` + +| MeasurementReferenceTime field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

gnss-TOD-msec
This field specifies the GNSS TOD for which the measurements and/or location estimate are valid. The 22 bits of GNSS TOD are the least significant bits. The most significant bits are derived by the location server to unambiguously derive the GNSS TOD.
The value for GNSS TOD is derived from the GNSS specific system time indicated in gnss-TimeID rounded down to the nearest millisecond unit.
Scale factor 1 millisecond.

| +|

gnss-TOD-frac
This field specifies the fractional part of the GNSS TOD in 250 ns resolution. The total GNSS TOD is given by gnss-TOD-msec + gnss-TOD-frac.
Scale factor 250 nanoseconds.

| +|

gnss-TOD-unc
This field provides the accuracy of the relation GNSS-network time when GNSS-network time association is provided. When GNSS-network time association is not provided, this element can be included to provide the accuracy of the reported gnss-TOD-msec.
If GNSS TOD is the given GNSS time, then the true GNSS time, corresponding to the provided network time if applicable, as observed at the target device location, lies in the interval [GNSS TOD – gnss-TOD-unc, GNSS TOD + gnss-TOD-unc].
The uncertainty r, expressed in microseconds, is mapped to a number K, with the following formula:
r = C * ((1+x)^K - 1) with C = 0.5 and x = 0.14. To encode any higher value of uncertainty than that corresponding in the above formula to K=127, the same value, K=127, shall also be used. The uncertainty is then coded on 7 bits, as the binary encoding of K. Examples of gnss-TOD-unc value are as in the table Value of K to Value of uncertainty relation below.
This field shall be included if the target device provides GNSS-network time relationship.

| +|

gnss-TimeID
This field specifies the GNSS system time for which the gnss-TOD-msec (and gnss-TOD-frac if applicable) is provided.

| +|

networkTime
These fields specify the network time event which the GNSS TOD time stamps.
This field shall be included if the target device provides GNSS-network time relationship.

| +|

physCellId
This field identifies the reference cell (E-UTRA), as defined in TS 36.331 [12], that is used for the GNSS-network time relation.

| +|

cellGlobalId
This field specifies the globally unique cell identifier (Evolved Cell Global Identifier (ECGI) in E-UTRA, global UTRAN Cell Identifier in UTRA, or Cell Global Identification (CGI) in GERAN) of the reference cell, as defined in TS 36.331 [12] for E-UTRA and in TS 25.331 [13] for UTRA, for which the GNSS network time relation is provided.

| +|

systemFrameNumber
This field specifies the system frame number in E-UTRA which the GNSS time time stamps, as defined in TS 36.331 [12].

| +|

mode
This field identifies the reference cell for the GNSS-network time relation, as defined in TS 25.331 [13].

| +|

referenceSystemFrameNumber
This field specifies the system frame number in UTRA, as defined in TS 25.331 [13], which is used for time stamping.

| +|

bcchCarrier, bsic
This field identifies the reference cell for the GNSS-network time relation in GERAN, as defined in TS 44.031 [14].

| +|

referenceFN, referenceFNMSB
These fields specify the frame number in GERAN which the GNSS time time stamps, as defined in TS 44.031 [14]. The time of the reference frame boundary is as observed by the target device, i.e. without Timing Advance compensation. The referenceFNMSB field indicates the most significant bits of the frame number of the reference BTS corresponding to the GNSS-MeasurementList. Starting from the complete GSM frame number denoted FN, the target device calculates Reference FN MSB as
\text{Reference FN MSB} = \text{floor}(\text{FN}/42432) The complete GSM frame number FN can then be reconstructed in the location server by combining the fields referenceFN with referenceFNMSB in the following way
\text{FN} = \text{referenceFNMSB} * 42432 + \text{referenceFN}

| +|

deltaGNSS-TOD
This field specifies the difference in milliseconds between gnss-TOD-msec reported and the milli-second part of the SV time tsv_1 of the first SV in the list reported from the target device, as defined in TS 44.031 [14]. The deltaGNSS-TOD is defined as
\text{deltaGNSS-TOD} = \text{gnss-TOD-msec} - \text{fix}(\text{tsv\_1}) where fix() denotes rounding to the nearest integer towards zero.

| +|

nbPhysCellId
This field identifies the reference cell, as defined in TS 36.331 [12] that is used for the GNSS-network time relation.

| +|

nbCellGlobalId
This field specifies the global cell identifier of the NB-IoT reference cell, as defined in TS 36.331 [12], for which the GNSS network time relation is provided.

| + +| MeasurementReferenceTime field descriptions | | +|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sfn | This field specifies the system frame number in NB-IoT which the GNSS time time stamps, as defined in TS 36.331 [12]. | +| hyperSFN | This field specifies the hyper-SFN in NB-IoT which the GNSS time time stamps, as defined in TS 36.331 [12]. | +| nrPhysCellId | This field identifies the reference cell (NR), as defined in TS 38.331 [35], that is used for the GNSS-network time relation. | +| nrCellGlobalID | This field specifies the NR Cell Global Identifier (NCGI) of the reference cell, as defined in TS 38.331 [35], for which the GNSS network time relation is provided. | +| nr-sfn | This field specifies the system frame number in NR which the GNSS time time stamps, as defined in TS 38.331 [35]. | + +### Value of K to Value of uncertainty relation + +| Value of K | Value of uncertainty | +|-------------------|-----------------------------| +| 0 | 0 microseconds | +| 1 | 0.07 microseconds | +| 2 | 0.1498 microseconds | +| - | - | +| 50 | 349.62 microseconds | +| - | - | +| 127 | $\geq 8430000$ microseconds | + +## GNSS-MeasurementList + +The IE *GNSS-MeasurementList* is used by the target device to provide measurements of code phase, Doppler, C/N0 and optionally accumulated carrier phase, also called accumulated deltarange (ADR). + +``` +-- ASN1START + +GNSS-MeasurementList ::= SEQUENCE (SIZE(1..16)) OF GNSS-MeasurementForOneGNSS + +GNSS-MeasurementForOneGNSS ::= SEQUENCE { + gnss-ID GNSS-ID, + gnss-SgnMeasList GNSS-SgnMeasList, + ... +} + +GNSS-SgnMeasList ::= SEQUENCE (SIZE(1..8)) OF GNSS-SgnMeasElement + +GNSS-SgnMeasElement ::= SEQUENCE { + gnss-SignalID GNSS-SignalID, + gnss-CodePhaseAmbiguity INTEGER (0..127) OPTIONAL, + gnss-SatMeasList GNSS-SatMeasList, + ... +} + +GNSS-SatMeasList ::= SEQUENCE (SIZE(1..64)) OF GNSS-SatMeasElement + +GNSS-SatMeasElement ::= SEQUENCE { + svID SV-ID, + cNo INTEGER (0..63), + mpathDet ENUMERATED {notMeasured (0), low (1), medium (2), high (3), ...}, + carrierQualityInd INTEGER (0..3) OPTIONAL, + codePhase INTEGER (0..2097151), + integerCodePhase INTEGER (0..127) OPTIONAL, + codePhaseRMSError INTEGER (0..63), + doppler INTEGER (-32768..32767) OPTIONAL, + adr INTEGER (0..33554431) OPTIONAL, + ..., + [[ + adrMSB-r15 INTEGER (0..15) OPTIONAL, + adrSign-r15 ENUMERATED {positive, negative} OPTIONAL, + adrRMSError-r15 INTEGER (0..127) OPTIONAL, + delta-codePhase-r15 INTEGER (0..7) OPTIONAL + ]] +} +``` + +} + +-- ASN1STOP + +| GNSS-MeasurementList field descriptions | | +|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-ID | This field identifies the GNSS constellation on which the GNSS signal measurements were measured. Measurement information for up to 16 GNSSs can be included. | +| gnss-SgnMeasList | This list provides GNSS signal measurement information for up to 8 GNSS signal types per GNSS. | +| gnss-SignalID | This field identifies the signal on which GNSS signal measurement parameters were measured. | +| gnss-CodePhaseAmbiguity | This field provides the ambiguity of the code phase measurement. It is given in units of milli-seconds in the range between 0 and 127 milli-seconds.
The total code phase for a satellite k (Satk) is given modulo this gnss-CodePhaseAmbiguity and is reconstructed with:
$\text{Code\_Phase\_Tot}(\text{Satk}) = \text{codePhase}(\text{Satk}) + \text{integerCodePhase}(\text{Satk}) + n * \text{gnss-CodePhaseAmbiguity}$ , $n = 0, 1, 2, \dots$
If there is no code phase ambiguity, the gnss-CodePhaseAmbiguity shall be set to 0.
The field is optional. If gnss-CodePhaseAmbiguity is absent, the default value is 1 milli-second. | +| gnss-SatMeasList | This list provides GNSS signal measurement information for up to 64 GNSS satellites. | +| svID | This field identifies the satellite on which the GNSS signal measurements were measured. | +| cNo | This field provides an estimate of the carrier-to-noise ratio of the received signal from the particular satellite. The target device shall set this field to the value of the satellite $C/N_0$ , as referenced to the antenna connector, in units of 1 dB-Hz, in the range from 0 to 63 dB-Hz.
Scale factor 1 dB-Hz. | +| mpathDet | This field contains the multipath indicator value, defined in the table Value of mpathDet to Multipath Indication relation below. | +| carrierQualityInd | If the fields adrMSB , adrSign , adrRMSerror , and delta-codePhase are not present:
This field indicates the quality of a carrier phase measurement. The LSB indicates the data polarity, that is, if the data from a specific satellite is received inverted, this is indicated by setting the LSB value to '1'. In the case the data is not inverted, the LSB is set to '0'. The MSB indicates if accumulation of the carrier phase has been continuous, that is, without cycle slips since the previous measurement report. If the carrier phase accumulation has been continuous, the MSB value is set to '1X'. Otherwise, the MSB is set to '0X'.
This field is optional but shall be included if the adr field is included. See table Bit to Polarity Indication relation below.
If any of the fields adrMSB , adrSign , adrRMSerror , or delta-codePhase are present:
This field indicates the quality of a carrier phase measurement. The LSB indicates the half-cycle ambiguity, that is, if there are no half-cycle ambiguities present in the ADR measurement report the LSB is set to '0'. In the case there are half-cycle ambiguities present in the ADR measurement report the LSB is set to '1'. When reporting ADR with unresolved polarity encoding the target device shall set this bit to 1.
The MSB indicates if accumulation of the carrier phase has been continuous, that is, without cycle slips since the previous measurement report. If the carrier phase accumulation has been continuous (no cycle slips), the MSB value is set to '1X'. Otherwise, the MSB is set to '0X'. If polarity resolution forced the ADR measurement to be corrected by half-a-cycle, then the MSB must be set to '0', indicating that despite continuous tracking the reported ADR experienced non-continuity. See table Bit to Ambiguity Indication relation below.
The target device shall include this field if the adr field is included. | +| codePhase | This field contains the whole and fractional value of the code-phase measurement made by the target device for the particular satellite signal at the time of measurement in the units of ms. GNSS specific code phase measurements (e.g. chips) are converted into unit of ms by dividing the measurements by the nominal values of the measured signal chipping rate.
Scale factor $2^{-21}$ milli-seconds, in the range from 0 to $(1-2^{-21})$ milli-seconds. | +| integerCodePhase | This field indicates the integer milli-second part of the code phase that is expressed modulo the gnss-CodePhaseAmbiguity . The value of the ambiguity is given in the gnss-CodePhaseAmbiguity field.
The integerCodePhase is optional. If integerCodePhase is absent, the default value is 0 milli-second.
Scale factor 1 milli-second, in the range from 0 to 127 milli-seconds. | +| codePhaseRMSerror | This field contains the pseudorange RMS error value. This parameter is specified according to a floating-point representation shown in the table below. | + +| GNSS-MeasurementList field descriptions | | +|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| doppler | This field contains the Doppler measured by the target device for the particular satellite signal. This information can be used to compute the 3-D velocity of the target device. Doppler measurements are converted into unit of m/s by multiplying the Doppler measurement in Hz by the nominal wavelength of the measured signal. Scale factor 0.04 metre/second. This field is optional, but shall be included, if the velocityRequest in CommonEsRequestLocationInformation is set to TRUE. | +| adr | This field contains the absolute value of the ADR measurement measured by the target device for the particular satellite signal. This information can be used to compute the 3-D velocity or high-accuracy position of the target device. ADR measurements are converted into units of metre by multiplying the ADR measurement by the nominal wavelength of the measured signal. Scale factor $2^{-10}$ metres, in the range from 0 to 32767.5 metres. This field is optional, but shall be included, if the adrMeasReq in GNSS-PositioningInstructions is set to TRUE and if ADR measurements are supported by the target device (i.e., adr-Support is set to TRUE in A-GNSS-ProvideCapabilities ). | +| adrMSB | This field contains the 4-MSBs of the ADR measurement in the case the ADR measurement is outside the range of the field adr alone. Scale factor 32768 metres. If present, the full ADR measurement is constructed as $adrMSB \times 32768 + adr \times 2^{-10}$ metres, representing measurements in the range from 0 to 524287.9990234375 metres. This field is optional, but shall be included, if the capability adrEnhancementsSupport is set to TRUE and the ADR measurement is outside the range of the adr field. | +| adrSign | This field indicates the sign of the ADR measurement. | +| adrRMSerror | This field contains the ADR root mean squared error value. Scale factor $2^{-10}$ metres. | +| delta-codePhase | This field specifies the higher resolution of the codePhase measurement. Scale factor $2^{-24}$ milli-seconds. The full code phase measurement is constructed as $codePhase \times 2^{-21} + delta-codePhase \times 2^{-24}$ milli-seconds, in the range from 0 to $(1-2^{-24})$ milli-seconds. | + +#### Value of *mpathDet* to Multipath Indication relation + +| Value of mpathDet | Multipath Indication | +|--------------------------|-----------------------------| +| 00 | Not measured | +| 01 | Low, MP error < 5m | +| 10 | Medium, 5m < MP error < 43m | +| 11 | High, MP error > 43m | + +#### Bit to Polarity Indication relation + +| Value | Polarity Indication | +|-------|---------------------------------------------| +| 0 | Data Direct, carrier phase not continuous | +| 1 | Data Inverted, carrier phase not continuous | +| 2 | Data Direct, carrier phase continuous | +| 3 | Data Inverted, carrier phase continuous | + +#### Bit to Ambiguity Indication relation + +| Value | Value MSB, LSB | Polarity Indication | +|-------|----------------|-------------------------------------------------------| +| 0 | 00 | carrier phase not continuous, no half-cycle ambiguity | +| 1 | 01 | carrier phase not continuous, half-cycle ambiguity | +| 2 | 10 | carrier phase continuous, no half-cycle ambiguity | +| 3 | 11 | carrier phase continuous, half-cycle ambiguity | + +**floating-point representation** + +| Index | Mantissa | Exponent | Floating-Point value, $x_i$ | Pseudorange value, P | +|-------|----------|----------|-----------------------------|------------------------| +| 0 | 000 | 000 | 0.5 | $P < 0.5$ | +| 1 | 001 | 000 | 0.5625 | $0.5 \leq P < 0.5625$ | +| $i$ | $x$ | $y$ | $0.5 * (1 + x/8) * 2^y$ | $x_{i-1} \leq P < x_i$ | +| 62 | 110 | 111 | 112 | $104 \leq P < 112$ | +| 63 | 111 | 111 | -- | $112 \leq P$ | + +![Timing diagram showing GNSS TOD, SV#1 time, SV#Nsat time, and target device observations with measurement information boxes.](8e688808a5a49f03662390e281bdbde9_img.jpg) + +The figure illustrates the calculation of GNSS Signal Measurement Information fields using timing diagrams. It shows the relationship between GNSS Time of Day (TOD), satellite clock biases, and observed times at a target device. + +- GNSS TOD t [ms]:** A sequence of frames (212-218) with a 1 ms interval. +- SV#1 time $t_{sv1}$ [ms]:** Shows frame 213 aligned with a vertical reference line, with a clock bias indicated. +- SV#Nsat time $t_{svNsat}$ [ms]:** Shows frame 213 aligned with the same reference line, with a different clock bias indicated. +- GNSS TOD Estimate [ms]:** A sequence of frames (211-218) at the target device. +- Serving eNB clock SFN:** Shows a frame number transition from 14 to 15. +- Observed SV#1 time $t_{sv1}$ [ms]:** A sequence of frames (140-147) at the target device. A specific epoch is chosen as the reference, with a 0.3617 ms offset from the eNB clock. +- Observed SV#Nsat time $t_{svNsat}$ [ms]:** A sequence of frames (135-141) at the target device. A ~1.7151 ms offset is shown from the reference epoch. + +**GNSS Signal Measurement Information:** + gnssTODmsec = 214 ms + systemFrameNumber = 15 + gnssCodePhaseAmbiguity = 4 ms + codePhase SV#1 = 0.3617 ms + integerCodePhase SV#1 = 0 + + codePhase SV#Nsat = 0.7151 ms + integerCodePhase SV#Nsat = 1 ms + +Timing diagram showing GNSS TOD, SV#1 time, SV#Nsat time, and target device observations with measurement information boxes. + +**Figure 6.5.2.6-1: Exemplary calculation of some GNSS Signal Measurement Information fields.** + +**GNSS-LocationInformation** + +The IE *GNSS-LocationInformation* is included by the target device when location and optionally velocity information derived using GNSS or hybrid GNSS and other measurements is provided to the location server. + +-- ASN1START + +``` + +GNSS-LocationInformation ::= SEQUENCE { + measurementReferenceTime MeasurementReferenceTime, + agnss-List GNSS-ID-Bitmap, + ... + [[ + ha-GNSS-Metrics-r17 HA-GNSS-Metrics-r17 OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +#### GNSS-LocationInformation field descriptions + +##### **measurementReferenceTime** + +This field specifies the GNSS system time for which the location estimate and optionally velocity are valid. It may also include GNSS-network time relationship, if requested by the location server and supported by the target device. + +##### **agnss-List** + +This field provides a list of satellite systems used by the target device to calculate the location estimate and velocity estimate, if included. This is represented by a bit string in *GNSS-ID-Bitmap*, with a one-value at the bit position means the particular method has been used; a zero-value means not used. + +##### **ha-GNSS-Metrics** + +This field provides high accuracy GNSS positioning metrics associated to the reported location estimate. + +## HA-GNSS-Metrics + +The IE *HA-GNSS-Metrics* is included by the target device when high accuracy GNSS positioning metrics associated to a location estimate is provided to the location server. The parameters provided in IE *HA-GNSS-Metrics* are used as specified for sentence type GGA in [51] and apply to all GNSSs and types of high accuracy GNSS assistance data. + +``` + +-- ASN1START + +HA-GNSS-Metrics-r17 ::= SEQUENCE { + nrOfUsedSatellites-r17 INTEGER (0..64), + hdopi-r17 INTEGER (1..256) OPTIONAL, + pdopi-r17 INTEGER (1..256) OPTIONAL, + age-r17 INTEGER (0..99) OPTIONAL, + fixType-r17 ENUMERATED {carrier-phase-float, + carrier-phase-fix, ...} OPTIONAL, + ... +} + +-- ASN1STOP + +``` + +#### HA-GNSS-Metrics field descriptions + +##### **nrOfUsedSatellites** + +This field specifies number of used GNSS satellites for the location estimate provided by the target device. + +##### **hdopi** + +This field specifies the horizontal dilution of precision for the location estimate, scale factor 0.1. + +##### **pdopi** + +This field specifies the 3D position dilution of precision, scale factor 0.1. + +##### **age** + +This field, if supported by the device, specifies the age of the most recent used assistance data for high accuracy GNSS, scale factor 0.1 second. + +##### **fixType** + +This field specifies the positioning fix type, based on the positioning fix quality indicators RTK float and RTK fix of [51]. Specifically: + +- *carrier-phase-float* - converged carrier phase floating point ambiguity resolution +- *carrier-phase-fix* - converging carrier phase integer ambiguity resolution + +## 6.5.2.7 GNSS Location Information Request + +### – *A-GNSS-RequestLocationInformation* + +The IE *A-GNSS-RequestLocationInformation* is used by the location server to request location information from the target device using GNSS. + +``` +-- ASN1START + +A-GNSS-RequestLocationInformation ::= SEQUENCE { + gnss-PositioningInstructions GNSS-PositioningInstructions, + ... +} + +-- ASN1STOP +``` + +## 6.5.2.8 GNSS Location Information Request Elements + +### – *GNSS-PositioningInstructions* + +The IE *GNSS-PositioningInstructions* is used to provide GNSS measurement instructions. + +``` +-- ASN1START + +GNSS-PositioningInstructions ::= SEQUENCE { + gnss-Methods GNSS-ID-Bitmap, + fineTimeAssistanceMeasReq BOOLEAN, + adrMeasReq BOOLEAN, + multiFreqMeasReq BOOLEAN, + assistanceAvailability BOOLEAN, + ... + [[ + ha-GNSS-Req-r15 ENUMERATED { true } OPTIONAL -- Cond UEB + ]], + [[ + ha-GNSS-MetricsReq-r17 ENUMERATED { true } OPTIONAL -- Cond UEB + ]] +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UEB | The field is optionally present, need OP, if the locationInformationType is set to locationEstimateRequired , locationEstimatePreferred , or locationMeasurementsPreferred ; otherwise it is not present. | + +| GNSS-PositioningInstructions field descriptions | | +|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnssMethods | This field indicates the satellite systems allowed by the location server. This is represented by a bit string in GNSS-ID-Bitmap , with a one-value at the bit position means the particular GNSS is allowed; a zero-value means not allowed. The target device shall not request assistance data or report or obtain measurements for systems that are not indicated in this bit map. At least one of the bits in this bit map shall be set to value one. | +| fineTimeAssistanceMeasReq | This field indicates whether the target device is requested to report GNSS-network time association. TRUE means requested. | +| adrMeasReq | This field indicates whether the target device is requested to include ADR measurements in GNSS-MeasurementList IE or not. TRUE means requested. | +| multiFreqMeasReq | This field indicates whether the target device is requested to report measurements on multiple supported GNSS signal types in GNSS-MeasurementList IE or not. TRUE means requested. | +| assistanceAvailability | This field indicates whether the target device may request additional GNSS assistance data from the server. TRUE means allowed and FALSE means not allowed. | + +| GNSS-PositioningInstructions field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ha-GNSS-Req
This field, if present, indicates that any location estimate provided by the target device should be obtained using high accuracy RTK/PPP methods. | +| ha-GNSS-MetricsReq
This field, if present, indicates that any location estimate provided by the target device should be reported with high accuracy GNSS positioning metrics. | + +## 6.5.2.9 GNSS Capability Information + +### – A-GNSS-ProvideCapabilities + +The IE *A-GNSS-Provide-Capabilities* is used by the target device to indicate its capability to support A-GNSS and to provide its A-GNSS location capabilities (e.g., GNSSs and assistance data supported) to the location server. + +``` + +-- ASN1START + +A-GNSS-ProvideCapabilities ::= SEQUENCE { + gnss-SupportList GNSS-SupportList OPTIONAL, + assistanceDataSupportList AssistanceDataSupportList OPTIONAL, + locationCoordinateTypes LocationCoordinateTypes OPTIONAL, + velocityTypes VelocityTypes OPTIONAL, + ..., + [[ periodicalReportingNotSupported-r14 + PositioningModes OPTIONAL, + idleStateForMeasurements-r14 + ENUMERATED { required } OPTIONAL + ]], + [[ periodicAssistanceData-r15 + BIT STRING { solicited (0), + unsolicited (1) } (SIZE (1..8)) OPTIONAL + ]], + [[ scheduledLocationRequestSupported-r17 + ScheduledLocationTimeSupportPerMode-r17 OPTIONAL + ]] +} + +GNSS-SupportList ::= SEQUENCE (SIZE(1..16)) OF GNSS-SupportElement + +GNSS-SupportElement ::= SEQUENCE { + gnss-ID GNSS-ID, + sbas-IDs SBAS-IDs OPTIONAL, -- Cond GNSS-ID-SBAS + agnss-Modes PositioningModes, + gnss-Signals GNSS-SignalIDs, + fta-MeasSupport SEQUENCE { + cellTime AccessTypes, + mode PositioningModes, + ... + } OPTIONAL, -- Cond fta + adr-Support BOOLEAN, + velocityMeasurementSupport BOOLEAN, + ..., + [[ + adrEnhancementsSupport-r15 ENUMERATED { true } OPTIONAL, + ha-gnss-Modes-r15 PositioningModes OPTIONAL + ]], + [[ + ha-gnss-MetricsSupport-r17 ENUMERATED { true } OPTIONAL + ]] +} + +AssistanceDataSupportList ::= SEQUENCE { + gnss-CommonAssistanceDataSupport GNSS-CommonAssistanceDataSupport, + gnss-GenericAssistanceDataSupport GNSS-GenericAssistanceDataSupport, + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| GNSS-ID-SBAS | The field is mandatory present if the GNSS-ID = sbas ; otherwise it is not present. | +| fta | The field is mandatory present if the target device supports the reporting of fine time assistance measurements; otherwise it is not present. | + +| A-GNSS-ProvideCapabilities field descriptions | | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-SupportList | This field specifies the list of GNSS supported by the target device and the target device capabilities associated with each of the supported GNSS. This field shall be present if the gnss-SupportListReq in the A-GNSS- RequestCapabilities IE is set to TRUE and if the target device supports the A-GNSS positioning method. If the IE A-GNSS- Provide-Capabilities is provided unsolicited, this field shall be included if the target device supports the assisted GNSS positioning method. | +| gnss-ID | This field specifies the GNSS supported by the target device for which the capabilities in GNSS-SupportElement are provided. | +| sbas-IDs | This field specifies the SBAS(s) supported by the target device. This is represented by a bit string, with a one-value at the bit position means the particular SBAS is supported; a zero-value means not supported. | +| agnss-Modes | This field specifies the GNSS mode(s) supported by the target device for the GNSS indicated by gnss-ID . This is represented by a bit string, with a one-value at the bit position means the particular GNSS mode is supported; a zero-value means not supported. | +| gnss-Signals | This field specifies the GNSS signal(s) supported by the target device for the GNSS indicated by gnss-ID . This is represented by a bit string, with a one-value at the bit position means the particular GNSS signal type is supported; a zero-value means not supported. | +| fta-MeasSupport | This field specifies that the target device is capable of performing fine time assistance measurements (i.e., GNSS-cellular time association reporting). The cellTime field specifies for which cellular network(s) this capability is supported. This is represented by a bit string, with a one-value at the bit position means FTA measurements for the specific cellular network time is supported; a zero-value means not supported. The mode field specifies for which GNSS mode(s) FTA measurements are supported by the target device. This is represented by a bit string, with a one-value at the bit position means FTA measurements for the GNSS mode is supported; a zero-value means not supported. | +| adr-Support | This field specifies whether the target device supports ADR measurement reporting. TRUE means supported. | +| velocityMeasurementSupport | This field specifies whether the target device supports measurement reporting related to velocity. TRUE means supported. | +| assistanceDataSupportList | This list defines the assistance data and assistance data choices supported by the target device. This field shall be present if the assistanceDataSupportListReq in the A-GNSS- RequestCapabilities IE is set to TRUE and if the target device supports GNSS assistance data. If the IE A-GNSS- Provide-Capabilities is provided unsolicited, this field shall be included if the target device supports any GNSS assistance data. | + +| A-GNSS-ProvideCapabilities field descriptions | | +|------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| locationCoordinateTypes | This parameter identifies the geographical location coordinate types that a target device supports for GNSS. TRUE indicates that a location coordinate type is supported and FALSE that it is not. This field shall be present if the locationVelocityTypesReq in the A-GNSS- RequestCapabilities IE is set to TRUE and if the target device supports UE-based or standalone GNSS positioning method. If the IE A-GNSS- Provide-Capabilities is provided unsolicited, this field shall be included if the target device supports UE-based or standalone GNSS positioning method. | +| velocityTypes | This parameter identifies the velocity types that a target device supports for GNSS. TRUE indicates that a velocity type is supported and FALSE that it is not. FALSE for all velocity types indicates that velocity reporting is not supported. This field shall be present if the locationVelocityTypesReq in the A-GNSS- RequestCapabilities IE is set to TRUE and if the target device supports UE-based or standalone GNSS positioning method. If the IE A-GNSS- Provide-Capabilities is provided unsolicited, this field shall be included if the target device supports UE-based or standalone GNSS positioning method. | +| periodicalReportingNotSupported | This field, if present, specifies the positioning modes for which the target device does not support periodicalReporting . This is represented by a bit string, with a one-value at the bit position means periodicalReporting for the positioning mode is not supported; a zero-value means supported. If this field is absent, the location server may assume that the target device supports periodicalReporting in CommonIEsRequestLocationInformation for each supported positioning mode. | +| idleStateForMeasurements | This field, if present, indicates that the target device requires idle state to perform GNSS measurements. | +| periodicAssistanceData | This field identifies the periodic assistance data delivery procedures supported by the target device. This is represented by a bit string, with a one value at the bit position means the periodic assistance data delivery procedure is supported; a zero value means not supported. Bit 0 (solicited) represents the procedure according to clause 5.2.1a; bit (1) (unsolicited) represents the procedure according to clause 5.2.2a. | +| adrEnhancementsSupport | This field, if present, indicates that the target device supports the fields adrMSB , adrSign , adrRMSerror , and delta-codePhase in IE GNSS-MeasurementList .
This field may only be present if adr-Support is set to TRUE, and shall be absent if adr-Support is set to FALSE. | +| ha-gnss-Modes | This field specifies the High-Accuracy GNSS mode(s) supported by the target device for the GNSS indicated by gnss-ID . This is represented by a bit string, with a one-value at the bit position means the particular GNSS mode is supported; a zero-value means not supported. | +| ha-gnss-MetricsSupport | This field specifies that high accuracy GNSS positioning metrics are supported by the target device. | +| scheduledLocationRequestSupported | This field, if present, specifies the positioning modes for which the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonIEsRequestLocationInformation – and the time base(s) supported for the scheduled location time for each positioning mode. If this field is absent, the target device does not support scheduled location requests. | + +## 6.5.2.10 GNSS Capability Information Elements + +### – GNSS-CommonAssistanceDataSupport + +The IE *GNSS-CommonAssistanceDataSupport* is used by the target device to provide information on supported GNSS common assistance data types to the location server. + +``` +-- ASN1START + +GNSS-CommonAssistanceDataSupport ::= SEQUENCE { + gnss-ReferenceTimeSupport GNSS-ReferenceTimeSupport + OPTIONAL, -- Cond RefTimeSup + gnss-ReferenceLocationSupport GNSS-ReferenceLocationSupport + OPTIONAL, -- Cond RefLocSup + gnss-IonosphericModelSupport GNSS-IonosphericModelSupport + OPTIONAL, -- Cond IonoModSup + gnss-EarthOrientationParametersSupport GNSS-EarthOrientationParametersSupport + OPTIONAL, -- Cond EOPSup + ..., + [[ + gnss-RTK-ReferenceStationInfoSupport-r15 + GNSS-RTK-ReferenceStationInfoSupport-r15 + OPTIONAL, -- Cond ARPSup + gnss-RTK-AuxiliaryStationDataSupport-r15 + GNSS-RTK-AuxiliaryStationDataSupport-r15 + OPTIONAL -- Cond ARPSup + ]] +} + +-- ASN1STOP +``` + +``` + + ]], + [[ + gnss-Integrity-ServiceParametersSupport-r17 + GNSS-Integrity-ServiceParametersSupport-r17 + OPTIONAL, -- Cond IntServiceSup + gnss-Integrity-ServiceAlertSupport-r17 + GNSS-Integrity-ServiceAlertSupport-r17 + OPTIONAL -- Cond IntAlertSup + ]], + [[ + gnss-SSR-IOD-UpdateSupport-r18 GNSS-SSR-IOD-UpdateSupport-r18 + OPTIONAL -- Cond IODUpdateSup + ]] + } + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| RefTimeSup | The field is mandatory present if the target device supports GNSS-ReferenceTime ; otherwise it is not present. | +| RefLocSup | This field is mandatory present if the target device supports GNSS-ReferenceLocation ; otherwise it is not present. | +| IonoModSup | This field is mandatory present if the target device supports GNSS-IonosphericModel ; otherwise it is not present. | +| EOPSup | This field is mandatory present if the target device supports GNSS-EarthOrientationParameters ; otherwise it is not present. | +| ARPSup | This field is mandatory present if the target device supports GNSS-RTK-ReferenceStationInfo ; otherwise it is not present. | +| AuxARPSup | This field is mandatory present if the target device supports GNSS-RTK-AuxiliaryStationData ; otherwise it is not present. | +| IntServiceSup | This field is mandatory present if the target device supports GNSS-Integrity-ServiceParameters ; otherwise it is not present. | +| IntAlertSup | This field is mandatory present if the target device supports GNSS-Integrity-ServiceAlert ; otherwise it is not present. | +| IODUpdateSup | This field is mandatory present if the target device supports GNSS SSR-IOD-Update ; otherwise it is not present. | + +## – *GNSS-ReferenceTimeSupport* + +``` + +-- ASN1START + +GNSS-ReferenceTimeSupport ::= SEQUENCE { + gnss-SystemTime GNSS-ID-Bitmap, + fta-Support AccessTypes + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| fta | The field is mandatory present if the target device supports fine time assistance in GNSSReferenceTime IE; otherwise it is not present. | + +| GNSS-ReferenceTimeSupport field descriptions | | +|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-SystemTime | This field specifies the GNSS system time(s) supported by the target device. This is represented by a bit string in GNSS-ID-Bitmap , with a one-value at the bit position means the particular GNSS system time is supported; a zero-value means not supported. | +| fta-Support | This field specifies that the target device supports fine time assistance (i.e., GNSS-cellular time association) in GNSS-ReferenceTime IE. This is represented by a bit string in AccessTypes , with a one-value at the bit position means FTA for the specific cellular network time is supported; a zero-value means not supported. | + +– ***GNSS-ReferenceLocationSupport*** + +``` +-- ASN1START +GNSS-ReferenceLocationSupport ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +– ***GNSS-IonosphericModelSupport*** + +``` +-- ASN1START +GNSS-IonosphericModelSupport ::= SEQUENCE { + ionoModel BIT STRING { + klobuchar (0), + neQuick (1), + klobuchar2-r16 (2) } (SIZE (1..8)), + ... +} +-- ASN1STOP +``` + +| GNSS-IonosphericModelSupport field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

ionoModel
This field specifies the ionospheric model(s) supported by the target device. This is represented by a bit string, with a one-value at the bit position means the particular ionospheric model is supported; a zero-value means not supported.

| + +– ***GNSS-EarthOrientationParametersSupport*** + +``` +-- ASN1START +GNSS-EarthOrientationParametersSupport ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +– ***GNSS-RTK-ReferenceStationInfoSupport*** + +``` +-- ASN1START +GNSS-RTK-ReferenceStationInfoSupport-r15 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +– ***GNSS-RTK-AuxiliaryStationDataSupport*** + +``` +-- ASN1START +GNSS-RTK-AuxiliaryStationDataSupport-r15 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +– ***GNSS-Integrity-ServiceParametersSupport*** + +``` +-- ASN1START +GNSS-Integrity-ServiceParametersSupport-r17 ::= SEQUENCE { + ... +} +``` + +``` + +} +-- ASN1STOP + +``` + +### — *GNSS-Integrity-ServiceAlertSupport* + +``` + +-- ASN1START +GNSS-Integrity-ServiceAlertSupport-r17 ::= SEQUENCE { + ... +} +-- ASN1STOP + +``` + +### — *GNSS-SSR-IOD-UpdateSupport* + +``` + +-- ASN1START +GNSS-SSR-IOD-UpdateSupport-r18 ::= SEQUENCE { + ... +} +-- ASN1STOP + +``` + +### — *GNSS-GenericAssistanceDataSupport* + +The IE *GNSS-GenericAssistanceDataSupport* is used by the target device to provide information on supported GNSS generic assistance data types to the location server for each supported GNSS. + +``` + +-- ASN1START +GNSS-GenericAssistanceDataSupport ::= + SEQUENCE (SIZE (1..16)) OF GNSS-GenericAssistDataSupportElement +GNSS-GenericAssistDataSupportElement ::= SEQUENCE { + gnss-ID GNSS-ID, + sbas-ID SBAS-ID OPTIONAL, -- Cond GNSS-ID-SBAS + gnss-TimeModelsSupport GNSS-TimeModelListSupport + OPTIONAL, -- Cond TimeModSup + gnss-DifferentialCorrectionsSupport GNSS-DifferentialCorrectionsSupport + OPTIONAL, -- Cond DGNSS-Sup + gnss-NavigationModelSupport GNSS-NavigationModelSupport + OPTIONAL, -- Cond NavModSup + gnss-RealTimeIntegritySupport GNSS-RealTimeIntegritySupport + OPTIONAL, -- Cond RTISup + gnss-DataBitAssistanceSupport GNSS-DataBitAssistanceSupport + OPTIONAL, -- Cond DataBitsSup + gnss-AcquisitionAssistanceSupport GNSS-AcquisitionAssistanceSupport + OPTIONAL, -- Cond AcquAssistSup + gnss-AlmanacSupport GNSS-AlmanacSupport + OPTIONAL, -- Cond AlmanacSup + gnss-UTC-ModelSupport GNSS-UTC-ModelSupport + OPTIONAL, -- Cond UTCModSup + gnss-AuxiliaryInformationSupport GNSS-AuxiliaryInformationSupport + OPTIONAL, -- Cond AuxInfoSup + ..., + [[ + bds-DifferentialCorrectionsSupport-r12 + BDS-DifferentialCorrectionsSupport-r12 + OPTIONAL, -- Cond DBDS-Sup + bds-GridModelSupport-r12 BDS-GridModelSupport-r12 + OPTIONAL -- Cond BDS-GridModSup + ]], + [[ + gnss-RTK-ObservationsSupport-r15 + GNSS-RTK-ObservationsSupport-r15 + OPTIONAL, -- Cond RTK-OSR-Sup + glo-RTK-BiasInformationSupport-r15 + GLO-RTK-BiasInformationSupport-r15 + OPTIONAL, -- Cond GLO-CPB-Sup + gnss-RTK-MAC-CorrectionDifferencesSupport-r15 + +``` + +``` + + GNSS-RTK-MAC-CorrectionDifferencesSupport-r15 + OPTIONAL, -- Cond MAC-Sup +gnss-RTK-ResidualsSupport-r15 GNSS-RTK-ResidualsSupport-r15 + OPTIONAL, -- Cond Res-Sup +gnss-RTK-FKP-GradientsSupport-r15 + GNSS-RTK-FKP-GradientsSupport-r15 + OPTIONAL, -- Cond FKP-Sup +gnss-SSR-OrbitCorrectionsSupport-r15 + GNSS-SSR-OrbitCorrectionsSupport-r15 + OPTIONAL, -- Cond OC-Sup +gnss-SSR-ClockCorrectionsSupport-r15 + GNSS-SSR-ClockCorrectionsSupport-r15 + OPTIONAL, -- Cond CC-Sup +gnss-SSR-CodeBiasSupport-r15 GNSS-SSR-CodeBiasSupport-r15 + OPTIONAL -- Cond CB-Sup + ]], + [[ +gnss-SSR-URA-Support-r16 GNSS-SSR-URA-Support-r16 OPTIONAL, -- Cond URA-Sup +gnss-SSR-PhaseBiasSupport-r16 GNSS-SSR-PhaseBiasSupport-r16 + OPTIONAL, -- Cond PB-Sup +gnss-SSR-STECCorrectionSupport-r16 + GNSS-SSR-STECCorrectionSupport-r16 + OPTIONAL, -- Cond STEC-Sup +gnss-SSR-GriddedCorrectionSupport-r16 + GNSS-SSR-GriddedCorrectionSupport-r16 + OPTIONAL, -- Cond Grid-Sup +navic-DifferentialCorrectionsSupport-r16 + NavIC-DifferentialCorrectionsSupport-r16 + OPTIONAL, -- Cond DNavIC-Sup +navic-GridModelSupport-r16 NavIC-GridModelSupport-r16 + OPTIONAL -- Cond NavIC-GridModSup + ]], + [[ +gnss-SSR-OrbitCorrectionsSet2Support-r17 + GNSS-SSR-OrbitCorrectionsSet2Support-r17 + OPTIONAL, -- Cond OC2-Sup +gnss-SSR-ClockCorrectionsSet2Support-r17 + GNSS-SSR-ClockCorrectionsSet2Support-r17 + OPTIONAL, -- Cond CC2-Sup +gnss-SSR-URA-Set2Support-r17 GNSS-SSR-URA-Set2Support-r17 + OPTIONAL -- Cond URA2-Sup + ]], + [[ +gnss-LOS-NLOS-GriddedIndicationsSupport-r18 + GNSS-LOS-NLOS-GriddedIndicationsSupport-r18 + OPTIONAL, -- Cond LOS-NLOS-Grid-Sup +gnss-SSR-SatellitePCVResidualsSupport-r18 + GNSS-SSR-SatellitePCVResidualsSupport-r18 + OPTIONAL -- Cond SatPCV-Sup + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------| +| GNSS-ID-SBAS | The field is mandatory present if the GNSS-ID = sbas ; otherwise it is not present. | +| TimeModSup | The field is mandatory present if the target device supports GNSS-TimeModelList ; otherwise it is not present. | +| DGNSS-Sup | The field is mandatory present if the target device supports GNSS-DifferentialCorrections ; otherwise it is not present. | +| NavModSup | The field is mandatory present if the target device supports GNSS-NavigationModel ; otherwise it is not present. | +| RTISup | The field is mandatory present if the target device supports GNSS-RealTimeIntegrity ; otherwise it is not present. | +| DataBitsSup | The field is mandatory present if the target device supports GNSS-DataBitAssistance ; otherwise it is not present. | +| AcquAssistSup | The field is mandatory present if the target device supports GNSS-AcquisitionAssistance ; otherwise it is not present. | +| AlmanacSup | The field is mandatory present if the target device supports GNSS-Almanac ; otherwise it is not present. | +| UTCModSup | The field is mandatory present if the target device supports GNSS-UTC-Model ; otherwise it is not present. | +| AuxInfoSup | The field is mandatory present if the target device supports GNSS-AuxiliaryInformation ; otherwise it is not present. | + +| Conditional presence | Explanation | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DBDS-Sup | The field is mandatory present if the target device supports BDS-DifferentialCorrections ; otherwise it is not present. This field may only be present if gnss-ID indicates 'bds'. | +| BDS-GridModSup | The field is mandatory present if the target device supports BDS-GridModel ; otherwise it is not present. This field may only be present if gnss-ID indicates 'bds'. | +| RTK-OSR-Sup | The field is mandatory present if the target device supports GNSS-RTK-Observations ; otherwise it is not present. Note, support for GNSS-RTK-Observations implies support for GNSS-RTK-CommonObservationInfo as well. | +| GLO-CPB-Sup | The field is mandatory present if the target device supports GLO-RTK-BiasInformation ; otherwise it is not present. This field may only be present if gnss-ID indicates 'glonass'. | +| MAC-Sup | The field is mandatory present if the target device supports GNSS-RTK-MAC-CorrectionDifferences ; otherwise it is not present. | +| Res-Sup | The field is mandatory present if the target device supports GNSS-RTK-Residuals ; otherwise it is not present. | +| FKP-Sup | The field is mandatory present if the target device supports GNSS-RTK-FKP-Gradients ; otherwise it is not present. | +| OC-Sup | The field is mandatory present if the target device supports GNSS-SSR-OrbitCorrections ; otherwise it is not present. | +| CC-Sup | The field is mandatory present if the target device supports GNSS-SSR-ClockCorrections ; otherwise it is not present. | +| CB-Sup | The field is mandatory present if the target device supports GNSS-SSR-CodeBias ; otherwise it is not present. | +| URA-Sup | The field is mandatory present if the target device supports GNSS-SSR-URA ; otherwise it is not present. | +| PB-Sup | The field is mandatory present if the target device supports GNSS-SSR-PhaseBias ; otherwise it is not present. | +| STEC-Sup | The field is mandatory present if the target device supports GNSS-SSR-STECCorrection ; otherwise it is not present. | +| Grid-Sup | The field is mandatory present if the target device supports GNSS-SSR-GriddedCorrection ; otherwise it is not present. Note, support for GNSS-SSR-GriddedCorrection implies support for GNSS-SSR-CorrectionPoints as well. | +| DNavIC-Sup | The field is mandatory present if the target device supports NavIC-DifferentialCorrections ; otherwise it is not present. This field may only be present if the gnss-ID indicates 'navic'. | +| NavIC-GridModSup | The field is mandatory present if the target device supports NavIC-GridModel ; otherwise it is not present. This field may only be present if the gnss-ID indicates 'navic'. | +| OC2-Sup | The field is mandatory present if the target device supports GNSS-SSR-OrbitCorrectionsSet2 ; otherwise it is not present. | +| CC2-Sup | The field is mandatory present if the target device supports GNSS-SSR-ClockCorrectionsSet2 ; otherwise it is not present. | +| URA2-Sup | The field is mandatory present if the target device supports GNSS-SSR-URA-Set2 ; otherwise it is not present. | +| LOS-NLOS-Grid-Sup | The field is mandatory present if the target device supports GNSS-LOS-NLOS-GriddedIndications ; otherwise it is not present. Support for GNSS-LOS-NLOS-GriddedIndications implies support for GNSS-LOS-NLOS-GridPoints . | +| SatPCV-Sup | The field is mandatory present if the target device supports GNSS-SSR-SatellitePCVResiduals ; otherwise it is not present. | + +### — *GNSS-TimeModelListSupport* + +``` +-- ASN1START +GNSS-TimeModelListSupport ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### — *GNSS-DifferentialCorrectionSupport* + +``` +-- ASN1START +GNSS-DifferentialCorrectionsSupport ::= SEQUENCE { + gnssSignalIDs GNSS-SignalIDs, + dgnss-ValidityTimeSup BOOLEAN, + ... +} +``` + +``` +-- ASN1STOP +``` + +#### GNSS-DifferentialCorrectionsSupport field descriptions + +##### **gnssSignalIDs** + +This field specifies the GNSS signal types for which differential corrections are supported by the target device. This is represented by a bit string in *GNSS-SignalIDs*, with a one-value at the bit position means differential corrections for the particular GNSS signal type is supported; a zero-value means not supported. + +##### **dgnss-ValidityTimeSup** + +This field specifies if the target device supports estimation of UDRE based on growth rate and validity time for differential corrections. TRUE means supported. + +#### — **GNSS-NavigationModelSupport** + +``` +-- ASN1START +``` + +``` +GNSS-NavigationModelSupport ::= SEQUENCE { + clockModel BIT STRING { + model-1 (0), + model-2 (1), + model-3 (2), + model-4 (3), + model-5 (4), + model-6 (5), + model-7-r16 (6), + model-8-r16 (7) } (SIZE (1..8)) OPTIONAL, + orbitModel BIT STRING { + model-1 (0), + model-2 (1), + model-3 (2), + model-4 (3), + model-5 (4), + model-6 (5), + model-7-r16 (6), + model-8-r16 (7) } (SIZE (1..8)) OPTIONAL, + ... +} +``` + +``` +-- ASN1STOP +``` + +#### GNSS-NavigationModelSupport field descriptions + +##### **clockModel** + +This field specifies the *gnss-ClockModel* choice(s) in *GNSS-NavigationModel* IE supported by the target device for the GNSS indicated by *GNSS-ID*. This is represented by a bit string, with a one-value at the bit position means the particular clock model is supported; a zero-value means not supported. + +If the target device supports GPS and *GNSS-NavigationModel* assistance, it shall support *clockModel* Model-2. + +If the target device supports SBAS and *GNSS-NavigationModel* assistance, it shall support *clockModel* Model-5. + +If the target device supports QZSS and *GNSS-NavigationModel* assistance, it shall support *clockModel* Model-2. + +If the target device supports Galileo and *GNSS-NavigationModel* assistance, it shall support *clockModel* Model-1. + +If the target device supports GLONASS and *GNSS-NavigationModel* assistance, it shall support *clockModel* Model-4. + +If the target device supports BDS and *GNSS-NavigationModel* assistance, it shall support *clockModel* Model-6. + +If the target device supports NavIC and *GNSS-NavigationModel* assistance, it shall support *clockModel* Model-8. + +If this field is absent, the target device supports the mandatory (native) *clockModel* choice only as listed above for the GNSS indicated by *GNSS-ID*. + +##### **orbitModel** + +This field specifies the *gnss-OrbitModel* choice(s) in *GNSS-NavigationModel* IE supported by the target device for the GNSS indicated by *GNSS-ID*. This is represented by a bit string, with a one-value at the bit position means the particular orbit model is supported; a zero-value means not supported. + +If the target device supports GPS and *GNSS-NavigationModel* assistance, it shall support *orbitModel* Model-2. + +If the target device supports SBAS and *GNSS-NavigationModel* assistance, it shall support *orbitModel* Model-5. + +If the target device supports QZSS and *GNSS-NavigationModel* assistance, it shall support *orbitModel* Model-2. + +If the target device supports Galileo and *GNSS-NavigationModel* assistance, it shall support *orbitModel* Model-1. + +If the target device supports GLONASS and *GNSS-NavigationModel* assistance, it shall support *orbitModel* Model-4. + +If the target device supports BDS and *GNSS-NavigationModel* assistance, it shall support *orbitModel* Model-6. + +If the target device supports NavIC and *GNSS-NavigationModel* assistance, it shall support *orbitModel* Model-8. + +If this field is absent, the target device supports the mandatory (native) *orbitModel* choice only as listed above for the GNSS indicated by *GNSS-ID*. + +### — *GNSS-RealTimeIntegritySupport* + +``` +-- ASN1START +GNSS-RealTimeIntegritySupport ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### — *GNSS-DataBitAssistanceSupport* + +``` +-- ASN1START +GNSS-DataBitAssistanceSupport ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### — *GNSS-AcquisitionAssistanceSupport* + +``` +-- ASN1START +GNSS-AcquisitionAssistanceSupport ::= SEQUENCE { + ... + confidenceSupport-r10 ENUMERATED { true } OPTIONAL, + dopplerUncertaintyExtSupport-r10 ENUMERATED { true } OPTIONAL +} +-- ASN1STOP +``` + +#### **GNSS-AcquisitionAssistanceSupport field descriptions** + +##### ***confidenceSupport*** + +If this field is present, the target device supports the *confidence* field in *GNSS-AcquisitionAssistance*. + +##### ***dopplerUncertaintyExtSupport*** + +If this field is present, the target device supports the *dopplerUncertaintyExt* field in *GNSS-AcquisitionAssistance*. + +### — *GNSS-AlmanacSupport* + +``` +-- ASN1START +GNSS-AlmanacSupport ::= SEQUENCE { + almanacModel BIT STRING { + model-1 (0), + model-2 (1), + model-3 (2), + model-4 (3), + model-5 (4), + model-6 (5), + model-7 (6) } (SIZE (1..8)) OPTIONAL, + ... +} +-- ASN1STOP +``` + +**GNSS-AlmanacSupport field descriptions*****almanacModel*** + +This field specifies the *almanacModel* choice(s) in *GNSS-Almanac* IE supported by the target device for the GNSS indicated by *GNSS-ID*. This is represented by a bit string, with a one-value at the bit position means the particular almanac model is supported; a zero-value means not supported. + +If the target device supports GPS and *GNSS-Almanac* assistance, it shall support Model-2. + +If the target device supports SBAS and *GNSS-Almanac* assistance, it shall support Model-6. + +If the target device supports QZSS and *GNSS-Almanac* assistance, it shall support Model-2. + +If the target device supports Galileo and *GNSS-Almanac* assistance, it shall support Model-1. + +If the target device supports GLONASS and *GNSS-Almanac* assistance, it shall support Model-5. + +If the target device supports BDS and *GNSS-Almanac* assistance, it shall support Model-7. + +If this field is absent, the target device supports the mandatory (native) *almanacModel* choice only as listed above for the GNSS indicated by *GNSS-ID*. + +## — ***GNSS-UTC-ModelSupport*** + +``` +-- ASN1START +GNSS-UTC-ModelSupport ::= SEQUENCE { + utc-Model BIT STRING { + model-1 (0), + model-2 (1), + model-3 (2), + model-4 (3), + model-5 (4) } (SIZE (1..8)) OPTIONAL, + ... +} + +-- ASN1STOP +``` + +**GNSS-UTC-ModelSupport field descriptions*****utc-Model*** + +This field specifies the *GNSS-UTC-Model* choice(s) in *GNSS-UTC-Model* IE supported by the target device for the GNSS indicated by *GNSS-ID*. This is represented by a bit string, with a one-value at the bit position means the particular UTC model is supported; a zero-value means not supported. + +If the target device supports GPS and *GNSS-UTC-Model* assistance, it shall support Model-1. + +If the target device supports SBAS and *GNSS-UTC-Model* assistance, it shall support Model-4. + +If the target device supports QZSS and *GNSS-UTC-Model* assistance, it shall support Model-1. + +If the target device supports Galileo and *GNSS-UTC-Model* assistance, it shall support Model-1. + +If the target device supports GLONASS and *GNSS-UTC-Model* assistance, it shall support Model-3. + +If the target device supports BDS and *GNSS-UTC-Model* assistance, it shall support Model-5. + +If this field is absent, the target device supports the mandatory (native) *utc-Model* choice only as listed above for the GNSS indicated by *GNSS-ID*. + +## — ***GNSS-AuxiliaryInformationSupport*** + +``` +-- ASN1START +GNSS-AuxiliaryInformationSupport ::= SEQUENCE { + ... +} + +-- ASN1STOP +``` + +## — ***BDS-DifferentialCorrectionsSupport*** + +``` +-- ASN1START +BDS-DifferentialCorrectionsSupport-r12 ::= SEQUENCE { + gnssSignalIDs GNSS-SignalIDs, + ... +} + +-- ASN1STOP +``` + +| BDS-DifferentialCorrectionsSupport field descriptions | +|---------------------------------------------------------------------| +|---------------------------------------------------------------------| + +| | +|-----------------------------| +| gnssSignalIDs | +|-----------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

This field specifies the BDS signal types for which differential corrections are supported by the target device. This is represented by a bit string in GNSS-SignalIDs, with a one-value at the bit position means differential corrections for the particular BDS signal type is supported; a zero-value means not supported.

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +— ***BDS-GridModelSupport*** + +``` +-- ASN1START +BDS-GridModelSupport-r12 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +— ***GNSS-RTK-ObservationsSupport*** + +``` +-- ASN1START +GNSS-RTK-ObservationsSupport-r15 ::= SEQUENCE { + gnssSignalIDs-r15 GNSS-SignalIDs, + ... +} +-- ASN1STOP +``` + +| GNSS-RTK-ObservationsSupport field descriptions | +|---------------------------------------------------------------| +|---------------------------------------------------------------| + +| | +|-----------------------------| +| gnssSignalIDs | +|-----------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

This field specifies the GNSS signal types for which GNSS-RTK-Observations are supported by the target device. This is represented by a bit string in GNSS-SignalIDs, with a one-value at the bit position means GNSS-RTK-Observations for the particular GNSS signal type is supported; a zero-value means not supported.

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +— ***GLO-RTK-BiasInformationSupport*** + +``` +-- ASN1START +GLO-RTK-BiasInformationSupport-r15 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +— ***GNSS-RTK-MAC-CorrectionDifferencesSupport*** + +``` +-- ASN1START +GNSS-RTK-MAC-CorrectionDifferencesSupport-r15 ::= SEQUENCE { + link-combinations-support-r15 GNSS-Link-CombinationsList-r15, + ... +} +-- ASN1STOP +``` + +| GNSS-RTK-MAC-CorrectionDifferencesSupport field descriptions | +|----------------------------------------------------------------------------| +|----------------------------------------------------------------------------| + +| | +|-----------------------------------------| +| link-combinations-support | +|-----------------------------------------| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

This field specifies the GNSS link/frequency combinations for which GNSS-RTK-MAC-CorrectionDifferences are supported by the target device for the GNSS indicated by GNSS-ID.

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## — **GNSS-RTK-ResidualsSupport** + +``` +-- ASN1START +GNSS-RTK-ResidualsSupport-r15 ::= SEQUENCE { + link-combinations-support-r15 GNSS-Link-CombinationsList-r15, + ... +} +-- ASN1STOP +``` + +### **GNSS-RTK-ResidualsSupport field descriptions** + +#### ***link-combinations-support*** + +This field specifies the GNSS link/frequency combinations for which *GNSS-RTK-Residuals* are supported by the target device for the GNSS indicated by *GNSS-ID*. + +## — **GNSS-RTK-FKP-GradientsSupport** + +``` +-- ASN1START +GNSS-RTK-FKP-GradientsSupport-r15 ::= SEQUENCE { + link-combinations-support-r15 GNSS-Link-CombinationsList-r15, + ... +} +-- ASN1STOP +``` + +### **GNSS-RTK-FKP-GradientsSupport field descriptions** + +#### ***link-combinations-support*** + +This field specifies the GNSS link/frequency combinations for which *GNSS-RTK-FKP-Gradients* are supported by the target device for the GNSS indicated by *GNSS-ID*. + +## — **GNSS-SSR-OrbitCorrectionsSupport** + +``` +-- ASN1START +GNSS-SSR-OrbitCorrectionsSupport-r15 ::= SEQUENCE { + ... + [[ + orbit-IntegritySup-r17 BIT STRING { correlationTimeSup (0) + } (SIZE(1..8)) + ]] +} +-- ASN1STOP +``` + +### **GNSS-SSR-OrbitCorrectionsSupport field descriptions** + +#### ***orbit-IntegritySup*** + +This field, if present, indicates that the target device supports the IEs *ORBIT-IntegrityParameters* and *SSR-IntegrityOrbitBounds*. + +A one-value at the bit position '0' means that the target device supports the fields *orbitRangeErrorCorrelationTime* and *orbitRangeRateErrorCorrelationTime* in IE *ORBIT-IntegrityParameters*. + +## — **GNSS-SSR-ClockCorrectionsSupport** + +``` +-- ASN1START +GNSS-SSR-ClockCorrectionsSupport-r15 ::= SEQUENCE { + ... + [[ + clock-IntegrityParameterSupport-r17 ENUMERATED { supported } OPTIONAL, + ssr-IntegrityClockBoundsSupport-r17 ENUMERATED { supported } OPTIONAL + ]] +} +``` + +``` +-- ASN1STOP +``` + +| GNSS-SSR-ClockCorrectionsSupport field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| clock-IntegrityParameterSupport
This field, if present, indicates that the target device supports the CLOCK-IntegrityParameters in IE GNSS-SSR-ClockCorrections . | +| ssr-IntegrityClockBoundsSupports
This field. If present, indicates that the target device supports the SSR-IntegrityClockBounds in IE GNSS-SSR-ClockCorrections . | + +### — **GNSS-SSR-CodeBiasSupport** + +``` +-- ASN1START +``` + +``` +GNSS-SSR-CodeBiasSupport-r15 ::= SEQUENCE { + signal-and-tracking-mode-ID-Sup-r15 GNSS-SignalIDs, + ... + [[ + ssr-IntegrityCodeBiasBoundsSup-r17 ENUMERATED { supported } OPTIONAL + ]] +} +``` + +``` +-- ASN1STOP +``` + +| GNSS-SSR-CodeBiasSupport field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| signal-and-tracking-mode-ID-Sup
This field specifies the GNSS signal(s) for which the GNSS-SSR-CodeBias is supported by the target device. | +| ssr-IntegrityCodeBiasBoundsSup
This field, if present, indicates that the target device supports the IE SSR-IntegrityCodeBiasBounds . | + +### — **GNSS-SSR-URA-Support** + +``` +-- ASN1START +``` + +``` +GNSS-SSR-URA-Support-r16 ::= SEQUENCE { + ... +} +``` + +``` +-- ASN1STOP +``` + +### — **GNSS-SSR-PhaseBiasSupport** + +``` +-- ASN1START +``` + +``` +GNSS-SSR-PhaseBiasSupport-r16 ::= SEQUENCE { + signal-and-tracking-mode-ID-Sup-r16 GNSS-SignalIDs, + ... + [[ + ssr-IntegrityPhaseBiasBoundsSup-r17 ENUMERATED { supported } OPTIONAL + ]] +} +``` + +``` +-- ASN1STOP +``` + +| GNSS-SSR-PhaseBiasSupport field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| signal-and-tracking-mode-ID-Sup
This field specifies the GNSS signal(s) for which the GNSS-SSR-PhaseBias is supported by the target device. | +| ssr-IntegrityPhaseBiasBoundsSup
This field, if present, indicates that the target device supports the IE SSR-IntegrityPhaseBiasBounds . | + +## GNSS-SSR-STECCorrectionSupport + +``` +-- ASN1START +GNSS-SSR-STECCorrectionSupport-r16 ::= SEQUENCE { + ... + [[ + stec-IntegritySup-r17 BIT STRING { correlationTimeSup (0) + } (SIZE(1..8)) + ]] OPTIONAL +} + +-- ASN1STOP +``` + +### GNSS-SSR-STECCorrectionSupport field descriptions + +#### **stec-IntegritySup** + +This field, if present, indicates that the target device supports the IEs *STECCorrectionIntegrityParameters* and *STECCorrectionErrorBounds*. + +A one-value at the bit position '0' means that the target device supports the fields *ionoRangeErrorCorrelationTime* and *ionoRangeRateErrorCorrelationTime* in IE *STECCorrectionIntegrityParameters*. + +## GNSS-SSR-GriddedCorrectionSupport + +``` +-- ASN1START +GNSS-SSR-GriddedCorrectionSupport-r16 ::= SEQUENCE { + ... + [[ + griddedCorrectionIntegritySup-r17 ENUMERATED { supported } + ]] OPTIONAL +} + +-- ASN1STOP +``` + +### GNSS-SSR-GriddedCorrectionSupport field descriptions + +#### **griddedCorrectionIntegritySup** + +This field, if present, indicates that the target device supports the IEs *SSR-GriddedCorrectionIntegrityParameters* and *TropoDelayIntegrityErrorBounds*. + +## NavIC-DifferentialCorrectionsSupport + +``` +-- ASN1START +NavIC-DifferentialCorrectionsSupport-r16 ::= SEQUENCE { + gnssSignalIDs-r16 GNSS-SignalIDs, + ... +} + +-- ASN1STOP +``` + +### NavIC-DifferentialCorrectionsSupport field descriptions + +#### **gnssSignalIDs** + +This field specifies the NavIC signal types for which differential corrections are supported by the target device. This is represented by a bit string in *GNSS-SignalIDs*, with a one-value at the bit position means differential corrections for the particular NavIC signal type is supported; a zero-value means not supported. + +## NavIC-GridModelSupport + +``` +-- ASN1START +NavIC-GridModelSupport-r16 ::= SEQUENCE { + ... +} +``` + +``` +-- ASN1STOP +``` + +— ***GNSS-SSR-OrbitCorrectionsSet2Support*** + +``` +-- ASN1START +``` + +``` +GNSS-SSR-OrbitCorrectionsSet2Support-r17 ::= SEQUENCE { + ... +} +``` + +``` +-- ASN1STOP +``` + +— ***GNSS-SSR-ClockCorrectionsSet2Support*** + +``` +-- ASN1START +``` + +``` +GNSS-SSR-ClockCorrectionsSet2Support-r17 ::= SEQUENCE { + ... +} +``` + +``` +-- ASN1STOP +``` + +— ***GNSS-SSR-URA-Set2Support*** + +``` +-- ASN1START +``` + +``` +GNSS-SSR-URA-Set2Support-r17 ::= SEQUENCE { + ... +} +``` + +``` +-- ASN1STOP +``` + +— ***GNSS-LOS-NLOS-GriddedIndicationsSupport*** + +``` +-- ASN1START +``` + +``` +GNSS-LOS-NLOS-GriddedIndicationsSupport-r18 ::= SEQUENCE { + ... +} +``` + +``` +-- ASN1STOP +``` + +— ***GNSS-SSR-SatellitePCVResidualsSupport*** + +``` +-- ASN1START +``` + +``` +GNSS-SSR-SatellitePCVResidualsSupport-r18 ::= SEQUENCE { + ... +} +``` + +``` +-- ASN1STOP +``` + +## 6.5.2.11 GNSS Capability Information Request + +— ***A-GNSS-RequestCapabilities*** + +The IE *A-GNSS-Request-Capabilities* is used by the location server to request A-GNSS location capabilities (e.g., GNSSs and assistance data supported) from the target device. + +``` +-- ASN1START +``` + +``` +A-GNSS-RequestCapabilities ::= SEQUENCE { + gnss-SupportListReq BOOLEAN, +``` + +``` + + assistanceDataSupportListReq BOOLEAN, + locationVelocityTypesReq BOOLEAN, + ... +} + +-- ASN1STOP + +``` + +#### **A-GNSS-RequestCapabilities field descriptions** + +##### ***gnss-SupportListReq*** + +This field specifies whether the target device is requested to include the *gnss-SupportList* field in the *A-GNSS-ProvideCapabilities* IE or not. TRUE means requested. + +##### ***assistanceDataSupportListReq*** + +This field specifies whether the target device is requested to include the *assistanceDataSupportList* field in the *A-GNSS-ProvideCapabilities* IE or not. TRUE means requested. + +##### ***locationVelocityTypesReq*** + +This field specifies whether the target device is requested to include the *locationCoordinateTypes* field and *velocityTypes* field in the *A-GNSS-ProvideCapabilities* IE or not. TRUE means requested. + +## 6.5.2.12 GNSS Error Elements + +### – ***A-GNSS-Error*** + +The IE *A-GNSS-Error* is used by the location server or target device to provide GNSS error reasons. + +``` + +-- ASN1START + +A-GNSS-Error ::= CHOICE { + locationServerErrorCauses GNSS-LocationServerErrorCauses, + targetDeviceErrorCauses GNSS-TargetDeviceErrorCauses, + ... +} + +-- ASN1STOP + +``` + +### – ***GNSS-LocationServerErrorCauses*** + +The IE *GNSS-LocationServerErrorCauses* is used by the location server to provide GNSS error reasons to the target device. + +``` + +-- ASN1START + +GNSS-LocationServerErrorCauses ::= SEQUENCE { + cause ENUMERATED { + undefined, + undeliveredAssistanceDataIsNotSupportedByServer, + undeliveredAssistanceDataIsSupportedButCurrentlyNotAvailableByServer, + undeliveredAssistanceDataIsPartlyNotSupportedAndPartlyNotAvailableByServer, + ..., + unconfirmedPeriodicAssistanceDataIsNotSupported-v1510, + unconfirmedPeriodicAssistanceDataIsSupportedButCurrentlyNotAvailable-v1510, + unconfirmedPeriodicAssistanceDataIsPartlyNotSupportedAndPartlyNotAvailable-v1510, + undeliveredPeriodicAssistanceDataIsCurrentlyNotAvailable-v1510 + }, + ... +} + +-- ASN1STOP + +``` + +| GNSS-LocationServerErrorCauses field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

cause
This field provides a GNSS specific error cause. The cause values 'unconfirmedPeriodicAssistanceDataIsNotSupported', 'unconfirmedPeriodicAssistanceDataIsSupportedButCurrentlyNotAvailable' and 'unconfirmedPeriodicAssistanceDataIsPartlyNotSupportedAndPartlyNotAvailable' may only be included in the control transaction of a periodic assistance data transfer procedure, as described in clause 5.2.1a. The cause value 'undeliveredPeriodicAssistanceDataIsCurrentlyNotAvailable' may only be included in the data transaction of a periodic assistance data transfer procedure when periodic assistance data are not available when the periodicity condition occurs, as described in clauses 5.2.1a and 5.2.2a.

| + +## – GNSS-TargetDeviceErrorCauses + +The IE *GNSS-TargetDeviceErrorCauses* is used by the target device to provide GNSS error reasons to the location server. + +``` +-- ASN1START +GNSS-TargetDeviceErrorCauses ::= SEQUENCE { + cause ENUMERATED { undefined, + thereWereNotEnoughSatellitesReceived, + assistanceDataMissing, + notAllRequestedMeasurementsPossible, + ... + }, + fineTimeAssistanceMeasurementsNotPossible NULL OPTIONAL, + adrMeasurementsNotPossible NULL OPTIONAL, + multiFrequencyMeasurementsNotPossible NULL OPTIONAL, + ... + [[ + remoteUE-Indication-r18 ENUMERATED {true} OPTIONAL -- Cond NR + ]] +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------| +| NR | This field is optionally present, need OR, for NR access. Otherwise it is not present. | + +| GNSS-TargetDeviceErrorCauses field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

cause
This field provides a GNSS specific error cause. If the cause value is 'notAllRequestedMeasurementsPossible', the target device was not able to provide all requested GNSS measurements (but may be able to report a location estimate or location measurements). In this case, the target device should include any of the fineTimeAssistanceMeasurementsNotPossible, adrMeasurementsNotPossible, or multiFrequencyMeasurementsNotPossible fields, as applicable.

| +|

remoteUE-Indication
This field indicates whether the target device in NR access is configured as a L2 U2N Remote UE.

| + +## 6.5.2.13 Common GNSS Information Elements + +### – GNSS-FrequencyID + +The IE *GNSS-FrequencyID* is used to indicate a specific GNSS link/frequency. The interpretation of *GNSS-FrequencyID* depends on the *GNSS-ID*. + +``` +-- ASN1START +GNSS-FrequencyID-r15 ::= SEQUENCE { + gnss-FrequencyID-r15 INTEGER (0 .. 7), + ... +} + +-- ASN1STOP +``` + +**GNSS-FrequencyID field descriptions*****gnss-FrequencyID*** + +This field specifies a particular GNSS link/frequency. The interpretation of *gnss-FrequencyID* depends on the *GNSS-ID* and is as shown in the table Value & Explanation relation below. + +**Value & Explanation relation** + +| System | Value | Explanation | | +|-------------------------|-------|-------------|------------------------| +| | | Link | Centre Frequency [MHz] | +| GPS | 0 | L1 | 1575.42 | +| | 1 | L2 | 1227.60 | +| | 2 | L5 | 1176.45 | +| | 3-7 | reserved | | +| SBAS | 0 | L1 | 1575.42 | +| | 1 | L5 | 1176.45 | +| | 2-7 | reserved | | +| QZSS | 0 | L1 | 1575.42 | +| | 1 | L2 | 1227.60 | +| | 2 | L5 | 1176.45 | +| | 3-7 | reserved | | +| GLONASS
$k = -7..13$ | 0 | G1 | $1602+k \times 0.5625$ | +| | 1 | G2 | $1246+k \times 0.4375$ | +| | 2 | G3 | 1202.025 | +| | 3-7 | reserved | | +| Galileo | 0 | E1 | 1575.420 | +| | 1 | E6 | 1278.750 | +| | 2 | E5a | 1176.450 | +| | 3 | E5b | 1207.140 | +| | 4 | E5 | 1191.795 | +| | 5-7 | reserved | | +| BDS | 0 | B1I | 1561.098 | +| | 1 | B1C | 1575.420 | +| | 2 | B2 | 1207.140 | +| | 3 | B3 | 1268.520 | +| | 4 | B2a | 1176.450 | +| | 5-7 | reserved | | +| NavIC | 0 | L5 | 1176.450 | +| | 1-7 | reserved | | + +## GNSS-ID + +The IE *GNSS-ID* is used to indicate a specific GNSS. + +``` +-- ASN1START +GNSS-ID ::= SEQUENCE { + gnss-id ENUMERATED{ gps, sbas, qzss, galileo, glonass, ..., bds, navic-v1610 }, + ... +} +-- ASN1STOP +``` + +## GNSS-ID-Bitmap + +The IE *GNSS-ID-Bitmap* is used to indicate several GNSSs using a bit map. + +``` +-- ASN1START +GNSS-ID-Bitmap ::= SEQUENCE { + gnss-ids BIT STRING { + gps (0), + sbas (1), + qzss (2), + } +} +``` + +``` + + galileo (3), + glonass (4), + bds (5), + navic-v1610 (6) } (SIZE (1..16)), + ... +} + +-- ASN1STOP + +``` + +#### ***GNSS-ID-Bitmap field descriptions*** + +##### ***gnss-ids*** + +This field specifies the GNSS(s). This is represented by a bit string, with a one-value at the bit position means the particular GNSS is addressed; a zero-value means not addressed. + +### — ***GNSS-Link-CombinationsList*** + +``` + +-- ASN1START + +GNSS-Link-CombinationsList-r15 ::= SEQUENCE (SIZE(1..8)) OF GNSS-Link-Combinations-r15 + +GNSS-Link-Combinations-r15 ::= SEQUENCE { + l1-r15 GNSS-FrequencyID-r15, + l2-r15 GNSS-FrequencyID-r15, + ... +} + +-- ASN1STOP + +``` + +### — ***GNSS-NavListInfo*** + +``` + +-- ASN1START + +GNSS-NavListInfo-r15 ::= SEQUENCE (SIZE (1..64)) OF SatListElement-r15 + +SatListElement-r15 ::= SEQUENCE { + svID-r15 SV-ID, + iod-r15 BIT STRING (SIZE(11)), + ... +} + +-- ASN1STOP + +``` + +### — ***GNSS-NetworkID*** + +The IE *GNSS-NetworkID* defines the reference network and the source of the particular set of reference stations and their observation information. This IE is used for MAC Network RTK as described in [30]. + +``` + +-- ASN1START + +GNSS-NetworkID-r15 ::= SEQUENCE { + networkID-r15 INTEGER (0..255), + ... +} + +-- ASN1STOP + +``` + +### — ***GNSS-PeriodicControlParam*** + +The IE *GNSS-PeriodicControlParam* is used to specify control parameters for a periodic assistance data delivery. + +``` + +-- ASN1START + +GNSS-PeriodicControlParam-r15 ::= SEQUENCE { + deliveryAmount-r15 INTEGER (1..32), + deliveryInterval-r15 INTEGER (1..64), + ... +} + +``` + +``` + +} +-- ASN1STOP + +``` + +#### GNSS-PeriodicControlParam field descriptions + +##### **deliveryAmount** + +This field specifies the number of periodic assistance data deliveries. Integer values $N=1\dots31$ correspond to an amount of $2^N$ . Integer value $N=32$ indicates an 'infinite/indefinite' amount, which means that the assistance data delivery should continue until a LPP *Abort* message is received. + +##### **deliveryInterval** + +This field specifies the interval between assistance data deliveries in seconds. + +### – GNSS-ReferenceStationID + +The IE *GNSS-ReferenceStationID* is used to identify a specific GNSS Reference Station. + +``` + +-- ASN1START + +GNSS-ReferenceStationID-r15 ::= SEQUENCE { + referenceStationID-r15 INTEGER (0..65535), + providerName-r15 VisibleString (SIZE (1..32)) OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP + +``` + +#### GNSS-ReferenceStationID field descriptions + +##### **referenceStationID** + +This field provides the reference station identity. + +##### **providerName** + +This field is associated with a GNSS correction data provider to ensure that the *referenceStationID*'s are unique from a target device perspective. + +### – GNSS-SignalID + +The IE *GNSS-SignalID* is used to indicate a specific GNSS signal type. The interpretation of *GNSS-SignalID* depends on the *GNSS-ID*. + +``` + +-- ASN1START + +GNSS-SignalID ::= SEQUENCE { + gnss-SignalID INTEGER (0 .. 7), + ... + [[ + gnss-SignalID-Ext-r15 INTEGER (8..23) OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP + +``` + +#### GNSS-SignalID field descriptions + +##### **gnss-SignalID, gnss-SignalID-Ext** + +This field specifies a particular GNSS signal. The interpretation of *gnss-SignalID* and *gnss-SignalID-Ext* depends on the *GNSS-ID* and is as shown in the table System to Value & Explanation relation below. + +If the field *gnss-SignalID-Ext* is present, the *gnss-SignalID* should be set to value 7 and shall be ignored by the receiver. + +#### System to Value & Explanation relation + +| System | Value | Explanation | +|--------|-------|-------------| +| GPS | 0 | GPS L1 C/A | +| | 1 | GPS L1C | +| | 2 | GPS L2C | + +| | | | +|------|-------|-------------------| +| SBAS | 3 | GPS L5 | +| | 4 | GPS L1 P | +| | 5 | GPS L1 Z-tracking | +| | 6 | GPS L2 C/A | +| | 7 | GPS L2 P | +| | 8 | GPS L2 Z-tracking | +| | 9 | GPS L2 L2C(M) | +| | 10 | GPS L2 L2C(L) | +| | 11 | GPS L2 L2C(M+L) | +| | 12 | GPS L5 I | +| | 13 | GPS L5 Q | +| | 14 | GPS L5 I+Q | +| | 15 | GPS L1 L1C(D) | +| | 16 | GPS L1 L1C(P) | +| | 17 | GPS L1 L1C(D+P) | +| | 18-23 | Reserved | +| | 0 | L1 C/A | +| | 1 | L5 I | +| | 2 | L5 Q | +| | 3 | L5 I+Q | +| | 4-7 | Reserved | +| QZSS | 0 | QZS-L1 C/A | +| | 1 | QZS-L1C | +| | 2 | QZS-L2C | +| | 3 | QZS-L5 | +| | 4 | QZS-LEX S | +| | 5 | QZS-LEX L | +| | 6 | QZS-LEX S+L | +| | 7 | QZS-L2 L2C(M) | +| | 8 | QZS-L2 L2C(L) | +| | 9 | QZS-L2 L2C(M+L) | +| | 10 | QZS-L5 I | +| | 11 | QZS-L5 Q | +| | 12 | QZS-L5 I+Q | +| | 13 | QZS L1 L1C(D) | +| | 14 | QZS L1 L1C(P) | +| | 15 | QZS L1 L1C(D+P) | +| | 16-23 | Reserved | + +| | | | +|---------|-------|------------------------------| +| GLONASS | 0 | GLONASS G1 C/A | +| | 1 | GLONASS G2 C/A | +| | 2 | GLONASS G3 | +| | 3 | GLONASS G1 P | +| | 4 | GLONASS G2 P | +| | 5 | GLONASS G1a(D) | +| | 6 | GLONASS G1a(P) | +| | 7 | GLONASS G1a (D+P) | +| | 8 | GLONASS G2a(I) | +| | 9 | GLONASS G2a(P) | +| | 10 | GLONASS G2a(I+P) | +| | 11 | GLONASS G3 I | +| | 12 | GLONASS G3 Q | +| | 13 | GLONASS G3 I+Q | +| | 14-23 | Reserved | +| Galileo | 0 | Galileo E1 | +| | 1 | Galileo E5A | +| | 2 | Galileo E5B | +| | 3 | Galileo E6 | +| | 4 | Galileo E5A + E5B | +| | 5 | Galileo E1 C No data | +| | 6 | Galileo E1 A | +| | 7 | Galileo E1 B I/NAV OS/CS/SOL | +| | 8 | Galileo E1 B+C | +| | 9 | Galileo E1 A+B+C | +| | 10 | Galileo E6 C | +| | 11 | Galileo E6 A | +| | 12 | Galileo E6 B | +| | 13 | Galileo E6 B+C | +| | 14 | Galileo E6 A+B+C | +| | 15 | Galileo E5B I | +| | 16 | Galileo E5B Q | +| | 17 | Galileo E5B I+Q | +| | 18 | Galileo E5(A+B) I | +| | 19 | Galileo E5(A+B) Q | +| | 20 | Galileo E5(A+B) I+Q | +| | 21 | Galileo E5A I | +| | 22 | Galileo E5A Q | +| | 23 | Galileo E5A I+Q | +| BDS | 0 | B1 I | +| | 1 | B1 Q | +| | 2 | B1 I+Q | +| | 3 | B3 I | +| | 4 | B3 Q | +| | 5 | B3 I+Q | +| | 6 | B2 I | +| | 7 | B2 Q | +| | 8 | B2 I+Q | +| | 9 | B1C(D) | +| | 10 | B1C(P) | +| | 11 | B1C(D+P) | +| | 12 | B2a(D) | +| | 13 | B2a(P) | +| | 14 | B2a(D+P) | +| | 15-23 | Reserved | +| NavIC | 0 | NavIC L5 SPS | +| | 1-23 | Reserved | + +## – GNSS-SignalIDs + +The IE *GNSSSignal-IDs* is used to indicate several GNSS signals using a bit map. The interpretation of *GNSSSignal-IDs* depends on the *GNSS-ID*. + +``` + +-- ASN1START + +GNSS-SignalIDs ::= SEQUENCE { + gnss-SignalIDs BIT STRING (SIZE(8)), + ... + [[ + gnss-SignalIDs-Ext-r15 BIT STRING (SIZE(16)) OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP + +``` + +#### GNSS-SignalIDs field descriptions + +##### *gnss-SignalIDs, gnss-SignalIDs-Ext* + +This field specifies one or several GNSS signals using a bit map. A one-value at the bit position means the particular signal is addressed; a zero-value at the particular bit position means the signal is not addressed. The interpretation of the bit map in *gnssSignalIDs* and *gnss-SignalIDs-Ext* depends on the *GNSS-ID* and is shown in the table below. Unfilled table entries indicate no assignment and shall be set to zero. + +#### Interpretation of the bit map in *gnssSignalIDs* + +| GNSS | Bit 1 (MSB) | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 (LSB) | +|---------|-------------|---------|---------|--------|---------|--------------|---------|----------------------| +| GPS | L1 C/A | L1C | L2C | L5 | L1P | L1 Z | L2 C/A | L2 P | +| SBAS | L1 C/A | L5 I | L5 Q | L5 I+Q | | | | | +| QZSS | QZS-L1 C/A | QZS-L1C | QZS-L2C | QZS-L5 | LEX S | LEX L | LEX S+L | L2C(M) | +| GLONASS | G1 C/A | G2 C/A | G3 | G1 P | G2 P | G1a(D) | G1a(P) | G1a(D+P) | +| Galileo | E1 | E5a | E5b | E6 | E5a+E5b | E1 C No Data | E1 A | E1 B I/NAV OS/CS/SoL | +| BDS | B1 I | B1 Q | B1 I+Q | B3 I | B3 Q | B3 I+Q | B2 I | B2 Q | +| NavIC | L5 SPS | | | | | | | | + +#### Interpretation of the bit map in *gnssSignalIDs-Ext* + +| GNSS | Bit 1 (MSB) | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | +|---------|-------------|----------|----------|----------|--------|---------|----------|----------| +| GPS | L2 Z | L2C(M) | L2C(L) | L2C(M+L) | L5 I | L5 Q | L5 I+Q | L1C(D) | +| SBAS | | | | | | | | | +| QZSS | L2C(L) | L2C(M+L) | L5 I | L5 Q | L5 I+Q | L1C(D) | L1C(P) | L1C(D+P) | +| GLONASS | G2a(I) | G2a(P) | G2a(I+P) | G3 I | G3 Q | G3(I+Q) | | | +| Galileo | E1 B+C | E1 A+B+C | E6C | E6A | E6B | E6 B+C | E6 A+B+C | E5B I | +| BDS | B2 I+Q | B1C(D) | B1C(P) | B1C(D+P) | B2a(D) | B2a(P) | B2a(D+P) | | +| NavIC | | | | | | | | | + +| GNSS | Bit 9 | Bit 10 | Bit 11 | Bit 12 | Bit 13 | Bit 14 | Bit 15 | Bit 16 (LSB) | +|---------|--------|----------|-----------|-----------|-------------|--------|--------|--------------| +| GPS | L1C(P) | L1C(D+P) | | | | | | | +| SBAS | | | | | | | | | +| QZSS | | | | | | | | | +| GLONASS | | | | | | | | | +| Galileo | E5B Q | E5B I+Q | E5(A+B) I | E5(A+B) Q | E5(A+B) I+Q | E5A I | E5A Q | E5A I+Q | +| BDS | | | | | | | | | +| NavIC | | | | | | | | | + +#### GNSS-SubNetworkID + +The IE *GNSS-SubNetworkID* defines the subnetwork of a network identified by *GNSS-NetworkID*. This IE is used for MAC Network RTK as described in [30]. + +``` +-- ASN1START +GNSS-SubNetworkID-r15 ::= SEQUENCE { + subNetworkID-r15 INTEGER (0..15), + ... +} +-- ASN1STOP +``` + +## – **SBAS-ID** + +The IE *SBAS-ID* is used to indicate a specific SBAS. + +``` +-- ASN1START +SBAS-ID ::= SEQUENCE { + sbas-id ENUMERATED { waas, egnos, msas, gagan, ...}, + ... +} +-- ASN1STOP +``` + +## – **SBAS-IDs** + +The IE *SBAS-IDs* is used to indicate several SBASs using a bit map. + +``` +-- ASN1START +SBAS-IDs ::= SEQUENCE { + sbas-IDs BIT STRING { + waas (0), + egnos (1), + msas (2), + gagan (3) } (SIZE (1..8)), + ... +} +-- ASN1STOP +``` + +### **SBAS-IDs field descriptions** + +#### ***sbas-IDs*** + +This field specifies one or several SBAS(s) using a bit map. A one-value at the bit position means the particular SBAS is addressed; a zero-value at the particular bit position means the SBAS is not addressed. + +## – **SV-ID** + +The IE *SV-ID* is used to indicate a specific GNSS satellite. The interpretation of *SV-ID* depends on the *GNSS-ID*. + +``` +-- ASN1START +SV-ID ::= SEQUENCE { + satellite-id INTEGER (0..63), + ... +} +-- ASN1STOP +``` + +### **SV-ID field descriptions** + +#### ***satellite-id*** + +This field specifies a particular satellite within a specific GNSS. The interpretation of *satellite-id* depends on the *GNSS-ID* see the table below. + +### Interpretation of *satellite-id* + +| System | Value of satellite-id | Interpretation of satellite-id | +|---------|------------------------------|------------------------------------------------------| +| GPS | '0' – '62'
'63' | Satellite PRN Signal No. 1 to 63
Reserved | +| SBAS | '0' – '38'
'39' – '63' | Satellite PRN Signal No. 120 to 158
Reserved | +| QZSS | '0' – '9'
'10' – '63' | Satellite PRN Signal No. 193 to 202
Reserved | +| GLONASS | '0' – '23'
'24' – '63' | Slot Number 1 to 24
Reserved | +| Galileo | '0' – '35'
'36' – '63' | Code No. 1 to 36
Reserved | +| BDS | '0' – '62'
'63' | Satellite ranging code number No.1 to 63
Reserved | +| NavIC | '0' – '13'
'14'–'63' | Satellite PRN Signal No. 1 to 14
Reserved | + +## 6.5.3 Enhanced Cell ID Positioning + +### 6.5.3.1 E-CID Location Information + +#### – *ECID-ProvideLocationInformation* + +The IE *ECID-ProvideLocationInformation* is used by the target device to provide E-CID location measurements to the location server. It may also be used to provide E-CID positioning specific error reason. + +``` +-- ASN1START +ECID-ProvideLocationInformation ::= SEQUENCE { + ecid-SignalMeasurementInformation ECID-SignalMeasurementInformation OPTIONAL, + ecid-Error ECID-Error OPTIONAL, + ... +} + +-- ASN1STOP +``` + +### 6.5.3.2 E-CID Location Information Elements + +#### – *ECID-SignalMeasurementInformation* + +The IE *ECID-SignalMeasurementInformation* is used by the target device to provide various UE-measurements to the location server. + +``` +-- ASN1START +ECID-SignalMeasurementInformation ::= SEQUENCE { + primaryCellMeasuredResults MeasuredResultsElement OPTIONAL, + measuredResultsList MeasuredResultsList, + ... +} + +MeasuredResultsList ::= SEQUENCE (SIZE(1..32)) OF MeasuredResultsElement + +MeasuredResultsElement ::= SEQUENCE { + physCellId INTEGER (0..503), + cellGlobalId CellGlobalIdEUTRA-AndUTRA OPTIONAL, + arfcnEUTRA ARFCN-ValueEUTRA, + systemFrameNumber BIT STRING (SIZE (10)) OPTIONAL, + rsrp-Result INTEGER (0..97) OPTIONAL, + rsrq-Result INTEGER (0..34) OPTIONAL, + ue-RxTxTimeDiff INTEGER (0..4095) OPTIONAL, + ..., + [[ arfcnEUTRA-v9a0 ARFCN-ValueEUTRA-v9a0 OPTIONAL -- Cond EARFCN-max + ]], +``` + +``` + +[[ nrsrp-Result-r14 INTEGER (0..113) OPTIONAL, + nrsrq-Result-r14 INTEGER (0..74) OPTIONAL, + carrierFreqOffsetNB-r14 CarrierFreqOffsetNB-r14 OPTIONAL, -- Cond NB-IoT + hyperSFN-r14 BIT STRING (SIZE (10)) OPTIONAL + ], + [[ + nrsrp-Result-v1470 INTEGER (-17..-1) OPTIONAL, + nrsrq-Result-v1470 INTEGER (-30..46) OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EARFCN-max | The field is mandatory present if the corresponding arfcnEUTRA (i.e. without suffix) is set to maxEARFCN . Otherwise the field is not present. | +| NB-IoT | The field is mandatory present if the measured cell is a NB-IoT cell. Otherwise it is not present. | + +| ECID-SignalMeasurementInformation field descriptions | | +|-------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| primaryCellMeasuredResults | This field contains measurements for the primary cell (if the primary cell is a E-UTRA or NB-IoT cell), when the target device reports measurements for both primary cell (E-UTRA or NB-IoT) and neighbour cells. This field shall be omitted when the target device reports measurements for the primary cell (E-UTRA or NB-IoT) only, in which case the measurements for the primary cell (E-UTRA or NB-IoT) is reported in the measuredResultsList . This field shall be omitted when the primary cell is not a E-UTRA or NB-IoT cell. | +| measuredResultsList | This list contains the E-CID measurements for up to 32 E-UTRA or NB-IoT cells. | +| physCellId | This field specifies the physical cell identity of the measured cell. | +| cellGlobalId | This field specifies cell global ID of the measured cell. The target device shall provide this field if it was able to determine the ECGI of the measured cell at the time of measurement. | +| arfcnEUTRA | This field specifies the ARFCN of the measured E-UTRA carrier frequency, as defined in TS 36.331 [12]. In the case the target device includes arfcnEUTRA-v9a0 , the target device shall set the corresponding arfcnEUTRA (i.e. without suffix) to maxEARFCN . | +| systemFrameNumber | This field specifies the system frame number of the measured cell during which the measurements have been performed. The target device shall include this field if it was able to determine the SFN of the cell at the time of measurement. | +| rsrp-Result | This field specifies the reference signal received power (RSRP) measurement, as defined in TS 36.331 [12], TS 36.214 [17]. In the case the target device includes rsrp-Result-v1470 , the target device shall set the corresponding rsrp-Result (i.e. without suffix) to value 0. | +| rsrq-Result | This field specifies the reference signal received quality (RSRQ) measurement, as defined in TS 36.331 [12], TS 36.214 [17]. In the case the target device includes rsrq-Result-v1470 , the target device shall set the corresponding rsrq-Result (i.e. without suffix) to value 0 or 34. | +| ue-RxTxTimeDiff | This field specifies the UE Rx-Tx time difference measurement, as defined in TS 36.214 [17]. It is provided only for measurements on the UE's primary cell.
Measurement report mapping is according to TS 36.133 [18]. | +| nrsrp-Result | This field specifies the narrowband reference signal received power (NRSRP) measurement, as defined in TS 36.214 [17]. Measurement report mapping is according to TS 36.133 [18]. | +| nrsrq-Result | This field specifies the narrowband reference signal received quality (NRSRQ) measurement, as defined in TS 36.214 [17].
Measurement report mapping to the value defined in TS 36.133 [18]. Values 0..29 map to values NRSRQ_-30..NRSRQ_-1. Values 30..62 map to NRSRQ_01..NRSRQ_33. Values 63..74 map to NRSRQ_35..NRSRQ_46. The UE does not report NRSRQ_00 nor NRSRQ_34. | +| carrierFreqOffsetNB | This field specifies the offset of the NB-IoT channel number to ARFCN given by arfcnEUTRA as defined in TS 36.101 [21]. | + +**ECID-SignalMeasurementInformation field descriptions****hyperSFN** + +This field specifies the hyper-SFN of the measured cell during which the measurements have been performed. The target device shall include this field if it was able to determine the hyper-SFN of the cell at the time of measurement. + +### 6.5.3.3 E-CID Location Information Request + +#### – *ECID-RequestLocationInformation* + +The IE *ECID-RequestLocationInformation* is used by the location server to request E-CID location measurements from a target device. + +``` +-- ASN1START +ECID-RequestLocationInformation ::= SEQUENCE { + requestedMeasurements BIT STRING { + rsrpReq (0), + rsrqReq (1), + ueRXTxReq (2), + nrsrpReq-r14 (3), + nrsrqReq-r14 (4) } (SIZE(1..8)), + ... +} +-- ASN1STOP +``` + +**ECID-RequestLocationInformation field descriptions****requestedMeasurements** + +This field specifies the E-CID measurements requested. This is represented by a bit string, with a one-value at the bit position means the particular measurement is requested; a zero-value means not requested. + +### 6.5.3.4 E-CID Capability Information + +#### – *ECID-ProvideCapabilities* + +The IE *ECID-ProvideCapabilities* is used by the target device to indicate its capability to support E-CID and to provide its E-CID location capabilities to the location server. + +``` +-- ASN1START +ECID-ProvideCapabilities ::= SEQUENCE { + ecid-MeasSupported BIT STRING { + rsrpSup (0), + rsrqSup (1), + ueRXTxSup (2), + nrsrpSup-r14 (3), + nrsrqSup-r14 (4) } (SIZE(1..8)), + ... + [[ ueRXTxSupTDD-r13 ENUMERATED { true } OPTIONAL + ]], + [[ periodicalReporting-r14 ENUMERATED { supported } OPTIONAL, + triggeredReporting-r14 ENUMERATED { supported } OPTIONAL, + idleStateForMeasurements-r14 ENUMERATED { required } OPTIONAL + ]], + [[ scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupport-r17 OPTIONAL + ]] +} +-- ASN1STOP +``` + +| ECID-Provide-Capabilities field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ecid-MeasSupported
This field specifies the E-CID measurements supported by the target device. This is represented by a bit string, with a one-value at the bit position means the particular measurement is supported; a zero-value means not supported. A zero-value in all bit positions in the bit string means only the basic Cell ID positioning method is supported by the target device.
If the UE Rx-Tx time difference measurement is supported by the target device (i.e., ueRxTxSup field is set to one), it means that the UE supports the UE Rx-Tx time difference measurement reporting via both LPP signaling and RRC signalling.
If a target device doesn't support LPP, the E-SMLC may assume the target device can not report the UE Rx-Tx time difference measurement results via RRC signalling. | +| ueRxTxSupTDD
This field, if present, indicates that any UE Rx-Tx time difference measurement reporting for TDD from the target device includes the NTAdoffset according to TS 36.211 [16], TS 36.214 [17] and uses the UE Rx-Tx time difference measurement report mapping for TDD as specified in TS 36.133 [18]. This field may only be included if the ueRxTxSup field in ecid-MeasSupported is set to value one. | +| periodicalReporting
This field, if present, indicates that the target device supports periodicalReporting of E-CID measurements. If this field is absent, the location server may assume that the target device does not support periodicalReporting in CommonEsRequestLocationInformation . | +| triggeredReporting
This field, if present, indicates that the target device supports triggeredReporting for the cellChange event. If this field is absent, the location server may assume that the target device does not support triggeredReporting in CommonEsRequestLocationInformation . | +| idleStateForMeasurements
This field, if present, indicates that the target device requires idle state to perform E-CID measurements. | +| scheduledLocationRequestSupported
This field, if present, indicates that the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonEsRequestLocationInformation – and the time base(s) supported for the scheduled location time. | + +### 6.5.3.5 E-CID Capability Information Request + +#### – *ECID-RequestCapabilities* + +The IE *ECID-RequestCapabilities* is used by the location server to request E-CID positioning capabilities from a target device. + +``` +-- ASN1START +ECID-RequestCapabilities ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### 6.5.3.6 E-CID Error Elements + +#### – *ECID-Error* + +The IE *ECID-Error* is used by the location server or target device to provide E-CID error reasons to the target device or location server, respectively. + +``` +-- ASN1START +ECID-Error ::= CHOICE { + locationServerErrorCauses ECID-LocationServerErrorCauses, + targetDeviceErrorCauses ECID-TargetDeviceErrorCauses, + ... +} +-- ASN1STOP +``` + +### – ***ECID-LocationServerErrorCauses*** + +The IE *ECID-LocationServerErrorCauses* is used by the location server to provide E-CID error reasons to the target device. + +``` +-- ASN1START +ECID-LocationServerErrorCauses ::= SEQUENCE { + cause ENUMERATED { undefined, + ... + }, + ... +} +-- ASN1STOP +``` + +### – ***ECID-TargetDeviceErrorCauses*** + +The IE *ECID-TargetDeviceErrorCauses* is used by the target device to provide E-CID error reasons to the location server. + +``` +-- ASN1START +ECID-TargetDeviceErrorCauses ::= SEQUENCE { + cause ENUMERATED { undefined, + requestedMeasurementNotAvailable, + notAllRequestedMeasurementsPossible, + ... + }, + rsrpMeasurementNotPossible NULL OPTIONAL, + rsrqMeasurementNotPossible NULL OPTIONAL, + ueRxBxMeasurementNotPossible NULL OPTIONAL, + ..., + [[ + nrsrpMeasurementNotPossible-r14 NULL OPTIONAL, + nrsrqMeasurementNotPossible-r14 NULL OPTIONAL + ]] +} +-- ASN1STOP +``` + +#### ***ECID-TargetDeviceErrorCauses* field descriptions** + +##### ***cause*** + +This field provides a E-CID specific error cause. If the cause value is 'notAllRequestedMeasurementsPossible', the target device was not able to provide all requested E-CID measurements (but may be able to provide some measurements). In this case, the target device should include any of the *rsrpMeasurementNotPossible*, *rsrqMeasurementNotPossible*, *ueRxBxMeasurementNotPossible*, *nrsrpMeasurementNotPossible*, or *nrsrqMeasurementNotPossible* fields, as applicable. + +## 6.5.4 Terrestrial Beacon System Positioning + +### 6.5.4.1 TBS Location Information + +#### – ***TBS-ProvideLocationInformation*** + +The IE *TBS-ProvideLocationInformation* is used by the target device to provide TBS location measurements to the location server. It may also be used to provide TBS positioning specific error reason. + +``` +-- ASN1START +TBS-ProvideLocationInformation-r13 ::= SEQUENCE { + tbs-MeasurementInformation-r13 TBS-MeasurementInformation-r13 OPTIONAL, + tbs-Error-r13 TBS-Error-r13 OPTIONAL, + ... +} +``` + +``` +-- ASN1STOP +``` + +## 6.5.4.2 TBS Location Information Elements + +### – *TBS-MeasurementInformation* + +The IE *TBS-MeasurementInformation* is used by the target device to provide TBS location measurements to the location server. + +``` +-- ASN1START +``` + +``` +TBS-MeasurementInformation-r13 ::= SEQUENCE { + measurementReferenceTime-r13 UTCTime OPTIONAL, + mbs-SgnMeasList-r13 MBS-BeaconMeasList-r13 OPTIONAL, -- Cond MBS + ... +} +``` + +``` +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| MBS | The field is mandatory present if the TBS-MeasurementInformation is provided for an MBS system; otherwise it is not present. | + +| TBS-MeasurementInformation field descriptions | | +|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| measurementReferenceTime | This field provides the UTC time when the TBS measurements are performed and should take the form of YYMMDDhhmmssZ. | +| mbs-SgnMeasList | This field provides the MBS measurements for up to 64 MBS beacons. | + +### – *MBS-BeaconMeasList* + +The IE *MBS-BeaconMeasList* is used by the target device to provide MBS location measurements to the location server, as defined in the MBS ICD [24]. + +``` +-- ASN1START +``` + +``` +MBS-BeaconMeasList-r13 ::= SEQUENCE (SIZE(1..64)) OF MBS-BeaconMeasElement-r13 +``` + +``` +MBS-BeaconMeasElement-r13 ::= SEQUENCE { + transmitterID-r13 INTEGER (0..32767), + codePhase-r13 INTEGER (0..2097151), + codePhaseRMSError-r13 INTEGER (0..63), + ... + [[ rssi-r14 INTEGER (-130..-30) OPTIONAL + ]] +} +``` + +``` +-- ASN1STOP +``` + +| MBS-BeaconMeasList field descriptions | | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| transmitterID | This field contains the MBS transmitter identifier. | +| codePhase | This field contains the value of the code-phase measurement made by the target device for the particular beacon signal at the time of measurement in the units of ms. MBS specific code phase measurements (e.g. chips) are converted into unit of ms by dividing the measurements by the nominal values of the measured signal chipping rate. Scale factor $2^{21}$ milli-seconds, in the range from 0 to $(1-2^{21})$ milli-seconds. | +| codePhaseRMSError | This field contains the pseudorange RMS error value. This parameter is specified according to a floating-point representation shown in the table below. | + +| MBS-BeaconMeasList field descriptions | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| rssi
This field provides an estimate of the received signal strength from the MBS beacon as referenced to the UE antenna connector.
If the estimated received signal strength for the MBS beacon is less than -130 dBm, the UE shall report an RSSI value of -130. If the estimated received signal strength for the MBS beacon is greater than -30 dBm, the UE shall report an RSSI value of -30.

Scale factor 1 dBm. | | + +#### floating-point representation + +| Index | Mantissa | Exponent | Floating-Point value, $x_i$ | Pseudorange value, $P$ [m] | +|-------|----------|----------|-----------------------------|----------------------------| +| 0 | 000 | 000 | 0.5 | $P < 0.5$ | +| 1 | 001 | 000 | 0.5625 | $0.5 \leq P < 0.5625$ | +| $i$ | $x$ | $y$ | $0.5 * (1 + x/8) * 2^y$ | $x_{i-1} \leq P < x_i$ | +| 62 | 110 | 111 | 112 | $104 \leq P < 112$ | +| 63 | 111 | 111 | -- | $112 \leq P$ | + +#### 6.5.4.3 TBS Location Information Request + +##### – *TBS-RequestLocationInformation* + +The IE *TBS-RequestLocationInformation* is used by the location server to request location information for TBS-based methods from the target device. + +``` +-- ASN1START +TBS-RequestLocationInformation-r13 ::= SEQUENCE { + mbsSgnMeasListReq-r13 BOOLEAN, + ... + [[ mbsAssistanceAvailability-r14 BOOLEAN OPTIONAL, -- Need ON + mbsRequestedMeasurements-r14 BIT STRING { + rssi (0) } (SIZE(1..8)) OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP +``` + +| TBS-RequestLocationInformation field descriptions | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| mbsSgnMeasListReq
This field indicates whether the target device is requested to report MBS measurements in TBS-MeasurementInformation IE or not. TRUE means requested. | | +| mbsAssistanceAvailability
This field indicates whether the target device may request additional MBS assistance data from the server. TRUE means allowed and FALSE means not allowed. | | +| mbsRequestedMeasurements
This field indicates the additional MBS measurements requested and may only be included if mbsSgnMeasListReq is set to TRUE. This field is represented by a bit string, with a one-value at the bit position means the particular measurement is requested; a zero-value means not requested. The following measurement requests can be included.

rssi: Beacon signal strength at the target | | + +#### 6.5.4.4 TBS Capability Information + +##### – *TBS-ProvideCapabilities* + +The IE *TBS-ProvideCapabilities* is used by the target device to indicate its capability to support TBS and to provide its TBS location capabilities to the location server. + +``` + +-- ASN1START + +TBS-ProvideCapabilities-r13 ::= SEQUENCE { + tbs-Modes-r13 BIT STRING { standalone (0), + ue-assisted (1), + ue-based (2) } (SIZE (1..8)), + ... + [[ mbs-AssistanceDataSupportList-r14 MBS-AssistanceDataSupportList-r14 OPTIONAL, + periodicalReportingSupported-r14 PositioningModes OPTIONAL, + mbs-ConfigSupport-r14 BIT STRING { tb1 (0), + tb2 (1), + tb3 (2), + tb4 (3) } (SIZE (1..8)) OPTIONAL, + mbs-IdleStateForMeasurements-r14 ENUMERATED { required } OPTIONAL + ]], + [[ scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupportPerMode-r17 OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +#### TBS-ProvideCapabilities field descriptions + +##### **tbs-Modes** + +This field specifies the TBS mode(s) supported by the target device. This is represented by a bit string, with a one-value at the bit position means the particular TBS mode is supported; a zero-value means not supported. + +##### **mbs-AssistanceDataSupportList** + +This list defines the MBS assistance data supported by the target device. This field shall be present if the target device supports MBS assistance data. + +##### **periodicalReportingSupported** + +This field, if present, specifies the positioning modes for which the target device supports *periodicalReporting*. This is represented by a bit string, with a one-value at the bit position means *periodicalReporting* for the positioning mode is supported; a zero-value means not supported. If this field is absent, the location server may assume that the target device does not support *periodicalReporting* in *CommonEsRequestLocationInformation*. + +##### **mbs-ConfigSupport** + +This field specifies the MBS configurations supported by the target device. This field shall be present if the target device supports MBS [24]. + +##### **mbs-IdleStateForMeasurements** + +This field, if present, indicates that the target device requires idle state to perform MBS measurements. + +##### **scheduledLocationRequestSupported** + +This field, if present, specifies the positioning modes for which the target device supports scheduled location requests – i.e., supports the IE *ScheduledLocationTime* in IE *CommonEsRequestLocationInformation* – and the time base(s) supported for the scheduled location time for each positioning mode. If this field is absent, the target device does not support scheduled location requests. + +## - MBS-AssistanceDataSupportList + +The IE *MBS-AssistanceDataSupportList* is used by the target device to indicate its capability to support MBS Assistance Data and to provide its capabilities to the location server. + +``` + +-- ASN1START + +MBS-AssistanceDataSupportList-r14 ::= SEQUENCE { + mbs-AcquisitionAssistanceDataSupport-r14 BOOLEAN, + mbs-AlmanacAssistanceDataSupport-r14 BOOLEAN, + ... +} + +-- ASN1STOP + +``` + +#### MBS-AssistanceDataSupportList field descriptions + +##### **mbs-AcquisitionAssistanceDataSupport** + +This field specifies whether the target device supports MBS Acquisition Assistance Data. TRUE means supported. + +##### **mbs-AlmanacAssistanceDataSupport** + +This field specifies whether the target device supports MBS Almanac Assistance Data. TRUE means supported. + +## 6.5.4.5 TBS Capability Information Request + +### – *TBS-RequestCapabilities* + +The IE *TBS-RequestCapabilities* is used by the location server to request TBS positioning capabilities from a target device. + +``` +-- ASN1START + +TBS-RequestCapabilities-r13 ::= SEQUENCE { + ... +} + +-- ASN1STOP +``` + +## 6.5.4.6 TBS Error Elements + +### – *TBS-Error* + +The IE *TBS-Error* is used by the location server or target device to provide TBS error reasons to the target device or location server, respectively. + +``` +-- ASN1START + +TBS-Error-r13 ::= CHOICE { + locationServerErrorCauses-r13 TBS-LocationServerErrorCauses-r13, + targetDeviceErrorCauses-r13 TBS-TargetDeviceErrorCauses-r13, + ... +} + +-- ASN1STOP +``` + +### – *TBS-LocationServerErrorCauses* + +The IE *TBS-LocationServerErrorCauses* is used by the location server to provide error reasons for TBS positioning to the target device. + +``` +-- ASN1START + +TBS-LocationServerErrorCauses-r13 ::= SEQUENCE { + cause-r13 ENUMERATED { undefined, + ..., + assistanceDataNotSupportedByServer-v1420, + assistanceDataSupportedButCurrentlyNotAvailableByServer-v1420 + }, + ... +} + +-- ASN1STOP +``` + +### – *TBS-TargetDeviceErrorCauses* + +The IE *TBS-TargetDeviceErrorCauses* is used by the target device to provide error reasons for TBS positioning to the location server. + +``` +-- ASN1START + +TBS-TargetDeviceErrorCauses-r13 ::= SEQUENCE { + cause-r13 ENUMERATED { undefined, + thereWereNotEnoughMBSBeaconsReceived, + ..., + assistanceDataMissing-v1420 + }, + ... +} + +-- ASN1STOP +``` + +``` +-- ASN1STOP +``` + +| | +|-------------------------------------------------------| +| TBS-TargetDeviceErrorCauses field descriptions | +|-------------------------------------------------------| + +| | +|--------------| +| cause | +|--------------| + +| | +|-------------------------------------------------| +| This field provides a TBS specific error cause. | +|-------------------------------------------------| + +## 6.5.4.7 TBS Assistance Data + +### – *TBS-ProvideAssistanceData* + +The IE *TBS-ProvideAssistanceData* is used by the location server to provide assistance data to assist in position estimation at the UE (e.g. for UE-based mode) and/or to expedite the acquisition of TBS signals. It may also be used to provide TBS positioning specific error reasons. + +``` +-- ASN1START +``` + +``` +TBS-ProvideAssistanceData-r14 ::= SEQUENCE { + tbs-AssistanceDataList-r14 TBS-AssistanceDataList-r14 OPTIONAL, -- Need ON + tbs-Error-r14 TBS-Error-r13 OPTIONAL, -- Need ON + ... +} +``` + +``` +-- ASN1STOP +``` + +## 6.5.4.8 TBS Assistance Data Elements + +### – *TBS-AssistanceDataList* + +The IE *TBS-AssistanceDataList* is used by the location server to provide the TBS specific assistance data to the UE. + +``` +-- ASN1START +``` + +``` +TBS-AssistanceDataList-r14 ::= SEQUENCE { + mbs-AssistanceDataList-r14 MBS-AssistanceDataList-r14 OPTIONAL, -- Need ON + ... +} + +MBS-AssistanceDataList-r14 ::= SEQUENCE (SIZE (1..maxMBS-r14)) OF MBS-AssistanceDataElement-r14 + +MBS-AssistanceDataElement-r14 ::= SEQUENCE { + mbs-AlmanacAssistance-r14 MBS-AlmanacAssistance-r14 OPTIONAL, -- Need ON + mbs-AcquisitionAssistance-r14 MBS-AcquisitionAssistance-r14 OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP +``` + +### – *MBS-AlmanacAssistance* + +The IE *MBS-AlmanacAssistance* is used by the location server to provide LLA of MBS transmitters to enable position estimation at the UE. + +``` +-- ASN1START +``` + +``` +MBS-AlmanacAssistance-r14 ::= SEQUENCE { + transmitterID-r14 INTEGER (0..32767), + transmitterLatitude-r14 BIT STRING (SIZE (26)), + transmitterLongitude-r14 BIT STRING (SIZE (27)), + transmitterAltitude-r14 BIT STRING (SIZE (15)), + timeCorrection-r14 INTEGER (0..25) OPTIONAL, -- Need ON + ... +} +``` + +``` +-- ASN1STOP +``` + +| MBS-AlmanacAssistance field descriptions | | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| transmitterID | This field specifies the MBS transmitter ID [24]. | +| transmitterLatitude | This field specifies latitude of the MBS transmitter, degrees. Scale factor $4/2^{20}$ decimal degrees, added to $-90^\circ$ . Valid range $-90^\circ$ to $90^\circ$ [24]. | +| transmitterLongitude | This field specifies longitude of the MBS transmitter, degrees. Scale factor $4/2^{20}$ decimal degrees, added to $-180^\circ$ . Valid range $-180^\circ$ to $180^\circ$ [24]. | +| transmitterAltitude | This field specifies altitude of the MBS transmitter, metres. Scale factor 0.29 metres, added to -500 metres. Valid range -500 to 9002.43 metres [24]. | +| timeCorrection | This field contains the residual timing error for a particular beacon, in units of nano-seconds, in the range from 0 to 25. This field is used for UE-based mode only, by subtracting from the codePhase measurement made by the target device [24]. | + +## – **MBS-AcquisitionAssistance** + +The IE *MBS-AcquisitionAssistance* is used by the location server to provide parameters that support acquisition of the MBS signals [24]. + +``` +-- ASN1START +MBS-AcquisitionAssistance-r14 ::= SEQUENCE { + transmitterID-r14 INTEGER (0..32767) OPTIONAL, -- Need ON + mbsConfiguration-r14 ENUMERATED {tb1, tb2, tb3, tb4, ...} OPTIONAL, -- Need ON + pnCodeIndex-r14 INTEGER (1..128) OPTIONAL, -- Need ON + freq-r14 INTEGER (919750000..927250000) OPTIONAL, -- Need ON + ... +} +-- ASN1STOP +``` + +| MBS-AcquisitionAssistance field descriptions | | +|-----------------------------------------------------|---------------------------------------------------------------------------| +| transmitterID | This field contains the MBS transmitter identifier [24]. | +| mbsConfiguration | This field specifies MBS configuration as defined in the MBS ICD [24]. | +| pnCodeIndex | This field specifies the index of the MBS PN code [24]. | +| freq | This field specifies the MBS signal centre frequency in units of Hz [24]. | + +## 6.5.4.9 TBS Assistance Data Request + +### – **TBS-RequestAssistanceData** + +The IE *TBS-RequestAssistanceData* is used by the target device to request TBS assistance data from a location server. + +``` +-- ASN1START +TBS-RequestAssistanceData-r14 ::= SEQUENCE { + mbs-AlmanacAssistanceDataReq-r14 BOOLEAN, + mbs-AcquisitionAssistanceDataReq-r14 BOOLEAN, + ... +} +-- ASN1STOP +``` + +## 6.5.5 Sensor based Positioning + +### 6.5.5.0 Introduction + +This clause defines support for sensor-based positioning. The supported sensor methods are "Barometric pressure sensor" and "Motion sensor" as described in TS 36.305, clauses 8.6 and 8.10 respectively [2]. + +#### 6.5.5.1 Sensor Location Information + +##### – *Sensor-ProvideLocationInformation* + +The IE *Sensor-ProvideLocationInformation* is used by the target device to provide location information for sensor-based methods to the location server. It may also be used to provide sensor specific error reason. + +``` +-- ASN1START +Sensor-ProvideLocationInformation-r13 ::= SEQUENCE { + sensor-MeasurementInformation-r13 Sensor-MeasurementInformation-r13 OPTIONAL, + sensor-Error-r13 Sensor-Error-r13 OPTIONAL, + .... + [[ + sensor-MotionInformation-r15 Sensor-MotionInformation-r15 OPTIONAL + ]] +} +-- ASN1STOP +``` + +#### 6.5.5.2 Sensor Location Information Elements + +##### – *Sensor-MeasurementInformation* + +The IE *Sensor-MeasurementInformation* is used by the target device to provide UE sensor measurements to the location server. + +``` +-- ASN1START +Sensor-MeasurementInformation-r13 ::= SEQUENCE { + measurementReferenceTime-r13 UTCTime OPTIONAL, + uncompensatedBarometricPressure-r13 INTEGER (30000..115000) OPTIONAL, -- Cond Barometer + .... + [[ + uncertainty-r14 SEQUENCE { + range-r14 INTEGER (0..1000), + confidence-r14 INTEGER (1..100) + } + OPTIONAL + ]], + [[ + adjustment-r16 INTEGER (-5000..5000) OPTIONAL + ]] +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Barometer | The field is mandatory present if the Sensor-MeasurementInformation is provided for barometric pressure; otherwise it is not present. | + +| Sensor-MeasurementInformation field descriptions | | +|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| measurementReferenceTime | This field provides the UTC time when the sensor measurements are performed and should take the form of YYMMDDhhmmssZ. | +| uncompensatedBarometricPressure | This field provides the uncompensated barometric pressure as measured by the UE sensor, in units of Pa. | +| uncertainty | This field provides the expected range for the pressure measurement in units of Pa and the confidence as a percentage that the true pressure lies in a range of (measurement – range) to (measurement + range). | +| adjustment | This field provides any adjustment available in the UE, in units of Pa, to allow the production of a compensated atmospheric pressure measurement where $\text{compensated atmospheric pressure} = \text{uncompensatedBarometricPressure} + \text{adjustment}$ | + +## – Sensor-MotionInformation + +The IE *Sensor-MotionInformation* is used by the target device to provide UE movement information to the location server. The movement information comprises an ordered series of points. This information may be obtained by the target device using one or more motion sensors. + +``` +-- ASN1START + +Sensor-MotionInformation-r15 ::= SEQUENCE { + refTime-r15 DisplacementTimeStamp-r15, + displacementInfoList-r15 DisplacementInfoList-r15, + ... +} + +DisplacementInfoList-r15 ::= SEQUENCE (SIZE (1..128)) OF DisplacementInfoListElement-r15 + +DisplacementInfoListElement-r15 ::= SEQUENCE { + deltaTimeStamp-r15 DeltaTime-r15, + displacement-r15 Displacement-r15 OPTIONAL, + ... +} + +DisplacementTimeStamp-r15 ::= CHOICE { + utcTime-r15 UTC-Time-r15, + gnssTime-r15 MeasurementReferenceTime, + systemFrameNumber-r15 SFN-r15, + measurementSFN-r15 INTEGER(-8192..9214), + ... +} + +DeltaTime-r15 ::= CHOICE { + deltaTimeSec-r15 INTEGER (1..16384), + deltaTimeSFN-r15 INTEGER (1..4096), + ... +} + +SFN-r15 ::= SEQUENCE { + sfn-r15 BIT STRING (SIZE (10)), + hyperSFN-r15 BIT STRING (SIZE (10)) OPTIONAL, + ... +} + +Displacement-r15 ::= SEQUENCE { + bearing-r15 INTEGER (0..3599), + bearingUncConfidence-r15 INTEGER (0..100) OPTIONAL, + bearingRef-r15 ENUMERATED { geographicNorth, magneticNorth, local }, + horizontalDistance-r15 INTEGER (0..8191), + horizontalDistanceUnc-r15 INTEGER (0..255) OPTIONAL, + horizontalUncConfidence-r15 INTEGER (0..100) OPTIONAL, + verticalDirection-r15 ENUMERATED{upward, downward} OPTIONAL, + verticalDistance-r15 INTEGER (0..8191) OPTIONAL, + verticalDistanceUnc-r15 INTEGER (0..255) OPTIONAL, + verticalUncConfidence-r15 INTEGER (0..100) OPTIONAL, + ... +} + +UTC-Time-r15 ::= SEQUENCE { + utcTime-r15 UTCTime, + utcTime-ms-r15 INTEGER (0..999), + ... +} +``` + +``` + +} +-- ASN1STOP + +``` + +| Sensor-MotionInformation field descriptions | | +|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| refTime | This field provides the reference time $t_0$ associated with the starting position of the first displacement in the displacement list. | +| displacementInfoList | This field provides an ordered series of direction and distance travelled by the target device and comprises the following subfields:
  • - deltaTimeStamp specifies the time between t_{n-1} and t_n, where n corresponds to the order of entry in the DisplacementInfoList (n=0 correspond to the time provided in refTime).
  • - displacement provides the direction and distance travelled between time t_{n-1} and t_n.
| +| utcTime | This field provides the time stamp of the refTime in UTC time and comprises the following subfields:
  • - utcTime in the form of YYMMDDhhmmssZ.
  • - utcTime-ms specifies the fractional part of the UTC time in ms resolution.
| +| gnssTime | This field provides the time stamp of the refTime in GNSS time. | +| systemFrameNumber | This field provides the time stamp of the refTime in serving cell SFN time. | +| measurementSFN | This field provides the time stamp of the refTime in form of the measurement SFN as defined in delta-SFN in IE OTDOA-SignalMeasurementInformation . This field may be included when OTDOA measurements are included. | +| deltaTimeSec | This field provides the time between $t_{n-1}$ and $t_n$ in units of milliseconds. | +| deltaTimeSFN | This field provides the time between $t_{n-1}$ and $t_n$ in units of system frame numbers. | +| bearing | This field specifies the direction (heading) of the horizontal displacement measured clockwise from bearingRef . Scale factor 0.1 degree. | +| bearingRef | This field specifies the reference direction for the bearing . Enumerated value ' geographicNorth ' indicates that the bearing is measured clockwise from the Geographic North; ' magneticNorth ' indicates that the bearing is measured clockwise from the Magnetic North; ' local ' indicates that the bearing is measured clockwise from an arbitrary (undefined) reference direction. | +| horizontalDistance | This field specifies the horizontal distance travelled between time $t_{n-1}$ and $t_n$ . Scale factor 1 cm. | +| horizontalDistanceUnc, horizontalUncConfidence | This field specifies the horizontal uncertainty of the displacement (corresponding to $t_n$ ). horizontalDistanceUnc correspond to the encoded high accuracy uncertainty as defined in TS 23.032 [15]. horizontalUncConfidence corresponds to confidence as defined in TS 23.032 [15]. | +| verticalDistance | This field specifies the vertical distance travelled between time $t_{n-1}$ and $t_n$ . Scale factor 1 cm. | +| verticalDistanceUnc, verticalUncConfidence | This field specifies the vertical uncertainty of the displacement (corresponding to $t_n$ ). verticalDistanceUnc correspond to the encoded high accuracy uncertainty as defined in TS 23.032 [15]. verticalUncConfidence corresponds to confidence as defined in TS 23.032 [15]. | + +### 6.5.5.3 Sensor Location Information Request + +#### — *Sensor-RequestLocationInformation* + +The IE *Sensor-RequestLocationInformation* is used by the location server to request location information for sensor-based methods from a target device. + +``` + +-- ASN1START + +Sensor-RequestLocationInformation-r13 ::= SEQUENCE { + uncompensatedBarometricPressureReq-r13 BOOLEAN, + ... + [[ assistanceAvailability-r14 BOOLEAN OPTIONAL -- Need ON + ]], + [[ sensor-MotionInformationReq-r15 BOOLEAN OPTIONAL -- Need ON + ]]] + +``` + +``` + + ]], + [[ adjustmentReq-r16 BOOLEAN OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP + +``` + +| Sensor-RequestLocationInformation field descriptions | | +|-------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| uncompensatedBarometricPressureReq | This field indicates whether the target device is requested to report Barometric pressure measurements in Sensor-MeasurementInformation IE or not. TRUE means requested. | +| assistanceAvailability | This field indicates whether the target device may request additional Sensor assistance data from the server. TRUE means allowed and FALSE means not allowed. | +| sensor-MotionInformationReq | This field indicates whether the target device is requested to report movement information in IE Sensor-MotionInformation or not. TRUE means requested. | +| adjustmentReq | This field indicates whether the target device is requested to report adjustment in IE Sensor-MeasurementInformation or not. TRUE means requested. | + +## 6.5.5.4 Sensor Capability Information + +### – *Sensor-ProvideCapabilities* + +The IE *Sensor-ProvideCapabilities* is used by the target device to provide capabilities for sensor-based methods from to the location server. + +``` + +-- ASN1START + +Sensor-ProvideCapabilities-r13 ::= SEQUENCE { + sensor-Modes-r13 BIT STRING { standalone (0), + ue-assisted (1), + ue-based (2) } (SIZE (1..8)), + .... + [[ sensor-AssistanceDataSupportList-r14 Sensor-AssistanceDataSupportList-r14 OPTIONAL, + periodicalReportingSupported-r14 PositioningModes OPTIONAL, + idleStateForMeasurements-r14 ENUMERATED { required } OPTIONAL + ]], + [[ sensor-MotionInformationSup-r15 ENUMERATED { true } OPTIONAL + ]], + [[ adjustmentSupported-r16 ENUMERATED { true } OPTIONAL + ]], + [[ scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupportPerMode-r17 OPTIONAL + ]] +} + +Sensor-AssistanceDataSupportList-r14 ::= SEQUENCE { + .... + [[ validityPeriodSupported-v1520 ENUMERATED { true } OPTIONAL, + validityAreaSupported-v1520 ENUMERATED { true } OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +| Sensor-ProvideCapabilities field descriptions | | +|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sensor-Modes | This field specifies the sensor mode(s) supported by the target device. This is represented by a bit string, with a one-value at the bit position means the particular sensor mode is supported; a zero-value means not supported. | +| sensor-AssistanceDataSupportList | This field specifies a list of sensor assistance data supported by the target device. This field shall be present if the target device supports assistance data for Barometric pressure sensor. | +| validityPeriodSupported | This field, if present, indicates that the target device supports period i.e. pressure validity period and pressure rate as part of the Sensor-AssistanceDataList . | + +| Sensor-ProvideCapabilities field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| validityAreaSupported
This field, if present, indicates that the target device supports area i.e. pressure validity area and North/East pressure gradient as part of the Sensor-AssistanceDataList . | +| periodicalReportingSupported
This field, if present, specifies the positioning modes for which the target device supports periodicalReporting . This is represented by a bit string, with a one-value at the bit position means periodicalReporting for the positioning mode is supported; a zero-value means not supported. If this field is absent, the location server may assume that the target device does not support periodicalReporting in CommonIEsRequestLocationInformation . | +| idleStateForMeasurements
This field, if present, indicates that the target device requires idle state to perform sensor measurements. | +| sensor-MotionInformationSup
This field, if present, indicates that the target device supports displacement reporting in IE Sensor-MotionInformation . | +| adjustmentSupported
This field, if present, indicates that the target device supports the adjustment IE in Sensor-MeasurementInformation . | +| scheduledLocationRequestSupported
This field, if present, specifies the positioning modes for which the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonIEsRequestLocationInformation – and the time base(s) supported for the scheduled location time for each positioning mode. If this field is absent, the target device does not support scheduled location requests. | + +### 6.5.5.5 Sensor Capability Information Request + +#### – *Sensor-RequestCapabilities* + +The IE *Sensor-RequestCapabilities* is used by the location server to request capabilities for sensor-based methods from the target device. + +``` +-- ASN1START +Sensor-RequestCapabilities-r13 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### 6.5.5.6 Sensor Error Elements + +#### – *Sensor-Error* + +The IE *Sensor-Error* is used by the location server or target device to provide Sensor Error Reasons to the target device or location server, respectively. + +``` +-- ASN1START +Sensor-Error-r13 ::= CHOICE { + locationServerErrorCauses-r13 Sensor-LocationServerErrorCauses-r13, + targetDeviceErrorCauses-r13 Sensor-TargetDeviceErrorCauses-r13, + ... +} +-- ASN1STOP +``` + +#### – *Sensor-LocationServerErrorCauses* + +The IE *Sensor-LocationServerErrorCauses* is used by the location server to provide error reasons for Sensor positioning to the target device. + +``` +-- ASN1START +Sensor-LocationServerErrorCauses-r13 ::= SEQUENCE { + cause-r13 ENUMERATED { undefined, + ... + assistanceDataNotSupportedByServer-v1420, +``` + +``` + + assistanceDataSupportedButCurrentlyNotAvailableByServer-v1420 + }, + ... +} + +-- ASN1STOP + +``` + +### – ***Sensor-TargetDeviceErrorCauses*** + +The IE *Sensor-TargetDeviceErrorCauses* is used by the target device to provide error reasons for Sensor positioning to the location server. + +``` + +-- ASN1START + +Sensor-TargetDeviceErrorCauses-r13 ::= SEQUENCE { + cause-r13 ENUMERATED { undefined, + ..., + assistanceDataMissing-v1420 + }, + ... +} + +-- ASN1STOP + +``` + +## 6.5.5.7 Sensor Assistance Data + +### – ***Sensor-ProvideAssistanceData*** + +The IE *Sensor-ProvideAssistanceData* is used by the location server to provide assistance data to assist in altitude computation at the UE (e.g. for UE-based mode). It may also be used to provide Sensor positioning specific error reasons. + +``` + +-- ASN1START + +Sensor-ProvideAssistanceData-r14 ::= SEQUENCE { + sensor-AssistanceDataList-r14 Sensor-AssistanceDataList-r14 OPTIONAL, -- Need ON + sensor-Error-r14 Sensor-Error-r13 OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP + +``` + +## 6.5.5.8 Sensor Assistance Data Elements + +### – ***Sensor-AssistanceDataList*** + +The IE *Sensor-AssistanceDataList* is used by the location server to provide the Sensor specific assistance data to the UE. + +``` + +-- ASN1START + +Sensor-AssistanceDataList-r14 ::= SEQUENCE { + refPressure-r14 INTEGER (-20000..10000), + refPosition-r14 EllipsoidPointWithAltitudeAndUncertaintyEllipsoid OPTIONAL, -- Need ON + refTemperature-r14 INTEGER (-64..63) OPTIONAL, -- Need ON + ..., + [[ + period-v1520 SEQUENCE { + pressureValidityPeriod-v1520 PressureValidityPeriod-v1520, + referencePressureRate-v1520 INTEGER (-128..127) OPTIONAL, -- Need ON + ... + } OPTIONAL, -- Need ON + area-v1520 SEQUENCE { + pressureValidityArea-v1520 PressureValidityArea-v1520, + gN-pressure-v1520 INTEGER (-1024..1023) OPTIONAL, -- Need ON + gE-pressure-v1520 INTEGER (-1024..1023) OPTIONAL, -- Need ON + ... + } + ]] +``` + +``` + + } + ]] +} +PressureValidityArea-v1520 ::= SEQUENCE { + centerPoint-v1520 Ellipsoid-Point, + validityAreaWidth-v1520 INTEGER (1..128), + validityAreaHeight-v1520 INTEGER (1..128), + ... +} +PressureValidityPeriod-v1520 ::= SEQUENCE { + beginTime-v1520 GNSS-SystemTime, + beginTimeAlt-v1520 INTEGER (0..2881), + duration-v1520 INTEGER (1..2881), + ... +} +-- ASN1STOP + +``` + +| Sensor-AssistanceDataList field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| refPressure
This field specifies the atmospheric pressure (Pa) nominal at sea level, EGM96 [29] to the target. The scale factor is 1 Pa. The value is added to the nominal pressure of 101325 Pa. | +| refPosition
This field specifies the reference position at which the pressure measurement is made, as an ellipsoid point with altitude and uncertainty ellipsoid. | +| refTemperature
Local temperature measurement at the reference where the pressure measurement is made. The scale factor 1K. The value is added to 273K. | +| period
This field specifies the pressure validity period and reference pressure rate. | +| pressureValidityPeriod
  • - beginTime: this field specifies the start time of the pressure validity period in GNSS System Time.
  • - beginTimeAlt: this field specifies an alternative start time. It may be used by the target device if GNSS-System Time is not available. The alternative start time is relative to the time the message was received. The scale factor is 15 min. The range is from 0 minutes to 43215 minutes = 30 days.
  • - duration: this field specifies the duration of the validity period after the begin time. The scale factor is 15 minutes. The range is from 15 minutes to 43215 minutes = 30 days.
| +| referencePressureRate
This field specifies the rate of change of pressure. When this field is included, the reference pressure applies only at the start of the pressure validity period. The scale factor is 10Pa/hour. | +| area
This field specifies the area within which the provided atmospheric reference pressure is valid and any spatial drift. | +| pressureValidityArea
  • - centerPoint: this field specifies the coordinates of the centre of the rectangular validity area.
  • - validityAreaWidth: this field specifies the width of the rectangular validity area. Width is measured from the centre along the latitude and is measured as the total width of the rectangle. The scale factor is 1km. The range is from 1km to 128km.
  • - validityAreaHeight: this field specifies the height of the rectangular validity area. Height is measured from the centre along the longitude and is measured as the total height of the rectangle. The scale factor is 1km. The range is from 1km to 128km.
If this field is present, refPosition should not be provided by the location server and if provided, shall be ignored by the target device. | +| gN-pressure
This field specifies the northward gradient of the reference pressure calculated from the centre of the pressureValidityArea . The scale factor is 1 Pa/km. If this field is not provided, the gradient is assumed to be zero. | +| gE-pressure
This field specifies the eastward gradient of the reference pressure calculated from the centre of the pressureValidityArea . The scale factor is 1 Pa/km. If this field is not provided, the gradient is assumed to be zero. | + +## 6.5.5.9 Sensor Assistance Data Request + +### – *Sensor-RequestAssistanceData* + +The IE *Sensor-RequestAssistanceData* is used by the target device to request Sensor assistance data from a location server. + +``` +-- ASN1START + +Sensor-RequestAssistanceData-r14 ::= SEQUENCE { + ... +} + +-- ASN1STOP +``` + +## 6.5.6 WLAN-based Positioning + +This clause defines support for positioning using measurements related to WLAN access points. + +### 6.5.6.1 WLAN Location Information + +#### – *WLAN-ProvideLocationInformation* + +The IE *WLAN-ProvideLocationInformation* is used by the target device to provide measurements for one or more WLANs to the location server. It may also be used to provide WLAN positioning specific error reason. + +``` +-- ASN1START + +WLAN-ProvideLocationInformation-r13 ::= SEQUENCE { + wlan-MeasurementInformation-r13 WLAN-MeasurementInformation-r13 OPTIONAL, + wlan-Error-r13 WLAN-Error-r13 OPTIONAL, + ... +} + +-- ASN1STOP +``` + +### 6.5.6.2 WLAN Location Information Elements + +#### – *WLAN-MeasurementInformation* + +``` +-- ASN1START + +WLAN-MeasurementInformation-r13 ::= SEQUENCE { + measurementReferenceTime-r13 UTCTime OPTIONAL, + wlan-MeasurementList-r13 WLAN-MeasurementList-r13 OPTIONAL, + ... +} + +WLAN-MeasurementList-r13 ::= SEQUENCE (SIZE(1..maxWLAN-AP-r13)) OF WLAN-MeasurementElement-r13 + +WLAN-MeasurementElement-r13 ::= SEQUENCE { + wlan-AP-Identifier-r13 WLAN-AP-Identifier-r13, + rssi-r13 INTEGER (-127..128) OPTIONAL, + rtt-r13 WLAN-RTT-r13 OPTIONAL, + apChannelFrequency-r13 INTEGER (0..256) OPTIONAL, + servingFlag-r13 BOOLEAN OPTIONAL, + ... +} + +WLAN-AP-Identifier-r13 ::= SEQUENCE { + bssid-r13 OCTET STRING (SIZE (6)), + ssid-r13 OCTET STRING (SIZE (1..32)) OPTIONAL, + ... +} + +WLAN-RTT-r13 ::= SEQUENCE { + rttValue-r13 INTEGER (0..16777215), + rttUnits-r13 ENUMERATED { + microseconds, + hundredsofnanoseconds, + tensofnanoseconds, + nanoseconds, + tenthsfnanoseconds, + ... }, + rttAccuracy-r13 INTEGER (0..255) OPTIONAL, + ... +} +``` + +``` +-- ASN1STOP +``` + +| WLAN-MeasurementInformation field descriptions | | +|-------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| measurementReferenceTime | This field provides the UTC time when the WLAN measurements are performed and should take the form of YYMMDDhhmmssZ. | +| wlan-MeasurementList | This field provides the WLAN measurements for up to 64 WLAN APs. | +| wlan-AP-Identifier | This field provides the BSSID and optionally the SSID of the wireless network served by the WLAN AP [26]. | +| rssi | This field provides the AP signal strength (RSSI) of a beacon frame, probe response frame or measurement pilot frame measured at the target in dBm as defined in Table 6-7 of [26]. | +| rtt | This field provides the measured round trip time between the target device and WLAN AP and optionally the accuracy expressed as the standard deviation of the delay. Units for each of these are 1000ns, 100ns, 10ns, 1ns, and 0.1ns. | +| apChannelFrequency | This field provides the AP channel number identification of the reported WLAN AP. | +| servingFlag | This parameter indicates whether a set of WLAN AP measurements were obtained for a serving WLAN AP (TRUE) or a non-serving WLAN AP (FALSE). A target device with multiple radio support may indicate more than one type of serving access for the same time instant. | +| rttValue | This field specifies the Round Trip Time (RTT) measurement between the target device and WLAN AP in units given by the field rttUnits . | +| rttUnits | This field specifies the Units for the fields rttValue and rttAccuracy . The available Units are 1000ns, 100ns, 10ns, 1ns, and 0.1ns. | +| rttAccuracy | This field provides the estimated accuracy of the provided rttValue expressed as the standard deviation in units given by the field rttUnits . | + +### 6.5.6.3 WLAN Location Information Request + +#### — *WLAN-RequestLocationInformation* + +The IE *WLAN-RequestLocationInformation* is used by the location server to request WLAN measurements from a target device. + +``` +-- ASN1START +WLAN-RequestLocationInformation-r13 ::= SEQUENCE { + requestedMeasurements-r13 BIT STRING { + rssi (0), + rtt (1) } (SIZE(1..8)), + .... + [[ assistanceAvailability-r14 BOOLEAN OPTIONAL -- Need ON + ]] +} +-- ASN1STOP +``` + +| WLAN-RequestLocationInformation field descriptions | | +|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| requestedMeasurements | This field specifies the WLAN measurements requested. This is represented by a bit string, with a one-value at the bit position means the particular measurement is requested; a zero-value means not requested. The following measurement requests can be included.

rssi: AP signal strength at the target
rtt: Round Trip Time between target and AP | +| assistanceAvailability | This field indicates whether the target device may request additional WLAN assistance data from the server. TRUE means allowed and FALSE means not allowed. | + +## 6.5.6.4 WLAN Capability Information + +### – WLAN-ProvideCapabilities + +The IE *WLAN-ProvideCapabilities* is used by the target device to provide its capabilities for WLAN positioning to the location server. + +``` +-- ASN1START + +WLAN-ProvideCapabilities-r13 ::= SEQUENCE { + wlan-Modes-r13 BIT STRING { standalone (0), + ue-assisted (1), + ue-based (2) } (SIZE (1..8)), + wlan-MeasSupported-r13 BIT STRING { rssi-r13 (0), + rtt-r13 (1) } (SIZE (1..8)), + ... , + [[ wlan-AP-AD-Supported-r14 + BIT STRING { ap-identifier (0), + ap-location (1) } (SIZE (1..8)) + periodicalReportingSupported-r14 PositioningModes + idleStateForMeasurements-r14 ENUMERATED { required } + ]], + [[ scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupportPerMode-r17 OPTIONAL + ]] +} + +-- ASN1STOP +``` + +#### WLAN-ProvideCapabilities field descriptions + +##### **wlan-Modes** + +This field specifies the WLAN mode(s) supported by the target device. This is represented by a bit string, with a one value at the bit position means the WLAN mode is supported; a zero value means not supported. + +##### **wlan-MeasSupported** + +This field specifies the measurements supported by the target device when accessing a WLAN. This is represented by a bit string, with a one-value at the bit position means the particular measurement is supported; a zero-value means not supported. A zero-value in all bit positions in the bit string means only the basic WLAN positioning method is supported by the target device which is reporting of the WLAN identity. The following bits are assigned for the indicated measurements. + +rssi: AP signal strength at the target + rtt: Round Trip Time between target and AP + +##### **wlan-AP-AD-Supported** + +This field specifies the WLAN AP assistance data supported by the target device. This is represented by a bit string, with a one-value at the bit position means the particular assistance data is supported; a zero-value means not supported. A zero-value in all bit positions or absence of this field means no assistance data is supported. The following bits are assigned for the indicated assistance data. + +ap-identifier: WLAN AP identity information + +ap-location: WLAN AP location information + +##### **periodicalReportingSupported** + +This field, if present, specifies the positioning modes for which the target device supports *periodicalReporting*. This is represented by a bit string, with a one value at the bit position means *periodicalReporting* for the positioning mode is supported; a zero value means not supported. If this field is absent, the location server may assume that the target device does not support *periodicalReporting* in *CommonIEsRequestLocationInformation*. + +##### **idleStateForMeasurements** + +This field, if present, indicates that the target device requires idle state to perform WLAN measurements. + +##### **scheduledLocationRequestSupported** + +This field, if present, specifies the positioning modes for which the target device supports scheduled location requests – i.e., supports the IE *ScheduledLocationTime* in IE *CommonIEsRequestLocationInformation* – and the time base(s) supported for the scheduled location time for each positioning mode. If this field is absent, the target device does not support scheduled location requests. + +### 6.5.6.5 WLAN Capability Information Request + +#### – *WLAN-RequestCapabilities* + +The IE *WLAN-RequestCapabilities* is used by the location server to request WLAN positioning capabilities information from a target device. + +``` +-- ASN1START +WLAN-RequestCapabilities-r13 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### 6.5.6.6 WLAN Error Elements + +#### – *WLAN-Error* + +The IE *WLAN-Error* is used by the location server or target device to provide error reasons for WLAN positioning to the target device or location server, respectively. + +``` +-- ASN1START +WLAN-Error-r13 ::= CHOICE { + locationServerErrorCauses-r13 WLAN-LocationServerErrorCauses-r13, + targetDeviceErrorCauses-r13 WLAN-TargetDeviceErrorCauses-r13, + ... +} +-- ASN1STOP +``` + +#### – *WLAN-LocationServerErrorCauses* + +The IE *WLAN-LocationServerErrorCauses* is used by the location server to provide error reasons for WLAN positioning to the target device. + +``` +-- ASN1START +WLAN-LocationServerErrorCauses-r13 ::= SEQUENCE { + cause-r13 ENUMERATED {undefined, + ..., + requestedADNotAvailable-v1420, + notAllrequestedADAvailable-v1420 + }, + ..., + [[ apLocationDataUnavailable-r14 NULL OPTIONAL -- Need ON + ]] +} +-- ASN1STOP +``` + +#### **WLAN-LocationServerErrorCauses field descriptions** + +##### **cause** + +This field provides a WLAN AP specific error cause for the server applicable to provision of assistance data. If the cause value is '*requestedADNotAvailable*', none of the requested assistance data could be provided and no further information needs to be included. If the cause value is '*notAllRequestedADAvailable*', the server was able to provide some but not all requested WLAN AP assistance data. In this case, the server should include any of the specific error indications as applicable. Note that inclusion of these fields is applicable when some of the associated information can be provided for some WLAN APs but not for all WLAN APs. + +### – **WLAN-TargetDeviceErrorCauses** + +The IE *WLAN-TargetDeviceErrorCauses* is used by the target device to provide error reasons for WLAN positioning to the location server. + +``` +-- ASN1START +WLAN-TargetDeviceErrorCauses-r13 ::= SEQUENCE { + cause-r13 ENUMERATED {undefined, + requestedMeasurementsNotAvailable, + notAllRequestedMeasurementsPossible, + ... + }, + wlan-AP-RSSI-MeasurementNotPossible-r13 NULL OPTIONAL, + wlan-AP-RTT-MeasurementNotPossible-r13 NULL OPTIONAL, + ... +} +-- ASN1STOP +``` + +#### **WLAN-TargetDeviceErrorCauses field descriptions** + +##### **cause** + +This field provides a WLAN specific error cause. If the cause value is 'notAllRequestedMeasurementsPossible', the target device was not able to provide all requested WLAN measurements (but may be able to provide some measurements). In this case, the target device should include any of the *wlan-AP-RSSI-MeasurementNotPossible*, or *wlan-AP-RTT-MeasurementNotPossible* fields, as applicable. + +### 6.5.6.7 WLAN Assistance Data + +### – **WLAN-ProvideAssistanceData** + +The IE *WLAN-ProvideAssistanceData* is used by the location server to provide assistance data to enable UE-based and UE-assisted WLAN positioning. It may also be used to provide WLAN positioning specific error reason. + +``` +-- ASN1START +WLAN-ProvideAssistanceData-r14 ::= SEQUENCE { + wlan-DataSet-r14 SEQUENCE (SIZE (1..maxWLAN-DataSets-r14)) OF WLAN-DataSet-r14 + OPTIONAL, -- Need ON + wlan-Error-r14 WLAN-Error-r13 + OPTIONAL, -- Need ON + ... +} +-- ASN1STOP +``` + +#### **WLAN-ProvideAssistanceData field descriptions** + +##### **wlan-DataSet** + +This field provides data for sets of WLAN APs. + +##### **wlan-Error** + +This field provides error information and may be included when a Provide Assistance Data is sent in response to a Request Assistance Data. It is allowed to include both a *wlan-DataSet* field and a *wlan-Error* field (e.g. when only some requested WLAN assistance data is provided). + +### 6.5.6.8 WLAN Assistance Data Elements + +### – **WLAN-DataSet** + +The IE *WLAN-DataSet* is used by the location server to provide WLAN AP information for one set of WLAN APs. + +``` +-- ASN1START +WLAN-DataSet-r14 ::= SEQUENCE { + wlan-AP-List-r14 SEQUENCE (SIZE (1..maxWLAN-AP-r14)) OF WLAN-AP-Data-r14, + supportedChannels-11a-r14 SupportedChannels-11a-r14 OPTIONAL, -- Need ON +``` + +``` + + supportedChannels-11bg-r14 SupportedChannels-11bg-r14 OPTIONAL, -- Need ON + ... +} + +SupportedChannels-11a-r14 ::= SEQUENCE { + ch34-r14 BOOLEAN, + ch36-r14 BOOLEAN, + ch38-r14 BOOLEAN, + ch40-r14 BOOLEAN, + ch42-r14 BOOLEAN, + ch44-r14 BOOLEAN, + ch46-r14 BOOLEAN, + ch48-r14 BOOLEAN, + ch52-r14 BOOLEAN, + ch56-r14 BOOLEAN, + ch60-r14 BOOLEAN, + ch64-r14 BOOLEAN, + ch149-r14 BOOLEAN, + ch153-r14 BOOLEAN, + ch157-r14 BOOLEAN, + ch161-r14 BOOLEAN +} + +SupportedChannels-11bg-r14 ::= SEQUENCE { + ch1-r14 BOOLEAN, + ch2-r14 BOOLEAN, + ch3-r14 BOOLEAN, + ch4-r14 BOOLEAN, + ch5-r14 BOOLEAN, + ch6-r14 BOOLEAN, + ch7-r14 BOOLEAN, + ch8-r14 BOOLEAN, + ch9-r14 BOOLEAN, + ch10-r14 BOOLEAN, + ch11-r14 BOOLEAN, + ch12-r14 BOOLEAN, + ch13-r14 BOOLEAN, + ch14-r14 BOOLEAN +} + +-- ASN1STOP + +``` + +#### **WLAN-DataSet field descriptions** + +##### ***wlan-AP-List*** + +This field provides information for WLAN APs in the data set. + +##### ***supportedChannels-11a*** + +This field defines the superset of all channels supported by all WLAN APs in the data set of type 801.11a (5GHz band). + +##### ***supportedChannels-11bg*** + +This field defines the superset of all channels supported by all WLAN APs in the data set of type 801.11b or 802.11g (2.4 GHz band). + +### — ***WLAN-AP-Data*** + +The IE *WLAN-AP-Data* is used by the location server to provide information for one WLAN AP as part of WLAN AP assistance data. + +``` + +-- ASN1START + +WLAN-AP-Data-r14 ::= SEQUENCE { + wlan-AP-Identifier-r14 WLAN-AP-Identifier-r13, + wlan-AP-Location-r14 WLAN-AP-Location-r14 OPTIONAL, -- Need ON + ... +} + +WLAN-AP-Location-r14 ::= SEQUENCE { + locationDataLCI-r14 LocationDataLCI-r14, + ... +} + +LocationDataLCI-r14 ::= SEQUENCE { + latitudeUncertainty-r14 BIT STRING (SIZE (6)), + latitude-r14 BIT STRING (SIZE (34)), + +``` + +``` + +longitudeUncertainty-r14 BIT STRING (SIZE (6)), +longitude-r14 BIT STRING (SIZE (34)), +altitudeUncertainty-r14 BIT STRING (SIZE (6)) OPTIONAL, -- Need ON +altitude-r14 BIT STRING (SIZE (30)) OPTIONAL, -- Need ON +datum-r14 BIT STRING (SIZE (8)), +... +} + +-- ASN1STOP + +``` + +#### WLAN-AP-Data field descriptions + +##### *wlan-AP-Location* + +###### *locationDataLCI* + +This field provides the location of the WLAN AP in the form of Location Configuration Information (LCI) defined in [27] and includes the following subfields: + +**latitudeUncertainty:** 6-bits quantifying the amount of uncertainty in latitude. A value of 0 is reserved to indicate that the uncertainty is unknown; values greater than 34 are reserved. Its relation with the corresponding value in degrees is expressed with the following formula: + +$$\text{latitudeUncertainty} = 8 - \text{ceil}(\log_2(\text{uncertainty in degrees}))$$ + +**latitude:** A 34-bits fixed point value consisting of 9-bits of integer and 25-bits of fraction indicating the Latitude (+/- 90 degrees) of the AP. + +**longitudeUncertainty:** 6-bits quantifying the amount of uncertainty in longitude. A value of 0 is reserved to indicate that the uncertainty is unknown; values greater than 34 are reserved. Its relation with the corresponding value in degrees is expressed with the following formula: + +$$\text{longitudeUncertainty} = 8 - \text{ceil}(\log_2(\text{uncertainty in degrees}))$$ + +**longitude:** A 34-bits fixed point value consisting of 9-bits of integer and 25-bits of fraction indicating the Longitude (+/- 180 degrees) of the AP. + +**altitudeUncertainty:** 6-bits value quantifying the amount of uncertainty in the altitude value. A value of 0 is reserved to indicate that the uncertainty is unknown; values greater than 30 are reserved. Its relation with the corresponding value in metres is expressed with the following formula: + +$$\text{altitudeUncertainty} = 21 - \text{ceil}(\log_2(\text{uncertainty in metres}))$$ + +**altitude:** A 30-bit fixed point value consisting of 22-bits of integer and 8-bits of fraction indicating the altitude of the AP in metres. + +**datum:** 8-bits indicating the map datum used for the coordinates. Defined codes are: + +Bit 1: World Geodetic System 1984 (WGS-84) + +Bit 2: North American Datum 1983 (NAD-83) with North American Vertical Datum 1988 (NAVD-88) + +Bit 3: North American Datum 1983 (NAD-83) with Mean Lower Low Water (MLLW) vertical datum. + +Bits 4 – 8 are reserved. + +### 6.5.6.9 WLAN Assistance Data Request + +#### *WLAN-RequestAssistanceData* + +The IE *WLAN-RequestAssistanceData* is used by the target device to request WLAN assistance data from a location server. + +``` + +-- ASN1START + +WLAN-RequestAssistanceData-r14 ::= SEQUENCE { + requestedAD-r14 BIT STRING { ap-identifier (0), + ap-location (1) } (SIZE (1..8)), + visibleAPs-r14 SEQUENCE (SIZE (1..maxVisibleAPs-r14)) OF WLAN-AP-Identifier-r13 + OPTIONAL, + wlan-AP-StoredData-r14 SEQUENCE (SIZE (1..maxKnownAPs-r14)) OF WLAN-AP-Identifier-r13 + OPTIONAL, + ... +} + +-- ASN1STOP + +``` + +| WLAN-RequestAssistanceData field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| requestedAD
This field specifies the WLAN AP assistance data requested. This is represented by a bit string, with a one-value at the bit position means the particular assistance data is requested; a zero-value means not requested. The following assistance data types are included:
ap-identifier: WLAN AP identity information
ap-location: WLAN AP location information | +| visibleAPs
This field enables a target to indicate to a server the identities of currently visible WLAN APs. This may assist a server to provide assistance data for WLAN APs nearby to the target. A target shall provide visible APs in order of received signal strength with the AP with the highest signal strength provided first. | +| wlan-AP-StoredData
This field enables a target to indicate to a server the identities of WLAN APs for which the target has stored assistance data received previously from the server. This may enable the server to avoid resending data for the same APs. | + +## 6.5.7 Bluetooth-based Positioning + +### 6.5.7.1 Bluetooth Location Information + +#### — *BT-ProvideLocationInformation* + +The IE *BT-ProvideLocationInformation* is used by the target device to provide measurements for one or more Bluetooth beacons to the location server. It may also be used to provide Bluetooth positioning specific error reason. + +``` +-- ASN1START + +BT-ProvideLocationInformation-r13 ::= SEQUENCE { + bt-MeasurementInformation-r13 BT-MeasurementInformation-r13 OPTIONAL, + bt-Error-r13 BT-Error-r13 OPTIONAL, + ..., + [[ + bt-AoA-Config-r18 BT-AoA-Config-r18 OPTIONAL + ]] +} + +BT-AoA-Config-r18 ::= SEQUENCE { + btAddr-r18 BIT STRING (SIZE (48)), + cteStatus-r18 ENUMERATED {enabled, disabled} OPTIONAL, + primaryAdvInterval-r18 INTEGER (32..16777) OPTIONAL, + secondAdvInterval-r18 INTEGER (6..65535) OPTIONAL, + txPower-r18 INTEGER (-127..20) OPTIONAL, + cteLength-r18 INTEGER (2..20) OPTIONAL, + cteCount-r18 INTEGER (1..16) OPTIONAL, + tx-PHY-M2-r18 NULL OPTIONAL, + ... +} + +-- ASN1STOP +``` + +| BT- ProvideLocationInformation field descriptions | | +|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| btAddr | This field specifies the Bluetooth address of the device [53]. In case the device updates its address during an established LPP session, the device shall provide the new address as unsolicited location information to the server | +| cteStatus | This field provides the Bluetooth AoA transmission status of the device:
enabled: Bluetooth AoA transmission is enabled
disabled: Bluetooth AoA transmission is disabled | +| primaryAdvInterval | This field specifies the Bluetooth primary advertisement channel periodicity that the device will use, scaling factor 0.625 ms [53]. | +| secondAdvInterval | This field specifies the Bluetooth periodic advertising interval on secondary advertisement channels that the device will use, scaling factor 0.625 ms [53]. | +| txPower | This field specifies the Bluetooth advertising TX power in dBm that the device will use. | +| cteLength | This field specifies the configured CTE length to be used by the device in number of 8us segments. | +| cteCount | This field specifies the number of Bluetooth packets that include a CTE that the device will transmit each periodic advertising. | +| tx-PHY-M2 | This field, if present, indicates that Bluetooth TX PHY 2 Megasymbols/s will be used for AoA, otherwise Bluetooth TX PHY 1 Megasymbols/s will be used, | + +## 6.5.7.2 Bluetooth Location Information Elements + +### – *BT-MeasurementInformation* + +``` +-- ASN1START + +BT-MeasurementInformation-r13 ::= SEQUENCE { + measurementReferenceTime-r13 UTCTime OPTIONAL, + bt-MeasurementList-r13 BT-MeasurementList-r13 OPTIONAL, + ..., + [[ + bt-MeasurementList-r18 BT-MeasurementList-r18 OPTIONAL + ]] +} + +BT-MeasurementList-r13 ::= SEQUENCE (SIZE(1..maxBT-Beacon-r13)) OF BT-MeasurementElement-r13 + +BT-MeasurementElement-r13 ::= SEQUENCE { + btAddr-r13 BIT STRING (SIZE (48)), + rssi-r13 INTEGER (-128..127) OPTIONAL, + ... +} + +BT-MeasurementList-r18 ::= SEQUENCE (SIZE(1..maxBT-Beacon-r13)) OF BT-MeasurementElement-r18 + +BT-MeasurementElement-r18 ::= SEQUENCE { + btAddr-r18 BIT STRING (SIZE (48)), + bt-azimuth-r18 INTEGER (0..359), + bt-elevation-r18 INTEGER (0..180) OPTIONAL, + rssi-r18 INTEGER (-128..127) OPTIONAL, + ... +} + +-- ASN1STOP +``` + +| BT-MeasurementInformation field descriptions | | +|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| measurementReferenceTime | This field provides the UTC time when the Bluetooth measurements are performed and should take the form of YYMMDDhhmmssZ. | +| bt-MeasurementList | This field provides the Bluetooth measurements for up to 32 Bluetooth beacons. | +| btAddr | This field specifies the Bluetooth public address of the Bluetooth beacon [25]. | +| rssi | This field provides the beacon received signal strength indicator (RSSI) in dBm. | +| bt-azimuth | This field represents the estimated AoD azimuth in GCD relative the Bluetooth beacon reference position. | +| bt-elevation | This field represents the estimated AoD elevation in GCD relative the Bluetooth beacon reference position. | + +### 6.5.7.3 Bluetooth Location Information Request + +#### – **BT-RequestLocationInformation** + +The IE **BT-RequestLocationInformation** is used by the location server to request Bluetooth measurements from a target device. + +``` +-- ASN1START +BT-RequestLocationInformation-r13 ::= SEQUENCE { + requestedMeasurements-r13 BIT STRING { + rssi (0), + aod-v1800 (1) } (SIZE(1..8)), + ..., + [[ + bt-requestedAoA-Config-r18 BIT STRING { + aoa-advConfig (0), + aoa-cteConfig (1) } (SIZE(1..8)) OPTIONAL, -- Need ON + bt-suggestedAoA-Config-r18 BT-SuggestedAoA-Config-r18 OPTIONAL -- Need ON + ]] +} + +BT-SuggestedAoA-Config-r18 ::= SEQUENCE { + cteStatus-r18 ENUMERATED {enabled, disabled} OPTIONAL, -- Need ON + primaryAdvInterval-r18 INTEGER (32..16777) OPTIONAL, -- Need ON + secondAdvInterval-r18 INTEGER (6..65535) OPTIONAL, -- Need ON + txPower-r18 INTEGER (-127..20) OPTIONAL, -- Need ON + cteLength-r18 INTEGER (2..20) OPTIONAL, -- Need ON + cteCount-r18 INTEGER (1..16) OPTIONAL, -- Need ON + tx-PHY-M2-r18 NULL OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP +``` + +| BT-RequestLocationInformation field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| requestedMeasurements
This field specifies the Bluetooth measurements requested. This is represented by a bit string, with a one-value at the bit position means the particular measurement is requested; a zero-value means not requested. The following measurement requests can be included:
rssi: Bluetooth beacon signal strength at the target
aod: Estimated AoD per Bluetooth beacon | +| bt-requestedAoA-Config
This field specifies the Bluetooth AoA configuration parameters requested. This is represented by a bit string, with a one-value at the bit position means the particular measurement is requested; a zero-value means not requested. The following information requests can be included:
aoa-advConfig: The Bluetooth advertisement address and periodic intervals of the device
aoa-cteConfig: The configured CTE status, length, count and PHY | +| cteStatus
This field suggests the Bluetooth AoA transmission status of the device, and is used by the location server to suggest BLE AoA transmission of the device to be enabled or disabled:
enabled: Bluetooth AoA transmission is suggested enabled
disabled: Bluetooth AoA transmission is suggested disabled | +| primaryAdvInterval
This field suggests the Bluetooth primary advertisement channel periodicity of the device, scaling factor 0.625 ms [53]. | +| secondAdvInterval
This field suggests the Bluetooth periodic advertising interval on secondary advertisement channels of the device, scaling factor 0.625 ms [53]. | +| txPower
This field suggests the Bluetooth advertising TX power in dBm of the device [53]. | +| cteLength
This field suggests the CTE length of the device in number of 8us segments. | +| cteCount
This field suggests the number of Bluetooth packets that include a CTE of the device each periodic advertising event | +| tx-PHY-M2
This field, if present, suggests that Bluetooth TX PHY 2 Megasymbols/s is used for AoA, otherwise Bluetooth TX PHY 1 Megasymbols/s is suggested to be used by the device, | + +## 6.5.7.4 Bluetooth Capability Information + +### — *BT-ProvideCapabilities* + +The IE *BT-ProvideCapabilities* is used by the target device to provide its capabilities for Bluetooth positioning to the location server. + +``` +-- ASN1START +BT-ProvideCapabilities-r13 ::= SEQUENCE { + bt-Modes-r13 BIT STRING { standalone (0), + ue-assisted (1) } (SIZE (1..8)), + bt-MeasSupported-r13 BIT STRING { rssi-r13 (0), + aod-v1800 (1) } (SIZE (1..8)), + ..., + [[ + idleStateForMeasurements-r14 + ENUMERATED { required } + OPTIONAL, + periodicalReportingSupported-r14 + PositioningModes + OPTIONAL + ]], + [[ scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupportPerMode-r17 OPTIONAL + ]] +} + +-- ASN1STOP +``` + +| BT-ProvideCapabilities field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bt-Modes
This field specifies the Bluetooth mode(s) supported by the target device. This is represented by a bit string, with a one value at the bit position means the Bluetooth mode is supported; a zero value means not supported. | +| bt-MeasSupported
This field specifies the Bluetooth measurements supported by the target device. This is represented by a bit string, with a one-value at the bit position means the particular measurement is supported; a zero-value means not supported. A zero-value in all bit positions in the bit string means only the basic Bluetooth positioning method is supported by the target device which is reporting of the Bluetooth beacon identity. The following bits are assigned for the indicated measurements.
rssi: Bluetooth beacon signal strength at the target device | +| idleStateForMeasurements
This field, if present, indicates that the target device requires idle state to perform BT measurements. | +| periodicalReportingSupported
This field, if present, specifies the positioning modes for which the target device supports periodicalReporting . This is represented by a bit string, with a one value at the bit position means periodicalReporting for the positioning mode is supported; a zero value means not supported. If this field is absent, the location server may assume that the target device does not support periodicalReporting in CommonIEsRequestLocationInformation . | +| scheduledLocationRequestSupported
This field, if present, specifies the positioning modes for which the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonIEsRequestLocationInformation – and the time base(s) supported for the scheduled location time for each positioning mode. If this field is absent, the target device does not support scheduled location requests. | +| bt-AoD
This field, if present, indicates that the target device supports Bluetooth AoD | + +### 6.5.7.5 Bluetooth Capability Information Request + +#### – *BT-RequestCapabilities* + +The IE *BT-RequestCapabilities* is used by the location server to request Bluetooth positioning capabilities from a target device. + +``` +-- ASN1START +BT-RequestCapabilities-r13 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +### 6.5.7.6 BT Error Elements + +#### – *BT-Error* + +The IE *BT-Error* is used by the location server or target device to provide error reasons for Bluetooth positioning to the target device or location server, respectively. + +``` +-- ASN1START +BT-Error-r13 ::= CHOICE { + locationServerErrorCauses-r13      BT-LocationServerErrorCauses-r13, + targetDeviceErrorCauses-r13      BT-TargetDeviceErrorCauses-r13, + ... +} +-- ASN1STOP +``` + +#### – *BT-LocationServerErrorCauses* + +The IE *BT-LocationServerErrorCauses* is used by the location server to provide error reasons for Bluetooth positioning to the target device. + +``` +-- ASN1START + +BT-LocationServerErrorCauses-r13 ::= SEQUENCE { + cause-r13 ENUMERATED {undefined, ...}, + ... +} + +-- ASN1STOP +``` + +### BT-TargetDeviceErrorCauses + +The IE *BT-TargetDeviceErrorCauses* is used by the target device to provide error reasons for Bluetooth positioning to the location server. + +``` +-- ASN1START + +BT-TargetDeviceErrorCauses-r13 ::= SEQUENCE { + cause-r13 ENUMERATED {undefined, + requestedMeasurementsNotAvailable, + notAllRequestedMeasurementsPossible, + ... + }, + bt-Beacon-rssiMeasurementNotPossible-r13 NULL OPTIONAL, + ... +} + +-- ASN1STOP +``` + +#### BT-TargetDeviceErrorCauses field descriptions + +##### cause + +This field provides a Bluetooth specific error cause. If the cause value is 'notAllRequestedMeasurementsPossible', the target device was not able to provide all requested Bluetooth measurements (but may be able to provide some measurements). In this case, the target device should include *bt-Beacon-rssiMeasurementNotPossible* field. + +## 6.5.7.7 Bluetooth Assistance Data + +### BT-ProvideAssistanceData + +The IE *BT-ProvideAssistanceData* is used by the location server to provide assistance data to enable UE-based and UE-assisted AoD positioning. It may also be used to provide Bluetooth positioning specific error reasons. + +``` +-- ASN1START + +BT-ProvideAssistanceData-r18 ::= SEQUENCE { + bt-BeaconInfo-r18 BT-BeaconInfo-r18, + bt-Error-r18 BT-Error-r13 OPTIONAL, -- Need ON + ... +} + +-- ASN1STOP +``` + +#### BT-ProvideAssistanceData field descriptions + +##### bt-BeaconInfo + +This field provides data for a set of Bluetooth beacons. + +##### bt-Error + +This field provides error information and may be included when a Provide Assistance Data is sent in response to a Request Assistance Data. + +## 6.5.7.8 Bluetooth Assistance Data Elements + +### — *BT-BeaconInfo* + +The IE *BT-BeaconInfo* is used by the location server to provide Bluetooth beacon information for one set of Bluetooth beacons. + +``` +-- ASN1START + +BT-BeaconInfo-r18 ::= SEQUENCE { + referencePoint-r18 ReferencePoint-r16, + bt-BeaconInfoList-r18 SEQUENCE (SIZE (1..maxBT-BeaconAD-r18)) OF + BT-BeaconInfoElement-r18, + ... +} + +BT-BeaconInfoElement-r18 ::= SEQUENCE { + btAddr-r18 BIT STRING (SIZE (48)), + bt-BeaconLocation-r18 RelativeLocation-r16 OPTIONAL, -- Need OP + bt-LCS-GCS-TranslationParameter-r18 LCS-GCS-TranslationParameter-r16 + OPTIONAL, -- Cond NotSameAsPrev1 + bt-antArrayConfig-r18 BT-AntArrayConfig-r18 OPTIONAL, -- Cond NotSameAsPrev2 + bt-antElementList-r18 SEQUENCE (SIZE (2..maxBT-BeaconAntElt-r18)) OF + BT-AntElement-r18 OPTIONAL, -- Cond NotSameAsPrev3 + bt-antSwitchingPattern-r18 SEQUENCE (SIZE (2..maxBT-BeaconAntElt-r18)) OF + BT-AntSwitchElement-r18 OPTIONAL, -- Cond NotSameAsPrev4 + bt-AoDTransmConfig-r18 BT-AoDTransmConfig-r18 OPTIONAL, -- Cond NotSameAsPrev5 + ... +} + +BT-AntArrayConfig-r18 ::= CHOICE { + bt-UniformLinearArray-r18 BT-UniformLinearArray-r18, + bt-UniformRectangularArray-r18 BT-UniformRectangularArray-r18, + bt-UniformCircularArray-r18 BT-UniformCircularArray-r18, + bt-GenericArray-r18 BT-GenericArray-r18 +} + +BT-AntElement-r18 ::= SEQUENCE { + polarization-r18 ENUMERATED {m45, zero, p45, p90, circ}, + ... +} + +BT-AntSwitchElement-r18 ::= SEQUENCE { + antElementIndexShort-r18 INTEGER (1..16), + antElementIndexOffset-r18 ENUMERATED {o16, o32, o48, o64} OPTIONAL, -- Need OP + ... +} + +BT-AoDTransmConfig-r18 ::= SEQUENCE { + primaryAdvInterval-r18 INTEGER (32..16777), + secondAdvInterval-r18 INTEGER (6..65535), + cteLength-r18 INTEGER (2..20), + cteCount-r18 INTEGER (1..16), + cteType2us-r18 NULL OPTIONAL, -- Need OP + tx-PHY-M2-r18 NULL OPTIONAL, -- Need OP + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NotSameAsPrev1 | The field is mandatory present in the first element of the bt-BeaconInfoList list; otherwise if not present, the bt-LCS-GCS-TranslationParameter of this element is the same as the bt-LCS-GCS-TranslationParameter of the previous element in the bt-BeaconInfoList list | +| NotSameAsPrev2 | The field is mandatory present in the first element of the bt-BeaconInfoList list; otherwise if not present, the bt-antArrayConfig of this element is the same as the bt-antArrayConfig of the previous element in the bt-BeaconInfoList list | +| NotSameAsPrev3 | The field is mandatory present in the first element of the bt-BeaconInfoList list; otherwise if not present, the bt-antElementList of this element is the same as the bt-antElementList of the previous element in the bt-BeaconInfoList list | +| NotSameAsPrev4 | The field is mandatory present in the first element of the bt-BeaconInfoList list; otherwise if not present, the bt-antSwitchingPattern of this element is the same as the bt-antSwitchingPattern of the previous element in the bt-BeaconInfoList list | +| NotSameAsPrev5 | The field is mandatory present in the first element of the bt-BeaconInfoList list; otherwise if not present, the bt-AoDTransmConfig of this element is the same as the bt-AoDTransmConfig of the previous element in the bt-BeaconInfoList list | + +| BT-BeaconInfo field descriptions | | +|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| btAddr | This field specifies the Bluetooth public address of the Bluetooth beacon [53]. | +| referencePoint | This field specifies the reference point used to define the locations of the set of Bluetooth beacons. | +| bt-BeaconLocation | This field provides the location of the Bluetooth beacon relative to the referencePoint location. If this field is absent the Bluetooth beacon location coincides with the referencePoint location | +| bt-LCS-GCS-TranslationParameter | This field provides the angles $\alpha$ (bearing angle), $\beta$ (downtilt angle) and $\gamma$ (slant angle) for the translation of a Local Coordinate System (LCS) to a Global Coordinate System (GCS) as defined in TR 38.901 [44]. | +| polarization | This field specifies the antenna element polarization in degrees relative the positive y-axis, where m45 , zero , p45 , p90 represents -45, zero, 45 and 90 degrees respectively towards the z-axis, and circ represents circular polarization. | +| bt-AoDTransmConfig | This field specifies Bluetooth beacon AoD transmission configuration in terms of advertising periodicities and CTE configuration to support the device to configure its scan windows and intervals. | +| primaryAdvInterval | This field specifies the Bluetooth primary advertisement channel periodicity used by the Bluetooth beacon, scaling factor 0.625 ms [53]. | +| secondAdvInterval | This field specifies the Bluetooth periodic advertising interval on secondary advertisement channels used by the Bluetooth beacon, scaling factor 0.625 ms [53]. | +| cteLength | This field specifies the configured CTE length to be used by the beacon in number of 8us segments. | +| cteCount | This field specifies the number of Bluetooth packets that include a CTE that are transmitted each periodic advertising event | +| cteType2us | This field, if present, indicates that 2us antenna switching slot duration is used by the beacon, otherwise 1us antenna switching slot duration is used, | +| tx-PHY-M2 | This field, if present, indicates that Bluetooth TX PHY 2 Megasymbols/s is used by the beacon, otherwise Bluetooth TX PHY 1 Megasymbols/s is used, | +| bt-antSwitchingPattern | This field specifies the Bluetooth antenna switching pattern as a list of indices, where each index is the order value of a specific antenna element in the bt-antElementList-r18 attribute of the IE BT-BeaconInfoElement-r18 – first element in the list corresponds to index 1 and so on. If the antenna switching pattern is shorter than the number of available sample slots, then the antenna switching patterns continues from the beginning of the bt-antSwitchingPattern-r18 . If antenna switching pattern is longer than the number of available sample slots, then the elements in bt-antSwitchingPattern-r18 are discarded. If this field is not present, the target device can assume an antenna switching pattern with the configured antenna element in the same order as in the bt-antElementList-r18 . | +| antElementIndexShort | This field specifies short part of the antenna element index | +| antElementIndexOffset | This field specifies offset of the antenna element index, where o16 , o32 , o48 and o64 respresents 16, 32, 48 and 64 respectively to offset the short part of the antenna element index. If not present, the offset is zero. | + +## – *BT-UniformLinearArray* + +The IE *BT-UniformLinearArray* is used by the location server to define a linear antenna array as a formula based on the antenna element index. + +``` +-- ASN1START +BT-UniformLinearArray-r18 ::= SEQUENCE { + bt-NoElements-r18 INTEGER (2..maxBT-BeaconAntElt-r18), + bt-InterElementDist-r18 INTEGER (30..130) +} +-- ASN1STOP +``` + +### ***BT-UniformLinearArray* field descriptions** + +#### ***bt-NoElements*** + +This field specifies the number of antenna elements in the linear antenna array. It is the same as the number of antenna elements in the *bt-antElementList-r18* of the IE *BT-BeaconInfoElement-r18*. + +#### ***bt-InterElementDist*** + +This field specifies the distance between to adjacent elements in the uniform linear antenna array between $\frac{1}{4}$ and just above 1 wavelength. Scale factor 1mm. + +The antenna element locations of the antenna array are defined along the y-axis from the reference point. The coordinates of the elements are $x=0$ , $z=0$ and $y = (index-1)*bt-InterElementDist-r18$ , where *index* is the order value of a specific antenna element in the *bt-antElementList-r18* attribute of the IE *BT-BeaconInfoElement-r18* – first element in the list corresponds to index 1 and so on. + +## – *BT-UniformRectangularArray* + +The IE *BT-UniformRectangularArray* is used by the location server to define a rectangular antenna array as a formula based on the antenna element index. + +``` +-- ASN1START +BT-UniformRectangularArray-r18 ::= SEQUENCE { + bt-NoElementsY-r18 INTEGER (1..maxBT-BeaconAntElt-r18), + bt-NoElementsZ-r18 INTEGER (1..maxBT-BeaconAntElt-r18), + bt-InterElementDistY-r18 INTEGER (30..135), + bt-InterElementDistZ-r18 INTEGER (30..135) +} +-- ASN1STOP +``` + +### ***BT-UniformRectangularArray* field descriptions** + +#### ***bt-NoElementsY*** + +This field specifies the number of antenna elements in the L-shaped antenna array along the y-axis. The product *bt-ElementDeltaY\* bt-ElementDeltaZ* is the same as the number of antenna elements in the *bt-antElementList-r18* of the IE *BT-BeaconInfoElement-r18*. + +#### ***bt-NoElementsZ*** + +This field specifies the number of antenna elements in the linear antenna array along the z-axis. + +#### ***bt-InterElementDistY*** + +This field specifies the distance between to adjacent elements in the uniform rectangular antenna array along the y-axis. + +#### ***bt-InterElementDistZ*** + +This field specifies the distance between to adjacent elements in the uniform rectangular antenna array along the z-axis. + +The antenna element locations of the uniform rectangular antenna array are defined row by row along the y-axis with an increasing offset in the z-direction for each row from the reference point. The coordinates of the elements of the + +- first row are $x=0$ , $z=0$ and $y = (index-1)*bt-InterElementDistY-r18$ , for index 1 to *bt-NoElementsY* +- second row are $x=0$ , $z = bt-InterElementDistZ$ and $y = (index-bt-NoElementsY-1)*bt-InterElementDistY-r18$ , for index (*bt-NoElementsY*+1) to $2*bt-NoElementsY$ + +- row $N$ are $x=0$ , $z = (N-1)*bt-InterElementDistZ$ and $y = (index-(N-1)*bt-NoElementsY-1)*bt-InterElementDistY-r18$ , for index $((N-1)*bt-NoElementsY+1)$ to $N*bt-NoElementsY$ , where $N = 1$ to $bt-NoElementsZ$ . + +### BT-UniformCircularArray + +The IE *BT-UniformCircularArray* is used by the location server to define a uniform circular antenna array as a formula based on the antenna element index. + +``` +-- ASN1START +BT-UniformCircularArray-r18 ::= SEQUENCE { + bt-NoElements-r18 INTEGER (2..maxBT-BeaconAntElt-r18), + bt-InterElementDist-r18 INTEGER (30..130) +} + +-- ASN1STOP +``` + +#### BT-UniformCircularArray field descriptions + +##### bt-NoElements + +This field specifies the number of antenna elements in the circular antenna array. It is the same as the number of antenna elements in the *bt-antElementList-r18* of the IE *BT-BeaconInfoElement-r18* + +##### bt-InterElementDist + +This field specifies the distance between to adjacent elements in the uniform circular antenna array between $\frac{1}{4}$ and just above 1 wavelengths. Scale factor 1mm. + +The antenna element locations of the antenna array are defined along a circle with the reference point as center. The coordinates of the elements are: + +- $x=0$ +- $y = bt-Radius * \cos(2*p*(index-1)/ bt-NoElements-r18)$ +- $z = bt-Radius * \sin(2*p*(index-1)/ bt-NoElements-r18)$ + +where *index* is the order value of a specific antenna element in the *bt-antElementList-r18* attribute of the IE *BT-BeaconInfoElement-r18* – first element in the list corresponds to index 1 and so on, and + +$$bt-Radius = bt-InterElementDist-r18 / (2 * \sin(\pi / bt-NoElements-r18))$$ + +### BT-GenericArray + +The IE *BT-GenericArray* is used by the location server to define a generic antenna array as a list of offset locations for each antenna element, where each ordered entry in *BT-GenericArray-r18* is associated to the same ordered entry in the *bt-antElementList-r18* attribute of the IE *BT-BeaconInfoElement-r18*. + +``` +-- ASN1START +BT-GenericArray-r18 ::= SEQUENCE (SIZE (2..maxBT-BeaconAntElt-r18)) OF BT-ULA-GenericAntElement-r18 +BT-ULA-GenericAntElement-r18 ::= SEQUENCE { + deltaY-r18 INTEGER (-135..135) OPTIONAL, -- Need OP + deltaX-r18 INTEGER (-135..135) OPTIONAL, -- Need OP + deltaZ-r18 INTEGER (-135..135) OPTIONAL, -- Need OP +} + +-- ASN1STOP +``` + +| BT-GenericArray field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| deltaX, deltaY, deltaZ
This field specifies the antenna element location offset in X, Y, Z directions respectively. If not present, the delta is zero. Scale factor 1mm. | + +## 6.5.7.9 Bluetooth Assistance Data Request + +### – *BT-RequestAssistanceData* + +The IE *BT-RequestAssistanceData* is used by the target device to request BT assistance data from a location server. + +``` +-- ASN1START + +BT-RequestAssistanceData-r18 ::= SEQUENCE { + requestedAD-r18 BIT STRING { + beacon-location (0), + beacon-antConfig (1), + beacon-transmConfig (2) } (SIZE (1..8)), + ... +} + +-- ASN1STOP +``` + +| BT-RequestAssistanceData field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| requestedAD
This field specifies the Bluetooth assistance data requested. This is represented by a bit string, with a one-value at the bit position means the particular assistance data is requested; a zero-value means not requested. The following assistance data types are included:
  • - beacon-location: Bluetooth beacon location information
  • - beacon-antConfig: Bluetooth beacon antenna orientation, array configuration information and antenna switching pattern for AoD estimation
  • - beacon-transmConfig: Bluetooth beacon advertisement and CTE configuration information
| + +## 6.5.8 NR UL Positioning + +### 6.5.8.1 NR UL Capability Information + +### – *NR-UL-ProvideCapabilities* + +The IE *NR-UL-ProvideCapabilities* is used by the target device to indicate its capability to support UL SRS for positioning and to provide its UL SRS for positioning capabilities to the location server. + +``` +-- ASN1START + +NR-UL-ProvideCapabilities-r16 ::= SEQUENCE { + nr-UL-SRS-Capability-r16 NR-UL-SRS-Capability-r16, + ..., + [[ + nr-UE-TEG-Capability-r17 NR-UE-TEG-Capability-r17 OPTIONAL + ]] +} + +-- ASN1STOP +``` + +| NR-UL-ProvideCapabilities field descriptions | +|-----------------------------------------------------------------| +| nr-UE-TEG-Capability
Indicates the UE TEG capability. | + +## 6.5.8.2 NR UL Capability Information Request + +### – *NR-UL-RequestCapabilities* + +The IE *NR-UL-RequestCapabilities* is used by the location server to request the capability of the target device to support UL SRS for positioning and to request UL SRS for positioning capabilities from a target device. + +``` +-- ASN1START +NR-UL-RequestCapabilities-r16 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +## 6.5.9 NR E-CID Positioning + +This clause defines the information elements for NR E-CID positioning (TS 38.305 [40]). + +### 6.5.9.1 NR E-CID Location Information + +#### – *NR-ECID-ProvideLocationInformation* + +The IE *NR-ECID-ProvideLocationInformation* is used by the target device to provide NR E-CID location measurements to the location server. It may also be used to provide NR E-CID positioning specific error reason. + +``` +-- ASN1START +NR-ECID-ProvideLocationInformation-r16 ::= SEQUENCE { + nr-ECID-SignalMeasurementInformation-r16 NR-ECID-SignalMeasurementInformation-r16 OPTIONAL, + nr-ECID-Error-r16 NR-ECID-Error-r16 OPTIONAL, + ... +} +-- ASN1STOP +``` + +### 6.5.9.2 NR E-CID Location Information Elements + +#### – *NR-ECID-SignalMeasurementInformation* + +The IE *NR-ECID-SignalMeasurementInformation* is used by the target device to provide NR E-CID measurements to the location server. + +``` +-- ASN1START +NR-ECID-SignalMeasurementInformation-r16 ::= SEQUENCE { + nr-PrimaryCellMeasuredResults-r16 NR-MeasuredResultsElement-r16, + nr-MeasuredResultsList-r16 NR-MeasuredResultsList-r16 OPTIONAL, + ... +} + +NR-MeasuredResultsList-r16 ::= SEQUENCE (SIZE(1..32)) OF NR-MeasuredResultsElement-r16 + +NR-MeasuredResultsElement-r16 ::= SEQUENCE { + nr-PhysCellID-r16 NR-PhysCellID-r16, + nr-ARFCN-r16 CHOICE { + ssb-ARFCN-r16 ARFCN-ValueNR-r15, + csi-RS-pointA-r16 ARFCN-ValueNR-r15 + }, + nr-CellGlobalID-r16 NCGI-r15 OPTIONAL, + systemFrameNumber-r16 BIT STRING (SIZE (10)) OPTIONAL, + resultsSSB-Cell-r16 MeasQuantityResults-r16 OPTIONAL, + resultsCSI-RS-Cell-r16 MeasQuantityResults-r16 OPTIONAL, + resultsSSB-Indexes-r16 ResultsPerSSB-IndexList-r16 OPTIONAL, + resultsCSI-RS-Indexes-r16 ResultsPerCSI-RS-IndexList-r16 OPTIONAL, + ... +} +``` + +``` + +MeasQuantityResults-r16 ::= SEQUENCE { + nr-RSRP-r16 INTEGER (0..127) OPTIONAL, + nr-RSRQ-r16 INTEGER (0..127) OPTIONAL +} + +ResultsPerSSB-IndexList-r16 ::= SEQUENCE (SIZE (1..64)) OF ResultsPerSSB-Index-r16 + +ResultsPerSSB-Index-r16 ::= SEQUENCE { + ssb-Index-r16 INTEGER (0..63), + ssb-Results-r16 MeasQuantityResults-r16 +} + +ResultsPerCSI-RS-IndexList-r16 ::= SEQUENCE (SIZE (1..64)) OF ResultsPerCSI-RS-Index-r16 + +ResultsPerCSI-RS-Index-r16 ::= SEQUENCE { + csi-RS-Index-r16 INTEGER (0..95), + csi-RS-Results-r16 MeasQuantityResults-r16 +} + +-- ASN1STOP + +``` + +| NR-ECID-SignalMeasurementInformation field descriptions | | +|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-PrimaryCellMeasuredResults | This field contains the NR E-CID measurements for the primary cell. | +| nr-MeasuredResultsList | This field contains the NR E-CID measurements for up to 32 neighbour cells. | +| nr-PhysCellID | This field specifies the NR physical cell identity of the measured cell. | +| nr-ARFCN | This field specifies the ARFCN of the first RE of SSB's RB#10 or the point A of CSI-RS. | +| nr-CellGlobalID | This field specifies the NR cell global ID of the measured cell. The target device shall provide this field if it was able to determine the NCGI of the measured cell at the time of measurement. | +| systemFrameNumber | This field specifies the system frame number of the measured cell during which the measurements have been performed. The target device shall include this field if it was able to determine the SFN of the cell at the time of measurement. | +| resultsSSB-Cell | This field specifies the SS reference signal received power (SS-RSRP) and quality (SS-RSRQ) measurement aggregated at cell level, as defined in TS 38.331 [35]. | +| resultsCSI-RS-Cell | This field specifies the CSI-RS reference signal received power (CSI-RSRP) and quality (CSI-RSRQ) measurement aggregated at cell level, as defined in TS 38.331 [35]. | +| resultsSSB-Indexes | This field specifies the SS reference signal received power (SS-RSRP) and quality (SS-RSRQ) measurement per SSB resource, as defined in TS 38.331 [35]. | +| resultsCSI-RS-Indexes | This field specifies the CSI-RS reference signal received power (CSI-RSRP) and quality (CSI-RSRQ) per CSI-RS resource, as defined in TS 38.331 [35]. | +| nr-RSRP | This field specifies the integer value for RSRP measurements according to Table 10.1.6.1-1 in TS 38.133 [46]. | +| nr-RSRQ | This field specifies the integer value for RSRQ measurements according to Table 10.1.11.1-1 in TS 38.133 [46]. | + +### 6.5.9.3 NR E-CID Location Information Request + +#### – *NR-ECID-RequestLocationInformation* + +The IE *NR-ECID-RequestLocationInformation* is used by the location server to request NR E-CID location measurements from a target device. + +``` + +-- ASN1START + +NR-ECID-RequestLocationInformation-r16 ::= SEQUENCE { + requestedMeasurements-r16 BIT STRING { + ssrsrpReq (0), + ssrsrqReq (1), + csirsprReq (2), + } +} + +``` + +``` + + csirsreqReq (3) { (SIZE(1..8)), + ... +} +-- ASN1STOP + +``` + +#### NR-ECID-RequestLocationInformation field descriptions + +##### **requestedMeasurements** + +This field specifies the NR E-CID measurements requested. This is represented by a bit string, with a one-value at the bit position means the particular measurement is requested; a zero-value means not requested. + +### 6.5.9.4 NR E-CID Capability Information + +#### – NR-ECID-ProvideCapabilities + +The IE *NR-ECID-ProvideCapabilities* is used by the target device to indicate its capability to support NR E-CID and to provide its NR E-CID positioning capabilities to the location server. + +``` + +-- ASN1START +NR-ECID-ProvideCapabilities-r16 ::= SEQUENCE { + nr-ECID-MeasSupported-r16 BIT STRING { + ssrsrpSup (0), + ssrsrqSup (1), + csirsrpSup (2), + csirsreqSup (3) } (SIZE(1..8)), + periodicalReporting-r16 ENUMERATED { supported } OPTIONAL, + triggeredReporting-r16 ENUMERATED { supported } OPTIONAL, + ... + [[ + ten-ms-unit-ResponseTime-r17 ENUMERATED { supported } OPTIONAL, + scheduledLocationRequestSupported-r17 + ScheduledLocationTimeSupport-r17 OPTIONAL + ]] +} +-- ASN1STOP + +``` + +#### NR-ECID-ProvideCapabilities field descriptions + +##### **nr-ECID-MeasSupported:** + +Indicates the supported NR ECID measurements: + +- *ssrsrpSup* indicates the UE supports SSB based cell/beam specific RSRP measurement; +- *ssrsrqSup* indicates the UE supports SSB based cell/beam specific RSRQ measurement; +- *csirsrpSup* indicates the UE supports CSI-RS based cell/beam specific RSRP measurement; +- *csirsreqSup* indicates the UE supports CSI-RS based cell/beam specific RSRQ measurement. + +##### **ten-ms-unit-ResponseTime** + +This field, if present, indicates that the target device supports the enumerated value '*ten-milli-seconds*' in the IE *ResponseTime* in IE *CommonEsRequestLocationInformation*. + +##### **scheduledLocationRequestSupported** + +This field, if present, indicates that the target device supports scheduled location requests – i.e., supports the IE *ScheduledLocationTime* in IE *CommonEsRequestLocationInformation* – and the time base(s) supported for the scheduled location time. + +### 6.5.9.5 NR E-CID Capability Information Request + +#### – NR-ECID-RequestCapabilities + +The IE *NR-ECID-RequestCapabilities* is used by the location server to request the capability of the target device to support NR E-CID and to request NR E-CID positioning capabilities from a target device. + +``` + +-- ASN1START +NR-ECID-RequestCapabilities-r16 ::= SEQUENCE { + ... +} + +``` + +``` +-- ASN1STOP +``` + +## 6.5.9.6 NR E-CID Error Elements + +### – *NR-ECID-Error* + +The IE *NR-ECID-Error* is used by the location server or target device to provide NR E-CID error reasons to the target device or location server, respectively. + +``` +-- ASN1START + +NR-ECID-Error-r16 ::= CHOICE { + locationServerErrorCauses-r16 NR-ECID-LocationServerErrorCauses-r16, + targetDeviceErrorCauses-r16 NR-ECID-TargetDeviceErrorCauses-r16, + ... +} + +-- ASN1STOP +``` + +### – *NR-ECID-LocationServerErrorCauses* + +The IE *NR-ECID-LocationServerErrorCauses* is used by the location server to provide NR E-CID error reasons to the target device. + +``` +-- ASN1START + +NR-ECID-LocationServerErrorCauses-r16 ::= SEQUENCE { + cause-r16 ENUMERATED { undefined, + ... + }, + ... +} + +-- ASN1STOP +``` + +### – *NR-ECID-TargetDeviceErrorCauses* + +The IE *NR-ECID-TargetDeviceErrorCauses* is used by the target device to provide NR E-CID error reasons to the location server. + +``` +-- ASN1START + +NR-ECID-TargetDeviceErrorCauses-r16 ::= SEQUENCE { + cause-r16 ENUMERATED { undefined, + requestedMeasurementNotAvailable, + notAllRequestedMeasurementsPossible, + ... + }, + ss-RSRPMeasurementNotPossible-r16 NULL OPTIONAL, + ss-RSRQMeasurementNotPossible-r16 NULL OPTIONAL, + csi-RSRPMeasurementNotPossible-r16 NULL OPTIONAL, + csi-RSRQMeasurementNotPossible-r16 NULL OPTIONAL, + ..., + [[ + remoteUE-Indication-r18 ENUMERATED {true} OPTIONAL -- Cond NR + ]] +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------| +| NR | This field is optionally present, need OR, for NR access. Otherwise it is not present. | + +| NR-ECID-TargetDeviceErrorCauses field descriptions | | +|-----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cause | This field provides a NR E-CID specific error cause. If the cause value is 'notAllRequestedMeasurementsPossible', the target device was not able to provide all requested NR E-CID measurements (but may be able to provide some measurements). In this case, the target device should include any of the ss-RSRPMeasurementNotPossible , ss-RSRQMeasurementNotPossible , csi-RSRPMeasurementNotPossible , or csi-RSRQMeasurementNotPossible fields, as applicable. | +| remoteUE-Indication | This field indicates whether the target device in NR access is configured as a L2 U2N Remote UE. | + +## 6.5.10 NR DL-TDOA Positioning + +This clause defines the information elements for NR downlink TDOA positioning (TS 38.305 [40]). + +### 6.5.10.1 NR DL-TDOA Assistance Data + +#### – NR-DL-TDOA-ProvideAssistanceData + +The IE *NR-DL-TDOA-ProvideAssistanceData* is used by the location server to provide assistance data to enable UE-assisted and UE-based NR DL-TDOA. It may also be used to provide NR DL-TDOA positioning specific error reason. + +``` +-- ASN1START +NR-DL-TDOA-ProvideAssistanceData-r16 ::= SEQUENCE { + nr-DL-PRS-AssistanceData-r16 NR-DL-PRS-AssistanceData-r16 OPTIONAL, -- Need ON + nr-SelectedDL-PRS-IndexList-r16 NR-SelectedDL-PRS-IndexList-r16 OPTIONAL, -- Need ON + nr-PositionCalculationAssistance-r16 + NR-PositionCalculationAssistance-r16 + OPTIONAL, -- Cond UEB + nr-DL-TDOA-Error-r16 NR-DL-TDOA-Error-r16 OPTIONAL, -- Need ON + ... + [ + nr-On-Demand-DL-PRS-Configurations-r17 + NR-On-Demand-DL-PRS-Configurations-r17 + OPTIONAL, -- Need ON + nr-On-Demand-DL-PRS-Configurations-Selected-IndexList-r17 + NR-On-Demand-DL-PRS-Configurations-Selected-IndexList-r17 + OPTIONAL, -- Need ON + assistanceDataValidityArea-r17 AreaID-CellList-r17 OPTIONAL -- Need ON + ], + [ + nr-PeriodicAssistData-r18 NR-PeriodicAssistData-r18 OPTIONAL -- Cond CtrTrans + ] +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UEB | The field is optionally present, need ON, for UE based NR DL-TDOA; otherwise it is not present. | +| CtrTrans | The field is mandatory present in the control transaction of a periodic assistance data delivery session as described in clauses 5.2.1a and 5.2.2a, for UE based NR DL-TDOA. Otherwise it is not present. | + +| NR-DL-TDOA-ProvideAssistanceData field descriptions | | +|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-DL-PRS-AssistanceData | This field specifies the assistance data reference and neighbour TRPs and provides the DL-PRS configuration for the TRPs.
Note, if this field is absent but the nr-SelectedDL-PRS-IndexList field is present, the nr-DL-PRS-AssistanceData may be provided in IE NR-Multi-RTT-ProvideAssistanceData or NR-DL-AoD-ProvideAssistanceData . | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-SelectedDL-PRS-IndexList
This field specifies the DL-PRS Resources which are applicable for this NR-DL-TDOA-ProvideAssistanceData message. | +| nr-PositionCalculationAssistance
This field provides position calculation assistance data for UE-based mode. | +| nr-DL-TDOA-Error
This field provides DL-TDOA error reasons. | +| nr-On-Demand-DL-PRS-Configurations
This field provides a set of available DL-PRS configurations which can be requested by the target device on-demand.

NOTE 1: Void
NOTE 2: If this field is absent but the nr-On-Demand-DL-PRS-Configurations-Selected-IndexList is present, the nr-On-Demand-DL-PRS-Configurations may be provided in IE NR-Multi-RTT-ProvideAssistanceData or NR-DL-AoD-ProvideAssistanceData . | +| nr-On-Demand-DL-PRS-Configurations-Selected-IndexList
This field specifies the selected available on-demand DL-PRS configurations which are applicable for this NR-DL-TDOA-ProvideAssistanceData message. | +| assistanceDataValidityArea
This field specifies the network area for which this NR-DL-TDOA-ProvideAssistanceData is valid. | +| nr-PeriodicAssistData
This field specifies the periodic assistance data for UE-based carrier phase positioning. | + +## 6.5.10.2 NR DL-TDOA Assistance Data Request + +### – NR-DL-TDOA-RequestAssistanceData + +The IE *NR-DL-TDOA-RequestAssistanceData* is used by the target device to request assistance data from a location server. + +``` +-- ASN1START +NR-DL-TDOA-RequestAssistanceData-r16 ::= SEQUENCE { + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, + nr-AdType-r16 BIT STRING { dl-prs (0), + posCalc (1) } (SIZE (1..8)), + ... + [ + nr-PosCalcAssistanceRequest-r17 BIT STRING { trpLoc (0), + beamInfo (1), + rtdInfo (2), + losNlosInfo (3), + trpTEG-Info (4), + integrityParameters-r18 (5), + pruInfo-r18 (6) + } (SIZE (1..8)) OPTIONAL, + nr-on-demand-DL-PRS-Request-r17 NR-On-Demand-DL-PRS-Request-r17 OPTIONAL, + nr-DL-PRS-ExpectedAoD-or-AoA-Request-r17 + ENUMERATED { eAoD, eAoA } OPTIONAL, + pre-configured-AssistanceDataRequest-r17 + ENUMERATED { true } OPTIONAL + ], + [ + nr-PeriodicAssistDataReq-r18 NR-PeriodicAssistDataReq-r18 OPTIONAL -- Cond PerADReq + ] +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PerADReq | This field is mandatory present if the target device requests periodic NR assistance data delivery. This field may only be included if 'pruInfo' bit in nr-PosCalcAssistanceRequest is set to '1'. | + +| NR-DL-TDOA-RequestAssistanceData field descriptions | | +|-----------------------------------------------------|------------------------------------------------------------------------------------------------------| +| nr-PhysCellID | This field specifies the NR physical cell identity of the current primary cell of the target device. | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

nr-AdType
This field indicates the requested assistance data. dl-prs means requested assistance data is nr-DL-PRS-AssistanceData, posCalc means requested assistance data is nr-PositionCalculationAssistance for UE based positioning.

| +|

nr-PosCalcAssistanceRequest
This field indicates the Position Calculation Assistance Data requested. This is represented by a bit string, with a one-value at the bit position means the particular assistance data is requested; a zero-value means not requested.

  • - bit 0 indicates whether the field nr-TRP-LocationInfo in IE NR-PositionCalculationAssistance is requested or not;
  • - bit 1 indicates whether the field nr-DL-PRS-BeamInfo in IE NR-PositionCalculationAssistance is requested or not;
  • - bit 2 indicates whether the field nr-RTD-Info in IE NR-PositionCalculationAssistance is requested or not;
  • - bit 3 indicates whether the field nr-DL-PRS-Expected-LOS-NLOS-Assistance in IE NR-PositionCalculationAssistance is requested or not;
  • - bit 4 indicates whether the field nr-DL-PRS-TRP-TEG-Info in IE NR-PositionCalculationAssistance is requested or not.
  • - bit 5 indicates whether integrity parameters, the service parameters for integrity, and bounds parameters for inter-TRP synchronization error, TRP/ARP location error and beam-related error is requested.
  • - bit 6 indicates whether the field nr-PRU-DL-Info in IE NR-PositionCalculationAssistance is requested or not.

This field may only be present if the 'posCalc' bit in nr-AdType is set to value '1'.

| +|

nr-on-demand-DL-PRS-Request
This field indicates the on-demand DL-PRS requested for DL-TDOA. This field may be included when the dl-prs bit in nr-AdType is set to value '1'.

| +|

nr-DL-PRS-ExpectedAoD-or-AoA-Request
This field, if present, indicates that the IE NR-DL-PRS-ExpectedAoD-or-AoA in NR-DL-PRS-AssistanceData is requested. Enumerated value 'eAoD' indicates that expected AoD information is requested; value 'eAoA' indicates that expected AoA information is requested.
This field may only be present if the 'dl-prs' bit in nr-AdType is set to value '1'.

| +|

pre-configured-AssistanceDataRequest
This field, if present, indicates that the target device requests pre-configured assistance data with area validity.

| +|

nr-PeriodicAssistDataReq
This field indicates the Periodic Position Calculation Assistance Data requested.

| + +## 6.5.10.3 NR DL-TDOA Location Information + +### – NR-DL-TDOA-ProvideLocationInformation + +The IE *NR-DL-TDOA-ProvideLocationInformation* is used by the target device to provide NR DL-TDOA location measurements to the location server. It may also be used to provide NR DL-TDOA positioning specific error reason. + +``` +-- ASN1START + +NR-DL-TDOA-ProvideLocationInformation-r16 ::= SEQUENCE { + nr-DL-TDOA-SignalMeasurementInformation-r16 + NR-DL-TDOA-SignalMeasurementInformation-r16 + OPTIONAL, + nr-dl-tdoa-LocationInformation-r16 NR-DL-TDOA-LocationInformation-r16 + OPTIONAL, + nr-DL-TDOA-Error-r16 NR-DL-TDOA-Error-r16 + OPTIONAL, + ..., + [[ + nr-DL-TDOA-SignalMeasurementInstances-r17 + SEQUENCE (SIZE (1..maxMeasInstances-r17)) OF + NR-DL-TDOA-SignalMeasurementInformation-r16 + OPTIONAL, -- Cond batchUEA + nr-DL-TDOA-LocationInformationInstances-r17 + SEQUENCE (SIZE (1..maxMeasInstances-r17)) OF + NR-DL-TDOA-LocationInformation-r16 + OPTIONAL -- Cond batchUEB + ]] +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| batchUEA | The field is optionally present if the field nr-DL-TDOA-SignalMeasurementInformation is absent; otherwise it is not present. | +| batchUEB | The field is optionally present if the field nr-dl-tdoa-LocationInformation is absent; otherwise it is not present. | + +## 6.5.10.4 NR DL-TDOA Location Information Elements + +### – *NR-DL-TDOA-SignalMeasurementInformation* + +The IE *NR-DL-TDOA-SignalMeasurementInformation* is used by the target device to provide NR DL-TDOA measurements to the location server. + +NOTE 1: The *dl-PRS-ReferenceInfo* defines the "RSTD reference" TRP. The *nr-RSTD*'s and *nr-RSTD-ResultDiff*'s in *nr-DL-TDOA-MeasList* are provided relative to the "RSTD reference" TRP. + +NOTE 2: The "RSTD reference" TRP may or may not be the same as the "assistance data reference" TRP provided by *nr-DL-PRS-ReferenceInfo* in IE *NR-DL-PRS-AssistanceData*. + +NOTE 3: The target device includes a value of zero for the *nr-RSTD* and *nr-RSTD-ResultDiff* of the "RSTD reference" TRP in *nr-DL-TDOA-MeasList*. + +``` +-- ASN1START + +NR-DL-TDOA-SignalMeasurementInformation-r16 ::= SEQUENCE { + dl-PRS-ReferenceInfo-r16 DL-PRS-ID-Info-r16, + nr-DL-TDOA-MeasList-r16 NR-DL-TDOA-MeasList-r16, + ... + [[ + nr-UE-RxTEG-TimingErrorMargin-r17 TEG-TimingErrorMargin-r17 OPTIONAL -- Cond UERxTEG + ]] +} + +NR-DL-TDOA-MeasList-r16 ::= SEQUENCE (SIZE(1..nrMaxTRPs-r16)) OF NR-DL-TDOA-MeasElement-r16 + +NR-DL-TDOA-MeasElement-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, + nr-CellGlobalID-r16 NCGI-r15 OPTIONAL, + nr-ARFCN-r16 ARFCN-ValueNR-r15 OPTIONAL, + nr-DL-PRS-ResourceID-r16 NR-DL-PRS-ResourceID-r16 OPTIONAL, + nr-DL-PRS-ResourceSetID-r16 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, + nr-TimeStamp-r16 NR-TimeStamp-r16, + nr-RSTD-r16 CHOICE { + k0-r16 INTEGER (0..1970049), + k1-r16 INTEGER (0..985025), + k2-r16 INTEGER (0..492513), + k3-r16 INTEGER (0..246257), + k4-r16 INTEGER (0..123129), + k5-r16 INTEGER (0..61565), + ... + kMinus1-r18 INTEGER (0..3940097), + kMinus2-r18 INTEGER (0..7880193) + }, + nr-AdditionalPathList-r16 NR-AdditionalPathList-r16 OPTIONAL, + nr-TimingQuality-r16 NR-TimingQuality-r16, + nr-DL-PRS-RSRP-Result-r16 INTEGER (0..126) OPTIONAL, + nr-DL-TDOA-AdditionalMeasurements-r16 + NR-DL-TDOA-AdditionalMeasurements-r16 + OPTIONAL, + ... + [[ + nr-UE-Rx-TEG-ID-r17 INTEGER (0..maxNumOfRxTEGs-1-r17) OPTIONAL, + nr-DL-PRS-FirstPathRSRP-Result-r17 + INTEGER (0..126) OPTIONAL, + nr-los-nlos-Indicator-r17 CHOICE { + perTRP-r17 LOS-NLOS-Indicator-r17, + perResource-r17 LOS-NLOS-Indicator-r17 + } + OPTIONAL, + nr-AdditionalPathListExt-r17 NR-AdditionalPathListExt-r17 OPTIONAL, + nr-DL-TDOA-AdditionalMeasurementsExt-r17 + ]] +} +``` + +``` + + NR-DL-TDOA-AdditionalMeasurementsExt-r17 OPTIONAL + ]], + [[ + nr-RSTD-BasedOnAggregatedResources-r18 ENUMERATED {true} OPTIONAL, + nr-AggregatedDL-PRS-ResourceSetID-List-r18 SEQUENCE (SIZE (2.. 3)) OF + NR-AggregatedDL-PRS-ResourceSetID-Element-r18 OPTIONAL, + nr-RSCPD-r18 INTEGER (0..61565) OPTIONAL, + nr-PhaseQuality-r18 NR-PhaseQuality-r18 OPTIONAL, + nr-RSCPD-AddSampleMeasurements-r18 SEQUENCE (SIZE (1..nrNumOfSamples-1-r18 )) OF + NR-RSCPD-AdditionalMeasurementElement-r18 OPTIONAL, + nr-ReportDL-PRS-MeasBasedOnSingleOrMultiHopRx-r18 + ENUMERATED { singleHop, multipleHop } OPTIONAL + ]] +} + +NR-DL-TDOA-AdditionalMeasurements-r16 ::= SEQUENCE (SIZE (1..3)) OF + NR-DL-TDOA-AdditionalMeasurementElement-r16 + +NR-DL-TDOA-AdditionalMeasurementsExt-r17 ::= SEQUENCE (SIZE (1..maxAddMeasTDOA-r17)) OF + NR-DL-TDOA-AdditionalMeasurementElement-r16 + +NR-DL-TDOA-AdditionalMeasurementElement-r16 ::= SEQUENCE { + nr-DL-PRS-ResourceID-r16 NR-DL-PRS-ResourceID-r16 OPTIONAL, + nr-DL-PRS-ResourceSetID-r16 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, + nr-Timestamp-r16 NR-Timestamp-r16, + nr-RSTD-ResultDiff-r16 CHOICE { + k0-r16 INTEGER (0..8191), + k1-r16 INTEGER (0..4095), + k2-r16 INTEGER (0..2047), + k3-r16 INTEGER (0..1023), + k4-r16 INTEGER (0..511), + k5-r16 INTEGER (0..255), + ..., + kMinus1-r18 INTEGER (0..16382), + kMinus2-r18 INTEGER (0..32764) + }, + nr-TimingQuality-r16 NR-TimingQuality-r16, + nr-DL-PRS-RSRP-ResultDiff-r16 INTEGER (0..61) OPTIONAL, + nr-AdditionalPathList-r16 NR-AdditionalPathList-r16 OPTIONAL, + ..., + [[ + nr-UE-Rx-TEG-ID-r17 INTEGER (0..maxNumOfRxTEGs-1-r17) OPTIONAL, + nr-DL-PRS-FirstPathRSRP-ResultDiff-r17 + INTEGER (0..61) OPTIONAL, + nr-los-nlos-IndicatorPerResource-r17 + LOS-NLOS-Indicator-r17 OPTIONAL, + nr-AdditionalPathListExt-r17 NR-AdditionalPathListExt-r17 OPTIONAL + ]], + [[ + nr-RSTD-BasedOnAggregatedResources-r18 ENUMERATED {true} OPTIONAL, + nr-AggregatedDL-PRS-ResourceSetID-List-r18 SEQUENCE (SIZE (2.. 3)) OF + NR-AggregatedDL-PRS-ResourceSetID-Element-r18 OPTIONAL, + nr-RSCPD-r18 INTEGER (0..61565) OPTIONAL, + nr-PhaseQuality-r18 NR-PhaseQuality-r18 OPTIONAL, + nr-RSCPD-AdditionalMeasurementsAddSample-r18 SEQUENCE (SIZE (1..nrNumOfSamples-1-r18 )) OF + NR-RSCPD-AdditionalMeasurementElement-r18 OPTIONAL, + nr-ReportDL-PRS-MeasBasedOnSingleOrMultiHopRx-r18 + ENUMERATED { singleHop, multipleHop } OPTIONAL + ]] +} + +NR-RSCPD-AdditionalMeasurementElement-r18 ::= SEQUENCE { + nr-RSCPD-Result-r18 INTEGER (0..61565) OPTIONAL, + nr-PhaseQuality-r18 NR-PhaseQuality-r18 OPTIONAL, + nr-Timestamp-r18 NR-Timestamp-r16 OPTIONAL, + ... +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------| +| UERxTEG | The field is optionally present, need OP, if the field nr-UE-Rx-TEG-ID is present; otherwise it is not present. | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-UE-RxTEG-TimingErrorMargin
This field specifies the UE Rx TEG timing error margin value for all the UE Rx TEGs within one NR-DL-TDOA-SignalMeasurementInformation . If the nr-UE-Rx-TEG-ID is present and this field is absent, the receiver should consider the UE Rx TEG timing error margin value to be the maximum applicable value as defined in TS 38.133 [46]. | +| dl-PRS-ID
This field is used along with a DL-PRS Resource Set ID and a DL-PRS Resources ID to uniquely identify a DL-PRS Resource. This ID can be associated with multiple DL-PRS Resource Sets associated with a single TRP. Each TRP should only be associated with one such ID. | +| nr-PhysCellID
This field specifies the physical cell identity of the associated TRP, as defined in TS 38.331 [35]. | +| nr-CellGlobalID
This field specifies the NCGI, the globally unique identity of a cell in NR, of the associated TRP, as defined in TS 38.331 [35]. | +| nr-ARFCN
This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID . | +| nr-TimeStamp
This field specifies the time instance at which the TOA, RSCP (if included) and DL PRS-RSRP/RSRPP (if included) measurement is performed. The nr-SFN , nr-Slot and nr-Symbol (if included) in IE NR-TimeStamp correspond to the TRP provided in dl-PRS-ReferenceInfo as specified in TS 38.214 [45]. Note, the TOA measurement refers to the TOA of this neighbour TRP or the reference TRP, as applicable, used to determine the nr-RSTD or nr-RSTD-ResultDiff . | +| nr-RSTD
This field specifies the relative timing difference between this neighbour TRP and the PRS reference TRP, as defined in TS 38.215 [36]. Mapping of the measured quantity is defined as in TS 38.133 [46]. | +| nr-AdditionalPathList
This field specifies one or more additional detected path timing values for the TRP or resource, relative to the path timing used for determining the nr-RSTD value. If this field was requested but is not included, it means the UE did not detect any additional path timing values. If this field is present, the field nr-AdditionalPathListExt shall be absent. | +| nr-TimingQuality
This field specifies the target device's best estimate of the quality of the TOA measurement. Note, the TOA measurement refers to the TOA of this neighbour TRP or the reference TRP, as applicable, used to determine the nr-RSTD or nr-RSTD-ResultDiff . | +| nr-DL-PRS-RSRP-Result
This field specifies the NR DL-PRS reference signal received power (DL PRS-RSRP) measurement, as defined in TS 38.215 [36]. The mapping of the quantity is defined as in TS 38.133 [46]. | +| nr-DL-TDOA-AdditionalMeasurements
This field provides up to 3 additional RSTD measurements per pair of TRPs, with each measurement between a different pair of DL-PRS Resources or DL-PRS Resource Sets of the DL-PRS for those TRPs [45]. If this field is present, the field nr-DL-TDOA-AdditionalMeasurementsExt shall be absent. | +| nr-UE-Rx-TEG-ID
This field provides the ID of the UE Rx TEG associated with the TOA measurement. Note, the TOA measurement refers to the TOA of this neighbour TRP or the reference TRP, as applicable, used to determine the nr-RSTD or nr-RSTD-ResultDiff . When different UE Rx TEGs for RSTD measurements are requested, the maximum number of reported RSTD measurements associated with different DL-PRS Resources per UE Rx TEG per target TRP is 4. | +| nr-DL-PRS-FirstPathRSRP-Result
This field specifies the NR DL-PRS reference signal received path power (DL PRS-RSRPP) of the first detected path in time, as defined in TS 38.215 [36]. The mapping of the measured quantity is defined as in TS 38.133 [46]. | +| nr-los-nlos-Indicator
This field specifies the target device's best estimate of the LOS or NLOS of the TOA measurement for the TRP or resource. Note, the TOA measurement refers to the TOA of this neighbour TRP or the reference TRP, as applicable, used to determine the nr-RSTD or nr-RSTD-ResultDiff .
This field also applies to specify the target device's best estimate of the LOS or NLOS of the RSCP measurement for the TRP or resource. Note, the RSCP measurement refers to the RSCP of this neighbour TRP or the reference TRP, as applicable, used to determine the nr-RSCPD or nr-RSCPD-ResultDiff .
NOTE: If the requested type or granularity in nr-los-nlos-IndicatorRequest is not possible, the target device may provide a different type and granularity for the estimated LOS-NLOS-Indicator . | +| nr-AdditionalPathListExt
This field provides up to 8 additional detected path timing values for the TRP or resource, relative to the path timing used for determining the nr-RSTD value. If this field was requested but is not included, it means the UE did not detect any additional path timing values. If this field is present, the field nr-AdditionalPathList shall be absent. | +| nr-DL-TDOA-AdditionalMeasurementsExt
This field, in addition to the measurements provided in NR-DL-TDOA-MeasElement , provides TOA measurements of up to 4 DL-PRS Resources of a TRP with different UE Rx TEGs. For a certain DL-PRS Resource, there can be up to 8 TOA measurement results with respect to different Rx TEGs. If this field is present, the field nr-DL-TDOA-AdditionalMeasurements shall be absent. | +| nr-RSTD-BasedOnAggregatedResources
This field indicates whether the measurement is based on aggregation across PFLs for DL-TDOA. | + +**nr-AggregatedDL-PRS-ResourceSetID-List** + +This field provides the PRS resource set IDs and the PRS resource IDs for the aggregated measurement which are used for timing measurement results. If the field is present, the field *nr-DL-PRS-ResourceID* and *nr-DL-PRS-ResourceSetID* should not be included. + +**nr-RSCPD** + +This field specifies the NR DL reference signal carrier phase difference measurement, as defined in TS 38.215 [36]. Mapping of the measured quantity is defined as in TS 38.133 [46]. The target and the reference TRP are in the same PFL. + +**nr-PhaseQuality** + +This field specifies the target device's best estimate of the quality of the RSCPD measurement. + +**nr-RSCPD-AddSampleMeasurements** + +This field, in addition to the measurements provided in *NR-DL-TDOA-MeasElement*, provides up to 3 RSCPD measurements associated with the *nr-RSTD* in *NR-DL-TDOA-MeasElement*. + +**nr-ReportDL-PRS-MeasBasedOnSingleOrMultiHopRx** + +This field indicates that the reported measurement is based on receiving single or multiple hops of DL PRS. + +**nr-RSTD-ResultDiff** + +This field provides the additional DL RSTD measurement result relative to *nr-RSTD*. The RSTD value of this measurement is obtained by adding the value of this field to the value of the *nr-RSTD* field. The mapping of the field is defined in TS 38.133 [46]. + +**nr-DL-PRS-RSRP-ResultDiff** + +This field provides the additional DL-PRS RSRP measurement result relative to *nr-DL-PRS-RSRP-Result*. The DL-PRS RSRP value of this measurement is obtained by adding the value of this field to the value of the *nr-DL-PRS-RSRP-Result* field. The mapping of the field is defined in TS 38.133 [46]. + +**nr-DL-PRS-FirstPathRSRP-ResultDiff** + +This field specifies the additional NR DL PRS reference signal received path power (DL PRS-RSRPP) of the first detected path in time relative to *nr-DL-PRS-FirstPathRSRP-Result*. The DL-PRS RSRPP of first path value of this measurement is obtained by adding the value of this field to the value of the *nr-DL-PRS-FirstPathRSRP-Result* field. The mapping of the field is defined in TS 38.133 [46]. + +**nr-los-nlos-IndicatorPerResource** + +This field specifies the target device's best estimate of the LOS or NLOS of the TOA measurement for the resource. Note, the TOA measurement refers to the TOA of this neighbour TRP or the reference TRP, as applicable, used to determine the *nr-RSTD* or *nr-RSTD-ResultDiff*. + +This field may only be present if the field *nr-LOS-NLOS-Indicator* choice indicates *perResource*. + +**nr-RSCPD-AdditionalMeasurements** + +This field, provides up to 4 RSCPD measurements associated with the TOA measurement in *NR-DL-TDOA-AdditionalMeasurementElement*. + +**nr-RSCPD-ResultDiff** + +This field provides the additional RSCPD measurement result relative to *nr-RSCPD*. The RSCPD value of this measurement is obtained by adding the value of this field to the value of the *nr-RSCPD* field. + +## NR-DL-TDOA-LocationInformation + +The IE *NR-DL-TDOA-LocationInformation* is included by the target device when location information derived using NR DL-TDOA is provided to the location server. + +``` +-- ASN1START +NR-DL-TDOA-LocationInformation-r16 ::= SEQUENCE { + measurementReferenceTime-r16 CHOICE { + systemFrameNumber-r16 NR-TimeStamp-r16, + utc-time-r16 UTCTime, + ... + } + ..., + [[ + locationCoordinates-r17 LocationCoordinates OPTIONAL, -- Cond batch1 + locationSource-r17 LocationSource-r13 OPTIONAL -- Cond batch2 + ]] +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| batch1 | The field is mandatory present if the field nr-DL-TDOA-LocationInformationInstances is present in IE NR-DL-TDOA-ProvideLocationInformation ; otherwise it is not present. | +| batch2 | The field is optionally present, need ON, if the field nr-DL-TDOA-LocationInformationInstances is present in IE NR-DL-TDOA-ProvideLocationInformation ; otherwise it is not present. | + +| NR-DL-TDOA-LocationInformation field descriptions | | +|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| measurementReferenceTime | This field specifies the time for which the location estimate is valid. | +| locationCoordinates | This field provides a location estimate using one of the geographic shapes defined in TS 23.032 [15]. NOTE 1. | +| locationSource | This field provides the source positioning technology for the location estimate. NOTE 1. | + +NOTE 1: In the case of *locationCoordinates* for multiple NR positioning methods are provided, the *locationCoordinates* and *locationSource* shall be present in only one of NR-DL-TDOA-*ProvideLocationInformation* or NR-DL-AoD-*ProvideLocationInformation*. + +## 6.5.10.5 NR DL-TDOA Location Information Request + +### – *NR-DL-TDOA-RequestLocationInformation* + +The IE *NR-DL-TDOA-RequestLocationInformation* is used by the location server to request NR DL-TDOA location measurements from a target device. + +``` +-- ASN1START + +NR-DL-TDOA-RequestLocationInformation-r16 ::= SEQUENCE { + nr-DL-PRS-RstdMeasurementInfoRequest-r16 ENUMERATED { true } OPTIONAL, -- Need ON + nr-RequestedMeasurements-r16 BIT STRING { prsrspReq (0), + firstPathRsrpReq-r17 (1), + jointMeasurementsReq-r18 (2) + } (SIZE(1..8)), + nr-AssistanceAvailability-r16 BOOLEAN, + nr-DL-TDOA-ReportConfig-r16 NR-DL-TDOA-ReportConfig-r16 OPTIONAL, -- Need ON + additionalPaths-r16 ENUMERATED { requested } OPTIONAL, -- Need ON + ..., + [[ + nr-UE-RxTEG-Request-r17 ENUMERATED { requested } OPTIONAL, -- Need ON + nr-los-nlos-IndicatorRequest-r17 SEQUENCE { + type-r17 LOS-NLOS-IndicatorType1-r17, + granularity-r17 LOS-NLOS-IndicatorGranularity1-r17, + ... + } + OPTIONAL, -- Need ON + additionalPathsExt-r17 ENUMERATED { requested } OPTIONAL, -- Need ON + additionalPathsDL-PRS-RSRP-Request-r17 ENUMERATED { requested } OPTIONAL, -- Need ON + multiMeasInSameReport-r17 ENUMERATED { requested } OPTIONAL, -- Need ON + ]], + [[ + nr-DL-PRS-JointMeasurementRequested-r18 SEQUENCE (SIZE (2..3)) OF + INTEGER (0..nrMaxFreqLayers-1-r16) OPTIONAL, -- Need ON + nr-DL-PRS-RxHoppingRequest-r18 ENUMERATED { requested } OPTIONAL, -- Need ON + nr-DL-PRS-RxHoppingTotalBandwidth-r18 CHOICE { + fr1 ENUMERATED { mhz40, mhz50, mhz80, mhz100}, + fr2 ENUMERATED { mhz100, mhz200, mhz400} + } + OPTIONAL, -- Need ON + nr-DL-PRS-RSCPD-Request-r18 ENUMERATED { requested } OPTIONAL, -- Need ON + ]] +} + +NR-DL-TDOA-ReportConfig-r16 ::= SEQUENCE { + maxDL-PRS-RSTD-MeasurementsPerTRP-Pair-r16 INTEGER (1..4) OPTIONAL, -- Need ON + timingReportingGranularityFactor-r16 INTEGER (0..5) OPTIONAL, -- Need ON + ..., + [[ + measureSameDL-PRS-ResourceWithDifferentRxTEGs-r17 + ENUMERATED { n0, n2, n3, n4, n6, n8, ... } + ]]] +``` + +| | | | +|--------------------------------------------|-------------------------------|----------------------| +| reducedDL-PRS-ProcessingSamples-r17 | ENUMERATED { requested, ... } | OPTIONAL, -- Need ON | +| lowerRxBBeamSweepingFactor-FR2-r17 | ENUMERATED { requested } | OPTIONAL -- Need ON | +| ]], | | | +| [[ | | | +| timingReportingGranularityFactorExt-r18 | INTEGER (6..7) | OPTIONAL, -- Need ON | +| nr-DL-PRS-MeasurementTimeWindowsConfig-r18 | | | +| NR-DL-PRS-MeasurementTimeWindowsConfig-r18 | | OPTIONAL -- Need ON | +| ]] | | | +| } | | | +| -- ASN1STOP | | | + +### NR-DL-TDOA-RequestLocationInformation field descriptions + +#### nr-DL-PRS-RstdMeasurementInfoRequest + +This field indicates whether the target device is requested to report DL-PRS Resource ID(s) or DL-PRS Resource Set ID(s) used for determining the timing of each TRP in RSTD measurements. The *jointMeasurementsReq* means that the target device is requested to perform joint measurement across aggregated PFLs for DL-TDOA. + +#### nr-RequestedMeasurements + +This field specifies the NR DL-TDOA measurements requested. This is represented by a bit string, with a one-value at the bit position means the particular measurement is requested; a zero-value means not requested. + +#### nr-AssistanceAvailability + +This field indicates whether the target device may request additional PRS assistance data from the server. TRUE means allowed and FALSE means not allowed. + +#### additionalPaths + +This field, if present, indicates that the target device is requested to provide the *nr-AdditionalPathList* in IE *NR-DL-TDOA-SignalMeasurementInformation*. If this field is present, the field *additionalPathsExt* shall be absent. + +#### nr-UE-RxTEG-Request + +This field, if present, indicates that the target device is requested to provide the *nr-UE-Rx-TEG-ID* in IE *NR-DL-TDOA-SignalMeasurementInformation*. + +#### nr-los-nlos-IndicatorRequest + +This field, if present, indicates that the target device is requested to provide the indicated type and granularity of the estimated LOS-NLOS-Indicator in the *NR-DL-TDOA-SignalMeasurementInformation*. + +#### additionalPathsExt + +This field, if present, indicates that the target device is requested to provide the *nr-AdditionalPathListExt* in IE *NR-DL-TDOA-SignalMeasurementInformation*. If this field is present, the field *additionalPaths* shall be absent. + +#### additionalPathsDL-PRS-RSRP-Request + +This field, if present, indicates that the target device is requested to provide the *nr-DL-PRS-RSRPP* for the additional paths in fields *nr-AdditionalPathList* or *nr-AdditionalPathListExt*. + +#### multiMeasInSameReport + +This field, if present, indicates that the target device is requested to provide multiple measurement instances in a single measurement report; i.e., include the *nr-DL-TDOA-SignalMeasurementInstances* (in the case of UE-assisted mode is requested) or *nr-DL-TDOA-LocationInformationInstances* (in the case of UE-based mode is requested) in IE *NR-DL-TDOA-ProvideLocationInformation*. + +#### nr-DL-PRS-JointMeasurementRequested + +This field, if present, indicates the target device is requested to perform joint measurements on the indicated two or three PFLs. The field can be present if *jointMeasurementsReq* in *nr-RequestedMeasurements* is set to one-value. Otherwise, it is absent. Value 0 corresponds to the first frequency layer provided in *nr-DL-PRS-AssistanceDataList*, value 1 to the second frequency layer in *nr-DL-PRS-AssistanceDataList*, and so on. + +#### nr-DL-PRS-RxHoppingRequest + +This field, if present, indicates that the target device is requested to perform DL PRS Rx hopping measurements and reporting. + +#### nr-DL-PRS-RxHoppingTotalBandwidth + +This field, if present, indicates the total bandwidth of all hops in MHz. + +#### nr-DL-PRS-RSCPD-Request + +This field, if present, indicates that the target device is requested to provide the RSCPD measurement together with DL-PRS RSTD measurement. + +#### maxDL-PRS-RSTD-MeasurementsPerTRP-Pair + +This field specifies the maximum number of DL-PRS RSTD measurements per pair of TRPs. The maximum number is defined across all Positioning Frequency Layers. When requested for aggregated measurements by the location server, this field specifies the maximum number of aggregated DL-PRS RSTD measurements per pair of TRPs. The maximum number is defined across all Positioning Frequency Layers. + +**timingReportingGranularityFactor, timingReportingGranularityFactorExt** + +This field specifies the recommended reporting granularity for the DL RSTD measurements. Value (0..5) corresponds to (k0..k5) and value (6..7) corresponds to (kMinus1..kMinus2) used for *nr-RSTD* and *nr-RSTD-ResultDiff* in *NR-DL-TDOA-MeasElement*. The UE may select a different granularity value for *nr-RSTD* and *nr-RSTD-ResultDiff*. The *timingReportingGranularityFactorExt* should not be included by the location server and shall be ignored by the target device if *timingReportingGranularityFactor* is included. The *timingReportingGranularityFactor* should not be included by the location server and shall be ignored by the target device if *timingReportingGranularityFactorExt* is included. + +**measureSameDL-PRS-ResourceWithDifferentRxTEGs** + +This field, if present, indicates that the target device is requested to measure the same DL-PRS Resource of a TRP with *N* different UE Rx TEGs. Enumerated value 'n0' indicates that the number *N* of different UE Rx TEGs to measure the same DL-PRS Resource can be determined by the target device, value 'n2' indicates that the target device is requested to measure the same DL-PRS Resource of a TRP with 2 different UE Rx TEGs, value 'n3' indicates that the target device is requested to measure the same DL-PRS Resource of a TRP with 3 different UE Rx TEGs, and so on. If this field is present, the field *nr-UE-RxTEG-Request* should also be present. When the location server requests aggregated measurements, the target device is requested to measure the same aggregated DL-PRS Resources of a TRP with *N* different UE Rx TEGs. + +**reducedDL-PRS-ProcessingSamples** + +This field, if present and set to 'requested', indicates that the target device is requested to perform the requested measurements with reduced number of samples (*M*=1 or *M*=2) as specified in TS 38.133 [46]. When requested for aggregated measurements by the location server, this field indicates processing of reduced number of samples for the aggregated measurements. + +**lowerRxBeamSweepingFactor-FR2** + +This field, if present, indicates that the target device is requested to use a lower Rx beam sweeping factor than 8 for FR2 according to UE's capability. When requested for aggregated measurements by the location server, this field indicates that the target device is requested to use a lower Rx beam sweeping factor than 8 for FR2 according to UE's capability for the aggregated measurements. + +**NR-DL-PRS-MeasurementTimeWindowsConfig** + +This field indicates DL-PRS resource set(s) occurring within time window(s) for performing measurements where the time window is indicated by a start time, periodicity, offset and duration. + +## 6.5.10.6 NR DL-TDOA Capability Information + +### – NR-DL-TDOA-ProvideCapabilities + +The IE *NR-DL-TDOA-ProvideCapabilities* is used by the target device to indicate its capability to support NR DL-TDOA and to provide its NR DL-TDOA positioning capabilities to the location server. + +``` +-- ASN1START +NR-DL-TDOA-ProvideCapabilities-r16 ::= SEQUENCE { + nr-DL-TDOA-Mode-r16 PositioningModes, + nr-DL-TDOA-PRS-Capability-r16 NR-DL-PRS-ResourcesCapability-r16, + nr-DL-TDOA-MeasurementCapability-r16 NR-DL-TDOA-MeasurementCapability-r16, + nr-DL-PRS-QCL-ProcessingCapability-r16 NR-DL-PRS-QCL-ProcessingCapability-r16, + nr-DL-PRS-ProcessingCapability-r16 NR-DL-PRS-ProcessingCapability-r16, + additionalPathsReport-r16 ENUMERATED { supported } OPTIONAL, + periodicalReporting-r16 PositioningModes OPTIONAL, + ..., + [[ + ten-ms-unit-ResponseTime-r17 PositioningModes OPTIONAL, + nr-PosCalcAssistanceSupport-r17 BIT STRING { + trpLocSup (0), + beamInfoSup (1), + rtdInfoSup (2), + trpTEG-InfoSup (3), + integritySup-r18 (4), + pruInfoSup-r18 (5) + } (SIZE (1..8)) OPTIONAL, + nr-los-nlos-AssistanceDataSupport-r17 SEQUENCE { + type-r17 LOS-NLOS-IndicatorType2-r17, + granularity-r17 LOS-NLOS-IndicatorGranularity2-r17, + ... + } OPTIONAL, + nr-DL-PRS-ExpectedAoD-or-AoA-Sup-r17 BIT STRING { + eAoD (0), + eAoA (1) + } (SIZE (1..8)) OPTIONAL, + nr-DL-TDOA-On-Demand-DL-PRS-Support-r17 NR-On-Demand-DL-PRS-Support-r17 OPTIONAL, + nr-los-nlos-IndicatorSupport-r17 SEQUENCE { + type-r17 LOS-NLOS-IndicatorType2-r17, + granularity-r17 LOS-NLOS-IndicatorGranularity2-r17, + ... + } + ]] +``` + +``` + +additionalPathsExtSupport-r17 } OPTIONAL, +scheduledLocationRequestSupported-r17 ENUMERATED { n4, n6, n8 } OPTIONAL, +nr-dl-prs-AssistanceDataValidity-r17 ScheduledLocationTimeSupportPerMode-r17 OPTIONAL, + area-validity-r17 INTEGER (1..maxNrOfAreas-r17) OPTIONAL, + ... + } OPTIONAL, +multiMeasInSameMeasReport-r17 ENUMERATED { supported } OPTIONAL, +mg-ActivationRequest-r17 ENUMERATED { supported } OPTIONAL +]], +[[ +posMeasGapSupport-r17 ENUMERATED { supported } OPTIONAL +]], +[[ +multiLocationEstimateInSameMeasReport-r17 ENUMERATED { supported } OPTIONAL +]], +[[ +locationCoordinateTypes-r18 LocationCoordinateTypes OPTIONAL, +symbolTimeStampSupport-r18 ENUMERATED { supported } OPTIONAL, +periodicAssistanceData-r18 BIT STRING { solicited (0), + unsolicited (1) } (SIZE (1..8)) OPTIONAL, +nr-DL-TDOA-PosIntegritySupport-r18 ENUMERATED { supported } OPTIONAL +]] +} +-- ASN1STOP + +``` + +### NR-DL-TDOA-ProvideCapabilities field descriptions + +#### nr-DL-TDOA-Mode + +This field specifies the NR DL-TDOA mode(s) supported by the target device. + +#### periodicalReporting + +This field, if present, specifies the positioning modes for which the target device supports *periodicalReporting*. This is represented by a bit string, with a one-value at the bit position means *periodicalReporting* for the positioning mode is supported; a zero-value means not supported. If this field is absent, the target device does not support *periodicalReporting* in *CommonEsRequestLocationInformation*. + +#### ten-ms-unit-ResponseTime + +This field, if present, specifies the positioning modes for which the target device supports the enumerated value '*ten-milli-seconds*' in the IE *ResponseTime* in IE *CommonEsRequestLocationInformation*. This is represented by a bit string, with a one-value at the bit position means '*ten-milli-seconds*' response time unit for the positioning mode is supported; a zero-value means not supported. If this field is absent, the target device does not support '*ten-milli-seconds*' response time unit in *CommonEsRequestLocationInformation*. + +#### nr-PosCalcAssistanceSupport + +This field indicates the Position Calculation Assistance Data supported by the target device for UE-based DL-TDOA. This is represented by a bit string, with a one-value at the bit position means the particular assistance data is supported; a zero-value means not supported. + +- bit 0 indicates whether the field *nr-TRP-LocationInfo* in IE *NR-PositionCalculationAssistance* is supported or not; +- bit 1 indicates whether the field *nr-DL-PRS-BeamInfo* in IE *NR-PositionCalculationAssistance* is supported or not; +- bit 2 indicates whether the field *nr-RTD-Info* in IE *NR-PositionCalculationAssistance* is supported or not; +- bit 3 indicates whether the field *nr-DL-PRS-TRP-TEG-Info* in IE *NR-PositionCalculationAssistance* is supported or not. The UE can indicate this bit only if the UE supports *prs-ProcessingCapabilityBandList* and any of *maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer*, *maxNrOfTRP-AcrossFreqs*, *maxNrOfPosLayer*, *maxNrOfDL-PRS-ResourcesPerResourceSet* and *maxNrOfDL-PRS-ResourcesPerPositioningFrequencyLayer*. Otherwise, the UE does not include this field. +- bit 4 indicates whether the target service supports the range of integrity risk (IR) for which the integrity assistance data are valid. +- bit 5 indicates whether the field *nr-PRU-DL-Info* in IE *NR-PositionCalculationAssistance* is supported or not. + +#### nr-los-nlos-AssistanceDataSupport + +This field, if present, indicates that the target device supports the *NR-DL-PRS-ExpectedLOS-NLOS-Assistance* in IE *NR-PositionCalculationAssistance*: + +- *type* indicates whether the target device supports '*hard*' value or '*hard*' and '*soft*' value in *LOS-NLOS-Indicator* in IE *NR-DL-PRS-ExpectedLOS-NLOS-Assistance*. +- *granularity* indicates whether the target device supports *nr-los-nlos-indicator* in IE *NR-DL-PRS-ExpectedLOS-NLOS-Assistance* '*per-trp*', '*per-resource*', or both. + +The UE can include this field only if the UE supports one of *maxDL-PRS-RSRP-MeasurementFR1*, *maxDL-PRS-RSRP-MeasurementFR2*, *dl-RSTD-MeasurementPerPairOfTRP-FR1*, *dl-RSTD-MeasurementPerPairOfTRP-FR2*, *maxNrOfRx-TX-MeasFR1*, *maxNrOfRx-TX-MeasFR2*, *supportOfRSRP-MeasFR1* and *supportOfRSRP-MeasFR2*. Otherwise, the UE does not include this field. + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-DL-PRS-ExpectedAoD-or-AoA-Sup
This field, if present, indicates that the target device supports the NR-DL-PRS-ExpectedAoD-or-AoA in NR-DL-PRS-AssistanceData . | +| nr-DL-TDOA-On-Demand-DL-PRS-Support
This field, if present, indicates that the target device supports on-demand DL-PRS requests. | +| nr-los-nlos-IndicatorSupport
This field, if present, indicates that the target device supports nr-los-nlos-Indicator reporting in IE NR-DL-TDOA-SignalMeasurementInformation .
  • - type indicates whether the target device supports 'hard' value or 'hard' and 'soft' value in IE LOS-NLOS-Indicator.
  • - granularity indicates whether the target device supports LOS-NLOS-Indicator reporting per TRP, per DL-PRS Resource, or both.
NOTE: A single value is reported when both Multi-RTT and DL-TDOA are supported. | +| additionalPathsExtSupport
This field, if present, indicates that the target device supports the nr-AdditionalPathListExt reporting in IE NR-DL-TDOA-SignalMeasurementInformation . The enumerated value indicates the number of additional paths supported by the target device.
NOTE: The supportOfDL-PRS-FirstPathRSRP in IE NR-DL-TDOA-MeasurementCapability also applies to the additional paths. | +| scheduledLocationRequestSupported
This field, if present, specifies the positioning modes for which the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonIEsRequestLocationInformation – and the time base(s) supported for the scheduled location time for each positioning mode. If this field is absent, the target device does not support scheduled location requests. | +| nr-dl-prs-AssistanceDataValidity
This field, if present, indicates that the target device supports validity conditions for pre-configured assistance data and comprises the following subfields:
  • - area-validity indicates that the target device supports pre-configured assistance data with area validity. The integer number indicates the maximum number of areas the target device supports.
| +| multiMeasInSameMeasReport
This field, if present, indicates that the target device supports multiple measurement instances in a single measurement report. | +| mg-ActivationRequest
This field, if present, indicates that the target device supports UL MAC CE for positioning measurement gap activation/deactivation request for DL-PRS measurements. The UE can include this field only if the UE supports mg-ActivationRequestPRS-Meas and mg-ActivationCommPRS-Meas defined in TS 38.331 [35]. | +| posMeasGapSupport
This field, if present, indicates that the target device supports pre-configured positioning measurement gap for DL-PRS measurements. The UE can include this field only if the UE supports mg-ActivationCommPRS-Meas defined in TS 38.331 [35]. | +| multiLocationEstimateInSameMeasReport
This field, if present, indicates that the target device supports multiple location estimate instances in a single measurement report. | +| locationCoordinateTypes
This field indicates the geographical location coordinate types that a target device supports for UE-based DL-TDOA. TRUE indicates that a location coordinate type is supported and FALSE that it is not. | +| symbolTimeStampSupport
This field, if present, indicates that the target device supports reporting timestamp in terms of radio frame timing down to OFDM symbol level. | +| periodicAssistanceData
This field identifies the periodic NR assistance data delivery procedures supported by the target device. This is represented by a bit string, with a one value at the bit position means the periodic NR assistance data delivery procedure is supported; a zero value means not supported. Bit 0 (solicited) represents the procedure according to clause 5.2.1a; bit (1) (unsolicited) represents the procedure according to clause 5.2.2a. | +| nr-DL-TDOA-PosIntegritySupport
This field, if present, indicates that the target device supports the RAT-dependent positioning integrity for DL-TDOA. | + +## 6.5.10.6a NR DL-TDOA Capability Information Elements + +### – NR-DL-TDOA-MeasurementCapability + +The IE *NR-DL-TDOA-MeasurementCapability* defines the DL-TDOA measurement capability. The UE can include this IE only if the UE supports *NR-DL-PRS-ResourcesCapability* for DL-TDOA. Otherwise, the UE does not include this IE. + +``` + +-- ASN1START + +NR-DL-TDOA-MeasurementCapability-r16 ::= SEQUENCE { + dl-RSTD-MeasurementPerPairOfTRP-FR1-r16 INTEGER (1..4), + dl-RSTD-MeasurementPerPairOfTRP-FR2-r16 INTEGER (1..4), + supportOfDL-PRS-RSRP-MeasFR1-r16 ENUMERATED { supported } OPTIONAL, + supportOfDL-PRS-RSRP-MeasFR2-r16 ENUMERATED { supported } OPTIONAL, + ... + [ + nr-UE-TEG-Capability-r17 NR-UE-TEG-Capability-r17 OPTIONAL, + dl-tdoa-MeasCapabilityBandList-r17 SEQUENCE (SIZE (1..nrMaxBands-r16)) OF + DL-TDOA-MeasCapabilityPerBand-r17 OPTIONAL + ] +} + +DL-TDOA-MeasCapabilityPerBand-r17 ::= SEQUENCE { + freqBandIndicatorNR-r17 FreqBandIndicatorNR-r16, + supportOfDL-PRS-FirstPathRSRP-r17 ENUMERATED { supported } OPTIONAL, + dl-PRS-MeasRRC-Inactive-r17 ENUMERATED { supported } OPTIONAL, + ... + [ + supportOfDL-PRS-BWA-RRC-Connected-r18 ENUMERATED { supported } OPTIONAL, + supportOfDL-PRS-BWA-RRC-Inactive-r18 ENUMERATED { supported } OPTIONAL, + supportOfDL-PRS-BWA-RRC-Idle-r18 ENUMERATED { supported } OPTIONAL + ] +} + +-- ASN1STOP + +``` + +#### **NR-DL-TDOA-MeasurementCapability field descriptions** + +| | | +|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-RSTD-MeasurementPerPairOfTRP-FR1 | Indicates number of DL RSTD measurements per pair of TRPs on FR1. | +| dl-RSTD-MeasurementPerPairOfTRP-FR2 | Indicates number of DL RSTD measurements per pair of TRPs on FR2. | +| supportOfDL-PRS-RSRP-MeasFR1 | Indicates whether the UE supports DL-PRS RSRP measurement for DL-TDOA on FR1. | +| supportOfDL-PRS-RSRP-MeasFR2 | Indicates whether the UE supports DL-PRS RSRP measurement for DL-TDOA on FR2. | +| nr-UE-TEG-Capability | Indicates the UE TEG capability. | +| supportOfDL-PRS-FirstPathRSRP | Indicates whether the target device supports DL-PRS RSRPP of first path measurement for DL-TDOA. The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList . Otherwise, the UE does not include this field. The UE supporting additionalPathsReport and supportOfDL-PRS-FirstPathRSRP shall support RSRPP reporting for K=1 or 2 additional paths. | +| dl-PRS-MeasRRC-Inactive | This field, if present, indicates that the target device supports DL-PRS measurement in RRC_INACTIVE state. The UE can include this field only if the UE supports maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer , maxNrOfTRP-AcrossFreqs , maxNrOfPosLayer and dl-PRS-BufferType-RRC-Inactive . Otherwise, the UE does not include this field.
NOTE 1: This capability is applicable to both, UE-assisted and UE-based DL-TDOA.
NOTE 2: The capabilities NR-DL-PRS-ResourcesCapability , dl-RSTD-MeasurementPerPairOfTRP-FR1 , dl-RSTD-MeasurementPerPairOfTRP-FR2 , supportOfDL-PRS-RSRP-MeasFR1 , supportOfDL-PRS-RSRP-MeasFR2 , simul-NR-DL-AoD-DL-TDOA are the same in RRC_INACTIVE state. | +| supportOfDL-PRS-BWA-RRC-Connected | Indicates whether the target device supports PRS bandwidth aggregation in RRC_CONNECTED for DL-TDOA. The UE can include this field only if the UE supports maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer , maxNrOfTRP-AcrossFreqs , maxNrOfPosLayer and prs-BWA-TwoContiguousIntrabandInMG-RRC-Connected . Otherwise, the UE does not include this field. | +| supportOfDL-PRS-BWA-RRC-Inactive | Indicates whether the target device supports PRS bandwidth aggregation in RRC_INACTIVE for DL-TDOA. The UE can include this field only if the UE supports dl-PRS-MeasRRC-Inactive and prs-BWA-TwoContiguousIntrabandInMG-RRC-IdleAndInactive . Otherwise, the UE does not include this field. | +| supportOfDL-PRS-BWA-RRC-Idle | Indicates the target device whether supports PRS bandwidth aggregation in RRC_IDLE for DL-TDOA. The UE can include this field only if the UE supports of PRS measurement in RRC_IDLE and prs-BWA-TwoContiguousIntrabandInMG-RRC-IdleAndInactive . Otherwise, the UE does not include this field. | + +## 6.5.10.7 NR DL-TDOA Capability Information Request + +### – *NR-DL-TDOA-RequestCapabilities* + +The IE *NR-DL-TDOA-RequestCapabilities* is used by the location server to request the capability of the target device to support NR DL-TDOA and to request NR DL-TDOA positioning capabilities from a target device. + +``` +-- ASN1START + +NR-DL-TDOA-RequestCapabilities-r16 ::= SEQUENCE { + ... +} + +-- ASN1STOP +``` + +## 6.5.10.8 NR DL-TDOA Error Elements + +### – *NR-DL-TDOA-Error* + +The IE *NR-DL-TDOA-Error* is used by the location server or target device to provide NR DL-TDOA error reasons to the target device or location server, respectively. + +``` +-- ASN1START + +NR-DL-TDOA-Error-r16 ::= CHOICE { + locationServerErrorCauses-r16 NR-DL-TDOA-LocationServerErrorCauses-r16, + targetDeviceErrorCauses-r16 NR-DL-TDOA-TargetDeviceErrorCauses-r16, + ... +} + +-- ASN1STOP +``` + +### – *NR-DL-TDOA-LocationServerErrorCauses* + +The IE *NR-DL-TDOA-LocationServerErrorCauses* is used by the location server to provide NR DL-TDOA error reasons to the target device. + +``` +-- ASN1START + +NR-DL-TDOA-LocationServerErrorCauses-r16 ::= SEQUENCE { + cause-r16 ENUMERATED { undefined, + assistanceDataNotSupportedByServer, + assistanceDataSupportedButCurrentlyNotAvailableByServer, + notProvidedAssistanceDataNotSupportedByServer, + ..., + on-demand-dl-prs-NotSupportedByServer-v1700, + on-demand-dl-prs-SupportedButCurrentlyNotAvailableByServer-v1700 + }, + ... +} + +-- ASN1STOP +``` + +### – *NR-DL-TDOA-TargetDeviceErrorCauses* + +The IE *NR-DL-TDOA-TargetDeviceErrorCauses* is used by the target device to provide NR DL-TDOA error reasons to the location server. + +``` +-- ASN1START + +NR-DL-TDOA-TargetDeviceErrorCauses-r16 ::= SEQUENCE { + cause-r16 ENUMERATED { undefined, + assistance-data-missing, + unableToMeasureAnyTRP, + attemptedButUnableToMeasureSomeNeighbourTRPs, + thereWereNotEnoughSignalsReceivedForUeBasedDL-TDOA, + }, + ... +} + +-- ASN1STOP +``` + +``` + + locationCalculationAssistanceDataMissing, + ... + }, + ..., + [[ + remoteUE-Indication-r18 ENUMERATED {true} OPTIONAL -- Cond NR + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------| +| NR | This field is optionally present, need OR, for NR access. Otherwise it is not present. | + +| NR-DL-TDOA-TargetDeviceErrorCauses field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------| +| remoteUE-Indication
This field indicates whether the target device in NR access is configured as a L2 U2N Remote UE. | + +## 6.5.11 NR DL-AoD Positioning + +This clause defines the information elements for NR downlink AoD positioning (TS 38.305 [40]). + +### 6.5.11.1 NR DL-AoD Assistance Data + +#### – NR-DL-AoD-ProvideAssistanceData + +The IE *NR-DL-AoD-ProvideAssistanceData* is used by the location server to provide assistance data to enable UE-assisted and UE-based NR DL-AoD. It may also be used to provide NR DL-AoD positioning specific error reason. + +``` + +-- ASN1START + +NR-DL-AoD-ProvideAssistanceData-r16 ::= SEQUENCE { + nr-DL-PRS-AssistanceData-r16 NR-DL-PRS-AssistanceData-r16 OPTIONAL, -- Need ON + nr-SelectedDL-PRS-IndexList-r16 NR-SelectedDL-PRS-IndexList-r16 OPTIONAL, -- Need ON + nr-PositionCalculationAssistance-r16 + NR-PositionCalculationAssistance-r16 + OPTIONAL, -- Cond UEB + nr-DL-AoD-Error-r16 NR-DL-AoD-Error-r16 OPTIONAL, -- Need ON + ..., + [[ + nr-DL-PRS-BeamInfo-r17 NR-DL-PRS-BeamInfo-r16 OPTIONAL, -- Cond UEA + nr-On-Demand-DL-PRS-Configurations-r17 + NR-On-Demand-DL-PRS-Configurations-r17 + OPTIONAL, -- Need ON + nr-On-Demand-DL-PRS-Configurations-Selected-IndexList-r17 + NR-On-Demand-DL-PRS-Configurations-Selected-IndexList-r17 + OPTIONAL, -- Need ON + assistanceDataValidityArea-r17 AreaID-CellList-r17 OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|---------------------------------------------------------------------------------------------------| +| UEB | The field is optionally present, need ON, for UE based NR DL-AoD; otherwise it is not present. | +| UEA | The field is optionally present, need ON, for UE-assisted NR DL-AoD; otherwise it is not present. | + +| NR-DL-AoD-ProvideAssistanceData field descriptions | +|----------------------------------------------------| +|----------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-DL-PRS-AssistanceData
This field specifies the assistance data reference and neighbour TRPs and provides the DL-PRS configuration for the TRPs.
Note, if this field is absent but the nr-SelectedDL-PRS-IndexList field is present, the nr-DL-PRS-AssistanceData may be provided in IE NR-Multi-RTT-ProvideAssistanceData or NR-DL-TDOA-ProvideAssistanceData . | +| nr-SelectedDL-PRS-IndexList
This field specifies the DL-PRS Resources which are applicable for this NR-DL-AoD-ProvideAssistanceData message. | +| nr-PositionCalculationAssistance
This field provides position calculation assistance data for UE-based mode. | +| nr-DL-AoD-Error
This field provides DL-AoD error reasons. | +| nr-DL-PRS-BeamInfo
This field provides spatial direction information of the DL-PRS Resources included in nr-DL-PRS-AssistanceData or indicated by nr-SelectedDL-PRS-IndexList . | +| nr-On-Demand-DL-PRS-Configurations
This field provides a set of available DL-PRS configurations which can be requested by the target device on-demand.
NOTE 1: Void.
NOTE 2: If this field is absent but the nr-On-Demand-DL-PRS-Configurations-Selected-IndexList is present, the nr-On-Demand-DL-PRS-Configurations may be provided in IE NR-Multi-RTT-ProvideAssistanceData or NR-DL-TDOA-ProvideAssistanceData . | +| nr-On-Demand-DL-PRS-Configurations-Selected-IndexList
This field specifies the selected available on-demand DL-PRS configurations which are applicable for this NR-DL-AoD-ProvideAssistanceData message. | +| assistanceDataValidityArea
This field specifies the network area for which this NR-DL-AoD-ProvideAssistanceData is valid. | + +## 6.5.11.2 NR DL-AoD Assistance Data Request + +### – NR-DL-AoD-RequestAssistanceData + +The IE *NR-DL-AoD-RequestAssistanceData* is used by the target device to request assistance data from a location server. + +``` +-- ASN1START +NR-DL-AoD-RequestAssistanceData-r16 ::= SEQUENCE { + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, + nr-AdType-r16 BIT STRING { dl-prs (0), + posCalc (1) } (SIZE (1..8)), + ..., + [[ + nr-PosCalcAssistanceRequest-r17 BIT STRING { trpLoc (0), + beamInfo (1), + rtdInfo (2), + beamAntInfo (3), + losNlosInfo (4), + integrityParameters-r18 (5) + } (SIZE (1..8)) OPTIONAL, + nr-DL-PRS-ExpectedAoD-or-AoA-Request-r17 ENUMERATED { eAoD, eAoA } OPTIONAL, + nr-DL-PRS-BeamInfoRequest-r17 ENUMERATED { requested } OPTIONAL, + nr-on-demand-DL-PRS-Request-r17 NR-On-Demand-DL-PRS-Request-r17 OPTIONAL, + pre-configured-AssistanceDataRequest-r17 ENUMERATED { true } OPTIONAL + ]] +} + +-- ASN1STOP +``` + +| NR-DL-AoD-RequestAssistanceData field descriptions | | +|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-PhysCellID | This field specifies the NR physical cell identity of the current primary cell of the target device. | +| nr-AdType | This field indicates the requested assistance data. dl-prs means requested assistance data is nr-DL-PRS-AssistanceData , posCalc means requested assistance data is nr-PositionCalculationAssistance for UE based positioning. | + +**nr-PosCalcAssistanceRequest** + +This field indicates the Position Calculation Assistance Data requested. This is represented by a bit string, with a one-value at the bit position means the particular assistance data is requested; a zero-value means not requested. + +- bit 0 indicates whether the field *nr-TRP-LocationInfo* in IE *NR-PositionCalculationAssistance* is requested or not; +- bit 1 indicates whether the field *nr-DL-PRS-BeamInfo* in IE *NR-PositionCalculationAssistance* is requested or not; +- bit 2 indicates whether the field *nr-RTD-Info* in IE *NR-PositionCalculationAssistance* is requested or not; +- bit 3 indicates whether the field *nr-TRP-BeamAntennaInfo* in IE *NR-PositionCalculationAssistance* is requested or not; +- bit 4 indicates whether the field *nr-DL-PRS-Expected-LOS-NLOS-Assistance* in IE *NR-PositionCalculationAssistance* is requested or not. +- bit 5 indicates the integrity parameters, the service parameters for integrity, the TRP/ARP location error and beam-related error is requested. + +This field may only be present if the 'posCalc' bit in *nr-AdType* is set to value '1'. + +**nr-DL-PRS-ExpectedAoD-or-AoA-Request** + +This field, if present, indicates that the IE *NR-DL-PRS-ExpectedAoD-or-AoA* in *NR-DL-PRS-AssistanceData* is requested. Enumerated value 'eAoD' indicates that expected AoD information is requested; value 'eAoA' indicates that expected AoA information is requested. + +This field may only be present if the 'dl-prs' bit in *nr-AdType* is set to value '1'. + +**nr-DL-PRS-BeamInfoRequest** + +This field, if present, indicates that the IE *NR-DL-PRS-BeamInfo* is requested. + +**nr-on-demand-DL-PRS-Request** + +This field indicates the on-demand DL-PRS requested for DL-AoD. This field may be included when the *dl-prs* bit in *nr-AdType* is set to value '1'. + +**pre-configured-AssistanceDataRequest** + +This field, if present, indicates that the target device requests pre-configured assistance data with area validity. + +## 6.5.11.3 NR DL-AoD Location Information + +### – NR-DL-AoD-ProvideLocationInformation + +The IE *NR-DL-AoD-ProvideLocationInformation* is used by the target device to provide NR DL-AoD location measurements to the location server. It may also be used to provide NR DL-AoD positioning specific error reason. + +``` +-- ASN1START +NR-DL-AoD-ProvideLocationInformation-r16 ::= SEQUENCE { + nr-DL-AoD-SignalMeasurementInformation-r16 + NR-DL-AoD-SignalMeasurementInformation-r16 + OPTIONAL, + nr-dl-AoD-LocationInformation-r16 NR-DL-AoD-LocationInformation-r16 + OPTIONAL, + nr-DL-AoD-Error-r16 NR-DL-AoD-Error-r16 + OPTIONAL, + ... + [[ + nr-DL-AoD-SignalMeasurementInstances-r17 SEQUENCE (SIZE (1..maxMeasInstances-r17)) OF + NR-DL-AoD-SignalMeasurementInformation-r16 OPTIONAL, -- Cond batchUEA + nr-DL-AoD-LocationInformationInstances-r17 SEQUENCE (SIZE (1..maxMeasInstances-r17)) OF + NR-DL-AoD-LocationInformation-r16 OPTIONAL -- Cond batchUEB + ]] +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------| +| batchUEA | The field is optionally present if the field nr-DL-AoD-SignalMeasurementInformation is absent; otherwise it is not present. | +| batchUEB | The field is optionally present if the field nr-dl-AoD-LocationInformation is absent; otherwise it is not present. | + +## 6.5.11.4 NR DL-AoD Location Information Elements + +### – NR-DL-AoD-SignalMeasurementInformation + +The IE *NR-DL-AoD-SignalMeasurementInformation* is used by the target device to provide NR DL-AoD measurements to the location server. + +``` +-- ASN1START + +NR-DL-AoD-SignalMeasurementInformation-r16 ::= SEQUENCE { + nr-DL-AoD-MeasList-r16 NR-DL-AoD-MeasList-r16, + ... +} + +NR-DL-AoD-MeasList-r16 ::= SEQUENCE (SIZE(1..nrMaxTRPs-r16)) OF NR-DL-AoD-MeasElement-r16 + +NR-DL-AoD-MeasElement-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, + nr-CellGlobalID-r16 NCGI-r15 OPTIONAL, + nr-ARFCN-r16 ARFCN-ValueNR-r15 OPTIONAL, + nr-DL-PRS-ResourceID-r16 NR-DL-PRS-ResourceID-r16 OPTIONAL, + nr-DL-PRS-ResourceSetID-r16 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, + nr-TimeStamp-r16 NR-TimeStamp-r16, + nr-DL-PRS-RSRP-Result-r16 INTEGER (0..126), + nr-DL-PRS-RxBeamIndex-r16 INTEGER (1..8) OPTIONAL, + nr-DL-AoD-AdditionalMeasurements-r16 + NR-DL-AoD-AdditionalMeasurements-r16 OPTIONAL, + ..., + [[ + nr-DL-PRS-FirstPathRSRP-Result-r17 + INTEGER (0..126) OPTIONAL, + nr-los-nlos-Indicator-r17 CHOICE { + perTRP-r17 LOS-NLOS-Indicator-r17, + perResource-r17 LOS-NLOS-Indicator-r17 + } OPTIONAL, + nr-DL-AoD-AdditionalMeasurementsExt-r17 + NR-DL-AoD-AdditionalMeasurementsExt-r17 OPTIONAL + ]] +} + +NR-DL-AoD-AdditionalMeasurements-r16 ::= SEQUENCE (SIZE(1..7)) OF + NR-DL-AoD-AdditionalMeasurementElement-r16 + +NR-DL-AoD-AdditionalMeasurementsExt-r17 ::= SEQUENCE (SIZE(1..maxAddMeasAoD-r17)) OF + NR-DL-AoD-AdditionalMeasurementElement-r17 + +NR-DL-AoD-AdditionalMeasurementElement-r16 ::= SEQUENCE { + nr-DL-PRS-ResourceID-r16 NR-DL-PRS-ResourceID-r16 OPTIONAL, + nr-DL-PRS-ResourceSetID-r16 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, + nr-TimeStamp-r16 NR-TimeStamp-r16, + nr-DL-PRS-RSRP-ResultDiff-r16 INTEGER (0..30), + nr-DL-PRS-RxBeamIndex-r16 INTEGER (1..8) OPTIONAL, + ... +} + +NR-DL-AoD-AdditionalMeasurementElement-r17 ::= SEQUENCE { + nr-DL-PRS-ResourceID-r17 NR-DL-PRS-ResourceID-r16 OPTIONAL, + nr-DL-PRS-ResourceSetID-r17 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, + nr-TimeStamp-r17 NR-TimeStamp-r16, + nr-DL-PRS-RSRP-ResultDiff-r17 INTEGER (0..30) OPTIONAL, -- Cond rsrp + nr-DL-PRS-RxBeamIndex-r17 INTEGER (1..8) OPTIONAL, + nr-DL-PRS-FirstPathRSRP-ResultDiff-r17 INTEGER (0..61) OPTIONAL, -- Cond rsrpp + nr-los-nlos-IndicatorPerResource-r17 LOS-NLOS-Indicator-r17 OPTIONAL, + ... +} + +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| rsrp | The field is mandatory present if the field nr-DL-PRS-FirstPathRSRP-ResultDiff-r17 is absent; otherwise it is optionally present, need ON. | +| rsrpp | The field is mandatory present if the field nr-DL-PRS-RSRP-ResultDiff-r17 is absent; otherwise it is optionally present, need ON. | + +| NR-DL-AoD-SignalMeasurementInformation field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PRS-ID
This field is used along with a DL-PRS Resource Set ID and a DL-PRS Resource ID to uniquely identify a DL-PRS Resource. This ID can be associated with multiple DL-PRS Resource Sets associated with a single TRP. Each TRP should only be associated with one such ID. | +| nr-PhysCellID
This field specifies the physical cell identity of the associated TRP, as defined in TS 38.331 [35]. | +| nr-CellGlobalID
This field specifies the NCGI, the globally unique identity of a cell in NR, of the associated TRP, as defined in TS 38.331 [35]. | +| nr-ARFCN
This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID . | +| nr-TimeStamp
This field specifies the time instance at which the measurement is performed. | +| nr-DL-PRS-RSRP-Result
This field specifies the NR DL-PRS reference signal received power (DL-PRS RSRP) measurement, as defined in TS 38.215 [36]. The mapping of the measured quantity is defined as in TS 38.133 [46]. | +| nr-DL-PRS-RxBeamIndex
This field provides an index of the target device receive beam used for DL-PRS measurements associated with a single TRP in nr-DL-AoD-MeasList-r16 when additional DL-PRS measurements are also included in either nr-DL-AoD-AdditionalMeasurements-r16 or nr-DL-AoD-AdditionalMeasurementsExt-r17 . If the value of the receive beam index for two or more DL-PRS measurements is the same, it indicates that the target device receive beam for the two or more DL-PRS measurements associated with a TRP were made with the same RX beam. The field is mandatory present if at least two DL-PRS RSRP measurements and/or DL-PRS RSRPP measurements from the same DL-PRS Resource Set associated with a TRP have been made with the same RX beam by the target device; otherwise it is not present. | +| nr-DL-AoD-AdditionalMeasurements
This field specifies a list of additional DL-PRS RSRP measurements of different DL-PRS resources for the same TRP. If this field is present, the field nr-DL-AoD-AdditionalMeasurementsExt should not be present. | +| nr-DL-PRS-FirstPathRSRP-Result
This field specifies the NR DL-PRS reference signal received path power (DL-PRS RSRPP) of the first detected path in time, as defined in TS 38.215 [36]. The mapping of the measured quantity is defined as in TS 38.133 [46]. | +| nr-los-nlos-Indicator
This field specifies the target device's best estimate of the LOS or NLOS of the RSRP or RSRPP of first path measurement for the TRP or resource.
NOTE: If the requested type or granularity in nr-los-nlos-IndicatorRequest is not possible, the target device may provide a different type and granularity for the estimated LOS-NLOS-Indicator . | +| nr-DL-AoD-AdditionalMeasurementsExt
This field specifies a list of additional DL-PRS RSRP and/or DL-PRS RSRPP measurements of different DL-PRS resources for the same TRP. If this field is present, the field nr-DL-AoD-AdditionalMeasurements should not be present. | +| nr-DL-PRS-RSRP-ResultDiff
This field provides the additional DL-PRS RSRP measurement result relative to nr-DL-PRS-RSRP-Result . The DL-PRS RSRP value of this measurement is obtained by adding the value of this field to the value of the nr-DL-PRS-RSRP-Result field. The mapping of the field is defined in TS 38.133 [46]. | +| nr-DL-PRS-FirstPathRSRP-ResultDiff
This field specifies the additional NR DL-PRS reference signal received path power (DL-PRS RSRPP) of the first detected path in time relative to nr-DL-PRS-FirstPathRSRP-Result . The DL-PRS RSRPP of first path value of this measurement is obtained by adding the value of this field to the value of the nr-DL-PRS-FirstPathRSRP-Result field. The mapping of the field is defined in TS 38.133 [46]. | +| nr-los-nlos-IndicatorPerResource
This field specifies the target device's best estimate of the LOS or NLOS of the RSRP or RSRPP of first path measurement for the resource.
This field may only be present if the field nr-LOS-NLOS-Indicator choice indicates perResource . | + +## — *NR-DL-AoD-LocationInformation* + +The IE *NR-DL-AoD-LocationInformation* is included by the target device when location information derived using NR DL-AoD is provided to the location server. + +``` +-- ASN1START +NR-DL-AoD-LocationInformation-r16 ::= SEQUENCE { + measurementReferenceTime-r16 CHOICE { + sfn-time-r16 NR-TimeStamp-r16, +``` + +``` + + utc-time-r16 UTCTime, + ... + } + OPTIONAL, + ... + [[ + locationCoordinates-r17 LocationCoordinates OPTIONAL, -- Cond batch1 + locationSource-r17 LocationSource-r13 OPTIONAL -- Cond batch2 + ]] + } + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| batch1 | The field is mandatory present if the field nr-DL-AoD-LocationInformationInstances is present in IE NR-DL-AoD-ProvideLocationInformation ; otherwise it is not present. | +| batch2 | The field is optionally present, need ON, if the field nr-DL-AoD-LocationInformationInstances is present in IE NR-DL-AoD-ProvideLocationInformation ; otherwise it is not present. | + +| NR-DL-AoD-LocationInformation field descriptions | | +|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| measurementReferenceTime | This field specifies the time for which the location estimate is valid. | +| locationCoordinates | This field provides a location estimate using one of the geographic shapes defined in TS 23.032 [15]. NOTE 1. | +| locationSource | This field provides the source positioning technology for the location estimate. NOTE 1. | + +NOTE 1: In the case of *locationCoordinates* for multiple NR positioning methods are provided, the *locationCoordinates* and *locationSource* shall be present in only one of *NR-DL-TDOA-ProvideLocationInformation* or *NR-DL-AoD-ProvideLocationInformation*. + +## 6.5.11.5 NR DL-AoD Location Information Request + +### – NR-DL-AoD-RequestLocationInformation + +The IE *NR-DL-AoD-RequestLocationInformation* is used by the location server to request NR DL-AoD location measurements from a target device. + +``` + +-- ASN1START + +NR-DL-AoD-RequestLocationInformation-r16 ::= SEQUENCE { + nr-AssistanceAvailability-r16 BOOLEAN, + nr-DL-AoD-ReportConfig-r16 NR-DL-AoD-ReportConfig-r16, + ... + [[ + multiMeasInSameReport-r17 ENUMERATED { requested } OPTIONAL -- Need ON + ]], + [[ + nr-DL-PRS-RxHoppingRequest-r18 ENUMERATED { requested } OPTIONAL, -- Need ON + nr-DL-PRS-RxHoppingTotalBandwidth-r18 CHOICE { + fr1 ENUMERATED { mhz40, mhz50, mhz80, mhz100}, + fr2 ENUMERATED { mhz100, mhz200, mhz400} + } + ]], + OPTIONAL -- Need ON +} + +NR-DL-AoD-ReportConfig-r16 ::= SEQUENCE { + maxDL-PRS-RSRP-MeasurementsPerTRP-r16 INTEGER (1..8) OPTIONAL, -- Need ON + ... + [[ + maxDL-PRS-RSRP-MeasurementsPerTRP-r17 INTEGER (9..24) OPTIONAL, -- Need ON + maxDL-PRS-RSRP-MeasurementsPerTRP-r17 INTEGER (1..24) OPTIONAL, -- Need ON + nr-los-nlos-IndicatorRequest-r17 SEQUENCE { + type-r17 LOS-NLOS-IndicatorType1-r17, + granularity-r17 LOS-NLOS-IndicatorGranularity1-r17, + ... + } + ]], + OPTIONAL, -- Need ON + reducedDL-PRS-ProcessingSamples-r17 ENUMERATED { requested, ... } +} + +``` + +``` + +lowerRxBeamSweepingFactor-FR2-r17 ENUMERATED { requested } OPTIONAL, -- Need ON +[[, +[[ +nr-DL-PRS-MeasurementTimeWindowsConfig-r18 + NR-DL-PRS-MeasurementTimeWindowsConfig-r18 OPTIONAL -- Need ON +]] +} + +-- ASN1STOP + +``` + +#### NR-DL-AoD-RequestLocationInformation field descriptions + +##### **nr-AssistanceAvailability** + +This field indicates whether the target device may request additional PRS assistance data from the server. TRUE means allowed and FALSE means not allowed. + +##### **multiMeasInSameReport** + +This field, if present, indicates that the target device is requested to provide multiple measurement instances in a single measurement report; i.e., include the *nr-DL-AoD-SignalMeasurementInstances* (in the case of UE-assisted mode is requested) or *nr-DL-AoD-LocationInformationInstances* (in the case of UE-based mode is requested) in IE *NR-DL-AoD-ProvideLocationInformation*. + +##### **nr-DL-PRS-RxHoppingRequest** + +This field, if present, indicates that the target device is requested to perform DL PRS Rx hopping measurements and reporting. + +##### **nr-DL-PRS-RxHoppingTotalBandwidth** + +This field, if present, indicates the total bandwidth of all hops in MHz. + +##### **maxDL-PRS-RSRP-MeasurementsPerTRP** + +This field specifies the maximum number of DL-PRS RSRP measurements on different DL-PRS Resources from the same TRP. If this field with -r17 suffix is present, the field with -r16 suffix should not be present. + +##### **maxDL-PRS-RSRPP-MeasurementsPerTRP** + +This field specifies the maximum number of DL-PRS RSRPP measurements on different DL-PRS Resources from the same TRP. + +##### **nr-los-nlos-IndicatorRequest** + +This field, if present, indicates that the target device is requested to provide the indicated type and granularity of the estimated *LOS-NLOS-Indicator* in the *NR-DL-AoD-SignalMeasurementInformation*. + +##### **reducedDL-PRS-ProcessingSamples** + +This field, if present and set to 'requested', indicates that the target device is requested to perform the requested measurements with reduced number of samples (M=1 or M=2) as specified in TS 38.133 [46]. + +##### **lowerRxBeamSweepingFactor-FR2** + +This field, if present, indicates that the target device is requested to use a lower Rx beam sweeping factor than 8 for FR2 according to UE's capability. + +##### **nr-DL-PRS-MeasurementTimeWindowsConfig** + +This field indicates DL-PRS resource set(s) occurring within time window(s) for performing measurements where the time window is indicated by a start time, periodicity, offset and duration. + +## 6.5.11.6 NR DL-AoD Capability Information + +### – NR-DL-AoD-ProvideCapabilities + +The IE *NR-DL-AoD-ProvideCapabilities* is used by the target device to indicate its capability to support NR DL-AoD and to provide its NR DL-AoD positioning capabilities to the location server. + +``` + +-- ASN1START + +NR-DL-AoD-ProvideCapabilities-r16 ::= SEQUENCE { + nr-DL-AoD-Mode-r16 PositioningModes, + nr-DL-AoD-PRS-Capability-r16 NR-DL-PRS-ResourcesCapability-r16, + nr-DL-AoD-MeasurementCapability-r16 NR-DL-AoD-MeasurementCapability-r16, + nr-DL-PRS-QCL-ProcessingCapability-r16 NR-DL-PRS-QCL-ProcessingCapability-r16, + nr-DL-PRS-ProcessingCapability-r16 NR-DL-PRS-ProcessingCapability-r16, + periodicalReporting-r16 PositioningModes OPTIONAL, + ..., + [[ + ten-ms-unit-ResponseTime-r17 PositioningModes OPTIONAL, + nr-PosCalcAssistanceSupport-r17 BIT STRING { + trpLocSup (0), + beamInfoSup (1), + rtdInfoSup (2), + beamAntInfoSup (3), + integritySup-r18 (4) + } +]] +} + +``` + +``` + + } (SIZE (1..8)) OPTIONAL, +nr-los-nlos-AssistanceDataSupport-r17 SEQUENCE { + type-r17 LOS-NLOS-IndicatorType2-r17, + granularity-r17 LOS-NLOS-IndicatorGranularity2-r17, + ... +} OPTIONAL, +nr-DL-PRS-ExpectedAoD-or-AoA-Sup-r17 BIT STRING { + eAoD (0), + eAoA (1) +} (SIZE (1..8)) OPTIONAL, +dl-PRS-ResourcePrioritySubset-Sup-r17 ENUMERATED { sameSet, differentSet, sameOrDifferentSet } OPTIONAL, +nr-DL-PRS-BeamInfoSup-r17 ENUMERATED { supported } OPTIONAL, +nr-DL-AoD-On-Demand-DL-PRS-Support-r17 NR-On-Demand-DL-PRS-Support-r17 OPTIONAL, +nr-los-nlos-IndicatorSupport-r17 SEQUENCE { + type-r17 LOS-NLOS-IndicatorType2-r17, + granularity-r17 LOS-NLOS-IndicatorGranularity2-r17, + ... +} OPTIONAL, +scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupportPerMode-r17 OPTIONAL, +nr-dl-prs-AssistanceDataValidity-r17 SEQUENCE { + area-validity-r17 INTEGER (1..maxNrOfAreas-r17) OPTIONAL, + ... +} OPTIONAL, +multiMeasInSameMeasReport-r17 ENUMERATED { supported } OPTIONAL, +mg-ActivationRequest-r17 ENUMERATED { supported } OPTIONAL, +[[ +posMeasGapSupport-r17 ENUMERATED { supported } OPTIONAL +]], +[[ +multiLocationEstimateInSameMeasReport-r17 ENUMERATED { supported } OPTIONAL +]], +[[ +locationCoordinateTypes-r18 LocationCoordinateTypes OPTIONAL, +nr-DL-AoD-PosIntegritySupport-r18 ENUMERATED { supported } OPTIONAL +]] +} +-- ASN1STOP + +``` + +### NR-DL-AoD-ProvideCapabilities field descriptions + +#### nr-DL-AoD-Mode + +This field specifies the NR DL-AoD mode(s) supported by the target device. + +#### periodicalReporting + +This field, if present, specifies the positioning modes for which the target device supports *periodicalReporting*. This is represented by a bit string, with a one-value at the bit position means *periodicalReporting* for the positioning mode is supported; a zero-value means not supported. If this field is absent, the target device does not support *periodicalReporting* in *CommonEsRequestLocationInformation*. + +#### ten-ms-unit-ResponseTime + +This field, if present, specifies the positioning modes for which the target device supports the enumerated value '*ten-milli-seconds*' in the IE *ResponseTime* in IE *CommonEsRequestLocationInformation*. This is represented by a bit string, with a one-value at the bit position means '*ten-milli-seconds*' response time unit for the positioning mode is supported; a zero-value means not supported. If this field is absent, the target device does not support '*ten-milli-seconds*' response time unit in *CommonEsRequestLocationInformation*. + +#### nr-PosCalcAssistanceSupport + +This field indicates the Position Calculation Assistance Data supported by the target device for UE-based DL-AoD. This is represented by a bit string, with a one-value at the bit position means the particular assistance data is supported; a zero-value means not supported. + +- bit 0 indicates whether the field *nr-TRP-LocationInfo* in IE *NR-PositionCalculationAssistance* is supported or not; +- bit 1 indicates whether the field *nr-DL-PRS-BeamInfo* in IE *NR-PositionCalculationAssistance* is supported or not; +- bit 2 indicates whether the field *nr-RTD-Info* in IE *NR-PositionCalculationAssistance* is supported or not. The UE can indicate this bit only if the UE supports *prs-ProcessingCapabilityBandList* and any of *maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer*, *maxNrOfTRP-AcrossFreqs*, *maxNrOfPosLayer*, *maxNrOfDL-PRS-ResourcesPerResourceSet* and *maxNrOfDL-PRS-ResourcesPerPositioningFrequencyLayer*. Otherwise, the UE does not include this field; +- bit 3 indicates whether the field *nr-TRP-BeamAntennaInfo* in IE *NR-PositionCalculationAssistance* is supported or not. +- bit 4 indicates whether the target service supports the range of integrity risk (IR) for which the integrity assistance data are valid. + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

nr-los-nlos-AssistanceDataSupport

This field, if present, indicates that the target device supports the NR-DL-PRS-ExpectedLOS-NLOS-Assistance in IE NR-PositionCalculationAssistance:

  • - type indicates whether the target device supports 'hard' value or 'hard' and 'soft' value in LOS-NLOS-Indicator in IE NR-DL-PRS-ExpectedLOS-NLOS-Assistance.
  • - granularity indicates whether the target device supports nr-los-nlos-indicator in IE NR-DL-PRS-ExpectedLOS-NLOS-Assistance 'per-trp', 'per-resource', or both.

The UE can include this field only if the UE supports one of maxDL-PRS-RSRP-MeasurementFR1, maxDL-PRS-RSRP-MeasurementFR2, dl-RSTD-MeasurementPerPairOfTRP-FR1, dl-RSTD-MeasurementPerPairOfTRP-FR2, maxNrOfRx-TX-MeasFR1, maxNrOfRx-TX-MeasFR2, supportOfRSRP-MeasFR1 and supportOfRSRP-MeasFR2. Otherwise, the UE does not include this field.

| +|

nr-DL-PRS-ExpectedAoD-or-AoA-Sup

This field, if present, indicates that the target device supports the NR-DL-PRS-ExpectedAoD-or-AoA in NR-DL-PRS-AssistanceData.

| +|

dl-PRS-ResourcePrioritySubset-Sup

This field, if present, indicates that the target device supports the DL-PRS-ResourcePrioritySubset in IE NR-DL-PRS-Info. Enumerated value indicates the supported resource set relationship for the target DL-PRS Resource and the associated subset.

| +|

nr-DL-PRS-BeamInfoSup

This field, if present, indicates that the target device supports the NR-DL-PRS-BeamInfo in IE NR-DL-AoD-ProvideAssistanceData.

| +|

nr-DL-AoD-On-Demand-DL-PRS-Support

This field, if present, indicates that the target device supports on-demand DL-PRS requests.

| +|

nr-los-nlos-IndicatorSupport

This field, if present, indicates that the target device supports nr-los-nlos-Indicator reporting in IE NR-DL-AoD-SignalMeasurementInformation.

  • - type indicates whether the target device supports 'hard' value or 'hard' and 'soft' value in IE LOS-NLOS-Indicator.
  • - granularity indicates whether the target device supports LOS-NLOS-Indicator reporting per TRP, per DL-PRS Resource, or both.
| +|

scheduledLocationRequestSupported

This field, if present, specifies the positioning modes for which the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonIEsRequestLocationInformation – and the time base(s) supported for the scheduled location time for each positioning mode. If this field is absent, the target device does not support scheduled location requests.

| +|

nr-dl-prs-AssistanceDataValidity

This field, if present, indicates that the target device supports validity conditions for pre-configured assistance data and comprises the following subfields:

  • - area-validity indicates that the target device supports pre-configured assistance data with area validity. The integer number indicates the maximum number of areas the target device supports.
| +|

multiMeasInSameMeasReport

This field, if present, indicates that the target device supports multiple measurement instances in a single measurement report.

| +|

mg-ActivationRequest

This field, if present, indicates that the target device supports UL MAC CE for positioning measurement gap activation/deactivation request for DL-PRS measurements. The UE can include this field only if the UE supports mg-ActivationRequestPRS-Meas and mg-ActivationCommPRS-Meas defined in TS 38.331 [35].

| +|

posMeasGapSupport

This field, if present, indicates that the target device supports pre-configured positioning measurement gap for DL-PRS measurements. The UE can include this field only if the UE supports mg-ActivationCommPRS-Meas defined in TS 38.331 [35].

| +|

multiLocationEstimateInSameMeasReport

This field, if present, indicates that the target device supports multiple location estimate instances in a single measurement report.

| +|

locationCoordinateTypes

This field indicates the geographical location coordinate types that a target device supports for UE-based DL-AoD. TRUE indicates that a location coordinate type is supported and FALSE that it is not.

| +|

nr-DL-AoD-PosIntegritySupport

This field, if present, indicates that the target device supports the RAT-dependent positioning integrity for DL-AoD.

| + +## 6.5.11.6a NR DL-AoD Capability Information Elements + +### – *NR-DL-AoD-MeasurementCapability* + +The IE *NR-DL-AoD-MeasurementCapability* defines the DL-AoD measurement capability. The UE can include this IE only if the UE supports *NR-DL-PRS-ResourcesCapability* for DL-AoD. Otherwise, the UE does not include this IE; + +``` +-- ASN1START + +NR-DL-AoD-MeasurementCapability-r16 ::= SEQUENCE { + maxDL-PRS-RSRP-MeasurementFR1-r16 INTEGER (1..8), + maxDL-PRS-RSRP-MeasurementFR2-r16 INTEGER (1..8), + dl-AoD-MeasCapabilityBandList-r16 SEQUENCE (SIZE (1..nrMaxBands-r16)) OF + DL-AoD-MeasCapabilityPerBand-r16, + ... + [ + maxDL-PRS-RSRP-MeasurementFR1-v1730 ENUMERATED { n16, n24 } OPTIONAL, + maxDL-PRS-RSRP-MeasurementFR2-v1730 ENUMERATED { n16, n24 } OPTIONAL + ] +} + +DL-AoD-MeasCapabilityPerBand-r16 ::= SEQUENCE { + freqBandIndicatorNR-r16 FreqBandIndicatorNR-r16, + simul-NR-DL-AoD-DL-TDOA-r16 ENUMERATED { supported } OPTIONAL, + simul-NR-DL-AoD-Multi-RTT-r16 ENUMERATED { supported } OPTIONAL, + ... + [ + maxDL-PRS-FirstPathRSRP-MeasPerTRP-r17 ENUMERATED { n1, n2, n4, n8, n16, n24 } OPTIONAL, + dl-PRS-MeasRRC-Inactive-r17 ENUMERATED { supported } OPTIONAL + ] +} + +-- ASN1STOP +``` + +#### *NR-DL-AoD-MeasurementCapability* field descriptions + +##### ***maxDL-PRS-RSRP-MeasurementFR1*** + +Indicates the maximum number of DL-PRS RSRP measurements on different PRS resources from the same TRP supported by the UE on FR1. If this field with suffix -v1730 is present, the target device should set the field with suffix -r16 to value '8'. + +##### ***maxDL-PRS-RSRP-MeasurementFR2*** + +Indicates the maximum number of DL-PRS RSRP measurements on different PRS resources from the same TRP supported by the UE on FR2. If this field with suffix -v1730 is present, the target device should set the field with suffix -r16 to value '8'. + +##### ***simul-NR-DL-AoD-DL-TDOA*** + +Indicates whether the UE supports simultaneous processing for DL-AoD and DL-TDOA measurements. The UE can include this field only if the UE supports DL-TDOA and DL-AoD. Otherwise, the UE does not include this field. + +##### ***simul-NR-DL-AoD-Multi-RTT*** + +Indicates whether the UE supports simultaneous processing for DL-AoD and UE Multi-RTT measurements. The UE can include this field only if the UE supports Multi-RTT and DL-AoD. Otherwise, the UE does not include this field. + +##### ***maxDL-PRS-FirstPathRSRP-MeasPerTRP*** + +This field, if present, indicates that the target device supports measuring and reporting the PRS RSRPP of the first path. The enumerated value indicates the maximum number of RSRPP of first path per TRP supported. The UE can include this field only if the UE supports one of *maxDL-PRS-RSRP-MeasurementFR1* and *maxDL-PRS-RSRP-MeasurementFR2*. Otherwise, the UE does not include this field. + +NOTE 1: The maximum number of first path PRS RSRP per TRP should be less than or equal to the maximum number of PRS RSRP defined in *maxDL-PRS-RSRP-MeasurementFR1* and *maxDL-PRS-RSRP-MeasurementFR2*. + +##### ***dl-PRS-MeasRRC-Inactive*** + +This field, if present, indicates that the target device supports DL-PRS measurement in RRC\_INACTIVE state. The UE can include this field only if the UE supports *maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer*, *maxNrOfTRP-AcrossFreqs*, *maxNrOfPosLayer* and *dl-PRS-BufferType-RRC-Inactive*. Otherwise, the UE does not include this field. + +NOTE 1: This capability is applicable to both, UE-assisted and UE-based DL-AoD. + +NOTE 2: The capabilities *NR-DL-PRS-ResourcesCapability*, *simul-NR-DL-AoD-DL-TDOA* are the same in RRC\_INACTIVE state. + +## 6.5.11.7 NR DL-AoD Capability Information Request + +### – *NR-DL-AoD-RequestCapabilities* + +The IE *NR-DL-AoD-RequestCapabilities* is used by the location server to request the capability of the target device to support NR DL-AoD and to request NR DL-AoD positioning capabilities from a target device. + +``` +-- ASN1START + +NR-DL-AoD-RequestCapabilities-r16 ::= SEQUENCE { + ... +} + +-- ASN1STOP +``` + +## 6.5.11.8 NR DL-AoD Error Elements + +### – *NR-DL-AoD-Error* + +The IE *NR-DL-AoD-Error* is used by the location server or target device to provide NR DL-AoD error reasons to the target device or location server, respectively. + +``` +-- ASN1START + +NR-DL-AoD-Error-r16 ::= CHOICE { + locationServerErrorCauses-r16 NR-DL-AoD-LocationServerErrorCauses-r16, + targetDeviceErrorCauses-r16 NR-DL-AoD-TargetDeviceErrorCauses-r16, + ... +} + +-- ASN1STOP +``` + +### – *NR-DL-AoD-LocationServerErrorCauses* + +The IE *NR-DL-AoD-LocationServerErrorCauses* is used by the location server to provide NR DL-AoD error reasons to the target device. + +``` +-- ASN1START + +NR-DL-AoD-LocationServerErrorCauses-r16 ::= SEQUENCE { + cause-r16 ENUMERATED { undefined, + assistanceDataNotSupportedByServer, + assistanceDataSupportedButCurrentlyNotAvailableByServer, + notProvidedAssistanceDataNotSupportedByServer, + ..., + on-demand-dl-prs-NotSupportedByServer-v1700, + on-demand-dl-prs-SupportedButCurrentlyNotAvailableByServer-v1700 + }, + ... +} + +-- ASN1STOP +``` + +### – *NR-DL-AoD-TargetDeviceErrorCauses* + +The IE *NR-DL-AoD-TargetDeviceErrorCauses* is used by the target device to provide NR DL-AoD error reasons to the location server. + +``` +-- ASN1START + +NR-DL-AoD-TargetDeviceErrorCauses-r16 ::= SEQUENCE { + cause-r16 ENUMERATED { undefined, + assistance-data-missing, + unableToMeasureAnyTRP, + attemptedButUnableToMeasureSomeNeighbourTRPs, + thereWereNotEnoughSignalsReceivedForUeBasedDL-AoD, + ... + }, + ... +} + +-- ASN1STOP +``` + +``` + + locationCalculationAssistanceDataMissing, + ... + }, + ..., + [[ + remoteUE-Indication-r18 ENUMERATED {true} OPTIONAL -- Cond NR + ]] +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------| +| NR | This field is optionally present, need OR, for NR access. Otherwise it is not present. | + +| NR-DL-AoD-TargetDeviceErrorCauses field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------| +| remoteUE-Indication
This field indicates whether the target device in NR access is configured as a L2 U2N Remote UE. | + +## 6.5.12 NR Multi-RTT Positioning + +This clause defines the information elements for NR Multi-RTT positioning (TS 38.305 [40]). + +### 6.5.12.1 NR Multi-RTT Assistance Data + +#### – *NR-Multi-RTT-ProvideAssistanceData* + +The IE *NR-Multi-RTT-ProvideAssistanceData* is used by the location server to provide assistance data to enable UE-assisted NR Multi-RTT. It may also be used to provide NR Multi-RTT positioning specific error reason. + +``` + +-- ASN1START + +NR-Multi-RTT-ProvideAssistanceData-r16 ::= SEQUENCE { + nr-DL-PRS-AssistanceData-r16 NR-DL-PRS-AssistanceData-r16 OPTIONAL, -- Need ON + nr-SelectedDL-PRS-IndexList-r16 NR-SelectedDL-PRS-IndexList-r16 OPTIONAL, -- Need ON + nr-Multi-RTT-Error-r16 NR-Multi-RTT-Error-r16 OPTIONAL, -- Need ON + ..., + [[ + nr-On-Demand-DL-PRS-Configurations-r17 NR-On-Demand-DL-PRS-Configurations-r17 + OPTIONAL, -- Need ON + nr-On-Demand-DL-PRS-Configurations-Selected-IndexList-r17 + NR-On-Demand-DL-PRS-Configurations-Selected-IndexList-r17 + OPTIONAL, -- Need ON + assistanceDataValidityArea-r17 AreaID-CellList-r17 OPTIONAL -- Need ON + ]] +} + +-- ASN1STOP + +``` + +| NR-Multi-RTT-ProvideAssistanceData field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-DL-PRS-AssistanceData
This field specifies the assistance data reference and neighbour TRPs and provides the DL-PRS configuration for the TRPs.
Note, if this field is absent but the nr-SelectedDL-PRS-IndexList field is present, the nr-DL-PRS-AssistanceData may be provided in IE NR-DL-TDOA-ProvideAssistanceData or NR-DL-AoD-ProvideAssistanceData . | +| nr-SelectedDL-PRS-IndexList
This field specifies the DL-PRS Resources which are applicable for this NR-Multi-RTT-ProvideAssistanceData message. | +| nr-Multi-RTT-Error
This field provides Multi-RTT error reasons. | +| nr-On-Demand-DL-PRS-Configurations
This field provides a set of available DL-PRS configurations which can be requested by the target device on-demand.
NOTE 1: Void.
NOTE 2: If this field is absent but the nr-On-Demand-DL-PRS-Configurations-Selected-IndexList is present, the nr-On-Demand-DL-PRS-Configurations may be provided in IE NR-DL-AoD-ProvideAssistanceData or NR-DL-TDOA-ProvideAssistanceData . | + +**nr-On-Demand-DL-PRS-Configurations-Selected-IndexList** + +This field specifies the selected available on-demand DL-PRS configurations which are applicable for this *NR-Multi-RTT-ProvideAssistanceData* message. + +**assistanceDataValidityArea** + +This field specifies the network area for which this *NR-Multi-RTT-ProvideAssistanceData* is valid. + +## 6.5.12.2 NR Multi-RTT Assistance Data Request + +### – *NR-Multi-RTT-RequestAssistanceData* + +The IE *NR-Multi-RTT-RequestAssistanceData* is used by the target device to request assistance data from a location server. + +``` +-- ASN1START +NR-Multi-RTT-RequestAssistanceData-r16 ::= SEQUENCE { + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, + nr-AdType-r16 BIT STRING { dl-prs (0), + ul-srs (1) } (SIZE (1..8)), + ... + [ + nr-on-demand-DL-PRS-Request-r17 NR-On-Demand-DL-PRS-Request-r17 OPTIONAL, + nr-DL-PRS-ExpectedAoD-or-AoA-Request-r17 ENUMERATED { eAoD, eAoA } OPTIONAL, + pre-configured-AssistanceDataRequest-r17 ENUMERATED { true } OPTIONAL + ] +} +-- ASN1STOP +``` + +### *NR-Multi-RTT-RequestAssistanceData* field descriptions + +**nr-PhysCellID** + +This field specifies the NR physical cell identity of the current primary cell of the target device. + +**nr-AdType** + +This field indicates the requested assistance data and/or configuration. *dl-prs* means requested assistance data is *nr-DL-PRS-AssistanceData*, *ul-srs* means a request for UL-SRS configuration. + +NOTE: UL-SRS is configured via NRPPa and RRC signalling as specified in clause 8.10.4 of TS 38.305 [40]. + +**nr-on-demand-DL-PRS-Request** + +This field indicates the on-demand DL-PRS requested for Multi-RTT. This field may be included when the *dl-prs* bit in *nr-AdType* is set to value '1'. + +**nr-DL-PRS-ExpectedAoD-or-AoA-Request** + +This field, if present, indicates that the IE *NR-DL-PRS-ExpectedAoD-or-AoA* in *NR-DL-PRS-AssistanceData* is requested. Enumerated value 'eAoD' indicates that expected AoD information is requested; value 'eAoA' indicates that expected AoA information is requested. + +This field may only be present if the '*dl-prs*' bit in *nr-AdType* is set to value '1'. + +**pre-configured-AssistanceDataRequest** + +This field, if present, indicates that the target device requests pre-configured assistance data with area validity. + +## 6.5.12.3 NR Multi-RTT Location Information + +### – *NR-Multi-RTT-ProvideLocationInformation* + +The IE *NR-Multi-RTT-ProvideLocationInformation* is used by the target device to provide NR Multi-RTT location measurements to the location server. It may also be used to provide NR Multi-RTT positioning specific error reason. + +``` +-- ASN1START +NR-Multi-RTT-ProvideLocationInformation-r16 ::= SEQUENCE { + nr-Multi-RTT-SignalMeasurementInformation-r16 + NR-Multi-RTT-SignalMeasurementInformation-r16 + OPTIONAL, + nr-Multi-RTT-Error-r16 NR-Multi-RTT-Error-r16 OPTIONAL, + ... + [ + nr-Multi-RTT-SignalMeasurementInstances-r17 + SEQUENCE (SIZE (1..maxMeasInstances-r17)) OF +``` + +``` + + ] ] + } + + -- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| batchUEA | The field is optionally present if the field nr-Multi-RTT-SignalMeasurementInformation is absent; otherwise it is not present. | + +## 6.5.12.4 NR Multi-RTT Location Information Elements + +### – *NR-Multi-RTT-SignalMeasurementInformation* + +The IE *NR-Multi-RTT-SignalMeasurementInformation* is used by the target device to provide NR Multi-RTT measurements to the location server. + +``` + +-- ASN1START + +NR-Multi-RTT-SignalMeasurementInformation-r16 ::= SEQUENCE { + nr-Multi-RTT-MeasList-r16 NR-Multi-RTT-MeasList-r16, + nr-NTA-Offset-r16 ENUMERATED { nTA1, nTA2, nTA3, nTA4, ... } OPTIONAL, + ..., + [[ + nr-SRS-TxTEG-Set-r17 SEQUENCE (SIZE(1..maxTxTEG-Sets-r17)) OF + NR-SRS-TxTEG-Element-r17 OPTIONAL + -- Cond Case2-3 + ]], + [[ + nr-UE-RxTEG-TimingErrorMargin-r17 TEG-TimingErrorMargin-r17 OPTIONAL, -- Cond TEGCase3 + nr-UE-TxTEG-TimingErrorMargin-r17 TEG-TimingErrorMargin-r17 OPTIONAL, -- Cond TEGCase2-3 + nr-UE-RxTxTEG-TimingErrorMargin-r17 RxTxTEG-TimingErrorMargin-r17 OPTIONAL -- Cond TEGCase1-2 + ]] +} + +NR-Multi-RTT-MeasList-r16 ::= SEQUENCE (SIZE(1..nrMaxTRPs-r16)) OF NR-Multi-RTT-MeasElement-r16 + +NR-Multi-RTT-MeasElement-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + nr-PhysCellID-r16 NR-PhysCellID-r16 OPTIONAL, + nr-CellGlobalID-r16 NCGI-r15 OPTIONAL, + nr-ARFCN-r16 ARFCN-ValueNR-r15 OPTIONAL, + nr-DL-PRS-ResourceID-r16 NR-DL-PRS-ResourceID-r16 OPTIONAL, + nr-DL-PRS-ResourceSetID-r16 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, + nr-UE-RxTxTimeDiff-r16 CHOICE { + k0-r16 INTEGER (0..1970049), + k1-r16 INTEGER (0..985025), + k2-r16 INTEGER (0..492513), + k3-r16 INTEGER (0..246257), + k4-r16 INTEGER (0..123129), + k5-r16 INTEGER (0..61565), + ..., + kMinus1-r18 INTEGER (0..3940097), + kMinus2-r18 INTEGER (0..7880193) + }, + nr-AdditionalPathList-r16 NR-AdditionalPathList-r16 OPTIONAL, + nr-TimeStamp-r16 NR-TimeStamp-r16, + nr-TimingQuality-r16 NR-TimingQuality-r16, + nr-DL-PRS-RSRP-Result-r16 INTEGER (0..126) OPTIONAL, + nr-Multi-RTT-AdditionalMeasurements-r16 + NR-Multi-RTT-AdditionalMeasurements-r16 OPTIONAL, + ..., + [[ + nr-UE-RxTx-TEG-Info-r17 NR-UE-RxTx-TEG-Info-r17 OPTIONAL, + nr-DL-PRS-FirstPathRSRP-Result-r17 INTEGER (0..126) OPTIONAL, + nr-los-nlos-Indicator-r17 CHOICE { + perTRP-r17 LOS-NLOS-Indicator-r17, + perResource-r17 LOS-NLOS-Indicator-r17 + } OPTIONAL, + nr-AdditionalPathListExt-r17 NR-AdditionalPathListExt-r17 OPTIONAL, + nr-Multi-RTT-AdditionalMeasurementsExt-r17 + ]] +} + +``` + +``` + + ], + [[ + nr-UE-RxTxTimeDiffBasedOnAggregatedResources-r18 ENUMERATED {true} OPTIONAL, + nr-AggregatedDL-PRS-ResourceSetID-List-r18 SEQUENCE (SIZE (2.. 3)) OF + NR-AggregatedDL-PRS-ResourceSetID-Element-r18 OPTIONAL, + nr-RSCP-r18 INTEGER (0..3600) OPTIONAL, + nr-PhaseQuality-r18 NR-PhaseQuality-r18 OPTIONAL, + nr-RSCP-AddSampleMeasurements-r18 + SEQUENCE (SIZE (1..nrNumOfSamples-1-r18 )) OF NR-RSCP-AdditionalMeasurements-r18 + OPTIONAL, + nr-ReportDL-PRS-MeasBasedOnSingleOrMultiHopRx-r18 + ENUMERATED { singleHop, multipleHop } OPTIONAL, + nr-NTN-UE-RxTxTimeDiff-r18 NR-NTN-UE-RxTxTimeDiff-r18 OPTIONAL + ]] + } + + NR-Multi-RTT-AdditionalMeasurements-r16 ::= SEQUENCE (SIZE (1..3)) OF + NR-Multi-RTT-AdditionalMeasurementElement-r16 + + NR-Multi-RTT-AdditionalMeasurementsExt-r17 ::= SEQUENCE (SIZE (1..maxAddMeasRTT-r17)) OF + NR-Multi-RTT-AdditionalMeasurementElement-r16 + + NR-Multi-RTT-AdditionalMeasurementElement-r16 ::= SEQUENCE { + nr-DL-PRS-ResourceID-r16 NR-DL-PRS-ResourceID-r16 OPTIONAL, + nr-DL-PRS-ResourceSetID-r16 NR-DL-PRS-ResourceSetID-r16 OPTIONAL, + nr-DL-PRS-RSRP-ResultDiff-r16 INTEGER (0..61) OPTIONAL, + nr-UE-RxTxTimeDiffAdditional-r16 CHOICE { + k0-r16 INTEGER (0..8191), + k1-r16 INTEGER (0..4095), + k2-r16 INTEGER (0..2047), + k3-r16 INTEGER (0..1023), + k4-r16 INTEGER (0..511), + k5-r16 INTEGER (0..255), + ..., + kMinus1-r18 INTEGER (0..16382), + kMinus2-r18 INTEGER (0..32764) + }, + nr-TimingQuality-r16 NR-TimingQuality-r16, + nr-AdditionalPathList-r16 NR-AdditionalPathList-r16 OPTIONAL, + nr-Timestamp-r16 NR-Timestamp-r16, + ..., + [[ + nr-UE-RxTx-TEG-Info-r17 NR-UE-RxTx-TEG-Info-r17 OPTIONAL, + nr-DL-PRS-FirstPathRSRP-ResultDiff-r17 INTEGER (0..61) OPTIONAL, + nr-los-nlos-IndicatorPerResource-r17 LOS-NLOS-Indicator-r17 OPTIONAL, + nr-AdditionalPathListExt-r17 NR-AdditionalPathListExt-r17 OPTIONAL + ]], + [[ + nr-UE-RxTxTimeDiffBasedOnAggregatedResources-r18 ENUMERATED {true} OPTIONAL, + nr-AggregatedDL-PRS-ResourceSetID-List-r18 SEQUENCE (SIZE (2.. 3)) OF + NR-AggregatedDL-PRS-ResourceSetID-Element-r18 OPTIONAL, + nr-RSCP-r18 INTEGER (0..3600) OPTIONAL, + nr-PhaseQuality-r18 NR-PhaseQuality-r18 OPTIONAL, + nr-RSCP-AdditionalMeasurementsAddSample-r18 + SEQUENCE (SIZE (1..nrNumOfSamples-1-r18 )) OF NR-RSCP-AdditionalMeasurements-r18 + OPTIONAL, + nr-ReportDL-PRS-MeasBasedOnSingleOrMultiHopRx-r18 + ENUMERATED { singleHop, multipleHop } OPTIONAL, + nr-NTN-UE-RxTxTimeDiff-r18 NR-NTN-UE-RxTxTimeDiff-r18 OPTIONAL + ]] + } + + NR-SRS-TxTEG-Element-r17 ::= SEQUENCE { + nr-Timestamp-r17 NR-Timestamp-r16 OPTIONAL, -- Need OP + nr-UE-Tx-TEG-ID-r17 INTEGER (0..maxNumOfTxTEGs-1-r17), + carrierFreq-r17 SEQUENCE { + absoluteFrequencyPointA-r17 ARFCN-ValueNR-r15, + offsetToPointA-r17 INTEGER (0..2199) + } OPTIONAL, + srs-PosResourceList-r17 SEQUENCE (SIZE (1..maxNumOfSRS-PosResources-r17)) OF + INTEGER (0..maxNumOfSRS-PosResources-1-r17), + ... + } + + NR-UE-RxTx-TEG-Info-r17 ::= CHOICE { + case1-r17 SEQUENCE { + nr-UE-RxTx-TEG-ID-r17 INTEGER (0..maxNumOfRxTxTEGs-1-r17) + } + } + +``` + +``` + + }, + case2-r17 SEQUENCE { + nr-UE-RxTx-TEG-ID-r17 INTEGER (0..maxNumOfRxTxTEGs-1-r17), + nr-UE-Tx-TEG-Index-r17 INTEGER (1..maxTxTEG-Sets-r17) + }, + case3-r17 SEQUENCE { + nr-UE-Rx-TEG-ID-r17 INTEGER (0..maxNumOfRxTEGs-1-r17), + nr-UE-Tx-TEG-Index-r17 INTEGER (1..maxTxTEG-Sets-r17) + }, + ... + } + + NR-RSCP-AdditionalMeasurements-r18 ::= SEQUENCE { + nr-RSCP-ResultDiff-r18 INTEGER (0..3600) OPTIONAL, + nr-PhaseQuality-r18 NR-PhaseQuality-r18 OPTIONAL, + nr-TimeStamp-r18 NR-TimeStamp-r16 OPTIONAL, + ... + } + + NR-NTN-UE-RxTxTimeDiff-r18 ::= SEQUENCE { + nr-NTN-UE-RxTxTimeDiffSubframeOffset-r18 INTEGER (0..542), + nr-NTN-DL-TimingDrift-r18 INTEGER (-265..265) + } + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Case2-3 | The field is mandatory present if the IE NR-UE-RxTx-TEG-Info is provided for choice's case2 and case3 . Otherwise it is not present. | +| TEGCase3 | The field is optionally present, need OP, if the IE NR-UE-RxTx-TEG-Info is provided for choice case3 . Otherwise it is not present. | +| TEGCase2-3 | The field is optionally present, need OP, if the IE NR-UE-RxTx-TEG-Info is provided for choice's case2 and case3 . Otherwise it is not present. | +| TEGCase1-2 | The field is optionally present, need OP, if the IE NR-UE-RxTx-TEG-Info is provided for choice's case1 and case2 . Otherwise it is not present. | + +| NR-Multi-RTT-SignalMeasurementInformation field descriptions | | +|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-NTA-Offset | This field provides the $N_{TAoffset}$ used by the target device as specified in TS 38.133 [46], Table 7.1.2-2. Enumerated values nTA1, nTA2, nTA3, and nTA4 correspond to $N_{TAoffset}$ of 25600 Tc, 0 Tc, 39936 Tc, and 13792 Tc, respectively. | +| nr-SRS-TxTEG-Set | This field provides the SRS for Positioning Resources associated with a particular UE Tx TEG and comprises the following subfields:
  • - nr-TimeStamp specifies the start time for which the NR-SRS-TxTEG-Element is valid. If this field is absent, the nr-TimeStamp of this instance of the NR-SRS-TxTEG-Element of the nr-SRS-TxTEG-Set is the same as the nr-TimeStamp of the previous instance of the NR-SRS-TxTEG-Element. If this field is also absent in the first NR-SRS-TxTEG-Element of the nr-SRS-TxTEG-Set, all NR-SRS-TxTEG-Element's provided are valid for the measurement period of the NR-Multi-RTT-SignalMeasurementInformation.
  • - nr-UE-Tx-TEG-ID specifies the ID of this UE Tx TEG.
  • - carrierFreq specifies the frequency of the SRS for positioning resources.
  • - srs-PosResourceList specifies the SRS for Positioning Resources belonging to this UE Tx TEG.
For each UE Tx TEG, there may be up to 8 changes (different nr-TimeStamp ) of the TEG-SRS association information provided in nr-SRS-TxTEG-Set , i.e., the maximum value for maxTxTEG-Sets is 64. | +| nr-UE-RxTEG-TimingErrorMargin | This field specifies the UE Rx TEG timing error margin value for all the UE Rx TEGs within one NR-Multi-RTT-SignalMeasurementInformation . If the IE NR-UE-RxTx-TEG-Info is present with choice case3 and this field is absent, the receiver should consider the UE Rx TEG timing error margin value to be the maximum value available in IE TEG-TimingErrorMargin . | +| nr-UE-TxTEG-TimingErrorMargin | This field specifies the UE Tx TEG timing error margin value for all the UE Tx TEGs within one NR-Multi-RTT-SignalMeasurementInformation . If the IE NR-UE-RxTx-TEG-Info is present with choice case2 or case3 and this field is absent, the receiver should consider the UE Tx TEG timing error margin value to be the maximum value available in IE TEG-TimingErrorMargin . | +| nr-UE-RxTxTEG-TimingErrorMargin | This field specifies the UE RxTx TEG timing error margin value for all the UE RxTx TEGs within one NR-Multi-RTT-SignalMeasurementInformation . If the IE NR-UE-RxTx-TEG-Info is present with choice case1 or case2 and this field is absent, the receiver should consider the UE RxTx TEG timing error margin value to be the maximum applicable value as defined in TS 38.133 [46]. | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PRS-ID
This field is used along with a DL-PRS Resource Set ID and a DL-PRS Resources ID to uniquely identify a DL-PRS Resource. This ID can be associated with multiple DL-PRS Resource Sets associated with a single TRP. Each TRP should only be associated with one such ID. | +| nr-PhysCellID
This field specifies the physical cell identity of the associated TRP, as defined in TS 38.331 [35]. | +| nr-CellGlobalID
This field specifies the NCGI, the globally unique identity of a cell in NR, of the associated TRP, as defined in TS 38.331 [35]. | +| nr-ARFCN
This field specifies the NR-ARFCN of the TRP's CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID . | +| nr-UE-RxTxTimeDiff
This field specifies the UE Rx-Tx time difference measurement, as defined in TS 38.215 [36]. | +| nr-AdditionalPathList
This field specifies one or more additional detected path timing values for the TRP or resource, relative to the path timing used for determining the nr-UE-RxTxTimeDiff value. If this field was requested but is not included, it means the UE did not detect any additional path timing values. If this field is present, the field nr-AdditionalPathListExt shall be absent. | +| nr-TimeStamp
This field specifies the time instance for which the measurement is performed. If RSCP measurement is present, the timestamp applies to both RSCP and UE Rx-Tx time difference measurement. | +| nr-TimingQuality
This field specifies the target device's best estimate of the quality of the measurement. | +| nr-DL-PRS-RSRP-Result
This field specifies the NR DL-PRS reference signal received power (DL PRS-RSRP) measurement, as defined in TS 38.215 [36]. The mapping of the quantity is defined as in TS 38.133 [46]. | +| nr-Multi-RTT-AdditionalMeasurements
This field provides up to 3 additional UE Rx-Tx time difference measurements corresponding to a single configured SRS Resource or Resource Set for positioning. Each measurement corresponds to a single received DL-PRS Resource or DL-PRS Resource Set [45].
If this field is present, the field nr-Multi-RTT-AdditionalMeasurementsExt shall be absent. | +| nr-UE-RxTx-TEG-Info
This field provides the ID(s) of the UE TEG associated with the nr-UE-RxTxTimeDiff or nr-UE-RxTxTimeDiffAdditional measurement. One of the following combinations of TEG IDs can be provided:
  • - case1 provides the UE RxTx TEG ID;
  • - case2 provides the UE RxTx TEG ID together with the UE Tx TEG ID. The nr-UE-Tx-TEG-Index provides the index to the nr-SRS-TxTEG-Set field for the applicable UE Tx TEG ID, where value '1' indicates the first NR-SRS-TxTEG-Element in nr-SRS-TxTEG-Set, value '2' indicates the second NR-SRS-TxTEG-Element in nr-SRS-TxTEG-Set, and so on;
  • - case3 provides the UE Rx TEG ID together with the UE Tx TEG ID. The nr-UE-Tx-TEG-Index provides the index to the nr-SRS-TxTEG-Set field for the applicable UE Tx TEG ID, where value '1' indicates the first NR-SRS-TxTEG-Element in nr-SRS-TxTEG-Set, value '2' indicates the second NR-SRS-TxTEG-Element in nr-SRS-TxTEG-Set, and so on.
| +| nr-DL-PRS-FirstPathRSRP-Result
This field specifies the NR DL PRS reference signal received path power (DL PRS-RSRPP) of the first detected path in time, as defined in TS 38.215 [36]. The mapping of the measured quantity is defined as in TS 38.133 [46]. | +| nr-los-nlos-Indicator
This field specifies the target device's best estimate of the LOS or NLOS of the UE Rx-Tx Time Difference, RSRP or RSRPP of first path measurement for the TRP or resource.
NOTE: If the requested type or granularity in nr-los-nlos-IndicatorRequest is not possible, the target device may provide a different type and granularity for the estimated LOS-NLOS-Indicator . | +| nr-AdditionalPathListExt
This field provides up to 8 additional detected path timing values for the TRP or resource, relative to the path timing used for determining the nr-UE-RxTxTimeDiff value. If this field was requested but is not included, it means the UE did not detect any additional path timing values. If this field is present, the field nr-AdditionalPathList shall be absent. | +| nr-Multi-RTT-AdditionalMeasurementsExt
This field, in addition to the measurements provided in NR-Multi-RTT-MeasElement , provides UE Rx-Tx time difference measurements of up to 4 DL-PRS Resources of a TRP with different UE RxTx or UE Rx TEGs. For a certain DL-PRS Resource, there can be up to 8 measurement results with respect to different UE RxTx or UE Rx TEGs. If this field is present, the field nr-Multi-RTT-AdditionalMeasurements shall be absent. | +| nr-UE-RxTxTimeDiffBasedOnAggregatedResources
This field indicates whether the measurement is based on aggregation across PFLs for Multi-RTT. | +| nr-AggregatedDL-PRS-ResourceSetID-List
This field provides the PRS resource set IDs and the PRS resource IDs for the aggregated measurement which are used for RSRP/RSRPP and/or timing measurement results. If the field is present, the field nr-DL-PRS-ResourceID and nr-DL-PRS-ResourceSetID should not be included. | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-RSCP
This field specifies the NR DL reference signal carrier phase measurement, as defined in TS 38.215 [36]. Mapping of the measured quantity is defined as in TS 38.133 [46]. | +| nr-PhaseQuality
This field specifies the target device's best estimate of the quality of the RSCP measurement. | +| nr-RSCP-AddSampleMeasurements
This field, in addition to the measurements provided in NR-Multi-RTT-MeasElement , provides up to 3 RSCP measurements associated with the nr-UE-RxTxTimeDiff in NR-Multi-RTT-MeasElement . | +| nr-ReportDL-PRS-MeasBasedOnSingleOrMultiHopRx
This field indicates that the reported measurement is based on receiving single or multiple hops of DL PRS. | +| nr-DL-PRS-RSRP-ResultDiff
This field provides the additional DL-PRS RSRP measurement result relative to nr-DL-PRS-RSRP-Result . The DL-PRS RSRP value of this measurement is obtained by adding the value of this field to the value of the nr-DL-PRS-RSRP-Result . The mapping of this field is defined as in TS 38.133 [46]. | +| nr-UE-RxTxTimeDiffAdditional
This field provides the additional UE Rx-Tx Difference measurement result relative to nr-UE-RxTxTimeDiff . The UE Rx-Tx Difference value of this measurement is obtained by adding the value of this field to the value of the nr-UE-RxTxTimeDiff field. The mapping of the field is defined in TS 38.133 [46]. | +| nr-DL-PRS-FirstPathRSRP-ResultDiff
This field specifies the additional NR DL-PRS reference signal received path power (DL PRS-RSRPP) of the first detected path in time relative to nr-DL-PRS-FirstPathRSRP-Result . The DL-PRS RSRPP of first path value of this measurement is obtained by adding the value of this field to the value of the nr-DL-PRS-FirstPathRSRP-Result field. The mapping of the field is defined in TS 38.133 [46]. | +| nr-los-nlos-IndicatorPerResource
This field specifies the target device's best estimate of the LOS or NLOS of the UE Rx-Tx Time Difference, RSRP or RSRPP of first path measurement for the resource.
This field may only be present if the field nr-LOS-NLOS-Indicator choice indicates perResource . | +| nr-RSCP-AdditionalMeasurements
This field, provides up to 4 RSCP measurements associated with the UE Rx-Tx Time Difference measurement in NR-Multi-RTT-MeasElement . | +| nr-RSCP-ResultDiff
This field provides the additional RSCP measurement result relative to nr-RSCP . The RSCP value of this measurement is obtained by adding the value of this field to the value of the nr-RSCP field. | +| nr-NTN-UE-RxTxTimeDiff
This field provides the offset of the UE Rx-Tx time difference measurement for NTN and comprises the following subfields:
  • - nr-NTN-UE-RxTxTimeDiffSubframeOffset specifies the UE Rx – Tx time difference subframe offset measurement in unit of subframe, as defined in TS 38.215 [36].
  • - nr-NTN-DL-TimingDrift specifies the DL timing drift measurement, as defined in TS 38.215 [36]. The granularity of nr-NTN-DL-TimingDrift is 0.1 ppm. Values are given in unit of corresponding granularity.
| + +## 6.5.12.5 NR Multi-RTT Location Information Request + +### – *NR-Multi-RTT-RequestLocationInformation* + +The IE *NR-Multi-RTT-RequestLocationInformation* is used by the location server to request NR Multi-RTT location measurements from a target device. + +``` +-- ASN1START +NR-Multi-RTT-RequestLocationInformation-r16 ::= SEQUENCE { + nr-UE-RxTxTimeDiffMeasurementInfoRequest-r16 + ENUMERATED { true } OPTIONAL, -- Need ON + nr-RequestedMeasurements-r16 + BIT STRING { prssrpReq (0), + firstPathRsrpReq-r17 (1), + jointMeasurementsReq-r18 (2) } (SIZE(1..8)), + nr-AssistanceAvailability-r16 + BOOLEAN, + nr-Multi-RTT-ReportConfig-r16 + NR-Multi-RTT-ReportConfig-r16, + additionalPaths-r16 + ENUMERATED { requested } OPTIONAL, -- Need ON + .... + [ + nr-UE-RxTxTEG-Request-r17 + ENUMERATED { case1, case2, case3, ... } OPTIONAL, -- Need ON + measureSameDL-PRS-ResourceWithDifferentRxTxTEGs-r17 + ENUMERATED { n0, n2, n3, n4, n6, n8, ... } OPTIONAL, -- Need ON + measureSameDL-PRS-ResourceWithDifferentRxTEGs-r17 + ENUMERATED { n0, n2, n3, n4, n6, n8, ... } +``` + +``` + +reducedDL-PRS-ProcessingSamples-r17 OPTIONAL, -- Need ON +nr-los-nlos-IndicatorRequest-r17 ENUMERATED { requested, ... } OPTIONAL, -- Need ON + SEQUENCE { + type-r17 LOS-NLOS-IndicatorType1-r17, + granularity-r17 LOS-NLOS-IndicatorGranularity1-r17, + ... + } + OPTIONAL, -- Need ON +additionalPathsExt-r17 ENUMERATED { requested } OPTIONAL, -- Need ON +additionalPathsDL-PRS-RSRP-Request-r17 + ENUMERATED { requested } OPTIONAL, -- Need ON +multiMeasInSameReport-r17 ENUMERATED { requested } OPTIONAL, -- Need ON +lowerRxBeamSweepingFactor-FR2-r17 ENUMERATED { requested } OPTIONAL, -- Need ON +[[, +[[ +nr-DL-PRS-RxHoppingRequest-r18 ENUMERATED { requested } OPTIONAL, -- Need ON +nr-DL-PRS-RxHoppingTotalBandwidth-r18 CHOICE { + fr1 ENUMERATED { mhz40, mhz50, mhz80, mhz100}, + fr2 ENUMERATED { mhz100, mhz200, mhz400} +} + OPTIONAL, -- Need ON +timingReportingGranularityFactorExt-r18 INTEGER (6..7) OPTIONAL, -- Need ON +nr-DL-PRS-JointMeasurementRequested-r18 SEQUENCE (SIZE (2..3)) OF + INTEGER (0..nrMaxFreqLayers-1-r16) OPTIONAL, -- Need ON +nr-UE-RSCP-Request-r18 ENUMERATED { requested } OPTIONAL, -- Need ON +nr-DL-PRS-MeasurementTimeWindowsConfig-r18 + NR-DL-PRS-MeasurementTimeWindowsConfig-r18 OPTIONAL -- Need ON +]] +] +} +NR-Multi-RTT-ReportConfig-r16 ::= SEQUENCE { + maxDL-PRS-RxTxTimeDiffMeasPerTRP-r16 INTEGER (1..4) OPTIONAL, -- Need ON + timingReportingGranularityFactor-r16 INTEGER (0..5) OPTIONAL -- Need ON +} + +-- ASN1STOP + +``` + +#### NR-Multi-RTT-RequestLocationInformation field descriptions + +##### **nr-UE-RxTxTimeDiffMeasurementInfoRequest** + +This field, if present, indicates that the target device is requested to report the DL-PRS Resource ID(s) or DL-PRS Resource Set ID(s) associated with the DL-PRS Resources(s) or the DL-PRS Resource Set(s) which are used in determining the UE Rx-Tx time difference measurements. + +##### **nr-AssistanceAvailability** + +This field indicates whether the target device may request additional PRS assistance data from the server. TRUE means allowed and FALSE means not allowed. + +##### **maxDL-PRS-RxTxTimeDiffMeasPerTRP** + +This field specifies the maximum number of UE-Rx-Tx time difference measurements for different DL-PRS Resources or DL-PRS Resource Sets per TRP. + +##### **timingReportingGranularityFactor, timingReportingGranularityFactorExt** + +This field specifies the recommended reporting granularity for the UE Rx-Tx time difference measurements. Value (0.5) corresponds to (*k0..k5*) and value (6..7) corresponds to (*kMinus1..kMinus2*) used for *nr-UE-RxTxTimeDiff* and *nr-UE-RxTxTimeDiffAdditional* in *NR-Multi-RTT-MeasElement*. The UE may select a different granularity value for *nr-UE-RxTxTimeDiff* and *nr-UE-RxTxTimeDiffAdditional*. The *timingReportingGranularityFactorExt* should not be included by the location server and shall be ignored by the target device if *timingReportingGranularityFactor* is included. The *timingReportingGranularityFactor* should not be included by the location server and shall be ignored by the target device if *timingReportingGranularityFactorExt* is included. + +##### **additionalPaths** + +This field, if present, indicates that the target device is requested to provide the *nr-AdditionalPathList* in IE *NR-Multi-RTT-SignalMeasurementInformation*. If this field is present, the field *additionalPathsExt* shall be absent. + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

nr-UE-RxTxTEG-Request
This field, if present, indicates that the target device is requested to provide the NR-UE-RxTx-TEG-Info in IE NR-Multi-RTT-SignalMeasurementInformation. Enumerated value 'case1' indicates that the target device is requested to provide the case1 choice in NR-UE-RxTx-TEG-Info, enumerated value 'case2' indicates that the target device is requested to provide the case2 choice in NR-UE-RxTx-TEG-Info, and so on.

| +|

measureSameDL-PRS-ResourceWithDifferentRxTxTEGs
This field, if present, indicates that the target device is requested to measure the same DL-PRS Resource of a TRP with N different UE RxTx TEGs and with the same UE Tx TEG. Enumerated value 'n0' indicates that the number N of different UE RxTx TEGs to measure the same DL PRS Resource can be determined by the target device, value 'n2' indicates that the target device is requested to measure the same DL-PRS Resource of a TRP with 2 different UE RxTx TEGs, value 'n3' indicates that the target device is requested to measure the same DL-PRS Resource of a TRP with 3 different UE RxTx TEGs, and so on. When the location server requests aggregated measurements, a request for configuring the target device to measure the same aggregated DL-PRS Resources of a TRP with N different UE RxTx TEGs.
If this field is present, the field nr-UE-RxTxTEG-Request should also be present.
If this field is present, the field measureSameDL-PRS-ResourceWithDifferentRxTEGs should not be present.

| +|

measureSameDL-PRS-ResourceWithDifferentRxTEGs
This field, if present, indicates that the target device is requested to measure the same DL-PRS Resource of a TRP with N different UE Rx TEGs. Enumerated value 'n0' indicates that the number N of different UE Rx TEGs to measure the same DL PRS Resource can be determined by the target device, value 'n2' indicates that the target device is requested to measure the same DL-PRS Resource of a TRP with 2 different UE Rx TEGs, value 'n3' indicates that the target device is requested to measure the same DL-PRS Resource of a TRP with 3 different UE Rx TEGs, and so on. When the location server requests aggregated measurements, a request for configuring the UE to measure the same aggregated DL-PRS Resources of a TRP with N different UE Rx TEGs.
If this field is present, the field nr-UE-RxTxTEG-Request should also be present.
If this field is present, the field measureSameDL-PRS-ResourceWithDifferentRxTxTEGs should not be present.

| +|

reducedDL-PRS-ProcessingSamples
This field, if present and set to 'requested', indicates that the target device is requested to perform the requested measurements with reduced number of samples (M=1 or M=2) as specified in TS 38.133 [46]. When requested for aggregated measurements by the location server, this field indicates processing of reduced number of samples for the aggregated measurements.

| +|

nr-los-nlos-IndicatorRequest
This field, if present, indicates that the target device is requested to provide the indicated type and granularity of the estimated LOS-NLOS-Indicator in the NR-Multi-RTT-SignalMeasurementInformation.

| +|

additionalPathsExt
This field, if present, indicates that the target device is requested to provide the nr-AdditionalPathListExt in IE NR-Multi-RTT-SignalMeasurementInformation. If this field is present, the field additionalPaths shall be absent.

| +|

additionalPathsDL-PRS-RSRP-Request
This field, if present, indicates that the target device is requested to provide the nr-DL-PRS-RSRPP for the additional paths in the field nr-AdditionalPathList or nr-AdditionalPathListExt.

| +|

multiMeasInSameReport
This field, if present, indicates that the target device is requested to provide multiple measurement instances in a single measurement report; i.e., include the nr-Multi-RTT-SignalMeasurementInstances in IE NR-Multi-RTT-ProvideLocationInformation.

| +|

lowerRxBeamSweepingFactor-FR2
This field, if present, indicates that the target device is requested to use a lower Rx beam sweeping factor than 8 for FR2 according to UE's capability. When requested for aggregated measurements by the LMF, this field indicates that the target device is requested to use a lower Rx beam sweeping factor than 8 for FR2 according to UE's capability for the aggregated measurements.

| +|

nr-DL-PRS-RxHoppingRequest
This field, if present, indicates that the target device is requested to perform DL PRS Rx hopping measurements and reporting.

| +|

nr-DL-PRS-RxHoppingTotalBandwidth
This field, if present, indicates the total bandwidth of all hops in MHz.

| +|

nr-DL-PRS-JointMeasurementRequested
This field, if present, indicates that the target device is requested to perform joint measurements on the indicated two or three PFLs that are linked for DL PRS BW aggregation. The field can be present if jointMeasurementsReq in nr-RequestedMeasurements is set to one-value. Otherwise, it is absent. Value 0 corresponds to the first frequency layer provided in nr-DL-PRS-AssistanceDataList, value 1 to the second frequency layer in nr-DL-PRS-AssistanceDataList, and so on.

| +|

nr-UE-RSCP-Request
This field, if present, indicates that the device is requested to provide the DL RSCP measurement in IE NR-Multi-RTT-SignalMeasurementInformation together with nr-UE-RxTxTimeDiff.

| +|

nr-DL-PRS-MeasurementTimeWindowsConfig
This field indicates DL-PRS resource set(s) occurring within time window(s) for performing measurements where the time window is indicated by a start time, periodicity, offset and duration.

| + +## 6.5.12.6 NR Multi-RTT Capability Information + +### – NR-Multi-RTT-ProvideCapabilities + +The IE *NR-Multi-RTT-ProvideCapabilities* is used by the target device to indicate its capability to support NR Multi-RTT and to provide its NR Multi-RTT positioning capabilities to the location server. + +``` +-- ASN1START + +NR-Multi-RTT-ProvideCapabilities-r16 ::= SEQUENCE { + nr-Multi-RTT-PRS-Capability-r16 NR-DL-PRS-ResourcesCapability-r16, + nr-Multi-RTT-MeasurementCapability-r16 NR-Multi-RTT-MeasurementCapability-r16, + nr-DL-PRS-QCL-ProcessingCapability-r16 NR-DL-PRS-QCL-ProcessingCapability-r16, + nr-DL-PRS-ProcessingCapability-r16 NR-DL-PRS-ProcessingCapability-r16, + nr-UL-SRS-Capability-r16 NR-UL-SRS-Capability-r16, + additionalPathsReport-r16 ENUMERATED { supported } OPTIONAL, + periodicalReporting-r16 ENUMERATED { supported } OPTIONAL, + ..., + [[ + ten-ms-unit-ResponseTime-r17 ENUMERATED { supported } OPTIONAL, + nr-DL-PRS-ExpectedAoD-or-AoA-Sup-r17 BIT STRING { + eAoD (0), + eAoA (1) + } (SIZE (1..8)) OPTIONAL, + nr-Multi-RTT-On-Demand-DL-PRS-Support-r17 NR-On-Demand-DL-PRS-Support-r17 OPTIONAL, + nr-UE-RxTx-TEG-ID-ReportingSupport-r17 BIT STRING { + case1 (0), + case2 (1), + case3 (2) + } (SIZE (1..8)) OPTIONAL, + nr-los-nlos-IndicatorSupport-r17 SEQUENCE { + type-r17 LOS-NLOS-IndicatorType2-r17, + granularity-r17 LOS-NLOS-IndicatorGranularity2-r17, + ... + } OPTIONAL, + additionalPathsExtSupport-r17 ENUMERATED { n4, n6, n8 } OPTIONAL, + scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupport-r17 OPTIONAL, + nr-dl-prs-AssistanceDataValidity-r17 SEQUENCE { + area-validity-r17 INTEGER (1..maxNrOfAreas-r17) OPTIONAL, + ... + } OPTIONAL, + multiMeasInSameMeasReport-r17 ENUMERATED { supported } OPTIONAL, + mg-ActivationRequest-r17 ENUMERATED { supported } OPTIONAL, + ]], + [[ + posMeasGapSupport-r17 ENUMERATED { supported } OPTIONAL, + ]], + [[ + symbolTimeStampSupport-r18 ENUMERATED { supported } OPTIONAL, + ]] +} + +-- ASN1STOP +``` + +| NR-Multi-RTT-ProvideCapabilities field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ten-ms-unit-ResponseTime
This field, if present, indicates that the target device supports the enumerated value 'ten-milli-seconds' in the IE ResponseTime in IE CommonEsRequestLocationInformation . | +| nr-DL-PRS-ExpectedAoD-or-AoA-Sup
This field, if present, indicates that the target device supports the NR-DL-PRS-ExpectedAoD-or-AoA in NR-DL-PRS-AssistanceData . | +| nr-Multi-RTT-On-Demand-DL-PRS-Support
This field, if present, indicates that the target device supports on-demand DL-PRS requests. | +| nr-UE-RxTx-TEG-ID-ReportingSupport
This field, if present, indicates that the target device supports nr-UE-RxTx-TEG-Info reporting in IE NR-Multi-RTT-SignalMeasurementInformation . This is represented by a bit string, with a one-value at the bit position means the particular case is supported; a zero-value means not supported:
  • - bit 0 indicates that the target device supports the 'case1' choice in NR-UE-RxTx-TEG-Info.
  • - bit 1 indicates that the target device supports the 'case2' choice in NR-UE-RxTx-TEG-Info.
  • - bit 2 indicates that the target device supports the 'case3' choice in NR-UE-RxTx-TEG-Info.
| +| nr-los-nlos-IndicatorSupport
This field, if present, indicates that the target device supports nr-los-nlos-Indicator reporting in IE NR-Multi-RTT-SignalMeasurementInformation .
  • - type indicates whether the target device supports 'hard' value or 'hard' and 'soft' value in IE LOS-NLOS-Indicator.
  • - granularity indicates whether the target device supports LOS-NLOS-Indicator reporting per TRP, per DL-PRS Resource, or both.
NOTE: A single value is reported when both Multi-RTT and DL-TDOA are supported. | +| additionalPathsExtSupport
This field, if present, indicates that the target device supports the nr-AdditionalPathListExt reporting in IE NR-Multi-RTT-SignalMeasurementInformation . The enumerated value indicates the number of additional paths supported by the target device.
NOTE: The supportOfDL-PRS-FirstPathRSRP in IE NR-Multi-RTT-MeasurementCapability also applies to the additional paths. | +| scheduledLocationRequestSupported
This field, if present, indicates that the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonEsRequestLocationInformation – and the time base(s) supported for the scheduled location time. | +| nr-dl-prs-AssistanceDataValidity
This field, if present, indicates that the target device supports validity conditions for pre-configured assistance data and comprises the following subfields:
  • - area-validity indicates that the target device supports pre-configured assistance data with area validity. The integer number indicates the maximum number of areas the target device supports.
| +| multiMeasInSameMeasReport
This field, if present, indicates that the target device supports multiple measurement instances in a single measurement report. | +| mg-ActivationRequest
This field, if present, indicates that the target device supports UL MAC CE for positioning measurement gap activation/deactivation request for DL-PRS measurements. The UE can include this field only if the UE supports mg-ActivationRequestPRS-Meas and mg-ActivationCommPRS-Meas defined in TS 38.331 [35]. | +| posMeasGapSupport
This field, if present, indicates that the target device supports pre-configured positioning measurement gap for DL-PRS measurements. The UE can include this field only if the UE supports mg-ActivationCommPRS-Meas defined in TS 38.331 [35]. | +| symbolTimeStampSupport
This field, if present, indicates that the target device supports reporting timestamp in terms of radio frame timing down to OFDM symbol level. | + +## 6.5.12.6a NR Multi-RTT Capability Information Elements + +### – NR-Multi-RTT-MeasurementCapability + +The IE *NR-Multi-RTT-MeasurementCapability* defines the Multi-RTT measurement capability. The UE can include this IE only if the UE supports *NR-DL-PRS-ResourcesCapability* for Multi-RTT. Otherwise, the UE does not include this IE; + +``` +-- ASN1START +NR-Multi-RTT-MeasurementCapability-r16 ::= SEQUENCE { + maxNrOfRx-TX-MeasFR1-r16 INTEGER (1..4) OPTIONAL, +``` + +``` + +maxNrOfRx-TX-MeasFR2-r16 INTEGER (1..4) OPTIONAL, +supportOfRSRP-MeasFR1-r16 ENUMERATED { supported } OPTIONAL, +supportOfRSRP-MeasFR2-r16 ENUMERATED { supported } OPTIONAL, +srs-AssocPRS-MultiLayersFR1-r16 ENUMERATED { supported } OPTIONAL, +srs-AssocPRS-MultiLayersFR2-r16 ENUMERATED { supported } OPTIONAL, +... +[[ +nr-UE-TEG-Capability-r17 NR-UE-TEG-Capability-r17 OPTIONAL, +multi-RTT-MeasCapabilityBandList-r17 SEQUENCE (SIZE (1..nrMaxBands-r16)) OF + Multi-RTT-MeasCapabilityPerBand-r17 + OPTIONAL +]] +} + +Multi-RTT-MeasCapabilityPerBand-r17 ::= SEQUENCE { + freqBandIndicatorNR-r17 FreqBandIndicatorNR-r16, + supportOfDL-PRS-FirstPathRSRP-r17 ENUMERATED { supported } OPTIONAL, + dl-PRS-MeasRRC-Inactive-r17 ENUMERATED { supported } OPTIONAL, + ... + [[ + supportOfDL-PRS-BWA-RRC-Connected-r18 ENUMERATED { supported } OPTIONAL, + supportOfDL-PRS-BWA-RRC-Inactive-r18 ENUMERATED { supported } OPTIONAL, + nr-NTN-MeasAndReport-r18 ENUMERATED { supported } OPTIONAL + ]] +} + +-- ASN1STOP + +``` + +### NR-Multi-RTT-MeasurementCapability field descriptions + +#### **maxNrOfRx-TX-MeasFR1** + +Indicates the maximum number of UE Rx-Tx time difference measurements corresponding to a single SRS resource/resource set for positioning with each measurement corresponding to a single DL-PRS resource/resource set on FR1. + +#### **maxNrOfRx-TX-MeasFR2** + +Indicates the maximum number of UE Rx-Tx time difference measurements corresponding to a single SRS resource/resource set for positioning with each measurement corresponding to a single DL-PRS resource/resource set on FR2. + +#### **srs-AssocPRS-MultiLayersFR1** + +Indicates whether the UE supports measurements derived on one or more DL-PRS resource/resource sets which may be in different positioning frequency layers for SRS transmitted in a single CC. PRS and SRS may be on different bands. This is for FR1 only. + +#### **srs-AssocPRS-MultiLayersFR2** + +Indicates whether the UE supports measurements derived on one or more DL-PRS resource/resource sets which may be in different positioning frequency layers for SRS transmitted in a single CC. PRS and SRS may be on different bands. This is for FR2 only. + +#### **supportOfRSRP-MeasFR1** + +Indicates whether the UE supports RSRP measurement for Multi-RTT on FR1. + +#### **supportOfRSRP-MeasFR2** + +Indicates whether the UE supports RSRP measurement for Multi-RTT on FR2. + +#### **nr-UE-TEG-Capability** + +Indicates the UE TEG capability. + +#### **supportOfDL-PRS-FirstPathRSRP** + +Indicates whether the target device supports DL-PRS RSRP of first path measurement for Multi-RTT. The UE can include this field only if the UE supports *prs-ProcessingCapabilityBandList*. Otherwise, the UE does not include this field. The UE supporting *additionalPathsReport* and *supportOfDL-PRS-FirstPathRSRP* shall support RSRP reporting for K=1 or 2 additional paths. + +#### **dl-PRS-MeasRRC-Inactive** + +This field, if present, indicates that the target device supports DL-PRS measurement in RRC\_INACTIVE state. The UE can include this field only if the UE supports *maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer*, *maxNrOfTRP-AcrossFreqs*, *maxNrOfPosLayer* and *dl-PRS-BufferType-RRC-Inactive*. Otherwise, the UE does not include this field. + +NOTE: The capabilities *NR-DL-PRS-ResourcesCapability*, *maxNrOfRx-TX-MeasFR1*, *maxNrOfRx-TX-MeasFR2*, *supportOfRSRP-MeasFR1*, *supportOfRSRP-MeasFR2*, *srs-AssocPRS-MultiLayersFR1*, *srs-AssocPRS-MultiLayersFR2*, *simul-NR-DL-AoD-Multi-RTT* are the same in RRC\_INACTIVE state. + +#### **supportOfDL-PRS-BWA-RRC-Connected** + +Indicates whether the target device supports PRS bandwidth aggregation in RRC\_CONNECTED for Multi-RTT. The target device can include this field only if the target device supports *maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer*, *maxNrOfTRP-AcrossFreqs*, *maxNrOfPosLayer* and *prs-BWA-TwoContiguousIntrabandInMG-RRC-Connected*. Otherwise, the UE does not include this field. + +***supportOfDL-PRS-BWA-RRC-Inactive*** + +Indicates whether the target device supports PRS bandwidth aggregation in RRC\_INACTIVE for Multi-RTT. The target device can include this field only if the target device supports *dl-PRS-MeasRRC-Inactive* and *prs-BWA-TwoContiguousIntrabandInMG-RRC-IdleandInactive*. Otherwise, the target device does not include this field. + +***nr-NTN-MeasAndReport*** + +This field, if present, indicates that the UE supports UE Rx-Tx Measurement and Report for Multi-RTT with single satellite in NTN with the following capabilities: + +- UE Rx-Tx time difference and UE Rx-Tx time difference offset measurement and report for Multi-RTT positioning; +- Reporting DL timing drift due to Doppler over the service link associated with the UE Rx-Tx time difference measurement period. + +NOTE: This field is only present, if *freqBandIndicatorNR* indicates the bands in Table 5.2.2-1 in TS 38.101-5 [54]. + +## 6.5.12.7 NR Multi-RTT Capability Information Request + +### – *NR-Multi-RTT-RequestCapabilities* + +The IE *NR-Multi-RTT-RequestCapabilities* is used by the location server to request the capability of the target device to support NR Multi-RTT and to request NR Multi-RTT positioning capabilities from a target device. + +``` +-- ASN1START +NR-Multi-RTT-RequestCapabilities-r16 ::= SEQUENCE { + ... +} +-- ASN1STOP +``` + +## 6.5.12.8 NR Multi-RTT Error Elements + +### – *NR-Multi-RTT-Error* + +The IE *NR-Multi-RTT-Error* is used by the location server or target device to provide NR Multi-RTT error reasons to the target device or location server, respectively. + +``` +-- ASN1START +NR-Multi-RTT-Error-r16 ::= CHOICE { + locationServerErrorCauses-r16 NR-Multi-RTT-LocationServerErrorCauses-r16, + targetDeviceErrorCauses-r16 NR-Multi-RTT-TargetDeviceErrorCauses-r16, + ... +} +-- ASN1STOP +``` + +### – *NR-Multi-RTT-LocationServerErrorCauses* + +The IE *NR-Multi-RTT-LocationServerErrorCauses* is used by the location server to provide NR Multi-RTT error reasons to the target device. + +``` +-- ASN1START +NR-Multi-RTT-LocationServerErrorCauses-r16 ::= SEQUENCE { + cause-r16 ENUMERATED { undefined, + assistanceDataNotSupportedByServer, + assistanceDataSupportedButCurrentlyNotAvailableByServer, + ..., + on-demand-dl-prs-NotSupportedByServer-v1700, + on-demand-dl-prs-SupportedButCurrentlyNotAvailableByServer-v1700 + }, + ... +} +-- ASN1STOP +``` + +## NR-Multi-RTT-TargetDeviceErrorCauses + +The IE *NR-Multi-RTT-TargetDeviceErrorCauses* is used by the target device to provide NR Multi-RTT error reasons to the location server. + +``` +-- ASN1START +NR-Multi-RTT-TargetDeviceErrorCauses-r16 ::= SEQUENCE { + cause-r16 ENUMERATED { undefined, + dl-assistance-data-missing, + unableToMeasureAnyTRP, + attemptedButUnableToMeasureSomeNeighbourTRPs, + ul-srs-configuration-missing, + unableToTransmit-ul-srs, + ... + }, + ..., + [[ + remoteUE-Indication-r18 ENUMERATED {true} OPTIONAL -- Cond NR + ]] +} +-- ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------| +| NR | This field is optionally present, need OR, for NR access. Otherwise it is not present. | + +| NR-Multi-RTT-TargetDeviceErrorCauses field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------| +| remoteUE-Indication
This field indicates whether the target device in NR access is configured as a L2 U2N Remote UE. | + +## 6.6 Multiplicity and type constraint values + +### Multiplicity and type constraint definitions + +``` +-- ASN1START + +maxEARFCN INTEGER ::= 65535 -- Maximum value of EUTRA carrier frequency +maxEARFCN-Plus1 INTEGER ::= 65536 -- Lowest value extended EARFCN range +maxEARFCN2 INTEGER ::= 262143 -- Highest value extended EARFCN range + +maxMBS-r14 INTEGER ::= 64 +maxWLAN-AP-r13 INTEGER ::= 64 +maxKnownAPs-r14 INTEGER ::= 2048 +maxVisibleAPs-r14 INTEGER ::= 32 +maxWLAN-AP-r14 INTEGER ::= 128 +maxWLAN-DataSets-r14 INTEGER ::= 8 + +maxBT-Beacon-r13 INTEGER ::= 32 +maxBT-BeaconAntElt-r18 INTEGER ::= 74 +maxBT-BeaconAD-r18 INTEGER ::= 64 + +nrMaxBands-r16 INTEGER ::= 1024 -- Maximum number of supported bands in + -- UE capability. +nrMaxFreqLayers-r16 INTEGER ::= 4 -- Max freq layers +nrMaxFreqLayers-1-r16 INTEGER ::= 3 +nrMaxNumDL-PRS-ResourcesPerSet-1-r16 INTEGER ::= 63 +nrMaxNumDL-PRS-ResourceSetsPerTRP-1-r16 INTEGER ::= 7 +nrMaxResourceIDs-r16 INTEGER ::= 64 -- Max Resource IDs +nrMaxResourceOffsetValue-1-r16 INTEGER ::= 511 +nrMaxResourcesPerSet-r16 INTEGER ::= 64 -- Maximum resources for one set +nrMaxSetsPerTrpPerFreqLayer-r16 INTEGER ::= 2 -- Maximum resource sets for one TRP +nrMaxSetsPerTrpPerFreqLayer-1-r16 INTEGER ::= 1 +nrMaxTRPs-r16 INTEGER ::= 256 -- Max TRPs per UE +nrMaxTRPsPerFreq-r16 INTEGER ::= 64 -- Max TRPs per freq layers +nrMaxTRPsPerFreq-1-r16 INTEGER ::= 63 +maxSimultaneousBands-r16 INTEGER ::= 4 -- Maximum number of simultaneously + -- measured bands +maxBandComb-r16 INTEGER ::= 1024 +``` + +``` + +nrMaxConfiguredBands-r16 INTEGER ::= 16 +maxNumOfRxTEGs-r17 INTEGER ::= 32 +maxNumOfRxTEGs-1-r17 INTEGER ::= 31 +maxNumOfTxTEGs-1-r17 INTEGER ::= 7 +maxTxTEG-Sets-r17 INTEGER ::= 256 -- Maximum applicable number is 64 +maxNumOfRxTxTEGs-1-r17 INTEGER ::= 255 +maxNumOfTRP-TxTEGs-1-r17 INTEGER ::= 7 +maxNumOfSRS-PosResources-r17 INTEGER ::= 64 +maxNumOfSRS-PosResources-1-r17 INTEGER ::= 63 + +maxNumResourcesPerAngle-r17 INTEGER ::= 24 +maxNumPrioResources-r17 INTEGER ::= 24 + +maxAddMeasTDOA-r17 INTEGER ::= 31 +maxAddMeasAoD-r17 INTEGER ::= 23 +maxAddMeasRTT-r17 INTEGER ::= 31 + +maxOD-DL-PRS-Configs-r17 INTEGER ::= 8 + +maxCellIDsPerArea-r17 INTEGER ::= 256 +maxNrOfAreas-r17 INTEGER ::= 16 +maxMeasInstances-r17 INTEGER ::= 32 + +nrMaxNumPRS-BandWidthAggregation-r18 INTEGER ::= 256 -- Max number of PRS bandwidth + -- aggregation configurations that LMF + -- can provide to the UE +nrNumOfSamples-r18 INTEGER ::= 4 -- NSample of RSCP/RSCPD +nrNumOfSamples-1-r18 INTEGER ::= 3 + +-- ASN1STOP + +``` + +— *End of LPP-PDU-Definitions* + +``` + +-- ASN1START + +END + +-- ASN1STOP + +``` + +## 7 Broadcast of assistance data + +### 7.1 General + +Broadcast of positioning assistance data is supported via Positioning System Information Blocks (posSIBs) as specified in TS 36.331 [12] or TS 38.331 [35]. The posSIBs are carried in RRC System Information (SI) messages (TS 36.331 [12] or TS 38.331 [35]). + +For LTE RRC System Information (SI), a single *SystemInformationBlockPos* IE is defined in TS 36.331 [12] which is carried in IE *PosSystemInformation-r15-IEs* specified in TS 36.331 [12]. The mapping of positioning SIB type (*posSibType*) to assistance data carried in *SystemInformationBlockPos* is specified in clause 7.2. + +For NR RRC System Information (SI), a single *SIBpos* IE is defined in TS 38.331 [35] which is carried in IE *PosSystemInformation-r16-IEs* specified in TS 38.331 [35]. The mapping of positioning SIB type (*posSibType*) to assistance data carried in *SIBpos* is specified in clause 7.2. + +### 7.2 Mapping of *posSibType* to assistance data element + +The supported *posSibType*'s are specified in Table 7.2-1. The GNSS Common and Generic Assistance Data IEs are defined in clause 6.5.2.2. The OTDOA Assistance Data IEs and NR DL-TDOA/DL-AoD Assistance Data IEs are defined in clause 7.4.2. The Barometric Assistance Data IEs are defined in clause 6.5.5.8. The TBS (based on MBS signals) Assistance Data IEs are defined in clause 6.5.4.8. + +**Table 7.2-1: Mapping of *posSibType* to *assistanceDataElement*** + +| | posSibType | assistanceDataElement | +|-----------------------------------------------|------------------------|-------------------------------------------| +| GNSS Common Assistance Data (clause 6.5.2.2) | posSibType1-1 | GNSS-ReferenceTime | +| | posSibType1-2 | GNSS-ReferenceLocation | +| | posSibType1-3 | GNSS-IonosphericModel | +| | posSibType1-4 | GNSS-EarthOrientationParameters | +| | posSibType1-5 | GNSS-RTK-ReferenceStationInfo | +| | posSibType1-6 | GNSS-RTK-CommonObservationInfo | +| | posSibType1-7 | GNSS-RTK-AuxiliaryStationData | +| | posSibType1-8 | GNSS-SSR-CorrectionPoints | +| | posSibType1-9 | GNSS-Integrity-ServiceParameters | +| | posSibType1-10 | GNSS-Integrity-ServiceAlert | +| | posSibType1-11 | GNSS-LOS-NLOS-GridPoints | +| | posSibType1-12 | GNSS-SSR-IOD-Update | +| GNSS Generic Assistance Data (clause 6.5.2.2) | posSibType2-1 | GNSS-TimeModelList | +| | posSibType2-2 | GNSS-DifferentialCorrections | +| | posSibType2-3 | GNSS-NavigationModel | +| | posSibType2-4 | GNSS-RealTimeIntegrity | +| | posSibType2-5 | GNSS-DataBitAssistance | +| | posSibType2-6 | GNSS-AcquisitionAssistance | +| | posSibType2-7 | GNSS-Almanac | +| | posSibType2-8 | GNSS-UTC-Model | +| | posSibType2-9 | GNSS-AuxiliaryInformation | +| | posSibType2-10 | BDS-DifferentialCorrections | +| | posSibType2-11 | BDS-GridModelParameter | +| | posSibType2-12 | GNSS-RTK-Observations | +| | posSibType2-13 | GLO-RTK-BiasInformation | +| | posSibType2-14 | GNSS-RTK-MAC-CorrectionDifferences | +| | posSibType2-15 | GNSS-RTK-Residuals | +| | posSibType2-16 | GNSS-RTK-FKP-Gradients | +| | posSibType2-17 | GNSS-SSR-OrbitCorrections | +| | posSibType2-17a | GNSS-SSR-OrbitCorrectionsSet2 | +| | posSibType2-18 | GNSS-SSR-ClockCorrections | +| | posSibType2-18a | GNSS-SSR-ClockCorrectionsSet2 | +| | posSibType2-19 | GNSS-SSR-CodeBias | +| | posSibType2-20 | GNSS-SSR-URA | +| | posSibType2-20a | GNSS-SSR-URA-Set2 | + +| | | | +|---------------------------------------------------------------------|-----------------------|-------------------------------------------| +| | posSibType2-21 | GNSS-SSR-PhaseBias | +| | posSibType2-22 | GNSS-SSR-STECCorrection | +| | posSibType2-23 | GNSS-SSR-GriddedCorrection | +| | posSibType2-24 | NavIC-DifferentialCorrections | +| | posSibType2-25 | NavIC-GridModelParameter | +| | posSibType2-26 | GNSS-LOS-NLOS-GriddedIndications | +| | posSibType2-27 | GNSS-SSR-SatellitePCVResiduals | +| OTDOA Assistance Data (clause 7.4.2) | posSibType3-1 | OTDOA-UE-Assisted | +| Barometric Assistance Data (clause 6.5.5.8) | posSibType4-1 | Sensor-AssistanceDataList | +| TBS Assistance Data (clause 6.5.4.8) | posSibType5-1 | TBS-AssistanceDataList | +| NR DL-TDOA/DL-AoD Assistance Data (clauses 6.4.3, 7.4.2) | posSibType6-1 | NR-DL-PRS-AssistanceData | +| | posSibType6-2 | NR-UEB-TRP-LocationData | +| | posSibType6-3 | NR-UEB-TRP-RTD-Info | +| | posSibType6-4 | NR-TRP-BeamAntennaInfo | +| | posSibType6-5 | NR-DL-PRS-TRP-TEG-Info | +| | posSibType6-6 | NR-PRU-DL-Info | +| | posSibType6-7 | NR-On-Demand-DL-PRS-Configurations | +| Integrity Assistance Data for NR Positioning Methods (clause 6.4.3) | posSibType7-1 | NR-IntegrityRiskParameters | +| | posSibType7-2 | NR-IntegrityServiceParameters | +| | posSibType7-3 | NR-IntegrityServiceAlert | +| | posSibType7-4 | NR-IntegrityParameters | + +## 7.3 Procedures related to broadcast information elements + +Upon receiving *AssistanceDataSIBElement*, the target device shall: + +- 1> if the *segmentationInfo* is not included: + - 2> if the *cipheringKeyData* is included: + - 3> if the UE has obtained a valid cipher key value and the first portion of the initial Counter denoted $C_0$ corresponding to the *cipherSetID* using NAS signalling: + - 4> if $C_0$ contains less than 128-bits: + - 5> pad out the bit string with zeroes in most significant bit positions to achieve 128 bits. + - 4> if the *d0* field contains less than 128-bits: + - 5> pad out the bit string with zeroes in least significant bit positions to achieve 128 bits, denoted $D_0$ . + - 4> determine the initial Counter $C_1 = (C_0 + D_0) \bmod 2^{128}$ (where all values are treated as non-negative integers); + - 4> determine any subsequent counter $C_i$ from the previous counter $C_{i-1}$ as $C_i = (C_{i-1} + 1) \bmod 2^{128}$ ; + - 4> use the sequence of counters $\langle C_1, C_2, C_3, \dots \rangle$ and the cipher key value to decipher the *assistanceDataElement*; + - 4> decode the deciphered *assistanceDataElement* and deliver the related assistance data to upper layers. + - 3> else: + - 4> discard the *AssistanceDataSIBElement*. + - 2> else: + - 3> decode the *assistanceDataElement* and deliver the related assistance data to upper layers. +- 1> else: + +- 2> if *segmentationOption* indicates 'pseudo-seg': + - 3> if the *cipheringKeyData* is included: + - 4> if the UE has obtained a valid cipher key value and the first portion of the initial Counter denoted $C_0$ corresponding to the *cipherSetID* using NAS signalling: + - 5> if $C_0$ contains less than 128-bits: + - 6> pad out the bit string with zeroes in most significant bit positions to achieve 128 bits. + - 5> if the *d0* field contains less than 128-bits: + - 6> pad out the bit string with zeroes in least significant bit positions to achieve 128 bits, denoted $D_0$ . + - 5> determine the initial Counter $C_1 = (C_0 + D_0) \bmod 2^{128}$ (where all values are treated as non-negative integers); + - 5> determine any subsequent counter $C_i$ from the previous counter $C_{i-1}$ as $C_i = (C_{i-1} + 1) \bmod 2^{128}$ ; + - 5> use the sequence of counters $\langle C_1, C_2, C_3, \dots \rangle$ and the cipher key value to decipher the *assistanceDataElement* segment; + - 5> decode the deciphered *assistanceDataElement* segment and deliver the related assistance data portion together with the *assistanceDataSegmentType* and *assistanceDataSegmentNumber* to upper layers. + - 4> else: + - 5> discard the *AssistanceDataSIBElement* segment. + - 3> else: + - 4> decode the *assistanceDataElement* segment and deliver the related assistance data portion together with the *assistanceDataSegmentType* and *assistanceDataSegmentNumber* to upper layers. +- 2> if *segmentationOption* indicates 'octet-string-seg': + - 3> if all segments of *assistanceDataElement* have been received: + - 4> assemble the assistance data element from the received *assistanceDataElement* segments; + - 5> if the *cipheringKeyData* is included in the first segment: + - 6> if the UE has obtained a valid cipher key value and the first portion of the initial Counter denoted $C_0$ corresponding to the *cipherSetID* using NAS signalling: + - 7> if $C_0$ contains less than 128-bits: + - 8> pad out the bit string with zeroes in most significant bit positions to achieve 128 bits. + - 7> if the *d0* field contains less than 128-bits: + - 8> pad out the bit string with zeroes in least significant bit positions to achieve 128 bits, denoted $D_0$ . + - 7> determine the initial Counter $C_1 = (C_0 + D_0) \bmod 2^{128}$ (where all values are treated as non-negative integers); + - 7> determine any subsequent counter $C_i$ from the previous counter $C_{i-1}$ as $C_i = (C_{i-1} + 1) \bmod 2^{128}$ ; + - 7> use the sequence of counters $\langle C_1, C_2, C_3, \dots \rangle$ and the cipher key value to decipher the assembled assistance data element; + +7> decode the assembled and deciphered assistance data element and deliver the related assistance data to upper layers. + +6> else: + +7> discard the assembled assistance data element. + +5> else: + +6> decode the assembled assistance data element and deliver the related assistance data to upper layers. + +NOTE: As an optional optimisation when *segmentationOption* indicates 'octet-string-seg', a target device may verify if the *cipheringKeyData* is included in the first segment as soon as the first segment is received and, if included, may verify that the UE has obtained a valid cipher key value and the first portion of the initial Counter denoted $C_0$ corresponding to the *cipherSetID* using NAS signalling. When the UE has not obtained a valid cipher key value and initial Counter $C_0$ using NAS signalling, the UE may discard the first segment and ignore all subsequent segments. + +The value for $D_0$ shall be different for different *AssistanceDataSIBElement's* to ensure that the counters derived from $C_1$ for any *assistanceDataElement* are different to the counters for any other *assistanceDataElement* for a given ciphering key. + +$D_0$ shall contain at least 16 least significant bits (LSBs) set to zero to ensure that the values of $D_0$ differ from another by a large value. + +## 7.4 Broadcast information elements + +### 7.4.1 Basic production + +This clause defines the LPP broadcast information elements which are encoded as 'basic production' for system information broadcast purposes (see TS 36.331 [12], TS 38.331 [35]). + +The 'basic production' is obtained from their ASN.1 definitions by use of Basic Packed Encoding Rules (BASIC-PER), Unaligned Variant, as specified in ITU-T Rec. X.691 [22]. It always contains a multiple of 8 bits. + +#### — *LPP-Broadcast-Definitions* + +This ASN.1 segment is the start of the LPP Broadcast definitions. + +``` +-- ASN1START +LPP-Broadcast-Definitions +DEFINITIONS AUTOMATIC TAGS ::= +BEGIN +IMPORTS + OTDOA-ReferenceCellInfo, + OTDOA-NeighbourCellInfoList, + NR-TRP-LocationInfo-r16, + NR-DL-PRS-BeamInfo-r16, + NR-RTD-Info-r16, + NR-IntegrityParametersTRP-LocationInfo-r18, + NR-IntegrityParametersDL-PRS-BeamInfo-r18, + NR-IntegrityParametersRTD-Info-r18, + NR-IntegrityParametersTRP-BeamAntennaInfo-r18 +FROM LPP-PDU-Definitions; +-- ASN1STOP +``` + +## 7.4.2 Element definitions + +### – *AssistanceDataSIBElement* + +The IE *AssistanceDataSIBElement* is used in the IE *SystemInformationBlockPos* as specified in TS 36.331 [12] and IE *SIBpos* as specified in TS 38.331 [35]. + +``` +-- ASN1START + +AssistanceDataSIBElement-r15 ::= SEQUENCE { + valueTag-r15 INTEGER (0..63) OPTIONAL, -- Need OP + expirationTime-r15 UTCTime OPTIONAL, -- Need OP + cipheringKeyData-r15 CipheringKeyData-r15 OPTIONAL, -- Need OP + segmentationInfo-r15 SegmentationInfo-r15 OPTIONAL, -- Need OP + assistanceDataElement-r15 OCTET STRING, + ... +} + +CipheringKeyData-r15 ::= SEQUENCE { + cipherSetID-r15 INTEGER (0..65535), + d0-r15 BIT STRING (SIZE (1..128)), + ... +} + +SegmentationInfo-r15 ::= SEQUENCE { + segmentationOption-r15 ENUMERATED {pseudo-seg, octet-string-seg}, + assistanceDataSegmentType-r15 ENUMERATED {notLastSegment, lastSegment}, + assistanceDataSegmentNumber-r15 INTEGER (0..63), + ... +} + +-- ASN1STOP +``` + +| AssistanceDataSIBElement field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| valueTag
This field is used to indicate to the target device any changes in the broadcast assistance data content. The valueTag is incremented by one, by the location server, every time a modified assistance data content is provided. This field is not included if the broadcast assistance data changes too frequently. If valueTag and expirationTime are absent, the UE assumes that the broadcast assistance data content changes at every broadcast interval. | +| expirationTime
This field indicates how long the broadcast assistance data content is valid. It is specified as UTC time and indicates when the broadcast assistance data content will expire. | +| cipheringKeyData
If present, indicates that the assistanceDataElement octet string is ciphered. | +| segmentationInfo
If present, indicates that the assistanceDataElement is one of many segments. | +| assistanceDataElement
The assistanceDataElement OCTET STRING depends on the posSibType and is specified in Table 7.2-1. NOTE. | +| cipherSetID
This field identifies a cipher set comprising a cipher key value and the first component $C_0$ of the initial counter $C_1$ . | +| d0
This field provides the second component for the initial ciphering counter $C_1$ . This field is defined as a bit string with a length of 1 to 128 bits. A target device first pads out the bit string if less than 128 bits with zeroes in least significant bit positions to achieve 128 bits. $C_1$ is then obtained from $D_0$ and $C_0$ (defined by the cipherSetID ) as:
$C_1 = (D_0 + C_0) \bmod 2^{128}$ (with all values treated as non-negative integers). | +| segmentationOption
Indicates the used segmentation option. | +| assistanceDataSegmentType
Indicates whether the included assistanceDataElement segment is the last segment or not. | +| assistanceDataSegmentNumber
Segment number of the assistanceDataElement segment. A segment number of zero corresponds to the first segment, one corresponds to the second segment, and so on. Segments numbers wraparound should there be more than 64 segments | + +NOTE: For example, if the *posSibType* in IE *PosSIB-Type* defined in TS 36.331 [12] and TS 38.331 [35] indicates '*posSibType1-7*', the *assistanceDataElement* OCTET STRING includes the LPP IE *GNSS-RTK-AuxiliaryStationData*. + +## — OTDOA-UE-Assisted + +The IE *OTDOA-UE-Assisted* is used in the *assistanceDataElement* if the *posSibType* in IE *PosSIB-Type* defined in TS 36.331 [12] indicates 'posSibType3-1'. + +``` +-- ASN1START +OTDOA-UE-Assisted-r15 ::= SEQUENCE { + otdoa-ReferenceCellInfo-r15 OTDOA-ReferenceCellInfo, + otdoa-NeighbourCellInfo-r15 OTDOA-NeighbourCellInfoList, + ... +} +-- ASN1STOP +``` + +### OTDOA-UE-Assisted field descriptions + +| | | +|--------------------------------|-------------------------------------------------------------------------| +| otdoa-ReferenceCellInfo | LPP IE OTDOA-ReferenceCellInfo as defined in clause 6.5.1.2. | +| otdoa-NeighbourCellInfo | LPP IE OTDOA-NeighbourCellInfoList as defined in clause 6.5.1.2. | + +## — NR-UEB-TRP-LocationData + +The IE *NR-UEB-TRP-LocationData* is used in the *assistanceDataElement* if the *posSibType* in IE *PosSIB-Type* defined in TS 38.331 [35] indicates 'posSibType6-2'. + +``` +-- ASN1START +NR-UEB-TRP-LocationData-r16 ::= SEQUENCE { + nr-trp-LocationInfo-r16 NR-TRP-LocationInfo-r16, + nr-dl-prs-BeamInfo-r16 NR-DL-PRS-BeamInfo-r16 OPTIONAL, -- Need ON + ... +} +-- ASN1STOP +``` + +### NR-UEB-TRP-LocationData field descriptions + +| | | +|----------------------------|-----------------------------------------------------------------| +| nr-trp-LocationInfo | LPP IE NR-TRP-LocationInfo as defined in clause 6.4.2.1. | +| nr-dl-prs-BeamInfo | LPP IE NR-DL-PRS-BeamInfo as defined in clause 6.4.2.1. | + +## — NR-UEB-TRP-RTD-Info + +The IE *NR-UEB-TRP-RTD-Info* is used in the *assistanceDataElement* if the *posSibType* in IE *PosSIB-Type* defined in TS 38.331 [35] indicates 'posSibType6-3'. + +``` +-- ASN1START +NR-UEB-TRP-RTD-Info-r16 ::= SEQUENCE { + nr-rtd-Info-r16 NR-RTD-Info-r16, + ... +} +-- ASN1STOP +``` + +### NR-UEB-TRP-RTD-Info field descriptions + +| | | +|--------------------|---------------------------------------------------------| +| nr-rtd-Info | LPP IE NR-RTD-Info as defined in clause 6.4.2.1. | +|--------------------|---------------------------------------------------------| + +## NR-IntegrityParameters + +The IE *NR-IntegrityParameters* is used in the *assistanceDataElement* if the *posSibType* in IE *PosSIB-Type* defined in TS 38.331 [35] indicates 'posSibType7-4'. + +``` +-- ASN1START +NR-IntegrityParameters-r18 ::= SEQUENCE { + nr-IntegrityParametersTRP-LocationInfo-r18 + NR-IntegrityParametersTRP-LocationInfo-r18 OPTIONAL, -- Need OR + nr-IntegrityParametersDL-PRS-BeamInfo-r18 + NR-IntegrityParametersDL-PRS-BeamInfo-r18 OPTIONAL, -- Need OR + nr-IntegrityParametersRTD-Info-r18 + NR-IntegrityParametersRTD-Info-r18 OPTIONAL, -- Need OR + nr-IntegrityParametersTRP-BeamAntennaInfo-r18 + NR-IntegrityParametersTRP-BeamAntennaInfo-r18 OPTIONAL, -- Need OR + ... +} +-- ASN1STOP +``` + +### NR-IntegrityParameters field descriptions + +| | | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| nr-IntegrityParametersTRP-LocationInfo | LPP IE NR-IntegrityParametersTRP-LocationInfo as defined in IE NR-PositionCalculationAssistance in clause 6.4.3. | +| nr-IntegrityParametersDL-PRS-BeamInfo | LPP IE NR-IntegrityParametersDL-PRS-BeamInfo as defined in IE NR-PositionCalculationAssistance in clause 6.4.3. | +| nr-IntegrityParametersRTD-Info | LPP IE NR-IntegrityParametersRTD-Info as defined in IE NR-PositionCalculationAssistance in clause 6.4.3. | +| nr-IntegrityParametersTRP-BeamAntennaInfo | LPP IE NR-IntegrityParametersTRP-BeamAntennaInfo as defined in IE NR-PositionCalculationAssistance in clause 6.4.3. | + +## End of LPP-Broadcast-Definitions + +``` +-- ASN1START + +END + +-- ASN1STOP +``` + +## 7.5 Broadcast ciphering (informative) + +The *assistanceDataElement* OCTET STRING included in IE *AssistanceDataSIBElement* may be ciphered using the 128-bit Advanced Encryption Standard (AES) algorithm (with counter mode). + +AES as specified in [32] and [33] is a block mode cipher algorithm that ciphers blocks of 128 bits at a time. However, Counter mode enables usage for a bit string that is not an exact multiple of 128 bits. Further, Counter mode enables a target (or a server) to perform most of the deciphering (or ciphering) processing independently of receipt of the data to be deciphered (or ciphered) which may enable more efficient processing. Provided counters are chosen in a non-repeating manner by the server (which is a requirement for Counter mode), every block of data will be ciphered in a unique manner. + +The algorithm makes use of a sequence of counters $\langle C_1, C_2, C_3, \dots \rangle$ each containing 128 bits, where $C_1$ is specified by the server and each subsequent counter ( $C_2, C_3$ etc.) is obtained from the previous counter by adding one modulo $2^{128}$ . Each counter $C_i$ is ciphered using the AES algorithm with a common 128-bit key to produce an output block $O_i$ of 128 bits. To perform ciphering, the *assistanceDataElement* is divided into blocks $B_1, B_2, \dots, B_n$ of 128 bits each, except for the last block $B_n$ which may contain fewer than 128 bits. The ciphered *assistanceDataElement* is obtained as a sequence of $n$ blocks containing 128 bits each (except possibly for the last block) given by $(O_1 \text{ XOR } B_1), (O_2 \text{ XOR } B_2), \dots, (O_n \text{ XOR } B_n)$ , where XOR denotes bitwise exclusive OR. In the case of the last block, if $B_n$ contains $m$ bits ( $m < 128$ ), then the $m$ most significant bits of $O_n$ would be used for the exclusive OR. Deciphering is performed in the same way except that the blocks $B_1, B_2, \dots, B_n$ are now obtained from the ciphered message and the result of the exclusive OR operations + +yields the original unciphered message. Figure 7.5-1 provides an illustration of Counter mode for the generic case of an arbitrary block cipher algorithm $CIPH_k$ . + +![Figure 7.5-1: Illustration of Block Ciphering with Counter Mode [33].](170c832d0b8936e975d0e6ef78f00ace_img.jpg) + +The diagram illustrates the Counter mode of operation for an arbitrary block cipher algorithm $CIPH_k$ . It is divided into two main sections: ENCRYPT and DECRYPT. + +**ENCRYPT:** On the left, a bracket labeled 'ENCRYPT' spans the top half. It shows three parallel processing paths for blocks 1, 2, and $n$ . Each path starts with a 'COUNTER' block (labeled 'COUNTER 1', 'COUNTER 2', and 'COUNTER n' respectively) pointing down to an 'INPUT BLOCK' (labeled 'INPUT BLOCK 1', 'INPUT BLOCK 2', and 'INPUT BLOCK n'). Each 'INPUT BLOCK' points down to a 'CIPH $_k$ ' block, which in turn points down to an 'OUTPUT BLOCK' (labeled 'OUTPUT BLOCK 1', 'OUTPUT BLOCK 2', and 'OUTPUT BLOCK n'). An ellipsis '...' is shown between the second and $n$ -th paths. Below each 'OUTPUT BLOCK' is an XOR symbol (a circle with a cross). Each XOR symbol receives two inputs: one from the 'OUTPUT BLOCK' and one from a 'PLAINTEXT' block (labeled 'PLAINTEXT 1', 'PLAINTEXT 2', and 'PLAINTEXT n'). The output of each XOR operation points down to a 'CIPHERTEXT' block (labeled 'CIPHERTEXT 1', 'CIPHERTEXT 2', and 'CIPHERTEXT n'). + +**DECRYPT:** On the right, a bracket labeled 'DECRYPT' spans the bottom half. It shows the reverse process. Each 'CIPHERTEXT' block from the encryption stage points down to an XOR symbol. Each XOR symbol receives two inputs: one from the 'CIPHERTEXT' block and one from the 'CIPHERTEXT' block of the same path (e.g., 'CIPHERTEXT 1' points to the first XOR). The output of each XOR operation points down to an 'OUTPUT BLOCK' (labeled 'OUTPUT BLOCK 1', 'OUTPUT BLOCK 2', and 'OUTPUT BLOCK n'). Each 'OUTPUT BLOCK' points down to an 'INPUT BLOCK' (labeled 'INPUT BLOCK 1', 'INPUT BLOCK 2', and 'INPUT BLOCK n'). Each 'INPUT BLOCK' points down to a 'CIPH $_k$ ' block, which in turn points down to a 'COUNTER' block (labeled 'COUNTER 1', 'COUNTER 2', and 'COUNTER n'). An ellipsis '...' is shown between the second and $n$ -th paths. Finally, each 'COUNTER' block points down to a 'PLAINTEXT' block (labeled 'PLAINTEXT 1', 'PLAINTEXT 2', and 'PLAINTEXT n'). + +Figure 7.5-1: Illustration of Block Ciphering with Counter Mode [33]. + +**Figure 7.5-1: Illustration of Block Ciphering with Counter Mode [33].** + +The algorithms require specific conventions for bit ordering. The bit ordering applicable to ciphering for a ASN.1 PER encoded *assistanceDataElement* is the bit ordering produced by the ASN.1 PER encoding where the first bit is the leading bit number zero, the second bit is bit one etc.. + +The initial counter $C_1$ used to cipher an entire *assistanceDataElement* is provided to a target by a server in two portions. The first portion, denoted $C_0$ , is provided using point to point mode along with the 128-bit ciphering key and an identifier for both of these values as specified in TS 23.271 [3]. The second portion, denoted $D_0(d0)$ , is provided in unciphered form in IE *CipheringKeyData*. A target then obtains $C_1$ as: + +$$C_1 = (C_0 + D_0) \bmod 2^{128} \text{ (where all values are treated as non-negative integers)}$$ + +To obtain any subsequent counter $C_i$ from the previous counter $C_{i-1}$ for any message, the following operation is used: + +$$C_i = (C_{i-1} + 1) \bmod 2^{128}$$ + +**NOTE:** As specified in clause 7.3 the value for $D_0$ is different for different *AssistanceDataSIBElement*'s to ensure that the counters derived from $C_1$ for any *assistanceDataElement* can be different to the counters for any other *assistanceDataElement*. However, a long *assistanceDataElement* or a segmented *assistanceDataElement* would require the use of consecutive counter values $C_1$ to $C_n$ , where $n$ is the *assistanceDataElement* size in bits divided by 128 (and rounded up). There would then be a danger of small changes in the value of $D_0$ for ciphering of different *assistanceDataElement*'s (e.g. $D_0$ being chosen as 1 larger than a previous $D_0$ value) reusing previous counter values. To avoid this, the values of $D_0$ contain 16 least significant bits (LSBs) set to zero, as specified in clause 7.3. + +## Annex A (informative): Change History + +| Change history of TS 36.355 up to v15.5.0 | | | | | | | | +|-------------------------------------------|-------------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 2009-10 | RAN2 #67bis | R2-096252 | | | | RAN2 agreed TS 36.355 v0.1.0 | 0.1.0 | +| 2009-11 | RAN2 #68 | R2-097492 | | | | RAN2 agreed TS 36.355 v2.0.0 | 2.0.0 | +| 2009-12 | RP-46 | RP-091208 | | | | RAN #46 approval of TS 36.355 | 9.0.0 | +| 2010-03 | RP-47 | RP-100304 | 0001 | - | | Clarification on Position location | 9.1.0 | +| | RP-47 | RP-100304 | 0002 | - | | Clarification on UE Rx-Tx time difference supporting capability | 9.1.0 | +| | RP-47 | RP-100304 | 0003 | 2 | | Completion of LPP common material | 9.1.0 | +| | RP-47 | RP-100304 | 0004 | 5 | | Completion of OTDOA in LPP | 9.1.0 | +| | RP-47 | RP-100304 | 0006 | - | | Provision of Frame Drift Information in Network Time | 9.1.0 | +| | RP-47 | RP-100304 | 0007 | - | | Clarification of measurement reference point | 9.1.0 | +| | RP-47 | RP-100304 | 0010 | - | | GNSS-DifferentialCorrectionsSupport | 9.1.0 | +| | RP-47 | RP-100304 | 0011 | - | | BSAlign Indication in GNSS Reference Time | 9.1.0 | +| | RP-47 | RP-100304 | 0012 | 1 | | Changes to reflect LPP ASN.1 review | 9.1.0 | +| | RP-47 | RP-100304 | 0013 | 1 | | Introduction of LPP reliability sublayer | 9.1.0 | +| | RP-47 | RP-100304 | 0015 | - | | LPP error procedures and conditions | 9.1.0 | +| | RP-47 | RP-100304 | 0016 | - | | Triggered Location Information Transfer due to Cell Change | 9.1.0 | +| 2010-06 | RP-48 | RP-100558 | 0018 | 2 | | Addition of need codes to optional LPP information elements | 9.2.0 | +| | RP-48 | RP-100558 | 0019 | 1 | | Miscellaneous corrections to LPP stage 3 | 9.2.0 | +| | RP-48 | RP-100558 | 0020 | 1 | | Small corrections to LPP specification | 9.2.0 | +| | RP-48 | RP-100558 | 0021 | - | | Clarifications of OTDOA parameters | 9.2.0 | +| | RP-48 | RP-100558 | 0022 | 1 | | Signalling support for PRS muting in OTDOA | 9.2.0 | +| | - | - | - | - | | Two times capital R replaced by lower case r in "MeasuredResultsElement" (undoing not intended change) | 9.2.1 | +| 2010-09 | RP-49 | RP-100852 | 0024 | - | | Addition of an EPDU to an LPP Error and LPP Abort | 9.3.0 | +| | RP-49 | RP-100852 | 0026 | - | | Division of LPP into Separate ASN.1 Modules with a Global Identifier | 9.3.0 | +| | RP-49 | RP-100852 | 0028 | - | | Proposed Corrections to LPP Reliable Transport | 9.3.0 | +| | RP-49 | RP-100852 | 0029 | - | | Proposed Corrections to the PeriodicalReportingCriteria in LPP | 9.3.0 | +| | RP-49 | RP-100852 | 0030 | 1 | | Various corrections and clarifications to LPP | 9.3.0 | +| | RP-49 | RP-100852 | 0031 | - | | Support of functional components for LPP reliable transport | 9.3.0 | +| | RP-49 | RP-100852 | 0032 | 1 | | Introduction of EPDU ID requested by OMA LOC | 9.3.0 | +| | RP-49 | RP-100852 | 0035 | 1 | | Several corrections in LPP | 9.3.0 | +| | RP-49 | RP-100852 | 0036 | - | | Clarification to Assistance Data Transfer Procedure | 9.3.0 | +| 2010-12 | RP-50 | RP-101207 | 0037 | - | | Correction of reliable transport terminology in description of LPP-Message | 9.4.0 | +| | RP-50 | RP-101207 | 0038 | - | | One cell with known SFN in OTDOA assistance data | 9.4.0 | +| | RP-50 | RP-101207 | 0039 | 1 | | UE frequency capability for LPP | 9.4.0 | +| | RP-50 | RP-101207 | 0041 | - | | Correction to LPP reliable transport | 9.4.0 | +| | RP-50 | RP-101207 | 0042 | - | | Correction to LPP Error procedure | 9.4.0 | +| | RP-50 | RP-101207 | 0043 | - | | Addition of missing reference to LPPE | 9.4.0 | +| | RP-50 | RP-101207 | 0044 | 2 | | Correction to the OTDOA assistance data | 9.4.0 | +| | RP-50 | RP-101226 | 0040 | - | | Update of 'serving cell' terminology in 36.355 | 10.0.0 | +| 2011-03 | RP-51 | RP-110269 | 0046 | - | | Editorial corrections to 36.355 | 10.1.0 | +| | RP-51 | RP-110269 | 0048 | - | | Removal of FFS for retransmission timer in LPP | 10.1.0 | +| | RP-51 | RP-110269 | 0050 | - | | Correction to code phase encoding in GNSS acquisition assistance | 10.1.0 | +| | RP-51 | RP-110269 | 0052 | 1 | | Clarification on SFN provided with OTDOA measurement | 10.1.0 | +| | RP-51 | RP-110269 | 0053 | 1 | | Introduction of OTDOA inter-freq RSTD measurement indication procedure | 10.1.0 | +| | RP-51 | RP-110269 | 0057 | - | | Small corrections in 36.355 | 10.1.0 | +| | RP-51 | RP-110269 | 0058 | 3 | | Further corrections to the OTDOA assistance data | 10.1.0 | +| 2011-06 | RP-52 | RP-110830 | 0060 | - | | Clarifications to description of OTDOA positioning fields | 10.2.0 | +| 2011-09 | RP-53 | RP-111279 | 0062 | 1 | | Various corrections to LPP | 10.3.0 | +| | RP-53 | RP-111279 | 0064 | - | | Mandatory support of PRS for OTDOA measurements | 10.3.0 | +| 2011-12 | RP-54 | RP-111709 | 0066 | - | | Clarification of packed encoding rules of LPP | 10.4.0 | +| | RP-54 | RP-111709 | 0068 | - | | Clarification of first bit in BIT STRING definitions | 10.4.0 | +| 2012-06 | RP-56 | RP-120808 | 0071 | - | | Usage of additionalInformation IE | 10.5.0 | +| 2012-09 | RP-57 | RP-121424 | 0074 | 2 | | Corrections to GNSS Acquisition Assistance Data | 10.6.0 | +| | RP-57 | - | - | - | | Upgrade to the Release 11 - no technical change | 11.0.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------------------------------|--------| +| 2012-12 | RP-58 | RP-121931 | 0077 | - | | Correcting the referencing of QoS parameters | 11.1.0 | +| | RP-58 | RP-121931 | 0080 | - | | Correction to missing field description in GNSS-AcquisitionAssistance IE | 11.1.0 | +| 2013-03 | RP-59 | RP-130237 | 0083 | 1 | | Extending E-UTRA Frequency Band and EARFCN value range | 11.2.0 | +| | RP-59 | RP-130230 | 0086 | - | | Correction to PRS Muting Configuration | 11.2.0 | +| 2013-06 | RP-60 | RP-130803 | 0088 | - | | Correction for ASN.1 errors from CR0083r1 | 11.3.0 | +| | RP-60 | RP-130803 | 0091 | - | | Correction to integer code phase field description in GNSS Acquisition Assistance | 11.3.0 | +| | RP-60 | RP-130803 | 0093 | - | | Correction to serving cell terminology | 11.3.0 | +| | RP-60 | RP-130803 | 0094 | - | | Encoding of LPP IEs | 11.3.0 | +| 2013-09 | RP-61 | RP-131314 | 0098 | - | | Correction on svReqList | 11.4.0 | +| 2013-12 | RP-62 | RP-131984 | 0103 | - | | Correction to missing capability indication for inter-frequency RSTD measurements | 11.5.0 | +| | RP-62 | RP-131984 | 0107 | 1 | | Correction to Galileo assistance data elements | 11.5.0 | +| | RP-62 | RP-132000 | 0104 | 1 | | Stage 3 CR of TS 36.355 for introducing BDS in LTE | 12.0.0 | +| | RP-62 | RP-131984 | 0108 | - | | Correction to Galileo assistance data elements | 12.0.0 | +| 2014-03 | RP-63 | RP-140342 | 0112 | 1 | | Clarification to gnss-DayNumber | 12.1.0 | +| 2014-06 | RP-64 | RP-140871 | 0119 | - | | Signaling of OTDOA Neighbour Cell Information and Measurements | 12.2.0 | +| 2014-12 | RP-66 | RP-142114 | 0122 | - | | Correction to Galileo Assistance Data | 12.3.0 | +| | RP-66 | RP-142114 | 0123 | - | | Addition of an Early Position Fix to LPP | 12.3.0 | +| | RP-66 | RP-142120 | 0124 | - | | BDS update to version 2.0 | 12.3.0 | +| 2015-03 | RP-67 | RP-150369 | 0126 | 2 | | Correction of GLONASS system time | 12.4.0 | +| | RP-67 | RP-150376 | 0125 | 1 | | LPP clean-up | 12.4.0 | +| 2015-12 | RP-70 | RP-152055 | 0134 | 1 | | Correction to the definition of Need codes | 12.5.0 | +| 2015-12 | RP-70 | RP-152068 | 0137 | 3 | | RAT-Independent positioning enhancements | 13.0.0 | +| 2016-03 | RP-71 | RP-160463 | 0138 | 1 | | Correction to GLONASS IOD value range | 13.1.0 | +| | RP-71 | RP-160470 | 0140 | 1 | | r13 Information Element correction | 13.1.0 | +| | RP-71 | RP-160470 | 0141 | - | | WLAN AP Identifier correction | 13.1.0 | +| | RP-71 | RP-160470 | 0142 | 1 | | LPP clean-up | 13.1.0 | +| 2016-09 | RP-73 | RP-161750 | 0143 | 4 | | Correction of ECID positioning for TDD | 13.2.0 | +| 2016-12 | RP-74 | RP-162317 | 0160 | 1 | | Clarification of WLAN RSSI value range | 13.3.0 | +| 2016-12 | RP-74 | RP-162326 | 0155 | 1 | | CR for 36.355 Further Indoor positioning enhancements | 14.0.0 | +| | RP-74 | RP-162327 | 0157 | - | | Barometric Pressure Uncertainty IEs | 14.0.0 | +| | RP-74 | RP-162326 | 0161 | 1 | | Introduction of Further Indoor Positioning Enhancements | 14.0.0 | +| 2017-03 | RP-75 | RP-170636 | 0162 | 3 | B | Introduction of positioning for further enhanced MTC | 14.1.0 | +| | RP-75 | RP-170642 | 0163 | - | C | Addition of periodical and triggered reporting capability signalling | 14.1.0 | +| | RP-75 | RP-170642 | 0165 | 2 | F | Further Indoor positioning enhancements corrections | 14.1.0 | +| | RP-75 | RP-170637 | 0166 | - | B | Introduction of positioning support for NB-IoT | 14.1.0 | +| 2017-06 | RP-76 | RP-171224 | 0169 | 3 | F | Compact Signal Measurement Information for OTDOA | 14.2.0 | +| | RP-76 | RP-171223 | 0171 | 1 | F | Correction to PRS Subframe Offset | 14.2.0 | +| | RP-76 | RP-171223 | 0173 | 1 | F | Correction to SFN time stamp in OTDOA Signal Measurement Information | 14.2.0 | +| | RP-76 | RP-171223 | 0174 | 1 | F | Correction to OTDOA capabilities | 14.2.0 | +| | RP-76 | RP-171224 | 0175 | 1 | F | Correction to NPRS | 14.2.0 | +| | RP-76 | RP-171225 | 0176 | 2 | F | LPP clean-up | 14.2.0 | +| | RP-76 | RP-171224 | 0177 | - | F | Corrections to number of NPRS carriers and ECID measurements for NB-IoT | 14.2.0 | +| | RP-76 | RP-171224 | 0178 | 1 | F | Removal of FFS for retransmission timer in LPP | 14.2.0 | +| | RP-76 | RP-171224 | 0181 | 1 | F | Signalling optimisation for NB-IoT Enhancements | 14.2.0 | +| 2017-09 | RP-77 | RP-171913 | 0182 | 2 | F | Clarification on definition of PRS Occasion Group | 14.3.0 | +| | RP-77 | RP-171914 | 0183 | 1 | F | Additional OTDOA Capabilities | 14.3.0 | +| | RP-77 | RP-171911 | 0184 | - | F | Clarification to GNSS-TimeModelList | 14.3.0 | +| | RP-77 | RP-171913 | 0185 | 1 | F | Minor corrections on TS 36.355 for Rel-14 MTC | 14.3.0 | +| 2017-12 | RP-78 | RP-172616 | 0187 | 2 | F | Correction on PRS hopping configuration | 14.4.0 | +| 2018-03 | RP-79 | RP-180446 | 0189 | 1 | F | Segmentation of LPP Messages | 14.5.0 | +| 2018-04 | RP-79 | | | | | New version to fix ASN.1 formatting | 14.5.1 | +| 2018-06 | RP-80 | RP-181235 | 0202 | 2 | F | Clarification for NRSRQ reporting with E-CID | 14.6.0 | +| 2018-06 | RP-80 | RP-181219 | 0204 | 2 | B | Introduction of IMU support for OTDOA | 15.0.0 | +| | RP-80 | RP-181219 | 0205 | 1 | B | Addition of RTK and PPP support | 15.0.0 | +| | RP-80 | RP-181219 | 0207 | 1 | B | Addition of broadcast of positioning assistance data | 15.0.0 | +| | RP-80 | RP-181215 | 0209 | 1 | B | Addition of NR Support | 15.0.0 | +| | RP-80 | RP-181252 | 0210 | 1 | B | Addition of NB-IoT TDD support | 15.0.0 | +| 2018-09 | RP-81 | RP-181963 | 0215 | 1 | A | Support for NPRS enhancements | 15.1.0 | +| | RP-81 | RP-181945 | 0218 | 1 | F | Corrections to TDD in 36.355 | 15.1.0 | +| | RP-81 | RP-181961 | 0221 | 3 | A | Correction to RSRQ range in 36.355 | 15.1.0 | +| | RP-81 | RP-181942 | 0222 | 1 | F | OTDOA Assistance Data Request for NR | 15.1.0 | +| | RP-81 | RP-181960 | 0223 | - | F | LPP clean-up | 15.1.0 | +| | RP-81 | RP-181952 | 0224 | 1 | F | GAD shapes for high accuracy positioning | 15.1.0 | +| | RP-81 | RP-181952 | 0226 | 1 | B | Positioning SIB value tag and expiration time | 15.1.0 | +| 2018-12 | RP-82 | RP-182672 | 0213 | 3 | F | Addition of TDD UL/DL configuration to OTDOA assistance data | 15.2.0 | +| | RP-82 | RP-182681 | 0228 | 2 | F | Introduction of TDD UL/DL configuration for NB-IoT in 36.355 | 15.2.0 | +| | RP-82 | RP-182659 | 0229 | 3 | F | SFN offset for OTDOA | 15.2.0 | +| | RP-82 | RP-182674 | 0230 | 1 | F | Alignment of IE/field names between LPP and RRC specifications | 15.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------------|--------| +| | RP-82 | RP-182672 | 0232 | 1 | F | Sensor Assistance Data Elements Correction | 15.2.0 | +| 2019-03 | RP-83 | RP-190550 | 0234 | 3 | F | Stage 2 and stage 3 sensor methods description alignment | 15.3.0 | +| 2019-06 | RP-84 | RP-191376 | 0239 | 1 | F | Minor corrections on NR Support | 15.4.0 | +| | RP-84 | RP-191384 | 0240 | 4 | F | Periodic assistance data transfer with cell ID change procedure | 15.4.0 | +| 2019-09 | RP-85 | RP-192196 | 0243 | 1 | F | Distinguishing Location Source when sensor method is used | 15.5.0 | + +NOTE: The table above will not be further updated in the future. It shows all TS 36.355 CRs taken over into TS 37.355 v1.0.0. + +| Change history of TS 37.355 | | | | | | | | +|-----------------------------|-------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 2019-12 | RP-86 | RP-192450 | - | - | - | TS 36.355 v15.5.0 contents was transferred into this new TS 37.355 as by definition 36 series specifications cover E-UTRA/LTE only aspects and multi-RAT aspects need to be covered in 37 series specifications.
The only changes compared to TS 36.355 v15.5.0:
- new 37 series TS number is added: TS 37.355
- "Evolved Universal Terrestrial Radio Access (E-UTRA)" is removed from the TS title as beginning with Rel-15 TS 36.355 needs to cover also NR
- clarification in the Scope clause that this TS covers radio access technologies E-UTRA/LTE and NR
- the CR history table of TS 36.355 was kept for easier reference of all changes included in TS 37.355 but a new CR history table was added for TS 37.355. | 1.0.0 | +| 2019-12 | RP-86 | | | | | The approved version upgraded to v15.0.0 by MCC. | 15.0.0 | +| 2020-03 | RP-87 | RP-200367 | 0001 | 2 | C | Addition of broadcast of barometric pressure assistance data | 16.0.0 | +| | RP-87 | RP-200357 | 0002 | 1 | F | Sensor Provide Location Information Elements Correction | 16.0.0 | +| | RP-87 | RP-200365 | 0247 | 8 | B | CR of TS 37.355 for introducing NavIC in LTE – core part | 16.0.0 | +| | RP-87 | RP-200357 | 0248 | 1 | B | Introduction of B1C signal in BDS system in A-GNSS | 16.0.0 | +| | RP-87 | RP-200367 | 0249 | 1 | C | Addition of broadcast TBS assistance data | 16.0.0 | +| | RP-87 | RP-200345 | 0250 | 2 | B | Introduction of NR positioning | 16.0.0 | +| | RP-87 | RP-200357 | 0252 | 1 | B | Introducing support for GNSS Integer Ambiguity Level Indications | 16.0.0 | +| 2020-07 | RP-88 | RP-201196 | 0257 | 2 | F | Introduction of NavIC Keplerian set IE | 16.1.0 | +| | RP-88 | RP-201190 | 0259 | 1 | F | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS | 16.1.0 | +| | RP-88 | RP-201175 | 0260 | - | F | LPP Clean-Up | 16.1.0 | +| | RP-88 | RP-201175 | 0261 | 1 | B | Introduction of Release-16 UE positioning capabilities | 16.1.0 | +| 2020-09 | RP-89 | RP-201989 | 0272 | - | F | LPP miscellaneous corrections | 16.2.0 | +| 2020-12 | RP-90 | RP-202775 | 0274 | - | F | Clarification of quality and time stamp for RSTD measurements | 16.3.0 | +| | RP-90 | RP-202789 | 0280 | 2 | F | Correction of hanging ASN.1 code after END | 16.3.0 | +| | RP-90 | RP-202775 | 0282 | - | F | Correction on LPP spec | 16.3.0 | +| 2021-03 | RP-91 | RP-210695 | 0284 | 1 | F | Corrections on the field description of commonEsProvideAssistanceData in TS37.355 | 16.4.0 | +| 2021-06 | RP-92 | RP-211474 | 0288 | 4 | F | LPP Layer interaction with lower layers for Positioning Frequency layer and Measurement Gap | 16.5.0 | +| | RP-92 | RP-211482 | 0292 | 3 | F | Correction to the need code for downlink LPP message-R16 | 16.5.0 | +| | RP-92 | RP-211474 | 0294 | 2 | F | Miscellaneous corrections on the field description | 16.5.0 | +| | RP-92 | RP-211474 | 0300 | 2 | F | Correction to PRS configuration | 16.5.0 | +| | RP-92 | RP-211474 | 0301 | 2 | F | Correction to the uplink LPP message | 16.5.0 | +| | RP-92 | RP-211474 | 0302 | 3 | F | Correction to DL-PRS capability | 16.5.0 | +| | RP-92 | RP-211474 | 0306 | 2 | F | Correction to NR-ARFCN of the TRP | 16.5.0 | +| | RP-92 | RP-211474 | 0311 | - | F | Description on timestamp reference in NR positioning measurement report | 16.5.0 | +| 2021-09 | RP-93 | RP-212443 | 0305 | 5 | F | Correction to PRS-only TP | 16.6.0 | +| | RP-93 | RP-212443 | 0312 | 1 | F | Correction for LPP assistance information | 16.6.0 | +| | RP-93 | RP-212443 | 0313 | 1 | F | Corrections on the conditional presence tag clarification for Uplink LPP message | 16.6.0 | +| | RP-93 | RP-212443 | 0318 | - | F | Correction to the need code in NR-SelectedDL-PRS-IndexList | 16.6.0 | +| 2021-12 | RP-94 | RP-213344 | 0321 | 2 | F | Updates based on RAN1 NR positioning features list | 16.7.0 | +| | RP-94 | RP-213345 | 0323 | 3 | F | Correction on BDS B2I clock model [Rel16BDS] | 16.7.0 | +| 2022-03 | RP-95 | RP-220835 | 0326 | - | F | Addition of missing need code for the BDS TGD2 parameter | 16.8.0 | +| | RP-95 | RP-220472 | 0329 | 1 | A | Correction on the object identifier of LPP ASN.1 for R16 | 16.8.0 | +| | RP-95 | RP-220835 | 0330 | - | F | Correction of reference TRP for DL-AoD and Multi-RTT measurement report | 16.8.0 | +| | RP-95 | RP-220835 | 0331 | - | F | Correction to NR-DL-PRS-ResourcesCapability field description | 16.8.0 | +| | RP-95 | RP-220835 | 0333 | 1 | F | Introducing new high accuracy GAD shape with scalable uncertainty | 16.8.0 | +| 2022-03 | RP-95 | RP-220479 | 0332 | - | B | Introduction of R17 Positioning Enhancements in LPP | 17.0.0 | +| 2022-06 | RP-96 | RP-221725 | 0347 | - | F | LPP Updates and ASN.1 Corrections | 17.1.0 | +| | RP-96 | RP-221736 | 0349 | 2 | B | NMEA GGA sentence info in high accuracy GNSS location estimates [HA-GNSS-NMEA] | 17.1.0 | +| 2022-09 | RP-97 | RP-222524 | 0359 | 2 | F | Corrections on LPP capabilities | 17.2.0 | +| | RP-97 | RP-222524 | 0377 | 1 | F | Correction on the GNSS Orbit and Clock Integrity Bounds in TS 37.355 | 17.2.0 | +| | RP-97 | RP-222524 | 0378 | 1 | F | Miscellaneous LPP Corrections | 17.2.0 | +| 2022-12 | RP-98 | RP-223411 | 0379 | 3 | F | Correction to UE capability for DL-AoD | 17.3.0 | +| | RP-98 | RP-223411 | 0386 | 3 | F | Various LPP Corrections | 17.3.0 | +| | RP-98 | RP-223408 | 0389 | 1 | A | Corrections of LPP capabilities on DL-RPS | 17.3.0 | +| | RP-98 | RP-223408 | 0392 | - | A | Correction to DL-PRS Search Window calculation | 17.3.0 | +| | RP-98 | RP-223408 | 0394 | 1 | A | Correction of NR DL-PRS BeamInfo attribute associated-DL-PRS-ID field description | 17.3.0 | +| | RP-98 | RP-223408 | 0400 | 1 | A | Correcting field description and definition of GNSS-SSR-URA | 17.3.0 | +| 2023-03 | RP-99 | RP-230688 | 0404 | 1 | F | Miscellaneous Corrections to LPP | 17.4.0 | +| | RP-99 | RP-230688 | 0405 | 3 | F | Correction to UE capability for MG (de-)activation | 17.4.0 | +| | RP-99 | RP-230688 | 0408 | 1 | F | Miscellaneous corrections for Positioning capabilities | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | RP-99 | RP-230686 | 0412 | 1 | A | Clarifying Galileo NAV message in the GNSS Navigation model to clarify SSR clock correction signal reference | 17.4.0 | +| | RP-99 | RP-230686 | 0413 | 1 | A | Correction of Note in NR-DL-PRS-AssistanceData field descriptions and Addition of missing field description | 17.4.0 | +| | RP-99 | RP-230688 | 0416 | - | F | Correction to UE capability for PRS measurement within a PPW | 17.4.0 | +| | RP-99 | RP-230720 | 0418 | - | A | Correction for SRS-PosResourcesPerBand | 17.4.0 | +| 2023-06 | RP-100 | RP-231412 | 0431 | 2 | F | Corrections on applicability of timing error margin of RxTEG in NR-Multi-RTT-SignalMeasurementInformation field descriptions and other Miscellaneous corrections | 17.5.0 | +| | RP-100 | RP-231412 | 0432 | 1 | F | Miscellaneous corrections on LPP | 17.5.0 | +| | RP-100 | RP-231412 | 0442 | 2 | F | LOS-NLOS-Indicator Types | 17.5.0 | +| | RP-100 | RP-231412 | 0445 | 1 | F | LPP capability for FGs27-13a,14a and 14-2 | 17.5.0 | +| | RP-100 | RP-231412 | 0448 | 1 | F | Miscellaneous LPP Corrections | 17.5.0 | +| | RP-100 | RP-231411 | 0452 | 1 | A | GNSS Tropospheric Delay Correction field description | 17.5.0 | +| 2023-09 | RP-101 | RP-232667 | 0455 | 2 | F | Correction to Multi-RTT | 17.6.0 | +| | RP-101 | RP-232567 | 0461 | 2 | F | GNSS SSR BDS orbit ephemeris reference clarification to align with RTCM | 17.6.0 | +| | RP-101 | RP-232667 | 0464 | 1 | F | Addition of missing values for dl-prs-ResourceSetPeriodicityReq-r17 | 17.6.0 | +| 2023-12 | RP-102 | RP-233888 | 0474 | 2 | F | Field description correction for HA-GNSS metrics | 17.7.0 | +| | RP-102 | RP-233888 | 0475 | 1 | F | Correction to UE TEG Capability | 17.7.0 | +| | RP-102 | RP-233888 | 0477 | 1 | F | Clarification on the field description of dl-prs-ResourceSetPeriodicityReq | 17.7.0 | +| | RP-102 | RP-233888 | 0478 | - | F | Correction to UE capability for batch reporting | 17.7.0 | +| | RP-102 | RP-233888 | 0485 | 2 | F | Correction on transmission of SSR Assistance Data based on BDS B1C | 17.7.0 | +| 2023-12 | RP-102 | RP-233881 | 0437 | 4 | B | Introduction of 1-symbol PRS in 37.355[1symbol_PRS] | 18.0.0 | +| | RP-102 | RP-233881 | 0444 | 3 | C | Support positioning of L2 UE-to-network remote UEs [PosL2RemoteUE] | 18.0.0 | +| | RP-102 | RP-233882 | 0446 | 6 | B | GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] | 18.0.0 | +| | RP-102 | RP-233881 | 0447 | 1 | C | Support of Local Cartesian Coordinates in LPP [PosLocalCoords] | 18.0.0 | +| | RP-102 | RP-233882 | 0465 | 2 | C | SSR Satellite PCV Residuals [Rel18PCV] | 18.0.0 | +| | RP-102 | RP-233881 | 0480 | 1 | B | Bluetooth AoA/AoD support [BT-AoA-AoD] | 18.0.0 | +| | RP-102 | RP-233901 | 0481 | 2 | B | Introduction of Expanded and improved NR positioning | 18.0.0 | +| | RP-102 | RP-233906 | 0482 | 1 | B | Introduction of network verification of UE location in TS 37.355 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37460/raw.md b/marked/Rel-18/37_series/37460/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..838e1a07d69d2faf2d2b1751fce72d6b507e3bd7 --- /dev/null +++ b/marked/Rel-18/37_series/37460/raw.md @@ -0,0 +1,307 @@ + + +# 3GPP TS 37.460 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Iuant interface: General aspects and principles (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +## --- **Keywords** + +radio, antenna + +## **3GPP** + +## --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|----------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 5 | +| 4 General aspects ..... | 6 | +| 4.1 Introduction ..... | 6 | +| 4.2 Iuant interface general principles ..... | 6 | +| 4.3 Iuant interface specification objectives ..... | 6 | +| 4.4 Iuant interface characteristics..... | 6 | +| 5 Functions of the Iuant interface protocols..... | 7 | +| 5.1 Physical layer functions ..... | 7 | +| 5.2 Data link layer functions ..... | 7 | +| 5.3 Application layer functions ..... | 8 | +| 5.3.1 Control of RET antennas ..... | 8 | +| 5.3.2 Application software and configuration data download..... | 8 | +| 5.3.3 Alarm reporting ..... | 8 | +| 5.3.4 Operator specific data storage ..... | 8 | +| 5.3.5 Control of Tower Mounted Amplifiers (TMAs) ..... | 8 | +| 6 Other Iuant interface specifications ..... | 9 | +| 6.1 Iuant interface: Layer 1 (TS 37.461)..... | 9 | +| 6.2 Iuant interface: Signalling Transport (TS 37.462) ..... | 9 | +| 6.3 Void..... | 9 | +| 6.4 Summary of Iuant interface Technical Specifications ..... | 9 | +| 6.5 Iuant interface: Application part specification (TS 37.466)..... | 9 | +| Annex A (informative): OSI model overview ..... | 10 | +| Annex B (informative): Change History..... | 11 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is an introduction to the 3GPP TS 37.46x series of Technical Specifications that define the Iuant Interface. The Iuant interface is applicable for UTRAN, E-UTRAN and NG-RAN. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". The logical Iuant interface is an interface internal to the RAN Node and defined to reside between the implementation specific O&M function and the RET antennas and between the implementation specific O&M function and the TMA control unit function. + +# --- 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 37.461: "Iuant Interface: Layer 1". +- [3] 3GPP TS 37.462: "Iuant Interface: Signalling Transport". +- [4] void +- [5] ISO/IEC 13239 (2nd Edition, March 2000): "Information Technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures". +- [6] 3GPP TS 25.442: "UTRAN implementation-specific O&M transport". +- [7] 3GPP TS 37.466: "Iuant interface: Application Part". +- [8] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [8]. + +| | | +|---------|--------------------------------------------| +| HDLC | High-Level Data Link Control | +| IP | Internet Protocol | +| O&M | Operations & Maintenance | +| OSI | Open Systems Interconnection | +| RET | Remote Electrical Tilting | +| RETAP | Remote Electrical Tilting Application Part | +| TMA | Tower Mounted Amplifier | +| TMAAP | Tower Mounted Amplifier application part | +| UMTS | Universal Mobile Telecommunications System | +| E-UTRAN | Evolved UTRAN | + +# 4 General aspects + +## 4.1 Introduction + +The Iuant interface for the control of RET antennas or TMAs is a logical part of the RAN Node as shown for a Node B in figure 9 of TS 25.401 [1] for UTRAN. Therefore, no new RAN element for the RET antennas or TMAs and no new RAN element manager is needed. The existing Implementation Specific O&M transport (see TS 25.442 [6] for UMTS) is used for the connection between the RET antennas or TMAs control unit and the Node B element manager. + +The Iuant interface between the Implementation Specific O&M function and the RET antenna control unit function is specified in detail in the specifications for layer 1, signalling transport and RET application part (TS 37.461 [2], TS 37.462 [3], TS 37.466 [7]). + +## 4.2 Iuant interface general principles + +The Iuant interface for the RET antenna control is based on a three-layer protocol model. The three-layer model is a compact form of the OSI seven-layer reference model and includes only layers 1, 2 and 7: + +- The Physical Layer (Layer 1) defines the signalling levels and basic data characteristics including the data rates; +- The Data Link Layer (Layer 2) for the Signalling Transport uses a specific class of the HDLC standard as defined in ISO/IEC 13239 [5]; +- The Application Layer (Layer 7) defines the data payload format and the required command set. This layer is called the "Iuant: Application Part". + +This compact model for the control interface provides an efficient protocol stack suitable for implementation on a single embedded micro-controller. + +## 4.3 Iuant interface specification objectives + +The Iuant interface specifications shall facilitate the following: + +- Controlling the tilting of RET antennas remotely from the O&M Network and locally from the Node B; +- Indicating of TMA alarms and optionally controlling the gain of TMAs remotely from the O&M Network and locally from the Node B; +- Interfacing a mix of RET antennas, TMAs and RAN Node from different vendors; +- Providing RET or TMAs functionality accompanied by an appropriate set of signalling commands and control parameters; +- Support of error and alarm handling. + +## 4.4 Iuant interface characteristics + +The Iuant interface has a protocol structure as shown below in figure 4.4.1. + +![Figure 4.4.1: Protocol structure for Iuant interface. The diagram shows two protocol stacks separated by a vertical line labeled 'Iuant'. The left stack, labeled 'RAN Node', consists of a top section 'Implementation specific O&M function', a middle section 'See Reference [6]' (blue), and a bottom section 'PHY' (yellow). The right stack consists of a top section 'RETAP TMAAP' (yellow), a middle section 'HDLC' (yellow), and a bottom section 'PHY' (yellow). The 'PHY' layers of both stacks are connected to the 'Iuant' interface.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +Figure 4.4.1: Protocol structure for Iuant interface. The diagram shows two protocol stacks separated by a vertical line labeled 'Iuant'. The left stack, labeled 'RAN Node', consists of a top section 'Implementation specific O&M function', a middle section 'See Reference [6]' (blue), and a bottom section 'PHY' (yellow). The right stack consists of a top section 'RETAP TMAAP' (yellow), a middle section 'HDLC' (yellow), and a bottom section 'PHY' (yellow). The 'PHY' layers of both stacks are connected to the 'Iuant' interface. + +**Figure 4.4.1: Protocol structure for Iuant interface** + +As the Iuant and the Implementation Specific O&M are different interfaces with e.g. different addressing schemes a mediation function is needed. This mediation function uses on one side a protocol that uses the implementation specific O&M bearer (e.g. IP) and on the other side the Iuant protocol. + +# 5 Functions of the Iuant interface protocols + +## 5.1 Physical layer functions + +The physical layer provides a multi drop broadcast link between the primary device (RAN Node) and all secondary devices (RET antennas or TMAs). Any message transmitted will be received by all other devices. If two devices transmit at the same time, their messages will be garbled. + +The connection requires a half duplex communication, which requires an appropriate scheme for the timing and access control of the connection. + +## 5.2 Data link layer functions + +The data link layer provides: + +- A data packet communication format; +- An addressing scheme; +- A relationship whereby the primary device controls the half duplex timing; +- A message checksum scheme to protect from transmission errors; +- A message sequence numbering scheme which protects layer 7 from: + +- Duplicated messages; +- Deleted messages; +- Receiving messages in the wrong order. +- A flow control mechanism protecting each device from being overrun by messages. + +These functions provide layer 7 with a safe full-duplex connection between the primary device and any secondary device. This full duplex connection allows both the primary and secondary device to transmit layer 7 messages to the opposite device of the connection, whenever they need to. Actual delivery time on layer 2 will depend on the layer 2 polling frequency, which is chosen by the primary device. + +## 5.3 Application layer functions + +The list of functions on the Iuant interface is the following: + +- Control of RET antennas; +- Application software and configuration data download; +- Alarm Reporting; +- Operator specific data storage; +- Control of Tower Mounted Amplifiers (TMAs). + +### 5.3.1 Control of RET antennas + +A RET device provides means to adjust the electrical tilt of one or multiple antennas. The set of procedures to control RET antennas provides means to control the electrical tilt of one or more RET antennas remotely. The procedures are defined in TS 37.466 [7]. + +### 5.3.2 Application software and configuration data download + +The interface provides means for downloading new application software and configuration data to a secondary device. + +The support of application software download to a secondary device is optional. If a secondary device supports application software download, it shall reset itself and start running the new application software automatically after the completed download. Further details on the software download procedure (e.g. the different states of the secondary device and the supported elementary procedures in these states) are described in subclause 6.1 of TS 37.466 [7]. + +### 5.3.3 Alarm reporting + +The secondary device reports every change in error status after subscription for alarm reporting by transmitting alarm messages to the primary device. Alarm information can also be interrogated in the application layer. + +### 5.3.4 Operator specific data storage + +The secondary device provides means for storage of operator specific data, e.g. inventory information. + +### 5.3.5 Control of Tower Mounted Amplifiers (TMAs) + +The TMA device provides means to indicate alarms and optionally to adjust the gain of TMAs. The set of procedures to control TMAs are defined in TS 37.466 [7]. + +# 6 Other Iuant interface specifications + +## 6.1 Iuant interface: Layer 1 (TS 37.461) + +TS 37.461 [2] specifies the standards allowed for implementation of Layer 1 (physical layer) on the Iuant interface. + +## 6.2 Iuant interface: Signalling Transport (TS 37.462) + +TS 37.462 [3] specifies the signalling transport related to RETAP and TMAAP signalling to be used across the Iuant interface. + +## 6.3 Void + +## 6.4 Summary of Iuant interface Technical Specifications + +The relationship between the technical specifications that define the Iuant interface is shown in figure 6.4.1. + +![Diagram showing the relationship between technical specifications for the Iuant interface layers.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) + +The diagram illustrates the relationship between technical specifications for the Iuant interface across three layers. On the left, the layers are labeled: 'Radio Network Layer', 'Transport Layer', and 'Physical Layer'. To the right of each label is a box containing the corresponding specification. The 'Radio Network Layer' box contains 'RETAP TMAAP' and 'TS 37.466'. The 'Transport Layer' box contains 'Iuant Transport' and 'TS 37.462'. The 'Physical Layer' box contains 'TS 37.461'. A dashed vertical line runs through the center of all three boxes, indicating a common interface or relationship between the specifications. + +Diagram showing the relationship between technical specifications for the Iuant interface layers. + +Figure 6.4.1: Iuant Interface Technical Specifications + +## 6.5 Iuant interface: Application part specification (TS 37.466) + +TS 37.466 [7] specifies protocols for application part to be used over the Iuant interface. + +# Annex A (informative): OSI model overview + +![Diagram of the OSI model showing three layers (7 Application, 2 Data Link, 1 Physical) for two devices. Solid arrows represent the actual message path through the physical layer, while dashed arrows represent the apparent message path between corresponding layers of the two devices.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +The diagram illustrates the OSI model layers for two communicating devices. Each device has three layers: 7 Application, 2 Data Link, and 1 Physical. Within each device, arrows show data moving down from the Application layer to the Data Link layer, and then down to the Physical layer. Conversely, arrows show data moving up from the Physical layer to the Data Link layer, and then up to the Application layer. Between the two devices, a solid horizontal arrow connects the 1 Physical layer of the first device to the 1 Physical layer of the second device, representing the actual message path. Dashed horizontal arrows connect the 7 Application layer of the first device to the 7 Application layer of the second device, and the 2 Data Link layer of the first device to the 2 Data Link layer of the second device, representing apparent message paths. A legend at the bottom indicates that a solid arrow represents the 'Actual message path' and a dashed arrow represents the 'Apparent message path'. + +Diagram of the OSI model showing three layers (7 Application, 2 Data Link, 1 Physical) for two devices. Solid arrows represent the actual message path through the physical layer, while dashed arrows represent the apparent message path between corresponding layers of the two devices. + +**Figure A.1: Relevant OSI model layers** + +Figure A.1 shows the relevant OSI model layers and the communication paths between the primary and secondary device. + +The two important aspects of the OSI model are: + +- It defines a layered structure for the communication software; +- It provides each layer with an apparent direct link to the same layer at the other device. + +However, in real life, the only actual message path between the two devices is through the physical connection between the two layer 1 entities. + +The layer 2 entities appear to communicate directly. In actual fact, a message passed from the first device to the second device takes the following path: + +- Layer 2 at the first device passes the message down to Layer 1; +- Layer 1 transmits the message across the physical connection (for instance a wire) to layer 1 at the second device; +- Layer 1 at the second device passes the message up to Layer 2 at the second device. + +Likewise, layer 7 entities appear to communicate directly. In actual fact, a message passed from the first device to the second device takes the following path: + +- Layer 7 at the first device passes the message down to Layer 2; +- Layer 2 at the first device passes the message down to Layer 1; +- Layer 1 transmits the message across the physical connection (for instance a wire) to layer 1 at the second device; +- Layer 1 at the second device passes the message up to Layer 2 at the second device; +- Layer 2 at the second device passes the message up to Layer 7 at the second device. + +## Annex B (informative): Change History + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-02 | R3-103 | R3-190079 | | | | Text transferred from 25.460 v15.0.0 (changes shown with rev marks) | 1.15.0 | +| 2019-04 | RAN#83 | RP-190582 | | | | Specification approved by RAN plenary | 15.1.0 | +| 2019-12 | RP-86 | RP-192915 | 0001 | 5 | F | Correction for luant | 15.2.0 | +| 2020-07 | RAN#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-03 | RAN#95-e | RP-220238 | 0002 | 1 | D | Inclusive language review | 17.0.0 | +| 2024-03 | RAN#103 | RP-240617 | 0004 | - | D | Rapporteur Editorial Review | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37461/raw.md b/marked/Rel-18/37_series/37461/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..36d36c8a830759f0e2c877c9fa9751944e940a5c --- /dev/null +++ b/marked/Rel-18/37_series/37461/raw.md @@ -0,0 +1,492 @@ + + +# 3GPP TS 37.461 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Iuant interface: Layer 1 (Release 18)** + +![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G ADVANCED logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## --- **Keywords** + +radio, EMC, power supply, antenna + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|---------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 Iuant layer 1 ..... | 6 | +| 4.1 General ..... | 6 | +| 4.2 RS485 option..... | 7 | +| 4.3 Modem option ..... | 7 | +| 4.3.1 Interference with existing systems ..... | 9 | +| 4.3.1.1 Carrier frequency and frequency stability ..... | 9 | +| 4.3.1.2 Modem isolation and modem emissions..... | 9 | +| 4.3.1.3 Modem intermodulation attenuation..... | 10 | +| 4.3.2 Recovery time..... | 10 | +| 4.3.3 Impedance..... | 10 | +| 4.3.4 Modulator characteristics ..... | 11 | +| 4.3.4.1 Levels..... | 11 | +| 4.3.4.2 Spectrum emission mask ..... | 11 | +| 4.3.5 Demodulator characteristics ..... | 11 | +| 4.3.6 Duty cycle variation ..... | 11 | +| 4.3.7 Operating bands..... | 12 | +| 4.3.8 Time delay and accuracy ..... | 12 | +| 4.3.9 Insertion Loss ..... | 12 | +| 4.3.10 DC port isolation ..... | 13 | +| 4.3.11 RET control unit spurious emission ..... | 13 | +| 4.3.12 Control unit spurious emission..... | 13 | +| 4.4 DC power supply..... | 14 | +| 4.4.1 Power consumption ..... | 14 | +| 4.4.2 Conducted emission..... | 14 | +| 4.4.3 Power-up characteristics..... | 14 | +| Annex A (normative): Test procedures ..... | 16 | +| Annex B (informative): Change history..... | 17 | + +# --- 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 standards allowed to implement layer 1 on the Iuant interface for UTRA, E-UTRA and NR. + +The specification of transmission delay requirements and O&M requirements are not in the scope of the present document. + +The modem option of Iuant layer 1 specification in clause 4.3 applies to UTRA, E-UTRA BS and NR BS type 1-C. + +# --- 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 37.462: "UTRAN Iuant interface: Signalling transport". +- [2] ISO/IEC 8482 (1993-12): "Information technology - Telecommunications and information exchange between systems - Twisted pair multipoint interconnections". +- [3] TIA/EIA TSB89: "Application guidelines for TIA/EIA-485-A". +- [4] 3GPP TS 25.101: "Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD)". +- [5] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [6] 3GPP TS 38.101: "NR; User Equipment (UE) radio transmission and reception (FDD)". +- [7] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [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 [7]. + +**On-Off-Keying:** A modulation system in which a carrier is switched between two states, ON and OFF. + +**Common feeder cable:** Feeder cable where some antenna line devices (e.g. RET, TMA) are connected via the same feeder cable. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|--------------------------------------------| +| BS | Base Station | +| DC | Direct Current | +| DL | Downlink | +| FDD | Frequency Division Duplex | +| ISB | Idle-State Biasing | +| OOK | On-Off-Keying | +| RET | Remote Electrical Tilting | +| RF | Radio Frequency | +| TMA | Tower Mounted Amplifier | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunications System | +| UTRA | UMTS Terrestrial Radio Access | + +# --- 4 Iuant layer 1 + +## 4.1 General + +There are two layer 1 options: + +- RS485 option: A screened multicore cable, which supports a conventional RS485 serial multi-drop bus. +- Modem option: A connection to a RET and/or a TMA control unit by way of a coaxial cable which is shared with DC supply and RF signals. + +Both layer 1 options support the connection of two-way serial data and DC power to the RET and/or TMA antenna device. + +At least one of these two layer 1 options shall be supported. + +The default data rate for both layer 1 options shall be 9.6 kbps. Higher data rates of 38.4 kbps for both layer 1 options and 115.2 kbps only for the RS485 layer 1 option may optionally be supported. Each unit communicates on one of the three data rates, but different units on the same interface may use different data rates. + +After a reset, a secondary device shall alternate between supported data rates. When alternating between data rates, the data rate shall be held constant for 300 ms. After every correctly received device scan command (see TS 37.462 [1]) independent of whether it matches or not, at one of the supported data rates, that data rate shall be held constant for 1.5 seconds. After successful reception of an address assignment frame, the secondary device shall use that data rate until it is reset. + +Data rates: + +- 9.6 kbps $\pm$ 3 % +- 38.4 kbps $\pm$ 3 % +- 115.2 kbps $\pm$ 3 % + +The format of the data octet shall be as shown in figure 4.1.1: + +![Figure 4.1.1: Format and order of transmitted data. The diagram shows a voltage level (Vb-Va) on the vertical axis and Time on the horizontal axis. The signal starts at an 'Idle' state (Logical 1, Carrier Off). It then transitions to a 'Startbit (0)' (Logical 0, Carrier On). This is followed by a sequence of bits, with the 'Least significant bit' at the beginning and the 'Most significant bit' at the end. The sequence ends with a 'Stop bit (1)' (Logical 1, Carrier Off), returning to the 'Idle' state.](a6a8016b231533e7f34b550f4676afc6_img.jpg) + +The figure illustrates the signal format for transmitted data. The vertical axis represents the voltage difference $V_b - V_a$ , with two levels marked: 'Logical 1 Carrier Off' (higher level) and 'Logical 0 Carrier On' (lower level). The horizontal axis represents 'Time'. The signal begins at the 'Idle' state (Logical 1). It then drops to the 'Startbit (0)' (Logical 0). This is followed by a series of bits, with the 'Least significant bit' being the first bit after the start bit and the 'Most significant bit' being the last bit before the stop bit. The sequence concludes with a 'Stop bit (1)' (Logical 1), returning to the 'Idle' state. + +Figure 4.1.1: Format and order of transmitted data. The diagram shows a voltage level (Vb-Va) on the vertical axis and Time on the horizontal axis. The signal starts at an 'Idle' state (Logical 1, Carrier Off). It then transitions to a 'Startbit (0)' (Logical 0, Carrier On). This is followed by a sequence of bits, with the 'Least significant bit' at the beginning and the 'Most significant bit' at the end. The sequence ends with a 'Stop bit (1)' (Logical 1, Carrier Off), returning to the 'Idle' state. + +Figure 4.1.1: Format and order of transmitted data + +## 4.2 RS485 option + +This option is constituted by a two wire bi-directional multi-drop configuration conforming to ISO/IEC 8482 [2]. The mapping of mark/space to logical one and zero as referred to in ISO/IEC 8482 [2] shall be according to figure 4.1.1. + +The use of ISB, also called idle-line failsafe in TIA/EIA TSB89 [3], is mandatory. The bias voltages shall be applied only by the primary device to any separate RS485 bus. The polarity of the idle-state bias is defined as a transmitted 1. + +The RS485 transmitter shall be set to drive the bus before the first start bit is sent and held active until the last stop bit is sent. The RS485 transmitter shall stop driving the bus within 20 bit-times after the last stop bit is sent. + +If an antenna modem is used ISB shall be implemented by the antenna modem. + +## 4.3 Modem option + +The connection to a RET and/or a TMA control unit by way of a coaxial cable which is shared with DC supply and RF signals is provided by two modems, a BS modem and an antenna modem. The BS modem shall be either connected to the antenna connector of the BS or integrated in the BS. It provides signal transmission to the antenna modem and signal reception from the antenna modem over the antenna feeder cable. The antenna modem is located between the antenna feeder cable and the antenna. Modem configurations and reference points for modem characteristics are specified in figure 4.3.1 and figure 4.3.2. Unless otherwise stated, requirements in this section apply to both BS modem and antenna modem. + +![Diagram of modem configuration and reference points for a BS without BS modem. It shows an antenna connected to an Antenna modem, which is connected via an antenna feeder cable (labeled Iuant) to a BS modem, which is in turn connected to a BS without BS modem. Reference points 1 through 6 are marked at various interfaces.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the modem configuration and reference points for a Base Station (BS) without a BS modem. It consists of three main components connected vertically: an Antenna at the top, an Antenna modem, a BS modem, and a BS without BS modem at the bottom. The connections and reference points are as follows: + +- Antenna:** The top component, connected to the Antenna modem. +- Reference point 4:** Located at the interface between the Antenna and the Antenna modem. +- Antenna modem:** The second component from the top. It receives **Control data** and **DC power** from the left. **Reference point 5** is located on its left side. +- Reference point 3:** Located at the interface between the Antenna modem and the Antenna feeder cable. +- Iuant:** The label for the **Antenna feeder cable** connecting the Antenna modem and the BS modem. +- Reference point 2:** Located at the interface between the Antenna feeder cable and the BS modem. +- BS modem:** The third component from the top. It receives **Control data** and **DC power** from the left. **Reference point 6** is located on its left side. +- Reference point 1 (BS antenna connector):** Located at the interface between the BS modem and the BS without BS modem. +- BS without BS modem:** The bottom component. + +Diagram of modem configuration and reference points for a BS without BS modem. It shows an antenna connected to an Antenna modem, which is connected via an antenna feeder cable (labeled Iuant) to a BS modem, which is in turn connected to a BS without BS modem. Reference points 1 through 6 are marked at various interfaces. + +Reference point 6, DC power to the BS modem, is optional and does not exist if the BS modem has integrated power supply. + +Figure 4.3.1: Modem configuration and modem reference points for a BS without BS modem + +![Diagram of modem configuration and reference points for a BS with integrated BS modem. The diagram shows an antenna connected to an 'Antenna modem' box. The 'Antenna modem' is connected to a 'BS with integrated BS modem' box via an 'Antenna feeder cable'. Reference points are indicated: Reference point 4 is at the antenna input to the Antenna modem; Reference point 3 is at the output of the Antenna modem; Reference point 2 (BS antenna connector) is at the input of the BS with integrated BS modem; Reference point 5 is at the DC power input to the Antenna modem. Control data and DC power are shown entering the Antenna modem from the left. The Iuant is indicated on the Antenna feeder cable.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Diagram of modem configuration and reference points for a BS with integrated BS modem. The diagram shows an antenna connected to an 'Antenna modem' box. The 'Antenna modem' is connected to a 'BS with integrated BS modem' box via an 'Antenna feeder cable'. Reference points are indicated: Reference point 4 is at the antenna input to the Antenna modem; Reference point 3 is at the output of the Antenna modem; Reference point 2 (BS antenna connector) is at the input of the BS with integrated BS modem; Reference point 5 is at the DC power input to the Antenna modem. Control data and DC power are shown entering the Antenna modem from the left. The Iuant is indicated on the Antenna feeder cable. + +**Figure 4.3.2: Modem configuration and modem reference points for a BS with integrated BS modem** + +### 4.3.1 Interference with existing systems + +The modem circuit shall be capable of managing its transmitting characteristic according to subclause 4.3.5. + +#### 4.3.1.1 Carrier frequency and frequency stability + +The following carrier frequency shall be used for this application: + +$2.176 \text{ MHz} \pm 100 \text{ ppm}$ + +#### 4.3.1.2 Modem isolation and modem emissions + +The external BS modem shall provide minimum attenuation according to figure 4.3.1.2.1 between reference point 2 and reference point 1 to protect the BS from emissions of the antenna modem. + +External BS modem emissions at reference point 1 shall be attenuated at least according to the modem attenuation in figure 4.3.1.2.1 below the levels specified for the modem spectrum emission mask in subclause 4.3.4.2 to protect the BS from emissions of the BS modem. + +The antenna modem shall provide minimum attenuation according to figure 4.3.1.2.1 between reference point 3 and reference point 4 to protect other radio systems from emission of the BS modem. + +Antenna modem emissions at reference point 4 shall be attenuated at least according to the modem attenuation in figure 4.3.1.2.1 below the levels specified for the modem spectrum emission mask in subclause 4.3.4.2 to protect other radio systems from emission of the antenna modem. + +![Figure 4.3.1.2.1: Modem attenuation. A graph showing attenuation in dB versus frequency. The x-axis shows frequency points: 9 kHz, 1 MHz, 10 MHz, 20 MHz, and 30 MHz. The y-axis shows attenuation levels: 0 dB, 10 dB, 21 dB, 41 dB, and 42 dB. The curve starts at 10 dB from 9 kHz to 1 MHz, then rises steeply to 21 dB and 41 dB. It peaks at 42 dB at center frequency f0. It then descends symmetrically to 41 dB, 21 dB, and back to 10 dB at 10 MHz. It stays at 10 dB until 20 MHz, then drops to 0 dB at 30 MHz. Bandwidth markers show 400 kHz and 1 MHz centered at f0. A 200 kHz offset is indicated from f0 to the 21 dB point on the right side.](f519a5be118c846f631c992412353fb9_img.jpg) + +Figure 4.3.1.2.1: Modem attenuation. A graph showing attenuation in dB versus frequency. The x-axis shows frequency points: 9 kHz, 1 MHz, 10 MHz, 20 MHz, and 30 MHz. The y-axis shows attenuation levels: 0 dB, 10 dB, 21 dB, 41 dB, and 42 dB. The curve starts at 10 dB from 9 kHz to 1 MHz, then rises steeply to 21 dB and 41 dB. It peaks at 42 dB at center frequency f0. It then descends symmetrically to 41 dB, 21 dB, and back to 10 dB at 10 MHz. It stays at 10 dB until 20 MHz, then drops to 0 dB at 30 MHz. Bandwidth markers show 400 kHz and 1 MHz centered at f0. A 200 kHz offset is indicated from f0 to the 21 dB point on the right side. + +**Figure 4.3.1.2.1: Modem attenuation** + +#### 4.3.1.3 Modem intermodulation attenuation + +The modem intermodulation attenuation is specified in terms of the power in intermodulation products of WCDMA modulated carriers present at reference point 1 or reference point 3. + +For 2 downlink carriers of 43 dBm the power of third order intermodulation products in the UL operating bands for the external BS modem and antenna modem shall not exceed: + +- – 130 dBm/100 kHz for frequencies $< 1$ GHz +- – 120 dBm/1 MHz for frequencies $\geq 1$ GHz + +NOTE: Using the modem with higher power than 43 dBm and or with more carriers than 2 carriers at 43dBm/carrier may increase intermodulation products and may degrade the receiver sensitivity of the BS if these intermodulation products fall at BS receive frequencies. + +For the worst input configuration of power and number of carriers declared by the modem manufacturer the power of any intermodulation product for the external BS modem and antenna modem shall not exceed: + +- – 98dBm/100kHz + +In addition, for the worst input configuration of power and number of carriers declared by the modem manufacturer the power of fifth or higher order intermodulation products in the UL operating bands for the external BS modem and antenna modem shall not exceed: + +- – 135 dBm/100 kHz for frequencies $< 1$ GHz +- – 125 dBm/1 MHz for frequencies $\geq 1$ GHz + +### 4.3.2 Recovery time + +A minimum recovery time shall be allowed between receiving and transmitting messages on the bus. For this reason a minimum permitted response time is specified in subclause 4.5 in TS 37.462 [1]. + +### 4.3.3 Impedance + +The modem transceiver shall provide constant impedance in both transmitting and receiving modes: + +- Nominal impedance $Z_0$ : 50 $\Omega$ ; +- Return loss at modem carrier frequency $\pm 0.1$ MHz $> 10$ dB; +- Return loss in external BS and antenna modem operating bands $> 20$ dB. + +### 4.3.4 Modulator characteristics + +#### 4.3.4.1 Levels + +ON-Level: $+3 \text{ dBm} \pm 2 \text{ dB}$ + +OFF-Level: $\leq -40 \text{ dBm}$ + +#### 4.3.4.2 Spectrum emission mask + +The modem spectrum emission mask is specified in figure 4.3.4.2.1. Intermediate values may be obtained by linear interpolation between the points shown. The corresponding measurement bandwidths are specified in table 4.3.4.2.1. For modem configurations according to figure 4.3.1 the BS modem emissions shall not exceed the limits of the spectrum emission mask at reference point 2. For modem configurations according to figure 4.3.2 the BS with integrated BS modem emissions shall not exceed the limits of the spectrum emission mask at reference point 2 only for frequencies below 20 MHz. Antenna modem emissions shall not exceed the limits of the spectrum emission mask at reference point 3. + +![Figure 4.3.4.2.1: Modem spectrum emission mask. The graph shows power density in dBm versus frequency. The x-axis is logarithmic, with markers at 9 kHz, 1 MHz, 10 MHz, 20 MHz, 30 MHz, 400 MHz, and 12.75 GHz. The y-axis is linear in dBm. The mask starts at -36 dBm from 9 kHz to 1 MHz. At 1 MHz, it rises to -25 dBm at 200 kHz offset from the carrier f0. At f0, it rises to +5 dBm. At 400 kHz offset from f0, it drops to -25 dBm. At 1 MHz offset from f0, it drops to -36 dBm. From 10 MHz to 30 MHz, it is -36 dBm. At 30 MHz, it drops to -67 dBm. From 400 MHz to 12.75 GHz, it is -67 dBm. A 'Note 1' is indicated for frequencies above 1 GHz.](1640ec1dfae8bdfa5af950db7623febc_img.jpg) + +Figure 4.3.4.2.1: Modem spectrum emission mask. The graph shows power density in dBm versus frequency. The x-axis is logarithmic, with markers at 9 kHz, 1 MHz, 10 MHz, 20 MHz, 30 MHz, 400 MHz, and 12.75 GHz. The y-axis is linear in dBm. The mask starts at -36 dBm from 9 kHz to 1 MHz. At 1 MHz, it rises to -25 dBm at 200 kHz offset from the carrier f0. At f0, it rises to +5 dBm. At 400 kHz offset from f0, it drops to -25 dBm. At 1 MHz offset from f0, it drops to -36 dBm. From 10 MHz to 30 MHz, it is -36 dBm. At 30 MHz, it drops to -67 dBm. From 400 MHz to 12.75 GHz, it is -67 dBm. A 'Note 1' is indicated for frequencies above 1 GHz. + +Figure 4.3.4.2.1: Modem spectrum emission mask. + +Note 1: For frequencies $< 1 \text{ GHz}$ the general emission limit is $-108 \text{ dBm}$ , except modem operating band UL frequencies where the emission limit is $-135 \text{ dBm}$ . +For frequencies $\geq 1 \text{ GHz}$ the general emission limit is $-98 \text{ dBm}$ , except modem operating band UL frequencies where the emission limit is $-125 \text{ dBm}$ . + +Table 4.3.4.2.1: Modem spectrum emission mask measurement bandwidth + +| Band | Measurement Bandwidth | +|-------------------|-----------------------| +| 9 kHz - 150 kHz | 1 kHz | +| 150 kHz - 30 MHz | 10 kHz | +| 30 MHz - 1 GHz | 100 kHz | +| 1 GHz - 12.75 GHz | 1 MHz | + +### 4.3.5 Demodulator characteristics + +The demodulator shall fulfil the requirement in subclause 4.3.6 for a carrier ON-Level within $+5 \text{ dBm}$ to $-12 \text{ dBm}$ and a carrier OFF-Level less than $-18 \text{ dBm}$ . The levels within $-12 \text{ dBm}$ to $-18 \text{ dBm}$ are undefined. + +### 4.3.6 Duty cycle variation + +In order to guarantee proper transmission of data bits through the processes of modulation and demodulation, the following limit shall be met for the duty cycle variation: + +$$\Delta DC_{\text{SYSTEM}} = |DC_{\text{RX}} - DC_{\text{TX}}| \leq 10 \%$$ + +Where: $\Delta DC_{SYSTEM}$ is the difference between the duty cycles of the transmitted and received bit streams, + $DC_{TX}$ = Duty cycle for the input bit stream, and + $DC_{RX}$ = Duty cycle for the output bit stream. + +![Figure 4.3.6.1: Duty cycles of the bit stream and OOK modulated subcarrier. The figure shows two waveforms. The top waveform is a bit stream with '1' and '0' levels, a 50% reference line, a bit period t_BS, and a cycle period T. The bottom waveform is an OOK modulated subcarrier with a 50% reference line, an on-period t_OOK, and a cycle period T.](252ea48d02dce93965b91746fb376f35_img.jpg) + +The figure consists of two vertically aligned waveforms. The top waveform represents a bit stream with two bits: a '1' followed by a '0'. The '1' bit is a high-level pulse, and the '0' bit is a low-level pulse. A horizontal dashed line at the center represents the 50% duty cycle reference. The duration of one bit is labeled $t_{BS}$ , and the duration of one full cycle (one '1' and one '0' bit) is labeled $T$ . The bottom waveform represents an OOK modulated subcarrier. It shows two cycles of a modulated signal. Each cycle consists of a period of high-frequency oscillation (the 'on' state) followed by a period of zero amplitude (the 'off' state). A horizontal dashed line at the center represents the 50% duty cycle reference. The duration of the 'on' state is labeled $t_{OOK}$ , and the duration of one full cycle is labeled $T$ . + +Figure 4.3.6.1: Duty cycles of the bit stream and OOK modulated subcarrier. The figure shows two waveforms. The top waveform is a bit stream with '1' and '0' levels, a 50% reference line, a bit period t\_BS, and a cycle period T. The bottom waveform is an OOK modulated subcarrier with a 50% reference line, an on-period t\_OOK, and a cycle period T. + +Duty cycle for bit stream = $t_{BS}/T$ ; duty cycle for OOK = $T_{OOK}/T$ + +**Figure 4.3.6.1: Duty cycles of the bit stream and OOK modulated subcarrier** + +For transmission through a coaxial cable, two converters are required, one from a bit stream to OOK (modulator) and one from OOK back to a bit stream (demodulator). Therefore half of the total duty cycle tolerance is available for each converter. + +For an input bit stream with a duty ratio of 50 %, the cascaded modulator and demodulator shall provide an output bit stream with a duty ratio within the limits 40 % - 60 %, measured in each case at 0.5 times peak amplitude (see figure 4.3.6.1). + +### 4.3.7 Operating bands + +A UTRA/FDD BS, UTRA/TDD BS, E-UTRA BS, NR BS or antenna modem is designed to operate in one or several of the operating bands defined in 3GPP TS 25.101 [4], 3GPP TS 36.101 [5] and 3GPP TS 38.101 [6]. + +**Table 4.3.7.1: Void** + +The operating bands of the BS modem or antenna modem shall be declared by the manufacturer. + +### 4.3.8 Time delay and accuracy + +The time delay in the operating bands shall be declared by the manufacturer with $\pm 1$ ns accuracy. The time delay shall not exceed 30 ns. This requirement is only applicable to external BS modem and antenna modem. + +### 4.3.9 Insertion Loss + +The insertion loss in the external BS modem or antenna modem operating band shall be $\leq 0.3$ dB. + +The actual insertion loss shall be declared by the manufacturer. + +### 4.3.10 DC port isolation + +The isolation between DC port and RF ports shall meet the minimum values in figure 4.3.10.1 and 4.3.10.2. Figure 4.3.10.1 is valid for antenna modems between reference point 5 and 4 as well as 5 and 3 and for BS modems without integrated power supply between reference point 6 and 2 as well as 6 and 1. Figure 4.3.10.2 is valid as additional requirement for antenna modems between reference point 5 and 3 and for BS modems without integrated power supply between reference point 6 and 2. + +![Figure 4.3.10.1: DC port isolation graph showing isolation levels across a wide frequency range from 9 kHz to 3 GHz.](8b79f5ec940d107c246612c2a2ec519f_img.jpg) + +This graph shows the DC port isolation in dB across a frequency range from 9 kHz to 3 GHz. The isolation levels are defined in several segments: + + +- From 9 kHz to 150 kHz: 10 dB +- From 150 kHz to 1 MHz: 16 dB +- From 1 MHz to 30 MHz: 16 dB (Note 3 applies here) +- From 30 MHz to 400 MHz: 21 dB +- From 400 MHz to 1 GHz: 38 dB (Note 1 applies here) +- From 1 GHz to 2.57 GHz: 38 dB (Note 2 applies here) +- From 2.57 GHz to 3 GHz: 20 dB + +Figure 4.3.10.1: DC port isolation graph showing isolation levels across a wide frequency range from 9 kHz to 3 GHz. + +Note 1: 38 dB, except for UL and DL operating bands where it is 65 dB + +Note 2: 38 dB, except for UL and DL operating bands where it is 65 dB + +Note 3: 16 dB. Between reference point 5 and 3 as well as 6 and 2 see figure 4.3.10.2. + +Figure 4.3.10.1: DC port isolation + +![Figure 4.3.10.2: DC port isolation graph showing a detailed view of the isolation around the carrier frequency f0.](3084f66c81a49b6225666f212179642c_img.jpg) + +This graph provides a detailed view of the DC port isolation around the carrier frequency $f_0$ . The isolation levels are: + + +- Outside the 1 MHz band (e.g., at 10 MHz, 20 MHz, 30 MHz): 16 dB +- At the edges of the 1 MHz band (1 MHz and 10 MHz): 35 dB +- At the carrier frequency $f_0$ : 36 dB +- At a distance of 200 kHz from $f_0$ : 35 dB +- At a distance of 400 kHz from $f_0$ : 36 dB + +Figure 4.3.10.2: DC port isolation graph showing a detailed view of the isolation around the carrier frequency f0. + +Figure 4.3.10.2: DC port isolation + +### 4.3.11 RET control unit spurious emission + +Void. + +### 4.3.12 Control unit spurious emission + +The control unit, or a combination of control units, shall not generate spurious emission, at reference point 5, above a level that will violate the spectrum emission mask requirement according to chapter 4.3.4.2. The DC port isolation according to chapter 4.3.10 shall be taken into account. + +## 4.4 DC power supply + +### 4.4.1 Power consumption + +The DC supply requirements refers to reference points 3 and 5 in subclause 4.3. + +BS modem and an antenna modem shall be able to operate with a DC supply voltage range of 10 V – 30 V. + +Power consumption modes are specified in table 4.4.1.1. and table 4.4.1.2. + +**Table 4.4.1.1: Power consumption modes for RET** + +| RET Power mode | Maximum power consumption | +|----------------|---------------------------| +| High | < 13 W | +| Low | < 2 W | + +**Table 4.4.1.2: Power consumption modes for TMA** + +| TMA Type | Maximum power consumption | +|----------------|---------------------------| +| Single Unit | < 7,5 W | +| Multi Unit (N) | < N * 7,5 W | + +BS modem and antenna modem maximum power consumption shall be < 2 W. + +BS modem and antenna modem shall impose a voltage drop less than 2 V between reference point 3 and 5. + +A Single Unit considers one RF amplifier in one TMA. A Multi Unit considers N RF amplifiers in equal or less than N TMAs. + +### 4.4.2 Conducted emission + +The levels of generated conducted noise and ripple on DC Power supply shall be within the limits given in table 4.4.2.1. + +**Table 4.4.2.1: Noise and ripple** + +| Item | Limit | Frequency | Remarks | +|------------------------|---------------------|---------------|-----------------------------------------------------------| +| RET power mode High | 70 mV pp | 0.15 - 30 MHz | Only one operating unit a time | +| RET power mode Low | 20 mV pp | 0.15 - 30 MHz | | +| TMA | 20 mV pp | 0.15 - 30 MHz | | +| Antenna modem, RF port | 15 mV pp | 0.15 - 30 MHz | Generated Noise and Ripple at RF feeder (in RX mode) | +| Antenna modem, DC port | 20 mV pp | 0.15 - 30 MHz | Allowed Noise and Ripple at external DC port (in TX mode) | + +All units connected to a DC supply bus shall exhibit full performance up to the limit of 112 mVpp total noise and ripple within 0.15 - 30 MHz. + +### 4.4.3 Power-up characteristics + +A BS modem, antenna modem or RET/TMA control units shall have a power-up period of 3 s. + +During the power-up period a BS modem, antenna modem or a RET control unit shall exhibit the circuit equivalent of a DC power consumer with a current consumption of maximum 400 mA in parallel with a capacitor of maximum 0.5 µF. + +During the power-up period the TMA control unit shall exhibit the circuit equivalent of a DC power consumer with a current consumption of maximum 1A in parallel with a capacitor of maximum 0.5 µF. + +After the power-up period, the unit shall be fully functional and the power consumption requirement as described in subclause 4.4.1 applies. + +# --- Annex A (normative): Test procedures + +## Test pattern + +Spectrum mask and emission requirement shall be tested both with a consecutive series of "0" and an alternating sequence of "0" and "1". + +## Emission requirement below noise floor + +As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy and sensitivity when measuring close to or below the noise floor, the resolution bandwidth may 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. + +## Conversion between modulated and CW for IM measurement + +The requirement for IM3 below 1 GHz shall be relaxed 15 dB and tested with CW interferers at the specified levels. +The requirement for IM3 above 1 GHz shall be relaxed 5 dB and tested with CW interferers at the specified levels. + +The requirement for IM5 or higher below 1 GHz shall be relaxed 10 dB and tested with CW interferers at the specified levels. + +The requirement for IM5 or higher above 1 GHz shall be relaxed 0 dB and tested with CW interferers at the specified levels. + +Example: A –130 dBm/100 kHz requirement below 1 GHz with two WCDMA-modulated carriers at 43 dBm is converted to a –115 dBm requirement with two CW carriers at 43 dBm. \ No newline at end of file diff --git a/marked/Rel-18/37_series/37462/raw.md b/marked/Rel-18/37_series/37462/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a0c2c8fa4a3c95bdced51ed013e49e03f6d9c168 --- /dev/null +++ b/marked/Rel-18/37_series/37462/raw.md @@ -0,0 +1,714 @@ + + +# 3GPP TS 37.462 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Iuant interface: Signalling transport (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +## --- **Keywords** + +radio, antenna + +### **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 Iuant data link layer..... | 6 | +| 4.1 Invalid receptions ..... | 6 | +| 4.2 Frame lengths ..... | 6 | +| 4.3 Default address..... | 7 | +| 4.4 Window size..... | 7 | +| 4.5 Message timing ..... | 7 | +| 4.6 State model..... | 7 | +| 4.7 Device types ..... | 7 | +| 4.8 XID negotiation..... | 8 | +| 4.8.1 HDLC parameters..... | 8 | +| 4.8.2 Protocol version..... | 8 | +| 4.8.3 Address assignment..... | 8 | +| 4.8.4 Device scan..... | 9 | +| 4.8.5 Reset device..... | 9 | +| 4.9 Link establishment ..... | 10 | +| 4.10 Link timeout ..... | 10 | +| Annex A (informative): HDLC description ..... | 11 | +| A.1 Basic structure ..... | 11 | +| A.2 UNC commands..... | 12 | +| A.2.1 Set Normal Response Mode (SNRM) ..... | 12 | +| A.2.2 Disconnect (DISC) ..... | 12 | +| A.2.3 Unnumbered Acknowledge (UA)..... | 12 | +| A.2.4 Disconnected Mode (DM)..... | 12 | +| A.2.5 Receiver Ready (RR)..... | 12 | +| A.2.6 Receiver Not Ready (RNR)..... | 12 | +| A.2.7 Information (I) ..... | 12 | +| A.2.8 Frame Reject (FRMR)..... | 12 | +| A.3 Option 1..... | 13 | +| A.4 Option 4..... | 13 | +| A.5 Option 15.1 ..... | 13 | +| A.6 Link safety..... | 13 | +| A.7 Full duplex link ..... | 13 | +| Annex B (informative): HDLC parameter negotiation ..... | 15 | +| Annex C (informative): HDLC parameter negotiation example ..... | 16 | +| Annex D (informative): Address assignment example..... | 17 | +| D.1 Address assignment command ..... | 17 | +| D.2 Address assignment response ..... | 17 | +| Annex E (informative): Device scan example..... | 18 | +| Annex F (informative): Change History..... | 20 | + +# --- 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 signalling transport related to RETAP and TMAAP signalling to be used across the Iuant interface for UTRAN, E-UTRAN and NG-RAN. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". The logical Iuant interface is an interface internal to the RAN Node and defined to reside between the implementation specific O&M function and the RET antennas and between the implementation specific O&M function and the TMA control unit function. + +# --- 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] ISO/IEC 13239 (3rd Edition, 2002-07): "Information Technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures". +- [3] 3GPP TS 37.461: "Iuant Interface: Layer 1". +- [4] Antenna Interface Standards Group: "Control Interface for Antenna Line Devices", Standard No. AISG v2.0. +- [5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [5]. + +**ASCII character:** A character forming part of the International Reference Version of the 7-bit character set defined in ISO/IEC 646:1991 represented as one octet. + +**Octet:** 8 bits as used in ISO/IEC 13239 [2]. + +**Device type:** One octet identifying the type of a device. + +**Unique ID:** A concatenation of the vendor code (2 octets) and a 1 to 17 octets long unit specific code (e.g. serial number) exclusive for each secondary device from the vendor to whom the vendor code is assigned. The vendor code is placed in the left-most (most significant) position of the unique ID. The vendor to whom the vendor code is assigned is responsible for ensuring the uniqueness of the unique ID for each device. + +**Vendor code:** A unique ASCII 2-character code assigned to each vendor in AISG v2.0 [4]. + +**Reset:** A process by which the device is put in the state it reaches after a completed power-up. + +**SecondaryPayloadTransmitLength:** The maximum length of the INFO field of an HDLC I-frame in the direction secondary device to primary device. + +**SecondaryPayloadReceiveLength:** The maximum length of the INFO field of an HDLC I-frame in the direction primary device to secondary device. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [5] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [5]. + +| | | +|-------|-------------------------------------------------| +| ADDR | Address | +| ACK | Acknowledgment | +| CRC | Cyclic Redundancy Check | +| DISC | Disconnect (frame type) | +| DM | Disconnected Mode (frame type) | +| FCS | Frame Checking Sequence | +| FI | Format Identifier | +| FRMR | Frame Reject (frame type) | +| GI | Group Identifier | +| GL | Group Length | +| HDLC | High-Level Data Link Control | +| I | Information (frame type) | +| ID | Identifier | +| INFO | Information (field name) | +| NAK | Non Acknowledgment | +| NRM | Normal Response Mode | +| P/F | Poll/Final | +| PI | Parameter Identifier | +| PL | Parameter Length | +| PV | Parameter Value | +| RET | Remote Electrical Tilting | +| RETAP | Remote Electrical Tilting Application Part | +| RNR | Receive Not Ready (frame type) | +| RR | Receive Ready (frame type) | +| SNRM | Set Normal Response Mode (frame type) | +| TMA | Tower Mounted Amplifier | +| TMAAP | Tower Mounted Amplifier Application Part | +| TWA | Two Way Alternate | +| UA | Unnumbered Acknowledgement (frame type) | +| UNC | Unbalanced Operation Normal Response Mode Class | +| XID | Exchange ID (frame type) | + +# 4 Iuant data link layer + +The Data Link Layer uses HDLC Class UNC1,15.1 TWA (see 6.10 in ISO/IEC 13239 [2]) according to ISO/IEC 13239 [2]. + +## 4.1 Invalid receptions + +Frames shall be discarded if a framing error or data overrun occurs. + +## 4.2 Frame lengths + +HDLC frame lengths may vary between 4 and N octets. + +All secondary devices shall support an N of 78 octets. A secondary device may, after XID negotiation, support a larger N. + +## 4.3 Default address + +After reset, a secondary device shall use the no-device address (0x00). While it has the no-device address, it may only respond to device scan and address assignment messages, but any broadcast messages shall be evaluated without response. + +## 4.4 Window size + +All devices shall support a window size of 1. A device may, after XID negotiation, support any window size up to 7. + +## 4.5 Message timing + +A minimum of 3 ms shall elapse between receiving and transmitting messages. + +A secondary device shall, after reception of a command with the P/F bit set, start transmitting a response within 10 ms from the time the final flag octet of that command frame was received. + +The transmission of the response shall be finalised within the time $t = n \cdot 10 \cdot 10^{-4} / \text{datarate}$ where n is the number of octets in the response frame including all HDLC framing overhead. The maximum gap time between two consecutive octets shall not exceed the time $t = 3 \cdot 10^{-4} / \text{datarate}$ . This corresponds to a 25% utilisation of the Data Link Layer. + +The data rate is specified in TS 37.461 [3]. + +## 4.6 State model + +The connection state model for the layer 2 of the secondary device is shown in figure 4.1. The events written in *italic* are procedures from higher levels e.g. link establishment. The HDLC frames that correspond to the events are written in bold as **command / response** messages. + +![Figure 4.6.1: Connection state model diagram showing three states: NoAddress, AddressAssigned, and Connected. Transitions are triggered by events (italic) and HDLC frames (bold).](06da11ab76cacc38bbcd714e437797ea_img.jpg) + +``` + +stateDiagram-v2 + [*] --> NoAddress : Reset (reset, power on, watchdog etc.) + NoAddress --> AddressAssigned : Address Configuration + AddressAssigned --> NoAddress : XID/XID + NoAddress --> Connected : DISC/UA + Connected --> NoAddress : Link Disconnection + Connected --> AddressAssigned : SNRM/UA, Link Establishment + +``` + +The diagram illustrates the connection state model for a secondary device. It consists of three states: **NoAddress**, **AddressAssigned**, and **Connected**. Transitions between states are triggered by specific events (shown in *italic*) and HDLC frames (shown in **bold**). + +- NoAddress** to **AddressAssigned**: Triggered by *Address Configuration* (event) and **XID/XID** (HDLC frame). +- AddressAssigned** to **NoAddress**: Triggered by **XID/XID** (HDLC frame). +- NoAddress** to **Connected**: Triggered by **DISC/UA** (HDLC frame). +- Connected** to **NoAddress**: Triggered by *Link Disconnection* (event) and **DISC/UA** (HDLC frame). +- Connected** to **AddressAssigned**: Triggered by **SNRM/UA** (HDLC frame) and *Link Establishment* (event). +- Initial state: **NoAddress** is reached upon **Reset (reset, power on, watchdog etc.)** (event). + +Figure 4.6.1: Connection state model diagram showing three states: NoAddress, AddressAssigned, and Connected. Transitions are triggered by events (italic) and HDLC frames (bold). + +Figure 4.6.1: Connection state model + +## 4.7 Device types + +Three device types are defined and identified by the assigned 1-octet unsigned integer code. + +**Table 4.7.1: Device types and codes** + +| Device Type | 1-octet unsigned integer code | +|-------------------------------|--------------------------------------| +| Single-Antenna RET Device | 0x01 | +| Multi-Antenna RET Device | 0x11 | +| Tower mounted amplifier (TMA) | 0x02 | + +## 4.8 XID negotiation + +XID negotiation shall use the standard format (see 5.5.3.1-5.5.3.2.3.2 in ISO/IEC 13239 [2]). See Annex B for a brief description of XID negotiation and Annex C to E for examples of XID negotiations. All GL fields have a size of 1 octet. + +Any parameter combination of 4.8.1 (HDLC parameter), 4.8.2 (Protocol Version) and 4.8.3 (Address assignment) in an XID command shall be supported by all secondary devices. + +### 4.8.1 HDLC parameters + +Format Identifier (FI) shall be 0x81 and Group Identifier (GI) shall be 0x80. All secondary devices shall support the following parameters: + +**Table 4.8.1.1: HDLC parameters for secondary devices** + +| PI | PL | Description of PV | +|-----------|-----------|----------------------------------------------------| +| 5 | 4 | Maximum information field length – transmit (bits) | +| 6 | 4 | Maximum information field length – receive (bits) | +| 7 | 1 | Window size – transmit (frames) | +| 8 | 1 | Window size – receive (frames) | + +The SecondaryPayloadTransmitLength shall be 74 octets by default. It can be increased via XID negotiation, but shall always be 74 octets or larger. + +The SecondaryPayloadReceiveLength shall be 74 octets by default. It can be increased via XID negotiation, but shall always be 74 octets or larger. + +### 4.8.2 Protocol version + +Format Identifier (FI) shall be 0x81 and Group Identifier (GI) shall be 0xF0. All secondary devices shall support the following parameter: + +**Table 4.8.2.1: HDLC parameter for protocol version** + +| PI | PL | Description of PV | +|-----------|-----------|--------------------------| +| 5 | 1 | 3GPP Release ID | + +### 4.8.3 Address assignment + +The primary device broadcasts the XID commands. The secondary device(s) which match shall respond. The primary shall ensure that only one secondary matches the supplied parameter(s). See below for details. + +Format Identifier (FI) shall be 0x81 and Group Identifier (GI) shall be 0xF0. All secondary devices shall support the following parameters: + +**Table 4.8.3.1: HDLC parameters for address assignment and device scan** + +| PI | PL | Description of PV | +|----|---------|---------------------------------------------------| +| 1 | 0 to 19 | Unique ID | +| 2 | 1 | HDLC Address | +| 3 | 0 to 19 | Bit Mask (for Unique ID), indicates a device scan | +| 4 | 1 | Device Type (see table 4.7.1) | +| 6 | 2 | Vendor Code as given in AISG v2.0 [4] | + +The XID message can be used to assign HDLC addresses or to scan for devices. + +An address assignment XID command shall contain at least PI=2 (HDLC Address) and shall not contain PI=3 (Bit Mask). During an address assignment all secondary devices first assume a match and then carry out the following steps: + +- If PI=1 (Unique ID) is supplied, the right-most PL octets of the secondary devices Unique ID are compared to the Unique ID in the XID command. If they are different, the secondary device does not match, and the message is ignored. If the Unique ID in the XID command is longer than the secondary devices Unique ID, the secondary device does not match, and the message is ignored. +- If PI=4 (Device Type) is supplied, the device type of the secondary device is compared to the device type in the XID command. If they are different, the secondary device does not match, and the message is ignored. +- If PI=6 (Vendor Code) is supplied, the vendor code of the secondary device is compared to the vendor code in the XID command. If they are different, the secondary device does not match, and the message is ignored. + +If the secondary device still matches after these steps, the secondary device sets its HDLC address to the address specified in PI=2 and responds with an XID response which contains PI=1 and PI=4. + +NOTE: Unlike the normal XID negotiation, in this XID negotiation, the XID response message returns a different set of parameters than the XID command message. + +### 4.8.4 Device scan + +The device scan messages may be utilised by the primary to identify all secondary stations in the NoAddress state on an interface . + +A device scan XID command shall only contain PI=1 (Unique ID) and PI=3 (Bit Mask), see table 4.8.3.1. PI=1 and PI=3 shall be of equal length PL octets. + +If in the NoAddress state, the secondary device masks the $\min(PL,2)$ left-most octets of its own unique ID with the $\min(PL,2)$ left-most octets of the bit mask in the XID command and compares the result with the $\min(PL,2)$ left-most octets the unique ID supplied in the XID command. If they match, the secondary device masks the $\max(0,PL-2)$ right-most octets of its own unique ID with the $\max(0,PL-2)$ right-most octets of the bit mask in the XID command and compares the result with the $\max(0,PL-2)$ right-most octets of the unique ID supplied in the XID command. If they also match, the secondary device transmits an XID response message with its own identification data in the fields PI=1 (complete unique ID), PI=4 (device type) and PI=6 (vendor code). + +For the device scan comparison, the unique ID of the secondary device shall be padded with NUL characters (character code 0x00) between the second and third left-most positions to a length of 19 octets. + +The scan command with zero length (PL=0) of the Unique ID (PI=1) and the Bit Mask (PI=3) shall match all secondary devices in the NoAddress state. + +Only matching secondary devices in the NoAddress state shall respond to the device scan messages. + +### 4.8.5 Reset device + +Format identifier (FI) shall be 0x81 and group identifier (GI) shall be 0xF0. All secondary devices shall support the following parameter: + +**Table 4.8.5.1: HDLC parameters for reset of secondary devices** + +| PI | PL | Description of PV | +|----|----|-------------------| +| 7 | 0 | Reset device | + +If the XID command reset device is received as a broadcast (0xFF) by the secondary device, the secondary device shall reset without responding, otherwise the addressed secondary device shall reset after responding. + +The reset device parameter shall not be combined with other parameters in an XID command. + +NOTE: There is no PV in the XID command Reset device. + +## 4.9 Link establishment + +Once the secondary device has been assigned an HDLC address, the primary device initiates the link establishment by sending the SNRM command frame. The secondary device responds with an UA frame and enters the state *Connected*. + +## 4.10 Link timeout + +Whenever a secondary device receives an HDLC frame addressed to itself, i.e. not an all-device address (0xFF), it shall restart a 3 minute timer. If this 3 minute timer expires, the secondary device shall be reset. + +# Annex A (informative): HDLC description + +HDLC is defined in ISO/IEC 13239 [2]. This description only covers the aspects of HDLC which are used by this TS. + +The HDLC definition “UNC1,15.1, TWA” can be broken down to: + +- UNC; + - The “U” means Unbalanced operation; + - The “N” means Normal response mode (sequence numbers used in data frames); + - The “C” means Class. +- Options supported; + - “1” means use of XID negotiation; + - “15.1” means use of start/stop transmission with basic transparency; + - Two Way Alternate (TWA) is the HDLC term for half duplex. + +## A.1 Basic structure + +In unbalanced operation, there is one primary station which controls the bus and a number of secondary stations which only are allowed to transmit when the primary station gives them permission to do so. + +All messages are transmitted as frames with the layout shown in table A.1.1: + +**Table A.1.1: Format of an HDLC frame** + +| Flag
1 octet | ADDR
1 octet | Control
1 octet | INFO
N octets | FCS
2 octets | Flag
1 octet | +|-----------------|---------------------------|--------------------|------------------|-----------------|-----------------| +| 0x7E | Secondary Station Address | Control bits | Variable length | CRC | 0x7E | + +HDLC frames begin and end with a Flag (0x7E) (see A.5 for details). + +The transmitting station calculates a Frame Check Sequence (CRC16) on all octets which follow the starting flag but not including the FCS octets. The checksum is transmitted as FCS in little endian order and is followed by the closing flag. + +The receiving station calculates the checksum on all octets between the flags. When it finds the closing flag, it compares the checksum to 0xF0B8. If it is a match, the HDLC frame is processed. + +The address field contains the HDLC address of the secondary station. If the primary station sends the message, it is called a command and the address field contains the address of the secondary station as destination. If the secondary station sends the message, it is called a response and the address field contains the address of the secondary station as source. Secondary stations cannot communicate directly to each other. + +The control field defines one of three frame types: + +- I frames contain data as well as a send and receive counter; +- S frames contain a receive counter; +- U frames contain unnumbered commands. + +The INFO field is only present in I frames and XID frames. The INFO field in an I frame contains the layer 7 payload. + +## A.2 UNC commands + +According to 6.6.2.1 in ISO/IEC 13239 [2] the following commands in shall be supported in UNC mode: + +**Table A.2.1: Commands supported in UNC mode** + +| Commands
(Primary Station) | Responses
(Secondary Station) | +|-------------------------------|----------------------------------| +| Frame type I | Frame type I | +| Frame type RR | Frame type RR | +| Frame type RNR | Frame type RNR | +| Frame type SNRM | Frame type UA | +| Frame type DISC | Frame type DM | +| | Frame type FRMR | + +### A.2.1 Set Normal Response Mode (SNRM) + +This command is used to set the secondary station in connected mode and reset its sequence number variables. + +### A.2.2 Disconnect (DISC) + +This command is used to terminate the connection. + +### A.2.3 Unnumbered Acknowledge (UA) + +This response is used to confirm that the secondary station received and acted on an SNRM or DISC command. + +### A.2.4 Disconnected Mode (DM) + +This response is used to inform the primary station that the secondary station is disconnected. + +### A.2.5 Receiver Ready (RR) + +This command and response is used to inform the opposite station (primary or secondary) that the transmitting station has empty buffers, i.e. is ready to receive an I frame. This aspect is used for flow control. + +It also contains the sequence number of the next frame the transmitting station expects to see. This works both as an ACK and a NAK depending on the value. + +### A.2.6 Receiver Not Ready (RNR) + +Just like RR, except it informs the opposite station that the transmitting station does not have empty buffers, i.e. that it is not ready to receive an I frame. This aspect is used for flow control. + +### A.2.7 Information (I) + +This command and response is used to transfer a block of data together with its sequence number. The command also includes the sequence number of the next frame the transmitting station expects to see. This way, it works as an RR. Like RR, it enables transmission of I frames from the opposite side. + +### A.2.8 Frame Reject (FRMR) + +This response is used to indicate an error condition. The two most likely error conditions are: + +- Invalid command; +- Sequence number problem. + +The latter is used when the primary station has requested retransmission of a sequence number which it has already acknowledged. + +## A.3 Option 1 + +Option 1 means the addition of the XID command/response, which is used for parameter negotiation. + +## A.4 Option 4 + +Option 4 means the addition of the UI command/response, which is used to transfer information without changing the sequence numbers used by I frames. + +## A.5 Option 15.1 + +Option 15.1 means that the serial link is not synchronous and start/stop flags are used (asynchronous serial link). The flags are coded as 0x7E and basic transparency is used. + +This means that all octets between the flags are part of the frame and shall not be transmitted as 0x7E. Since the frame may contain 0x7E, basic transparency is used, which means that 0x7E is transmitted as 0x7D 0x5E and 0x7D is transmitted as 0x7D 0x5D. The receiving station converts back on reception. + +All checksum calculations are done on unconverted data. + +## A.6 Link safety + +HDLC provides the upper layer with a safe link between two stations. + +Unless excessive frame lengths are used, the CRC16 checksum provides excellent protection against transmission errors. At worst, $10^{-5}$ of the bit errors will not be detected. The likelihood of an undetected error in a frame can be calculated by multiplying $10^{-5}$ with the Bit Error Rate (at least $10^{-9}$ for a reasonable link) and the frame length. + +The sequence numbers provide protection against: + +- Message duplication; +- Message deletion; +- Message re-ordering. + +Without sequence numbers, the protection is only given by a checksum and some sort of ACK. + +If the original message is lost, there will be no ACK and a timeout will cause retransmission which solves the problem. + +If the original message is not lost, but the ACK is lost, the same timeout will cause a retransmission. + +With sequence numbers, the message is retransmitted, but the receiving station sees that the sequence number is the same, i.e. that the message is a retransmission, and throws it away without processing it further. It does send an ACK which informs the transmitting station that the message got through. + +## A.7 Full duplex link + +The upper layer sees the HDLC link as a full duplex link, although the actual transmissions on layer 1 are half duplex. The reason for this is that the upper layer is not aware of any restrictions on transmissions or receptions between layer 2 and layer 1 or between the stations. + +Whenever the upper layer wants to transmit, it places a message on the queue to layer 2. The message will not be transmitted until the primary station does a poll. + +NOTE: This applies to both the primary and the secondary station. + +The same applies to reception. The upper layer will either be told by layer 2 when a message has arrived, or it will periodically check to see if a message has arrived at layer 2. Neither of these two methods will in any way influence the reception of a message. That only depends on when the primary does a poll. + +NOTE This still applies to both the primary and the secondary station. + +A poll is a command frame from the primary station where the P/F (Poll/Final) bit in the control field is set to 1. This informs the secondary that it is allowed to transmit response frames. + +U frames set the P/F bit, which means that they are polls. However, since the U frames used in UNC 1,4 require a specific U frame response, they are not used for I frame transmission, which is what the upper layer messages depend upon. + +An I, RR or RNR frame type with the P/F bit set constitutes a poll as used above. An RNR frame prevents transmission of I frames, so it does not really apply. + +NOTE: Whenever an I or RR poll occurs, the secondary station may transmit whatever I frame it wishes (as long as the window size is not exceeded, i.e. previous messages have been acknowledged). This means that the secondary station does not have to transmit a reply to a layer 7 instruction. It is free to transmit an alarm instruction, if an alarm has occurred. It is also free to transmit any valid reply to an earlier layer 7 instruction, if it has received (acknowledged) more than one. + +# Annex B (informative): HDLC parameter negotiation + +See also sections 5.5.3.1 – 5.5.3.2.3.2 in ISO/IEC 13239 [2]. + +**Table B.1: Format of XID parameters** + +| | | | | | | | | | +|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------| +| FI | GI | GL | PI | PL | PV | PI | PL | PV | +|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------| + +XID parameter negotiation uses a specific format (see table C.1) to transfer parameters. + +The parameters are identified by a one octet Format Identifier (FI) code and a one octet Group Identifier (GI) code. The Group Length (GL) is a one octet unsigned integer giving the length in octets of the parameters following it. + +The parameters are a sequence of PI/PL/PV values. The Parameter Identifier (PI) is a one octet code identifying the parameter. Parameter Length (PL) is a one octet unsigned integer giving the length in octets of the Parameter Value. The parameter order is not defined. + +The HDLC parameter negotiation is initiated by the primary station. The primary station transmits an XID frame with the values it suggests. The secondary station can either accept these or lower them. Regardless, it responds with an XID frame with the appropriate values. + +Generally this means that the primary station initially uses whatever its maximum limit is for each parameter. If the secondary can accept this, it responds with the same values. If it cannot support that, it lowers the values. + +Maximum information field length is a good example. If the primary station suggests using an information field length of 28000 bits (3500 octets), the secondary station can respond with 28000 bits, if it can use that much or even more, or respond with a lower number of e.g. 592 bits (74 octets) if that is its maximum supported information field length. + +The same applies to the Release ID. If a release 7 primary station attempts to communicate with a release 6 secondary station, the initial message will suggest release 7 and the response will be release 6. + +On the other hand, if a release 6 primary station attempts to communicate with a release 7 secondary station, the initial message will suggest release 6 and the response will release 6. + +Regardless, the primary station will have the final decision, since it can refuse to communicate with a station that does not support whatever parameter values it suggests. It can always repeat the XID negotiation with a new value. + +# Annex C (informative): HDLC parameter negotiation example + +XID Frame from primary station: + +**Table C.1: XID frame from primary station** + +| Field | Content | Description | +|-------|---------|----------------------------------------------| +| ADDR | 12 | Station address | +| CTRL | XID | Command | +| FI | 0x81 | Format identifier | +| GI | 0x80 | HDLC Parameter set | +| GL | 18 | Length of the parameter field (PI) in octets | +| PI | 5 | Maximum I Field length Transmit | +| PL | 4 | Length of the PV field in octets | +| PV | 341040 | Maximum I Field length Transmit in bits | +| PI | 6 | Maximum I Field length Receive | +| PL | 4 | Length of the PV field in octets | +| PV | 224000 | Maximum I Field length Receive in bits | +| PI | 7 | Maximum window size Transmit | +| PL | 1 | Length of the PV field in octets | +| PV | 7 | Maximum window size Transmit | +| PI | 8 | Maximum window size Receive | +| PL | 1 | Length of the PV field in octets | +| PV | 3 | Maximum window size Receive | + +Response from secondary station: + +**Table C.2: XID frame from secondary station** + +| Field | Content | Description | +|-------|---------|-----------------------------------------| +| ADDR | 12 | Station address | +| CTRL | XID | Command | +| FI | 0x81 | Format identifier | +| GI | 0x80 | HDLC Parameters set | +| GL | 16 | Length of the parameter field in octets | +| PI | 5 | Maximum I field length Transmit | +| PL | 2 | Length of the PV field (octets) | +| PV | 3200 | Maximum I field length Transmit in bits | +| PI | 6 | Maximum I field length Receive | +| PL | 4 | Length of the PV field (octets) | +| PV | 341040 | Maximum I field length Receive in bits | +| PI | 7 | Maximum window size Transmit | +| PL | 1 | Length of the PV field (octets) | +| PV | 3 | Maximum window size Transmit | +| PI | 8 | Maximum window size Receive | +| PL | 1 | Length of the PV field (octets) | +| PV | 1 | Maximum window size Receive | + +# Annex D (informative): Address assignment example + +## D.1 Address assignment command + +**Table D.1: Format of the XID frame originated by the primary station** + +| Field | Content | Description | +|-------|---------------------------------------|-------------------------------------------------------------------------------------------------------| +| ADDR | 0xFF | All-station address (Broadcast) | +| CTRL | 0xBF | XID command | +| FI | 0x81 | Format identifier | +| GI | 0xF0 | User defined parameter set | +| GL | 0x10 | Length of the parameter field (rest of the message) in octets | +| PI | 0x01 | Unique ID | +| PL | 0x07 | Length of PV field in octets | +| PV | 0x58 0x59 0x7B 0x20
0x41 0x42 0x43 | Unique ID of the secondary station | +| PI | 0x02 | HDLC address | +| PL | 0x01 | Length of PV field in octets | +| PV | 0x17 | Assigned HDLC address | +| PI | 0x06 | Vendor code as given in AISG v2.0 [4] | +| PL | 0x02 | Length of PV field in octets | +| PV | 0x58 0x59 | Unique assigned vendor code as given in AISG v2.0 [4] (virtual vendor code "XY" used in this example) | + +## D.2 Address assignment response + +**Table D.2: Format of Address Assignment Response by the secondary station** + +| Field | Content | Description | +|-------|------------------------------------------|------------------------------------------------------------| +| ADDR | 0x17 | HDLC address of the station | +| CTRL | 0xBF | XID command | +| FI | 0x81 | Format identifier | +| GI | 0xF0 | User defined parameter set | +| GL | 0x0C | Length of parameter field (rest of the message) in octets. | +| PI | 0x01 | Unique ID | +| PL | 0x07 | Length of PV field in octets | +| PV | 0x58 0x59 0x7B
0x20 0x41 0x42
0x43 | Unique ID of the secondary station | +| PI | 0x04 | Device type | +| PL | 0x01 | Length of PV field in octets | +| PV | 0x01 | Device type as defined in table 4.7.1 | + +NOTE: In this address assignment example messages the virtual vendor code "XY", the unique ID 0x58 0x59 0x7B 0x20 0x41 0x42 0x43, the HDLC address 0x17 and the device type 0x01 for a single-antenna device are used. + +# Annex E (informative): Device scan example + +In some situations it may be found that the Unique ID of a bus device is unknown or has been inaccurately recorded. This HDLC command exchange is used by the primary station to perform a binary tree scan of the bus, in order to identify all connected and disconnected devices. + +**Table E.1: Primary device scan command (XID Frame)** + +| Field | Content | Description | +|-------|----------------|-------------------------------------------------------------------------------------------------------------| +| ADDR | 0xFF | All-station address (Broadcast) | +| CTRL | 0xBF | XID command | +| FI | 0x81 | Format identifier | +| GI | 0xF0 | User defined parameter set | +| GL | 0x0A | Length in octets for the rest of the message | +| PI | 0x01 | Unique ID | +| PL | 0x03 | Length of PV field in octets | +| PV | 0x58 0x11 0x15 | Unique ID supplied by the primary station for masked comparison with the unique ID of the secondary station | +| PI | 0x03 | Bit mask | +| PL | 0x03 | Length of PV field in octets (same as for PI=1) | +| PV | 0xFF 0x17 0xFF | Bit mask to be applied | + +NOTE: The parameters may occur in any order in the XID command. + +## Device Scan Response + +When each secondary station in the NoAddress state receives the command it masks its Unique ID with the bit mask and compares the result with the Unique ID supplied as described in clause 4.8.4. If they match, the secondary station responds using XID format frame according to table 8 of section 5.5 of ISO/IEC 13239 [2]. + +**Table E.2: Secondary device scan response (XID Frame) in case of a match** + +| Field | Content | Description | +|-------|----------------------------------|----------------------------------------------------------------------------------------------------------| +| ADDR | 0x00 | No station address | +| CTRL | 0xBF | XID command | +| FI | 0x81 | Format identifier | +| GI | 0xF0 | User defined parameter set | +| GL | 0x0F | Length in octets for the rest of the message | +| PI | 0x01 | Unique ID | +| PL | 0x06 | Length of PV field in octets | +| PV | 0x58 0x59 0x07 0x5B
0xCD 0x15 | Unique ID of the secondary station | +| PI | 0x06 | Vendor code | +| PL | 0x02 | Length of PV field in octets | +| PV | 0x58 0x59 | Unique assigned vendor code as given in AISG v2.0 [4] (virtual vendor code "XY" is used in this example) | +| PI | 0x04 | Device type | +| PL | 0x01 | Length of PV field in octets | +| PV | 0x01 | Single-antenna RET device type as defined in table 4.7.1 | + +NOTE1: In this device scan example, the virtual vendor code "XY", the unique ID "0x58 0x59 0x07 0x5B 0xCD 0x15", and the device type 0x01 for a single-antenna RET device are used. + +NOTE2: The parameters may occur in any order in the response. + +It is recommended that the response of individual devices is subject to a random delay (within the permitted response time) to aid collision detection at the primary station. + +If there is no response, the primary station knows that no secondary station had those bits in its Unique ID or that the secondary stations having those bits in their unique ID already have assigned addresses, so the tree scan can be truncated at that branch. + +If multiple secondary stations respond, the responses might garble each other, unless one secondary station is close enough to overpower the signal from the other(s). + +If any response arrives, a single frame, multiple frames or frames with incorrect checksums or framing errors, the branch of the tree is inhabited. + +# Annex F (informative): Change History + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-02 | R3-103 | R3-190095 | | | | Text transferred from 25.462 v15.0.0 (changes shown with rev marks) | 1.15.0 | +| 2019-04 | RAN#83 | RP-190598 | | | | Specification approved by RAN plenary | 15.1.0 | +| 2019-12 | RP-86 | RP-192915 | 0001 | 6 | F | Correction for luant | 15.2.0 | +| 2020-07 | RAN#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-03 | RAN#95-e | RP-220238 | 0002 | 1 | D | Inclusive language review | 17.0.0 | +| 2024-03 | RAN#103 | RP-240617 | 0004 | - | D | Rapporteur Editorial Review | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37466/raw.md b/marked/Rel-18/37_series/37466/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..167b7699b5dc740b9c6eb03034eb81f8f3a45b69 --- /dev/null +++ b/marked/Rel-18/37_series/37466/raw.md @@ -0,0 +1,2369 @@ + + +# 3GPP TS 37.466 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Iuant Interface: Application Part (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## --- **Keywords** + +radio, antenna + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|----------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 8 | +| 4 General..... | 8 | +| 4.1 Procedure specification principles ..... | 8 | +| 4.2 Forwards and backwards compatibility..... | 8 | +| 4.3 Multi-antenna units ..... | 9 | +| 4.4 Integer representation..... | 9 | +| 4.5 TMA Subunits ..... | 9 | +| 5 Services expected from signalling transport..... | 9 | +| 5.1 Elementary procedure format..... | 9 | +| 5.1.1 Initiating message..... | 9 | +| 5.1.2 Response message ..... | 10 | +| 6 Control elementary procedures..... | 10 | +| 6.1 State model..... | 10 | +| 6.2 General procedure handling ..... | 11 | +| 6.2.1 Alarms ..... | 11 | +| 6.2.2 Procedure message interpretation..... | 11 | +| 6.2.3 Parallel procedure handling..... | 11 | +| 6.3 Overview of elementary procedures ..... | 12 | +| 6.4 Description of elementary procedures..... | 14 | +| 6.5 Common elementary procedures..... | 15 | +| 6.5.1 Reset Software..... | 15 | +| 6.5.2 Get Alarm Status ..... | 16 | +| 6.5.3 Get Information ..... | 16 | +| 6.5.4 Clear Active Alarms ..... | 17 | +| 6.5.5 Alarm Subscribe ..... | 18 | +| 6.5.6 Self Test..... | 18 | +| 6.5.7 Void..... | 19 | +| 6.5.8 Void..... | 19 | +| 6.5.9 Read User Data..... | 19 | +| 6.5.10 Write User Data..... | 20 | +| 6.5.11 Download Start..... | 21 | +| 6.5.12 Download Application..... | 21 | +| 6.5.13 Download End..... | 22 | +| 6.5.14 Vendor specific procedure..... | 23 | +| 6.6 Single-antenna elementary procedures..... | 23 | +| 6.6.1 Calibrate ..... | 23 | +| 6.6.2 Send Configuration Data ..... | 24 | +| 6.6.3 Set Tilt ..... | 25 | +| 6.6.4 Get Tilt..... | 26 | +| 6.6.5 Alarm Indication..... | 26 | +| 6.6.6 Set Device Data ..... | 27 | +| 6.6.7 Get Device Data ..... | 27 | +| 6.7 Multi-antenna elementary procedures..... | 28 | +| 6.7.1 Antenna Calibrate..... | 28 | +| 6.7.2 Antenna Set Tilt..... | 29 | +| 6.7.3 Antenna Get Tilt..... | 30 | +| 6.7.4 Antenna Set Device Data..... | 30 | +| 6.7.5 Antenna Get Device Data..... | 31 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------------|-----------| +| 6.7.6 | Antenna Alarm Indication ..... | 32 | +| 6.7.7 | Antenna Clear Active Alarms ..... | 32 | +| 6.7.8 | Antenna Get Alarm Status ..... | 33 | +| 6.7.9 | Antenna Get Number Of Antennas ..... | 34 | +| 6.7.10 | Antenna Send Configuration Data ..... | 34 | +| 6.8 | TMAAP Elementary procedures for TMA ..... | 35 | +| 6.8.1 | TMA Set Mode ..... | 35 | +| 6.8.2 | TMA Get Mode ..... | 36 | +| 6.8.3 | TMA Get Supported Functions ..... | 36 | +| 6.8.4 | TMA Set Gain ..... | 37 | +| 6.8.5 | TMA Get Gain ..... | 38 | +| 6.8.6 | TMA Set Device Data ..... | 39 | +| 6.8.7 | TMA Get Device Data ..... | 40 | +| 6.8.8 | TMA Alarm Indication ..... | 40 | +| 6.8.8.1 | Further requirements ..... | 41 | +| 6.8.9 | TMA Clear Active Alarms ..... | 41 | +| 6.8.10 | TMA Get Alarm Status ..... | 42 | +| 6.8.11 | TMA Get Number of Subunits ..... | 42 | +| 6.8.12 | 3GPP Clear Active Alarms and Get Alarm Status ..... | 43 | +| 6.8.13 | TMA Get Supported Non-Linear Gain Values ..... | 43 | +| 7 | Unknown elementary procedures ..... | 44 | +| Annex A (normative): | Return codes for secondary devices ..... | 45 | +| Annex B (normative): | Assigned fields for additional data ..... | 46 | +| Annex C (normative): | Procedure sequence for download of software to a secondary device ..... | 49 | +| Annex D (informative): | Overview of elementary procedures ..... | 50 | +| Annex E (informative): | I-frame and INFO-field format ..... | 52 | +| Annex F (Informative): | Assigned fields for additional data coding for operating bands ..... | 53 | +| Annex G (informative): | Change History ..... | 56 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document is an introduction to the 3GPP TS 37.46x series of Technical Specifications that define the Iuant Interface. The Iuant interface is applicable for UTRAN, E-UTRAN and NG-RAN. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". The logical Iuant interface is an interface internal to the RAN Node and defined to reside between the implementation specific O&M function and the RET antennas together with the TMAs control unit function of the RAN Node. + +The present document is applicable for UTRAN, E-UTRAN and NG-RAN and specifies the *Remote Electrical Tilting Application Part (RETAP)* and the *Tower Mounted Amplifier Application Part (TMAAP)*. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". RETAP supports the functions of the Iuant interface between the implementation specific O&M transport function and the RET Antenna Control unit function, TMAAP supports the functions of the Iuant interface between the implementation specific O&M transport function and the TMA control function. + +# 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] Void +- [3] 3GPP TS 37.462: "Iuant Interface: Signalling Transport". +- [4] 3GPP TS 37.461: "Iuant Interface: Layer 1". +- [5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [5]. + +**Active alarm:** An alarm which has an alarm state that has been raised, but not cleared. + +**Alarm:** Persistent indication of a fault. + +**Alarm code:** A code that identifies a specific alarm. The alarm code set is a subset of the return code set. The alarm codes are listed in annex A of this TS. + +**Alarm state:** A condition or state in the existence of an alarm. Alarm states are raised and cleared. + +**ASCII character:** A character forming part of the International Reference Version of the 7-bit character set defined in ISO/IEC 646:1991. + +**Calibrate:** Exercise the antenna drive unit over its entire range of travel to ensure fault-free operation and synchronise the measured and actual beam tilt of the antenna. + +**Configuration data:** A stored table or function defining the relationship between the physical position of the drive and electrical beam tilt. + +**Data type:** A definition determining the value range and interpretation of a series of octets. The following specified data types are used in this TS: + +| Name: | Definition: | +|---------------|----------------------------------------------------------------------------------------------| +| AlarmCode | 1 octet unsigned enumerated code
All AlarmCode values are listed in annex A of this TS | +| FieldNumber | 1 octet unsigned enumerated code
All field number values are listed in annex B of this TS | +| ProcedureCode | 1 octet unsigned enumerated code | +| ReturnCode | 1 octet unsigned enumerated code
All ReturnCode values are listed in annex A of this TS | +| TextString | Octets with integer values in the range of 32 to 126 to be interpreted as ASCII characters | + +**Elementary procedure:** The RETAP and TMAAP protocol consists of elementary procedures (EPs). An elementary procedure is a unit of interaction between the primary device (RAN Node) and the secondary devices (RET or TMAs devices) + +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. + +**Error:** Deviation of a system from normal operation. + +**Fault:** Lasting error condition. + +**Little endian:** The order of transmission in which the least-significant octets of a multi-octet representation of a number are transmitted first. Little endian only applies to binary integer representations. + +**MaxDataReceiveLength:** SecondaryPayloadReceiveLength minus 3 octets (see subclause 4.8.1 in TS 37.462 [3]). + +**MaxDataTransmitLength:** SecondaryPayloadTransmitLength minus 3 octets (see subclause 4.8.1 in TS 37.462 [3]). + +**Procedure code:** A code identifying an elementary procedure. + +**Reset:** A process by which the device is put in the state it reaches after a completed power-up. + +**Return code:** A code which defines information about the outcome of an elementary procedure execution. + +**Tilt (also downtilt, tilt angle, beamtilt):** The elevation angle between the direction orthogonal to the antenna element axis and the maximum of its main beam in the elevation plane. A positive electrical tilt angle means that the antenna + +beam is directed below the direction orthogonal to the antenna axis. An antenna has separate values for electrical and mechanical tilt. The mechanical tilt is fixed by the geometry of the installation. In this TS the tilt referred to is always the electrical tilt unless otherwise stated. + +**Tilt value:** A signed integer used in elementary procedures to define the electrical tilt setting of the antenna. The tilt value is 10 times the antenna electrical tilt angle in degrees. + +**TMA:** A TMA comprises a low noise amplifier together with its control and monitoring electronics and optional antenna modem. + +**TMA subunit:** A TMA may comprise more than one TMA subunit. All TMA subunits within one TMA have the same HDLC address and are addressable by an index via the application layer procedures. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [5] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [5]. + +| | | +|-------|--------------------------------------------| +| EP | Elementary Procedure | +| HDLC | High-Level Data Link Control | +| RET | Remote Electrical Tilting | +| TMA | Tower Mounted Amplifier | +| RETAP | Remote Electrical Tilting Application Part | +| TMAAP | Tower Mounted Amplifier Application Part | +| TCP | Time-Consuming Procedure | + +# --- 4 General + +## 4.1 Procedure specification principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the RET antenna control unit and TMA Subunits exactly and completely. The RAN Node functional behaviour is left unspecified. + +The following specification principles have been applied for the procedure text in clause 6: + +- 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. + +- 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. + +## 4.2 Forwards and backwards compatibility + +The forwards and backwards compatibility of all versions of the protocol shall be assured by a mechanism in which all current and further messages will not be changed in the future. These parts can always be decoded regardless of the standard version. + +New functionalities are added into the specification by introducing new procedures and thus the existing messages are not changed in the future. + +## 4.3 Multi-antenna units + +The RETAP elementary procedures are split into a single-antenna oriented part, a multi-antenna oriented part and a common part for both device types in order to support RET units controlling single- or multi-antenna devices. The RET unit responds, upon request, the number of antennas it controls. All multi-antenna oriented elementary procedures include a parameter stating which antenna the elementary procedure addresses. Antennas are numbered 1 and upwards. + +## 4.4 Integer representation + +Multi-octet integer values are transmitted in little endian order. Signed integers are represented as 2-complement values. + +## 4.5 TMA Subunits + +TMA subunits shall be numbered starting with 1 and proceeding upwards. The error message format for TMA procedures follows that of multiple RET devices. + +# --- 5 Services expected from signalling transport + +RETAP and TMAAP requires an assured in-sequence delivery service from the signalling transport and notification if the assured in-sequence delivery service is no longer available. + +## 5.1 Elementary procedure format + +Layer 2 provides a full-duplex link for the transmission of RETAP and TMAAP messages. + +There are two types of RETAP and TMAAP elementary procedures: + +**Class 1:** Initiating messages are sent either from the primary to a secondary device, or from a secondary to the primary device, in order to initiate some action within the receiving device. The other device sends a response message completing the procedure. + +**Class 2:** Initiating messages are sent either from the primary to a secondary device, or from a secondary to the primary device. No response message is expected. + +All RETAP and TMAAP messages use the same basic format: + +**Table 5.1.1: Basic format for all RETAP and TMAAP messages** + +| Elementary procedure | Number of data octets | Data | +|----------------------|-----------------------|---------------------------------------------------| +| 1 octet | 2 octets | MaxDataReceiveLength or
MaxDataTransmitLength. | + +NOTE: Response messages have the same basic format as initiating messages. The elementary procedure code shall be the same in the response message as in the associated initiating message. + +### 5.1.1 Initiating message + +The data part of an initiating message may contain parameters as specified in clause 6 of this TS. + +### 5.1.2 Response message + +Elementary procedures shall, unless otherwise specified, provide a response message within 1 second. The response time is measured from the time the message frame was received by the transport layer to the time the response message is ready for transfer by the transport layer. + +If the class1 elementary procedure requested by the initiating message was successfully executed, the response message data part from a single-antenna device shall contain return code . Additional information may follow in the data part. The response message data part from a multi-antenna device starts with the antenna number followed by return code and optional additional information. + +If the elementary procedure requested by the initiating message was not successfully executed, the response message data part from a single-antenna device shall contain return code . + +The following octet shall contain a second return code which describes why the execution of the requested procedure failed. The response message data part from a multi-antenna device starts with the antenna number followed by return code and a second return code which describes why the execution of the requested procedure failed. + +In some situations an initiating message can cause a change of operating conditions, for instance a SetTilt procedure might cause a RET device to discover that an adjuster is jammed or that a previously jammed adjuster works normally again. In these cases an alarm procedure reporting the change of operating conditions shall be used in addition to the regular or return codes in response message. + +A complete annotated table of all return codes with their corresponding hexadecimal numbers is provided in annex A of this TS. + +Return codes marked with an X in the Alarm column of annex A in this TS are used to report operating conditions in alarm procedures (see subclauses 6.6.5 and 6.7.6 for details). + +# 6 Control elementary procedures + +## 6.1 State model + +The state model describing the secondary device is shown in figure 6.1 with procedures written in *italic*. + +The relation to the connection state model for layer 2 can be found in TS 37.462 [3]. + +![State model diagram for the Secondary device showing two main states: DownloadMode and OperatingMode, with transitions between them based on specific conditions and procedures.](cd48273072c5c3a23e11fde892d1b6b6_img.jpg) + +``` + +stateDiagram-v2 + [*] --> DownloadMode : Link Establishment from state AddressAssigned, see ref. [3] + [*] --> OperatingMode : Application software is available + DownloadMode --> [*] : DownloadEnd or ResetSoftware + DownloadMode --> DownloadMode : GetInformation, DownloadStart or DownloadApplication + OperatingMode --> DownloadMode : DownloadStart + OperatingMode --> [*] : All other Elementary Procedures except for DownloadApplication and DownloadEnd + +``` + +The diagram illustrates the state model for the Secondary device. It features two primary states: **DownloadMode** and **OperatingMode**. The device starts in an initial state (represented by a solid black circle) and transitions to **DownloadMode** via *Link Establishment from state AddressAssigned, see ref. [3]*. From **DownloadMode**, the device can return to the initial state via *DownloadEnd or ResetSoftware*, remain in **DownloadMode** via *GetInformation, DownloadStart or DownloadApplication*, or transition to **OperatingMode** via *DownloadStart*. From **OperatingMode**, the device can return to **DownloadMode** via *DownloadStart* or return to the initial state via *All other Elementary Procedures except for DownloadApplication and DownloadEnd*. The initial state is also labeled as *to state NoAddress, see ref. [3]*. + +State model diagram for the Secondary device showing two main states: DownloadMode and OperatingMode, with transitions between them based on specific conditions and procedures. + +Figure 6.1: State model for the Secondary device + +If an application software is not missing the secondary device enters the state OperatingMode. + +If an application software is missing, the secondary device enters the state DownloadMode. In this state only software download functionality is supported in order to restore the application software. + +The primary device will be notified that the secondary device has entered the state DownloadMode when a procedure which only is supported in the state OperatingMode fails with the return code WorkingSoftwareMissing. + +If no software download functionality is supported, then only the state OperatingMode for the secondary device is supported. + +## 6.2 General procedure handling + +### 6.2.1 Alarms + +When a fault is detected, the corresponding alarm state shall be changed to state *raised* by the secondary device. When the fault no longer exists, the corresponding alarm state shall be changed to state *cleared* by the secondary device. Alarm changes are reported through the AlarmIndication or AntennaAlarmIndication elementary procedures. Whenever an AlarmIndication or AntennaAlarmIndication elementary procedure message is transmitted, it shall contain all the alarm states changed that have not yet been reported as described in subclauses 6.6.5 and 6.7.6. + +All alarm states shall be cleared by any type of reset. + +### 6.2.2 Procedure message interpretation + +The following message interpretation rules shall apply to a secondary device in the order mentioned: + +- Any message shorter than 3 octets shall be disregarded. In case of Multi-Antenna-Procedures or TMA-Procedures, which uses a subunit field, any messages shorter than 4 octets shall be disregarded; +- If a message has a length inconsistent with its "Number of data octets" field value it shall be responded with a failure message stating "FormatError" as the cause of failure. The response message shall be to the initiating message identified by the procedure code; +- If a secondary device in the OperatingMode state receives a procedure message which is undefined for this device type, it shall respond with "Unknown Procedure"; +- If a secondary device in the OperatingMode state is receiving a procedure message of an optional procedure not supported, it shall respond with a failure message stating "UnsupportedProcedure" as the cause of failure; +- If a secondary device receives a procedure message, part of the software download procedure sequence described in Annex C, without having received the previous procedure messages in that sequence it shall respond with a failure message stating "InvalidProcedureSequence" as the cause of failure; +- If a secondary device in the DownloadMode state is receiving a procedure message not supported in that state it shall respond with a failure message stating "WorkingSoftwareMissing" as the cause of failure; +- If a message has a length inconsistent with the defined message length in the procedure definition it shall be responded with a failure message stating "FormatError" as the cause of failure. The response message shall be to the initiating message identified by the procedure code; +- If a secondary device in the OperatingMode state is receiving a procedure message which addressed device subunit does not exist "FormatError" shall be returned. + +### 6.2.3 Parallel procedure handling + +The secondary device shall support parallel execution of in maximum one additional EP only in parallel to one of the Time-Consuming Procedures defined in table 6.2.3.1: + +**Table 6.2.3.1: Definition of TCPs and the execution of procedures in parallel to a TCP** + +| Elementary Procedure | TCP | Execution in parallel to a TCP | +|-------------------------------------|-----------------|--------------------------------| +| Common Procedure Set | | | +| (Reserved) | | | +| Reset Software | No | mandatory | +| Get Alarm Status | No | mandatory | +| Get Information | No | mandatory | +| Clear Active Alarms | No | disallowed | +| Read User Data | No | optional | +| Write User Data | No | optional | +| Alarm Subscribe | No | optional | +| Self Test | Yes | disallowed | +| Download Start | No | disallowed | +| Download Application | No | disallowed | +| Download End | No | disallowed | +| Vendor specific procedure | vendor specific | optional | +| Single-Antenna Procedure Set | | | +| Set Device Data | No | optional | +| Get Device Data | No | optional | +| Calibrate | Yes | disallowed | +| Send Configuration Data | No | disallowed | +| Set Tilt | Yes | disallowed | +| Get Tilt | No | optional | +| Alarm Indication | No | optional | +| Multi-Antenna Procedure Set | | | +| Antenna Calibrate | Yes | optional | +| Antenna Send Configuration Data | No | disallowed | +| Antenna Set Tilt | Yes | optional | +| Antenna Get Tilt | No | optional | +| Antenna Set Device Data | No | optional | +| Antenna Get Device Data | No | optional | +| Antenna Alarm Indication | No | optional | +| Antenna Clear Active Alarms | No | disallowed | +| Antenna Get Alarm Status | No | mandatory | +| Antenna Get Number of Antennas | No | mandatory | + +"yes" in the "TCP" column indicates that the procedure is a TCP, "no" in the "TCP" column indicates that the procedure is not a TCP. "mandatory" in the "Execution in parallel to a TCP" column indicates that the procedure shall be executed in parallel to an ongoing TCP. "optional" in this column indicates, that the support of the execution of the procedure in parallel to an ongoing TCP is optional and "disallowed" indicates that the procedure shall not be executed in parallel to a TCP. + +If a secondary device receives an initiating message for an EP which cannot be executed due to the ongoing execution of other EPs, the secondary device shall respond with a failure message stating "Busy" as the cause of failure. + +Parallel execution of one TCP marked "optional" in the "Execution in parallel to a TCP" column in table 6.2.3.1 may be supported for each antenna by the secondary device. The EPs AntennaSetTilt and AntennaCalibrate shall be executed in parallel only for different antenna numbers. If more than one TCP is executed, ResetSoftware shall be executed anyway and never be responded with "Busy". + +If the EPs Get Tilt and Antenna GetTilt are executed in parallel with a TCP, their response message shall deliver a tilt value sampled during their execution. + +TMAAP doesn't define any TCPs. Therefore parallel procedure handling is not supported by TMAAP. + +## 6.3 Overview of elementary procedures + +The set of elementary procedures for RET antennas and TMAs control provides procedure-oriented instructions. An overview of the procedures is given in annex D. Table 6.3.1 lists all common elementary procedures described in subclause 6.5. Table 6.3.2 lists all RETAP elementary procedures specific for single-antenna device types described in subclause 6.6. Table 6.3.3 lists all RETAP elementary procedures specific for multi-antenna device types described in + +subclause 6.7. Table 6.3.4 lists all TMAAP elementary procedures specific for TMA device types described in subclause 6.8. Subclause 6.4 describes how to interpret the elementary procedure definitions in subclauses 6.5 to 6.8. + +Some elementary procedures shall be performed in sequence as described in Annex C for the software download. + +**Table 6.3.1: Common elementary procedure set for all device types** + +| Elementary procedure | Requirement | Comment | +|---------------------------|-------------|---------------------------------------------------------------------------| +| Reset Software | Mandatory | | +| Get Alarm Status | Mandatory | | +| Get Information | Mandatory | | +| Clear Active Alarms | Mandatory | | +| Alarm Subscribe | Mandatory | | +| Read User Data | Mandatory | | +| Write User Data | Mandatory | | +| Self Test | Mandatory | | +| Download Start | Optional | This procedure is mandatory if the software download feature is supported | +| Download Application | Optional | This procedure is mandatory if the software download feature is supported | +| Download End | Optional | This procedure is mandatory if the software download feature is supported | +| Vendor specific procedure | Optional | | + +**Table 6.3.2: RETAP Elementary procedure set for single-antenna device type** + +| Elementary procedure | Requirement | Comment | +|-------------------------|-------------|---------| +| Calibrate | Mandatory | | +| Send Configuration Data | Mandatory | | +| Set Tilt | Mandatory | | +| Get Tilt | Mandatory | | +| Alarm Indication | Mandatory | | +| Set Device Data | Mandatory | | +| Get Device Data | Mandatory | | + +**Table 6.3.3: RETAP Elementary procedure set for multi-antenna device type** + +| Elementary procedure | Requirement | Comment | +|---------------------------------|-------------|---------| +| Antenna Calibrate | Mandatory | | +| Antenna Send Configuration Data | Mandatory | | +| Antenna Set Tilt | Mandatory | | +| Antenna Get Tilt | Mandatory | | +| Antenna Set Device Data | Mandatory | | +| Antenna Get Device Data | Mandatory | | +| Antenna Alarm Indication | Mandatory | | +| Antenna Clear Active Alarms | Mandatory | | +| Antenna Get Alarm Status | Mandatory | | +| Antenna Get Number Of Antennas | Mandatory | | + +**Table 6.3.4: TMAAP elementary procedure set for TMA devices** + +| Elementary procedure | Requirement | Comment | +|------------------------------------|-------------|-----------------------------------------------------------------------------------------| +| TMASetMode | Optional | Shall only be supported if the TMA subunit supports bypass mode | +| TMAGetMode | Mandatory | | +| TMAGetSupportedFunctions | Mandatory | | +| TMASetGain | Optional | Shall only be supported if the TMA subunit supports variable gain | +| TMAGetGain | Mandatory | | +| TMASetDeviceData | Mandatory | | +| TMAGetDeviceData | Mandatory | | +| TMAAlarmIndication | Mandatory | | +| TMAClearActiveAlarms | Mandatory | | +| TMAGetAlarmStatus | Mandatory | | +| TMAGetNumberOfSubunits | Mandatory | | +| TMAGetSupportedNonLinearGainValues | Optional | Shall only be supported if the TMA subunit supports variable gain with non-linear steps | + +## 6.4 Description of elementary procedures + +**Table 6.4.1: Description of elementary procedures** + +| | | | | | +|-------------------------------------------------------------------------------------|---------------------------------------------------------|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name:
The name used to refer to the elementary procedure | | | | | +| Code:
The code is defined here. All other code references are informative | Issued by:
Primary device or secondary device | Procedure class:
Class 1 or Class 2 | DownloadMode state:
Defines whether the procedure shall be supported in the DownloadMode state. | Power mode:
Defines the secondary device power consumption as described in TS 37.461 [4] during the execution of the elementary procedure. | + +**Table 6.4.2: Initiating and response message parameters and format** + +| Number | Length | Type | Description | +|-------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------|-------------------------------| +| The enumerated order in which the parameter occurs in the data field of the message. The first number is 1. | The length of the parameter, in number of octets, if defined. | The data type used in the parameter. | Description of the parameter. | + +**Table 6.4.3: Response message parameters and format for common class 1 elementary procedures upon error** + +| Number | Length | Type | Description | +|--------|---------|------------|--------------------| +| 1 | 1 octet | ReturnCode | Return code FAIL | +| 2 | 1 octet | ReturnCode | Reason for failure | + +**Table 6.4.4: Response message parameters and format for single-antenna class 1 elementary procedures upon error** + +| Number | Length | Type | Description | +|--------|---------|------------|--------------------| +| 1 | 1 octet | ReturnCode | Return code FAIL | +| 2 | 1 octet | ReturnCode | Reason for failure | + +**Table 6.4.5: Response message parameters and format for multi-antenna class 1 and TMA subunit class 1 elementary procedures upon error** + +| Number | Length | Type | Description | +|--------|---------|------------------|--------------------------------------| +| 1 | 1 octet | Unsigned integer | Antenna number or TMA subunit number | +| 2 | 1 octet | ReturnCode | Return code FAIL | +| 3 | 1 octet | ReturnCode | Reason for failure | + +NOTE 1: The response message in the elementary procedure AntennaGetAntennaNumber, has the format given in table 6.4.4, although it is defined as a multi-antenna class 1 elementary procedure. + +NOTE 2: The response message in the elementary procedure TMAGetNumberOfSubunits has the format given in table 6.4.4 as class 1 elementary procedure. + +**Table 6.4.6: Return codes** + +| OK | FAIL | Comment | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| All return codes applicable in a response message to a successful procedure, except "OK", are listed here. The return codes are listed by name as defined in annex A. | All return codes applicable in a response message to a failing procedure, except "FAIL" are listed here. The return codes are listed by name as defined in annex A. | Any comment needed for clarification. | + +## 6.5 Common elementary procedures + +### 6.5.1 Reset Software + +**Table 6.5.1.1: Elementary procedure Reset Software** + +| Name:
ResetSoftware | | | | | +|------------------------|------------------------------|-----------------------|----------------------------|--------------------| +| Code:
0x03 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
Yes | Power mode:
Low | + +**Table 6.5.1.2: Initiating message parameters and format for Reset Software** + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +**Table 6.5.1.3: Response message parameters and format for Reset Software** + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### Description: + +On the receipt of the initiating message the secondary device shall reset the application. All alarm states shall be cleared. + +If the initiating message is received in the OperatingMode state, the transport layer shall remain unaffected. + +If the initiating message is received in the DownloadMode state, the ResetSoftware procedure shall reset the entire device without activating any new application software downloaded since entering the DownloadMode state. + +The device shall not execute the reset procedure before transport layer acknowledgement through sequence number update is received for the response. + +Table 6.5.1.4: Return codes for Reset Software + +| OK | FAIL | Comment | +|----|-------------|----------------------------------------------------------------------| +| | FormatError | In case of format error, the procedure code validity is not secured. | + +### 6.5.2 Get Alarm Status + +Table 6.5.2.1: Elementary procedure Get Alarm Status + +| | | | | | +|--------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
GetAlarmStatus | | | | | +| Code:
0x04 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +Table 6.5.2.2: Initiating message parameters and format for Get Alarm Status + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +Table 6.5.2.3: Response message parameters and format for Get Alarm Status + +| Number | Length | Type | Description | +|--------|---------|------------|-----------------------| +| 1 | 1 octet | ReturnCode | Return code OK | +| i + 1 | 1 octet | AlarmCode | Active alarm number i | + +i = 1 ... N + +#### Description: + +On receipt of the initiating message the secondary device reports the alarm codes of the active alarms. + +Table 6.5.2.4: Return codes for Get Alarm Status + +| OK | FAIL | Comment | +|--------------------------------------------------------|---------------------------------------|---------| +| All return codes marked as used for alarms in Annex A. | FormatError
WorkingSoftwareMissing | | + +### 6.5.3 Get Information + +Table 6.5.3.1: Elementary procedure Get Information + +| | | | | | +|--------------------------------|-------------------------------------|------------------------------|-----------------------------------|---------------------------| +| Name:
GetInformation | | | | | +| Code:
0x05 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
Yes | Power mode:
Low | + +Table 6.5.3.2: Initiating message parameters and format for Get Information + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +**Table 6.5.3.3: Response message parameters and format for Get Information** + +| Number | Length | Type | Description | +|--------|---------|------------------|-------------------------------------------| +| 1 | 1 octet | ReturnCode | Return code OK | +| 2 | 1 octet | Unsigned integer | Length of parameter 3 in number of octets | +| 3 | | TextString | Product number | +| 4 | 1 octet | Unsigned integer | Length of parameter 5 in number of octets | +| 5 | | TextString | Serial number | +| 6 | 1 octet | Unsigned integer | Length of parameter 7 in number of octets | +| 7 | | TextString | Hardware Version | +| 8 | 1 octet | Unsigned integer | Length of parameter 9 in number of octets | +| 9 | | TextString | Software Version | + +#### **Description:** + +On receipt of the initiating message the secondary device shall return the product number ProdNr and the serial number SerNr of the secondary device. If known, also the hardware version and the software version may be returned. The software version should indicate the version number of the currently executed software. + +The parameters HWVersion and SWVersion in the response message refer to the version designators of the hardware and installed software of the secondary device. If the application is missing or no HW or SW version number is found, then an empty string shall be returned as the HW or SW version number. The empty string is represented as a length field equals 0 and no octets in the TextString field. + +The response message length shall be less than or equal to the minimum SecondaryPayloadTransmitLength as given in subclause 4.8.1 in TS 37.462 [3]. + +**Table 6.5.3.4: Return codes for Get Information** + +| OK | FAIL | Comment | +|----|-------------|---------| +| | FormatError | | + +### 6.5.4 Clear Active Alarms + +**Table 6.5.4.1: Elementary procedure Clear Active Alarms** + +| | | | | | +|-----------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
ClearActiveAlarms | | | | | +| Code:
0x06 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.5.4.2: Initiating message parameters and format for Clear Active Alarms** + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +**Table 6.5.4.3: Response message parameters and format for Clear Active Alarms** + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### **Description:** + +On receipt of the initiating message the secondary device shall first clear all stored alarm information and then return a procedure response message. + +**Table 6.5.4.4: Return codes for Clear Active Alarms** + +| OK | FAIL | Comment | +|-----------|-----------------------------------------------|----------------| +| | FormatError
Busy
WorkingSoftwareMissing | | + +### 6.5.5 Alarm Subscribe + +**Table 6.5.5.1: Elementary procedure Alarm Subscribe** + +| | | | | | +|--------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AlarmSubscribe | | | | | +| Code:
0x12 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.5.5.2: Initiating message parameters and format for Alarm Subscribe** + +| Number | Length | Type | Description | +|---------------|---------------|-------------|--------------------| +| None | 0 octets | None | No data carried | + +**Table 6.5.5.3: Response message parameters and format for Alarm Subscribe** + +| Number | Length | Type | Description | +|---------------|---------------|-------------|--------------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### Description: + +On receipt of the initiating message the secondary device shall start reporting alarms to the primary device. + +**Table 6.5.5.4: Return codes for Alarm Subscribe** + +| OK | FAIL | Comment | +|-----------|-----------------------------------------------|----------------| +| | FormatError
Busy
WorkingSoftwareMissing | | + +### 6.5.6 Self Test + +**Table 6.5.6.1: Elementary procedure Self Test** + +| | | | | | +|--------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------| +| Name:
SelfTest | | | | | +| Code:
0x0A | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
High | + +**Table 6.5.6.2: Initiating message parameters and format for Self Test** + +| Number | Length | Type | Description | +|---------------|---------------|-------------|--------------------| +| None | 0 octets | None | No data carried | + +**Table 6.5.6.3: Response message parameters and format for Self Test** + +| Number | Length | Type | Description | +|--------|---------|------------|---------------------------------------------------| +| 1 | 1 octet | ReturnCode | Return code OK | +| i + 1 | 1 octet | AlarmCode | Alarm code for alarm i detected during self test. | + +i = 1 ... N + +#### Description: + +On receipt of the initiating message the secondary device shall execute a test procedure which may include a check of physical and processor functions. The specific tests to be performed are implementation specific, and may include the movement of the adjuster, which shall not exceed +/-5% of total available tilting range starting from the current adjuster position. + +The response message of the secondary device on the procedure provides information on detected faults or, if no fault is detected, with confidence that the operation of the device is normal in all respects. + +During the test the operational parameters of the device shall not change beyond operationally acceptable limits and on completion all parameters shall be returned to their initial values. + +In the normal response message, after the self test was executed successfully, the return codes are set to report possible detected faults during the self test. If no faults are detected, this shall be signalled by no return codes following the return code . + +In the case of a failure response message, the self test could not be executed successfully and the reported return code relates to the inability of the device to perform the requested self-test operation. + +**Table 6.5.6.4: Return codes for Self Test** + +| OK | FAIL | Comment | +|-----------------------------------------------|-----------------------------------------------------------------------------|---------| +| All return codes marked as alarms in annex A. | FormatError
Busy
WorkingSoftwareMissing
NotCalibrated
NotScaled | | + +6.5.7 Void + +6.5.8 Void + +6.5.9 Read User Data + +**Table 6.5.9.1: Elementary procedure Read User Data** + +| | | | | | +|------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
ReadUserData | | | | | +| Code:
0x10 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.5.9.2: Initiating message parameters and format for Read User Data** + +| Number | Length | Type | Description | +|--------|----------|------------------|--------------------------| +| 1 | 2 octets | Unsigned integer | Memory offset | +| 2 | 1 octet | Unsigned integer | Number of octets to read | + +NOTE: Number of octets to read shall be less than, or equal to MaxDataTransmit Length minus 1. + +**Table 6.5.9.3: Response message parameters and format for Read User Data** + +| Number | Length | Type | Description | +|--------|-----------------------------------------------------------------|---------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | +| 2 | Number of octets given by parameter 2 of the initiating message | User specific | User data | + +#### **Description:** + +On receipt of the initiating message the secondary device shall send back user specific data stored in a user data area to the primary device. + +The user data area is intended for storage of user defined data, e.g. inventory information. + +**Table 6.5.9.4: Return codes for Read User Data** + +| OK | FAIL | Comment | +|----|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| | FormatError
WorkingSoftwareMissing
OutOfRange | The return code OutOfRange is used, if the given memory address range is outside the valid address space. | + +### 6.5.10 Write User Data + +**Table 6.5.10.1: Elementary procedure Write User Data** + +| | | | | | +|-------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
WriteUserData | | | | | +| Code:
0x11 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.5.10.2: Initiating message parameters and format for Write User Data** + +| Number | Length | Type | Description | +|--------|----------------------------------------|------------------|---------------------------| +| 1 | 2 octets | Unsigned integer | Memory offset | +| 2 | 1 octet | Unsigned integer | Number of octets to write | +| 3 | Message specific, given by parameter 2 | User specific | Data to write | + +NOTE: Number of octets to write shall be less than, or equal to MaxDataReceiveLength minus 3. + +**Table 6.5.10.3: Response message parameters and format for Write User Data** + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### **Description:** + +On receipt of the initiating message the secondary device shall store user data in non-volatile memory. The user data is stored in the user data area using the relative memory address offset given in the initiating message and starting with zero. + +The user data area is intended for storage of user defined data, e.g. inventory information. + +Table 6.5.10.4: Return codes for Write User Data + +| OK | FAIL | Comment | +|----|------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| | FormatError
Busy
WorkingSoftwareMissing
HardwareError
OutOfRange | The return code OutOfRange is used if the given memory address range is outside the valid address space. | + +### 6.5.11 Download Start + +Table 6.5.11.1: Elementary procedure Download Start + +| | | | | | +|-------------------------------|-------------------------------------|------------------------------|-----------------------------------|---------------------------| +| Name:
DownloadStart | | | | | +| Code:
0x40 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
Yes | Power mode:
Low | + +Table 6.5.11.2: Initiating message parameters and format for Download Start + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +Table 6.5.11.3: Response message parameters and format for Download Start + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### Description: + +On receipt of this initiating message the software download process shall be initiated. Following transition to the DownloadMode state, the secondary device sends return code . Previous subscription of alarms by use of the AlarmSubscribe procedure is cancelled. + +Table 6.5.11.4: Return codes for Download Start + +| OK | FAIL | Comment | +|----|---------------------------------------------|---------| +| | FormatError
Busy
UnsupportedProcedure | | + +### 6.5.12 Download Application + +Table 6.5.12.1: Elementary procedure Download Application + +| | | | | | +|-------------------------------------|-------------------------------------|------------------------------|-----------------------------------|---------------------------| +| Name:
DownloadApplication | | | | | +| Code:
0x41 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
Yes | Power mode:
Low | + +Table 6.5.12.2: Initiating message parameters and format for Download Application + +| Number | Length | Type | Description | +|--------|---------------------------------------------|-----------------|---------------| +| 1 | Less than, or equal to MaxDataReceiveLength | Vendor specific | Software data | + +**Table 6.5.12.3: Response message parameters and format for Download Application** + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### **Description:** + +This elementary procedure is used once or several times to transfer software data from the primary device to the secondary device. + +**Table 6.5.12.4: Return codes for Download Application** + +| OK | FAIL | Comment | +|----|----------------------------------------------------------------------------------------|---------| +| | FormatError
Busy
HardwareError
InvalidFileContent
InvalidProcedureSequence | | + +### 6.5.13 Download End + +**Table 6.5.13.1: Elementary procedure Download End** + +| | | | | | +|-----------------------------|-------------------------------------|------------------------------|-----------------------------------|---------------------------| +| Name:
DownloadEnd | | | | | +| Code:
0x42 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
Yes | Power mode:
Low | + +**Table 6.5.13.2: Initiating message parameters and format for Download End** + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +**Table 6.5.13.3: Response message parameters and format for Download End** + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### **Description:** + +This elementary procedure signals the end of a multi-message data transfer to the secondary device. The secondary device shall respond after verifying the received data. The secondary device shall reset autonomously after completion of the layer 2 response and activate the new application software. + +**Table 6.5.13.4: Return codes for Download End** + +| OK | FAIL | Comment | +|----|---------------------------------------------------------------------------------------------------------|---------| +| | FormatError
Busy
HardwareError
ChecksumError
InvalidFileContent
InvalidProcedureSequence | | + +### 6.5.14 Vendor specific procedure + +Table 6.5.14.1: Elementary procedure Vendor Specific Procedure + +| | | | | | +|-----------------------------------------|--------------------------------------|--------------------------------------------|-----------------------------------------------|---------------------------------------| +| Name:
VendorSpecificProcedure | | | | | +| Code:
0x90 | Issued by:
Vendor specific | Procedure class:
Vendor specific | DownloadMode state:
Vendor specific | Power mode:
Vendor specific | + +Table 6.5.14.2: Initiating message parameters and format for Vendor Specific Procedure + +| Number | Length | Type | Description | +|--------|-----------------|-----------------|-------------| +| 1 | 2 octets | ASCII | Vendor code | +| 1 + i | Vendor specific | Vendor specific | | + +i = 1 ... N + +Table 6.5.14.3: Response message parameters and format for Vendor Specific Procedure + +| Number | Length | Type | Description | +|--------|-----------------|-----------------|-----------------| +| 1 | Vendor specific | Vendor specific | Vendor specific | + +i = 1 ... N + +#### Description: + +The vendor specific procedure is intended for vendor specific purposes like e.g. testing. + +Table 6.5.14.4: Return codes for vendor specific procedure + +| OK | FAIL | Comment | +|----|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| | FormatError
UnsupportedProcedure | If the Vendor code in the initiating message does not match that of the RET device, UnsupportedProcedure shall be returned. | + +## 6.6 Single-antenna elementary procedures + +### 6.6.1 Calibrate + +Table 6.6.1.1: Elementary procedure Calibrate + +| | | | | | +|---------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------| +| Name:
Calibrate | | | | | +| Code:
0x31 | Issued by:
Primary Device | Procedure class:
1 | DownloadMode state:
No | Power mode:
High | + +Table 6.6.1.2: Initiating message parameters and format for Calibrate + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +**Table 6.6.1.3: Response message parameters and format for Calibrate** + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### **Description:** + +On receipt of the initiating message the secondary device shall perform a calibration of the RET antenna where the actuator is driven through its whole tilt range. + +The response time to this Calibrate procedure shall be less than 4 minutes. + +**Table 6.6.1.4: Return codes for Calibrate** + +| OK | FAIL | Comment | +|----|------------------------------------------------------------------------------------------------------------------------------------|---------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
MotorJam
ActuatorJam
NotConfigured
UnsupportedProcedure | | + +### 6.6.2 Send Configuration Data + +**Table 6.6.2.1: Elementary procedure Send Configuration Data** + +| | | | | | +|---------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
SendConfigurationData | | | | | +| Code:
0x32 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.6.2.2: Initiating message parameters and format for Send Configuration Data** + +| Number | Length | Type | Description | +|--------|---------------------------------------------|-----------------|--------------------| +| 1 | Less than, or equal to MaxDataReceiveLength | Vendor specific | Configuration data | + +**Table 6.6.2.3: Response message parameters and format for Send Configuration Data** + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### **Description:** + +On receipt of the initiating message the secondary device shall store the provided vendor and antenna specific configuration data for the relationship between the movement of the drive system and the beam tilt position of the antenna. + +If the configuration data exceeds MaxDataReceiveLength, the data shall be split into a number of MaxDataReceiveLength segments and one final segment with whatever is left. The primary device transmits the segments in order. The layer 2 sequence numbers guarantee that no segment will be lost or received out of order. + +**Table 6.6.2.4: Return codes for Send Configuration Data** + +| OK | FAIL | Comment | +|----|-------------------------------------------------------------------------------------------------------------------------------|---------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
ChecksumError
InvalidFileContent
UnsupportedProcedure | | + +### 6.6.3 Set Tilt + +**Table 6.6.3.1: Elementary procedure Set Tilt** + +| | | | | | +|-------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------| +| Name:
SetTilt | | | | | +| Code:
0x33 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
High | + +**Table 6.6.3.2: Initiating message parameters and format for Set Tilt** + +| Number | Length | Type | Description | +|--------|----------|----------------|-------------| +| 1 | 2 octets | Signed integer | Tilt value | + +**Table 6.6.3.3: Response message parameters and format for Set Tilt** + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### Description: + +On receipt of the initiating message the secondary device shall set the electrical tilt in increments of 0.1°. + +The secondary device shall respond to the initiating message in less than 2 minutes. + +The tilt value corresponding to the actual tilt angle shall not go outside of the range between the tilt value corresponding to the current tilt angle and the tilt value corresponding to the requested tilt angle by more than 5 during this operation. + +The format of the value of parameter 1 is given in subclause 3.1. + +**Table 6.6.3.4: Return codes for Set Tilt** + +| OK | FAIL | Comment | +|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
MotorJam
ActuatorJam
NotConfigured
NotCalibrated
OutOfRange
UnsupportedProcedure | | + +### 6.6.4 Get Tilt + +**Table 6.6.4.1: Elementary procedure Get Tilt** + +| | | | | | +|-------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
GetTilt | | | | | +| Code:
0x34 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.6.4.2: Initiating message parameters and format for Get Tilt** + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +**Table 6.6.4.3: Response message parameters and format for Get Tilt** + +| Number | Length | Type | Description | +|--------|----------|----------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | +| 2 | 2 octets | Signed integer | Tilt value | + +#### Description: + +On receipt of the initiating message the secondary device shall return the current tilt value. + +The returned tilt value is given in the format specified in subclause 3.1. + +**Table 6.6.4.4: Return codes for Get Tilt** + +| OK | FAIL | Comment | +|----|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
NotCalibrated
NotConfigured
UnsupportedProcedure | HardwareError shall only be used, if error is detected in tilt detector. | + +### 6.6.5 Alarm Indication + +**Table 6.6.5.1: Elementary procedure Alarm Indication** + +| | | | | | +|---------------------------------|---------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AlarmIndication | | | | | +| Code:
0x07 | Issued by:
Secondary device | Procedure class:
2 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.6.5.2: Initiating message parameters and format for Alarm Indication** + +| Number | Length | Type | Description | +|---------|---------|------------------|----------------------------| +| 2 i - 1 | 1 octet | Unsigned integer | Return code i; see annex A | +| 2 i | 1 octet | Unsigned integer | State flag i | + +i = 1 ... N + +#### Description: + +The secondary device uses this procedure to report alarm state changes to the primary device. This procedure shall only be performed if the secondary has performed an AlarmSubscribe procedure since its latest reset. + +For each alarm, the current alarm state and alarm code shall be reported if and only if any change in its state has occurred during the period of time since the last reported state. An AlarmIndication procedure shall be performed if at least one alarm shall be reported. The first AlarmIndication procedure after the AlarmSubscribe procedure shall report the active alarms. + +Alarm state changes are considered as reported at the time the message is passed to the transport layer. + +State flag = 0 represents alarm state *cleared*. + +State flag = 1 represents alarm state *raised*. + +### 6.6.6 Set Device Data + +**Table 6.6.6.1: Elementary procedure Set Device Data** + +| | | | | | +|-------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
SetDeviceData | | | | | +| Code:
0x0E | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.6.6.2: Initiating message parameters and format for Set Device Data** + +| Number | Length | Type | Description | +|--------|-------------|------------------|---------------------------| +| 1 | 1 octet | Unsigned integer | Field number, see annex B | +| 2 | See annex B | See annex B | Data to write | + +**Table 6.6.6.3: Response message parameters and format for Set Device Data** + +| Number | Length | Type | Description | +|--------|---------|------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | + +#### Description: + +On receipt of the initiating message the secondary device shall write the data given in the parameters of the initiating message into the fields optionally provided for configuration data and listed in annex B of this TS. If an attempt is made to write to fields which are designated as read only, the return code *ReadOnly* is returned and the data for those fields is ignored. If an attempt is made to write to fields which are not supported by the device the return code *UnknownParameter* is returned and the data for those fields is ignored. + +**Table 6.6.6.4: Return codes for Set Device Data** + +| OK | FAIL | Comment | +|----|------------------------------------------------------------------------------------------------|---------| +| | FormatError
Busy
WorkingSoftwareMissing
HardwareError
ReadOnly
UnknownParameter | | + +### 6.6.7 Get Device Data + +**Table 6.6.7.1: Elementary procedure Get Device Data** + +| | | | | | +|-------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
GetDeviceData | | | | | +| Code:
0x0F | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.6.7.2: Initiating message parameters and format for Get Device Data** + +| Number | Length | Type | Description | +|--------|---------|------------------|---------------------------| +| 1 | 1 octet | Unsigned integer | Field number; see annex B | + +**Table 6.6.7.3: Response message parameters and format for Get Device Data** + +| Number | Length | Type | Description | +|--------|-------------|-------------|----------------| +| 1 | 1 octet | ReturnCode | Return code OK | +| 2 | See annex B | See annex B | Field value | + +#### **Description:** + +In this procedure the secondary device shall return the data stored in the field for configuration data specified by the field number in the procedure and listed in annex B of this TS. + +**Table 6.6.7.4: Return codes for Get Device Data** + +| OK | FAIL | Comment | +|----|-------------------------------------------------------------------|---------| +| | FormatError
Busy
WorkingSoftwareMissing
UnknownParameter | | + +## 6.7 Multi-antenna elementary procedures + +### 6.7.1 Antenna Calibrate + +**Table 6.7.1.1: Elementary procedure Antenna Calibrate** + +| | | | | | +|----------------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------| +| Name:
AntennaCalibrate | | | | | +| Code:
0x80 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
High | + +**Table 6.7.1.2: Initiating message parameters and format for Antenna Calibrate** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | + +**Table 6.7.1.3: Response message parameters and format for Antenna Calibrate** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | ReturnCode | Return code OK | + +#### **Description:** + +On receipt of the initiating message the secondary device shall perform a calibration of the antenna addressed by the antenna number. During calibration the actuator is driven through the whole tilt range of the antenna. + +The response time to this Antenna Calibrate procedure shall be less than 4 minutes. + +**Table 6.7.1.4: Return codes for Antenna Calibrate** + +| OK | FAIL | Comment | +|----|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
MotorJam
ActuatorJam
NotConfigured
UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. | + +### 6.7.2 Antenna Set Tilt + +**Table 6.7.2.1: Elementary procedure Antenna Set Tilt** + +| | | | | | +|--------------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------| +| Name:
AntennaSetTilt | | | | | +| Code:
0x81 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
High | + +**Table 6.7.2.2: Initiating message parameters and format for Antenna Set Tilt** + +| Number | Length | Type | Description | +|--------|----------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 2 octets | Signed integer | Tilt value | + +**Table 6.7.2.3: Response message parameters and format for Antenna Set Tilt** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | ReturnCode | Return code OK | + +#### Description: + +On receipt of the initiating message the secondary device shall set the electrical tilt of the antenna addressed by the antenna number in increments of $0.1^\circ$ . + +The secondary device shall respond to the initiating message in less than 2 minutes. + +The tilt value corresponding to the actual tilt angle shall not go outside of the range between the tilt value corresponding to the current tilt angle and the tilt value corresponding to the requested tilt angle by more than 5 during this operation. + +The format of the value of parameter 2 is given in subclause 3.1. + +**Table 6.7.2.4: Return codes for Antenna Set Tilt** + +| OK | FAIL | Comment | +|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
MotorJam
ActuatorJam
NotConfigured
NotCalibrated
OutOfRange
UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. | + +### 6.7.3 Antenna Get Tilt + +**Table 6.7.3.1: Elementary procedure Antenna Get Tilt** + +| | | | | | +|--------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AntennaGetTilt | | | | | +| Code:
0x82 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.7.3.2: Initiating message parameters and format for Antenna Get Tilt** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | + +**Table 6.7.3.3: Response message parameters and format for Antenna Get Tilt** + +| Number | Length | Type | Description | +|--------|----------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | ReturnCode | Return code OK | +| 3 | 2 octets | Signed integer | Tilt value | + +#### Description: + +On receipt of the initiating message the secondary device shall return the current tilt value of the antenna addressed by the antenna number. + +The returned tilt value is in the format specified in subclause 3.1. + +**Table 6.7.3.4: Return codes for Antenna Get Tilt** + +| OK | FAIL | Comment | +|----|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
NotConfigured
NotCalibrated
UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned.
HardwareError shall only be used, if an error is detected in tilt detector. | + +### 6.7.4 Antenna Set Device Data + +**Table 6.7.4.1: Elementary procedure Antenna Set Device Data** + +| | | | | | +|--------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AntennaSetDeviceData | | | | | +| Code:
0x83 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.7.4.2: Initiating message parameters and format for Antenna Set Device Data** + +| Number | Length | Type | Description | +|--------|-------------|------------------|---------------------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | Unsigned integer | Field number; see annex B | +| 3 | See annex B | See annex B | Data to write | + +**Table 6.7.4.3: Response message parameters and format for Antenna Set Device Data** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | ReturnCode | Return code OK | + +#### **Description:** + +On receipt of the initiating message the secondary device shall write the provided data for the antenna addressed by the antenna number into the fields optionally provided for configuration data and listed in annex B of this TS. If an attempt is made to write to fields which are designated as read only for the addressed antenna the return code ReadOnly is returned and the data for those fields is ignored. If an attempt is made to write to fields which are not supported for the addressed antenna the return code UnknownParameter is returned and the data for those fields is ignored. + +**Table 6.7.4.4: Return codes for Antenna Set Device Data** + +| OK | FAIL | Comment | +|----|------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
ReadOnly
UnknownParameter
UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. | + +### 6.7.5 Antenna Get Device Data + +**Table 6.7.5.1: Elementary procedure Antenna Get Device Data** + +| | | | | | +|--------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AntennaGetDeviceData | | | | | +| Code:
0x84 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.7.5.2: Initiating message parameters and format for Antenna Get Device Data** + +| Number | Length | Type | Description | +|--------|---------|------------------|-----------------------------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | Unsigned integer | Field number to read; see annex B | + +**Table 6.7.5.3: Response message parameters and format for Antenna Get Device Data** + +| Number | Length | Type | Description | +|--------|-------------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | ReturnCode | Return code OK | +| 3 | See annex B | See annex B | Field value | + +#### **Description:** + +On receipt of the initiating message the secondary device shall return the data stored for the addressed antenna in the field for configuration data specified by the field number in the initiating message and listed in annex B of this TS. + +Table 6.7.5.4: Return codes for Antenna Get Device Data + +| OK | FAIL | Comment | +|----|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| | FormatError
Busy
WorkingSoftwareMissing
UnsupportedProcedure
UnknownParameter | If the addressed antenna is not existing, FormatError is returned. | + +### 6.7.6 Antenna Alarm Indication + +Table 6.7.6.1: Elementary procedure Antenna Alarm Indication + +| | | | | | +|----------------------------------------|---------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AntennaAlarmIndication | | | | | +| Code:
0x85 | Issued by:
Secondary device | Procedure class:
2 | DownloadMode state:
No | Power mode:
Low | + +Table 6.7.6.2: Initiating message parameters and format for Antenna Alarm Indication + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 i | 1 octet | Unsigned integer | Return code i; see annex A | +| 2 i +1 | 1 octet | Unsigned integer | State flag i | + +i = 1 ... N + +#### Description: + +The multi-antenna secondary device uses this procedure to report antenna alarm state changes to the primary device. This procedure shall only be performed if the secondary has performed an AlarmSubscribe procedure since its latest reset. Multi-antenna devices shall use this AntennaAlarmIndication procedure only for multi-antenna specific alarms and the AlarmIndication procedure in subclause 6.6.5 for the other alarms. + +For each alarm, the current alarm state and alarm code shall be reported if and only if any change in its state has occurred during the period of time since the last reported state. An AntennaAlarmIndication procedure shall be performed if at least one multi-antenna specific alarm shall be reported. The first AntennaAlarmIndication procedure after the AlarmSubscribe procedure shall report the active alarms. + +Alarm state changes are considered as reported at the time the message is passed to the transport layer. + +State flag = 0 represents alarm state *cleared*. + +State flag = 1 represents alarm state *raised*. + +### 6.7.7 Antenna Clear Active Alarms + +Table 6.7.7.1: Elementary procedure Antenna Clear Active Alarms + +| | | | | | +|------------------------------------------|---------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AntennaClearActiveAlarms | | | | | +| Code:
0x86 | Issued by:
Secondary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +Table 6.7.7.2: Initiating message parameters and format for Antenna Clear Active Alarms + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | + +**Table 6.7.7.3: Response message parameters and format for Antenna Clear Active Alarms** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | ReturnCode | Return code OK | + +#### **Description:** + +On receipt of the initiating message the secondary device shall first clear all stored alarm information for the addressed antenna and then return a procedure response message. + +**Table 6.7.7.4: Return codes for Antenna Clear Active Alarms** + +| OK | FAIL | Comment | +|----|-----------------------------------------------------------------------|--------------------------------------------------------------------| +| | FormatError
Busy
WorkingSoftwareMissing
UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. | + +### 6.7.8 Antenna Get Alarm Status + +**Table 6.7.8.1: Elementary procedure Antenna Get Alarm Status** + +| | | | | | +|---------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AntennaGetAlarmStatus | | | | | +| Code:
0x87 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.7.8.2: Initiating message parameters and format for Antenna Get Alarm Status** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | + +**Table 6.7.8.3: Response message parameters and format for Antenna Get Alarm Status** + +| Number | Length | Type | Description | +|--------|---------|------------------|-----------------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | ReturnCode | Return code OK | +| i + 2 | 1 octet | AlarmCode | Active alarm number i | + +i = 1 ... N + +#### **Description:** + +On receipt of the initiating message the secondary device shall report the alarm codes of the active alarms for the addressed antenna. + +**Table 6.7.8.4: Return codes for Antenna Get Alarm Status** + +| OK | FAIL | Comment | +|-------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------| +| All return codes marked as used for alarms in Annex A | FormatError
WorkingSoftwareMissing
UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. | + +### 6.7.9 Antenna Get Number Of Antennas + +**Table 6.7.9.1: Elementary procedure Antenna Get Number Of Antennas** + +| | | | | | +|--------------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AntennaGetNumberOfAntennas | | | | | +| Code:
0x88 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.7.9.2: Initiating message parameters and format for Antenna Get Number Of Antennas** + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +**Table 6.7.9.3: Response message parameters and format for Antenna Get Number Of Antennas** + +| Number | Length | Type | Description | +|--------|---------|------------------|--------------------| +| 1 | 1 octet | ReturnCode | Return code OK | +| 2 | 1 octet | Unsigned integer | Number of antennas | + +#### Description: + +On receipt of the initiating message the secondary device shall return the number of antennas it controls. + +**Table 6.7.9.4: Return codes for Antenna Get Number Of Antennas** + +| OK | FAIL | Comment | +|----|---------------------------------------------------------------|---------| +| | FormatError
WorkingSoftwareMissing
UnsupportedProcedure | | + +### 6.7.10 Antenna Send Configuration Data + +**Table 6.7.10.1: Elementary procedure Antenna Send Configuration Data** + +| | | | | | +|----------------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------| +| Name:
AntennaSendConfigurationData | | | | | +| Code:
0x89 | Issued by:
Primary device | Procedure class:
1 | DownloadMode state:
No | Power mode:
Low | + +**Table 6.7.10.2: Initiating message parameters and format for Antenna Send Configuration Data** + +| Number | Length | Type | Description | +|--------|-----------------------------------------------------|------------------|--------------------| +| 1 | 1 octet | Unsigned Integer | Antenna number | +| 2 | Less than, or equal to MaxDataReceiveLength minus 1 | Vendor specific | Configuration data | + +**Table 6.7.10.3: Response message parameters and format for Antenna Send Configuration Data** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Antenna number | +| 2 | 1 octet | ReturnCode | Return code OK | + +#### Description: + +On receipt of the initiating message the secondary device shall store the provided vendor and antenna specific configuration data for the relationship between the movement of the drive system and the beam tilt position of the addressed antenna. + +If the configuration data exceeds MaxDataReceiveLength minus 1, the data shall be split into a number of MaxDataReceiveLength minus 1 segments and one final segment with whatever is left. The primary device transmits the segments in order. The layer 2 sequence numbers guarantee that no segment will be lost or received out of order. + +**Table 6.7.10.4: Return codes for Antenna Send Configuration Data** + +| OK | FAIL | Comment | +|----|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
ChecksumError
InvalidFileContent
UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. | + +## 6.8 TMAAP Elementary procedures for TMA + +### 6.8.1 TMA Set Mode + +The TMA Set Mode procedure shall only be supported if the TMA subunit can be set in bypass mode. On receipt of the initiating message, the secondary device shall first set the TMA subunit in the appropriate mode as indicated by the mode state flag, and then return a response message. If a TMA subunit in bypass mode receives the elementary procedure TMASetMode to Bypass, the TMA subunit shall remain in the Bypass mode and the response OK shall be returned. + +Mode state flag = 0 represents *Normal mode*. + +Mode state flag = 1 represents *Bypass mode*. + +**Table 6.8.1.1: Elementary procedure TMA Set Mode** + +| Name: TMA Set Mode | | | | | +|--------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x70 | Primary device | 1 | No | n/a | + +**Table 6.8.1.2: Initiating message parameters and format TMA Set Mode** + +| Number | Length | Type | Description | +|--------|---------|------------------|-----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | Unsigned integer | Mode state flag | + +**Table 6.8.1.3: Response message parameters and format for TMA Set Mode** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | ReturnCode | Return code OK | + +**Table 6.8.1.4: Return codes for TMA Set Mode** + +| OK | FAIL | Comment | +|----|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | FormatError | | +| | Busy | | +| | HardwareError | HardwareError shall refer to a detected inability to switch mode. | +| | WorkingSoftwareMissing | | +| | UnsupportedProcedure | UnsupportedProcedure shall be returned if set mode is not supported by the TMA subunit. | +| | OutOfRange | OutOfRange shall be returned if the mode state flag has another value than those listed in the procedure description. | +| | MajorTMAFault | MajorTMAFault shall be returned if the TMA subunit is in bypass mode due to a major TMA fault and TMASetMode to Normal is received and not possible to set. | +| | MinorTMAFault | MinorTMAFault shall be returned if the TMA subunit is in bypass mode due to a minor TMA fault and TMASetMode to Normal is received and not possible to set. | + +### 6.8.2 TMA Get Mode + +On receipt of the initiating message, the secondary device shall respond with the mode state flag indicating whether the TMA subunit is in normal mode or in bypass mode. TMA subunits which do not support bypass mode shall return Normal mode. + +Mode state flag = 0x00 represents *Normal mode*. + +Mode state flag = 0x01 represents *Bypass mode*. + +**Table 6.8.2.1: Elementary procedure TMA Get Mode** + +| | | | | | +|--------------------|-------------------|-------------------------|----------------------------|--------------------| +| Name: TMA Get Mode | | | | | +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x71 | Primary device | 1 | No | n/a | + +**Table 6.8.2.2: Initiating message parameters and format for TMA Get Mode** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | + +**Table 6.8.2.3: Response message parameters and format for TMA Get Mode** + +| Number | Length | Type | Description | +|--------|---------|------------------|-----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | ReturnCode | Return code OK | +| 3 | 1 octet | Unsigned integer | Mode state flag | + +**Table 6.8.2.4: Return codes TMA Get Mode** + +| OK | FAIL | Comment | +|----|-----------------------------------------------|---------| +| | FormatError
Busy
WorkingSoftwareMissing | | + +### 6.8.3 TMA Get Supported Functions + +On receipt of the initiating message, the secondary device shall respond with the function flags and parameters indicating the supported functionality of the addressed TMA subunit. + +**Table 6.8.3.1: Elementary procedure TMAGetSupportedFunctions** + +| Name: TMA Get Supported Functions | | | | | +|-----------------------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x7A | Primary device | 1 | No | n/a | + +**Table 6.8.3.2: Initiating message parameters and format for TMAGetSupportedFunctions** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | + +**Table 6.8.3.3: Response message parameters and format for TMAGetSupportedFunctions** + +| Number | Length | Type | Description | +|--------|---------|------------------|-------------------------------------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | ReturnCode | Return code OK | +| 3 | 1 octet | Unsigned integer | Function flags | +| 4 | 1 octet | Unsigned integer | Min Gain capability (expressed in dB/4) | +| 5 | 1 octet | Unsigned integer | Max Gain capability (expressed in dB/4) | +| 6 | 1 octet | Unsigned integer | Resolution capability (expressed in dB/4) | + +#### **Description:** + +1. A fixed gain TMA subunit shall have min and max gain as the same value. +2. If the resolution is zero, then non linear gain steps are supported (e.g. 3dB and 6dB and 12dB). + +NOTE: These parameters represent absolute fixed physical data. Any change of the corresponding parameter in the additional data will not have any operational impact on the TMA. + +**Table 6.8.3.4: Return codes TMAGetSupportedFunctions** + +| OK | FAIL | Comment | +|----|-----------------------------------------------|---------| +| | FormatError
Busy
WorkingSoftwareMissing | | + +Function flags: + +| Bit | 7 to 1 | 0 | +|----------|--------|-------------| +| Function | Spare | Bypass Mode | + +- Bits are numbered from 0....7, bit number 0 set to 1 represents the value 0x01 +- Bit value 0 represents function is not supported +- Bit value 1 represents function is supported +- Spare bits shall be set to 0 + +### 6.8.4 TMA Set Gain + +The procedure TMASetGain shall only be supported if the TMA subunit gain can be adjusted. On receipt of the initiating message, the secondary device shall first set the addressed TMA subunit to the gain determined by the TMA + +gain figure parameter, and then return the response message. The TMA gain figure parameter is calculated as 4 times the required gain expressed in dB. (This method of specification allows the gain to be set with a resolution of 0.25 dB while using an integer parameter.) + +If the TMA subunit is set in bypass mode by TMASetMode, and TMASetGain is received, then the procedure shall be performed and bypass mode shall be retained. + +If any alarm state flag is set than the status has to be validated and the result has to be responded. + +Gain shall be accepted if $G_{min} \leq G_{demanded} \leq G_{max}$ + +For linear steps: $G_{demanded} = (G_{min} + n * G_{resolution})$ where n is a non-negative integer + +For non-linear steps: $G_{demanded}$ must be equal to a supported value. + +$G_{min}$ , $G_{max}$ and $G_{resolution}$ are reported by TMAGetSupportedFunctions. The supported values for non-linear steps are reported by TMAGetSupportedNonLinearGainValues. + +For all other values of $G_{demanded}$ , the TMA subunit shall respond UnsupportedValue. + +**Table 6.8.4.1: Elementary procedure TMA Set Gain** + +| Name: TMA Set Gain | | | | | +|--------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x72 | Primary device | 1 | No | n/a | + +**Table 6.8.4.2: Initiating message parameters and format TMA Set Gain** + +| Number | Length | Type | Description | +|--------|---------|------------------|-----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | Unsigned integer | TMA gain figure | + +**Table 6.8.4.3: Response message parameters and format for TMA Set Gain** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | ReturnCode | Return code OK | + +**Table 6.8.4.4: Return codes for TMA Set Gain** + +| OK | FAIL | Comment | +|----|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| | FormatError | | +| | Busy | | +| | HardwareError | HardwareError shall refer to the detected inability to set the gain according to the instruction, although it is within the TMA gain adjustment range. | +| | WorkingSoftwareMissing | | +| | UnsupportedProcedure | UnsupportedProcedure shall be returned if gain adjustment is not supported by the TMA subunit. | +| | UnsupportedValue | The requested value is not supported. | +| | MajorTMAFault | | +| | MinorTMAFault | | + +### 6.8.5 TMA Get Gain + +On receipt of the initiating message, the secondary device shall return the set gain of the TMA subunit. Fixed gain TMA subunits shall return their fixed gain value. The TMA gain figure is calculated as 4 times the set gain expressed in dB. + +**Table 6.8.5.1: Elementary procedure TMA Get Gain** + +| Name: TMA Get Gain | | | | | +|--------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x73 | Primary device | 1 | No | n/a | + +**Table 6.8.5.2: Initiating message parameters and format TMA Get Gain** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | + +**Table 6.8.5.3: Response message parameters and format for TMA Get Gain** + +| Number | Length | Type | Description | +|--------|---------|------------------|-----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | Return Code | Return code OK | +| 3 | 1 octet | Unsigned integer | TMA gain figure | + +**Table 6.8.5.4: Return codes for TMA Get Gain** + +| OK | FAIL | Comment | +|----|------------------------|--------------------------------------------------------------------------------------------------| +| | FormatError | | +| | Busy | | +| | WorkingSoftwareMissing | | +| | MajorTMAFault | | +| | MinorTMAFault | | +| | BypassMode | BypassMode shall be returned if the TMA subunit is in bypass mode due to a TMASetMode procedure. | + +### 6.8.6 TMA Set Device Data + +On receipt of the initiating message the secondary device shall first write the provided data for the TMA subunit addressed by the subunit number into the fields provided for device data (and listed in Annex C of this document) and then return the response message. If an attempt is made to write to a field which is implemented as read only for the addressed TMA subunit, the return code *ReadOnly* is returned and the data for that field is ignored. If an attempt is made to write to a field which is not supported for the addressed TMA subunit the return code *UnknownParameter* is returned and the data for that field is ignored. + +**Table 6.8.6.1: Elementary procedure TMA Set Device Data** + +| Name: TMASetDeviceData | | | | | +|------------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x74 | Primary device | 1 | No | n/a | + +**Table 6.8.6.2: Initiating message parameters and format for TMA Set Device Data** + +| Number | Length | Type | Description | +|--------|-------------|------------------|---------------------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | Unsigned integer | Field number; see annex C | +| 3 | See annex C | See annex C | Data to write | + +**Table 6.8.6.3: Response message parameters and format for TMA Set Device Data** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | ReturnCode | Return code OK | + +**Table 6.8.6.4: Return codes for TMA Set Device Data** + +| OK | FAIL | Comment | +|----|------------------------------------------------------------------------------------------------|---------| +| | FormatError
Busy
HardwareError
WorkingSoftwareMissing
ReadOnly
UnknownParameter | | + +### 6.8.7 TMA Get Device Data + +On receipt of the initiating message the secondary device shall return the data stored for the addressed TMA subunit in the field for additional device data specified by the field number in the initiating message and listed in Annex C of this document. + +**Table 6.8.7.1: Elementary procedure TMA Get Device Data** + +| Name: TMAGetDeviceData | | | | | +|------------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x75 | Primary device | 1 | No | n/a | + +**Table 6.8.7.2: Initiating message parameters and format for TMA Get Device Data** + +| Number | Length | Type | Description | +|--------|---------|------------------|--------------------------------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | Unsigned integer | Field number to be read; see Annex C | + +**Table 6.8.7.3: Response message parameters and format for TMA Get Device Data** + +| Number | Length | Type | Description | +|--------|-------------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | Return Code | Return code OK | +| 3 | See Annex C | See Annex C | Field value | + +**Table 6.8.7.4: Return codes for TMA Get Device Data** + +| OK | FAIL | Comment | +|----|-------------------------------------------------------------------|---------| +| | FormatError
Busy
WorkingSoftwareMissing
UnknownParameter | | + +### 6.8.8 TMA Alarm Indication + +TMAs use this procedure to report TMA alarm state changes to the primary device. This procedure shall only be performed if the TMA has performed an AlarmSubscribe procedure since its latest reset. + +**Table 6.8.8.1: Elementary procedure TMA Alarm Indication** + +| Name: TMAAlarmIndication | | | | | +|--------------------------|------------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x76 | Secondary device | 2 | No | n/a | + +**Table 6.8.8.2: Initiating message parameters and format for TMA Alarm Indication** + +| Number | Length | Type | Description | +|-----------|---------|------------------|----------------------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| $2^i$ | 1 octet | Unsigned integer | Return code i; see Annex A | +| $2^i + 1$ | 1 octet | Unsigned integer | State flag i | + +$i = 1 \dots N$ + +#### 6.8.8.1 Further requirements + +For each alarm, the current alarm state and alarm code shall be reported if and only if any change in its state has occurred since the last reported state. + +A TMA Alarm Indication procedure shall be performed if at least one TMA alarm shall be reported for the TMA subunit. The first TMA Alarm Indication procedure after the Alarm Subscribe procedure shall report the active alarms. + +Alarm state changes are considered as reported at the time the message is passed to the transport layer. + +State flag = 0x00 represents alarm state *cleared*. + +State flag = 0x01 represents alarm state *raised*. + +### 6.8.9 TMA Clear Active Alarms + +On receipt of the initiating message the secondary device shall first clear all stored alarm information for the addressed TMA subunit and then return a procedure response message. In the event that the cause of the alarm persists the alarm shall be re-raised and a new TMA Alarm Indication procedure shall be performed. + +**Table 6.8.9.1: Elementary procedure TMA Clear Active Alarms** + +| Name: TMAClearActiveAlarms | | | | | +|----------------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by | Procedure class: | DownloadMode state: | Power mode: | +| 0x77 | Primary device | 1 | No | n/a | + +**Table 6.8.9.2: Initiating message parameters and format for TMA Clear Active Alarms** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | + +**Table 6.8.9.3: Response message parameters and format for TMA Clear Active Alarms** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | ReturnCode | Return code OK | + +**Table 6.8.9.4: Return codes for TMA Clear Active Alarms** + +| OK | FAIL | Comment | +|----|-----------------------------------------------|---------| +| | FormatError
Busy
WorkingSoftwareMissing | | + +### 6.8.10 TMA Get Alarm Status + +On receipt of the initiating message the secondary device shall report the alarm codes of the active alarms for the addressed TMA subunit. + +**Table 6.8.10.1: Elementary procedure TMA Get Alarm Status** + +| Name: TMAGetAlarmStatus | | | | | +|-------------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x78 | Primary device | 1 | No | n/a | + +**Table 6.8.10.2: Initiating message parameters and format for TMA Get Alarm Status** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | + +**Table 6.8.10.3: Response message parameters and format for TMA Get Alarm Status** + +| Number | Length | Type | Description | +|--------|---------|------------------|-------------------------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | ReturnCode | Return code OK | +| 2 + i | 1 octet | AlarmCode | Alarm code for alarm number i | + +i = 1 ... N + +**Table 6.8.10.4: Return codes for TMA Get Alarm Status** + +| OK | FAIL | Comment | +|-------------------------------------------------------|-----------------------------------------------|---------| +| All return codes marked as used for alarms in Annex A | FormatError
Busy
WorkingSoftwareMissing | | + +### 6.8.11 TMA Get Number of Subunits + +On receipt of the initiating message the secondary device shall return the number of subunits it controls. + +**Table 6.8.11.1: Elementary procedure TMAGetNumberOfSubunits** + +| Name: TMAGetNumberOfSubunits | | | | | +|------------------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x79 | Primary device | 1 | No | n/a | + +**Table 6.8.11.2: Initiating message parameters and format for TMAGetNumberOfSubunits** + +| Number | Length | Type | Description | +|--------|----------|------|-----------------| +| None | 0 octets | None | No data carried | + +**Table 6.8.11.3: Response message parameters and format for TMAGetNumberOfSubunits** + +| Number | Length | Type | Description | +|--------|---------|------------------|--------------------| +| 1 | 1 octet | ReturnCode | Return code OK | +| 2 | 1 octet | Unsigned integer | Number of subunits | + +**Table 6.8.11.4: Return codes for TMAGetNumberOfSubunits** + +| OK | FAIL | Comment | +|----|-----------------------------------------------|---------| +| | FormatError
Busy
WorkingSoftwareMissing | | + +### 6.8.12 3GPP Clear Active Alarms and Get Alarm Status + +When an TMA receives ClearActiveAlarms, it shall perform the procedure for all subunits of the TMA and then return a single procedure response message. + +When an TMA receives GetAlarmStatus, it shall in a single procedure response message report the union of the alarm codes of all active alarms for all subunits, i.e. the same alarm codes shall be reported only once. + +### 6.8.13 TMA Get Supported Non-Linear Gain Values + +On receipt of the initiating message, the secondary device shall respond with a message containing a list of supported values in numerical order, preceded by the number (N) of such values contained in the list. + +**Table 6.8.13.1: Elementary procedure TMAGetSupportedNonLinearGainValues** + +| Name: TMAGetSupportedNonLinearGainValues | | | | | +|------------------------------------------|----------------|------------------|---------------------|-------------| +| Code: | Issued by: | Procedure class: | DownloadMode state: | Power mode: | +| 0x7B | Primary device | 1 | No | n/a | + +**Table 6.8.13.2: Initiating message parameters and format for TMAGetSupportedNonLinearGainValues** + +| Number | Length | Type | Description | +|--------|---------|------------------|----------------| +| 1 | 1 octet | Unsigned integer | Subunit number | + +**Table 6.8.13.3: Response message parameters and format for TMAGetSupportedNonLinearGainValues** + +| Number | Length | Type | Description | +|--------|---------|------------------|--------------------------------------------------------------| +| 1 | 1 octet | Unsigned integer | Subunit number | +| 2 | 1 octet | ReturnCode | Return code OK | +| 3 | 1 octet | Unsigned integer | Number of non linear gain values supported (N) | +| 3 + i | 1 octet | Unsigned integer | Non linear gain supported value number i (expressed in dB/4) | + +i=1 .. N + +**Table 6.8.13.4: Return codes TMAGetSupportedNonLinearGainValues** + +| OK | FAIL | Comment | +|----|------------------------|------------------------------------------------------------------------------------------| +| | FormatError | | +| | Busy | | +| | WorkingSoftwareMissing | | +| | UnsupportedProcedure | UnsupportedProcedure shall be returned if the TMA does not support non-linear gain steps | + +# --- 7 Unknown elementary procedures + +Void. + +# Annex A (normative): Return codes for secondary devices + +**Table A.1: Return Codes for Secondary Devices** + +| Code | Name | Comment | Alarm | DownloadMode state | +|------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------| +| 0x00 | OK | Normal response | | X | +| 0x02 | Motor Jam | Motor cannot move | X | | +| 0x03 | ActuatorJam | Actuator jam has been detected. No movement of the actuator, but movement of the motor was detected | X | | +| 0x05 | Busy | The device is busy and cannot execute the procedure until an ongoing activity is completed | | | +| 0x06 | ChecksumError | Checksum incorrect for otherwise valid data.. | | | +| 0x0B | FAIL | Abnormal response. Indicates that a procedure has not been executed successfully | | X | +| 0x0E | NotCalibrated | The device has not completed a calibration operation, or calibration has been lost | X | | +| 0x0F | NotConfigured | Actuator configuration data is missing | X | | +| 0x11 | HardwareError | Any hardware error which cannot be classified. May not be reported as an alarm until the fault is likely to be persistent | X | X | +| 0x13 | OutOfRange | A parameter given by an operator (e.g. tilt value or memory offset) is out of range | | | +| 0x19 | UnknownProcedure | Received procedure code is not defined | | X | +| 0x1D | ReadOnly | Invalid device data parameter usage | | X | +| 0x1E | UnknownParameter | Specified parameter is not supported for the used procedure | | X | +| 0x21 | WorkingSoftwareMissing | The unit is inDownloadMode state. Returned upon unsupported procedure when in DownloadMode state | | X | +| 0x22 | InvalidFileContent | The data being downloaded is detected to be of wrong format or size | | X | +| 0x24 | FormatError | Procedure message is inconsistent or if an addressed field or antenna is invalid or the data parameter field length is inconsistent with the corresponding field length parameter | | X | +| 0x25 | UnsupportedProcedure | The procedure is optional and not supported or the procedure does not apply to this device type | | | +| 0x26 | InvalidProcedureSequence | Procedure sequence as described in annex C is expected but not experienced by the secondary device | | | +| 0x27 | ActuatorInterference | An actuator movement outside the control of the RET unit has been detected. Probable cause is manual interference | X | | +| 0x1A | MinorTMAFault | A fault in the TMA subunit is detected which reduces the gain performance but maintains its function. | x | | +| 0x1B | MajorTMAFault | A fault in the TMA subunit is detected. The fault prevents the function of the TMA subunit. | x | | +| 0x1C | UnsupportedValue | The requested value is not supported. | | | +| 0x1F | BypassMode | The TMA subunit is in bypass mode and cannot report a correct gain value. | x | | + +NOTE: A TMA subunit with a fault which is causing it to switch to bypass mode will report both the fault and the BypassMode alarm. + +# Annex B (normative): Assigned fields for additional data + +The following standard fields have no operational impact and are used by the procedures SetDeviceData, GetDeviceData, AntennaSetDeviceData and AntennaGetDeviceData. Little endian order is used for storage of multiple-octet numbers. Where ASCII variables are shorter than the assigned field lengths the characters are right aligned and leading blanks are filled with null characters (0x00). Unused or not initialized parameter shall return the value 0x00 for the GetDeviceData, AntennaGetDeviceData and TMAGetDeviceData procedure. + +**Table B.1: Assigned fields for additional data of RETAP** + +| Field No. | Length (octets) | Format | Description | +|-----------|-----------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0x01 | 15 | ASCII | Antenna model number | +| 0x02 | 17 | ASCII | Antenna serial number | +| 0x03 | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x08 | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x09 | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x0A | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x0B | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x04 | 8 | 4 x 16-bit unsigned | Beamwidth for each operating band in band order (deg), beginning with lowest band. The lowest band is transmitted within the first 16-bit value.
Not supported in this release | +| 0x05 | 4 | 4 x 8-bit unsigned | Gain [dBi] for each operating band in band order, expressed in gain value times 10, beginning with the lowest band. The lowest band is transmitted within the first 8-bit value
Not supported in this release | +| 0x06 | 2 | 16-bit signed | Maximum supported electrical tilt [degree], expressed in tilt value times 10, format as in subclause 3.1 | +| 0x07 | 2 | 16-bit signed | Minimum supported electrical tilt [degree], expressed in tilt value times 10, format as in subclause 3.1 | +| 0x21 | 6 | ASCII | Installation date | +| 0x22 | 5 | ASCII | Installer's ID | +| 0x23 | 32 | ASCII | Base station ID | +| 0x24 | 32 | ASCII | Sector ID | +| 0x25 | 2 | 16-bit unsigned | Antenna bearing [degree], in the range of 0 – 359,9 degree, expressed as bearing value times 10 | +| 0x26 | 2 | 16-bit signed | Installed mechanical tilt [degree], expressed in tilt value times 10, format as in subclause 3.1 | + +**Table B.2: Void** + +**Table B.2-1: Void** + +**Table B.2-2: Void** + +**Table B.2-3: Void** + +**Table B.2-4: Void** + +The operating bands are defined in subclause 4.3.7 in TS 37.461 [4], an example of operating bands coding is provided in Annex F. + +**Table B.3: Assigned fields for additional data of TMAAP** + +| Field No. | Length (octets) | Format | Description | +|-----------|-----------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0x01 | 15 | ASCII | Antenna model number | +| 0x02 | 17 | ASCII | Antenna serial number | +| 0x03 | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x08 | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x09 | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x0A | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x0B | 2 | 16-bit unsigned | Antenna operating band(s): Not supported in this release | +| 0x04 | 8 | 4 x 16-bit unsigned | Beamwidth for each operating band in band order (deg) beginning with lowest band. The lowest band is transmitted within the first 16-bit value. Not supported in this release | +| 0x05 | 4 | 4 x 8-bit unsigned | Gain [dBi] for each operating band in band order, expressed in gain value times 10, beginning with the lowest band. The lowest band is transmitted within the first 8-bit value. Not supported in this release | +| 0x21 | 6 | ASCII | Installation date | +| 0x22 | 5 | ASCII | Installer's ID | +| 0x23 | 32 | ASCII | Base station ID | +| 0x24 | 32 | ASCII | Sector ID | +| 0x25 | 2 | 16-bit unsigned | Antenna bearing | +| 0x26 | 2 | 16-bit signed | Installed mechanical tilt (degrees * 10) | +| 0x13 | 1 | 8-bit unsigned | TMA subunit type (see table B.4) | +| 0x14 | 4 | 2x16-bit unsigned integer | TMA subunit receive frequency band (see Table B.5) | +| 0x15 | 4 | 2x16-bit unsigned integer | TMA subunit transmit frequency band (see Table B.5) | +| 0x16 | 1 | Unsigned integer | Maximum supported gain given as gain figure expressed in dB/4 | +| 0x17 | 1 | Unsigned integer | Minimum supported gain given as gain figure expressed in dB/4 | +| 0x18 | 1 | Unsigned integer | Gain resolution given as the gain resolution figure expressed in dB/4 | + +**Table B.4: Field 0x13 interpretation** + +| Bit number | 7... 2 | 1 | 0 | +|------------------|--------|-----------------------|--------| +| TMA subunit type | Spare | Reserved for AISG use | Bypass | + +Bits are numbered from 0...7, bit numbered 0 set to 1 represents the value 0x01. + +Bit value 0 represents TMA subunit type is not supported. + +Bit value 1 represents TMA subunit type is supported. + +Spare bits and Bit 1 shall be set to 0. + +Example: 0000 0001 = Bypass + +**Table B.5: Field 0x14 and 0x15 interpretation** + +| Octet number | Description | +|--------------|-----------------| +| 0 | fmin low octet | +| 1 | fmin high octet | +| 2 | fmax low octet | +| 3 | fmax high octet | + +fmin and fmax are expressed in 100kHz steps from 0kHz. + +Example: For 850MHz, low octet = 0x34, high octet = 0x21. + +## Annex C (normative): Procedure sequence for download of software to a secondary device + +![Sequence diagram showing the procedure for software download between a Primary Device and a Secondary Device.](0f1767577a073167eb9628d72034e083_img.jpg) + +``` +sequenceDiagram + participant Primary Device + participant Secondary Device + Note left of Primary Device: Repeat until all application software is downloaded + Primary Device->>Secondary Device: DownloadStart + Secondary Device-->>Primary Device: Response: DownloadStart + Primary Device->>Secondary Device: DownloadApplication + Secondary Device-->>Primary Device: Response: DownloadApplication + Primary Device->>Secondary Device: DownloadEnd + Secondary Device-->>Primary Device: Response: DownloadEnd +``` + +The diagram illustrates a sequence of messages between a Primary Device and a Secondary Device for a software download. The sequence starts with the Primary Device sending a **DownloadStart** message to the Secondary Device. The Secondary Device responds with **Response: DownloadStart**. Next, the Primary Device sends a **DownloadApplication** message, which is responded to by **Response: DownloadApplication**. A loop indicated by a box on the left labeled "Repeat until all application software is downloaded" encompasses these two steps. Finally, the Primary Device sends a **DownloadEnd** message, which is responded to by **Response: DownloadEnd**. + +Sequence diagram showing the procedure for software download between a Primary Device and a Secondary Device. + +Figure C.1: Procedure sequence for Software Download + +The erasure of the secondary device application software shall not be done before the reception of the Download Application message. The data content of the Download Application message is implementation specific but it is recommended to support an application software validity feature that shall minimise the risk of downloading faulty or invalid application software. + +# Annex D (informative): Overview of elementary procedures + +**Table D.1: Elementary Procedures and Procedure Codes** + +| Elementary Procedure | Procedure Code | Issued by | DownloadMode state | +|-----------------------------------------------------|----------------|------------------|--------------------| +| Common Procedure Set | | | | +| (Reserved) | 0x01 | | | +| Reset Software | 0x03 | primary device | Yes | +| Get Alarm Status | 0x04 | primary device | No | +| Get Information | 0x05 | primary device | Yes | +| Clear Active Alarms | 0x06 | primary device | No | +| Read User Data | 0x10 | primary device | No | +| Write User Data | 0x11 | primary device | No | +| Alarm Subscribe | 0x12 | primary device | No | +| Self Test | 0x0A | primary device | No | +| Download Start | 0x40 | primary device | Yes | +| Download Application | 0x41 | primary device | Yes | +| Download End | 0x42 | primary device | Yes | +| Vendor Specific Procedure | 0x90 | primary device | Vendor specific | +| RETAP Single-Antenna Procedure Set | | | | +| Set Device Data | 0x0E | primary device | No | +| Get Device Data | 0x0F | primary device | No | +| Calibrate | 0x31 | primary device | No | +| Send Configuration Data | 0x32 | primary device | No | +| Set Tilt | 0x33 | primary device | No | +| Get Tilt | 0x34 | primary device | No | +| Alarm Indication | 0x07 | secondary device | No | +| RETAP Multi-Antenna Procedure Set | | | | +| Antenna Calibrate | 0x80 | primary device | No | +| Antenna Send Configuration Data | 0x89 | primary device | No | +| Antenna Set Tilt | 0x81 | primary device | No | +| Antenna Get Tilt | 0x82 | primary device | No | +| Antenna Set Device Data | 0x83 | primary device | No | +| Antenna Get Device Data | 0x84 | primary device | No | +| Antenna Alarm Indication | 0x85 | secondary device | No | +| Antenna Clear Active Alarms | 0x86 | primary device | No | +| Antenna Get Alarm Status | 0x87 | primary device | No | +| Antenna Get Number of Antennas | 0x88 | primary device | No | +| TMAAP Procedure Set for multi and single TMA | | | | +| TMASetMode | 0x70 | primary device | No | +| TMAGetMode | 0x71 | primary device | No | +| TMAGetSupportedFunctions | 0x7A | primary device | No | +| TMASetGain | 0x72 | primary device | No | +| TMAGetGain | 0x73 | primary device | No | +| TMASetDeviceData | 0x74 | primary device | No | +| TMAGetDeviceData | 0x75 | primary device | No | +| TMAAlarmIndication | 0x76 | secondary device | No | +| TMAClearActiveAlarms | 0x77 | primary device | No | +| TMAGetAlarmStatus | 0x78 | primary device | No | +| TMAGetNumberOfSubunits | 0x79 | primary device | No | +| TMAGetSupportedNonLinearGainValues | 0x7B | primary device | No | + +NOTE: The notion "yes" in the DownloadMode state column indicates that the listed procedures are mandatory if the DownloadMode state can be entered by the secondary device. + + + +# Annex E (informative): I-frame and INFO-field format + +The I-frame and INFO-field formats for both primary and secondary stations are illustrated. To transfer elementary procedures, the INFO-field of the I-frame is used. + +**Table E.1: HDLC-Frame:** + +| Flag
1 octet | ADR
1 octet | Control
1 octet | INFO
N octets | CRC
2 octets | | Flag
1 octet | +|-----------------|----------------|--------------------|--------------------------------------------------------------------------|-------------------|--------------------|-----------------| +| 0x7E | Device Address | Control bits | Variable length
(must support a maximum length of at least 74 octets) | CRC1
Low Octet | CRC2
high octet | 0x7E | + +Image: Diagram showing the INFO field structure. A dashed line connects the INFO field of the HDLC-Frame table to this table, indicating that the INFO field contains the procedure ID and data octets. + +| Procedure ID | Number of data octets | | Data octets | +|--------------|-----------------------|------------|--------------------------------------------------------------------------| +| 1 octet | low octet | high octet | Variable length
(must support a maximum length of at least 71 octets) | + +## Format of the I-Frame and INFO Field + +Devices shall support the following data length: + +Mandatory: $0 \leq \text{data octets} \leq 71$ + +Optional: $0 \leq \text{data octets} < 65,536 \text{ octets}$ + +## Annex F (Informative): Assigned fields for additional data coding for operating bands + +NOTE: This Annex is not updated in Rel-16 and onwards. + +**Table F.1: Band related fields for additional data of RETAP** + +| Field No. | Length (octets) | Format | Description | +|-----------|-----------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0x03 | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2 below | +| 0x08 | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2-1 below | +| 0x09 | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2-2 below | +| 0x0A | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2-3 below | +| 0x0B | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2-4 below | +| 0x04 | 8 | 4 x 16-bit unsigned | Beamwidth for each operating band in band order (deg), beginning with lowest band. The lowest band is transmitted within the first 16-bit value.
(example: width for band I, width for band III) | +| 0x05 | 4 | 4 x 8-bit unsigned | Gain [dBi] for each operating band in band order , expressed in gain value times 10, beginning with the lowest band. The lowest band is transmitted within the first 8-bit value
(example: gain for band I, gain for band III) | + +**Table F.2: Coding for operating bands in field 0x03** + +| Bit no | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-----------------------|---------|---------|-----|------|-----|----|----|----|------|-----|---|----|-----|----|---|----| +| Operating band UTRA | Ext. 09 | Ext. 08 | XIV | XIII | XII | XI | X | IX | VIII | VII | I | II | III | IV | V | VI | +| Operating band E-UTRA | Ext. 09 | Ext. 08 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 1 | 2 | 3 | 4 | 5 | 6 | + +Bit 14 set to "1" indicates that field 0x08 is defined. + +Bit 15 set to "1" indicates that field 0x09 is defined. + +**Table F.2-1: Coding for operating bands in field 0x08** + +| Bit no | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-----------------------|----|----|----|----|------|-----|----|----|------|-----|----|-----|-------|------|------|------| +| Operating band UTRA | - | - | - | - | XXVI | XXV | - | - | XXII | XXI | XX | XIX | XVIII | XVII | Res. | Res. | +| Operating band E-UTRA | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | Res. | Res. | + +**Table F.2-2: Coding for operating bands in field 0x09** + +| Bit no | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-----------------------|--------|----|-------|----|----|----|----|----|----|----|----|----|------|------|------|------| +| Operating band UTRA | Ext 0A | - | XXXII | - | - | - | - | - | e | f | d | c | b)36 | b)35 | a)34 | a)33 | +| Operating band E-UTRA | Ext 0A | 65 | 32 | 31 | 44 | 43 | 42 | 41 | 40 | 39 | 38 | 37 | 36 | 35 | 34 | 33 | + +Bit 15 set to "1" indicates that field 0x0A is defined. + +**Table F.2-3: Coding for operating bands in field 0x0A** + +| Bit no | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-----------------------|--------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| Operating band UTRA | Ext 0B | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | +| Operating band E-UTRA | Ext 0B | 75 | 74 | 72 | 71 | 49 | 51 | 50 | 48 | 69 | 70 | 46 | 68 | 45 | 67 | 66 | + +Bit 15 set to "1" indicates that field 0x0B is defined. + +**Table F.2-4: Coding for operating bands in field 0x0B** + +| Bit no | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-----------------------|------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|----|----|----|----| +| Operating band UTRA | Res. | Spare | Spare | Spare | Spare | Spare | Spare | Spare | Spare | Spare | Spare | Spare | - | - | - | - | +| Operating band E-UTRA | Res. | Spare | Spare | Spare | Spare | Spare | Spare | Spare | Spare | Spare | Spare | Spare | 85 | 52 | 73 | 76 | + +The operating bands are defined in subclause 4.3.7 in TS 37.461 [4]. In Table F.2-2, the notation a)33 is equivalent to E-UTRA band 33. + +Bits are numbered from 0 to 15, bit no 0 set=1 represents the value 0x0001. + +Bit set=1 represents operating band is supported. + +Bit set=0 represents operating band is not supported. + +Spare bits shall be set=0. + +Unused Beamwidth and Gain octets shall be set to 0x0000. + +Examples of operating bands: 0000 0000 0001 0000 = Operating band II + +0000 0000 0011 1000 = Operating band I, II and III + +**Table F.3: Band related fields for additional data of TMAAP** + +| Field No. | Length (octets) | Format | Description | +|------------------|------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0x03 | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2 above | +| 0x08 | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2-1 above | +| 0x09 | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2-2 above | +| 0x0A | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2-3 above | +| 0x0B | 2 | 16-bit unsigned | Antenna operating band(s): see Table F.2-4 above | +| 0x04 | 8 | 4 x 16-bit unsigned | Beamwidth for each operating band in band order (deg) beginning with lowest band. The lowest band is transmitted within the first 16-bit value. | +| 0x05 | 4 | 4 x 8-bit unsigned | Gain [dBi] for each operating band in band order, expressed in gain value times 10, beginning with the lowest band. The lowest band is transmitted within the first 8-bit value (example: gain for band I, gain for band III) | + +## Annex G (informative): Change History + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-02 | R3-103 | R3-190103 | | | | Text transferred from 25.466 v15.3.0 (changes shown with rev marks) | 1.15.0 | +| 2019-04 | RAN#83 | RP-190606 | | | | Specification approved by RAN plenary | 15.4.0 | +| 2019-12 | RP-86 | RP-192915 | 0001 | 5 | F | Correction for luant | 15.5.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-03 | SA#95-e | | | | | Promotion to Release 17 without technical change | 17.0.0 | +| 2024-03 | RAN#103 | RP-240617 | 0003 | - | D | Rapporteur Editorial Review | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37470/raw.md b/marked/Rel-18/37_series/37470/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6925c9cbdff64b9f1a7dc9fd6252bface3ece256 --- /dev/null +++ b/marked/Rel-18/37_series/37470/raw.md @@ -0,0 +1,461 @@ + + +# 3GPP TS 37.470 V18.0.0(2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 interface; General aspects and principles (Release 18)** + +![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G ADVANCED logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 7 | +| 4 General aspects ..... | 7 | +| 4.0 General ..... | 7 | +| 4.1 W1 interface general principles..... | 7 | +| 4.2 W1 interface specification objectives ..... | 8 | +| 4.3 W1 interface capabilities..... | 8 | +| 4.4 W1 interface characteristics ..... | 8 | +| 5 Functions of the W1 interface..... | 8 | +| 5.1 General ..... | 8 | +| 5.2 W1-C functions ..... | 8 | +| 5.2.1 Interface management function ..... | 8 | +| 5.2.2 System Information management function ..... | 9 | +| 5.2.3 Paging function..... | 9 | +| 5.2.4 UE context management function ..... | 9 | +| 5.2.5 RRC message transfer function ..... | 10 | +| 5.2.6 Warning messages information transfer function..... | 10 | +| 5.3 W1-U functions ..... | 10 | +| 5.3.1 Transfer of user data..... | 10 | +| 5.3.2 Flow control function ..... | 10 | +| 6 Procedures of the W1 interface..... | 10 | +| 6.1 Control plane procedures ..... | 10 | +| 6.1.1 Interface Management procedures..... | 10 | +| 6.1.2 Context Management procedures..... | 10 | +| 6.1.3 RRC Message Transfer procedures ..... | 11 | +| 6.1.3A Void ..... | 11 | +| 6.1.4 Warning Message Transmission procedures ..... | 11 | +| 6.1.5 Paging procedures ..... | 11 | +| 6.2 User plane procedures ..... | 11 | +| 6.2.1 User Data Transfer ..... | 11 | +| 6.2.2 Flow Control..... | 11 | +| 7 W1 interface protocol structure..... | 12 | +| 7.1 W1 Control Plane Protocol (W1-C)..... | 12 | +| 7.2 W1 User Plane Protocol (W1-U) ..... | 12 | +| 8 Other W1 interface specifications..... | 12 | +| 8.0 General ..... | 12 | +| 8.1 E-UTRAN and NG-RAN; W1 interface: layer 1 (3GPP TS 37.471) ..... | 13 | +| 8.2 E-UTRAN and NG-RAN; W1 signalling transport (3GPP TS 37.472) ..... | 13 | +| 8.3 E-UTRAN and NG-RAN; W1 application protocol (WIAP) (3GPP TS 37.473)..... | 13 | +| 8.4 NG-RAN; NR user plane protocol (3GPP TS 38.425) ..... | 13 | +| Annex A (informative): Change history..... | 14 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document is an introduction to the 3GPP TS 37.4xx series of technical specifications that define the W1 interface. The W1 interface provides means for interconnecting an ng-eNB-CU and an ng-eNB-DU of an ng-eNB within an NG-RAN. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.425: "NR user plane protocol". +- [3] 3GPP TS 38.300: "NR; Overall description; Stage-2" +- [4] 3GPP TS 37.471: "E-UTRAN and NG-RAN; W1 interface: layer 1". +- [5] 3GPP TS 37.472: "E-UTRAN and NG-RAN; W1 signalling transport". +- [6] 3GPP TS 37.473: "E-UTRAN and NG-RAN; W1 application protocol (WIAP)". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**W1:** interface between an ng-eNB-CU and an ng-eNB-DU, providing an interconnection point between the ng-eNB-CU and the ng-eNB-DU. + +**W1-C:** Reference point for the control plane protocol between ng-eNB-CU and ng-eNB-DU. + +**ng-eNB-CU:** a logical node hosting RRC, SDAP and PDCP protocols of the ng-eNB that controls the operation of one or more ng-eNB-DUs. The ng-eNB-CU terminates the W1 interface connected with the ng-eNB-DU. + +**ng-eNB-DU:** a logical node hosting RLC, MAC and PHY layers of the ng-eNB, and its operation is partly controlled by ng-eNB-CU. One ng-eNB-DU supports one or multiple cells. One cell is supported by only one ng-eNB-DU. The ng-eNB-DU terminates the W1 interface connected with the ng-eNB-CU. + +**ng-eNB:** as defined in TS 38.300 [3]. + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|--------------------------------------| +| DRB | Data Radio Bearers | +| W1-U | W1 User plane interface | +| W1-C | W1 Control plane interface | +| W1AP | W1 Application Protocol | +| GTP-U | GPRS Tunnelling Protocol | +| IP | Internet Protocol | +| NR-MIB | NR-Master Information Block | +| O&M | Operation and Maintenance | +| PA | Paging Area | +| PF | Paging Frame | +| PO | Paging Occasion | +| QoS | Quality of Service | +| RRC | Radio Resource Control | +| SCTP | Stream Control Transmission Protocol | +| SRB | Signalling Radio Bearers | +| SIB1 | System Information Block 1 | +| TNL | Transport Network Layer | + +# --- 4 General aspects + +## 4.0 General + +This clause captures the W1 interface principles and characteristics. + +## 4.1 W1 interface general principles + +The general principles for the specification of the W1 interface are as follows: + +- An ng-eNB may consist of an ng-eNB-CU and ng-eNB-DUs. An ng-eNB-CU and an ng-eNB-DU is connected via W1 logical interface. +- One ng-eNB-CU controls one or more ng-eNB-DUs. +- One ng-eNB-DU supports one or multiple cells. One cell is supported by only one ng-eNB-DU. +- ng-eNB-DU ID is used to identify ng-eNB-DU only over W1AP procedures, ng-eNB-DU ID is not connected to cell identifier. +- The ng-eNB-CU terminates W1 interface connected with the ng-eNB-DU. +- The ng-eNB-DU terminates W1 interface connected with the ng-eNB-CU. +- The W1 interface shall separate Radio Network Layer and Transport Network Layer. +- The W1 interface shall enable exchange of UE associated information and non-UE associated information. +- The W1 interface is open; +- From a logical standpoint, the W1 is a point-to-point interface between an ng-eNB-CU and an ng-eNB-DU. + +NOTE: A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints. + +- The W1 interface supports control plane and user plane separation; +- The W1 interface enables exchange of UE associated information and non-UE associated information; +- The standard should not prevent to separated CP and UP. + +## 4.2 W1 interface specification objectives + +The W1 interface specifications facilitate the following: + +- inter-connection of an ng-eNB-CU and an ng-eNB-DU supplied by different manufacturers. + +## 4.3 W1 interface capabilities + +The W1 interface supports: + +- procedures to establish, maintain and release radio bearers for the NG-RAN part of PDU sessions and for E-UTRAN Radio Access Bearers; +- the separation of each UE on the protocol level for user specific signalling management; +- the transfer of RRC signalling messages between the UE and the ng-eNB-CU. + +## 4.4 W1 interface characteristics + +# --- 5 Functions of the W1 interface + +## 5.1 General + +The following clauses describe the functions supported over W1-C and W1-U. + +## 5.2 W1-C functions + +### 5.2.1 Interface management function + +The W1 setup function allows to exchange application level data needed for the ng-eNB-DU and ng-eNB-CU to interoperate correctly on the W1 interface. The W1 setup is initiated by the ng-eNB-DU. + +The ng-eNB-CU Configuration Update and ng-eNB-DU Configuration Update functions allow to update application level configuration data needed between ng-eNB-CU and ng-eNB-DU to interoperate correctly over the W1 interface, and may activate or deactivate cells. + +For NG-RAN, the W1 setup and ng-eNB-DU Configuration Update functions allow to inform the S-NSSAI(s) supported by the ng-eNB-DU. + +The error indication function is used by the ng-eNB-DU or ng-eNB-CU to indicate to the ng-eNB-CU or ng-eNB-DU that an error has occurred. + +The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the ng-eNB-DU and the ng-eNB-CU. + +The W1 resource coordination function is used to transfer information about frequency resource sharing between ng-eNB-CU and ng-eNB-DU. + +The ng-eNB-DU status indication function allows the ng-eNB-DU to indicate overload status to ng-eNB-CU. + +### 5.2.2 System Information management function + +Scheduling of system broadcast information is carried out in the ng-eNB-DU. The ng-eNB-DU is responsible for transmitting the system information according to the scheduling parameters available. + +The ng-eNB-DU is responsible for the encoding of ng-eNB-MIB. In case broadcast of SIB1 and other SI messages is needed, the ng-eNB-DU is responsible for assembling SIB1, SIB2, SIB3, SIB8 and SIB16 and the ng-eNB-CU is responsible for assembling other SIBs. + +### 5.2.3 Paging function + +The ng-eNB-DU is responsible for transmitting the paging information. + +The ng-eNB-CU provides paging information to enable the ng-eNB-DU to calculate the exact PO and PF. The ng-eNB-CU determines the PA. The ng-eNB-DU consolidates all the paging records for a particular PO, PF and PA, and encodes the final RRC message and broadcasts the paging message on the respective PO, PF in the PA. + +### 5.2.4 UE context management function + +The W1 UE context management function supports the establishment and modification of the necessary overall UE context. + +The establishment of the W1 UE context is initiated by the ng-eNB-CU and accepted or rejected by the ng-eNB-DU based on admission control criteria (e.g., resource not available). + +The modification of the W1 UE context can be initiated by either ng-eNB-CU or ng-eNB-DU. The receiving node can accept or reject the modification. The W1 UE context management function also supports the release of the context previously established in the ng-eNB-DU. The release of the context is triggered by the ng-eNB-CU either directly or following a request received from the ng-eNB-DU. The ng-eNB-CU requests the ng-eNB-DU to remove the UE Context when the UE enters RRC\_IDLE or RRC\_INACTIVE. + +This function can be also used to manage DRBs and SRBs, i.e., establishing, modifying and releasing DRB and SRB resources. The establishment and modification of DRB resources are triggered by the ng-eNB-CU and accepted/rejected by the ng-eNB-DU based on resource reservation information and QoS information to be provided to the ng-eNB-DU. For each DRB to be setup or modified, the S-NSSAI may be provided by ng-eNB-CU to the ng-eNB-DU in the UE Context Setup procedure and the UE Context Modification procedure. + +For NG-RAN, the mapping between QoS flows and radio bearers is performed by ng-eNB-CU and the granularity of bearer related management over W1 is radio bearer level, and the ng-eNB-CU decides an aggregated DRB QoS profile for each radio bearer based on received QoS flow profile, and provides both aggregated DRB QoS profile and QoS flow profile to the ng-eNB-DU, and the ng-eNB-DU either accepts the request or rejects it with appropriate cause value. + +With this function, ng-eNB-DU could also notify ng-eNB-CU whether the QoS for already established DRBs is not fulfilled any longer or it is fulfilled again. + +The UE Inactivity Notification function is initiated by the ng-eNB-DU to indicate the UE activity event. + +The Notify function is to enable the ng-eNB-DU to inform the ng-eNB-CU that the QoS of an already established GBR DRB cannot be fulfilled any longer or that it can be fulfilled again. + +With this function, the ng-eNB-CU indicates the UL UE AMBR limit to the ng-eNB-DU, and the ng-eNB-DU enforces the indicated limit. + +With this function, the ng-eNB-CU indicates the UL UE AMBR limit to the ng-eNB-DU, and the ng-eNB-DU enforces the indicated limit. + +With this function, ng-eNB-CU requests the ng-eNB-DU to setup or change of the SpCell for the UE, and the ng-eNB-DU either accepts or rejects the request with appropriate cause value. + +With this function, the ng-eNB-CU requests the setup of the SCell(s) at the ng-eNB-DU side, and the ng-eNB-DU accepts all, some or none of the SCell(s) and replies to the ng-eNB-CU. The ng-eNB-CU requests the removal of the SCell(s) for the UE. + +With this function, the ng-eNB-DU indicates that a bearer, or a UE is inactive or active. The ng-eNB-CU consolidates all the serving ng-eNB-DUs for the UE and takes further action. + +### 5.2.5 RRC message transfer function + +This function allows to transfer RRC messages between ng-eNB-CU and ng-eNB-DU. RRC messages are transferred over W1-C. The ng-eNB-CU is responsible for the encoding of the dedicated RRC message with assistance information provided by ng-eNB-DU. This function also allows ng-eNB-DU to report to ng-eNB-CU if the downlink RRC message has been successfully delivered to UE or not. + +### 5.2.6 Warning messages information transfer function + +This function allows to cooperate with the warning message transmission procedures over NG interface. The ng-eNB-CU is responsible for encoding the warning related SI message and sending it together with other warning related information for the ng-eNB-DU to broadcast over the radio interface. + +## 5.3 W1-U functions + +### 5.3.1 Transfer of user data + +This function allows to transfer of user data between ng-eNB-CU and ng-eNB-DU. + +### 5.3.2 Flow control function + +This function allows to control the downlink user data flow to the ng-eNB-DU. The detailed protocol is specified in TS 38.425 [2] + +# --- 6 Procedures of the W1 interface + +## 6.1 Control plane procedures + +### 6.1.1 Interface Management procedures + +The W1 Interface management procedures are listed below: + +- Reset procedure +- Error Indication procedure +- W1 Setup procedure +- ng-eNB-DU Configuration Update procedure +- ng-eNB-CU Configuration Update procedure +- ng-eNB-DU Resource Coordination procedure +- ng-eNB-DU Status Indication procedure + +### 6.1.2 Context Management procedures + +The W1 Context management procedures are listed below: + +- UE Context Setup procedure +- UE context Release Request (ng-eNB-DU initiated) procedure + +- UE context Release (ng-eNB-CU initiated) procedure +- UE Context Modification (ng-eNB-CU initiated) procedure +- UE Context Modification Required (ng-eNB-DU initiated) procedure +- UE Inactivity Notification procedure +- Notify procedure + +### 6.1.3 RRC Message Transfer procedures + +The W1 RRC message transfer procedures are listed below: + +- Initial UL RRC Message Transfer procedure +- UL RRC Message Transfer procedure +- DL RRC Message Transfer procedure +- RRC Delivery Report procedure + +### 6.1.3A Void + +### 6.1.4 Warning Message Transmission procedures + +The W1 Warning message transmission procedures are listed below: + +- Write-Replace Warning procedure +- PWS Cancel procedure +- PWS Restart Indication procedure +- PWS Failure Indication procedure + +### 6.1.5 Paging procedures + +The W1 Paging procedures are listed below: + +- Paging + +## 6.2 User plane procedures + +### 6.2.1 User Data Transfer + +Void + +### 6.2.2 Flow Control + +Void + +# 7 W1 interface protocol structure + +## 7.1 W1 Control Plane Protocol (W1-C) + +Figure 7.1-1 shows the protocol structure for W1-C. The TNL is based on IP transport, comprising the SCTP on top of IP. The application layer signalling protocol is referred to as WIAP (W1 Application Protocol). + +![Figure 7.1-1: Interface protocol structure for W1-C](08441fa90c5fd11994626f662ac13f19_img.jpg) + +The diagram illustrates the protocol stack for the W1 Control Plane (W1-C). At the top, the 'Control Plane' label is centered. Below it, the 'Radio Network Layer' is indicated on the left, containing a box labeled 'WIAP'. A horizontal line with an oval in the center separates the Radio Network Layer from the 'Transport Network Layer' below. The Transport Network Layer contains four stacked boxes: 'SCTP', 'IP', 'Data link layer', and 'Physical layer'. + +Figure 7.1-1: Interface protocol structure for W1-C + +Figure 7.1-1: Interface protocol structure for W1-C + +## 7.2 W1 User Plane Protocol (W1-U) + +Figure 7.2-1 shows the protocol structure for W1-U. The TNL is based on IP transport, comprising the UDP and GTP-U on top of IP. + +![Figure 7.2-1: Interface protocol structure for W1-U](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +The diagram illustrates the protocol stack for the W1 User Plane (W1-U). At the top, the 'User Plane' label is centered. Below it, the 'Radio Network Layer' is indicated on the left, containing an empty box. A horizontal line with an oval in the center separates the Radio Network Layer from the 'Transport Network Layer' below. The Transport Network Layer contains four stacked boxes: 'GTP-U', 'UDP', 'IP', and 'Data link layer'. The 'Physical layer' is shown as a separate box at the bottom of the stack. + +Figure 7.2-1: Interface protocol structure for W1-U + +Figure 7.2-1: Interface protocol structure for W1-U + +# 8 Other W1 interface specifications + +## 8.0 General + +This clause contains the description of the other related 3GPP specifications. + +## 8.1 E-UTRAN and NG-RAN; W1 interface: layer 1 (3GPP TS 37.471) + +3GPP TS 37.471 [4] specifies the physical layer technologies that may be used to support the W1 interface. + +## 8.2 E-UTRAN and NG-RAN; W1 signalling transport (3GPP TS 37.472) + +3GPP TS 37.472 [5] specifies the signalling bearers for the W1AP for the W1-C interface. + +## 8.3 E-UTRAN and NG-RAN; W1 application protocol (W1AP) (3GPP TS 37.473) + +3GPP TS 37.473 [6] specifies the FIAP protocol for radio network control plane signalling over the W1 interface. + +## 8.4 NG-RAN; NR user plane protocol (3GPP TS 38.425) + +3GPP TS 38.425 [2] specifies the user plane protocol being used over the W1-U interface. \ No newline at end of file diff --git a/marked/Rel-18/37_series/37471/raw.md b/marked/Rel-18/37_series/37471/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fc9ba97fea5d8ccab0f94648dde16e6d2dd8a1a6 --- /dev/null +++ b/marked/Rel-18/37_series/37471/raw.md @@ -0,0 +1,168 @@ + + +# 3GPP TS 37.471 V18.0.0(2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 interface; Layer 1 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|--------------------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 Introduction..... | 6 | +| Annex A (informative): Change history..... | 7 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document specifies the standards allowed to implement Layer 1 on the W1 interface. The W1 interface provides means for interconnecting an ng-eNB-CU and an ng-eNB-DU of an ng-eNB within NG-RAN. + +The specification of transmission delay requirements and O&M requirements are not in the scope of the present document. + +In the following 'Layer 1' and 'Physical Layer' are assumed to be synonymous. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] 3GPP TS 38.300: "NR; Overall description; Stage-2". + +[3] 3GPP TS 38.411: "NG-RAN; NG layer 1". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +ng-eNB: as defined in 3GPP TS 38.300 [2]. + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1], in TS 38.411 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +# --- 4 Introduction + +The W1 Layer 1 shall comply with the requirements of clauses 4 through 6 in 3GPP TS 38.411 [3]. \ No newline at end of file diff --git a/marked/Rel-18/37_series/37472/raw.md b/marked/Rel-18/37_series/37472/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5eb8ad59d2de61c7bbd669171cba4ce1be0b7307 --- /dev/null +++ b/marked/Rel-18/37_series/37472/raw.md @@ -0,0 +1,251 @@ + + +# 3GPP TS 37.472 V18.0.0(2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 interface; Signalling transport (Release 18)** + +![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G ADVANCED logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|--------------------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 7 | +| 4. W1-C signalling bearer ..... | 7 | +| 4.1 Function and protocol stack ..... | 7 | +| 5 Data link layer..... | 7 | +| 6 IP layer..... | 7 | +| 7 Transport layer ..... | 8 | +| Annex A (informative): Change History..... | 9 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document specifies the standards for Signalling Transport to be used across the W1 interface. The W1 interface provides means for interconnecting a ng-eNB-CU and a ng-eNB-DU of a ng-eNB within a NG-RAN. The present document describes how the W1AP signalling messages are transported over W1. + +# --- 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] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification". +- [3] IETF RFC 791 (1981-09): "Internet Protocol". +- [4] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [5] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol". +- [6] 3GPP TS 38.300: "NR; Overall description; Stage-2". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**ng-eNB:** as defined in 3GPP TS 38.300 [6] + +**SCTP association:** as defined in IETF RFC 4960 (2007-09) [5] + +**SCTP endpoint:** as defined in IETF RFC 4960 (2007-09) [5] + +**W1:** interface between a ng-eNB-CU and a ng-eNB-DU, providing an interconnection point between the ng-eNB-CU and the ng-eNB-DU. + +**W1-C:** Reference point for the control plane protocol between ng-eNB-CU and ng-eNB-DU. + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|----------|--------------------------------------| +| DiffServ | Differentiated Service | +| IANA | Internet Assigned Number Authority | +| IP | Internet Protocol | +| PPP | Point to Point Protocol | +| SCTP | Stream Control Transmission Protocol | + +# 4. W1-C signalling bearer + +## 4.1 Function and protocol stack + +The W1-C signalling bearer provides the following functions: + +- Provision of reliable transfer of W1AP messages over the W1-C interface. +- Provision of networking and routing function. +- Provision of redundancy in the signalling network. +- Support for flow control and congestion control. + +The protocol stack for W1-C Signalling Bearer is shown in figure 4.1-1 and details on each protocol are described in the following clauses. + +![Figure 4.1-1: W1-C signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer, which contains the W1AP protocol. Below W1AP is a horizontal line with an oval in the center, representing an interface. Below the interface is the Transport Network Layer, which contains the SCTP, IP, Data link layer, and Physical layer stacked vertically.](c9d8a18a6137ad054b841d7a614afb48_img.jpg) + +The diagram illustrates the protocol stack for the W1-C signalling bearer. It is divided into two main layers: the Radio Network Layer and the Transport Network Layer. The Radio Network Layer contains the W1AP protocol. Below the Radio Network Layer is an interface, represented by a horizontal line with an oval in the center. The Transport Network Layer consists of four stacked protocols: SCTP, IP, Data link layer, and Physical layer. + +Figure 4.1-1: W1-C signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer, which contains the W1AP protocol. Below W1AP is a horizontal line with an oval in the center, representing an interface. Below the interface is the Transport Network Layer, which contains the SCTP, IP, Data link layer, and Physical layer stacked vertically. + +**Figure 4.1-1: W1-C signalling bearer protocol stack** + +The Transport Network Layer is based on IP transport, comprising SCTP on top of IP. + +# --- 5 Data link layer + +The support of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented. + +# --- 6 IP layer + +The ng-eNB-CU and ng-eNB-DU shall support IPv6 (IETF RFC 8200 [2]) and/or IPv4 (IETF RFC 791 [3]). + +The IP layer of W1-C only supports point-to-point transmission for delivering W1AP message. + +The ng-eNB-CU and ng-eNB-DU shall support the Diffserv Code Point marking as described in IETF RFC 2474 [4]. + +# 7 Transport layer + +SCTP (IETF RFC 4960 [5]) shall be supported as the transport layer of W1-C signalling bearer. The Payload Protocol Identifier assigned by IANA to be used by SCTP for the application layer protocol W1AP is 73. + +SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network. + +The ng-eNB-DU and ng-eNB-CU shall support a configuration with a single SCTP association per ng-eNB-DU/ng-eNB-CU pair. + +The ng-eNB-DU shall establish the SCTP association. The SCTP Destination Port number value assigned by IANA to be used for W1AP is 37472. + +Within the set of SCTP associations established between one ng-eNB-CU and ng-eNB-DU pair, a single SCTP association shall be employed for W1AP elementary procedures that utilize non-UE-associated signalling with the possibility of fail-over to a new association to enable robustness. + +Between one ng-eNB-CU and ng-eNB-DU pair: + +- A single pair of stream identifiers shall be reserved over an SCTP association for the sole use of W1AP elementary procedures that utilize non UE-associated signalling. +- At least one pair of stream identifiers over one or several SCTP associations shall be reserved for the sole use of W1AP elementary procedures that utilize UE-associated signalling. However, a few pairs (i.e. more than one) should be reserved. +- For a single UE-associated signalling, the ng-eNB-DU shall use one SCTP association and one SCTP stream, and the association/stream should not be changed during the communication of the UE-associated signalling unless TNL binding update is performed. + +Transport network redundancy may be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remote SCTP end-point. For SCTP endpoint redundancy an INIT may be sent from a ng-eNB-CU or ng-eNB-DU, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960[5] in sub clause 5.2. + +The SCTP congestion control may, using an implementation specific mechanism, initiate higher layer protocols to reduce the signalling traffic at the source and prioritise certain messages. + +# Annex A (informative): Change History + +| Change history | | | | | | | | +|----------------|---------------|-----------|------|-----|-----|---------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-05 | RAN3#100 | R3-183554 | | | | BL TS submission for approval. | | +| 2019-08 | RAN3#105 | R3-194678 | | | | Add the description of procedure for the W1 signalling transport protocol | 0.1.0 | +| 2019-10 | RAN3#105 -Bis | R3-196134 | | | | Add the description of References, Definitions and abbreviations. | 0.1.0 | +| 2019-11 | RAN3#106 -Bis | R3-197634 | | | | Change the version number to 0.2.0. | 0.2.0 | +| 2019-12 | RP-86 | RP-192954 | | | | TS submitted to TSG RAN plenary for approval | 1.3.0 | +| 2019-12 | RP-86 | | | | | TS approved by TSG RAN plenary | 16.0.0 | +| 2020-07 | RP-88-e | RP-201236 | 0002 | - | F | SCTP Payload Protocol Identifier for W1AP | 16.1.0 | +| 2020-09 | RP-89-e | RP-201948 | 0003 | - | F | SCTP port number allocatd by IANA | 16.2.0 | +| 2022-03 | SA#95-e | | | | | Promotion to Release 17 without technical change | 17.0.0 | +| 2024-03 | SA#103- | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37480/raw.md b/marked/Rel-18/37_series/37480/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e602890a802a6c22bb35dd945f80e377b445e7e8 --- /dev/null +++ b/marked/Rel-18/37_series/37480/raw.md @@ -0,0 +1,431 @@ + + +# 3GPP TS 37.480 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E1 general aspects and principles (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo. + +3GPP logo + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|--------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 General aspects ..... | 6 | +| 4.1 E1 interface general principles..... | 6 | +| 4.2 E1 interface specification objectives..... | 7 | +| 5 Functions of the E1 interface ..... | 7 | +| 5.1 General ..... | 7 | +| 5.1.1 E1 interface management function..... | 7 | +| 5.1.2 E1 bearer context management function ..... | 7 | +| 5.1.3 Trace function..... | 8 | +| 5.1.4 Load management function ..... | 8 | +| 5.1.5 Measurement results transfer function ..... | 8 | +| 5.1.6 Support for IAB ..... | 8 | +| 5.1.7 E1 bearer context management function for NR MBS..... | 9 | +| 5.2 TEIDs allocation ..... | 9 | +| 6 Procedures of the E1 interface ..... | 9 | +| 6.1 Interface Management procedures ..... | 9 | +| 6.2 Bearer Context Management procedures ..... | 9 | +| 6.3 UE Tracing procedures..... | 10 | +| 6.4 Load management procedures..... | 10 | +| 6.5 Measurement results transfer procedures..... | 10 | +| 6.6 IAB procedures ..... | 10 | +| 6.7 NR MBS procedures ..... | 10 | +| 7 E1 interface protocol structure..... | 11 | +| 8 Other E1 interface specifications ..... | 11 | +| 8.1 E1 interface: layer 1 (3GPP TS 37.481)..... | 11 | +| 8.2 E1 interface: signalling transport (3GPP TS 37.482)..... | 11 | +| 8.3 E1 interface: E1AP specification (3GPP TS 37.483)..... | 12 | +| Annex A (informative): Change history..... | 13 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document is an introduction to the 3GPP TS 37.48x series of technical specifications that define the E1 interface. The E1 interface provides means for interconnecting a gNB-CU-CP and a gNB-CU-UP of a gNB-CU within an NG-RAN, or for interconnecting a gNB-CU-CP and a gNB-CU-UP of an en-gNB within an E-UTRAN, or for interconnecting an eNB-CP and an eNB-UP of an eNB within an E-UTRAN, or for interconnecting an ng-eNB-CU-CP and an ng-eNB-CU-UP of an ng-eNB-CU within an NG-RAN. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.401: "NG-RAN; Architecture Description". +- [3] 3GPP TS 37.481: "E1 layer 1". +- [4] 3GPP TS 37.482: "E1 signalling transport". +- [5] 3GPP TS 37.483: "E1 Application Protocol (E1AP)". +- [6] 3GPP TS 38.300: "NR; Overall description; Stage-2". +- [7] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2". +- [8] 3GPP TS 37.470: "W1 interface; General aspects and principles". +- [9] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description". +- [10] 3GPP TS 23.247: "5G multicast-broadcast services; Stage 2". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**eNB-CP:** as defined in TS 36.401 [9]. + +**eNB-UP:** as defined in TS 36.401 [9]. + +**en-gNB:** as defined in TS 37.340 [7]. + +**gNB-CU:** as defined in TS 38.401 [2]. + +**gNB-CU-CP:** as defined in TS 38.401 [2]. + +**gNB-CU-UP:** as defined in TS 38.401 [2]. + +**gNB-DU:** as defined in TS 38.401 [2]. + +**gNB:** as defined in TS 38.300 [6]. + +**IAB:** as defined in TS 38.300 [6]. + +**ng-eNB-CU:** as defined in TS 37.470 [8]. + +**ng-eNB-CU-CP:** as defined in TS 38.401 [2]. + +**ng-eNB-CU-UP:** as defined in TS 38.401 [2]. + +**ng-eNB-DU:** as defined in TS 37.470 [8]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|-------------------------------------------| +| DL | Downlink | +| DRB | Data Radio Bearer | +| E1AP | E1 Application Protocol | +| IP | Internet Protocol | +| MBS | Multicast/Broadcast Service | +| MT-SDT | Mobile Terminated Small Data Transmission | +| PTP | Point to Point | +| PTM | Point to Multipoint | +| SCTP | Stream Control Transmission Protocol | +| TNL | Transport Network Layer | + +# --- 4 General aspects + +This clause captures the E1 interface principles and characteristics. + +**Note:** The principles, functions and procedures specified in this specification also apply to the case where E1AP is used between an ng-eNB-CU-CP and an ng-eNB-CU-UP or between an eNB-CP and an eNB-UP, unless stated otherwise. + +## 4.1 E1 interface general principles + +The general principles for the specification of the E1 interface are as follows: + +- the E1 interface is open; +- the E1 interface supports the exchange of signalling information between the endpoints; +- from a logical standpoint, the E1 is a point-to-point interface between a gNB-CU-CP and a gNB-CU-UP, or between an ng-eNB-CU-CP and an ng-eNB-CU-UP, or between an eNB-CP and an eNB-UP. + +**NOTE 1:** A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints. + +- the E1 interface separates Radio Network Layer and Transport Network Layer; +- the E1 interface enables exchange of UE associated information and non-UE associated information; +- the E1 interface is future proof to fulfil different new requirements, support of new services and new functions. + +## 4.2 E1 interface specification objectives + +The E1 interface specifications facilitate the following: + +- inter-connection of a gNB-CU-CP and a gNB-CU-UP supplied by different manufacturers. +- inter-connection of an ng-eNB-CU-CP and an ng-eNB-CU-UP supplied by different manufacturers. +- inter-connection of an eNB-CP and an eNB-UP supplied by different manufacturers. + +# --- 5 Functions of the E1 interface + +## 5.1 General + +The following clauses describe the functions supported over E1. + +### 5.1.1 E1 interface management function + +The error indication function is used by the gNB-CU-UP or gNB-CU-CP to indicate to the gNB-CU-CP or gNB-CU-UP that an error has occurred. + +The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the gNB-CU-UP and the gNB-CU-CP. + +The E1 setup function allows to exchange application level data needed for the gNB-CU-UP and gNB-CU-CP to interoperate correctly on the E1 interface. The E1 setup is initiated by both the gNB-CU-UP and gNB-CU-CP. + +The gNB-CU-UP Configuration Update and gNB-CU-CP Configuration Update functions allow to update application level configuration data needed between the gNB-CU-CP and the gNB-CU-UP to interoperate correctly over the E1 interface. + +The E1 setup and gNB-CU-UP Configuration Update functions allow to inform NR CGI(s), ECGI(s), S-NSSAI(s), PLMN-ID(s), QoS information and NID(s) supported by the gNB-CU-UP. + +The E1 setup and gNB-CU-UP Configuration Update functions allow the gNB-CU-UP to signal its capacity information to the gNB-CU-CP. + +The E1 gNB-CU-UP Status Indication function allows to inform the overloaded or non-overloaded status over the E1 interface. + +### 5.1.2 E1 bearer context management function + +The establishment of the E1 bearer context is initiated by the gNB-CU-CP and accepted or rejected by the gNB-CU-UP based on admission control criteria (e.g., resource not available). + +The modification of the E1 bearer context can be initiated by either gNB-CU-CP or gNB-CU-UP. The receiving node can accept or indicate failure to carry out the modification request. The E1 bearer context management function also supports the release of the bearer context previously established in the gNB-CU-UP. The release of the bearer context is triggered by the gNB-CU-CP either directly or following a request received from the gNB-CU-UP. + +This function is used to setup and modify the QoS-flow to DRB mapping configuration. The gNB-CU-CP decides flow-to-DRB mapping and provides the generated SDAP and PDCP configuration to the gNB-CU-UP. The gNB-CU-CP also decides the Reflective QoS flow to DRB mapping. The function is also used to send to the gNB-CU-UP the alternative QoS Parameters Sets when available for a QoS flow. For each PDU Session Resource to be setup or modified, the S-NSSAI, shall be provided in the E1 bearer context setup procedure and may be provided in the E1 bearer context modification procedure by gNB-CU-CP to the gNB-CU-UP. + +This function is also used to setup and modify the EPS bearer/E-RAB to DRB mapping configuration for the case of eNB-CP and eNB-UP separation. The eNB-CP decides EPS bearer/E-RAB-to-DRB mapping and provides the E-UTRAN/NR PDCP configuration to the eNB-UP. + +This function is also used for the gNB-CU-UP to report the MT-SDT data size to the gNB-CU-CP. + +This function is used for the gNB-CU-CP to send the security information to the gNB-CU-UP. + +This function is used for the gNB-CU-CP to send to the gNB-CU-UP transport layer information to be used for data forwarding e.g., during handovers. + +This function is used for the gNB-CU-CP to send the parameters for header compression for certain traffic types e.g., IP, Ethernet to the gNB-CU-UP. + +This function is used for the gNB-CU-CP to send the uplink data compression parameters to the gNB-CU-UP for certain data radio bearer(s). + +This function is used for the gNB-CU-UP to notify the event of DL data arrival detection to the gNB-CU-CP. With this function, the gNB-CU-UP requests gNB-CU-CP to trigger paging procedure over F1 or Xn to support RRC Inactive state. RRC Inactive state is not supported when this function is used between an eNB-CP and an eNB-UP. + +This function is used for the gNB-CU-UP to notify the gNB-CU-CP that a DL packet including a QFI value not configured by the gNB-CU-CP or an UL packet including a QFI value in the SDAP header of the default DRB not configured by the gNB-CU-CP is received for the first time. The gNB-CU-CP can take further action if needed. + +This function is used for the gNB-CU-UP to notify the gNB-CU-CP during the SDT procedure that the received DL SDT data crossed the data size threshold. The gNB-CU-CP can take further action if needed. + +This function is used for the gNB-CU-UP to notify the event of user inactivity to the gNB-CU-CP. With this function, the gNB-CU-UP indicates that the inactivity timer associated with a bearer, a PDU session or a UE expires, or that user data is received for the bearer, the PDU session or the UE whose inactivity timer has expired. The gNB-CU-CP consolidates all the serving gNB-CU-UPs for the UE and takes further action. + +This function is used for the gNB-CU-UP to report data volume to the gNB-CU-CP. + +This function is used for the gNB-CU-CP to notify the suspension and resumption of bearer contexts to the gNB-CU-UP. Suspension and resumption of bearer contexts are not applicable to eNB-CP/eNB-UP and ng-eNB-CU-CP/ng-eNB-CU-UP. + +This function also allows to support CA based packet duplication as described in TS 38.300 [6], i.e. one data radio bearer should be configured with at least two GTP-U tunnels between gNB-CU-UP and a gNB-DU. + +This function is used to support the enhanced mobility operations as described in TS 38.300 [6] in the gNB-CU-UP. + +### 5.1.3 Trace function + +The Trace function provides means to control trace sessions for a UE over E1 interface. + +### 5.1.4 Load management function + +The load management function allows an gNB-CU-CP to request the reporting of load measurements to gNB-DU and is used by gNB-CU-UP to report the result of measurements admitted by gNB-CU-UP. + +### 5.1.5 Measurement results transfer function + +The measurement results transfer is used by the gNB-CU-CP to transfer UE associated measurement results to the gNB-CU-UP. + +### 5.1.6 Support for IAB + +Note: IAB is an NR feature, and this function is not applicable to eNB CP-UP separation and ng-eNB CP-UP separation. + +This function is used to update the DL/UL F1-U GTP-U tunnels for an IAB network, and allow the gNB-CU-CP to send the security key info to the gNB-CU-UP for the protection of the F1-U interface with IAB-DU. + +### 5.1.7 E1 bearer context management function for NR MBS + +The E1 bearer context management function for NR MBS consists of two sub-sets for functions, one for NR MBS broadcast, one for NR MBS multicast. + +Both sets follow the principles of the E1 bearer context management functions, with the following differences. + +- E1 NR MBS procedure concerns a single MBS Session Resource only. +- E1 NR MBS procedures concern the control of MRB resources in gNB-CU-UP. +- E1 NR MBS procedures do not control security information, as for NR MBS, PDCP does not apply security as specified in TS 38.300 [6]. +- QoS flow to MRB mapping is determined by the gNB-CU-CP or, in case of shared NR-U terminations, the gNB-CU-UP may be notified about the QoS flow to MRB mapping already determined in the bearer context for the shared NR-U termination. The gNB-CU-CP may inform the gNB-CU-UP whether it is contended with the already determined mapping decision. + +NOTE: Not all QoS flow parameters are applicable for NR MBS, as specified in TS 23.247 [10]. + +- Data volume reporting is not applicable for NR MBS. +- CA based packet duplication is not applicable for NR MBS. + +## 5.2 TEIDs allocation + +The gNB-CU-UP is responsible for the allocation of the F1-U UL GTP TEID for each data radio bearer. + +The gNB-CU-UP is responsible for the allocation of the S1-U DL GTP TEID for each E-RAB and the NG-U DL GTP TEID for each PDU Session. + +The gNB-CU-UP is responsible for the allocation of the X2-U DL/UL GTP TEID or the Xn-U DL/UL GTP TEID for each data radio bearer. + +# --- 6 Procedures of the E1 interface + +## 6.1 Interface Management procedures + +The E1 interface management procedures are listed below: + +- Reset procedure +- Error Indication procedure +- gNB-CU-UP E1 Setup procedure +- gNB-CU-CP E1 Setup procedure +- gNB-CU-UP Configuration Update procedure +- gNB-CU-CP Configuration Update procedure +- E1 Release procedure +- gNB-CU-UP Status Indication procedure + +## 6.2 Bearer Context Management procedures + +The E1 bearer management procedures are listed below: + +- Bearer Context Setup procedure +- Bearer Context Release Request (gNB-CU-UP initiated) procedure +- Bearer Context Release (gNB-CU-CP initiated) procedure +- Bearer Context Modification (gNB-CU-CP initiated) procedure +- Bearer Context Modification Required (gNB-CU-UP initiated) procedure +- DL Data Notification procedure +- Bearer Context Inactivity Notification procedure +- Data Usage Report procedure +- MR-DC Data Usage Report procedure + +## 6.3 UE Tracing procedures + +The following procedures are used to trace the UE: + +- Trace Start procedure +- Deactivate Trace procedure +- Cell Traffic Trace procedure + +## 6.4 Load management procedures + +The load management procedures are listed as below: + +- Resource Status Reporting Initiation procedure +- Resource Status Reporting procedure + +## 6.5 Measurement results transfer procedures + +The measurement results transfer procedures are listed as below: + +- gNB-CU-CP Measurement Results Information + +## 6.6 IAB procedures + +Note: IAB is an NR feature, and this procedure is not applicable to eNB CP-UP separation and ng-eNB CP-UP separation. + +The IAB procedures are listed as below: + +- IAB UP TNL Address Update procedure +- IAB PSK Notification procedure + +## 6.7 NR MBS procedures + +The E1 MBS procedures are listed below: + +- Broadcast E1AP MBS procedures +- BC Bearer Context Setup + +- BC Bearer Context Modification (gNB-CU-CP initiated) +- BC Bearer Context Modification (gNB-CU-UP initiated) +- BC Bearer Context Release (gNB-CU-CP initiated) +- BC Bearer Context Release (gNB-CU-UP initiated) +- Multicast E1AP MBS procedures + - MC Bearer Context Setup + - MC Bearer Context Modification (gNB-CU-CP initiated) + - MC Bearer Context Modification (gNB-CU-UP initiated) + - MC Bearer Context Release (gNB-CU-CP initiated) + - MC Bearer Context Release (gNB-CU-UP initiated) + - MC Bearer Notification + +# 7 E1 interface protocol structure + +Figure 7.1-1 shows the protocol structure for E1. The TNL is based on IP transport, comprising the SCTP on top of IP. The application layer signalling protocol is referred to as E1AP (E1 Application Protocol). + +![Diagram of E1 interface protocol structure showing Control Plane and User Plane layers.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +The diagram illustrates the protocol stack for the E1 interface. It is divided into two main sections: the Control Plane and the User Plane. The Control Plane contains the E1-AP (E1 Application Protocol) block. The User Plane consists of a stack of four layers: SCTP (Stream Control Transmission Protocol), IP (Internet Protocol), Data link layer, and Physical layer. The E1-AP block is connected to the SCTP block via a horizontal line with an oval symbol, representing a protocol data unit (PDU) or a connection point. The SCTP block is part of the Transport Network Layer, which also includes the IP, Data link layer, and Physical layer blocks. The Radio Network Layer is shown above the E1-AP block, indicating its position in the overall network architecture. + +Diagram of E1 interface protocol structure showing Control Plane and User Plane layers. + +Figure 7.1-1: Interface protocol structure for E1 + +# 8 Other E1 interface specifications + +This clause contains the description of the other related 3GPP specifications. + +## 8.1 E1 interface: layer 1 (3GPP TS 37.481) + +3GPP TS 37.481 [3] specifies the physical layer technologies that may be used to support the E1 interface. + +## 8.2 E1 interface: signalling transport (3GPP TS 37.482) + +3GPP TS 37.482 [4] specifies the signalling bearers for the E1AP for the E1 interface. + +## 8.3 E1 interface: E1AP specification (3GPP TS 37.483) + +3GPP TS 37.483 [5] specifies the E1AP protocol for radio network control plane signalling over the E1 interface. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-01 | R3#114bis-e | R3-220846 | | | | Text transferred from TS 38.460 v16.4.0 and references updated to 37.48x series | 0.0.1 | +| 2022-02 | R3#115-e | R3-221646 | | | | Changes from Rel-17 WI "LTE_NR_arch_evo_enh-Core" incorporated and change history updated. | 0.1.0 | +| 2022-03 | R3#115-e | R3-222579 | | | | Agreements from Rel-17 WI "LTE_NR_arch_evo_enh-Core" at RAN3#115-e incorporated. | 0.1.1 | +| 2022-03 | R3#115-e | R3-222973 | | | | Change history updated | 0.2.0 | +| 2022-03 | RAN#95-e | RP-220795 | | | | Version submitted for approval in RAN#95-e | 1.0.0 | +| 2022-03 | RAN#95-e | R3-220848 | | | | Agreed Rel-16/17 CRs from other WIs are merged.
Including REL-16 38.460 changes of R3-221224 of RP-220276, and REL-17 38.460 changes of R3-222614 of RP-220234, R3-222929 of RP-220224. | 1.1.0 | +| 2022-03 | SA#95-e | | | | | Promotion to Release 17 without technical change | 17.0.0 | +| 2022-06 | RAN#96 | RP-221145 | 0001 | - | D | E1 TS 37.480 Editorial corrections | 17.1.0 | +| 2022-06 | RAN#96 | RP-221134 | 0002 | - | F | Corrections on E1 bearer context management function for NR MBS | 17.1.0 | +| 2023-12 | RAN#102 | RP-233849 | 0005 | 2 | F | Correction on Temp no data and DL data arrival for Activate Multicast Session | 17.2.0 | +| 2023-12 | RAN#102 | RP-233820 | 0003 | 5 | B | Introduction on MT-SDT | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37481/raw.md b/marked/Rel-18/37_series/37481/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b8b26abb6ccbd1624607f1a2f12d25ed72150361 --- /dev/null +++ b/marked/Rel-18/37_series/37481/raw.md @@ -0,0 +1,108 @@ + + +# 3GPP TS 37.481 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E1 layer 1 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|---------------------------------------------------|----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Abbreviations ..... | 6 | +| 4 Introduction..... | 6 | +| Annex A (informative): Change history..... | 6 | + +# --- 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 standards allowed to implement layer 1 on the E1 interface. + +The specification of transmission delay requirements and O&M requirements are not in the scope of the present document. + +In the following, 'layer 1' and 'physical layer' are assumed to be synonymous. + +# --- 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 38.411: "NG-RAN; NG layer 1". + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations given in TS 38.411 [1] apply. + +# --- 4 Introduction + +The E1 Layer 1 shall comply with the requirements of clauses 4 through 6 in TS 38.411 [1]. \ No newline at end of file diff --git a/marked/Rel-18/37_series/37482/raw.md b/marked/Rel-18/37_series/37482/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9dece5314c5018b6fc6f2b0839c41f14c254f552 --- /dev/null +++ b/marked/Rel-18/37_series/37482/raw.md @@ -0,0 +1,231 @@ + + +# 3GPP TS 37.482 V18.1.0 (2024-06) + +Technical Specification + +## 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E1 signalling transport (Release 18) + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|---------------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 E1 signalling bearer ..... | 6 | +| 4.1 Function and protocol stack ..... | 6 | +| 5 Data link layer..... | 7 | +| 6 IP layer..... | 7 | +| 7 Transport layer ..... | 7 | +| Annex A (informative): Change history..... | 9 | + +# --- 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 standards for Signalling Transport to be used across the E1 interface. The E1 interface provides means for the interconnection of gNB-CU-CP and gNB-CU-UP within the NG-RAN architecture (TS 38.401 [2]), or for the interconnection of ng-eNB-CU-CP and ng-eNB-CU-UP within the NG-RAN architecture (TS 38.401 [2]), or for the interconnection of eNB-CP and eNB-UP within the E-UTRAN architecture (TS 36.401 [13]). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.401: "NG-RAN; Architecture description". +- [3] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification". +- [4] IETF RFC 791 (1981-09): "Internet Protocol". +- [5] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [6] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol". +- [7] 3GPP TS 37.480: "E1 general aspects and principles". +- [8] 3GPP TS 37.481: "E1 layer 1". +- [9] 3GPP TS 37.483: "E1 Application Protocol (E1AP)". +- [10] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage-2". +- [11] IETF RFC 6083 (2011-01): "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)". +- [12] IETF RFC 6335 (2011-08): "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry". +- [13] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description". +- [14] 3GPP TS 37.470: "W1 interface; General aspects and principles". +- [15] IANA: "Stream Control Transmission Protocol (SCTP) Parameters", []. +- [16] IANA: "Service Name and Transport Protocol Port Number Registry", []. + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**E1:** interface between a gNB-CU-CP and a gNB-CU-UP, providing an interconnection point between the gNB-CU-CP and the gNB-CU-UP, as defined in TS 38.300 [10]. This interface also applies to between the ng-eNB-CU-CP and the ng-eNB-CU-UP or between the eNB-CP and the eNB-UP. + +**eNB-CP:** as defined in TS 36.401 [13]. + +**eNB-UP:** as defined in TS 36.401 [13]. + +**gNB-CU:** as defined in TS 38.401 [2]. + +**gNB-CU-CP:** as defined in TS 38.401 [2]. + +**gNB-CU-UP:** as defined in TS 38.401 [2]. + +**ng-eNB-CU:** as defined in TS 37.470 [14]. + +**ng-eNB-CU-CP:** as defined in TS 38.401 [2]. + +**ng-eNB-CU-UP:** as defined in TS 38.401 [2]. + +**ng-eNB-DU:** as defined in TS 37.470 [14]. + +**SCTP endpoint:** as defined in IETF RFC 4960 (2007-09) [6]. + +**SCTP association:** as defined in IETF RFC 4960 (2007-09) [6]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|----------|--------------------------------------| +| DiffServ | Differentiated Service | +| IANA | Internet Assigned Number Authority | +| IP | Internet Protocol | +| PPP | Point to Point Protocol | +| SCTP | Stream Control Transmission Protocol | + +# 4 E1 signalling bearer + +## 4.1 Function and protocol stack + +E1 signalling bearer provides the following functions: + +- Provision of reliable transfer of E1AP message over E1 interface; +- Provision of networking and routing function; +- Provision of redundancy in the signalling network; +- Support for flow control and congestion control. + +The protocol stack for E1 Signalling Bearer is shown in figure 4.1-1 and details on each protocol are described in the following sections. + +![Figure 4.1-1: E1 signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer, which contains the EIAP protocol. Below EIAP is a horizontal line with an oval in the center, representing a connection point. Below this line is the Transport Network Layer, which contains the SCTP, IP, Data link layer, and Physical layer protocols stacked vertically.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +| | | +|-------------------------|-----------------| +| Radio Network Layer | EIAP | +| | — ( ) — | +| Transport Network Layer | SCTP | +| | IP | +| | Data link layer | +| | Physical layer | + +Figure 4.1-1: E1 signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer, which contains the EIAP protocol. Below EIAP is a horizontal line with an oval in the center, representing a connection point. Below this line is the Transport Network Layer, which contains the SCTP, IP, Data link layer, and Physical layer protocols stacked vertically. + +**Figure 4.1-1: E1 signalling bearer protocol stack** + +The Transport Network Layer is based on IP transport, comprising SCTP on top of IP. + +# 5 Data link layer + +The support of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented. + +# 6 IP layer + +The gNB-CU-CP, gNB-CU-UP, ng-eNB-CU-CP, ng-eNB-CU-UP, eNB-CP and eNB-UP shall support IPv6 (IETF RFC 8200 [3]) and/or IPv4 (IETF RFC 791 [4]). + +The IP layer of E1 only supports point-to-point transmission for delivering EIAP message. + +The gNB-CU-CP, gNB-CU-UP, ng-eNB-CU-CP, ng-eNB-CU-UP, eNB-CP and eNB-UP shall support the Diffserv Code Point marking as described in IETF RFC 2474 [5]. + +# 7 Transport layer + +**NOTE:** The transport layer structure and mechanism specified in this section are also used between ng-eNB-CU-CP and ng-eNB-CU-UP or between eNB-CP and eNB-UP, unless stated otherwise. With this understanding, in this section each instance of gNB-CU-CP could be treated as eNB-CP or ng-eNB-CU-CP, and each gNB-CU-UP could be treated as eNB-UP or ng-eNB-CU-UP, for eNB or ng-eNB CP/UP separation respectively. + +SCTP (IETF RFC 4960 [6]) shall be supported as the transport layer of E1 signalling bearer. The Payload Protocol Identifier to be used by SCTP for the application layer protocol EIAP and for DTLS over SCTP (IETF RFC 6083 [11]) is assigned by IANA in [15]. The byte order of the ppid shall be big-endian. + +SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network. + +The gNB-CU-CP and gNB-CU-UP shall support a configuration with a single SCTP association per gNB-CU-CP/gNB-CU-UP pair. Configurations with multiple SCTP endpoints per gNB-CU-CP/gNB-CU-UP pair should be supported. When configurations with multiple SCTP associations are supported, the gNB-CU-CP or the gNB-CU-UP may request to dynamically add/remove SCTP associations between the gNB-CU-CP/gNB-CU-UP pair. Within the set of SCTP associations established between one gNB-CU-CP and gNB-CU-UP pair, a single SCTP association shall be employed + +for E1AP elementary procedures that utilize non-UE-associated signalling with the possibility of fail-over to a new association to enable robustness. + +When the configuration with multiple SCTP endpoints per gNB-CU-UP is supported and gNB-CU-UP wants to add additional SCTP endpoints, the gNB-CU-UP Configuration Update procedure shall be the first E1AP procedure triggered on an additional TNLA of an already setup E1 interface instance after the TNL association has become operational, and the gNB-CU-CP shall associate the TNLA to the E1 interface instance using the included gNB-CU-UP ID. + +Either the gNB-CU-CP or gNB-CU-UP shall establish the first SCTP association. The additional SCTP associations are established by the gNB-CU-UP. The SCTP Destination Port number value to be used for E1AP is assigned by IANA in [16]. When the gNB-CU-CP requests to dynamically add additional SCTP associations between the gNB-CU-CP and gNB-CU-UP pair, the gNB-CU-CP port is selected and signalled by the gNB-CU-CP to the gNB-CU-UP, and it can be port number value assigned by IANA in [16] or any dynamic port value as defined by IETF RFC 6335 [12]. + +Between one gNB-CU-CP and gNB-CU-UP pair: + +- A single pair of stream identifiers shall be reserved over an SCTP association for the sole use of E1AP elementary procedures that utilize non UE-associated signalling; +- At least one pair of stream identifiers over one or several SCTP associations shall be reserved for the sole use of E1AP elementary procedures that utilize UE-associated signalling. However, a few pairs (i.e. more than one) should be reserved; +- For a single UE-associated signalling the gNB-CU-CP and the gNB-CU-UP shall use one SCTP association and one SCTP stream, and the SCTP association/stream should not be changed during the communication of the UE-associated signalling until after current SCTP association is failed or removed, or TNL binding update is performed. + +Transport network redundancy may be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remote SCTP end-point. For SCTP endpoint redundancy an INIT may be sent from a gNB-CU-CP or a gNB-CU-UP, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960 [6] in sub clause 5.2. + +The SCTP congestion control may, using an implementation specific mechanism, initiate higher layer protocols to reduce the signalling traffic at the source and prioritise certain messages. + +For MBS-associated signalling, principles specified above for UE-associated signalling shall apply. \ No newline at end of file diff --git a/marked/Rel-18/37_series/37483/raw.md b/marked/Rel-18/37_series/37483/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..41881622546ff4911e2d0ecfa6dcdbc9b6d3efd7 --- /dev/null +++ b/marked/Rel-18/37_series/37483/raw.md @@ -0,0 +1,16708 @@ + + +# 3GPP TS 37.483 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E1 Application Protocol (E1AP) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. + +Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +Postal address + +3GPP support office address +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + +# Contents + +| | | +|----------------------------------------------------|----| +| Foreword..... | 12 | +| 1 Scope..... | 13 | +| 2 References..... | 13 | +| 3 Definitions and abbreviations..... | 14 | +| 3.1 Definitions..... | 14 | +| 3.2 Abbreviations..... | 16 | +| 4 General..... | 17 | +| 4.1 Procedure specification principles..... | 17 | +| 4.2 Forwards and backwards compatibility..... | 17 | +| 4.3 Specification notations..... | 17 | +| 5 EIAP services..... | 18 | +| 6 Services expected from signalling transport..... | 18 | +| 7 Functions of EIAP..... | 18 | +| 8 EIAP procedures..... | 18 | +| 8.1 List of EIAP Elementary Procedures..... | 18 | +| 8.2 Interface Management procedures..... | 20 | +| 8.2.1 Reset..... | 20 | +| 8.2.1.1 General..... | 20 | +| 8.2.1.2 Successful Operation..... | 20 | + +# **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +| | | | +|-----------|---------------------------------------------------|----| +| 8.2.1.2.1 | Reset Procedure Initiated from the gNB-CU-CP..... | 20 | +| 8.2.1.2.2 | Reset Procedure Initiated from the gNB-CU-UP..... | 21 | +| 8.2.1.3 | Abnormal Conditions..... | 22 | +| 8.2.2 | Error Indication..... | 22 | +| 8.2.2.1 | General..... | 22 | +| 8.2.2.2 | Successful Operation..... | 22 | +| 8.2.2.3 | Abnormal Conditions..... | 23 | +| 8.2.3 | gNB-CU-UP E1 Setup..... | 23 | +| 8.2.3.1 | General..... | 23 | +| 8.2.3.2 | Successful Operation..... | 23 | +| 8.2.3.3 | Unsuccessful Operation..... | 24 | +| 8.2.3.4 | Abnormal Conditions..... | 25 | +| 8.2.4 | gNB-CU-CP E1 Setup..... | 25 | +| 8.2.4.1 | General..... | 25 | +| 8.2.4.2 | Successful Operation..... | 25 | +| 8.2.4.3 | Unsuccessful Operation..... | 26 | +| 8.2.4.4 | Abnormal Conditions..... | 26 | +| 8.2.5 | gNB-CU-UP Configuration Update..... | 27 | +| 8.2.5.1 | General..... | 27 | +| 8.2.5.2 | Successful Operation..... | 27 | +| 8.2.5.3 | Unsuccessful Operation..... | 28 | +| 8.2.5.4 | Abnormal Conditions..... | 29 | +| 8.2.6 | gNB-CU-CP Configuration Update..... | 29 | +| 8.2.6.1 | General..... | 29 | +| 8.2.6.2 | Successful Operation..... | 29 | +| 8.2.6.3 | Unsuccessful Operation..... | 30 | +| 8.2.6.4 | Abnormal Conditions..... | 30 | +| 8.2.7 | E1 Release..... | 31 | +| 8.2.7.1 | General..... | 31 | +| 8.2.7.2 | Successful Operation..... | 31 | + +| | | | +|-----------|-----------------------------------------------------------------|----| +| 8.2.7.2.1 | E1 Release Procedure Initiated from the gNB-CU-CP..... | 31 | +| 8.2.7.2.2 | E1 Release Procedure Initiated from the gNB-CU-UP..... | 31 | +| 8.2.7.3 | Abnormal Conditions..... | 32 | +| 8.2.8 | gNB-CU-UP Status Indication..... | 32 | +| 8.2.8.1 | General..... | 32 | +| 8.2.8.2 | Successful Operation..... | 32 | +| 8.2.8.3 | Abnormal Conditions..... | 32 | +| 8.2.9 | Resource Status Reporting Initiation..... | 32 | +| 8.2.9.1 | General..... | 32 | +| 8.2.9.2 | Successful Operation..... | 33 | +| 8.2.9.3 | Unsuccessful Operation..... | 33 | +| 8.2.9.4 | Abnormal Conditions..... | 33 | +| 8.2.10 | Resource Status Reporting..... | 34 | +| 8.2.10.1 | General..... | 34 | +| 8.2.10.2 | Successful Operation..... | 34 | +| 8.2.10.3 | Unsuccessful Operation..... | 34 | +| 8.2.10.4 | Abnormal Conditions..... | 34 | +| 8.3 | Bearer Context Management procedures..... | 34 | +| 8.3.1 | Bearer Context Setup..... | 34 | +| 8.3.1.1 | General..... | 34 | +| 8.3.1.2 | Successful Operation..... | 35 | +| 8.3.1.3 | Unsuccessful Operation..... | 40 | +| 8.3.1.4 | Abnormal Conditions..... | 40 | +| 8.3.2 | Bearer Context Modification (gNB-CU-CP initiated)..... | 40 | +| 8.3.2.1 | General..... | 40 | +| 8.3.2.2 | Successful Operation..... | 41 | +| 8.3.2.3 | Unsuccessful Operation..... | 47 | +| 8.3.2.4 | Abnormal Conditions..... | 47 | +| 8.3.3 | Bearer Context Modification Required (gNB-CU-UP initiated)..... | 48 | +| 8.3.3.1 | General..... | 48 | + +| | | | +|----------|-----------------------------------------------------------|----| +| 8.3.3.2 | Successful Operation..... | 48 | +| 8.3.3.3 | Abnormal Conditions..... | 48 | +| 8.3.4 | Bearer Context Release (gNB-CU-CP initiated)..... | 48 | +| 8.3.4.1 | General..... | 48 | +| 8.3.4.2 | Successful Operation..... | 49 | +| 8.3.4.3 | Abnormal Conditions..... | 49 | +| 8.3.5 | Bearer Context Release Request (gNB-CU-UP initiated)..... | 49 | +| 8.3.5.1 | General..... | 49 | +| 8.3.5.2 | Successful Operation..... | 49 | +| 8.3.5.3 | Abnormal Conditions..... | 50 | +| 8.3.6 | Bearer Context Inactivity Notification..... | 50 | +| 8.3.6.1 | General..... | 50 | +| 8.3.6.2 | Successful Operation..... | 50 | +| 8.3.6.3 | Abnormal Conditions..... | 50 | +| 8.3.7 | DL Data Notification..... | 51 | +| 8.3.7.1 | General..... | 51 | +| 8.3.7.2 | Successful Operation..... | 51 | +| 8.3.7.3 | Abnormal Conditions..... | 51 | +| 8.3.8 | Data Usage Report..... | 51 | +| 8.3.8.1 | General..... | 51 | +| 8.3.8.2 | Successful Operation..... | 52 | +| 8.3.8.3 | Abnormal Conditions..... | 52 | +| 8.3.9 | gNB-CU-UP Counter Check..... | 52 | +| 8.3.9.1 | General..... | 52 | +| 8.3.9.2 | Successful Operation..... | 52 | +| 8.3.9.3 | Unsuccessful Operation..... | 52 | +| 8.3.9.4 | Abnormal Conditions..... | 52 | +| 8.3.10 | UL Data Notification..... | 53 | +| 8.3.10.1 | General..... | 53 | +| 8.3.10.2 | Successful Operation..... | 53 | + +| | | | +|----------|------------------------------------------------|----| +| 8.3.10.3 | Abnormal Conditions..... | 53 | +| 8.3.11 | MR-DC Data Usage Report..... | 53 | +| 8.3.11.1 | General..... | 53 | +| 8.3.11.2 | Successful Operation..... | 53 | +| 8.3.11.3 | Abnormal Conditions..... | 54 | +| 8.3.12 | Early Forwarding SN Transfer..... | 54 | +| 8.3.12.1 | General..... | 54 | +| 8.3.12.2 | Successful Operation..... | 54 | +| 8.3.12.3 | Unsuccessful Operation..... | 54 | +| 8.3.12.4 | Abnormal Conditions..... | 54 | +| 8.3.13 | GNB-CU-CP Measurement Results Information..... | 54 | +| 8.3.13.1 | General..... | 54 | +| 8.3.13.2 | Successful Operation..... | 55 | +| 8.3.13.3 | Abnormal Conditions..... | 55 | +| 8.4 | Trace Procedures..... | 55 | +| 8.4.1 | Trace Start..... | 55 | +| 8.4.1.1 | General..... | 55 | +| 8.4.1.2 | Successful Operation..... | 55 | +| 8.4.1.3 | Abnormal Conditions..... | 55 | +| 8.4.2 | Deactivate Trace..... | 56 | +| 8.4.2.1 | General..... | 56 | +| 8.4.2.2 | Successful Operation..... | 56 | +| 8.4.2.3 | Abnormal Conditions..... | 56 | +| 8.4.3 | Cell Traffic Trace..... | 56 | +| 8.4.3.1 | General..... | 56 | +| 8.4.3.2 | Successful Operation..... | 56 | +| 8.4.3.3 | Abnormal Conditions..... | 57 | +| 8.5 | IAB Procedures..... | 57 | +| 8.5.1 | IAB UP TNL Address Update..... | 57 | +| 8.5.1.1 | General..... | 57 | + +| | | | +|-----------|--------------------------------------------------------------|----| +| 8.5.1.2 | Successful Operation..... | 57 | +| 8.5.1.3 | Unsuccessful Operation..... | 58 | +| 8.5.1.4 | Abnormal Conditions..... | 58 | +| 8.5.2 | IAB PSK Notification..... | 58 | +| 8.5.2.1 | General..... | 58 | +| 8.5.2.2 | Successful Operation..... | 58 | +| 8.5.2.3 | Abnormal Conditions..... | 59 | +| 8.6 | MBS Procedures..... | 59 | +| 8.6.1 | MBS Procedures for Broadcast..... | 59 | +| 8.6.1.1 | BC Bearer Context Setup..... | 59 | +| 8.6.1.1.1 | General..... | 59 | +| 8.6.1.1.2 | Successful Operation..... | 59 | +| 8.6.1.1.3 | Unsuccessful Operation..... | 60 | +| 8.6.1.1.4 | Abnormal Conditions..... | 60 | +| 8.6.1.2 | BC Bearer Context Modification (gNB-CU-CP initiated)..... | 60 | +| 8.6.1.2.1 | General..... | 60 | +| 8.6.1.2.2 | Successful Operation..... | 61 | +| 8.6.1.2.3 | Unsuccessful Operation..... | 62 | +| 8.6.1.2.4 | Abnormal Conditions..... | 62 | +| 8.6.1.3 | BC Bearer Context Modification Required..... | 62 | +| 8.6.1.3.1 | General..... | 62 | +| 8.6.1.3.2 | Successful Operation..... | 62 | +| 8.6.1.3.3 | Abnormal Conditions..... | 63 | +| 8.6.1.4 | BC Bearer Context Release (gNB-CU-CP initiated)..... | 63 | +| 8.6.1.4.1 | General..... | 63 | +| 8.6.1.4.2 | Successful Operation..... | 63 | +| 8.6.1.4.3 | Abnormal Conditions..... | 63 | +| 8.6.1.5 | BC Bearer Context Release Request (gNB-CU-UP initiated)..... | 63 | +| 8.6.1.5.1 | General..... | 63 | +| 8.6.1.5.2 | Successful Operation..... | 64 | + +| | | | +|-----------|--------------------------------------------------------------------|----| +| 8.6.1.5.3 | Abnormal Conditions..... | 64 | +| 8.6.2 | MBS Procedures for Multicast..... | 64 | +| 8.6.2.1 | MC Bearer Context Setup..... | 64 | +| 8.6.2.1.1 | General..... | 64 | +| 8.6.2.1.2 | Successful Operation..... | 64 | +| 8.6.2.1.3 | Unsuccessful Operation..... | 66 | +| 8.6.2.1.4 | Abnormal Conditions..... | 66 | +| 8.6.2.2 | MC Bearer Context Modification (gNB-CU-CP initiated)..... | 66 | +| 8.6.2.2.1 | General..... | 66 | +| 8.6.2.2.2 | Successful Operation..... | 66 | +| 8.6.2.2.3 | Unsuccessful Operation..... | 68 | +| 8.6.2.2.4 | Abnormal Conditions..... | 68 | +| 8.6.2.3 | MC Bearer Context Modification Required (gNB-CU-UP initiated)..... | 69 | +| 8.6.2.3.1 | General..... | 69 | +| 8.6.2.3.2 | Successful Operation..... | 69 | +| 8.6.2.3.3 | Abnormal Conditions..... | 69 | +| 8.6.2.4 | MC Bearer Context Release (gNB-CU-CP initiated)..... | 69 | +| 8.6.2.4.1 | General..... | 69 | +| 8.6.2.4.2 | Successful Operation..... | 70 | +| 8.6.2.4.3 | Abnormal Conditions..... | 70 | +| 8.6.2.5 | MC Bearer Context Release Request (gNB-CU-UP initiated)..... | 70 | +| 8.6.2.5.1 | General..... | 70 | +| 8.6.2.5.2 | Successful Operation..... | 70 | +| 8.6.2.5.3 | Abnormal Conditions..... | 71 | +| 8.6.2.6 | MC Bearer Notification..... | 71 | +| 8.6.2.6.1 | General..... | 71 | +| 8.6.2.6.2 | Successful Operation..... | 71 | +| 8.6.2.6.3 | Abnormal Conditions..... | 71 | +| 9 | Elements for E1AP communication..... | 71 | +| 9.1 | General..... | 71 | + +| | | | +|----------|-------------------------------------------------|----| +| 9.2 | Message Functional Definition and Content..... | 72 | +| 9.2.1 | Interface Management messages..... | 72 | +| 9.2.1.1 | RESET..... | 72 | +| 9.2.1.2 | RESET ACKNOWLEDGE..... | 72 | +| 9.2.1.3 | ERROR INDICATION..... | 73 | +| 9.2.1.4 | GNB-CU-UP E1 SETUP REQUEST..... | 73 | +| 9.2.1.5 | GNB-CU-UP E1 SETUP RESPONSE..... | 74 | +| 9.2.1.6 | GNB-CU-UP E1 SETUP FAILURE..... | 74 | +| 9.2.1.7 | GNB-CU-CP E1 SETUP REQUEST..... | 75 | +| 9.2.1.8 | GNB-CU-CP E1 SETUP RESPONSE..... | 75 | +| 9.2.1.9 | GNB-CU-CP E1 SETUP FAILURE..... | 76 | +| 9.2.1.10 | GNB-CU-UP CONFIGURATION UPDATE..... | 76 | +| 9.2.1.11 | GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE..... | 77 | +| 9.2.1.12 | GNB-CU-UP CONFIGURATION UPDATE FAILURE..... | 77 | +| 9.2.1.13 | GNB-CU-CP CONFIGURATION UPDATE..... | 78 | +| 9.2.1.14 | GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE..... | 79 | +| 9.2.1.15 | GNB-CU-CP CONFIGURATION UPDATE FAILURE..... | 79 | +| 9.2.1.16 | E1 RELEASE REQUEST..... | 80 | +| 9.2.1.17 | E1 RELEASE RESPONSE..... | 80 | +| 9.2.1.18 | GNB-CU-UP STATUS INDICATION..... | 80 | +| 9.2.1.19 | RESOURCE STATUS REQUEST..... | 80 | +| 9.2.1.20 | RESOURCE STATUS RESPONSE..... | 81 | +| 9.2.1.21 | RESOURCE STATUS FAILURE..... | 82 | +| 9.2.1.22 | RESOURCE STATUS UPDATE..... | 82 | +| 9.2.2 | Bearer Context Management messages..... | 82 | +| 9.2.2.1 | BEARER CONTEXT SETUP REQUEST..... | 82 | +| 9.2.2.2 | BEARER CONTEXT SETUP RESPONSE..... | 84 | +| 9.2.2.3 | BEARER CONTEXT SETUP FAILURE..... | 84 | +| 9.2.2.4 | BEARER CONTEXT MODIFICATION REQUEST..... | 85 | +| 9.2.2.5 | BEARER CONTEXT MODIFICATION RESPONSE..... | 86 | + +| | | | +|-----------|------------------------------------------------|----| +| 9.2.2.6 | BEARER CONTEXT MODIFICATION FAILURE..... | 88 | +| 9.2.2.7 | BEARER CONTEXT MODIFICATION REQUIRED..... | 88 | +| 9.2.2.8 | BEARER CONTEXT MODIFICATION CONFIRM..... | 88 | +| 9.2.2.9 | BEARER CONTEXT RELEASE COMMAND..... | 89 | +| 9.2.2.10 | BEARER CONTEXT RELEASE COMPLETE..... | 89 | +| 9.2.2.11 | BEARER CONTEXT RELEASE REQUEST..... | 90 | +| 9.2.2.12 | BEARER CONTEXT INACTIVITY NOTIFICATION..... | 90 | +| 9.2.2.13 | DL DATA NOTIFICATION..... | 91 | +| 9.2.2.14 | DATA USAGE REPORT..... | 91 | +| 9.2.2.15 | GNB-CU-UP COUNTER CHECK REQUEST..... | 92 | +| 9.2.2.16 | UL DATA NOTIFICATION..... | 93 | +| 9.2.2.17 | MR-DC DATA USAGE REPORT..... | 93 | +| 9.2.2.18 | EARLY FORWARDING SN TRANSFER..... | 94 | +| 9.2.2.19 | GNB-CU-CP MEASUREMENT RESULTS INFORMATION..... | 94 | +| 9.2.3 | Trace Messages..... | 95 | +| 9.2.3.1 | TRACE START..... | 95 | +| 9.2.3.2 | DEACTIVATE TRACE..... | 95 | +| 9.2.3.3 | CELL TRAFFIC TRACE..... | 95 | +| 9.2.4 | IAB Messages..... | 96 | +| 9.2.4.1 | IAB UP TNL ADDRESS UPDATE..... | 96 | +| 9.2.4.2 | IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE..... | 97 | +| 9.2.4.3 | IAB UP TNL ADDRESS UPDATE FAILURE..... | 97 | +| 9.2.4.4 | IAB PSK NOTIFICATION..... | 97 | +| 9.2.5 | MBS Messages..... | 98 | +| 9.2.5.1 | MBS Messages for Broadcast..... | 98 | +| 9.2.5.1.1 | BC BEARER CONTEXT SETUP REQUEST..... | 98 | +| 9.2.5.1.2 | BC BEARER CONTEXT SETUP RESPONSE..... | 98 | +| 9.2.5.1.3 | BC BEARER CONTEXT SETUP FAILURE..... | 98 | +| 9.2.5.1.4 | BC BEARER CONTEXT MODIFICATION REQUEST..... | 99 | +| 9.2.5.1.5 | BC BEARER CONTEXT MODIFICATION RESPONSE..... | 99 | + +| | | | +|------------|----------------------------------------------|-----| +| 9.2.5.1.6 | BC BEARER CONTEXT MODIFICATION FAILURE..... | 99 | +| 9.2.5.1.7 | BC BEARER CONTEXT MODIFICATION REQUIRED..... | 99 | +| 9.2.5.1.8 | BC BEARER CONTEXT MODIFICATION CONFIRM..... | 100 | +| 9.2.5.1.9 | BC BEARER CONTEXT RELEASE COMMAND..... | 100 | +| 9.2.5.1.10 | BC BEARER CONTEXT RELEASE COMPLETE..... | 100 | +| 9.2.5.1.11 | BC BEARER CONTEXT RELEASE REQUEST..... | 101 | +| 9.2.5.2 | MBS Messages for Multicast..... | 101 | +| 9.2.5.2.1 | MC BEARER CONTEXT SETUP REQUEST..... | 101 | +| 9.2.5.2.2 | MC BEARER CONTEXT SETUP RESPONSE..... | 101 | +| 9.2.5.2.3 | MC BEARER CONTEXT SETUP FAILURE..... | 101 | +| 9.2.5.2.4 | MC BEARER CONTEXT MODIFICATION REQUEST..... | 102 | +| 9.2.5.2.5 | MC BEARER CONTEXT MODIFICATION RESPONSE..... | 102 | +| 9.2.5.2.6 | MC BEARER CONTEXT MODIFICATION FAILURE..... | 102 | +| 9.2.5.2.7 | MC BEARER CONTEXT MODIFICATION REQUIRED..... | 103 | +| 9.2.5.2.8 | MC BEARER CONTEXT MODIFICATION CONFIRM..... | 103 | +| 9.2.5.2.9 | MC BEARER CONTEXT RELEASE COMMAND..... | 103 | +| 9.2.5.2.10 | MC BEARER CONTEXT RELEASE COMPLETE..... | 103 | +| 9.2.5.2.11 | MC BEARER CONTEXT RELEASE REQUEST..... | 104 | +| 9.2.5.2.12 | MC BEARER NOTIFICATION..... | 104 | +| 9.3 | Information Element Definitions..... | 104 | +| 9.3.1 | Radio Network Layer Related IEs..... | 104 | +| 9.3.1.1 | Message Type..... | 104 | +| 9.3.1.2 | Cause..... | 105 | +| 9.3.1.3 | Criticality Diagnostics..... | 109 | +| 9.3.1.4 | gNB-CU-CP UE E1AP ID..... | 109 | +| 9.3.1.5 | gNB-CU-UP UE E1AP ID..... | 109 | +| 9.3.1.6 | Time To wait..... | 110 | +| 9.3.1.7 | PLMN Identity..... | 110 | +| 9.3.1.8 | Slice Support List..... | 110 | +| 9.3.1.9 | S-NSSAI..... | 110 | + +| | | | +|-----------|-------------------------------------------------|-----| +| 9.3.1.10 | Security Information..... | 111 | +| 9.3.1.11 | Cell Group Information..... | 111 | +| 9.3.1.12 | QoS Flow List..... | 112 | +| 9.3.1.13 | UP Parameters..... | 112 | +| 9.3.1.14 | NR CGI..... | 113 | +| 9.3.1.15 | gNB-CU-UP ID..... | 113 | +| 9.3.1.16 | DRB ID..... | 113 | +| 9.3.1.16a | MRB ID..... | 113 | +| 9.3.1.17 | E-UTRAN QoS..... | 113 | +| 9.3.1.18 | E-UTRAN Allocation and Retention Priority..... | 114 | +| 9.3.1.19 | GBR QoS Information..... | 114 | +| 9.3.1.20 | Bit Rate..... | 115 | +| 9.3.1.21 | PDU Session ID..... | 115 | +| 9.3.1.22 | PDU Session Type..... | 115 | +| 9.3.1.23 | Security Indication..... | 116 | +| 9.3.1.24 | QoS Flow Identifier..... | 116 | +| 9.3.1.25 | QoS Flow QoS Parameters List..... | 116 | +| 9.3.1.26 | QoS Flow Level QoS Parameters..... | 117 | +| 9.3.1.27 | Non Dynamic 5QI Descriptor..... | 118 | +| 9.3.1.28 | Dynamic 5QI Descriptor..... | 119 | +| 9.3.1.29 | NG-RAN Allocation and Retention Priority..... | 120 | +| 9.3.1.30 | GBR QoS Flow Information..... | 121 | +| 9.3.1.31 | Security Algorithm..... | 121 | +| 9.3.1.32 | User Plane Security Keys..... | 122 | +| 9.3.1.33 | UL Configuration..... | 122 | +| 9.3.1.34 | gNB-CU-UP Cell Group Related Configuration..... | 122 | +| 9.3.1.35 | PDCP Count..... | 123 | +| 9.3.1.35a | MBS PDCP COUNT..... | 123 | +| 9.3.1.36 | NR CGI Support List..... | 123 | +| 9.3.1.37 | QoS Parameters Support List..... | 123 | + +| | | | +|----------|--------------------------------------------|-----| +| 9.3.1.38 | PDCP Configuration..... | 124 | +| 9.3.1.39 | SDAP Configuration..... | 126 | +| 9.3.1.40 | ROHC Parameters..... | 127 | +| 9.3.1.41 | T-Reordering Timer..... | 128 | +| 9.3.1.42 | Discard Timer..... | 128 | +| 9.3.1.43 | UL Data Split Threshold..... | 128 | +| 9.3.1.44 | Data Usage Report List..... | 129 | +| 9.3.1.45 | Flow Failed List..... | 130 | +| 9.3.1.46 | Packet Loss Rate..... | 130 | +| 9.3.1.47 | Packet Delay Budget..... | 130 | +| 9.3.1.48 | Packet Error Rate..... | 130 | +| 9.3.1.49 | Averaging Window..... | 130 | +| 9.3.1.50 | Maximum Data Burst Volume..... | 131 | +| 9.3.1.51 | Priority Level..... | 131 | +| 9.3.1.52 | Security Result..... | 131 | +| 9.3.1.53 | Transaction ID..... | 131 | +| 9.3.1.54 | Inactivity timer..... | 131 | +| 9.3.1.55 | Paging Priority Indicator (PPI)..... | 132 | +| 9.3.1.56 | gNB-CU-UP Capacity..... | 132 | +| 9.3.1.57 | Maximum Integrity Protected Data Rate..... | 132 | +| 9.3.1.58 | PDCP SN Status Information..... | 132 | +| 9.3.1.59 | QoS Flow Mapping List..... | 133 | +| 9.3.1.60 | QoS Flow Mapping Indication..... | 133 | +| 9.3.1.61 | PDCP SN Size..... | 133 | +| 9.3.1.62 | Network Instance..... | 134 | +| 9.3.1.63 | MR-DC Usage Information..... | 134 | +| 9.3.1.64 | MR-DC Data Usage Report List..... | 134 | +| 9.3.1.65 | gNB-DU ID..... | 135 | +| 9.3.1.66 | Common Network Instance..... | 135 | +| 9.3.1.67 | Activity Notification Level..... | 135 | + +| | | | +|----------|-------------------------------------------------------|-----| +| 9.3.1.68 | Trace Activation..... | 136 | +| 9.3.1.69 | Subscriber Profile ID for RAT/Frequency priority..... | 137 | +| 9.3.1.70 | Additional RRM Policy Index..... | 137 | +| 9.3.1.71 | Retainability Measurements Information..... | 137 | +| 9.3.1.72 | TNL Available Capacity Indicator..... | 138 | +| 9.3.1.73 | HW Capacity Indicator..... | 138 | +| 9.3.1.74 | Redundant QoS Flow Indicator..... | 138 | +| 9.3.1.75 | TSC Traffic Characteristics..... | 138 | +| 9.3.1.76 | TSC Assistance Information..... | 139 | +| 9.3.1.77 | Periodicity..... | 139 | +| 9.3.1.78 | Burst Arrival Time..... | 139 | +| 9.3.1.79 | Extended Packet Delay Budget..... | 139 | +| 9.3.1.80 | Redundant PDU Session Information..... | 139 | +| 9.3.1.81 | QoS Mapping Information..... | 140 | +| 9.3.1.82 | NID..... | 140 | +| 9.3.1.83 | NPN Support Information..... | 140 | +| 9.3.1.84 | NPN Context Information..... | 140 | +| 9.3.1.85 | MDT Configuration..... | 141 | +| 9.3.1.86 | M4 Configuration..... | 141 | +| 9.3.1.87 | M6 Configuration..... | 142 | +| 9.3.1.88 | M7 Configuration..... | 142 | +| 9.3.1.89 | MDT PLMN List..... | 142 | +| 9.3.1.90 | EHC Parameters..... | 142 | +| 9.3.1.91 | DAPS Request Information..... | 144 | +| 9.3.1.92 | Early Forwarding COUNT Information..... | 144 | +| 9.3.1.93 | Alternative QoS Parameters Set List..... | 144 | +| 9.3.1.94 | Extended Slice Support List..... | 145 | +| 9.3.1.95 | Extended gNB-CU-CP Name..... | 145 | +| 9.3.1.96 | Extended gNB-CU-UP Name..... | 145 | +| 9.3.1.97 | Extended NR CGI Support List..... | 145 | + +| | | | +|-----------|----------------------------------------------------------------|-----| +| 9.3.1.98 | Direct Forwarding Path Availability..... | 146 | +| 9.3.1.99 | IAB-donor-CU-UP PSK Info..... | 146 | +| 9.3.1.100 | ECGI Support List..... | 146 | +| 9.3.1.101 | ECGI..... | 146 | +| 9.3.1.102 | UE Slice Maximum Bit Rate List..... | 146 | +| 9.3.1.103 | Survival Time..... | 147 | +| 9.3.1.104 | UDC Parameters..... | 147 | +| 9.3.1.105 | SCG Activation Status..... | 148 | +| 9.3.1.106 | gNB-CU-CP MBS EIAP ID..... | 148 | +| 9.3.1.107 | gNB-CU-UP MBS EIAP ID..... | 148 | +| 9.3.1.108 | Global MBS Session ID..... | 148 | +| 9.3.1.109 | DU Cell Reference..... | 149 | +| 9.3.1.110 | gNB-CU-UP MBS Support Information..... | 149 | +| 9.3.1.111 | MBS Area Session ID..... | 149 | +| 9.3.1.112 | BC Bearer Context NG-U TNL Info at 5GC..... | 149 | +| 9.3.1.113 | MBS NG-U Information at 5GC..... | 150 | +| 9.3.1.114 | BC MRB Setup Configuration..... | 150 | +| 9.3.1.115 | Requested Action for Available Shared NG-U Termination..... | 151 | +| 9.3.1.116 | BC Bearer Context NG-U TNL Info at NG-RAN..... | 151 | +| 9.3.1.117 | MBS NG-U Information at NG-RAN..... | 151 | +| 9.3.1.118 | BC Bearer Context F1-U TNL Info at CU..... | 151 | +| 9.3.1.119 | BC Bearer Context F1-U TNL Info at DU..... | 152 | +| 9.3.1.120 | MC MRB Setup Configuration..... | 152 | +| 9.3.1.121 | MC Bearer Context NG-U TNL Info at NG-RAN..... | 153 | +| 9.3.1.122 | MC Bearer Context NG-U TNL Info at 5GC..... | 153 | +| 9.3.1.123 | MC Bearer Context NG-U TNL Info at NG-RAN Request..... | 153 | +| 9.3.1.124 | MC Bearer Context F1-U TNL Info at DU..... | 153 | +| 9.3.1.125 | MBS Multicast F1-U Context Descriptor..... | 154 | +| 9.3.1.126 | Void..... | 154 | +| 9.3.1.127 | MC Bearer Context NG-U TNL Info at NG-RAN Modify Response..... | 154 | + +| | | | +|-----------|----------------------------------------------------------------|-----| +| 9.3.1.128 | Discard Timer Extended..... | 155 | +| 9.3.1.129 | MDT PLMN Modification List..... | 155 | +| 9.3.1.130 | MRB Progress Information..... | 155 | +| 9.3.1.131 | MRB Progress Information Type..... | 155 | +| 9.3.1.132 | MC Forwarding Resource ID..... | 155 | +| 9.3.1.133 | MBS Session Associated Information..... | 156 | +| 9.3.1.134 | MC Forwarding Resource Request..... | 156 | +| 9.3.1.135 | MC Forwarding Resource Indication..... | 156 | +| 9.3.1.136 | MC Forwarding Resource Response..... | 157 | +| 9.3.1.137 | MC Forwarding Resource Release..... | 157 | +| 9.3.1.138 | MC Forwarding Resource Release Indication..... | 157 | +| 9.3.1.139 | Multicast F1-U Context ReferenceE1..... | 157 | +| 9.3.1.140 | MBS Session Associated Information Non-Support-to-Support..... | 157 | +| 9.3.1.141 | MBS Session Associated Information List..... | 158 | +| 9.3.1.142 | MT-SDT Information..... | 158 | +| 9.3.1.143 | PDU Set QoS Parameters..... | 158 | +| 9.3.1.144 | N6 Jitter Information..... | 159 | +| 9.3.1.145 | ECN Marking or Congestion Information Reporting Request..... | 159 | +| 9.3.2 | Transport Network Layer Related IEs..... | 159 | +| 9.3.2.1 | UP Transport Layer Information..... | 159 | +| 9.3.2.2 | CP Transport Layer Information..... | 160 | +| 9.3.2.3 | GTP-TEID..... | 160 | +| 9.3.2.4 | Transport Layer Address..... | 160 | +| 9.3.2.5 | Data Forwarding Information Request..... | 160 | +| 9.3.2.6 | Data Forwarding Information..... | 161 | +| 9.3.2.7 | Transport Network Layer Address Info..... | 161 | +| 9.3.2.8 | URI..... | 162 | +| 9.3.3 | Container and List IE definitions..... | 162 | +| 9.3.3.1 | DRB To Setup List E-UTRAN..... | 162 | +| 9.3.3.2 | PDU Session Resource To Setup List..... | 163 | + +| | | | +|----------|------------------------------------------------------|-----| +| 9.3.3.3 | DRB Setup List E-UTRAN..... | 164 | +| 9.3.3.4 | DRB Failed List E-UTRAN..... | 165 | +| 9.3.3.5 | PDU Session Resource Setup List..... | 165 | +| 9.3.3.6 | PDU Session Resource Failed List..... | 166 | +| 9.3.3.7 | DRB To Setup Modification List E-UTRAN..... | 166 | +| 9.3.3.8 | DRB To Modify List E-UTRAN..... | 167 | +| 9.3.3.9 | DRB To Remove List E-UTRAN..... | 168 | +| 9.3.3.10 | PDU Session Resource To Setup Modification List..... | 168 | +| 9.3.3.11 | PDU Session Resource To Modify List..... | 169 | +| 9.3.3.12 | PDU Session Resource To Remove List..... | 173 | +| 9.3.3.13 | DRB Setup Modification List E-UTRAN..... | 173 | +| 9.3.3.14 | DRB Failed Modification List E-UTRAN..... | 174 | +| 9.3.3.15 | DRB Modified List E-UTRAN..... | 174 | +| 9.3.3.16 | DRB Failed To Modify List E-UTRAN..... | 174 | +| 9.3.3.17 | PDU Session Resource Setup Modification List..... | 174 | +| 9.3.3.18 | PDU Session Resource Failed Modification List..... | 175 | +| 9.3.3.19 | PDU Session Resource Modified List..... | 176 | +| 9.3.3.20 | PDU Session Resource Failed To Modify List..... | 177 | +| 9.3.3.21 | DRB Required To Modify List E-UTRAN..... | 177 | +| 9.3.3.22 | DRB Required To Remove List E-UTRAN..... | 177 | +| 9.3.3.23 | PDU Session Resource Required To Modify List..... | 178 | +| 9.3.3.24 | DRB Confirm Modified List E-UTRAN..... | 178 | +| 9.3.3.25 | PDU Session Resource Confirm Modified List..... | 179 | +| 9.3.3.26 | BC Bearer Context To Setup..... | 179 | +| 9.3.3.27 | BC Bearer Context To Setup Response..... | 179 | +| 9.3.3.28 | BC Bearer Context To Modify..... | 180 | +| 9.3.3.29 | BC Bearer Context To Modify Response..... | 181 | +| 9.3.3.30 | BC Bearer Context To Modify Required..... | 181 | +| 9.3.3.31 | BC Bearer Context To Modify Confirm..... | 181 | +| 9.3.3.32 | MC Bearer Context To Setup..... | 181 | + +| | | | +|----------|-------------------------------------------------------------------|-----| +| 9.3.3.33 | MC Bearer Context To Setup Response..... | 182 | +| 9.3.3.34 | MC Bearer Context To Modify..... | 182 | +| 9.3.3.35 | MC Bearer Context To Modify Response..... | 183 | +| 9.3.3.36 | MC Bearer Context To Modify Required..... | 184 | +| 9.3.3.37 | MC Bearer Context To Modify Confirm..... | 185 | +| 9.3.3.38 | Associated Session ID..... | 185 | +| 9.3.3.39 | MBS Service Area..... | 185 | +| 9.3.3.40 | MBS Service Area information..... | 185 | +| 9.3.3.41 | 5GS TAC..... | 186 | +| 9.4 | Message and Information Element Abstract Syntax (with ASN.1)..... | 186 | +| 9.4.1 | General..... | 186 | +| 9.4.2 | Usage of private message mechanism for non-standard use..... | 186 | +| 9.4.3 | Elementary Procedure Definitions..... | 188 | +| 9.4.4 | PDU Definitions..... | 198 | +| 9.4.5 | Information Element Definitions..... | 239 | +| 9.4.6 | Common Definitions..... | 311 | +| 9.4.7 | Constant Definitions..... | 312 | +| 9.4.8 | Container Definitions..... | 318 | +| 10 | Handling of unknown, unforeseen and erroneous protocol data..... | 322 | + +| | | | +|-------------------------------|-----------------------|------------| +| Annex A (informative): | Change History | 323 | +|-------------------------------|-----------------------|------------| + +--- + +## 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 5G radio network layer signalling protocol for the E1 interface. The E1 interface provides means for interconnecting a gNB-CU-CP and a gNB-CU-UP of a gNB within an NG-RAN, or for interconnecting a gNB-CU-CP and a gNB-CU-UP of an en-gNB within an E-UTRAN, or for interconnecting an eNB-CP and an eNB-UP of an eNB within an E-UTRAN, or for interconnecting an ng-eNB-CU-CP and an ng-eNB-CU-UP of an ng-eNB within an NG-RAN. The E1 Application Protocol (E1AP) supports the functions of E1 interface by signalling procedures defined in the present document. E1AP is developed in accordance to the general principles stated in TS 38.401 [2] and TS 37.480 [3]. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.401: "NG-RAN; Architecture Description". +- [3] 3GPP TS 37.480: "E1 general aspects and principles". +- [4] 3GPP TS 38.300: "NR; Overall description; Stage-2". +- [5] 3GPP TR 25.921 (version.7.0.0): "Guidelines and principles for protocol description and error". +- [6] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [7] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)". +- [8] ITU-T Recommendation X.680 (07/2002): "Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [9] ITU-T Recommendation X.681 (07/2002): "Information technology – Abstract Syntax Notation One (ASN.1): Information object specification". +- [10] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification". +- [11] 3GPP TS 23.401: "General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [12] 3GPP TS 23.203: "Policy and Charging Control Architecture". +- [13] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System". +- [14] IETF RFC 5905: "Network Time Protocol Version 4: Protocol and Algorithms Specification". + +- [15] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)". +- [16] 3GPP TS 38.414: "NG-RAN; NG Data Transport". +- [17] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification". +- [18] 3GPP TS 37.482: "E1 Signalling Transport". +- [19] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2". +- [20] 3GPP TS 23.501: "System Architecture for the 5G System". +- [21] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification". +- [22] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". +- [23] 3GPP TS 23.003: "Numbering, addressing and identification". +- [24] 3GPP TS 32.422: "Trace control and configuration management". +- [25] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [26] 3GPP TS 32.425: "Performance measurements; Evolved Universal Terrestrial Radio Access Network (E-UTRAN)". +- [27] 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". +- [28] 3GPP TS 38.474: "NG-RAN; F1 data transport". +- [29] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes; Stage 3". +- [30] 3GPP TS 37.470: "W1 interface; General aspects and principles". +- [31] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description". +- [32] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture". +- [33] 3GPP TS 36.331: "Radio Resource Control (RRC); Protocol specification". +- [34] 3GPP TS 36.323: " Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Packet Data Convergence Protocol (PDCP) specification". +- [35] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". + +--- + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +Elementary Procedure: E1AP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between gNB-CU-CP and gNB-CU-UP, or between eNB-CP and eNB-UP, or between ng-eNB-CU-CP and ng-eNB-CU-UP. 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 standalone procedures, which can be active in parallel. The usage of several E1AP EPs together is specified in stage 2 specifications (e.g., TS 37.480 [3]). + +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 and/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 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. + +Conditional handover: as defined in TS 38.300 [4]. + +**Conditional PSCell Change:** as defined in TS 37.340 [19]. + +DAPS Handover: as defined in TS 38.300 [4]. + +eNB-CP: as defined in TS 36.401 [31]. + +eNB-UP: as defined in TS 36.401 [31]. + +gNB: as defined in TS 38.300 [4]. + +gNB-CU: as defined in TS 38.401 [2]. + +gNB-DU: as defined in TS 38.401 [2]. + +gNB-CU-CP: as defined in TS 38.401 [2]. + +gNB-CU-UP: as defined in TS 38.401 [2]. + +**MBS-associated signalling:** When E1AP messages associated to one MBS session uses the MBS-associated logical E1-connection for association of the message to the MBS session in gNB-CU-CP and gNB-CU-UP. + +**MBS-associated logical E1-connection:** The MBS-associated logical E1-connection uses the identities *GNB-CU-CP MBS E1AP ID* and *GNB-CU-UP MBS E1AP ID* according to the definition in TS 38.401 [2]. For a received MBS-associated E1AP message the gNB-CU-CP identifies the associated MBS session based on the *GNB-CU-CP MBS E1AP ID* IE and the gNB-CU-UP identifies the associated MBS session based on the *GNB-CU-UP MBS E1AP ID* IE. + +**MBS session resource:** as defined in TS 38.401 [2]. + +**Multicast F1-U Context:** as defined in TS 38.401 [2]. + +ng-eNB-CU: as defined in TS 37.470 [30]. + +ng-eNB-CU-CP: as defined in TS 38.401 [2]. + +ng-eNB-CU-UP: as defined in TS 38.401 [2]. + +ng-eNB-DU: as defined in TS 37.470 [30]. + +PDU Session Resource: as defined in TS 38.401 [2]. + +UE-associated signalling: When EIAP messages associated to one UE uses the UE-associated logical E1-connection for association of the message to the UE in gNB-CU-UP and gNB-CU-CP, or in eNB-CP and eNB-UP, or in ng-eNB-CU-CP and ng-eNB-CU-UP. + +UE-associated logical E1-connection: The UE-associated logical E1-connection uses the identities *GNB-CU-CP UE EIAP ID* and *GNB-CU-UP UE EIAP ID* according to the definition in TS 38.401 [2]. For a received UE associated EIAP message the gNB-CU-CP or eNB-CP or ng-eNB-CU-CP identifies the associated UE based on the *GNB-CU-CP UE EIAP ID* IE and the gNB-CU-UP or eNB-UP or ng-eNB-CU-UP identifies the associated UE based on the *GNB-CU-UP UE EIAP ID* IE. + +Public Network Integrated NPN: as defined in TS 23.501 [20]. + +Stand-alone Non-Public Network: as defined in TS 23.501 [20]. + +U2N Remote UE: as defined in TS 38.300 [4]. + +Subsequent Conditional PSCell Addition or Change (subsequent CPAC): as defined in TS 37.340 [30] + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. + +An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|-------------------------------------------| +| 5GC | 5G Core Network | +| 5QI | 5G QoS Identifier | +| CAG | Closed Access Group | +| CGI | Cell Global Identifier | +| CHO | Conditional Handover | +| CN | Core Network | +| CP | Control Plane | +| CPA | Conditional PSCell Addition | +| CPAC | Conditional PSCell Addition or Change | +| CPC | Conditional PSCell Change | +| DAPS | Dual Active Protocol Stack | +| DL | Downlink | +| EHC | Ethernet Header Compression | +| EN-DC | E-UTRA-NR Dual Connectivity | +| EPC | Evolved Packet Core | +| IAB | Integrated Access and Backhaul | +| MBS | Multicast/Broadcast Service | +| MCG | Master Cell Group | +| MT-SDT | Mobile Terminated Small Data Transmission | + +| | | +|---------|-------------------------------------------------------| +| NID | Network Identifier | +| NPN | Non-Public Network | +| PNI-NPN | Public Network Integrated Non-Public Network | +| PTP | Point to Point | +| PTM | Point to Multipoint | +| NSSAI | Network Slice Selection Assistance Information | +| RANAC | RAN Area Code | +| SCG | Secondary Cell Group | +| SDAP | Service Data Adaptation Protocol | +| SDT | Small Data Transmission | +| SNPN | Stand-alone Non-Public Network | +| S-NSSAI | Single Network Slice Selection Assistance Information | +| TNLA | Transport Network Layer Association | +| U2N | UE-to-Network | +| UDC | Uplink Data Compression | + +--- + +## 4 General + +### 4.1 Procedure specification principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the terminating node exactly and completely. Any rule that specifies the behaviour of the originating node shall be possible to be verified with information that is visible within the system. + +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 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 clause 10. + +### 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. Handover Preparation 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. HANDOVER 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. E-RAB ID 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 the specification enclosed by quotation marks, e.g. "Value". | + +--- + +## 5 E1AP services + +E1AP provides the signalling service between the gNB-CU-CP and the gNB-CU-UP, or between the eNB-CP and the eNB-UP, or between the ng-eNB-CU-CP and the ng-eNB-CU-UP that is required to fulfil the E1AP functions described in clause 7. E1AP services are divided into three groups: + +| | | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Non UE-associated services: | They are related to the whole E1 interface instance between the gNB-CU-CP and gNB-CU-UP, or between the eNB-CP and eNB-UP, or between the ng-eNB-CU-CP and ng-eNB-CU-UP utilising a non UE-associated signalling connection. | +| UE-associated services: | They are related to one UE. E1AP functions that provide these services are associated with a UE-associated signalling connection that is maintained for the UE in question. | +| MBS-associated services: | They are related to one MBS session. E1AP functions that provide these services are associated with an MBS-associated signalling connection that is maintained for the MBS session in question. | + +Unless explicitly indicated in the procedure specification, at any instance in time one protocol endpoint shall have a maximum of one ongoing E1AP procedure related to a certain UE. + +Unless explicitly indicated in the procedure specification, at any instance in time one protocol endpoint shall have a maximum of one ongoing E1AP procedure related to a certain MBS session. + +--- + +## 6 Services expected from signalling transport + +The signalling connection shall provide in sequence delivery of E1AP messages. E1AP shall be notified if the signalling connection breaks. + +--- + +## 7 Functions of E1AP + +The functions of E1AP are described in TS 37.480 [3]. + +## 8 E1AP procedures + +NOTE: The procedures listed in this section should also be applied to CP/UP separation for eNB and ng-eNB, except for the IAB UP TNL Address Update procedure, if not stated otherwise. With this understanding, in this section each instance of gNB-CU-CP could be treated as eNB-CP or ng-eNB-CU-CP, and each gNB-CU-UP could be treated as eNB-UP or ng-eNB-CU-UP, for eNB or ng-eNB CP/UP separation respectively. + +### 8.1 List of E1AP Elementary Procedures + +In the following tables, all EPs are divided into Class 1 and Class 2 EPs (see subclause 3.1 for explanation of the different classes): + +**Table 1: Class 1 procedures** + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|------------------------------------------------------------|--------------------------------------|--------------------------------------------|----------------------------------------| +| | | Response message | Response message | +| Reset | RESET | RESET ACKNOWLEDGE | | +| gNB-CU-UP E1 Setup | GNB-CU-UP E1 SETUP REQUEST | GNB-CU-UP E1 SETUP RESPONSE | GNB-CU-UP E1 SETUP FAILURE | +| gNB-CU-CP E1 Setup | GNB-CU-CP E1 SETUP REQUEST | GNB-CU-CP E1 SETUP RESPONSE | GNB-CU-CP E1 SETUP FAILURE | +| gNB-CU-UP Configuration Update | GNB-CU-UP CONFIGURATION UPDATE | GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE | GNB-CU-UP CONFIGURATION UPDATE FAILURE | +| gNB-CU-CP Configuration Update | GNB-CU-CP CONFIGURATION UPDATE | GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE | GNB-CU-CP CONFIGURATION UPDATE FAILURE | +| E1 Release | E1 RELEASE REQUEST | E1 RELEASE RESPONSE | | +| Bearer Context Setup | BEARER CONTEXT SETUP REQUEST | BEARER CONTEXT SETUP RESPONSE | BEARER CONTEXT SETUP FAILURE | +| Bearer Context Modification (gNB-CU-CP initiated) | BEARER CONTEXT MODIFICATION REQUEST | BEARER CONTEXT MODIFICATION RESPONSE | BEARER CONTEXT MODIFICATION FAILURE | +| Bearer Context Modification Required (gNB-CU-UP initiated) | BEARER CONTEXT MODIFICATION REQUIRED | BEARER CONTEXT MODIFICATION CONFIRM | | +| Bearer Context Release (gNB-CU-CP initiated) | BEARER CONTEXT RELEASE COMMAND | BEARER CONTEXT RELEASE COMPLETE | | +| Resource Status Reporting Initiation | RESOURCE STATUS REQUEST | RESOURCE STATUS RESPONSE | RESOURCE STATUS FAILURE | +| IAB UP TNL Address Update | IAB UP TNL ADDRESS UPDATE | IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE | IAB UP TNL ADDRESS UPDATE FAILURE | +| BC Bearer Context Setup | BC BEARER CONTEXT SETUP REQUEST | BC BEARER CONTEXT SETUP RESPONSE | BC BEARER CONTEXT SETUP FAILURE | + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|---------------------------------------------------------------|-----------------------------------------|-----------------------------------------|----------------------------------------| +| | | Response message | Response message | +| BC Bearer Context Modification (gNB-CU-CP initiated) | BC BEARER CONTEXT MODIFICATION REQUEST | BC BEARER CONTEXT MODIFICATION RESPONSE | BC BEARER CONTEXT MODIFICATION FAILURE | +| BC Bearer Context Modification Required (gNB-CU-UP initiated) | BC BEARER CONTEXT MODIFICATION REQUIRED | BC BEARER CONTEXT MODIFICATION CONFIRM | | +| BC Bearer Context Release (gNB-CU-CP initiated) | BC BEARER CONTEXT RELEASE COMMAND | BC BEARER CONTEXT RELEASE COMPLETE | | +| MC Bearer Context Setup | MC BEARER CONTEXT SETUP REQUEST | MC BEARER CONTEXT SETUP RESPONSE | MC BEARER CONTEXT SETUP FAILURE | +| MC Bearer Context Modification (gNB-CU-CP initiated) | MC BEARER CONTEXT MODIFICATION REQUEST | MC BEARER CONTEXT MODIFICATION RESPONSE | MC BEARER CONTEXT MODIFICATION FAILURE | +| MC Bearer Context Modification Required (gNB-CU-UP initiated) | MC BEARER CONTEXT MODIFICATION REQUIRED | MC BEARER CONTEXT MODIFICATION CONFIRM | | +| MC Bearer Context Release (gNB-CU-CP initiated) | MC BEARER CONTEXT RELEASE COMMAND | MC BEARER CONTEXT RELEASE COMPLETE | | + +**Table 2: Class 2 procedures** + +| Elementary Procedure | Message | +|------------------------------------------------------|-------------------------------------------| +| Error Indication | ERROR INDICATION | +| Bearer Context Release Request (gNB-CU-UP initiated) | BEARER CONTEXT RELEASE REQUEST | +| Bearer Context Inactivity Notification | BEARER CONTEXT INACTIVITY NOTIFICATION | +| DL Data Notification | DL DATA NOTIFICATION | +| UL Data Notification | UL DATA NOTIFICATION | +| Data Usage Report | DATA USAGE REPORT | +| gNB-CU-UP Counter Check | GNB-CU-UP COUNTER CHECK | +| gNB-CU-UP Status Indication | GNB-CU-UP STATUS INDICATION | +| MR-DC Data Usage Report | MR-DC DATA USAGE REPORT | +| Trace Start | TRACE START | +| Deactivate Trace | DEACTIVATE TRACE | +| Resource Status Reporting | RESOURCE STATUS UPDATE | +| Early Forwarding SN Transfer | EARLY FORWARDING SN TRANSFER | +| GNB-CU-CP Measurement Results Information | GNB-CU-CP MEASUREMENT RESULTS INFORMATION | +| IAB PSK Notification | IAB PSK NOTIFICATION | +| BC Bearer Context Release (gNB-CU-UP initiated) | BC BEARER CONTEXT RELEASE REQUEST | +| BC Bearer Context Release (gNB-CU-UP initiated) | BC BEARER CONTEXT RELEASE REQUEST | +| MC Bearer Notification | MC BEARER NOTIFICATION | + +## 8.2 Interface Management procedures + +### 8.2.1 Reset + +#### 8.2.1.1 General + +The purpose of the Reset procedure is to initialise or re-initialise the E1AP UE-related contexts, in the event of a failure in the gNB-CU-CP or gNB-CU-UP. This procedure does not affect the application level configuration data exchanged during, e.g., the E1 Setup procedure. + +The procedure uses non-UE associated signalling. + +## 8.2.1.2 Successful Operation + +### 8.2.1.2.1 Reset Procedure Initiated from the gNB-CU-CP + +![Sequence diagram showing the Reset procedure initiated from the gNB-CU-CP. The gNB-CU-CP sends a RESET message to the gNB-CU-UP, and the gNB-CU-UP responds with a RESET ACKNOWLEDGE message.](7d2d1d3870cd224c4430d19334557716_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: (gNB-CU-CP) + gNB-CU-CP->>gNB-CU-UP: RESET + Note right of gNB-CU-UP: (gNB-CU-UP) + gNB-CU-UP-->>gNB-CU-CP: RESET ACKNOWLEDGE + +``` + +Sequence diagram showing the Reset procedure initiated from the gNB-CU-CP. The gNB-CU-CP sends a RESET message to the gNB-CU-UP, and the gNB-CU-UP responds with a RESET ACKNOWLEDGE message. + +**Figure 8.2.1.2.1-1: Reset procedure initiated from the gNB-CU-CP. Successful operation.** + +In the event of a failure at the gNB-CU-CP, which has resulted in the loss of some or all transaction reference information, a RESET message shall be sent to the gNB-CU-UP. + +At reception of the RESET message the gNB-CU-UP shall release all allocated resources on E1 related to the UE association(s) indicated explicitly or implicitly in the RESET message and remove the indicated bearer contexts including E1AP ID. + +After the gNB-CU-UP has released all assigned E1 resources and the UE E1AP IDs for all indicated UE associations which can be used for new UE-associated logical E1-connections over the E1 interface, the gNB-CU-UP shall respond with the RESET ACKNOWLEDGE message. The gNB-CU-UP does not need to wait for the release of bearer resources to be completed before returning the RESET ACKNOWLEDGE message. + +If the RESET message contains the *UE-associated logical E1-connection list* IE, then: + +- The gNB-CU-UP shall use the *gNB-CU-CP UE E1AP ID* IE and/or the *gNB-CU-UP UE E1AP ID* IE to explicitly identify the UE association(s) to be reset. +- The gNB-CU-UP shall include in the RESET ACKNOWLEDGE message, for each UE association to be reset, the *UE-associated logical E1-connection Item* IE in the *UE-associated logical E1-connection list* IE. The *UE-associated logical E1-connection Item* IEs shall be in the same order as received in the RESET message and shall include also unknown UE-associated logical E1-connections. Empty *UE-associated logical E1-connection Item* IEs, received in the RESET message, may be omitted in the RESET ACKNOWLEDGE message. +- If the *gNB-CU-CP UE E1AP ID* IE is included in the *UE-associated logical E1-connection Item* IE for a UE association, the gNB-CU-UP shall include the *gNB-CU-CP UE E1AP ID* IE in the corresponding *UE-associated logical E1-connection Item* IE in the RESET ACKNOWLEDGE message. +- If the *gNB-CU-UP UE E1AP ID* IE is included in the *UE-associated logical E1-connection Item* IE for a UE association, the gNB-CU-UP shall include the *gNB-CU-UP UE E1AP ID* IE in the corresponding *UE-associated logical E1-connection Item* IE in the RESET ACKNOWLEDGE message. + +#### Interactions with other procedures: + +If the RESET message is received, any other ongoing procedure (except for another Reset procedure) on the same E1 interface related to a UE association, indicated explicitly or implicitly in the RESET message, shall be aborted. + +### 8.2.1.2.2 Reset Procedure Initiated from the gNB-CU-UP + +![Sequence diagram showing the reset procedure initiated from the gNB-CU-UP. The gNB-CU-UP sends a RESET message to the gNB-CU-CP, which responds with a RESET ACKNOWLEDGE message.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: (Start of procedure) + gNB-CU-UP->>gNB-CU-CP: RESET + gNB-CU-CP-->>gNB-CU-UP: RESET ACKNOWLEDGE + Note right of gNB-CU-UP: (End of procedure) + +``` + +Sequence diagram showing the reset procedure initiated from the gNB-CU-UP. The gNB-CU-UP sends a RESET message to the gNB-CU-CP, which responds with a RESET ACKNOWLEDGE message. + +**Figure 8.2.1.2.2-1: Reset procedure initiated from the gNB-CU-UP. Successful operation.** + +In the event of a failure at the gNB-CU-UP, which has resulted in the loss of some or all transaction reference information, a RESET message shall be sent to the gNB-CU-CP. + +At reception of the RESET message the gNB-CU-CP shall release all allocated resources on E1 related to the UE association(s) indicated explicitly or implicitly in the RESET message and remove the E1AP ID for the indicated UE associations. + +After the gNB-CU-CP has released all assigned E1 resources and the UE E1AP IDs for all indicated UE associations which can be used for new UE-associated logical E1-connections over the E1 interface, the gNB-CU-CP shall respond with the RESET ACKNOWLEDGE message. The gNB-CU-CP does not need to wait for the release of bearer resources to be completed before returning the RESET ACKNOWLEDGE message. + +If the RESET message contains the *UE-associated logical E1-connection list* IE, then: + +- The gNB-CU-CP shall use the *gNB-CU-CP UE E1AP ID* IE and/or the *gNB-CU-UP UE E1AP ID* IE to explicitly identify the UE association(s) to be reset. +- The gNB-CU-CP shall in the RESET ACKNOWLEDGE message include, for each UE association to be reset, the *UE-associated logical E1-connection Item* IE in the *UE-associated logical E1-connection list* IE. The *UE-associated logical E1-connection Item* IEs shall be in the same order as received in the RESET message and shall include also unknown UE-associated logical E1-connections. Empty *UE-associated logical E1-connection Item* IEs, received in the RESET message, may be omitted in the RESET ACKNOWLEDGE message. +- If the *gNB-CU-CP UE E1AP ID* IE is included in the *UE-associated logical E1-connection Item* IE for a UE association, the gNB-CU-CP shall include the *gNB-CU-CP UE E1AP ID* IE in the corresponding *UE-associated logical E1-connection Item* IE in the RESET ACKNOWLEDGE message. +- If the *gNB-CU-UP UE E1AP ID* IE is included in a *UE-associated logical E1-connection Item* IE for a UE association, the gNB-CU-CP shall include the *gNB-CU-UP UE E1AP ID* IE in the corresponding *UE-associated logical E1-connection Item* IE in the RESET ACKNOWLEDGE message. + +#### Interactions with other procedures: + +If the RESET message is received, any other ongoing procedure (except for another Reset procedure) on the same E1 interface related to a UE association, indicated explicitly or implicitly in the RESET message, shall be aborted. + +### 8.2.1.3 Abnormal Conditions + +Not applicable. + +## 8.2.2 Error Indication + +### 8.2.2.1 General + +The Error Indication procedure is initiated by a node in order 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 UE associated signalling, then the Error Indication procedure uses UE associated signalling. Otherwise the procedure uses non-UE associated signalling. + +### 8.2.2.2 Successful Operation + +![Sequence diagram showing the Error Indication procedure originating from gNB-CU-CP to gNB-CU-UP.](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: ERROR INDICATION + Note right of gNB-CU-UP: +``` + +A sequence diagram illustrating the Error Indication procedure. It features two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. Each lifeline has a small horizontal bar at the bottom. A horizontal arrow labeled "ERROR INDICATION" points from the gNB-CU-CP lifeline to the gNB-CU-UP lifeline. + +Sequence diagram showing the Error Indication procedure originating from gNB-CU-CP to gNB-CU-UP. + +Figure 8.2.2.2-1: Error Indication procedure, gNB-CU-CP originated. Successful operation. + +![Sequence diagram showing the Error Indication procedure originating from gNB-CU-UP to gNB-CU-CP.](80ec3bf791fd8eb41f73a420c2122529_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-UP->>gNB-CU-CP: ERROR INDICATION + Note right of gNB-CU-UP: +``` + +A sequence diagram illustrating the Error Indication procedure. It features two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. Each lifeline has a small horizontal bar at the bottom. A horizontal arrow labeled "ERROR INDICATION" points from the gNB-CU-UP lifeline to the gNB-CU-CP lifeline. + +Sequence diagram showing the Error Indication procedure originating from gNB-CU-UP to gNB-CU-CP. + +Figure 8.2.2.2-2: Error Indication procedure, gNB-CU-UP 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. In case the Error Indication procedure is triggered by utilising UE associated signalling the *gNB-CU-CP UE EIAP ID* IE and *gNB-CU-UP UE EIAP ID* IE shall be included in the ERROR INDICATION message. If one or both of the *gNB-CU-CP UE EIAP ID* IE and the *gNB-CU-UP UE EIAP ID* IE are not correct, the cause shall be set to appropriate value, e.g., "Unknown or already allocated gNB-CU-CP UE EIAP ID", "Unknown or already allocated gNB-CU-UP UE EIAP ID" or "Unknown or inconsistent pair of UE EIAP ID". + +### 8.2.2.3 Abnormal Conditions + +Not applicable. + +## 8.2.3 gNB-CU-UP E1 Setup + +### 8.2.3.1 General + +The purpose of the gNB-CU-UP E1 Setup procedure is to exchange application level data needed for the gNB-CU-UP and the gNB-CU-CP to correctly interoperate on the E1 interface. If the gNB-CU-UP initiates the first TNL association, it shall also initiate the gNB-CU-UP E1 Setup procedure. The procedure uses non-UE associated signalling. + +This procedure erases any existing application level configuration data in the two nodes and replaces it by the one received. This procedure also re-initialises the E1AP UE-related contexts (if any) and erases all related signalling connections in the two nodes like a Reset procedure would do. + +### 8.2.3.2 Successful Operation + +![Sequence diagram of the gNB-CU-UP E1 Setup procedure: Successful Operation. The diagram shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. The gNB-CU-UP sends a 'GNB-CU-UP E1 SETUP REQUEST' message to the gNB-CU-CP. The gNB-CU-CP responds with a 'GNB-CU-UP E1 SETUP RESPONSE' message to the gNB-CU-UP. Both lifelines end with a solid black horizontal bar at the bottom.](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: gNB-CU-UP initiates procedure + gNB-CU-UP->>gNB-CU-CP: GNB-CU-UP E1 SETUP REQUEST + gNB-CU-CP-->>gNB-CU-UP: GNB-CU-UP E1 SETUP RESPONSE + +``` + +Sequence diagram of the gNB-CU-UP E1 Setup procedure: Successful Operation. The diagram shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. The gNB-CU-UP sends a 'GNB-CU-UP E1 SETUP REQUEST' message to the gNB-CU-CP. The gNB-CU-CP responds with a 'GNB-CU-UP E1 SETUP RESPONSE' message to the gNB-CU-UP. Both lifelines end with a solid black horizontal bar at the bottom. + +**Figure 8.2.3.2-1: gNB-CU-UP E1 Setup procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending a GNB-CU-UP E1 SETUP REQUEST message including the appropriate data to the gNB-CU-CP. The gNB-CU-CP responds with a GNB-CU-UP E1 SETUP RESPONSE message including the appropriate data. + +If the GNB-CU-UP E1 SETUP REQUEST message contains the *gNB-CU-UP Name* IE the gNB-CU-CP may use this IE as a human readable name of the gNB-CU-UP. If the GNB-CU-UP E1 SETUP REQUEST message contains the *Extended gNB-CU-UP Name* IE, the gNB-CU-CP may use this IE as a human readable name of the gNB-CU-UP and shall ignore the *gNB-CU-UP Name* IE if included. + +If the GNB-CU-UP E1 SETUP RESPONSE message contains the *gNB-CU-CP Name* IE, the gNB-CU-UP may use this IE as a human readable name of the gNB-CU-CP. If the GNB-CU-UP E1 SETUP RESPONSE message contains the *Extended gNB-CU-CP Name* IE, the gNB-CU-UP may use this IE as a human readable name of the gNB-CU-CP and shall ignore the *gNB-CU-CP Name* IE if included. + +If the *Slice Support List* IE is contained in the GNB-CU-UP E1 SETUP REQUEST message, the gNB-CU-CP shall store the corresponding information and it may take it into account for bearer context establishment. + +If the *NR CGI Support List* or the *Extended NR CGI Support List* IE is contained in the GNB-CU-UP E1 SETUP REQUEST message, the gNB-CU-CP shall store the corresponding information and it may take it into account for bearer context establishment. + +If the *ECGI Support List* IE is contained in the GNB-CU-UP E1 SETUP REQUEST message, the gNB-CU-CP shall store the corresponding information and it may take it into account for bearer context establishment. + +If the *QoS Parameters Support List* IE is contained in the GNB-CU-UP E1 SETUP REQUEST message, the gNB-CU-CP shall store the corresponding information and it may take it into account for bearer context establishment. + +If the *NPN Support Information* IE is contained in the GNB-CU-UP E1 SETUP REQUEST message, the gNB-CU-CP shall store the corresponding information and it may take it into account for bearer context establishment. + +The exchanged data shall be stored in respective node and used as long as there is an operational TNL association. When this procedure is finished, the E1 interface is operational and other E1 messages can be exchanged. + +If the *gNB-CU-UP Capacity* IE is contained in the GNB-CU-UP E1 SETUP REQUEST message, the gNB-CU-CP shall take this IE into account. + +If the GNB-CU-UP E1 SETUP REQUEST message includes the *Transport Network Layer Address Info* IE, the gNB-CU-CP shall, if supported, take this IE into account for IPSec tunnel establishment. + +If the GNB-CU-UP E1 SETUP RESPONSE message includes the *Transport Network Layer Address Info* IE, the gNB-CU-UP shall, if supported, take this IE into account for IPSec tunnel establishment. + +### 8.2.3.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the gNB-CU-UP E1 Setup procedure. The gNB-CU-UP sends a GNB-CU-UP E1 SETUP REQUEST to the gNB-CU-CP, which responds with a GNB-CU-UP E1 SETUP FAILURE.](1841f348dfa81a3438d4e1f8465d9ac7_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: (Not shown in this diagram) + gNB-CU-UP->>gNB-CU-CP: GNB-CU-UP E1 SETUP REQUEST + gNB-CU-CP-->>gNB-CU-UP: GNB-CU-UP E1 SETUP FAILURE +``` + +Sequence diagram showing the Unsuccessful Operation of the gNB-CU-UP E1 Setup procedure. The gNB-CU-UP sends a GNB-CU-UP E1 SETUP REQUEST to the gNB-CU-CP, which responds with a GNB-CU-UP E1 SETUP FAILURE. + +Figure 8.2.3.3-1: gNB-CU-UP E1 Setup procedure: Unsuccessful Operation. + +If the gNB-CU-CP cannot accept the setup, it shall respond with a GNB-CU-UP E1 SETUP FAILURE and appropriate cause value. + +If the GNB-CU-UP E1 SETUP FAILURE message includes the *Time To Wait* IE, the gNB-CU-UP shall wait at least for the indicated time before reinitiating the E1 setup towards the same gNB-CU-CP. + +### 8.2.3.4 Abnormal Conditions + +If the first message received for a specific TNL association is not a GNB-CU-CP E1 SETUP REQUEST, GNB-CU-UP E1 SETUP RESPONSE, or GNB-CU-UP E1 SETUP FAILURE message then this shall be treated as a logical error. + +If the gNB-CU-UP does not receive either GNB-CU-UP E1 SETUP RESPONSE message or GNB-CU-UP E1 SETUP FAILURE message, the gNB-CU-UP may reinitiate the gNB-CU-UP E1 Setup procedure towards the same gNB-CU-CP, provided that the content of the new GNB-CU-UP E1 SETUP REQUEST message is identical to the content of the previously unacknowledged GNB-CU-UP E1 SETUP REQUEST message. + +If the gNB-CU-UP receives a GNB-CU-CP E1 SETUP REQUEST message from the peer entity on the same E1 interface: + +- In case the gNB-CU-UP answers with a GNB-CU-CP E1 SETUP RESPONSE message and receives a subsequent GNB-CU-UP E1 SETUP FAILURE message, the gNB-CU-UP shall consider the E1 interface as non operational and the procedure as unsuccessfully terminated according to sub clause 8.2.3.3. + +- In case the gNB-CU-UP answers with a GNB-CU-CP E1 SETUP FAILURE message and receives a subsequent GNB-CU-UP E1 SETUP RESPONSE message, the gNB-CU-UP shall ignore the GNB-CU-UP E1 SETUP RESPONSE message and consider the E1 interface as non operational. + +## 8.2.4 gNB-CU-CP E1 Setup + +### 8.2.4.1 General + +The purpose of the gNB-CU-CP E1 Setup procedure is to exchange application level data needed for the gNB-CU-CP and the gNB-CU-UP to correctly interoperate on the E1 interface. If the gNB-CU-CP initiates the first TNL association, it shall also initiate the gNB-CU-CP E1 Setup procedure. The procedure uses non-UE associated signalling. + +This procedure erases any existing application level configuration data in the two nodes and replaces it by the one received. This procedure also re-initialises the E1AP UE-related contexts (if any) and erases all related signalling connections in the two nodes like a Reset procedure would do. + +### 8.2.4.2 Successful Operation + +![Sequence diagram of the gNB-CU-CP E1 Setup procedure: Successful Operation. The diagram shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A solid arrow points from gNB-CU-CP to gNB-CU-UP labeled 'GNB-CU-CP E1 SETUP REQUEST'. A solid arrow points from gNB-CU-UP back to gNB-CU-CP labeled 'GNB-CU-CP E1 SETUP RESPONSE'. Both lifelines end with a thick horizontal bar at the bottom.](b2ddf2a678bd20b1b491023eb1db6458_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: GNB-CU-CP E1 SETUP REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: GNB-CU-CP E1 SETUP RESPONSE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +Sequence diagram of the gNB-CU-CP E1 Setup procedure: Successful Operation. The diagram shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A solid arrow points from gNB-CU-CP to gNB-CU-UP labeled 'GNB-CU-CP E1 SETUP REQUEST'. A solid arrow points from gNB-CU-UP back to gNB-CU-CP labeled 'GNB-CU-CP E1 SETUP RESPONSE'. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 8.2.4.2-1: gNB-CU-CP E1 Setup procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending a GNB-CU-CP E1 SETUP REQUEST message including the appropriate data to the gNB-CU-UP. The gNB-CU-UP responds with a GNB-CU-CP E1 SETUP RESPONSE message including the appropriate data. + +If the GNB-CU-CP E1 SETUP REQUEST message contains the *gNB-CU-CP Name* IE the gNB-CU-UP may use this IE as a human readable name of the gNB-CU-CP. If the GNB-CU-CP E1 SETUP REQUEST message contains the *Extended gNB-CU-CP Name* IE, the gNB-CU-UP may use this IE as a human readable name of the gNB-CU-CP and shall ignore the *gNB-CU-CP Name* IE if included. + +If the GNB-CU-CP E1 SETUP RESPONSE message contains the *gNB-CU-UP Name* IE, the gNB-CU-CP may use this IE as a human readable name of the gNB-CU-UP. If the GNB-CU-CP E1 SETUP RESPONSE message contains the *Extended gNB-CU-UP Name* IE, the gNB-CU-CP may use this IE as a human readable name of the gNB-CU-UP and shall ignore the *gNB-CU-UP Name* IE if included. + +The exchanged data shall be stored in respective node and used as long as there is an operational TNL association. When this procedure is finished, the E1 interface is operational and other E1 messages can be exchanged. + +If the *gNB-CU-UP Capacity* IE is contained in the GNB-CU-CP E1 SETUP RESPONSE message, the gNB-CU-CP shall take this IE into account. + +If the GNB-CU-CP E1 SETUP REQUEST message includes the *Transport Network Layer Address Info* IE, the gNB-CU-UP shall, if supported, take this IE into account for IPSec tunnel establishment. + +If the GNB-CU-CP E1 SETUP RESPONSE message includes the *Transport Network Layer Address Info* IE, the gNB-CU-CP shall, if supported, take this IE into account for IPSec tunnel establishment. + +If the *NPN Support Information* IE is contained in the GNB-CU-CP E1 SETUP RESPONSE message, the gNB-CU-CP shall store the corresponding information and it may take it into account for bearer context establishment. + +If the *NR CGI Support List* or the *Extended NR CGI Support List* IE is contained in the GNB-CU-CP E1 SETUP RESPONSE message, the gNB-CU-CP shall store the corresponding information and it may take it into account for bearer context establishment. + +If the *ECGI Support List* IE is contained in the GNB-CU-CP E1 SETUP RESPONSE message, the gNB-CU-CP shall store the corresponding information and it may take it into account for bearer context establishment. + +#### 8.2.4.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the gNB-CU-CP E1 Setup procedure. The diagram shows two entities: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a 'GNB-CU-CP E1 SETUP REQUEST' message to the gNB-CU-UP. The gNB-CU-UP responds with a 'GNB-CU-CP E1 SETUP FAILURE' message back to the gNB-CU-CP.](409498e57b1f988b2b604d12cd997002_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: GNB-CU-CP E1 SETUP REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: GNB-CU-CP E1 SETUP FAILURE + Note left of gNB-CU-CP: + +``` + +Sequence diagram showing the Unsuccessful Operation of the gNB-CU-CP E1 Setup procedure. The diagram shows two entities: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a 'GNB-CU-CP E1 SETUP REQUEST' message to the gNB-CU-UP. The gNB-CU-UP responds with a 'GNB-CU-CP E1 SETUP FAILURE' message back to the gNB-CU-CP. + +**Figure 8.2.4.3-1: gNB-CU-CP E1 Setup procedure: Unsuccessful Operation.** + +If the gNB-CU-UP cannot accept the setup, it shall respond with a GNB-CU-CP E1 SETUP FAILURE and appropriate cause value. + +If the GNB-CU-CP E1 SETUP FAILURE message includes the *Time To Wait* IE, the gNB-CU-CP shall wait at least for the indicated time before reinitiating the E1 setup towards the same gNB-CU-UP. + +#### 8.2.4.4 Abnormal Conditions + +If the first message received for a specific TNL association is not a GNB-CU-UP E1 SETUP REQUEST, GNB-CU-CP E1 SETUP RESPONSE, or GNB-CU-CP E1 SETUP FAILURE message then this shall be treated as a logical error. + +If the gNB-CU-CP does not receive either GNB-CU-CP E1 SETUP RESPONSE message or GNB-CU-CP E1 SETUP FAILURE message, the gNB-CU-CP may reinitiate the gNB-CU-CP E1 Setup procedure towards the same gNB-CU-UP, provided that the content of the new GNB-CU-CP E1 SETUP REQUEST message is identical to the content of the previously unacknowledged GNB-CU-CP E1 SETUP REQUEST message. + +If the gNB-CU-CP receives a GNB-CU-UP E1 SETUP REQUEST message from the peer entity on the same E1 interface: + +- In case the gNB-CU-CP answers with a GNB-CU-UP E1 SETUP RESPONSE message and receives a subsequent GNB-CU-CP E1 SETUP FAILURE message, the gNB-CU-CP shall consider the E1 interface as non operational and the procedure as unsuccessfully terminated according to sub clause 8.2.4.3. +- In case the gNB-CU-CP answers with a GNB-CU-UP E1 SETUP FAILURE message and receives a subsequent GNB-CU-CP E1 SETUP RESPONSE message, the gNB-CU-CP shall ignore the GNB-CU-CP E1 SETUP RESPONSE message and consider the E1 interface as non operational. + +## 8.2.5 gNB-CU-UP Configuration Update + +### 8.2.5.1 General + +The purpose of the gNB-CU-UP Configuration Update procedure is to update application level configuration data needed for the gNB-CU-UP and the gNB-CU-CP to interoperate correctly on the E1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling. + +### 8.2.5.2 Successful Operation + +![Sequence diagram showing the successful operation of the gNB-CU-UP Configuration Update procedure. The gNB-CU-UP sends a GNB-CU-UP CONFIGURATION UPDATE message to the gNB-CU-CP, which responds with a GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message.](6be06b7dc72bb42afcb3465394667c3b_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: GNB-CU-UP CONFIGURATION UPDATE + Note right of gNB-CU-CP: + gNB-CU-CP-->>gNB-CU-UP: GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE + Note right of gNB-CU-UP: + +``` + +Sequence diagram showing the successful operation of the gNB-CU-UP Configuration Update procedure. The gNB-CU-UP sends a GNB-CU-UP CONFIGURATION UPDATE message to the gNB-CU-CP, which responds with a GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message. + +**Figure 8.2.5.2-1: gNB-CU-UP Configuration Update procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending a GNB-CU-UP CONFIGURATION UPDATE message to the gNB-CU-CP including an appropriate set of updated configuration data that it has just taken into operational use. The gNB-CU-CP responds with GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP shall interpret that the corresponding configuration data is not changed and shall continue to operate with the existing related configuration data. + +If the *Supported PLMNs* IE is included in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP shall overwrite the whole list of information and store the corresponding information. + +- If the *Slice Support List* IE is contained in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP shall store the corresponding information and replace any existing information. +- If the *NR CGI Support List* or the *Extended NR CGI Extended Support List* IE is contained in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP shall store the corresponding information and replace any existing information. +- If the *ECGI Support List* IE is contained in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP shall store the corresponding information and replace any existing information. +- If the *QoS Parameters Support List* IE is contained in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP shall store the corresponding information and replace any existing information. +- If the *NPN Support Information* IE is contained in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP shall store the corresponding information and replace any existing information. + +The updated configuration data shall be stored in both nodes and used as long as there is an operational TNL association or until any further update is performed. + +If the *gNB-CU-UP Capacity* IE is contained in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP shall take this IE into account. + +If the *gNB-CU-UP ID* IE is included in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP shall associate the TNLA to the E1 interface instance using the gNB-CU-UP ID. + +If the *gNB-CU-UP Name* IE is included in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP may store it or update this IE value if already stored, and use it as a human readable name of the gNB-CU-UP. If the *Extended gNB-CU-UP Name* IE is included in the GNB-CU-UP CONFIGURATION UPDATE message, the gNB-CU-CP may store it or update this IE value if already stored, and use it as a human readable name of the gNB-CU-UP and shall ignore the *gNB-CU-UP Name* IE if also included. + +If the GNB-CU-UP CONFIGURATION UPDATE message includes *gNB-CU-UP TNLA To Remove List* IE, the gNB-CU-CP shall, if supported, initiate removal of the TNL association(s) indicated by gNB-CU-CP TNL endpoint(s) and gNB-CU-UP TNL endpoint(s) if the *TNLA Transport Layer Address gNB-CU-CP* IE is present, or the TNL association(s) indicated by gNB-CU-UP TNL endpoint(s) if the *TNLA Transport Layer Address gNB-CU-CP* IE is absent: + +- if the received *TNLA Transport Layer Address* IE includes the *Port Number* IE, the gNB-CU-UP TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the gNB-CU-UP TNL endpoints correspond to all gNB-CU-UP TNL endpoints identified by the *Endpoint IP Address* IE and any Port Number(s). +- if the received *TNLA Transport Layer Address gNB-CU-CP* IE includes the *Port Number* IE, the gNB-CU-CP TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the gNB-CU-CP TNL endpoints correspond to all gNB-CU-CP TNL endpoints identified by the *Endpoint IP Address* IE and any Port Number(s). + +If the GNB-CU-UP CONFIGURATION UPDATE message includes the *Transport Network Layer Address Info* IE, the gNB-CU-CP shall, if supported, take this IE into account for IPSec tunnel establishment. + +If the GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message includes the *Transport Network Layer Address Info* IE, the gNB-CU-UP shall, if supported, take this IE into account for IPSec tunnel establishment. + +### 8.2.5.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the gNB-CU-UP Configuration Update procedure. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends a GNB-CU-UP CONFIGURATION UPDATE message to the gNB-CU-CP. The gNB-CU-CP responds with a GNB-CU-UP CONFIGURATION UPDATE FAILURE message.](257c8341b41f1f4a287f27d33227974c_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-CP: + gNB-CU-UP->>gNB-CU-CP: GNB-CU-UP CONFIGURATION UPDATE + Note right of gNB-CU-CP: + gNB-CU-CP-->>gNB-CU-UP: GNB-CU-UP CONFIGURATION UPDATE FAILURE + Note right of gNB-CU-UP: +``` + +Sequence diagram showing the Unsuccessful Operation of the gNB-CU-UP Configuration Update procedure. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends a GNB-CU-UP CONFIGURATION UPDATE message to the gNB-CU-CP. The gNB-CU-CP responds with a GNB-CU-UP CONFIGURATION UPDATE FAILURE message. + +**Figure 8.2.5.3-1: gNB-CU-UP Configuration Update procedure: Unsuccessful Operation.** + +If the gNB-CU-CP cannot accept the update, it shall respond with a GNB-CU-UP CONFIGURATION UPDATE FAILURE message and appropriate cause value. + +If the GNB-CU-UP CONFIGURATION UPDATE FAILURE message includes the *Time To Wait* IE, the gNB-CU-UP shall wait at least for the indicated time before reinitiating the GNB-CU-UP CONFIGURATION UPDATE message towards the same gNB-CU-CP. + +### 8.2.5.4 Abnormal Conditions + +Not applicable. + +## 8.2.6 gNB-CU-CP Configuration Update + +### 8.2.6.1 General + +The purpose of the gNB-CU-CP Configuration Update procedure is to update application level configuration data needed for the gNB-CU-CP and the gNB-CU-UP to interoperate correctly on the E1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling. + +### 8.2.6.2 Successful Operation + +![Sequence diagram of the gNB-CU-CP Configuration Update procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a GNB-CU-CP CONFIGURATION UPDATE message to the gNB-CU-UP. The gNB-CU-UP responds with a GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message back to the gNB-CU-CP.](24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: GNB-CU-CP CONFIGURATION UPDATE + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE + Note left of gNB-CU-CP: +``` + +Sequence diagram of the gNB-CU-CP Configuration Update procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a GNB-CU-CP CONFIGURATION UPDATE message to the gNB-CU-UP. The gNB-CU-UP responds with a GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message back to the gNB-CU-CP. + +**Figure 8.2.6.2-1: gNB-CU-CP Configuration Update procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending a GNB-CU-CP CONFIGURATION UPDATE message to the gNB-CU-UP including an appropriate set of updated configuration data that it has just taken into operational use. The gNB-CU-UP responds with GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the GNB-CU-CP CONFIGURATION UPDATE message, the gNB-CU-UP shall interpret that the corresponding configuration data is not changed and shall continue to operate with the existing related configuration data. + +The updated configuration data shall be stored in both nodes and used as long as there is an operational TNL association or until any further update is performed. + +If the *gNB-CU-CP Name* IE is included in the GNB-CU-CP CONFIGURATION UPDATE message, the gNB-CU-UP may store it or update this IE value if already stored, and use it as a human readable name of the gNB-CU-CP. If the *Extended gNB-CU-CP Name* IE is included in the GNB-CU-CP CONFIGURATION UPDATE message, the gNB-CU-UP may store it or update this IE value if already stored, and use it as a human readable name of the gNB-CU-CP and shall ignore the *gNB-CU-CP Name* IE if also included. + +If the *gNB-CU-CP TNLA To Add List* IE is contained in the gNB-CU-CP CONFIGURATION UPDATE message, the gNB-CU-UP shall, if supported, use it to establish the TNL association(s) with the gNB-CU-CP. If the *gNB-CU-CP TNLA To Add List* IE is included in the gNB-CU-CP CONFIGURATION UPDATE message, and if the *gNB-CU-CP TNLA To Add List* IE does not include the *Port Number* IE, the gNB-CU-UP shall assume that port number value 38462 is used for the endpoint. The gNB-CU-UP shall report to the gNB-CU-CP, in the gNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the gNB-CU-CP as follows: + +- A list of TNL address(es) with which the gNB-CU-UP successfully established the TNL association shall be included in the *gNB-CU-CP TNLA Setup List IE*; +- A list of TNL address(es) with which the gNB-CU-UP failed to establish the TNL association shall be included in the *gNB-CU-CP TNLA Failed To Setup List IE*. + +If the GNB-CU-CP CONFIGURATION UPDATE message includes *gNB-CU-CP TNLA To Remove List IE*, the gNB-CU-UP shall, if supported, initiate removal of the TNL association(s) indicated by gNB-CU-UP TNL endpoint(s) and gNB-CU-CP TNL endpoint(s) if the *TNLA Transport Layer Address gNB-CU-UP IE* is present, or the TNL association(s) indicated by gNB-CU-CP TNL endpoint(s) if the *TNLA Transport Layer Address gNB-CU-UP IE* is absent: + +- if the received *TNLA Transport Layer Address IE* includes the *Port Number IE*, the gNB-CU-CP TNL endpoint is identified by the *Endpoint IP Address IE* and the *Port Number IE*. Otherwise, the gNB-CU-CP TNL endpoints correspond to all gNB-CU-CP TNL endpoints identified by the *Endpoint IP Address IE* and any Port Number(s). +- if the received *TNLA Transport Layer Address gNB-CU-UP IE* includes the *Port Number IE*, the gNB-CU-UP TNL endpoint is identified by the *Endpoint IP Address IE* and the *Port Number IE*. Otherwise, the gNB-CU-UP TNL endpoints correspond to all gNB-CU-UP TNL endpoints identified by the *Endpoint IP Address IE* and any Port Number(s). If the *gNB-CU-CP TNLA To Update List IE* is contained in the gNB-CU-CP CONFIGURATION UPDATE message the gNB-CU-UP shall, if supported, overwrite the previously stored information for the related TNL association. +- If the received *TNLA Transport Layer Address IE* includes the *Port Number IE*, the gNB-CU-CP TNL endpoint is identified by the *Endpoint IP Address IE* and the *Port Number IE*. Otherwise, the gNB-CU-CP TNL endpoints correspond to all gNB-CU-CP TNL endpoints identified by the *Endpoint IP Address IE* and any Port Number(s). + +If the *TNLA Usage IE* is included in the *gNB-CU-CP TNLA To Add List IE* or the *gNB-CU-CP TNLA To Update List IE* in the gNB-CU-CP CONFIGURATION UPDATE message, the gNB-CU-UP shall, if supported, use it as described in TS 38.462 [18]. + +If the GNB-CU-CP CONFIGURATION UPDATE message includes the *Transport Network Layer Address Info IE*, the gNB-CU-UP shall, if supported, take this IE into account for IPSec tunnel establishment. + +If the GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message includes the *Transport Network Layer Address Info IE*, the gNB-CU-CP shall, if supported, take this IE into account for IPSec tunnel establishment. + +### 8.2.6.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the gNB-CU-CP Configuration Update procedure. The diagram shows two entities: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a GNB-CU-CP CONFIGURATION UPDATE message to the gNB-CU-UP. The gNB-CU-UP responds with a GNB-CU-CP CONFIGURATION UPDATE FAILURE message back to the gNB-CU-CP.](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: GNB-CU-CP CONFIGURATION UPDATE + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: GNB-CU-CP CONFIGURATION UPDATE FAILURE + Note left of gNB-CU-CP: +``` + +Sequence diagram showing the Unsuccessful Operation of the gNB-CU-CP Configuration Update procedure. The diagram shows two entities: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a GNB-CU-CP CONFIGURATION UPDATE message to the gNB-CU-UP. The gNB-CU-UP responds with a GNB-CU-CP CONFIGURATION UPDATE FAILURE message back to the gNB-CU-CP. + +**Figure 8.2.6.3-1: gNB-CU-CP Configuration Update procedure: Unsuccessful Operation.** + +If the gNB-CU-UP cannot accept the update, it shall respond with a GNB-CU-CP CONFIGURATION UPDATE FAILURE message and appropriate cause value. + +If the GNB-CU-CP CONFIGURATION UPDATE FAILURE message includes the *Time To Wait* IE, the gNB-CU-CP shall wait at least for the indicated time before reinitiating the GNB-CU-CP CONFIGURATION UPDATE message towards the same gNB-CU-UP. + +#### 8.2.6.4 Abnormal Conditions + +Not applicable. + +### 8.2.7 E1 Release + +#### 8.2.7.1 General + +The purpose of the E1 Release procedure is to release all existing signalling connections and related application level data. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling. + +#### 8.2.7.2 Successful Operation + +##### 8.2.7.2.1 E1 Release Procedure Initiated from the gNB-CU-CP + +![Sequence diagram of the E1 Release procedure initiated from the gNB-CU-CP. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends an E1 RELEASE REQUEST message to the gNB-CU-UP, and the gNB-CU-UP responds with an E1 RELEASE RESPONSE message.](e97d663314aff9c29bf8971323e6539e_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: E1 RELEASE REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: E1 RELEASE RESPONSE + Note left of gNB-CU-CP: +``` + +Sequence diagram of the E1 Release procedure initiated from the gNB-CU-CP. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends an E1 RELEASE REQUEST message to the gNB-CU-UP, and the gNB-CU-UP responds with an E1 RELEASE RESPONSE message. + +**Figure 8.2.7.2.1-1: E1 Release procedure initiated from the gNB-CU-CP. Successful operation.** + +The gNB-CU-CP initiates the procedure by sending the E1 RELEASE REQUEST message to the gNB-CU-UP. + +Upon reception of the E1 RELEASE REQUEST message, the gNB-CU-UP shall release any existing resources related to the E1 interface. The gNB-CU-UP shall respond with a E1 RELEASE RESPONSE message to confirm that it has initiated the release of the resources, if existing, and that the signalling connection for the E1AP application protocol is released. + +##### 8.2.7.2.2 E1 Release Procedure Initiated from the gNB-CU-UP + +![Sequence diagram for E1 Release procedure initiated from the gNB-CU-UP. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends an 'E1 RELEASE REQUEST' message to the gNB-CU-CP. The gNB-CU-CP responds with an 'E1 RELEASE RESPONSE' message to the gNB-CU-UP.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: (Initiator) + gNB-CU-UP->>gNB-CU-CP: E1 RELEASE REQUEST + gNB-CU-CP-->>gNB-CU-UP: E1 RELEASE RESPONSE + Note right of gNB-CU-UP: (Receiver) +``` + +Sequence diagram for E1 Release procedure initiated from the gNB-CU-UP. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends an 'E1 RELEASE REQUEST' message to the gNB-CU-CP. The gNB-CU-CP responds with an 'E1 RELEASE RESPONSE' message to the gNB-CU-UP. + +**Figure 8.2.7.2.2-1: E1 Release procedure initiated from the gNB-CU-UP. Successful operation.** + +The gNB-CU-UP initiates the procedure by sending the E1 RELEASE REQUEST message to the gNB-CU-CP. + +Upon reception of the E1 RELEASE REQUEST message, the gNB-CU-CP shall release any existing resources related to the E1 interface. The gNB-CU-CP shall respond with a E1 RELEASE RESPONSE message to confirm that it has initiated the release of the resources, if existing, and that the signalling connection for the E1AP application protocol is released. + +### 8.2.7.3 Abnormal Conditions + +Not applicable. + +## 8.2.8 gNB-CU-UP Status Indication + +### 8.2.8.1 General + +The purpose of the gNB-CU-UP Status Indication procedure is to inform the gNB-CU-CP that the gNB-CU-UP is overloaded so that overload reduction actions can be applied. The procedure uses non-UE associated signalling. + +### 8.2.8.2 Successful Operation + +![Sequence diagram for DL Data Notification procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends a 'GNB-CU-UP STATUS INDICATION' message to the gNB-CU-CP.](5dca16cd6224cb81fefbd38274e5eb80_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: (Initiator) + gNB-CU-UP->>gNB-CU-CP: GNB-CU-UP STATUS INDICATION + Note right of gNB-CU-UP: (Receiver) +``` + +Sequence diagram for DL Data Notification procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends a 'GNB-CU-UP STATUS INDICATION' message to the gNB-CU-CP. + +**Figure 8.3.7.2-1: DL Data Notification procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the GNB-CU-UP STATUS INDICATION message to the gNB-CU-CP. + +If the *gNB-CU-UP Overload Information* IE in the GNB-CU-UP STATUS INDICATION message indicates that the gNB-CU-UP is overloaded, the gNB-CU-CP shall apply overload reduction actions until informed, with a new GNB-CU-UP STATUS INDICATION message, that the overload situation has ceased. + +The detailed overload reduction policy is up to gNB-CU-CP implementation. + +### 8.2.8.3 Abnormal Conditions + +Not applicable. + +## 8.2.9 Resource Status Reporting Initiation + +### 8.2.9.1 General + +This procedure is used by an gNB-CU-CP to request the reporting of load measurements to gNB-CU-UP. + +The procedure uses non UE-associated signalling. + +### 8.2.9.2 Successful Operation + +![Sequence diagram showing the successful operation of Resource Status Reporting Initiation. The gNB-CU-CP sends a RESOURCE STATUS REQUEST to the gNB-CU-UP, and the gNB-CU-UP responds with a RESOURCE STATUS RESPONSE.](ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: RESOURCE STATUS REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: RESOURCE STATUS RESPONSE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +Sequence diagram showing the successful operation of Resource Status Reporting Initiation. The gNB-CU-CP sends a RESOURCE STATUS REQUEST to the gNB-CU-UP, and the gNB-CU-UP responds with a RESOURCE STATUS RESPONSE. + +**Figure 8.2.9.2-1: Resource Status Reporting Initiation, successful operation** + +The procedure is initiated with a RESOURCE STATUS REQUEST message sent from gNB-CU-CP to gNB-CU-UP to start a measurement or stop a measurements. + +If gNB-CU-UP is capable to provide all requested resource status information, it shall initiate the measurement as requested by gNB-CU-CP, and respond with the RESOURCE STATUS RESPONSE message. + +#### Interaction with other procedures + +When starting a measurement, the *Report Characteristics* IE in the RESOURCE STATUS REQUEST indicates the type of objects gNB-CU-UP shall perform measurements on. The gNB-CU-UP shall include in the RESOURCE STATUS UPDATE message: + +- the *HW Capacity Indicator* IE, if the second bit, "HW Capacity Ind Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to 1; +- the *TNL Available Capacity Indicator* IE, if the first bit, " TNL Available Capacity Ind Periodic " of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to 1; + +If the *Reporting Periodicity* IE is included in the RESOURCE STATUS REQUEST message, this indicates the periodicity for the reporting of periodic measurements. The gNB-CU-UP shall report only once, unless otherwise requested within the *Reporting Periodicity* IE. + +### 8.2.9.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation](cf8bd014a50b7c69435e804f67f9617f_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: RESOURCE STATUS REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: RESOURCE STATUS FAILURE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +The diagram shows a sequence of messages between gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a RESOURCE STATUS REQUEST message to the gNB-CU-UP. The gNB-CU-UP responds with a RESOURCE STATUS FAILURE message. Both entities are represented by vertical lifelines with horizontal bars at the bottom. + +Sequence diagram for Unsuccessful Operation + +Figure 8.2.9.3-1: Resource Status Reporting Initiation, unsuccessful operation + +If any of the requested measurements cannot be initiated, gNB-CU-UP shall send a RESOURCE STATUS FAILURE message with an appropriate cause value. + +### 8.2.9.4 Abnormal Conditions + +If the initiating gNB-CU-CP does not receive either RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message, the gNB-CU-CP may reinitiate the Resource Status Reporting Initiation procedure towards the same gNB-CU-UP, provided that the content of the new RESOURCE STATUS REQUEST message is identical to the content of the previously unacknowledged RESOURCE STATUS REQUEST message with the same Transaction ID. + +If the *Report Characteristics* IE bitmap is set to "0" (all bits are set to "0") in the RESOURCE STATUS REQUEST message then gNB-CU-UP shall initiate a RESOURCE STATUS FAILURE message with an appropriate cause value. + +If the gNB-CU-UP receives a RESOURCE STATUS REQUEST message which includes the *Registration Request* IE set to "start" and the *gNB-CU-CP Measurement ID* IE corresponding to an existing on-going load measurement reporting, for which a different Transaction ID is used, then gNB-CU-UP shall initiate a RESOURCE STATUS FAILURE message with an appropriate cause value. + +## 8.2.10 Resource Status Reporting + +### 8.2.10.1 General + +This procedure is initiated by gNB-CU-UP to report the result of measurements admitted by gNB-CU-UP following a successful Resource Status Reporting Initiation procedure. + +The procedure uses non UE-associated signalling. + +### 8.2.10.2 Successful Operation + +![Sequence diagram for Successful Operation](92271d74f67effbd92583eb3fba71514_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: RESOURCE STATUS UPDATE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +The diagram shows a sequence of messages between gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends a RESOURCE STATUS UPDATE message to the gNB-CU-CP. Both entities are represented by vertical lifelines with horizontal bars at the bottom. + +Sequence diagram for Successful Operation + +Figure 8.2.10.2-1: Resource Status Reporting, successful operation + +The gNB-CU-UP shall report the results of the admitted measurements in RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding Resource Status Reporting Initiation procedure. + +### 8.2.10.3 Unsuccessful Operation + +Not applicable. + +### 8.2.10.4 Abnormal Conditions + +Void. + +## 8.3 Bearer Context Management procedures + +### 8.3.1 Bearer Context Setup + +#### 8.3.1.1 General + +The purpose of the Bearer Context Setup procedure is to allow the gNB-CU-CP to establish a bearer context in the gNB-CU-UP. The procedure uses UE-associated signalling. + +#### 8.3.1.2 Successful Operation + +![Sequence diagram of the Bearer Context Setup procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP. The gNB-CU-UP responds with a BEARER CONTEXT SETUP RESPONSE message. Both lifelines end with a solid black bar.](d6015fcef74bce83d04acd2e17b4fc15_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: BEARER CONTEXT SETUP REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: BEARER CONTEXT SETUP RESPONSE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +Sequence diagram of the Bearer Context Setup procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP. The gNB-CU-UP responds with a BEARER CONTEXT SETUP RESPONSE message. Both lifelines end with a solid black bar. + +**Figure 8.3.1.2-1: Bearer Context Setup procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to establish the requested resources, it replies to the gNB-CU-CP with the BEARER CONTEXT SETUP RESPONSE message. + +The gNB-CU-UP shall report to the gNB-CU-CP, in the BEARER CONTEXT SETUP RESPONSE message, the result for all the requested resources in the following way: + +For E-UTRAN: + +- A list of DRBs which are successfully established shall be included in the *DRB Setup List* IE; +- A list of DRBs which failed to be established shall be included in the *DRB Failed List* IE; + +For NG-RAN: + +- A list of PDU Session Resources which are successfully established shall be included in the *PDU Session Resource Setup List* IE; +- A list of PDU Session Resources which failed to be established shall be included in the *PDU Session Resource Failed List* IE; +- For each established PDU Session Resource, a list of DRBs which are successfully established shall be included in the *DRB Setup List* IE; +- For each established PDU Session Resource, a list of DRBs which failed to be established shall be included in the *DRB Failed List* IE; +- For each established DRB, a list of QoS Flows which are successfully established shall be included in the *Flow Setup List* IE; +- For each established DRB, a list of QoS Flows which failed to be established shall be included in the *Flow Failed List* IE; + +When the gNB-CU-UP reports the unsuccessful establishment of a PDU Session Resource, DRB or QoS Flow the cause value should be precise enough to enable the gNB-CU-CP to know the reason for the unsuccessful establishment. + +If the *Existing Allocated NG DL UP Transport Layer Information* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may re-use the indicated resources already allocated for this bearer context. If the gNB-CU-UP decides to re-use the indicated resources, it shall include the *NG DL UP Unchanged* IE in the BEARER CONTEXT SETUP RESPONSE message. + +If the *PDU Session Resource DL Aggregate Maximum Bit Rate* IE is contained in the *PDU Session Resource To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store and use the information for the down link traffic policing for the Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [20]. + +If the *Data Forwarding Information Request* IE, *PDU Session Data Forwarding Information Request* IE or the *DRB Data Forwarding Information Request* IE are included in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall include the requested forwarding information in the *Data Forwarding Information Response* IE, *PDU Session Data Forwarding Information Response* IE or the *DRB Data Forwarding Information Response* IE in the BEARER CONTEXT SETUP RESPONSE message. + +If the *DL UP Parameters* IE is contained in the *DRB To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall configure the corresponding information. + +For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource To Setup List* IE of the BEARER CONTEXT SETUP REQUEST message, and the *Integrity Protection Indication* IE or *Confidentiality Protection Indication* IE is set to "preferred", then the gNB-CU-UP should, if supported, perform user plane integrity protection or ciphering, respectively, for the concerned PDU session and shall notify whether it performed the user plane integrity protection or ciphering by including the *Integrity Protection Result* IE or *Confidentiality Protection Result* IE, respectively, in the *PDU Session Resource Setup List* IE of the BEARER CONTEXT SETUP RESPONSE message. + +For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource To Setup List* IE of the BEARER CONTEXT SETUP REQUEST message, and the *Integrity Protection Indication* IE or *Confidentiality Protection Indication* IE is set to "required", then the gNB-CU-UP shall perform user plane integrity protection or ciphering, respectively, for the concerned PDU Session. If the gNB-CU-UP cannot perform the user plane integrity protection or ciphering, it shall reject the setup of the PDU Session Resources with an appropriate cause value. + +For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource To Setup List* IE of the BEARER CONTEXT SETUP REQUEST message: + +- if the *Integrity Protection Indication* IE is set to "not needed", then the gNB-CU-UP shall not perform user plane integrity protection for the concerned PDU session; + +- if the *Confidentiality Protection Indication* IE is set to "not needed", then the gNB-CU-UP shall not perform user plane ciphering for the concerned PDU session. + +For E-UTRAN: - For each DRB for which the *Security Indication* IE is included in the *DRB To Setup List* IE of the BEARER CONTEXT SETUP REQUEST message, and the *Integrity Protection Indication* IE is set to "preferred", then the gNB-CU-UP should, if supported, perform user plane integrity protection for the concerned DRB and notify whether it performed the user plane integrity protection by including the *Integrity Protection Result* IE, in the *DRB Setup List* IE of the BEARER CONTEXT SETUP RESPONSE message. + +- For each DRB for which the *Security Indication* IE is included in the *DRB To Setup List* IE of the BEARER CONTEXT SETUP REQUEST message, and the *Integrity Protection Indication* IE is set to "required", then the gNB-CU-UP shall, if supported, perform user plane integrity protection for the concerned DRB. If the gNB-CU-UP cannot perform the user plane integrity protection, it shall reject the setup of the DRB with an appropriate cause value. +- For each DRB for which the *Security Indication* IE is included in the *DRB To Setup List* IE of the BEARER CONTEXT SETUP REQUEST message, and the *Integrity Protection Indication* IE is set to "not needed", then the gNB-CU-UP shall not perform user plane integrity protection for the concerned DRB. + +For each PDU session, if the *Data Forwarding to E-UTRAN Information List* IE is included in the *PDU Session Resource To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it for inter-system data forwarding from 5GS to EPS as specified in TS38.300 [8]. + +If the *UE DL Maximum Integrity Protected Data Rate* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall use this value when enforcing the maximum integrity protected data rate for the UE. + +If the *Bearer Context Status Change* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall consider the UE RRC state and act as specified in TS 38.401 [2]. If the *Bearer Context Status Change* IE is set to "ResumeforSDT", the gNB-CU-UP shall, if supported, consider that DRBs not configured with SDT are suspended after being established. + +For each requested DRB, if the *PDCP Duplication* IE is included in the *PDCP Configuration* IE contained in the BEARER CONTEXT SETUP REQUEST message, then the gNB-CU-UP shall include two *UP Transport Layer Information* IEs in the BEARER CONTEXT SETUP RESPONSE message to support packet duplication. If only one cell group is included in the *Cell Group Information* IE for the concerned DRB, then the gNB-CU-UP shall consider that the first *UP Transport Layer Information* IE of the two *UP Transport Layer Information* IEs is for the primary path. + +For each requested DRB, if the *Additional PDCP duplication Information* IE is included in the *PDCP Configuration* IE contained in the BEARER CONTEXT SETUP REQUEST message, then the gNB-CU-UP shall, if supported, include the same number of *UP Transport Layer Information* IEs indicated by the *Additional PDCP duplication Information* IE in the BEARER CONTEXT SETUP RESPONSE message to support packet duplication. If only one cell group is included in the *Cell Group Information* IE for the concerned DRB, then the gNB-CU-UP shall consider that the first *UP Transport Layer Information* IE of these *UP Transport Layer Information* IEs is for the primary path. If more than one cell group is included in the *Cell Group Information* IE, then the gNB-CU-UP shall consider that the number of duplication tunnels for each cell group is indicated by the *Number of tunnels* IE, and that the first *UP Transport Layer Information* IE for each cell group is for the primary path or the split secondary path. + +If the *PDCP SN Status Information* IE is contained within the *DRB To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall take it into account and act as specified in TS 38.401 [2]. + +If the *QoS Flow Mapping Indication* IE is contained in the *QoS Flows Information To Be Setup* IE within the *DRB To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may take it into account that only the uplink or downlink QoS flow is mapped to the DRB. + +If the *QoS Flows Remapping* IE is contained within the *DRB To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message for a DRB and set to "update", the gNB-CU-UP shall, if supported, consider that QoS flows + +mapped for the DRB is updated to the QoS flow(s) included in the *QoS Flows Information To Be Setup* IE after finishing handling forwarded PDCP SDUs during an intra-system handover procedure. If the *QoS Flows Remapping* IE is contained within the *DRB To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message for a DRB and set to "source configuration", the gNB-CU-UP shall, if supported, consider that no QoS flow is mapped to the DRB after finishing handling forwarded PDCP SDUs over that DRB during an intra-system handover procedure and ignore the information included in the *QoS Flows Information To Be Setup* IE for the concerned DRB. + +For each PDU Session Resource, if the *Network Instance* IE is included in the *PDU Session Resource To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message and the *Common Network Instance* IE is not included, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [20]. + +For each PDU session, if the *Common Network Instance* IE is included in the *PDU Session Resource To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [20]. + +For each PDU session, if the *Redundant NG UL UP Transport Layer Information* IE is included in the *PDU Session Resource To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, use it as the uplink termination point of the redundant tunnel for the user plane data of those QoS flows in this PDU session which need redundant transmission as described in TS 23.501 [20], and it shall include the *Redundant NG DL UP Transport Layer Information* IE in the *PDU Session Resource Setup List* IE in the BEARER CONTEXT SETUP RESPONSE message. + +For each PDU Session Resource, if the *Redundant Common Network Instance* IE is included in the *PDU Session Resource To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501 [20]. + +For each PDU session, if the *Redundant QoS Flow Indicator* IE is included in the *QoS Flow QoS Parameters List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, consider it for the redundant transmission. + +For each PDU session, if the *Redundant PDU Session Information* IE is included in the *PDU Session Resource To Setup List* IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, set up the redundant user plane resources, as specified in TS 23.501 [20] and include, if supported, the *Used Redundant PDU Session Information* IE in the *PDU Session Resource Setup List* IE in the BEARER CONTEXT SETUP RESPONSE message. If the *PDU Session Pair ID* IE is included in the *Redundant PDU Session Information* IE, the gNB-CU-UP may use it to identify the paired PDU Sessions. + +If the *SpecialTriggeringPurpose* IE is included in *PDU Session Resource To Setup List* IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may consider that the setup of the DRB or the PDU session for which the IE is included is for the purpose of indirect data forwarding. + +If *UE Inactivity Timer* IE or *PDU session Inactivity Timer* IE or *DRB Inactivity Timer* IE is contained in BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall take it into account when perform inactivity monitoring. + +If the *DRB QoS* IE is contained within the *DRB To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, take it into account as specified in TS 28.552 [22]. + +If the *gNB-DU-ID* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store the information received. + +If the *RAN UE ID* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store the information received. + +For each successfully established DRB, the gNB-CU-UP shall provide, in the respective *UL UP Parameters* IE of the BEARER CONTEXT SETUP RESPONSE, one UL UP Transport Layer Information Item per cell group entry contained in the respective *Cell Group Information* IE of the BEARER CONTEXT SETUP REQUEST message. + +If the *Trace Activation* IE is included in the BEARER CONTEXT SETUP REQUEST message the gNB-CU-UP shall, if supported, initiate the requested trace function as described in TS 32.422 [24]. In particular, the gNB-CU-UP shall, if supported: + +- if the *MDT Activation* IE is set to "Immediate MDT Only", initiate the requested MDT session as described in TS 32.422 [24] and the gNB-CU-UP shall ignore *Interfaces To Trace* IE, and *Trace Depth* IE; +- if the *MDT Activation* IE is set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422 [24]; + +If the *Management Based MDT PLMN List* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, store the received information, and use this information to allow subsequent selection of the UE for management based MDT defined in TS 32.422 [24]. + +For EN-DC, if the *Subscriber Profile ID for RAT/Frequency priority* IE is included in the BEARER CONTEXT SETUP REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300 [25]. If the *Additional RRM Policy Index* IE is included in the BEARER CONTEXT SETUP REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300 [25]. + +If the *TSC Traffic Characteristics* IE is included in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, take into account the corresponding information received in the *TSC Traffic Characteristics* IE. + +For each QoS flow whose DRB has been successfully established and the *QoS Monitoring Request* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501 [20]. If the *QoS Monitoring Reporting Frequency* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store this information, and, if supported, use it for RAN part delay reporting. + +For each QoS flow whose DRB has been successfully established in the gNB-CU-UP, if the *ECN Marking or Congestion Information Request* IE is included in the *PDU Session Resource To Setup List* IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, use it accordingly for the specific QoS flow. If the *ECN Marking or Congestion Information Reporting Status* IE is included in the *Flow Setup List* IE contained in the the *PDU Session Resource Setup List* IE of the BEARER CONTEXT SETUP RESPONSE message, the gNB-CU-CP shall, if supported, use it to deduce if ECN marking at NG-RAN or ECN marking at UPF or congestion information reporting is active or not active. + +If the BEARER CONTEXT SETUP REQUEST message contains the *NPN Context Information* IE the gNB-CU-UP shall, if supported, take it into account when allocating UP resources for the bearer context. + +For each requested DRB, if the *EHC Parameters* IE is included in the *PDCP Configuration* IE, the gNB-CU-CP shall, if supported, also include *ROHC Parameters* IE in the *PDCP Configuration* IE in the BEARER CONTEXT SETUP REQUEST message, to enable the gNB-CU-UP to perform appropriate header compression. + +If the *EHC parameters* IE is included in the *PDCP Configuration* IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may take these parameters into account to perform appropriate header compression for the concerned DRB. If the *EHC Downlink* IE is included in the *EHC parameters* IE and the value of *drb-ContinueEHC-DL* IE is set to 'true', the gNB-CU-UP shall, if supported, configure Ethernet header compression for downlink and continue the downlink EHC header compression protocol as specified in TS 38.331 [10]. If the *EHC Downlink* IE is included in the *EHC parameters* IE and the value of *drb-ContinueEHC-DL* IE is set to 'false', the gNB-CU-UP shall, if supported, configure Ethernet header compression for downlink and reset the downlink EHC header compression protocol during PDCP re-establishment as specified in TS 38.331 [10]. If the *EHC Uplink* IE is included in + +the *EHC parameters* IE and the value of *drb-ContinueEHC-UL* IE is set to 'true', the gNB-CU-UP shall, if supported, configure Ethernet header compression for uplink and continue the uplink EHC header compression protocol as specified in TS 38.331 [10]. If the *EHC Uplink* IE is included in the *EHC parameters* IE and the value of *drb-ContinueEHC-UL* IE is set to 'false', the gNB-CU-UP shall, if supported, configure Ethernet header compression for uplink and resets the uplink EHC header compression protocol during PDCP re-establishment as specified in TS 38.331 [10]. + +If the *DAPS Request Information* IE is included for a DRB to be setup in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall consider that the request concerns a DAPS handover for that DRB and, if admitted, act as specified in TS 38.300 [4]. + +If the *CHO Initiation* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall consider that the request concerns conditional handover or conditional PSCell change or conditional PSCell addition or subsequent CPAC and act as specified in TS 38.401 [2]. + +If the *MCG Offered GBR QoS Flow Information* IE is contained in the *QoS Flows Information To Be Setup* IE within the *DRB To Setup List* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may take it into account when two cell groups are served by the gNB-CU-UP. + +If the *Additional Handover Information* IE is included in the BEARER CONTEXT SETUP REQUEST message and set to "Discard PDCP SN", the gNB-CU-UP shall, if supported, remove the forwarded PDCP SNs if received in the forwarded GTP-U packets, and deliver the forwarded PDCP SDUs to the UE, as specified in TS 38.300 [8]. + +If the *Ignore Mapping Rule Indication* IE is contained within the *DRB To Setup List* IE for a DRB in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, ignore the QoS flow mapping information indicated by the *QoS Flows Information To Be Setup* IE for the concerned DRB. + +If the *Direct Forwarding Path Availability* IE set to "inter-system direct path available" is included in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, assign the UP Transport Layer Information for inter-system direct data forwarding from the appropriate address space, if applicable. + +If the *Direct Forwarding Path Availability* IE set to "intra-system direct path available" is included in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, assign the UP Transport Layer Information for intra-system direct data forwarding from the appropriate address space, if applicable. + +If the *gNB-CU-UP UE EIAP ID* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may use it to identify the UE context as specified in TS 38.401 [2]. + +If the *Data Forwarding Source IP Address* IE is included in the *DRB To Setup List E-UTRAN* IE or in the *QoS Flow Level QoS Parameters* IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. + +If the *Data Forwarding Source IP Address* IE is included in the *DRB Setup List E-UTRAN* IE or in the *Flow Setup List* IE within the *DRB Setup List* IE in the *PDU Session Resource Setup List* IE of the BEARER CONTEXT SETUP RESPONSE message, the gNB-CU-CP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. + +If the *MDT Polluted Measurement Indicator* IE is included in the BEARER CONTEXT SETUP REQUEST, the gNB-CU-UP shall take this information into account as specified in TS 38.401 [2]. + +If the *UE Slice Maximum Bit Rate List* IE is included in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, store and use the information for the downlink traffic policing for each concerned slice as specified in TS 23.501 [20]. + +If the *UDC parameters* IE is included in the *PDCP Configuration* IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, take these parameters into account to perform appropriate uplink data compression for the concerned DRB. + +If the *SCG Activation Status* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall take it into account when handling DL data transfer as specified in TS 37.340 [19]. + +If the *PDU Set QoS Parameters* IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, store it and use the information as specified in TS 23.501 [20]. + +#### Interactions with DL Data Notification procedure: + +If the *MT-SDT Information Request* IE is included in the BEARER CONTEXT SETUP REQUEST message and the value is set to 'true', the gNB-CU-UP shall, if supported, store it and report the *MT-SDT Information* IE in the DL DATA NOTIFICATION message as specified in TS 38.401 [2]. + +If the *SDT Data Size Threshold* IE is included in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, store it and act as specified in TS 38.401 [2]. + +### 8.3.1.3 Unsuccessful Operation + +![Sequence diagram showing the Bearer Context Setup procedure: Unsuccessful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP. The gNB-CU-UP responds with a BEARER CONTEXT SETUP FAILURE message back to the gNB-CU-CP. Both lifelines end with a solid black bar.](2aa94b70ba3fadcba8420d9e3128253a_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: BEARER CONTEXT SETUP REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: BEARER CONTEXT SETUP FAILURE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: + +``` + +Sequence diagram showing the Bearer Context Setup procedure: Unsuccessful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP. The gNB-CU-UP responds with a BEARER CONTEXT SETUP FAILURE message back to the gNB-CU-CP. Both lifelines end with a solid black bar. + +Figure 8.3.1.3-1: Bearer Context Setup procedure: Unsuccessful Operation. + +If the gNB-CU-UP cannot establish the requested bearer context, or cannot even establish one bearer, or cannot handle SCG with the indicated activated or deactivated status it shall consider the procedure as failed and respond with a BEARER CONTEXT SETUP FAILURE message and appropriate cause value. + +### 8.3.1.4 Abnormal Conditions + +If the gNB-CU-UP receives a BEARER CONTEXT SETUP REQUEST message containing a *E-UTRAN QoS* IE in the *DRB To Setup List* IE for a GBR QoS DRB but where the *GBR QoS Information* IE is not present, the gNB-CU-UP shall report the establishment of the corresponding DRB as failed in the *DRB Failed List* IE of the BEARER CONTEXT SETUP RESPONSE message with an appropriate cause value. + +If the gNB-CU-UP receives a BEARER CONTEXT SETUP REQUEST message containing a *QoS Flow Level QoS Parameters* IE in the *PDU Session Resource To Setup List* IE for a GBR QoS Flow but where the *GBR QoS Flow Information* IE is not present, the gNB-CU-UP shall report the establishment of the corresponding QoS Flow as failed in the corresponding *Flow Failed List* IE of the BEARER CONTEXT SETUP RESPONSE message with an appropriate cause value. + +## 8.3.2 Bearer Context Modification (gNB-CU-CP initiated) + +### 8.3.2.1 General + +The purpose of the Bearer Context Modification procedure is to allow the gNB-CU-CP to modify a bearer context in the gNB-CU-UP. The procedure uses UE-associated signalling. + +### 8.3.2.2 Successful Operation + +![Sequence diagram showing the Bearer Context Modification procedure: Successful Operation. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with a BEARER CONTEXT MODIFICATION RESPONSE.](fb4274c4b7882a4059103f1dbca9b111_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: BEARER CONTEXT MODIFICATION REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: BEARER CONTEXT MODIFICATION RESPONSE + Note left of gNB-CU-CP: + +``` + +Sequence diagram showing the Bearer Context Modification procedure: Successful Operation. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with a BEARER CONTEXT MODIFICATION RESPONSE. + +**Figure 8.3.2.2-1: Bearer Context Modification procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to modify the bearer context, it replies to the gNB-CU-CP with the BEARER CONTEXT MODIFICATION RESPONSE message. + +The gNB-CU-UP shall report to the gNB-CU-CP, in the BEARER CONTEXT MODIFICATION RESPONSE message, the result for all the requested resources in the following way: + +For E-UTRAN: + +- A list of DRBs which are successfully established shall be included in the *DRB Setup List* IE; +- A list of DRBs which failed to be established shall be included in the *DRB Failed List* IE; +- A list of DRBs which are successfully modified shall be included in the *DRB Modified List* IE; +- A list of DRBs which failed to be modified shall be included in the *DRB Failed To Modify List* IE; + +For NG-RAN: + +- A list of PDU Session Resources which are successfully established shall be included in the *PDU Session Resource Setup List* IE; +- A list of PDU Session Resources which failed to be established shall be included in the *PDU Session Resource Failed List* IE; +- A list of PDU Session Resources which are successfully modified shall be included in the *PDU Session Resource Modified List* IE; +- A list of PDU Session Resources which failed to be modified shall be included in the *PDU Session Resource Failed To Modify List* IE; +- For each successfully established or modified PDU Session Resource, a list of DRBs which are successfully established shall be included in the *DRB Setup List* IE; +- For each successfully established or modified PDU Session Resource, a list of DRBs which failed to be established shall be included in the *DRB Failed List* IE; +- For each successfully modified PDU Session Resource, a list of DRBs which are successfully modified shall be included in the *DRB Modified List* IE; + +- For each successfully modified PDU Session Resource, a list of DRBs which failed to be modified shall be included in the *DRB Failed To Modify List IE*; +- For each successfully established or modified DRB, a list of QoS Flows which are successfully established shall be included in the *Flow Setup List IE*; +- For each successfully established or modified DRB, a list of QoS Flows which failed to be established shall be included in the *Flow Failed List IE*; + +When the gNB-CU-UP reports the unsuccessful establishment of a PDU Session Resource, DRB or QoS Flow the cause value should be precise enough to enable the gNB-CU-CP to know the reason for the unsuccessful establishment. + +If the *Security Information IE* is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. + +If the *UE DL Aggregate Maximum Bit Rate IE* is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. + +If the *UE DL Maximum Integrity Protected Data Rate IE* is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. + +If the *Bearer Context Status Change IE* is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall consider the UE RRC state and act as specified in TS 38.401 [2]. If the *Bearer Context Status Change IE* is set to "ResumeforSDT", the gNB-CU-UP shall consider that DRBs configured with SDT are resumed only and the other DRBs remain suspended. + +If *SDT Continue ROHC IE* is contained in the BEARER CONTEXT MODIFICATION REQUEST message and the value is set to "true", the gNB-CU-UP shall, if supported, continue the ROHC for the SDT bearers for the UE. + +If the *Data Forwarding Information Request IE*, *PDU Session Data Forwarding Information Request IE* or the *DRB Data Forwarding Information Request IE* are included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall include the requested forwarding information in the *Data Forwarding Information Response IE*, *PDU Session Data Forwarding Information Response IE* or the *DRB Data Forwarding Information Response IE* in the BEARER CONTEXT MODIFICATION RESPONSE message. + +If the *PDU Session Data Forwarding Information IE* is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, consider that data forwarding is applicable for the indicated QoS flows for the concerned PDU session. + +If the *Secondary PDU Session Data Forwarding Information IE* is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, consider that data forwarding is applicable for the indicated QoS flows for the concerned PDU session. + +If the *PDCP Configuration IE* is contained in the *DRB To Modify List IE* in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information, except for the *PDCP SN UL Size IE*, the *PDCP SN DL Size IE* and the *RLC mode IE* which shall be ignored. + +If the *E-UTRAN QoS IE* is contained in the *DRB To Modify List IE* in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. + +If the *PDCP SN Status Request IE* is contained in the *DRB To Modify List IE* in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall act as specified in TS 38.401 [2] and include the *UL COUNT Value IE* and the *DL COUNT Value IE* in the BEARER CONTEXT MODIFICATION RESPONSE message. + +If the *PDCP SN Status Information IE* is contained in the *DRB To Setup List IE* or the *DRB To Modify List IE* in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account and act as specified in TS 38.401 [2]. + +If the *DL UP Parameters* IE is contained in the *DRB To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. If the *Indirect Path Indication* IE is contained in the *DL UP Parameters* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, act as specified in TS 38.401 [2]. + +If the *PDCP COUNT Reset* IE is contained within the *DRB To Modify List* IE for a DRB of the *PDU Session Resource To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, reset the PDCP COUNT value for this DRB (i.e. its HFN and PDCP-SN to value "0"). + +If the *Cell Group To Add* IE or the *Cell Group To Modify* IE or the *Cell Group To Remove* IE is contained in the *DRB To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall add or modify or remove the corresponding cell group. + +If the *PDU Session Resource DL Aggregate Maximum Bit Rate* IE is contained in the *PDU Session Resource To Setup List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall replace the information in the UE context and use it when enforcing downlink traffic policing for the non GBR QoS flows for the concerned UE, as specified in TS 23.501 [20]. + +If the *PDU Session Resource DL Aggregate Maximum Bit Rate* IE is contained in the *PDU Session Resource To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. + +If the *SDAP Configuration* IE is contained in the *DRB To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. + +If the *Flow Mapping Information* IE is contained in the *DRB To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. + +For each requested DRB, if the *PDCP Duplication* IE or *Additional PDCP duplication Information* IE is included in the *PDCP Configuration* IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, then the gNB-CU-CP shall include two or more *UP Transport Layer Information* IEs in the BEARER CONTEXT MODIFICATION REQUEST message, and the gNB-CU-UP shall, if supported, also include two or more *UP Transport Layer Information* IEs in the BEARER CONTEXT MODIFICATION RESPONSE message to support packet duplication. If only one cell group is included in the *Cell Group Information* IE for the concerned DRB, then the gNB-CU-UP shall consider that the first *UP Transport Layer Information* IE of these *UP Transport Layer Information* IEs is for the primary path. If more than one cell group is included in the *Cell Group Information* IE, then the gNB-CU-UP shall consider that the number of duplication tunnels for each cell group is indicated by the *Number of tunnels* IE, and that the first *UP Transport Layer Information* IE for each cell group is for the primary path or the split secondary path. + +For a certain DRB which was allocated with two or more GTP-U tunnels, if such DRB is modified and given one GTP-U tunnel via the Bearer Context Modification (gNB-CU-CP initiated) procedure, i.e. only one UP Transport Layer Information per Cell Group ID is present in *DL UP Parameters* IE for the concerned DRB, then the gNB-CU-UP shall consider that PDCP duplication is deconfigured for this DRB. If such Bearer Context Modification (gNB-CU-CP initiated) procedure occurs, the *Duplication Activation* IE shall not be included for the concerned DRB. + +If the *New UL TNL Information Required* IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall include the new UP Transport Layer Information in the BEARER CONTEXT MODIFICATION RESPONSE message. + +For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource To Setup List* IE or the *Security Indication Modify* IE is included in the *PDU Session Resource To Modify List* IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the *Integrity Protection Indication* IE or *Confidentiality Protection Indication* IE is set to "preferred", then the gNB-CU-UP should, if supported, perform user plane integrity protection or ciphering, respectively, for the concerned PDU session and shall notify whether it performed the user plane integrity protection or ciphering by including the *Integrity Protection Result* IE or *Confidentiality Protection Result* IE, respectively, in the *PDU Session Resource Setup List* IE or the *PDU Session Resource Modified List* IE of the BEARER CONTEXT MODIFICATION RESPONSE message. + +For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource To Setup List* IE or the *Security Indication Modify* IE is included in the *PDU Session Resource To Modify List* IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the *Integrity Protection Indication* IE or *Confidentiality Protection Indication* IE is set to "required", then the gNB-CU-UP shall perform user plane integrity protection or ciphering, respectively, for the concerned PDU Session. If the gNB-CU-UP cannot perform the user plane integrity protection or ciphering, it shall reject the setup of the PDU Session Resources with an appropriate cause value. + +For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource To Setup List* IE or the *Security Indication Modify* IE is included in the *PDU Session Resource To Modify List* IE of the BEARER CONTEXT MODIFICATION REQUEST message: + +- if the *Integrity Protection Indication* IE is set to "not needed", then the gNB-CU-UP shall not perform user plane integrity protection for the concerned PDU session; +- if the *Confidentiality Protection Indication* IE is set to "not needed", then the gNB-CU-UP shall not perform user plane ciphering for the concerned PDU session. + +For E-UTRAN: + +- For each DRB for which the *Security Indication* IE is included in the *DRB To Setup List* IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the *Integrity Protection Indication* IE is set to "preferred", then the gNB-CU-UP should, if supported, perform user plane integrity protection for the concerned DRB and notify whether it performed the user plane integrity protection by including the *Integrity Protection Result* IE in the *DRB Setup List* IE of the BEARER CONTEXT MODIFICATION RESPONSE message. +- For each DRB for which the *Security Indication* IE is included in the *DRB To Setup List* IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the *Integrity Protection Indication* IE is set to "required", then the gNB-CU-UP shall, if supported, perform user plane integrity protection for the concerned DRB. If the gNB-CU-UP cannot perform the user plane integrity protection, it shall reject the setup of the DRB with an appropriate cause value. +- For each DRB for which the *Security Indication* IE is included in the *DRB To Setup List* IE of the BEARER CONTEXT MODIFICATION REQUEST message and the *Integrity Protection Indication* IE is set to "not needed", then the gNB-CU-UP shall not perform user plane integrity protection for the concerned DRB. + +For each PDU Session Resource, if the *Network Instance* IE is included in the *PDU Session Resource To Setup List* IE or the *PDU Session Resource To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message and the *Common Network Instance* IE is not included, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [20]. + +For each PDU session, if the *Common Network Instance* IE is included in the *PDU Session Resource To Setup List* IE or the *PDU Session Resource To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [20]. + +For each PDU session, if the *Redundant NG UL UP Transport Layer Information* IE is included in the *PDU Session Resource To Setup List* IE or the *PDU Session Resource To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, include the *Redundant NG DL UP Transport Layer Information* IE in the *PDU Session Resource Setup List* IE or the *PDU Session Resource Modified List* IE in the BEARER CONTEXT MODIFICATION RESPONSE message. + +If the *Redundant Common Network Instance* IE is included in the *PDU Session Resource To Setup List* IE or the *PDU Session Resource To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501 [20]. + +For each PDU session for which the *Redundant QoS Flow Indicator* IE is included in *QoS Flows Information To Be Setup* IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if support, shall store and use it as specified in TS 23.501 [20]. + +For each PDU session, if the *Redundant QoS Flow Indicator* IE is set to false for all QoS flows, the gNB-CU-UP shall, if supported, stop the redundant transmission and release the redundant tunnel for the concerned PDU session as specified in TS 23.501 [20]. + +If the *SpecialTriggeringPurpose* IE is included in *PDU Session Resource To Setup Modification List* IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP may consider that the setup of the DRB or the PDU session for which the IE is included is for the purpose of indirect data forwarding. + +If the *QoS Flow Mapping Indication* IE is contained in the *QoS Flow QoS Parameters List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, replace any previously received value and take it into account that only the uplink or downlink QoS flow is mapped to the DRB. + +If the *Data Discard Required* IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message and the value is set to "Required", the gNB-CU-UP shall consider that a RAN Paging Failure occurred for that UE. The gNB-CU-UP shall discard the user plane data for that UE and consider that the bearer context is still suspended. + +If *UE Inactivity Timer* IE or *PDU session Inactivity Timer* IE or *DRB Inactivity Timer* IE is contained in BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account when perform inactivity monitoring. + +If the *S-NSSAI* IE is contained in the *PDU Session Resource To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store the corresponding information and replace any existing information. + +If the *DRB QoS* IE is contained within the *DRB To Setup List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, take it into account for each DRB, as specified in TS 28.552 [22]. + +If the *DRB QoS* IE is contained within the *DRB To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, replace any previously received value and take it into account for each DRB, as specified in TS 28.552 [22]. + +If the *gNB-DU-ID* IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store and replace any previous information received. + +If the *RAN UE ID* IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store and replace any previous information received. + +If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message including *Activity Notification Level* IE and its value does not match the current bearer context, the gNB-CU-UP shall ignore the *Activity Notification Level* IE and also the requested modification of inactivity timer. + +For each successfully established DRB, the gNB-CU-UP shall provide, in the respective *UL UP Parameters* IE of the BEARER CONTEXT MODIFICATION RESPONSE, one UL UP Transport Layer Information Item per cell group entry contained in the respective *Cell Group Information* IE of the BEARER CONTEXT MODIFICATION REQUEST message. + +If the *Old QoS Flow List - UL End Marker expected* IE is included in the *PDU Session Resource To Modify List* IE of the BEARER CONTEXT MODIFICATION REQUEST message for a DRB to be modified, the gNB-CU-UP shall consider that the source NG-RAN node has initiated QoS flow re-mapping and has not yet received SDAP end markers, as described in TS 38.300 [8]. The gNB-CU-UP shall consider that the *Old QoS Flow List - UL End Marker expected* IE only contains UL QoS flow information for QoS flows for which no SDAP end marker has been yet received on the source side. + +For EN-DC, if the *Subscriber Profile ID for RAT/Frequency priority* IE is included in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300 [25]. If the *Additional RRM Policy Index* IE is included in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300 [25]. + +If there is at least one DRB removed by the gNB-CU-UP, the gNB-CU-UP shall, if supported, include the *Retainability Measurements Information* IE in the BEARER CONTEXT MODIFICATION RESPONSE message, providing information on the removed DRB(s) for retainability measurements in the gNB-CU-CP, as described in TS 32.425 [26] and TS 28.552 [22]. + +If the *TSC Traffic Characteristics* IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, take into account the corresponding information received in the *TSC Traffic Characteristics* IE. + +For each QoS flow whose DRB has been successfully established or modified and the *QoS Monitoring Request* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501 [20]. If the *QoS Monitoring Reporting Frequency* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store this information, and, if supported, use it for RAN part delay reporting. + +For each QoS flow whose DRB has been successfully established or modified in the gNB-CU-UP, if the *ECN Marking or Congestion Information Request* IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it accordingly for the specific QoS flow. If the *ECN Marking or Congestion Information Reporting Status* IE is included in the *Flow Setup List* IE contained in the the *PDU Session Resource Setup List* IE or the *PDU Session Resource Modified List* IE of the BEARER CONTEXT MODIFICATION RESPONSE message, the gNB-CU-CP shall, if supported, use it to deduce if ECN marking at NG-RAN or ECN marking at UPF or congestion information reporting is active or not active. + +For each requested DRB, if the *QoS Mapping Information* IE is contained in the *DL UP Parameters* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall use it to set DSCP and/or flow label fields in the downlink IP packets which are transmitted through the GTP tunnels indicated by the *UP Transport Layer Information* IE. The Diffserv code point (DSCP) marking is performed as specified in TS 38.474 [28]. + +If the *Early Forwarding COUNT Request* IE is contained in the *DRB To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall act as specified in TS 38.401 [2] and include the requested *FIRST DL COUNT Value* IE or *DISCARD DL COUNT Value* IE in the BEARER CONTEXT MODIFICATION RESPONSE message. + +If the *Early Forwarding COUNT Information* IE is contained in the *DRB To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account and act as specified in TS 38.401 [2]. + +If the *Ignore Mapping Rule Indication* IE is contained within the *DRB To Setup List* IE for a DRB in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, ignore the QoS flow mapping information indicated by the *QoS Flows Information To Be Setup* IE for the concerned DRB. + +If the *DAPS Request Information* IE is included for a DRB to be modified in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall consider that the request concerns a DAPS handover for that DRB and, if admitted, act as specified in TS 38.300 [4]. + +If the *Early Data Forwarding Indicator* IE set to “stop” is contained in the *DRB To Modify List* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported and if already initiated, stop the early data forwarding for the concerned DRB. If the *DRB Data forwarding information* IE containing the *DL Data Forwarding* IE is included together in the *DRB To Modify List* IE, the gNB-CU-UP shall consider that the stop is only for the early data forwarding initiated toward that forwarding TNL. + +If the *MDT Polluted Measurement Indicator* IE is included in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP shall take this information into account as specified in TS 38.401 [2]. + +If the *UE Slice Maximum Bit Rate List* IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, store and replace the previously provided UE Slice Maximum Bit Rate List by the received UE Slice Maximum Bit Rate List in the UE context, and use the received UE Slice Maximum Bit Rate List for the downlink traffic policing for each concerned slice as specified in TS 23.501 [20]. + +If the *SCG Activation Status* IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account when handling DL data transfer as specified in TS 37.340 [19]. + +If the *UDC parameters* IE is included in the *PDCP Configuration* IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, take these parameters into account to perform appropriate uplink data compression for the concerned DRB. + +If the *Data Forwarding Source IP Address* IE is included in the *DRB To Setup Modification List E-UTRAN* IE or in the *QoS Flow Level QoS Parameters* IE within the *PDU Session Resource To Setup Modification List* IE and the *PDU Session Resource To Modify List* IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. + +If the *Data Forwarding Source IP Address* IE is included in the *DRB Setup Modification List E-UTRAN* IE or in the *Flow Setup List* IE within the *PDU Session Resource Setup Modification List* IE and the *PDU Session Resource Modified List* IE of the BEARER CONTEXT MODIFICATION RESPONSE message, the gNB-CU-CP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. + +If the *Management Based MDT PLMN Modification List* IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, overwrite any previously stored Management Based MDT PLMN List information in the UE context and use the received information to determine subsequent selection of the UE for management based MDT defined in TS 32.422 [24]. + +If the *Inactivity Information Request* IE is contained in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP shall, if supported, include the *UE Inactivity Information* IE in the BEARER CONTEXT MODIFICATION RESPONSE message. + +If the *PDU Set QoS Parameters* IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, store it and use the information as specified in TS 23.501 [20]. + +For a QoS flow established with PDU Set QoS parameters, if the *PDU Set based Handling Indicator* IE is included in the *PDU Session Data Forwarding Information* IE within the BEARER CONTEXT MODIFICATION REQUEST message and the value of the *PDU Set based Handling Indicator* IE is set to "supported", the gNB-CU-UP shall, if supported, include the PDU Set information in the data to be forwarded. Otherwise, the gNB-CU-UP may not include the PDU Set identification and marking for the data to be forwarded. + +#### **Interactions with DL Data Notification procedure:** + +If the *MT-SDT Information Request* IE is included in the BEARER CONTEXT MODIFICATION REQUEST message and the value is set to 'true', the gNB-CU-UP shall, if supported, store it and report the *MT-SDT Information* IE in the DL DATA NOTIFICATION message as specified in TS 38.401 [2]. + +If the *SDT Data Size Threshold* IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, store it and act as specified in TS 38.401 [2]. + +#### **Interaction with the Bearer Context Modification (gNB-CU-CP initiated)** + +If the BEARER CONTEXT MODIFICATION REQUEST message includes for a DRB in the *DRB To Modify List* IE the *PDCP SN Status Request* IE set to "requested" and if the gNB-CU-UP has not yet received a SDAP end marker + +packet for a QoS flow which has been previously re-configured to another DRB by means of a gNB-CU-CP initiated Bearer Context Modification procedure, the gNB-CU-UP shall include the QoS Flow Identifier of that QoS flow in the *Old QoS Flow List - UL End Marker expected* IE in the *PDU Session Resource Modified List* IE in the BEARER CONTEXT MODIFICATION RESPONSE message. + +### 8.3.2.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful Bearer Context Modification procedure. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with a BEARER CONTEXT MODIFICATION FAILURE.](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: BEARER CONTEXT MODIFICATION REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: BEARER CONTEXT MODIFICATION FAILURE + Note left of gNB-CU-CP: + +``` + +Sequence diagram showing an unsuccessful Bearer Context Modification procedure. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with a BEARER CONTEXT MODIFICATION FAILURE. + +**Figure 8.3.2.3-1: Bearer Context Modification procedure: Unsuccessful Operation.** + +If the gNB-CU-UP cannot successfully perform any of the requested bearer context modifications, or cannot handle SCG with the indicated activated or deactivated status, it shall respond with a BEARER CONTEXT MODIFICATION FAILURE message and appropriate cause value. + +If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message containing the *Security Indication Modify* IE in the *PDU Session Resource To Modify List* IE for a PDU session that may result in the change of security status that has been applied but the DRBs that have been established for that PDU session are not requested to be released via the *DRB To Remove List* IEs as specified in TS 38.331 [10], then the gNB-CU-UP shall respond with a BEARER CONTEXT MODIFICATION FAILURE message and appropriate cause value. + +If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message containing the *PDCP COUNT Reset* IE in the *DRB To Modify List* IE of the *PDU Session Resource To Modify List* IE but if the *Security Information* IE is not present, then the gNB-CU-UP shall respond with a BEARER CONTEXT MODIFICATION FAILURE message and appropriate cause value. + +### 8.3.2.4 Abnormal Conditions + +If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message containing a *E-UTRAN QoS* IE in the *DRB To Setup List* or the *DRB To Modify List* IE for a GBR QoS DRB but where the *GBR QoS Information* IE is not present, the gNB-CU-UP shall report the addition or the modification of the corresponding DRB as failed in the *DRB Failed List* IE or the *DRB Failed To Modify List* IE of the BEARER CONTEXT MODIFICATION RESPONSE message with an appropriate cause value. + +If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message containing a *QoS Flow Level QoS Parameters* IE in the *PDU Session Resource To Setup List* IE or the *PDU Session Resource To Modify List* IE for a GBR QoS Flow but where the *GBR QoS Flow Information* IE is not present, the gNB-CU-UP shall report the addition or the modification of the corresponding QoS Flow as failed in the corresponding *Flow Failed List* IE of the BEARER CONTEXT MODIFICATION RESPONSE message with an appropriate cause value. + +### 8.3.3 Bearer Context Modification Required (gNB-CU-UP initiated) + +#### 8.3.3.1 General + +The purpose of the Bearer Context Modification Required procedure is to allow the gNB-CU-UP to modify a bearer context (e.g., due to local problems) and inform the gNB-CU-CP. The procedure uses UE-associated signalling. + +#### 8.3.3.2 Successful Operation + +![Sequence diagram showing the successful operation of the Bearer Context Modification Required procedure. The gNB-CU-UP sends a BEARER CONTEXT MODIFICATION REQUIRED message to the gNB-CU-CP, which responds with a BEARER CONTEXT MODIFICATION CONFIRM message.](802707b774f2d2973b49cea2020e8453_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-CP: + gNB-CU-UP->>gNB-CU-CP: BEARER CONTEXT MODIFICATION REQUIRED + gNB-CU-CP-->>gNB-CU-UP: BEARER CONTEXT MODIFICATION CONFIRM + Note right of gNB-CU-UP: +``` + +Sequence diagram showing the successful operation of the Bearer Context Modification Required procedure. The gNB-CU-UP sends a BEARER CONTEXT MODIFICATION REQUIRED message to the gNB-CU-CP, which responds with a BEARER CONTEXT MODIFICATION CONFIRM message. + +**Figure 8.3.3.2-1: Bearer Context Modification Required procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the BEARER CONTEXT MODIFICATION REQUIRED message to the gNB-CU-CP. The gNB-CU-CP replies with the BEARER CONTEXT MODIFICATION CONFIRM message. + +If the *SI DL UP Transport Layer Information IE* or the *NG DL UP Transport Layer Information IE* or the *Redundant NG DL UP Transport Layer Information IE* is contained in the BEARER CONTEXT MODIFICATION REQUIRED message, the gNB-CU-CP shall update the corresponding information. + +If the *gNB-CU-UP Cell Group Related Configuration IE* is contained in the *DRB To Modify List IE* in the BEARER CONTEXT MODIFICATION REQUIRED message, the gNB-CU-CP shall try to change the cell group related configuration accordingly. If the gNB-CU-CP is not able to update the requested cell group related configuration, it shall include the *Cell Group Information IE* with the current cell group configuration in the *DRB Modified List IE* in the BEARER CONTEXT MODIFICATION CONFIRM message. + +#### 8.3.3.3 Abnormal Conditions + +Not applicable. + +### 8.3.4 Bearer Context Release (gNB-CU-CP initiated) + +#### 8.3.4.1 General + +The purpose of the Bearer Context Release procedure is to allow the gNB-CU-CP to command the release of an UE-associated logical E1 connection. The procedure uses UE-associated signalling. + +### 8.3.4.2 Successful Operation + +![Sequence diagram for Bearer Context Release procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a BEARER CONTEXT RELEASE COMMAND message to the gNB-CU-UP. The gNB-CU-UP responds with a BEARER CONTEXT RELEASE COMPLETE message. Both lifelines end with a solid black bar.](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: BEARER CONTEXT RELEASE COMMAND + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: BEARER CONTEXT RELEASE COMPLETE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +Sequence diagram for Bearer Context Release procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a BEARER CONTEXT RELEASE COMMAND message to the gNB-CU-UP. The gNB-CU-UP responds with a BEARER CONTEXT RELEASE COMPLETE message. Both lifelines end with a solid black bar. + +**Figure 8.3.4.2-1: Bearer Context Release procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT RELEASE COMMAND message to the gNB-CU-UP. The gNB-CU-UP replies with the BEARER CONTEXT RELEASE COMPLETE message. + +Upon reception of the BEARER CONTEXT RELEASE COMMAND message, the gNB-CU-UP shall release all related signalling and user data transport resources and reply with the BEARER CONTEXT RELEASE COMPLETE message. + +The gNB-CU-UP shall, if supported, include the *Retainability Measurements Information* IE in the BEARER CONTEXT RELEASE COMPLETE message, providing information on the removed DRB(s) for retainability measurements in the gNB-CU-CP, as described in TS 32.425 [26] and TS 28.552 [22]. + +### 8.3.4.3 Abnormal Conditions + +Not applicable. + +## 8.3.5 Bearer Context Release Request (gNB-CU-UP initiated) + +### 8.3.5.1 General + +The purpose of the Bearer Context Release Request procedure is to allow the gNB-CU-UP to request the gNB-CU-CP to release an UE-associated logical E1 connection. The procedure uses UE-associated signalling. + +### 8.3.5.2 Successful Operation + +![Sequence diagram for Bearer Context Release Request procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends a BEARER CONTEXT RELEASE REQUEST message to the gNB-CU-CP. Both lifelines end with a solid black bar.](5043b1d06ff3f78c43f3432a4bae436d_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-UP-->>gNB-CU-CP: BEARER CONTEXT RELEASE REQUEST + Note right of gNB-CU-UP: +``` + +Sequence diagram for Bearer Context Release Request procedure: Successful Operation. The diagram shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends a BEARER CONTEXT RELEASE REQUEST message to the gNB-CU-CP. Both lifelines end with a solid black bar. + +**Figure 8.3.5.2-1: Bearer Context Release Request procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the BEARER CONTEXT RELEASE REQUEST message to the gNB-CU-CP. + +If the *DRB Status List* IE is included in the BEARER CONTEXT RELEASE REQUEST message, the gNB-CU-CP shall act as specified in TS 38.401 [2]. + +#### Interactions with Bearer Context Release procedure: + +The Bearer Context Release (gNB-CU-CP initiated) procedure may be initiated upon reception of a BEARER CONTEXT RELEASE REQUEST message. + +#### Interaction with Bearer Context Modification (gNB-CU-CP initiated) procedure: + +If applicable, as specified in TS 38.401 [2], the gNB-CU-UP may receive, after having performed the Bearer Context Release Request (gNB-CU-UP initiated) procedure, the BEARER CONTEXT MODIFICATION REQUEST message including the *Data Forwarding Information Request* IE within the *DRBs To Modify List* IE. + +### 8.3.5.3 Abnormal Conditions + +Not applicable. + +## 8.3.6 Bearer Context Inactivity Notification + +### 8.3.6.1 General + +This procedure is initiated by the gNB-CU-UP to indicate the inactivity/resumption of activity related to the UE. The procedure uses UE-associated signalling. + +### 8.3.6.2 Successful Operation + +![Sequence diagram showing the Bearer Context Inactivity Notification procedure. The gNB-CU-UP sends a BEARER CONTEXT INACTIVITY NOTIFICATION message to the gNB-CU-CP.](b15db6d53b3f3bf00c9b42cc510cf23d_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: BEARER CONTEXT INACTIVITY NOTIFICATION + Note right of gNB-CU-CP: +``` + +Sequence diagram showing the Bearer Context Inactivity Notification procedure. The gNB-CU-UP sends a BEARER CONTEXT INACTIVITY NOTIFICATION message to the gNB-CU-CP. + +**Figure 8.3.6.2-1: Bearer Context Inactivity Notification procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the BEARER CONTEXT INACTIVITY NOTIFICATION message to the gNB-CU-CP. + +If the Activity Notification Level was set to “DRB” during the Bearer Context establishment, the gNB-CU-UP shall include the *DRB Activity List* IE in the BEARER CONTEXT INACTIVITY NOTIFICATION message. + +If the Activity Notification Level was set to “PDU Session” during the Bearer Context establishment, the gNB-CU-UP shall include the *PDU Session Resource Activity List* IE in the BEARER CONTEXT INACTIVITY NOTIFICATION message. + +If the Activity Notification Level was set to “UE” during the Bearer Context establishment, the gNB-CU-UP shall include the *UE Activity* IE in the BEARER CONTEXT INACTIVITY NOTIFICATION message. + +### 8.3.6.3 Abnormal Conditions + +Not applicable. + +## 8.3.7 DL Data Notification + +### 8.3.7.1 General + +This procedure is initiated by the gNB-CU-UP to indicate the detection of DL data arrival for the UE, or indicate that a DL packet including a QFI value in the NG-U header not configured by the *QoS Flows Information To Be Setup* IE or the *Flow Mapping Information* IE is received for the first time. The procedure uses UE-associated signalling. + +### 8.3.7.2 Successful Operation + +![Sequence diagram showing the DL Data Notification procedure. The gNB-CU-UP sends a DL DATA NOTIFICATION message to the gNB-CU-CP.](a97f7c055c1fd8d79037d02b3fc38496_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: (UE-associated signalling) + gNB-CU-UP->>gNB-CU-CP: DL DATA NOTIFICATION + Note right of gNB-CU-CP: (UE-associated signalling) +``` + +Sequence diagram showing the DL Data Notification procedure. The gNB-CU-UP sends a DL DATA NOTIFICATION message to the gNB-CU-CP. + +**Figure 8.3.7.2-1: DL Data Notification procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the DL DATA NOTIFICATION message to the gNB-CU-CP. + +If the *PPI* IE is included in the DL DATA NOTIFICATION message, the gNB-CU-CP shall use it for paging policy differentiation. + +If the *PDU Session To Notify List* IE is included in the DL DATA NOTIFICATION message, the gNB-CU-CP shall, if supported, either map the flow(s) included in *PDU Session To Notify List* IE to the existing DRB or establish a new DRB for the flow(s). + +If the *MT-SDT Information* IE is included in the DL DATA NOTIFICATION message, the gNB-CU-CP shall, if supported, take it into account for MT-SDT paging. + +If the *SDT Data Size Threshold Crossed* IE is included in the DL DATA NOTIFICATION message, the gNB-CU-CP shall, if supported, act as specified in TS 38.401 [2]. + +NOTE: If a DL packet including a QFI value in the NG-U header not configured by the *QoS Flows Information To Be Setup* IE or the *Flow Mapping Information* IE is received, the gNB-CU-UP may deliver the DL packet via any existing configured DRB before it initiates DL Data Notification procedure. + +### 8.3.7.3 Abnormal Conditions + +Not applicable. + +## 8.3.8 Data Usage Report + +### 8.3.8.1 General + +This procedure is initiated by the gNB-CU-UP to report data volume served at the gNB-CU-UP. The procedure uses UE-associated signalling. + +### 8.3.8.2 Successful Operation + +![Sequence diagram for Data Usage Report procedure: Successful Operation. It shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A horizontal arrow labeled 'DATA USAGE REPORT' points from the gNB-CU-UP lifeline to the gNB-CU-CP lifeline. Both lifelines end in a thick horizontal bar at the bottom.](4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: DATA USAGE REPORT + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +Sequence diagram for Data Usage Report procedure: Successful Operation. It shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A horizontal arrow labeled 'DATA USAGE REPORT' points from the gNB-CU-UP lifeline to the gNB-CU-CP lifeline. Both lifelines end in a thick horizontal bar at the bottom. + +**Figure 8.3.8.2-1: Data Usage Report procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the DATA USAGE REPORT message to the gNB-CU-CP. + +### 8.3.8.3 Abnormal Conditions + +Not applicable. + +## 8.3.9 gNB-CU-UP Counter Check + +### 8.3.9.1 General + +This procedure is initiated by the gNB-CU-UP to request the gNB-CU-CP to execute a counter check procedure to verify the value of the PDCP COUNTs associated with DRBs established in the gNB-CU-UP. + +The procedure uses UE-associated signalling. + +### 8.3.9.2 Successful Operation + +![Sequence diagram for gNB-CU-UP Counter Check procedure, successful operation. It shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A horizontal arrow labeled 'GNB-CU-UP COUNTER CHECK REQUEST' points from the gNB-CU-UP lifeline to the gNB-CU-CP lifeline. Both lifelines end in a thick horizontal bar at the bottom.](51bca542502bc86a3d68f777885524cc_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: GNB-CU-UP COUNTER CHECK REQUEST + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +Sequence diagram for gNB-CU-UP Counter Check procedure, successful operation. It shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A horizontal arrow labeled 'GNB-CU-UP COUNTER CHECK REQUEST' points from the gNB-CU-UP lifeline to the gNB-CU-CP lifeline. Both lifelines end in a thick horizontal bar at the bottom. + +**Figure 8.3.9.2-1: gNB-CU-UP Counter Check procedure, successful operation.** + +The gNB-CU-UP initiates the procedure by sending the gNB-CU-UP COUNTER CHECK REQUEST message to the gNB-CU-CP. + +Upon reception of the gNB-CU-UP COUNTER CHECK REQUEST message, the gNB-CU-CP may perform the RRC counter check procedure as defined in TS 33.501 [13]. + +### 8.3.9.3 Unsuccessful Operation + +Not applicable. + +### 8.3.9.4 Abnormal Conditions + +Not applicable. + +## 8.3.10 UL Data Notification + +### 8.3.10.1 General + +This procedure is initiated by the gNB-CU-UP to notify the gNB-CU-CP that an UL packet including a QFI value in the SDAP header not configured by the *QoS Flows Information To Be Setup* IE or the *Flow Mapping Information* IE is received for the first time at the default DRB. The procedure uses UE-associated signalling. + +### 8.3.10.2 Successful Operation + +![Sequence diagram showing the UL Data Notification procedure. The gNB-CU-UP sends a UL DATA NOTIFICATION message to the gNB-CU-CP.](a82bc78bff7fbefef1c0fb744365f957_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: UL DATA NOTIFICATION + Note right of gNB-CU-CP: + Note left of gNB-CU-UP: + Note right of gNB-CU-CP: +``` + +Sequence diagram showing the UL Data Notification procedure. The gNB-CU-UP sends a UL DATA NOTIFICATION message to the gNB-CU-CP. + +**Figure 8.3.10.2-1: UL Data Notification procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the UL DATA NOTIFICATION message to the gNB-CU-CP. + +### 8.3.10.3 Abnormal Conditions + +Not applicable. + +## 8.3.11 MR-DC Data Usage Report + +### 8.3.11.1 General + +This procedure is initiated by the gNB-CU-UP to report data volume served at the gNB-CU-UP, where the UE is connected to the 5GC. The procedure uses UE-associated signalling. + +### 8.3.11.2 Successful Operation + +![Sequence diagram for MR-DC Data Usage Report procedure: Successful Operation. It shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A horizontal arrow labeled 'MR-DC DATA USAGE REPORT' points from the gNB-CU-UP lifeline to the gNB-CU-CP lifeline. Both lifelines end in a thick horizontal bar at the bottom.](74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: MR-DC DATA USAGE REPORT + Note right of gNB-CU-CP: + gNB-CU-UP-->>gNB-CU-CP: + Note left of gNB-CU-UP: + Note right of gNB-CU-CP: +``` + +Sequence diagram for MR-DC Data Usage Report procedure: Successful Operation. It shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A horizontal arrow labeled 'MR-DC DATA USAGE REPORT' points from the gNB-CU-UP lifeline to the gNB-CU-CP lifeline. Both lifelines end in a thick horizontal bar at the bottom. + +**Figure 8.3.11.2-1: MR-DC Data Usage Report procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the MR-DC DATA USAGE REPORT message to the gNB-CU-CP. + +### 8.3.11.3 Abnormal Conditions + +Not applicable. + +## 8.3.12 Early Forwarding SN Transfer + +### 8.3.12.1 General + +The purpose of the Early Forwarding SN Transfer procedure is to transfer, from the source gNB-CU-UP to the source gNB-CU-CP, DL COUNT of the last PDCP SDU successfully delivered or transmitted to the UE, for the purpose of discarding early forwarded downlink PDCP SDUs during Conditional Handover or conditional PSCell change or conditional PSCell addition. + +The procedure uses UE-associated signalling. + +### 8.3.12.2 Successful Operation + +![Sequence diagram for Early Forwarding SN Transfer procedure: Successful Operation. It shows two vertical lifelines: source gNB-CU-CP on the left and source gNB-CU-UP on the right. A horizontal arrow labeled 'EARLY FORWARDING SN TRANSFER' points from the source gNB-CU-UP lifeline to the source gNB-CU-CP lifeline. Both lifelines end in a thick horizontal bar at the bottom.](0804537310c1bb3f615cb001e33efd1a_img.jpg) + +``` +sequenceDiagram + participant source gNB-CU-UP + participant source gNB-CU-CP + Note left of source gNB-CU-UP: + source gNB-CU-UP->>source gNB-CU-CP: EARLY FORWARDING SN TRANSFER + Note right of source gNB-CU-CP: + source gNB-CU-UP-->>source gNB-CU-CP: + Note left of source gNB-CU-UP: + Note right of source gNB-CU-CP: +``` + +Sequence diagram for Early Forwarding SN Transfer procedure: Successful Operation. It shows two vertical lifelines: source gNB-CU-CP on the left and source gNB-CU-UP on the right. A horizontal arrow labeled 'EARLY FORWARDING SN TRANSFER' points from the source gNB-CU-UP lifeline to the source gNB-CU-CP lifeline. Both lifelines end in a thick horizontal bar at the bottom. + +**Figure 8.3.12.2-1: Early Forwarding SN Transfer procedure: Successful Operation.** + +The source gNB-CU-UP initiates the procedure by sending the EARLY FORWARDING SN TRANSFER message. + +The *DRBs Subject To Early Forwarding List* IE included in the EARLY FORWARDING SN TRANSFER message contains the DRB ID(s) corresponding to the DRB(s) subject to early data forwarding during Conditional Handover or conditional PSCell change or conditional PSCell addition or subsequent CPAC. + +For each DRB in the *DRBs Subject To Early Forwarding List* IE, the value of the *DL COUNT Value* IE indicates the DL COUNT of the last PDCP SDU successfully delivered in-sequence to the UE, if RLC-AM, and successfully transmitted, if RLC-UM. + +### 8.3.12.3 Unsuccessful Operation + +Not applicable. + +### 8.3.12.4 Abnormal Conditions + +If the source gNB-CU-CP receives this message for a UE for which no prepared Conditional Handover exists, the source gNB-CU-CP shall ignore the message. + +## 8.3.13 GNB-CU-CP Measurement Results Information + +### 8.3.13.1 General + +This procedure is initiated by the gNB-CU-CP to inform the measurement results received from the UE to the gNB-CU-UP. + +The procedure uses UE-associated signalling. + +### 8.3.13.2 Successful Operation + +![Sequence diagram showing the successful operation of the GNB-CU-CP Measurement Results Information procedure. The gNB-CU-CP sends a GNB-CU-CP MEASUREMENT RESULTS INFORMATION message to the gNB-CU-UP.](ef8f4838401ece0abd51d63b897fa388_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: GNB-CU-CP MEASUREMENT RESULTS INFORMATION + Note right of gNB-CU-UP: + activate gNB-CU-UP + deactivate gNB-CU-UP +``` + +Sequence diagram showing the successful operation of the GNB-CU-CP Measurement Results Information procedure. The gNB-CU-CP sends a GNB-CU-CP MEASUREMENT RESULTS INFORMATION message to the gNB-CU-UP. + +**Figure 8.3.13.2-1: GNB-CU-CP Measurement Results Information procedure. Successful operation.** + +The gNB-CU-CP initiates the procedure by sending a GNB-CU-CP MEASUREMENT RESULTS INFORMATION message. + +### 8.3.13.3 Abnormal Conditions + +Not applicable. + +## 8.4 Trace Procedures + +### 8.4.1 Trace Start + +#### 8.4.1.1 General + +The purpose of the Trace Start procedure is to allow the gNB-CU-CP to request the gNB-CU-UP to initiate a trace session for a UE. The procedure uses UE-associated signalling. + +#### 8.4.1.2 Successful Operation + +![Sequence diagram for Trace start procedure: Successful Operation. It shows two lifelines: gNB-CU-UP on the left and gNB-CU-CP on the right. A horizontal arrow labeled 'TRACE START' points from the gNB-CU-CP lifeline to the gNB-CU-UP lifeline. Both lifelines have a thick black horizontal bar at the bottom, representing the activation of the trace session.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: [Activation] + gNB-CU-CP->>gNB-CU-UP: TRACE START + Note right of gNB-CU-CP: [Activation] +``` + +Sequence diagram for Trace start procedure: Successful Operation. It shows two lifelines: gNB-CU-UP on the left and gNB-CU-CP on the right. A horizontal arrow labeled 'TRACE START' points from the gNB-CU-CP lifeline to the gNB-CU-UP lifeline. Both lifelines have a thick black horizontal bar at the bottom, representing the activation of the trace session. + +**Figure 8.4.1.2-1: Trace start procedure: Successful Operation.** + +Upon reception of the TRACE START message, the gNB-CU-UP shall initiate the requested trace session for the requested UE, as described in TS 32.422 [24]. In particular, the gNB-CU-UP shall, if supported: + +- if the *MDT Activation* IE is set to "Immediate MDT Only", initiate the requested MDT session as described in TS 32.422 [24] and the gNB-CU-UP shall ignore *Interfaces To Trace* IE, and *Trace Depth* IE. + +#### 8.4.1.3 Abnormal Conditions + +Void. + +### 8.4.2 Deactivate Trace + +#### 8.4.2.1 General + +The purpose of the Deactivate Trace procedure is to allow the gNB-CU-CP to request the gNB-CU-UP to stop the trace session for the indicated trace reference. The procedure uses UE-associated signalling. + +#### 8.4.2.2 Successful Operation + +![Sequence diagram for Deactivate trace procedure: Successful Operation. It shows two lifelines: gNB-CU-UP on the left and gNB-CU-CP on the right. A horizontal arrow labeled 'DEACTIVATE TRACE' points from the gNB-CU-CP lifeline to the gNB-CU-UP lifeline. Both lifelines have a thick black horizontal bar at the bottom, representing the activation of the trace session.](2071a5d5382d83adafa96687d358e5b2_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: [Activation] + gNB-CU-CP->>gNB-CU-UP: DEACTIVATE TRACE + Note right of gNB-CU-CP: [Activation] +``` + +Sequence diagram for Deactivate trace procedure: Successful Operation. It shows two lifelines: gNB-CU-UP on the left and gNB-CU-CP on the right. A horizontal arrow labeled 'DEACTIVATE TRACE' points from the gNB-CU-CP lifeline to the gNB-CU-UP lifeline. Both lifelines have a thick black horizontal bar at the bottom, representing the activation of the trace session. + +**Figure 8.4.2.2-1: Deactivate trace procedure: Successful Operation.** + +Upon reception of the DEACTIVATE TRACE message, the gNB-CU-UP shall stop the trace session for the indicated trace reference contained in the *Trace ID* IE, as described in TS 32.422 [24]. + +#### 8.4.2.3 Abnormal Conditions + +Void. + +## 8.4.3 Cell Traffic Trace + +### 8.4.3.1 General + +The purpose of the Cell Traffic Trace procedure is to send the allocated Trace Recording Session Reference and the Trace Reference to the gNB-CU-CP. The procedure uses UE-associated signalling. + +### 8.4.3.2 Successful Operation + +![Sequence diagram for Cell Traffic Trace procedure. It shows two vertical lifelines. The right lifeline has a rectangle at the top and a small black oval at the bottom. The left lifeline has a small black oval at the bottom. A horizontal arrow points from the right lifeline to the left lifeline, originating from the middle of the right lifeline and pointing to the middle of the left lifeline.](23cb65390082ab306c15bd3d8196135e_img.jpg) + +Sequence diagram for Cell Traffic Trace procedure. It shows two vertical lifelines. The right lifeline has a rectangle at the top and a small black oval at the bottom. The left lifeline has a small black oval at the bottom. A horizontal arrow points from the right lifeline to the left lifeline, originating from the middle of the right lifeline and pointing to the middle of the left lifeline. + +**Figure 8.4.3.2-1: Cell Traffic Trace procedure. Successful operation.** + +The procedure is initiated with a CELL TRAFFIC TRACE message sent from the gNB-CU-UP to the gNB-CU-CP. + +If the *Privacy Indicator* IE is included in the message, the gNB-CU-CP shall store the information so that it can be transferred towards the AMF. + +### 8.4.3.3 Abnormal Conditions + +Void. + +## 8.5 IAB Procedures + +### 8.5.1 IAB UP TNL Address Update + +#### 8.5.1.1 General + +The purpose of the IAB UP TNL Address Update procedure is to allow the gNB-CU-CP to request the gNB-CU-UP to update the TNL Address(es) for all the DL F1-U GTP-U tunnels related to this (these) TNL address(es), and to allow the gNB-CU-UP to inform the gNB-CU-CP about the updated TNL Address(es) for all the UL F1-U GTP-U tunnels. The procedure uses non-UE associated signalling. + +NOTE: This procedure is applicable for IAB-nodes, where the term "gNB-CU-CP" applies to IAB-donor-CU-CP, and the term "gNB-CU-UP" applies to IAB-donor-CU-UP. + +NOTE: Implementation shall ensure the avoidance of potential race conditions, i.e. it must ensure that the UP configuration (e.g., UL/DL UP TNL address) update is not concurrently performed using the non-UE-associated IAB UP TNL Address Update procedure and the UE-associated procedures for Bearer Context Management. + +### 8.5.1.2 Successful Operation + +![Sequence diagram for Successful Operation of IAB UP TNL Address Update procedure.](a9159a006d67a834a7b1a771c18191cc_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: IAB UP TNL ADDRESS UPDATE + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE + Note left of gNB-CU-CP: +``` + +The diagram shows a sequence of two messages between gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends an 'IAB UP TNL ADDRESS UPDATE' message to the gNB-CU-UP. The gNB-CU-UP responds with an 'IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE' message. Both entities are represented by boxes with a horizontal line at the bottom, indicating lifelines. + +Sequence diagram for Successful Operation of IAB UP TNL Address Update procedure. + +**Figure 8.5.1.2-1: IAB UP TNL Address Update procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the IAB UP TNL ADDRESS UPDATE message to the gNB-CU-UP. If the gNB-CU-UP succeeds to update the TNL Address(es), it replies to the gNB-CU-CP with the IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE message. + +Upon reception of the IAB UP TNL ADDRESS UPDATE message, if the *DL UP TNL Address to Update List* IE is included therein, the gNB-CU-UP shall replace the old TNL Address(es) by the new TNL Address(es) for all the maintained DL F1-U GTP tunnels corresponding to the old TNL Address(es). + +If the *UL UP TNL Address to Update List* IE is contained in the IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE message, the gNB-CU-CP shall consider the new TNL address(es) as replacement for the corresponding old TNL address(es). + +### 8.5.1.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of IAB UP TNL Address Update procedure.](de98d4c97665a29427651680af184ff4_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: IAB UP TNL ADDRESS UPDATE + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: IAB UP TNL ADDRESS UPDATE FAILURE + Note left of gNB-CU-CP: +``` + +The diagram shows a sequence of two messages between gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends an 'IAB UP TNL ADDRESS UPDATE' message to the gNB-CU-UP. The gNB-CU-UP responds with an 'IAB UP TNL ADDRESS UPDATE FAILURE' message. Both entities are represented by boxes with a horizontal line at the bottom, indicating lifelines. + +Sequence diagram for Unsuccessful Operation of IAB UP TNL Address Update procedure. + +**Figure 8.5.1.3-1: IAB UP TNL Address Update procedure: Unsuccessful Operation.** + +If the gNB-CU-UP receives an IAB UP TNL ADDRESS UPDATE message, but cannot perform the update accordingly, it shall consider the update procedure as failed and respond with an IAB UP TNL ADDRESS UPDATE FAILURE message and appropriate cause value. + +If the IAB UP TNL ADDRESS UPDATE FAILURE message includes the *Time To Wait* IE, the gNB-CU-CP shall wait at least for the indicated amount of time before reinitiating the IAB UP TNL Address Update procedure towards the same gNB-CU-UP. + +### 8.5.1.4 Abnormal Conditions + +Not Applicable. + +## 8.5.2 IAB PSK Notification + +### 8.5.2.1 General + +The purpose of the IAB PSK Notification procedure is to allow the gNB-CU-CP to send the security key info to the gNB-CU-UP, which will be used for the IKEv2 Pre-shared Secret Key (PSK) authentication to protect the F1-U interface of the IAB-node(s) as specified in TS 33.501 [13]. The procedure uses non-UE associated signalling. + +NOTE: This procedure is applicable for IAB-nodes, where the term "gNB-CU-CP" applies to IAB-donor-CU-CP, and the term "gNB-CU-UP" applies to IAB-donor-CU-UP. + +NOTE: Implementation should ensure that the IAB PSK Notification procedure be performed after the IAB-donor-CU-CP obtains the IP address of the IAB-DU and of the IAB-donor-CU-UP. + +### 8.5.2.2 Successful Operation + +![Sequence diagram showing the IAB PSK Notification procedure. A gNB-CU-CP sends an IAB PSK NOTIFICATION message to a gNB-CU-UP.](879d68959f0c0ba370ef82447298ba17_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: IAB PSK NOTIFICATION + Note right of gNB-CU-UP: +``` + +Sequence diagram showing the IAB PSK Notification procedure. A gNB-CU-CP sends an IAB PSK NOTIFICATION message to a gNB-CU-UP. + +**Figure 8.5.2.2-1: IAB PSK Notification procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the IAB PSK NOTIFICATION message to the gNB-CU-UP. + +The gNB-CU-UP uses the *IAB-Donor-CU-UP PSK Info* IE included in the IAB PSK NOTIFICATION message as specified in TS 33.501 [13]. + +### 8.5.2.3 Abnormal Conditions + +Not applicable. + +## 8.6 MBS Procedures + +### 8.6.1 MBS Procedures for Broadcast + +#### 8.6.1.1 BC Bearer Context Setup + +##### 8.6.1.1.1 General + +The purpose of the BC Bearer Context Setup procedure is to allow the gNB-CU-CP to establish MBS session resources for a broadcast MBS session in the gNB-CU-UP. The procedure uses MBS-associated signalling. + +## 8.6.1.1.2 Successful Operation + +![Sequence diagram showing the BC Bearer Context Setup procedure for Successful Operation. The gNB-CU-CP sends a BC BEARER CONTEXT SETUP REQUEST to the gNB-CU-UP, which responds with a BC BEARER CONTEXT SETUP RESPONSE.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: BC BEARER CONTEXT SETUP REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: BC BEARER CONTEXT SETUP RESPONSE + Note left of gNB-CU-CP: + +``` + +Sequence diagram showing the BC Bearer Context Setup procedure for Successful Operation. The gNB-CU-CP sends a BC BEARER CONTEXT SETUP REQUEST to the gNB-CU-UP, which responds with a BC BEARER CONTEXT SETUP RESPONSE. + +**Figure 8.6.1.1.2-1: BC Bearer Context Setup procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the BC BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to establish the requested MBS session resources, it replies to the gNB-CU-CP with the BC BEARER CONTEXT SETUP RESPONSE message. + +The gNB-CU-UP shall report to the gNB-CU-CP, in the BC BEARER CONTEXT SETUP RESPONSE message, the result of all the requested resources in the following way: + +- A list of BC MRBs which are successfully established shall be included in the *BC MRB Setup Response List* IE; +- A list of BC MRBs which failed to be established shall be included in the *BC MRB Failed List* IE; +- For each established BC MRB, a list of MBS QoS Flows which are successfully established shall be included in the *MBS QoS Flow Setup List* IE; +- For each established BC MRB, a list of MBS QoS Flows which failed to be established shall be included in the *MBS QoS Flow Failed List* IE. + +When the gNB-CU-UP reports the unsuccessful establishment of a BC MRB or MBS QoS Flow the cause value should be precise enough to enable the gNB-CU-CP to know the reason for the unsuccessful establishment. + +If the *Requested Action for Available Shared NG-U Termination* IE in the *BC Bearer Context To Setup* IE in the BC BEARER CONTEXT SETUP REQUEST message is set to + +- "apply available configuration" and an appropriate Shared NG-U Termination is available, the gNB-CU-UP shall apply the radio bearer configuration of the Shared NG-U Termination, and indicate in the BC BEARER CONTEXT SETUP RESPONSE message within the *Available BC MRB Configuration* IE in the *BC Bearer Context To Setup Response* IE the radio bearer configuration of the Shared NG-U Termination, if the radio bearer configuration of the Shared NG-U Termination is different than the one requested by the gNB-CU-CP. +- "apply requested configuration" the gNB-CU-UP shall make use of an available appropriate Shared NG-U Termination if the radio bearer configuration of the Shared NG-U Termination, is the same as the one requested by the gNB-CU-CP, otherwise allocate separate resources as requested by the gNB-CU-CP and indicate in the BC BEARER CONTEXT SETUP RESPONSE message within the *Available BC MRB Configuration* IE in the *BC Bearer Context To Setup Response* IE the radio bearer configuration of the Shared NG-U Termination. +- "apply available configuration if same as requested" the gNB-CU-UP shall make use of an available appropriate Shared NG-U Termination only if the radio bearer configuration of the Shared NG-U Termination is the same as the one requested by the gNB-CU-CP and reply with BC BEARER CONTEXT SETUP RESPONSE message. + +If the *Associated Session ID* IE is contained in the BC BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, take this information into account to determine the appropriate resources, as specified in TS 38.401 [2]. + +If the *MBS Service Area* IE is contained in the BC BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, take this information into account to determine the appropriate resources, as specified in TS 38.401 [2]. + +#### 8.6.1.1.3 Unsuccessful Operation + +![Sequence diagram for BC Bearer Context Setup procedure: Unsuccessful Operation. The diagram shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A horizontal arrow labeled 'BC BEARER CONTEXT SETUP REQUEST' points from gNB-CU-CP to gNB-CU-UP. A return horizontal arrow labeled 'BC BEARER CONTEXT SETUP FAILURE' points from gNB-CU-UP back to gNB-CU-CP. Both lifelines end with a thick horizontal bar representing the end of the sequence.](c0f64806753a053854921deb8f4fc798_img.jpg) + +Sequence diagram for BC Bearer Context Setup procedure: Unsuccessful Operation. The diagram shows two vertical lifelines: gNB-CU-CP on the left and gNB-CU-UP on the right. A horizontal arrow labeled 'BC BEARER CONTEXT SETUP REQUEST' points from gNB-CU-CP to gNB-CU-UP. A return horizontal arrow labeled 'BC BEARER CONTEXT SETUP FAILURE' points from gNB-CU-UP back to gNB-CU-CP. Both lifelines end with a thick horizontal bar representing the end of the sequence. + +**Figure 8.6.1.1.3-1: BC Bearer Context Setup procedure: Unsuccessful Operation.** + +If the gNB-CU-UP cannot establish the requested resources for the MBS session, it shall consider the procedure as failed and respond with the BC BEARER CONTEXT SETUP FAILURE message and an appropriate cause value. + +If the *Requested Action for Available Shared NG-U Termination* IE in the *BC Bearer Context To Setup* IE in the BC BEARER CONTEXT SETUP REQUEST message is set to "apply available configuration if same as requested" and the requested configuration does not match the available shared NG-U termination, the gNB-CU UP shall reply with BC BEARER CONTEXT SETUP FAILURE message. + +#### 8.6.1.1.4 Abnormal Conditions + +void. + +### 8.6.1.2 BC Bearer Context Modification (gNB-CU-CP initiated) + +#### 8.6.1.2.1 General + +The purpose of the gNB-CU-CP initiated BC Bearer Context Modification procedure is to allow the gNB-CU-CP to modify MBS session resources for a broadcast MBS session. The procedure uses MBS-associated signalling. + +## 8.6.1.2.2 Successful Operation + +![Sequence diagram showing the BC Bearer Context Modification procedure between gNB-CU-CP and gNB-CU-UP.](5bba23cc120ad806779f82df1c01bebf_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: BC BEARER CONTEXT MODIFICATION REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: BC BEARER CONTEXT MODIFICATION RESPONSE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +The diagram illustrates a sequence of messages between two entities: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a 'BC BEARER CONTEXT MODIFICATION REQUEST' message to the gNB-CU-UP. The gNB-CU-UP responds with a 'BC BEARER CONTEXT MODIFICATION RESPONSE' message. Both entities have a small black horizontal bar at the bottom of their lifelines, indicating the start and end of the sequence. + +Sequence diagram showing the BC Bearer Context Modification procedure between gNB-CU-CP and gNB-CU-UP. + +**Figure 8.6.1.2.2-1: BC Bearer Context Modification procedure, gNB-CU-CP initiated: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the BC BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to perform at least partially the requested modifications it replies to the gNB-CU-CP with the BC BEARER CONTEXT MODIFICATION RESPONSE message. + +The gNB-CU-UP shall report to the gNB-CU-CP, in the BC BEARER CONTEXT MODIFICATION RESPONSE message, the result of all the requested MBS session resources in the following way: + +- A list of BC MRBs which are successfully established or modified shall be included in the *BC MRB Setup or Modify Response List IE*; +- A list of BC MRBs which failed to be established or modified shall be included in the *BC MRB Failed List IE*; +- For each newly established or modified BC MRB, a list of MBS QoS Flows which are successfully established or modified shall be included in the *MBS QoS Flow Setup List IE*; +- For each newly established or modified BC MRB, a list of MBS QoS Flows which failed to be established or modified shall be included in the *MBS QoS Flow Failed List IE*. + +When the gNB-CU-UP reports the unsuccessful establishment of a BC MRB or MBS QoS Flow the cause value should be precise enough to enable the gNB-CU-CP to know the reason for the unsuccessful establishment. + +If the *BC Bearer Context NG-U TNL Info at 5GC To Setup or Modify IE* is contained in the BC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the previously received BC Bearer Context NG-U TNL Info at 5GC. + +### 8.6.1.2.3 Unsuccessful Operation + +![Sequence diagram for BC Bearer Context Modification procedure, gNB-CU-CP initiated: Unsuccessful Operation.](9f50279046b74a4e66a1a0144c3b1d11_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: BC BEARER CONTEXT MODIFICATION REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: BC BEARER CONTEXT MODIFICATION FAILURE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +The diagram illustrates an unsuccessful BC Bearer Context Modification procedure initiated by the gNB-CU-CP. It shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends a 'BC BEARER CONTEXT MODIFICATION REQUEST' message to the gNB-CU-UP. The gNB-CU-UP responds with a 'BC BEARER CONTEXT MODIFICATION FAILURE' message. Both lifelines have activation bars at the bottom, indicating they are active during the procedure. + +Sequence diagram for BC Bearer Context Modification procedure, gNB-CU-CP initiated: Unsuccessful Operation. + +**Figure 8.6.1.2.3-1: BC Bearer Context Modification procedure, gNB-CU-CP initiated: Unsuccessful Operation.** + +If the gNB-CU-UP cannot successfully perform any of the requested modifications, it shall respond with a BC BEARER CONTEXT MODIFICATION FAILURE message and an appropriate cause value. + +### 8.6.1.2.4 Abnormal Conditions + +void. + +## 8.6.1.3 BC Bearer Context Modification Required + +### 8.6.1.3.1 General + +The purpose of the gNB-CU-UP initiated BC Bearer Context Modification Required procedure is to allow the gNB-CU-UP to request the gNB-CU-CP to initiate the modification MBS session resources for a broadcast MBS session and inform the gNB-CU-CP. The procedure uses MBS-associated signalling. + +### 8.6.1.3.2 Successful Operation + +![Sequence diagram for BC Bearer Context Modification Required procedure, gNB-CU-UP initiated: Successful Operation.](53cbabe6260e970b4472b25503f74e9f_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-UP->>gNB-CU-CP: BC BEARER CONTEXT MODIFICATION REQUIRED + Note right of gNB-CU-CP: + gNB-CU-CP-->>gNB-CU-UP: BC BEARER CONTEXT MODIFICATION CONFIRM + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +The diagram illustrates a successful BC Bearer Context Modification Required procedure initiated by the gNB-CU-UP. It shows two lifelines: gNB-CU-CP and gNB-CU-UP. The gNB-CU-UP sends a 'BC BEARER CONTEXT MODIFICATION REQUIRED' message to the gNB-CU-CP. The gNB-CU-CP responds with a 'BC BEARER CONTEXT MODIFICATION CONFIRM' message. Both lifelines have activation bars at the bottom, indicating they are active during the procedure. + +Sequence diagram for BC Bearer Context Modification Required procedure, gNB-CU-UP initiated: Successful Operation. + +**Figure 8.6.1.3.2-1: BC Bearer Context Modification Required procedure, gNB-CU-UP initiated: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the BC BEARER CONTEXT MODIFICATION REQUIRED message to the gNB-CU-CP. The gNB-CU-CP replies to the gNB-CU-UP with the BC BEARER CONTEXT MODIFICATION CONFIRM message. + +#### 8.6.1.3.3 Abnormal Conditions + +void. + +#### 8.6.1.4 BC Bearer Context Release (gNB-CU-CP initiated) + +##### 8.6.1.4.1 General + +The purpose of the gNB-CU-CP initiated BC Bearer Context Release procedure is to allow the gNB-CU-CP to command the release of MBS session resources for a broadcast MBS Session. The procedure uses MBS-associated signalling. + +##### 8.6.1.4.2 Successful Operation + +![Sequence diagram showing the successful operation of the MC Bearer Context Release procedure. The gNB-CU-CP sends a BC BEARER CONTEXT RELEASE COMMAND to the gNB-CU-UP, and the gNB-CU-UP responds with a BC BEARER CONTEXT RELEASE COMPLETE message.](10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: BC BEARER CONTEXT RELEASE COMMAND + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: BC BEARER CONTEXT RELEASE COMPLETE + Note left of gNB-CU-CP: +``` + +Sequence diagram showing the successful operation of the MC Bearer Context Release procedure. The gNB-CU-CP sends a BC BEARER CONTEXT RELEASE COMMAND to the gNB-CU-UP, and the gNB-CU-UP responds with a BC BEARER CONTEXT RELEASE COMPLETE message. + +**Figure 8.6.1.4.2-1: MC Bearer Context Release procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the BC BEARER CONTEXT RELEASE COMMAND message to the gNB-CU-UP. + +Upon reception of the BC BEARER CONTEXT RELEASE COMMAND message, the gNB-CU-UP shall release all related signalling and user data transport resources and reply with the BC BEARER CONTEXT RELEASE COMPLETE message. + +##### 8.6.1.4.3 Abnormal Conditions + +Not applicable. + +#### 8.6.1.5 BC Bearer Context Release Request (gNB-CU-UP initiated) + +##### 8.6.1.5.1 General + +The purpose of the BC Bearer Context Release Request procedure is to allow the gNB-CU-UP to request the gNB-CU-CP to trigger the release of MBS session resources for a broadcast MBS Session. The procedure uses MBS-associated signalling. + +8.6.1.5.2 Successful Operation + +![Sequence diagram for BC Bearer Context Release Request procedure: Successful Operation. It shows two lifelines: gNB-CU-CP and gNB-CU-UP. A message labeled 'BC BEARER CONTEXT RELEASE REQUEST' is sent from gNB-CU-UP to gNB-CU-CP. Both lifelines end with a solid black bar representing a deactivation point.](d9cfc30025244dcd75766061f27ee09f_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: BC BEARER CONTEXT RELEASE REQUEST + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +Sequence diagram for BC Bearer Context Release Request procedure: Successful Operation. It shows two lifelines: gNB-CU-CP and gNB-CU-UP. A message labeled 'BC BEARER CONTEXT RELEASE REQUEST' is sent from gNB-CU-UP to gNB-CU-CP. Both lifelines end with a solid black bar representing a deactivation point. + +Figure 8.6.1.5.2-1: BC Bearer Context Release Request procedure: Successful Operation. + +The gNB-CU-UP initiates the procedure by sending the BC BEARER CONTEXT RELEASE REQUEST message to the gNB-CU-CP. + +**Interactions with gNB-CU-CP initiated BC Bearer Context Release procedure:** + +Upon reception of the BC BEARER CONTEXT RELEASE REQUEST message the gNB-CU-CP should initiate the BC Bearer Context Context Release procedure. + +8.6.1.5.3 Abnormal Conditions + +Not applicable. + +8.6.2 MBS Procedures for Multicast + +8.6.2.1 MC Bearer Context Setup + +8.6.2.1.1 General + +The purpose of the MC Bearer Context Setup procedure is to allow the gNB-CU-CP to establish MBS session resources for a multicast MBS session in the gNB-CU-UP. The procedure uses MBS-associated signalling. + +8.6.2.1.2 Successful Operation + +![Sequence diagram for MC Bearer Context Setup procedure: Successful Operation. It shows two lifelines: gNB-CU-CP and gNB-CU-UP. A message labeled 'MC BEARER CONTEXT SETUP REQUEST' is sent from gNB-CU-CP to gNB-CU-UP. A response message labeled 'MC BEARER CONTEXT SETUP RESPONSE' is sent from gNB-CU-UP back to gNB-CU-CP. Both lifelines end with a solid black bar representing a deactivation point.](973221d410a5fc97ca8868e730bc796a_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: + gNB-CU-CP->>gNB-CU-UP: MC BEARER CONTEXT SETUP REQUEST + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: MC BEARER CONTEXT SETUP RESPONSE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +Sequence diagram for MC Bearer Context Setup procedure: Successful Operation. It shows two lifelines: gNB-CU-CP and gNB-CU-UP. A message labeled 'MC BEARER CONTEXT SETUP REQUEST' is sent from gNB-CU-CP to gNB-CU-UP. A response message labeled 'MC BEARER CONTEXT SETUP RESPONSE' is sent from gNB-CU-UP back to gNB-CU-CP. Both lifelines end with a solid black bar representing a deactivation point. + +Figure 8.6.2.1.2-1: MC Bearer Context Setup procedure: Successful Operation. + +The gNB-CU-CP initiates the procedure by sending the MC BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to establish the requested MBS session resources, it replies to the gNB-CU-CP with the MC BEARER CONTEXT SETUP RESPONSE message. + +If MRB resources are requested to be setup by the gNB-CU-CP the gNB-CU-UP shall report to the gNB-CU-CP, in the MC BEARER CONTEXT SETUP RESPONSE message, the result of all the requested resources in the following way: + +- A list of MC MRBs which are successfully established shall be included in the *MC MRB Setup Response List IE*; +- A list of MC MRBs which failed to be established shall be included in the *MC MRB Failed List IE*; +- For each established MC MRB, a list of MBS QoS Flows which are successfully established shall be included in the *MBS QoS Flow Setup List IE*; +- For each established MC MRB, a list of MBS QoS Flows which failed to be established shall be included in the *MBS QoS Flow Failed List IE*. + +When the gNB-CU-UP reports the unsuccessful establishment of a MC MRB or MBS QoS Flow the cause value should be precise enough to enable the gNB-CU-CP to know the reason for the unsuccessful establishment. + +If MRB resources are requested to be setup by the gNB-CU-CP and if the *Requested Action for Available Shared NG-U Termination IE* in the *MC Bearer Context To Setup IE* in the MC BEARER CONTEXT SETUP REQUEST message is set to + +- "apply available configuration" and an appropriate Shared NG-U Termination is available, the gNB-CU-UP shall apply the radio bearer configuration of the Shared NG-U Termination, and indicate in the MC BEARER CONTEXT SETUP RESPONSE message within the *Available MC MRB Configuration IE* in the *MC Bearer Context To Setup Response IE* the radio bearer configuration of the Shared NG-U Termination, if the radio bearer configuration of the Shared NG-U Termination is different than the one requested by the gNB-CU-CP. +- "apply requested configuration" the gNB-CU-UP shall make use of an available appropriate Shared NG-U Termination if the radio bearer configuration of the Shared NG-U Termination, is the same as the one requested by the gNB-CU-CP, otherwise allocate separate resources as requested by the gNB-CU-CP and indicate in the MC BEARER CONTEXT SETUP RESPONSE message within the *Available MC MRB Configuration IE* in the *MC Bearer Context To Setup Response IE* the radio bearer configuration of the Shared NG-U Termination. +- "apply available configuration if same as requested" the gNB-CU-UP shall make use of an available appropriate Shared NG-U Termination only if the radio bearer configuration of the Shared NG-U Termination is the same as the one requested by the gNB-CU-CP and reply with MC BEARER CONTEXT SETUP RESPONSE message. + +If the *MBS Session Associated Information Non-Support-to-Support IE* is contained in the MC BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, perform duplication elimination between the packets delivered through the individual NG-U tunnel and the shared NG-U tunnel. + +If the *MBS Area Session ID IE* is received in the MC BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, store it and use it to establish the shared NG-U tunnel. + +If the *MC Bearer Context Status Change IE* set to "Resume" is contained in the MC BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, resume transmitting DL data. + +#### Interaction with other procedures + +If the *MC Bearer Context Status Change IE* is contained in the MC BEARER CONTEXT SETUP REQUEST message and set to "Suspend", the gNB-CU-UP shall, if supported, + +- suspend transmitting DL data to the gNB-DU. +- upon DL data arrival, buffer the received DL data and trigger the MC Bearer Notification procedure to indicate DL Data Arrival to the gNB-CU-CP. + +If the *MC Bearer Context Inactivity Timer* IE is contained in MC BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall take it into account when performing inactivity monitoring, and if applicable, trigger MC Bearer Notification procedure to indicate inactivity of the MC Bearer context to the gNB-CU-CP. + +#### 8.6.2.1.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the MC Bearer Context Setup procedure. The gNB-CU-CP sends an MC BEARER CONTEXT SETUP REQUEST to the gNB-CU-UP, which responds with an MC BEARER CONTEXT SETUP FAILURE.](cf018d13814389b0bd7f94a2f9bb812a_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: MC BEARER CONTEXT SETUP REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: MC BEARER CONTEXT SETUP FAILURE + Note left of gNB-CU-CP: +``` + +Sequence diagram showing the Unsuccessful Operation of the MC Bearer Context Setup procedure. The gNB-CU-CP sends an MC BEARER CONTEXT SETUP REQUEST to the gNB-CU-UP, which responds with an MC BEARER CONTEXT SETUP FAILURE. + +**Figure 8.6.2.1.3-1: MC Bearer Context Setup procedure: Unsuccessful Operation.** + +If the gNB-CU-UP cannot establish the requested MBS session resources for the multicast MBS session, it shall consider the procedure as failed and respond with the MC BEARER CONTEXT SETUP FAILURE message and an appropriate cause value. + +If the *Requested Action for Available Shared NG-U Termination* IE in the *MC Bearer Context To Setup* IE in the MC BEARER CONTEXT SETUP REQUEST message is set to "apply available configuration if same as requested" and the requested configuration does not match the available shared NG-U termination, the gNB-CU UP shall reply with MC BEARER CONTEXT SETUP FAILURE message. + +#### 8.6.2.1.4 Abnormal Conditions + +void. + +### 8.6.2.2 MC Bearer Context Modification (gNB-CU-CP initiated) + +#### 8.6.2.2.1 General + +The purpose of the gNB-CU-CP initiated MC Bearer Context Modification procedure is to allow the gNB-CU-CP to modify MBS session resources for a multicast MBS session. The procedure uses MBS-associated signalling. + +## 8.6.2.2.2 Successful Operation + +![Sequence diagram showing the MC Bearer Context Modification procedure between gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends an MC BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with an MC BEARER CONTEXT MODIFICATION RESPONSE.](f97535cdaa4fe017f4659512f4f78028_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: MC BEARER CONTEXT MODIFICATION REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: MC BEARER CONTEXT MODIFICATION RESPONSE + Note left of gNB-CU-CP: + +``` + +Sequence diagram showing the MC Bearer Context Modification procedure between gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends an MC BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with an MC BEARER CONTEXT MODIFICATION RESPONSE. + +**Figure 8.6.2.2.2-1: MC Bearer Context Modification procedure, gNB-CU-CP initiated: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the MC BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to perform at least partially the requested modifications it replies to the gNB-CU-CP with the MC BEARER CONTEXT MODIFICATION RESPONSE message. + +If MRB resources are requested to be setup or modified by the gNB-CU-CP, the gNB-CU-UP shall report to the gNB-CU-CP, in the MC BEARER CONTEXT MODIFICATION RESPONSE message, the result of all the requested resources in the following way: + +- A list of MC MRBs which are successfully established or modified shall be included in the *MC MRB Setup or Modify Response List IE*; +- A list of MC MRBs which failed to be established or modified shall be included in the *MC MRB Failed List IE*; +- For each newly established or modified MC MRB, a list of MBS QoS Flows which are successfully established or modified shall be included in the *MBS QoS Flow Setup List IE*; +- For each newly established or modified MC MRB, a list of MBS QoS Flows which failed to be established or modified shall be included in the *MBS QoS Flow Failed List IE*. + +When the gNB-CU-UP reports the unsuccessful establishment of a MC MRB or MBS QoS Flow the cause value should be precise enough to enable the gNB-CU-CP to know the reason for the unsuccessful establishment. + +If MRB resources are requested to be setup by the gNB-CU-CP and if the *Requested Action for Available Shared NG-U Termination IE* in the *MC Bearer Context To Modify IE* in the MC BEARER CONTEXT MODIFICATION REQUEST message is set to + +- "apply available configuration" and an appropriate Shared NG-U Termination is available, the gNB-CU-UP shall apply the radio bearer configuration of the Shared NG-U Termination, and indicate in the MC BEARER CONTEXT MODIFICATION RESPONSE message within the *Available MC MRB Configuration IE* in the *MC Bearer Context To Modify Response IE* the radio bearer configuration of the Shared NG-U Termination, if the radio bearer configuration of the Shared NG-U Termination is different than the one requested by the gNB-CU-CP. +- "apply requested configuration" the gNB-CU-UP shall make use of an available appropriate Shared NG-U Termination if the radio bearer configuration of the Shared NG-U Termination, is the same as the one requested by the gNB-CU-CP, otherwise allocate separate resources as requested by the gNB-CU-CP and indicate in the MC BEARER CONTEXT MODIFICATION RESPONSE message within the *Available MC MRB* + +*Configuration IE* in the *MC Bearer Context To Modify Response IE* the radio bearer configuration of the Shared NG-U Termination. + +- "apply available configuration if same as requested" the gNB-CU-UP shall make use of an available appropriate Shared NG-U Termination only if the radio bearer configuration of the Shared NG-U Termination is the same as the one requested by the gNB-CU-CP and reply with MC BEARER CONTEXT MODIFICATION RESPONSE message. + +If the *MC Bearer Context NG-U TNL Info at 5GC IE* is contained in the MC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the previously received MC Bearer Context NG-U TNL Info at 5GC. + +If the *MC Bearer Context NG-U TNL Info at NG-RAN Request IE* is contained in the MC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall include the *MC Bearer Context NG-U TNL Info at NG-RAN Modify Response IE* in the MC BEARER CONTEXT MODIFICATION RESPONSE message. + +If the *MRB Progress Information Request Type IE* is contained within the *MC Forwarding Resource Request IE* in the MC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, include the requested information in the *MRB Progress Information IE* within the *MC Forwarding Resource Response IE* in the MC BEARER CONTEXT MODIFICATION RESPONSE message. If the *MRB Forwarding Address Request IE* set to "true" is contained in the *MC Forwarding Resource Request IE* in the MC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, include the *MRB Forwarding Address IE* within the *MC Forwarding Resource Response IE* in the MC BEARER CONTEXT MODIFICATION RESPONSE message. + +If the *MC Forwarding Resource Indication IE* is contained in the MC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, take the included information into account. + +If the *MC Forwarding Resource Release IE* is contained in the MC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, release the indicated MC Forwarding Resource. + +If the *MBS Session Associated Information Non-Support-to-Support IE* is contained in the MC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, perform duplication elimination between the packets delivered through the individual NG-U tunnel and the shared NG-U tunnel. + +If the *MC Bearer Context Status Change IE* set to "Resume" is contained in the MC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, resume transmitting DL data. + +### Interaction with other procedures + +If the *MC Bearer Context Status Change IE* is contained in MC BEARER CONTEXT MODIFICATION REQUEST message and set to "Suspend", the gNB-CU-UP shall, if supported, + +- suspend transmitting DL data to the gNB-DU. +- upon DL data arrival, buffer the received DL data and trigger the MC Bearer Notification procedure to indicate DL Data Arrival to the gNB-CU-CP. + +If the *MC Bearer Context Inactivity Timer IE* is contained in MC BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account when perform inactivity monitoring, and if applicable, trigger MC Bearer Notification procedure to indicate inactivity of the MC Bearer context to the gNB-CU-CP. + +### 8.6.2.2.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the MC Bearer Context Modification procedure. The gNB-CU-CP sends an MC BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with an MC BEARER CONTEXT MODIFICATION FAILURE.](e5ded42f8e352da02ee86cb55550c45d_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: MC BEARER CONTEXT MODIFICATION REQUEST + Note right of gNB-CU-UP: + gNB-CU-UP-->>gNB-CU-CP: MC BEARER CONTEXT MODIFICATION FAILURE + Note left of gNB-CU-CP: + Note right of gNB-CU-UP: +``` + +Sequence diagram showing the Unsuccessful Operation of the MC Bearer Context Modification procedure. The gNB-CU-CP sends an MC BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with an MC BEARER CONTEXT MODIFICATION FAILURE. + +**Figure 8.6.2.2.3-1: MC Bearer Context Modification procedure, gNB-CU-CP initiated: Unsuccessful Operation.** + +If the gNB-CU-UP cannot successfully perform any of the requested modifications, it shall respond with a MC BEARER CONTEXT MODIFICATION FAILURE message and an appropriate cause value. + +If the *Requested Action for Available Shared NG-U Termination* IE in the *MC Bearer Context To Setup* IE in the MC BEARER CONTEXT MODIFICATION REQUEST message is set to "apply available configuration if same as requested" and the requested configuration does not match the available shared NG-U termination, the gNB-CU UP shall reply with MC BEARER CONTEXT MODIFICATION FAILURE message. + +### 8.6.2.2.4 Abnormal Conditions + +void. + +## 8.6.2.3 MC Bearer Context Modification Required (gNB-CU-UP initiated) + +### 8.6.2.3.1 General + +The purpose of the gNB-CU-UP initiated MC Bearer Context Modification Required procedure is to allow the gNB-CU-UP to request the gNB-CU-CP to initiate the modification of MBS session resources for a multicast MBS session and inform the gNB-CU-CP. The procedure uses MBS-associated signalling. + +### 8.6.2.3.2 Successful Operation + +![Sequence diagram for MC Bearer Context Modification Required procedure, gNB-CU-UP initiated: Successful Operation.](0a3ab80d35c138cc4038b5758f6ff34d_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-CP: + gNB-CU-UP->>gNB-CU-CP: MC BEARER CONTEXT MODIFICATION REQUIRED + Note right of gNB-CU-UP: + gNB-CU-CP->>gNB-CU-UP: MC BEARER CONTEXT MODIFICATION CONFIRM + Note left of gNB-CU-CP: +``` + +The diagram shows a sequence of two messages between gNB-CU-UP and gNB-CU-CP. The gNB-CU-UP sends an 'MC BEARER CONTEXT MODIFICATION REQUIRED' message to the gNB-CU-CP. The gNB-CU-CP responds with an 'MC BEARER CONTEXT MODIFICATION CONFIRM' message. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for MC Bearer Context Modification Required procedure, gNB-CU-UP initiated: Successful Operation. + +**Figure 8.6.2.3.2-1: MC Bearer Context Modification Required procedure, gNB-CU-UP initiated: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the MC BEARER CONTEXT MODIFICATION REQUIRED message to the gNB-CU-CP. The gNB-CU-CP replies to the gNB-CU-UP with the MC BEARER CONTEXT MODIFICATION CONFIRM message. + +If the *MC Forwarding Resource Release Indication* IE is contained in the MC BEARER CONTEXT MODIFICATION REQUIRED message, the gNB-CU-CP shall, if supported, assume that the indicated MC Forwarding Resource was released by the gNB-CU-UP. + +### 8.6.2.3.3 Abnormal Conditions + +void + +## 8.6.2.4 MC Bearer Context Release (gNB-CU-CP initiated) + +### 8.6.2.4.1 General + +The purpose of the gNB-CU-CP initiated MC Bearer Context Release procedure is to allow the gNB-CU-CP to command the release of MBS session resources for a multicast MBS Session. The procedure uses MBS-associated signalling. + +### 8.6.2.4.2 Successful Operation + +![Sequence diagram for MC Bearer Context Release procedure: Successful Operation.](c2a437e6e47315a089530c05883ca3eb_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-CU-CP: + gNB-CU-CP->>gNB-CU-UP: MC BEARER CONTEXT RELEASE COMMAND + Note right of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: MC BEARER CONTEXT RELEASE COMPLETE + Note left of gNB-CU-CP: +``` + +The diagram shows a sequence of two messages between gNB-CU-CP and gNB-CU-UP. The gNB-CU-CP sends an 'MC BEARER CONTEXT RELEASE COMMAND' message to the gNB-CU-UP. The gNB-CU-UP responds with an 'MC BEARER CONTEXT RELEASE COMPLETE' message. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for MC Bearer Context Release procedure: Successful Operation. + +**Figure 8.6.2.4.2-1: MC Bearer Context Release procedure: Successful Operation.** + +The gNB-CU-CP initiates the procedure by sending the MC BEARER CONTEXT RELEASE COMMAND message to the gNB-CU-UP. + +Upon reception of the MC BEARER CONTEXT RELEASE COMMAND message, the gNB-CU-UP shall release all related signalling and user data transport resources and reply with the MC BEARER CONTEXT RELEASE COMPLETE message. + +#### 8.6.2.4.3 Abnormal Conditions + +Not applicable. + +### 8.6.2.5 MC Bearer Context Release Request (gNB-CU-UP initiated) + +#### 8.6.2.5.1 General + +The purpose of the MC Bearer Context Release Request procedure is to allow the gNB-CU-UP to request the gNB-CU-CP to trigger the release of MBS session resources for a multicast MBS Session. The procedure uses MBS-associated signalling. + +#### 8.6.2.5.2 Successful Operation + +![Sequence diagram showing the MC Bearer Context Release Request procedure. The gNB-CU-UP sends an MC BEARER CONTEXT RELEASE REQUEST message to the gNB-CU-CP.](0adcd19063a66145a465add40bf956e6_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + Note left of gNB-CU-UP: + gNB-CU-UP->>gNB-CU-CP: MC BEARER CONTEXT RELEASE REQUEST + Note right of gNB-CU-CP: + activate gNB-CU-CP + deactivate gNB-CU-CP +``` + +Sequence diagram showing the MC Bearer Context Release Request procedure. The gNB-CU-UP sends an MC BEARER CONTEXT RELEASE REQUEST message to the gNB-CU-CP. + +**Figure 8.6.2.5.2-1: MC Bearer Context Release Request procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the MC BEARER CONTEXT RELEASE REQUEST message to the gNB-CU-CP. + +#### **Interactions with gNB-CU-CP initiated MC Bearer Context Release procedure:** + +Upon reception of the MC BEARER CONTEXT RELEASE REQUEST message the gNB-CU-CP should initiate the MC Bearer Context Context Release procedure. + +#### 8.6.2.5.3 Abnormal Conditions + +Not applicable. + +### 8.6.2.6 MC Bearer Notification + +#### 8.6.2.6.1 General + +The purpose of MC Bearer Notification procedure is initiated by the gNB-CU-UP to indicate DL data arrival or inactivity of the MC Bearer context. + +The procedure uses MBS-associated signalling. + +#### 8.6.2.6.2 Successful Operation + +![Sequence diagram showing the MC Bearer Notification procedure for successful operation. The gNB-CU-U sends an MC BEARER NOTIFICATION message to the NB-CU-CP.](18d7d8de298d79e7bc87af5217f11203_img.jpg) + +``` +sequenceDiagram + participant gNB-CU-U + participant NB-CU-CP + Note left of gNB-CU-U: + gNB-CU-U->>NB-CU-CP: MC BEARER NOTIFICATION + Note right of NB-CU-CP: + Note left of gNB-CU-U: + Note right of gNB-CU-U: +``` + +Sequence diagram showing the MC Bearer Notification procedure for successful operation. The gNB-CU-U sends an MC BEARER NOTIFICATION message to the NB-CU-CP. + +**Figure 8.6.2.6.2-1: MC Bearer Notification procedure: Successful Operation.** + +The gNB-CU-UP initiates the procedure by sending the MC BEARER NOTIFICATION message to the gNB-CU-CP. + +#### 8.6.2.6.3 Abnormal Conditions + +Not applicable. + +## 9 Elements for E1AP communication + +NOTE: In this section, each occurrence of gNB-CU-CP could be replaced by eNB-CP or ng-eNB-CU-CP, and each occurrence of gNB-CU-UP could be replaced by eNB-UP or ng-eNB-CU-UP, for eNB CP-UP separation and ng-eNB CP-UP separation respectively. + +### 9.1 General + +Subclauses 9.2 and 9.3 present the E1AP message and IE definitions in tabular format. The corresponding ASN.1 definition is presented in subclause 9.4. In case there is contradiction between the tabular format 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. + +The messages have been defined in accordance to the guidelines specified in TR 25.921 [5]. + +When specifying IEs 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; + +The following attributes are used for the tabular description of the messages and information elements: Presence, Range Criticality and Assigned Criticality. Their definition and use can be found in TS 38.413 [6]. + +## 9.2 Message Functional Definition and Content + +### 9.2.1 Interface Management messages + +#### 9.2.1.1 RESET + +This message is sent by both the gNB-CU-CP and the gNB-CU-UP and is used to request that the E1 interface, or parts of the E1 interface, to be reset. + +Direction: gNB-CU-CP → gNB-CU-UP and gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-------------------------------------------------|-------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| CHOICE Reset Type | M | | | | YES | reject | +| >E1 interface | | | | | | | +| >>Reset All | M | | ENUMERATED
(Reset all,...) | | - | | +| >Part of E1 interface | | | | | | | +| >>UE-associated logical E1-connection list | | 1 | | | - | | +| >>>UE-associated logical E1-connection Item | | 1 ..
| | | EACH | reject | +| >>>>gNB-CU-CP UE E1AP ID | O | | 9.3.1.4 | | - | | +| >>>>gNB-CU-UP UE E1AP ID | O | | 9.3.1.5 | | - | | + +| Range bound | Explanation | +|---------------------------------------|------------------------------------------------------------------------------------------------------| +| maxnoofIndividualE1ConnectionsToReset | Maximum no. of UE-associated logical E1-connections allowed to reset in one message. Value is 65536. | + +#### 9.2.1.2 RESET ACKNOWLEDGE + +This message is sent by both the gNB-CU-CP and the gNB-CU-UP as a response to a RESET message. + +Direction: gNB-CU-UP → gNB-CU-CP and gNB-CU-CP → gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------------------------------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| UE-associated logical E1-connection list | | 0..1 | | | YES | ignore | +| >UE-associated logical E1-connection Item | | 1 ..
| | | EACH | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|------------------------|-----------------------|-----------------------|-------------|----------------------| +| | | onsToRes et> | | | | | +| >>gNB-CU-CP UE E1AP ID | O | | 9.3.1.4 | | - | | +| >>gNB-CU-UP UE E1AP ID | O | | 9.3.1.5 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------------------|------------------------------------------------------------------------------------------------------| +| maxnoofIndividualE1ConnectionsToReset | Maximum no. of UE-associated logical E1-connections allowed to reset in one message. Value is 65536. | + +### 9.2.1.3 ERROR INDICATION + +This message is sent by both the gNB-CU-CP and the gNB-CU-UP and is used to indicate that some error has been detected in the node. + +Direction: gNB-CU-CP → gNB-CU-UP and gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|---------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| Transaction ID | M | | 9.3.1.53 | This IE is ignored if received in UE associated signalling message. | YES | reject | +| gNB-CU-CP UE E1AP ID | O | | 9.3.1.4 | | YES | ignore | +| gNB-CU-UP UE E1AP ID | O | | 9.3.1.5 | | YES | ignore | +| Cause | O | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| gNB-CU-CP MBS E1AP ID | O | | 9.3.1.106 | | YES | ignore | +| gNB-CU-UP MBS E1AP ID | O | | 9.3.1.107 | | YES | ignore | + +### 9.2.1.4 GNB-CU-UP E1 SETUP REQUEST + +This message is sent by the gNB-CU-UP to transfer information for a TNL association. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-------------------------------------|---------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-UP ID | M | | 9.3.1.15 | | YES | reject | +| gNB-CU-UP Name | O | | PrintableString( SIZE(1..150,...) ) | Human readable name of the gNB-CU-UP. | YES | ignore | +| CN Support | M | | ENUMERATED | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|---------------------|-----------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| | | | (EPC, 5GC, both, ...) | | | | +| Supported PLMNs | | 1.. | | Supported PLMNs | YES | reject | +| >PLMN Identity | M | | 9.3.1.7 | | - | - | +| >Slice Support List | O | | 9.3.1.8 | Supported S-NSSAIs per PLMN. | - | - | +| >Extended Slice Support List | O | | 9.3.1.94 | Additional Supported S-NSSAIs per PLMN. | YES | reject | +| >NR CGI Support List | O | | 9.3.1.36 | Supported cells for gNB CP-UP separation. | - | - | +| >QoS Parameters Support List | O | | 9.3.1.37 | Supported QoS parameters per PLMN. | - | - | +| >NPN Support Information | O | | 9.3.1.83 | NOTE: This IE is not applicable to eNB-CP/eNB-UP and ng-eNB-CU-CP/ng-eNB-CU-UP | YES | reject | +| >Extended NR CGI Support List | O | | 9.3.1.97 | Additional supported cells per PLMN. | YES | ignore | +| >ECGI Support List | O | | 9.3.1.100 | Supported cells for eNB or ng-eNB CP-UP separation. | - | - | +| gNB-CU-UP Capacity | O | | 9.3.1.56 | | YES | ignore | +| Transport Network Layer Address Info | O | | 9.3.2.7 | | YES | ignore | +| Extended gNB-CU-UP Name | O | | 9.3.1.95 | | YES | ignore | +| gNB-CU-UP MBS Support Information | O | | 9.3.1.110 | | YES | reject | + +| Range bound | Explanation | +|---------------|-------------------------------------------------| +| maxnoofSPLMNs | Maximum no. of Supported PLMN Ids. Value is 12. | + +### 9.2.1.5 GNB-CU-UP E1 SETUP RESPONSE + +This message is sent by the gNB-CU-CP to transfer information for a TNL association. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------------------|---------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-CP Name | O | | PrintableString(SIZE(1..150,...)) | Human readable name of the gNB- | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | ) | CU-CP. | | | +| Transport Network Layer Address Info | O | | 9.3.2.7 | | YES | ignore | +| Extended gNB-CU-CP Name | O | | 9.3.1.96 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.6 GNB-CU-UP E1 SETUP FAILURE + +This message is sent by the gNB-CU-CP to indicate E1 Setup failure. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time To wait | O | | 9.3.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.7 GNB-CU-CP E1 SETUP REQUEST + +This message is sent by the gNB-CU-CP to transfer information for a TNL association. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-------------------------------------------|---------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-CP Name | O | | PrintableString(
SIZE(1..150,...)
) | Human readable name of the gNB-CU-CP. | YES | ignore | +| Transport Network Layer Address Info | O | | 9.3.2.7 | | YES | ignore | +| Extended gNB-CU-CP Name | O | | 9.3.1.95 | | YES | ignore | + +### 9.2.1.8 GNB-CU-CP E1 SETUP RESPONSE + +This message is sent by the gNB-CU-UP to transfer information for a TNL association. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-------------------------------------------|---------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-UP ID | M | | 9.3.1.15 | | YES | reject | +| gNB-CU-UP Name | O | | PrintableString(
SIZE(1..150,...)
) | Human readable name of the gNB-CU-UP. | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|---------------------|----------------------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| CN Support | M | | ENUMERATED (EPC, 5GC, both, ...) | | YES | reject | +| Supported PLMNs | | 1.. | | Supported PLMNs | YES | reject | +| >PLMN Identity | M | | 9.3.1.7 | | - | - | +| >Slice Support List | O | | 9.3.1.8 | Supported S-NSSAIs per PLMN. | - | - | +| >Extended Slice Support List | O | | 9.3.1.94 | Additional Supported S-NSSAIs per PLMN. | YES | reject | +| >NR CGI Support List | O | | 9.3.1.36 | Supported cells for gNB CP-UP separation. | - | - | +| >QoS Parameters Support List | O | | 9.3.1.37 | Supported QoS parameters per PLMN. | - | - | +| >NPN Support Information | O | | 9.3.1.83 | NOTE: This IE is not applicable to eNB-CP/eNB-UP and ng-eNB-CU-CP/ng-eNB-CU-UP | YES | reject | +| >Extended NR CGI Support List | O | | 9.3.1.97 | Additional supported cells per PLMN. | YES | ignore | +| >ECGI Support List | O | | 9.3.1.100 | Supported cells for eNB or ng-eNB CP-UP separation. | - | - | +| gNB-CU-UP Capacity | O | | 9.3.1.56 | | YES | ignore | +| Transport Network Layer Address Info | O | | 9.3.2.7 | | YES | ignore | +| Extended gNB-CU-UP Name | O | | 9.3.1.95 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|---------------|-------------------------------------------------| +| maxnoofSPLMNs | Maximum no. of Supported PLMN Ids. Value is 12. | + +### 9.2.1.9 GNB-CU-CP E1 SETUP FAILURE + +This message is sent by the gNB-CU-UP to indicate E1 Setup failure. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time To wait | O | | 9.3.1.6 | | YES | ignore | + +| | | | | | | | +|-------------------------|---|--|---------|--|-----|--------| +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +|-------------------------|---|--|---------|--|-----|--------| + +## 9.2.1.10 GNB-CU-UP CONFIGURATION UPDATE + +This message is sent by the gNB-CU-UP to transfer updated information for a TNL association. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|--------------------------------------------|-------------------------------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-UP ID | O | | 9.3.1.15 | | YES | reject | +| gNB-CU-UP Name | O | | PrintableString(
SIZE(1..150,...)
) | Human readable name of the gNB-CU-UP. | YES | ignore | +| Supported PLMNs | | 0.. <maxno ofSPLMNs> | | Supported PLMNs | YES | reject | +| >PLMN Identity | M | | 9.3.1.7 | | - | - | +| >Slice Support List | O | | 9.3.1.8 | Supported S-NSSAIs per PLMN. | - | - | +| >Extended Slice Support List | O | | 9.3.1.94 | Additional Supported S-NSSAIs per PLMN. | YES | reject | +| >NR CGI Support List | O | | 9.3.1.36 | Supported cells for gNB CP-UP separation. | - | - | +| >QoS Parameters Support List | O | | 9.3.1.37 | Supported QoS parameters per PLMN. | - | - | +| >NPN Support Information | O | | 9.3.1.83 | NOTE: This IE is not applicable to eNB-CP/eNB-UP and ng-eNB-CU-CP/ng-eNB-CU-UP | YES | reject | +| >Extended NR CGI Support List | O | | 9.3.1.97 | Additional supported cells per PLMN. | YES | ignore | +| >ECGI Support List | O | | 9.3.1.100 | Supported cells for eNB or ng-eNB CP-UP separation. | - | - | +| gNB-CU-UP Capacity | O | | 9.3.1.56 | | YES | ignore | +| gNB-CU-UP TNLA To Remove List | | 0..1 | | | YES | reject | +| >gNB-CU-UP TNLA To Remove Item IEs | | 1.. <maxno ofTNLAssociations> | | | - | - | +| >>TNLA Transport Layer Address | M | | CP Transport Layer Information 9.3.2.2 | Transport Layer Address of the gNB-CU-UP. | - | - | +| >>TNLA Transport Layer Address gNB-CU-CP | O | | CP Transport Layer | Transport Layer Address of the | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | Information 9.3.2.2 | gNB-CU-CP. | | | +| Transport Network Layer Address Info | O | | 9.3.2.7 | | YES | ignore | +| Extended gNB-CU-UP Name | O | | 9.3.1.96 | | YES | ignore | +| gNB-CU-UP MBS Support Information | O | | 9.3.1.110 | | YES | reject | + +| Range bound | Explanation | +|------------------------|-------------------------------------------------------------------------------------------| +| maxnooSPLMNs | Maximum no. of Supported PLMN Ids. Value is 12. | +| maxnoofTNLAssociations | Maximum numbers of TNL Associations between the gNB-CU-UP and the gNB-CU-CP. Value is 32. | + +### 9.2.1.11 GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE + +This message is sent by a gNB-CU-CP to a gNB-CU-UP to acknowledge update of information for a TNL association. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Transport Network Layer Address Info | O | | 9.3.2.7 | | YES | ignore | + +### 9.2.1.12 GNB-CU-UP CONFIGURATION UPDATE FAILURE + +This message is sent by the gNB-CU-CP to indicate gNB-CU-UP Configuration Update failure. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time To wait | O | | 9.3.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.13 GNB-CU-CP CONFIGURATION UPDATE + +This message is sent by the gNB-CU-CP to transfer updated information for a TNL association. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------------|----------|--------------------------------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-CP Name | O | | PrintableString(
SIZE(1..150,...)
) | Human readable name of the gNB-CU-CP | YES | ignore | +| gNB-CU-CP TNLA To Add List | | 0..1 | | | YES | ignore | +| >gNB-CU-CP TNLA To Add Item IEs | | 1.. <maxno ofTNLAssociations> | | | - | - | +| >>TNLA Transport Layer Information | M | | CP Transport Layer Information 9.3.2.2 | Transport Layer Address of the gNB-CU-CP. | - | - | +| >>TNLA Usage | M | | ENUMERATED (ue, non-ue, both, ...) | Indicates whether the TNLA is only used for UE-associated signalling, or non-UE-associated signalling, or both. For usage of this IE, refer to TS 37.482 [18]. | - | - | +| gNB-CU-CP TNLA To Remove List | | 0..1 | | | YES | ignore | +| >gNB-CU-CP TNLA To Remove Item IEs | | 1.. <maxno ofTNLAssociations> | | | - | - | +| >>TNLA Transport Layer Address | M | | CP Transport Layer Information 9.3.2.2 | Transport Layer Address of the gNB-CU-CP. | - | - | +| >>TNLA Transport Layer Address gNB-CU-UP | O | | CP Transport Layer Information 9.3.2.2 | Transport Layer Address of the gNB-CU-UP. | YES | reject | +| gNB-CU-CP TNLA To Update List | | 0..1 | | | YES | ignore | +| >gNB-CU-CP TNLA To Update Item IEs | | 1.. <maxno ofTNLAssociations> | | | - | - | +| >>TNLA Transport Layer Address | M | | CP Transport Layer Address 9.3.2.2 | Transport Layer Address of the gNB-CU-CP. | - | - | +| >>TNLA Usage | O | | ENUMERATED (ue, non-ue, both, ...) | Indicates whether the TNLA is only used for UE-associated signalling, or non-UE-associated signalling, or both. For usage of this IE, refer to TS 37.482 [18]. | - | - | +| Transport Network Layer Address Info | O | | 9.3.2.7 | | YES | ignore | +| Extended gNB-CU-CP | O | | 9.3.1.95 | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Name | | | | | | | + +| Range bound | Explanation | +|------------------------|-------------------------------------------------------------------------------------------| +| maxnoofTNLAssociations | Maximum numbers of TNL Associations between the gNB-CU-CP and the gNB-CU-UP. Value is 32. | + +### 9.2.1.14 GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE + +This message is sent by a gNB-CU-UP to a gNB-CU-CP to acknowledge update of information for a TNL association. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|------------------------------|----------------------------------------|------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-CP TNLA Setup List | | 0..1 | | | YES | ignore | +| >gNB-CU-CP TNLA Setup Item IEs | | 1.. | | | - | - | +| >>TNLA Transport Layer Address | M | | CP Transport Layer Information 9.3.2.2 | Transport Layer Address of the gNB-CU-CP | - | - | +| gNB-CU-CP TNLA Failed to Setup List | | 0..1 | | | YES | ignore | +| >gNB-CU-CP TNLA Failed To Setup Item IEs | | 1.. | | | - | - | +| >>TNLA Transport Layer Address | M | | CP Transport Layer Information 9.3.2.2 | Transport Layer Address of the gNB-CU-CP | - | - | +| >>Cause | M | | 9.3.1.2 | | | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Transport Network Layer Address Info | O | | 9.3.2.7 | | YES | ignore | + +| Range bound | Explanation | +|------------------------|-------------------------------------------------------------------------------------------| +| maxnoofTNLAssociations | Maximum numbers of TNL Associations between the gNB-CU-CP and the gNB-CU-UP. Value is 32. | + +### 9.2.1.15 GNB-CU-CP CONFIGURATION UPDATE FAILURE + +This message is sent by the gNB-CU-UP to indicate gNB-CU-CP Configuration Update failure. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time To wait | O | | 9.3.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.16 E1 RELEASE REQUEST + +This message is sent by both the gNB-CU-CP and the gNB-CU-UP and is used to request the release of the E1 interface. + +Direction: gNB-CU-CP → gNB-CU-UP and gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.1.17 E1 RELEASE RESPONSE + +This message is sent by both the gNB-CU-CP and the gNB-CU-UP as a response to an E1 RELEASE REQUEST message. + +Direction: gNB-CU-UP → gNB-CU-CP and gNB-CU-CP → gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.18 GNB-CU-UP STATUS INDICATION + +This message is sent by the gNB-CU-UP to indicate to the gNB-CU-CP its status of overload. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-----------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-UP Overload Information | M | | ENUMERATED (overloaded, not-overloaded) | | YES | reject | + +### 9.2.1.19 RESOURCE STATUS REQUEST + +This message is sent by an gNB-CU-CP to gNB-CU-UP to initiate the requested measurement according to the parameters given in the message. + +Direction: gNB-CU-CP → gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------------------------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-CP Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU-CP | YES | reject | +| gNB-CU-UP Measurement ID | C-
ifRegistrationRequestStop | | INTEGER (1..4095,...) | Allocated by gNB-CU-UP | YES | ignore | +| Registration Request | M | | ENUMERATED (start, stop, ...) | Type of request for which the resource status is required. | YES | reject | +| Report Characteristics | C-
ifRegistrationRequestStart | | BITSTRING (SIZE(36)) | Each position in the bitmap indicates measurement object the gNB-CU-UP is requested to report.
First Bit = TNL Available Capacity Ind Periodic,
Second Bit = HW Capacity Ind Periodic.
Other bits shall be ignored by the gNB-CU-UP. | YES | reject | +| Reporting Periodicity | O | | ENUMERATED (500ms, 1000ms, 2000ms, 5000ms, 10000ms, 20000ms, 30000ms, 40000ms, 50000ms, 60000ms, 70000ms, 80000ms, 90000ms, 100000ms, 110000ms, 120000ms, ...) | Periodicity that can be used for reporting. Also used as the averaging window length for all measurement object if supported. | YES | ignore | + +| Condition | Explanation | +|----------------------------|---------------------------------------------------------------------------------------------| +| ifRegistrationRequestStop | This IE shall be present if the Registration Request IE is set to the value "stop" | +| ifRegistrationRequestStart | This IE shall be present if the Registration Request IE is set to the value "start". | + +## 9.2.1.20 RESOURCE STATUS RESPONSE + +This message is sent by the gNB-CU-UP to indicate that the requested measurement, for all the measurement objects + +included in the measurement is successfully initiated. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|-----------------------|------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-CP Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU-CP | YES | reject | +| gNB-CU-UP Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU-UP | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.21 RESOURCE STATUS FAILURE + +This message is sent by the gNB-CU-UP to indicate that for any of the requested measurement objects the measurement cannot be initiated. + +Direction: gNB-CU-UP → gNB-CU-CP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|-----------------------|------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-CP Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU-CP | YES | reject | +| gNB-CU-UP Measurement ID | O | | INTEGER (1..4095,...) | Allocated by gNB-CU-UP | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.22 RESOURCE STATUS UPDATE + +This message is sent by gNB-CU-UP to gNB-CU-CP to report the results of the requested measurements. + +Direction: gNB-CU-UP → gNB-CU-CP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-------|-----------------------|------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| gNB-CU-CP Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU-CP | YES | reject | +| gNB-CU-UP Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU-UP | YES | ignore | +| TNL Available Capacity Indicator | O | | 9.3.1.72 | | YES | ignore | +| HW Capacity Indicator | O | | 9.3.1.73 | | YES | ignore | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------| +| maxnooSPLMNs | Maximum no. of Supported PLMN Ids. Value is 12. | +| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. | + +## 9.2.2 Bearer Context Management messages + +### 9.2.2.1 BEARER CONTEXT SETUP REQUEST + +This message is sent by the gNB-CU-CP to request the gNB-CU-UP to setup a bearer context. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|-------|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| Security Information | M | | 9.3.1.10 | | YES | reject | +| UE DL Aggregate Maximum Bit Rate | M | | Bit Rate
9.3.1.20 | | YES | reject | +| UE DL Maximum Integrity Protected Data Rate | O | | Bit Rate
9.3.1.20 | The Bit Rate is a portion of the UE's Maximum Integrity Protected Data Rate, and is enforced by the gNB-CU-UP node. | YES | reject | +| Serving PLMN | M | | PLMN Identity
9.3.1.7 | | YES | ignore | +| Activity Notification Level | M | | 9.3.1.67 | | YES | reject | +| UE Inactivity Timer | O | | Inactivity Timer
9.3.1.54 | Included if the Activity Notification Level is set to UE. | - | - | +| Bearer Context Status Change | O | | ENUMERATED (Suspend, Resume, ..., ResumeforSDT ) | Indicates the status of the Bearer Context.
NOTE: This IE is not applicable to eNB-CP/eNB-UP. | YES | reject | +| CHOICE System | M | | | | YES | reject | +| >E-UTRAN | | | | | | | +| >>DRB To Setup List | M | | DRB To Setup List E-UTRAN
9.3.3.1 | | YES | reject | +| >>Subscriber Profile ID for RAT/Frequency priority | O | | 9.3.1.69 | | YES | ignore | +| >>Additional RRM Policy Index | O | | 9.3.1.70 | | YES | Ignore | +| >NG-RAN | | | | | | | +| >>PDU Session Resource To Setup List | M | | 9.3.3.2 | | YES | reject | +| RAN UE ID | O | | OCTET STRING (SIZE(8)) | | YES | ignore | +| gNB-DU ID | O | | 9.3.1.65 | Included whenever it is known by the gNB-CU-CP or by the ng-eNB-CU- | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | CP | | | +| Trace Activation | O | | 9.3.1.68 | | YES | ignore | +| NPN Context Information | O | | 9.3.1.84 | | YES | reject | +| Management Based MDT PLMN List | O | | MDT PLMN List 9.3.1.89 | | YES | ignore | +| CHO Initiation | O | | ENUMERATED (True, ...) | | YES | reject | +| Additional Handover Information | O | | ENUMERATED (Discard PDCP SN, ...) | If set to "Discard PDCP SN", indicates that the forwarded PDCP SNs have to be removed | YES | ignore | +| Direct Forwarding Path Availability | O | | 9.3.1.98 | | YES | ignore | +| gNB-CU-UP UE E1AP ID | O | | 9.3.1.5 | | YES | ignore | +| MDT Polluted Measurement Indicator | O | | ENUMERATED (IDC, no-IDC, ...) | Indication on whether MDT Measurement affect (e.g. IDC) is undertake or not. | YES | ignore | +| UE Slice Maximum Bit Rate List | O | | 9.3.1.102 | | YES | ignore | +| SCG Activation Status | O | | 9.3.1.105 | | YES | ignore | +| MT-SDT Information Request | O | | ENUMERATED (true, ...) | Indicates to request the report of MT-SDT Information. | YES | ignore | +| SDT Data Size Threshold | O | | INTEGER (1..192000, ...) | Unit: byte. | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +## 9.2.2.2 BEARER CONTEXT SETUP RESPONSE + +This message is sent by the gNB-CU-UP to confirm the setup of the requested bearer context. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| CHOICE System | M | | | | YES | reject | +| >E-UTRAN | | | | | | | +| >>DRB Setup List | M | | DRB Setup List E-UTRAN | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|---------------------------------------|-----------------------|-------------|----------------------| +| | | | 9.3.3.3 | | | | +| >>DRB Failed List | O | | DRB Failed List
E-UTRAN
9.3.3.4 | | YES | reject | +| >NG-RAN | | | | | | | +| >>PDU Session
Resource Setup List | M | | 9.3.3.5 | | YES | reject | +| >>PDU Session
Resource Failed List | O | | 9.3.3.6 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.2.2.3 BEARER CONTEXT SETUP FAILURE + +This message is sent by the gNB-CU-UP to indicate that the setup of the bearer context was unsuccessful. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | O | | 9.3.1.5 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.2.4 BEARER CONTEXT MODIFICATION REQUEST + +This message is sent by the gNB-CU-CP to request the gNB-CU-UP to modify a bearer context. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| Security Information | O | | 9.3.1.10 | | YES | reject | +| UE DL Aggregate
Maximum Bit Rate | O | | Bit Rate
9.3.1.20 | | YES | reject | +| UE DL Maximum
Integrity Protected Data
Rate | O | | Bit Rate
9.3.1.20 | The Bit Rate is a portion of the UE's Maximum Integrity Protected Data Rate, and is enforced by the | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|-------|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | gNB-CU-UP node. | | | +| Bearer Context Status Change | O | | ENUMERATED (Suspend, Resume, ..., ResumeforSDT ) | Indicates the status of the Bearer Context
NOTE: This IE is not applicable to eNB-CP/eNB-UP. | YES | reject | +| New UL TNL Information Required | O | | ENUMERATED (required, ...) | Indicates that new UL TNL information has been requested to be provided. | YES | reject | +| UE Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to UE. | - | - | +| Data Discard Required | O | | ENUMERATED (required, ...) | Indicate to discard the DL user data in case of RAN paging failure. | YES | ignore | +| CHOICE System | O | | | | YES | reject | +| >E-UTRAN | | | | | | | +| >>DRB To Setup List | O | | DRB To Setup Modification List E-UTRAN 9.3.3.7 | | YES | reject | +| >>DRB To Modify List | O | | DRB To Modify List E-UTRAN 9.3.3.8 | | YES | reject | +| >>DRB To Remove List | O | | DRB To Remove List E-UTRAN 9.3.3.9 | | YES | reject | +| >>Subscriber Profile ID for RAT/Frequency priority | O | | 9.3.1.69 | | YES | ignore | +| >>Additional RRM Policy Index | O | | 9.3.1.70 | | YES | ignore | +| >NG-RAN | | | | | | | +| >>PDU Session Resource To Setup List | O | | PDU Session Resource To Setup Modification List 9.3.3.10 | | YES | reject | +| >>PDU Session Resource To Modify List | O | | 9.3.3.11 | | YES | reject | +| >>PDU Session Resource To Remove List | O | | 9.3.3.12 | | YES | reject | +| RAN UE ID | O | | OCTET STRING (SIZE(8)) | | YES | ignore | +| gNB-DU ID | O | | 9.3.1.65 | | YES | ignore | +| Activity Notification Level | O | | 9.3.1.67 | | YES | ignore | +| MDT Polluted | O | | ENUMERATED | Indication on | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Measurement Indicator | | | (IDC, no-IDC, ...) | whether MDT Measurement affect (e.g. IDC) is undertake or not. | | | +| UE Slice Maximum Bit Rate List | O | | 9.3.1.102 | | YES | ignore | +| SCG Activation Status | O | | 9.3.1.105 | | YES | ignore | +| SDT Continue ROHC | O | | ENUMERATED (true, ...) | Indicates ROHC should be continued for SDT DRBs. This IE corresponds to information provided in the sdt-DRB-ContinueROHC contained in the SDT-Config IE as defined in TS 38.331 [10]. | YES | reject | +| Management Based MDT PLMN Modification List | O | | MDT PLMN Modification List
9.3.1.129 | | YES | ignore | +| Inactivity Information Request | O | | ENUMERATED (true, ...) | Indicates to gNB-CU-UP to report the UE Inactivity Information | YES | ignore | +| MT-SDT Information Request | O | | ENUMERATED (true, ...) | Indicates to request the report of MT-SDT Information. | YES | ignore | +| SDT Data Size Threshold | O | | INTEGER (1..192000, ...) | Unit: byte. | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +## 9.2.2.5 BEARER CONTEXT MODIFICATION RESPONSE + +This message is sent by the gNB-CU-UP to confirm the modification of the requested bearer context. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| CHOICE System | O | | | | YES | ignore | +| >E-UTRAN | | | | | | | +| >>DRB Setup List | O | | DRB Setup | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | Modification List E-UTRAN 9.3.3.13 | | | | +| >>DRB Failed List | O | | DRB Failed Modification List E-UTRAN 9.3.3.14 | | YES | ignore | +| >>DRB Modified List | O | | DRB Modified List E-UTRAN 9.3.3.15 | | YES | ignore | +| >>DRB Failed To Modify List | O | | DRB Failed To Modify List E-UTRAN 9.3.3.16 | | YES | ignore | +| >>Retainability Measurements Information | O | | 9.3.1.71 | Provides information on all the removed DRB(s), needed for retainability measurements in the gNB-CU-CP | YES | ignore | +| >NG-RAN | | | | | | | +| >>PDU Session Resource Setup List | O | | PDU Session Resource Setup Modification List 9.3.3.17 | | YES | reject | +| >>PDU Session Resource Failed List | O | | PDU Session Resource Failed Modification List 9.3.3.18 | | YES | reject | +| >>PDU Session Resource Modified List | O | | 9.3.3.19 | | YES | reject | +| >>PDU Session Resource Failed To Modify List | O | | 9.3.3.20 | | YES | reject | +| >>Retainability Measurements Information | O | | 9.3.1.71 | Provides information on all the removed DRB(s), needed for retainability measurements in the gNB-CU-CP | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| UE Inactivity Information | O | | INTEGER (1.. 7200, ...) | Indicates the inactive time. The values are expressed in seconds. | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.2.2.6 BEARER CONTEXT MODIFICATION FAILURE + +This message is sent by the gNB-CU-UP to indicate that the modification of the bearer context was unsuccessful. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.2.7 BEARER CONTEXT MODIFICATION REQUIRED + +This message is sent by the gNB-CU-UP to inform the gNB-CU-CP that a modification of a bearer context is required (e.g., due to local problems at the gNB-CU-UP). + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-------------------------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| CHOICE System | M | | | | YES | reject | +| >E-UTRAN | | | | | | | +| >>DRB To Modify List | O | | DRB Required To Modify List E-UTRAN 9.3.3.21 | | YES | reject | +| >>DRB To Remove List | O | | DRB Required To Remove List 9.3.3.22 | | YES | reject | +| >NG-RAN | | | | | | | +| >>PDU Session Resource Required To Modify List | O | | PDU Session Resource Required To Modify List 9.3.3.23 | | YES | reject | +| >>PDU Session Resource To Remove List | O | | 9.3.3.12 | | YES | reject | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.2.2.8 BEARER CONTEXT MODIFICATION CONFIRM + +This message is sent by the gNB-CU-CP to confirm the modification of the requested bearer context. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| CHOICE System | O | | | | YES | ignore | +| > E-UTRAN | | | | | | | +| >>DRB Modified List | O | | DRB Confirm Modified List E-UTRAN 9.3.3.24 | | YES | ignore | +| > NG-RAN | | | | | | | +| >>PDU Session Resource Modified List | O | | PDU Session Resource Confirm Modified List 9.3.3.25 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +## 9.2.2.9 BEARER CONTEXT RELEASE COMMAND + +This message is sent by the gNB-CU-CP to command the gNB-CU-UP to release an UE-associated logical E1 connection. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +## 9.2.2.10 BEARER CONTEXT RELEASE COMPLETE + +This message is sent by the gNB-CU-UP to confirm the release of the UE-associated logical E1 connection. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | + +| | | | | | | | +|----------------------------------------|---|--|----------|------------------------------------------------------------------------------------------------------------------------|-----|--------| +| ID | | | | | | | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Retainability Measurements Information | O | | 9.3.1.71 | Provides information on all the removed DRB(s) and QoS Flow(s), needed for retainability measurements in the gNB-CU-CP | YES | ignore | + +## 9.2.2.11 BEARER CONTEXT RELEASE REQUEST + +This message is sent by the gNB-CU-UP to request the release of an UE-associated logical E1 connection. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------------------|-----------------------|------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| DRB Status List | | 0.. 1 | | | YES | ignore | +| >DRB Status Item | | 1.. | | | - | - | +| >>DRB ID | M | | 9.3.1.16 | | - | - | +| >>PDCP DL Count | O | | PDCP Count 9.3.1.35 | PDCP count for next DL packet to be assigned. | - | - | +| >>PDCP UL Count | O | | PDCP Count 9.3.1.35 | PDCP count for first unacknowledged UL packet. | - | - | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +## 9.2.2.12 BEARER CONTEXT INACTIVITY NOTIFICATION + +This message is sent by the gNB-CU-UP to provide information about the UE activity to the gNB-CU-CP. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-----------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Activity Information | M | | | | YES | reject | +| >DRB Activity List | | 1 | | Used if the Activity Notification Level IE is set as “DRB” in BEARER CONTEXT SETUP Request message | YES | reject | +| >>DRB Activity Item | | 1 .. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>DRB Activity | M | | ENUMERATED (Active, Not active, ...) | | - | - | +| >PDU Session Resource Activity List | | 1 | | Used if the Activity Notification Level IE is set as “PDU Session” in the BEARER CONTEXT SETUP Request message | YES | reject | +| >>PDU Session Resource Activity Item | | 1 .. | | | - | - | +| >>>PDU Session ID | M | | 9.3.1.21 | | - | - | +| >>>PDU Session Resource Activity | M | | ENUMERATED (Active, Not active, ...) | | - | - | +| >UE Activity | M | | ENUMERATED (Active, Not active, ...) | Used if the Activity Notification Level IE is set as “UE” in the BEARER CONTEXT SETUP Request message | YES | reject | + +| Range bound | Explanation | +|---------------------------|-------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRB for a UE, the maximum value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +## 9.2.2.13 DL DATA NOTIFICATION + +This message is sent by the gNB-CU-UP to provide information about the DL data detection to the gNB-CU-CP. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | + +| | | | | | | | +|----------------------------------------|---|---------------------------------|------------------------|--------------------------------------------------------|-----|--------| +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| Paging Priority Indicator (PPI) | O | | 9.3.1.55 | | YES | ignore | +| PDU Session To Notify List | O | | | | YES | ignore | +| >PDU Session To Notify Item | | 1.. | | | - | - | +| >>PDU Session ID | M | | 9.3.1.21 | | - | - | +| >>QoS Flow List | M | | 9.3.1.12 | | - | - | +| MT-SDT Information | O | | 9.3.1.142 | | YES | ignore | +| SDT Data Size Threshold Crossed | O | | ENUMERATED (true, ...) | Indicates that the SDT Data Size Threshold is crossed. | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +## 9.2.2.14 DATA USAGE REPORT + +This message is sent by the gNB-CU-UP to report data volumes. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| Data Usage Report List | M | | 9.3.1.44 | | YES | ignore | + +## 9.2.2.15 GNB-CU-UP COUNTER CHECK REQUEST + +This message is sent by the gNB-CU-UP to request the verification of the value of the PDCP COUNTs associated with the DRBs established in the gNB-CU-UP. + +Direction: gNB-CU-UP → gNB-CU-CP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| CHOICE System | M | | | | YES | reject | +| >E-UTRAN | | | | | | | +| >>DRBs Subject to Counter Check List | | 1 | | | YES | ignore | +| >>>DRBs Subject | | 1 .. | | | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|---------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| to Counter Check Item | | | | | | | +| >>>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>>PDCP UL Count | M | | PDCP Count 9.3.1.35 | Indicates the value of uplink COUNT associated to this DRB, as specified in TS 38.331 [8] for the gNB/ ng-eNB CP-UP separation, or in TS 36.331 [33] for the eNB CP-UP separation. | - | - | +| >>>>PDCP DL Count | M | | PDCP Count 9.3.1.35 | Indicates the value of downlink COUNT associated to this DRB, as specified in TS 38.331 [8] for the gNB/ ng-eNB CP-UP separation, or in TS 36.331 [33] for the eNB CP-UP separation. | - | - | +| >NG-RAN | | | | | | | +| >>DRBs Subject to Counter Check List | | 1 | | | YES | ignore | +| >>>DRBs Subject to Counter Check Item | | 1 .. | | | - | - | +| >>>>PDU Session ID | M | | 9.3.1.21 | | - | - | +| >>>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>>PDCP UL Count | M | | PDCP Count 9.3.1.35 | Indicates the value of uplink COUNT associated to this DRB, as specified in TS 38.331 [8] for the gNB/ ng-eNB CP-UP separation, or in TS 36.331 [33] for the eNB CP-UP separation. | - | - | +| >>>>PDCP DL Count | M | | PDCP Count 9.3.1.35 | Indicates the value of downlink COUNT associated to this DRB, as specified in TS 38.331 [8] for the gNB/ ng-eNB CP-UP separation, or in TS 36.331 [33] for the eNB CP-UP separation. | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | | separation. | | | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +## 9.2.2.16 UL DATA NOTIFICATION + +This message is sent by the gNB-CU-UP to provide information about the UL data detection to the gNB-CU-CP. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|--------------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| PDU Session To Notify List | | 1 | | | YES | reject | +| >PDU Session To Notify Item | | 1.. | | | - | - | +| >>PDU Session ID | M | | 9.3.1.21 | | - | - | +| >>QoS Flow List | M | | 9.3.1.12 | | - | - | + +## 9.2.2.17 MR-DC DATA USAGE REPORT + +This message is sent by the gNB-CU-UP to report data volumes when the UE is connected to the 5GC. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|---------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| PDU Session Resource Data Usage List | | 1 | | | YES | ignore | +| >PDU Session Resource Data Usage Item | | 1 .. | | | - | - | +| >>PDU Session ID | M | | 9.3.1.21 | | - | - | +| >>MR-DC Usage Information | M | | 9.3.1.63 | | - | - | + +| Range bound | Explanation | +|-------------|-------------| +|-------------|-------------| + +| | | +|--------------------|-------------------------------------------| +| maxnoofPDUsessions | Maximum no. of PDU sessions. Value is 256 | +|--------------------|-------------------------------------------| + +### 9.2.2.18 EARLY FORWARDING SN TRANSFER + +This message is sent by the source gNB-CU-UP to the source gNB-CU-CP to transfer the COUNT value(s) related to early forwarded downlink PDCP SDUs during Conditional Handover or conditional PSCell change or conditional PSCell addition or subsequent CPAC. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------|----------|---------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| DRBs Subject To Early Forwarding List | M | 1 | | | YES | reject | +| >DRBs Subject To Early Forwarding Item | | 1 .. | | | - | - | +| >>DRB ID | M | | 9.3.1.16 | | - | - | +| >>DL COUNT Value | M | | PDCP Count 9.3.1.35 | PDCP-SN and Hyper frame number of the last DL SDU successfully delivered in sequence to the UE, if RLC-AM, and successfully transmitted, if RLC-UM. | - | - | + +### 9.2.2.19 GNB-CU-CP MEASUREMENT RESULTS INFORMATION + +This message is sent to the gNB-CU-UP to provide the measurement result received by the gNB-CU-CP. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|---------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| DRB Measurement Results Information List | | 1 | | | YES | reject | +| >DRB Measurement Results Information Item | | 1 .. | | | EACH | reject | +| >>DRB ID | M | | 9.3.1.16 | | - | - | +| >>UL D1 Result | O | | INTEGER (0 .. | The unit is: 0.1ms | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | 10000,...) | | | | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | + +## 9.2.3 Trace Messages + +### 9.2.3.1 TRACE START + +This message is sent by the gNB-CU-CP to initiate a trace session for a UE. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| Trace Activation | M | | 9.3.1.68 | | YES | ignore | + +### 9.2.3.2 DEACTIVATE TRACE + +This message is sent by the gNB-CU-CP to deactivate a trace session. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|------------------------|-----------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| Trace ID | M | | OCTET STRING (SIZE(8)) | As per Trace ID in Trace Activation IE | YES | ignore | + +### 9.2.3.3 CELL TRAFFIC TRACE + +This message is sent by the gNB-CU-UP to initiate a trace session for a UE. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| gNB-CU-CP UE E1AP ID | M | | 9.3.1.4 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| gNB-CU-UP UE E1AP ID | M | | 9.3.1.5 | | YES | reject | +| Trace ID | M | | OCTET STRING (SIZE(8)) | The Trace ID IE is composed of the following: Trace Reference defined in TS 32.422 [24] (leftmost 6 octets, with PLMN information coded as in 9.2.3.8), and Trace Recording Session Reference defined in TS 32.422 [24] (last 2 octets). | YES | ignore | +| Trace Collection Entity IP Address | M | | Transport Layer Address 9.2.2.1 | For File based Reporting. Defined in TS 32.422 [24]. Should be ignored if URI is present. | YES | ignore | +| Privacy Indicator | O | | ENUMERATED (Immediate MDT, Logged MDT, ...) | | YES | ignore | +| Trace Collection Entity URI | O | | 9.3.2.8 | For Streaming based Reporting. Defined in TS 32.422 [24]. Replaces Trace Collection Entity IP Address if present. | YES | ignore | + +## 9.2.4 IAB Messages + +### 9.2.4.1 IAB UP TNL ADDRESS UPDATE + +This message is sent by the gNB-CU-CP to request the gNB-CU-UP to update the TNL address(es) of the DL F1-U GTP tunnel information. + +NOTE: This message is not applicable for eNB CP-UP separation or ng-eNB CP-UP separation. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------|----------|---------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| DL UP TNL Address To Update List | | 0..1 | | | YES | reject | +| > DL UP TNL Address To Update Item IEs | | 1.. | | | - | - | +| >>Old TNL | M | | 9.3.2.4 | The old Transport | - | - | + +| | | | | | | | +|-------------------|---|--|---------|-------------------------------------------------------------------|---|---| +| Address | | | | Layer Address of IAB-DU for DL F1-U GTP tunnel. | | | +| >>New TNL Address | M | | 9.3.2.4 | The new Transport Layer Address of IAB-DU for DL F1-U GTP tunnel. | - | - | + +| Range bound | Explanation | +|---------------------|-------------------------------------------------------------------------------| +| maxnoofTNLAddresses | Maximum no. of TNL addresses to be updated in one E1AP procedure. Value is 8. | + +#### 9.2.4.2 IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE + +This message is sent by the gNB-CU-UP to the gNB-CU-CP to acknowledge the update of TNL address in DL F1-U GTP tunnel information, or provide the updated TNL address(es) of the UL F1-U GTP tunnel information. + +NOTE: This message is not applicable for eNB CP-UP separation or ng-eNB CP-UP separation. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|---------------------------|-----------------------|------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| UL UP TNL Address to Update List | | 0..1 | | | YES | ignore | +| > UL UP TNL Address Updated Item IEs | | 1.. | | | - | - | +| >>Old TNL Address | M | | 9.3.2.4 | The old Transport Layer Address of CU-UP for UL F1-U GTP tunnel. | - | - | +| >>New TNL Address | M | | 9.3.2.4 | The new Transport Layer Address of CU-UP for UL F1-U GTP tunnel. | - | - | + +| Range bound | Explanation | +|---------------------|-------------------------------------------------------------------------| +| maxnoofTNLAddresses | Maximum no. of TNL addresses updated in one E1AP procedure. Value is 8. | + +#### 9.2.4.3 IAB UP TNL ADDRESS UPDATE FAILURE + +This message is sent by the gNB-CU-UP to indicate IAB UP TNL address Update failure. + +NOTE: This message is not applicable for eNB CP-UP separation or ng-eNB CP-UP separation. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| + +| | | | | | | | +|-------------------------|---|--|----------|--|-----|--------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.53 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time To wait | O | | 9.3.1.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.4.4 IAB PSK NOTIFICATION + +This message is sent by the gNB-CU-CP to the gNB-CU-UP to transfer the security key info to be used for the IKEv2 Pre-shared Secret Key (PSK) authentication to protect the F1-U interface of the IAB-node(s). + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.23 | | YES | reject | +| IAB-donor-CU-UP PSK Info | M | | 9.3.1.99 | | YES | reject | + +### 9.2.5 MBS Messages + +#### 9.2.5.1 MBS Messages for Broadcast + +##### 9.2.5.1.1 BC BEARER CONTEXT SETUP REQUEST + +This message is sent by the gNB-CU-CP to request the gNB-CU-UP to setup MBS session resources for a broadcast MBS session. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| Global MBS Session ID | M | | 9.3.1.108 | | YES | reject | +| BC Bearer Context To Setup | M | | 9.3.3.26 | | YES | reject | +| Associated Session ID | O | | 9.3.3.38 | | YES | ignore | +| MBS Service Area | O | | 9.3.3.39 | | YES | ignore | + +##### 9.2.5.1.2 BC BEARER CONTEXT SETUP RESPONSE + +This message is sent by the gNB-CU-UP to confirm the setup of the requested MBS session resources for a broadcast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | + +| | | | | | | | +|-------------------------------------|---|--|-----------|--|-----|--------| +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| BC Bearer Context To Setup Response | M | | 9.3.3.27 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.5.1.3 BC BEARER CONTEXT SETUP FAILURE + +This message is sent by the gNB-CU-UP to indicate that the setup of the requested broadcast MBS session resources was unsuccessful. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | O | | 9.3.1.107 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.5.1.4 BC BEARER CONTEXT MODIFICATION REQUEST + +This message is sent by the gNB-CU-CP to request the gNB-CU-UP to modify MBS session resources for a broadcast MBS session. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| BC Bearer Context To Modify | M | | 9.3.3.28 | | YES | reject | + +#### 9.2.5.1.5 BC BEARER CONTEXT MODIFICATION RESPONSE + +This message is sent by the gNB-CU-UP to confirm the requested modification of MBS session resources for a broadcast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | + +| | | | | | | | +|--------------------------------------|---|--|----------|--|-----|--------| +| ID | | | | | | | +| BC Bearer Context To Modify Response | M | | 9.3.3.29 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.5.1.6 BC BEARER CONTEXT MODIFICATION FAILURE + +This message is sent by the gNB-CU-UP to indicate that the requested modification of MBS session resources for a broadcast MBS session was unsuccessful. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.5.1.7 BC BEARER CONTEXT MODIFICATION REQUIRED + +This message is sent by the gNB-CU-UP to request the gNB-CU-CP to initiate the modification of MBS session resources for a broadcast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| BC Bearer Context To Modify Required | M | | 9.3.3.30 | | YES | reject | + +#### 9.2.5.1.8 BC BEARER CONTEXT MODIFICATION CONFIRM + +This message is sent by the gNB-CU-CP to confirm the requested modification of the MBS session resources of a broadcast MBS session. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| BC Bearer Context To Modify Confirm | M | | 9.3.3.31 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.5.1.9 BC BEARER CONTEXT RELEASE COMMAND + +This message is sent by the gNB-CU-CP to command the gNB-CU-UP to release MBS session resources for a broadcast MBS session. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +#### 9.2.5.1.10 BC BEARER CONTEXT RELEASE COMPLETE + +This message is sent by the gNB-CU-UP to confirm the release of the MBS session resources for a broadcast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.5.1.11 BC BEARER CONTEXT RELEASE REQUEST + +This message is sent by the gNB-CU-UP to request the release of MBS session resources for a broadcast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +#### 9.2.5.2 MBS Messages for Multicast + +### 9.2.5.2.1 MC BEARER CONTEXT SETUP REQUEST + +This message is sent by the gNB-CU-CP to request the gNB-CU-UP to setup MBS session resources for a multicast MBS session. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| Global MBS Session ID | M | | 9.3.1.108 | | YES | reject | +| MC Bearer Context To Setup | M | | 9.3.3.32 | | YES | reject | + +### 9.2.5.2.2 MC BEARER CONTEXT SETUP RESPONSE + +This message is sent by the gNB-CU-UP to confirm the setup of the requested MBS session resources for a multicast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| MC Bearer Context To Setup Response | M | | 9.3.3.33 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.5.2.3 MC BEARER CONTEXT SETUP FAILURE + +This message is sent by the gNB-CU-UP to indicate that the setup of MBS session resources for a multicast MBS session was unsuccessful. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | O | | 9.3.1.107 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.5.2.4 MC BEARER CONTEXT MODIFICATION REQUEST + +This message is sent by the gNB-CU-CP to request the gNB-CU-UP to modify MBS session resources for a multicast MBS session. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| MC Bearer Context To Modify | M | | 9.3.3.34 | | YES | reject | + +#### 9.2.5.2.5 MC BEARER CONTEXT MODIFICATION RESPONSE + +This message is sent by the gNB-CU-UP to confirm the requested modification of MBS session resources for a multicast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| MC Bearer Context To Modify Response | M | | 9.3.3.35 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.5.2.6 MC BEARER CONTEXT MODIFICATION FAILURE + +This message is sent by the gNB-CU-UP to indicate that the requested modification of MBS session resources for a multicast MBS session was unsuccessful. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| MBS Multicast F1-U Context Descriptor | O | | 9.3.1.125 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.5.2.7 MC BEARER CONTEXT MODIFICATION REQUIRED + +This message is sent by the gNB-CU-UP to request the gNB-CU-CP to initiate the modification MBS session resources for a multicast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| MC Bearer Context To Modify Required | M | | 9.3.3.36 | | YES | reject | + +#### 9.2.5.2.8 MC BEARER CONTEXT MODIFICATION CONFIRM + +This message is sent by the gNB-CU-CP to confirm the requested modification of MBS session resources for a multicast MBS session. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| MC Bearer Context To Modify Confirm | M | | 9.3.3.37 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.5.2.9 MC BEARER CONTEXT RELEASE COMMAND + +This message is sent by the gNB-CU-CP to command the gNB-CU-UP to release MBS session resources for a multicast MBS session. + +Direction: gNB-CU-CP → gNB-CU-UP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +#### 9.2.5.2.10 MC BEARER CONTEXT RELEASE COMPLETE + +This message is sent by the gNB-CU-UP to confirm the release of MBS session resources for a multicast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | + +| | | | | | | | +|-------------------------|---|--|-----------|--|-----|--------| +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.5.2.11 MC BEARER CONTEXT RELEASE REQUEST + +This message is sent by the gNB-CU-UP to request the release of MBS session resources for a multicast MBS session. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.5.2.12 MC BEARER NOTIFICATION + +This message is sent by the gNB-CU-UP to provide information about the DL data arrival or inactivity of the MC Bearer Context to the gNB-CU-CP. + +Direction: gNB-CU-UP → gNB-CU-CP + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU-CP MBS E1AP ID | M | | 9.3.1.106 | | YES | reject | +| gNB-CU-UP MBS E1AP ID | M | | 9.3.1.107 | | YES | reject | +| CHOICE MBS Session Resource Notification | M | | | | YES | ignore | +| >DL Data Arrival | | | | | | | +| >>DL Data Arrival Indication | M | | ENUMERATED (true, ...) | | YES | ignore | +| >>Paging Priority Indicator (PPI) | O | | 9.3.1.55 | | YES | ignore | +| >MC Bearer Context Inactivity | | | | | | | +| >>MC Bearer Context Inactivity Indication | M | | ENUMERATED (true, ...) | | YES | ignore | + +## 9.3 Information Element Definitions + +### 9.3.1 Radio Network Layer Related IEs + +#### 9.3.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 | | | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|----------------------------------------------------------------------------|-----------------------| +| >Procedure Code | M | | INTEGER (0..255) | | +| >Type of Message | M | | CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, ...) | | + +### 9.3.1.2 Cause + +The purpose of the *Cause* IE is to indicate the reason for a particular event for the E1AP protocol. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| CHOICE Cause Group | M | | | | +| > Radio Network Layer | | | | | +| >>Radio Network Layer Cause | M | | ENUMERATED (Unspecified, Unknown or already allocated gNB-CU-CP UE E1AP ID, Unknown or already allocated gNB-CU-UP UE E1AP ID, Unknown or inconsistent pair of UE E1AP ID, Interaction with other procedure, PDCP Count Wrap Around, Not supported QCI value, Not supported 5QI value, Encryption algorithms not supported, Integrity protection algorithms not supported, UP integrity protection not possible, UP confidentiality protection not possible, Multiple PDU Session ID Instances, Unknown PDU Session ID, Multiple QoS Flow ID Instances, Unknown QoS Flow ID, | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| | | | Multiple DRB ID Instances,
Unknown DRB ID,
Invalid QoS combination,
Procedure cancelled,
Normal release,
No radio resources available,
Action desirable for radio reasons,
Resources not available for the slice,
PDCP configuration not supported,
...
UE DL maximum integrity protected data rate reason,
UP integrity protection failure,
Release due to Pre-Emption, RSN not available for the UP,
NPN not supported,
Report Characteristics
Empty,
Existing
Measurement ID,
Measurement
Temporarily not Available
Measurement not Supported For The Object,
SCG activation deactivation failure,
SCG deactivation failure due to data transmission,
Unknown or already allocated gNB-CU-CP MBS E1AP ID,
Unknown or already allocated gNB-CU-UP MBS E1AP ID,
Unknown or inconsistent pair of MBS E1AP ID,
Unknown or inconsistent MRB ID) | | +| >Transport Layer | | | | | +| >>Transport Layer | M | | ENUMERATED | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Cause | | | (Unspecified, Transport Resource Unavailable, ..., Unknown TNL address for IAB) | | +| >Protocol | | | | | +| >>Protocol Cause | M | | ENUMERATED (Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, Abstract Syntax Error (Falsely Constructed Message), Unspecified, ...) | | +| >Misc | | | | | +| >>Miscellaneous Cause | M | | ENUMERATED (Control Processing Overload, Not enough User Plane Processing Resources, Hardware Failure, O&M Intervention, Unspecified, ...) | | + +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 | +|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Unspecified | Sent for radio network layer cause when none of the specified cause values applies. | +| Unknown or already allocated gNB-CU-CP UE E1AP ID | The action failed because the gNB-CU-CP UE E1AP ID is either unknown, or (for a first message received at the gNB-CU) is known and already allocated to an existing context. | +| Unknown or already allocated gNB-CU-UP UE E1AP ID | The action failed because the gNB-CU-UP UE E1AP ID is either unknown, or (for a first message received at the gNB-CU-UP) is known and already allocated to an existing context. | +| Unknown or inconsistent pair of UE E1AP ID | The action failed because both UE E1AP IDs are unknown, or are known but do not define a single UE context. | +| Interaction with other procedure | The action is due to an ongoing interaction with another procedure. | +| PDCP COUNT wrap around | PDCP COUNT approaches the maximum value. | +| Not supported QCI value | The action failed because the requested QCI is not supported. | +| Not supported 5QI value | The action failed because the requested 5QI is not supported. | +| Encryption algorithms not supported | The gNB-CU-UP is unable to support the selected encryption algorithm for the UE. | + +| Radio Network Layer cause | Meaning | +|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Integrity protection algorithms not supported | The gNB-CU-UP is unable to support the selected integrity protection algorithm for the UE. | +| UP integrity protection not possible | The PDU Session (for 5GC) or E-RAB (for EPC) cannot be accepted according to the required user plane integrity protection policy. | +| UP confidentiality protection not possible | The PDU Session cannot be accepted according to the required user plane confidentiality protection policy. | +| Multiple PDU Session ID Instances | The action failed because multiple instances of the same PDU Session had been provided. | +| Unknown PDU Session ID | The action failed because the PDU Session ID is unknown. | +| Multiple QoS Flow ID Instances | The action failed because multiple instances of the same QoS flow had been provided. | +| Unknown QoS Flow ID | The action failed because the QoS Flow ID is unknown. | +| Multiple DRB ID Instances | The action failed because multiple instances of the same DRB had been provided. | +| Unknown DRB ID | The action failed because the DRB ID is unknown. | +| Invalid QoS combination | The action was failed because of invalid QoS combination. | +| Procedure cancelled | The sending node cancelled the procedure due to other urgent actions to be performed. | +| Normal release | The action is due to a normal release of the UE (e.g. because of mobility) and does not indicate an error. | +| No radio resources available | The requested node doesn't have sufficient radio resources available. | +| Action desirable for radio reasons | The reason for requesting the action is radio related. | +| Resources not available for the slice | The requested resources are not available for the slice. | +| PDCP configuration not supported, | The gNB-CU-UP is unable to support the selected PDCP configuration for the UE. | +| UE DL maximum integrity protected data rate reason | The request is not accepted in order to comply with the maximum downlink data rate for integrity protection supported by the UE. | +| UP integrity protection failure | The gNB-CU-UP detects an integrity protection failure in the UL PDU. | +| Release due to Pre-Emption | Release is initiated due to pre-emption. | +| RSN not available for the UP | The redundant user plane resources indicated by RSN are not available. | +| NPN not supported | The action failed because the indicated SNPN is not supported in the node. | +| Report Characteristics Empty | The action failed because there is no measurement object in the report characteristics. | +| Existing Measurement ID | The action failed because the measurement ID is already used. | +| Measurement Temporarily not Available | The gNB-CU-UP can temporarily not provide the requested measurement object. | +| Measurement not Supported For The Object | At least one of the concerned object(s) does not support the requested measurement. | +| SCG activation deactivation failure | The action failed due to rejection of the SCG activation deactivation request. | +| SCG deactivation failure due to data transmission | The SCG deactivation failed due to ongoing or arriving data transmission. | +| Unknown or already allocated gNB-CU-CP MBS E1AP ID | The action failed because the gNB-CU-CP MBS E1AP ID is either unknown, or (for a first message received at the gNB-CU-CP) is known and already allocated to an existing context. | +| Unknown or already allocated gNB-CU-UP MBS E1AP ID | The action failed because the gNB-CU-UP MBS E1AP ID is either unknown, or (for a first message received at the gNB-CU-UP) is known and already allocated to an existing context. | +| Unknown or inconsistent pair of MBS E1AP ID | The action failed because both MBS E1AP IDs are unknown, or are known but do not define a single MBS context. | + +| Radio Network Layer cause | Meaning | +|--------------------------------|------------------------------------------------------------------| +| Unknown or inconsistent MRB ID | The action failed because the MRB ID is unknown or inconsistent. | + +| Transport Layer cause | Meaning | +|--------------------------------|----------------------------------------------------------------------------------------------------------| +| Unspecified | Sent when none of the above cause values applies but still the cause is Transport Network Layer related. | +| Transport Resource Unavailable | The required transport resources are not available. | +| Unknown TNL address for IAB | The action failed because the TNL address is unknown.
This cause value is applicable for IAB only. | + +| Protocol cause | Meaning | +|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Transfer Syntax Error | The received message included a transfer syntax error. | +| 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". | +| 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. | +| Abstract Syntax Error (Falsely Constructed Message) | The received message contained IEs or IE groups in wrong order or with too many occurrences. | +| Unspecified | Sent when none of the above cause values applies but still the cause is Protocol related. | + +| Miscellaneous cause | Meaning | +|------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Control Processing Overload | Control processing overload. | +| Not Enough User Plane Processing Resources Available | No enough resources are available related to user plane processing. | +| Hardware Failure | Action related to hardware failure. | +| O&M Intervention | The action is due to O&M intervention. | +| Unspecified Failure | Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer, NAS or Protocol. | + +### 9.3.1.3 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by the gNB-CU-UP or the gNB-CU-CP 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. The conditions for inclusion of the *Transaction ID* IE are described in clause 10. + +For further details on how to use the *Criticality Diagnostics* IE, (see clause 10). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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 | | ENUMERATED(initiating message, | The Triggering Message is used only if the Criticality Diagnostics | + +| | | | | | +|----------------------------------------------------|---|----------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| | | | successful outcome, unsuccessful outcome) | is part of Error Indication procedure. | +| Procedure Criticality | O | | ENUMERATED(reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). | +| Transaction ID | O | | 9.3.1.53 | | +| Information Element Criticality Diagnostics | | 0 .. | | | +| >IE Criticality | M | | ENUMERATED(reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' is not applicable. | +| >IE ID | M | | INTEGER (0..65535) | The IE ID of the not understood or missing IE. | +| >Type of Error | M | | ENUMERATED(not understood, missing, ...) | | + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------------------------------------------| +| maxnoofErrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxnoofErrors is 256. | + +### 9.3.1.4 gNB-CU-CP UE E1AP ID + +The gNB-CU-CP UE E1AP ID uniquely identifies the UE association over the E1 interface within the gNB-CU-CP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-CU-CP UE E1AP ID | M | | INTEGER (0 .. 2 32 -1) | | + +### 9.3.1.5 gNB-CU-UP UE E1AP ID + +The gNB-CU-UP UE E1AP ID uniquely identifies the UE association over the E1 interface within the gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-CU-UP UE E1AP ID | M | | INTEGER (0 .. 2 32 -1) | | + +### 9.3.1.6 Time To wait + +This IE defines the minimum allowed waiting times. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------------------|-----------------------| +| Time To wait | M | | ENUMERATED(1s, 2s, 5s, 10s, 20s, 60s) | | + +### 9.3.1.7 PLMN Identity + +This information element indicates the PLMN Identity. + +| 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).
| + +### 9.3.1.8 Slice Support List + +This IE indicates the list of supported slices. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|---------------------------------------|-----------------------|-----------------------|-------------|----------------------| +| Slice Support Item IEs | | 1.. <maxno ofSliceItems> | | | - | - | +| >S-NSSAI | M | | 9.3.1.9 | | - | | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------| +| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. | + +### 9.3.1.9 S-NSSAI + +This IE indicates the S-NSSAI as defined in TS 23.003 [23]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|-----------------------| +| SST | M | | OCTET STRING (SIZE(1)) | | +| SD | O | | OCTET STRING (SIZE(3)) | | + +### 9.3.1.10 Security Information + +This IE provides the information for configuring UP ciphering and/or integrity protection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|-----------------------|-----------------------| +| Security Algorithm | M | | 9.3.1.31 | | +| User Plane Security Keys | M | | 9.3.1.32 | | + +### 9.3.1.11 Cell Group Information + +This IE provides information about the cell group(s) (i.e., radio leg(s)) that are part of the DRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Cell Group List | | 1 | | | - | - | +| > Cell Group Item | | 1.. | | | - | - | +| >>Cell Group ID | M | | INTEGER (0..3, ...) | This IE corresponds to information provided in the CellGroupId IE as defined in TS 38.331 [10] (0=MCG, 1=SCG). In this version of the specification, values "2" and "3" are not used. For E-UTRA Cell Groups, the same encoding is used as for NR Cell Groups. NOTE: There is no corresponding IE defined in TS 36.331 [21]. | - | - | +| >>UL Configuration | O | | 9.3.1.33 | Indicates whether the Cell Group is used for UL traffic. | - | - | +| >>DL TX Stop | O | | ENUMERATED (stop, resume, ...) | | - | - | +| >>RAT Type | O | | ENUMERATED (E-UTRA, NR, ...) | Indicates the RAT. | - | - | +| >>Number of tunnels | O | | INTEGER (1..4, ...) | Indicates the tunnel number of PDCP duplication for this cell group. | YES | ignore | + +| Range bound | Explanation | +|-------------------|---------------------------------------------------| +| maxnoofCellGroups | Maximum no. of cell groups for a DRB. Value is 4. | + +### 9.3.1.12 QoS Flow List + +This IE includes a list of QoS Flows that are identified by the QoS Flow Identifier. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|-----------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| QoS Flow List | | 1 | | | - | - | +| > QoS Flow Item | | 1.. | | | - | - | +| >>QoS Flow Identifier | M | | 9.3.1.24 | | - | - | +| >>QoS Flow Mapping Indication | O | | 9.3.1.60 | Indicates that only the uplink or downlink QoS flow is mapped to the DRB | YES | ignore | +| >>Data Forwarding Source IP Address | O | | Transport Layer Address 9.3.2.4 | Identifies the TNL address used by the source node for data forwarding. | YES | ignore | +| >>ECN Marking or Congestion Information Reporting Status | O | | ENUMERATED (active, not active, ...) | Indicates whether ECN marking at NG-RAN or ECN marking at UPF or congestion information reporting is active or not active. | YES | ignore | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows in a PDU Session. Value is 64. | + +### 9.3.1.13 UP Parameters + +This IE provides information related to a DRB configured in the gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|---------------------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| UP Parameters List | | 1 | | | - | - | +| > UP Parameters Item | | 1.. | | | - | - | +| >>UP Transport Layer Information | M | | 9.3.2.1 | | - | - | +| >>Cell Group ID | M | | INTEGER (0..3, ...) | This IE corresponds to information provided in the CellGroupId IE in TS 38.331 [10] (0=MCG, 1=SCG). In this version of the specification, values "2" and "3" are not used. | - | - | +| >>QoS Mapping Information | O | | 9.3.1.81 | This IE is only used for IAB. | YES | reject | +| >>Indirect Path Indication | O | | ENUMERATED (true, ...) | This IE is only used for L2 U2N Remote UE | YES | ignore | + +| Range bound | Explanation | +|---------------------|---------------------------------------------------------------------------| +| maxnoofUPParameters | Maximum no. of UP parameters (e.g., GTP tunnels) for a DRB.
Value is 8 | + +### 9.3.1.14 NR CGI + +The NR Cell Global Identifier (NR CGI) is used to globally identify a cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-----------------------|-----------------------| +| PLMN Identity | M | | 9.3.1.7 | | +| NR Cell Identity | M | | BIT STRING (SIZE(36)) | | + +### 9.3.1.15 gNB-CU-UP ID + +The gNB-CU-UP ID uniquely identifies the gNB-CU-UP at least within a gNB-CU-CP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------------|-----------------------| +| gNB-CU-UP ID | M | | INTEGER (0 .. 2 36 -1) | | + +### 9.3.1.16 DRB ID + +This IE uniquely identifies a DRB for a UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DRB ID | M | | INTEGER (1.. 32, ...) | This IE corresponds to information provided in the DRB-Identity IE as defined in TS 38.331 [10] for the gNB/ ng-eNB CP-UP separation, or in TS 36.331 [33] for the eNB CP-UP separation. | + +### 9.3.1.16a MRB ID + +This IE identifies an MRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|-----------------------| +| MRB ID | M | | INTEGER (1.. 512, ...) | | + +### 9.3.1.17 E-UTRAN QoS + +This IE defines the QoS to be applied to a DRB for EN-DC case. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------|-------------|----------------------| +| QCI | M | | INTEGER (0..255) | QoS Class Identifier defined in TS 23.401 [11]. Logical range and coding specified in TS 23.203 [12]. | – | – | +| E-UTRAN Allocation and Retention Priority | M | | 9.3.1.18 | E-UTRAN Allocation and Retention Priority | – | – | +| GBR QoS Information | O | | 9.3.1.19 | This IE applies to GBR bearers only and is ignored otherwise. | – | – | + +### 9.3.1.18 E-UTRAN Allocation and Retention Priority + +This IE specifies the relative importance compared to other E-RABs for allocation and retention of the E-UTRAN Radio Access Bearer. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|--------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Priority Level | M | | INTEGER (0..15) | Desc.: This IE should be understood as "priority of allocation and retention" (see TS 23.401 [11]).
Usage:
Value 15 means "no priority". Values between 1 and 14 are ordered in decreasing order of priority, i.e. 1 is the highest and 14 the lowest.
Value 0 shall be treated as a logical error if received. | +| Pre-emption Capability | M | | ENUMERATED(shall not trigger pre-emption, may trigger pre-emption) | Desc.: This IE indicates the pre-emption capability of the request on other E-RABs
Usage:
The E-RAB shall not pre-empt other E-RABs or, the E-RAB may pre-empt other E-RABs
The Pre-emption Capability indicator applies to the allocation of resources for an E-RAB and as such it provides the trigger to the pre-emption procedures/processes of the eNB. | +| Pre-emption Vulnerability | M | | ENUMERATED(not pre-emptable, pre-emptable) | Desc.: This IE indicates the vulnerability of the E-RAB to pre-emption of other E-RABs.
Usage:
The E-RAB shall not be pre-empted by other E-RABs or the E-RAB may be pre-empted by other RABs.
Pre-emption Vulnerability | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | indicator applies for the entire duration of the E-RAB, unless modified, and as such indicates whether the E-RAB is a target of the pre-emption procedures/processes of the eNB. | + +### 9.3.1.19 GBR QoS Information + +This IE indicates the maximum and guaranteed bit rates of a GBR E-RAB for downlink and uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| E-RAB Maximum Bit Rate Downlink | M | | Bit Rate 9.3.1.20 | Maximum Bit Rate in DL (i.e. from EPC to E-UTRAN) for the bearer. Details in TS 23.401 [11]. | – | – | +| E-RAB Maximum Bit Rate Uplink | M | | Bit Rate 9.3.1.20 | Maximum Bit Rate in UL (i.e. from E-UTRAN to EPC) for the bearer. Details in TS 23.401 [11]. | – | – | +| E-RAB Guaranteed Bit Rate Downlink | M | | Bit Rate 9.3.1.20 | Guaranteed Bit Rate (provided that there is data to deliver) in DL (i.e. from EPC to E-UTRAN) for the bearer. Details in TS 23.401 [11]. | – | – | +| E-RAB Guaranteed Bit Rate Uplink | M | | Bit Rate 9.3.1.20 | Guaranteed Bit Rate (provided that there is data to deliver) in UL (i.e. from E-UTRAN to EPC) for the bearer. Details in TS 23.401 [11]. | – | – | + +### 9.3.1.20 Bit Rate + +This IE indicates the number of bits delivered by NG-RAN/E-UTRAN in UL or to NG-RAN/E-UTRAN in DL within a period of time, divided by the duration of the period. It is used, for example, to indicate the maximum or guaranteed bit rate for a GBR QoS flow or a GBR bearer, or an aggregated maximum bit rate. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| Bit Rate | M | | INTEGER (0.. | The unit is: bit/s | + +| | | | | | +|--|--|--|----------------------------|--| +| | | | 4,000,000,000,000,
...) | | +|--|--|--|----------------------------|--| + +### 9.3.1.21 PDU Session ID + +This IE identifies a PDU Session for a UE. The definition and use of the PDU Session ID is specified in TS 23.501 [20]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|-----------------------| +| PDU Session ID | M | | INTEGER (0 ..255) | | + +### 9.3.1.22 PDU Session Type + +This IE indicates the PDU Session Type as specified in TS 23.501 [20]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-----------------------------------------------------------------------|-----------------------| +| PDU Session Type | M | | ENUMERATED
(IPv4, IPv6, IPv4v6,
ethernet,
unstructured, ...) | | + +### 9.3.1.23 Security Indication + +This IE contains the user plane integrity protection indication and confidentiality protection indication which indicates the requirements on UP integrity protection and ciphering for corresponding PDU Session Resources, respectively. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|------------------------------------------------------------|-------|---------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Integrity Protection Indication | M | | ENUMERATED
(required, preferred,
not needed, ...) | Indicates whether UP integrity protection shall apply, should apply or shall not apply for the concerned PDU Session Resource for the gNB/ng-eNB CP-UP separation, or for the concerned E-RAB for the eNB CP-UP separation. | +| Confidentiality Protection Indication | M | | ENUMERATED
(required, preferred,
not needed, ...) | Indicates whether UP ciphering shall apply, should apply or shall not apply for the concerned PDU Session Resource.
NOTE: This IE is not applicable to eNB CP-UP separation. | +| Maximum Integrity Protected Data Rate | C-
ifIntegrityP
rotectionre
quiredorpr
eferred | | 9.3.1.57 | If present, this is the value received from the CN for the overall UE capability. This IE is ignored when enforcing the maximum IP data rate.
NOTE: This IE is not applicable to eNB CP-UP separation. | + +| Condition | Explanation | +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| ifIntegrityProtectionrequiredorpreferred | This IE shall be present if the Integrity Protection Indication IE within the Security Indication IE is set to “required” or “preferred”. | + +### 9.3.1.24 QoS Flow Identifier + +This IE identifies a QoS Flow within a PDU Session. Definition and use of the QoS Flow Identifier is specified in TS 23.501 [20]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|-----------------------| +| QoS Flow Identifier | M | | INTEGER (0 ..63) | | + +### 9.3.1.25 QoS Flow QoS Parameters List + +This IE contains a list of QoS Flows including the QoS Flow parameters. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|----------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| QoS Flow List | | 1 | | | - | - | +| > QoS Flow Item | | 1.. | | | - | - | +| >>QoS Flow Identifier | M | | 9.3.1.24 | | - | - | +| >>QoS Flow Level | M | | 9.3.1.26 | | - | - | +| QoS Parameters | | | | | | | +| >>QoS Flow Mapping Indication | O | | 9.3.1.60 | Indicates that only the uplink or downlink QoS flow is mapped to the DRB. For MBS, this IE is associated with an MRB and always set to "dl". | - | - | +| >>Redundant QoS Flow Indicator | O | | 9.3.1.74 | This IE indicates that this QoS flow is requested for the redundant transmission. | YES | ignore | +| >>TSC Traffic Characteristics | O | | 9.3.1.75 | Traffic pattern information associated with the QFI. Details in TS 23.501 [20]. | YES | ignore | +| >>ECN Marking or Congestion Information Reporting Request | O | | 9.3.1.145 | | YES | ignore | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows in a PDU Session. Value is 64. | + +### 9.3.1.26 QoS Flow Level QoS Parameters + +This IE defines the QoS parameters to be applied to a QoS Flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE QoS Characteristics | M | | | | - | | +| >Non-dynamic 5QI | | | | | | | +| >>Non Dynamic 5QI Descriptor | M | | 9.3.1.27 | | - | | +| >Dynamic 5QI | | | | | | | +| >>Dynamic 5QI Descriptor | M | | 9.3.1.28 | | - | | +| NG-RAN Allocation and Retention Priority | M | | 9.3.1.29 | | - | | +| GBR QoS Flow Information | O | | 9.3.1.30 | This IE shall be present for GBR QoS Flows and is ignored otherwise. | - | | +| Reflective QoS Attribute | O | | ENUMERATED (subject to, ...) | Details in TS 23.501 [20]. This IE applies to Non-GBR flows only and is ignored otherwise. | - | | +| Additional QoS Flow Information | O | | ENUMERATED (more likely, ...) | This IE indicates that traffic for this QoS flow is likely to appear more often than traffic for other flows established for the PDU Session. | - | | +| Paging Priority Index | O | | INTEGER (1.. 8, ...) | This IE is not used in this version of the specification. | - | | +| RDI | O | | ENUMERATED (enabled, ...) | Indicates whether Reflective QoS flow to DRB mapping should be applied. | - | | +| QoS Monitoring Request | O | | ENUMERATED (UL, DL, Both, ...) | Indicates to measure UL, or DL, or both UL/DL delays for the associated QoS flow. | YES | ignore | +| MCG Offered GBR QoS Flow Information | O | | GBR QoS Flow Information 9.3.1.30 | This IE contains M-Node offered GBR QoS Flow Information. | YES | ignore | +| QoS Monitoring Reporting Frequency | O | | INTEGER (1..1800, ...) | Indicates the Reporting Frequency for RAN part delay for QoS monitoring. Units: second | YES | ignore | +| QoS Monitoring Disabled | O | | ENUMERATED (true, ...) | Indicates to stop the QoS monitoring. | YES | ignore | +| Data Forwarding Source IP Address | O | | Transport Layer Address | Identifies the TNL address used by | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------|-----------------------|--------------------------------------|-------------|----------------------| +| | | | 9.3.2.4 | the source node for data forwarding. | | | +| PDU Set QoS Parameters | O | | 9.3.1.143 | | YES | ignore | + +### 9.3.1.27 Non Dynamic 5QI Descriptor + +This IE indicates the QoS Characteristics for a standardized or pre-configured 5QI for downlink and uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| 5QI | M | | INTEGER (0..255, ...) | This IE contains the standardized or pre-configured 5QI as specified in TS 23.501 [20]. | - | - | +| Priority Level | O | | 9.3.1.51 | For details see TS 23.501 [20]. When included overrides standardized or pre-configured value. | - | - | +| Averaging Window | O | | 9.3.1.49 | This IE applies to GBR QoS Flows only. For details see TS 23.501 [20]. When included overrides standardized or pre-configured value. | - | - | +| Maximum Data Burst Volume | O | | 9.3.1.50 | For details see TS 23.501 [20]. When included overrides standardized or pre-configured value. | - | - | +| CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget
9.3.1.79 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | +| CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget
9.3.1.79 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | + +### 9.3.1.28 Dynamic 5QI Descriptor + +This IE indicates the QoS Characteristics for a Non-standardised or not pre-configured 5QI for downlink and uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|-------------|-------|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Priority Level | M | | 9.3.1.51 | For details see TS 23.501 [20]. | - | - | +| Packet Delay Budget | M | | 9.3.1.47 | For details see TS 23.501 [20]. This IE is ignored if the Extended Packet Delay Budget IE is present. | - | - | +| Packet Error Rate | M | | 9.3.1.48 | For details see TS 23.501 [20]. | - | - | +| 5QI | O | | INTEGER (0..255,...) | This IE contains the dynamically assigned 5QI as specified in TS 23.501 [20]. | - | - | +| Delay Critical | C-ifGBRflow | | ENUMERATED (delay critical, non-delay critical) | For details see TS 23.501 [20]. | - | - | +| Averaging Window | C-ifGBRflow | | 9.3.1.49 | For details see TS 23.501 [20]. | - | - | +| Maximum Data Burst Volume | O | | 9.3.1.50 | For details see TS 23.501 [20]. This IE shall be included if the Delay Critical IE is set to "delay critical" and is ignored otherwise. | - | - | +| Extended Packet Delay Budget | O | | Extended Packet Delay Budget
9.3.1.79 | Packet Delay Budget is specified in TS 23.501 [9] | YES | ignore | +| CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget
9.3.1.79 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | +| CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget
9.3.1.79 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows and is ignored | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | | otherwise. | | | + +| Condition | Explanation | +|-----------|-------------------------------------------------------------------------------------------------------------------------------| +| ifGBRflow | This IE shall be present if the GBR QoS Flow Information IE is present in the QoS Flow Level QoS Parameters IE. | + +### 9.3.1.29 NG-RAN Allocation and Retention Priority + +This IE specifies the relative importance of a QoS flow compared to other QoS flows for allocation and retention of NG-RAN resources. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Priority Level | M | | INTEGER (0..15) |

Desc.: This IE defines the relative importance of a resource request (see TS 23.501 [20]).

Usage: Values are ordered in decreasing order of priority, i.e., with 1 as the highest priority and 15 as the lowest priority. Further usage is defined in TS 23.501 [20].

| +| Pre-emption Capability | M | | ENUMERATED (shall not trigger pre-emption, may trigger pre-emption) |

Desc.: This IE indicates the pre-emption capability of the request on other QoS flows.

Usage: The QoS flow shall not pre-empt other QoS flows or, the QoS flow may pre-empt other QoS flows.

Specified in TS 23.501 [20]

NOTE: The Pre-emption Capability indicator applies to the allocation of resources for a QoS flow and as such it provides the trigger to the pre-emption procedures/processes of the NG-RAN node.

| +| Pre-emption Vulnerability | M | | ENUMERATED (not pre-emptable, pre-emptable) |

Desc.: This IE indicates the vulnerability of the QoS flow to pre-emption of other QoS flows.

Usage: The QoS flow shall not be pre-empted by other QoS flows or the QoS flow may be pre-empted by other QoS flows.

Specified in TS 23.501 [20]

NOTE: The Pre-emption Vulnerability indicator applies for the entire duration of the QoS flow, unless modified and as such indicates whether the QoS flow is a target of the pre-emption procedures/processes of the NG-RAN node.

| + +### 9.3.1.30 GBR QoS Flow Information + +This IE indicates QoS parameters for a GBR QoS flow for downlink and uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|----------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Maximum Flow Bit Rate Downlink | M | | Bit Rate 9.3.1.20 | Maximum Bit Rate in DL. Details in TS 23.501 [20]. | - | | +| Maximum Flow Bit Rate Uplink | M | | Bit Rate 9.3.1.20 | Maximum Bit Rate in UL. Details in TS 23.501 [20]. | - | | +| Guaranteed Flow Bit Rate Downlink | M | | Bit Rate 9.3.1.20 | Guaranteed Bit Rate (provided there is data to deliver) in DL. Details in TS 23.501 [20]. | - | | +| Guaranteed Flow Bit Rate Uplink | M | | Bit Rate 9.3.1.20 | Guaranteed Bit Rate (provided there is data to deliver). Details in TS 23.501 [20]. | - | | +| Maximum Packet Loss Rate Downlink | O | | Packet Loass Rate 9.3.1.46 | Indicates the maximum rate for lost packets that can be tolerated in the downlink direction. Details in TS 23.501 [20]. | - | | +| Maximum Packet Loss Rate Uplink | O | | Packet Loss Rate 9.3.1.46 | Indicates the maximum rate for lost packets that can be tolerated in the uplink direction. Details in TS 23.501 [20]. | - | | +| Alternative QoS Parameters Set List | O | | 9.3.1.93 | Indicates alternative sets of QoS Parameters for the QoS flow. | YES | | + +### 9.3.1.31 Security Algorithm + +This IE defines the type of ciphering algorithm and/or integrity protection used for the DRBs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ciphering Algorithm | M | | ENUMERATED (NEA0, 128-NEA1, 128-NEA2, 128-NEA3) | As defined in TS 33.501 [13] for NG-RAN or TS 33.401 [32] for E-UTRAN where the corresponding enumerated value is EEA0, 128-EEA1, 128-EEA2, 128-EEA3. | +| Integrity Protection Algorithm | O | | ENUMERATED (NIA0, 128-NIA1, 128-NIA2, 128-NIA3) | As defined in TS 33.501 [13] for NG-RAN or TS 33.401 [32] for E-UTRAN where the corresponding enumerated value is EIA0, 128-EIA1, 128-EIA2, 128-EIA3. | + +### 9.3.1.32 User Plane Security Keys + +This IE contains the ciphering and/or integrity protection keys generated by the gNB-CU-CP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------| +| Encryption Key | M | | OCTET STRING | As defined in TS 33.501 [13] for gNB or ng-eNB CP-UP separation, or in TS 33.401 [32] for eNB CP-UP separation. | +| Integrity Protection Key | O | | OCTET STRING | As defined in TS 33.501 [13] for NG-RAN or TS 33.401 [32] for eNB CP-UP separation.. | + +### 9.3.1.33 UL Configuration + +This IE includes the UL configuration for the DRB and the corresponding Cell Groups. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UL Configuration | M | | ENUMERATED (no-data, shared, only, ..) | Indicates the UL configuration for a Cell Group that is part of a DRB. "no data" means that the Cell Group is not used for UL data. "shared" means that the Cell Group is used for UL data together with at least another Cell Group. "only" means that only this Cell Group is used for UL data. | + +### 9.3.1.34 gNB-CU-UP Cell Group Related Configuration + +This IE provides information related to a cell group that the gNB-CU-UP is allowed to change. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|---------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| UP Parameters List | | 1 | | | - | - | +| >UP Parameters Item | | 1.. | | | - | - | +| >>Cell Group ID | M | | INTEGER (0..3, ...) | This IE corresponds to information provided in the CellGroupId IE as defined in TS 38.331 [10] (0=MCG, 1=SCG). Used to identify the Cell Group to modify. In this version of the specification, | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-------|-----------------------|----------------------------------------------------------|-------------|----------------------| +| | | | | values "2" and "3" are not used. | | | +| >>UP Transport Layer Information | M | | 9.3.2.1 | | - | - | +| >>UL Configuration | O | | 9.3.1.33 | Indicates whether the Cell Group is used for UL traffic. | - | - | + +| Range bound | Explanation | +|---------------------|-------------------------------------------------------------------------| +| maxnoofUPParameters | Maximum no. of UP parameters (e.g., GTP tunnels) for a DRB. Value is 8. | + +### 9.3.1.35 PDCP Count + +This IE include the PDCP Count information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------------------------------------|-------------------------------------------------------------------| +| >PDCP SN | M | | INTEGER (0 .. $2^{\text{PDCP\_SN\_Size\_1}} - 1$ ) | The PDCP SN Size is provided in the PDCP Configuration IE. | +| >HFN | M | | INTEGER (0 .. $2^{32-\text{PDCP\_SN\_Size\_1}} - 1$ ) | The PDCP SN Size is provided in the PDCP Configuration IE. | + +### 9.3.1.35a MBS PDCP COUNT + +This IE includes the MBS PDCP Count information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MBS PDCP COUNT | M | | BIT STRING (32) | Corresponds to information provided in the initialRX-DELIV contained in the PDCP-Config IE and to be taken into account to configure the UE, as specified in TS 38.331 [10]. | + +### 9.3.1.36 NR CGI Support List + +This IE indicates the list of supported NR CGIs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------------------|-----------------------|-----------------------| +| NR CGI Support Item IEs | | 1.. | | | +| >NR CGI | M | | 9.3.1.14 | | + +| Range bound | Explanation | +|--------------|------------------------------------------------------------------------------| +| maxnoofNRCGI | Maximum no. of supported NR CGIs. Value is 512. This range may be redefined. | + +### 9.3.1.37 QoS Parameters Support List + +This IE indicates the list of supported QoS parameters. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|---------------------------------|-----------------------|-----------------------| +| E-UTRAN QoS Support List | O | | | | +| >E-UTRAN QoS Support Item | | 1.. | | | +| >>E-UTRAN QoS | M | | 9.3.1.17 | | +| NG-RAN QoS Support List | O | | | | +| >NG-RAN QoS Support Item | | 1.. | | | +| >>Non Dynamic 5QI Descriptor | M | | 9.3.1.27 | | + +| Range bound | Explanation | +|----------------------------|---------------------------------------------------------------------------------------------| +| maxnoofEUTRANQOSParameters | Maximum no. of supported E-UTRAN QoS parameters. Value is 256. This range may be redefined. | +| maxnoofNGRANQOSParameters | Maximum no. of supported NG-RAN QoS parameters. Value is 256. This range may be redefined. | + +### 9.3.1.38 PDCP Configuration + +This IE carries the PDCP configuration. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| PDCP SN UL Size | M | | PDCP SN Size 9.3.1.61 | Indicates the PDCP SN UL size in bits. Corresponds to information provided in the pdcp-SN-SizeUL contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. Is ignored if received through DRB To Modify | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | List IE in the BEARER CONTEXT MODIFICATION REQUEST message. | | | +| PDCP SN DL Size | M | | PDCP SN Size 9.3.1.61 | Indicates the PDCP SN DL size in bits. Corresponds to information provided in the pdcp-SN-SizeDL contained in the PDCP-Config IE in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. Is ignored if received through DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message. | - | - | +| RLC mode | M | | ENUMERATED (RLC-TM, RLC-AM, RLC-UM-Bidirectional, RLC-UM-Unidirectional-UL, RLC-UM-Unidirectional-DL, ...) | Indicates the RLC mode for the DRB. For more information see PDCP-Config IE in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. Is ignored if received through DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message. | - | - | +| ROHC Parameters | O | | 9.3.1.40 | | - | - | +| T-Reordering Timer | O | | 9.3.1.41 | | - | - | +| Discard Timer | O | | 9.3.1.42 | This IE is ignored if the Discard Timer Extended IE is present. | - | - | +| UL Data Split Threshold | O | | 9.3.1.43 | | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| PDCP Duplication | O | | ENUMERATED (True, ...) | Indicates whether PDCP duplication is to be configured for the DRB. This IE is ignored when the “ Additional PDCP duplication Information ” IE is present. | - | - | +| PDCP Re-establishment | O | | ENUMERATED (true,...) | Indicates PDCP entity re-establishment to be triggered as defined in TS 38.323 [17] for gNB or ng-eNB CP-UP separation, or in TS 36.323 [34] for eNB CP-UP separation. | - | - | +| PDCP Data Recovery | O | | ENUMERATED (true,...) | Indicates PDCP data recovery to be triggered as defined in TS 38.323 [17] for gNB or ng-eNB CP-UP separation, or in TS 36.323 [34] for eNB CP-UP separation. | - | - | +| Duplication Activation | O | | ENUMERATED ( Active, Inactive, ...) | Information on the initial state of DL PDCP duplication | - | - | +| Out Of Order Delivery | O | | ENUMERATED (true,...) | Indicates whether or not outOfOrderDelivery specified in TS 38.323 [17] is configured. Out of order delivery is configured only when the radio bearer is established for gNB or ng-eNB CP-UP separation, or indicates whether or not rlc-OutOfOrderDelivery in TS 36.323 [34] is configured for eNB CP-UP separation. | - | - | +| PDCP Status Report Indication | O | | ENUMERATED (downlink, uplink, both, ...) | For AM DRB, “downlink” indicates that the | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|-------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | PDCP entity is configured to send PDCP status report(s) to the UE, and “uplink” indicates that the UE is configured to send PDCP status report(s), as specified in TS 38.323 [17] for gNB or ng-eNB CP-UP separation, or in TS 36.323 [34] for eNB CP-UP separation. “both” indicates that both “downlink” and “uplink” should be applied. | | | +| Additional PDCP duplication Information | O | | ENUMERATED (three, four, ...) | Indicates the number of PDCP duplication configured when it is more than 2 for the DRB | YES | ignore | +| EHC Parameters | O | | 9.3.1.90 | | YES | ignore | +| UDC Parameters | O | | 9.3.1.104 | | YES | ignore | +| Discard Timer Extended | O | | 9.3.1.128 | | YES | reject | + +### 9.3.1.39 SDAP Configuration + +This IE carries the SDAP configuration. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Default DRB | M | | ENUMERATED (True, False, ...) | Indicates whether or not this is the default DRB for the PDU Session Resource. Corresponds to information provided in the defaultDRB contained in the SDAP-Config IE as defined in TS 38.331 [10]. | +| SDAP Header UL | M | | ENUMERATED (Present, Absent, ...) | Indicates whether or not a SDAP header is present for UL data on this DRB. Corresponds to information provided in the sdap-HeaderUL contained in the SDAP-Config IE as defined in TS 38.331 [10]. | +| SDAP Header DL | M | | ENUMERATED (Present, Absent, ...) | Indicates whether or not a SDAP header is present for DL data on this DRB. Corresponds to information provided in the sdap-HeaderDL contained in the | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------------------------------------| +| | | | | SDAP-Config IE as defined in TS 38.331 [10]. | + +### 9.3.1.40 ROHC Parameters + +This IE carries the ROHC parameters for header compressions. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Choice ROHC Parameters | M | | | Corresponds to information provided in the rohc contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | +| >ROHC | | | | | +| >>max CID | M | | INTEGER (0..16383) | Corresponds to information provided in the maxCID contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | +| >>ROHC Profiles | M | | INTEGER (0..511) | Bitmap with supported UE profiles, bit 0 (LSB 0) = profile0x0001, bit 1 = profile0x0002, bit 2 = profile0x0003, bit 3 = profile0x0004, bit 4 = profile0x0006, bit 5 = profile0x0101, bit 6 = profile0x0102, bit 7 = profile0x0103, bit 8 = profile0x0104. Corresponds to information provided in the supportedROHC-Profiles contained in the PDCP-Parameters IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | +| >>Continue ROHC | O | | ENUMERATED (true, ...) | Corresponds to information provided in the drb-ContinueROHC contained in the PDCP-Config IE as defined in TS 38.331 [10] | +| >uplinkOnlyROHC | | | | | +| >>max CID | M | | INTEGER (0..16383) | Corresponds to information provided in the maxCID contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >>ROHC Profiles | M | | INTEGER (0..511) | Bitmap with supported UE profiles, bit 4 = profile0x0006. Corresponds to information provided in the supportedROHC-Profiles contained in the PDCP-Parameters IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | +| >>Continue ROHC | O | | ENUMERATED (true, ...) | Corresponds to information provided in the drb-ContinueROHC contained in the PDCP-Config IE as defined in TS 38.331 [10] | + +### 9.3.1.41 T-Reordering Timer + +This IE indicates the t-Reordering timer. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T-Reordering Timer | M | | ENUMERATED (0, 1, 2, 4, 5, 8, 10, 15, 20, 30, 40, 50, 60, 80, 100, 120, 140, 160, 180, 200, 220, 240, 260, 280, 300, 500, 750, 1000, 1250, 1500, 1750, 2000, 2250, 2500, 2750, 3000, ...) | Indicates the t-Reordering UL timer. The values are expressed in ms. Corresponds to information provided in the t-Reordering contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | + +### 9.3.1.42 Discard Timer + +This IE indicates PDCP discard timer. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Discard Timer | | | ENUMERATED (10, 20, 30, 40, 50, 60, 75, 100, 150, 200, 250, 300, 500, 750, 1500, Infinity) | Indicates the PDCP discard timer. The values are expressed in ms. Corresponds to information provided in the discardTimer contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | + +### 9.3.1.43 UL Data Split Threshold + +This IE indicates UL data split threshold. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UL Data Split Threshold | | | ENUMERATED (0, 100, 200, 400, 800, 1600, 3200, 6400, 12800, 25600, 51200, 102400, 204800, 409600, 819200, 1228800, 1638400, 2457600, 3276800, 4096000, 4915200, 5734400, 6553600, Infinity, ...) | Indicates the UL data split threshold. The values are expressed in bytes. Corresponds to information provided in the ul-DataSplitThreshold contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | + +### 9.3.1.44 Data Usage Report List + +This IE provides information on the data usage for the UE, e.g., secondary NR RAT in EN-DC as specified in TS 37.340 [19]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Data usage report Item | | 1 .. | | | - | - | +| >DRB ID | M | | 9.3.1.16 | | - | - | +| > RAT Type | M | | ENUMERATED (E-UTRA, NR, ...) | The value E-UTRA is not used in this version of the specification. | - | - | +| >DRB Usage Report List | | 1 | | | - | - | +| >>DRB Usage Report Item | | 1.. | | | - | - | +| >>>Start timestamp | M | | OCTET STRING (SIZE(4)) | Encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [14]. It indicates the UTC time when the recording of the Data Volume was started. | - | - | +| >>>End timestamp | M | | OCTET STRING (SIZE(4)) | Encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [14]. It indicates the UTC | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------|----------|-------|---------------------------------|-------------------------------------------------------|-------------|----------------------| +| | | | | time when the recording of the Data Volume was ended. | | | +| >>>Usage count UL | M | | INTEGER (0..2 64 -1) | The unit is: octets. | - | - | +| >>>Usage count DL | M | | INTEGER (0..2 64 -1) | The unit is: octets. | - | - | + +| Range bound | Explanation | +|--------------------|----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs. Value is 32. | +| Maxnooftimeperiods | Maximum no. of time reporting periods. Value is 2. | + +### 9.3.1.45 Flow Failed List + +This IE contains a list of QoS flows with a cause value. It is used for example to indicate failed QoS flow(s) or QoS flow(s) to be released. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|-----------------------|-----------------------|-----------------------|-------------|----------------------| +| QoS Flow Item IEs | | 1.. | | | - | - | +| >QoS Flow Identifier | M | | 9.3.1.24 | | - | - | +| >Cause | M | | 9.3.1.2 | | - | - | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows in a PDU Session. Value is 64. | + +### 9.3.1.46 Packet Loss Rate + +This IE indicates the Packet Loss Rate for a QoS Flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|------------------------|----------------------------------------------------------------------------------| +| Packet Loss Rate | M | | INTEGER (0..1000, ...) | Ratio of lost packets per number of packets sent, expressed in tenth of percent. | + +### 9.3.1.47 Packet Delay Budget + +This IE indicates the Packet Delay Budget for a QoS Flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|------------------------|------------------------------------------------------------------------------------------| +| Packet Delay Budget | M | | INTEGER (0..1023, ...) | Upper bound value for the delay that a packet may experience expressed in unit of 0.5ms. | + +### 9.3.1.48 Packet Error Rate + +This IE indicates the Packet Error Rate for a QoS Flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------| +| Scalar | M | | INTEGER (0..9, ...) | The packet error rate is expressed as $\text{Scalar} \times 10^{-k}$ where $k$ is the Exponent. | +| Exponent | M | | INTEGER (0..9, ...) | | + +### 9.3.1.49 Averaging Window + +This IE indicates the Averaging Window for a QoS Flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|------------------------|-------------------------------------------| +| Averaging Window | M | | INTEGER (0..4095, ...) | Unit: ms.
The default value is 2000ms. | + +### 9.3.1.50 Maximum Data Burst Volume + +This IE indicates the Maximum Data Burst Volume for a QoS Flow and applies to delay critical GBR QoS flows only. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|---------------------------------------|-----------------------| +| Maximum Data Burst Volume | M | | INTEGER (0..4095, ..., 4096..2000000) | Unit: byte. | + +### 9.3.1.51 Priority Level + +This IE indicates the Priority Level for a QoS Flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Priority Level | M | | INTEGER (0..127, ...) | Values ordered in decreasing order of priority i.e. with 1 as the highest priority and 127 as the lowest priority.
The value 0 is not used in this version of the specification. | + +### 9.3.1.52 Security Result + +This IE indicates whether the security policy indicated as "preferred" in the *Security Indication* IE is performed or not. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Integrity Protection Result | M | | ENUMERATED (performed, not performed, ...) | Indicates whether UP integrity protection is performed or not for the concerned PDU Session Resource for the gNB/ng-eNB CP-UP separation, or for the | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | concerned DRB for the eNB CP-UP separation. | +| Confidentiality Protection Result | M | | ENUMERATED (performed, not performed, ...) | Indicates whether UP ciphering is performed or not for the concerned PDU Session Resource.
NOTE: This IE is not applicable to eNB CP-UP separation. | + +### 9.3.1.53 Transaction ID + +The *Transaction ID* IE uniquely identifies a procedure among all ongoing parallel procedures of the same type initiated by the same protocol peer. Messages belonging to the same procedure shall use the same Transaction ID. The Transaction ID is determined by the initiating peer of a procedure. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|-----------------------| +| Transaction ID | M | | INTEGER (0..255, ...) | | + +### 9.3.1.54 Inactivity timer + +This IE indicates the inactivity timer. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-------------------------|------------------------------------------------------------------------------| +| Inactivity Timer | M | | INTEGER (1.. 7200, ...) | Indicates the inactivity timer. The values are expressed in seconds . | + +### 9.3.1.55 Paging Priority Indicator (PPI) + +The Paging Policy Indicator is used for paging policy differentiation (see details in TS 23.501 [20]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| PPI | M | | INTEGER (0.. 7, ...) | | + +### 9.3.1.56 gNB-CU-UP Capacity + +This IE indicates the relative processing capacity of an gNB-CU-UP with respect to other gNB-CU-UPs in order to load-balance among different gNB-CU-UPs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| gNB-CU-UP Capacity | M | | INTEGER(0..255) | | - | - | + +### 9.3.1.57 Maximum Integrity Protected Data Rate + +This IE indicates the maximum aggregate data rate for integrity protected DRBs for a UE as defined in TS 38.300 [8]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum IP rate | M | | ENUMERATED
(64kbps, max-
UErate, ...) | Defines the upper bound of the aggregated data rate of user plane integrity protected data. This limit applies to both UL and DL independently. | + +### 9.3.1.58 PDCP SN Status Information + +This IE contains information about PDCP PDU transfer status of a DRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| PDCP Status Transfer UL | | 1 | | | – | | +| >Receive Status Of PDCP SDU | O | | BIT STRING
(SIZE(1..
131072)) |

The first bit indicates the status of the SDU after the First Missing UL PDCP SDU.

The Nth bit indicates the status of the UL PDCP SDU in position (N + First Missing SDU Number) modulo (1 + the maximum value of the PDCP-SN).

0: PDCP SDU has not been received.
1: PDCP SDU has been received correctly.

| – | | +| >UL COUNT Value | M | | PDCP Count
9.3.1.35 | PDCP-SN and Hyper Frame Number of the first missing UL SDU | – | | +| PDCP Status Transfer DL | | 1 | | | – | | +| >DL COUNT Value | M | | PDCP Count
9.3.1.35 | PDCP-SN and Hyper Frame Number that the target NG-RAN node (handover) or the NG-RAN node to which the DRB context is transferred (dual connectivity) should assign for the next DL SDU | – | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | | not having an SN yet. | | | + +### 9.3.1.59 QoS Flow Mapping List + +This IE contains a list of DRBs containing information about the mapped QoS flows. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------|----------|-----------------------|-----------------------|-----------------------|-------------|----------------------| +| QoS Flow Mapping Item | | 1.. | | | – | | +| >QoS Flow Identifier | M | | 9.3.1.24 | | – | | +| >QoS Flow Mapping Indication | O | | 9.3.1.60 | | – | | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU Session. Value is 64. | + +### 9.3.1.60 QoS Flow Mapping Indication + +This IE is used to indicate whether only the uplink or only the downlink of a QoS flow is mapped to a DRB. For MBS this IE is applied to an MRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| QoS Flow Mapping Indication | M | | ENUMERATED (ul, dl, ...) | Indicates that only the uplink or downlink QoS flow is mapped to the DRB.
If applied to an MRB, the IE is always set to "dl". | + +### 9.3.1.61 PDCP SN Size + +This IE carries the PDCP SN Size. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDCP SN Size | M | | ENUMERATED (s-12, s-18, ..., s-7, s-15, s-16) | Indicates the PDCP SN size in bits. For more information see PDCP-Config IE in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | + +### 9.3.1.62 Network Instance + +This IE provides the network instance to be used by the NG-RAN node when selecting a particular transport network resource as described in TS 23.501 [20]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-----------------------|-----------------------| +| Network Instance | M | | INTEGER (1..256, ...) | | + +### 9.3.1.63 MR-DC Usage Information + +This IE provides information on the data usage for the UE connected to 5GC, e.g., secondary RAT in MR-DC as specified in TS 37.340 [19]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|----------------------|---------------------------------------|-----------------------|-------------|----------------------| +| Data Usage per PDU Session Report | O | | | | - | | +| >Secondary RAT Type | M | | ENUMERATED (nR, e-UTRA...) | | | | +| >PDU session Timed Report List | M | | MR-DC Data Usage Report List 9.3.1.64 | | | | +| Data Usage per QoS Flow List | O | | | | | | +| >Data Usage per QoS Flow Item | | 1.. | | | - | | +| >>QoS Flow Indicator | M | | 9.3.1.24 | | - | | +| >>Secondary RAT Type | M | | ENUMERATED (nR, e-UTRA...) | | - | | +| >>QoS Flow Timed Report List | M | | MR-DC Data Usage Report List 9.3.1.64 | | - | | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.1.64 MR-DC Data Usage Report List + +This IE provides information on the data usage. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MR-DC Data Usage Report Item | | 1.. | | | +| >Start timestamp | M | | OCTET STRING (SIZE(4)) | UTC time encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [14]. It indicates the start time of the collecting period of the included Usage Count UL IE and Usage Count DL IE. | +| >End timestamp | M | | OCTET STRING | UTC time encoded in the same | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | (SIZE(4)) | format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [14]. It indicates the end time of the collecting period of the included Usage Count UL IE and Usage Count DL IE. | +| >Usage count UL | M | | INTEGER (0..2 64 -1) | The unit is: octets. | +| >Usage count DL | M | | INTEGER (0..2 64 -1) | The unit is: octets. | + +| Range bound | Explanation | +|--------------------|----------------------------------------------------| +| maxnooftimeperiods | Maximum no. of time reporting periods. Value is 2. | + +### 9.3.1.65 gNB-DU ID + +The gNB-DU ID uniquely identifies a gNB-DU at least within a gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| gNB-DU ID | M | | INTEGER (0 .. 2 36 -1) | The gNB-DU ID is independently configured from cell identifiers, i.e. no connection between gNB-DU ID and cell identifiers. | + +### 9.3.1.66 Common Network Instance + +This IE provides the common network instance to be used by the NG-RAN node when selecting a particular transport network resource as described in TS 23.501 [9] in a format common with 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Common Network Instance | M | | OCTET STRING | The octets of OCTET STRING are encoded as the Network Instance field of the Network Instance IE specified in TS 29.244 [29] | + +### 9.3.1.67 Activity Notification Level + +This IE contains information on which level activity notification shall be performed.. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|----------------------------------------|-----------------------| +| Activity Notification Level | M | | ENUMERATED (DRB, PDU Session, UE, ...) | | + +### 9.3.1.68 Trace Activation + +This IE defines parameters related to a trace session activation. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Trace ID | M | | OCTET STRING (SIZE(8)) | This IE is composed of the following:
Trace Reference defined in TS 32.422 [24] (leftmost 6 octets, with PLMN information encoded as in 9.3.1.7), and
Trace Recording Session Reference defined in TS 32.422 [24] (last 2 octets). | - | - | +| Interfaces To Trace | M | | BIT STRING (SIZE(8)) | Each position in the bitmap represents an NG-RAN node interface:
first bit = NG-C,
second bit = Xn-C,
third bit = Uu,
fourth bit = F1-C,
fifth bit = E1:
other bits reserved for future use.
Value '1' indicates 'should be traced'.
Value '0' indicates 'should not be traced'. | - | - | +| Trace Depth | M | | ENUMERATED (minimum, medium, maximum, minimumWithoutVendorSpecific Extension, mediumWithout VendorSpecific Extension, maximumWithoutVendorSpecific Extension, ...) | Defined in TS 32.422 [24]. | - | - | +| Trace Collection Entity IP Address | M | | Transport Layer Address 9.3.2.4 | For File based Reporting.
Defined in TS 32.422 [24].
Should be ignored if URI is present. | - | - | +| Trace Collection Entity URI | O | | 9.3.2.8 | For Streaming based Reporting.
Defined in TS 32.422 [24]
Replaces Trace | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------|----------|-------|-----------------------|------------------------------------------|-------------|----------------------| +| | | | | Collection Entity IP Address if present. | | | +| MDT Configuration | O | | 9.3.1.85 | | YES | ignore | + +### 9.3.1.69 Subscriber Profile ID for RAT/Frequency priority + +This parameter is used to define local configuration for RRM strategies. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------|----------|-------|-----------------------|-----------------------| +| Subscriber Profile ID for RAT/Frequency priority | M | | INTEGER (1..256, ...) | | + +### 9.3.1.70 Additional RRM Policy Index + +The *Additional RRM Policy Index* IE is used to provide additional information as specified in TS 36.300 [25]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|-----------------------|-----------------------| +| Additional RRM Policy Index | M | | BIT STRING (SIZE(32)) | | + +### 9.3.1.71 Retainability Measurements Information + +This IE contains information on removed DRB(s) and QoS Flow(s) which are needed to perform retainability measurements. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|----------------------|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DRB Removed List | | 1 | | | - | | +| >DRB Removed Item | | 1.. | | | - | | +| >>DRB ID | M | | 9.3.1.16 | | - | | +| >>DRB Released In Session | O | | ENUMERATED (released in session, not released in session, ...) | Indicates if the DRB was “in session” or not (as defined in TS 32.425 [26] and TS 28.552 [22]) when released | - | | +| >>DRB Accumulated Session Time | O | | OCTET STRING (SIZE(5)) | Accumulated “in session” time for the DRB, as defined in TS 32.425 [26] and TS 28.552 [22], in milliseconds | - | | +| >>QoS Flow Removed List | | 0..1 | | | - | | +| >>>QoS Flow Removed Item | | 1.. | | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>>QoS Flow Identifier | M | | 9.3.1.24 | | - | | +| >>>>QoS Flow Released In Session | O | | ENUMERATED (released in session, not released in session, ...) | Indicates if the QoS Flow was "in session" or not (as defined in TS 28.552 [22]), when released | - | | +| >>>>QoS Flow Accumulated Session Time | O | | OCTET STRING (SIZE(5)) | Accumulated "in session" time for the QoS Flow, as defined in TS 28.552 [22], in milliseconds | - | | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofQoSFlows | Maximum no. of QoS flows in a PDU Session. Value is 64. | + +### 9.3.1.72 TNL Available Capacity Indicator + +The *TNL Available Capacity Indicator* IE indicates offered and available capacity of the Transport Network. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|---------------------------|--------------------------------------------------------------------| +| DL TNL Offered Capacity | M | | INTEGER (0..16777216,...) | Maximum capacity in kbps | +| DL TNL Available Capacity | M | | INTEGER (0..100,...) | Available capacity. Value 100 corresponds to the offered capacity. | +| UL TNL Offered Capacity | M | | INTEGER (0..16777216,...) | Maximum capacity in kbps | +| UL TNL Available Capacity | M | | INTEGER (0..100,...) | Available capacity. Value 100 corresponds to the offered capacity. | + +### 9.3.1.73 HW Capacity Indicator + +The *HW Capacity Indicator* IE indicates offered and available throughput experienced by the gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|---------------------------|-----------------------------------------------------------------------------------------------| +| Offered Throughput | M | | INTEGER (1..16777216,...) | Maximum capacity offered by the gNB-CU-UP in kbps | +| Available Throughput | M | | INTEGER(0..100, ...) | Average available capacity at the gNB-CU-UP. Value 100 corresponds to the offered throughput. | + +### 9.3.1.74 Redundant QoS Flow Indicator + +This IE provides the Redundant QoS Flow Indicator for a QoS flow as specified in TS 23.501 [20]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Redundant QoS Flow Indicator | M | | ENUMERATED (true, false) | This IE indicates that this QoS flow is requested for the redundant transmission. Value "true" indicates that redundant transmission is requested for this QoS flow. Value "false" indicates that redundant transmission is requested to be stopped if started. | + +### 9.3.1.75 TSC Traffic Characteristics + +This IE provides the traffic characteristics of TSC QoS flows. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|-------------------------------------|-----------------------| +| TSC Assistance Information Downlink | O | | TSC Assistance Information 9.3.1.76 | | +| TSC Assistance Information Uplink | O | | TSC Assistance Information 9.3.1.76 | | + +### 9.3.1.76 TSC Assistance Information + +This IE provides the TSC assistance information for a TSC QoS flow in the uplink or downlink (see TS 23.501 [20]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Periodicity | M | | 9.3.1.77 | | - | | +| Burst Arrival Time | O | | 9.3.1.78 | | - | | +| Survival Time | O | | 9.3.1.103 | | YES | ignore | +| N6 Jitter Information | O | | 9.3.1.144 | | YES | ignore | + +### 9.3.1.77 Periodicity + +This IE indicates the Periodicity of the TSC QoS flow as defined in TS 23.501 [20]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------|-----------------------------------------| +| Periodicity | M | | INTEGER (0..640000, ...) | Periodicity expressed in units of 1 us. | + +### 9.3.1.78 Burst Arrival Time + +This IE indicates the Burst Arrival Time of the TSC QoS flow as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------| +| Burst Arrival Time | M | | OCTET STRING | Encoded in the same format as the ReferenceTime IE as defined in TS 38.331 [10]. The value is | + +| | | | | | +|--|--|--|--|------------------------------| +| | | | | provided with 1 us accuracy. | +|--|--|--|--|------------------------------| + +### 9.3.1.79 Extended Packet Delay Budget + +This IE indicates the Packet Delay Budget for a QoS flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|-------------------------------------------|-------------------------------------------------------------------------------------------| +| Extended Packet Delay Budget | M | | INTEGER
(0..65535, ..., 65536..109999) | Upper bound value for the delay that a packet may experience expressed in unit of 0.01ms. | + +### 9.3.1.80 Redundant PDU Session Information + +This IE defines Redundancy information to be applied to a PDU Session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------|----------|-------|-----------------------------|------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| RSN | M | | ENUMERATED
(v1, v2, ...) | | - | - | +| PDU Session Pair ID | O | | INTEGER
(0..255, ...) | as defined in TS 23.501 [20]. This IE is not used in the response message. If received, the gNB-CU-CP shall ignore it. | YES | ignore | + +### 9.3.1.81 QoS Mapping Information + +This IE indicates the DSCP and/or IPv6 Flow Label field(s) of IP packet which is sent through the GTP-U tunnel of a requested DRB. This IE is only used for IAB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------|-----------------------| +| DSCP | O | | BIT STRING
(SIZE(6)) | | +| Flow Label | O | | BIT STRING
(SIZE(20)) | | + +### 9.3.1.82 NID + +This IE contains the Network Identifier of an SNPN, as specified in TS 23.501 [20]. The NID is specified in TS 23.003 [23]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------|-----------------------| +| NID | M | | BIT STRING
(SIZE(44)) | | + +### 9.3.1.83 NPN Support Information + +This IE provides NPN related information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE NPN Support Information | M | | | | +| > NPN Support Information -SNPN | | | | | +| >>NID | M | | 9.3.1.82 | This IE is associated with the PLMN Identity and the Slice Support List contained in the Supported PLMNs IE. Together with the PLMN Identity it identifies the SNPN supported by the gNB-CU-UP. | + +### 9.3.1.84 NPN Context Information + +This IE provides bearer context related NPN information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE NPN Context Information | M | | | | +| > SNPN Information | | | | | +| >>NID | M | | 9.3.1.82 | This IE is associated with Serving PLMN information contained in bearer context related E1AP message. Together with the Serving PLMN identity it identifies the serving SNPN. | + +### 9.3.1.85 MDT Configuration + +The IE defines the NR/E-UTRAN MDT configuration parameters. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MDT Activation | M | | ENUMERATED
(Immediate MDT only, Immediate MDT and Trace,...) | | +| CHOICE MDT Mode | M | | | | +| > Immediate MDT | | | | | +| >>Measurements to Activate | M | | BITSTRING
(SIZE(8)) | Each position in the bitmap indicates a MDT measurement, as defined in TS 37.320 [27].
Fourth Bit = M4,
Seventh Bit = M6,
Eighth Bit = M7.
Value “1” indicates “activate” and value “0” indicates “do not activate”.
This version of the specification does not use bits 1, bit 2, bit 3, | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------|-----------------------| +| | | | | bit 5 and bit 6. | +| >>M4 Configuration | C-ifM4 | | 9.3.1.86 | | +| >>M6 Configuration | C-ifM6 | | 9.3.1.87 | | +| >>M7 Configuration | C-ifM7 | | 9.3.1.88 | | + +| Condition | Explanation | +|-----------|----------------------------------------------------------------------------------------------------| +| ifM4 | This IE shall be present if the Measurements to Activate IE has the fourth bit set to "1". | +| ifM6 | This IE shall be present if the Measurements to Activate IE has the seventh bit set to "1". | +| ifM7 | This IE shall be present if the Measurements to Activate IE has the eighth bit set to "1". | + +### 9.3.1.86 M4 Configuration + +This IE defines the parameters for M4 measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|--------------------------------------------------------------|-----------------------|-------------|----------------------| +| M4 Collection Period | M | | ENUMERATED (ms1024, ms2048, ms5120, ms10240, min1, ...) | | - | - | +| M4 Links to log | M | | ENUMERATED (uplink, downlink, both-uplink-and-downlink, ...) | | - | - | +| M4 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity, ...) | Number of reports. | YES | ignore | + +### 9.3.1.87 M6 Configuration + +This IE defines the parameters for M6 measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| M6 Report Interval | M | | ENUMERATED (ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1, min6, min12, min30, ...) | | - | - | +| M6 Links to log | M | | ENUMERATED(uplink, downlink, both-uplink-and-downlink, ...) | | - | - | + +| | | | | | | | +|------------------|---|--|---------------------------------------------------|--------------------|-----|--------| +| M6 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity,...) | Number of reports. | YES | ignore | +|------------------|---|--|---------------------------------------------------|--------------------|-----|--------| + +### 9.3.1.88 M7 Configuration + +This IE defines the parameters for M7 measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|---------------------------------------------------|-----------------------|-------------|----------------------| +| M7 Collection Period | M | | INTEGER (1..60, ...) | | - | - | +| M7 Links to log | M | | ENUMERATED(uplink, ...) | | - | - | +| M7 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity,...) | Number of reports. | YES | ignore | + +### 9.3.1.89 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 | | 9.3.1.7 | | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofMDTPLMNs | Maximum no. of PLMNs in the MDT PLMN list. Value is 16. | + +### 9.3.1.90 EHC Parameters + +This IE carries the EHC parameters for ethernet header compression. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------|----------|-------|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| EHC Common | M | | | | - | - | +| >EHC-CID-Length | M | | ENUMERATED { bits7, bits15, ... } | Corresponds to information provided in the ehc-CID-Length contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | - | - | +| EHC Downlink | O | | | | - | - | +| >drb-ContinueEHC-DL | M | | ENUMERATED { true, ..., false } | Corresponds to information | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------|----------|-------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | provided in the drb-ContinueEHC-DL contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. The value "false" indicates that the PDCP entity resets the downlink EHC header compression protocol during PDCP re-establishment. | | | +| >maxCID-EHC-DL | O | | INTEGER(1..32 767, ...) | Indicate the maximum number of DL EHC contexts that can be established for the DRB. The total value of maxCID-EHC-DL plus maxCID-EHC-UL (as specified in TS 38.331) across all bearers for the UE should be less than or equal to the value of maxNumberEHC-Contexts parameter as indicated by the UE. | YES | ignore | +| EHC Uplink | O | | | | - | - | +| >drb-ContinueEHC-UL | M | | ENUMERATED { true, ..., false } | Corresponds to information provided in the drb-ContinueEHC-UL contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. The value "false" indicates that the | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | PDCP entity resets the uplink EHC header compression protocol during PDCP re-establishment. | | | + +### 9.3.1.91 DAPS Request Information + +The *DAPS Indicator* IE indicates that DAPS HO is requested for the concerned DRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|------------------------------------|-------------------------------------| +| DAPS Indicator | M | | ENUMERATED (DAPS HO required, ...) | Indicates that DAPS HO is requested | + +### 9.3.1.92 Early Forwarding COUNT Information + +This IE contains DL COUNT value related to early data forwarding during DAPS Handover or Conditional Handover or conditional PSCell change or conditional PSCell addition or subsequent CPAC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------| +| CHOICE Early Forwarding | M | | | | +| > First DL COUNT | | | | | +| >>FIRST DL COUNT Value | M | | PDCP Count 9.3.1.35 | PDCP-SN and Hyper frame number of the first DL SDU that the source NG-RAN node forwards to the target NG-RAN node | +| > DL Discarding | | | | | +| >>DISCARD DL COUNT Value | M | | PDCP Count 9.3.1.35 | PDCP-SN and Hyper frame number for which the target NG-RAN node should discard forwarded DL SDUs associated with lower values. | + +### 9.3.1.93 Alternative QoS Parameters Set List + +This IE contains alternative sets of QoS parameters which the NG-RAN node can indicate to be fulfilled when notification control is enabled and it cannot fulfil the requested list of QoS parameters. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|----------------------------------|-----------------------|-----------------------| +| Alternative QoS Parameters Item | | 1..< maxnoofQoSParaSets > | | | +| >Alternative QoS Parameters Index | M | | INTEGER (1..8,..) | | +| >Guaranteed Flow Bit Rate Downlink | O | | Bit Rate 9.3.1.20 | | +| >Guaranteed Flow Bit | O | | Bit Rate | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|-----------------------|-----------------------| +| Rate Uplink | | | 9.3.1.20 | | +| >Packet Delay Budget | O | | 9.3.1.47 | | +| >Packet Error Rate | O | | 9.3.1.48 | | + +| Range bound | Explanation | +|--------------------|---------------------------------------------------------------------------------------------------------------| +| maxnoofQoSParaSets | Maximum no. of alternative sets of QoS Parameters allowed for the QoS under Notification Control. Value is 8. | + +### 9.3.1.94 Extended Slice Support List + +This IE indicates a list of supported slices. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-----------------------------|-----------------------|-----------------------|-------------|----------------------| +| Slice Support Item IEs | | 1.. | | | - | | +| >S-NSSAI | M | | 9.3.1.9 | | - | | + +| Range bound | Explanation | +|----------------------|---------------------------------------------------------------| +| maxnoofExtSliceItems | Maximum no. of signalled slice support items. Value is 65535. | + +### 9.3.1.95 Extended gNB-CU-CP Name + +This IE provides extended human readable name of the gNB-CU-CP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------|-----------------------------------|-----------------------|-------------|----------------------| +| gNB-CU-CP Name Visible | O | | VisibleString (SIZE(1..150, ...)) | | - | | +| gNB-CU-CP Name UTF8 | O | | UTF8String (SIZE(1..150, ...)) | | - | | + +### 9.3.1.96 Extended gNB-CU-UP Name + +This IE provides extended human readable name of the gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------|-----------------------------------|-----------------------|-------------|----------------------| +| gNB-CU-UP Name Visible | O | | VisibleString (SIZE(1..150, ...)) | | - | | +| gNB-CU-UP Name UTF8 | O | | UTF8String (SIZE(1..150, ...)) | | - | | + +### 9.3.1.97 Extended NR CGI Support List + +This IE indicates the list of supported NR CGIs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|-----------------------|-----------------------|-----------------------| +| Extended NR CGI Support Item IEs | | 0.. | | | +| >NR CGI | M | | 9.3.1.14 | | + +| Range bound | Explanation | +|------------------|------------------------------------------------------------| +| maxnoofExtNR CGI | Maximum no. of extended NR CGIs supported. Value is 16384. | + +### 9.3.1.98 Direct Forwarding Path Availability + +This IE indicates whether a direct forwarding path is available. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|---------------------------------------------------------------------------------------------|-----------------------| +| Direct Forwarding Path Availability | M | | ENUMERATED
(inter-system direct path available, ..., intra-system direct path available) | | + +### 9.3.1.99 IAB-donor-CU-UP PSK Info + +This IE contains the IAB-Donor-CU-UP Pre-Shared Key generated by the gNB-CU-CP and IP addresses for IAB-donor-CU-UP and IAB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|------------------|-----------------------|--------------------------------------------------------------------| +| IAB-donor-CU-UP PSK Info Item IEs | | 1.. | | | +| >IAB-Donor-CU-UP PSK | M | | OCTET STRING | This IE contains the $K_{IAB-CU-UP}$ as defined in TS 33.501 [13]. | +| >IAB-Donor-CU-UP IP Address | M | | 9.3.2.4 | | +| >IAB-DU IP Address | M | | 9.3.2.4 | | + +| Range bound | Explanation | +|-------------|------------------------------------------------------------------------| +| maxnoofPSKs | Maximum no. of PSKs to be updated in one E1AP procedure. Value is 256. | + +### 9.3.1.100 ECGI Support List + +This IE indicates the list of supported ECGIs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|------------------|-----------------------|-----------------------| +| ECGI Support Item IEs | | 1.. | | | +| >ECGI | M | | 9.3.1.101 | | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------------------------| +| maxnoofECGI | Maximum no. of supported ECGIs. Value is 512. This range may be redefined. | + +### 9.3.1.101 ECGI + +The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| PLMN Identity | M | | 9.3.1.7 | | +| E-UTRAN Cell Identity | M | | BIT STRING (SIZE(28)) | | + +### 9.3.1.102 UE Slice Maximum Bit Rate List + +This IE contains the UE Slice Maximum Bit Rate List as specified in TS 23.501 [20]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|----------------------------|-----------------------|---------------------------------------------------------------------------------------------| +| UE Slice Maximum Bit Rate Item | | 1..<
maxnoofSMBRValues> | | | +| >S-NSSAI | M | | 9.3.1.9 | | +| >UE Slice Maximum Bit Rate Downlink | M | | Bit Rate
9.3.1.20 | This IE indicates the UE-Slice-MBR as specified in TS 23.501 [9] in the downlink direction. | + +| Range bound | Explanation | +|-----------------------------------------|------------------------------------------------------------------------------------------------------------------| +| maxnoofSMBRValuesmaxnoofAllowedS-NSSAIs | Maximum no. of SLICE MAXIMUM BIT RATE values for a UE. Value is 8
Maximum no. of allowed S-NSSAI. Value is 8. | + +### 9.3.1.103 Survival Time + +This IE indicates the Survival Time of the TSC QoS flow as defined in TS 23.501 [20]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|-------------------------------------------| +| Survival Time | M | | INTEGER (0..1920000, ...) | Survival Time expressed in units of 1 us. | + +### 9.3.1.104 UDC Parameters + +This IE carries the UDC parameters for uplink data compression. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|------------------------------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| Buffer Size | M | | ENUMERATED (kbyte2, kbyte4, kbyte8, ...) | Indicates the buffer size applied for UDC. Corresponds to information provided in the | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | bufferSize contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | | | +| Dictionary | O | | ENUMERATED (sip-SDP, operator, ...) | Indicates which pre-defined dictionary is used for UDC. Corresponds to information provided in the dictionary contained in the PDCP-Config IE as defined in TS 38.331 [10] for gNB or ng-eNB CP-UP separation, or in TS 36.331 [33] for eNB CP-UP separation. | - | | +| Continue UDC | O | | ENUMERATED (true, ...) | Corresponds to information provided in the drb-ContinueUDC contained in the PDCP-Config IE as defined in TS 38.331 [10]. | - | | +| Version ID | O | | INTEGER (0..15) | Indicates the version ID for Operator Defined Dictionary. Corresponds to information provided in versionOfDictionary contained in the PDCP-Parameters IE as defined in TS38.331[10]. | YES | ignore | + +### 9.3.1.105 SCG Activation Status + +The *SCG Activation Status* IE indicates the status of SCG resources. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|----------------------------|-----------------------| +| SCG Activation Status | M | | ENUMERATED (SCG activated, | | + +| | | | | | +|--|--|--|-----------------------|--| +| | | | SCG deactivated, ...) | | +|--|--|--|-----------------------|--| + +### 9.3.1.106 gNB-CU-CP MBS E1AP ID + +The gNB-CU-CP UE E1AP ID uniquely identifies the MBS association over the E1 interface within the gNB-CU-CP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-CU-CP MBS E1AP ID | M | | INTEGER (0 .. 2 24 -1) | | + +### 9.3.1.107 gNB-CU-UP MBS E1AP ID + +The gNB-CU-UP UE E1AP ID uniquely identifies the MBS association over the E1 interface within the gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-CU-UP MBS E1AP ID | M | | INTEGER (0 .. 2 16 -1) | | + +### 9.3.1.108 Global MBS Session ID + +This IE indicates the TMGI uniquely identifies an MBS session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|----------------------------------| +| TMGI | M | | OCTET STRING (SIZE(6)) | Encoded as defined in TS 23.003. | +| NID | O | | 9.3.1.82 | Defined in TS 23.003 [23]. | + +### 9.3.1.109 DU Cell Reference + +This IE indicates the index of an NR CGI within a DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------| +| DU Cell Index | M | | INTEGER (1..512) | To support per cell F1-U tunnels and being able to refer to it. | +| NR CGI | M | | 9.3.1.14 | | + +### 9.3.1.110 gNB-CU-UP MBS Support Information + +This IE includes MBS related support information for the E1 Setup procedure. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------------|----------|---------------------------|-----------------------|-----------------------| +| MBS Support Information To Add List | | 0..1 | | | +| >MBS Support Information To Add Item | | 1.. | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------|----------|---------------------------|-----------------------|-----------------------| +| | | > | | | +| >>Global MBS Session ID | M | | 9.3.1.108 | | +| MBS Support Information To Remove List | | 0..1 | | | +| > MBS Support Information To Remove Item | | 1.. | | | +| >>Global MBS Session ID | M | | 9.3.1.108 | | + +| Range bound | Explanation | +|----------------------|-----------------------------------------------| +| maxnoofMBSSessionIDs | Maximum no. of MBS Session IDs. Value is 512. | + +### 9.3.1.111 MBS Area Session ID + +This IE indicates an MBS Area Session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|---------------------------|-----------------------| +| MBS Area Session ID | M | | INTEGER (0 .. 65535, ...) | | + +### 9.3.1.112 BC Bearer Context NG-U TNL Info at 5GC + +This IE contains TNL information for an MBS Session as provided by the 5GC for shared NG-U multicast transport. It may also contain per Area Session ID NG-U TNL information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------------|----------|-------------------------------|-----------------------|-----------------------| +| CHOICE MBS Session Type | | | | | +| > location independent | | | | | +| >>MBS NG-U Information at 5GC | M | | 9.3.1.113 | | +| > location dependent | | | | | +| >> Location dependent MBS NG-U Information at 5GC | | 1.. | | | +| >>>MBS Area Session ID | M | | 9.3.1.111 | | +| >>MBS NG-U Information at 5GC | M | | 9.3.1.113 | | + +| Range bound | Explanation | +|--------------------------|----------------------------------------------------| +| maxnoofMBSAreaSessionIDs | Maximum no. of MBS Area Session IDs. Value is 256. | + +### 9.3.1.113 MBS NG-U Information at 5GC + +This IE contains TNL information for a single shared NG-U tunnel as provided by the 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|---------------------------------|-----------------------| +| CHOICE MBS NG-U Transport | | | | | +| > multicast | | | | | +| >IP Multicast Address | M | | Transport Layer Address 9.3.2.4 | | +| >IP Source Address | M | | Transport Layer Address 9.3.2.4 | | +| >GTP DL TEID | M | | GTP-TEID 9.3.2.3 | | + +### 9.3.1.114 BC MRB Setup Configuration + +This IE contains MRB configuration information for a BC Bearer Context Context. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|---------------------------|----------------------------------------|-------------------------------------------------------------------------| +| BC MRB To Setup List | | 1..< maxnoofMRBs > | | | +| >MRB ID | M | | 9.3.1.16a | | +| >MBS PDCP Configuration | M | | PDCP Configuration 9.3.1.38 | | +| >MBS QoS Flows Information To Be Setup | M | | QoS Flow QoS Parameters List 9.3.1.25 | | +| >MRB QoS | O | | QoS Flow Level QoS Parameters 9.3.1.26 | Indicates the MRB QoS when more than one QoS Flow is mapped to the MRB. | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +### 9.3.1.115 Requested Action for Available Shared NG-U Termination + +This IE provides information about the requested gNB-CU-UP's action with regards to a potentially available shared NG-U termination. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Requested Action for Available Shared NG-U Termination | M | | ENUMERATED (apply available configuration, apply requested configuration, ..., apply available configuration if same as requested) | | + +### 9.3.1.116 BC Bearer Context NG-U TNL Info at NG-RAN + +This IE contains NG-RAN NG-U TNL information for an MBS Session for both, shared NG-U unicast transport. It may also contain per Area Session ID NG-U TNL information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------------------|----------|-------------------------------|-----------------------|-----------------------| +| CHOICE MBS Session Type | M | | | | +| > location independent | | | | | +| >>MBS NG-U Information at NG-RAN | M | | 9.3.1.117 | | +| > location dependent | | | | | +| >>Location dependent MBS NG-U Information at NG-RAN | | 1.. | | | +| >>>MBS Area Session ID | M | | 9.3.1.111 | | +| >>MBS NG-U Information at NG-RAN | M | | 9.3.1.117 | | + +| Range bound | Explanation | +|--------------------------|----------------------------------------------------| +| maxnoofMBSAreaSessionIDs | Maximum no. of MBS Area Session IDs. Value is 256. | + +### 9.3.1.117 MBS NG-U Information at NG-RAN + +This IE contains NG-RAN TNL information for a single shared NG-U tunnel. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------|----------|-------|----------------------------------------|-----------------------| +| CHOICE MBS NG-U Transport | M | | | | +| > unicast | | | | | +| >>Shared NG-U DL Transport Layer Information | M | | UP Transport Layer Information 9.3.2.1 | | + +| Range bound | Explanation | +|--------------------------|----------------------------------------------------| +| maxnoofMBSAreaSessionIDs | Maximum no. of MBS Area Session IDs. Value is 256. | + +### 9.3.1.118 BC Bearer Context F1-U TNL Info at CU + +This IE contains gNB-CU UP F1-U TNL information for an MBS Session. It may also contain per Area Session ID F1-U TNL information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|----------------------------------------|-----------------------| +| CHOICE MBS Session Type | M | | | | +| > location independent | | | | | +| >>MBS F1-U Information at CU | M | | UP Transport Layer Information 9.3.2.1 | | +| > location dependent | | | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------------------|----------|--------------------------------------------|----------------------------------------|-----------------------| +| >>Location dependent MBS F1-U Information at CU | | 1..<maxnoofMBSAreaSessionIDs> | | | +| >>>MBS Area Session ID | M | | 9.3.1.111 | | +| >>MBS F1-U Information at CU | M | | UP Transport Layer Information 9.3.2.1 | | + +| Range bound | Explanation | +|--------------------------|----------------------------------------------------| +| maxnoofMBSAreaSessionIDs | Maximum no. of MBS Area Session IDs. Value is 256. | + +### 9.3.1.119 BC Bearer Context F1-U TNL Info at DU + +This IE contains CU F1-U TNL information for an MBS Session. It may also contain per Area Session ID F1-U TNL information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------------------|----------|--------------------------------------------|----------------------------------------|-----------------------| +| CHOICE MBS Session Type | M | | | | +| > location independent | | | | | +| >>MBS F1-U Information at DU | M | | UP Transport Layer Information 9.3.2.1 | | +| > location dependent | | | | | +| >>Location dependent MBS F1-U Information at DU | | 1..<maxnoofMBSAreaSessionIDs> | | | +| >>>MBS Area Session ID | M | | 9.3.1.111 | | +| >>MBS F1-U Information at DU | M | | UP Transport Layer Information 9.3.2.1 | | + +| Range bound | Explanation | +|--------------------------|----------------------------------------------------| +| maxnoofMBSAreaSessionIDs | Maximum no. of MBS Area Session IDs. Value is 256. | + +### 9.3.1.120 MC MRB Setup Configuration + +This IE contains MRB configuration information for a MC Bearer Context Context. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------------------------------|---------------------------------------|-----------------------| +| MC MRB To Setup List | | 1..<maxnoofMRBs> | | | +| >MRB ID | M | | 9.3.1.16a | | +| >MBS PDCP Configuration | M | | PDCP Configuration 9.3.1.38 | | +| >MBS QoS Flows Information To Be Setup | M | | QoS Flow QoS Parameters List 9.3.1.25 | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------------------------|-------------------------------------------------------------------------| +| >MRB QoS | O | | QoS Flow Level
QoS Parameters
9.3.1.26 | Indicates the MRB QoS when more than one QoS Flow is mapped to the MRB. | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +### 9.3.1.121 MC Bearer Context NG-U TNL Info at NG-RAN + +This IE contains NG-RAN NG-U TNL information for an MBS Session for both, shared NG-U unicast transport. It may also contain per Area Session ID NG-U TNL information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------------------|----------|-------------------------------|-----------------------|-----------------------| +| CHOICE MBS Session Type | M | | | | +| > location independent | | | | | +| >>MBS NG-U Information at NG-RAN | M | | 9.3.1.117 | | +| > location dependent | | | | | +| >>Location dependent MBS NG-U Information at NG-RAN | | 1.. | | | +| >>>MBS Area Session ID | M | | 9.3.1.111 | | +| >>>MBS NG-U Information at NG-RAN | M | | 9.3.1.117 | | + +| Range bound | Explanation | +|--------------------------|----------------------------------------------------| +| maxnoofMBSAreaSessionIDs | Maximum no. of MBS Area Session IDs. Value is 256. | + +### 9.3.1.122 MC Bearer Context NG-U TNL Info at 5GC + +This IE contains TNL information for a multicast MBS Session as provided by the 5GC for shared NG-U multicast transport. It may also contain an MBS Area Session ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|-----------------------|------------------------------------------------| +| MBS NG-U Information at 5GC | M | | 9.3.1.113 | | +| MBS Area Session ID | O | | 9.3.1.111 | For a location dependent multicast MBS Session | + +### 9.3.1.123 MC Bearer Context NG-U TNL Info at NG-RAN Request + +This IE is used to request NG-U TNL information from the gNB-CU-UP, if not yet available at gNB-CU-CP and may contain an MBS Area Session ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +|---------------|----------|-------|-----------------------|-----------------------| + +| | | | | | +|----------------------------|---|--|-----------------------------|--| +| NG-RAN NG-U TNL requested. | M | | ENUMERATED (requested, ...) | | +| MBS Area Session ID | O | | 9.3.1.111 | | + +### 9.3.1.124 MC Bearer Context F1-U TNL Info at DU + +This IE contains DU F1-U TNL information for a multicast MBS Session. It may also contain per Area Session ID F1-U TNL information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|----------------------------------------|-------------------------------------------------------------------------------------------------| +| MBS F1-U Information at DU | M | | UP Transport Layer Information 9.3.2.1 | | +| MBS Multicast F1-U Context Descriptor | M | | 9.3.1.125 | To support per DU, per cell or per MBS Area Session F1-U tunnels and being able to refer to it. | + +### 9.3.1.125 MBS Multicast F1-U Context Descriptor + +This IE contains a reference to a Multicast F1-U Context and may contain an MBS Area Session ID and an indication to setup a Multicast F1-U Context for ptp retransmissions. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Multicast F1-U Context ReferenceE1 | M | | 9.3.1.139 | | +| MC F1-U Context usage | M | | ENUMERATED (ptm, ptp, ptp retransmission, ptp forwarding, ...) |

"ptm" indicates that the Multicast F1-U Context is setup for ptm transmissions; decided by the DU.

"ptp" indicates that the Multicast F1-U Context is setup for ptp transmissions; decided by the DU.

"ptp retransmission" indicates that the Multicast F1-U Context is setup for ptp retransmissions (based on PDCP Status Report); requested by the CU

"ptp forwarding" indicates that the Multicast F1-U Context is setup for transmitting from a defined MBS Progress Information status onwards; requested by the CU.

| +| MBS Area Session ID | O | | 9.3.1.111 | To support per MBS Area Session F1-U tunnels and being able to refer to it. | + +### 9.3.1.126 Void + +Void. + +### 9.3.1.127 MC Bearer Context NG-U TNL Info at NG-RAN Modify Response + +This IE contains NG-RAN NG-U TNL information for an MBS Session for both, shared NG-U multicast and unicast transport. It may also contain per Area Session ID NG-U TNL information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|-----------------------|-----------------------| +| MBS NG-U Information at NG-RAN | M | | 9.3.1.117 | | +| MBS Area Session ID | O | | 9.3.1.111 | | + +### 9.3.1.128 Discard Timer Extended + +This IE indicates the extended PDCP discard timer. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------|----------|-------|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Discard Timer Extended | M | | ENUMERATED
(0.5, 1, 2, 4, 6, 8, ..., 2000) | Indicates the PDCP discard timer. The values are expressed in ms. Corresponds to information provided in the DiscardTimerExt-r16 or the DiscardTimerExt2-r17 contained in the PDCP-Config IE as defined in TS 38.331 [10]. | + +### 9.3.1.129 MDT PLMN Modification List + +The purpose of the *MDT PLMN List Modification* IE is to provide the modified list of PLMN allowed for MDT. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|----------------------|-----------------------|-----------------------------------------------------------| +| MDT PLMN Modification List | | 0.. | | An empty list indicates there is no PLMN allowed for MDT. | +| >PLMN Identity | M | | 9.3.1.7 | | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofMDTPLMNs | Maximum no. of PLMNs in the MDT PLMN list. Value is 16. | + +### 9.3.1.130 MRB Progress Information + +This IE contains the MRB progress information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE MRB Progress Information SNs | M | | | | +| >12bits | | | | | +| >>PDCP SN Length 12 | M | | INTEGER (0..4095) | | +| >18bits | | | | | +| >>PDCP SN Length 18 | M | | INTEGER | | + +| | | | | | +|-------------------------------|---|--|-------------|--| +| | | | (0..262143) | | +| MRB Progress Information Type | M | | 9.3.1.131 | | + +### 9.3.1.131 MRB Progress Information Type + +This IE contains the MRB progress information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|----------------------------------------------------------|-----------------------| +| MRB Progress Information Type | M | | ENUMERATED
(oldest available,
last delivered, ...) | | + +### 9.3.1.132 MC Forwarding Resource ID + +This IE provides the means to identify a MC forwarding resource. It is uniquely allocated for a MC Bearer Context. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|---------------------------|-----------------------| +| MC Forwarding Resource ID | M | | OCTET STRING
(SIZE(2)) | | + +### 9.3.1.133 MBS Session Associated Information + +This IE provides the means to establish a MC MBS session level forwarding resource to support handover to a gNB not supporting NR MBS. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|----------------------|-------------------------------------------|-----------------------| +| Associated QoS Flow Information List | | 1.. | | | +| >MBS QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.24 | | +| >Associated Unicast QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.24 | | +| MBS Session Forwarding Address | M | | UP Transport Layer Information
9.3.2.1 | | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows in a PDU Session. Value is 64. | + +### 9.3.1.134 MC Forwarding Resource Request + +This IE is used by the gNB-CU-CP for request from the gNB-CU-UP information from the peer node regarding a MC Forwarding Resource. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| MC Forwarding Resource ID | M | | 9.3.1.132 | | + +| | | | | | +|---------------------------------------------|---|-------------------------------|---------------------------|----------------------------------------------------------------------------| +| MBS Area Session ID | O | | 9.3.1.111 | | +| MRB Forwarding Resource Request List | | 0..<maxnoofMRBs> | | | +| >MRB ID | M | | 9.3.1.16a | | +| >MRB Progress Information Type | O | | 9.3.1.131 | Requests MRB Progress Information of the indicated type from the peer node | +| >MRB Forwarding Address Request | O | | ENUMERATED (request, ...) | | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +### 9.3.1.135 MC Forwarding Resource Indication + +This IE is used by the gNB-CU-CP for indicate to the gNB-CU-UP information from the peer node regarding MC Forwarding Resources. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------------------------------|----------------------------------------|-------------------------------------------------------| +| MC Forwarding Resource ID | M | | 9.3.1.132 | | +| MRB Forwarding Indication List | | 0..<maxnoofMRBs> | | | +| >MRB ID | M | | 9.3.1.16a | | +| >MRB Progress Information | O | | 9.3.1.130 | Provides MRB Progress Information from the peer node. | +| >MRB Forwarding Address | O | | UP Transport Layer Information 9.3.2.1 | | +| MBS Session Associated Information | O | | 9.3.1.133 | | + +### 9.3.1.136 MC Forwarding Resource Response + +This IE is used by the gNB-CU-UP to response to requests from the gNB-CU-CP regarding a MC Forwarding Resource at the gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------------------------------|----------------------------------------|-----------------------| +| MC Forwarding Resource ID | M | | 9.3.1.132 | | +| MRB Forwarding Indication List | | 0..<maxnoofMRBs> | | | +| >MRB ID | M | | 9.3.1.16a | | +| >MRB Progress Information | O | | 9.3.1.130 | | +| >MRB Forwarding Address | O | | UP Transport Layer Information 9.3.2.1 | | + +### 9.3.1.137 MC Forwarding Resource Release + +This IE is used by the gNB-CU-CP to release a MC Forwarding Resource at the gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| MC Forwarding Resource ID | M | | 9.3.1.132 | | + +### 9.3.1.138 MC Forwarding Resource Release Indication + +This IE is used by the gNB-CU-UP to indicate the release of a MC Forwarding Resource to the gNB-CU-CP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| MC Forwarding Resource ID | M | | 9.3.1.132 | | + +### 9.3.1.139 Multicast F1-U Context ReferenceE1 + +This IE contains a reference to a Multicast F1-U Context used within an MBS-associated logical E1-connection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|------------------------|----------------------------------------------------------------------------------------------------------------------| +| Multicast F1-U Context ReferenceE1 | M | | OCTET STRING (SIZE(4)) | This value is allocated to uniquely denote an Multicast F1-U Context within an MBS-associated logical E1-connection. | + +### 9.3.1.140 MBS Session Associated Information Non-Support-to-Support + +This IE contains the UE ID, PDU session ID and QFIs associated to a given MBS session, used in handover from non-MBS-supporting RAN node to MBS-supporting RAN node to eliminate packet duplication. + +NOTE: This IE is only applicable for deployments deriving the PDCP COUNT values by means of a DL MBS QFI Sequence Number provided on NG-U and requires the appropriate associated PDU Session and MBS session resources to be provided by the same logical gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|---------------------------------------------------|-----------------------| +| UE Reference ID | M | | gNB-CU-CP UE E1AP ID 9.3.1.4 | | +| PDU Session ID | M | | 9.3.1.21 | | +| Associated QoS Flow Information List | M | | MBS Session Associated Information List 9.3.1.141 | | + +### 9.3.1.141 MBS Session Associated Information List + +This IE provides the association between MBS QoS flows and unicast QoS flows. + +NOTE: This IE is only applicable for deployments deriving the PDCP COUNT values by means of a DL MBS + +QFI Sequence Number provided on NG-U and requires the appropriate associated PDU Session and MBS session resources to be provided by the same logical gNB-CU-UP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------|----------|----------------------|---------------------------------|-----------------------| +| MBS Session Association Information Item | | 1.. | | | +| >MBS QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.24 | | +| >Associated Unicast QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.24 | | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows in a PDU Session. Value is 64. | + +### 9.3.1.142 MT-SDT Information + +This IE provides the assistant information for MT-SDT. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|---------------------------|--------------------------------------------------------------------------------------------------------------------------| +| MT-SDT Data Size | M | | INTEGER
(1..96000,...) | Indicates the total data size for all SDT bearers. Unit: byte. Corresponds to the SDAP SDU size of the received DL data. | + +### 9.3.1.143 PDU Set QoS Parameters + +This IE defines PDU Set QoS parameters to be applied to a QoS flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|-------|------------------------------------------|-----------------------------------------------------------------------------| +| PDU Set Delay Budget | O | | Extended Packet Delay Budget
9.3.1.79 | The PDU Set Delay Budget is specified in TS 23.501 [20]. | +| PDU Set Error Rate | O | | Packet Error Rate
9.3.1.48 | The PDU Set Error Rate is specified in TS 23.501 [20]. | +| PDU Set Integrated Handling Information | O | | ENUMERATED
(true, false, ...) | The PDU Set Integrated Handling Information is specified in TS 23.501 [20]. | + +### 9.3.1.144 N6 Jitter Information + +This IE defines the jitter information associated with the Periodicity in downlink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|------------------------------|-----------------------------------------------------------------| +| N6 Jitter Lower Bound | M | | INTEGER (-127..
127, ...) | Indicates the lower bound of the N6 jitter. The unit is: 0.5ms. | +| N6 Jitter Upper Bound | M | | INTEGER (-127.. | Indicates the upper | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|------------------------------------------------| +| | | | 127, ...) | bound of the N6 jitter.
The unit is: 0.5ms. | + +### 9.3.1.145 ECN Marking or Congestion Information Reporting Request + +This IE indicates the gNB-CU-UP to perform ECN marking or to report information for ECN marking or to report congestion information for a QoS flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------------------|----------|-------|--------------------------------------|-----------------------| +| CHOICE ECN Marking or Congestion Information Request | M | | | | +| > ECN Marking at RAN | | | | | +| >>ECN Marking at NG-RAN Request | M | | ENUMERATED (ul, dl, both, stop, ...) | | +| > ECN Marking at UPF | | | | | +| >>ECN Marking at UPF Request | M | | ENUMERATED (ul, dl, both, stop, ...) | | +| > Congestion Information | | | | | +| >>Congestion Information Request | M | | ENUMERATED (ul, dl, both, stop, ...) | | + +## 9.3.2 Transport Network Layer Related IEs + +### 9.3.2.1 UP Transport Layer Information + +The *UP Transport Layer Information* IE identifies an transport bearer associated to a DRB. It contains a Transport Layer Address and a GTP Tunnel Endpoint Identifier. The Transport Layer Address is an IP address to be used for the user plane transport. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Transport Layer Information | M | | | | +| > GTP Tunnel | | | | | +| >>Transport Layer Address | M | | 9.3.2.4 | | +| >>GTP-TEID | M | | 9.3.2.3 | | + +### 9.3.2.2 CP Transport Layer Information + +This IE is used to provide the E1 control plane transport layer information associated with an gNB-CU-CP and gNB-CU-UP pair. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE CP Transport Layer Information | | | | | | | +| > Endpoint-IP-address | | | | | - | - | +| >> Endpoint IP | M | | Transport Layer | | - | - | + +| | | | | | | | +|-----------------------------------|---|--|---------------------------------------|--|-----|--------| +| address | | | Address
9.3.2.4 | | | | +| >Endpoint-IP-
address-and-port | | | | | YES | reject | +| >>Endpoint IP
address | M | | Transport Layer
Address
9.3.2.4 | | - | - | +| >>Port Number | M | | BIT STRING
(SIZE(16)) | | - | - | + +### 9.3.2.3 GTP-TEID + +The *GTP-TEID* IE is the GTP Tunnel Endpoint Identifier to be used for the user plane transport. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|--------------------------------------------| +| GTP-TEID | M | | OCTET STRING
(SIZE(4)) | For details and range, see TS 29.281 [15]. | + +### 9.3.2.4 Transport Layer Address + +This *Transport Layer Address* IE is an IP address. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transport Layer Address | M | | BIT STRING
(SIZE(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, see TS 38.414 [16]. | + +### 9.3.2.5 Data Forwarding Information Request + +This IE offers the possibility for the gNB-CU-CP to request data forwarding addresses to the gNB-CU-UP. It also offers the possibility for the gNB-CU-CP to provide a list of QoS flows subject to PDU Session level or DRB level data forwarding to the gNB to which DRBs or QoS flows have been offloaded. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------|----------|-------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Data Forwarding Request | M | | ENUMERATED (UL, DL, both, ...) | | +| QoS Flows forwarded on the forwarding tunnel(s) | O | | QoS Flow Mapping List
9.3.1.59 | This IE contains information for which QoS flows forwarded data packets are sent on:
- either the PDU Session forwarding tunnel (UL and DL)
- or the DRB forwarding tunnel (UL and DL). | + +### 9.3.2.6 Data Forwarding Information + +This IE provides the data forwarding information when performing handover or data offloading. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|----------------------|----------------------------------------|---------------------------------------------------------------------------|-------------|----------------------| +| UL Data Forwarding | O | | UP Transport Layer Information 9.3.2.1 | | - | - | +| DL Data Forwarding | O | | UP Transport Layer Information 9.3.2.1 | | - | - | +| Data Forwarding to NG-RAN QoS Flow Information List | | 0..1 | | Providing QoS flows accepted for data forwarding to the source gNB-CU-UP. | YES | ignore | +| >Data Forwarding to NG-RAN QoS Flow Information List Item | | 1.. | | | - | - | +| >>QoS Flow Identifier | M | | QoS Flow Identifier 9.3.1.24 | | - | - | +| PDU Set based Handling Indicator | O | | ENUMERATED (supported, ...) | Indicates the support of PDU Set based QoS handling. | YES | ignore | + +### 9.3.2.7 Transport Network Layer Address Info + +This IE is used for signalling TNL address information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------------|----------|---------------------|---------------------------------|-----------------------------------------------------| +| Transport UP Layer Addresses Info to Add List | | 0..1 | | | +| >Transport UP Layer Addresses Info to Add Item | | 1.. | | | +| >>IPsec Transport Layer Address | M | | Transport Layer Address 9.3.2.4 | Transport Network Layer address for IPsec endpoint. | +| >>>GTP Transport Layer Addresses To Add List | | 0..1 | | | +| >>>>GTP Transport Layer Addresses To Add Item | | 1.. | | | +| >>>>>GTP Transport Layer Address Info | M | | Transport Layer Address 9.3.2.4 | GTP Transport Layer Addresses for GTP end-points. | +| Transport UP Layer Addresses Info to Remove List | | 0..1 | | | +| >Transport UP Layer Addresses Info to Remove Item | | 1.. | | | +| >>IPsec Transport Layer Address | M | | Transport Layer | Transport Network Layer | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------------------------------|----------|---------------------|------------------------------------|---------------------------------------------------| +| | | | Address
9.3.2.4 | address for IPsec endpoint. | +| >>GTP Transport Layer Addresses To Remove List | | 0..1 | | | +| >>>GTP Transport Layer Addresses To Remove Item | | 1.. | | | +| >>>>GTP Transport Layer Address Info | M | | Transport Layer Address
9.3.2.4 | GTP Transport Layer Addresses for GTP end-points. | + +| Range bound | Explanation | +|----------------|-----------------------------------------------------------------------------------------------| +| maxnoofTLAs | Maximum no. of Transport Layer Addresses in the message. Value is 16. | +| maxnoofGTPTLAs | Maximum no. of GTP Transport Layer Addresses for a GTP end-point in the message. Value is 16. | + +### 9.3.2.8 URI + +This IE is defined to contain a URI address. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------| +| URI | M | | VisibleString | String representing URI (Uniform Resource Identifier) | + +## 9.3.3 Container and List IE definitions + +### 9.3.3.1 DRB To Setup List E-UTRAN + +This IE contains DRB related information used at Bearer Context Setup Request in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|------------------|-------------------------------------------|-------------------------------------------------------|-------------|----------------------| +| DRB To Setup Item E-UTRAN | | 1.. | | | - | - | +| >DRB ID | M | | 9.3.1.16 | | - | - | +| >PDCP Configuration | M | | 9.3.1.38 | | - | - | +| >E-UTRAN QoS | M | | 9.3.1.17 | | - | - | +| >S1 UL UP Transport Layer Information | M | | UP Transport Layer Information
9.3.2.1 | | - | - | +| >Data Forwarding Information Request | O | | 9.3.2.5 | Requesting forwarding info from the target gNB-CU-UP. | - | - | +| >Cell Group Information | M | | 9.3.1.11 | | - | - | +| >DL UP Parameters | O | | UP Parameters
9.3.1.13 | | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|-------|----------------------------------------|-------------------------------------------------------------------------|-------------|----------------------| +| >DRB Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to DRB. | - | - | +| >Existing Allocated S1 DL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | This IE is not used in this version of the specification. | - | - | +| >Data Forwarding Source IP Address | O | | Transport Layer Address 9.3.2.4 | Identifies the TNL address used by the source node for data forwarding. | YES | ignore | +| >Security Indication | O | | 9.3.1.23 | | YES | reject | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.2 PDU Session Resource To Setup List + +This IE contains PDU session resource related information used at Bearer Context Setup Request + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|--------------------------------|---------------------------------------------|------------------------------------------------------------------------------|-------------|----------------------| +| PDU Session Resource To Setup Item | | 1.. | | | - | - | +| >PDU Session ID | M | | 9.3.1.21 | | - | - | +| >PDU Session Type | M | | 9.3.1.22 | | - | - | +| >S-NSSAI | M | | 9.3.1.9 | | - | - | +| >Security Indication | M | | 9.3.1.23 | | - | - | +| >PDU Session Resource DL Aggregate Maximum Bit Rate | O | | Bit Rate 9.3.1.20 | This IE shall be present when at least one Non-GBR QoS Flows is being setup. | - | - | +| >NG UL UP Transport Layer Information | M | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >PDU Session Data Forwarding Information Request | O | | Data Forwarding Information Request 9.3.2.5 | | - | - | +| >PDU Session Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to PDU Session. | - | - | +| >Existing Allocated NG DL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------------------|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >Network Instance | O | | 9.3.1.62 | This IE is ignored if the Common Network Instance IE is included. | YES | ignore | +| >Common Network Instance | O | | 9.3.1.66 | | YES | ignore | +| >DRB To Setup List | | 1 | | | - | - | +| >>DRB To Setup Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>SDAP Configuration | M | | 9.3.1.39 | | - | - | +| >>>PDCP Configuration | M | | 9.3.1.38 | | - | - | +| >>>Cell Group Information | M | | 9.3.1.11 | | - | - | +| >>>QoS Flows Information To Be Setup | M | | QoS Flow QoS Parameters List 9.3.1.25 | | - | - | +| >>>DRB Data forwarding information Request | O | | Data Forwarding Information Request 9.3.2.5 | Requesting forwarding info from the target gNB-CU-UP. | - | - | +| >>>DRB Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to DRB. | - | - | +| >>>PDCP SN Status Information | O | | 9.3.1.58 | Contains the PDCP SN Status at setup after Resume. | - | - | +| >>>DRB QoS | O | | 9.3.1.26 | Indicates the DRB QoS when more than one QoS Flow is mapped to the DRB. | YES | ignore | +| >>>DAPS Request Information | O | | 9.3.1.91 | | YES | ignore | +| >>>Ignore Mapping Rule Indication | O | | ENUMERATED (True, ...) | Included if the QoS flow mapping rule for the DRB has not been decided by gNB-CU-CP. | YES | reject | +| >>>QoS Flows Remapping | O | | ENUMERATED (update, source configuration, ...) | Indicates that the target gNB-CU-CP requests QoS flow remapping during an intra-system lossless handover as specified in TS 38.300 [4]. | YES | reject | +| >>>SDT Indicator Setup | O | | ENUMERATED (true, ...) | Indicates that the DRB is for SDT. | YES | reject | +| >>>SpecialTriggeringPurpose | O | | ENUMERATED (indirect-data- | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------|--------------------------------------------|-----------------------|-------------|----------------------| +| | | | forwarding, ...) | | | | +| >Redundant NG UL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | YES | ignore | +| >Redundant Common Network Instance | O | | Common Network Instance 9.3.1.66 | | YES | ignore | +| >Redundant PDU Session Information | O | | 9.3.1.80 | | YES | ignore | +| >SpecialTriggeringPurpose | O | | ENUMERATED (indirect-data-forwarding, ...) | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.3 DRB Setup List E-UTRAN + +This IE contains setup DRB related information at Bearer Context Setup Response in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|----------------------|----------------------------------------|-------------------------------------------------------------------------|-------------|----------------------| +| DRB Setup Item E-UTRAN | | 1..oofDRBs> | | | - | - | +| >DRB ID | M | | 9.3.1.16 | | - | - | +| >S1 DL UP Transport Layer Information | M | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >Data Forwarding Information Response | O | | Data Forwarding Information 9.3.2.6 | Providing forwarding info from the target gNB-CU-UP. | - | - | +| >UL UP Parameters | M | | UP Parameters 9.3.1.13 | | - | - | +| >S1 DL UP Unchanged | O | | ENUMERATED (True, ...) | This IE is not used in this version of the specification. | - | - | +| >Data Forwarding Source IP Address | O | | Transport Layer Address 9.3.2.4 | Identifies the TNL address used by the source node for data forwarding. | YES | ignore | +| >Security Result | O | | 9.3.1.52 | | YES | ignore | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.4 DRB Failed List E-UTRAN + +This IE contains failed to setup DRB related information at Bearer Context Setup Response in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|------------------|-----------------------|-----------------------| +| DRB Failed Item E-UTRAN | | 1.. | | | +| >DRB ID | M | | 9.3.1.16 | | +| >Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.5 PDU Session Resource Setup List + +This IE contains setup PDU session resource related information used at Bearer Context Setup Response + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|--------------------------------|----------------------------------------|------------------------------------------------------|-------------|----------------------| +| PDU Session Resource Setup Item | | 1.. | | | - | - | +| >PDU Session ID | M | | 9.3.1.21 | | - | - | +| >Security Result | O | | 9.3.1.52 | | - | - | +| >NG DL UP Transport Layer Information | M | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >PDU Session Data Forwarding Information Response | O | | Data Forwarding Information 9.3.2.6 | Providing forwarding info from the target gNB-CU-UP. | - | - | +| >NG DL UP Unchanged | O | | ENUMERATED (True, ...) | | - | - | +| >DRB Setup List | | 1 | | | - | - | +| >>DRB Setup Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>DRB Data forwarding information Response | O | | Data Forwarding Information 9.3.2.6 | Providing forwarding info from the target gNB-CU-UP. | - | - | +| >>>UL UP Parameters | M | | UP Parameters 9.3.1.13 | | - | - | +| >>>Flow Setup List | M | | QoS Flow List 9.3.1.12 | | - | - | +| >>>Flow Failed List | O | | Flow Failed List 9.3.1.45 | | - | - | +| >DRB Failed List | | 0.. 1 | | | - | - | +| >>DRB Failed Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>Cause | M | | 9.3.1.2 | | - | - | +| >Redundant NG DL UP Transport Layer Information | O | | UP Transport Layer Information | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | 9.3.2.1 | | | | +| >Used Redundant PDU Session Information | O | | 9.3.1.80 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.6 PDU Session Resource Failed List + +This IE contains failed PDU session resource related information used at Bearer Context Setup Response + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|--------------------------------|-----------------------|-----------------------| +| PDU Session Resource Failed Item | | 1.. | | | +| >PDU Session ID | M | | 9.3.1.21 | | +| >Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.7 DRB To Setup Modification List E-UTRAN + +This IE contains DRB to setup related information used at Bearer Context Modification Request in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|------------------|----------------------------------------|------------------------------------------------------------|-------------|----------------------| +| DRB To Setup Modification Item E-UTRAN | | 1.. | | | - | - | +| >DRB ID | M | | 9.3.1.16 | | - | - | +| >PDCP Configuration | M | | 9.3.1.38 | | - | - | +| >E-UTRAN QoS | M | | 9.3.1.17 | | - | - | +| >S1 UL UP Transport Layer Information | M | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >Data Forwarding Information Request | O | | 9.3.2.5 | Requesting forwarding info from the target gNB-CU-UP. | - | - | +| >Cell Group Information | M | | 9.3.1.11 | | - | - | +| >DL UP Parameters | O | | UP Parameters 9.3.1.13 | | - | - | +| >DRB Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to DRB. | - | - | +| >Security Indication | O | | 9.3.1.23 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|---------------------------------|-------------------------------------------------------------------------|-------------|----------------------| +| >Data Forwarding Source IP Address | O | | Transport Layer Address 9.3.2.4 | Identifies the TNL address used by the source node for data forwarding. | YES | ignore | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.8 DRB To Modify List E-UTRAN + +This IE contains DRB to modify related information used at Bearer Context Modification Request in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|------------------|----------------------------------------|---------------------------------------------------------------------------------------------| +| DRB To Modify Item E-UTRAN | | 1.. | | | +| >DRB ID | M | | 9.3.1.16 | | +| >PDCP Configuration | O | | 9.3.1.38 | | +| >E-UTRAN QoS | O | | 9.3.1.17 | | +| >S1 UL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | +| >Data Forwarding Information | O | | 9.3.2.6 | Providing forwarding info to the source gNB-CU-UP. | +| >PDCP SN Status Request | O | | ENUMERATED (requested, ...) | The gNB-CU-CP requests the gNB-CU-UP to provide the PDCP SN Status in the response message. | +| >PDCP SN Status Information | O | | 9.3.1.58 | Providing SN Status information to the target gNB-CU-UP. | +| >DL UP Parameters | O | | UP Parameters 9.3.1.13 | | +| >Cell Group To Add | O | | Cell Group Information 9.3.1.11 | | +| >Cell Group To Modify | O | | Cell Group Information 9.3.1.11 | | +| >Cell Group To Remove | O | | Cell Group Information 9.3.1.11 | | +| >DRB Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to DRB. | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.9 DRB To Remove List E-UTRAN + +This IE contains DRB to remove related information used at Bearer Context Modification Request in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|------------------|-----------------------|-----------------------| +| DRB To Remove Item E- | | 1.. | | | + +| | | | | | +|--------------|---|----------------|----------|--| +| UTRAN | | RBs> | | | +| >DRB ID | M | | 9.3.1.16 | | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.10 PDU Session Resource To Setup Modification List + +This IE contains PDU session resource to setup related information used at Bearer Context Modification Request + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------------|----------|----------------------------------------------|---------------------------------------------|--------------------------------------------------------------------|-------------|----------------------| +| PDU Session Resource To Setup Modification Item | | 1..<maxno ofPDUSessionResource> | | | - | - | +| >PDU Session ID | M | | 9.3.1.21 | | - | - | +| >PDU Session Type | M | | 9.3.1.22 | | - | - | +| >S-NSSAI | M | | 9.3.1.9 | | - | - | +| >Security Indication | M | | 9.3.1.23 | | - | - | +| >PDU Session Resource DL Aggregate Maximum Bit Rate | O | | Bit Rate 9.3.1.20 | This IE shall be present when Non-GBR QoS Flows are setting up. | - | - | +| >NG UL UP Transport Layer Information | M | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >PDU Session Data Forwarding Information Request | O | | Data Forwarding Information Request 9.3.2.5 | Requesting forwarding info from the target gNB-CU-UP. | - | - | +| >PDU Session Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to PDU Session. | - | - | +| >Network Instance | O | | 9.3.1.62 | | - | - | +| >Common Network Instance | O | | 9.3.1.66 | | YES | ignore | +| >DRB To Setup List | | 1 | | | - | - | +| >>DRB To Setup Item | | 1..<maxno ofDRBs> | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>SDAP Configuration | M | | 9.3.1.39 | | - | - | +| >>>PDCP Configuration | M | | 9.3.1.38 | | - | - | +| >>>Cell Group Information | M | | 9.3.1.11 | | - | - | +| >>>QoS Flows Information To Be Setup | M | | QoS Flow QoS Parameters List 9.3.1.25 | | - | - | +| >>>DRB Data forwarding | O | | Data Forwarding | Requesting forwarding info | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------|--------------------------------------------|--------------------------------------------------------------------------------------|-------------|----------------------| +| information Request | | | Information Request 9.3.2.5 | from the target gNB-CU-UP. | | | +| >>>DRB Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to DRB. | - | - | +| >>>PDCP SN Status Information | O | | 9.3.1.58 | Provides the PDCP SN Status at setup after Resume to the target gNB-CU-UP. | - | - | +| >>>DRB QoS | O | | 9.3.1.26 | Indicates the DRB QoS when more than one QoS Flow is mapped to the DRB | YES | ignore | +| >>>Ignore Mapping Rule Indication | O | | ENUMERATED (True, ...) | Included if the QoS flow mapping rule for the DRB has not been decided by gNB-CU-CP. | YES | reject | +| >>>DAPS Request Information | O | | 9.3.1.91 | This IE is not used in this version of the specification. | YES | ignore | +| >>>SDT Indicator Setup | O | | ENUMERATED (true, ...) | Indicates that the DRB is for SDT. | YES | reject | +| >>>SpecialTriggeringPurpose | O | | ENUMERATED (indirect-data-forwarding, ...) | | YES | ignore | +| >Redundant NG UL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | YES | ignore | +| >Redundant Common Network Instance | O | | Common Network Instance 9.3.1.66 | | YES | ignore | +| >SpecialTriggeringPurpose | O | | ENUMERATED (indirect-data-forwarding, ...) | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.11 PDU Session Resource To Modify List + +This IE contains PDU session resource to modify related information used at Bearer Context Modification Request + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------|----------|-----------------------------------------------|---------------------------------------------|--------------------------------------------------------------------------|-------------|----------------------| +| PDU Session Resource To Modify Item | | 1.. <maxno ofPDUSessionResource> | | | - | - | +| >PDU Session ID | M | | 9.3.1.21 | | - | - | +| >Security Indication | O | | 9.3.1.23 | This IE is not used in this release. | - | - | +| >PDU Session Resource DL Aggregate Maximum Bit Rate | O | | Bit Rate 9.3.1.20 | | - | - | +| >NG UL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >PDU Session Data Forwarding Information Request | O | | Data Forwarding Information Request 9.3.2.5 | Requesting forwarding information from the target gNB-CU-UP. | - | - | +| >PDU Session Data Forwarding Information | O | | Data Forwarding Information 9.3.2.6 | Providing forwarding information to the source gNB-CU-UP. | - | - | +| >PDU Session Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to PDU Session. | - | - | +| >Network Instance | O | | 9.3.1.62 | This IE is ignored if the Common Network Instance IE is included. | YES | ignore | +| >Common Network Instance | O | | 9.3.1.66 | | YES | ignore | +| >DRB To Setup List | | 0..1 | | | - | - | +| >>DRB To Setup Item | | 1.. <maxno ofDRBs> | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>SDAP Configuration | M | | 9.3.1.39 | | - | - | +| >>>PDCP Configuration | M | | 9.3.1.38 | | - | - | +| >>>Cell Group Information | M | | 9.3.1.11 | | - | - | +| >>>QoS Flow Information To Be Setup | M | | QoS Flow QoS Parameters List 9.3.1.25 | | - | - | +| >>>DRB Data Forwarding Information Request | O | | Data Forwarding Information Request 9.3.2.5 | Requesting forwarding information from the target gNB-CU-UP. | - | - | +| >>>DRB Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to DRB. | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------------------|------------------------------------------------|---------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>PDCP SN Status Information | O | | 9.3.1.58 | Provides the PDCP SN Status at setup after Resume to the target gNB-CU-UP. | - | - | +| >>>DRB QoS | O | | 9.3.1.26 | Indicates the DRB QoS when more than one QoS Flow is mapped to the DRB | YES | ignore | +| >>>DAPS Request Information | O | | 9.3.1.91 | This IE is not used in this version of the specification | YES | ignore | +| >>>Ignore Mapping Rule Indication | O | | ENUMERATED (True, ...) | Included if the QoS flow mapping rule for the DRB has not been decided by gNB-CU-CP. | YES | reject | +| >>>QoS Flows Remapping | O | | ENUMERATED (update, source configuration, ...) | This IE is not used in this version of the specification. | YES | reject | +| >>>SDT Indicator Setup | O | | ENUMERATED (true, ...) | Indicates that the DRB is for SDT. | YES | reject | +| >DRB To Modify List | | 0.. 1 | | | - | - | +| >>DRB To Modify Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>SDAP Configuration | O | | 9.3.1.39 | | - | - | +| >>>PDCP Configuration | O | | 9.3.1.38 | | - | - | +| >>>DRB Data forwarding information | O | | Data Forwarding Information 9.3.2.6 | Providing forwarding information to the source gNB-CU-UP. | - | - | +| >>>PDCP SN Status Request | O | | ENUMERATED (requested, ...) | The gNB-CU-CP requests the gNB-CU-UP to provide the PDCP SN Status in the response message. | - | - | +| >>>PDCP SN Status Information | O | | 9.3.1.58 | Provides the PDCP SN Status to the target gNB-CU-UP. | - | - | +| >>>DL UP Parameters | O | | UP Parameters 9.3.1.13 | | - | - | +| >>>Cell Group To Add | O | | Cell Group Information 9.3.1.11 | | - | - | +| >>>Cell Group To Modify | O | | Cell Group Information | | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|-------------------|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | 9.3.1.11 | | | | +| >>>Cell Group To Remove | O | | Cell Group Information 9.3.1.11 | | - | - | +| >>>Flow Mapping Information | O | | QoS Flow QoS Parameters List 9.3.1.25 | Overrides previous mapping information. | - | - | +| >>>DRB Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | Included if the Activity Notification Level is set to DRB. | - | - | +| >>>Old QoS Flow List - UL End Marker expected | O | | QoS Flow List 9.3.1.12 | Indicates that the source NG-RAN node has initiated QoS flow re-mapping and has not yet received SDAP end markers, as described in TS 38.300 [8]. | YES | reject | +| >>>DRB QoS | O | | 9.3.1.26 | Indicates the DRB QoS when more than one QoS Flow is mapped to the DRB | YES | ignore | +| >>>Early Forwarding COUNT Request | O | | ENUMERATED (First DL count, DL discarding, ...) | Requests early data forwarding information from the source gNB-CU-UP | YES | reject | +| >>>Early Forwarding COUNT Information | O | | 9.3.1.92 | Provides early data forwarding information to the target gNB-CU-UP. | YES | reject | +| >>>DAPS Request Information | O | | 9.3.1.91 | Used to request intra-gNB-CU-UP DAPS HO | YES | ignore | +| >>>Early Data Forwarding Indicator | O | | ENUMERATED (stop, ...) | | YES | ignore | +| >>>SDT Indicator Modify | O | | ENUMERATED (true, false, ...) | Indicates that the DRB is for SDT or not. | YES | reject | +| >>>PDCP COUNT Reset | O | | ENUMERATED (True, ...) | Used for intra-gNB-CU-UP HO with full configuration | YES | reject | +| >DRB To Remove List | | 0.. 1 | | | - | - | +| >>DRB To Remove Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >S-NSSAI | O | | 9.3.1.9 | | YES | reject | +| >Redundant NG UL | O | | UP Transport | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|--------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| UP Transport Layer Information | | | Layer Information 9.3.2.1 | | | | +| >Redundant Common Network Instance | O | | Common Network Instance 9.3.1.66 | | YES | ignore | +| >Data Forwarding to E-UTRAN Information List | | 0..1 | | Contains a list of DL Data Forwarding tunnels and the associated QoS Flows to be forwarded on each tunnel | YES | ignore | +| >>Data Forwarding to E-UTRAN Information List Item | | 1.. | | | - | - | +| >>>Data forwarding tunnel information | M | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >>>QoS Flows to be forwarded List | | 1 | | | - | - | +| >>>>QoS Flows to be forwarded Item | | 1.. | | | - | - | +| >>>>>QoS Flow Identifier | M | | QoS Flow Identifier 9.3.1.24 | | - | - | +| >Security Indication Modify | O | | Security Indication 9.3.1.23 | | YES | ignore | +| >Secondary PDU Session Data Forwarding Information | O | | Data Forwarding Information 9.3.2.6 | Providing secondary forwarding information to the source gNB-CU-UP in case of split PDU session. | YES | ignore | + +| Range bound | Explanation | +|--------------------------------------|---------------------------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | +| maxnoofDataForwardingTunneltoE-UTRAN | Maximum no. of Data Forwarding Tunnels to E-UTRAN for a UE. Value is 256. | +| maxnoofQoSflows | Maximum no. of QoS flows in a PDU Session. Value is 64. | + +### 9.3.3.12 PDU Session Resource To Remove List + +This IE contains PDU session resource to remove related information + +| IE/Group Name | Presence | Range | IE type and | Semantics | Criticality | Assigned | +|---------------|----------|-------|-------------|-----------|-------------|----------| +|---------------|----------|-------|-------------|-----------|-------------|----------| + +| | | | reference | description | | Criticality | +|--------------------------------------------|---|---------------------------------|-----------|-------------|-----|-------------| +| PDU Session Resource To Remove Item | | 1.. | | | - | - | +| >PDU Session ID | M | | 9.3.1.21 | | - | - | +| >Cause | O | | 9.3.1.2 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.13 DRB Setup Modification List E-UTRAN + +This IE contains setup DRB related information at Bearer Context Modification Response in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------------------|----------------------------------------|-------------------------------------------------------------------------|-------------|----------------------| +| DRB Setup Modification Item E-UTRAN | | 1.. | | | - | - | +| >DRB ID | M | | 9.3.1.16 | | - | - | +| >S1 DL UP Transport Layer Information | M | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >Data Forwarding Information Response | O | | 9.3.2.6 | Provides forwarding information from the target gNB-CU-UP. | - | - | +| >UL UP Parameters | M | | UP Parameters 9.3.1.13 | | - | - | +| >Security Result | O | | 9.3.1.52 | | YES | ignore | +| >Data Forwarding Source IP Address | O | | Transport Layer Address 9.3.2.4 | Identifies the TNL address used by the source node for data forwarding. | YES | ignore | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.14 DRB Failed Modification List E-UTRAN + +This IE contains failed to setup DRB related information at Bearer Context Modification Response in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|------------------|-----------------------|-----------------------| +| DRB Failed Modification Item E-UTRAN | | 1.. | | | +| >DRB ID | M | | 9.3.1.16 | | +| >Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.15 DRB Modified List E-UTRAN + +This IE contains modified DRB related information at Bearer Context Modification Response in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|------------------|----------------------------------------|--------------------------------------------------------| +| DRB Modified Item E-UTRAN | | 1.. | | | +| >DRB ID | M | | 9.3.1.16 | | +| >S1 DL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | +| >PDCP SN Status Information | O | | 9.3.1.58 | Provides the PDCP SN Status from the source gNB-CU-UP. | +| >UL UP Parameters | O | | UP Parameters 9.3.1.13 | Carries the UL UP parameters. | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.16 DRB Failed To Modify List E-UTRAN + +This IE contains failed to modify DRB related information at Bearer Context Modification Response in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|------------------|-----------------------|-----------------------| +| DRB Failed To Modify Item E-UTRAN | | 1.. | | | +| >DRB ID | M | | 9.3.1.16 | | +| >Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.17 PDU Session Resource Setup Modification List + +This IE contains setup PDU session resource related information used at Bearer Context Modification Response + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------|----------|--------------------------------|----------------------------------------|-----------------------|-------------|----------------------| +| PDU Session Resource Setup Modification Item | | 1.. | | | - | - | +| >PDU Session ID | M | | 9.3.1.21 | | - | - | +| >Security Result | O | | 9.3.1.52 | | - | - | +| >NG DL UP Transport Layer Information | M | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >PDU Session Data | O | | Data | Provides | - | - | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------------------|----------------------------------------|------------------------------------------------------------|-------------|----------------------| +| Forwarding Information Response | | | Forwarding Information 9.3.2.6 | forwarding information from the target gNB-CU-UP. | | | +| >DRB Setup List | | 1 | | | - | - | +| >>DRB Setup Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>DRB Data forwarding information Response | O | | Data Forwarding Information 9.3.2.6 | Provides forwarding information from the target gNB-CU-UP. | - | - | +| >>>UL UP Parameters | M | | UP Parameters 9.3.1.13 | | - | - | +| >>>Flow Setup List | M | | QoS Flow List 9.3.1.12 | | - | - | +| >>>Flow Failed List | O | | Flow Failed List 9.3.1.45 | | - | - | +| >DRB Failed List | | 0.. 1 | | | - | - | +| >>DRB Failed Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>Cause | M | | 9.3.1.2 | | - | - | +| >Redundant NG DL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.18 PDU Session Resource Failed Modification List + +This IE contains failed to setup PDU session resource related information used at Bearer Context Modification Response + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------------------|----------|--------------------------------|-----------------------|-----------------------| +| PDU Session Resource Failed Modification Item | | 1.. | | | +| >PDU Session ID | M | | 9.3.1.21 | | +| >Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.19 PDU Session Resource Modified List + +This IE contains modified PDU session resource related information used at Bearer Context Modification Response + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|---------------------------------|----------------------------------------|-----------------------------------------------------------------------|-------------|----------------------| +| PDU Session Resource Modified Item | | 1.. | | | - | | +| >PDU Session ID | M | | 9.3.1.21 | | - | | +| >NG DL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | - | | +| >Security Result | O | | 9.3.1.52 | | - | | +| >PDU Session Data Forwarding Information Response | O | | Data Forwarding Information 9.3.2.6 | | - | | +| >DRB Setup List | | 0.. 1 | | | - | | +| >>DRB Setup Item | | 1.. | | | - | | +| >>>DRB ID | M | | 9.3.1.16 | | - | | +| >>>DRB Data forwarding information Response | O | | Data Forwarding Information 9.3.2.6 | | - | | +| >>>UL UP Parameters | M | | UP Parameters 9.3.1.13 | | - | | +| >>>Flow Setup List | M | | QoS Flow List 9.3.1.12 | | - | | +| >>>Flow Failed List | O | | Flow Failed List 9.3.1.45 | | - | | +| >DRB Failed List | | 0.. 1 | | | - | | +| >>DRB Failed Item | | 1.. | | | - | | +| >>>DRB ID | M | | 9.3.1.16 | | - | | +| >>>Cause | M | | 9.3.1.2 | | - | | +| >DRB Modified List | | 0.. 1 | | | - | | +| >>DRB Modified Item | | 1.. | | | - | | +| >>>DRB ID | M | | 9.3.1.16 | | - | | +| >>>UL UP Parameters | O | | UP Parameters 9.3.1.13 | Carries the UL UP parameters. | - | | +| >>>PDCP SN Status Information | O | | 9.3.1.58 | Provides PDCP SN Status to the target gNB-CU-UP. | - | | +| >>>Flow Setup List | O | | QoS Flow List 9.3.1.12 | | - | | +| >>>Flow Failed List | O | | Flow Failed List 9.3.1.45 | | - | | +| >>>Early Forwarding COUNT Information | O | | 9.3.1.92 | Provides early data forwarding information from the source gNB-CU-UP. | - | | +| >>> Old QoS Flow List - UL End Marker expected | O | | QoS Flow List 9.3.1.12 | Indicates the QoS flow(s) for which the gNB-CU-UP has not yet | Yes | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|------------------|----------------------------------------|----------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | received SDAP end markers after the gNB-CU-CP reconfigured those QoS flow(s) to another DRB. | | | +| >DRB Failed To Modify List | | 0.. 1 | | | - | - | +| >>DRB Failed To Modify Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>Cause | M | | 9.3.1.2 | | - | - | +| >Redundant NG DL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.20 PDU Session Resource Failed To Modify List + +This IE contains failed to modify PDU session resource related information used at Bearer Context Modification Response + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------------|----------|--------------------------------|-----------------------|-----------------------| +| PDU Session Resource Failed To Modify Item | | 1.. | | | +| >PDU Session ID | M | | 9.3.1.21 | | +| >Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.21 DRB Required To Modify List E-UTRAN + +This IE contains DRB to modify related information used at Bearer Context Modification Required in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|------------------|----------------------------------------|-----------------------| +| DRB Required To Modify Item E-UTRAN | | 1.. | | | +| >DRB ID | M | | 9.3.1.16 | | +| >S1 DL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | +| >gNB-CU-UP Cell Group Related Configuration | O | | 9.3.1.34 | | +| >Cause | O | | 9.3.1.2 | | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.22 DRB Required To Remove List E-UTRAN + +This IE contains DRB to remove related information used at Bearer Context Modification Required in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|------------------|-----------------------|-----------------------| +| DRB Required To Remove Item E-UTRAN | | 1.. | | | +| >DRB ID | M | | 9.3.1.16 | | +| >Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.23 PDU Session Resource Required To Modify List + +This IE contains PDU session resource to modify related information used at Bearer Context Modification Required + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------|----------|--------------------------------|----------------------------------------|-----------------------|-------------|----------------------| +| PDU Session Resource Required To Modify Item | | 1.. | | | - | - | +| >PDU Session ID | M | | 9.3.1.21 | | - | - | +| >NG DL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | - | - | +| >DRB To Modify List | | 0..1 | | | - | - | +| >>DRB To Modify Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>gNB-CU-UP Cell Group Related Configuration | O | | 9.3.1.34 | | - | - | +| >>>Flow To Remove | O | | QoS Flow List 9.3.1.12 | | - | - | +| >>>Cause | O | | 9.3.1.2 | | - | - | +| >DRB To Remove List | | 0..1 | | | - | - | +| >>DRB To Remove Item | | 1.. | | | - | - | +| >>>DRB ID | M | | 9.3.1.16 | | - | - | +| >>>Cause | M | | 9.3.1.2 | | - | - | +| >Redundant NG DL UP Transport Layer Information | O | | UP Transport Layer Information 9.3.2.1 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.24 DRB Confirm Modified List E-UTRAN + +This IE contains modified DRB related information at Bearer Context Modification Confirm in E-UTRAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DRB Confirm Modified Item E-UTRAN | | 1.. | | | +| >DRB ID | M | | 9.3.1.16 | | +| >Cell Group Information | O | | 9.3.1.11 | Included if the gNB-CU-CP was unable to change cell group related information as requested in the gNB-CU-UP Cell Group Related Configuration IE (e.g., UL Configuration). | + +| Range bound | Explanation | +|-------------|--------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | + +### 9.3.3.25 PDU Session Resource Confirm Modified List + +This IE contains modified PDU session resource related information used at Bearer Context Modification Confirm + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|--------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDU Session Resource Modified Item | | 1.. | | | +| >PDU Session ID | M | | 9.3.1.21 | | +| >DRB Modified List | | 0.. 1 | | | +| >>DRB Modified Item | | 1.. | | | +| >>>DRB ID | M | | 9.3.1.16 | | +| >>>Cell Group Information | O | | 9.3.1.11 | Included if the gNB-CU-CP was unable to change cell group related information as requested in the gNB-CU-UP Cell Group Related Configuration IE (e.g., UL Configuration). | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs for a UE. Value is 32. | +| maxnoofPDUSessionResource | Maximum no. of PDU Sessions for a UE. Value is 256. | + +### 9.3.3.26 BC Bearer Context To Setup + +This IE contains MBS session resource related information used to request BC Bearer Context Context Setup. + +| IE/Group Name | Presence | Range | IE type and | Semantics description | +|---------------|----------|-------|-------------|-----------------------| +|---------------|----------|-------|-------------|-----------------------| + +| | | | reference | | +|--------------------------------------------------------------|---|--|--------------------------------------------|--| +| S-NSSAI | M | | 9.3.1.9 | | +| BC Bearer Context NG-U
TNL Info at 5GC | O | | 9.3.1.112 | | +| BC MRB To Setup List | M | | BC MRB Setup
Configuration
9.3.1.114 | | +| Requested Action for
Available Shared NG-U
Termination | O | | 9.3.1.115 | | + +### 9.3.3.27 BC Bearer Context To Setup Response + +This IE contains MBS session resource related information used to confirm BC Bearer Context Setup. + +| IE/Group Name | Presence | Range | IE type and
reference | Semantics description | +|----------------------------------------------|----------|----------------------|--------------------------------------------|-----------------------| +| BC Bearer Context NG-U
TNL Info at NG-RAN | O | | 9.3.1.116 | | +| BC MRB Setup Response
List | | 1..RBs> | | | +| >MRB ID | M | | 9.3.1.16a | | +| >MBS QoS Flow Setup
List | M | | QoS Flow List
9.3.1.12 | | +| >MBS QoS Flow Failed
List | O | | Flow Failed List
9.3.1.45 | | +| >BC Bearer Context F1-U
TNL Info at CU | M | | 9.3.1.118 | | +| BC MRB Failed List | | 0..RBs> | | | +| >MRB ID | M | | 9.3.1.16a | | +| >Cause | M | | 9.3.1.2 | | +| Available BC MRB
Configuration | O | | BC MRB Setup
Configuration
9.3.1.114 | | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +### 9.3.3.28 BC Bearer Context To Modify + +This IE contains MBS session resource related information used to request BC Bearer Context Modification. + +| IE/Group Name | Presence | Range | IE type and
reference | Semantics
description | Criticality | Assigned
Criticality | +|-----------------------------------------------------------------|----------|----------------------|-----------------------------------------------------------|--------------------------|-------------|-------------------------| +| BC Bearer Context NG-U
TNL Info at 5GC To
Setup or Modify | O | | BC Bearer
Context NG-U
TNL Info at 5GC
9.3.1.112 | | - | | +| BC MRB To Setup List | O | | BC MRB Setup
Configuration
9.3.1.114 | | - | | +| BC MRB To Modify
List | | 0..ofMRBs> | | | - | | +| >MRB ID | M | | 9.3.1.16a | | - | | + +| | | | | | | | +|----------------------------------------|---|------------------|----------------------------------------|-------------------------------------------------------------------------|-----|--------| +| >BC Bearer Context F1-U TNL Info at DU | O | | 9.3.1.119 | | - | | +| >MBS PDCP Configuration | O | | PDCP Configuration 9.3.1.38 | | - | | +| >MBS QoS Flows Information To Be Setup | O | | QoS Flow QoS Parameters List 9.3.1.25 | | - | | +| >MRB QoS | O | | QoS Flow Level QoS Parameters 9.3.1.26 | Indicates the MRB QoS when more than one QoS Flow is mapped to the MRB. | - | | +| BC MRB To Remove List | | 0.. | | | - | | +| >MRB ID | M | | 9.3.1.16a | | - | | +| F1-U tunnel Not Established | O | | ENUMERATED (true, ...) | Indicates to not establish F1-U tunnel for this MBS broadcast session. | YES | ignore | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +### 9.3.3.29 BC Bearer Context To Modify Response + +This IE contains MBS session resource related information used to confirm a BC Bearer Context Modification. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|------------------|--------------------------------------|------------------------------------------------------------------------------------| +| BC Bearer Context NG-U TNL Info at NG-RAN | O | | 9.3.1.116 | | +| BC MRB Setup or Modify Response List | | 1.. | | | +| >MRB ID | M | | 9.3.1.16a | | +| >MBS QoS Flow Setup List | O | | QoS Flow List 9.3.1.12 | | +| >MBS QoS Flow Failed List | O | | Flow Failed List 9.3.1.45 | | +| >BC Bearer Context F1-U TNL Info at CU | O | | 9.3.1.118 | | +| BC MRB Failed List | | 0.. | | | +| >MRB ID | M | | 9.3.1.16a | | +| >Cause | M | | 9.3.1.2 | | +| Available BC MRB Configuration | O | | BC MRB Setup Configuration 9.3.1.114 | In case the shared MBS NG-U termination had a different MRB Configuration applied. | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +### 9.3.3.30 BC Bearer Context To Modify Required + +This IE contains MBS session resource related information used to request BC Bearer Context Modification. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------------------------------|-----------------------|-----------------------| +| BC MRB To Remove List Required | | 0..<maxnoofMRBs> | | | +| >MRB ID | M | | 9.3.1.16a | | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +### 9.3.3.31 BC Bearer Context To Modify Confirm + +This IE contains MBS session resource related information used to confirm a BC Bearer Context Modification. + +NOTE: In the current version of this specification, this IE does not contain any information. + +### 9.3.3.32 MC Bearer Context To Setup + +This IE contains MBS session resource related information used to request MC Bearer Context Context Setup. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Criticality | +|-----------------------------------------------------------|----------|-------|--------------------------------------|-----------------------|-------------|-------------| +| S-NSSAI | M | | 9.3.1.9 | | - | - | +| MC MRB To Setup List | O | | MC MRB Setup Configuration 9.3.1.120 | | - | - | +| Requested Action for Available Shared NG-U Termination | O | | 9.3.1.115 | | - | - | +| MBS Session Associated Information Non-Support-to-Support | O | | 9.3.1.140 | | YES | ignore | +| MBS Area Session ID | O | | 9.3.1.111 | | YES | ignore | +| MC Bearer Context Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | | YES | ignore | +| MC Bearer Context Status Change | O | | ENUMERATED (Suspend, Resume, ...) | | YES | ignore | + +### 9.3.3.33 MC Bearer Context To Setup Response + +This IE contains MBS session resource related information used to confirm MC Bearer Context Context Setup. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|-------------------------------|---------------------------|-----------------------| +| MC Bearer Context NG-U TNL Info at NG-RAN | O | | 9.3.1.121 | | +| MC MRB Setup Response List | | 0..<maxnoofMRBs> | | | +| >MRB ID | M | | 9.3.1.16a | | +| >MBS QoS Flow Setup List | M | | QoS Flow List 9.3.1.12 | | +| >MBS QoS Flow Failed List | O | | Flow Failed List 9.3.1.45 | | + +| | | | | | +|--------------------------------|---|-------------------------------|--------------------------------------|--| +| >MBS PDCP COUNT | O | | 9.3.1.35a | | +| MC MRB Failed List | | 0..<maxnoofMRBs> | | | +| >MRB ID | M | | 9.3.1.16a | | +| >Cause | M | | 9.3.1.2 | | +| Available MC MRB Configuration | O | | MC MRB Setup Configuration 9.3.1.120 | | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +### 9.3.3.34 MC Bearer Context To Modify + +This IE contains MBS session resource related information used to request a modification of a multicast MC Bearer Context. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------------|---------------------|-------------------------------|----------------------------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| MC Bearer Context NG-U TNL Info at 5GC | O | | 9.3.1.122 | | - | | +| MC Bearer Context NG-U TNL Info at NG-RAN Request | O | | 9.3.1.123 | To request NG-U TNL information from the gNB-CU-UP, if not yet available at gNB-CU-CP | - | | +| MBS Multicast F1-U Context Descriptor | C- ifSetupOr Remove | | 9.3.1.125 | | - | | +| Requested Action for Available Shared NG-U Termination | O | | 9.3.1.115 | | - | | +| MC MRB To Setup or Modify List | | 0..<maxnoofMRBs> | | | - | | +| >MRB ID | M | | 9.3.1.16a | | - | | +| >MC Bearer Context F1-U TNL Info at DU | O | | 9.3.1.124 | | - | | +| >MBS PDCP Configuration | O | | PDCP Configuration 9.3.1.38 | | - | | +| >MBS QoS Flows Information To Be Setup | O | | QoS Flow QoS Parameters List 9.3.1.25 | | - | | +| >MRB QoS | O | | QoS Flow Level QoS Parameters 9.3.1.26 | Indicates the MRB QoS when more than one QoS Flow is mapped to the MRB. | - | | +| >MBS PDCP COUNT Request | O | | ENUMERATED (true, ...) | Indicates that the MBS PDCP COUNT is requested. | - | | +| MC MRB To Remove List | | 0..<maxnoofMRBs> | | | - | | +| >MRB ID | M | | 9.3.1.16a | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|-------|-----------------------------------|------------------------------------------------------------------------|-------------|----------------------| +| MC Forwarding Resource Request | O | | 9.3.1.134 | Requests MC Forwarding Resource related information for the peer node | YES | ignore | +| MC Forwarding Resource Indication | O | | 9.3.1.135 | Provides MC Forwarding Resource related information from the peer node | YES | ignore | +| MC Forwarding Resource Release | O | | 9.3.1.137 | Requests the release of the MC Forwarding Resource | YES | ignore | +| MBS Session Associated Information Non-Support-to-Support | O | | 9.3.1.140 | | YES | ignore | +| MC Bearer Context Inactivity Timer | O | | Inactivity Timer 9.3.1.54 | | YES | ignore | +| MC Bearer Context Status Change | O | | ENUMERATED (Suspend, Resume, ...) | | YES | ignore | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +| Condition | Explanation | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| ifSetupOrRemove | This IE shall be present if either the MC MRB To Setup or Modify List IE or the MC MRB To Remove List IE or both IEs are included. | + +### 9.3.3.35 MC Bearer Context To Modify Response + +This IE contains MBS session resource related information used to confirm a MC Bearer Context Modification. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|---------------------|-------------------|----------------------------------------|-----------------------|-------------|----------------------| +| MC Bearer Context NG-U TNL Info at NG-RAN Modify Response | O | | 9.3.1.127 | | - | | +| MBS Multicast F1-U Context Descriptor | C- ifSetupOr Failed | | 9.3.1.125 | | - | | +| MC MRB Setup or Modify Response List | | 0.. | | | - | | +| >MRB ID | M | | 9.3.1.16a | | - | | +| >MBS QoS Flow Setup List | O | | QoS Flow List 9.3.1.12 | | - | | +| >MBS QoS Flow Failed List | O | | Flow Failed List 9.3.1.45 | | - | | +| >MC Bearer Context F1-U TNL Info at CU | O | | UP Transport Layer Information 9.3.2.1 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|--------------------------------|--------------------------------------|------------------------------------------------------------------------------------|-------------|----------------------| +| >MBS PDCP COUNT | O | | 9.3.1.35a | | - | | +| MC MRB Failed List | | 0..<maxno ofMRBs> | | | - | | +| >MRB ID | M | | 9.3.1.16a | | - | | +| >Cause | M | | 9.3.1.2 | | - | | +| Available MC MRB Configuration | O | | MC MRB Setup Configuration 9.3.1.120 | In case the shared MBS NG-U termination had a different MRB Configuration applied. | - | | +| MC Forwarding Resource Response | O | | 9.3.1.136 | Provides MC Forwarding Resource related information destined to the peer node | YES | ignore | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +| Condition | Explanation | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| ifSetupOrFailed | This IE shall be present if either the MC MRB Setup or Modify Response List IE or the MC MRB Failed List IE or both IEs are included. | + +### 9.3.3.36 MC Bearer Context To Modify Required + +This IE contains MBS session resource related information used to request MC Bearer Context Modification. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|-----------------|--------------------------------|-----------------------|----------------------------------------------------|-------------|----------------------| +| MBS Multicast F1-U Context Descriptor | C-
ifRemoved | | 9.3.1.125 | | - | | +| MC MRB To Remove List Required | | 0..<maxno ofMRBs> | | | - | | +| >MRB ID | M | | 9.3.1.16a | | - | | +| MC MRB To Modify List Required | | 0..<maxno ofMRBs> | | | - | | +| >MRB ID | M | | 9.3.1.16a | | - | | +| > MBS PDCP COUNT | O | | 9.3.1.35a | | - | | +| MC Forwarding Resource Release Indication | O | | 9.3.1.138 | Indicates the release of an MC Forwarding Resource | YES | ignore | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +| Condition | Explanation | +|-----------|----------------------------------------------------------------------------------------------| +| ifRemove | This IE shall be present if either the MC MRB To Remove List Required IE is included. | + +### 9.3.3.37 MC Bearer Context To Modify Confirm + +This IE contains MBS session resource related information used to confirm a MC Bearer Context Modification. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|------------------|-----------------------|-----------------------| +| MBS Multicast F1-U Context Descriptor | O | | 9.3.1.125 | | +| MC MRB Modify List Required | | 0.. | | | +| >MRB ID | M | | 9.3.1.16a | | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRBs for one MBS Session. Value is 32. | + +### 9.3.3.38 Associated Session ID + +This IE is used to associate MBS Session IDs providing identical user data. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Associated Session ID | M | | OCTET STRING | Coded as AssociatedSessionId defined in TS 29.571 [35]. The gNB-CU-UP does not interpret the content of the Associated Session ID IE. | + +### 9.3.3.39 MBS Service Area + +This IE contains the MBS service area. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------------------------------|----------|-------------------------------------|-----------------------|-----------------------| +| CHOICE Session Type | M | | | | +| >location dependent | | | | | +| >>MBS Service Area Information Location Dependent List | | 1..maxnoofMBSServiceAreaInformation | | | +| >>>MBS Area Session ID | M | | 9.3.1.111 | | +| >>>MBS Service Area Information | M | | 9.3.3.40 | | + +| Range bound | Explanation | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| maxnoofMBSServiceAreaInformation | Maximum no. of MBS Service Area Information elements in the MBS Service Area Information Location Dependent List IE. Value is 256 | + +### 9.3.3.40 MBS Service Area information + +This IE contains MBS service area information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|--------------------------------------|-----------------------|-----------------------| +| MBS Service Area Cell List | | 0..<maxnoofCellsforMBS> | | | +| >NR CGI | M | | 9.3.1.14 | | +| MBS Service Area TAI List | | 0..<maxnoofTAIforMBS> | | | +| >PLMN-Identity | M | | 9.3.1.7 | | +| >5GS TAC | M | | 9.3.3.41 | | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------------| +| maxnoofCellsforMBS | Maximum no. of cells allowed within one MBS Service Area. Value is 512. | +| maxnoofTAIforMBS | Maximum no. of TAs allowed within one MBS Service Area. Value is 512. | + +### 9.3.3.41 5GS TAC + +This information element is used to identify Tracking Area Code. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------|-----------------------| +| 5GS TAC | M | | OCTET STRING (SIZE (3)) | | + +## 9.4 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.4.1 General + +EIAP ASN.1 definition conforms to ITU-T Rec. X.691 [7], ITU-T Rec. X.680 [8] and ITU-T Rec. X.681 [9]. + +The ASN.1 definition specifies the structure and content of EIAP messages. EIAP 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 an EIAP 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: In the above "IE" means an IE in the object set with an explicit ID. If one IE needs to appear more than once in one object set, then the different occurrences will have different IE IDs. + +If an EIAP 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 clause 10. + +## 9.4.2 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.4.3 Elementary Procedure Definitions + +``` + +-- ASN1START + +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +ELAP-PDU-Descriptions { + + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + + ngran-access (22) modules (3) elap (5) version1 (1) elap-PDU-Descriptions (0) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules +-- +-- ***** + +``` + +## IMPORTS + +Criticality, +ProcedureCode + +## FROM E1AP-CommonDataTypes + +Reset, +ResetAcknowledge, +ErrorIndication, +GNB-CU-UP-E1SetupRequest, +GNB-CU-UP-E1SetupResponse, +GNB-CU-UP-E1SetupFailure, +GNB-CU-CP-E1SetupRequest, +GNB-CU-CP-E1SetupResponse, +GNB-CU-CP-E1SetupFailure, +GNB-CU-UP-ConfigurationUpdate, +GNB-CU-UP-ConfigurationUpdateAcknowledge, +GNB-CU-UP-ConfigurationUpdateFailure, +GNB-CU-CP-ConfigurationUpdate, +GNB-CU-CP-ConfigurationUpdateAcknowledge, +GNB-CU-CP-ConfigurationUpdateFailure, +BCBearerContextSetupRequest, +BCBearerContextSetupResponse, +BCBearerContextSetupFailure, + +BCBearerContextModificationRequest, +BCBearerContextModificationResponse, +BCBearerContextModificationFailure, +BCBearerContextModificationRequired, +BCBearerContextModificationConfirm, +BCBearerContextReleaseCommand, +BCBearerContextReleaseComplete, +BCBearerContextReleaseRequest, +BearerContextSetupRequest, +BearerContextSetupResponse, +BearerContextSetupFailure, +BearerContextModificationRequest, +BearerContextModificationResponse, +BearerContextModificationFailure, +BearerContextModificationRequired, +BearerContextModificationConfirm, +BearerContextReleaseCommand, +BearerContextReleaseComplete, +BearerContextReleaseRequest, +BearerContextInactivityNotification, +DLDataNotification, +ULDataNotification, +DataUsageReport, + +ElReleaseRequest, +ElReleaseResponse, +GNB-CU-UP-CounterCheckRequest, +GNB-CU-UP-StatusIndication, +MCBearerContextSetupRequest, +MCBearerContextSetupResponse, +MCBearerContextSetupFailure, +MCBearerContextModificationRequest, +MCBearerContextModificationResponse, +MCBearerContextModificationFailure, +MCBearerContextModificationRequired, +MCBearerContextModificationConfirm, +MCBearerNotification, +MCBearerContextReleaseCommand, +MCBearerContextReleaseComplete, +MCBearerContextReleaseRequest, +MRDC-DataUsageReport, +DeactivateTrace, +TraceStart, +PrivateMessage, +ResourceStatusRequest, +ResourceStatusResponse, +ResourceStatusFailure, + +ResourceStatusUpdate, +IAB-UPTNAddressUpdate, +IAB-UPTNAddressUpdateAcknowledge, +IAB-UPTNAddressUpdateFailure, +CellTrafficTrace, +EarlyForwardingSNTransfer, +GNB-CU-CPMeasurementResultsInformation, +IABPSKNotification + +FROM E1AP-PDU-Contents + +id-reset, +id-errorIndication, +id-gNB-CU-UP-E1Setup, +id-gNB-CU-CP-E1Setup, +id-gNB-CU-UP-ConfigurationUpdate, +id-gNB-CU-CP-ConfigurationUpdate, +id-e1Release, +id-bearerContextSetup, +id-bearerContextModification, +id-bearerContextModificationRequired, +id-bearerContextRelease, +id-bearerContextReleaseRequest, +id-bearerContextInactivityNotification, + +id-dLDataNotification, +id-uLDataNotification, +id-dataUsageReport, +id-gNB-CU-UP-CounterCheck, +id-gNB-CU-UP-StatusIndication, +id-mRDC-DataUsageReport, +id-DeactivateTrace, +id-TraceStart, +id-privateMessage, +id-resourceStatusReportingInitiation, +id-resourceStatusReporting, +id-iAB-UPTNLAddressUpdate, +id-CellTrafficTrace, +id-earlyForwardingSNTransfer, +id-gNB-CU-CPMeasurementResultsInformation, +id-iABPSKNotification, +id-BCBearerContextSetup, +id-BCBearerContextModification, +id-BCBearerContextModificationRequired, +id-BCBearerContextRelease, +id-BCBearerContextReleaseRequest, +id-MCBearerContextSetup, +id-MCBearerContextModification, + +``` + id-MCBearerContextModificationRequired, + id-MCBearerNotification, + id-MCBearerContextRelease, + id-MCBearerContextReleaseRequest + +FROM E1AP-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +E1AP-ELEMENTARY-PROCEDURE ::= CLASS { + &InitiatingMessage , + &SuccessfulOutcome OPTIONAL, + +&UnsuccessfulOutcome OPTIONAL, + &procedureCode ProcedureCode UNIQUE, + &criticality Criticality DEFAULT ignore +} + +WITH SYNTAX { + INITIATING MESSAGE &InitiatingMessage + [SUCCESSFUL OUTCOME &SuccessfulOutcome] +``` + +``` +[UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] +PROCEDURE CODE &procedureCode +[CRITICALITY &criticality] +} + +-- ***** +-- +-- Interface PDU Definition +-- +-- ***** + +E1AP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode E1AP-ELEMENTARY-PROCEDURE.&procedureCode ({E1AP-ELEMENTARY-PROCEDURES}), + criticality E1AP-ELEMENTARY-PROCEDURE.&criticality ({E1AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value E1AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({E1AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { +``` + +``` + + procedureCode E1AP-ELEMENTARY-PROCEDURE.&procedureCode ({E1AP-ELEMENTARY-PROCEDURES}), + criticality E1AP-ELEMENTARY-PROCEDURE.&criticality ({E1AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value E1AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({E1AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +``` + +``` + +UnsuccessfulOutcome := SEQUENCE { + procedureCode E1AP-ELEMENTARY-PROCEDURE.&procedureCode ({E1AP-ELEMENTARY-PROCEDURES}), + criticality E1AP-ELEMENTARY-PROCEDURE.&criticality ({E1AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value E1AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({E1AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +``` + +``` + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +``` + +``` + +E1AP-ELEMENTARY-PROCEDURES E1AP-ELEMENTARY-PROCEDURE ::= { + E1AP-ELEMENTARY-PROCEDURES-CLASS-1 | + E1AP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +``` + +``` + +E1AP-ELEMENTARY-PROCEDURES-CLASS-1 E1AP-ELEMENTARY-PROCEDURE ::= { + +``` + +``` + reset | + gNB-CU-UP-ElSetup | + gNB-CU-CP-ElSetup | + gNB-CU-UP-ConfigurationUpdate | + gNB-CU-CP-ConfigurationUpdate | + e1Release | + bearerContextSetup | + bearerContextModification | + bearerContextModificationRequired | + bearerContextRelease | + resourceStatusReportingInitiation | + iAB-UPTNLAddressUpdate | + bCBearerContextSetup | + bCBearerContextModification | + bCBearerContextModificationRequired | + bCBearerContextRelease | + mCBearerContextSetup | + mCBearerContextModification | + mCBearerContextModificationRequired | + mCBearerContextRelease | + ... | +} +``` + +``` +E1AP-ELEMENTARY-PROCEDURES-CLASS-2 E1AP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + + errorIndication | + bearerContextReleaseRequest | + bearerContextInactivityNotification | + dLDataNotification | + ULDataNotification | + dataUsageReport | + gNB-CU-UP-CounterCheck | + gNB-CU-UP-StatusIndication | + mRDC-DataUsageReport | + deactivateTrace | + traceStart | + privateMessage | + cellTrafficTrace | + resourceStatusReporting | + earlyForwardingSNTransfer | + gNB-CU-CPMeasurementResultsInformation | + iABPSKNotification | + bCBearerContextReleaseRequest | + mCBearerContextReleaseRequest | + mCBearerNotification , + ... +} + +``` + +``` + +-- ***** +-- + +``` + +``` +-- Interface Elementary Procedures +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +reset ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Reset + SUCCESSFUL OUTCOME ResetAcknowledge + PROCEDURE CODE id-reset + CRITICALITY reject +} +``` + +``` +errorIndication ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication + PROCEDURE CODE id-errorIndication + CRITICALITY ignore +} +``` + +``` +gNB-CU-UP-ElSetup ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNB-CU-UP-ElSetupRequest + SUCCESSFUL OUTCOME GNB-CU-UP-ElSetupResponse + UNSUCCESSFUL OUTCOME GNB-CU-UP-ElSetupFailure + PROCEDURE CODE id-gNB-CU-UP-ElSetup + CRITICALITY reject +} +``` + +``` +gNB-CU-CP-ElSetup E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNB-CU-CP-ElSetupRequest + SUCCESSFUL OUTCOME GNB-CU-CP-ElSetupResponse + UNSUCCESSFUL OUTCOME GNB-CU-CP-ElSetupFailure + PROCEDURE CODE id-gNB-CU-CP-ElSetup + CRITICALITY reject +} + +gNB-CU-UP-ConfigurationUpdate E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNB-CU-UP-ConfigurationUpdate + SUCCESSFUL OUTCOME GNB-CU-UP-ConfigurationUpdateAcknowledge + UNSUCCESSFUL OUTCOME GNB-CU-UP-ConfigurationUpdateFailure + PROCEDURE CODE id-gNB-CU-UP-ConfigurationUpdate + CRITICALITY reject +} + +gNB-CU-CP-ConfigurationUpdate E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNB-CU-CP-ConfigurationUpdate + SUCCESSFUL OUTCOME GNB-CU-CP-ConfigurationUpdateAcknowledge + UNSUCCESSFUL OUTCOME GNB-CU-CP-ConfigurationUpdateFailure + PROCEDURE CODE id-gNB-CU-CP-ConfigurationUpdate + CRITICALITY reject +} + +e1Release E1AP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE E1ReleaseRequest + SUCCESSFUL OUTCOME E1ReleaseResponse + PROCEDURE CODE id-e1Release + CRITICALITY reject +} + +bearerContextSetup E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BearerContextSetupRequest + SUCCESSFUL OUTCOME BearerContextSetupResponse + UNSUCCESSFUL OUTCOME BearerContextSetupFailure + PROCEDURE CODE id-bearerContextSetup + CRITICALITY reject +} + +bearerContextModification E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BearerContextModificationRequest + SUCCESSFUL OUTCOME BearerContextModificationResponse + UNSUCCESSFUL OUTCOME BearerContextModificationFailure + PROCEDURE CODE id-bearerContextModification + CRITICALITY reject +} + +bearerContextModificationRequired E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BearerContextModificationRequired + SUCCESSFUL OUTCOME BearerContextModificationConfirm +} +``` + +``` + PROCEDURE CODE id-bearerContextModificationRequired + CRITICALITY reject +} + +bearerContextRelease E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BearerContextReleaseCommand + SUCCESSFUL OUTCOME BearerContextReleaseComplete + PROCEDURE CODE id-bearerContextRelease + CRITICALITY reject +} + +bearerContextReleaseRequest E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BearerContextReleaseRequest + PROCEDURE CODE id-bearerContextReleaseRequest + CRITICALITY ignore +} + +bearerContextInactivityNotification E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BearerContextInactivityNotification + PROCEDURE CODE id-bearerContextInactivityNotification + CRITICALITY ignore +} + +dLDataNotification E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DLDataNotification +} +``` + +``` +PROCEDURE CODE id-dLDataNotification +CRITICALITY ignore +} + +uLDataNotification ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ULDataNotification + PROCEDURE CODE id-uLDataNotification + CRITICALITY ignore +} + +dataUsageReport ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DataUsageReport + PROCEDURE CODE id-dataUsageReport + CRITICALITY ignore +} + +gNB-CU-UP-CounterCheck ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNB-CU-UP-CounterCheckRequest + PROCEDURE CODE id-gNB-CU-UP-CounterCheck + CRITICALITY ignore +} + +gNB-CU-UP-StatusIndication ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNB-CU-UP-StatusIndication + PROCEDURE CODE id-gNB-CU-UP-StatusIndication +``` + +``` + CRITICALITY ignore + +} + +privateMessage E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + PROCEDURE CODE id-privateMessage + CRITICALITY ignore +} + +gNB-CU-CPMeasurementResultsInformation E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNB-CU-CPMeasurementResultsInformation + PROCEDURE CODE id-gNB-CU-CPMeasurementResultsInformation + CRITICALITY ignore +} + +mRDC-DataUsageReport E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MRDC-DataUsageReport + PROCEDURE CODE id-mRDC-DataUsageReport + CRITICALITY ignore +} + +deactivateTrace E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DeactivateTrace + PROCEDURE CODE id-DeactivateTrace +} +``` + +``` + CRITICALITY ignore + + } + + traceStart ELAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE TraceStart + + PROCEDURE CODE id-TraceStart + + CRITICALITY ignore + + } + + resourceStatusReportingInitiation ELAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE ResourceStatusRequest + + SUCCESSFUL OUTCOME ResourceStatusResponse + + UNSUCCESSFUL OUTCOME ResourceStatusFailure + + PROCEDURE CODE id-resourceStatusReportingInitiation + + CRITICALITY reject + + } + + resourceStatusReporting ELAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE ResourceStatusUpdate + + PROCEDURE CODE id-resourceStatusReporting + + CRITICALITY ignore + + } +``` + +``` +iAB-UPTNLAddressUpdate E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE IAB-UPTNLAddressUpdate + SUCCESSFUL OUTCOME IAB-UPTNLAddressUpdateAcknowledge + UNSUCCESSFUL OUTCOME IAB-UPTNLAddressUpdateFailure + PROCEDURE CODE id-iAB-UPTNLAddressUpdate + CRITICALITY reject +} +``` + +``` +cellTrafficTrace E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellTrafficTrace + PROCEDURE CODE id-CellTrafficTrace + CRITICALITY ignore +} +``` + +``` +earlyForwardingSNTransfer E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE EarlyForwardingSNTransfer + PROCEDURE CODE id-earlyForwardingSNTransfer + CRITICALITY ignore +} +``` + +``` +iABPSKNotification E1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE IABPSKNotification + PROCEDURE CODE id-iABPSKNotification +} +``` + +``` + CRITICALITY reject + +} + +bCBearerContextSetup ELAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE BCBearerContextSetupRequest + + SUCCESSFUL OUTCOME BCBearerContextSetupResponse + + UNSUCCESSFUL OUTCOME BCBearerContextSetupFailure + + PROCEDURE CODE id-BCBearerContextSetup + + CRITICALITY reject + +} + +bCBearerContextModification ELAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE BCBearerContextModificationRequest + + SUCCESSFUL OUTCOME BCBearerContextModificationResponse + + UNSUCCESSFUL OUTCOME BCBearerContextModificationFailure + + PROCEDURE CODE id-BCBearerContextModification + + CRITICALITY reject + +} + +bCBearerContextModificationRequired ELAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE BCBearerContextModificationRequired + + SUCCESSFUL OUTCOME BCBearerContextModificationConfirm + + PROCEDURE CODE id-BCBearerContextModificationRequired +``` + +``` + CRITICALITY reject + + } + + bCBearerContextRelease EIAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE BCBearerContextReleaseCommand + + SUCCESSFUL OUTCOME BCBearerContextReleaseComplete + + PROCEDURE CODE id-BCBearerContextRelease + + CRITICALITY reject + + } + + bCBearerContextReleaseRequest EIAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE BCBearerContextReleaseRequest + + PROCEDURE CODE id-BCBearerContextReleaseRequest + + CRITICALITY reject + + } + + mCBearerContextSetup EIAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE MCBearerContextSetupRequest + + SUCCESSFUL OUTCOME MCBearerContextSetupResponse + + UNSUCCESSFUL OUTCOME MCBearerContextSetupFailure + + PROCEDURE CODE id-MCBearerContextSetup + + CRITICALITY reject + + } +``` + +``` +mCBearerContextModification ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE mCBearerContextModificationRequest + SUCCESSFUL OUTCOME mCBearerContextModificationResponse + UNSUCCESSFUL OUTCOME mCBearerContextModificationFailure + PROCEDURE CODE id-mCBearerContextModification + CRITICALITY reject +} + +mCBearerContextModificationRequired ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE mCBearerContextModificationRequired + SUCCESSFUL OUTCOME mCBearerContextModificationConfirm + PROCEDURE CODE id-mCBearerContextModificationRequired + CRITICALITY reject +} + +mCBearerNotification ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE mCBearerNotification + PROCEDURE CODE id-mCBearerNotification + CRITICALITY reject +} + +mCBearerContextRelease ELAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + +INITIATING MESSAGE MCBearerContextReleaseCommand +SUCCESSFUL OUTCOME MCBearerContextReleaseComplete +PROCEDURE CODE id-MCBearerContextRelease +CRITICALITY reject +} + +mCBearerContextReleaseRequest ELAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MCBearerContextReleaseRequest + PROCEDURE CODE id-MCBearerContextReleaseRequest + CRITICALITY reject +} + +END + +-- ASN1STOP + +``` + +### 9.4.4 PDU Definitions + +``` + +-- ASN1START + +-- ***** +-- +-- PDU definitions for ELAP +-- +-- ***** + +``` + +``` +E1AP-PDU-Contents { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + ngran-access (22) modules (3) elap (5) version1 (1) elap-PDU-Contents (1) } + + DEFINITIONS AUTOMATIC TAGS ::= + + BEGIN + + -- ***** + -- + -- IE parameter types from other modules + -- + -- ***** + + IMPORTS + + AssociatedSessionID, + Cause, + CriticalityDiagnostics, + GNB-CU-CP-MBS-E1AP-ID, + GNB-CU-UP-MBS-E1AP-ID, + GNB-CU-CP-UE-E1AP-ID, + GNB-CU-UP-UE-E1AP-ID, + UE-associatedLogicalE1-ConnectionItem, + GNB-CU-UP-ID, +``` + +GNB-CU-UP-Name, +Extended-GNB-CU-UP-Name, +GNB-CU-CP-Name, +Extended-GNB-CU-CP-Name, +CNSupport, +PLMN-Identity, +Slice-Support-List, +NR-CGI-Support-List, +QoS-Parameters-Support-List, +SecurityInformation, +BitRate, +BearerContextStatusChange, +DRB-To-Setup-List-EUTRAN, +DRB-Setup-List-EUTRAN, +DRB-Failed-List-EUTRAN, +DRB-To-Modify-List-EUTRAN, +DRB-Measurement-Results-Information-List, +DRB-Modified-List-EUTRAN, +DRB-Failed-To-Modify-List-EUTRAN, +DRB-To-Remove-List-EUTRAN, +DRB-Required-To-Remove-List-EUTRAN, +DRB-Required-To-Modify-List-EUTRAN, +DRB-Confirm-Modified-List-EUTRAN, +DRB-To-Setup-Mod-List-EUTRAN, +DRB-Setup-Mod-List-EUTRAN, + +DRB-Failed-Mod-List-EUTRAN, +ExtendedSliceSupportList, +PDU-Session-Resource-To-Setup-List, +PDU-Session-Resource-Setup-List, +PDU-Session-Resource-Failed-List, +PDU-Session-Resource-To-Modify-List, +PDU-Session-Resource-Modified-List, +PDU-Session-Resource-Failed-To-Modify-List, +PDU-Session-Resource-To-Remove-List, +PDU-Session-Resource-Required-To-Modify-List, +PDU-Session-Resource-Confirm-Modified-List, +PDU-Session-Resource-To-Setup-Mod-List, +PDU-Session-Resource-Setup-Mod-List, +PDU-Session-Resource-Failed-Mod-List, +PDU-Session-To-Notify-List, +DRB-Status-Item, +DRB-Activity-Item, +Data-Usage-Report-List, +TimeToWait, +ActivityNotificationLevel, +ActivityInformation, +New-UL-TNL-Information-Required, +GNB-CU-CP-TNLA-Setup-Item, +GNB-CU-CP-TNLA-Failed-To-Setup-Item, +GNB-CU-CP-TNLA-To-Add-Item, + +GNB-CU-CP-TNLA-To-Remove-Item, +GNB-CU-CP-TNLA-To-Update-Item, +GNB-CU-UP-TNLA-To-Remove-Item, +TransactionID, +Inactivity-Timer, +DRBs-Subject-To-Counter-Check-List-EUTRAN, +DRBs-Subject-To-Counter-Check-List-NG-RAN, +PFI, +GNB-CU-UP-Capacity, +GNB-CU-UP-OverloadInformation, +DataDiscardRequired, +PDU-Session-Resource-Data-Usage-List, +RANUEID, +GNB-DU-ID, +TraceID, +TraceActivation, +SubscriberProfileIDforRFP, +AdditionalRRMPriorityIndex, +RetainabilityMeasurementsInfo, +Transport-Layer-Address-Info, +HW-CapacityIndicator, +RegistrationRequest, +ReportCharacteristics, +ReportingPeriodicity, +TNL-AvailableCapacityIndicator, + +DLUPTNLAddressToUpdateItem, +ULUPTNLAddressToUpdateItem, +NPNContextInfo, +NPNSupportInfo, +MDTPLMNList, +PrivacyIndicator, +URIaddress, +DRBs-Subject-To-Early-Forwarding-List, +CHOInitiation, +ExtendedSliceSupportList, +TransportLayerAddress, +AdditionalHandoverInfo, +Extended-NR-CGI-Support-List, +DirectForwardingPathAvailability, +IAB-Donor-CU-UPPSKInfo-Item, +ECGI-Support-List, +MDTPollutedMeasurementIndicator, +UESliceMaximumBitRateList, +SCGActivationStatus, +GlobalMBSSessionID, +BCBearerContextToSetup, +BCBearerContextToSetupResponse, +BCBearerContextToModify, +BCBearerContextToModifyResponse, +BCBearerContextToModifyRequired, + +BCBearerContextToModifyConfirm, +MCBearerContextToSetup, +MCBearerContextToSetupResponse, +MCBearerContextToModify, +MCBearerContextToModifyResponse, +MCBearerContextToModifyRequired, +MCBearerContextToModifyConfirm, +MBSMulticastFlUContextDescriptor, +MBS-ServiceArea, +GNB-CU-UP-MBS-Support-Info, +SDTContinueROHC, +MDTPLMNModificationList, +InactivityInformationRequest, +UEInactivityInformation, +MBSSessionResourceNotification, +MT-SDT-Information, +MT-SDT-Information-Request, +SDT-data-size-threshold, +SDT-data-size-threshold-Crossed + +FROM E1AP-IEs + +``` +PrivateIE-Container{}, +ProtocolExtensionContainer{}, +ProtocolIE-Container{}, +ProtocolIE-ContainerList{}, +ProtocolIE-SingleContainer{}, +E1AP-PRIVATE-IES, +E1AP-PROTOCOL-EXTENSION, +E1AP-PROTOCOL-IES +``` + +``` +FROM E1AP-Containers +``` + +``` +id-AssociatedSessionID, +id-Cause, +id-CriticalityDiagnostics, +id-gNB-CU-CP-UE-E1AP-ID, +id-gNB-CU-UP-UE-E1AP-ID, +id-ResetType, +id-UE-associatedLogicalE1-ConnectionItem, +id-UE-associatedLogicalE1-ConnectionListResAck, +id-gNB-CU-UP-ID, +id-gNB-CU-UP-Name, +id-Extended-GNB-CU-UP-Name, +id-gNB-CU-CP-Name, +id-Extended-GNB-CU-CP-Name, +``` + +id-CNSupport, +id-SupportedPLMNs, +id-NPNSupportInfo, +id-NPNContextInfo, +id-SecurityInformation, +id-UEDLAggregateMaximumBitRate, +id-BearerContextStatusChange, +id-System-BearerContextSetupRequest, +id-System-BearerContextSetupResponse, +id-System-BearerContextModificationRequest, +id-System-BearerContextModificationResponse, +id-System-BearerContextModificationConfirm, +id-System-BearerContextModificationRequired, +id-DRB-Status-List, +id-Data-Usage-Report-List, +id-TimeToWait, +id-ActivityNotificationLevel, +id-ActivityInformation, +id-New-UL-TNL-Information-Required, +id-GNB-CU-CP-TNLA-Setup-List, +id-GNB-CU-CP-TNLA-Failed-To-Setup-List, +id-GNB-CU-CP-TNLA-To-Add-List, +id-GNB-CU-CP-TNLA-To-Remove-List, +id-GNB-CU-CP-TNLA-To-Update-List, +id-GNB-CU-UP-TNLA-To-Remove-List, + +id-DRB-To-Setup-List-EUTRAN, +id-DRB-To-Modify-List-EUTRAN, +id-DRB-To-Remove-List-EUTRAN, +id-DRB-Required-To-Modify-List-EUTRAN, +id-DRB-Required-To-Remove-List-EUTRAN, +id-DRB-Setup-List-EUTRAN, +id-DRB-Failed-List-EUTRAN, +id-DRB-Measurement-Results-Information-List, +id-DRB-Modified-List-EUTRAN, +id-DRB-Failed-To-Modify-List-EUTRAN, +id-DRB-Confirm-Modified-List-EUTRAN, +id-DRB-To-Setup-Mod-List-EUTRAN, +id-DRB-Setup-Mod-List-EUTRAN, +id-DRB-Failed-Mod-List-EUTRAN, +id-PDU-Session-Resource-To-Setup-List, +id-PDU-Session-Resource-To-Modify-List, +id-PDU-Session-Resource-To-Remove-List, +id-PDU-Session-Resource-Required-To-Modify-List, +id-PDU-Session-Resource-Setup-List, +id-PDU-Session-Resource-Failed-List, +id-PDU-Session-Resource-Modified-List, +id-PDU-Session-Resource-Failed-To-Modify-List, +id-PDU-Session-Resource-Confirm-Modified-List, +id-PDU-Session-Resource-Setup-Mod-List, +id-PDU-Session-Resource-Failed-Mod-List, + +id-PDU-Session-Resource-To-Setup-Mod-List, +id-PDU-Session-To-Notify-List, +id-TransactionID, +id-Serving-PLMN, +id-UE-Inactivity-Timer, +id-System-GNB-CU-UP-CounterCheckRequest, +id-DRBs-Subject-To-Counter-Check-List-EUTRAN, +id-DRBs-Subject-To-Counter-Check-List-NG-RAN, +id-PPI, +id-gNB-CU-UP-Capacity, +id-GNB-CU-UP-OverloadInformation, +id-UEDLMaximumIntegrityProtectedDataRate, +id-DataDiscardRequired, +id-PDU-Session-Resource-Data-Usage-List, +id-RANUEID, +id-GNB-DU-ID, +id-TraceID, +id-TraceActivation, +id-SubscriberProfileIDforRFP, +id-AdditionalRRMPriorityIndex, +id-RetainabilityMeasurementsInfo, +id-Transport-Layer-Address-Info, +id-gNB-CU-CP-Measurement-ID, +id-gNB-CU-UP-Measurement-ID, +id-RegistrationRequest, + +id-ReportCharacteristics, +id-ReportingPeriodicity, +id-TNL-AvailableCapacityIndicator, +id-HW-CapacityIndicator, +id-DLUPTNLAddressToUpdateList, +id-ULUPTNLAddressToUpdateList, +id-ManagementBasedMDTPLMNList, +id-TraceCollectionEntityIPAddress, +id-PrivacyIndicator, +id-URIaddress, +id-DRBs-Subject-To-Early-Forwarding-List, +id-CHOInitiation, +id-ExtendedSliceSupportList, +id-AdditionalHandoverInfo, +id-Extended-NR-CGI-Support-List, +id-DirectForwardingPathAvailability, id-IAB-Donor-CU-UPPSKInfo, +id-ECGI-Support-List, +id-MDTPollutedMeasurementIndicator, +id-UESliceMaximumBitRateList, +id-SCGActivationStatus, +id-GNB-CU-CP-MBS-E1AP-ID, +id-GNB-CU-UP-MBS-E1AP-ID, +id-GlobalMBSSessionID, +id-BCBearerContextToSetup, +id-BCBearerContextToSetupResponse, + +id-BCBearerContextToModify, +id-BCBearerContextToModifyResponse, +id-BCBearerContextToModifyRequired, +id-BCBearerContextToModifyConfirm, +id-MCBearerContextToSetup, +id-MCBearerContextToSetupResponse, +id-MCBearerContextToModify, +id-MCBearerContextToModifyResponse, +id-MCBearerContextToModifyRequired, +id-MCBearerContextToModifyConfirm, +id-MBSMulticastFluContextDescriptor, +id-gNB-CU-UP-MBS-Support-Info, +id-SDTContinueROHC, +id-ManagementBasedMDTPLMNModificationList, +id-MBS-ServiceArea, +id-InactivityInformationRequest, +id-UEInactivityInformation, +id-MBSSessionResourceNotification, +id-MT-SDT-Information, +id-MT-SDT-Information-Request, +id-SDT-data-size-threshold, +id-SDT-data-size-threshold-Crossed, +maxnoofErrors, +maxnoofSPLMNs, + +``` + +maxnoofDRBs, +maxnoofTNLAssociations, +maxnoofIndividualE1ConnectionsToReset, +maxnoofTNLAddresses, +maxnoofPSKs + +FROM E1AP-Constants; + +-- ***** +-- +-- RESET +-- +-- ***** + +-- ***** +-- +-- Reset +-- +-- ***** + +Reset ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ResetIEs} }, + ... +} + +``` + +``` +} + +ResetIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-ResetType CRITICALITY reject TYPE ResetType PRESENCE mandatory }, + ... +} + +ResetType ::= CHOICE { + e1-Interface ResetAll, + partOfE1-Interface UE-associatedLogicalE1-ConnectionListRes, + choice-extension ProtocolIE-SingleContainer {{ResetType-ExtIEs}} +} + +ResetType-ExtIEs E1AP-PROTOCOL-IES ::= { + ... +} + +ResetAll ::= ENUMERATED { + reset-all, + ... +} +``` + +``` +UE-associatedLogicalE1-ConnectionListRes ::= SEQUENCE (SIZE(1.. maxnoofIndividualE1ConnectionsToReset)) OF ProtocolIE-SingleContainer { { UE-associatedLogicalE1-ConnectionItemRes } } +``` + +``` +UE-associatedLogicalE1-ConnectionItemRes E1AP-PROTOCOL-IES ::= { +``` + +``` + { ID id-UE-associatedLogicalE1-ConnectionItem CRITICALITY reject TYPE UE-associatedLogicalE1-ConnectionItem PRESENCE mandatory}, + ... +} +``` + +``` +-- ***** +-- +-- Reset Acknowledge +-- +-- ***** +``` + +``` +ResetAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ResetAcknowledgeIEs} }, + ... +} +``` + +``` +ResetAcknowledgeIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | + { ID id-UE-associatedLogicalE1-ConnectionListResAck CRITICALITY ignore TYPE UE-associatedLogicalE1-ConnectionListResAck PRESENCE +optional } | +``` + +``` + + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +UE-associatedLogicalE1-ConnectionListResAck ::= SEQUENCE (SIZE(1.. maxnoofIndividualE1ConnectionsToReset)) OF ProtocolIE-SingleContainer { { UE- +associatedLogicalE1-ConnectionItemResAck } } + +UE-associatedLogicalE1-ConnectionItemResAck EIAP-PROTOCOL-IES ::= { + { ID id-UE-associatedLogicalE1-ConnectionItem CRITICALITY ignore TYPE UE-associatedLogicalE1-ConnectionItem PRESENCE mandatory }, + ... +} + +-- ***** +-- +-- ERROR INDICATION +-- +-- ***** + +ErrorIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ErrorIndication-IEs}}, + ... +} + +ErrorIndication-IEs EIAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY ignore TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE optional}| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY ignore TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE optional}| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}| + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY ignore TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE optional}| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY ignore TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE optional}, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- GNB-CU-UP E1 SETUP + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- GNB-CU-UP E1 Setup Request + +-- + +-- \*\*\*\*\* + +``` + +GNB-CU-UP-E1SetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-UP-E1SetupRequestIEs} }, + ... +} + +``` + +``` + +} + +GNB-CU-UP-ElSetupRequestIEs ELAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNB-CU-UP-ID CRITICALITY reject TYPE GNB-CU-UP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-Name CRITICALITY ignore TYPE GNB-CU-UP-Name PRESENCE optional }| + { ID id-CNSupport CRITICALITY reject TYPE CNSupport PRESENCE mandatory }| + { ID id-SupportedPLMNs CRITICALITY reject TYPE SupportedPLMNs-List PRESENCE mandatory }| + { ID id-gNB-CU-UP-Capacity CRITICALITY ignore TYPE GNB-CU-UP-Capacity PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-Extended-GNB-CU-UP-Name CRITICALITY ignore TYPE Extended-GNB-CU-UP-Name PRESENCE optional }| + { ID id-gNB-CU-UP-MBS-Support-Info CRITICALITY reject TYPE GNB-CU-UP-MBS-Support-Info PRESENCE optional }, + ... +} + +``` + +``` + +SupportedPLMNs-List ::= SEQUENCE (SIZE (1..maxnoofSPLMNs)) OF SupportedPLMNs-Item + +``` + +``` + +SupportedPLMNs-Item ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + slice-Support-List Slice-Support-List OPTIONAL, + nR-CGI-Support-List NR-CGI-Support-List OPTIONAL, + qos-Parameters-Support-List QoS-Parameters-Support-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SupportedPLMNs-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +SupportedPLMNs-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + { ID id-NPNSupportInfo CRITICALITY reject EXTENSION NPNSupportInfo PRESENCE optional}| + { ID id-ExtendedSliceSupportList CRITICALITY reject EXTENSION ExtendedSliceSupportList PRESENCE optional}| + { ID id-Extended-NR-CGI-Support-List CRITICALITY ignore EXTENSION Extended-NR-CGI-Support-List PRESENCE optional}| + { ID id-ECGI-Support-List CRITICALITY ignore EXTENSION ECGI-Support-List PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- GNB-CU-UP E1 Setup Response +-- +-- ***** + +``` + +``` + +GNB-CU-UP-E1SetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-UP-E1SetupResponseIEs} }, + ... +} + +``` + +``` + +GNB-CU-UP-E1SetupResponseIEs ELAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNB-CU-CP-Name CRITICALITY ignore TYPE GNB-CU-CP-Name PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-Extended-GNB-CU-CP-Name CRITICALITY ignore TYPE Extended-GNB-CU-CP-Name PRESENCE optional }| + +``` + +``` +{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, +... +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- GNB-CU-UP E1 Setup Failure +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +GNB-CU-UP-E1SetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-UP-E1SetupFailureIEs} }, + ... +} +``` + +``` +GNB-CU-UP-E1SetupFailureIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +-- GNB-CU-CP E1 SETUP + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- GNB-CU-CP E1 Setup Request + +-- + +-- \*\*\*\*\* + +GNB-CU-CP-E1SetupRequest ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container      { {GNB-CU-CP-E1SetupRequestIEs} }, + +    ... + +} + +GNB-CU-CP-E1SetupRequestIEs EIAP-PROTOCOL-IES ::= { + +    { ID id-TransactionID                          CRITICALITY reject  TYPE TransactionID                  PRESENCE mandatory  }| + +    { ID id-gNB-CU-CP-Name                          CRITICALITY ignore  TYPE GNB-CU-CP-Name                  PRESENCE optional }| + +    { ID id-Transport-Layer-Address-Info          CRITICALITY ignore  TYPE Transport-Layer-Address-Info  PRESENCE optional }| + +    { ID id-Extended-GNB-CU-CP-Name                CRITICALITY ignore  TYPE Extended-GNB-CU-CP-Name      PRESENCE optional }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- GNB-CU-CP E1 Setup Response + +-- + +-- \*\*\*\*\* + +``` + +GNB-CU-CP-E1SetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-CP-E1SetupResponseIEs} }, + ... +} + +``` + +``` + +GNB-CU-CP-E1SetupResponseIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNB-CU-UP-ID CRITICALITY reject TYPE GNB-CU-UP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-Name CRITICALITY ignore TYPE GNB-CU-UP-Name PRESENCE optional }| + { ID id-CNSupport CRITICALITY reject TYPE CNSupport PRESENCE mandatory }| + { ID id-SupportedPLMNs CRITICALITY reject TYPE SupportedPLMNs-List PRESENCE mandatory }| + { ID id-gNB-CU-UP-Capacity CRITICALITY ignore TYPE GNB-CU-UP-Capacity PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-Extended-GNB-CU-UP-Name CRITICALITY ignore TYPE Extended-GNB-CU-UP-Name PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- GNB-CU-CP E1 Setup Failure + +-- +-- \*\*\*\*\* + +GNB-CU-CP-ElSetupFailure ::= SEQUENCE { +    protocolIEs          ProtocolIE-Container      { {GNB-CU-CP-ElSetupFailureIEs} }, +    ... +} + +GNB-CU-CP-ElSetupFailureIEs ELAP-PROTOCOL-IES ::= { +    { ID id-TransactionID          CRITICALITY reject  TYPE TransactionID          PRESENCE mandatory  }| +    { ID id-Cause                  CRITICALITY ignore  TYPE Cause                  PRESENCE mandatory  }| +    { ID id-TimeToWait           CRITICALITY ignore  TYPE TimeToWait              PRESENCE optional }| +    { ID id-CriticalityDiagnostics  CRITICALITY ignore  TYPE CriticalityDiagnostics  PRESENCE optional }, +    ... +} + +-- \*\*\*\*\* +-- + +-- GNB-CU-UP CONFIGURATION UPDATE + +-- +-- \*\*\*\*\* + +-- \*\*\*\*\* +-- + +-- GNB-CU-UP Configuration Update + +``` + +-- +-- ***** + +GNB-CU-UP-ConfigurationUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-UP-ConfigurationUpdateIEs} }, + ... +} + +GNB-CU-UP-ConfigurationUpdateIEs ELAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNB-CU-UP-ID CRITICALITY reject TYPE GNB-CU-UP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-Name CRITICALITY ignore TYPE GNB-CU-UP-Name PRESENCE optional }| + { ID id-SupportedPLMNs CRITICALITY reject TYPE SupportedPLMNs-List PRESENCE optional }| + { ID id-gNB-CU-UP-Capacity CRITICALITY ignore TYPE GNB-CU-UP-Capacity PRESENCE optional }| + { ID id-GNB-CU-UP-TNLA-To-Remove-List CRITICALITY reject TYPE GNB-CU-UP-TNLA-To-Remove-List PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-Extended-GNB-CU-UP-Name CRITICALITY ignore TYPE Extended-GNB-CU-UP-Name PRESENCE optional }| + { ID id-gNB-CU-UP-MBS-Support-Info CRITICALITY reject TYPE GNB-CU-UP-MBS-Support-Info PRESENCE optional }, + ... +} + +GNB-CU-UP-TNLA-To-Remove-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF GNB-CU-UP-TNLA-To-Remove-Item + +-- ***** +-- + +``` + +``` +-- GNB-CU-UP Configuration Update Acknowledge +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +GNB-CU-UP-ConfigurationUpdateAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-UP-ConfigurationUpdateAcknowledgeIEs} }, + ... +} +``` + +``` +GNB-CU-UP-ConfigurationUpdateAcknowledgeIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }, + ... +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- GNB-CU-UP Configuration Update Failure +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +GNB-CU-UP-ConfigurationUpdateFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-UP-ConfigurationUpdateFailureIEs} }, + ... +} +``` + +``` + +} + +GNB-CU-UP-ConfigurationUpdateFailureIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- GNB-CU-CP CONFIGURATION UPDATE +-- +-- ***** + +-- ***** +-- +-- GNB-CU-CP Configuration Update +-- +-- ***** + +``` + +``` + +GNB-CU-CP-ConfigurationUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-CP-ConfigurationUpdateIEs} }, + ... +} + +``` + +``` + +} + +GNB-CU-CP-ConfigurationUpdateIEs EIAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNB-CU-CP-Name CRITICALITY ignore TYPE GNB-CU-CP-Name PRESENCE optional }| + { ID id-GNB-CU-CP-TNLA-To-Add-List CRITICALITY ignore TYPE GNB-CU-CP-TNLA-To-Add-List PRESENCE optional }| + { ID id-GNB-CU-CP-TNLA-To-Remove-List CRITICALITY ignore TYPE GNB-CU-CP-TNLA-To-Remove-List PRESENCE optional }| + { ID id-GNB-CU-CP-TNLA-To-Update-List CRITICALITY ignore TYPE GNB-CU-CP-TNLA-To-Update-List PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-Extended-GNB-CU-CP-Name CRITICALITY ignore TYPE Extended-GNB-CU-CP-Name PRESENCE optional }, + ... +} + +``` + +``` + +GNB-CU-CP-TNLA-To-Add-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF GNB-CU-CP-TNLA-To-Add-Item +GNB-CU-CP-TNLA-To-Remove-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF GNB-CU-CP-TNLA-To-Remove-Item +GNB-CU-CP-TNLA-To-Update-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF GNB-CU-CP-TNLA-To-Update-Item + +``` + +``` + +-- ***** +-- +-- GNB-CU-CP Configuration Update Acknowledge +-- +-- ***** + +``` + +``` + +GNB-CU-CP-ConfigurationUpdateAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-CP-ConfigurationUpdateAcknowledgeIEs} }, + +``` + +``` + + ... + } + + GNB-CU-CP-ConfigurationUpdateAcknowledgeIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-GNB-CU-CP-TNLA-Setup-List CRITICALITY ignore TYPE GNB-CU-CP-TNLA-Setup-List PRESENCE optional }| + { ID id-GNB-CU-CP-TNLA-Failed-To-Setup-List CRITICALITY ignore TYPE GNB-CU-CP-TNLA-Failed-To-Setup-List PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }, + ... + } + +``` + +``` + +GNB-CU-CP-TNLA-Setup-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF GNB-CU-CP-TNLA-Setup-Item +GNB-CU-CP-TNLA-Failed-To-Setup-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF GNB-CU-CP-TNLA-Failed-To-Setup-Item + +``` + +``` + +-- ***** +-- +-- GNB-CU-CP Configuration Update Failure +-- +-- ***** + +``` + +``` + +GNB-CU-CP-ConfigurationUpdateFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNB-CU-CP-ConfigurationUpdateFailureIEs} }, + ... + +``` + +``` + +} + +GNB-CU-CP-ConfigurationUpdateFailureIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- E1 RELEASE +-- +-- ***** +-- +-- ***** +-- +-- E1 Release Request +-- +-- ***** + +``` + +``` + +E1ReleaseRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {E1ReleaseRequestIEs} }, + ... + +``` + +``` +} + +E1ReleaseRequestIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +-- ***** +-- +-- E1 Release Response +-- +-- ***** + +E1ReleaseResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {E1ReleaseResponseIEs} }, + ... +} + +E1ReleaseResponseIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} +``` + +``` + +-- ***** +-- +-- BEARER CONTEXT SETUP +-- +-- ***** + +-- ***** +-- +-- Bearer Context Setup Request +-- +-- ***** + +``` + +``` + +BearerContextSetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BearerContextSetupRequestIEs } }, + ... +} + +``` + +``` + +BearerContextSetupRequestIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-SecurityInformation CRITICALITY reject TYPE SecurityInformation PRESENCE mandatory }| + { ID id-UEDLAggregateMaximumBitRate CRITICALITY reject TYPE BitRate PRESENCE mandatory }| + { ID id-UEDLMaximumIntegrityProtectedDataRate CRITICALITY reject TYPE BitRate PRESENCE optional }| + { ID id-Serving-PLMN CRITICALITY ignore TYPE PLMN-Identity PRESENCE mandatory }| + { ID id-ActivityNotificationLevel CRITICALITY reject TYPE ActivityNotificationLevel PRESENCE mandatory }| +} + +``` + +``` + +{ ID id-UE-Inactivity-Timer CRITICALITY reject TYPE Inactivity-Timer PRESENCE optional }| +{ ID id-BearerContextStatusChange CRITICALITY reject TYPE BearerContextStatusChange PRESENCE optional }| +{ ID id-System-BearerContextSetupRequest CRITICALITY reject TYPE System-BearerContextSetupRequest PRESENCE mandatory }| +{ ID id-RANUEID CRITICALITY ignore TYPE RANUEID PRESENCE optional }| +{ ID id-GNB-DU-ID CRITICALITY ignore TYPE GNB-DU-ID PRESENCE optional }| +{ ID id-TraceActivation CRITICALITY ignore TYPE TraceActivation PRESENCE optional }| +{ ID id-NPNContextInfo CRITICALITY reject TYPE NPNContextInfo PRESENCE optional}| +{ ID id-ManagementBasedMDTPLMNList CRITICALITY ignore TYPE MDTPLMNList PRESENCE optional}| +{ ID id-CHOInitiation CRITICALITY reject TYPE CHOInitiation PRESENCE optional }| +{ ID id-AdditionalHandoverInfo CRITICALITY ignore TYPE AdditionalHandoverInfo PRESENCE optional }| +{ ID id-DirectForwardingPathAvailability CRITICALITY ignore TYPE DirectForwardingPathAvailability PRESENCE optional }| +{ ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY ignore TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE optional }| +{ ID id-MDTPollutedMeasurementIndicator CRITICALITY ignore TYPE MDTPollutedMeasurementIndicator PRESENCE optional }| +{ ID id-UESliceMaximumBitRateList CRITICALITY ignore TYPE UESliceMaximumBitRateList PRESENCE optional }| +{ ID id-SCGActivationStatus CRITICALITY ignore TYPE SCGActivationStatus PRESENCE optional }| +{ ID id-MT-SDT-Information-Request CRITICALITY ignore TYPE MT-SDT-Information-Request PRESENCE optional }| +{ ID id-SDT-data-size-threshold CRITICALITY ignore TYPE SDT-data-size-threshold PRESENCE optional }, +... +} + +``` + +``` + +System-BearerContextSetupRequest ::= CHOICE { + e-UTRAN-BearerContextSetupRequest ProtocolIE-Container {{EUTRAN-BearerContextSetupRequest}}, + nG-RAN-BearerContextSetupRequest ProtocolIE-Container {{NG-RAN-BearerContextSetupRequest}}, + choice-extension ProtocolIE-SingleContainer {{System-BearerContextSetupRequest-ExtIEs}} +} + +``` + +} + +System-BearerContextSetupRequest-ExtIEs E1AP-PROTOCOL-IES ::= { + +... + +} + +EUTRAN-BearerContextSetupRequest E1AP-PROTOCOL-IES ::= { + +{ ID id-DRB-To-Setup-List-EUTRAN            CRITICALITY reject    TYPE DRB-To-Setup-List-EUTRAN    PRESENCE mandatory }| + +{ ID id-SubscriberProfileIDforRFP            CRITICALITY ignore    TYPE SubscriberProfileIDforRFP    PRESENCE optional }| + +{ ID id-AdditionalRRMPriorityIndex           CRITICALITY ignore    TYPE AdditionalRRMPriorityIndex PRESENCE optional }, + +... + +} + +NG-RAN-BearerContextSetupRequest E1AP-PROTOCOL-IES ::= { + +{ ID id-PDU-Session-Resource-To-Setup-List            CRITICALITY reject    TYPE PDU-Session-Resource-To-Setup-List    PRESENCE mandatory }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- Bearer Context Setup Response + +-- + +-- \*\*\*\*\* + +``` + +BearerContextSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BearerContextSetupResponseIEs } }, + ... +} + +``` + +``` + +BearerContextSetupResponseIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory } | + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory } | + { ID id-System-BearerContextSetupResponse CRITICALITY ignore TYPE System-BearerContextSetupResponse PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +System-BearerContextSetupResponse ::= CHOICE { + e-UTRAN-BearerContextSetupResponse ProtocolIE-Container {{EUTRAN-BearerContextSetupResponse}}, + nG-RAN-BearerContextSetupResponse ProtocolIE-Container {{NG-RAN-BearerContextSetupResponse}}, + choice-extension ProtocolIE-SingleContainer {{System-BearerContextSetupResponse-ExtIEs}} +} + +``` + +``` + +System-BearerContextSetupResponse-ExtIEs E1AP-PROTOCOL-IES ::= { + ... +} + +``` + +``` + +EUTRAN-BearerContextSetupResponse E1AP-PROTOCOL-IES ::= { + { ID id-DRB-Setup-List-EUTRAN CRITICALITY ignore TYPE DRB-Setup-List-EUTRAN PRESENCE mandatory }| + { ID id-DRB-Failed-List-EUTRAN CRITICALITY ignore TYPE DRB-Failed-List-EUTRAN PRESENCE optional }, + ... +} + +NG-RAN-BearerContextSetupResponse E1AP-PROTOCOL-IES ::= { + { ID id-PDU-Session-Resource-Setup-List CRITICALITY ignore TYPE PDU-Session-Resource-Setup-List PRESENCE mandatory }| + { ID id-PDU-Session-Resource-Failed-List CRITICALITY ignore TYPE PDU-Session-Resource-Failed-List PRESENCE optional }, + ... +} + +-- ***** +-- +-- Bearer Context Setup Failure +-- +-- ***** + +BearerContextSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BearerContextSetupFailureIEs} }, + ... +} + +``` + +BearerContextSetupFailureIEs E1AP-PROTOCOL-IES ::= { + +{ ID id-gNB-CU-CP-UE-E1AP-ID            CRITICALITY reject    TYPE GNB-CU-CP-UE-E1AP-ID            PRESENCE mandatory }| + +{ ID id-gNB-CU-UP-UE-E1AP-ID            CRITICALITY ignore    TYPE GNB-CU-UP-UE-E1AP-ID            PRESENCE optional }| + +{ ID id-Cause                                CRITICALITY ignore    TYPE Cause                                    PRESENCE mandatory }| + +{ ID id-CriticalityDiagnostics            CRITICALITY ignore    TYPE CriticalityDiagnostics            PRESENCE optional }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- BEARER CONTEXT MODIFICATION + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Bearer Context Modification Request + +-- + +-- \*\*\*\*\* + +BearerContextModificationRequest ::= SEQUENCE { + +protocolIEs            ProtocolIE-Container            { { BearerContextModificationRequestIEs } }, + +... + +} + +``` + +BearerContextModificationRequestIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-SecurityInformation CRITICALITY reject TYPE SecurityInformation PRESENCE optional }| + { ID id-UEDLAggregateMaximumBitRate CRITICALITY reject TYPE BitRate PRESENCE optional }| + { ID id-UEDLMaximumIntegrityProtectedDataRate CRITICALITY reject TYPE BitRate PRESENCE optional }| + { ID id-BearerContextStatusChange CRITICALITY reject TYPE BearerContextStatusChange PRESENCE optional }| + { ID id-New-UL-TNL-Information-Required CRITICALITY reject TYPE New-UL-TNL-Information-Required PRESENCE optional }| + { ID id-UE-Inactivity-Timer CRITICALITY reject TYPE Inactivity-Timer PRESENCE optional }| + { ID id-DataDiscardRequired CRITICALITY ignore TYPE DataDiscardRequired PRESENCE optional }| + { ID id-System-BearerContextModificationRequest CRITICALITY reject TYPE System-BearerContextModificationRequest PRESENCE optional }| + { ID id-RANUEID CRITICALITY ignore TYPE RANUEID PRESENCE optional }| + { ID id-GNB-DU-ID CRITICALITY ignore TYPE GNB-DU-ID PRESENCE optional }| + { ID id-ActivityNotificationLevel CRITICALITY ignore TYPE ActivityNotificationLevel PRESENCE optional }| + { ID id-MDTPollutedMeasurementIndicator CRITICALITY ignore TYPE MDTPollutedMeasurementIndicator PRESENCE optional }| + { ID id-UESliceMaximumBitRateList CRITICALITY ignore TYPE UESliceMaximumBitRateList PRESENCE optional }| + { ID id-SCGActivationStatus CRITICALITY ignore TYPE SCGActivationStatus PRESENCE optional }| + { ID id-SDTContinueROHC CRITICALITY reject TYPE SDTContinueROHC PRESENCE optional }| + { ID id-ManagementBasedMDTPLMNModificationList CRITICALITY ignore TYPE MDTPLMNModificationList PRESENCE optional }| + { ID id-InactivityInformationRequest CRITICALITY ignore TYPE InactivityInformationRequest PRESENCE optional }| + { ID id-MT-SDT-Information-Request CRITICALITY ignore TYPE MT-SDT-Information-Request PRESENCE optional }| + { ID id-SDT-data-size-threshold CRITICALITY ignore TYPE SDT-data-size-threshold PRESENCE optional }, + ... +} + +``` + +``` + +System-BearerContextModificationRequest ::= CHOICE { + e-UTRAN-BearerContextModificationRequest ProtocolIE-Container {{EUTRAN-BearerContextModificationRequest}}, + nG-RAN-BearerContextModificationRequest ProtocolIE-Container {{NG-RAN-BearerContextModificationRequest}}, + choice-extension ProtocolIE-SingleContainer {{System-BearerContextModificationRequest-ExtIEs}} +} + +System-BearerContextModificationRequest-ExtIEs E1AP-PROTOCOL-IES ::= { + ... +} + +EUTRAN-BearerContextModificationRequest E1AP-PROTOCOL-IES ::= { + { ID id-DRB-To-Setup-Mod-List-EUTRAN CRITICALITY reject TYPE DRB-To-Setup-Mod-List-EUTRAN PRESENCE optional }| + { ID id-DRB-To-Modify-List-EUTRAN CRITICALITY reject TYPE DRB-To-Modify-List-EUTRAN PRESENCE optional }| + { ID id-DRB-To-Remove-List-EUTRAN CRITICALITY reject TYPE DRB-To-Remove-List-EUTRAN PRESENCE optional }| + { ID id-SubscriberProfileIDforRFP CRITICALITY ignore TYPE SubscriberProfileIDforRFP PRESENCE optional }| + { ID id-AdditionalRRMPriorityIndex CRITICALITY ignore TYPE AdditionalRRMPriorityIndex PRESENCE optional }, + ... +} + +NG-RAN-BearerContextModificationRequest E1AP-PROTOCOL-IES ::= { + { ID id-PDU-Session-Resource-To-Setup-Mod-List CRITICALITY reject TYPE PDU-Session-Resource-To-Setup-Mod-List PRESENCE optional }| + { ID id-PDU-Session-Resource-To-Modify-List CRITICALITY reject TYPE PDU-Session-Resource-To-Modify-List PRESENCE optional }| + { ID id-PDU-Session-Resource-To-Remove-List CRITICALITY reject TYPE PDU-Session-Resource-To-Remove-List PRESENCE optional }, + +``` + +``` + + ... + } + + -- ***** + -- + -- Bearer Context Modification Response + -- + -- ***** + + BearerContextModificationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BearerContextModificationResponseIEs } }, + ... + } + + BearerContextModificationResponseIEs ELAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-System-BearerContextModificationResponse CRITICALITY ignore TYPE System-BearerContextModificationResponse PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-UEInactivityInformation CRITICALITY ignore TYPE UEInactivityInformation PRESENCE optional}, + ... + } + +``` + +``` + +System-BearerContextModificationResponse := CHOICE { + e-UTRAN-BearerContextModificationResponse ProtocolIE-Container {{EUTRAN-BearerContextModificationResponse}}, + nG-RAN-BearerContextModificationResponse ProtocolIE-Container {{NG-RAN-BearerContextModificationResponse}}, + choice-extension ProtocolIE-SingleContainer {{System-BearerContextModificationResponse-ExtIEs}} +} + +System-BearerContextModificationResponse-ExtIEs E1AP-PROTOCOL-IES := { + ... +} + +EUTRAN-BearerContextModificationResponse E1AP-PROTOCOL-IES := { + { ID id-DRB-Setup-Mod-List-EUTRAN CRITICALITY ignore TYPE DRB-Setup-Mod-List-EUTRAN PRESENCE optional }| + { ID id-DRB-Failed-Mod-List-EUTRAN CRITICALITY ignore TYPE DRB-Failed-Mod-List-EUTRAN PRESENCE optional }| + { ID id-DRB-Modified-List-EUTRAN CRITICALITY ignore TYPE DRB-Modified-List-EUTRAN PRESENCE optional }| + { ID id-DRB-Failed-To-Modify-List-EUTRAN CRITICALITY ignore TYPE DRB-Failed-To-Modify-List-EUTRAN PRESENCE optional }| + { ID id-RetainabilityMeasurementsInfo CRITICALITY ignore TYPE RetainabilityMeasurementsInfo PRESENCE optional }, + ... +} + +NG-RAN-BearerContextModificationResponse E1AP-PROTOCOL-IES := { + { ID id-PDU-Session-Resource-Setup-Mod-List CRITICALITY reject TYPE PDU-Session-Resource-Setup-Mod-List PRESENCE optional }| + { ID id-PDU-Session-Resource-Failed-Mod-List CRITICALITY reject TYPE PDU-Session-Resource-Failed-Mod-List PRESENCE optional }| + { ID id-PDU-Session-Resource-Modified-List CRITICALITY reject TYPE PDU-Session-Resource-Modified-List PRESENCE optional }| + { ID id-PDU-Session-Resource-Failed-To-Modify-List CRITICALITY reject TYPE PDU-Session-Resource-Failed-To-Modify-List PRESENCE optional }| +} + +``` + +``` + + { ID id-RetainabilityMeasurementsInfo CRITICALITY ignore TYPE RetainabilityMeasurementsInfo PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- Bearer Context Modification Failure +-- +-- ***** + +``` + +``` + +BearerContextModificationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BearerContextModificationFailureIEs } }, + ... +} + +``` + +``` + +BearerContextModificationFailureIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory } | + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** + +``` + +``` + +-- +-- BEARER CONTEXT MODIFICATION REQUIRED +-- +-- ***** +-- +-- ***** +-- +-- Bearer Context Modification Required +-- +-- ***** + +BearerContextModificationRequired ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BearerContextModificationRequiredIEs} }, + ... +} + +BearerContextModificationRequiredIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-System-BearerContextModificationRequired CRITICALITY reject TYPE System-BearerContextModificationRequired PRESENCE mandatory }, + ... +} + +System-BearerContextModificationRequired ::= CHOICE { + e-UTRAN-BearerContextModificationRequired ProtocolIE-Container {{EUTRAN-BearerContextModificationRequired}}, +} + +``` + +``` + +nG-RAN-BearerContextModificationRequired ProtocolIE-Container {{NG-RAN-BearerContextModificationRequired}}, +choice-extension ProtocolIE-SingleContainer {{System-BearerContextModificationRequired-ExtIEs}} +} + +``` + +``` + +System-BearerContextModificationRequired-ExtIEs E1AP-PROTOCOL-IES ::= { + ... +} + +``` + +``` + +EUTRAN-BearerContextModificationRequired E1AP-PROTOCOL-IES ::= { + { ID id-DRB-Required-To-Modify-List-EUTRAN CRITICALITY reject TYPE DRB-Required-To-Modify-List-EUTRAN PRESENCE optional }| + { ID id-DRB-Required-To-Remove-List-EUTRAN CRITICALITY reject TYPE DRB-Required-To-Remove-List-EUTRAN PRESENCE optional }, + ... +} + +``` + +``` + +NG-RAN-BearerContextModificationRequired E1AP-PROTOCOL-IES ::= { + { ID id-PDU-Session-Resource-Required-To-Modify-List CRITICALITY reject TYPE PDU-Session-Resource-Required-To-Modify-List PRESENCE +optional }| + { ID id-PDU-Session-Resource-To-Remove-List CRITICALITY reject TYPE PDU-Session-Resource-To-Remove-List PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- + +``` + +-- Bearer Context Modification Confirm + +-- + +-- \*\*\*\*\* + +BearerContextModificationConfirm ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container { { BearerContextModificationConfirmIEs } }, + +    ... + +} + +BearerContextModificationConfirmIEs ELAP-PROTOCOL-IES ::= { + +    { ID id-gNB-CU-CP-UE-E1AP-ID                  CRITICALITY reject  TYPE GNB-CU-CP-UE-E1AP-ID                  PRESENCE mandatory }| + +    { ID id-gNB-CU-UP-UE-E1AP-ID                  CRITICALITY reject  TYPE GNB-CU-UP-UE-E1AP-ID                  PRESENCE mandatory }| + +    { ID id-System-BearerContextModificationConfirm  CRITICALITY ignore  TYPE System-BearerContextModificationConfirm  PRESENCE optional }| + +    { ID id-CriticalityDiagnostics                  CRITICALITY ignore  TYPE CriticalityDiagnostics                  PRESENCE optional }, + +    ... + +} + +System-BearerContextModificationConfirm ::= CHOICE { + +    e-UTRAN-BearerContextModificationConfirm    ProtocolIE-Container {{EUTRAN-BearerContextModificationConfirm}}, + +    nG-RAN-BearerContextModificationConfirm    ProtocolIE-Container {{NG-RAN-BearerContextModificationConfirm}}, + +    choice-extension                            ProtocolIE-SingleContainer {{System-BearerContextModificationConfirm-ExtIEs}} + +} + +System-BearerContextModificationConfirm-ExtIEs ELAP-PROTOCOL-IES ::= { + +``` + + ... + } + + EUTRAN-BearerContextModificationConfirm E1AP-PROTOCOL-IES ::= { + { ID id-DRB-Confirm-Modified-List-EUTRAN CRITICALITY ignore TYPE DRB-Confirm-Modified-List-EUTRAN PRESENCE optional }, + ... + } + + NG-RAN-BearerContextModificationConfirm E1AP-PROTOCOL-IES ::= { + { ID id-PDU-Session-Resource-Confirm-Modified-List CRITICALITY ignore TYPE PDU-Session-Resource-Confirm-Modified-List PRESENCE optional }, + ... + } + + -- ***** + -- + -- BEARER CONTEXT RELEASE + -- + -- ***** + -- + -- ***** + -- + -- Bearer Context Release Command + -- + +``` + +-- \*\*\*\*\* + +``` + +BearerContextReleaseCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BearerContextReleaseCommandIEs } }, + ... +} + +``` + +``` + +BearerContextReleaseCommandIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory } | + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- Bearer Context Release Complete + +-- + +-- \*\*\*\*\* + +``` + +BearerContextReleaseComplete ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BearerContextReleaseCompleteIEs } }, + ... +} + +``` + +``` + +BearerContextReleaseCompleteIEs EIAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-EIAP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-EIAP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-EIAP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-EIAP-ID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-RetainabilityMeasurementsInfo CRITICALITY ignore TYPE RetainabilityMeasurementsInfo PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- BEARER CONTEXT RELEASE REQUEST + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Bearer Context Release Request + +-- + +-- \*\*\*\*\* + +``` + +BearerContextReleaseRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BearerContextReleaseRequestIEs } }, + ... +} + +``` + +``` + +BearerContextReleaseRequestIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-DRB-Status-List CRITICALITY ignore TYPE DRB-Status-List PRESENCE optional }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +DRB-Status-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRB-Status-Item + +``` + +``` + +-- ***** +-- +-- BEARER CONTEXT INACTIVITY NOTIFICATION +-- +-- ***** + +-- ***** +-- +-- Bearer Context Inactivity Notification +-- +-- ***** + +``` + +``` + +BearerContextInactivityNotification ::= SEQUENCE { + +``` + +``` + +protocolIEs ProtocolIE-Container { { BearerContextInactivityNotificationIEs } }, +... +} + +``` + +``` + +BearerContextInactivityNotificationIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-ActivityInformation CRITICALITY reject TYPE ActivityInformation PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- DL DATA NOTIFICATION +-- +-- ***** +-- +-- ***** +-- +-- DL Data Notification +-- +-- ***** + +``` + +``` + +DLDataNotification ::= SEQUENCE { + +``` + +``` + +protocolIEs ProtocolIE-Container { { DLDataNotificationIEs } }, +... +} + +``` + +``` + +DLDataNotificationIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-PPI CRITICALITY ignore TYPE PPI PRESENCE optional }| + { ID id-PDU-Session-To-Notify-List CRITICALITY ignore TYPE PDU-Session-To-Notify-List PRESENCE optional }| + { ID id-MT-SDT-Information CRITICALITY ignore TYPE MT-SDT-Information PRESENCE optional }| + { ID id-SDT-data-size-threshold-Crossed CRITICALITY ignore TYPE SDT-data-size-threshold-Crossed PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- ***** +-- +-- UL Data Notification +-- +-- ***** + +``` + +``` + +ULDataNotification ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { ULDataNotificationIEs } }, + ... +} + +``` + +``` + +} + +ULDataNotificationIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-PDU-Session-To-Notify-List CRITICALITY reject TYPE PDU-Session-To-Notify-List PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- DATA USAGE REPORT +-- +-- ***** + +-- ***** +-- +-- Data Usage Report +-- +-- ***** + +``` + +``` + +DataUsageReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { DataUsageReportIEs } }, + ... +} + +``` + +DataUsageReportIEs E1AP-PROTOCOL-IES ::= { + +{ ID id-gNB-CU-CP-UE-E1AP-ID            CRITICALITY reject    TYPE GNB-CU-CP-UE-E1AP-ID            PRESENCE mandatory } | + { ID id-gNB-CU-UP-UE-E1AP-ID            CRITICALITY reject    TYPE GNB-CU-UP-UE-E1AP-ID            PRESENCE mandatory } | + { ID id-Data-Usage-Report-List           CRITICALITY ignore    TYPE Data-Usage-Report-List            PRESENCE mandatory }, + ... + +} + +-- \*\*\*\*\* + +-- + +-- GNB-CU-UP COUNTER CHECK + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- gNB-CU-UP Counter Check Request + +-- + +-- \*\*\*\*\* + +GNB-CU-UP-CounterCheckRequest ::= SEQUENCE { + +protocolIEs            ProtocolIE-Container            { { GNB-CU-UP-CounterCheckRequestIEs } }, + ... + +} + +``` +GNB-CU-UP-CounterCheckRequestIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-System-GNB-CU-UP-CounterCheckRequest CRITICALITY reject TYPE System-GNB-CU-UP-CounterCheckRequest PRESENCE mandatory }, + ... +} + +System-GNB-CU-UP-CounterCheckRequest ::= CHOICE { + e-UTRAN-GNB-CU-UP-CounterCheckRequest ProtocolIE-Container {{EUTRAN-GNB-CU-UP-CounterCheckRequest}}, + nG-RAN-GNB-CU-UP-CounterCheckRequest ProtocolIE-Container {{NG-RAN-GNB-CU-UP-CounterCheckRequest}}, + choice-extension ProtocolIE-SingleContainer {{System-GNB-CU-UP-CounterCheckRequest-ExtIEs}} +} + +System-GNB-CU-UP-CounterCheckRequest-ExtIEs E1AP-PROTOCOL-IES ::= { + ... +} + +EUTRAN-GNB-CU-UP-CounterCheckRequest E1AP-PROTOCOL-IES ::= { + { ID id-DRBs-Subject-To-Counter-Check-List-EUTRAN CRITICALITY ignore TYPE DRBs-Subject-To-Counter-Check-List-EUTRAN PRESENCE mandatory }, + ... +} + +NG-RAN-GNB-CU-UP-CounterCheckRequest E1AP-PROTOCOL-IES ::= { +``` + +``` + + { ID id-DRBs-Subject-To-Counter-Check-List-NG-RAN CRITICALITY ignore TYPE DRBs-Subject-To-Counter-Check-List-NG-RAN PRESENCE mandatory }, + ... +} + +-- ***** +-- +-- gNB-CU-UP STATUS INDICATION ELEMENTARY PROCEDURE +-- +-- ***** + +-- ***** +-- +-- gNB-CU-UP Status Indication +-- +-- ***** + +GNB-CU-UP-StatusIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { GNB-CU-UP-StatusIndicationIEs} }, + ... +} + +``` + +``` + +GNB-CU-UP-StatusIndicationIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-GNB-CU-UP-OverloadInformation CRITICALITY reject TYPE GNB-CU-UP-OverloadInformation PRESENCE mandatory }, + ... +} + +-- ***** +-- +-- gNB-CU-CP MEASUREMENT RESULTS INFORMATION +-- +-- ***** + +GNB-CU-CPMeasurementResultsInformation ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { GNB-CU-CPMeasurementResultsInformationIEs } }, + ... +} + +GNB-CU-CPMeasurementResultsInformationIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory}| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory}| + { ID id-DRB-Measurement-Results-Information-List CRITICALITY ignore TYPE DRB-Measurement-Results-Information-List PRESENCE mandatory}, + ... +} + +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- MR-DC DATA USAGE REPORT +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +MRDC-DataUsageReport ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container { { MRDC-DataUsageReportIEs } }, +``` + +``` + ... +``` + +``` +} +``` + +``` +MRDC-DataUsageReportIEs E1AP-PROTOCOL-IES ::= { +``` + +``` + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory} | +``` + +``` + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory} | +``` + +``` + { ID id-PDU-Session-Resource-Data-Usage-List CRITICALITY ignore TYPE PDU-Session-Resource-Data-Usage-List PRESENCE mandatory}, +``` + +``` + ... +``` + +``` +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- TRACE ELEMENTARY PROCEDURES +``` + +``` +-- +``` + +``` + +-- ***** + +-- ***** + +-- + +-- TRACE START + +-- + +-- ***** + +``` + +``` + +TraceStart ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {TraceStartIEs} }, + ... +} + +``` + +``` + +TraceStartIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-TraceActivation CRITICALITY ignore TYPE TraceActivation PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** + +-- + +-- DEACTIVATE TRACE + +``` + +``` + +-- +-- ***** + +DeactivateTrace ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { DeactivateTraceIEs } }, + ... +} + +DeactivateTraceIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory }| + { ID id-TraceID CRITICALITY ignore TYPE TraceID PRESENCE mandatory }, + ... +} + +-- ***** +-- +-- CELL TRAFFIC TRACE +-- +-- ***** + +CellTrafficTrace ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { CellTrafficTraceIEs } }, + +``` + +... +} + +CellTrafficTraceIEs E1AP-PROTOCOL-IES ::= { + +| | | | | +|---------------------------------------|--------------------|----------------------------|---------------------| +| {ID id-gNB-CU-CP-UE-E1AP-ID | CRITICALITY reject | TYPE GNB-CU-CP-UE-E1AP-ID | PRESENCE mandatory} | +| {ID id-gNB-CU-UP-UE-E1AP-ID | CRITICALITY reject | TYPE GNB-CU-UP-UE-E1AP-ID | PRESENCE mandatory} | +| {ID id-TraceID | CRITICALITY ignore | TYPE TraceID | PRESENCE mandatory} | +| {ID id-TraceCollectionEntityIPAddress | CRITICALITY ignore | TYPE TransportLayerAddress | PRESENCE mandatory} | +| {ID id-PrivacyIndicator | CRITICALITY ignore | TYPE PrivacyIndicator | PRESENCE optional} | +| {ID id-URIaddress | CRITICALITY ignore | TYPE URIaddress | PRESENCE optional}, | + +... +} + +-- \*\*\*\*\* +-- +-- PRIVATE MESSAGE +-- +-- \*\*\*\*\* + +PrivateMessage ::= SEQUENCE { + +privateIEs PrivateIE-Container {{PrivateMessage-IEs}}, +... + +``` + +} + +PrivateMessage-IEs E1AP-PRIVATE-IES ::= { + ... +} + +-- ***** +-- +-- RESOURCE STATUS REQUEST +-- +-- ***** + +ResourceStatusRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { ResourceStatusRequestIEs } }, + ... +} + +ResourceStatusRequestIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory}| + { ID id-gNB-CU-CP-Measurement-ID CRITICALITY reject TYPE INTEGER (1..4095, ...) PRESENCE mandatory}| + { ID id-gNB-CU-UP-Measurement-ID CRITICALITY ignore TYPE INTEGER (1..4095, ...) PRESENCE optional}| + { ID id-RegistrationRequest CRITICALITY reject TYPE RegistrationRequest PRESENCE mandatory}| + { ID id-ReportCharacteristics CRITICALITY reject TYPE ReportCharacteristics PRESENCE conditional}| + { ID id-ReportingPeriodicity CRITICALITY ignore TYPE ReportingPeriodicity PRESENCE optional}, + +``` + +``` + + ... + } + + -- ***** + -- + -- RESOURCE STATUS RESPONSE + -- + -- ***** + +``` + +``` + +ResourceStatusResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { ResourceStatusResponseIEs } }, + ... +} + +``` + +``` + +ResourceStatusResponseIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory}| + { ID id-gNB-CU-CP-Measurement-ID CRITICALITY reject TYPE INTEGER (1..4095, ...) PRESENCE mandatory}| + { ID id-gNB-CU-UP-Measurement-ID CRITICALITY ignore TYPE INTEGER (1..4095, ...) PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + + -- ***** + +``` + +``` + +-- +-- RESOURCE STATUS FAILURE +-- +-- ***** + +``` + +``` + +ResourceStatusFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { ResourceStatusFailureIEs } }, + ... +} + +``` + +``` + +ResourceStatusFailureIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory}| + { ID id-gNB-CU-CP-Measurement-ID CRITICALITY reject TYPE INTEGER (1..4095, ...) PRESENCE mandatory}| + { ID id-gNB-CU-UP-Measurement-ID CRITICALITY ignore TYPE INTEGER (1..4095, ...) PRESENCE optional}| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- RESOURCE STATUS UPDATE +-- +-- ***** + +``` + +ResourceStatusUpdate ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { { ResourceStatusUpdateIEs } }, + +    ... + +} + +ResourceStatusUpdateIEs E1AP-PROTOCOL-IES ::= { + +    { ID id-TransactionID                    CRITICALITY reject    TYPE TransactionID    PRESENCE mandatory}| + +    { ID id-gNB-CU-CP-Measurement-ID        CRITICALITY reject    TYPE INTEGER (1..4095, ...)    PRESENCE mandatory}| + +    { ID id-gNB-CU-UP-Measurement-ID        CRITICALITY ignore    TYPE INTEGER (1..4095, ...)    PRESENCE mandatory}| + +    { ID id-TNL-AvailableCapacityIndicator    CRITICALITY ignore    TYPE    TNL-AvailableCapacityIndicator    PRESENCE +optional}| + +    { ID id-HW-CapacityIndicator            CRITICALITY ignore    TYPE    HW-CapacityIndicator    PRESENCE +optional}| + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- IAB UP TNL ADDRESS UPDATE + +-- + +-- \*\*\*\*\* + +``` +-- ***** +-- +-- IAB UP TNL Address Update +-- +-- ***** +``` + +``` +IAB-UPTNLAddressUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { IAB-UPTNLAddressUpdateIEs } }, + ... +} +``` + +``` +IAB-UPTNLAddressUpdateIEs ELAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | + { ID id-DLUPTNLAddressToUpdateList CRITICALITY ignore TYPE DLUPTNLAddressToUpdateList PRESENCE optional }, + ... +} +``` + +``` +DLUPTNLAddressToUpdateList ::= SEQUENCE (SIZE(1.. maxnoofTNLAddresses)) OF DLUPTNLAddressToUpdateItem +``` + +``` +-- ***** +-- +-- IAB UP TNL Address Update Acknowledge +-- +``` + +-- \*\*\*\*\* + +IAB-UPTNLAddressUpdateAcknowledge ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container    { { IAB-UPTNLAddressUpdateAcknowledgeIEs } }, + +    ... + +} + +IAB-UPTNLAddressUpdateAcknowledgeIEs ELAP-PROTOCOL-IES ::= { + +    { ID id-TransactionID          CRITICALITY reject  TYPE TransactionID          PRESENCE mandatory  }| + +    { ID id-CriticalityDiagnostics  CRITICALITY ignore  TYPE CriticalityDiagnostics    PRESENCE optional }| + +    { ID id-ULUPTNLAddressToUpdateList    CRITICALITY ignore  TYPE ULUPTNLAddressToUpdateList    PRESENCE optional }, + +    ... + +} + +ULUPTNLAddressToUpdateList ::= SEQUENCE (SIZE(1.. maxnoofTNLAddresses)) OF ULUPTNLAddressToUpdateItem + +-- \*\*\*\*\* + +-- + +-- IAB UP TNL Address Update Failure + +-- + +-- \*\*\*\*\* + +``` + +IAB-UPTNLAddressUpdateFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { IAB-UPTNLAddressUpdateFailureIEs } }, + ... +} + +``` + +``` + +IAB-UPTNLAddressUpdateFailureIEs E1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- EARLY FORWARDING SN TRANSFER +-- +-- ***** +-- +-- ***** +-- +-- Early Forwarding SN Transfer +-- +-- ***** + +``` + +``` + +EarlyForwardingSNTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { EarlyForwardingSNTransferIEs } }, + ... +} + +EarlyForwardingSNTransferIEs E1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-CP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-UE-E1AP-ID PRESENCE mandatory } | + { ID id-gNB-CU-UP-UE-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-UE-E1AP-ID PRESENCE mandatory } | + { ID id-DRBs-Subject-To-Early-Forwarding-List CRITICALITY reject TYPE DRBs-Subject-To-Early-Forwarding-List PRESENCE mandatory }, + ... +} + +-- ***** +-- +-- IAB PSK NOTIFICATION +-- +-- ***** +-- +-- ***** +-- +-- IAB PSK Notification +-- +-- ***** + +``` + +``` + +IABPSKNotification ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { IABPSKNotificationIEs } }, + ... +} + +IABPSKNotificationIEs ELAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-IAB-Donor-CU-UPPSKInfo CRITICALITY reject TYPE IAB-Donor-CU-UPPSKInfo PRESENCE mandatory }, + ... +} + +IAB-Donor-CU-UPPSKInfo ::= SEQUENCE (SIZE(1.. maxnoofPSKs)) OF IAB-Donor-CU-UPPSKInfo-Item + +-- ***** +-- +-- BC BEARER CONTEXT SETUP +-- +-- ***** +-- +-- ***** +-- +-- BC BEARER CONTEXT SETUP REQUEST +-- + +``` + +-- \*\*\*\*\* + +``` + +BCBearerContextSetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextSetupRequestIEs } }, + ... +} + +``` + +``` + +BCBearerContextSetupRequestIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GlobalMBSSessionID CRITICALITY reject TYPE GlobalMBSSessionID PRESENCE mandatory }| + { ID id-BCBearerContextToSetup CRITICALITY reject TYPE BCBearerContextToSetup PRESENCE mandatory }| + { ID id-AssociatedSessionID CRITICALITY ignore TYPE AssociatedSessionID PRESENCE optional }| + { ID id-MBS-ServiceArea CRITICALITY ignore TYPE MBS-ServiceArea PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- BC BEARER CONTEXT SETUP RESPONSE + +-- + +-- \*\*\*\*\* + +``` + +BCBearerContextSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextSetupResponseIEs } }, + +``` + +``` + + ... + } + + BCBearerContextSetupResponseIEs E1AP-PROTOCOL-IES ::= { + + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-BCBearerContextToSetupResponse CRITICALITY reject TYPE BCBearerContextToSetupResponse PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + + ... + } + + -- ***** + -- + -- BC BEARER CONTEXT SETUP FAILURE + -- + -- ***** + +``` + +``` + + BCBearerContextSetupFailure ::= SEQUENCE { + + protocolIEs ProtocolIE-Container { { BCBearerContextSetupFailureIEs } }, + + ... + } + +``` + +``` + + BCBearerContextSetupFailureIEs E1AP-PROTOCOL-IES ::= { + + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + +``` + +``` + + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY ignore TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE optional }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- BC BEARER CONTEXT MODIFICATION + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- BC BEARER CONTEXT MODIFICATION REQUEST + +-- + +-- \*\*\*\*\* + +``` + +BCBearerContextModificationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextModificationRequestIEs } }, + ... +} + +``` + +``` + +BCBearerContextModificationRequestIEs E1AP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-BCBearerContextToModify CRITICALITY reject TYPE BCBearerContextToModify PRESENCE mandatory }, + ... +} + +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- BC BEARER CONTEXT MODIFICATION RESPONSE +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` + +BCBearerContextModificationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextModificationResponseIEs } }, + ... +} + +``` + +``` + +BCBearerContextModificationResponseIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-BCBearerContextToModifyResponse CRITICALITY reject TYPE BCBearerContextToModifyResponse PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` +-- ***** +-- +-- BC BEARER CONTEXT MODIFICATION FAILURE +-- +-- ***** +``` + +``` +BCBearerContextModificationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextModificationFailureIEs } }, + ... +} +``` + +``` +BCBearerContextModificationFailureIEs EIAP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} +``` + +``` +-- ***** +-- +-- BC BEARER CONTEXT MODIFICATION REQUIRED +-- +``` + +``` + +-- ***** +-- +-- ***** +-- +-- BC BEARER CONTEXT MODIFICATION REQUIRED +-- +-- ***** + +``` + +``` + +BCBearerContextModificationRequired ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextModificationRequiredIEs } }, + ... +} + +``` + +``` + +BCBearerContextModificationRequiredIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory } | + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory } | + { ID id-BCBearerContextToModifyRequired CRITICALITY reject TYPE BCBearerContextToModifyRequired PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- BC BEARER CONTEXT MODIFICATION CONFIRM +-- + +``` + +-- \*\*\*\*\* + +``` + +BCBearerContextModificationConfirm ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextModificationConfirmIEs } }, + ... +} + +``` + +``` + +BCBearerContextModificationConfirmIEs ELAP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-BCBearerContextToModifyConfirm CRITICALITY reject TYPE BCBearerContextToModifyConfirm PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- BC BEARER CONTEXT RELEASE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- BC BEARER CONTEXT RELEASE COMMAND + +-- + +-- \*\*\*\*\* + +``` + +BCBearerContextReleaseCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextReleaseCommandIEs } }, + ... +} + +``` + +``` + +BCBearerContextReleaseCommandIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory } | + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- BC BEARER CONTEXT RELEASE COMPLETE + +-- + +-- \*\*\*\*\* + +``` + +BCBearerContextReleaseComplete ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextReleaseCompleteIEs } }, + ... +} + +``` + +``` + +} + +BCBearerContextReleaseCompleteIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- BC BEARER CONTEXT RELEASE REQUEST +-- +-- ***** + +-- ***** +-- +-- BC BEARER CONTEXT RELEASE REQUEST +-- +-- ***** + +``` + +``` + +BCBearerContextReleaseRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BCBearerContextReleaseRequestIEs } }, + ... +} + +``` + +``` + +} + +BCBearerContextReleaseRequestIEs EIAP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-EIAP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-EIAP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-EIAP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-EIAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- MC BEARER CONTEXT SETUP +-- +-- ***** +-- +-- ***** +-- +-- MC BEARER CONTEXT SETUP REQUEST +-- +-- ***** + +``` + +``` + +MCBearerContextSetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerContextSetupRequestIEs } }, + ... +} + +``` + +``` + +} + +MCBearerContextSetupRequestIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GlobalMBSSessionID CRITICALITY reject TYPE GlobalMBSSessionID PRESENCE mandatory }| + { ID id-MCBearerContextToSetup CRITICALITY reject TYPE MCBearerContextToSetup PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- MC BEARER CONTEXT SETUP RESPONSE +-- +-- ***** + +``` + +``` + +MCBearerContextSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerContextSetupResponseIEs } }, + ... +} + +``` + +``` + +MCBearerContextSetupResponseIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + +``` + +``` + + { ID id-MCBearerContextToSetupResponse CRITICALITY reject TYPE MCBearerContextToSetupResponse PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- MC BEARER CONTEXT SETUP FAILURE +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` + +MCBearerContextSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerContextSetupFailureIEs } }, + ... +} + +``` + +``` + +MCBearerContextSetupFailureIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY ignore TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE optional }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- MC BEARER CONTEXT MODIFICATION +-- +-- ***** + +-- ***** +-- +-- MC BEARER CONTEXT MODIFICATION REQUEST +-- +-- ***** + +``` + +``` + +MCBearerContextModificationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerContextModificationRequestIEs } }, + ... +} + +``` + +``` + +MCBearerContextModificationRequestIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-MCBearerContextToModify CRITICALITY reject TYPE MCBearerContextToModify PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- MC BEARER CONTEXT MODIFICATION RESPONSE +-- +-- ***** + +``` + +``` + +MCBearerContextModificationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerContextModificationResponseIEs } }, + ... +} + +``` + +``` + +MCBearerContextModificationResponseIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-MCBearerContextToModifyResponse CRITICALITY reject TYPE MCBearerContextToModifyResponse PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- MC BEARER CONTEXT MODIFICATION FAILURE +-- +-- ***** + +``` + +``` + +MCBearerContextModificationFailure := SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerContextModificationFailureIEs } }, + ... +} + +MCBearerContextModificationFailureIEs E1AP-PROTOCOL-IES := { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-MBSMulticastFlUContextDescriptor CRITICALITY reject TYPE MBSMulticastFlUContextDescriptor PRESENCE optional }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- +-- MC BEARER CONTEXT MODIFICATION REQUIRED + +-- +-- \*\*\*\*\* + +-- +-- \*\*\*\*\* + +-- +-- MC BEARER CONTEXT MODIFICATION REQUIRED + +-- +-- \*\*\*\*\* + +MCBearerContextModificationRequired ::= SEQUENCE { +    protocolIEs          ProtocolIE-Container      { { MCBearerContextModificationRequiredIEs } }, +    ... +} + +MCBearerContextModificationRequiredIEs E1AP-PROTOCOL-IES ::= { +    { ID id-GNB-CU-CP-MBS-E1AP-ID          CRITICALITY reject  TYPE    GNB-CU-CP-MBS-E1AP-ID          PRESENCE mandatory  }| +    { ID id-GNB-CU-UP-MBS-E1AP-ID          CRITICALITY reject  TYPE    GNB-CU-UP-MBS-E1AP-ID          PRESENCE mandatory  }| +    { ID id-MCBearerContextToModifyRequired CRITICALITY reject  TYPE    MCBearerContextToModifyRequired PRESENCE mandatory  }, +    ... +} + +-- \*\*\*\*\* +-- + +-- MC BEARER CONTEXT MODIFICATION CONFIRM + +-- +-- \*\*\*\*\* + +MCBearerContextModificationConfirm ::= SEQUENCE { +    protocolIEs          ProtocolIE-Container      { { MCBearerContextModificationConfirmIEs } }, +    ... +} + +``` + +} + +MCBearerContextModificationConfirmIEs E1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-MCBearerContextToModifyConfirm CRITICALITY reject TYPE MCBearerContextToModifyConfirm PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- MC BEARER CONTEXT RELEASE +-- +-- ***** +-- +-- ***** +-- +-- MC BEARER CONTEXT RELEASE COMMAND +-- +-- ***** + +``` + +``` + +MCBearerContextReleaseCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerContextReleaseCommandIEs } }, + +``` + +``` + + ... + } + + MCBearerContextReleaseCommandIEs E1AP-PROTOCOL-IES ::= { + + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... + } + +``` + +``` + +-- ***** +-- +-- MC BEARER CONTEXT RELEASE COMPLETE +-- +-- ***** + +``` + +``` + +MCBearerContextReleaseComplete ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerContextReleaseCompleteIEs } }, + ... +} + +``` + +``` + +MCBearerContextReleaseCompleteIEs E1AP-PROTOCOL-IES ::= { + + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory }| + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory }| + +``` + +``` + + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- MC BEARER CONTEXT RELEASE REQUEST + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- MC BEARER CONTEXT RELEASE REQUEST + +-- + +-- \*\*\*\*\* + +``` + +MCBearerContextReleaseRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerContextReleaseRequestIEs } }, + ... +} + +``` + +``` + +MCBearerContextReleaseRequestIEs EIAP-PROTOCOL-IES ::= { + { ID id-GNB-CU-CP-MBS-EIAP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-EIAP-ID PRESENCE mandatory } | + { ID id-GNB-CU-UP-MBS-EIAP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-EIAP-ID PRESENCE mandatory } | + +``` + +``` +{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, +... +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- MC BEARER NOTIFICATION +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +MCBearerNotification ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MCBearerNotificationIEs } }, + ... +} +``` + +``` +MCBearerNotificationIEs E1AP-PROTOCOL-IEs ::= { + { ID id-GNB-CU-CP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-CP-MBS-E1AP-ID PRESENCE mandatory } | + { ID id-GNB-CU-UP-MBS-E1AP-ID CRITICALITY reject TYPE GNB-CU-UP-MBS-E1AP-ID PRESENCE mandatory } | + { ID id-MBSSessionResourceNotification CRITICALITY ignore TYPE MBSSessionResourceNotification PRESENCE mandatory }, + ... +} +``` + +``` +END +``` + +-- ASN1STOP + +## 9.4.5 Information Element Definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- Information Element Definitions + +-- + +-- \*\*\*\*\* + +ELAP-IEs { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-access (22) modules (3) elap (5) version1 (1) elap-IEs (2) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + +id-CommonNetworkInstance, + +id-SNSSAI, + +id-OldQoSFlowMap-ULendmarkerexpected, + +id-DRB-QoS, + +id-endpoint-IP-Address-and-Port, +id-NetworkInstance, +id-QoSFlowMappingIndication, +id-TNLAssociationTransportLayerAddressgNBCUUP, +id-Cause, +id-QoSMonitoringRequest, +id-QoSMonitoringReportingFrequency, +id-QoSMonitoringDisabled, +id-PDCP-StatusReportIndication, +id-RedundantCommonNetworkInstance, +id-redundant-nG-UL-UP-TNL-Information, +id-redundant-nG-DL-UP-TNL-Information, +id-RedundantQoSFlowIndicator, +id-TSCTrafficCharacteristics, +id-ExtendedPacketDelayBudget, +id-CNPacketDelayBudgetDownlink, +id-CNPacketDelayBudgetUplink, +id-AdditionalPDCPduplicationInformation, +id-RedundantPDUSessionInformation, +id-RedundantPDUSessionInformation-used, +id-QoS-Mapping-Information, +id-MDTConfiguration, +id-TraceCollectionEntityURI, +id-EHC-Parameters, +id-DAPSRequestInfo, + +id-EarlyForwardingCOUNTReq, +id-EarlyForwardingCOUNTInfo, +id-AlternativeQoSParaSetList, +id-MCG-OfferedGBRQoSFlowInfo, +id-Number-of-tunnels, +id-DataForwardingtoE-UTRANInformationList, +id-DataForwardingtoNG-RANQoSFlowInformationList, +id-MaxCIDEHCDL, +id-ignoreMappingRuleIndication, +id-EarlyDataForwardingIndicator, +id-QoSFlowsDRBRemapping, +id-SecurityIndicationModify, +id-DataForwardingSourceIPAddress, +id-M4ReportAmount, +id-M6ReportAmount, +id-M7ReportAmount, +id-PDUSession-PairID, +id-SurvivalTime, +id-UDC-Parameters, +id-SecurityIndication, +id-SecurityResult, +id-SDTindicatorSetup, +id-SDTindicatorMod, +id-DiscardTimerExtended, + +id-MCForwardingResourceRequest, +id-MCForwardingResourceIndication, +id-MCForwardingResourceResponse, +id-MCForwardingResourceRelease, +id-MCForwardingResourceReleaseIndication, +id-PDCP-COUNT-Reset, +id-MBSSessionAssociatedInfoNonSupportToSupport, +id-VersionID, +id-MBSAreaSessionID, +id-Secondary-PDU-Session-Data-Forwarding-Information, +id-MBSSessionResourceNotification, +id-MCBearerContextInactivityTimer, +id-MCBearerContextStatusChange, +id-SpecialTriggeringPurpose, +id-FlUTunnelNotEstablished, +id-PDUSetQoSParameters, +id-N6JitterInformation, +id-ECNMarkingorCongestionInformationReportingRequest, +id-ECNMarkingorCongestionInformationReportingStatus, +id-PDUSetbasedHandlingIndicator, +id-IndirectPathIndication, +maxnoofMBSAreaSessionIDs, +maxnoofSharedNG-UTerminations, + +maxnoofMRBs, +maxnoofMBSSessionIDs, +maxnoofQoSParaSets, +maxnoofErrors, +maxnoofSliceItems, +maxnoofEUTRANQoSParameters, +maxnoofNGRANQoSParameters, +maxnoofDRBs, +maxnoofPDUSessionResource, +maxnoofQoSFlows, +maxnoofUPParameters, +maxnoofCellGroups, +maxnooftimeperiods, +maxnoofNRCGI, +maxnoofTLAs, +maxnoofGTPTLAs, +maxnoofSPLMNs, +maxnoofMDTPLMNs, +maxnoofExtSliceItems, +maxnoofDataForwardingTunneltoE-UTRAN, +maxnoofExtNRCGI, +maxnoofECGI, +maxnoofSMBRValues, +maxnoofCellsforMBS, +maxnoofTAIforMBS, + +``` +maxnoofMBSServiceAreaInformation + +FROM E1AP-Constants + + Criticality, + ProcedureCode, + ProtocolIE-ID, + TriggeringMessage + +FROM E1AP-CommonDataTypes + + ProtocolExtensionContainer{}, + ProtocolIE-SingleContainer{}, + E1AP-PROTOCOL-EXTENSION, + E1AP-PROTOCOL-IES + +FROM E1AP-Containers; + +-- A + +ActivityInformation ::= CHOICE { + dRB-Activity-List DRB-Activity-List, + pDU-Session-Resource-Activity-List PDU-Session-Resource-Activity-List, +``` + +``` + uE-Activity UE-Activity, + choice-extension ProtocolIE-SingleContainer {{ActivityInformation-ExtIEs}} +} +``` + +``` +ActivityInformation-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +ActivityNotificationLevel ::= ENUMERATED { + drb, + pdu-session, + ue, + ... +} +``` + +``` +AdditionalHandoverInfo ::= ENUMERATED { + discard-pdpc-SN, + ... +} +``` + +``` +AdditionalPDCPduplicationInformation ::= ENUMERATED { + three, + four, + ... +} +``` + +AdditionalRRMPriorityIndex ::= BIT STRING (SIZE(32)) + +AveragingWindow ::= INTEGER (0..4095, ...) + +AlternativeQoSParaSetList ::= SEQUENCE (SIZE(1..maxnoofQoSParaSets)) OF AlternativeQoSParaSetItem + +AlternativeQoSParaSetItem ::= SEQUENCE { +    alternativeQoSParameterIndex    INTEGER(1..8, ...), +    guaranteedFlowBitRateDL        BitRate                OPTIONAL, +    guaranteedFlowBitRateUL        BitRate                OPTIONAL, +    packetDelayBudget                PacketDelayBudget    OPTIONAL, +    packetErrorRate                    PacketErrorRate        OPTIONAL, +    iE-Extensions                    ProtocolExtensionContainer { {AlternativeQoSParaSetItem-ExtIEs} }    OPTIONAL, +    ... +} + +AlternativeQoSParaSetItem-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +    ... +} + +AssociatedSessionID ::= OCTET STRING + +-- B + +-- BCBearerContextToSetup + +``` +BCBearerContextToSetup ::= SEQUENCE { + snssai SNSSAI, + bcBearerContextNGU-TNLInfoat5GC BCBearerContextNGU-TNLInfoat5GC OPTIONAL, + bcMRBToSetupList BCMRBSetupConfiguration, + requestedAction RequestedAction4AvailNGUTermination OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {BCBearerContextToSetup-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +BCBearerContextToSetup-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BCBearerContextNGU-TNLInfoat5GC ::= CHOICE { + locationindependent MBSNGUInformationAt5GC, + locationdependent LocationDependentMBSNGUInformationAt5GC, + choice-extension ProtocolIE-SingleContainer { {BCBearerContextNGU-TNLInfoat5GC-ExtIEs} } +} +``` + +``` +BCBearerContextNGU-TNLInfoat5GC-ExtIEs E1AP-PROTOCOL-IES ::= { +``` + +``` + + ... + } + + BCMRBSetupConfiguration ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF BCMRBSetupConfiguration-Item + + BCMRBSetupConfiguration-Item ::= SEQUENCE { + mrb-ID MRB-ID, + mbs-pdcp-config PDCP-Configuration, + qos-Flow-QoS-Parameter-List QoS-Flow-QoS-Parameter-List, + qosFlowLevelQoSParameters QoSFlowLevelQoSParameters OPTIONAL, + iE-Extensions ProtocolExtensionContainer { BCMRBSetupConfiguration-Item-ExtIEs } OPTIONAL, + ... + } + + BCMRBSetupConfiguration-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- BCBearerContextToSetupResponse + + BCBearerContextToSetupResponse ::= SEQUENCE { + bcBearerContextNGU-TNLInfoatNGRAN BCBearerContextNGU-TNLInfoatNGRAN OPTIONAL, + bcMRBSetupResponseList BCMRBSetupResponseList, + bcMRBFailedList BCMRBFailedList OPTIONAL, + availableBCMRBConfig BCMRBSetupConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { BCBearerContextToSetupResponse-ExtIEs } OPTIONAL, + ... + } + +``` + +``` +BCBearerContextToSetupResponse-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +BCBearerContextNGU-TNLInfoatNGRAN ::= CHOICE { + locationindependent MBSNGUInformationAtNGRAN, + locationdependent LocationDependentMBSNGUInformationAtNGRAN, + choice-extension ProtocolIE-SingleContainer {BCBearerContextNGU-TNLInfoatNGRAN-ExtIEs} +} + +BCBearerContextNGU-TNLInfoatNGRAN-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +BCMRBSetupResponseList ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF BCMRBSetupResponseList-Item +BCMRBSetupResponseList-Item ::= SEQUENCE { + mrb-ID MRB-ID, + qosflow-setup QoS-Flow-List, + qosflow-failed QoS-Flow-Failed-List OPTIONAL, + bcBearerContextFlU-TNLInfoatCU BCBearerContextFlU-TNLInfoatCU, + iE-Extensions ProtocolExtensionContainer { BCMRBSetupResponseList-Item-ExtIEs } OPTIONAL, + ... +} +``` + +``` +BCMRBSetupResponseList-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +BCBearerContextFlU-TNLInfoatCU ::= CHOICE { + locationindependent MBSFlUInformationAtCU, + locationdependent LocationDependentMBSFlUInformationAtCU, + choice-extension ProtocolIE-SingleContainer {BCBearerContextFlU-TNLInfoatCU-ExtIEs} +} + +BCBearerContextFlU-TNLInfoatCU-ExtIEs E1AP-PROTOCOL-IES ::= { + ... +} + +BCMRBFailedList ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF BCMRBFailedList-Item +BCMRBFailedList-Item ::= SEQUENCE { + mrb-ID MRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { BCMRBFailedList-Item-ExtIEs } OPTIONAL, + ... +} +``` + +``` +BCMRFailedList-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- BCBearerContextToModify + +BCBearerContextToModify ::= SEQUENCE { + bcBearerContextNGU-TNLInfoat5GC BCBearerContextNGU-TNLInfoat5GC OPTIONAL, + bcMRBToSetupList BCMRBSetupConfiguration OPTIONAL, + bcMRBToModifyList BCMRBModifyConfiguration OPTIONAL, + bcMRBToRemoveList BCMRBRemoveConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {BCBearerContextToModify-ExtIEs} } OPTIONAL, + ... +} + +BCBearerContextToModify-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + { ID id-FlUTunnelNotEstablished CRITICALITY ignore EXTENSION FlUTunnelNotEstablished PRESENCE optional}, + ... +} + +BCMRBModifyConfiguration ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF BCMRBModifyConfiguration-Item + +BCMRBModifyConfiguration-Item ::= SEQUENCE { +``` + +``` + mrb-ID MRB-ID, + bcBearerContextFlU-TNLInfoatDU BCBearerContextFlU-TNLInfoatDU OPTIONAL, + mbs-pdcp-config PDCP-Configuration OPTIONAL, + qos-Flow-QoS-Parameter-List QoS-Flow-QoS-Parameter-List OPTIONAL, + qosFlowLevelQoSParameters QoSFlowLevelQoSParameters OPTIONAL, + iE-Extensions ProtocolExtensionContainer { BCMRBModifyConfiguration-Item-ExtIEs } OPTIONAL, + ... +} + +BCMRBModifyConfiguration-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +BCBearerContextFlU-TNLInfoatDU ::= CHOICE { + locationindependent MBSFlUInformationAtDU, + locationdependent LocationDependentMBSFlUInformationAtDU, + choice-extension ProtocolIE-SingleContainer {BCBearerContextFlU-TNLInfoatDU-ExtIEs} +} + +BCBearerContextFlU-TNLInfoatDU-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +BCMRBRemoveConfiguration ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MRB-ID +``` + +-- BCBearerContextToModifyResponse + +``` +BCBearerContextToModifyResponse ::= SEQUENCE { + bcBearerContextNGU-TNLInfoatNGRAN BCBearerContextNGU-TNLInfoatNGRAN OPTIONAL, + bcMRBSetupModifyResponseList BCMRBSetupModifyResponseList, + bcMRBFailedList BCMRBFailedList OPTIONAL, + availableBCMRBConfig BCMRBSetupConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {BCBearerContextToModifyResponse-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +BCBearerContextToModifyResponse-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BCMRBSetupModifyResponseList ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF BCMRBSetupModifyResponseList-Item +``` + +``` +BCMRBSetupModifyResponseList-Item ::= SEQUENCE { + mrb-ID MRB-ID, + qosflow-setup QoS-Flow-List OPTIONAL, + qosflow-failed QoS-Flow-Failed-List OPTIONAL, + bcBearerContextFlU-TNLInfoatCU BCBearerContextFlU-TNLInfoatCU OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {BCMRSSetupModifyResponseList-Item-ExtIEs} } OPTIONAL, + ... +} + +BCMRSSetupModifyResponseList-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- BCBearerContextToModifyRequired + +BCBearerContextToModifyRequired ::= SEQUENCE { + bcMRBToRemoveList BCMRBRemoveConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {BCBearerContextToModifyRequired-ExtIEs} } OPTIONAL, + ... +} + +BCBearerContextToModifyRequired-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- BCBearerContextToModifyConfirm + +BCBearerContextToModifyConfirm ::= SEQUENCE { +``` + +``` +iE-Extensions ProtocolExtensionContainer { {BCBearerContextToModifyConfirm-ExtIEs} } OPTIONAL, +... +} +``` + +``` +BCBearerContextToModifyConfirm-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +... +} +``` + +``` +BearerContextStatusChange ::= ENUMERATED { +suspend, +resume, +... , +resumeforSDT +} +``` + +``` +BitRate ::= INTEGER (0..40000000000000, ...) +``` + +``` +BufferSize ::= ENUMERATED { +kbyte2, +kbyte4, +kbyte8, +... +} +``` + +``` +-- C +``` + +``` +Cause ::= CHOICE { + radioNetwork CauseRadioNetwork, + transport CauseTransport, + protocol CauseProtocol, + misc CauseMisc, + choice-extension ProtocolIE-SingleContainer {{Cause-ExtIEs}} +} +``` + +``` +Cause-ExtIEs EIAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +CauseMisc ::= ENUMERATED { + control-processing-overload, + not-enough-user-plane-processing-resources, + hardware-failure, + om-intervention, + unspecified, + ... +} +``` + +``` +CauseProtocol ::= ENUMERATED { + transfer-syntax-error, + abstract-syntax-error-reject, +``` + +``` +abstract-syntax-error-ignore-and-notify, +message-not-compatible-with-receiver-state, +semantic-error, +abstract-syntax-error-falsely-constructed-message, +unspecified, +... +} +``` + +``` +CauseRadioNetwork ::= ENUMERATED { + unspecified, + unknown-or-already-allocated-gnb-cu-cp-ue-elap-id, + unknown-or-already-allocated-gnb-cu-up-ue-elap-id, + unknown-or-inconsistent-pair-of-ue-elap-id, + interaction-with-other-procedure, + pPDCP-Count-wrap-around, + not-supported-QCI-value, + not-supported-5QI-value, + encryption-algorithms-not-supported, + integrity-protection-algorithms-not-supported, + uP-integrity-protection-not-possible, + uP-confidentiality-protection-not-possible, + multiple-PDU-Session-ID-Instances, + unknown-PDU-Session-ID, + multiple-QoS-Flow-ID-Instances, + unknown-QoS-Flow-ID, +``` + +multiple-DRB-ID-Instances, +unknown-DRB-ID, +invalid-QoS-combination, +procedure-cancelled, +normal-release, +no-radio-resources-available, +action-desirable-for-radio-reasons, +resources-not-available-for-the-slice, +pDCP-configuration-not-supported, +... +ue-dl-max-IP-data-rate-reason, +uP-integrity-protection-failure, +release-due-to-pre-emption, +rsn-not-available-for-the-up, +nPN-not-supported, +report-characteristic-empty, +existing-measurement-ID, +measurement-temporarily-not-available, +measurement-not-supported-for-the-object, +scg-activation-deactivation-failure, +scg-deactivation-failure-due-to-data-transmission, +unknown-or-already-allocated-gNB-CU-CP-MBS-E1AP-ID, +unknown-or-already-allocated-gNB-CU-UP-MBS-E1AP-ID, +unknown-or-inconsistent-pair-of-MBS-E1AP-ID, +unknown-or-inconsistent-MRB-ID + +``` +} + +CauseTransport ::= ENUMERATED { + unspecified, + transport-resource-unavailable, + ..., + unknown-TNL-address-for-IAB +} + +Cell-Group-Information ::= SEQUENCE (SIZE(1.. maxnoofCellGroups)) OF Cell-Group-Information-Item + +Cell-Group-Information-Item ::= SEQUENCE { + cell-Group-ID Cell-Group-ID, + uL-Configuration uL-Configuration OPTIONAL, + dL-TX-Stop dL-TX-Stop OPTIONAL, + rAT-Type rAT-Type OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Cell-Group-Information-Item-ExtIEs } } OPTIONAL, + ... +} + +Cell-Group-Information-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + { ID id-Number-of-tunnels CRITICALITY ignore EXTENSION Number-of-tunnels PRESENCE optional }, + ... +} +``` + +Cell-Group-ID := INTEGER (0..3, ...) + +CHOInitiation := ENUMERATED {true, ...} + +Number-of-tunnels := INTEGER (1..4, ...) + +CipheringAlgorithm := ENUMERATED { +    nEA0, +    c-128-NEA1, +    c-128-NEA2, +    c-128-NEA3, +    ... +} + +CNSupport := ENUMERATED { +    c-epc, +    c-5gc, +    both, +    ... +} + +CommonNetworkInstance := OCTET STRING + +ConfidentialityProtectionIndication := ENUMERATED { + +``` + required, + preferred, + not-needed, + ... +} +``` + +``` +ConfidentialityProtectionResult ::= ENUMERATED { + performed, + not-performed, + ... +} +``` + +``` +CP-TNL-Information ::= CHOICE { + endpoint-IP-Address TransportLayerAddress, + choice-extension ProtocolIE-SingleContainer {{CP-TNL-Information-ExtIEs}} +} +``` + +``` +CP-TNL-Information-ExtIEs ELAP-PROTOCOL-IES ::= { + { ID id-endpoint-IP-Address-and-Port CRITICALITY reject TYPE Endpoint-IP-address-and-port PRESENCE mandatory}, + ... +} +``` + +``` +CriticalityDiagnostics ::= SEQUENCE { +``` + +``` +procedureCode ProcedureCode OPTIONAL, +triggeringMessage TriggeringMessage OPTIONAL, +procedureCriticality Criticality OPTIONAL, +transactionID TransactionID OPTIONAL, +iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, +iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, +... +} +``` + +``` +CriticalityDiagnostics-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +... +} +``` + +``` +CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxnoofErrors)) OF +SEQUENCE { + iECriticality Criticality, + iE-ID ProtocolIE-ID, + typeOfError TypeOfError, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +CriticalityDiagnostics-IE-List-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +... +} +``` + +``` +} + +-- D + +DAPSRequestInfo ::= SEQUENCE { + dapsIndicator ENUMERATED {daps-HO-required, ...}, + iE-Extensions ProtocolExtensionContainer { {DAPSRequestInfo-ExtIEs} } OPTIONAL, + ... +} + +DAPSRequestInfo-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +Data-Forwarding-Information-Request ::= SEQUENCE { + data-Forwarding-Request Data-Forwarding-Request, + qos-Flows-Forwarded-On-Fwd-Tunnels QoS-Flow-Mapping-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Data-Forwarding-Information-Request-ExtIEs } } OPTIONAL, + ... +} + +Data-Forwarding-Information-Request-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Data-Forwarding-Information ::= SEQUENCE { + uL-Data-Forwarding UP-TNL-Information OPTIONAL, + dL-Data-Forwarding UP-TNL-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Data-Forwarding-Information-ExtIEs } } OPTIONAL, + ... +} + +Data-Forwarding-Information-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-DataForwardingtoNG-RANQoSFlowInformationList CRITICALITY ignore EXTENSION DataForwardingtoNG-RANQoSFlowInformationList PRESENCE +optional}| + {ID id-PDUSetbasedHandlingIndicator CRITICALITY ignore EXTENSION PDUSetbasedHandlingIndicator PRESENCE optional}, + ... +} + +Data-Forwarding-Request ::= ENUMERATED { + uL, + dL, + both, + ... +} + +DataForwardingtoE-UTRANInformationList ::= SEQUENCE (SIZE(1.. maxnoofDataForwardingTunneltoE-UTRAN)) OF DataForwardingtoE-UTRANInformationListItem + +DataForwardingtoE-UTRANInformationListItem ::= SEQUENCE { + data-forwarding-tunnel-information UP-TNL-Information, +``` + +``` + qosFlows-to-be-forwarded-List qosFlows-to-be-forwarded-List, + iE-Extensions ProtocolExtensionContainer { { DataForwardingtoE-UTRANInformationListItem-ExtIEs } } OPTIONAL, + ... +} + +DataForwardingtoE-UTRANInformationListItem-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +Data-Usage-per-PDU-Session-Report ::= SEQUENCE { + secondaryRATType ENUMERATED {nR, e-UTRA, ...}, + pdu-session-Timed-Report-List SEQUENCE (SIZE(1..maxnooftimeperiods)) OF MRDC-Data-Usage-Report-Item, + iE-Extensions ProtocolExtensionContainer { { Data-Usage-per-PDU-Session-Report-ExtIEs } } OPTIONAL, + ... +} + +Data-Usage-per-PDU-Session-Report-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +Data-Usage-per-QoS-Flow-List ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF Data-Usage-per-QoS-Flow-Item + +Data-Usage-per-QoS-Flow-Item ::= SEQUENCE { + qosFlow-Identifier QoS-Flow-Identifier, +``` + +``` + secondaryRATType ENUMERATED {nR, e-UTRA, ...}, + qosFlow-Timed-Report-List SEQUENCE (SIZE(1..maxnooftimeperiods)) OF MRDC-Data-Usage-Report-Item, + iE-Extensions ProtocolExtensionContainer { { Data-Usage-per-QoS-Flow-Item-ExtIEs} } OPTIONAL, + ... +} + +Data-Usage-per-QoS-Flow-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +Data-Usage-Report-List ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF Data-Usage-Report-Item + +Data-Usage-Report-Item ::= SEQUENCE { + dRB-ID DRB-ID, + rAT-Type RAT-Type, + dRB-Usage-Report-List DRB-Usage-Report-List, + iE-Extensions ProtocolExtensionContainer { { Data-Usage-Report-ItemExtIEs } } OPTIONAL, + ... +} + +Data-Usage-Report-ItemExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +DefaultDRB ::= ENUMERATED { +``` + +``` + true, + false, + ... +} + +Dictionary ::= ENUMERATED { + sip-SDP, + operator, + ... +} + +DirectForwardingPathAvailability ::= ENUMERATED { + inter-system-direct-path-available, + ..., + intra-system-direct-path-available +} + +DiscardTimer ::= ENUMERATED {ms10, ms20, ms30, ms40, ms50, ms60, ms75, ms100, ms150, ms200, ms250, ms300, ms500, ms750, ms1500, infinity} + +DiscardTimerExtended ::= ENUMERATED {ms0dot5, ms1, ms2, ms4, ms6, ms8, ..., ms2000} + +DLDiscarding ::= SEQUENCE { + dLDiscardingCountVal PDCP-Count, + iE-Extensions ProtocolExtensionContainer { { DLDiscarding-ExtIEs } } OPTIONAL +} +``` + +``` +DLDiscarding-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DLUPTNLAddressToUpdateItem ::= SEQUENCE { + oldTNLAddress TransportLayerAddress, + newTNLAddress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { DLUPTNLAddressToUpdateItemExtIEs } } OPTIONAL, + ... +} + +DLUPTNLAddressToUpdateItemExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-TX-Stop ::= ENUMERATED { + stop, + resume, + ... +} + +DRB-Activity ::= ENUMERATED { + active, + not-active, +``` + +``` + ... +} + +DRB-Activity-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRB-Activity-Item + +DRB-Activity-Item ::= SEQUENCE { + dRB-ID DRB-ID, + dRB-Activity DRB-Activity, + iE-Extensions ProtocolExtensionContainer { { DRB-Activity-ItemExtIEs } } OPTIONAL, + ... +} + +DRB-Activity-ItemExtIEs EIAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Confirm-Modified-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Confirm-Modified-Item-EUTRAN + +DRB-Confirm-Modified-Item-EUTRAN ::= SEQUENCE { + dRB-ID DRB-ID, + cellGroup-Information Cell-Group-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Confirm-Modified-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +DRB-Confirm-Modified-Item-EUTRAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Confirm-Modified-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Confirm-Modified-Item-NG-RAN + +DRB-Confirm-Modified-Item-NG-RAN ::= SEQUENCE { + dRB-ID DRB-ID, + cellGroup-Information Cell-Group-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Confirm-Modified-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Confirm-Modified-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Failed-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Failed-Item-EUTRAN + +DRB-Failed-Item-EUTRAN ::= SEQUENCE { + dRB-ID DRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Failed-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +DRB-Failed-Item-EUTRAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Failed-Mod-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Failed-Mod-Item-EUTRAN + +DRB-Failed-Mod-Item-EUTRAN ::= SEQUENCE { + dRB-ID dRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Failed-Mod-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Failed-Mod-Item-EUTRAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Failed-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Failed-Item-NG-RAN + +DRB-Failed-Item-NG-RAN ::= SEQUENCE { + dRB-ID dRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Failed-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +} + +DRB-Failed-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Failed-Mod-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Failed-Mod-Item-NG-RAN + +DRB-Failed-Mod-Item-NG-RAN ::= SEQUENCE { + dRB-ID dRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Failed-Mod-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Failed-Mod-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Failed-To-Modify-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Failed-To-Modify-Item-EUTRAN + +DRB-Failed-To-Modify-Item-EUTRAN ::= SEQUENCE { + dRB-ID dRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Failed-To-Modify-Item-EUTRAN-ExtIEs } } OPTIONAL, +``` + +``` + ... +} + +DRB-Failed-To-Modify-Item-EUTRAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Failed-To-Modify-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Failed-To-Modify-Item-NG-RAN + +DRB-Failed-To-Modify-Item-NG-RAN ::= SEQUENCE { + dRB-ID dRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Failed-To-Modify-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Failed-To-Modify-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-ID ::= INTEGER (1..32, ...) + +DRB-Measurement-Results-Information-List ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Measurement-Results-Information-Item + +DRB-Measurement-Results-Information-Item ::= SEQUENCE { + dRB-ID dRB-ID, + uL-DL-Result INTEGER (0..10000, ...) OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { DRB-Measurement-Results-Information-Item-ExtIEs } } OPTIONAL, + ... +} + +DRB-Measurement-Results-Information-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Modified-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Modified-Item-EUTRAN + +DRB-Modified-Item-EUTRAN ::= SEQUENCE { + dRB-ID dRB-ID, + s1-DL-UP-TNL-Information UP-TNL-Information OPTIONAL, + pDCP-SN-Status-Information PDCP-SN-Status-Information OPTIONAL, + uL-UP-Transport-Parameters UP-Parameters OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Modified-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Modified-Item-EUTRAN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Modified-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Modified-Item-NG-RAN +``` + +``` + +DRB-Modified-Item-NG-RAN ::= SEQUENCE { + dRB-ID DRB-ID, + uL-UP-Transport-Parameters UP-Parameters OPTIONAL, + pDCP-SN-Status-Information PDCP-SN-Status-Information OPTIONAL, + flow-Setup-List QoS-Flow-List OPTIONAL, + flow-Failed-List QoS-Flow-Failed-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Modified-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Modified-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-EarlyForwardingCOUNTInfo CRITICALITY reject EXTENSION EarlyForwardingCOUNTInfo PRESENCE optional}| + {ID id-OldQoSFlowMap-ULendmarkerexpected CRITICALITY ignore EXTENSION QoS-Flow-List PRESENCE optional}, + ... +} + +DRB-Removed-Item ::= SEQUENCE { + dRB-ID DRB-ID, + dRB-Released-In-Session ENUMERATED {released-in-session, not-released-in-session, ...} OPTIONAL, + dRB-Accumulated-Session-Time OCTET STRING (SIZE(5)) OPTIONAL, + qoS-Flow-Removed-List SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF QoS-Flow-Removed-Item OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Removed-Item-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` +DRB-Removed-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Required-To-Modify-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Required-To-Modify-Item-EUTRAN + +DRB-Required-To-Modify-Item-EUTRAN ::= SEQUENCE { + dRB-ID dRB-ID, + s1-DL-UP-TNL-Information UP-TNL-Information OPTIONAL, + gNB-CU-UP-CellGroupRelatedConfiguration GNB-CU-UP-CellGroupRelatedConfiguration OPTIONAL, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Required-To-Modify-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Required-To-Modify-Item-EUTRAN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Required-To-Modify-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Required-To-Modify-Item-NG-RAN + +DRB-Required-To-Modify-Item-NG-RAN ::= SEQUENCE { + dRB-ID dRB-ID, + gNB-CU-UP-CellGroupRelatedConfiguration GNB-CU-UP-CellGroupRelatedConfiguration OPTIONAL, +``` + +``` + + flow-To-Remove QoS-Flow-List OPTIONAL, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Required-To-Modify-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... + } + + DRB-Required-To-Modify-Item-NG-RAN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... + } + + DRB-Setup-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Setup-Item-EUTRAN + + DRB-Setup-Item-EUTRAN ::= SEQUENCE { + dRB-ID DRB-ID, + sl-DL-UP-TNL-Information UP-TNL-Information, + data-Forwarding-Information-Response Data-Forwarding-Information OPTIONAL, + uL-UP-Transport-Parameters UP-Parameters, + sl-DL-UP-Unchanged ENUMERATED {true, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Setup-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... + } + + DRB-Setup-Item-EUTRAN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + {ID id-DataForwardingSourceIPAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}| + +``` + +``` +{ID id-SecurityResult CRITICALITY ignore EXTENSION SecurityResult PRESENCE optional}, +... +} +``` + +``` +DRB-Setup-Mod-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Setup-Mod-Item-EUTRAN +``` + +``` +DRB-Setup-Mod-Item-EUTRAN ::= SEQUENCE { + dRB-ID DRB-ID, + s1-DL-UP-TNL-Information UP-TNL-Information, + data-Forwarding-Information-Response Data-Forwarding-Information OPTIONAL, + uL-UP-Transport-Parameters UP-Parameters, + iE-Extensions ProtocolExtensionContainer { { DRB-Setup-Mod-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +DRB-Setup-Mod-Item-EUTRAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-SecurityResult CRITICALITY ignore EXTENSION SecurityResult PRESENCE optional}| + {ID id-DataForwardingSourceIPAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}, + ... +} +``` + +``` +DRB-Setup-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Setup-Item-NG-RAN +``` + +``` +DRB-Setup-Item-NG-RAN ::= SEQUENCE { + dRB-ID DRB-ID, +``` + +``` + + dRB-data-Forwarding-Information-Response Data-Forwarding-Information OPTIONAL, + uL-UP-Transport-Parameters UP-Parameters, + flow-Setup-List QoS-Flow-List, + flow-Failed-List QoS-Flow-Failed-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Setup-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Setup-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Setup-Mod-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Setup-Mod-Item-NG-RAN + +DRB-Setup-Mod-Item-NG-RAN ::= SEQUENCE { + dRB-ID DRB-ID, + dRB-data-Forwarding-Information-Response Data-Forwarding-Information OPTIONAL, + uL-UP-Transport-Parameters UP-Parameters, + flow-Setup-List QoS-Flow-List, + flow-Failed-List QoS-Flow-Failed-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Setup-Mod-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Setup-Mod-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + +``` + +``` +... +} + +DRB-Status-Item ::= SEQUENCE { + dRB-ID DRB-ID, + pDCP-DL-Count PDCP-Count OPTIONAL, + pDCP-UL-Count PDCP-Count OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Status-ItemExtIEs } } OPTIONAL, + ... +} + +DRB-Status-ItemExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRBs-Subject-To-Counter-Check-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRBs-Subject-To-Counter-Check-Item-EUTRAN + +DRBs-Subject-To-Counter-Check-Item-EUTRAN ::= SEQUENCE { + dRB-ID DRB-ID, + pDCP-UL-Count PDCP-Count, + pDCP-DL-Count PDCP-Count, + iE-Extensions ProtocolExtensionContainer { { DRBs-Subject-To-Counter-Check-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +DRBs-Subject-To-Counter-Check-Item-EUTRAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRBs-Subject-To-Counter-Check-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRBs-Subject-To-Counter-Check-Item-NG-RAN + +DRBs-Subject-To-Counter-Check-Item-NG-RAN ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + dRB-ID DRB-ID, + pDCP-UL-Count PDCP-Count, + pDCP-DL-Count PDCP-Count, + iE-Extensions ProtocolExtensionContainer { { DRBs-Subject-To-Counter-Check-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRBs-Subject-To-Counter-Check-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRBs-Subject-To-Early-Forwarding-List ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRBs-Subject-To-Early-Forwarding-Item + +DRBs-Subject-To-Early-Forwarding-Item ::= SEQUENCE { + dRB-ID DRB-ID, + dLCountValue PDCP-Count, + iE-Extensions ProtocolExtensionContainer { { DRBs-Subject-To-Early-Forwarding-Item-ExtIEs } } OPTIONAL, +``` + +``` + + ... + } + + DRBs-Subject-To-Early-Forwarding-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... + } + + DRB-To-Modify-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-To-Modify-Item-EUTRAN + + DRB-To-Modify-Item-EUTRAN ::= SEQUENCE { + dRB-ID dRB-ID, + pDCP-Configuration pDCP-Configuration OPTIONAL, + eUTRAN-QoS eUTRAN-QoS OPTIONAL, + sl-UL-UP-TNL-Information UP-TNL-Information OPTIONAL, + data-Forwarding-Information Data-Forwarding-Information OPTIONAL, + pDCP-SN-Status-Request pDCP-SN-Status-Request OPTIONAL, + pDCP-SN-Status-Information pDCP-SN-Status-Information OPTIONAL, + dL-UP-Parameters UP-Parameters OPTIONAL, + cell-Group-To-Add Cell-Group-Information OPTIONAL, + cell-Group-To-Modify Cell-Group-Information OPTIONAL, + cell-Group-To-Remove Cell-Group-Information OPTIONAL, + dRB-Inactivity-Timer Inactivity-Timer OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-To-Modify-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... + } + +``` + +``` + +DRB-To-Modify-Item-EUTRAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-To-Modify-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-To-Modify-Item-NG-RAN + +DRB-To-Modify-Item-NG-RAN ::= SEQUENCE { + dRB-ID DRB-ID, + sDAP-Configuration SDAP-Configuration OPTIONAL, + pDCP-Configuration PDCP-Configuration OPTIONAL, + dRB-Data-Forwarding-Information Data-Forwarding-Information OPTIONAL, + pDCP-SN-Status-Request PDCP-SN-Status-Request OPTIONAL, + pdcp-SN-Status-Information PDCP-SN-Status-Information OPTIONAL, + dL-UP-Parameters UP-Parameters OPTIONAL, + cell-Group-To-Add Cell-Group-Information OPTIONAL, + cell-Group-To-Modify Cell-Group-Information OPTIONAL, + cell-Group-To-Remove Cell-Group-Information OPTIONAL, + flow-Mapping-Information QoS-Flow-QoS-Parameter-List OPTIONAL, + dRB-Inactivity-Timer Inactivity-Timer OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-To-Modify-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-To-Modify-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + +``` + +``` + + {ID id-OldQoSFlowMap-ULendmarkerexpected CRITICALITY reject EXTENSION QoS-Flow-List PRESENCE optional}| + {ID id-DRB-QoS CRITICALITY ignore EXTENSION QoSFlowLevelQoSParameters PRESENCE optional}| + {ID id-EarlyForwardingCOUNTReq CRITICALITY reject EXTENSION EarlyForwardingCOUNTReq PRESENCE optional}| + {ID id-EarlyForwardingCOUNTInfo CRITICALITY reject EXTENSION EarlyForwardingCOUNTInfo PRESENCE optional}| + {ID id-DAPSRequestInfo CRITICALITY ignore EXTENSION DAPSRequestInfo PRESENCE optional}| + {ID id-EarlyDataForwardingIndicator CRITICALITY ignore EXTENSION EarlyDataForwardingIndicator PRESENCE optional}| + {ID id-SDTIndicatorMod CRITICALITY reject EXTENSION SDTIndicatorMod PRESENCE optional}| + {ID id-PDCP-COUNT-Reset CRITICALITY reject EXTENSION PDCP-COUNT-Reset PRESENCE optional }, + ... +} + +DRB-To-Remove-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-To-Remove-Item-EUTRAN + +DRB-To-Remove-Item-EUTRAN ::= SEQUENCE { + dRB-ID DRB-ID, + iE-Extensions ProtocolExtensionContainer { { DRB-To-Remove-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-To-Remove-Item-EUTRAN-ExtIEs ::= E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Required-To-Remove-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Required-To-Remove-Item-EUTRAN + +``` + +``` +DRB-Required-To-Remove-Item-EUTRAN ::= SEQUENCE { + dRB-ID DRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Required-To-Remove-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Required-To-Remove-Item-EUTRAN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-To-Remove-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-To-Remove-Item-NG-RAN + +DRB-To-Remove-Item-NG-RAN ::= SEQUENCE { + dRB-ID DRB-ID, + iE-Extensions ProtocolExtensionContainer { { DRB-To-Remove-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-To-Remove-Item-NG-RAN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Required-To-Remove-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Required-To-Remove-Item-NG-RAN +``` + +``` +DRB-Required-To-Remove-Item-NG-RAN ::= SEQUENCE { + dRB-ID dRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Required-To-Remove-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-Required-To-Remove-Item-NG-RAN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-To-Setup-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-To-Setup-Item-EUTRAN + +DRB-To-Setup-Item-EUTRAN ::= SEQUENCE { + dRB-ID dRB-ID, + pDCP-Configuration pDCP-Configuration, + eUTRAN-QoS eUTRAN-QoS, + s1-UL-UP-TNL-Information UP-TNL-Information, + data-Forwarding-Information-Request Data-Forwarding-Information-Request OPTIONAL, + cell-Group-Information Cell-Group-Information, + dL-UP-Parameters UP-Parameters OPTIONAL, + dRB-Inactivity-Timer Inactivity-Timer OPTIONAL, + existing-Allocated-S1-DL-UP-TNL-Info UP-TNL-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-To-Setup-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} +``` + +``` + +} + +DRB-To-Setup-Item-EUTRAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-DataForwardingSourceIPAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}| + {ID id-SecurityIndication CRITICALITY reject EXTENSION SecurityIndication PRESENCE optional}, + ... +} + +DRB-To-Setup-Mod-List-EUTRAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-To-Setup-Mod-Item-EUTRAN + +DRB-To-Setup-Mod-Item-EUTRAN ::= SEQUENCE { + dRB-ID DRB-ID, + pDCP-Configuration PDCP-Configuration, + eUTRAN-QoS EUTRAN-QoS, + s1-UL-UP-TNL-Information UP-TNL-Information, + data-Forwarding-Information-Request Data-Forwarding-Information-Request OPTIONAL, + cell-Group-Information Cell-Group-Information, + dL-UP-Parameters UP-Parameters OPTIONAL, + dRB-Inactivity-Timer Inactivity-Timer OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-To-Setup-Mod-Item-EUTRAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-To-Setup-Mod-Item-EUTRAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-SecurityIndication CRITICALITY reject EXTENSION SecurityIndication PRESENCE optional}| + +``` + +``` + + {ID id-DataForwardingSourceIPAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}, + ... +} + +``` + +``` + +DRB-To-Setup-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-To-Setup-Item-NG-RAN + +``` + +``` + +DRB-To-Setup-Item-NG-RAN ::= SEQUENCE { + dRB-ID DRB-ID, + sDAP-Configuration SDAP-Configuration, + pDCP-Configuration PDCP-Configuration, + cell-Group-Information Cell-Group-Information, + qos-flow-Information-To-Be-Setup QoS-Flow-QoS-Parameter-List, + dRB-Data-Forwarding-Information-Request Data-Forwarding-Information-Request OPTIONAL, + dRB-Inactivity-Timer Inactivity-Timer OPTIONAL, + pDCP-SN-Status-Information PDCP-SN-Status-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-To-Setup-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +DRB-To-Setup-Item-NG-RAN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + {ID id-DRB-QoS CRITICALITY ignore EXTENSION QoSFlowLevelQoSParameters PRESENCE optional}| + {ID id-DAPSRequestInfo CRITICALITY ignore EXTENSION DAPSRequestInfo PRESENCE optional}| + {ID id-ignoreMappingRuleIndication CRITICALITY reject EXTENSION IgnoreMappingRuleIndication PRESENCE optional}| + {ID id-QoSFlowsDRBRemapping CRITICALITY reject EXTENSION QoS-Flows-DRB-Remapping PRESENCE optional}| + {ID id-SDTIndicatorSetup CRITICALITY reject EXTENSION SDTIndicatorSetup PRESENCE optional}| +} + +``` + +``` + + {ID id-SpecialTriggeringPurpose CRITICALITY ignore EXTENSION SpecialTriggeringPurpose PRESENCE optional}, + ... +} + +DRB-To-Setup-Mod-List-NG-RAN ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-To-Setup-Mod-Item-NG-RAN + +DRB-To-Setup-Mod-Item-NG-RAN ::= SEQUENCE { + dRB-ID DRB-ID, + sDAP-Configuration SDAP-Configuration, + pDCP-Configuration PDCP-Configuration, + cell-Group-Information Cell-Group-Information, + flow-Mapping-Information QoS-Flow-QoS-Parameter-List, + dRB-Data-Forwarding-Information-Request Data-Forwarding-Information-Request OPTIONAL, + dRB-Inactivity-Timer Inactivity-Timer OPTIONAL, + pDCP-SN-Status-Information PDCP-SN-Status-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-To-Setup-Mod-Item-NG-RAN-ExtIEs } } OPTIONAL, + ... +} + +DRB-To-Setup-Mod-Item-NG-RAN-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-DRB-QoS CRITICALITY ignore EXTENSION QoSFlowLevelQoSParameters PRESENCE optional}| + {ID id-ignoreMappingRuleIndication CRITICALITY reject EXTENSION IgnoreMappingRuleIndication PRESENCE optional}| + {ID id-DAPSRequestInfo CRITICALITY ignore EXTENSION DAPSRequestInfo PRESENCE optional}| + {ID id-SDTIndicatorSetup CRITICALITY reject EXTENSION SDTIndicatorSetup PRESENCE optional}| + {ID id-SpecialTriggeringPurpose CRITICALITY ignore EXTENSION SpecialTriggeringPurpose PRESENCE optional}, + +``` + +``` + ... +} + +DRB-Usage-Report-List ::= SEQUENCE (SIZE(1..maxnooftimeperiods)) OF DRB-Usage-Report-Item + +DRB-Usage-Report-Item ::= SEQUENCE { + startTimeStamp OCTET STRING (SIZE(4)), + endTimeStamp OCTET STRING (SIZE(4)), + usageCountUL INTEGER (0..18446744073709551615), + usageCountDL INTEGER (0..18446744073709551615), + iE-Extensions ProtocolExtensionContainer { { DRB-Usage-Report-Item-ExtIEs} } OPTIONAL, + ... +} + +DRB-Usage-Report-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +Duplication-Activation ::= ENUMERATED { + active, + inactive, + ... +} +``` + +``` + +Dynamic5QIDescriptor ::= SEQUENCE { + qosPriorityLevel QoSPriorityLevel, + packetDelayBudget PacketDelayBudget, + packetErrorRate PacketErrorRate, + fiveQI INTEGER (0..255, ...) OPTIONAL, + delayCritical ENUMERATED {delay-critical, non-delay-critical} OPTIONAL, + averagingWindow AveragingWindow OPTIONAL, + maxDataBurstVolume MaxDataBurstVolume OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Dynamic5QIDescriptor-ExtIEs } } OPTIONAL +} + +Dynamic5QIDescriptor-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedPacketDelayBudget CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }| + { ID id-CNPacketDelayBudgetDownlink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }| + { ID id-CNPacketDelayBudgetUplink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }, + ... +} + +DataDiscardRequired ::= ENUMERATED { + required, + ... +} + +-- E + +``` + +EarlyDataForwardingIndicator ::= ENUMERATED {stop, ...} + +EarlyForwardingCOUNTInfo ::= CHOICE { +    firstDLCount                FirstDLCount, +    dLDiscardingCount          DLDiscarding, +    choice-Extension          ProtocolIE-SingleContainer { { EarlyForwardingCOUNTInfo-ExtIEs } } +} + +EarlyForwardingCOUNTInfo-ExtIEs ELAP-PROTOCOL-IES ::= { +    ... +} + +EarlyForwardingCOUNTReq ::= ENUMERATED { first-dl-count, dl-discarding, ... } + +ECNMarkingorCongestionInformationReportingRequest ::= CHOICE { +    eCNMarkingatNGRAN          ENUMERATED { ul, dl, both, stop, ... }, +    eCNMarkingatUPF            ENUMERATED { ul, dl, both, stop, ... }, +    congestionInformation      ENUMERATED { ul, dl, both, stop, ... }, +    choice-extension          ProtocolIE-SingleContainer {ECNMarkingorCongestionInformationReportingRequest-ExtIEs} +} + +ECNMarkingorCongestionInformationReportingRequest-ExtIEs ELAP-PROTOCOL-IES ::= { +    ... +} + +ECNMarkingorCongestionInformationReportingStatus ::= ENUMERATED { active, not-active, ...} + +EHC-Common-Parameters ::= SEQUENCE { +    ehc-CID-Length                    ENUMERATED { bits7, bits15, ...}, +    iE-Extensions                    ProtocolExtensionContainer { { EHC-Common-Parameters-ExtIEs } }    OPTIONAL +} + +EHC-Common-Parameters-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +    ... +} + +EHC-Downlink-Parameters ::= SEQUENCE { +    drb-ContinueEHC-DL                ENUMERATED { true, ..., false}, +    iE-Extensions                    ProtocolExtensionContainer { { EHC-Downlink-Parameters-ExtIEs } }    OPTIONAL +} + +EHC-Downlink-Parameters-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +    { ID id-MaxCIDEHCDL            CRITICALITY ignore    EXTENSION    MaxCIDEHCDL    PRESENCE optional    }, +    ... +} + +``` +EHC-Uplink-Parameters ::= SEQUENCE { + drb-ContinueEHC-UL ENUMERATED {true, ... , false}, + iE-Extensions ProtocolExtensionContainer { { EHC-Uplink-Parameters-ExtIEs } } OPTIONAL +} +``` + +``` +EHC-Uplink-Parameters-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +EHC-Parameters ::= SEQUENCE { + ehc-Common EHC-Common-Parameters, + ehc-Downlink EHC-Downlink-Parameters OPTIONAL, + ehc-Uplink EHC-Uplink-Parameters OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { EHC-Parameters-ExtIEs } } OPTIONAL +} +``` + +``` +EHC-Parameters-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +EncryptionKey ::= OCTET STRING +``` + +``` +Endpoint-IP-address-and-port ::= SEQUENCE { + endpoint-IP-Address TransportLayerAddress, + portNumber PortNumber, + iE-Extensions ProtocolExtensionContainer { { Endpoint-IP-address-and-port-ExtIEs} } OPTIONAL +} +``` + +``` +Endpoint-IP-address-and-port-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +EUTRANAllocationAndRetentionPriority ::= SEQUENCE { + priorityLevel PriorityLevel, + pre-emptionCapability Pre-emptionCapability, + pre-emptionVulnerability Pre-emptionVulnerability, + iE-Extensions ProtocolExtensionContainer { {EUTRANAllocationAndRetentionPriority-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +ExtendedPacketDelayBudget ::= INTEGER (1..65535, ..., 65536..109999) +``` + +``` +EUTRANAllocationAndRetentionPriority-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +E-UTRAN-Cell-Identity ::= BIT STRING (SIZE(28)) + +ECGI ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + eUTRAN-Cell-Identity E-UTRAN-Cell-Identity, + iE-Extensions ProtocolExtensionContainer { { ECGI-ExtIEs } } OPTIONAL +} + +ECGI-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +ECGI-Support-List ::= SEQUENCE (SIZE(1.. maxnoofECGI)) OF ECGI-Support-Item + +ECGI-Support-Item ::= SEQUENCE { + eCGI ECGI, + iE-Extensions ProtocolExtensionContainer { { ECGI-Support-Item-ExtIEs } } OPTIONAL +} + +ECGI-Support-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRAN-QoS-Support-List ::= SEQUENCE (SIZE(1.. maxnoofEUTRANQoSParameters)) OF EUTRAN-QoS-Support-Item +``` + +``` +EUTRAN-QoS-Support-Item ::= SEQUENCE { + eUTRAN-QoS EUTRAN-QoS, + iE-Extensions ProtocolExtensionContainer { { EUTRAN-QoS-Support-Item-ExtIEs } } OPTIONAL +} + +EUTRAN-QoS-Support-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRAN-QoS ::= SEQUENCE { + qCI QCI, + eUTRANAllocationAndRetentionPriority EUTRANAllocationAndRetentionPriority, + gbrQosInformation GBR-QoSInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { EUTRAN-QoS-ExtIEs } } OPTIONAL, + ... +} + +EUTRAN-QoS-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +ExtendedSliceSupportList ::= SEQUENCE (SIZE(1.. maxnoofExtSliceItems)) OF Slice-Support-Item + +-- F +``` + +``` +FirstDLCount ::= SEQUENCE { + firstDLCountVal PDCP-Count, + iE-Extensions ProtocolExtensionContainer { { FirstDLCount-ExtIEs } } OPTIONAL +} + +FirstDLCount-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +FiveGS-TAC ::= OCTET STRING (SIZE(3)) + +-- G + +GlobalMBSSessionID ::= SEQUENCE { + tmgi OCTET STRING (SIZE(6)), + nid NID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GlobalMBSSessionID-ExtIEs } } OPTIONAL, + ... +} + +GlobalMBSSessionID-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +GNB-CU-CP-Name ::= PrintableString(SIZE(1..150,...)) + +Extended-GNB-CU-CP-Name ::= SEQUENCE { + gNB-CU-CP-NameVisibleString GNB-CU-CP-NameVisibleString OPTIONAL, + gNB-CU-CP-NameUTF8String GNB-CU-CP-NameUTF8String OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Extended-GNB-CU-CP-Name-ExtIEs } } OPTIONAL, + ... +} + +Extended-GNB-CU-CP-Name-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-CP-MBS-ELAP-ID ::= INTEGER (0..16777215) + +GNB-CU-CP-NameVisibleString ::= VisibleString(SIZE(1..150,...)) + +GNB-CU-CP-NameUTF8String ::= UTF8String(SIZE(1..150,...)) + +GNB-CU-CP-UE-ELAP-ID ::= INTEGER (0..4294967295) + +GNB-CU-UP-Capacity ::= INTEGER (0..255) + +GNB-CU-UP-CellGroupRelatedConfiguration ::= SEQUENCE (SIZE(1.. maxnoofUPParameters)) OF GNB-CU-UP-CellGroupRelatedConfiguration-Item +``` + +``` +GNB-CU-UP-CellGroupRelatedConfiguration-Item ::= SEQUENCE { + cell-Group-ID Cell-Group-ID, + uP-TNL-Information UP-TNL-Information, + uL-Configuration UL-Configuration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-UP-CellGroupRelatedConfiguration-Item-ExtIEs } } OPTIONAL +} + +GNB-CU-UP-CellGroupRelatedConfiguration-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-UP-ID ::= INTEGER (0..68719476735) + +GNB-CU-UP-MBS-Support-Info ::= SEQUENCE { + mbs-Support-Info-ToAdd-List MBS-Support-Info-ToAdd-List OPTIONAL, + mbs-Support-Info-ToRemove-List MBS-Support-Info-ToRemove-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-UP-MBS-Support-Info-ExtIEs } } OPTIONAL, + ... +} + +GNB-CU-UP-MBS-Support-Info-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +GNB-CU-UP-Name ::= PrintableString(SIZE(1..150,...)) + +Extended-GNB-CU-UP-Name ::= SEQUENCE { + gNB-CU-UP-NameVisibleString GNB-CU-UP-NameVisibleString OPTIONAL, + gNB-CU-UP-NameUTF8String GNB-CU-UP-NameUTF8String OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Extended-GNB-CU-UP-Name-ExtIEs } } OPTIONAL, + ... +} + +Extended-GNB-CU-UP-Name-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-UP-MBS-ELAP-ID ::= INTEGER (0..65535) + +GNB-CU-UP-NameVisibleString ::= VisibleString(SIZE(1..150,...)) + +GNB-CU-UP-NameUTF8String ::= UTF8String(SIZE(1..150,...)) + +GNB-CU-UP-UE-ELAP-ID ::= INTEGER (0..4294967295) + +GNB-CU-CP-TNLA-Setup-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TNL-Information, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { GNB-CU-CP-TNLA-Setup-Item-ExtIEs} } OPTIONAL, + ... +} + +GNB-CU-CP-TNLA-Setup-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-CP-TNLA-Failed-To-Setup-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TNL-Information, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-CP-TNLA-Failed-To-Setup-Item-ExtIEs} } OPTIONAL +} + +GNB-CU-CP-TNLA-Failed-To-Setup-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-CP-TNLA-To-Add-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TNL-Information, + tNLAssociationUsage TNLAssociationUsage, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-CP-TNLA-To-Add-Item-ExtIEs} } OPTIONAL +} +``` + +``` +GNB-CU-CP-TNLA-To-Add-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +GNB-CU-CP-TNLA-To-Remove-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TNL-Information, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-CP-TNLA-To-Remove-Item-ExtIEs} } OPTIONAL +} +``` + +``` +GNB-CU-CP-TNLA-To-Remove-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + {ID id-TNLAssociationTransportLayerAddressgNBCUUP CRITICALITY reject EXTENSION CP-TNL-Information PRESENCE optional}, + ... +} +``` + +``` +GNB-CU-CP-TNLA-To-Update-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TNL-Information, + tNLAssociationUsage TNLAssociationUsage OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-CP-TNLA-To-Update-Item-ExtIEs} } OPTIONAL +} +``` + +``` +GNB-CU-CP-TNLA-To-Update-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +GNB-CU-UP-TNLA-To-Remove-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TNL-Information, + tNLAssociationTransportLayerAddressgNBCUCP CP-TNL-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-UP-TNLA-To-Remove-Item-ExtIEs} } OPTIONAL +} + +GNB-CU-UP-TNLA-To-Remove-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +GBR-QosInformation ::= SEQUENCE { + e-RAB-MaximumBitrateDL BitRate, + e-RAB-MaximumBitrateUL BitRate, + e-RAB-GuaranteedBitrateDL BitRate, + e-RAB-GuaranteedBitrateUL BitRate, + iE-Extensions ProtocolExtensionContainer { { GBR-QosInformation-ExtIEs} } OPTIONAL, + ... +} + +GBR-QosInformation-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +GBR-QoSFlowInformation ::= SEQUENCE { + maxFlowBitRateDownlink BitRate, + maxFlowBitRateUplink BitRate, + guaranteedFlowBitRateDownlink BitRate, + guaranteedFlowBitRateUplink BitRate, + maxPacketLossRateDownlink MaxPacketLossRate OPTIONAL, + maxPacketLossRateUplink MaxPacketLossRate OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GBR-QoSFlowInformation-ExtIEs } } OPTIONAL, + ... +} + +GBR-QoSFlowInformation-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-AlternativeQoSParaSetList CRITICALITY ignore EXTENSION AlternativeQoSParaSetList PRESENCE optional}, + ... +} + +GTP-TEID ::= OCTET STRING (SIZE (4)) + +GTPTLAs ::= SEQUENCE (SIZE(1.. maxnoofGTPTLAs)) OF GTPTLA-Item + +GTPTLA-Item ::= SEQUENCE { + gTPTransportLayerAddresses TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { GTPTLA-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +} +``` + +``` +GTPTLA-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +GTP Tunnel ::= SEQUENCE { +``` + +``` + transportLayerAddress TransportLayerAddress, +``` + +``` + gTP-TEID GTP-TEID, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { GTP Tunnel-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +GTP Tunnel-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +GNB-CU-UP-OverloadInformation ::= ENUMERATED {overloaded, not-overloaded} +``` + +``` +GNB-DU-ID ::= INTEGER (0..68719476735) +``` + +``` +-- H +``` + +``` +HFN ::= INTEGER (0..4294967295) +``` + +``` +HW-CapacityIndicator ::= SEQUENCE { + offeredThroughput INTEGER (1..16777216, ...), + availableThroughput INTEGER (0..100, ...), + iE-Extensions ProtocolExtensionContainer { { HW-CapacityIndicator-ExtIEs } } OPTIONAL, + ... +} + +HW-CapacityIndicator-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- I + +IndirectPathIndication ::= ENUMERATED { + true, + ... +} + +IgnoreMappingRuleIndication ::= ENUMERATED { + true, + ... +} +``` + +``` +IntegrityProtectionIndication ::= ENUMERATED { + required, + preferred, + not-needed, + ... +} +``` + +``` +IntegrityProtectionAlgorithm ::= ENUMERATED { + nIA0, + i-128-NIA1, + i-128-NIA2, + i-128-NIA3, + ... +} +``` + +``` +IntegrityProtectionKey ::= OCTET STRING +``` + +``` +IntegrityProtectionResult ::= ENUMERATED { + performed, + not-performed, + ... +} +``` + +``` +Inactivity-Timer ::= INTEGER (1..7200, ...) +``` + +``` +InterfacesToTrace ::= BIT STRING (SIZE(8)) + +ImmediateMDT ::= SEQUENCE { + measurementsToActivate MeasurementsToActivate, + measurementFour M4Configuration OPTIONAL, + measurementSix M6Configuration OPTIONAL, + measurementSeven M7Configuration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ImmediateMDT-ExtIEs} } OPTIONAL, + ... +} + +ImmediateMDT-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +IAB-Donor-CU-UPPSKInfo-Item ::= SEQUENCE { + iAB-donor-CU-UPPSK IAB-donor-CU-UPPSK, + iAB-donor-CU-UPIPAddress TransportLayerAddress, + iAB-DUIPAddress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { IAB-donor-CU-UPPSKInfoItemExtIEs } } OPTIONAL, + ... +} + +IAB-donor-CU-UPPSKInfoItemExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +IAB-donor-CU-UPPSK ::= OCTET STRING + +InactivityInformationRequest ::= ENUMERATED {true, ...} + +-- J + +-- K + +-- L + +Links-to-log ::= ENUMERATED { + uplink, + downlink, + both-uplink-and-downlink, + ... +} + +LocationDependentMBSNGUInformationAt5GC ::= SEQUENCE (SIZE(1..maxnoofMBSAreaSessionIDs)) OF LocationDependentMBSNGUInformationAt5GC-Item + +LocationDependentMBSNGUInformationAt5GC-Item ::= SEQUENCE { + mbsAreaSession-ID                    MBSAreaSessionID, + mbsNGUInformationAt5GC             MBSNGUInformationAt5GC, + iE-Extensions                        ProtocolExtensionContainer { { LocationDependentMBSNGUInformationAt5GC-Item-ExtIEs } } OPTIONAL, + ... +} + +``` +} + +LocationDependentMBSNGUInformationAt5GC-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +LocationDependentMBSF1UInformationAtCU ::= SEQUENCE (SIZE(1..maxnoofMBSAreaSessionIDs)) OF LocationDependentMBSF1UInformationAtCU-Item + +LocationDependentMBSF1UInformationAtCU-Item ::= SEQUENCE { + mbsAreaSession-ID MBSAreaSessionID, + mbs-flu-info-at-CU UP-TNL-Information, + iE-Extensions ProtocolExtensionContainer { { LocationDependentMBSF1UInformationAtCU-Item-ExtIEs } } OPTIONAL, + ... +} + +LocationDependentMBSF1UInformationAtCU-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +LocationDependentMBSF1UInformationAtDU ::= SEQUENCE (SIZE(1..maxnoofMBSAreaSessionIDs)) OF LocationDependentMBSF1UInformationAtDU-Item + +LocationDependentMBSF1UInformationAtDU-Item ::= SEQUENCE { + mbsAreaSession-ID MBSAreaSessionID, + mbs-flu-info-at-DU UP-TNL-Information, + iE-Extensions ProtocolExtensionContainer { { LocationDependentMBSF1UInformationAtDU-Item-ExtIEs } } OPTIONAL, +``` + +``` + ... +} + +LocationDependentMBSF1InformationAtDU-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +LocationDependentMBSNGUInformationAtNGRAN ::= SEQUENCE (SIZE(1..maxnoofMBSAreaSessionIDs)) OF LocationDependentMBSNGUInformationAtNGRAN-Item + +LocationDependentMBSNGUInformationAtNGRAN-Item ::= SEQUENCE { + mbsAreaSession-ID MBSAreaSessionID, + mbsNGUInformationAtNGRAN MBSNGUInformationAtNGRAN, + iE-Extensions ProtocolExtensionContainer { { LocationDependentMBSNGUInformationAtNGRAN-Item-ExtIEs } } OPTIONAL, + ... +} + +LocationDependentMBSNGUInformationAtNGRAN-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- M + +MaxDataBurstVolume ::= INTEGER (0..4095, ..., 4096.. 2000000) + +MaximumIPdatarate ::= SEQUENCE { +``` + +``` + maxIPRate MaxIPRate, + iE-Extensions ProtocolExtensionContainer { {MaximumIPdatarate-ExtIEs} } OPTIONAL, + ... + } + +MaximumIPdatarate-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MaxIPRate ::= ENUMERATED { + bitrate64kbs, + max-UErate, + ... +} + +MaxPacketLossRate ::= INTEGER (0..1000, ...) + +MaxCIDEHCDL ::= INTEGER (1..32767, ...) + +MBSAreaSessionID ::= INTEGER (0..65535, ...) + +MBSFluInformationAtCU ::= SEQUENCE { + mbs-flu-info-at-CU UP-TNL-Information, + iE-Extensions ProtocolExtensionContainer { { MBSFluInformationAtCU-ExtIEs } } OPTIONAL, + ... +} +``` + +} + +``` +MBSF1UInformationAtCU-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MBSF1UInformationAtDU ::= SEQUENCE { + mbs-flu-info-at-DU UP-TNL-Information, + iE-Extensions ProtocolExtensionContainer { { MBSF1UInformationAtDU-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +MBSF1UInformationAtDU-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MBSNGUInformationAt5GC ::= CHOICE { + multicast MBSNGUInformationAt5GC-Multicast, + choice-extension ProtocolIE-SingleContainer { {MBSNGUInformationAt5GC-ExtIEs} } +} +``` + +``` +MBSNGUInformationAt5GC-ExtIEs E1AP-PROTOCOL-IES ::= { + ... +} +``` + +``` +MBSNGUInformationAt5GC-Multicast ::= SEQUENCE { + ipmcAddress TransportLayerAddress, + ipsourceAddress TransportLayerAddress, + gtpDLTEID GTP-TEID, + iE-Extensions ProtocolExtensionContainer { {MBSNGUInformationAt5GC-Multicast-ExtIEs} } OPTIONAL, + ... +} + +MBSNGUInformationAt5GC-Multicast-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBSNGUInformationAtNGRAN ::= CHOICE { + unicast UP-TNL-Information, + choice-extension ProtocolIE-SingleContainer { {MBSNGUInformationAtNGRAN-ExtIEs} } +} + +MBSNGUInformationAtNGRAN-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +MBSSessionAssociatedInfoNonSupportToSupport ::= SEQUENCE { + ue-Reference-ID GNB-CU-CP-UE-ELAP-ID, +``` + +``` + pDU-Session-ID PDU-Session-ID, + associatedQoSFlowInformationList MBSSessionAssociatedInformationList, + iE-Extensions ProtocolExtensionContainer { {MBSSessionAssociatedInfoNonSupportToSupport-ExtIEs} } OPTIONAL, + ... +} + +MBSSessionAssociatedInfoNonSupportToSupport-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBSSessionAssociatedInformation ::= SEQUENCE { + mbsSessionAssociatedInformationList MBSSessionAssociatedInformationList, + mbsSessionForwardingAddress UP-TNL-Information, + iE-Extensions ProtocolExtensionContainer { {MBSSessionAssociatedInformation-ExtIEs} } OPTIONAL, + ... +} + +MBSSessionAssociatedInformation-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBSSessionAssociatedInformationList ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF MBSSessionAssociatedInformation-Item + +MBSSessionAssociatedInformation-Item ::= SEQUENCE { +``` + +``` + mbs-QoS-Flow-Identifier QoS-Flow-Identifier, + associated-unicast-QoS-Flow-Identifier QoS-Flow-Identifier, + iE-Extensions ProtocolExtensionContainer { { MBSSessionAssociatedInformation-Item-ExtIEs } } OPTIONAL, + ... +} + +MBSSessionAssociatedInformation-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-Support-Info-ToAdd-List ::= SEQUENCE (SIZE(1..maxnoofMBSSessionIDs)) OF MBS-Support-Info-ToAdd-Item + +MBS-Support-Info-ToAdd-Item ::= SEQUENCE { + globalMBSSessionID GlobalMBSSessionID, + iE-Extensions ProtocolExtensionContainer { { MBS-Support-Info-ToAdd-Item-ExtIEs } } OPTIONAL, + ... +} + +MBS-Support-Info-ToAdd-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-Support-Info-ToRemove-List ::= SEQUENCE (SIZE(1..maxnoofMBSSessionIDs)) OF MBS-Support-Info-ToRemove-Item +``` + +``` +MBSSessionResourceNotification ::= CHOICE { + mbs-DL-Data-Arrival MBS-DL-Data-Arrival, + inactivity MCBearerContext-Inactivity, + choice-extension ProtocolIE-SingleContainer {{ MBSSessionResourceNotification-ExtIEs}} +} + +MBSSessionResourceNotification-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +MBS-DL-Data-Arrival ::= SEQUENCE { + dlDataArrival ENUMERATED {true, ...}, + ppi PPI OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{ MBS-DL-Data-Arrival-ExtIEs}} OPTIONAL, + ... +} + +MBS-DL-Data-Arrival-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MCBearerContext-Inactivity ::= SEQUENCE { + mcBearerContext-Inactivity-Indication ENUMERATED {true, ...}, +} +``` + +``` + iE-Extensions ProtocolExtensionContainer { {MCBearerContext-Inactivity-ExtIEs} } OPTIONAL, + ... +} + +MCBearerContext-Inactivity-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-Support-Info-ToRemove-Item ::= SEQUENCE { + globalMBSSessionID GlobalMBSSessionID, + iE-Extensions ProtocolExtensionContainer { { MBS-Support-Info-ToRemove-Item-ExtIEs} } OPTIONAL, + ... +} + +MBS-Support-Info-ToRemove-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- MCBearerContextToSetup + +MCBearerContextToSetup ::= SEQUENCE { + snssai SNSSAI, + mcMRBToSetupList MCMBRSetupConfiguration OPTIONAL, + requestedAction RequestedAction4AvailNGUTermination OPTIONAL, +``` + +``` +iE-Extensions ProtocolExtensionContainer { MCBearerContextToSetup-ExtIEs } OPTIONAL, +... +} + +MCBearerContextToSetup-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-MBSSessionAssociatedInfoNonSupportToSupport CRITICALITY ignore EXTENSION MBSSessionAssociatedInfoNonSupportToSupport PRESENCE +optional}| + {ID id-MBSAreaSessionID CRITICALITY ignore EXTENSION MBSAreaSessionID PRESENCE optional}| + {ID id-MCBearerContextInactivityTimer CRITICALITY ignore EXTENSION Inactivity-Timer PRESENCE optional}| + {ID id-MCBearerContextStatusChange CRITICALITY ignore EXTENSION MCBearerContextStatusChange PRESENCE optional}, +... +} + +MCMBRSetupConfiguration ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MCMBRSetupConfiguration-Item + +MCMBRSetupConfiguration-Item ::= SEQUENCE { + mrb-ID MRB-ID, + mbs-pdcp-config PDCP-Configuration, + qos-Flow-QoS-Parameter-List QoS-Flow-QoS-Parameter-List, + qosFlowLevelQoSParameters QoSFlowLevelQoSParameters OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCMBRSetupConfiguration-Item-ExtIEs } OPTIONAL, + ... +} +``` + +``` + +MCMRBSetupConfiguration-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MCBearerContextStatusChange ::= ENUMERATED {suspend, resume, ...} + +-- MCBearerContextToSetupResponse + +MCBearerContextToSetupResponse ::= SEQUENCE { + mcBearerContextNGU-TNLInfoatNGRAN MCBearerContextNGU-TNLInfoatNGRAN OPTIONAL, + mcMRBSetupResponseList MCMRBSetupResponseList OPTIONAL, + mcMRBFailedList MCMRBFailedList OPTIONAL, + availableMCMRBConfig MCMRBSetupConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCBearerContextToSetupResponse-ExtIEs } OPTIONAL, + ... +} + +MCBearerContextToSetupResponse-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MCBearerContextNGU-TNLInfoatNGRAN ::= CHOICE { + locationindependent MBSNGUInformationAtNGRAN, + +``` + +``` + locationdependent LocationDependentMBSNGUInformationAtNGRAN, + choice-extension ProtocolIE-SingleContainer {MCBearerContextNGU-TNLInfoatNGRAN-ExtIEs} +} + +MCBearerContextNGU-TNLInfoatNGRAN-ExtIEs E1AP-PROTOCOL-IES ::= { + ... +} + +MCMBRSetupResponseList ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MCMBRSetupResponseList-Item + +MCMBRSetupResponseList-Item ::= SEQUENCE { + mrb-ID MRB-ID, + qosflow-setup QoS-Flow-List, + qosflow-failed QoS-Flow-Failed-List OPTIONAL, + mBS-PDCP-COUNT MBS-PDCP-COUNT OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCMBRSetupResponseList-Item-ExtIEs } OPTIONAL, + ... +} + +MCMBRSetupResponseList-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-PDCP-COUNT ::= BIT STRING (SIZE (32)) +``` + +``` +MCMRBFailedList ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MCMRBFailedList-Item +``` + +``` +MCMRBFailedList-Item ::= SEQUENCE { + mrb-ID MRB-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { {MCMRBFailedList-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MCMRBFailedList-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +-- MCBearerContextToModify +``` + +``` +MCBearerContextToModify ::= SEQUENCE { + mcBearerContextNGUTNLInfoat5GC MCBearerContextNGUTNLInfoat5GC OPTIONAL, + mcBearerContextNGUTnlInfoatNGRANRequest MCBearerContextNGUTnlInfoatNGRANRequest OPTIONAL, + mbsMulticastFlUContextDescriptor MBSMulticastFlUContextDescriptor OPTIONAL, + -- This IE shall be present if either the MC MRB To Setup or Modify List IE or the MC MRB To Remove List IE or both IEs are included. + requestedAction RequestedAction4AvailNGUTermination OPTIONAL, + mcMRBToSetupModifyList MCMRBSetupModifyConfiguration OPTIONAL, +} +``` + +``` + + mCMRBToRemoveList mCMRBRemoveConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { mCBearerContextToModify-ExtIEs } OPTIONAL, + ... +} + +mCBearerContextToModify-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + + {ID id-MCForwardingResourceRequest CRITICALITY ignore EXTENSION MCForwardingResourceRequest PRESENCE +optional}| + + {ID id-MCForwardingResourceIndication CRITICALITY ignore EXTENSION MCForwardingResourceIndication PRESENCE +optional}| + + {ID id-MCForwardingResourceRelease CRITICALITY ignore EXTENSION MCForwardingResourceRelease PRESENCE +optional}| + + {ID id-MBSSessionAssociatedInfoNonSupportToSupport CRITICALITY ignore EXTENSION MBSSessionAssociatedInfoNonSupportToSupport PRESENCE +optional}| + + {ID id-MCBearerContextInactivityTimer CRITICALITY ignore EXTENSION Inactivity-Timer PRESENCE +optional}| + + {ID id-MCBearerContextStatusChange CRITICALITY ignore EXTENSION mCBearerContextStatusChange PRESENCE +optional}| + + ... + +} + +mCBearerContextNGUTNLInfoat5GC ::= SEQUENCE { + + mbsNGUInformationAt5GC mBSNGUInformationAt5GC, + + mbsAreaSession-ID mBSAreaSessionID OPTIONAL, + + iE-Extensions ProtocolExtensionContainer { mCBearerContextNGUTNLInfoat5GC-ExtIEs } OPTIONAL, + + ... + +} + +``` + +``` + +MCBearerContextNGUTNLInfoat5GC-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MCBearerContextNGUTNLInfoatNGRANRequest ::= SEQUENCE { + ngRANNGUTNLRequested ENUMERATED {requested, ...}, + mbsAreaSession-ID MBSAreaSessionID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCBearerContextNGUTNLInfoatNGRANRequest-ExtIEs } OPTIONAL, + ... +} + +MCBearerContextNGUTNLInfoatNGRANRequest-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MCMBRSetupModifyConfiguration ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MCMBRSetupModifyConfiguration-Item + +MCMBRSetupModifyConfiguration-Item ::= SEQUENCE { + mrb-ID MRB-ID, + flUTNLatDU MCBearerContextFLUTNLInfoatDU OPTIONAL, + mbs-pdcp-config PDCP-Configuration OPTIONAL, + qos-Flow-QoS-Parameter-List QoS-Flow-QoS-Parameter-List OPTIONAL, + mrbQoS QoSFlowLevelQoSParameters OPTIONAL, + mbs-PDCP-COUNT-Req MBS-PDCP-COUNT-Req OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCMBRSetupModifyConfiguration-Item-ExtIEs } OPTIONAL, +} + +``` + +``` + ... +} + +MCMBRSetupModifyConfiguration-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MCBearerContextFlUTNLInfoatDU ::= SEQUENCE { + mbsFlUInfoatDU UP-TNL-Information, + mbsMulticastFlUContextDescriptor MBSMulticastFlUContextDescriptor, + iE-Extensions ProtocolExtensionContainer { { MCBearerContextFlUTNLInfoatDU-ExtIEs } } OPTIONAL, + ... +} + +MCBearerContextFlUTNLInfoatDU-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MulticastFlUContextReferenceE1 ::= OCTET STRING (SIZE(4)) + +MBSMulticastFlUContextDescriptor ::= SEQUENCE { + multicastFlUContextReferenceE1 MulticastFlUContextReferenceE1, + mc-FlUCtxtusage ENUMERATED {ptm, ptp, ptp-retransmission, ptp-forwarding, ...}, + mbsAreaSession MBSAreaSessionID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MBSMulticastFlUContextDescriptor-ExtIEs } } OPTIONAL, +``` + +``` + + ... + } + + MBSMulticastFlUContextDescriptor-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... + } + + MCMBRRemoveConfiguration ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MRB-ID + + MBS-PDCP-COUNT-Req ::= ENUMERATED {true, ... } + + -- MCBearerContextToModifyResponse + + MCBearerContextToModifyResponse ::= SEQUENCE { + mcBearerContextNGU-TNLInfoatNGRANModifyResponse MCBearerContextNGU-TNLInfoatNGRANModifyResponse OPTIONAL, + mbsMulticastFlUContextDescriptor MBSMulticastFlUContextDescriptor OPTIONAL, + -- This IE shall be present if either the MC MRB Setup or Modify Response List IE or the MC MRB Failed List IE or both IEs are included. + mcMRBModifySetupResponseList MCMBRSetupModifyResponseList OPTIONAL, + mcMRBFailedList MCMRBFailedList OPTIONAL, + availableMCMBRConfig MCMBRSetupConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCBearerContextToModifyResponse-ExtIEs } OPTIONAL, + } + +``` + +``` + ... +} + +MCBearerContextToModifyResponse-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-MCForwardingResourceResponse CRITICALITY ignore EXTENSION MCForwardingResourceResponse PRESENCE optional}, + ... +} + +MCBearerContextNGU-TNLInfoatNGRANModifyResponse ::= SEQUENCE { + mbs-NGU-InfoatNGRAN MBSNGUInformationAtNGRAN, + mbsAreaSession MBSAreaSessionID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCBearerContextNGU-TNLInfoatNGRANModifyResponse-ExtIEs } OPTIONAL, + ... +} + +MCBearerContextNGU-TNLInfoatNGRANModifyResponse-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +MCMBRSetupModifyResponseList ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MCMBRSetupModifyResponseList-Item + +MCMBRSetupModifyResponseList-Item ::= SEQUENCE { + mrb-ID MRB-ID, + qosflow-setup QoS-Flow-List OPTIONAL, +} +``` + +``` + + qosflow-failed QoS-Flow-Failed-List OPTIONAL, + mcBearerContextFlUTNLInfoatCU UP-TNL-Information OPTIONAL, + mBS-PDCP-COUNT MBS-PDCP-COUNT OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MCMRBSetupModifyResponseList-Item-ExtIEs} } OPTIONAL, + ... +} + +MCMRBSetupModifyResponseList-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- MCBearerContextToModifyRequired + +MCBearerContextToModifyRequired ::= SEQUENCE { + mbsMulticastFlUContextDescriptor MBSMulticastFlUContextDescriptor OPTIONAL, + -- This IE shall be present if either the MC MRB To Remove List Required IE is included. + mcMRBToRemoveRequiredList MCMRBRemoveConfiguration OPTIONAL, + mcMRBToModifyRequiredList MCMRBModifyRequiredConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MCBearerContextToModifyRequired-ExtIEs} } OPTIONAL, + ... +} + +MCBearerContextToModifyRequired-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + {ID id-MCForwardingResourceReleaseIndication CRITICALITY ignore EXTENSION MCForwardingResourceReleaseIndication PRESENCE optional}, + +``` + +``` + ... +} + +MCMBRModifyRequiredConfiguration ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MCMBRModifyRequiredConfiguration-Item + +MCMBRModifyRequiredConfiguration-Item ::= SEQUENCE { + mrb-ID MRB-ID, + mBS-PDCP-COUNT mBS-PDCP-COUNT OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCMBRModifyRequiredConfiguration-Item-ExtIEs } OPTIONAL, + ... +} + +MCMBRModifyRequiredConfiguration-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- MCBearerContextToModifyConfirm + +MCBearerContextToModifyConfirm ::= SEQUENCE { + mbsMulticastFlUContextDescriptor MBSMulticastFlUContextDescriptor OPTIONAL, + mcMRBModifyConfirmList MCMBRModifyConfirmList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCBearerContextToModifyConfirm-ExtIEs } OPTIONAL, + ... +} +``` + +``` +MCMBRModifyConfirmList ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MCMBRModifyConfirmList-Item +``` + +``` +MCMBRModifyConfirmList-Item ::= SEQUENCE { + mrb-ID MRB-ID, + iE-Extensions ProtocolExtensionContainer { { MCMBRModifyConfirmList-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MCMBRModifyConfirmList-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MCBearerContextToModifyConfirm-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +-- MCForwardingResourceRequest +``` + +``` +MCForwardingResourceRequest ::= SEQUENCE { + mcForwardingResourceID MCForwardingResourceID, + mbsAreaSession-ID MBSAreaSessionID OPTIONAL, + mrbForwardingResourceRequestList MRBForwardingResourceRequestList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MCForwardingResourceRequest-ExtIEs} } OPTIONAL, +``` + +``` +... +} + +MCForwardingResourceRequest-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +MRBForwardingResourceRequestList ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF MRBForwardingResourceRequest-Item + +MRBForwardingResourceRequest-Item ::= SEQUENCE { + mrb-ID MRB-ID, + mrbProgressRequestType MRB-ProgressInformationType OPTIONAL, + mrbForwardingAddressRequest ENUMERATED {request, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MRBForwardingResourceRequest-Item-ExtIEs} } OPTIONAL, + ... +} + +MRBForwardingResourceRequest-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- MCForwardingResourceIndication +``` + +``` +MCForwardingResourceIndication ::= SEQUENCE { + mcForwardingResourceID MCForwardingResourceID, + mrbForwardingResourceIndicationList MRBFForwardingResourceIndicationList OPTIONAL, + mbsSessionAssociatedInformation MBSSessionAssociatedInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MCForwardingResourceIndication-ExtIEs} } OPTIONAL, + ... +} + +MCForwardingResourceIndication-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MRBFForwardingResourceIndicationList ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF MRBFForwardingResourceIndication-Item + +MRBFForwardingResourceIndication-Item ::= SEQUENCE { + mrb-ID MRB-ID, + mrb-ProgressInformation MRB-ProgressInformation OPTIONAL, + mrbForwardingAddress UP-TNL-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MRBFForwardingResourceIndication-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MRBForwardingResourceIndication-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- MCForwardingResourceResponse + +MCForwardingResourceResponse ::= SEQUENCE { + mcForwardingResourceID MCForwardingResourceID, + mrbForwardingResourceResponseList MRBForwardingResourceResponseList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MCForwardingResourceResponse-ExtIEs } OPTIONAL, + ... +} + +MCForwardingResourceResponse-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MRBForwardingResourceResponseList ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF MRBForwardingResourceResponse-Item + +MRBForwardingResourceResponse-Item ::= SEQUENCE { + mrb-ID MRB-ID, + mrb-ProgressInformation MRB-ProgressInformation OPTIONAL, +``` + +``` + mrbForwardingAddress UP-TNL-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MRBForwardingResourceResponse-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MRBForwardingResourceResponse-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +-- MCForwardingResourceRelease +``` + +``` +MCForwardingResourceRelease ::= SEQUENCE { + mcForwardingResourceID MCForwardingResourceID, + iE-Extensions ProtocolExtensionContainer { {MCForwardingResourceRelease-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MCForwardingResourceRelease-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +-- MCForwardingResourceReleaseIndication +``` + +``` +MCForwardingResourceReleaseIndication ::= SEQUENCE { + mcForwardingResourceID MCForwardingResourceID, + iE-Extensions ProtocolExtensionContainer { {MCForwardingResourceReleaseIndication-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MCForwardingResourceReleaseIndication-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MCForwardingResourceID ::= OCTET STRING (SIZE(2)) +``` + +``` +MDTPollutedMeasurementIndicator ::= ENUMERATED { + iDC, + no-IDC, + ... +} +``` + +``` +MRB-ID ::= INTEGER (1..512, ...) +``` + +``` +MRB-ProgressInformation ::= SEQUENCE { + mrb-ProgressInformationSNs MRB-ProgressInformationSNs, + mrb-ProgressInformationType MRB-ProgressInformationType, +``` + +``` +iE-Extensions ProtocolExtensionContainer { {MRB-ProgressInformation-ExtIEs} } OPTIONAL, +... +} + +MRB-ProgressInformation-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MRB-ProgressInformationSNs ::= CHOICE { + pdcp-SN12 INTEGER (0..4095), + pdcp-SN18 INTEGER (0..262143), + choice-extension ProtocolIE-SingleContainer { { MRB-ProgressInformationSNs-ExtIEs} } +} + +MRB-ProgressInformationSNs-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +MRB-ProgressInformationType ::= ENUMERATED {oldest-available, last-delivered, ...} + +MRDC-Data-Usage-Report-Item ::= SEQUENCE { + startTimestamp OCTET STRING (SIZE(4)), + endTimestamp OCTET STRING (SIZE(4)), + usageCountUL INTEGER (0..18446744073709551615), +``` + +``` +usageCountDL INTEGER (0..18446744073709551615), +iE-Extensions ProtocolExtensionContainer { { MRDC-Data-Usage-Report-Item-ExtIEs } } OPTIONAL, +... +} + +MRDC-Data-Usage-Report-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MRDC-Usage-Information ::= SEQUENCE { + data-Usage-per-PDU-Session-Report Data-Usage-per-PDU-Session-Report OPTIONAL, + data-Usage-per-QoS-Flow-List Data-Usage-per-QoS-Flow-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MRDC-Usage-Information-ExtIEs } } OPTIONAL, + ... +} + +MRDC-Usage-Information-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +M4Configuration ::= SEQUENCE { + m4period M4period, + m4-links-to-log Links-to-log, + iE-Extensions ProtocolExtensionContainer { { M4Configuration-ExtIEs } } OPTIONAL, + ... +} +``` + +} + +M4Configuration-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + +{ ID id-M4ReportAmount CRITICALITY ignore EXTENSION M4ReportAmount PRESENCE optional }, +... + +} + +M4period ::= ENUMERATED {ms1024, ms2048, ms5120, ms10240, min1, ... } + +M4ReportAmount ::= ENUMERATED { r1, r2, r4, r8, r16, r32, r64, infinity, ... } + +M6Configuration ::= SEQUENCE { + +m6report-Interval M6report-Interval, +m6-links-to-log Links-to-log, +iE-Extensions ProtocolExtensionContainer { { M6Configuration-ExtIEs} } OPTIONAL, +... + +} + +M6Configuration-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + +{ ID id-M6ReportAmount CRITICALITY ignore EXTENSION M6ReportAmount PRESENCE optional }, +... + +} + +M6ReportAmount ::= ENUMERATED { r1, r2, r4, r8, r16, r32, r64, infinity, ... } + +M6report-Interval ::= ENUMERATED { ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480 ,ms40960, min1, min6, min12, min30, ... } + +M7Configuration ::= SEQUENCE { +    m7period            M7period, +    m7-links-to-log    Links-to-log, +    iE-Extensions    ProtocolExtensionContainer { { M7Configuration-ExtIEs} } OPTIONAL, +    ... +} + +M7Configuration-ExtIEs EIAP-PROTOCOL-EXTENSION ::= { +    { ID id-M7ReportAmount    CRITICALITY ignore    EXTENSION M7ReportAmount    PRESENCE optional    }, +    ... +} + +M7period ::= INTEGER(1..60, ...) + +M7ReportAmount ::= ENUMERATED { r1, r2, r4, r8, r16, r32, r64, infinity, ... } + +MDT-Activation ::= ENUMERATED { +    immediate-MDT-only, +    immediate-MDT-and-Trace, +    ... +} + +MDT-Configuration ::= SEQUENCE { + +``` + mdt-Activation MDT-Activation, + mDTMode MDTMode, + iE-Extensions ProtocolExtensionContainer { { MDT-Configuration-ExtIEs} } OPTIONAL, + ... +} + +MDT-Configuration-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +MDTMode ::= CHOICE { + immediateMDT ImmediateMDT, + choice-extension ProtocolIE-SingleContainer { {MDTMode-ExtIEs} } +} + +MDTMode-ExtIEs E1AP-PROTOCOL-IES ::= { + ... +} + +MeasurementsToActivate ::= BIT STRING (SIZE (8)) + +MDTPLMNList ::= SEQUENCE (SIZE(1..maxnoofMDTPLMNs)) OF PLMN-Identity + +MDTPLMNModificationList ::= SEQUENCE (SIZE(0..maxnoofMDTPLMNs)) OF PLMN-Identity + +MT-SDT-Information ::= SEQUENCE { +``` + +``` + mT-SDT-Data-Size MT-SDT-Data-Size, + iE-Extensions ProtocolExtensionContainer { {MT-SDT-Information-ExtIEs} } OPTIONAL +} + +MT-SDT-Information-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +MT-SDT-Information-Request ::= ENUMERATED {true, ...} + +MT-SDT-Data-Size ::= INTEGER (1..96000, ...) + +MBS-ServiceArea ::= CHOICE { + locationdependent MBS-ServiceAreaInformationList, + choice-Extensions ProtocolIE-SingleContainer { {MBSServiceArea-ExtIEs} } +} + +MBSServiceArea-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +MBS-ServiceAreaInformation ::= SEQUENCE { +``` + +``` + mBS-ServiceAreaCellList MBS-ServiceAreaCellList OPTIONAL, + mBS-ServiceAreaTAList MBS-ServiceAreaTAList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MBS-ServiceAreaInformation-ExtIEs} } OPTIONAL, + ... + } + + MBS-ServiceAreaInformation-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... + } + + MBS-ServiceAreaCellList ::= SEQUENCE (SIZE(1.. maxnoofCellsforMBS)) OF NR-CGI + + MBS-ServiceAreaTAList ::= SEQUENCE (SIZE(1.. maxnoofTAforMBS)) OF MBS-ServiceAreaTAList-Item + + MBS-ServiceAreaTAList-Item ::= SEQUENCE { + plmn-ID PLMN-Identity, + five5-TAC FiveGS-TAC, + iE-Extensions ProtocolExtensionContainer { {MBS-ServiceAreaTAList-Item-ExtIEs} } OPTIONAL, + ... + } + + MBS-ServiceAreaTAList-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... + } +``` + +MBS-ServiceAreaInformationList ::= SEQUENCE (SIZE(1..maxnoofMBSServiceAreaInformation)) OF MBS-ServiceAreaInformationItem + +MBS-ServiceAreaInformationItem ::= SEQUENCE { +    mBS-AreaSessionID                  MBSAreaSessionID, +    mBS-ServiceAreaInformation      MBS-ServiceAreaInformation, +    iE-Extensions                      ProtocolExtensionContainer { { MBS-ServiceAreaInformationItem-ExtIEs} } OPTIONAL, +    ... +} + +MBS-ServiceAreaInformationItem-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +    ... +} + +-- N + +NetworkInstance ::= INTEGER (1..256, ...) + +New-UL-TNL-Information-Required ::= ENUMERATED { +    required, +    ... +} + +NGRANAllocationAndRetentionPriority ::= SEQUENCE { + +``` + priorityLevel PriorityLevel, + pre-emptionCapability Pre-emptionCapability, + pre-emptionVulnerability Pre-emptionVulnerability, + iE-Extensions ProtocolExtensionContainer { {NGRANAllocationAndRetentionPriority-ExtIEs} } OPTIONAL +} + +NGRANAllocationAndRetentionPriority-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +NG-RAN-QoS-Support-List ::= SEQUENCE (SIZE(1.. maxnoofNGRANQoSParameters)) OF NG-RAN-QoS-Support-Item + +NG-RAN-QoS-Support-Item ::= SEQUENCE { + non-Dynamic5QIDescriptor Non-Dynamic5QIDescriptor, + iE-Extensions ProtocolExtensionContainer { { NG-RAN-QoS-Support-Item-ExtIEs } } OPTIONAL +} + +NG-RAN-QoS-Support-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +NID ::= BIT STRING (SIZE (44)) + +Non-Dynamic5QIDescriptor ::= SEQUENCE { + fiveQI INTEGER (0..255, ...), +``` + +``` + qosPriorityLevel QoSPriorityLevel OPTIONAL, + averagingWindow AveragingWindow OPTIONAL, + maxDataBurstVolume MaxDataBurstVolume OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Non-Dynamic5QIDescriptor-ExtIEs } } OPTIONAL +} + +Non-Dynamic5QIDescriptor-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + { ID id-CNPacketDelayBudgetDownlink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional } | + { ID id-CNPacketDelayBudgetUplink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }, + ... +} + +NPNSupportInfo ::= CHOICE { + sNPN NPNSupportInfo-SNPN, + choice-extension ProtocolIE-SingleContainer { {NPNSupportInfo-ExtIEs} } +} + +NPNSupportInfo-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +NPNSupportInfo-SNPN ::= SEQUENCE { + nID NID, + iE-Extensions ProtocolExtensionContainer { { NPNSupportInfo-SNPN-ExtIEs } } OPTIONAL +} +``` + +``` +NPNSupportInfo-SNPN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +NPNContextInfo ::= CHOICE { + sNPN NPNContextInfo-SNPN, + choice-extension ProtocolIE-SingleContainer {{NPNContextInfo-ExtIEs}} +} + +NPNContextInfo-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +NPNContextInfo-SNPN ::= SEQUENCE { + nID NID, + iE-Extensions ProtocolExtensionContainer { {NPNContextInfo-SNPN-ExtIEs} } OPTIONAL +} + +NPNContextInfo-SNPN-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +NR-Cell-Identity ::= BIT STRING (SIZE(36)) +``` + +``` +NR-CGI ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + nR-Cell-Identity NR-Cell-Identity, + iE-Extensions ProtocolExtensionContainer { { NR-CGI-ExtIEs } } OPTIONAL +} + +NR-CGI-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +NR-CGI-Support-List ::= SEQUENCE (SIZE(1.. maxnoofNRCGI)) OF NR-CGI-Support-Item + +NR-CGI-Support-Item ::= SEQUENCE { + nR-CGI NR-CGI, + iE-Extensions ProtocolExtensionContainer { { NR-CGI-Support-Item-ExtIEs } } OPTIONAL +} + +NR-CGI-Support-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +Extended-NR-CGI-Support-List ::= SEQUENCE (SIZE(1.. maxnoofExtNRCGI)) OF Extended-NR-CGI-Support-Item + +Extended-NR-CGI-Support-Item ::= SEQUENCE { +``` + +``` + nR-CGI NR-CGI, + iE-Extensions ProtocolExtensionContainer { { Extended-NR-CGI-Support-Item-ExtIEs } } OPTIONAL +} + +Extended-NR-CGI-Support-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +N6JitterInformation ::= SEQUENCE { + n6JitterLowerBound INTEGER (-127..127), + n6JitterUpperBound INTEGER (-127..127), + iE-Extensions ProtocolExtensionContainer { { N6JitterInformationExtIEs } } OPTIONAL, + ... +} + +N6JitterInformationExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- O + +OutOfOrderDelivery ::= ENUMERATED { +``` + +``` + true, + ... +} + +-- P + +PacketDelayBudget ::= INTEGER (0..1023, ...) + +PacketErrorRate ::= SEQUENCE { + pER-Scalar PER-Scalar, + pER-Exponent PER-Exponent, + iE-Extensions ProtocolExtensionContainer { {PacketErrorRate-ExtIEs} } OPTIONAL, + ... +} + +PacketErrorRate-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +PER-Scalar ::= INTEGER (0..9, ...) +PER-Exponent ::= INTEGER (0..9, ...) +``` + +``` + +PDCP-Configuration ::= SEQUENCE { + + pDCP-SN-Size-UL PDCP-SN-Size, + pDCP-SN-Size-DL PDCP-SN-Size, + rLC-Mode RLC-Mode, + rOHC-Parameters ROHC-Parameters OPTIONAL, + t-ReorderingTimer T-ReorderingTimer OPTIONAL, + discardTimer DiscardTimer OPTIONAL, + uLDataSplitThreshold ULDataSplitThreshold OPTIONAL, + pDCP-Duplication PDCP-Duplication OPTIONAL, + pDCP-Reestablishment PDCP-Reestablishment OPTIONAL, + pDCP-DataRecovery PDCP-DataRecovery OPTIONAL, + duplication-Activation Duplication-Activation OPTIONAL, + outOfOrderDelivery OutOfOrderDelivery OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDCP-Configuration-ExtIEs } } OPTIONAL, + ... +} + +PDCP-Configuration-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + { ID id-PDCP-StatusReportIndication CRITICALITY ignore EXTENSION PDCP-StatusReportIndication PRESENCE optional } | + { ID id-AdditionalPDCPduplicationInformation CRITICALITY ignore EXTENSION AdditionalPDCPduplicationInformation PRESENCE optional } | + { ID id-EHC-Parameters CRITICALITY ignore EXTENSION EHC-Parameters PRESENCE optional } | + { ID id-UDC-Parameters CRITICALITY ignore EXTENSION UDC-Parameters PRESENCE optional } | + { ID id-DiscardTimerExtended CRITICALITY reject EXTENSION DiscardTimerExtended PRESENCE optional }, +} + +``` + +``` + ... +} + +PDCP-COUNT-Reset ::= ENUMERATED { + true, + ... +} + +PDCP-Count ::= SEQUENCE { + pDCP-SN PDCP-SN, + hFN HFN, + iE-Extensions ProtocolExtensionContainer { { PDCP-Count-ExtIEs } } OPTIONAL, + ... +} + +PDCP-Count-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +PDCP-SN-Status-Request ::= ENUMERATED { + requested, + ... +} + +PDCP-DataRecovery ::= ENUMERATED { +``` + +``` + true, + ... +} + +PDCP-Duplication ::= ENUMERATED { + true, + ... +} + +PDCP-Reestablishment ::= ENUMERATED { + true, + ... +} + +PDU-Session-Resource-Data-Usage-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Data-Usage-Item + +PDU-Session-Resource-Data-Usage-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + mRDC-Usage-Information MRDC-Usage-Information, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Data-Usage-Item-ExtIEs } } OPTIONAL, + ... +} + +PDU-Session-Resource-Data-Usage-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +PDCP-SN ::= INTEGER (0..262143) + +PDCP-SN-Size ::= ENUMERATED { + +s-12, + +s-18, + +..., + +s-7, + +s-15, + +s-16 + +} + +PDCP-SN-Status-Information ::= SEQUENCE { + +pdcpStatusTransfer-UL DRBBStatusTransfer, + +pdcpStatusTransfer-DL PDCP-Count, + +iE-Extension ProtocolExtensionContainer { { PDCP-SN-Status-Information-ExtIEs} } OPTIONAL, + +... + +} + +PDCP-StatusReportIndication ::= ENUMERATED { + +downlink, + +uplink, + +both, + +... + +} + +PDCP-SN-Status-Information-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + +... + +} + +DRBBStatusTransfer ::= SEQUENCE { + +    receiveStatusofPDCPSDU    BIT STRING (SIZE(1..131072))                                OPTIONAL, + +    countValue                PDCP-Count, + +    iE-Extension              ProtocolExtensionContainer { {DRBBStatusTransfer-ExtIEs} }  OPTIONAL, + +    ... + +} + +DRBBStatusTransfer-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + +    ... + +} + +PDU-Session-ID ::= INTEGER (0..255) + +PDUSession-PairID ::= INTEGER (0..255, ...) + +PDU-Session-Resource-Activity ::= ENUMERATED { + +    active, + +    not-active, + +    ... + +``` +} + +PDU-Session-Resource-Activity-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Activity-Item + +PDU-Session-Resource-Activity-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + pDU-Session-Resource-Activity PDU-Session-Resource-Activity, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Activity-ItemExtIEs } } OPTIONAL, + ... +} + +PDU-Session-Resource-Activity-ItemExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDU-Session-Resource-Confirm-Modified-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Confirm-Modified-Item + +PDU-Session-Resource-Confirm-Modified-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + dRB-Confirm-Modified-List-NG-RAN DRB-Confirm-Modified-List-NG-RAN OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Confirm-Modified-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PDU-Session-Resource-Confirm-Modified-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDU-Session-Resource-Failed-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Failed-Item + +PDU-Session-Resource-Failed-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Failed-Item-ExtIEs } } OPTIONAL, + ... +} + +PDU-Session-Resource-Failed-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDU-Session-Resource-Failed-Mod-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Failed-Mod-Item + +PDU-Session-Resource-Failed-Mod-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Failed-Mod-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PDU-Session-Resource-Failed-Mod-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDU-Session-Resource-Failed-To-Modify-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Failed-To-Modify-Item + +PDU-Session-Resource-Failed-To-Modify-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Failed-To-Modify-Item-ExtIEs } } OPTIONAL, + ... +} + +PDU-Session-Resource-Failed-To-Modify-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDU-Session-Resource-Modified-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Modified-Item + +PDU-Session-Resource-Modified-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + nG-DL-UP-TNL-Information UP-TNL-Information OPTIONAL, + securityResult SecurityResult OPTIONAL, + pDU-Session-Data-Forwarding-Information-Response Data-Forwarding-Information OPTIONAL, +``` + +``` + + dRB-Setup-List-NG-RAN dRB-Setup-List-NG-RAN OPTIONAL, + dRB-Failed-List-NG-RAN dRB-Failed-List-NG-RAN OPTIONAL, + dRB-Modified-List-NG-RAN dRB-Modified-List-NG-RAN OPTIONAL, + dRB-Failed-To-Modify-List-NG-RAN dRB-Failed-To-Modify-List-NG-RAN OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Modified-Item-ExtIEs } } OPTIONAL, + ... +} + +PDU-Session-Resource-Modified-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + { ID id-redundant-nG-DL-UP-TNL-Information CRITICALITY ignore EXTENSION UP-TNL-Information PRESENCE optional }, + ... +} + +PDU-Session-Resource-Required-To-Modify-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Required-To-Modify-Item + +PDU-Session-Resource-Required-To-Modify-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + nG-DL-UP-TNL-Information UP-TNL-Information OPTIONAL, + dRB-Required-To-Modify-List-NG-RAN dRB-Required-To-Modify-List-NG-RAN OPTIONAL, + dRB-Required-To-Remove-List-NG-RAN dRB-Required-To-Remove-List-NG-RAN OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Required-To-Modify-Item-ExtIEs } } OPTIONAL, + ... +} + +PDU-Session-Resource-Required-To-Modify-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + +``` + +``` +{ ID id-redundant-nG-DL-UP-TNL-Information CRITICALITY ignore EXTENSION UP-TNL-Information PRESENCE optional }, +... +} + +PDU-Session-Resource-Setup-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Setup-Item + +PDU-Session-Resource-Setup-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + securityResult SecurityResult OPTIONAL, + nG-DL-UP-TNL-Information UP-TNL-Information, + pDU-Session-Data-Forwarding-Information-Response Data-Forwarding-Information OPTIONAL, + nG-DL-UP-Unchanged ENUMERATED {true, ...} OPTIONAL, + dRB-Setup-List-NG-RAN DRB-Setup-List-NG-RAN, + dRB-Failed-List-NG-RAN DRB-Failed-List-NG-RAN OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Setup-Item-ExtIEs } } OPTIONAL, + ... +} + +PDU-Session-Resource-Setup-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + { ID id-redundant-nG-DL-UP-TNL-Information CRITICALITY ignore EXTENSION UP-TNL-Information PRESENCE optional }| + { ID id-RedundantPDUSessionInformation-used CRITICALITY ignore EXTENSION RedundantPDUSessionInformation PRESENCE optional }, + ... +} + +PDU-Session-Resource-Setup-Mod-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-Setup-Mod-Item +``` + +``` + +PDU-Session-Resource-Setup-Mod-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + securityResult SecurityResult OPTIONAL, + nG-DL-UP-TNL-Information UP-TNL-Information, + pDU-Session-Data-Forwarding-Information-Response Data-Forwarding-Information OPTIONAL, + dRB-Setup-Mod-List-NG-RAN DRB-Setup-Mod-List-NG-RAN, + dRB-Failed-Mod-List-NG-RAN DRB-Failed-Mod-List-NG-RAN OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-Setup-Mod-Item-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +PDU-Session-Resource-Setup-Mod-Item-ExtIEs EIAP-PROTOCOL-EXTENSION ::= { + { ID id-redundant-nG-DL-UP-TNL-Information CRITICALITY ignore EXTENSION UP-TNL-Information PRESENCE optional }, + ... +} + +``` + +``` + +PDU-Session-Resource-To-Modify-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-To-Modify-Item + +``` + +``` + +PDU-Session-Resource-To-Modify-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + securityIndication SecurityIndication OPTIONAL, + pDU-Session-Resource-DL-AMBR BitRate OPTIONAL, + nG-UL-UP-TNL-Information UP-TNL-Information OPTIONAL, + pDU-Session-Data-Forwarding-Information-Request Data-Forwarding-Information-Request OPTIONAL, +} + +``` + +``` + + pDU-Session-Data-Forwarding-Information Data-Forwarding-Information OPTIONAL, + pDU-Session-Inactivity-Timer Inactivity-Timer OPTIONAL, + networkInstance NetworkInstance OPTIONAL, + dRB-To-Setup-List-NG-RAN DRB-To-Setup-List-NG-RAN OPTIONAL, + dRB-To-Modify-List-NG-RAN DRB-To-Modify-List-NG-RAN OPTIONAL, + dRB-To-Remove-List-NG-RAN DRB-To-Remove-List-NG-RAN OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-To-Modify-Item-ExtIEs } } OPTIONAL, + ... +} + +PDU-Session-Resource-To-Modify-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + {ID id-SNSSAI CRITICALITY reject EXTENSION SNSSAI PRESENCE optional}| + {ID id-CommonNetworkInstance CRITICALITY ignore EXTENSION CommonNetworkInstance PRESENCE optional + }| + {ID id-redundant-nG-UL-UP-TNL-Information CRITICALITY ignore EXTENSION UP-TNL-Information PRESENCE optional }| + {ID id-RedundantCommonNetworkInstance CRITICALITY ignore EXTENSION CommonNetworkInstance PRESENCE optional }| + {ID id-DataForwardingtoE-UTRANInformationList CRITICALITY ignore EXTENSION DataForwardingtoE-UTRANInformationList PRESENCE optional }| + {ID id-SecurityIndicationModify CRITICALITY ignore EXTENSION SecurityIndication PRESENCE optional }| + {ID id-Secondary-PDU-Session-Data-Forwarding-Information CRITICALITY ignore EXTENSION Data-Forwarding-Information PRESENCE optional }, + ... +} + +PDU-Session-Resource-To-Remove-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-To-Remove-Item + +PDU-Session-Resource-To-Remove-Item ::= SEQUENCE { + +``` + +``` + + pDU-Session-ID pDU-Session-ID, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-To-Remove-Item-ExtIEs } } OPTIONAL, + ... + } + + PDU-Session-Resource-To-Remove-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + {ID id-Cause CRITICALITY ignore EXTENSION Cause PRESENCE optional}, + ... + } + + PDU-Session-Resource-To-Setup-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-To-Setup-Item + + PDU-Session-Resource-To-Setup-Item ::= SEQUENCE { + pDU-Session-ID pDU-Session-ID, + pDU-Session-Type pDU-Session-Type, + sNSSAI SNSSAI, + securityIndication SecurityIndication, + pDU-Session-Resource-DL-AMBR BitRate OPTIONAL, + nG-UL-UP-TNL-Information UP-TNL-Information, + pDU-Session-Data-Forwarding-Information-Request Data-Forwarding-Information-Request OPTIONAL, + pDU-Session-Inactivity-Timer Inactivity-Timer OPTIONAL, + existing-Allocated-NG-DL-UP-TNL-Info UP-TNL-Information OPTIONAL, + networkInstance NetworkInstance OPTIONAL, + dRB-To-Setup-List-NG-RAN dRB-To-Setup-List-NG-RAN, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-To-Setup-Item-ExtIEs } } OPTIONAL, + } + +``` + +``` + + ... + } + + PDU-Session-Resource-To-Setup-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + { ID id-CommonNetworkInstance CRITICALITY ignore EXTENSION CommonNetworkInstance PRESENCE optional + } | + { ID id-redundant-nG-UL-UP-TNL-Information CRITICALITY ignore EXTENSION UP-TNL-Information PRESENCE optional } | + { ID id-RedundantCommonNetworkInstance CRITICALITY ignore EXTENSION CommonNetworkInstance PRESENCE optional } | + { ID id-RedundantPDUSessionInformation CRITICALITY ignore EXTENSION RedundantPDUSessionInformation PRESENCE optional } | + { ID id-SpecialTriggeringPurpose CRITICALITY ignore EXTENSION SpecialTriggeringPurpose PRESENCE optional }, + ... + } + + PDU-Session-Resource-To-Setup-Mod-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-Resource-To-Setup-Mod-Item + + PDU-Session-Resource-To-Setup-Mod-Item ::= SEQUENCE { + pDU-Session-ID PDU-Session-ID, + pDU-Session-Type PDU-Session-Type, + sNSSAI SNSSAI, + securityIndication SecurityIndication, + pDU-Session-Resource-AMBR BitRate OPTIONAL, + nG-UL-UP-TNL-Information UP-TNL-Information, + pDU-Session-Data-Forwarding-Information-Request Data-Forwarding-Information-Request OPTIONAL, + pDU-Session-Inactivity-Timer Inactivity-Timer OPTIONAL, + dRB-To-Setup-Mod-List-NG-RAN DRB-To-Setup-Mod-List-NG-RAN, + } + +``` + +``` +iE-Extensions ProtocolExtensionContainer { { PDU-Session-Resource-To-Setup-Mod-Item-ExtIEs } } OPTIONAL, +... +} + +PDU-Session-Resource-To-Setup-Mod-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + {ID id-NetworkInstance CRITICALITY ignore EXTENSION NetworkInstance PRESENCE optional}| + {ID id-CommonNetworkInstance CRITICALITY ignore EXTENSION CommonNetworkInstance PRESENCE optional}| + {ID id-redundant-nG-UL-UP-TNL-Information CRITICALITY ignore EXTENSION UP-TNL-Information PRESENCE optional }| + {ID id-RedundantCommonNetworkInstance CRITICALITY ignore EXTENSION CommonNetworkInstance PRESENCE optional }| + {ID id-SpecialTriggeringPurpose CRITICALITY ignore EXTENSION SpecialTriggeringPurpose PRESENCE optional}, + ... +} + +PDU-Session-To-Notify-List ::= SEQUENCE (SIZE(1.. maxnoofPDUSessionResource)) OF PDU-Session-To-Notify-Item + +PDU-Session-To-Notify-Item ::= SEQUENCE { + pDU-Session-ID pDU-Session-ID, + qoS-Flow-List QoS-Flow-List, + iE-Extensions ProtocolExtensionContainer { { PDU-Session-To-Notify-Item-ExtIEs } } OPTIONAL, + ... +} + +PDU-Session-To-Notify-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +``` +PDU-Session-Type ::= ENUMERATED { + ipv4, + ipv6, + ipv4v6, + ethernet, + unstructured, + ... +} +``` + +``` +PDUSetbasedHandlingIndicator ::= ENUMERATED {supported, ...} +``` + +``` +PLMN-Identity ::= OCTET STRING (SIZE(3)) +``` + +``` +PortNumber ::= BIT STRING (SIZE(16)) +``` + +``` +PPI ::= INTEGER (0..7, ...) +``` + +``` +PriorityLevel ::= INTEGER { spare (0), highest (1), lowest (14), no-priority (15) } (0..15) +``` + +``` +Pre-emptionCapability ::= ENUMERATED { + shall-not-trigger-pre-emption, + may-trigger-pre-emption +} +``` + +``` +Pre-emptionVulnerability ::= ENUMERATED { + not-pre-emptable, + pre-emptable +} + +PrivacyIndicator ::= ENUMERATED { + immediate-MDT, + logged-MDT, + ... +} + +PDUSetQoSParameters ::= SEQUENCE { + pduSetDelayBudget ExtendedPacketDelayBudget OPTIONAL, + pduSetErrorRate PacketErrorRate OPTIONAL, + pduSetIntegratedHandlingInformation ENUMERATED {true, false, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDUSetQoSParameters-ExtIEs } } OPTIONAL +} + +PDUSetQoSParameters-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- Q +``` + +QCI ::= INTEGER (0..255) + +QoS-Characteristics ::= CHOICE { +    non-Dynamic-5QI           Non-Dynamic5QIDescriptor, +    dynamic-5QI               Dynamic5QIDescriptor, +    choice-extension        ProtocolIE-SingleContainer {{QoS-Characteristics-ExtIEs}} +} + +QoS-Characteristics-ExtIEs ELAP-PROTOCOL-IES ::= { +    ... +} + +QoS-Flow-Identifier ::= INTEGER (0..63) + +QoS-Flow-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF QoS-Flow-Item + +QoS-Flow-Item ::= SEQUENCE { +    qoS-Flow-Identifier           QoS-Flow-Identifier, +    iE-Extensions                 ProtocolExtensionContainer { { QoS-Flow-Item-ExtIEs } } OPTIONAL, +    ... +} + +QoS-Flow-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +    {ID id-QoSFlowMappingIndication   CRITICALITY ignore   EXTENSION QoS-Flow-Mapping-Indication   PRESENCE optional}| + +``` +{ID id-DataForwardingSourceIPAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}| + +{ID id-ECNMarkingorCongestionInformationReportingStatus CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingStatus +PRESENCE optional}, + +... + +} + +QoS-Flow-Failed-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF QoS-Flow-Failed-Item + +QoS-Flow-Failed-Item ::= SEQUENCE { + qoS-Flow-Identifier QoS-Flow-Identifier, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { QoS-Flow-Failed-Item-ExtIEs } } OPTIONAL, + ... +} + +QoS-Flow-Failed-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +QoS-Flow-Mapping-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF QoS-Flow-Mapping-Item + +QoS-Flow-Mapping-Item ::= SEQUENCE { + qoS-Flow-Identifier QoS-Flow-Identifier, + qoSFlowMappingIndication QoS-Flow-Mapping-Indication OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { QoS-Flow-Mapping-Item-ExtIEs } } OPTIONAL, +``` + +``` + ... +} + +QoS-Flow-Mapping-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +QoS-Flow-Mapping-Indication ::= ENUMERATED {ul, dl, ...} + +QoS-Flows-DRB-Remapping ::= ENUMERATED {update, source-configuration, ...} + +QoS-Parameters-Support-List ::= SEQUENCE { + eUTRAN-QoS-Support-List EUTRAN-QoS-Support-List OPTIONAL, + nG-RAN-QoS-Support-List NG-RAN-QoS-Support-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { QoS-Parameters-Support-List-ItemExtIEs} } OPTIONAL, + ... +} + +QoS-Parameters-Support-List-ItemExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} + +QoSPriorityLevel ::= INTEGER (0..127, ...) +``` + +QoS-Flow-QoS-Parameter-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF QoS-Flow-QoS-Parameter-Item + +QoS-Flow-QoS-Parameter-Item ::= SEQUENCE { + qosFlowIdentifier QoS-Flow-Identifier, + qosFlowLevelQoSParameters QoSFlowLevelQoSParameters, + qosFlowMappingIndication QoS-Flow-Mapping-Indication OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { QoS-Flow-QoS-Parameter-Item-ExtIEs } } OPTIONAL, + ... +} + +QoS-Flow-QoS-Parameter-Item-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-RedundantQoSFlowIndicator CRITICALITY ignore EXTENSION RedundantQoSFlowIndicator PRESENCE optional}| + {ID id-TSCTrafficCharacteristics CRITICALITY ignore EXTENSION TSCTrafficCharacteristics PRESENCE optional}| + {ID id-ECNMarkingorCongestionInformationReportingRequest CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingRequest + PRESENCE optional}| + ... +} + +QoSFlowLevelQoSParameters ::= SEQUENCE { + qosCharacteristics QoS-Characteristics, + nGRANallocationRetentionPriority NGRANAllocationAndRetentionPriority, + gBR-QoS-Flow-Information GBR-QoSFlowInformation OPTIONAL, + reflective-QoS-Attribute ENUMERATED {subject-to, ...} OPTIONAL, + additional-QoS-Information ENUMERATED {more-likely, ...} OPTIONAL, + +``` + + paging-Policy-Index INTEGER (1..8, ...) OPTIONAL, +-- The paging-Policy-Index IE is not used in this version of the specification. + reflective-QoS-Indicator ENUMERATED {enabled, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { QoSFlowLevelQoSParameters-ExtIEs } } OPTIONAL +} + +QoSFlowLevelQoSParameters-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + {ID id-QoSMonitoringRequest CRITICALITY ignore EXTENSION QoSMonitoringRequest PRESENCE optional}| + {ID id-MCG-OfferedGBRQoSFlowInfo CRITICALITY ignore EXTENSION GBR-QoSFlowInformation PRESENCE optional}| + {ID id-QoSMonitoringReportingFrequency CRITICALITY ignore EXTENSION QoSMonitoringReportingFrequency PRESENCE optional}| + {ID id-QoSMonitoringDisabled CRITICALITY ignore EXTENSION QoSMonitoringDisabled PRESENCE optional}| + {ID id-DataForwardingSourceIPAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}| + {ID id-PDUSetQoSParameters CRITICALITY ignore EXTENSION PDUSetQoSParameters PRESENCE optional}, + ... +} + +QoSMonitoringRequest ::= ENUMERATED {ul, dl, both} + +QoSMonitoringReportingFrequency ::= INTEGER (1..1800, ...) + +QoSMonitoringDisabled ::= ENUMERATED {true, ...} + +QoS-Flow-Removed-Item ::= SEQUENCE { + qoS-Flow-Identifier QoS-Flow-Identifier, +} + +``` + +``` + qoS-Flow-Released-In-Session ENUMERATED {released-in-session, not-released-in-session, ...} OPTIONAL, + qoS-Flow-Accumulated-Session-Time OCTET STRING (SIZE(5)) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { QoS-Flow-Removed-Item-ExtIEs } } OPTIONAL, + ... +} + +QoS-Flow-Removed-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +QoS-Flows-to-be-forwarded-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF QoS-Flows-to-be-forwarded-Item + +QoS-Flows-to-be-forwarded-Item ::= SEQUENCE { + qoS-Flow-Identifier QoS-Flow-Identifier, + iE-Extensions ProtocolExtensionContainer { { QoS-Flows-to-be-forwarded-Item-ExtIEs } } OPTIONAL, + ... +} + +QoS-Flows-to-be-forwarded-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +QoS-Mapping-Information ::= SEQUENCE { + dscp BIT STRING (SIZE(6)) OPTIONAL, + flow-label BIT STRING (SIZE(20)) OPTIONAL, +``` + +``` +... +} + +DataForwardingtoNG-RANQoSFlowInformationList := SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF DataForwardingtoNG-RANQoSFlowInformationList-Item + +DataForwardingtoNG-RANQoSFlowInformationList-Item := SEQUENCE { + qosFlow-Identifier QoS-Flow-Identifier, + iE-Extensions ProtocolExtensionContainer { { DataForwardingtoNG-RANQoSFlowInformationList-Item-ExtIEs} } OPTIONAL, + ... +} + +DataForwardingtoNG-RANQoSFlowInformationList-Item-ExtIEs ELAP-PROTOCOL-EXTENSION := { + ... +} + +-- R + +RANUEID := OCTET STRING (SIZE (8)) + +RAT-Type := ENUMERATED { + e-UTRA, + nR, + ... +} +``` + +RedundantQoSFlowIndicator ::= ENUMERATED {true,false} + +RedundantPDUSessionInformation ::= SEQUENCE { +    rSN                  RSN, +    iE-Extensions      ProtocolExtensionContainer { {RedundantPDUSessionInformation-ExtIEs} } OPTIONAL, +    ... +} + +RedundantPDUSessionInformation-ExtIEs EIAP-PROTOCOL-EXTENSION ::= { +    {ID id-PDUSession-PairID    CRITICALITY ignore    EXTENSION PDUSession-PairID PRESENCE optional}, +    ... +} + +RSN ::= ENUMERATED {v1, v2, ...} + +RetainabilityMeasurementsInfo ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Removed-Item + +RegistrationRequest ::= ENUMERATED { +    start, +    stop, +    ... +} + +ReportCharacteristics ::= BIT STRING (SIZE(36)) + +ReportingPeriodicity ::= ENUMERATED { +    ms500, ms1000, ms2000, ms5000, ms10000, ms20000, ms30000, ms40000, ms50000, ms60000, ms70000, ms80000, ms90000, ms100000, ms110000, ms120000, +    ... +} + +RequestedAction4AvailNGUTermination ::= ENUMERATED { +    apply-available-configuration, +    apply-requested-configuration, +    ... +    apply-available-configuration-if-same-as-requested +} + +RLC-Mode ::= ENUMERATED { +    rlc-tm, +    rlc-am, +    rlc-um-bidirectional, +    rlc-um-unidirectional-ul, +    rlc-um-unidirectional-dl, +    ... +} + +``` +ROHC-Parameters ::= CHOICE { + rOHC ROHC, + uPlinkOnlyROHC UplinkOnlyROHC, + choice-Extension ProtocolIE-SingleContainer { { ROHC-Parameters-ExtIEs } } +} + +ROHC-Parameters-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +ROHC ::= SEQUENCE { + maxCID INTEGER (0..16383, ...), + rOHC-Profiles INTEGER (0..511, ...), + continueROHC ENUMERATED {true, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ROHC-ExtIEs } } OPTIONAL +} + +ROHC-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- S +``` + +``` +SDT-data-size-threshold ::= INTEGER (1.. 192000, ...) + +SDT-data-size-threshold-Crossed ::= ENUMERATED {true, ...} + +SCGActivationStatus ::= ENUMERATED { scg-activated, scg-deactivated, ...} + +SecurityAlgorithm ::= SEQUENCE { + cipheringAlgorithm CipheringAlgorithm, + integrityProtectionAlgorithm IntegrityProtectionAlgorithm OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SecurityAlgorithm-ExtIEs } } OPTIONAL, + ... +} + +SecurityAlgorithm-ExtIEs EIAP-PROTOCOL-EXTENSION ::= { + ... +} + +SecurityIndication ::= SEQUENCE { + integrityProtectionIndication IntegrityProtectionIndication, + confidentialityProtectionIndication ConfidentialityProtectionIndication, + maximumIPDatarate MaximumIPDatarate OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {SecurityIndication-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +SecurityIndication-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +SecurityInformation ::= SEQUENCE { + securityAlgorithm SecurityAlgorithm, + uPSecuritykey UPSecuritykey, + iE-Extensions ProtocolExtensionContainer { { SecurityInformation-ExtIEs } } OPTIONAL, + ... +} + +SecurityInformation-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +SecurityResult ::= SEQUENCE { + integrityProtectionResult IntegrityProtectionResult, + confidentialityProtectionResult ConfidentialityProtectionResult, + iE-Extensions ProtocolExtensionContainer { {SecurityResult-ExtIEs} } OPTIONAL, + ... +} + +SecurityResult-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} +``` + +``` +Slice-Support-List ::= SEQUENCE (SIZE(1.. maxnoofSliceItems)) OF Slice-Support-Item +``` + +``` +Slice-Support-Item ::= SEQUENCE { +``` + +``` + sNSSAI SNSSAI, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { Slice-Support-Item-ExtIEs } } OPTIONAL +``` + +``` +} +``` + +``` +Slice-Support-Item-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SNSSAI ::= SEQUENCE { +``` + +``` + sST OCTET STRING (SIZE(1)), +``` + +``` + sD OCTET STRING (SIZE(3)) OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SNSSAI-ExtIEs } } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +SNSSAI-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SDAP-Configuration ::= SEQUENCE { +``` + +``` + defaultDRB DefaultDRB, + sDAP-Header-UL sDAP-Header-UL, + sDAP-Header-DL sDAP-Header-DL, + iE-Extensions ProtocolExtensionContainer { { sDAP-Configuration-ExtIEs } } OPTIONAL, + ... +} + +sDAP-Configuration-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +sDAP-Header-DL ::= ENUMERATED { + present, + absent, + ... +} + +sDAP-Header-UL ::= ENUMERATED { + present, + absent, + ... +} + +SDTContinueROHC ::= ENUMERATED {true, ...} +``` + +SDTIndicatorSetup ::= ENUMERATED {true, ...} + +SDTIndicatorMod ::= ENUMERATED {true, false, ...} + +SubscriberProfileIDforRFP ::= INTEGER (1..256, ...) + +SurvivalTime ::= INTEGER (0..1920000, ...) + +SpecialTriggeringPurpose ::= ENUMERATED { + indirect-data-forwarding, + ... +} + +FlUTunnelNotEstablished ::= ENUMERATED { + true, + ... +} + +-- T + +TimeToWait ::= ENUMERATED {v1s, v2s, v5s, v10s, v20s, v60s, ...} + +TNLAssociationUsage ::= ENUMERATED { + +``` +ue, +non-ue, +both, +... +} +``` + +``` +TNL-AvailableCapacityIndicator ::= SEQUENCE { + dL-TNL-OfferedCapacity INTEGER (0..16777216, ...), + dL-TNL-AvailableCapacity INTEGER (0..100, ...), + uL-TNL-OfferedCapacity INTEGER (0..16777216, ...), + uL-TNL-AvailableCapacity INTEGER (0..100, ...), + iE-Extensions ProtocolExtensionContainer { { TNL-AvailableCapacityIndicator-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +TNL-AvailableCapacityIndicator-ExtIEs E1AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TSCTrafficCharacteristics ::= SEQUENCE { + tSCTrafficCharacteristicsUL TSCTrafficInformation OPTIONAL, + tSCTrafficCharacteristicsDL TSCTrafficInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TSCTrafficCharacteristics-ExtIEs } } OPTIONAL +``` + +``` + } + + TSCTrafficCharacteristics-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... + } + + TSCTrafficInformation ::= SEQUENCE { + periodicity Periodicity, + burstArrivalTime BurstArrivalTime OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TSCTrafficInformation-ExtIEs } } OPTIONAL + } + + TSCTrafficInformation-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + {ID id-SurvivalTime CRITICALITY ignore EXTENSION SurvivalTime PRESENCE optional}| + {ID id-N6JitterInformation CRITICALITY ignore EXTENSION N6JitterInformation PRESENCE optional}, + ... + } + + Periodicity ::= INTEGER (1..640000, ...) + + BurstArrivalTime ::= OCTET STRING + + TraceActivation ::= SEQUENCE { +``` + +``` +traceID TraceID, +interfacesToTrace InterfacesToTrace, +traceDepth TraceDepth, +traceCollectionEntityIPAddress TransportLayerAddress, +iE-Extensions ProtocolExtensionContainer { {TraceActivation-ExtIEs} } OPTIONAL, +... +} + +TraceActivation-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + { ID id-MDTConfiguration CRITICALITY ignore EXTENSION MDT-Configuration PRESENCE optional } | + { ID id-TraceCollectionEntityURI CRITICALITY ignore EXTENSION URIaddress PRESENCE optional }, + ... +} + +TraceDepth ::= ENUMERATED { + minimum, + medium, + maximum, + minimumWithoutVendorSpecificExtension, + mediumWithoutVendorSpecificExtension, + maximumWithoutVendorSpecificExtension, + ... +} +``` + +TraceID ::= OCTET STRING (SIZE(8)) + +TransportLayerAddress ::= BIT STRING (SIZE(1..160, ...)) + +TransactionID ::= INTEGER (0..255, ...) + +T-Reordering ::= ENUMERATED {ms0, ms1, ms2, ms4, ms5, ms8, ms10, ms15, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms120, ms140, ms160, ms180, ms200, ms220, ms240, ms260, ms280, ms300, ms500, ms750, ms1000, ms1250, ms1500, ms1750, ms2000, ms2250, ms2500, ms2750, ms3000, ...} + +T-ReorderingTimer ::= SEQUENCE { + +    t-Reordering                T-Reordering, + +    iE-Extensions              ProtocolExtensionContainer { T-ReorderingTimer-ExtIEs } OPTIONAL, + +    ... + +} + +T-ReorderingTimer-ExtIEs EIAP-PROTOCOL-EXTENSION ::= { + +    ... + +} + +TypeOfError ::= ENUMERATED { + +    not-understood, + +    missing, + +    ... + +``` +} + +Transport-Layer-Address-Info ::= SEQUENCE { + transport-UP-Layer-Addresses-Info-To-Add-List Transport-UP-Layer-Addresses-Info-To-Add-List OPTIONAL, + transport-UP-Layer-Addresses-Info-To-Remove-List Transport-UP-Layer-Addresses-Info-To-Remove-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Transport-Layer-Address-Info-ExtIEs} } OPTIONAL, + ... +} + +Transport-Layer-Address-Info-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +Transport-UP-Layer-Addresses-Info-To-Add-List ::= SEQUENCE (SIZE(1.. maxnoofTLAs)) OF Transport-UP-Layer-Addresses-Info-To-Add-Item + +Transport-UP-Layer-Addresses-Info-To-Add-Item ::= SEQUENCE { + iP-SecTransportLayerAddress TransportLayerAddress, + gTPTransportLayerAddressesToAdd GTPTLAs OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Transport-UP-Layer-Addresses-Info-To-Add-ItemExtIEs } } OPTIONAL, + ... +} + +Transport-UP-Layer-Addresses-Info-To-Add-ItemExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Transport-UP-Layer-Addresses-Info-To-Remove-List ::= SEQUENCE (SIZE(1.. maxnoofTLAs)) OF Transport-UP-Layer-Addresses-Info-To-Remove-Item +``` + +``` +Transport-UP-Layer-Addresses-Info-To-Remove-Item ::= SEQUENCE { + iP-SecTransportLayerAddress TransportLayerAddress, + gTPTransportLayerAddressesToRemove GTPTLAs OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Transport-UP-Layer-Addresses-Info-To-Remove-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +Transport-UP-Layer-Addresses-Info-To-Remove-ItemExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} +-- U +``` + +``` +UDC-Parameters ::= SEQUENCE { + bufferSize BufferSize, + dictionary Dictionary OPTIONAL, + continueUDC ENUMERATED {true, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UDC-Parameters-ExtIEs } } OPTIONAL +} +``` + +``` +UDC-Parameters-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + { ID id-VersionID CRITICALITY ignore EXTENSION INTEGER (0..15) PRESENCE optional}, + ... +} +``` + +``` +} + +UE-Activity ::= ENUMERATED { + active, + not-active, + ... +} + +UE-associatedLogicalEl-ConnectionItem ::= SEQUENCE { + gNB-CU-CP-UE-ElAP-ID GNB-CU-CP-UE-ElAP-ID OPTIONAL, + gNB-CU-UP-UE-ElAP-ID GNB-CU-UP-UE-ElAP-ID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UE-associatedLogicalEl-ConnectionItemExtIEs} } OPTIONAL, + ... +} + +UE-associatedLogicalEl-ConnectionItemExtIEs ElAP-PROTOCOL-EXTENSION ::= { + ... +} + +UESliceMaximumBitRateList ::= SEQUENCE (SIZE(1.. maxnooSMBRValues)) OF UESliceMaximumBitRateItem +UESliceMaximumBitRateItem ::= SEQUENCE { + sNSSAI SNSSAI, + uESliceMaximumBitRateDL BitRate, + iE-Extensions ProtocolExtensionContainer { { UESliceMaximumBitRateItem-ExtIEs} } OPTIONAL, +} +``` + +``` + ... +} + +UESliceMaximumBitRateItem-ExtIEs EIAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-Configuration ::= ENUMERATED { + no-data, + shared, + only, + ... +} + +ULUPTNLAddressToUpdateItem ::= SEQUENCE { + oldTNLAddress TransportLayerAddress, + newTNLAddress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { ULUPTNLAddressToUpdateItemExtIEs } } OPTIONAL, + ... +} + +ULUPTNLAddressToUpdateItemExtIEs EIAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +ULDataSplitThreshold := ENUMERATED {b0, b100, b200, b400, b800, b1600, b3200, b6400, b12800, b25600, b51200, b102400, b204800, b409600, b819200, +b1228800, b1638400, b2457600, b3276800, b4096000, b4915200, b5734400, b6553600, infinity, ...} + +UP-Parameters := SEQUENCE (SIZE(1.. maxnoofUPParameters)) OF UP-Parameters-Item + +UP-Parameters-Item := SEQUENCE { + uP-TNL-Information UP-TNL-Information, + cell-Group-ID Cell-Group-ID, + iE-Extensions ProtocolExtensionContainer { { UP-Parameters-Item-ExtIEs } } OPTIONAL, + ... +} + +UP-Parameters-Item-ExtIEs EIAP-PROTOCOL-EXTENSION := { + {ID id-QoS-Mapping-Information CRITICALITY reject EXTENSION QoS-Mapping-Information PRESENCE optional}| + {ID id-IndirectPathIndication CRITICALITY ignore EXTENSION IndirectPathIndication PRESENCE optional}, + ... +} + +UPSecuritykey := SEQUENCE { + encryptionKey EncryptionKey, + integrityProtectionKey IntegrityProtectionKey OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UPSecuritykey-ExtIEs } } OPTIONAL, +``` + +``` + ... +} + +UPSecuritykey-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { + ... +} + +UP-TNL-Information ::= CHOICE { + gTP Tunnel GTP Tunnel, + choice-extension ProtocolIE-SingleContainer {{UP-TNL-Information-ExtIEs}} +} + +UP-TNL-Information-ExtIEs ELAP-PROTOCOL-IES ::= { + ... +} + +UplinkOnlyROHC ::= SEQUENCE { + maxCID INTEGER (0..16383, ...), + rOHC-Profiles INTEGER (0..511, ...), + continueROHC ENUMERATED {true, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UplinkOnlyROHC-ExtIEs } } OPTIONAL +} + +UplinkOnlyROHC-ExtIEs ELAP-PROTOCOL-EXTENSION ::= { +``` + +``` + + ... +} + +URIaddress ::= VisibleString + +UEInactivityInformation ::= INTEGER (1..7200, ...) + +-- V + +-- W + +-- X + +-- Y + +-- Z + +END + +-- ASN1STOP + +``` + +### 9.4.6 Common Definitions + +``` + +-- ASN1START +-- ***** +-- +-- Common definitions + +``` + +``` + +-- +-- ***** + +ELAP-CommonDataTypes { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + + ngran-access (22) modules (3) elap (5) version1 (1) elap-CommonDataTypes (3)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- Extension constants +-- +-- ***** + +maxPrivateIEs INTEGER ::= 65535 +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 + +-- ***** +-- + +``` + +``` +-- Common Data Types +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +Criticality ::= ENUMERATED { reject, ignore, notify } +``` + +``` +Presence ::= ENUMERATED { optional, conditional, mandatory } +``` + +``` +PrivateIE-ID ::= CHOICE { + local INTEGER (0.. maxPrivateIEs), + global OBJECT IDENTIFIER +} +``` + +``` +ProcedureCode ::= INTEGER (0..255) +``` + +``` +ProtocolExtensionID ::= INTEGER (0..maxProtocolExtensions) +``` + +``` +ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs) +``` + +``` +TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome } +``` + +``` +END +``` + +``` +-- ASN1STOP +``` + +## 9.4.7 Constant Definitions + +``` +-- ASN1START + +-- ***** + +-- + +-- Constant definitions + +-- + +-- ***** + +ElAP-Constants { + + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + + ngran-access (22) modules (3) elap (5) version1 (1) elap-Constants (4) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + + ProcedureCode, + + ProtocolIE-ID + +FROM ElAP-CommonDataTypes; +``` + +``` +-- ***** +-- +-- Elementary Procedures +-- +-- ***** + +id-reset ProcedureCode ::= 0 +id-errorIndication ProcedureCode ::= 1 +id-privateMessage ProcedureCode ::= 2 +id-gNB-CU-UP-EISetup ProcedureCode ::= 3 +id-gNB-CU-CP-EISetup ProcedureCode ::= 4 +id-gNB-CU-UP-ConfigurationUpdate ProcedureCode ::= 5 +id-gNB-CU-CP-ConfigurationUpdate ProcedureCode ::= 6 +id-eIRelease ProcedureCode ::= 7 +id-bearerContextSetup ProcedureCode ::= 8 +id-bearerContextModification ProcedureCode ::= 9 +id-bearerContextModificationRequired ProcedureCode ::= 10 +id-bearerContextRelease ProcedureCode ::= 11 +id-bearerContextReleaseRequest ProcedureCode ::= 12 +id-bearerContextInactivityNotification ProcedureCode ::= 13 +id-dLDataNotification ProcedureCode ::= 14 +id-dataUsageReport ProcedureCode ::= 15 +id-gNB-CU-UP-CounterCheck ProcedureCode ::= 16 +id-gNB-CU-UP-StatusIndication ProcedureCode ::= 17 +id-uLDataNotification ProcedureCode ::= 18 +``` + +| | | +|-------------------------------------------|----------------------| +| id-mRDC-DataUsageReport | ProcedureCode ::= 19 | +| id-TraceStart | ProcedureCode ::= 20 | +| id-DeactivateTrace | ProcedureCode ::= 21 | +| id-resourceStatusReportingInitiation | ProcedureCode ::= 22 | +| id-resourceStatusReporting | ProcedureCode ::= 23 | +| id-iAB-UPTNLAddressUpdate | ProcedureCode ::= 24 | +| id-CellTrafficTrace | ProcedureCode ::= 25 | +| id-earlyForwardingSNTransfer | ProcedureCode ::= 26 | +| id-gNB-CU-CPMeasurementResultsInformation | ProcedureCode ::= 27 | +| id-iABPSKNotification | ProcedureCode ::= 28 | +| id-BCBearerContextSetup | ProcedureCode ::= 29 | +| id-BCBearerContextModification | ProcedureCode ::= 30 | +| id-BCBearerContextModificationRequired | ProcedureCode ::= 31 | +| id-BCBearerContextRelease | ProcedureCode ::= 32 | +| id-BCBearerContextReleaseRequest | ProcedureCode ::= 33 | +| id-MCBearerContextSetup | ProcedureCode ::= 34 | +| id-MCBearerContextModification | ProcedureCode ::= 35 | +| id-MCBearerContextModificationRequired | ProcedureCode ::= 36 | +| id-MCBearerContextRelease | ProcedureCode ::= 37 | +| id-MCBearerContextReleaseRequest | ProcedureCode ::= 38 | +| id-MCBearerNotification | ProcedureCode ::= 39 | + +-- \*\*\*\*\* + +``` +-- +-- Lists +-- +-- ***** + +maxnoofErrors INTEGER ::= 256 +maxnoofSPLMNs INTEGER ::= 12 +maxnoofSliceItems INTEGER ::= 1024 +maxnoofIndividueElConnectionsToReset INTEGER ::= 65536 +maxnoofEUTRANQOSParameters INTEGER ::= 256 +maxnoofNGRANQOSParameters INTEGER ::= 256 +maxnoofDRBs INTEGER ::= 32 +maxnoofNRCGI INTEGER ::= 512 +maxnoofPDUSessionResource INTEGER ::= 256 +maxnoofQoSFlows INTEGER ::= 64 +maxnoofUPParameters INTEGER ::= 8 +maxnoofCellGroups INTEGER ::= 4 +maxnooftimeperiods INTEGER ::= 2 +maxnoofTNLAssociations INTEGER ::= 32 +maxnoofTLAs INTEGER ::= 16 +maxnoofGTPTLAs INTEGER ::= 16 +maxnoofTNLAddresses INTEGER ::= 8 +maxnoofMDTFLMNs INTEGER ::= 16 +maxnoofQoSParaSets INTEGER ::= 8 +``` + +``` + +maxnoofExtSliceItems INTEGER ::= 65535 +maxnoofDataForwardingTunneltoE-UTRAN INTEGER ::= 256 +maxnoofExtNRCGI INTEGER ::= 16384 +maxnoofPSKs INTEGER ::= 256 +maxnoofECGI INTEGER ::= 512 +maxnoofSMBRValues INTEGER ::= 8 +maxnoofMBSAreaSessionIDs INTEGER ::= 256 +maxnoofSharedNG-UTerminations INTEGER ::= 8 +maxnoofMRBs INTEGER ::= 32 +maxnoofMBSSessionIDs INTEGER ::= 512 +maxnoofCellsforMBS INTEGER ::= 512 +maxnoofTAIforMBS INTEGER ::= 512 +maxnoofMBSServiceAreaInformation INTEGER ::= 256 + +``` + +``` + +-- ***** +-- +-- IEs +-- +-- ***** + +``` + +``` + +id-Cause ProtocolIE-ID ::= 0 +id-CriticalityDiagnostics ProtocolIE-ID ::= 1 +id-gNB-CU-CP-UE-E1AP-ID ProtocolIE-ID ::= 2 + +``` + +| | | +|------------------------------------------------|----------------------| +| id-gNB-CU-UP-UE-E1AP-ID | ProtocolIE-ID ::= 3 | +| id-ResetType | ProtocolIE-ID ::= 4 | +| id-UE-associatedLogicalE1-ConnectionItem | ProtocolIE-ID ::= 5 | +| id-UE-associatedLogicalE1-ConnectionListResAck | ProtocolIE-ID ::= 6 | +| id-gNB-CU-UP-ID | ProtocolIE-ID ::= 7 | +| id-gNB-CU-UP-Name | ProtocolIE-ID ::= 8 | +| id-gNB-CU-CP-Name | ProtocolIE-ID ::= 9 | +| id-CNSupport | ProtocolIE-ID ::= 10 | +| id-SupportedPLMNs | ProtocolIE-ID ::= 11 | +| id-TimeToWait | ProtocolIE-ID ::= 12 | +| id-SecurityInformation | ProtocolIE-ID ::= 13 | +| id-UEDLAGgregateMaximumBitRate | ProtocolIE-ID ::= 14 | +| id-System-BearerContextSetupRequest | ProtocolIE-ID ::= 15 | +| id-System-BearerContextSetupResponse | ProtocolIE-ID ::= 16 | +| id-BearerContextStatusChange | ProtocolIE-ID ::= 17 | +| id-System-BearerContextModificationRequest | ProtocolIE-ID ::= 18 | +| id-System-BearerContextModificationResponse | ProtocolIE-ID ::= 19 | +| id-System-BearerContextModificationConfirm | ProtocolIE-ID ::= 20 | +| id-System-BearerContextModificationRequired | ProtocolIE-ID ::= 21 | +| id-DRB-Status-List | ProtocolIE-ID ::= 22 | +| id-ActivityNotificationLevel | ProtocolIE-ID ::= 23 | +| id-ActivityInformation | ProtocolIE-ID ::= 24 | +| id-Data-Usage-Report-List | ProtocolIE-ID ::= 25 | +| id-New-UL-TNL-Information-Required | ProtocolIE-ID ::= 26 | +| id-GNB-CU-CP-TNLA-To-Add-List | ProtocolIE-ID ::= 27 | + +| | | +|-------------------------------------------------|----------------------| +| id-GNB-CU-CP-TNLA-To-Remove-List | ProtocolIE-ID ::= 28 | +| id-GNB-CU-CP-TNLA-To-Update-List | ProtocolIE-ID ::= 29 | +| id-GNB-CU-CP-TNLA-Setup-List | ProtocolIE-ID ::= 30 | +| id-GNB-CU-CP-TNLA-Failed-To-Setup-List | ProtocolIE-ID ::= 31 | +| id-DRB-To-Setup-List-EUTRAN | ProtocolIE-ID ::= 32 | +| id-DRB-To-Modify-List-EUTRAN | ProtocolIE-ID ::= 33 | +| id-DRB-To-Remove-List-EUTRAN | ProtocolIE-ID ::= 34 | +| id-DRB-Required-To-Modify-List-EUTRAN | ProtocolIE-ID ::= 35 | +| id-DRB-Required-To-Remove-List-EUTRAN | ProtocolIE-ID ::= 36 | +| id-DRB-Setup-List-EUTRAN | ProtocolIE-ID ::= 37 | +| id-DRB-Failed-List-EUTRAN | ProtocolIE-ID ::= 38 | +| id-DRB-Modified-List-EUTRAN | ProtocolIE-ID ::= 39 | +| id-DRB-Failed-To-Modify-List-EUTRAN | ProtocolIE-ID ::= 40 | +| id-DRB-Confirm-Modified-List-EUTRAN | ProtocolIE-ID ::= 41 | +| id-PDU-Session-Resource-To-Setup-List | ProtocolIE-ID ::= 42 | +| id-PDU-Session-Resource-To-Modify-List | ProtocolIE-ID ::= 43 | +| id-PDU-Session-Resource-To-Remove-List | ProtocolIE-ID ::= 44 | +| id-PDU-Session-Resource-Required-To-Modify-List | ProtocolIE-ID ::= 45 | +| id-PDU-Session-Resource-Setup-List | ProtocolIE-ID ::= 46 | +| id-PDU-Session-Resource-Failed-List | ProtocolIE-ID ::= 47 | +| id-PDU-Session-Resource-Modified-List | ProtocolIE-ID ::= 48 | +| id-PDU-Session-Resource-Failed-To-Modify-List | ProtocolIE-ID ::= 49 | +| id-PDU-Session-Resource-Confirm-Modified-List | ProtocolIE-ID ::= 50 | +| id-DRB-To-Setup-Mod-List-EUTRAN | ProtocolIE-ID ::= 51 | +| id-DRB-Setup-Mod-List-EUTRAN | ProtocolIE-ID ::= 52 | + +| | | +|-----------------------------------------------|----------------------| +| id-DRB-Failed-Mod-List-EUTRAN | ProtocolIE-ID ::= 53 | +| id-PDU-Session-Resource-Setup-Mod-List | ProtocolIE-ID ::= 54 | +| id-PDU-Session-Resource-Failed-Mod-List | ProtocolIE-ID ::= 55 | +| id-PDU-Session-Resource-To-Setup-Mod-List | ProtocolIE-ID ::= 56 | +| id-TransactionID | ProtocolIE-ID ::= 57 | +| id-Serving-PLMN | ProtocolIE-ID ::= 58 | +| id-UE-Inactivity-Timer | ProtocolIE-ID ::= 59 | +| id-System-GNB-CU-UP-CounterCheckRequest | ProtocolIE-ID ::= 60 | +| id-DRBs-Subject-To-Counter-Check-List-EUTRAN | ProtocolIE-ID ::= 61 | +| id-DRBs-Subject-To-Counter-Check-List-NG-RAN | ProtocolIE-ID ::= 62 | +| id-PPI | ProtocolIE-ID ::= 63 | +| id-gNB-CU-UP-Capacity | ProtocolIE-ID ::= 64 | +| id-GNB-CU-UP-OverloadInformation | ProtocolIE-ID ::= 65 | +| id-UEDLMaximumIntegrityProtectedDataRate | ProtocolIE-ID ::= 66 | +| id-PDU-Session-To-Notify-List | ProtocolIE-ID ::= 67 | +| id-PDU-Session-Resource-Data-Usage-List | ProtocolIE-ID ::= 68 | +| id-SNSSAI | ProtocolIE-ID ::= 69 | +| id-DataDiscardRequired | ProtocolIE-ID ::= 70 | +| id-OldQoSFlowMap-ULendmarkerexpected | ProtocolIE-ID ::= 71 | +| id-DRB-QoS | ProtocolIE-ID ::= 72 | +| id-GNB-CU-UP-TNLA-To-Remove-List | ProtocolIE-ID ::= 73 | +| id-endpoint-IP-Address-and-Port | ProtocolIE-ID ::= 74 | +| id-TNLAssociationTransportLayerAddressgNBCUUP | ProtocolIE-ID ::= 75 | +| id-RANUEID | ProtocolIE-ID ::= 76 | +| id-GNB-DU-ID | ProtocolIE-ID ::= 77 | + +| | | +|---------------------------------------|-----------------------| +| id-CommonNetworkInstance | ProtocolIE-ID ::= 78 | +| id-NetworkInstance | ProtocolIE-ID ::= 79 | +| id-QoSFlowMappingIndication | ProtocolIE-ID ::= 80 | +| id-TraceActivation | ProtocolIE-ID ::= 81 | +| id-TraceID | ProtocolIE-ID ::= 82 | +| id-SubscriberProfileIDforRFP | ProtocolIE-ID ::= 83 | +| id-AdditionalRRMPriorityIndex | ProtocolIE-ID ::= 84 | +| id-RetainabilityMeasurementsInfo | ProtocolIE-ID ::= 85 | +| id-Transport-Layer-Address-Info | ProtocolIE-ID ::= 86 | +| id-QoSMonitoringRequest | ProtocolIE-ID ::= 87 | +| id-PDCP-StatusReportIndication | ProtocolIE-ID ::= 88 | +| id-gNB-CU-CP-Measurement-ID | ProtocolIE-ID ::= 89 | +| id-gNB-CU-UP-Measurement-ID | ProtocolIE-ID ::= 90 | +| id-RegistrationRequest | ProtocolIE-ID ::= 91 | +| id-ReportCharacteristics | ProtocolIE-ID ::= 92 | +| id-ReportingPeriodicity | ProtocolIE-ID ::= 93 | +| id-TNL-AvailableCapacityIndicator | ProtocolIE-ID ::= 94 | +| id-HW-CapacityIndicator | ProtocolIE-ID ::= 95 | +| id-RedundantCommonNetworkInstance | ProtocolIE-ID ::= 96 | +| id-redundant-nG-UL-UP-TNL-Information | ProtocolIE-ID ::= 97 | +| id-redundant-nG-DL-UP-TNL-Information | ProtocolIE-ID ::= 98 | +| id-RedundantQoSFlowIndicator | ProtocolIE-ID ::= 99 | +| id-TSCTrafficCharacteristics | ProtocolIE-ID ::= 100 | +| id-CNPacketDelayBudgetDownlink | ProtocolIE-ID ::= 101 | +| id-CNPacketDelayBudgetUplink | ProtocolIE-ID ::= 102 | + +| | | +|------------------------------------------|-----------------------| +| id-ExtendedPacketDelayBudget | ProtocolIE-ID ::= 103 | +| id-AdditionalPDCPduplicationInformation | ProtocolIE-ID ::= 104 | +| id-RedundantPDUSessionInformation | ProtocolIE-ID ::= 105 | +| id-RedundantPDUSessionInformation-used | ProtocolIE-ID ::= 106 | +| id-QoS-Mapping-Information | ProtocolIE-ID ::= 107 | +| id-DLUPTNLAddressToUpdateList | ProtocolIE-ID ::= 108 | +| id-ULUPTNLAddressToUpdateList | ProtocolIE-ID ::= 109 | +| id-NPNSupportInfo | ProtocolIE-ID ::= 110 | +| id-NPNContextInfo | ProtocolIE-ID ::= 111 | +| id-MDTConfiguration | ProtocolIE-ID ::= 112 | +| id-ManagementBasedMDTPLMNList | ProtocolIE-ID ::= 113 | +| id-TraceCollectionEntityIPAddress | ProtocolIE-ID ::= 114 | +| id-PrivacyIndicator | ProtocolIE-ID ::= 115 | +| id-TraceCollectionEntityURI | ProtocolIE-ID ::= 116 | +| id-URIaddress | ProtocolIE-ID ::= 117 | +| id-EHC-Parameters | ProtocolIE-ID ::= 118 | +| id-DRBs-Subject-To-Early-Forwarding-List | ProtocolIE-ID ::= 119 | +| id-DAPSRequestInfo | ProtocolIE-ID ::= 120 | +| id-CHOInitiation | ProtocolIE-ID ::= 121 | +| id-EarlyForwardingCOUNTReq | ProtocolIE-ID ::= 122 | +| id-EarlyForwardingCOUNTInfo | ProtocolIE-ID ::= 123 | +| id-AlternativeQoSParaSetList | ProtocolIE-ID ::= 124 | +| id-ExtendedSliceSupportList | ProtocolIE-ID ::= 125 | +| id-MCG-OfferedGBRQoSFlowInfo | ProtocolIE-ID ::= 126 | +| id-Number-of-tunnels | ProtocolIE-ID ::= 127 | + +| | | +|-------------------------------------------------|-----------------------| +| id-DRB-Measurement-Results-Information-List | ProtocolIE-ID ::= 128 | +| id-Extended-GNB-CU-CP-Name | ProtocolIE-ID ::= 129 | +| id-Extended-GNB-CU-UP-Name | ProtocolIE-ID ::= 130 | +| id-DataForwardingtoE-UTRANInformationList | ProtocolIE-ID ::= 131 | +| id-QoSMonitoringReportingFrequency | ProtocolIE-ID ::= 132 | +| id-QoSMonitoringDisabled | ProtocolIE-ID ::= 133 | +| id-AdditionalHandoverInfo | ProtocolIE-ID ::= 134 | +| id-Extended-NR-CGI-Support-List | ProtocolIE-ID ::= 135 | +| id-DataForwardingtoNG-RANQoSFlowInformationList | ProtocolIE-ID ::= 136 | +| id-MaxCIDEHC DL | ProtocolIE-ID ::= 137 | +| id-ignoreMappingRuleIndication | ProtocolIE-ID ::= 138 | +| id-DirectForwardingPathAvailability | ProtocolIE-ID ::= 139 | +| id-EarlyDataForwardingIndicator | ProtocolIE-ID ::= 140 | +| id-QoSFlowsDRBRemapping | ProtocolIE-ID ::= 141 | +| id-DataForwardingSourceIPAddress | ProtocolIE-ID ::= 142 | +| id-SecurityIndicationModify | ProtocolIE-ID ::= 143 | +| id-IAB-Donor-CU-UPPSKInfo | ProtocolIE-ID ::= 144 | +| id-ECGI-Support-List | ProtocolIE-ID ::= 145 | +| id-MDTPollutedMeasurementIndicator | ProtocolIE-ID ::= 146 | +| id-M4ReportAmount | ProtocolIE-ID ::= 147 | +| id-M6ReportAmount | ProtocolIE-ID ::= 148 | +| id-M7ReportAmount | ProtocolIE-ID ::= 149 | +| id-UESliceMaximumBitRateList | ProtocolIE-ID ::= 150 | +| id-PDUSession-PairID | ProtocolIE-ID ::= 151 | + +| | | +|-------------------------------------|-----------------------| +| id-SurvivalTime | ProtocolIE-ID ::= 152 | +| id-UDC-Parameters | ProtocolIE-ID ::= 153 | +| id-SCGActivationStatus | ProtocolIE-ID ::= 154 | +| id-GNB-CU-CP-MBS-ElAP-ID | ProtocolIE-ID ::= 155 | +| id-GNB-CU-UP-MBS-ElAP-ID | ProtocolIE-ID ::= 156 | +| id-GlobalMBSSessionID | ProtocolIE-ID ::= 157 | +| id-BCBearerContextToSetup | ProtocolIE-ID ::= 158 | +| id-BCBearerContextToSetupResponse | ProtocolIE-ID ::= 159 | +| id-BCBearerContextToModify | ProtocolIE-ID ::= 160 | +| id-BCBearerContextToModifyResponse | ProtocolIE-ID ::= 161 | +| id-BCBearerContextToModifyRequired | ProtocolIE-ID ::= 162 | +| id-BCBearerContextToModifyConfirm | ProtocolIE-ID ::= 163 | +| id-MCBearerContextToSetup | ProtocolIE-ID ::= 164 | +| id-MCBearerContextToSetupResponse | ProtocolIE-ID ::= 165 | +| id-MCBearerContextToModify | ProtocolIE-ID ::= 166 | +| id-MCBearerContextToModifyResponse | ProtocolIE-ID ::= 167 | +| id-MCBearerContextToModifyRequired | ProtocolIE-ID ::= 168 | +| id-MCBearerContextToModifyConfirm | ProtocolIE-ID ::= 169 | +| id-MBSMulticastFlUContextDescriptor | ProtocolIE-ID ::= 170 | +| id-gNB-CU-UP-MBS-Support-Info | ProtocolIE-ID ::= 171 | +| id-SecurityIndication | ProtocolIE-ID ::= 172 | +| id-SecurityResult | ProtocolIE-ID ::= 173 | +| id-SDTContinueROHC | ProtocolIE-ID ::= 174 | +| id-SDTIndicatorSetup | ProtocolIE-ID ::= 175 | +| id-SDTIndicatorMod | ProtocolIE-ID ::= 176 | + +| | | +|------------------------------------------------------|-----------------------| +| id-DiscardTimerExtended | ProtocolIE-ID ::= 177 | +| id-ManagementBasedMDTPLMNModificationList | ProtocolIE-ID ::= 178 | +| id-MCForwardingResourceRequest | ProtocolIE-ID ::= 179 | +| id-MCForwardingResourceIndication | ProtocolIE-ID ::= 180 | +| id-MCForwardingResourceResponse | ProtocolIE-ID ::= 181 | +| id-MCForwardingResourceRelease | ProtocolIE-ID ::= 182 | +| id-MCForwardingResourceReleaseIndication | ProtocolIE-ID ::= 183 | +| id-PDCP-COUNT-Reset | ProtocolIE-ID ::= 184 | +| id-MBSSessionAssociatedInfoNonSupportToSupport | ProtocolIE-ID ::= 185 | +| id-VersionID | ProtocolIE-ID ::= 186 | +| id-InactivityInformationRequest | ProtocolIE-ID ::= 187 | +| id-UEInactivityInformation | ProtocolIE-ID ::= 188 | +| id-MBSAreaSessionID | ProtocolIE-ID ::= 189 | +| id-Secondary-PDU-Session-Data-Forwarding-Information | ProtocolIE-ID ::= 190 | +| id-MBSSessionResourceNotification | ProtocolIE-ID ::= 191 | +| id-MCBearerContextInactivityTimer | ProtocolIE-ID ::= 192 | +| id-MCBearerContextStatusChange | ProtocolIE-ID ::= 193 | +| id-MT-SDT-Information | ProtocolIE-ID ::= 194 | +| id-MT-SDT-Information-Request | ProtocolIE-ID ::= 195 | +| id-SDT-data-size-threshold | ProtocolIE-ID ::= 196 | +| id-SDT-data-size-threshold-Crossed | ProtocolIE-ID ::= 197 | +| id-SpecialTriggeringPurpose | ProtocolIE-ID ::= 198 | +| id-AssociatedSessionID | ProtocolIE-ID ::= 199 | +| id-MBS-ServiceArea | ProtocolIE-ID ::= 200 | + +``` + +id-PDUSetQoSParameters ProtocolIE-ID ::= 201 +id-N6JitterInformation ProtocolIE-ID ::= 202 +id-ECNMarkingorCongestionInformationReportingRequest + ProtocolIE-ID ::= 203 +id-ECNMarkingorCongestionInformationReportingStatus + ProtocolIE-ID ::= 204 +id-PDUSetbasedHandlingIndicator ProtocolIE-ID ::= 205 +id-IndirectPathIndication ProtocolIE-ID ::= 206 +id-F1UtunnelNotEstablished ProtocolIE-ID ::= 207 + +``` + +END + +-- ASN1STOP + +### 9.4.8 Container Definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- Container definitions + +-- + +-- \*\*\*\*\* + +ElAP-Containers { + +``` +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +ngran-access (22) modules (3) elap (5) version1 (1) elap-Containers (5) } +``` + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +``` +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** +``` + +IMPORTS + +``` + maxPrivateIEs, + maxProtocolExtensions, + maxProtocolIEs, + Criticality, + Presence, + PrivateIE-ID, + ProtocolIE-ID +``` + +FROM E1AP-CommonDataTypes; + +``` + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +``` + +``` + +ELAP-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 Extensions +-- +-- ***** + +``` + +``` + +E1AP-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality, + &Extension, + &presence Presence +} + +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Private IEs +-- +-- ***** + +``` + +``` + +E1AP-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 { E1AP-PROTOCOL-IES : IEsSetParam} ::= + +    SEQUENCE (SIZE (0..maxProtocolIEs)) OF + +    ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-SingleContainer { E1AP-PROTOCOL-IES : IEsSetParam} ::= + +    ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field { E1AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + +    id                E1AP-PROTOCOL-IES.&id                {{IEsSetParam}}, +    criticality      E1AP-PROTOCOL-IES.&criticality        {{IEsSetParam}{@id}}, +    value            E1AP-PROTOCOL-IES.&Value              {{IEsSetParam}{@id}} + +} + +``` +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +ProtocolIE-ContainerList { INTEGER : lowerBound, INTEGER : upperBound, E1AP-PROTOCOL-IES : IESetParam } ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container { IESetParam } + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +ProtocolExtensionContainer { E1AP-PROTOCOL-EXTENSION : ExtensionSetParam } ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField { ExtensionSetParam } + +ProtocolExtensionField { E1AP-PROTOCOL-EXTENSION : ExtensionSetParam } ::= SEQUENCE { + id E1AP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), + criticality E1AP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), + extensionValue E1AP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) +} +``` + +``` +} + +-- ***** +-- +-- Container for Private IEs +-- +-- ***** + +PrivateIE-Container { ELAP-PRIVATE-IES : IEsSetParam } ::= + SEQUENCE (SIZE (1..maxPrivateIEs)) OF + PrivateIE-Field {{IEsSetParam}} + +PrivateIE-Field { ELAP-PRIVATE-IES : IEsSetParam } ::= SEQUENCE { + id ELAP-PRIVATE-IES.&id {{IEsSetParam}}, + criticality ELAP-PRIVATE-IES.&criticality {{IEsSetParam}{@id}}, + value ELAP-PRIVATE-IES.&Value {{IEsSetParam}{@id}} +} + +END + +-- ASN1STOP +``` + +## 9.5 Message Transfer Syntax + +EIAP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax, as specified in ITU-T Recommendation X.691 [7]. + +## 9.6 Timers + +--- + +## 10 Handling of unknown, unforeseen and erroneous protocol data + +Section 10 of TS 38.413 [6] is applicable for the purposes of the present document, with the following additions for non-UE-associated procedures: + +- In case of Abstract Syntax Error, when reporting the *Criticality Diagnostics* IE for not comprehended IE/IEgroups or missing IE/IE groups, the *Transaction ID* IE shall also be included; +- In case of Logical Error, when reporting the *Criticality Diagnostics* IE, the *Transaction ID* IE shall also be included; +- In case of Logical Error in a response message of a Class 1 procedure, or failure to comprehend *Transaction ID* IE from a received message, the procedure shall be considered as unsuccessfully terminated or not terminated (e.g., transaction ID unknown in response message), and local error handling shall be initiated. + +## Annex A (informative): Change History + +| Change history | | | | | | | | +|----------------|-----------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-01 | R3#114b-e | R3-221121 | - | - | - | Text transferred from TS 38.463 v16.8.0 with no changes.
Capture LTE_NR_arch_evo_enh-Core endorsed BL CRs and agreed TPs | 0.0.1 | +| 2022-02 | R3#115-e | R3-221645 | - | - | - | Submitted to RAN3#115-e | 0.1.0 | +| 2022-02 | R3#115-e | R3-222578 | - | - | - | Change the date of specification release | 0.1.1 | +| 2022-03 | RAN#95-e | RP-220798 | - | - | - | Version submitted for approval in RAN#95-e | 1.0.0 | +| 2022-03 | RAN#95-e | RP-220851 | - | - | - | Agreed Rel-16/17 CRs from other WIs are merged.
Including REL-16 38.463 changes of: R3-221223 of RP-220276, R3-221253 of RP-220278, R3-220836 of RP-220277, R3-221707 of RP-220282, R3-222108 of RP-220279, R3-222844 of RP-220279.
and REL-17 38.463 changes of: R3-221516 of RP-220218, R3-221550 of RP-220221, R3-221598 of RP-220232, R3-221617 of RP-220294, R3-222541 of RP-220223, R3-222613 of RP-220234, R3-222906 of RP-220218, R3-222930 of RP-220224, RP-220927, R3-222986 of RP-220233. | 1.1.0 | +| 2022-03 | RAN#95-e | | | | | Promotion to Release 17 without technical change | 17.0.0 | +| 2022-06 | RAN#96 | RP-221138 | 0001 | 1 | F | Correction of UDC in CP-UP Split architecture | 17.1.0 | +| 2022-06 | RAN#96 | RP-221132 | 0002 | 2 | F | Extended PDCP Discard Timer over E1 interface | 17.1.0 | +| 2022-06 | RAN#96 | RP-221154 | 0004 | 1 | A | Correction on EHC parameters | 17.1.0 | +| 2022-06 | RAN#96 | RP-221140 | 0005 | 1 | F | Correction on enhanced eNB architecture evolution | 17.1.0 | +| 2022-06 | RAN#96 | RP-221134 | 0007 | 1 | F | Correction on configuration of initial value of HFN and reference SN | 17.1.0 | +| 2022-06 | RAN#96 | RP-221150 | 0008 | 1 | A | Dynamic ACL over E1 CR 37.483 | 17.1.0 | +| 2022-06 | RAN#96 | RP-221134 | 0009 | 1 | F | MBS E1AP corrections | 17.1.0 | +| 2022-06 | RAN#96 | RP-221149 | 0010 | 2 | A | Correction on IAB PSK generation | 17.1.0 | +| 2022-06 | RAN#96 | RP-221134 | 0013 | 3 | F | Correction of MBS shared NG-U termination | 17.1.0 | +| 2022-06 | RAN#96 | RP-221145 | 0014 | 1 | D | E1AP Rapporteur Corrections | 17.1.0 | +| 2022-06 | RAN#96 | RP-221134 | 0015 | 1 | F | Correction on NR MBS in E1AP | 17.1.0 | +| 2022-06 | RAN#96 | RP-221141 | 0016 | 1 | F | Correction on update management based MDT user consent | 17.1.0 | +| 2022-06 | RAN#96 | RP-221134 | 0019 | - | F | NR MBS E1AP asn.1 correction | 17.1.0 | +| 2022-06 | RAN#96 | RP-221135 | 0020 | 1 | F | Correction for E1AP on SCG (de)activation | 17.1.0 | +| 2022-09 | RAN#97-e | RP-222201 | 0027 | 1 | A | Correction on Missing Criticality Diagnostics over E1AP | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222188 | 0030 | 1 | F | Correction of shared CU UP codepoints | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222188 | 0031 | 1 | F | Further Corrections for NR MBS | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222188 | 0032 | - | F | E1AP ASN.1 correction on MCBearerContextToModify | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222188 | 0034 | 1 | F | Introduction of MBS specific cause values | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222188 | 0035 | 1 | F | Correction on Maximum number of MRBs | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222188 | 0037 | 2 | F | Correction for the MBS multicast data forwarding | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222188 | 0038 | 1 | F | Corrections for the establishment of F1-U ptp retransmission tunnels | 17.2.0 | +| 2022-12 | RAN#98 | RP-222891 | 0026 | 4 | A | PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | 17.3.0 | +| 2022-12 | RAN#98 | RP-222882 | 0042 | 3 | F | Clarification on initialRX-DELIV over E1AP | 17.3.0 | +| 2022-12 | RAN#98 | RP-222882 | 0043 | 2 | F | Correction on non-MBS-supporting to MBS-supporting handover on TS 37.483 | 17.3.0 | +| 2022-12 | RAN#98 | RP-222882 | 0046 | 1 | F | MC Bearer Context Setup without MBS QoS flow information available | 17.3.0 | +| 2023-03 | RAN#99 | RP-230583 | 0049 | - | F | Correction on providing MBS Session Associated Information | 17.4.0 | +| 2023-03 | RAN#99 | RP-230595 | 0050 | - | A | Mandatory extension container in E1AP Resource Status Update | 17.4.0 | +| 2023-03 | RAN#99 | RP-230594 | 0051 | 1 | F | E1AP corrections of references to RRC | 17.4.0 | +| 2023-06 | RAN#100 | RP-231081 | 0055 | 1 | A | Alignment of the tabular and ASN.1 definitions for the Resource Status Update | 17.5.0 | +| 2023-06 | RAN#100 | RP-231075 | 0056 | 1 | A | Corrections on TNL association addition, update and removal (E1) | 17.5.0 | +| 2023-06 | RAN#100 | RP-231073 | 0057 | 1 | F | Correction of Burst Arrival Time semantics description | 17.5.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|---------------------------------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-06 | RAN#100 | RP-231074 | 0058 | 1 | F | Correction on NG-U tunnel aspect for MBS session | 17.5.0 | +| 2023-06 | RAN#100 | RP-231075 | 0059 | 2 | F | Correction of Priority Level | 17.5.0 | +| 2023-06 | RAN#100 | RP-231068 | 0060 | 2 | F | Correction of RAT type in Data Usage Report List for Rel-17 | 17.5.0 | +| 2023-06 | RAN#100 | RP-231081 | 0061 | 2 | A | Correction on RESOURCE STATUS FAILURE message over E1 in Rel-17 | 17.5.0 | +| 2023-06 | RAN#100 | RP-231084 | 0062 | 2 | F | Correction of Extended Packet Delay Budget | 17.5.0 | +| 2023-06 | RAN#100 | RP-231070 | 0063 | 2 | A | Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters | 17.5.0 | +| 2023-06 | RAN#100 | RP-231082 | 0064 | 4 | F | Correction to UDC Parameters in E1AP | 17.5.0 | +| 2023-06 | RAN#100 | RP-231074 | 0065 | 0 | F | Correction of MRB Setup Configuration over E1 | 17.5.0 | +| 2023-09 | RAN#101 | RP-231902 | 0067 | 0 | F | UDC Parameters over E1 | 17.6.0 | +| 2023-09 | RAN#101 | RP-231895 | 0068 | 2 | A | Inactive Time Signaling over E1 for Mobility | 17.6.0 | +| 2023-09 | RAN#101 | RP-231897 | 0069 | 1 | F | Correction of Location Dependent Service | 17.6.0 | +| 2023-09 | RAN#101 | RP-231895 | 0072 | 2 | A | Correction of data forwarding for split PDU session | 17.6.0 | +| 2023-09 | RAN#101 | RP-231897 | 0073 | 0 | F | Correction on MBS Session Forwarding Address | 17.6.0 | +| 2023-12 | RAN#102 | RP-233849 | 0079 | 3 | F | Correction on Temp no data and DL data arrival for Activate Multicast Session | 17.7.0 | +| 2023-12 | RAN#102 | RP-233847 | 0089 | 1 | A | Correction on Resource Status Request | 17.7.0 | +| 2023-12 | RAN#102 | RP-233849 | 0094 | 1 | F | ASN.1 and tabular alignment for Multicast related message | 17.7.0 | +| 2023-12 | RAN#102 | RP-233852 | 0096 | 1 | F | Correction on Bearer Context Status Change | 17.7.0 | +| 2023-12 | RAN#102 | RP-233819 | 0054 | 9 | B | Introduction of MT-SDT | 18.0.0 | +| 2023-12 | RAN#102 | RP-233844 | 0086 | 2 | F | Correction of Transport Addresses | 18.0.0 | +| 2023-12 | RAN#102 | RP-233844 | 0095 | 3 | B | Avoiding unnecessary setup of DRB(s) in indirect data forwarding [Indirect Data forwarding] | 18.0.0 | +| 2023-12 | RAN#102 | RP-233829 | 0077 | 4 | B | Introduction of NR MBS enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233830 | 0078 | 4 | B | Introducing enhancement for NR XR | 18.0.0 | +| 2023-12 | RAN#102 | RP-233823 | 0088 | 3 | B | Support of NR SL relay enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233818 | 0097 | 0 | B | on subsequent CPAC | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37877/raw.md b/marked/Rel-18/37_series/37877/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f85e03fe1eecfb8cd2e796f5dc5917b57651f6e0 --- /dev/null +++ b/marked/Rel-18/37_series/37877/raw.md @@ -0,0 +1,329 @@ + + +# 3GPP TR 37.877 V18.0.0 (2023-12) --- + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx switching; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 Background ..... | 7 | +| 4.1 TR Maintenance ..... | 7 | +| 5 Specific Band Combinations..... | 7 | +| 5.1 NR band combinations..... | 7 | +| 5.1.1 CA_n1-n5-n78..... | 7 | +| 5.1.1.1 Configurations ..... | 7 | +| 5.1.1.2 Technical analysis..... | 7 | +| 5.1.1.3 Conclusion ..... | 7 | +| 5.1.2 CA_n3-n5-n78..... | 8 | +| 5.1.2.1 Configurations ..... | 8 | +| 5.1.2.2 Technical analysis..... | 8 | +| 5.1.2.3 Conclusion ..... | 8 | +| 6 Release Independent Requirements ..... | 8 | +| 6.1 Inter-band CA..... | 8 | +| 6.2 Inter-band EN-DC ..... | 9 | +| Annex A (informative): Common UE RF requirements ..... | 9 | +| A.1 Common UE RF requirements for Inter-band EN-DC with tx switching..... | 9 | +| A.2 Common UE RF requirements for Inter-band CA configurations with tx switching within NR FR1 ..... | 10 | +| Annex B (informative): Change history ..... | 11 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document is a technical report for WI “Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx Switching in Uplink” under Rel-18 time frame. The purpose is to gather the relevant background information and studies in order to address the band combinations requested for mandating no DL interruption to conduct dynamic Tx switching in uplink listed in Table 1-1. + +**Table 1-1: Band combinations requested for mandating no DL interruption** + +| Configuration | Uplink configuration | +|---------------|----------------------| +| CA n1-n5-n78 | CA n1-n78, CA n5-n78 | +| CA n3-n5-n78 | CA n3-n78, CA n5-n78 | + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] TS38.101-1, NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone +- [3] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [4] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios". + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +# 4 Background + +At 3GPP RAN#96 meeting, a new basket Work Item “Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx Switching in Uplink” was approved. The objectives are as following, + +For the core part: + +- Discuss and specify inter-band uplink CA and EN-DC combinations for which DL interruption is not allowed when dynamic switching between two uplink carriers is conducted. + - 1) Based on the requested band combinations from operators, analyze if it is feasible to specify no DL interruption in RAN4 specification. + - 2) Based on the feasibility analysis for specific combination, decide to introduce no DL interruption in RAN4 specification. + +For the performance part: + +- For 2CC 1Tx-2Tx switching, the mandating of no DL interruption for new band combinations is release independent from Rel-16. +- For 3CC 1Tx-2Tx switching and 2CC or 3CC 2Tx-2Tx switching, the mandating of no DL interruption for new band combinations is release independent from Rel-17. + +The present document is the technical report for this basket Work Item. + +## 4.1 TR Maintenance + +A single company is responsible for introducing all approved TPs in the current TR, i.e. TR editor. However, it is the responsibility of the contact person of each band/band combination to ensure that the TPs related to the band/band combination have been implemented. + +# 5 Specific Band Combinations + +## 5.1 NR band combinations + +### 5.1.1 CA\_n1-n5-n78 + +#### 5.1.1.1 Configurations + +**Table 5.1.1.1-1: CA configuration for mandating no DL interruption** + +| Configuration | Uplink configuration | +|---------------|----------------------| +| CA_n1-n5-n78 | CA_n1-n78, CA_n5-n78 | + +#### 5.1.1.2 Technical analysis + +For CA\_n1-n78 and CA\_n5-n78, no DL interruption allowed has been specified as mandated in 38101-1, which means switching from n1/n5 to n78 has no impact to n1/n5 downlink. Thus there is no DL interruption for CA\_n1-n5-n78 with CA\_n1-n78 or CA\_n5-n78 uplink configuration when conducting dynamic Tx switching. + +#### 5.1.1.3 Conclusion + +No DL interruption for CA\_n1-n5-n78 with CA\_n1-n78 or CA\_n5-n78 uplink configuration is mandated. + +**Table 5.1.1.3-1: Inter-band CA operating bands involving FR1 (three bands)** + +| NR CA Band | NR Band
(Table 5.2-1) | DL interruption
allowed (Note 3) | +|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------------------------| +| CA_n1-n5-n78 | n1, n5, n78 | No for CA_n1-n78,
CA_n5-n78 | +| NOTE 4: Applicable when dynamic Tx switching is conducted. The DL interruption requirement is specified in clause 8.2.2.2.10 of 38.133 [3]. | | | + +### 5.1.2 CA\_n3-n5-n78 + +#### 5.1.2.1 Configurations + +**Table 5.1.2.1-1: CA configuration for mandating no DL interruption** + +| Configuration | Uplink configuration | +|---------------|----------------------| +| CA_n3-n5-n78 | CA_n3-n78, CA_n5-n78 | + +#### 5.1.2.2 Technical analysis + +For CA\_n3-n78 and CA\_n5-n78, no DL interruption allowed has been specified as mandated in 38.101-1, which means switching from n3/n5 to n78 has no impact to n3/n5 downlink. Thus there is no DL interruption for CA\_n3-n5-n78 with CA\_n3-n78 or CA\_n5-n78 uplink configuration when conducting dynamic Tx switching. + +#### 5.1.2.3 Conclusion + +No DL interruption for CA\_n3-n5-n78 with CA\_n3-n78 or CA\_n5-n78 uplink configuration is mandated. + +**Table 5.1.2.3-1: Inter-band CA operating bands involving FR1 (three bands)** + +| NR CA Band | NR Band
(Table 5.2-1) | DL interruption
allowed (Note 3) | +|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------------------------| +| CA_n3-n5-n78 | n3, n5, n78 | No for CA_n3-n78,
CA_n5-n78 | +| NOTE 4: Applicable when dynamic Tx switching is conducted. The DL interruption requirement is specified in clause 8.2.2.2.10 of 38.133 [3]. | | | + +# 6 Release Independent Requirements + +The mandating of no DL interruption requirement belongs to the feature of inter-band CA or EN-DC with tx switching. Thus to specify the release independent requirement shall involve the feature of tx switching. The specific requirements need to be fulfilled include downlink interruption requirement, mandating no DL interruption requirement and time mask requirements as specified in the 38.133 [3] and 38.101-1 [2]. Because RRM downlink interruption requirement is referred when specifying mandating no DL interruption in 38.101-1, only UE RF requirements are listed in the last column of the table in the clause 6.1 and 6.2, which are the requirements to be fulfilled by inter-band CA or EN-DC to support tx switching feature. + +## 6.1 Inter-band CA + +Requirements for a Rel-16 UE for additional NR inter-band CA configurations within FR1 compared to TS 38.101-1 of Rel-16 [2] are introduced via this clause. + +Requirements for a Rel-17 UE for additional NR inter-band CA configurations within FR1 compared to TS 38.101-1 of Rel-17 [2] are introduced via this clause. + +Table 6.1-1: NR inter-band CA within FR1 + +| Feature | DL/UL | Maximum number of bands | number of CCs | CA BW Classes | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|-------------------------------------------------------------------|-------|-------------------------|---------------|---------------|------------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Inter-band CA configurations with 1Tx-2Tx switching within NR FR1 | UL | 2 | 2 | A | TDD, FDD and TDD | Rel-16 | Table A.2-1 | +| Inter-band CA configurations with 1Tx-2Tx switching within NR FR1 | UL | 2 | 3 | A, B, C | TDD, FDD and TDD | Rel-17 | Table A.2-1 | +| Inter-band CA configurations with 2Tx-2Tx switching within NR FR1 | UL | 2 | 2 | A | TDD, FDD and TDD | Rel-17 | Table A.2-1 | +| | | 2 | 3 | A, B, C | | | | + +## 6.2 Inter-band EN-DC + +Requirements for a Rel-16 UE for additional EN-DC inter-band configurations within FR1 compared to TS 38.101-3 of Rel-16 [4] are introduced via this clause. + +Table 6.2-1: EN-DC inter-band configurations without SUL within FR1 + +| Feature | DL/UL | maximum number of E-UTRA bands | maximum number of E-UTRA CCs | maximum number of NR bands | maximum number of NR CCs | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|-----------------------------------------|-------|--------------------------------|------------------------------|----------------------------|--------------------------|------------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Inter-band EN-DC with 1Tx-2Tx switching | UL | 1 | 1 | 1 | 1 | TDD, FDD and TDD | Rel-16 | Table A.1-1 | + +# Annex A (informative): Common UE RF requirements + +## A.1 Common UE RF requirements for Inter-band EN-DC with tx switching + +The requirements and test cases listed in Table A.1-1 are specified in in REL-16 version of TS 38.101-3 [4]. + +Table A.1-1: Common UE RF requirements for Inter-band EN-DC with tx switching + +| Clause | Description | +|--------|-----------------------------------------------------------------| +| 5.5B.4 | Configuration for Inter-band EN-DC within FR1 | +| 6.3B.4 | Output power dynamics for switching between two uplink carriers | + +## A.2 Common UE RF requirements for Inter-band CA configurations with tx switching within NR FR1 + +The requirements and test cases listed in Table A.2-1 are specified in Rel-16 version of TS 38.101-1 [2]. + +The requirements and test cases listed in Table A.2-1 are specified in Rel-17 version of TS 38.101-1 [2]. + +**Table A.2-1: Common UE RF requirements for Inter-band CA configurations with tx switching within NR FR1** + +| Clause | Description | +|----------|---------------------------------------------| +| 5.2A.2 | Operating bands for inter-band CA | +| 6.3A.3.3 | Transmit ON/OFF time mask for inter-band CA | + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-08 | RAN4 #104-e | R4-2212699 | | | | TR skeleton | 0.0.1 | +| 2022-10 | RAN4#104-bis-e | R4-2216097 | | | | Implement the following TPs from RAN4#104-bis-e:
R4-2216096, TP to 37.877 DL interruption clarification for CA_n1-n5-n78 at dynamic Tx switching, China Telecom | 0.1.0 | +| 2022-11 | RAN4#105 | R4-2218608 | | | | Implement the following TPs from RAN4#105:
R4-2218607, TP to 37.877 DL interruption clarification for CA_n3-n5-n78 at dynamic Tx switching, China Telecom | 0.2.0 | +| 2023-04 | RAN4#106bis-e | R4-2305155 | | | | Implement the following TPs from RAN4#106bis-e:
R4-2306549, TP to TR 37.877: Release independence on mandating no DL interruption for Tx Switching, China Telecom | 0.3.0 | +| 2023-12 | RAN#102 | RP-23xxxx | | | | Editorial change and change history update | 1.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37878/raw.md b/marked/Rel-18/37_series/37878/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b651ef7d9cbe4704931478844132399244a947fe --- /dev/null +++ b/marked/Rel-18/37_series/37878/raw.md @@ -0,0 +1,597 @@ + + +# 3GPP TR 37.878 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X PC5 band (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. At the bottom, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | | +|---------|------------------------------------------------------------------------|-----------| +| 1 | Scope..... | 5 | +| 2 | References..... | 5 | +| 3 | Definitions, symbols and abbreviations ..... | 6 | +| 3.1 | Definitions..... | 6 | +| 3.2 | Symbols..... | 6 | +| 3.3 | Abbreviations ..... | 6 | +| 4 | Background ..... | 6 | +| 4.1 | Justification ..... | 6 | +| 4.2 | Objective ..... | 6 | +| 5 | Void..... | 7 | +| 6 | Con-current operation between one Uu band and one PC5 band ..... | 7 | +| 6.1 | Con-current operation between one LTE Uu band and one NR PC5 band..... | 7 | +| 6.1.1 | V2X_34A_n47A..... | 7 | +| 6.1.1.1 | Operating bands for V2X_34A_n47A..... | 7 | +| 6.1.1.2 | Channel bandwidths per operating band for V2X_34A_n47A ..... | 8 | +| 6.1.1.3 | UE co-existence studies ..... | 8 | +| 6.1.1.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values..... | 8 | +| 6.2 | Con-current operation between one NR Uu band and one NR PC5 band ..... | 8 | +| 6.2.1 | V2X_n34A-n47A ..... | 8 | +| 6.2.1.1 | Operating bands for V2X_n34A-n47A..... | 8 | +| 6.2.1.2 | Channel bandwidths per operating band for V2X_n34A-n47A ..... | 9 | +| 6.2.1.3 | Coexistence studies..... | 10 | +| 6.2.1.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values..... | 13 | +| 6.2.2 | V2X_n3A-n47A ..... | 13 | +| 6.2.2.1 | Operating bands for V2X_n3A-n47A..... | 13 | +| 6.2.2.2 | Channel bandwidths per operating band for V2X_n3A-n47A ..... | 14 | +| 6.2.2.3 | UE co-existence studies ..... | 14 | +| 6.2.2.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values..... | 16 | +| 6.3 | Con-current operation between one NR Uu band and one LTE PC5 band..... | 16 | +| 6.3.1 | V2X_n34A_47A..... | 16 | +| 6.3.1.1 | Operating bands for V2X_n34A_47A..... | 16 | +| 6.3.1.2 | Channel bandwidths per operating band for V2X_n34A_47A ..... | 17 | +| 6.3.1.3 | UE co-existence studies ..... | 17 | +| 6.3.1.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values..... | 17 | +| 6.3.2 | V2X_n3A_47A..... | 17 | +| 6.3.2.1 | Operating bands for V2X_n3A_47A..... | 17 | +| 6.3.2.2 | Channel bandwidths per operating band for V2X_n3A_47A ..... | 18 | +| 6.3.2.3 | UE co-existence studies ..... | 18 | +| 6.3.2.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values..... | 18 | +| 7 | Void..... | 18 | +| | Annex A: Change history ..... | 19 | + +# --- 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 the Technical Report on TR on band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X band in Release 18. + +The purpose of the present document is to study the extension of the band combinations for V2X service to grow the NR V2X ecosystem. Operators propose new band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X band. Whether to specify con-current operation of LTE/NR CA/DC band combinations and V2X band depends on requests in Rel-18. Specifically, the self-desensitization problem of con-current operation band combinations will be analysed including harmonics, IMD problem, etc.. Also the candidate solutions will be studied to solve the self-desensitization problem. + +**Table 1-1: Release 18 NR V2X band combinations** + +| V2X Band combination | REL independent from | +|----------------------|----------------------| +| V2X_n3-n47 | Rel-16 | +| V2X_n34-n47 | Rel-16 | +| V2X_n3_47 | Rel-16 | +| V2X_n34_47 | Rel-16 | +| V2X_34_n47 | Rel-16 | + +Note: All band combinations in table 1-1 that are release independent from Rel-16 are optional + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] RP-221879: " New WID: Rel-18 band combinations for concurrent operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X PC5 band ". +- [3] 3GPP TR 38.886 V16.3.0: " V2X Services based on NR; User Equipment (UE) radio transmission and reception". +- [4] 3GPP TR 38.785 V17.0.0: " User Equipment (UE) radio transmission and reception for enhanced NR sidelink". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------| +| $\Delta R_{IB,c}$ | Allowed reference sensitivity relaxation due to support for CA or DC operation, for serving cell $c$ . | +| $\Delta T_{IB,c}$ | Allowed maximum configured output power relaxation due to support for CA or DC operation, for serving cell $c$ | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|---------|-----------------------------------| +| CA | Carrier Aggregation | +| CC | Component Carrier | +| DC | Dual Connectivity | +| ITS | Intelligent Transportation System | +| MSD | Maximum Sensitivity Degradation | +| REFSENS | Reference Sensitivity | + +# 4 Background + +## 4.1 Justification + +3GPP has completed the Release 17 work item on NR V2X including RAN4 minimum requirements and frequency bands for V2X operation. The current specification considers an set of frequency bands for PC5 interface and requirement frame work for con-current operation between Uu bands and V2X bands as part of Release 17 work. + +However, in order to further enhance the V2X ecosystem, it is necessary to set up a basket WI to introduce more band combinations on con-current operation of Uu bands and V2X bands in Release 18. + +## 4.2 Objective + +The objective of this work item is to specify band specific RF requirements for the following scenarios with maximum two simultaneous transmission bands within FR1: + +- Con-current operation between NR Uu band and NR PC5 band. +- Con-current operation between LTE Uu band and NR PC5 band. +- Con-current operation between NR Uu band and LTE PC5 band. +- Whether to specify con-current operation of LTE/NR CA/DC band combinations + PC5 V2X band depending on requests in Rel-18. + - If there is such request the denotation on the combination definition need to be discussed at first. + +- Analyse con-current operation band combinations that have self-desensitization due to following reasons: + - TX Harmonic and/or inter modulation overlap of receive band + - TX signal overlap of receiver harmonic frequency + - TX frequency being in close proximity of one of the receive bands + - Any other identified reasons +- For the combination where self-desensitization exists, specify at least needed + - $\Delta T_{IB}$ and $\Delta R_{IB}$ + - Reference sensitivity excerpts + - UL/SL RB restrictions for REFSENS test +- Add conformance testing in RAN5 specifications (to follow at a later stage) + +of all REL-18 V2X con-current operation band combinations that fall into the category defined by the WI title. + +An overview of these V2X con-current operation band combinations is provided in the attached Excel. + +NOTE: Only power class 3 (PC3) is considered in this work item. + +# 5 Void + +# 6 Con-current operation between one Uu band and one PC5 band + +## 6.1 Con-current operation between one LTE Uu band and one NR PC5 band + +### 6.1.1 V2X\_34A\_n47A + +#### 6.1.1.1 Operating bands for V2X\_34A\_n47A + +The operating bands for V2X\_34A\_n47A are specified in table 6.1.1.1-1. + +**Table 6.1.1.1-1: Inter-band con-current V2X operating bands for V2X\_34A\_n47A** + +| V2X con-current configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band | | | Downlink (DL) band | | | Duplex Mode | | +|-------------------------------|----------------------------|-----------|--------------------------|---|----------------------|--------------------------|---|----------------------|-------------|--| +| | | | BS receive / UE transmit | | | BS transmit / UE receive | | | | | +| | | | F UL_low | – | F UL_high | F DL_low | – | F DL_high | | | +| V2X_34A_n47A | 34 | Uu | 2010 MHz | – | 2025 MHz | 2010 MHz | – | 2025 MHz | TDD | | +| | n47 | PC5 | 5855 MHz | – | 5925 MHz | 5855 MHz | – | 5925 MHz | HD | | + +#### 6.1.1.2 Channel bandwidths per operating band for V2X\_34A\_n47A + +The channel bandwidths per operating band for V2X\_34A\_n47A are specified in table 6.1.1.2-1. + +**Table 6.1.1.2-1: V2X inter-band con-current configurations and bandwidth combination sets for V2X\_34A\_n47A** + +| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz) | Maximum aggregated bandwidth [MHz] | Bandwidth combination set | +|------------------------------|----------------------------|---------|-------------------------|------------------------------------|---------------------------| +| V2X_34A_n47A | 34 | 15 | 5, 10, 15 | 55 | 0 | +| | n47 | 15 | 10, 20, 30, 40 | | | +| | | 30 | 10, 20, 30, 40 | | | +| | | 60 | 10, 20, 30, 40 | | | + +#### 6.1.1.3 UE co-existence studies + +The UE co-existence studies specified for V2X\_n34A-n47A in clause 6.2.1.3 are applicable to V2X\_34A\_n47A since band 34 and band n34 have the same frequency range. + +#### 6.1.1.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values + +**Table 6.1.1.4-1: $\Delta T_{IB,c}$ for inter-band con-current V2X operation (two bands)** + +| V2X con-current band Combination | E-UTRA or V2X Operating Band | $\Delta T_{IB,c}$ [dB] | +|----------------------------------|------------------------------|------------------------| +| V2X_34A_n47A | 34 | 0.0 | + +**Table 6.1.1.4-2: $\Delta R_{IB,c}$ for inter-band con-current V2X operation (two bands)** + +| V2X inter-band con-current band Combination | E-UTRA Band | $\Delta R_{IB,c}$ [dB] | +|---------------------------------------------|-------------|------------------------| +| V2X_34A_n47A | 34 | 0.0 | + +## 6.2 Con-current operation between one NR Uu band and one NR PC5 band + +### 6.2.1 V2X\_n34A-n47A + +#### 6.2.1.1 Operating bands for V2X\_n34A-n47A + +The operating bands for V2X\_n34A-n47A are specified in table 6.2.1.1-1. + +Table 6.2.1.1-1: Inter-band concurrent V2X operating bands for V2X\_n34A-n47A + +| V2X concurrent configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band | | | Downlink (DL) band | | | Duplex Mode | | +|------------------------------|----------------------------|-----------|--------------------------|---|----------------------|--------------------------|---|----------------------|-------------|--| +| | | | BS receive / UE transmit | | | BS transmit / UE receive | | | | | +| | | | F UL_low | – | F UL_high | F DL_low | – | F DL_high | | | +| V2X_n34A-n47A | n34 | Uu | 2010 MHz | – | 2025 MHz | 2010 MHz | – | 2025 MHz | TDD | | +| | n47 | PC5 | 5855 MHz | – | 5925 MHz | 5855 MHz | – | 5925 MHz | HD | | + +#### 6.2.1.2 Channel bandwidths per operating band for V2X\_n34A-n47A + +The channel bandwidths per operating band for V2X\_n34A-n47A are specified in table 6.2.1.2-1. + +**Table 6.2.1.2-1: V2X inter-band concurrent configurations and bandwidth combination sets for V2X\_n34A-n47A** + +| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz) | Maximum aggregated bandwidth [MHz] | Bandwidth combination set | +|------------------------------|----------------------------|---------|-------------------------|------------------------------------|---------------------------| +| V2X_n34A_n47A | n34 | 15 | 5, 10, 15 | 55 | 0 | +| | | 30 | 10, 15 | | | +| | | 60 | 10, 15 | | | +| | n47 | 15 | 10, 20, 30, 40 | | | +| | | 30 | 10, 20, 30, 40 | | | +| | | 60 | 10, 20, 30, 40 | | | + +#### 6.2.1.3 Coexistence studies + +The harmonics analysis for V2X\_n34A-n47A is specified in table 6.2.1.3-1. Up to 4th harmonics of band n34 are provided since the frequency range of the 5th harmonics is much higher than 5.9GHz. The harmonics of band n47 are not listed as the harmonics distributed in the frequency range much higher than 5.9GHz have no impact on GNSS and ISM bands. + +**Table 6.2.1.3-1: Harmonics analysis for V2X\_n34A-n47A** + +| Operating Band | Band n34 | | Band n47 | | | +|--------------------------------------|----------------|----------|-----------|-----------|---------| +| | UE UL carriers | fx_low | fx_high | fy_low | fy_high | +| UL frequency (MHz) | | 2010 | 2025 | 5855 | 5925 | +| 2nd harmonics frequency limits | | 2*fx_low | 2*fx_high | No effect | | +| 2nd harmonics frequency limits (MHz) | | 4020 | 4050 | | | +| 3rd harmonics frequency limits | | 3*fx_low | 3*fx_high | No effect | | +| 3rd harmonics frequency limits (MHz) | | 6030 | 6075 | | | +| 4th harmonics frequency limits | | 4*fx_low | 4*fx_high | No effect | | +| 4th harmonics frequency limits (MHz) | | 8040 | 8100 | | | + +The IMD analysis for V2X\_n34A-n47A is specified in table 6.2.1.3-2. Up to the 5th order IMDs of band n34 and band n47 are provided. Based on the IMD analysis, it is observed that no IMD products fall into the associated bands. + +**Table 6.2.1.3-2: IMD analysis for V2X\_n34A-n47A** + +| Operating Band | Band 34 | | Band n47 | | +|--------------------------------------------------|----------------------|-----------------------|----------------------|-----------------------| +| UE UL carriers | fx_low | fx_high | fy_low | fy_high | +| UL frequency (MHz) | 2010 | 2025 | 5855 | 5925 | +| 2 nd harmonics frequency limits | 2*fx_low | 2*fx_high | 2* fy_low | 2* fy_high | +| 2 nd harmonics frequency limits (MHz) | 4020 | 4050 | 11710 | 11850 | +| 3 rd harmonics frequency limits | 3*fx_low | 3*fx_high | 3* fy_low | 3* fy_high | +| 3 rd harmonics frequency limits (MHz) | 6030 | 6075 | 17565 | 17775 | +| Two tone 2 nd order IMD products | fy_low – fx_high | fy_high – fx_low | fy_low + fx_low | fy_high + fx_high | +| IMD frequency limits (MHz) | 3830 | 3915 | 7865 | 7950 | +| Two-tone 3 rd order IMD products | 2*fx_low – fy_high | 2*fx_high – fy_low | 2*fy_low – fx_high | 2*fy_high – fx_low | +| IMD frequency limits (MHz) | 1905 | 1805 | 9685 | 9840 | +| Two-tone 3 rd order IMD products | 2*fx_low + fy_low | 2*fx_high + fy_high | 2*fy_low + fx_low | 2*fy_high + fx_high | +| IMD frequency limits (MHz) | 9875 | 9975 | 13720 | 13875 | +| Two-tone 4 th order IMD products | 3*fx_low – fy_high | 3*fx_high – fy_low | 3*fy_low – fx_high | 3*fy_high – fx_low | +| IMD frequency limits (MHz) | 105 | 220 | 15540 | 15765 | +| Two-tone 4 th order IMD products | 3*fx_low + fy_low | 3*fx_high + fy_high | 3*fy_low + fx_low | 3*fy_high + fx_high | +| IMD frequency limits (MHz) | 11885 | 12000 | 19575 | 19800 | +| Two-tone 4 th order IMD products | 2*fx_low – 2*fy_high | 2*fx_high – 2*fy_low | 2*fy_low + 2*fy_low | 2*fx_high + 2*fy_high | +| IMD frequency limits (MHz) | 7830 | 7660 | 15730 | 15900 | +| Two-tone 5 th order IMD products | fx_low – 4*fy_high | fx_high – 4*fy_low | fy_low – 4*fx_high | fy_high – 4*fx_low | +| IMD frequency limits (MHz) | 21690 | 21395 | 2245 | 2115 | +| Two-tone 5 th order IMD products | fx_low + 4*fy_low | fx_high + 4*fy_high | fy_low + 4*fx_low | fy_high + 4*fx_high | +| IMD frequency limits (MHz) | 25430 | 25725 | 13895 | 14025 | +| Two-tone 5 th order IMD products | 2*fx_low – 3*fy_high | 2*fx_high – 3*fy_low | 2*fy_low – 3*fx_high | 2*fy_high – 3*fx_low | +| IMD frequency limits (MHz) | 13755 | 13515 | 5635 | 5820 | +| Two-tone 5 th order IMD products | 2*fx_low + 3*fy_low | 2*fx_high + 3*fy_high | 2*fy_low + 3*fx_low | 2*fy_high + 3*fx_high | + +| | | | | | +|----------------------------|-------|-------|-------|-------| +| IMD frequency limits (MHz) | 21585 | 21825 | 17740 | 17925 | +|----------------------------|-------|-------|-------|-------| + +The harmonics and intermodulation products should be evaluated when V2X inter-band concurrent operating UE coexists with other systems such as GNSS and ISM. The harmonics and IMD analysis of V2X\_n34A-n47A for GNSS and ISM bands is shown in table 6.2.1.3-3. Based on the analysis for GNSS and ISM bands, band n47 has an impact on the ISM band (5GHz). + +**Table 6.2.1.3-3: Harmonic and IMDs analysis of V2X\_n34A-n47A UE for GNSS and ISM bands** + +| Victim Systems | Frequency range [MHz] | | | Impact | Regions | Comments | +|-------------------|-----------------------|---|--------|--------|-----------|-------------------------------| +| COMPASS (Beidou) | 1559 | - | 1591 | No | | | +| Galileo | 1559 | - | 1591 | No | | | +| GLONASS | 1591 | - | 1610 | No | | | +| GPS | 1563 | - | 1587 | No | | | +| ISM band (2.4GHz) | 2400 | - | 2483.5 | No | US/Europe | | +| | 2400 | - | 2494 | No | Asia | | +| ISM band (5GHz) | 5150 | - | 5925 | Yes | US | 5 th IMD, Band n47 | +| | 5150 | - | 5350 | Yes | Europe | | +| | 5470 | - | 5725 | Yes | | 5 th IMD | +| | 5150 | - | 5825 | Yes | Asia | 5 th IMD | + +#### 6.2.1.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values + +**Table 6.2.1.4-1: $\Delta T_{IB,c}$ for inter-band concurrent V2X operation (two bands)** + +| V2X concurrent band Combination | NR Operating Band | $\Delta T_{IB,c}$ [dB] | +|---------------------------------|-------------------|------------------------| +| V2X_n34A-n47A | n34 | 0.0 | + +**Table 6.2.1.4-2: $\Delta R_{IB,c}$ for inter-band concurrent V2X operation (two bands)** + +| V2X inter-band concurrent band Combination | NR Operating Band | $\Delta R_{IB,c}$ [dB] | +|--------------------------------------------|-------------------|------------------------| +| V2X_n34A-n47A | n34 | 0.0 | + +### 6.2.2 V2X\_n3A-n47A + +#### 6.2.2.1 Operating bands for V2X\_n3A-n47A + +The operating bands for V2X\_n3A-n47A are specified in table 6.2.2.1-1. + +Table 6.2.2.1-1: Inter-band concurrent V2X operating bands for V2X\_n3A-n47A + +| V2X concurrent configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band | | | Downlink (DL) band | | | Duplex Mode | | +|------------------------------|----------------------------|-----------|--------------------------|---|----------------------|--------------------------|---|----------------------|-------------|--| +| | | | BS receive / UE transmit | | | BS transmit / UE receive | | | | | +| | | | F UL_low | – | F UL_high | F DL_low | – | F DL_high | | | +| V2X_n3A-n47A | n3 | Uu | 1710 MHz | – | 1785 MHz | 1805 MHz | – | 1880 MHz | FDD | | +| | n47 | PC5 | 5855 MHz | – | 5925 MHz | 5855 MHz | – | 5925 MHz | HD | | + +#### 6.2.2.2 Channel bandwidths per operating band for V2X\_n3A-n47A + +The channel bandwidths per operating band for V2X\_n3A-n47A are specified in table 6.2.2.2-1. + +Table 6.2.2.2-1: V2X inter-band concurrent configurations and bandwidth combination sets for V2X\_n3A-n47A + +| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz) | Maximum aggregated bandwidth [MHz] | Bandwidth combination set | +|------------------------------|----------------------------|---------|---------------------------------------|------------------------------------|---------------------------| +| V2X_n3A-n47A | n3 | 15 | 5, 10, 15, 20, 25, 30, 35, 40, 45, 50 | 90 | 0 | +| | | 30 | 10, 15, 20, 25, 30, 35, 40, 45, 50 | | | +| | | 60 | 10, 15, 20, 25, 30, 35, 40, 45, 50 | | | +| | n47 | 15 | 10, 20, 30, 40 | | | +| | | 30 | 10, 20, 30, 40 | | | +| | | 60 | 10, 20, 30, 40 | | | + +#### 6.2.2.3 UE co-existence studies + +The harmonics analysis for V2X\_n3A-n47A is specified in table 6.2.2.3-1. Up to the 3rd harmonics of band 3 are provided since the frequency range of the 4th harmonics is higher than 5.9GHz. The harmonics of band n47 are not listed as the harmonics distributed in the frequency range much higher than 5.9GHz have no impact on GNSS and ISM bands. Based on the harmonics analysis, it is observed that the 3rd harmonics of band 3 have no impact on band n47. + +Table 6.2.2.3-1: Harmonics analysis for V2X\_n3A-n47A + +| Operating Band | Band 3 | | Band n47 | | +|--------------------------------------|----------|-----------|-----------|---------| +| UE UL carriers | fx_low | fx_high | fy_low | fy_high | +| UL frequency (MHz) | 1710 | 1785 | 5855 | 5925 | +| 2nd harmonics frequency limits | 2*fx_low | 2*fx_high | No effect | | +| 2nd harmonics frequency limits (MHz) | 3420 | 3570 | | | +| 3rd harmonics frequency limits | 3*fx_low | 3*fx_high | No effect | | +| 3rd harmonics frequency limits (MHz) | 5130 | 5355 | | | + +The IMD analysis for V2X\_n3A-n47A is specified in table 6.2.2.3-2. Up to the 5th order IMDs of band 3 and band n47 are provided. Based on the IMD analysis, it is observed that no IMD products fall into the associated bands. So there is no IMD issue caused by the band combination. + +Table 6.2.2.3-2: IMD analysis for V2X\_n3A-n47A + +| Operating Band | Band 3 | | Band n47 | | | +|--------------------------------------------------|----------------|----------------------|-----------------------|----------------------|-----------------------| +| | UE UL carriers | fx_low | fx_high | fy_low | fy_high | +| UL frequency (MHz) | | 1710 | 1785 | 5855 | 5925 | +| 2 nd harmonics frequency limits | | 2*fx_low | 2*fx_high | 2* fy_low | 2* fy_high | +| 2 nd harmonics frequency limits (MHz) | | 3420 | 3570 | 11710 | 11850 | +| 3 rd harmonics frequency limits | | 3*fx_low | 3*fx_high | 3* fy_low | 3* fy_high | +| 3 rd harmonics frequency limits (MHz) | | 5130 | 5355 | 17565 | 17775 | +| Two tone 2 nd order IMD products | | fy_low – fx_high | fy_high – fx_low | fy_low + fx_low | fy_high + fx_high | +| IMD frequency limits (MHz) | | 4070 | 4215 | 7565 | 7710 | +| Two-tone 3 rd order IMD products | | 2*fx_low – fy_high | 2*fx_high – fy_low | 2*fy_low – fx_high | 2*fy_high – fx_low | +| IMD frequency limits (MHz) | | 2505 | 2285 | 9925 | 10140 | +| Two-tone 3 rd order IMD products | | 2*fx_low + fy_low | 2*fx_high + fy_high | 2*fy_low + fx_low | 2*fy_high + fx_high | +| IMD frequency limits (MHz) | | 9275 | 9425 | 13420 | 13635 | +| Two-tone 4 th order IMD products | | 3*fx_low – fy_high | 3*fx_high – fy_low | 3*fy_low – fx_high | 3*fy_high – fx_low | +| IMD frequency limits (MHz) | | 795 | 500 | 15780 | 16065 | +| Two-tone 4 th order IMD products | | 3*fx_low + fy_low | 3*fx_high + fy_high | 3*fy_low + fx_low | 3*fy_high + fx_high | +| IMD frequency limits (MHz) | | 10985 | 11280 | 19275 | 19560 | +| Two-tone 4 th order IMD products | | 2*fx_low – 2*fy_high | 2*fx_high – 2*fy_low | 2*fx_low + 2*fy_low | 2*fx_high + 2*fy_high | +| IMD frequency limits (MHz) | | 8430 | 8140 | 15130 | 15420 | +| Two-tone 5 th order IMD products | | fx_low – 4*fy_high | fx_high – 4*fy_low | fy_low – 4*fx_high | fy_high – 4*fx_low | +| IMD frequency limits (MHz) | | 21990 | 21635 | 1285 | 915 | +| Two-tone 5 th order IMD products | | fx_low + 4*fy_low | fx_high + 4*fy_high | fy_low + 4*fx_low | fy_high + 4*fx_high | +| IMD frequency limits (MHz) | | 25130 | 25485 | 12695 | 13065 | +| Two-tone 5 th order IMD products | | 2*fx_low – 3*fy_high | 2*fx_high – 3*fy_low | 2*fy_low – 3*fx_high | 2*fy_high – 3*fx_low | +| IMD frequency limits (MHz) | | 14355 | 13995 | 6355 | 6720 | +| Two-tone 5 th order IMD products | | 2*fx_low + 3*fy_low | 2*fx_high + 3*fy_high | 2*fy_low + 3*fx_low | 2*fy_high + 3*fx_high | +| IMD frequency limits (MHz) | | 20985 | 21345 | 16840 | 17205 | + +The harmonics and intermodulation products should be evaluated when V2X inter-band concurrent operating UE coexists with other systems such as GNSS and ISM. The harmonics and IMD analysis of V2X\_n3A-n47A for GNSS and ISM bands is shown in table 6.2.2.3-3. Based on the analysis for GNSS and ISM bands, band n47 and the 3rd harmonics of band 3 have an impact on the ISM band (5GHZ). + +Table 6.2.2.3-3: Harmonic and IMDs analysis of V2X\_n3A-n47A UE for GNSS and ISM bands + +| Victim Systems | Frequency range [MHz] | | | Impact | Regions | Comments | +|-------------------|-----------------------|---|--------|--------|-----------|--------------------------------------------------| +| COMPASS (Beidou) | 1559 | - | 1591 | No | | | +| Galileo | 1559 | - | 1591 | No | | | +| GLONASS | 1591 | - | 1610 | No | | | +| GPS | 1563 | - | 1587 | No | | | +| ISM band (2.4GHz) | 2400 | - | 2483.5 | No | US/Europe | | +| | 2400 | - | 2494 | No | Asia | | +| ISM band (5GHz) | 5150 | - | 5925 | Yes | US | Band n47 and 3 rd harmonics of band 3 | +| | 5150 | - | 5350 | Yes | Europe | 3 rd harmonics of band 3 | +| | 5470 | - | 5725 | Yes | | | +| | 5150 | - | 5825 | Yes | Asia | 3 rd harmonics of band 3 | + +#### 6.2.2.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values + +Table 6.2.2.4-1: $\Delta T_{IB,c}$ for inter-band con-current V2X operation (two bands) + +| V2X con-current band Combination | NR Operating Band | $\Delta T_{IB,c}$ [dB] | +|----------------------------------|-------------------|------------------------| +| V2X_n3A-n47A | n3 | 0.0 | + +Table 6.2.2.4-2: $\Delta R_{IB,c}$ for inter-band con-current V2X operation (two bands) + +| V2X inter-band con-current band Combination | NR Operating Band | $\Delta R_{IB,c}$ [dB] | +|---------------------------------------------|-------------------|------------------------| +| V2X_n3A-n47A | n3 | 0.0 | + +## 6.3 Con-current operation between one NR Uu band and one LTE PC5 band + +### 6.3.1 V2X\_n34A\_47A + +#### 6.3.1.1 Operating bands for V2X\_n34A\_47A + +The operating bands for V2X\_n34A\_47A are specified in table 6.3.1.1-1. + +Table 6.3.1.1-1: Inter-band con-current V2X operating bands for V2X\_n34A\_47A + +| V2X con-current configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band | | | Downlink (DL) band | | | Duplex Mode | | +|-------------------------------|----------------------------|-----------|--------------------------|---|----------------|--------------------------|---|----------------|-------------|--| +| | | | BS receive / UE transmit | | | BS transmit / UE receive | | | | | +| | | | $F_{UL\_low}$ | – | $F_{UL\_high}$ | $F_{DL\_low}$ | – | $F_{DL\_high}$ | | | +| V2X_n34A_47A | n34 | Uu | 2010 MHz | – | 2025 MHz | 2010 MHz | – | 2025 MHz | TDD | | +| | 47 | PC5 | 5855 MHz | – | 5925 MHz | 5855 MHz | – | 5925 MHz | HD | | + +#### 6.3.1.2 Channel bandwidths per operating band for V2X\_n34A\_47A + +The channel bandwidths per operating band for V2X\_n34A\_47A are specified in table 6.3.1.2-1. + +Table 6.3.1.2-1: V2X inter-band con-current configurations and bandwidth combination sets for V2X\_n34A\_47A + +| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz) | Maximum aggregated bandwidth [MHz] | Bandwidth combination set | +|------------------------------|----------------------------|---------|-------------------------|------------------------------------|---------------------------| +| V2X_n34A_47A | n34 | 15 | 5, 10, 15 | 35 | 0 | +| | | 30 | 10, 15 | | | +| | | 60 | 10, 15 | | | +| | 47 | 15 | 10, 20 | 35 | | + +#### 6.3.1.3 UE co-existence studies + +The UE co-existence studies specified for V2X\_n34A-n47A in clause 6.2.1.3 are applicable to V2X\_n34A\_47A since band 47 and band n47 have the same frequency range. + +#### 6.3.1.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values + +Table 6.3.1.4-1: $\Delta T_{IB,c}$ for inter-band con-current V2X operation (two bands) + +| V2X con-current band Combination | NR Operating Band | $\Delta T_{IB,c}$ [dB] | +|----------------------------------|-------------------|------------------------| +| V2X_n34A_47A | n34 | 0.0 | + +Table 6.3.1.4-2: $\Delta R_{IB,c}$ for inter-band con-current V2X operation (two bands) + +| V2X inter-band con-current band Combination | NR Operating Band | $\Delta R_{IB,c}$ [dB] | +|---------------------------------------------|-------------------|------------------------| +| V2X_n34A_47A | n34 | 0.0 | + +### 6.3.2 V2X\_n3A\_47A + +#### 6.3.2.1 Operating bands for V2X\_n3A\_47A + +The operating bands for V2X\_n3A\_47A are specified in table 6.3.2.1-1. + +Table 6.3.2.1-1: Inter-band con-current V2X operating bands for V2X\_n3A\_47A + +| V2X con-current configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band | | | Downlink (DL) band | | | Duplex Mode | | +|-------------------------------|----------------------------|-----------|--------------------------|---|----------------------|--------------------------|---|----------------------|-------------|--| +| | | | BS receive / UE transmit | | | BS transmit / UE receive | | | | | +| | | | F UL_low | – | F UL_high | F DL_low | – | F DL_high | | | +| V2X_n3A_47A | n3 | Uu | 1710 MHz | – | 1785 MHz | 1805 MHz | – | 1880 MHz | FDD | | +| | 47 | PC5 | 5855 MHz | – | 5925 MHz | 5855 MHz | – | 5925 MHz | HD | | + +#### 6.3.2.2 Channel bandwidths per operating band for V2X\_n3A\_47A + +The channel bandwidths per operating band for V2X\_n3A\_47A are specified in table 6.3.2.2-1. + +Table 6.3.2.2-1: V2X inter-band con-current configurations and bandwidth combination sets for V2X\_n3A\_47A + +| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz) | Maximum aggregated bandwidth [MHz] | Bandwidth combination set | +|------------------------------|----------------------------|---------|---------------------------------------|------------------------------------|---------------------------| +| V2X_n3A_47A | n3 | 15 | 5, 10, 15, 20, 25, 30, 35, 40, 45, 50 | 70 | 0 | +| | | 30 | 10, 15, 20, 25, 30, 35, 40, 45, 50 | | | +| | | 60 | 10, 15, 20, 25, 30, 35, 40, 45, 50 | | | +| | 47 | 15 | 10, 20 | | | + +#### 6.3.2.3 UE co-existence studies + +The UE co-existence studies specified for V2X\_n3A-n47A in clause 6.2.2.3 are applicable to V2X\_n3A\_47A since band 47 and band n47 have the same frequency range. + +#### 6.3.2.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values + +Table 6.3.2.4-1: $\Delta T_{IB,c}$ for inter-band con-current V2X operation (two bands) + +| V2X con-current band Combination | NR Operating Band | $\Delta T_{IB,c}$ [dB] | +|----------------------------------|-------------------|------------------------| +| V2X_n3A_47A | n3 | 0.0 | + +Table 6.3.2.4-2: $\Delta R_{IB,c}$ for inter-band con-current V2X operation (two bands) + +| V2X inter-band con-current band Combination | NR Operating Band | $\Delta R_{IB,c}$ [dB] | +|---------------------------------------------|-------------------|------------------------| +| V2X_n3A_47A | n3 | 0.0 | + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-08 | RAN4 #104e | R4-2214902 | | | | Create the TR skeleton | 0.0.1 | +| 2022-10 | RAN4 #104bis-e | R4-2217812 | | | | Capture the following approved TPs:
R4-2217114 TP for V2X_n34A-n47A_V2X_34A-n47A_V2X_n34A-47A
R4-2217115 TP on coexistence study of V2X_n3A-n47A and V2X_n3A_47A | 0.1.0 | +| 2022-11 | RAN4 #105 | R4-2218442 | | | | Capture the following approved TP:
R4-2218198 TP updates for TR37.878 | 0.2.0 | +| 2023-12 | RAN#102 | RP-234066 | | | | Presented to TSG RAN for approval (specification v1.0.0). | 1.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37911/raw.md b/marked/Rel-18/37_series/37911/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4f6ab5e07bfdc75b1d24b5e61a67fff9f517cb21 --- /dev/null +++ b/marked/Rel-18/37_series/37911/raw.md @@ -0,0 +1,1252 @@ + + +# 3GPP TR 37.911 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on self-evaluation towards the IMT-2020 submission of the 3GPP Satellite Radio Interface Technology (Release 18)** + +![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G ADVANCED logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon, and below the entire logo is the text 'A GLOBAL INITIATIVE' in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis + +Valbonne - FRANCE + +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations ..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 8 | +| 4 Self-evaluation of eMBB-s technical performance..... | 9 | +| 4.1 Peak spectral efficiency..... | 9 | +| 4.2 Peak data rate ..... | 9 | +| 4.3 5 th percentile user spectral efficiency..... | 10 | +| 4.4 Average spectral efficiency..... | 10 | +| 4.5 User experienced data rate ..... | 11 | +| 4.6 Area traffic capacity ..... | 12 | +| 4.7 Latency ..... | 13 | +| 4.7.1 General ..... | 13 | +| 4.7.2 User plane latency ..... | 13 | +| 4.7.2.1 General..... | 13 | +| 4.7.2.2 Downlink ..... | 14 | +| 4.7.2.3 Uplink ..... | 15 | +| 4.7.3 Control plane latency..... | 15 | +| 4.8 Energy efficiency ..... | 19 | +| 4.8.1 General ..... | 19 | +| 4.8.2 Network side..... | 19 | +| 4.8.2.1 General..... | 19 | +| 4.8.2.2 Evaluation of sleep ratio ..... | 20 | +| 4.8.2.3 Evaluation of sleep duration ..... | 21 | +| 4.8.3 Device side ..... | 21 | +| 4.8.3.1 General..... | 21 | +| 4.8.3.2 Evaluation of sleep ratio ..... | 21 | +| 4.8.3.3 Evaluation of sleep duration ..... | 23 | +| 4.9 Mobility..... | 23 | +| 4.10 Mobility interruption time ..... | 23 | +| 5 Self-evaluation of mMTC-s technical performance..... | 24 | +| 5.1 Connection density..... | 24 | +| 5.1.1 General ..... | 24 | +| 5.1.2 NR satellite access ..... | 24 | +| 5.1.3 IoT NTN ..... | 25 | +| 6 Self-evaluation of HTC-s technical performance ..... | 26 | +| 6.1 Reliability ..... | 26 | +| 6.1.1 General ..... | 26 | +| 6.1.2 DL reliability ..... | 26 | +| 6.1.3 UL reliability ..... | 26 | +| 7 Self-evaluation of generic requirements ..... | 26 | +| 7.1 Service aspects ..... | 26 | +| 7.2 Bandwidth ..... | 27 | +| 7.2.1 NR satellite access ..... | 27 | +| 7.2.2 IoT NTN ..... | 27 | +| 7.3 Spectrum..... | 28 | +| 7.3.1 NR satellite access ..... | 28 | +| 7.3.2 IoT NTN ..... | 28 | + +| | | | +|-----|--------------------------------------------------------------------------------------------------------|-----------| +| 8 | Conclusions..... | 28 | +| | Annex A: Simulation models and assumptions ..... | 30 | +| A.1 | Evaluation assumption for peak spectral efficiency and peak data rate for NR satellite access..... | 30 | +| A.2 | Evaluation assumption for spectral efficiency for NR satellite access ..... | 30 | +| A.3 | Evaluation assumption for mobility for NR satellite access ..... | 30 | +| A.4 | Evaluation assumptions and results for connection density..... | 31 | +| A.5 | Evaluation assumptions and results for reliability for NR satellite access ..... | 31 | +| | Annex B: Calibration for self-evaluation ..... | 32 | +| | Annex C: ITU-R Submission Templates for IMT-2020 for Satellite Radio Interface Technology ..... | 35 | +| C.1 | Description template – characteristics ..... | 35 | +| C.2 | Description template – link budget..... | 35 | +| C.3 | Compliance templates for services, for spectrum, for technical performance..... | 35 | +| | Annex D: Change history ..... | 36 | + +# Foreword + +This Technical Specification/Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- Introduction + +This report presents the self-evaluation results of by 3GPP 5G (developed by 3GPP as 5G NTN, Release 17 and beyond) developed satellite technology. + +From evaluation perspective, the technologies are evaluated against the technical performance requirements as defined in Report ITU-R M.2514[2] for eMBB-s, mMTC-s and HRC-S use cases, as well as spectrum requirements and service aspects requirements, using the evaluation criteria as defined in the report. Detailed self-evaluation results are provided through Section 4 to 7. + +The conclusion is given in Section 8. + +# --- 1 Scope + +The present document reports on the self-evaluation results for meeting the requirements defined by ITU in Report ITU-R M.2514 [2]. + +# --- 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] Report ITU-R M.2514: "Vision, requirements and evaluation guidelines for satellite radio interface(s) of IMT-2020". +- [3] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [4] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [5] 3GPP TS 38.101-5: "NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements". +- [6] 3GPP TS 38.108: "NR; Satellite Access Node radio transmission and reception". +- [7] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [8] 3GPP TS 38.214: "NR; Physical layer procedures for data". +- [9] Report ITU-R M.2412: "Guidelines for evaluation of radio interface technologies for IMT-2020". +- [10] 3GPP TS 36.102: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception for satellite access". +- [11] 3GPP TS 36.108: "Evolved Universal Terrestrial Radio Access (E-UTRA); Satellite Access Node radio transmission and reception". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +- $f$ Scaling factor can at least take the values 1 and 0.75. + +| | | +|--------------------------------|-----------------------------------------------------------------------------------------------| +| $N_{PRB}^{BW,\mu}$ | Maximum RB allocation in bandwidth $BW$ with numerology $\mu$ ; see clause 4.1 | +| $OH$ | Overhead calculated as the average ratio of the number of REs not used for data transmissions | +| $P_{SSB}$ | SSB set periodicity; see clause 4.8.2 | +| $P_{SIB1}$ | SIB1 periodicity; see clause 4.8.2 | +| $Q_m$ | Maximum modulation order | +| $R_{max}$ | Maximum code rate | +| $R_p$ | Peak data rate | +| $SE_p$ | Peak spectral efficiency | +| $Sleep\_ratio_{Slot\_based}$ | Sleep ratio per slot basis; see clause 4.8.2 | +| $Sleep\_ratio_{Symbol\_based}$ | Sleep ratio per symbol basis; see clause 5.8.1 | +| $T_s^\mu$ | OFDM symbol duration in a subframe for numerology; see clause 4.1 | +| $\mu$ | Numerology (as defined in TS 38.211 [3]) | +| $\nu_{Layers}$ | Maximum number of layers | +| $W_a$ | Assigned bandwidth | + +## 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]. + +| | | +|---------|--------------------------------------------------| +| DL | Downlink | +| DRX | Discontinuous Reception | +| eMBB-s | Enhanced Mobile Broadband - satellite | +| FDD | Frequency division duplexing | +| FR1 | Frequency range 1 | +| FRF | Frequency Reuse Factor | +| HRC-s | High Reliability Communications - satellite | +| IoT NTN | Satellite components of NB-IoT and LTE -MTC | +| LTE-MTC | Long Term Evolution – Machine Type Communication | +| mMTC-s | Massive machine type communications – satellite | +| NB-IoT | Narrowband Internet of Things | +| NR NTN | Satellite component of NR | +| NTN | Non-terrestrial networks | +| OFDM | Orthogonal Frequency Division Multiplexing | +| PBCH | Physical Broadcast CHannel | +| PDCCH | Physical Downlink Control CHannel | +| PDSCH | Physical Downlink Shared CHannel | +| PRACH | Physical Random Access CHannel | +| PUCCH | Physical Uplink Control CHannel | +| PUSCH | Physical Uplink Shared CHannel | +| QoS | Quality of Service | +| RB | Resource block | +| RIT | Radio Interface Technology | +| RRM | Radio Resource Management | +| SCS | SubCarrier Spacing | +| SIB1 | System Information Block Type 1 | +| SINR | Signal to Interference and Noise Ratio | +| SRIT | Set of Radio Interface Technologies | +| SS | Synchronization Signal | +| SSB | SS/PBCH Block | +| TRxP | Transmission Reception Point | +| UL | Uplink | + +# 4 Self-evaluation of eMBB-s technical performance + +## 4.1 Peak spectral efficiency + +As defined in R MReport ITU-R M.2514 [2], peak spectral efficiency is the maximum data rate under ideal conditions normalized by the assigned bandwidth (in bit/s/Hz), where the maximum data rate is the received data bits assignable to a single mobile station, when up to all assignable radio resources for the corresponding link direction are utilized (i.e. excluding radio resources that are used for physical layer synchronization, reference signals or pilots and guard bands). + +When only one component carrier is in use, the generic formula for peak spectral efficiency is given by: + +$$SE_p = \frac{v_{Layers} \cdot Q_m \cdot f \cdot R_{max} \cdot \frac{N_{PRB}^{BW,\mu} \cdot 12}{T_s^\mu} \cdot (1-OH)}{BW} \quad (4.1-1)$$ + +wherein + +- $R_{max}$ is the maximum code rate +- $v_{Layers}$ is the maximum number of layers +- $Q_m$ is the maximum modulation order +- $f$ is the scaling factor can at least take the values 1 and 0.75 +- $\mu$ is the numerology (as defined in TS 38.211 [3]) +- $T_s^\mu$ is the average OFDM symbol duration in a subframe for numerology $\mu$ , i.e $T_s^\mu = \frac{10^{-3}}{14 \cdot 2^\mu}$ , assuming normal cyclic prefix +- $N_{PRB}^{BW,\mu}$ is the maximum RB allocation in bandwidth with numerology $\mu$ and $BW$ is the UE supported maximum bandwidth in a given band. +- $OH$ is the overhead calculated as the average ratio of the number of REs occupied by L1/L2 control, Synchronization Signal, PBCH, reference signals, etc. with respect to the total number of REs in the effective bandwidth time product as given by $(BW \cdot 14 \cdot T_s^\mu)$ . + +The peak spectral efficiency of NR satellite access is evaluated based on an analytical method. Unlike a terrestrial system, where conditions close to ideal be achieved, for an NTN system the minimum orbit height will result in a signal-to-noise ratio where the theoretical maximum is not achievable. The evaluation assumptions for the ideal conditions can be found in Annex A.1. + +The evaluation results for Peak spectral efficiency for DL and UL can be found in Table 4.1-1. + +**Table 4.1-1: NR satellite access peak spectral efficiency (bit/s/Hz)** + +| Link | SCS [kHz] | BW [MHz/RB] | Peak spect. eff. (bits/s/Hz) | Req. | +|------|-----------|-------------|------------------------------|------| +| DL | 15 | 30 / 160 | 3.71 | 3 | +| UL | 15 | 1.44 / 8 | 1.85 | 1.5 | + +Based on the above analysis, NR satellite access fulfils peak spectral efficiency requirement for both DL and UL. + +## 4.2 Peak data rate + +Peak data rate for NR NTN is evaluated based on the evaluation results of NR satellite access peak spectral efficiency provided in Section 4.1.1. Using the analytical way as provided in Report ITU-R M.2514 [2] DL peak data rate is calculated as: + +$$R_p = W_a \times SE_p \quad (4.2-1)$$ + +The evaluation results for Peak spectral efficiency for DL and UL can be found in Table 4.2-1. + +**Table 4.2-1: NR satellite access Peak data rate (Mbit/s)** + +| Link | SCS [kHz] | BW [MHz/RB] | Peak data rate (Mbit/s) | Req. | +|------|-----------|-------------|-------------------------|------| +| DL | 15 | 30 / 160 | 111 | 70 | +| UL | 15 | 1.44 / 8 | 2.67 | 2 | + +Based on the above analysis, NR satellite access fulfils peak data rate requirements for both DL and UL. + +## 4.3 5th percentile user spectral efficiency + +As defined in Rep ITU-R M.2514 [2], the 5th percentile user spectral efficiency is the 5% point of the CDF of the normalized user throughput. The normalized user throughput is defined as the number of correctly received bits, i.e. the number of bits contained in the SDUs delivered to Layer 3, over a certain period of time, divided by the channel bandwidth and is measured in bit/s/Hz. + +As required by Report Rep ITU-R M.2514 [2], 5th percentile user spectral efficiency shall be assessed jointly with average spectral efficiency using the same simulation. Therefore, the evaluation results of the 5th percentile user spectral efficiency are provided together with average spectral efficiency in Section 4.4. + +## 4.4 Average spectral efficiency + +As defined in Report ITU-R M.2514 [2], average spectral efficiency is the aggregate throughput of all users (the number of correctly received bits, i.e. the number of bits contained in the SDUs delivered to Layer 3, over a certain period of time) divided by the channel bandwidth of a specific band divided by the number of TRxPs and is measured in bit/s/Hz/TRxP. A TRxP (transmission and reception point) refers to a beam generated by the satellite. The channel bandwidth for this purpose is defined as the effective bandwidth times the frequency reuse factor. + +As required by Report ITU-R M.2514 [2], average spectral efficiency and 5th percentile user spectral efficiency are assessed jointly using the same simulation. + +Average spectral efficiency and 5th percentile user spectral efficiency are evaluated for NR satellite access with satellite orbit at 600km with a transparent payload operating in S-Band. Both configurations with frequency reuse factor equals to 1 and frequency reuse factor equals to 3 are evaluated. Detailed evaluation assumptions and results can be found in Annex A.2. + +The antenna configuration is indicated as $(M, N, P, M_g, N_g; M_p, N_p)$ , where $M$ and $N$ are the number of vertical, horizontal antenna elements within a panel, $P$ is number of polarizations, $M_g$ is the number of panels in a column, $N_g$ is the number of panels in row; and $M_p$ and $N_p$ are the number of vertical, horizontal TXRUs within a panel and polarization. + +The evaluation results of DL spectral efficiency for NR satellite access are provided in Table 4.4-1. + +It is observed that NR satellite access can fulfil downlink spectral efficiency requirement. + +**Table 4.4-1: Evaluation results of DL spectral efficiency for NR satellite access** + +| Scintillation loss | Number of UE antennas | Frequency reuse factor | ITU Requirement | | DL Spectral efficiency | Number of samples | +|--------------------|-----------------------|------------------------|---------------------------|-------|------------------------|-------------------| +| | | | | | | | +| 2.2 dB | 2 | FRF = 1 | Average [bit/s/Hz/TRxP] | 0.500 | 0.572 | 9 | +| | | | 5th percentile [bit/s/Hz] | 0.030 | 0.031 | 9 | +| | | FRF = 3 | Average [bit/s/Hz/TRxP] | 0.500 | 0.537 | 9 | +| | | | 5th percentile [bit/s/Hz] | 0.030 | 0.038 | 9 | +| | 4 | FRF = 1 | Average [bit/s/Hz/TRxP] | 0.500 | 0.746 | 2 | +| | | | 5th percentile [bit/s/Hz] | 0.030 | 0.036 | 2 | +| | | FRF = 3 | Average [bit/s/Hz/TRxP] | 0.500 | 0.608 | 4 | +| | | | 5th percentile [bit/s/Hz] | 0.030 | 0.040 | 4 | +| 0 dB | 2 | FRF = 1 | Average [bit/s/Hz/TRxP] | 0.500 | 0.589 | 6 | +| | | | 5th percentile [bit/s/Hz] | 0.030 | 0.029 | 6 | +| | | FRF = 3 | Average [bit/s/Hz/TRxP] | 0.500 | 0.562 | 6 | +| | | | 5th percentile [bit/s/Hz] | 0.030 | 0.038 | 6 | +| | 4 | FRF = 1 | Average [bit/s/Hz/TRxP] | 0.500 | 0.783 | 3 | +| | | | 5th percentile [bit/s/Hz] | 0.030 | 0.041 | 3 | +| | | FRF = 3 | Average [bit/s/Hz/TRxP] | 0.500 | 0.659 | 3 | +| | | | 5th percentile [bit/s/Hz] | 0.030 | 0.047 | 3 | + +The evaluation results of UL spectral efficiency for NR satellite access are provided in Table 4.4-2. + +It is observed that NR satellite access can fulfil uplink spectral efficiency requirement. + +**Table 4.4-2: Evaluation results of UL spectral efficiency for NR satellite access** + +| Scintillation loss | Number of UE antennas | Frequency reuse factor | ITU Requirement | | UL Spectral efficiency | Number of samples | +|--------------------|-----------------------|------------------------|---------------------------|-------|------------------------|-------------------| +| | | | | | | | +| 2.2 dB | 2 | FRF = 1 | Average [bit/s/Hz/TRxP] | 0.100 | 0.145 | 9 | +| | | | 5th percentile [bit/s/Hz] | 0.003 | 0.006 | 9 | +| | | FRF = 3 | Average [bit/s/Hz/TRxP] | 0.100 | 0.199 | 8 | +| | | | 5th percentile [bit/s/Hz] | 0.003 | 0.010 | 8 | +| 0 dB | 2 | FRF = 1 | Average [bit/s/Hz/TRxP] | 0.100 | 0.233 | 4 | +| | | | 5th percentile [bit/s/Hz] | 0.003 | 0.006 | 4 | +| | | FRF = 3 | Average [bit/s/Hz/TRxP] | 0.100 | 0.230 | 5 | +| | | | 5th percentile [bit/s/Hz] | 0.003 | 0.009 | 5 | + +## 4.5 User experienced data rate + +As defined in Report ITU-R M.2514 [2], user experienced data rate is the 5% point of the cumulative distribution function (CDF) of the user throughput. User throughput (during active time) is defined as the number of correctly received bits, i.e. the number of bits contained in the service data units (SDUs) delivered to Layer 3, over a certain period of time. + +User experienced data rate for NR satellite access is evaluated under Rural – eMBB test environment. The user experienced data rate is derived from the 5th percentile user spectral efficiency through equation as defined in Report ITU-R M.2514 [2]. Detailed evaluation assumptions are based on spectral efficiency evaluation and can be found in Annex A.2. + +The evaluation results of DL user experienced data rate for NR satellite access are provided in Table 4.5-1. + +It is observed that NR satellite access can fulfil DL user experienced data rate requirement. + +**Table 4.5-1: Evaluation results of DL user experienced data rate for NR satellite access** + +| Scintillation loss | Number of UE antennas | Frequency reuse factor | ITU Requirement (Mbit/s) | DL user experienced data rate (Mbit/s) | Number of samples | +|--------------------|-----------------------|------------------------|--------------------------|----------------------------------------|-------------------| +| 2.2 dB | 2 | FRF = 1 | 1 | 0.91 | 9 | +| | | FRF = 3 | 1 | 1.12 | 9 | +| | 4 | FRF = 1 | 1 | 1.07 | 2 | +| | | FRF = 3 | 1 | 1.21 | 4 | +| 0 dB | 2 | FRF = 1 | 1 | 0.85 | 6 | +| | | FRF = 3 | 1 | 1.12 | 6 | +| | 4 | FRF = 1 | 1 | 1.24 | 3 | +| | | FRF = 3 | 1 | 1.43 | 3 | + +The evaluation results of UL user experienced data rate for NR satellite access are provided in Table 4.5-2. + +It is observed that NR satellite access can fulfil UL user experienced data rate requirement. + +**Table 4.5-2: Evaluation results of UL user experienced data rate for NR satellite access** + +| Scintillation loss | Number of UE antennas | Frequency reuse factor | ITU Requirement (Mbit/s) | UL user experienced data rate (Mbit/s) | Number of samples | +|--------------------|-----------------------|------------------------|--------------------------|----------------------------------------|-------------------| +| 2.2 dB | 2 | FRF = 1 | 0.1 | 0.15 | 9 | +| | | FRF = 3 | 0.1 | 0.28 | 8 | +| 0 dB | 2 | FRF = 1 | 0.1 | 0.13 | 4 | +| | | FRF = 3 | 0.1 | 0.26 | 5 | + +## 4.6 Area traffic capacity + +As defined in Report ITU-R M.2514 [2], area traffic capacity is the total traffic throughput served per geographic area (in Mbit/s/m2). The throughput is the number of correctly received bits, i.e. the number of bits contained in the SDUs delivered to Layer 3, over a certain period of time. + +For NR satellite access, Area traffic capacity is evaluated under the Rural-eMBB-s test environment using analytical way based on the downlink average spectral efficiency as defined in in Report ITU-R M.2514 [2]. Detailed evaluation assumptions are based on spectral efficiency evaluation and can be found in Annex A.2. + +The evaluation results of DL area traffic capacity NR satellite access a with 19 TRxP are provided in Table 4.6-1. + +It is observed that NR satellite access can fulfil DL area traffic capacity requirement. + +**Table 4.6-1 Evaluation results of DL area traffic capacity for NR satellite access** + +| Scintillation loss | Number of UE antennas | Frequency reuse factor | ITU Requirement (kbit/s/km 2 ) | DL area traffic capacity (kbit/s/km 2 ) | Number of samples | +|--------------------|-----------------------|------------------------|-------------------------------------------|----------------------------------------------------|-------------------| +| 2.2 dB | 2 | FRF = 1 | 8 | 12.07 | 9 | +| | | FRF = 3 | 8 | 11.30 | 9 | +| | 4 | FRF = 1 | 8 | 15.81 | 2 | +| | | FRF = 3 | 8 | 12.81 | 4 | +| 0 dB | 2 | FRF = 1 | 8 | 12.41 | 6 | +| | | FRF = 3 | 8 | 11.85 | 6 | +| | 4 | FRF = 1 | 8 | 16.60 | 3 | +| | | FRF = 3 | 8 | 13.97 | 3 | + +The evaluation results of UL area traffic capacity NR satellite access a with 19 TRxP are provided in Table 4.6-2. + +It is observed that NR satellite access can fulfil UL area traffic capacity requirement. + +**Table 4.6-2 Evaluation results of UL area traffic capacity for NR satellite access** + +| Scintillation loss | Number of UE antennas | Frequency reuse factor | ITU Requirement (kbit/s/km 2 ) | UL area traffic capacity (kbit/s/km 2 ) | Number of samples | +|--------------------|-----------------------|------------------------|-------------------------------------------|----------------------------------------------------|-------------------| +| 2.2 dB | 2 | FRF = 1 | 1.5 | 3.06 | 9 | +| | | FRF = 3 | 1.5 | 4.19 | 8 | +| 0 dB | 2 | FRF = 1 | 1.5 | 4.87 | 4 | +| | | FRF = 3 | 1.5 | 4.84 | 5 | + +## 4.7 Latency + +### 4.7.1 General + +As defined in Report ITU-R M.2514 [2], user plane latency is the contribution of the radio network to the time from when the source sends a packet to when the destination receives it (in ms). It is defined as the one-way time it takes to successfully deliver an application layer packet/message from the radio protocol layer 2/3 SDU ingress point to the radio protocol layer 2/3 SDU egress point of the radio interface in either uplink or downlink in the network for a given service in unloaded conditions, assuming the mobile station is in the active state. + +### 4.7.2 User plane latency + +#### 4.7.2.1 General + +The evaluation of NR satellite access user plane latency is based on the procedure illustrated in Figure 4.7.2.1-1. + +![Figure 4.7.2.1-1: User plane procedure for evaluation. The diagram shows the flow of data between a Base Station (BS) and a User Equipment (UE) for both Downlink (DL) and Uplink (UL). In the DL, data flows from BS to UE, with components t_BS,tx + t_FA,DL at the BS, t_DL_duration + t_prop in the air, and t_UE,rx at the UE. In the UL, data flows from UE to BS, with components t_UE,tx + t_FA,UL at the UE, t_UL_duration + t_prop in the air, and t_BS,rx at the BS. The BS and UE are represented by large grey rectangles, and the air interface is represented by dashed blue arrows labeled DL and UL.](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg) + +Figure 4.7.2.1-1: User plane procedure for evaluation. The diagram shows the flow of data between a Base Station (BS) and a User Equipment (UE) for both Downlink (DL) and Uplink (UL). In the DL, data flows from BS to UE, with components t\_BS,tx + t\_FA,DL at the BS, t\_DL\_duration + t\_prop in the air, and t\_UE,rx at the UE. In the UL, data flows from UE to BS, with components t\_UE,tx + t\_FA,UL at the UE, t\_UL\_duration + t\_prop in the air, and t\_BS,rx at the BS. The BS and UE are represented by large grey rectangles, and the air interface is represented by dashed blue arrows labeled DL and UL. + +**Figure 4.7.2.1-1 User plane procedure for evaluation** + +The detailed assumptions of each step are provided in Table 4.7.2.2-1 and Table 4.7.2.3-1 for downlink and uplink, respectively. + +The additional assumptions to derive the evaluation results of NR satellite access user plane latency are list as below. + +- It is assumed that the packet arrives at any time of any OFDM symbol. In this case, the 0.5 symbol length is added as the “average symbol alignment time” at the beginning of the procedure. +- The transmission of PDCCH, PDSCH, PUCCH, PUSCH cannot be across the slot. Otherwise, the transmission will wait for the next slot. +- The PDSCH/PUSCH allocation (transmission duration) of 2/4/7/14-OFDM symbols non-slot or slot are evaluated. + - If the evaluation is for 14 OFDM Symbol length slot, then slot-based scheduling is used. + - Otherwise, non-slot-based scheduling is used. + +- The resource mapping type A and B are considered, which impact the start timing of a transmission. Details on resource mapping mechanism can be found in TS 38.214 [8]. +- It is assumed that PDCCH monitoring occasion occurs at every OFDM symbol in the evaluation. +- It is assumed that HARQ feedback is disabled, i.e., packet retransmissions are not considered. +- It is assumed an initial error probability of 0. +- It is assumed that satellite on-board delay can be considered negligible. + +#### 4.7.2.2 Downlink + +The downlink procedure is abstracted in Table 4.7.2.2-1, where the assumptions of each step for evaluation are given. + +**Table 4.7.2.2-1: DL user plane procedure for of NR satellite access** + +| ID | Component | Notations | Value | +|----|------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| 1 | BS processing delay | $t_{BS,tx}$
The time interval between data arrival and packet generation. | $T_{proc,2}/2$ , with $d_{2,1} = d_{2,2} = 0$ .
$T_{proc,2}$ is defined in Section 6.4 of TS 38.214 [8]. | +| 2 | DL frame alignment (transmission alignment) | $t_{FA,DL}$
The time interval between packet generation and the next Tx opportunity. | $T_{FA}$
Length of one slot, since $T_{FA}$ is bounded by the slot duration. | +| 3 | TTI for DL data packet transmission | $t_{DL\_duration}$ | Length of one slot (14 OFDM symbol length) or non-slot (4/7 OFDM symbol length), depending on slot or non-slot selected in evaluation. | +| 4 | One-way propagation time BS -> satellite -> UE | $t_{prop}$ | $RTD/2$ | +| 5 | UE processing delay | $t_{UE,rx}$
The time interval between PDSCH reception and decoding of the data. | $T_{proc,1}/2$ , with $d_{1,1} = 0$ .
$T_{proc,1}$ is defined in Section 5.3 of TS 38.214 [8]. | +| | Total one-way user plane latency for DL | $T_{DL} = (t_{BS,tx} + t_{FA,DL}) + (t_{DL\_duration} + t_{prop}) + t_{UE,rx}$ | | + +Note: +1. The value is used for evaluation only; gNB processing delay may vary depending on implementation + +Based on the DL user plane procedure and assumptions given in Table 4.7.2.2-1, a variety of configurations and UE capabilities are evaluated for NR satellite access in Table 4.7.2.2-2. + +**Table 4.7.2.2-2: DL user plane latency for NR satellite access (ms)** + +| DL user plane latency | | UE processing capability 1 | | UE processing capability 2 | | +|-------------------------|----------------------|----------------------------|--------|----------------------------|--------| +| | | SCS | | SCS | | +| | | 15 kHz | 30 kHz | 15 kHz | 30 kHz | +| Resource mapping Type A | M = 4 (4OS non-slot) | 6.21 | 5.21 | 5.67 | 4.90 | +| | M = 7 (7OS non-slot) | 6.43 | 5.32 | 5.89 | 5.01 | +| | M = 14 (14OS slot) | 6.93 | 5.57 | 6.39 | 5.26 | +| Resource mapping Type B | M = 2 (20S non-slot) | 5.78 | 5.00 | 5.25 | 4.69 | +| | M = 4 (40S non-slot) | 5.71 | 4.96 | 5.18 | 4.65 | +| | M = 7 (70S non-slot) | 5.93 | 5.07 | 5.39 | 4.76 | + +It is observed that NR fulfils DL user plane latency requirement in a wide range of configurations. + +In addition, it is indicated that NR satellite access has designed user plane downlink timers to support larger latencies, e.g., up to 650 ms, for the operation in other relevant satellite orbits (e.g., GSO). + +#### 4.7.2.3 Uplink + +The uplink procedure using a grant free transmission is abstracted in Table 4.7.2.3-1, where the assumptions of each step for evaluation are given. + +**Table 4.7.2.3-1: UL user plane procedure for NR satellite access** + +| ID | Component | Notations | Value | +|-----|---------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| 1.1 | UE processing delay | $t_{UE,tx}$
The time interval between data arrival and packet generation. | $T_{proc,2}/2$ , with $d_{2,1} = d_{2,2} = 0$ .
$T_{proc,2}$ is defined in Section 6.4 of TS 38.214 [8]. | +| 1.2 | UL frame alignment (transmission alignment) | $t_{FA,UL}$
The time interval between packet generation and the next Tx opportunity. | $T_{FA}$
Length of one slot, since $T_{FA}$ is bounded by the slot duration. | +| 1.3 | TTI for UL data packet transmission | $t_{UL\_duration}$ | Length of one slot (14 OFDM symbol length) or non-slot (4/7 OFDM symbol length), depending on slot or non-slot selected in evaluation. | +| 1.4 | One-way propagation time
UE -> satellite -> BS | $t_{prop}$ | $RTD/2$ | +| 1.5 | BS processing delay | $t_{BS,rx}$
The time interval between PUSCH reception and decoding of the data. | $T_{proc,1}/2$ , with $d_{1,1} = 0$ .
$T_{proc,1}$ is defined in Section 5.3 of TS 38.214 [8]. | +| | Total UP latency for UL | $T_{UL} = (t_{UE,tx} + t_{FA,UL}) + (t_{UL\_duration} + t_{prop}) + t_{BS,rx}$ | | + +Note: + +1. The value is used for evaluation only; gNB processing delay may vary depending on implementation. + +Based on the UL user plane procedure and assumptions given in Table 4.7.2.3-1, a variety of configurations and UE capabilities are evaluated for NR satellite access in Table 4.7.2.3-2. + +**Table 4.7.2.3-2: UL user plane latency for NR satellite access with grant free transmission (ms)** + +| UL user plane latency | | UE processing capability 1 | | UE processing capability 2 | | +|-------------------------|----------------------|----------------------------|--------|----------------------------|--------| +| | | SCS | | SCS | | +| | | 15 kHz | 30 kHz | 15 kHz | 30 kHz | +| Resource mapping Type A | M = 4 (4OS non-slot) | 6.21 | 5.21 | 5.67 | 4.90 | +| | M = 7 (7OS non-slot) | 6.43 | 5.32 | 5.89 | 5.01 | +| | M = 14 (14OS slot) | 6.93 | 5.57 | 6.39 | 5.26 | +| Resource mapping Type B | M = 2 (2OS non-slot) | 5.78 | 5.00 | 5.25 | 4.69 | +| | M = 4 (4OS non-slot) | 5.71 | 4.96 | 5.18 | 4.65 | +| | M = 7 (7OS non-slot) | 5.93 | 5.07 | 5.39 | 4.76 | +| | M = 14 (14OS slot) | 6.93 | 5.57 | 6.39 | 5.26 | + +It is observed that NR satellite access fulfils UL user plane latency requirement in a wide range of configurations. + +In addition, it is indicated that NR satellite access has designed user plane uplink timers to support larger latencies, e.g., up to 650 ms, for the operation in other relevant satellite orbits (e.g., GSO). + +### 4.7.3 Control plane latency + +As defined in Report ITU-R M.2514 [2], control plane latency refers to the transition time from a most “battery efficient” state (e.g., Idle state) to the start of continuous data transfer (e.g., Active state). + +For NR satellite access, control plane latency is evaluated from RRC\_INACTIVE state to RRC\_CONNECTED state. Figure 4.7.3-1 provides an example control plane flow for NR satellite access. + +![Sequence diagram of C-plane procedure for NR satellite access between UE and BS.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates the C-plane procedure between a User Equipment (UE) and a Base Station (BS). The sequence of events is as follows: + +- 1. Delay for RACH scheduling period and processing delay in UE**: A delay period at the UE before sending the initial message. +- 2. MsgA (Preamble + PUSCH)**: The UE sends MsgA to the BS. +- 3. Processing delay in BS**: The BS processes the received MsgA. +- 4. MsgB (RA Response)**: The BS sends MsgB back to the UE. +- 5. Processing delay in UE**: The UE processes the received MsgB. +- 6. RRC Resume Complete**: The UE sends the final RRC Resume Complete message to the BS. + +The entire sequence from step 2 to step 5 is labeled as the **CP procedure** on the right side of the diagram. Vertical dashed lines separate the delay periods at the UE (steps 1 and 5) from the message exchanges. + +Sequence diagram of C-plane procedure for NR satellite access between UE and BS. + +**Figure 4.7.3-1: C-plane procedure (example for NR satellite access)** + +The detailed assumption of each step as shown in Figure 4.7.3-1 is provided in Table 4.7.3-1. The evaluation is for UL data transfer. It is understood that the evaluation results for DL data transfer can be further reduced because UE processing delay in Step 6 for DL data transfer does not need to handle UL grant receiving, and therefore can be reduced compared to the case of UL data transfer. + +NOTE: The delay values shown below do not include the waiting time for DL/UL subframe. It is only gNB or UE processing delay. The waiting time will be calculated, and it depends on the detailed DL/UL configuration. + +**Table 4.7.3-1: Assumption of C-plane procedure for NR satellite access** + +| Step | Description | CP latency for UL data transfer | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| 1.1 | Delay due to RACH scheduling period (1TTI) | 0 | +| 1.2 | UE Processing Delay (L1 encoding of RRC Resume Request) for MsgA | $T_{proc,2}/2$ (assuming $d_2 = d_{2,1} = d_{2,2} = 0$ ) | +| 2.1.1 | Transmission of RACH preamble | Length of the preamble according to the PRACH format as specified in TS 38.211 [3] | +| 2.1.2 | Transmission interval | Length of the interval between PRACH and PUSCH transmissions as specified in TS 38.213 [7] | +| 2.1.3 | Transmission of PUSCH payload (RRCResumeRequest) | $T_s$ (the length of 1 slot / non-slot) | +| 2.2 | Propagation delay UE -> BS | $RTD/2$ | +| 3 | MsgA detection and processing delay in gNB (preamble, L2 and RRC) | 3 ms | +| 4.1 | Transmission of MsgB (RA response) | $T_s$ (the length of 1 slot / non-slot) | +| 4.2 | Propagation delay BS -> UE | $RTD/2$ | +| 5 | Processing delay in UE of RRC Resume including RA response | 7 ms | +| 6 | Transmission of RRC Resume Complete and data | 0 | +| NOTE 1: For step 1.1, the procedure for transition from a most "battery efficient" state has yet not begun, hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above. | | | +| NOTE 2: For step 3, the processing delay in gNB (L2 and RRC) has been reduced to 3 ms. The delays due to inside-gNB or inter-gNB communication are not included in Step 3. Such delays may exist depending on deployment but are not within the scope of this evaluation. | | | +| NOTE 3: For step 5 for UL data transfer, the processing delay in the UE (L2 and RRC) is considered, i.e., from reception of RRC Connection Resume including the RA response to the reception of UL grant. The transmission of UL grant by gNB and processing delay in the UE (processing of UL grant and preparing for UL tx) are also considered. The RRCConnectionResume message only includes MAC and PHY configuration. No DRX, SPS, or MIMO re-configuration will be triggered by this message. Further, the UL grant for transmission of RRC Connection Resume Complete and the data is transmitted over common search space with DCI format 0. | | | +| NOTE 4: For step 6, the beginning of this subframe is considered to be " the start of continuous data transfer ", hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above. | | | + +In addition, the following assumptions apply to the evaluation: + +- The transmission duration of Step 2 and 4 cannot be crossing the boundary of a slot; +- The CP procedure can start from the OFDM symbols within the slot that PRACH preamble can be transmitted (assuming that the slot is UL slot; otherwise, it will wait for the available UL slot). +- It is assumed that satellite on-board delay can be considered negligible. + +Based on the control plane procedure and assumptions given in Table 4.7.3-1, a variety of configurations and UE capabilities are evaluated for NR for UL data transfer in Tables 4.7.3-2, 4.7.3-3 and 4.7.3-4. + +**Table 4.7.3-2: Control plane latency for NR satellite access (ms), PRACH length = 2 OFDM symbols** + +| Resource mapping type | Non-slot duration | UE capability 1 | | UE capability 2 | | +|-----------------------|-------------------------|-----------------|-----------|-----------------|-----------| +| | | 15kHz SCS | 30kHz SCS | 15kHz SCS | 30kHz SCS | +| Type A | $M=4$
(4OS non-slot) | 21.1 | 19.6 | 20.9 | 19.5 | +| | $M=7$
(7OS non-slot) | 21.5 | 19.8 | 21.3 | 19.7 | +| Type B | $M=2$
(2OS non-slot) | 20.5 | 19.3 | 20.3 | 19.2 | +| | $M=4$
(4OS non-slot) | 20.6 | 19.3 | 20.4 | 19.2 | +| | $M=7$
(7OS non-slot) | 21.0 | 19.5 | 20.8 | 19.4 | + +**Table 4.7.3-3: Control plane latency for NR satellite access (ms), PRACH length = 6 OFDM symbols** + +| Resource mapping type | Non-slot duration | UE capability 1 | | UE capability 2 | | +|-----------------------|-------------------------|-----------------|-----------|-----------------|-----------| +| | | 15kHz SCS | 30kHz SCS | 15kHz SCS | 30kHz SCS | +| Type A | $M=4$
(4OS non-slot) | 21.4 | 19.7 | 21.2 | 19.6 | +| | $M=7$
(7OS non-slot) | 21.8 | 19.9 | 21.6 | 19.8 | +| Type B | $M=2$
(2OS non-slot) | 20.8 | 19.4 | 20.6 | 19.3 | +| | $M=4$
(4OS non-slot) | 20.9 | 19.5 | 20.7 | 19.3 | +| | $M=7$
(7OS non-slot) | 21.3 | 19.7 | 21.1 | 19.6 | + +**Table 4.7.3-4 Control plane latency for NR satellite access (ms), PRACH length = 1 ms** + +| Resource mapping type | Non-slot duration | UE capability 1 | | UE capability 2 | | +|-----------------------|-------------------------|-----------------|-----------|-----------------|-----------| +| | | 15kHz SCS | 30kHz SCS | 15kHz SCS | 30kHz SCS | +| Type A | $M=4$
(4OS non-slot) | 21.9 | 20.5 | 21.8 | 20.4 | +| | $M=7$
(7OS non-slot) | 22.4 | 20.7 | 22.2 | 20.6 | +| | $M=14$
(14OS slot) | 23.4 | 21.2 | 23.2 | 21.1 | +| Type B | $M=2$
(2OS non-slot) | 21.4 | 20.2 | 21.2 | 20.1 | +| | $M=4$
(4OS non-slot) | 21.4 | 20.2 | 21.2 | 20.1 | +| | $M=7$
(7OS non-slot) | 21.9 | 20.5 | 21.7 | 20.3 | + +It is observed that NR satellite access fulfils the control plane latency requirement of 40 ms in a wide range of configurations. + +In addition, it is indicated that NR satellite access has extended the range of a series of control plane session management timers to support larger latencies, e.g., up to 1.15 s, for the operation in other relevant satellite orbits (e.g., GSO). + +## 4.8 Energy efficiency + +### 4.8.1 General + +As defined in Report ITU-R M.2514 [2], Network energy efficiency is the capability of a RIT/SRIT to minimize the radio access network energy consumption in relation to the traffic capacity provided. Device energy efficiency is the capability of the RIT/SRIT to minimize the power consumed by the device modem in relation to the traffic characteristics. + +The RIT/SRIT shall have the capability to support a high sleep ratio and long sleep duration. + +The sleep ratio is the fraction of unoccupied time resources (for the network) or sleeping time (for the device) in a period of time corresponding to the cycle of the control signalling (for the network) or the cycle of discontinuous reception (for the device) when no user data transfer takes place. The sleep duration is the continuous period of time with no transmission (for network and device) and reception (for the device). + +### 4.8.2 Network side + +#### 4.8.2.1 General + +The sleep ratio and sleep duration for NR satellite access network under unloaded case are evaluated. + +When no data transfer takes place, NR satellite access network will keep periodical transmission of SS/PBCH blocks and SIB1 (remaining minimum system information), as well as paging signal in order for UEs to detect and access the radio network. The following mechanisms for SS/PBCH block, SIB1 and paging are assumed for the evaluation. + +For SS/PBCH block transmission, the following configurations are considered in evaluation in FR1. + +- One SS/PBCH block occupies 4 OFDM symbols with 20 RBs in one slot. +- One or multiple SS/PBCH block(s) compose an "SS burst set" (SSB set). + - Denote $L$ as the number of SS/PBCH blocks in an SSB set, where $L$ can be 1~ 64. For below 3 GHz, the maximum value of $L$ is 4; for below 7.125 GHz, the maximum value of $L$ is 8. +- One SSB set transmission is confined to a half radio frame (5 ms) window +- The SSB set periodicity ( $P_{\text{SSB}}$ ) can be configured to be {5, 10, 20, 40, 80, 160} ms +- The following mapping is used in a half radio frame for 15 and 30 kHz SCS + - 2 SS/PBCH blocks are transmitted in one slot. And the $L$ SS/PBCH blocks in an SSB set is transmitted in successive slots from the first slot in one SSB set period. + +For SIB1 transmission, the following configurations are considered in evaluation. + +- One SIB1 transmission occupies 2 OFDM symbols in one slot. +- SIB1 is multiplexed with SS/PBCH block using the following ways: + - SIB1 is time division multiplexed (TDMed) with SS/PBCH block. + - SS/PBCH block and SIB1 could be transmitted in the same slot +- SIB1 periodicity ( $P_{\text{SIB1}}$ ) is assumed as follows: + - 20ms for SSB set periodicity less than or equal to 20ms; + - Otherwise SIB1 periodicity equals to SSB set periodicity. +- The following mapping is used + - One SIB1 transmission corresponds to one SS/PBCH block + - If $L$ SS/PBCH block is transmitted, then $L$ SIB1 transmissions are required. + +- One slot accommodates 2 SIB1 transmissions. +- The offset of SIB1 transmission can be set as {0, 2, 5, 7}ms with respect to every 20ms time point. In the evaluation, the offset value that allows the closest SIB1 transmission to SS/PBCH block transmission is selected. + +For paging occasion, + +- The periodicity of paging occasion is the same as that of SSB set, and it is FDMed with an SS block. + +Figure 4.8.2.1-1 illustrates NR SS/PBCH block and SIB1 transmission which employs the above-mentioned mechanism. + +![Diagram illustrating NR SS/PBCH block and SIB1 transmission. It shows a timeline with 'Half frame (5ms)' segments. The first half frame contains two SS blocks and two SIB1 transmissions. The second half frame contains two SS blocks and two SIB1 transmissions. The 'SSB set periodicity' is indicated by a dashed line spanning the two half frames.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +Diagram illustrating NR SS/PBCH block and SIB1 transmission. It shows a timeline with 'Half frame (5ms)' segments. The first half frame contains two SS blocks and two SIB1 transmissions. The second half frame contains two SS blocks and two SIB1 transmissions. The 'SSB set periodicity' is indicated by a dashed line spanning the two half frames. + +Figure 4.8.2.1-1 Illustration of NR SS/PBCH block and SIB1 transmission. + +#### 4.8.2.2 Evaluation of sleep ratio + +Based on the above mechanisms, the sleep ratio per slot basis and per symbol basis are given as follows, + +$$Sleep\_ratio_{Slot\_based} = 1 - \frac{\lceil L/2 \rceil}{2^\mu \times P_{SSB}} \quad (4.8.2.2-1)$$ + +$$Sleep\_ratio_{Symbol\_based} = 1 - \frac{\frac{L \times 2}{7}}{2^\mu \times P_{SSB}} - \alpha \cdot \frac{\frac{L}{7}}{2^\mu \times P_{SIB1}} \quad (4.8.2.2-2)$$ + +where $\lceil x \rceil$ indicates the ceiling of $x$ , $\mu$ is the numerology (as defined in TS 38.211 [3], e.g., $\mu=0$ for 15 kHz SCS and $\mu=1$ for 30 kHz SCS), $L$ is the number of SS/PBCH blocks in one SSB set, $P_{SSB}$ is the SSB set periodicity, $P_{SIB1}$ is the RSMI periodicity, and $\alpha = 1$ . + +Evaluation results are shown in Table 4.8.2.2-1 and Table 4.8.2.2-2, respectively, for slot level and symbol level sleep ratio. It is observed that with SSB set period of 5ms, more than 80% of sleep ratio can be obtained by NR satellite access network; with SSB set period of larger than 10ms, more than 90% of sleep ratio can be obtained by NR satellite access network. Higher sleep ratio is expected with finer sleep granularity, e.g., in symbol level. Note that a subset of configurations in terms of number of SSB per set is used to derive the results. + +Therefore, NR network can achieve high sleep ratio in unloaded case. + +Table 4.8.2.2-1 NR satellite access network sleep ratio in slot level + +| SSB configuration | | SSB set periodicity $P_{SSB}$ | | | | | | +|-------------------|------------------------------------------|-------------------------------|--------|--------|--------|--------|--------| +| SCS [kHz] | Number of SS/PBCH block per SSB set, $L$ | 5ms | 10ms | 20ms | 40ms | 80ms | 160ms | +| 15kHz | 1 | 80.00% | 90.00% | 95.00% | 97.50% | 98.75% | 99.38% | +| | 2 | 80.00% | 90.00% | 95.00% | 97.50% | 98.75% | 99.38% | +| 30kHz | 1 | 95.00% | 97.50% | 98.75% | 99.38% | 99.69% | 99.84% | +| | 4 | 80.00% | 90.00% | 95.00% | 97.50% | 98.75% | 99.38% | + +**Table 4.8.2.2-2 NR satellite access network sleep ratio in symbol level** + +| SSB configuration | | SSB set periodicity $P_{\text{SSB}}$ | | | | | | +|-------------------|------------------------------------------|--------------------------------------|--------|--------|--------|--------|--------| +| SCS [kHz] | Number of SS/PBCH block per SSB set, $L$ | 5ms | 10ms | 20ms | 40ms | 80ms | 160ms | +| 15kHz | 1 | 93.57% | 96.43% | 97.86% | 98.93% | 99.46% | 99.73% | +| | 2 | 87.14% | 92.86% | 95.71% | 97.86% | 98.93% | 99.46% | +| 30kHz | 1 | 96.79% | 98.21% | 98.93% | 99.46% | 99.73% | 99.87% | +| | 4 | 87.14% | 92.86% | 95.71% | 97.86% | 98.93% | 99.46% | + +#### 4.8.2.3 Evaluation of sleep duration + +Based on the above mechanisms, evaluation results of sleep duration are provided in Table 4.8.2.2-1. It is observed that with SSB set period of 160 ms, more than 150ms sleep duration can be obtained by NR satellite access network. Therefore, NR network can achieve long sleep duration in unloaded case. + +Therefore, NR meets network side energy efficiency requirement. + +**Table 4.8.2.3-1 NR satellite access network sleep duration (ms) in slot level** + +| SSB configuration | | SSB set periodicity $P_{\text{SSB}}$ | | | | | | +|-------------------|------------------------------------------|--------------------------------------|------|-------|-------|-------|--------| +| SCS [kHz] | Number of SS/PBCH block per SSB set, $L$ | 5ms | 10ms | 20ms | 40ms | 80ms | 160ms | +| 15kHz | 1 | 4.00 | 9.00 | 19.00 | 39.00 | 79.00 | 159.00 | +| | 2 | 4.00 | 9.00 | 19.00 | 39.00 | 79.00 | 159.00 | +| 30kHz | 1 | 4.50 | 9.50 | 19.50 | 39.50 | 79.50 | 159.50 | +| | 4 | 4.00 | 9.00 | 19.00 | 39.00 | 79.00 | 159.00 | + +### 4.8.3 Device side + +#### 4.8.3.1 General + +The sleep ratio and sleep duration for NR satellite access UEs under unloaded case are evaluated. + +For NR, DRX is supported for UEs in idle, inactive and connected states. + +#### 4.8.3.2 Evaluation of sleep ratio + +For idle state and inactive state, the UE should monitor one paging occasion per discontinuous reception (DRX) cycle (which equals to the paging cycle), and the UE can use DRX to reduce power consumption. Before paging receiving, the SSB monitoring is needed. Also, RRM measurement(s), including intra- and inter-cell shall be performed. + +The DRX cycle for idle state / inactive state UE consists of an "On Duration" during which the UE should perform SSB monitoring, paging monitoring and RRM measurement, and an "Off Duration" during which the UE can skip reception of downlink channels to save energy. It is illustrated in Figure 4.8.3.2-1. + +Therefore, the sleep ratio is determined by the length of "On Duration" and the length of one paging cycle. + +![Figure 4.8.3.2-1: Illustration of DRX cycle in connected state. The diagram shows a red rectangular pulse representing the 'On duration' followed by a blue horizontal line representing the 'Off duration'. The 'On duration' is labeled with a double-headed arrow above it. The 'Off duration' is also labeled with a double-headed arrow above it. The 'DRX Cycle' is indicated by a double-headed arrow below the pulse, spanning from the start of the 'On duration' to the start of the next 'On duration'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 4.8.3.2-1: Illustration of DRX cycle in connected state. The diagram shows a red rectangular pulse representing the 'On duration' followed by a blue horizontal line representing the 'Off duration'. The 'On duration' is labeled with a double-headed arrow above it. The 'Off duration' is also labeled with a double-headed arrow above it. The 'DRX Cycle' is indicated by a double-headed arrow below the pulse, spanning from the start of the 'On duration' to the start of the next 'On duration'. + +Figure 4.8.3.2-1 Illustration of DRX cycle in connected state + +When DRX is used, the UE wakes up and receives SSB for synchronization, listens to PDCCH only on specific paging occasion defined in-terms of paging frame and subframe within period of $N_{PC\_RF}$ radio frames defined by the DRX cycle (paging cycle) of the cell and performs RRM measurement. The UE can remain in sleep mode for remaining duration within DRX cycle. + +For synchronization, one SSB-burst set is assumed for short paging cycle (e.g., 320ms). Further, it is assumed that synchronization signal can be located in the same slot as paging-on slot and UE can finish network synchronization before paging monitoring. For longer paging cycle, one SSB-burst can still be assumed. In addition, to improve synchronization accuracy, the case of two SSB-burst sets is also evaluated. In this case, UE needs additional time up to one SSB cycle for SSB reception. + +For paging monitoring, a paging occasion *can consist of multiple time slots (e.g. slot or OFDM symbol)* where paging DCI can be sent. In the evaluation, it is assumed that one paging occasion consists of one slot. On the other hand, one paging cycle consists of one or multiple Paging Frames. One Paging Frame may contain one or multiple paging occasion(s) or starting point of a PO. In the evaluation, it is assumed that one Paging Frame contains one paging occasion and time for paging monitoring is no longer than that of one SSB burst. + +RRM measurement is based on SS/PBCH. In the evaluation, it is assumed that RRM measurement takes place in “On Duration” time, and the RRM measurement time is assumed to be 3ms for FR1 (see TS 38.133 [4]). + +In addition to the above procedure, transition time is needed for UE to switch on / off its components. 10ms transition time is assumed for evaluation; but further reduced value is possible. + +Based on the above analysis, the idle mode sleep ratio is evaluated with the configurations shown in Table 4.8.3.2-1. It is observed that more than 90% sleep ratio is achieved in idle mode by NR device. + +Table 4.8.3.2-1 NR satellite access device sleep ratio in slot level (for idle / inactive mode) + +| | Paging cycle
$N_{PC\_RF} \times 10$
(ms) | SCS(kHz) | SSB L | SSB reception time(ms) | SSB cycle (ms) | Number of SSB burst set | RRM measurement time per DRX (ms) | Transition time(ms) | Sleep ratio | +|--|------------------------------------------------|----------|-------|------------------------|----------------|-------------------------|-----------------------------------|---------------------|-------------| +| | 2560 | 15 | 2 | 1 | -- | 1 | 3 | 10 | 99.5% | +| | 2560 | 15 | 2 | 1 | 160 | 2 | 3 | 10 | 93.2% | + +NOTE: For SSB period, "--" is assumed that SSB reception is during DRX-On time. + +For connected state, if there is no data transmission in either downlink or uplink direction, the DRX mode is switched on. + +The DRX cycle for connected state UE consists of an “On Duration” during which the UE should perform SSB monitoring, PDCCH monitoring (reflected as *DRX-onDurationTimer*), and RRM measurement, and an “Off Duration” during which the UE can skip reception of downlink channels to save energy. Also, transition time is assumed in “On Duration”. The connected mode sleep ratio for different DRX cycles is shown in Table 4.8.3.2-2. Therefore, NR device can achieve high sleep ratio for both idle/inactive state and connected state in unloaded case. + +**Table 4.8.3.2-2 NR satellite access device sleep ratio in slot level (for connected mode)** + +| | DRX cycle
$T_{sc\_ms} * M_{sc}$ (ms) | Number of SSB burst set | DRX-onDurationTimer(ms) | RRM measurement time per DRX (ms) | Transition time(ms) | Sleep ratio | +|---------------|-----------------------------------------|-------------------------|-------------------------|-----------------------------------|---------------------|-------------| +| RRC-Connected | 320 | 1 | 2 | 3.5 | 10 | 95.2% | +| | 320 | 1 | 10 | 3 | 10 | 92.8% | +| | 2560 | 1 | 100 | 3 | 10 | 95.6% | +| | 10240 | 1 | 1600 | 3 | 10 | 84.2% | + +NOTE: For SSB period, "--" is assumed that SSB reception is during DRX-On time. + +#### 4.8.3.3 Evaluation of sleep duration + +The sleep duration for NR satellite access UE in idle mode is 2546ms for paging cycle of 2560ms with the assumed parameters. + +The sleep duration of NR satellite access UE in connected state is 8627ms for paging cycle of 10240ms with the assumed parameters. + +Consequently NR satellite access device can achieve very long sleep duration in both idle mode and connected mode. + +It is therefore concluded that NR satellite access meets device side energy efficiency requirement. + +## 4.9 Mobility + +As defined in in Report ITU-R M.2514 [2], mobility is the maximum device speed at which a defined QoS can be achieved (in km/h). The QoS is defined as normalized traffic channel link data rate. + +Both configurations with frequency reuse factor equal to 1 (FRF1) and frequency reuse factor equal to 3 (FRF3) are considered for mobility evaluation of the Rural-eMBB-s test environment. Detailed evaluation assumptions and results can be found in Annex A.3. + +The evaluation results of mobility for NR satellite access for both evaluation configuration with FRF1 and FRF3 are provided in Table 4.9-1. + +It is observed that NR satellite access fulfils the mobility requirement under 250 km/h. + +**Table 4.9-1 Evaluation results of NR satellite access mobility under 250 km/h** + +| Frequency reuse factor | ITU Requirement | | Evaluation results | Number of samples | +|------------------------|------------------------------------------------------|-------|--------------------|-------------------| +| FRF1 | Normalized traffic channel link data rate (bit/s/Hz) | 0.005 | 0.07 | 4 | +| | Residual decoded packet error ratio | 1% | 0.18% | 4 | +| FRF3 | Normalized traffic channel link data rate (bit/s/Hz) | 0.005 | 0.14 | 4 | +| | Residual decoded packet error ratio | 1% | 0.33% | 4 | + +## 4.10 Mobility interruption time + +As defined in Report ITU-R M.2514 [2], mobility interruption time is the shortest time duration supported by the system during which a user terminal cannot exchange user plane packets with any base station during mobility transitions. + +The mobility interruption time includes the time required to execute any radio access network procedure, radio resource control signalling protocol, or other message exchanges between the user terminal and base station, as applicable to the candidate RIT/SRIT. + +For NR satellite access, the mobility interruption time is evaluated without cell and satellite change for the beam mobility scenario. + +When moving within the same cell, the transmitting/receiving beam pair of the UE may need to be changed. + +For DL data transmission during UE mobility, gNB can configure different beams for this UE at different slots. It ensures appropriate transmit beam allocation to the UE for continuous DL transmission. Therefore, DL data packet transmission is kept during beam pair switching at different slots. + +For UL data transmission, PUSCH is sent using the beam configured by SRI (SRS resource indicator) by gNB. Accordingly, an appropriate gNB-side beam is selected for UL data reception. gNB may select different beams at different slots depending on the UE mobility. Therefore, UL data packet transmission is kept during beam pair switching at different slots. + +Based on the above analysis, the UE can keep exchanging user plane packets with gNB during the mobility transitions without cell and satellite change. Therefore, 0ms mobility interruption time is achieved by NR satellite access for this scenario. + +# --- 5 Self-evaluation of mMTC-s technical performance + +## 5.1 Connection density + +### 5.1.1 General + +As defined in Report ITU-R M.2514 [2], connection density is the system capacity metric defined as the total number of devices fulfilling a specific quality of service (QoS) per unit area (per km2). + +The evaluation methodology follows section 8.2 in Report ITU-R M.2514 [2], with assumptions, including system level configurations and traffic model. The QoS evaluated is that a 32-byte packet is successfully received. + +The Full-buffer system-level simulation approach followed by link level simulation (referred to as “full buffer system level simulation” below) has been used for the evaluation, following the methodology and principles outlined in section 7.1.3 of Report ITU-R M.2412 [9], adapted accordingly for satellite deployment. + +In a first step this evaluation method employs a full buffer system level simulation to derive the uplink SINR distribution. In a second step link level simulation are performed to determine the uplink spectral efficiency and data rate as functions of SINR. When combined these three functions supports the calculation of the expected long-term time-frequency resources required for each SINR to support the specified traffic model. + +Connection density is in a final step conceptually derived by the system bandwidth, declared for the candidate technology, divided by the average required frequency resource. The requirement is fulfilled if the recorded connection density exceeds the 500 devices/km2, while the time resource, i.e. the packet delay, at the 99th percentile per user is less than 10 seconds and the utilized total bandwidth does not exceed 30 MHz. + +This evaluation method is targeted to evaluate the connection density in terms of the capability of uplink data transmission. The capacity calculation is based on an assumption of ideal resource allocation among the multiple packets and users (e.g., there is no collision on resource allocation). The packet delay calculation does not consider the delays introduced by the connection access procedure. It also does not model synchronization and system information acquisition, control channel and downlink data channel performance. + +### 5.1.2 NR satellite access + +The connection density of NR satellite access is evaluated using the method described in clause 5.1.1. The Rural mMTC-s test environment is used for evaluation, with detailed evaluation assumptions as defined in Annex A.4 Configurations with frequency reuse factor (FRF) equal to 1 and 3 have been evaluated. + +The evaluation results of NR satellite access (applicable for FDD frequency bands defined in 3GPP TS 38.108/38.101-5) are shown in Table 5.1.2-1 expressed as the average performance presented by the contributing companies. The bandwidth evaluated to be required to fulfil the requirement is also provided, noting that the minimum bandwidth required is determined by the minimum defined system channel bandwidth: 5 MHz for NR satellite access. It is observed that NR satellite access fulfills connection density requirement under full buffer system level simulation followed by link level simulation. In all cases, the 99th percentile packet delay per user was observed to achieve the <10 seconds target by a large margin. It is also observed that, using this methodology, the connection density will scale linearly with the bandwidth allocated. + +**Table 5.1.2-1 Evaluation results of connection density for NR satellite access +(Full buffer system level simulation followed by link level simulation)** + +| Traffic model | Frequency reuse factor | ITU Requirement (/km2) | Connection density(/km2) | Bandwidth (kHz) | Number of samples | +|--------------------------|------------------------|------------------------|--------------------------|-----------------|-------------------| +| 1 message/day/device | FRF1 | 500 | 7205 | 180 | 4 | +| | FRF3 | 500 | 27357 | 540 | 4 | +| 1 message/2 hours/device | FRF1 | 500 | 600 | 180 | 4 | +| | FRF3 | 500 | 2277 | 540 | 4 | + +### 5.1.3 IoT NTN + +The connection density of IoT NTN (NB-IoT satellite access and eMTC satellite access) is evaluated using the method described in clause 5.1.1. The Rural mMTC-s test environment is used for evaluation, with detailed evaluation assumptions as defined in Annex A.4. Deployments with frequency reuse factor (FRF) equal to 1 and 3 have been evaluated. + +The evaluation results of NB-IoT satellite access and eMTC satellite access (applicable for FDD frequency bands defined in 3GPP TS 36.108/36.102) are shown respectively in Table 5.1.3-1 and Table 5.1.3-2 expressed as the average performance presented by the contributing companies. The bandwidth evaluated to be required to fulfil the requirement is also provided, noting that the minimum bandwidth required is determined by the defined system channel bandwidth: 200kHz for NB-IoT satellite access and 1.4MHz for eMTC satellite access. It is observed that NB-IoT satellite access and eMTC satellite access both fulfil connection density requirement under full buffer system level simulation followed by link level simulation. In all cases, the 99th percentile packet delay per user was observed to achieve the <10 seconds target by a large margin. It is also observed that, using this methodology, the connection density will scale linearly with the bandwidth allocated. + +**Table 5.1.3-1 Evaluation results of connection density for NB-IoT satellite access +(Full buffer system level simulation followed by link level simulation)** + +| Traffic model | Frequency reuse factor | ITU Requirement (/km2) | Connection density(/km2) | Bandwidth (kHz) | Number of samples | +|--------------------------|------------------------|------------------------|--------------------------|-----------------|-------------------| +| 1 message/day/device | FRF1 | 500 | 7218 | 180 | 5 | +| | FRF3 | 500 | 32744 | 540 | 5 | +| 1 message/2 hours/device | FRF1 | 500 | 601 | 180 | 5 | +| | FRF3 | 500 | 2728 | 540 | 5 | + +**Table 5.1.3-2 Evaluation results of connection density for eMTC satellite access +(Full buffer system level simulation followed by link level simulation)** + +| Traffic model | Frequency reuse factor | ITU Requirement (/km2) | Connection density(/km2) | Bandwidth (kHz) | Number of samples | +|--------------------------|------------------------|------------------------|--------------------------|-----------------|-------------------| +| 1 message/day/device | FRF1 | 500 | 4940 | 180 | 1 | +| | FRF3 | 500 | 18612 | 540 | 1 | +| 1 message/2 hours/device | FRF1 | 500 | 411 | 180 | 1 | +| | FRF1 | 500 | 2470 | 1080 | 1 | +| | FRF3 | 500 | 1551 | 540 | 1 | +| | FRF3 | 500 | 9306 | 3240 | 1 | + +# 6 Self-evaluation of HTC-s technical performance + +## 6.1 Reliability + +### 6.1.1 General + +As defined in Report ITU-R M.2514 [2], reliability is the success probability of transmitting a layer 2/3 packet within a required maximum time, which is the time it takes to deliver a small data packet from the radio protocol layer 2/3 SDU ingress point to the radio protocol layer 2/3 SDU egress point of the radio interface at a certain channel quality. + +The evaluation is conducted in the Rural-HRC-s test environment, applicable to handheld devices. Both downlink and uplink are evaluated. Detailed assumptions and results are provided in Annex A.5. + +### 6.1.2 DL reliability + +For downlink reliability, both evaluation configuration with frequency reuse factor equal to 1 and evaluation configuration with frequency reuse factor equal to 3 are evaluated. + +The evaluation results of NR FDD for downlink reliability are provided in Table 6.1.2-1. + +It is observed that NR satellite access fulfils the reliability requirement for downlink. + +**Table 6.1.2-1 Evaluation results of DL reliability for NR satellite access** + +| Frequency Reuse Factor | ITU Requirement | DL Reliability | Number of samples | +|------------------------|-----------------|----------------|-------------------| +| FRF 1 | 99.9% | 99.98% | 4 | +| FRF 3 | 99.9% | 99.96% | 5 | + +### 6.1.3 UL reliability + +For uplink reliability, both evaluation configuration with frequency reuse factor equal to 1 and evaluation configuration with frequency reuse factor equal to 3 are evaluated. + +The evaluation results of NR FDD for uplink reliability are provided in Table 6.1.3-2. + +It is observed that NR satellite access fulfils the reliability requirement for uplink. + +**Table 6.1.3-2 Evaluation results of UL reliability for NR satellite access** + +| Frequency Reuse Factor | ITU Requirement | UL Reliability | Number of samples | +|------------------------|-----------------|----------------|-------------------| +| FRF 1 | 99.9% | 99.97% | 4 | +| FRF 3 | 99.9% | 99.97% | 5 | + +# 7 Self-evaluation of generic requirements + +## 7.1 Service aspects + +According to Report ITU-R M.2514-0 [x5], the support for wide range of services should be inspected by the following question: + +- Does the proposal support a range of services? (eMBB-s, HRC-s, and mMTC-s)? + +The evaluation method is defined in Report ITU-R M.2412 [9], and the support of a wide range of services is verified by inspection of the candidate RITs/SRITs ability to meet the minimum technical performance requirements for various usage scenarios and their associated test environments. + +Based on the self-evaluation results in Section 5 to 7, it is observed that: + +- For the standalone RIT, NR satellite access RIT can meet the minimum technical performance requirements for the three test environments in eMBB-s, HRC-s and mMTC-s, Therefore, the standalone RIT can fulfil the service requirements. +- For the SRIT, NR satellite access component RIT can meet the minimum technical performance requirements for the three test environments in eMBB-s, HRC-s and mMTC-s, and IoT NTN RIT can at least meet the minimum technical performance requirements for the one of the test environments in mMTC-s. Therefore, the SRIT can fulfil the service requirements. + +## 7.2 Bandwidth + +### 7.2.1 NR satellite access + +The *transmission bandwidth configuration* $N_{RB}$ for each *SAN channel bandwidth* and subcarrier spacing is specified in Table 7.2.1-1 for FR1 as explained in TS 38.108[6] and TS 38.101-5[5]. + +**Table 7.2.1-1: Transmission bandwidth configuration $N_{RB}$ for FR1** + +| SCS (kHz) | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 30 MHz | +|-----------|----------|----------|----------|----------|----------| +| | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | +| 15 | 25 | 52 | 79 | 106 | 160 | +| 30 | 11 | 24 | 38 | 51 | 78 | +| 60 | N/A | 11 | 18 | 24 | 38 | + +The minimum guard band for each *SAN channel bandwidth* and SCS is specified in Table 7.2.1-2 for FR1. + +**Table 7.2.1-2 Minimum guard band (kHz) (FR1)** + +| SCS (kHz) | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 30 MHz | +|-----------|-------|--------|--------|--------|--------| +| 15 | 242.5 | 312.5 | 382.5 | 452.5 | 592.5 | +| 30 | 505 | 665 | 645 | 805 | 945 | +| 60 | N/A | 1010 | 990 | 1330 | 1290 | + +The number of RBs configured in any *SAN channel bandwidth* shall ensure that the minimum guard band specified in this clause is met. + +### 7.2.2 IoT NTN + +For NB-IoT satellite access, the *transmission bandwidth configuration* $N_{RB}$ for *SAN and UE channel bandwidth* and subcarrier spacing is specified in Table 7.2.2-1, as documented in TS 36.108 [11] and TS 36.102 [10], where 15kHz subcarrier spacing is specified for downlink and uplink operation, and 3.75kHz subcarrier spacing is specified only for uplink operation. + +**Table 7.2.2-1: Transmission bandwidth configuration $N_{RB}$ , $N_{tone\ 15kHz}$ and $N_{tone\ 3.75kHz}$ in NB-IoT satellite access channel bandwidth** + +| Channel bandwidth $BW_{Channel}$ [kHz] | 200 | +|----------------------------------------------------------|-----| +| Transmission bandwidth configuration $N_{RB}$ | 1 | +| Transmission bandwidth configuration $N_{tone\ 15kHz}$ | 12 | +| Transmission bandwidth configuration $N_{tone\ 3.75kHz}$ | 48 | + +For eMTC satellite access, the *transmission bandwidth configuration* $N_{RB}$ for *SAN and UE channel bandwidth* and subcarrier spacing is specified in Table 7.2.2-2, as documented in TS 38.108 [6] and TS 38.101-5 [5]. + +**Table 7.2.2-2: Transmission bandwidth configuration $N_{RB}$ in eMTC satellite access channel bandwidth** + +| | | +|----------------------------------------------------------|------------| +| Channel bandwidth BW_{Channel} [MHz] | 1.4 | +| Transmission bandwidth configuration $N_{RB}$ | 6 | + +The up to 30MHz scalable channel bandwidth to support the peak rate requirement for the SRIT is fulfilled via NR satellite access. The channel bandwidth for IoT NTN is not scalable at the UE because it is tailored for mMTC-s, where supporting high peak user data rates are less important than maintaining low device complexity. There is no aggregation support by the UE of multiple RF carriers. However, the system capacity can be scaled up by network deployment of multiple NB-IoT satellite access RF carriers or eMTC satellite access carriers, which enables to also scale up the user connection density and capacity. + +## 7.3 Spectrum + +### 7.3.1 NR satellite access + +Corresponding to the definition of frequency ranges from TS 38.108[6], FR1 frequency range is defined based on 410 MHz – 7125 MHz frequency interval as represented in Table 7.3.1-1. + +**Table 7.3.1-1: Definition of frequency ranges** + +| Frequency range designation | Corresponding frequency range | +|-----------------------------|-------------------------------| +| FR1 | 410 MHz – 7125 MHz | + +The Satellite Access Node and related UEs are designed to operate in the *operating bands* defined in Table 7.3.1-2. + +**Table 7.3.1-2: Satellite operating bands in FR1** + +| Satellite operating band | Uplink (UL) operating band
SAN receive / UE transmit
$F_{UL,low} - F_{UL,high}$ | Downlink (DL) operating band
SAN transmit / UE receive
$F_{DL,low} - F_{DL,high}$ | Duplex mode | +|-------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-------------| +| n256 | 1980 MHz – 2010 MHz | 2170 MHz – 2200 MHz | FDD | +| n255 | 1626.5 MHz – 1660.5 MHz | 1525 MHz – 1559 MHz | FDD | +| n254 | 1610 MHz – 1626.5 MHz | 2483.5 MHz – 2500 MHz | FDD | +| NOTE: Satellite bands are numbered in descending order from n256. | | | | + +### 7.3.2 IoT NTN + +IoT NTN is currently specified for operation in the *operating bands* defined in Table 7.3.2-1. + +**Table 7.3.2-1: Satellite operating bands in IoT NTN** + +| Satellite operating band | Uplink (UL) operating band
SAN receive / UE transmit
$F_{UL,low} - F_{UL,high}$ | Downlink (DL) operating band
SAN transmit / UE receive
$F_{DL,low} - F_{DL,high}$ | Duplex mode | +|------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-------------| +| 256 | 1980 MHz – 2010 MHz | 2170 MHz – 2200 MHz | FDD | +| 255 | 1626.5 MHz – 1660.5 MHz | 1525 MHz – 1559 MHz | FDD | +| 254 | 1610 MHz – 1626.5 MHz | 2483.5 MHz – 2500 MHz | FDD | +| NOTE: Satellite bands are numbered in descending order from 256. | | | | + +# --- 8 Conclusions + +Based on the self-evaluation results presented through Section 4 to 7, NR satellite access RIT fulfils all technical performance requirements in the three test environments: Rural – eMBB-s, Rural – mMTC-s, and Rural – HRC-s. IoT NTN RIT fulfils the technical performance requirements in at least one test environment: Rural – mMTC. + +Both NR satellite access RIT and IoT NTN RIT fulfil the spectrum requirement. + +5G NTN NR RIT and 5G NTN SRIT both fulfil the scalable bandwidth requirement by virtue of the scalable channel bandwidth supported by NR satellite access RIT. + +It is therefore concluded that: + +- 3GPP's 5G NTN SRIT fulfils the requirements and criteria for the Satellite Component of IMT-2020. +- 3GPP's 5G NTN NR RIT fulfils the requirements and criteria for the Satellite Component of IMT-2020. + +# Annex A: Simulation models and assumptions + +## A.1 Evaluation assumption for peak spectral efficiency and peak data rate for NR satellite access + +Evaluation parameters for NR satellite access peak spectral efficiency and peak data rate is shown in Table A.1-1. The notations can be found in equation (4.1.1) in Section 4.1. + +**Table A.1.1 NR Parameters for peak spectral efficiency and peak data rate evaluation** + +| Parameters | DL | UL | Remarks | +|---------------------------------------------|-----------------------|-----------------------|-------------------------------------------------------------| +| Max. coding rate $R_{max}$ | [666/1024 - 822/1024] | [434/1024 - 553/1024] | | +| Max. number of layers
$\nu_{Layers}$ | 1 | | | +| Highest modulation order $Q_m$ | 6 | 4 | DL: 64QAM
UL: 16QAM | +| Scaling factor of modulation
$f$ | 1 | | | +| Numerology
$\mu$ | 0 | | SCS = 15 kHz | +| Maximum RB allocation
$N_{PRB}^{BW,\mu}$ | 160 | 8 | For UL, 8 PRBs out of the full bandwidth is assigned per UE | +| Overhead (OH) | 0.14 | 0.08 | See 38.306, clause 4.1.2 | +| Elevation angle | 90° | | | +| Orbit height [km] | 600 | | | +| Frequency [GHz] | 2.00 | | | +| TX: EIRP [dBm] | 78.77 | 23.00 | | +| RX: G/T [dB/T] | -31.62 | 1.10 | | +| Atmospheric loss [dB] | 0 | | | +| Shadow fading margin [dB] | 0 | | | +| Scintillation loss [dB] | 0 | | | +| Polarization loss [dB] | 0 | | | +| Additional losses [dB] | 0 | | | + +## A.2 Evaluation assumption for spectral efficiency for NR satellite access + +The detailed assumptions and results for average, 5th percentile user spectral efficiency, user experienced data rate and area traffic capacity can be found in the attached document "A.2\_eMBB\_SE\_UserExpDataRate\_AreaTrafCap.zip". + +## A.3 Evaluation assumption for mobility for NR satellite access + +The detailed assumptions and results for mobility can be found in the attached document "A.3\_Mobility.zip" + +## --- A.4 Evaluation assumptions and results for connection density + +The detailed assumptions and results for connection density can be found in the attached document "A.4\_ConnectionDensity.zip". + +## --- A.5 Evaluation assumptions and results for reliability for NR satellite access + +The detailed assumptions and results for reliability can be found in the attached document "A.5\_Reliability.zip". + +# Annex B: Calibration for self-evaluation + +To facilitate the self-evaluation towards IMT-2020 submission of the 3GPP Satellite Radio Interface Technology, the system level simulators have been calibrated to ensure the results from different 3GPP entities are comparable. + +The following metrics are selected for calibration of self-evaluation: + +- DL Geometry +- Coupling loss: Coupling loss is defined as the signal loss from the antenna port to the antenna port. + +The calibration was conducted to the corresponding evaluation configurations of case 9 (FRF 1) and case 10 (FRF 3). Detailed calibration parameters and assumptions are found in Section 6 of 3GPP TR 38.821. It should be noted that these parameters are used for calibration purpose only. It worth also noting that two additional tiers of beams for FRF 1 and three additional tiers of beams for FRF 3 are simulated for intra-satellite interference modelling. However, only the statistics of the UEs connecting to the inner 19 beams were collected (see Fig. 6.1.1.1.1 [TR 38.821] for the beam layout based on FRF configurations). For the calibration purpose, the ionospheric scintillation loss shall be considered equal to zero (i.e., the UEs are located between 20 and 60 degrees of latitude). The atmospheric absorptions loss shall be considered. + +Fourteen 3GPP entities provided the calibration results, including ZTE, Thales, DOCOMO, Huawei, vivo, Nokia, CCU, ITRI, Qualcomm, Ericsson, CATT, Panasonic, CEWiT, and OPPO. The detailed assumptions and results for the calibration simulations can be found in the attached document "**B\_Calibration.zip**". + +The calibration results for the Rural eMBB-s environment with FRF1 and FRF3 are shown through Figure B-1 to Figure B-4, respectively. The results are based on the average of the results from the contributing entities. + +![Figure B-1: A line graph showing the coupling loss (CL) in dB for the Rural eMBB-s environment with FRF1. The x-axis is labeled 'CL, dB' and ranges from 120.00 to 130.00. The y-axis is labeled 'C.D.E. (%)' and ranges from 0 to 100. A blue curve labeled 'FRF1' shows a sigmoidal increase, starting near 0% at 122.00 dB and reaching nearly 100% at 128.00 dB.](d316838f6e9e77e82b4560d899938987_img.jpg) + +| CL, dB | C.D.E. (%) | +|--------|------------| +| 122.00 | 0 | +| 123.00 | 1 | +| 124.00 | 10 | +| 125.00 | 40 | +| 126.00 | 75 | +| 127.00 | 95 | +| 128.00 | 99 | +| 129.00 | 100 | + +Figure B-1: A line graph showing the coupling loss (CL) in dB for the Rural eMBB-s environment with FRF1. The x-axis is labeled 'CL, dB' and ranges from 120.00 to 130.00. The y-axis is labeled 'C.D.E. (%)' and ranges from 0 to 100. A blue curve labeled 'FRF1' shows a sigmoidal increase, starting near 0% at 122.00 dB and reaching nearly 100% at 128.00 dB. + +**Figure B-1 Coupling loss of Rural eMBB-s with FRF1** + +![Figure B-2: Geometry SINR of Rural eMBB-s with FRF1. A line graph showing the cumulative distribution function (CDF) of Geometry SINR (dB) for FRF1. The x-axis ranges from -10.00 to 10.00 dB, and the y-axis ranges from 0 to 100. The curve starts at 0% at -4.00 dB and reaches 100% at approximately 1.00 dB.](051638d871c75230edb3d005fa668810_img.jpg) + +This graph shows the cumulative distribution function (CDF) of Geometry SINR (dB) for FRF1. The x-axis represents Geometry SINR (dB) from -10.00 to 10.00 in increments of 2.00. The y-axis represents the CDF in percent from 0 to 100 in increments of 10. A blue curve labeled 'FRF1' starts at 0% at -4.00 dB, rises steeply between -3.00 dB and 1.00 dB, and reaches 100% at approximately 1.00 dB. + +| Geometry SINR (dB) | CDF (%) | +|--------------------|---------| +| -4.00 | 0 | +| -3.00 | 10 | +| -2.00 | 30 | +| -1.00 | 55 | +| 0.00 | 75 | +| 1.00 | 100 | + +Figure B-2: Geometry SINR of Rural eMBB-s with FRF1. A line graph showing the cumulative distribution function (CDF) of Geometry SINR (dB) for FRF1. The x-axis ranges from -10.00 to 10.00 dB, and the y-axis ranges from 0 to 100. The curve starts at 0% at -4.00 dB and reaches 100% at approximately 1.00 dB. + +Figure B-2 Geometry SINR of Rural eMBB-s with FRF1 + +![Figure B-3: Coupling loss of Rural eMBB-s with FRF3. A line graph showing the cumulative distribution function (CDF) of Coupling loss (CL, dB) for FRF3. The x-axis ranges from 90.00 to 150.00 dB, and the y-axis ranges from 0 to 100. The curve starts at 0% at approximately 118 dB and reaches 100% at approximately 128 dB.](bac21fd48fcd7f025c723590e07d1823_img.jpg) + +This graph shows the cumulative distribution function (CDF) of Coupling loss (CL, dB) for FRF3. The x-axis represents CL, dB from 90.00 to 150.00 in increments of 20.00. The y-axis represents the CDF in percent from 0 to 100 in increments of 10. A blue curve labeled 'FRF3' starts at 0% at approximately 118 dB, rises very steeply between 118 dB and 128 dB, and reaches 100% at approximately 128 dB. + +| CL, dB | CDF (%) | +|--------|---------| +| 118.00 | 0 | +| 120.00 | 10 | +| 122.00 | 30 | +| 124.00 | 55 | +| 126.00 | 75 | +| 128.00 | 100 | + +Figure B-3: Coupling loss of Rural eMBB-s with FRF3. A line graph showing the cumulative distribution function (CDF) of Coupling loss (CL, dB) for FRF3. The x-axis ranges from 90.00 to 150.00 dB, and the y-axis ranges from 0 to 100. The curve starts at 0% at approximately 118 dB and reaches 100% at approximately 128 dB. + +Figure B-3 Coupling loss of Rural eMBB-s with FRF3 + +![Line graph showing Coverage Probability (CP) vs Geometry SINR (dB) for FRF3. The curve starts near 0% at 6 dB and reaches 100% at approximately 8.5 dB.](b9d879f357d5f15fac9ea8585b87d0a2_img.jpg) + +The graph plots Coverage Probability (CP) in percent on the y-axis (0 to 100) against Geometry SINR in dB on the x-axis (4.00 to 10.00). A single blue line represents the FRF3 scenario. The curve begins at approximately 0% CP at 6.00 dB, rises steeply between 7.00 dB and 8.50 dB, and plateaus at 100% CP from 8.50 dB onwards. A legend in the bottom right corner identifies the line as 'FRF3'. + +| Geometry SINR (dB) | CP (%) | +|--------------------|--------| +| 4.00 | 0 | +| 6.00 | 0 | +| 7.00 | 5 | +| 8.00 | 35 | +| 8.50 | 100 | +| 10.00 | 100 | + +Line graph showing Coverage Probability (CP) vs Geometry SINR (dB) for FRF3. The curve starts near 0% at 6 dB and reaches 100% at approximately 8.5 dB. + +Figure B-4 Geometry SINR of Rural eMBB-s with FRF3 + +# --- Annex C: ITU-R Submission Templates for IMT-2020 for Satellite Radio Interface Technology + +## --- C.1 Description template – characteristics + +The characteristics template can be found in the attached document "C.1\_CharacteristicsTemplate.zip". + +## --- C.2 Description template – link budget + +The link budget template can be found in the attached document "C.2\_LinkBudgetTemplate.zip". + +## --- C.3 Compliance templates for services, for spectrum, for technical performance + +The compliance template can be found in the attached document "C.3\_ComplianceTemplate.zip". + +# Annex D: Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-06 | RAN#100 | RP-231403 | | | | TR skeleton for Study on self-evaluation towards the IMT-2020 submission of the 3GPP Satellite Radio Interface Technology | 0.0.1 | +| 2023-09 | RAN#101 | RP-232645 | | | | Added text for agreements on peak spectral efficiency and peak data rate | 0.1.0 | +| 2023-12 | RAN#102 | RP-23738 | | | | Withdrawn | 0.1.1 | +| 2023-12 | RAN#102 | RP-233945 | | | | Updated with agreed pCRs | 0.2.0 | +| 2023-12 | RAN#102 | RP-233980 | | | | For presentation to TSG RAN | 1.0.0 | +| 2023-12 | RAN #102 | - | | | | Approved v18.0.0 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/37_series/37985/raw.md b/marked/Rel-18/37_series/37985/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b3321633aef8829bbffc1312add52ecb45d20523 --- /dev/null +++ b/marked/Rel-18/37_series/37985/raw.md @@ -0,0 +1,1151 @@ + + +# 3GPP TR 37.985 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions of terms, symbols and abbreviations ..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Services and requirements ..... | 10 | +| 5 LTE V2X..... | 11 | +| 5.1 V2X sidelink physical layer..... | 11 | +| 5.1.1 Physical sidelink channels and signals ..... | 11 | +| 5.1.2 Sidelink synchronization ..... | 12 | +| 5.1.2.1 Synchronization references and priorities..... | 12 | +| 5.1.2.2 SLSS ..... | 12 | +| 5.1.2.2.1 SLSSID..... | 13 | +| 5.1.3 Concurrent operation and carrier aggregation ..... | 13 | +| 5.2 V2X sidelink resource allocation ..... | 14 | +| 5.2.1 Resource pools..... | 14 | +| 5.2.2 Resource allocation modes ..... | 15 | +| 5.2.2.1 Resource allocation mode 3 ..... | 15 | +| 5.2.2.2 Resource allocation mode 4 ..... | 16 | +| 5.2.2.2.1 Zones ..... | 17 | +| 5.2.2.3 Modes 3 and 4 resource pool sharing ..... | 18 | +| 5.3 Sidelink congestion control..... | 18 | +| 5.4 V2X sidelink higher-layer protocols ..... | 18 | +| 5.4.1 General ..... | 18 | +| 5.4.2 Resource pool configuration..... | 19 | +| 5.4.3 Measurement and reporting ..... | 19 | +| 5.4.4 Mobility management..... | 19 | +| 5.4.5 Assistance information for SL SPS configuration..... | 19 | +| 5.4.6 Transmission carrier selection..... | 19 | +| 5.4.7 SL packet duplication ..... | 19 | +| 5.4.8 Coordination between UL and V2X SL transmission..... | 20 | +| 5.4.9 Multi-PLMN operation..... | 20 | +| 5.5 V2X via the Uu interface ..... | 20 | +| 5.6 Network aspects ..... | 20 | +| 5.6.1 V2X service authorization..... | 20 | +| 5.6.2 Sidelink AMBR ..... | 20 | +| 6 NR V2X ..... | 21 | +| 6.1 Sidelink unicast, groupcast, and broadcast..... | 21 | +| 6.2 V2X sidelink physical layer..... | 21 | +| 6.2.1 Physical sidelink channels and signals ..... | 21 | +| 6.2.2 Sidelink synchronization ..... | 23 | +| 6.2.2.1 Synchronization references and priorities..... | 23 | +| 6.2.2.2 S-SSB and SLSS ..... | 23 | +| 6.2.2.2.1 SLSSID..... | 24 | +| 6.2.3 Sidelink CSI..... | 24 | +| 6.2.4 Sidelink HARQ ..... | 24 | +| 6.2.5 Coexistence between LTE-V2X and NR-V2X sidelinks ..... | 24 | +| 6.2.5.1 In-device coexistence..... | 24 | +| 6.2.5.2 Dynamic resource pool sharing ..... | 25 | +| 6.2.6 Concurrent operation and carrier aggregation ..... | 25 | + +| | | | +|-----------------|----------------------------------------------------------------------|-----------| +| 6.3 | V2X sidelink resource allocation ..... | 26 | +| 6.3.1 | Sidelink bandwidth parts and resource pools ..... | 26 | +| 6.3.1.1 | Sidelink bandwidth parts ..... | 26 | +| 6.3.1.2 | Resource pools ..... | 26 | +| 6.3.2 | Resource allocation modes ..... | 27 | +| 6.3.2.1 | Mode 1 ..... | 27 | +| 6.3.2.2 | Mode 2 ..... | 27 | +| 6.4 | Sidelink congestion control ..... | 30 | +| 6.5 | V2X sidelink higher-layer protocols ..... | 30 | +| 6.5.1 | General ..... | 30 | +| 6.5.2 | Measurement and reporting related to NR sidelink communication ..... | 31 | +| 6.5.3 | Mobility management for NR SL transmission/reception ..... | 32 | +| 6.5.4 | Assistance information and SL configured grant configuration ..... | 32 | +| 6.5.5 | Coordination between UL and NR SL transmission ..... | 32 | +| 6.5.6 | QoS mechanism ..... | 32 | +| 6.5.7 | Sidelink RRC ..... | 32 | +| 6.5.8 | Sidelink packet duplication ..... | 33 | +| 6.6 | V2X via the Uu interface ..... | 33 | +| 6.7 | Network aspects ..... | 33 | +| 6.7.1 | V2X service authorization ..... | 33 | +| 6.7.2 | Alternative QoS profiles ..... | 33 | +| 6.8 | Inter-UE coordination ..... | 33 | +| 7 | Multi-RAT V2X ..... | 34 | +| 7.1 | Cross-RAT operation ..... | 34 | +| 7.2 | MR-DC ..... | 34 | +| 8 | Transmission profiles ..... | 36 | +| 9 | Battery-limited UEs ..... | 37 | +| 9.1 | Power supply ..... | 37 | +| 9.2 | Partial sensing ..... | 37 | +| 9.3 | Sidelink DRX ..... | 38 | +| 10 | Roadside unit ..... | 38 | +| Annex A: | Change history ..... | 40 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, certain modal verbs have the following meanings: + +**shall** indicates a mandatory requirement to do something + +**shall not** indicates an interdiction (prohibition) to do something + +NOTE 1: The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +NOTE 2: The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +**should** indicates a recommendation to do something + +**should not** indicates a recommendation not to do something + +**may** indicates permission to do something + +**need not** indicates permission not to do something + +NOTE 3: The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +**can** indicates that something is possible + +**cannot** indicates that something is impossible + +NOTE 4: The constructions "can" and "cannot" shall not to be used as substitutes for "may" and "need not". + +**will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +NOTE 5: The constructions "is" and "is not" do not indicate requirements. + +# Introduction + +The 3GPP platform was first expanded to the automotive industry by the introduction of support for V2V and V2X services in Release 14. This support forms Phase 1 of 3GPP's ongoing project relating to V2X, and was intended to support a set of requirements sufficient for basic road safety services. Vehicles containing UEs with these features can use the uplink, downlink and sidelink to exchange information on their own status, such as position, speed, and heading with other nearby vehicles, infrastructure nodes, and pedestrians. Phase 2 of the V2X project was standardised in Release 15, and adds a number of new features to the sidelink intended to enhance efficiency and exploit developments in UE and network designs. These enhancements include sidelink carrier aggregation, higher-order modulation, and reduced latency. + +Phase 3 of V2X, in Release 16, adds support to NR (and also 5GC, not addressed in this TR) for advanced V2X use cases, and includes introduction of the NR sidelink. The use-cases are broadly grouped to enable vehicular platooning, exchange of extended sensor information, advanced driving, and remote driving. Phase 3 also allows either RAT's sidelink to be operated under control of the other RAT's Uu interface, as well as permitting connection to EPC or 5GC, to enable usage in the main MR-DC deployment scenarios. + +In the following clauses, LTE-V2X is described first, then NR-V2X, and finally certain aspects which have a degree of commonality to both RATs. + +Although this TR deals with RAN aspects, note that the core network architectures also have many adaptations to support V2X in both EPC and 5GC. These are referred to only as needed for other explanations in this TR, and details can be found in the relevant specifications. + +# 1 Scope + +The present document provides an overall description of the features introduced by 3GPP to LTE and NR in support of V2X services, starting from Rel-14. The purpose of this TR is to give an overview across the RAN specifications of how the features have been designed, and how they operate together. This document addresses LTE V2X and NR V2X via both sidelink, i.e. the PC5 interfaces, and via the cellular uplink/downlink, i.e. the Uu interfaces. It covers V2V, V2I/N, and V2P, as well as the eNB/gNB, UE, and RSU nodes. The intention is to provide descriptions at approximately the Stage 2 level of detail, and thus references are provided to RAN specifications for the reader to obtain precise details. + +The document is a 'living' document, i.e. it is permanently updated and presented to TSG-RAN meetings. + +# 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 TR 36.885: "Study on LTE-based V2X Services". +- [3] ETSI EN 302 637-2: "Specification of Cooperative Awareness Basic Service". +- [4] SAE J2735: "Dedicated Short Range Communications (DSRC) Message Set Dictionary". +- [5] ETSI EN 302 637-3 "Specifications of Decentralized Environmental Notification Basic Service". +- [6] 3GPP TS 22.185: "Service requirements for V2X services". +- [7] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios". +- [8] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation". +- [9] 3GPP TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding". +- [10] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC)". +- [11] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [12] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Measurements". +- [13] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [14] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC)". +- [15] 3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP)". + +- [16] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [17] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification". +- [18] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [19] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2". +- [20] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". +- [21] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [22] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms 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]. + +**example:** text used to clarify abstract rules by applying them literally. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +| | | +|----------|---------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 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]. + +Where the same abbreviation is used for LTE V2X and NR V2X, which is meant can be derived from the clause within which it appears, unless otherwise stated. + +| | | +|-------|--------------------------------------------------| +| 5GC | Fifth Generation core network | +| AGC | Automatic gain control | +| AMBR | Aggregate maximum bit rate | +| BSM | Basic safety message | +| BWP | Bandwidth part | +| CA | Carrier aggregation | +| CAM | Cooperative awareness message | +| CBR | Channel busy ratio | +| CPS | Contiguous partial sensing | +| CR | Channel occupancy ratio | +| DENM | Decentralized environmental notification message | +| DMRS | Demodulation reference signal | +| DRX | Discontinuous reception | +| EPC | Evolved packet core | +| MBSFN | Multicast-broadcast single-frequency network | +| MNO | Mobile network operator | +| PBPS | Periodic-based partial sensing | +| PPPP | ProSe per-packet priority | +| PPPR | ProSe per-packet reliability | + +| | | +|-------------|-------------------------------------------------------------------------------------------------| +| PSBCH | Physical sidelink broadcast channel | +| PSCCH | Physical sidelink control channel | +| PSSCH | Physical sidelink shared channel | +| PSSS, S-PSS | Primary sidelink synchronization signal (LTE), sidelink primary synchronization signal (NR) | +| PT-RS | Phase-tracking reference signal | +| P-UE | Pedestrian UE | +| RSU | Roadside unit | +| SA | Scheduling assignment | +| SCI | Sidelink control information | +| SC-PTM | Single-cell point-to-multipoint | +| SL-BCH | Sidelink broadcast channel | +| SLSS | Sidelink synchronization signal | +| S-RSSI | Sidelink received signal strength indicator | +| S-SSB | Sidelink synchronization signal block | +| SSSS, S-SSS | Secondary sidelink synchronization signal (LTE), sidelink secondary synchronization signal (NR) | +| V2I | Vehicle-to-infrastructure | +| V2P | Vehicle-to-pedestrian | +| V2V | Vehicle-to-vehicle | +| V2X | Vehicle-to-everything | + +# 4 Services and requirements + +LTE-V2X is designed with BSM, CAM, and DENM particularly in mind. BSMs and CAMs have the characteristic of generating periodic messages at intervals, whereas DENMs are event-triggered. As an illustration of the different message types, in TR 36.885 [2], BSM/CAM were modelled, for evaluation purposes, as periodically occurring sets of one 300-byte message followed by four 190-byte messages. These types of message regularly broadcast information such as the vehicle's heading, speed, latitude/longitude, etc. ETSI EN 302 637-2 [3], SAE J2735 [4]. In TR 36.885 [2], DENMs were modelled, for evaluation purposes, as Poisson distributed initiations of six 800-byte messages spaced by 100 ms. DENMs can contain various different messages depending on the cause for their transmission, such as imminent collision, sudden braking, or detection of a traffic jam, amongst others ETSI EN 302 637-3 [5]. The requirements relating to traffic size and pattern for LTE-V2X set in TS 22.185 [6] can be summarized as follows, although they do not limit the usage of LTE-V2X. Other requirements relating to general system function are also included in TS 22.185 [6]. + +- Support for periodic broadcast messages with payloads of 50-300 bytes. +- Support for event-triggered messages with payloads of up to 1200 bytes. +- Up to 10 messages per second transmitted by a UE. +- V2V and V2P latency of maximum 100 ms, or for V2V pre-crash sensing, maximum 20 ms. +- V2I latency, i.e. between a UE and RSU, of maximum 100 ms. +- V2N latency, i.e. when transferring messages via the cellular network, of maximum 1000 ms. +- Maximum relative velocity between two vehicles of 500 km/h, and maximum absolute velocity of 250 km/h for V2V and V2P UEs, and of a UE communicating with an RSU. +- Requirements relating to security, integrity, authorization, and privacy. + +NR V2X is designed with a broader set of more advanced V2X use cases in mind. These were specified in TS 22.18 [7], and are broadly arranged into four use case groups: vehicular platooning, extended sensors, advanced driving, and remote driving. + +- 1) Vehicles Platooning enables the vehicles to dynamically form a platoon travelling together. All the vehicles in the platoon obtain information from the leading vehicle to manage this platoon. These information allow the vehicles to drive closer than normal in a coordinated manner, going to the same direction and travelling together. +- 2) Extended Sensors enables the exchange of raw or processed data gathered through local sensors or live video images among vehicles, road site units, devices of pedestrian and V2X application servers. The vehicles can + +increase the perception of their environment beyond of what their own sensors can detect and have a more broad and holistic view of the local situation. High data rate is one of the key characteristics. + +- 3) Advanced Driving enables semi-automated or full-automated driving. Each vehicle and/or RSU shares its own perception data obtained from its local sensors with vehicles in proximity and that allows vehicles to synchronize and coordinate their trajectories or manoeuvres. Each vehicle shares its driving intention with vehicles in proximity too. +- 4) Remote Driving enables a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive by themselves or remote vehicles located in dangerous environments. For a case where variation is limited and routes are predictable, such as public transportation, driving based on cloud computing can be used. High reliability and low latency are the main requirements. + +The most demanding requirements set in TS 22.186 [7] are for a maximum sidelink range of 1000 m, a maximum throughput of 1 Gbps, a shortest latency of 3 ms, a maximum reliability of 99.999%, and a maximum transmission rate of 100 messages/second. However, there is not a use case which, on its own, demands all of these bounding requirements. The communication scenarios described in TS 22.186 [7] include a mixture of periodic and aperiodic services. Similar to LTE-V2X, there are also requirements relating to security, integrity, authorization, and privacy. + +# --- 5 LTE V2X + +## 5.1 V2X sidelink physical layer + +The LTE V2X sidelink supports broadcast transmission of messages in the physical layer, since this is a suitable approach for delivery BSM, CAM, DENM and similar traffic. In the MAC layer, a broadcast address can be mapped to a single UE or a group of UEs by implementation. Such implementation techniques have no particular specification support in LTE, and are transparent to the physical layer. + +### 5.1.1 Physical sidelink channels and signals + +The LTE V2X sidelink uses the following physical channels and signals: + +- Physical sidelink broadcast channel (PSBCH), specified in TS 36.211 [8, clause 9.6] +- Physical sidelink control channel (PSCCH), specified in TS 36.211 [8, clause 9.4] +- Physical sidelink shared channel (PSSCH), specified in TS 36.211 [8, clause 9.3] +- Primary and secondary sidelink synchronization signals (PSSS and SSSS) specified in TS 36.211 [8, clause 9.7]. These can be referred to jointly as the sidelink synchronization signal (SLSS). +- A demodulation reference signal (DMRS) associated with each of the three physical channels, specified in TS 36.211 [8, clause 9.8] + +LTE-V2X sidelink physical channels are transmitted using SC-FDMA. + +PSBCH transmits the SL-BCH transport channel, which carries the sidelink V2X Master Information Block (MIB-V2X) from the RRC layer. When in use, PSBCH transmits MIB-V2X every 160 ms in the central 72 subcarriers of the SL bandwidth. DMRS associated with PSBCH are transmitted in the 5th, 7th, and 10th symbols of the subframe. + +PSSS and SSSS are transmitted to allow other UEs to achieve sidelink synchronization when they do not have another source of synchronization available. They jointly convey the SLSS ID selected by the UE. For further details of SLSS and synchronization, refer to Clause 5.1.2. PSSS/SSSS also allow UEs to detect the sidelink subframe boundary, with subframe number and frame number signalled in MIB-V2X. + +PSSCH transmits the SL-SCH transport channel, which carries the TBs of data for transmission over SL. The resources in which PSSCH is transmitted can either be scheduled by an eNB and granted to the UE by a DCI (termed resource allocation mode 3, see Clause 5.2.2.1) or determined through a sensing procedure conducted autonomously by the transmitting UE (termed resource allocation mode 4, see Clause 5.2.2.2). A given TB can be transmitted once or twice, with a second transmission occurring a time gap after the first which is indicated in the scheduling SCI. + +PSCCH transmits physical layer sidelink control information (SCI), also known as a scheduling assignment (SA). For V2X, PSCCH is transmitted in two frequency-adjacent PRBs, and always carries SCI format 1, defined in TS 36.212 [9, clause 5.4.3.1.2]. To receive PSCCH, a UE has to monitor each defined pair of PRBs to determine whether PSCCH has been transmitted in them. PSCCH is transmitted in the same subframe(s) as the associated PSSCH, and can be transmitted in PRBs that are either frequency adjacent or frequency non-adjacent to the PSSCH. + +DMRS associated with PSSCH and PSCCH are transmitted in the 3rd, 6th, 9th, and 12th symbols of a subframe. + +### 5.1.2 Sidelink synchronization + +#### 5.1.2.1 Synchronization references and priorities + +There are four basic sources, or references, from which a V2X UE can derive its own synchronization: GNSS, its serving eNB, another UE transmitting SLSS (a SyncRef UE), or its own internal clock. In general, GNSS or eNB are regarded as the highest-quality sources. SyncRef UEs are distinguished between those which are directly synchronized to GNSS or an eNB, those which are 1 further step away, and those which are $\geq 2$ further steps away from GNSS/eNB. As a last resort, a UE unable to find any other synchronization reference will use its own internal clock to transmit SLSS. The V2X synchronization procedure defines a hierarchy or set of priorities among such synchronization references and requires all UEs to continuously search the hierarchy to get to the highest-quality one they can find. The general preference order is as follows, with details specified in TS 36.331 [10, clause 5.10.8]: + +- Level 1. Either GNSS or eNB, according to (pre-)configuration. +- Level 2. A SyncRef UE directly synchronized to a Level 1 source. +- Level 3. A SyncRef UE synchronized to a Level 2 source, i.e. indirectly synchronized to a Level 1 source. + - When the Level 1 preference is (pre-)configured as GNSS, in Level 2 and 3, SyncRef UEs in hierarchies derived from GNSS and eNB are of equal preference as a synchronization source. +- Level 4. Any other SyncRef UE. +- Level 5. UE's internal clock. + +Within a Level 2, or 3, or 4 set of SyncRef UEs, the one with the highest S-RSRP is selected. The hierarchy also allows fallback between eNB-derived and GNSS-derived chains should the Level 1 type chosen by (pre-)configuration be unsuitable. + +#### 5.1.2.2 SLSS + +The transmission and reception of SLSS (and PSBCH) is an optional V2X UE capability, and they can be transmitted on one or multiple synchronization carriers. + +A UE which is deriving its own synchronization from eNB or GNSS can be configured by the network to transmit SLSS on a synchronization carrier, or the network can permit it to do so if the RSRP of a reference cell falls below a threshold. If the network is not available, and the UE is synchronized to GNSS, it will transmit SLSS if permitted by its pre-configuration. When such a UE does not have GNSS synchronization, it will transmit SLSS, if permitted by its pre-configuration, while it cannot find a SyncRef UE with sufficiently high S-RSRP. Full details of the conditions for SLSS transmission are specified in TS 36.331 [10, clause 5.10.7.2]. + +In a V2X system, there can be a variety of UEs which are deriving synchronization from different sources, and since a UE can transmit SLSS on multiple carriers, it can have different synchronization sources among them. SLSS is therefore transmitted in different subframes depending on what synchronization source the UE is using. The system can be configured with either two or three different offsets with respect to the start of the 160 ms PSBCH period can be defined, which can allow different subframes for transmission according to whether the UE is synchronized to GNSS, eNB, or another SyncRef UE. + +PSSS and SSSS use the same sequences as PSS and SSS, respectively, with different root indices. When in use, both sequences are transmitted in the central 62 subcarriers of the SL bandwidth, in the same subframe as PSBCH, i.e. every 160 ms. PSSS is in the 2nd and 3rd symbols of the subframe, and SSSS in the 12th and 13th symbols. The two symbols of each signal are the same, which allows detectors to benefit from phase tracking between the two symbols. Figure 5.1.2.1-1 shows the relevant contents of a subframe which contain PSBCH, PSSS, and SSSS. + +![Figure 5.1.2.2-1: Contents of an LTE-V2X synchronization subframe. The diagram shows a 1 ms subframe structure. It starts with a 6 RBs wide PSBCH (blue), followed by two 6 RBs wide PSSS (yellow) blocks. This is followed by a 6 RBs wide DMRS (grey) block, then a 6 RBs wide PSBCH (blue) block, another 6 RBs wide DMRS (grey) block, a 6 RBs wide PSBCH (blue) block, a 6 RBs wide DMRS (grey) block, a 6 RBs wide PSBCH (blue) block, a 6 RBs wide DMRS (grey) block, a 6 RBs wide PSBCH (blue) block, two 6 RBs wide SSSS (green) blocks, and finally a GUARD (white) block. The total duration is 1 ms, and the total number of subcarriers is 82.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 5.1.2.2-1: Contents of an LTE-V2X synchronization subframe. The diagram shows a 1 ms subframe structure. It starts with a 6 RBs wide PSBCH (blue), followed by two 6 RBs wide PSSS (yellow) blocks. This is followed by a 6 RBs wide DMRS (grey) block, then a 6 RBs wide PSBCH (blue) block, another 6 RBs wide DMRS (grey) block, a 6 RBs wide PSBCH (blue) block, a 6 RBs wide DMRS (grey) block, a 6 RBs wide PSBCH (blue) block, a 6 RBs wide DMRS (grey) block, a 6 RBs wide PSBCH (blue) block, two 6 RBs wide SSSS (green) blocks, and finally a GUARD (white) block. The total duration is 1 ms, and the total number of subcarriers is 82. + +Figure 5.1.2.2-1: Contents of an LTE-V2X synchronization subframe. + +##### 5.1.2.2.1 SLSSID + +The SLSSID itself conveys information about the synchronization source of the transmitting UE. In general, the further a UE is away from a high-quality source of GNSS or eNB, the lower quality will be its own synchronization and thus the quality of an SLSS it transmits. There are a series of association rules among SLSS IDs, designed to allow the identification, and propagation through the system of, high-quality synchronization sources. Thus, for example, a UE which is in-coverage and directly synchronized to an eNB (a Level 2 SyncRef UE) uses an SLSSID which is configured by the network from 1-167, allowing SLSSID planning, and a UE using such a UE as a SyncRef UE (a Level 3 SyncRef UE) uses the same SLSSID, but indicates in V2X MIB that it is not directly eNB-synchronized. Subsequent UEs in this example hierarchy (Level 4 SyncRef UEs) use the SLSSID+168 to indicate their source is not directly synchronized to an eNB. A similar propagation hierarchy is used starting with a UE which is directly synchronized to GNSS, whose SLSSID is always 0, resulting in any UE which is more than one further step from GNSS using SLSSID 168 (or, in some cases, 169) so that a synchronization hierarchy based on GNSS can always be identified. Finally, a UE which cannot find GNSS, eNB, nor a SyncRef UE, selects an SLSSID randomly from 170-335, and UEs which synchronize to it propagate the same SLSSID. + +### 5.1.3 Concurrent operation and carrier aggregation + +V2X operation is defined in band 47 in TS 36.101 [11, clause 5.5G], which supports single-carrier and multi-carrier operation: + +Table 5.1.3-1: V2X operating band + +| E-UTRA Operating Band | E-UTRA V2X Operating Band | V2X UE transmit | | V2X UE receive | | Duplex Mode | Interface | +|-----------------------|---------------------------|-----------------|----------------|----------------|----------------|-------------|-----------| +| | | $F_{UL\_low}$ | $F_{UL\_high}$ | $F_{DL\_low}$ | $F_{DL\_high}$ | | | +| 47 | 47 | 5855 MHz | 5925 MHz | 5855 MHz | 5925 MHz | HD | PC5 | + +The V2X sidelink in band 47 can be operated concurrently with Uu FDD bands 3, 5, 7, 8, 20, 28, 71; Uu TDD bands 34, 39, 41; and NR Uu bands n1, n3, n5, n8, n34, n39, n40, n71, n78, n79. + +Sidelink CA is defined for resource allocation modes 3 and 4. When operating in CA, a given (sidelink) MAC PDU is transmitted, and if necessary re-transmitted, on a single sidelink carrier, and multiple MAC PDUs can be transmitted in parallel on different carriers. This provides a throughput gain in a similar way as for Uu CA. + +Sidelink CA in resource allocation mode 3 using a dynamic grant is similar to on the Uu interface, by including a carrier indication field (CIF) in the DCI from the eNB. This indicates which among the up to 8 configured sidelink carriers the allocation in the DCI applies to. + +Sidelink CA in resource allocation mode 4 uses the sensing procedure described in Clause 5.2.2.2 to select resources independently on each involved carrier. The same carrier is used for all MAC PDUs of the same sidelink process at least until the process triggers resource re-selection. Procedures to avoid unexpected UE behaviour when the demands of CA become high are also specified, which allow a UE to drop a transmission which uses an unmanageable amount of resources or transmit chains, or to reject and re-select resources for which it cannot meet the RF requirements under CA. + +Sidelink synchronization can also operate on multiple carriers, as mentioned in Clause 5.1.2. In addition, in sidelink CA operation, a SyncRef UE uses a single synchronization reference for all aggregated carriers, and may transmit SLSS/PSBCH on one or multiple of them according to capability. A receiving UE likewise uses the same + +synchronization reference (not necessarily a SyncRef UE) for all its aggregated carriers, and it uses the highest priority synchronization reference present among the available synchronization carriers. + +Another form of CA is PDCP duplication, where the same PDCP packet is transmitted in parallel on multiple sidelink carriers, to increase reliability. See Clause 5.4.7 for more discussion. + +## 5.2 V2X sidelink resource allocation + +### 5.2.1 Resource pools + +PSCCH and PSSCH resources are defined within resource pools for the respective channels. This concept is used because in general PSCCH/PSSCH cannot be transmitted (and thus are not expected to be received) in all PRBs and subframes in the system bandwidth, nor within a given frequency span configured for V2X sidelink. The notion of a resource pool also reflects, in resource allocation mode 4, that a UE will make its resource selections based on sensing within the (PSSCH) pool. + +For PSSCH, a resource pool is divided into sub-channels in the frequency domain, which are consecutively non-overlapping sets of $\geq 4$ PRBs in a subframe, the size depending on (pre-)configuration. Resource allocation, sensing, and resource selection are performed in units of a sub-channel, although it is possible that a small number of PRBs within a sub-channel are not used for transmission. + +For PSCCH, the resource pool definition depends on whether adjacent or non-adjacent transmission of PSCCH and PSSCH has been (pre-)configured for the resource pool. Adjacent transmission is achieved by defining the lowest pair of PRBs in each subchannel as candidates to contain PSCCH, and PSSCH is transmitted in the contiguous PRBs above them for the allocated number of subchannels. Non-adjacent transmission is achieved by defining sequential pairs of PRBs starting at the lowest frequency of the resource pool for PSCCH, and associating the $n^{\text{th}}$ pair to PSSCH transmission occupying from the $n^{\text{th}}$ PSSCH sub-channel for the allocated number of subchannels. Figure 5.2.1-1 shows examples of adjacent and non-adjacent transmission. To receive PSCCH, a UE has to monitor each defined pair of PRBs to determine whether PSCCH has been transmitted in them. + +![Figure 5.2.1-1a: Illustration of adjacent allocations of PSCCH and associated PSSCH. The diagram shows a grid of frequency (f) vs. time (t) resources. A vertical bracket on the left indicates 'One sub-channel'. Arrows point to specific resource blocks labeled 'PSCCH candidate resources'. The grid contains labels for User Equipment (UE): UE1, UE2, and UE4. UE1 is shown in the top row, UE2 in the middle row, and UE4 in the bottom row. The PSCCH candidate resources are indicated by green blocks, while the associated PSSCH resources are indicated by yellow blocks.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +The diagram illustrates a grid of frequency (f) on the vertical axis and time (t) on the horizontal axis. A vertical bracket on the left side of the grid is labeled 'One sub-channel'. Arrows point to specific resource blocks labeled 'PSCCH candidate resources'. The grid contains labels for User Equipment (UE): UE1, UE2, and UE4. UE1 is shown in the top row, UE2 in the middle row, and UE4 in the bottom row. The PSCCH candidate resources are indicated by green blocks, while the associated PSSCH resources are indicated by yellow blocks. + +Figure 5.2.1-1a: Illustration of adjacent allocations of PSCCH and associated PSSCH. The diagram shows a grid of frequency (f) vs. time (t) resources. A vertical bracket on the left indicates 'One sub-channel'. Arrows point to specific resource blocks labeled 'PSCCH candidate resources'. The grid contains labels for User Equipment (UE): UE1, UE2, and UE4. UE1 is shown in the top row, UE2 in the middle row, and UE4 in the bottom row. The PSCCH candidate resources are indicated by green blocks, while the associated PSSCH resources are indicated by yellow blocks. + +Figure 5.2.1-1a: Illustration of adjacent allocations of PSCCH and associated PSSCH. + +![Figure 5.2.1-1b: Illustration of non-adjacent allocations of PSCCH and associated PSSCH. The diagram shows a grid of frequency (f) vs. time (t) resources. The top section is labeled 'One sub-channel' and contains four resource blocks: UE1 (top-left), UE4 (middle-left), UE2 (top-right), and UE1 (middle-right). The bottom section is labeled 'PSCCH candidate resources' and contains four rows of resources. Green blocks represent PSCCH transmissions, and yellow blocks represent associated PSSCH transmissions. Dashed arrows indicate the mapping from PSCCH to PSSCH. The first row has a green block in the second column and a yellow block in the third column. The second row has a green block in the second column and a yellow block in the third column. The third row has a green block in the fourth column and a yellow block in the fifth column. The fourth row has a green block in the fifth column and a yellow block in the sixth column.](0a8d173734e4e46c344178e8d21bcbc3_img.jpg) + +Figure 5.2.1-1b: Illustration of non-adjacent allocations of PSCCH and associated PSSCH. The diagram shows a grid of frequency (f) vs. time (t) resources. The top section is labeled 'One sub-channel' and contains four resource blocks: UE1 (top-left), UE4 (middle-left), UE2 (top-right), and UE1 (middle-right). The bottom section is labeled 'PSCCH candidate resources' and contains four rows of resources. Green blocks represent PSCCH transmissions, and yellow blocks represent associated PSSCH transmissions. Dashed arrows indicate the mapping from PSCCH to PSSCH. The first row has a green block in the second column and a yellow block in the third column. The second row has a green block in the second column and a yellow block in the third column. The third row has a green block in the fourth column and a yellow block in the fifth column. The fourth row has a green block in the fifth column and a yellow block in the sixth column. + +**Figure 5.2.1-1b: Illustration of non-adjacent allocations of PSCCH and associated PSSCH.** + +Resource pools are (pre-)configured to a UE separately from the transmission perspective (TX pools) and the reception perspective (RX pools). This allows a UE to monitor for PSCCH, and hence receive PSSCH transmissions, in resource pools other than those in which it transmits, so that it can attempt to receive transmissions made by other UEs in those RX pools. + +In addition, there are exceptional resource pools configured to a UE, in its serving cell's SIB21 or in dedicated signalling. These can be used e.g. during RLF, handover, transition from RRC IDLE to RRC CONNECTED, or during change of dedicated V2X sidelink resource pools within a cell. In these cases, a UE may not have a stable configuration of TX resource pools but nevertheless should not be removed from the V2X system, so it can randomly select resources in the exceptional pool provided in its serving cell's SIB21 or in dedicated signalling, and use them temporarily. Likewise, UEs need to monitor the exceptional pools for PSCCH transmissions. + +### 5.2.2 Resource allocation modes + +LTE sidelink defines four resource allocation modes: 1, 2, 3, and 4. Modes 1 and 2 apply to D2D, while modes 3 and 4 apply to LTE V2X. + +#### 5.2.2.1 Resource allocation mode 3 + +Mode 3 is for resource allocation scheduled by eNB. As described in Clause 4, among the primary use cases for LTE-V2X is transmission of periodically-occurring messages, and for this reason there is particular support for sidelink SPS. However, dynamic sidelink grants are equally supported. + +The eNB scheduling activity is driven by the UE needing to send data on sidelink performing a sidelink BSR procedure similar to that on Uu to request a sidelink resource allocation from eNB. Depending on the type of traffic the UE has, eNB can provide a dynamic sidelink grant, or an activation of a SPS sidelink grant. + +A dynamic sidelink grant DCI provides, amongst other details TS 36.212 [9, clause 5.3.3.1.9A], the resources for up to two transmissions of the same TB. This is to allow higher reliability to be achieved without a feedback-based HARQ procedure, since LTE-V2X physical layer supports only broadcast transmission. Unlike Uu UL grants, the MCS information can optionally be provided by RRC signalling instead of the traditional DCI. For the case where RRC does not provide the MCS, the transmitting UE is left to select an appropriate MCS/TBS itself based on the knowledge it has of the TB to be transmitted and, potentially, the sidelink radio conditions. The transmitting UE populates its SCI with the information from eNB and other fields related to sidelink operation TS 36.212 [9, clause 5.4.3.1.2], and then transmits it and the associated PSSCH. + +The UE can be configured by eNB with up to 8 sidelink SPS configurations. Each configuration has an identifying index, and provides a different periodicity of sidelink transmission resource. A sidelink SPS configuration is not used by the UE until the eNB sends the UE a DCI which indicates it is now active. The activating DCI also provides all the + +same fields as a dynamic sidelink scheduling DCI described above, allowing the precise resource allocation for SPS to be determined by eNB at the time it is needed. A transmitting UE can use the thus activated sidelink SPS resources, at the configured periodicity, until they are released (i.e. de-activated) by the eNB transmitting a special DCI. Note that each time the UE uses the resources, it either uses the RRC configured MCS/TBS or selects one itself, i.e. the same way as dynamic operation. + +#### 5.2.2.2 Resource allocation mode 4 + +Mode 4 is for UE autonomous resource selection. Its basic structure is of a UE sensing, within a (pre-)configured resource pool, which resources are not in use by other UEs with higher-priority traffic, and choosing an appropriate amount of such resources for its own PSCCH/PSSCH transmission. Having selected such resources, the UE can transmit in them on a periodic (i.e. SPS) basis for a certain number of times, or until a cause of resource reselection is triggered. + +As described in Clause 5.2.2.1, the SCIs transmitted by UEs on PSCCH indicate the time-frequency resources in which the UE will transmit a PSSCH. The same SCI contents is used in mode 4, and also indicates the periodicity with which the UE will use the same resources. These SCI transmissions are used by sensing UEs to maintain a moving sensing window in the immediate past of which resources have been reserved by other UEs. This window is 1000 ms long for FDD systems. A sensing UE also measures the PSSCH-RSRP in the subframes of the sensing window, which implies the level of interference which would be caused and experienced if the sensing UE were to transmit in them. + +The sensing UE then selects resources for its first transmission from within a resource selection window. This window begins $\leq 4$ ms after the trigger for transmission, and is bounded by the latency requirement of the traffic, up to 100 ms (see Clause 4). The sensing UE assumes the same resources will be used by other UEs in the future as have been found reserved during the sensing window, according to the indicated periodicities and durations. Reserved resources in the selection window with PSSCH-RSRP above a threshold are excluded from being candidates by the sensing UE, with the threshold set according to the priorities (PPPP) of the traffic of the sensing and transmitting UE. Thus, a higher priority transmission from a sensing UE can occupy resources which are reserved by a transmitting UE with sufficiently low PSSCH-RSRP and sufficiently lower-priority traffic. + +From the set of resources in the selection window which have not been excluded, the sensing UE identifies those containing the lowest total received energy as a way to account for transmissions which were not found during decoding of PSCCHs, and identifies resources totalling 20% of the available resources within the traffic's latency bound, including gradual relaxation of the PSSCH-RSRP exclusion thresholds in 3 dB steps if necessary. The UE then selects a resource at random from the identified 20% and uses this resource semi-persistently for its transmissions. + +There are a number of triggers for resource re-selection. They are designed to support high mobility, and ensure that a UE cannot assume occupation of a resource for an excessive period, nor when the selected resource is either insufficient or excessive for what is needed by the UE's traffic, amongst other causes. + +![Flowchart of sensing and resource (re-)selection procedures. The steps are: 1. Keep decoding other UEs' SA and measuring corresponding PSSCH energy. 2. Collect sensing information including PSSCH-RSRP and S-RSSI measurement. 3. Exclude high-energy resources and form candidate resource set. 4. Select Tx resource and transmit semi-persistently. A decision diamond 'Resource Re-selection?' follows. If YES, Restart process (loop back to step 2). If NO, Continue transmissions on same resources (loop back to step 4).](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +graph TD + A[Keep decoding other UEs' SA and measuring corresponding PSSCH energy] --> B[Collect sensing information including PSSCH-RSRP and S-RSSI measurement] + B --> C[Exclude high-energy resources and form candidate resource set] + C --> D[Select Tx resource and transmit semi-persistently] + D --> E{Resource Re-selection?} + E -- YES - Restart process --> B + E -- NO - Continue transmissions on same resources --> D + +``` + +Flowchart of sensing and resource (re-)selection procedures. The steps are: 1. Keep decoding other UEs' SA and measuring corresponding PSSCH energy. 2. Collect sensing information including PSSCH-RSRP and S-RSSI measurement. 3. Exclude high-energy resources and form candidate resource set. 4. Select Tx resource and transmit semi-persistently. A decision diamond 'Resource Re-selection?' follows. If YES, Restart process (loop back to step 2). If NO, Continue transmissions on same resources (loop back to step 4). + +Figure 5.2.2.2-1: Summary of sensing and resource (re-)selection procedures. + +##### 5.2.2.2.1 Zones + +Cellular networks are designed to support resource re-use over a given geographical area, to manage interference and improve area spectral efficiency. A similar concept is available in LTE-V2X. LTE-V2X can optionally divide the world into zones, which have a (pre-)configurable width and height. Nearby zones are assigned different resource pools, with spatially-periodic re-use over a distance controlled by the zone width and height. A UE performs transmission within the resource pool(s) associated with its current zone, for mode 4. Figure 5.2.3-1 shows an example of the configuration of zones, where those with the same zone\_id use the same transmission resource pools. + +![Illustration of zones showing a grid of zones with IDs 0 through 8. The grid is 6 columns wide and 5 rows high. The columns are labeled x=0, 1, 2, 0, 1, 2. The rows are labeled y=0, 1, 2, 0, 1. The zones repeat in a 3x3 pattern: Zone 0 (yellow), Zone 1 (green), Zone 2 (blue) in the first row; Zone 3 (red), Zone 4 (purple), Zone 5 (orange) in the second row; Zone 6 (grey), Zone 7 (pink), Zone 8 (cyan) in the third row. This pattern repeats for the remaining rows.](250cf77a1cd51989da09fca796b3e4ea_img.jpg) + +| | | | | | | | +|-------|--------|--------|--------|--------|--------|--------| +| x \ y | 0 | 1 | 2 | 0 | 1 | 2 | +| 0 | Zone 0 | Zone 1 | Zone 2 | Zone 0 | Zone 1 | Zone 2 | +| 1 | Zone 3 | Zone 4 | Zone 5 | Zone 3 | Zone 4 | Zone 5 | +| 2 | Zone 6 | Zone 7 | Zone 8 | Zone 6 | Zone 7 | Zone 8 | +| 0 | Zone 0 | Zone 1 | Zone 2 | Zone 0 | Zone 1 | Zone 2 | +| 1 | Zone 3 | Zone 4 | Zone 5 | Zone 3 | Zone 4 | Zone 5 | + +Illustration of zones showing a grid of zones with IDs 0 through 8. The grid is 6 columns wide and 5 rows high. The columns are labeled x=0, 1, 2, 0, 1, 2. The rows are labeled y=0, 1, 2, 0, 1. The zones repeat in a 3x3 pattern: Zone 0 (yellow), Zone 1 (green), Zone 2 (blue) in the first row; Zone 3 (red), Zone 4 (purple), Zone 5 (orange) in the second row; Zone 6 (grey), Zone 7 (pink), Zone 8 (cyan) in the third row. This pattern repeats for the remaining rows. + +Figure 5.2.3-1: Illustration of zones. $x' = \text{ceil}(x/L) \bmod N_x$ ; $y' = \text{ceil}(y/W) \bmod N_y$ ; zone\_id= $y' \times N_x + x'$ ; where x and y are the longitude and latitude of the UE's location, L, W are the length and width of each zone, respectively, and $N_x$ , $N_y$ are the number of zones in length and width respectively. + +#### 5.2.2.3 Modes 3 and 4 resource pool sharing + +Resource pools for mode 3 and mode 4 are (pre-)configured separately from one another. In Rel-14, a receiving UE whether operating in mode 3 or mode 4 does not know in any particular way that a transmission in mode 3 has SPS characteristics, since the mode 3 SCI always indicates that its PSSCH transmission is single-shot. Thus, a mode 4 UE will not exclude the occupied resources during its resource selection procedure. In Rel-15, resource pool sharing is enabled by the mode 3 SCI also indicating a SPS reservation period, and mode 4 UEs of both releases are therefore able to account for such transmissions in the resource (re-)selection procedure. + +It is also possible for a UE operating in mode 3 to perform the mode 4 sensing procedure in order to report to eNB regarding the occupancy of resources in the mode 4 pools. This provides information which the eNB can use in determining its scheduling behaviour for mode 3. + +## 5.3 Sidelink congestion control + +Each sidelink packet is associated with a PPPP and PPPR passed down ultimately to the physical layer from upper layers, which determine the values based on the QoS requirements of the message. PPPR allows management of reliability, for example see Clause 5.4.7. The PPPP of a packet is indicated dynamically in the SCI which schedules the PSSCH for the packet. A physical measurement of CBR is also defined in each subframe TS 36.214 [12, clause 5.1.30], which measures the portion of the resource in a resource pool which has a high received signal energy (S-RSSI) in the most recent 100 subframes. CBR is a measurement of the congestion present recently in the resource pool. Another measurement, CR defined in TS 36.214 [12, clause 5.1.31], counts the total number of subchannels a UE has and will transmit in during a window of up to 1000 ms including the current subframe. CR is thus a measurement of how much resource a UE has recently, and will soon, claim. + +A UE can be (pre-)configured with a set of CBR ranges to each of which is linked a CR-limit. When a UE finds its CR exceeds the CR-limit for the CBR range it currently measures, it must reduce its CR to not exceed the limit. How this is done is up to UE implementation, and can include increasing MCS to reduce resource occupation, dropping (re-)transmissions, etc. PPPP can also be (pre-)configured with a mapping to the UE's maximum permitted transmit power, the limitation on which acts to reduce the CBR measured by sufficiently distant UEs. + +PPPP is used as described in Clause 5.2.2 to aid distributed sidelink congestion control based on the relative priorities of traffic from UEs that consider occupying a given resource. PPPP and CBR can each also be (pre-)configured with mappings to ranges of values of transmission parameters, e.g. a range of MCS values, and/or a range of numbers of subchannels, etc. In this case, the UE has to choose its transmission parameters from within the range corresponding to the prevailing PPPP and/or CBR. + +## 5.4 V2X sidelink higher-layer protocols + +### 5.4.1 General + +Figure 5.4.1-1 shows the user plane protocol stack for V2X sidelink communication. The Access Stratum protocol stack for user plane in the PC5 interface consists of PDCP, RLC, MAC and PHY as shown below in Figure 5.4.1-1. The detailed functions performed by PDCP, RLC and MAC sublayers are listed in TS 36.300 [13, clause 6], and some other details specific to V2X sidelink are described in TS 36.300 [13, clauses 23.10.2.1 and 23.14.1.1]. The PHY layer performs the functions described in Clause 5.1. + +![Diagram of the user-plane protocol stack for V2X sidelink communication between UE A and UE B.](7b8b192e2853ef28d28eff0241ebe86b_img.jpg) + +The diagram illustrates the user-plane protocol stack for V2X sidelink communication between two User Equipment (UE) units, UE A and UE B. Both UEs are shown within dashed rectangular boxes. Inside each box, there are four stacked protocol layers: PDCP at the top, followed by RLC, MAC, and PHY at the bottom. Horizontal double-headed arrows connect the corresponding layers in UE A and UE B, indicating bidirectional communication. The label 'PC5-U' is positioned below the PHY layers, centered between the two UEs. + +Diagram of the user-plane protocol stack for V2X sidelink communication between UE A and UE B. + +Figure 5.4.1-1: User-Plane protocol stack for V2X sidelink communication + +Figure 5.4.1-2 shows the control plane protocol stack for V2X sidelink communication. The Access Stratum protocol stack for control plane in the PC5 interface consists of RRC, RLC, MAC and PHY as shown below in Figure 5.4.1-2. The control plane protocol for V2X sidelink communication is mainly used for the transmission of sidelink broadcast control channel (SBCCH), and its functions are detailed in TS 36.300 [13, clause 23.10.2.2]. + +![Diagram of the control-plane protocol stack for V2X sidelink communication between UE A and UE B.](10781f43062bf3e9601a1e086710556c_img.jpg) + +The diagram illustrates the control-plane protocol stack for V2X sidelink communication between two User Equipment (UE) units, UE A and UE B. Both UEs are shown within dashed rectangular boxes. Inside each UE box, there are four stacked protocol layers: RRC (Radio Resource Control) at the top, followed by RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical) at the bottom. Horizontal double-headed arrows connect the corresponding layers in UE A to those in UE B, indicating bidirectional communication. The entire stack is labeled 'PC5-C' at the bottom center, indicating the PC5 interface for control plane communication. + +Diagram of the control-plane protocol stack for V2X sidelink communication between UE A and UE B. + +Figure 5.4.1-2: Control-Plane protocol stack for V2X sidelink communication + +### 5.4.2 Resource pool configuration + +When the UE is in network coverage, it may use the resource configurations provided by the eNB via dedicated signalling or system information. When the UE is out of coverage, it may use pre-configured resource pools for V2X sidelink communication. Details of how the resource pools are (pre)configured and how the UE uses them for V2X sidelink communication transmission and reception are specified in TS 36.331 [10, clauses 5.10.12 and 5.10.13]. + +### 5.4.3 Measurement and reporting + +Some measurement and reporting mechanisms are supported specifically for V2X sidelink communication, including CBR measurement and reporting, reporting of its sensing results and geo-location reporting. Details of above listed measurement and reporting mechanism specific for V2X sidelink communication are specified in TS 36.331 [10, clause 5.5]. + +### 5.4.4 Mobility management + +UE can perform V2X sidelink transmission and reception during handover and cell reselection. Related details are specified in TS 36.331 [10, clause 5.10.13.1]. + +### 5.4.5 Assistance information for SL SPS configuration + +The UE can report UE assistance information to the eNB to facilitate the configuration of sidelink SPS described in Clause 5.2.2.1. Details of the UE assistance information for sidelink SPS configuration are specified in TS 36.331 [10, clause 5.6.10]. + +### 5.4.6 Transmission carrier selection + +For V2X sidelink communication, the UE is allowed to transmit and receive on multiple sidelink carriers (pre)configured by the network, and the UE selects specific sidelink carriers among them for transmission. The (pre)configured sidelink carriers can be provided by the network as specified in TS 36.331 [10, clause 5.10.13.1]. Details of transmission carrier selection are specified in TS 36.321 [14, clause 5.14.1.5]. + +### 5.4.7 SL packet duplication + +To improve the reliability of V2X sidelink communication, a sidelink PDCP duplication mechanism is supported, where a PDCP PDU is duplicated into two instances and transmitted on two different sidelink carriers. Details of sidelink PDCP duplication are specified in TS 36.323 [15, clause 5.1.3 and 5.1.4] as well as TS 36.321 [14, clause 5.14.1.3.1]. + +### 5.4.8 Coordination between UL and V2X SL transmission + +There is the possibility that the UE needs to perform UL transmission and V2X sidelink transmission overlapped in time domain, but the UE cannot transmit both. In this case, the UE will prioritize between the two transmissions. Details of the prioritization between UL transmission and V2X sidelink transmission are specified in TS 36.321 [14, clauses 5.4.2.2 and 5.14.1.2.2]. + +### 5.4.9 Multi-PLMN operation + +To support multi-PLMN operation for V2X sidelink communication, the UE may receive the V2X sidelink communication of other PLMNs. However, V2X sidelink transmission in other PLMNs is not allowed. The same sidelink resource pool may be configured to the eNBs within a PLMN. Details of multi-PLMN operation for V2X sidelink communication are specified in TS 36.331 [10, clause 23.14.1.1]. + +## 5.5 V2X via the Uu interface + +LTE-V2X, as mentioned above, is focused on transmission of a few types of periodic traffic, which can have different periodicities. Apart from using the sidelink, it is possible to transfer V2X data via the cellular network UL/DL, taking advantage of its centrally-scheduled operation, predictable latency bounds, and inter-cell communications. + +An extended form of UL SPS for V2X is supported, to allow firstly that V2X UL SPS and normal UL SPS can be used together, and also that multiple V2X UL SPS configurations can be defined to account for the different periodic V2X traffic types. Whereas in Rel-8 UL SPS a single SPS configuration can be provided by RRC, for LTE-V2X, up to 8 UL SPS configurations can be provided, similar to on the sidelink, which the eNB is assisted in the configuration of by information on traffic characteristics, etc., reported provided by the UE. A specialised version of DCI format 0 is then used to activate/release UL V2X SPS configurations as needed, and separately from the normal UL SPS configuration. + +LTE supports multicast/broadcast operation via SC-PTM and MBSFN transmission. These transmission types can also be used for V2X messages, and some adaptations for LTE-V2X are included to allow scheduling more frequent transmissions of data and service (re-)configuration information. + +## 5.6 Network aspects + +### 5.6.1 V2X service authorization + +Considering the different UE types based on subscription information in the HSS, the eNB receives the authorization status of the UE provided by a MME or a neighbour eNB, to know whether the UE is authorized as a Vehicle UE and/or a Pedestrian UE. + +Only authorized UEs can perform V2X sidelink communication. Sidelink radio resources are provided to UEs in different ways according to the different services supported. + +### 5.6.2 Sidelink AMBR + +UE sidelink AMBR is provided to the eNB by a MME or a neighbour eNB, and used for the UE's sidelink communication in mode 3. The sidelink AMBR is based on subscription information from the HSS and the operator's policy, which is used to cap the PC5 transmission from a particular UE. + +![Figure 5.6-1 Network Infrastructure for LTE V2X. The diagram shows an EPC (Evolved Packet Core) connected to two eNBs (evolved NodeBs). The eNBs are connected to several User Equipment (UE) devices, represented by car icons. The connections between the eNBs and the UEs are labeled 'Uu'. A callout box from the EPC indicates '- Authorization status of UE' and '- UE Sidelink AMBR'. On the right side, three UEs are shown with bidirectional arrows between them labeled 'PC5', representing sidelink communication.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Figure 5.6-1 Network Infrastructure for LTE V2X. The diagram shows an EPC (Evolved Packet Core) connected to two eNBs (evolved NodeBs). The eNBs are connected to several User Equipment (UE) devices, represented by car icons. The connections between the eNBs and the UEs are labeled 'Uu'. A callout box from the EPC indicates '- Authorization status of UE' and '- UE Sidelink AMBR'. On the right side, three UEs are shown with bidirectional arrows between them labeled 'PC5', representing sidelink communication. + +Figure 5.6-1 Network Infrastructure for LTE V2X. + +# 6 NR V2X + +## 6.1 Sidelink unicast, groupcast, and broadcast + +Whereas LTE-V2X supports broadcast transmission in the physical layer and any finer-grained addressing is handled according to MAC layer ID implementation, NR V2X has physical layer support for broadcast, unicast, and groupcast sidelink operation. The addition of unicast and groupcast is linked with the introduction of sidelink HARQ feedback (clause 6.2.4), high order modulation, sidelink CSI, and PC5-RRC (clause 6.5.7), amongst other points. + +## 6.2 V2X sidelink physical layer + +### 6.2.1 Physical sidelink channels and signals + +The NR V2X sidelink uses the following physical channels and signals: + +- Physical sidelink broadcast channel (PSBCH) and its DMRS, specified in TS 38.211 [16, clauses 8.3.3 and 8.4.1.4] +- Physical sidelink control channel (PSCCH) and its DMRS, specified in TS 38.211 [16, clauses 8.3.2 and 8.4.1.3] +- Physical sidelink shared channel (PSSCH) and its DMRS, specified in TS 38.211 [16, clauses 8.3.1 and 8.4.1.1] +- Physical sidelink feedback channel (PSFCH), specified in TS 38.211 [16, clause 8.3.4] +- Sidelink primary and secondary synchronization signals (S-PSS and S-SSS) specified in TS 38.211 [16, clause 8.4.2], which are organized into the sidelink synchronization signal block (S-SSB) together with PSBCH. S-PSS and S-SSS can be referred to jointly as the sidelink synchronization signal (SLSS). +- Phase-tracking reference signal (PT-RS) in FR2, specified in TS 38.211 [16, clause 8.4.1.2]. +- Channel state information reference signal (CSI-RS), specified in TS 38.211 [16, clause 8.4.1.5]. See clause 6.2.3 for CSI. + +NR-V2X sidelink supports subcarrier spacings of 15, 30, 60 and 120 kHz. Their associations to CPs and frequency ranges are as for NR UL/DL, but using only the CP-OFDM waveform. The modulation schemes available are QPSK, 16-QAM, 64-QAM, and 256-QAM. + +PSBCH transmits the SL-BCH transport channel, which carries the sidelink V2X Master Information Block (MIB-V2X) from the RRC layer. When in use, PSBCH transmits MIB-V2X every 160 ms in 11 RBs of the SL bandwidth, with possible repetitions in the period. DMRS associated with PSBCH are transmitted in every symbol of the S-SSB slot. S-PSS and S-SSS are transmitted together with PSBCH in the S-SSB. They jointly convey the SLSS ID used by the UE. For further details of S-SSB, SLSS, and synchronization, refer to Clause 6.2.2. + +Sidelink control information (SCI) in NR V2X is transmitted in two stages. The first-stage SCI is carried on PSCCH and contains information to enable sensing operations, information about the resource allocation of the PSSCH, and, when needed, indication that the UE can receive conflict information in inter-UE coordination. + +PSSCH transmits the second-stage SCI and the SL-SCH transport channel. The second-stage SCI can carry information needed to identify and decode the associated SL-SCH, as well as control for HARQ procedures, triggers for CSI feedback, inter-UE coordination requests and information, etc. SL-SCH carries the TB of data for transmission over SL. + +The resources in which PSSCH is transmitted can be scheduled or configured by a gNB (termed resource allocation mode 1, see Clause 6.3.2.1) or determined through a sensing procedure conducted autonomously by the transmitting UE (termed resource allocation mode 2, see Clause 6.3.2.2). A given TB can be transmitted multiple times, as described in Clauses 6.2.4 and 6.3.2. DMRS associated with rank-1 or rank-2 PSSCH can be transmitted in 2, 3, or 4 sidelink symbols distributed through a sidelink slot. + +Multiplexing between PSCCH and PSSCH is in time and frequency within a slot, illustrated in two examples in Figure 6.2.1-1. + +![Figure 6.2.1-1(a): Example slot format of 2-symbol PSCCH, 2-symbol PSSCH-DMRS, and no PSFCH. The diagram shows a single slot divided into 14 symbols. The first symbol is AGC (blue). The second and third symbols are PSCCH (yellow) and PSSCH (green) respectively. The fourth symbol is DMRS (red). The fifth through tenth symbols are PSSCH (green). The eleventh symbol is DMRS (red). The twelfth and thirteenth symbols are PSSCH (green). The fourteenth symbol is GUARD (white).](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +Figure 6.2.1-1(a): Example slot format of 2-symbol PSCCH, 2-symbol PSSCH-DMRS, and no PSFCH. The diagram shows a single slot divided into 14 symbols. The first symbol is AGC (blue). The second and third symbols are PSCCH (yellow) and PSSCH (green) respectively. The fourth symbol is DMRS (red). The fifth through tenth symbols are PSSCH (green). The eleventh symbol is DMRS (red). The twelfth and thirteenth symbols are PSSCH (green). The fourteenth symbol is GUARD (white). + +Figure 6.2.1-1(a): Example slot format of 2-symbol PSCCH, 2-symbol PSSCH-DMRS, and no PSFCH. + +![Figure 6.2.1-1(b): Example slot format of 3-symbol PSCCH, 3-symbol PSSCH-DMRS, and PSFCH. The diagram shows a single slot divided into 14 symbols. The first symbol is AGC (blue). The second, third, and fourth symbols are PSCCH (yellow), DMRS (red), and PSSCH (green) respectively. The fifth through seventh symbols are DMRS (red), PSSCH (green), and PSSCH (green) respectively. The eighth symbol is DMRS (red). The ninth and tenth symbols are PSSCH (green). The eleventh symbol is GUARD (white). The twelfth symbol is AGC (PSFCH) (purple). The thirteenth symbol is PSFCH (purple). The fourteenth symbol is GUARD (white).](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +Figure 6.2.1-1(b): Example slot format of 3-symbol PSCCH, 3-symbol PSSCH-DMRS, and PSFCH. The diagram shows a single slot divided into 14 symbols. The first symbol is AGC (blue). The second, third, and fourth symbols are PSCCH (yellow), DMRS (red), and PSSCH (green) respectively. The fifth through seventh symbols are DMRS (red), PSSCH (green), and PSSCH (green) respectively. The eighth symbol is DMRS (red). The ninth and tenth symbols are PSSCH (green). The eleventh symbol is GUARD (white). The twelfth symbol is AGC (PSFCH) (purple). The thirteenth symbol is PSFCH (purple). The fourteenth symbol is GUARD (white). + +Figure 6.2.1-1(b): Example slot format of 3-symbol PSCCH, 3-symbol PSSCH-DMRS, and PSFCH. + +When used for HARQ purposes, PSFCH carries HARQ feedback over the sidelink from a UE which is an intended recipient of a PSSCH transmission (henceforth an Rx UE) to the UE which performed the transmission (henceforth a Tx UE). Sidelink HARQ feedback may be in the form of conventional ACK/NACK, or NACK-only with nothing transmitted in case of successful decoding; for more information refer to clause 6.2.4. PSFCH can also convey inter-UE coordination information; refer to clause 6.8. + +PSFCH transmits a Zadoff-Chu sequence in one PRB repeated over two OFDM symbols, the first of which can be used for AGC, near the end of the sidelink resource in a slot. The time resources for PSFCH are (pre-)configured to occur once in every 1, 2, or 4 slots. Frequency/code resources are derived implicitly from those used by the associated PSSCH transmission, together with the L1 identity of the UE transmitting PSSCH and, when groupcast with ACK/NACK feedback is used, the identity within the group of the UE transmitting PSFCH. + +### 6.2.2 Sidelink synchronization + +#### 6.2.2.1 Synchronization references and priorities + +There are four basic sources, or references, from which a V2X UE can derive its own synchronization: GNSS, a gNB/eNB, another UE transmitting SLSS (here termed a SyncRef UE), or its own internal clock. In general, GNSS or eNB/gNB are regarded as the highest-quality sources. SyncRef UEs are distinguished between those which are directly synchronized to GNSS or a gNB/eNB, those which are 1 further step away, and those which are $\geq 2$ further steps away from GNSS or gNB/eNB. As a last resort, a UE unable to find any other synchronization reference will use its own internal clock to transmit S-SSB. The V2X synchronization procedure defines a hierarchy or set of priorities among such synchronization references and requires all UEs to continuously search the hierarchy to get to the highest-quality one they can find. The general preference order is as follows, with details specified in TS 38.331 [17, clause 5.8.6]: + +- Level 1. Either GNSS or eNB/gNB, according to (pre-)configuration. +- Level 2. A SyncRef UE directly synchronized to a Level 1 source. +- Level 3. A SyncRef UE synchronized to a Level 2 source, i.e. indirectly synchronized to a Level 1 source. +- Level 4. Whichever of GNSS or eNB/gNB was not (pre-)configured as the Level 1 source. +- Level 5. A SyncRef UE directly synchronized to a Level 4 source. +- Level 6. A SyncRef UE synchronized to a Level 5 source, i.e. indirectly synchronized to a Level 4 source. +- Level 7. Any other SyncRef UE. +- Level 8. UE's internal clock. + +The NR V2X scheme is intended to allow the merging of otherwise-separate hierarchies derived from GNSS and gNB/eNB, so that a UE is able to move between nearby such hierarchies without loss of sidelink service. However, since it is possible that a gNB/eNB does not itself have synchronization to GNSS, use of Levels 4-6 can be disabled when GNSS is used as Level 1, so that there is no deviation from the hierarchy being derived from GNSS. + +#### 6.2.2.2 S-SSB and SLSS + +S-PSS and S-SSS use the same types of sequence as NR PSS and SSS respectively, i.e. an *M*-sequence and a Gold sequence. When in use, both sequences are transmitted in 127 subcarriers of the S-SSB bandwidth, in the same slots as PSBCH. S-PSS is in the 2nd and 3rd symbols of the slot, S-SSS is in the 4th and 5th symbols, and PSBCH and its DMRS in each of the remaining symbols. The two symbols of each synchronization signal are the same, which allows detectors to benefit from phase tracking between the two symbols. Figure 6.2.2.2-1 shows the contents of a slot containing S-SSB, the frequency location of which is (pre-)configured. + +![Figure 6.2.2.2-1: Contents of a slot containing S-SSB for normal CP. The diagram shows a single slot divided into 14 symbols. The first symbol is PSBCH (blue). The second and third symbols are S-PSS (yellow). The fourth and fifth symbols are S-SSS (green). The sixth through thirteenth symbols are PSBCH (blue). The fourteenth symbol is GUARD (white). A vertical double-headed arrow on the left indicates a height of 132 subcarriers / 11 RBs. A vertical double-headed arrow on the right indicates a height of 127 subcarriers. A horizontal double-headed arrow at the bottom indicates the entire duration is 1 slot.](f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg) + +Figure 6.2.2.2-1: Contents of a slot containing S-SSB for normal CP. The diagram shows a single slot divided into 14 symbols. The first symbol is PSBCH (blue). The second and third symbols are S-PSS (yellow). The fourth and fifth symbols are S-SSS (green). The sixth through thirteenth symbols are PSBCH (blue). The fourteenth symbol is GUARD (white). A vertical double-headed arrow on the left indicates a height of 132 subcarriers / 11 RBs. A vertical double-headed arrow on the right indicates a height of 127 subcarriers. A horizontal double-headed arrow at the bottom indicates the entire duration is 1 slot. + +**Figure 6.2.2.2-1: Contents of a slot containing S-SSB for normal CP. Each PSBCH symbol contains DMRS.** + +S-SSB can be transmitted on one or multiple synchronization carriers. The MIB-V2X is transmitted on PSBCH every 160 ms, and thus S-SSB occurs on the same period. Within a period, there can be multiple transmissions of S-SSB, with the number depending on subcarrier spacing and frequency range. For details refer to TS 38.213 [18, clause 16.1]. + +##### 6.2.2.2.1 SLSSID + +The SLSSID itself conveys information about the synchronization source of the transmitting UE. In general, the further a UE is away from a high-quality source of GNSS or gNB/eNB, the lower quality will be its own synchronization and thus the quality of an SLSS it transmits. There are a series of association rules among SLSS IDs, designed to allow the identification, and propagation through the system of, high-quality synchronization sources. The operation of this procedure is essentially the same as LTE-V2X, described in Clause 5.1.2.2.1, with the main difference that there are 672 SLSS IDs in NR-V2X, divided into 0, 1, ..., 335 for in-coverage indication and 336, ..., 671 for out-of-coverage indication. The special SLSS IDs of 0, 336, and 337 in NR-V2X are used equivalently to 0, 168, and 169 respectively in LTE-V2X. + +### 6.2.3 Sidelink CSI + +To provide the Tx UE with information it can use for sidelink link adaptation and rank adaptation in unicast transmissions, the Tx UE can configure aperiodic sidelink CSI reporting from the Rx UE. CQI and RI are reported via MAC layer signalling, in a PSSCH transmission. Calculation of the reported values is performed on sidelink CSI-RS from the Tx UE, which are a simplified subset of the Uu CSI-RS design, suitable for 1 or 2 antenna ports. The CSI report is transmitted by the Rx UE within a latency bound that is configured via PC5-RRC by the Tx UE, to ensure the report is timely with respect to the latency characteristic of the Tx UE's data traffic. The Tx UE must wait to trigger the next CSI report from a given Rx UE until the preceding report has been received, or its latency bound has expired. + +### 6.2.4 Sidelink HARQ + +NR-V2X supports HARQ based on transmission of ACK/NACK (or DTX) for sidelink unicast and groupcast services, as well as a NACK-only HARQ scheme particular to groupcast services. In addition, it supports blind re-transmission schemes, which are described in clauses 6.3.2.1 and 6.3.2.2 on resource allocation modes 1 and 2, respectively. + +When ACK/NACK (or DTX) operation is used, the sidelink HARQ procedure is similar to the Uu scheme for non-codeblock group feedback, i.e. the HARQ feedback is transmitted based on the success or failure of the whole transport block. + +NACK-only operation is defined for groupcast to allow a potentially lower sidelink resource demand to be created when a larger number of Rx UEs need to send feedback to the same Tx UE. A typical use case is an extended sensors scenario where UEs within a given radius all receive the same sensor information from the Tx UE, and re-transmission will occur if any UE fails to decode successfully. Since such information may only be relevant within a given radius around the Tx UE (e.g. a few tens or hundreds of meters around a road junction), the transmission of NACK-only feedback can be restricted to UEs within such a radius, and any UE beyond it does not provide any HARQ feedback. The minimum range requirement of a service is provided together with the associated QoS parameters from service layers. + +One bit of sidelink HARQ feedback is carried on PSFCH from an Rx UE to its Tx UE. In addition, when under the control of a gNB in resource allocation mode 1, the Tx UE informs the gNB via PUCCH or PUSCH of the status of the sidelink HARQ feedback it has computed related to a particular dynamic or configured grant to assist the scheduling of re-transmissions and allocation of sidelink resources. + +### 6.2.5 Coexistence between LTE-V2X and NR-V2X sidelinks + +#### 6.2.5.1 In-device coexistence + +It is envisaged that there will exist devices that support both LTE-V2X and NR-V2X, and which will be operating in both systems concurrently. If the two RATs are widely spaced in frequency, e.g. being in different bands, then there need be no particular issues to consider since it is assumed that a separate RF chain will be provided for each band. + +If, however, a sufficiently close frequency spacing is deployed, then it is desirable to enable a single RF chain to be used in the implementation, and also to adhere to the sidelink half-duplex principle established in LTE-V2X, i.e. that the UE is not required to simultaneously transmit and receive on sidelink. The former constraint means that interference between the two RATs' receptions can occur in the device if they are placed sufficiently close together in the frequency domain, and that simultaneous transmission on both RATs is prevented by the UE's single power budget. The latter constraint implies that one RAT cannot be received/transmitted while the other RAT is doing the opposite. + +It is possible to (pre-)configure the resource pools for the two sidelinks such that overlapping is avoided entirely. When this is not arranged, the general rule is that (at least) one of the RATs may be dropped at times when both occur + +simultaneously, but that in some cases where the priority of the V2X service on both RATs is known, the higher priority one is automatically selected: + +- Receive/receive overlap handling is always left to UE implementation decision. +- Transmit/transmit overlap handling and transmit/receive overlap handling will automatically select the RAT with the highest priority service if both priorities are known. If the priorities are equal or not both known, the handling is left to UE implementation to decide. + +In the above rules, the priority of transmission and reception of sidelink synchronization signals/channels is set by (pre-)configuration and that of PSFCH is the same as the corresponding PSSCH. + +#### 6.2.5.2 Dynamic resource pool sharing + +For devices which contain both LTE-V2X and NR-V2X modules, there is support for the NR module to make use of information obtained from the LTE module's mode 4 resource allocation procedure in the NR mode 2 resource allocation procedure, when the subcarrier spacing of NR-V2X is 15 or 30 kHz. + +In this feature, the NR module additionally excludes from its resource selection window resources which, according to LTE-V2X mode 4 information, are considered occupied by LTE-V2X transmissions by the same or other LTE-V2X UEs, as well as resources in which a NR PSCCH/PSSCH transmission would result in a corresponding PSFCH in such LTE resources. Occupancy can be determined according to relative priority between LTE-V2X and NR-V2X traffic, SL-RSRP, periodicity of LTE-V2X, and resources in which the LTE-V2X module did not sense. + +There are similar steps as with NR's own resource selection to expand the candidate resource set if insufficient resources are found to be present. + +### 6.2.6 Concurrent operation and carrier aggregation + +NR-V2X operation is defined in bands n38, n47 and n79 in TS 38.101-1 [22, clause 5.2E], which support single-carrier operation: + +**Table 6.2.6-1: NR-V2X operating bands** + +| V2X Operating Band | Sidelink (SL) Transmission operating band | | Sidelink (SL) Reception operating band | | Duplex Mode | Interface | +|--------------------|------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------------------------|----------------------|-------------|-----------| +| | F UL_low | F UL_high | F DL_low | F DL_high | | | +| n14 2 | 788 MHz | 798 MHz | 788 MHz | 798 MHz | HD | PC5 | +| n38 1 | 2570 MHz | 2620 MHz | 2570 MHz | 2620 MHz | HD | PC5 | +| n47 | 5855 MHz | 5925 MHz | 5855 MHz | 5925 MHz | HD | PC5 | +| n79 | 4400 MHz | 5000 MHz | 4400 MHz | 5000 MHz | HD | PC5 | +| Note 1: | When this band is used for V2X SL service, the band is exclusively used for NR V2X in particular regions. | | | | | | +| Note 2: | When this band is used for public safety service, the NR band is operated with both in-coverage scenarios and out-of-coverage scenarios. | | | | | | + +The NR-V2X sidelink in band n38 can be operated concurrently with LTE Uu band 20. The NR-V2X sidelink in band n47 can be operated concurrently with Uu bands 1, 3, 5, 8, 34, 39, 40, 41, n1, n3, n5, n8, n34, n39, n40, n41, n71, n78, and n79. The NR-V2X sidelink in band n79 can be operated concurrently with Uu band n79. + +Sidelink CA is defined for resource allocation mode 2, in band n47. When operating in CA, a given (sidelink) MAC PDU is transmitted, and if necessary re-transmitted, on a single sidelink carrier, and multiple MAC PDUs can be transmitted in parallel on different carriers. This provides a throughput gain in a similar way as for Uu CA. + +Sidelink CA uses the sensing procedure described in Clause 6.3.2.2 to select resources independently on each involved carrier. The same carrier is used for all MAC PDUs of the same sidelink process at least until the process triggers resource re-selection. + +The carrier(s) that can be used for transmitting data for a destination L2 ID are provided by the V2X layer per QoS flow. The V2X layer provides multiple carriers associated to a service type with QoS flow to carrier mapping information to the AS for all cast types. For groupcast and broadcast, TX profile is used to indicate whether the transmission corresponding to the service type is backward compatible or not. + +Carrier selection is performed at the MAC layer, depending on the CBR measurement of the allowed carriers associated to the logical channel priority. For unicast, CA related UE capability is exchanged between the TX UE and RX UE, and the TX UE delivers the carrier configuration to the RX UE in PC5-RRC. + +Sidelink synchronization can also operate on multiple carriers, as mentioned in Clause 6.2.2.2. A SyncRef UE uses a single synchronization reference for all aggregated carriers, and may transmit S-SSB on one or multiple of them according to capability. A receiving UE likewise uses the same synchronization reference (not necessarily a SyncRef UE) for all its aggregated carriers, and it uses the highest priority synchronization reference present among the available synchronization carriers. + +Another form of CA is PDCP duplication, where the same PDCP packet is transmitted in parallel on multiple sidelink carriers, to increase reliability. See Clause 6.5.8 for more discussion. + +## 6.3 V2X sidelink resource allocation + +### 6.3.1 Sidelink bandwidth parts and resource pools + +#### 6.3.1.1 Sidelink bandwidth parts + +BWPs are defined for the sidelink in a similar way as for UL/DL, to provide a convenient way to specify aspects relating to a UE's RF hardware chain implementation. A UE is configured with one active sidelink BWP when in connected mode to a gNB, which is the same as the single sidelink BWP used for idle mode or out-of-coverage operation. + +The subcarrier spacing used on sidelink is provided in the sidelink BWP (pre-)configuration, from the same set of values and associations to frequency ranges as for the Uu interface (i.e. 15, 30, or 60 kHz for FR1; and 60 or 120 kHz for FR2). Sidelink transmission and reception for a UE are thus contained within a sidelink BWP, and the same sidelink BWP is used for both transmitting and receiving. This means that resource pools, S-SSB, etc. must also be contained within an appropriate sidelink BWP from the UE's perspective. + +#### 6.3.1.2 Resource pools + +PSCCH and PSSCH resources are defined within resource pools for the respective channels. This concept is used because in general PSCCH/PSSCH cannot be transmitted (and thus are not expected to be received) in all RBs and slots in the NR system bandwidth, nor within the frequency span configured for V2X sidelink. The notion of a resource pool also reflects, in resource allocation mode 2, that a UE will make its resource selections based on sensing within the pool. + +A resource pool is divided into sub-channels in the frequency domain, which are consecutively non-overlapping sets of $\geq 10$ PRBs in a slot, the size depending on (pre-)configuration. Resource allocation, sensing, and resource selection are performed in units of a sub-channel. The UE's PSCCH occupies a (pre-)configurable number of PRBs within one sub-channel, starting from the lowest PRB of the PSSCH it schedules. + +Within the slots that can be used for PSSCH transmission, there can be from 7 to 14 of the symbols reserved for sidelink operation, of which PSSCH can be transmitted in 5 to 12 symbols. The remaining sidelink symbols transmit some or all of PSCCH, PSFCH, AGC symbol(s), guard symbol(s). Refer to Figure 6.2.1-1 for examples of slot formats. + +Resource pools are (pre-)configured to a UE separately from the transmission perspective (TX pools) and the reception perspective (RX pools). This allows a UE to monitor for PSCCH, and hence receive PSSCH transmissions, in resource pools other than those in which it transmits, so that it can attempt to receive transmissions made by other UEs in those RX pools. + +In addition, there are exceptional resource pools configured to a UE, in its serving cell's broadcast or in dedicated signalling. These can be used e.g. during RLF in some cases, handover, transition from RRC IDLE to RRC CONNECTED, or during change of dedicated V2X sidelink resource pools within a cell. In these cases, a UE may not have a stable configuration of TX resource pools but nevertheless should not be removed from the V2X system, and so it can randomly select resources in the exceptional pool, and use them temporarily. Likewise, UEs need to monitor the exceptional TX pools for PSCCH transmissions. + +### 6.3.2 Resource allocation modes + +#### 6.3.2.1 Mode 1 + +Mode 1 is for resource allocation by gNB. As described in Clause 4, the use cases intended for NR V2X can generate a diverse array of periodic and aperiodic message types. Therefore, resource allocation mode 1 provides dynamic grants of sidelink resources from a gNB, as well as grants of periodic sidelink resources configured semi-statically by RRC, termed sidelink configured grants. + +A dynamic sidelink grant DCI can provide resources for one or multiple transmissions of a transport block, in order to allow control of reliability. The transmission(s) can be subject to the sidelink HARQ procedure, if that operation is enabled. + +A sidelink configured grant can be such that it is configured once and can be used by the UE immediately, until it is released by RRC signalling (known as Type 1). A UE is allowed to continue using this type of sidelink configured grant when beam failure or physical layer problems occur in NR Uu until an RLF detection timer expires, before falling back to an exception resource pool. The other type of sidelink configured grant, known as Type 2, is configured once but cannot be used until the gNB sends the UE a DCI indicating it is now active, and only until another DCI indicates deactivation. The resources in both types are a set of sidelink resources recurring with a periodicity which a gNB will desire to match to the characteristics of the V2X traffic. Multiple configured grants can be configured, to allow provision for different services, traffic types, etc. + +MCS information for dynamic and configured grants can optionally be provided or constrained by RRC signalling instead of the traditional DCI. RRC can configure the exact MCS the Tx UE uses, or a range of MCS. It may also be left unconfigured. For the cases where RRC does not provide the exact MCS, the transmitting UE is left to select an appropriate MCS itself based on the knowledge it has of the TB to be transmitted and, potentially, the sidelink radio conditions. + +The gNB scheduling activity is driven by the UE reporting its sidelink traffic characteristics to the gNB, or by performing a sidelink BSR procedure similar to that on Uu to request a sidelink resource allocation from gNB. + +#### 6.3.2.2 Mode 2 + +Mode 2 is for UE autonomous resource selection. Its basic structure is of a UE sensing, within a (pre-)configured resource pool, which resources are not in use by other UEs with higher-priority traffic, and choosing an appropriate amount of such resources for its own transmissions. Having selected such resources, the UE can transmit and re-transmit in them a certain number of times, or until a cause of resource reselection is triggered. + +The mode 2 sensing procedure can select and then reserve resources for a variety of purposes reflecting that NR V2X introduces sidelink HARQ in support of unicast and groupcast in the physical layer. It may reserve resources to be used for a number of blind (re-)transmissions or HARQ-feedback-based (re-)transmissions of a transport block, in which case the resources are indicated in the SCI(s) scheduling the transport block. Alternatively, it may select resources to be used for the initial transmission of a later transport block, in which case the resources are indicated in an SCI scheduling a current transport block, in a manner similar to the LTE-V2X scheme (clause 5.2.2.2). Finally, an initial transmission of a transport block can be performed after sensing and resource selection, but without a reservation. + +The first-stage SCIs transmitted by UEs on PSCCH indicate the time-frequency resources in which the UE will transmit a PSSCH. These SCI transmissions are used by sensing UEs to maintain a record of which resources have been reserved by other UEs in the recent past. When a resource selection is triggered (e.g. by traffic arrival or a re-selection trigger), the UE considers a sensing window which starts a (pre-)configured time in the past and finishes shortly before the trigger time. The window can be either 1100 ms or 100 ms wide, with the intention that the 100 ms option is particularly useful for aperiodic traffic, and 1100 ms particularly for periodic traffic. A sensing UE also measures the SL-RSRP in the slots of the sensing window, which implies the level of interference which would be caused and experienced if the sensing UE were to transmit in them. In NR-V2X, SL-RSRP is a (pre-)configurable measurement of either PSSCH-RSRP or PSCCH-RSRP. + +The sensing UE then selects resources for its (re-)transmission(s) from within a resource selection window. The window starts shortly after the trigger for (re-)selection of resources, and cannot be longer than the remaining latency budget of the packet due to be transmitted. Reserved resources in the selection window with SL-RSRP above a threshold are excluded from being candidates by the sensing UE, with the threshold set according to the priorities of the traffic of the sensing and transmitting UEs. Thus, a higher priority transmission from a sensing UE can occupy resources which are reserved by a transmitting UE with sufficiently low SL-RSRP and sufficiently lower-priority traffic. + +If the set of resources in the selection window which have not been excluded is less than a certain proportion of the available resources within the window, the SL-RSRP exclusion threshold is relaxed in 3 dB steps. The proportion is set by (pre-)configuration to 20%, 35%, or 50% for each traffic priority. The UE selects an appropriate amount of resources randomly from this non-excluded set. The resources selected are not in general periodic. Up to three resources can be indicated in each SCI transmission, which can each be independently located in time and frequency. When the indicated resources are for semi-persistent transmission of another transport block, the range of supported periodicities is expanded compared to LTE-V2X, in order to cover the broader set of envisioned use cases in NR-V2X. + +Shortly before transmitting in a reserved resource, a sensing UE re-evaluates the set of resources from which it can select, to check whether its intended transmission is still suitable, taking account of late-arriving SCIs due, typically, to an aperiodic higher-priority service starting to transmit after the end of the original sensing window. If the reserved resources would not be part of the set for selection at this time ( $T3$ ), then new resources are selected from the updated resource selection window. The cut-off time $T3$ is long enough before transmission to allow the UE to perform the calculations relating to resource re-selection. + +The timeline of the sensing and resource (re-)selection windows with respect to the time of trigger $n$ , are shown in Figure 6.3.2.2-2(a), and the effect of the possibility of re-evaluation before first use of the reservation in Figure 6.3.2.2-2(b). + +There are a number of triggers for resource re-selection, several of which are similar to LTE-V2X in Clause 5.2.2.2. In addition, there is the possibility to configure a resource pool with a pre-emption function designed to help accommodate aperiodic sidelink traffic, so that a UE reselects all the resources it has already reserved in a particular slot if another nearby UE with higher priority indicates it will transmit in any of them, implying a high-priority aperiodic traffic arrival at the other UE, and the SL-RSRP is above the exclusion threshold. The application of pre-emption can apply between all priorities of data traffic, or only when the priority of the pre-empting traffic is higher than a threshold and higher than that of the pre-empted traffic. A UE does not need to consider the possibility of pre-emption later than time $T3$ before the particular slot containing the reserved resources. + +![Flowchart of sensing and resource (re-)selection procedures. The process starts with 'Keep decoding other UE's PSCCH and measuring corresponding PSCH energy', followed by 'Collect sensing information including reserved resources and SL-RSRP measurements', 'Exclude own, and high-energy resources, and form candidate resource set', 'Select Tx resource semi-persistently, or up to maximum reservations, with start time 'm'', and 'Re-evaluate resource selection'. A decision diamond 'Re-selection triggered?' leads to 'Begin transmitting' if YES, or loops back to 'Collect sensing information' if NO. Another decision diamond 'Resource re-selection?' follows 'Begin transmitting', leading to 'Restart process' if YES, or loops back to 'Begin transmitting' if NO - Continue using reservation.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +graph TD + A[Keep decoding other UE's PSCCH and measuring corresponding PSCH energy] --> B[Collect sensing information including reserved resources and SL-RSRP measurements] + B --> C[Exclude own, and high-energy resources, and form candidate resource set] + C --> D[Select Tx resource semi-persistently, or up to maximum reservations, with start time 'm'] + D --> E[Re-evaluate resource selection] + E --> F{Re-selection triggered?} + F -- YES --> G[Begin transmitting] + F -- NO --> B + G --> H{Resource re-selection?} + H -- YES - Restart process --> B + H -- NO - Continue using reservation --> G + +``` + +Flowchart of sensing and resource (re-)selection procedures. The process starts with 'Keep decoding other UE's PSCCH and measuring corresponding PSCH energy', followed by 'Collect sensing information including reserved resources and SL-RSRP measurements', 'Exclude own, and high-energy resources, and form candidate resource set', 'Select Tx resource semi-persistently, or up to maximum reservations, with start time 'm'', and 'Re-evaluate resource selection'. A decision diamond 'Re-selection triggered?' leads to 'Begin transmitting' if YES, or loops back to 'Collect sensing information' if NO. Another decision diamond 'Resource re-selection?' follows 'Begin transmitting', leading to 'Restart process' if YES, or loops back to 'Begin transmitting' if NO - Continue using reservation. + +Figure 6.3.2.2-1: Summary of sensing and resource (re-)selection procedures + +![Timeline diagram showing sensing and resource (re-)selection procedure. A horizontal timeline has a 'sensing window' ending at time n, followed by a 'selection window'. At time n, there are markers for T_proc,0 and T1. At time m, the first 'reservation(s)' begins. Subsequent reservations are shown as green bars with blue arrows indicating semi-persistent reservations. The total duration from the start to the end of the selection window is labeled T0 and T2, with the constraint T2, T_min ≤ T2 ≤ remaining PDB.](97d95cd0cbe6c0c801edb6a4aaa5fc1c_img.jpg) + +Timeline details: The sensing window ends at time $n$ . Processing time $T_{proc,0}$ and interval $T_1$ are marked at $n$ . The selection window starts at $n$ and ends at $m$ . The first reservation is at $m$ . Subsequent reservations are indicated by blue arrows. The total duration is $T_2$ , where $T_2, T_{min} \leq T_2 \leq \text{remaining PDB}$ . + +Timeline diagram showing sensing and resource (re-)selection procedure. A horizontal timeline has a 'sensing window' ending at time n, followed by a 'selection window'. At time n, there are markers for T\_proc,0 and T1. At time m, the first 'reservation(s)' begins. Subsequent reservations are shown as green bars with blue arrows indicating semi-persistent reservations. The total duration from the start to the end of the selection window is labeled T0 and T2, with the constraint T2, T\_min ≤ T2 ≤ remaining PDB. + +Figure 6.3.2.2-2(a): Timeline of sensing and resource (re-)selection procedure triggered at time $n$ , without re-evaluation before $(m-T_3)$ . Its first reserved resource is at time $m$ . + +![Figure 6.3.2.2-2(b): Timeline of sensing and resource (re-)selection procedure. A horizontal timeline shows a 'sensing window' ending at time n. A 're-selection window' starts at time n and ends at time m'. A resource is reserved at time m. A re-evaluation occurs at time m' - T3. The new re-evaluation cut-off becomes (m' - T3). The diagram shows a resource at time m being re-evaluated at time m' - T3, and if no longer selectable, a new resource is reserved at time m'.](dd5771673aececa53d42ece89218299d_img.jpg) + +Figure 6.3.2.2-2(b): Timeline of sensing and resource (re-)selection procedure. A horizontal timeline shows a 'sensing window' ending at time n. A 're-selection window' starts at time n and ends at time m'. A resource is reserved at time m. A re-evaluation occurs at time m' - T3. The new re-evaluation cut-off becomes (m' - T3). The diagram shows a resource at time m being re-evaluated at time m' - T3, and if no longer selectable, a new resource is reserved at time m'. + +Figure 6.3.2.2-2(b): Timeline of sensing and resource (re-)selection procedure originally triggered at time $n$ , which has a first reserved resource at time $m$ , when re-evaluation occurring at $m-T3$ determines the resources are no longer selectable. The new re-evaluation cut-off becomes $(m'-T3)$ . + +## 6.4 Sidelink congestion control + +Congestion control for NR-V2X is similar to that described in Clause 5.3 for LTE-V2X, and it likewise is used in resource allocation mode 2 in NR. The main differences are that each packet is associated with a single 'priority' value, passed down to the physical layer from upper layers, which is comparable to PPPP in LTE-V2X. The priority value is transmitted in the first-stage SCI associated with each transport block. Broadly equivalent measurements of CBR and CR, together with CR-limits are defined, which can be used similarly to constrain the ranges of transmission parameters. NR V2X sets a shorter time of 1 ms or 2 ms in which the UE must calculate the CR and CBR than LTE-V2X's 4 ms, with the aim of adapting to faster fluctuations in congestion due to aperiodic traffic. + +## 6.5 V2X sidelink higher-layer protocols + +### 6.5.1 General + +Figure 6.5.1-1 shows the user plane protocol stack for NR sidelink communication. The AS protocol stack of user plane in the PC5 interface consists of SDAP, PDCP, RLC, MAC, and the physical layer as shown below in Figure 6.5.1-1, from TS 38.300 [20, Clause 16.9.2.1]. + +![Figure 6.5.1-1: User plane protocol stack for STCH. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a stack of five protocols: SDAP, PDCP, RLC, MAC, and PHY. Horizontal arrows connect the corresponding protocol layers between UE A and UE B, indicating bidirectional communication.](17a1ba23b641c01871b08f0a4f08ef48_img.jpg) + +Figure 6.5.1-1: User plane protocol stack for STCH. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a stack of five protocols: SDAP, PDCP, RLC, MAC, and PHY. Horizontal arrows connect the corresponding protocol layers between UE A and UE B, indicating bidirectional communication. + +Figure 6.5.1-1: User plane protocol stack for STCH. + +Figure 6.5.1-2 shows the control plane protocol stack for SCCH for RRC for NR sidelink communication. The AS protocol stack of the control plane for SCCH for RRC in the PC5 interface consists of RRC, PDCP, RLC, MAC and the physical layer as shown below in Figure 6.5.1-2, from TS 38.300 [20, Clause 16.9.2.1]. + +![Figure 6.5.1-2: Control plane (PC5-C) protocol stack for SCCH for RRC. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of five protocol layers: RRC, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the RRC layer of UE A to the RRC layer of UE B, the PDCP layer of UE A to the PDCP layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Figure 6.5.1-2: Control plane (PC5-C) protocol stack for SCCH for RRC. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of five protocol layers: RRC, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the RRC layer of UE A to the RRC layer of UE B, the PDCP layer of UE A to the PDCP layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B. + +**Figure 6.5.1-2: Control plane (PC5-C) protocol stack for SCCH for RRC.** + +Figure 6.5.1-3 shows the control plane protocol stack for PC-S. PC5-S is located on top of PDCP, RLC and MAC sublayers, and the physical layer for the control plane in the PC5 interface as shown in Figure 6.5.1-3, from TS 38.300 [20, Clause 16.9.2.1]. + +![Figure 6.5.1-3: Control plane (PC5-C) protocol stack for SCCH for PC5-S. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of five protocol layers: PC5-S, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the PC5-S layer of UE A to the PC5-S layer of UE B, the PDCP layer of UE A to the PDCP layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) + +Figure 6.5.1-3: Control plane (PC5-C) protocol stack for SCCH for PC5-S. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of five protocol layers: PC5-S, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the PC5-S layer of UE A to the PC5-S layer of UE B, the PDCP layer of UE A to the PDCP layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B. + +**Figure 6.5.1-3: Control plane (PC5-C) protocol stack for SCCH for PC5-S.** + +The AS protocol stack for SBCCH in the PC5 interface consists of RRC, RLC, MAC sublayers, and the physical layer as shown below in Figure 6.5.1-4, from TS 38.300 [20, Clause 16.9.2.1]. + +![Figure 6.5.1-4: Control plane protocol stack for SBCCH. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of four protocol layers: RRC, RLC, MAC, and PHY. Horizontal double-headed arrows connect the RRC layer of UE A to the RRC layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B.](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +Figure 6.5.1-4: Control plane protocol stack for SBCCH. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of four protocol layers: RRC, RLC, MAC, and PHY. Horizontal double-headed arrows connect the RRC layer of UE A to the RRC layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B. + +**Figure 6.5.1-4: Control plane protocol stack for SBCCH.** + +### 6.5.2 Measurement and reporting related to NR sidelink communication + +Some measurement and reporting mechanisms are supported specifically for NR sidelink communication, including CBR measurement and reporting to NG-RAN, reporting of location information to NG-RAN, and L3-filtered RSRP measurement and reporting in PC5 interface. + +To provide some information to assist network's scheduling and/or transmission parameter adjustment, CBR measurement and reporting is performed for the RRC\_CONNECTED UEs. + +To provide the Tx UE with information it can use for open loop power control in unicast transmissions, the Rx UE can perform RSRP measurement based on DMRS and report the L3-filtered RSRP to the Tx UE. + +Details of the measurement and reporting mechanism specific for NR sidelink communication are specified in TS 38.331 [17, clause 5.5]. + +### 6.5.3 Mobility management for NR SL transmission/reception + +UE can perform NR sidelink transmission and reception during handover and cell reselection. During handover, sidelink transmission and reception are performed based on configuration of the exceptional transmission resource pool or sidelink configured grant Type 1 and reception resource pool of the target cell as provided in the handover command. + +Related details are specified in TS 38.331 [17, clause 5.8.8]. + +### 6.5.4 Assistance information and SL configured grant configuration + +NG-RAN can allocate sidelink resources to UE with two types of sidelink configured grants (Type 1 and Type 2). For the UE performing NR sidelink communication, there can be more than one sidelink configured grant activated at a time on the carrier configured for sidelink transmission. + +To provide assistant information for the configuration of configured grant, UE assistance information on traffic pattern can be reported to the network. The periodicity, time offset, message size, QoS info and destination can be included in the reporting message. + +### 6.5.5 Coordination between UL and NR SL transmission + +NR-UL/NR-SL prioritization is performed when the following scenarios occur: + +- when UL TX overlaps in time domain with SL TX in the shared/same carrier frequency; +- when UL TX and SL TX (in different carrier frequency) share TX chains and power budget; + +To support NR-UL/NR-SL prioritization, a separate LCH priority threshold is configured for both NR-UL and NR-SL. For SL data and UL data/SRB, the SL transmission is prioritized if the highest priority value of UL LCH(s) with available data is larger than the UL priority threshold and the highest priority value of SL LCH(s) with available data is lower than the SL priority threshold, otherwise the UL transmission is prioritized. Details of the prioritization between UL transmission and NR sidelink transmission are specified in TS 38.321 [21, clause 5.22.1.3.1a]. + +The physical layer also provides prioritization and multiplexing rules between NR UL and NR SL when their transmissions would overlap, using rules similar to those from the Uu interface and relying on the priorities of the respective transmissions. + +### 6.5.6 QoS mechanism + +For NR sidelink communication, per flow based QoS model is used for sidelink unicast, groupcast and broadcast. + +For RRC\_CONNECTED UEs, the UE may report the QoS information of the PC5 QoS flow via RRC dedicated signalling for transmission of a new PC5 QoS flow, and the network may provide SLRB configurations and configure the mapping of PC5 QoS flow to SLRB via RRC dedicated signalling, based on the QoS information reported by the UE. + +For RRC\_IDLE/INACTIVE UEs, the network may provide SLRB configurations and configure the PC5 QoS profile to SLRB mapping via V2X-specific SIB. + +For out of coverage UEs, SLRB configurations and the mapping of PC5 QoS profile to SLRB can be pre-configured or provided via V2X-specific SIB of the cell on the frequency which provides inter-carrier NR sidelink configuration. + +### 6.5.7 Sidelink RRC + +For unicast NR sidelink communication, the PC5-RRC connection is a logical connection between a pair of source and destination L2 IDs. + +The AS layer configuration including the parameters which need to be aligned between Tx UE and Rx UE can be conveyed via PC5 RRC signalling. In case AS layer configuration fails, both explicit failure message and timer based indication can be considered to be used to indicate the failure to the peer UE. + +UE capability can be interacted between pair UEs via PC5 RRC. A UE can send Capability Enquiry message to request peer UE's capability along with its own capability information. When to include its own capabilities is up to UE implementation. + +Moreover, SL RLM/RLF is supported for unicast NR sidelink communication. Upon RL RLF declaration, the UE releases the PC5 RRC connection immediately and sends an indication to upper layer. For RRC\_CONNECTED UEs, the UE also informs the network via sidelink UE information upon RLF is detected. + +Details of the sidelink RRC procedures for NR sidelink communication are specified in TS 38.331 [17, clause 5.8.9]. + +### 6.5.8 Sidelink packet duplication + +Packet duplication is supported for sidelink and is performed at PDCP layer. The duplicated PDCP PDUs of the same PDCP entity are only allowed to be transmitted on different sidelink carriers. + +## 6.6 V2X via the Uu interface + +Some advanced V2X services are provided by an application server residing in the Internet which processes information received from the UE and issues instructions back to control the vehicle. Such applications can allow a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive themselves. Other services, termed advanced driving, can incorporate video sharing among vehicles via an application server. In such applications, the communication is UE to/from the server via a cellular network's NR Uu interface. + +Therefore, the Uu interface can activate multiple PUSCH configured grants (which are periodical resource grants configured by RRC, similar to LTE SPS in clause 5.5) simultaneously so that traffic sources with different requirements on latency, reliability, etc. can be handled at the same time. It is also possible for a PUSCH configured grant to send more than one PUSCH repetition in a slot or across a slot boundary, for the purpose of reducing UL latency. + +## 6.7 Network aspects + +### 6.7.1 V2X service authorization + +Similarly as LTE V2X, the NG-RAN node receives the authorization status of the UE provided by a Core Network or a neighbour NG-RAN node, to know whether the UE is authorized as a Vehicle UE and/or a Pedestrian UE. Only the authorized UEs can perform V2X sidelink communication. Sidelink radio resources are provided to UEs in different ways according to the different services supported. + +### 6.7.2 Alternative QoS profiles + +A list of alternative QoS parameter sets may be provided additionally for a GBR QoS Flow with Notification control enabled by the SMF to the NG-RAN node, or by the source NG-RAN node to the target NG-RAN node during handover. + +The NG-RAN node, or the target NG-RAN node during handover, checks the requested QoS profile and the list of alternative QoS parameter sets. If one of the alternative QoS parameter sets can be fulfilled, it then indicates a reference to the fulfilled alternative QoS parameters set to the SMF and/or the source NG-RAN node. + +## 6.8 Inter-UE coordination + +NR-V2X UEs may exchange information with one another over sidelink which can aid the resource allocation mode 2 (re-)selection procedure. + +There are two schemes for doing so, where UE-B has a sidelink transmission to perform and receives coordination information from UE-A: + +1. A UE-A can provide to another UE-B indications of resources that are preferred to be included in UE-B's (re-)selected resources, or preferred to be excluded. When given resources to include, UE-B may rely only on those resources, at least if it does not support sensing/resource exclusion, or may combine them with resources identified by its own sensing procedure, before making a final selection. + +Transmissions of, and requests for, coordination information are sent by UE-A or UE-B, respectively, in a MAC-CE and may also, if the UE supports the function, be sent in a 2nd-stage SCI. Coordination information can be in response to a request from UE-B, or due to an internal cause at UE-A. A request is sent in unicast to UE-A, which responds also in unicast. When due to an internal cause, UE-A uses unicast to indicate resources preferred to be included, and unicast, groupcast or broadcast to indicate resources preferred to be excluded. + +2. A UE-A can provide to another UE-B an indication that resources reserved for UE-B's transmission (which may or may not be to UE-A) will be, or could be, subject to conflict with a transmission from another UE. UE-B can then re-select new resources to replace them. + +The indication from UE-A is a PSFCH sent to UE-B in resources which are (pre-)configured separately from those for SL-HARQ operation, and from which UE-B can derive which of its transmissions is indicated for re-selection. + +In both schemes, UE-A can identify resources according to a number of conditions which are based on the SL-RSRP of the resources in question as a function of the traffic priority, and/or whether UE-A would be unable to receive a transmission from UE-B, due to performing its own transmission, i.e. a half-duplex problem. The purpose of this exchange of information is to give UE-B information about resource occupancy acquired by UE-A which it might not be able to determine on its own due to hidden nodes, exposed nodes, persistent collisions, etc. + +# --- 7 Multi-RAT V2X + +## 7.1 Cross-RAT operation + +It is envisaged that NR-V2X and LTE-V2X will be at least initially deployed in similar timeframes, and also during a time when MNOs may have either or both of NR and LTE cellular networks available. An optional UE design response to this is supported where a device has both an LTE-V2X RAT and an NR-V2X RAT which are able to inter-communicate. This would enable the UE to perform sidelink communications with other UEs which implement only one of the sidelinks, and to do so whether they are in a cellular network of LTE or NR. Hence, for example, an LTE cellular network can be involved in controlling the NR sidelink via such dual-mode UEs, and an NR cellular network can similarly be involved in controlling LTE sidelink UEs. + +LTE Uu can control NR resource allocation mode 1 by providing configured grant Type 1 configurations via LTE RRC signalling. This allows provision of periodically occurring sets of NR resources for the NR sidelink – see Clause 6.3.2.1. Control of NR resource allocation mode 2 is by LTE Uu RRC providing the semi-static configurations relevant to resource pools, sensing, etc. within which the NR-V2X RAT autonomously selects resources for sidelink transmission. + +NR Uu can control LTE resource allocation mode 3 by transmitting an NR DCI which contains the information needed to dynamically control the LTE sidelink. The UE transfers this information internally to its LTE RAT, for which a certain amount of processing time is allowed, and then follows normal LTE sidelink procedures. Control of LTE resource allocation mode 4 is by NR Uu RRC providing the necessary semi-static configurations within which the LTE-V2X RAT autonomously selects resources for sidelink transmission. + +Two separate sets of information for V2X services authorization can be signalled, i.e., the NR V2X Services Authorized IE, and the LTE V2X Services Authorized IE. These can be provided over the NG, S1, Xn, X2, and F1 interfaces, from the Core Network to the RAN node, between RAN nodes, and from gNB-CU to gNB-DU. + +## 7.2 MR-DC + +The scenarios for LTE V2X sidelink communication and NR sidelink communication are captured in the following figures. The scenarios can be categorized into standalone and MR-DC scenarios, according to TS 37.340 [19], regarding the architecture. + +Figure 7.2-1, Figure 7.2-2 and Figure 7.2-3 illustrate the standalone scenarios to support LTE V2X sidelink communication and NR sidelink communication. Particularly: + +- 1) In scenario 1, a gNB provides control/configuration for a UE's V2X communication in both LTE SL and NR SL; +- 2) In scenario 2, an ng-eNB provides control/configuration for a UE's V2X communication in both LTE SL and NR SL; +- 3) In scenario 3, an eNB provides control/configuration for a UE's V2X communication in both LTE SL and NR SL. + +![Figure 7.2-1: Scenario 1 diagram](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +Diagram illustrating Scenario 1: A 5GC (5G Core) connected to an NR (New Radio) base station (gNB). Two UEs (User Equipment) are shown, connected to the gNB via Uu interfaces. The UEs are communicating via NR V2X SL (NR V2X Sidelink) and LTE V2X SL (LTE V2X Sidelink) interfaces. + +Figure 7.2-1: Scenario 1 diagram + +Figure 7.2-1: Scenario 1 + +![Figure 7.2-2: Scenario 2 diagram](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) + +Diagram illustrating Scenario 2: A 5GC (5G Core) connected to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) base station (ng-eNB). Two UEs (User Equipment) are shown, connected to the ng-eNB via Uu interfaces. The UEs are communicating via NR V2X SL (NR V2X Sidelink) and LTE V2X SL (LTE V2X Sidelink) interfaces. + +Figure 7.2-2: Scenario 2 diagram + +Figure 7.2-2: Scenario 2 + +![Figure 7.2-3: Scenario 3 diagram](b2ddf2a678bd20b1b491023eb1db6458_img.jpg) + +Diagram illustrating Scenario 3: An EPC (Evolved Packet Core) connected to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) base station (eNB). Two UEs (User Equipment) are shown, connected to the eNB via Uu interfaces. The UEs are communicating via NR V2X SL (NR V2X Sidelink) and LTE V2X SL (LTE V2X Sidelink) interfaces. + +Figure 7.2-3: Scenario 3 diagram + +Figure 7.2-3: Scenario 3 + +Figure 7.2-4, Figure 7.2-5 and Figure 7.2-6 illustrate the MR-DC scenarios to support LTE V2X sidelink communication and NR sidelink communication. For the MR-DC scenario, MN controlling/configuring both NR SL and LTE SL in Scenarios 4, 5 and 6 is covered by Scenarios 1, 2 and 3 respectively. Particularly: + +- 1) In scenario 4, a UE's V2X communication in LTE SL and NR SL is controlled/configured by Uu while the UE is configured with NE-DC; + +- 2) In scenario 5, a UE's V2X communication in LTE SL and NR SL is controlled/configured by Uu while the UE is configured in NGEN-DC; +- 3) In scenario 6, a UE's V2X communication in LTE SL and NR SL is controlled/configured by Uu while the UE is configured in EN-DC. + +![Diagram of Scenario 4: A 5GC cloud is connected to an MgNB (blue) and an SeNB (yellow). Two cars are shown below. The MgNB has a solid arrow to the left car and a dashed arrow to the right car. The SeNB has a solid arrow to the right car and a dashed arrow to the left car. Between the cars, there is a yellow double-headed arrow labeled 'LTE V2X SL' and a blue double-headed arrow labeled 'NR V2X SL'.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +The diagram illustrates Scenario 4. At the top, a cloud labeled '5GC' contains two base stations: 'MgNB' (blue icon) and 'SeNB' (yellow icon). Below, two cars are shown. The MgNB has a solid arrow pointing to the left car and a dashed arrow pointing to the right car. The SeNB has a solid arrow pointing to the right car and a dashed arrow pointing to the left car. Between the two cars, there are two horizontal double-headed arrows: a yellow one labeled 'LTE V2X SL' and a blue one labeled 'NR V2X SL'. + +Diagram of Scenario 4: A 5GC cloud is connected to an MgNB (blue) and an SeNB (yellow). Two cars are shown below. The MgNB has a solid arrow to the left car and a dashed arrow to the right car. The SeNB has a solid arrow to the right car and a dashed arrow to the left car. Between the cars, there is a yellow double-headed arrow labeled 'LTE V2X SL' and a blue double-headed arrow labeled 'NR V2X SL'. + +Figure 7.2-4: Scenario 4 + +![Diagram of Scenario 5: A 5GC cloud is connected to an MeNB (blue) and an SgNB (yellow). Two cars are shown below. The MeNB has a solid arrow to the left car and a dashed arrow to the right car. The SgNB has a solid arrow to the right car and a dashed arrow to the left car. Between the cars, there is a yellow double-headed arrow labeled 'NR V2X SL' and a blue double-headed arrow labeled 'LTE V2X SL'.](ac31fdfebb9751f7f10416dfe33bc872_img.jpg) + +The diagram illustrates Scenario 5. At the top, a cloud labeled '5GC' contains two base stations: 'MeNB' (blue icon) and 'SgNB' (yellow icon). Below, two cars are shown. The MeNB has a solid arrow pointing to the left car and a dashed arrow pointing to the right car. The SgNB has a solid arrow pointing to the right car and a dashed arrow pointing to the left car. Between the two cars, there are two horizontal double-headed arrows: a yellow one labeled 'NR V2X SL' and a blue one labeled 'LTE V2X SL'. + +Diagram of Scenario 5: A 5GC cloud is connected to an MeNB (blue) and an SgNB (yellow). Two cars are shown below. The MeNB has a solid arrow to the left car and a dashed arrow to the right car. The SgNB has a solid arrow to the right car and a dashed arrow to the left car. Between the cars, there is a yellow double-headed arrow labeled 'NR V2X SL' and a blue double-headed arrow labeled 'LTE V2X SL'. + +Figure 7.2-5: Scenario 5 + +![Diagram of Scenario 6: An EPC cloud is connected to an MN (blue) and an SN (yellow). Two cars are shown below. The MN has a solid arrow to the left car and a dashed arrow to the right car. The SN has a solid arrow to the right car and a dashed arrow to the left car. Between the cars, there is a yellow double-headed arrow labeled 'NR V2X SL' and a blue double-headed arrow labeled 'LTE V2X SL'.](409498e57b1f988b2b604d12cd997002_img.jpg) + +The diagram illustrates Scenario 6. At the top, a cloud labeled 'EPC' contains two base stations: 'MN' (blue icon) and 'SN' (yellow icon). Below, two cars are shown. The MN has a solid arrow pointing to the left car and a dashed arrow pointing to the right car. The SN has a solid arrow pointing to the right car and a dashed arrow pointing to the left car. Between the two cars, there are two horizontal double-headed arrows: a yellow one labeled 'NR V2X SL' and a blue one labeled 'LTE V2X SL'. + +Diagram of Scenario 6: An EPC cloud is connected to an MN (blue) and an SN (yellow). Two cars are shown below. The MN has a solid arrow to the left car and a dashed arrow to the right car. The SN has a solid arrow to the right car and a dashed arrow to the left car. Between the cars, there is a yellow double-headed arrow labeled 'NR V2X SL' and a blue double-headed arrow labeled 'LTE V2X SL'. + +Figure 7.2-6: Scenario 6 + +# 8 Transmission profiles + +LTE-V2X was developed over the course of two 3GPP Releases, Rel-14 and Rel-15. In Rel-15, non-backward compatible changes to physical transmission formats were introduced, primarily to support the use of 64-QAM on PSSCH compared to the maximum of 16-QAM in Rel-14. Such transmissions cannot be decoded by Rel-14 UEs. + +However, on sidelink, a transmitting UE cannot know the Release of specifications supported by the UEs which will receive the PSSCH transmission, since the transmission is broadcast in the physical layer. Therefore, the concept of transmission profiles was introduced, which associates to each transmission by a Rel-15 UE a (pre-)configuration of which Release's transmission format to use. A transmitting UE performs transmission format selection based on the profile indicated by higher layer of the 3GPP protocol stack. If a Rel-14 format is indicated, then the transmission can be decoded by both Releases of UE, whereas if Rel-15 format is indicated, it can be decoded only by Rel-15 UEs. When a UE has traffic from different application sources to transmit at the same time, the transmission profile associated with the highest-priority traffic is applied. The association of transmission profiles to traffic sources (specifically, logical channels) is provided by 3GPP protocol layers outside of RAN. + +Transmission profiles are also defined in NR, for the support of sidelink DRX, which was introduced in Rel-17; see Clause 9.3. This is to ensure compatibility for sidelink groupcast and broadcast between UEs supporting and not supporting sidelink DRX, since a receiver UE would miss transmissions sent in its DRX inactive times. Only if all those transmission profiles of interest to the receiver UE correspond to support of sidelink DRX does the UE assume it can be used. Similarly, a transmitting UE only assumes sidelink DRX is used by its groupcast or broadcast receiver UEs when the relevant transmission profile corresponds to support of sidelink DRX. + +# --- 9 Battery-limited UEs + +## 9.1 Power supply + +LTE-V2X, as discussed in Clause 4, and NR-V2X both include communications between Pedestrian UEs and Vehicular UEs, i.e. V2P. Whereas a vehicular UE is assumed to be attached to the vehicle's power supply, and thus to have no particular battery life concerns, the situation is different for a P-UE and, more generally, a vulnerable road user (VRU). A VRU could be, e.g. a conventional smartphone running suitable applications, or a specialised device attached to a pedestrian's clothing, etc. In either case, battery life has to be considered so that the device will provide the V2P or VRU services for a reasonable length of time without need of re-charging, and without imposing such battery drain that associated applications could become unattractive. + +## 9.2 Partial sensing + +As described in Clause 5.2.2.2, a LTE-V2X UE performs sensing continuously in a 1000 ms historical window, implying an amount of ongoing power consumption due to the sensing procedure. It is allowed for a LTE P-UE to not support sidelink reception, so that it is only broadcasting packets relating to its own location and direction. This type of P-UE is allowed, if a resource pool's (pre-)configuration permits, to select transmission resources randomly, with no sensing procedure. For a LTE P-UE which does support sidelink reception, it can be permitted by (pre-)configuration to perform partial sensing. In partial sensing, only a subset of the subframes in the typically 1000 ms sensing window have to be monitored. The LTE UE implementation can choose how few subframes it wishes to monitor, by trading off the reliability of its transmissions with the power saving, subject to monitoring a (pre-)configured minimum number. (Pre-)configuration can also set how far into the past the sensing window extends, and can require that the UE performs partial sensing in a number of these truncated sensing windows. + +In NR-V2X, there are two similar power-saving resource allocation methods which, as well as being applicable to P-UEs and VRUs, are also intended to have applicability to non-V2X applications. As with LTE-V2X, a UE is allowed, if a resource pool's (pre-)configuration permits, to select transmission resources randomly, with no sensing procedure. To retain the higher reliability provided by sidelink HARQ, the resources selected must still obey the constraints of HARQ feedback preparation time, and allow successive re-transmission resources to be signalled in the reach of one SCI. + +For partial sensing in NR-V2X, there is a need to account for the wider set of targeted periodicities, and also for aperiodic traffic. Partial sensing therefore has two parts: periodic-based (PBPS), and contiguous (CPS). PBPS is similar to the LTE-V2X partial sensing, where a UE chooses a set of $Y$ candidate slots, subject to a minimum number, and monitors that set. The UE can be (pre-)configured to monitor the $Y$ slots at least according to a subset or the whole set of periodicities configured in the resource pool. When traffic arrives at slot $n$ , sensing information from either the most recent one, or the most recent two, monitoring occasions of $Y$ slots at each relevant periodicity is used in performing resource (re-)selection. PBPS is designed to provide sufficient sensing information to manage resource allocation for periodic traffic, whilst providing configurability to balance sensing accuracy with power consumption. On its own, PBPS may not be sufficient for detecting aperiodic traffic. For this purpose, CPS is performed in each of at least $M$ sidelink slots ending shortly before the first of the $Y$ candidates. $M$ can be (pre-)configured to balance detection of + +aperiodic SCIs with UE power consumption. An example of this combined PBPS and CPS operation is shown in Figure 9.1. It is also possible for the UE to perform only CPS, if the resource pool does not permit periodic reservations. + +![Figure 9.1: Example of NR partial sensing. The diagram shows a timeline of slots. A vertical dashed line marks slot 'n'. To the left of 'n', there are two sets of periodic transmissions. The first set has red bars with a period of 2xP2. The second set has yellow bars with a period of 2xP1. A blue rectangle labeled 'CPS window (M slots)' ends at slot 'n'. To the right of the CPS window, there are green bars labeled 'Y candidate slots'. A horizontal double-headed arrow labeled '1xP2' spans from a red bar to the start of the CPS window. Another horizontal double-headed arrow labeled '1xP1' spans from a yellow bar to the start of the CPS window. A horizontal double-headed arrow labeled '(re-)selection window' spans from the end of the CPS window to the start of the candidate slots.](04cfca33e3fc26513abe649d7474f733_img.jpg) + +Figure 9.1: Example of NR partial sensing. The diagram shows a timeline of slots. A vertical dashed line marks slot 'n'. To the left of 'n', there are two sets of periodic transmissions. The first set has red bars with a period of 2xP2. The second set has yellow bars with a period of 2xP1. A blue rectangle labeled 'CPS window (M slots)' ends at slot 'n'. To the right of the CPS window, there are green bars labeled 'Y candidate slots'. A horizontal double-headed arrow labeled '1xP2' spans from a red bar to the start of the CPS window. Another horizontal double-headed arrow labeled '1xP1' spans from a yellow bar to the start of the CPS window. A horizontal double-headed arrow labeled '(re-)selection window' spans from the end of the CPS window to the start of the candidate slots. + +**Figure 9.1: Example of NR partial sensing. PBPS of $Y$ candidate slots at two periodicities, $P_1$ and $P_2$ , for the two most recent PBPS occasions before slot $n$ , and CPS for $M$ sidelink slots ending a processing time before the $Y$ candidate slots.** + +For partial sensing applied to periodic transmissions, re-evaluation and pre-emption are also performed before the resources are used (see Clause 6.3.2.2) for the remaining PBPS candidate slots, and CPS slots preceding them. + +## 9.3 Sidelink DRX + +To aid in power consumption reduction for P-UEs, as well as other applications, NR-V2X supports DRX operation on sidelink. It is similar to DRX on the Uu interface, with DRX active and inactive times occurring on a periodically-repeating cycle. In the DRX active part of the cycle, full or partial sensing is performed as usual, together with reception and decoding of PSCCH, PSSCH, etc. In the DRX inactive part, a UE only performs reception of PSCCH and SL-RSRP measurements for sensing. When resource (re-)selection is performed, the physical layer ensures that at least a subset of the resources reported to the MAC layer are within the active time of the UE to which the intended transmission will be sent. + +Sidelink DRX is supported for unicast, groupcast, and broadcast. For unicast, sidelink DRX is configured per pair of source L2 ID and destination L2 ID. A receiver UE may send assistance information to the transmitter UE to assist the determination of the sidelink DRX configuration for the receiver UE. The receiver UE may accept or reject the configuration via PC5-RRC signalling. + +For groupcast and broadcast, sidelink DRX is configured based on QoS profile and destination L2 ID with multiple configurations supported. UE needs to perform down selection on cycle/timers when multiple QoS profiles are configured for one destination L2 ID. A default sidelink DRX configuration can be used for a QoS profile which cannot be mapped to any configuration for the dedicated QoS profile(s). Transmission profiles are defined for groupcast and broadcast to ensure backward compatibility; refer to Clause 8. A transmission profile is indicated from upper layers to AS layers, and includes at least the information of whether or not sidelink DRX is supported. + +Alignment of Uu DRX and sidelink DRX for a receiver UE in RRC\_CONNECTED state is supported for unicast, groupcast, and broadcast. + +Details of the sidelink DRX operation are specified in TS 38.321 [21, clause 5.28]. + +# 10 Roadside unit + +The development of LTE and NR V2X contemplates three entities in the network: base stations, i.e. eNBs and gNBs; UEs; and RSUs. An RSU is defined in TS 22.185 [6], TS 22.186 [7] as a stationary infrastructure entity supporting V2X applications that can exchange messages with other entities supporting V2X applications. Note that RSU is a term frequently used in existing ITS specifications, and the reason for introducing the term in the 3GPP specifications is to make the documents easier to read for the ITS industry. RSU is a logical entity that supports V2X application logic + +using the functionality provided by either a 3GPP network (referred to as an eNB/gNB-type RSU) or a UE (referred to as UE-type RSU). + +Since an RSU is essentially only different from a eNB/gNB or UE in terms of its deployment nature, e.g. it may be deployed by a national roads authority instead of an MNO, there is no specification of features particular to RSUs. They operate simply according to sidelink or UL/DL specifications as appropriate. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|---------------|------------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-05 | RAN1#97 | R1-1906663 | | | | Initial version of TR and skeleton of LTE-V2X clauses | 0.0.1 | +| 2019-08 | RAN1#98 | R1-1909651 | | | | LTE-V2X first version, and skeleton of NR-V2X clauses | 0.1.0 | +| 2019-10 | RAN1#98bis | R1-1910616 | | | | Addition of RAN2 and RAN3 LTE-V2X, and NR-V2X first version | 0.2.0 | +| 2019-11 | RAN1#99 | R1-1913120 | | | | RAN2 NR V2X skeleton and updates to RAN1 NR V2X clauses | 0.3.0 | +| 2019-11 | RAN1#99 | R1-1913587 | | | | V1.0.0 to RAN for information | 1.0.0 | +| 2020-02 | RAN1#100-e | R1-2001223 | | | | Updates to NR V2X clauses; addition of introduction and scope | 1.1.0 | +| 2020-04 | RAN1#100bis-e | R1-2002762 | | | | Updates and refinements after RAN1#100-e | 1.2.0 | +| 2020-05 | RAN1#101-e | R1-2004861 | | | | Updates and refinements after RAN1#100bis-e | 1.4.0 | +| 2020-06 | RAN#88-e | RP-200708 | | | | V2.0.0 (endorsed by RAN1#101-e in R1-2005121) to RAN for approval | 2.0.0 | +| 2020-06 | RAN#88-e | - | | | | TR37.985 is approved and under change control as a Rel-16 spec | 16.0.0 | +| 2021-12 | RAN#94-e | RP-212978 | 0001 | - | B | Introduction of Rel-17 sidelink enhancements | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220245 | 0003 | - | A | Addition of Rel-16 NR V2X bands to TR 37.985 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220262 | 0004 | - | F | Introduction of Rel-17 sidelink enhancements and concurrent Uu-PC5 bands | 17.1.0 | +| 2022-03 | RAN#95-e | - | - | - | - | MCC editorial fixing an oversight in cross-reference issue in clause 9.3 of version 17.1.0 – reference is changed to TS 38.321 [21, clause 5.28] | 17.1.1 | +| 2023-12 | RAN#102 | RP-233723 | 0006 | - | A | Miscellaneous corrections on TR 37.985 | 17.2.0 | +| 2023-12 | RAN#102 | RP-233706 | 0007 | - | B | Introduction of sidelink CA and dynamic resource pool sharing for NR V2X | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46001/raw.md b/marked/Rel-18/46_series/46001/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..690c0c427845a512c3c65a6a95850d8f416b5783 --- /dev/null +++ b/marked/Rel-18/46_series/46001/raw.md @@ -0,0 +1,269 @@ + + +# 3GPP TS 46.001 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Full rate speech; Processing functions (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The GSM logo consists of the letters "GSM" in a stylized blue font. The "G" and "S" are connected at the top by a single horizontal bar. The "M" is composed of two "A" shapes joined at the top. Below the letters, the text "GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS" is written in a smaller, blue, sans-serif font. A registered trademark symbol (®) is located to the right of the "M". + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo features the letters "3GPP" in a bold, black, stylized font. The "3" is a standard numeral. The "G" and "P" are connected at the top by a single horizontal bar. The "P" has a small red signal icon below it, consisting of three curved lines of increasing size. A trademark symbol (TM) is located to the upper right of the "P". + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|-------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 5 | +| 4 Introduction..... | 6 | +| 5 Full rate speech transcoding (GSM 06.10) ..... | 6 | +| 6 Full rate Discontinuous Transmission (DTX) (GSM 06.31) ..... | 6 | +| 7 Full rate Voice Activity Detection (VAD) (GSM 06.32) ..... | 7 | +| 8 Full rate comfort noise insertion (GSM 06.12)..... | 7 | +| 9 Full rate lost speech frame substitution and muting (GSM 06.11) ..... | 7 | +| 10 Full Rate codec homing (GSM 06.10, optional feature)..... | 7 | +| 11 Speech transmission functions of the half rate traffic channel ..... | 8 | +| Annex A (informative): Change History ..... | 10 | + +## --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is an introduction to the 06 series of the GSM technical specifications dealing with the Full rate speech processing functions in the GSM system. A general overview of the speech processing parts is given with reference to the technical specifications where each part is specified in detail. + +# --- 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 03.50: "Digital cellular telecommunications system (Phase 2+); Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system". +- [3] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding". +- [4] GSM 06.11: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Substitution and muting of lost frames for full rate speech channels". +- [5] GSM 06.12: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Comfort noise aspect for full rate speech traffic channels". +- [6] GSM 06.31: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels". +- [7] GSM 06.32: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD) for full rate speech traffic channels". +- [8] GSM 06.02: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- [9] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- [10] GSM 06.21: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- [11] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- [12] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- [13] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". + +# --- 3 Abbreviations + +Abbreviations used in the present document are listed in GSM 01.04 [1]. + +# 4 Introduction + +Figure 1 presents a reference configuration where the various speech processing functions are identified. In this figure, the relevant technical specifications for each function are also indicated. + +In figure 1, the audio parts including analogue to digital and digital to analogue conversion are included to show the complete speech path between the audio input/output in the Mobile Station (MS) and the digital interface to the PSTN. The specification of the audio parts are contained in GSM 03.50 [2] (Transmission plan aspects of the speech service in the GSM PLMN system). These aspects are only considered in the GSM 06-series to the extent that the performance of the audio parts affect the performance of the speech transcoder. + +# 5 Full rate speech transcoding (GSM 06.10) + +As shown in figure 1, the speech encoder takes its input as a 13 bit uniform PCM signal either from the audio part of the mobile station or on the network side, from the PSTN via an 8 bit/A-law or $\mu$ -law (PCS 1900) to 13 bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to the channel coding function defined in GSM 05.03 to produce an encoded block consisting of 456 bits leading to a gross bit rate of 22,8 kbit/s. + +In the receive direction, the inverse operations take place. GSM 06.10 [3] describes the detailed mapping between input blocks of 160 speech samples in 13 bit uniform PCM format to encoded blocks of 260 bits and from encoded blocks of 260 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8 000 sample/s leading to an average bit rate for the encoded bit stream of 13 kbit/s. The coding scheme is the so-called Regular Pulse Excitation - Long Term prediction - Linear Predictive Coder, here-after referred to as RPE-LTP. + +The technical specification describes the codec down to the bit level, thus enabling the verification of compliance to the technical specification to a high degree of confidence by use of a set of digital test sequences. These test sequences are also described and are available on floppy disks. + +# 6 Full rate Discontinuous Transmission (DTX) (GSM 06.31) + +During a normal conversation, the participants alternate so that, on the average, each direction of transmission is occupied about 50 % of the time. Discontinuous transmission (DTX) is a mode of operation where the transmitters are switched on only for those frames which contain useful information. This may be done for the following two purposes: + +- 1) in the MS, battery life will be prolonged or a smaller battery could be used for a given operational duration; +- 2) the average interference level on the "air" is reduced, leading to better spectrum efficiency. + +The overall DTX mechanism is implemented in the DTX handlers (TX and RX) described in GSM 06.31 [6] and requires the following functions which are described in separate technical specifications: + +- a Voice Activity Detector on the transmit side; +- evaluation of the background acoustic noise on the transmit side, in order to transmit characteristic parameters to the receive side; +- generation on the receive side of a similar noise, called comfort noise, during periods where the radio transmission is cut. + +The transmission of comfort noise information to the receive side is achieved by means of a special frame (Silence descriptor = SID). This frame is transmitted at the end of speech bursts and serves as an end of speech marker for the receive side. In order to update the comfort noise characteristics at the receive side, SID frames are transmitted at regular intervals also during speech pauses. This also serves the purpose of improving the measurement of the radio link quality by the radio subsystem. + +For the overall DTX functionality, the DTX handlers interwork via various flags with the Radio Subsystem, which is in control of the actual transmitter keying on the TX side and which performs various pre-processing functions on the RX side. This is also described in GSM 06.31 [6]. + +A common terminology used throughout the GSM 06-series of technical specifications is also defined in the present document. + +# --- 7 Full rate Voice Activity Detection (VAD) (GSM 06.32) + +The input to the VAD is a set of parameters computed by the full-rate speech encoder defined in GSM 06.10 [3]. The VAD uses this information to decide whether each 20 ms speech coder frame contains speech or not. Note that the VAD flag is an input to TX DTX handler and does not control the transmitter keying directly. + +The technical specification describes the VAD algorithm down to the bit level. The conventions used in the bit-exact specification are the same as those used in GSM 06.10 [3]. The verification of compliance to the technical specification is achieved by use of digital test sequences applied to the same interface as the test sequences for the speech codec. These test sequences are also described and are available on floppy disks. + +## --- 8 Full rate comfort noise insertion (GSM 06.12) + +When switching the transmission on and off during DTX operation, the effect would be a modulation of the background noise at the receiving end if no precautions were taken. When transmission is on, the background noise is transmitted together with the speech to the receiving end. As the speech burst ends, the connection is off and the perceived noise would drop to a very low level. This step modulation of noise is perceived as very annoying and may reduce the intelligibility of speech if presented to a listener without modification. + +This so-called "noise contrast effect" is reduced in the GSM system by inserting an artificial noise, termed comfort noise, at the receiving end when speech is absent. + +GSM 06.12 [5] deals with the detailed aspects of the comfort noise process: + +- the evaluation of the acoustic background noise in the transmitter; +- the noise parameter encoding (SID frames) and decoding; +- and the generation of comfort noise in the receiver. + +The algorithm for updating the noise parameters during speech pauses is also defined. + +The comfort noise mechanism is based on the full rate speech codec defined in GSM 06.10 [3]. + +# --- 9 Full rate lost speech frame substitution and muting (GSM 06.11) + +In the receiver, frames may be lost due to transmission errors or frame stealing. GSM 06.11 [4] describes the actions to be taken in these cases, both for lost speech frames and for lost SID-frames in DTX operation. + +In order to mask the effect of an isolated lost frame, a scheme is used, where the lost speech frame is substituted by a predicted frame based on previous frames. Insertion of silence frames is not allowed. For several lost frames in a row, some muting technique must be used to indicate to the customer that transmission is interrupted. + +# --- 10 Full Rate codec homing (GSM 06.10, optional feature) + +A codec homing procedure has been introduced to the GSM Full Rate speech codec as an optional feature. + +The GSM Full Rate speech transcoder and VAD algorithm (see figure 1) are defined in bit exact arithmetic. Consequently, they shall react on a given input sequence always with the corresponding bit exact output sequence, provided that the internal state variables are also always exactly in the same state at the beginning of the experiment. + +The input test sequences provided in GSM 06.10 [3] shall force the corresponding output test sequences, provided that the tested modules are in their home-state when starting. + +The modules may be set into their home states by provoking the appropriate homing-functions. + +NOTE: This is normally done during reset (initialization of the codec). + +Special inband signalling frames (encoder-homing-frame and decoder-homing-frame) also described in GSM 06.10 [3] have been defined to provoke these homing-functions also in remotely placed modules. + +This mechanism is specified to support three main areas: + +- type approval and laboratory test of mobile terminal equipment; +- type approval and laboratory test of infrastructure equipment; +- remote control and testing for operation and maintenance. + +At the end of the first received homing frame, the audio functions that are defined in a bit exact way shall be rendered into their predefined home states. The output corresponding to the first homing frame is dependent on the codec state when the frame was received. Any consecutive homing frames shall produce corresponding homing frames at the output. + +# --- 11 Speech transmission functions of the half rate traffic channel + +The gross bit rate of the half rate speech traffic channel is 11,4 kbit/s. The algorithm for the half rate speech transcoder as well as the associated DTX functions are defined in GSM 06.02 [8], GSM 06.20 [9], GSM 06.21 [10], GSM 06.22 [11], GSM 06.41 [12] and GSM 06.42 [13]. + +![Figure 1: Overview of audio processing functions. The diagram is split into 'Transmit side' and 'Receive side'. The Transmit side shows audio input from BSS (GSM 06.10) and MS (GSM 03.50) being processed through LPF, A/D, and 8-bit to 13-bit conversion. It then enters the TX DTX handler which contains a Voice Activity Detector (GSM 06.32), Speech encoder (GSM 06.10), and Comfort noise TX functions (GSM 06.12). These feed into a DTX control and operation block (GSM 06.31) which outputs a SP flag (6) and Info. bits (7). The Receive side shows Info. bits (8), BFI (9), SID (10), and TAF (11) entering the RX DTX handler's DTX control and operation block. This block feeds into Speech frame substitution, Speech decoder (GSM 06.10), and Comfort noise RX functions (GSM 06.12). The output is then processed through D/A and LPF to produce the final audio output for BSS (GSM 06.10) and MS (GSM 03.50).](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +**Transmit side** + +**RX DTX handler** + +**Receive side** + +Figure 1: Overview of audio processing functions. The diagram is split into 'Transmit side' and 'Receive side'. The Transmit side shows audio input from BSS (GSM 06.10) and MS (GSM 03.50) being processed through LPF, A/D, and 8-bit to 13-bit conversion. It then enters the TX DTX handler which contains a Voice Activity Detector (GSM 06.32), Speech encoder (GSM 06.10), and Comfort noise TX functions (GSM 06.12). These feed into a DTX control and operation block (GSM 06.31) which outputs a SP flag (6) and Info. bits (7). The Receive side shows Info. bits (8), BFI (9), SID (10), and TAF (11) entering the RX DTX handler's DTX control and operation block. This block feeds into Speech frame substitution, Speech decoder (GSM 06.10), and Comfort noise RX functions (GSM 06.12). The output is then processed through D/A and LPF to produce the final audio output for BSS (GSM 06.10) and MS (GSM 03.50). + +- (1) 8 bit /A- or u-law (PCS 1900) PCM (ITU-T rec G.711) +- (2) 13 bit uniform PCM, 8000 samples/s +- (3) Voice activity flag +- (4) Encoded speech frame, 50 samples/s, 260 bits/frame +- (5) Silence Descriptor (SID) frame, 260 bits/frame +- (6) Speech flag, indicates whether information bits are speech or SID information +- (7) Information bits delivered to the radio subsystem +- (8) Information bits received from the radio subsystem +- (9) Bad Frame Indication (BFI) flag +- (10) Silence Descriptor (SID) flag +- (11) Time Alignment Flag (TAF), marks the position of the SID frame within the SACCH multiframe + +**Figure 1: Overview of audio processing functions** + +## Annex A (informative): Change History + +| Change history | | | | | | +|----------------|------------------|--------------|-----------------|-------------|---------------------------------------------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments | +| SMG#07 | | | | 4.0.5 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#23 | 97-737
97-741 | A004
A005 | | 5.1.0 | UAP61 comments
Introduction of Homing for Full Rate Speech Transcoding | +| SMG#23 | | | | 5.1.1 | ETSI version change | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#28 | P-99-136 | A006 | 5 and Figure 1 | 7.0.0 | Addition of mu-law (PCS 1900) | +| | | | | 7.0.2 | Update to Version 7.0.2 for Publication | +| SMG#31 | | | | 8.0.0 | Version for Release 1999 | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46002/raw.md b/marked/Rel-18/46_series/46002/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4f2dedc4ea008a8fc29658f30f8cc003fce4ea69 --- /dev/null +++ b/marked/Rel-18/46_series/46002/raw.md @@ -0,0 +1,316 @@ + + +# 3GPP TS 46.002 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Half rate speech; Half rate speech processing functions (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## --- **Keywords** + +GSM, speech + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 General ..... | 6 | +| 5 Half rate speech transcoding..... | 8 | +| 6 Half rate Discontinuous Transmission (DTX) ..... | 8 | +| 7 Half rate Voice Activity Detection (VAD)..... | 9 | +| 8 Half rate comfort noise insertion ..... | 9 | +| 9 Half rate lost speech frame substitution and muting..... | 9 | +| 10 Half rate codec homing..... | 10 | +| Annex A (informative): Change History ..... | 11 | + +# 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. + +The present document gives a general overview of the half rate speech traffic channels speech processing functions for the digital cellular telecommunications system. The present document is part of ENs' series covering the half rate speech traffic channels as described below: + +- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".** +- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". +- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". + +# --- 1 Scope + +The present document is an introduction to GSM 06.20 [4], GSM 06.21 [5], GSM 06.22 [6], GSM 06.41 [7] and GSM 06.42 [8] TSs dealing with the speech processing functions in the half-rate channel of the GSM system. A general overview of the speech processing functions is given, with reference to the TSs where each function is specified in detail. + +# --- 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] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 03.50: "Digital cellular telecommunication system (Phase 2+); Transmission planning aspects of the speech services in the GSM Public Land Mobile Network (PLMN) system". +- [3] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [4] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech: Half rate speech transcoding". +- [5] GSM 06.21: " Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frame for half rate speech traffic channels". +- [6] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels ". +- [7] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous transmission (DTX) for half rate speech traffic channels". +- [8] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels ". +- [9] ITU-T Recommendation G.711: "Pulse Code Modulation (PCM) of voice frequencies". +- [10] GSM 06.07: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". +- [11] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +Definition of terms used in the present document can be found in GSM 06.20 [4], GSM 06.21 [5], GSM 06.22 [6], GSM 06.41 [7] and GSM 06.42 [8]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply. + +| | | +|---------|-----------------------------------------| +| BFI | Bad Frame Indication | +| BSS | Base Station System | +| DTX | Discontinuous Transmission | +| GSM | Global System for Mobile communications | +| MS | Mobile Station | +| PCM | Pulse Code Modulated | +| PLMN | Public Land Mobile Network | +| PSTN | Public Switched Telephone Network | +| RF | Radio Frequency | +| RX | Receive | +| RSS | Radio SubSystem | +| SACCH | Slow Associated Control CHannel | +| SID | SIlence Descriptor | +| SP flag | SPeech flag | +| TAF | Time Alignment Flag | +| TX | Transmit | +| VSELP | Vector Sum Excited Linear Predictor | +| UFI | Unreliable Frame Indication | + +For abbreviations not given in this subclause, see GSM 01.04 [1]. + +# --- 4 General + +Figure 1 presents a reference configuration where the various speech processing functions are identified. In this figure, the relevant documents for each function are also indicated. + +In figure 1, the audio parts including analogue to digital and digital to analogue conversion are included, to show the complete speech path between the audio input/output in the Mobile Station (MS) and the digital interface of the Public Switched Telephone Network (PSTN). The detailed specification of the audio parts are contained in GSM 03.50 [2]. These aspects are only considered to the extent that the performance of the audio parts affect the performance of the speech transcoder. + +![Figure 1: Overview of audio processing functions. The diagram shows the flow of audio data between the Transmit Side (TX) and the Receive Side (RX). On the TX side, audio from BSS (GSM 06.02) and MS (GSM 03.50) sources is combined at point 2 and sent to the TX DTX handler. The TX DTX handler contains a Voice Activity Detector (VAD) at point 3, a Speech encoder at point 4, and Comfort noise TX functions at point 5. It also outputs a SP flag at point 6 and info. bits at point 7. On the RX side, the RX DTX handler receives Info bits (8), BFI (9), SID (10), TAF (11), and UFI (12). It contains a DTX control and operation block (GSM 06.41) and a speech decoder (GSM 06.20) at point 4. It also includes Speech frame substitution (GSM 06.21) and Comfort noise RX functions (GSM 06.22). The output of the RX DTX handler is combined at point 2 and sent to the BSS (GSM 06.02) and MS (GSM 03.50) destinations.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +Figure 1: Overview of audio processing functions. The diagram shows the flow of audio data between the Transmit Side (TX) and the Receive Side (RX). On the TX side, audio from BSS (GSM 06.02) and MS (GSM 03.50) sources is combined at point 2 and sent to the TX DTX handler. The TX DTX handler contains a Voice Activity Detector (VAD) at point 3, a Speech encoder at point 4, and Comfort noise TX functions at point 5. It also outputs a SP flag at point 6 and info. bits at point 7. On the RX side, the RX DTX handler receives Info bits (8), BFI (9), SID (10), TAF (11), and UFI (12). It contains a DTX control and operation block (GSM 06.41) and a speech decoder (GSM 06.20) at point 4. It also includes Speech frame substitution (GSM 06.21) and Comfort noise RX functions (GSM 06.22). The output of the RX DTX handler is combined at point 2 and sent to the BSS (GSM 06.02) and MS (GSM 03.50) destinations. + +- 1 8 bit /A-law or $\mu$ -law (PCS 1900) PCM (ITU-T Recommendation G.711) [9], 8 000 samples/s. +- 2 13 bit uniform PCM, 8 000 samples/s. +- 3 Voice Activity Detector (VAD) flag. +- 4 Encoded speech frame, 50 frames/s, 112 bits/frame. +- 5 Silence Descriptor (SID) frame, 112 bits/frame. +- 6 SPeech (SP) flag, indicates whether information bits are speech or SID information. +- 7 Information bits delivered to the radio subsystem. +- 8 Information bits received from the radio subsystem. +- 9 Bad Frame Indication (BFI) flag. +- 10 Silence Descriptor (SID) flag. +- 11 Time Alignment Flag (TAF), marks the position of the SID frame within the Slow Associated Control CHannel (SACCH) multiframe. +- 12 Unreliable Frame Indication (UFI). + +Figure 1: Overview of audio processing functions + +# 5 Half rate speech transcoding + +The half rate speech transcoding function is described in GSM 06.20 [4]. + +As shown in figure 1, the speech encoder takes its input as a 13 bit uniform Pulse Code Modulated (PCM) signal either from the audio part of the MS or on the network side, from the PSTN via an 8 bit/A-law or $\mu$ -law (PCS 1900) to 13 bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to the channel coding function as defined in GSM 05.03 [3] to produce an encoded block consisting of 228 bits leading to a gross bit rate of 11,4 kbit/s. + +In the RX direction, the inverse operations take place. + +GSM 06.20 [4] describes the detailed mapping between input blocks of 160 speech samples in 13 bit uniform PCM format into encoded blocks of 112 bits and from encoded blocks of 112 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8 000 sample/s leading to an average bit rate for the encoded bit stream of 5,6 kbit/s. The coding scheme is called Vector Sum Excited Linear Prediction (VSELP) coding. + +GSM 06.20 [4] describes the codec and GSM 06.06 [11] defines the C code, thus enabling the verification of compliance to GSM 06.20 [4] to a high degree of confidence by use of a set of digital test sequences given in GSM 06.07 [10]. + +# 6 Half rate Discontinuous Transmission (DTX) + +The half rate discontinuous transmission function is described in GSM 06.41 [7]. + +During a normal conversation, the participants alternate so that, on the average, each direction of transmission is occupied about 50 % of the time. Discontinuous Transmission (DTX) is a mode of operation where the transmitters are switched on only for those frames which contain useful information. This may be done for the following two purposes: + +- 1) in the MS, battery life will be prolonged or a smaller battery could be used for a given operational duration; +- 2) the average interference level over the air interface is reduced, leading to better Radio Frequency (RF) spectrum efficiency. + +The overall DTX mechanism is implemented in the DTX handlers (Transmit (TX) and Receive (RX)) described in GSM 06.41 [7] and requires the following functions: + +- a Voice Activity Detector (VAD) on the TX side, see GSM 06.42 [8]; +- evaluation of the background acoustic noise on the TX side, in order to transmit characteristic parameters to the RX side, see GSM 06.22 [6]; +- generation of comfort noise on the RX side during periods where the radio transmission is turned off, see GSM 06.22 [6]. + +The transmission of comfort noise information to the RX side is achieved by means of a SIlence Descriptor (SID) frame. The SID frame is transmitted at the end of speech bursts and serves as an end of speech marker for the RX side. In order to update the comfort noise characteristics at the RX side, SID frames are transmitted at regular intervals also during speech pauses. This also serves the purpose of improving the measurement of the radio link quality by the Radio SubSystem (RSS). + +The DTX handlers interwork with the RSS using flags. The RSS is controlled by the transmitter keying on the TX side, which performs pre-processing functions on the RX side. This is described in GSM 06.41 [7]. + +The speech flag (SP) indicates whether information bits are speech or SID information. The SP flag is calculated from the VAD flag by the TX DTX handler. When SID information is transmitted (SP="0") the operation of the speech encoder is modified to reduce the remaining computation for that frame. This is described in GSM 06.22 [6]. + +# --- 7 Half rate Voice Activity Detection (VAD) + +The half rate VAD function is described in GSM 06.42 [8]. + +The input to the VAD is a set of parameters computed by the half-rate speech encoder defined in GSM 06.20 [4]. The VAD uses this information to decide whether each 20 ms speech coder frame contains speech or not. + +NOTE: The VAD flag is an input to TX DTX handler and does not control the transmitter keying directly. + +GSM 06.42 [8] describes the VAD algorithm and GSM 06.06 [11] defines the C code. The verification of compliance to GSM 06.42 [8] is achieved by use of digital test sequences (see GSM 06.07 [10]) applied to the same interface as the test sequences for the speech codec. + +# --- 8 Half rate comfort noise insertion + +The half rate noise comfort insertion function is described in GSM 06.22 [6]. + +When switching the transmission on and off during DTX operation, the effect would be a modulation of the background noise at the receiving end, if no precautions were taken. When transmission is on, the background noise is transmitted together with the speech to the receiving end. As the speech burst ends, the connection is off and the perceived noise would drop to a very low level. This step modulation of noise may be perceived as annoying and reduce the intelligibility of speech, if presented to a listener without modification. + +This "noise contrast effect" is reduced in the GSM system by inserting an artificial noise, termed comfort noise, at the receiving end when speech is absent. + +The comfort noise processes are as follows: + +- the evaluation of the acoustic background noise in the transmitter; +- the noise parameter encoding (SID frames) and decoding; +- and the generation of comfort noise in the receiver. + +The comfort noise processes and the algorithm for updating the noise parameters during speech pauses are defined in detail in GSM 06.22 [6]. + +The comfort noise mechanism is based on the half rate speech codec defined in GSM 06.20 [4]. + +# --- 9 Half rate lost speech frame substitution and muting + +The half rate speech frame substitution and muting function is described in GSM 06.21 [5]. + +In the receiver, frames may be lost due to transmission errors or frame stealing. + +GSM 06.21 [5] describes the actions to be taken in these cases, both for lost speech frames and for lost SID frames in DTX operation. + +In order to mask the effect of an isolated lost frame, the lost speech frame is substituted by a predicted frame based on previous frames. Insertion of silence frames is not allowed. For several subsequent lost frames, a muting technique shall be used to indicate to the listener that transmission has been interrupted. + +# 10 Half rate codec homing + +The GSM half rate speech transcoder, VAD, DTX system and comfort noise parts of the audio processing functions (see figure 1) are defined in bit exact arithmetic. Consequently, they shall react on a given input sequence always with the corresponding bit exact output sequence, provided that the internal state variables are also always exact in the same state at the beginning of the experiment. + +The input test sequences provided in GSM 06.07 [10] shall force the corresponding output test sequences, provided that the tested modules are in their home-state when starting. + +The modules may be set into their home states by provoking the appropriate homing-functions. + +NOTE: This is normally done during reset. + +Special inband signalling frames (encoder-homing-frame and decoder-homing-frame described in GSM 06.20 [4]) have been defined to provoke these homing-functions also in remotely placed modules. + +This mechanism is specified to support three main areas: + +- type approval of mobile terminal equipment; +- type approval of infrastructure equipment; +- remote control and testing for operation and maintenance. + +At the end of the first received homing frame, the audio functions that are defined in a bit exact way shall go into their predefined home states. The output corresponding to the first homing frame is dependent on the codec state when the frame was received. Any consecutive homing frames shall produce corresponding homing frames at the output. + +# Annex A (informative): Change History + +| Change history | | | | | | +|----------------|-----------|---------|------------------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#13 | | | | 4.0.2 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#28 | P-99-137 | A001 | 5 and caption Figure 1 | 7.0.0 | Addition of mu-law (PCS 1900) | +| | | | | 7.0.2 | Update to Version 7.0.2 for Publication | +| SMG#31 | | | | 8.0.0 | Version for Release 1999 | + +| Change history | | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46006/raw.md b/marked/Rel-18/46_series/46006/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cb0180d7c7937b41d4c71d2b323c7a955807507b --- /dev/null +++ b/marked/Rel-18/46_series/46006/raw.md @@ -0,0 +1,319 @@ + + +# 3GPP TS 46.006 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Half rate speech; ANSI-C code for the GSM half rate speech codec (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The GSM logo consists of the letters 'GSM' in a stylized blue font. The 'G' and 'S' are connected at the top by a single horizontal bar. The 'M' is composed of two 'A' shapes joined at the top. Below the letters, the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' is written in a smaller, blue, sans-serif font. A small red square is located to the right of the 'M'. + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo features the letters '3GPP' in a bold, black, stylized font. The '3' is a standard digit. The 'G' and 'P' are connected at the top by a single horizontal bar. The 'P' has a small red signal icon below it, consisting of three curved lines. A small 'TM' symbol is located to the top right of the 'P'. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +### **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|--------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 C code structure ..... | 6 | +| 4.1 Directory structure..... | 6 | +| 4.2 Program execution..... | 7 | +| 4.3 Code hierarchy ..... | 7 | +| 5 ANSI-C code for the GSM half rate speech codec ..... | 12 | +| Annex A (informative): Change History..... | 13 | + +# 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. + +The present document specifies the half rate speech traffic channels for the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below: + +- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".** +- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". +- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". + +# --- 1 Scope + +The present document contains an electronic copy of the ANSI-C code for the GSM half rate codec. The ANSI-C code is necessary for a bit exact implementation of the half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]), Discontinuous Transmission (GSM 06.41 [5]) and example solutions for substituting and muting of lost frames (GSM 06.21 [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] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- [3] GSM 06.21: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frame for half rate speech traffic channels". +- [4] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- [5] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- [6] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". +- [7] GSM 06.07: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". +- [8] American National Standards Institute ANSI 9899 (1990): "Programming Language - C (ISO)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +Definition of terms used in the present document can be found in GSM 06.20 [2], GSM 06.21 [3], GSM 06.22 [4], GSM 06.41 [5] and GSM 06.42 [6]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------------| +| ANSI | American National Standards Institute | +| DS-HD | Double Sided High Density | +| ETS | European Telecommunication Standard | +| GSM | Global System for Mobile communications | +| I/O | Input/Output | +| ROM | Read Only Memory | + +For abbreviations not given in this clause, see GSM 01.04 [1]. + +# 4 C code structure + +This clause gives an overview of the structure of the bit-exact C code and provides an overview of the contents and organization of the electronic attachment accompanying the present document. + +The C code has been verified on the following systems: + +- Sun Microsystems's 1) workstations and Sun Microsystems acc; +- IBM 2) PC/AT compatible computers and Borlands Turbo-C 3) compiler; +- VAX 4) and Digital Equipment Corporations CC. + +ANSI-C 9899 [8] was selected as the programming language because portability was desirable. + +The code representation is contained in a MS-DOS 5) file (called Disk and contained in archive en\_300967v080001p0.ZIP which accompanies the present document. + +## 4.1 Directory structure + +A listing of the directories is given in table 1. + +**Table 1: Directory structure listing** + +| Directory name | Contents | Size (bytes) | +|----------------|--------------------------------------------|--------------| +| \c | C files and headers | 1 215 563 | +| \d | example binary data input and output files | 72 400 | +| \exec | executables and makefiles | 5 509 | +| \utils | utility programs and the "reid" program | 49 531 | +| readme.txt | usage description of files | 9 116 | + +The C code file (called Disk and contained in archive en\_300967v080001p0.ZIP) which accompanies the present document has one main directory and four subdirectories. The top directory has in it the file readme.txt which explains the installation procedure, along with some miscellaneous descriptive information regarding the code. + +Below this directory, are the four subdirectories. The "c" subdirectory contains all the source code and header files. This directory alone is essential, the others aid in the building, or testing of the code. All ROM data is in this source directory. After installation, this directory can be made read only. + +- +- 1) Registered trade mark of Sun Microsystems + - 2) Registered trade mark of International Business Machines + - 3) Registered trade mark of Borland + - 4) Registered trade mark of Digital Equipment Corporation + - 5) Registered trade mark of Microsoft + +The "d" subdirectory contains all the speech coder installation verification data files. All of the data files are written/read as 16 bit words, so these may require byte swapping on the target platform. All data and text files are formatted such that they are correct for an IBM PC/AT compatible. + +Final verification is to be performed using the GSM half rate test sequences described in GSM 06.07 [7]. + +The "utils" subdirectory contains miscellaneous utilities which may be useful in the installation of the software. Two programs are provided to transform text files: topcwild and tosnwild. The program topcwild takes UNIX text files and converts them to pc text files. tosnwild does the opposite. The program swapbin is also in this directory. This performs byte swapping on a binary data file. A fourth program, reid, is also contained in this sub directory. This is the residual error insertion program which also provides the format conversion between the encoder output file format and the decoder input file format. + +The "exec" subdirectory contains the makefiles for the various platforms. Once the software is installed, this directory will have a compiled version of gsm\_hr (the bit-exact C executable), programs from the "utils" directory, and all the object files. + +The program gsm\_hr is the name of the GSM half rate codec executable file. + +## 4.2 Program execution + +The GSM half rate speech codec is implemented as two separate programs: + +- (gsm\_hr) speech codec; +- (reid) encoder/decoder interface. + +The gsm\_hr program operates in one of two modes: + +- (0) encoding only; +- (1) decoding only. + +For encoding, the input is a binary speech file (\*.inp) and the output is a binary encoded parameter file (\*.cod). For decoding, the input is a binary parameter files (\*.dec) and the output is a binary synthesized speech file (\*.out). Note that the format for the parameter input file required for decoding (\*.dec) is not the same as the format of the parameter output file generated by encoding (\*.cod). The reid program will translate an \*.cod file into an \*.dec file (select error-free mode, EP0). + +See the file readme.txt for more information on how to run the gsm\_hr and reid programs. + +## 4.3 Code hierarchy + +Figures 1 to 7 are call graphs that show the functions used in the speech codec. + +The encode call graph is broken down into six separate call graphs. Those clauses, which are large, are separated from the primary encode call tree and given their own call tree. Each vertical column represents a call level. For example, main() is at level 0, encode() at level 1, speechEncoder() at level 2, openLoopLagSearch() at level 3, getCCThreshold() at level 4, etc. The basic operations are not counted as extending the depth, therefore the deepest level in this software is level 6. + +Some items have been omitted from this call graph. All standard C functions: printf(), fwrite(), etc. have been omitted. Also, no basic operations (add(), L\_add(), mac(), etc.) or double precision extended operations (e.g. L\_mpy\_ls()) appear in the graphs. + +![Speech decoder call graph showing the hierarchy of function calls starting from 'main' to 'decode' to 'speechDecoder' and its sub-functions.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the call hierarchy for the speech decoder. It begins with 'main' calling 'decode'. 'decode' then calls 'speechDecoderHostInterface', 'speechDecoder', 'readDecfile', 'decoderHomingFrameTest', and 'resetDec'. 'speechDecoder' calls a variety of sub-functions including 'level\_estimator', 'spectralPostFilter', 'signal\_conceal\_sub', 'pitchPreFilt', 'scaleExcite', 'rs\_mNs', 'rs\_rr', 'v\_con', 'b\_con', 'fp\_ex', 'lagDecode', 'r0BasedEnergyShft', 'getSfmLpc', 'a\_sst', 'rxInterpR0Lpc', 'getPnBits', 'gsQuant', 'avgGsHistQntz', 'lookupVq', and 'para\_conceal\_speech\_decoder'. Further sub-function calls are shown, such as 'level\_estimator' calling 'level\_calc', 'spectralPostFilter' calling 'agcGain', 'lpclir', and 'lpcFir', and 'a\_sst' calling 'interpolateCheck', 'rcToADp', 'aFlatRcDp', 'rcToCorrDpL', 'linInterpSid', and 'linInterpSidShort'. 'interpolateCheck' calls 'aToRc', which in turn calls 'sqroot' and 'res\_eng'. 'res\_eng' also calls 'sqroot'. 'resetDec' calls 'decoderReset' and 'dtxResetRx'. + +Speech decoder call graph showing the hierarchy of function calls starting from 'main' to 'decode' to 'speechDecoder' and its sub-functions. + +Figure 1: Speech decoder call graph + +![Speech encoder call graph showing the hierarchy of function calls starting from main, through encode, speechEncoder, and various sub-functions like fillBitAlloc, sfmAnalysis, and getNWCoefs.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` +graph LR; main --> encode; encode --> writeEncfile; encode --> speechEncoder; encode --> hostEncoderInterface; encode --> resetEnc; encode --> encoderHomingFrameTest; speechEncoder --> fillBitAlloc; speechEncoder --> sfmAnalysis; speechEncoder --> periodicity_update; speechEncoder --> openLoopLagSearch; speechEncoder --> weightSpeechFrame; speechEncoder --> getSfrmLpcTx; speechEncoder --> getNWCoefs; speechEncoder --> aflat; speechEncoder --> filt4_2nd; hostEncoderInterface --> encoderReset; hostEncoderInterface --> vad_reset; hostEncoderInterface --> dtxResetTx; resetEnc --> encoderReset; resetEnc --> vad_reset; resetEnc --> dtxResetTx; weightSpeechFrame --> lpcIir; weightSpeechFrame --> lpcFir; weightSpeechFrame --> res_eng; res_eng --> sqroot; getSfrmLpcTx --> compResidEnergy; getSfrmLpcTx --> interpolateCheck; interpolateCheck --> aToRc; getNWCoefs --> rcToADp; getNWCoefs --> aFlatRcDp; getNWCoefs --> g_corr1; getNWCoefs --> lpcZsIirP; getNWCoefs --> lpcZsFir; getNWCoefs --> lpcIrZsIiR; filt4_2nd --> iir_d; +``` + +Speech encoder call graph showing the hierarchy of function calls starting from main, through encode, speechEncoder, and various sub-functions like fillBitAlloc, sfmAnalysis, and getNWCoefs. + +Figure 2: Speech encoder call graph + +![Speech encoder LPC quantization call graph](e6df2733626a85205c1db682e6259c46_img.jpg) + +This call graph shows the function `aflat` as the root node. It has directed edges to the following functions: `aflatNewBarRecursionL`, `getNextVec`, `setupQuant`, `findBestInQuantList`, `aflatRecursion`, `setupPreQ`, `initPBarVBarL`, `initPBarFullVBarFullL`, `swComfortNoise`, `vad_algorithm`, `rcToCorrDpL`, and `flat`. The function `flat` further has directed edges to `r0Quant`, `sqrroot`, and `cov32`. + +Speech encoder LPC quantization call graph + +Figure 3: Speech encoder LPC quantization call graph + +![Speech encoder open-loop lag search call graph](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +This call graph shows the function `openLoopLagSearch` as the root node. It has directed edges to `bestDelta`, `pitchLags`, `getCCThreshold`, `r0BasedEnergyShft`, and `g_corr1s`. The function `bestDelta` has directed edges to `maxCCOverGWithSign`, `get_ipjj`, `quantLag`, and `GCInterp`. The function `pitchLags` has directed edges to `quantLag`, `GCInterp`, `CGInterpValid`, and `findPeak`. The function `getCCThreshold` has directed edges to `findPeak`, `fnExp2`, and `fnLog2`. The function `findPeak` has directed edges to `quantLag`, `GCInterp`, and `fnBest_CG`. The function `fnExp2` has directed edges to `quantLag`, `GCInterp`, and `fnBest_CG`. The function `fnLog2` has directed edges to `quantLag`, `GCInterp`, and `fnBest_CG`. + +Speech encoder open-loop lag search call graph + +Figure 4: Speech encoder open-loop lag search call graph + +![Speech encoder subframe processing call graph](5a4e62bead259c258d069fd3663ea670_img.jpg) + +This call graph illustrates the subframe processing within the speech encoder. The root node, **sfmAnalysis**, initiates a series of calls to various processing blocks. These include **lpcLir**, **scaleExcite**, **g\_quant\_vl**, **rs\_rrNs**, **hnwFilt**, **v\_con**, **b\_con**, **v\_srch**, **decorr**, **closedLoopLagSearch**, and **lpcZilr**. Further dependencies are shown: **lpcLir** and **scaleExcite** lead to **gainTweak**; **g\_quant\_vl** leads to **g\_corr1** and **g\_corr2**; **rs\_rrNs** leads to **g\_corr1**, **g\_corr2**, and **sqroot**; **hnwFilt** leads to **lpcZsLir**; **v\_con** and **b\_con** lead to **get\_ipjj**; **v\_srch** and **decorr** lead to **lpcZsLir**; **closedLoopLagSearch** leads to **fp\_ex**, **quantLag**, and **maxCCOverGWithSign**; and **lpcZilr** leads to **lpcZsLir**. Additionally, **gainTweak** leads to **sqroot**. + +Speech encoder subframe processing call graph + +Figure 5: Speech encoder subframe processing call graph + +![Comfort noise call graph](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +This call graph shows the processing flow for comfort noise. The root node, **swComfortNoise**, calls several functions: **getPnBits**, **lpcCorrQntz**, **r0Quant**, **avgCNHist**, **gsQuant**, **avgGsHistQntz**, and **updateCNHist**. The **lpcCorrQntz** node further branches into a series of calls: **aflatNewBarRecursionL**, **getNextVec**, **setupQuant**, **findBestInQuantList**, **aflatRecursion**, **setupPreQ**, **initPBarVBarL**, and **initPBarFullVBarFullL**. + +Comfort noise call graph + +Figure 6: Comfort noise call graph + +![Voice Activity Detector (VAD) call graph showing vad_algorithm calling various sub-functions like vad_hangover, vad_decision, threshold_adaptation, tone_detection, spectral_comparison, predictor_values, average_acf, and energy_computation. tone_detection calls step_up. predictor_values calls compute_rav1 and schur_recursion.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` +graph LR; vad_algorithm --> vad_hangover; vad_algorithm --> vad_decision; vad_algorithm --> threshold_adaptation; vad_algorithm --> tone_detection; vad_algorithm --> spectral_comparison; vad_algorithm --> predictor_values; vad_algorithm --> average_acf; vad_algorithm --> energy_computation; tone_detection --> step_up; predictor_values --> compute_rav1; predictor_values --> schur_recursion; +``` + +Voice Activity Detector (VAD) call graph showing vad\_algorithm calling various sub-functions like vad\_hangover, vad\_decision, threshold\_adaptation, tone\_detection, spectral\_comparison, predictor\_values, average\_acf, and energy\_computation. tone\_detection calls step\_up. predictor\_values calls compute\_rav1 and schur\_recursion. + +Figure 7: Voice Activity Detector (VAD) call graph + +# --- 5 ANSI-C code for the GSM half rate speech codec + +NOTE: This clause is contained in archive en\_300967v080001p0.ZIP which accompanies the present document. + +## Annex A (informative): Change History + +| Change history | | | | | | +|----------------|------------------|--------------|------------------|-------------|-----------------------------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#16 | | | | 4.0.3 | ETSI Publication | +| SMG#17 | 332/95
119/96 | A001
A002 | | 4.1.0 | HR C-code
GSM half rate Codec Homing Procedure | +| SMG#23 | 97-737 | A002 | | 4.1.1 | UAP60 and Supplementary notes on 06.06 Call Graph Changes | +| SMG#20 | | | | 5.0.0 | Release 1996 version | +| SMG#20 | | | | 5.0.1 | ETSI version change | +| SMG#22 | 430/97 | A002 | | 5.1.0 | UAP 60 | +| SMG#23 | 97-737 | A003 | | 5.1.1 | UAP60 and Supplementary notes on 06.06 Call Graph Changes | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#28 | | | | 6.0.1 | ETSI Publication | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | | +| 06-2018 | SA#80 | | | | | Version for Release 15 | 15.0.0 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46007/raw.md b/marked/Rel-18/46_series/46007/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..245e8d58562546dd6213c78982e9fe80cea86cb1 --- /dev/null +++ b/marked/Rel-18/46_series/46007/raw.md @@ -0,0 +1,547 @@ + + +# 3GPP TS 46.007 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Half rate speech; Test sequences for the GSM half rate speech codec (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +**GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS** + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**A GLOBAL INITIATIVE** + +3GPP logo + +## --- **Keywords** + +GSM, codec, speech, testing + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 General ..... | 7 | +| 5 Test sequence format ..... | 7 | +| 5.1 File format ..... | 7 | +| 5.2 Codec homing ..... | 8 | +| 6 Speech codec test sequences..... | 8 | +| 6.1 Codec configuration ..... | 8 | +| 6.2 Speech codec test sequences ..... | 9 | +| 6.2.1 Speech encoder test sequences ..... | 9 | +| 6.2.2 Speech decoder test sequences ..... | 9 | +| 6.2.3 Codec homing sequence ..... | 9 | +| 7 DTX test sequences..... | 10 | +| 7.1 Codec configuration ..... | 10 | +| 7.2 DTX test sequences..... | 10 | +| 7.2.1 Predictor values computation ..... | 10 | +| 7.2.2 Spectral comparison ..... | 11 | +| 7.2.3 Threshold adaptation ..... | 11 | +| 7.2.4 Periodicity detection ..... | 11 | +| 7.2.5 Tone detection ..... | 11 | +| 7.2.6 Safety and initialization ..... | 11 | +| 7.2.7 Comfort noise test sequence ..... | 11 | +| 7.2.8 Real speech and tones..... | 11 | +| 8 Sequences for finding the 20 ms framing of the GSM half rate speech encoder..... | 12 | +| 8.1 Bit synchronization ..... | 12 | +| 8.2 Frame synchronization ..... | 12 | +| 8.3 Formats and sizes of the synchronization sequences ..... | 13 | +| 9 Trau Testing with 8 Bit A- and $\mu$ -law PCM Test Sequences ..... | 14 | +| 10 Test sequences for the GSM half rate speech codec ..... | 15 | +| Annex A (informative): Change history..... | 16 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +An electronic attachment accompanies the present document, containing test sequences for a bit exact implementation of the half rate speech transcoder. + +Archive en\_300968v080001p0.ZIP which accompanies the present document contains compressed files which are labelled as follows: + +- Disks24.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 2 and 4 (GSM 06.07). +- Disks135.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 1, 3 and 5 (GSM 06.07). +- Disks6A.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 6 and 10 (GSM 06.07). +- Disks7B.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 7 and 11 (GSM 06.07). +- Disks89.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 8 and 9 (GSM 06.07). + +The present document specifies the half rate speech traffic channels for the Digital cellular telecommunications system. + +The present document specifies the digital test sequences for the GSM half rate speech codec for the digital cellular telecommunications system. The present document, is part of a series covering the half rate speech traffic channels as described below: + +- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".** +- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". + +GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". + +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 digital test sequences for the GSM half rate speech codec. These sequences test for a bit exact implementation of the half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and the discontinuous transmission (GSM 06.41 [5]). + +# --- 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- [3] GSM 06.21: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frame for half rate speech traffic channels". +- [4] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- [5] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- [6] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". +- [7] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- [8] GSM 06.02: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech coding functions". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +Definition of terms used in the present document can be found in GSM 06.20 [2], GSM 06.21 [3], GSM 06.22 [4], GSM 06.41 [5] and GSM 06.42 [6]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|-----------------------------------------| +| ETS | European Telecommunication Standard | +| GSM | Global System for Mobile communications | + +For abbreviations not given in this clause, see GSM 01.04 [1]. + +# --- 4 General + +Digital test sequences are necessary to test for a bit exact implementation of the half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and the discontinuous transmission (GSM 06.41 [5]). + +The test sequences may also be used to verify installations of the ANSI C code in GSM 06.06 [7]. + +Clause 5 describes the format of the files which contain the digital test sequences. Clause 6 describes the test sequences for the speech transcoder. Clause 7 describes the test sequences for the VAD, comfort noise and discontinuous transmission. + +Clause 8 describes the method by which synchronization is obtained between the test sequences and the speech codec under test. + +Clause 9 describes the optional acceptance testing of the speech encoder and decoder in the TRAUs by means of 8 bit A- or $\mu$ -law compressed test sequences on the A-Interface. + +Electronic copies of the digital test sequences are provided as clause 10, these digital test sequences are contained in archive en\_300968v080001p0.ZIP which accompanies the present document. + +# --- 5 Test sequence format + +This clause provides information on the format of the digital test sequences for the GSM half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and the discontinuous transmission (GSM 06.41 [5]). + +## 5.1 File format + +The test sequence files are provided in archive en\_300968v080001p0.ZIP which accompanies the present document. + +Following decompression, by execution of the 11 "disk\*.exe" files, four types of file are provided: + +- Files for input to the GSM half rate speech encoder: \*.INP +- Files for comparison with the encoder output: \*.COD +- Files for input to the GSM half rate speech decoder: \*.DEC +- Files for comparison with the decoder output: \*.OUT + +Tables 1, 2, 3 and 4 define the formats of the four types of file. Each parameter in these tables is contained in a 16 bit word except for the samples of the 8 bit PCM test sequences, which are contained in an 8 bit word each. The left or right justification is indicated in the tables. The size and location of speech parameters in the encoder output (\*.COD) and decoder input files (\*.DEC) are described in GSM 06.20 [2]. + +## 5.2 Codec homing + +Each \*.INP file includes two homing frames at the start of the test sequence. The function of these frames is to reset the speech encoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (GSM 06.06 [7]), all speech encoder output frames shall be identical to the corresponding frame in the \*.COD file. In the case of a correct hardware implementation undergoing type approval, the first speech encoder output frame is undefined and need not be identical to the first frame in the \*.COD file, but all remaining speech encoder output frames shall be identical to the corresponding frames in the \*.COD file. + +Each \*.DEC file includes two homing frames at the start of the test sequence. The function of these frames is to reset the speech decoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (GSM 06.06 [7]), all speech decoder output frames shall be identical to the corresponding frame in the \*.OUT file. In the case of a correct hardware implementation undergoing type approval, the first speech decoder output frame is undefined and need not be identical to first frame in the \*.OUT file, but all remaining speech decoder output frames shall be identical to the corresponding frames in the \*.OUT file. + +**Table 1: Encoder input sequence (\*.INP) format** + +| Name | Description | No. of bits | Justification | +|------|----------------------|-------------|---------------| +| s(n) | Encoder input signal | 13 | Left | + +**Table 2: Encoder output sequence (\*.COD) format** + +| Name | Description | No. of words | Justification | +|------------------------|------------------------------------------|--------------|---------------| +| Speech | Speech parameters to the channel encoder | 18 | Right | +| Additional information | | | | +| VAD | Voice activity detection flag | 1 | Right | +| SP | SP flag | 1 | Right | + +**Table 3: Decoder input sequence (\*.DEC) format** + +| Name | Description | No. of bits/words | Justification | +|-------------------|------------------------------------------|-------------------|---------------| +| Speech parameters | Speech parameters to the channel encoder | 18 words | Right | +| BFI flag | Bad Frame Indicator | 1 bit / 1 word | Right | +| UFI flag | Unreliable Frame Indicator | 1 bit / 1 word | Right | +| SID flag | Silence Descriptor | 2 bits / 1 word | Right | +| TAF flag | Time Alignment Flag | 1 bit / 1 word | Right | + +**Table 4: Decoder output sequence (\*.OUT) format** + +| Name | Description | No. of bits | Justification | +|-------|-----------------------|-------------|---------------| +| s'(n) | Decoder output signal | 13 | Left | + +# 6 Speech codec test sequences + +This clause describes the test sequences designed to exercise the GSM half rate speech transcoder (GSM 06.20 [2]). + +## 6.1 Codec configuration + +The speech encoder shall be configured to operate in the non-DTX mode. The VAD and SP flags shall be set to 1 at the speech encoder output. + +## 6.2 Speech codec test sequences + +Table 5 lists the location and size of the speech codec test sequences. + +### 6.2.1 Speech encoder test sequences + +Three encoder input sequences are provided: + +- SEQ01.INP - Sequence for exercising the LPC vector quantization codebooks; +- SEQ02.INP - Sequence for exercising the long term predictor codebooks; +- SEQ03.INP - Sequence for exercising the remaining excitation codebooks. + +The SEQ01.INP sequence causes the GSM half rate speech encoder to select every vector in the three reflection coefficient vector quantizers at least once. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the SEQ01.COD sequence. + +The SEQ02.INP sequence causes the encoder to select at least once every quantization level in the eight bit table of long term filter lags for the first subframe, and every quantization level in the four bit delta lag quantizer for subframes 2, 3, and 4. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the SEQ02.COD sequence. + +The SEQ03.INP sequence causes the encoder to select each of the quantization levels at least once for the remaining GSM half rate speech coder parameters: R0 (frame energy), the soft interpolation decision for the LPC coefficients, the four voicing modes, the gain vectors (GSP0) for each of the voicing modes, and the voiced and unvoiced VSELP codebooks. The only exception to this is that two GSP0 levels in the unvoiced mode are not selected. However, these levels are exercised in the GSM half rate speech decoder as described below. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the SEQ03.COD sequence. + +### 6.2.2 Speech decoder test sequences + +Four speech decoder input sequences are provided: + +- SEQ01.DEC; +- SEQ02.DEC; +- SEQ03.DEC; +- SEQ04.DEC. + +The SEQ01.DEC, SEQ02.DEC, and SEQ03.DEC sequences test the operation of the GSM half rate speech decoder in the absence of channel errors. They are derived from the corresponding SEQXX.INP sequences. In a correct implementation, the resulting speech decoder output shall be identical to the SEQ01.OUT, SEQ02.OUT, and SEQ03.OUT sequences, respectively. Together, these three sequences exercise every quantization level in every codebook in the decoder, with the exception of two GSP0 levels in the unvoiced mode. + +The SEQ04.DEC sequence is designed to test the GSM half rate speech decoder under conditions which can result from channel errors. In particular, it is the decoding of LTP lags at the lag table boundaries, given delta lag codes which if incorrectly decoded would point outside the eight bit lag table, that is being tested. Also, the two remaining GSP0 levels in the unvoiced mode are exercised by this sequence. In a correct implementation, the resulting speech decoder output shall be identical to the SEQ04.OUT sequence. + +### 6.2.3 Codec homing sequence + +In addition to the test sequences described above, two homing sequences are provided to assist in codec type approval testing. SEQ05.INP contains one encoder-homing-frame. SEQ05.DEC contains one decoder-homing-frame. The use of these sequences is described in GSM 06.02 [8]. + +**Table 5: Location and size of speech codec test sequences** + +| Disk No. | File Name | No. of frames | Size (bytes) | +|----------|-----------|---------------|--------------| +| 1 | SEQ01.INP | | 754 880 | +| 1 | SEQ01.COD | 2 359 | 94 360 | +| 2 | SEQ01.DEC | | 103 796 | +| 2 | SEQ01.OUT | | 754 880 | +| 1 | SEQ02.INP | | 249 920 | +| 1 | SEQ02.COD | 781 | 31 240 | +| 2 | SEQ02.DEC | | 34 364 | +| 2 | SEQ02.OUT | | 249 920 | +| 1 | SEQ03.INP | | 132 160 | +| 1 | SEQ03.COD | 413 | 16 520 | +| 2 | SEQ03.DEC | | 18 172 | +| 2 | SEQ03.OUT | | 132 160 | +| 2 | SEQ04.DEC | 76 | 3 344 | +| 2 | SEQ04.OUT | | 24 320 | +| 1 | SEQ05.INP | 1 | 320 | +| 2 | SEQ05.DEC | | 44 | + +# 7 DTX test sequences + +This clause describes the test sequences designed to exercise the VAD algorithm (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and discontinuous transmission (GSM 06.41 [5]). + +## 7.1 Codec configuration + +The VAD, comfort noise and discontinuous transmission shall be tested in conjunction with the speech encoder [2]). The speech encoder shall be configured to operate in the DTX mode defined in GSM 06.22 [4]. + +## 7.2 DTX test sequences + +Each DTX test sequence consists of four files: + +- Files for input to the GSM half rate speech encoder: \*.INP +- Files for comparison with the encoder output \*.COD +- Files for input to the GSM half rate speech decoder: \*.DEC +- Files for comparison with the decoder output: \*.OUT + +The \*.DEC files are generated from the corresponding \*.COD files. + +In a correct implementation, the speech encoder parameters generated by the \*.INP file shall be identical to those specified in the \*.COD file; and the speech decoder output generated by the \*.DEC file shall be identical to that specified in the \*.OUT file. + +Table 6 lists the DTX test sequences and their size in frames. + +### 7.2.1 Predictor values computation + +The computation of the predictor values described in GSM 06.42 [6] is not tested explicitly, since the results from the computation are tested many times via the spectral comparison and threshold adaptation tests. + +### 7.2.2 Spectral comparison + +The spectral comparison algorithm described in GSM 06.42 [6] is tested by the following test sequence: + +- DTX01.\* + +### 7.2.3 Threshold adaptation + +The threshold adaptation algorithm described in GSM 06.42 [6] is tested by the following test sequence: + +- DTX02.\* + +### 7.2.4 Periodicity detection + +The periodicity detection algorithm described in GSM 06.42 [6] is tested by the following test sequence: + +- DTX03.\* + +### 7.2.5 Tone detection + +The tone detection algorithm described in GSM 06.42 [6] is tested by the following test sequence: + +- DTX04.\* + +### 7.2.6 Safety and initialization + +This sequence checks the safety paths used to prevent zero values being passed to the norm function. It checks the functions described in the adaptive filtering and energy computation, and the prediction values computation given in GSM 06.42 [6]. This sequence also checks the initialization of thvad and the rvad array: + +- DTX05.\* + +### 7.2.7 Comfort noise test sequence + +The test sequences described in sub-clauses 7.2.2 to 7.2.6 are designed to exercise the VAD described in GSM 06.42 [6] and the discontinuous transmission described in GSM 06.41 [5]. The following test sequence is defined to exercise the comfort noise algorithm described in GSM 06.22 [4]: + +- DTX06.\* + +### 7.2.8 Real speech and tones + +The test sequences cannot be guaranteed to find every possible error. There is therefore a small possibility that an incorrect implementation produces the correct output for the test sequences, but fails with real signals. Consequently, an extra sequence is included, which consists of very clean speech, barely detectable speech and a swept frequency tone: + +- DTX07.\* + +NOTE: Some of the DTX test sequences contain homing frames. The DTX test sequences are therefore only suitable for testing a single transcoding. + +**Table 6: Location and size of DTX test sequences** + +| Disk No. | File Name | No. of Frames | size (bytes) | | | | +|----------|-----------|---------------|--------------|--------|--------|---------| +| | | | *.INP | *.COD | *.DEC | *.OUT | +| 3 | DTX01 | 460 | 147 200 | 18 400 | 20 240 | 147 200 | +| 3 | DTX02 | 886 | 283 520 | 35 440 | 38 984 | 283 520 | +| 3 | DTX03 | 125 | 40 000 | 5 000 | 5 500 | 40 000 | +| 3 | DTX04 | 317 | 101 440 | 12 680 | 13 948 | 101 440 | +| 3 | DTX05 | 37 | 11 840 | 1 480 | 1 628 | 11 840 | +| 4 | DTX06 | 240 | 76 800 | 9 600 | 10 560 | 76 800 | +| 4 | DTX07 | 1 188 | 380 160 | 47 520 | 52 272 | 380 160 | + +# 8 Sequences for finding the 20 ms framing of the GSM half rate speech encoder + +When testing the decoder, alignment of the test sequences used to the decoder framing is achieved by the air interface (testing of MS) or can be reached easily on the Abis-interface (testing on network side). + +When testing the encoder, usually there is no information available about where the encoder starts its 20 ms segments of speech input to the encoder. + +In the following, a procedure is described to find the 20 ms framing of the encoder using special synchronization sequences. This procedure can be used for MS as well as for network side. + +Synchronization can be achieved in two steps. First, bit synchronization has to be found. In a second step, frame synchronization can be determined. This procedure takes advantage of the codec homing feature of the half rate codec, which puts the codec in a defined home state after the reception of the first homing frame. On the reception of further homing frames, the output of the codec is predefined and can be triggered to. + +## 8.1 Bit synchronization + +The input to the speech encoder is a series of 13 bit long words (104 kbits/s, 13 bit linear PCM). When starting to test the speech encoder, no knowledge is available on bit synchronization, i.e. where the encoder expects its least significant bits, and where it expects the most significant bits. + +The encoder homing frame consists of 160 samples, all set to zero with the exception of the least significant bit, which is set to one (0 0000 0000 0001 binary, or 0x0008 hex if written into 16 bit words left justified). If two such encoder homing frames are input to the encoder consecutively, the decoder homing frame is expected at the output as a reaction of the second encoder homing frame. + +Since there are only 13 possibilities for bit synchronization, after a maximum of 13 trials bit synchronization can be reached. In each trial, three consecutive encoder homing frames are input to the encoder. If the decoder homing frame is not detected at the output, the relative bit position of the three input frames is shifted by one and another trial is performed. As soon as the decoder homing frame is detected at the output, bit synchronization is found, and the first step can be terminated. + +The reason why three consecutive encoder homing frames are needed is that frame synchronization is not known at this stage. To be sure that the encoder reads two complete homing frames, three frames have to be input. Wherever the encoder has its 20 ms segmentation, it will always read at least two complete encoder homing frames. + +An example of the 13 different frame triplets is given in sequence BITSYNC.INP (see table 7). + +## 8.2 Frame synchronization + +Once bit synchronization is found, frame synchronization can be found by inputting one special frame that delivers 160 different output frames, depending on the 160 different positions that this frame can possibly have with respect to the encoder framing. + +This special synchronization frame was found by taking one input frame and shifting it through the positions 0 to 159. The corresponding 160 encoded speech frames were calculated and it was verified that all 160 output frames were different. When shifting the input synchronization frame, the samples at the beginning were set to 0x0008 hex, which corresponds to the samples of the encoder homing frame. + +Before inputting this special synchronization frame to the encoder, again the encoder has to be reset by one encoder homing frame. A second encoder homing frame is needed to provoke a decoder homing frame at the output that can be triggered to. And since the framing of the encoder is not known at that stage, three encoder homing frames have to precede the special synchronization frame to ensure that the encoder reads at least two homing frames, and at least one decoder homing frame is produced at the output, serving as a trigger for recording. + +The special synchronization frame preceded by the three encoder homing frames are given in SEQSYNC.INP. The corresponding 160 different output frames are given in SYNC000.COD through SYNC159.COD. The three digit number in the filename indicates the number of samples by which the input was retarded with respect to the encoder framing. By a corresponding shift in the opposite direction, alignment with the encoder framing can be reached. + +## 8.3 Formats and sizes of the synchronization sequences + +### BIT SYNC.INP: + +This sequence consists of 13 frame triplets. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero). + +The size of it is therefore: + +$$\text{SIZE (BITSYNC.INP)} = 13 * 3 * 160 * 2 \text{ bytes} = 12480 \text{ bytes.}$$ + +### SEQSYNC.INP: + +This sequence consists of 3 encoder reset frames and the special synchronization frame. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero). + +The size of it is therefore: + +$$\text{SIZE (SEQSYNC.INP)} = 4 * 160 * 2 \text{ bytes} = 1280 \text{ bytes.}$$ + +### SYNCXXX.COD: + +These sequences consists of 1 encoder output frame each. They have the format of the speech encoder output test sequences (16 bit words right justified). The values of the VAD and SP flags are set to one in these files. + +The size of them is therefore: + +$$\text{SIZE (SYNCXXX.COD)} = (18 + 2) * 2 \text{ bytes} = 40 \text{ bytes}$$ + +Table 7 summarizes this information. + +**Table 7: Location, size and justification of synchronization sequences** + +| Disk No. | Purpose of Sequence | Name of Sequence | No. of Frames | Size in Bytes | Justification | +|----------|--------------------------------|-------------------------------------------------------------------------|---------------------------------|-------------------------------------|-------------------------------------------------| +| 5 | Bit Synchronization | BITSYNC.INP | 39 | 1 2480 | Left | +| 5 | Frame Synchronization (input) | SEQSYNC.INP | 4 | 1 280 | Left | +| 5 | Frame Synchronization (output) | SYNC000.COD
SYNC001.COD
SYNC002.COD
"
"
"
SYNC159.COD | 1
1
1
"
"
"
1 | 40
40
40
"
"
"
40 | Right
Right
Right
"
"
"
Right | + +# 9 Trau Testing with 8 Bit A- and $\mu$ -law PCM Test Sequences + +In the previous clauses tests for the transcoder in the TRAU are described using 13 bit linear test sequences. However, these 13 bit test sequences require a special interface in the Trau and do not allow testing in the field. In most cases the TRAU has to be set in special mode before testing. + +As an option, the speech codec tests can be performed with A/ $\mu$ law compressed 8 bit PCM test sequences on the A interface. These modified input test sequences (\*.X.INP) are generated from the original sequences by A or $\mu$ law compression. As an input to the encoder they result in modified encoder output sequences (\*.X.COD). The same \*.dec decoder input sequences as in clause 6.2.2. are then used to produce the output sequences \*.X.OUT, which are A- or $\mu$ -law compressed. + +The A- and $\mu$ -law compression and decompression does not change the homing frames at the encoder input. The format of all A- and $\mu$ -law PCM files \*.X.INP and \*.X.OUT is one sample (8 bit) per byte. The format of all other files is as described in clause 5. + +All files are provided in archive en\_300968v080001p0.ZIP which accompanies the present document. The 'X' in the tables below with the filenames stands for A (A-law) and U ( $\mu$ -law), respectively. The decoder input files \*.dec are the same as in Table 5 and are not described in this clause. + +**Table 8: Location and size of compressed 8 bit PCM speech codec test sequences** + +| Disk No. | File Name | No. of frames | Size (bytes) | +|----------|-------------|---------------|--------------| +| 6/7 | SEQ01-X.INP | 2 359 | 377 440 | +| 6/7 | SEQ01-X.COD | | 94 360 | +| 6/7 | SEQ01-X.OUT | | 377 440 | +| 6/7 | SEQ02-X.INP | 781 | 124 960 | +| 6/7 | SEQ02-X.COD | | 31 240 | +| 6/7 | SEQ02-X.OUT | | 124 960 | +| 6/7 | SEQ03-X.INP | 413 | 66 080 | +| 6/7 | SEQ03-X.COD | | 16 520 | +| 6/7 | SEQ03-X.OUT | | 66 080 | +| 6/7 | SEQ04-X.OUT | 76 | 12 160 | +| 6/7 | SEQ05-X.INP | 1 | 160 | + +**Table 9: Location and size of compressed 8 bit PCM DTX test sequences** + +| Disk No. | File Name | No. of Frames | size (bytes) | | | +|----------|-----------|---------------|--------------|--------|---------| +| | | | *.INP | *.COD | *.OUT | +| 8/9 | DTX01-X | 460 | 73 600 | 18 400 | 73 600 | +| 8/9 | DTX02-X | 886 | 141 760 | 35 440 | 141 760 | +| 8/9 | DTX03-X | 125 | 20 000 | 5 000 | 20 000 | +| 8/9 | DTX04-X | 317 | 50 720 | 12 680 | 50 720 | +| 8/9 | DTX05-X | 37 | 5 920 | 1 480 | 5 920 | +| 8/9 | DTX06-X | 240 | 38 400 | 9 600 | 38 400 | +| 8/9 | DTX07-X | 1 188 | 190 080 | 47 520 | 190 080 | + +In addition to the test sequences above, special input (seqsyncX.inp) and output (syncxxxX.cod) sequences for frame synchronization are provided. The X again stands for A and $\mu$ law compressed PCM. The synchronization procedure is described in clause 8. + +**Table 10: Location, size and justification of compressed8 bit PCM test sequences** + +| Disk No. | Purpose of Sequence | Name of Sequence | No. of Frames | Size in Bytes | Justification | +|----------|--------------------------------|----------------------------------------------------------------------------------|--------------------------------------|------------------------------------------|------------------------------------------------------| +| 10/11 | Frame Synchronization (input) | SEQSYNCX.INP | 4 | 640 | - | +| 10/11 | Frame Synchronization (output) | SYNC000X.COD
SYNC001X.COD
SYNC002X.COD
"
"
"
"
SYNC159X.COD | 1
1
1
"
"
"
"
1 | 40
40
40
"
"
"
"
40 | Right
Right
Right
"
"
"
"
Right | + +# 10 Test sequences for the GSM half rate speech codec + +NOTE: This clause is contained in archive en\_300968v080001p0.ZIP which accompanies the present document. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|-----------------------------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#16 | | | | 4.0.3 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#23 | 97-737 | A003 | | 5.1.1 | UAP60 and Supplementary notes on 06.06 Call Graph Changes | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#28 | | | | 6.0.1 | ETSI Publication | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|------------------------------------------------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | +| 2020-10 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2020-10 | 88-e | | | | | Post SA#88-e, Updated after insertion of correct document in the zipped file | 16.0.1 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46008/raw.md b/marked/Rel-18/46_series/46008/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ea899a36f2bbe87c0a6061066fce7eaf61d23ea0 --- /dev/null +++ b/marked/Rel-18/46_series/46008/raw.md @@ -0,0 +1,732 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Half rate speech; Performance characterization of the GSM half rate speech codec (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The GSM logo consists of the letters 'GSM' in a stylized blue font. The 'G' and 'S' are connected at the top by a single horizontal bar. The 'M' is composed of two 'A'-like shapes joined at the top. To the right of the 'M' is a small red square. Below the letters, the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' is written in a smaller, blue, sans-serif font. A registered trademark symbol (®) is located to the right of the 'M'. + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo features the letters '3GPP' in a bold, black, stylized font. The '3' is a standard digit. The 'G' and 'P' are connected at the top by a single horizontal bar. The 'P' has a small red signal icon below it, consisting of three curved lines. A trademark symbol (TM) is located to the top right of the 'P'. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## --- **Keywords** + +Digital cellular telecommunications system, +Global System for Mobile communications (GSM) + +## **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------------|-----------| +| ContentsForeword ..... | 3 | +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Abbreviations..... | 6 | +| 4 Quality under error conditions (A-law, IRS), Experiment 1..... | 7 | +| 5 Quality under error conditions (UPCM, No IRS), Experiment 2 ..... | 7 | +| 6 Quality under tandeming conditions..... | 8 | +| 6.1 Quality under tandeming conditions, Experiment 3..... | 8 | +| 6.2 Effect of tandeming with other standards, Experiment 7 ..... | 8 | +| 7 Quality under background noise conditions..... | 9 | +| 7.1 Experiments 4 and 5..... | 9 | +| 7.2 Special background noise..... | 10 | +| 7.2.1 Introduction ..... | 10 | +| 7.2.2 Observations ..... | 10 | +| 8 Assessment of equivalent qdu, Experiment 6..... | 11 | +| 9 Talker dependency, Experiment 8 ..... | 11 | +| 10 DTX System..... | 11 | +| 10.1 Assessment of DTX algorithm, Experiment 9 ..... | 11 | +| 10.2 Channel activity in DTX mode ..... | 12 | +| 10.2.1 Test procedure ..... | 12 | +| 10.2.2 Speech channel activity ..... | 12 | +| 10.2.3 Level compensation..... | 12 | +| 10.2.4 SID update rate ..... | 12 | +| 10.2.5 Interleaving compensation..... | 12 | +| 10.2.6 Estimated mean TDMA channel activity ..... | 12 | +| 11 Performance with DTMF tones..... | 13 | +| 11.1 Introduction ..... | 13 | +| 11.2 Test set-up ..... | 13 | +| 11.3 Results ..... | 13 | +| 11.4 Conclusions ..... | 14 | +| 11.5 Result tables of experiments with standard and modified DTMF detectors ..... | 14 | +| 12 Performance with signalling tones..... | 14 | +| 13 Delay ..... | 15 | +| 14 Frequency response..... | 15 | +| 15 Half Rate codec complexity..... | 17 | +| 16 Summary of results from characterization Phase 1 and 2..... | 17 | +| 16.1 Summary of Results From Characterization Phase 1..... | 17 | +| 16.2 Summary of Results From Characterization Phase 2..... | 19 | +| 16.3 Conclusion..... | 19 | +| Annex A: Bibliography | 20 | +| Annex B: Change history | 21 | + +# 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. + +# --- Introduction + +During five years of activity, the Traffic CHannel Half rate Speech (TCH-HS) Experts Group has produced a number of test plans and experiments to assess the performance of the candidate algorithms submitted for the GSM half rate standardization. An aid in this task was a large knowledge base made available from previous CCITT (now ITU-T) and ETSI activities on codec assessment (see annex A references 1) 2) 3) 4) 5)), plus the use of recommendations in the field (see annex A references 6) 7) 8)). + +Here are reported 3 different phases of the standardization of the GSM half rate codec: Characterization Phase 1, Characterization Phase 2 and Verification phase. The selection of the codec candidate for the GSM half rate traffic channel was based on the results of the characterization phase 1. Test results reported hereafter are based on version 3.3 of the GSM half rate codec. + +**Characterization Phase 1** (Experiments 1 to 5): For characterization Phase 1, C-simulations of the candidate codecs were used as hardware implementations were not available at that time. The simulations were produced by MOTOROLA (USA) and Ericsson (Sweden) with support by MATRA (France). The following experiments were carried out: + +- Experiment 1: Quality under error conditions (A-law, IRS); +- Experiment 2: Quality under error conditions (UPCM, No IRS); +- Experiment 3: Quality under tandeming conditions; +- Experiment 4: Quality under background noise conditions (ACR); +- Experiment 5: Quality under background noise conditions (DCR). + +**Characterization Phase 2** (Experiments 6 to 9): During Characterization Phase 2, a hardware implementation of the candidate algorithm was employed, provided by ANT (Germany). The following experiments were carried out: + +- Experiment 6: Assessment of equivalent qdu; +- Experiment 7: Effect of tandeming with other standards; +- Experiment 8: Talker Dependency; +- Experiment 9: Assessment of DTX algorithm. + +**Verification phase:** Further tests accompanied characterization Phase 1 and 2 to obtain a better knowledge of the characteristics of the GSM half rate codec and its performance under different operational conditions: + +- Special background noise; +- Channel activity in DTX mode; +- Performance with DTMF tones; +- Performance with signalling tones; +- Delay; +- Frequency response; +- Complexity. + +For the characterization tests, a practical "indirect" method of performance comparison between different codecs was adopted, that utilizes the Modulated Noise Reference Unit (MNRU) (see annex A reference 7)) as a reference degradation in a subjective experiment including the codecs under test. + +NOTE: The MNRU is a device designed for producing speech correlated noise that sounds subjectively like the quantizing noise produced by log-companded PCM codecs. The device is subjectively calibrated for Mean Opinion Scores (MOS) against Q dB (where Q is the ratio of the speech to speech-correlated noise power). The "Equivalent Q" of the codecs under test can then be found from the corresponding MOS on the calibration curve of the MNRU. + +It is well known that this procedure works as long as the reference degradation sounds similar to the degradation under test. + +The MNRU provides the additional function of normalization across laboratories carrying out the same experiment, i.e. all MOS are converted to Equivalent Q (dB) and the results can be analysed statistically for differences between laboratories. An appropriate analysis of variance (ANOVA) was identified to evaluate the statistical significance of the experimental factors. + +The aim was to show that the subjective performance of the GSM half rate algorithm is at least as good as that of the full rate codec over a selected set of conditions. To allow for experimental error, the half rate candidate had to perform better than 1 dB below the performance of the full rate (for the overall figure of merit) and better than 3 dB below the performance of the full rate for individual test conditions. + +To model its use in a network, the half rate candidate codec had to be placed between either a ITU-T Recommendation G.711 [1] PCM coder and decoder, or a Uniform PCM, which provided the necessary A/D and D/A conversions. Source files of speech, produced either by using an "average" telephone set (called IRS - Intermediate Reference System) or a microphone showing a "flat" sending frequency characteristic (No IRS or "flat"), could then be processed through the different experimental conditions, for presentation to subjects in listening experiments. Among the different experimental conditions were error conditions at different input levels under both IRS A-Law PCM and No-IRS Linear PCM audio parts, tandeming conditions for different error patterns and background noise conditions. During all phases of testing, the host laboratory functions for the processing were provided by Aachen University of Technology (RWTH at Aachen, Germany). + +The whole set of "individual" and "global" data, collected in Experiment 1 to Experiment 9 were extensively analysed and discussed within TCH-HS expert group; for each condition, the MOS (or DMOS for Experiment 5) were computed, separately for male and female speech, as well as averaged together, and the effects of different factors and their interactions were subject to analysis of variance (ANOVA). Within characterization Phase 1, conversion to Q values and weighted averages were calculated for the whole set of results, in order to assess that the global figure of merit of the GSM half rate algorithm meets the quality requirement. + +# --- 1 Scope + +The present document gives background information on the performance of the GSM half rate speech codec. Experimental results from the characterization and verification tests carried out during the selection process by the Traffic CHannel Half rate Speech (TCH-HS) expert group are reported to give a more detailed picture of the behaviour of the GSM half rate speech codec under different conditions of operation. + +# --- 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 G.711: "Pulse code modulation (PCM) of voice frequencies". +- [2] ITU-T Recommendation G.726: "40, 32, 24, 16 kbit/s adaptive differential pulse code modulation". +- [3] ITU-T Recommendation G.728: "Coding of speech at 16 kbit/s using low-delay code excited linear prediction". + +# --- 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------------------------------------------------------| +| A/D | Analogue to Digital | +| ACR | Absolute Category Rating | +| ANOVA | ANalysis Of VAriance | +| C/I | Carrier-to-Interferer ratio | +| CEPT | Conférence Européenne des Postes et Télécommunications | +| CNI | Comfort Noise Insertion | +| D/A | Digital to Analogue | +| DAT | Digital Audio Tape | +| DCR | Degradation Category Rating | +| DSP | Digital Signal Processor | +| DTMF | Dual Tone Multi Frequency | +| DTX | Discontinuous Transmission for power consumption and interference reduction | +| EID | Error Insertion Device | +| ETSI | European Telecommunications Standards Institute | +| GBER | Average gross bit error rate | +| GSM | Global System for Mobile communications | +| IRS | Intermediate Reference System, No IRS= rather flat | +| HLCS | Host Laboratory Control System | +| ITU-T | International Telecommunication Union - Telecommunications Standardization Sector | +| MNRU | Modulated Noise Reference Unit | +| MOS | Mean Opinion Score | +| MS | Mobile Station | +| OVL | Overload point | +| PCM | Pulse Code Modulation | + +| | | +|---------|-------------------------------------------------------| +| Q | Speech-to-speech correlated noise power ratio in dB | +| qdu | quantization distortion unit | +| RPE-LTP | Regular Pulse Excited codec with Long Term Prediction | +| SCD | Signal Conditioning Device | +| SFC | Sending Frequency Characteristic | +| SID | Silence Descriptor | +| SMG | Special Mobile Group | +| SNR | Signal to Noise Ratio | +| TCH-HS | Traffic CHannel Half rate Speech | +| TDMA | Time Division Multiple Access | +| UPCM | Uniform or Linear PCM | +| VAD | Voice Activity Detector | +| wMOPs | Weighted Million OPerations per second | + +Four different Error Patterns (EP0, EP1, EP2 and EP3) were used, where: + +- EP0 without channel errors; +- EP1 C/I=10 dB; 5 % GBER (well inside a cell); +- EP2 C/I= 7 dB; 8 % GBER (at a cell boundary); +- EP3 C/I= 4 dB; 13 % GBER (outside a cell). + +# 4 Quality under error conditions (A-law, IRS), Experiment 1 + +A listening-only test was chosen, adopting the Absolute Category Rating (ACR) method. + +Subjective tests were carried out by BT (United Kingdom), CSELT (Italy), and Deutsche Telekom (Germany). Table 1 reports the results obtained in Experiment 1: each cell shows the difference in terms of equivalent Q values between the candidate and the full rate, negative values meaning worse performance than the full rate. + +**Table 1: Results from experiment 1 (A-law, IRS)** + +| Error Pattern | Input Level
(dB relative to OVL) | | | +|---------------|-------------------------------------|-------|-------| +| | -12 | -22 | -32 | +| EP0 | -0,27 | -0,02 | 0,34 | +| EP1 | -0,26 | -0,86 | -0,59 | +| EP2 | -0,49 | -1,61 | 1,14 | +| EP3 | -0,39 | 1,79 | 3,80 | + +NOTE: The figures in table 1 indicate DQ values in dB, where $DQ = Q_{HR} - Q_{FR}$ . + +In general, the candidate codec performed equally well or slightly worse than the full rate (in any case never exceeded the -3 dB limit). + +# 5 Quality under error conditions (UPCM, No IRS), Experiment 2 + +A listening-only test was chosen, adopting the Absolute Category Rating (ACR) method. + +Subjective tests were carried out by BT (United Kingdom), CSELT (Italy), and DEUTSCHE TELEKOM (Germany). Table 2 reports the results obtained in Experiment 2: each cell shows the difference in terms of equivalent Q values between the candidate and the full rate codec, negative values meaning worse performance than the full rate codec. + +**Table 2: Results from experiment 2 (UPCM, No IRS)** + +| Error Pattern | Input Level
(dB relative to OVL) | | | +|---------------|-------------------------------------|-------|-------| +| | -12 | -22 | -32 | +| EP0 | -1,13 | -2,90 | -1,70 | +| EP1 | -3,72 | -1,72 | -1,21 | +| EP2 | -1,93 | -1,79 | 0,69 | +| EP3 | 0,79 | 1,49 | 3,59 | + +NOTE: The figures indicate DQ values in dB, where $DQ = Q_{HR} - Q_{FR}$ . + +In general, the candidate codec performed equally well or slightly worse than the full rate (in one case, at -12 dB relative to Overload point (OVL) in EP1 condition, $Q_{HR} - Q_{FR}$ exceeded the -3 dB limit). + +# 6 Quality under tandeming conditions + +## 6.1 Quality under tandeming conditions, Experiment 3 + +A listening-only test was chosen, adopting the Absolute Category Rating (ACR) method. Subjective tests were carried out by BT (United Kingdom), CSELT (Italy), and DEUTSCHE TELEKOM (Germany). Table 3 reports the results obtained in Experiment 3: each cell shows the difference in terms of equivalent Q values between the candidate and the full rate, negative values meaning worse performance than the full rate. + +**Table 3: Results from experiment 3 (Tandem Conditions)** + +| Error Pattern | A-Law PCM (with IRS)
$DQ (dB) = (HR+HR)-(FR+FR)$ | | | Linear PCM (No IRS)
$DQ (dB) = (HR+HR)-(FR+FR)$ | | | +|---------------|-----------------------------------------------------|-------|-------|----------------------------------------------------|--------------|--------------| +| | Input Level
(dB relative to OVL) | | | Input Level
(dB relative to OVL) | | | +| | -12 | -22 | -32 | -12 | -22 | -32 | +| EP0 | -0,14 | -0,56 | -0,03 | -5,20 | -5,43 | -3,89 | +| EP1 | -0,46 | -0,75 | 0,49 | -4,98 | -4,14 | -2,79 | + +NOTE: The figures indicate DQ values in dB, where $DQ = Q_{HR} - Q_{FR}$ . + +In general, two candidate codecs in tandem performed equally well or slightly worse than two full rate codecs in tandem for the A-Law IRS audio part, while in most cases exceeded the -3 dB limit for the Uniform PCM No IRS audio part. + +In operating networks, A-law coding and decoding is performed between both speech processing steps in both mobile to mobile calls. Therefore, the results of real network configurations are expected to be somewhere in between the figures obtained using the A-law input speech material and those obtained using the linear PCM speech material for each condition. + +## 6.2 Effect of tandeming with other standards, Experiment 7 + +The experiment was conducted in two different laboratories: BT (UK) and CNET (France). + +The following standards were tandemed with the half rate codec in this experiment: half rate, full rate, ITU-T Recommendation G.726 [2] (at 32 kbit/s) and G.728 [3]. Both possible orders of tandeming were tested for each of these cases, in both error free and EP1 conditions. The error pattern EP1 was only applied to the full and half rate codecs. + +The main conclusion that can be drawn is that the performance is always better when the half rate codec follows the other codec in the tandeming chain. This effect is most pronounced at the higher speech input level (12 dB below overload point). + +# 7 Quality under background noise conditions + +## 7.1 Experiments 4 and 5 + +International subjective test programs have been conducted in the past, by both the ITU and ETSI, to investigate the effects of environmental noise. This has proved to be a difficult area to evaluate, and more satisfactory methodologies are continually being sought to improve the accuracy of these tests. Several methodologies have been used recently to investigate this factor: + +- the ACR (Absolute Category Rating) method using the classical Quality scale (second selection phase of the GSM half rate speech coding algorithm candidate, 1992); +- the ACR method using the Listening Effort scale (second pre-selection test of the GSM Half Rate candidate, 1992); +- the DCR (Degradation Category Rating) method such as in the ITU-T test methodology for the 16 kbit/s and 8 kbit/s speech coders which is an adapted version of the standard DCR procedure (described in ITU-T Recommendation P.80) and where several types of noise at different Signal-to-Noise ratios were evaluated in a unique experiment; +- the DCR procedure adapted such as in the first pre-selection phase of testing for the GSM half rate candidates in 1991, where only one distinct noise has been tested in the same experiment in order to prevent the noise from being the predominant factor within the test; two experiments were, then, designed to take into account two types of noise: babble noise at a SNR of 30 dB and vehicle noise at a SNR of 10 dB. + +Analysis of results gathered from these four experimental designs led to the conclusion that the last procedure - DCR test per noise (d) - is the most appropriate one to study the effects of environmental noise on a codec's behaviour. + +For the final characterization phase of testing, it was decided to follow up two methodologies: the ACR and the DCR methods, i.e. to formally compare two distinct modes of collecting the subjects' responses with exactly the same experimental test plan (four 24 x 24 interleaved graeco-latin squares). The following environmental noises were considered of interest: office babble, vehicular, and traffic. + +A listening-only test was chosen, adopting, for Exp. 4, the Absolute Category Rating (ACR) method, and subjective tests were carried out by BT (United Kingdom) and DEUTSCHE TELEKOM (Germany), while a modified version of the Degradation Category rating (DCR) was agreed for Exp. 5, and subjective tests were carried out by CNET (France) and CSELT (Italy). + +Table 4 and 5 report the results obtained in experiment 4 and 5, respectively: each cell shows the difference in terms of equivalent Q values between the candidate and the full rate, negative values meaning worse performance than the full rate. + +**Table 4: Results from experiment 4 (ACR)** + +| Noise | Office Babble | Vehicular | Traffic | +|-------------------|---------------|--------------|--------------| +| Low noise | -0,78 | -2,19 | -1,06 | +| High Noise | -1,75 | -0,87 | -1,25 | +| Low Noise Tandem | -1,75 | -2,38 | -2,66 | +| High Noise Tandem | -2,99 | -4,10 | -3,09 | + +NOTE: The figures indicate DQ values in dB, where $DQ = Q_{HR} - Q_{FR}$ . + +**Table 5: Results from experiment 5 (DCR)** + +| Noise | Office Babble | Vehicular | Traffic | +|-------------------|---------------|--------------|--------------| +| Low noise | -2,10 | -2,96 | -4,53 | +| High Noise | -2,79 | -2,83 | -2,04 | +| Low Noise Tandem | -4,03 | -4,39 | -5,31 | +| High Noise Tandem | -4,96 | -5,85 | -5,68 | + +NOTE: The figures indicate DQ values in dB, where $DQ = Q_{HR} - Q_{FR}$ . + +The main conclusion that can be drawn is that the performance of the half rate codec is (always) worse than that of the full rate, the amount of perceived degradation, in terms of DQ in dB, depending on the method chosen for the test (DCR being clearly more discriminant than ACR). Such background noise effect is most pronounced in tandem conditions. + +## 7.2 Special background noise + +### 7.2.1 Introduction + +Some informal listening sessions were carried out to further investigate background noise effects. Speech samples from four different talkers were electronically mixed (at 3 different Signal-to-Noise Ratios; 5 dB, 10 dB, and 20 dB) with a wide range of different background noises, reflecting the following types of environment: + +- Industrial Setting; +- Babble (offices and public places such as airports); +- Trains; +- Cars and Lorries; +- Roadside. + +These were processed through a simulation of the Half Rate codec (with no DTX) and were listened to (on an informal basis) under controlled listening conditions using headphones. + +No formal method of voting or opinion collation was employed; observations were simply noted. + +### 7.2.2 Observations + +At the lower Signal-to-Noise Ratios, the speech was often unintelligible without considerable concentration and effort on the part of the listener. In some cases, even where the listener was familiar with the speech material, it was impossible to understand some parts of the speech. + +The codec had the effect of making the background noises sound "babble", which, for example, made most background noises sound more "busy". This effect was particularly bad at 5 dB SNR. At 10 dB, the listening was more comfortable although parts of it were still difficult to understand. At 20 dB the speech was clearly understandable, although the noise was still "babble". + +For the -12 dB and -22 dB input levels, peak clipping also distorted the speech. Understandably, this effect was worse for the higher input level and for the higher Signal-to-Noise Ratios. + +It must be particularly remembered when considering these results that the listening was informal and used headphones, not a handset. Also, the use of electrically summed speech and noise will not give the same results as would have been obtained if the speech used had actually been recorded in the noisy environment. + +# 8 Assessment of equivalent qdu, Experiment 6 + +The experiment on the assessment of qdu was designed to assess the half rate codec performance, in error free conditions, in terms of Equivalent Quantization Distortion Units (qdu) as defined by the ITU-T. Two laboratories performed the experiment (CSELT and DEUTSCHE TELEKOM) and the following conclusions were drawn from their results: + +- a) For single encoding, the half rate codec was judged to be statistically equivalent to the full rate. Similar planning rules could therefore be applied to both algorithms if the configuration is not mobile-to-mobile. The figure of equivalent qdu for the half rate codec was found to lie somewhere between 8 and 16 qdu. A more precise figure could not be determined due to differences in the results from the two laboratories. + +(It is reminded that for the full rate an "average" figure of 7-8 qdu was indicated by SCEG to GSM, after considering test results showing values between a minimum of 4-5 qdu and a maximum of 21-22 qdu). + +- b) For tandemed conditions, a statistically significant difference in performance between the half and full rate codecs was detected in one of the two laboratories. The results confirmed that a noticeable degradation in speech quality in mobile-to-mobile connections is likely. + +Generally, both the Half- and Full-Rate showed a worse performance than the other standards (ITU-T Recommendations G.711 [1], G.726 [2], at 32 kbit/s, and G.728 [3]) included in the experiment. + +# 9 Talker dependency, Experiment 8 + +From the results obtained in the two laboratories which conducted this experiment, the performance of any given condition undoubtedly varies from talker to talker. + +The existence of this talker dependency has been confirmed by a further analysis applied to the results from the first phase of characterization testing. + +Under error free conditions, it was shown in the tests carried out, that the talker dependency for the half rate codec is similar to that for the full rate. + +# 10 DTX System + +## 10.1 Assessment of DTX algorithm, Experiment 9 + +The four laboratories who performed the subjective evaluation of DTX functions concentrated their expert listening on the following effects, using conversational speech; + +- Voice Activity Detection (VAD); and +- Comfort Noise Insertion (CNI). + +For this, the speech material available was monitored for the following effects: + +- speech clipping; +- noise quality; +- noise contrast. + +The tests showed that malfunctions of the VAD and the CNI were only predominant with low SNRs. The VAD functions appeared to work well in most situations (i.e. rather little clipping). In many situations, the Comfort Noise Insertion did not operate properly, being poorly matched in terms of quality and/or level. The DTX performed better with hand-held terminals relative to its performance with hands-free. + +## 10.2 Channel activity in DTX mode + +### 10.2.1 Test procedure + +Speech material recorded during testing of the full rate DTX system was processed through the codec/DTX hardware. This material comprised real conversations in the English, French, German and Italian languages. The activity of the VAD algorithm was measured for all 480 conversations. The mean channel activity was then calculated by means of a software simulation of the TX DTX handler. + +### 10.2.2 Speech channel activity + +The percentage of speech frames scheduled for transmission by the radio sub-system (subsequently referred to as the speech channel activity) varied significantly between conversations. Speech channel activities ranged from 35 % to 85 % for individual sides of a conversation. For this reason, it was not possible to identify any significant trends in the results with regard to terminal type and environmental conditions. The mean speech channel activity, measured over all 480 conversations, was approximately 55 %. + +### 10.2.3 Level compensation + +During the expert listening, it was found that the speech material had been processed at a level 6,5 dB below the original recorded level. However, the activity of the basic VAD algorithm rises approximately 0,5 % per dB increase in input level. To compensate for this, a factor of 3 % must be added to the speech channel activity estimate. + +### 10.2.4 SID update rate + +The DTX handler simulation used a SID update period of 480 ms. The SID update rate has subsequently been reduced to 240 ms. This modification will raise the speech channel activity by approximately 2 %. + +### 10.2.5 Interleaving compensation + +The channel measurements were calculated on a signal frame basis. However, the use of interleaving (depth 4) implies that the TDMA activity will be approximately 2 % higher than the signal frame activity. + +### 10.2.6 Estimated mean TDMA channel activity + +The estimated mean TDMA channel activity is shown in table 6. + +**Table 6: Calculation of mean TDMA channel activity** + +| | | +|-----------------------------|------| +| speech channel activity | 55 % | +| level compensation | 3 % | +| 240 ms SID update period | 2 % | +| interleaving compensation | 2 % | +| total TDMA channel activity | 62 % | + +# 11 Performance with DTMF tones + +## 11.1 Introduction + +In the fixed telephone system, DTMF (Dual Tone Multi Frequency) signals are transmitted in the speech channel for signalling. This has led to the use of DTMF tones for applications such as the control of answering machines and mail/messaging boxes. In the GSM system, the handling of these signalling tones is dependant on the direction the signal is travelling. If it is in the uplink (from the mobile station to the network), the signalling channel is used, rather than the speech channel. In the downlink (from the network to the mobile station), these tones are carried in the speech channel. Even though it was not a requirement for the half rate speech channel to be able to carry these tones in the downlink, their transmission was tested. + +## 11.2 Test set-up + +16 DTMF signals are defined representing the 10 numeric keys, the characters "A", "B", "C", "D", "\*" and "#". Each digit consists of two sine signals of distinctive frequencies, one chosen out of 4 values from the low frequency group (or row frequency), and one out of the 4 values from the high frequency group (column frequency). Both frequencies are sent simultaneously ideally with same amplitude and at exact frequency values. For practical use, certain tolerances of the frequencies and of the signal amplitudes are specified. + +A DTMF receiver must be capable of detecting these tones. It should detect all the DTMF tones even under noisy conditions or when speech is present. Also, it should not interpret other signals from the voice band as valid tones. The tones can only be distinguished by their specific frequency and amplitude composition so it is important, if they are to be recognized by the half rate system, that they conform to the CEPT recommendation T/CS 46-02 (1985). Among others, the difference in the amplitudes of the 2 components (twist) shall not exceed 6 dB. The minimum signal length from sending unit is 75 ms while a 40 ms signal should be detected at the receiver side. Pauses from the generator shall last 65 ms while the receiver shall detect 20 ms. + +The DTMF tests were done at nominal frequencies with different pulse and pause duration and different amplitude levels on a PC based set-up. DTMF signal files were generated by means of a DTMF software package for the 16 signals with 10 samples for each tone. After processing with the HR-codeset software, the result files were input to a DSP based hardware with a standard DTMF recognition S/W meeting CEPT requirements. All experiments were done also with modified DTMF receiver software. The tables in subclause 11.5 list the number of recognized tones. + +All dB values mentioned are for each individual component of the DTMF signal, with reference to the overload point. + +## 11.3 Results + +The results of the test with a standard DTMF detector are shown in table 7. Even at ideal conditions with nominal DTMF signal frequencies, no additional signals in the speech band, and error free transmission, the recognition is poor after processing. Only with a relatively high level of -12 dB and a tone length of 80 ms is a 100 % recognition achieved. Under all other conditions at least one tone shows severe problems. There is no linearity in this experiment, e.g. "4" is recognized well at -18 dB level but very poor at -22 dB while "7" shows the opposite behaviour. Also, when the twist is reversed, the results differ in ways which depend on the code being transmitted. The recognition of very short tones (40 ms) is not acceptable, and the longer tones (120 ms) are problematical too. + +A reason for the poor behaviour might be a time dependent twist generated by the GSM Half Rate codec when one of the two components develops differently from the other due to the non-linear behaviour of the codec. For more than 40 ms the twist at certain DTMF tones was observed to be greater than 6 dB and thus out of the allowed range of the specification of standard DTMF receivers. In experiment (h) with -12/-18 dB signals and 120 ms tones, 10 inputs of "A" resulted in 12 recognitions. A slow oscillation of the signal amplitudes may have generated a twist of more than 6 dB for longer than 20 ms. This made the detector observe a valid pause and a new tone, increasing the number of detected tones above the number of input tones. This might have happened also for other tones under the condition (h) where e.g. 10 detected tones may result of 8 correct detections, a double detection from one input and one failure. The test equipment could not decide such effects - as also in practise just the result counts. At 80 ms twist signals, such slow oscillations do not have the same effect because under no condition a valid 2nd tone can be detected (40+20+40>80). + +Table 8 shows the results of the same experiments as described above with a DTMF detector tuned for recognition in GSM half rate speech codec transmission. Using knowledge of the possible reasons for detection errors in the tuned detector, the detection rate was improved. However, even at the still ideal signal conditions as described above, the results were not satisfactory where there was severe twist or short (40 ms) tones. Also, the modifications may well increase the acceptance of non-DTMF signals as valid DTMF tones. This, however, was not tested. + +## 11.4 Conclusions + +With the standard detector the recognition rate averaged over all experiments was 74 %. The tuning of the detector for the half rate channel characteristics could improve the detection rate to 92 %. As all experiments still had rather ideal conditions, in real application an even lower rate for detection has to be assumed, also due to the misinterpretation of other signals in the modified detector. + +In conclusion, a serious commercial application using DTMF in the speech channel should not be supported with the GSM half rate codec. + +## 11.5 Result tables of experiments with standard and modified DTMF detectors + +The tables below list the numbers of detected tones from 10 input signals at each tested condition. For twist conditions, the pair of level figures indicate the level of row frequencies and column frequencies respectively. + +**Table 7: Summary of DTMF tests with standard DTMF detector** + +| Condition\Tone | 1 | 2 | 3 | A | 4 | 5 | 6 | B | 7 | 8 | 9 | C | * | 0 | # | D | Total | +|-----------------------------------------|----|----|----|------------|----|----|----|----|----|----|----|----|----|----|----|----|-------| +| (a) -12 dB, 40 ms | 5 | 2 | 9 | 10 | 0 | 8 | 1 | 5 | 10 | 5 | 3 | 0 | 0 | 10 | 10 | 9 | 87 | +| (b) -12 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160 | +| (c) -18 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 8 | 10 | 1 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 149 | +| (d) -22 dB, 80 ms | 10 | 10 | 10 | 10 | 4 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 154 | +| (e) 3 dB twist, -12/-15 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 7 | 10 | 10 | 10 | 0 | 10 | 10 | 10 | 147 | +| (f) 6 dB twist, -12/-18 dB, 80 ms | 0 | 1 | 0 | 10 | 0 | 10 | 0 | 10 | 0 | 10 | 0 | 4 | 0 | 0 | 10 | 0 | 55 | +| (g) 6 dB tw. reverse, -18/-12 dB, 80 ms | 10 | 10 | 4 | 10 | 6 | 3 | 0 | 0 | 0 | 0 | 10 | 10 | 0 | 0 | 6 | 10 | 79 | +| (h) 6 dB twist, -12/-18 dB, 120 ms | 8 | 3 | 9 | 12
note | 7 | 10 | 5 | 10 | 0 | 10 | 7 | 9 | 3 | 10 | 10 | 9 | 122 | +| Total | 63 | 56 | 62 | 82 | 47 | 71 | 44 | 65 | 38 | 65 | 60 | 63 | 33 | 60 | 76 | 68 | 953 | + +NOTE: 10 input signals in this test case resulted in 12 recognized tones. An explanation is given in subclause 11.3. + +**Table 8: Summary of DTMF tests with modified DTMF detector** + +| Condition\Tone | 1 | 2 | 3 | A | 4 | 5 | 6 | B | 7 | 8 | 9 | C | * | 0 | # | D | Total | +|-----------------------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|-------| +| (a) -12 dB, 40 ms | 9 | 10 | 8 | 1 | 0 | 8 | 4 | 10 | 10 | 10 | 8 | 9 | 8 | 10 | 6 | 8 | 119 | +| (b) -12 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160 | +| (c) -18 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160 | +| (d) -22 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160 | +| (e) 3 dB twist, -12/-15 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160 | +| (f) 6 dB twist, -12/-18 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 6 | 10 | 0 | 10 | 6 | 10 | 0 | 10 | 10 | 0 | 122 | +| (g) 6 dB tw. reverse, -18/-12 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 7 | 10 | 10 | 10 | 7 | 0 | 10 | 10 | 144 | +| (h) 6 dB twist, -12/-18 dB, 120 ms | 10 | 8 | 10 | 10 | 10 | 10 | 8 | 10 | 8 | 10 | 10 | 10 | 8 | 10 | 10 | 10 | 152 | +| Total | 79 | 78 | 78 | 71 | 70 | 78 | 68 | 80 | 65 | 80 | 74 | 79 | 63 | 70 | 76 | 68 | 1177 | + +# 12 Performance with signalling tones + +The capability of the codec to transmit network information tones was assessed with 5 French signalling tones following the IUT-T recommendation: "Warn" tone, "Busy" tone, "Ring" tone, "Inf" tone and "Pay" tone (tones of length 200 ms to 1 s and silences between tones of length 30 ms to 4 s). + +All signalling tones are recognized. However, the half rate codec introduces a very audible distortion and performs significantly worse than the full rate codec. + +None of the tones is perturbed by the VAD/DTI system. + +# --- 13 Delay + +[tbd] + +# --- 14 Frequency response + +The frequency response of the GSM half rate codec, has been evaluated by computing the logarithmic gain. + +The codec has been tested in error free condition only, without DTX associated, by independently processing 198 sine waves files spaced by 20 Hz and spanning the range between 50 to 3 990 Hz. Each file had a duration of 8 seconds and the input signal level was fixed at -22 dB ( $V_{max} = 2\,603$ ). + +The gain of the codec has been calculated by means of the formula: + +$$gain = 10 * \log_{10} \left( \frac{\sum_i (out_i)^2}{\sum_i (inp_i)^2} \right)$$ + +Figures 1 and 2 report the logarithmic gain for the whole range of tones considered and for telephone bandwidth respectively. + +Both figures show that the codec provide a flat frequency response in the telephone bandwidth, with the algorithmic gain confined in the range $\pm 0,2$ dB with a very few outliers. + +The highest attenuation observed is 0,65 dB and occurs at 1 150 Hz. + +It shall be noted that small deviations from these figures can be observed by using different levels and/or different initial phases for the sinewave signals. + +![Figure 1: Frequency response for the whole bandwidth considered. A line graph showing gain [dB] on the y-axis (from -25 to 5) versus frequency [Hz] on the x-axis (from 0 to 4000). The gain is mostly flat around 0 dB, with a sharp drop at 0 Hz and a small dip around 1200 Hz.](cbc4516eb885829fe8c9dabc0946dcbe_img.jpg) + +This graph shows the frequency response across a wide bandwidth. The y-axis represents gain in dB, ranging from -25 to 5. The x-axis represents frequency in Hz, ranging from 0 to 4000. The response is relatively flat around 0 dB, with a significant drop at 0 Hz and a minor dip around 1200 Hz. + +Figure 1: Frequency response for the whole bandwidth considered. A line graph showing gain [dB] on the y-axis (from -25 to 5) versus frequency [Hz] on the x-axis (from 0 to 4000). The gain is mostly flat around 0 dB, with a sharp drop at 0 Hz and a small dip around 1200 Hz. + +Figure 1: Frequency response for the whole bandwidth considered + +![Figure 2: Frequency response in the telephone bandwidth. A line graph showing gain [dB] on the y-axis (from -0.7 to 0.3) versus frequency [Hz] on the x-axis (from 0 to 3500). The gain fluctuates around 0 dB, with a sharp dip at approximately 1150 Hz reaching -0.65 dB.](fc857414626a8d94d132e12d9afe52a4_img.jpg) + +This graph shows the frequency response within the telephone bandwidth. The y-axis represents gain in dB, ranging from -0.7 to 0.3. The x-axis represents frequency in Hz, ranging from 0 to 3500. The response fluctuates around 0 dB, with a sharp dip at approximately 1150 Hz reaching -0.65 dB. + +Figure 2: Frequency response in the telephone bandwidth. A line graph showing gain [dB] on the y-axis (from -0.7 to 0.3) versus frequency [Hz] on the x-axis (from 0 to 3500). The gain fluctuates around 0 dB, with a sharp dip at approximately 1150 Hz reaching -0.65 dB. + +Figure 2: Frequency response in the telephone bandwidth + +# 15 Half Rate codec complexity + +The complexity of the half rate codec is characterized by the 3 following items: + +- the number of cycles; +- the data memory size; +- the program memory size. + +The values of these different figures depend on a specific DSP implementation. Nevertheless, the results obtained by the C description analysis can be used as references. + +The speech transcoding functions are specified using a set of basic arithmetic operations. The wMOPs figure quoted is a weighted sum of the operations required to perform transcoding. The weight assigned to each operation is representative of the number of instruction cycles required to perform that operation on a typical DSP device. + +The complexity range of the half rate codec is approximately 4,5 times that of the full rate codec. + +The number of cycles required by the half rate algorithm is highly dependent on the values of input samples. The execution time of an average and an extreme input case may differ by up to 20 %. + +That is why, to evaluate the complexity, it is necessary to compute the theoretical worst case, i.e. the maximum possible number of cycles, and not just observe the results of a simulation. + +The principal figures of this evaluation are the following: + +**Table 9: Principal figures of evaluation** + +| | Theoretical worst case wMOPs | Data RAM (note)
(16 bits words) | Data ROM (constants)
(16 bits words) | Program ROM (assembly instructions) | +|--------------------------------------------------------------|------------------------------|------------------------------------|-----------------------------------------|-------------------------------------| +| Speech and channel half rate codec (excluding DTX functions) | 21,2 | 5 002 | 8 781 | 8 000-12 000 | +| Ratio half rate vers. full rate | 4,5 | 2,4 | 9,7 | 4 | + +NOTE: The Data RAM figure can be split in 2 parts: the static variables: 2 100 words; and the dynamic variables (i.e. local to a procedure): 2 900 words. + +# 16 Summary of results from characterization Phase 1 and 2 + +The whole set of individual and global data were extensively analysed and discussed within the TCH-HS expert group. The effects of different factors and their interactions were subject to analysis of variance (ANOVA). Tables 10 to 14 report the results obtained in 9 experiments. + +## 16.1 Summary of Results From Characterization Phase 1 + +The whole set of individual and global data were extensively analysed and discussed within the TCH-HS expert group. The effects of different factors and their interactions were subject to analysis of variance (ANOVA). Tables 10 to 14 report the results obtained in 9 experiments. + +**Table 10: Summary of Characterization Phase 1 Results - Differential Q values** + +| Diff Q (dB) | | | | +|--------------------------------------|---------------------------------------------------|----------------------------|-------------------| +| exc.
(UPCM, No-IRS)
Exp. 1 - 3 | EP3
(A law-IRS and UPCM, No-IRS)
Exp. 1 - 3 | Noise only
Exp. 4 and 5 | All
Exp. 1 - 5 | +| -1,09 | -1,45 | -3,01 | -2,29 | + +NOTE: The figures indicate DQ values in dB averaged over input level, + +$$\text{where } DQ = Q_{HR} - Q_{FR}.$$ + +**Table 11: Summary of Characterization Phase 1 Results (Exp. 1, 2 and 3)** + +| Audio part | Single Encoding Conditions | | | | Tandeming Conditions | | All | All | +|-----------------------|----------------------------|-------|---------|-----------|----------------------|-------|----------|--------------| +| | EP0 | EP0/1 | EP0/1/2 | EP0/1/2/3 | EP0 | EP0/1 | exc. EP3 | | +| 1.A-Law IRS | +0,01 | -0,32 | -0,43 | +0,12 | -0,32 | -0,34 | -0,41 | +0,02 | +| 2.NoIRS,
LinearPCM | -2,16 | -2,13 | -1,82 | -0,90 | -4,98 | -4,50 | -2,49 | -1,62 | +| 1 and 2. | -1,08 | -1,22 | -1,12 | -0,39 | -2,65 | -2,42 | -1,45 | -0,80 | + +NOTE: Dependence on Specific Conditions without Background Noise. The figures indicate DQ values in dB averaged over input level, + +$$\text{where } DQ = Q_{HR} - Q_{FR}.$$ + +**Table 12: Summary of Characterization Phase 1 Results (Exp. 4 and 5)-** + +| Audio part | Office Babble | Vehicle | Traffic | No Tandeming | With Tandeming | All | +|------------|---------------|---------|---------|--------------|----------------|-------| +| A-Law IRS | -2,64 | -3,19 | -3,20 | -2,10 | -3,93 | -3,01 | + +NOTE: Differential Q values in Noise Conditions. The figures indicate DQ values in dB averaged over input level, + +$$\text{where } DQ = Q_{HR} - Q_{FR}.$$ + +**Table 13: Summary of Characterization Phase 1 Results - Significant differences (Experiment 1 to Experiment 5)** + +| Laboratory | Experiment 1 | Experiment 2 | Experiment 3 | Experiment 4 | Experiment 5 | +|------------------|--------------|--------------|--------------|--------------|--------------| +| BT | HR = FR | HR < FR | HR < FR | HR < FR | x | +| CNET | x | x | x | x | HR < FR | +| CSELT | HR = FR | HR = FR | HR = FR | x | HR < FR | +| Deutsche Telekom | HR = FR | HR = FR | HR < FR | HR < FR | x | +| Global | HR = FR | HR < FR | HR < FR | HR < FR | HR < FR | + +NOTE: See legend in subclause 16.2 for symbol explanation. + +## 16.2 Summary of Results From Characterization Phase 2 + +**Table 14: Summary of Characterization Phase 2 Results (Experiment 6 to Experiment 9)** + +| Subject: | qdu | Tandem with other Standards | Talker Dependency | DTX Functions | +|-------------------|--------------------------|-----------------------------|-------------------|----------------------------------------------------------------| +| Laboratory | Experiment 6 | Experiment 7 | Experiment 8 | Experiment 9 | +| BT | | HR+any < any+HR | see clause 9 | DTX operation appears to be satisfactory. | +| CNET | | HR+any < any+HR | | DTX fairly satisfactory, concerns over CNI. | +| CSELT | HR = FR
HR+HR < FR+FR | | | DTX satisfactory, concerns over CNI and comfort noise quality. | +| DBP | HR = FR
HR+HR = FR+FR | | see clause 9 | DTX fairly satisfactory, concerns over comfort noise quality. | + +### Legend + +| Symbol | Definition | +|--------|--------------------------------------------------------------| +| = | no significant difference at the 95 % confidence level | +| HR | Half rate codec | +| FR | Full rate codec | +| x | Experiment not performed by laboratory | +| HR16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46011/raw.md b/marked/Rel-18/46_series/46011/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f1ff013c34b5b13c033af7540b835e6114bb5f61 --- /dev/null +++ b/marked/Rel-18/46_series/46011/raw.md @@ -0,0 +1,225 @@ + + +# 3GPP TS 46.011 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Full rate speech; Substitution and muting of lost frames for full rate speech channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +### **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|---------------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 4 General ..... | 5 | +| 5 Requirements ..... | 5 | +| 5.1 First lost speech frame..... | 5 | +| 5.2 Subsequent lost speech frames..... | 6 | +| 5.3 First lost SID frame ..... | 6 | +| 5.4 Subsequent lost SID frame ..... | 6 | +| 6 Example solution..... | 6 | +| Annex A (informative): Change history..... | 8 | + +## --- 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 defines a frame substitution and muting procedure which shall be used by the RX DTX handler when one or more lost speech or SID frames are received from the radio subsystem. + +The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS) and Mobile Stations (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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding". +- [3] GSM 06.31: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channel". + +## --- 3 Definitions and abbreviations + +Abbreviations used in the present document are listed in GSM 01.04 [1]. + +The definitions of terms used in the present document can be found in GSM 06.31 [3]. + +## --- 4 General + +The purpose of the frame substitution is to conceal the effect of lost frames. + +The purpose of muting the output in the case of several lost frames is to indicate the breakdown of the channel to the user. + +## --- 5 Requirements + +### 5.1 First lost speech frame + +Normal decoding of lost speech frames would result in very unpleasant noise effects. In order to improve the subjective quality, the first lost speech frame shall be substituted with either a repetition or an extrapolation of the previous good speech frame(s). Lost speech frames shall not be delivered to the speech decoder, nor shall the output be muted directly. + +### 5.2 Subsequent lost speech frames + +For subsequent lost speech frames, a muting technique shall be used that will gradually decrease the output level, resulting in silencing of the output after a maximum of 320 ms. Clause 6 gives an example solution. + +### 5.3 First lost SID frame + +A single lost SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied as described in GSM 06.31 [3]. + +### 5.4 Subsequent lost SID frame + +For the second lost SID frame, a muting technique shall be used on the comfort noise that will gradually decrease the output level, resulting in silencing of the output after a maximum of 320 ms. Clause 6 gives an example solution. + +For subsequent lost SID frames, the muting of the output shall be maintained. + +## --- 6 Example solution + +For guidance, an example solution is given. + +The first lost speech frame is replaced at the speech decoder input by the previous good speech frame. Normal decoding is then performed. + +The muting procedure to be used in the case of subsequent lost speech frames or for comfort noise frames following the second lost SID frame is as follows: + +The pseudo-logarithmic encoded block amplitude $X_{maxcr}$ (GSM 06.10 [2]), coded on the interval from 0 to 63, is decreased with a constant value $d=4$ in each frame, down to the lowest possible value. Consequently, $X_{maxcr}$ will be reduced gradually, and the output muted after a maximum of 320 ms. The grid position parameters are chosen randomly between 0 and 3 during this time. + +For subsequent unusable frames, after the frame where $X_{maxcr}$ reached the lowest possible value, "silence frames" are passed from the RX DTX handler to the speech decoder to guarantee a low output level under all conditions. The silence frame is defined in table 1. + +**Table 1: Encoded parameters (GSM 06.10) of the silence frame** + +Log area ratio 1 = 42 +Log area ratio 2 = 39 +Log area ratio 3 = 21 +Log area ratio 4 = 10 +Log area ratio 5 = 9 +Log area ratio 6 = 4 +Log area ratio 7 = 3 +Log area ratio 8 = 2 + +LTP gain = 0 +LTP lag = 40 + +Grid position = 1 +Block amplitude = 0 + +RPE pulse no. 1 = 3 +RPE pulse no. 2 = 4 +RPE pulse no. 3 = 3 +RPE pulse no. 4 = 4 +RPE pulse no. 5 = 4 + +- repeated for each subsegment + +RPE pulse no. 6 = 3 +RPE pulse no. 7 = 3 +RPE pulse no. 8 = 3 +RPE pulse no. 9 = 3 +RPE pulse no. 10 = 4 +RPE pulse no. 11 = 4 +RPE pulse no. 12 = 3 +RPE pulse no. 13 = 3 + +– + +## Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|-------------------------------------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#07 | | | | 4.0.4 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#28 | | | | 6.0.1 | ETSI Publication | +| SMG#29 | | | | 7.0.0 | Specification version 6.0.0 upgrade to Release 1998 version 7.0.0 | +| | | | | 7.0.1 | Version update for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46012/raw.md b/marked/Rel-18/46_series/46012/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..58900e854064c0eb828fb8cb8928c6b0ee203bd7 --- /dev/null +++ b/marked/Rel-18/46_series/46012/raw.md @@ -0,0 +1,229 @@ + + +# 3GPP TS 46.012 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Full rate speech; Comfort noise aspect for full rate speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|----------------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 4 General ..... | 5 | +| 5 Functions on the transmit side ..... | 6 | +| 5.1 Background acoustic noise evaluation ..... | 6 | +| 5.2 SID-frame encoding ..... | 6 | +| 6 Functions on the receive side ..... | 7 | +| 6.1 Comfort noise generation and updating ..... | 7 | +| Annex A (informative): Change history ..... | 8 | + +# --- 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 gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX) on full rate speech traffic channels. + +The requirements described in the present document are mandatory for implementation in all GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used. + +# --- 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [3] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding". +- [4] GSM 06.31: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channel". + +# --- 3 Definitions and abbreviations + +Definitions and abbreviations used in the present document are listed in GSM 01.04 [1]. + +The definitions of terms used in this technical specification can be found in GSM 06.31 [4]. + +# --- 4 General + +The overall operation of Discontinuous Transmission is described in GSM 06.31 [4]. + +A basic problem when using DTX is that the background acoustic noise, which is transmitted together with the speech, would disappear when the radio transmission is cut, resulting in a modulation of the background noise. Since the DTX switching can take place rapidly, it has been found that this effect can be very annoying for the listener - especially in a car environment with high background noise levels. In bad cases the speech may be hardly intelligible. + +The present document specifies the way to overcome this problem by generating on the receive side synthetic noise similar to the transmit side background noise. The parameters of this so called comfort noise are estimated on the transmit side and transmitted to the receive side before the radio transmission is cut and at a regular low rate afterwards. This allows the comfort noise to adapt to the changes of the noise on the transmit side. + +# 5 Functions on the transmit side + +The comfort noise evaluation algorithm uses the unquantized block amplitude and Log Area Ratio (LAR) parameters of the full rate speech encoder, defined in subclauses 4.2.15 and 4.2.6 of GSM 06.10 [3]. These parameters give information on the level and the spectrum of the background noise, respectively. + +The evaluated comfort noise parameters are encoded into a special frame, called a SID (Silence Descriptor) frame, for transmission to the receive side. + +The SID frame also serves to initiate the comfort noise generation on the receive side, as a SID frame is always sent at the end of a speech burst, i.e. before the radio transmission is cut. + +The scheduling of SID or speech frames on the radio path is described in GSM 06.31 [4]. + +## 5.1 Background acoustic noise evaluation + +The comfort noise parameters to be encoded into a SID frame are calculated over $N=4$ consecutive frames marked with VAD=0, as follows: + +The Log Area Ratio parameters shall be averaged according to the equation: + +$$mean(LAR(i)) = \frac{1}{N} \sum_{n=1}^N LAR[j-n](i) \quad i = 1, 2..8$$ + +where $LAR[j](i)$ is the $i$ 'th Log Area Ratio coefficient of the current frame $j$ and $j-n$ indicates the previous frames. + +The block amplitude parameter shall be averaged according to the equation: + +$$mean(x_{max}) = \frac{1}{(4N)} \sum_{n=1}^N \sum_{i=1}^4 x_{max}[j-n](i)$$ + +where $x_{max}[j](i)$ is the block amplitude in sub-segment $i$ of the current frame. The SID frame containing these averaged parameters is passed to the Radio Subsystem instead of frame number $j$ . + +## 5.2 SID-frame encoding + +The SID-frame encoding algorithm exploits the fact that only some of the 260 bits in a frame are needed to code the comfort noise parameters. The other bits can then be used to mark the SID-frame by means of a fixed bit pattern, called the SID code word. + +The log area ratio coefficients are replaced by the mean ( $LAR(i)$ ) values defined above and encoded as described in GSM 06.10 [3]. + +The block amplitude values are replaced by the mean ( $x_{max}$ ) value defined above, repeated four times inside the frame and encoded as described in GSM 06.10 [3]. + +The SID code word consists of 95 bits which are all zero. The bits of the SID code word are inserted in the SID field defined as the positions of those 95 bits of the encoded RPE-pulses $X_{mc}$ , which are in the error protection class I (see GSM 05.03 [2], table 2). + +The remaining bits in the SID frame are set to zero. The use of these bits is for further study. + +# 6 Functions on the receive side + +The situations in which comfort noise shall be generated on the receive side are defined in GSM 06.31 [4]. Generally speaking, the comfort noise generation is started or updated whenever a valid SID frame is received. + +## 6.1 Comfort noise generation and updating + +The comfort noise generation procedure uses the RPE-LTP speech decoder algorithm defined in GSM 06.10 [3]. + +When comfort noise is to be generated, then the various encoded parameters are set as follows. + +The RPE pulses ( $X_{mer}$ ) are replaced by a locally generated random integer sequence, uniformly distributed between 1 and 6. + +Also the grid position parameters ( $M_{cr}$ ) are set to random integer values, uniformly distributed between 0 and 3. + +The LTP gain values ( $b_{cr}$ ) are set to 0. + +The LTP lag values ( $N_{cr}$ ) of the 4 sub-segments are set to 40, 120, 40 and 120 respectively. + +The 4 block amplitude values ( $X_{maxer}$ ) used are those received in the SID frame. + +The log area ratio parameters ( $LAR_{cr}$ ) used are those received in the SID frame. + +With these parameters, the speech decoder now performs the standard operations described in GSM 06.10 [3] and synthesizes comfort noise. + +Updating of the comfort noise parameters occurs each time a valid SID frame is received, as described in GSM 06.31 [4]. + +When updating the comfort noise, the parameters above should preferably be interpolated over a few frames to obtain smooth transitions. + +## Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#07 | | | | 4.0.4 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-----------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2001 | 12 | SP-010304 | 001 | | Corrections of the formula for averaging Xmax | 4.0.0 | 4.1.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.1.0 | 5.0.0 | +| 12-2006 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46020/raw.md b/marked/Rel-18/46_series/46020/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..af48bb9035e617fca590baded35dd4d5eefd4e72 --- /dev/null +++ b/marked/Rel-18/46_series/46020/raw.md @@ -0,0 +1,1730 @@ + + +# 3GPP TS 46.020 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Half rate speech; Half rate speech transcoding (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|---------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 9 | +| 4 Functional description of the GSM half rate speech codec ..... | 10 | +| 4.1 GSM half rate speech encoder ..... | 10 | +| 4.1.1 High-pass filter ..... | 12 | +| 4.1.2 Segmentation ..... | 13 | +| 4.1.3 Fixed Point Lattice Technique (FLAT)..... | 13 | +| 4.1.4 Spectral quantization ..... | 14 | +| 4.1.4.1 Autocorrelation Fixed Point Lattice Technique (AFLAT) ..... | 14 | +| 4.1.5 Frame energy calculation and quantization..... | 16 | +| 4.1.6 Soft interpolation of the spectral parameters..... | 16 | +| 4.1.7 Spectral noise weighting filter coefficients ..... | 17 | +| 4.1.8 Long Term Predictor lag determination ..... | 18 | +| 4.1.8.1 Open loop long term search initialization..... | 19 | +| 4.1.8.2 Open loop lag search..... | 20 | +| 4.1.8.3 Frame lag trajectory search (Mode $\neq$ 0)..... | 25 | +| 4.1.8.4 Voicing mode selection ..... | 27 | +| 4.1.8.5 Closed loop lag search ..... | 27 | +| 4.1.9 Harmonic noise weighting..... | 28 | +| 4.1.10 Code search algorithm..... | 30 | +| 4.1.10.1 Decorrelation of filtered basis vectors ..... | 31 | +| 4.1.10.2 Fast search technique ..... | 32 | +| 4.1.11 Multimode gain vector quantization..... | 33 | +| 4.1.11.1 Coding GS and P0..... | 33 | +| 4.2 GSM half rate speech decoder ..... | 36 | +| 4.2.1 Excitation generation..... | 37 | +| 4.2.2 Adaptive pitch prefilter..... | 37 | +| 4.2.3 Synthesis Filter ..... | 37 | +| 4.2.4 Adaptive spectral postfilter..... | 37 | +| 4.2.5 Updating decoder states..... | 39 | +| 5 Homing sequences ..... | 39 | +| 5.1 Functional description ..... | 39 | +| 5.2 Definitions..... | 39 | +| 5.3 Encoder homing ..... | 40 | +| 5.4 Decoder homing ..... | 40 | +| 5.5 Encoder home state ..... | 40 | +| 5.6 Decoder home state ..... | 40 | + +# **Annex A (normative):            Codec parameter description ..... 41** + +| | | +|--------------------------------------|----| +| A.1 Codec parameter description..... | 41 | +| A.1.1 MODE..... | 41 | +| A.1.2 R0..... | 41 | +| A.1.3 LPC1 - LPC3..... | 42 | +| A.1.4 LAG_1 - LAG_4..... | 42 | +| A.1.5 CODEX_1 - CODEX_4..... | 42 | +| A.1.6 GSP0_1 - GSP0_4..... | 42 | + +A.2 Basic coder parameters ..... 42 + +**Annex B (normative):**      **Order of occurrence of the codec parameters over Abis** ..... 43 + +**Annex C (informative):**    **Bibliography** ..... 44 + +**Annex D (informative):**    **Change history** ..... 45 + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the speech codec to be used for the GSM half rate channel for the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below: + +- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". +- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".** +- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". + +GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". + +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 speech codec to be used for the GSM half rate channel. It also specifies the test methods to be used to verify that the codec implementation complies with the present document. + +The requirements are mandatory for the codec to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the half rate GSM speech traffic channel. + +# --- 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] GSM 06.02: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- [2] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- [3] GSM 06.07: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following definitions apply: + +**adaptive codebook:** adaptive codebook is derived from the long term filter state. The lag value can be viewed as an index into the adaptive codebook. + +**adaptive pitch prefilter:** in the GSM half rate speech decoder, this filter is applied to the excitation signal to enhance the periodicity of the reconstructed speech. Note that this is done prior to the application of the short term filter. + +**adaptive spectral postfilter:** in the GSM half rate speech decoder, this filter is applied to the output of the short term filter to enhance the perceptual quality of the reconstructed speech. + +**allowable lags:** set of lag values which may be coded by the GSM half rate speech encoder and transmitted to the GSM half rate speech decoder. This set contains both integer and fractional values (see table 3). + +**analysis window:** for each frame, the short term filter coefficients are computed using the high pass filtered speech samples within the analysis window. The analysis window is 170 samples in length, and is centered about the last 100 samples in the frame. + +**basis vectors:** set of M, M1, or M2 vectors of length Ns used to generate the VSELP codebook vectors. These vectors are not necessarily orthogonal. + +**closed loop lag search:** process of determining the near optimal lag value from the weighted input speech and the long term filter state. + +**closed loop lag trajectory:** for a given frame, the sequence of near optimal lag values whose elements correspond to each of the four subframes as determined by the closed loop lag search. + +**codebook:** set of vectors used in a vector quantizer. + +**Codeword (OR Code):** M, M1, or M2 bit symbol indicating the vector to be selected from a VSELP codebook. + +**Delta (LAG) code:** four bit code indicating the change in lag value for a subframe relative to the previous subframe's coded lag. For frames in which the long term predictor is enabled (MODE 1, 2, or 3), the lag for subframe 1 is independently coded using eight bits, and delta codes are used for subframes 2, 3, and 4. + +**direct form coefficients:** one of the formats for storing the short term filter parameters. All filters which are used to modify speech samples use direct form coefficients. + +**fractional lags:** set of lag values having sub-sample resolution. Note that not every fractional lag value considered in the GSM half rate speech encoder is an allowable lag value. + +**frame:** time interval equal to 20 ms, or 160 samples at an 8 kHz sampling rate. + +**harmonic noise weighting filter:** this filter exploits the noise masking properties of the spectral peaks which occur at harmonics of the pitch frequency by weighting the residual error less in regions near the pitch harmonics and more in regions away from them. Note that this filter is only used when the long term filter is enabled (MODE = 1, 2 or 3). + +**high pass filter:** this filter is used to de-emphasize the low frequency components of the input speech signal. + +**integer lags:** set of lag values having whole sample resolution. + +**interpolating filter:** FIR filter used to estimate sub-sample resolution samples, given an input sampled with integer sample resolution. + +**lag:** long term filter delay. This is typically the pitch period, or a multiple or sub-multiple of it. + +**long term filter:** this filter is used to generate the periodic component in the excitation for the current subframe. This filter is only enabled for MODE = 1, 2 or 3. + +**LPC coefficients:** Linear Predictive Coding (LPC) coefficients is a generic descriptive term for describing the short term filter coefficients. + +**open loop lag search:** process of estimating the near optimal lag directly from the weighted speech input. This is done to narrow the range of lag values over which the closed loop lag search shall be performed. + +**open loop lag trajectory:** for a given frame, the sequence of near optimal lag values whose elements correspond to the four subframes as determined by the open loop lag search. + +**reflection coefficients:** alternative representation of the information contained in the short term filter parameters. + +**residual:** output signal resulting from an inverse filtering operation. + +**short term filter:** this filter introduces, into the excitation signal, short term correlation which models the impulse response of the vocal tract. + +**soft interpolation:** process wherein a decision is made for each frame to use either interpolated or uninterpolated short term filter parameters for the four subframes in that frame. + +**soft interpolation bit:** one bit code indicating whether or not interpolation of the short term parameters is to be used in the current frame. + +**spectral noise weighting filter:** this filter exploits the noise masking properties of the formants (vocal tract resonances) by weighting the residual error less in regions near the formant frequencies and more in regions away from them. + +**subframe:** time interval equal to 5 ms, or 40 samples at an 8 kHz sampling rate. + +**vector quantization:** method of grouping several parameters into a vector and quantizing them simultaneously. + +**GSP0 vector quantizer:** process of vector quantization, its intermediate parameters (GS and P0) for the coding of the excitation gains $\beta$ and $\gamma$ . + +**VSELP codebook:** Vector-Sum Excited Linear Predictive (VSELP) codebook, used in the GSM half rate speech coder, wherein each codebook vector is constructed as a linear combination of the fixed basis vectors. + +**zero input response:** output of a filter due to all past inputs, i.e. due to the present state of the filter, given that an input of zeros is applied. + +**zero state response:** output of a filter due to the present input, given that no past inputs have been applied, i.e. given the state information in the filter is all zeroes. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $A(z)$ | Short term spectral filter. | +| $\alpha_i$ | The LPC coefficients. | +| $b_L(n)$ | The output of the long term filter state (adaptive codebook) for lag L. | +| $\beta$ | The long term filter coefficient. | +| $C(z)$ | Second weighting filter. | +| $e(n)$ | Weighted error signal | +| $f_j(i)$ | The coefficients of the $j^{\text{th}}$ phase of the 10th order interpolating filter used to evaluate candidate fractional lag values; $i$ ranges from 0 to $P_f-1$ . | +| $g_j(i)$ | The coefficients of the $j^{\text{th}}$ phase of the 6th order interpolating filter used to interpolate C's and G's as well as fractional lags in the harmonic noise weighting; $i$ ranges from 0 to $P_g-1$ . | +| $\gamma$ | The gain applied to the vector(s) selected from the VSELP codebook(s). | +| H | A M2 bit code indicating the vector to be selected from the second VSELP codebook (when operating in mode 0). | +| I | A M or M1 bit code indicating the vector to be selected from one of the two first VSELP codebooks. | +| L | The long term filter lag value. | +| $L_{\max}$ | 142 (samples), the maximum possible value for the long term filter lag. | +| $L_{\min}$ | 21 (samples), the minimum possible value for the long term filter lag. | +| M | 9, the number of basis vectors, and the number of bits in a codeword, for the VSELP codebook used in modes 1, 2, and 3. | +| M1 | 7, the number of basis vectors, and the number of bits in a codeword, for the first VSELP codebook used in mode 0. | +| M2 | 7, the number of basis vectors, and the number of bits in a codeword, for the second VSELP codebook used in mode 0. | +| MODE | A two bit code indicating the mode for the current frame (see annex A). | +| $N_A$ | 170, the length of the analysis window. This is the number of high pass filtered speech samples used to compute the short term filter parameters for each frame. | +| $N_F$ | 160, the number of samples per frame (at a sampling rate of 8 kHz). | +| $N_p$ | 10, the short term filter order. | +| $N_s$ | 40, the number of samples per subframe (at a sampling rate of 8 kHz). | +| P1 | 6, the number of bits in the prequantizer for the $r1 - r3$ vector quantizer. | +| P2 | 5, the number of bits in the prequantizer for the $r4 - r6$ vector quantizer. | +| P3 | 4, the number of bits in the prequantizer for the $r7 - r10$ vector quantizer. | +| $P_f$ | The order of one phase of an interpolating filter used to evaluate candidate fractional lag values. $P_f$ equals 10 for $j \neq 0$ and equal to 1 for $j = 0$ . | +| $P_g$ | The order of one phase of an interpolating filter, $f_j(n)$ , used to interpolate C's and G's as well as fractional lags in the harmonic noise weighting, $P_g$ equals 6. | +| pitch | The time duration between the glottal pulses which result when the vocal chords vibrate during speech production. | +| Q1 | 11, the number of bits in the $r1 - r3$ reflection coefficient vector quantizer. | +| Q2 | 9, the number of bits in the $r4 - r6$ reflection coefficient vector quantizer. | +| Q3 | 8, the number of bits in the $r7 - r10$ reflection coefficient vector quantizer. | +| $R0$ | A five bit code used to indicate the energy level in the current frame. | +| $r(n)$ | The long term filter state (the history of the excitation signal); $n < 0$ | +| $r_L(n)$ | The long term filter state with the adaptive codebook output for lag L appended. | + +| | | +|----------------------|----------------------------------------------------------------------------------------------------| +| $s'(n)$ | Synthesized speech. | +| $W(z)$ | Spectral weighting filter. | +| $\lambda_{hnr}$ | The harmonic noise weighting filter coefficient. | +| $\xi$ | The adaptive pitch prefilter coefficient. | +| $\lceil x \rceil$ | Ceiling function: the largest integer $y$ where $y < x + 1, 0$ . | +| $\lfloor x \rfloor$ | Floor function: the largest integer $y$ where $y \leq x$ . | +| $\sum_{i=j}^K x(i)$ | Summation: $x(j)+x(j+1)+\dots+x(K)$ . | +| $\prod_{i=j}^K x(i)$ | Product: $x(j)(x(j+1))\dots(x(K))$ | +| $\max(x,y)$ | Find the larger of two numbers $x$ and $y$ . | +| $\min(x,y)$ | Find the smaller of two numbers $x$ and $y$ . | +| $\text{round}(x)$ | Round the non-integer $x$ to the closest integer $y$ : $y = \lfloor x + 0,5 \rfloor$ ; $y=x+0,5$ . | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------------------| +| AFLAT | Autocorrelation Fixed point LAttice Technique | +| CELP | Code Excited Linear Prediction | +| FLAT | Fixed Point Lattice Technique | +| LTP | Long Term Predictor | +| SST | Spectral Smoothing Technique | +| VSELP | Vector-Sum Excited Linear Prediction | + +# 4 Functional description of the GSM half rate speech codec + +The GSM half rate codec uses the VSELP (Vector-Sum Excited Linear Prediction) algorithm. The VSELP algorithm is an analysis-by-synthesis coding technique and belongs to the class of speech coding algorithms known as CELP (Code Excited Linear Prediction). + +The GSM half rate codec's encoding process is performed on a 20 ms speech frame at a time. A speech frame of the sampled speech waveform is read and based on the current waveform and the past history of the waveform, the codec encoder derives 18 parameters that describe it. The parameters extracted are grouped into the following three general classes: + +- energy parameters (R0 and GSP0); +- spectral parameters (LPC and INT\_LPC); +- excitation parameters (LAG and CODE). + +These parameters are quantized into 112 bits for transmission as described in annex A and their order of occurrence over Abis is given in annex B. + +The GSM half rate codec is an analysis-by-synthesis codec, therefore the speech decoder is primarily a subset of the speech encoder. The quantized parameters are decoded and a synthetic excitation is generated using the energy and excitation parameters. The synthetic excitation is then filtered to provide the spectral information resulting in the generation of the synthesized speech (see figure 1). + +![Block diagram of the GSM half rate speech codec showing the flow between speech, transmitted/received parameters, and synthesized speech through a speech encoder and decoder.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +GSM half rate speech codec + +``` + + graph LR + S[speech] --> SE[Speech encoder] + SE --> TP[transmitted speech parameters] + RP[received speech parameters] --> SD[Speech decoder] + SD --> SS[synthesised speech] + subgraph GSM_Codec [GSM half rate speech codec] + SE + SD + end + +``` + +Block diagram of the GSM half rate speech codec showing the flow between speech, transmitted/received parameters, and synthesized speech through a speech encoder and decoder. + +**Figure 1: Block diagram of the GSM half rate speech codec** + +The ANSI-C code that describes the GSM half rate speech codec is given in GSM 06.06 [2] and the test sequences in GSM 06.07 [3] (see clause 5 for the codec homing test sequences). + +## 4.1 GSM half rate speech encoder + +The GSM half rate speech encoder uses an analysis by synthesis approach to determine the code to use to represent the excitation for each subframe. The codebook search procedure consists of trying each codevector as a possible excitation for the Code Excited Linear Predictive (CELP) synthesizer. The synthesized speech $s'(n)$ is compared against the input speech and a difference signal is generated. This difference signal is then filtered by a spectral weighting filter, $W(z)$ , (and possibly a second weighting filter, $C(z)$ ) to generate a weighted error signal, $e(n)$ . The power in $e(n)$ is computed. The codevector which generates the minimum weighted error power is chosen as the codevector for that subframe. The spectral weighting filter serves to weight the error spectrum based on perceptual considerations. This weighting filter is a function of the speech spectrum and can be expressed in terms of the $\alpha$ parameters of the short term (spectral) filter. + +$$W(z) = \frac{1 - \sum_{i=1}^{N_p} \alpha_i z^{-i}}{1 - \sum_{i=1}^{N_p} \tilde{\alpha}_i z^{-i}} \quad (1)$$ + +The computation of the $\tilde{\alpha}_i$ coefficients is described in subclause 4.1.7. + +The second weighting filter $C(z)$ , if used, is a harmonic weighting filter and is used to control the amount of error in the harmonics of the speech signal. If the weighting filter(s) are moved to both input paths to the subtracter, an equivalent configuration is obtained as shown in figure 2. + +![Block diagram of the GSM half rate speech encoder (MODE = 1, 2 and 3).](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +The diagram illustrates the signal processing flow of the GSM half rate speech encoder. The input speech $s(n)$ is split into two paths. One path goes through a weighting filter $W(z)$ and then a harmonic weighting filter $C(z)$ to produce $y(n)$ . The other path from $s(n)$ goes to a block labeled 'Determine LPC coefficients', which outputs parameters: LPC 1, LPC 2, LPC 3, R0, and INT\_LPC. These parameters are fed into the $W(z)$ filter and also into a synthesis filter $H(z)$ . The $y(n)$ signal is subtracted from the output of $H(z)$ to produce an error signal $e(n)$ . The error signal is squared ( $\sum ( )^2$ ) to produce the 'total weighted error'. This error is minimized over lag $L$ and codebook index $I$ using a 'Find Minimum over L and all I' block. This block outputs MODE, LAG-1, CODE\_1, LAG\_2, CODE\_2, LAG\_3, CODE\_3, LAG\_4, and CODE\_4. Below this, a 'find optimal gains $\beta$ and $\gamma$ ' block is performed, which outputs GSP 0-1, GSP 0\_2, GSP 0\_3, and GSP 0\_4. The optimal gains $\beta$ and $\gamma$ are fed back to the synthesis filter $H(z)$ and the gain $\gamma$ is also used in the summation node. The synthesis filter $H(z)$ takes inputs from a VSELP Codebook (index $I$ ), a gain $\gamma$ , a lag $L$ , and a gain $\beta$ . The output of $H(z)$ is then passed through a $C(z)$ filter before being subtracted from $y(n)$ . + +Block diagram of the GSM half rate speech encoder (MODE = 1, 2 and 3). + +Figure 2: Block diagram of the GSM half rate speech encoder (MODE = 1, 2 and 3) + +Here $H(z)$ is the combination of $A(z)$ , the short term (spectral) filter, and $W(z)$ , the spectral weighting filter. These filters are combined since the denominator of $A(z)$ is cancelled by the numerator of $W(z)$ . + +$$H(z) = \frac{1}{1 - \sum_{i=1}^{N_p} \tilde{\alpha}_i z^{-i}} \quad (2)$$ + +There are two approaches that can be used for calculating the gain, $\gamma$ . The gain can be determined prior to codebook search based on residual energy. This gain would then be fixed for the codebook search. Another approach is to optimize the gain for each codevector during the codebook search. The codevector which yields the minimum weighted error would be chosen and its corresponding optimal gain would be used for $\gamma$ . The latter approach generally yields better results since the gain is optimized for each codevector. This approach also implies that the gain term needs to be updated at the subframe rate. The optimal code and gain for this technique can be computed as follows. + +The input speech is first filtered by a high pass filter as described in subclause 4.1.1. The short term filter parameters are computed from the filtered input speech once per frame. A fast fixed point covariance lattice technique is used. Subclauses 4.1.3 and 4.1.4 describes in detail how the short term parameters are determined and quantized. An overall frame energy is also computed and coded once per frame. Once per frame, one of the four voicing modes is selected. If MODE $\neq$ 0, the long term predictor is used and the long term predictor lag, $L$ , is updated at the subframe rate. $L$ and a VSELP codeword are selected sequentially. Each is chosen to minimize the weighted mean square error. The long-term filter coefficient, $\beta$ , and the codebook gain, $\gamma$ , are optimized jointly. Subclause 4.1.8 describes the technique for selecting from among the voicing modes and, if one of voiced modes is chosen, determining the long-term filter lag. Subclause 4.1.10 describes an efficient technique for jointly optimizing $\beta$ , $\gamma$ and the codeword selection. Subclause 4.1.10 also includes the description of the fast VSELP codebook search technique. The $\beta$ and $\gamma$ parameters are transformed to equivalent parameters using the frame energy term, and are vector quantized every subframe. The coding of the frame energy and the $\beta$ and $\gamma$ parameters is described in subclause 4.1.11. + +### 4.1.1 High-pass filter + +The 13 bit linear Pulse Code Modulated (PCM) input speech, $x(n)$ , is filtered by a fourth order pole-zero high pass filter. This filter suppresses the frequency components of the input speech which are below 120 Hz. The filter is implemented as a cascade of two second-order Infinite Impulse Response (IIR) filters. Incorporated into the filter coefficients is a gain of 0,5. The difference equation for the first filter is: + +$$\tilde{y}(n) = \sum_{i=0}^2 b_{1,i} x(n-i) + \sum_{j=1}^2 a_{1,j} \tilde{y}(n-j) \quad (3)$$ + +where: + +$$b_{10} = 0,335052$$ + +$$b_{11} = -0,669983 \quad a_{11} = 0,926117$$ + +$$b_{12} = 0,335052 \quad a_{12} = -0,429413$$ + +The difference equation for the second filter is: + +$$y(n) = \sum_{i=0}^2 b_{2,i} \tilde{y}(n-i) + \sum_{j=1}^2 a_{2,j} y(n-j) \quad (4)$$ + +where: + +$$b_{20} = 0,335052$$ + +$$b_{21} = -0,669434 \quad a_{21} = 0,965332$$ + +$$b_{22} = 0,335052 \quad a_{22} = -0,469513$$ + +### 4.1.2 Segmentation + +A sample buffer containing the previous 195 input high pass filtered speech samples, $y(n)$ , is shifted so that the oldest 160 samples are shifted out while the next 160 input samples are shifted in. The oldest 160 samples in the buffer correspond to the next frame of samples to be encoded. The analysis interval comprises the most recent 170 samples in the buffer. The samples in the buffer are labelled as $s(n)$ where $0 \leq n \leq 194$ and $s(0)$ is the first (oldest) sample. + +### 4.1.3 Fixed Point Lattice Technique (FLAT) + +Let $r_j$ represent the $j^{\text{th}}$ reflection coefficient. The FLAT algorithm for the determination of the reflection coefficients is stated as follows: + +STEP 1 Compute the covariance (autocorrelation) matrix from the input speech: + +$$\phi(i, k) = \sum_{n=N_p}^{N_A} s(n + 24 - i)s(n + 24 - k) \quad 0 \leq i, k \leq N_p \quad (5)$$ + +STEP 2 The $\phi(i, k)$ array is modified by windowing + +$$\phi'(i, k) = \phi(i, k)w(|i - k|) \quad 0 \leq i, k \leq N_p \quad (6)$$ + +STEP 3 $F_0(i, k) = \phi'(i, k) \quad 0 \leq i, k \leq N_p - 1 \quad (7)$ + +$$B_0(i, k) = \phi'(i + 1, k + 1) \quad 0 \leq i, k \leq N_p - 1 \quad (8)$$ + +$$C_0(i, k) = \phi'(i, k + 1) \quad 0 \leq i, k \leq N_p - 1 \quad (9)$$ + +STEP 4 set $j = 1$ + +STEP 5 Compute $r_j$ + +$$r_j = -2 \frac{C_{j-1}(0, 0) + C_{j-1}(N_p - j, N_p - j)}{F_{j-1}(0, 0) + B_{j-1}(0, 0) + F_{j-1}(N_p - j, N_p - j) + B_{j-1}(N_p - j, N_p - j)} \quad (10)$$ + +STEP 6 If $j = N_p$ then done. + +STEP 7 Update $F_j(i, k)$ , $B_j(i, k)$ , $C_j(i, k) \quad 0 \leq i, k \leq N_p - j - 1$ + +$$F_j(i, k) = F_{j-1}(i, k) + r_j(C_{j-1}(i, k) + C_{j-1}(k, i)) + r_j^2 B_{j-1}(i, k) \quad (11)$$ + +$$B_j(i, k) = B_{j-1}(i + 1, k + 1) + r_j(C_{j-1}(i + 1, k + 1) + C_{j-1}(k + 1, i + 1)) + r_j^2 F_{j-1}(i + 1, k + 1), \quad (12)$$ + +$$C_j(i, k) = C_{j-1}(i, k + 1) + r_j(B_{j-1}(i, k + 1) + F_{j-1}(i, k + 1)) + r_j^2 C_{j-1}(k + 1, i) \quad (13)$$ + +STEP 8 $j = j + 1$ + +STEP 9 go to step 5. + +The windowing coefficients, $w(|i - k|)$ , are found in the table 1. + +**Table 1: Windowing coefficients** + +| | | | | +|------|----------|------|----------| +| w(0) | 0,998966 | w(5) | 0,974915 | +| w(1) | 0,996037 | w(6) | 0,969054 | +| w(2) | 0,991663 | w(7) | 0,963060 | +| w(3) | 0,986399 | w(8) | 0,956796 | +| w(4) | 0,980722 | w(9) | 0,950127 | + +This algorithm can be simplified by noting that the $\phi'$ , F and B matrices are symmetric such that only the upper triangular part of the matrices need to be computed or updated. Also, step 7 is done so that $F_j(i,k)$ , $B_j(i-1,k-1)$ , $C_j(i,k-1)$ , and $C_j(k,i-1)$ are updated together and common terms are computed once and the recursion is done in place. + +### 4.1.4 Spectral quantization + +A three segment vector quantizer of the reflection coefficients is employed. A reduced complexity search technique is used to select the vector of reflection coefficients for each segment. The reflection coefficient vector quantizer codebooks are stored in compressed form to minimize their memory requirements. + +The three segments of the vector quantizer span reflection coefficients $r_1$ - $r_3$ , $r_4$ - $r_6$ , and $r_7$ - $r_{10}$ respectively. The bit allocations for the vector quantizer segments are: + +| | | +|-------|---------| +| $Q_1$ | 11 bits | +| $Q_2$ | 9 bits | +| $Q_3$ | 8 bits | + +A reflection coefficient vector prequantizer is used at each segment. The prequantizer size at each segment is: + +| | | +|-------|--------| +| $P_1$ | 6 bits | +| $P_2$ | 5 bits | +| $P_3$ | 4 bits | + +At a given segment, the residual error due to each vector from the prequantizer is computed and stored in temporary memory. This list is searched to identify the four prequantizer vectors which have the lowest distortion. The index of each selected prequantizer vector is used to calculate an offset into the vector quantizer table at which the contiguous subset of quantizer vectors associated with that prequantizer vector begins. The size of each vector quantizer subset at the k-th segment is given by: + +$$S_k = \frac{2^{Q_k}}{2^{P_k}} \quad (14)$$ + +The four subsets of quantizer vectors, associated with the selected prequantizer vectors, are searched for the quantizer vector which yields the lowest residual error. Thus at the first segment, 64 prequantizer vectors and 128 quantizer vectors are evaluated, 32 prequantizer vectors and 64 quantizer vectors are evaluated at the second segment, and 16 prequantizer vectors and 64 quantizer vectors are evaluated at the third segment. + +#### 4.1.4.1 Autocorrelation Fixed Point Lattice Technique (AFLAT) + +An autocorrelation version of the FLAT algorithm, AFLAT, is used to compute the residual error energy for a reflection coefficient vector being evaluated. Compute the autocorrelation sequence $R(i)$ , from the optimal reflection coefficients, $r_j$ , over the range $0 \leq i \leq N_p$ . + +STEP 1 Define the initial conditions for the AFLAT recursion: + +$$\bar{P}_0(i) = R(i), \quad 0 \leq i \leq N_p - 1 \quad (15)$$ + +$$\bar{V}_0(i) = R(i+1), \quad 1 - N_p \leq i \leq N_p - 1 \quad (16)$$ + +STEP 2 Initialize k, the vector quantizer segment index: + +$$k = 1 \quad (17)$$ + +STEP 3 Let $I_l(k)$ be the index of the first lattice stage in the k-th segment, and $I_h(k)$ be the index of the last lattice stage in the k-th segment. + +STEP 4 Initialize j, the index of the lattice stage, to point to the beginning of the k-th segment: + +$$j = I_l(k) \quad (18)$$ + +STEP 5 Set the initial conditions $P_{j-1}$ and $V_{j-1}$ to: + +$$P_{j-1}(i) = \bar{P}_{j-1}(i), \quad 0 \leq i \leq I_h(k) - I_l(k) \quad (19)$$ + +$$V_{j-1}(i) = \bar{V}_{j-1}(i), \quad -I_h(k) + I_l(k) \leq i \leq I_h(k) - I_l(k) \quad (20)$$ + +STEP 6 Compute the values of $V_j$ and $P_j$ arrays using: + +$$P_j(i) = \left(1 + \hat{r}_j^2\right) P_{j-1}(i) + \hat{r}_j \left[ V_{j-1}(i) + V_{j-1}(-i) \right], \quad 0 \leq i \leq I_h(k) - j - 1 \quad (21)$$ + +$$V_j(i) = V_{j-1}(i+1) + \hat{r}_j^2 V_{j-1}(-i-1) + 2\hat{r}_j P_{j-1}(|i+1|), \quad 1 + j - N_p \leq i \leq N_p - j - 1 \quad (22)$$ + +STEP 7 Increment j: + +$$j = j+1$$ + +STEP 8 If $j < I_h(k)$ go to STEP 6. + +STEP 9 The residual error out of lattice stage $I_h(k)$ , given the reflection coefficient vector $\hat{\mathbf{r}}$ , is computed using equation (21): + +$$E_r = P_{I_h(k)}(0) \quad (23)$$ + +STEP 10 Using the AFLAT recursion outlined, the residual error due to each vector from the prequantizer at the k-th segment is evaluated, the four subsets of quantizer vectors to be searched are identified, and residual error due to each quantizer vector from the selected four subsets is computed. The index of $\tilde{\mathbf{r}}$ , the quantizer vector which minimized $E_r$ over all the quantizer vectors in the four subsets, is encoded with $Q_k$ bits. + +STEP 11 If $k < 3$ then the initial conditions for doing the recursion at segment k+1 need to be computed. Set j, the lattice stage index, equal to: + +$$j = I_l(k) \quad (24)$$ + +STEP 12 Compute: + +$$\bar{P}_j(i) = \left(1 + \tilde{r}_j^2\right) \bar{P}_{j-1}(i) + \tilde{r}_j \left[ \bar{V}_{j-1}(i) + \bar{V}_{j-1}(-i) \right], \quad 0 \leq i \leq N_p - j - 1 \quad (25)$$ + +$$\bar{V}_j(i) = \bar{V}_{j-1}(i+1) + \tilde{r}_j^2 \bar{V}_{j-1}(-i-1) + 2\tilde{r}_j \bar{P}_{j-1}(|i+1|), \quad 1 + j - N_p \leq i \leq N_p - j - 1 \quad (26)$$ + +STEP 13 Increment j, + +$$j = j+1$$ + +STEP 14 If $j \leq I_h(k)$ go to STEP 12 + +STEP 15 Increment $k$ , the vector quantizer segment index: + $k=k+1$ + +STEP 16 If $k \leq 3$ go to STEP 4. + +Otherwise, the indices of the reflection coefficient vectors for the three segments have been chosen, and the search of the reflection coefficient vector quantizer is terminated. + +To minimize the storage requirements for the reflection coefficient vector quantizer, eight bit codes for the individual reflection coefficients are stored in the vector quantizer table, instead of the actual reflection coefficient values. The codes are used to look up the values of the reflection coefficients from a scalar quantization table with 256 entries. + +### 4.1.5 Frame energy calculation and quantization + +The unquantized value of $R_0$ , $R(0)$ , is computed during the computation of the short term predictor parameters. + +$$R(0) = \frac{\phi(0,0) + \phi(10,10)}{320} \quad (27)$$ + +where $\phi(i,k)$ is defined by equation (5). $R(0)$ is then converted into dB relative to full scale (full scale, $R_{\max}$ , is defined as the square of the maximum sample amplitude). + +$$R_{dB} = 10 \log_{10} \left( \frac{R(0)}{R_{\max}} \right) \quad (28)$$ + +$R_{dB}$ is then quantized to 32 levels. The 32 quantized values for $R_{dB}$ range from a minimum of -66 (corresponding to a code of 0 for $R_0$ ) to a maximum of -4 (corresponding to a code of 31 for $R_0$ ). The step size of the quantizer is 2 (2 dB steps). $R_0$ is chosen as: + +$$R_0 \text{ which minimizes } \text{abs}(R_0 - (R_{dB} + 66)/2) \quad (29)$$ + +where $R_0$ can take on the integer values from 0 to 31 corresponding to the 32 codes for $R_0$ . + +Decoding of the $R_0$ code is given by: + +$$R(0) = R_{\max} 10^{((2R_0)-66)/10} \quad (30)$$ + +### 4.1.6 Soft interpolation of the spectral parameters + +Interpolation of the short term filter parameters improves the performance of the GSM half rate encoder. The direct form filter coefficients ( $\alpha_i$ 's), which correspond to quantized reflection coefficients, are the spectral parameters used for interpolation. The GSM half rate speech encoder uses either an interpolated set of $\alpha_i$ 's or an uninterpolated set of $\alpha_i$ 's, choosing the set which gives better prediction gain for the frame. + +Two sets of LPC coefficient vectors are generated: the first corresponds to the interpolated coefficients, the second to the uninterpolated coefficients. The frame's speech samples are inverse filtered using each of the two coefficient sets, and the residual frame energy corresponding to each set is computed. The coefficient set yielding the lower frame residual energy is then selected to be used. If the residual energies are equal, the uninterpolated coefficient set is used. INT\_LPC, a soft interpolation bit, is set to 1 when interpolation is selected or to 0 otherwise. + +To generate the interpolated coefficient set, the coder interpolates the $\alpha_i$ 's for the first, second, and third subframes of each frame. The fourth subframe uses the uninterpolated $\alpha_i$ 's for that frame. + +The interpolation is done as follows. Let $\alpha_{i,L}$ be the direct-form LPC coefficients corresponding to the last frame, $\alpha_{i,C}$ be the direct-form LPC coefficients corresponding to the current frame, and Del to be the interpolation curve used. The interpolated direct-form LPC coefficient vector at the j-th subframe of the current frame, $\alpha_{i,j}$ , is given by: + +$$\alpha_{i,j} = \alpha_{i,L} + \text{Del}(j, \text{INT\_SOFT})(\alpha_{i,C} - \alpha_{i,L}), \quad 1 \leq i \leq N_p, 1 \leq j \leq 4 \quad (31)$$ + +The values of the interpolation curve Del are given in table 2. + +**Table 2: Values of the interpolation curve Del** + +| j | Del(j,0) | Del(j,1) | +|---|----------|----------| +| 1 | 0,0 | 0,30 | +| 2 | 1,0 | 0,62 | +| 3 | 1,0 | 0,92 | +| 4 | 1,0 | 1,00 | + +From this point on, the subframe index j is omitted for simplicity when referring to $\alpha_{i,j}$ coefficients, although it is implied. For interpolated subframes, the $\alpha_i$ 's are converted to reflection coefficients to check for filter stability. If the resulting filter is unstable, then uninterpolated coefficients are used for that subframe. The uninterpolated coefficients used for subframe 1 are the previous frame's coefficients. The uninterpolated coefficients used for subframes 2, 3, and 4 are the current frame's coefficients. + +### 4.1.7 Spectral noise weighting filter coefficients + +To exploit the noise masking potential of the formants, spectral noise weighting is applied. The computation of the $\tilde{\alpha}_i$ coefficients, used by spectral noise weighting filters W(z) and H(z), is now described. Define an impulse sequence $\delta(n)$ over $N_s$ samples: + +$$\begin{aligned} \delta(0) &= 1,0 \\ \delta(n) &= 0,0 \end{aligned} \quad (32)$$ + +where $1 \leq n \leq N_s-1$ and $h_3(n)$ is the zero-state response of the cascade of three filters to $\delta(n)$ . The three filters are an LPC synthesis filter, an inverse filter using a weighting factor of 0,93 and a synthesis filter with a weighting factor of 0,7. In equation form: + +$$h_1(n) = \delta(n) + \sum_{i=1}^{N_p} \alpha_i h_1(n-i) \quad 0 \leq n \leq N_s-1 \quad (33)$$ + +$$h_2(n) = h_1(n) - \sum_{i=1}^{N_p} (0,93)^i \alpha_i h_1(n-i) \quad 0 \leq n \leq N_s-1 \quad (34)$$ + +$$h_3(n) = h_2(n) + \sum_{i=1}^{N_p} (0,7)^i \alpha_i h_3(n-i), \quad 0 \leq n \leq N_s-1 \quad (35)$$ + +where $\alpha_i$ 's are the direct form LP coefficients. The autocorrelation sequence of $h_3(n)$ is calculated using: + +$$R_{h_3}(i) = \sum_{n=i}^{N_s-1} h_3(n)h_3(n-i), \quad 0 \leq i \leq N_p \quad (36)$$ + +From $R_{h_3}(i)$ the reflection coefficients which define the combined spectrally noise weighted synthesis filter are computed using the AFLAT recursion once per frame. + +STEP 1 Define the initial conditions for the AFLAT recursion: + +$$P_0(i) = R_{h_3}(i), \quad 0 \leq i \leq N_p-1 \quad (37)$$ + +$$V_0(i) = R_{h_3}(i+1), \quad 1-N_p \leq i \leq N_p-1 \quad (38)$$ + +STEP 2 Initialize j, the index of the lattice stage, to point to the first lattice stage: + +$$j = 1$$ + +STEP 3 Compute $r_j$ , the j-th reflection coefficient, using: + +$$r_j = -\frac{V_{j-1}(0)}{P_{j-1}(0)} \quad (39)$$ + +STEP 4 Given $r_j$ , update the values of $V_j$ and $P_j$ arrays using: + +$$P_j(i) = (1+r_j^2)P_{j-1}(i) + r_j[V_{j-1}(i) + V_{j-1}(-i)], \quad 0 \leq i \leq N_p - j - 1 \quad (40)$$ + +$$V_j(i) = V_{j-1}(i+1) + r_j^2 V_{j-1}(-i-1) + 2r_j P_{j-1}(i+1), \quad 1+j-N_p \leq i \leq N_p - j - 1 \quad (41)$$ + +STEP 5 Increment j: + +$$j = j+1$$ + +STEP 6 If $j \leq N_p$ go to STEP 3, otherwise all $N_p$ reflection coefficients have been obtained. + +STEP 7 The reflection coefficients, $r_j$ , are then converted to direct-form LPC filter coefficients, $\tilde{\alpha}_i$ , for implementing the combined spectrally noise weighted synthesis filter $H(z)$ and the filter $W(z)$ . + +The method for the spectral noise weighting filter coefficient update mimicks how the direct form LPC filter coefficients are updated at subframes of a frame (subclause 4.1.6). No stability check of interpolated spectral noise weighting filter coefficients is done at subframes 1, 2, or 3 if the interpolation flag, INT\_LPC="1", but if uninterpolated coefficients are used at subframes 1, 2, and/or 3 due to instability of the unweighted coefficients (INT\_LPC = "0"), uninterpolated weighting filter coefficients are also used at those subframes. + +### 4.1.8 Long Term Predictor lag determination + +Figure 3 illustrates that the long term lag optimization looks just like a codebook search where the codebook is defined by the long term filter state and the specific vector in the codebook is pointed to by the long term predictor lag, L. The input $p(n)$ is the weighted input speech for the subframe minus the zero input response of just the $H(z)$ filter. + +![Block diagram of the long term predictor lag search. The diagram shows a 'Long term filter state' block receiving an input 'L' and outputting 'b_L(n)'. This signal is multiplied by 'beta' in a block labeled 'X'. The output of 'X' is then processed by a block labeled 'H(z)' to produce 'p'(n)'. This signal is subtracted from an input 'p(n)' in a block labeled '-'. The result is 'e(n)', which is then processed by a block labeled 'Σ( )^2' to produce the final output 'total weighted error'.](c923e830926610e73d6cbcdedb9e5ea4_img.jpg) + +Block diagram of the long term predictor lag search. The diagram shows a 'Long term filter state' block receiving an input 'L' and outputting 'b\_L(n)'. This signal is multiplied by 'beta' in a block labeled 'X'. The output of 'X' is then processed by a block labeled 'H(z)' to produce 'p'(n)'. This signal is subtracted from an input 'p(n)' in a block labeled '-'. The result is 'e(n)', which is then processed by a block labeled 'Σ( )^2' to produce the final output 'total weighted error'. + +Figure 3: Long term predictor lag search + +The GSM half rate speech encoder uses a combination of open loop and closed loop techniques in choosing the long term predictor lag. First an open loop search is conducted to determine "candidate" lags at each subframe. Then at most, two best candidate lags at each subframe are selected, with each serving as an anchor point for constructing an open loop frame lag trajectory, subject to a maximum delta coding constraint. The frame lag trajectory which minimizes the + +open loop LTP spectrally weighted error energy for the frame is then chosen. The open loop LTP prediction gains corresponding to the winning trajectory are used to select the voicing mode 1, 2 or 3. If MODE $\neq$ 0, the closed loop lag evaluation is initiated. The winning trajectory has associated with it a list of lags to be searched closed loop at each subframe. + +It is possible to allow L to take on fractional values, thus increasing the resolution, and in turn the performance, of the adaptive codebook. Table 3 shows the allowable lags. + +**Table 3: Allowable lags** + +| Range | Resolution | Number of lags in range | +|--------------|------------|-------------------------| +| 21 to 22 2/3 | 1/3 | 6 | +| 23 to 34 5/6 | 1/6 | 72 | +| 35 to 49 2/3 | 1/3 | 45 | +| 50 to 89 1/2 | 1/2 | 80 | +| 90 to 142 | 1 | 53 | + +The resolution of the long term filter state may be increased by upsampling and filtering the state. In this implementation, a non-causal, zero-phase Finite Impulse Response (FIR) filter is used. Where needed, the future samples for the non-causal filtering operation are replaced by the output of the predictor. + +#### 4.1.8.1 Open loop long term search initialization + +An open-loop lag search is done to narrow the range of lags over which a closed-loop search will eventually be performed. + +The first steps of the open-loop subframe lag search are as follows: + +STEP 1 Initialize the subframe counter + +$m=1$ + +STEP 2 The autocorrelation sequence of $y(n)$ the input speech, $s(n)$ , filtered by $W$ , is calculated for all allowable integer lags, and for a few integer lags below and above the lower and upper limits for the current subframe. + +$$C(k,m) = \sum_{n=0}^{N_s-1} y(n+(m-1)N_s) y(n+(m-1)N_s-k), \quad L_{\min} - \frac{P_g}{2} \leq k \leq L_{\max} + \frac{P_g}{2} - 1 \quad (42)$$ + +where $L_{\min} = 21$ and $L_{\max} = 142$ . + +The value $P_g$ is the order of one phase of the interpolating FIR filter used to interpolate the correlations. The energy of $y(n)$ for the subframe is computed: + +$$G(k,m) = \sum_{n=0}^{N_s-1} y^2(n+(m-1)N_s-k), \quad L_{\min} - \frac{P_g}{2} \leq k \leq L_{\max} + \frac{P_g}{2} - 1 \quad (43)$$ + +STEP 3 These arrays, $C(k,m)$ and $G(k,m)$ , are searched for the integer lag which maximizes $C^2(k,m)/G(k,m)$ where $C(k,m)$ and $G(k,m)$ need to be greater than 0. + +STEP 4 If a valid maximum is found in step 3, the values for the lag, $C$ , and $G$ corresponding to the maximum are retained in the arrays as $L_{\text{peak}}(0,m)$ , $C_{\text{peak}}(0,m)$ , and $G_{\text{peak}}(0,m)$ . + +Otherwise, $L_{\text{peak}}(0,m) = L_{\min}$ (44) + +$$C_{\text{peak}}(0,m) = 0 \quad (45)$$ + +$$G_{\text{peak}}(0,m) = 1 \quad (46)$$ + +STEP 5 $m=m+1$ + +STEP 6 If $m \leq 4$ , go to step 2 + +STEP 7 Calculate the open loop frame LTP prediction gain: + +$$P_v = 10 \log_{10} \left[ \frac{\sum_{m=1}^4 R(0,m)}{\sum_{m=1}^4 \left[ R(0,m) - \frac{C_{peak}^2(0,m)}{G_{peak}(0,m)} \right]} \right] \quad (47)$$ + +where + +$$R(0,m) = \sum_{n=0}^{N_s-1} y^2(n + (m-1)N_s), \quad (48)$$ + +STEP 8 Determine if the voicing mode is unvoiced: + +If $P_v < 1,7$ then $MODE=0$ , the long term predictor is disabled and the open loop and closed loop lag searches are aborted. In this case, proceed to subclause 4.1.10. + +#### 4.1.8.2 Open loop lag search + +When $MODE \neq 0$ , the lag search processing is continued. The next part of the search finds the allowable lag (see table 3) which maximizes $\frac{C^2}{G}$ in the vicinity of the best open-loop integer resolution lag, $L_{peak}(0,m)$ , for values of $C > 0$ . + +STEP 1 Initialize the subframe counter + +$m=1$ + +STEP 2 Initialize the peak index + +$L_{p,m} = 0$ + +STEP 3 Using interpolated versions of the C and G arrays, allowable lag values $k'$ in the range: + +$$L_{peak}(0,m) - 1 < k' < L_{peak}(0,m) + 1 \quad (49)$$ + +are searched for a $k$ which maximizes + +$$\frac{C_I^2(k)}{G_I(k)} \quad (50)$$ + +where + +$$C_I(k) = \sum_{i=0}^5 g_j(i) C(\lceil k \rceil - 3 + i, m) \quad (51)$$ + +$$G_I(k) = \sum_{i=0}^5 g_j(i) G(\lceil k \rceil - 3 + i, m) \quad (52)$$ + +and + +$$j = 6(\lceil k \rceil - k) \quad (53)$$ + +The coefficients of the interpolating filter are $g_j(i)$ for $0 \leq i \leq 5$ . + +Only $C_I(k) > 0$ and $G_I(k) > 0$ values are considered. If no positive correlation is found, then set + +$\lambda_{\text{hnw},m} = 0$ , $L_{\text{peak}}(1,m) = L_{\text{min}}$ , and go to Step 22. + +Otherwise, store the information related to the valid best allowable lag $k$ . + +$$L_{p,m} = L_{p,m} + 1 \quad (54)$$ + +$$L_{\text{peak}}(L_{p,m}, m) = k \quad (55)$$ + +$$C_{\text{peak}}(L_{p,m}, m) = C_I(k) \quad (56)$$ + +$$G_{\text{peak}}(L_{p,m}, m) = G_I(k) \quad (57)$$ + +The next part of the search evaluates $\frac{C^2}{G}$ , for $C > 0$ and $G > 0$ , at the submultiples of the lag $L_{\text{peak}}(L_{p,m}, m)$ to find candidate peaks. + +STEP 4 Initialize the divisor + +$$J = 2$$ + +STEP 5 Find nearest integer lag corresponding to submultiple of maximum peak + +$$k_1 = \text{round}[L_{\text{peak}}(1,m)/J] \quad (58)$$ + +STEP 6 Determine if submultiple is within allowable lag range + +If $k_1 < L_{\text{min}}$ + +Go to step 12 + +STEP 7 Find value of $k'$ where $C^2(k',m)/G(k',m)$ is a maximum for + +$$\max(L_{\text{min}}, k_1 - 3) \leq k' \leq \min(L_{\text{max}}, k_1 + 3) \quad (59)$$ + +If either $C(k',m) \leq 0$ or $G(k',m) \leq 0$ go to step 11. + +STEP 8 Determine if maximum in step 7 is a peak + +If + +$$\frac{C^2(k'-1,m)}{G(k'-1,m)} > \frac{C^2(k',m)}{G(k',m)} \quad (60)$$ + +Go to step 11 + +If + +$$\frac{C^2(k'+1,m)}{G(k'+1,m)} > \frac{C^2(k',m)}{G(k',m)} \quad (61)$$ + +Go to step 11 + +STEP 9 A peak has been found at an integer lag, $k'$ . Using interpolated versions of the C and G arrays, allowable lag values within $\pm 1$ (exclusive) of $k'$ are searched. + +Find $k$ where + +$$\frac{C_I^2(k)}{G_I(k)} \quad (62)$$ + +is a maximum, where + +$$C_I(k) = \sum_{i=0}^5 g_j(i) C(\lceil k \rceil - 3 + i, m) \quad (63)$$ + +$$G_I(k) = \sum_{i=0}^5 g_j(i) G(\lceil k \rceil - 3 + i, m) \quad (64)$$ + +where + +$$j = 6(\lceil k \rceil - k) \quad (65)$$ + +$$\text{and } k'-1 < k < k'+1 \quad (66)$$ + +Only $C_I(k) > 0$ and $G_I(k) > 0$ are considered. + +STEP 10 If the prediction gain exceeds a threshold, the corresponding lag, $C_I$ , and $G_I$ are stored in the $L_{\text{peak}}()$ , $C_{\text{peak}}()$ , and $G_{\text{peak}}()$ arrays; otherwise, these values are not stored. + +If + +$$\frac{C_I^2(k)}{G_I(k)} > R(0,m) - \frac{R(0,m)}{10^x}, \text{ where } x = 7,5 \log_{10} \left( \frac{R(0,m)}{R(0,m) - \frac{C_{\text{peak}}^2(0,m)}{G_{\text{peak}}(0,m)}} \right) \quad (67)$$ + +then + +$$L_{p,m} = L_{p,m} + 1 \quad (68)$$ + +$$L_{peak}(L_{p,m}, m) = k \quad (69)$$ + +$$C_{peak}(L_{p,m}, m) = C_I(k) \quad (70)$$ + +$$G_{peak}(L_{p,m}, m) = G_I(k) \quad (71)$$ + +STEP 11 Increment divisor and check the next submultiple + +$$J = J + 1$$ + +Go to step 5 + +STEP 12 A full-resolution search (1/6 sample resolution) is done for a peak within 1 integer lag (exclusive) of the shortest lag. + +Find $k$ such that + +$$\frac{C_I^2(k)}{G_I(k)} \quad (72)$$ + +is a maximum, where + +$$C_I(k) = \sum_{i=0}^5 g_j(i) C(\lceil k \rceil - 3 + i, m) \quad (73)$$ + +$$G_I(k) = \sum_{i=0}^5 g_j(i) G(\lceil k \rceil - 3 + i, m) \quad (74)$$ + +$$j = 6(\lceil k \rceil - k) \quad (75)$$ + +$$\max\left(L_{min} - \frac{1}{6}, L_{peak}(L_{p,m}) - 1\right) < k < \min\left(L_{max} + \frac{1}{6}, L_{peak}(L_{p,m}) + 1\right) \quad (76)$$ + +The fractional lag corresponding to the maximum is referred to as $L_{pitch,m}$ . This lag is used by the harmonic noise weighting function $C(z)$ at subframe $m$ . Then + +$$C_{pitch,m} = C_I(L_{pitch,m}) \quad (77)$$ + +$$G_{pitch,m} = G_I(L_{pitch,m}) \quad (78)$$ + +STEP 13 The harmonic noise weighting coefficient for subframe $m$ is calculated in this step (see subclause 4.1.9) + +$$\lambda_{hnw,m} = 0,4 \frac{C_{pitch,m}}{G_{pitch,m}} \quad (79)$$ + +Once all the correlation peaks associated with submultiples of the $L_{peak}(1,m)$ have been examined, the correlation peaks associated with multiples of $L_{pitch,m}$ are examined. + +STEP 14 Initialize the multiplier + +$$J = 2$$ + +STEP 15 Find nearest integer lag corresponding to a multiple of the fundamental lag + +$$k_1 = \text{round} [L_{\text{pitch,m}} * J] \quad (80)$$ + +STEP 16 Determine if multiple is within allowable lag range + +If + +$$k_1 > L_{\text{max}}$$ + +Go to step 22 + +STEP 17 Find value of $k'$ where $C^2(k',m)/G(k',m)$ is a maximum for + +$$\max(L_{\text{min}}, k_1 - 3) \leq k' \leq \min(L_{\text{max}}, k_1 + 3) \quad (81)$$ + +If either $C(k',m) \leq 0$ or $G(k',m) \leq 0$ go to step 21. + +STEP 18 Determine if maximum in step 17 is a peak + +If + +$$\frac{C^2(k'-1,m)}{G(k'-1,m)} > \frac{C^2(k',m)}{G(k',m)} \quad (82)$$ + +Go to step 21 + +If + +$$\frac{C^2(k'+1,m)}{G(k'+1,m)} > \frac{C^2(k',m)}{G(k',m)} \quad (83)$$ + +Go to step 21 + +STEP 19 A peak has been found at an integer lag, $k'$ . Using interpolated versions of the C and G arrays, allowable lag values within $\pm 1$ (exclusive) of $k'$ are searched. + +Find $k$ where + +$$\frac{C_I^2(k)}{G_I(k)} \quad (84)$$ + +is a maximum, where + +$$C_I(k) = \sum_{i=0}^5 g_j(i) C(\lceil k \rceil - 3 + i, m) \quad (85)$$ + +$$G_I(k) = \sum_{i=0}^5 g_j(i) G(\lceil k \rceil - 3 + i, m) \quad (86)$$ + +where + +$$j = 6(\lceil k \rceil - k) \quad (87)$$ + +$$\text{and } k'-1 < k < k'+1 \quad (88)$$ + +Only $C_I(k) > 0$ and $G_I(k) > 0$ are considered. + +STEP 20 If the prediction gain exceeds a threshold, the corresponding lag, $C_I$ , and $G_I$ are stored. + +If + +$$\frac{C_I^2(k)}{G_I(k)} > R(0,m) - \frac{R(0,m)}{10^x}, \text{ where } x = 7,5 \log_{10} \left( \frac{R(0,m)}{R(0,m) - \frac{C_{peak}^2(0,m)}{G_{peak}(0,m)}} \right) \quad (89)$$ + +then + +$$L_{p,m} = L_{p,m} + 1 \quad (90)$$ + +$$L_{peak}(L_{p,m}) = k \quad (91)$$ + +$$C_{peak}(L_{p,m}) = C_I(k) \quad (92)$$ + +$$G_{peak}(L_{p,m}) = G_I(k) \quad (93)$$ + +STEP 21 Increment multiplier and check the next multiple + +$$J = J + 1$$ + +Go to step 15 + +STEP 22 Increment subframe pointer and repeat for all subframes + +$$m = m + 1$$ + +If $m \leq 4$ + +Go to step 2. + +Otherwise, the list of correlation peaks and the harmonic noise weighting filter parameters for each subframe have been found. + +#### 4.1.8.3 Frame lag trajectory search (Mode $\neq 0$ ) + +The frame lag trajectory search uses the list of potential lag values to determine the one lag value for each subframe which minimizes the open loop prediction error energy for the frame subject to the constraints of the delta lag coding employed for subframes 2, 3 and 4. Several candidate lag trajectories are determined. The trajectory which minimizes the open loop prediction error energy for the frame is chosen. + +In subclause 4.1.8.2, the open loop lag search found a list of lags, $L_{peak}(i,m)$ , corresponding to the $\frac{C^2}{G}$ peaks, for each subframe. Each trajectory evaluation begins with one of the subframes and selects a lag corresponding to a $\frac{C^2}{G}$ peak for that subframe as the anchor for that candidate trajectory. + +A maximum of 2 trajectories are anchored per subframe. From the anchor lag, the trajectory is extended forward and backward to the adjacent subframes in the frame subject to the lag differential coding constraints. The lag for each subframe on the trajectory is chosen to minimize the open loop frame prediction error energy. The trajectory search is described below. + +The steps involved in the frame lag trajectory evaluation and selection are: + +STEP 1 Set $m$ , the pointer to the selected subframe, equal to 1. + +STEP 2 Choose the lag at the selected subframe, $m$ , to be an anchor lag for the frame lag trajectory; i.e., the frame lag trajectory being evaluated needs to pass through that lag. The lag which is chosen, corresponds to the highest peak in the list of $\frac{C_I^2}{G_I}$ peaks at subframe $m$ , which has not been crossed by a trajectory evaluated previously. If no peaks qualify, no peaks are left, or two trajectories have already been anchored and evaluated at subframe $m$ , go to step 7. Otherwise, compute the open loop subframe weighted error energy corresponding to the chosen lag, and store the result in the frame weighted error accumulator corresponding to the trajectory currently being evaluated. + +STEP 3 If $m < 4$ , begin the forward search: + +STEP 3a Define the current subframe to be $m+1$ . + +STEP 3b Define the forward search range as -7 to +6 levels relative to the current subframe's lag level. + +STEP 3c Check that the lower bound does not point to a level below the lowest allowable lag level, clipping if necessary. Similarly, check that the upper bound does not point past the highest allowable lag level; clip if necessary. + +STEP 3d Find the lag within the range which maximizes $\frac{C_I}{\sqrt{G_I}}$ . + +NOTE: negative values of $C_I$ are allowed. Compute the open loop subframe weighted error energy corresponding to that lag at the current subframe, and add the result to the frame weighted error accumulator corresponding to the trajectory being evaluated. + +STEP 3e If the current subframe $< 4$ , increment the pointer to the current subframe, and go to step 3b. + +STEP 4 If $m > 1$ , initiate the backward search: + +STEP 4a Define the current subframe to be $m-1$ . + +STEP 4b Define the backward search range as -6 to +7 levels relative to the current subframe's lag level. + +STEP 4c Check that the lower bound does not point to a level below the lowest allowable lag level, clipping if necessary. Similarly, check that the upper bound does not point past the highest allowable lag level; clip if necessary. + +STEP 4d Find lag within the range which maximizes $\frac{C_I}{\sqrt{G_I}}$ . + +NOTE: negative values of $C_I$ are allowed. Compute the open loop subframe weighted error energy corresponding to that lag at the current subframe, and add the result to the frame weighted error accumulator corresponding to the trajectory being evaluated. + +STEP 4e If the current subframe index is $> 1$ , decrement the pointer to the current subframe, and go to step 4a. + +STEP 5 Store the lags defining the frame lag trajectory derived and the open loop LTP frame weighted error energy which this trajectory yields. Increment the counter of evaluated frame lag trajectories. + +STEP 6 Go to step 2. + +STEP 7 If $m < 4$ , increment $m$ and go to step 2. + +STEP 8 Choose, from the set of constructed frame lag trajectories, a lag trajectory which yields the lowest LTP weighted error energy for the frame, as the selected frame lag trajectory. + +#### 4.1.8.4 Voicing mode selection + +The frame lag trajectory is specified by a vector $K=\{k_1,k_2,k_3,k_4\}$ , where $k_m$ is the open loop LTP lag at the m-th subframe. Define the interpolated correlation of the input spectrally weighted speech $y(n)$ at the m-th subframe, specified by lag $k_m$ , as $C_I(k_m,m)$ and the interpolated energy of $y(n)$ , delayed by $k_m$ samples relative to the m-th subframe, as $G_I(k_m,m)$ . + +The open loop LTP prediction gain in dB at the m-th subframe is: + +$$P_m = 10 \log_{10} \left[ \frac{R(0,m)}{R(0,m) - \frac{C_I^2(k_m,m)}{G_I(k_m,m)}} \right] \quad (94)$$ + +The open loop frame LTP prediction gain, is given by: + +$$P_v = 10 \log_{10} \left[ \frac{\sum_{m=1}^4 R(0,m)}{\sum_{m=1}^4 \left[ R(0,m) - \frac{C_{peak}^2(0,m)}{G_{peak}(0,m)} \right]} \right] \quad (95)$$ + +The rules for mode selection are specified as follows: + +$$\text{MODE}=0 \text{ if } P_v < 1,7 \quad (96)$$ + +$$\text{MODE}=1 \text{ if } P_v \geq 1,7 \text{ and } P_m < 3,5 \text{ for any } m \quad (97)$$ + +$$\text{MODE}=2 \text{ if } P_m \geq 3,5 \text{ for all } m \text{ and } P_m < 7 \text{ for any } m \quad (98)$$ + +$$\text{MODE}=3 \text{ if } P_m \geq 7,0 \text{ for all } m \quad (99)$$ + +#### 4.1.8.5 Closed loop lag search + +From the selected frame lag trajectory, develop a list of lags to be searched closed loop. At each subframe, three allowable lag levels centered around the subframe lag, specified by the selected frame lag trajectory, will be searched. If the lag points to the lowest or the highest level in the table of quantized lag values, only two closed loop lag evaluations will be done at that subframe, with the lag outside the quantizer range being eliminated from consideration. The closed loop evaluation of the subframe lags is not performed if MODE=0. What follows is a description of the construction of the output of the long term predictor (adaptive codebook) for a given, possibly fractional lag, L. Defining: + +| | | +|------------------|-----------------------------------------------------------------------------------------------------------------------| +| $L_{max}$ | maximum possible value for long term lag L | +| $r(n)$ | long term filter state; $n < 0$ (history of the excitation signal) | +| $r_L(n)$ | long term filter state with adaptive codebook output for L appended | +| $b_L(n)$ | output of long term filter state (adaptive codebook) for lag L | +| $P_f$ | order of one phase of the interpolating FIR filter ( $P_f = 10$ except for the special case when $j = 0$ , see below) | +| $\tilde{f}_j(i)$ | coefficients of jth phase of interpolating FIR filter, $i=0$ to $i=P_f-1$ | +| $N_s$ | number of samples per subframe ( $N_s = 40$ ) | + +The sequence $r_L(n)$ is defined as: + +$$r_L(n) = \begin{cases} r(n) & ; -L_{\max} \leq n \leq -1 \\ \sum_{i=0}^{P_f-1} \tilde{f}_j(i) r_L\left(n - \Lambda - \frac{P_f}{2} + i\right) & ; 0 \leq n \leq N_s - 1 \end{cases} \quad (100)$$ + +where; $q = \left\lfloor \frac{n + L + \frac{5}{6}}{L} \right\rfloor L$ , $\Lambda = \lfloor q \rfloor$ , and $j = 6(q - \lfloor q \rfloor)$ + +The portion of the sequence $r_L(n)$ from $n=0$ to $n=N_s-1$ shall be calculated in order from 0 to $N_s-1$ , so that the necessary terms in the sum will be available. The 0th phase of the interpolating filter, $\tilde{f}_0(i)$ , is a special case and has only one non-zero tap, so that if $q$ is an integer, the summation reduces to the single term, $r_L(n-q)$ . + +The output of the codebook for lag $L$ is just the last $N_s$ samples in the sequence $r_L(n)$ . + +$$b_L(n) = r_L(n) \quad ; 0 \leq n \leq N_s-1 \quad (101)$$ + +The closed loop search minimizes the weighted error by maximizing the term $\frac{C^2}{G}$ , where + +$$C = \sum_{n=0}^{N_s-1} b'_L(n) p(n) \quad (102)$$ + +$$G = \sum_{n=0}^{N_s-1} b'^2_L(n) \quad (103)$$ + +The sequence $b'_L(n)$ is the zero state response of $H(z)$ to the adaptive codebook output for lag $L$ . The sequence $p(n)$ is the input speech, weighted by the filter $W(z)$ , minus the zero input response of $H(z)$ . The error minimization is done over only those lags in the list supplied by the open loop search. The lag $L$ which maximizes $\frac{C}{\sqrt{G}}$ ( $C$ is allowed to be negative) is then chosen as the lag for the subframe. + +### 4.1.9 Harmonic noise weighting + +If $MODE = 1, 2$ or $3$ , then $C(z)$ , the harmonic noise weighting transfer function, is activated. The excitation codebook vector and gains codebook vector are selected to minimize the spectrally and harmonically weighted error. The harmonic weighting filter, $C(z)$ , can be expressed as: + +$$C(z) = 1 - \lambda_{hnw} z^{-L_{pitch}} \quad (104)$$ + +where + +$$\lambda_{hnw} = 0,4 \frac{C_{pitch}}{G_{pitch}} \quad (105)$$ + +$C_{pitch}$ , $G_{pitch}$ and $L_{pitch}$ were determined during the open loop lag search where the subscript $m$ denoting the subframe has been dropped from $L_{pitch,m}$ and $\lambda_{hnw,m}$ for notational convenience. $L_{pitch}$ can take on fractional values so the interpolating filter employed for the open loop lag search is utilized to generate the fractionally delayed samples. + +Let $x(n)$ represent the input of the harmonic noise weighting filter and $y(n)$ represent the output. The filter can then be described by equation (106) and equation (107). + +$$y(n) = x(n) - \lambda_{hnw} x(n - L_{pitch}) \quad (106)$$ + +$$x\left(n - L_{pitch}\right) = \sum_{i=0}^{P_g-1} g_j(i) x\left(n - \left\lfloor L_{pitch} \right\rfloor - \frac{P_g}{2} + i\right) \quad (107)$$ + +where + +$$j = \left(L_{pitch} - \left\lfloor L_{pitch} \right\rfloor\right) 6$$ + +Figure 4 incorporates harmonic noise weighting (for MODE = 1, 2 or 3) and shows the VSELP excitation source. All error minimizations done after lag selection utilize the combination of spectral and harmonic noise weighting. + +For MODE $\neq 0$ , $P(n)$ is the input speech signal weighted by $W(z)C(z)$ minus the input response of $H(z)C(z)$ . For MODE = 0, $P(n)$ is the input speech signal weighted by $W(z)$ minus the zero input response of $H(z)$ . + +![Figure 4: Long term predictor lag and code search. The diagram shows two signal flow graphs for different modes. The top graph for MODE=1,2, or 3 shows the long term predictor lag L being processed through a 'Long term Filter state' block to produce b_L(n), which is then multiplied by beta. Simultaneously, a 'VSELP Codebook' block takes inputs I and gamma to produce an excitation vector, which is multiplied by gamma. These two signals are summed and then processed through filters H(z) and C(z) to produce p''(n). The error e(n) is calculated as the difference between p(n) and p''(n), and the total weighted error is the sum of the squared error. The bottom graph for MODE=0 shows two 'VSELP Codebook' blocks, one taking inputs I and beta, and the other taking inputs H and gamma. Their outputs are multiplied by gamma and summed, then processed through filter H(z) to produce p''(n). The error e(n) is calculated as the difference between p(n) and p''(n), and the total weighted error is the sum of the squared error.](dd5771673aececa53d42ece89218299d_img.jpg) + +Figure 4 illustrates the long term predictor lag and code search process for two different modes. + +**MODE=1,2, or 3:** The diagram shows the following signal flow: + + +- Inputs $L$ and $\beta$ are processed by a "Long term Filter state" block to produce $b_L(n)$ . +- $b_L(n)$ is multiplied by $\beta$ . +- Inputs $I$ and $\gamma$ are processed by a "VSELP Codebook" block to produce an excitation vector. +- This excitation vector is multiplied by $\gamma$ . +- The two resulting signals are summed ( $+$ ). +- The sum is processed by filter $H(z)$ and then filter $C(z)$ to produce $p''(n)$ . +- The error $e(n)$ is calculated as $p(n) - p''(n)$ . +- The total weighted error is calculated as $\sum (e(n))^2$ . + +**MODE=0:** The diagram shows the following signal flow: + + +- Inputs $I$ and $\beta$ are processed by "VSELP Codebook 1" to produce an excitation vector. +- This excitation vector is multiplied by $\beta$ . +- Inputs $H$ and $\gamma$ are processed by "VSELP Codebook 2" to produce another excitation vector. +- This excitation vector is multiplied by $\gamma$ . +- The two resulting signals are summed ( $+$ ). +- The sum is processed by filter $H(z)$ to produce $p''(n)$ . +- The error $e(n)$ is calculated as $p(n) - p''(n)$ . +- The total weighted error is calculated as $\sum (e(n))^2$ . + +Figure 4: Long term predictor lag and code search. The diagram shows two signal flow graphs for different modes. The top graph for MODE=1,2, or 3 shows the long term predictor lag L being processed through a 'Long term Filter state' block to produce b\_L(n), which is then multiplied by beta. Simultaneously, a 'VSELP Codebook' block takes inputs I and gamma to produce an excitation vector, which is multiplied by gamma. These two signals are summed and then processed through filters H(z) and C(z) to produce p''(n). The error e(n) is calculated as the difference between p(n) and p''(n), and the total weighted error is the sum of the squared error. The bottom graph for MODE=0 shows two 'VSELP Codebook' blocks, one taking inputs I and beta, and the other taking inputs H and gamma. Their outputs are multiplied by gamma and summed, then processed through filter H(z) to produce p''(n). The error e(n) is calculated as the difference between p(n) and p''(n), and the total weighted error is the sum of the squared error. + +Figure 4: Long term predictor lag and code search + +The zero state response of $H(z)C(z)$ to the pitch predictor (adaptive codebook) vector, $b_L(n)$ , needs to be computed prior to the search of the excitation codebook. This spectrally and harmonically weighted adaptive codebook vector is represented by $b''_L(n)$ . + +### 4.1.10 Code search algorithm + +For $MODE \neq 0$ , the excitation codebook search procedure takes place after the long term predictor lag, $L$ , has been determined. The codebook search procedure then chooses one codevector from the VSELP codebook. The GSM half rate speech encoder uses an excitation codebook of $2^M$ codevectors which is constructed from $M$ basis vectors. Defining $v_m(n)$ as the $m^{\text{th}}$ basis vector and $u_i(n)$ as the $i^{\text{th}}$ codevector in the codebook, then: + +$$u_i(n) = \sum_{m=1}^M \theta_{im} v_m(n) \quad (108)$$ + +where $0 \leq i \leq 2^M-1$ ; $0 \leq n \leq N_s-1$ . In other words, each codevector in the codebook is constructed as a linear combination of the $M$ basis vectors. The linear combinations are defined by the $\theta$ parameters. + +$\theta_{im}$ is defined as: + +$$\theta_{im} = +1 \text{ if bit } m \text{ of codeword } i = 1$$ + +$$\theta_{im} = -1 \text{ if bit } m \text{ of codeword } i = 0$$ + +The codebook construction for the GSM half rate speech encoder can be restated as follows. Codevector $i$ is constructed as the sum of the $M$ basis vectors where the sign (plus or minus) of each basis vector is determined by the state of the corresponding bit in codeword $i$ . The codebook search procedure finds the codevector which will produce the minimum total spectral and harmonic weighted error for the subframe given $b''_L(n)$ (the zero state response of $H(z)C(z)$ to $b_L(n)$ ) and allowing both the gain, $\gamma$ , and the long term filter coefficient, $\beta$ , to be optimized for each codevector being evaluated. + +The filtered codevector $f_i(n)$ , can be expressed as: + +$$f_i(n) = \sum_{m=1}^M \theta_{im} q_m(n) \quad (109)$$ + +where $q_m(n)$ is the zero state response of $H(z)C(z)$ to basis vector $v_m(n)$ . + +If MODE=0, two VSELP codebooks are the excitation sources and are searched sequentially to identify the codeword $I$ specifying the codevector selected from the first codebook, and codeword $H$ , identifying the codevector chosen from the second VSELP codebook. Harmonic noise weighting is not used. When searching the second VSELP codebook, each codevector is evaluated assuming optimal gains for the codevector $I$ , and the potential codevector $H$ . + +#### 4.1.10.1 Decorrelation of filtered basis vectors + +For MODE $\neq$ 0, each filtered codevector, $f_i(n)$ , is decorrelated to the long term predictor vector, $b''_L(n)$ . If MODE=0, the $b_L(n)$ vector and the single VSELP codebook excitation are replaced by two VSELP codebook excitations, as the excitation sources. In this case, decorrelation is only performed for the second VSELP codebook. In this case, the orthogonalization is done with respect to the filtered codevector chosen from the first VSELP codebook. + +Defining: + +$$\Gamma = \sum_{n=0}^{N_s-1} (b''_L(n))^2 \quad (110)$$ + +and + +$$\Psi_m = \sum_{n=0}^{N_s-1} b''_L(n) q_m(n) \quad (111)$$ + +for $1 \leq m \leq M$ ; then $q'_m(n)$ , the decorrelated filtered basis vectors, can be computed by: + +$$q'_m(n) = q_m(n) - \left( \frac{\Psi_m}{\Gamma} \right) b''_L(n) \quad (112)$$ + +for $1 \leq m \leq M$ and $0 \leq n \leq N_s-1$ . + +The decorrelated filtered codevectors can now be expressed as: + +$$f'_i(n) = \sum_{m=1}^M \theta_{im} q'_m(n) \quad (113)$$ + +for $0 \leq i \leq 2^M-1$ and $0 \leq n \leq N_s-1$ . + +#### 4.1.10.2 Fast search technique + +The codebook search procedure should find the codeword $i$ which minimizes: + +$$E'_i = \sum_{n=0}^{N_s-1} (p(n) - \gamma f'_i(n))^2 \quad (114)$$ + +Defining : + +$$C_i = \sum_{n=0}^{N_s-1} f'_i(n)p(n) \quad (115)$$ + +and + +$$G_i = \sum_{n=0}^{N_s-1} (f'_i(n))^2 \quad (116)$$ + +then the best codevector is the one which maximizes: + +$$\frac{(C_i)^2}{G_i} \quad (117)$$ + +and the corresponding optimal gain is given by: + +$$\gamma_i = \frac{C_i}{G_i} \quad (118)$$ + +The search process needs to evaluate equation (117) for each codevector. The codevector which maximizes equation (117) is then chosen. Using properties of the VSELP codebook construction, the computations required for computing $C_i$ and $G_i$ can be greatly simplified. + +defining: + +$$R_m = 2 \sum_{n=0}^{N_s-1} q'_m(n)p(n) \quad (119)$$ + +for $1 \leq m \leq M$ and + +$$D_{mj} = 4 \sum_{n=0}^{N_s-1} q'_m(n)q'_j(n) \quad (120)$$ + +for $1 \leq m \leq j \leq M$ + +$C_i$ can be expressed as: + +$$C_i = \frac{1}{2} \sum_{m=1}^M \theta_{im} R_m \quad (121)$$ + +and $G_i$ can be expressed as: + +$$G_i = \frac{1}{2} \sum_{j=2}^M \sum_{m=1}^{j-1} \theta_{im} \theta_{ij} D_{mj} + \frac{1}{4} \sum_{j=1}^M D_{jj} \quad (122)$$ + +Assuming that codeword $u$ differs from codeword $i$ in only one bit position, say position $v$ such that $\theta_{uv} = -\theta_{iv}$ and $\theta_{um} = \theta_{im}$ for $m \neq v$ then: + +$$C_u = C_i + \theta_{uv} R_v \quad (123)$$ + +and + +$$G_u = G_i + \sum_{j=1}^{v-1} \theta_{uj} \theta_{uv} D_{jv} + \sum_{j=v+1}^M \theta_{uj} \theta_{uv} D_{vj} \quad (124)$$ + +The codebook search is structured such that each successive codeword evaluated differs from the previous codeword in only one bit position, then equation (123) and equation (124) can be used to update $C_i$ and $G_i$ in a very efficient manner. Sequencing of the codewords in this manner is accomplished using a binary Gray code. This updating operation for both equation (123) and equation (124) can be accomplished with a total of only $M$ multiply-accumulates per codevector. + +With this technique for computing $C_i$ and $G_i$ for the codevectors in a VSELP codebook, it is necessary to find the $i$ which maximizes equation (117). Note that complementary codewords (see subclause 3.1.10) will have equivalent values for equation (117). Therefore only half of the codevectors need to be evaluated. Once the codevector which maximizes equation (117) is found, the sign of $C_i$ for that codevector will determine whether that codevector or its complement will yield a positive gain, $\gamma$ . + +A running maximum for equation (117) is kept during the code search then for each codevector evaluated, evaluate equation (117) and compare to the running maximum. + +$$\frac{(C_i)^2}{G_i} > \frac{(C_{best})^2}{G_{best}} \quad (125)$$ + +Evaluating equation (125) directly from $C_i$ and $G_i$ requires one multiply, one divide and one compare operation. By cross multiplying equation (117) can be expressed as: + +$$(C_i)^2 G_{best} > (C_{best})^2 G_i \quad (126)$$ + +Using equation (126) requires only three multiplies and a compare per evaluation (and no divides) where $(C_{best})^2$ and $G_{best}$ are updated throughout the search to reflect the running best codeword. + +### 4.1.11 Multimode gain vector quantization + +A separate GSP0 vector quantizer is derived for each of the four voicing modes. Once the frame voicing mode is selected, the vector quantizer, corresponding to that mode, is searched to select the excitation gains at each subframe of the frame. + +Although the interpretation of what the excitation sources are differs between MODE=0 and the remaining MODE values, the procedure for searching the gain vector quantizer is identical. In each case, the P0 term specifies the relative contribution of the first of the two excitation vectors to the total excitation energy at the subframe, where the first excitation vector is the long term prediction vector for MODE=1, 2 or 3, while the vector selected from the first of the two VSELP codebooks is used in the MODE=0 case. + +#### 4.1.11.1 Coding GS and P0 + +Define $ex(n)$ to be the excitation function at a given subframe. For MODE=1, 2 or 3, $ex(n)$ is a linear combination of the pitch prediction vector scaled by $\beta$ , the long term predictor coefficient, and of the codevector scaled by $\gamma$ , its gain. In equation form + +$$ex(n) = \beta c_0(n) + \gamma c_1(n) \quad 0 \leq n \leq N_s-1 \quad (127)$$ + +where for MODE $\neq$ 0 + +$c_0(n)$ is the unweighted long term prediction vector, $b_L(n)$ + +$c_1(n)$ is the unweighted codevector selected, $u_I(n)$ + +and for MODE=0 + +$c_0(n)$ is the unweighted codevector selected from the first VSELP codebook, $u_{I,1}(n)$ + +$c_1(n)$ is the unweighted codevector selected from the second VSELP codebook, $u_{H,2}(n)$ + +The variable $c'_j(n)$ is a weighted version of $c_j(n)$ . The power in each excitation vector is given by + +$$R_x(k) = \sum_{n=0}^{N_s-1} c_k^2(n) \quad 0 \leq k \leq 1 \quad (128)$$ + +Let $R$ be the total power in the coder subframe excitation + +$$R = \beta^2 R_x(0) + \gamma^2 R_x(1) \quad (129)$$ + +$P_0$ , the power contribution of the pitch prediction vector as a fraction of the total excitation power at a subframe, + +$$P_0 = \frac{\beta^2 R_x(0)}{R} \quad \text{where } 0 \leq P_0 \leq 1 \quad (130)$$ + +Define $R'_q(0)$ to be the quantized value of $R(0)$ to be used for the current subframe and $R_q(0)$ to be the quantized value of $R(0)$ . Then: + +$$R'_q(0) = R_q(0)_{\text{previous frame}} \quad \text{for subframe 1} \quad (131a)$$ + +$$R'_q(0) = R_q(0)_{\text{current frame}} \quad \text{for subframes 2, 3, 4} \quad (131b)$$ + +Let $RS$ be + +$$RS = N_s R'_q(0) \prod_{i=1}^{N_p} (1 - r_i^2) \quad (132)$$ + +The term $GS$ is the energy tweak parameter defined as + +$$R = GS \cdot RS \rightarrow GS = \frac{R}{RS} \quad (133)$$ + +$P_0$ represents the fraction of the total subframe excitation energy which is due to the first codebook vector, and $GS$ , the energy tweak factor which bridges the gap between $R$ , the actual energy in the coder excitation, and $RS$ , its estimated value. + +The gain bias factor $\chi$ , formulated to force a better energy match between $p(n)$ and the weighted synthetic excitation, is given below where. + +$$\chi = \min \left[ \sqrt{2, 0}, \left\{ \max \left[ 1, 0, \sqrt{\frac{R_{pp}}{\beta_{opt}^2 R_{cc}(0,0) + \gamma_{opt}^2 R_{cc}(1,1) + 2\beta_{opt} \gamma_{opt} R_{cc}(0,1)}}} \right] \right\} \right] \quad (134)$$ + +The weighted error equation is + +$$E = \chi^2 R_{pp} - a \sqrt{GS P_0} - b \sqrt{GS (1 - P_0)} + c GS \sqrt{P_0 (1 - P_0)} + d GS P_0 + e GS (1 - P_0) \quad (135)$$ + +where + +$$a = 2\chi R_{pc}(0) \sqrt{\frac{RS}{R_x(0)}} \quad (136)$$ + +$$b = 2\chi R_{pc}(1) \sqrt{\frac{RS}{R_x(1)}} \quad (137)$$ + +$$c = \frac{2R_{cc}(0,1)RS}{\sqrt{R_x(0)R_x(1)}} \quad (138)$$ + +$$d = \frac{RS R_{cc}(0,0)}{R_x(0)} \quad (139)$$ + +$$e = \frac{RS R_{cc}(1,1)}{R_x(1)} \quad (140)$$ + +$$R_{pc}(k) = \sum_{n=0}^{N_s-1} p(n) c'_k(n) \quad k=0,1 \quad (141)$$ + +$$R_{cc}(k,j) = \sum_{n=0}^{N_s-1} c'_k(n) c'_j(n) \quad k=0,1, j=k,1 \quad (142)$$ + +$$R_{cc}(k,j) = R_{cc}(j,k) \quad (143)$$ + +$$R_{pp} = \sum_{n=0}^{N_s-1} p^2(n) \quad (144)$$ + +Four separate vector quantizers for jointly coding P0 and GS are defined, one for each of the four voicing modes. The first step in quantizing of P0 and GS consists of calculating the parameters required by the error equation: + +$$R_{cc}(k,j) \quad k = 0, 1, j = k, 1$$ + +$$R_x(k) \quad k = 0, 1$$ + +$$RS$$ + +$$R_{pc}(k) \quad k = 0, 1$$ + +$$a, b, c, d, e$$ + +Next equation (135) is evaluated for each of the 32 vectors in the {P0,GS} codebook, corresponding to the selected voicing mode, and the vector which minimizes the weighted error is chosen. Note that in conducting the code search $\chi^2 R_{pp}$ may be ignored in equation (135), since it is a constant. $\beta_q$ , the quantized long term predictor coefficient, and $\gamma_q$ , the quantized gain, are reconstructed from + +$$\beta_q = \sqrt{\frac{RS GS_{vq} P0_{vq}}{R_x(0)}} \quad (145)$$ + +$$\gamma_q = \sqrt{\frac{RS GS_{vq} (1 - P0_{vq})}{R_x(1)}} \quad (146)$$ + +where P0vq and GSvq are the elements of the vector chosen from the {P0,GS} codebook. + +A special case occurs when the long term predictor is disabled for a certain subframe, but voicing MODE $\neq$ 0. This will occur when the state of the long term predictor is populated entirely by zeroes. + +For that case, the following error equation is used: + +$$E \cong \chi^2 R_{pp} - b\sqrt{GS} + eGS \quad (147)$$ + +For this case the quantized codevector gains are: + +$$\beta_q = 0 \quad (148)$$ + +$$\gamma_q = \sqrt{\frac{RS GS_{vq} (1 - P0_{vq})}{R_x(1)}} \quad (149)$$ + +## 4.2 GSM half rate speech decoder + +![Block diagram of the GSM half rate speech decoder for MODE = 1, 2 or 3. The diagram shows the flow from input parameters (LPC 1-3, R0, INT_LPC, MODE, LAG_1-4, CODE_1-4, GSP 0_1-4) through various processing blocks including gain calculation, long-term filtering, VSELP codebook selection, pitch prefiltering, synthesis filtering, spectral postfiltering, and automatic gain control to produce the output speech signal.](3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg) + +The diagram illustrates the GSM half rate speech decoder architecture. On the left, input parameters are grouped into three sets: + +- LPC parameters:** LPC 1, LPC 2, LPC 3, R0, and INT\_LPC. These are fed into a 'calculation of gains' block and a 'Long Term Filter State' block. +- MODE and codebook parameters:** MODE, LAG\_1, CODE\_1, LAG\_2, CODE\_2, LAG\_3, CODE\_3, LAG\_4, and CODE\_4. These are fed into a 'calculation of gains' block, a 'VSELP Codebook' block, and a gain multiplier 'γ'. +- Gain parameters:** GSP 0\_1, GSP 0\_2, GSP 0\_3, and GSP 0\_4. These are fed into the 'calculation of gains' block. + +The 'calculation of gains' block outputs two gain values, 'β' and 'γ'. The 'Long Term Filter State' block, receiving 'L' and 'β', outputs a signal $b_L(n)$ . The 'VSELP Codebook' block, receiving 'γ' and 'I', outputs a codevector. These two signals are summed ( $+$ ) to produce the combined excitation signal $ex(n)$ . This signal is then processed by a 'pitch prefilter' to produce $ex_{ps}(n)$ . The 'pitch prefilter' also receives feedback from the 'synthesis filter' output $s(n)$ . The signal $ex_{ps}(n)$ is then processed by a 'synthesis filter', which also receives feedback from the 'spectral postfilter' output. The output of the synthesis filter is $s(n)$ . This signal is then processed by a 'spectral postfilter', which also receives feedback from the 'automatic gain control' output. The output of the spectral postfilter is then processed by an 'automatic gain control' block, which produces the final 'output speech' signal. + +Block diagram of the GSM half rate speech decoder for MODE = 1, 2 or 3. The diagram shows the flow from input parameters (LPC 1-3, R0, INT\_LPC, MODE, LAG\_1-4, CODE\_1-4, GSP 0\_1-4) through various processing blocks including gain calculation, long-term filtering, VSELP codebook selection, pitch prefiltering, synthesis filtering, spectral postfiltering, and automatic gain control to produce the output speech signal. + +Figure 5: The GSM half rate speech decoder for MODE = 1, 2 or 3 + +A block diagram of the GSM half rate speech decoder for MODE=1, 2 or 3 is given in figure 5. The speech decoder creates the combined excitation signal, $ex(n)$ , from the long term filter state and the VSELP codevector. For MODE=0, the long term filter state is replaced by another VSELP codebook and the pitch prefilter is not used. The combined excitation is then processed by an adaptive pitch prefilter and gain. The prefiltered excitation is applied to the LPC synthesis filter. After reconstructing the speech signal with the synthesis filter, an adaptive spectral postfilter is applied followed by an automatic gain control which is the final processing step in the speech decoder. + +### 4.2.1 Excitation generation + +The combined excitation, $ex(n)$ , shall be computed as shown in equation (127) + +The combined excitation, $ex(n)$ , is filtered by the synthesis filter to generate the speech signal. The synthesis filter is a tenth order all pole filter. The filter coefficients for the subframe are the $\alpha_i$ 's defined in subclause 4.1.6. The filter coefficients will change from subframe to subframe. The filter state shall be preserved from subframe to subframe. A direct form filter shall be used for the synthesis filter. + +### 4.2.2 Adaptive pitch prefilter + +Given $ex(n)$ as the input, $ex_p(n)$ , the pitch prefiltered output, is defined by + +$$ex_p(n) = ex(n) + \xi ex_p(n - L) \quad ; \text{for } 0 \leq n \leq N_s - 1 \quad (150)$$ + +where + +$$\xi = \begin{cases} 0, 3 \text{Min}[\beta, \sqrt{P0}] & ; \text{MODE} \neq 0 \\ 0 & ; \text{MODE} = 0 \end{cases} \quad (151)$$ + +Since $L$ can be fractional in value, an interpolating filter is used. This is the same interpolating filter which is used for the open loop lag search. A gain scale factor is computed and is used to scale the pitch prefiltered excitation, prior to applying it to the LPC synthesis filter. $P_{scale}$ , the gain scale factor, is + +$$P_{scale} = \sqrt{\frac{\sum_{n=0}^{N-1} ex^2(n)}{\sum_{n=0}^{N-1} ex_p^2(n)}} \quad (152)$$ + +Thus $ex_{ps}(n)$ , the gain corrected pitch prefiltered excitation which drives the LPC synthesis filter, is given by + +$$ex_{ps}(n) = P_{scale} ex_p(n) \quad ; \text{for } 0 \leq n \leq N_s - 1 \quad (153)$$ + +### 4.2.3 Synthesis Filter + +A direct form synthesis filter is used: + +$$s(n) = ex_{ps}(n) + \sum_{i=1}^{10} \alpha_i s(n - i) \quad , 0 \leq n \leq N_s - 1 \quad (154)$$ + +### 4.2.4 Adaptive spectral postfilter + +The perceptual quality of the synthetic speech is enhanced by using an adaptive postfilter as the final processing step. The general form of the postfilter is given by: + +$$\bar{s}(n) = s(n) - \sum_{i=1}^{N_p} r_i^j \alpha_i s(n - i) \quad , 0 \leq n \leq N_s - 1 \quad (155)$$ + +$$\hat{s}(n) = \bar{s}(n) + \sum_{i=1}^{N_p} (0,75)^i \alpha_i \bar{s}(n - i) \quad , 0 \leq n \leq N_s - 1 \quad (156)$$ + +$$\hat{s}(n) = \bar{s}(n) - 0,2\bar{s}(n-1) \quad 0 \leq n \leq N_s-1 \quad (157)$$ + +The adaptive spectral postfilter numerator polynomial equation (155) is replaced by a spectrally smoothed version of the adaptive spectral postfilter denominator polynomial equation (156). To derive the coefficients of the numerator polynomial, the denominator polynomial coefficients are converted to the autocorrelation coefficients $R(i)$ . The SST bandwidth expansion function is then applied to the autocorrelation sequence, + +$$R_{sst}(i) = R(i)W_{sst}(i) \quad , 0 \leq i \leq N_p \quad (158)$$ + +and the numerator polynomial coefficients are calculated from the modified autocorrelation sequence via the AFLAT recursion. + +From $R_{sst}(i)$ the reflection coefficients which define the combined spectrally noise weighted synthesis filter are computed using the AFLAT recursion once per frame. + +STEP 1 Define the initial conditions for the AFLAT recursion: + +$$P_o(i) = R_{sst}(i) \quad , 0 \leq i \leq N_p \quad (159)$$ + +$$V_o(i) = R_{sst}(|i+1|) \quad , 1-N_p \leq i \leq N_p-1 \quad (160)$$ + +STEP 2 Initialize $j$ , the index of the lattice stage, to point to the first lattice stage: + +$$j=1 \quad (161)$$ + +STEP 3 Compute $r_j$ , the $j$ -th reflection coefficient, using: + +$$r_j = -\frac{V_{j-1}(0)}{P_{j-1}(0)} \quad (162)$$ + +STEP 4 Given $r_j$ , update the values of $V_j$ and $P_j$ arrays using: + +$$P_j(i) = (1+r_j^2)P_{j-1}(i) + r_j[V_{j-1}(i) + V_{j-1}(-i)] \quad , 0 \leq i \leq N_p - j - 1 \quad (163)$$ + +$$V_j(i) = V_{j-1}(i+1) + r_j^2 V_{j-1}(-i-1) + 2r_j P_{j-1}(|i+1|) \quad , 1+j-N_p \leq i \leq N_p-j-1 \quad (164)$$ + +STEP 5 Increment $j$ : + +$$j = j + 1$$ + +STEP 6 If $j \leq N_p$ go to step 3, otherwise all $N_p$ reflection coefficients have been obtained. + +STEP 7 The reflection coefficients, $r_j$ , are then converted to $\bar{\alpha}_i$ , the direct-form LP filter coefficients for use in the adaptive spectral postfilter numerator polynomial. + +The resultant adaptive spectral postfilter is derived from equations 155, 156 and 157: + +$$\bar{s}(n) = s(n) - \sum_{i=1}^{N_p} \bar{\alpha}_i s(n-i) \quad , 0 \leq n \leq N_s-1 \quad (165)$$ + +$$\tilde{s}(n) = \bar{s}(n) + \sum_{i=1}^{N_p} (0,75)^i \alpha_i \tilde{s}(n-i) \quad , 0 \leq n \leq N_s-1 \quad (166)$$ + +$$\hat{s}(n) = \tilde{s}(n) - 0,2\tilde{s}(n-1) \quad , 0 \leq n \leq N_s-1 \quad (167)$$ + +In order to reduce the computations needed to compute the spectrally smoothed numerator coefficients, the spectral smoothing operation is performed once per frame on the denominator coefficients corresponding to the uninterpolated coefficients. This will yield the coefficients for the numerator of the spectral postfilter for subframe four. The numerator + +coefficients for subframes one, two, and three are interpolated using the same interpolation scheme that is used for the LPC synthesis coefficients (see subclause 4.1.6). + +As in the case of the pitch prefilter, a means of automatic gain control is needed to ensure unity gain through the spectral postfilter. A scale factor, $S_{\text{scale}}$ , is given by: + +$$S'_{\text{scale}}(n) = (0,9875 S'_{\text{scale}}(n-1) ) + (0,0125 S_{\text{scale}} ) \quad (168)$$ + +Scale factor, $S_{\text{scale}}$ , is the square root of the ratio of the input signal energy to the output signal energy over the subframe. + +The output of the spectral postfilter is then multiplied by $S'_{\text{scale}}$ as the last step in reconstructing the speech signal in the speech decoder. + +### 4.2.5 Updating decoder states + +The long term predictor state, $r(n)$ , is updated by: + +$$r(n) = r(n+40) \quad \text{for } -146 \leq n \leq -41 \quad (169)$$ + +$$r(n) = \text{ex}(n+40) \quad \text{for } -40 \leq n \leq -1 \quad (170)$$ + +# 5 Homing sequences + +## 5.1 Functional description + +The half rate speech codec as well as the DTX system and comfort noise generator are described in a bit exact arithmetic to allow for easy type approval as well as general testing purposes of the half rate speech codec. + +The response of the codec to a predefined input sequence can only be foreseen if the internal state variables of the codec are in a predefined state at the beginning of the experiment. Therefore, the codec has to be put in a so called home state before a bit exact test can be performed. This is usually done by a reset. + +To allow a reset of the codec in remote locations, special homing frames have been defined for the encoder and the decoder, thus enabling a codec homing by inband signalling. + +The codec homing procedure is defined in such a way, that on either direction (encoder or decoder), the homing functions are called after processing the homing frame that is input. The output corresponding to the first homing frame is therefore dependent on the codec state when receiving that frame and hence usually not known. The response to any further homing frame in one direction is by definition a homing frame of the other direction. This procedure allows homing of both, the encoder and decoder from either side, if a loop back configuration is implemented, taking proper framing into account. + +## 5.2 Definitions + +**encoder homing frame:** The encoder homing frame consists of 160 identical samples, each 13 bit long, with the least significant bit set to "one" and all other bits set to "zero". When written to 16 bit long words with left justifications, the samples have a value of 0008 hex. Test sequence SEQ05.INP described in GSM 06.07 [3] defines the encoder homing frame. The speech decoder has to produce this frame as a response to the second and any further decoder homing frame if at least two decoder homing frames were input to the decoder consecutively. + +**decoder homing frame:** The decoder homing frame has a fixed set of speech parameters as defined in test sequence SEQ05.INP described in GSM 06.07 [3]. It is the natural response of the speech encoder to the second and any further encoder homing frame if at least two encoder homing frames were input to the encoder consecutively. + +## 5.3 Encoder homing + +Whenever the half rate speech encoder receives at its input an encoder homing frame exactly aligned with its internal speech frame segmentation, the following events take place: + +- Step 1: The speech encoder performs its normal operation including VAD and DTX and produces a speech parameter frame at its output which is in general unknown. But if the speech encoder was in its home state at the beginning of that frame, then the resulting speech parameter frame is identical to the decoder homing frame (this is the way how the decoder homing frame was constructed). +- Step 2: After successful termination of that operation, the speech encoder provokes the homing functions for all submodules including VAD and DTX and sets all state variables into their home state. On the reception of the next input frame, the speech encoder will start from its home state. + +NOTE: Applying a sequence of N encoder homing frames will cause at least N-1 decoder homing frames at the output of the speech encoder. + +## 5.4 Decoder homing + +Whenever the speech decoder receives at its input a decoder homing frame, then the following events take place: + +- Step 1: The speech decoder performs its normal operation including comfort noise generation and produces a speech frame at its output which is in general unknown. But if the speech decoder was in its home state at the beginning of that frame, then the resulting speech frame is replaced by the encoder homing frame. This would not naturally be the case but is forced by this definition here. +- Step 2: After successful termination of that operation, the speech decoder provokes the homing functions for all submodules including the comfort noise generator and sets all state variables into their home state. On the reception of the next input frame, the speech decoder will start from its home state. + +NOTE 1: Applying a sequence of N decoder homing frames will cause at least N-1 encoder homing frames at the output of the speech decoder. + +NOTE 2: By definition the first 58 bits of the decoder homing frame must differ in at least one bit position from the first 58 bits of any of the decoder test sequences. Therefore, if the decoder is in its home state, it is sufficient to check only these first 58 bits to detect a subsequent decoder homing frame. This definition is made to support a delay optimised implementation in the TRAUs uplink direction. + +## 5.5 Encoder home state + +In GSM 06.06 [2], a listing of all the encoder state variables with their predefined values when in the home state is given. + +## 5.6 Decoder home state + +In GSM 06.06 [2], a listing of all the decoder state variables with their predefined values when in the home state is given. + +# Annex A (normative): Codec parameter description + +## A.1 Codec parameter description + +The following is a list of all the parameters which are coded for each 20 ms speech frame. The basic data rate of the speech coder is 5,6 kbps. Therefore each 20 ms speech frame consists of 112 bits. These bits are given in table A.1. + +**Table A.1: Codec parameter description** + +| Parameter | No. of bits | Description | +|----------------------------------|-------------|------------------------------------------------| +| Frame bits: | | | +| MODE | 2 | voicing mode | +| R0 | 5 | frame energy | +| LPC1 | 11 | reflection coefficient vector $r_1$ - $r_3$ | +| LPC2 | 9 | reflection coefficient vector $r_4$ - $r_6$ | +| LPC3 | 8 | reflection coefficient vector $r_7$ - $r_{10}$ | +| INT_LPC | 1 | the soft interpolation bit for the frame | +| Subframe bits (MODE = 1,2 or 3): | | | +| LAG_1 | 8 | lag for first subframe | +| LAG_2 | 4 | lag delta code for second subframe | +| LAG_3 | 4 | lag delta code for third subframe | +| LAG_4 | 4 | lag delta code for fourth subframe | +| CODE_1 | 9 | codebook, I, for first subframe | +| CODE_2 | 9 | codebook, I, for second subframe | +| CODE_3 | 9 | codebook, I, for third subframe | +| CODE_4 | 9 | codebook, I, for fourth subframe | +| GSP0_1 | 5 | {P0,GS} code for first subframe | +| GSP0_2 | 5 | {P0,GS} code for second subframe | +| GSP0_3 | 5 | {P0,GS} code for third subframe | +| GSP0_4 | 5 | {P0,GS} code for fourth subframe | +| Subframe bits (MODE=0): | | | +| CODE1_1 | 7 | codebook code, I, for first subframe | +| CODE2_1 | 7 | codebook code, H, for first subframe | +| CODE1_2 | 7 | codebook code, I, for second subframe | +| CODE2_2 | 7 | codebook code, H, for second subframe | +| CODE1_3 | 7 | codebook code, I, for third subframe | +| CODE2_3 | 7 | codebook code, H for third subframe | +| CODE1_4 | 7 | codebook code, I, for fourth subframe | +| CODE2_4 | 7 | codebook code, H, for fourth subframe | +| GSP0_1 | 5 | {P0,GS} code for first subframe | +| GSP0_2 | 5 | {P0,GS} code for second subframe | +| GSP0_3 | 5 | {P0,GS} code for third subframe | +| GSP0_4 | 5 | {P0,GS} code for fourth subframe | + +### A.1.1 MODE + +The speech coder is defined by 4 voicing modes. MODE is a two bit code which specifies which of the four voicing modes is used at the current frame. The MODE indicates which definition of the frame bits to apply to the current frame. + +### A.1.2 R0 + +R0 is a code which represents the average signal power of the input speech for the frame. The average signal power is computed using an analysis window which is centered over the last 100 samples of the frame. + +### A.1.3 LPC1 - LPC3 + +The 10 reflection coefficients are vector quantized in three vector segments. The first vector segment codes reflection coefficients $r_1 - r_3$ , the second vector segment codes coefficients $r_4 - r_6$ , the third vector segment codes coefficients $r_7 - r_{10}$ . + +### A.1.4 LAG\_1 - LAG\_4 + +LAG\_1, the lag for the first subframe, can take on the value in the range of 21 to 142. Eight bits are used to encode the lag which may be fractional in value. Each of the remaining lag values ( LAG\_2 through LAG\_4) is delta coded relative to the preceding subframe's coded value of the lag, with a deviation of -8 to +7 allowable lag value levels specified by a four bit code. + +### A.1.5 CODEx\_1 - CODEx\_4 + +If $MODE \neq 0$ , the code value for the VSELP codebook is the codeword I as derived by the codebook search procedure. If $MODE=0$ , two VSELP codebooks are sequentially searched, with codeword I, specifying the codevector from the first VSELP codebook, assigned onto CODE1\_x, and codeword H, specifying the codeword selected from the second VSELP codebook, assigned onto CODE2\_x, where x is the subframe number. + +### A.1.6 GSP0\_1 - GSP0\_4 + +The {P0,GS} codebook contains the values needed to determine the gain factors for the excitation vectors of a given subframe. The index of the corresponding codebook entry is assigned to GSP0\_x. + +The speech coder is a multimode speech coder, defined by four voicing modes: + +| | | +|----------|-------------------| +| MODE = 0 | unvoiced | +| MODE = 1 | slightly voiced | +| MODE = 2 | moderately voiced | +| MODE = 3 | strongly voiced | + +If $MODE=0$ , the adaptive codebook (long-term predictor) and the VSELP codebook are replaced by two other VSELP codebooks. + +## A.2 Basic coder parameters + +The following are the basic parameters for the 5 600 bps GSM half rate speech codec system. + +| | | | +|----------------|----------------------------|---------------------| +| | sampling rate | 8 kHz | +| N F | frame length | 160 samples (20 ms) | +| N s | subframe length | 40 samples (5 ms) | +| N p | short term predictor order | 10 | + +# Annex B (normative): Order of occurrence of the codec parameters over Abis + +The order of occurrence of the codec parameters over the Abis is defined for unvoiced speech (MODE = 0) and voiced speech (MODE = 1, 2 or 3) in tables B.1 and B.2 respectively. + +**Table B.1: Occurrence of the codec parameters over Abis for unvoiced speech (MODE = 0)** + +| Parameter | No. of bits | Bit No. (MSB - LSB) | +|-----------|-------------|---------------------| +| R0 | 5 | b1 - b5 | +| LPC1 | 11 | b6 - b16 | +| LPC2 | 9 | b17 - b25 | +| LPC3 | 8 | b26 - b33 | +| INT_LPC | 1 | b34 | +| MODE | 2 | b35 - b36 | +| | | | +| CODE1 1 | 7 | b37 - b43 | +| CODE2 1 | 7 | b44 - b50 | +| GSP0 1 | 5 | b51 - b55 | +| | | | +| CODE1 2 | 7 | b56 - b62 | +| CODE2 2 | 7 | b63 - b69 | +| GSP0 2 | 5 | b70 - b74 | +| | | | +| CODE1 3 | 7 | b75 - b81 | +| CODE2 3 | 7 | b82 - b88 | +| GSP0 3 | 5 | b89 - b93 | +| | | | +| CODE1 4 | 7 | b94 - b100 | +| CODE2 4 | 7 | b101 - b107 | +| GSP0 4 | 5 | b108 - b112 | + +**Table B.2: Occurrence of the codec parameters over Abis for voiced speech (MODE = 1, 2 or 3)** + +| Parameter | No. of bits | Bit No. (MSB - LSB) | +|-----------|-------------|---------------------| +| R0 | 5 | b1 - b5 | +| LPC1 | 11 | b6 - b16 | +| LPC2 | 9 | b17 - b25 | +| LPC3 | 8 | b26 - b33 | +| INT_LPC | 1 | b34 | +| MODE | 2 | b35 - b36 | +| | | | +| LAG 1 | 8 | b37 - b44 | +| CODE1 | 9 | b45 - b53 | +| GSP0 1 | 5 | b54 - b58 | +| | | | +| LAG 2 | 4 | b59 - b62 | +| CODE2 | 9 | b63 - b71 | +| GSP0 2 | 5 | b72 - b76 | +| | | | +| LAG 3 | 4 | b77 - b80 | +| CODE3 | 9 | b81 - b89 | +| GSP0 3 | 5 | b90 - b94 | +| | | | +| LAG 4 | 4 | b95 - b98 | +| CODE4 | 9 | b99 - b107 | +| GSP0 4 | 5 | b108 - b112 | + +# --- Annex C (informative): Bibliography + +M. R. Schroeder and B. S. Atal, "Code-Excited Linear Prediction (CELP): High Quality Speech at Very Low Bit Rates", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 937-940, March 1985. + +G. Davidson and A. Gersho, "Complexity Reduction Methods for Vector Excitation Coding", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 3055-3058, April 1986. + +I. Gerson and M. Jasiuk, "Vector Sum Excited Linear Prediction (VSELP) Speech Coding at 8 kbps", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 461-464, April 1990. + +P. Kroon and B. S. Atal, "Pitch Predictors with High Temporal Resolution", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 661-664, April 1990. + +I. A. Gerson, "Method and Means of Determining Coefficients for Linear Predictive Coding", U. S. Patent #4,544,919, Oct. 1985. + +A. Cumani, "On a Covariance-Lattice Algorithm for Linear Prediction", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 651-654, May 1982. + +M. McLaughlin, I. Gerson, F. Hudziak, and K. Kloker, "High Performance Processor for Real-Time Speech Applications", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 859-863, April 1980. + +Y. Tohkura, F. Itakura and S. Hashimoto, "Spectral Smoothing Technique in PARCOR Speech Analysis-Synthesis", **IEEE Trans. Acoustics, Speech and Signal Processing**, vol. ASSP-26, pp. 591-596, Dec. 1978. + +W. Kleijn, D. Krasinski, and R. Ketchum, "Improved Speech Quality and Efficient Vector Quantization in SELP", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 155-158, April 1988. + +Y. Linde, A. Buzo, and R. M. Gray, "An Algorithm for Vector Quantizer Design", **IEEE Trans. Comm.**, vol. COM-28, pp. 84-95, Jan. 1980. + +Juin-Hwey Chen and Allen Gersho, "Real-Time Vector APC Speech Coding at 4800 bps with Adaptive Postfiltering", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 2185-2188, 1987. + +# Annex D (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|----------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#13 | | | | 4.0.0 | ETSI Publication | +| SMG#20 | | | | 5.0.0 | Release 1996 version | +| SMG#22 | 430/97 | A001 | | 5.1.1 | UAP 60 comments | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| SMG#31 | | | | 8.0.0 | Release 1999 version | + +| Change history | | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46021/raw.md b/marked/Rel-18/46_series/46021/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e97d257be53a4ed0de5906fe55cf04d455d9896f --- /dev/null +++ b/marked/Rel-18/46_series/46021/raw.md @@ -0,0 +1,271 @@ + + +# 3GPP TS 46.021 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +### **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|---------------------------------------------------------------------------------------|----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 General..... | 6 | +| 5 Requirements ..... | 6 | +| 5.1 Error detection and concealment in case of unreliable speech or SID frames ..... | 6 | +| 5.1.1 Error detection ..... | 6 | +| 5.1.2 Output signal concealment ..... | 6 | +| 5.2 Frame substitution and muting in case of lost speech or SID frames ..... | 6 | +| 5.2.1 First and second lost speech frame..... | 6 | +| 5.2.2 Subsequent lost speech frames ..... | 7 | +| 5.2.3 First and second lost SID frame ..... | 7 | +| 5.2.4 Subsequent lost SID frames..... | 7 | +| 6 Example solutions ..... | 7 | +| 6.1 Example solution for error detection in case of unreliable frames ..... | 7 | +| 6.2 Example solution for output signal concealment in case of unreliable frames ..... | 7 | +| 6.3 Example solution for substitution and muting of lost speech frames ..... | 7 | +| 6.4 Example solution for substitution and muting of lost SID frames ..... | 8 | +| Annex A (informative): Change history..... | 9 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines a frame substitution and muting procedure which shall be used by the Receive (RX) Discontinuous Transmission (DTX) handler for the half rate speech traffic channels within the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below: + +- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".** +- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". +- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". + +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 a frame substitution and muting procedure which shall be used by the Receive (RX) Discontinuous Transmission (DTX) handler when one or more lost or unreliable speech or Silence Descriptor (SID) frames are received from the Radio Sub System (RSS). + +The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS)s and Mobile Stations (MS)s capable of supporting the half rate speech traffic channel. + +# --- 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] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [3] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- [4] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- [5] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +The definitions of terms used in the present document can be found in GSM 06.20 [3], GSM 06.41 [4], GSM 05.03 [2]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|-----------------------------------------| +| BFI | Bad Frame Indication | +| BSS | Base Station System | +| DTX | Discontinuous Transmission | +| GSM | Global System for Mobile communications | +| LPC | Linear Predictive Coding | +| MS | Mobile Station | +| RSS | Radio Sub System | +| RX | Receive | +| SID | Silence Descriptor | + +UFI                    Unreliable Frame Indication + +For abbreviations not given in this clause, see GSM 01.04 [1]. + +# --- 4 General + +The RSS indicates lost speech or SID frames by setting the Bad Frame Indication (BFI) flag and unreliably decoded speech or SID frames by setting the Unreliable Frame Indication (UFI) flag. + +If the BFI flag is set, the speech decoder performs frame substitution and muting of the speech output. The purpose of frame substitution is to conceal the effect of lost frames. The purpose of muting the speech output in case of several lost frames is to indicate the breakdown of the channel to the Mobile Station (MS) user in a way that avoids excessively unpleasant sounds. + +If the UFI flag is set, the speech decoder performs a plausibility analysis of the received frame parameters and of the output signal aiming at the detection and concealment of erroneous frames which are not marked with the BFI flag. + +# --- 5 Requirements + +## 5.1 Error detection and concealment in case of unreliable speech or SID frames + +A cleared BFI flag (BFI="0") and a set UFI flag (UFI="1") indicate a probably erroneous speech or SID frame. To improve the subjective quality, the probability of decoding erroneous frames shall be decreased by additional error detection which is based on both the exploitation of the frame parameters' properties and the decoder output signal's properties. + +### 5.1.1 Error detection + +By investigating the frame parameter properties, it shall be decided whether the frame is to be considered as usable or unusable. In the latter case, the BFI flag is set and substitution and muting is performed (clause 5.2). Clause 6.1 gives an example solution for error detection in case of unreliable frames. + +### 5.1.2 Output signal concealment + +If the frame is considered as usable, properties of the decoder output signal shall be compared to the corresponding signal properties of the previous valid frames. In case of large differences, the output signal shall be modified such that these differences are limited. Clause 6.2 gives an example solution for output signal concealment in case of unreliable frames. + +## 5.2 Frame substitution and muting in case of lost speech or SID frames + +A set BFI flag (BFI="1") indicates a lost speech or SID frame. Normal decoding of these frames would result in a degradation of the subjective quality of the speech. To improve the subjective quality of the speech, the frame parameters shall be appropriately modified prior to the execution of the speech decoder functions. + +### 5.2.1 First and second lost speech frame + +The first and second lost speech frame shall be partly or completely substituted with the last valid speech frame. For the first and second lost speech frame, the output shall not be muted directly. + +### 5.2.2 Subsequent lost speech frames + +For subsequent lost speech frames, a muting technique shall be used that will gradually decrease the output level, resulting in silencing of the output after a maximum of 80 ms. For subsequent lost speech frames, the muting of the output shall be maintained. Clause 6.3 gives an example of such a method. + +### 5.2.3 First and second lost SID frame + +The first and second lost SID frame shall be substituted with the last good SID frame. For the first and second lost SID frame, the output shall not be muted directly. + +### 5.2.4 Subsequent lost SID frames + +For subsequent lost SID frames, a muting technique shall be used that will gradually decrease the output level, resulting in silencing of the output after a maximum of 320 ms. For subsequent lost SID frames, the muting of the output shall be maintained. Clause 6.4 gives an example of such a method. + +# --- 6 Example solutions + +The C code of the following example solutions are given in GSM 06.06 [5]. + +## 6.1 Example solution for error detection in case of unreliable frames + +With the parameter R0, the average signal energy is transmitted. Except at the beginning or the end of a talk spurt, this parameter shows a smooth behaviour from frame to frame. For error detection purposes, the difference of the R0-value between the actual and the last good frame is computed. If this difference exceeds a level dependent threshold and the frame is marked as unreliable, it is declared unusable by setting the BFI flag equal to "1". + +## 6.2 Example solution for output signal concealment in case of unreliable frames + +In the speech decoder, the output signal is created by processing an excitation sequence through an LPC synthesis filter. The output signal energy of each subframe is calculated and compared to the output signal energy of the previous subframes. If the difference exceeds a level dependent threshold, the excitation sequence is attenuated such that the output signal energy corresponds to the output signal energy of the previous subframes. + +## 6.3 Example solution for substitution and muting of lost speech frames + +For the half rate speech decoder, a possible substitution and muting strategy is based on an 8-state machine. + +The state, with the exception of states 6 and 7, indicates how many consecutive frames were lost. For example, state 5 indicates that 5 consecutive frames (including the current frame) were lost. State 7 is the initial state of the system, so that if the first decoded frame is lost, the frame is muted. Usually, the system will operate in state 0. The state machine remains in this state unless a frame is lost. On each successive lost speech frame, the state machine moves to the next higher numbered state. As soon as a frame is not declared lost, the machine returns to state 0 (unless it is in state 6). The machine remains in state 6 in the case of additional lost speech frames. If the machine is in state 6, a single frame without detected errors moves the machine to state 7 (i.e., two successive frames with no detected errors are needed to return to state 0 from state 6). This provides additional protection during prolonged intervals of very poor channel conditions which might cause false indications of valid speech data. If the machine is in state 7 and a lost speech frame is received, the machine returns to state 6. + +In each state, the following occurs: + +- State 0: No error is detected. The received decoded speech data is output. The current frame parameters are stored. +- State 1: An error has been detected in the frame. If the last speech frame in state 0 is in the unvoiced mode, then the parameters R0, INT\_LPC and the LPC coefficients in the current frame are replaced with the corresponding values from the last good frame. All GSP0 parameters are replaced with the GSP0\_4 parameter from the last good frame. If the MODE bits for the current frame indicate unvoiced, the current frame of codevectors is used. If not, the codevectors from the last good frame are used. The frame's remaining decoded bits are passed to the speech decoder without modification. +- Alternatively, if the last speech frame in state 0 was in the voiced mode, the long term predictor lag from the last good frame is used for all subframes in the current frame. The parameters MODE, R0, INT\_LPC and the LPC coefficients are replaced with those from the last good frame. All GSP0 parameters are replaced with the GSP0\_4 parameter from the last good frame. If the MODE bits for the current frame indicate voiced (MODE = 1, 2 or 3), the current frame of codevectors is used. If not, the codevectors from the last good frame are used. The frame's remaining decoded bits are passed to the speech decoder without modification. +- State 2: Same action as in state 1. +- State 3: As in state 1 and 2, a frame repetition is performed, but the frame energy R0 (coded on the interval from 0 to 31) is decreased by a value of 2. +- State 4: Same action as in state 3. +- State 5: Same action as in state 3. +- State 6: Again a frame repetition is performed. The output speech signal is muted by setting R0 to zero. +- State 7: The speech signal remains muted, R0 remains zero. + +## 6.4 Example solution for substitution and muting of lost SID frames + +The first and second lost SID frame is replaced by the last good SID frame. + +For subsequent lost SID frames the last good SID frame is repeated, but the frame energy R0 (coded on the interval from 0 to 31) is decreased with a constant value of 2 in each frame down to R0 = 0. This value is maintained if additional lost SID frames occur. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|-----------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments | +| SMG#15 | | | | 4.0.2 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46022/raw.md b/marked/Rel-18/46_series/46022/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a625c667b3e9ec3a1051418bdbe7417fae4dd92c --- /dev/null +++ b/marked/Rel-18/46_series/46022/raw.md @@ -0,0 +1,425 @@ + + +# 3GPP TS 46.022 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Half rate speech; Comfort noise aspects for the half rate speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 General..... | 6 | +| 5 Functions on the transmit (TX) side ..... | 7 | +| 5.1 Background acoustic noise evaluation ..... | 7 | +| 5.2 Modification of the speech encoding algorithm during SID frame generation..... | 8 | +| 5.3 SID-frame encoding ..... | 9 | +| 6 Functions on the receive (RX) side..... | 10 | +| 6.1 Averaging of the GS parameters ..... | 10 | +| 6.2 Comfort noise generation and updating ..... | 11 | +| 7 Computational details ..... | 11 | +| Annex A (informative): Change Request History ..... | 12 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation within the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below: + +- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". +- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".** +- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". + +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 gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX) on half rate speech traffic channels. + +The requirements described in the present document are mandatory for implementation in all GSM MSs capable of supporting the half rate speech traffic channel. + +The receiver requirements are mandatory for implementation in all GSM BSSs capable of supporting the half rate speech traffic channel, the transmitter requirements are only for those where downlink DTX will be used. + +# --- 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] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech transcoding". +- [3] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- [4] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); "Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". +- [5] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**frame:** time interval of 20 ms corresponding to the time segmentation of the half rate speech transcoder, also used as a short term for a traffic frame. + +**H(Z):** combination of the short term (spectral) filter $A(z)$ and the spectral weighting filter $W(z)$ . + +**SID codeword:** fixed bit pattern for labelling a traffic frame as a SID frame. + +**SID field:** bit positions of the SID codeword within a SID frame. + +**SID frame:** frame characterized by the SID (Silence Descriptor) codeword. It conveys information on the acoustic background noise. + +**SP flag:** speech flag. + +**speech frame:** traffic frame that cannot be classified as a SID frame. + +**VAD flag:** Voice Activity Detector flag. + +**W(Z):** spectral weighting filter of the GSM half rate speech codec. + +Other definitions of terms used in the present document can be found in GSM 06.20 [2] and GSM 06.41 [3]. The overall operation of DTX is described in GSM 06.41 [3]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------|--------------------------------------------------------------------------------------------------------------| +| GS | Energy tweak parameter. | +| R0 | Frame energy value. | +| R(i) | Unquantised (normalized) autocorrelation sequence. | +| $r_j$ | Optimal reflection coefficient. | +| b | | +| SUM ( $x(n)$ ) | = $x(a) + x(a+1) + \dots + x(b-1) + x(b)$ ; (Accumulation). | +| n=a | | +| GSP0 codeword | Vector quantization index, joint vector quantization of the parameters GS and P0. | +| P0 | Power contribution of the first excitation vector as a fraction of the total excitation power at a subframe. | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------| +| AFLAT | Autocorrelation Fixed Point LAttice Technique (used in the GSM half rate speech codec for the vector quantization of the LPC coefficients) | +| BSS | Base Station System | +| DTX | Discontinuous Transmission | +| ETS | European Telecommunication Standard | +| GSM | Global System for Mobile communications | +| MS | Mobile Station | +| SID | SIlence Descriptor | +| RX | Receive | +| TX | Transmit | +| VAD | Voice Activity Detector | +| VQ | Vector Quantization | + +For abbreviations not given in this subclause, see GSM 01.04 [1]. + +# --- 4 General + +A problem when using DTX is that the background acoustic noise, which is transmitted together with the speech, would disappear when the radio transmission is switched off, resulting in a modulation of the background noise. Since the DTX switching can take place rapidly, it has been found that this effect may be annoying for the listener, especially in a car environment with high background noise levels. In bad cases, the speech may be hardly intelligible. + +The present document specifies a solution to overcome this problem by generating synthetic noise similar to the transmit (TX) side background noise on the receive (RX) side. The comfort noise parameters are estimated on the TX side and transmitted to the RX side before the radio transmission is switched off and at a regular low rate afterwards. This allows the comfort noise to adapt to the changes of the noise on the TX side. + +# 5 Functions on the transmit (TX) side + +The comfort noise evaluation algorithm uses the following parameters of the GSM half rate speech encoder, defined in GSM 06.20 [2]: + +- the unquantized frame energy value $R_0$ ; +- the unquantized (normalized) autocorrelation sequence $R(i)$ derived from the optimal reflection coefficients $r_j$ ; +- the quantized energy tweak parameter GS. + +These parameters give information on the level ( $R_0$ and GS) and the spectrum ( $R(i)$ ) of the background noise. + +Two of the evaluated comfort noise parameters ( $R_0$ and $R(i)$ ) are encoded into a special frame, called a SIlence Descriptor (SID) frame, for transmission to the RX side. While the energy tweak parameter GS can be evaluated in the encoder and decoder in the same way as given in subclause 5.1, therefore no transmission of GS is necessary. + +The SID frame also serves to initiate the comfort noise generation on the RX side, as a SID frame is always sent at the end of a speech burst, i.e. before the radio transmission is terminated. + +The scheduling of SID or speech frames on the radio path is described in GSM 06.41 [3]. + +## 5.1 Background acoustic noise evaluation + +The comfort noise parameters to be encoded into a SID frame are calculated over 8 consecutive frames marked with Voice Activated Detector (VAD) flag = "0", as follows: + +The frame energy values shall be averaged according to the equation: + +$$\text{mean}(R_0[j]) = 1/8 \sum_{n=0}^7 R_0[j-n];$$ + +where: + +- $R_0[j]$ is the frame energy value of the current frame $j$ ( $n=0$ ); +- $R_0[j-n]$ is the frame energy of the previous frames ( $n=1, \dots, 7$ ); +- $n$ is the averaging period index $n=0, 1, \dots, 7$ ; +- $j$ is the frame index. + +The averaged value $\text{mean}(R_0[j])$ is encoded using the same encoding table that is also used by the GSM half rate speech codec for the encoding of the non-averaged $R_0$ values in ordinary speech encoding mode. + +The (normalized) autocorrelation sequence $R(i)$ shall be averaged according to the equation: + +$$\text{mean}(R[j](i)) = 1/8 \sum_{n=0}^7 R[j-n](i) \quad i = 0, 1, 2, \dots, 10;$$ + +where: + +- $R[j](i)$ is the $i$ 'th autocorrelation value of the current frame $j$ ( $n=0$ ); +- $R[j-n](i)$ is the $i$ 'th autocorrelation value of one of the previous frames ( $n=1, \dots, 7$ ); +- $n$ is the averaging period index $n=0, 1, \dots, 7$ ; +- $j$ is the frame index. + +The averaged values $\text{mean}(R[j](i))$ are used as input parameters of the Autocorrelation Fixed Point LAttice Technique (AFLAT) recursion algorithm which calculates the Vector Quantization (VQ) indices of the reflection coefficients, see GSM 06.20 [2]. + +The SID frame containing the quantization index of $\text{mean}(R0[j])$ , the VQ indices of $\text{mean}(R[j](i))$ and the SID codeword is passed to the radio subsystem instead of frame number $j$ (see subclause 5.3, SID-frame encoding). + +The averaging of the energy tweak parameters GS is made on the basis of the quantized GS parameters. The quantized GS parameters can be derived from the GSP0 indices. These indices are used as pointers to the GSP0 vector quantization codebook. The GS components of the selected GSP0 vectors are the quantized GS values which will be averaged. + +The quantized energy tweak parameters GS shall be averaged according to the equation: + +$$\text{mean}(GS[j]) = 1/28 \sum_{n=1}^7 \sum_{i=1}^4 GS[j-n](i)$$ + +where: + +$GS[j](i)$ is the quantized energy tweak parameter in subframe $i$ of the current frame $j$ ( $n=0$ ); + +$GS[j-n](i)$ is the quantized energy tweak parameter in subframe $i$ of one of the last frames ( $n=1, \dots, 7$ ); + +$n$ is the averaging period index $n=1, 2, \dots, 7$ ; + +$i$ is the subframe index $i=1, 2, 3, 4$ ; + +$j$ is the frame index. + +NOTE: The averaging of GS is made over 7 frames only. + +For each comfort noise insertion period, the averaging of the GS parameters is done only once before sending the first SID frame to the decoder and for the rest of the comfort noise insertion period, the averaged value $\text{mean}(GS[j])$ will be frozen. + +Under normal conditions, the averaging of the GS parameters is done during the hangover period, but in case of short speech bursts handling, the hangover period can be skipped under certain conditions, see GSM 06.41 [3]. In such cases, the GS parameters of the last seven speech frames marked with SP flag="1" are averaged. + +The hangover period is defined in GSM 06.41 [3]. It is a period added at the end of a speech burst in which no voice activity is detected (VAD flag="0"), but the speech encoder stays for the processing of 7 speech frames in speech encoding mode (SP flag="1"). This hangover period and the first SID frame are used for averaging the comfort noise parameters contained in the first SID frame. + +$\text{mean}(GS[j])$ can be evaluated at the decoder in the same way as in the encoder, because in both the encoder and decoder, the GSP0 indexes of the last 7 speech frames shall be kept in memory. In case of an error free transmission, the GSP0 indexes are identical at the encoder and decoder. + +## 5.2 Modification of the speech encoding algorithm during SID frame generation + +When the SP flag is equal to "0", the speech encoding algorithm is modified in the following way: + +- the non-averaged reflection coefficients which are used to derive the filter coefficients of the filters $H(z)$ and $W(z)$ of the speech encoder are not quantized; +- the unvoiced speech encoding mode is forced. This simplifies the open loop long term prediction processing: only the integer lags have to be calculated, no determination of fractional lags is necessary and the frame lag trajectory derivation can be avoided; + +- no fixed codebook search is made. In each subframe, the indices of both fixed codebooks (CODE1\_1, ..., CODE1\_4 and CODE2\_1, ..., CODE2\_4) are replaced by pseudo random numbers uniformly distributed in [0,127] (7 bit random numbers); +- no GSP0 determination is made. The GSP0 codeword is selected as follows: + - at the beginning of a comfort noise insertion period, $\text{mean}(\text{GS}[j])$ is calculated as defined in subclause 5.1. Then $\text{mean}(\text{GS}[j])$ is quantized, using only the GS component of the GSP0 vector quantization codebook of the unvoiced speech encoding mode as quantization table. The P0 parameter is not averaged. For this parameter, the value is used which is associated with the quantized $\text{mean}(\text{GS}[j])$ value in the GSP0 codebook of the unvoiced speech encoding mode. For the rest of the comfort noise insertion period, the GSP0 indices are frozen. + +A simplified block diagram of the GSM half rate speech encoder in comfort noise insertion mode is shown in figure 1. + +![Figure 1: GSM half rate speech encoder in comfort noise insertion mode. The diagram shows the signal flow from input s(n) through various processing blocks including W(z), VSELP Codebook 1 and 2, and H(z) to produce the error signal e(n).](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +The diagram illustrates the GSM half rate speech encoder in comfort noise insertion mode. The input signal $s(n)$ is processed by a block $W(z)$ containing coefficients $(\alpha_i, \tilde{\alpha}_i)$ . The output of $W(z)$ is subtracted from the sum of two VSELP codebook outputs to produce the error signal $e(n)$ . The VSELP codebook outputs are generated by pseudo-noise (PN) generators (I and H) feeding into VSELP Codebook 1 and 2 respectively. These outputs are then multiplied by factors $\beta$ and $\gamma$ before being summed. The summed signal is also fed back to a Long Term Filter State Update block, which in turn feeds back into the VSELP codebooks. The filter $H(z)$ contains coefficients $(\tilde{\alpha}_i)$ . + +Mode = 0 (unvoiced); + $\alpha_i$ : direct form LPC coeff. / unquantized; + $\tilde{\alpha}_i$ : weighted direct form LPC coeff. / unquantized; + PN : pseudo noise generator. + +Figure 1: GSM half rate speech encoder in comfort noise insertion mode. The diagram shows the signal flow from input s(n) through various processing blocks including W(z), VSELP Codebook 1 and 2, and H(z) to produce the error signal e(n). + +Figure 1: GSM half rate speech encoder in comfort noise insertion mode + +## 5.3 SID-frame encoding + +The SID frame encoding algorithm exploits the fact that only some of the 112 bits in a frame are needed to code the comfort noise parameters. The other bits can then be used to mark the SID frame by means of a fixed bit pattern, called the SID codeword. + +SID frames are encoded in the encoder output format for voiced frames (MODE = 3), because the two voicing mode bits are part of the SID codeword. + +The index of the frame energy value $R_0$ is replaced by the quantization index derived from $\text{mean}(R_0[j])$ . $\text{mean}(R_0[j])$ is defined in subclause 5.1 and is encoded as described in GSM 06.20 [2]. + +The VQ indices of the reflection coefficients are replaced by VQ indices derived from $\text{mean}(R[j](i))$ . $\text{mean}(R[j](i))$ is defined in subclause 5.1 and the VQ of the reflection coefficients is described in GSM 06.20 [2]. + +The SID codeword consists of 79 bits which are all "1". To mark a frame as a SID frame, the parameters in table 1 have to be set as shown. + +Table 1: SID codeword + +| Parameter | Number of bits | Value (Hex) | +|-----------|----------------|-------------| +| MODE | 2 | 0x0003 | +| INT LPC | 1 | 0x0001 | +| LAG 1 | 8 | 0x00ff | +| LAG 2 | 4 | 0x000f | +| LAG 3 | 4 | 0x000f | +| LAG 4 | 4 | 0x000f | +| CODE 1 | 9 | 0x01ff | +| CODE 2 | 9 | 0x01ff | +| CODE 3 | 9 | 0x01ff | +| CODE 4 | 9 | 0x01ff | +| GSP0 1 | 5 | 0x001f | +| GSP0 2 | 5 | 0x001f | +| GSP0 3 | 5 | 0x001f | +| GSP0 4 | 5 | 0x001f | + +The parameters in table 1 are defined in GSM 06.20 [2]. + +# 6 Functions on the receive (RX) side + +The situations in which comfort noise shall be generated on the RX side are defined in GSM 06.41 [3] and may be started or updated whenever a valid SID frame is received. + +## 6.1 Averaging of the GS parameters + +When speech frames are received by the decoder, the GS parameters of the last seven speech frames shall be kept in memory. As soon as a SID frame is received, these stored GS parameters shall be averaged. The averaged GS value will be frozen and used for the actual comfort noise insertion period. + +The averaging procedure works as follows: + +- when a speech frame is received, the GSP0 indices are decoded and the decoded GS parts of these parameters are stored in memory; +- when the first SID frame is received, the stored GS values are averaged in the same way as in the speech encoder as follows (see also subclause 5.1): + +$$\text{mean (GS[j])} = 1/28 \sum_{n=1}^7 \sum_{i=1}^4 \text{GS}[j-n](i);$$ + +where: + +GS[j](i) is the quantized energy tweak parameter in subframe i of the current frame j; + +GS[j-n](i) is the quantized energy tweak parameter in subframe i of one of the last frames; + +n is the averaging period index n=1,2,...,7; + +i is the subframe index i=1,2,3,4; + +j is the frame index; + +- then $\text{mean}(\text{GS}[j])$ is quantized, using the GS component of the GSP0 vector quantization codebook for the unvoiced speech encoding mode as quantization table. The resulting index of this quantization is used for one complete comfort noise insertion period as GSP0 codeword. The P0 parameter is not averaged. For this parameter, the value is used which is associated with the quantized $\text{mean}(\text{GS}[j])$ value in the GSP0 codebook of the unvoiced speech encoding mode. + +## 6.2 Comfort noise generation and updating + +The comfort noise generation procedure uses the GSM half rate speech decoder algorithm defined in GSM 06.20 [2]. + +When comfort noise is to be generated, then the various encoded parameters are set as in table 2. + +**Table 2: Comfort noise encoded parameters** + +| Parameter | Value | +|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| MODE | 0 | +| R0 | interpolation of the values received in the last two valid SID frames | +| LPC1
LPC2
LPC3 | interpolation of the values received in the last two valid SID frames | +| INT LPC | 1 | +| CODE1_1
CODE1_2
CODE1_3
CODE1_4
CODE2_1
CODE2_2
CODE2_3
CODE2_4 | pseudo random numbers uniformly distributed in [0,127] (7 bit numbers) | +| GSP0_1
GSP0_2
GSP0_3
GSP0_4 | index of the averaged GS parameter (calculated at the beginning of each comfort noise insertion period and frozen for the rest of the period) | + +With these parameters, the speech decoder now performs the standard operations described in GSM 06.20 [2] and thereby synthesizes comfort noise. + +Updating of the comfort noise parameters (frame energy and LPC coefficients) occurs each time a valid SID frame is received, as described in GSM 06.41 [3]. + +NOTE: The GSP0 codewords are not updated, they are frozen during each comfort noise insertion period. + +When updating the comfort noise parameters (frame energy and LPC coefficients), these parameters shall be interpolated over the SID update period to obtain smooth transitions. + +# --- 7 Computational details + +A low level description has been prepared in form of an ANSI C source code which is part of GSM 06.06 [5]. + +# Annex A (informative): Change Request History + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#15 | | | | 4.1.1 | ETSI Publication | +| SMG#20 | | | | 5.1.0 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | + +| Change history | | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46031/raw.md b/marked/Rel-18/46_series/46031/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..82a9a10defd9657788ddefda2a2880b0ba5ce653 --- /dev/null +++ b/marked/Rel-18/46_series/46031/raw.md @@ -0,0 +1,358 @@ + + +# 3GPP TS 46.031 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +### **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|----------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definition of general terms ..... | 6 | +| 3.2 Definition of terms on the receive side ..... | 6 | +| 4 General ..... | 6 | +| 4.1 General organization ..... | 7 | +| 4.2 Naming convention ..... | 7 | +| 5 Transmit side..... | 7 | +| 5.1 General operation ..... | 7 | +| 5.1.1 Functions of the TX DTX handler..... | 8 | +| 5.1.2 Functions of the TX radio subsystem..... | 9 | +| 6 Receive side ..... | 9 | +| 6.1 General operation ..... | 10 | +| 6.1.1 Functions of the RX Radio Subsystem..... | 10 | +| 6.1.2 Functions of the RX DTX handler ..... | 11 | +| Annex A (informative): Change history ..... | 12 | + +# --- 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 gives a description of the general baseband operation of full rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX). + +For clarity, the description is structured according the block diagrams in figures 1 and 4. Except in the case described next, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same. + +In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX Handlers and the Radio Subsystem (RSS) as described in the present document together with all their flags is mandatory, being a part of the A-bis- interface as described in GSM 08.60. In this case the various flags also serve to avoid additional delays. + +The DTX functions described in the present document are mandatory for implementation in all GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used. + +DTX shall be in operation in GSM MSs if commanded so by the network, see GSM 04.08. + +# 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". +- [3] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [4] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". +- [5] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". +- [6] GSM 06.01: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Processing functions". +- [7] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding". +- [8] GSM 06.11: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Substitution and muting of lost frames for full rate speech channels". +- [9] GSM 06.12: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Comfort noise aspect for full rate speech traffic channels". + +- [10] GSM 06.32: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD)". +- [11] GSM 08.60: "Digital cellular telecommunications system (Phase 2+); Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels". + +# --- 3 Definitions and abbreviations + +Abbreviations used in the present document are listed in GSM 01.04. + +## 3.1 Definition of general terms + +**frame:** time interval of 20 msec. corresponding to the time segmentation of the full rate speech transcoder (GSM 06.10), also used as a short term for a traffic frame. + +**traffic frame:** block of 260 information bits (see GSM 05.03) transmitted on the full rate speech traffic channel. + +**(SID) silence descriptor frame:** frame characterized by the SID code word. It conveys information on the acoustic background noise. + +**SID code word:** fixed bit pattern defined in GSM 06.12, for labelling a traffic frame as a SID frame. + +**SID field:** bit positions defined in GSM 06.12, of the SID codeword within a SID frame. + +**speech frame:** traffic frame that cannot be classified as a SID frame. + +## 3.2 Definition of terms on the receive side + +**bad traffic frame:** traffic frame flagged BFI=1 (Bad Frame Indication) by the Radio Subsystem. + +**good traffic frame:** traffic frame flagged BFI=0 by the Radio Subsystem. + +**good speech frame:** good traffic frame which is not an accepted SID frame. + +**accepted SID frame:** traffic frame in which the SID field deviates in less than 16 bit positions from the SID code word (flag SID=2 or SID=1). + +**valid SID frame:** good traffic frame in which the SID field deviates in less than 2 bit positions from the SID code word (flag SID=2). This frame is valid for updating of comfort noise parameters at any time. + +**invalid SID frame:** accepted SID frame with BFI=1, or accepted SID frame with BFI=0, in which the SID field deviates in more than 1 bit position from the SID code word (flag SID=1). This frame is not valid for updating comfort noise parameters, but the frame conveys information that comfort noise generations should be started or continued. + +**unusable frame:** bad traffic frame that is not an accepted SID frame. + +**lost SID frame:** unusable frame received when the RX DTX Handler is generating comfort noise and a SID frame is expected (Time Alignment Flag, TAF=1). + +**lost speech frame:** unusable frame received when the RX DTX Handler is passing on traffic frames directly to the speech decoder. + +# --- 4 General + +Discontinuous Transmission is a mechanism which allows the radio transmitter to be switched off most of the time during speech pauses for the following two purposes: + +- to save power in the MS; +- to reduce the overall interference level on the air. + +## 4.1 General organization + +The overall DTX mechanism described in the present document requires the following functions: + +- a Voice Activity Detector on the transmit side; +- evaluation of the background acoustic noise on the transmit side, in order to transmit characteristic parameters to the receive side; +- generation on the receive side of a similar noise, called comfort noise, during periods where the radio transmission is cut. + +The Voice Activity Detector is defined in GSM 06.32 "Voice Activity Detector", the comfort noise functions in GSM 06.12 "Comfort Noise Aspects". Both are based partly on the speech transcoder and its internal variables, defined in GSM 06.10 "GSM Full Rate Speech Transcoding". + +In addition to these functions, if the parameters arriving at the receive side are detected to be seriously corrupted by errors, the speech or comfort noise must be generated from substituted data in order to avoid seriously annoying effects for the listener. This function is defined in GSM 06.11 "Substitution and Muting of Lost Frames". + +An overall description of the speech processing parts can be found in GSM 06.01 "Processing functions". + +## 4.2 Naming convention + +Clause 3 lists the definitions of terms relevant for the DTX functions, as used in this and the technical specifications mentioned above. + +# 5 Transmit side + +A block diagram of the transmit side DTX functions is shown in figure 1. + +![Block diagram of the transmit side DTX functions showing the TX DTX handler and TX radio subsystem.](34f788b0e5bc8af774fa5561c22e6d01_img.jpg) + +The diagram illustrates the transmit side DTX functions. It consists of two main blocks: the TX DTX handler and the TX radio subsystem. The TX DTX handler contains three sub-blocks: Speech encoder, Voice Activity Detection, and Comfort Noise Computation. The TX radio subsystem contains two sub-blocks: Channel encoding and SP flag monitoring. Arrows indicate the flow of data: Information bits (260) from the Speech encoder to the Channel encoding, and an SP flag (1) from the Voice Activity Detection to the SP flag monitoring. + +``` +graph LR; subgraph TX_DTX_handler [TX DTX handler]; SE[Speech encoder]; VAD[Voice Activity Detection]; CNC[Comfort Noise Computation]; end; subgraph TX_radio_subsystem [TX radio subsystem]; CE[Channel encoding]; SFM[SP flag monitoring]; end; SE -- "Information bits 260" --> CE; VAD -- "SP flag 1" --> SFM; +``` + +Block diagram of the transmit side DTX functions showing the TX DTX handler and TX radio subsystem. + +Figure 1: Block diagram of the transmit side DTX functions + +## 5.1 General operation + +The TX DTX Handler continuously passes traffic frames, individually marked by a flag SP, to the Radio Subsystem. This binary flag is redundant to the SID code word labelling. SP=1 indicates a speech frame, SP=0 a SID frame. + +The scheduling of the frames for transmission on the air interface is controlled by the radio subsystem alone, on the basis of the SP flag as described next. + +### 5.1.1 Functions of the TX DTX handler + +To allow an exact verification of the TX DTX handler functions, all frames before the reset of the system have to be treated as if there would have been speech frames for an infinitely long time. Therefore, the first N frames after the reset are always marked with SP=1, even if VAD=0 (hangover period, see below). + +The Voice Activity Detector must be operating all the time in order to assess whether the input signal contains speech or not. The output is a binary flag (VAD=1 or VAD=0, respectively) on a frame by frame basis (see GSM 06.32). + +The VAD flag controls indirectly, via the TX DTX Handler operations described below, the overall DTX operation on the transmit side. + +Whenever VAD=1, the speech encoder output frame shall be passed directly to the radio subsystem, marked with SP=1. + +At the end of a speech burst (transition VAD=1 to VAD=0), it takes N+1 consecutive frames to make a new updated SID frame available (see GSM 06.12). Normally, the first N speech encoder output frames after the end of the speech burst shall therefore be passed directly to the radio subsystem, marked with SP=1 ("hangover period"). The first new SID frame is then passed to the RSS as frame N+1 after the end of the speech burst, marked with SP=0 (see figure 2). + +![Timing diagram showing VAD, SP, and frame transmission over time. It illustrates the hangover period where SP=1 for N frames after VAD becomes 0, followed by SID frames. A table at the bottom shows the sequence of frames sent to the RSS: SPEECH, ..., SPEECH, SID k+1, SID k+2.](2396add2849eccefcbcfbe1c7142a253_img.jpg) + +The figure illustrates the "Normal" hangover procedure. The top section shows three horizontal timelines: + + +- VAD:** Shows a transition from high (speech) to low (pause) at the "end of speech burst". The "last 'speech' frame" is just before this transition, and the "first 'pause' frame" is just after. +- SP:** Shows a high state starting at the end of the speech burst and lasting for a duration labeled "hangover". +- Nelapsed:** Shows frame numbers (e.g., 49, 50, 51, 52, 53, 54) during the hangover, followed by 0, 0. + + Below this, a table shows the sequence of frames sent to the RSS: + + +| | | | | | | | | | +|---------------|--------|-------|-------|-------|-------|--------|---------|---------| +| Frames to RSS | SPEECH | ..... | ..... | ..... | ..... | SPEECH | SID k+1 | SID k+2 | +|---------------|--------|-------|-------|-------|-------|--------|---------|---------| + + Arrows indicate the mapping from the timelines above to the frames in the table. A bracket labeled "SID averaging periods" spans from the start of the hangover to the transmission of SID k+2. + + (Nelapsed : No. of elapsed frames since last updates SID) + +Timing diagram showing VAD, SP, and frame transmission over time. It illustrates the hangover period where SP=1 for N frames after VAD becomes 0, followed by SID frames. A table at the bottom shows the sequence of frames sent to the RSS: SPEECH, ..., SPEECH, SID k+1, SID k+2. + +**Figure 2: "Normal" hangover procedure (Nelapsed >23)** + +If, however, at the end of the speech burst, less than 24 frames have elapsed since the last SID frame was computed and passed to the RSS, then this last SID frame shall repeatedly be passed to the RSS, until a new updated SID frame is available (N+1 consecutive frames marked with VAD=0). This reduces the activity on the air in cases where short background noise spikes are taken for speech, by avoiding the "hangover" waiting for the SID frame computation (see also figure 3: Note that figure 3 shows as example the longest possible speech burst without hangover). + +![Figure 3: Handling of short speech bursts (N_elapsed < 24) (Example). The diagram shows four horizontal timelines: VAD, SP, N_elapsed, and Frames to RSS. VAD and SP show speech bursts. Arrows labeled 'end of speech burst' point to the end of the first burst in both. N_elapsed shows frame counts since last SID update, with values: ?, ?, ?, 0, 1, 2, 3, 4, 5, 6, 7, 8, ..., 22, 23, 24, 25, 26, 0. Frames to RSS shows the sequence of frames: ?, ?, ?, SID k, Speech, SID k, SID k, SID k, SID k, Speech, SID k, SID k, SID k, SID k, SID k+1. Brackets indicate 'SID averaging period' for the first and last groups of SID frames. Brackets below the frames indicate 'repeat previous SID' for the two groups of SID frames. A 'Frame (20ms)' is indicated on the VAD timeline. A note at the bottom states: (N_elapsed : No. of elapsed frames since last updates SID).](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +(Nelapsed : No. of elapsed frames since last updates SID) + +Figure 3: Handling of short speech bursts (N\_elapsed < 24) (Example). The diagram shows four horizontal timelines: VAD, SP, N\_elapsed, and Frames to RSS. VAD and SP show speech bursts. Arrows labeled 'end of speech burst' point to the end of the first burst in both. N\_elapsed shows frame counts since last SID update, with values: ?, ?, ?, 0, 1, 2, 3, 4, 5, 6, 7, 8, ..., 22, 23, 24, 25, 26, 0. Frames to RSS shows the sequence of frames: ?, ?, ?, SID k, Speech, SID k, SID k, SID k, SID k, Speech, SID k, SID k, SID k, SID k, SID k+1. Brackets indicate 'SID averaging period' for the first and last groups of SID frames. Brackets below the frames indicate 'repeat previous SID' for the two groups of SID frames. A 'Frame (20ms)' is indicated on the VAD timeline. A note at the bottom states: (N\_elapsed : No. of elapsed frames since last updates SID). + +**Figure 3: Handling of short speech bursts (Nelapsed < 24) (Example)** + +Once the first SID frame after the end of a speech burst has been computed and passed to the Radio Subsystem, the TX DTX Handler shall continuously compute and pass updated SID frames to the Radio Subsystem, marked with SP=0 as long as VAD remains VAD=0. + +Consequently, the speech encoder must be operating all the time. + +### 5.1.2 Functions of the TX radio subsystem + +The following traffic frames shall be scheduled for transmission: + +- 1) all frames marked with SP=1; +- 2) the first one with SP = 0 after one or more frames with SP=1; +- 3) those marked with SP=0 and aligned with the SACCH multiframe structure as described in GSM 05.08. + +This has the overall function, that the radio transmission is cut after the transmission of a SID frame when the speaker stops talking. During speech pauses the transmission is resumed at regular intervals for transmission of one SID frame, in order to update the generated comfort noise on the receive side (and to improve the measurement of the link quality by the radio subsystem). + +If a SID frame (SP=0), scheduled for transmission is stolen for signalling (FACCH) purposes, then the subsequent frame shall be scheduled for transmission instead. + +# 6 Receive side + +A block diagram of the receive side DTX functions is shown in figure 4. + +![Block diagram of the receive side DTX functions. The diagram shows two main components: RX DTX handler and RX radio subsystem. The RX radio subsystem contains 'Error correction & detection' and 'SID frame detection' blocks. The RX DTX handler contains 'Comfort Noise Computation' and 'Speech decoder' blocks. Arrows indicate data flow: 'Information bits 260' from Error correction & detection to Comfort Noise Computation; 'BFI 1' from Error correction & detection to Comfort Noise Computation; 'SID 1' from SID frame detection to Speech decoder; and 'TAF 1' from SID frame detection to Speech decoder.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Block diagram of the receive side DTX functions. The diagram shows two main components: RX DTX handler and RX radio subsystem. The RX radio subsystem contains 'Error correction & detection' and 'SID frame detection' blocks. The RX DTX handler contains 'Comfort Noise Computation' and 'Speech decoder' blocks. Arrows indicate data flow: 'Information bits 260' from Error correction & detection to Comfort Noise Computation; 'BFI 1' from Error correction & detection to Comfort Noise Computation; 'SID 1' from SID frame detection to Speech decoder; and 'TAF 1' from SID frame detection to Speech decoder. + +Figure 4: Block diagram of the receive side DTX functions + +## 6.1 General operation + +Whatever their context (speech, SID, FACCH or none), the Radio Subsystem continuously passes the received traffic frames to the RX DTX handler, individually marked by various pre-processing functions with 3 flags. These are the BFI, the SID and the TAF flags described below, which serve to classify the traffic frame according to the list of terms defined in clause 3. This classification, summarized in table 1 below, in turn allows the RX DTX Handler to determine in a simple way how the received frame is to be handled. + +Table 1: Classification of traffic frames + +| BFI | SID | | | +|-----|-----------------|-------------------|-------------------| +| | 2 | 1 | 0 | +| 0 | Valid SID frame | Invalid SID frame | Good speech frame | +| 1 | | | Unusable frame | + +### 6.1.1 Functions of the RX Radio Subsystem + +The binary BFI flag (Bad Frame Indication, see also GSM 05.05) indicates whether the traffic frame is considered to contain meaningful information bits (BFI=0) or not (BFI=1). In the context of this technical specification, a FACCH frame is considered not to contain meaningful bits and must also be marked with BFI=1. The BFI flag must fulfil the performance requirements of GSM 05.05. + +The ternary SID flag is the output of a SID frame detector, which compares bit by bit the relevant bits of the received traffic frame (the SID field) with the SID code word defined in GSM 06.12. The flag is coded as follows, where n designates the number of bit deviation: + +- SID=2 when $n < 2$ ; +- SID=1 when $2 \leq n < 16$ ; +- SID=0 when $n \geq 16$ . + +The binary TAF flag (Time Alignment Flag) marks with TAF=1 those traffic frames that are aligned with the SACCH multiframe structure as described in the technical specifications referenced in subclause 5.1.2. + +### 6.1.2 Functions of the RX DTX handler + +The RX DTX Handler is responsible for the overall DTX operation on the receive side, which shall be as follows: + +- whenever a good speech frame is detected, the DTX Handler shall pass it directly on to the speech decoder; +- when lost speech or lost SID frames are detected, the substitution and muting procedure defined in GSM 06.11 shall be applied; +- valid SID frames shall result in comfort noise generation, as defined in GSM 06.12, until the next SID frame is expected (TAF=1) or good speech frames are detected. During this period, the RX DTX handler shall ignore any unusable frames delivered by the Radio Subsystem; +- an invalid SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied. + +NOTE: If the first SID frame after a speech burst (a series of good speech frames) is invalid, then the comfort noise parameters can be taken from the last valid SID frame or from the last received good speech frame which, because of the VAD hangover time (see GSM 06.32), may be supposed to contain noise only. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#07 | | | | 4.0.5 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | + +| Change history | | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46032/raw.md b/marked/Rel-18/46_series/46032/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8203bff7089dd2532c9b446917005868ddb6a3fc --- /dev/null +++ b/marked/Rel-18/46_series/46032/raw.md @@ -0,0 +1,1737 @@ + + +# 3GPP TS 46.032 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Full rate speech; Voice Activity Detector (VAD) for full rate speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|----------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope ..... | 6 | +| 2 References ..... | 6 | +| 3 Abbreviations ..... | 6 | +| 4 General ..... | 6 | +| 5 Functional description ..... | 7 | +| 5.1 Overview and principles of operation ..... | 7 | +| 5.2 Algorithm description ..... | 7 | +| 5.2.1 Adaptive filtering and energy computation ..... | 9 | +| 5.2.2 ACF averaging ..... | 9 | +| 5.2.3 Predictor values computation ..... | 9 | +| 5.2.4 Spectral comparison ..... | 10 | +| 5.2.5 Periodicity detection ..... | 10 | +| 5.2.6 Information tone detection ..... | 11 | +| 5.2.7 Threshold adaptation ..... | 12 | +| 5.2.8 VAD decision ..... | 15 | +| 5.2.9 VAD hangover addition ..... | 15 | +| 6 Computational details ..... | 15 | +| 6.1 Adaptive filtering and energy computation ..... | 17 | +| 6.2 ACF averaging ..... | 18 | +| 6.3 Predictor values computation ..... | 18 | +| 6.3.1 Schur recursion to compute reflection coefficients ..... | 19 | +| 6.3.2 Step-up procedure to obtain the aav1[0..8] ..... | 19 | +| 6.3.3 Computation of the rav1[0..8] ..... | 20 | +| 6.4 Spectral comparison ..... | 20 | +| 6.5 Periodicity detection ..... | 21 | +| 6.6 Threshold adaptation ..... | 21 | +| 6.7 VAD decision ..... | 23 | +| 6.8 VAD hangover addition ..... | 23 | +| 6.9 Periodicity updating ..... | 24 | +| 6.10 Tone detection ..... | 24 | +| 6.10.1 Windowing ..... | 24 | +| 6.10.2 Auto-correlation ..... | 24 | +| 6.10.3 Computation of the reflection coefficients ..... | 25 | +| 6.10.4 Filter coefficient calculation ..... | 26 | +| 6.10.5 Pole Frequency Test ..... | 26 | +| 6.10.6 Prediction gain test ..... | 26 | +| 7 Digital test sequences ..... | 27 | +| 7.1 Test configuration ..... | 27 | +| 7.2 Test sequences ..... | 28 | +| Annex A (informative): | 29 | +| A.1 Simplified block filtering operation ..... | 29 | +| A.2 Description of digital test sequences ..... | 29 | +| A.2.1 Test sequences ..... | 29 | +| A.2.2 File format description ..... | 31 | + +A.3 VAD performance..... 33 + +A.4 Pole frequency calculation..... 34 + +**Annex B (normative): Test sequences..... 35** + +**Annex C (informative): Change history..... 36** + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) for the digital cellular telecommunications system. + +Archive en\_300965v080000p0.zip which accompanies the present document, contains test sequences, as described in clause A.2. + +en\_300965v080000p0.zip Annex B: Test sequences for the GSM Full Rate speech codec; Test sequences files \*.inp, \*.cod, \*.vad. + +The specification from which the present document has been derived was originally based on CEPT documentation, hence the presentation of the present document may not be entirely in accordance with the ETSI/PNE Rules. + +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 Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.31. It also specifies the test methods to be used to verify that a VAD complies with the technical specification. + +The requirements are mandatory on any VAD to be used either in the GSM Mobile Stations (MS)s or Base Station Systems (BSS)s. + +# 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.10: "Digital cellular telecommunications system(Phase 2+); Full rate speech; Transcoding". +- [3] GSM 06.12: "Digital cellular telecommunications system(Phase 2+); Full rate speech; Comfort noise aspect for full rate speech traffic channels". +- [4] GSM 06.31: "Digital cellular telecommunications system(Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels". + +# --- 3 Abbreviations + +Abbreviations used in the present document are listed in GSM 01.04 [1]. + +# --- 4 General + +The function of the VAD is to indicate whether each 20 ms frame produced by the speech encoder contains speech or not. The output is a binary flag which is used by the TX DTX handler defined in GSM 06.31 [4]. + +The ETS is organized as follows. + +Clause 2 describes the principles of operation of the VAD. + +In clause 3, the computational details necessary for the fixed point implementation of the VAD algorithm are given. This clause uses the same notation as used for computational details in GSM 06.10. + +The verification of the VAD is based on the use of digital test sequences. Clause 4 defines the input and output signals and the test configuration, whereas the detailed description of the test sequences is contained in clause A.2. + +The performance of the VAD algorithm is characterized by the amount of audible speech clipping it introduces and the percentage activity it indicates. These characteristics for the VAD defined in the present document have been established by extensive testing under a wide range of operating conditions. The results are summarized in clause A.3. + +# 5 Functional description + +The purpose of this clause is to give the reader an understanding of the principles of operation of the VAD, whereas the detailed description is given in clause 3. In case of discrepancy between the two descriptions, the detailed description of clause 3 shall prevail. + +In the following subclauses of clause 2, a Pascal programming type of notation has been used to describe the algorithm. + +## 5.1 Overview and principles of operation + +The function of the VAD is to distinguish between noise with speech present and noise without speech present. The biggest difficulty for detecting speech in a mobile environment is the very low speech/noise ratios which are often encountered. The accuracy of the VAD is improved by using filtering to increase the speech/noise ratio before the decision is made. + +For a mobile environment, the worst speech/noise ratios are encountered in moving vehicles. It has been found that the noise is relatively stationary for quite long periods in a mobile environment. It is therefore possible to use an adaptive filter with coefficients obtained during noise, to remove much of the vehicle noise. + +The VAD is basically an energy detector. The energy of the filtered signal is compared with a threshold; speech is indicated whenever the threshold is exceeded. + +The noise encountered in mobile environments may be constantly changing in level. The spectrum of the noise can also change, and varies greatly over different vehicles. Because of these changes the VAD threshold and adaptive filter coefficients must be constantly adapted. To give reliable detection the threshold must be sufficiently above the noise level to avoid noise being identified as speech but not so far above it that low level parts of speech are identified as noise. The threshold and the adaptive filter coefficients are only updated when speech is not present. It is, of course, potentially dangerous for a VAD to update these values on the basis of its own decision. This adaptation therefore only occurs when the signal seems stationary in the frequency domain but does not have the pitch component inherent in voiced speech. A tone detector is also used to prevent adaptation during information tones. + +A further mechanism is used to ensure that low level noise (which is often not stationary over long periods) is not detected as speech. Here, an additional fixed threshold is used. + +A VAD hangover period is used to eliminate mid-burst clipping of low level speech. Hangover is only added to speech-bursts which exceed a certain duration to avoid extending noise spikes. + +## 5.2 Algorithm description + +The block diagram of the VAD algorithm is shown in figure 2.1. The individual blocks are described in the following subclauses. ACF, N and sof are calculated in the speech encoder. + +![Functional block diagram of the VAD (Voice Activity Detection) system. The diagram shows the flow of data from input ACF, N, and sof through various processing blocks to produce the final vad output. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Global variables shown are r_vad, p_vad, ptch, tone, r_av1, av1, av0, th_vad, stat, v_vad, and vad.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` + +graph LR + ACF[ACF] --> AFE[Adaptive filtering and energy computation] + ACF --> PD[Periodicity detection] + ACF --> TD[Tone detection] + ACF --> PVE[Predictor values computation] + ACF --> AA[ACF averaging] + N[N] --> PD + sof[sof] --> TD + PD -- ptch --> TA[Threshold adaptation] + TD -- tone --> TA + PVE -- r_av1 --> TA + PVE -- r_av1 --> SC[Spectral comparison] + AA -- av1 --> PVE + AA -- av0 --> SC + AFE -- p_vad --> VD[VAD decision] + AFE -- r_vad --> TA + TA -- th_vad --> VD + TA -- stat --> SC + VD -- v_vad --> VHA[VAD hangover addition] + VHA -- vad --> Output[vad] + +``` + +Functional block diagram of the VAD (Voice Activity Detection) system. The diagram shows the flow of data from input ACF, N, and sof through various processing blocks to produce the final vad output. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Global variables shown are r\_vad, p\_vad, ptch, tone, r\_av1, av1, av0, th\_vad, stat, v\_vad, and vad. + +**Figure 2.1: Functional block diagram of the VAD** + +The global variables shown in the block diagram are described as follows: + +- ACF are auto-correlation coefficients which are calculated in the speech encoder defined in GSM 06.10 (subclause 3.1.4, see also clause A.1). The inputs to the speech encoder are 16 bit 2's complement numbers, as described in GSM 06.10, subclause 4.2.0; +- av0 and av1 are averaged ACF vectors; +- rav1 are autocorrelated predictor values obtained from av1; +- rvad are the autocorrelated predictor values of the adaptive filter; +- N is the long term predictor lag value which is obtained every sub-segment in the speech coder defined in GSM 06.10; +- ptch indicates whether the signal has a steady periodic component; +- sof is the offset compensated signal frame obtained in the speech coder defined in GSM 06.10; +- pvad is the energy in the current frame of the input signal after filtering; +- thvad is an adaptive threshold; +- stat indicates spectral stationarity; +- vvad indicates the VAD decision before hangover is added; +- vad is the final VAD decision with hangover included. + +### 5.2.1 Adaptive filtering and energy computation + +Pvad is computed as follows: + +$$Pvad = rvad_0 acf_0 + 2 \sum_{i=1}^8 rvad_i acf_i$$ + +This corresponds to performing an 8th order block filtering on the input samples to the speech encoder, after zero offset compensation and pre-emphasis. This is explained in clause A.1. + +### 5.2.2 ACF averaging + +Spectral characteristics of the input signal have to be obtained using blocks that are larger than one 20 ms frame. This is done by averaging the auto-correlation values for several consecutive frames. This averaging is given by the following equations: + +$$av0\{n\}_i = \sum_{j=0}^{frames-1} acf\{n-j\}_i \quad ; i = 0..8$$ + +$$av1\{n\}_i = av0\{n-frames\}_i \quad ; i = 0..8$$ + +Where n represents the current frame, $n-1$ represents the previous frame etc. The values of constants are given in table 2.1. + +**Table 2.1: Constants and variables for ACF averaging** + +| Constant | Value | Variable | Initial value | +|----------|-------|-----------------------------|---------------| +| frames | 4 | previous ACF's
av0 & av1 | All set to 0 | + +### 5.2.3 Predictor values computation + +The filter predictor values aav1 are obtained from the auto-correlation values av1 according to the equation: + +$$\underline{a} = \underline{R}^{-1} \underline{p}$$ + +where: + +$$\underline{R} = \begin{bmatrix} av1[0], & av1[1], & av1[2], & av1[3], & av1[4], & av1[5], & av1[6], & av1[7] \\ av1[1], & av1[0], & av1[1], & av1[2], & av1[3], & av1[4], & av1[5], & av1[6] \\ av1[2], & av1[1], & av1[0], & av1[1], & av1[2], & av1[3], & av1[4], & av1[5] \\ av1[3], & av1[2], & av1[1], & av1[0], & av1[1], & av1[2], & av1[3], & av1[4] \\ av1[4], & av1[3], & av1[2], & av1[1], & av1[0], & av1[1], & av1[2], & av1[3] \\ av1[5], & av1[4], & av1[3], & av1[2], & av1[1], & av1[0], & av1[1], & av1[2] \\ av1[6], & av1[5], & av1[4], & av1[3], & av1[2], & av1[1], & av1[0], & av1[1] \\ av1[7], & av1[6], & av1[5], & av1[4], & av1[3], & av1[2], & av1[1], & av1[0] \end{bmatrix}$$ + +and: + +$$\mathbf{p} = \begin{bmatrix} |av1[1]| \\ |av1[2]| \\ |av1[3]| \\ |av1[4]| \\ |av1[5]| \\ |av1[6]| \\ |av1[7]| \\ |av1[8]| \end{bmatrix} \quad \mathbf{a} = \begin{bmatrix} |aav1[1]| \\ |aav1[2]| \\ |aav1[3]| \\ |aav1[4]| \\ |aav1[5]| \\ |aav1[6]| \\ |aav1[7]| \\ |aav1[8]| \end{bmatrix}$$ + +$$aav1[0] = -1$$ + +av1 is used in preference to av0 as av0 may contain speech. + +The autocorrelated predictor values rav1 are then obtained: + +$$rav1_i = \sum_{k=0}^{8-i} aav1_k aav1_{k+i} \quad ; i = 0..8$$ + +### 5.2.4 Spectral comparison + +The spectra represented by the autocorrelated predictor values rav1 and the averaged auto-correlation values av0 are compared using the distortion measure dm defined below. This measure is used to produce a Boolean value stat every 20 ms, as given by these equations: + +$$dm = \frac{\left( rav1_0 av0_0 + 2 \sum_{i=1}^8 rav1_i av0_i \right)}{av0_0}$$ + +$$\text{difference} = |dm - \text{lastdm}|$$ + +$$\text{lastdm} = dm$$ + +$$\text{stat} = \text{difference} < \text{thresh}$$ + +The values of constants and initial values are given in table 2.2. + +**Table 2.2: Constants and variables for spectral comparison** + +| Constant | Value | Variable | Initial value | +|----------|-------|----------|---------------| +| thresh | 0.05 | lastdm | 0 | + +### 5.2.5 Periodicity detection + +The frequency spectrum of mobile noise is relatively stationary over quite long periods. The Inverse Filter Autocorrelated Predictor coefficients of the adaptive filter rvad are only updated when this stationarity is detected. Vowel sounds however, also have this stationarity, but can be excluded by detecting the periodicity of these sounds using the long term predictor lag values (Nj) which are obtained every sub-segment from the speech codec defined in GSM 06.10. Consecutive lag values are compared. Cases in which one lag value is a factor of the other are catered for, however cases in which both lag values have a common factor, are not. This case is not important for speech input but this method of periodicity detection may fail for some sine waves. The Boolean variable ptch is updated every 20 ms and is true when periodicity is detected. It is calculated according to the following equation: + +$$\text{ptch} = \text{oldlagcount} + \text{veryoldlagcount} \geq \text{nthresh}$$ + +The following operations are done after the VAD decision and when the current LTP lag values (N0 .. N3) are available, this reduces the delay of the VAD decision. ( $N\{-1\} = N3$ of previous segment.) + +``` + +lagcount = 0 + +for j = 0 to 3 do +begin + smalllag = maximum(Nj, N{j-1}) mod minimum(Nj, N{j-1}) + if minimum(smalllag, minimum(Nj, N{j-1}) - smalllag) < lthresh + then increment(lagcount) +end + +veryoldlagcount = oldlagcount + +oldlagcount = lagcount + +``` + +The values of constants and initial values are given in table 2.. + +**Table 2.3: Constants and variables for periodicity detection** + +| Constant | Value | Variable | Initial value | +|----------|-------|-----------------|---------------| +| lthresh | 2 | oldlagcount | 0 | +| nthresh | 4 | veryoldlagcount | 0 | +| | | N3 | 40 | + +### 5.2.6 Information tone detection + +The tone flag is only evaluated in the downlink VAD. In the uplink VAD, tone detection is not performed and tone = false. + +Computation of the tone flag is complex. It is therefore evaluated after the processing of the current speech encoder frame. In this way transmission of the speech or SID frame is not delayed. + +Information tones and environmental noise can be classified by inspecting the short term prediction gain, information tones resulting in higher prediction gains than environmental noise. Tones can therefore be detected by comparing the prediction gain to a fixed threshold. By limiting the prediction gain calculation to a fourth order analysis, information signals consisting of one or two tones can be detected whilst minimizing the prediction gain for environmental noise. + +The prediction gain decision is implemented by comparing the normalized prediction error with a threshold. This measure is used to evaluate the Boolean variable tone every 20 ms. The signal is classified as a tone if the prediction error is smaller than the threshold predth. This is equivalent to a prediction gain threshold of 13,5 dB. + +Mobile noise can contain very strong resonances at low frequencies, resulting in a high prediction gain. A further test is therefore made to determine the pole frequency of a second order analysis of the signal frame. The signal is classified as noise if the frequency of the pole is less than 385 Hz. The pole frequency calculation is described in clause A.4. + +The algorithm for detecting information tones is as follows: + +``` + +tone = false + +den = a[1]*a[1] +num = 4*a[2] - a[1]*a[1] + +if ( num <= 0 ) + return + +if ( ( a[1] < 0 ) AND ( num / den < freqth ) ) + return + +prederr = MULT ( 1 - RC[i]*RC[i] ) + i=1 + +if (prederr < predth) + tone = true + +return + +``` + +The values of the constants are given in table 2.4. The coefficients a[1..2] are transversal filter coefficients calculated from rc[1..2]. The calculation of the reflection coefficients rc[1..4] is described below. + +The offset compensated signal frame sof[0..159] is multiplied by the Hanning window to give the windowed frame sofh[0..159]: + +$$sofh_i = sof_i hann_i \quad i = 0..159$$ + +where + +$$hann_i = 0.5 \left( 1 - \cos \left( 2\pi \left( \frac{i}{159} \right) \right) \right) \quad i = 0..159$$ + +The auto-correlation $acfh[0..4]$ of the windowed signal frame is then calculated: + +$$acfh_k = \sum_{i=k}^{159} sofh_i sofh_{i-k} \quad ; k = 0..4$$ + +$rc[1..4]$ are then calculated from $acfh[0..4]$ using the Schur recursion described in the RPE-LTP codec. + +**Table 2.4: Constants for information tone detection** + +| Constant | Value | +|----------|--------| +| freqth | 0,0973 | +| predth | 0,0158 | + +NOTE: Reflection coefficients are available in the RPE-LTP codec. However, they are calculated after pre-emphasis using a rectangular window and do not give good tone detection results. + +### 5.2.7 Threshold adaptation + +A check is made every 20 ms to determine whether the VAD decision threshold (thvad) should be changed. This adaptation is carried out according to the flowchart shown in figure 2.2. The constants used are given in table 2.5. + +Adaptation takes place in two different situations: firstly whenever $ACF[0]$ is very low and secondly whenever there is a very high probability that speech and information tones are not present. + +In the first case, the threshold is adapted if the energy of the input signal is less than $pth$ . The threshold is set to $plev$ without carrying out any further tests because at these very low levels the effect of the signal quantization makes it impossible to obtain reliable results from these tests. + +In the second case, the decision threshold (thvad) and the adaptive filter coefficients (rvad) are only updated with the $rav1$ values when there is a very high probability that speech and information tones are not present. Adaptation occurs if the following conditions are met over a number (adp) of signal frames: + +- stationarity is detected in the frequency domain; +- the signal does not contain a periodic component; +- information tones are not present. + +The step-size by which the threshold is adapted is not constant but a proportion of the current value (determined by constants $dec$ and $inc$ ). The adaptation begins by experimentally multiplying the threshold by a factor of $(1-1/dec)$ . If the new threshold is now higher than or equal to $Pvad$ times $fac$ then the threshold needed to be decreased and it is left at this new lower level. If, on the other hand, the new threshold level is less than $Pvad$ times $fac$ then the threshold either needed to be increased or kept constant. In this case it is set to $Pvad$ times $fac$ unless this would mean multiplying it by more than a factor of $(1+1/inc)$ (in which case it is multiplied by a factor of $(1+1/inc)$ ). The threshold is never allowed to be greater than $Pvad+margin$ . + +**Table 2.5: Constants and variables for threshold adaptation** + +| Constant | Value | Variable | Initial value | +|----------|------------|------------|---------------| +| pth | 300 000 | adaptcount | 0 | +| plev | 800 000 | thvad | 1 000 000 | +| fac | 3.0 | rvad[0] | 6 | +| adp | 8 | rvad[1] | -4 | +| inc | 16 | rvad[2] | 1 | +| dec | 32 | rvad[3] to | | +| margin | 80 000 000 | rvad[8] | All 0 | + +![Flow diagram for threshold adaptation. The process starts at BEGIN, checks if ACF[0] < pth. If yes, th_vad = plev and ends. If no, checks if stat and not ptch and not tone. If yes, increments adaptcount. If no, sets adaptcount = 0. Then checks if adaptcount > adp. If yes, th_vad = th_vad - th_vad / dec. Then checks if th_vad < p_vad * fac. If yes, th_vad = min(th_vad + th_vad / inc, p_vad * fac). Then checks if th_vad > p_vad + margin. If yes, th_vad = p_vad + margin. Finally, r_vad = r_av1, adaptcount = adp + 1, and ends.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` +graph TD; BEGIN((BEGIN)) --> ACF{ACF[0] < pth ?}; ACF -- yes --> th_vad_1[th_vad = plev]; ACF -- no --> stat{stat and not ptch and not tone ?}; stat -- yes --> inc[increment adaptcount]; stat -- no --> zero[adaptcount = 0]; inc --> adp{adaptcount > adp ?}; zero --> adp; th_vad_1 --> END1((END)); adp -- yes --> dec[th_vad = th_vad - th_vad / dec]; adp -- no --> END1; dec --> fac{th_vad < p_vad * fac ?}; fac -- yes --> min[th_vad = min(th_vad + th_vad / inc, p_vad * fac)]; fac -- no --> margin{th_vad > p_vad + margin ?}; min --> margin; margin -- yes --> margin_val[th_vad = p_vad + margin]; margin -- no --> r_vad[r_vad = r_av1]; margin_val --> r_vad; r_vad --> adaptcount[adaptcount = adp + 1]; adaptcount --> END2((END)); +``` + +Flow diagram for threshold adaptation. The process starts at BEGIN, checks if ACF[0] < pth. If yes, th\_vad = plev and ends. If no, checks if stat and not ptch and not tone. If yes, increments adaptcount. If no, sets adaptcount = 0. Then checks if adaptcount > adp. If yes, th\_vad = th\_vad - th\_vad / dec. Then checks if th\_vad < p\_vad \* fac. If yes, th\_vad = min(th\_vad + th\_vad / inc, p\_vad \* fac). Then checks if th\_vad > p\_vad + margin. If yes, th\_vad = p\_vad + margin. Finally, r\_vad = r\_av1, adaptcount = adp + 1, and ends. + +Figure 2.2: Flow diagram for threshold adaptation + +### 5.2.8 VAD decision + +Prior to hangover the VAD decision condition is: + +``` +vvad = pvad > thvad +``` + +### 5.2.9 VAD hangover addition + +VAD hangover is only added to bursts of speech greater than or equal to burstconst blocks. The Boolean variable vad indicates the decision of the VAD with hangover included. The values of the constants are given in table 2.6. The hangover algorithm is as follows: + +``` +if vvad then increment(burstcount) else burstcount = 0 + +if burstcount >= burstconst then +begin + hangcount = hangconst; + burstcount = burstconst +end + +vad = vvad or (hangcount >= 0) + +if hangcount >= 0 then decrement(hangcount) +``` + +**Table 2.6: Constants and variables for VAD hangover addition** + +| Constant | Value | Variable | Initial value | +|------------|-------|------------|---------------| +| burstconst | 3 | burstcount | 0 | +| hangconst | 5 | hangcount | -1 | + +# 6 Computational details + +In the next paragraphs, the detailed description of the VAD algorithm follows the preceding high level description. This detailed description is divided in ten clauses related to the blocks of figure 2.1 (except periodicity updating) in the high level description of the VAD algorithm. + +Those clauses are: + +- 1) adaptive filtering and energy computation; +- 2) ACF averaging; +- 3) predictor values computation; +- 4) spectral comparison; +- 5) periodicity detection; +- 6) threshold adaptation; +- 7) VAD decision; +- 8) VAD hangover addition; +- 9) periodicity updating; +- 10) information tone detection. + +The VAD algorithm takes as input the following variables of the RPE-LTP encoder (see the detailed description of the RPE-LTP encoder GSM 06.10): + +- L\_ACF[0..8], auto-correlation function (GSM 06.10/4.2.4); +- scalauto, scaling factor to compute the L\_ACF[0..8] (GSM 06.10/4.2.4); + +- Nc, LTP lag (one for each sub-segment, GSM 06.10/4.2.11); +- sof, offset compensated signal frame (GSM 06.10/4.2.2). + +So four Nc values are needed for the VAD algorithm. + +The VAD computation can start as soon as the L\_ACF[0..8] and scalauto variables are known. This means that the VAD computation can take place after part 4.2.4 of GSM 06.10 (Auto-correlation) of the LPC analysis clause of the RPE-LTP encoder. This scheme will reduce the delay to yield the VAD information. The periodicity updating (included in subclause 2.2.5) and information tone detection, are done after the processing of the current speech encoder frame. + +All the arithmetic operations and names of the variables follow the RPE-LTP detailed description. To increase the precision within the fixed point implementation, a pseudo-floating point representation of some variables is used. This stands for the following variables (and related constants) of the VAD algorithm: + +pvad: Energy of filtered signal; + +thvad: Threshold of the VAD decision; + +acf0: Energy of input signal. + +For the representation of these variables, two integers (16 bits) are needed: + +- one for the exponent (e\_pvad, e\_thvad, e\_acf0); +- one for the mantissa (m\_pvad, m\_thvad, m\_acf0). + +The value e\_pvad represents the lowest power of 2 just greater or equal to the actual value of pvad and the m\_pvad value represents a integer which is always greater or equal to 16384 (normalized mantissa). It means that the pvad value is equal to: + +$$\text{pvad} = 2^{e\_pvad} * (m\_pvad / 32768)$$ + +This scheme guarantees a large dynamic range for the pvad value and always keeps a precision of 16 bits. All the comparisons are easy to make by comparing the exponents of two variables and the VAD algorithm needs only one pseudo-floating point addition. All the computations related to the pseudo-floating point variables require very simple 16 or 32 bits arithmetic operations defined in the detailed description of the RPE-LTP encoder. This pseudo-floating point arithmetic is only used in subclauses 3.1 and 3.6. + +Table 3.1 gives a list of all the variables of the VAD algorithm that must be initialized in the reset procedure and kept in memory for processing the subsequent frame of the RPE- LTP encoder. The types (16 or 32 bits) and initial values of all these variables are clearly indicated and their related subclause is also mentioned. The bit exact implementation uses other temporary variables that are introduced in the detailed description whenever it is needed. + +Table 3.1: Initial values for variables to be stored in memory + +| Names of variables: | type (# of bits): | Initialization: | Subclause: | +|------------------------------------------------------------------------------------|--------------------------|-------------------------------------|--------------------------------------------------| +| Adaptive filter coefficients:
rvad[0]
rvad[1]
rvad[2]
rvad[3..8] |
16
16
16
16 |
24 576
-16 384
4 096
0 |
3.1, 3.6
3.1, 3.6
3.1, 3.6
3.1, 3.6 | +| Scaling factor of rvad[0..8]:
normrvad |
16 |
7 |
3.1, 3.6 | +| Delay line of the auto-correlation coefficients:
L_sacf[0..26]
L_sav0[0..35] |
32
32 |
0
0 |
3.2
3.2 | +| Pointers on the delay lines:
pt_sacf
pt_sav0 |
16
16 |
0
0 |
3.2
3.2 | +| Distance measure:
L_lastdm |
32 |
0 |
3.4 | +| Periodicity counters:
oldlagcount
veryoldlagcount |
16
16 |
0
0 |
3.5, 3.9
3.5, 3.9 | +| Adaptive threshold:
e_thvad (exponent)
m_thvad (mantissa) |
16
16 |
20
31 250 |
3.6
3.6 | +| Counter for adaptation:
adaptcount |
16 |
0 |
3.6 | +| Hangover flags:
burstcount
hangcount |
16
16 |
0
-1 |
3.8
3.8 | +| LTP lag memory:
oldlag |
16 |
40 |
3.9 | +| Tone Detection
tone |
16 |
0 |
3.10 | + +## 6.1 Adaptive filtering and energy computation + +This subclause computes the e\_pvad and m\_pvad variables which represent the pvad value. It needs the L\_ACF[0..8] and scalauto variables of the RPE-LTP algorithm and the rvad[0..8] and normrvad variables produced by subclause 3.6 of the VAD algorithm. It also computes a floating point representation of L\_ACF[0] (e\_acf0 and m\_acf0) used in subclause 3.6. + +### Test if L\_ACF[0] is equal to 0: + +``` +IF ( scalauto < 0 ) THEN scalvad = 0; +ELSE scalvad = scalauto; / keep scalvad for use in subclause 3.2 / + +IF ( L_ACF[0] == 0 ) THEN + | e_pvad = -32768; + | m_pvad = 0; + | e_acf0 = -32768; + | m_acf0 = 0; + | EXIT /continue with subclause 3.2/ +``` + +### Re-normalization of the L\_ACF[0..8]: + +``` +normacf = norm( L_ACF[0] ); + +| FOR i = 0 to 8: +| sacf[i] = ( L_ACF[i] << normacf ) >> 19; +| NEXT i: +``` + +### Computation of e\_acf0 and m\_acf0: + +``` +e_acf0 = add( 32, (scalvad << 1) ); +e_acf0 = sub( e_acf0, normacf); +m_acf0 = sacf[0] << 3; +``` + +### Computation of e\_pvad and m\_pvad: + +``` +e_pvad = add( e_acf0, 14 ); +e_pvad = sub( e_pvad, normrvad ); + +L_temp = 0; + +| FOR i = 1 to 8: +| L_temp = L_add( L_temp, L_mult( sacf[i], rvad[i] ) ); +| NEXT i: + +L_temp = L_add( L_temp, L_mult( sacf[0], rvad[0] ) >> 1 ); + +IF ( L_temp <= 0 ) THEN L_temp = 1; + +normprod = norm( L_temp ); +e_pvad = sub( e_pvad, normprod ); +m_pvad = ( L_temp << normprod ) >> 16; +``` + +## 6.2 ACF averaging + +This subclause uses the L\_ACF[0..8] and the scalvad variables to compute the array L\_av0[0..8] and L\_av1[0..8] used in subclause 3.3 and 3.4. + +### Computation of the scaling factor: + +``` +scal = sub( 10, (scalvad << 1) ); +``` + +### Computation of the arrays L\_av0[0..8] and L\_av1[0..8]: + +``` +| FOR i = 0 to 8: +| L_temp = L_ACF[i] >> scal; +| L_av0[i] = L_add( L_sacf[i], L_temp ); +| L_av0[i] = L_add( L_sacf[i+9], L_av0[i] ); +| L_av0[i] = L_add( L_sacf[i+18], L_av0[i] ); +| L_sacf[ pt_sacf + i ] = L_temp; +| L_av1[i] = L_sav0[ pt_sav0 + i ]; +| L_sav0[ pt_sav0 + i ] = L_av0[i]; +| NEXT i: +``` + +### Update of the array pointers: + +``` +IF ( pt_sacf == 18 ) THEN pt_sacf = 0; +ELSE pt_sacf = add( pt_sacf, 9); + +IF ( pt_sav0 == 27 ) THEN pt_sav0 = 0; +ELSE pt_sav0 = add( pt_sav0, 9); +``` + +## 6.3 Predictor values computation + +This subclause computes the array rav1[0..8] needed for the spectral comparison and the threshold adaptation. It uses the L\_av1[0..8] computed in subclause 3.2, and is divided in the three following subclauses: + +- Schur recursion to compute reflection coefficients. +- Step up procedure to obtain the aav1[0..8]. +- Computation of the rav1[0..8]. + +### 6.3.1 Schur recursion to compute reflection coefficients + +This subclause is identical to the one used in the RPE-LTP algorithm. The array vpar[1..8] is computed with the array L\_av1[0..8] as an input. + +#### Schur recursion with 16 bits arithmetic: + +``` +IF( L_av1[0] == 0 ) THEN + |== FOR i = 1 to 8: + | vpar[i] = 0; + |== NEXT i: + | EXIT; /continue with subclause 3.3.2/ +temp = norm( L_av1[0] ); +|== FOR k=0 to 8: +| sacf[k] = ( L_av1[k] << temp ) >> 16; +|== NEXT k: +``` + +#### Initialize array P[..] and K[..] for the recursion: + +``` +|== FOR i=1 to 7: +| K[9-i] = sacf[i]; +|== NEXT i: + +|== FOR i=0 to 8: +| P[i] = sacf[i]; +|== NEXT i: +``` + +#### Compute reflection coefficients: + +``` +|== FOR n=1 to 8: +| IF( P[0] < abs( P[1] ) ) THEN +| |== FOR i = n to 8: +| | vpar[i] = 0; +| |== NEXT i: +| | EXIT; /continue with +| | subclause 3.3.2/ +| vpar[n] = div( abs( P[1] ), P[0] ); +| IF ( P[1] > 0 ) THEN vpar[n] = sub( 0, vpar[n] ); +| IF ( n == 8 ) THEN EXIT; /continue with subclause 3.3.2/ +| Schur recursion: +| P[0] = add( P[0], mult_r( P[1], vpar[n] ) ); +| |=== FOR m=1 to 8-n: +| | P[m] = add( P[m+1], mult_r( K[9-m], vpar[n] ) ); +| | K[9-m] = add( K[9-m], mult_r( P[m+1], vpar[n] ) ); +| |=== NEXT m: +| +|== NEXT n: +``` + +### 6.3.2 Step-up procedure to obtain the aav1[0..8] + +#### Initialization of the step-up recursion: + +``` +L_coef[0] = 16384 << 15; +L_coef[1] = vpar[1] << 14; +``` + +#### Loop on the LPC analysis order: + +``` +|= FOR m = 2 to 8: +|== FOR i = 1 to m-1: +|== temp = L_coef[m-i] >> 16; / takes the msb / +|== L_work[i] = L_add( L_coef[i], L_mult( vpar[m], temp ) ); +|== NEXT i +| +|== FOR i = 1 to m-1: +|== L_coef[i] = L_work[i]; +``` + +``` + +|== NEXT i +| +| L_coef[m] = vpar[m] << 14; +| NEXT m: + +``` + +**Keep the aav1[0..8] on 13 bits for next clause:** + +``` + +| FOR i = 0 to 8: +| aav1[i] = L_coef[i] >> 19; +| NEXT i: + +``` + +### 6.3.3 Computation of the rav1[0..8] + +``` + +| FOR i= 0 to 8: +| L_work[i] = 0; +|== FOR k = 0 to 8-i: +|== L_work[i] = L_add( L_work[i], L_mult( aav1[k], aav1[k+i] ) ); +|== NEXT k: +| NEXT i: + +IF ( L_work[0] == 0 ) THEN normrav1 =0; +ELSE normrav1 = norm( L_work[0] ); + +| FOR i= 0 to 8: +| rav1[i] = ( L_work[i] << normrav1 ) >> 16; +| NEXT i: + +``` + +Keep the normrav1 for use in subclause 3.4 and 3.6. + +## 6.4 Spectral comparison + +This subclause computes the variable stat needed for the threshold adaptation. It uses the array L\_av0[0..8] computed in subclause 3.2 and the array rav1[0..8] computed in subclause 3.3.3. + +**Re-normalize L\_av0[0..8]:** + +``` + +IF ( L_av0[0] == 0 ) THEN +| FOR i = 0 to 8: +| sav0[i] = 4095; +| NEXT i: +ELSE +| shift = norm( L_av0[0] ); +| FOR i = 0 to 8: +| sav0[i] = ( L_av0[i] << shift-3 ) >> 16; +| NEXT i: + +``` + +**Compute partial $\sum$ of dm:** + +``` + +L_ $\sum$ p = 0; +| FOR i = 1 to 8: +| L_ $\sum$ p = L_add( L_ $\sum$ p, L_mult( rav1[i], sav0[i] ) ); +| NEXT i: + +``` + +**Compute the division of partial $\sum$ by sav0[0]:** + +``` + +IF ( L_ $\sum$ p < 0 ) THEN L_temp = L_sub( 0, L_ $\sum$ p ); +ELSE L_temp = L_ $\sum$ p; + +IF ( L_temp == 0 ) THEN +| L_dm = 0; +| shift = 0; +ELSE +| sav0[0] = sav0[0] << 3; +| shift = norm( L_temp ); +| temp = ( L_temp << shift ) >> 16; + +``` + +``` + +| IF ( sav0[0] >= temp ) THEN +| | divshift = 0; +| | temp = div( temp, sav0[0] ); +| ELSE +| | divshift = 1; +| | temp = sub( temp, sav0[0] ); +| | temp = div( temp, sav0[0] ); +| +| IF( divshift == 1 ) THEN L_dm = 32768; +| ELSE L_dm = 0; +| +| L_dm = L_add( L_dm, temp) << 1; +| +| IF( L_Σ p < 0 ) THEN L_dm = L_sub( 0, L_dm); + +``` + +### Re-normalization and final computation of L\_dm: + +``` + +L_dm = ( L_dm << 14 ); +L_dm = L_dm >> shift; +L_dm = L_add( L_dm, ( rav1[0] << 11 ) ); +L_dm = L_dm >> normrav1; + +``` + +### Compute the difference and save L\_dm: + +``` + +L_temp = L_sub( L_dm, L_lastdm ); +L_lastdm = L_dm; +IF ( L_temp < 0 ) THEN L_temp = L_sub( 0, L_temp ); +L_temp = L_sub( L_temp, 3277 ); + +``` + +### Evaluation of the stat flag: + +``` + +IF ( L_temp < 0 ) THEN stat = 1; +ELSE stat = 0; + +``` + +## 6.5 Periodicity detection + +This subclause just sets the ptch flag needed for the threshold adaptation. + +``` + +temp = add( oldlagcount, veryoldlagcount ); +IF ( temp >= 4 ) THEN ptch = 1; +ELSE ptch = 0; + +``` + +## 6.6 Threshold adaptation + +This subclause uses the variables e\_pvad, m\_pvad, e\_acf0 and m\_acf0 computed in subclause 3.1. It also uses the flags stat (see subclause 3.4) and ptch (see subclause 3.5). It follows the flowchart represented on figure 2.2. + +Some constants, represented by a floating point format, are needed and a symbolic name (in capital letter) for their exponent and mantissa is used; table 3.2 lists all these constants with the symbolic names associated and their numerical constant values. + +**Table 3.2: List of constants** + +| Constant | Exponent | Mantissa | +|----------|---------------|-------------------| +| pth | E_PTH = 19 | M_PTH = 18 750 | +| margin | E_MARGIN = 27 | M_MARGIN = 19 531 | +| plev | E_PLEV = 20 | M_PLEV = 25 000 | + +NOTE: Floating point representation of constants used in subclause 3.6: + +``` + +pth = 2(E_PTH)x(M_PTH/32768). +margin = 2(E_MARGIN)x(M_MARGIN/32768). +plev = 2(E_PLEV)x(M_PLEV/32768). + +``` + +Test if acf0 < pth; if yes set thvad to plev: + +``` + +comp = 0; +IF ( e_acf0 < E_PTH ) THEN comp = 1; +IF ( e_acf0 == E_PTH ) THEN IF ( m_acf0 < M_PTH ) THEN comp =1; +IF ( comp == 1 ) THEN + | e_thvad = E_PLEV; + | m_thvad = M_PLEV; + | EXIT; /continue with subclause 3.7/ + +``` + +### Test if an adaptation is needed: + +``` + +comp = 0; +IF ( ptch == 1 ) THEN comp = 1; +IF ( stat == 0 ) THEN comp = 1; +IF ( tone == 1 ) THEN comp = 1; +IF ( comp == 1 ) THEN + | adaptcount = 0; + | EXIT; /continue with subclause 3.7/ + +``` + +### Incrementation of adaptcount: + +``` + +adaptcount = add( adaptcount, 1 ); +IF ( adaptcount <= 8 ) THEN EXIT; /continue with subclause 3.7/ + +``` + +### Computation of thvad-(thvad/dec): + +``` + +m_thvad = sub( m_thvad, (m_thvad >> 5) ); +IF ( m_thvad < 16384 ) THEN + | m_thvad = m_thvad << 1; + | e_thvad = sub( e_thvad, 1 ); + +``` + +### Computation of pvad\*fac: + +``` + +L_temp = L_add( m_pvad, m_pvad ); +L_temp = L_add( L_temp, m_pvad ); +L_temp = L_temp >> 1; +e_temp = add( e_pvad, 1 ); +IF ( L_temp > 32767 ) THEN + | L_temp = L_temp >> 1; + | e_temp = add( e_temp, 1 ); +m_temp = L_temp; + +``` + +### Test if thvad < pvad\*fac: + +``` + +comp = 0; +IF ( e_thvad < e_temp ) THEN comp = 1; +IF ( e_thvad == e_temp ) THEN IF ( m_thvad < m_temp ) THEN comp =1; + +``` + +### Computation of minimum (thvad+(thvad/inc), pvad\*fac) if comp = 1: + +``` + +IF ( comp == 1 ) THEN +| Compute thvad +(thvad/inc). +| L_temp = L_add( m_thvad, (m_thvad >> 4) ); +| IF ( L_temp > 32767 ) THEN +| | m_thvad = L_temp >> 1; +| | e_thvad = add( e_thvad, 1 ); +| ELSE m_thvad = L_temp; +| comp2 = 0; +| IF ( e_temp < e_thvad ) THEN comp2 = 1; +| IF ( e_temp == e_thvad ) THEN IF ( m_temp < m_thvad ) THEN comp2 = 1; +| IF ( comp2 == 1 ) THEN +| | e_thvad = e_temp; +| | m_thvad = m_temp; + +``` + +### Computation of pvad + margin: + +``` + +IF ( e_pvad == E_MARGIN ) THEN + | L_temp = L_add(m_pvad, M_MARGIN); + | m_temp = L_temp >> 1; + +``` + +``` + + | e_temp = add( e_pvad, 1 ); +ELSE +| IF ( e_pvad > E_MARGIN ) THEN +| | temp = sub( e_pvad, E_MARGIN ); +| | temp = M_MARGIN >> temp; +| | L_temp = L_add( m_pvad, temp ); +| | IF ( L_temp > 32767) THEN +| | | e_temp = add( e_pvad, 1 ); +| | | m_temp = L_temp >> 1; +| | ELSE +| | | e_temp = e_pvad; +| | | m_temp = L_temp; +| ELSE +| | temp = sub( E_MARGIN, e_pvad ); +| | temp = m_pvad >> temp; +| | L_temp = L_add( M_MARGIN, temp ); +| | IF ( L_temp > 32767) THEN +| | | e_temp = add( E_MARGIN, 1 ); +| | | m_temp = L_temp >> 1; +| | ELSE +| | | e_temp = E_MARGIN; +| | | m_temp = L_temp; + +``` + +### Test if thvad > pvad + margin: + +``` + +comp = 0; +IF ( e_thvad > e_temp) THEN comp = 1; +IF (e_thvad == e_temp) THEN IF (m_thvad > m_temp) THEN comp =1; + +IF ( comp == 1 ) THEN +| e_thvad = e_temp; +| m_thvad = m_temp; + +``` + +### Initialize new rvad[0..8] in memory: + +``` + +normrvad = normrav1; + +|= FOR i = 0 to 8: +|= rvad[i] = rav1[i]; +|= NEXT i: + +``` + +### Set adaptcount to adp + 1: + +``` + +adaptcount = 9; + +``` + +## 6.7 VAD decision + +This subclause only outputs the result of the comparison between pvad and thvad using the pseudo-floating point representation of thvad and pvad. The values e\_pvad and m\_pvad are computed in subclause 3.1 and the values e\_thvad and m\_thvad are computed in subclause 3.6. + +``` + +vvad = 0; +IF (e_pvad > e_thvad) THEN vvad = 1; +IF (e_pvad == e_thvad) THEN IF (m_pvad > m_thvad) THEN vvad =1; + +``` + +## 6.8 VAD hangover addition + +This subclause finally sets the vad decision for the current frame to be processed. + +``` + +IF ( vvad == 1 ) THEN burstcount = add( burstcount, 1 ); +ELSE burstcount = 0; + +IF ( burstcount >= 3 ) THEN +| hangcount = 5; +| burstcount = 3; + +vad = vvad; +IF ( hangcount >= 0 ) THEN +| vad = 1; + +``` + +``` +| hangcount = sub( hangcount, 1 ); +``` + +## 6.9 Periodicity updating + +This subclause must be delayed until the LTP lags are computed by the RPE-LTP algorithm. The LTP lags called Nc in the speech encoder are renamed lags[0..3] (index 0 for the first sub- segment of the frame, 1 for the second and so on). + +### Loop on sub-segments for the frame: + +``` +lagcount = 0; + +|= FOR i = 0 to 3: +|= Search the maximum and minimum of consecutive lags. +|= IF ( oldlag > lags[i] ) THEN +|= | minlag = lags[i]; +|= | maxlag = oldlag; +|= ELSE +|= | minlag = oldlag; +|= | maxlag = lags[i] ; +|= +|= Compute smallag (modulo operation not defined ): +|= +|= smallag = maxlag; +|== | FOR j = 0 to 2: +|== | IF (smallag >= minlag) THEN smallag =sub( smallag, minlag); +|== | NEXT j; +|= +|= Minimum of smallag and minlag - smallag: +|= +|= temp = sub( minlag, smallag ); +|= IF ( temp < smallag ) THEN smallag = temp; +|= IF ( smallag < 2 ) THEN lagcount = add( lagcount, 1 ); +|= Save the current LTP lag. +|= oldlag = lags[i]; +|= NEXT i: +``` + +### Update the veryoldlagcount and oldlagcount: + +``` +veryoldlagcount = oldlagcount; +oldlagcount = lagcount; +``` + +## 6.10 Tone detection + +This subclause computes the tone variable needed for the threshold adaptation. Tone is only calculated for the VAD in the downlink. In the uplink VAD tone=0. + +To reduce delay, this subclause should be calculated after the processing of the current speech encoder frame. + +### 6.10.1 Windowing + +This subclause applies a Hanning window to the input frame sof[0..159] to form the output frame sofh[0..159]. The input frame is the current offset compensated signal frame calculated in the RPE-LTP codec. The array of constants hann[i] is defined in table 3.2. + +#### Multiply signal frame by Hanning window : + +``` +|== FOR i = 0 to 79: +| sofh[i] = mult_r( sof[i], hann[i] ); +| sofh[159-i] = mult_r( sof[159-i], hann[i] ); +|== NEXT i; +``` + +### 6.10.2 Auto-correlation + +This subclause computes the auto-correlation vector L\_acfh[0..5] from the windowed input frame sofh[0..159]. The input frame must be scaled in order to avoid an overflow situation. This subclause is identical to the one used in the RPE-LTP algorithm, with the exception that only five auto-correlation values are calculated. + +#### Dynamic scaling of the array sofh[0..159]: + +#### Search for the maximum : + +``` +smax = 0; + +|== FOR k = 0 to 159: +| temp = abs( sofh[k] ); +| IF ( temp > smax ) THEN smax = temp; +|== NEXT k; +``` + +#### Computation of the scaling factor : + +``` +IF ( smax == 0 ) THEN scalauto = 0; +ELSE scalauto = sub( 4, norm( smax << 16) ); +``` + +#### Scaling of the array sofh[0..159]: + +``` +IF ( scalauto > 0 ) THEN + | temp = 16384 >> sub( scalauto,1); + |== FOR k = 0 to 159: + | sofh[k] = mult_r( sofh[k], temp); + |== NEXT k; +``` + +#### Compute the L\_ACF[..]: + +``` +|== FOR k=0 to 4: +| L_acfh[k] = 0; +|=== FOR i=k to 159: +| L_temp = L_mult( sofh[i], sofh[i-k] ); +| L_acfh[k] = L_add( L_acfh[k], L_temp ); +|=== NEXT i: +|== NEXT k: +``` + +### 6.10.3 Computation of the reflection coefficients + +This subclause calculates the reflection coefficients rc[1..4] from the input array L\_acfh[0..4]. This procedure is identical to the one in subclause 3.3.1 and the RPE-LTP codec, with the exception that only four reflection coefficients are calculated. + +#### Schur recursion with 16 bits arithmetic : + +``` +IF( L_acfh[0] == 0 ) THEN + |== FOR i = 1 to 4: + | rc[i] = 0; + |== NEXT i: + | EXIT; /continue with subclause 3.10.4/ +temp = norm( L_acfh[0] ); +|== FOR k=0 to 4: +| sacf[k] = ( L_acfh[k] << temp ) >> 16; +|== NEXT k: +``` + +#### Initialize array P[..] and K[..] for the recursion : + +``` +|== FOR i=1 to 3: +| K[5-i] = sacf[i]; +|== NEXT i: + +|== FOR i=0 to 4: +| P[i] = sacf[i]; +|== NEXT i: +``` + +#### Compute reflection coefficients : + +``` +|== FOR n=1 to 4: +| IF( P[0] < abs( P[1] ) ) THEN +| |== FOR i = n to 4: +| | rc[i] = 0; +| |== NEXT i: +| | EXIT; /continue with subclause 3.10.4/ +| rc[n] = div( abs( P[1] ), P[0] ); +| IF ( P[1] > 0 ) THEN rc[n] = sub( 0, rc[n] ); +| IF ( n == 4 ) THEN EXIT; /continue with subclause 3.10.4/ +``` + +``` + +| +| Schur recursion : +| +| P[0] = add( P[0], mult_r( P[1], rc[n] ) ); +|==== FOR m=1 to 4-n: +| P[m] = add( P[m+1], mult_r( K[5-m], rc[n] ) ); +| K[5-m] = add( K[5-m], mult_r( P[m+1], rc[n] ) ); +|==== NEXT m: +| +|== NEXT n: + +``` + +### 6.10.4 Filter coefficient calculation + +This subclause calculates the direct form filter coefficients a[1..2] from the reflection coefficients rc[1..4]. + +#### Step-up procedure to obtain the a[1..2]: + +``` + +temp = rc[1] >> 2; +a[1] = add( temp, mult_r( rc[2], temp ) ); +a[2] = rc[2] >> 2; + +``` + +### 6.10.5 Pole Frequency Test + +This subclause uses the direct form filter coefficients a[1..2] to determine the pole frequency of the second order LPC analysis. If the pole frequency is less than 385 Hz tone is set to 0 and clause 3 terminates. + +``` + +L_den = L_mult ( a[1], a[1] ); + +L_temp = a[2] << 16; +L_num = L_sub ( L_temp, L_den ); + +``` + +#### If pole is not complex then exit : + +``` + +IF ( L_num <= 0 ) THEN +| tone = 0; +| EXIT; /clause 3 complete/ + +``` + +#### If pole frequency is less than 385 Hz then exit : + +``` + +IF ( a[1] < 0 ) THEN +| temp = L_den >> 16; +| L_den = L_mult ( temp, 3189 ); +| L_temp = L_sub ( L_num, L_den ); +| IF ( L_temp < 0 ) THEN +| | tone = 0; +| | EXIT; /clause 3 complete/ + +``` + +### 6.10.6 Prediction gain test + +This subclause uses the reflection coefficients rc[1..4] to calculate the prediction gain. If the prediction gain is greater than 13,5 dB then tone is set to 1 otherwise tone is set to 0. + +#### Calculate normalized prediction error : + +``` + +prederr = 32767; + +|== FOR i=1 to 4 +| temp = mult ( rc[i], rc[i] ); +| temp = sub ( 32767, temp ); +| prederr = mult( prederr, temp ); +|== NEXT i; + +``` + +#### Test if prediction error is smaller than threshold : + +``` + +temp = sub ( prederr, 1464 ); + +IF ( temp < 0 ) THEN tone = 1; +ELSE tone = 0; + +``` + +**Table 3.2: Values of the Hanning window array hann[i]** + +| i | hann | i | hann | i | hann | i | hann | +|----|------|----|-------|----|-------|----|-------| +| 0 | 0 | 20 | 4856 | 40 | 16545 | 60 | 28139 | +| 1 | 12 | 21 | 5325 | 41 | 17192 | 61 | 28581 | +| 2 | 51 | 22 | 5811 | 42 | 17838 | 62 | 29003 | +| 3 | 114 | 23 | 6314 | 43 | 18482 | 63 | 29406 | +| 4 | 204 | 24 | 6832 | 44 | 19122 | 64 | 29789 | +| 5 | 318 | 25 | 7365 | 45 | 19758 | 65 | 30151 | +| 6 | 458 | 26 | 7913 | 46 | 20389 | 66 | 30491 | +| 7 | 622 | 27 | 8473 | 47 | 21014 | 67 | 30809 | +| 8 | 811 | 28 | 9046 | 48 | 21631 | 68 | 31105 | +| 9 | 1025 | 29 | 9631 | 49 | 22240 | 69 | 31377 | +| 10 | 1262 | 30 | 10226 | 50 | 22840 | 70 | 31626 | +| 11 | 1523 | 31 | 10831 | 51 | 23430 | 71 | 31852 | +| 12 | 1807 | 32 | 11444 | 52 | 24009 | 72 | 32053 | +| 13 | 2114 | 33 | 12065 | 53 | 24575 | 73 | 32230 | +| 14 | 2444 | 34 | 12693 | 54 | 25130 | 74 | 32382 | +| 15 | 2795 | 35 | 13326 | 55 | 25670 | 75 | 32509 | +| 16 | 3167 | 36 | 13964 | 56 | 26196 | 76 | 32611 | +| 17 | 3560 | 37 | 14607 | 57 | 26707 | 77 | 32688 | +| 18 | 3972 | 38 | 15251 | 58 | 27201 | 78 | 32739 | +| 19 | 4405 | 39 | 15898 | 59 | 27679 | 79 | 32764 | + +# 7 Digital test sequences + +This clause provides information on the digital test sequences that have been designed to help the verification of implementations of the Voice Activity Detector. Copies of these sequences are available (see clause A.2). + +## 7.1 Test configuration + +The VAD must be tested in conjunction with the speech encoder defined in GSM 06.10. The test configuration is shown in figure 4.1. The input signal to the speech encoder is the sop[...] signal as defined in GSM 06.10 table 5.1. The relevant parameters produced by the speech encoder are input to the VAD algorithm to produce the VAD output. This output has to be checked against some reference files. + +The file format of the encoder output parameters given in GSM 06.10 table 5.1 is extended to carry the VAD information. + +The VAD information is placed in the unused bit 15 (MSB) of the first encoded parameter: + +``` +LAR(1): bit 15 = 1 if VAD on + bit 15 = 0 if VAD Off +``` + +Furthermore, in order to facilitate approval testing over the air interface, the SP flag generated by the TX DTX handler (see GSM 06.31) on the basis of the VAD flag is placed in the MSB position of the second encoded parameter: + +``` +LAR(2): bit 15 = 1 if SP on + bit 15 = 0 if SP off +``` + +The output file will also contain the SID codeword and the comfort noise parameters as described in GSM 06.12 and GSM 06.31. + +![Block diagram of VAD test configuration showing RPE-LTP encoder, VAD under test, and TX DTX handler components and their connections.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The diagram illustrates the VAD test configuration. It consists of three main components: an RPE-LTP encoder, a VAD under test, and a TX DTX handler. The RPE-LTP encoder receives a 13 bit PCM input and a Reset signal. It is also connected to an 8kHz clock. The encoder outputs 260 bits to the TX DTX handler. The VAD under test receives the same Reset signal and outputs a 1 bit VAD flag to the TX DTX handler. The TX DTX handler contains internal components labeled TX, DTX, and handler. It outputs a 260 bit SID or speech signal and a 1 bit SP flag. A COMPARISON block is shown between the TX DTX handler and the output signals. + +Block diagram of VAD test configuration showing RPE-LTP encoder, VAD under test, and TX DTX handler components and their connections. + +Figure 4.1: VAD test configuration + +## 7.2 Test sequences + +The test sequences are described in detail in clause A.2. + +# Annex A (informative): + +## A.1 Simplified block filtering operation + +Consider an 8th order transversal filter with filter coefficients $a_0..a_8$ , through which a signal is being passed, the output of the filter being: + +$$s'(n) = -\sum_{i=0}^8 a_i s(n-i) \quad (1)$$ + +If we apply block filtering over 20 ms segments, then this equation becomes: + +$$s'(n) = -\sum_{i=0}^8 a_i s(n-i) \quad ; 0 \leq n-i \leq 159 \quad ; 0 \leq n \leq 167 \quad (2)$$ + +If the energy of the filtered signal is then obtained for every 20 ms segment, the equation for this is: + +$$P_{vad} = \sum_{n=0}^{167} \left\{ -\sum_{i=0}^8 a_i s(n-i) \right\}^2 \quad ; 0 \leq n-i \leq 159 \quad (3)$$ + +We know that (see GSM 06.10, subclause 3.1.4): + +$$acf_i = \sum_{n=0}^{159} s_n s_{n-i} \quad ; 0 \leq n-i \leq 159 \quad ; i = 0..8 \quad (4)$$ + +If equation (3) is expanded and $acf_0..acf_8$ are substituted for $s_n$ then we arrive at the equations: + +$$P_{vad} = r_0 acf_0 + 2 \sum_{i=1}^8 r_i acf_i \quad (5)$$ + +Where: + +$$r_i = \sum_{k=0}^{8-i} a_k a_{k+i} \quad ; i = 0..8 \quad (6)$$ + +## A.2 Description of digital test sequences + +### A.2.1 Test sequences + +The VAD algorithm uses results from the full rate speech encoder defined in GSM 06.10. In the testing of the VAD, it is assumed that the relevant speech encoder functions have been verified by the test sequences defined in GSM 06.10. + +The five types of input sequences are briefly described below. + +Spectral comparison + +The two kinds of statements of the spectral comparison algorithm (subclause 3.4), arithmetic statements and control statements, are tested by separate test sequences. + +Arithmetic statements: + +spec\_a1.\* +spec\_a2.\* + +Control statements + +spec\_c1.\* +spec\_c2.\* +spec\_c3.\* +spec\_c4.\* + +#### Threshold adaptation + +There are two types of tests to verify the threshold adaptation described in subclause 3.6: + +adapt\_i1.\* +adapt\_i2.\* + +The initial test sequences test the acf0 and VAD decision. A fault in the VAD decision will cause all the other sequences to fail, so it is recommended that this test is run before all other tests. + +adapt\_m1.\* +adapt\_m2.\* + +The main test sequences will check the basic threshold adaptation mechanism. + +#### Periodicity detection + +pitch1.\* +pitch2.\* + +These sequences check the periodicity detection algorithm described in subclause 3.5. + +#### Tone detection + +The tone detector test sequences are only required for downlink VAD implementations. There are three types of test to verify the tone detection algorithm described in subclause 3.10. The first test sequence tests the operation of the tone detector by means of a frequency sweep: + +freq\_sw.\* + +The following test sequences test the prediction gain calculation within the tone detector: + +pred1.\* +pred2.\* + +The following sequences test the second order pole frequency calculation within the tone detector: + +pole1.\* +pole2.\* + +"Safety" and initialization + +safety.\* + +This sequence checks that safety tests have been implemented to prevent zero values being passed to the norm function. It checks the functions described in the Adaptive Filtering and Energy Computation subclause (subclause 3.1), and the Predictor Values Computation (subclause 3.3). This sequence also checks the initialization of thvad and the rvad array. + +#### Real speech + +good\_sp.\* + +bad\_sp.\* + +Because the test sequences cannot be guaranteed to find every possible error, there is a small possibility that an implementation of the correct output for test sequences, but fail with real speech. Because of this, an extra set of sequences are included that consist of barely detectable speech and very clean speech. + +There are 3 different file extensions: + +\*.inp: speech encoder input sequences, binary files + +\*.vad: output flag of the VAD algorithm, ASCII files + +\*.cod: TX DTX handler output sequences, binary files for comparison with VAD/DTX handler output. + +The \*.cod files contain speech coder output information in the format described in clause 4. + +It should be noted that there is no requirement in GSM 06.12 for a bit exact implementation of the averaging procedure to calculate the "LAR" and "xmax" parameters in the SID frames. Different implementations are allowed. + +The algorithms used for the calculation of the LAR and xmax parameters of the SID frames are therefore reproduced below: + +#### **LAR averaging:** + +``` + +| FOR i = 1 to 8: +| L_Temp = 2; /* const. for rounding*/ +| | FOR n = 1 to 4: +| | L_Temp1 = LAR[j-n](i); /*conversion 16 --> 32 bit*/ +| | L_Temp = L_Add( L_Temp , L_Temp1 ); +| | NEXT n +| L_Temp = L_Temp >> 2; +| mean (LAR(i)) = L_Temp; /*conversion 32 --> 16 bit*/ +| NEXT i; + +``` + +#### **xmax averaging** + +``` + +L_Temp = 8; /* const. for rounding*/ + +| FOR n = 1 to 4: +| | FOR i = 1 to 4: +| | L_Temp1 = xmax[j-n](i); /*conversion 16 --> 32 bit*/ +| | L_Temp = L_Add( L_Temp , L_Temp1 ); +| | NEXT i +| NEXT n + +L_Temp = L_Temp >> 4; + +mean (xmax) = L_Temp; /*conversion 32 --> 16 bit*/ + +``` + +### **A.2.2 File format description** + +All the \*.inp and \*.cod files are written in binary using 16 bit words, while all \*.vad files are written in ASCII format. The sizes of the files are shown in table A.2.1, A.2.2 and A.2.3. The detailed format of the \*.inp and \*.cod files is in accordance with the descriptions given in GSM 06.10 clause 5. + +**Table A.2.1: File sizes for \*.inp extension files** + +| File: | Frames: | Size in bytes: | +|--------------|----------------|-----------------------| +| spec_a1.inp | 22 | 7 040 | +| spec_a2.inp | 22 | 7 040 | +| spec_c1.inp | 48 | 15 360 | +| spec_c2.inp | 48 | 15 360 | +| spec_c3.inp | 48 | 15 360 | +| spec_c4.inp | 48 | 15 360 | +| adapt_i1.inp | 67 | 21 440 | +| adapt_i2.inp | 48 | 15 360 | +| adapt_m1.inp | 403 | 128 960 | +| adapt_m2.inp | 376 | 120 320 | +| pitch1.inp | 35 | 11 200 | +| pitch2.inp | 35 | 11 200 | +| freq_sw.inp | 560 | 179 200 | +| pred1.inp | 126 | 40 320 | +| pred2.inp | 126 | 40 320 | +| pole1.inp | 97 | 31 040 | +| pole2.inp | 42 | 13 440 | +| safety.inp | 5 | 16 00 | +| good_sp.inp | 312 | 99 840 | +| bad_sp.inp | 312 | 99 840 | + +**Table A.2.2: File sizes for \*.cod extension files** + +| File: | Frames: | Size in bytes: | +|--------------|----------------|-----------------------| +| spec_a1.cod | 22 | 3 344 | +| spec_a2.cod | 22 | 3 344 | +| spec_c1.cod | 48 | 7 296 | +| spec_c2.cod | 48 | 7 296 | +| spec_c3.cod | 48 | 7 296 | +| spec_c4.cod | 48 | 7 296 | +| adapt_i1.cod | 67 | 10 184 | +| adapt_i2.cod | 48 | 7 296 | +| adapt_m1.cod | 403 | 61 256 | +| adapt_m2.cod | 376 | 57 152 | +| pitch1.cod | 35 | 5 320 | +| pitch2.cod | 35 | 5 320 | +| freq_sw.cod | 560 | 85 120 | +| pred1.cod | 126 | 19 152 | +| pred2.cod | 126 | 19 152 | +| pole1.cod | 97 | 14 744 | +| pole2.cod | 42 | 6 384 | +| safety.cod | 5 | 760 | +| good_sp.cod | 312 | 47 424 | +| bad_sp.cod | 312 | 47 424 | + +**Table A.2.3: File sizes for \*.vad extension files** + +| File: | Frames: | Size in bytes: | +|--------------|---------|----------------| +| spec_a1.vad | 22 | 88 | +| spec_a2.vad | 22 | 88 | +| spec_c1.vad | 48 | 192 | +| spec_c2.vad | 48 | 192 | +| spec_c3.vad | 48 | 192 | +| spec_c4.vad | 48 | 192 | +| adapt_i1.vad | 67 | 268 | +| adapt_i2.vad | 48 | 192 | +| adapt_m1.vad | 403 | 1 612 | +| adapt_m2.vad | 376 | 1504 | +| pitch1.vad | 35 | 140 | +| pitch2.vad | 35 | 140 | +| freq_sw.inp | 560 | 2 240 | +| pred1.vad | 126 | 504 | +| pred2.vad | 126 | 504 | +| pole1.vad | 97 | 388 | +| pole2.vad | 42 | 168 | +| safety.vad | 5 | 20 | +| good_sp.vad | 312 | 1 248 | +| bad_sp.vad | 312 | 1 248 | + +## A.3 VAD performance + +In optimizing a VAD a difficult trade-off has to be made between speech clipping which reduces the subjective performance of the system, and the average activity factor. The benefit of DTX is increased as the average activity factor is reduced. However, in general, a reduction of the activity will be associated with a greater risk for audible speech clipping. + +In the optimization process, great emphasis has been placed on avoiding unnecessary speech clipping. However, it has been found that a VAD with virtually no audible clipping would result in a very high activity and very little DTX advantage. + +The VAD specified in this technical specification introduces audible and possibly objectionable clipping in certain cases, mainly with low input levels. However, a comprehensive evaluation programme consisting of about 600 individual conversations conducted in a wide range of realistic conditions, it was found that about 90% of the conversations were free from objectionable clipping. + +The voice activity performance of the VAD is summarized in table A.3.1. The activity figures are averages of a large number of conversations covering factors like different talkers, noise characteristics and locations. It should be noted that the actual activity of a particular talker in a specific conversation may vary considerably relative to the averages given. This is due both to the variation in talker behaviour as well as to the level dependency of the VAD (the channel activity has been found to decrease by about 0,5 points of percentage per dB level reduction). However, as mentioned above, a decreased speech input level increases the risk of objectionable speech clipping. + +All the values given are activity figures, i.e. the % of time the radio channel has to be on. + +**Table A.3.1: Summary of channel activity** + +| Telephone instrument | Situation | Typical channel activity factor: | +|----------------------|----------------------------------------------------------|----------------------------------| +| Handset | Quiet location | 55% | +| Handset | Moderate office noise with voice interference | 60% | +| Handset | Strong voice interference (e.g. airport/railway station) | 65-70% | +| Handsfree/handset | Variable vehicle noise | 60% | + +## A.4 Pole frequency calculation + +This annex describes the algorithm used to determine whether the pole frequency for a second order analysis of the signal frame is less than 385 Hz. + +The filter coefficients for a second order synthesis filter are calculated from the first two unquantized reflection coefficients $rc[1..2]$ obtained from the speech encoder. This is done using the routine described in subclause 3.10.4. If the filter coefficients $a[0..2]$ are defined such that the synthesis filter response is given by: + +$$H(z) = 1 / (a[0] + a[1]z^{-1} + a[2]z^{-2}) \quad (1)$$ + +Then the positions of the poles in the Z-plane are given by the solutions to the following quadratic: + +$$a[0]z^2 + a[1]z + a[2] = 0, \quad a[0] = 1 \quad (2)$$ + +The positions of the poles, $z$ , are therefore: + +$$z = re \pm j \cdot \text{sqr}(im), \quad j^2 = -1 \quad (3)$$ + +where: + +$$re = -a[1] / 2 \quad (4)$$ + +$$im = (4 \cdot a[2] - a[1]^2) / 4 \quad (5)$$ + +If $im$ is negative then the poles lie on the real axis of the Z-plane and the signal is not a tone and the algorithm terminates. If $re$ is negative then the poles lie in the left hand side of the Z-plane and the frequency is greater than 2 000 Hz and the prediction error test can be performed. + +If $im$ is positive and $re$ is positive then the poles are complex and lie in the right hand side of the Z-plane and the frequency in Hz is related to $re$ and $im$ by the expression: + +$$\text{freq} = \arctan(\text{sqr}(im)/re) \cdot 4000 / \pi \quad (6)$$ + +Having ensured that both $im$ and $re$ are positive, the test for a dominant frequency less than 385 Hz can be derived by substituting Equations 4 and 5 into Equation 6 and re-arranging: + +$$(4 \cdot a[2] - a[1]^2) / a[1]^2 < (\tan(\pi \cdot 385 / 4000))^2 \quad (7)$$ + +or + +$$(4 \cdot a[2] - a[1]^2) / a[1]^2 < 0.0973 \quad (8)$$ + +If this test is true then the signal is not a tone and the algorithm terminates, otherwise the prediction error test is performed. + +# --- Annex B (normative): Test sequences + +The test vectors are described in the present document are supplied in archive en\_300965v080000p0.zip which accompanies the present document. The files contained in this archive are listed in clause A.2. + +The full rate test vectors apply to both GSM Phase 1 and Phase 2. However, the files pole1.\* pole2.\* pred1.\* pred2.\* and freq\_sw.\* are not required for Phase 1 (uplink and downlink) and Phase 2 uplink implementations. + +# Annex C (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#09 | | | | 4.0.5 | ETSI Publication | +| SMG#17 | | | | 4.2.1 | ETSI Publication | +| SMG#23 | | | | 4.3.1 | ETSI Publication | +| SMG#23 | | | | 5.0.3 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46041/raw.md b/marked/Rel-18/46_series/46041/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dd6c916be41f438cb996be792d69712f9b328803 --- /dev/null +++ b/marked/Rel-18/46_series/46041/raw.md @@ -0,0 +1,425 @@ + + +# 3GPP TS 46.041 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +### **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|---------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 General Organisation..... | 7 | +| 5 Transmit (TX) side..... | 8 | +| 5.1 General Operation ..... | 8 | +| 5.1.1 Functions of the TX DTX handler..... | 8 | +| 5.1.2 Functions of the TX radio subsystem..... | 9 | +| 6 Receive (RX) side ..... | 11 | +| 6.1 General operation ..... | 11 | +| 6.1.1 Functions of the RX radio subsystem..... | 11 | +| 6.1.2 Functions of the RX DTX handler ..... | 12 | +| Annex A (informative): Change history..... | 13 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document is a GSM technical specification version 7 and is part of the 1998 release of the GSM Technical Specifications. The present document is part of a series covering the half rate speech traffic channels as described below: + +- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". +- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".** + +GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". + +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 gives a description of the general baseband operation of half rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX). + +For clarity, the description is structured according to the block diagrams in figures 1 and 4. Except in the case described below, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same. + +In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX Handlers and the Radio Sub System (RSS) as described in the present document together with all their flags is mandatory, being a part of the A-bis interface as described in GSM 08.61 [10]. + +The DTX functions described in the present document are mandatory for implementation in all GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used. + +# 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] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 04.08: "Digital cellular telecommunication system (Phase 2+); Mobile radio interface layer 3 specification". +- [3] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". +- [4] GSM 05.08: "Digital cellular telecommunication system (Phase 2+); Radio subsystem link control". +- [5] GSM 06.02: "Digital cellular telecommunications system (Phase 2+); Half rate speech Part 1: Half rate speech processing functions". +- [6] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- [7] GSM 06.21: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- [8] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- [9] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". + +- [10] GSM 08.61: "Digital cellular telecommunications system (Phase 2+); Inband control of remote transcoders and rate adaptors for half rate traffic channels". +- [11] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech Part 7: ANSI-C code for the GSM half rate speech codec". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**accepted SID frame:** traffic frame which is flagged with SID= "1" or SID= "2" by the Radio Subsystem. + +**bad traffic frame:** traffic frame flagged BFI= "1" (Bad Frame Indication) or with UFI= "1" (Unreliable Frame Indication) by the Radio Subsystem. + +**frame:** time interval of 20 ms corresponding to the time segmentation of the half rate speech transcoder defined in GSM 06.20 (ETS 300 969) [6], also used as a short term for a traffic frame. + +**good speech frame:** good traffic frame which is not an accepted SID frame. + +**good traffic frame:** traffic frame flagged BFI= "0" and UFI= "0" by the Radio Subsystem. + +**GS averaging period:** period in which the quantized energy tweak parameters GS are averaged: it corresponds to the hangover period. + +**hangover period:** period of 7 frames added at the end of a speech burst in which VAD flag= "0" and SP flag= "1". + +**invalid SID frame:** accepted SID frame which was not classified as valid SID frame. This frame is not valid for updating comfort noise parameters, but the frame conveys information that comfort noise generations should be started or continued. + +**lost SID frame:** unusable frame received when the RX DTX Handler is generating comfort noise and a SID frame is expected (Time Alignment Flag TAF= "1"). + +**lost speech frame:** unusable frame received when the RX DTX Handler is passing on traffic frames directly to the speech decoder. + +**SID code word:** fixed bit pattern defined in GSM 06.22 [8], for labelling a traffic frame as a SID frame. + +**SID field:** bit positions defined in GSM 06.22 [8], of the SID codeword within a SID frame. + +**SID frame:** frame characterised by the SID (Silence Descriptor) code word. It conveys information on the acoustic background noise. + +**SP flag:** boolean flag, generated by the TX DTX handler, indicating the presence of a speech frame ("1") or the presence of a SID frame ("0"). + +**speech frame:** traffic frame that cannot be classified as a SID frame. + +**traffic frame:** block of 112 information bits transmitted on the half rate speech traffic channel. + +**unusable frame:** bad traffic frame that is not an accepted SID frame. + +**VAD flag:** boolean flag, generated by the VAD algorithm defined in GSM 06.42 [9], indicating the presence ("1") or the absence ("0") of a speech frame. + +**valid SID frame:** good traffic frame flagged with SID= "2" by the Radio Subsystem. This frame is valid for updating comfort noise parameters at any time. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------|-----------------------------------------------------------| +| GS | Energy tweak parameter | +| N elapsed | Number of elapsed frames since the last updated SID frame | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------------| +| BFI | Bad Frame Indicator | +| BSC | Base Station Controller | +| BSS | Base Station System | +| DTX | Discontinuous Transmission | +| FACCH | Fast Associated Control CHannel | +| FEC | Forward Error Correction | +| GSM | Global System for Mobile communications | +| MS | Mobile Station | +| RSS | Radio Sub System | +| RX | Receive | +| SACCH | Slow Associated Control CHannel | +| SID | SIlence Descriptor | +| TAF | Time Alignment Flag | +| TX | Transmit | +| UFI | Unreliable Frame Indicator | +| VAD | Voice Activity Detector | + +For abbreviations not given in this clause, see GSM 01.04 [1]. + +# --- 4 General + +DTX is a mechanism which allows the radio transmitter to be switched off most of the time during speech pauses for the following two purposes: + +- to save power in the MS; +- to reduce the overall interference level over the air interface. + +DTX shall be in operation in GSM MS if commanded so by the network, see GSM 04.08 [2]. + +## 4.1 General Organisation + +The overall DTX mechanism described in the present document requires the following functions: + +- a Voice Activity Detector (VAD) on the transmit (TX) side; +- evaluation of the background acoustic noise on the TX side, in order to TX characteristic parameters to the receive (RX) side; +- generation on the RX side of a similar noise, called comfort noise, during periods where the radio transmission is switched off. + +The VAD is defined in GSM 06.42 [9], the comfort noise functions in GSM 06.22 [8]. Both are based partly on the speech transcoder and its internal variables, defined in GSM 06.20 [6]. + +In addition to these functions, if the parameters arriving at the (RX) side are detected to be corrupted by errors, the speech or comfort noise shall be generated from substituted data in order to avoid sound defects for the listener. This function is defined in GSM 06.21 [7]. + +An overall description of the speech processing parts can be found in GSM 06.02 [5]. + +# 5 Transmit (TX) side + +A block diagram of the TX side DTX functions is shown in figure 1. + +![Block diagram of the transmit side DTX functions. The TX DTX handler contains three sub-blocks: Speech encoder, Voice Activity Detector, and Comfort Noise Computation. The TX radio subsystem contains two sub-blocks: Channel Encoding and SP flag monitoring. Arrows show data flow: Information bits (112) from Speech encoder to Channel Encoding, and SP flag (1) from Voice Activity Detector to SP flag monitoring.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +``` + +graph LR + subgraph TX_DTX_handler [TX DTX handler] + SE[Speech encoder] + VAD[Voice Activity Detector] + CNC[Comfort Noise Computation] + end + subgraph TX_radio_subsystem [TX radio subsystem] + CE[Channel Encoding] + SFM[SP flag monitoring] + end + SE -- "Information bits 112" --> CE + VAD -- "SP flag 1" --> SFM + +``` + +Block diagram of the transmit side DTX functions. The TX DTX handler contains three sub-blocks: Speech encoder, Voice Activity Detector, and Comfort Noise Computation. The TX radio subsystem contains two sub-blocks: Channel Encoding and SP flag monitoring. Arrows show data flow: Information bits (112) from Speech encoder to Channel Encoding, and SP flag (1) from Voice Activity Detector to SP flag monitoring. + +Figure 1: Block diagram of the transmit side DTX functions + +## 5.1 General Operation + +The TX DTX handler continuously passes traffic frames, individually marked by the SP flag, to the RSS. This binary flag is redundant to the Silence Descriptor (SID) code word labelling. SP flag = "1" indicates a speech frame, SP flag = "0" a SID frame. + +The scheduling of the frames for transmission on the air interface is controlled by the RSS alone, on the basis of the SP flag as described in clause 5.1.1. + +### 5.1.1 Functions of the TX DTX handler + +To allow verification of the TX DTX handler functions, all frames before the reset of the system are treated as if they were speech frames of an infinitely long time. Therefore, the first 7 frames after the reset are marked with SP flag = "1", even if VAD flag = "0" (hangover period, see figure 2). + +The VAD shall operate all the time in order to assess whether the input signal contains speech or not. The output is a binary flag (VAD flag = "1" or VAD flag = "0", respectively) on a frame by frame basis (see GSM 06.42 [9]). + +The VAD flag controls indirectly, via the TX DTX handler operations described below, the overall DTX operation on the TX side. + +Whenever the VAD flag = "1", the speech encoder output frame shall be passed directly to the RSS, marked with SP flag = "1". + +At the end of a speech burst (transition VAD flag = "1" to VAD flag = "0"), it takes 8 consecutive frames to make a new updated SID frame available (see GSM 06.22 [8]). Normally, the first 7 speech encoder output frames after the end of the speech burst shall therefore be passed directly to the RSS, marked with SP flag = "1" ("hangover period"). The first new SID frame is then passed to the RSS as frame 8 after the end of the speech burst, marked with SP flag = "0" (see figure 2). + +![Figure 2: Normal hangover procedure (N_elapsed > 23). A timing diagram showing VAD Flag, SP Flag, and frame sequence. The VAD Flag drops from 1 to 0 at the 'end of speech burst'. The SP Flag remains 1 for a 'hangover (GS averaging period)' of 7 frames after the VAD Flag drops. The frame sequence shows N_elapsed values from 35 to 45, then resetting to 0. Frames are labeled 'Speech' during the hangover and 'SID k+1', 'SID k+2' afterwards. SID averaging periods are shown spanning the last 8 speech frames.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the timing relationship between the Voice Activity Detection (VAD) flag, the Scheduling Priority (SP) flag, and the transmitted frames. + - **VAD Flag:** Transitions from high to low at the end of a speech burst. Key points: last "speech" frame, end of speech burst, first "pause" frame. + - **SP Flag:** Stays high for a hangover period (GS averaging period) after the VAD flag goes low. + - **Frame Sequence:** Shows $N_{elapsed}$ values (35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 0, 0, 0). Frames are marked as 'Speech' until the end of the hangover, then 'SID k+1' and 'SID k+2' follow. + - **SID averaging periods:** Indicated as averaging periods of R0 and LPC coefficients, spanning the last 8 frames marked as speech before the first SID frame. + +Figure 2: Normal hangover procedure (N\_elapsed > 23). A timing diagram showing VAD Flag, SP Flag, and frame sequence. The VAD Flag drops from 1 to 0 at the 'end of speech burst'. The SP Flag remains 1 for a 'hangover (GS averaging period)' of 7 frames after the VAD Flag drops. The frame sequence shows N\_elapsed values from 35 to 45, then resetting to 0. Frames are labeled 'Speech' during the hangover and 'SID k+1', 'SID k+2' afterwards. SID averaging periods are shown spanning the last 8 speech frames. + +**Figure 2: Normal hangover procedure ( $N_{elapsed} > 23$ )** + +If, however, at the end of the speech burst, less than 24 frames have elapsed since the last SID frame was computed and passed to the RSS, then this last SID frame shall repeatedly be passed to the RSS, until a new updated SID frame is available (8 consecutive frames marked with VAD flag = "0"). This reduces the activity on the air interface in cases where short background noise spikes are taken for speech, by avoiding the "hangover" waiting for the SID frame computation (see figure 3). + +NOTE: Figure 3 shows an example of the longest possible speech burst without hangover. + +Once the first SID frame after the end of a speech burst has been computed and passed to the RSS, the TX DTX Handler shall continuously compute and pass updated SID frames to the RSS, marked with SP flag = "0" as long as the VAD flag = "0". + +The speech encoder is operated in full speech modality if SP flag = "1" and in a simplified mode if SP flag = "0", because not all encoder functions are required for the evaluation of comfort noise parameters (see GSM 06.22 [8]). + +### 5.1.2 Functions of the TX radio subsystem + +The following traffic frames shall be scheduled for transmission: + +- all frames marked with SP flag = "1"; +- the first one with SP flag = "0" after one or more frames with SP flag = "1"; +- those marked with SP flag = "0" and aligned with the Slow Associated Control CHannel (SACCH) multiframe structure as described in GSM 05.08 [4]. + +This has the overall function, that the radio transmission is turned off after the transmission of a SID frame when the speaker stops talking. During speech pauses, the transmission is resumed at regular intervals for transmission of one SID frame, in order to update the generated comfort noise on the RX side (and to improve the measurement of the link quality by the RSS). + +If a SID frame (SP flag = "0"), scheduled for transmission is stolen for Fast Associated Control CHannel (FACCH) signalling purposes, then the subsequent frame shall be scheduled for transmission instead. + +![Timing diagram showing VAD and SP flags over frames, with SID averaging periods and updates for short speech bursts.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the handling of short speech bursts for $N_{\text{elapsed}} < 24$ . It shows two flags over a sequence of frames: + +- VAD Flag:** A binary flag that is high during a speech burst. An arrow labeled "end of speech burst" points to the falling edge of this flag at frame 23. +- SP Flag:** A binary flag that is high during a speech burst. It follows the VAD flag with some latency. +- Frames to RSS:** A row of cells representing the state of each frame. The cells contain: + - Frames 0 to 2: "Speech" + - Frames 3 to 7: "SID k" + - Frames 8 to 22: "Speech" + - Frames 23 to 29: "SID k" + - Frame 0 (next cycle): "SID k+1" +- SID averaging period:** Two horizontal bars indicate the averaging periods. + - The first period is from frame 0 to 7. An arrow points from the "SID k" cell at frame 0 to this period, and another arrow points from the period to the "repeat previous SID" label. + - The second period is from frame 23 to 29. An arrow points from the "SID k" cells in this period to the "repeat previous SID" label. +- new (updated) SID:** Two arrows point from the "SID k" cells at frames 28 and 29 to the "new (updated) SID" label, indicating the update of the SID value. + +A bracket at the top indicates a "Frame (20 ms)" duration between frame 28 and 29. + +Timing diagram showing VAD and SP flags over frames, with SID averaging periods and updates for short speech bursts. + +Figure 3: Handling of short speech bursts for $N_{\text{elapsed}} < 24$ (An example) + +# 6 Receive (RX) side + +A block diagram of the RX side DTX functions is shown in figure 4. + +![Block diagram of the receive side DTX functions. The diagram shows two main components: RX DTX handler and RX radio subsystem. The RX radio subsystem contains two blocks: Error Correction & Detection and SID frame detection. The Error Correction & Detection block outputs Information bits (112), BFI (1), UFI (1), SID (2), and TAF (1) to the RX DTX handler. The RX DTX handler contains three blocks: Speech decoder, Comfort Noise Generation, and Error Concealment. The Speech decoder receives the Information bits. The Comfort Noise Generation block receives the BFI, UFI, SID, and TAF flags. The Error Concealment block receives the SID and TAF flags.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Block diagram of the receive side DTX functions. The diagram shows two main components: RX DTX handler and RX radio subsystem. The RX radio subsystem contains two blocks: Error Correction & Detection and SID frame detection. The Error Correction & Detection block outputs Information bits (112), BFI (1), UFI (1), SID (2), and TAF (1) to the RX DTX handler. The RX DTX handler contains three blocks: Speech decoder, Comfort Noise Generation, and Error Concealment. The Speech decoder receives the Information bits. The Comfort Noise Generation block receives the BFI, UFI, SID, and TAF flags. The Error Concealment block receives the SID and TAF flags. + +Figure 4: Block diagram of the receive side DTX functions + +## 6.1 General operation + +Whatever their context (speech, SID, FACCH or none), the RSS continuously passes the received traffic frames to the RX DTX handler, individually marked by various pre-processing functions with 4 flags. These are the Bad Frame Indicator (BFI) flag, the Unreliable Frame Indicator (UFI) flag, the Silence Descriptor (SID) flag and the Time Alignment Flag (TAF) described in clause 6.1.1 and table 1, which serve to classify the traffic frame according to the list of terms defined in clause 3.1. This classification, summarised in table 1, allows the RX DTX handler to determine how the received frame is to be handled. + +Table 1 Classification of traffic frames + +| BFI "OR" UFI* | SID | | | +|---------------|-------------------|---|-------------------| +| | 2 | 1 | 0 | +| 0 | Valid SID frame | | Good speech frame | +| 1 | Invalid SID frame | | Unusable frame | + +\* BFI "OR" UFI indicates a logical OR combination of the BFI and UFI flags. + +NOTE: The SID computation is left open to manufacturers with the constraint to meet the performance requirements given in the GSM 05.05 [3]. An example solution is given in the C-code (GSM 06.06 [11]). + +### 6.1.1 Functions of the RX radio subsystem + +The binary BFI flag (see GSM 05.05 [3]) indicates whether the traffic frame is considered to contain meaningful information bits (BFI flag = "0") or not (BFI flag = "1"). In the context of the present document, a FACCH frame is considered not to contain meaningful bits and shall be marked with BFI flag = "1". The BFI flag shall fulfil the performance requirements of GSM 05.05 [3]. + +NOTE: That the BFI flag, which is generated by the channel error correction scheme, will in some cases be modified by the SID frame detection unit. + +The UFI flag is the output of the Forward Error Correction (FEC) procedure and give indications about the channel performance. The UFI flag shall fulfil the performance requirements of GSM 05.05 [3]. + +The SID frame detector compares bit by bit the relevant bits of the received traffic frame (the SID field) with the SID code word defined in GSM 06.22 [8] and gives back the ternary SID flag. The SID flag shall fulfil the performance requirements of GSM 05.05 [3]. The binary TAF flag marks with TAF = "1" those traffic frames that are aligned with the SACCH multiframe structure as described in GSM 05.08 [4]. + +### 6.1.2 Functions of the RX DTX handler + +The RX DTX handler shall be responsible for the overall DTX operation on the RX side. + +The DTX operation on the RX side shall be as follows: + +- whenever a good speech frame is detected, the DTX Handler shall pass it directly on to the speech decoder; +- when lost speech or lost SID frames are detected, the substitution and muting procedure defined in GSM 06.21 [7] shall be applied; +- valid SID frames shall result in comfort noise generation, as defined in GSM 06.22 [8], until the next SID frame is expected (TAF="1") or good speech frames are detected. During this period, the RX DTX handler shall ignore any unusable frames delivered by the RSS; +- an invalid SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied. + +NOTE: If the first SID frame after a speech burst (a series of good speech frames) is invalid, then the comfort noise parameters can be taken from the last valid SID frame or, if the series of good speech frames received was longer than 30 (23+7), from the last received good speech frame which, because of the VAD hangover time (see GSM 06.42 [9]), may be supposed to contain noise only. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#13 | | | | 4.0.2 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#23 | 430/97 | A001 | | 5.1.1 | UAP 60 | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46042/raw.md b/marked/Rel-18/46_series/46042/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c635ccf8dcc9c358458b3f5138a636a64e28b718 --- /dev/null +++ b/marked/Rel-18/46_series/46042/raw.md @@ -0,0 +1,668 @@ + + +# 3GPP TS 46.042 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|-------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Symbols..... | 6 | +| 3.2.1 Variables..... | 6 | +| 3.2.2 Constants ..... | 6 | +| 3.2.3 Functions ..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 5 Functional description..... | 7 | +| 5.1 Overview and principles of operation ..... | 8 | +| 5.2 Algorithm description ..... | 8 | +| 5.2.1 Adaptive filtering and energy computation ..... | 9 | +| 5.2.2 ACF averaging..... | 9 | +| 5.2.3 Predictor values computation ..... | 10 | +| 5.2.4 Spectral comparison ..... | 10 | +| 5.2.5 Information tone detection ..... | 11 | +| 5.2.6 Threshold adaptation ..... | 11 | +| 5.2.7 VAD decision ..... | 14 | +| 5.2.8 VAD hangover addition ..... | 14 | +| 5.2.9 Periodicity detection..... | 14 | +| 6 Computational description overview ..... | 15 | +| 6.1 VAD modules..... | 15 | +| 6.2 Pseudo-floating point arithmetic ..... | 15 | +| Annex A (informative): VAD performance ..... | 17 | +| Annex B (informative): Simplified block filtering operation..... | 18 | +| Annex C (informative): Pole frequency calculation..... | 19 | +| Annex D (informative): Change history..... | 20 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) within the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below: + +- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec". +- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". +- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". + +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 Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.41 [4]. It also specifies the test methods to be used to verify that a VAD implementation complies with the present document. + +The requirements are mandatory on any VAD to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the half-rate GSM speech traffic channel. + +# --- 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- [3] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- [4] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- [5] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI C code for the GSM half rate speech codec". +- [6] GSM 06.07: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**mobile environment:** any environment in which MSs may be used. + +**noise:** signal component resulting from acoustic environmental noise. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +### 3.2.1 Variables + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------| +| aav1 | filter predictor values, see clause 5.2.3 | +| acf | the ACF vector which is calculated in the speech encoder (GSM 06.20 [2]) | +| adaptcount | secondary hangover counter, see clause 5.2.6 | +| av0 | averaged ACF vector, see clause 5.2.2 | +| av1 | a previous value of av0, see clause 5.2.2 | +| burstcount | speech burst length counter, see clause 5.2.7 | +| den | denominator of left hand side of equation 8 in annex C, see clause 5.2.5 | +| difference | difference between consecutive values of dm, see clause 5.2.4 | +| dm | spectral distortion measure, see clause 5.2.4 | +| hangcount | primary hangover counter, see clause 5.2.7 | +| lagcount | number of subframes in current frame meeting periodicity criterion, see clause 5.2.9 | +| lastdm | previous value of dm, see clause 5.2.4 | +| lags | the open loop long term predictor lags for the four speech encoder subframes (GSM 06.20 [2].) | +| num | numerator of left hand side of equation 8 in annex C, see clause 5.2.5 | +| oldlagcount | previous value of lagcount, see clause 5.2.9 | +| prederr | fourth order short term prediction error, see clause 5.2.5 | +| ptch | Boolean flag indicating the presence of a periodic signal component, see clause 5.2.9 | +| pvad | energy in the current filtered signal frame, see clause 5.2.1 | +| rav1 | autocorrelation vector obtained from av1, see clause 5.2.3 | +| rc | the first four unquantized reflection coefficients calculated in the speech encoder (GSM 06.20 [2]) | +| rvad | autocorrelation vector of the adaptive filter predictor values, see clause 5.2.6 | +| smalllag | difference between consecutive lag values, see clause 5.2.9 | +| stat | Boolean flag indicating that the frequency spectrum of the input signal is stationary, see clause 5.2.4 | +| thvad | adaptive primary VAD threshold, see clause 5.2.6 | +| tone | Boolean flag indicating the presence of an information tone, see clause 5.2.5 | +| vadflag | Boolean VAD decision with hangover included, see clause 5.2.8 | +| veryoldlagcount | previous value of oldlagcount, see clause 5.2.9 | +| vvad | Boolean VAD decision before hangover, see clause 5.2.7 | + +### 3.2.2 Constants + +| | | +|------------|-----------------------------------------------------------------------------| +| adp | number of frames of hangover for secondary VAD, see clause 5.2.6 | +| burstconst | minimum length of speech burst to which hangover is added, see clause 5.2.8 | +| dec | determines rate of decrease in adaptive threshold, see clause 5.2.6 | +| fac | determines steady state adaptive threshold, see clause 5.2.6 | +| frames | number of frames over which av0 and av1 are calculated, see clause 5.2.2 | +| freqth | threshold for pole frequency decision, see clause 5.2.5 | +| hangconst | number of frames of hangover for primary VAD, see clause 5.2.8 | +| inc | determines rate of increase in adaptive threshold, see clause 5.2.6 | +| lthresh | lag difference threshold for periodicity decision, see clause 5.2.9 | +| margin | determines upper limit for adaptive threshold, see clause 5.2.6 | +| nthresh | frame count threshold for periodicity decision, see clause 5.2.9 | +| plev | lower limit for adaptive threshold, see clause 5.2.6 | +| predth | threshold for short term prediction error, see clause 5.2.5 | +| pth | energy threshold, see clause 5.2.6 | +| thresh | decision threshold for evaluation of stat flag, clause 5.2.4 | + +### 3.2.3 Functions + +| | | +|------------|---------------------------------------------| +| + | addition | +| - | subtraction | +| * | multiplication | +| / | division | +| x | absolute value of x | +| AND | Boolean AND | +| OR | Boolean OR | +| b | | +| MULT(x(i)) | the product of the series x(i) for i=a to b | +| i=a | | +| b | | +| SUM(x(i)) | the sum of the series x(i) for i=a to b | +| i=a | | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------------------| +| ACF | Autocorrelation Function | +| AFLAT | Autocorrelation Fixed point LAttice Technique | +| ANSI | American National Standards Institute | +| DTX | Discontinuous Transmission | +| LTP | Long Term Predictor | +| TX | Transmission | +| VAD | Voice Activity Detector | + +For abbreviations not given in this clause see GSM 01.04 [1]. + +# --- 4 General + +The function of the VAD is to indicate whether each 20 ms frame produced by the speech encoder contains speech or not. The output is a Boolean flag (vadflag) which is used by the Transmit (TX) DTX handler defined in GSM 06.41 [4]. + +The present document is organized as follows. + +Clause 5 describes the principles of operation of the VAD. Clause 6 provides an overview of the computational description of the VAD. The computational details necessary for the fixed point implementation of the VAD algorithm are given in the form of an American National Standards Institute (ANSI) C program contained in GSM 06.06 [5]. + +The verification of the VAD is based on the use of digital test sequences which are described in GSM 06.07 [6]. + +The performance of the VAD algorithm is characterized by the amount of audible speech clipping it introduces and the percentage activity it indicates. The characteristics for the VAD defined in the present document have been established by extensive testing under a wide range of operating conditions. The results are summarized in annex A. + +# --- 5 Functional description + +The purpose of this clause is to give the reader an understanding of the principles of operation of the VAD, whereas GSM 06.06 [5] contains the fixed point computational description of the VAD. In the case of discrepancy between the two descriptions, the description in GSM 06.06 [5] will prevail. + +## 5.1 Overview and principles of operation + +The function of the VAD is to distinguish between noise with speech present and noise without speech present. This is achieved by comparing the energy of a filtered version of the input signal with a threshold. The presence of speech is indicated whenever the threshold is exceeded. + +The detection of speech in mobile environments is difficult due to the low speech/noise ratios which are encountered, particularly in moving vehicles. To increase the probability of detecting speech, the input signal is adaptively filtered (see clause 5.2.1) to reduce its noise content before the voice activity decision is made (see clause 5.2.7). + +The frequency spectrum and level of the noise may vary within a given environment as well as between different environments. It is therefore necessary to adapt the input filter coefficients and energy threshold at regular intervals as described in clause 5.2.6. + +## 5.2 Algorithm description + +The block diagram of the VAD algorithm is shown in figure 1. The individual blocks are described in the following clauses. The global variables shown in the block diagram are described in table 1. + +**Table 1: Description of variables in figure 1** + +| Var | Description | +|---------|------------------------------------------------------------------------------------------------------| +| acf | The ACF vector which is calculated in the speech encoder (GSM 06.20 [2]). | +| av0 | Averaged ACF vector. | +| av1 | A previous value of av0. | +| lags | The open loop long term predictor lags for the four speech encoder subframes (GSM 06.20 [2]). | +| ptch | Boolean flag indicating the presence of a periodic signal component. | +| pvad | Energy in the current filtered signal frame. | +| rav1 | Autocorrelation vector obtained from av1. | +| rc | The first four unquantized reflection coefficients calculated in the speech encoder (GSM 06.20 [2]). | +| rvad | Autocorrelation vector of the adaptive filter predictor values. | +| stat | Boolean flag indicating that the frequency spectrum of the input signal is stationary. | +| thvad | Adaptive primary VAD threshold. | +| tone | Boolean flag indicating the presence of an information tone. | +| vadflag | Boolean VAD decision with hangover included. | +| vvad | Boolean VAD decision before hangover. | + +![Functional block diagram of the VAD. The diagram shows the flow of data from input 'acf' through various processing blocks to produce 'vadflag'. The 'acf' input is split into 'Adaptive filtering and energy computation', 'Periodicity detection', 'Tone detection', 'Predictor values computation', and 'ACF averaging'. 'Adaptive filtering and energy computation' outputs 'P_vad' to 'VAD decision' and 'r_vad' to 'Threshold adaptation'. 'Periodicity detection' outputs 'ptch' to 'Threshold adaptation'. 'Tone detection' outputs 'tone' to 'Threshold adaptation'. 'Predictor values computation' outputs 'r_av1' to 'Spectral comparison' and receives 'av1' from 'ACF averaging'. 'ACF averaging' outputs 'av0' to 'Spectral comparison'. 'Spectral comparison' outputs 'stat' to 'Threshold adaptation'. 'Threshold adaptation' outputs 'th_vad' to 'VAD decision'. 'VAD decision' outputs 'V_vad' to 'VAD hangover addition', which finally outputs 'vadflag'.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Functional block diagram of the VAD. The diagram shows the flow of data from input 'acf' through various processing blocks to produce 'vadflag'. The 'acf' input is split into 'Adaptive filtering and energy computation', 'Periodicity detection', 'Tone detection', 'Predictor values computation', and 'ACF averaging'. 'Adaptive filtering and energy computation' outputs 'P\_vad' to 'VAD decision' and 'r\_vad' to 'Threshold adaptation'. 'Periodicity detection' outputs 'ptch' to 'Threshold adaptation'. 'Tone detection' outputs 'tone' to 'Threshold adaptation'. 'Predictor values computation' outputs 'r\_av1' to 'Spectral comparison' and receives 'av1' from 'ACF averaging'. 'ACF averaging' outputs 'av0' to 'Spectral comparison'. 'Spectral comparison' outputs 'stat' to 'Threshold adaptation'. 'Threshold adaptation' outputs 'th\_vad' to 'VAD decision'. 'VAD decision' outputs 'V\_vad' to 'VAD hangover addition', which finally outputs 'vadflag'. + +Figure 1: Functional block diagram of the VAD + +### 5.2.1 Adaptive filtering and energy computation + +The energy in the current filtered signal frame ( $p_{vad}$ ) is computed as follows: + +$$p_{vad} = r_{vad}[0] * acf[0] + 2 * \sum_{i=1}^8 (r_{vad}[i] * acf[i])$$ + +This corresponds to performing an 8th order block filtering on the filtered input samples to the speech encoder. This is explained in annex B. + +### 5.2.2 ACF averaging + +Spectral characteristics of the input signal have to be obtained using blocks that are larger than one 20 ms frame. This is done by averaging the ACF (autocorrelation function) vectors for several consecutive frames. The averaging is given by the following equations: + +$$\begin{aligned} av0\{n\}[i] &= \sum_{j=0}^{frames-1} (acf\{n-j\}[i]) & ; \quad i = 0..8 \\ av1\{n\}[i] &= av0\{n-frames\}[i] & ; \quad i = 0..8 \end{aligned}$$ + +where (n) represents the current frame, (n-1) represents the previous frame etc. The values of the constants and initial variable values are given in table 2. + +Table 2: Constants and variables for ACF averaging + +| Constant | Value | Variable | Initial value | +|----------|-------|---------------------------|---------------| +| frames | 4 | previous ACF's, av0 & av1 | All set to 0 | + +### 5.2.3 Predictor values computation + +The filter predictor values $aav1$ are obtained from the autocorrelation values $av1$ according to the equation: + +$$a = R^{-1} p$$ + +where: + +$$R = \begin{bmatrix} av1[0] & av1[1] & av1[2] & av1[3] & av1[4] & av1[5] & av1[6] & av1[7] \\ av1[1] & av1[0] & av1[1] & av1[2] & av1[3] & av1[4] & av1[5] & av1[6] \\ av1[2] & av1[1] & av1[0] & av1[1] & av1[2] & av1[3] & av1[4] & av1[5] \\ av1[3] & av1[2] & av1[1] & av1[0] & av1[1] & av1[2] & av1[3] & av1[4] \\ av1[4] & av1[3] & av1[2] & av1[1] & av1[0] & av1[1] & av1[2] & av1[3] \\ av1[5] & av1[4] & av1[3] & av1[2] & av1[1] & av1[0] & av1[1] & av1[2] \\ av1[6] & av1[5] & av1[4] & av1[3] & av1[2] & av1[1] & av1[0] & av1[1] \\ av1[7] & av1[6] & av1[5] & av1[4] & av1[3] & av1[2] & av1[1] & av1[0] \end{bmatrix}$$ + +and: + +$$p = \begin{bmatrix} av1[1] \\ av1[2] \\ av1[3] \\ av1[4] \\ av1[5] \\ av1[6] \\ av1[7] \\ av1[8] \end{bmatrix} \quad a = \begin{bmatrix} aav1[1] \\ aav1[2] \\ aav1[3] \\ aav1[4] \\ aav1[5] \\ aav1[6] \\ aav1[7] \\ aav1[8] \end{bmatrix}$$ + +$$aav1[0] = -1$$ + +$av1$ is used in preference to $av0$ as the latter may contain speech. The autocorrelated predictor values $rav1$ are then obtained: + +$$rav1[i] = \sum_{k=0}^{8-i} (aav1[k] * aav1[k+i]) \quad ; i = 0..8$$ + +### 5.2.4 Spectral comparison + +The spectra represented by the autocorrelated predictor values $rav1$ and the averaged autocorrelation values $av0$ are compared using the distortion measure ( $dm$ ), defined below. This measure is used to produce a Boolean value $stat$ every 20 ms, as shown in the following equations: + +$$\begin{aligned} dm &= (rav1[0] * av0[0] + 2 * \sum_{i=1}^8 (rav1[i] * av0[i])) / av0[0] \\ difference &= | dm - lastdm | \\ lastdm &= dm \\ stat &= (difference < thresh) \end{aligned}$$ + +The values of the constants and initial variable values are given in table 3. + +**Table 3: Constants and variables for spectral comparison** + +| Constant | Value | Variable | Initial value | +|----------|-------|----------|---------------| +| thresh | 0,068 | lastdm | 0 | + +### 5.2.5 Information tone detection + +Information tones and noise can be classified by inspecting the short term prediction gain, information tones resulting in a higher prediction gain than noise. Tones can therefore be detected by comparing the prediction gain to a fixed threshold. By limiting the prediction gain calculation to a fourth order analysis, information signals consisting of one or two tones can be detected whilst minimizing the prediction gain for noise. + +The prediction gain decision is implemented by comparing the normalized short term prediction error with the short term prediction error threshold (predth). This measure is used to produce a Boolean value, tone, every 20 ms. The signal is classified as a tone if the prediction error is less than predth. This is equivalent to a prediction gain threshold of 13,5 dB. + +Vehicle noise can contain strong resonances at low frequencies, resulting in a high prediction gain. A further test is therefore made to determine the pole frequency of a second order analysis of the signal frame. The signal is classified as noise if the frequency of the pole is less than 385 Hz. + +The algorithm for evaluating the Boolean tone flag is as follows: + +``` +tone = false + +den = a[1]*a[1] +num = 4*a[2] - a[1]*a[1] + +if (num <= 0) + return + +if ((a[1] < 0) AND (num/den < freqth)) + return + +prederr = MULT (1 - rc[i]*rc[i]) + i=1 + +if (prederr < predth) + tone = true + +return +``` + +rc[1..4] are the first four unquantized reflection coefficients obtained from the speech encoder short term predictor. The coefficients a[0..2] are transversal filter coefficients calculated from rc[1..2]. The pole frequency calculation is described in annex C. + +The values of the constants are given in table 4. + +**Table 4: Constants for information tone detection** + +| Constant | Value | +|----------|--------| +| freqth | 0,0973 | +| predth | 0,0447 | + +### 5.2.6 Threshold adaptation + +A check is made every 20 ms to determine whether the adaptive primary VAD threshold, (thvad) should be changed. This adaptation is carried out according to the flow chart in figure 2. The values of the constants and initial variable values are given in table 5. + +Adaptation of thvad takes place in two different situations: + +In the first case, the decision threshold (thvad) is set to the lower limit for the adaptive threshold (plev) if the input signal frame energy (acf[0]) is less than the energy threshold (pth). The autocorrelation vector of the adaptive filter predictor values (rvad) remains unchanged. + +In the second case, thvad and rvad are adapted if there is a low probability that speech or information tones are present. This occurs when the following conditions are met: + +- the frequency spectrum of the input signal is stationary (clause 5.2.4); + +- b) the signal does not contain a periodic component (clause 5.2.9); +- c) information tones are not present (clause 5.2.5). + +The autocorrelation vector of the adaptive filter predictor values (rvad) is updated with the rav1 values. The step size by which thvad is adapted is not constant but a proportion of the current value and its rate of increase or decrease is determined by constants inc and dec respectively. + +The adaptation begins by experimentally multiplying thvad by a factor of $(1-1/\text{dec})$ . If thvad is now higher than or equal to pvad times, the steady state adaptive threshold constant (fac), then thvad needed to be decreased and it is left at this new lower level. If, on the other hand, thvad is less than pvad times fac, then it either needs to be increased or kept constant. In this case, it is multiplied by a factor of $(1+1/\text{inc})$ or set to pvad times fac whichever yields the lower value. thvad is never allowed to be greater than pvad+upper adaptive threshold limit (margin). + +**Table 5: Constants and variables threshold adaptation** + +| Constant | Value | Variable | Initial value | +|----------|--------|------------|---------------| +| pth | 210000 | margin | 112000000 | +| plev | 560000 | adaptcount | 0 | +| fac | 2,55 | thvad | 1400000 | +| adp | 8 | rvad[0] | 6 | +| inc | 16 | rvad[1] to | All 0 | +| dec | 32 | rvad[8] | | + +![Flow diagram for threshold adaptation. The process starts with BEGIN, checks if acf[0] < pth. If yes, it sets th_vad = plev. If no, it checks if stat and not ptch and not tone. If yes, it increments adaptcount. If no, it sets adaptcount = 0. Both lead to a check if adaptcount > adp. If yes, it updates th_vad = th_vad - th_vad / dec. If no, it ends. The updated th_vad is then checked against pvad * fac. If less, it updates th_vad = min(th_vad + th_vad / inc, pvad * fac). Both lead to a check if th_vad > pvad + margin. If yes, it updates th_vad = pvad + margin. Both lead to setting r_vad = f_vad1, then adaptcount = adp + 1, and finally END.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +graph TD; BEGIN((BEGIN)) --> D1{acf[0] < pth ?}; D1 -- yes --> P1[th_vad = plev]; D1 -- no --> D2{stat and not ptch and not tone ?}; D2 -- yes --> P2[increment adaptcount]; D2 -- no --> P3[adaptcount = 0]; P1 --> D3{adaptcount > adp ?}; P2 --> D3; P3 --> D3; D3 -- yes --> P4[th_vad = th_vad - th_vad / dec]; D3 -- no --> END1((END)); P4 --> D4{th_vad < pvad * fac ?}; D4 -- yes --> P5[th_vad = min ( th_vad + th_vad / inc, pvad * fac )]; D4 -- no --> D5{th_vad > pvad + margin ?}; P5 --> D5; D5 -- yes --> P6[th_vad = pvad + margin]; D5 -- no --> P7[r_vad = f_vad1]; P6 --> P7; P7 --> P8[adaptcount = adp + 1]; P8 --> END2((END)); +``` + +Flow diagram for threshold adaptation. The process starts with BEGIN, checks if acf[0] < pth. If yes, it sets th\_vad = plev. If no, it checks if stat and not ptch and not tone. If yes, it increments adaptcount. If no, it sets adaptcount = 0. Both lead to a check if adaptcount > adp. If yes, it updates th\_vad = th\_vad - th\_vad / dec. If no, it ends. The updated th\_vad is then checked against pvad \* fac. If less, it updates th\_vad = min(th\_vad + th\_vad / inc, pvad \* fac). Both lead to a check if th\_vad > pvad + margin. If yes, it updates th\_vad = pvad + margin. Both lead to setting r\_vad = f\_vad1, then adaptcount = adp + 1, and finally END. + +Figure 2: Flow diagram for threshold adaptation + +### 5.2.7 VAD decision + +Prior to hangover the Boolean VAD decision is defined as: + +``` +vvad = (pvad > thvad) +``` + +### 5.2.8 VAD hangover addition + +VAD hangover is only added to bursts of speech greater than or equal to burstcount blocks. The Boolean variable vadflag indicates the decision of the VAD with hangover included. The values of the constants and initial variable values are given in table 6. The hangover algorithm is as follows: + +``` +if (vvad) + increment(burstcount) +else + burstcount = 0 + +if (burstcount >= burstconst) +{ + hangcount = hangconst + burstcount = burstconst +} + +vadflag = (vvad OR (hangcount >= 0)) + +if (hangcount >= 0) + decrement(hangcount) +``` + +**Table 6: Constants and variables for VAD hangover addition** + +| Constant | Value | Variable | Initial value | +|------------|-------|------------|---------------| +| burstconst | 3 | burstcount | 0 | +| hangconst | 5 | hangcount | -1 | + +### 5.2.9 Periodicity detection + +thvad and rvad are updated when the frequency spectrum of the input signal is stationary. However, vowel sounds also have a stationary frequency spectrum. The Boolean variable ptch indicates the presence of a periodic signal component and prevents adaptation of thvad and rvad. ptch is updated every 20 ms and is true when periodicity (a vowel sound) is detected. The periodicity detector identifies the vowel sounds by comparing consecutive Long Term Predictor (LTP) lag values lags[1..4] which are obtained every sub frame from the speech codec defined in GSM 06.20 [2]. Cases in which one lag value is a factor of the other are catered for. However, consecutive lags with a ratio which is either non-integer or greater than 3 are not classified as periodic. + +``` +lagcount = 0 + +for ( j=1; j<=4; j++ ) +{ + smalllag=maximum(lags[j], lags[j-1]) + for ( i=1; i<=3; i++ ) + if (smalllag >= minimum(lags[i], lags[i-1])) + smalllag = smalllag - minimum(lags[i], lags[i-1]) + if (minimum(smalllag, minimum(lags[j], lags[j-1]) - smalllag) < lthresh) + increment(lagcount) +} + +veryoldlagcount = oldlagcount + +oldlagcount = lagcount + +ptch = (oldlagcount + veryoldlagcount >= nthresh) +``` + +The values of constants and initial values are given in table 7. lags[0] = lags[4] of the previous frame. + +ptch is calculated after the VAD decision and when the current LTP lag values lags[1..4] are available. This reduces the delay of the VAD decision. + +**Table 7: Constants and variables for periodicity detection** + +| Constant | Value | Variable | Initial value | +|----------|-------|-----------------|---------------| +| lthresh | 2 | ptch | 1 | +| nthresh | 7 | oldlagcount | 0 | +| | | veryoldlagcount | 0 | +| | | lags[0] | 21 | + +# 6 Computational description overview + +The computational details necessary for the fixed point implementation of the speech transcoding and DTX functions are given in the form of an American National Standards Institute (ANSI) C program contained in GSM 06.06 [5]. This clause provides an overview of the modules which describe the computation of the VAD algorithm. + +## 6.1 VAD modules + +The computational description of the VAD is divided into three ANSI C modules. These modules are: + +- vad\_reset; +- vad\_algorithm; +- periodicity\_update. + +The vad\_reset module sets the VAD variables to their initial values. + +The vad\_algorithm module is divided into nine sub-modules which correspond to the blocks of figure 1 in the high level description of the VAD algorithm. The vad\_algorithm module can be called as soon as the acf[0..8] and rc[1..4] variables are known. This means that the VAD computation can take place after the Autocorrelation Fixed point LAttice Technique (AFLAT) routine in the speech encoder (GSM 06.20 [2]). The vad\_algorithm module also requires the value of the ptch variable calculated in the previous frame. + +The ptch variable is calculated by the periodicity\_update module from the lags[1..4] variable. The individual lag values are calculated for each subframe in the LTP routine of the speech encoder (GSM 06.20 [2]). The periodicity\_update module is called after the current 20 ms signal frame has been encoded. + +## 6.2 Pseudo-floating point arithmetic + +All the arithmetic operations follow the precision and format used in the computational description of the speech codec in GSM 06.06 [5]. To increase the precision within the fixed point implementation, a pseudo-floating point representation of some variables is used. This applies to the following variables (and related constants) of the VAD algorithm: + +- **pvad:** Energy of filtered signal; +- **thvad:** Threshold of the VAD decision; +- **acf0:** Energy of the input signal. + +For the representation of these variables, two 16-bit integers are needed: + +- one for the exponent (e\_pvad, e\_thvad, e\_acf0); +- one for the mantissa (m\_pvad, m\_thvad, m\_acf0). + +The value $e\_pvad$ represents the lowest power of 2 just greater or equal to the actual value of $pvad$ , and the $m\_pvad$ value represents an integer which is always greater than or equal to 16384 (normalized mantissa). It means that the $pvad$ value is equal to + +$$pvad = 2^{e\_pvad} * (m\_pvad / 32768)$$ + +This scheme provides a large dynamic range for the $pvad$ value and always keeps a precision of 16 bits. All the comparisons are easy to make by comparing the exponents of two variables, and the VAD algorithm needs only one pseudo floating point addition and multiplication. All the computations related to the pseudo-floating point variables require simple 16 or 32-bit arithmetic operations defined in the detailed description of the speech codec. + +Some constants, represented by a floating point format, are needed and symbolic names (in capital letters) for their exponent and mantissa are used; table 8 lists all these constants with the associated symbolic names and their numerical constant values. + +**Table 8: List of floating point constants** + +| Constant | Exponent | Mantissa | +|----------|---------------|------------------| +| pth | E_PTH = 18 | M_PTH = 26250 | +| margin | E_MARGIN = 27 | M_MARGIN = 27343 | +| plev | E_PLEV = 20 | M_PLEV = 17500 | + +# --- Annex A (informative): VAD performance + +In the optimization of a VAD, a trade-off has to be made between speech clipping, which reduces the subjective performance of the system, and the mean channel activity factor. The benefit of DTX is increased as the activity factor is reduced. However, in general, a reduction of the activity factor will be associated with a greater risk of audible speech clipping. + +In the optimization process, emphasis has been placed on avoiding unnecessary speech clipping. However, it has been found that a VAD with virtually no audible clipping would result in a high activity and little DTX advantage. The VAD specified in the present document introduces audible and possibly objectionable clipping in certain cases, mainly for low input levels and low signal to noise ratios. + +An indication of the mean channel activity in DTX mode is given in table A.1. The figure quoted is the average calculated over a large number of conversations covering factors such as different talkers, noise characteristics and locations. It should be noted that the actual activity of a particular talker in a specific conversation may vary considerably from the figure given in the table. This is due to both talker behaviour and the level dependency of the VAD (the channel activity has been found to decrease by about 0.5% per dB of level reduction). However, as mentioned above, a decreased speech input level increases the risk of objectionable clipping. + +**Table A.1: Mean channel activity factor in DTX mode** + +| Channel activity factor | +|-------------------------| +| 60% | + +# Annex B (informative): Simplified block filtering operation + +Consider an 8th order transversal filter with filter coefficients $a[0..8]$ , through which a signal is being passed, the output of the filter being: + +$$s'n = - \sum_{i=0}^8 (a[i]*s[n-i]) \quad (1)$$ + +If we apply block filtering over 20 ms frames, then this equation becomes: + +$$s'n = - \sum_{i=0}^{\min(8,n)} (a[i]*s[n-i]) \quad ; \begin{matrix} n = 0..167 \\ 0 \leq n \leq 167 \end{matrix} \quad (2)$$ + +If the energy of the filtered signal is then obtained for every 20 ms frame, the equation for this is: + +$$pvad = \sum_{n=0}^{167} \left( - \sum_{i=0}^{\min(8,n)} (a[i]*s[n-i]) \right)^2 \quad ; \quad 0 \leq n-i \leq 159 \quad (3)$$ + +We know that: + +$$acf[i] = \sum_{n=i}^{159} (s[n]*s[n-i]) \quad ; \begin{matrix} i = 0..8 \\ 0 \leq n-i \leq 159 \end{matrix} \quad (4)$$ + +If equation (3) is expanded and $acf[0..8]$ are substituted for $s[n]$ then we arrive at the equations: + +$$pvad = r[0]*acf[0] + 2*\sum_{i=1}^8 (r[i]*acf[i]) \quad (5)$$ + +Where: + +$$r[i] = \sum_{k=0}^{8-i} (a[k]*a[k+i]) \quad ; \quad i = 0..8 \quad (6)$$ + +# Annex C (informative): Pole frequency calculation + +This annex describes the algorithm used to determine whether the pole frequency for a second order analysis of the signal frame is less than 385 Hz. + +The filter coefficients for a second order synthesis filter are calculated from the first two unquantized reflection coefficients $rc[1..2]$ obtained from the speech encoder. If the filter coefficients $a[0..2]$ are defined such that the synthesis filter response is given by: + +$$H(z) = 1 / (a[0] + a[1]z^{-1} + a[2]z^{-2}) \quad (1)$$ + +Then the positions of the poles in the Z-plane are given by the solutions to the following quadratic: + +$$a[0]z^2 + a[1]z + a[2] = 0, \quad a[0] = 1 \quad (2)$$ + +The positions of the poles, $z$ , are therefore: + +$$z = re \pm j \cdot \sqrt{im}, \quad j^2 = -1 \quad (3)$$ + +where: + +$$re = -a[1] / 2 \quad (4)$$ + +$$im = (4 \cdot a[2] - a[1]^2) / 4 \quad (5)$$ + +If $im$ is negative then the poles lie on the real axis of the Z-plane and the signal is not a tone and the algorithm terminates. If $re$ is negative then the poles lie in the left hand side of the Z-plane and the frequency is greater than 2000 Hz and the prediction error test can be performed. + +If $im$ is positive and $re$ is positive then the poles are complex and lie in the right hand side of the Z-plane and the frequency in Hz is related to $re$ and $im$ by the expression: + +$$freq = \arctan(\sqrt{im} / re) \cdot 4000 / \pi \quad (6)$$ + +Having ensured that both $im$ and $re$ are positive the test for a pole frequency less than 385 Hz can be derived by substituting equations 4 and 5 into equation 6 and re-arranging: + +$$(4 \cdot a[2] - a[1]^2) / a[1]^2 < \tan^2(\pi \cdot 385 / 4000) \quad (7)$$ + +or + +$$(4 \cdot a[2] - a[1]^2) / a[1]^2 < 0.0973 \quad (8)$$ + +If this test is true then the signal is not a tone and the algorithm terminates, otherwise the prediction error test is performed. + +# Annex D (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#15 | | | | 4.1.1 | ETSI Publication | +| SMG#20 | | | | 5.0.1 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46051/raw.md b/marked/Rel-18/46_series/46051/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..33103e674c1f946fbf0bbbf07b344e69544ddfa6 --- /dev/null +++ b/marked/Rel-18/46_series/46051/raw.md @@ -0,0 +1,309 @@ + + +# 3GPP TS 46.051 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Enhanced Full Rate (EFR) speech processing functions; General description (Release 18)** + +![GSM logo with the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS'](64662465bba247703fdec49c8f3309f9_img.jpg) + +The GSM logo consists of the letters 'GSM' in a stylized blue font, with a small red square to the right of the 'M'. Below the logo, the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' is written in a smaller blue font. + +GSM logo with the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' + +![3GPP logo with a signal icon](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo features the letters '3GPP' in a bold, black, stylized font. Below the 'G' and 'P', there is a red signal icon consisting of three curved lines. + +3GPP logo with a signal icon + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|-------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 General ..... | 6 | +| 5 Enhanced Full Rate speech channel transcoding ..... | 7 | +| 6 Enhanced Full Rate speech channel discontinuous transmission (DTX) ..... | 7 | +| 7 Enhanced Full Rate speech channel Voice Activity Detection (VAD) ..... | 8 | +| 8 Enhanced Full Rate speech channel comfort noise insertion..... | 8 | +| 9 Enhanced Full Rate speech channel lost speech frame substitution and muting ..... | 9 | +| 10 Enhanced Full Rate codec homing..... | 9 | +| 11 Alternative Enhanced Full Rate implementation using the Adaptive Multi Rate 12.2 kbit/s mode ..... | 9 | +| Annex A (informative): Change History ..... | 11 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is an introduction to GSM 06.60 [6], GSM 06.61 [7], GSM 06.62 [8], GSM 06.81 [9] and GSM 06.82 [10] ENs dealing with the speech processing functions in the Enhanced Full Rate channel of the GSM system. A general overview of the speech processing functions is given, with reference to the ENs where each function is specified in detail. + +# --- 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 03.50: "Digital cellular telecommunications system (Phase 2+); Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system". +- [3] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [4] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec". +- [5] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test vectors for the GSM Enhanced Full Rate (EFR) speech codec". +- [6] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding". +- [7] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frame for Enhanced Full Rate (EFR) speech traffic channels". +- [8] GSM 06.62: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels". +- [9] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels". +- [10] GSM 06.82: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD) for Enhanced Full Rate (EFR) speech traffic channels". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +Definition of terms used in the present document can be found in GSM 06.60 [6], GSM 06.61 [7], GSM 06.62 [8], GSM 06.81 [9] and GSM 06.82 [10]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------------------------------------| +| ACELP | Algebraic Code Excited Linear Prediction | +| BFI | Bad Frame Indication | +| BSS | Base Station System | +| CCITT | Comité Consultatif International Télégraphique et Téléphonique | +| DTX | Discontinuous Transmission | +| ETS | European Telecommunication Standard | +| GSM | Global System for Mobile communications | +| MS | Mobile Station | +| PCM | Pulse Code Modulated | +| PLMN | Public Land Mobile Network | +| PSTN | Public Switched Telephone Network | +| RF | Radio Frequency | +| RSS | Radio SubSystem | +| RX | Receive | +| SACCH | Slow Associated Control CHannel | +| SID | Silence Descriptor | +| SP flag | SPeech flag | +| TAF | Time Alignment Flag | +| TX | Transmit | + +For abbreviations not given in this subclause, see GSM 01.04 [1]. + +# 4 General + +Figure 1 presents a reference configuration where the various speech processing functions are identified. In this figure, the relevant Standards for each function are also indicated. + +In figure 1, the audio parts including analogue to digital and digital to analogue conversion are included, to show the complete speech path between the audio input/output in the Mobile Station (MS) and the digital interface of the PSTN. The detailed specification of the audio parts are contained in GSM 03.50 [2]. These aspects are only considered to the extent that the performance of the audio parts affect the performance of the speech transcoder. + +An alternative and fully interoperable implementation using as a basis the 12.2 kbit/s mode of the Adaptive Multi Rate speech coder is described in section 11. + +![Figure 1: Reference configuration of speech processing functions. The diagram is divided into two main sections: TRANSMIT SIDE and RECEIVE SIDE. The TRANSMIT SIDE shows the flow from the MS side (GSM 03.50) through LPF and A/D conversion, then to the BSS side (GSM 06.60) for 8-bit /A-law to 13-bit uniform conversion. The signal then enters the Speech encoder (GSM 06.60) via a VAD (GSM 06.82) and Comfort noise TX functions (GSM 06.62). The Speech encoder outputs a Speech frame (GSM 06.60) to the DTX control and operation block (GSM 06.81). The DTX control and operation block outputs an SP flag (GSM 06.81) and Info. blts (GSM 06.81). The RECEIVE SIDE shows the flow from the DTX control and operation block (GSM 06.81) through the Speech decoder (GSM 06.60) to the LPF and A/D conversion (GSM 03.50) on the MS side. The Speech decoder also receives a Speech frame (GSM 06.60) from the DTX control and operation block. The LPF and A/D conversion block outputs the final audio signal. The diagram includes numbered circles 1 through 7 indicating key processing points: 1 (BSS side only, GSM 06.60), 2 (interface between BSS and MS), 3 (Voice Activity Detector, GSM 06.82), 4 (Speech frame, GSM 06.60), 5 (SID frame, GSM 06.62), 6 (SP flag, GSM 06.81), and 7 (Info. blts, GSM 06.81).](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) + +Figure 1: Reference configuration of speech processing functions. The diagram is divided into two main sections: TRANSMIT SIDE and RECEIVE SIDE. The TRANSMIT SIDE shows the flow from the MS side (GSM 03.50) through LPF and A/D conversion, then to the BSS side (GSM 06.60) for 8-bit /A-law to 13-bit uniform conversion. The signal then enters the Speech encoder (GSM 06.60) via a VAD (GSM 06.82) and Comfort noise TX functions (GSM 06.62). The Speech encoder outputs a Speech frame (GSM 06.60) to the DTX control and operation block (GSM 06.81). The DTX control and operation block outputs an SP flag (GSM 06.81) and Info. blts (GSM 06.81). The RECEIVE SIDE shows the flow from the DTX control and operation block (GSM 06.81) through the Speech decoder (GSM 06.60) to the LPF and A/D conversion (GSM 03.50) on the MS side. The Speech decoder also receives a Speech frame (GSM 06.60) from the DTX control and operation block. The LPF and A/D conversion block outputs the final audio signal. The diagram includes numbered circles 1 through 7 indicating key processing points: 1 (BSS side only, GSM 06.60), 2 (interface between BSS and MS), 3 (Voice Activity Detector, GSM 06.82), 4 (Speech frame, GSM 06.60), 5 (SID frame, GSM 06.62), 6 (SP flag, GSM 06.81), and 7 (Info. blts, GSM 06.81). + +![Figure 1: Overview of audio processing functions. The diagram shows the flow of audio data between GSM 06.81 (DTX control and operation), GSM 06.61 (Speech frame substitution), GSM 06.60 (Speech decoder), and GSM 06.62 (Comfort noise RX functions) on the transmit side, and GSM 06.60 (13-bit uniform to 8-bit /A-law conversion) and GSM 03.50 (D/A and LPF) on the receive side. Inputs include Info. bits (8), BFI (9), SID (10), and TAF (11).](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +The diagram illustrates the audio processing functions in a GSM system. On the left, the transmit side shows inputs for Info. bits (8), BFI (9), SID (10), and TAF (11) entering a 'DTX control and operation' block (GSM 06.81). This block outputs a 'Speech frame' (4) to a 'Speech decoder' (GSM 06.60) and a 'SID frame' (5) to 'Comfort noise RX functions' (GSM 06.62). The 'Speech decoder' also receives input from 'Speech frame substitution' (GSM 06.61). The output of the 'Speech decoder' (2) is then processed by a '13-bit uniform to 8-bit /A-law' converter (GSM 06.60) on the 'BSS side only', which outputs (1). The output of the 'Speech decoder' (2) is also processed by a 'D/A' converter and an 'LPF' (GSM 03.50) on the 'MS side only'. + +Figure 1: Overview of audio processing functions. The diagram shows the flow of audio data between GSM 06.81 (DTX control and operation), GSM 06.61 (Speech frame substitution), GSM 06.60 (Speech decoder), and GSM 06.62 (Comfort noise RX functions) on the transmit side, and GSM 06.60 (13-bit uniform to 8-bit /A-law conversion) and GSM 03.50 (D/A and LPF) on the receive side. Inputs include Info. bits (8), BFI (9), SID (10), and TAF (11). + +- 1) 8-bit /A-law or $\mu$ -law (PCS 1900) PCM (CCITT recommendation G.711), 8 000 samples/s. +- 2) 13-bit uniform PCM, 8 000 samples/s. +- 3) Voice Activity Detector (VAD) flag. +- 4) Encoded speech frame, 50 frames/s, 244 bits/frame. +- 5) Silence Descriptor (SID) frame, 244 bits/frame. +- 6) SPEech (SP) flag, indicates whether information bits are speech or SID information. +- 7) Information bits delivered to the radio subsystem. +- 8) Information bits received from the radio subsystem. +- 9) Bad Frame Indication. +- 10) Silence Descriptor (SID) flag. +- 11) Time Alignment Flag (TAF), marks the position of the SID frame within the Slow Associated Control CHannel (SACCH) multiframe. + +Figure 1: Overview of audio processing functions + +# 5 Enhanced Full Rate speech channel transcoding + +As shown in figure 1, the speech encoder takes its input as a 13-bit uniform Pulse Code Modulated (PCM) signal either from the audio part of the Mobile Station or on the network side, from the Public Switched Telephone Network (PSTN) via an 8-bit/A-law or $\mu$ -law (PCS 1900) to 13-bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to the channel coding function defined in GSM 05.03 [3] to produce an encoded block consisting of 456 bits leading to a gross bit rate of 22,8 kbit/s. + +In the receive direction, the inverse operations take place. GSM 06.60 [6] describes the detailed mapping between input blocks of 160 speech samples in 13-bit uniform PCM format to encoded blocks of 244 bits and from encoded blocks of 244 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8 000 sample/s leading to a bit rate for the encoded bit stream of 12,2 kbit/s. The coding scheme is the so-called Algebraic Code Excited Linear Prediction, hereafter referred to as ACELP. + +GSM 06.60 [6] describes the codec and GSM 06.53 [4] defines the C code, thus enabling the verification of compliance to GSM 06.60 [6] to a high degree of confidence by use of a set of digital test sequences given in GSM 06.54 [5]. + +# 6 Enhanced Full Rate speech channel discontinuous transmission (DTX) + +During a normal phone conversation, the participants alternate so that, on the average, each direction of transmission is occupied about 50 % of the time. Discontinuous transmission (DTX) is a mode of operation where the transmitters are switched on only for those frames which contain useful information. This may be done for the following two purposes: + +- 1) In the MS, battery life will be prolonged or a smaller battery could be used for a given operational duration. +- 2) The average interference level over the air interface is reduced, leading to better Radio Frequency (RF) spectrum efficiency. + +The overall DTX mechanism is implemented in the DTX handlers (Transmit (TX) and Receive (RX)) described in GSM 06.81 [9] and requires the following functions: + +- a Voice Activity Detector (VAD) on the TX side, see GSM 06.82 [10]; +- evaluation of the background acoustic noise on the TX side, in order to transmit characteristic parameters to the RX side, see GSM 06.62 [8]; +- generation of comfort noise on the RX side during periods where the radio transmission is turned off, see GSM 06.62 [8]. + +The transmission of comfort noise information to the RX side is achieved by means of a Silence Descriptor (SID) frame. The SID frame is transmitted at the end of speech bursts and serves as an end of speech marker for the RX side. In order to update the comfort noise characteristics at the RX side, SID frames are transmitted at regular intervals also during speech pauses. This also serves the purpose of improving the measurement of the radio link quality by the Radio SubSystem (RSS). + +The DTX handlers interwork with the RSS using flags. The RSS is in control of the actual transmitter keying on the TX side, and performs various pre-processing functions on the RX side. This is described in GSM 06.81 [9]. + +The speech flag (SP) indicates whether information bits are speech or SID information. The SP flag is calculated from the VAD flag by the TX DTX handler. When SID information is transmitted (SP="0") the operation of the speech encoder is modified to reduce the remaining computation for that frame. This is described in GSM 06.62 [8]. + +# --- 7 Enhanced Full Rate speech channel Voice Activity Detection (VAD) + +The Enhanced Full Rate VAD function is described in GSM 06.82 [10]. + +The input to the VAD is a set of parameters computed by the Enhanced Full Rate speech encoder defined in GSM 06.60 [6]. The VAD uses this information to decide whether each 20 ms speech coder frame contains speech or not. Note that the VAD flag is an input to TX DTX handler and does not control the transmitter keying directly. + +GSM 06.82 [10] describes the VAD algorithm and GSM 06.53 [4] defines the C code. The verification of compliance to GSM 06.82 [10] is achieved by use of digital test sequences (see GSM 06.54 [5]) applied to the same interface as the test sequences for the speech codec. + +# --- 8 Enhanced Full Rate speech channel comfort noise insertion + +The Enhanced Full Rate noise comfort insertion function is described in GSM 06.62 [8]. + +When switching the transmission on and off during DTX operation, the effect would be a modulation of the background noise at the receiving end, if no precautions were taken. When transmission is on, the background noise is transmitted together with the speech to the receiving end. As the speech burst ends, the connection is off and the perceived noise would drop to a very low level. This step modulation of noise may be perceived as annoying and reduce the intelligibility of speech, if presented to a listener without modification. + +This "noise contrast effect" is reduced in the GSM system by inserting an artificial noise, termed comfort noise, at the receiving end when speech is absent. + +The comfort noise processes are as follows: + +- the evaluation of the acoustic background noise in the transmitter; + +- the noise parameter encoding (SID frames) and decoding; +- and the generation of comfort noise in the receiver. + +The comfort noise processes and the algorithm for updating the noise parameters during speech pauses are defined in detail in GSM 06.62 [8]. + +The comfort noise mechanism is based on the Enhanced Full Rate speech codec defined in GSM 06.60 [6]. + +# --- 9 Enhanced Full Rate speech channel lost speech frame substitution and muting + +The Enhanced Full Rate speech frame substitution and muting function is described in GSM 06.61 [7]. + +In the receiver, frames may be lost due to transmission errors or frame stealing. GSM 06.61 [7] describes the actions to be taken in these cases, both for lost speech frames and for lost SID frames in DTX operation. + +In order to mask the effect of an isolated lost frame, the lost speech frame is substituted by a predicted frame based on previous frames. Insertion of silence frames is not allowed. For several subsequent lost frames, a muting technique shall be used to indicate to the listener that transmission has been interrupted. + +# --- 10 Enhanced Full Rate codec homing + +The GSM Enhanced Full Rate speech transcoder, VAD, DTX system and comfort noise parts of the audio processing functions (see figure 1) are defined in bit exact arithmetic. Consequently, they shall react on a given input sequence always with the corresponding bit exact output sequence, provided that the internal state variables are also always exactly in the same state at the beginning of the experiment. + +The input test sequences provided in GSM 06.54 [5] shall force the corresponding output test sequences, provided that the tested modules are in their home-state when starting. + +The modules may be set into their home states by provoking the appropriate homing-functions. + +NOTE: This is normally done during reset (initialization of the codec). + +Special inband signalling frames (encoder-homing-frame and decoder-homing-frame) described in GSM 06.60 [6] have been defined to provoke these homing-functions also in remotely placed modules. + +This mechanism is specified to support three main areas: + +- type approval of mobile terminal equipment; +- type approval of infrastructure equipment; +- remote control and testing for operation and maintenance. + +At the end of the first received homing frame, the audio functions that are defined in a bit exact way shall go into their predefined home states. The output corresponding to the first homing frame is dependent on the codec state when the frame was received. Any consecutive homing frames shall produce corresponding homing frames at the output. + +# --- 11 Alternative Enhanced Full Rate implementation using the Adaptive Multi Rate 12.2 kbit/s mode + +The 12.2 kbit/s mode of the Adaptive Multi Rate speech coder described in TS 26.071 is functionally equivalent to the GSM Enhanced Full Rate speech coder. An alternative implementation of the Enhanced Full Rate speech service based on the 12.2 kbit/s mode of the Adaptive Multi Rate coder is allowed. Alternative implementations shall implement the functionality specified in TS 26.071 for the 12.2 kbit/s mode, with the difference that the DTX transmission format + +from GSM 06.81, the comfort noise generation from GSM 06.62 and the decoder-homing-frame from GSM 06.60 shall be used. + +Verification of compliance using the alternative implementation is achieved by use of a set of digital test sequences given in GSM 06.54. + +NOTE: The alternative implementation of the GSM Enhanced Full Rate speech coder incurs an additional 5ms look-ahead delay, and the implementation in this specification (GSM 06.51) is the preferred option. + +## Annex A (informative): Change History + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|--------------------------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#21 | | | | 4.0.1 | ETSI Publication | +| SMG#20 | | | | 5.1.2 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#28 | P-99-139 | A003 | Figure 1, Sect.5 | 7.0.0 | Addition of mu-law (PCS 1900) | +| | | | | 7.0.2 | Update to Version 7.0.2 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| SMG#32 | P-00-273 | A008 | 4 and 11 | 8.1.0 | Alternative EFR implementation using the AMR 12.2 mode | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----------------------------------------------------------------------|--------|--------| +| Date | TSG SA# | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 12-2000 | 10 | SP-000572 | A013 | | Definition of the homing frame for the alternative EFR implementation | 8.1.0 | 8.2.0 | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46053/raw.md b/marked/Rel-18/46_series/46053/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8182f1a3844bd116da1ff6c5e23cc606e8a63dfb --- /dev/null +++ b/marked/Rel-18/46_series/46053/raw.md @@ -0,0 +1,283 @@ + + +# 3GPP TS 46.053 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec (Release 18)** + +![GSM logo with the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS'](64662465bba247703fdec49c8f3309f9_img.jpg) + +The GSM logo consists of the letters 'GSM' in a stylized blue font, with a small red square to the right of the 'M'. Below the logo, the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' is written in a smaller blue font. + +GSM logo with the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' + +![3GPP logo with a signal icon](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo features the letters '3GPP' in a bold, black, stylized font. Below the 'P', there is a red signal icon consisting of three curved lines. A small 'TM' symbol is located to the top right of the 'P'. + +3GPP logo with a signal icon + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|----------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 C code structure ..... | 6 | +| 4.1 Contents of the C source code disk..... | 6 | +| 4.2 Program execution..... | 7 | +| 4.3 Code hierarchy ..... | 7 | +| Annex A (informative): Change History ..... | 13 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document provides the bit exact definition of the Enhanced Full Rate (EFR) speech traffic codec for the digital cellular telecommunications system. + +An electronic attachment accompanies the present document, containing clause 5, the bit-exact ANSI-C code for the Enhanced Full Rate speech transcoder. + +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 contains an electronic copy of the ANSI-C code for the GSM Enhanced Full Rate codec. The ANSI-C code is necessary for a bit exact implementation of the Enhanced Full Rate speech transcoder (GSM 06.60 [3]), Voice Activity Detection (GSM 06.82 [7]), comfort noise (GSM 06.62 [5]), Discontinuous Transmission (GSM 06.81 [6]) and example solutions for substituting and muting of lost frames (GSM 06.61 [4]). + +# --- 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test sequences for the GSM Enhanced Full Rate (EFR) speech codec". +- [3] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding". +- [4] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frame for Enhanced Full Rate (EFR) speech traffic channels". +- [5] GSM 06.62: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels". +- [6] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels". +- [7] GSM 06.82: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD) for Enhanced Full Rate (EFR) speech traffic channels". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +Definition of terms used in the present document can be found in GSM 06.60 [3], GSM 06.61 [4], GSM 06.62 [5], GSM 06.81 [6] and GSM 06.82 [7]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------------| +| ANSI | American National Standards Institute | +| DS-HD | Double Sided High Density | +| ETS | European Telecommunication Standard | +| GSM | Global System for Mobile communications | +| I/O | Input/Output | +| ROM | Read Only Memory | + +For abbreviations not given in this clause see GSM 01.04 [1]. + +# --- 4 C code structure + +This clause gives an overview of the structure of the bit-exact C code and provides an overview of the contents and organization of the archive en\_300724v080000o0.ZIP which accompanies the present document. + +The C code has been verified on the following systems: + +- Sun Microsystems 1) workstations and Sun Microsystems cc compiler and gcc compiler; +- IBM 2) PC/AT compatible computers and Borland Turbo-C++ 3) compiler; +- Hewlett Packard's 4) workstations and HP cc compiler; + +ANSI-C 9899 was selected as the programming language because portability was desirable. + +## 4.1 Contents of the C source code disk + +The C code disk has all of the files in the root level. + +In this disk, the files with suffix "c" contain the source code and the files with suffix "h" are the header files. The ROM data is contained mostly in files with suffix "tab". All text files are formatted such that they are correct for an IBM PC/AT compatible. + +The archive en\_300724v080000o0.ZIP which accompanies the present document contains one speech coder installation verification data file, "spch\_dos.inp". The reference encoder output file is named "spch\_dos.cod", the reference decoder input file is named "spch\_dos.dec" and the reference decoder output file is named "spch\_dos.out". These four files are formatted such that they are correct for an IBM PC/AT compatible. The same files with reversed byte order of the 16 bit words are named "spch\_unx.inp", "spch\_unx.cod", "spch\_unx.dec" and "spch\_unx.out", respectively. + +In an IBM PC/AT compatible platform, the installation verification can be performed by running the batch file "ts\_dos.bat". In most UNIX platforms, the installation verification can be performed by running the batch file "ts\_unx.bat". Final verification is to be performed using the GSM Enhanced Full Rate test sequences described in GSM 06.54 [2]. + +Makefiles are provided for the three platforms in which the C code has been verified (listed above). Once the software is installed, this directory will have compiled versions of *coder* and *decoder* (the bit-exact C executables of the speech codec), *ed\_iface* (interface program between coder and decoder) and all the object files. + +The programs *coder* and *decoder* are the GSM Enhanced Full Rate encoder and decoder executable files, respectively. A third program, *ed\_iface*, is also contained in this directory. This is the program which provides the format conversion between the encoder output file format and the decoder input file format. + +--- + +1) Registered trade mark of Sun Microsystems + +2) Registered trade mark of International Business Machines + +3) Registered trade mark of Borland + +4) Registered trade mark of Hewlett Packard + +## 4.2 Program execution + +The GSM enhanced full rate speech codec is implemented as three separate programs: + +- (*coder*) speech encoder; +- (*ed\_iface*) encoder/decoder interface; +- (*decoder*) speech decoder. + +For encoding using the *coder* program, the input is a binary speech file (\*.inp) and the output is a binary encoded parameter file (\*.cod). For decoding using the *decoder* program, the input is a binary parameter file (\*.dec) and the output is a binary synthesized speech file (\*.out). + +NOTE: The format for the parameter input file required for decoding (\*.dec) is not the same as the format of the parameter output file generated by encoding (\*.cod). The *ed\_iface* program will translate an \*.cod file into a \*.dec file. + +See the file readme.txt for more information on how to run the *coder*, *ed\_iface* and *decoder* programs. + +## 4.3 Code hierarchy + +Figures 1 to 5 are call graphs that show the functions used in the speech codec, including the functions of VAD, DTX, and comfort noise generation. + +The encode call graph is broken down into three separate call graphs, and the decode call graph is broken down into two separate call graphs. Those clauses which are large are separated from the primary call tree and given their own call tree. Each vertical column represents a call level. For example, main() is at level 0, Coder\_12k2() at level 1, Int\_lpc2() at level 2, Lsp\_Az() at level 3, Get\_lsp\_pol() at level 4, etc. The basic operations are not counted as extending the depth, therefore the deepest level in this software is level 4. + +Some items have been omitted from this call graph. All standard C functions: printf(), fwrite(), etc. have been omitted. Also, no basic operations (add(), L\_add(), mac(), etc.) or double precision extended operations (e.g. L\_Extract()) appear in the graphs. The reset functions of the encoder and decoder are only visible as the functions reset\_enc and reset\_dec, respectively. There are several subroutine calls from inside these functions. + +The time order in the call graphs is from the bottom upwards as the processing of a frame advances. + +![Speech encoder call graph showing 'main' at the center with arrows pointing to various sub-functions like 'sid_codeword_encoding', 'Prm2bits_12k2', 'Int2bin', 'Lag_max', 'Lsp_Az', 'Get_lsp_pol', 'Pre_Process', 'encoder_homing_frame_test', 'reset_enc', 'Lsf_lsp', 'Reorder_lsf', 'Vq_subvec_s', 'Vq_subvec', 'Lsf_wt', 'update_lsf_history', 'aver_lsf_history', 'update_lsf_p_CN', 'Lsp_lsf', 'Chebbs', 'periodicity_update', 'Pitch_ol', 'Syn_filt', 'Residu', 'Weight_Ai', 'Int_lpc', 'Int_lpc2', 'Q_plsf_5', 'tx_dtx', 'vad_computation', 'Az_lsp', 'Levinson', 'Lag_window', 'Autocorr'.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the call graph for a speech encoder. At the center is the **main** function. Arrows radiate from **main** to several sub-functions: **sid\_codeword\_encoding**, **Prm2bits\_12k2**, **CN\_encoding**, **Coder\_12k2**, **Pre\_Process**, **encoder\_homing\_frame\_test**, and **reset\_enc**. **sid\_codeword\_encoding** points to **Int2bin**. **Prm2bits\_12k2** points to **periodicity\_update**. **CN\_encoding** points to **Pitch\_ol**. **Coder\_12k2** points to **Syn\_filt**, **Residu**, **Weight\_Ai**, **Int\_lpc**, **Int\_lpc2**, **Q\_plsf\_5**, **tx\_dtx**, **vad\_computation**, **Az\_lsp**, **Levinson**, **Lag\_window**, and **Autocorr**. **Pre\_Process** points to **Lag\_max**. **encoder\_homing\_frame\_test** points to **Lsp\_Az**. **reset\_enc** points to **Lsf\_lsp**, **Reorder\_lsf**, **Vq\_subvec\_s**, **Vq\_subvec**, **Lsf\_wt**, **update\_lsf\_history**, **aver\_lsf\_history**, **update\_lsf\_p\_CN**, **Lsp\_lsf**, and **Chebbs**. **periodicity\_update** points to **Lag\_max**. **Pitch\_ol** points to **Lsp\_Az**. **Syn\_filt** points to **Get\_lsp\_pol**. **Residu** points to **Int\_sqrt**. **Weight\_Ai** points to **Lsf\_lsp**. **Int\_lpc** points to **Reorder\_lsf**. **Int\_lpc2** points to **Vq\_subvec\_s**. **Q\_plsf\_5** points to **Vq\_subvec**. **tx\_dtx** points to **Lsf\_wt**. **vad\_computation** points to **update\_lsf\_history**. **Az\_lsp** points to **aver\_lsf\_history**. **Levinson** points to **update\_lsf\_p\_CN**. **Lag\_window** points to **Lsp\_lsf**. **Autocorr** points to **Chebbs**. + +Speech encoder call graph showing 'main' at the center with arrows pointing to various sub-functions like 'sid\_codeword\_encoding', 'Prm2bits\_12k2', 'Int2bin', 'Lag\_max', 'Lsp\_Az', 'Get\_lsp\_pol', 'Pre\_Process', 'encoder\_homing\_frame\_test', 'reset\_enc', 'Lsf\_lsp', 'Reorder\_lsf', 'Vq\_subvec\_s', 'Vq\_subvec', 'Lsf\_wt', 'update\_lsf\_history', 'aver\_lsf\_history', 'update\_lsf\_p\_CN', 'Lsp\_lsf', 'Chebbs', 'periodicity\_update', 'Pitch\_ol', 'Syn\_filt', 'Residu', 'Weight\_Ai', 'Int\_lpc', 'Int\_lpc2', 'Q\_plsf\_5', 'tx\_dtx', 'vad\_computation', 'Az\_lsp', 'Levinson', 'Lag\_window', 'Autocorr'. + +Figure 1: Speech encoder call graph (see figures 2 and 3) + +![Speech encoder subframe processing call graph](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +This call graph illustrates the processing flow within a speech encoder subframe. The process begins with the **Coder\_12k2** block at the bottom, which outputs to a central junction. From this junction, multiple processing paths emerge: **q\_gain\_code**, **G\_code**, **build\_CN\_code**, **code\_10i40\_35bits**, **q\_gain\_pitch**, **G\_pitch**, **Convolve**, **Pred\_lt\_6**, **Enc\_lag6**, **Pitch\_fr6**, **Copy**, and **compute\_CN\_excitation\_gain**. The **q\_gain\_code** path leads to a junction for **aver\_gain\_code\_history**, **update\_gcode0\_CN**, **update\_gain\_code\_history\_tx**, **Pow2**, and **Log2**. The **build\_CN\_code** path leads to **pseudonoise** and **q\_p**. The **code\_10i40\_35bits** path leads to a junction for **build\_code**, **search\_10i40**, **cor\_h**, **set\_sign**, and **cor\_h\_x**. The **compute\_CN\_excitation\_gain** path leads to a junction for **Interpol\_6**, **Norm\_Corr**, **Inv\_sqrt**, and **Convolve**. + +Speech encoder subframe processing call graph + +Figure 2: Speech encoder subframe processing call graph + +![Voice Activity Detector (VAD) call graph showing vad_computation calling various sub-functions including vad_hangover, vad_decision, threshold_adaptation, tone_detection, spectral_comparison, predictor_values, acf_averaging, and energy_computation. tone_detection calls step_up. predictor_values calls step_up, compute_rav1, and schur_recursion.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` +graph LR; vad_computation --> vad_hangover; vad_computation --> vad_decision; vad_computation --> threshold_adaptation; vad_computation --> tone_detection; vad_computation --> spectral_comparison; vad_computation --> predictor_values; vad_computation --> acf_averaging; vad_computation --> energy_computation; tone_detection --> step_up; predictor_values --> step_up; predictor_values --> compute_rav1; predictor_values --> schur_recursion; +``` + +Voice Activity Detector (VAD) call graph showing vad\_computation calling various sub-functions including vad\_hangover, vad\_decision, threshold\_adaptation, tone\_detection, spectral\_comparison, predictor\_values, acf\_averaging, and energy\_computation. tone\_detection calls step\_up. predictor\_values calls step\_up, compute\_rav1, and schur\_recursion. + +Figure 3: Voice Activity Detector (VAD) call graph + +![Speech decoder call graph showing the hierarchy of functions starting from 'main'.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the call graph for a speech decoder. At the top level is the **main** function. It branches into four primary components: **Post\_Filter**, **Decoder\_12k2**, **decoder\_homing\_frame\_test**, and **reset\_dec**. The **Decoder\_12k2** component is the most complex, further branching into a large number of sub-functions. These include **Copy**, **Syn\_filt**, **agc2**, **d\_gain\_code**, **build\_CN\_code**, **dec\_10140\_35bits**, **d\_gain\_pitch**, **Pred\_It\_6**, **Dec\_lag6**, **Lsp\_Az**, **Int\_lpc**, **D\_plsf\_5**, **rx\_dtx**, **Get\_lsp\_pol**, **Lsp\_Az**, **update\_lsf\_history**, **Reorder\_lsf**, **Lsf\_lsp**, **interpolate\_CN\_lsf**, and **update\_lsf\_p\_CN**. The **d\_gain\_code** function further branches into **Inv\_sqr**, **Pow2**, **Log2**, **update\_gain\_code\_history\_rx**, **interpolate\_CN\_param**, **update\_gcode0\_CN**, **pseudonoise**, and **gmed5**. The **interpolate\_CN\_lsf** function branches into **interpolate\_CN\_param**. The **decoder\_homing\_frame\_test** component branches into **Bits2prm\_12k2**, which in turn branches into **Bin2int**. + +Speech decoder call graph showing the hierarchy of functions starting from 'main'. + +Figure 4: Speech decoder call graph (see figure 5) + +![Speech decoder postfilter call graph showing Post_Filter calling agc, preemphasis, Syn_filt, Set_zero, Copy, Residu, and Weight_Ai. The agc function further calls Inv_sqrt.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +graph LR + Post_Filter --> agc + Post_Filter --> preemphasis + Post_Filter --> Syn_filt + Post_Filter --> Set_zero + Post_Filter --> Copy + Post_Filter --> Residu + Post_Filter --> Weight_Ai + agc --> Inv_sqrt + +``` + +Speech decoder postfilter call graph showing Post\_Filter calling agc, preemphasis, Syn\_filt, Set\_zero, Copy, Residu, and Weight\_Ai. The agc function further calls Inv\_sqrt. + +**Figure 5: Speech decoder postfilter call graph** + +# Annex A (informative): Change History + +| Change history | | | | | | +|----------------|-----------|---------|-----------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments | +| SMG#23 | | | | 4.0.1 | ETSI Publication | +| SMG#20 | | | | 5.1.2 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | | +| 06-2018 | SA#80 | - | - | - | - | Version for Release 15 | 15.0.0 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46054/raw.md b/marked/Rel-18/46_series/46054/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..280659663495a72acba74d3c08fa801eb21d544d --- /dev/null +++ b/marked/Rel-18/46_series/46054/raw.md @@ -0,0 +1,759 @@ + + +# 3GPP TS 46.054 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Test sequences for the GSM Enhanced Full Rate (EFR) speech codec (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The GSM logo features the letters "GSM" in a stylized blue font. The "G" and "S" are connected at the top by a single horizontal bar. The "M" is composed of two "A"-like shapes joined at the top. Below the letters, the text "GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS" is written in a smaller, blue, sans-serif font. A small red square is positioned to the upper right of the "M", and a registered trademark symbol (®) is to the right of the "M". + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo consists of the letters "3GPP" in a bold, black, stylized font. The "3" is rounded, and the "G" and "P" are connected at the top by a single horizontal bar. Below the "P", there are three red curved lines representing signal waves. A trademark symbol (™) is located to the upper right of the "P". + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General ..... | 6 | +| 5 Test sequence format ..... | 6 | +| 5.1 File format ..... | 6 | +| 5.2 Codec homing ..... | 7 | +| 6 Speech codec test sequences..... | 8 | +| 6.1 Codec configuration ..... | 8 | +| 6.2 Speech codec test sequences ..... | 8 | +| 6.2.1 Speech encoder test sequences ..... | 8 | +| 6.2.2 Speech decoder test sequences ..... | 9 | +| 6.2.3 Codec homing sequence ..... | 9 | +| 7 DTX test sequences..... | 11 | +| 7.1 Codec configuration ..... | 11 | +| 7.2 DTX test sequences..... | 11 | +| 7.2.1 Predictor values computation ..... | 12 | +| 7.2.2 Spectral comparison ..... | 12 | +| 7.2.3 Threshold adaptation ..... | 12 | +| 7.2.4 Periodicity detection ..... | 12 | +| 7.2.5 Tone detection ..... | 12 | +| 7.2.6 Safety and initialisation ..... | 12 | +| 7.2.7 Comfort noise test sequence ..... | 12 | +| 7.2.8 Real speech and tones..... | 12 | +| 8 Sequences for finding the 20 ms framing of the GSM enhanced full rate speech encoder ..... | 13 | +| 8.1 Bit synchronisation..... | 13 | +| 8.2 Frame synchronisation ..... | 14 | +| 8.3 Formats and sizes of the synchronisation sequences ..... | 14 | +| 9 Trau Testing with 8 Bit A- and $\mu$ -law PCM Test Sequences ..... | 15 | +| 10 Alternative Enhanced Full Rate implementation using the Adaptive Multi Rate 12.2 kbit/s mode..... | 17 | +| Annex A (informative): Change History..... | 19 | + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +Test sequences for a bit exact implementation of the Enhanced Full Rate (EFR) speech transcoder are contained in the archive files which accompany the present document. + +The archive contains ZIP compressed files, as follows: + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Disk1_8 | Clause 10: Test sequences for the GSM Enhanced Full Rate (EFR) speech codec; Speech test sequences TEST0.xxx to TEST8.xxx. | +| Disk2_8 | Clause 10: Test sequences for the GSM Enhanced Full Rate (EFR) speech codec; Speech test sequences TEST09.xxx to TEST16.xxx. | +| Disk3_8 | Clause 10: Test sequences for the GSM Enhanced Full Rate (EFR) speech codec; Speech test sequences TEST17.xxx to TEST20.xxx, Codec homing and synchronisation sequences. | +| Disk4_8 | Clause 10: Test sequences for the GSM Enhanced Full Rate (EFR) speech codec; DTX test sequences. | +| Disk5_8 to
Disk8_8 | Clause 10: Test sequences for the GSM Enhanced Full Rate (EFR) speech codec; 8 bit A- and $\mu$ -law compressed test sequences for alternative TRAU testing. | +| amr122_efr | Test sequences for the GSM-EFR speech codec using the Adaptive Multi-Rate (AMR) speech codec mode MR122 (GSM 06.74) | + +The present document specifies the digital test sequences for the GSM enhanced full rate speech codec for the digital cellular telecommunications system. + +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 digital test sequences for the GSM enhanced full rate speech codec. These sequences test for a bit exact implementation of the enhanced full rate speech transcoder (GSM 06.60 [2]), Voice Activity Detection (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and the discontinuous transmission (GSM 06.81 [5]). + +# --- 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] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding". +- [3] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frames for Enhanced Full Rate (EFR) speech traffic channels". +- [4] GSM 06.62: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels". +- [5] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous Transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels". +- [6] GSM 06.82: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detection (VAD) for Enhanced Full Rate (EFR) speech traffic channels". +- [7] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec". +- [8] GSM 06.51: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech coding functions; General description". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +Definition of terms used in the present document can be found in GSM 06.60 [2], GSM 06.61 [3], GSM 06.62 [4], GSM 06.81 [5] and GSM 06.82 [6]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|-----------------------------------------| +| ETS | European Telecommunication Standard | +| GSM | Global System for Mobile communications | + +For abbreviations not given in this subclause see GSM 01.04 [1]. + +# --- 4 General + +Digital test sequences are necessary to test for a bit exact implementation of the enhanced full rate speech transcoder (GSM 06.60 [2]), Digital test Voice Activity Detection (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and the discontinuous transmission (GSM 06.81 [5]). + +The test sequences may also be used to verify installations of the ANSI C code in GSM 06.53 [7]. + +Clause 5 describes the format of the files which contain the digital test sequences. Clause 6 describes the test sequences for the speech transcoder. Clause 7 describes the test sequences for the VAD, comfort noise and discontinuous transmission. + +Clause 8 describes the method by which synchronisation is obtained between the test sequences and the speech codec under test. + +Clause 9 describes the alternative acceptance testing of the speech encoder and decoder in the TRAU by means of 8 bit A- or $\mu$ -law compressed test sequences on the A-Interface. + +Test sequences for an alternative and fully interoperable implementation using as a basis the 12.2 kbit/s mode of the Adaptive Multi Rate speech coder are described in section 10. + +Electronic copies of the digital test sequences are provided as clause 10, these digital test sequences are contained in the archive ts\_100725v080100p0.zip which accompanies the present document. + +# --- 5 Test sequence format + +This clause provides information on the format of the digital test sequences for the GSM enhanced full rate speech transcoder (GSM 06.60 [2]), Voice Activity Detection (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and the discontinuous transmission (GSM 06.81 [5]). + +## 5.1 File format + +The test sequence files are provided in archive ts\_100725v080100p0.zip which accompanies the present document. + +Following decompression, four types of file are provided: + +- Files for input to the GSM enhanced full rate speech encoder: \*.INP +- Files for comparison with the encoder output: \*.COD +- Files for input to the GSM enhanced full rate speech decoder: \*.DEC + +- Files for comparison with the decoder output: \*.OUT + +The \*.DEC files are generated from the corresponding \*.COD files. + +Tables 1, 2, 3 and 4 define the formats of the four types of file. + +Each speech parameter within the speech frame of 244 bits/20 ms is contained in a serial string of 16 bit words, where each word contains the value of one bit of the parameter. In each string of $n$ 16 bit words containing the $n$ bits of a parameter, the most significant bit of the parameter is written first, and the least significant bit is written last. The bit value contained in a single 16 bit word is either 0x0000 or 0x0001 (right justified) for the binary values of “0” and “1”, respectively. See table 6 of GSM 06.60 [2] for the order of occurrence and bit allocation of speech parameters within the speech frame of 244 bits/20 ms. + +The samples in the encoder input signal and in the decoder output signal are left justified. + +## 5.2 Codec homing + +Each \*.INP file includes two homing frames at the start of the test sequence. The function of these frames is to reset the speech encoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (GSM 06.53 [7]), all speech encoder output frames shall be identical to the corresponding frame in the \*.COD file. In the case of a correct hardware implementation undergoing testing, the first speech encoder output frame is undefined and need not be identical to the first frame in the \*.COD file, but all remaining speech encoder output frames shall be identical to the corresponding frames in the \*.COD file. + +Each \*.DEC file includes two homing frames at the start of the test sequence. The function of these frames is to reset the speech decoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (GSM 06.53 [7]), all speech decoder output frames shall be identical to the corresponding frame in the \*.OUT file. In the case of a correct hardware implementation undergoing testing, the first speech decoder output frame is undefined and need not be identical to first frame in the \*.OUT file, but all remaining speech decoder output frames shall be identical to the corresponding frames in the \*.OUT file. + +**Table 1: Encoder input sequence (\*.INP) format** + +| Name | Description | No. of bits | Justification | +|------|----------------------|-------------|---------------| +| s(n) | Encoder input signal | 13 | Left | + +**Table 2: Encoder output sequence (\*.COD) format** + +| Name | Description | No. of bits | Justification | +|------------------------|---------------------------------------------------------------|-------------|---------------| +| Speech parameters | | | | +| SPEECH | Serial stream of speech parameter bits to the channel encoder | 244 | Right | +| Additional information | | | | +| VAD | Voice activity detection flag | 1 | Right | +| SP | SP flag | 1 | Right | + +**Table 3: Decoder input sequence (\*.DEC) format** + +| Name | Description | No. of bits | Justification | +|------------------------|---------------------------------------------------------------|-------------|---------------| +| Additional information | | | | +| BFI | Bad Frame Indicator flag | 1 | Right | +| Speech parameters | | | | +| SPEECH | Serial stream of speech parameter bits to the channel encoder | 244 | Right | +| Additional information | | | | +| SID | Silence Descriptor flag | 1 | Right | +| TAF | Time Alignment Flag | 1 | Right | + +**Table 4: Decoder output sequence (\*.OUT) format** + +| Name | Description | No. of bits | Justification | +|-------|-----------------------|-------------|---------------| +| s'(n) | Decoder output signal | 13 | Left | + +# 6 Speech codec test sequences + +This clause describes the test sequences designed to exercise the GSM enhanced full rate speech transcoder (GSM 06.60 [2]). + +## 6.1 Codec configuration + +The speech encoder shall be configured to operate in the non-DTX mode. The VAD and SP flags shall be set to 1 at the speech encoder output. + +## 6.2 Speech codec test sequences + +Table 5 lists the location and size of the speech codec test sequences. + +### 6.2.1 Speech encoder test sequences + +Twenty-one encoder input sequences are provided. Note that for the input sequences TEST0.INP to TEST3.INP, the amplitude figures are given in 13-bit precision. The active speech levels are given in dBov. + +- TEST0.INP - Synthetic harmonic signal. The pitch delay varies slowly from 18 to 143.5 samples. The minimum and maximum amplitudes are -997 and +971. +- TEST1.INP - Synthetic harmonic signal. The pitch delay varies slowly from 144 down to 18.5 samples. Amplitudes at saturation point -4096 and +4095. +- TEST2.INP - Sinusoidal sweep varying from 150 Hz to 3400 Hz. Amplitudes $\pm 1250$ . +- TEST3.INP - Sinusoidal sweep varying from 150 Hz to 3400 Hz. Amplitudes $\pm 4000$ . +- TEST4.INP - Female speech, active speech level: -19.4 dBov, flat frequency response. +- TEST5.INP - Male speech, active speech level: -18.7 dBov, flat frequency response. +- TEST6.INP - Female speech, ambient noise, active speech level: -35.0 dBov, flat frequency response. +- TEST7.INP - Female speech, ambient noise, active speech level: -25.0 dBov, flat frequency response. +- TEST8.INP - Female speech, ambient noise, active speech level: -15.6 dBov, flat frequency response. +- TEST9.INP - Female speech, car noise, active speech level: -35.5 dBov, flat frequency response. +- TEST10.INP - Female speech, car noise, active speech level: -26.1 dBov, flat frequency response. +- TEST11.INP - Female speech, car noise, active speech level: -15.8 dBov, flat frequency response. +- TEST12.INP - Male speech, ambient noise, active speech level: -34.9 dBov, flat frequency response. +- TEST13.INP - Male speech, ambient noise, active speech level: -24.8 dBov, flat frequency response. +- TEST14.INP - Male speech, ambient noise, active speech level: -15.0 dBov, flat frequency response. +- TEST15.INP - Male speech, babble noise, active speech level: -34.1 dBov, flat frequency response. +- TEST16.INP - Male speech, babble noise, active speech level: -24.3 dBov, flat frequency response. +- TEST17.INP - Male speech, babble noise, active speech level: -14.4 dBov, flat frequency response. +- TEST18.INP - Female speech, ambient noise, active speech level: -26.0 dBov, modified IRS frequency response, with many zero frames. +- TEST19.INP - Male speech, ambient noise, active speech level: -36.0 dBov, modified IRS frequency response, with many zero frames. +- TEST20.INP - Sequence for exercising the LPC vector quantisation codebooks and ROM tables of the codec. + +The TEST0.INP and TEST1.INP sequences were designed to test the pitch lag of the GSM enhanced full rate speech encoder. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST0.COD and TEST1.COD sequences, respectively. + +The TEST2.INP and TEST3.INP sequences are particularly suited for testing the LPC analysis, as well as for finding saturation problems. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST2.COD and TEST3.COD sequences, respectively. + +The TEST4.INP and TEST5.INP sequences contain a lot of low-frequency components. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST4.COD and TEST5.COD sequences, respectively. + +The TEST18.INP and TEST19.INP sequences contain some “all zeros” frames (silence) in between segments of speech. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST18.COD and TEST19.COD sequences, respectively. + +The TEST20.INP sequence was designed to force the encoder to select each of the LPC code indices and each but one of the the ROM table indices of the codec. + +The remaining sequences (TEST6.INP to TEST17.INP) were selected on the basis of bringing various input characteristics (background noise) and levels to the test sequence set. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST6.COD to TEST17.COD sequences, respectively. + +### 6.2.2 Speech decoder test sequences + +Twenty-one speech decoder input sequences TESTXX.DEC (XX = 0..20) are provided. These are derived from the corresponding TESTXX.INP sequences. In a correct implementation, the resulting speech decoder output shall be identical to the corresponding TESTXX.OUT sequences. + +### 6.2.3 Codec homing sequence + +In addition to the test sequences described above, two homing sequences are provided to assist in codec testing. TEST21.INP contains one encoder-homing-frame. TEST21.DEC contains one decoder-homing-frame. The use of these sequences is described in GSM 06.51 [8]. + +Table 5: Location and size of speech codec test sequences + +| Disk No. | File Name | No. of frames | Size (bytes) | +|----------|------------|---------------|--------------| +| 1/8 | TEST0.INP | 285 | 91 200 | +| 1/8 | TEST0.COD | | 140 220 | +| 1/8 | TEST0.DEC | | 140 790 | +| 1/8 | TEST0.OUT | | 91 200 | +| 1/8 | TEST1.INP | 285 | 91 200 | +| 1/8 | TEST1.COD | | 140 220 | +| 1/8 | TEST1.DEC | | 140 790 | +| 1/8 | TEST1.OUT | | 91 200 | +| 1/8 | TEST2.INP | 402 | 128 640 | +| 1/8 | TEST2.COD | | 197 784 | +| 1/8 | TEST2.DEC | | 198 588 | +| 1/8 | TEST2.OUT | | 128 640 | +| 1/8 | TEST3.INP | 402 | 128 640 | +| 1/8 | TEST3.COD | | 197 784 | +| 1/8 | TEST3.DEC | | 198 588 | +| 1/8 | TEST3.OUT | | 128 640 | +| 1/8 | TEST4.INP | 301 | 96 320 | +| 1/8 | TEST4.COD | | 148 092 | +| 1/8 | TEST4.DEC | | 148 694 | +| 1/8 | TEST4.OUT | | 96 320 | +| 1/8 | TEST5.INP | 224 | 71 680 | +| 1/8 | TEST5.COD | | 110 208 | +| 1/8 | TEST5.DEC | | 110 656 | +| 1/8 | TEST5.OUT | | 71 680 | +| 1/8 | TEST6.INP | 335 | 107 200 | +| 1/8 | TEST6.COD | | 164 820 | +| 1/8 | TEST6.DEC | | 165 490 | +| 1/8 | TEST6.OUT | | 107 200 | +| 1/8 | TEST7.INP | 363 | 116 160 | +| 1/8 | TEST7.COD | | 178 596 | +| 1/8 | TEST7.DEC | | 179 322 | +| 1/8 | TEST7.OUT | | 116 160 | +| 1/8 | TEST8.INP | 340 | 108 800 | +| 1/8 | TEST8.COD | | 167 280 | +| 1/8 | TEST8.DEC | | 167 960 | +| 1/8 | TEST8.OUT | | 108 800 | +| 2/8 | TEST9.INP | 407 | 130 240 | +| 2/8 | TEST9.COD | | 200 244 | +| 2/8 | TEST9.DEC | | 201 058 | +| 2/8 | TEST9.OUT | | 130 240 | +| 2/8 | TEST10.INP | 383 | 122 560 | +| 2/8 | TEST10.COD | | 188 436 | +| 2/8 | TEST10.DEC | | 189 202 | +| 2/8 | TEST10.OUT | | 122 560 | +| 2/8 | TEST11.INP | 367 | 117 440 | +| 2/8 | TEST11.COD | | 180 564 | +| 2/8 | TEST11.DEC | | 181 298 | +| 2/8 | TEST11.OUT | | 117 440 | +| 2/8 | TEST12.INP | 298 | 95 360 | +| 2/8 | TEST12.COD | | 146 616 | +| 2/8 | TEST12.DEC | | 147 212 | +| 2/8 | TEST12.OUT | | 95 360 | +| 2/8 | TEST13.INP | 338 | 108 160 | +| 2/8 | TEST13.COD | | 166 296 | +| 2/8 | TEST13.DEC | | 166 972 | +| 2/8 | TEST13.OUT | | 108 160 | +| 2/8 | TEST14.INP | 318 | 101 760 | +| 2/8 | TEST14.COD | | 156 456 | +| 2/8 | TEST14.DEC | | 157 092 | +| 2/8 | TEST14.OUT | | 101 760 | + +(continued) + +**Table 5 (concluded): Location and size of speech codec test sequences** + +| Disk No. | File Name | No. of frames | Size (bytes) | +|----------|------------|---------------|--------------| +| 2/8 | TEST15.INP | 328 | 104 960 | +| 2/8 | TEST15.COD | | 161 376 | +| 2/8 | TEST15.DEC | | 162 032 | +| 2/8 | TEST15.OUT | | 104 960 | +| 2/8 | TEST16.INP | 354 | 113 280 | +| 2/8 | TEST16.COD | | 174 168 | +| 2/8 | TEST16.DEC | | 174 876 | +| 2/8 | TEST16.OUT | | 113 280 | +| 3/8 | TEST17.INP | 316 | 101 120 | +| 3/8 | TEST17.COD | | 155 472 | +| 3/8 | TEST17.DEC | | 156 104 | +| 3/8 | TEST17.OUT | | 101 120 | +| 3/8 | TEST18.INP | 402 | 128 640 | +| 3/8 | TEST18.COD | | 197 784 | +| 3/8 | TEST18.DEC | | 198 588 | +| 3/8 | TEST18.OUT | | 128 640 | +| 3/8 | TEST19.INP | 402 | 128 640 | +| 3/8 | TEST19.COD | | 197 784 | +| 3/8 | TEST19.DEC | | 198 588 | +| 3/8 | TEST19.OUT | | 128 640 | +| 3/8 | TEST20.INP | 631 | 201 920 | +| 3/8 | TEST20.COD | | 310 452 | +| 3/8 | TEST20.DEC | | 311 714 | +| 3/8 | TEST20.OUT | | 201 920 | +| 3/8 | TEST21.INP | 1 | 320 | +| 3/8 | TEST21.DEC | | 494 | + +# 7 DTX test sequences + +This subclause describes the test sequences designed to exercise the VAD algorithm (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and discontinuous transmission (GSM 06.81 [5]). + +## 7.1 Codec configuration + +The VAD, comfort noise and discontinuous transmission shall be tested in conjunction with the speech encoder (GSM 06.60 [2]). The speech encoder shall be configured to operate in the DTX mode defined in GSM 06.62 [4]. + +## 7.2 DTX test sequences + +Each DTX test sequence consists of four files: + +- Files for input to the GSM enhanced full rate speech encoder: \*.INP +- Files for comparison with the encoder output: \*.COD +- Files for input to the GSM enhanced full rate speech decoder: \*.DEC +- Files for comparison with the decoder output: \*.OUT + +The \*.DEC files are generated from the corresponding \*.COD files. + +In a correct implementation, the speech encoder parameters generated by the \*.INP file shall be identical to those specified in the \*.COD file; and the speech decoder output generated by the \*.DEC file shall be identical to that specified in the \*.OUT file. + +Table 6 lists the DTX test sequences and their size in frames. + +### 7.2.1 Predictor values computation + +The computation of the predictor values described in GSM 06.82 [6] is not tested explicitly, since the results from the computation are tested many times via the spectral comparison and threshold adaptation tests. + +### 7.2.2 Spectral comparison + +The spectral comparison algorithm described in GSM 06.82 [6] is tested by the following test sequence: + +- DTX01.\* + +### 7.2.3 Threshold adaptation + +The threshold adaptation algorithm described in GSM 06.82 [6] is tested by the following test sequence: + +- DTX02.\* + +### 7.2.4 Periodicity detection + +The periodicity detection algorithm described in GSM 06.82 [6] is tested by the following test sequence: + +- DTX03.\* + +### 7.2.5 Tone detection + +The tone detection algorithm described in GSM 06.82 [6] is tested by the following test sequence: + +- DTX04.\* + +### 7.2.6 Safety and initialisation + +This sequence checks the safety paths used to prevent zero values being passed to the norm function. It checks the functions described in the adaptive filtering and energy computation, and the prediction values computation given in GSM 06.82 [6]. This sequence also checks the initialisation of thvad and the rvad array: + +- DTX05.\* + +### 7.2.7 Comfort noise test sequence + +The test sequences described in sub-subclauses 7.2.2 to 7.2.6 are designed to exercise the VAD described in GSM 06.82 [6] and the discontinuous transmission described in GSM 06.81 [5]. The following test sequence is defined to exercise the comfort noise algorithm described in GSM 06.62 [4]: + +- DTX06.\* + +### 7.2.8 Real speech and tones + +The test sequences cannot be guaranteed to find every possible error. There is therefore a small possibility that an incorrect implementation produces the correct output for the test sequences, but fails with real signals. Consequently, an extra sequence is included, which consists of very clean speech, barely detectable speech and a swept frequency tone: + +- DTX07.\* + +NOTE: Some of the DTX test sequences contain homing frames. The DTX test sequences are therefore only suitable for testing a single transcoding. + +**Table 6: Location and size of DTX test sequences** + +| Disk No. | File Name | No. of Frames | size (bytes) | | | | +|----------|-----------|---------------|--------------|---------|---------|---------| +| | | | *.INP | *.COD | *.DEC | *.OUT | +| 4/8 | DTX01 | 710 | 227 200 | 349 320 | 350 740 | 227 200 | +| 4/8 | DTX02 | 933 | 298 560 | 459 036 | 460 902 | 298 560 | +| 4/8 | DTX03 | 156 | 49 920 | 76 752 | 77 064 | 49 920 | +| 4/8 | DTX04 | 245 | 78 400 | 120 540 | 121 030 | 78 400 | +| 4/8 | DTX05 | 56 | 17 920 | 27 552 | 27 664 | 17 920 | +| 4/8 | DTX06 | 771 | 246 720 | 379 332 | 380 874 | 246 720 | +| 4/8 | DTX07 | 1188 | 380 160 | 584 496 | 586 872 | 380 160 | + +# 8 Sequences for finding the 20 ms framing of the GSM enhanced full rate speech encoder + +When testing the decoder, alignment of the test sequences used to the decoder framing is achieved by the air interface (testing of MS) or can be reached easily on the Abis-interface (testing on network side). + +When testing the encoder, usually there is no information available about where the encoder starts its 20 ms segments of speech input to the encoder. + +In the following, a procedure is described to find the 20 ms framing of the encoder using special synchronisation sequences. This procedure can be used for MS as well as for network side. + +Synchronisation can be achieved in two steps. First, bit synchronisation has to be found. In a second step, frame synchronisation can be determined. This procedure takes advantage of the codec homing feature of the enhanced full rate codec, which puts the codec in a defined home state after the reception of the first homing frame. On the reception of further homing frames, the output of the codec is predefined and can be triggered to. + +## 8.1 Bit synchronisation + +The input to the speech encoder is a series of 13 bit long words (104 kbits/s, 13 bit linear PCM). When starting to test the speech encoder, no knowledge is available on bit synchronisation, i.e., where the encoder expects its least significant bits, and where it expects the most significant bits. + +The encoder homing frame consists of 160 samples, all set to zero with the exception of the least significant bit, which is set to one (0 0000 0000 0001 binary, or 0x0008 hex if written into 16 bit words left justified). If two such encoder homing frames are input to the encoder consecutively, the decoder homing frame is expected at the output as a reaction of the second encoder homing frame. + +Since there are only 13 possibilities for bit synchronisation, after a maximum of 13 trials bit synchronisation can be reached. In each trial three consecutive encoder homing frames are input to the encoder. If the decoder homing frame is not detected at the output, the relative bit position of the three input frames is shifted by one and another trial is performed. As soon as the decoder homing frame is detected at the output, bit synchronisation is found, and the first step can be terminated. + +The reason why three consecutive encoder homing frames are needed is that frame synchronisation is not known at this stage. To be sure that the encoder reads two complete homing frames, three frames have to be input. Wherever the encoder has its 20 ms segmentation, it will always read at least two complete encoder homing frames. + +An example of the 13 different frame triplets is given in sequence BITSYNC.INP (see table 7). + +## 8.2 Frame synchronisation + +Once bit synchronisation is found, frame synchronisation can be found by inputting one special frame that delivers 160 different output frames, depending on the 160 different positions that this frame can possibly have with respect to the encoder framing. + +This special synchronisation frame was found by taking one input frame and shifting it through the positions 0 to 159. The corresponding 160 encoded speech frames were calculated and it was verified that all 160 output frames were different. When shifting the input synchronisation frame, the samples at the beginning were set to 0x0008 hex, which corresponds to the samples of the encoder homing frame. + +Before inputting this special synchronisation frame to the encoder, again the encoder has to be reset by one encoder homing frame. A second encoder homing frame is needed to provoke a decoder homing frame at the output that can be triggered to. And since the framing of the encoder is not known at that stage, three encoder homing frames have to precede the special synchronisation frame to ensure that the encoder reads at least two homing frames, and at least one decoder homing frame is produced at the output, serving as a trigger for recording. + +The special synchronisation frame preceded by the three encoder homing frames are given in SEQSYNC.INP. The corresponding 160 different output frames are given in SYNC000.COD through SYNC159.COD. The three digit number in the filename indicates the number of samples by which the input was retarded with respect to the encoder framing. By a corresponding shift in the opposite direction, alignment with the encoder framing can be reached. + +## 8.3 Formats and sizes of the synchronisation sequences + +### BIT SYNC.INP: + +This sequence consists of 13 frame triplets. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero). + +The size of it is therefore: + +$$\text{SIZE (BITSYNC.INP)} = 13 * 3 * 160 * 2 \text{ bytes} = 12480 \text{ bytes}$$ + +### SEQSYNC.INP: + +This sequence consist of 3 encoder reset frames and the special synchronisation frame. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero). + +The size of it is therefore: + +$$\text{SIZE (SEQSYNC.INP)} = 4 * 160 * 2 \text{ bytes} = 1280 \text{ bytes}$$ + +### SYNCXXX.COD: + +These sequences consists of 1 encoder output frame each. They have the format of the speech encoder output test sequences (16 bit words right justified). The values of the VAD and SP flags are set to one in these files. + +The size of them is therefore: + +$$\text{SIZE (SYNCXXX.COD)} = (244 + 2) * 2 \text{ bytes} = 492 \text{ bytes}$$ + +Table 7 summarises this information. + +**Table 7: Location, size and justification of synchronisation sequences** + +| Disk No. | Purpose of Sequence | Name of Sequence | No. of Frames | Size in Bytes | Justification | +|----------|--------------------------------|------------------|---------------|---------------|---------------| +| 3/8 | Bit Synchronisation | BITSYNC.INP | 39 | 1 2480 | Left | +| 3/8 | Frame Synchronisation (input) | SEQSYNC.INP | 4 | 1 280 | Left | +| 3/8 | Frame Synchronisation (output) | SYNC000.COD | 1 | 492 | Right | +| 3/8 | | SYNC001.COD | 1 | 492 | Right | +| 3/8 | | SYNC002.COD | 1 | 492 | Right | +| " | | " | " | " | " | +| " | | " | " | " | " | +| " | | " | " | " | " | +| " | | " | " | " | " | +| 3/8 | | SYNC159.COD | 1 | 492 | Right | + +# 9 Trau Testing with 8 Bit A- and $\mu$ -law PCM Test Sequences + +In the previous clauses, tests for the transcoder in the TRAU are described, using 13 bit linear test sequences. However, these 13 bit test sequences require a special interface in the TRAU and do not allow testing in the field. In most cases the TRAU has to be set in special mode before testing. + +As an alternative, the speech codec tests in the TRAU can be performed using A- or $\mu$ -law compressed 8 bit PCM test sequences on the A interface. For this purpose modified input test sequences (\*-X.INP) are generated from the original sequences by A or $\mu$ law compression. As an input to the encoder they result in modified encoder output sequences (\*-X.COD). The same \*.dec decoder input sequences as in subclause 6.2.2. are then used to produce the output sequences \*-X.OUT, which are A- or $\mu$ compressed. + +The A- and $\mu$ -law compression and decompression does not change the homing frames at the encoder input. The format of all A- and $\mu$ -law PCM files \*-X.INP and \*-X.OUT is one sample (8 bit) per byte. The format of all other files is as described in clause 5. + +All files are contained in archive ts\_100725v080100p0.zip which accompanies the present document. The 'X' in the tables below with the filenames stands for A (A-law) and U ( $\mu$ -law), respectively. The decoder input files \*.dec are the same as in table 5 and are not described in this clause. + +Table 8: Location and size of compressed 8 bit PCM speech codec test sequences + +| Disk No. | File Name | No. of frames | Size (bytes) | +|----------|--------------|---------------|--------------| +| 5-8/8 | TEST0-X.INP | 285 | 45 600 | +| 5-8/8 | TEST0-X.COD | | 140 220 | +| 5-8/8 | TEST0-X.OUT | | 45 600 | +| 5-8/8 | TEST1-X.INP | 285 | 45 600 | +| 5-8/8 | TEST1-X.COD | | 140 220 | +| 5-8/8 | TEST1-X.OUT | | 45 600 | +| 5-8/8 | TEST2-X.INP | 402 | 64 320 | +| 5-8/8 | TEST2-X.COD | | 197 784 | +| 5-8/8 | TEST2-X.OUT | | 64 320 | +| 5-8/8 | TEST3-X.INP | 402 | 64 320 | +| 5-8/8 | TEST3-X.COD | | 197 784 | +| 5-8/8 | TEST3-X.OUT | | 64 320 | +| 5-8/8 | TEST4-X.INP | 301 | 48 160 | +| 5-8/8 | TEST4-X.COD | | 148 092 | +| 5-8/8 | TEST4-X.OUT | | 48 160 | +| 5-8/8 | TEST5-X.INP | 224 | 35 840 | +| 5-8/8 | TEST5-X.COD | | 110 208 | +| 5-8/8 | TEST5-X.OUT | | 35 840 | +| 5-8/8 | TEST6-X.INP | 335 | 53 600 | +| 5-8/8 | TEST6-X.COD | | 164 820 | +| 5-8/8 | TEST6-X.OUT | | 53 600 | +| 5-8/8 | TEST7-X.INP | 363 | 58 080 | +| 5-8/8 | TEST7-X.COD | | 178 596 | +| 5-8/8 | TEST7-X.OUT | | 58 080 | +| 5-8/8 | TEST8-X.INP | 340 | 54 400 | +| 5-8/8 | TEST8-X.COD | | 167 280 | +| 5-8/8 | TEST8-X.OUT | | 54 400 | +| 5-8/8 | TEST9-X.INP | 407 | 65 120 | +| 5-8/8 | TEST9-X.COD | | 200 244 | +| 5-8/8 | TEST9-X.OUT | | 65 120 | +| 5-8/8 | TEST10-X.INP | 383 | 61 280 | +| 5-8/8 | TEST10-X.COD | | 188 436 | +| 5-8/8 | TEST10-X.OUT | | 61 280 | +| 5-8/8 | TEST11-X.INP | 367 | 58 720 | +| 5-8/8 | TEST11-X.COD | | 180 564 | +| 5-8/8 | TEST11-X.OUT | | 58 720 | +| 5-8/8 | TEST12-X.INP | 298 | 47 680 | +| 5-8/8 | TEST12-X.COD | | 146 616 | +| 5-8/8 | TEST12-X.OUT | | 47 680 | +| 5-8/8 | TEST13-X.INP | 338 | 54 080 | +| 5-8/8 | TEST13-X.COD | | 166 296 | +| 5-8/8 | TEST13-X.OUT | | 54 080 | +| 5-8/8 | TEST14-X.INP | 318 | 50 880 | +| 5-8/8 | TEST14-X.COD | | 156 456 | +| 5-8/8 | TEST14-X.OUT | | 50 880 | +| 5-8/8 | TEST15-X.INP | 328 | 52 480 | +| 5-8/8 | TEST15-X.COD | | 161 376 | +| 5-8/8 | TEST15-X.OUT | | 52 480 | +| 5-8/8 | TEST16-X.INP | 354 | 56 640 | +| 5-8/8 | TEST16-X.COD | | 174 168 | +| 5-8/8 | TEST16-X.OUT | | 56 640 | +| 5-8/8 | TEST17-X.INP | 316 | 50 560 | +| 5-8/8 | TEST17-X.COD | | 155 472 | +| 5-8/8 | TEST17-X.OUT | | 50 560 | +| 5-8/8 | TEST18-X.INP | 402 | 64 320 | +| 5-8/8 | TEST18-X.COD | | 197 784 | +| 5-8/8 | TEST18-X.OUT | | 64 320 | +| 5-8/8 | TEST19-X.INP | 402 | 64 320 | +| 5-8/8 | TEST19-X.COD | | 197 784 | +| 5-8/8 | TEST19-X.OUT | | 64 320 | +| 5-8/8 | TEST20-X.INP | 631 | 100 960 | +| 5-8/8 | TEST20-X.COD | | 310 452 | +| 5-8/8 | TEST20-X.OUT | | 100 960 | +| 5-8/8 | TEST21-X.INP | 1 | 160 | + +**Table 9: Location and size of compressed 8 bit PCM DTX test sequences** + +| Disk No. | File Name | No. of Frames | size | | bytes | +|----------|-----------|---------------|---------|---------|---------| +| | | | *.INP | *.COD | *.OUT | +| 5-8/8 | DTX01-X | 710 | 113 600 | 349 320 | 113 600 | +| 5-8/8 | DTX02-X | 933 | 149 280 | 459 036 | 149 280 | +| 5-8/8 | DTX03-X | 156 | 24 960 | 76 752 | 24 960 | +| 5-8/8 | DTX04-X | 245 | 39 200 | 120 540 | 39 200 | +| 5-8/8 | DTX05-X | 56 | 8 960 | 27 552 | 8 960 | +| 5-8/8 | DTX06-X | 771 | 123 360 | 379 332 | 123 360 | +| 5-8/8 | DTX07-X | 1188 | 190 080 | 584 496 | 190 080 | + +In addition to the test sequences above, special input (seqsyncX.inp) and output (syncxxxX.cod) sequences for frame synchronization are provided. The X again stands for A and $\mu$ law compressed PCM. The synchronization procedure is described in clause 8. + +**Table 10: Location, size and justification of compressed 8 bit PCM test sequences** + +| Disk No. | Purpose of Sequence | Name of Sequence | No. of Frames | Size in Bytes | Justification | +|----------|--------------------------------|------------------|---------------|---------------|---------------| +| 5-8/8 | Frame Synchronisation (input) | SEQSYNCX.INP | 4 | 640 | - | +| 5-8/8 | Frame Synchronisation (output) | SYNC000X.COD | 1 | 492 | Right | +| 5-8/8 | | SYNC001X.COD | 1 | 492 | Right | +| 5-8/8 | | SYNC002X.COD | 1 | 492 | Right | +| " | | " | " | " | " | +| " | | " | " | " | " | +| " | | " | " | " | " | +| 5-8/8 | | SYNC159X.COD | 1 | 492 | Right | + +| | | | | | | +|-------|--------------------------------|--------------|---|-----|-------| +| 5-8/8 | Frame Synchronisation (output) | SYNC000X.COD | 1 | 492 | Right | +| 5-8/8 | | SYNC001X.COD | 1 | 492 | Right | +| 5-8/8 | | SYNC002X.COD | 1 | 492 | Right | +| " | | " | " | " | " | +| " | | " | " | " | " | +| " | | " | " | " | " | +| 5-8/8 | | SYNC159X.COD | 1 | 492 | Right | + +# 10 Alternative Enhanced Full Rate implementation using the Adaptive Multi Rate 12.2 kbit/s mode + +The 12.2 kbit/s mode of the Adaptive Multi Rate speech coder described in TS 26.071 is functionally equivalent to the GSM Enhanced Full Rate speech coder. An alternative implementation of the Enhanced Full Rate speech service based on the 12.2 kbit/s mode of the Adaptive Multi Rate coder is allowed. Alternative implementations shall implement the functionality specified in TS 26.071 for the 12.2 kbit/s mode, with the difference that the DTX transmission format from GSM 06.81, the comfort noise generation from GSM 06.62 and the decoder homing frame from GSM 06.60 shall be used. + +The test sequences are derived from the corresponding AMR test sequences. The modifications that were made and the use of the respective sequences are described below. The input sequences are identical to the AMR test input sequences \*.inp. + +## Speech codec test sequences + +- with DTX disabled + +t00.inp ... t22.inp (encoder input, from TS 26.074) + +t00\_efr.cod ... t22\_efr.cod (encoder output) + +t00\_efr.dec ... t22\_efr.dec (decoder input) + +t00\_efr.out ... t22\_efr.out (decoder output) + +- with DTX enabled, VAD option 1 + +Dtx1.inp ... Dtx4.inp (encoder input, from TS 26.074) + +Dtx1\_efr.cod ... Dtx4\_efr.cod (encoder output) + +Dtx1\_efr.dec ... Dtx4\_efr.dec (decoder input) + +Dtx1\_efr.out ... Dtx4\_efr.out (decoder output) + +- with DTX enabled, VAD option 2 + +Dt21.inp .... Dt24.inp (encoder input, from TS 26.074) + +Dt21\_efr.cod ... Dt24\_efr.cod (encoder output) + +Dt21\_efr.dec ... Dt24\_efr.dec (decoder input) + +Dt21\_efr.out ... Dt24\_efr.out (decoder output) + +The format of the \*.cod files is identical to the GSM\_EFR \*.cod file format (244 Data Bits, VadFlag, SpFlag equaling 246 Words per 20ms frame). The format of the \*.dec files is identical to the GSM\_EFR \*.dec file format, that is (Bfi, 244 Data Bits, Sid, Taf equaling 247 Words per frame (20ms). + +In summary, the differences to the AMR Mode MR122 test sequences are: + +- DTX handling (VadFlag and SpFlag instead of TxType; different SID frames) +- Decoder homing frame (Decoder homing frame for GSM\_EFR is different than for AMR MR122). + +## Annex A (informative): Change History + +| Change history | | | | | | +|----------------|-----------|---------|------------------|-------------|--------------------------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +| SMG#23 | | | | 4.0.1 | ETSI Publication | +| SMG#23 | | | | 5.1.0 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| SMG#32 | P-00-274 | A006 | 4 and new 10 | 8.1.0 | Alternative EFR implementation using the AMR 12.2 mode | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|---------------------------------------------------------------|--------|--------| +| Date | TSG SA# | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 12-2000 | 10 | SP-000573 | A011 | | Correction to the test vectors of the alternative EFR version | 8.1.0 | 8.2.0 | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | | | | | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46061/raw.md b/marked/Rel-18/46_series/46061/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..de692e4f8c5100d812c4af571646f80cbe7cb384 --- /dev/null +++ b/marked/Rel-18/46_series/46061/raw.md @@ -0,0 +1,325 @@ + + +# 3GPP TS 46.061 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Substitution and muting of lost frames for Enhanced Full Rate (EFR) speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +### **3GPP** + +## --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 General ..... | 6 | +| 5 Requirements ..... | 6 | +| 5.1 Error detection ..... | 6 | +| 5.2 Lost speech frames ..... | 6 | +| 5.3 First lost SID frame ..... | 6 | +| 5.4 Subsequent lost SID frames ..... | 6 | +| 6 Example solution..... | 6 | +| 6.1 Example solution for substitution and muting of lost speech frames ..... | 7 | +| 6.2 Example solution for substitution and muting of lost SID frames ..... | 9 | +| Annex A (informative): Change history ..... | 10 | + +## --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines a frame substitution and muting procedure which is used by the Receive (RX) Discontinuous Transmission (DTX) handler when one or more lost speech or Silence Descriptor (SID) frames are received from the Radio Sub System (RSS) within the digital cellular telecommunications system. + +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 a frame substitution and muting procedure which shall be used by the Receive (RX) Discontinuous Transmission (DTX) handler when one or more lost speech or Silence Descriptor (SID) frames are received from the Radio Sub System (RSS). + +The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS) and Mobile Stations (MS)s capable of supporting the enhanced Full Rate speech traffic channel. It is not mandatory to follow the bit exact implementation outlined in the present document and the corresponding C-source code. + +# --- 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] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [2] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding". +- [3] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels". +- [4] GSM 08.60: "Digital cellular telecommunications system (Phase 2+); Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels". + +# --- 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the following term and definition applies: + +**5-point median operation:** consists of sorting the 5 elements belonging to the set for which the median operation is to be performed in an ascending order according to their values, and selecting the third largest value of the sorted set as the median value. + +Further definitions of terms used in the present document can be found in GSM 06.60 [2], GSM 06.81 [3], GSM 05.03 [1] and GSM 08.60 [4]. + +### 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|---------------------------------------------------------| +| BFI | Bad Frame Indication from Radio Sub System | +| BSI_Abis | Bad Sub-block Indication obtained from A-bis CRC checks | +| CCU | Channel Coding Unit | +| CRC | Cyclic Redundancy Check | + +| | | +|---------|----------------------------------------| +| DTX | Discontinuous transmission | +| median5 | 5-point median operation | +| PrevBFI | Bad Frame Indication of Previous frame | +| RSS | Radio Sub System | +| RX | Receive | +| SID | SIlence Descriptor frame | +| TRAU | Transcoding Rate Adaptation Unit | + +# --- 4 General + +The purpose of frame substitution is to conceal the effect of lost frames. The purpose of muting the output in the case of several lost frames is to indicate the breakdown of the channel to the user and to avoid generating possible annoying sounds as a result from frame substitution procedure. + +The RSS indicates lost speech or SID frames by setting its Bad Frame Indication flag (BFI) based on its 3-bit and 8-bit CRCs and possibly other error detection mechanisms. The TRAU calculates from the CRCs inserted by the CCU in the TRAU frames one BSI\_Abis flag for every sub-block of speech parameters. If either one or more of these flags is set, the speech decoder shall either perform frame substitution or subframe substitution. + +The example solution provided in clause 6 applies only for bad frame handling on a complete speech frame basis. However some parts could be modified for substitution of bad sub-blocks. + +# --- 5 Requirements + +### 5.1 Error detection + +An error is detected and the BFI-flag is set-by the RSS according to the principle described in clause 4. + +### 5.2 Lost speech frames + +Normal decoding of lost speech frames would result in very unpleasant noise effects. In order to improve the subjective quality, lost speech frames shall be substituted with either a repetition or an extrapolation of the previous good speech frame(s). This substitution is done so that it will gradually decrease the output level, resulting in silencing of the output. Clause 6.1 gives an example solution. + +### 5.3 First lost SID frame + +A single lost SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied as described in GSM 06.81 [3]. + +### 5.4 Subsequent lost SID frames + +For the second lost SID frame, a muting technique shall be used on the comfort noise that will gradually decrease the output level (-3 dB/frame), resulting in silencing of the output of the decoder. + +For subsequent lost SID frames, the muting of the output shall be maintained. Clause 6.2 gives an example solution. + +# --- 6 Example solution + +The C-code of the following example is embedded in the bit exact software of the enhanced full rate codec. + +### 6.1 Example solution for substitution and muting of lost speech frames + +This example solution for substitution and muting is based on a state machine with seven states (figure 1). + +The system starts in state 0. Each time a bad frame is detected, the state counter is incremented by one and is saturated when it reaches 6. Each time a good speech frame is detected, the state counter is reset to zero, except when we are in state 6, where we set the state counter to 5. The state indicates the quality of the channel: the bigger the state counter, the worse the channel quality is. The control flow of the state machine can be described with the following C-code (**BFI** = bad frame indicator, **State** = state variable): + +``` +if(BFI != 0 ) + State = State + 1; +else if(State == 6) + State = 5; +else + State = 0; +if(State > 6 ) + State = 6; +``` + +In addition to this state machine, the **Bad Frame Flag** from the previous frame is checked (**PrevBFI**). The processing depends on the value of the **State**-variable. In states 0 and 5, the processing depends also on the two flags **BFI** and **PrevBFI**. + +The procedure can be described as follows: + +![Figure 1: State machine for controlling the bad frame substitution. The diagram shows a vertical sequence of seven states (STATE 0 to STATE 6) with transitions between them based on Bad Frame Indication (BFI) and Previous Bad Frame Indication (PrevBFI). STATE 0 is the initial state where BFI=0 and PrevBFI=0 or 1. Transitions to STATE 1, 2, 3, 4, and 5 occur when BFI=1. STATE 1 has PrevBFI=0, while STATE 2, 3, 4, and 5 have PrevBFI=1. STATE 5 has BFI=0 or 1. Transitions from STATE 1, 2, 3, 4, and 5 back to STATE 0 occur when BFI=0. STATE 6 is reached from STATE 5 when BFI=1 and PrevBFI=0 or 1. STATE 6 has a self-loop for BFI=1. A legend indicates that a black arrow represents a 'Bad frame (BFI=1)' and a grey arrow represents a 'Good frame (BFI=0)'.](35a7554182eb055209552843f341a1ae_img.jpg) + +``` + +graph TD + S0["STATE = 0 +BFI = 0 +PrevBFI = 0 or 1"] -- "Bad frame (BFI=1)" --> S1["STATE = 1 +BFI = 1 +PrevBFI = 0"] + S1 -- "Good frame (BFI=0)" --> S0 + S1 -- "Bad frame (BFI=1)" --> S2["STATE = 2 +BFI = 1 +PrevBFI = 1"] + S2 -- "Good frame (BFI=0)" --> S0 + S2 -- "Bad frame (BFI=1)" --> S3["STATE = 3 +BFI = 1 +PrevBFI = 1"] + S3 -- "Good frame (BFI=0)" --> S0 + S3 -- "Bad frame (BFI=1)" --> S4["STATE = 4 +BFI = 1 +PrevBFI = 1"] + S4 -- "Good frame (BFI=0)" --> S0 + S4 -- "Bad frame (BFI=1)" --> S5["STATE = 5 +BFI = 0 or 1 +PrevBFI = 1"] + S5 -- "Good frame (BFI=0)" --> S0 + S5 -- "Bad frame (BFI=1)" --> S6["STATE = 6 +BFI = 1 +PrevBFI = 0 or 1"] + S6 -- "Bad frame (BFI=1)" --> S6 + S6 -- "Good frame (BFI=0)" --> S5 + +``` + +Figure 1: State machine for controlling the bad frame substitution. The diagram shows a vertical sequence of seven states (STATE 0 to STATE 6) with transitions between them based on Bad Frame Indication (BFI) and Previous Bad Frame Indication (PrevBFI). STATE 0 is the initial state where BFI=0 and PrevBFI=0 or 1. Transitions to STATE 1, 2, 3, 4, and 5 occur when BFI=1. STATE 1 has PrevBFI=0, while STATE 2, 3, 4, and 5 have PrevBFI=1. STATE 5 has BFI=0 or 1. Transitions from STATE 1, 2, 3, 4, and 5 back to STATE 0 occur when BFI=0. STATE 6 is reached from STATE 5 when BFI=1 and PrevBFI=0 or 1. STATE 6 has a self-loop for BFI=1. A legend indicates that a black arrow represents a 'Bad frame (BFI=1)' and a grey arrow represents a 'Good frame (BFI=0)'. + +Figure 1: State machine for controlling the bad frame substitution + +#### **BFI = 0, PrevBFI = 0, State = 0** + +No error is detected in the received or in the previous received speech frame. The received speech parameters are used normally in the speech synthesis. The current frame of speech parameters is saved. + +#### **BFI = 0, PrevBFI = 1, State = 0 or 5** + +No error is detected in the received speech frame but the previous received speech frame was bad. The LTP-gain and fixed codebook gain are limited below the values used for the last received good subframe: + +$$g^p = \begin{cases} g^p, & g^p \leq g^p(-1) \\ g^p(-1), & g^p > g^p(-1) \end{cases} \quad (1)$$ + +where $g^p$ = current decoded LTP-gain, $g^p(-1)$ = LTP-gain used for the last good subframe (BFI = 0), and + +$$g^c = \begin{cases} g^c, & g^c \leq g^c(-1) \\ g^c(-1), & g^c > g^c(-1) \end{cases} \quad (2)$$ + +where $g^c$ = current decoded fixed codebook-gain and $g^c(-1)$ = fixed codebook gain used for the last good subframe (BFI = 0). + +The rest of the received speech parameters are used normally in the speech synthesis. The current frame of speech parameters is saved. + +**BFI = 1, PrevBFI = 0 or 1, State = 1...6** + +An error is detected in the received speech frame and the substitution and muting procedure is started. The LTP-gain and fixed codebook gain are replaced by attenuated values from the previous subframes: + +$$g^p = \begin{cases} P(state) g^p(-1), & g^p(-1) \leq median5(g^p(-1), \dots, g^p(-5)) \\ P(state) median5(g^p(-1), \dots, g^p(-5)), & g^p(-1) > median5(g^p(-1), \dots, g^p(-5)) \end{cases} \quad (3)$$ + +where $g^p$ = current decoded LTP-gain, $g^p(-1), \dots, g^p(-n)$ = LTP-gains used for the last n subframes, $median5()$ = 5-point median operation, $P(state)$ = attenuation factor ( $P(1) = 0.98, P(2) = 0.98, P(3) = 0.8, P(4) = 0.3, P(5) = 0.2, P(6) = 0.2$ ), $state$ = state number, and + +$$g^c = \begin{cases} C(state) g^c(-1), & g^c(-1) \leq median5(g^c(-1), \dots, g^c(-5)) \\ C(state) median5(g^c(-1), \dots, g^c(-5)), & g^c(-1) > median5(g^c(-1), \dots, g^c(-5)) \end{cases} \quad (4)$$ + +where $g^c$ = current decoded fixed codebook gain, $g^c(-1), \dots, g^c(-n)$ = fixed codebook gains used for the last n subframes, $median5()$ = 5-point median operation, $C(state)$ = attenuation factor ( $C(1) = 0.98, C(2) = 0.98, C(3) = 0.98, C(4) = 0.98, C(5) = 0.98, C(6) = 0.7$ ), and $state$ = state number. + +The higher the state value is, the more the gains are attenuated. Also the memory of the predictive fixed codebook gain is updated by using the average value of the past four values in the memory: + +$$ener(0) = \frac{1}{4} \sum_{i=1}^4 ener(-i) \quad (5)$$ + +The past LSFs are used by shifting their values towards their mean: + +$$lsf\_q1(i) = lsf\_q2(i) = \alpha past\_lsf\_q(i) + (1 - \alpha)mean\_lsf(i), \quad i = 0..9 \quad (6)$$ + +where $\alpha = 0.95$ , $lsf\_q1$ and $lsf\_q2$ are two sets of LSF-vectors for current frame, $past\_lsf\_q$ is $lsf\_q2$ from the previous frame, and $mean\_lsf$ is the average LSF-vector. + +The LTP-lag values are replaced by the past value from the 4th subframe of the previous frame. + +The received fixed codebook excitation pulses from the erroneous frame are always used as such. + +### 6.2 Example solution for substitution and muting of lost SID frames + +The first lost SID frame is replaced by the last valid SID frame. + +For subsequent lost SID frames, the last valid SID frame is repeated, but the fixed codebook gain is decreased with a constant value of -3 dB in each frame down to the minimum value of 0. This value is maintained if additional lost SID frames occur. + +## Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|-----------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments | +| SMG#22 | | | | 4.0.1 | ETSI Publication | +| SMG#20 | | | | 5.1.2 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | | | | | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46062/raw.md b/marked/Rel-18/46_series/46062/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..25c7b463cea29a41fd6eeff992f2f0a793d117f6 --- /dev/null +++ b/marked/Rel-18/46_series/46062/raw.md @@ -0,0 +1,562 @@ + + +# 3GPP TS 46.062 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 General..... | 7 | +| 5 Functions on the transmit (TX) side ..... | 7 | +| 5.1 Background acoustic noise evaluation ..... | 8 | +| 5.2 Modification of the speech encoding algorithm during SID frame generation..... | 11 | +| 5.3 SID-frame encoding ..... | 11 | +| 6 Functions on the receive (RX) side..... | 12 | +| 6.1 Averaging and decoding of the LP and fixed codebook gain parameters..... | 12 | +| 6.2 Comfort noise generation and updating ..... | 14 | +| 7 Computational details ..... | 15 | +| Annex A (informative): Change history..... | 16 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in Mobile Stations (MSs) and Base Station Systems (BSSs) during Discontinuous Transmission (DTX) on Enhanced Full Rate speech traffic channels within the digital cellular telecommunications system. + +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 gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in Mobile Stations (MSs) and Base Station Systems (BSSs) during Discontinuous Transmission (DTX) on Enhanced Full Rate speech traffic channels. + +The requirements described in the present document are mandatory for implementation in all GSM MSs capable of supporting the Enhanced Full Rate speech traffic channel. + +The receiver requirements are mandatory for implementation in all GSM BSSs capable of supporting the Enhanced Full Rate speech traffic channel, the transmitter requirements only for those where downlink DTX will be used. + +In case of discrepancy between the requirements described in the present document and the fixed point computational description of these requirements contained in GSM 06.53 [2], the description in GSM 06.53 [2] will prevail. + +# 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec". +- [3] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding". +- [4] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frame for Enhanced Full Rate (EFR) speech traffic channels". +- [5] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**frame:** time interval of 20 ms corresponding to the time segmentation of the Enhanced Full Rate speech transcoder, also used as a short term traffic frame. + +**SID frame:** frame characterized by the SID (Silence Descriptor) codeword. It conveys information on the acoustic background noise. + +**SID codeword:** fixed bit pattern for labelling a traffic frame as a SID frame. + +**SID field:** bit positions of the SID codeword within a SID frame. + +**speech frame:** traffic frame that cannot be classified as a SID frame. + +**VAD flag:** Voice Activity Detection flag. + +**SP flag:** SPEech flag. + +Other definitions of terms used in the present document can be found in GSM 06.60 [3] and GSM 06.81 [5]. The overall operation of DTX is described in GSM 06.81 [5]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply. Boldface symbols are used for vector variables. + +$\mathbf{f}^T = [f_1 \ f_2 \ \dots \ f_{10}]$ Unquantized LSF vector + +$\hat{\mathbf{f}}^T = [\hat{f}_1 \ \hat{f}_2 \ \dots \ \hat{f}_{10}]$ Quantized LSF vector + +$\mathbf{f}^{(m)}$ $m$ th unquantized LSF vector of the frame + +$\hat{\mathbf{f}}^{(m)}$ $m$ th quantized LSF vector of the frame + +$\hat{\mathbf{f}}^{ref}$ Reference LSF parameter vector + +$\mathbf{f}^{mean}$ Averaged LSF parameter vector + +$g_c$ Unquantized fixed codebook gain + +$\hat{g}_c$ Quantized fixed codebook gain + +$\hat{g}_c^{ref}$ Reference fixed codebook gain + +$g_c^{mean}$ Averaged fixed codebook gain + +$e_{LP}$ Linear prediction residual signal + +$\mathbf{e}$ Computed LSF parameter prediction residual + +$\hat{\mathbf{e}}$ Quantized LSF parameter prediction residual + +$\gamma$ Computed fixed codebook gain correction factor + +$\hat{\gamma}$ Quantized fixed codebook gain correction factor + +$$\sum_{n=a}^b x(n) = x(a) + x(a+1) + \dots + x(b-1) + x(b)$$ + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|----------------------------| +| BSS | Base Station Subsystem | +| DTX | Discontinuous Transmission | +| LP | Linear Prediction | +| LSF | Line Spectral Frequency | + +| | | +|-----|-------------------------| +| LSP | Line Spectral Pair | +| MS | Mobile Station | +| RX | Receive | +| SID | Silence Descriptor | +| TX | Transmit | +| VAD | Voice Activity Detector | + +For abbreviations not given in this clause, see GSM 01.04 [1]. + +# 4 General + +A basic problem when using DTX is that the background acoustic noise, which is transmitted together with the speech, would disappear when the radio transmission is cut, resulting in discontinuities of the background noise. Since the DTX switching can take place rapidly, it has been found that this effect can be very annoying for the listener - especially in a car environment with high background noise levels. In bad cases, the speech may be hardly intelligible. + +The present document specifies the way to overcome this problem by generating on the receive (RX) side synthetic noise similar to the transmit (TX) side background noise. The comfort noise parameters are estimated on the TX side and transmitted to the RX side before the radio transmission is switched off and at a regular low rate afterwards. This allows the comfort noise to adapt to the changes of the noise on the TX side. + +# 5 Functions on the transmit (TX) side + +The comfort noise evaluation algorithm uses the following parameters of the GSM Enhanced Full Rate speech encoder, defined in GSM 06.60 [3]: + +- the unquantized and quantized Linear Prediction (LP) parameters, using the Line Spectral Pair (LSP) representation, where the unquantized Line Spectral Frequency (LSF) vector is given by $\mathbf{f}^T = [f_1 \ f_2 \ \dots \ f_{10}]$ , the quantized LSF vector is given by $\hat{\mathbf{f}}^T = [\hat{f}_1 \ \hat{f}_2 \ \dots \ \hat{f}_{10}]$ , and the two sets of unquantized and quantized LSF vectors (one for each half of a frame) are given by $\mathbf{f}^{(1)}$ , $\mathbf{f}^{(2)}$ , $\hat{\mathbf{f}}^{(1)}$ and $\hat{\mathbf{f}}^{(2)}$ , respectively; +- the quantized fixed-codebook gain $\hat{g}_c$ . + +The algorithm also computes the following parameters to assist in comfort noise generation: + +- the reference LSF parameter vector $\hat{\mathbf{f}}^{ref}$ (average of the quantized LSF parameters of the hangover period); +- the averaged LSF parameter vector $\mathbf{f}^{mean}$ (average of the LSF parameters of the eight most recent frames); +- the reference fixed codebook gain $\hat{g}_c^{ref}$ (average of the quantized fixed codebook gain values of the hangover period); +- the averaged fixed codebook gain $g_c^{mean}$ (average of the fixed codebook gain values of the eight most recent frames); +- the unquantized fixed codebook gain $g_c$ . + +These parameters give information on the level ( $g_c$ , $\hat{g}_c$ , $\hat{g}_c^{ref}$ , $g_c^{mean}$ ) and the spectrum ( $\mathbf{f}^{(1)}$ , $\mathbf{f}^{(2)}$ , $\hat{\mathbf{f}}^{(1)}$ , $\hat{\mathbf{f}}^{(2)}$ , $\hat{\mathbf{f}}^{ref}$ , $\mathbf{f}^{mean}$ ) of the background noise. + +Two of the evaluated comfort noise parameters ( $\mathbf{f}^{mean}$ and $g_c^{mean}$ ) are encoded into a special frame, called a Silence Descriptor (SID) frame, for transmission to the RX side. Since the reference LSF parameter vector $\hat{\mathbf{f}}^{ref}$ and the + +reference fixed codebook gain $\hat{g}_c^{ref}$ can be evaluated in the same way in the encoder and decoder, as given in clause 5.1, no transmission of these parameters is necessary. + +The averaged LSF parameter and fixed codebook gain values, $\mathbf{f}^{mean}$ and $g_c^{mean}$ , are computed in the encoder using both quantized and unquantized parameter values if the period of the eight most recent frames (the SID averaging period) is overlapping with the hangover period (the parameters from the frames overlapping with the hangover period have quantized values, while the parameters of the more recent frames of the SID averaging period have unquantized values). If the period of the eight most recent frames is non-overlapping with the hangover period, the averaged LSF parameter and fixed codebook gain values are computed using only unquantized parameter values. + +The SID frame also serves to initiate the comfort noise generation on the receive side, as a SID frame is always sent at the end of a speech burst, i.e., before the radio transmission is terminated. + +The scheduling of SID or speech frames on the radio path is described in GSM 06.81 [5]. + +## 5.1 Background acoustic noise evaluation + +The comfort noise parameters to be encoded into a SID frame are calculated over $N = 8$ consecutive frames marked with VAD = 0, as follows: + +The averaged LSF parameter vector $\mathbf{f}^{mean}(i)$ of the frame $i$ shall be computed according to the equation: + +$$\mathbf{f}^{mean}(i) = \frac{1}{8} \sum_{n=0}^7 \left( \frac{1}{2} \sum_{m=1}^2 \mathbf{f}^{(m)}(i-n) \right) \quad (1)$$ + +where: + +$\mathbf{f}^{(m)}(i)$ is the $m$ th (unquantized) LSF parameter vector of the current frame $i$ ( $n = 0$ ); + +$\mathbf{f}^{(m)}(i-n)$ is the $m$ th (quantized or unquantized) LSF parameter vector of one of the last frames ( $n = 1, \dots, 7$ ); + +$n$ is the averaging period index ( $n = 0, 1, \dots, 7$ ); + +$m$ is the LSF parameter vector index within a frame (1 or 2); + +$i$ is the frame index. + +NOTE: When the averaging is performed at the end of the hangover period (first SID update), all of the LSF parameter vectors $\mathbf{f}^{(m)}(i-n)$ of the 7 previous frames (the hangover period) have quantized values, while the LSF parameter vectors $\mathbf{f}^{(m)}(i)$ of the current frame $i$ have unquantized values. In the subsequent SID updates, the LSF parameter vectors of the SID averaging period in the frames overlapping with the hangover period have quantized values, while the parameter vectors of the more recent frames of the SID averaging period have unquantized values. + +The averaged LSF parameter vector $\mathbf{f}^{mean}(i)$ of the frame $i$ is encoded using the same encoding tables that are also used by the GSM Enhanced Full Rate speech codec for the encoding of the non-averaged LSF parameter vectors in ordinary speech encoding mode, but the quantization algorithm is modified in order to support the quantization of comfort noise. The LSF parameter prediction residual to be quantized is obtained according to the following equation: + +$$\mathbf{e}(i) = \mathbf{f}^{mean}(i) - \hat{\mathbf{f}}^{ref} \quad (2)$$ + +where: + +$\mathbf{f}^{mean}(i)$ is the averaged LSF parameter vector at the current frame $i$ + +$\hat{\mathbf{f}}^{ref}$ is the reference LSF parameter vector + +$e(i)$ is the computed LSF parameter prediction residual at the current frame $i$ + +$i$ is the frame index; + +NOTE: This prediction residual is used for both halves of the frame in the quantization algorithm. The computation of the reference LSF parameter vector $\hat{\mathbf{f}}^{ref}$ is made on the basis of the quantized LSF parameters, $\hat{\mathbf{f}}^{(1)}$ and $\hat{\mathbf{f}}^{(2)}$ , by averaging the parameters over the hangover period of 7 frames, according to the following equation: + +$$\hat{\mathbf{f}}^{ref} = \frac{1}{7} \sum_{n=1}^7 \left( \frac{1}{2} \sum_{m=1}^2 \hat{\mathbf{f}}^{(m)}(k-n) \right) \quad (3)$$ + +where: + +$\hat{\mathbf{f}}^{(m)}(k-n)$ is the $m$ th quantized LSF parameter vector of one of the frames of the hangover period ( $n = 1, \dots, 7$ ); + +$n$ is the hangover period frame index ( $n = 1, \dots, 7$ ); + +$m$ is the LSF parameter index within a frame (1 or 2); + +$k$ is the frame index. + +For each comfort noise insertion period, the computation of the reference LSF parameter vector $\hat{\mathbf{f}}^{ref}$ is done only once at the end of the hangover period and for the rest of the comfort noise insertion period $\hat{\mathbf{f}}^{ref}$ will be frozen. The reference LSF parameter vector $\hat{\mathbf{f}}^{ref}$ is evaluated in the decoder in the same way as in the encoder, because during the hangover period the same LSF parameter vectors $\hat{\mathbf{f}}^{(m)}$ are available at the encoder and decoder. An exception to this are the cases when transmission errors are severe enough to cause the parameters to become unusable, and the frame substitution procedure is activated (see GSM 06.61 [4]). In these cases, the modified parameters obtained from the frame substitution procedure are used instead of the received parameters. + +The fixed codebook gain values shall be averaged and updated in every subframe according to the equation: + +$$g_c^{mean} = \frac{1}{29} \sum_{n=0}^{28} g_c(-n) \quad (4)$$ + +where: + +$g_c(0)$ is the (unquantized) fixed codebook gain in the current subframe ( $n=0$ ); + +$g_c(-n)$ is the (quantized or unquantized) fixed codebook gain in one of the past subframes ( $n = 1, \dots, 28$ ); + +$n$ is the averaging period index ( $n = 0, 1, \dots, 28$ ); + +NOTE: When the averaging is started at the end of the hangover period (first SID update), all of the fixed codebook gains $g_c(-n)$ of the 28 ( $n=1, \dots, 28$ ) previous subframes (the hangover period) have quantized values, while the fixed codebook gains $g_c(0)$ of the current subframe has an unquantized value. In the subsequent SID updates, the fixed codebook gain values of the SID averaging period in the subframes overlapping with the hangover period have quantized values, while the parameter vectors of the more recent subframes of the SID averaging period have unquantized values. + +Since most parts of the subframe processing clause in the encoder are switched off when the SP flag = "0" (to minimize the average complexity of the speech encoder algorithm), the unquantized fixed codebook gain is not directly available for gain averaging. Due to this, the unquantized fixed codebook gain is separately computed, based on the energy of the LP residual signal in each subframe, according to the following equation: + +$$g_c(j) = \sqrt{\frac{\sum_{l=1}^{40} (e_{LP}(j)(l))^2}{10}} \quad (5)$$ + +where: + +$g_c(j)$ is the unquantized fixed codebook gain of the current subframe $j$ ; + +$e_{LP}(j)(l)$ is the $l$ th sample of the LP residual in the current subframe $j$ ; + +$j$ is the subframe index ( $j = 1, \dots, 4$ ); + +$l$ is the sample index ( $l = 1, \dots, 40$ ). + +NOTE: The computed energy of the LP residual signal is divided by the value of 10 to yield the energy for one excitation pulse, since during comfort noise generation, the subframe excitation signal (pseudo noise) has 10 non-zero samples, whose amplitudes can take values of +1 or -1. + +The averaged fixed codebook gain value $g_c^{mean}$ of the current subframe is encoded using the non-averaged fixed codebook gain values in ordinary speech encoding mode, but the quantization algorithm is modified in order to support comfort noise quantization. The fixed codebook gain correction factor $\gamma$ to be quantized is obtained according to the following equation: + +$$\gamma = g_c^{mean} / \hat{g}_c^{ref} \quad (6)$$ + +where: + +$g_c^{mean}$ is the averaged fixed codebook gain value in the current subframe; + +$\hat{g}_c^{ref}$ is the reference fixed codebook gain; + +The computation of the reference fixed codebook gain $\hat{g}_c^{ref}$ is made on the basis of the quantized fixed codebook gain parameters $\hat{g}_c$ , by averaging the parameter values over the hangover period of 7 frames according to the following equation: + +$$\hat{g}_c^{ref} = \frac{1}{7} \sum_{n=1}^7 \left( \frac{1}{4} \sum_{j=1}^4 \hat{g}_c(k-n)(j) \right) \quad (7)$$ + +where: + +$\hat{g}_c(k-n)(j)$ is the quantized fixed codebook gain parameter value in subframe $j$ of one of the frames of the hangover period ( $n = 1, \dots, 7$ ); + +$n$ is the hangover period frame index ( $n = 1, 2, \dots, 7$ ); + +$k$ is the frame index; + +$j$ is the subframe index ( $j = 1, \dots, 4$ ); + +For each comfort noise insertion period, the computation of the reference fixed codebook gain $\hat{g}_c^{ref}$ is done only once at the end of the hangover period and for the rest of the comfort noise insertion period $\hat{g}_c^{ref}$ will be frozen. The reference fixed codebook gain $\hat{g}_c^{ref}$ can be evaluated in the decoder in the same way as in the encoder, because during the hangover period the same quantized fixed codebook gain values $\hat{g}_c$ are available at the encoder and decoder. An exception to this are the cases when transmission errors are severe enough to cause the parameters to become unusable, + +and the frame substitution procedure is activated (see GSM 06.61 [4]). In these cases, the modified parameters obtained from the frame substitution procedure are used instead of the received parameters. + +The hangover period is defined in GSM 06.81 [5]. It is a period added at the end of a speech burst in which no voice activity is detected (VAD flag = "0"), but the speech encoder stays for the processing of 7 speech frames in speech encoding mode (SP flag = "1"). This hangover period and the first SID frame are used for averaging the comfort noise parameters contained in the first SID frame. + +## 5.2 Modification of the speech encoding algorithm during SID frame generation + +When the SP flag is equal to "0" the speech encoding algorithm is modified in the following way: + +- The non-averaged LP parameters which are used to derive the filter coefficients of the filters $H(z)$ and $W(z)$ of the speech encoder are not quantized. +- The open loop pitch lag search is performed, but the closed loop pitch lag search is inactivated. The adaptive codebook gain is set to zero. +- No fixed codebook search is made. In each subframe the pulse positions and signs of the fixed codebook excitation are locally generated using uniformly distributed pseudo random numbers. The excitation pulses take values of +1 and -1 when comfort noise is generated. The fixed codebook comfort noise excitation generation algorithm is defined in clause 6.2. +- The memory of weighting filter $W(z)$ is set to zero, i.e., the memory of $W(z)$ is not updated. +- The ordinary LP parameter quantization algorithm is inactive. At the end of the hangover period the reference LSF parameter vector $\hat{\mathbf{f}}^{ref}$ is calculated as defined in clause 5.1. For the rest of the comfort noise insertion period $\hat{\mathbf{f}}^{ref}$ is frozen. The averaged LSF parameter vector $\mathbf{f}^{mean}$ is calculated each time a new SID frame is to be sent to the Radio Subsystem. This parameter vector is encoded into the SID frame as defined in clause 5.1. +- The ordinary fixed codebook gain quantization algorithm is inactive. At the end of the hangover period the reference fixed codebook gain $\hat{g}_c^{ref}$ is calculated as defined in clause 5.1. For the rest of the comfort noise insertion period $\hat{g}_c^{ref}$ is frozen. The averaged fixed codebook gain value $g_c^{mean}$ is calculated each time a new SID frame is to be sent to the Radio Subsystem. This gain value is encoded into the SID frame as defined in clause 5.1. +- The predictor memories of the ordinary LP parameter quantization and fixed codebook gain quantization algorithms are reset when SP flag = "0", so that the quantizers start from their initial states when the speech activity begins again. +- The computation of the unquantized fixed codebook gain is performed based on the energy of the LP residual signal. + +## 5.3 SID-frame encoding + +The SID-frame encoding algorithm exploits the fact that only some of the 244 bits in a frame are needed to code the comfort noise parameters. The other bits can then be used to mark the SID-frame by means of a fixed bit pattern, called the SID code word. + +The quantization indices of the LP parameters are replaced by the quantization indices derived from the averaged LSF parameter vector $\mathbf{f}^{mean}$ . The encoding of the quantization indices is defined in clause 5.1. + +The fixed codebook gain quantization indices are replaced by the quantization index derived from the averaged fixed codebook gain value $g_c^{mean}$ , encoded as defined in clause 5.1, repeated four times inside the frame. + +The SID code word consists of 95 bits which are all set to one. The bits of the SID code word are inserted in the SID field as defined in table 1. All of the bits in the SID field are in the error protection Class I. + +The remaining bits in the SID frame are set to zero. The use of these bits is for further study. + +**Table 1: SID codeword** + +| Parameter | Number of bits | Bit positions
(b0 = LSB) | +|-----------------------|----------------|-----------------------------| +| LTP LAG 1 | 2 | b0, b1 | +| LTP LAG 2 | 3 | b0, b1, b2 | +| LTP LAG 3 | 2 | b0, b1 | +| LTP LAG 4 | 4 | b0, b1, b2, b3 | +| LTP GAIN 1 | 3 | b0, b1, b2 | +| LTP GAIN 2 | 3 | b0, b1, b2 | +| LTP GAIN 3 | 4 | b0, b1, b2, b3 | +| LTP GAIN 4 | 4 | b0, b1, b2, b3 | +| PULSE 1 of 1st subfr. | 4 | b0, b1, b2, b3 | +| PULSE 2 of 1st subfr. | 4 | b0, b1, b2, b3 | +| PULSE 3 of 1st subfr. | 4 | b0, b1, b2, b3 | +| PULSE 4 of 1st subfr. | 4 | b0, b1, b2, b3 | +| PULSE 5 of 1st subfr. | 2 | b2,b3 | +| PULSE 1 of 2nd subfr. | 4 | b0, b1, b2, b3 | +| PULSE 2 of 2nd subfr. | 4 | b0, b1, b2, b3 | +| PULSE 3 of 2nd subfr. | 4 | b0, b1, b2, b3 | +| PULSE 4 of 2nd subfr. | 4 | b0, b1, b2, b3 | +| PULSE 5 of 2nd subfr. | 2 | b2,b3 | +| PULSE 1 of 3rd subfr. | 4 | b0, b1, b2, b3 | +| PULSE 2 of 3rd subfr. | 4 | b0, b1, b2, b3 | +| PULSE 3 of 3rd subfr. | 4 | b0, b1, b2, b3 | +| PULSE 4 of 3rd subfr. | 4 | b0, b1, b2, b3 | +| PULSE 5 of 3rd subfr. | 2 | b2,b3 | +| PULSE 1 of 4th subfr. | 4 | b0, b1, b2, b3 | +| PULSE 2 of 4th subfr. | 2 | b2, b3 | +| PULSE 3 of 4th subfr. | 4 | b0, b1, b2, b3 | +| PULSE 4 of 4th subfr. | 4 | b0, b1, b2, b3 | +| PULSE 5 of 4th subfr. | 2 | b2,b3 | + +The parameters in table 1 are defined in GSM 06.60 [3]. + +# 6 Functions on the receive (RX) side + +The situations in which comfort noise shall be generated on the receive side are defined in GSM 06.81 [5]. Generally speaking, the comfort noise generation is started or updated whenever a valid SID frame is received. + +## 6.1 Averaging and decoding of the LP and fixed codebook gain parameters + +When speech frames are received by the decoder the LP and the fixed codebook gain parameters of the last seven speech frames shall be kept in memory. The decoder counts the number of frames elapsed since the last SID frame was updated and passed to the RSS by the encoder. Based on this count, the decoder determines whether or not there is a hangover period at the end of the speech burst (if at least 31 frames have elapsed since the last SID update when the first SID frame after a speech burst arrives, the hangover period has existed at the end of the speech burst). + +As soon as a SID frame is received, and the hangover period is detected at the end of the speech burst, the stored LP and fixed codebook gain parameters shall be averaged to obtain the reference LSF parameter vector $\hat{\mathbf{f}}^{ref}$ and the reference fixed gain codebook value $g_c^{ref}$ . The reference LSF parameter vector and the reference fixed codebook gain value shall be frozen and used for the actual comfort noise insertion period. + +The averaging procedure for obtaining the reference parameters is as follows: + +- when a speech frame is received, the LSF and fixed codebook gain parameters are decoded and stored in memory; +- when the first SID frame is received, and the hangover period is detected at the end of the speech burst, the stored LSF and fixed codebook gain parameters are averaged in the same way as in the speech encoder as follows (see also clause 5.1): + +$$\hat{\mathbf{f}}^{ref} = \frac{1}{7} \sum_{n=1}^7 \left( \frac{1}{2} \sum_{m=1}^2 \hat{\mathbf{f}}^{(m)}(k-n) \right) \quad (8)$$ + +where: + +$\hat{\mathbf{f}}^{(m)}(k-n)$ is the $m$ th quantized LSF parameter vector of one of the frames of the hangover period ( $n = 1, \dots, 7$ ); + +$n$ is the hangover period frame index ( $n = 1, 2, \dots, 7$ ); + +$m$ is the LSF parameter index within a frame (1 or 2); + +$k$ is the frame index. + +and + +$$\hat{\mathbf{g}}_c^{ref} = \frac{1}{7} \sum_{n=1}^7 \left( \frac{1}{4} \sum_{j=1}^4 \hat{\mathbf{g}}_c(k-n)(j) \right) \quad (9)$$ + +where: + +$\hat{\mathbf{g}}_c(k-n)(j)$ is the quantized fixed codebook gain parameter value in subframe $j$ of one of the frames of the hangover period ( $n = 1, \dots, 7$ ); + +$n$ is the hangover period frame index ( $n = 1, \dots, 7$ ); + +$k$ is the frame index; + +$j$ is the subframe index ( $j = 1, \dots, 4$ ). + +Once the reference LSF parameter vector has been computed, the averaged LSF parameter vector $\hat{\mathbf{f}}^{mean}(i)$ of the frame $i$ (encoded into the SID frame) can be reproduced at the decoder each time a SID update frame is received, according to the equation: + +$$\hat{\mathbf{f}}^{mean}(i) = \hat{\mathbf{e}}(i) + \hat{\mathbf{f}}^{ref} \quad (10)$$ + +where: + +$\hat{\mathbf{f}}^{mean}(i)$ is the quantized, averaged LSF parameter vector at the current frame $i$ to be used for comfort noise generation; + +$\hat{\mathbf{f}}^{ref}$ is the reference LSF parameter vector; + +$\hat{\mathbf{e}}(i)$ is the received quantized LSF parameter prediction residual at the current frame $i$ ; + +$i$ is the frame index. + +The averaged fixed codebook gain $\hat{\mathbf{g}}_c^{mean}(i)$ of the frame $i$ (encoded into the SID frame) can be similarly reproduced at the decoder each time a SID update frame is received, according to the following equation: + +$$\hat{g}_c^{mean}(i) = \hat{g}_c^{ref} \cdot \hat{\gamma}(i) \quad (11)$$ + +where: + +$\hat{g}_c^{mean}(i)$ is the averaged fixed codebook gain value in the current frame $i$ to be used for comfort noise generation; + +$\hat{g}_c^{ref}$ is the reference fixed codebook gain; + +$\hat{\gamma}(i)$ is the received quantized fixed codebook gain correction factor in the current frame $i$ ; + +$i$ is the frame index. + +## 6.2 Comfort noise generation and updating + +The comfort noise generation procedure uses the GSM Enhanced Full Rate speech decoder algorithm defined in GSM 06.60 [3]. + +When comfort noise is to be generated, the various encoded parameters are set as follows: + +In each subframe, the pulse positions and signs of the fixed codebook excitation are locally generated using uniformly distributed pseudo random numbers. The excitation pulses take values of +1 and -1 when comfort noise is generated. The fixed codebook comfort noise excitation generation algorithm works as follows: + +``` +for (i = 0; i < 40; i++) code[i] = 0; +for (i = 0; i < 10; i++) { + j = random(4); + idx = j * 10 + i; + if (random(2) == 1) code[idx] = 1; + else code[idx] = -1; +} +``` + +where: + +**code[0..39]** fixed codebook excitation buffer; + +**random(4)** generates a random integer value, uniformly distributed between 0 and 3; + +**random(2)** generates a random integer value, uniformly distributed between 0 and 1. + +The fixed codebook gain values are those received in the SID frame. + +The adaptive codebook gain values in each subframe are set to 0. + +The pitch delay values in each subframe are set to 40. + +The LP filter parameters used are those received in the SID frame. + +The predictor memories of the ordinary LP parameter and fixed codebook gain quantization algorithms are reset when SP flag = "0", so that the quantizers start from their initial states when the speech activity begins again. + +With these parameters, the speech decoder now performs the standard operations described in GSM 06.60 [3] and synthesizes comfort noise. + +Updating of the comfort noise parameters (fixed codebook gain and LP filter parameters) occurs each time a valid SID frame is received, as described in GSM 06.81 [5]. + +When updating the comfort noise, the parameters above should preferably be interpolated over the SID update period to obtain smooth transitions. + +# --- 7 Computational details + +A low level description has been prepared in form of an ANSI C source code which is part of GSM 06.53 [2]. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|-----------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments | +| SMG#22 | | | | 4.0.1 | ETSI Publication | +| SMG#20 | | | | 5.1.2 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | | +| 06-2018 | SA#80 | | | | | Version for Release 15 | 15.0.0 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46081/raw.md b/marked/Rel-18/46_series/46081/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1db4e02206ee6302c6ced46e94fb9ab6213e08dd --- /dev/null +++ b/marked/Rel-18/46_series/46081/raw.md @@ -0,0 +1,425 @@ + + +# 3GPP TS 46.081 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Discontinuous Transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, speech, codec + +### **3GPP** + +## --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|----------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 General organization ..... | 7 | +| 5 Transmit (TX) side..... | 8 | +| 5.1 General operation ..... | 8 | +| 5.1.1 Functions of the TX DTX handler..... | 8 | +| 5.1.2 Functions of the TX Radio Subsystem..... | 10 | +| 6 Receive (RX) side ..... | 11 | +| 6.1 General operation ..... | 11 | +| 6.1.1 Functions of the RX radio subsystem..... | 11 | +| 6.1.2 Functions of the RX DTX handler ..... | 12 | +| Annex A (informative): Change history ..... | 13 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document describes the general baseband operation of Enhanced Full Rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations and Base Station Systems during Discontinuous Transmission (DTX) within the digital cellular telecommunications system. + +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 gives a description of the general baseband operation of Enhanced Full Rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX). + +For clarity, the description is structured according to the block diagrams in figures 1 and 4. Except in the case described next, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same. + +In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX handlers and the Radio Sub System (RSS) as described in the present document together with all their flags is mandatory, being part of the A-bis interface as described in GSM 08.60 [13]. + +The DTX functions described in the present document are mandatory for implementation in the GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used. + +# 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". +- [3] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding". +- [4] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". +- [5] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". +- [6] GSM 06.51: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech processing functions; General description". +- [7] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec". +- [8] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test vectors for the GSM Enhanced Full Rate (EFR) speech codec". +- [9] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding". +- [10] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frame for Enhanced Full Rate (EFR) speech traffic channels". + +- [11] GSM 06.62: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels". +- [12] GSM 06.82: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD) for Enhanced Full Rate (EFR) speech traffic channels". +- [13] GSM 08.60: "Digital cellular telecommunications system (Phase 2+); Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**accepted SID frame:** traffic frame which is flagged with SID="1" or SID="2" by the Radio Subsystem. + +**bad traffic frame:** traffic frame flagged BFI flag ="1" (Bad Frame Indication) by the Radio Subsystem. + +**frame:** time interval of 20 msec. corresponding to the time segmentation of the Enhanced Full Rate speech transcoder (GSM 06.60 [9]), also used as a short term for a traffic frame. + +**good speech frame:** good traffic frame which is not an accepted SID frame. + +**good traffic frame:** traffic frame flagged BFI flag ="0" by the Radio Subsystem. + +**hangover period:** period of 7 frames added at the end of a speech burst in which VAD flag ="0" and SP flag ="1". + +**invalid SID frame:** accepted SID frame which was not classified as valid SID frame. This frame is not valid for updating comfort noise parameters, but the frame conveys information that comfort noise generations should be started or continued. + +**lost SID frame:** unusable frame received when the RX DTX handler is generating comfort noise and a SID frame is expected (Time Alignment Flag, TAF="1"). + +**lost speech frame:** unusable frame received when the RX DTX handler is passing on traffic frames directly to the speech decoder. + +**SID code word:** fixed bit pattern defined in GSM 06.62 [11], for labelling a traffic frame as a SID frame. + +**SID field:** bit positions defined in GSM 06.62 [11], of the SID codeword within a SID frame. + +**SID frame:** frame characterized by the SID (Silence Descriptor) code word. It conveys information on the acoustic background noise. + +**SP flag:** boolean flag, generated by the TX DTX handler, indicating the presence of a speech frame ("1") or the presence of a SID frame ("0"). + +**speech frame:** traffic frame that cannot be classified as a SID frame. + +**TAF flag:** Time Alignment Flag. Boolean flag, marks with TAF=1 those traffic frames that are aligned with the SACCH multiframe structure (see GSM 05.08 [5]). The next SID frame is expected at the decoder when TAF=1. + +**traffic frame:** block of 244 information bits transmitted on the Enhanced Full Rate speech traffic channel. + +**unusable frame:** bad traffic frame that is not an accepted SID frame. + +**VAD flag:** boolean flag, generated by the VAD algorithm defined in GSM 06.82 [12] indicating the presence ("1") or the absence ("0") of a speech frame. + +**valid SID frame:** good traffic frame flagged with SID="2" by the Radio Subsystem. This frame is valid for updating of comfort noise parameters at any time. + +## 3.2 Symbols + +For the purposes of the present document, the following symbol applies: + +| | | +|----------------------|------------------------------------------------------------| +| $N_{\text{elapsed}}$ | Number of elapsed frames since the last updated SID frame. | +|----------------------|------------------------------------------------------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|---------------------------------------------| +| BFI | Bad Frame Indicator | +| BSC | Base Station Controller | +| BSS | Base Station System | +| DTX | Discontinuous Transmission | +| ETS | European Telecommunication Standard | +| FACCH | Fast Associated Control CHannel | +| GSM | Global System for Mobile Telecommunications | +| MS | Mobile Station | +| RSS | Radio Sub System | +| RX | Receive | +| SACCH | Slow Associated Control CHannel | +| SID | SIlence Descriptor | +| TX | Transmit | +| VAD | Voice Activity Detector | + +For abbreviations not given in this clause, see GSM 01.04 [1]. + +# --- 4 General + +Discontinuous Transmission (DTX) is a mechanism which allows the radio transmitter to be switched off most of the time during speech pauses for the following two purposes: + +- to save power in the Mobile Station (MS); +- to reduce the overall interference level over the air interface; + +DTX shall be in operation in GSM MS if commanded so by the network, see GSM 04.08 [2]. + +## 4.1 General organization + +The overall DTX mechanism described in the present document requires the following functions: + +- a Voice Activity Detector (VAD) on the transmit (TX) side; +- evaluation of the background acoustic noise on the transmit (TX) side, in order to transmit characteristic parameters to the receive (RX) side; +- generation on the receive (RX) side of a similar noise, called comfort noise, during periods where the radio transmission is switched off. + +The Voice Activity Detector (VAD) is defined in GSM 06.82 [12] and the comfort noise functions in GSM 06.62 [11]. Both are based partly on the speech transcoder and its internal variables, defined in GSM 06.60 [9]. + +In addition to these functions, if the parameters arriving at the RX side are detected to be seriously corrupted by errors, the speech or comfort noise must be generated from substituted data in order to avoid seriously annoying effects for the listener. This function is defined in GSM 06.61 [10]. + +An overall description of the speech processing parts can be found in GSM 06.51 [6]. + +# 5 Transmit (TX) side + +A block diagram of the transmit side DTX functions is shown in figure 1. + +![Block diagram of the transmit side DTX functions. The TX DTX handler contains Speech encoder, Voice Activity Detector, and Comfort Noise Computation. The TX radio subsystem contains Channel Encoding and SP flag monitoring. Arrows show Information bits (244) from Speech encoder to Channel Encoding, and SP flag (1) from Voice Activity Detector to SP flag monitoring.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +``` + +graph LR + subgraph TX_DTX_handler [TX DTX handler] + SE[Speech encoder] + VAD[Voice Activity Detector] + CNC[Comfort Noise Computation] + end + subgraph TX_radio_subsystem [TX radio subsystem] + CE[Channel Encoding] + SFM[SP flag monitoring] + end + SE -- "Information bits +244" --> CE + VAD -- "SP flag +1" --> SFM + +``` + +Block diagram of the transmit side DTX functions. The TX DTX handler contains Speech encoder, Voice Activity Detector, and Comfort Noise Computation. The TX radio subsystem contains Channel Encoding and SP flag monitoring. Arrows show Information bits (244) from Speech encoder to Channel Encoding, and SP flag (1) from Voice Activity Detector to SP flag monitoring. + +Figure 1: Block diagram of the transmit side DTX functions + +## 5.1 General operation + +The TX DTX handler continuously passes traffic frames, individually marked by a flag SP, to the Radio Subsystem (RSS). This binary flag is redundant to the SID code word labelling. SP flag = "1" indicates a speech frame, SP flag = "0" a SID frame. + +The scheduling of the frames for transmission on the air interface is controlled by the radio subsystem (RSS) alone, on the basis of the SP flag as described in clause 5.1.1. + +### 5.1.1 Functions of the TX DTX handler + +To allow an exact verification of the TX DTX handler functions, all frames before the reset of the system are treated as if there were speech frames of an infinitely long time. Therefore, the first 7 frames after the reset are always marked with SP flag = "1", even if VAD flag = "0" (hangover period, see figure 2). + +The Voice Activity Detector (VAD) shall operate all the time in order to assess whether the input signal contains speech or not. The output is a binary flag (VAD flag = "1" or VAD flag = "0", respectively) on a frame by frame basis (see GSM 06.82 [12]). + +The VAD flag controls indirectly, via the TX DTX handler operations described below, the overall DTX operation on the transmit side. + +Whenever VAD flag = "1", the speech encoder output frame shall be passed directly to the radio subsystem (RSS), marked with SP flag = "1". + +At the end of a speech burst (transition VAD flag = "1" to VAD flag = "0"), it takes 8 consecutive frames to make a new updated SID frame available (see GSM 06.62 [11]). Normally, the first 7 speech encoder output frames after the end of the speech burst shall therefore be passed directly to the radio subsystem, marked with SP flag = "1" ("hangover period"). The first new SID frame is then passed to the RSS as frame 8 after the end of the speech burst, marked with SP flag = "0" (see figure 2). + +![Figure 2: Normal hangover procedure (N_elapsed > 23). The diagram illustrates the timing and logic for SID frame updates during a speech burst. It shows three horizontal timelines: VAD flag, SP flag, and Frames to RSS. The VAD flag timeline shows a transition from 'speech' to 'pause' at the 'end of speech burst'. The SP flag timeline shows a 'hangover' period starting at the end of the speech burst. The Frames to RSS timeline shows a sequence of frames (35-42) with SID frames (k+1, k+2, k+3) being updated. Arrows indicate the averaging periods for calculating reference values f^ref and g_c^ref.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the normal hangover procedure for SID frame updates. It consists of three horizontal timelines: + +- VAD flag:** Shows a transition from a high state to a low state at the "end of speech burst". The "last 'speech' frame" is the last frame before the transition, and the "first 'pause' frame" is the first frame after the transition. A double-headed arrow indicates a "Frame (20 ms)" duration. +- SP flag:** Shows a "hangover" period starting at the end of the speech burst. A double-headed arrow indicates the "averaging period to calculate $\hat{f}^{ref}$ and $\hat{g}_c^{ref}$ ". +- Frames to RSS:** Shows a sequence of frames. The first row shows frame numbers: e.g. 35, 36, 37, 38, 39, 40, 41, 42, 0, 0, 0. The second row shows the content: Speech, ..., ..., ..., ..., ..., ..., ..., Speech, SID k+1, SID k+2, SID k+3. The third row shows "Frames to RSS" with three horizontal lines and arrows pointing to the SID frames k+1, k+2, and k+3. Below these lines, "SID averaging periods (averaging periods of $\hat{f}^{mean}$ and $\hat{g}_c^{mean}$ )" are indicated. + +Figure 2: Normal hangover procedure (N\_elapsed > 23). The diagram illustrates the timing and logic for SID frame updates during a speech burst. It shows three horizontal timelines: VAD flag, SP flag, and Frames to RSS. The VAD flag timeline shows a transition from 'speech' to 'pause' at the 'end of speech burst'. The SP flag timeline shows a 'hangover' period starting at the end of the speech burst. The Frames to RSS timeline shows a sequence of frames (35-42) with SID frames (k+1, k+2, k+3) being updated. Arrows indicate the averaging periods for calculating reference values f^ref and g\_c^ref. + +(Nelapsed: No. of elapsed frames since last update SID). + +**Figure 2: Normal hangover procedure (Nelapsed > 23)** + +If, however, at the end of the speech burst, less than 24 frames have elapsed since the last SID frame was computed and passed to the RSS, then this last SID frame shall repeatedly be passed to the RSS, until a new updated SID frame is available (8 consecutive frames marked with VAD flag = "0"). This reduces the activity on the air in cases where short background noise spikes are taken for speech, by avoiding the "hangover" waiting for the SID frame computation (see figure 3). + +NOTE: Figure 3 shows as example the longest possible speech burst without hangover. + +![Figure 3: Handling of short speech bursts (N_elapsed < 24) (Example). The diagram shows three horizontal timelines. The top timeline is the 'VAD flag', which is high during a speech burst and low otherwise. The second timeline is the 'SP flag', which follows the VAD flag with some hysteresis. The bottom timeline shows 'Frames to RSS' over time, indexed by 'N_elapsed' from 0 to 29. Frames 0-3 are marked with '?' and are part of an initial 'SID averaging period'. Frame 4 is 'SID k' with SP flag=0. Frames 5-8 are 'Speech' with SP flag=1. Frames 9-12 are 'SID k' with SP flag=0. Frames 13-16 are 'Speech' with SP flag=1. Frames 17-20 are 'SID k' with SP flag=0. Frames 21-24 are 'Speech' with SP flag=1. Frames 25-28 are 'SID k' with SP flag=0. Frame 29 is 'SID k+1' with SP flag=0. A bracket labeled 'repeat previous SID' spans frames 9-12 and 17-20. Another bracket labeled 'repeat previous SID' spans frames 25-28. A bracket labeled 'SID averaging period' spans frames 25-28. An arrow points to frame 29 with the label 'new (updated) SID'. A bracket labeled 'end of speech burst' points to the transition between frame 24 and 25. A bracket labeled 'Frame (20 ms)' spans one frame.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 3: Handling of short speech bursts (N\_elapsed < 24) (Example). The diagram shows three horizontal timelines. The top timeline is the 'VAD flag', which is high during a speech burst and low otherwise. The second timeline is the 'SP flag', which follows the VAD flag with some hysteresis. The bottom timeline shows 'Frames to RSS' over time, indexed by 'N\_elapsed' from 0 to 29. Frames 0-3 are marked with '?' and are part of an initial 'SID averaging period'. Frame 4 is 'SID k' with SP flag=0. Frames 5-8 are 'Speech' with SP flag=1. Frames 9-12 are 'SID k' with SP flag=0. Frames 13-16 are 'Speech' with SP flag=1. Frames 17-20 are 'SID k' with SP flag=0. Frames 21-24 are 'Speech' with SP flag=1. Frames 25-28 are 'SID k' with SP flag=0. Frame 29 is 'SID k+1' with SP flag=0. A bracket labeled 'repeat previous SID' spans frames 9-12 and 17-20. Another bracket labeled 'repeat previous SID' spans frames 25-28. A bracket labeled 'SID averaging period' spans frames 25-28. An arrow points to frame 29 with the label 'new (updated) SID'. A bracket labeled 'end of speech burst' points to the transition between frame 24 and 25. A bracket labeled 'Frame (20 ms)' spans one frame. + +**Figure 3: Handling of short speech bursts ( $N_{elapsed} < 24$ ) (Example)** + +Once the first SID frame after the end of a speech burst has been computed and passed to the Radio Subsystem, the TX DTX handler shall continuously compute and pass updated SID frames to the Radio Subsystem (RSS), marked with SP flag = "0" as long as VAD flag = "0". + +Following a handover, the DTX hangover period shall be initiated in the MS speech encoder to synchronize the encoder and decoder DTX states. This will allow a decoder which is reset at handover to synthesize comfort noise with the correct noise level using the first received SID frame following the handover. + +The speech encoder is operated in full speech modality if SP flag = "1" and in a simplified mode if SP flag = "0", because not all encoder functions are required for the evaluation of comfort noise parameters. + +### 5.1.2 Functions of the TX Radio Subsystem + +The following traffic frames shall be scheduled for transmission: + +- all frames marked with SP flag = "1"; +- the first one with SP flag = "0" after one or more frames with SP flag = "1"; +- those marked with SP=0 and aligned with the SACCH multiframe structure as described in GSM 05.08 [5]. + +This has the overall function, that the radio transmission is cut after the transmission of a SID frame when the speaker stops talking. During speech pauses the transmission is resumed at regular intervals for transmission of one SID frame, in order to update the generated comfort noise on the RX side (and to improve the measurement of the link quality by the RSS). + +If a SID frame (SP flag = "0"), scheduled for transmission is stolen for Fast Associated Control Channel (FACCH) signalling purposes, then the subsequent frame shall be scheduled for transmission instead. + +# 6 Receive (RX) side + +A block diagram of the receive side DTX functions is shown in figure 4. + +![Figure 4: Block diagram of the receive side DTX functions. The diagram shows two main blocks: 'RX DTX handler' on the left and 'RX radio subsystem' on the right. The RX DTX handler contains 'Speech decoder', 'Comfort Noise Generation', and 'Error Concealment'. The RX radio subsystem contains 'Error Correction & Detection' and 'SID frame detection'. Arrows flow from the radio subsystem to the handler: 'Information bits' (244) to Speech decoder; 'BFI' (1) and 'SID' (2) to Comfort Noise Generation; and 'TAF' (1) to Error Concealment. 'SID frame detection' also feeds into the SID signal path.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` + +graph LR + subgraph RX_DTX_handler [RX DTX handler] + SD[Speech decoder] + CNG[Comfort Noise Generation] + EC[Error Concealment] + end + subgraph RX_radio_subsystem [RX radio subsystem] + ECD[Error Correction & Detection] + SFD[SID frame detection] + end + ECD -- "Information bits (244)" --> SD + ECD -- "BFI (1)" --> CNG + ECD -- "SID (2)" --> CNG + ECD -- "TAF (1)" --> EC + SFD --> CNG + +``` + +Figure 4: Block diagram of the receive side DTX functions. The diagram shows two main blocks: 'RX DTX handler' on the left and 'RX radio subsystem' on the right. The RX DTX handler contains 'Speech decoder', 'Comfort Noise Generation', and 'Error Concealment'. The RX radio subsystem contains 'Error Correction & Detection' and 'SID frame detection'. Arrows flow from the radio subsystem to the handler: 'Information bits' (244) to Speech decoder; 'BFI' (1) and 'SID' (2) to Comfort Noise Generation; and 'TAF' (1) to Error Concealment. 'SID frame detection' also feeds into the SID signal path. + +Figure 4: Block diagram of the receive side DTX functions + +## 6.1 General operation + +Whatever their context (speech, SID, FACCH or none), the RSS continuously passes the received traffic frames to the RX DTX handler, individually marked by various pre-processing functions with 3 flags. These are the Bad Frame Indicator (BFI) flag, the Silence Descriptor (SID) flag and the Time Alignment Flag (TAF) described in clause 6.1.1 and table 1, which serve to classify the traffic frame according to the list of terms defined in clause 3.1. This classification, summarized in table 1, allows the RX DTX handler to determine in a simple way how the received frame is to be handled. + +Table 1: Classification of traffic frames + +| BFI | SID | | | +|-----|-------------------|---|-------------------| +| | 2 | 1 | 0 | +| 0 | Valid SID frame | | Good speech frame | +| 1 | Invalid SID frame | | Unusable frame | + +### 6.1.1 Functions of the RX radio subsystem + +The binary BFI flag (see GSM 05.05 [4]) indicates whether the traffic frame is considered to contain meaningful information bits (BFI flag = "0") or not (BFI flag = "1"). In the context of the present document, a FACCH frame is considered not to contain meaningful bits and shall be marked with BFI flag = "1". The BFI flag must fulfil the performance requirements of GSM 05.05 [4]. + +The SID frame detector compares bit by bit the relevant bits of the received traffic frame (the SID field) with the SID code word defined in GSM 06.62 [11] and gives back the ternary SID flag. The SID flag is coded as follows, where $n$ designates the number of bit deviations: + +SID = 2 when $n < 2$ + +SID = 1 when $2 \leq n < 16$ + +SID = 0 when $n \geq 16$ + +The binary TAF flag marks with TAF="1" those traffic frames that are aligned with the SACCH multiframe structure as described in GSM 05.08 [5]. + +### 6.1.2 Functions of the RX DTX handler + +The RX DTX handler is responsible for the overall DTX operation on the RX side. + +The DTX operation on the RX side shall be as follows: + +- whenever a good speech frame is detected, the DTX handler shall pass it directly on to the speech decoder; +- when lost speech or lost SID frames are detected, the substitution and muting procedure defined in GSM 06.61 [10] shall be applied; +- valid SID frames shall result in comfort noise generation, as defined in GSM 06.62 [11], until the next SID frame is expected (TAF ="1") or good speech frames are detected. During this period, the RX DTX handler shall ignore any unusable frames delivered by the RSS; +- an invalid SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied. + +## Annex A (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|-----------------|-------------|------------------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments | +| SMG#22 | | | | 4.0.1 | ETSI Publication | +| SMG#20 | | | | 5.1.2 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| SMG#30 | 631/99 | A004 | 5.1.1 | 7.1.0 | Fix of DTX Synchronization Problem at Handover | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | | | | | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/46_series/46082/raw.md b/marked/Rel-18/46_series/46082/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d227b027d4fc4a4e9a984cf29c29ec5b567f81d8 --- /dev/null +++ b/marked/Rel-18/46_series/46082/raw.md @@ -0,0 +1,708 @@ + + +# 3GPP TS 46.082 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Voice Activity Detector (VAD) for Enhanced Full Rate (EFR) speech traffic channels (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## --- **Keywords** + +GSM, speech, codec + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|-------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Symbols..... | 5 | +| 3.2.1 Variables..... | 5 | +| 3.2.2 Constants ..... | 6 | +| 3.2.3 Functions ..... | 6 | +| 3.3 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 5 Functional description..... | 7 | +| 5.1 Overview and principles of operation ..... | 7 | +| 5.2 Algorithm description ..... | 7 | +| 5.2.1 Adaptive filtering and energy computation ..... | 8 | +| 5.2.2 ACF averaging..... | 9 | +| 5.2.3 Predictor values computation ..... | 9 | +| 5.2.4 Spectral comparison ..... | 10 | +| 5.2.5 Information tone detection ..... | 10 | +| 5.2.6 Threshold adaptation ..... | 11 | +| 5.2.7 VAD decision ..... | 12 | +| 5.2.8 VAD hangover addition ..... | 13 | +| 5.2.9 Periodicity detection..... | 13 | +| 6 Computational description overview ..... | 14 | +| 6.1 VAD modules..... | 14 | +| 6.2 Pseudo-floating point arithmetic ..... | 14 | +| Annex A (informative): Simplified block filtering operation..... | 16 | +| Annex B (informative): Pole frequency calculation..... | 17 | +| Annex C (informative): Change history..... | 18 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels within the digital cellular telecommunications system. + +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 Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.81 [5] Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels. + +The requirements are mandatory on any VAD to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the enhanced full-rate speech traffic channel. + +# 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec". +- [3] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test vectors for the GSM Enhanced Full Rate (EFR) speech codec". +- [4] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding". +- [5] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**noise:** signal component resulting from acoustic environmental noise. + +**mobile environment:** any environment in which mobile stations may be used. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +### 3.2.1 Variables + +| | | +|------|-------------------------------------------| +| aav1 | filter predictor values, see clause 5.2.3 | +|------|-------------------------------------------| + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------| +| acf | the ACF vector which is calculated in the speech encoder (GSM 06.60 [4]) | +| adaptcount | secondary hangover counter, see clause 5.2.6 | +| av0 | averaged ACF vector, see clause 5.2.2 | +| av1 | a previous value of av0, see clause 5.2.2 | +| burstcount | speech burst length counter, see clause 5.2.8 | +| den | denominator of left hand side of equation 8 in annex B, see clause 5.2.5 | +| difference | difference between consecutive values of dm, see clause 5.2.4 | +| dm | spectral distortion measure, see clause 5.2.4 | +| hangcount | primary hangover counter, see clause 5.2.8 | +| lagcount | number of subframes in current frame meeting periodicity criterion, see clause 5.2.9 | +| lastdm | previous value of dm, see clause 5.2.4 | +| lags | the open loop long term predictor lags for the two halves of the speech encoder frame (GSM 06.60 [4]) | +| num | numerator of left hand side of equation 8 in annex B, see clause 5.2.5 | +| oldlagcount | previous value of lagcount, see clause 5.2.9 | +| prederr | fourth order short term prediction error, see clause 5.2.5 | +| ptch | Boolean flag indicating the presence of a periodic signal component, see clause 5.2.9 | +| pvad | energy in the current filtered signal frame, see clause 5.2.1 | +| rav1 | autocorrelation vector obtained from av1, see clause 5.2.3 | +| rc | the first four unquantized reflection coefficients calculated in the speech encoder (GSM 06.60 [4]) | +| rvad | autocorrelation vector of the adaptive filter predictor values, see clause 5.2.6 | +| smalllag | difference between consecutive lag values, see clause 5.2.9 | +| stat | Boolean flag indicating that the frequency spectrum of the input signal is stationary, see clause 5.2.4 | +| thvad | adaptive primary VAD threshold, see clause 5.2.6 | +| tone | Boolean flag indicating the presence of an information tone, see clause 5.2.5 | +| vadflag | Boolean VAD decision with hangover included, see clause 5.2.8 | +| veryoldlagcount | previous value of oldlagcount, see clause 5.2.9 | +| vvad | Boolean VAD decision before hangover, see clause 5.2.7 | + +### 3.2.2 Constants + +| | | +|------------|-----------------------------------------------------------------------------| +| adp | number of frames of hangover for secondary VAD, see clause 5.2.6 | +| burstconst | minimum length of speech burst to which hangover is added, see clause 5.2.8 | +| dec | determines rate of decrease in adaptive threshold, see clause 5.2.6 | +| fac | determines steady state adaptive threshold, see clause 5.2.6 | +| frames | number of frames over which av0 and av1 are calculated, see clause 5.2.2 | +| freqth | threshold for pole frequency decision, see clause 5.2.5 | +| hangconst | number of frames of hangover for primary VAD, see clause 5.2.8 | +| inc | determines rate of increase in adaptive threshold, see clause 5.2.6 | +| lthresh | lag difference threshold for periodicity decision, see clause 5.2.9 | +| margin | determines upper limit for adaptive threshold, see clause 5.2.6 | +| nthresh | frame count threshold for periodicity decision, see clause 5.2.9 | +| plev | lower limit for adaptive threshold, see clause 5.2.6 | +| predth | threshold for short term prediction error, see clause 5.2.5 | +| pth | energy threshold, see clause 5.2.6 | +| thresh | decision threshold for evaluation of stat flag, see clause 5.2.4 | + +### 3.2.3 Functions + +| | | +|------------|---------------------------------------------| +| + | addition | +| - | subtraction | +| * | multiplication | +| / | division | +| x | absolute value of x | +| AND | Boolean AND | +| OR | Boolean OR | +| b | | +| MULT(x(i)) | the product of the series x(i) for i=a to b | +| i=a | | +| b | | + +SUM(x(i))      the sum of the series x(i) for i=a to b +i=a + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|---------------------------------------| +| ACF | Autocorrelation function | +| ANSI | American National Standards Institute | +| DTX | Discontinuous Transmission | +| LTP | Long Term Predictor | +| TX | Transmission | +| VAD | Voice Activity Detector | + +For abbreviations not given in this clause, see GSM 01.04 [1]. + +# --- 4 General + +The function of the VAD is to indicate whether each 20 ms frame produced by the speech encoder contains speech or not. The output is a Boolean flag (vadflag) which is used by the Transmit (TX) DTX handler defined in GSM 06.81 [5]. + +The present document is organized as follows. + +Clause 5 describes the principles of operation of the VAD. Clause 6 provides an overview of the computational description of the VAD. The computational details necessary for the fixed point implementation of the VAD algorithm are given in the form of ANSI C program contained in GSM 06.53 [2]. + +The verification of the VAD is based on the use of digital test sequences which are described in GSM 06.54 [3]. + +# --- 5 Functional description + +The purpose of this clause is to give the reader an understanding of the principles of operation of the VAD, whereas GSM 06.53 [2] contains the fixed point computational description of the VAD. In the case of discrepancy between the two descriptions, the description in GSM 06.53 [2] will prevail. + +## 5.1 Overview and principles of operation + +The function of the VAD is to distinguish between noise with speech present and noise without speech present. This is achieved by comparing the energy of a filtered version of the input signal with a threshold. The presence of speech is indicated whenever the threshold is exceeded. + +The detection of speech in a mobile environment is difficult due to the low speech/noise ratios which are encountered, particularly in moving vehicles. To increase the probability of detecting speech the input signal is adaptively filtered (see clause 5.2.1) to reduce its noise content before the voice activity decision is made (see clause 5.2.7). + +The frequency spectrum and level of the noise may vary within a given environment as well as between different environments. It is therefore necessary to adapt the input filter coefficients and energy threshold at regular intervals as described in clause 5.2.6. + +## 5.2 Algorithm description + +The block diagram of the VAD algorithm is shown in figure 1. The individual blocks are described in the following clauses. The variables shown in the block diagram are described in table 1. + +Table 1: Description of variables in figure 1 + +| Var | Description | +|---------|--------------------------------------------------------------------------------------------------------| +| acf | The ACF vector which is calculated in the speech encoder (GSM 06.60 [4]). | +| av0 | Averaged ACF vector. | +| av1 | A previous value of av0. | +| lags | The open loop long term predictor lags for the two halves of the speech encoder frame (GSM 06.60 [4]). | +| ptch | Boolean flag indicating the presence of a periodic signal component. | +| pvad | Energy in the current filtered signal frame. | +| rav1 | Autocorrelation vector obtained from av1. | +| rc | The first four reflection coefficients calculated in the speech encoder (GSM 06.60 [4]). | +| rvad | Autocorrelation vector of the adaptive filter predictor values. | +| stat | Boolean flag indicating that the frequency spectrum of the input signal is stationary. | +| thvad | Adaptive primary VAD threshold. | +| tone | Boolean flag indicating the presence of an information tone. | +| vadflag | Boolean VAD decision with hangover included. | +| vvad | Boolean VAD decision before hangover. | + +![Functional block diagram of the VAD. The diagram shows the flow of data from input variables (acf, lags, rc) through various processing blocks to the output vadflag. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Data flow is indicated by arrows, with some blocks providing feedback or control signals to others.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +``` + +graph LR + acf --> AEC[Adaptive filtering and energy computation] + lags --> PD[Periodicity detection] + rc --> TD[Tone detection] + acf --> AVC[ACF averaging] + acf --> P[Predictor values computation] + PD -- ptch --> TA[Threshold adaptation] + TD -- tone --> TA + AVC -- av0 --> SC[Spectral comparison] + AVC -- av1 --> P + P -- rav1 --> SC + SC -- stat --> TA + SC -- thvad --> VD[VAD decision] + AEC -- pvad --> VD + AEC -- rvad --> TA + VD -- vvad --> VHA[VAD hangover addition] + VHA -- vadflag --> Output + +``` + +Functional block diagram of the VAD. The diagram shows the flow of data from input variables (acf, lags, rc) through various processing blocks to the output vadflag. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Data flow is indicated by arrows, with some blocks providing feedback or control signals to others. + +Figure 1: Functional block diagram of the VAD + +### 5.2.1 Adaptive filtering and energy computation + +The energy in the current filtered signal frame (pvad) is computed as follows: + +$$pvad = rvad[0] * acf[0] + 2 * \sum_{i=1}^8 (rvad[i] * acf[i]) \quad (1)$$ + +This corresponds to performing an 8th order block filtering on the filtered input samples to the speech encoder. This is explained in annex A. + +### 5.2.2 ACF averaging + +Spectral characteristics of the input signal have to be obtained using blocks that are larger than one 20 ms frame. This is done by averaging the ACF (autocorrelation function) values for several consecutive frames. The averaging is given by the following equations: + +$$\text{av0}\{n\}[i] = \sum_{j=0}^{\text{frames}-1} (\text{acf}\{n-j\}[i]) \quad ; i = 0..8 \quad (2)$$ + +$$\text{av1}\{n\}[i] = \text{av0}\{n-\text{frames}\}[i] \quad ; i = 0..8 \quad (3)$$ + +where (n) represents the current frame, (n-1) represents the previous frame. The values of constants are given in table 2. + +**Table 2: Constants and variables for ACF averaging** + +| Constant | Value | Variable | Initial value | +|----------|-------|------------------------------|---------------| +| frames | 4 | previous ACF's,
av0 & av1 | All set to 0 | + +### 5.2.3 Predictor values computation + +The filter predictor values aav1 are obtained from the autocorrelation values av1 according to the equation: + +$$a = R^{-1}p \quad (4)$$ + +where: + +$$R = \begin{bmatrix} \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] & \text{av1}[4] & \text{av1}[5] & \text{av1}[6] & \text{av1}[7] \\ \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] & \text{av1}[4] & \text{av1}[5] & \text{av1}[6] \\ \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] & \text{av1}[4] & \text{av1}[5] \\ \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] & \text{av1}[4] \\ \text{av1}[4] & \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] \\ \text{av1}[5] & \text{av1}[4] & \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] \\ \text{av1}[6] & \text{av1}[5] & \text{av1}[4] & \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] \\ \text{av1}[7] & \text{av1}[6] & \text{av1}[5] & \text{av1}[4] & \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] \end{bmatrix}$$ + +and: + +$$p = \begin{bmatrix} \text{av1}[1] \\ \text{av1}[2] \\ \text{av1}[3] \\ \text{av1}[4] \\ \text{av1}[5] \\ \text{av1}[6] \\ \text{av1}[7] \\ \text{av1}[8] \end{bmatrix} \quad a = \begin{bmatrix} \text{aav1}[1] \\ \text{aav1}[2] \\ \text{aav1}[3] \\ \text{aav1}[4] \\ \text{aav1}[5] \\ \text{aav1}[6] \\ \text{aav1}[7] \\ \text{aav1}[8] \end{bmatrix}$$ + +``` +aav1[0] = -1 +``` + +av1 is used in preference to av0 as the latter may contain speech. The autocorrelated predictor values rav1 are then obtained: + +$$\text{rav1}[i] = \sum_{k=0}^{8-i} (\text{aav1}[k] * \text{aav1}[k+i]) \quad ; i = 0..8 \quad (5)$$ + +### 5.2.4 Spectral comparison + +The spectra represented by the autocorrelated predictor values rav1 and the averaged autocorrelation values av0 are compared using the distortion measure (dm) defined below. This measure is used to produce a Boolean value stat every 20 ms, as shown in the following equations: + +$$\text{dm} = (\text{rav1}[0] * \text{av0}[0] + 2 * \sum_{i=1}^8 (\text{rav1}[i] * \text{av0}[i])) / \text{av0}[0] \quad (6a)$$ + +$$\text{difference} = |\text{dm} - \text{lastdm}| \quad (6b)$$ + +$$\text{lastdm} = \text{dm} \quad (6c)$$ + +$$\text{stat} = (\text{difference} < \text{thresh}) \quad (6d)$$ + +The values of constants and initial values are given in table 3. + +**Table 3: Constants and variables for spectral comparison** + +| Constant | Value | Variable | Initial value | +|----------|-------|----------|---------------| +| thresh | 0.056 | lastdm | 0 | + +### 5.2.5 Information tone detection + +Information tones and noise can be classified by inspecting the short term prediction gain, information tones resulting in a higher prediction gain than noise. Tones can therefore be detected by comparing the prediction gain to a fixed threshold. By limiting the prediction gain calculation to a fourth order analysis, information signals consisting of one or two tones can be detected whilst minimizing the prediction gain for noise. + +The prediction gain decision is implemented by comparing the normalized short term prediction error with the short term prediction error threshold (predth). This measure is used to produce a Boolean value, tone, every 20 ms. The signal is classified as a tone if the prediction error is less than predth. This is equivalent to a prediction gain threshold of 13.5 dB. + +Vehicle noise can contain strong resonances at low frequencies, resulting in a high prediction gain. A further test is therefore made to determine the pole frequency of a second order analysis of the signal frame. The signal is classified as noise if the frequency of the pole is less than 385 Hz. + +The algorithm for evaluating the Boolean tone flag is as follows: + +``` +tone = false +den = a[1]*a[1] +num = 4*a[2] - a[1]*a[1] +if (num <= 0) + return + +if ((a[1] < 0) AND (num/den < freqth)) + return +``` + +4 + +``` + +prederr = MULT (1 - rc[i] * rc[i]) + i=1 + +if (prederr < predth) + tone = true + +return + +``` + +rc[1..4] are the first four unquantized reflection coefficients obtained from the speech encoder short term predictor. The coefficients a[0..2] are transversal filter coefficients calculated from rc[1..2] using the step up routine. The pole frequency calculation is described in annex B. + +The values of the constants are given in table 4. + +**Table 4: Constants for information tone detection** + +| Constant | Value | +|----------|--------| +| freqth | 0,0973 | +| predth | 0,0447 | + +### 5.2.6 Threshold adaptation + +A check is made every 20 ms to determine whether the VAD decision threshold, (thvad) should be changed. This adaptation is carried out according to the flowchart shown in figure 2. The values of the constants and initial variable values are given in table 5. + +Adaptation of thvad takes place in two different situations: + +In the first case, the decision threshold (thvad) is set to the lower limit for the adaptive threshold (plev) if the input signal frame energy (acf[0]) is less than the energy threshold (pth). The autocorrelation vector of the adaptive filter predictor values (rvad) remains unchanged. + +In the second case, thvad and rvad are adapted if there is a low probability that speech or information tones are present. This occurs when the following conditions are met: + +- a) The frequency spectrum of the input signal is stationary (clause 5.2.4). +- b) The signal does not contain a periodic component (clause 5.2.9). +- c) Information tones are not present (clause 5.2.5). + +The autocorrelation vector of the adaptive filter predictor values (rvad) is updated with the rav1 values. The step size by which thvad is adapted is not constant but a proportion of the current value and its rate of increase or decrease is determined by constants inc and dec respectively. + +The adaptation begins by experimentally multiplying thvad by a factor of $(1-1/\text{dec})$ . If thvad is now higher than or equal to pvad times the steady state adaptive threshold constant (fac), then thvad needed to be decreased and it is left at this new lower level. If, on the other hand, thvad is less than pvad times fac then it either needs to be increased or kept constant. In this case, it is multiplied by a factor of $(1+1/\text{inc})$ or set to pvad times fac whichever yields the lower value. Thvad is never allowed to be greater than pvad+upper adaptive threshold limit (margin). + +**Table 5: Constants and variables threshold adaptation** + +| Constant | Value | Variable | Initial value | +|----------|--------|------------|---------------| +| pth | 130000 | margin | 69333340 | +| plev | 346667 | adaptcount | 0 | +| fac | 2,1 | thvad | 866656 | +| adp | 8 | rvad[0] | 6 | +| inc | 16 | rvad[1..8] | All set to 0 | +| dec | 32 | | | + +![Flow diagram for threshold adaptation. The process starts at BEGIN, checks if acf[0] < pth. If yes, th_vad = plev. If no, checks if stat and not ptch and not tone. If yes, increment adaptcount. If no, adaptcount = 0. Then checks if adaptcount > adp. If yes, th_vad = th_vad - th_vad / dec. If no, END. Next checks if th_vad < pvad * fac. If yes, th_vad = min(th_vad + th_vad / inc, pvad * fac). If no, next checks if th_vad > pvad + margin. If yes, th_vad = pvad + margin. If no, rvad = favl. Finally, adaptcount = adp + 1, and END.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +graph TD + BEGIN((BEGIN)) --> D1{acf[0] < pth ?} + D1 -- yes --> P1[th_vad = plev] + D1 -- no --> D2{stat and not ptch and not tone ?} + D2 -- yes --> P2[increment adaptcount] + D2 -- no --> P3[adaptcount = 0] + P2 --> D3{adaptcount > adp ?} + P3 --> D3 + D3 -- yes --> P4[th_vad = th_vad - th_vad / dec] + D3 -- no --> END1((END)) + P4 --> D4{th_vad < pvad * fac ?} + D4 -- yes --> P5[th_vad = min ( th_vad + th_vad / inc, pvad * fac )] + D4 -- no --> D5{th_vad > pvad + margin ?} + P5 --> D5 + D5 -- yes --> P6[th_vad = pvad + margin] + D5 -- no --> P7[rvad = favl] + P6 --> P7 + P7 --> P8[adaptcount = adp + 1] + P8 --> END2((END)) + +``` + +Flow diagram for threshold adaptation. The process starts at BEGIN, checks if acf[0] < pth. If yes, th\_vad = plev. If no, checks if stat and not ptch and not tone. If yes, increment adaptcount. If no, adaptcount = 0. Then checks if adaptcount > adp. If yes, th\_vad = th\_vad - th\_vad / dec. If no, END. Next checks if th\_vad < pvad \* fac. If yes, th\_vad = min(th\_vad + th\_vad / inc, pvad \* fac). If no, next checks if th\_vad > pvad + margin. If yes, th\_vad = pvad + margin. If no, rvad = favl. Finally, adaptcount = adp + 1, and END. + +Figure 2: Flow diagram for threshold adaptation + +### 5.2.7 VAD decision + +Prior to hangover the Boolean VAD decision is defined as: + +$$vvad = (pvad > thvad)$$ + +### 5.2.8 VAD hangover addition + +VAD hangover is only added to bursts of speech greater than or equal to burstconst blocks. The Boolean variable vadflag indicates the decision of the VAD with hangover included. The values of the constants and initial variable values are given in table 6. The hangover algorithm is as follows: + +``` + +if (vvad) + increment(burstcount) +else + burstcount = 0 + +if (burstcount >= burstconst) +{ + hangcount = hangconst + burstcount = burstconst +} + +vadflag = (vvad OR (hangcount >= 0)) + +if (hangcount >= 0) + decrement(hangcount) + +``` + +**Table 6: Constants and variables for VAD hangover addition** + +| Constant | Value | Variable | Initial value | +|------------|-------|------------|---------------| +| burstconst | 3 | burstcount | 0 | +| hangconst | 10 | hangcount | -1 | + +### 5.2.9 Periodicity detection + +The variables thvad and rvad are updated when the frequency spectrum of the input signal is stationary. However, vowel sounds also have a stationary frequency spectrum. The Boolean variable ptch indicates the presence of a periodic signal component and prevents adaptation of thvad and rvad. The variable ptch is updated every 20 ms and is true when periodicity (a vowel sound) is detected. The periodicity detector identifies the vowel sounds by comparing consecutive Long Term Predictor (LTP) lag values lags[1..2] which are obtained during the open loop pitch lag search from the speech codec defined in GSM 06.60 [4]. Cases in which one lag value is near the other are catered for, however the cases in which one lag value is a factor of the other, or in which both lag values have a common factor, are not. + +``` + +lagcount = 0 + +for (j = 1; j <= 2; j++) +{ + smallag = maximum(lags[j], lags[j-1]) - minimum(lags[j], lags[j-1]) + + if ((smallag - lthresh) < 0) + increment(lagcount) +} + +veryoldlagcount = oldlagcount +oldlagcount = lagcount + +ptch = (oldlagcount + veryoldlagcount >= nthresh) + +``` + +The values of constants and initial values are given in table 7. lags[0] = lags[2] of the previous frame. + +ptch is calculated after the VAD decision and when the current LTP lag values lags[1..2] are available. This reduces the delay of the VAD decision. + +**Table 7: Constants and variables for periodicity detection** + +| Constant | Value | Variable | Initial value | +|----------|-------|-----------------|---------------| +| lthresh | 2 | ptch | 1 | +| nthresh | 4 | oldlagcount | 0 | +| | | veryoldlagcount | 0 | +| | | lags[0] | 18 | + +# 6 Computational description overview + +The computational details necessary for the fixed point implementation of the speech transcoding and DTX functions are given in the form of an American National Standards Institute (ANSI) C program contained in GSM 06.53 [2]. This clause provides an overview of the modules which describe the computation of the VAD algorithm. + +## 6.1 VAD modules + +The computational description of the VAD is divided into three ANSI C modules. These modules are: + +- vad\_reset; +- vad\_computation; +- periodicity\_update. + +The vad\_reset module sets the VAD variables to their initial values. + +The vad\_computation module is divided into nine sub-modules which correspond to the blocks of figure 1 in the high level description of the VAD algorithm. The vad\_computation module can be called as soon as the acf[0..8] and rc[1..4] variables are known. This means that the VAD computation can take place after the levinson routine of the second half of the frame in the speech encoder (GSM 06.60 [4]). The vad\_computation module also requires the value of the ptch variable calculated in the previous frame. + +The ptch variable is calculated by the periodicity\_update module from the lags[1..2] variable. The individual lag values are calculated by the open loop pitch search routine in the speech encoder (GSM 06.60 [4]). The periodicity\_update module is called after the VAD decision and when the current LTP lag values lags[1..2] are available. + +## 6.2 Pseudo-floating point arithmetic + +All the arithmetic operations follow the precision and format used in the computational description of the speech codec in GSM 06.53 [2]. To increase the precision within the fixed point implementation, a pseudo-floating point representation of some variables is used. This applies to the following variables (and related constants) of the VAD algorithm: + +- pvad: Energy of filtered signal; +- thvad: Threshold of the VAD decision; +- acf0: Energy of input signal. + +For the representation of these variables, two 16-bit integers are needed: + +- one for the exponent (e\_pvad, e\_thvad, e\_acf0); +- one for the mantissa (m\_pvad, m\_thvad, m\_acf0). + +The value e\_pvad represents the lowest power of 2 just greater or equal to the actual value of pvad and the m\_pvad value represents an integer which is always greater or equal to 16 384 (normalized mantissa). It means that the pvad value is equal to: + +$$\text{pvad} = 2^{e\_pvad} * (m\_pvad/32768) \quad (7)$$ + +This scheme provides a large dynamic range for the pvad value and always keeps a precision of 16 bits. All the comparisons are easy to make by comparing the exponents of two variables. The VAD algorithm needs only one pseudo-floating point addition and multiplication. All the computations related to the pseudo-floating point variables require simple 16- or 32-bit arithmetic operations defined in the detailed description of the speech codec. + +Some constants, represented by a pseudo-floating point format, are needed and symbolic names (in capital letters) for their exponent and mantissa are used; table 8 lists all these constants with the associated symbolic names and their numerical constant values. + +Table 8: List of floating point constants + +| Constant | Exponent | Mantissa | +|----------|---------------|------------------| +| pth | E_PTH = 17 | M_PTH = 32500 | +| margin | E_MARGIN = 27 | M_MARGIN = 16927 | +| plev | E_PLEV = 19 | M_PLEV = 21667 | + +## Annex A (informative): Simplified block filtering operation + +Consider an 8th order transversal filter with filter coefficients $a_0..a_8$ , through which a signal is being passed, the output of the filter being: + +$$s'[n] = - \sum_{i=0}^8 (a[i]*s[n-i]) \quad (1)$$ + +If we apply block filtering over 20 ms segments, then this equation becomes: + +$$s'[n] = - \sum_{i=0}^8 (a[i]*s[n-i]) \quad ; n = 0..167 \quad (2)$$ + +; 0 ≤ n-i ≤ 159 + +If the energy of the filtered signal is then obtained for every 20 ms segment, the equation for this is: + +$$pvad = \sum_{n=0}^{167} \left( - \sum_{i=0}^8 (a[i]*s[n-i]) \right)^2 \quad ; 0 \leq n-i \leq 159 \quad (3)$$ + +We know that: + +$$acf[i] = \sum_{n=0}^{159} (s[n]*s[n-i]) \quad ; i = 0..8 \quad (4)$$ + +; 0 ≤ n-i ≤ 159 + +If equation (3) is expanded and $acf[0..8]$ are substituted for $s[n]$ then we arrive at the equations: + +$$pvad = r[0]*acf[0] + 2* \sum_{i=1}^8 (r[i]*acf[i]) \quad (5)$$ + +Where: + +$$r[i] = \sum_{k=0}^{8-i} (a[k]*a[k+i]) \quad ; i = 0..8 \quad (6)$$ + +## Annex B (informative): Pole frequency calculation + +This annex describes the algorithm used to determine whether the pole frequency for a second order analysis of the signal frame is less than 385 Hz. + +The filter coefficients for a second order synthesis filter are calculated from the first two unquantized reflection coefficients $rc[1..2]$ obtained from the speech encoder. This is done using the step up routine described in GSM 06.53 [2]. If the filter coefficients $a[0..2]$ are defined such that the synthesis filter response is given by: + +$$H(z) = 1/(a[0] + a[1]z^{-1} + a[2]z^{-2}) \quad (1)$$ + +Then the positions of the poles in the Z-plane are given by the solutions to the following quadratic: + +$$a[0]z^2 + a[1]z + a[2] = 0, \quad a[0] = 1 \quad (2)$$ + +The positions of the poles, $z$ , are therefore: + +$$z = re \pm j*sqrt(im), \quad j^2 = -1 \quad (3)$$ + +where: + +$$re = - a[1] / 2 \quad (4)$$ + +$$im = (4*a[2] - a[1]^2)/4 \quad (5)$$ + +If $im$ is negative then the poles lie on the real axis of the Z-plane and the signal is not a tone and the algorithm terminates. If $re$ is negative then the poles lie in the left hand side of the Z-plane and the frequency is greater than 2000 Hz and the prediction error test can be performed. + +If $im$ is positive and $re$ is positive then the poles are complex and lie in the right hand side of the Z-plane and the frequency in Hz is related to $re$ and $im$ by the expression: + +$$freq = \arctan(sqrt(im)/re)*4000/pi \quad (6)$$ + +Having ensured that both $im$ and $re$ are positive the test for a pole frequency less than 385 Hz can be derived by substituting equations 4 and 5 into equation 6 and re-arranging: + +$$(4*a[2] - a[1]^2)/a[1]^2 < \tan^2(pi*385/4000) \quad (7)$$ + +or + +$$(4*a[2] - a[1]^2)/a[1]^2 < 0.0973 \quad (8)$$ + +If this test is true then the signal is not a tone and the algorithm terminates, otherwise the prediction error test is performed. + +# Annex C (informative): Change history + +| Change history | | | | | | +|----------------|-----------|---------|-----------------|-------------|-----------------------------------------| +| SMG No. | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments | +| SMG#22 | | | | 4.0.1 | ETSI Publication | +| SMG#20 | | | | 5.0.3 | Release 1996 version | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#29 | | | | 7.0.0 | Release 1998 version | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Release 1999 version | +| | | | | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|----------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | | | | Version for Release 4 | | 4.0.0 | +| 06-2002 | 16 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 07-2007 | | | | | Makes matrices in §5.2.3 visible | 7.0.0 | 7.0.1 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.0.1 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 65 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 70 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03-2017 | SA#75 | | | | | Version for Release 14 | 14.0.0 | +| 06-2018 | SA#80 | | | | | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file